diff --git a/content/nomad/v0.11.x/content/api-docs/acl-policies.mdx b/content/nomad/v0.11.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..9611f95bf1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,168 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+sidebar_title: ACL Policies
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/acl-tokens.mdx b/content/nomad/v0.11.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..9cca68460b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,344 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+sidebar_title: ACL Tokens
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](https://learn.hashicorp.com/nomad?track=acls#acls) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/agent.mdx b/content/nomad/v0.11.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..0d46c58514
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/agent.mdx
@@ -0,0 +1,644 @@
+---
+layout: api
+page_title: Agent - HTTP API
+sidebar_title: Agent
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string!
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "protocol_version_max": "3",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "protocol_version": "1",
+      "protocol_version_min": "0",
+      "snapshot_version_min": "0",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/allocations.mdx b/content/nomad/v0.11.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..a128d60d9d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/allocations.mdx
@@ -0,0 +1,690 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+sidebar_title: Allocations
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": "5000000000"
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2017-07-25T23:36:26.106431265Z",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400,
+    "ModifyTime": 1495747371794276400
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:3.2"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:3.2"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was singled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Task": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/client.mdx b/content/nomad/v0.11.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..e90601b6ca
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/client.mdx
@@ -0,0 +1,618 @@
+---
+layout: api
+page_title: Client - HTTP API
+sidebar_title: Client
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/deployments.mdx b/content/nomad/v0.11.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..6554454661
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/deployments.mdx
@@ -0,0 +1,493 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+sidebar_title: Deployments
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/evaluations.mdx b/content/nomad/v0.11.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..02c576e2f5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,267 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+sidebar_title: Evaluations
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Priority": 50,
+  "Type": "service",
+  "TriggeredBy": "job-register",
+  "JobID": "example",
+  "JobModifyIndex": 52,
+  "NodeID": "",
+  "NodeModifyIndex": 0,
+  "Status": "complete",
+  "StatusDescription": "",
+  "Wait": 0,
+  "NextEval": "",
+  "PreviousEval": "",
+  "BlockedEval": "",
+  "FailedTGAllocs": null,
+  "ClassEligibility": null,
+  "EscapedComputedClass": false,
+  "AnnotatePlan": false,
+  "SnapshotIndex": 53,
+  "QueuedAllocations": {
+    "cache": 0
+  },
+  "CreateIndex": 53,
+  "ModifyIndex": 55
+}
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/index.mdx b/content/nomad/v0.11.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..e0f5a4b8d9
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/index.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: HTTP API
+sidebar_title: HTTP API Overview
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+This documentation is only for the v1 API.
+
+~> **Backwards compatibility:** At the current version, Nomad does not yet
+promise backwards compatibility even with the v1 prefix. We'll remove this
+warning when this policy changes. We expect to reach API stability by Nomad
+1.0.
+
+## Addressing &amp; Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v0.11.x/content/api-docs/jobs.mdx b/content/nomad/v0.11.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..1096087790
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/jobs.mdx
@@ -0,0 +1,1858 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+sidebar_title: Jobs
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 300000000000,
+          "Attempts": 10,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 36000000000000,
+          "MaxDelay": 3600000000000,
+          "Unlimited": false
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" { type = \"service\" group \"cache\" {} }",
+  "Canonicalize": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Stop": false,
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Update": {
+          "Stagger": 0,
+          "MaxParallel": 1,
+          "HealthCheck": "checks",
+          "MinHealthyTime": 10000000000,
+          "HealthyDeadline": 300000000000,
+          "AutoRevert": false,
+          "Canary": 0
+        },
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": [
+          {
+            "Attribute": "${node.datacenter}",
+            "SpreadTarget": null,
+            "Weight": 100
+          }
+        ],
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Spreads": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 1,
+      "HealthCheck": "",
+      "MinHealthyTime": 0,
+      "HealthyDeadline": 0,
+      "AutoRevert": false,
+      "Canary": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Spreads": null,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stable": false,
+    "Version": 0,
+    "CreateIndex": 7,
+    "ModifyIndex": 7,
+    "JobModifyIndex": 7
+  }
+]
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 15 KB.
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": "...",
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `purge` `(bool: false)` - Specifies that the job should stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status <sup>Beta</sup>
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group <sup>Beta</sup>
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Reason` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Reason` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Reason` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Reason": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/json-jobs.mdx b/content/nomad/v0.11.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..36d454696d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1064 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+sidebar_title: JSON Jobs
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+This guide covers the JSON syntax for submitting jobs to Nomad. A useful command
+for generating valid JSON versions of HCL jobs is:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+## Syntax
+
+Below is the JSON representation of the job outputted by `$ nomad init`:
+
+```json
+{
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Migrate": {
+          "HealthCheck": "checks",
+          "HealthyDeadline": 300000000000,
+          "MaxParallel": 1,
+          "MinHealthyTime": 10000000000
+        },
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Header": {},
+                    "Method": "",
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false,
+                    "CheckRestart": {
+                      "Limit": 3,
+                      "Grace": 30000000000,
+                      "IgnoreWarnings": false
+                    }
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 0,
+          "MaxDelay": 3600000000000,
+          "Unlimited": true
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+The example JSON could be submitted as a job using the following:
+
+```shell-session
+$ curl -XPUT -d @example.json http://127.0.0.1:4646/v1/job/example
+{
+  "EvalID": "5d6ded54-0b2a-8858-6583-be5f476dec9d",
+  "EvalCreateIndex": 12,
+  "JobModifyIndex": 11,
+  "Warnings": "",
+  "Index": 12,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Values other than default are not allowed in non-Enterprise versions of Nomad.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the Qemu driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+  - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+    checks do not have an `auto` address mode as there's no way for
+    Nomad to know which is the best address to use for checks. Consul
+    needs access to the address for any HTTP or TCP checks. Added in
+    Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+    from the `Service`.
+
+  - `PortLabel`: Specifies the label of the port on which the check will
+    be performed. Note this is the _label_ of the port and not the port
+    number unless `AddressMode: "driver"`. The port label must match one
+    defined in the Network stanza. If a port value was declared on the
+    `Service`, this will inherit from that value if not supplied. If
+    supplied, this value takes precedence over the `Service.PortLabel`
+    value. This is useful for services which operate on multiple ports.
+    `http` and `tcp` checks require a port while `script` checks do not.
+    Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+    later numeric ports may be used if `AddressMode: "driver"` is set on
+    the check.
+
+  - `Header`: Headers for HTTP checks. Should be an object where the values are an
+    array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+  - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+    certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update stanza can be specified at the job or task group level.
+When specified at the job, the update stanza is inherited by all task groups.
+When specified in both the job and in a task group, the stanzas are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /docs/commands/node/drain
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v0.11.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v0.11.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..b708c4e1da
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+sidebar_title: Libraries &amp; SDKs
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/master/api) - Official Golang
+  client for the Nomad HTTP API
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Official Ruby client
+  for the Nomad HTTP API
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v0.11.x/content/api-docs/metrics.mdx b/content/nomad/v0.11.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..d2d5407732
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/metrics.mdx
@@ -0,0 +1,97 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+sidebar_title: Metrics
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/namespaces.mdx b/content/nomad/v0.11.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..8173ddb14c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+sidebar_title: Namespaces
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 31,
+    "Description": "Production API Servers",
+    "ModifyIndex": 31,
+    "Name": "api-prod",
+    "Quota": ""
+  },
+  {
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 5,
+    "Name": "default",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 31,
+  "Description": "Production API Servers",
+  "Quota": "",
+  "Hash": "N8WvePwqkp6J354eLJMKyhvsFdPELAos0VuBfMoVKoU=",
+  "ModifyIndex": 31,
+  "Name": "api-prod"
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Quota": "prod-quota"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/nodes.mdx b/content/nomad/v0.11.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..3ff11dd0b7
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1018 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+sidebar_title: Nodes
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "0.10.0-dev",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 0,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2019-08-26T12:22:50+02:00"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 9,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": null,
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v0.11.x/content/api-docs/operator.mdx b/content/nomad/v0.11.x/content/api-docs/operator.mdx
new file mode 100644
index 0000000000..eb5fd9dea8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/operator.mdx
@@ -0,0 +1,473 @@
+---
+layout: api
+page_title: Operator - HTTP API
+sidebar_title: Operator
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# /v1/operator
+
+The `/operator` endpoint provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/docs/commands/operator) command.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4
+```
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:8300",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:8205",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. This API was introduced in
+Nomad 0.9 and currently supports enabling/disabling preemption. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "ModifyIndex": 5,
+    "SchedulerAlgorithm": "spread",
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft commit index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler binpacks or spreads allocations on available nodes.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `BatchSchedulerEnabled` `(bool: false)` (Enterprise Only) - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` (Enterprise Only) - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server stanza will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes.  Possible values are
+  `"binpack"` and `"spread"`
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+- `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+  system jobs is enabled. Note that if this is set to true, then system jobs
+  can preempt any other jobs.
+
+- `BatchSchedulerEnabled` `(bool: false)` (Enterprise Only) - Specifies
+  whether preemption for batch jobs is enabled. Note that if this is set to
+  true, then batch jobs can preempt any other jobs.
+
+- `ServiceSchedulerEnabled` `(bool: false)` (Enterprise Only) - Specifies
+  whether preemption for service jobs is enabled. Note that if this is set to
+  true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v0.11.x/content/api-docs/plugins.mdx b/content/nomad/v0.11.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..1d717995fd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/plugins.mdx
@@ -0,0 +1,141 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+sidebar_title: Plugins
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Topologies": [
+      {"key": "val"},
+      {"key": "val2"}
+    ],
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/quotas.mdx b/content/nomad/v0.11.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..a9e2febd42
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/quotas.mdx
@@ -0,0 +1,351 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+sidebar_title: Quotas
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://github.com/hashicorp/nomad/blob/master/api/quota.go#L100-L131).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/regions.mdx b/content/nomad/v0.11.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..dd0559f09d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/regions.mdx
@@ -0,0 +1,37 @@
+---
+layout: api
+page_title: Regions - HTTP API
+sidebar_title: Regions
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/scaling-policies.mdx b/content/nomad/v0.11.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..626c6986f3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,103 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+sidebar_title: Scaling Policies <sup>Beta</sup>
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies <sup>Beta</sup>
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 10,
+    "Enabled": true,
+    "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+    "ModifyIndex": 10,
+    "Target": {
+      "Group": "cache",
+      "Job": "example",
+      "Namespace": "default"
+    }
+  }
+]
+```
+
+## Read Scaling Policy <sup>Beta</sup>
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/search.mdx b/content/nomad/v0.11.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..cac8ff3821
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/search.mdx
@@ -0,0 +1,120 @@
+---
+layout: api
+page_title: Search - HTTP API
+sidebar_title: Search
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+or volumes. When using Nomad Enterprise, the allowed contexts include quotas
+and namespaces. Additionally, a prefix can be searched for within every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v0.11.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..455a050100
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,178 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+sidebar_title: Sentinel Policies
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](https://learn.hashicorp.com/nomad/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/status.mdx b/content/nomad/v0.11.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..f56e328ba7
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/status.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: Status - HTTP API
+sidebar_title: Status
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/system.mdx b/content/nomad/v0.11.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..6a8d5e4e6b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+sidebar_title: System
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/ui.mdx b/content/nomad/v0.11.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..98b21f70a3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/ui.mdx
@@ -0,0 +1,264 @@
+---
+layout: api
+page_title: UI
+sidebar_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+Starting in v0.7, the Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/`
+will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter. Namespaces are an enterprise feature.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the node the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the node the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Nodes List
+
+This page lists all nodes in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path        | Produces    |
+| ----------- | ----------- |
+| `/ui/nodes` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of client nodes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible client nodes. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the client nodes list that should be visible. This
+  is specified as a query string parameter.
+
+## Node Detail
+
+This page shows the details of a node, including the node name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                 | Produces    |
+| -------------------- | ----------- |
+| `/ui/nodes/:node_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
diff --git a/content/nomad/v0.11.x/content/api-docs/validate.mdx b/content/nomad/v0.11.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..92f04330b5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/validate.mdx
@@ -0,0 +1,65 @@
+---
+layout: api
+page_title: Validate - HTTP API
+sidebar_title: Validate
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to a server. In the event a server can't be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v0.11.x/content/api-docs/volumes.mdx b/content/nomad/v0.11.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..b4d8a85573
--- /dev/null
+++ b/content/nomad/v0.11.x/content/api-docs/volumes.mdx
@@ -0,0 +1,328 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+sidebar_title: Volumes
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` endpoints are used to query for and interact with volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "volume-id1",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "volume-id1",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:3.2"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. It is an error
+to register an existing volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that described the volume's
+parameters.
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "volume-id1",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "PluginID": "plugin-id1"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Delete Volume
+
+This endpoint deregisters an external volume with Nomad. It is an
+error to deregister a volume that is in use.
+
+| Method  | Path                        | Produces           |
+| ------- | --------------------------- | ------------------ |
+| `DELTE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..836c720e09
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+sidebar_title: bootstrap
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Bootstrap the initial token:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/index.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..9f83e24f31
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+sidebar_title: acl
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /docs/commands/acl/bootstrap
+[policyapply]: /docs/commands/acl/policy-apply
+[policydelete]: /docs/commands/acl/policy-delete
+[policyinfo]: /docs/commands/acl/policy-info
+[policylist]: /docs/commands/acl/policy-list
+[tokencreate]: /docs/commands/acl/token-create
+[tokenupdate]: /docs/commands/acl/token-update
+[tokendelete]: /docs/commands/acl/token-delete
+[tokeninfo]: /docs/commands/acl/token-info
+[tokenself]: /docs/commands/acl/token-self
+[secure-guide]: https://learn.hashicorp.com/nomad/acls/fundamentals
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..3f7c8d7cc3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+sidebar_title: policy apply
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..95d88b9710
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+sidebar_title: policy delete
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..d2bf26165f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+sidebar_title: policy info
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..417e797b73
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+sidebar_title: policy list
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..678b9756b8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+sidebar_title: token create
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..6bd65565aa
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+sidebar_title: token delete
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..6adcb7d5b8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+sidebar_title: token info
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..1599643556
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+sidebar_title: token list
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..a3544208d1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+sidebar_title: token self
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v0.11.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..6f5004ff68
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+sidebar_title: token update
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/agent-info.mdx b/content/nomad/v0.11.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..ddbbe6ac48
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+sidebar_title: agent-info
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/agent.mdx b/content/nomad/v0.11.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..6970eb8213
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/agent.mdx
@@ -0,0 +1,225 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+sidebar_title: agent
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-network-speed=<MBits>`: Equivalent to the Client
+  [network_speed] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /docs/configuration/consul#address
+[alloc_dir]: /docs/configuration/client/#alloc_dir
+[auth]: /docs/configuration/consul#auth
+[auto_advertise]: /docs/configuration/consul#auto_advertise
+[bind_addr]: /docs/configuration/#bind_addr
+[bootstrap_expect]: /docs/configuration/server/#bootstrap_expect
+[ca_file]: /docs/configuration/consul#ca_file
+[cert_file]: /docs/configuration/consul#cert_file
+[checks_use_advertise]: /docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /docs/configuration/consul#client_auto_join
+[client_http_check_name]: /docs/configuration/consul#client_http_check_name
+[client_service_name]: /docs/configuration/consul#client_service_name
+[configuration]: /docs/configuration
+[data_dir]: /docs/configuration#data_dir
+[datacenter]: /docs/configuration/#datacenter
+[enabled]: /docs/configuration/acl#enabled
+[encryption overview]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption
+[key_file]: /docs/configuration/consul#key_file
+[log_json]: /docs/configuration#log_json
+[log_level]: /docs/configuration#log_level
+[meta]: /docs/configuration/client/#meta
+[name]: /docs/configuration/#name
+[network_interface]: /docs/configuration/client/#network_interface
+[network_speed]: /docs/configuration/client/#network_speed
+[node_class]: /docs/configuration/client/#node_class
+[nomad agent]: /docs/install/production/nomad-agent
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: /docs/configuration/#region
+[rejoin_after_leave]: /docs/configuration/server/#rejoin_after_leave
+[replication_token]: /docs/configuration/acl#replication_token
+[retry_interval]: /docs/configuration/server/#retry_interval
+[retry_max]: /docs/configuration/server/#retry_max
+[server_auto_join]: /docs/configuration/consul#server_auto_join
+[server_http_check_name]: /docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /docs/configuration/consul#server_serf_check_name
+[server_service_name]: /docs/configuration/consul#server_service_name
+[servers]: /docs/configuration/client/#servers
+[ssl]: /docs/configuration/consul#ssl
+[state_dir]: /docs/configuration/client/#state_dir
+[token]: /docs/configuration/consul#token
+[verify_ssl]: /docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..6b84e32bc5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+sidebar_title: exec
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..25a404924d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+sidebar_title: fs
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an allocation directory on a Nomad
+client. The following functionalities are available - `cat`, `tail`, `ls` and
+`stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a path.
+The path is relative to the root of the allocation directory. The path is
+optional and it defaults to `/` of the allocation directory.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/index.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..d6f2c4e73e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+sidebar_title: alloc
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..62ffbb746f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+sidebar_title: logs
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..3f35090410
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+sidebar_title: restart
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be restarted.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..061c14b955
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+sidebar_title: signal
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/status.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..27a103b800
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+sidebar_title: status
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v0.11.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..646eb53285
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+sidebar_title: stop
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..b1eaa2c9d2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+sidebar_title: fail
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/index.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..d5eb0bb24c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+sidebar_title: deployment
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /docs/commands/deployment/list 'List all deployments'
+[pause]: /docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/list.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..9930700c5b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+sidebar_title: list
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..569d233b87
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+sidebar_title: pause
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..1ee5ed8e9e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+sidebar_title: promote
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..582137151d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+sidebar_title: resume
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/deployment/status.mdx b/content/nomad/v0.11.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..c854211c18
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+sidebar_title: status
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       2        2       2        0
+web         2        2       2        0
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       0        0
+web         N/A       2        0         2       2        0
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/eval-status.mdx b/content/nomad/v0.11.x/content/docs/commands/eval-status.mdx
new file mode 100644
index 0000000000..eb7aaeaf76
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/eval-status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+sidebar_title: eval status
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output the evaluation in its JSON format.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/index.mdx b/content/nomad/v0.11.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..657686fa0f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Commands (CLI)
+sidebar_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash or zsh shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ nomad_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/deployments.mdx b/content/nomad/v0.11.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..d130f56966
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+sidebar_title: deployments
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v0.11.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..926f9eb444
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+sidebar_title: dispatch
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16KiB**.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+[eval status]: /docs/commands/eval-status
+[parameterized job]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/eval.mdx b/content/nomad/v0.11.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..a4b77976aa
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+sidebar_title: eval
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/history.mdx b/content/nomad/v0.11.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..e6ba1c89e5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+sidebar_title: history
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/index.mdx b/content/nomad/v0.11.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..8026c0fb74
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: job'
+sidebar_title: job
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /docs/commands/job/promote "Promote a job's canaries"
+[revert]: /docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/init.mdx b/content/nomad/v0.11.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..217f29cb45
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+sidebar_title: init
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[drivers]: /docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/inspect.mdx b/content/nomad/v0.11.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..9b0e151c4e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+sidebar_title: inspect
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /api-docs/jobs
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v0.11.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..86b1fce684
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+sidebar_title: periodic force
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /docs/commands/eval-status
+[force the evaluation]: /api-docs/jobs#force-new-periodic-instance
+[periodic job]: /docs/job-specification/periodic
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/plan.mdx b/content/nomad/v0.11.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..46fdf0209f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,205 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+sidebar_title: plan
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:3.2"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+[job specification]: /docs/job-specification
+[hcl job specification]: /docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /docs/commands/job/run#check-index
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/promote.mdx b/content/nomad/v0.11.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..dbdde983a6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+sidebar_title: promote
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/revert.mdx b/content/nomad/v0.11.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..aafe64a0ca
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+sidebar_title: revert
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  \$CONSUL_HTTP_TOKEN environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  \$VAULT_TOKEN environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:3.2"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /docs/commands/job/history
+[eval status]: /docs/commands/eval-status
+[consul service identity]: /docs/configuration/consul#allow_unauthenticated
+[vault policy]: /docs/configuration/vault#allow_unauthenticated
+[run]: /docs/commands/job/run
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/run.mdx b/content/nomad/v0.11.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..4e039c3b5d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+sidebar_title: run
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions and placement information for the provided job. The monitor will
+exit after scheduling has finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+If the job has specified the region, the -region flag and `\$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the \$CONSUL_HTTP_TOKEN
+  environment variable and that found in the job.
+
+- `-vault-token`: If set, the passed Vault token is stored in the job before
+  sending to the Nomad servers. This allows passing the Vault token without
+  storing it in the job file. This overrides the token found in the \$VAULT_TOKEN
+  environment variable and that found in the job.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement:
+
+```shell-session
+$ nomad job run job1.nomad
+==> Monitoring evaluation "52dee78a"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+    Allocation "5e0b39f0" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "52dee78a" finished with status "complete"
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> Monitoring evaluation "5ef16dff"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5ef16dff" finished with status "complete"
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+4947e728
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> Monitoring evaluation "2ae0e6a5"
+    Evaluation triggered by job "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /docs/commands/job/plan
+[eval status]: /docs/commands/eval-status
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/status.mdx b/content/nomad/v0.11.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..490d2a4e6d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+sidebar_title: status
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/stop.mdx b/content/nomad/v0.11.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..f31abde940
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+sidebar_title: stop
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.11.x/content/docs/commands/job/validate.mdx b/content/nomad/v0.11.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..0339a00d14
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+sidebar_title: validate
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+## Examples
+
+Validate a job with invalid syntax:
+
+```shell-session
+$ nomad job validate example.nomad
+Job validation errors:
+1 error(s) occurred:
+
+* group "cache" -> task "redis" -> config: 1 error(s) occurred:
+
+* field "image" is required
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v0.11.x/content/docs/commands/monitor.mdx b/content/nomad/v0.11.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..3fa44e165d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+sidebar_title: monitor
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..e3417386b8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+sidebar_title: apply
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <namespace>
+```
+
+The `namespace apply` command requires the name of the namespace to be created
+or updated.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+## Examples
+
+Create a namespace with a quota
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..d25485ecdf
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+sidebar_title: delete
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/index.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..7a8b064ae6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+sidebar_title: namespace
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /docs/commands/namespace/list 'List available namespaces'
+[status]: /docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..b859061848
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+sidebar_title: inspect
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/list.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..dc03ce9a0b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+sidebar_title: list
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/namespace/status.mdx b/content/nomad/v0.11.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..3ee41fbefe
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+sidebar_title: status
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name        = default
+Description = Default shared namespace
+Quota       = shared-default-quota
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/node/config.mdx b/content/nomad/v0.11.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..7477749b67
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+sidebar_title: config
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /docs/configuration/client#servers
diff --git a/content/nomad/v0.11.x/content/docs/commands/node/drain.mdx b/content/nomad/v0.11.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..1b8e3cf434
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+sidebar_title: drain
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] stanza until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first disable
+[scheduling eligibility][eligibility] on all nodes that will be drained. For
+example if you are decommissioning an entire class of nodes, first run `node eligibility -disable` on all of their node IDs, and then run `node drain -enable`. This will ensure allocations drained from the first node are not
+placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are force removed from the
+  node. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Force remove allocations off the node immediately.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node
+  without being force stopped after a certain deadline.
+
+- `-ignore-system`: Ignore system allows the drain to complete without stopping
+  system job allocations. By default system jobs are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /docs/commands/node/eligibility
+[migrate]: /docs/job-specification/migrate
+[node status]: /docs/commands/node/status
+[workload migration guide]: https://learn.hashicorp.com/nomad/operating-nomad/node-draining
diff --git a/content/nomad/v0.11.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v0.11.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..d82dbbbd6e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+sidebar_title: eligibility
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+elegibility disabled are ineligibile for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained!
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /docs/commands/node/drain
diff --git a/content/nomad/v0.11.x/content/docs/commands/node/index.mdx b/content/nomad/v0.11.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..d5563d4cb8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: node'
+sidebar_title: node
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /docs/commands/node/config 'View or modify client configuration details'
+[drain]: /docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v0.11.x/content/docs/commands/node/status.mdx b/content/nomad/v0.11.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..15d38804b8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,364 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+sidebar_title: status
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-get-config.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-get-config.mdx
new file mode 100644
index 0000000000..5464e951f3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-get-config.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+sidebar_title: autopilot get-config
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: https://learn.hashicorp.com/nomad/operating-nomad/autopilot
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-set-config.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-set-config.mdx
new file mode 100644
index 0000000000..d9f87562a2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/autopilot-set-config.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+sidebar_title: autopilot set-config
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /docs/configuration/server#upgrade_version
+[autopilot guide]: https://learn.hashicorp.com/nomad/operating-nomad/autopilot
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/index.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..b64b2d6113
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+sidebar_title: operator
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+[get-config]: /docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /api-docs/operator 'Operator API documentation'
+[outage recovery guide]: https://learn.hashicorp.com/nomad/operating-nomad/outage
+[remove]: /docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..3baf7bfd6a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+sidebar_title: keygen
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+YgZOXLMhC7TtZqeghMT8+w==
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..1ac7282ba5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+sidebar_title: keyring
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/raft-list-peers.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/raft-list-peers.mdx
new file mode 100644
index 0000000000..2a41bd2e4e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/raft-list-peers.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+sidebar_title: raft list-peers
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The Raft list-peers command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /api-docs/operator
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.11.x/content/docs/commands/operator/raft-remove-peer.mdx b/content/nomad/v0.11.x/content/docs/commands/operator/raft-remove-peer.mdx
new file mode 100644
index 0000000000..9f0081e9c5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/operator/raft-remove-peer.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+sidebar_title: raft remove-peer
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /docs/commands/server/members 'Nomad server members command'
+[operator]: /api-docs/operator 'Nomad Operator API'
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.11.x/content/docs/commands/plugin/index.mdx b/content/nomad/v0.11.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..fee7edf365
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+sidebar_title: plugin
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[status]: /docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v0.11.x/content/docs/commands/plugin/status.mdx b/content/nomad/v0.11.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..df1cdf012c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+sidebar_title: status
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/apply.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..0f113d3f80
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+sidebar_title: apply
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <name> <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/delete.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..ccfbf5679e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+sidebar_title: delete
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/index.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..264e91c1b1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+sidebar_title: quota
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /docs/commands/quota/apply
+[quotadelete]: /docs/commands/quota/delete
+[quotainit]: /docs/commands/quota/init
+[quotainspect]: /docs/commands/quota/inspect
+[quotalist]: /docs/commands/quota/list
+[quotastatus]: /docs/commands/quota/status
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/init.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..c0d1168e39
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+sidebar_title: init
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..d34c100efd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+sidebar_title: inspect
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/list.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..4ec7223d1f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+sidebar_title: list
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/quota/status.mdx b/content/nomad/v0.11.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..0ca2350018
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+sidebar_title: status
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v0.11.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..8f78ad97b0
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+sidebar_title: apply
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v0.11.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..a57a18c59a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+sidebar_title: delete
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v0.11.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..d1db0d0fea
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+sidebar_title: sentinel
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /docs/commands/sentinel/delete
+[list]: /docs/commands/sentinel/list
+[read]: /docs/commands/sentinel/read
+[apply]: /docs/commands/sentinel/apply
diff --git a/content/nomad/v0.11.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v0.11.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..b80836ea00
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+sidebar_title: list
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v0.11.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..e49c1a38af
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+sidebar_title: read
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v0.11.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..61a437888b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+sidebar_title: force-leave
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/server/index.mdx b/content/nomad/v0.11.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..a56135439b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: server'
+sidebar_title: server
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /docs/commands/server/join 'Join server nodes together'
+[members]: /docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v0.11.x/content/docs/commands/server/join.mdx b/content/nomad/v0.11.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..3f4eba7a53
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+sidebar_title: join
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/server/members.mdx b/content/nomad/v0.11.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..f45bcc513a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+sidebar_title: members
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Server Members Options
+
+- `-detailed`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in the
+  standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name          Addr      Port  Status  Proto  Build     DC   Region
+node1.global  10.0.0.8  4648  alive   2      0.1.0dev  dc1  global
+node2.global  10.0.0.9  4648  alive   2      0.1.0dev  dc1  global
+```
+
+Detailed view:
+
+```shell-session
+$ nomad server members -detailed
+Name   Addr      Port  Tags
+node1  10.0.0.8  4648  bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+node2  10.0.0.9  4648  bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/status.mdx b/content/nomad/v0.11.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..a57901788d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/status.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'Commands: status'
+sidebar_title: status
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/system/gc.mdx b/content/nomad/v0.11.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..aff2c38074
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+sidebar_title: gc
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/system/index.mdx b/content/nomad/v0.11.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..afdf094f9b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: system'
+sidebar_title: system
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v0.11.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v0.11.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..f8d1cc0719
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+sidebar_title: reconcile summaries
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/ui.mdx b/content/nomad/v0.11.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..903032844d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/ui.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+sidebar_title: ui
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/version.mdx b/content/nomad/v0.11.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b3d756dd9e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/version.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: version'
+sidebar_title: version
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v0.11.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v0.11.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..06dc19c3ad
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+sidebar_title: deregister
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be deregistered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v0.11.x/content/docs/commands/volume/index.mdx b/content/nomad/v0.11.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..0f3db82667
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+sidebar_title: volume
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume register`][register] - Register a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume status`][status] - Display status information about a volume
+
+[register]: /docs/commands/volume/register 'Register a volume'
+[deregister]: /docs/commands/volume/deregister 'Deregister a volume'
+[status]: /docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v0.11.x/content/docs/commands/volume/register.mdx b/content/nomad/v0.11.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..815f80135c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+sidebar_title: register
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be registered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying
+the path to a file containing a valid [volume
+specification][volume_specification]. This file will be read and the
+job will be submitted to Nomad for scheduling. If the supplied path is
+"-", the job file is read from STDIN. Otherwise it is read from the
+file at the supplied path.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+The file may be provided as either HCL or JSON. An example HCL configuration:
+
+```hcl
+id = "ebs_prod_db1"
+name = "database"
+type = "csi"
+external_id = "vol-23452345"
+plugin_id = "ebs-prod"
+access_mode = "single-node-writer"
+attachment_mode = "file-system"
+mount_options {
+   fs_type = "ext4"
+   mount_flags = ["ro"]
+}
+secrets {
+   example_secret = "xyzzy"
+}
+parameters {
+    skuname = "Premium_LRS"
+}
+context {
+    endpoint = "http://192.168.1.101:9425"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This will
+  be how [`volume`][csi_volume] stanzas in a jobspec refer to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only
+  `"csi"` is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume
+  from the storage provider. For example, the volume ID of an AWS EBS
+  volume or Digital Ocean volume.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI
+  plugin][csi_plugin] that manages this volume.
+
+- `access_mode` `(string: <required>)` - Defines whether a volume
+  should be available concurrently. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only
+  single-node modes. Consult the documentation of the storage provider
+  and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will
+  be used by the volume. Most storage providers will support
+  `"file-system"`, to mount pre-formatted file system volumes. Some
+  storage providers will support `"block-device"`, which will require
+  the job be configured with appropriate mount options.
+
+- `mount_options` <code>([mount_options][]:nil)</code> - Options for
+  mounting `block-device`volumes without a pre-formatted file system.
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `"ro,noatime"`)
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings used as credentials for publishing and
+  unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  configure the volume. The details of these parameters are specific
+  to each storage provider, so please see the specific plugin
+  documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  validate the volume. The details of these parameters are specific to
+  each storage provider, so please see the specific plugin
+  documentation for more information.
+
+[volume_specification]: #volume-specification
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volumes]: /docs/job-specification/volume
diff --git a/content/nomad/v0.11.x/content/docs/commands/volume/status.mdx b/content/nomad/v0.11.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..8788167d05
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+sidebar_title: status
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify
+  times are shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.11.x/content/docs/configuration/acl.mdx b/content/nomad/v0.11.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..bb4e193416
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: acl Stanza - Agent Configuration
+sidebar_title: acl
+description: >-
+  The "acl" stanza configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Stanza
+
+<Placement groups={['acl']} />
+
+The `acl` stanza configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  client configuration options depend on this value.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region.
+
+[secure-guide]: https://learn.hashicorp.com/nomad/acls/fundamentals
diff --git a/content/nomad/v0.11.x/content/docs/configuration/audit.mdx b/content/nomad/v0.11.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..3423d3aeec
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,297 @@
+---
+layout: docs
+page_title: audit Stanza - Agent Configuration
+sidebar_title: audit
+description: >-
+  The "audit" stanza configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Stanza
+
+<Placement groups={['audit']} />
+
+The `audit` stanza configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit stanza (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enable = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to 
+`"enforced"` meaning that all requests must successfully be written to the sink 
+in order for HTTP requests to successfully complete.
+
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-stanza): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-stanza)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Stanza
+
+The `sink` stanza is used to make audit logging sinks for events to be 
+sent to. Currently only a single sink is supported.
+
+The key of the stanza corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the 
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  hault request execution if the audit log event fails to be written to it's sink.
+  `"best-effort"` will not hault request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be 
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use it's configured 
+  [`data_dir`](/docs/configuration#data_dir) for a combined path of 
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit log
+  file archives to keep. If 0 no files are ever deleted.
+
+### `filter` Stanza
+
+The `filter` stanza is used to create filters to filter __out__ matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit 
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern](https://github.com/ryanuber/go-glob/blob/master/README.md#example) matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to 
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages 
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this 
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`.
+The first entry is for the `OperationReceived` stage. The second entry is for
+the `OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": [
+        "anonymous"
+      ],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
diff --git a/content/nomad/v0.11.x/content/docs/configuration/autopilot.mdx b/content/nomad/v0.11.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..f986c69d70
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: autopilot Stanza - Agent Configuration
+sidebar_title: autopilot
+description: >-
+  The "autopilot" stanza configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Stanza
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` stanza configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers = true
+    last_contact_threshold = "200ms"
+    max_trailing_logs = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v0.11.x/content/docs/configuration/client.mdx b/content/nomad/v0.11.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..aa81a1aef6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/client.mdx
@@ -0,0 +1,436 @@
+---
+layout: docs
+page_title: client Stanza - Agent Configuration
+sidebar_title: client
+description: |-
+  The "client" stanza configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Stanza
+
+<Placement groups={['client']} />
+
+The `client` stanza configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## Plugin Options
+
+Nomad 0.9 now supports pluggable drivers. Operators should use the new
+[plugin][plugin-stanza] syntax to modify driver configuration. To find the
+plugin options supported by each individual Nomad driver, please see the
+[drivers documentation](/docs/drivers). The pre-0.9 `client.options`
+stanza will be supported in 0.9 for backward compatibility (except for the `lxc`
+driver) but will be removed in a future release.
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks.
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `network_speed` `(int: 0)` - Specifies an override for the network link speed.
+  This value, if set, overrides any detected or defaulted link speed. Most
+  clients can determine their speed automatically, and thus in most cases this
+  should be left unset.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, 20% of the node's CPU could be reserved to target a CPU utilization
+  of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `bridge_network name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.66.0/23")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/docs/job-specification/template) stanzas.
+
+- `host_volume` <code>([host_volume](#host_volume-stanza): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/docs/drivers/exec#chroot) for
+the full list.
+
+### `options` Parameters
+
+~> Note: client configuration options for drivers will soon be deprecated. See
+the [plugin stanza][plugin-stanza] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/docs/drivers).
+
+- `"driver.whitelist"` `(string: "")` - Specifies a comma-separated list of
+  whitelisted drivers . If specified, drivers not in the whitelist will be
+  disabled. If the whitelist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.whitelist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.blacklist"` `(string: "")` - Specifies a comma-separated list of
+  blacklisted drivers . If specified, drivers in the blacklist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.blacklist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.blacklist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.blacklist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.blacklist"` `(string: see below)` - Specifies a comma-separated
+  blacklist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.blacklist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.blacklist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.whitelist"` `(string: "")` - Specifies a comma-separated list of
+  whitelisted fingerprinters. If specified, any fingerprinters not in the
+  whitelist will be disabled. If the whitelist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.whitelist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.blacklist"` `(string: "")` - Specifies a comma-separated list of
+  blacklisted fingerprinters. If specified, any fingerprinters in the blacklist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.blacklist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separated the two inclusive ends.
+
+### `template` Parameters
+
+- `function_blacklist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the task directory.
+
+### `host_volume` Stanza
+
+The `host_volume` stanza is used to make volumes available to jobs.
+
+The key of the stanza corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  network_speed = 500
+  node_class    = "prod"
+
+  meta {
+    "owner" = "ops"
+    "cached_binaries" = "redis,apache,nginx,jq,cypress,nodejs"
+    "rack" = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[server-join]: /docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
diff --git a/content/nomad/v0.11.x/content/docs/configuration/consul.mdx b/content/nomad/v0.11.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..29a7825807
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: consul Stanza - Agent Configuration
+sidebar_title: consul
+description: |-
+  The "consul" stanza configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Stanza
+
+<Placement groups={['consul']} />
+
+The `consul` stanza configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` stanza is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the bind address.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: https://learn.hashicorp.com/nomad/operating-nomad/clustering 'Automatic Bootstrapping'
diff --git a/content/nomad/v0.11.x/content/docs/configuration/index.mdx b/content/nomad/v0.11.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..91d0e2b211
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/index.mdx
@@ -0,0 +1,344 @@
+---
+layout: docs
+page_title: Agent Configuration
+sidebar_title: Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+  network_speed = 10
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this stanza take
+  precedence over the default [bind_addr](#bind_addr).
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most common
+    bind address to change.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this stanza take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the address
+  private IP found is advertised. You may advertise an alternate port as well.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address advertised to Nomad client nodes. This allows
+    advertising a different RPC address than is used by Nomad Servers such that
+    the clients can connect to the Nomad servers if they are behind a NAT.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+  ~> **WARNING**: This directory **must not** be set to a directory that is
+  [included in the chroot](/docs/drivers/exec#chroot) if you use the
+  [`exec`](/docs/drivers/exec) driver.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins.
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to "nomad-{timestamp}.log".
+  This setting can be combined with `log_rotate_bytes` and `log_rotate_duration`
+  for a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older log
+  file archives to keep. If 0 no files are ever deleted.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin stanza may be repeated, once for each plugin being
+  configured. The key of the stanza is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
diff --git a/content/nomad/v0.11.x/content/docs/configuration/plugin.mdx b/content/nomad/v0.11.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..6f583cd7dc
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: plugin Stanza - Agent Configuration
+sidebar_title: plugin
+description: The "plugin" stanza is used to configure a Nomad plugin.
+---
+
+# `plugin` Stanza
+
+<Placement groups={['plugin']} />
+
+The `plugin` stanza is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v0.11.x/content/docs/configuration/sentinel.mdx b/content/nomad/v0.11.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..f83d147321
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: sentinel Stanza - Agent Configuration
+sidebar_title: sentinel
+description: >-
+  The "sentinel" stanza configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Stanza
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` stanza configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v0.11.x/content/docs/configuration/server.mdx b/content/nomad/v0.11.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..aafc402751
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/server.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: server Stanza - Agent Configuration
+sidebar_title: server
+description: |-
+  The "server" stanza configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Stanza
+
+<Placement groups={['server']} />
+
+The `server` stanza configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use -
+  for server-specific data, including the replicated log. By default, this is -
+  the top-level [data_dir](/docs/configuration#data_dir)
+  suffixed with "server", like `"/opt/nomad/server"`. This must be an absolute
+  path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 16 bytes that are
+  base64-encoded. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the
+  [encryption documentation][encryption] for more details on this option
+  and its impact on the cluster.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `protocol_version` `(int: 1)` - Specifies the Nomad protocol version to use
+  when communicating with other Nomad servers. This value is typically not
+  required as the agent internally knows the latest version, but may be useful
+  in some upgrade scenarios.
+
+- `raft_protocol` `(int: 2)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  stanza][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join stanza][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration stanza. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/nomad/operating-nomad/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` stanza
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+   the [update scheduler configuration][update-scheduler-config] API. This
+   option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm = "spread"
+
+    preemption_config {
+      batch_scheduler_enabled   = true
+      system_scheduler_enabled  = true
+      service_scheduler_enabled = true
+    }
+  }
+}
+```
+
+[encryption]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /api-docs/operator#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /docs/faq#bootstrapping
\ No newline at end of file
diff --git a/content/nomad/v0.11.x/content/docs/configuration/server_join.mdx b/content/nomad/v0.11.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..62f0a85829
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,230 @@
+---
+layout: docs
+page_title: server_join Stanza - Agent Configuration
+sidebar_title: server_join
+description: >-
+  The "server_join" stanza specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Stanza
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join']
+  ]}
+/>
+
+The `server_join` stanza specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join][#cloud_auto_join] for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+````
+
+```json
+{
+"retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+````
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v0.11.x/content/docs/configuration/telemetry.mdx b/content/nomad/v0.11.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..0db8756c55
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: telemetry Stanza - Agent Configuration
+sidebar_title: telemetry
+description: |-
+  The "telemetry" stanza configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Stanza
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` stanza configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` stanza. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` stanza,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `backwards_compatible_metrics` `(bool: false)` - Specifies if Nomad should
+  publish metrics that are backwards compatible with versions below 0.7, as
+  post version 0.7, Nomad emits tagged metrics. All new metrics will
+  only be added to tagged metrics. Note that this option is used to transition
+  monitoring to tagged metrics and will eventually be deprecated.
+
+- `disable_tagged_metrics` `(bool: false)` - Specifies if Nomad should not emit
+  tagged metrics and only emit metrics compatible with versions below Nomad
+  0.7. Note that this option is used to transition monitoring to tagged
+  metrics and will eventually be deprecated.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/dd-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v0.11.x/content/docs/configuration/tls.mdx b/content/nomad/v0.11.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..f04a0f0578
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: tls Stanza - Agent Configuration
+sidebar_title: tls
+description: |-
+  The "tls" stanza configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers, clients, and between.
+---
+
+# `tls` Stanza
+
+<Placement groups={['tls']} />
+
+The `tls` stanza configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` stanza. To understand how to setup the certificates themselves, please see
+the [Encryption Overview Guide](https://learn.hashicorp.com/nomad/transport-security/gossip-encryption).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` stanzas. Remember that the
+`tls` stanza is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v0.11.x/content/docs/configuration/vault.mdx b/content/nomad/v0.11.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..11ccd6832a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: vault Stanza - Agent Configuration
+sidebar_title: vault
+description: |-
+  The "vault" stanza configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Stanza
+
+<Placement groups={['vault']} />
+
+The `vault` stanza configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used
+  for Vault communication. If this is set then you need to also set
+  `tls_key_file`.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive child tokens for jobs
+  requesting tokens.
+  Visit the [Vault Integration Guide](/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v0.11.x/content/docs/devices/community.mdx b/content/nomad/v0.11.x/content/docs/devices/community.mdx
new file mode 100644
index 0000000000..f6e894e1f8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/devices/community.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Device Plugins.
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+## Authoring Device Plugins
+
+Nomad has a plugin system for defining device drivers. External device plugins
+will have the same user experience as built in drivers. For details on
+authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
diff --git a/content/nomad/v0.11.x/content/docs/devices/index.mdx b/content/nomad/v0.11.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..bb403ea6d3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/devices/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in Nomad.
+Devices are physical hardware that exists on a node such as a GPU or an FPGA. By
+having extensible device plugins, Nomad has the flexibility to support a broad
+set of devices and allows the community to build additional device plugins as
+needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
+
+For details on authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
diff --git a/content/nomad/v0.11.x/content/docs/devices/nvidia.mdx b/content/nomad/v0.11.x/content/docs/devices/nvidia.mdx
new file mode 100644
index 0000000000..222c9ae535
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/devices/nvidia.mdx
@@ -0,0 +1,330 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+sidebar_title: Nvidia
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nvidia-gpu`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad. The Nvidia
+plugin is built into Nomad and does not need to be downloaded separately.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nvidia-gpu` the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+
+### Docker Driver Requirements
+
+In order to use the Nvidia driver plugin with the Docker driver, please follow
+the installation instructions for
+[`nvidia-docker`](<https://github.com/NVIDIA/nvidia-docker/wiki/Installation-(version-1.0)>).
+
+## Plugin Configuration
+
+```hcl
+plugin "nvidia-gpu" {
+  ignored_gpu_ids = ["GPU-fef8089b", "GPU-ac81e44d"]
+  fingerprint_period = "1m"
+}
+```
+
+The `nvidia-gpu` device plugin supports the following configuration in the agent
+config:
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Restrictions
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver] and plans to
+bring support to the built-in [`exec`][exec-driver] and [`java`][java-driver]
+drivers. Support for [`lxc`][lxc-driver] should be possible by installing the
+[Nvidia hook](https://github.com/lxc/lxc/blob/master/hooks/nvidia) but is not
+tested or documented by Nomad.
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m43s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2674/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Allocations
+No allocations placed
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m59s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2673/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+
+Allocations
+No allocations placed
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:9.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+ID                  = d250baed
+Eval ID             = 21bd7584
+Name                = gpu-test.smi[0]
+Node ID             = 4d46e59f
+Job ID              = example
+Job Version         = 0
+Client Status       = complete
+Client Description  = All tasks have completed
+Desired Status      = run
+Desired Description = <none>
+Created             = 7s ago
+Modified            = 2s ago
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[docker-driver]: /docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /docs/drivers/external/lxc 'Nomad lxc Driver'
diff --git a/content/nomad/v0.11.x/content/docs/drivers/docker.mdx b/content/nomad/v0.11.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..f261ba45c1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,987 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+sidebar_title: Docker
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:3.2"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for the container
+  to use.
+
+- `dns_options` - (Optional) A list of DNS options for the container to use.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container to use
+  (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or greater.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl {
+      net.core.somaxconn = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `port_map` - (Optional) A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace when user namespace remapping is enabled on the
+  docker daemon.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the allocation
+  directory can be disabled on clients by setting the `docker.volumes.enabled`
+  option set to false. This will limit volumes to directories that exist inside
+  the allocation directory. We recommend using [`mounts`](#mounts) if you wish
+  to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mounts` - (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-or-volumes)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options {
+          no_copy = false
+          labels {
+            foo = "bar"
+          }
+          driver_config {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-add`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured whitelist.
+  The whitelist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME",
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-drop`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured whitelist.
+  The whitelist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD",
+    ]
+  }
+  ```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/docs/job-specification/service#IPv6 Docker containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in \$PATH,
+"docker-credential-ecr" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script "docker-credential-ecr" in
+\$PATH
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network). Here is a recap:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  resources {
+    network {
+      port "http" {}
+      port "https" {}
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose all of the ports it allocates to your
+container.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+port "http" {}
+```
+
+If Nomad allocates port `23332` to your task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+`port_map` option in your job specification. It looks like this:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "redis"
+
+    port_map {
+      redis = 6379
+    }
+  }
+
+  resources {
+    network {
+      mbits = 20
+      port "redis" {}
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your task, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work!
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `vagrant`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a vagrant
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver on
+a Nomad client, you can modify them with the [plugin stanza][plugin-stanza] syntax. Below is an example of a configuration (many of the values are the default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "docker-credential-aws"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["CHOWN", "NET_RAW"]
+
+    # allow_caps can also be set to "ALL"
+    # allow_caps = ["ALL"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the DOCKER_HOST environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to unix:///var/run/docker.sock on Unix platforms and
+  npipe:////./pipe/docker_engine for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `allow_caps`<a id="plugin_caps"></a> - A list of allowed Linux capabilities.
+  Defaults to
+  "CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP,SETPCAP,
+  NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE", which is the list of
+  capabilities allowed by docker by default, as defined here. Allows the
+  operator to control which capabilities can be obtained by tasks using cap_add
+  and cap_drop options. Supports the value "ALL" as a shortcut for whitelisting
+  all capabilities.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` stanza:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    -like script on \$PATH to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+- `tls` stanza:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `gc` stanza:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a tasks is received that uses the same image within
+    the delay, the image will be reused.
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+  - `dangling_containers` stanza for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults
+  to "gcr.io/google_containers/pause-amd64:3.0".
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.whitelist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for whitelisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config stanza.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Adriver%2Fdocker+label%3Aplatform-windows
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.11.x/content/docs/drivers/exec.mdx b/content/nomad/v0.11.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..8aaa71979b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+sidebar_title: Isolated Fork/Exec
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `no_pivot_root` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the
+resources of a process and as such the Nomad agent must be run as root.
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/firecracker-task-driver.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..00f1a0f7df
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+sidebar_title: Firecracker driver
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' on nomad's allocation directory.
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' on nomad's allocation directory.
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/iis.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/iis.mdx
new file mode 100644
index 0000000000..2c83a6940b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/iis.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+sidebar_title: Windows IIS
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+    - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+    - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+    - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+    - `hostname` (string)      - (Optional) IIS hostname for a binding.
+    - `ipaddress` (string)     - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+    - `resource_port` (string) - (Optional) Use a label from an established network stanza port. It is recommended to use this approach over using `port`.
+    - `port` (number)          - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+    - `type` (string)          - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+    - `cert_hash` (string)     - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/index.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/index.mdx
new file mode 100644
index 0000000000..96c9b10494
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/index.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [LXC][lxc]
+- [Rkt][rkt]
+- [Podman][podman]
+- [Singularity][singularity]
+- [Jail task driver][jail-task-driver]
+- [Pot][pot]
+- [Firecracker][firecracker-task-driver]
+- [Systemd-Nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[lxc]: /docs/drivers/external/lxc
+[rkt]: /docs/drivers/external/rkt
+[plugin_guide]: /docs/internals/plugins
+[singularity]: /docs/drivers/external/singularity
+[jail-task-driver]: /docs/drivers/external/jail-task-driver
+[podman]: /docs/drivers/external/podman
+[pot]: /docs/drivers/external/pot
+[firecracker-task-driver]: /docs/drivers/external/firecracker-task-driver
+[nspawn-driver]: /docs/drivers/external/nspawn
+[nomad-driver-iis]: /docs/drivers/external/iis
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/jail-task-driver.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/jail-task-driver.mdx
new file mode 100644
index 0000000000..a880fca820
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+sidebar_title: Jailtask driver
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to nomad's allocation directory.
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /docs/configuration#plugin_dir
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/lxc.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/lxc.mdx
new file mode 100644
index 0000000000..e8d7cb4912
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/lxc.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+sidebar_title: LXC
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind-mount host paths to container paths. Mounting host paths outside of the allocation directory can be disabled on clients by setting the [`volumes_enabled`](#volumes_enabled) option set to false. This will limit volumes to directories that exist inside the allocation directory.
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` stanza:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: https://learn.hashicorp.com/nomad/using-plugins/lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/nspawn.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/nspawn.mdx
new file mode 100644
index 0000000000..78eb7458cf
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/nspawn.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: 'Drivers: Systemd-Nspawn'
+sidebar_title: Systemd-Nspawn
+description: The Nspawn task driver is used to run application containers using Systemd-Nspawn.
+---
+
+# Nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using Systemd-Nspawn for running application
+containers. You can download the external Systemd-Nspawn driver [here][nspawn-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+* [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+* [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+* [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+* [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+* [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+* `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+* [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+* `image` - Path to the image to be used in the container. This can either be a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D)
+  or the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device. Can be specified as a relative path from the configured Nomad
+  plugin directory. **This option is mandatory**.
+* [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+* [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+* [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+* [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+* [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+* [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+* [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+* `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+* `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker
+  driver][docker_driver].
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface of
+  your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+
+## Networking
+
+Currently the `nspawn` driver only supports host networking.
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+* 64-bit Linux host
+* The `linux_amd64` Nomad binary
+* The Nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+* `systemd-nspawn` to be installed
+* Nomad running with root privileges
+
+## Plugin Options
+
+* `enabled` - The `nspawn` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+  }
+}
+```
+
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+* `driver.nspawn` - Set to `true` if Systemd-Nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+* `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[docker_driver]: /docs/drivers/docker#using-the-port-map
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/podman.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/podman.mdx
new file mode 100644
index 0000000000..1965a4ffb6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/podman.mdx
@@ -0,0 +1,244 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+sidebar_title: Podman
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/pascomnet/nomad-driver-podman
+
+The podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+See the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+- Linux host with [`podman`][podman] installed.
+- [`nomad-driver-podman`][releases] binary in Nomad's [`plugin_dir`][plugin_dir].
+
+You need a varlink enabled podman binary and a system socket activation unit, see https://podman.io/blogs/2019/01/16/podman-varlink.html.
+
+Since the Nomad agent, nomad-driver-podman plugin binary, and podman will
+reside on the same host, skip the ssh aspects of the podman varlink
+documentation above.
+
+## Task Configuration
+
+Due to Podman's similarity to Docker, the example job created by [`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis:3.2"
+
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+
+        network {
+          mbits = 10
+          port  "db"  {}
+        }
+      }
+    }
+  }
+}
+```
+
+- `image` - The image to run.
+
+```hcl
+config {
+  image = "docker://redis"
+}
+```
+
+- `command` - (Optional) The command to run when starting the container.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  _command_ is specified, the arguments are passed directly to the container.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths.
+
+```hcl
+config {
+  volumes = [
+    "/some/host/data:/container/data"
+  ]
+}
+```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for tmpfs mount
+  points. See `podman run --tmpfs` options for details.
+
+```hcl
+config {
+  tmpfs = [
+    "/var"
+  ]
+}
+```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using count) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - Run an init inside the container that forwards signals and reaps processes.
+
+```hcl
+config {
+  init = true
+}
+```
+
+- `init_path` - Path to the container-init binary.
+
+```hcl
+config {
+  init = true
+  init_path = "/usr/libexec/podman/catatonit"
+}
+```
+
+- `user` - Run the command as a specific user/uid within the container. See
+  [task configuration][task].
+
+- `memory_reservation` - Memory soft limit (unit = b (bytes), k (kilobytes), m
+  (megabytes), or g (gigabytes))
+
+After setting memory reservation, when the system detects memory contention or
+low memory, containers are forced to restrict their consumption to their
+reservation. So you should always set the value below --memory, otherwise the
+hard limit will take precedence. By default, memory reservation will be the
+same as memory limit.
+
+```hcl
+config {
+  memory_reservation = "100m"
+}
+```
+
+- `memory_swap` - A limit value equal to memory plus swap. The swap limit
+  should always be larger than the [memory value][memory-value].
+
+Unit can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you
+don't specify a unit, b is used. Set LIMIT to -1 to enable unlimited swap.
+
+```hcl
+config {
+  memory_swap = "180m"
+}
+```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between 0 and 100.
+
+```hcl
+config {
+  memory_swappiness = 60
+}
+```
+
+## Networking
+
+Podman supports forwarding and exposing ports like Docker. See [Docker Driver
+configuration][docker-ports] for details.
+
+## Plugin Options
+
+The podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+  }
+}
+```
+
+- `gc` stanza:
+
+  - `container` - Defaults to `true`. This option can be used to disable
+    Nomad from removing a container when the task exits.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously managed containers
+  will be reused instead of disposed and recreated.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    recover_stopped = false
+  }
+}
+```
+
+[docker-ports]: /docs/drivers/docker#forwarding-and-exposing-ports
+[homepage]: https://github.com/pascomnet/nomad-driver-podman
+[memory-value]: /docs/job-specification/resources#memory
+[nomad-init]: /docs/commands/job/init
+[plugin_dir]: /docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[releases]: https://github.com/pascomnet/nomad-driver-podman/releases
+[task]: /docs/job-specification/task#user
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/pot.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/pot.mdx
new file mode 100644
index 0000000000..d2cff5da53
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/pot.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+sidebar_title: Pot
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/rkt.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/rkt.mdx
new file mode 100644
index 0000000000..38da283a6a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/rkt.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+sidebar_title: 'Rkt <sup>Deprecated</sup> '
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:3.2"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			mbits = 10
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.11.x/content/docs/drivers/external/singularity.mdx b/content/nomad/v0.11.x/content/docs/drivers/external/singularity.mdx
new file mode 100644
index 0000000000..e160e4d5e3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/external/singularity.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+sidebar_title: Singularity
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. /tmp and \$HOME) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and \$HOME (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v0.11.x/content/docs/drivers/index.mdx b/content/nomad/v0.11.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..ad191d9413
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/index.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Task Drivers
+sidebar_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin stanza][plugin] documentation for examples on how to
+use the `plugin` stanza in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/internals/plugins
+[acl_guide]: https://learn.hashicorp.com/nomad?track=acls#operations-and-development
diff --git a/content/nomad/v0.11.x/content/docs/drivers/java.mdx b/content/nomad/v0.11.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..06f9ea5efd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/java.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+sidebar_title: Java
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
diff --git a/content/nomad/v0.11.x/content/docs/drivers/qemu.mdx b/content/nomad/v0.11.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..60cd98cf5b
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Drivers: Qemu'
+sidebar_title: Qemu
+description: The Qemu task driver is used to run virtual machines using Qemu/KVM.
+---
+
+# Qemu Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. Qemu can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. (Note that
+  [prior to qemu 2.10.1](https://github.com/qemu/qemu/commit/ad9579aaa16d5b385922d49edac2c96c79bcfb6),
+  the monitor socket path is limited to 108 characters. Graceful shutdown will
+  be disabled if qemu is < 2.10.1 and the generated monitor path exceeds this
+  length. You may encounter this issue if you set long
+  [data_dir](/docs/configuration#data_dir)
+  or
+  [alloc_dir](/docs/configuration/client#alloc_dir)
+  paths.) This feature is currently not supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to qemu as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Client Requirements
+
+The `qemu` driver requires Qemu to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if Qemu is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Resource Isolation
+
+Nomad uses Qemu to provide full software virtualization for virtual machine
+workloads. Nomad can use Qemu KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the Qemu
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
diff --git a/content/nomad/v0.11.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v0.11.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..581b3b3ecc
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+sidebar_title: Raw Fork/Exec
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin stanza:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.11.x/content/docs/enterprise/index.mdx b/content/nomad/v0.11.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..ae0120db93
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+sidebar_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Namespaces, Resource Quotas, Sentinel Policies, and Advanced
+  Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities to Nomad. Nomad Enterprise is available as a base Platform package with an optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and its features in detail.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as enhances performance and availability through Advanced Autopilot features such as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new servers and then simply wait for the upgrade to complete. As the new servers join the cluster, server logic checks the version of each Nomad server node. If the version is higher than the version on the current set of voters, it will avoid promoting the new servers to voters until the number of new servers matches the number of existing servers at the previous version. Once the numbers match, Nomad will begin to promote new servers and demote old ones.
+
+See the [Autopilot - Upgrade Migrations](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#upgrade-migrations) documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a Nomad cluster. Non-voting servers will receive the replication stream but will not take part in quorum (required by the leader before log entries can be committed). Adding explicit non-voters will scale reads and scheduling without impacting write latency.
+
+See the [Autopilot - Read Scalability](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#server-read-and-scheduling-scaling) documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot standby server on a per availability zone basis. For example, in an environment with three availability zones an operator can run one voter and one non-voter in each availability zone, for a total of six servers. If an availability zone is completely lost, only one voter will be lost, so the cluster remains available. If a voter is lost in an availability zone, Nomad will promote the non-voter to a voter automatically, putting the hot standby server into service quickly.
+
+See the [Autopilot - Redundancy Zones](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#redundancy-zones) documentation for a thorough overview.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an organization to securely operate Nomad at scale across multiple teams through features such as Audit Logging, Namespaces, Resource Quotas, Sentinel Policies, and Preemption.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to fulfill compliance requirements. This Enterprise feature provides administrators with a complete set of records for all user-issued actions in Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies, ensure enforcement of their security policies, and diagnose cluster behavior by viewing preceding user operations.  Designed as an HTTP API based audit logging system, each audit event is captured with relevant request and response information in a JSON format that is easily digestibile and familiar to operators.
+
+See the [Audit Logging Documentation](/docs/configuration/audit) for a  thorough overview.
+
+### Namespaces
+
+Namespaces enable multiple teams to safely use a shared multi-region Nomad environment and reduce cluster fleet size. In Nomad Enterprise, a shared cluster can be partitioned into multiple namespaces which allow jobs and their associated objects to be isolated from each other and other users of the cluster.
+
+Namespaces enhance the usability of a shared cluster by isolating teams from the jobs of others, by providing fine grain access control to jobs when coupled with ACLs, and by preventing bad actors from negatively impacting the whole cluster.
+
+See the [Namespaces Guide](https://learn.hashicorp.com/nomad/governance-and-policy/namespaces) for a thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams or projects to reduce waste and align budgets. In Nomad Enterprise, operators can define quota specifications and apply them to namespaces. When a quota is attached to a namespace, the jobs within the namespace may not consume more resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas Guide](https://learn.hashicorp.com/nomad/governance-and-policy/quotas) for a thorough overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained policy enforcement. Sentinel policies build on top of the ACL system and allow operators to define policies such as disallowing jobs to be submitted to production on Fridays or only allowing users to run jobs that use pre-authorized Docker images. Sentinel policies are defined as code, giving operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide](https://learn.hashicorp.com/nomad/governance-and-policy/sentinel) for a thorough overview.
+
+### Preemption
+
+When a Nomad cluster is at capacity for a given set of placement constraints, any allocations that result from a newly scheduled service or batch job will remain in the pending state until sufficient resources become available - regardless of the defined priority.
+
+Preemption enables Nomad's scheduler to automatically evict lower priority allocations of service and batch jobs so that allocations from higher priority jobs can be placed. This behavior ensures that critical workloads can run when resources are limited or when partial outages require workloads to be rescheduled across a smaller set of client nodes.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or request a trial
+of Nomad Enterprise.
diff --git a/content/nomad/v0.11.x/content/docs/faq.mdx b/content/nomad/v0.11.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..f8e13bef28
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/faq.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+sidebar_title: FAQ
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/docs/internals/consensus) and
+a [gossip protocol](/docs/internals/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+[consul_dc]: https://www.consul.io/docs/agent/options.html#_datacenter
+[consul_fed]: https://www.consul.io/docs/guides/datacenters.html
+[nomad_region]: /docs/configuration#datacenter
+[`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v0.11.x/content/docs/index.mdx b/content/nomad/v0.11.x/content/docs/index.mdx
new file mode 100644
index 0000000000..5d17bf4c3f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/index.mdx
@@ -0,0 +1,14 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation! This documentation is more of a reference
+  guide for all available features and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation! This documentation is a reference guide for
+all available features and options of Nomad. If you are just getting
+started with Nomad, please start with the
+[introduction and getting started guide](/intro) instead.
diff --git a/content/nomad/v0.11.x/content/docs/install/index.mdx b/content/nomad/v0.11.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..8be776939e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/index.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: Installing Nomad
+sidebar_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Installing Nomad is simple. There are two approaches to installing Nomad:
+
+1. Using a [precompiled binary](#precompiled-binaries)
+1. Installing [from source](#from-source)
+
+Downloading a precompiled binary is easiest, and we provide downloads over
+TLS along with SHA-256 sums to verify the binary.
+
+## Precompiled Binaries ((#precompiled-binaries))
+
+To install the precompiled binary,
+[download](/downloads) the appropriate package for your system.
+Nomad is currently packaged as a zip file. We do not have any near term
+plans to provide system packages.
+
+Once the zip is downloaded, unzip it into any directory. The
+`nomad` (or `nomad.exe` for Windows) binary inside is all that is
+necessary to run Nomad. Any additional files, if any, are not
+required to run Nomad.
+
+Copy the binary to anywhere on your system. If you intend to access it
+from the command-line, make sure to place it somewhere on your `PATH`.
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+## Verifying the Installation
+
+To verify Nomad is properly installed, run `nomad -v` on your system. You should
+see help output. If you are executing it from the command line, make sure it is
+on your `PATH` or you may get an error about `nomad` not being found.
+
+```shell-session
+$ nomad -v
+
+```
diff --git a/content/nomad/v0.11.x/content/docs/install/production/deployment-guide.mdx b/content/nomad/v0.11.x/content/docs/install/production/deployment-guide.mdx
new file mode 100644
index 0000000000..01aa1df979
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/production/deployment-guide.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: Nomad Deployment Guide
+sidebar_title: Reference Install Guide
+description: |-
+  This deployment guide covers the steps required to install and
+  configure a single HashiCorp Nomad cluster as defined in the
+  Nomad Reference Architecture
+ea_version: 0.9
+---
+
+# Nomad Reference Install Guide
+
+This deployment guide covers the steps required to install and configure a single HashiCorp Nomad cluster as defined in the [Nomad Reference Architecture](/docs/install/production/reference-architecture).
+
+These instructions are for installing and configuring Nomad on Linux hosts running the systemd system and service manager.
+
+## Reference Material
+
+This deployment guide is designed to work in combination with the [Nomad Reference Architecture](/docs/install/production/reference-architecture) and [Consul Deployment Guide](https://www.consul.io/docs/guides/deployment-guide.html). Although it is not a strict requirement to follow the Nomad Reference Architecture, please ensure you are familiar with the overall architecture design. For example, installing Nomad server agents on multiple physical or virtual (with correct anti-affinity) hosts for high-availability.
+
+## Overview
+
+To provide a highly-available single cluster architecture, we recommend Nomad server agents be deployed to more than one host, as shown in the [Nomad Reference Architecture](/docs/install/production/reference-architecture).
+
+![Reference diagram](/img/nomad_reference_diagram.png)
+
+These setup steps should be completed on all Nomad hosts:
+
+- [Download Nomad](#download-nomad)
+- [Install Nomad](#install-nomad)
+- [Configure systemd](#configure-systemd)
+- [Configure Nomad](#configure-nomad)
+- [Start Nomad](#start-nomad)
+
+## Download Nomad
+
+Precompiled Nomad binaries are available for download at [https://releases.hashicorp.com/nomad/](https://releases.hashicorp.com/nomad/) and Nomad Enterprise binaries are available for download by following the instructions made available to HashiCorp Enterprise customers.
+
+```text
+export NOMAD_VERSION="0.9.0"
+curl --silent --remote-name https://releases.hashicorp.com/nomad/${NOMAD_VERSION}/nomad_${NOMAD_VERSION}_linux_amd64.zip
+```
+
+You may perform checksum verification of the zip packages using the SHA256SUMS and SHA256SUMS.sig files available for the specific release version. HashiCorp provides [a guide on checksum verification](https://www.hashicorp.com/security) for precompiled binaries.
+
+## Install Nomad
+
+Unzip the downloaded package and move the `nomad` binary to `/usr/local/bin/`. Check `nomad` is available on the system path.
+
+```text
+unzip nomad_${NOMAD_VERSION}_linux_amd64.zip
+sudo chown root:root nomad
+sudo mv nomad /usr/local/bin/
+nomad version
+```
+
+The `nomad` command features opt-in autocompletion for flags, subcommands, and arguments (where supported). Enable autocompletion.
+
+```text
+nomad -autocomplete-install
+complete -C /usr/local/bin/nomad nomad
+```
+
+Create a data directory for Nomad.
+
+```text
+sudo mkdir --parents /opt/nomad
+```
+
+## Configure systemd
+
+Systemd uses [documented sane defaults](https://www.freedesktop.org/software/systemd/man/systemd.directives.html) so only non-default values must be set in the configuration file.
+
+Create a Nomad service file at `/etc/systemd/system/nomad.service`.
+
+```text
+sudo touch /etc/systemd/system/nomad.service
+```
+
+Add this configuration to the Nomad service file:
+
+```text
+[Unit]
+Description=Nomad
+Documentation=https://nomadproject.io/docs/
+Wants=network-online.target
+After=network-online.target
+
+[Service]
+ExecReload=/bin/kill -HUP $MAINPID
+ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d
+KillMode=process
+KillSignal=SIGINT
+LimitNOFILE=infinity
+LimitNPROC=infinity
+Restart=on-failure
+RestartSec=2
+StartLimitBurst=3
+StartLimitIntervalSec=10
+TasksMax=infinity
+
+[Install]
+WantedBy=multi-user.target
+```
+
+The following parameters are set for the `[Unit]` stanza:
+
+- [`Description`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Description=) - Free-form string describing the nomad service
+- [`Documentation`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Documentation=) - Link to the nomad documentation
+- [`Wants`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Wants=) - Configure a dependency on the network service
+- [`After`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#After=) - Configure an ordering dependency on the network service being started before the nomad service
+
+The following parameters are set for the `[Service]` stanza:
+
+- [`ExecReload`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecReload=) - Send Nomad a `SIGHUP` signal to trigger a configuration reload
+- [`ExecStart`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=) - Start Nomad with the `agent` argument and path to a directory of configuration files
+- [`KillMode`](https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillMode=) - Treat nomad as a single process
+- [`LimitNOFILE`, `LimitNPROC`](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%20Properties) - Disable limits for file descriptors and processes
+- [`RestartSec`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#RestartSec=) - Restart nomad after 2 seconds of it being considered 'failed'
+- [`Restart`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Restart=) - Restart nomad unless it returned a clean exit code
+- [`StartLimitBurst`, `StartLimitIntervalSec`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#StartLimitIntervalSec=interval) - Configure unit start rate limiting
+- [`TasksMax`](https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#TasksMax=N) - Disable task limits (only available in systemd >= 226)
+
+The following parameters are set for the `[Install]` stanza:
+
+- [`WantedBy`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#WantedBy=) - Creates a weak dependency on nomad being started by the multi-user run level
+
+## Configure Nomad
+
+Nomad uses [documented sane defaults](/docs/configuration) so only non-default values must be set in the configuration file. Configuration can be read from multiple files and is loaded in lexical order. See the [full description](/docs/configuration) for more information about configuration loading and merge semantics.
+
+Some configuration settings are common to both server and client Nomad agents, while some configuration settings must only exist on one or the other. Follow the [common configuration](#common-configuration) guidance on all hosts and then the specific guidance depending on whether you are configuring a Nomad [server](#server-configuration) or [client](#client-configuration).
+
+- [Common Nomad configuration](#common-configuration)
+- [Configure a Nomad server](#server-configuration)
+- [Configure a Nomad client](#client-configuration)
+
+### Common configuration
+
+Create a configuration file at `/etc/nomad.d/nomad.hcl`:
+
+```text
+sudo mkdir --parents /etc/nomad.d
+sudo chmod 700 /etc/nomad.d
+sudo touch /etc/nomad.d/nomad.hcl
+```
+
+Add this configuration to the `nomad.hcl` configuration file:
+
+~> **Note:** Replace the `datacenter` parameter value with the identifier you will use for the datacenter this Nomad cluster is deployed in.
+
+```hcl
+datacenter = "dc1"
+data_dir = "/opt/nomad"
+```
+
+- [`datacenter`](/docs/configuration#datacenter) - The datacenter in which the agent is running.
+- [`data_dir`](/docs/configuration#data_dir) - The data directory for the agent to store state.
+
+### Server configuration
+
+Create a configuration file at `/etc/nomad.d/server.hcl`:
+
+```text
+sudo touch /etc/nomad.d/server.hcl
+```
+
+Add this configuration to the `server.hcl` configuration file:
+
+~> **NOTE** Replace the `bootstrap_expect` value with the number of Nomad servers you will use; three or five [is recommended](/docs/internals/consensus#deployment-table).
+
+```hcl
+server {
+  enabled = true
+  bootstrap_expect = 3
+}
+```
+
+- [`server`](/docs/configuration/server#enabled) - Specifies if this agent should run in server mode. All other server options depend on this value being set.
+- [`bootstrap_expect`](/docs/configuration/server#bootstrap_expect) - The number of expected servers in the cluster. Either this value should not be provided or the value must agree with other servers in the cluster.
+
+### Client configuration
+
+Create a configuration file at `/etc/nomad.d/client.hcl`:
+
+```text
+sudo touch /etc/nomad.d/client.hcl
+```
+
+Add this configuration to the `client.hcl` configuration file:
+
+```hcl
+client {
+  enabled = true
+}
+```
+
+- [`client`](/docs/configuration/client#enabled) - Specifies if this agent should run in client mode. All other client options depend on this value being set.
+
+~> **NOTE** The [`options`](/docs/configuration/client#options-parameters) parameter can be used to enable or disable specific configurations on Nomad clients, unique to your use case requirements.
+
+### ACL configuration
+
+The [Access Control](https://learn.hashicorp.com/nomad?track=acls#operations-and-development) guide provides instructions on configuring and enabling ACLs.
+
+### TLS configuration
+
+Securing Nomad's cluster communication with mutual TLS (mTLS) is recommended for production deployments and can even ease operations by preventing mistakes and misconfigurations. Nomad clients and servers should not be publicly accessible without mTLS enabled.
+
+The [Securing Nomad with TLS](https://learn.hashicorp.com/nomad/transport-security/enable-tls) guide provides instructions on configuring and enabling TLS.
+
+## Start Nomad
+
+Enable and start Nomad using the systemctl command responsible for controlling systemd managed services. Check the status of the nomad service using systemctl.
+
+```text
+sudo systemctl enable nomad
+sudo systemctl start nomad
+sudo systemctl status nomad
+```
+
+## Next Steps
+
+- Read [Outage Recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage) to learn
+  the steps required to recover from a Nomad cluster outage.
+- Read [Autopilot](https://learn.hashicorp.com/nomad/operating-nomad/autopilot) to learn about
+  features in Nomad 0.8 to allow for automatic operator-friendly
+  management of Nomad servers.
diff --git a/content/nomad/v0.11.x/content/docs/install/production/index.mdx b/content/nomad/v0.11.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..3912ba9d6a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/production/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+sidebar_title: Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+This section covers how to install Nomad for production.
+
+There are multiple steps to cover for a successful Nomad deployment:
+
+## Installing Nomad
+
+This page lists the two primary methods to installing Nomad and how to verify a successful installation.
+
+Please refer to [Installing Nomad](/docs/install) sub-section.
+
+## Hardware Requirements
+
+This page details the recommended machine resources (instances), port requirements, and network topology for Nomad.
+
+Please refer to [Hardware Requirements](/docs/install/production/requirements) sub-section.
+
+## Setting Nodes with Nomad Agent
+These pages explain the Nomad agent process and how to set the server and client nodes in the cluster.
+
+Please refer to [Set Server & Client Nodes](/docs/install/production/nomad-agent) and [Nomad Agent documentation](/docs/commands/agent) pages.
+
+## Reference Architecture
+
+This document provides recommended practices and a reference architecture for HashiCorp Nomad production deployments. This reference architecture conveys a general architecture that should be adapted to accommodate the specific needs of each implementation.
+
+Please refer to [Reference Architecture](/docs/install/production/reference-architecture) sub-section.
+
+## Install Guide Based on Reference Architecture
+This guide provides an end-to-end walkthrough of the steps required to install a single production-ready Nomad cluster as defined in the Reference Architecture section.
+
+Please refer to [Reference Install Guide](/docs/install/production/deployment-guide) sub-section.
diff --git a/content/nomad/v0.11.x/content/docs/install/production/nomad-agent.mdx b/content/nomad/v0.11.x/content/docs/install/production/nomad-agent.mdx
new file mode 100644
index 0000000000..b97f40ce44
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/production/nomad-agent.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Nomad Agent
+sidebar_title: Set Server & Client Nodes
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Setting Nodes with Nomad Agent
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/docs/internals/consensus) and [gossip protocol](/docs/internals/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default,
+any signal to an agent (interrupt, terminate, kill) will cause the agent
+to forcefully stop. Graceful termination can be configured by either
+setting `leave_on_interrupt` or `leave_on_terminate` to respond to the
+respective signals.
+
+When gracefully exiting, clients will update their status to terminal on
+the servers so that tasks can be migrated to healthy agents. Servers
+will notify their intention to leave the cluster which allows them to
+leave the [consensus](/docs/internals/consensus) peer set.
+
+It is especially important that a server node be allowed to leave gracefully
+so that there will be a minimal impact on availability as the server leaves
+the consensus peer set. If a server does not gracefully leave, and will not
+return into service, the [`server force-leave` command](/docs/commands/server/force-leave)
+should be used to eject it from the consensus peer set.
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/docs/internals/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers should be run with the lowest possible permissions. Nomad clients
+must be run as root due to the OS isolation mechanisms that require root
+privileges. In all cases, it is recommended you create a `nomad` user with the
+minimal set of required privileges.
diff --git a/content/nomad/v0.11.x/content/docs/install/production/reference-architecture.mdx b/content/nomad/v0.11.x/content/docs/install/production/reference-architecture.mdx
new file mode 100644
index 0000000000..ea7d1f7f37
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/production/reference-architecture.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: Nomad Reference Architecture
+sidebar_title: Reference Architecture
+description: |-
+  This document provides recommended practices and a reference
+  architecture for HashiCorp Nomad production deployments.
+ea_version: 0.9
+---
+
+# Nomad Reference Architecture
+
+This document provides recommended practices and a reference architecture for HashiCorp Nomad production deployments. This reference architecture conveys a general architecture that should be adapted to accommodate the specific needs of each implementation.
+
+The following topics are addressed:
+
+- [Reference Architecture](#ra)
+- [Deployment Topology within a Single Region](#one-region)
+- [Deployment Topology across Multiple Regions](#multi-region)
+- [Network Connectivity Details](#net)
+- [Deployment System Requirements](#system-reqs)
+- [High Availability](#high-availability)
+- [Failure Scenarios](#failure-scenarios)
+
+This document describes deploying a Nomad cluster in combination with, or with access to, a [Consul cluster](/docs/integrations/consul-integration). We recommend the use of Consul with Nomad to provide automatic clustering, service discovery, health checking and dynamic configuration.
+
+## Reference Architecture ((#ra))
+
+A Nomad cluster typically comprises three or five servers (but no more than seven) and a number of client agents. Nomad differs slightly from Consul in that it divides infrastructure into regions which are served by one Nomad server cluster, but can manage multiple datacenters or availability zones. For example, a _US Region_ can include datacenters _us-east-1_ and _us-west-2_.
+
+In a Nomad multi-region architecture, communication happens via [WAN gossip](/docs/internals/gossip). Additionally, Nomad can integrate easily with Consul to provide features such as automatic clustering, service discovery, and dynamic configurations. Thus we recommend you use Consul in your Nomad deployment to simplify the deployment.
+
+In cloud environments, a single cluster may be deployed across multiple availability zones. For example, in AWS each Nomad server can be deployed to an associated EC2 instance, and those EC2 instances distributed across multiple AZs. Similarly, Nomad server clusters can be deployed to multiple cloud regions to allow for region level HA scenarios.
+
+For more information on Nomad server cluster design, see the [cluster requirements documentation](/docs/install/production/requirements).
+
+The design shared in this document is the recommended architecture for production environments, as it provides flexibility and resilience. Nomad utilizes an existing Consul server cluster; however, the deployment design of the Consul server cluster is outside the scope of this document.
+
+Nomad to Consul connectivity is over HTTP and should be secured with TLS as well as a Consul token to provide encryption of all traffic. This is done using Nomad's [Automatic Clustering with Consul](https://learn.hashicorp.com/nomad/operating-nomad/clustering).
+
+### Deployment Topology within a Single Region ((#one-region))
+
+A single Nomad cluster is recommended for applications deployed in the same region.
+
+Each cluster is expected to have either three or five servers. This strikes a balance between availability in the case of failure and performance, as [Raft](https://raft.github.io/) consensus gets progressively slower as more servers are added.
+
+The time taken by a new server to join an existing large cluster may increase as the size of the cluster increases.
+
+#### Reference Diagram
+
+![Reference diagram](/img/nomad_reference_diagram.png)
+
+### Deployment Topology across Multiple Regions ((#multi-region))
+
+By deploying Nomad server clusters in multiple regions, the user is able to interact with the Nomad servers by targeting any region from any Nomad server even if that server resides in a separate region. However, most data is not replicated between regions as they are fully independent clusters. The exceptions are [ACL tokens and policies][acl], as well as [Sentinel policies in Nomad Enterprise][sentinel], which _are_ replicated between regions.
+
+Nomad server clusters in different datacenters can be federated using WAN links. The server clusters can be joined to communicate over the WAN on port `4648`. This same port is used for single datacenter deployments over LAN as well.
+
+Additional documentation is available to learn more about [Nomad server federation](https://learn.hashicorp.com/nomad/operating-nomad/federation).
+
+## Network Connectivity Details ((#net))
+
+![Nomad network diagram](/img/nomad_network_arch.png)
+
+Nomad servers are expected to be able to communicate in high bandwidth, low latency network environments and have below 10 millisecond latencies between cluster members. Nomad servers can be spread across cloud regions or datacenters if they satisfy these latency requirements.
+
+Nomad client clusters require the ability to receive traffic as noted above in the Network Connectivity Details; however, clients can be separated into any type of infrastructure (multi-cloud, on-prem, virtual, bare metal, etc.) as long as they are reachable and can receive job requests from the Nomad servers.
+
+Additional documentation is available to learn more about [Nomad networking](/docs/install/production/requirements#network-topology).
+
+## Deployment System Requirements ((#system-reqs))
+
+Nomad server agents are responsible for maintaining the cluster state, responding to RPC queries (read operations), and for processing all write operations. Given that Nomad server agents do most of the heavy lifting, server sizing is critical for the overall performance efficiency and health of the Nomad cluster.
+
+### Nomad Servers
+
+| Size  | CPU      | Memory       | Disk   | Typical Cloud Instance Types              |
+| ----- | -------- | ------------ | ------ | ----------------------------------------- |
+| Small | 2 core   | 8-16 GB RAM  | 50 GB  | **AWS:** m5.large, m5.xlarge              |
+|       |          |              |        | **Azure:** Standard_D2_v3, Standard_D4_v3 |
+|       |          |              |        | **GCE:** n1-standard-8, n1-standard-16    |
+| Large | 4-8 core | 32-64 GB RAM | 100 GB | **AWS:** m5.2xlarge, m5.2xlarge           |
+|       |          |              |        | **Azure:** Standard_D4_v3, Standard_D8_v3 |
+|       |          |              |        | **GCE:** n1-standard-16, n1-standard-32   |
+
+#### Hardware Sizing Considerations
+
+- The small size would be appropriate for most initial production
+  deployments, or for development/testing environments.
+
+- The large size is for production environments where there is a
+  consistently high workload.
+
+~> **NOTE** For large workloads, ensure that the disks support a high number of IOPS to keep up with the rapid Raft log update rate.
+
+Nomad clients can be setup with specialized workloads as well. For example, if workloads require GPU processing, a Nomad datacenter can be created to serve those GPU specific jobs and joined to a Nomad server cluster. For more information on specialized workloads, see the documentation on [job constraints](/docs/job-specification/constraint) to target specific client nodes.
+
+## High Availability
+
+A Nomad server cluster is the highly-available unit of deployment within a single datacenter. A recommended approach is to deploy a three or five node Nomad server cluster. With this configuration, during a Nomad server outage, failover is handled immediately without human intervention.
+
+When setting up high availability across regions, multiple Nomad server clusters are deployed and connected via WAN gossip. Nomad clusters in regions are fully independent from each other and do not share jobs, clients, or state. Data residing in a single region-specific cluster is not replicated to other clusters in other regions.
+
+## Failure Scenarios
+
+Typical distribution in a cloud environment is to spread Nomad server nodes into separate Availability Zones (AZs) within a high bandwidth, low latency network, such as an AWS Region. The diagram below shows Nomad servers deployed in multiple AZs promoting a single voting member per AZ and providing both AZ-level and node-level failure protection.
+
+![Nomad fault tolerance](/img/nomad_fault_tolerance.png)
+
+Additional documentation is available to learn more about [cluster sizing and failure tolerances](/docs/internals/consensus#deployment-table) as well as [outage recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage).
+
+### Availability Zone Failure
+
+In the event of a single AZ failure, only a single Nomad server will be affected which would not impact job scheduling as long as there is still a Raft quorum (i.e. 2 available servers in a 3 server cluster, 3 available servers in a 5 server cluster, etc.). There are two scenarios that could occur should an AZ fail in a multiple AZ setup: leader loss or follower loss.
+
+#### Leader Server Loss
+
+If the AZ containing the Nomad leader server fails, the remaining quorum members would elect a new leader. The new leader then begins to accept new log entries and replicates these entries to the remaining followers.
+
+#### Follower Server Loss
+
+If the AZ containing a Nomad follower server fails, there is no immediate impact to the Nomad leader server or cluster operations. However, there still must be a Raft quorum in order to properly manage a future failure of the Nomad leader server.
+
+### Region Failure
+
+In the event of a region-level failure (which would contain an entire Nomad server cluster), clients will still be able to submit jobs to another region that is properly federated. However, there will likely be data loss as Nomad server clusters do not replicate their data to other region clusters. See [Multi-region Federation](https://learn.hashicorp.com/nomad/operating-nomad/federation) for more setup information.
+
+## Next Steps
+
+- Read [Deployment Guide](/docs/install/production/deployment-guide) to learn
+  the steps required to install and configure a single HashiCorp Nomad cluster.
+
+[acl]: https://learn.hashicorp.com/nomad?track=acls#operations-and-development
+[sentinel]: https://learn.hashicorp.com/nomad/governance-and-policy/sentinel
diff --git a/content/nomad/v0.11.x/content/docs/install/production/requirements.mdx b/content/nomad/v0.11.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..da6eeb7ac5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: Hardware Requirements
+sidebar_title: Hardware Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Hardware Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
diff --git a/content/nomad/v0.11.x/content/docs/install/quickstart/index.mdx b/content/nomad/v0.11.x/content/docs/install/quickstart/index.mdx
new file mode 100644
index 0000000000..26fcf81356
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/quickstart/index.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+sidebar_title: Quickstart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to our [Production
+Installation](/docs/install/production) guide here.
+
+## Local
+
+Install Nomad on your local machine.
+
+- [Installing the Pre-compiled Binary][installing-binary]
+- [Installing Nomad with Vagrant][vagrant-environment]
+
+## Cloud
+
+Install Nomad on the public cloud.
+
+- AWS
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+- Azure
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+## Katacoda
+
+Experiment with Nomad in your browser via KataCoda's interactive learning platform.
+
+- [Introduction to Nomad](https://www.katacoda.com/hashicorp/scenarios/nomad-introduction)
+- [Nomad Playground](https://katacoda.com/hashicorp/scenarios/playground)
+
+[installing-binary]: /docs/install/#precompiled-binaries
+[vagrant-environment]: https://learn.hashicorp.com/nomad/getting-started/install#vagrant-setup-optional
diff --git a/content/nomad/v0.11.x/content/docs/install/windows-service.mdx b/content/nomad/v0.11.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..dba9e7bd9e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+sidebar_title: Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /downloads
+[logging]: /docs/configuration#log_file
diff --git a/content/nomad/v0.11.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v0.11.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..83e77d2d48
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,343 @@
+---
+layout: docs
+page_title: Consul Connect
+sidebar_title: Consul Connect
+description: >-
+  Learn how to use Nomad with Consul Connect to enable secure service to service
+  communication
+---
+
+# Consul Connect
+
+~> **Note:** This guide requires Nomad 0.10.0 or later and Consul 1.6.0 or
+later.
+
+~> **Note:** Nomad's Connect integration requires Linux network namespaces.
+Nomad Connect will not run on Windows or macOS.
+
+[Consul Connect](https://www.consul.io/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of Connect at all.
+
+# Nomad with Consul Connect Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. In order to support Consul Connect, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into Connect integration. When Connect is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul Connect integration to
+implement [service segmentation](https://www.consul.io/segmentation.html) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in Connect continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul Connect integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/nomad/consul-integration/nomad-connect-acl)
+guide.
+
+# Nomad Consul Connect Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+Connect integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+**Note**: Nomad's Connect integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use Connect on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Connect.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul Connect sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+$ curl -L -o cni-plugins.tgz https://github.com/containernetworking/plugins/releases/download/v0.8.6/cni-plugins-linux-amd64-v0.8.6.tgz
+$ sudo mkdir -p /opt/cni/bin
+$ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Connect-enabled Services
+
+Once Nomad and Consul are running, submit the following Connect-enabled services
+to Nomad by copying the HCL into a file named `connect.nomad` and running:
+`nomad run connect.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v1"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v1"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul Connect, it does not define
+any ports in its network. The service stanza enables Connect:
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service stanza is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace.
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul Connect:
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` stanza defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul Connect Native is not yet supported ([#6083][gh6083]).
+- Only the Docker, `exec`, `raw_exec`, and `java` drivers support network namespaces
+  and Connect.
+- Changes to the `connect` stanza may not properly trigger a job update
+  ([#6459][gh6459]). Changing a `meta` variable is the suggested workaround as
+  this will always cause an update to occur.
+- Consul Connect and network namespaces are only supported on Linux.
+
+[count-dashboard]: /img/count-dashboard.png
+[gh6083]: https://github.com/hashicorp/nomad/issues/6083
+[gh6120]: https://github.com/hashicorp/nomad/issues/6120
+[gh6701]: https://github.com/hashicorp/nomad/issues/6701
+[gh6459]: https://github.com/hashicorp/nomad/issues/6459
diff --git a/content/nomad/v0.11.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v0.11.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..fa95528fa5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Consul Integration
+sidebar_title: Consul
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](https://learn.hashicorp.com/nomad/operating-nomad/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` stanza](/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template stanza and how it leverages Consul Template,
+please see the [`template` job specification documentation](/docs/job-specification/template).
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/integrations/index.mdx b/content/nomad/v0.11.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..5778b3e468
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/integrations/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+sidebar_title: Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v0.11.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v0.11.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..f3e7f9e1dd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,709 @@
+---
+layout: docs
+page_title: Vault Integration and Retrieving Dynamic Secrets
+sidebar_title: Vault
+description: |-
+  Learn how to deploy an application in Nomad and retrieve dynamic credentials
+  by integrating with Vault.
+---
+
+# Vault Integration
+
+Nomad integrates seamlessly with [Vault][vault] and allows your application to
+retrieve dynamic credentials for various tasks. In this guide, you will deploy a
+web application that needs to authenticate against [PostgreSQL][postgresql] to
+display data from a table to the user.
+
+## Reference Material
+
+- [Vault Integration Documentation][vault-integration]
+- [Nomad Template Stanza Integration with Vault][nomad-template-vault]
+- [Secrets Task Directory][secrets-task-directory]
+
+## Estimated Time to Complete
+
+20 minutes
+
+## Challenge
+
+Think of a scenario where a Nomad operator needs to deploy an application that
+can quickly and safely retrieve dynamic credentials to authenticate against a
+database and return information.
+
+## Solution
+
+Deploy Vault and configure the nodes in your Nomad cluster to integrate with it.
+Use the appropriate [templating syntax][nomad-template-vault] to retrieve
+credentials from Vault and then store those credentials in the
+[secrets][secrets-task-directory] task directory to be consumed by the Nomad
+task.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul and Vault installed. You can use this [repo][repo] to
+easily provision a sandbox environment. This guide will assume a cluster with
+one server node and three client nodes.
+
+-> **Please Note:** This guide is for demo purposes and is only using a single
+Nomad server with Vault installed alongside. In a production cluster, 3 or 5
+Nomad server nodes are recommended along with a separate Vault cluster.
+
+## Steps
+
+### Step 1: Initialize Vault Server
+
+Run the following command to initialize Vault server and receive an
+[unseal][seal] key and initial root [token][token]. Be sure to note the unseal
+key and initial root token as you will need these two pieces of information.
+
+```shell-session
+$ vault operator init -key-shares=1 -key-threshold=1
+```
+
+The `vault operator init` command above creates a single Vault unseal key for
+convenience. For a production environment, it is recommended that you create at
+least five unseal key shares and securely distribute them to independent
+operators. The `vault operator init` command defaults to five key shares and a
+key threshold of three. If you provisioned more than one server, the others will
+become standby nodes but should still be unsealed.
+
+### Step 2: Unseal Vault
+
+Run the following command and then provide your unseal key to Vault.
+
+```shell-session
+$ vault operator unseal
+```
+
+The output of unsealing Vault will look similar to the following:
+
+```text
+Key                    Value
+---                    -----
+Seal Type              shamir
+Initialized            true
+Sealed                 false
+Total Shares           1
+Threshold              1
+Version                0.11.4
+Cluster Name           vault-cluster-d12535e5
+Cluster ID             49383931-c782-fdc6-443e-7681e7b15aca
+HA Enabled             true
+HA Cluster             n/a
+HA Mode                standby
+Active Node Address    <none>
+```
+
+### Step 3: Log in to Vault
+
+Use the [login][login] command to authenticate yourself against Vault using the
+initial root token you received earlier. You will need to authenticate to run
+the necessary commands to write policies, create roles, and configure a
+connection to your database.
+
+```shell-session
+$ vault login <your initial root token>
+```
+
+If your login is successful, you will see output similar to what is shown below:
+
+```text
+Success! You are now authenticated. The token information displayed below
+is already stored in the token helper. You do NOT need to run "vault login"
+again. Future Vault requests will automatically use this token.
+...
+```
+
+### Step 4: Write the Policy for the Nomad Server Token
+
+To use the Vault integration, you must provide a Vault token to your Nomad
+servers. Although you can provide your root token to easily get started, the
+recommended approach is to use a token [role][role] based token. This first
+requires writing a policy that you will attach to the token you provide to your
+Nomad servers. By using this approach, you can limit the set of
+[policies][policy] that tasks managed by Nomad can access.
+
+For this exercise, use the following policy for the token you will create for
+your Nomad server. Place this policy in a file named `nomad-server-policy.hcl`.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+You can now write a policy called `nomad-server` by running the following
+command:
+
+```shell-session
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+You should see the following output:
+
+```text
+Success! Uploaded policy: nomad-server
+```
+
+You will generate the actual token in the next few steps.
+
+### Step 5: Create a Token Role
+
+At this point, you must create a Vault token role that Nomad can use. The token
+role allows you to limit what Vault policies are accessible by jobs
+submitted to Nomad. We will use the following token role:
+
+```json
+{
+  "allowed_policies": "access-tables",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+Please notice that the `access-tables` policy is listed under the
+`allowed_policies` key. We have not created this policy yet, but it will be used
+by our job to retrieve credentials to access the database. A job running in our
+Nomad cluster will only be allowed to use the `access-tables` policy.
+
+If you would like to allow all policies to be used by any job in the Nomad
+cluster except for the ones you specifically prohibit, then use the
+`disallowed_policies` key instead and simply list the policies that should not
+be granted. If you take this approach, be sure to include `nomad-server` in the
+disallowed policies group. An example of this is shown below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+Save the policy in a file named `nomad-cluster-role.json` and create the token
+role named `nomad-cluster`.
+
+```shell-session
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+You should see the following output:
+
+```text
+Success! Data written to: auth/token/roles/nomad-cluster
+```
+
+### Step 6: Generate the Token for the Nomad Server
+
+Run the following command to create a token for your Nomad server:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically creates
+tokens with a parent-child relationship. When an ancestor token is revoked, all
+of its descendant tokens and their associated leases are revoked as well.
+
+If everything works, you should see output similar to the following:
+
+```text
+Key                  Value
+---                  -----
+token                1gr0YoLyTBVZl5UqqvCfK9RJ
+token_accessor       5fz20DuDbxKgweJZt3cMynya
+token_duration       72h
+token_renewable      true
+token_policies       ["default" "nomad-server"]
+identity_policies    []
+policies             ["default" "nomad-server"]
+```
+
+### Step 7: Edit the Nomad Server Configuration to Enable Vault Integration
+
+At this point, you are ready to edit the [vault stanza][vault-stanza] in the
+Nomad Server's configuration file located at `/etc/nomad.d/nomad.hcl`. Provide
+the token you generated in the previous step in the `vault` stanza of your Nomad
+server configuration. The token can also be provided as an environment variable
+called `VAULT_TOKEN`. Be sure to specify the `nomad-cluster-role` in the
+[create_from_role][create-from-role] option. If using
+[Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+modify both the client and server configuration to include the namespace;
+alternatively, it can be provided in the environment variable `VAULT_NAMESPACE`.
+After following these steps and enabling Vault, the `vault` stanza in your Nomad
+server configuration will be similar to what is shown below:
+
+```hcl
+vault {
+  enabled = true
+  address = "http://active.vault.service.consul:8200"
+  task_token_ttl = "1h"
+  create_from_role = "nomad-cluster"
+  token = "<your nomad server token>"
+  namespace = "<vault namespace for the cluster>"
+}
+```
+
+Restart the Nomad server
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+NOTE: Nomad servers will renew the token automatically.
+
+Vault integration needs to be enabled on the client nodes as well, but this has
+been configured for you already in this environment. You will see the `vault`
+stanza in your Nomad clients' configuration (located at
+`/etc/nomad.d/nomad.hcl`) looks similar to the following:
+
+```hcl
+vault {
+  enabled = true
+  address = "http://active.vault.service.consul:8200"
+}
+```
+
+Please note that the Nomad clients do not need to be provided with a Vault
+token.
+
+### Step 8: Deploy Database
+
+The next few steps will involve configuring a connection between Vault and our
+database, so let's deploy one that we can connect to. Create a Nomad job called
+`db.nomad` with the following content:
+
+```hcl
+job "postgres-nomad-demo" {
+  datacenters = ["dc1"]
+
+  group "db" {
+
+    task "server" {
+      driver = "docker"
+
+      config {
+        image = "hashicorp/postgres-nomad-demo:latest"
+        port_map {
+          db = 5432
+        }
+      }
+      resources {
+        network {
+          port  "db"{
+	    static = 5432
+	  }
+        }
+      }
+
+      service {
+        name = "database"
+        port = "db"
+
+        check {
+          type     = "tcp"
+          interval = "2s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+Run the job as shown below:
+
+```shell-session
+$ nomad run db.nomad
+```
+
+Verify the job is running with the following command:
+
+```shell-session
+$ nomad status postgres-nomad-demo
+```
+
+The result of the status command will look similar to the output below:
+
+```text
+ID            = postgres-nomad-demo
+Name          = postgres-nomad-demo
+Submit Date   = 2018-11-15T21:01:00Z
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+db          0       0         1        0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+701e2699  5de1330c  db          0        run      running  1m56s ago  1m33s ago
+```
+
+Now we can move on to configuring the connection between Vault and our database.
+
+### Step 9: Enable the Database Secrets Engine
+
+We are using the database secrets engine for Vault in this exercise so that we
+can generate dynamic credentials for our PostgreSQL database. Run the following command to enable it:
+
+```shell-session
+$ vault secrets enable database
+```
+
+If the previous command was successful, you will see the following output:
+
+```text
+Success! Enabled the database secrets engine at: database/
+```
+
+### Step 10: Configure the Database Secrets Engine
+
+Create a file named `connection.json` and placed the following information into
+it:
+
+```json
+{
+  "plugin_name": "postgresql-database-plugin",
+  "allowed_roles": "accessdb",
+  "connection_url": "postgresql://{{username}}:{{password}}@database.service.consul:5432/postgres?sslmode=disable",
+  "username": "postgres",
+  "password": "postgres123"
+}
+```
+
+The information above allows Vault to connect to our database and create users
+with specific privileges. We will specify the `accessdb` role soon. In a
+production setting, it is recommended to give Vault credentials with enough
+privileges to generate database credentials dynamically and and manage their
+lifecycle.
+
+Run the following command to configure the connection between the database
+secrets engine and our database:
+
+```shell-session
+$ vault write database/config/postgresql @connection.json
+```
+
+If the operation is successful, there will be no output.
+
+### Step 11: Create a Vault Role to Manage Database Privileges
+
+Recall from the previous step that we specified `accessdb` in the
+`allowed_roles` key of our connection information. Let's set up that role now. Create a file called `accessdb.sql` with the following content:
+
+```shell
+CREATE USER "{{name}}" WITH ENCRYPTED PASSWORD '{{password}}' VALID UNTIL
+'{{expiration}}';
+GRANT USAGE ON ALL SEQUENCES IN SCHEMA public TO "{{name}}";
+GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO "{{name}}";
+GRANT ALL ON SCHEMA public TO "{{name}}";
+```
+
+The SQL above will be used in the [creation_statements][creation-statements]
+parameter of our next command to specify the privileges that the dynamic
+credentials being generated will possess. In our case, the dynamic database user
+will have broad privileges that include the ability to read from the tables that
+our application will need to access.
+
+Run the following command to create the role:
+
+```shell-session
+$ vault write database/roles/accessdb db_name=postgresql \
+creation_statements=@accessdb.sql default_ttl=1h max_ttl=24h
+```
+
+You should see the following output after running the previous command:
+
+```text
+Success! Data written to: database/roles/accessdb
+```
+
+### Step 12: Generate PostgreSQL Credentials
+
+You should now be able to generate dynamic credentials to access your database.
+Run the following command to generate a set of credentials:
+
+```shell-session
+$ vault read database/creds/accessdb
+```
+
+The previous command should return output similar to what is shown below:
+
+```text
+Key                Value
+---                -----
+lease_id           database/creds/accessdb/3JozEMSMqw0vHHhvla15sKTW
+lease_duration     1h
+lease_renewable    true
+password           A1a-3pMGjpDXHZ2Qzuf7
+username           v-root-accessdb-5LA65urB4daA8KYy2xku-1542318363
+```
+
+Congratulations! You have configured Vault's connection to your database and can
+now generate credentials with the previously specified privileges. Now we need
+to deploy our application and make sure that it will be able to communicate with
+Vault and obtain the credentials as well.
+
+### Step 13: Create the `access-tables` Policy for Your Nomad Job to Use
+
+Recall from [Step 5][step-5] that we specified a policy named `access-tables` in
+our `allowed_policies` section of the token role. We will create this policy now
+and give it the capability to read from the `database/creds/accessdb` endpoint
+(the same endpoint we read from in the previous step to generate credentials for
+our database). We will then specify this policy in our Nomad job which will
+allow it to retrieve credentials for itself to access the database.
+
+On the Nomad server (which is also running Vault), create a file named
+`access-tables-policy.hcl` with the following content:
+
+```hcl
+path "database/creds/accessdb" {
+  capabilities = ["read"]
+}
+```
+
+Create the `access-tables` policy with the following command:
+
+```shell-session
+$ vault policy write access-tables access-tables-policy.hcl
+```
+
+You should see the following output:
+
+```text
+Success! Uploaded policy: access-tables
+```
+
+### Step 14: Deploy Your Job with the Appropriate Policy and Templating
+
+Now we are ready to deploy our web application and give it the necessary policy
+and configuration to communicate with our database. Create a file called
+`web-app.nomad` and save the following content in it.
+
+```hcl
+job "nomad-vault-demo" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "server" {
+
+      vault {
+        policies = ["access-tables"]
+      }
+
+      driver = "docker"
+      config {
+        image = "hashicorp/nomad-vault-demo:latest"
+        port_map {
+          http = 8080
+        }
+
+        volumes = [
+          "secrets/config.json:/etc/demo/config.json"
+        ]
+      }
+
+      template {
+        data = <<EOF
+{{ with secret "database/creds/accessdb" }}
+  {
+    "host": "database.service.consul",
+    "port": 5432,
+    "username": "{{ .Data.username }}",
+    {{ /* Ensure password is a properly escaped JSON string. */ }}
+    "password": {{ .Data.password | toJSON }},
+    "db": "postgres"
+  }
+{{ end }}
+EOF
+        destination = "secrets/config.json"
+      }
+
+      resources {
+        network {
+          port "http" {}
+        }
+      }
+
+      service {
+        name = "nomad-vault-demo"
+        port = "http"
+
+        tags = [
+          "urlprefix-/",
+        ]
+
+        check {
+          type     = "tcp"
+          interval = "2s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+There are a few key points to note here:
+
+- We have specified the `access-tables` policy in the [vault][vault-jobspec]
+  stanza of this job. The Nomad client will receive a token with this policy
+  attached. Recall from the previous step that this policy will allow our
+  application to read from the `database/creds/accessdb` endpoint in Vault and
+  retrieve credentials.
+- We are using the [template][template] stanza's [vault
+  integration][nomad-template-vault] to populate the JSON configuration file
+  that our application needs. The underlying tool being used is [Consul
+  Template][consul-template]. You can use Consul Template's documentation to
+  learn more about the [syntax][consul-temp-syntax] needed to interact with
+  Vault. Please note that although we have defined the template
+  [inline][inline], we can use the template stanza [in conjunction with the
+  artifact stanza][remote-template] to download an input template from a remote
+  source such as an S3 bucket.
+- We are using the `toJSON` function to ensure the password is encoded as a JSON
+  string. Any templated value which may contain special characters (like quotes
+  or newlines) should be passed through the `toJSON` function.
+- Finally, note that that [destination][destination] of our template is the
+  [secrets/][secrets-task-directory] task directory. This ensures the data is
+  not accessible with a command like [nomad alloc fs][nomad-alloc-fs] or
+  filesystem APIs.
+
+Use the following command to run the job:
+
+```shell-session
+$ nomad run web-app.nomad
+```
+
+### Step 15: Confirm the Application is Accessing the Database
+
+At this point, you can visit your application at the path `/names` to confirm
+the appropriate data is being accessed from the database and displayed to you.
+There are several ways to do this.
+
+- Use the `dig` command to query the SRV record of your service and obtain the
+  port it is using. Then `curl` your service at the appropriate port and `names` path.
+
+```shell-session
+$ dig +short SRV nomad-vault-demo.service.consul
+1 1 30478 ip-172-31-58-230.node.dc1.consul.
+```
+
+```shell-session
+$ curl nomad-vault-demo.service.consul:30478/names
+<!DOCTYPE html>
+<html>
+<body>
+
+<h1> Welcome! </h1>
+<h2> If everything worked correctly, you should be able to see a list of names
+below </h2>
+
+<hr>
+
+
+<h4> John Doe </h4>
+
+<h4> Peter Parker </h4>
+
+<h4> Clifford Roosevelt </h4>
+
+<h4> Bruce Wayne </h4>
+
+<h4> Steven Clark </h4>
+
+<h4> Mary Jane </h4>
+
+
+</body>
+<html>
+```
+
+- You can also deploy [fabio][fabio] and visit any Nomad client at its public IP
+  address using a fixed port. The details of this method are beyond the scope of
+  this guide, but you can refer to the [Load Balancing with Fabio][fabio-lb]
+  guide for more information on this topic. Alternatively, you could use the
+  `nomad` [alloc status][alloc-status] command along with the AWS console to
+  determine the public IP and port your service is running (remember to open the
+  port in your AWS security group if you choose this method).
+
+[![Web Service][web-service]][web-service]
+
+[alloc-status]: /docs/commands/alloc/status
+[consul-template]: https://github.com/hashicorp/consul-template
+[consul-temp-syntax]: https://github.com/hashicorp/consul-template#secret
+[create-from-role]: /docs/configuration/vault#create_from_role
+[creation-statements]: https://www.vaultproject.io/api/secret/databases#creation_statements
+[destination]: /docs/job-specification/template#destination
+[fabio]: https://github.com/fabiolb/fabio
+[fabio-lb]: https://learn.hashicorp.com/nomad/load-balancing/fabio
+[inline]: /docs/job-specification/template#inline-template
+[login]: https://www.vaultproject.io/docs/commands/login
+[nomad-alloc-fs]: /docs/commands/alloc/fs
+[nomad-template-vault]: /docs/job-specification/template#vault-integration
+[policy]: https://www.vaultproject.io/docs/concepts/policies
+[postgresql]: https://www.postgresql.org/about/
+[remote-template]: /docs/job-specification/template#remote-template
+[repo]: https://github.com/hashicorp/nomad/tree/master/terraform
+[role]: https://www.vaultproject.io/docs/auth/token
+[seal]: https://www.vaultproject.io/docs/concepts/seal
+[secrets-task-directory]: /docs/runtime/environment#secrets
+[step-5]: /docs/integrations/vault-integration#step-5-create-a-token-role
+[template]: /docs/job-specification/template
+[token]: https://www.vaultproject.io/docs/concepts/tokens
+[vault]: https://www.vaultproject.io/
+[vault-integration]: /docs/vault-integration
+[vault-jobspec]: /docs/job-specification/vault
+[vault-stanza]: /docs/configuration/vault
+[web-service]: /img/nomad-demo-app.png
diff --git a/content/nomad/v0.11.x/content/docs/internals/architecture.mdx b/content/nomad/v0.11.x/content/docs/internals/architecture.mdx
new file mode 100644
index 0000000000..18919474bd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/architecture.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: Architecture
+sidebar_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+- **Job** - A Job is a specification provided by users that declares a workload for
+  Nomad. A Job is a form of _desired state_; the user is expressing that the job should
+  be running, but not where it should be run. The responsibility of Nomad is to make sure
+  the _actual state_ matches the user desired state. A Job is composed of one or more
+  task groups.
+
+- **Task Group** - A Task Group is a set of tasks that must be run together. For example, a
+  web server may require that a log shipping co-process is always running as well. A task
+  group is the unit of scheduling, meaning the entire group must run on the same client node and
+  cannot be split.
+
+- **Driver** – A Driver represents the basic means of executing your **Tasks**.
+  Example Drivers include Docker, Qemu, Java, and static binaries.
+
+- **Task** - A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+  which allow Nomad to be flexible in the types of tasks it supports. Tasks
+  specify their driver, configuration for the driver, constraints, and resources required.
+
+- **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the
+  Nomad agent. The agent is responsible for registering with the servers, watching for any
+  work to be assigned and executing tasks. The Nomad agent is a long lived process which
+  interfaces with the servers.
+
+- **Allocation** - An Allocation is a mapping between a task group in a job and a client
+  node. A single job may have hundreds or thousands of task groups, meaning an equivalent
+  number of allocations must exist to map the work to client machines. Allocations are created
+  by the Nomad servers as part of scheduling decisions made during an evaluation.
+
+- **Evaluation** - Evaluations are the mechanism by which Nomad makes scheduling decisions.
+  When either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad creates
+  a new evaluation to determine if any actions must be taken. An evaluation may result
+  in changes to allocations if necessary.
+
+- **Server** - Nomad servers are the brains of the cluster. There is a cluster of servers
+  per region and they manage all jobs and clients, run evaluations, and create task allocations.
+  The servers replicate data between each other and perform leader election to ensure high
+  availability. Servers federate across regions to make Nomad globally aware.
+
+- **Regions and Datacenters** - Nomad models infrastructure as regions and
+  datacenters. Regions may contain multiple datacenters. Servers are assigned to
+  a specific region, managing state and making scheduling decisions within that
+  region. Multiple regions can be federated together. For example, you may
+  have a `US` region with the `us-east-1` and `us-west-1` datacenters,
+  connected to the `EU` region with the `eu-fr-1` and `eu-uk-1` datacenters.
+  Requests that are made between regions are forwarded to the appropriate servers.
+  Data is _not_ replicated between regions.
+
+- **Bin Packing** - Bin Packing is the process of filling bins with items in a way that
+  maximizes the utilization of bins. This extends to Nomad, where the clients are "bins"
+  and the items are task groups. Nomad optimizes resources by efficiently bin packing
+  tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/docs/internals/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/docs/internals/consensus),
+[gossip protocol](/docs/internals/gossip), and [scheduler design](/docs/internals/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v0.11.x/content/docs/internals/consensus.mdx b/content/nomad/v0.11.x/content/docs/internals/consensus.mdx
new file mode 100644
index 0000000000..280729ab05
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/consensus.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Consensus Protocol
+sidebar_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v0.11.x/content/docs/internals/gossip.mdx b/content/nomad/v0.11.x/content/docs/internals/gossip.mdx
new file mode 100644
index 0000000000..400e0c6629
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/gossip.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Gossip Protocol
+sidebar_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/internals/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/docs/internals/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v0.11.x/content/docs/internals/index.mdx b/content/nomad/v0.11.x/content/docs/internals/index.mdx
new file mode 100644
index 0000000000..d9c0711f9c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Internals
+sidebar_title: Internals
+description: >-
+  This section covers the internals of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Internals
+
+This section covers the internals of Nomad and explains the technical
+details of how Nomad functions, its architecture, and sub-systems.
+
+-> **Note:** Knowledge of Nomad internals is not
+required to use Nomad. If you aren't interested in the internals
+of Nomad, you may safely skip this section. If you are operating Nomad,
+we recommend understanding the internals.
diff --git a/content/nomad/v0.11.x/content/docs/internals/plugins/base.mdx b/content/nomad/v0.11.x/content/docs/internals/plugins/base.mdx
new file mode 100644
index 0000000000..8a71735125
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/plugins/base.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Base Plugin
+sidebar_title: Base
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /docs/configuration/plugin
diff --git a/content/nomad/v0.11.x/content/docs/internals/plugins/csi.mdx b/content/nomad/v0.11.x/content/docs/internals/plugins/csi.mdx
new file mode 100644
index 0000000000..e0c3c57ec1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/plugins/csi.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: Storage Plugins
+sidebar_title: Storage
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the
+industry-standard Container Storage Interface specification unifies
+these APIs in a way that's agnostic to both the storage vendor and the
+container orchestrator. Each storage provider can build its own CSI
+plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
+(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
+Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given
+Nomad client node. A list of available CSI plugins can be found in the
+[Kubernetes CSI documentation][csi-drivers-list]. Any of these plugins
+should work with Nomad out of the box.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+You should almost always run node plugins as Nomad `system` jobs to
+ensure volume claims are released when a Nomad client is drained. Use
+constraints for the node plugin jobs based on the availability of
+volumes. For example, AWS EBS volumes are specific to particular
+availability zones with a region. Controller plugins can be run as
+`service` jobs.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to the Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client updates the server frequently about changes to
+allocations, including terminal state. When the server receives a
+terminal state for a job with volume claims, it creates a volume claim
+garbage collection (GC) evaluation to to handled by the core job
+scheduler. The GC job will send "detach" RPCs to the node plugin. The
+node plugin unmounts the bind-mount from the allocation and unmounts
+the volume from the plugin (if it's not in use by another task). The
+GC job will then send "unpublish" RPCs to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.11.x/content/docs/internals/plugins/devices.mdx b/content/nomad/v0.11.x/content/docs/internals/plugins/devices.mdx
new file mode 100644
index 0000000000..01829331bb
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/plugins/devices.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Devices
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad/tree/master/devices/gpu/nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/docs/internals/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /docs/internals/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v0.11.x/content/docs/internals/plugins/index.mdx b/content/nomad/v0.11.x/content/docs/internals/plugins/index.mdx
new file mode 100644
index 0000000000..d9bb9ae245
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/plugins/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Plugins
+sidebar_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/docs/internals/plugins/task-drivers)
+- [Devices](/docs/internals/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v0.11.x/content/docs/internals/plugins/task-drivers.mdx b/content/nomad/v0.11.x/content/docs/internals/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..7a45b0cb95
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/plugins/task-drivers.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+sidebar_title: Task Drivers
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+Capabilities {
+    // Does the driver support sending OS signals to the task?
+    SendSignals: true,
+    // Does the driver support executing a command within the task execution
+    // environment?
+    Exec:        true,
+    // What filesystem isolation is supported by the driver. Options include
+    // FSIsolationImage, FSIsolationChroot, and FSIsolationNone
+    FSIsolation: FSIsolationImage,
+
+    // NetIsolationModes lists the set of isolation modes supported by the driver.
+    // Options include NetIsolationModeHost, NetIsolationModeGroup,
+    // NetIsolationModeTask, and NetIsolationModeNone.
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver
+    // supports. This is used to check whether mounting host volumes or CSI
+    // volumes is allowed. Options include MountConfigSupportAll (default),
+    // or MountConfigSupportNone.
+    MountConfigs MountConfigSupport
+}
+```
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /docs/internals/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
diff --git a/content/nomad/v0.11.x/content/docs/internals/scheduling/index.mdx b/content/nomad/v0.11.x/content/docs/internals/scheduling/index.mdx
new file mode 100644
index 0000000000..76e2deaf0d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/docs/internals/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/docs/internals/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v0.11.x/content/docs/internals/scheduling/preemption.mdx b/content/nomad/v0.11.x/content/docs/internals/scheduling/preemption.mdx
new file mode 100644
index 0000000000..50f4119d85
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/scheduling/preemption.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Preemption
+sidebar_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporary displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+~> **Enterprise Functionality** System job preemption is available as an Open Source
+feature, while Batch and Service job preemption are only available as
+Enterprise features.
+
+Preemption is enabled by default in Nomad 0.9. Operators can use the [scheduler config](/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v0.11.x/content/docs/internals/scheduling/scheduling.mdx b/content/nomad/v0.11.x/content/docs/internals/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..96c9ff1983
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/internals/scheduling/scheduling.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Internals
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, a `system` scheduler
+that is used to run jobs on every node, and a `core` scheduler which is used
+for internal maintenance. Nomad can be extended to support custom schedulers as
+well.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/affinity.mdx b/content/nomad/v0.11.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..b6a7cf447f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: affinity Stanza - Job Specification
+sidebar_title: affinity
+description: |-
+  The "affinity" stanza allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Stanza
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity']
+  ]}
+/>
+
+The `affinity` stanza allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 5
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task stanzas as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` stanzas. Remember that the
+`affinity` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` stanza matches the node.
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/artifact.mdx b/content/nomad/v0.11.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..9338e935d2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: artifact Stanza - Job Specification
+sidebar_title: artifact
+description: |-
+  The "artifact" stanza instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Stanza
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` stanza instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to download
+  the artifact, relative to the root of the task's directory. If omitted, the
+  default value is to place the artifact in `local/`. The destination is treated
+  as a directory unless `mode` is set to `file`. Source files will be downloaded
+  into that directory path.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` stanzas. Remember that the
+`artifact` stanza is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the task's directory.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/example/nomad-examples"
+  destination = "local/repo"
+}
+```
+
+To download from private repo, sshkey needs to be set. The key must be
+base64-encoded string. Run `base64 -w0 <file>`
+
+```hcl
+artifact {
+  source      = "git@github.com:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    sshkey = "<string>"
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v0.11.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..5b884f1cc1
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: check_restart Stanza - Job Specification
+sidebar_title: check_restart
+description: |-
+  The "check_restart" stanza instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart']
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` stanza instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` stanza, it is
+restarted according to the task group's [`restart` policy][restart_stanza]. The
+`check_restart` settings apply to [`check`s][check_stanza], but may also be
+placed on [`service`s][service_stanza] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the stanzas are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_stanza] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` stanza][restart_stanza] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` stanza][restart_stanza] for
+details.
+
+[check_stanza]: /docs/job-specification/service#check-parameters 'check stanza'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[service_stanza]: /docs/job-specification/service 'service stanza'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/connect.mdx b/content/nomad/v0.11.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..15567cd1e2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,176 @@
+---
+layout: docs
+page_title: connect Stanza - Job Specification
+sidebar_title: connect
+description: The "connect" stanza allows specifying options for Consul Connect integration
+---
+
+# `connect` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` stanza allows configuring various options for
+[Consul Connect](/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/nomad/consul-integration/nomad-connect-acl)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to configure the sidecar
+  service injected by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the configuration of the Envoy
+  proxy task.
+
+## `connect` Examples
+
+The following example is a minimal connect stanza with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v2"
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[Consul Connect Native services][native] and [Nomad variable
+interpolation][interpolation] are _not_ yet supported.
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
+[native]: https://www.consul.io/docs/connect/native.html
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/constraint.mdx b/content/nomad/v0.11.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..6bddf52d10
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,305 @@
+---
+layout: docs
+page_title: constraint Stanza - Job Specification
+sidebar_title: constraint
+description: |-
+  The "constraint" stanza allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Stanza
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint']
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` stanzas. Remember that the
+`constraint` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v0.11.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..cff59997df
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: csi_plugin Stanza - Job Specification
+sidebar_title: csi_plugin <sup>Beta</sup>
+description: >-
+  The "csi_plugin" stanza allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume']} />
+
+The "csi_plugin" stanza allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows the
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <required>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad.
+
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+~> **Note:** During node drains, jobs that claim volumes should be
+moved before the `node` or `monolith` plugin for those
+volumes. Because [`system`][system] jobs are moved last during node drains, you
+should run `node` or `monolith` plugins as `system` jobs.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:latest"
+
+        args = [
+          "node",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id        = "aws-efs0"
+        type      = "node"
+        mount_dir = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /docs/job-specification/volume
+[system]: /docs/schedulers/#system
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/device.mdx b/content/nomad/v0.11.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..2c4c6b83a6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,304 @@
+---
+layout: docs
+page_title: device Stanza - Job Specification
+sidebar_title: device
+description: |-
+  The "device" stanza is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` stanza is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` stanza is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` stanza
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` stanza can be.
+
+~> Device supported is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports is as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` stanzas. Remember that the
+`device` stanza is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v0.11.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..15c20b5d5f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: dispatch_payload Stanza - Job Specification
+sidebar_title: dispatch_payload
+description: |-
+  The "dispatch_payload" stanza allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Stanza
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` stanza is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` stanza. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` stanzas. Remember that the
+`dispatch_payload` stanza is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/env.mdx b/content/nomad/v0.11.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..bff811ed19
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: env Stanza - Job Specification
+sidebar_title: env
+description: |-
+  The "env" stanza configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Stanza
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` stanza configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` stanzas. Remember that the
+`env` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+  "key" = 1.4
+  "key" = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` stanza][template-env].
+
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /docs/job-specification/template#environment-variables 'Nomad template Stanza'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v0.11.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..6645886bbb
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: ephemeral_disk Stanza - Job Specification
+sidebar_title: ephemeral_disk
+description: |-
+  The "ephemeral_disk" stanza describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Stanza
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` stanza describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = "500"
+      sticky  = true
+    }
+  }
+}
+```
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be
+  removed if an error is encountered.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` stanzas. Remember that the
+`ephemeral_disk` stanza is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/expose.mdx b/content/nomad/v0.11.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..3e51efced2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: expose Stanza - Job Specification
+sidebar_title: expose
+description: |-
+  The "expose" stanza allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Stanza
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy', 'expose']}
+/>
+
+The `expose` stanza allows configuration of additional listeners for the default Envoy sidecar
+proxy managed by Nomad for [Consul Connect](/guides/integrations/consul-connect). These
+listeners create a bypass of the Connect TLS and network namespace isolation, enabling
+non-Connect enabled services to make requests to specific HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` stanza. Additional
+information about Expose Path configurations for Envoy can be found in Consul's
+[Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration.html#expose-paths-configuration-reference).
+
+Service [check](https://nomadproject.io/docs/job-specification/service/#check-parameters)
+configurations can use their [expose](/docs/job-specification/service#expose)
+parameter to automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` stanza. The example below effectively demonstrates exposing the `/health`
+endpoint similar to the example above, but using the fully flexible `expose`
+configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations](/docs/job-specification/path)
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+   the configured `path`. Typically this will be the same as the `service.port` value, but
+   could be different if for example the exposed path is intended to resolve to another task
+   in the task group.
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+   for the exposed listener. The port should be configured to [map inside](/docs/job-specification/network#to)
+   the task's network namespace.
+
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the Connect-enabled
+`count-dashboard` service, using the `HTTP` protocol. `count-dashboard` is expected
+to listen inside its namespace to port `9001`, and external services will be able to
+reach its `/metrics` endpoint by connecting to the [network interface](https://nomadproject.io/docs/configuration/client/#network_interface)
+of the node on the allocated `metrics` [Port](/docs/job-specification/network#port-parameters).
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics` endpoint
+using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health` endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service check
+definitions. For these cases the [expose](/docs/job-specification/service#expose)
+parameter in the service check stanza can be used to automatically generate the
+expose path configuration. Configuring a port for use by the check is optional,
+as a dynamic port will be automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[path]: /docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /docs/job-specification/network#port-parameters 'Nomad Port Parameters'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/group.mdx b/content/nomad/v0.11.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..8949949754
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,200 @@
+---
+layout: docs
+page_title: group Stanza - Job Specification
+sidebar_title: group
+description: |-
+  The "group" stanza defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `group` stanza defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/docs/job-specification/spread) for more details.
+
+- `count` `(int: 1)` - Specifies the number of the task groups that should
+  be running under this group. This value must be non-negative.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate stanzas.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart stanza documentation][restart].
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul deregistration
+  and sending each task a shutdown signal. Ideally, services would fail
+  healthchecks once they receive a shutdown signal. Alternatively
+  `shutdown_delay` may be set to give in flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group services. In addition, tasks may have their
+  own [`shutdown_delay`](/docs/job-specification/task#shutdown_delay)
+  which waits between deregistering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration
+  after which a Nomad client that cannot communicate with the servers
+  will stop allocations based on this task group. By default, a client
+  will not stop an allocation until explicitly told to by a server. A
+  client that fails to heartbeat to a server within the
+  `hearbeat_grace` window and any allocations running on it will be
+  marked "lost" and Nomad will schedule replacement
+  allocations. However, these replaced allocations will continue to
+  run on the non-responsive client; an operator may desire that these
+  replaced allocations are also stopped in this case — for example,
+  allocations requiring exclusive access to an external resource. When
+  specified, the Nomad client will stop them after this duration. The
+  Nomad client process must be running for this to occur.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` stanzas. Remember that the
+`group` stanza is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    "my-key" = "my-value"
+  }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other stanzas. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /docs/configuration/server/#heartbeat_grace
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/index.mdx b/content/nomad/v0.11.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..37ac6ff1be
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Job Specification
+sidebar_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+stanza. Alternatively, you can keep reading to see a few examples.
+
+For machine-friendliness, Nomad can also read JSON-equivalent configurations. In
+general, we recommend using the HCL syntax.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+      }
+
+      # The service block tells Nomad how to register this service
+      # with Consul for service discovery and monitoring.
+      service {
+        # This tells Consul to monitor the service on the port
+        # labelled "http". Since Nomad allocates high dynamic port
+        # numbers, we use labels to refer to them.
+        port = "http"
+
+        check {
+          type     = "http"
+          path     = "/health"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        "DB_HOST" = "db01.example.com"
+        "DB_USER" = "web"
+        "DB_PASS" = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU, memory, and bandwidth.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+
+        network {
+          mbits = 100
+
+          # This requests a dynamic port named "http". This will
+          # be something like "46283", but we refer to it via the
+          # label "http".
+          port "http" {}
+
+          # This requests a static port on 443 on the host. This
+          # will restrict this task to running once per host, since
+          # there is only one port 443 on each host.
+          port "https" {
+            static = 443
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` stanza can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+stanza specified at the group level must include a [connect][] stanza, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /docs/job-specification/connect 'Connect Stanza Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/job.mdx b/content/nomad/v0.11.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..2a00ee83ba
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: job Stanza - Job Specification
+sidebar_title: job
+description: |-
+  The "job" stanza is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Stanza
+
+<Placement group={['job']} />
+
+The `job` stanza is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace] (if Nomad
+Enterprise is used).
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    "my-key" = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` `([Group][group]: <required>)` - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate stanzas.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Values other than default are not allowed in non-Enterprise versions of Nomad.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system` and `batch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, rolling updates are disabled.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] stanza. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` stanzas. Remember that the
+`job` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: https://learn.hashicorp.com/nomad/governance-and-policy/namespaces
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: https://learn.hashicorp.com/nomad/operating-nomad/federation
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /docs/schedulers 'Nomad Scheduler Types'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v0.11.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..60aad0d2a8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: lifecycle Stanza - Job Specification
+sidebar_title: lifecycle
+description: |-
+  The "lifecycle" stanza configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Stanza
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` stanza is used to express task dependencies in Nomad and
+configures when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` stanza. Lifecycle task hooks
+are run in relation to the main tasks. Tasks can be run as Prestart Hooks, which
+ensures the prestart task is run before the main tasks are run.
+
+Tasks can be run with an additional parameter to indicate that they are
+sidecars, which ensures that they are running over the duration of the whole
+task group. This will allow you to run a long-lived task in a task group for a
+batch job. The absence of the sidecar flag indicates that the task is ephemeral
+and the task will not be restarted if it completes successfully. This allows you
+to run an ephemeral prestart task in a task group for a service job, which can
+serve as initialization that occurs before the main services are started.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "init" {
+      lifecycle {
+        hook    = "prestart"
+      }
+      ...
+    }
+
+    task "logging" {
+      lifecycle {
+        hook    = "prestart"
+        sidecar = true
+      }
+      ...
+    }
+
+    task "main" {
+      ...
+    }
+
+  }
+}
+```
+
+## `lifecycle` Parameters
+
+- `hook` `(string: "prestart")` - Specifies when a task should be run within
+  the lifecycle of a group. Currently only Prestart Hooks are supported.
+
+- `sidecar` `(bool: false)` - Controls whether or not a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral (`sidecar =
+  false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and it terminates, it will be
+  restarted as long as the task group is running in its allocation.
+
+[learn-taskdeps]: https://learn.hashicorp.com/nomad?track=task-deps&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS#task-deps
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/logs.mdx b/content/nomad/v0.11.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..1d262aa49d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: logs Stanza - Job Specification
+sidebar_title: logs
+description: |-
+  The "logs" stanza configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" stanza
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Stanza
+
+<Placement group={['job', 'group', 'task', 'logs']} />
+
+The `logs` stanza configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` stanza allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` stanzas. Remember that the
+`logs` stanza is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /docs/commands/alloc/logs 'Nomad logs command'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/meta.mdx b/content/nomad/v0.11.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..9067713e33
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: meta Stanza - Job Specification
+sidebar_title: meta
+description: The "meta" stanza allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Stanza
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta']
+  ]}
+/>
+
+The `meta` stanza allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` stanza at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+## `meta` Parameters
+
+The "parameters" for the `meta` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings.
+
+## `meta` Examples
+
+The following examples only show the `meta` stanzas. Remember that the
+`meta` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  "key" = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/migrate.mdx b/content/nomad/v0.11.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..f82b3bf0a6
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: migrate Stanza - Job Specification
+sidebar_title: migrate
+description: |-
+  The "migrate" stanza specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Stanza
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate']
+  ]}
+/>
+
+The `migrate` stanza specifies the group's strategy for migrating off of
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+stanzas.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+stanza for allocations on that node. The `migrate` stanza is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /docs/job-specification/service#check-parameters
+[count]: /docs/job-specification/group#count
+[drain]: /docs/commands/node/drain
+[deadline]: /docs/commands/node/drain#deadline
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/network.mdx b/content/nomad/v0.11.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..c6a9c1b17c
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,213 @@
+---
+layout: docs
+page_title: network Stanza - Job Specification
+sidebar_title: network
+description: |-
+  The "network" stanza specifies the networking requirements for the task,
+  including the minimum bandwidth and port allocations. The network stanza
+  can be specified at the task group level to enable all tasks in the task
+  group to share the same network namespace.
+---
+
+# `network` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'network'],
+    ['job', 'group', 'task', 'resources', 'network']
+  ]}
+/>
+
+The `network` stanza specifies the networking requirements for the task,
+including the minimum bandwidth and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Nomad 0.10 enables support for the `network` stanza at the task group level. When
+the `network` stanza is defined at the group level with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][] enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        network {
+          mbits = 200
+          port "http" {}
+          port "https" {}
+          port "lb" {
+            static = 8889
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `network` Parameters
+
+- `mbits` `(int: 10)` - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. `-1` sets the mapped port equal to the dynamic port allocated by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain the `to` value.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined
+  <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `network` Examples
+
+The following examples only show the `network` stanzas. Remember that the
+`network` stanza is only valid in the placements listed above.
+
+### Bandwidth
+
+This example specifies a resource requirement of 1 Gbit in bandwidth:
+
+```hcl
+network {
+  mbits = 1000
+}
+```
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+task "example" {
+  resources {
+    network {
+      port "http" {}
+      port "https" {}
+    }
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    port_map = {
+      http = 8080
+    }
+  }
+
+  resources {
+    network {
+      port "http" {}
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+The following example is a group level network stanza that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+}
+```
+
+### Limitations
+
+- Only one `network` stanza can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v0.11.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..416e474ed8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,155 @@
+---
+layout: docs
+page_title: parameterized Stanza - Job Specification
+sidebar_title: parameterized
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` stanza is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Stanza
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+stanza is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` stanza allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] stanza that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/periodic.mdx b/content/nomad/v0.11.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..10a7c876de
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: periodic Stanza - Job Specification
+sidebar_title: periodic
+description: |-
+  The "periodic" stanza allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Stanza
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` stanza allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+## `periodic` Examples
+
+The following examples only show the `periodic` stanzas. Remember that the
+`periodic` stanza is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is *desired:*
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be *skipped* for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be *run twice* for that day (eg November 3rd).
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/gorhill/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/proxy.mdx b/content/nomad/v0.11.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..14368187fc
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: proxy Stanza - Job Specification
+sidebar_title: proxy
+description: |-
+  The "proxy" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Stanza
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` stanza allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int:[port][])` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration.html#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](https://www.consul.io/docs/connect/proxies/envoy.html#dynamic-configuration)
+  for details.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[port]: /docs/job-specification/network#port-parameters 'Nomad network port configuration'
+[expose]: /docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v0.11.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..1ce62a4a5e
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: reschedule Stanza - Job Specification
+sidebar_title: reschedule
+description: >-
+  The "reschedule" stanza specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Stanza
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule']
+  ]}
+/>
+
+The `reschedule` stanza specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule stanza is present on both the job and the group, they are merged with
+the group stanza taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the task on another node if any of its allocation
+statuses become "failed". It prefers to create a replacement allocation on a node
+that hasn't previously been used.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule stanza does not apply to `system` jobs because they run on
+every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The Default Batch Reschedule Policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The Default Service Reschedule Policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Rescheduling during deployments
+
+The [update stanza](/docs/job-specification/update) controls rolling updates and canary deployments. A task
+group's reschedule stanza does not take affect during a deployment. For example, if a new version of the job
+is rolled out and the deployment failed due to a failing allocation, Nomad will not reschedule it.
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/resources.mdx b/content/nomad/v0.11.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..a0f6d5fdf5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: resources Stanza - Job Specification
+sidebar_title: resources
+description: |-
+  The "resources" stanza describes the requirements a task needs to execute.
+  Resource requirements include memory, network, cpu, and more.
+---
+
+# `resources` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` stanza describes the requirements a task needs to execute.
+Resource requirements include memory, network, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        network {
+          mbits = 100
+          port "http" {}
+          port "ssh" {
+            static = 22
+          }
+        }
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements, including static and dynamic port allocations.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` stanzas. Remember that the
+`resources` stanza is only valid in the placements listed above.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] stanza
+which require 1 Gbit of bandwidth, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+resources {
+  network {
+    mbits = 1000
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] stanza
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[device]: /docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/restart.mdx b/content/nomad/v0.11.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..4f28f40b6a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: restart Stanza - Job Specification
+sidebar_title: restart
+description: The "restart" stanza configures a group's behavior on task failure.
+---
+
+# `restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart']
+  ]}
+/>
+
+The `restart` stanza configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group. If present on the task, the policy is merged with
+the restart policy from the encapsulating task group.
+
+For example, assuming that the task group restart policy is: 
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+and the individual task restart policy is: 
+```hcl
+restart {
+  attempts = 5
+}
+```
+then the effective restart policy for the task will be: 
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the scheduler to delay the next restart until the next
+  `interval` is reached.
+
+- `"fail"` - Instructs the scheduler to not attempt to restart the task on
+  failure. This is the default behavior. This mode is useful for non-idempotent jobs which are unlikely to
+  succeed after a few failures. Failed jobs will be restarted according to
+  the [`reschedule`](/docs/job-specification/reschedule) stanza.
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/scaling.mdx b/content/nomad/v0.11.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..e2000541fe
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: scaling Stanza - Job Specification
+sidebar_title: scaling <sup>Beta</sup>
+description: The "scaling" stanza allows specifying scaling policy for a task group
+---
+
+# `scaling` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `scaling` stanza allows configuring scaling options for a task group, for the purpose
+of supporting external autoscalers like the [Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler).
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+      }
+    }
+    scaling {
+      enabled = true
+      min = 0
+      max = 10
+      policy {
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [count][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; see autoscaler documentation.
+
+[count]: /docs/job-specification/group/#count 'Nomad Task Group specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/service.mdx b/content/nomad/v0.11.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..622d3481ed
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,704 @@
+---
+layout: docs
+page_title: service Stanza - Job Specification
+sidebar_title: service
+description: |-
+  The "service" stanza instructs Nomad to register the task as a service using
+  the service discovery integration.
+---
+
+# `service` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service']
+  ]}
+/>
+
+The `service` stanza instructs Nomad to register a service with Consul. This
+section of the documentation will discuss the configuration, but please also
+read the [Nomad service discovery documentation][service-discovery] for more
+detailed information about the integration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and stanzas
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` stanza at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `check` <code>([Check](#check-parameters): nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, Nomad supports the
+  `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services.
+
+- `name` `(string: "<job>-<group>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${GROUP}` - the name of the group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${GROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `driver` - Advertise the port determined by the driver (eg Docker or rkt).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `port_map`.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] stanza.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](https://www.consul.io/docs/internals/anti-entropy.html#enable-tag-override)
+  for more information.
+
+- `address_mode` `(string: "auto")` - Specifies what address (host or
+  driver-specific) this service should advertise. This setting is supported in
+  Docker since Nomad 0.6 and rkt since Nomad 0.7. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker and rkt.
+
+  - `host` - Use the host IP and port.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter.
+
+### `check` Parameters
+
+Note that health checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. Added in Nomad 0.7.1. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` stanza][check_restart_stanza].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the originating status of the
+  service. Valid options are the empty string, `passing`, `warning`, and
+  `critical`.
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s"
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. Check
+  must be of [`type`][type] `http` or `grpc`.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] stanza. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` stanzas will apply to the specified task. For `checks` on group
+  level `services` only.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+#### `header` Stanza
+
+HTTP checks may include a `header` stanza to set HTTP headers. The `header`
+stanza parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with Consul. It
+is important to understand when each of these steps happens and how they can be
+customized.
+
+**Registration**: Nomad will register `group` services and checks *before*
+starting any tasks. Services and checks for a specific `task` are registered
+*after* the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in Consul as well. Consul is updated without restarting a task.
+
+**Deregistering**: If a running task with a service stanza exits, the services
+and checks are immediately deregistered from Consul without delay. If however
+Nomad needs to kill a running task, the task is killed in the following order:
+
+1. Immediately remove the services and checks from Consul. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in Consul, and
+   thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` stanzas. Remember that the
+`service` stanza is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks.
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+This example must be accompanied by a [`network`][network] stanza which defines
+a static or dynamic port labeled "lb". For example:
+
+```hcl
+resources {
+  network {
+    mbits = 10
+    port "lb" {}
+  }
+}
+```
+
+### Script Checks with Shells
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name     = "Postgres Check"
+    type     = "script"
+    command  = "/usr/local/bin/pg-tools"
+    args     = ["verify", "database", "prod", "up"]
+    interval = "5s"
+    timeout  = "2s"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] stanza. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Using Driver Address Mode
+
+The [Docker](/docs/drivers/docker#network_mode) and
+[rkt](/docs/drivers/rkt#net) drivers support the `driver` setting for the
+`address_mode` parameter in both `service` and `check` stanzas. The driver
+address mode allows advertising and health checking the IP and port assigned to
+a task by the driver. This way if you're using a network plugin like Weave with
+Docker, you can advertise the Weave address in Consul instead of the host's
+address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+          port "db" {}
+        }
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required!
+
+Services default to the `auto` address mode. When a Docker network mode other
+than "host" or "bridge" is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` stanzas default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` stanza's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        # No port map required!
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+        }
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` stanzas can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` stanza to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+          port "db" {}
+        }
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        # No port map required!
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+        }
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` stanzas can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the [qemu driver][qemu] since the Nomad
+  client does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_stanza]: /docs/job-specification/check_restart 'check_restart stanza'
+[consul_grpc]: https://www.consul.io/api/agent/check.html#grpc
+[service-discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /docs/drivers/qemu 'Nomad qemu Driver'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /docs/job-specification/service#type
+[shutdowndelay]: /docs/job-specification/task#shutdown_delay
+[killsignal]: /docs/job-specification/task#kill_signal
+[killtimeout]: /docs/job-specification/task#kill_timeout
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v0.11.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..f16aa06023
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: sidecar_service Stanza - Job Specification
+sidebar_title: sidecar_service
+description: |-
+  The "sidecar_service" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` stanza allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags for the sidecar service.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the sidecar proxy service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` stanza with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v0.11.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..9ec98c1f51
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,161 @@
+---
+layout: docs
+page_title: sidecar_task Stanza - Job Specification
+sidebar_title: sidecar_task
+description: |-
+  The "sidecar_task" stanza allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` stanza allows configuring various options for the proxy
+sidecar managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service = {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy proxy sidecar
+
+Nomad automatically includes a default Envoy proxy sidecar task whenever a
+group service has a [`sidecar_service`][sidecar_service] stanza.
+
+The default sidecar task is equivalent to:
+
+```hcl
+   sidecar_task {
+     name   = "connect-proxy-<service>"
+
+     lifecycle {
+       hook = "prestart"
+       sidecar = true
+     }
+
+     driver = "docker"
+     config {
+       image = "${meta.connect.sidecar_image}"
+       args  = [
+         "-c",
+         "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+         "-l",
+         "${meta.connect.log_level}"
+       ]
+     }
+
+     logs {
+       max_files     = 2
+       max_file_size = 2 # MB
+     }
+
+     resources {
+       cpu    = 250 # MHz
+       memory = 128 # MB
+     }
+
+     shutdown_delay = "5s"
+   }
+```
+
+The `meta.connect.sidecar_image` and `meta.connect.log_level` are [_client_
+configurable][nodemeta] variables with the following defaults:
+
+- `sidecar_image` - `"envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"` - The official upstream Envoy Docker image.
+- `sidecar_log_level` - `"info"` - Envoy sidecar log level. "`debug`" is useful
+  for debugging Connect related issues.
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-proxy-<service>")` - Name of the task. Defaults to
+  including the name of the service it is a proxy for.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /docs/job-specification/connect 'Nomad connect Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[nodemeta]: /docs/configuration/client#meta
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/spread.mdx b/content/nomad/v0.11.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..04c05899ad
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,164 @@
+---
+layout: docs
+page_title: spread Stanza - Job Specification
+sidebar_title: spread
+description: >-
+  The "spread" stanza is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread stanza may be specified with relative weights between
+  each.
+---
+
+# `spread` Stanza
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread']
+  ]}
+/>
+
+The `spread` stanza allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread stanza. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler.
+If no nodes match a given spread criteria, placement is still successful.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread stanza. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread stanza. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity stanza to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` stanza.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` stanza.
+
+### Even Spread Across Data Center
+
+This example shows a spread stanza across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread stanza that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread stanza that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread stanzas with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread stanza used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/task.mdx b/content/nomad/v0.11.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..aaada691e9
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,215 @@
+---
+layout: docs
+page_title: task Stanza - Job Specification
+sidebar_title: task
+description: |-
+  The "task" stanza creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Stanza
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` stanza creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad sends an `SIGINT`.
+  If the task does not exit before the configured timeout, `SIGKILL` is sent to
+  the task. Note that the value set here is capped at the value set for
+  [`max_kill_timeout`][max_kill] on the agent running the task, which has a
+  default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT. Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to true, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and network.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing it from Consul and sending it a shutdown
+  signal. Ideally services would fail healthchecks once they receive a shutdown
+  signal. Alternatively `shutdown_delay` may be set to give in flight requests
+  time to complete before shutting down. In addition, task groups may have their
+  own [`shutdown_delay`](/docs/job-specification/group#shutdown_delay)
+  which waits between deregistering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_blacklist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` stanzas. Remember that the
+`task` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    network {
+      mbits = 250
+    }
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[exec]: /docs/drivers/exec 'Nomad exec Driver'
+[java]: /docs/drivers/java 'Nomad Java Driver'
+[docker]: /docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /docs/configuration/client#user-checked_drivers
+[user_blacklist]: /docs/configuration/client#user-blacklist
+[max_kill]: /docs/configuration/client#max_kill_timeout
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/template.mdx b/content/nomad/v0.11.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..a4feba161d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,345 @@
+---
+layout: docs
+page_title: template Stanza - Job Specification
+sidebar_title: template
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Stanza
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. Since Nomad
+v0.5.6, the template can reference [Node attributes and metadata][nodevars]. For
+a full list of the API template functions, please refer to the [Consul Template
+README][ct]. Since Nomad v0.6.0, templates can be read as environment variables.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the task directory.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task. ([See below](#environment-variables))
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside of a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` stanzas. Remember that the
+`template` stanza is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] stanza to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template stanza:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `template.allow_host_source` - Allows templates to specify their source
+  template as an absolute path referencing host directories. Defaults to `true`.
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/update.mdx b/content/nomad/v0.11.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..2cbbcc46c8
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,270 @@
+---
+layout: docs
+page_title: update Stanza - Job Specification
+sidebar_title: update
+description: |-
+  The "update" stanza specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, rolling updates and canaries are disabled.
+---
+
+# `update` Stanza
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update']
+  ]}
+/>
+
+The `update` stanza specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, rolling updates and canaries are disabled. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` stanzas are specified, they are merged with the
+group stanza taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` stanza in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state. If no allocation
+  transitions to the healthy state before the progress deadline, the deployment
+  is marked as failed. If the `progress_deadline` is set to `0`, the first
+  allocation to be marked as unhealthy causes the deployment to fail. This is
+  specified using a label suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to the
+  canary version when all canaries become healthy during a deployment. Defaults to
+  false which means canaries must be manually updated with the `nomad deployment promote`
+  command.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` stanzas. Remember that the
+`update` stanza is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Stanza Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update stanza, each groups update
+stanza may be kept to a minimum. The merged update stanzas for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 'Nomad Rolling Upgrades'
+[strategies]: https://learn.hashicorp.com/nomad/update-strategies 'Nomad Update Strategies'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v0.11.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..59c5cb010a
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: upstreams Stanza - Job Specification
+sidebar_title: upstreams
+description: |-
+  The "upstreams" stanza allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams'
+  ]}
+/>
+
+The `upstreams` stanza allows configuring various options for managing upstream
+services that a [Consul
+Connect](/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` stanza.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v1"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/vault.mdx b/content/nomad/v0.11.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..996f3641ab
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: vault Stanza - Job Specification
+sidebar_title: vault
+description: |-
+  The "vault" stanza allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Stanza
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault']
+  ]}
+/>
+
+The `vault` stanza allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` stanzas are specified, they are merged with the `task` stanza
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/docs/configuration/vault#namespace)
+to use [Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` stanza is specified, the [`template`][template] stanza can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/volume.mdx b/content/nomad/v0.11.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..1411b86cd7
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: volume Stanza - Job Specification
+sidebar_title: volume
+description: >-
+  The "volume" stanza allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Stanza
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` stanza allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the stanza is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` stanzas. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] stanza in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+[volume_mount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /docs/configuration/client/#host_volume-stanza
+[csi_volume]: /docs/commands/volume/register
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.11.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v0.11.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..4f9b2becbb
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: volume_mount Stanza - Job Specification
+sidebar_title: volume_mount
+description: |-
+  The "volume_mount" stanza allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` stanza allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v0.11.x/content/docs/runtime/environment.mdx b/content/nomad/v0.11.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..03313bfbfd
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Environment - Runtime
+sidebar_title: Runtime Environment
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name as well as the task, group and
+job's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`.
+The allocation ID and index can be useful when the task being run needs a unique
+identifier or to know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT` and
+`NOMAD_MEMORY_LIMIT`. Your task should use these values to adapt its behavior to
+fit inside the resource allocation that nomad provides. For example, you can use
+the memory limit to inform how large your in-process cache should be, or to
+decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad makes the following directories available to tasks:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs and where possible backed by an
+  in-memory filesystem. It can be used to store secret data that should not be
+  visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories are
+made available in various ways. For example, on `docker` the directories are
+bound to the container, while on `exec` on Linux the directories are mounted into the
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v0.11.x/content/docs/runtime/index.mdx b/content/nomad/v0.11.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..395b323583
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/docs/runtime/environment)
+- [Interpolation](/docs/runtime/interpolation)
+- [Schedulers](/docs/schedulers)
diff --git a/content/nomad/v0.11.x/content/docs/runtime/interpolation.mdx b/content/nomad/v0.11.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..8838fd7c1f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,333 @@
+---
+layout: docs
+page_title: Variable Interpolation
+sidebar_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    "DC"      = "Running on datacenter ${node.datacenter}"
+    "VERSION" = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:3.2"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v0.11.x/content/docs/schedulers.mdx b/content/nomad/v0.11.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..304f6d60c2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/schedulers.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: Schedulers
+sidebar_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has three scheduler types that can be used when creating your job:
+`service`, `batch` and `system`. Here we will describe the differences between
+each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] stanzas.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+stanzas.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] stanza; system jobs do not have rescheduling.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
+[preemption]: /docs/internals/scheduling/preemption
+[restart]: /docs/job-specification/restart
+[reschedule]: /docs/job-specification/reschedule
diff --git a/content/nomad/v0.11.x/content/docs/telemetry/index.mdx b/content/nomad/v0.11.x/content/docs/telemetry/index.mdx
new file mode 100644
index 0000000000..4126835b21
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/telemetry/index.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: Telemetry Overview
+sidebar_title: Telemetry
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Telemetry Overview
+
+The Nomad client and server agents collect a wide range of runtime metrics
+related to the performance of the system. Operators can use this data to gain
+real-time visibility into their cluster and improve performance. Additionally,
+Nomad operators can set up monitoring and alerting based on these metrics in
+order to respond to any changes in the cluster state.
+
+On the server side, leaders and
+followers have metrics in common as well as metrics that are specific to their
+roles. Clients have separate metrics for the host metrics and for
+allocations/tasks, both of which have to be [explicitly
+enabled][telemetry-stanza]. There are also runtime metrics that are common to
+all servers and clients.
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [Gauges, counters and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/metrics API endpoint][metrics-api-endpoint] to return metrics for
+  the current Nomad process (as of Nomad 0.7). This endpoint supports Prometheus
+  formatted metrics.
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+- Configure Nomad to automatically forward metrics to a third-party provider.
+
+Nomad 0.7 added support for [tagged metrics][tagged-metrics], improving the
+integrations with [DataDog][datadog-telem] and [Prometheus][prometheus-telem].
+Metrics can also be forwarded to [Statsite][statsite-telem],
+[StatsD][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns:
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+The sections below cover a number of important metrics
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking issues
+between the servers or insufficient CPU resources. Users in cloud environments
+often bump their servers up to the next instance class with improved networking
+and CPU to stabilize leader elections. The `nomad.raft.leader.lastContact` metric
+is a general indicator of Raft latency which can be used to observe how Raft
+timing is performing and guide the decision to upgrade to more powerful servers.
+`nomad.raft.leader.lastContact` should not get too close to the leader lease
+timeout of 500ms.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+## Scheduling
+
+The following metrics allow an operator to observe changes in throughput at the
+various points in the scheduling process (evaluation, scheduling/planning, and
+placement):
+
+- **nomad.broker.total_blocked** - The number of blocked evaluations.
+- **nomad.worker.invoke_scheduler.\<type\>** - The time to run the scheduler of
+  the given type.
+- **nomad.plan.evaluate** - The time to evaluate a scheduler Plan.
+- **nomad.plan.submit** - The time to submit a scheduler Plan.
+- **nomad.plan.queue_depth** - The number of scheduler Plans waiting to be
+  evaluated.
+
+Upticks in any of the above metrics indicate a decrease in scheduler throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis:
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+We do not currently surface metrics for job and task/allocation status, although
+we will consider adding metrics where it makes sense.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure:
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /docs/configuration/telemetry#circonus
+[collection-interval]: /docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /docs/configuration/telemetry#datadog
+[prometheus-telem]: /docs/configuration/telemetry#prometheus
+[metrics-api-endpoint]: /api-docs/metrics
+[metric-types]: /docs/telemetry/metrics#metric-types
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /docs/configuration/telemetry#statsd
+[statsite-telem]: /docs/configuration/telemetry#statsite
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[telemetry-stanza]: /docs/configuration/telemetry
diff --git a/content/nomad/v0.11.x/content/docs/telemetry/metrics.mdx b/content/nomad/v0.11.x/content/docs/telemetry/metrics.mdx
new file mode 100644
index 0000000000..4c731d8728
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/telemetry/metrics.mdx
@@ -0,0 +1,1109 @@
+---
+layout: docs
+page_title: Metrics
+sidebar_title: Metrics
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process.
+
+As of Nomad version 0.7, this data is available via HTTP at `/metrics`. See
+[Metrics](/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+## Key Metrics
+
+When telemetry is being streamed to statsite or statsd, `interval` is defined to
+be their flush interval. Otherwise, the interval can be assumed to be 10 seconds
+when retrieving metrics using the above described signals.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.runtime.num_goroutines</code>
+      </td>
+      <td>Number of goroutines and general load pressure indicator</td>
+      <td># of goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.runtime.alloc_bytes</code>
+      </td>
+      <td>Memory utilization</td>
+      <td># of bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.runtime.heap_objects</code>
+      </td>
+      <td>Number of objects on the heap. General memory pressure indicator</td>
+      <td># of heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.apply</code>
+      </td>
+      <td>Number of Raft transactions</td>
+      <td>Raft transactions / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.replication.appendEntries</code>
+      </td>
+      <td>Raft transaction commit time</td>
+      <td>ms / Raft Log Append</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.leader.lastContact</code>
+      </td>
+      <td>
+        Time since last contact to leader. General indicator of Raft latency
+      </td>
+      <td>ms / Leader Contact</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_ready</code>
+      </td>
+      <td>Number of evaluations ready to be processed</td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_unacked</code>
+      </td>
+      <td>Evaluations dispatched for processing but incomplete</td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_blocked</code>
+      </td>
+      <td>
+        Evaluations that are blocked until an existing evaluation for the same
+        job completes
+      </td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.queue_depth</code>
+      </td>
+      <td>Number of scheduler Plans waiting to be evaluated</td>
+      <td># of plans</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.submit</code>
+      </td>
+      <td>
+        Time to submit a scheduler Plan. Higher values cause lower scheduling
+        throughput
+      </td>
+      <td>ms / Plan Submit</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.evaluate</code>
+      </td>
+      <td>
+        Time to validate a scheduler Plan. Higher values cause lower scheduling
+        throughput. Similar to <code>nomad.plan.submit</code> but does not
+        include RPC time or time in the Plan Queue
+      </td>
+      <td>ms / Plan Evaluation</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.worker.invoke_scheduler.&lt;type&gt;</code>
+      </td>
+      <td>Time to run the scheduler of the given type</td>
+      <td>ms / Scheduler Run</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.worker.wait_for_index</code>
+      </td>
+      <td>
+        Time waiting for Raft log replication from leader. High delays result in
+        lower scheduling throughput
+      </td>
+      <td>ms / Raft Index Wait</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.heartbeat.active</code>
+      </td>
+      <td>
+        Number of active heartbeat timers. Each timer represents a Nomad Client
+        connection
+      </td>
+      <td># of heartbeat timers</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.heartbeat.invalidate</code>
+      </td>
+      <td>
+        The length of time it takes to invalidate a Nomad Client due to failed
+        heartbeats
+      </td>
+      <td>ms / Heartbeat Invalidation</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.query</code>
+      </td>
+      <td>Number of RPC queries</td>
+      <td>RPC Queries / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.request</code>
+      </td>
+      <td>Number of RPC requests being handled</td>
+      <td>RPC Requests / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.request_error</code>
+      </td>
+      <td>Number of RPC requests being handled that result in an error</td>
+      <td>RPC Errors / `interval`</td>
+      <td>Counter</td>
+    </tr>
+  </tbody>
+</table>
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/docs/configuration/telemetry)
+page for more details.
+
+As of Nomad 0.9, Nomad will emit additional labels for [parameterized](/docs/job-specification/parameterized) and
+[periodic](/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+<table>
+  <thead>
+    <tr>
+      <th>Label</th>
+      <th>Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>job</td>
+      <td>
+        <code>myjob/dispatch-1312323423423</code>
+      </td>
+    </tr>
+    <tr>
+      <td>parent_id</td>
+      <td>myjob</td>
+    </tr>
+    <tr>
+      <td>dispatch_id</td>
+      <td>1312323423423</td>
+    </tr>
+  </tbody>
+</table>
+
+## Host Metrics (post Nomad version 0.7)
+
+Starting in version 0.7, Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.cpu</code>
+      </td>
+      <td>Total amount of CPU shares the scheduler has allocated to tasks</td>
+      <td>MHz</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.cpu</code>
+      </td>
+      <td>
+        Total amount of CPU shares free for the scheduler to allocate to tasks
+      </td>
+      <td>MHz</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.memory</code>
+      </td>
+      <td>Total amount of memory the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.memory</code>
+      </td>
+      <td>
+        Total amount of memory free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.disk</code>
+      </td>
+      <td>Total amount of disk space the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.disk</code>
+      </td>
+      <td>
+        Total amount of disk space free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.network</code>
+      </td>
+      <td>
+        Total amount of bandwidth the scheduler has allocated to tasks on the
+        given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, device</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.network</code>
+      </td>
+      <td>
+        Total amount of bandwidth free for the scheduler to allocate to tasks on
+        the given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, device</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.total</code>
+      </td>
+      <td>Total amount of physical memory on the node</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.available</code>
+      </td>
+      <td>
+        Total amount of memory available to processes which includes free and
+        cached memory
+      </td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.used</code>
+      </td>
+      <td>Amount of memory used by processes</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.free</code>
+      </td>
+      <td>Amount of memory which is free</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.uptime</code>
+      </td>
+      <td>Uptime of the host running the Nomad client</td>
+      <td>Seconds</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.total</code>
+      </td>
+      <td>Total CPU utilization</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.user</code>
+      </td>
+      <td>CPU utilization in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.system</code>
+      </td>
+      <td>CPU utilization in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.idle</code>
+      </td>
+      <td>Idle time spent by the CPU</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.size</code>
+      </td>
+      <td>Total size of the device</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.used</code>
+      </td>
+      <td>Amount of space which has been used</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.available</code>
+      </td>
+      <td>Amount of space which is available</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.used_percent</code>
+      </td>
+      <td>Percentage of disk space used</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.inodes_percent</code>
+      </td>
+      <td>Disk space consumed by the inodes</td>
+      <td>Percent</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.start</code>
+      </td>
+      <td>Number of allocations starting</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.running</code>
+      </td>
+      <td>Number of allocations starting to run</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.failed</code>
+      </td>
+      <td>Number of allocations failing</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.restart</code>
+      </td>
+      <td>Number of allocations restarting</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.complete</code>
+      </td>
+      <td>Number of allocations completing</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.destroy</code>
+      </td>
+      <td>Number of allocations being destroyed</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+  </tbody>
+</table>
+
+Nomad 0.9 adds an additional `node_class` label from the client's
+`NodeClass` attribute. This label is set to the string "none" if empty.
+
+## Host Metrics (deprecated post Nomad 0.7)
+
+The below are metrics emitted by Nomad in versions prior to 0.7. These metrics
+can be emitted in the below format post-0.7 (as well as the new format,
+detailed above) but any new metrics will only be available in the new format.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.cpu.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of CPU shares the scheduler has allocated to tasks</td>
+      <td>MHz</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.cpu.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of CPU shares free for the scheduler to allocate to tasks
+      </td>
+      <td>MHz</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.memory.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of memory the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.memory.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of memory free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.disk.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of disk space the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.disk.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of disk space free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocated.network.&lt;Device-Name&gt;.&lt;HostID&gt;
+        </code>
+      </td>
+      <td>
+        Total amount of bandwidth the scheduler has allocated to tasks on the
+        given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.unallocated.network.&lt;Device-Name&gt;.&lt;HostID&gt;
+        </code>
+      </td>
+      <td>
+        Total amount of bandwidth free for the scheduler to allocate to tasks on
+        the given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.total</code>
+      </td>
+      <td>Total amount of physical memory on the node</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.available</code>
+      </td>
+      <td>
+        Total amount of memory available to processes which includes free and
+        cached memory
+      </td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.used</code>
+      </td>
+      <td>Amount of memory used by processes</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.free</code>
+      </td>
+      <td>Amount of memory which is free</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.uptime.&lt;HostID&gt;</code>
+      </td>
+      <td>Uptime of the host running the Nomad client</td>
+      <td>Seconds</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.total</code>
+      </td>
+      <td>Total CPU utilization</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.user</code>
+      </td>
+      <td>CPU utilization in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.system
+        </code>
+      </td>
+      <td>CPU utilization in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.idle</code>
+      </td>
+      <td>Idle time spent by the CPU</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.size
+        </code>
+      </td>
+      <td>Total size of the device</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.used
+        </code>
+      </td>
+      <td>Amount of space which has been used</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.available
+        </code>
+      </td>
+      <td>Amount of space which is available</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.used_percent
+        </code>
+      </td>
+      <td>Percentage of disk space used</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.inodes_percent
+        </code>
+      </td>
+      <td>Disk space consumed by the inodes</td>
+      <td>Percent</td>
+      <td>Gauge</td>
+    </tr>
+  </tbody>
+</table>
+
+## Allocation Metrics
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.rss
+        </code>
+      </td>
+      <td>Amount of RSS memory consumed by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.cache
+        </code>
+      </td>
+      <td>Amount of memory cached by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.swap
+        </code>
+      </td>
+      <td>Amount of memory swapped by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.max_usage
+        </code>
+      </td>
+      <td>Maximum amount of memory ever used by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.kernel_usage
+        </code>
+      </td>
+      <td>Amount of memory used by the kernel for this task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.memory.kernel_max_usage
+        </code>
+      </td>
+      <td>Maximum amount of memory ever used by the kernel for this task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.cpu.total_percent
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task across all cores</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.cpu.system
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.cpu.user
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.cpu.throttled_time
+        </code>
+      </td>
+      <td>Total time that the task was throttled</td>
+      <td>Nanoseconds</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.&lt;Job&gt;.&lt;TaskGroup&gt;.&lt;AllocID&gt;.&lt;Task&gt;.cpu.total_ticks
+        </code>
+      </td>
+      <td>CPU ticks consumed by the process in the last collection interval</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+  </tbody>
+</table>
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.job_summary.queued</code>
+      </td>
+      <td>Number of queued allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.complete</code>
+      </td>
+      <td>Number of complete allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.failed</code>
+      </td>
+      <td>Number of failed allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.running</code>
+      </td>
+      <td>Number of running allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.starting</code>
+      </td>
+      <td>Number of starting allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.lost</code>
+      </td>
+      <td>Number of lost allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+  </tbody>
+</table>
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.job_status.pending</code>
+      </td>
+      <td>Number jobs pending</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_status.running</code>
+      </td>
+      <td>Number jobs running</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_status.dead</code>
+      </td>
+      <td>Number of dead jobs</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+  </tbody>
+</table>
+
+## Metric Types
+
+<table>
+  <thead>
+    <tr>
+      <th>Type</th>
+      <th>Description</th>
+      <th>Quantiles</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Gauge</td>
+      <td>
+        Gauge types report an absolute number at the end of the aggregation
+        interval
+      </td>
+      <td>false</td>
+    </tr>
+    <tr>
+      <td>Counter</td>
+      <td>
+        Counts are incremented and flushed at the end of the aggregation
+        interval and then are reset to zero
+      </td>
+      <td>true</td>
+    </tr>
+    <tr>
+      <td>Timer</td>
+      <td>
+        Timers measure the time to complete a task and will include quantiles,
+        means, standard deviation, etc per interval.
+      </td>
+      <td>true</td>
+    </tr>
+  </tbody>
+</table>
+
+## Tagged Metrics
+
+As of version 0.7, Nomad will start emitting metrics in a tagged format. Each
+metric can support more than one tag, meaning that it is possible to do a
+match over metrics for datapoints such as a particular datacenter, and return
+all metrics with this tag. Nomad supports labels for namespaces as well.
+
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
diff --git a/content/nomad/v0.11.x/content/docs/upgrade/index.mdx b/content/nomad/v0.11.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..2f216ba884
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/docs/commands/node/drain) command.
+
+## Done!
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /docs/configuration#data_dir
+[heartbeat_grace]: /docs/configuration/server#heartbeat_grace
+[monitor]: /docs/commands/monitor
+[node-status]: /docs/commands/node/status
+[server-members]: /docs/commands/server/members
+[upgrade-specific]: /docs/upgrade/upgrade-specific
diff --git a/content/nomad/v0.11.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v0.11.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..10d90d36e3
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,645 @@
+---
+layout: docs
+page_title: Upgrade Guides
+sidebar_title: Specific Version Details
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/docs/upgrade) covers the details of doing
+a standard upgrade. However, specific versions of Nomad may have more
+details provided for their upgrades as a result of new features or changed
+behavior. This page is used to document those details separately from the
+standard upgrade flow.
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fixes for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled =
+true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do *not* need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasability (whether a node is capable of running a job at all) is *not*
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1.
+This library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the
+code is available in an external repository,
+[https://github.com/hashicorp/nomad-driver-rkt](https://github.com/hashicorp/nomad-driver-rkt),
+it will not be maintained as `rkt` is [no longer being developed
+upstream](https://github.com/rkt/rkt). We encourage all `rkt` users to find a
+new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fixes for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled =
+true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the
+same-node penalty for allocations that have not previously failed. In
+earlier versions of Nomad, the node where an allocation was running
+was penalized from receiving updated versions of that allocation,
+resulting in a higher chance of the allocation being placed on a new
+node. This was changed so that the penalty only applies to nodes where
+the previous allocation has failed or been rescheduled, to reduce the
+risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that
+are being updated from a healthy state. You can view the placement
+metrics for an allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with TLS][tls-guide]
+guide or the [Vault PKI Secrets Engine Integration][tls-vault-guide] guide
+should already have certificates that will pass validation. Before upgrading to
+Nomad 0.10.3, operators using mTLS with `verify_server_hostname = true` should
+confirm that the common name or SAN of all Nomad client node certs is
+`client.<region>.nomad`, and that the common name or SAN of all Nomad server
+node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][limits] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits stanza is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in
+scheduler preemption since 0.9.0. Users unable to immediately upgrade Nomad can
+[disable preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default
+and adds a default update stanza when a service job is created or updated.
+This does not affect jobs with an update stanza.
+
+In pre-0.10 releases, when updating a service job without an update stanza,
+all existing allocations are stopped while new allocations start up,
+and this may cause a service degradation or an outage.
+You can regain this behavior and disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` stanza][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in handling of job `template` stanzas:
+
+- The client host's environment variables are now cleaned before rendering the template. If a template includes the `env` function, the job should include an [`env`](/docs/job-specification/env) stanza to allow access to the variable in the template.
+- The `plugin` function is no longer permitted by default and will raise an error if used in a template. Operator can opt-in to permitting this function with the new [`template.function_blacklist`](/docs/configuration/client#template-parameters) field in the client configuration.
+- The `file` function has been changed to restrict paths to fall inside the task directory by default. Paths that used the `NOMAD_TASK_DIR` environment variable to prefix file paths should work unchanged. Relative paths or symlinks that point outside the task directory will raise an error. An operator can opt-out of this protection with the new [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters) field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+- Task driver [`config`][task-config] stanzas are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-stanza] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2,
+users will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` stanza. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should
+transition away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a
+previous version of the client after upgrading it to Nomad 0.9 is not supported.
+To downgrade safely, users should erase the Nomad client's data directory.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the
+[`raft_protocol`](/docs/configuration/server#raft_protocol) option
+in their `server` stanza to 1 in order to maintain backwards compatibility with
+the old servers during the upgrade. After the servers have been migrated to
+version 0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted
+to match the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers are
+compatible (for example, version 1 cannot talk to version 3). Here is a table of the
+Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all [Autopilot](https://learn.hashicorp.com/nomad/operating-nomad/autopilot) features, all servers
+in a Nomad cluster must be running with Raft protocol version 3 or later.
+
+#### Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3 in Nomad 0.8 and higher. Raft protocol version 3 requires Nomad running 0.8.0 or newer on all servers in order to work. See [Raft Protocol Version Compatibility](/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility) for more details. Also the format of `peers.json` used for outage recovery is different when running with the latest Raft protocol. See [Manual Recovery Using peers.json](https://learn.hashicorp.com/nomad/operating-nomad/outage#manual-recovery-using-peersjson) for a description of the required format.
+
+Please note that the Raft protocol is different from Nomad's internal protocol as shown in commands like `nomad server members`. To see the version of the Raft protocol in use on each server, use the `nomad operator raft list-peers` command.
+
+The easiest way to upgrade servers is to have each server leave the cluster, upgrade its `raft_protocol` version in the `server` stanza, and then add it back. Make sure the new server joins successfully and that the cluster is stable before rolling the upgrade forward to the next server. It's also possible to stand up a new set of servers, and then slowly stand down each of the older servers in a similar fashion.
+
+When using Raft protocol version 3, servers are identified by their `node-id` instead of their IP address when Nomad makes changes to its internal Raft quorum configuration. This means that once a cluster has been upgraded with servers all running Raft protocol version 3, it will no longer allow servers running any older Raft protocol versions to be added. If running a single Nomad server, restarting it in-place will result in that server not being able to elect itself as a leader. To avoid this, either set the Raft protocol back to 2, or use [Manual Recovery Using peers.json](https://learn.hashicorp.com/nomad/operating-nomad/outage#manual-recovery-using-peersjson) to map the server to its node ID in the Raft quorum configuration.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] stanza in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad
+0.7.1 and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` stanza documentation][migrate] and [Decommissioning Nodes
+guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/docs/job-specification/env) and
+[`template`](/docs/job-specification/template) stanzas.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following stanza:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC
+address](/docs/configuration#rpc-1) has changed to be only used
+to advertise the RPC address of servers to client nodes. Server to server
+communication is done using the advertised Serf address. Existing cluster's
+should not be effected but the advertised RPC address may need to be updated to
+allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/docs/configuration/client#network_interface)
+such that tasks bind to the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[dangling-containers]: /docs/drivers/docker#dangling-containers
+[drain-api]: /api-docs/nodes#drain-node
+[drain-cli]: /docs/commands/node/drain
+[dst]: /docs/job-specification/periodic#daylight-saving-time
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /docs/configuration#limits
+[lxc]: /docs/drivers/external/lxc
+[migrate]: /docs/job-specification/migrate
+[plugin-stanza]: /docs/configuration/plugin
+[plugins]: /docs/drivers/external
+[preemption-api]: /api-docs/operator#update-scheduler-configuration
+[preemption]: /docs/internals/scheduling/preemption
+[reserved]: /docs/configuration/client#reserved-parameters
+[task-config]: /docs/job-specification/task#config
+[tls-guide]: https://learn.hashicorp.com/nomad/transport-security/enable-tls
+[tls-vault-guide]: https://learn.hashicorp.com/nomad/vault-integration/vault-pki-nomad
+[update]: /docs/job-specification/update
+[validate]: /docs/commands/job/validate
+[vault_grace]: /docs/job-specification/template
diff --git a/content/nomad/v0.11.x/content/docs/vault-integration/index.mdx b/content/nomad/v0.11.x/content/docs/vault-integration/index.mdx
new file mode 100644
index 0000000000..6a8b5bd75d
--- /dev/null
+++ b/content/nomad/v0.11.x/content/docs/vault-integration/index.mdx
@@ -0,0 +1,350 @@
+---
+layout: docs
+page_title: Vault Integration
+sidebar_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](https://www.vaultproject.io/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both white-list and blacklist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a whitelist by using `allowed_policies` in the token
+role definition or as a blacklist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the blacklist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The token can then be set in the server configuration's
+[`vault` stanza][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` stanza of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+[auth]: https://www.vaultproject.io/docs/auth/token 'Vault Authentication Backend'
+[config]: /docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: https://www.vaultproject.io/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: https://www.vaultproject.io/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/cluster.mdx b/content/nomad/v0.11.x/content/intro/getting-started/cluster.mdx
new file mode 100644
index 0000000000..88d1be5b21
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/cluster.mdx
@@ -0,0 +1,221 @@
+---
+layout: intro
+page_title: Clustering
+sidebar_title: Clustering
+description: Join another Nomad client to create your first cluster.
+---
+
+# Clustering
+
+We have started our first agent and run a job against it in development mode.
+This demonstrates the ease of use and the workflow of Nomad, but did not show how
+this could be extended to a scalable, production-grade configuration. In this step,
+we will create our first real cluster with multiple nodes.
+
+## Starting the Server
+
+The first step is to create the config file for the server. Either download the
+[file from the repository][server.hcl], or paste this into a file called
+`server.hcl`:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/server1"
+
+# Enable the server
+server {
+    enabled = true
+
+    # Self-elect, should be 3 or 5 for production
+    bootstrap_expect = 1
+}
+```
+
+This is a fairly minimal server configuration file, but it
+is enough to start an agent in server only mode and have it
+elected as a leader. The major change that should be made for
+production is to run more than one server, and to change the
+corresponding `bootstrap_expect` value.
+
+Once the file is created, start the agent in a new tab:
+
+```shell-session
+$ nomad agent -config server.hcl
+==> WARNING: Bootstrap mode enabled! Potentially unsafe operation.
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: false
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+               Version: 0.7.0
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: nomad.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+    [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state
+    [INFO] nomad: adding server nomad.global (Addr: 127.0.0.1:4647) (DC: dc1)
+    [WARN] raft: Heartbeat timeout reached, starting election
+    [INFO] raft: Node at 127.0.0.1:4647 [Candidate] entering Candidate state
+    [DEBUG] raft: Votes needed: 1
+    [DEBUG] raft: Vote granted. Tally: 1
+    [INFO] raft: Election won. Tally: 1
+    [INFO] raft: Node at 127.0.0.1:4647 [Leader] entering Leader state
+    [INFO] nomad: cluster leadership acquired
+    [INFO] raft: Disabling EnableSingleNode (bootstrap)
+    [DEBUG] raft: Node 127.0.0.1:4647 updated peer set (2): [127.0.0.1:4647]
+```
+
+We can see above that client mode is disabled, and that we are
+only running as the server. This means that this server will manage
+state and make scheduling decisions but will not run any tasks.
+Now we need some agents to run tasks!
+
+## Starting the Clients
+
+Similar to the server, we must first configure the clients. Either download
+the configuration for `client1` and `client2` from the
+[repository here](https://github.com/hashicorp/nomad/tree/master/demo/vagrant), or
+paste the following into `client1.hcl`:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/client1"
+
+# Give the agent a unique name. Defaults to hostname
+name = "client1"
+
+# Enable the client
+client {
+    enabled = true
+
+    # For demo assume we are talking to server1. For production,
+    # this should be like "nomad.service.consul:4647" and a system
+    # like Consul used for service discovery.
+    servers = ["127.0.0.1:4647"]
+}
+
+# Modify our port to avoid a collision with server1
+ports {
+    http = 5656
+}
+```
+
+Copy that file to `client2.hcl`. Change the `data_dir` to be `/tmp/client2`,
+the `name` to `client2`, and the `http` port to 5657. Once you have created
+both `client1.hcl` and `client2.hcl`, open a tab for each and start the agents:
+
+```shell-session
+$ sudo nomad agent -config client1.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: false
+               Version: 0.7.0
+
+==> Nomad agent started! Log data will stream in below:
+
+    [DEBUG] client: applied fingerprints [host memory storage arch cpu]
+    [DEBUG] client: available drivers [docker exec]
+    [DEBUG] client: node registration complete
+    ...
+```
+
+In the output we can see the agent is running in client mode only.
+This agent will be available to run tasks but will not participate
+in managing the cluster or making scheduling decisions.
+
+Using the [`node status` command](/docs/commands/node/status)
+we should see both nodes in the `ready` state:
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+fca62612  dc1  client1  <none>  false  eligible     ready
+c887deef  dc1  client2  <none>  false  eligible     ready
+```
+
+We now have a simple three node cluster running. The only difference
+between a demo and full production cluster is that we are running a
+single server instead of three or five.
+
+## Submit a Job
+
+Now that we have a simple cluster, we can use it to schedule a job.
+We should still have the `example.nomad` job file from before, but
+verify that the `count` is still set to 3.
+
+Then, use the [`job run` command](/docs/commands/job/run) to submit the job:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "8e0a7cf9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "0917b771"
+    Allocation "501154ac" created: node "c887deef", group "cache"
+    Allocation "7e2b3900" created: node "fca62612", group "cache"
+    Allocation "9c66fcaf" created: node "c887deef", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8e0a7cf9" finished with status "complete"
+```
+
+We can see in the output that the scheduler assigned two of the
+tasks for one of the client nodes and the remaining task to the
+second client.
+
+We can again use the [`status` command](/docs/commands/status) to verify:
+
+```shell-session
+$ nomad status example
+ID          = example
+Name        = example
+Submit Date   = 07/26/17 16:34:58 UTC
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+
+Latest Deployment
+ID          = fc49bd6c
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        3       0        0
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status   Created At
+501154ac  8e0a7cf9  c887deef  cache       run      running  08/08/16 21:03:19 CDT
+7e2b3900  8e0a7cf9  fca62612  cache       run      running  08/08/16 21:03:19 CDT
+9c66fcaf  8e0a7cf9  c887deef  cache       run      running  08/08/16 21:03:19 CDT
+```
+
+We can see that all our tasks have been allocated and are running.
+Once we are satisfied that our job is happily running, we can tear
+it down with `nomad job stop`.
+
+## Next Steps
+
+Nomad is now up and running. The cluster can be entirely managed from the command line,
+but Nomad also comes with a web interface that is hosted alongside the HTTP API.
+Next, we'll [visit the UI in the browser](/intro/getting-started/ui).
+
+[server.hcl]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/server.hcl
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/index.mdx b/content/nomad/v0.11.x/content/intro/getting-started/index.mdx
new file mode 100644
index 0000000000..a9fff53359
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: intro
+page_title: Install Nomad
+sidebar_title: Getting Started
+description: The first step to using Nomad is to get it installed.
+---
+
+# Install Nomad
+
+To simplify the getting started experience, you can download the pre-compiled
+binary and run it directly (see the instructions [here][binary-instructions]) or
+you can optionally work in a Vagrant environment (detailed in the following
+section).
+
+## Vagrant Setup (Optional)
+
+Note: To use the Vagrant Setup first install Vagrant following these
+[instructions][install-instructions].
+
+Create a new directory, and download [this
+`Vagrantfile`](https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile).
+
+Once you have created a new directory and downloaded the `Vagrantfile` you must
+create the virtual machine:
+
+```shell-session
+$ vagrant up
+```
+
+This will take a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see output similar to:
+
+```text
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-16.04'...
+...
+==> default: Running provisioner: docker...
+
+```
+
+At this point the Vagrant box is running and ready to go.
+
+## Verifying the Installation
+
+After starting the Vagrant box, verify the installation worked by connecting
+to the box using SSH and checking that `nomad` is available. By executing
+`nomad`, you should see help output similar to the following:
+
+```shell-session
+$ vagrant ssh
+...
+
+vagrant@nomad:~$ nomad
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+If you get an error that Nomad could not be found, then your Vagrant box
+may not have provisioned correctly. Check for any error messages that may have
+been emitted during `vagrant up`. You can always [destroy the box][destroy] and
+re-create it.
+
+## Next Steps
+
+Nomad is installed. Let's [start Nomad](/intro/getting-started/running)!
+
+[binary-instructions]: /docs/install#precompiled-binaries
+[destroy]: https://www.vagrantup.com/docs/cli/destroy.html
+[install-instructions]: https://www.vagrantup.com/docs/installation/
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/jobs.mdx b/content/nomad/v0.11.x/content/intro/getting-started/jobs.mdx
new file mode 100644
index 0000000000..a61a6dadfa
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/jobs.mdx
@@ -0,0 +1,345 @@
+---
+layout: intro
+page_title: Jobs
+sidebar_title: Jobs
+description: 'Learn how to submit, modify and stop jobs in Nomad.'
+---
+
+# Jobs
+
+Jobs are the primary configuration that users interact with when using
+Nomad. A job is a declarative specification of tasks that Nomad should run.
+Jobs have a globally unique name, one or many task groups, which are themselves
+collections of one or many tasks.
+
+The format of the jobs is documented in the [job specification][jobspec]. They
+can either be specified in [HashiCorp Configuration Language][hcl] or JSON,
+however we recommend only using JSON when the configuration is generated by a machine.
+
+## Running a Job
+
+To get started, we will use the [`job init` command](/docs/commands/job/init) which
+generates a skeleton job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+You can view the contents of this file by running `cat example.nomad`. In this
+example job file, we have declared a single task 'redis' which is using
+the Docker driver to run the task. The primary way you interact with Nomad
+is with the [`job run` command](/docs/commands/job/run). The `run` command takes
+a job file and registers it with Nomad. This is used both to register new
+jobs and to update existing jobs.
+
+We can register our example job now:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "13ebb66d"
+    Evaluation triggered by job "example"
+    Allocation "883269bf" created: node "e42d6f19", group "cache"
+    Evaluation within deployment: "b0a84e74"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "13ebb66d" finished with status "complete"
+```
+
+Anytime a job is updated, Nomad creates an evaluation to determine what
+actions need to take place. In this case, because this is a new job, Nomad has
+determined that an allocation should be created and has scheduled it on our
+local agent.
+
+To inspect the status of our job we use the [`status` command](/docs/commands/status):
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 10/31/17 22:58:40 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = b0a84e74
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+8ba85cef  171a583b  cache       0        run      running  5m ago   5m ago
+```
+
+Here we can see that the result of our evaluation was the creation of an
+allocation that is now running on the local node.
+
+An allocation represents an instance of Task Group placed on a node. To inspect
+an allocation we use the [`alloc status` command](/docs/commands/alloc/status):
+
+```shell-session
+$ nomad alloc status 8ba85cef
+ID                  = 8ba85cef
+Eval ID             = 13ebb66d
+Name                = example.cache[0]
+Node ID             = e42d6f19
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created             = 5m ago
+Modified            = 5m ago
+Deployment ID       = fa882a5b
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+8/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:22672
+
+Task Events:
+Started At     = 10/31/17 22:58:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+10/31/17 22:58:49 UTC  Started     Task started by client
+10/31/17 22:58:40 UTC  Driver      Downloading image redis:3.2
+10/31/17 22:58:40 UTC  Task Setup  Building Task Directory
+10/31/17 22:58:40 UTC  Received    Task received by client
+```
+
+We can see that Nomad reports the state of the allocation as well as its
+current resource usage. By supplying the `-stats` flag, more detailed resource
+usage statistics will be reported.
+
+To see the logs of a task, we can use the [`logs` command](/docs/commands/alloc/logs):
+
+````shell-session
+$ nomad alloc logs 8ba85cef redis
+                 _._
+            _.-``__ ''-._
+       _.-``    `.  `_.  ''-._           Redis 3.2.1 (00000000/0) 64 bit
+   .-`` .-```.  ```\/    _.,_ ''-._
+  (    '      ,       .-`  | `,    )     Running in standalone mode
+  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
+  |    `-._   `._    /     _.-'    |     PID: 1
+   `-._    `-._  `-./  _.-'    _.-'
+  |`-._`-._    `-.__.-'    _.-'_.-'|
+  |    `-._`-._        _.-'_.-'    |           http://redis.io
+   `-._    `-._`-.__.-'_.-'    _.-'
+  |`-._`-._    `-.__.-'    _.-'_.-'|
+  |    `-._`-._        _.-'_.-'    |
+   `-._    `-._`-.__.-'_.-'    _.-'
+       `-._    `-.__.-'    _.-'
+           `-._        _.-'
+               `-.__.-'
+...
+````
+
+## Modifying a Job
+
+The definition of a job is not static, and is meant to be updated over time.
+You may update a job to change the docker container, to update the application version,
+or to change the count of a task group to scale with load.
+
+For now, edit the `example.nomad` file to update the count and set it to 3:
+
+```
+# The "count" parameter specifies the number of the task groups that should
+# be running under this group. This value must be non-negative and defaults
+# to 1.
+count = 3
+```
+
+Once you have finished modifying the job specification, use the [`job plan`
+command](/docs/commands/job/plan) to invoke a dry-run of the scheduler to see
+what would happen if you ran the updated job:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (2 create, 1 in-place update)
+  +/- Count: "1" => "3" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+We can see that the scheduler detected the change in count and informs us that
+it will cause 2 new instances to be created. The in-place update that will
+occur is to push the updated job specification to the existing allocation and
+will not cause any service interruption. We can then run the job with the run
+command the `plan` emitted.
+
+By running with the `-check-index` flag, Nomad checks that the job has not
+been modified since the plan was run. This is useful if multiple people are
+interacting with the job at the same time to ensure the job hasn't changed
+before you apply your modifications.
+
+```shell-session
+$ nomad job run -check-index 7 example.nomad
+==> Monitoring evaluation "93d16471"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "0d06e1b6"
+    Allocation "3249e320" created: node "e42d6f19", group "cache"
+    Allocation "453b210f" created: node "e42d6f19", group "cache"
+    Allocation "883269bf" modified: node "e42d6f19", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "93d16471" finished with status "complete"
+```
+
+Because we set the count of the task group to three, Nomad created two
+additional allocations to get to the desired state. It is idempotent to
+run the same job specification again and no new allocations will be created.
+
+Now, let's try to do an application update. In this case, we will simply change
+the version of redis we want to run. Edit the `example.nomad` file and change
+the Docker image from "redis:3.2" to "redis:4.0":
+
+```
+# Configure Docker driver with the image
+config {
+    image = "redis:4.0"
+}
+```
+
+We can run `plan` again to see what will happen if we submit this change:
+
+```text
++/- Job: "example"
++/- Task Group: "cache" (1 create/destroy update, 2 ignore)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 1127
+To submit the job with version verification run:
+
+nomad job run -check-index 1127 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+The plan output shows us that one allocation will be updated and that the other
+two will be ignored. This is due to the `max_parallel` setting in the `update`
+stanza, which is set to 1 to instruct Nomad to perform only a single change at
+a time.
+
+Once ready, use `run` to push the updated specification:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "293b313a"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "f4047b3a"
+    Allocation "27bd4a41" created: node "e42d6f19", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "293b313a" finished with status "complete"
+```
+
+After running, the rolling upgrade can be followed by running `nomad status` and
+watching the deployed count.
+
+We can see that Nomad handled the update in three phases, only updating a single
+allocation in each phase and waiting for it to be healthy for `min_healthy_time`
+of 10 seconds before moving on to the next. The update strategy can be
+configured, but rolling updates makes it easy to upgrade an application at large
+scale.
+
+## Stopping a Job
+
+So far we've created, run and modified a job. The final step in a job lifecycle
+is stopping the job. This is done with the [`job stop` command](/docs/commands/job/stop):
+
+```shell-session
+$ nomad job stop example
+==> Monitoring evaluation "6d4cd6ca"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "f4047b3a"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6d4cd6ca" finished with status "complete"
+```
+
+When we stop a job, it creates an evaluation which is used to stop all
+the existing allocations. If we now query the job status, we can see it is
+now marked as `dead (stopped)`, indicating that the job has been stopped and
+Nomad is no longer running it:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 11/01/17 17:30:40 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = dead (stopped)
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         0        0       6         0
+
+Latest Deployment
+ID          = f4047b3a
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        3       3        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+8ace140d  2cfe061e  cache       2        stop     complete  5m ago     5m ago
+8af5330a  2cfe061e  cache       2        stop     complete  6m ago     6m ago
+df50c3ae  2cfe061e  cache       2        stop     complete  6m ago     6m ago
+```
+
+If we wanted to start the job again, we could simply `run` it again.
+
+## Next Steps
+
+Users of Nomad primarily interact with jobs, and we've now seen
+how to create and scale our job, perform an application update,
+and do a job tear down. Next we will add another Nomad
+client to [create our first cluster](/intro/getting-started/cluster)
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/next-steps.mdx b/content/nomad/v0.11.x/content/intro/getting-started/next-steps.mdx
new file mode 100644
index 0000000000..9be8741103
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/next-steps.mdx
@@ -0,0 +1,32 @@
+---
+layout: intro
+page_title: Next Steps
+sidebar_title: Next Steps
+description: >-
+  After completing the getting started guide, learn about what to do next with
+  Nomad.
+---
+
+# Next Steps
+
+That concludes the getting started guide for Nomad. Hopefully you are
+excited about the possibilities of Nomad and ready to put this knowledge
+to use to improve your environment.
+
+We've covered the basics of all the core features of Nomad in this guide.
+We recommend exploring the following resources as next steps.
+
+- [HashiCorp Learn Guides](http://learn/hashicorp.com/nomad) - The Guides provide best practices and
+  guidance for using and operating Nomad in a real-world production setting.
+
+- [Docs](/docs) - The Docs provide detailed reference information
+  all available features and options of Nomad.
+
+- [Job Lifecycle](https://learn.hashicorp.com/nomad?track=managing-jobs#operations-and-development) - Additional details
+  specific to running a job in production.
+
+- [Creating a Cluster](https://learn.hashicorp.com/nomad/operating-nomad/clustering) - Additional
+  details on creating a production worthy Nomad Cluster.
+
+- [Example Terraform configuration](https://github.com/hashicorp/nomad/tree/master/terraform) -
+  Use Terraform to automatically provision a cluster in AWS.
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/running.mdx b/content/nomad/v0.11.x/content/intro/getting-started/running.mdx
new file mode 100644
index 0000000000..b722e423be
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/running.mdx
@@ -0,0 +1,145 @@
+---
+layout: intro
+page_title: Running Nomad
+sidebar_title: Running Nomad
+description: 'Learn about the Nomad agent, and the lifecycle of running and stopping.'
+---
+
+# Running Nomad
+
+Nomad relies on a long running agent on every machine in the cluster.
+The agent can run either in server or client mode. Each region must
+have at least one server, though a cluster of 3 or 5 servers is recommended.
+A single server deployment is _**highly**_ discouraged as data loss is inevitable
+in a failure scenario.
+
+All other agents run in client mode. A Nomad client is a very lightweight
+process that registers the host machine, performs heartbeating, and runs the tasks
+that are assigned to it by the servers. The agent must be run on every node that
+is part of the cluster so that the servers can assign work to those machines.
+
+## Starting the Agent
+
+For simplicity, we will run a single Nomad agent in development mode. This mode
+is used to quickly start an agent that is acting as a client and server to test
+job configurations or prototype interactions. It should _**not**_ be used in
+production as it does not persist state.
+
+```shell-session
+$ sudo nomad agent -dev
+
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: nomad.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+    [INFO] client: using alloc directory /tmp/NomadClient599911093
+    [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state
+    [INFO] nomad: adding server nomad.global (Addr: 127.0.0.1:4647) (DC: dc1)
+    [WARN] fingerprint.network: Ethtool not found, checking /sys/net speed file
+    [WARN] raft: Heartbeat timeout reached, starting election
+    [INFO] raft: Node at 127.0.0.1:4647 [Candidate] entering Candidate state
+    [DEBUG] raft: Votes needed: 1
+    [DEBUG] raft: Vote granted. Tally: 1
+    [INFO] raft: Election won. Tally: 1
+    [INFO] raft: Node at 127.0.0.1:4647 [Leader] entering Leader state
+    [INFO] raft: Disabling EnableSingleNode (bootstrap)
+    [DEBUG] raft: Node 127.0.0.1:4647 updated peer set (2): [127.0.0.1:4647]
+    [INFO] nomad: cluster leadership acquired
+    [DEBUG] client: applied fingerprints [arch cpu host memory storage network]
+    [DEBUG] client: available drivers [docker exec java]
+    [DEBUG] client: node registration complete
+    [DEBUG] client: updated allocations at index 1 (0 allocs)
+    [DEBUG] client: allocs: (added 0) (removed 0) (updated 0) (ignore 0)
+    [DEBUG] client: state updated to ready
+```
+
+As you can see, the Nomad agent has started and has output some log
+data. From the log data, you can see that our agent is running in both
+client and server mode, and has claimed leadership of the cluster.
+Additionally, the local client has been registered and marked as ready.
+
+-> **Note:** Typically any agent running in client mode must be run with root level
+privilege. Nomad makes use of operating system primitives for resource isolation
+which require elevated permissions. The agent will function as non-root, but
+certain task drivers will not be available.
+
+## Cluster Nodes
+
+If you run [`nomad node status`](/docs/commands/node/status) in another
+terminal, you can see the registered nodes of the Nomad cluster:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+171a583b  dc1  nomad  <none>  false  eligible     ready
+```
+
+The output shows our Node ID, which is a randomly generated UUID,
+its datacenter, node name, node class, drain mode and current status.
+We can see that our node is in the ready state, and task draining is
+currently off.
+
+The agent is also running in server mode, which means it is part of
+the [gossip protocol](/docs/internals/gossip) used to connect all
+the server instances together. We can view the members of the gossip
+ring using the [`server members`](/docs/commands/server/members) command:
+
+```shell-session
+$ nomad server members
+Name          Address    Port  Status  Leader  Protocol  Build  Datacenter  Region
+nomad.global  127.0.0.1  4648  alive   true    2         0.7.0  dc1         global
+```
+
+The output shows our own agent, the address it is running on, its
+health state, some version information, and the datacenter and region.
+Additional metadata can be viewed by providing the `-detailed` flag.
+
+## Stopping the Agent ((#stopping))
+
+You can use `Ctrl-C` (the interrupt signal) to halt the agent.
+By default, all signals will cause the agent to forcefully shutdown.
+The agent [can be configured](/docs/configuration#leave_on_terminate) to
+gracefully leave on either the interrupt or terminate signals.
+
+After interrupting the agent, you should see it leave the cluster
+and shut down:
+
+```
+^C==> Caught signal: interrupt
+    [DEBUG] http: Shutting down http server
+    [INFO] agent: requesting shutdown
+    [INFO] client: shutting down
+    [INFO] nomad: shutting down server
+    [WARN] serf: Shutdown without a Leave
+    [INFO] agent: shutdown complete
+```
+
+By gracefully leaving, Nomad clients update their status to prevent
+further tasks from being scheduled and to start migrating any tasks that are
+already assigned. Nomad servers notify their peers they intend to leave.
+When a server leaves, replication to that server stops. If a server fails,
+replication continues to be attempted until the node recovers. Nomad will
+automatically try to reconnect to _failed_ nodes, allowing it to recover from
+certain network conditions, while _left_ nodes are no longer contacted.
+
+If an agent is operating as a server, [`leave_on_terminate`](/docs/configuration#leave_on_terminate) should only
+be set if the server will never rejoin the cluster again. The default value of `false` for `leave_on_terminate` and `leave_on_interrupt`
+work well for most scenarios. If Nomad servers are part of an auto scaling group where new servers are brought up to replace
+failed servers, using graceful leave avoids causing a potential availability outage affecting the [consensus protocol](/docs/internals/consensus).
+As of Nomad 0.8, Nomad includes Autopilot which automatically removes failed or dead servers. This allows the operator to skip setting `leave_on_terminate`.
+
+If a server does forcefully exit and will not be returning into service, the
+[`server force-leave` command](/docs/commands/server/force-leave) should
+be used to force the server from a _failed_ to a _left_ state.
+
+## Next Steps
+
+If you shut down the development Nomad agent as instructed above, ensure that it is back up and running again and let's try to [run a job](/intro/getting-started/jobs)!
diff --git a/content/nomad/v0.11.x/content/intro/getting-started/ui.mdx b/content/nomad/v0.11.x/content/intro/getting-started/ui.mdx
new file mode 100644
index 0000000000..bb4a499746
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/getting-started/ui.mdx
@@ -0,0 +1,63 @@
+---
+layout: intro
+page_title: Web UI
+sidebar_title: Web UI
+description: 'Visit the Nomad Web UI to inspect jobs, allocations, and more.'
+---
+
+# Web UI
+
+At this point we have a fully functioning cluster with a job running in it. We have
+learned how to inspect a job using `nomad status`, next we'll learn how to inspect
+a job in the web client.
+
+## Opening the Web UI
+
+As long as Nomad is running, the Nomad UI is also running. It is hosted at the same address
+and port as the Nomad HTTP API under the `/ui` namespace.
+
+With Nomad running, visit `http://localhost:4646` to open the Nomad UI.
+
+[![Nomad UI Jobs List][img-jobs-list]][img-jobs-list]
+
+If you can't connect it's possible that Vagrant was unable to properly map the
+port from your host to the VM. Your `vagrant up` output will contain the new
+port mapping:
+
+```text
+==> default: Fixed port collision for 4646 => 4646. Now on port 2200.
+```
+
+In the case above you would connect to `http://localhost:2200` instead.
+
+## Inspecting a Job
+
+You should be automatically redirected to `/ui/jobs` upon visiting the UI in your browser. This
+pages lists all jobs known to Nomad, regardless of status. Click the `example` job to inspect it.
+
+[![Nomad UI Job Detail][img-job-detail]][img-job-detail]
+
+The job detail page shows pertinent information about the job, including overall status as well as
+allocation statuses broken down by task group. It is similar to the `nomad status` CLI command.
+
+Click on the `cache` task group to drill into the task group detail page. This page lists each allocation
+for the task group.
+
+[![Nomad UI Task Group Detail][img-task-group-detail]][img-task-group-detail]
+
+Click on the allocation in the allocations table. This page lists all tasks for an allocation as well
+as the recent events for each task. It is similar to the `nomad alloc status` command.
+
+[![Nomad UI Alloc Status][img-alloc-status]][img-alloc-status]
+
+The Nomad UI offers a friendly and visual alternative experience to the CLI.
+
+## Next Steps
+
+We've now concluded the getting started guide, however there are a number
+of [next steps](/intro/getting-started/next-steps) to get started with Nomad.
+
+[img-jobs-list]: /img/intro-ui-jobs-list.png
+[img-job-detail]: /img/intro-ui-job-detail.png
+[img-task-group-detail]: /img/intro-ui-task-group-detail.png
+[img-alloc-status]: /img/intro-ui-alloc-status.png
diff --git a/content/nomad/v0.11.x/content/intro/index.mdx b/content/nomad/v0.11.x/content/intro/index.mdx
new file mode 100644
index 0000000000..6af8cf4750
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/index.mdx
@@ -0,0 +1,57 @@
+---
+layout: intro
+page_title: Introduction
+sidebar_title: What is Nomad?
+description: >-
+  Welcome to the intro guide to Nomad! This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad! This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/docs) and [HashiCorp Learn guides](https://learn.hashicorp.com/nomad) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/intro/use-cases) and [Who Uses Nomad](/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v0.11.x/content/intro/use-cases.mdx b/content/nomad/v0.11.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..2512e4c77f
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/use-cases.mdx
@@ -0,0 +1,67 @@
+---
+layout: intro
+page_title: Use Cases
+sidebar_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker)
+and integrates seamlessly with [Consul](/docs/integrations/consul-integration)
+and [Vault](/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utlization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs, [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs, and [Spark](https://github.com/hashicorp/nomad-spark)
+workloads. Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v0.11.x/content/intro/vs/ecs.mdx b/content/nomad/v0.11.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..47006274e2
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+sidebar_title: AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v0.11.x/content/intro/vs/index.mdx b/content/nomad/v0.11.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..c75add3cbe
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/vs/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+sidebar_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v0.11.x/content/intro/vs/kubernetes.mdx b/content/nomad/v0.11.x/content/intro/vs/kubernetes.mdx
new file mode 100644
index 0000000000..ff6938ac91
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/vs/kubernetes.mdx
@@ -0,0 +1,39 @@
+---
+layout: intro
+page_title: Nomad vs. Kubernetes
+sidebar_title: Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native
+Computing Foundation (CNCF) and developed by Google, Red Hat, CoreOS and many others. Kubernetes aims to provide all the features needed to run Docker or Rkt-based applications including cluster management,
+scheduling, service discovery, monitoring, secrets management and more.
+
+Nomad only aims to provide cluster management and scheduling and is designed
+with the Unix philosophy of having a small scope while composing with tools like [Consul](https://www.consul.io)
+for service discovery and [Vault](https://www.vaultproject.io) for secret management.
+
+While Kubernetes is specifically focused on Docker, Nomad is more general purpose.
+Nomad supports virtualized, containerized and standalone applications, including Docker.
+Nomad is designed with extensible drivers and support will be extended to all
+common drivers.
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating
+services which together provide the full functionality. Coordination and
+storage is provided by etcd at the core. The state is wrapped by API controllers
+which are consumed by other services that provide higher level APIs for features
+like scheduling. Kubernetes supports running in a highly available
+configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines a lightweight resource manager and a sophisticated scheduler
+into a single system. By default, Nomad is distributed, highly available,
+and operationally simple.
+
+Kubernetes documentation states they can support clusters greater than 5,000 nodes
+and they support a multi-AZ/multi-region configuration. Nomad has been proven to scale
+to cluster sizes that exceed 10,000 nodes in real-world production environments. Nomad
+also natively supports multi-datacenter and multi-region configurations.
diff --git a/content/nomad/v0.11.x/content/intro/vs/mesos.mdx b/content/nomad/v0.11.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..6d957ab418
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,36 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+sidebar_title: Mesos & Marathon
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v0.11.x/content/intro/vs/terraform.mdx b/content/nomad/v0.11.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..e1a2f839ee
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,32 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+sidebar_title: Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v0.11.x/content/intro/who-uses-nomad.mdx b/content/nomad/v0.11.x/content/intro/who-uses-nomad.mdx
new file mode 100644
index 0000000000..d60db68319
--- /dev/null
+++ b/content/nomad/v0.11.x/content/intro/who-uses-nomad.mdx
@@ -0,0 +1,114 @@
+---
+layout: intro
+page_title: Who Uses Nomad
+sidebar_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Pandora
+
+- [How Pandora Uses Nomad](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### SeatGeek
+
+- [Nomad Helper Tools](https://github.com/seatgeek/nomad-helper)
+
+#### Spaceflight Industries
+
+- [Spaceflight’s Hub-And-Spoke Infrastructure](https://www.hashicorp.com/blog/spaceflight-uses-hashicorp-consul-for-service-discovery-and-real-time-updates-to-their-hub-and-spoke-network-architecture)
+
+#### SpotInst
+
+- [SpotInst and HashiCorp Nomad to Reduce EC2 Costs for Users](https://www.hashicorp.com/blog/spotinst-and-hashicorp-nomad-to-reduce-ec2-costs-fo)
+
+#### Target
+
+- [Nomad at Target: Scaling Microservices Across Public and Private Clouds](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes](https://matthias-endler.de/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Roblox
+
+- [How Roblox runs a platform for 70 million gamers on HashiCorp Nomad](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay: A Fully Containerized Platform Based on Infrastructure as Code](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Joyent
+
+- [Build Your Own Autoscaling Feature with HashiCorp Nomad](https://www.hashicorp.com/resources/autoscaling-hashicorp-nomad)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### Q2Ebanking
+
+- [Q2’s Nomad Use and Overview](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+#### Region Syddanmark
+
+...and more!
diff --git a/content/nomad/v0.11.x/content/partials/envvars.mdx b/content/nomad/v0.11.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..02861416f0
--- /dev/null
+++ b/content/nomad/v0.11.x/content/partials/envvars.mdx
@@ -0,0 +1,249 @@
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_DIR</code>
+      </td>
+      <td>
+        The path to the shared <code>alloc/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">
+          here for more
+        </a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_DIR</code>
+      </td>
+      <td>
+        The path to the task <code>local/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_SECRETS_DIR</code>
+      </td>
+      <td>
+        Path to the task's secrets directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_MEMORY_LIMIT</code>
+      </td>
+      <td>Memory limit in MB for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_CPU_LIMIT</code>
+      </td>
+      <td>CPU limit in MHz for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_ID</code>
+      </td>
+      <td>Allocation ID of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_NAME</code>
+      </td>
+      <td>Allocation name of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_INDEX</code>
+      </td>
+      <td>
+        Allocation index; useful to distinguish instances of task groups. From 0
+        to (count - 1). The index is unique within a given version of a job, but
+        canaries or failed tasks in a deployment may reuse the index.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_NAME</code>
+      </td>
+      <td>Task's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_GROUP_NAME</code>
+      </td>
+      <td>Group's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_NAME</code>
+      </td>
+      <td>Job's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_DC</code>
+      </td>
+      <td>Datacenter in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_NAMESPACE</code>
+      </td>
+      <td>Namespace in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_REGION</code>
+      </td>
+      <td>Region in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_META_&lt;key&gt;</code>
+      </td>
+      <td>
+        The metadata value given by <code>key</code> on the task's metadata.
+        Note that this is different from
+        <a href="/docs/runtime/interpolation#node-variables-">
+          <code>$&#123;meta.&lt;key&gt;&#125;</code>
+        </a>
+        which are keys in the node's metadata.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>VAULT_TOKEN</code>
+      </td>
+      <td>
+        The task's Vault token. See
+        <a href="/docs/vault-integration">Vault Integration</a>
+        for more details
+      </td>
+    </tr>
+    <tr>
+      <th colspan="2">Network-related Variables</th>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code>. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code>. Driver-specified port when a
+        port map is used, otherwise the host's static or dynamic port
+        allocation. Services should bind to this port. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code>. See
+        <a href="/docs/job-specification/network#mapped-ports">here</a> for more
+        information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group. Driver-specified port when a port map is
+        used, otherwise the host's static or dynamic port allocation. Services
+        should bind to this port.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code> and
+        <code>task</code> for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code> and <code>task</code>
+        for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_IP_&lt;service&gt;</code>
+      </td>
+      <td>
+        IP for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_PORT_&lt;service&gt;</code>
+      </td>
+      <td>
+        Port for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> for the given <code>service</code> when
+        defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ENVOY_ADMIN_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Local address <code>localhost:Port</code> for the admin port of the
+        envoy sidecar for the given <code>service</code> when defined as a
+        Consul Connect enabled service.
+      </td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v0.11.x/content/partials/general_options.mdx b/content/nomad/v0.11.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..7ae431c4f5
--- /dev/null
+++ b/content/nomad/v0.11.x/content/partials/general_options.mdx
@@ -0,0 +1,35 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v0.11.x/data/alert-banner.js b/content/nomad/v0.11.x/data/alert-banner.js
new file mode 100644
index 0000000000..cd49de104d
--- /dev/null
+++ b/content/nomad/v0.11.x/data/alert-banner.js
@@ -0,0 +1,10 @@
+export const ALERT_BANNER_ACTIVE = true
+
+// https://github.com/hashicorp/web-components/tree/master/packages/alert-banner
+export default {
+  url:
+    'https://www.nomadproject.io/downloads/',
+  tag: 'NEW',
+  text:
+    'Nomad 0.11 is now generally available, with CSI integration, autoscaling, and more. Download now',
+}
diff --git a/content/nomad/v0.11.x/data/api-docs-nav-data.json b/content/nomad/v0.11.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..0f37dfb664
--- /dev/null
+++ b/content/nomad/v0.11.x/data/api-docs-nav-data.json
@@ -0,0 +1,112 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "path": "operator"
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies <sup>Beta</sup>",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v0.11.x/data/docs-nav-data.json b/content/nomad/v0.11.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..1f71a0c719
--- /dev/null
+++ b/content/nomad/v0.11.x/data/docs-nav-data.json
@@ -0,0 +1,954 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/quickstart"
+          }
+        ]
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Hardware Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Set Server & Client Nodes",
+            "path": "install/production/nomad-agent"
+          },
+          {
+            "title": "Reference Architecture",
+            "path": "install/production/reference-architecture"
+          },
+          {
+            "title": "Reference Install Guide",
+            "path": "install/production/deployment-guide"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Connect",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Internals",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "internals"
+      },
+      {
+        "title": "Architecture",
+        "path": "internals/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "internals/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "internals/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "internals/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "internals/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/scheduling"
+          },
+          {
+            "title": "Internals",
+            "path": "internals/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "internals/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "internals/consensus"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "internals/gossip"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          }
+        ]
+      },
+      {
+        "title": "eval status",
+        "path": "commands/eval-status"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "autopilot get-config",
+            "path": "commands/operator/autopilot-get-config"
+          },
+          {
+            "title": "autopilot set-config",
+            "path": "commands/operator/autopilot-set-config"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "raft list-peers",
+            "path": "commands/operator/raft-list-peers"
+          },
+          {
+            "title": "raft remove-peer",
+            "path": "commands/operator/raft-remove-peer"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin <sup>Beta</sup>",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling <sup>Beta</sup>",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Qemu",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/external"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/external/lxc"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/external/rkt"
+          },
+          {
+            "title": "Podman",
+            "path": "drivers/external/podman"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/external/singularity"
+          },
+          {
+            "title": "Jailtask driver",
+            "path": "drivers/external/jail-task-driver"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/external/pot"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/external/firecracker-task-driver"
+          },
+          {
+            "title": "Systemd-Nspawn",
+            "path": "drivers/external/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/external/iis"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "path": "devices/community"
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Telemetry",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "telemetry"
+      },
+      {
+        "title": "Metrics",
+        "path": "telemetry/metrics"
+      }
+    ]
+  },
+  {
+    "title": "Vault Integration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
\ No newline at end of file
diff --git a/content/nomad/v0.11.x/data/guides-navigation.js b/content/nomad/v0.11.x/data/guides-navigation.js
new file mode 100644
index 0000000000..aea152ecbf
--- /dev/null
+++ b/content/nomad/v0.11.x/data/guides-navigation.js
@@ -0,0 +1,100 @@
+// The root folder for this documentation category is `pages/guides`
+//
+// - A string refers to the name of a file
+// - A "category" value refers to the name of a directory
+// - All directories must have an "index.mdx" file to serve as
+//   the landing page for the category
+
+export default [
+  {
+    category: 'install',
+    content: [
+      { category: 'quickstart' },
+      {
+        category: 'production',
+        content: [
+          'requirements',
+          'nomad-agent',
+          'reference-architecture',
+          'deployment-guide'
+        ]
+      },
+      'windows-service'
+    ]
+  },
+  { category: 'upgrade', content: ['upgrade-specific'] },
+  {
+    category: 'integrations',
+    content: ['consul-integration', 'consul-connect', 'vault-integration']
+  },
+  '-----------',
+  {
+    category: 'operating-a-job',
+    content: [
+      'configuring-tasks',
+      'submitting-jobs',
+      'inspecting-state',
+      'accessing-logs',
+      'resource-utilization',
+      {
+        category: 'update-strategies',
+        content: [
+          'rolling-upgrades',
+          'blue-green-and-canary-deployments',
+          'handling-signals'
+        ]
+      },
+      {
+        category: 'failure-handling-strategies',
+        content: ['restart', 'check-restart', 'reschedule']
+      },
+      {
+        category: 'advanced-scheduling',
+        content: ['affinity', 'spread', 'preemption-service-batch']
+      },
+      { category: 'external', content: ['lxc'] }
+    ]
+  },
+  {
+    category: 'operations',
+    content: [
+      {
+        category: 'cluster',
+        content: ['manual', 'automatic', 'cloud_auto_join']
+      },
+      'federation',
+      'node-draining',
+      'outage',
+      { category: 'monitoring-and-alerting', content: ['prometheus-metrics'] },
+      'autopilot'
+    ]
+  },
+
+  {
+    category: 'security',
+    content: ['encryption', 'acl', 'securing-nomad', 'vault-pki-integration']
+  },
+  { category: 'stateful-workloads' },
+  {
+    category: 'analytical-workloads',
+    content: [
+      {
+        category: 'spark',
+        content: [
+          'pre',
+          'customizing',
+          'resource',
+          'dynamic',
+          'submit',
+          'hdfs',
+          'monitoring',
+          'configuration'
+        ]
+      }
+    ]
+  },
+
+  { category: 'load-balancing' },
+  { category: 'governance-and-policy', content: [] },
+  { category: 'web-ui', content: [] }
+]
diff --git a/content/nomad/v0.11.x/data/intro-nav-data.json b/content/nomad/v0.11.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..50d1264416
--- /dev/null
+++ b/content/nomad/v0.11.x/data/intro-nav-data.json
@@ -0,0 +1,64 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "Kubernetes",
+        "path": "kubernetes"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "getting-started"
+      },
+      {
+        "title": "Running Nomad",
+        "path": "getting-started/running"
+      },
+      {
+        "title": "Jobs",
+        "path": "getting-started/jobs"
+      },
+      {
+        "title": "Clustering",
+        "path": "getting-started/cluster"
+      },
+      {
+        "title": "Web UI",
+        "path": "getting-started/ui"
+      },
+      {
+        "title": "Next Steps",
+        "path": "getting-started/next-steps"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v0.11.x/data/subnav.js b/content/nomad/v0.11.x/data/subnav.js
new file mode 100644
index 0000000000..a114322b05
--- /dev/null
+++ b/content/nomad/v0.11.x/data/subnav.js
@@ -0,0 +1,46 @@
+export default [
+  { text: 'Overview', url: '/', type: 'inbound' },
+  {
+    text: 'Use Cases',
+    submenu: [
+      {
+        text: 'Simple Container Orchestration',
+        url: '/use-cases/simple-container-orchestration'
+      },
+      {
+        text: 'Non-Containerized Application Orchestration',
+        url: '/use-cases/non-containerized-application-orchestration'
+      },
+      {
+        text: 'Automated Service Networking with Consul',
+        url: '/use-cases/automated-service-networking-with-consul'
+      }
+    ]
+  },
+  {
+    text: 'Enterprise',
+    url: 'https://www.hashicorp.com/products/nomad/',
+    type: 'outbound'
+  },
+  'divider',
+  {
+    text: 'Learn',
+    url: 'https://learn.hashicorp.com/nomad',
+    type: 'outbound'
+  },
+  {
+    text: 'Docs',
+    url: '/docs',
+    type: 'inbound'
+  },
+  {
+    text: 'API',
+    url: '/api-docs',
+    type: 'inbound'
+  },
+  {
+    text: 'Resources',
+    url: '/resources',
+    type: 'inbound'
+  }
+]
diff --git a/content/nomad/v0.11.x/data/version.js b/content/nomad/v0.11.x/data/version.js
new file mode 100644
index 0000000000..a04b7c8b24
--- /dev/null
+++ b/content/nomad/v0.11.x/data/version.js
@@ -0,0 +1 @@
+export default '0.11.3'
diff --git a/content/nomad/v0.11.x/img/acl.jpg b/content/nomad/v0.11.x/img/acl.jpg
new file mode 100644
index 0000000000..c892dd3928
Binary files /dev/null and b/content/nomad/v0.11.x/img/acl.jpg differ
diff --git a/content/nomad/v0.11.x/img/active-alert.png b/content/nomad/v0.11.x/img/active-alert.png
new file mode 100644
index 0000000000..65dcc51fe6
Binary files /dev/null and b/content/nomad/v0.11.x/img/active-alert.png differ
diff --git a/content/nomad/v0.11.x/img/alertmanager-webui.png b/content/nomad/v0.11.x/img/alertmanager-webui.png
new file mode 100644
index 0000000000..13691f6f72
Binary files /dev/null and b/content/nomad/v0.11.x/img/alertmanager-webui.png differ
diff --git a/content/nomad/v0.11.x/img/alerts.png b/content/nomad/v0.11.x/img/alerts.png
new file mode 100644
index 0000000000..b1ef6df853
Binary files /dev/null and b/content/nomad/v0.11.x/img/alerts.png differ
diff --git a/content/nomad/v0.11.x/img/count-dashboard.png b/content/nomad/v0.11.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v0.11.x/img/count-dashboard.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/android-chrome-192x192.png b/content/nomad/v0.11.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/android-chrome-512x512.png b/content/nomad/v0.11.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/apple-touch-icon.png b/content/nomad/v0.11.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/favicon-16x16.png b/content/nomad/v0.11.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/favicon-194x194.png b/content/nomad/v0.11.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/favicon-32x32.png b/content/nomad/v0.11.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/favicon.ico b/content/nomad/v0.11.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v0.11.x/img/favicons/mstile-144x144.png b/content/nomad/v0.11.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/mstile-150x150.png b/content/nomad/v0.11.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/mstile-310x150.png b/content/nomad/v0.11.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/mstile-310x310.png b/content/nomad/v0.11.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/mstile-70x70.png b/content/nomad/v0.11.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v0.11.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v0.11.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v0.11.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v0.11.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-binpacking.svg b/content/nomad/v0.11.x/img/feature-binpacking.svg
new file mode 100644
index 0000000000..de1e3e7ee2
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-binpacking.svg
@@ -0,0 +1,60 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1557 543">
+  <g fill="none" fill-rule="evenodd">
+    <g fill="#FFF" fill-rule="nonzero">
+      <path fill-opacity=".8" d="M1196.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1176.672 88.016 1134 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1171.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1308.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1288.672 88.016 1246 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1283.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1420.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1400.672 88.016 1358 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1395.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1532.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1512.672 88.016 1470 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1507.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1140.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1120.672 177.016 1078 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1115.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1252.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1232.672 177.016 1190 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1227.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1364.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1344.672 177.016 1302 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1339.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1476.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1456.672 177.016 1414 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1451.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1084.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1064.672 266.016 1022 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1059.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1196.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1176.672 266.016 1134 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1171.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1308.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1288.672 266.016 1246 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1283.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1420.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1400.672 266.016 1358 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1395.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1028.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1008.672 355.016 966 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1003.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623H966v49.115l43.033 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1140.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1120.672 355.016 1078 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1115.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1252.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1232.672 355.016 1190 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1227.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1364.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1344.672 355.016 1302 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1339.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+    </g>
+    <g fill="#FFF" fill-rule="nonzero">
+      <path d="M611 204a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 611 204m-453 86a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 158 290M57 250a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 57 250m-45 82a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 12 332m245 12a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 257 344m439 110a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 696 454M378 121a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 378 121m305 252a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 683 373m-262 44a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 421 417M253 171a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 253 171m209 78a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 462 249M124 539a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 124 539m187-370a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 311 169m-178 89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 133 258m441 257a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 574 515M5 407a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 5 407M361 59a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 361 59m25 157a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 386 216m-97 244a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 289 460m-31-161a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 258 299m217-56a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 243M79 411a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 79 411M647 75a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 647 75m-33 80a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 614 155m39 324a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 653 479M484 125a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 484 125m-96 231a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 388 356m-89-96a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 299 260m21 0a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 320 260m80-98a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 400 162M183 373a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 183 373M630 67a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 630 67M194 392a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 194 392m-72 126a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 122 518m235-314a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 357 204M99 329a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 99 329m449 128a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 548 457m110-299a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 658 158m-278-4a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 380 154m-205 62a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 175 216m157-31a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 332 185M98 490a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 98 490m563-103a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 661 387M475 532a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 532M335 402a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 335 402m55-3a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 390 399"/>
+      <path d="M649 481a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 649 481m22-105a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 671 376M42 38a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 42 38m268 495a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 310 533M154 92a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 154 92m224 139a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 378 231m250 80a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 628 311m-112-59a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 516 252M387 542a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 387 542m-84-265a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 303 277m-176-94a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 127 183m447 180a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 574 363m-1 180a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 573 543m-24-190a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 549 353M62 119a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 62 119m535-39a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 597 80m-103 0a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 494 80M25 217a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 25 217M338 48a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 338 48M82 51a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 82 51m441 375a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 523 426m-243-89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 280 337m99-226a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 379 111m36 413a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 415 524M311 129a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 311 129m66 364a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 377 493m162-236a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 539 257M90 398a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 90 398M608 83a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 608 83M70 184a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 70 184m355 139a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 425 323M144 476a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 144 476m451-140a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 595 336m-180 47a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 415 383m283-157a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 698 226M590 96a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 590 96m49-35a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 639 61m0 85a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 639 146m-252-10a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 387 136m236 363a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 623 499M87 509a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 87 509m163-342a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 250 167M85 10a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 85 10m482 451a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 567 461m98 25a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 665 486M160 338a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 160 338M69 535a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 69 535m25-332a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 94 203m381-20a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 183m-43-89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 432 94m-70 232a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 362 326m127-25a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 489 301m-287 12a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 202 313m454-84a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 656 229"/>
+    </g>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="3" d="M767.5 271.5h208"/>
+    <path fill="#FFF" d="M989 271.5 964 284v-25"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-blue-green.svg b/content/nomad/v0.11.x/img/feature-blue-green.svg
new file mode 100644
index 0000000000..0e38fe6763
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-blue-green.svg
@@ -0,0 +1,37 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path d="m17.484 1.02-16.29 9.473 16.29 9.474 16.162-9.56"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M17.484.037 0 10.194v20.27l11.94 6.915v-.985l-11.087-6.4V11.303l16.204 9.388v19.42l.64.385 17.27-10.03v-20.27zm0 19.93-16.29-9.474 16.29-9.474 16.162 9.386-16.162 9.56zm16.63 10.03L18.55 39l-.64.384V20.692l16.205-9.56z"/>
+    <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+      <text font-size="12" transform="translate(43 2)">
+        <tspan x="0" y="31">web-app:1.0</tspan>
+      </text>
+      <text font-size="18" transform="translate(43 2)">
+        <tspan x="0" y="15">group.blue</tspan>
+      </text>
+    </g>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m255.484 1.02-16.29 9.473 16.29 9.474 16.162-9.56"/>
+      <path fill-rule="nonzero" d="M255.484.037 238 10.194v20.27l11.94 6.915v-.985l-11.087-6.4V11.303l16.204 9.388v19.42l.64.385 17.27-10.03v-20.27L255.485.037zm0 19.93-16.29-9.474 16.29-9.474 16.162 9.386-16.162 9.56zm16.63 10.03L256.55 39l-.64.384V20.692l16.205-9.56v18.864z"/>
+      <g font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+        <text font-size="12" transform="translate(281 2)">
+          <tspan x="0" y="31">web-app:1.1</tspan>
+        </text>
+        <text font-size="18" transform="translate(281 2)">
+          <tspan x="0" y="15">group.green</tspan>
+        </text>
+      </g>
+    </g>
+    <path stroke="#FFF" stroke-width="5" d="M81.5 49C47.534 49 20 76.534 20 110.5S47.534 172 81.5 172s61.5-27.534 61.5-61.5a61.7 61.7 0 0 0-1.72-14.51"/>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M140.247 92.25c-7.342-23.662-28.587-41.206-54.184-43.083"/>
+    <text fill="#FFF" font-family="Courier-Bold, Courier" font-size="30" font-weight="bold" transform="translate(20 49)">
+      <tspan x="25.494" y="73">8/10</tspan>
+    </text>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M318.5 49c-33.966 0-61.5 27.534-61.5 61.5s27.534 61.5 61.5 61.5 61.5-27.534 61.5-61.5a61.7 61.7 0 0 0-1.72-14.51"/>
+    <path stroke="#FFF" stroke-width="5" d="M377.247 92.25c-7.342-23.662-28.587-41.206-54.184-43.083"/>
+    <text fill="#FFF" font-family="Courier-Bold, Courier" font-size="30" font-weight="bold" transform="translate(257 49)">
+      <tspan x="25.494" y="73">2/10</tspan>
+    </text>
+    <path stroke="#FFF" stroke-linecap="square" d="M202.5 66.41v89.18"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-flexible-workloads.svg b/content/nomad/v0.11.x/img/feature-flexible-workloads.svg
new file mode 100644
index 0000000000..63883b34c0
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-flexible-workloads.svg
@@ -0,0 +1,49 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 3324 402">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#979797" stroke-linecap="square" stroke-width="2" d="M2204.45 1v400"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1245.42 211.35c.36 7.42 7.76 4 11.12 1.67 3.18-2.2 4.12-.37 4.4-4.7.18-2.87.5-5.72.35-8.6-4.9-.42-10.1.72-14.1 3.6-2.1 1.47-5.9 6.2-1.9 8.04"/>
+    <path fill="#C6B198" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1245.42 211.35c1.07-.4 2.22-.68 2.95-1.66"/>
+    <path fill="#6AD7E5" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1262.54 123c-28.4-7.97-7.28-44.1 15.5-29.23l-15.5 29.24zm126.13-31.94c22.47-15.78 42.77 19.82 16.66 28.78z"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1393.5 302.62c5.7 3.53 16.14 14.2 7.58 19.4-8.23 7.52-12.83-8.28-20.06-10.47 3.1-4.22 7.06-8.07 12.48-8.93z"/>
+    <path stroke="#000" stroke-linecap="round" stroke-width="3" d="M1401.08 322c-1.27-2.52-1.7-5.46-3.82-7.5"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1291.53 314.7c-6.7 1.03-10.47 7.07-16.05 10.14-5.27 3.14-7.28-1-7.76-1.85-.82-.4-.75.3-2.02-1-4.88-7.7 5.08-13.4 10.27-17.2 7.22-1.5 11.75 4.8 15.56 9.8z"/>
+    <path stroke="#000" stroke-linecap="round" stroke-width="3" d="M1267.73 323c.25-2.94 2.58-4.9 3.7-7.4"/>
+    <path fill="#000" fill-rule="nonzero" d="M1263.72 113.04c-3.74-1.98-6.5-4.67-4.2-9 2.12-4.02 6.06-3.58 9.8-1.6zm135.7-3.77c3.73-1.98 6.48-4.67 4.2-9-2.13-4-6.07-3.58-9.82-1.6l5.6 10.6z"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1425.2 210.4c-.37 7.43-7.78 4-11.13 1.68-3.2-2.2-4.12-.37-4.4-4.72-.18-2.85-.5-5.7-.35-8.57 4.8-.5 10.05.7 14 3.5 2.03 1.5 5.85 6.2 1.86 8"/>
+    <path fill="#C6B198" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1425.2 210.4c-1.1-.4-2.23-.67-2.96-1.65"/>
+    <path fill="#6AD7E5" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1332.46 76.06c28.42 0 55.06 4.06 68.95 31.37 12.5 30.6 8.1 63.6 10 95.95 1.7 27.77 5.3 59.86-7.6 85.6-13.5 27.08-47.4 33.9-75.3 32.9-21.9-.8-48.4-7.95-60.7-27.97-14.5-23.4-7.6-58.4-6.5-84.5 1.3-30.9-8.4-62 1.8-92.3 10.6-31.4 39.1-38.5 69.7-40.9"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="2.91" d="M1337.48 114.2c5.1 29.67 53.58 21.83 46.62-8.1-6.24-26.8-48.32-19.4-46.62 8.1"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="2.82" d="M1279.54 119c6.6 25.83 47.95 19.22 46.4-6.68-1.87-31.03-52.73-25.04-46.4 6.7"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1343.33 149.8c.02 3.86.87 8.2.14 12.3-.98 1.85-2.9 2.05-4.58 2.8-2.3-.36-4.3-1.87-5.2-4.02-.6-4.7.2-9.22.3-13.9l9.2 2.83z"/>
+    <g fill-rule="nonzero" transform="translate(1283.724 107.073)">
+      <ellipse cx="7.21" cy="7.72" fill="#000" rx="6.98" ry="7.56"/>
+      <ellipse cx="10.39" cy="9.43" fill="#FFF" rx="1.65" ry="1.92"/>
+    </g>
+    <g fill-rule="nonzero" transform="translate(1342.104 105.19)">
+      <ellipse cx="7.33" cy="7.72" fill="#000" rx="6.87" ry="7.56"/>
+      <ellipse cx="10.45" cy="9.43" fill="#FFF" rx="1.62" ry="1.92"/>
+    </g>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1323.37 149.4c-3.04 7.37 1.7 22.13 9.97 11.24-.6-4.68.22-9.22.37-13.9l-10.3 2.65z"/>
+    <g fill-rule="nonzero">
+      <path fill="#F6D2A2" stroke="#231F20" stroke-linecap="round" stroke-width="3" d="M1324.42 135.17c-5.68.48-10.32 7.23-7.37 12.57 3.9 7.08 12.63-.62 18.07.1 6.25.13 11.38 6.6 16.4 1.17 5.6-6-2.4-11.9-8.65-14.5l-18.45.8z"/>
+      <path fill="#000" d="M1323.7 134.87c-.42-9.83 18.33-11.06 20.55-2.83 2.2 8.2-19.62 10.12-20.55 2.83-.73-5.82 0 0 0 0"/>
+    </g>
+    <g fill-rule="nonzero">
+      <path fill="#5382A1" d="M968.58 268.63s-9.5 5.53 6.77 7.4c19.7 2.24 29.78 1.92 51.5-2.2 0 0 5.7 3.6 13.7 6.7-48.7 20.86-110.2-1.22-71.97-11.9m-5.95-27.24s-10.66 7.8 5.62 9.5c21.06 2.1 37.7 2.3 66.46-3.2 0 0 4 4 10.3 6.2-58.9 17.2-124.4 1.3-82.3-12.7z"/>
+      <path fill="#F8981D" d="M1012.8 195.2c12 13.8-3.16 26.25-3.16 26.25s30.47-15.73 16.47-35.43c-13-18.36-23-27.48 31.2-58.95 0 0-85.1 21.27-44.5 68.13"/>
+      <path fill="#5382A1" d="M1077.2 288.77s7.03 5.8-7.75 10.28c-28.1 8.52-117 11.1-141.68.34-8.87-3.9 7.77-9.3 13-10.4 5.46-1.2 8.58-1 8.58-1-9.87-7-63.8 13.6-27.4 19.5 99.3 16.1 180.98-7.3 155.23-18.9M973.15 213s-45.2 10.75-16 14.65c12.32 1.65 36.9 1.3 59.8-.64 18.7-1.5 37.5-4.9 37.5-4.9s-6.6 2.9-11.38 6.1c-45.9 12.1-134.6 6.5-109.06-5.9 21.6-10.4 39.2-9.2 39.2-9.2m81.1 45.3c46.7-24.2 25.1-47.5 10.1-44.4-3.7.8-5.3 1.4-5.3 1.4s1.4-2.1 4-3.1c29.8-10.4 52.7 30.9-9.6 47.3 0 0 .8-.6 1-1.2"/>
+      <path fill="#F8981D" d="M1026.1 76.27s25.86 25.85-24.5 65.6c-40.38 31.9-9.2 50.08-.02 70.86-23.57-21.27-40.86-40-29.26-57.42 17.03-25.5 64.22-37.9 53.8-79"/>
+      <path fill="#5382A1" d="M977.74 324.22c44.8 2.87 113.58-1.6 115.2-22.78 0 0-3.12 8.03-37 14.4-38.24 7.2-85.4 6.37-113.37 1.76 0 0 5.73 4.74 35.17 6.63z"/>
+    </g>
+    <g fill-rule="nonzero" transform="translate(509.063 76)">
+      <path fill="#54A3DA" d="M165.18 249.2s5.9-28.48 30.55-62.68c17.14-9.9 34.33-22.04 48.9-36.6 13.45-66.74-6.98-138.36-6.98-138.36S166.03-8.87 99.3 4.6C84.7 19.15 72.6 36.33 62.7 53.47 28.47 78.13 0 84.03 0 84.03s22.78 15.64 33.78 33.4c-4.7 13.5-6.9 22.2-6.9 22.2 1.8 8.33 7.06 18.05 14.34 27.86-5.03 3.9-10.92 8.1-17.3 11.5l-2.34 1.2c5.5 18.1 29.74 40.9 47.4 47 .37-.7.74-1.4 1.13-2.1 3.6-6.6 7.9-12.6 12-17.8 9.9 7.2 19.6 12.5 27.6 14.7 0 0 8.7-2.2 22.2-6.9 17.8 11 33.4 33.8 33.4 33.8zm-50.35-60.32c-10.16-4.4-23.65-15.24-32.85-24.45C69.54 152 62.8 141.4 60.2 134.8c4.38-14.88 21.16-66.32 53.4-100.9 38.86-6.6 79.58.5 97.3 4.4 3.9 17.72 11 58.45 4.4 97.32-34.37 32.06-85.06 48.73-100.48 53.26z"/>
+      <circle cx="148.9" cy="100.64" r="26.62" fill="#F1616E"/>
+    </g>
+    <path fill="#1869A5" fill-rule="nonzero" d="M203.38 191h37.13v-33.76h-37.1V191zm-43.88 0h37.13v-33.76H159.5zm-43.9 0h37.13v-33.76H115.6zm-43.88 0h37.15v-33.76H71.75V191zm-43.88 0h37.14v-33.76H27.85V191zm43.9-40.52h37.13v-33.75H71.75v33.75zm43.88 0h37.13v-33.75h-37.13zm43.88 0h37.13v-33.75H159.5zm0-40.5h37.13V76.22H159.5zm192.57 61.33c-8.1-5.4-26.74-7.4-41.08-4.7-1.9-13.5-9.4-25.2-23.1-35.8l-7.9-5.2-5.3 7.9c-6.8 10.2-10.1 24.2-9 37.7.5 4.8 2 13.3 6.9 20.7-4.9 2.7-14.5 6.3-27.2 6H1.4l-.5 2.8c-2.3 13.6-2.24 55.8 25.2 88.3 20.83 24.5 52.1 37 92.9 37 88.44 0 153.88-40.7 184.52-114.7 12.05.3 38 .1 51.32-25.4.35-.6 1.15-2.1 3.47-6.9l1.3-2.6-7.5-5z"/>
+    <path fill="#000" fill-rule="nonzero" d="M2559.34 269.98c-3.73 8.63-8.15 16.57-13.28 23.87-6.98 9.95-12.7 16.85-17.1 20.67-6.83 6.28-14.15 9.5-21.98 9.68-5.63 0-12.4-1.6-20.3-4.85-7.93-3.23-15.2-4.83-21.87-4.83-6.9 0-14.4 1.6-22.4 4.83-8 3.25-14.5 4.94-19.4 5.1-7.5.33-15-2.98-22.4-9.93-4.7-4.16-10.7-11.3-17.9-21.4-7.6-10.8-13.9-23.3-18.9-37.58-5.3-15.4-7.9-30.33-7.9-44.78 0-16.55 3.6-30.83 10.8-42.8 5.6-9.6 13.1-17.17 22.5-22.74 9.4-5.56 19.5-8.4 30.4-8.58 6 0 13.8 1.85 23.5 5.47 9.7 3.7 15.9 5.5 18.7 5.5 2 0 9-2.1 20.7-6.4 11.1-4 20.5-5.6 28.2-5 20.8 1.7 36.4 9.9 46.8 24.7-18.6 11.3-27.7 27.1-27.6 47.3.2 15.8 5.9 28.9 17.2 39.3 5.1 4.9 10.8 8.6 17.1 11.3-1.4 4-2.8 7.8-4.4 11.5zM2511.7 82.46c0 12.35-4.52 23.9-13.52 34.56-10.85 12.7-23.98 20.02-38.22 18.86-.18-1.48-.28-3.04-.28-4.68 0-11.85 5.16-24.54 14.33-34.92 4.6-5.25 10.4-9.62 17.5-13.1 7.1-3.43 13.7-5.33 20-5.66.2 1.65.3 3.3.3 4.94zm304.76 55.62c0 .83-.83.83-.83.83h-.82c-.8 0-.8-.8-1.6-1.6 0 0-.8-.8-.8-1.6s0-.8.8-.8l1.7.9c.9.8 1.7 1.7 1.7 2.5m-14.8-8.2c0-4.1-1.6-6.5-4.1-6.5 0 0 0 .8-.8.8v1.6h2.5c0 1.7.8 2.5.8 4.1h1.7m28.8-4.1c1.6 0 2.5 1.7 3.3 4.1h1.7c-.8-.8-.8-1.6-.8-2.4s0-1.7-.8-2.5-1.6-1.6-2.5-1.6c0 0-.8.9-1.6.9 0 .8.9.8.9 1.6m-24.7 13.2c-.8 0-.8 0-.8-.8s0-1.6.9-2.5c1.7 0 2.5-.8 2.5-.8.9 0 .9.9.9.9 0 .8-.8 1.7-2.5 3.3h-.8m-9-.8c-3.3-1.6-4.1-4.1-4.1-8.2 0-2.5 0-4.1 1.6-5.7.9-1.6 2.5-2.4 4.1-2.4 1.7 0 2.5.9 4.1 2.5.9 2.5 1.7 5 1.7 7.4v1.7h.8v-.9c.9 0 .9-1.7.9-5 0-2.5 0-4.9-1.7-7.4-1.6-2.5-3.3-4.1-6.6-4.1-2.4 0-4.9 1.7-5.7 4.1-1.6 3.3-2 5.8-2 9.9 0 3.3 1.2 6.6 4.5 9.9.8-.8 1.6-.8 2.5-1.7M2900 254.5c.8 0 .8-.3.8-1.04 0-1.8-.8-3.93-3.3-6.3-2.4-2.5-6.5-4.04-11.5-4.7-.8-.1-1.6-.1-1.6-.1-.8-.14-.8-.14-1.6-.14-.85-.06-2.5-.2-3.3-.4 2.45-7.64 3.3-14.4 3.3-20.3 0-8.2-1.67-13.95-4.96-18.9-3.3-4.9-6.6-7.4-10.7-8.2-.8.8-.8.8-.8 1.64 4.1 1.6 8.2 4.9 10.7 9.85 2.5 5.8 3.3 10.7 3.3 16.5 0 4.6-.8 11.4-4.1 20.2-3.3 1.3-6.6 4.4-9.1 9.2 0 .7 0 1.2.8 1.2 0 0 .8-.7 1.66-2.1 1.62-1.4 2.45-2.8 4.1-4.2 2.46-1.4 4.1-2.1 6.6-2.1 4.1 0 8.2.6 10.7 1.8 3.3 1.1 4.9 2.2 5.74 3.5.8 1.2 1.6 2.4 2.4 3.5 0 1 .8 1.5.8 1.5m-76-119.6c-.8-.8-.8-2.5-.8-4.1 0-3.3 0-4.9 1.65-7.4 1.6-1.6 3.3-2.4 4.9-2.4 2.4 0 4.1 1.7 5.7 3.3.8 2.5 1.6 4.1 1.6 6.6 0 4.1-1.7 6.6-5 7.4 0 0 .8.9 1.6.9 1.6 0 2.4.8 4.1 1.7.8-4.9 1.6-8.2 1.6-12.3 0-4.9-.8-8.2-2.5-10.7-2.5-2.4-5-3.2-8.3-3.2-2.5 0-5 .8-7.4 2.5-1.7 2.5-2.5 4.1-2.5 6.6 0 4.1.8 7.4 2.4 10.7.8 0 1.7.8 2.5.8m9.9 13.2c-10.7 7.4-19 10.7-25.5 10.7-5.8 0-11.5-2.4-16.5-6.5.8 1.7 1.6 3.3 2.4 4.1l4.9 5c3.3 3.3 7.4 4.9 11.5 4.9 5.8 0 12.4-3.3 20.6-9l7.4-4.95c1.6-1.6 3.3-3.3 3.3-5.7 0-.8 0-1.62-.9-1.62-.8-1.6-4.9-4.1-13.2-6.5-7.4-3.23-13.2-4.9-16.5-4.9-2.5 0-6.6 1.68-12.3 4.96-5 3.3-8.3 6.6-8.3 9.9 0 0 .82.8 1.64 2.46 4.9 4.1 9.85 6.56 14.8 6.56 6.6 0 14.8-3.3 25.5-11.5v1.6c.8 0 .8.8.8.8m18.9 166.17c3.3 6.2 9.06 9.3 15.64 9.3 1.6 0 3.3-.3 4.9-.8 1.7-.36 3.3-.9 4.1-1.6.86-.55 1.7-1.1 2.5-1.8 1.66-.56 1.66-1 2.5-1.4l14-12.1c3.3-2.6 6.55-4.9 10.7-6.9 3.25-1.96 6.54-3.3 8.2-4 2.45-.66 4.1-1.65 5.74-2.96.8-1.24 1.6-2.8 1.6-4.77 0-2.4-1.6-4.2-3.3-5.5-1.6-1.3-3.2-2.2-4.9-2.8-1.6-.6-3.3-1.9-5.7-4.1-1.7-2.13-3.3-5.1-4.1-9l-.9-4.8c-.8-2.2-.8-3.8-1.68-4.7 0-.25 0-.33-.8-.33s-2.5.7-3.3 2.1c-1.63 1.4-3.3 3-4.9 4.6-.8 1.7-3.3 3.1-5 4.5-2.5 1.4-4.94 2.2-6.6 2.2-6.56 0-9.85-1.8-12.3-5.33-1.64-2.6-2.46-5.62-3.3-9.1-1.6-1.4-2.45-2.1-4.1-2.1-4.1 0-5.75 4.3-5.75 12.9V292c0 .8-.8 2.4-.8 4.97-.8 2.6-.8 5.5-.8 8.7l-1.67 9.1v.2m-92.8 2.8c9.94 3.66 16 5.5 18.24 5.5 5.8 0 10.6-2.5 14.5-7.5.8-1.6.8-3.5.8-5.6 0-7.8-4.7-17.6-14-29.52l-5.6-7.5c-1.2-1.52-2.6-3.9-4.4-7.1-1.7-3.2-3.3-5.7-4.5-7.4-1-1.9-2.8-3.8-5-5.7-2.1-1.9-4.6-3.1-7.3-3.77-3.5.7-5.85 1.8-7 3.4-1.15 1.57-1.8 3.3-2 5.1-.2 1.74-.7 2.9-1.54 3.46-.82.5-2.22.9-4.1 1.35h-4.5c-4.3 0-7.3.5-8.83 1.3-2 2.4-3.1 5.1-3.1 8 0 1.3.3 3.5 1 6.7.7 3 1 5.5 1 7.2 0 3.3-1 6.7-3.1 10.1-2.1 3.5-3.1 6.2-3.1 8 .8 3.2 6.2 5.4 16.2 6.7q11.4 1.8 26.4 7.2zm5.5-101.23c2.96-7.4 5.9-12.3 8.8-15.6-.17-.8-.6-.8-1.24-.8l-.86-.86c-2.4 2.5-5.27 8.26-8.7 16.5-3.48 7.4-5.3 14.2-5.3 19.2 0 3.7.9 6.9 2.6 9.7 1.8 2.7 6.2 6.6 13.1 11.6l8.7 5.63c9.3 8.1 14.22 13.7 14.22 17 0 1.7-.9 3.5-3.3 5.4-1.7 2-3.9 3-5.8 3-.1 0-.2.2-.2.6 0 .1.8 1.8 2.52 5 3.5 4.7 10.9 7 20.7 7 18.1 0 32.1-7.4 42.8-22.2 0-4.1 0-6.7-.8-7.7v-4c0-5.3.8-9.3 2.43-12 1.7-2.6 3.3-3.8 5.8-3.8 1.7 0 3.3.6 5 1.8.8-6.3.8-11.8.8-16.7 0-7.5 0-13.6-1.6-19.4-.8-4.9-2.5-9-4.1-12.3l-4.9-7.4c-1.64-2.4-2.5-4.9-4.1-7.4-.83-3.3-1.65-5.7-1.65-9.8-2.5-4.2-4.2-8.3-6.6-12.4-1.7-4.1-3.3-8.3-5-11.5l-7.4 5.7c-8.2 5.7-14.8 8.2-20.56 8.2-4.95 0-9.06-.8-11.5-4.1l-4.96-4.2c0 2.5-.8 5.8-2.5 9l-5.2 9.8c-2.3 5.7-3.5 9-3.73 11.5-.33 1.6-.6 3.3-.74 3.3l-6.2 12.3c-6.7 12.3-10 23.7-10 33.2 0 1.9.1 3.8.5 5.8-3.7-2.6-5.6-6.1-5.6-10.7 0-5.7 1.5-11.9 4.5-19.3zm29.7 101.4c-4.13 4.7-8.73 7.3-15.15 7.3-4 0-10.4-1.6-18.9-4.7-8.64-2.94-16.3-5.2-23-6.7-.6-.2-2.1-.5-4.5-.87-2.3-.4-4.4-.74-6.3-1.12-1.7-.3-3.7-.9-5.8-1.6-2.04-.64-3.7-1.5-4.9-2.52-1.1-1-1.7-2.2-1.7-3.5q0-1.95.9-4.2c.53-.9 1.1-1.8 1.7-2.6.6-.9 1.1-1.7 1.4-2.5.5-.75.83-1.5 1.16-2.3.3-.75.63-1.5.8-2.4.16-.8.33-1.64.33-2.47 0-.8-.3-3.24-1-7.6-.66-4.3-1-7-1-8.13 0-3.6.8-6.5 2.7-8.56 1.8-2.03 3.53-3.1 5.34-3.1h9.5c.8 0 1.9-.4 3.67-1.4.6-1.3 1.1-2.4 1.4-3.4.4-1 .6-1.7.8-2.04.1-.47.3-.96.5-1.4.3-.55.7-1.2 1.3-1.87-.7-.8-1-1.9-1-3.2 0-.9 0-1.73.17-2.23 0-2.95 1.4-7.14 4.36-12.65l2.9-5.2c2.4-4.5 4.2-7.77 5.5-11.06 1.4-3.3 2.9-8.23 4.5-14.8 1.3-5.77 4.45-11.53 9.4-17.3l6.15-7.4c4.3-4.9 7.1-9 8.64-12.3 1.6-3.3 2.4-7.4 2.4-10.7 0-1.63-.4-6.56-1.3-14.8-.87-8.2-1.3-16.43-1.3-23.83 0-5.8.5-9.9 1.54-14s3-8.3 5.8-11.5c2.5-3.3 5.7-6.6 10.7-8.3 4.9-1.7 10.7-2.5 17.2-2.5 2.5 0 4.94 0 7.4.8 2.5 0 5.76.8 9.9 2.5 3.3 1.6 6.55 3.3 9 5.7 3.3 2.4 5.77 6.5 8.2 10.7 1.68 4.9 3.3 9.8 4.1 16.4.8 4.1.8 8.2 1.67 14 0 4.9.84 8.2.84 10.7.82 2.4.82 5.7 1.64 9.8.8 3.3 1.6 6.6 3.3 9.1 1.6 3.3 3.3 6.6 5.7 9.9 2.5 4.1 5.8 8.2 9.1 13.2 7.4 8.2 13.2 17.2 16.48 26.3 4.1 8.2 6.6 18.9 6.6 30.3 0 5.7-.8 11.2-2.5 16.5 1.64 0 2.5.7 3.3 1.8.8 1.2 1.6 3.6 2.46 7.5l.8 6.1c.8 1.8 1.64 3.5 4.1 5 1.65 1.5 3.3 2.7 5.8 3.7 1.6.8 4.1 2 5.7 3.4 1.64 1.7 2.46 3.4 2.46 5.2q0 4.2-2.4 6.3c-1.7 1.6-3.3 2.8-5.8 3.5-1.66.8-4.9 2.5-9.88 4.8-4.1 2.4-8.2 5.4-12.3 8.9l-8.3 7c-3.3 3.2-6.6 5.5-9.04 6.9-2.43 1.5-5.7 2.2-9 2.2l-5.77-.7c-6.5-1.7-10.7-5-13.1-10-13.2-1.6-23.9-2.3-30.45-2.3-10.7 0-18.9 1.4-24.7 4.3z"/>
+    <path fill="#00ADEF" fill-rule="nonzero" d="m3075 111.23 101.38-13.8.05 97.8-101.34.57-.1-84.57zm101.34 95.26.07 97.8-101.3-14v-84.6l101.3.6zm12.3-110.9 134.4-19.6v117.9l-134.4 1V95.6zm134.44 111.8-.03 117.4-134.43-19-.18-98.7 134.64.2z"/>
+    <path fill="#E25A1C" d="m2013.6 202.65-.8-1.75c-6-11.4-11.98-22.78-18.02-34.14-.6-1.14-.53-1.82.3-2.8 9.53-11.12 19-22.3 28.5-33.45.32-.3.62-.8.75-1.5l-8.32 2.2c-11.5 3.1-23 6.1-34.5 9.2-1 .3-1.5 0-2.1-.9-6.5-10.9-13.1-21.8-19.6-32.7-.3-.5-.7-1.1-1.4-1.6l-1.5 8.8-5.5 30.8c-.2 1.1-.4 2.2-.5 3.4-.1 1.1-.6 1.5-1.6 1.8-13.5 4.3-27.1 8.6-40.6 12.9-.6.2-1.2.5-1.8 1 11.1 4.4 22.2 8.8 33.5 13.3-.4.3-.7.6-1 .8l-20.7 13.5c-.8.6-1.5.6-2.4.2l-24.9-11.1c-3.7-1.6-7-3.8-9.6-7-5.9-7.2-4.7-15.4 3.2-20.4 2.6-1.6 5.5-2.9 8.4-3.8 13.3-4.4 26.6-8.5 40-12.7 1.2-.4 1.7-.9 1.9-2.1 1.8-10.3 3.6-20.5 5.5-30.8 1-5.5 1.5-11.1 4.2-16.1 1-1.9 2.3-3.8 3.7-5.4 5.3-5.9 12.7-6.1 18.3-.5 1.9 1.9 3.5 4.1 4.9 6.4 6.2 10 12.3 20.2 18.3 30.3.7 1.2 1.4 1.4 2.7 1.1 14.9-4 29.7-7.9 44.6-11.8 3.1-.8 6.2-1.1 9.3-.5 6.9 1.3 9.9 6.5 7.5 13.1-1 3.1-2.9 5.6-4.9 8l-31.2 36.6c-.8 1-.8 1.7-.3 2.8 6.3 11.7 12.4 23.5 18.6 35.2 1.5 2.8 2.6 5.7 2.7 9 .1 7.4-5.3 13.4-12.6 14.4-4 .6-7.8-.2-11.7-1.4-9.3-2.9-18.6-5.7-28-8.5-.8-.3-1.2-.6-1.3-1.5-1-6.6-2.2-13.1-3.4-19.7 0-.2.1-.4.1-.8l32.2 8.9"/>
+    <path fill="#3C3A3E" d="M1995.44 298.38c-8.4-.02-16.8-.06-25.2-.02-1.12 0-1.75-.32-2.37-1.27-9.95-15.2-19.94-30.3-29.93-45.5l-1.22-1.8-6.36 48.3h-22c.25-2.2.48-4.2.75-6.3l6.5-49.2c2.1-15.7 4.1-31.4 6.2-47.1.1-.5.4-1.1.8-1.3l22.8-14.7c.1-.1.3-.1.7-.2l-6.8 52.3.3.2 36.1-39.9 1 5.5c.9 5 1.7 10 2.6 14.9.2 1 0 1.6-.7 2.3-7.7 8-15.4 16.1-23.1 24.2l-1 1.1.7 1.1 39.8 55.8.9.9v.3m-261-48.3c-.3-1.7-.5-4.3-1.3-6.6-3.7-11.4-15.3-17.6-27.4-14.8-13.2 3.1-22.7 13.5-24 27-1 10 4.4 19.6 14.4 23.2 8.1 2.9 15.8 1.6 23.1-2.7 9.6-5.8 14.8-14.3 15.4-26.3zm-58.2 42.3c-.6 4.9-1.3 9.5-1.9 14.1l-2.4 18.4c0 .7-.3 1-1 1-6.1-.1-12.1 0-18.1-.1-.1 0-.2-.1-.6-.2l1.1-8.7 4.1-30.6c1.6-11.7 2.8-23.3 4.8-34.9 3.5-20.5 20.9-38.1 41.2-42.5 11.8-2.6 23.1-1.4 33.5 5.2 10.3 6.6 16.2 16.2 17.6 28.3 1.9 17.1-4.4 31.3-16.5 43-8 7.7-17.5 12.6-28.5 14.3-11.4 1.7-22-.2-31.6-6.9-.4-.3-.7-.5-1.3-.9zm-9.8-97.2-19.9 14.8c-1.1-1.7-2-3.4-3.1-4.9-2.9-4-6.4-7-11.5-7.3-4.2-.3-7.9 1.1-10.8 4.2-2.6 2.9-2.9 6.9-.5 10.1 2.7 3.5 5.6 6.8 8.6 10 5 5.4 10.2 10.5 15.1 16 4.5 4.9 8.1 10.4 9.2 17.2 1.3 8-.2 15.6-4 22.7-7 13-18 20.5-32.6 22.9-6.4 1-12.8.8-19.1-1-8.3-2.5-14.1-7.9-17.8-15.6-1.3-2.8-2.3-5.6-3.5-8.6 7.3-3.9 14.3-7.7 21.5-11.5.3.6.5 1.1.7 1.6 1.2 2.4 2.2 5 3.8 7.3 4.5 6.7 11.8 8.7 19.2 5.4 1.88-.9 3.7-2.1 5.2-3.4 4.7-4.3 5.6-10.1 2.1-15.4-2-3.1-4.52-5.8-7-8.6-5.9-6.5-12-12.8-17.72-19.5-4-4.6-6.66-9.9-7.5-16.1-.94-6.7.4-13 3.9-18.7 8.66-14 21.26-21.3 37.9-20.7 9.5.3 17.07 4.8 22.94 12.1 1.73 2.2 3.4 4.5 5.14 6.8m161 75.2c-1.1 8.5-2.2 16.5-3.25 24.5-.1.4-.4 1-.7 1.1-16.4 7.6-38 6.6-51.5-8.7-7.3-8.3-10.3-18-9.8-28.9 1-25.2 21.8-47.1 46.8-50.1 14.5-1.8 27.3 2.1 37.1 13.4 6.7 7.7 9.8 16.9 9.35 27-.3 6.7-1.3 13.4-2.2 20-1.15 9.5-2.44 18.9-3.7 28.33 0 .3-.1.63-.2 1.1h-20l.77-6.4c1.4-10.9 3-21.8 4.2-32.8.76-6.8.27-13.5-2.84-19.8-3.32-6.7-8.87-10.3-16.17-11.05-15.1-1.6-29.5 8.9-32.7 23.73-2.16 9.8 1.2 19.2 9 24.4 7.6 5.1 15.8 5.1 24.1 1.8 4.2-1.67 7.8-4.3 11.2-7.86m82.6-60.2-2.66 20.4h-12.3c-3.3 0-6.3 2.12-7.3 5.2-.4 1.2-.5 2.5-.7 3.73l-6.1 46.8-1.5 11.9H1859l1.1-8.8 4-30.4c1.2-8.7 2.2-17.5 3.6-26.2 1.84-11.7 13.5-22.1 25.3-22.6 5.62-.2 11.3 0 17.1 0"/>
+    <path fill="#3C3A3E" fill-rule="nonzero" d="M2019.52 298.25v-8.62h-.05l-3.38 8.62h-1.1l-3.4-8.62h-.1v8.62h-1.7v-10.33h2.6l3.1 7.85 3-7.85h2.6v10.33h-1.7zm-15-8.95v8.95h-1.7v-8.95h-3.23v-1.38h8.1v1.38h-3.3zM1693.9 180.54h5.08l-1.2-7.67-3.87 7.67zm5.87 4.95h-8.43l-2.67 5.2h-5.97l13.16-24.6h5.76l4.48 24.6h-5.53l-.8-5.3zm30.15-14.4h-3l-1.02 5.6h3c1.8 0 3.26-1.2 3.26-3.5 0-1.5-.9-2.3-2.24-2.3zm-7.27-5h7.88c4.13 0 7.02 2.4 7.02 6.7 0 5.3-3.76 8.9-9.12 8.9h-3.4l-1.6 9h-5.12l4.4-24.6zm32.35 14.4h5.05l-1.2-7.7-3.86 7.6zm5.85 4.9h-8.43l-2.67 5.2h-5.97l13.16-24.6h5.75l4.4 24.6h-5.6l-.8-5.3zm33.3 4.3c-1.73.8-3.64 1.2-5.56 1.2-6.6 0-10.6-4.9-10.6-11 0-7.8 6.5-14.4 14.4-14.4 1.9 0 3.7.4 5.1 1.2l-.7 5.9c-1.1-1.2-2.9-2-5-2-4.5 0-8.5 4-8.5 8.7 0 3.6 2.2 6.4 5.8 6.4 2.1 0 4.2-.9 5.6-2l-.7 5.8m31.4-9.1h-10.7l-1.8 9.9h-5.2l4.3-24.6h5.1l-1.8 9.7h10.7l1.7-9.7h5.1l-4.4 24.6h-5.2l1.7-9.9m18.8 9.9 4.3-24.6h13.7l-.9 4.9h-8.5l-.9 4.7h7.8l-.8 4.9h-7.8l-.9 4.9h8.5l-.9 4.9H1844"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-machine-failure.svg b/content/nomad/v0.11.x/img/feature-machine-failure.svg
new file mode 100644
index 0000000000..5f8302ca74
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-machine-failure.svg
@@ -0,0 +1,17 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path fill="#FFF" d="M268 84h100v21.212H268zm5.116 4.714v11.784h72.093V88.714h-72.1zm83.49 11.784c3.21 0 5.813-2.638 5.813-5.892s-2.61-5.892-5.82-5.892-5.82 2.638-5.82 5.892 2.603 5.892 5.814 5.892zM268 112.738h100v21.21H268v-21.212zm5.116 4.713v11.79h72.093v-11.79h-72.1zm83.49 11.79c3.21 0 5.813-2.64 5.813-5.89s-2.61-5.89-5.82-5.89-5.82 2.64-5.82 5.895 2.603 5.893 5.814 5.893zM268 141.48h100v21.212H268zm5.116 4.714v11.78h72.093v-11.78h-72.1zm83.49 11.78c3.21 0 5.813-2.64 5.813-5.89 0-3.255-2.61-5.89-5.82-5.89s-5.82 2.635-5.82 5.89c0 3.253 2.603 5.89 5.814 5.89z"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M185 123h27.538"/>
+    <path fill="#FFF" d="m221.5 123.037-10.5 6.038V117"/>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="M32 84h100v21.212H32zm5.116 4.714v11.784h72.093V88.714h-72.1zm83.49 11.784c3.21 0 5.813-2.638 5.813-5.892s-2.61-5.892-5.82-5.892-5.82 2.638-5.82 5.892 2.603 5.892 5.814 5.892zM32 112.738h100v21.21H32v-21.212zm5.116 4.713v11.79h72.093v-11.79h-72.1zm83.49 11.79c3.21 0 5.813-2.64 5.813-5.89s-2.61-5.89-5.82-5.89-5.82 2.64-5.82 5.895 2.603 5.893 5.814 5.893z"/>
+      <path d="M32 141.475h100v21.212H32zm5.116 4.714v11.78h72.093v-11.78h-72.1zm83.49 11.78c3.21 0 5.813-2.64 5.813-5.89 0-3.26-2.61-5.89-5.82-5.89s-5.82 2.63-5.82 5.89c0 3.25 2.603 5.89 5.814 5.89z"/>
+    </g>
+    <path d="m318.498 14.238-16.303 9.474 16.303 9.474 16.174-9.56"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M318.498 13.256 301 23.413v20.272l11.95 6.914v-.99l-11.096-6.4V24.52l16.217 9.39v19.42l.64.384L336 43.684v-20.27l-17.5-10.158zm0 19.93-16.303-9.474 16.303-9.474 16.174 9.39zm16.644 10.03-15.577 9.004-.64.384V33.912l16.217-9.56v18.863z"/>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m81.498 14.238-16.303 9.474 16.303 9.474 16.174-9.56"/>
+      <path fill-rule="nonzero" d="M81.498 13.256 64 23.413v20.272L75.95 50.6v-.983l-11.096-6.402V24.523l16.217 9.39V53.33l.64.384L99 43.684v-20.27l-17.5-10.16zm0 19.93-16.303-9.474 16.303-9.474 16.174 9.39zm16.644 10.03L82.565 52.22l-.64.384V33.912l16.217-9.56v18.863z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-public-private-clouds.svg b/content/nomad/v0.11.x/img/feature-public-private-clouds.svg
new file mode 100644
index 0000000000..860aa31fc2
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-public-private-clouds.svg
@@ -0,0 +1,147 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 3334 402">
+  <style xmlns="http://www.w3.org/2000/svg">
+    .aws-smile{fill-rule:evenodd;clip-rule:evenodd;fill:#f90}
+  </style>
+  <defs>
+    <path id="a" d="M.9 44.94h44.37V.04H.9z"/>
+    <path id="reuse-0" fill="#871F1C" d="m3235.02 188.7-19.15-18.98 28.98-2.56 19.1 18.95"/>
+    <path id="reuse-1" fill="#871F1C" d="m3125.3 198.37-19.15-19 28.98-2.56 19.1 19"/>
+    <path id="reuse-2" fill="#871F1C" d="m3234.87 136.06-19.16-19 29-2.55 19.1 19"/>
+    <path id="reuse-3" fill="#E63F46" d="m3134.52 98.47 120.3-10.52c5.1-.4 9.18 3.32 9.18 8.43l-.1 30.28-28.88 2.55v-5.7c0-2.6-2.14-4.6-4.74-4.4l-71.26 6.3c-2.65.2-4.84 2.6-4.84 5.2v5.8l-28.93 2.5.1-30.2c0-5.1 4.13-9.5 9.17-10z"/>
+    <radialGradient id="c" cx="14.38%" cy="6.75%" r="76.97%" fx="14.38%" fy="6.75%" gradientTransform="matrix(.89055 0 0 1 .016 0)">
+      <stop offset="0%" stop-color="#FFF" stop-opacity=".1"/>
+      <stop offset="100%" stop-color="#FFF" stop-opacity="0"/>
+    </radialGradient>
+  </defs>
+  <g fill="none" fill-rule="evenodd">
+    <path fill="#252f3e" d="M156.726 169.706c0 5 .54 9.052 1.487 12.024 1.08 2.973 2.431 6.215 4.323 9.728.675 1.08.945 2.161.945 3.107 0 1.35-.81 2.702-2.566 4.053l-8.512 5.674c-1.216.81-2.432 1.216-3.512 1.216-1.351 0-2.702-.676-4.053-1.892a42 42 0 0 1-4.864-6.35c-1.351-2.296-2.702-4.863-4.188-7.97q-15.807 18.644-39.72 18.644c-11.348 0-20.4-3.243-27.02-9.727s-9.997-15.132-9.997-25.94c0-11.483 4.053-20.805 12.294-27.83s19.184-10.538 33.1-10.538c4.593 0 9.322.405 14.32 1.08s10.133 1.757 15.537 2.973v-9.862c0-10.268-2.162-17.428-6.35-21.616-4.323-4.189-11.618-6.215-22.021-6.215-4.729 0-9.592.54-14.591 1.756s-9.862 2.702-14.59 4.594c-2.162.945-3.784 1.486-4.73 1.756s-1.62.405-2.16.405c-1.892 0-2.838-1.35-2.838-4.188v-6.62c0-2.161.27-3.783.946-4.728s1.891-1.892 3.783-2.837q7.092-3.648 17.022-6.08c6.62-1.756 13.645-2.567 21.076-2.567 16.077 0 27.83 3.648 35.396 10.943 7.43 7.296 11.213 18.374 11.213 33.235v43.772zm-54.85 20.536c4.458 0 9.051-.811 13.915-2.432s9.187-4.594 12.835-8.647c2.161-2.567 3.782-5.404 4.593-8.646s1.351-7.16 1.351-11.754v-5.674c-3.918-.946-8.106-1.756-12.43-2.297s-8.51-.81-12.699-.81c-9.051 0-15.671 1.756-20.13 5.404s-6.62 8.781-6.62 15.536c0 6.35 1.622 11.078 5 14.32 3.242 3.378 7.97 5 14.185 5m108.485 14.59c-2.432 0-4.053-.405-5.134-1.35-1.08-.811-2.026-2.703-2.837-5.27L170.642 93.78c-.81-2.702-1.216-4.458-1.216-5.404 0-2.161 1.08-3.377 3.242-3.377h13.24c2.567 0 4.323.405 5.269 1.35 1.08.811 1.891 2.703 2.702 5.27l22.697 89.436 21.075-89.436c.676-2.702 1.486-4.459 2.567-5.27S243.19 85 245.622 85h10.808c2.567 0 4.323.405 5.404 1.35 1.081.811 2.027 2.703 2.567 5.27l21.346 90.517 23.372-90.517c.81-2.702 1.756-4.459 2.702-5.27 1.081-.81 2.837-1.35 5.27-1.35h12.563c2.162 0 3.378 1.08 3.378 3.377 0 .676-.135 1.351-.27 2.162s-.406 1.891-.946 3.377l-32.56 104.433q-1.215 4.053-2.836 5.268c-1.081.811-2.837 1.351-5.134 1.351h-11.619c-2.567 0-4.323-.405-5.404-1.35s-2.026-2.702-2.567-5.404l-20.94-87.14-20.805 87.004c-.676 2.702-1.486 4.459-2.567 5.404s-2.972 1.351-5.404 1.351zm173.604 3.648c-7.026 0-14.05-.81-20.806-2.432s-12.024-3.377-15.536-5.404c-2.162-1.216-3.648-2.567-4.188-3.783s-.811-2.566-.811-3.782v-6.89c0-2.838 1.08-4.189 3.107-4.189q1.216 0 2.432.406c.81.27 2.027.81 3.378 1.35a73.5 73.5 0 0 0 14.86 4.73c5.405 1.08 10.673 1.62 16.077 1.62 8.512 0 15.132-1.486 19.725-4.458s7.025-7.295 7.025-12.834c0-3.783-1.216-6.89-3.647-9.457s-7.026-4.864-13.646-7.026l-19.589-6.079c-9.862-3.107-17.158-7.7-21.616-13.78-4.458-5.945-6.755-12.565-6.755-19.59q0-8.511 3.648-14.996c2.432-4.323 5.674-8.106 9.727-11.078 4.053-3.107 8.646-5.404 14.05-7.025s11.079-2.297 17.023-2.297c2.972 0 6.08.135 9.052.54 3.107.406 5.944.946 8.781 1.487 2.702.675 5.269 1.35 7.7 2.161q3.648 1.216 5.675 2.432c1.891 1.08 3.242 2.162 4.053 3.378q1.216 1.62 1.216 4.458v6.35c0 2.837-1.08 4.323-3.107 4.323-1.081 0-2.838-.54-5.134-1.621q-11.551-5.27-25.94-5.27c-7.7 0-13.78 1.216-17.968 3.783s-6.35 6.485-6.35 12.024c0 3.783 1.352 7.025 4.054 9.592s7.7 5.134 14.86 7.43l19.185 6.08c9.727 3.108 16.752 7.43 20.94 12.97s6.215 11.889 6.215 18.914c0 5.81-1.216 11.078-3.513 15.672-2.432 4.593-5.674 8.646-9.862 11.888-4.188 3.378-9.187 5.81-14.996 7.566-6.08 1.891-12.43 2.837-19.32 2.837"/>
+    <path d="M409.499 274.139c-44.448 32.829-109.026 50.257-164.552 50.257-77.818 0-147.935-28.776-200.894-76.602-4.188-3.783-.405-8.916 4.593-5.944 57.283 33.234 127.94 53.364 201.03 53.364 49.31 0 103.486-10.267 153.338-31.343 7.43-3.377 13.78 4.864 6.484 10.268" class="aws-smile"/>
+    <path d="M428.007 253.063c-5.674-7.295-37.558-3.512-52.013-1.756-4.324.54-4.999-3.243-1.081-6.08 25.399-17.833 67.145-12.7 72.008-6.755 4.864 6.08-1.35 47.826-25.128 67.82-3.648 3.108-7.16 1.487-5.54-2.566 5.404-13.375 17.428-43.503 11.754-50.663" class="aws-smile"/>
+    <path fill="#456DA7" d="M2066.18 245.7v-34.16c36.24 0 64.26-35.87 50.43-73.98-5.1-14.1-16.3-25.37-30.5-30.5-38.1-13.8-73.9 14.2-73.9 50.44H1978c0-57.73 55.78-102.7 116.28-83.8 26.44 8.25 47.45 29.26 55.7 55.7 18.9 60.5-26.06 116.3-83.8 116.3"/>
+    <path fill="#456DA7" d="M2066.26 211.62h-34.06v-34.04h34.05v34.04m-34.05 26.18h-26.16v-26.2h26.16v26.16"/>
+    <path fill="#456DA7" d="M2006.06 211.62h-21.93V189.7h21.93zm-107.9 71.52h4.4c4.9 0 8.95.96 12 2.87 3.4 2.1 5.14 6 5.14 11.6 0 5.9-1.73 9.9-5.14 12.2-2.94 2-6.95 3-11.94 3h-4.47v-29.5zm22.25-2.9c-4.4-3.08-9.9-4.64-16.4-4.64h-14v44.58h14c6.5 0 12-1.65 16.5-4.9 2.4-1.7 4.4-4.12 5.7-7.14 1.4-3 2-6.55 2-10.54 0-3.94-.6-7.43-2-10.4-1.3-2.97-3.2-5.3-5.6-6.95zm17.5-5.18c-1.3 0-2.5.47-3.4 1.4-.9.9-1.4 2.06-1.4 3.4 0 1.36.5 2.53 1.4 3.47 1 .95 2.2 1.43 3.5 1.43s2.5-.48 3.5-1.43c1-.94 1.5-2.1 1.5-3.45 0-1.36-.5-2.5-1.4-3.4-.9-.95-2.1-1.43-3.4-1.43"/>
+    <g transform="translate(1932.944 288)">
+      <mask id="b" fill="#fff">
+        <use xlink:href="#a"/>
+      </mask>
+      <path fill="#456DA7" d="M.9 32.18h7.9V.78H.9m34.52 21.17c-1.4 1.57-3.16 2.33-5.42 2.33-2.27 0-4.03-.76-5.4-2.33-1.35-1.55-2.04-3.62-2.04-6.14 0-2.5.7-4.6 2.05-6.2C26 8.1 27.8 7.3 30 7.3c2.3 0 4.06.77 5.4 2.35 1.4 1.58 2.1 3.67 2.1 6.2 0 2.54-.7 4.6-2.05 6.16zM37.5 3.4C35.1 1.3 32.44.06 29.56.06c-4.36 0-8 1.5-10.77 4.48-2.9 2.95-4.3 6.75-4.3 11.28 0 4.45 1.4 8.23 4.2 11.26 2.8 2.92 6.4 4.42 10.8 4.42 3 0 5.6-.85 7.8-2.52v.72c0 2.6-.7 4.63-2.1 6.02q-2.1 2.1-5.7 2.1c-3.7 0-6-1.43-8.7-5.2l-5.4 5.17.1.2c1.1 1.6 2.9 3.2 5.3 4.7 2.3 1.5 5.3 2.3 8.7 2.3 4.7 0 8.5-1.5 11.2-4.3C43.5 37.8 45 34 45 29.3V.8h-7.7v2.6z" mask="url(#b)"/>
+    </g>
+    <path fill="#456DA7" d="M1984.97 320.18h7.9v-31.4h-7.9m4.03-13.72c-1.35 0-2.52.47-3.45 1.4-.95.9-1.43 2.06-1.43 3.4 0 1.36.48 2.53 1.42 3.47.94.95 2.1 1.43 3.46 1.43 1.35 0 2.5-.48 3.46-1.43.94-.94 1.42-2.1 1.42-3.45 0-1.36-.48-2.5-1.42-3.4-.95-.95-2.1-1.43-3.46-1.43m21.2 5.25h-7.8v8.5h-4.5v7.2h4.5v13.03c0 4.08.83 7 2.44 8.68 1.6 1.7 4.47 2.6 8.5 2.6 1.3 0 2.6 0 3.85-.1h.3V313l-2.7.14c-1.9 0-3.2-.33-3.8-1-.6-.65-.9-2.05-.9-4.14v-12h7.3v-7.22h-7.4v-8.48m44.4 39.88h7.9V275.6h-7.9m87.7 33.36c-1.4 1.58-2.9 2.95-4 3.67-1.1.7-2.5 1.06-4.1 1.06-2.4 0-4.2-.9-5.7-2.6-1.6-1.8-2.3-4-2.3-6.7s.7-4.9 2.2-6.6c1.5-1.8 3.3-2.6 5.6-2.6 2.5 0 5.2 1.6 7.5 4.3l5.2-5c-3.4-4.5-7.8-6.5-13-6.5-4.4 0-8.1 1.6-11.2 4.7s-4.6 7-4.6 11.7 1.5 8.6 4.6 11.7c3 3.1 6.8 4.7 11.1 4.7 5.7 0 10.3-2.5 13.4-7l-5.2-5m15.1-8.4c.4-1.5 1.1-2.8 2-3.8 1-1.1 2.4-1.6 4.1-1.6 1.9 0 3.4.6 4.4 1.6.9 1 1.4 2.2 1.5 3.7h-12zm17.3-7.4c-1.1-1.6-2.7-2.8-4.6-3.8-1.9-.9-4.1-1.4-6.5-1.4q-6.6 0-10.8 4.8c-2.6 3.1-4 7.1-4 11.7 0 4.7 1.4 8.7 4.3 11.7s6.7 4.5 11.4 4.5c5.3 0 9.7-2.2 13-6.4l.2-.3-5.1-5-1.8 1.8c-.8.7-1.5 1.3-2.3 1.7-1.2.6-2.5.9-4 .9-2.2 0-4-.7-5.4-2-1.3-1.2-2-2.8-2.2-4.8h21l.1-2.9c0-2.1-.3-4-.8-5.9-.6-1.8-1.4-3.6-2.5-5.1zm16.3 15c.9-.7 2.1-1 3.8-1 1.9 0 3.9.4 6 1.1v3q-2.7 2.4-6.9 2.4c-1.4 0-2.5-.3-3.2-.9-.8-.6-1.1-1.3-1.1-2.3 0-1.1.4-1.9 1.3-2.5zm14-17.1c-2.4-2.1-5.7-3.1-9.9-3.1-2.6 0-5.1.6-7.3 1.7-2.1 1-4.1 2.8-5.4 5l.1.1 5 4.8c2.1-3.3 4.4-4.5 7.5-4.5 1.6 0 3 .5 4 1.3s1.5 1.9 1.5 3.3v1.5c-1.9-.6-3.9-.9-5.8-.9-3.9 0-7.1.9-9.5 2.7s-3.6 4.5-3.6 7.8c0 3 1 5.3 3.1 7.1 2.04 1.7 4.6 2.6 7.62 2.6 3 0 5.8-1.3 8.4-3.3v2.6h7.8v-20c0-3.8-1.2-6.8-3.6-8.9zm34 .6c-2.2-2.5-5.3-3.7-9.2-3.7-3.2 0-5.7.9-7.6 2.7v-2h-7.7V320h7.9v-17.3c0-2.4.5-4.3 1.7-5.63 1.1-1.34 2.6-2 4.6-2 1.8 0 3.1.6 4.1 1.8s1.5 2.86 1.5 4.93V320h7.9v-18.2c0-4.35-1.1-7.8-3.3-10.23m-208.5 16.5c.9-.64 2.1-.95 3.7-.95 1.9 0 3.9.4 6 1.14v3.1q-2.55 2.4-6.9 2.4c-1.4 0-2.4-.3-3.2-.9-.7-.6-1.1-1.35-1.1-2.3 0-1.08.4-1.9 1.3-2.5zm14-17.07c-2.4-2.03-5.7-3.07-9.9-3.07-2.6 0-5.1.57-7.3 1.7-2 1.04-4.1 2.77-5.3 5.03v.1l5 4.84c2-3.33 4.4-4.5 7.4-4.5 1.6 0 3 .46 4.1 1.33 1 .87 1.5 1.97 1.5 3.37v1.5c-2-.6-3.9-.9-5.8-.9-4 0-7.2.94-9.5 2.76-2.4 1.87-3.7 4.5-3.7 7.88 0 2.94 1 5.33 3.05 7.12 2.1 1.7 4.65 2.6 7.66 2.6 3 0 5.8-1.25 8.4-3.3v2.56h7.8V300c0-3.82-1.2-6.8-3.63-8.87zm46.5-8.1c-8.2 0-14.9 6.65-14.9 14.85s6.6 14.86 14.8 14.86 14.8-6.6 14.8-14.8-6.7-14.9-14.9-14.9zm0 37.83c-12.7 0-23-10.3-23-23s10.3-23 22.9-23 22.9 10.3 22.9 22.97c0 12.7-10.3 23-23 23z"/>
+    <g fill-rule="nonzero">
+      <path fill="#737373" d="M1183.98 298.84c.18-12.7 10.6-22.87 23.36-22.8 5.88-.1 11.55 2.17 15.73 6.3l-4.54 4.36c-3-2.88-7.02-4.48-11.2-4.45-4.4 0-8.65 1.77-11.74 4.9-3.1 3.15-4.8 7.4-4.7 11.8-.1 4.4 1.6 8.66 4.7 11.8 3 3.14 7.3 4.92 11.7 4.92 4.3.17 8.5-1.5 11.6-4.57 2-2.16 3.2-4.93 3.4-7.86h-15v-6.46h21q.3 1.95.3 3.9c.2 5.4-1.8 10.62-5.4 14.6-4.2 4.3-9.9 6.62-15.9 6.4-12.8.06-23.2-10.13-23.4-22.84zm61.72-6.57c-8.15.02-14.75 6.6-14.74 14.72 0 8.1 6.63 14.7 14.78 14.6 8.16 0 14.76-6.6 14.76-14.7.07-4-1.47-7.7-4.26-10.5-2.8-2.8-6.6-4.3-10.54-4.3zm0 23.6c-2.3-.04-4.5-1-6.1-2.7a8.5 8.5 0 0 1-2.3-6.22c0-4.62 3.77-8.36 8.4-8.36 4.64 0 8.4 3.7 8.4 8.3.12 2.3-.7 4.5-2.3 6.2-1.57 1.7-3.78 2.6-6.1 2.7v-.1zm32.35-23.6c-8.15.03-14.74 6.63-14.72 14.74.02 8.2 6.64 14.7 14.8 14.7 8.14 0 14.75-6.6 14.75-14.7.06-3.9-1.5-7.7-4.28-10.5-2.8-2.7-6.6-4.3-10.55-4.2zm0 23.6c-2.32-.04-4.52-1-6.1-2.7a8.5 8.5 0 0 1-2.3-6.22c0-4.62 3.76-8.36 8.4-8.36 4.63 0 8.4 3.7 8.4 8.3.1 2.3-.7 4.5-2.3 6.2-1.58 1.7-3.78 2.6-6.1 2.7v-.1zm39.67-22.7v2.4h-.22c-2-2.17-4.83-3.37-7.78-3.3-7.9.34-14.13 6.82-14.13 14.7 0 7.86 6.2 14.34 14.1 14.7 2.9.06 5.8-1.16 7.8-3.36h.2v2.2c0 5.6-3 8.7-7.9 8.7-3.3-.1-6.2-2.1-7.4-5.2l-5.6 2.4c2.1 5.3 7.3 8.8 13.1 8.7 7.6 0 14-4.4 14-15.3v-26.4h-6.3zm-7.44 22.72c-2.3-.1-4.46-1.1-6-2.7-1.56-1.7-2.36-3.9-2.23-6.2-.12-2.3.68-4.5 2.22-6.2a8.64 8.64 0 0 1 6-2.8c2.26.1 4.36 1.1 5.85 2.8 1.48 1.7 2.22 3.9 2.05 6.1.14 2.2-.62 4.4-2.1 6s-3.56 2.6-5.8 2.8zm18.08-38.3h6.5v43.1h-6.5zm24.24 38.3c-3.07.1-5.9-1.7-7.15-4.5l19.76-8.2-.6-1.7c-1.8-5.5-6.8-9.2-12.6-9.4-3.8 0-7.5 1.5-10.2 4.3-2.6 2.8-4 6.5-3.8 10.3-.1 3.9 1.5 7.7 4.2 10.4 2.8 2.8 6.6 4.3 10.5 4.2 5 0 9.6-2.4 12.3-6.5l-5-3.4c-1.5 2.5-4.2 4-7.2 4zm-.5-18c2.35-.3 4.58 1 5.6 3.1l-13.2 5.5c-.18-2.2.53-4.3 1.96-6 1.44-1.7 3.47-2.7 5.65-2.8zm25.92 2.9c-.13-5.6 2.02-10.9 5.95-14.9s9.3-6.1 14.87-6c5.63-.1 11.03 2.2 14.7 6.5l-3.57 3.4c-2.7-3.4-6.86-5.3-11.2-5.1-4.22-.1-8.3 1.6-11.25 4.6s-4.5 7.1-4.3 11.3c-.17 4.1 1.4 8.2 4.33 11.2 2.94 3 6.98 4.6 11.18 4.5 4.72 0 9.2-2 12.3-5.6l3.6 3.5c-5.77 6.5-14.96 8.7-23.1 5.7-8.12-3.1-13.5-10.8-13.5-19.5zm40.63 19.9v-39.9h5.15v39.9m32.03-13.7c0 7.7-6.3 14-14.1 14-7.77 0-14.07-6.3-14.07-14.1 0-7.7 6.3-14 14.08-14 7.8 0 14.1 6.3 14.1 14zm-5.15 0c.27-3.4-1.38-6.6-4.26-8.3s-6.5-1.8-9.38 0c-2.88 1.7-4.53 4.9-4.26 8.3 0 4.9 4.02 8.9 9 8.9 4.96 0 9-4 9-9h-.1zm28.4 13.6V317h-.33c-1.93 2.9-5.18 4.66-8.68 4.68-7.05 0-10.46-4.73-10.46-11.47v-16.7h5.2v15.9c0 5.6 2.8 7.7 6.8 7.7 4.3-.3 7.5-4 7.2-8.3v-15.1h5.2V321h-5l.1-.07zm9.07-13.7c-.35-7.6 5.4-14 12.98-14.6 3.7-.1 7.23 1.6 9.35 4.7h.22l-.22-3.8v-12.6h5.15v39.9h-4.93V317h-.22a10.99 10.99 0 0 1-9.35 4.68c-7.57-.54-13.33-7-12.98-14.54zm22.6 0c.4-3.4-1.2-6.6-4.05-8.4a8.77 8.77 0 0 0-9.35 0c-2.86 1.8-4.43 5-4.05 8.4-.38 3.3 1.2 6.6 4.05 8.4 2.86 1.7 6.5 1.7 9.35 0 2.86-1.8 4.44-5.1 4.06-8.4zm18.95 13.6v-39.9h13.65c3.25-.1 6.4 1.1 8.77 3.3 2.35 2.2 3.7 5.3 3.77 8.5-.1 3.2-1.5 6.3-3.8 8.6-2.4 2.2-5.5 3.4-8.8 3.3h-8.4v16.1h-5.2zm13.77-21.1c3.86 0 7-3.2 7-7 0-3.9-3.14-7-7-7h-8.76v13.9h8.8zm16.03 21v-39.9h5.15v39.9m4.42-8.3c0-6.2 5.6-9.6 12.03-9.6 2.58-.1 5.14.5 7.44 1.7v-.8c-.2-3.3-2.57-6-5.78-6.6-3.2-.7-6.46.9-7.93 3.8l-4.7-2c2.58-5 8.2-7.6 13.67-6.4 5.48 1.2 9.44 6 9.67 11.5v16.5h-4.93V317h-.22c-1.97 3.03-5.4 4.8-9 4.68-2.6.24-5.2-.6-7.14-2.34a9.26 9.26 0 0 1-3.1-6.8zm19.58-3.5c-1.93-1.3-4.23-1.9-6.54-1.8-5.4 0-7.5 2.8-7.5 5.4.4 2.7 2.9 4.6 5.6 4.3 4.5 0 8.2-3.5 8.4-8h.1zm12.23 3.4v-14h-4.8v-4.7h4.8V285h5.15v8.37h6.7v4.66h-6.7V312c0 3.06 1.3 4.46 3.7 4.46.8.03 1.6-.12 2.34-.45l1.8 4.4c-1.32.6-2.73.8-4.15.8-2.4.3-4.82-.5-6.55-2.2a7.94 7.94 0 0 1-2.3-6.5zm33.46-31.1-1.7 4.4c-.74-.4-1.54-.5-2.35-.5-1.3-.1-2.6.3-3.4 1.3-.9.9-1.4 2.1-1.2 3.4v3.5h6.9v4.7h-7.2v22.6h-5.2V298h-5.2v-4.7h5.1v-3.63c-.1-2.56.9-5.03 2.8-6.78 1.8-1.8 4.4-2.7 6.9-2.4 1.5-.1 2.9.1 4.3.7zm28 25.7c0 7.7-6.3 14-14.1 14-7.76 0-14.06-6.3-14.06-14 0-7.8 6.3-14 14.08-14s14.1 6.3 14.1 14zm-5.14 0c.27-3.4-1.38-6.6-4.26-8.4s-6.5-1.8-9.38 0c-2.88 1.7-4.53 5-4.26 8.3-.27 3.3 1.38 6.6 4.26 8.3s6.5 1.8 9.38 0 4.53-5 4.26-8.3zm9.3 13.6V293h4.92v4.47h.22a9.03 9.03 0 0 1 7.95-5.14c1.3 0 2.6.2 3.8.7l-2 4.8c-.9-.3-1.9-.47-2.8-.4-2 .06-3.9.96-5.3 2.46s-2 3.4-1.9 5.4v14.9h-5.1zm19.72-27.3h4.92v3.8h.26c1.88-2.8 5-4.5 8.4-4.7 3.7-.3 7.2 1.8 8.66 5.2 2.06-3.3 5.7-5.3 9.57-5.2 6.72 0 9.8 4.7 9.8 11.5v16.7h-5.15v-15.9c0-5.6-2.2-7.6-6.1-7.6-3.92 0-7 4.2-7 8.4v15.1h-5.15v-15.9c0-5.6-2.18-7.6-6.1-7.6-3.9 0-7 4.3-7 8.4v15.1h-5.14V293z"/>
+      <g transform="translate(1355.296 68)">
+        <path fill="#FBBC05" d="M131 143.23 110.5 179H56.8c-4.8 0-9.22-2.57-11.6-6.74l-43.43-76a13.44 13.44 0 0 1 0-13.36L18.3 54l20.4 35.58 30.75 53.65z"/>
+        <path fill="#EA4335" d="m200.22 96.3-43.44 75.96c-2.38 4.17-6.8 6.74-11.6 6.74H112l20.5-35.75 30.8-53.63L132.5 36h40.86l26.85 46.96c2.4 4.12 2.4 9.2.1 13.33z"/>
+        <path fill="#4285F4" d="M173 35.6H70.3L39.47 89 19 53.58 45.98 6.7C48.38 2.57 52.8 0 57.6 0h87.15c4.8 0 9.24 2.56 11.63 6.7z"/>
+        <path fill="#E0E0E0" d="m132 36 31 54-31 54H70L39 90l31-54z"/>
+        <circle cx="101" cy="90" r="27" fill="#FFF"/>
+        <path fill="#FFF" d="M45.98 7.8c2.4-4.15 6.83-6.7 11.63-6.7h87.2c4.8 0 9.3 2.56 11.7 6.7l16 27.7h.7L156.4 6.7A13.44 13.44 0 0 0 144.76 0H57.6C52.8 0 48.38 2.56 46 6.7L19 53.44l.32.56z" opacity=".2"/>
+        <path fill="#1A237E" fill-opacity=".2" d="m39 90 30.72-53.88H172l-.64-1.12H69.72L39 88.88"/>
+        <path fill="#FFF" d="M1.75 83.92 18.3 55.1l20.4 35.46L69.44 144h60.9l.65-1.12H69.4L38.7 89.45 18.3 54 1.74 82.8C.5 85-.1 87.5 0 90c.1-2.13.7-4.22 1.75-6.08" opacity=".2"/>
+        <path fill="#BF360C" d="M111.94 177.75H57.5c-4.8 0-9.24-2.6-11.63-6.8L2.35 94.33C1.3 92.43.7 90.33.6 88.16c-.1 2.55.5 5.08 1.75 7.3l43.52 76.63c2.4 4.2 6.82 6.8 11.62 6.8h53.8l.6-1.2z" opacity=".2"/>
+        <path fill="#3E2723" d="M163.6 89.72 133 36.22h-.63l30.57 53.5m36.73 5.54-43.17 75.8a13.25 13.25 0 0 1-11.52 6.72h-32.33l-.65 1.12h32.98c4.76 0 9.15-2.57 11.52-6.73l43.17-75.8c1.24-2.2 1.84-4.7 1.73-7.2-.1 2.13-.68 4.22-1.73 6.1z" opacity=".2"/>
+        <path fill="#FFF" d="m172.98 37.33 26.7 46.85a13.7 13.7 0 0 1 1.72 6.1c.12-2.53-.5-5.03-1.73-7.22l-26.7-46.85H132.4l.63 1.2m-.63 107 31.2-54.6h-.63l-30.58 53.5-20.4 35.6h.6" opacity=".2"/>
+        <path fill="url(#c)" d="M199.22 82.82 172.3 35.8 155.67 6.75C153.27 2.57 148.85 0 144.04 0h-87.1c-4.8 0-9.23 2.58-11.62 6.75L1.77 82.82a13.49 13.49 0 0 0 0 13.36l43.55 76.07c2.4 4.18 6.82 6.75 11.63 6.75h87.1c4.8 0 9.24-2.58 11.63-6.75l43.55-76.07a13.49 13.49 0 0 0 0-13.36z"/>
+      </g>
+    </g>
+    <g fill="#0078D7" fill-rule="nonzero">
+      <path d="M854.5 174.24c-7.03 0-13 4.2-15.8 10.16H738.24c-16.86 0-30.9-13.67-30.9-30.85 0-17.2 13.7-30.86 30.9-30.86h14.06c.7-3.6 1.75-7.1 3.16-10.2.7-1.1 1.05-2.5 1.75-3.5 7.1-12.3 20.4-20.4 35.5-20.4 13.7 0 25.7 6.6 33 16.5 4.3-2.1 8.8-3.5 13.4-4.6-9.9-15.4-26.7-25.5-46.4-25.5-22.8 0-42.5 14-50.5 34h-3.8c-24.6.3-44.6 20.3-44.6 44.9 0 24.5 20 44.5 44.6 44.5h100.8c2.8 5.9 8.8 10.1 15.8 10.1 9.5 0 17.2-7.7 17.2-17.2-.3-9.5-8.1-17.2-17.5-17.2z"/>
+      <path d="M907.98 251c30.14 0 56.07-25.66 56.07-55.88 0-30.23-24.18-54.48-54.32-54.83-10.16-20.4-30.83-34.1-55-34.1-29.45 0-53.97 20.7-59.93 48.1-14.37 1.4-26.63 9.1-34.34 20h73.23c4.9-6.3 12.6-10.2 21.3-10.2 15 0 27.3 12.3 27.3 27.4s-12.3 27.4-27.4 27.4c-8.8 0-16.1-3.9-21.4-10.2H752c3.16 23.2 21.73 42.2 45.9 42.2h110.04zm-230.33 77h-4.67v-28.08c0-2.12 0-4.95.23-8.02-.4 1.9-.9 3.3-1.1 4L657.8 328h-2.32l-14-31.85c-.47-.95-.7-2.36-1.17-4.25V328h-4.6v-41.76h6.3l12.6 29.02c1 2.12 1.7 4 1.9 4.95h.3c1-2.3 1.4-4 2.1-5.1l12.8-29h6.1v42zm11-37.82c-.92 0-1.62-.23-2.08-.95-.46-.7-.92-1.42-.92-2.14 0-.8.23-1.7.92-2.2.7-.7 1.4-1 2.08-1 .92 0 1.6.2 2.08.9.7.7.92 1.4.92 2.1 0 .9-.23 1.6-.92 2.1-.47.7-1.16.9-2.08.9zm2.3 37.82h-4.6v-30.2h4.6zm29.45-2.1c-2.36 1.4-4.97 2.1-8.3 2.1-4.26 0-7.8-1.4-10.42-4.2-2.6-2.8-4.03-6.3-4.03-10.72 0-4.9 1.42-8.62 4.27-11.65 3.32-2.8 6.87-4.43 11.6-4.43 2.62 0 5 .47 7.13 1.63v4.9c-2.14-1.64-4.5-2.33-7.12-2.33-3.08 0-5.45 1.16-7.58 3.26q-2.85 3.15-2.85 8.4c0 5.25.95 6.05 2.85 8.15s4.27 3.1 7.35 3.1c2.6 0 4.98-.9 7.35-2.5v4.4h-.24zm21.25-22.55c-.96-.7-2.15-.93-3.82-.93-2.15 0-3.82.93-5.26 2.8-1.43 1.85-2.15 4.4-2.15 7.66V328h-4.77v-29.53h4.77v6.04c.72-2 1.68-3.7 3.1-4.8 1.44-1.1 3.1-1.6 4.78-1.6 1.2 0 2.15.3 2.87.5v4.9h.48zM757.03 328c-4.4 0-7.9-1.4-10.44-4.2-2.6-2.8-4-6.3-4-10.95 0-4.9 1.4-8.86 3.9-11.65 2.5-2.8 6.5-4.2 11.1-4.2 4.4 0 7.9 1.4 10.2 3.96 2.5 2.8 3.7 6.53 3.7 11.2 0 4.65-1.4 8.38-4 11.18-2.8 3.03-6.3 4.66-10.7 4.66zm.23-27.04c-3 0-5.33.93-7.2 3.03-1.84 2.1-2.54 4.9-2.54 8.6 0 3.5.93 6.3 2.55 8.1 1.86 2.1 4.18 3 7.2 3 3 0 5.33-1 6.95-3.1 1.63-1.9 2.56-4.7 2.56-8.4s-.93-6.5-2.56-8.4c-1.62-1.9-3.94-3.1-6.96-3.1zm18.4 25.18V321c2.54 1.87 5.32 2.8 8.33 2.8 4.1 0 6.2-1.4 6.2-4.2 0-.7-.3-1.4-.5-2.1l-1.4-1.4c-.7-.45-1.4-.7-2.1-1.15-.7-.24-1.7-.7-2.6-.93-1.4-.47-2.3-.94-3.5-1.64-1-.46-1.9-1.16-2.6-1.86s-1.2-1.4-1.4-2.33c-.3-1-.5-1.9-.5-3.1 0-1.4.2-2.6.9-3.8.5-.5 1.2-1.4 2.3-2.1 1.2-.7 2.3-1.2 3.5-1.7 1.4-.5 2.8-.7 4.2-.7 2.5 0 4.8.4 6.7 1.4v4.7c-2.1-1.4-4.6-2.1-7.4-2.1-.9 0-1.6 0-2.3.2s-1.4.4-1.9.9c-.5.4-.9.7-1.2 1.4-.3.4-.5 1.1-.5 1.6 0 .7.2 1.4.4 1.8s.7.9 1.1 1.4c.4.4 1.1.7 1.8 1.1.7.3 1.6.7 2.5 1.2 1.4.5 2.6.9 3.5 1.6.9.4 1.8 1.1 2.5 1.8s1.4 1.4 1.6 2.3c.5.9.7 1.8.7 3 0 1.4-.2 2.8-.9 3.7-.7 1.1-1.4 1.8-2.6 2.5s-2.3 1.2-3.7 1.6c-1.4.2-2.8.5-4.4.5-2.6 0-5.4-.7-7.5-1.9zm37.37 1.86c-4.4 0-7.9-1.4-10.44-4.2-2.6-2.8-4-6.3-4-10.95 0-4.9 1.4-8.86 3.9-11.65 3-2.8 6.5-4.2 11.1-4.2 4.4 0 7.9 1.4 10.2 3.96 2.5 2.8 3.7 6.53 3.7 11.2 0 4.65-1.4 8.38-4 11.18-2.8 3.03-6.3 4.66-10.7 4.66zm.23-27.04c-3 0-5.33.93-7.2 3.03-1.84 2.1-2.54 4.9-2.54 8.6 0 3.5.93 6.3 2.55 8.1 1.86 2.1 4.18 3 7.2 3 3 0 5.33-1 6.95-3.1 1.63-1.9 2.56-4.7 2.56-8.4s-.93-6.5-2.56-8.4c-1.4-1.9-3.94-3.1-6.96-3.1zm53.4.94v-4.2h-7.7v-8.64l-4.8 1.63v7.2h-13.2v-4.7c0-4.2 1.7-6.3 5.05-6.3 1.2 0 2.2.2 3.2.7v-4.2c-.9-.3-2.1-.5-3.6-.5-2.6 0-5 .9-6.9 2.8-1.9 1.8-2.6 4.2-2.6 7.2v4.6h-5.3v3.9h5.3V327h4.8v-25.4H854v17.47c0 5.82 2.64 8.62 7.92 8.62 1.9 0 3.34-.3 4.54-1V323c-.93.7-1.9.95-3.1.95-1.7 0-2.63-.5-3.35-1.2-.7-.9-1-2.3-1-4.2v-16.7h7.7zm52 26.1h-5.54l-4.57-11.86H890.5L886.2 328h-5.53l16.6-42h5.04l16.4 42zm-11.56-16.37-6.73-17.8q-.36-.705-.72-2.85c-.24 1.2-.48 2.14-.72 2.85l-6.5 17.8z"/>
+      <path d="m941.65 299.42-17.3 24.33h17.07V328h-23.77v-1.42l17.3-24.33h-15.68V298h22.38m29.75 29.3h-4.75v-4.6c-1.9 3.45-5 5.3-9.3 5.3-7.13 0-10.7-4.15-10.7-12.46V298h4.76v16.62c0 6.23 2.4 9.23 7.4 9.23 2.4 0 4.3-.93 5.7-2.54 1.5-1.6 2.4-3.9 2.4-6.6V298h4.8v29.3h-.2zm23.25-23.95c-.97-.7-2.18-.93-3.64-.93-2.1 0-3.8.93-5.3 2.8-1.4 1.85-2.2 4.4-2.2 7.66V328h-4.8v-29.53h4.9v6.04c.8-2 1.7-3.7 3.2-4.8a8.2 8.2 0 0 1 4.9-1.6c1.2 0 2.2.3 2.9.5v4.9h.3zm27 10.32h-21.04c0 3.3 1 5.88 2.6 7.75 1.7 1.88 4.1 2.6 7.1 2.6 3.3 0 6.4-1.2 9.3-3.3v4.46c-2.6 1.88-6.1 2.82-10.4 2.82-4.2 0-7.5-1.4-9.9-4-2.3-2.58-3.5-6.57-3.5-11.27s1.4-8.45 4-11.27 5.9-4.46 9.7-4.46 6.9 1.17 9 3.76c2.1 2.58 3.3 6.1 3.3 10.33v2.5zm-4.97-4c0-2.8-.7-4.92-1.9-6.33-1.4-1.4-3.06-2.35-5.42-2.35-2.37 0-4.26.7-5.68 2.3-1.65 1.6-2.6 3.7-2.83 6.3h15.83z"/>
+    </g>
+    <path fill="#BB2C23" d="m3230.23 200.6-19.15-18.98c.05 0 .15-.06.2-.06l19.2 19c-.1.05-.2.05-.25.05z"/>
+    <path fill="#BD2D24" d="m3230.48 200.56-19.2-19c.26 0 .5-.1.72-.15l19.2 19c-.26.1-.5.2-.72.2z"/>
+    <path fill="#C32E24" d="m3231.2 200.4-19.2-19c.4-.1.7-.24 1.07-.4l19.15 19c-.3.16-.67.3-1.02.4"/>
+    <path fill="#BD2D24" d="m3232.22 200-19.15-19c.25-.15.45-.25.66-.4l19.1 19c-.2.15-.4.3-.6.4z"/>
+    <path fill="#BB2C23" d="m3232.83 199.6-19.15-19c.15-.1.25-.2.35-.3l19.15 19c-.1.1-.2.2-.35.3"/>
+    <path fill="#B62B24" d="m3233.18 199.3-19.15-19c.1-.06.2-.17.3-.27l19.16 19c-.1.1-.2.2-.4.26z"/>
+    <path fill="#B42924" d="m3233.5 199.03-19.16-19c.05-.1.15-.15.2-.25l19.2 19-.25.25z"/>
+    <path fill="#B02824" d="m3233.74 198.78-19.2-19c.1-.1.16-.16.2-.26l19.2 19c-.1.1-.14.15-.2.26"/>
+    <path fill="#AD2823" d="m3233.95 198.52-19.2-19c.1-.05.15-.15.2-.25l19.15 19.05c-.05.05-.1.15-.15.2"/>
+    <path fill="#A82722" d="m3234.1 198.32-19.15-19.05c.05-.05.1-.16.15-.2l19.15 19c-.05.04-.1.14-.15.25"/>
+    <path fill="#A52522" d="m3234.25 198.06-19.15-19c.05-.1.1-.15.16-.25l19.15 19c0 .1-.1.2-.1.3z"/>
+    <path fill="#A02421" d="m3234.4 197.8-19.14-19c0-.1.05-.15.1-.25l19.15 19c0 .1 0 .2-.1.26z"/>
+    <path fill="#9B2420" d="m3234.5 197.55-19.14-19c.05-.05.1-.15.1-.25l19.15 19c0 .1 0 .2-.1.25z"/>
+    <path fill="#982420" d="m3234.6 197.35-19.14-19.05c.05-.06.1-.16.1-.26l19.15 19.05s0 .1-.1.2z"/>
+    <path fill="#952220" d="m3234.7 197.1-19.14-19.06c.05-.05.05-.15.1-.25l19.15 18.9c0 .1 0 .2-.1.3z"/>
+    <path fill="#912120" d="m3234.8 196.78-19.14-19c0-.05.05-.15.05-.25l19.3 19c0 .1 0 .2-.1.25z"/>
+    <path fill="#8E201E" d="m3234.92 196.53-19.2-19c.04-.1.04-.2.1-.3l19.15 19c0 .1-.05.2-.05.3"/>
+    <path fill="#8B1F1E" d="m3234.97 196.22-19.15-19c0-.1 0-.2.05-.35l19.15 19c0 .1-.05.25-.05.35"/>
+    <path fill="#871F1C" d="m3235.02 195.86-19.15-19v-.35l19.15 19v.4z"/>
+    <path fill="#841F1C" d="m3235.02 195.46-19.15-18.95v-.1l19.15 19.1v.1z"/>
+    <use xlink:href="#reuse-0"/>
+    <use xlink:href="#reuse-0"/>
+    <path fill="#871F1C" d="m3235.02 195.4-19.15-19.04v-6.64l19.15 18.94"/>
+    <path fill="#C32E24" d="m3159.02 206.85-19.15-19 71.26-6.23 19.1 19"/>
+    <path fill="#912120" d="m3155.5 205.62-19.14-19c.05.1.1.15.2.15l19.15 19.05-.2-.2z"/>
+    <path fill="#952220" d="m3155.7 205.82-19.14-19.05.3.3 19.16 19c-.1-.1-.2-.14-.3-.25z"/>
+    <path fill="#982420" d="m3156.02 206.08-19.15-19c.05.05.15.1.25.15l19.2 19z"/>
+    <path fill="#9B2420" d="m3156.32 206.23-19.2-19 .3.16 19.16 19c-.1 0-.2-.1-.26-.2z"/>
+    <path fill="#A02421" d="m3156.58 206.4-19.15-19c.1.04.2.1.25.14l19.2 19-.3-.15z"/>
+    <path fill="#A52522" d="m3156.88 206.54-19.2-19c.1 0 .2.05.3.1l19.16 19c-.1-.05-.15-.05-.26-.1"/>
+    <path fill="#A82722" d="m3157.14 206.64-19.15-19c.1.05.2.05.3.1l19.1 19c-.1-.05-.2-.05-.3-.1z"/>
+    <path fill="#AD2823" d="m3157.44 206.74-19.15-19c.1 0 .2.06.3.06l19.1 19c-.1 0-.2-.06-.3-.06z"/>
+    <path fill="#B02824" d="m3157.75 206.8-19.15-19c.1 0 .2.05.3.05l19.16 19c-.1 0-.2 0-.3-.06z"/>
+    <path fill="#B42924" d="m3158.06 206.85-19.16-19h.36l19.15 19.05c-.1 0-.2-.05-.3-.05z"/>
+    <path fill="#B62B24" d="m3158.4 206.9-19.14-19.05c.1.05.26.05.36.05l19.2 19h-.4z"/>
+    <path fill="#BB2C23" d="m3158.82 206.9-19.2-19c.1-.05.15-.05.25-.05l19.15 19c-.1.05-.15.05-.2.05"/>
+    <path fill="#7F1D1C" d="m3127.7 235.6-19.15-19.05c-1.38-1.33-2.24-3.17-2.4-5.26l19.15 18.9c.16 2.1 1.07 4 2.4 5.3z"/>
+    <path fill="#841F1C" d="m3125.3 230.3-19.15-19c-.05-.27-.05-.52-.05-.73l19.2 18.95c-.05.26 0 .5 0 .77z"/>
+    <path fill="#D93023" d="m3263.95 186.1-.05 31.27c0 5.05-4.13 9.55-9.22 10l-120.3 10.58c-5.05.4-9.18-3.32-9.13-8.43l.05-31.2 28.88-2.56v6.7c0 2.6 2.14 4.6 4.8 4.33l71.25-6.3c2.65-.3 4.8-2.6 4.8-5.2v-6.7l28.92-2.6z"/>
+    <use xlink:href="#reuse-1"/>
+    <use xlink:href="#reuse-1"/>
+    <path fill="#871F1C" d="m3125.3 229.52-19.2-18.9.1-31.25 19.16 18.95"/>
+    <path fill="#E63F46" d="m3263.75 133.45.2 45.97-28.93 2.55-.2-45.96"/>
+    <path fill="#E23535" d="m3263.75 133.45.2 45.97-28.93 2.55-.2-45.96"/>
+    <path fill="#871F1C" d="m3235.07 181.97-19.15-18.94-.2-45.97 19.15 19"/>
+    <use xlink:href="#reuse-2"/>
+    <use xlink:href="#reuse-2"/>
+    <path fill="#E63F46" d="m3154.08 143.1.16 45.97-28.94 2.56-.2-46.02"/>
+    <path fill="#E23535" d="m3154.08 143.1.16 45.97-28.94 2.56-.2-46.02"/>
+    <path fill="#871F1C" d="m3125.36 191.63-19.16-19-.2-45.92 19.15 18.9"/>
+    <path fill="#871F1C" d="M3125.1 145.66 3106 126.7l28.98-2.54 19.1 18.95m80.94-13.9-19.15-18.9v-5.8l19.15 19"/>
+    <path fill="#841F1C" d="m3235.02 123.44-19.15-19v-.35l19.15 19v.3z"/>
+    <path fill="#7F1D1C" d="m3235.02 123.1-19.15-18.96c-.1-1.18-.56-2.15-1.28-2.86l19.1 19c.7.7 1.2 1.68 1.3 2.8z"/>
+    <path fill="#BB2C23" d="m3254.83 88-19.15-19h.4l19.16 19h-.4z"/>
+    <path fill="#B62B24" d="m3255.24 88.05-19.15-19c.2-.05.5-.05.7 0l19.1 19h-.7z"/>
+    <path fill="#B42924" d="m3255.95 88-19.15-19c.26 0 .46 0 .66.05l19.2 19c-.25-.05-.45-.05-.7-.05z"/>
+    <path fill="#B02824" d="m3256.67 88.05-19.2-19c.25 0 .45.05.66.05l19.15 19.05c-.2-.05-.4-.1-.6-.1z"/>
+    <path fill="#AD2823" d="m3257.28 88.15-19.15-19.05.56.16 19.1 19c-.2-.06-.4-.1-.6-.1z"/>
+    <path fill="#A82722" d="m3257.84 88.25-19.15-19 .5.16 19.1 19-.6-.1z"/>
+    <path fill="#A52522" d="m3258.4 88.4-19.15-19c.2.06.35.16.56.2l19.2 19c-.1-.04-.3-.1-.5-.2z"/>
+    <path fill="#A02421" d="m3258.96 88.6-19.15-19c.2.12.4.22.6.27l19.2 19-.5-.26z"/>
+    <path fill="#9B2420" d="m3259.52 88.87-19.15-19 .5.3 19.16 19c-.16-.1-.36-.2-.5-.3z"/>
+    <path fill="#982420" d="m3260.03 89.17-19.15-19c.2.16.4.26.56.4l19.15 18.96c-.2-.1-.4-.25-.6-.36z"/>
+    <path fill="#952220" d="m3260.6 89.53-19.16-18.95c.2.1.4.26.6.46L3261.2 90z"/>
+    <path fill="#912120" d="m3261.2 90-19.15-18.96c.1.1.25.2.35.3l19.16 19-.36-.35z"/>
+    <path fill="#871F1C" d="m3125.3 138.77-19.15-18.95.1-30.34 19.16 19"/>
+    <path fill="#C32E24" d="m3134.52 98.52-19.1-18.95L3235.72 69l19.1 19"/>
+    <use xlink:href="#reuse-3"/>
+    <use xlink:href="#reuse-3"/>
+    <path fill="#841F1C" d="m3125.4 108.48-19.15-19v-.2l19.16 19v.2z"/>
+    <path fill="#871F1C" d="m3125.4 108.28-19.15-19c0-.26 0-.5.06-.77l19.2 19.1v.7z"/>
+    <path fill="#8B1F1E" d="M3125.46 107.56 3106.3 88.5c0-.2.06-.4.1-.6l19.16 19c-.05.2-.1.4-.1.66"/>
+    <path fill="#8E201E" d="m3125.56 106.9-19.15-19c0-.2.1-.4.1-.62l19.2 19.05c0 .16-.1.36-.1.57z"/>
+    <path fill="#912120" d="m3125.66 106.33-19.15-19.05c.1-.15.1-.35.2-.5l19.2 19-.1.55z"/>
+    <path fill="#952220" d="m3125.8 105.77-19.14-19 .15-.5 19.2 19-.1.5z"/>
+    <path fill="#982420" d="m3125.97 105.26-19.16-19 .3-.5 19.2 19.04c0 .16-.1.3-.2.46z"/>
+    <path fill="#9B2420" d="m3126.17 104.8-19.15-19.05c.05-.15.1-.3.2-.46l19.15 19c-.05.1-.15.3-.2.5z"/>
+    <path fill="#A02421" d="m3126.37 104.3-19.15-19c.05-.16.16-.3.26-.47l19.15 19c-.1.15-.15.3-.26.46z"/>
+    <path fill="#A52522" d="m3126.63 103.83-19.15-19c.05-.15.15-.3.25-.46l19.15 19c-.1.16-.2.3-.25.46"/>
+    <path fill="#A82722" d="m3126.88 103.37-19.15-19 .3-.46 19.16 19c-.1.2-.2.4-.4.5z"/>
+    <path fill="#AD2823" d="m3127.2 102.9-19.16-19 .3-.45 19.15 19-.3.46z"/>
+    <path fill="#B02824" d="m3127.5 102.45-19.16-19c.1-.15.26-.3.4-.46l19.16 19c-.15.1-.25.3-.4.4z"/>
+    <path fill="#B42924" d="m3127.9 102-19.15-19c.15-.16.26-.3.4-.52l19.2 19.05c-.14.16-.3.3-.45.46z"/>
+    <path fill="#B62B24" d="m3128.36 101.53-19.2-19.05c.2-.15.35-.3.56-.5l19.15 19c-.15.2-.36.35-.5.55z"/>
+    <path fill="#BB2C23" d="m3128.87 100.97-19.15-19 .7-.56 19.16 19c-.25.2-.46.5-.7.6z"/>
+    <path fill="#BD2D24" d="m3129.58 100.4-19.15-19c.36-.24.77-.5 1.17-.7l19.2 18.94c-.45.26-.8.5-1.22.77z"/>
+    <path fill="#C32E24" d="m3130.8 99.64-19.2-19c.66-.3 1.33-.6 2-.8l19.14 19c-.66.2-1.32.5-1.93.8z"/>
+    <path fill="#BD2D24" d="m3132.74 98.83-19.15-19c.4-.1.9-.2 1.3-.26l19.1 19c-.5.05-.9.15-1.4.26z"/>
+    <path fill="#BB2C23" d="m3134.12 98.57-19.16-19c.16-.05.3-.05.46-.05l19.15 19c-.15 0-.3 0-.45.05"/>
+    <path fill="#666769" d="M3164 286.22c0-4.86-.27-7.33-.32-10.64h5.63l.4 5h.2c1.8-3.3 5.1-5.58 9.4-5.58 5.7 0 9.9 4.18 9.9 14.1v27.58h-6.4v-26.43c0-4.9-.9-9.7-5.7-9.7-2.7 0-5.3 2.27-6 6.6-.2 1-.3 2.28-.3 3.73v25.8h-6.6v-30.46zm-13.18 5.68c.05-8.16-2.93-11.8-6.06-11.8-4.3 0-6.4 6.17-6.64 11.8zm-12.8 4.8c0 12.64 4.96 15.32 9.58 15.32 2.9 0 5.15-.73 6.74-1.56l1.1 4.8c-2.26 1.18-5.72 1.95-9 1.95-9.77 0-14.78-8.1-14.78-20.6 0-13.2 5.64-21.5 13.77-21.5 8.23 0 11.65 8.9 11.65 18 0 1.6-.14 2.8-.24 3.8h-18.82zm-31.77 4.97c0 1.2.1 2.38.33 3.4 1.3 5.88 4.3 6.9 6.02 6.9 5.4 0 7.17-7.48 7.17-15.74 0-8.5-2.02-15.64-7.22-15.64-2.98 0-5.68 3.6-6.02 7.3-.2.9-.28 2-.28 3.1v10.5zm-6.36-13.26c0-6.2-.3-9.9-.4-12.8h5.7l.3 5.3h.2c2.2-4.3 5.5-5.9 8.7-5.9 7.1 0 11.7 7.6 11.7 21.1 0 15.3-6.2 21.4-12.6 21.4-3.9 0-6.1-2.4-7.2-4.7h-.2V333h-6.4v-44.6zm-27.4 7.8c0 6.8 1.1 16.1 7 16.1 5.6 0 6.8-9.5 6.8-16 0-6.2-1.2-15.9-7-15.9s-6.9 9.7-6.9 16zm20.2 0c0 15.9-7.2 21.3-13.6 21.3-7.4 0-13.2-6.7-13.2-21.1 0-14.9 6.6-21.2 13.6-21.2 7.3 0 13.1 6.9 13.1 21.2z"/>
+    <path fill="#D02A25" d="M3305.63 294.47h.14c.77-1.6 1.44-3.18 2.2-4.53l8.05-14.43h6.97l-10.8 17.2 11.7 23.6h-7.2l-8.9-19.2-2.4 3.8v15.5h-6.4V258h6.4v36.47zm-11.84 20.84c-1.5.9-3.9 1.6-6.8 1.6-8.9 0-14.9-7.2-14.9-20.7 0-11.7 5.8-21.2 16-21.2 2.2 0 4.5.6 5.7 1.3l-1.3 5.3c-.9-.4-2.5-1-4.7-1-6.6 0-9.4 7.7-9.4 15.8 0 9.5 3.6 15.3 9.5 15.3 1.7 0 3.2-.3 4.7-1.1l.9 5zm-35.3-20.1c-3.4 0-11.2.7-11.2 9.5 0 5.4 2.7 7.3 4.9 7.3 2.8 0 5.2-2.1 5.9-6.1.2-.7.3-1.6.3-2.3v-8.2zm6.3 11.9c0 3.2 0 6.7.4 9.3h-5.8l-.4-4.4h-.3c-1.8 3.2-4.6 5.1-8.2 5.1-5.5 0-9.7-4.6-9.7-11.6 0-10.3 8.2-14.7 17.3-14.8v-1.2c0-5.5-1.5-9.2-6.5-9.2-2.6 0-4.8.8-6.8 2.1l-1.5-4.5c1.8-1.2 5.5-2.7 9.6-2.7 8.1 0 11.6 5.3 11.6 14.5V307zm-35-41v9.6h7.8v4.9h-7.9v24.3c0 5.3 1.9 6.8 4.2 6.8 1 0 1.9-.1 2.6-.2l.3 5c-1.2.5-2.7.7-4.8.7-2.6 0-4.9-.7-6.4-2.4-1.7-1.8-2.5-4.6-2.5-10.3v-23.7h-5v-4.9h5V269l6.4-2.7zm-33.3 43.6c1.4.9 3.9 2.1 6.5 2.1 3.6 0 5.9-2.3 5.9-5.9 0-3.1-1.1-5.2-5.2-8-5.3-3.4-8.2-6.9-8.2-11.5 0-6.6 4.8-11.3 11.1-11.3 3.2 0 5.5 1.1 7.2 2.2l-1.7 4.9c-1.6-1.1-3.3-1.8-5.5-1.8-3.5 0-5.2 2.5-5.2 5.2s1 4.2 5 7c4.7 3.1 8.4 6.7 8.4 12.4 0 8.3-5.6 12.2-12.4 12.2-3 0-6.3-.9-8-2.3l1.6-4.9z"/>
+    <path fill="#CECCC9" d="M3330 313.35h.38c.44 0 .78-.15.78-.5s-.2-.55-.73-.55c-.2 0-.35.05-.44.05v1zm0 1.95h-.8v-3.45c.3-.05.74-.15 1.32-.15.64 0 .93.15 1.13.3.25.15.34.4.34.75 0 .4-.3.7-.7.8v.05c.3.1.5.4.6.85.1.55.2.7.2.85h-.8c-.2-.15-.2-.45-.3-.85-.1-.35-.3-.55-.7-.55h-.4v1.4zm-2.12-1.8c0 1.55 1.18 2.75 2.64 2.75 1.47.05 2.6-1.2 2.6-2.75s-1.13-2.85-2.6-2.85c-1.46 0-2.64 1.3-2.64 2.85m6.12 0c0 1.95-1.52 3.5-3.48 3.5-1.95 0-3.52-1.55-3.52-3.5s1.57-3.5 3.52-3.5c1.96 0 3.48 1.55 3.48 3.5"/>
+    <path fill="#696566" fill-rule="nonzero" d="m2718.36 224.24-15.23-42.43c-.2-.5-.5-1.3-.5-2 0-1.8 1.56-3.6 3.8-3.6 1.93 0 3.2 1.3 3.78 3.1l12.7 36.6 12.7-36.6c.6-1.7 1.8-3 3.7-3h.4c2.1 0 3.3 1.3 3.9 3l12.6 36.7 12.9-36.7c.5-1.5 1.6-2.9 3.6-2.9 2.1 0 3.7 1.7 3.7 3.5 0 .7-.3 1.5-.4 2l-15.3 42.6c-.8 2.3-2.3 3.4-4.1 3.4h-.2c-1.9 0-3.4-1.1-4.1-3.4l-12.5-36-12.7 36.1c-.6 2.2-2.1 3.4-4 3.4h-.2c-1.8 0-3.4-1.2-4.2-3.4m111-44.4c0-2 1.7-3.8 3.7-3.8 2.2 0 3.8 1.7 3.8 3.8v8.6c3.7-8.3 11.9-12.3 17.3-12.3 2.3 0 3.7 1.7 3.7 3.8 0 2-1.3 3.5-3.3 3.8-9.7 1.2-17.7 8.5-17.7 23v17c0 2.1-1.5 3.8-3.6 3.8s-3.8-1.7-3.8-3.8v-44zm52.5 48.2c-13.5 0-24.5-10.5-24.5-25.9v-.2c0-14.3 10-25.9 23.7-25.9 14.6 0 22.9 12 22.9 25.2 0 2-1.6 3.5-3.4 3.5H2865c1.04 10.7 8.56 16.8 17.34 16.8 6.1 0 10.6-2.4 14.2-5.8.6-.5 1.28-.9 2.1-.9 1.8 0 3.28 1.5 3.28 3.2 0 .9-.4 1.7-1.15 2.4-4.65 4.5-10.2 7.5-18.56 7.5zm14.6-28.8c-.7-9-5.9-16.9-15.7-16.9-8.5 0-15 7.3-16 17h31.8zm-120.1 13.2v-.2c0-10.5 8.7-16.2 21.4-16.2 6.4 0 11 .9 15.4 2.2v-1.7c0-9-5.5-13.7-14.9-13.7-5 0-8 .6-11.6 2.3-.5.2-1 .3-1.4.3-1.7 0-3.3-1.4-3.3-3.2 0-1.5.7-2.5 2.1-3.1 5-2.1 8.7-2.8 15.1-2.8 7 0 12.5 1.8 16.1 5.5 3.4 3.4 5.2 8.3 5.2 14.7V224c0 2.14-1.6 3.7-3.6 3.7-2.1 0-3.6-1.56-3.6-3.5v-4.78c-3.5 4.57-9.3 8.63-18.1 8.63-9.3 0-18.7-5.33-18.7-15.6m36.9-3.9v-4.84c-3.7-1-8.6-2.1-14.7-2.1-9.4 0-14.6 4.1-14.6 10.4v.2c0 6.3 5.8 10 12.6 10 9.2 0 16.8-5.6 16.8-13.5M2583 179.5c-1.66-3.6-5.7-5.2-9.5-3.5s-5.2 5.9-3.48 9.5l15.9 34.6c2.5 5.5 5.14 8.3 10.1 8.3 5.27 0 7.58-3.1 10.08-8.2l14-30.5c.16-.3.6-1.3 2-1.3 1.2 0 2.2 1 2.2 2.3V220c0 4.56 2.5 8.3 7.4 8.3 4.8 0 7.48-3.74 7.48-8.3v-24.2c0-4.67 3.3-7.7 7.9-7.7 4.5 0 7.55 3.14 7.55 7.7v24.17c0 4.57 2.53 8.3 7.4 8.3 4.83 0 7.5-3.73 7.5-8.3V195.8c0-4.66 3.33-7.7 7.9-7.7s7.6 3.15 7.6 7.7v24.18c0 4.57 2.5 8.3 7.35 8.3s7.5-3.73 7.5-8.3v-27.6c0-10.1-8.14-17.2-17.9-17.2-9.8 0-15.9 6.8-15.9 6.8-3.3-4.23-7.75-6.77-15.34-6.77-8 0-15 6.8-15 6.8-3.26-4.2-8.8-6.7-13.4-6.7-7.1 0-12.72 3.2-16.16 11l-10.2 24-13-30.7z"/>
+    <path stroke="#979797" stroke-linecap="square" stroke-width="2" d="M2405.6 1v400"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-rolling-deploys.svg b/content/nomad/v0.11.x/img/feature-rolling-deploys.svg
new file mode 100644
index 0000000000..cbbb2cba78
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-rolling-deploys.svg
@@ -0,0 +1,33 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#FFF" stroke-width="5" d="M33.302 90.566A61.4 61.4 0 0 0 30 110.5c0 33.966 27.534 61.5 61.5 61.5s61.5-27.534 61.5-61.5S125.466 49 91.5 49"/>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M87.935 49.102c-24.4 1.394-44.99 17.013-53.607 38.69"/>
+    <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+      <text font-size="12" transform="translate(55 88)">
+        <tspan x=".494" y="42">rolling...</tspan>
+      </text>
+      <text font-size="30" transform="translate(55 88)">
+        <tspan x=".494" y="25">9/12</tspan>
+      </text>
+    </g>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M195 109h27.538"/>
+    <path fill="#FFF" d="m231.5 109.037-10.5 6.038V103"/>
+    <g transform="translate(267 49)">
+      <circle cx="61.5" cy="61.5" r="61.5" stroke="#FFF" stroke-width="5"/>
+      <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+        <text font-size="12" transform="translate(16 39)">
+          <tspan x="27.497" y="42">done!</tspan>
+        </text>
+        <text font-size="30" transform="translate(16 39)">
+          <tspan x=".493" y="25">12/12</tspan>
+        </text>
+      </g>
+    </g>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m258.527 1.02-16.33 9.473 16.33 9.474 16.2-9.56"/>
+      <path fill-rule="nonzero" d="M258.527.037 241 10.194v20.27l11.97 6.915v-.985l-11.115-6.4V11.303L258.1 20.69v19.42l.64.384 17.312-10.03v-20.27zm0 19.93-16.33-9.474 16.33-9.474 16.2 9.386-16.2 9.56zm16.67 10.03L259.597 39l-.64.384V20.692l16.242-9.56v18.864z"/>
+    </g>
+    <path d="M27.5 1.02 11.195 10.5 27.5 19.983l16.177-9.567"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M27.5.037 10 10.202V30.49l11.95 6.917v-.982L10.855 30.02V11.312l16.22 9.395V40.14l.64.385L45 30.49V10.2zm0 19.945-16.305-9.48L27.5 1.02l16.177 9.396zM44.146 30.02l-15.58 9.01-.64.385V20.708l16.22-9.566z"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/feature-simplify.svg b/content/nomad/v0.11.x/img/feature-simplify.svg
new file mode 100644
index 0000000000..da08278683
--- /dev/null
+++ b/content/nomad/v0.11.x/img/feature-simplify.svg
@@ -0,0 +1,23 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 694 456">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M341 63.5v26m0 1v30"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M111 345h232v111H111z"/>
+    <path fill="#1F9967" d="M178.26 385.96a5.7 5.7 0 0 1-1.31.27q-.73.07-1.75.07.96.44 1.44 1.1t.48 1.6q0 1.04-.51 1.84t-1.45 1.26-2.22.46q-.9 0-1.44-.18a1.1 1.1 0 0 0-.34.39q-.12.23-.12.49 0 .8 1.3.8h1.84q1.12 0 2 .38c.88.38 1.043.603 1.37 1.05q.49.67.49 1.51 0 1.58-1.36 2.45t-3.92.87q-1.78 0-2.81-.37t-1.46-1.08-.43-1.83h2q0 .6.23.95t.81.52 1.68.17q1.6 0 2.3-.39t.7-1.15q0-.64-.55-.99t-1.49-.35h-1.82q-1.42 0-2.15-.58t-.73-1.46q0-.54.3-1.04t.86-.86q-.94-.5-1.37-1.21t-.43-1.75q0-1.1.56-1.95t1.56-1.32 2.28-.47q1.72.02 2.73-.24c1.01-.26 1.39-.447 2.15-.82zm-7.04 1.35q-.54.59-.54 1.59 0 1.02.55 1.61t1.61.59q1 0 1.52-.58t.52-1.66q0-2.14-2.06-2.14-1.06 0-1.6.59m18.64-1.87-.38 3.9h-1.6v-2.16q-1.1.02-1.91.88t-1.29 2.42v3.92h2.12v1.6h-5.92v-1.6h1.56v-7.36h-1.56v-1.6h3.26l.4 2.44q.62-1.36 1.51-2.03t2.21-.67q.82 0 1.6.26m10.68 1.21q1.24 1.49 1.24 4.05t-1.26 4.06-3.52 1.5q-2.28 0-3.53-1.47t-1.25-4.07q0-2.52 1.27-4.04c1.27-1.52 2.023-1.52 3.53-1.52q2.28 0 3.52 1.49m-5.35 1.19q-.61.94-.61 2.88 0 1.96.6 2.89t1.82.93 1.82-.94.6-2.9q0-1.94-.6-2.87t-1.8-.93q-1.22 0-1.83.94m11.83 4.98q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm18.76-2.12q0 2.5-1.06 4.03t-3.02 1.53q-1.66 0-2.68-1.16v4.96l-2.24.26v-14.88h1.94l.14 1.36q.6-.8 1.39-1.22t1.69-.42q3.84 0 3.84 5.54m-5.74-3.4q-.58.42-1.02 1.1v4.94q.78 1.18 2.08 1.18 1.16 0 1.74-.92c.58-.92.58-1.573.58-2.88q0-2.02-.52-2.93t-1.58-.91q-.7 0-1.28.42m11.58 5.66q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36m12.69-7.4q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m10.55-.49q0 1.34 1.6 1.34.8 0 1.68-.36l.56 1.56q-1.1.6-2.72.6-1.58 0-2.47-.89t-.89-2.45v-10.08H252v-1.64h5.42zm9.6-.3q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm12.51.93q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m-91.464 30.664.714 1.008q-.491.42-1.176.665-.687.245-1.414.245-1.694 0-2.646-1.043c-.635-.7-.952-1.63-.952-2.8 0-.758.145-1.43.434-2.025a3.34 3.34 0 0 1 1.253-1.4c.54-.34 1.19-.51 1.93-.51q1.47.001 2.562.895l-.73.98q-.896-.615-1.805-.615-.923 0-1.456.665-.532.666-.532 2.01 0 1.315.532 1.93.532.619 1.455.618.883 0 1.82-.63zm8.442-4.81q.869 1.043.868 2.836 0 1.792-.882 2.842t-2.464 1.05q-1.596 0-2.47-1.03-.876-1.028-.876-2.848 0-1.765.89-2.828.888-1.064 2.47-1.064 1.596 0 2.464 1.043zm-3.745.834q-.427.659-.427 2.016 0 1.373.42 2.023t1.274.65 1.274-.657q.42-.659.42-2.03 0-1.358-.42-2.01-.42-.65-1.26-.65-.854 0-1.28.658zm8.28 3.486q0 .645.26.93.26.288.79.288.504 0 .974-.294.469-.294.75-.742v-5.348h1.567V420h-1.358l-.098-.952q-.391.546-1.022.84-.63.294-1.302.294-1.064.001-1.596-.574t-.532-1.638v-5.362h1.568v5.166zm6.833-5.166h1.358l.112.966a3.2 3.2 0 0 1 1.085-.86c.42-.202.86-.302 1.31-.302.68 0 1.2.19 1.54.574.35.383.52.924.52 1.624V420h-1.57v-4.606c0-.457-.02-.81-.07-1.057q-.077-.371-.3-.546c-.15-.11-.374-.17-.673-.17-.335 0-.655.107-.96.31-.3.207-.56.46-.775.77v5.3h-1.57v-7.39zm13.594 7.42a4.4 4.4 0 0 1-1.176.154q-1.261 0-1.946-.65-.686-.652-.686-1.772v-4.004h-1.638v-1.148h1.638v-1.652l1.568-.182v1.834h2.506l-.182 1.148H219.1v3.99q0 .601.308.89.308.286.98.286.742 0 1.372-.35l.56 1.036q-.42.265-.98.42m17.458-5.124h-5.796v-1.288h5.796zm0 2.758h-5.796v-1.274h5.796zm11.816-8.022h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246zm9.275.868q.693.365 1.057.98.364.616.364 1.386 0 .854-.392 1.66-.391.804-1.274 1.777-.883.975-2.492 2.43h4.382l-.168 1.26h-6.006v-1.19c1.213-1.16 2.12-2.08 2.716-2.73q.895-.989 1.26-1.686a3.04 3.04 0 0 0 .364-1.414q0-.73-.42-1.15t-1.148-.42q-.63.001-1.07.23-.441.233-.89.78l-1.008-.785q.573-.741 1.316-1.112.743-.37 1.764-.37.952 0 1.645.363zm5.06-.868h1.71l-.24 3.738h-1.245zm2.465 0h1.708l-.224 3.738h-1.246z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M461 345h232v111H461zM17 174h202v102H17z"/>
+    <path fill="#1F9967" d="m89.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L92.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M137.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm15.3-1.76V232h-8.34v-1.76h3.36v-9.74l-3.04 1.86-.96-1.56 4.24-2.6h1.98v12.04z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M237 174h202v102H237z"/>
+    <path fill="#1F9967" d="m309.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L312.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M357.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm15.3-1.76V232h-8.34v-1.76h3.36v-9.74l-3.04 1.86-.96-1.56 4.24-2.6h1.98v12.04z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M476 174h202v102H476z"/>
+    <path fill="#1F9967" d="m548.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L551.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M596.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm12.49-13.56q.99.52 1.51 1.4c.52.88.52 1.247.52 1.98a5.36 5.36 0 0 1-.56 2.37q-.56 1.15-1.82 2.54t-3.56 3.47h6.26l-.24 1.8h-8.58v-1.7q2.6-2.5 3.88-3.91t1.8-2.41c.52-1 .52-1.34.52-2.02q0-1.04-.6-1.64t-1.64-.6q-.9 0-1.53.33t-1.27 1.11l-1.44-1.12q.82-1.06 1.88-1.59t2.52-.53q1.36 0 2.35.52"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M227 294.5v52"/>
+    <path fill="#1F9967" d="M528.26 385.96a5.7 5.7 0 0 1-1.31.27q-.73.07-1.75.07.96.44 1.44 1.1t.48 1.6q0 1.04-.51 1.84t-1.45 1.26-2.22.46q-.9 0-1.44-.18a1.1 1.1 0 0 0-.34.39q-.12.23-.12.49 0 .8 1.3.8h1.84q1.12 0 2 .38c.88.38 1.043.603 1.37 1.05q.49.67.49 1.51 0 1.58-1.36 2.45t-3.92.87q-1.78 0-2.81-.37t-1.46-1.08-.43-1.83h2q0 .6.23.95t.81.52 1.68.17q1.6 0 2.3-.39t.7-1.15q0-.64-.55-.99t-1.49-.35h-1.82q-1.42 0-2.15-.58t-.73-1.46q0-.54.3-1.04t.86-.86q-.94-.5-1.37-1.21t-.43-1.75q0-1.1.56-1.95t1.56-1.32 2.28-.47q1.72.02 2.73-.24c1.01-.26 1.39-.447 2.15-.82zm-7.04 1.35q-.54.59-.54 1.59 0 1.02.55 1.61t1.61.59q1 0 1.52-.58t.52-1.66q0-2.14-2.06-2.14-1.06 0-1.6.59m18.64-1.87-.38 3.9h-1.6v-2.16q-1.1.02-1.91.88t-1.29 2.42v3.92h2.12v1.6h-5.92v-1.6h1.56v-7.36h-1.56v-1.6h3.26l.4 2.44q.62-1.36 1.51-2.03t2.21-.67q.82 0 1.6.26m10.68 1.21q1.24 1.49 1.24 4.05t-1.26 4.06-3.52 1.5q-2.28 0-3.53-1.47t-1.25-4.07q0-2.52 1.27-4.04c1.27-1.52 2.023-1.52 3.53-1.52q2.28 0 3.52 1.49m-5.35 1.19q-.61.94-.61 2.88 0 1.96.6 2.89t1.82.93 1.82-.94.6-2.9q0-1.94-.6-2.87t-1.8-.93q-1.22 0-1.83.94m11.83 4.98q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm18.76-2.12q0 2.5-1.06 4.03t-3.02 1.53q-1.66 0-2.68-1.16v4.96l-2.24.26v-14.88h1.94l.14 1.36q.6-.8 1.39-1.22t1.69-.42q3.84 0 3.84 5.54m-5.74-3.4q-.58.42-1.02 1.1v4.94q.78 1.18 2.08 1.18 1.16 0 1.74-.92c.58-.92.58-1.573.58-2.88q0-2.02-.52-2.93t-1.58-.91q-.7 0-1.28.42m11.58 5.66q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36m12.69-7.4q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m10.55-.49q0 1.34 1.6 1.34.8 0 1.68-.36l.56 1.56q-1.1.6-2.72.6-1.58 0-2.47-.89t-.89-2.45v-10.08H602v-1.64h5.42zm9.6-.3q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm12.51.93q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m-91.464 30.664.714 1.008q-.491.42-1.176.665-.687.245-1.414.245-1.693 0-2.646-1.043c-.635-.7-.952-1.63-.952-2.8 0-.758.145-1.43.434-2.025a3.34 3.34 0 0 1 1.253-1.4c.54-.34 1.19-.51 1.93-.51q1.47.001 2.562.895l-.73.98q-.896-.615-1.805-.615-.923 0-1.456.665-.532.666-.532 2.01 0 1.315.532 1.93.532.619 1.455.618c.59 0 1.194-.21 1.82-.63zm8.442-4.81q.869 1.043.868 2.836 0 1.792-.882 2.842t-2.464 1.05q-1.596 0-2.47-1.03-.876-1.028-.876-2.848 0-1.765.89-2.828.888-1.064 2.47-1.064 1.596 0 2.464 1.043zm-3.745.834q-.427.659-.427 2.016 0 1.373.42 2.023t1.274.65 1.274-.657q.42-.659.42-2.03 0-1.358-.42-2.01-.42-.65-1.26-.65-.855 0-1.28.658zm8.28 3.486q0 .645.26.93.26.288.79.288.504 0 .974-.294.469-.294.75-.742v-5.348h1.567V420h-1.358l-.098-.952q-.391.546-1.022.84-.63.294-1.302.294-1.063.001-1.596-.574-.532-.575-.532-1.638v-5.362h1.568zm6.833-5.166h1.358l.112.966a3.2 3.2 0 0 1 1.085-.86c.42-.202.86-.302 1.31-.302.68 0 1.2.19 1.54.574.35.383.52.924.52 1.624V420h-1.57v-4.606c0-.457-.02-.81-.07-1.057q-.077-.371-.3-.546c-.15-.11-.374-.17-.673-.17-.335 0-.655.107-.96.31-.3.207-.56.46-.775.77v5.3h-1.57v-7.39zm13.594 7.42a4.4 4.4 0 0 1-1.176.154q-1.261 0-1.946-.65-.686-.652-.686-1.772v-4.004h-1.638v-1.148h1.638v-1.652l1.568-.182v1.834h2.506l-.182 1.148H569.1v3.99q0 .601.308.89.308.286.98.286.742 0 1.372-.35l.56 1.036q-.42.265-.98.42m17.458-5.124h-5.796v-1.288h5.796zm0 2.758h-5.796v-1.274h5.796zm11.816-8.022h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246zm11.242 9.128V420h-5.838v-1.232h2.352v-6.818l-2.128 1.302-.672-1.092 2.968-1.82h1.386v8.428zm3.094-9.128h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246z"/>
+    <path stroke="#FFF" stroke-width="2" d="M1 156h455v137H1z"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M579 294.5v52"/>
+    <path stroke="#FFF" stroke-width="2" d="M461 156h232v137H461z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m341.5 133 6.5-13h-13"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M282.5 90h119m0 .5 25.633 25.633"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m435.096 124.096-4.596-13.788-9.192 9.192"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="m281.5 90.5-26.34 26.34"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m246.904 125.096 4.596-13.788 9.192 9.192M374.9 27.6c.1-.8.1-1.4.1-2.2C375 11.6 363.8.5 350 .5c-11.5 0-21.5 7.9-24.3 19q-3.6-.9-7.2-.9c-14.9 0-27.2 12.1-27.5 27l1-.2V45l1 .5V45h64.8l.1-.6c.1-.9.2-1.5.2-2.2 0-9.5-7.8-17.2-17.3-17.2-6.9 0-13.2 4.2-15.9 10.5l2.1.9c2.4-5.5 7.8-9.1 13.8-9.1 8.3 0 15 6.5 15 14.8 0 .4 0-.1-.1.9h-62.6c1.3-12 12.2-22.7 25.4-22.7 2.6 0 5.2.5 7.7 1.3l1.1.4.2-1.1c2.1-10.7 11.6-18.4 22.5-18.4 12.7 0 23 10.3 23 23 0 .9-.1 1.9-.2 2.9l-.1.8h.8c6.2 2.1 10.6 7.8 11.4 13.8H372v2h15c0-7-4.8-14.6-12.1-17.4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/guide-ui-acl-token-set.png b/content/nomad/v0.11.x/img/guide-ui-acl-token-set.png
new file mode 100644
index 0000000000..cd36638084
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-acl-token-set.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-acl-token.png b/content/nomad/v0.11.x/img/guide-ui-acl-token.png
new file mode 100644
index 0000000000..9f48d05c7e
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-acl-token.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempted.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempted.png
new file mode 100644
index 0000000000..3bf46e4e60
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempted.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempter.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempter.png
new file mode 100644
index 0000000000..4449e9f918
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-preempter.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-details.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-details.png
new file mode 100644
index 0000000000..b949d6371d
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-details.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-icon.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-icon.png
new file mode 100644
index 0000000000..0d964f2044
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-reschedule-icon.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-resource-utilization.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-resource-utilization.png
new file mode 100644
index 0000000000..519585acd6
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-resource-utilization.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-stop-restart.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-stop-restart.png
new file mode 100644
index 0000000000..3b84b36aa4
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-stop-restart.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-alloc-unhealthy-driver.png b/content/nomad/v0.11.x/img/guide-ui-img-alloc-unhealthy-driver.png
new file mode 100644
index 0000000000..7477bd80df
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-alloc-unhealthy-driver.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-allocations.png b/content/nomad/v0.11.x/img/guide-ui-img-client-allocations.png
new file mode 100644
index 0000000000..244b4ca922
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-allocations.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-attributes.png b/content/nomad/v0.11.x/img/guide-ui-img-client-attributes.png
new file mode 100644
index 0000000000..f87d1d45fe
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-attributes.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-detail.png b/content/nomad/v0.11.x/img/guide-ui-img-client-detail.png
new file mode 100644
index 0000000000..28234e93de
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-detail.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-drain.png b/content/nomad/v0.11.x/img/guide-ui-img-client-drain.png
new file mode 100644
index 0000000000..7ef21066c7
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-drain.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-driver-status.png b/content/nomad/v0.11.x/img/guide-ui-img-client-driver-status.png
new file mode 100644
index 0000000000..8eb6e6766a
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-driver-status.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-events.png b/content/nomad/v0.11.x/img/guide-ui-img-client-events.png
new file mode 100644
index 0000000000..0b8c674ac3
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-events.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-client-resource-utilization.png b/content/nomad/v0.11.x/img/guide-ui-img-client-resource-utilization.png
new file mode 100644
index 0000000000..4171f9a57b
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-client-resource-utilization.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-clients-filters.png b/content/nomad/v0.11.x/img/guide-ui-img-clients-filters.png
new file mode 100644
index 0000000000..28e356864f
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-clients-filters.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-clients-list.png b/content/nomad/v0.11.x/img/guide-ui-img-clients-list.png
new file mode 100644
index 0000000000..bd76f1600e
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-clients-list.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-allocations.png b/content/nomad/v0.11.x/img/guide-ui-img-job-allocations.png
new file mode 100644
index 0000000000..66c6afc430
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-allocations.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-definition-edit.png b/content/nomad/v0.11.x/img/guide-ui-img-job-definition-edit.png
new file mode 100644
index 0000000000..b3cebc245c
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-definition-edit.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-definition.png b/content/nomad/v0.11.x/img/guide-ui-img-job-definition.png
new file mode 100644
index 0000000000..b5557ee057
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-definition.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-deployment-canary.png b/content/nomad/v0.11.x/img/guide-ui-img-job-deployment-canary.png
new file mode 100644
index 0000000000..4e77aa9bcb
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-deployment-canary.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-deployments.png b/content/nomad/v0.11.x/img/guide-ui-img-job-deployments.png
new file mode 100644
index 0000000000..cd873b855f
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-deployments.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-evaluations.png b/content/nomad/v0.11.x/img/guide-ui-img-job-evaluations.png
new file mode 100644
index 0000000000..683d195e35
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-evaluations.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-filters.png b/content/nomad/v0.11.x/img/guide-ui-img-job-filters.png
new file mode 100644
index 0000000000..7bf26684c6
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-filters.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-overview-system.png b/content/nomad/v0.11.x/img/guide-ui-img-job-overview-system.png
new file mode 100644
index 0000000000..70e5e38233
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-overview-system.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-plan-placement-failures.png b/content/nomad/v0.11.x/img/guide-ui-img-job-plan-placement-failures.png
new file mode 100644
index 0000000000..6cb000100e
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-plan-placement-failures.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-plan-preemptions.png b/content/nomad/v0.11.x/img/guide-ui-img-job-plan-preemptions.png
new file mode 100644
index 0000000000..5abbd89ef3
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-plan-preemptions.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-plan.png b/content/nomad/v0.11.x/img/guide-ui-img-job-plan.png
new file mode 100644
index 0000000000..0ede71ed69
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-plan.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-run.png b/content/nomad/v0.11.x/img/guide-ui-img-job-run.png
new file mode 100644
index 0000000000..6de945978a
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-run.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-stop.png b/content/nomad/v0.11.x/img/guide-ui-img-job-stop.png
new file mode 100644
index 0000000000..8b6f07b434
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-stop.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-job-versions.png b/content/nomad/v0.11.x/img/guide-ui-img-job-versions.png
new file mode 100644
index 0000000000..748e1620c6
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-job-versions.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-periodic-force.png b/content/nomad/v0.11.x/img/guide-ui-img-periodic-force.png
new file mode 100644
index 0000000000..234ae0fda7
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-periodic-force.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-server-detail.png b/content/nomad/v0.11.x/img/guide-ui-img-server-detail.png
new file mode 100644
index 0000000000..31729fb9bd
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-server-detail.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-servers-list.png b/content/nomad/v0.11.x/img/guide-ui-img-servers-list.png
new file mode 100644
index 0000000000..6b13e5b901
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-servers-list.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-task-events.png b/content/nomad/v0.11.x/img/guide-ui-img-task-events.png
new file mode 100644
index 0000000000..4e2e1480e4
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-task-events.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-img-task-logs.png b/content/nomad/v0.11.x/img/guide-ui-img-task-logs.png
new file mode 100644
index 0000000000..92105b8201
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-img-task-logs.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-jobs-list-unauthorized.png b/content/nomad/v0.11.x/img/guide-ui-jobs-list-unauthorized.png
new file mode 100644
index 0000000000..a4af5bb9b5
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-jobs-list-unauthorized.png differ
diff --git a/content/nomad/v0.11.x/img/guide-ui-jobs-list.png b/content/nomad/v0.11.x/img/guide-ui-jobs-list.png
new file mode 100644
index 0000000000..5e030aa25d
Binary files /dev/null and b/content/nomad/v0.11.x/img/guide-ui-jobs-list.png differ
diff --git a/content/nomad/v0.11.x/img/haproxy_ui.png b/content/nomad/v0.11.x/img/haproxy_ui.png
new file mode 100644
index 0000000000..1ebfcd8b21
Binary files /dev/null and b/content/nomad/v0.11.x/img/haproxy_ui.png differ
diff --git a/content/nomad/v0.11.x/img/intro-ui-alloc-status.png b/content/nomad/v0.11.x/img/intro-ui-alloc-status.png
new file mode 100644
index 0000000000..89ceb91d10
Binary files /dev/null and b/content/nomad/v0.11.x/img/intro-ui-alloc-status.png differ
diff --git a/content/nomad/v0.11.x/img/intro-ui-job-detail.png b/content/nomad/v0.11.x/img/intro-ui-job-detail.png
new file mode 100644
index 0000000000..a067f28311
Binary files /dev/null and b/content/nomad/v0.11.x/img/intro-ui-job-detail.png differ
diff --git a/content/nomad/v0.11.x/img/intro-ui-jobs-list.png b/content/nomad/v0.11.x/img/intro-ui-jobs-list.png
new file mode 100644
index 0000000000..d9acc28c4e
Binary files /dev/null and b/content/nomad/v0.11.x/img/intro-ui-jobs-list.png differ
diff --git a/content/nomad/v0.11.x/img/intro-ui-task-group-detail.png b/content/nomad/v0.11.x/img/intro-ui-task-group-detail.png
new file mode 100644
index 0000000000..ab435d9ef3
Binary files /dev/null and b/content/nomad/v0.11.x/img/intro-ui-task-group-detail.png differ
diff --git a/content/nomad/v0.11.x/img/lb-homepage.png b/content/nomad/v0.11.x/img/lb-homepage.png
new file mode 100644
index 0000000000..75e40a3ee4
Binary files /dev/null and b/content/nomad/v0.11.x/img/lb-homepage.png differ
diff --git a/content/nomad/v0.11.x/img/lb-routing-table.png b/content/nomad/v0.11.x/img/lb-routing-table.png
new file mode 100644
index 0000000000..dc357f520c
Binary files /dev/null and b/content/nomad/v0.11.x/img/lb-routing-table.png differ
diff --git a/content/nomad/v0.11.x/img/logo-hashicorp.svg b/content/nomad/v0.11.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v0.11.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/logo-text.svg b/content/nomad/v0.11.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v0.11.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/new-targets.png b/content/nomad/v0.11.x/img/new-targets.png
new file mode 100644
index 0000000000..55ac0f4e29
Binary files /dev/null and b/content/nomad/v0.11.x/img/new-targets.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-architecture-global.png b/content/nomad/v0.11.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-architecture-region.png b/content/nomad/v0.11.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-data-model.png b/content/nomad/v0.11.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-demo-app.png b/content/nomad/v0.11.x/img/nomad-demo-app.png
new file mode 100644
index 0000000000..0b21f4e877
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad-demo-app.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-evaluation-flow.png b/content/nomad/v0.11.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v0.11.x/img/nomad-hero-pattern.svg b/content/nomad/v0.11.x/img/nomad-hero-pattern.svg
new file mode 100644
index 0000000000..b73292eb68
--- /dev/null
+++ b/content/nomad/v0.11.x/img/nomad-hero-pattern.svg
@@ -0,0 +1,1688 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="509" fill="none" viewBox="0 0 1600 509" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="1600" height="509" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+    <path fill="#00BC7F" d="M0 0h1600v509H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g opacity=".75">
+      <path fill="url(#b)" d="M1363.61 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#c)" d="M1382.37 171.828c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#d)" d="M1401.05 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#e)" d="M1401.05 161.005c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#f)" d="M1288.91 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M1307.58 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#h)" d="M1326.26 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#i)" d="M1326.26 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#j)" d="M1344.94 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#k)" d="M1363.61 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#l)" d="M1344.94 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M1363.61 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#n)" d="M1382.37 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#o)" d="M1401.05 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#p)" d="M1382.37 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#q)" d="M1401.05 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#r)" d="M1232.8 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#s)" d="M1251.55 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#t)" d="M1251.55 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#u)" d="M1270.23 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#v)" d="M1288.91 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#w)" d="M1270.23 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#x)" d="M1288.91 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#y)" d="M1307.58 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#z)" d="M1326.26 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#A)" d="M1307.58 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#B)" d="M1326.26 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#C)" d="M1344.94 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#D)" d="M1363.61 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#E)" d="M1344.94 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#F)" d="M1363.61 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#G)" d="M1382.37 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823a.6.6 0 0 1-.32.081" opacity=".9"/>
+      <path fill="url(#H)" d="M1401.05 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#I)" d="M1382.37 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#J)" d="M1401.05 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#K)" d="M1232.8 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#L)" d="M1251.55 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#M)" d="M1232.8 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#N)" d="M1251.55 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#O)" d="M1270.23 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#P)" d="M1288.91 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#Q)" d="M1270.23 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#R)" d="M1288.91 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#S)" d="M1307.58 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#T)" d="M1326.26 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#U)" d="M1307.58 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#V)" d="M1326.26 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#W)" d="M1344.94 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#X)" d="M1363.61 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.744c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823z" opacity=".8"/>
+      <path fill="url(#Y)" d="M1344.94 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#Z)" d="M1363.61 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aa)" d="M1382.37 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ab)" d="M1401.05 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ac)" d="M1382.37 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ad)" d="M1401.05 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ae)" d="M1232.8 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#af)" d="M1251.55 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ag)" d="M1232.8 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#ah)" d="M1251.55 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ai)" d="M1270.23 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aj)" d="M1288.91 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ak)" d="M1270.23 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#al)" d="M1288.91 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#am)" d="M1307.58 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#an)" d="M1326.26 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ao)" d="M1307.58 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#ap)" d="M1326.26 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aq)" d="M1344.94 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#ar)" d="M1363.61 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#as)" d="M1344.94 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#at)" d="M1363.61 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#au)" d="M1382.37 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#av)" d="M1401.05 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aw)" d="M1382.37 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ax)" d="M1401.05 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ay)" d="M1232.8 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#az)" d="M1251.55 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aA)" d="M1232.8 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#aB)" d="M1251.55 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#aC)" d="M1270.23 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aD)" d="M1288.91 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aE)" d="M1270.23 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#aF)" d="M1288.91 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#aG)" d="M1307.58 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#aH)" d="M1326.26 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aI)" d="M1307.58 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09 0-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#aJ)" d="M1326.26 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aK)" d="M1344.94 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#aL)" d="M1363.61 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aM)" d="M1344.94 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#aN)" d="M1363.61 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.17.081-.33.081" opacity=".8"/>
+      <path fill="url(#aO)" d="M1382.37 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#aP)" d="M1401.05 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aQ)" d="M1382.37 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#aR)" d="M1401.05 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aS)" d="M1232.8 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aT)" d="M1251.55 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aU)" d="M1232.8 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aV)" d="M1251.55 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aW)" d="M1270.23 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aX)" d="M1288.91 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aY)" d="M1270.23 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aZ)" d="M1288.91 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ba)" d="M1307.58 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bb)" d="M1326.26 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bc)" d="M1307.58 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bd)" d="M1326.26 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#be)" d="M1344.94 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bf)" d="M1363.61 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bg)" d="M1344.94 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bh)" d="M1363.61 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bi)" d="M1382.37 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bj)" d="M1401.05 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bk)" d="M1382.37 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bl)" d="M1401.05 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bm)" d="M1232.8 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bn)" d="M1251.55 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#bo)" d="M1232.8 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#bp)" d="M1251.55 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bq)" d="M1270.23 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#br)" d="M1288.91 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#bs)" d="M1270.23 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#bt)" d="M1288.91 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bu)" d="M1307.58 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bv)" d="M1326.26 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#bw)" d="M1307.58 452.354c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.6-10.743c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824z" opacity=".5"/>
+      <path fill="url(#bx)" d="M1326.26 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#by)" d="M1344.94 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bz)" d="M1344.94 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#bA)" d="M1363.61 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bB)" d="M1382.37 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#bC)" d="M1232.8 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bD)" d="M1232.8 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bE)" d="M1251.55 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bF)" d="M1270.23 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bG)" d="M1270.23 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bH)" d="M1288.91 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bI)" d="M1307.58 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.25.08-.33.08" opacity=".5"/>
+    </g>
+    <path fill="url(#bJ)" d="M130.232 9.88c-.08 0-.24 0-.32-.081L110.353-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L112.678-1.505l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bK)" d="M167.585 9.88c-.08 0-.24 0-.32-.081L147.706-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803L150.031-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#bL)" d="M148.909 20.703c-.08 0-.241 0-.321-.08L129.03 9.317l19.558-11.304c.321-.16.642-.08.802.24s.08.641-.241.802L131.354 9.318l17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bM)" d="M130.232 31.526c-.08 0-.24 0-.32-.08L110.353 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L112.678 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.321.321-.481.321"/>
+    <path fill="url(#bN)" d="M204.939 9.879c-.08 0-.241 0-.321-.08L185.06-1.506l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384-1.506l17.795 10.263c.321.16.401.56.241.801-.08.24-.241.32-.481.32"/>
+    <path fill="url(#bO)" d="M186.262 20.703c-.08 0-.24 0-.32-.08L166.383 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L168.708 9.318l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bP)" d="M167.585 31.526c-.08 0-.24 0-.32-.08L147.706 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802L150.031 20.14l17.795 10.262c.321.16.401.562.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bQ)" d="M148.909 42.269c-.08 0-.241 0-.321-.08L129.03 30.884l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bR)" d="M130.232 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.32-.481.32"/>
+    <path fill="url(#bS)" d="M242.292 9.88c-.08 0-.24 0-.32-.081L222.413-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803L224.738-1.505l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#bT)" d="M223.616 20.703c-.081 0-.241 0-.321-.08L203.737 9.317l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.641-.241.802L206.141 9.318l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#bU)" d="M204.939 31.526c-.08 0-.241 0-.321-.08L185.06 20.14l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384 20.14l17.795 10.263c.321.16.401.56.241.801-.08.16-.241.321-.481.321"/>
+    <path fill="url(#bV)" d="M186.262 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bW)" d="M167.585 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bX)" d="M148.909 63.836c-.08 0-.241 0-.321-.08L129.03 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L131.435 52.45l17.794 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32"/>
+    <path fill="url(#bY)" d="M130.232 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.321.321-.481.321"/>
+    <path fill="url(#bZ)" d="M279.726 9.88c-.08 0-.241 0-.321-.081L259.847-1.505l19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803L262.251-1.505l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#ca)" d="M261.049 20.703c-.08 0-.24 0-.321-.08L241.17 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802L243.495 9.318 261.29 19.58c.32.16.4.562.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cb)" d="M242.292 31.526c-.08 0-.24 0-.32-.08L222.413 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L224.738 20.14l17.795 10.263c.32.16.401.56.24.801 0 .16-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cc)" d="M223.616 42.27c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#cd)" d="M204.939 53.093c-.08 0-.241 0-.321-.08L185.06 41.708l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32"/>
+    <path fill="url(#ce)" d="M186.262 63.836c-.08 0-.24 0-.32-.08L166.383 52.45l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L168.788 52.45l17.795 10.262c.321.16.401.562.24.802-.16.24-.32.32-.561.32"/>
+    <path fill="url(#cf)" d="M167.585 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321"/>
+    <path fill="url(#cg)" d="M148.909 85.483c-.08 0-.241 0-.321-.08L129.03 74.097l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802l-17.714 10.262 17.794 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32"/>
+    <path fill="url(#ch)" d="M130.232 96.226c-.08 0-.24 0-.32-.08L110.353 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L112.678 84.84l17.795 10.262c.32.16.4.562.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#ci)" d="M317.079 9.88c-.08 0-.24 0-.32-.081L297.2-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L299.525-1.505 317.32 8.757c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cj)" d="M298.402 20.703c-.08 0-.24 0-.32-.08L278.523 9.317l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L280.848 9.318l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+    <path fill="url(#ck)" d="M279.726 31.526c-.08 0-.241 0-.321-.08L259.847 20.06l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 20.06l17.795 10.262c.321.16.401.561.241.802-.16.24-.401.4-.561.4" opacity=".7"/>
+    <path fill="url(#cl)" d="M261.049 42.27c-.08 0-.24 0-.321-.081L241.17 30.885l19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#cm)" d="M242.292 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cn)" d="M223.616 63.836c-.081 0-.241 0-.321-.08L203.737 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L206.141 52.45l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#co)" d="M204.939 74.659c-.08 0-.241 0-.321-.08L185.06 63.274l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cp)" d="M186.262 85.482c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.16.16-.32.32-.561.32"/>
+    <path fill="url(#cq)" d="M167.585 96.226c-.08 0-.24 0-.32-.08L147.706 84.84l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L150.031 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#cr)" d="M148.909 107.049c-.08 0-.241 0-.321-.08L129.03 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cs)" d="M130.232 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.321.321-.481.321"/>
+    <path fill="url(#ct)" d="M354.433 9.88c-.081 0-.241 0-.321-.081L334.553-1.505l19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803L336.878-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cu)" d="M335.756 20.703c-.08 0-.241 0-.321-.08L315.877 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.201 9.318l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cv)" d="M317.079 31.526c-.08 0-.24 0-.32-.08L297.2 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L299.525 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cw)" d="M298.402 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321" opacity=".6"/>
+    <path fill="url(#cx)" d="M279.726 53.092c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32" opacity=".7"/>
+    <path fill="url(#cy)" d="M261.049 63.836c-.08 0-.24 0-.321-.08L241.09 52.45l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L243.495 52.45l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cz)" d="M242.292 74.66c-.08 0-.24-.001-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801 0 .24-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cA)" d="M223.616 85.482c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32"/>
+    <path fill="url(#cB)" d="M204.939 96.226c-.08 0-.241 0-.321-.08L185.06 84.84l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L187.384 84.84l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cC)" d="M186.262 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#cD)" d="M167.585 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.32.321-.481.321"/>
+    <path fill="url(#cE)" d="M148.909 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cF)" d="M130.232 139.439c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#cG)" d="M373.189 20.703c-.08 0-.24 0-.32-.08L353.31 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L355.635 9.318 373.43 19.58c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+    <path fill="url(#cH)" d="M354.433 31.526c-.081 0-.241 0-.321-.08L334.553 20.14l19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802L336.878 20.14l17.795 10.263c.321.16.401.56.24.801-.08.16-.24.321-.48.321" opacity=".3"/>
+    <path fill="url(#cI)" d="M335.756 42.27c-.08 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cJ)" d="M317.079 53.092c-.08 0-.24 0-.32-.08L297.2 41.708l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262L317.32 51.97c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cK)" d="M298.402 63.836c-.08 0-.24 0-.32-.08L278.523 52.45l19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802L280.928 52.45l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.562.32" opacity=".6"/>
+    <path fill="url(#cL)" d="M279.726 74.659c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#cM)" d="M261.049 85.482c-.08 0-.24 0-.321-.08L241.09 74.098l19.558-11.305c.321-.16.642-.08.802.24.16.322.08.642-.241.803l-17.714 10.262L261.29 84.36c.32.16.4.561.24.802-.08.16-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cN)" d="M242.292 96.225c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L224.738 84.84l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cO)" d="M223.616 107.049c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321"/>
+    <path fill="url(#cP)" d="M204.939 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.241.321-.481.321"/>
+    <path fill="url(#cQ)" d="M186.262 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#cR)" d="M167.585 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#cS)" d="M148.909 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cT)" d="M130.232 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cU)" d="M373.189 42.27c-.08 0-.24 0-.32-.081L353.31 30.885l19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801-.08.241-.32.321-.481.321" opacity=".2"/>
+    <path fill="url(#cV)" d="M354.433 53.092c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cW)" d="M335.756 63.836c-.08 0-.241 0-.321-.08L315.877 52.45l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.281 52.45l17.796 10.262c.32.16.4.562.24.802s-.321.32-.561.32" opacity=".4"/>
+    <path fill="url(#cX)" d="M317.079 74.659c-.08 0-.24 0-.32-.08L297.2 63.275l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cY)" d="M298.402 85.483c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.401.32-.562.32" opacity=".6"/>
+    <path fill="url(#cZ)" d="M279.726 96.226c-.08 0-.241 0-.321-.08L259.847 84.84l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 84.84l17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#da)" d="M261.049 107.049c-.08 0-.24 0-.321-.08L241.17 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#db)" d="M242.292 117.792c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.401.561.24.801 0 .241-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#dc)" d="M223.616 128.615c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#dd)" d="M204.939 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321"/>
+    <path fill="url(#de)" d="M186.262 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#df)" d="M167.585 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#dg)" d="M148.909 171.829c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#dh)" d="M130.232 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321"/>
+    <g opacity=".9">
+      <path fill="url(#di)" d="M373.189 63.836c-.08 0-.24 0-.32-.08L353.23 52.45l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L355.635 52.45l17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dj)" d="M354.433 74.659c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dk)" d="M335.756 85.482c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.321.32-.561.32" opacity=".4"/>
+      <path fill="url(#dl)" d="M317.079 96.226c-.08 0-.24 0-.32-.08L297.2 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L299.525 84.84l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#dm)" d="M298.402 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dn)" d="M279.726 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.801a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#do)" d="M261.049 128.615c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#dp)" d="M242.292 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dq)" d="M223.616 150.182c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321" opacity=".9"/>
+      <path fill="url(#dr)" d="M204.939 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".9"/>
+      <path fill="url(#ds)" d="M186.262 171.828c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dt)" d="M167.586 182.572c-.081 0-.241 0-.321-.081l-19.559-11.304 19.559-11.304c.321-.161.641-.081.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.321-.48.321" opacity=".9"/>
+      <path fill="url(#du)" d="M148.909 193.395c-.08 0-.241 0-.321-.08L129.03 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.161-.321.321-.481.321" opacity=".9"/>
+      <path fill="url(#dv)" d="M130.232 204.138c-.08 0-.24 0-.32-.08l-19.639-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <path fill="url(#dw)" d="M373.189 85.482c-.08 0-.24 0-.32-.08L353.23 74.098l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.715 10.262L373.43 84.36c.32.16.401.561.24.802-.08.16-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dx)" d="M354.433 96.225c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.304c.321-.16.641-.08.801.24s.081.641-.24.802L336.878 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+      <path fill="url(#dy)" d="M335.756 107.049c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#dz)" d="M317.079 117.792c-.08 0-.24 0-.32-.08L297.2 106.408l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dA)" d="M298.402 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+      <path fill="url(#dB)" d="M279.726 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.16.16-.401.321-.561.321" opacity=".7"/>
+      <path fill="url(#dC)" d="M261.049 150.182c-.08 0-.24 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dD)" d="M242.292 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dE)" d="M223.616 171.829c-.081 0-.241 0-.321-.081l-19.558-11.384 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.401-.561.401" opacity=".8"/>
+      <path fill="url(#dF)" d="M204.939 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".8"/>
+      <path fill="url(#dG)" d="M186.262 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.24.321-.481.321" opacity=".8"/>
+      <path fill="url(#dH)" d="M167.586 204.138c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.241s.081.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".8"/>
+      <path fill="url(#dI)" d="M148.909 214.962c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dJ)" d="M130.232 225.785c-.08 0-.24 0-.32-.08L110.353 214.4l19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801L112.678 214.4l17.795 10.262c.32.161.4.562.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <path fill="url(#dK)" d="M373.189 107.049c-.08 0-.24 0-.32-.08L353.31 95.664l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#dL)" d="M354.433 117.792c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dM)" d="M335.756 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#dN)" d="M317.079 139.439c-.08 0-.24 0-.32-.08L297.2 128.054l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.16-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dO)" d="M298.402 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dP)" d="M279.726 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#dQ)" d="M261.049 171.829c-.08 0-.24 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dR)" d="M242.292 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802 0 .241-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#dS)" d="M223.616 193.395c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dT)" d="M204.939 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.714 10.262 17.795 10.262c.32.16.4.561.24.802-.16.24-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dU)" d="M186.262 214.962c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.24.321-.481.321" opacity=".7"/>
+      <path fill="url(#dV)" d="M167.585 225.785c-.08 0-.24 0-.32-.08L147.706 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801L150.031 214.4l17.795 10.262c.321.161.401.562.24.802-.08.16-.32.321-.481.321" opacity=".7"/>
+      <path fill="url(#dW)" d="M148.909 236.528c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.321.321-.481.321" opacity=".7"/>
+      <path fill="url(#dX)" d="M130.232 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.321-.481.321" opacity=".7"/>
+    </g>
+    <g opacity=".6">
+      <path fill="url(#dY)" d="M373.189 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dZ)" d="M354.433 139.439c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.16-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#ea)" d="M335.756 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#eb)" d="M317.079 161.005c-.08 0-.24 0-.32-.08L297.2 149.621l19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#ec)" d="M298.402 171.829c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#ed)" d="M279.726 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#ee)" d="M261.049 193.395c-.08 0-.24 0-.321-.08L241.17 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#ef)" d="M242.292 204.138c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.561.32" opacity=".9"/>
+      <path fill="url(#eg)" d="M223.616 214.962c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.161.24-.321.321-.561.321" opacity=".6"/>
+      <path fill="url(#eh)" d="M204.939 225.785c-.08 0-.241 0-.321-.08L185.06 214.4l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801L187.384 214.4l17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321" opacity=".6"/>
+      <path fill="url(#ei)" d="M186.262 236.528c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".6"/>
+      <path fill="url(#ej)" d="M148.909 258.095c-.08 0-.241 0-.321-.08L129.03 246.71l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#ek)" d="M130.232 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#el)" d="M167.585 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <path fill="url(#em)" d="M373.189 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#en)" d="M354.433 161.005c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#eo)" d="M335.756 171.828c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ep)" d="M317.079 182.572c-.08 0-.24 0-.32-.081L297.2 171.187l19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.24-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#eq)" d="M298.402 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.161-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#er)" d="M279.726 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#es)" d="M261.049 214.961c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.304c.321-.161.642-.081.802.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#et)" d="M242.292 225.785c-.08 0-.24 0-.32-.08L222.413 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.08.641-.24.801L224.738 214.4l17.795 10.262c.32.161.401.562.24.802 0 .16-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#eu)" d="M148.909 279.741c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ev)" d="M130.232 290.484c-.08 0-.24 0-.32-.08L110.353 279.1l19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802L112.678 279.1l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ew)" d="M167.585 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".4"/>
+      <path fill="url(#ex)" d="M186.262 258.095c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.321-.481.321" opacity=".4"/>
+      <path fill="url(#ey)" d="M204.939 247.351c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ez)" d="M223.616 236.528c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.263c.321.16.401.561.241.801-.161.241-.321.321-.561.321" opacity=".4"/>
+    </g>
+    <path fill="#BDBEC2" d="M1587.89 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.08 0-.16.08-.33.08m-18.67-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l37.35-21.567c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-37.35 21.567c-.08.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l56.03-32.389c.32-.161.64-.081.8.24s.08.641-.24.802l-56.03 32.39c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l74.79-43.133c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-74.78 43.133c-.16.081-.25.081-.33.081m-18.67-10.824c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l93.46-53.957c.32-.16.64-.08.8.241s.08.641-.24.802l-93.46 53.956c-.16.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l112.14-64.78c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-112.14 64.78c-.16 0-.24.08-.32.08m-18.76-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l130.82-75.523c.32-.16.64-.08.8.241s.08.641-.24.802l-130.81 75.522c-.08.081-.17.081-.33.081m-18.67-10.744c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l149.49-86.346c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-149.49 86.346c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l168.17-97.09c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-168.17 97.089c-.08.08-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l186.93-107.912c.32-.16.64-.08.8.24s.08.642-.24.802l-186.92 107.913c-.17.08-.25.08-.33.08" opacity=".8"/>
+    <path fill="url(#eA)" d="M111.475 301.308c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.22 64.779c.321.161.401.562.24.802-.16.241-.32.321-.561.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.801.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.081L-.985 193.235c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.161.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .241-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.985 150.102c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .161-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.905 106.969c-.321-.161-.401-.562-.24-.802.16-.321.56-.401.8-.241l112.141 64.78c.321.16.401.561.24.802-.08.16-.32.321-.561.321m0-21.647c-.08 0-.24 0-.32-.08L-.985 85.322c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 63.755c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .24-.24.32-.481.32m0-21.566c-.08 0-.24 0-.32-.08L-.985 42.189c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 20.622c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.08L-.985-1.025c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.56.24.8 0 .241-.24.322-.481.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-22.591c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .24-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.08L-.985-44.158c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.22 64.78c.321.16.401.56.24.8-.08.241-.32.322-.561.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-65.724c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .16-.24.321-.481.321m18.757-10.823c-.08 0-.24 0-.32-.08L20.657-74.865c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24L130.473-12.81c.32.16.4.561.24.802-.08.24-.32.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08L58.01-74.784c-.32-.16-.4-.562-.24-.802.16-.32.561-.401.801-.24l90.578 52.272c.321.16.401.561.241.802-.08.16-.321.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-71.821-41.53c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24l71.821 41.529c.321.16.401.56.241.801-.081.24-.321.321-.481.321m18.676-10.823c-.08 0-.24 0-.32-.08l-53.145-30.707c-.32-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24L186.503-45.2c.32.16.401.562.24.802-.08.24-.24.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08l-34.467-19.884c-.321-.16-.401-.56-.241-.801.16-.32.561-.401.802-.24l34.467 19.882c.321.16.401.561.241.802-.08.16-.241.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-15.791-9.14c-.321-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24l15.791 9.139c.321.16.401.561.241.802-.081.24-.241.32-.481.32"/>
+    <path fill="url(#eB)" d="M1606.57 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eC)" d="M1606.57 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eD)" d="M1587.9 9.88c-.09 0-.25 0-.33-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eE)" d="M1587.9 31.526c-.09 0-.25 0-.33-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eF)" d="M1587.9 53.092c-.09 0-.25 0-.33-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eG)" d="M1569.22 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eH)" d="M1569.22 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eI)" d="M1569.22 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eJ)" d="M1550.54 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eK)" d="M1550.54 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eL)" d="M1550.54 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eM)" d="M1550.54 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eN)" d="M1531.86 20.703c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eO)" d="M1531.86 42.27c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.49.321"/>
+    <path fill="url(#eP)" d="M1531.86 63.836c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eQ)" d="M1513.19 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#eR)" d="M1513.19 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eS)" d="M1513.19 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eT)" d="M1513.19 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.48.321"/>
+    <path fill="url(#eU)" d="M1494.43 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eV)" d="M1494.43 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eW)" d="M1494.43 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eX)" d="M1475.75 9.88c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 8.757c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#eY)" d="M1475.75 31.526c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.49.32"/>
+    <path fill="url(#eZ)" d="M1475.75 53.092c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 51.97c.32.16.4.561.24.802-.08.16-.24.32-.49.32"/>
+    <path fill="url(#fa)" d="M1475.75 74.659c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.49.321"/>
+    <path fill="url(#fb)" d="M1457.08 20.703c-.08 0-.24 0-.32-.08L1437.2 9.317l19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.88 10.262c.32.16.4.561.24.802-.16.24-.32.32-.56.32"/>
+    <path fill="url(#fc)" d="M1457.08 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fd)" d="M1457.08 63.836c-.08 0-.24 0-.32-.08L1437.2 52.45l19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fe)" d="M1438.4 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#ff)" d="M1438.4 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fg)" d="M1438.4 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fh)" d="M1438.4 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fi)" d="M1457.08 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fj)" d="M1438.4 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fk)" d="M1494.43 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .16-.24.32-.48.32"/>
+    <path fill="url(#fl)" d="M1457.08 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.161.4.561.24.802-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fm)" d="M1438.4 117.792c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.561.24.801-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fn)" d="M1475.75 96.226c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#fo)" d="M1457.08 128.615c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.241s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fp)" d="M1438.4 139.438c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.304c.32-.161.64-.081.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fq)" d="M1475.75 117.792c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.561.24.801-.08.241-.24.321-.49.321"/>
+    <path fill="url(#fr)" d="M1494.43 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.161.4.561.24.802 0 .241-.24.321-.48.321"/>
+    <path fill="url(#fs)" d="M1513.19 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#ft)" d="M1531.86 85.482c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.49.32"/>
+    <path fill="url(#fu)" d="M1419.73 150.182c-.09 0-.25 0-.33-.08L1109.6-29.646c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.562.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-51.213c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.801-.08.241-.32.321-.48.321m0-21.566c-.09 0-.25 0-.33-.08L1109.6-72.779c-.32-.16-.4-.562-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.561.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-94.346c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1419.97 84.36c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.668c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.24-.48.24m0-21.567c-.09 0-.25 0-.33-.08L1109.6-137.56c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24l309.81 179.748c.32.16.4.56.24.801-.08.24-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1420.05 19.58c.32.16.4.561.24.802-.16.24-.4.32-.56.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24L1419.97-1.987c.32.16.4.562.24.802-.08.16-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08L1109.6-202.26c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.24L1419.97-45.2c.32.16.4.562.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.321-.48.321m0-21.647c-.09 0-.25 0-.33-.08l-309.8-179.667c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.161.4.561.24.802-.08.16-.32.24-.48.24m0-21.566c-.09 0-.25 0-.33-.08L1109.6-331.74c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.241-.48.241m18.67-10.743c-.08 0-.24 0-.32-.08L1131.16-340.88c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l306.92 178.064c.32.161.4.562.24.802-.08.16-.24.321-.48.321m18.68-10.824c-.08 0-.24 0-.32-.08l-90.58-52.273c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l90.58 52.273c.32.16.4.561.24.802-.08.24-.24.32-.48.32m18.68-10.823c-.09 0-.25 0-.33-.08l-71.82-41.53c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l71.83 41.53c.32.16.4.561.24.801-.08.241-.24.321-.48.321m18.67-10.743c-.08 0-.24 0-.32-.08l-53.14-30.707c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l53.14 30.706c.32.161.4.562.24.802 0 .161-.24.321-.48.321m18.76-10.824c-.08 0-.24 0-.32-.08l-34.47-19.883c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l34.47 19.883c.32.16.4.561.24.802-.08.24-.32.32-.48.32m18.68-10.743c-.08 0-.25 0-.33-.08l-15.79-9.14c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l15.8 9.14c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#fv)" d="M1606.57 538.7c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08L1419.4 387.574c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801-.08.161-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08L1419.4 365.927c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802-.08.24-.32.4-.56.4m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.561-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.81-.24l186.92 107.913c.32.16.4.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.08 0-.24 0-.32-.081l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.912c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l187 107.912c.32.161.4.562.24.802-.08.241-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+    <path fill="#BDBEC2" fill-opacity=".8" d="M92.799 592.656c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.823c.32-.161.641-.081.801.24s.081.641-.24.802l-18.677 10.823c-.08.08-.16.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.24-.801l37.354-21.567c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-37.353 21.567c-.08 0-.24.08-.321.08M55.445 571.09c-.24 0-.4-.08-.56-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.641-.08.801.241s.08.641-.24.802l-56.03 32.39c0 .08-.16.08-.24.08M36.77 560.266c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.24.16.321.08.642-.241.802L37.09 560.186c-.16.08-.24.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.561-.32-.16-.321-.08-.642.24-.802l93.464-53.957c.32-.16.641-.08.801.241s.081.641-.24.802l-93.464 53.956c-.08.08-.16.08-.24.08M-.585 538.7c-.24 0-.4-.08-.48-.321-.161-.321-.08-.641.24-.802l112.14-64.779c.321-.161.641-.08.802.24.16.321.08.642-.241.802L-.264 538.62c-.16.08-.24.08-.32.08m-.08-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.779c.32-.161.641-.081.801.24s.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801L-.344 473.92c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 452.273c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 409.14c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 365.927c-.08.08-.16.161-.32.161m0-21.647c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l93.463-53.956c.32-.16.641-.08.802.241.16.32.08.641-.24.801L-.345 344.361c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l74.787-43.133c.32-.161.64-.08.801.24.16.321.08.642-.24.802L-.344 322.794c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.64-.08.801.241.16.321.08.641-.24.802l-56.03 32.39c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l37.353-21.567c.32-.16.641-.08.801.241s.08.641-.24.802L-.344 279.661c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l18.676-10.823c.32-.161.642-.08.802.24.16.321.08.642-.24.802L-.345 258.014c-.08.081-.16.081-.32.081" opacity=".8"/>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="1368.02" x2="1377.97" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="1386.78" x2="1396.73" y1="174.458" y2="157.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="1405.46" x2="1415.41" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="1405.46" x2="1415.41" y1="163.634" y2="146.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="1293.32" x2="1303.27" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="1311.99" x2="1321.94" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="1330.67" x2="1340.62" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="1330.67" x2="1340.62" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="1349.35" x2="1359.3" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="1368.02" x2="1377.97" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="1349.35" x2="1359.3" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="1368.02" x2="1377.97" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="1386.78" x2="1396.73" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="1405.46" x2="1415.41" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="1386.78" x2="1396.73" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="1405.46" x2="1415.41" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="1237.21" x2="1247.15" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="1255.96" x2="1265.91" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="1255.96" x2="1265.91" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="1274.64" x2="1284.59" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="1293.32" x2="1303.27" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="1274.64" x2="1284.59" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="1293.32" x2="1303.26" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="1311.99" x2="1321.94" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="1330.67" x2="1340.62" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="1311.99" x2="1321.94" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="1330.67" x2="1340.62" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="1349.35" x2="1359.3" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="1368.02" x2="1377.97" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="1349.35" x2="1359.3" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="1368.02" x2="1377.97" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="1386.78" x2="1396.73" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="1405.46" x2="1415.41" y1="271.547" y2="254.32" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="1386.78" x2="1396.73" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="1405.46" x2="1415.41" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="1237.21" x2="1247.15" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="1255.96" x2="1265.91" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="1237.21" x2="1247.15" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="1255.96" x2="1265.91" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="1274.64" x2="1284.59" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="1293.32" x2="1303.26" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="1274.64" x2="1284.59" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="1293.32" x2="1303.27" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="1311.99" x2="1321.94" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="1330.67" x2="1340.62" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="1311.99" x2="1321.94" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="1330.67" x2="1340.62" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="1349.35" x2="1359.3" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="1368.02" x2="1377.87" y1="314.663" y2="297.493" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="1349.35" x2="1359.3" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="1368.02" x2="1377.97" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="1386.78" x2="1396.73" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="1405.46" x2="1415.41" y1="314.68" y2="297.453" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="1386.78" x2="1396.73" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="1405.46" x2="1415.41" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="1237.21" x2="1247.15" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="1255.96" x2="1265.91" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="1237.21" x2="1247.15" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="1255.96" x2="1265.91" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="1274.64" x2="1284.59" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="1293.32" x2="1303.27" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="1274.64" x2="1284.59" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="al" x1="1293.32" x2="1303.26" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="am" x1="1311.99" x2="1321.94" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="an" x1="1330.67" x2="1340.62" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="1311.99" x2="1321.94" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="1330.67" x2="1340.62" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="1349.35" x2="1359.3" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="1368.02" x2="1377.97" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="as" x1="1349.35" x2="1359.3" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="at" x1="1368.02" x2="1377.97" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="au" x1="1386.78" x2="1396.73" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="av" x1="1405.46" x2="1415.41" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="1386.78" x2="1396.73" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="1405.46" x2="1415.41" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="1237.21" x2="1247.15" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="az" x1="1255.96" x2="1265.91" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="1237.21" x2="1247.15" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="1255.96" x2="1265.91" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="1274.64" x2="1284.59" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="1293.32" x2="1303.26" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="1274.64" x2="1284.59" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="1293.32" x2="1303.27" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="1311.99" x2="1321.94" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="1330.67" x2="1340.62" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="1311.99" x2="1321.94" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="1330.67" x2="1340.62" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="1349.35" x2="1359.3" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="1368.02" x2="1377.97" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="1349.35" x2="1359.3" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="1368.02" x2="1377.97" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="1386.78" x2="1396.73" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="1405.46" x2="1415.41" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="1386.78" x2="1396.73" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="1405.46" x2="1415.41" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="1237.21" x2="1247.15" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="1255.96" x2="1265.91" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="1237.21" x2="1247.15" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="1255.96" x2="1265.91" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="1274.64" x2="1284.59" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="1293.32" x2="1303.27" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="1274.64" x2="1284.59" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="1293.32" x2="1303.27" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="1311.99" x2="1321.94" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="1330.67" x2="1340.62" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="1311.99" x2="1321.94" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="1330.67" x2="1340.62" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="be" x1="1349.35" x2="1359.3" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="1368.02" x2="1377.97" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="1349.35" x2="1359.3" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="1368.02" x2="1377.97" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="1386.78" x2="1396.73" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="1405.46" x2="1415.41" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="1386.78" x2="1396.73" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="1405.46" x2="1415.41" y1="422.673" y2="405.446" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="1237.21" x2="1247.15" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="1255.96" x2="1265.91" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="1237.21" x2="1247.15" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="1255.96" x2="1265.91" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="1274.64" x2="1284.59" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="br" x1="1293.32" x2="1303.26" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="1274.64" x2="1284.59" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="1293.32" x2="1303.26" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="1311.99" x2="1321.94" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="1330.67" x2="1340.62" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="1311.97" x2="1321.84" y1="454.965" y2="437.83" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="1330.67" x2="1340.62" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="by" x1="1349.35" x2="1359.3" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="1349.35" x2="1359.3" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="1368.02" x2="1377.97" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="1386.78" x2="1396.73" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="1237.21" x2="1247.15" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="1237.21" x2="1247.15" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="1255.96" x2="1265.91" y1="508.939" y2="491.712" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="1274.64" x2="1284.59" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="1274.64" x2="1284.59" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="1293.32" x2="1303.27" y1="508.939" y2="491.711" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="1311.99" x2="1321.94" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="110.366" x2="130.858" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="147.719" x2="168.212" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bL" x1="129.043" x2="149.535" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bM" x1="110.366" x2="130.858" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bN" x1="185.073" x2="205.565" y1="-1.541" y2="-1.541" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bO" x1="166.396" x2="186.888" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bP" x1="147.719" x2="168.212" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bQ" x1="129.043" x2="149.535" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bR" x1="110.366" x2="130.858" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bS" x1="222.426" x2="242.918" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bT" x1="203.749" x2="224.322" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bU" x1="185.073" x2="205.565" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bV" x1="166.396" x2="186.888" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bW" x1="147.719" x2="168.212" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bX" x1="129.043" x2="149.615" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bY" x1="110.366" x2="130.858" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bZ" x1="259.859" x2="280.432" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ca" x1="241.183" x2="261.675" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cb" x1="222.426" x2="242.918" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cc" x1="203.749" x2="224.322" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cd" x1="185.073" x2="205.565" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ce" x1="166.396" x2="186.969" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cf" x1="147.719" x2="168.212" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cg" x1="129.043" x2="149.615" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ch" x1="110.366" x2="130.858" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ci" x1="297.213" x2="317.705" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cj" x1="278.536" x2="299.029" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ck" x1="259.859" x2="280.432" y1="20.066" y2="20.066" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cl" x1="241.183" x2="261.675" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cm" x1="222.426" x2="242.918" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cn" x1="203.749" x2="224.322" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="co" x1="185.073" x2="205.565" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cp" x1="166.396" x2="186.969" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cq" x1="147.719" x2="168.212" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cr" x1="129.043" x2="149.535" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cs" x1="110.366" x2="130.858" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ct" x1="334.566" x2="355.059" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cu" x1="315.889" x2="336.382" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cv" x1="297.213" x2="317.705" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cw" x1="278.536" x2="299.029" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cx" x1="259.859" x2="280.432" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cy" x1="241.103" x2="261.675" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cz" x1="222.426" x2="242.918" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cA" x1="203.749" x2="224.322" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cB" x1="185.073" x2="205.565" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cC" x1="166.396" x2="186.888" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cD" x1="147.719" x2="168.212" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cE" x1="129.043" x2="149.535" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cF" x1="110.366" x2="130.858" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cG" x1="353.323" x2="373.815" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cH" x1="334.566" x2="355.059" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cI" x1="315.889" x2="336.382" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cJ" x1="297.213" x2="317.705" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cK" x1="278.536" x2="299.109" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cL" x1="259.859" x2="280.432" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cM" x1="241.103" x2="261.675" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cN" x1="222.426" x2="242.918" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cO" x1="203.749" x2="224.322" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cP" x1="185.073" x2="205.565" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cQ" x1="166.396" x2="186.888" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cR" x1="147.719" x2="168.212" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cS" x1="129.043" x2="149.535" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cT" x1="110.366" x2="130.858" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cU" x1="353.323" x2="373.815" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cV" x1="334.566" x2="355.059" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cW" x1="315.889" x2="336.463" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cX" x1="297.213" x2="317.705" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cY" x1="278.536" x2="299.109" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cZ" x1="259.859" x2="280.432" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="da" x1="241.183" x2="261.675" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="db" x1="222.426" x2="242.918" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dc" x1="203.749" x2="224.322" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dd" x1="185.073" x2="205.565" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="de" x1="166.396" x2="186.888" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="df" x1="147.719" x2="168.212" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dg" x1="129.043" x2="149.535" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dh" x1="110.366" x2="130.858" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="di" x1="353.243" x2="373.816" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dj" x1="334.566" x2="355.059" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dk" x1="315.889" x2="336.462" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dl" x1="297.213" x2="317.705" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dm" x1="278.536" x2="299.029" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dn" x1="259.859" x2="280.432" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="do" x1="241.183" x2="261.675" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dp" x1="222.426" x2="242.918" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dq" x1="203.749" x2="224.322" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dr" x1="185.073" x2="205.565" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ds" x1="166.396" x2="186.888" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dt" x1="147.719" x2="168.212" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="du" x1="129.042" x2="149.535" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dv" x1="110.286" x2="130.859" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dw" x1="353.243" x2="373.816" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dx" x1="334.566" x2="355.059" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dy" x1="315.889" x2="336.382" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dz" x1="297.213" x2="317.705" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dA" x1="278.536" x2="299.029" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dB" x1="259.859" x2="280.432" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dC" x1="241.183" x2="261.675" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dD" x1="222.426" x2="242.918" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dE" x1="203.749" x2="224.322" y1="160.369" y2="160.369" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dF" x1="185.073" x2="205.565" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dG" x1="166.396" x2="186.888" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dH" x1="147.719" x2="168.292" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dI" x1="129.043" x2="149.535" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dJ" x1="110.366" x2="130.858" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dK" x1="353.323" x2="373.815" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dL" x1="334.566" x2="355.059" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dM" x1="315.889" x2="336.382" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dN" x1="297.213" x2="317.705" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dO" x1="278.536" x2="299.029" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dP" x1="259.859" x2="280.432" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dQ" x1="241.183" x2="261.675" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dR" x1="222.426" x2="242.918" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dS" x1="203.749" x2="224.322" y1="181.976" y2="181.976" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dT" x1="185.073" x2="205.646" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dU" x1="166.396" x2="186.888" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dV" x1="147.719" x2="168.212" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dW" x1="129.043" x2="149.535" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dX" x1="110.366" x2="130.858" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dY" x1="353.323" x2="373.815" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dZ" x1="334.566" x2="355.059" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ea" x1="315.889" x2="336.382" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eb" x1="297.213" x2="317.705" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ec" x1="278.536" x2="299.029" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ed" x1="259.859" x2="280.432" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ee" x1="241.183" x2="261.675" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ef" x1="222.426" x2="242.999" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eg" x1="203.749" x2="224.322" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eh" x1="185.073" x2="205.565" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ei" x1="166.396" x2="186.888" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ej" x1="129.043" x2="149.535" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ek" x1="110.366" x2="130.858" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="el" x1="147.719" x2="168.212" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="em" x1="353.323" x2="373.815" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="en" x1="334.566" x2="355.059" y1="149.585" y2="149.585" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eo" x1="315.889" x2="336.382" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ep" x1="297.213" x2="317.705" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eq" x1="278.536" x2="299.029" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="er" x1="259.859" x2="280.432" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="es" x1="241.183" x2="261.675" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="et" x1="222.426" x2="242.918" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eu" x1="129.043" x2="149.535" y1="268.322" y2="268.322" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ev" x1="110.366" x2="130.858" y1="279.065" y2="279.065" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ew" x1="147.719" x2="168.212" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ex" x1="166.396" x2="186.888" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ey" x1="185.073" x2="205.565" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ez" x1="203.749" x2="224.322" y1="225.108" y2="225.108" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eA" x1="-1.227" x2="224.241" y1="112.671" y2="112.671" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".25"/>
+      <stop offset=".777" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="eB" x1="1586.71" x2="1607.2" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eC" x1="1586.71" x2="1607.2" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eD" x1="1568.03" x2="1588.52" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eE" x1="1568.03" x2="1588.52" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eF" x1="1568.03" x2="1588.52" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eG" x1="1549.35" x2="1569.84" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eH" x1="1549.35" x2="1569.84" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eI" x1="1549.35" x2="1569.84" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eJ" x1="1530.68" x2="1551.17" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eK" x1="1530.68" x2="1551.17" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eL" x1="1530.68" x2="1551.17" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eM" x1="1530.68" x2="1551.17" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eN" x1="1512" x2="1532.49" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eO" x1="1512" x2="1532.49" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eP" x1="1512" x2="1532.49" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eQ" x1="1493.32" x2="1513.81" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eR" x1="1493.32" x2="1513.81" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eS" x1="1493.32" x2="1513.81" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eT" x1="1493.32" x2="1513.81" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eU" x1="1474.57" x2="1495.06" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eV" x1="1474.57" x2="1495.06" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eW" x1="1474.57" x2="1495.06" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eX" x1="1455.89" x2="1476.38" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eY" x1="1455.89" x2="1476.38" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eZ" x1="1455.89" x2="1476.38" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fa" x1="1455.89" x2="1476.38" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fb" x1="1437.21" x2="1457.78" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fc" x1="1437.21" x2="1457.7" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fd" x1="1437.21" x2="1457.7" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fe" x1="1418.54" x2="1439.03" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ff" x1="1418.54" x2="1439.03" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fg" x1="1418.54" x2="1439.03" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fh" x1="1418.54" x2="1439.03" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fi" x1="1437.21" x2="1457.7" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fj" x1="1418.54" x2="1439.03" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fk" x1="1474.57" x2="1495.06" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fl" x1="1437.21" x2="1457.7" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fm" x1="1418.54" x2="1439.03" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fn" x1="1455.89" x2="1476.38" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fo" x1="1437.21" x2="1457.7" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fp" x1="1418.54" x2="1439.03" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fq" x1="1455.89" x2="1476.38" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fr" x1="1474.57" x2="1495.06" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fs" x1="1493.32" x2="1513.81" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ft" x1="1512" x2="1532.49" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fu" x1="1109.3" x2="1532.45" y1="-95.896" y2="-95.896" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="fv" x1="1513.16" x2="1513.16" y1="538.721" y2="149.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.11.x/img/nomad-panel-learn.svg b/content/nomad/v0.11.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..090a5b337a
--- /dev/null
+++ b/content/nomad/v0.11.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="#BDBEC2" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.11.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v0.11.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v0.11.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.11.x/img/nomad_fault_tolerance.png b/content/nomad/v0.11.x/img/nomad_fault_tolerance.png
new file mode 100644
index 0000000000..dcac5802a3
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad_fault_tolerance.png differ
diff --git a/content/nomad/v0.11.x/img/nomad_network_arch.png b/content/nomad/v0.11.x/img/nomad_network_arch.png
new file mode 100644
index 0000000000..554d0b85e1
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad_network_arch.png differ
diff --git a/content/nomad/v0.11.x/img/nomad_reference_diagram.png b/content/nomad/v0.11.x/img/nomad_reference_diagram.png
new file mode 100644
index 0000000000..b6e7ea2894
Binary files /dev/null and b/content/nomad/v0.11.x/img/nomad_reference_diagram.png differ
diff --git a/content/nomad/v0.11.x/img/og-image.png b/content/nomad/v0.11.x/img/og-image.png
new file mode 100644
index 0000000000..7faccf445c
Binary files /dev/null and b/content/nomad/v0.11.x/img/og-image.png differ
diff --git a/content/nomad/v0.11.x/img/pattern.svg b/content/nomad/v0.11.x/img/pattern.svg
new file mode 100644
index 0000000000..ce1eefa887
--- /dev/null
+++ b/content/nomad/v0.11.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="#BDBEC2" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.11.x/img/prometheus-targets.png b/content/nomad/v0.11.x/img/prometheus-targets.png
new file mode 100644
index 0000000000..f8c567f162
Binary files /dev/null and b/content/nomad/v0.11.x/img/prometheus-targets.png differ
diff --git a/content/nomad/v0.11.x/img/routing-table.png b/content/nomad/v0.11.x/img/routing-table.png
new file mode 100644
index 0000000000..28de2e8434
Binary files /dev/null and b/content/nomad/v0.11.x/img/routing-table.png differ
diff --git a/content/nomad/v0.11.x/img/running-jobs.png b/content/nomad/v0.11.x/img/running-jobs.png
new file mode 100644
index 0000000000..69e005ae47
Binary files /dev/null and b/content/nomad/v0.11.x/img/running-jobs.png differ
diff --git a/content/nomad/v0.11.x/img/sentinel.jpg b/content/nomad/v0.11.x/img/sentinel.jpg
new file mode 100644
index 0000000000..5ce7fa54b6
Binary files /dev/null and b/content/nomad/v0.11.x/img/sentinel.jpg differ
diff --git a/content/nomad/v0.11.x/img/terminal-circle.svg b/content/nomad/v0.11.x/img/terminal-circle.svg
new file mode 100644
index 0000000000..ea76caabc9
--- /dev/null
+++ b/content/nomad/v0.11.x/img/terminal-circle.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 50 50">
+  <circle cx="25" cy="25" r="25" fill="#FFF"/>
+</svg>
diff --git a/content/nomad/v0.11.x/img/traefik_ui.png b/content/nomad/v0.11.x/img/traefik_ui.png
new file mode 100644
index 0000000000..787a7df67e
Binary files /dev/null and b/content/nomad/v0.11.x/img/traefik_ui.png differ
diff --git a/content/nomad/v0.12.x/content/api-docs/acl-policies.mdx b/content/nomad/v0.12.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..9611f95bf1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,168 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+sidebar_title: ACL Policies
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/acl-tokens.mdx b/content/nomad/v0.12.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..9cca68460b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,344 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+sidebar_title: ACL Tokens
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](https://learn.hashicorp.com/nomad?track=acls#acls) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/agent.mdx b/content/nomad/v0.12.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..2daeb9a26e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/agent.mdx
@@ -0,0 +1,728 @@
+---
+layout: api
+page_title: Agent - HTTP API
+sidebar_title: Agent
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string!
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "protocol_version_max": "3",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "protocol_version": "1",
+      "protocol_version_min": "0",
+      "snapshot_version_min": "0",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/host`   | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/allocations.mdx b/content/nomad/v0.12.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..b2567b51c0
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/allocations.mdx
@@ -0,0 +1,698 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+sidebar_title: Allocations
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": "5000000000"
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2017-07-25T23:36:26.106431265Z",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400,
+    "ModifyTime": 1495747371794276400
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:3.2"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:3.2"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was singled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Task": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/client.mdx b/content/nomad/v0.12.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..e90601b6ca
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/client.mdx
@@ -0,0 +1,618 @@
+---
+layout: api
+page_title: Client - HTTP API
+sidebar_title: Client
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/deployments.mdx b/content/nomad/v0.12.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..b92b1e0cfd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/deployments.mdx
@@ -0,0 +1,539 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+sidebar_title: Deployments
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/evaluations.mdx b/content/nomad/v0.12.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..02c576e2f5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,267 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+sidebar_title: Evaluations
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Priority": 50,
+  "Type": "service",
+  "TriggeredBy": "job-register",
+  "JobID": "example",
+  "JobModifyIndex": 52,
+  "NodeID": "",
+  "NodeModifyIndex": 0,
+  "Status": "complete",
+  "StatusDescription": "",
+  "Wait": 0,
+  "NextEval": "",
+  "PreviousEval": "",
+  "BlockedEval": "",
+  "FailedTGAllocs": null,
+  "ClassEligibility": null,
+  "EscapedComputedClass": false,
+  "AnnotatePlan": false,
+  "SnapshotIndex": 53,
+  "QueuedAllocations": {
+    "cache": 0
+  },
+  "CreateIndex": 53,
+  "ModifyIndex": 55
+}
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/index.mdx b/content/nomad/v0.12.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..0909816963
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/index.mdx
@@ -0,0 +1,222 @@
+---
+layout: api
+page_title: HTTP API
+sidebar_title: HTTP API Overview
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+This documentation is only for the v1 API.
+
+~> **Backwards compatibility:** At the current version, Nomad does not yet
+promise backwards compatibility even with the v1 prefix. We'll remove this
+warning when this policy changes. We expect to reach API stability by Nomad
+1.0.
+
+## Addressing &amp; Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad Enterprise has support for namespaces, which allow jobs and their associated objects to be segmented from each other and other users of the cluster.  When using non-default namespace, the API request must pass the target namespace as an API query parameter.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v0.12.x/content/api-docs/jobs.mdx b/content/nomad/v0.12.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..8f88712fce
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/jobs.mdx
@@ -0,0 +1,1868 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+sidebar_title: Jobs
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 300000000000,
+          "Attempts": 10,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 36000000000000,
+          "MaxDelay": 3600000000000,
+          "Unlimited": false
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" { type = \"service\" group \"cache\" {} }",
+  "Canonicalize": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Stop": false,
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Update": {
+          "Stagger": 0,
+          "MaxParallel": 1,
+          "HealthCheck": "checks",
+          "MinHealthyTime": 10000000000,
+          "HealthyDeadline": 300000000000,
+          "AutoRevert": false,
+          "Canary": 0
+        },
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": [
+          {
+            "Attribute": "${node.datacenter}",
+            "SpreadTarget": null,
+            "Weight": 100
+          }
+        ],
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Spreads": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 1,
+      "HealthCheck": "",
+      "MinHealthyTime": 0,
+      "HealthyDeadline": 0,
+      "AutoRevert": false,
+      "Canary": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Spreads": null,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stable": false,
+    "Version": 0,
+    "CreateIndex": 7,
+    "ModifyIndex": 7,
+    "JobModifyIndex": 7
+  }
+]
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 15 KB.
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": "...",
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `purge` `(bool: false)` - Specifies that the job should stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status <sup>Beta</sup>
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group <sup>Beta</sup>
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/json-jobs.mdx b/content/nomad/v0.12.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..36d454696d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1064 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+sidebar_title: JSON Jobs
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+This guide covers the JSON syntax for submitting jobs to Nomad. A useful command
+for generating valid JSON versions of HCL jobs is:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+## Syntax
+
+Below is the JSON representation of the job outputted by `$ nomad init`:
+
+```json
+{
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Migrate": {
+          "HealthCheck": "checks",
+          "HealthyDeadline": 300000000000,
+          "MaxParallel": 1,
+          "MinHealthyTime": 10000000000
+        },
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Header": {},
+                    "Method": "",
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false,
+                    "CheckRestart": {
+                      "Limit": 3,
+                      "Grace": 30000000000,
+                      "IgnoreWarnings": false
+                    }
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 0,
+          "MaxDelay": 3600000000000,
+          "Unlimited": true
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+The example JSON could be submitted as a job using the following:
+
+```shell-session
+$ curl -XPUT -d @example.json http://127.0.0.1:4646/v1/job/example
+{
+  "EvalID": "5d6ded54-0b2a-8858-6583-be5f476dec9d",
+  "EvalCreateIndex": 12,
+  "JobModifyIndex": 11,
+  "Warnings": "",
+  "Index": 12,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Values other than default are not allowed in non-Enterprise versions of Nomad.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the Qemu driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+  - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+    checks do not have an `auto` address mode as there's no way for
+    Nomad to know which is the best address to use for checks. Consul
+    needs access to the address for any HTTP or TCP checks. Added in
+    Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+    from the `Service`.
+
+  - `PortLabel`: Specifies the label of the port on which the check will
+    be performed. Note this is the _label_ of the port and not the port
+    number unless `AddressMode: "driver"`. The port label must match one
+    defined in the Network stanza. If a port value was declared on the
+    `Service`, this will inherit from that value if not supplied. If
+    supplied, this value takes precedence over the `Service.PortLabel`
+    value. This is useful for services which operate on multiple ports.
+    `http` and `tcp` checks require a port while `script` checks do not.
+    Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+    later numeric ports may be used if `AddressMode: "driver"` is set on
+    the check.
+
+  - `Header`: Headers for HTTP checks. Should be an object where the values are an
+    array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+  - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+    certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update stanza can be specified at the job or task group level.
+When specified at the job, the update stanza is inherited by all task groups.
+When specified in both the job and in a task group, the stanzas are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /docs/commands/node/drain
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v0.12.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v0.12.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..83177d5a8e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+sidebar_title: Libraries &amp; SDKs
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/master/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://godoc.org/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Official Ruby client
+  for the Nomad HTTP API
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v0.12.x/content/api-docs/metrics.mdx b/content/nomad/v0.12.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..d2d5407732
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/metrics.mdx
@@ -0,0 +1,97 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+sidebar_title: Metrics
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/namespaces.mdx b/content/nomad/v0.12.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..8173ddb14c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+sidebar_title: Namespaces
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 31,
+    "Description": "Production API Servers",
+    "ModifyIndex": 31,
+    "Name": "api-prod",
+    "Quota": ""
+  },
+  {
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 5,
+    "Name": "default",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 31,
+  "Description": "Production API Servers",
+  "Quota": "",
+  "Hash": "N8WvePwqkp6J354eLJMKyhvsFdPELAos0VuBfMoVKoU=",
+  "ModifyIndex": 31,
+  "Name": "api-prod"
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Quota": "prod-quota"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/nodes.mdx b/content/nomad/v0.12.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..814687d99f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1034 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+sidebar_title: Nodes
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "0.10.0-dev",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 0,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2019-08-26T12:22:50+02:00"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 9,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": null,
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host",
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v0.12.x/content/api-docs/operator.mdx b/content/nomad/v0.12.x/content/api-docs/operator.mdx
new file mode 100644
index 0000000000..0b2271a9d8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/operator.mdx
@@ -0,0 +1,659 @@
+---
+layout: api
+page_title: Operator - HTTP API
+sidebar_title: Operator
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# /v1/operator
+
+The `/operator` endpoint provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/docs/commands/operator) command.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4
+```
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:8300",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:8205",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. This API was introduced in
+Nomad 0.9 and currently supports enabling/disabling preemption. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "ModifyIndex": 5,
+    "SchedulerAlgorithm": "spread",
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft commit index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler binpacks or spreads allocations on available nodes.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server stanza will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes.  Possible values are
+  `"binpack"` and `"spread"`
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "temporary license customer",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": [
+        "governance-policy"
+      ]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "temporary-license",
+    "Modules": [
+      "governance-policy"
+    ],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
+
+## Updating the Nomad Enterprise License
+
+This endpoint updates the Nomad license.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `PUT`  | `/v1/operator/license` | `application/json` |
+
+
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+
+### Sample Payload
+
+The payload is the raw license blob.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @nomad.license \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15
+}
+```
+
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
+
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/docs/internals/consensus).
+
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v0.12.x/content/api-docs/plugins.mdx b/content/nomad/v0.12.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..f7e3392a60
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/plugins.mdx
@@ -0,0 +1,138 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+sidebar_title: Plugins
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/quotas.mdx b/content/nomad/v0.12.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..a9e2febd42
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/quotas.mdx
@@ -0,0 +1,351 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+sidebar_title: Quotas
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://github.com/hashicorp/nomad/blob/master/api/quota.go#L100-L131).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/regions.mdx b/content/nomad/v0.12.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..dd0559f09d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/regions.mdx
@@ -0,0 +1,37 @@
+---
+layout: api
+page_title: Regions - HTTP API
+sidebar_title: Regions
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/scaling-policies.mdx b/content/nomad/v0.12.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..626c6986f3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,103 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+sidebar_title: Scaling Policies <sup>Beta</sup>
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies <sup>Beta</sup>
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 10,
+    "Enabled": true,
+    "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+    "ModifyIndex": 10,
+    "Target": {
+      "Group": "cache",
+      "Job": "example",
+      "Namespace": "default"
+    }
+  }
+]
+```
+
+## Read Scaling Policy <sup>Beta</sup>
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/search.mdx b/content/nomad/v0.12.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..cac8ff3821
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/search.mdx
@@ -0,0 +1,120 @@
+---
+layout: api
+page_title: Search - HTTP API
+sidebar_title: Search
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+or volumes. When using Nomad Enterprise, the allowed contexts include quotas
+and namespaces. Additionally, a prefix can be searched for within every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v0.12.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..455a050100
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,178 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+sidebar_title: Sentinel Policies
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](https://learn.hashicorp.com/nomad/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/nomad?track=acls#operations-and-development).
+
+~> **Enterprise Only!** This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/status.mdx b/content/nomad/v0.12.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..f56e328ba7
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/status.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: Status - HTTP API
+sidebar_title: Status
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/system.mdx b/content/nomad/v0.12.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..6a8d5e4e6b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+sidebar_title: System
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/ui.mdx b/content/nomad/v0.12.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..98b21f70a3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/ui.mdx
@@ -0,0 +1,264 @@
+---
+layout: api
+page_title: UI
+sidebar_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+Starting in v0.7, the Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/`
+will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter. Namespaces are an enterprise feature.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the node the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the node the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Nodes List
+
+This page lists all nodes in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path        | Produces    |
+| ----------- | ----------- |
+| `/ui/nodes` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of client nodes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible client nodes. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the client nodes list that should be visible. This
+  is specified as a query string parameter.
+
+## Node Detail
+
+This page shows the details of a node, including the node name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                 | Produces    |
+| -------------------- | ----------- |
+| `/ui/nodes/:node_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression uses to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 0)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
diff --git a/content/nomad/v0.12.x/content/api-docs/validate.mdx b/content/nomad/v0.12.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..92f04330b5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/validate.mdx
@@ -0,0 +1,65 @@
+---
+layout: api
+page_title: Validate - HTTP API
+sidebar_title: Validate
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to a server. In the event a server can't be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v0.12.x/content/api-docs/volumes.mdx b/content/nomad/v0.12.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..ea2843aec7
--- /dev/null
+++ b/content/nomad/v0.12.x/content/api-docs/volumes.mdx
@@ -0,0 +1,367 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+sidebar_title: Volumes
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` endpoints are used to query for and interact with volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "volume-id1",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "volume-id1",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:3.2"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. It is an error
+to register an existing volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that described the volume's
+parameters.
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "volume-id1",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "PluginID": "plugin-id1"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Delete Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method  | Path                         | Produces           |
+| ------- | ---------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)`- Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node.  It is an
+error to detach a volume that is in use.
+
+| Method  | Path                                | Produces           |
+| ------- | ----------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)`- The node to detach the volume from.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id/detach
+```
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/agent.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/agent.mdx
new file mode 100644
index 0000000000..d96b31dd84
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/agent.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Agent
+sidebar_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.conf -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.conf`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+## General Parameters
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+## `http` Block
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+### `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
+
+## `nomad` Block
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+### `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+## `policy` Block
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+}
+```
+
+### `policy` Parameters
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+## `apm` Block
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+### `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+## `target` Block
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+### `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+## `strategy` Block
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+### `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: https://learn.hashicorp.com/nomad/governance-and-policy/namespaces
+[nomad_acls]: https://learn.hashicorp.com/nomad?track=acls#acls
+[autoscaler_cli_config]: /docs/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /docs/autoscaling/cli#policy-dir
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/api.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/api.mdx
new file mode 100644
index 0000000000..1b9591314d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/api.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: HTTP API
+sidebar_title: API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent.
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:8080/v1/health
+```
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/cli.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/cli.mdx
new file mode 100644
index 0000000000..7d44bd1f40
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/cli.mdx
@@ -0,0 +1,108 @@
+---
+layout: docs
+page_title: CLI
+sidebar_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`:  The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /docs/autoscaling/agent
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/index.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/index.mdx
new file mode 100644
index 0000000000..38f09a3bc7
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/index.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Autoscaling
+sidebar_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. The source code can be viewed on [GitHub][autoscaler_github] and releases
+are available on the [HashiCorp releases page][autoscaler_releases] or via
+[Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the autoscaler.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the number of instances of an application
+to have sufficient work throughput to meet service-level agreements (SLA). In
+Nomad, horizontal application autoscaling can be achieved by modifying the number
+of allocations in a task group based on the value of a relevant metric, such as
+CPU and memory utilization or number of open connections. This is enabled by configuring
+[autoscaling policies][autoscaling_policy] on individual Nomad jobs using the [`scaling` block][scaling_block].
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients from a cluster to ensure there
+is an appropriate amount of cluster resource for the scheduled applications.
+This is achieved by interacting with remote providers to start or terminate new
+Nomad clients based on metrics such as the remaining free schedulable CPU or memory.
+Cluster scaling is enabled by configuring the [autoscaler agent](/docs/autoscaling/agent#dir)
+with policies targeting the Nomad cluster.
+
+[scaling_block]: /docs/job-specification/scaling
+[autoscaling_policy]: /docs/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler/tree/master/demo
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/internals/checks.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/internals/checks.mdx
new file mode 100644
index 0000000000..b317d075af
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/internals/checks.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: Checks
+sidebar_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Nomad Autoscaler Check Calculations
+
+A scaling policy can include several checks all of which produce a scaling
+suggesting. The checks are executed at the same time during a policy evaluation
+and the results can conflict with each other. In a scenario like this, the
+autoscaler iterates the results the chooses the safest result which results in
+retaining the most capacity of the resource.
+
+In a scenario where two checks return different desired directions, the following
+logic is applied.
+
+- `ScaleOut and ScaleIn   => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn  and ScaleNone => ScaleNone`
+
+In situations where the two same actions are suggested, but with different counts the
+following logic is applied, where the count is the absolute desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3)   and  ScaleIn(4) => ScaleIn(4)`
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/internals/index.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/internals/index.mdx
new file mode 100644
index 0000000000..4def6a4be8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/internals/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Internals
+sidebar_title: Internals
+description: >
+  This section covers the internals of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Internals
+
+This section covers the internals of the Nomad Autoscaler and explains the
+technical details of how it functions, its architecture, and sub-systems.
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/plugins/apm.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/apm.mdx
new file mode 100644
index 0000000000..60f6606140
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/apm.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: APM
+sidebar_title: APM
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+APMs are used to store metrics about an applications performance and current
+state. The APM (Application Performance Management) plugin is responsible for
+querying the APM and returning a value which will be used to determine if
+scaling should occur.
+
+## Prometheus APM Plugin
+
+Use [Prometheus][prometheus_io] metrics to scale your Nomad job task groups or
+cluster. The query performed on Prometheus should return a single value. You can
+use the [scalar][prometheus_scaler_function] function in your query to achieve
+this.
+
+### Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+### Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "scalar(avg((haproxy_server_current_sessions{backend=\"http_back\"}) and (haproxy_server_up{backend=\"http_back\"} == 1)))"
+  ...
+}
+```
+
+## Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+### Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+### Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+### Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "percentage-allocated_cpu"
+  ...
+}
+```
+
+Querying Nomad client node metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[prometheus_io]: https://prometheus.io/
+[prometheus_scaler_function]: https://prometheus.io/docs/prometheus/latest/querying/functions/#scalar
+[nomad_telemetry_stanza]: /docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/plugins/index.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..ab37e4f83e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: Plugins
+sidebar_title: Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task;
+APM plugins retrieve metrics about the workloads being monitored and Strategy
+plugins decide which actions Nomad should execute to keep the policy valid. The
+flexibility of plugins allows the Nomad Autoscaler to be extended to meet specific
+business requirements or technology use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections.
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/plugins/strategy.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/strategy.mdx
new file mode 100644
index 0000000000..ae70cb92f3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/strategy.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Strategy
+sidebar_title: Strategy
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current count and a metric value for a task group or from servers in a
+cluster, and output what the new count should be.
+
+## Target Value Strategy Plugin
+
+The target value strategy plugin will perform count calculations in order to keep
+the value resulting from the APM query at or around a specified target.
+
+### Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check {
+  ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  ...
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/plugins/target.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/target.mdx
new file mode 100644
index 0000000000..ae711f6493
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/plugins/target.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: Target
+sidebar_title: Target
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target Plugins determine where the resource to be autoscaled is located. All
+target plugins support the `dry-run` policy config parameter which allows a policy
+to be evaluated, but will noop any suggested changes.
+
+## Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+### Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad"
+}
+```
+
+### Policy Configuration Options
+
+If using the [Nomad job specification scaling stanza][nomad_scaling_stanza] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check {
+  ...
+  target "nomad" {
+    Job   = "example"
+    Group = "cache"
+  }
+  ...
+```
+
+- `job` `(string: "") ` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` stanza][nomad_job_stanza].
+
+- `group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` stanza][nomad_group_stanza].
+
+## AWS AutoScaling Group Target
+
+The AWS ASG target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+### Agent Configuration Options
+
+To use the AWS ASG target plugin, the agent configuration needs to be populated
+with the appropriate target block. Authentication to the AWS API can be supplied
+in a number of ways including EC2 instance roles. It is recommended, if possible
+to use the [Vault AWS Secrets engine][vault_aws_backend] for supplying access
+credentials to the plugin. Credentials should be injected into the configuration
+via a template rather than as environment variables. This ensures the credentials
+are passed only to the plugin, rather than being available for all plugins and
+the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "",
+            "Effect": "Allow",
+            "Action": [
+                "ec2:TerminateInstances",
+                "ec2:DescribeInstanceStatus",
+                "autoscaling:UpdateAutoScalingGroup",
+                "autoscaling:DetachInstances",
+                "autoscaling:DescribeScalingActivities",
+                "autoscaling:DescribeAutoScalingGroups",
+                "autoscaling:CreateOrUpdateTags"
+            ],
+            "Resource": "*"
+        }
+    ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region        = "eu-west-3"
+    aws_access_key_id = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_key_id = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token which provides
+the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API.
+
+- `aws_secret_key_id` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+### Policy Configuration Options
+
+```hcl
+check {
+  ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+  }
+  ...
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `node_class` `(string: <required>)` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain deadline][nomad_node_drain_deadline]
+  to use when performing node draining actions.
+
+[nomad_node_class]: https://www.nomadproject.io/docs/configuration/client#node_class
+[nomad_node_drain_deadline]: https://www.nomadproject.io/api-docs/nodes#deadline
+[nomad_scaling_stanza]: /docs/job-specification/scaling
+[nomad_group_stanza]: /docs/job-specification/group#group-stanza
+[nomad_job_stanza]: /docs/job-specification/job#job-stanza
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[vault_aws_backend]: https://www.vaultproject.io/docs/secrets/aws
diff --git a/content/nomad/v0.12.x/content/docs/autoscaling/policy.mdx b/content/nomad/v0.12.x/content/docs/autoscaling/policy.mdx
new file mode 100644
index 0000000000..53c396859c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/autoscaling/policy.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: Scaling Policies
+sidebar_title: Policy
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the
+[task group `scaling` stanza][jobspec_scaling_stanza] or by configuration
+files stored on disk.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## `policy` Options
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page.
+
+### Example
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` stanza or via a file within the `policy_dir` can be seen below.
+
+```hcl
+min     = 2
+max     = 10
+enabled = true
+
+policy {
+  evaluation_interval = "5s"
+  cooldown            = "1m"
+
+  target "target" {
+    Job   = "example"
+    Group = "example"
+  }
+
+  check "active_connections" {
+    source = "prometheus"
+    query  = "scalar(open_connections_example_cache)"
+
+    strategy "target_value" {
+      target = 10
+    }
+  }
+}
+```
+
+[policy_default_cooldown_agent]: /docs/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /docs/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /docs/autoscaling/plugins/target
+[strategy_plugin_docs]: /docs/autoscaling/plugins/strategy
+[apm_plugin_docs]: /docs/autoscaling/plugins/apm
+[jobspec_scaling_stanza]: /docs/job-specification/scaling
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..836c720e09
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+sidebar_title: bootstrap
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Bootstrap the initial token:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/index.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..766d3d1a26
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+sidebar_title: acl
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /docs/commands/acl/bootstrap
+[policyapply]: /docs/commands/acl/policy-apply
+[policydelete]: /docs/commands/acl/policy-delete
+[policyinfo]: /docs/commands/acl/policy-info
+[policylist]: /docs/commands/acl/policy-list
+[tokencreate]: /docs/commands/acl/token-create
+[tokenupdate]: /docs/commands/acl/token-update
+[tokendelete]: /docs/commands/acl/token-delete
+[tokeninfo]: /docs/commands/acl/token-info
+[tokenlist]: /docs/commands/acl/token-list
+[tokenself]: /docs/commands/acl/token-self
+[secure-guide]: https://learn.hashicorp.com/nomad/acls/fundamentals
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..3f7c8d7cc3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+sidebar_title: policy apply
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..95d88b9710
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+sidebar_title: policy delete
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..d2bf26165f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+sidebar_title: policy info
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..417e797b73
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+sidebar_title: policy list
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..678b9756b8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+sidebar_title: token create
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..6bd65565aa
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+sidebar_title: token delete
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..6adcb7d5b8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+sidebar_title: token info
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..1599643556
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+sidebar_title: token list
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..a3544208d1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+sidebar_title: token self
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v0.12.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..6f5004ff68
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+sidebar_title: token update
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/agent-info.mdx b/content/nomad/v0.12.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..ddbbe6ac48
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+sidebar_title: agent-info
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/agent.mdx b/content/nomad/v0.12.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..6970eb8213
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/agent.mdx
@@ -0,0 +1,225 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+sidebar_title: agent
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-network-speed=<MBits>`: Equivalent to the Client
+  [network_speed] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /docs/configuration/consul#address
+[alloc_dir]: /docs/configuration/client/#alloc_dir
+[auth]: /docs/configuration/consul#auth
+[auto_advertise]: /docs/configuration/consul#auto_advertise
+[bind_addr]: /docs/configuration/#bind_addr
+[bootstrap_expect]: /docs/configuration/server/#bootstrap_expect
+[ca_file]: /docs/configuration/consul#ca_file
+[cert_file]: /docs/configuration/consul#cert_file
+[checks_use_advertise]: /docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /docs/configuration/consul#client_auto_join
+[client_http_check_name]: /docs/configuration/consul#client_http_check_name
+[client_service_name]: /docs/configuration/consul#client_service_name
+[configuration]: /docs/configuration
+[data_dir]: /docs/configuration#data_dir
+[datacenter]: /docs/configuration/#datacenter
+[enabled]: /docs/configuration/acl#enabled
+[encryption overview]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption
+[key_file]: /docs/configuration/consul#key_file
+[log_json]: /docs/configuration#log_json
+[log_level]: /docs/configuration#log_level
+[meta]: /docs/configuration/client/#meta
+[name]: /docs/configuration/#name
+[network_interface]: /docs/configuration/client/#network_interface
+[network_speed]: /docs/configuration/client/#network_speed
+[node_class]: /docs/configuration/client/#node_class
+[nomad agent]: /docs/install/production/nomad-agent
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: /docs/configuration/#region
+[rejoin_after_leave]: /docs/configuration/server/#rejoin_after_leave
+[replication_token]: /docs/configuration/acl#replication_token
+[retry_interval]: /docs/configuration/server/#retry_interval
+[retry_max]: /docs/configuration/server/#retry_max
+[server_auto_join]: /docs/configuration/consul#server_auto_join
+[server_http_check_name]: /docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /docs/configuration/consul#server_serf_check_name
+[server_service_name]: /docs/configuration/consul#server_service_name
+[servers]: /docs/configuration/client/#servers
+[ssl]: /docs/configuration/consul#ssl
+[state_dir]: /docs/configuration/client/#state_dir
+[token]: /docs/configuration/consul#token
+[verify_ssl]: /docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..6b84e32bc5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+sidebar_title: exec
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..25a404924d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+sidebar_title: fs
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an allocation directory on a Nomad
+client. The following functionalities are available - `cat`, `tail`, `ls` and
+`stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a path.
+The path is relative to the root of the allocation directory. The path is
+optional and it defaults to `/` of the allocation directory.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/index.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..d6f2c4e73e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+sidebar_title: alloc
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..62ffbb746f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+sidebar_title: logs
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..3f35090410
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+sidebar_title: restart
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be restarted.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..061c14b955
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+sidebar_title: signal
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/status.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..27a103b800
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+sidebar_title: status
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v0.12.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..646eb53285
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+sidebar_title: stop
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..b1eaa2c9d2
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+sidebar_title: fail
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/index.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..d5eb0bb24c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+sidebar_title: deployment
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /docs/commands/deployment/list 'List all deployments'
+[pause]: /docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/list.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..9930700c5b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+sidebar_title: list
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..569d233b87
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+sidebar_title: pause
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..1ee5ed8e9e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+sidebar_title: promote
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..582137151d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+sidebar_title: resume
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/status.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..c854211c18
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+sidebar_title: status
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       2        2       2        0
+web         2        2       2        0
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       0        0
+web         N/A       2        0         2       2        0
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v0.12.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..a3b8a59d4f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+sidebar_title: unblock
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
+[federated regions]: https://learn.hashicorp.com/nomad/operating-nomad/federation
diff --git a/content/nomad/v0.12.x/content/docs/commands/eval-status.mdx b/content/nomad/v0.12.x/content/docs/commands/eval-status.mdx
new file mode 100644
index 0000000000..eb7aaeaf76
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/eval-status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+sidebar_title: eval status
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output the evaluation in its JSON format.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/index.mdx b/content/nomad/v0.12.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..affda0b623
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Commands (CLI)
+sidebar_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash or zsh shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/deployments.mdx b/content/nomad/v0.12.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..d130f56966
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+sidebar_title: deployments
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v0.12.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..926f9eb444
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+sidebar_title: dispatch
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16KiB**.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+[eval status]: /docs/commands/eval-status
+[parameterized job]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/eval.mdx b/content/nomad/v0.12.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..a4b77976aa
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+sidebar_title: eval
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/history.mdx b/content/nomad/v0.12.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..e6ba1c89e5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+sidebar_title: history
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/index.mdx b/content/nomad/v0.12.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..8026c0fb74
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: job'
+sidebar_title: job
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /docs/commands/job/promote "Promote a job's canaries"
+[revert]: /docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/init.mdx b/content/nomad/v0.12.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..217f29cb45
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+sidebar_title: init
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[drivers]: /docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/inspect.mdx b/content/nomad/v0.12.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..9b0e151c4e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+sidebar_title: inspect
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /api-docs/jobs
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v0.12.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..86b1fce684
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+sidebar_title: periodic force
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /docs/commands/eval-status
+[force the evaluation]: /api-docs/jobs#force-new-periodic-instance
+[periodic job]: /docs/job-specification/periodic
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/plan.mdx b/content/nomad/v0.12.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..46fdf0209f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,205 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+sidebar_title: plan
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:3.2"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+[job specification]: /docs/job-specification
+[hcl job specification]: /docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /docs/commands/job/run#check-index
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/promote.mdx b/content/nomad/v0.12.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..dbdde983a6
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+sidebar_title: promote
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/revert.mdx b/content/nomad/v0.12.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..aafe64a0ca
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+sidebar_title: revert
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  \$CONSUL_HTTP_TOKEN environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  \$VAULT_TOKEN environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:3.2"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /docs/commands/job/history
+[eval status]: /docs/commands/eval-status
+[consul service identity]: /docs/configuration/consul#allow_unauthenticated
+[vault policy]: /docs/configuration/vault#allow_unauthenticated
+[run]: /docs/commands/job/run
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/run.mdx b/content/nomad/v0.12.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..dfbf104046
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+sidebar_title: run
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions and placement information for the provided job. The monitor will
+exit after scheduling has finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+If the job has specified the region, the -region flag and `\$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the \$CONSUL_HTTP_TOKEN
+  environment variable and that found in the job.
+
+- `-vault-token`: If set, the passed Vault token is stored in the job before
+  sending to the Nomad servers. This allows passing the Vault token without
+  storing it in the job file. This overrides the token found in the \$VAULT_TOKEN
+  environment variable and that found in the job.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement:
+
+```shell-session
+$ nomad job run job1.nomad
+==> Monitoring evaluation "52dee78a"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+    Allocation "5e0b39f0" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "52dee78a" finished with status "complete"
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> Monitoring evaluation "5ef16dff"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5ef16dff" finished with status "complete"
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> Monitoring evaluation "2ae0e6a5"
+    Evaluation triggered by job "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /docs/commands/job/plan
+[eval status]: /docs/commands/eval-status
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/status.mdx b/content/nomad/v0.12.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..490d2a4e6d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+sidebar_title: status
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/stop.mdx b/content/nomad/v0.12.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..c74018f13d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+sidebar_title: stop
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+    Stop a [multi-region] job in all its regions. By default, `job stop` will
+    stop only a single region at a time. Ignored for single-region jobs.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /docs/commands/eval-status
+[multi-region]: /docs/job-specification/multiregion
diff --git a/content/nomad/v0.12.x/content/docs/commands/job/validate.mdx b/content/nomad/v0.12.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..0339a00d14
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+sidebar_title: validate
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+## Examples
+
+Validate a job with invalid syntax:
+
+```shell-session
+$ nomad job validate example.nomad
+Job validation errors:
+1 error(s) occurred:
+
+* group "cache" -> task "redis" -> config: 1 error(s) occurred:
+
+* field "image" is required
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v0.12.x/content/docs/commands/license/get.mdx b/content/nomad/v0.12.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..6c96eb91dc
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+sidebar_title: get
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise license.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/license/index.mdx b/content/nomad/v0.12.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..42e6e6d91f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: license'
+sidebar_title: license
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+- [`license put`][put] - Set the current license
+
+[get]: /docs/commands/license/get 'Get the current license'
+[put]: /docs/commands/license/put 'Set the current license'
diff --git a/content/nomad/v0.12.x/content/docs/commands/license/put.mdx b/content/nomad/v0.12.x/content/docs/commands/license/put.mdx
new file mode 100644
index 0000000000..56ec7e1d7a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/license/put.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: license put'
+sidebar_title: put
+description: |
+  The license put command is used to set the Nomad Enterprise license.
+---
+
+# Command: license put
+
+The `license put` command is used to set the Nomad Enterprise license.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license put
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+```plaintext
+Install a new license from a file:
+
+        $ nomad license put <path>
+
+Install a new license from stdin:
+
+        $ nomad license put -
+```
+
+## Examples
+
+Set a license using a path
+
+```shell-session 
+$ nomad license put /path/to/my/license.txt
+```
+
+Set a license using a path
+
+```shell-session 
+$ nomad license put -
+
+02MV4UU43BK5HGYYTOJZWFQMTMNNEWU33JLJKES6S2NJMXUWLKIV2E2RCCNRMXSMBQLJKFSM2MK5KTKTLKLF2FS6SJPFNFIYZVJV5GI2S2K5LGUSLJO5UVSM2WPJSEOOLULJMEUZTBK5IWST3JJF5E4VCBPJHFIWTMJZJTANCZK5LGUTCXJJVVU2SRORHUIVLYJVBTC2KNNJATCTKEMM2VSMSONBNEISLJJRBUU4DCNZHDAWKXPBZVSWCSOBRDENLGMFLVC2KPNFEXCSLJO5UWCWCOPJSFOVTGMRDWY5C2KNETMSLKJF3U22SBORGUIVLUJVCGQVKNKRITMTLKJU3E26TDOVHHURJRJVVEC52NPJATGV3JJFZUS3SOGBMVQSRQLAZVE4DCK5KWST3JJF4U2RCJO5GFIQJRJRKECNCWIRAXOT3KIF3U62SBO5LWSSLTJFWVMNDDI5WHSWKYKJYGEMRVMZSEO3DULJJUSNSJNJEXOTLKIF2E2RCVORGUI3CVJVCECNSNIRATMTKEIJQUS2LXNFSEOVTZMJLWY5KZLBJHAYRSGVTGIR3MORNFGSJWJFVES52NNJAXITKEKV2E2VCCKVGUIQJWJVCECNSNIRBGCSLJO5UWGSCKOZNEQVTKMRBUSNSJNU2XMYSXIZVUS2LXNFNG26DILIZU22KPNZZWSYSXHFVWIV3YNRRXSSJWK54UU3TCGNNGYY3NGVUGE3KONRGFQQ
+
+<ctrl-d>
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/monitor.mdx b/content/nomad/v0.12.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..3fa44e165d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+sidebar_title: monitor
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..e3417386b8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+sidebar_title: apply
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <namespace>
+```
+
+The `namespace apply` command requires the name of the namespace to be created
+or updated.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+## Examples
+
+Create a namespace with a quota
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..d25485ecdf
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+sidebar_title: delete
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/index.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..7a8b064ae6
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+sidebar_title: namespace
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /docs/commands/namespace/list 'List available namespaces'
+[status]: /docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..b859061848
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+sidebar_title: inspect
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/list.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..dc03ce9a0b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+sidebar_title: list
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/namespace/status.mdx b/content/nomad/v0.12.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..3ee41fbefe
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+sidebar_title: status
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespace commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name        = default
+Description = Default shared namespace
+Quota       = shared-default-quota
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/node/config.mdx b/content/nomad/v0.12.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..7477749b67
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+sidebar_title: config
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /docs/configuration/client#servers
diff --git a/content/nomad/v0.12.x/content/docs/commands/node/drain.mdx b/content/nomad/v0.12.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..6976759351
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+sidebar_title: drain
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] stanza until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are force removed from the
+  node. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Force remove allocations off the node immediately.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node
+  without being force stopped after a certain deadline.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs are stopped
+  last. You should always use this flag when draining a node running
+  [CSI node plugins][internals-csi].
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /docs/commands/node/eligibility
+[migrate]: /docs/job-specification/migrate
+[node status]: /docs/commands/node/status
+[workload migration guide]: https://learn.hashicorp.com/nomad/operating-nomad/node-draining
+[internals-csi]: /docs/internals/plugins/csi
diff --git a/content/nomad/v0.12.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v0.12.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..d82dbbbd6e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+sidebar_title: eligibility
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+elegibility disabled are ineligibile for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained!
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /docs/commands/node/drain
diff --git a/content/nomad/v0.12.x/content/docs/commands/node/index.mdx b/content/nomad/v0.12.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..d5563d4cb8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: node'
+sidebar_title: node
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /docs/commands/node/config 'View or modify client configuration details'
+[drain]: /docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v0.12.x/content/docs/commands/node/status.mdx b/content/nomad/v0.12.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..15d38804b8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,364 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+sidebar_title: status
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-get-config.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-get-config.mdx
new file mode 100644
index 0000000000..5464e951f3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-get-config.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+sidebar_title: autopilot get-config
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: https://learn.hashicorp.com/nomad/operating-nomad/autopilot
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-set-config.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-set-config.mdx
new file mode 100644
index 0000000000..d9f87562a2
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/autopilot-set-config.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+sidebar_title: autopilot set-config
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /docs/configuration/server#upgrade_version
+[autopilot guide]: https://learn.hashicorp.com/nomad/operating-nomad/autopilot
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/debug.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..05158f02fd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+sidebar_title: debug
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the log monitor command.
+  Defaults to `"2m"`. Logs will be captured from specified servers and
+  nodes at `log-level`.
+
+- `-interval=2m`: The interval between snapshots of the Nomad state.
+   If unspecified, only one snapshot is captured.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-node-id=n1,n2`: Comma separated list of Nomad client node ids, to
+   monitor for logs and include pprof data. Accepts id prefixes.
+
+- `-server-id=s1,s2`: Comma separated list of Nomad server names, or
+   the special server name "leader" to monitor for logs and include
+   pprof data.
+
+- `-output=path`: Path to the parent directory of the output
+   directory. Defaults to the current directory. If specified, no
+   archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+    `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+    file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+    environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+    environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+    environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+    environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+    certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+    environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+    variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+    environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+    environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+    environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+    certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints the name of the timestamped archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 20s -interval 5s -server-id leader -node-id 6e,dd
+Starting debugger and capturing cluster data...
+    Interval: '5s'
+    Duration: '20s'
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-07-20-205223Z.tar.gz
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/index.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..42aa7cb179
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+sidebar_title: operator
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+  
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[get-config]: /docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /api-docs/operator 'Operator API documentation'
+[outage recovery guide]: https://learn.hashicorp.com/nomad/operating-nomad/outage
+[remove]: /docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
+[snapshot-save]: /docs/commands/operator/snapshot-save 'Snapshot Save command'
+[snapshot-restore]: /docs/commands/operator/snapshot-restore 'Snapshot Restore command'
+[snapshot-inspect]: /docs/commands/operator/snapshot-inspect 'Snapshot Inspect command'
+[snapshot-agent]: /docs/commands/operator/snapshot-agent 'Snapshot Agent command'
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..3baf7bfd6a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+sidebar_title: keygen
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+YgZOXLMhC7TtZqeghMT8+w==
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..1ac7282ba5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+sidebar_title: keyring
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/raft-list-peers.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/raft-list-peers.mdx
new file mode 100644
index 0000000000..2a41bd2e4e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/raft-list-peers.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+sidebar_title: raft list-peers
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The Raft list-peers command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /api-docs/operator
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/raft-remove-peer.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/raft-remove-peer.mdx
new file mode 100644
index 0000000000..9f0081e9c5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/raft-remove-peer.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+sidebar_title: raft remove-peer
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /docs/commands/server/members 'Nomad server members command'
+[operator]: /api-docs/operator 'Nomad Operator API'
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-agent.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-agent.mdx
new file mode 100644
index 0000000000..eb7310f105
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-agent.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+sidebar_title: snapshot agent
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:8500"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+(Note: Non-Solaris platforms only)
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-inspect.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-inspect.mdx
new file mode 100644
index 0000000000..0be3ae6d1c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-inspect.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+sidebar_title: snapshot inspect
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-restore.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-restore.mdx
new file mode 100644
index 0000000000..292f1fa15e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-restore.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+sidebar_title: snapshot restore
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-save.mdx b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-save.mdx
new file mode 100644
index 0000000000..e9f0fc96dd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/operator/snapshot-save.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+sidebar_title: snapshot save
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
diff --git a/content/nomad/v0.12.x/content/docs/commands/plugin/index.mdx b/content/nomad/v0.12.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..fee7edf365
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+sidebar_title: plugin
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[status]: /docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v0.12.x/content/docs/commands/plugin/status.mdx b/content/nomad/v0.12.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..df1cdf012c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+sidebar_title: status
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/apply.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..0f113d3f80
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+sidebar_title: apply
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <name> <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/delete.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..ccfbf5679e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+sidebar_title: delete
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/index.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..264e91c1b1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+sidebar_title: quota
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /docs/commands/quota/apply
+[quotadelete]: /docs/commands/quota/delete
+[quotainit]: /docs/commands/quota/init
+[quotainspect]: /docs/commands/quota/inspect
+[quotalist]: /docs/commands/quota/list
+[quotastatus]: /docs/commands/quota/status
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/init.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..c0d1168e39
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+sidebar_title: init
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..d34c100efd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+sidebar_title: inspect
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/list.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..4ec7223d1f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+sidebar_title: list
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/quota/status.mdx b/content/nomad/v0.12.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..0ca2350018
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+sidebar_title: status
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v0.12.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..8f78ad97b0
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+sidebar_title: apply
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v0.12.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..a57a18c59a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+sidebar_title: delete
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v0.12.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..d1db0d0fea
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+sidebar_title: sentinel
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /docs/commands/sentinel/delete
+[list]: /docs/commands/sentinel/list
+[read]: /docs/commands/sentinel/read
+[apply]: /docs/commands/sentinel/apply
diff --git a/content/nomad/v0.12.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v0.12.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..b80836ea00
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+sidebar_title: list
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v0.12.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..e49c1a38af
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+sidebar_title: read
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v0.12.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..61a437888b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+sidebar_title: force-leave
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/server/index.mdx b/content/nomad/v0.12.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..a56135439b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: server'
+sidebar_title: server
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /docs/commands/server/join 'Join server nodes together'
+[members]: /docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v0.12.x/content/docs/commands/server/join.mdx b/content/nomad/v0.12.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..3f4eba7a53
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+sidebar_title: join
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/server/members.mdx b/content/nomad/v0.12.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..f45bcc513a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+sidebar_title: members
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Server Members Options
+
+- `-detailed`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in the
+  standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name          Addr      Port  Status  Proto  Build     DC   Region
+node1.global  10.0.0.8  4648  alive   2      0.1.0dev  dc1  global
+node2.global  10.0.0.9  4648  alive   2      0.1.0dev  dc1  global
+```
+
+Detailed view:
+
+```shell-session
+$ nomad server members -detailed
+Name   Addr      Port  Tags
+node1  10.0.0.8  4648  bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+node2  10.0.0.9  4648  bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/status.mdx b/content/nomad/v0.12.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..a57901788d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/status.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'Commands: status'
+sidebar_title: status
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/system/gc.mdx b/content/nomad/v0.12.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..aff2c38074
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+sidebar_title: gc
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/system/index.mdx b/content/nomad/v0.12.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..afdf094f9b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: system'
+sidebar_title: system
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v0.12.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v0.12.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..f8d1cc0719
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+sidebar_title: reconcile summaries
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/ui.mdx b/content/nomad/v0.12.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..903032844d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/ui.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+sidebar_title: ui
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/version.mdx b/content/nomad/v0.12.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b3d756dd9e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/version.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: version'
+sidebar_title: version
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v0.12.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v0.12.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..0b7e3f3ddf
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+sidebar_title: deregister
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be deregistered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v0.12.x/content/docs/commands/volume/detach.mdx b/content/nomad/v0.12.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..9b80ba0e66
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+sidebar_title: detach
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v0.12.x/content/docs/commands/volume/index.mdx b/content/nomad/v0.12.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..67930c1555
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+sidebar_title: volume
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume register`][register] - Register a volume.
+- [`volume status`][status] - Display status information about a volume
+
+[deregister]: /docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /docs/commands/volume/detach 'Detach a volume'
+[register]: /docs/commands/volume/register 'Register a volume'
+[status]: /docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v0.12.x/content/docs/commands/volume/register.mdx b/content/nomad/v0.12.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..815f80135c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+sidebar_title: register
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be registered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying
+the path to a file containing a valid [volume
+specification][volume_specification]. This file will be read and the
+job will be submitted to Nomad for scheduling. If the supplied path is
+"-", the job file is read from STDIN. Otherwise it is read from the
+file at the supplied path.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+The file may be provided as either HCL or JSON. An example HCL configuration:
+
+```hcl
+id = "ebs_prod_db1"
+name = "database"
+type = "csi"
+external_id = "vol-23452345"
+plugin_id = "ebs-prod"
+access_mode = "single-node-writer"
+attachment_mode = "file-system"
+mount_options {
+   fs_type = "ext4"
+   mount_flags = ["ro"]
+}
+secrets {
+   example_secret = "xyzzy"
+}
+parameters {
+    skuname = "Premium_LRS"
+}
+context {
+    endpoint = "http://192.168.1.101:9425"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This will
+  be how [`volume`][csi_volume] stanzas in a jobspec refer to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only
+  `"csi"` is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume
+  from the storage provider. For example, the volume ID of an AWS EBS
+  volume or Digital Ocean volume.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI
+  plugin][csi_plugin] that manages this volume.
+
+- `access_mode` `(string: <required>)` - Defines whether a volume
+  should be available concurrently. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only
+  single-node modes. Consult the documentation of the storage provider
+  and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will
+  be used by the volume. Most storage providers will support
+  `"file-system"`, to mount pre-formatted file system volumes. Some
+  storage providers will support `"block-device"`, which will require
+  the job be configured with appropriate mount options.
+
+- `mount_options` <code>([mount_options][]:nil)</code> - Options for
+  mounting `block-device`volumes without a pre-formatted file system.
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `"ro,noatime"`)
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings used as credentials for publishing and
+  unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  configure the volume. The details of these parameters are specific
+  to each storage provider, so please see the specific plugin
+  documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  validate the volume. The details of these parameters are specific to
+  each storage provider, so please see the specific plugin
+  documentation for more information.
+
+[volume_specification]: #volume-specification
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volumes]: /docs/job-specification/volume
diff --git a/content/nomad/v0.12.x/content/docs/commands/volume/status.mdx b/content/nomad/v0.12.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..8788167d05
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+sidebar_title: status
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify
+  times are shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.12.x/content/docs/configuration/acl.mdx b/content/nomad/v0.12.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..bb4e193416
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: acl Stanza - Agent Configuration
+sidebar_title: acl
+description: >-
+  The "acl" stanza configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Stanza
+
+<Placement groups={['acl']} />
+
+The `acl` stanza configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  client configuration options depend on this value.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region.
+
+[secure-guide]: https://learn.hashicorp.com/nomad/acls/fundamentals
diff --git a/content/nomad/v0.12.x/content/docs/configuration/audit.mdx b/content/nomad/v0.12.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..3423d3aeec
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,297 @@
+---
+layout: docs
+page_title: audit Stanza - Agent Configuration
+sidebar_title: audit
+description: >-
+  The "audit" stanza configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Stanza
+
+<Placement groups={['audit']} />
+
+The `audit` stanza configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit stanza (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enable = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to 
+`"enforced"` meaning that all requests must successfully be written to the sink 
+in order for HTTP requests to successfully complete.
+
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-stanza): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-stanza)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Stanza
+
+The `sink` stanza is used to make audit logging sinks for events to be 
+sent to. Currently only a single sink is supported.
+
+The key of the stanza corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the 
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  hault request execution if the audit log event fails to be written to it's sink.
+  `"best-effort"` will not hault request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be 
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use it's configured 
+  [`data_dir`](/docs/configuration#data_dir) for a combined path of 
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit log
+  file archives to keep. If 0 no files are ever deleted.
+
+### `filter` Stanza
+
+The `filter` stanza is used to create filters to filter __out__ matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit 
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern](https://github.com/ryanuber/go-glob/blob/master/README.md#example) matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to 
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages 
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this 
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`.
+The first entry is for the `OperationReceived` stage. The second entry is for
+the `OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": [
+        "anonymous"
+      ],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
diff --git a/content/nomad/v0.12.x/content/docs/configuration/autopilot.mdx b/content/nomad/v0.12.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..f986c69d70
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: autopilot Stanza - Agent Configuration
+sidebar_title: autopilot
+description: >-
+  The "autopilot" stanza configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Stanza
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` stanza configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers = true
+    last_contact_threshold = "200ms"
+    max_trailing_logs = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v0.12.x/content/docs/configuration/client.mdx b/content/nomad/v0.12.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..40eea277f1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/client.mdx
@@ -0,0 +1,471 @@
+---
+layout: docs
+page_title: client Stanza - Agent Configuration
+sidebar_title: client
+description: |-
+  The "client" stanza configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Stanza
+
+<Placement groups={['client']} />
+
+The `client` stanza configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## Plugin Options
+
+Nomad 0.9 now supports pluggable drivers. Operators should use the new
+[plugin][plugin-stanza] syntax to modify driver configuration. To find the
+plugin options supported by each individual Nomad driver, please see the
+[drivers documentation](/docs/drivers). The pre-0.9 `client.options`
+stanza will be supported in 0.9 for backward compatibility (except for the `lxc`
+driver) but will be removed in a future release.
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks.
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `network_speed` `(int: 0)` - Specifies an override for the network link speed.
+  This value, if set, overrides any detected or defaulted link speed. Most
+  clients can determine their speed automatically, and thus in most cases this
+  should be left unset.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, 20% of the node's CPU could be reserved to target a CPU utilization
+  of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting CNI networks.
+	 
+- `bridge_network name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.66.0/23")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/docs/job-specification/template) stanzas.
+
+- `host_volume` <code>([host_volume](#host_volume-stanza): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-stanza): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/docs/drivers/exec#chroot) for
+the full list.
+
+### `options` Parameters
+
+~> Note: client configuration options for drivers will soon be deprecated. See
+the [plugin stanza][plugin-stanza] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/docs/drivers).
+
+- `"driver.whitelist"` `(string: "")` - Specifies a comma-separated list of
+  whitelisted drivers . If specified, drivers not in the whitelist will be
+  disabled. If the whitelist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.whitelist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.blacklist"` `(string: "")` - Specifies a comma-separated list of
+  blacklisted drivers . If specified, drivers in the blacklist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.blacklist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.blacklist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.blacklist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.blacklist"` `(string: see below)` - Specifies a comma-separated
+  blacklist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.blacklist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.blacklist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.whitelist"` `(string: "")` - Specifies a comma-separated list of
+  whitelisted fingerprinters. If specified, any fingerprinters not in the
+  whitelist will be disabled. If the whitelist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.whitelist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.blacklist"` `(string: "")` - Specifies a comma-separated list of
+  blacklisted fingerprinters. If specified, any fingerprinters in the blacklist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.blacklist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separated the two inclusive ends.
+
+### `template` Parameters
+
+- `function_blacklist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the task directory.
+
+### `host_volume` Stanza
+
+The `host_volume` stanza is used to make volumes available to jobs.
+
+The key of the stanza corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Stanza
+
+The `host_network` stanza is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the stanza corresponds to the name of the network used in the
+[`host_network`](/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+    If an address is found on the node that is contained by this cidr block, the
+    host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  network_speed = 500
+  node_class    = "prod"
+
+  meta {
+    "owner" = "ops"
+    "cached_binaries" = "redis,apache,nginx,jq,cypress,nodejs"
+    "rack" = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[server-join]: /docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
diff --git a/content/nomad/v0.12.x/content/docs/configuration/consul.mdx b/content/nomad/v0.12.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..09922fb1b6
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,180 @@
+---
+layout: docs
+page_title: consul Stanza - Agent Configuration
+sidebar_title: consul
+description: |-
+  The "consul" stanza configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Stanza
+
+<Placement groups={['consul']} />
+
+The `consul` stanza configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` stanza is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the bind address.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: https://learn.hashicorp.com/nomad/operating-nomad/clustering 'Automatic Bootstrapping'
diff --git a/content/nomad/v0.12.x/content/docs/configuration/index.mdx b/content/nomad/v0.12.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..91d0e2b211
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/index.mdx
@@ -0,0 +1,344 @@
+---
+layout: docs
+page_title: Agent Configuration
+sidebar_title: Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+  network_speed = 10
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this stanza take
+  precedence over the default [bind_addr](#bind_addr).
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most common
+    bind address to change.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this stanza take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the address
+  private IP found is advertised. You may advertise an alternate port as well.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address advertised to Nomad client nodes. This allows
+    advertising a different RPC address than is used by Nomad Servers such that
+    the clients can connect to the Nomad servers if they are behind a NAT.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+  ~> **WARNING**: This directory **must not** be set to a directory that is
+  [included in the chroot](/docs/drivers/exec#chroot) if you use the
+  [`exec`](/docs/drivers/exec) driver.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins.
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to "nomad-{timestamp}.log".
+  This setting can be combined with `log_rotate_bytes` and `log_rotate_duration`
+  for a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older log
+  file archives to keep. If 0 no files are ever deleted.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin stanza may be repeated, once for each plugin being
+  configured. The key of the stanza is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
diff --git a/content/nomad/v0.12.x/content/docs/configuration/plugin.mdx b/content/nomad/v0.12.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..6f583cd7dc
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: plugin Stanza - Agent Configuration
+sidebar_title: plugin
+description: The "plugin" stanza is used to configure a Nomad plugin.
+---
+
+# `plugin` Stanza
+
+<Placement groups={['plugin']} />
+
+The `plugin` stanza is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v0.12.x/content/docs/configuration/sentinel.mdx b/content/nomad/v0.12.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..f83d147321
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: sentinel Stanza - Agent Configuration
+sidebar_title: sentinel
+description: >-
+  The "sentinel" stanza configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Stanza
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` stanza configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v0.12.x/content/docs/configuration/server.mdx b/content/nomad/v0.12.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..d46d55d40f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/server.mdx
@@ -0,0 +1,297 @@
+---
+layout: docs
+page_title: server Stanza - Agent Configuration
+sidebar_title: server
+description: |-
+  The "server" stanza configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Stanza
+
+<Placement groups={['server']} />
+
+The `server` stanza configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use -
+  for server-specific data, including the replicated log. By default, this is -
+  the top-level [data_dir](/docs/configuration#data_dir)
+  suffixed with "server", like `"/opt/nomad/server"`. This must be an absolute
+  path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 16 bytes that are
+  base64-encoded. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the
+  [encryption documentation][encryption] for more details on this option
+  and its impact on the cluster.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `protocol_version` `(int: 1)` - Specifies the Nomad protocol version to use
+  when communicating with other Nomad servers. This value is typically not
+  required as the agent internally knows the latest version, but may be useful
+  in some upgrade scenarios.
+
+- `raft_protocol` `(int: 2)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/docs/telemetry/metrics) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](https://learn.hashicorp.com/nomad/operating-nomad/autopilot).
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  stanza][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join stanza][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration stanza. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/nomad/operating-nomad/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` stanza
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+   the [update scheduler configuration][update-scheduler-config] API. This
+   option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm = "spread"
+
+    preemption_config {
+      batch_scheduler_enabled   = true
+      system_scheduler_enabled  = true
+      service_scheduler_enabled = true
+    }
+  }
+}
+```
+
+[encryption]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /api-docs/operator#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /docs/faq#bootstrapping
diff --git a/content/nomad/v0.12.x/content/docs/configuration/server_join.mdx b/content/nomad/v0.12.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..dff84264ce
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,230 @@
+---
+layout: docs
+page_title: server_join Stanza - Agent Configuration
+sidebar_title: server_join
+description: >-
+  The "server_join" stanza specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Stanza
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join']
+  ]}
+/>
+
+The `server_join` stanza specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud_auto_join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+````
+
+```json
+{
+"retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+````
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v0.12.x/content/docs/configuration/telemetry.mdx b/content/nomad/v0.12.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..680553eca3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: telemetry Stanza - Agent Configuration
+sidebar_title: telemetry
+description: |-
+  The "telemetry" stanza configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Stanza
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` stanza configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` stanza. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` stanza,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `backwards_compatible_metrics` `(bool: false)` - Specifies if Nomad should
+  publish metrics that are backwards compatible with versions below 0.7, as
+  post version 0.7, Nomad emits tagged metrics. All new metrics will
+  only be added to tagged metrics. Note that this option is used to transition
+  monitoring to tagged metrics and will eventually be deprecated.
+
+- `disable_tagged_metrics` `(bool: false)` - Specifies if Nomad should not emit
+  tagged metrics and only emit metrics compatible with versions below Nomad
+  0.7. Note that this option is used to transition monitoring to tagged
+  metrics and will eventually be deprecated.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v0.12.x/content/docs/configuration/tls.mdx b/content/nomad/v0.12.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..f04a0f0578
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: tls Stanza - Agent Configuration
+sidebar_title: tls
+description: |-
+  The "tls" stanza configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers, clients, and between.
+---
+
+# `tls` Stanza
+
+<Placement groups={['tls']} />
+
+The `tls` stanza configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` stanza. To understand how to setup the certificates themselves, please see
+the [Encryption Overview Guide](https://learn.hashicorp.com/nomad/transport-security/gossip-encryption).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` stanzas. Remember that the
+`tls` stanza is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v0.12.x/content/docs/configuration/vault.mdx b/content/nomad/v0.12.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..5af2e31c4b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Stanza - Agent Configuration
+sidebar_title: vault
+description: |-
+  The "vault" stanza configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Stanza
+
+<Placement groups={['vault']} />
+
+The `vault` stanza configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp/#inlinecode-tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp/#inlinecode-tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces/index.html)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive child tokens for jobs
+  requesting tokens.
+  Visit the [Vault Integration Guide](/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v0.12.x/content/docs/devices/community.mdx b/content/nomad/v0.12.x/content/docs/devices/community.mdx
new file mode 100644
index 0000000000..f6e894e1f8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/devices/community.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Device Plugins.
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+## Authoring Device Plugins
+
+Nomad has a plugin system for defining device drivers. External device plugins
+will have the same user experience as built in drivers. For details on
+authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
diff --git a/content/nomad/v0.12.x/content/docs/devices/index.mdx b/content/nomad/v0.12.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..bb403ea6d3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/devices/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in Nomad.
+Devices are physical hardware that exists on a node such as a GPU or an FPGA. By
+having extensible device plugins, Nomad has the flexibility to support a broad
+set of devices and allows the community to build additional device plugins as
+needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
+
+For details on authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
diff --git a/content/nomad/v0.12.x/content/docs/devices/nvidia.mdx b/content/nomad/v0.12.x/content/docs/devices/nvidia.mdx
new file mode 100644
index 0000000000..09a928bc1f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/devices/nvidia.mdx
@@ -0,0 +1,335 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+sidebar_title: Nvidia
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nvidia-gpu`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad. The Nvidia
+plugin is built into Nomad and does not need to be downloaded separately.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nvidia-gpu` the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+
+### Docker Driver Requirements
+
+In order to use the Nvidia driver plugin with the Docker driver, please follow
+the installation instructions for
+[`nvidia-docker`](<https://github.com/NVIDIA/nvidia-docker/wiki/Installation-(version-1.0)>).
+
+## Plugin Configuration
+
+```hcl
+plugin "nvidia-gpu" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nvidia-gpu` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Restrictions
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver] and plans to
+bring support to the built-in [`exec`][exec-driver] and [`java`][java-driver]
+drivers. Support for [`lxc`][lxc-driver] should be possible by installing the
+[Nvidia hook](https://github.com/lxc/lxc/blob/master/hooks/nvidia) but is not
+tested or documented by Nomad.
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m43s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2674/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Allocations
+No allocations placed
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m59s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2673/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+
+Allocations
+No allocations placed
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:9.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+ID                  = d250baed
+Eval ID             = 21bd7584
+Name                = gpu-test.smi[0]
+Node ID             = 4d46e59f
+Job ID              = example
+Job Version         = 0
+Client Status       = complete
+Client Description  = All tasks have completed
+Desired Status      = run
+Desired Description = <none>
+Created             = 7s ago
+Modified            = 2s ago
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[docker-driver]: /docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /docs/drivers/external/lxc 'Nomad lxc Driver'
diff --git a/content/nomad/v0.12.x/content/docs/drivers/docker.mdx b/content/nomad/v0.12.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..4ddefbf846
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1025 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+sidebar_title: Docker
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:3.2"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for the container
+  to use.
+
+- `dns_options` - (Optional) A list of DNS options for the container to use.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container to use
+  (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or greater.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl {
+      net.core.somaxconn = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) *Deprecated* A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace when user namespace remapping is enabled on the
+  docker daemon.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the allocation
+  directory can be disabled on clients by setting the `docker.volumes.enabled`
+  option set to false. This will limit volumes to directories that exist inside
+  the allocation directory. We recommend using [`mounts`](#mounts) if you wish
+  to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mounts` - (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-or-volumes)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options {
+          no_copy = false
+          labels {
+            foo = "bar"
+          }
+          driver_config {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-add`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured whitelist.
+  The whitelist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME",
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-drop`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured whitelist.
+  The whitelist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD",
+    ]
+  }
+  ```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in \$PATH,
+"docker-credential-ecr" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script "docker-credential-ecr" in
+\$PATH
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work!
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource stanza and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network stanza and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | true |
+| `nomad alloc exec` | true |
+| filesystem isolation | image |
+| network isolation | host, group, task |
+| volume mounting | all |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver on
+a Nomad client, you can modify them with the [plugin stanza][plugin-stanza] syntax. Below is an example of a configuration (many of the values are the default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "docker-credential-aws"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["CHOWN", "NET_RAW"]
+
+    # allow_caps can also be set to "ALL"
+    # allow_caps = ["ALL"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `allow_caps`<a id="plugin_caps"></a> - A list of allowed Linux capabilities.
+  Defaults to
+  `CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP,SETPCAP,
+  NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE` which is the list of
+  capabilities allowed by docker by default, as defined here. Allows the
+  operator to control which capabilities can be obtained by tasks using cap_add
+  and cap_drop options. Supports the value "ALL" as a shortcut for whitelisting
+  all capabilities.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` stanza:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+- `tls` stanza:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `gc` stanza:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a tasks is received that uses the same image within
+    the delay, the image will be reused.
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+  - `dangling_containers` stanza for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults
+  to "gcr.io/google_containers/pause-amd64:3.0".
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.whitelist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for whitelisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config stanza.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Adriver%2Fdocker+label%3Aplatform-windows
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.12.x/content/docs/drivers/exec.mdx b/content/nomad/v0.12.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..43686b2d92
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+sidebar_title: Isolated Fork/Exec
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | true |
+| `nomad alloc exec` | true |
+| filesystem isolation | chroot |
+| network isolation | host, group |
+| volume mounting | all |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `no_pivot_root` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the
+resources of a process and as such the Nomad agent must be run as root.
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/containerd.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/containerd.mdx
new file mode 100644
index 0000000000..a150dfc1c1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/containerd.mdx
@@ -0,0 +1,198 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+sidebar_title: Containerd
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# Containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+Containerd ([`containerd.io`](https://containerd.io)) is a lightweight container daemon
+for running and managing container lifecycle. Docker daemon also uses containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly using containerd, without Docker!
+The Docker daemon is therefore not required on the host system.
+
+See the project's [`homepage`](https://github.com/Roblox/nomad-driver-containerd) for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be [`downloaded`](https://github.com/Roblox/nomad-driver-containerd/releases/)
+onto the client host in the configured plugin directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+- [`containerd-driver`](https://github.com/Roblox/nomad-driver-containerd/releases/) binary in Nomad's [plugin_dir][plugin_dir].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| send signals | true |
+| exec | true |
+| filesystem isolation | none |
+| volume mounting | true |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since docker also relies on containerd for managing container lifecycle, the example job created by [`nomad init -short`][nomad-init] can easily be adapted to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+        network {
+          mbits = 10
+        }
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+- `privileged` - (Optional) `true` or `false` (default) Run container in privileged mode.
+Your container will have all linux capabilities when running in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root filesystem will be read-only.
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+- `cap_add` - (Optional) Add individual capabilities.
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+- `cap_drop` - (Optional) Drop individual capabilities.
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+- `devices` - (Optional) A list of devices to be exposed to the container.
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+- `mounts` - (Optional) A list of mounts to be mounted in the container.
+Volume, bind and tmpfs type mounts are supported. fstab style [`mount options`](https://github.com/containerd/containerd/blob/master/mount/mount_linux.go#L187-L211) are supported.
+   - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`. **Default:** `volume`.
+   - `target` - (Required) Target path in the container.
+   - `source` - (Optional) Source path on the host.
+   - `options` - (Optional) fstab style [`mount options`](https://github.com/containerd/containerd/blob/master/mount/mount_linux.go#L187-L211). **NOTE:** For bind mounts, atleast `rbind` and `ro` are required.
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+Networking is [`out-of-scope`](https://kubernetes.io/blog/2017/11/containerd-container-runtime-options-kubernetes/#containerd) for containerd. An external CNI plugin might be needed to support networking.
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g. `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /docs/commands/job/init
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/firecracker-task-driver.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..00f1a0f7df
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+sidebar_title: Firecracker driver
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' on nomad's allocation directory.
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' on nomad's allocation directory.
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/iis.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/iis.mdx
new file mode 100644
index 0000000000..2c83a6940b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/iis.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+sidebar_title: Windows IIS
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+    - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+    - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+    - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+    - `hostname` (string)      - (Optional) IIS hostname for a binding.
+    - `ipaddress` (string)     - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+    - `resource_port` (string) - (Optional) Use a label from an established network stanza port. It is recommended to use this approach over using `port`.
+    - `port` (number)          - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+    - `type` (string)          - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+    - `cert_hash` (string)     - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/index.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/index.mdx
new file mode 100644
index 0000000000..4f22a2a018
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [LXC][lxc]
+- [Rkt][rkt]
+- [Podman][podman]
+- [Singularity][singularity]
+- [Jail task driver][jail-task-driver]
+- [Pot][pot]
+- [Firecracker][firecracker-task-driver]
+- [Systemd-Nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+- [Containerd][nomad-driver-containerd]
+
+[lxc]: /docs/drivers/external/lxc
+[rkt]: /docs/drivers/external/rkt
+[plugin_guide]: /docs/internals/plugins
+[singularity]: /docs/drivers/external/singularity
+[jail-task-driver]: /docs/drivers/external/jail-task-driver
+[podman]: /docs/drivers/external/podman
+[pot]: /docs/drivers/external/pot
+[firecracker-task-driver]: /docs/drivers/external/firecracker-task-driver
+[nspawn-driver]: /docs/drivers/external/nspawn
+[nomad-driver-iis]: /docs/drivers/external/iis
+[nomad-driver-containerd]: /docs/drivers/external/containerd
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/jail-task-driver.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/jail-task-driver.mdx
new file mode 100644
index 0000000000..a880fca820
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+sidebar_title: Jailtask driver
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to nomad's allocation directory.
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /docs/configuration#plugin_dir
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/lxc.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/lxc.mdx
new file mode 100644
index 0000000000..e8d7cb4912
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/lxc.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+sidebar_title: LXC
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind-mount host paths to container paths. Mounting host paths outside of the allocation directory can be disabled on clients by setting the [`volumes_enabled`](#volumes_enabled) option set to false. This will limit volumes to directories that exist inside the allocation directory.
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` stanza:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: https://learn.hashicorp.com/nomad/using-plugins/lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/nspawn.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/nspawn.mdx
new file mode 100644
index 0000000000..bab39c448d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/nspawn.mdx
@@ -0,0 +1,182 @@
+---
+layout: docs
+page_title: 'Drivers: Systemd-Nspawn'
+sidebar_title: Systemd-Nspawn
+description: The Nspawn task driver is used to run application containers using Systemd-Nspawn.
+---
+
+# Nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using Systemd-Nspawn for running application
+containers. You can download the external Systemd-Nspawn driver [here][nspawn-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+* [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+* [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+* [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+* [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+* [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+* `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+* [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+* `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+* `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+* [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+* [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+* [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+* [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+* [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+* [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+* [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+* `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+* `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker
+  driver][docker_driver].
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface of
+  your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+* `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+* [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+* `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+* `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+* 64-bit Linux host
+* The `linux_amd64` Nomad binary
+* The Nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+* `systemd-nspawn` to be installed
+* Nomad running with root privileges
+
+## Plugin Options
+
+* `enabled` - The `nspawn` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+* `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+* `driver.nspawn` - Set to `true` if Systemd-Nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+* `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[docker_driver]: /docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /docs/integrations/consul-connect
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/pot.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/pot.mdx
new file mode 100644
index 0000000000..d2cff5da53
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/pot.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+sidebar_title: Pot
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/rkt.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/rkt.mdx
new file mode 100644
index 0000000000..38da283a6a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/rkt.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+sidebar_title: 'Rkt <sup>Deprecated</sup> '
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:3.2"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			mbits = 10
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.12.x/content/docs/drivers/external/singularity.mdx b/content/nomad/v0.12.x/content/docs/drivers/external/singularity.mdx
new file mode 100644
index 0000000000..e160e4d5e3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/external/singularity.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+sidebar_title: Singularity
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. /tmp and \$HOME) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and \$HOME (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v0.12.x/content/docs/drivers/index.mdx b/content/nomad/v0.12.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..ad191d9413
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/index.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Task Drivers
+sidebar_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin stanza][plugin] documentation for examples on how to
+use the `plugin` stanza in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/internals/plugins
+[acl_guide]: https://learn.hashicorp.com/nomad?track=acls#operations-and-development
diff --git a/content/nomad/v0.12.x/content/docs/drivers/java.mdx b/content/nomad/v0.12.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..4b686aa096
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/java.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+sidebar_title: Java
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | false |
+| `nomad alloc exec` | false |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation | host, group |
+| volume mounting | none, all (only for linux) |
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
diff --git a/content/nomad/v0.12.x/content/docs/drivers/podman.mdx b/content/nomad/v0.12.x/content/docs/drivers/podman.mdx
new file mode 100644
index 0000000000..72555a0a3b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/podman.mdx
@@ -0,0 +1,282 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+sidebar_title: Podman
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+See the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be [downloaded][downloaded] onto the client host
+in the configured plugin directory.
+
+- Linux host with [`podman`][podman] installed.
+- [`nomad-driver-podman`][releases] binary in Nomad's [`plugin_dir`][plugin_dir].
+
+You need a varlink enabled Podman binary and a system socket activation unit, see https://podman.io/blogs/2019/01/16/podman-varlink.html.
+
+Since the Nomad agent, nomad-driver-podman plugin binary, and Podman will
+reside on the same host, skip the ssh aspects of the Podman varlink
+documentation above.
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | true |
+| `nomad alloc exec` | false |
+| filesystem isolation | none |
+| network isolation | host, group, task, none |
+| volume mounting | none |
+
+## Known Limitations
+
+The Podman task driver is under active development. It currently does not support [stderr logging][stderr-logging] and [devices][devices].
+Podman recently released [Podman v2](https://podman.io/blogs/2020/06/29/podman-v2-announce.html). The task driver currently supports v1 
+and will be working on supporting v2 in upcoming releases.
+
+## Task Configuration
+
+Due to Podman's similarity to Docker, the example job created by [`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis:3.2"
+
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+
+        network {
+          mbits = 10
+          port  "db"  {}
+        }
+      }
+    }
+  }
+}
+```
+
+- `image` - The image to run.
+
+```hcl
+config {
+  image = "docker://redis"
+}
+```
+
+- `command` - (Optional) The command to run when starting the container.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  _command_ is specified, the arguments are passed directly to the container.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths.
+
+```hcl
+config {
+  volumes = [
+    "/some/host/data:/container/data"
+  ]
+}
+```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for tmpfs mount
+  points. See `podman run --tmpfs` options for details.
+
+```hcl
+config {
+  tmpfs = [
+    "/var"
+  ]
+}
+```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using count) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - Run an init inside the container that forwards signals and reaps processes.
+
+```hcl
+config {
+  init = true
+}
+```
+
+- `init_path` - Path to the container-init binary.
+
+```hcl
+config {
+  init = true
+  init_path = "/usr/libexec/podman/catatonit"
+}
+```
+
+- `user` - Run the command as a specific user/uid within the container. See
+  [task configuration][task].
+
+- `memory_reservation` - Memory soft limit (unit = b (bytes), k (kilobytes), m
+  (megabytes), or g (gigabytes))
+
+After setting memory reservation, when the system detects memory contention or
+low memory, containers are forced to restrict their consumption to their
+reservation. So you should always set the value below --memory, otherwise the
+hard limit will take precedence. By default, memory reservation will be the
+same as memory limit.
+
+```hcl
+config {
+  memory_reservation = "100m"
+}
+```
+
+- `memory_swap` - A limit value equal to memory plus swap. The swap limit
+  should always be larger than the [memory value][memory-value].
+
+Unit can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you
+don't specify a unit, b is used. Set LIMIT to -1 to enable unlimited swap.
+
+```hcl
+config {
+  memory_swap = "180m"
+}
+```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between 0 and 100.
+
+```hcl
+config {
+  memory_swappiness = 60
+}
+```
+
+- `network_mode` - Set the [network mode][network-mode] for the container. This will be
+  overridden by nomad if a group network is created and passed in by Nomad.
+
+  - `bridge` - (default for rootful) create a network stack on the default bridge
+  - `none` - no networking
+  - `container:id` - reuse another container's network stack
+  - `host` - use the Podman host network stack. Note: the host mode gives the container
+    full access to local system services such as D-bus and is therefore considered insecure.
+  - `slirp4netns` - use `slirp4netns` to create a user network stack. This is the default for
+    rootless containers. Podman currently does not support this option for rootful containers ([issue][slirp-issue])
+
+## Networking
+
+Podman supports forwarding and exposing ports like Docker. See [Docker Driver
+configuration][docker-ports] for details.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+  }
+}
+```
+
+- `gc` stanza:
+
+  - `container` - Defaults to `true`. This option can be used to disable
+    Nomad from removing a container when the task exits.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously managed containers
+  will be reused instead of disposed and recreated.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    recover_stopped = false
+  }
+}
+```
+
+[docker-ports]: /docs/drivers/docker#forwarding-and-exposing-ports
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /docs/job-specification/resources#memory
+[nomad-init]: /docs/commands/job/init
+[plugin_dir]: /docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[task]: /docs/job-specification/task#user
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[stderr-logging]: https://github.com/hashicorp/nomad-driver-podman/issues/4
+[devices]: https://github.com/hashicorp/nomad-driver-podman/issues/41
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman 
+
diff --git a/content/nomad/v0.12.x/content/docs/drivers/qemu.mdx b/content/nomad/v0.12.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..2973f54d5d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'Drivers: Qemu'
+sidebar_title: Qemu
+description: The Qemu task driver is used to run virtual machines using Qemu/KVM.
+---
+
+# Qemu Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. Qemu can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. (Note that
+  [prior to qemu 2.10.1](https://github.com/qemu/qemu/commit/ad9579aaa16d5b385922d49edac2c96c79bcfb6),
+  the monitor socket path is limited to 108 characters. Graceful shutdown will
+  be disabled if qemu is < 2.10.1 and the generated monitor path exceeds this
+  length. You may encounter this issue if you set long
+  [data_dir](/docs/configuration#data_dir)
+  or
+  [alloc_dir](/docs/configuration/client#alloc_dir)
+  paths.) This feature is currently not supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to qemu as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | false |
+| `nomad alloc exec` | false |
+| filesystem isolation | image |
+| network isolation | none |
+| volume mounting | none |
+
+## Client Requirements
+
+The `qemu` driver requires Qemu to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if Qemu is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/image/paths"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the Qemu driver is
+  allowed to load images from.
+
+## Resource Isolation
+
+Nomad uses Qemu to provide full software virtualization for virtual machine
+workloads. Nomad can use Qemu KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the Qemu
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
diff --git a/content/nomad/v0.12.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v0.12.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..e57f9c5d2f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+sidebar_title: Raw Fork/Exec
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature | Implementation |
+| --- | --- |
+| `nomad alloc signal` | true |
+| `nomad alloc exec` | true |
+| filesystem isolation | none |
+| network isolation | host, group |
+| volume mounting | none |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin stanza:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v0.12.x/content/docs/enterprise/index.mdx b/content/nomad/v0.12.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..88136dad57
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,119 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+sidebar_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Namespaces, Resource Quotas, Sentinel Policies, and Advanced
+  Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities to Nomad. Nomad Enterprise is available as a base Platform package with an optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and its features in detail.
+
+## Nomad Enterprise Licensing
+
+Nomad Enterprise requires a license to run. When a Enterprise server first starts it will be set with a temporary license that includes all features. This will be valid for 6 hours and allows users to test enterprise features and provide enough time for operators to apply their enterprise license.
+
+If a server is never given a valid license and the temporary license expires, the server will shutdown. If a valid (non-temporary) license expires, the cluster will continue to function, but write operations to enterprise features will be disabled.
+
+See the [License commands](/docs/commands/license) for more information on interacting with the Enterprise License.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as enhances performance and availability through Advanced Autopilot features such as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new servers and then simply wait for the upgrade to complete. As the new servers join the cluster, server logic checks the version of each Nomad server node. If the version is higher than the version on the current set of voters, it will avoid promoting the new servers to voters until the number of new servers matches the number of existing servers at the previous version. Once the numbers match, Nomad will begin to promote new servers and demote old ones.
+
+See the [Autopilot - Upgrade Migrations](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#upgrade-migrations) documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running daemon process or in a one-shot mode from a batch job. The agent takes snapshots of the state of the Nomad servers and saves them locally, or pushes them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the state of Nomad servers within an environment in an automated manner. These snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](https://www.nomadproject.io/docs/commands/operator/snapshot-agent) documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a Nomad cluster. Non-voting servers will receive the replication stream but will not take part in quorum (required by the leader before log entries can be committed). Adding explicit non-voters will scale reads and scheduling without impacting write latency.
+
+See the [Autopilot - Read Scalability](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#server-read-and-scheduling-scaling) documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot standby server on a per availability zone basis. For example, in an environment with three availability zones an operator can run one voter and one non-voter in each availability zone, for a total of six servers. If an availability zone is completely lost, only one voter will be lost, so the cluster remains available. If a voter is lost in an availability zone, Nomad will promote the non-voter to a voter automatically, putting the hot standby server into service quickly.
+
+See the [Autopilot - Redundancy Zones](https://learn.hashicorp.com/nomad/operating-nomad/autopilot#redundancy-zones) documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster to support multiple Vault Namespaces for topology simplicity and fleet consolidation when running Nomad and Vault together. Nomad will automatically retrieve a Vault token based on a job's defined Vault Namespace and make it available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](https://www.nomadproject.io/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an organization to securely operate Nomad at scale across multiple teams through features such as Audit Logging, Namespaces, Resource Quotas, Sentinel Policies, and Cross-Namespace Queries.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to fulfill compliance requirements. This Enterprise feature provides administrators with a complete set of records for all user-issued actions in Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies, ensure enforcement of their security policies, and diagnose cluster behavior by viewing preceding user operations.  Designed as an HTTP API based audit logging system, each audit event is captured with relevant request and response information in a JSON format that is easily digestibile and familiar to operators.
+
+See the [Audit Logging Documentation](/docs/configuration/audit) for a  thorough overview.
+
+### Namespaces
+
+Namespaces enable multiple teams to safely use a shared multi-region Nomad environment and reduce cluster fleet size. In Nomad Enterprise, a shared cluster can be partitioned into multiple namespaces which allow jobs and their associated objects to be isolated from each other and other users of the cluster.
+
+Namespaces enhance the usability of a shared cluster by isolating teams from the jobs of others, by providing fine grain access control to jobs when coupled with ACLs, and by preventing bad actors from negatively impacting the whole cluster.
+
+See the [Namespaces Guide](https://learn.hashicorp.com/nomad/governance-and-policy/namespaces) for a thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams or projects to reduce waste and align budgets. In Nomad Enterprise, operators can define quota specifications and apply them to namespaces. When a quota is attached to a namespace, the jobs within the namespace may not consume more resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas Guide](https://learn.hashicorp.com/nomad/governance-and-policy/quotas) for a thorough overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained policy enforcement. Sentinel policies build on top of the ACL system and allow operators to define policies such as disallowing jobs to be submitted to production on Fridays or only allowing users to run jobs that use pre-authorized Docker images. Sentinel policies are defined as code, giving operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide](https://learn.hashicorp.com/nomad/governance-and-policy/sentinel) for a thorough overview.
+
+### Cross-Namespace Queries
+Cross-Namespace Queries allows operators to query jobs and allocations across all namespaces for faster operator debugging and visibility in multi-tenant clusters. This enterprise feature accelerates and simplifies the debugging process by allowing operators to easily locate faulty jobs and allocations from developers.
+
+See the individual Nomad CLI command documentation (e.g., [alloc exec](https://www.nomadproject.io/docs/commands/alloc/exec#namespace)) for more information.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions.  This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or request a trial
+of Nomad Enterprise.
+
+[Multiregion Deployments]: /docs/job-specification/multiregion
diff --git a/content/nomad/v0.12.x/content/docs/faq.mdx b/content/nomad/v0.12.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..f8e13bef28
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/faq.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+sidebar_title: FAQ
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/docs/internals/consensus) and
+a [gossip protocol](/docs/internals/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+[consul_dc]: https://www.consul.io/docs/agent/options.html#_datacenter
+[consul_fed]: https://www.consul.io/docs/guides/datacenters.html
+[nomad_region]: /docs/configuration#datacenter
+[`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v0.12.x/content/docs/index.mdx b/content/nomad/v0.12.x/content/docs/index.mdx
new file mode 100644
index 0000000000..5d17bf4c3f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/index.mdx
@@ -0,0 +1,14 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation! This documentation is more of a reference
+  guide for all available features and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation! This documentation is a reference guide for
+all available features and options of Nomad. If you are just getting
+started with Nomad, please start with the
+[introduction and getting started guide](/intro) instead.
diff --git a/content/nomad/v0.12.x/content/docs/install/index.mdx b/content/nomad/v0.12.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..6e56002157
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/index.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: Installing Nomad
+sidebar_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation">
+
+You can download a [precompiled binary](https://nomadproject.io/downloads/) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+You can check the locations available on your path by running this command.
+
+```shell-session
+$ echo $PATH
+
+/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
+```
+
+The output is a list of locations separated by colons. You can make Nomad
+available by moving the binary to one of the listed locations, or by adding
+Nomad's location to your `PATH`.
+
+-> **Tip (Linux-based or Mac):** Permanently add a new location to your path by
+editing your shell's settings file (usually called something like `~/.bashrc`,
+where the part of the file name after the `.` and before `rc` is the name of
+your shell). In that file you will see a line that starts with `export PATH=`,
+followed by a colon-separated list of locations. Add the location of the Consul
+binary to that list and save the file. Then reload your shell's configuration
+with the command `source ~/.bashrc`, replacing `bash` with the name of your
+shell.
+
+-> **Tip (Windows):** Add a location to your path via the GUI by navigating to
+`Environment Variables` in your system settings, and looking for the variable
+called `PATH`. You will see a semicolon-separated list of locations. Add the
+Nomad binary's location to that list and then launch a new console window.
+
+</Tab>
+<Tab heading="Linux Packages">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](https://learn.hashicorp.com/consul) and
+[Vault](https://learn.hashicorp.com/vault) with the same command.
+
+</Tab>
+<Tab heading="Homebrew (macOS)">
+
+[Homebrew](https://brew.sh) is a free and open-source package management system
+for macOS. Install the [Nomad formula](https://formulae.brew.sh/formula/nomad)
+from the terminal.
+
+```shell-session
+$ brew install nomad
+```
+
+~> **NOTE:** Homebrew and the Nomad formula are **NOT** directly maintained by
+HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+~> **NOTE**: On macOS, machines without a Java environment installed will be
+prompted to install Java because of a [known issue—#7865][gh-7865]. The linked
+GitHub issue has workarounds for this issue.
+
+</Tab>
+<Tab heading="Chocolatey (Windows)">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+</Tabs>
+
+---
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+[consul-download]: https://www.consul.io/downloads.html
+[destroy]: https://www.vagrantup.com/docs/cli/destroy.html
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+[gpg-key]: https://apt.releases.hashicorp.com/gpg 'HashiCorp GPG key'
diff --git a/content/nomad/v0.12.x/content/docs/install/production/deployment-guide.mdx b/content/nomad/v0.12.x/content/docs/install/production/deployment-guide.mdx
new file mode 100644
index 0000000000..99bd34a87b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/production/deployment-guide.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: Deployment Guide
+sidebar_title: Reference Install Guide
+description: |-
+  This deployment guide covers the steps required to install and
+  configure a single HashiCorp Nomad cluster as defined in the
+  Nomad Reference Architecture
+ea_version: 0.9
+---
+
+# Nomad Reference Install Guide
+
+This deployment guide covers the steps required to install and configure a single HashiCorp Nomad cluster as defined in the [Nomad Reference Architecture](/docs/install/production/reference-architecture).
+
+These instructions are for installing and configuring Nomad on Linux hosts running the systemd system and service manager.
+
+## Reference Material
+
+This deployment guide is designed to work in combination with the [Nomad Reference Architecture](/docs/install/production/reference-architecture) and [Consul Deployment Guide](https://www.consul.io/docs/guides/deployment-guide.html). Although it is not a strict requirement to follow the Nomad Reference Architecture, please ensure you are familiar with the overall architecture design. For example, installing Nomad server agents on multiple physical or virtual (with correct anti-affinity) hosts for high-availability.
+
+## Overview
+
+To provide a highly-available single cluster architecture, we recommend Nomad server agents be deployed to more than one host, as shown in the [Nomad Reference Architecture](/docs/install/production/reference-architecture).
+
+![Reference diagram](/img/nomad_reference_diagram.png)
+
+These setup steps should be completed on all Nomad hosts:
+
+- [Download Nomad](#download-nomad)
+- [Install Nomad](#install-nomad)
+- [Configure systemd](#configure-systemd)
+- [Configure Nomad](#configure-nomad)
+- [Start Nomad](#start-nomad)
+
+## Download Nomad
+
+Precompiled Nomad binaries are available for download at [https://releases.hashicorp.com/nomad/](https://releases.hashicorp.com/nomad/) and Nomad Enterprise binaries are available for download by following the instructions made available to HashiCorp Enterprise customers.
+
+```text
+export NOMAD_VERSION="0.9.0"
+curl --silent --remote-name https://releases.hashicorp.com/nomad/${NOMAD_VERSION}/nomad_${NOMAD_VERSION}_linux_amd64.zip
+```
+
+You may perform checksum verification of the zip packages using the SHA256SUMS and SHA256SUMS.sig files available for the specific release version. HashiCorp provides [a guide on checksum verification](https://www.hashicorp.com/security) for precompiled binaries.
+
+## Install Nomad
+
+Unzip the downloaded package and move the `nomad` binary to `/usr/local/bin/`. Check `nomad` is available on the system path.
+
+```text
+unzip nomad_${NOMAD_VERSION}_linux_amd64.zip
+sudo chown root:root nomad
+sudo mv nomad /usr/local/bin/
+nomad version
+```
+
+The `nomad` command features opt-in autocompletion for flags, subcommands, and arguments (where supported). Enable autocompletion.
+
+```text
+nomad -autocomplete-install
+complete -C /usr/local/bin/nomad nomad
+```
+
+Create a data directory for Nomad.
+
+```text
+sudo mkdir --parents /opt/nomad
+```
+
+## Configure systemd
+
+Systemd uses [documented sane defaults](https://www.freedesktop.org/software/systemd/man/systemd.directives.html) so only non-default values must be set in the configuration file.
+
+Create a Nomad service file at `/etc/systemd/system/nomad.service`.
+
+```text
+sudo touch /etc/systemd/system/nomad.service
+```
+
+Add this configuration to the Nomad service file:
+
+```text
+[Unit]
+Description=Nomad
+Documentation=https://nomadproject.io/docs/
+Wants=network-online.target
+After=network-online.target
+
+[Service]
+ExecReload=/bin/kill -HUP $MAINPID
+ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d
+KillMode=process
+KillSignal=SIGINT
+LimitNOFILE=infinity
+LimitNPROC=infinity
+Restart=on-failure
+RestartSec=2
+StartLimitBurst=3
+StartLimitIntervalSec=10
+TasksMax=infinity
+
+[Install]
+WantedBy=multi-user.target
+```
+
+The following parameters are set for the `[Unit]` stanza:
+
+- [`Description`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Description=) - Free-form string describing the nomad service
+- [`Documentation`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Documentation=) - Link to the nomad documentation
+- [`Wants`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Wants=) - Configure a dependency on the network service
+- [`After`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#After=) - Configure an ordering dependency on the network service being started before the nomad service
+
+The following parameters are set for the `[Service]` stanza:
+
+- [`ExecReload`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecReload=) - Send Nomad a `SIGHUP` signal to trigger a configuration reload
+- [`ExecStart`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=) - Start Nomad with the `agent` argument and path to a directory of configuration files
+- [`KillMode`](https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillMode=) - Treat nomad as a single process
+- [`LimitNOFILE`, `LimitNPROC`](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%20Properties) - Disable limits for file descriptors and processes
+- [`RestartSec`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#RestartSec=) - Restart nomad after 2 seconds of it being considered 'failed'
+- [`Restart`](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Restart=) - Restart nomad unless it returned a clean exit code
+- [`StartLimitBurst`, `StartLimitIntervalSec`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#StartLimitIntervalSec=interval) - Configure unit start rate limiting
+- [`TasksMax`](https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#TasksMax=N) - Disable task limits (only available in systemd >= 226)
+
+The following parameters are set for the `[Install]` stanza:
+
+- [`WantedBy`](https://www.freedesktop.org/software/systemd/man/systemd.unit.html#WantedBy=) - Creates a weak dependency on nomad being started by the multi-user run level
+
+## Configure Nomad
+
+Nomad uses [documented sane defaults](/docs/configuration) so only non-default values must be set in the configuration file. Configuration can be read from multiple files and is loaded in lexical order. See the [full description](/docs/configuration) for more information about configuration loading and merge semantics.
+
+Some configuration settings are common to both server and client Nomad agents, while some configuration settings must only exist on one or the other. Follow the [common configuration](#common-configuration) guidance on all hosts and then the specific guidance depending on whether you are configuring a Nomad [server](#server-configuration) or [client](#client-configuration).
+
+- [Common Nomad configuration](#common-configuration)
+- [Configure a Nomad server](#server-configuration)
+- [Configure a Nomad client](#client-configuration)
+
+### Common configuration
+
+Create a configuration file at `/etc/nomad.d/nomad.hcl`:
+
+```text
+sudo mkdir --parents /etc/nomad.d
+sudo chmod 700 /etc/nomad.d
+sudo touch /etc/nomad.d/nomad.hcl
+```
+
+Add this configuration to the `nomad.hcl` configuration file:
+
+~> **Note:** Replace the `datacenter` parameter value with the identifier you will use for the datacenter this Nomad cluster is deployed in.
+
+```hcl
+datacenter = "dc1"
+data_dir = "/opt/nomad"
+```
+
+- [`datacenter`](/docs/configuration#datacenter) - The datacenter in which the agent is running.
+- [`data_dir`](/docs/configuration#data_dir) - The data directory for the agent to store state.
+
+### Server configuration
+
+Create a configuration file at `/etc/nomad.d/server.hcl`:
+
+```text
+sudo touch /etc/nomad.d/server.hcl
+```
+
+Add this configuration to the `server.hcl` configuration file:
+
+~> **NOTE** Replace the `bootstrap_expect` value with the number of Nomad servers you will use; three or five [is recommended](/docs/internals/consensus#deployment-table).
+
+```hcl
+server {
+  enabled = true
+  bootstrap_expect = 3
+}
+```
+
+- [`server`](/docs/configuration/server#enabled) - Specifies if this agent should run in server mode. All other server options depend on this value being set.
+- [`bootstrap_expect`](/docs/configuration/server#bootstrap_expect) - The number of expected servers in the cluster. Either this value should not be provided or the value must agree with other servers in the cluster.
+
+### Client configuration
+
+Create a configuration file at `/etc/nomad.d/client.hcl`:
+
+```text
+sudo touch /etc/nomad.d/client.hcl
+```
+
+Add this configuration to the `client.hcl` configuration file:
+
+```hcl
+client {
+  enabled = true
+}
+```
+
+- [`client`](/docs/configuration/client#enabled) - Specifies if this agent should run in client mode. All other client options depend on this value being set.
+
+~> **NOTE** The [`options`](/docs/configuration/client#options-parameters) parameter can be used to enable or disable specific configurations on Nomad clients, unique to your use case requirements.
+
+### ACL configuration
+
+The [Access Control](https://learn.hashicorp.com/collections/nomad/access-control) guide provides instructions on configuring and enabling ACLs.
+
+### TLS configuration
+
+Securing Nomad's cluster communication with mutual TLS (mTLS) is recommended for production deployments and can even ease operations by preventing mistakes and misconfigurations. Nomad clients and servers should not be publicly accessible without mTLS enabled.
+
+The [Securing Nomad with TLS](https://learn.hashicorp.com/nomad/transport-security/enable-tls) guide provides instructions on configuring and enabling TLS.
+
+## Start Nomad
+
+Enable and start Nomad using the systemctl command responsible for controlling systemd managed services. Check the status of the nomad service using systemctl.
+
+```text
+sudo systemctl enable nomad
+sudo systemctl start nomad
+sudo systemctl status nomad
+```
+
+## Next Steps
+
+- Read [Outage Recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage) to learn
+  the steps required to recover from a Nomad cluster outage.
+- Read [Autopilot](https://learn.hashicorp.com/nomad/operating-nomad/autopilot) to learn about
+  features in Nomad 0.8 to allow for automatic operator-friendly
+  management of Nomad servers.
diff --git a/content/nomad/v0.12.x/content/docs/install/production/index.mdx b/content/nomad/v0.12.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..3912ba9d6a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/production/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+sidebar_title: Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+This section covers how to install Nomad for production.
+
+There are multiple steps to cover for a successful Nomad deployment:
+
+## Installing Nomad
+
+This page lists the two primary methods to installing Nomad and how to verify a successful installation.
+
+Please refer to [Installing Nomad](/docs/install) sub-section.
+
+## Hardware Requirements
+
+This page details the recommended machine resources (instances), port requirements, and network topology for Nomad.
+
+Please refer to [Hardware Requirements](/docs/install/production/requirements) sub-section.
+
+## Setting Nodes with Nomad Agent
+These pages explain the Nomad agent process and how to set the server and client nodes in the cluster.
+
+Please refer to [Set Server & Client Nodes](/docs/install/production/nomad-agent) and [Nomad Agent documentation](/docs/commands/agent) pages.
+
+## Reference Architecture
+
+This document provides recommended practices and a reference architecture for HashiCorp Nomad production deployments. This reference architecture conveys a general architecture that should be adapted to accommodate the specific needs of each implementation.
+
+Please refer to [Reference Architecture](/docs/install/production/reference-architecture) sub-section.
+
+## Install Guide Based on Reference Architecture
+This guide provides an end-to-end walkthrough of the steps required to install a single production-ready Nomad cluster as defined in the Reference Architecture section.
+
+Please refer to [Reference Install Guide](/docs/install/production/deployment-guide) sub-section.
diff --git a/content/nomad/v0.12.x/content/docs/install/production/nomad-agent.mdx b/content/nomad/v0.12.x/content/docs/install/production/nomad-agent.mdx
new file mode 100644
index 0000000000..b97f40ce44
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/production/nomad-agent.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Nomad Agent
+sidebar_title: Set Server & Client Nodes
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Setting Nodes with Nomad Agent
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/docs/internals/consensus) and [gossip protocol](/docs/internals/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default,
+any signal to an agent (interrupt, terminate, kill) will cause the agent
+to forcefully stop. Graceful termination can be configured by either
+setting `leave_on_interrupt` or `leave_on_terminate` to respond to the
+respective signals.
+
+When gracefully exiting, clients will update their status to terminal on
+the servers so that tasks can be migrated to healthy agents. Servers
+will notify their intention to leave the cluster which allows them to
+leave the [consensus](/docs/internals/consensus) peer set.
+
+It is especially important that a server node be allowed to leave gracefully
+so that there will be a minimal impact on availability as the server leaves
+the consensus peer set. If a server does not gracefully leave, and will not
+return into service, the [`server force-leave` command](/docs/commands/server/force-leave)
+should be used to eject it from the consensus peer set.
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/docs/internals/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers should be run with the lowest possible permissions. Nomad clients
+must be run as root due to the OS isolation mechanisms that require root
+privileges. In all cases, it is recommended you create a `nomad` user with the
+minimal set of required privileges.
diff --git a/content/nomad/v0.12.x/content/docs/install/production/reference-architecture.mdx b/content/nomad/v0.12.x/content/docs/install/production/reference-architecture.mdx
new file mode 100644
index 0000000000..ea7d1f7f37
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/production/reference-architecture.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: Nomad Reference Architecture
+sidebar_title: Reference Architecture
+description: |-
+  This document provides recommended practices and a reference
+  architecture for HashiCorp Nomad production deployments.
+ea_version: 0.9
+---
+
+# Nomad Reference Architecture
+
+This document provides recommended practices and a reference architecture for HashiCorp Nomad production deployments. This reference architecture conveys a general architecture that should be adapted to accommodate the specific needs of each implementation.
+
+The following topics are addressed:
+
+- [Reference Architecture](#ra)
+- [Deployment Topology within a Single Region](#one-region)
+- [Deployment Topology across Multiple Regions](#multi-region)
+- [Network Connectivity Details](#net)
+- [Deployment System Requirements](#system-reqs)
+- [High Availability](#high-availability)
+- [Failure Scenarios](#failure-scenarios)
+
+This document describes deploying a Nomad cluster in combination with, or with access to, a [Consul cluster](/docs/integrations/consul-integration). We recommend the use of Consul with Nomad to provide automatic clustering, service discovery, health checking and dynamic configuration.
+
+## Reference Architecture ((#ra))
+
+A Nomad cluster typically comprises three or five servers (but no more than seven) and a number of client agents. Nomad differs slightly from Consul in that it divides infrastructure into regions which are served by one Nomad server cluster, but can manage multiple datacenters or availability zones. For example, a _US Region_ can include datacenters _us-east-1_ and _us-west-2_.
+
+In a Nomad multi-region architecture, communication happens via [WAN gossip](/docs/internals/gossip). Additionally, Nomad can integrate easily with Consul to provide features such as automatic clustering, service discovery, and dynamic configurations. Thus we recommend you use Consul in your Nomad deployment to simplify the deployment.
+
+In cloud environments, a single cluster may be deployed across multiple availability zones. For example, in AWS each Nomad server can be deployed to an associated EC2 instance, and those EC2 instances distributed across multiple AZs. Similarly, Nomad server clusters can be deployed to multiple cloud regions to allow for region level HA scenarios.
+
+For more information on Nomad server cluster design, see the [cluster requirements documentation](/docs/install/production/requirements).
+
+The design shared in this document is the recommended architecture for production environments, as it provides flexibility and resilience. Nomad utilizes an existing Consul server cluster; however, the deployment design of the Consul server cluster is outside the scope of this document.
+
+Nomad to Consul connectivity is over HTTP and should be secured with TLS as well as a Consul token to provide encryption of all traffic. This is done using Nomad's [Automatic Clustering with Consul](https://learn.hashicorp.com/nomad/operating-nomad/clustering).
+
+### Deployment Topology within a Single Region ((#one-region))
+
+A single Nomad cluster is recommended for applications deployed in the same region.
+
+Each cluster is expected to have either three or five servers. This strikes a balance between availability in the case of failure and performance, as [Raft](https://raft.github.io/) consensus gets progressively slower as more servers are added.
+
+The time taken by a new server to join an existing large cluster may increase as the size of the cluster increases.
+
+#### Reference Diagram
+
+![Reference diagram](/img/nomad_reference_diagram.png)
+
+### Deployment Topology across Multiple Regions ((#multi-region))
+
+By deploying Nomad server clusters in multiple regions, the user is able to interact with the Nomad servers by targeting any region from any Nomad server even if that server resides in a separate region. However, most data is not replicated between regions as they are fully independent clusters. The exceptions are [ACL tokens and policies][acl], as well as [Sentinel policies in Nomad Enterprise][sentinel], which _are_ replicated between regions.
+
+Nomad server clusters in different datacenters can be federated using WAN links. The server clusters can be joined to communicate over the WAN on port `4648`. This same port is used for single datacenter deployments over LAN as well.
+
+Additional documentation is available to learn more about [Nomad server federation](https://learn.hashicorp.com/nomad/operating-nomad/federation).
+
+## Network Connectivity Details ((#net))
+
+![Nomad network diagram](/img/nomad_network_arch.png)
+
+Nomad servers are expected to be able to communicate in high bandwidth, low latency network environments and have below 10 millisecond latencies between cluster members. Nomad servers can be spread across cloud regions or datacenters if they satisfy these latency requirements.
+
+Nomad client clusters require the ability to receive traffic as noted above in the Network Connectivity Details; however, clients can be separated into any type of infrastructure (multi-cloud, on-prem, virtual, bare metal, etc.) as long as they are reachable and can receive job requests from the Nomad servers.
+
+Additional documentation is available to learn more about [Nomad networking](/docs/install/production/requirements#network-topology).
+
+## Deployment System Requirements ((#system-reqs))
+
+Nomad server agents are responsible for maintaining the cluster state, responding to RPC queries (read operations), and for processing all write operations. Given that Nomad server agents do most of the heavy lifting, server sizing is critical for the overall performance efficiency and health of the Nomad cluster.
+
+### Nomad Servers
+
+| Size  | CPU      | Memory       | Disk   | Typical Cloud Instance Types              |
+| ----- | -------- | ------------ | ------ | ----------------------------------------- |
+| Small | 2 core   | 8-16 GB RAM  | 50 GB  | **AWS:** m5.large, m5.xlarge              |
+|       |          |              |        | **Azure:** Standard_D2_v3, Standard_D4_v3 |
+|       |          |              |        | **GCE:** n1-standard-8, n1-standard-16    |
+| Large | 4-8 core | 32-64 GB RAM | 100 GB | **AWS:** m5.2xlarge, m5.2xlarge           |
+|       |          |              |        | **Azure:** Standard_D4_v3, Standard_D8_v3 |
+|       |          |              |        | **GCE:** n1-standard-16, n1-standard-32   |
+
+#### Hardware Sizing Considerations
+
+- The small size would be appropriate for most initial production
+  deployments, or for development/testing environments.
+
+- The large size is for production environments where there is a
+  consistently high workload.
+
+~> **NOTE** For large workloads, ensure that the disks support a high number of IOPS to keep up with the rapid Raft log update rate.
+
+Nomad clients can be setup with specialized workloads as well. For example, if workloads require GPU processing, a Nomad datacenter can be created to serve those GPU specific jobs and joined to a Nomad server cluster. For more information on specialized workloads, see the documentation on [job constraints](/docs/job-specification/constraint) to target specific client nodes.
+
+## High Availability
+
+A Nomad server cluster is the highly-available unit of deployment within a single datacenter. A recommended approach is to deploy a three or five node Nomad server cluster. With this configuration, during a Nomad server outage, failover is handled immediately without human intervention.
+
+When setting up high availability across regions, multiple Nomad server clusters are deployed and connected via WAN gossip. Nomad clusters in regions are fully independent from each other and do not share jobs, clients, or state. Data residing in a single region-specific cluster is not replicated to other clusters in other regions.
+
+## Failure Scenarios
+
+Typical distribution in a cloud environment is to spread Nomad server nodes into separate Availability Zones (AZs) within a high bandwidth, low latency network, such as an AWS Region. The diagram below shows Nomad servers deployed in multiple AZs promoting a single voting member per AZ and providing both AZ-level and node-level failure protection.
+
+![Nomad fault tolerance](/img/nomad_fault_tolerance.png)
+
+Additional documentation is available to learn more about [cluster sizing and failure tolerances](/docs/internals/consensus#deployment-table) as well as [outage recovery](https://learn.hashicorp.com/nomad/operating-nomad/outage).
+
+### Availability Zone Failure
+
+In the event of a single AZ failure, only a single Nomad server will be affected which would not impact job scheduling as long as there is still a Raft quorum (i.e. 2 available servers in a 3 server cluster, 3 available servers in a 5 server cluster, etc.). There are two scenarios that could occur should an AZ fail in a multiple AZ setup: leader loss or follower loss.
+
+#### Leader Server Loss
+
+If the AZ containing the Nomad leader server fails, the remaining quorum members would elect a new leader. The new leader then begins to accept new log entries and replicates these entries to the remaining followers.
+
+#### Follower Server Loss
+
+If the AZ containing a Nomad follower server fails, there is no immediate impact to the Nomad leader server or cluster operations. However, there still must be a Raft quorum in order to properly manage a future failure of the Nomad leader server.
+
+### Region Failure
+
+In the event of a region-level failure (which would contain an entire Nomad server cluster), clients will still be able to submit jobs to another region that is properly federated. However, there will likely be data loss as Nomad server clusters do not replicate their data to other region clusters. See [Multi-region Federation](https://learn.hashicorp.com/nomad/operating-nomad/federation) for more setup information.
+
+## Next Steps
+
+- Read [Deployment Guide](/docs/install/production/deployment-guide) to learn
+  the steps required to install and configure a single HashiCorp Nomad cluster.
+
+[acl]: https://learn.hashicorp.com/nomad?track=acls#operations-and-development
+[sentinel]: https://learn.hashicorp.com/nomad/governance-and-policy/sentinel
diff --git a/content/nomad/v0.12.x/content/docs/install/production/requirements.mdx b/content/nomad/v0.12.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..da6eeb7ac5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: Hardware Requirements
+sidebar_title: Hardware Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Hardware Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
diff --git a/content/nomad/v0.12.x/content/docs/install/quickstart/index.mdx b/content/nomad/v0.12.x/content/docs/install/quickstart/index.mdx
new file mode 100644
index 0000000000..ea30f4dfeb
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/quickstart/index.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+sidebar_title: Quickstart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to our [Production Installation](/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via the Katacoda interactive learning platform.
+
+- [Introduction to Nomad](https://www.katacoda.com/hashicorp/scenarios/nomad-introduction)
+
+- [Nomad Playground](https://katacoda.com/hashicorp/scenarios/playground)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](https://www.vagrantup.com/docs/installation/). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which will start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This will take a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[installing-binary]: /docs/install
+[vagrant-environment]: https://learn.hashicorp.com/nomad/getting-started/install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v0.12.x/content/docs/install/windows-service.mdx b/content/nomad/v0.12.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..dba9e7bd9e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+sidebar_title: Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /downloads
+[logging]: /docs/configuration#log_file
diff --git a/content/nomad/v0.12.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v0.12.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..38cdb4c9a4
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,339 @@
+---
+layout: docs
+page_title: Consul Connect
+sidebar_title: Consul Connect
+description: >-
+  Learn how to use Nomad with Consul Connect to enable secure service to service
+  communication
+---
+
+# Consul Connect
+
+~> **Note:** This guide requires Nomad 0.10.0 or later and Consul 1.6.0 or
+later.
+
+~> **Note:** Nomad's Connect integration requires Linux network namespaces.
+Nomad Connect will not run on Windows or macOS.
+
+[Consul Connect](https://www.consul.io/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of Connect at all.
+
+# Nomad with Consul Connect Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. In order to support Consul Connect, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into Connect integration. When Connect is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul Connect integration to
+implement [service segmentation](https://www.consul.io/segmentation.html) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in Connect continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul Connect integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/nomad/consul-integration/nomad-connect-acl)
+guide.
+
+# Nomad Consul Connect Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+Connect integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+**Note**: Nomad's Connect integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use Connect on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Connect.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul Connect sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+$ curl -L -o cni-plugins.tgz https://github.com/containernetworking/plugins/releases/download/v0.8.6/cni-plugins-linux-amd64-v0.8.6.tgz
+$ sudo mkdir -p /opt/cni/bin
+$ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Connect-enabled Services
+
+Once Nomad and Consul are running, submit the following Connect-enabled services
+to Nomad by copying the HCL into a file named `connect.nomad` and running:
+`nomad run connect.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v1"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v1"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul Connect, it does not define
+any ports in its network. The service stanza enables Connect:
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service stanza is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace.
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul Connect:
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` stanza defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Changes to the `connect` stanza may not properly trigger a job update
+  ([#6459][gh6459]). Changing a `meta` variable is the suggested workaround as
+  this will always cause an update to occur.
+- Consul Connect using network namespaces is only supported on Linux.
+
+[count-dashboard]: /img/count-dashboard.png
+[gh6120]: https://github.com/hashicorp/nomad/issues/6120
+[gh6701]: https://github.com/hashicorp/nomad/issues/6701
+[gh6459]: https://github.com/hashicorp/nomad/issues/6459
diff --git a/content/nomad/v0.12.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v0.12.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..fa95528fa5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Consul Integration
+sidebar_title: Consul
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](https://learn.hashicorp.com/nomad/operating-nomad/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` stanza](/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template stanza and how it leverages Consul Template,
+please see the [`template` job specification documentation](/docs/job-specification/template).
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/integrations/index.mdx b/content/nomad/v0.12.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..5778b3e468
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/integrations/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+sidebar_title: Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v0.12.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v0.12.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..96ab4e67f5
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,471 @@
+---
+layout: docs
+page_title: Vault Integration
+sidebar_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](https://www.vaultproject.io/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both white-list and blacklist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a whitelist by using `allowed_policies` in the token
+role definition or as a blacklist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the blacklist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The token can then be set in the server configuration's
+[`vault` stanza][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` stanza of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To Submit this job a token that has the `access-kv` policy in the Namespace `engineering`
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -oprhan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: https://www.vaultproject.io/docs/auth/token 'Vault Authentication Backend'
+[config]: /docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: https://www.vaultproject.io/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: https://www.vaultproject.io/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v0.12.x/content/docs/internals/architecture.mdx b/content/nomad/v0.12.x/content/docs/internals/architecture.mdx
new file mode 100644
index 0000000000..18919474bd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/architecture.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: Architecture
+sidebar_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+- **Job** - A Job is a specification provided by users that declares a workload for
+  Nomad. A Job is a form of _desired state_; the user is expressing that the job should
+  be running, but not where it should be run. The responsibility of Nomad is to make sure
+  the _actual state_ matches the user desired state. A Job is composed of one or more
+  task groups.
+
+- **Task Group** - A Task Group is a set of tasks that must be run together. For example, a
+  web server may require that a log shipping co-process is always running as well. A task
+  group is the unit of scheduling, meaning the entire group must run on the same client node and
+  cannot be split.
+
+- **Driver** – A Driver represents the basic means of executing your **Tasks**.
+  Example Drivers include Docker, Qemu, Java, and static binaries.
+
+- **Task** - A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+  which allow Nomad to be flexible in the types of tasks it supports. Tasks
+  specify their driver, configuration for the driver, constraints, and resources required.
+
+- **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the
+  Nomad agent. The agent is responsible for registering with the servers, watching for any
+  work to be assigned and executing tasks. The Nomad agent is a long lived process which
+  interfaces with the servers.
+
+- **Allocation** - An Allocation is a mapping between a task group in a job and a client
+  node. A single job may have hundreds or thousands of task groups, meaning an equivalent
+  number of allocations must exist to map the work to client machines. Allocations are created
+  by the Nomad servers as part of scheduling decisions made during an evaluation.
+
+- **Evaluation** - Evaluations are the mechanism by which Nomad makes scheduling decisions.
+  When either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad creates
+  a new evaluation to determine if any actions must be taken. An evaluation may result
+  in changes to allocations if necessary.
+
+- **Server** - Nomad servers are the brains of the cluster. There is a cluster of servers
+  per region and they manage all jobs and clients, run evaluations, and create task allocations.
+  The servers replicate data between each other and perform leader election to ensure high
+  availability. Servers federate across regions to make Nomad globally aware.
+
+- **Regions and Datacenters** - Nomad models infrastructure as regions and
+  datacenters. Regions may contain multiple datacenters. Servers are assigned to
+  a specific region, managing state and making scheduling decisions within that
+  region. Multiple regions can be federated together. For example, you may
+  have a `US` region with the `us-east-1` and `us-west-1` datacenters,
+  connected to the `EU` region with the `eu-fr-1` and `eu-uk-1` datacenters.
+  Requests that are made between regions are forwarded to the appropriate servers.
+  Data is _not_ replicated between regions.
+
+- **Bin Packing** - Bin Packing is the process of filling bins with items in a way that
+  maximizes the utilization of bins. This extends to Nomad, where the clients are "bins"
+  and the items are task groups. Nomad optimizes resources by efficiently bin packing
+  tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/docs/internals/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/docs/internals/consensus),
+[gossip protocol](/docs/internals/gossip), and [scheduler design](/docs/internals/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v0.12.x/content/docs/internals/consensus.mdx b/content/nomad/v0.12.x/content/docs/internals/consensus.mdx
new file mode 100644
index 0000000000..280729ab05
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/consensus.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Consensus Protocol
+sidebar_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v0.12.x/content/docs/internals/gossip.mdx b/content/nomad/v0.12.x/content/docs/internals/gossip.mdx
new file mode 100644
index 0000000000..400e0c6629
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/gossip.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Gossip Protocol
+sidebar_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/internals/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/docs/internals/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v0.12.x/content/docs/internals/index.mdx b/content/nomad/v0.12.x/content/docs/internals/index.mdx
new file mode 100644
index 0000000000..d9c0711f9c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Internals
+sidebar_title: Internals
+description: >-
+  This section covers the internals of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Internals
+
+This section covers the internals of Nomad and explains the technical
+details of how Nomad functions, its architecture, and sub-systems.
+
+-> **Note:** Knowledge of Nomad internals is not
+required to use Nomad. If you aren't interested in the internals
+of Nomad, you may safely skip this section. If you are operating Nomad,
+we recommend understanding the internals.
diff --git a/content/nomad/v0.12.x/content/docs/internals/plugins/base.mdx b/content/nomad/v0.12.x/content/docs/internals/plugins/base.mdx
new file mode 100644
index 0000000000..8a71735125
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/plugins/base.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Base Plugin
+sidebar_title: Base
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /docs/configuration/plugin
diff --git a/content/nomad/v0.12.x/content/docs/internals/plugins/csi.mdx b/content/nomad/v0.12.x/content/docs/internals/plugins/csi.mdx
new file mode 100644
index 0000000000..4ca4513416
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/plugins/csi.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: Storage Plugins
+sidebar_title: Storage
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the
+industry-standard Container Storage Interface specification unifies
+these APIs in a way that's agnostic to both the storage vendor and the
+container orchestrator. Each storage provider can build its own CSI
+plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
+(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
+Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given
+Nomad client node. A list of available CSI plugins can be found in the
+[Kubernetes CSI documentation][csi-drivers-list]. Any of these plugins
+should work with Nomad out of the box.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+You should always run node plugins as Nomad `system` jobs and use the
+`-ignore-system` flag on the `nomad node drain` command to ensure that the
+node plugins are still running while the node is being drained. Use
+constraints for the node plugin jobs based on the availability of volumes. For
+example, AWS EBS volumes are specific to particular availability zones with a
+region. Controller plugins can be run as `service` jobs.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to the Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes terminal. The
+client will send an "unpublish" RPC to the server, which will send "detach"
+RPCs to the node plugin.  The node plugin unmounts the bind-mount from the
+allocation and unmounts the volume from the plugin (if it's not in use by
+another task). The server will then send "unpublish" RPCs to the controller
+plugin (if any), and decrement the claim count for the volume. At this point
+the volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.12.x/content/docs/internals/plugins/devices.mdx b/content/nomad/v0.12.x/content/docs/internals/plugins/devices.mdx
new file mode 100644
index 0000000000..01829331bb
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/plugins/devices.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Devices
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad/tree/master/devices/gpu/nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/docs/internals/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /docs/internals/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v0.12.x/content/docs/internals/plugins/index.mdx b/content/nomad/v0.12.x/content/docs/internals/plugins/index.mdx
new file mode 100644
index 0000000000..d9bb9ae245
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/plugins/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Plugins
+sidebar_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/docs/internals/plugins/task-drivers)
+- [Devices](/docs/internals/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v0.12.x/content/docs/internals/plugins/task-drivers.mdx b/content/nomad/v0.12.x/content/docs/internals/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..50bf958775
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/plugins/task-drivers.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+sidebar_title: Task Drivers
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+Capabilities {
+    // Does the driver support sending OS signals to the task? This capability
+    // is used by 'nomad alloc signal'.
+    SendSignals: true,
+
+    // Does the driver support executing a command within the task execution
+    // environment? This capability is used by 'nomad alloc exec'.
+    Exec:        true,
+
+    // What filesystem isolation is supported by the driver. Options include
+    // FSIsolationImage, FSIsolationChroot, and FSIsolationNone. See below for
+    // more details.
+    FSIsolation: FSIsolationImage,
+
+    // NetIsolationModes lists the set of isolation modes supported by the
+    // driver.  Options include NetIsolationModeHost, NetIsolationModeGroup,
+    // NetIsolationModeTask, and NetIsolationModeNone. See below for more
+    // details.
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are
+    // implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver
+    // supports. This is used to check whether mounting host volumes or CSI
+    // volumes is allowed. Options include MountConfigSupportAll (default), or
+    // MountConfigSupportNone.
+    MountConfigs MountConfigSupport
+}
+```
+
+The file system isolation options are:
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using thre host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /docs/internals/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
diff --git a/content/nomad/v0.12.x/content/docs/internals/scheduling/index.mdx b/content/nomad/v0.12.x/content/docs/internals/scheduling/index.mdx
new file mode 100644
index 0000000000..76e2deaf0d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/docs/internals/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/docs/internals/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v0.12.x/content/docs/internals/scheduling/preemption.mdx b/content/nomad/v0.12.x/content/docs/internals/scheduling/preemption.mdx
new file mode 100644
index 0000000000..150174d88a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/scheduling/preemption.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Preemption
+sidebar_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v0.12.x/content/docs/internals/scheduling/scheduling.mdx b/content/nomad/v0.12.x/content/docs/internals/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..0283aade26
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/scheduling/scheduling.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Internals
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, a `system` scheduler
+that is used to run jobs on every node, and a `core` scheduler which is used
+for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v0.12.x/content/docs/internals/security.mdx b/content/nomad/v0.12.x/content/docs/internals/security.mdx
new file mode 100644
index 0000000000..e63e902928
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/internals/security.mdx
@@ -0,0 +1,326 @@
+---
+layout: docs
+page_title: Security Model
+sidebar_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](https://www.consul.io/docs/internals/security.html), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+* **[mTLS](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)** -
+    Mutual authentication of both the TLS server and client x509 certificates
+    prevents internal abuse by preventing unauthenticated access to network
+    components within the cluster.
+
+* **[ACLs](https://learn.hashicorp.com/collections/nomad/access-control)** - Enables
+    authorization for authenticated connections by granting capabilities to ACL
+    tokens.
+
+* **[Namespaces](/docs/enterprise/index.html#namespaces)**
+    (**Enterprise Only**) - Access to read and write to a Namepsace can be
+    controlled to allow for granular access to job information managed within a
+    multi-tenant cluster.
+
+* **[Sentinel Policies](/docs/enterprise/index.html#sentinel-policies)**
+    (**Enterprise Only**) - Sentinel policies allow for granular control over
+    components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](https://www.vaultproject.io/docs/secrets/nomad/index.html). This is
+described further with getting started steps using a development server
+[here](https://learn.hashicorp.com/collections/nomad/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+* **System Administrator** - This is someone who has access to the underlying
+    infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+    directly into a server within a cluster through a bastion host. Ultimately
+    they have read, write and execute permissions for the actual Nomad binary.
+    This binary is the same for server and client nodes using different
+    configuration files. These users potentially have something like sudo,
+    administrative, or some other super-user access to the underlying compute
+    resource. Users like these are essentially totally trusted by Nomad as they
+    have administrative rights to the system and can start or stop the agent.
+
+* **Nomad Administrator** - This is someone (probably the same **System
+    Administrator**) who has access to define the Nomad agent configurations
+    for servers and clients, and/or have a Nomad management ACL token. They also
+    have total rights to all of the parts in the Nomad system including the
+    ability to start and stop all jobs within a cluster.
+
+* **Nomad Operator** - This is someone who likely has selective access with
+    restricted capabilities to manage jobs applicable to their namespace within
+    a cluster.
+
+* **User** - This is someone who is a user of an application being run on the
+    system. In some cases applications may be public facing and exposed to the
+    internet such as a web server. This is someone who shouldn't have any
+    network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+* **[mTLS enabled](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)**
+    - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/docs/configuration/tls.html#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+* **[ACLs enabled](https://learn.hashicorp.com/collections/nomad/access-control)** - The
+    access control list (ACL) system provides a capability-based control
+    mechanism for Nomad administrators allowing for custom roles (typically
+    within Vault) to be tied to an individual human or machine operator
+    identity. This allows for access to capabilities within the cluster to be
+    restricted to specific users.
+
+* **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+    (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+    a feature which enables
+    [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code/)
+    to enforce further restrictions on operators. This is used to augment the
+    built-in ACL system for fine-grained control over jobs.
+
+* **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+    (**Enterprise Only**) - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+* **[Resource Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas)**
+    (**Enterprise Only**) - Can limit a namespace's access to the underlying
+    compute resources in the cluster by setting upper-limits for operators.
+    Access to these resource quotas can be managed via ACLs to ensure read-only
+    access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+* **Rotate credentials** - Using short-lived credentials or rotating them
+    frequently is highly recommended to reduce damage of accidentally leaked
+    credentials.
+
+    * Use [Vault](/docs/vault-integration/index.html) to create and manage
+      dynamic, rotated credentials prevent secrets from being easily exposed
+      within the [job specification](/docs/job-specification/index.html) itself
+      which may be leaked into version control or otherwise be accidentally stored
+      on disk on an operator's local machine.
+
+    * Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+      PKI secret engine](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad) to
+      automatically generate and renew dynamic, unique X.509 certificates for each
+      Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+* **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+    Nomad servers can be run as unprivileged users that only require access to
+    the data directory.
+
+* **Containers with Sandbox Runtimes** - In some situations, such as running
+    untrusted code as a service, it may be worth considering using different
+    container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+    Containers](https://katacontainers.io/). These types of runtimes provide
+    sandboxing features which help prevent raw access to the underlying shared
+    kernel for other containers and the Nomad client agent itself. Docker driver
+    allows [customizing runtimes](/docs/drivers/docker#runtime).
+
+* **[Disable Unused Drivers](/docs/configuration/client#driver-blacklist)** -
+    Each driver provides different degrees of isolation, and bugs may allow
+    unintended privilege escalation. If a task driver is not needed, you can
+    disable it to reduce risk.
+
+* **Linux Security Modules** - Use of security modules that can be directly
+    integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+    both the Nomad hosts and applied to containers for an extra layer of
+    security. Seccomp profiles are able to be passed directly to containers
+    using the
+    **[`security_opt`](/docs/drivers/docker.html#security_opt)**
+    parameter available in the default [Docker
+    driver](/docs/drivers/docker.html).
+
+* **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+    Integrating service mesh technologies such as
+    **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+    and efficiently load balancing network connectivity within a cluster.
+
+* **[TLS Settings](/docs/configuration/tls)** -
+    TLS settings, such as the available [cipher suites](/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+* **[HTTP Headers](/docs/configuration#http_api_response_headers)** -
+    Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/docs/configuration#http_api_response_headers) for HTTP API responses. 
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+* **Nomad agent-to-agent communication** - Transport encryption for
+    agent-to-agent communication is required to prevent eavesdropping. TCP and
+    UDP based protocols within Nomad provide different mechanisms for enabling
+    encryption including symmetric (shared gossip encryption keys) and
+    asymmetric keys (TLS).
+
+* **Tampering of data in transit** - Any tampering should be detectable via mTLS
+    and cause Nomad to avoid processing the request.
+
+* **Access to data without authentication or authorization** - Requests to the
+    server should be authenticated and authorized using mTLS and ACLs
+    respectively.
+
+* **State modification or corruption due to malicious messages** - Improperly
+    formatted messages are discarded while properly formatted messages require
+    authentication and authorization.
+
+* **Non-server members accessing raw data** - All servers that join the cluster
+    require proper authentication and authorization in order to begin
+    participating in Raft. All data in Raft should be encrypted with TLS.
+
+* **Denial of Service against a node** - DoS attacks against a single node
+    should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+* **Access (read or write) to the Nomad data directory** - Information about the
+    jobs managed by Nomad is persisted to a server's data directory.
+
+* **Access (read or write) to the Nomad configuration directory** - Access to
+    Nomad's configuration file(s) directory can enable and disable features for
+    a cluster.
+
+* **Memory access to a running Nomad server agent** - Direct access to the
+    memory of the Nomad server agent process (usually requiring a shell on the
+    system through various means) results in almost all aspects of the agent
+    being compromised including access to certificates and other secrets.
+
+The following are not part of the threat model for client agents:
+
+* **Access (read or write) to the Nomad data directory** - Information about the
+    allocations scheduled to a Nomad client is persisted to its data directory.
+    This would include any secrets in any of the allocation's file systems.
+
+* **Access (read or write) to the Nomad configuration directory** - Access to a
+    client's configuration file can enable and disable features for a client
+    including insecure drivers such as
+    [`raw_exec`](/docs/drivers/raw_exec.html).
+
+* **Memory access to a running Nomad client agent** - Direct access to the
+    memory of the Nomad client agent process allows an attack to extract secrets
+    from clients such as Vault tokens.
+
+* **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+    e.g. filesystem access to configuration directories, or raw accesses to host
+    devices. Such privileges can be used to facilitate compromise other workloads,
+    or cause denial-of-service attacks.
+
+#### Internal Threats
+
+* **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+    threat to your cluster in certain situations, especially in multi-team
+    cluster deployments. They may accidentally or intentionally use a malicious
+    job to harm a cluster which can help be protected against using
+    Quotas, Namespace, and Sentinel policies.
+
+* **Workload** - Workloads may have host network access within a cluster which
+    can lead to SSRF due to application security issues outside of the scope of
+    Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+    and Sentinel policies together can add layers of protection against
+    malicious workloads.
+
+* **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+    clusters to abuse within the cluster from malicious workloads.
+
+* **Client driver** - Drivers implement various workload types for a cluster,
+    and the backend configuration of these drivers should be considered to
+    implement defense in depth. For example, a custom Docker driver that limits
+    the ability to mount the host file system may be subverted by network access
+    to an exposed Docker daemon API through other means such as the [`raw_exec`](/docs/drivers/raw_exec.html)
+    driver.
+
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+* **Server agent** - Internal cluster leader elections and replication is
+    managed via Raft between server agents encrypted in transit. However,
+    information about the server is stored unencrypted at rest in the agent's
+    data directory. This may contain sensitive information such as ACL tokens
+    and TLS certificates.
+
+* **Client agent** - Client-to-server communication within a cluster is
+    encrypted and authenticated using mTLS. Information about the allocations on
+    a client node is unencrypted in the agent's data and configuration
+    directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description |
+|----------------------|---------|-------------|
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](https://learn.hashicorp.com/collections/nomad/web-ui) and [API](/api-docs) access to agents. |
+| **4647** / TCP       | Servers | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents. |
+| **4648** / TCP + UDP | Servers | [gossip](/docs/internals/gossip.html) protocol to manage server membership using [Serf](https://www.serf.io/). |
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/affinity.mdx b/content/nomad/v0.12.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..b6a7cf447f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: affinity Stanza - Job Specification
+sidebar_title: affinity
+description: |-
+  The "affinity" stanza allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Stanza
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity']
+  ]}
+/>
+
+The `affinity` stanza allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 5
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task stanzas as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` stanzas. Remember that the
+`affinity` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` stanza matches the node.
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/artifact.mdx b/content/nomad/v0.12.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..9338e935d2
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: artifact Stanza - Job Specification
+sidebar_title: artifact
+description: |-
+  The "artifact" stanza instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Stanza
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` stanza instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to download
+  the artifact, relative to the root of the task's directory. If omitted, the
+  default value is to place the artifact in `local/`. The destination is treated
+  as a directory unless `mode` is set to `file`. Source files will be downloaded
+  into that directory path.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` stanzas. Remember that the
+`artifact` stanza is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the task's directory.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/example/nomad-examples"
+  destination = "local/repo"
+}
+```
+
+To download from private repo, sshkey needs to be set. The key must be
+base64-encoded string. Run `base64 -w0 <file>`
+
+```hcl
+artifact {
+  source      = "git@github.com:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    sshkey = "<string>"
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v0.12.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..5b884f1cc1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: check_restart Stanza - Job Specification
+sidebar_title: check_restart
+description: |-
+  The "check_restart" stanza instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart']
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` stanza instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` stanza, it is
+restarted according to the task group's [`restart` policy][restart_stanza]. The
+`check_restart` settings apply to [`check`s][check_stanza], but may also be
+placed on [`service`s][service_stanza] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the stanzas are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_stanza] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` stanza][restart_stanza] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` stanza][restart_stanza] for
+details.
+
+[check_stanza]: /docs/job-specification/service#check-parameters 'check stanza'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[service_stanza]: /docs/job-specification/service 'service stanza'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/connect.mdx b/content/nomad/v0.12.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..d4869f140e
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,203 @@
+---
+layout: docs
+page_title: connect Stanza - Job Specification
+sidebar_title: connect
+description: The "connect" stanza allows specifying options for Consul Connect integration
+---
+
+# `connect` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` stanza allows configuring various options for
+[Consul Connect](/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/nomad/consul-integration/nomad-connect-acl)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](https://www.consul.io/docs/connect/native) applications. If set,
+  the service definition must provide the name of the implementing task in the
+  [task][service_task] field.
+  Incompatible with `sidecar_service` and `sidecar_task`.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to configure the sidecar
+  service injected by Nomad for Consul Connect. Incompatible with `native`.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the configuration of the Envoy
+  proxy task. Incompatible with `native`.
+
+## `connect` Examples
+
+### Using Sidecar Service
+
+The following example is a minimal connect stanza with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v2"
+      }
+    }
+  }
+}
+```
+
+### Using Connect Native
+
+The following example is a minimal service stanza for a
+[Consul Connect Native](https://www.consul.io/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Limitations
+
+[Nomad variable interpolation][interpolation] is _not_ yet supported ([gh-7221]).
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
+[native]: https://www.consul.io/docs/connect/native.html
+[service_task]: /docs/job-specification/service#task-1 'Nomad service task'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/constraint.mdx b/content/nomad/v0.12.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..6bddf52d10
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,305 @@
+---
+layout: docs
+page_title: constraint Stanza - Job Specification
+sidebar_title: constraint
+description: |-
+  The "constraint" stanza allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Stanza
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint']
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` stanzas. Remember that the
+`constraint` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v0.12.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..54d5a36b16
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: csi_plugin Stanza - Job Specification
+sidebar_title: csi_plugin <sup>Beta</sup>
+description: >-
+  The "csi_plugin" stanza allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume']} />
+
+The "csi_plugin" stanza allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows the
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <required>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad.
+
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+~> **Note:** During node drains, jobs that claim volumes must be moved before
+the `node` or `monolith` plugin for those volumes. You should run `node` or
+`monolith` plugins as [`system`][system] jobs and use the `-ignore-system`
+flag on `nomad node drain` to ensure that the plugins are running while the
+node is being drained.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:latest"
+
+        args = [
+          "node",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id        = "aws-efs0"
+        type      = "node"
+        mount_dir = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /docs/job-specification/volume
+[system]: /docs/schedulers/#system
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/device.mdx b/content/nomad/v0.12.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..2c4c6b83a6
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,304 @@
+---
+layout: docs
+page_title: device Stanza - Job Specification
+sidebar_title: device
+description: |-
+  The "device" stanza is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` stanza is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` stanza is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` stanza
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` stanza can be.
+
+~> Device supported is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports is as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` stanzas. Remember that the
+`device` stanza is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v0.12.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..15c20b5d5f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: dispatch_payload Stanza - Job Specification
+sidebar_title: dispatch_payload
+description: |-
+  The "dispatch_payload" stanza allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Stanza
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` stanza is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` stanza. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` stanzas. Remember that the
+`dispatch_payload` stanza is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/env.mdx b/content/nomad/v0.12.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..bff811ed19
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: env Stanza - Job Specification
+sidebar_title: env
+description: |-
+  The "env" stanza configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Stanza
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` stanza configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` stanzas. Remember that the
+`env` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+  "key" = 1.4
+  "key" = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` stanza][template-env].
+
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /docs/job-specification/template#environment-variables 'Nomad template Stanza'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v0.12.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..6645886bbb
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: ephemeral_disk Stanza - Job Specification
+sidebar_title: ephemeral_disk
+description: |-
+  The "ephemeral_disk" stanza describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Stanza
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` stanza describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = "500"
+      sticky  = true
+    }
+  }
+}
+```
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be
+  removed if an error is encountered.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` stanzas. Remember that the
+`ephemeral_disk` stanza is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/expose.mdx b/content/nomad/v0.12.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..4633f60cec
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: expose Stanza - Job Specification
+sidebar_title: expose
+description: |-
+  The "expose" stanza allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` stanza allows configuration of additional listeners for the default Envoy sidecar
+proxy managed by Nomad for [Consul Connect](/guides/integrations/consul-connect). These
+listeners create a bypass of the Connect TLS and network namespace isolation, enabling
+non-Connect enabled services to make requests to specific HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` stanza. Additional
+information about Expose Path configurations for Envoy can be found in Consul's
+[Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration.html#expose-paths-configuration-reference).
+
+Service [check](https://nomadproject.io/docs/job-specification/service/#check-parameters)
+configurations can use their [expose](/docs/job-specification/service#expose)
+parameter to automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` stanza. The example below effectively demonstrates exposing the `/health`
+endpoint similar to the example above, but using the fully flexible `expose`
+configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations](/docs/job-specification/expose/#path-1)
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside](/docs/job-specification/network#to)
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the Connect-enabled
+`count-dashboard` service, using the `HTTP` protocol. `count-dashboard` is expected
+to listen inside its namespace to port `9001`, and external services will be able to
+reach its `/metrics` endpoint by connecting to the [network interface](https://nomadproject.io/docs/configuration/client/#network_interface)
+of the node on the allocated `metrics` [Port](/docs/job-specification/network#port-parameters).
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics` endpoint
+using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health` endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service check
+definitions. For these cases the [expose](/docs/job-specification/service#expose)
+parameter in the service check stanza can be used to automatically generate the
+expose path configuration. Configuring a port for use by the check is optional,
+as a dynamic port will be automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[path]: /docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /docs/job-specification/network#port-parameters 'Nomad Port Parameters'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/gateway.mdx b/content/nomad/v0.12.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..0964083199
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,207 @@
+---
+layout: docs
+page_title: gateway Stanza - Job Specification
+sidebar_title: gateway
+description: |-
+  The "gateway" stanza allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'gateway',
+  ]}
+/>
+
+The `gateway` stanza allows configuration of [Consul Connect Gateways](https://www.consul.io/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](https://www.consul.io/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` stanza.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](https://www.consul.io/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](https://www.consul.io/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx?in=nomad/load-balancing)
+provide more suitable features.
+
+```hcl
+job "ingress-example" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      port "inbound" {
+        static = 8080
+      }
+    }
+
+    service {
+      name = "ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          proxy {
+            // Consul Gateway Proxy configuration options
+            connect_timeout = "500ms"
+          }
+
+          ingress {
+            // Consul Ingress Gateway Configuration Entry
+
+            tls {
+              enabled = false
+            }
+
+            listener {
+              port     = 8080
+              protocol = "http"
+              service {
+                name  = "web"
+                hosts = ["example.com", "example.com:8080"]
+              }
+            }
+
+            listener {
+              port = 3306
+              protocol = "tcp"
+              service {
+                name = "database"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. Either
+  `tcp` or `http`.
+
+  ~> **Note:** If using `http`, preconfiguring a [service-default] in Consul to
+  set the [Protocol](https://www.consul.io/docs/agent/config-entries/service-defaults#protocol)
+  of the service to `http` is recommended.
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests *must*
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+  ~> **Note:** If a well-known port is not used, i.e. a port other than 80 (http) or 443 (https),
+  then the port must be appended to the host to correctly match traffic. This is
+  defined in the [HTTP/1.1 RFC](https://tools.ietf.org/html/rfc2616#section-14.23).
+  If TLS is enabled, then the host **without** the port must be added to the `hosts`
+  field as well. TLS verification only matches against the hostname of the incoming
+  connection, and does not take into account the port.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+[proxy]: /docs/job-specification/gateway#proxy-parameters
+[ingress]: /docs/job-specification/gateway#ingress-parameters
+[tls]: /docs/job-specification/gateway#tlsconfig-parameters
+[listener]: /docs/job-specification/gateway#listener-parameters
+[service]: /docs/job-specification/gateway#service-parameters
+[service-default]: https://www.consul.io/docs/agent/config-entries/service-defaults
+[connect_timeout_ms]: https://www.consul.io/docs/agent/config-entries/service-resolver#connecttimeout
+[address]: /docs/job-specification/gateway#address-parameters
+[Advanced Configuration]: https://www.consul.io/docs/connect/proxies/envoy#advanced-configuration
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/group.mdx b/content/nomad/v0.12.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..6a4faa2820
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: group Stanza - Job Specification
+sidebar_title: group
+description: |-
+  The "group" stanza defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `group` stanza defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate stanzas.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart stanza documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers each service when an allocation
+  is started and de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul deregistration
+  and sending each task a shutdown signal. Ideally, services would fail
+  healthchecks once they receive a shutdown signal. Alternatively
+  `shutdown_delay` may be set to give in flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group services. In addition, tasks may have their
+  own [`shutdown_delay`](/docs/job-specification/task#shutdown_delay)
+  which waits between deregistering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration
+  after which a Nomad client that cannot communicate with the servers
+  will stop allocations based on this task group. By default, a client
+  will not stop an allocation until explicitly told to by a server. A
+  client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be
+  marked "lost" and Nomad will schedule replacement
+  allocations. However, these replaced allocations will continue to
+  run on the non-responsive client; an operator may desire that these
+  replaced allocations are also stopped in this case — for example,
+  allocations requiring exclusive access to an external resource. When
+  specified, the Nomad client will stop them after this duration. The
+  Nomad client process must be running for this to occur.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` stanzas. Remember that the
+`group` stanza is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    "my-key" = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] stanza
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other stanzas. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /docs/configuration/server#heartbeat_grace
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/index.mdx b/content/nomad/v0.12.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..54fab1f315
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Job Specification
+sidebar_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+stanza. Alternatively, you can keep reading to see a few examples.
+
+For machine-friendliness, Nomad can also read JSON-equivalent configurations. In
+general, we recommend using the HCL syntax.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        "DB_HOST" = "db01.example.com"
+        "DB_USER" = "web"
+        "DB_PASS" = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` stanza can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+stanza specified at the group level must include a [connect][] stanza, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /docs/job-specification/connect 'Connect Stanza Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/job.mdx b/content/nomad/v0.12.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..5f18e64687
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: job Stanza - Job Specification
+sidebar_title: job
+description: |-
+  The "job" stanza is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Stanza
+
+<Placement groups={['job']} />
+
+The `job` stanza is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace] (if Nomad
+Enterprise is used).
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    "my-key" = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` `([Group][group]: <required>)` - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate stanzas.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Values other than default are not allowed in non-Enterprise versions of Nomad.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system` and `batch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, rolling updates are disabled.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] stanza. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` stanzas. Remember that the
+`job` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: https://learn.hashicorp.com/nomad/governance-and-policy/namespaces
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: https://learn.hashicorp.com/nomad/operating-nomad/federation
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /docs/schedulers 'Nomad Scheduler Types'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v0.12.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..60aad0d2a8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: lifecycle Stanza - Job Specification
+sidebar_title: lifecycle
+description: |-
+  The "lifecycle" stanza configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Stanza
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` stanza is used to express task dependencies in Nomad and
+configures when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` stanza. Lifecycle task hooks
+are run in relation to the main tasks. Tasks can be run as Prestart Hooks, which
+ensures the prestart task is run before the main tasks are run.
+
+Tasks can be run with an additional parameter to indicate that they are
+sidecars, which ensures that they are running over the duration of the whole
+task group. This will allow you to run a long-lived task in a task group for a
+batch job. The absence of the sidecar flag indicates that the task is ephemeral
+and the task will not be restarted if it completes successfully. This allows you
+to run an ephemeral prestart task in a task group for a service job, which can
+serve as initialization that occurs before the main services are started.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "init" {
+      lifecycle {
+        hook    = "prestart"
+      }
+      ...
+    }
+
+    task "logging" {
+      lifecycle {
+        hook    = "prestart"
+        sidecar = true
+      }
+      ...
+    }
+
+    task "main" {
+      ...
+    }
+
+  }
+}
+```
+
+## `lifecycle` Parameters
+
+- `hook` `(string: "prestart")` - Specifies when a task should be run within
+  the lifecycle of a group. Currently only Prestart Hooks are supported.
+
+- `sidecar` `(bool: false)` - Controls whether or not a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral (`sidecar =
+  false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and it terminates, it will be
+  restarted as long as the task group is running in its allocation.
+
+[learn-taskdeps]: https://learn.hashicorp.com/nomad?track=task-deps&utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS#task-deps
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/logs.mdx b/content/nomad/v0.12.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..17d39c7356
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: logs Stanza - Job Specification
+sidebar_title: logs
+description: |-
+  The "logs" stanza configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" stanza
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Stanza
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` stanza configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` stanza allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` stanzas. Remember that the
+`logs` stanza is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /docs/commands/alloc/logs 'Nomad logs command'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/meta.mdx b/content/nomad/v0.12.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..9067713e33
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: meta Stanza - Job Specification
+sidebar_title: meta
+description: The "meta" stanza allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Stanza
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta']
+  ]}
+/>
+
+The `meta` stanza allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` stanza at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+## `meta` Parameters
+
+The "parameters" for the `meta` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings.
+
+## `meta` Examples
+
+The following examples only show the `meta` stanzas. Remember that the
+`meta` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  "key" = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/migrate.mdx b/content/nomad/v0.12.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..f82b3bf0a6
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: migrate Stanza - Job Specification
+sidebar_title: migrate
+description: |-
+  The "migrate" stanza specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Stanza
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate']
+  ]}
+/>
+
+The `migrate` stanza specifies the group's strategy for migrating off of
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+stanzas.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+stanza for allocations on that node. The `migrate` stanza is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /docs/job-specification/service#check-parameters
+[count]: /docs/job-specification/group#count
+[drain]: /docs/commands/node/drain
+[deadline]: /docs/commands/node/drain#deadline
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v0.12.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..41e6b7a064
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,272 @@
+---
+layout: docs
+page_title: multiregion Stanza - Job Specification
+sidebar_title: multiregion <sup>Beta</sup>
+description: |-
+  The "multiregion" stanza specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Stanza
+
+<Placement
+  groups={[
+    ['job', 'multiregion'],
+  ]}
+/>
+
+~> **Enterprise Only!** This functionality only exists in Nomad
+Enterprise. This is not present in the open source version of Nomad.
+
+The `multiregion` stanza specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region
+— the one specified by the `region` field or the `-region` command line
+flag to `nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` stanza. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` stanza.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+stanza has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` stanza] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` stanza (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the the
+[`update` stanza] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta stanza allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta stanza at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` stanza and the other
+stanzas it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` stanza with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: https://learn.hashicorp.com/nomad/operating-nomad/federation
+[`update` stanza]: /docs/job-specification/update
+[update-auto-revert]: /docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: https://learn.hashicorp.com/nomad?track=update-strategies#update-strategies
+[`nomad deployment unblock`]: /docs/commands/deployment/unblock
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/network.mdx b/content/nomad/v0.12.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..96162bcc19
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,300 @@
+---
+layout: docs
+page_title: network Stanza - Job Specification
+sidebar_title: network
+description: |-
+  The "network" stanza specifies the networking requirements for the task group,
+  including networking mode and port allocations. 
+---
+
+# `network` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'network'],
+  ]}
+/>
+
+The `network` stanza specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+When the `network` stanza is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][] enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+## `network` Parameters
+
+- `mbits` <code>([*deprecated*](/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+ - `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+   for the allocations. By default all DNS configuration is inherited from the client host.
+   DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. `-1` sets the mapped port equal to the
+  dynamic port allocated by the scheduler. The `NOMAD_PORT_<label>` environment variable
+  will contain the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined
+  <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+## `network` Examples
+
+The following examples only show the `network` stanzas. Remember that the
+`network` stanza is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {}
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      port_map = {
+        http = 8080
+      }
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network stanza that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+}
+```
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network stanza could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+    }
+  ]
+}
+```
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port stanzas.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+*Host networks does not currently support task based mapped ports such as the Docker driver's `port_map` configuration.
+
+
+```hcl
+network {
+  mode = "bridge"
+  
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` stanza can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v0.12.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..416e474ed8
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,155 @@
+---
+layout: docs
+page_title: parameterized Stanza - Job Specification
+sidebar_title: parameterized
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` stanza is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Stanza
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+stanza is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` stanza allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] stanza that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/periodic.mdx b/content/nomad/v0.12.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..f24deadae0
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: periodic Stanza - Job Specification
+sidebar_title: periodic
+description: |-
+  The "periodic" stanza allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Stanza
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` stanza allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+## `periodic` Examples
+
+The following examples only show the `periodic` stanzas. Remember that the
+`periodic` stanza is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is *desired:*
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be *skipped* for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be *run twice* for that day (eg November 3rd).
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/proxy.mdx b/content/nomad/v0.12.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..14368187fc
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: proxy Stanza - Job Specification
+sidebar_title: proxy
+description: |-
+  The "proxy" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Stanza
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` stanza allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int:[port][])` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration.html#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](https://www.consul.io/docs/connect/proxies/envoy.html#dynamic-configuration)
+  for details.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[port]: /docs/job-specification/network#port-parameters 'Nomad network port configuration'
+[expose]: /docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v0.12.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..ca2880c3d3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Stanza - Job Specification
+sidebar_title: reschedule
+description: >-
+  The "reschedule" stanza specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Stanza
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule']
+  ]}
+/>
+
+The `reschedule` stanza specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule stanza is present on both the job and the group, they are merged with
+the group stanza taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the task on another node if any of its allocation
+statuses become "failed". It prefers to create a replacement allocation on a node
+that hasn't previously been used.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule stanza does not apply to `system` jobs because they run on
+every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The Default Batch Reschedule Policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The Default Service Reschedule Policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/resources.mdx b/content/nomad/v0.12.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..c92b6033b1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: resources Stanza - Job Specification
+sidebar_title: resources
+description: |-
+  The "resources" stanza describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` stanza describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` stanzas. Remember that the
+`resources` stanza is only valid in the placements listed above.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] stanza
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+
+[device]: /docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/restart.mdx b/content/nomad/v0.12.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..4f28f40b6a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: restart Stanza - Job Specification
+sidebar_title: restart
+description: The "restart" stanza configures a group's behavior on task failure.
+---
+
+# `restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart']
+  ]}
+/>
+
+The `restart` stanza configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group. If present on the task, the policy is merged with
+the restart policy from the encapsulating task group.
+
+For example, assuming that the task group restart policy is: 
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+and the individual task restart policy is: 
+```hcl
+restart {
+  attempts = 5
+}
+```
+then the effective restart policy for the task will be: 
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the scheduler to delay the next restart until the next
+  `interval` is reached.
+
+- `"fail"` - Instructs the scheduler to not attempt to restart the task on
+  failure. This is the default behavior. This mode is useful for non-idempotent jobs which are unlikely to
+  succeed after a few failures. Failed jobs will be restarted according to
+  the [`reschedule`](/docs/job-specification/reschedule) stanza.
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/scaling.mdx b/content/nomad/v0.12.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1523ccea22
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: scaling Stanza - Job Specification
+sidebar_title: scaling <sup>Beta</sup>
+description: The "scaling" stanza allows specifying scaling policy for a task group
+---
+
+# `scaling` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `scaling` stanza allows configuring scaling options for a task group, for the purpose
+of supporting external autoscalers like the [Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler)
+and scaling via the Nomad UI. This stanza is not supported within jobs of type `system`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+      }
+    }
+    scaling {
+      enabled = true
+      min = 0
+      max = 10
+      policy {
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [count][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; see autoscaler documentation.
+
+[count]: /docs/job-specification/group/#count 'Nomad Task Group specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/service.mdx b/content/nomad/v0.12.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..634f3ef6c9
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,716 @@
+---
+layout: docs
+page_title: service Stanza - Job Specification
+sidebar_title: service
+description: |-
+  The "service" stanza instructs Nomad to register the task as a service using
+  the service discovery integration.
+---
+
+# `service` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service']
+  ]}
+/>
+
+The `service` stanza instructs Nomad to register a service with Consul. This
+section of the documentation will discuss the configuration, but please also
+read the [Nomad service discovery documentation][service-discovery] for more
+detailed information about the integration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and stanzas
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` stanza at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `check` <code>([Check](#check-parameters): nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, Nomad supports the
+  `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services.
+
+- `name` `(string: "<job>-<group>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${GROUP}` - the name of the group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${GROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `driver` - Advertise the port determined by the driver (eg Docker or rkt).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `port_map`.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] stanza.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](https://www.consul.io/docs/internals/anti-entropy.html#enable-tag-override)
+  for more information.
+
+- `address_mode` `(string: "auto")` - Specifies what address (host or
+  driver-specific) this service should advertise. This setting is supported in
+  Docker since Nomad 0.6 and rkt since Nomad 0.7. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker and rkt.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad Task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect Native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter.
+
+### `check` Parameters
+
+Note that health checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. Added in Nomad 0.7.1. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` stanza][check_restart_stanza].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the originating status of the
+  service. Valid options are the empty string, `passing`, `warning`, and
+  `critical`.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s"
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. Check
+  must be of [`type`][type] `http` or `grpc`.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] stanza. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` stanzas will apply to the specified task. For `checks` on group
+  level `services` only.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+#### `header` Stanza
+
+HTTP checks may include a `header` stanza to set HTTP headers. The `header`
+stanza parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with Consul. It
+is important to understand when each of these steps happens and how they can be
+customized.
+
+**Registration**: Nomad will register `group` services and checks *before*
+starting any tasks. Services and checks for a specific `task` are registered
+*after* the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in Consul as well. Consul is updated without restarting a task.
+
+**Deregistering**: If a running task with a service stanza exits, the services
+and checks are immediately deregistered from Consul without delay. If however
+Nomad needs to kill a running task, the task is killed in the following order:
+
+1. Immediately remove the services and checks from Consul. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in Consul, and
+   thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` stanzas. Remember that the
+`service` stanza is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks.
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+This example must be accompanied by a [`network`][network] stanza which defines
+a static or dynamic port labeled "lb". For example:
+
+```hcl
+resources {
+  network {
+    mbits = 10
+    port "lb" {}
+  }
+}
+```
+
+### Script Checks with Shells
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name     = "Postgres Check"
+    type     = "script"
+    command  = "/usr/local/bin/pg-tools"
+    args     = ["verify", "database", "prod", "up"]
+    interval = "5s"
+    timeout  = "2s"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] stanza. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Using Driver Address Mode
+
+The [Docker](/docs/drivers/docker#network_mode) and
+[rkt](/docs/drivers/rkt#net) drivers support the `driver` setting for the
+`address_mode` parameter in both `service` and `check` stanzas. The driver
+address mode allows advertising and health checking the IP and port assigned to
+a task by the driver. This way if you're using a network plugin like Weave with
+Docker, you can advertise the Weave address in Consul instead of the host's
+address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+          port "db" {}
+        }
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required!
+
+Services default to the `auto` address mode. When a Docker network mode other
+than "host" or "bridge" is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` stanzas default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` stanza's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        # No port map required!
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+        }
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` stanzas can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` stanza to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        port_map {
+          db = 6379
+        }
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+          port "db" {}
+        }
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        # No port map required!
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+        network {
+          mbits = 10
+        }
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` stanzas can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the [qemu driver][qemu] since the Nomad
+  client does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_stanza]: /docs/job-specification/check_restart 'check_restart stanza'
+[consul_grpc]: https://www.consul.io/api/agent/check.html#grpc
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[service-discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /docs/drivers/qemu 'Nomad qemu Driver'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /docs/job-specification/service#type
+[shutdowndelay]: /docs/job-specification/task#shutdown_delay
+[killsignal]: /docs/job-specification/task#kill_signal
+[killtimeout]: /docs/job-specification/task#kill_timeout
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v0.12.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..f16aa06023
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: sidecar_service Stanza - Job Specification
+sidebar_title: sidecar_service
+description: |-
+  The "sidecar_service" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` stanza allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags for the sidecar service.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the sidecar proxy service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` stanza with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v0.12.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..a88025205b
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,161 @@
+---
+layout: docs
+page_title: sidecar_task Stanza - Job Specification
+sidebar_title: sidecar_task
+description: |-
+  The "sidecar_task" stanza allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` stanza allows configuring various options for the proxy
+sidecar managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service = {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v2"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy proxy sidecar
+
+Nomad automatically includes a default Envoy proxy sidecar task whenever a
+group service has a [`sidecar_service`][sidecar_service] stanza.
+
+The default sidecar task is equivalent to:
+
+```hcl
+   sidecar_task {
+     name   = "connect-proxy-<service>"
+
+     lifecycle {
+       hook = "prestart"
+       sidecar = true
+     }
+
+     driver = "docker"
+     config {
+       image = "${meta.connect.sidecar_image}"
+       args  = [
+         "-c",
+         "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+         "-l",
+         "${meta.connect.log_level}"
+       ]
+     }
+
+     logs {
+       max_files     = 2
+       max_file_size = 2 # MB
+     }
+
+     resources {
+       cpu    = 250 # MHz
+       memory = 128 # MB
+     }
+
+     shutdown_delay = "5s"
+   }
+```
+
+The `meta.connect.sidecar_image` and `meta.connect.log_level` are [_client_
+configurable][nodemeta] variables with the following defaults:
+
+- `sidecar_image` - `"envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"` - The official upstream Envoy Docker image.
+- `log_level` - `"info"` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-proxy-<service>")` - Name of the task. Defaults to
+  including the name of the service it is a proxy for.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /docs/job-specification/connect 'Nomad connect Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[nodemeta]: /docs/configuration/client#meta
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/spread.mdx b/content/nomad/v0.12.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..04c05899ad
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,164 @@
+---
+layout: docs
+page_title: spread Stanza - Job Specification
+sidebar_title: spread
+description: >-
+  The "spread" stanza is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread stanza may be specified with relative weights between
+  each.
+---
+
+# `spread` Stanza
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread']
+  ]}
+/>
+
+The `spread` stanza allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread stanza. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler.
+If no nodes match a given spread criteria, placement is still successful.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread stanza. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread stanza. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity stanza to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` stanza.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` stanza.
+
+### Even Spread Across Data Center
+
+This example shows a spread stanza across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread stanza that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread stanza that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread stanzas with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread stanza used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/task.mdx b/content/nomad/v0.12.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..fac774b009
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,218 @@
+---
+layout: docs
+page_title: task Stanza - Job Specification
+sidebar_title: task
+description: |-
+  The "task" stanza creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Stanza
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` stanza creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`). Note that this is only
+  supported for drivers sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to true, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing it from Consul and sending it a shutdown
+  signal. Ideally services would fail healthchecks once they receive a shutdown
+  signal. Alternatively `shutdown_delay` may be set to give in flight requests
+  time to complete before shutting down. In addition, task groups may have their
+  own [`shutdown_delay`](/docs/job-specification/group#shutdown_delay)
+  which waits between deregistering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_blacklist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` stanzas. Remember that the
+`task` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /docs/drivers/exec 'Nomad exec Driver'
+[java]: /docs/drivers/java 'Nomad Java Driver'
+[docker]: /docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /docs/configuration/client#user-checked_drivers
+[user_blacklist]: /docs/configuration/client#user-blacklist
+[max_kill]: /docs/configuration/client#max_kill_timeout
+[kill_signal]: /docs/job-specification/task#kill_signal
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/template.mdx b/content/nomad/v0.12.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..a4feba161d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,345 @@
+---
+layout: docs
+page_title: template Stanza - Job Specification
+sidebar_title: template
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Stanza
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. Since Nomad
+v0.5.6, the template can reference [Node attributes and metadata][nodevars]. For
+a full list of the API template functions, please refer to the [Consul Template
+README][ct]. Since Nomad v0.6.0, templates can be read as environment variables.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the task directory.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task. ([See below](#environment-variables))
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside of a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` stanzas. Remember that the
+`template` stanza is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] stanza to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template stanza:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `template.allow_host_source` - Allows templates to specify their source
+  template as an absolute path referencing host directories. Defaults to `true`.
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/update.mdx b/content/nomad/v0.12.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..953b93f166
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,272 @@
+---
+layout: docs
+page_title: update Stanza - Job Specification
+sidebar_title: update
+description: |-
+  The "update" stanza specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, rolling updates and canaries are disabled.
+---
+
+# `update` Stanza
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update']
+  ]}
+/>
+
+The `update` stanza specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, rolling updates and canaries are disabled. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` stanzas are specified, they are merged with the
+group stanza taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` stanza in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state. If no allocation
+  transitions to the healthy state before the progress deadline, the deployment
+  is marked as failed. If the `progress_deadline` is set to `0`, the first
+  allocation to be marked as unhealthy causes the deployment to fail. This is
+  specified using a label suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to the
+  canary version when all canaries become healthy during a deployment. Defaults to
+  false which means canaries must be manually updated with the `nomad deployment promote`
+  command.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` stanzas. Remember that the
+`update` stanza is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Stanza Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update stanza, each groups update
+stanza may be kept to a minimum. The merged update stanzas for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 'Nomad Rolling Upgrades'
+[strategies]: https://learn.hashicorp.com/nomad/update-strategies 'Nomad Update Strategies'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v0.12.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..59c5cb010a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: upstreams Stanza - Job Specification
+sidebar_title: upstreams
+description: |-
+  The "upstreams" stanza allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams'
+  ]}
+/>
+
+The `upstreams` stanza allows configuring various options for managing upstream
+services that a [Consul
+Connect](/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` stanza.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v1"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/vault.mdx b/content/nomad/v0.12.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..f823659c5c
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: vault Stanza - Job Specification
+sidebar_title: vault
+description: |-
+  The "vault" stanza allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Stanza
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault']
+  ]}
+/>
+
+The `vault` stanza allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` stanzas are specified, they are merged with the `task` stanza
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/docs/configuration/vault#namespace)
+to use [Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` stanza is specified, the [`template`][template] stanza can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/volume.mdx b/content/nomad/v0.12.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..1411b86cd7
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: volume Stanza - Job Specification
+sidebar_title: volume
+description: >-
+  The "volume" stanza allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Stanza
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` stanza allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the stanza is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` stanzas. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] stanza in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+[volume_mount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /docs/configuration/client/#host_volume-stanza
+[csi_volume]: /docs/commands/volume/register
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v0.12.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v0.12.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..4f9b2becbb
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: volume_mount Stanza - Job Specification
+sidebar_title: volume_mount
+description: |-
+  The "volume_mount" stanza allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` stanza allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v0.12.x/content/docs/runtime/environment.mdx b/content/nomad/v0.12.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..03313bfbfd
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Environment - Runtime
+sidebar_title: Runtime Environment
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name as well as the task, group and
+job's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`.
+The allocation ID and index can be useful when the task being run needs a unique
+identifier or to know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT` and
+`NOMAD_MEMORY_LIMIT`. Your task should use these values to adapt its behavior to
+fit inside the resource allocation that nomad provides. For example, you can use
+the memory limit to inform how large your in-process cache should be, or to
+decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad makes the following directories available to tasks:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs and where possible backed by an
+  in-memory filesystem. It can be used to store secret data that should not be
+  visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories are
+made available in various ways. For example, on `docker` the directories are
+bound to the container, while on `exec` on Linux the directories are mounted into the
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v0.12.x/content/docs/runtime/index.mdx b/content/nomad/v0.12.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..395b323583
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/docs/runtime/environment)
+- [Interpolation](/docs/runtime/interpolation)
+- [Schedulers](/docs/schedulers)
diff --git a/content/nomad/v0.12.x/content/docs/runtime/interpolation.mdx b/content/nomad/v0.12.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..0706d06efa
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,341 @@
+---
+layout: docs
+page_title: Variable Interpolation
+sidebar_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    "DC"      = "Running on datacenter ${node.datacenter}"
+    "VERSION" = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.placement.availability-zone}'}</code>
+      </td>
+      <td>Availability Zone of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:3.2"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v0.12.x/content/docs/schedulers.mdx b/content/nomad/v0.12.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..304f6d60c2
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/schedulers.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: Schedulers
+sidebar_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has three scheduler types that can be used when creating your job:
+`service`, `batch` and `system`. Here we will describe the differences between
+each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] stanzas.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+stanzas.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] stanza; system jobs do not have rescheduling.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
+[preemption]: /docs/internals/scheduling/preemption
+[restart]: /docs/job-specification/restart
+[reschedule]: /docs/job-specification/reschedule
diff --git a/content/nomad/v0.12.x/content/docs/telemetry/index.mdx b/content/nomad/v0.12.x/content/docs/telemetry/index.mdx
new file mode 100644
index 0000000000..4126835b21
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/telemetry/index.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: Telemetry Overview
+sidebar_title: Telemetry
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Telemetry Overview
+
+The Nomad client and server agents collect a wide range of runtime metrics
+related to the performance of the system. Operators can use this data to gain
+real-time visibility into their cluster and improve performance. Additionally,
+Nomad operators can set up monitoring and alerting based on these metrics in
+order to respond to any changes in the cluster state.
+
+On the server side, leaders and
+followers have metrics in common as well as metrics that are specific to their
+roles. Clients have separate metrics for the host metrics and for
+allocations/tasks, both of which have to be [explicitly
+enabled][telemetry-stanza]. There are also runtime metrics that are common to
+all servers and clients.
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [Gauges, counters and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/metrics API endpoint][metrics-api-endpoint] to return metrics for
+  the current Nomad process (as of Nomad 0.7). This endpoint supports Prometheus
+  formatted metrics.
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+- Configure Nomad to automatically forward metrics to a third-party provider.
+
+Nomad 0.7 added support for [tagged metrics][tagged-metrics], improving the
+integrations with [DataDog][datadog-telem] and [Prometheus][prometheus-telem].
+Metrics can also be forwarded to [Statsite][statsite-telem],
+[StatsD][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns:
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+The sections below cover a number of important metrics
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking issues
+between the servers or insufficient CPU resources. Users in cloud environments
+often bump their servers up to the next instance class with improved networking
+and CPU to stabilize leader elections. The `nomad.raft.leader.lastContact` metric
+is a general indicator of Raft latency which can be used to observe how Raft
+timing is performing and guide the decision to upgrade to more powerful servers.
+`nomad.raft.leader.lastContact` should not get too close to the leader lease
+timeout of 500ms.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+## Scheduling
+
+The following metrics allow an operator to observe changes in throughput at the
+various points in the scheduling process (evaluation, scheduling/planning, and
+placement):
+
+- **nomad.broker.total_blocked** - The number of blocked evaluations.
+- **nomad.worker.invoke_scheduler.\<type\>** - The time to run the scheduler of
+  the given type.
+- **nomad.plan.evaluate** - The time to evaluate a scheduler Plan.
+- **nomad.plan.submit** - The time to submit a scheduler Plan.
+- **nomad.plan.queue_depth** - The number of scheduler Plans waiting to be
+  evaluated.
+
+Upticks in any of the above metrics indicate a decrease in scheduler throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis:
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+We do not currently surface metrics for job and task/allocation status, although
+we will consider adding metrics where it makes sense.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure:
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /docs/configuration/telemetry#circonus
+[collection-interval]: /docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /docs/configuration/telemetry#datadog
+[prometheus-telem]: /docs/configuration/telemetry#prometheus
+[metrics-api-endpoint]: /api-docs/metrics
+[metric-types]: /docs/telemetry/metrics#metric-types
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /docs/configuration/telemetry#statsd
+[statsite-telem]: /docs/configuration/telemetry#statsite
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[telemetry-stanza]: /docs/configuration/telemetry
diff --git a/content/nomad/v0.12.x/content/docs/telemetry/metrics.mdx b/content/nomad/v0.12.x/content/docs/telemetry/metrics.mdx
new file mode 100644
index 0000000000..c94a8351c1
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/telemetry/metrics.mdx
@@ -0,0 +1,1165 @@
+---
+layout: docs
+page_title: Metrics
+sidebar_title: Metrics
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process.
+
+As of Nomad version 0.7, this data is available via HTTP at `/metrics`. See
+[Metrics](/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+## Key Metrics
+
+When telemetry is being streamed to statsite or statsd, `interval` is defined to
+be their flush interval. Otherwise, the interval can be assumed to be 10 seconds
+when retrieving metrics using the above described signals.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.runtime.num_goroutines</code>
+      </td>
+      <td>Number of goroutines and general load pressure indicator</td>
+      <td># of goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.runtime.alloc_bytes</code>
+      </td>
+      <td>Memory utilization</td>
+      <td># of bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.runtime.heap_objects</code>
+      </td>
+      <td>Number of objects on the heap. General memory pressure indicator</td>
+      <td># of heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.apply</code>
+      </td>
+      <td>Number of Raft transactions</td>
+      <td>Raft transactions / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.replication.appendEntries</code>
+      </td>
+      <td>Raft transaction commit time</td>
+      <td>ms / Raft Log Append</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.raft.leader.lastContact</code>
+      </td>
+      <td>
+        Time since last contact to leader. General indicator of Raft latency
+      </td>
+      <td>ms / Leader Contact</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_ready</code>
+      </td>
+      <td>Number of evaluations ready to be processed</td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_unacked</code>
+      </td>
+      <td>Evaluations dispatched for processing but incomplete</td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.broker.total_blocked</code>
+      </td>
+      <td>
+        Evaluations that are blocked until an existing evaluation for the same
+        job completes
+      </td>
+      <td># of evaluations</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.queue_depth</code>
+      </td>
+      <td>Number of scheduler Plans waiting to be evaluated</td>
+      <td># of plans</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.submit</code>
+      </td>
+      <td>
+        Time to submit a scheduler Plan. Higher values cause lower scheduling
+        throughput
+      </td>
+      <td>ms / Plan Submit</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.plan.evaluate</code>
+      </td>
+      <td>
+        Time to validate a scheduler Plan. Higher values cause lower scheduling
+        throughput. Similar to <code>nomad.plan.submit</code> but does not
+        include RPC time or time in the Plan Queue
+      </td>
+      <td>ms / Plan Evaluation</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.worker.invoke_scheduler.&lt;type&gt;</code>
+      </td>
+      <td>Time to run the scheduler of the given type</td>
+      <td>ms / Scheduler Run</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.worker.wait_for_index</code>
+      </td>
+      <td>
+        Time waiting for Raft log replication from leader. High delays result in
+        lower scheduling throughput
+      </td>
+      <td>ms / Raft Index Wait</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.heartbeat.active</code>
+      </td>
+      <td>
+        Number of active heartbeat timers. Each timer represents a Nomad Client
+        connection
+      </td>
+      <td># of heartbeat timers</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.heartbeat.invalidate</code>
+      </td>
+      <td>
+        The length of time it takes to invalidate a Nomad Client due to failed
+        heartbeats
+      </td>
+      <td>ms / Heartbeat Invalidation</td>
+      <td>Timer</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.query</code>
+      </td>
+      <td>Number of RPC queries</td>
+      <td>RPC Queries / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.request</code>
+      </td>
+      <td>Number of RPC requests being handled</td>
+      <td>RPC Requests / `interval`</td>
+      <td>Counter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.rpc.request_error</code>
+      </td>
+      <td>Number of RPC requests being handled that result in an error</td>
+      <td>RPC Errors / `interval`</td>
+      <td>Counter</td>
+    </tr>
+  </tbody>
+</table>
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/docs/configuration/telemetry)
+page for more details.
+
+As of Nomad 0.9, Nomad will emit additional labels for [parameterized](/docs/job-specification/parameterized) and
+[periodic](/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+<table>
+  <thead>
+    <tr>
+      <th>Label</th>
+      <th>Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>job</td>
+      <td>
+        <code>myjob/dispatch-1312323423423</code>
+      </td>
+    </tr>
+    <tr>
+      <td>parent_id</td>
+      <td>myjob</td>
+    </tr>
+    <tr>
+      <td>dispatch_id</td>
+      <td>1312323423423</td>
+    </tr>
+  </tbody>
+</table>
+
+## Host Metrics (post Nomad version 0.7)
+
+Starting in version 0.7, Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.cpu</code>
+      </td>
+      <td>Total amount of CPU shares the scheduler has allocated to tasks</td>
+      <td>MHz</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.cpu</code>
+      </td>
+      <td>
+        Total amount of CPU shares free for the scheduler to allocate to tasks
+      </td>
+      <td>MHz</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.memory</code>
+      </td>
+      <td>Total amount of memory the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.memory</code>
+      </td>
+      <td>
+        Total amount of memory free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.disk</code>
+      </td>
+      <td>Total amount of disk space the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.disk</code>
+      </td>
+      <td>
+        Total amount of disk space free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.network</code>
+      </td>
+      <td>
+        Total amount of bandwidth the scheduler has allocated to tasks on the
+        given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, device</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.network</code>
+      </td>
+      <td>
+        Total amount of bandwidth free for the scheduler to allocate to tasks on
+        the given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, device</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.total</code>
+      </td>
+      <td>Total amount of physical memory on the node</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.available</code>
+      </td>
+      <td>
+        Total amount of memory available to processes which includes free and
+        cached memory
+      </td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.used</code>
+      </td>
+      <td>Amount of memory used by processes</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.free</code>
+      </td>
+      <td>Amount of memory which is free</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.uptime</code>
+      </td>
+      <td>Uptime of the host running the Nomad client</td>
+      <td>Seconds</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.total</code>
+      </td>
+      <td>Total CPU utilization</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.user</code>
+      </td>
+      <td>CPU utilization in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.system</code>
+      </td>
+      <td>CPU utilization in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.idle</code>
+      </td>
+      <td>Idle time spent by the CPU</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, cpu</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.size</code>
+      </td>
+      <td>Total size of the device</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.used</code>
+      </td>
+      <td>Amount of space which has been used</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.available</code>
+      </td>
+      <td>Amount of space which is available</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.used_percent</code>
+      </td>
+      <td>Percentage of disk space used</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.disk.inodes_percent</code>
+      </td>
+      <td>Disk space consumed by the inodes</td>
+      <td>Percent</td>
+      <td>Gauge</td>
+      <td>node_id, datacenter, disk</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.start</code>
+      </td>
+      <td>Number of allocations starting</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.running</code>
+      </td>
+      <td>Number of allocations starting to run</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.failed</code>
+      </td>
+      <td>Number of allocations failing</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.restart</code>
+      </td>
+      <td>Number of allocations restarting</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.complete</code>
+      </td>
+      <td>Number of allocations completing</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocs.destroy</code>
+      </td>
+      <td>Number of allocations being destroyed</td>
+      <td>Integer</td>
+      <td>Counter</td>
+      <td>node_id, job, task_group</td>
+    </tr>
+  </tbody>
+</table>
+
+Nomad 0.9 adds an additional `node_class` label from the client's
+`NodeClass` attribute. This label is set to the string "none" if empty.
+
+## Host Metrics (deprecated post Nomad 0.7)
+
+The below are metrics emitted by Nomad in versions prior to 0.7. These metrics
+can be emitted in the below format post-0.7 (as well as the new format,
+detailed above) but any new metrics will only be available in the new format.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.cpu.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of CPU shares the scheduler has allocated to tasks</td>
+      <td>MHz</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.cpu.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of CPU shares free for the scheduler to allocate to tasks
+      </td>
+      <td>MHz</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.memory.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of memory the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.memory.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of memory free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.allocated.disk.&lt;HostID&gt;</code>
+      </td>
+      <td>Total amount of disk space the scheduler has allocated to tasks</td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.unallocated.disk.&lt;HostID&gt;</code>
+      </td>
+      <td>
+        Total amount of disk space free for the scheduler to allocate to tasks
+      </td>
+      <td>Megabytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocated.network.&lt;Device-Name&gt;.&lt;HostID&gt;
+        </code>
+      </td>
+      <td>
+        Total amount of bandwidth the scheduler has allocated to tasks on the
+        given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.unallocated.network.&lt;Device-Name&gt;.&lt;HostID&gt;
+        </code>
+      </td>
+      <td>
+        Total amount of bandwidth free for the scheduler to allocate to tasks on
+        the given device
+      </td>
+      <td>Megabits</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.total</code>
+      </td>
+      <td>Total amount of physical memory on the node</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.available</code>
+      </td>
+      <td>
+        Total amount of memory available to processes which includes free and
+        cached memory
+      </td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.used</code>
+      </td>
+      <td>Amount of memory used by processes</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.memory.&lt;HostID&gt;.free</code>
+      </td>
+      <td>Amount of memory which is free</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.uptime.&lt;HostID&gt;</code>
+      </td>
+      <td>Uptime of the host running the Nomad client</td>
+      <td>Seconds</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.total</code>
+      </td>
+      <td>Total CPU utilization</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.user</code>
+      </td>
+      <td>CPU utilization in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.system
+        </code>
+      </td>
+      <td>CPU utilization in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.client.host.cpu.&lt;HostID&gt;.&lt;CPU-Core&gt;.idle</code>
+      </td>
+      <td>Idle time spent by the CPU</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.size
+        </code>
+      </td>
+      <td>Total size of the device</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.used
+        </code>
+      </td>
+      <td>Amount of space which has been used</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.available
+        </code>
+      </td>
+      <td>Amount of space which is available</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.used_percent
+        </code>
+      </td>
+      <td>Percentage of disk space used</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.host.disk.&lt;HostID&gt;.&lt;Device-Name&gt;.inodes_percent
+        </code>
+      </td>
+      <td>Disk space consumed by the inodes</td>
+      <td>Percent</td>
+      <td>Gauge</td>
+    </tr>
+  </tbody>
+</table>
+
+## Allocation Metrics
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.allocated
+        </code>
+      </td>
+      <td>Amount of memory allocated by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.rss
+        </code>
+      </td>
+      <td>Amount of RSS memory consumed by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.cache
+        </code>
+      </td>
+      <td>Amount of memory cached by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.swap
+        </code>
+      </td>
+      <td>Amount of memory swapped by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.usage
+        </code>
+      </td>
+      <td>Total amount of memory used by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.max_usage
+        </code>
+      </td>
+      <td>Maximum amount of memory ever used by the task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.kernel_usage
+        </code>
+      </td>
+      <td>Amount of memory used by the kernel for this task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.memory.kernel_max_usage
+        </code>
+      </td>
+      <td>Maximum amount of memory ever used by the kernel for this task</td>
+      <td>Bytes</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.allocated
+        </code>
+      </td>
+      <td>Total CPU resources allocated by the task across all cores</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>alloc_id, host, job, namespace, task, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.total_percent
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task across all cores</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.system
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task in the system space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.user
+        </code>
+      </td>
+      <td>Total CPU resources consumed by the task in the user space</td>
+      <td>Percentage</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.throttled_time
+        </code>
+      </td>
+      <td>Total time that the task was throttled</td>
+      <td>Nanoseconds</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.throttled_periods
+        </code>
+      </td>
+      <td>Total number of CPU periods that the task was throttled</td>
+      <td>Nanoseconds</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          nomad.client.allocs.cpu.total_ticks
+        </code>
+      </td>
+      <td>CPU ticks consumed by the process in the last collection interval</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>alloc_id, task, namespace, host, job, task_group</td>
+    </tr>
+  </tbody>
+</table>
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.job_summary.queued</code>
+      </td>
+      <td>Number of queued allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.complete</code>
+      </td>
+      <td>Number of complete allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.failed</code>
+      </td>
+      <td>Number of failed allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.running</code>
+      </td>
+      <td>Number of running allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.starting</code>
+      </td>
+      <td>Number of starting allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_summary.lost</code>
+      </td>
+      <td>Number of lost allocations for a job</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+      <td>job, task_group</td>
+    </tr>
+  </tbody>
+</table>
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Unit</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad.job_status.pending</code>
+      </td>
+      <td>Number jobs pending</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_status.running</code>
+      </td>
+      <td>Number jobs running</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad.job_status.dead</code>
+      </td>
+      <td>Number of dead jobs</td>
+      <td>Integer</td>
+      <td>Gauge</td>
+    </tr>
+  </tbody>
+</table>
+
+## Metric Types
+
+<table>
+  <thead>
+    <tr>
+      <th>Type</th>
+      <th>Description</th>
+      <th>Quantiles</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Gauge</td>
+      <td>
+        Gauge types report an absolute number at the end of the aggregation
+        interval
+      </td>
+      <td>false</td>
+    </tr>
+    <tr>
+      <td>Counter</td>
+      <td>
+        Counts are incremented and flushed at the end of the aggregation
+        interval and then are reset to zero
+      </td>
+      <td>true</td>
+    </tr>
+    <tr>
+      <td>Timer</td>
+      <td>
+        Timers measure the time to complete a task and will include quantiles,
+        means, standard deviation, etc per interval.
+      </td>
+      <td>true</td>
+    </tr>
+  </tbody>
+</table>
+
+## Tagged Metrics
+
+As of version 0.7, Nomad will start emitting metrics in a tagged format. Each
+metric can support more than one tag, meaning that it is possible to do a
+match over metrics for datapoints such as a particular datacenter, and return
+all metrics with this tag. Nomad supports labels for namespaces as well.
+
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
diff --git a/content/nomad/v0.12.x/content/docs/upgrade/index.mdx b/content/nomad/v0.12.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..2f216ba884
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/docs/commands/node/drain) command.
+
+## Done!
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /docs/configuration#data_dir
+[heartbeat_grace]: /docs/configuration/server#heartbeat_grace
+[monitor]: /docs/commands/monitor
+[node-status]: /docs/commands/node/status
+[server-members]: /docs/commands/server/members
+[upgrade-specific]: /docs/upgrade/upgrade-specific
diff --git a/content/nomad/v0.12.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v0.12.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..d54b2b611a
--- /dev/null
+++ b/content/nomad/v0.12.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,802 @@
+---
+layout: docs
+page_title: Upgrade Guides
+sidebar_title: Specific Version Details
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/docs/upgrade) covers the details of doing
+a standard upgrade. However, specific versions of Nomad may have more
+details provided for their upgrades as a result of new features or changed
+behavior. This page is used to document those details separately from the
+standard upgrade flow.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed
+  and could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled =
+true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.7. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated.  This is in part because we felt that `mbits` didn't
+accurately account network bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block is
+also deprecated. Users are advised to move their `network` block to the `group`
+block. Recent networking features have only been added to group based network
+configuration. If any usecase or feature which was available with task network
+resource is not fulfilled with group network configuration, please open an issue
+detailing the missing capability.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put
+...`](https://www.nomadproject.io/docs/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+   that are upgraded will **not** have 6 hours to apply a license. The minimal
+   grace period should be sufficient to apply a valid license, but enterprise
+   users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+   fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/docs/configuration/client#host_volume-stanza) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### Qemu images
+
+Nomad 0.12.0 restricts the paths the Qemu tasks can load an image from. A Qemu
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading Qemu images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fixes for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled =
+true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do *not* need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasability (whether a node is capable of running a job at all) is *not*
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1.
+This library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the
+code is available in an external repository,
+[https://github.com/hashicorp/nomad-driver-rkt](https://github.com/hashicorp/nomad-driver-rkt),
+it will not be maintained as `rkt` is [no longer being developed
+upstream](https://github.com/rkt/rkt). We encourage all `rkt` users to find a
+new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fixes for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled =
+true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the
+same-node penalty for allocations that have not previously failed. In
+earlier versions of Nomad, the node where an allocation was running
+was penalized from receiving updated versions of that allocation,
+resulting in a higher chance of the allocation being placed on a new
+node. This was changed so that the penalty only applies to nodes where
+the previous allocation has failed or been rescheduled, to reduce the
+risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that
+are being updated from a healthy state. You can view the placement
+metrics for an allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with TLS][tls-guide]
+guide or the [Vault PKI Secrets Engine Integration][tls-vault-guide] guide
+should already have certificates that will pass validation. Before upgrading to
+Nomad 0.10.3, operators using mTLS with `verify_server_hostname = true` should
+confirm that the common name or SAN of all Nomad client node certs is
+`client.<region>.nomad`, and that the common name or SAN of all Nomad server
+node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][limits] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits stanza is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in
+scheduler preemption since 0.9.0. Users unable to immediately upgrade Nomad can
+[disable preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default
+and adds a default update stanza when a service job is created or updated.
+This does not affect jobs with an update stanza.
+
+In pre-0.10 releases, when updating a service job without an update stanza,
+all existing allocations are stopped while new allocations start up,
+and this may cause a service degradation or an outage.
+You can regain this behavior and disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` stanza][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in handling of job `template` stanzas:
+
+- The client host's environment variables are now cleaned before rendering the template. If a template includes the `env` function, the job should include an [`env`](/docs/job-specification/env) stanza to allow access to the variable in the template.
+- The `plugin` function is no longer permitted by default and will raise an error if used in a template. Operator can opt-in to permitting this function with the new [`template.function_blacklist`](/docs/configuration/client#template-parameters) field in the client configuration.
+- The `file` function has been changed to restrict paths to fall inside the task directory by default. Paths that used the `NOMAD_TASK_DIR` environment variable to prefix file paths should work unchanged. Relative paths or symlinks that point outside the task directory will raise an error. An operator can opt-out of this protection with the new [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters) field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+- Task driver [`config`][task-config] stanzas are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-stanza] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2,
+users will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` stanza. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should
+transition away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a
+previous version of the client after upgrading it to Nomad 0.9 is not supported.
+To downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` stanza could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` stanza, including
+its `port_map`, are available for interpolation. This means `{{ env
+NOMAD_PORT_<label> }}` in a `template` stanza or `HTTP_PORT =
+"${NOMAD_PORT_http}"` in an `env` stanza will now interpolate the *host* ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port
+mapping without relying on task driver specific `port_map` fields. The
+[`to`](/docs/job-specification/network/#to) field on group network port stanzas
+will be interpolated properly. Please see the
+[`network`](/docs/job-specification/network/) stanza documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the
+[`raft_protocol`](/docs/configuration/server#raft_protocol) option
+in their `server` stanza to 1 in order to maintain backwards compatibility with
+the old servers during the upgrade. After the servers have been migrated to
+version 0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted
+to match the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers are
+compatible (for example, version 1 cannot talk to version 3). Here is a table of the
+Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all [Autopilot](https://learn.hashicorp.com/nomad/operating-nomad/autopilot) features, all servers
+in a Nomad cluster must be running with Raft protocol version 3 or later.
+
+#### Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3 in Nomad 0.8 and higher. Raft protocol version 3 requires Nomad running 0.8.0 or newer on all servers in order to work. See [Raft Protocol Version Compatibility](/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility) for more details. Also the format of `peers.json` used for outage recovery is different when running with the latest Raft protocol. See [Manual Recovery Using peers.json](https://learn.hashicorp.com/nomad/operating-nomad/outage#manual-recovery-using-peersjson) for a description of the required format.
+
+Please note that the Raft protocol is different from Nomad's internal protocol as shown in commands like `nomad server members`. To see the version of the Raft protocol in use on each server, use the `nomad operator raft list-peers` command.
+
+The easiest way to upgrade servers is to have each server leave the cluster, upgrade its `raft_protocol` version in the `server` stanza, and then add it back. Make sure the new server joins successfully and that the cluster is stable before rolling the upgrade forward to the next server. It's also possible to stand up a new set of servers, and then slowly stand down each of the older servers in a similar fashion.
+
+When using Raft protocol version 3, servers are identified by their `node-id` instead of their IP address when Nomad makes changes to its internal Raft quorum configuration. This means that once a cluster has been upgraded with servers all running Raft protocol version 3, it will no longer allow servers running any older Raft protocol versions to be added. If running a single Nomad server, restarting it in-place will result in that server not being able to elect itself as a leader. To avoid this, either set the Raft protocol back to 2, or use [Manual Recovery Using peers.json](https://learn.hashicorp.com/nomad/operating-nomad/outage#manual-recovery-using-peersjson) to map the server to its node ID in the Raft quorum configuration.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] stanza in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad
+0.7.1 and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` stanza documentation][migrate] and [Decommissioning Nodes
+guide](https://learn.hashicorp.com/nomad/operating-nomad/node-draining) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/docs/job-specification/env) and
+[`template`](/docs/job-specification/template) stanzas.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following stanza:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC
+address](/docs/configuration#rpc-1) has changed to be only used
+to advertise the RPC address of servers to client nodes. Server to server
+communication is done using the advertised Serf address. Existing cluster's
+should not be effected but the advertised RPC address may need to be updated to
+allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/docs/configuration/client#network_interface)
+such that tasks bind to the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[dangling-containers]: /docs/drivers/docker#dangling-containers
+[drain-api]: /api-docs/nodes#drain-node
+[drain-cli]: /docs/commands/node/drain
+[dst]: /docs/job-specification/periodic#daylight-saving-time
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /docs/configuration#limits
+[lxc]: /docs/drivers/external/lxc
+[migrate]: /docs/job-specification/migrate
+[plugin-stanza]: /docs/configuration/plugin
+[plugins]: /docs/drivers/external
+[preemption-api]: /api-docs/operator#update-scheduler-configuration
+[preemption]: /docs/internals/scheduling/preemption
+[reserved]: /docs/configuration/client#reserved-parameters
+[task-config]: /docs/job-specification/task#config
+[tls-guide]: https://learn.hashicorp.com/nomad/transport-security/enable-tls
+[tls-vault-guide]: https://learn.hashicorp.com/nomad/vault-integration/vault-pki-nomad
+[update]: /docs/job-specification/update
+[validate]: /docs/commands/job/validate
+[vault_grace]: /docs/job-specification/template
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/cluster.mdx b/content/nomad/v0.12.x/content/intro/getting-started/cluster.mdx
new file mode 100644
index 0000000000..88d1be5b21
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/cluster.mdx
@@ -0,0 +1,221 @@
+---
+layout: intro
+page_title: Clustering
+sidebar_title: Clustering
+description: Join another Nomad client to create your first cluster.
+---
+
+# Clustering
+
+We have started our first agent and run a job against it in development mode.
+This demonstrates the ease of use and the workflow of Nomad, but did not show how
+this could be extended to a scalable, production-grade configuration. In this step,
+we will create our first real cluster with multiple nodes.
+
+## Starting the Server
+
+The first step is to create the config file for the server. Either download the
+[file from the repository][server.hcl], or paste this into a file called
+`server.hcl`:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/server1"
+
+# Enable the server
+server {
+    enabled = true
+
+    # Self-elect, should be 3 or 5 for production
+    bootstrap_expect = 1
+}
+```
+
+This is a fairly minimal server configuration file, but it
+is enough to start an agent in server only mode and have it
+elected as a leader. The major change that should be made for
+production is to run more than one server, and to change the
+corresponding `bootstrap_expect` value.
+
+Once the file is created, start the agent in a new tab:
+
+```shell-session
+$ nomad agent -config server.hcl
+==> WARNING: Bootstrap mode enabled! Potentially unsafe operation.
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: false
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+               Version: 0.7.0
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: nomad.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+    [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state
+    [INFO] nomad: adding server nomad.global (Addr: 127.0.0.1:4647) (DC: dc1)
+    [WARN] raft: Heartbeat timeout reached, starting election
+    [INFO] raft: Node at 127.0.0.1:4647 [Candidate] entering Candidate state
+    [DEBUG] raft: Votes needed: 1
+    [DEBUG] raft: Vote granted. Tally: 1
+    [INFO] raft: Election won. Tally: 1
+    [INFO] raft: Node at 127.0.0.1:4647 [Leader] entering Leader state
+    [INFO] nomad: cluster leadership acquired
+    [INFO] raft: Disabling EnableSingleNode (bootstrap)
+    [DEBUG] raft: Node 127.0.0.1:4647 updated peer set (2): [127.0.0.1:4647]
+```
+
+We can see above that client mode is disabled, and that we are
+only running as the server. This means that this server will manage
+state and make scheduling decisions but will not run any tasks.
+Now we need some agents to run tasks!
+
+## Starting the Clients
+
+Similar to the server, we must first configure the clients. Either download
+the configuration for `client1` and `client2` from the
+[repository here](https://github.com/hashicorp/nomad/tree/master/demo/vagrant), or
+paste the following into `client1.hcl`:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/client1"
+
+# Give the agent a unique name. Defaults to hostname
+name = "client1"
+
+# Enable the client
+client {
+    enabled = true
+
+    # For demo assume we are talking to server1. For production,
+    # this should be like "nomad.service.consul:4647" and a system
+    # like Consul used for service discovery.
+    servers = ["127.0.0.1:4647"]
+}
+
+# Modify our port to avoid a collision with server1
+ports {
+    http = 5656
+}
+```
+
+Copy that file to `client2.hcl`. Change the `data_dir` to be `/tmp/client2`,
+the `name` to `client2`, and the `http` port to 5657. Once you have created
+both `client1.hcl` and `client2.hcl`, open a tab for each and start the agents:
+
+```shell-session
+$ sudo nomad agent -config client1.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: false
+               Version: 0.7.0
+
+==> Nomad agent started! Log data will stream in below:
+
+    [DEBUG] client: applied fingerprints [host memory storage arch cpu]
+    [DEBUG] client: available drivers [docker exec]
+    [DEBUG] client: node registration complete
+    ...
+```
+
+In the output we can see the agent is running in client mode only.
+This agent will be available to run tasks but will not participate
+in managing the cluster or making scheduling decisions.
+
+Using the [`node status` command](/docs/commands/node/status)
+we should see both nodes in the `ready` state:
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+fca62612  dc1  client1  <none>  false  eligible     ready
+c887deef  dc1  client2  <none>  false  eligible     ready
+```
+
+We now have a simple three node cluster running. The only difference
+between a demo and full production cluster is that we are running a
+single server instead of three or five.
+
+## Submit a Job
+
+Now that we have a simple cluster, we can use it to schedule a job.
+We should still have the `example.nomad` job file from before, but
+verify that the `count` is still set to 3.
+
+Then, use the [`job run` command](/docs/commands/job/run) to submit the job:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "8e0a7cf9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "0917b771"
+    Allocation "501154ac" created: node "c887deef", group "cache"
+    Allocation "7e2b3900" created: node "fca62612", group "cache"
+    Allocation "9c66fcaf" created: node "c887deef", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8e0a7cf9" finished with status "complete"
+```
+
+We can see in the output that the scheduler assigned two of the
+tasks for one of the client nodes and the remaining task to the
+second client.
+
+We can again use the [`status` command](/docs/commands/status) to verify:
+
+```shell-session
+$ nomad status example
+ID          = example
+Name        = example
+Submit Date   = 07/26/17 16:34:58 UTC
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+
+Latest Deployment
+ID          = fc49bd6c
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        3       0        0
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status   Created At
+501154ac  8e0a7cf9  c887deef  cache       run      running  08/08/16 21:03:19 CDT
+7e2b3900  8e0a7cf9  fca62612  cache       run      running  08/08/16 21:03:19 CDT
+9c66fcaf  8e0a7cf9  c887deef  cache       run      running  08/08/16 21:03:19 CDT
+```
+
+We can see that all our tasks have been allocated and are running.
+Once we are satisfied that our job is happily running, we can tear
+it down with `nomad job stop`.
+
+## Next Steps
+
+Nomad is now up and running. The cluster can be entirely managed from the command line,
+but Nomad also comes with a web interface that is hosted alongside the HTTP API.
+Next, we'll [visit the UI in the browser](/intro/getting-started/ui).
+
+[server.hcl]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/server.hcl
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/index.mdx b/content/nomad/v0.12.x/content/intro/getting-started/index.mdx
new file mode 100644
index 0000000000..a9fff53359
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: intro
+page_title: Install Nomad
+sidebar_title: Getting Started
+description: The first step to using Nomad is to get it installed.
+---
+
+# Install Nomad
+
+To simplify the getting started experience, you can download the pre-compiled
+binary and run it directly (see the instructions [here][binary-instructions]) or
+you can optionally work in a Vagrant environment (detailed in the following
+section).
+
+## Vagrant Setup (Optional)
+
+Note: To use the Vagrant Setup first install Vagrant following these
+[instructions][install-instructions].
+
+Create a new directory, and download [this
+`Vagrantfile`](https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile).
+
+Once you have created a new directory and downloaded the `Vagrantfile` you must
+create the virtual machine:
+
+```shell-session
+$ vagrant up
+```
+
+This will take a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see output similar to:
+
+```text
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-16.04'...
+...
+==> default: Running provisioner: docker...
+
+```
+
+At this point the Vagrant box is running and ready to go.
+
+## Verifying the Installation
+
+After starting the Vagrant box, verify the installation worked by connecting
+to the box using SSH and checking that `nomad` is available. By executing
+`nomad`, you should see help output similar to the following:
+
+```shell-session
+$ vagrant ssh
+...
+
+vagrant@nomad:~$ nomad
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+If you get an error that Nomad could not be found, then your Vagrant box
+may not have provisioned correctly. Check for any error messages that may have
+been emitted during `vagrant up`. You can always [destroy the box][destroy] and
+re-create it.
+
+## Next Steps
+
+Nomad is installed. Let's [start Nomad](/intro/getting-started/running)!
+
+[binary-instructions]: /docs/install#precompiled-binaries
+[destroy]: https://www.vagrantup.com/docs/cli/destroy.html
+[install-instructions]: https://www.vagrantup.com/docs/installation/
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/jobs.mdx b/content/nomad/v0.12.x/content/intro/getting-started/jobs.mdx
new file mode 100644
index 0000000000..a61a6dadfa
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/jobs.mdx
@@ -0,0 +1,345 @@
+---
+layout: intro
+page_title: Jobs
+sidebar_title: Jobs
+description: 'Learn how to submit, modify and stop jobs in Nomad.'
+---
+
+# Jobs
+
+Jobs are the primary configuration that users interact with when using
+Nomad. A job is a declarative specification of tasks that Nomad should run.
+Jobs have a globally unique name, one or many task groups, which are themselves
+collections of one or many tasks.
+
+The format of the jobs is documented in the [job specification][jobspec]. They
+can either be specified in [HashiCorp Configuration Language][hcl] or JSON,
+however we recommend only using JSON when the configuration is generated by a machine.
+
+## Running a Job
+
+To get started, we will use the [`job init` command](/docs/commands/job/init) which
+generates a skeleton job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+You can view the contents of this file by running `cat example.nomad`. In this
+example job file, we have declared a single task 'redis' which is using
+the Docker driver to run the task. The primary way you interact with Nomad
+is with the [`job run` command](/docs/commands/job/run). The `run` command takes
+a job file and registers it with Nomad. This is used both to register new
+jobs and to update existing jobs.
+
+We can register our example job now:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "13ebb66d"
+    Evaluation triggered by job "example"
+    Allocation "883269bf" created: node "e42d6f19", group "cache"
+    Evaluation within deployment: "b0a84e74"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "13ebb66d" finished with status "complete"
+```
+
+Anytime a job is updated, Nomad creates an evaluation to determine what
+actions need to take place. In this case, because this is a new job, Nomad has
+determined that an allocation should be created and has scheduled it on our
+local agent.
+
+To inspect the status of our job we use the [`status` command](/docs/commands/status):
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 10/31/17 22:58:40 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = b0a84e74
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+8ba85cef  171a583b  cache       0        run      running  5m ago   5m ago
+```
+
+Here we can see that the result of our evaluation was the creation of an
+allocation that is now running on the local node.
+
+An allocation represents an instance of Task Group placed on a node. To inspect
+an allocation we use the [`alloc status` command](/docs/commands/alloc/status):
+
+```shell-session
+$ nomad alloc status 8ba85cef
+ID                  = 8ba85cef
+Eval ID             = 13ebb66d
+Name                = example.cache[0]
+Node ID             = e42d6f19
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created             = 5m ago
+Modified            = 5m ago
+Deployment ID       = fa882a5b
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+8/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:22672
+
+Task Events:
+Started At     = 10/31/17 22:58:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+10/31/17 22:58:49 UTC  Started     Task started by client
+10/31/17 22:58:40 UTC  Driver      Downloading image redis:3.2
+10/31/17 22:58:40 UTC  Task Setup  Building Task Directory
+10/31/17 22:58:40 UTC  Received    Task received by client
+```
+
+We can see that Nomad reports the state of the allocation as well as its
+current resource usage. By supplying the `-stats` flag, more detailed resource
+usage statistics will be reported.
+
+To see the logs of a task, we can use the [`logs` command](/docs/commands/alloc/logs):
+
+````shell-session
+$ nomad alloc logs 8ba85cef redis
+                 _._
+            _.-``__ ''-._
+       _.-``    `.  `_.  ''-._           Redis 3.2.1 (00000000/0) 64 bit
+   .-`` .-```.  ```\/    _.,_ ''-._
+  (    '      ,       .-`  | `,    )     Running in standalone mode
+  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
+  |    `-._   `._    /     _.-'    |     PID: 1
+   `-._    `-._  `-./  _.-'    _.-'
+  |`-._`-._    `-.__.-'    _.-'_.-'|
+  |    `-._`-._        _.-'_.-'    |           http://redis.io
+   `-._    `-._`-.__.-'_.-'    _.-'
+  |`-._`-._    `-.__.-'    _.-'_.-'|
+  |    `-._`-._        _.-'_.-'    |
+   `-._    `-._`-.__.-'_.-'    _.-'
+       `-._    `-.__.-'    _.-'
+           `-._        _.-'
+               `-.__.-'
+...
+````
+
+## Modifying a Job
+
+The definition of a job is not static, and is meant to be updated over time.
+You may update a job to change the docker container, to update the application version,
+or to change the count of a task group to scale with load.
+
+For now, edit the `example.nomad` file to update the count and set it to 3:
+
+```
+# The "count" parameter specifies the number of the task groups that should
+# be running under this group. This value must be non-negative and defaults
+# to 1.
+count = 3
+```
+
+Once you have finished modifying the job specification, use the [`job plan`
+command](/docs/commands/job/plan) to invoke a dry-run of the scheduler to see
+what would happen if you ran the updated job:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (2 create, 1 in-place update)
+  +/- Count: "1" => "3" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+We can see that the scheduler detected the change in count and informs us that
+it will cause 2 new instances to be created. The in-place update that will
+occur is to push the updated job specification to the existing allocation and
+will not cause any service interruption. We can then run the job with the run
+command the `plan` emitted.
+
+By running with the `-check-index` flag, Nomad checks that the job has not
+been modified since the plan was run. This is useful if multiple people are
+interacting with the job at the same time to ensure the job hasn't changed
+before you apply your modifications.
+
+```shell-session
+$ nomad job run -check-index 7 example.nomad
+==> Monitoring evaluation "93d16471"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "0d06e1b6"
+    Allocation "3249e320" created: node "e42d6f19", group "cache"
+    Allocation "453b210f" created: node "e42d6f19", group "cache"
+    Allocation "883269bf" modified: node "e42d6f19", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "93d16471" finished with status "complete"
+```
+
+Because we set the count of the task group to three, Nomad created two
+additional allocations to get to the desired state. It is idempotent to
+run the same job specification again and no new allocations will be created.
+
+Now, let's try to do an application update. In this case, we will simply change
+the version of redis we want to run. Edit the `example.nomad` file and change
+the Docker image from "redis:3.2" to "redis:4.0":
+
+```
+# Configure Docker driver with the image
+config {
+    image = "redis:4.0"
+}
+```
+
+We can run `plan` again to see what will happen if we submit this change:
+
+```text
++/- Job: "example"
++/- Task Group: "cache" (1 create/destroy update, 2 ignore)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 1127
+To submit the job with version verification run:
+
+nomad job run -check-index 1127 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+The plan output shows us that one allocation will be updated and that the other
+two will be ignored. This is due to the `max_parallel` setting in the `update`
+stanza, which is set to 1 to instruct Nomad to perform only a single change at
+a time.
+
+Once ready, use `run` to push the updated specification:
+
+```shell-session
+$ nomad job run example.nomad
+==> Monitoring evaluation "293b313a"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "f4047b3a"
+    Allocation "27bd4a41" created: node "e42d6f19", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "293b313a" finished with status "complete"
+```
+
+After running, the rolling upgrade can be followed by running `nomad status` and
+watching the deployed count.
+
+We can see that Nomad handled the update in three phases, only updating a single
+allocation in each phase and waiting for it to be healthy for `min_healthy_time`
+of 10 seconds before moving on to the next. The update strategy can be
+configured, but rolling updates makes it easy to upgrade an application at large
+scale.
+
+## Stopping a Job
+
+So far we've created, run and modified a job. The final step in a job lifecycle
+is stopping the job. This is done with the [`job stop` command](/docs/commands/job/stop):
+
+```shell-session
+$ nomad job stop example
+==> Monitoring evaluation "6d4cd6ca"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "f4047b3a"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6d4cd6ca" finished with status "complete"
+```
+
+When we stop a job, it creates an evaluation which is used to stop all
+the existing allocations. If we now query the job status, we can see it is
+now marked as `dead (stopped)`, indicating that the job has been stopped and
+Nomad is no longer running it:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 11/01/17 17:30:40 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = dead (stopped)
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         0        0       6         0
+
+Latest Deployment
+ID          = f4047b3a
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        3       3        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+8ace140d  2cfe061e  cache       2        stop     complete  5m ago     5m ago
+8af5330a  2cfe061e  cache       2        stop     complete  6m ago     6m ago
+df50c3ae  2cfe061e  cache       2        stop     complete  6m ago     6m ago
+```
+
+If we wanted to start the job again, we could simply `run` it again.
+
+## Next Steps
+
+Users of Nomad primarily interact with jobs, and we've now seen
+how to create and scale our job, perform an application update,
+and do a job tear down. Next we will add another Nomad
+client to [create our first cluster](/intro/getting-started/cluster)
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/next-steps.mdx b/content/nomad/v0.12.x/content/intro/getting-started/next-steps.mdx
new file mode 100644
index 0000000000..9be8741103
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/next-steps.mdx
@@ -0,0 +1,32 @@
+---
+layout: intro
+page_title: Next Steps
+sidebar_title: Next Steps
+description: >-
+  After completing the getting started guide, learn about what to do next with
+  Nomad.
+---
+
+# Next Steps
+
+That concludes the getting started guide for Nomad. Hopefully you are
+excited about the possibilities of Nomad and ready to put this knowledge
+to use to improve your environment.
+
+We've covered the basics of all the core features of Nomad in this guide.
+We recommend exploring the following resources as next steps.
+
+- [HashiCorp Learn Guides](http://learn/hashicorp.com/nomad) - The Guides provide best practices and
+  guidance for using and operating Nomad in a real-world production setting.
+
+- [Docs](/docs) - The Docs provide detailed reference information
+  all available features and options of Nomad.
+
+- [Job Lifecycle](https://learn.hashicorp.com/nomad?track=managing-jobs#operations-and-development) - Additional details
+  specific to running a job in production.
+
+- [Creating a Cluster](https://learn.hashicorp.com/nomad/operating-nomad/clustering) - Additional
+  details on creating a production worthy Nomad Cluster.
+
+- [Example Terraform configuration](https://github.com/hashicorp/nomad/tree/master/terraform) -
+  Use Terraform to automatically provision a cluster in AWS.
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/running.mdx b/content/nomad/v0.12.x/content/intro/getting-started/running.mdx
new file mode 100644
index 0000000000..b722e423be
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/running.mdx
@@ -0,0 +1,145 @@
+---
+layout: intro
+page_title: Running Nomad
+sidebar_title: Running Nomad
+description: 'Learn about the Nomad agent, and the lifecycle of running and stopping.'
+---
+
+# Running Nomad
+
+Nomad relies on a long running agent on every machine in the cluster.
+The agent can run either in server or client mode. Each region must
+have at least one server, though a cluster of 3 or 5 servers is recommended.
+A single server deployment is _**highly**_ discouraged as data loss is inevitable
+in a failure scenario.
+
+All other agents run in client mode. A Nomad client is a very lightweight
+process that registers the host machine, performs heartbeating, and runs the tasks
+that are assigned to it by the servers. The agent must be run on every node that
+is part of the cluster so that the servers can assign work to those machines.
+
+## Starting the Agent
+
+For simplicity, we will run a single Nomad agent in development mode. This mode
+is used to quickly start an agent that is acting as a client and server to test
+job configurations or prototype interactions. It should _**not**_ be used in
+production as it does not persist state.
+
+```shell-session
+$ sudo nomad agent -dev
+
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: nomad.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+    [INFO] client: using alloc directory /tmp/NomadClient599911093
+    [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state
+    [INFO] nomad: adding server nomad.global (Addr: 127.0.0.1:4647) (DC: dc1)
+    [WARN] fingerprint.network: Ethtool not found, checking /sys/net speed file
+    [WARN] raft: Heartbeat timeout reached, starting election
+    [INFO] raft: Node at 127.0.0.1:4647 [Candidate] entering Candidate state
+    [DEBUG] raft: Votes needed: 1
+    [DEBUG] raft: Vote granted. Tally: 1
+    [INFO] raft: Election won. Tally: 1
+    [INFO] raft: Node at 127.0.0.1:4647 [Leader] entering Leader state
+    [INFO] raft: Disabling EnableSingleNode (bootstrap)
+    [DEBUG] raft: Node 127.0.0.1:4647 updated peer set (2): [127.0.0.1:4647]
+    [INFO] nomad: cluster leadership acquired
+    [DEBUG] client: applied fingerprints [arch cpu host memory storage network]
+    [DEBUG] client: available drivers [docker exec java]
+    [DEBUG] client: node registration complete
+    [DEBUG] client: updated allocations at index 1 (0 allocs)
+    [DEBUG] client: allocs: (added 0) (removed 0) (updated 0) (ignore 0)
+    [DEBUG] client: state updated to ready
+```
+
+As you can see, the Nomad agent has started and has output some log
+data. From the log data, you can see that our agent is running in both
+client and server mode, and has claimed leadership of the cluster.
+Additionally, the local client has been registered and marked as ready.
+
+-> **Note:** Typically any agent running in client mode must be run with root level
+privilege. Nomad makes use of operating system primitives for resource isolation
+which require elevated permissions. The agent will function as non-root, but
+certain task drivers will not be available.
+
+## Cluster Nodes
+
+If you run [`nomad node status`](/docs/commands/node/status) in another
+terminal, you can see the registered nodes of the Nomad cluster:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+171a583b  dc1  nomad  <none>  false  eligible     ready
+```
+
+The output shows our Node ID, which is a randomly generated UUID,
+its datacenter, node name, node class, drain mode and current status.
+We can see that our node is in the ready state, and task draining is
+currently off.
+
+The agent is also running in server mode, which means it is part of
+the [gossip protocol](/docs/internals/gossip) used to connect all
+the server instances together. We can view the members of the gossip
+ring using the [`server members`](/docs/commands/server/members) command:
+
+```shell-session
+$ nomad server members
+Name          Address    Port  Status  Leader  Protocol  Build  Datacenter  Region
+nomad.global  127.0.0.1  4648  alive   true    2         0.7.0  dc1         global
+```
+
+The output shows our own agent, the address it is running on, its
+health state, some version information, and the datacenter and region.
+Additional metadata can be viewed by providing the `-detailed` flag.
+
+## Stopping the Agent ((#stopping))
+
+You can use `Ctrl-C` (the interrupt signal) to halt the agent.
+By default, all signals will cause the agent to forcefully shutdown.
+The agent [can be configured](/docs/configuration#leave_on_terminate) to
+gracefully leave on either the interrupt or terminate signals.
+
+After interrupting the agent, you should see it leave the cluster
+and shut down:
+
+```
+^C==> Caught signal: interrupt
+    [DEBUG] http: Shutting down http server
+    [INFO] agent: requesting shutdown
+    [INFO] client: shutting down
+    [INFO] nomad: shutting down server
+    [WARN] serf: Shutdown without a Leave
+    [INFO] agent: shutdown complete
+```
+
+By gracefully leaving, Nomad clients update their status to prevent
+further tasks from being scheduled and to start migrating any tasks that are
+already assigned. Nomad servers notify their peers they intend to leave.
+When a server leaves, replication to that server stops. If a server fails,
+replication continues to be attempted until the node recovers. Nomad will
+automatically try to reconnect to _failed_ nodes, allowing it to recover from
+certain network conditions, while _left_ nodes are no longer contacted.
+
+If an agent is operating as a server, [`leave_on_terminate`](/docs/configuration#leave_on_terminate) should only
+be set if the server will never rejoin the cluster again. The default value of `false` for `leave_on_terminate` and `leave_on_interrupt`
+work well for most scenarios. If Nomad servers are part of an auto scaling group where new servers are brought up to replace
+failed servers, using graceful leave avoids causing a potential availability outage affecting the [consensus protocol](/docs/internals/consensus).
+As of Nomad 0.8, Nomad includes Autopilot which automatically removes failed or dead servers. This allows the operator to skip setting `leave_on_terminate`.
+
+If a server does forcefully exit and will not be returning into service, the
+[`server force-leave` command](/docs/commands/server/force-leave) should
+be used to force the server from a _failed_ to a _left_ state.
+
+## Next Steps
+
+If you shut down the development Nomad agent as instructed above, ensure that it is back up and running again and let's try to [run a job](/intro/getting-started/jobs)!
diff --git a/content/nomad/v0.12.x/content/intro/getting-started/ui.mdx b/content/nomad/v0.12.x/content/intro/getting-started/ui.mdx
new file mode 100644
index 0000000000..bb4a499746
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/getting-started/ui.mdx
@@ -0,0 +1,63 @@
+---
+layout: intro
+page_title: Web UI
+sidebar_title: Web UI
+description: 'Visit the Nomad Web UI to inspect jobs, allocations, and more.'
+---
+
+# Web UI
+
+At this point we have a fully functioning cluster with a job running in it. We have
+learned how to inspect a job using `nomad status`, next we'll learn how to inspect
+a job in the web client.
+
+## Opening the Web UI
+
+As long as Nomad is running, the Nomad UI is also running. It is hosted at the same address
+and port as the Nomad HTTP API under the `/ui` namespace.
+
+With Nomad running, visit `http://localhost:4646` to open the Nomad UI.
+
+[![Nomad UI Jobs List][img-jobs-list]][img-jobs-list]
+
+If you can't connect it's possible that Vagrant was unable to properly map the
+port from your host to the VM. Your `vagrant up` output will contain the new
+port mapping:
+
+```text
+==> default: Fixed port collision for 4646 => 4646. Now on port 2200.
+```
+
+In the case above you would connect to `http://localhost:2200` instead.
+
+## Inspecting a Job
+
+You should be automatically redirected to `/ui/jobs` upon visiting the UI in your browser. This
+pages lists all jobs known to Nomad, regardless of status. Click the `example` job to inspect it.
+
+[![Nomad UI Job Detail][img-job-detail]][img-job-detail]
+
+The job detail page shows pertinent information about the job, including overall status as well as
+allocation statuses broken down by task group. It is similar to the `nomad status` CLI command.
+
+Click on the `cache` task group to drill into the task group detail page. This page lists each allocation
+for the task group.
+
+[![Nomad UI Task Group Detail][img-task-group-detail]][img-task-group-detail]
+
+Click on the allocation in the allocations table. This page lists all tasks for an allocation as well
+as the recent events for each task. It is similar to the `nomad alloc status` command.
+
+[![Nomad UI Alloc Status][img-alloc-status]][img-alloc-status]
+
+The Nomad UI offers a friendly and visual alternative experience to the CLI.
+
+## Next Steps
+
+We've now concluded the getting started guide, however there are a number
+of [next steps](/intro/getting-started/next-steps) to get started with Nomad.
+
+[img-jobs-list]: /img/intro-ui-jobs-list.png
+[img-job-detail]: /img/intro-ui-job-detail.png
+[img-task-group-detail]: /img/intro-ui-task-group-detail.png
+[img-alloc-status]: /img/intro-ui-alloc-status.png
diff --git a/content/nomad/v0.12.x/content/intro/index.mdx b/content/nomad/v0.12.x/content/intro/index.mdx
new file mode 100644
index 0000000000..6af8cf4750
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/index.mdx
@@ -0,0 +1,57 @@
+---
+layout: intro
+page_title: Introduction
+sidebar_title: What is Nomad?
+description: >-
+  Welcome to the intro guide to Nomad! This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad! This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/docs) and [HashiCorp Learn guides](https://learn.hashicorp.com/nomad) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/intro/use-cases) and [Who Uses Nomad](/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v0.12.x/content/intro/use-cases.mdx b/content/nomad/v0.12.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..2512e4c77f
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/use-cases.mdx
@@ -0,0 +1,67 @@
+---
+layout: intro
+page_title: Use Cases
+sidebar_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker)
+and integrates seamlessly with [Consul](/docs/integrations/consul-integration)
+and [Vault](/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utlization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs, [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs, and [Spark](https://github.com/hashicorp/nomad-spark)
+workloads. Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v0.12.x/content/intro/vs/ecs.mdx b/content/nomad/v0.12.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..47006274e2
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+sidebar_title: AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v0.12.x/content/intro/vs/index.mdx b/content/nomad/v0.12.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..c75add3cbe
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/vs/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+sidebar_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v0.12.x/content/intro/vs/kubernetes.mdx b/content/nomad/v0.12.x/content/intro/vs/kubernetes.mdx
new file mode 100644
index 0000000000..ff6938ac91
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/vs/kubernetes.mdx
@@ -0,0 +1,39 @@
+---
+layout: intro
+page_title: Nomad vs. Kubernetes
+sidebar_title: Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native
+Computing Foundation (CNCF) and developed by Google, Red Hat, CoreOS and many others. Kubernetes aims to provide all the features needed to run Docker or Rkt-based applications including cluster management,
+scheduling, service discovery, monitoring, secrets management and more.
+
+Nomad only aims to provide cluster management and scheduling and is designed
+with the Unix philosophy of having a small scope while composing with tools like [Consul](https://www.consul.io)
+for service discovery and [Vault](https://www.vaultproject.io) for secret management.
+
+While Kubernetes is specifically focused on Docker, Nomad is more general purpose.
+Nomad supports virtualized, containerized and standalone applications, including Docker.
+Nomad is designed with extensible drivers and support will be extended to all
+common drivers.
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating
+services which together provide the full functionality. Coordination and
+storage is provided by etcd at the core. The state is wrapped by API controllers
+which are consumed by other services that provide higher level APIs for features
+like scheduling. Kubernetes supports running in a highly available
+configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines a lightweight resource manager and a sophisticated scheduler
+into a single system. By default, Nomad is distributed, highly available,
+and operationally simple.
+
+Kubernetes documentation states they can support clusters greater than 5,000 nodes
+and they support a multi-AZ/multi-region configuration. Nomad has been proven to scale
+to cluster sizes that exceed 10,000 nodes in real-world production environments. Nomad
+also natively supports multi-datacenter and multi-region configurations.
diff --git a/content/nomad/v0.12.x/content/intro/vs/mesos.mdx b/content/nomad/v0.12.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..6d957ab418
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,36 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+sidebar_title: Mesos & Marathon
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v0.12.x/content/intro/vs/terraform.mdx b/content/nomad/v0.12.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..e1a2f839ee
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,32 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+sidebar_title: Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v0.12.x/content/intro/who-uses-nomad.mdx b/content/nomad/v0.12.x/content/intro/who-uses-nomad.mdx
new file mode 100644
index 0000000000..2ea6d2935d
--- /dev/null
+++ b/content/nomad/v0.12.x/content/intro/who-uses-nomad.mdx
@@ -0,0 +1,115 @@
+---
+layout: intro
+page_title: Who Uses Nomad
+sidebar_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, CloudFlare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### CloudFlare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a $1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+-  [Eslevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v0.12.x/content/partials/envvars.mdx b/content/nomad/v0.12.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..a3cd5c23a3
--- /dev/null
+++ b/content/nomad/v0.12.x/content/partials/envvars.mdx
@@ -0,0 +1,249 @@
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_DIR</code>
+      </td>
+      <td>
+        The path to the shared <code>alloc/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">
+          here for more
+        </a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_DIR</code>
+      </td>
+      <td>
+        The path to the task <code>local/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_SECRETS_DIR</code>
+      </td>
+      <td>
+        Path to the task&lsquo;s secrets directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_MEMORY_LIMIT</code>
+      </td>
+      <td>Memory limit in MB for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_CPU_LIMIT</code>
+      </td>
+      <td>CPU limit in MHz for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_ID</code>
+      </td>
+      <td>Allocation ID of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_NAME</code>
+      </td>
+      <td>Allocation name of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_INDEX</code>
+      </td>
+      <td>
+        Allocation index; useful to distinguish instances of task groups. From 0
+        to (count - 1). The index is unique within a given version of a job, but
+        canaries or failed tasks in a deployment may reuse the index.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_NAME</code>
+      </td>
+      <td>Task&lsquo;s name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_GROUP_NAME</code>
+      </td>
+      <td>Group&lsquo;s name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_NAME</code>
+      </td>
+      <td>Job&lsquo;s name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_DC</code>
+      </td>
+      <td>Datacenter in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_NAMESPACE</code>
+      </td>
+      <td>Namespace in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_REGION</code>
+      </td>
+      <td>Region in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_META_&lt;key&gt;</code>
+      </td>
+      <td>
+        The metadata value given by <code>key</code> on the task&lsquo;s
+        metadata. Note that this is different from
+        <a href="/docs/runtime/interpolation#node-variables-">
+          <code>$&#123;meta.&lt;key&gt;&#125;</code>
+        </a>
+        which are keys in the node&lsquo;s metadata.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>VAULT_TOKEN</code>
+      </td>
+      <td>
+        The task&lsquo;s Vault token. See
+        <a href="/docs/vault-integration">Vault Integration</a>
+        for more details
+      </td>
+    </tr>
+    <tr>
+      <th colspan="2">Network-related Variables</th>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code>. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code>. Driver-specified port when a
+        port map is used, otherwise the host&lsquo;s static or dynamic port
+        allocation. Services should bind to this port. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code>. See
+        <a href="/docs/job-specification/network#mapped-ports">here</a> for more
+        information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group. Driver-specified port when a port map is
+        used, otherwise the host&lsquo;s static or dynamic port allocation.
+        Services should bind to this port.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code> and
+        <code>task</code> for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code> and <code>task</code>
+        for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_IP_&lt;service&gt;</code>
+      </td>
+      <td>
+        IP for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_PORT_&lt;service&gt;</code>
+      </td>
+      <td>
+        Port for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> for the given <code>service</code> when
+        defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ENVOY_ADMIN_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Local address <code>localhost:Port</code> for the admin port of the
+        envoy sidecar for the given <code>service</code> when defined as a
+        Consul Connect enabled service.
+      </td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v0.12.x/content/partials/general_options.mdx b/content/nomad/v0.12.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..71106ce559
--- /dev/null
+++ b/content/nomad/v0.12.x/content/partials/general_options.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the NOMAD_NAMESPACE environment variable if set.
+  If set to '*', job and alloc subcommands query all namespacecs authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v0.12.x/data/alert-banner.js b/content/nomad/v0.12.x/data/alert-banner.js
new file mode 100644
index 0000000000..41a3e7b7cb
--- /dev/null
+++ b/content/nomad/v0.12.x/data/alert-banner.js
@@ -0,0 +1,10 @@
+export const ALERT_BANNER_ACTIVE = true
+
+// https://github.com/hashicorp/web-components/tree/master/packages/alert-banner
+export default {
+  url:
+    'https://www.hashicorp.com/blog/announcing-general-availability-of-hashicorp-nomad-0-12',
+  tag: 'ANNOUNCING',
+  text:
+    'Nomad 0.12 is now generally available, which includes 15+ new features and our breakthrough Multi-Cluster Deployment. Learn more!',
+}
diff --git a/content/nomad/v0.12.x/data/api-docs-nav-data.json b/content/nomad/v0.12.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..0f37dfb664
--- /dev/null
+++ b/content/nomad/v0.12.x/data/api-docs-nav-data.json
@@ -0,0 +1,112 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "path": "operator"
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies <sup>Beta</sup>",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v0.12.x/data/docs-nav-data.json b/content/nomad/v0.12.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..404d357646
--- /dev/null
+++ b/content/nomad/v0.12.x/data/docs-nav-data.json
@@ -0,0 +1,1065 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/quickstart"
+          }
+        ]
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Hardware Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Set Server & Client Nodes",
+            "path": "install/production/nomad-agent"
+          },
+          {
+            "title": "Reference Architecture",
+            "path": "install/production/reference-architecture"
+          },
+          {
+            "title": "Reference Install Guide",
+            "path": "install/production/deployment-guide"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Connect",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Internals",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "internals"
+      },
+      {
+        "title": "Architecture",
+        "path": "internals/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "internals/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "internals/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "internals/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "internals/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "internals/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "internals/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "internals/consensus"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "internals/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "internals/security"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval status",
+        "path": "commands/eval-status"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "put",
+            "path": "commands/license/put"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "autopilot get-config",
+            "path": "commands/operator/autopilot-get-config"
+          },
+          {
+            "title": "autopilot set-config",
+            "path": "commands/operator/autopilot-set-config"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "raft list-peers",
+            "path": "commands/operator/raft-list-peers"
+          },
+          {
+            "title": "raft remove-peer",
+            "path": "commands/operator/raft-remove-peer"
+          },
+          {
+            "title": "snapshot agent",
+            "path": "commands/operator/snapshot-agent"
+          },
+          {
+            "title": "snapshot inspect",
+            "path": "commands/operator/snapshot-inspect"
+          },
+          {
+            "title": "snapshot restore",
+            "path": "commands/operator/snapshot-restore"
+          },
+          {
+            "title": "snapshot save",
+            "path": "commands/operator/snapshot-save"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin <sup>Beta</sup>",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion <sup>Beta</sup>",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling <sup>Beta</sup>",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Qemu",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/external"
+          },
+          {
+            "title": "Containerd",
+            "path": "drivers/external/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/external/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "path": "drivers/external/jail-task-driver"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/external/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/external/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/external/rkt"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/external/singularity"
+          },
+          {
+            "title": "Systemd-Nspawn",
+            "path": "drivers/external/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/external/iis"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "path": "devices/community"
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Agent",
+        "path": "autoscaling/agent"
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "path": "autoscaling/plugins/apm"
+          },
+          {
+            "title": "Strategy",
+            "path": "autoscaling/plugins/strategy"
+          },
+          {
+            "title": "Target",
+            "path": "autoscaling/plugins/target"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "path": "autoscaling/internals/checks"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Telemetry",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "telemetry"
+      },
+      {
+        "title": "Metrics",
+        "path": "telemetry/metrics"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
\ No newline at end of file
diff --git a/content/nomad/v0.12.x/data/guides-navigation.js b/content/nomad/v0.12.x/data/guides-navigation.js
new file mode 100644
index 0000000000..aea152ecbf
--- /dev/null
+++ b/content/nomad/v0.12.x/data/guides-navigation.js
@@ -0,0 +1,100 @@
+// The root folder for this documentation category is `pages/guides`
+//
+// - A string refers to the name of a file
+// - A "category" value refers to the name of a directory
+// - All directories must have an "index.mdx" file to serve as
+//   the landing page for the category
+
+export default [
+  {
+    category: 'install',
+    content: [
+      { category: 'quickstart' },
+      {
+        category: 'production',
+        content: [
+          'requirements',
+          'nomad-agent',
+          'reference-architecture',
+          'deployment-guide'
+        ]
+      },
+      'windows-service'
+    ]
+  },
+  { category: 'upgrade', content: ['upgrade-specific'] },
+  {
+    category: 'integrations',
+    content: ['consul-integration', 'consul-connect', 'vault-integration']
+  },
+  '-----------',
+  {
+    category: 'operating-a-job',
+    content: [
+      'configuring-tasks',
+      'submitting-jobs',
+      'inspecting-state',
+      'accessing-logs',
+      'resource-utilization',
+      {
+        category: 'update-strategies',
+        content: [
+          'rolling-upgrades',
+          'blue-green-and-canary-deployments',
+          'handling-signals'
+        ]
+      },
+      {
+        category: 'failure-handling-strategies',
+        content: ['restart', 'check-restart', 'reschedule']
+      },
+      {
+        category: 'advanced-scheduling',
+        content: ['affinity', 'spread', 'preemption-service-batch']
+      },
+      { category: 'external', content: ['lxc'] }
+    ]
+  },
+  {
+    category: 'operations',
+    content: [
+      {
+        category: 'cluster',
+        content: ['manual', 'automatic', 'cloud_auto_join']
+      },
+      'federation',
+      'node-draining',
+      'outage',
+      { category: 'monitoring-and-alerting', content: ['prometheus-metrics'] },
+      'autopilot'
+    ]
+  },
+
+  {
+    category: 'security',
+    content: ['encryption', 'acl', 'securing-nomad', 'vault-pki-integration']
+  },
+  { category: 'stateful-workloads' },
+  {
+    category: 'analytical-workloads',
+    content: [
+      {
+        category: 'spark',
+        content: [
+          'pre',
+          'customizing',
+          'resource',
+          'dynamic',
+          'submit',
+          'hdfs',
+          'monitoring',
+          'configuration'
+        ]
+      }
+    ]
+  },
+
+  { category: 'load-balancing' },
+  { category: 'governance-and-policy', content: [] },
+  { category: 'web-ui', content: [] }
+]
diff --git a/content/nomad/v0.12.x/data/intro-nav-data.json b/content/nomad/v0.12.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..50d1264416
--- /dev/null
+++ b/content/nomad/v0.12.x/data/intro-nav-data.json
@@ -0,0 +1,64 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "Kubernetes",
+        "path": "kubernetes"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "getting-started"
+      },
+      {
+        "title": "Running Nomad",
+        "path": "getting-started/running"
+      },
+      {
+        "title": "Jobs",
+        "path": "getting-started/jobs"
+      },
+      {
+        "title": "Clustering",
+        "path": "getting-started/cluster"
+      },
+      {
+        "title": "Web UI",
+        "path": "getting-started/ui"
+      },
+      {
+        "title": "Next Steps",
+        "path": "getting-started/next-steps"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v0.12.x/data/subnav.js b/content/nomad/v0.12.x/data/subnav.js
new file mode 100644
index 0000000000..50574d3419
--- /dev/null
+++ b/content/nomad/v0.12.x/data/subnav.js
@@ -0,0 +1,46 @@
+export default [
+  { text: 'Overview', url: '/', type: 'inbound' },
+  {
+    text: 'Use Cases',
+    submenu: [
+      {
+        text: 'Simple Container Orchestration',
+        url: '/use-cases/simple-container-orchestration',
+      },
+      {
+        text: 'Non-Containerized Application Orchestration',
+        url: '/use-cases/non-containerized-application-orchestration',
+      },
+      {
+        text: 'Automated Service Networking with Consul',
+        url: '/use-cases/automated-service-networking-with-consul',
+      },
+    ],
+  },
+  {
+    text: 'Enterprise',
+    url: 'https://www.hashicorp.com/products/nomad/',
+    type: 'outbound',
+  },
+  'divider',
+  {
+    text: 'Tutorials',
+    url: 'https://learn.hashicorp.com/nomad',
+    type: 'outbound',
+  },
+  {
+    text: 'Docs',
+    url: '/docs',
+    type: 'inbound',
+  },
+  {
+    text: 'API',
+    url: '/api-docs',
+    type: 'inbound',
+  },
+  {
+    text: 'Resources',
+    url: '/resources',
+    type: 'inbound',
+  },
+]
diff --git a/content/nomad/v0.12.x/data/version.js b/content/nomad/v0.12.x/data/version.js
new file mode 100644
index 0000000000..e45b172468
--- /dev/null
+++ b/content/nomad/v0.12.x/data/version.js
@@ -0,0 +1 @@
+export default '0.12.3'
diff --git a/content/nomad/v0.12.x/img/acl.jpg b/content/nomad/v0.12.x/img/acl.jpg
new file mode 100644
index 0000000000..c892dd3928
Binary files /dev/null and b/content/nomad/v0.12.x/img/acl.jpg differ
diff --git a/content/nomad/v0.12.x/img/active-alert.png b/content/nomad/v0.12.x/img/active-alert.png
new file mode 100644
index 0000000000..65dcc51fe6
Binary files /dev/null and b/content/nomad/v0.12.x/img/active-alert.png differ
diff --git a/content/nomad/v0.12.x/img/alertmanager-webui.png b/content/nomad/v0.12.x/img/alertmanager-webui.png
new file mode 100644
index 0000000000..13691f6f72
Binary files /dev/null and b/content/nomad/v0.12.x/img/alertmanager-webui.png differ
diff --git a/content/nomad/v0.12.x/img/alerts.png b/content/nomad/v0.12.x/img/alerts.png
new file mode 100644
index 0000000000..b1ef6df853
Binary files /dev/null and b/content/nomad/v0.12.x/img/alerts.png differ
diff --git a/content/nomad/v0.12.x/img/count-dashboard.png b/content/nomad/v0.12.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v0.12.x/img/count-dashboard.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/android-chrome-192x192.png b/content/nomad/v0.12.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/android-chrome-512x512.png b/content/nomad/v0.12.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/apple-touch-icon.png b/content/nomad/v0.12.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/favicon-16x16.png b/content/nomad/v0.12.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/favicon-194x194.png b/content/nomad/v0.12.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/favicon-32x32.png b/content/nomad/v0.12.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/favicon.ico b/content/nomad/v0.12.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v0.12.x/img/favicons/mstile-144x144.png b/content/nomad/v0.12.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/mstile-150x150.png b/content/nomad/v0.12.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/mstile-310x150.png b/content/nomad/v0.12.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/mstile-310x310.png b/content/nomad/v0.12.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/mstile-70x70.png b/content/nomad/v0.12.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v0.12.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v0.12.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v0.12.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v0.12.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-binpacking.svg b/content/nomad/v0.12.x/img/feature-binpacking.svg
new file mode 100644
index 0000000000..de1e3e7ee2
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-binpacking.svg
@@ -0,0 +1,60 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1557 543">
+  <g fill="none" fill-rule="evenodd">
+    <g fill="#FFF" fill-rule="nonzero">
+      <path fill-opacity=".8" d="M1196.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1176.672 88.016 1134 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1171.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1308.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1288.672 88.016 1246 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1283.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1420.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1400.672 88.016 1358 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1395.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1532.328 125.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1512.672 88.016 1470 112.672l28.787 16.918 5.836-3.557 14.147 7.9V117.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1507.295 140.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1140.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1120.672 177.016 1078 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1115.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1252.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1232.672 177.016 1190 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1227.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1364.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1344.672 177.016 1302 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1339.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1476.328 214.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1456.672 177.016 1414 201.672l28.787 16.918 5.836-3.557 14.147 7.9V206.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1451.295 229.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1084.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1064.672 266.016 1022 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1059.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1196.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1176.672 266.016 1134 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1171.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1308.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1288.672 266.016 1246 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1283.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1420.328 303.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1400.672 266.016 1358 290.672l28.787 16.918 5.836-3.557 14.147 7.9V295.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1395.295 318.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1028.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1008.672 355.016 966 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1003.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623H966v49.115l43.033 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1140.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1120.672 355.016 1078 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1115.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1252.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1232.672 355.016 1190 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1227.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+      <path fill-opacity=".8" d="M1364.328 392.82v16.31l-11.36 6.575-7.935-4.918v42.59h.23l42.803-24.59v-49.115l-.804-.016"/>
+      <path d="M1344.672 355.016 1302 379.672l28.787 16.918 5.836-3.557 14.147 7.9V384.54l13.558-8.146v16.427l23.738-13.14v-.065"/>
+      <path d="M1339.295 407.508v16.377l-12.918 8.197v-32.787l4.902-3-29.04-16.623h-.24v49.115l43.03 24.59v-42.59"/>
+    </g>
+    <g fill="#FFF" fill-rule="nonzero">
+      <path d="M611 204a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 611 204m-453 86a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 158 290M57 250a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 57 250m-45 82a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 12 332m245 12a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 257 344m439 110a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 696 454M378 121a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 378 121m305 252a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 683 373m-262 44a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 421 417M253 171a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 253 171m209 78a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 462 249M124 539a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 124 539m187-370a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 311 169m-178 89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 133 258m441 257a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 574 515M5 407a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 5 407M361 59a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 361 59m25 157a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 386 216m-97 244a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 289 460m-31-161a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 258 299m217-56a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 243M79 411a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 79 411M647 75a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 647 75m-33 80a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 614 155m39 324a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 653 479M484 125a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 484 125m-96 231a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 388 356m-89-96a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 299 260m21 0a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 320 260m80-98a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 400 162M183 373a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 183 373M630 67a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 630 67M194 392a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 194 392m-72 126a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 122 518m235-314a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 357 204M99 329a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 99 329m449 128a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 548 457m110-299a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 658 158m-278-4a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 380 154m-205 62a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 175 216m157-31a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 332 185M98 490a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 98 490m563-103a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 661 387M475 532a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 532M335 402a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 335 402m55-3a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 390 399"/>
+      <path d="M649 481a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 649 481m22-105a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 671 376M42 38a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 42 38m268 495a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 310 533M154 92a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 154 92m224 139a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 378 231m250 80a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 628 311m-112-59a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 516 252M387 542a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 387 542m-84-265a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 303 277m-176-94a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 127 183m447 180a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 574 363m-1 180a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 573 543m-24-190a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 549 353M62 119a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 62 119m535-39a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 597 80m-103 0a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 494 80M25 217a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 25 217M338 48a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 338 48M82 51a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 82 51m441 375a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 523 426m-243-89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 280 337m99-226a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 379 111m36 413a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 415 524M311 129a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 311 129m66 364a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 377 493m162-236a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 539 257M90 398a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 90 398M608 83a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 608 83M70 184a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 70 184m355 139a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 425 323M144 476a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 144 476m451-140a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 595 336m-180 47a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 415 383m283-157a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 698 226M590 96a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 590 96m49-35a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 639 61m0 85a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 639 146m-252-10a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 387 136m236 363a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 623 499M87 509a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 87 509m163-342a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 250 167M85 10a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 85 10m482 451a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 567 461m98 25a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 665 486M160 338a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 160 338M69 535a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 69 535m25-332a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 94 203m381-20a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 475 183m-43-89a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 432 94m-70 232a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 362 326m127-25a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 489 301m-287 12a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 202 313m454-84a5 5 0 0 0 3.536-1.464 5.004 5.004 0 0 0 0-7.072 5.004 5.004 0 0 0-7.072 0 5.004 5.004 0 0 0 0 7.072A5 5 0 0 0 656 229"/>
+    </g>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="3" d="M767.5 271.5h208"/>
+    <path fill="#FFF" d="M989 271.5 964 284v-25"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-blue-green.svg b/content/nomad/v0.12.x/img/feature-blue-green.svg
new file mode 100644
index 0000000000..0e38fe6763
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-blue-green.svg
@@ -0,0 +1,37 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path d="m17.484 1.02-16.29 9.473 16.29 9.474 16.162-9.56"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M17.484.037 0 10.194v20.27l11.94 6.915v-.985l-11.087-6.4V11.303l16.204 9.388v19.42l.64.385 17.27-10.03v-20.27zm0 19.93-16.29-9.474 16.29-9.474 16.162 9.386-16.162 9.56zm16.63 10.03L18.55 39l-.64.384V20.692l16.205-9.56z"/>
+    <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+      <text font-size="12" transform="translate(43 2)">
+        <tspan x="0" y="31">web-app:1.0</tspan>
+      </text>
+      <text font-size="18" transform="translate(43 2)">
+        <tspan x="0" y="15">group.blue</tspan>
+      </text>
+    </g>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m255.484 1.02-16.29 9.473 16.29 9.474 16.162-9.56"/>
+      <path fill-rule="nonzero" d="M255.484.037 238 10.194v20.27l11.94 6.915v-.985l-11.087-6.4V11.303l16.204 9.388v19.42l.64.385 17.27-10.03v-20.27L255.485.037zm0 19.93-16.29-9.474 16.29-9.474 16.162 9.386-16.162 9.56zm16.63 10.03L256.55 39l-.64.384V20.692l16.205-9.56v18.864z"/>
+      <g font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+        <text font-size="12" transform="translate(281 2)">
+          <tspan x="0" y="31">web-app:1.1</tspan>
+        </text>
+        <text font-size="18" transform="translate(281 2)">
+          <tspan x="0" y="15">group.green</tspan>
+        </text>
+      </g>
+    </g>
+    <path stroke="#FFF" stroke-width="5" d="M81.5 49C47.534 49 20 76.534 20 110.5S47.534 172 81.5 172s61.5-27.534 61.5-61.5a61.7 61.7 0 0 0-1.72-14.51"/>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M140.247 92.25c-7.342-23.662-28.587-41.206-54.184-43.083"/>
+    <text fill="#FFF" font-family="Courier-Bold, Courier" font-size="30" font-weight="bold" transform="translate(20 49)">
+      <tspan x="25.494" y="73">8/10</tspan>
+    </text>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M318.5 49c-33.966 0-61.5 27.534-61.5 61.5s27.534 61.5 61.5 61.5 61.5-27.534 61.5-61.5a61.7 61.7 0 0 0-1.72-14.51"/>
+    <path stroke="#FFF" stroke-width="5" d="M377.247 92.25c-7.342-23.662-28.587-41.206-54.184-43.083"/>
+    <text fill="#FFF" font-family="Courier-Bold, Courier" font-size="30" font-weight="bold" transform="translate(257 49)">
+      <tspan x="25.494" y="73">2/10</tspan>
+    </text>
+    <path stroke="#FFF" stroke-linecap="square" d="M202.5 66.41v89.18"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-flexible-workloads.svg b/content/nomad/v0.12.x/img/feature-flexible-workloads.svg
new file mode 100644
index 0000000000..63883b34c0
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-flexible-workloads.svg
@@ -0,0 +1,49 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 3324 402">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#979797" stroke-linecap="square" stroke-width="2" d="M2204.45 1v400"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1245.42 211.35c.36 7.42 7.76 4 11.12 1.67 3.18-2.2 4.12-.37 4.4-4.7.18-2.87.5-5.72.35-8.6-4.9-.42-10.1.72-14.1 3.6-2.1 1.47-5.9 6.2-1.9 8.04"/>
+    <path fill="#C6B198" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1245.42 211.35c1.07-.4 2.22-.68 2.95-1.66"/>
+    <path fill="#6AD7E5" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1262.54 123c-28.4-7.97-7.28-44.1 15.5-29.23l-15.5 29.24zm126.13-31.94c22.47-15.78 42.77 19.82 16.66 28.78z"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1393.5 302.62c5.7 3.53 16.14 14.2 7.58 19.4-8.23 7.52-12.83-8.28-20.06-10.47 3.1-4.22 7.06-8.07 12.48-8.93z"/>
+    <path stroke="#000" stroke-linecap="round" stroke-width="3" d="M1401.08 322c-1.27-2.52-1.7-5.46-3.82-7.5"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1291.53 314.7c-6.7 1.03-10.47 7.07-16.05 10.14-5.27 3.14-7.28-1-7.76-1.85-.82-.4-.75.3-2.02-1-4.88-7.7 5.08-13.4 10.27-17.2 7.22-1.5 11.75 4.8 15.56 9.8z"/>
+    <path stroke="#000" stroke-linecap="round" stroke-width="3" d="M1267.73 323c.25-2.94 2.58-4.9 3.7-7.4"/>
+    <path fill="#000" fill-rule="nonzero" d="M1263.72 113.04c-3.74-1.98-6.5-4.67-4.2-9 2.12-4.02 6.06-3.58 9.8-1.6zm135.7-3.77c3.73-1.98 6.48-4.67 4.2-9-2.13-4-6.07-3.58-9.82-1.6l5.6 10.6z"/>
+    <path fill="#F6D2A2" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1425.2 210.4c-.37 7.43-7.78 4-11.13 1.68-3.2-2.2-4.12-.37-4.4-4.72-.18-2.85-.5-5.7-.35-8.57 4.8-.5 10.05.7 14 3.5 2.03 1.5 5.85 6.2 1.86 8"/>
+    <path fill="#C6B198" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1425.2 210.4c-1.1-.4-2.23-.67-2.96-1.65"/>
+    <path fill="#6AD7E5" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1332.46 76.06c28.42 0 55.06 4.06 68.95 31.37 12.5 30.6 8.1 63.6 10 95.95 1.7 27.77 5.3 59.86-7.6 85.6-13.5 27.08-47.4 33.9-75.3 32.9-21.9-.8-48.4-7.95-60.7-27.97-14.5-23.4-7.6-58.4-6.5-84.5 1.3-30.9-8.4-62 1.8-92.3 10.6-31.4 39.1-38.5 69.7-40.9"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="2.91" d="M1337.48 114.2c5.1 29.67 53.58 21.83 46.62-8.1-6.24-26.8-48.32-19.4-46.62 8.1"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="2.82" d="M1279.54 119c6.6 25.83 47.95 19.22 46.4-6.68-1.87-31.03-52.73-25.04-46.4 6.7"/>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1343.33 149.8c.02 3.86.87 8.2.14 12.3-.98 1.85-2.9 2.05-4.58 2.8-2.3-.36-4.3-1.87-5.2-4.02-.6-4.7.2-9.22.3-13.9l9.2 2.83z"/>
+    <g fill-rule="nonzero" transform="translate(1283.724 107.073)">
+      <ellipse cx="7.21" cy="7.72" fill="#000" rx="6.98" ry="7.56"/>
+      <ellipse cx="10.39" cy="9.43" fill="#FFF" rx="1.65" ry="1.92"/>
+    </g>
+    <g fill-rule="nonzero" transform="translate(1342.104 105.19)">
+      <ellipse cx="7.33" cy="7.72" fill="#000" rx="6.87" ry="7.56"/>
+      <ellipse cx="10.45" cy="9.43" fill="#FFF" rx="1.62" ry="1.92"/>
+    </g>
+    <path fill="#FFF" stroke="#000" stroke-linecap="round" stroke-width="3" d="M1323.37 149.4c-3.04 7.37 1.7 22.13 9.97 11.24-.6-4.68.22-9.22.37-13.9l-10.3 2.65z"/>
+    <g fill-rule="nonzero">
+      <path fill="#F6D2A2" stroke="#231F20" stroke-linecap="round" stroke-width="3" d="M1324.42 135.17c-5.68.48-10.32 7.23-7.37 12.57 3.9 7.08 12.63-.62 18.07.1 6.25.13 11.38 6.6 16.4 1.17 5.6-6-2.4-11.9-8.65-14.5l-18.45.8z"/>
+      <path fill="#000" d="M1323.7 134.87c-.42-9.83 18.33-11.06 20.55-2.83 2.2 8.2-19.62 10.12-20.55 2.83-.73-5.82 0 0 0 0"/>
+    </g>
+    <g fill-rule="nonzero">
+      <path fill="#5382A1" d="M968.58 268.63s-9.5 5.53 6.77 7.4c19.7 2.24 29.78 1.92 51.5-2.2 0 0 5.7 3.6 13.7 6.7-48.7 20.86-110.2-1.22-71.97-11.9m-5.95-27.24s-10.66 7.8 5.62 9.5c21.06 2.1 37.7 2.3 66.46-3.2 0 0 4 4 10.3 6.2-58.9 17.2-124.4 1.3-82.3-12.7z"/>
+      <path fill="#F8981D" d="M1012.8 195.2c12 13.8-3.16 26.25-3.16 26.25s30.47-15.73 16.47-35.43c-13-18.36-23-27.48 31.2-58.95 0 0-85.1 21.27-44.5 68.13"/>
+      <path fill="#5382A1" d="M1077.2 288.77s7.03 5.8-7.75 10.28c-28.1 8.52-117 11.1-141.68.34-8.87-3.9 7.77-9.3 13-10.4 5.46-1.2 8.58-1 8.58-1-9.87-7-63.8 13.6-27.4 19.5 99.3 16.1 180.98-7.3 155.23-18.9M973.15 213s-45.2 10.75-16 14.65c12.32 1.65 36.9 1.3 59.8-.64 18.7-1.5 37.5-4.9 37.5-4.9s-6.6 2.9-11.38 6.1c-45.9 12.1-134.6 6.5-109.06-5.9 21.6-10.4 39.2-9.2 39.2-9.2m81.1 45.3c46.7-24.2 25.1-47.5 10.1-44.4-3.7.8-5.3 1.4-5.3 1.4s1.4-2.1 4-3.1c29.8-10.4 52.7 30.9-9.6 47.3 0 0 .8-.6 1-1.2"/>
+      <path fill="#F8981D" d="M1026.1 76.27s25.86 25.85-24.5 65.6c-40.38 31.9-9.2 50.08-.02 70.86-23.57-21.27-40.86-40-29.26-57.42 17.03-25.5 64.22-37.9 53.8-79"/>
+      <path fill="#5382A1" d="M977.74 324.22c44.8 2.87 113.58-1.6 115.2-22.78 0 0-3.12 8.03-37 14.4-38.24 7.2-85.4 6.37-113.37 1.76 0 0 5.73 4.74 35.17 6.63z"/>
+    </g>
+    <g fill-rule="nonzero" transform="translate(509.063 76)">
+      <path fill="#54A3DA" d="M165.18 249.2s5.9-28.48 30.55-62.68c17.14-9.9 34.33-22.04 48.9-36.6 13.45-66.74-6.98-138.36-6.98-138.36S166.03-8.87 99.3 4.6C84.7 19.15 72.6 36.33 62.7 53.47 28.47 78.13 0 84.03 0 84.03s22.78 15.64 33.78 33.4c-4.7 13.5-6.9 22.2-6.9 22.2 1.8 8.33 7.06 18.05 14.34 27.86-5.03 3.9-10.92 8.1-17.3 11.5l-2.34 1.2c5.5 18.1 29.74 40.9 47.4 47 .37-.7.74-1.4 1.13-2.1 3.6-6.6 7.9-12.6 12-17.8 9.9 7.2 19.6 12.5 27.6 14.7 0 0 8.7-2.2 22.2-6.9 17.8 11 33.4 33.8 33.4 33.8zm-50.35-60.32c-10.16-4.4-23.65-15.24-32.85-24.45C69.54 152 62.8 141.4 60.2 134.8c4.38-14.88 21.16-66.32 53.4-100.9 38.86-6.6 79.58.5 97.3 4.4 3.9 17.72 11 58.45 4.4 97.32-34.37 32.06-85.06 48.73-100.48 53.26z"/>
+      <circle cx="148.9" cy="100.64" r="26.62" fill="#F1616E"/>
+    </g>
+    <path fill="#1869A5" fill-rule="nonzero" d="M203.38 191h37.13v-33.76h-37.1V191zm-43.88 0h37.13v-33.76H159.5zm-43.9 0h37.13v-33.76H115.6zm-43.88 0h37.15v-33.76H71.75V191zm-43.88 0h37.14v-33.76H27.85V191zm43.9-40.52h37.13v-33.75H71.75v33.75zm43.88 0h37.13v-33.75h-37.13zm43.88 0h37.13v-33.75H159.5zm0-40.5h37.13V76.22H159.5zm192.57 61.33c-8.1-5.4-26.74-7.4-41.08-4.7-1.9-13.5-9.4-25.2-23.1-35.8l-7.9-5.2-5.3 7.9c-6.8 10.2-10.1 24.2-9 37.7.5 4.8 2 13.3 6.9 20.7-4.9 2.7-14.5 6.3-27.2 6H1.4l-.5 2.8c-2.3 13.6-2.24 55.8 25.2 88.3 20.83 24.5 52.1 37 92.9 37 88.44 0 153.88-40.7 184.52-114.7 12.05.3 38 .1 51.32-25.4.35-.6 1.15-2.1 3.47-6.9l1.3-2.6-7.5-5z"/>
+    <path fill="#000" fill-rule="nonzero" d="M2559.34 269.98c-3.73 8.63-8.15 16.57-13.28 23.87-6.98 9.95-12.7 16.85-17.1 20.67-6.83 6.28-14.15 9.5-21.98 9.68-5.63 0-12.4-1.6-20.3-4.85-7.93-3.23-15.2-4.83-21.87-4.83-6.9 0-14.4 1.6-22.4 4.83-8 3.25-14.5 4.94-19.4 5.1-7.5.33-15-2.98-22.4-9.93-4.7-4.16-10.7-11.3-17.9-21.4-7.6-10.8-13.9-23.3-18.9-37.58-5.3-15.4-7.9-30.33-7.9-44.78 0-16.55 3.6-30.83 10.8-42.8 5.6-9.6 13.1-17.17 22.5-22.74 9.4-5.56 19.5-8.4 30.4-8.58 6 0 13.8 1.85 23.5 5.47 9.7 3.7 15.9 5.5 18.7 5.5 2 0 9-2.1 20.7-6.4 11.1-4 20.5-5.6 28.2-5 20.8 1.7 36.4 9.9 46.8 24.7-18.6 11.3-27.7 27.1-27.6 47.3.2 15.8 5.9 28.9 17.2 39.3 5.1 4.9 10.8 8.6 17.1 11.3-1.4 4-2.8 7.8-4.4 11.5zM2511.7 82.46c0 12.35-4.52 23.9-13.52 34.56-10.85 12.7-23.98 20.02-38.22 18.86-.18-1.48-.28-3.04-.28-4.68 0-11.85 5.16-24.54 14.33-34.92 4.6-5.25 10.4-9.62 17.5-13.1 7.1-3.43 13.7-5.33 20-5.66.2 1.65.3 3.3.3 4.94zm304.76 55.62c0 .83-.83.83-.83.83h-.82c-.8 0-.8-.8-1.6-1.6 0 0-.8-.8-.8-1.6s0-.8.8-.8l1.7.9c.9.8 1.7 1.7 1.7 2.5m-14.8-8.2c0-4.1-1.6-6.5-4.1-6.5 0 0 0 .8-.8.8v1.6h2.5c0 1.7.8 2.5.8 4.1h1.7m28.8-4.1c1.6 0 2.5 1.7 3.3 4.1h1.7c-.8-.8-.8-1.6-.8-2.4s0-1.7-.8-2.5-1.6-1.6-2.5-1.6c0 0-.8.9-1.6.9 0 .8.9.8.9 1.6m-24.7 13.2c-.8 0-.8 0-.8-.8s0-1.6.9-2.5c1.7 0 2.5-.8 2.5-.8.9 0 .9.9.9.9 0 .8-.8 1.7-2.5 3.3h-.8m-9-.8c-3.3-1.6-4.1-4.1-4.1-8.2 0-2.5 0-4.1 1.6-5.7.9-1.6 2.5-2.4 4.1-2.4 1.7 0 2.5.9 4.1 2.5.9 2.5 1.7 5 1.7 7.4v1.7h.8v-.9c.9 0 .9-1.7.9-5 0-2.5 0-4.9-1.7-7.4-1.6-2.5-3.3-4.1-6.6-4.1-2.4 0-4.9 1.7-5.7 4.1-1.6 3.3-2 5.8-2 9.9 0 3.3 1.2 6.6 4.5 9.9.8-.8 1.6-.8 2.5-1.7M2900 254.5c.8 0 .8-.3.8-1.04 0-1.8-.8-3.93-3.3-6.3-2.4-2.5-6.5-4.04-11.5-4.7-.8-.1-1.6-.1-1.6-.1-.8-.14-.8-.14-1.6-.14-.85-.06-2.5-.2-3.3-.4 2.45-7.64 3.3-14.4 3.3-20.3 0-8.2-1.67-13.95-4.96-18.9-3.3-4.9-6.6-7.4-10.7-8.2-.8.8-.8.8-.8 1.64 4.1 1.6 8.2 4.9 10.7 9.85 2.5 5.8 3.3 10.7 3.3 16.5 0 4.6-.8 11.4-4.1 20.2-3.3 1.3-6.6 4.4-9.1 9.2 0 .7 0 1.2.8 1.2 0 0 .8-.7 1.66-2.1 1.62-1.4 2.45-2.8 4.1-4.2 2.46-1.4 4.1-2.1 6.6-2.1 4.1 0 8.2.6 10.7 1.8 3.3 1.1 4.9 2.2 5.74 3.5.8 1.2 1.6 2.4 2.4 3.5 0 1 .8 1.5.8 1.5m-76-119.6c-.8-.8-.8-2.5-.8-4.1 0-3.3 0-4.9 1.65-7.4 1.6-1.6 3.3-2.4 4.9-2.4 2.4 0 4.1 1.7 5.7 3.3.8 2.5 1.6 4.1 1.6 6.6 0 4.1-1.7 6.6-5 7.4 0 0 .8.9 1.6.9 1.6 0 2.4.8 4.1 1.7.8-4.9 1.6-8.2 1.6-12.3 0-4.9-.8-8.2-2.5-10.7-2.5-2.4-5-3.2-8.3-3.2-2.5 0-5 .8-7.4 2.5-1.7 2.5-2.5 4.1-2.5 6.6 0 4.1.8 7.4 2.4 10.7.8 0 1.7.8 2.5.8m9.9 13.2c-10.7 7.4-19 10.7-25.5 10.7-5.8 0-11.5-2.4-16.5-6.5.8 1.7 1.6 3.3 2.4 4.1l4.9 5c3.3 3.3 7.4 4.9 11.5 4.9 5.8 0 12.4-3.3 20.6-9l7.4-4.95c1.6-1.6 3.3-3.3 3.3-5.7 0-.8 0-1.62-.9-1.62-.8-1.6-4.9-4.1-13.2-6.5-7.4-3.23-13.2-4.9-16.5-4.9-2.5 0-6.6 1.68-12.3 4.96-5 3.3-8.3 6.6-8.3 9.9 0 0 .82.8 1.64 2.46 4.9 4.1 9.85 6.56 14.8 6.56 6.6 0 14.8-3.3 25.5-11.5v1.6c.8 0 .8.8.8.8m18.9 166.17c3.3 6.2 9.06 9.3 15.64 9.3 1.6 0 3.3-.3 4.9-.8 1.7-.36 3.3-.9 4.1-1.6.86-.55 1.7-1.1 2.5-1.8 1.66-.56 1.66-1 2.5-1.4l14-12.1c3.3-2.6 6.55-4.9 10.7-6.9 3.25-1.96 6.54-3.3 8.2-4 2.45-.66 4.1-1.65 5.74-2.96.8-1.24 1.6-2.8 1.6-4.77 0-2.4-1.6-4.2-3.3-5.5-1.6-1.3-3.2-2.2-4.9-2.8-1.6-.6-3.3-1.9-5.7-4.1-1.7-2.13-3.3-5.1-4.1-9l-.9-4.8c-.8-2.2-.8-3.8-1.68-4.7 0-.25 0-.33-.8-.33s-2.5.7-3.3 2.1c-1.63 1.4-3.3 3-4.9 4.6-.8 1.7-3.3 3.1-5 4.5-2.5 1.4-4.94 2.2-6.6 2.2-6.56 0-9.85-1.8-12.3-5.33-1.64-2.6-2.46-5.62-3.3-9.1-1.6-1.4-2.45-2.1-4.1-2.1-4.1 0-5.75 4.3-5.75 12.9V292c0 .8-.8 2.4-.8 4.97-.8 2.6-.8 5.5-.8 8.7l-1.67 9.1v.2m-92.8 2.8c9.94 3.66 16 5.5 18.24 5.5 5.8 0 10.6-2.5 14.5-7.5.8-1.6.8-3.5.8-5.6 0-7.8-4.7-17.6-14-29.52l-5.6-7.5c-1.2-1.52-2.6-3.9-4.4-7.1-1.7-3.2-3.3-5.7-4.5-7.4-1-1.9-2.8-3.8-5-5.7-2.1-1.9-4.6-3.1-7.3-3.77-3.5.7-5.85 1.8-7 3.4-1.15 1.57-1.8 3.3-2 5.1-.2 1.74-.7 2.9-1.54 3.46-.82.5-2.22.9-4.1 1.35h-4.5c-4.3 0-7.3.5-8.83 1.3-2 2.4-3.1 5.1-3.1 8 0 1.3.3 3.5 1 6.7.7 3 1 5.5 1 7.2 0 3.3-1 6.7-3.1 10.1-2.1 3.5-3.1 6.2-3.1 8 .8 3.2 6.2 5.4 16.2 6.7q11.4 1.8 26.4 7.2zm5.5-101.23c2.96-7.4 5.9-12.3 8.8-15.6-.17-.8-.6-.8-1.24-.8l-.86-.86c-2.4 2.5-5.27 8.26-8.7 16.5-3.48 7.4-5.3 14.2-5.3 19.2 0 3.7.9 6.9 2.6 9.7 1.8 2.7 6.2 6.6 13.1 11.6l8.7 5.63c9.3 8.1 14.22 13.7 14.22 17 0 1.7-.9 3.5-3.3 5.4-1.7 2-3.9 3-5.8 3-.1 0-.2.2-.2.6 0 .1.8 1.8 2.52 5 3.5 4.7 10.9 7 20.7 7 18.1 0 32.1-7.4 42.8-22.2 0-4.1 0-6.7-.8-7.7v-4c0-5.3.8-9.3 2.43-12 1.7-2.6 3.3-3.8 5.8-3.8 1.7 0 3.3.6 5 1.8.8-6.3.8-11.8.8-16.7 0-7.5 0-13.6-1.6-19.4-.8-4.9-2.5-9-4.1-12.3l-4.9-7.4c-1.64-2.4-2.5-4.9-4.1-7.4-.83-3.3-1.65-5.7-1.65-9.8-2.5-4.2-4.2-8.3-6.6-12.4-1.7-4.1-3.3-8.3-5-11.5l-7.4 5.7c-8.2 5.7-14.8 8.2-20.56 8.2-4.95 0-9.06-.8-11.5-4.1l-4.96-4.2c0 2.5-.8 5.8-2.5 9l-5.2 9.8c-2.3 5.7-3.5 9-3.73 11.5-.33 1.6-.6 3.3-.74 3.3l-6.2 12.3c-6.7 12.3-10 23.7-10 33.2 0 1.9.1 3.8.5 5.8-3.7-2.6-5.6-6.1-5.6-10.7 0-5.7 1.5-11.9 4.5-19.3zm29.7 101.4c-4.13 4.7-8.73 7.3-15.15 7.3-4 0-10.4-1.6-18.9-4.7-8.64-2.94-16.3-5.2-23-6.7-.6-.2-2.1-.5-4.5-.87-2.3-.4-4.4-.74-6.3-1.12-1.7-.3-3.7-.9-5.8-1.6-2.04-.64-3.7-1.5-4.9-2.52-1.1-1-1.7-2.2-1.7-3.5q0-1.95.9-4.2c.53-.9 1.1-1.8 1.7-2.6.6-.9 1.1-1.7 1.4-2.5.5-.75.83-1.5 1.16-2.3.3-.75.63-1.5.8-2.4.16-.8.33-1.64.33-2.47 0-.8-.3-3.24-1-7.6-.66-4.3-1-7-1-8.13 0-3.6.8-6.5 2.7-8.56 1.8-2.03 3.53-3.1 5.34-3.1h9.5c.8 0 1.9-.4 3.67-1.4.6-1.3 1.1-2.4 1.4-3.4.4-1 .6-1.7.8-2.04.1-.47.3-.96.5-1.4.3-.55.7-1.2 1.3-1.87-.7-.8-1-1.9-1-3.2 0-.9 0-1.73.17-2.23 0-2.95 1.4-7.14 4.36-12.65l2.9-5.2c2.4-4.5 4.2-7.77 5.5-11.06 1.4-3.3 2.9-8.23 4.5-14.8 1.3-5.77 4.45-11.53 9.4-17.3l6.15-7.4c4.3-4.9 7.1-9 8.64-12.3 1.6-3.3 2.4-7.4 2.4-10.7 0-1.63-.4-6.56-1.3-14.8-.87-8.2-1.3-16.43-1.3-23.83 0-5.8.5-9.9 1.54-14s3-8.3 5.8-11.5c2.5-3.3 5.7-6.6 10.7-8.3 4.9-1.7 10.7-2.5 17.2-2.5 2.5 0 4.94 0 7.4.8 2.5 0 5.76.8 9.9 2.5 3.3 1.6 6.55 3.3 9 5.7 3.3 2.4 5.77 6.5 8.2 10.7 1.68 4.9 3.3 9.8 4.1 16.4.8 4.1.8 8.2 1.67 14 0 4.9.84 8.2.84 10.7.82 2.4.82 5.7 1.64 9.8.8 3.3 1.6 6.6 3.3 9.1 1.6 3.3 3.3 6.6 5.7 9.9 2.5 4.1 5.8 8.2 9.1 13.2 7.4 8.2 13.2 17.2 16.48 26.3 4.1 8.2 6.6 18.9 6.6 30.3 0 5.7-.8 11.2-2.5 16.5 1.64 0 2.5.7 3.3 1.8.8 1.2 1.6 3.6 2.46 7.5l.8 6.1c.8 1.8 1.64 3.5 4.1 5 1.65 1.5 3.3 2.7 5.8 3.7 1.6.8 4.1 2 5.7 3.4 1.64 1.7 2.46 3.4 2.46 5.2q0 4.2-2.4 6.3c-1.7 1.6-3.3 2.8-5.8 3.5-1.66.8-4.9 2.5-9.88 4.8-4.1 2.4-8.2 5.4-12.3 8.9l-8.3 7c-3.3 3.2-6.6 5.5-9.04 6.9-2.43 1.5-5.7 2.2-9 2.2l-5.77-.7c-6.5-1.7-10.7-5-13.1-10-13.2-1.6-23.9-2.3-30.45-2.3-10.7 0-18.9 1.4-24.7 4.3z"/>
+    <path fill="#00ADEF" fill-rule="nonzero" d="m3075 111.23 101.38-13.8.05 97.8-101.34.57-.1-84.57zm101.34 95.26.07 97.8-101.3-14v-84.6l101.3.6zm12.3-110.9 134.4-19.6v117.9l-134.4 1V95.6zm134.44 111.8-.03 117.4-134.43-19-.18-98.7 134.64.2z"/>
+    <path fill="#E25A1C" d="m2013.6 202.65-.8-1.75c-6-11.4-11.98-22.78-18.02-34.14-.6-1.14-.53-1.82.3-2.8 9.53-11.12 19-22.3 28.5-33.45.32-.3.62-.8.75-1.5l-8.32 2.2c-11.5 3.1-23 6.1-34.5 9.2-1 .3-1.5 0-2.1-.9-6.5-10.9-13.1-21.8-19.6-32.7-.3-.5-.7-1.1-1.4-1.6l-1.5 8.8-5.5 30.8c-.2 1.1-.4 2.2-.5 3.4-.1 1.1-.6 1.5-1.6 1.8-13.5 4.3-27.1 8.6-40.6 12.9-.6.2-1.2.5-1.8 1 11.1 4.4 22.2 8.8 33.5 13.3-.4.3-.7.6-1 .8l-20.7 13.5c-.8.6-1.5.6-2.4.2l-24.9-11.1c-3.7-1.6-7-3.8-9.6-7-5.9-7.2-4.7-15.4 3.2-20.4 2.6-1.6 5.5-2.9 8.4-3.8 13.3-4.4 26.6-8.5 40-12.7 1.2-.4 1.7-.9 1.9-2.1 1.8-10.3 3.6-20.5 5.5-30.8 1-5.5 1.5-11.1 4.2-16.1 1-1.9 2.3-3.8 3.7-5.4 5.3-5.9 12.7-6.1 18.3-.5 1.9 1.9 3.5 4.1 4.9 6.4 6.2 10 12.3 20.2 18.3 30.3.7 1.2 1.4 1.4 2.7 1.1 14.9-4 29.7-7.9 44.6-11.8 3.1-.8 6.2-1.1 9.3-.5 6.9 1.3 9.9 6.5 7.5 13.1-1 3.1-2.9 5.6-4.9 8l-31.2 36.6c-.8 1-.8 1.7-.3 2.8 6.3 11.7 12.4 23.5 18.6 35.2 1.5 2.8 2.6 5.7 2.7 9 .1 7.4-5.3 13.4-12.6 14.4-4 .6-7.8-.2-11.7-1.4-9.3-2.9-18.6-5.7-28-8.5-.8-.3-1.2-.6-1.3-1.5-1-6.6-2.2-13.1-3.4-19.7 0-.2.1-.4.1-.8l32.2 8.9"/>
+    <path fill="#3C3A3E" d="M1995.44 298.38c-8.4-.02-16.8-.06-25.2-.02-1.12 0-1.75-.32-2.37-1.27-9.95-15.2-19.94-30.3-29.93-45.5l-1.22-1.8-6.36 48.3h-22c.25-2.2.48-4.2.75-6.3l6.5-49.2c2.1-15.7 4.1-31.4 6.2-47.1.1-.5.4-1.1.8-1.3l22.8-14.7c.1-.1.3-.1.7-.2l-6.8 52.3.3.2 36.1-39.9 1 5.5c.9 5 1.7 10 2.6 14.9.2 1 0 1.6-.7 2.3-7.7 8-15.4 16.1-23.1 24.2l-1 1.1.7 1.1 39.8 55.8.9.9v.3m-261-48.3c-.3-1.7-.5-4.3-1.3-6.6-3.7-11.4-15.3-17.6-27.4-14.8-13.2 3.1-22.7 13.5-24 27-1 10 4.4 19.6 14.4 23.2 8.1 2.9 15.8 1.6 23.1-2.7 9.6-5.8 14.8-14.3 15.4-26.3zm-58.2 42.3c-.6 4.9-1.3 9.5-1.9 14.1l-2.4 18.4c0 .7-.3 1-1 1-6.1-.1-12.1 0-18.1-.1-.1 0-.2-.1-.6-.2l1.1-8.7 4.1-30.6c1.6-11.7 2.8-23.3 4.8-34.9 3.5-20.5 20.9-38.1 41.2-42.5 11.8-2.6 23.1-1.4 33.5 5.2 10.3 6.6 16.2 16.2 17.6 28.3 1.9 17.1-4.4 31.3-16.5 43-8 7.7-17.5 12.6-28.5 14.3-11.4 1.7-22-.2-31.6-6.9-.4-.3-.7-.5-1.3-.9zm-9.8-97.2-19.9 14.8c-1.1-1.7-2-3.4-3.1-4.9-2.9-4-6.4-7-11.5-7.3-4.2-.3-7.9 1.1-10.8 4.2-2.6 2.9-2.9 6.9-.5 10.1 2.7 3.5 5.6 6.8 8.6 10 5 5.4 10.2 10.5 15.1 16 4.5 4.9 8.1 10.4 9.2 17.2 1.3 8-.2 15.6-4 22.7-7 13-18 20.5-32.6 22.9-6.4 1-12.8.8-19.1-1-8.3-2.5-14.1-7.9-17.8-15.6-1.3-2.8-2.3-5.6-3.5-8.6 7.3-3.9 14.3-7.7 21.5-11.5.3.6.5 1.1.7 1.6 1.2 2.4 2.2 5 3.8 7.3 4.5 6.7 11.8 8.7 19.2 5.4 1.88-.9 3.7-2.1 5.2-3.4 4.7-4.3 5.6-10.1 2.1-15.4-2-3.1-4.52-5.8-7-8.6-5.9-6.5-12-12.8-17.72-19.5-4-4.6-6.66-9.9-7.5-16.1-.94-6.7.4-13 3.9-18.7 8.66-14 21.26-21.3 37.9-20.7 9.5.3 17.07 4.8 22.94 12.1 1.73 2.2 3.4 4.5 5.14 6.8m161 75.2c-1.1 8.5-2.2 16.5-3.25 24.5-.1.4-.4 1-.7 1.1-16.4 7.6-38 6.6-51.5-8.7-7.3-8.3-10.3-18-9.8-28.9 1-25.2 21.8-47.1 46.8-50.1 14.5-1.8 27.3 2.1 37.1 13.4 6.7 7.7 9.8 16.9 9.35 27-.3 6.7-1.3 13.4-2.2 20-1.15 9.5-2.44 18.9-3.7 28.33 0 .3-.1.63-.2 1.1h-20l.77-6.4c1.4-10.9 3-21.8 4.2-32.8.76-6.8.27-13.5-2.84-19.8-3.32-6.7-8.87-10.3-16.17-11.05-15.1-1.6-29.5 8.9-32.7 23.73-2.16 9.8 1.2 19.2 9 24.4 7.6 5.1 15.8 5.1 24.1 1.8 4.2-1.67 7.8-4.3 11.2-7.86m82.6-60.2-2.66 20.4h-12.3c-3.3 0-6.3 2.12-7.3 5.2-.4 1.2-.5 2.5-.7 3.73l-6.1 46.8-1.5 11.9H1859l1.1-8.8 4-30.4c1.2-8.7 2.2-17.5 3.6-26.2 1.84-11.7 13.5-22.1 25.3-22.6 5.62-.2 11.3 0 17.1 0"/>
+    <path fill="#3C3A3E" fill-rule="nonzero" d="M2019.52 298.25v-8.62h-.05l-3.38 8.62h-1.1l-3.4-8.62h-.1v8.62h-1.7v-10.33h2.6l3.1 7.85 3-7.85h2.6v10.33h-1.7zm-15-8.95v8.95h-1.7v-8.95h-3.23v-1.38h8.1v1.38h-3.3zM1693.9 180.54h5.08l-1.2-7.67-3.87 7.67zm5.87 4.95h-8.43l-2.67 5.2h-5.97l13.16-24.6h5.76l4.48 24.6h-5.53l-.8-5.3zm30.15-14.4h-3l-1.02 5.6h3c1.8 0 3.26-1.2 3.26-3.5 0-1.5-.9-2.3-2.24-2.3zm-7.27-5h7.88c4.13 0 7.02 2.4 7.02 6.7 0 5.3-3.76 8.9-9.12 8.9h-3.4l-1.6 9h-5.12l4.4-24.6zm32.35 14.4h5.05l-1.2-7.7-3.86 7.6zm5.85 4.9h-8.43l-2.67 5.2h-5.97l13.16-24.6h5.75l4.4 24.6h-5.6l-.8-5.3zm33.3 4.3c-1.73.8-3.64 1.2-5.56 1.2-6.6 0-10.6-4.9-10.6-11 0-7.8 6.5-14.4 14.4-14.4 1.9 0 3.7.4 5.1 1.2l-.7 5.9c-1.1-1.2-2.9-2-5-2-4.5 0-8.5 4-8.5 8.7 0 3.6 2.2 6.4 5.8 6.4 2.1 0 4.2-.9 5.6-2l-.7 5.8m31.4-9.1h-10.7l-1.8 9.9h-5.2l4.3-24.6h5.1l-1.8 9.7h10.7l1.7-9.7h5.1l-4.4 24.6h-5.2l1.7-9.9m18.8 9.9 4.3-24.6h13.7l-.9 4.9h-8.5l-.9 4.7h7.8l-.8 4.9h-7.8l-.9 4.9h8.5l-.9 4.9H1844"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-machine-failure.svg b/content/nomad/v0.12.x/img/feature-machine-failure.svg
new file mode 100644
index 0000000000..5f8302ca74
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-machine-failure.svg
@@ -0,0 +1,17 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path fill="#FFF" d="M268 84h100v21.212H268zm5.116 4.714v11.784h72.093V88.714h-72.1zm83.49 11.784c3.21 0 5.813-2.638 5.813-5.892s-2.61-5.892-5.82-5.892-5.82 2.638-5.82 5.892 2.603 5.892 5.814 5.892zM268 112.738h100v21.21H268v-21.212zm5.116 4.713v11.79h72.093v-11.79h-72.1zm83.49 11.79c3.21 0 5.813-2.64 5.813-5.89s-2.61-5.89-5.82-5.89-5.82 2.64-5.82 5.895 2.603 5.893 5.814 5.893zM268 141.48h100v21.212H268zm5.116 4.714v11.78h72.093v-11.78h-72.1zm83.49 11.78c3.21 0 5.813-2.64 5.813-5.89 0-3.255-2.61-5.89-5.82-5.89s-5.82 2.635-5.82 5.89c0 3.253 2.603 5.89 5.814 5.89z"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M185 123h27.538"/>
+    <path fill="#FFF" d="m221.5 123.037-10.5 6.038V117"/>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="M32 84h100v21.212H32zm5.116 4.714v11.784h72.093V88.714h-72.1zm83.49 11.784c3.21 0 5.813-2.638 5.813-5.892s-2.61-5.892-5.82-5.892-5.82 2.638-5.82 5.892 2.603 5.892 5.814 5.892zM32 112.738h100v21.21H32v-21.212zm5.116 4.713v11.79h72.093v-11.79h-72.1zm83.49 11.79c3.21 0 5.813-2.64 5.813-5.89s-2.61-5.89-5.82-5.89-5.82 2.64-5.82 5.895 2.603 5.893 5.814 5.893z"/>
+      <path d="M32 141.475h100v21.212H32zm5.116 4.714v11.78h72.093v-11.78h-72.1zm83.49 11.78c3.21 0 5.813-2.64 5.813-5.89 0-3.26-2.61-5.89-5.82-5.89s-5.82 2.63-5.82 5.89c0 3.25 2.603 5.89 5.814 5.89z"/>
+    </g>
+    <path d="m318.498 14.238-16.303 9.474 16.303 9.474 16.174-9.56"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M318.498 13.256 301 23.413v20.272l11.95 6.914v-.99l-11.096-6.4V24.52l16.217 9.39v19.42l.64.384L336 43.684v-20.27l-17.5-10.158zm0 19.93-16.303-9.474 16.303-9.474 16.174 9.39zm16.644 10.03-15.577 9.004-.64.384V33.912l16.217-9.56v18.863z"/>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m81.498 14.238-16.303 9.474 16.303 9.474 16.174-9.56"/>
+      <path fill-rule="nonzero" d="M81.498 13.256 64 23.413v20.272L75.95 50.6v-.983l-11.096-6.402V24.523l16.217 9.39V53.33l.64.384L99 43.684v-20.27l-17.5-10.16zm0 19.93-16.303-9.474 16.303-9.474 16.174 9.39zm16.644 10.03L82.565 52.22l-.64.384V33.912l16.217-9.56v18.863z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-public-private-clouds.svg b/content/nomad/v0.12.x/img/feature-public-private-clouds.svg
new file mode 100644
index 0000000000..860aa31fc2
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-public-private-clouds.svg
@@ -0,0 +1,147 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 3334 402">
+  <style xmlns="http://www.w3.org/2000/svg">
+    .aws-smile{fill-rule:evenodd;clip-rule:evenodd;fill:#f90}
+  </style>
+  <defs>
+    <path id="a" d="M.9 44.94h44.37V.04H.9z"/>
+    <path id="reuse-0" fill="#871F1C" d="m3235.02 188.7-19.15-18.98 28.98-2.56 19.1 18.95"/>
+    <path id="reuse-1" fill="#871F1C" d="m3125.3 198.37-19.15-19 28.98-2.56 19.1 19"/>
+    <path id="reuse-2" fill="#871F1C" d="m3234.87 136.06-19.16-19 29-2.55 19.1 19"/>
+    <path id="reuse-3" fill="#E63F46" d="m3134.52 98.47 120.3-10.52c5.1-.4 9.18 3.32 9.18 8.43l-.1 30.28-28.88 2.55v-5.7c0-2.6-2.14-4.6-4.74-4.4l-71.26 6.3c-2.65.2-4.84 2.6-4.84 5.2v5.8l-28.93 2.5.1-30.2c0-5.1 4.13-9.5 9.17-10z"/>
+    <radialGradient id="c" cx="14.38%" cy="6.75%" r="76.97%" fx="14.38%" fy="6.75%" gradientTransform="matrix(.89055 0 0 1 .016 0)">
+      <stop offset="0%" stop-color="#FFF" stop-opacity=".1"/>
+      <stop offset="100%" stop-color="#FFF" stop-opacity="0"/>
+    </radialGradient>
+  </defs>
+  <g fill="none" fill-rule="evenodd">
+    <path fill="#252f3e" d="M156.726 169.706c0 5 .54 9.052 1.487 12.024 1.08 2.973 2.431 6.215 4.323 9.728.675 1.08.945 2.161.945 3.107 0 1.35-.81 2.702-2.566 4.053l-8.512 5.674c-1.216.81-2.432 1.216-3.512 1.216-1.351 0-2.702-.676-4.053-1.892a42 42 0 0 1-4.864-6.35c-1.351-2.296-2.702-4.863-4.188-7.97q-15.807 18.644-39.72 18.644c-11.348 0-20.4-3.243-27.02-9.727s-9.997-15.132-9.997-25.94c0-11.483 4.053-20.805 12.294-27.83s19.184-10.538 33.1-10.538c4.593 0 9.322.405 14.32 1.08s10.133 1.757 15.537 2.973v-9.862c0-10.268-2.162-17.428-6.35-21.616-4.323-4.189-11.618-6.215-22.021-6.215-4.729 0-9.592.54-14.591 1.756s-9.862 2.702-14.59 4.594c-2.162.945-3.784 1.486-4.73 1.756s-1.62.405-2.16.405c-1.892 0-2.838-1.35-2.838-4.188v-6.62c0-2.161.27-3.783.946-4.728s1.891-1.892 3.783-2.837q7.092-3.648 17.022-6.08c6.62-1.756 13.645-2.567 21.076-2.567 16.077 0 27.83 3.648 35.396 10.943 7.43 7.296 11.213 18.374 11.213 33.235v43.772zm-54.85 20.536c4.458 0 9.051-.811 13.915-2.432s9.187-4.594 12.835-8.647c2.161-2.567 3.782-5.404 4.593-8.646s1.351-7.16 1.351-11.754v-5.674c-3.918-.946-8.106-1.756-12.43-2.297s-8.51-.81-12.699-.81c-9.051 0-15.671 1.756-20.13 5.404s-6.62 8.781-6.62 15.536c0 6.35 1.622 11.078 5 14.32 3.242 3.378 7.97 5 14.185 5m108.485 14.59c-2.432 0-4.053-.405-5.134-1.35-1.08-.811-2.026-2.703-2.837-5.27L170.642 93.78c-.81-2.702-1.216-4.458-1.216-5.404 0-2.161 1.08-3.377 3.242-3.377h13.24c2.567 0 4.323.405 5.269 1.35 1.08.811 1.891 2.703 2.702 5.27l22.697 89.436 21.075-89.436c.676-2.702 1.486-4.459 2.567-5.27S243.19 85 245.622 85h10.808c2.567 0 4.323.405 5.404 1.35 1.081.811 2.027 2.703 2.567 5.27l21.346 90.517 23.372-90.517c.81-2.702 1.756-4.459 2.702-5.27 1.081-.81 2.837-1.35 5.27-1.35h12.563c2.162 0 3.378 1.08 3.378 3.377 0 .676-.135 1.351-.27 2.162s-.406 1.891-.946 3.377l-32.56 104.433q-1.215 4.053-2.836 5.268c-1.081.811-2.837 1.351-5.134 1.351h-11.619c-2.567 0-4.323-.405-5.404-1.35s-2.026-2.702-2.567-5.404l-20.94-87.14-20.805 87.004c-.676 2.702-1.486 4.459-2.567 5.404s-2.972 1.351-5.404 1.351zm173.604 3.648c-7.026 0-14.05-.81-20.806-2.432s-12.024-3.377-15.536-5.404c-2.162-1.216-3.648-2.567-4.188-3.783s-.811-2.566-.811-3.782v-6.89c0-2.838 1.08-4.189 3.107-4.189q1.216 0 2.432.406c.81.27 2.027.81 3.378 1.35a73.5 73.5 0 0 0 14.86 4.73c5.405 1.08 10.673 1.62 16.077 1.62 8.512 0 15.132-1.486 19.725-4.458s7.025-7.295 7.025-12.834c0-3.783-1.216-6.89-3.647-9.457s-7.026-4.864-13.646-7.026l-19.589-6.079c-9.862-3.107-17.158-7.7-21.616-13.78-4.458-5.945-6.755-12.565-6.755-19.59q0-8.511 3.648-14.996c2.432-4.323 5.674-8.106 9.727-11.078 4.053-3.107 8.646-5.404 14.05-7.025s11.079-2.297 17.023-2.297c2.972 0 6.08.135 9.052.54 3.107.406 5.944.946 8.781 1.487 2.702.675 5.269 1.35 7.7 2.161q3.648 1.216 5.675 2.432c1.891 1.08 3.242 2.162 4.053 3.378q1.216 1.62 1.216 4.458v6.35c0 2.837-1.08 4.323-3.107 4.323-1.081 0-2.838-.54-5.134-1.621q-11.551-5.27-25.94-5.27c-7.7 0-13.78 1.216-17.968 3.783s-6.35 6.485-6.35 12.024c0 3.783 1.352 7.025 4.054 9.592s7.7 5.134 14.86 7.43l19.185 6.08c9.727 3.108 16.752 7.43 20.94 12.97s6.215 11.889 6.215 18.914c0 5.81-1.216 11.078-3.513 15.672-2.432 4.593-5.674 8.646-9.862 11.888-4.188 3.378-9.187 5.81-14.996 7.566-6.08 1.891-12.43 2.837-19.32 2.837"/>
+    <path d="M409.499 274.139c-44.448 32.829-109.026 50.257-164.552 50.257-77.818 0-147.935-28.776-200.894-76.602-4.188-3.783-.405-8.916 4.593-5.944 57.283 33.234 127.94 53.364 201.03 53.364 49.31 0 103.486-10.267 153.338-31.343 7.43-3.377 13.78 4.864 6.484 10.268" class="aws-smile"/>
+    <path d="M428.007 253.063c-5.674-7.295-37.558-3.512-52.013-1.756-4.324.54-4.999-3.243-1.081-6.08 25.399-17.833 67.145-12.7 72.008-6.755 4.864 6.08-1.35 47.826-25.128 67.82-3.648 3.108-7.16 1.487-5.54-2.566 5.404-13.375 17.428-43.503 11.754-50.663" class="aws-smile"/>
+    <path fill="#456DA7" d="M2066.18 245.7v-34.16c36.24 0 64.26-35.87 50.43-73.98-5.1-14.1-16.3-25.37-30.5-30.5-38.1-13.8-73.9 14.2-73.9 50.44H1978c0-57.73 55.78-102.7 116.28-83.8 26.44 8.25 47.45 29.26 55.7 55.7 18.9 60.5-26.06 116.3-83.8 116.3"/>
+    <path fill="#456DA7" d="M2066.26 211.62h-34.06v-34.04h34.05v34.04m-34.05 26.18h-26.16v-26.2h26.16v26.16"/>
+    <path fill="#456DA7" d="M2006.06 211.62h-21.93V189.7h21.93zm-107.9 71.52h4.4c4.9 0 8.95.96 12 2.87 3.4 2.1 5.14 6 5.14 11.6 0 5.9-1.73 9.9-5.14 12.2-2.94 2-6.95 3-11.94 3h-4.47v-29.5zm22.25-2.9c-4.4-3.08-9.9-4.64-16.4-4.64h-14v44.58h14c6.5 0 12-1.65 16.5-4.9 2.4-1.7 4.4-4.12 5.7-7.14 1.4-3 2-6.55 2-10.54 0-3.94-.6-7.43-2-10.4-1.3-2.97-3.2-5.3-5.6-6.95zm17.5-5.18c-1.3 0-2.5.47-3.4 1.4-.9.9-1.4 2.06-1.4 3.4 0 1.36.5 2.53 1.4 3.47 1 .95 2.2 1.43 3.5 1.43s2.5-.48 3.5-1.43c1-.94 1.5-2.1 1.5-3.45 0-1.36-.5-2.5-1.4-3.4-.9-.95-2.1-1.43-3.4-1.43"/>
+    <g transform="translate(1932.944 288)">
+      <mask id="b" fill="#fff">
+        <use xlink:href="#a"/>
+      </mask>
+      <path fill="#456DA7" d="M.9 32.18h7.9V.78H.9m34.52 21.17c-1.4 1.57-3.16 2.33-5.42 2.33-2.27 0-4.03-.76-5.4-2.33-1.35-1.55-2.04-3.62-2.04-6.14 0-2.5.7-4.6 2.05-6.2C26 8.1 27.8 7.3 30 7.3c2.3 0 4.06.77 5.4 2.35 1.4 1.58 2.1 3.67 2.1 6.2 0 2.54-.7 4.6-2.05 6.16zM37.5 3.4C35.1 1.3 32.44.06 29.56.06c-4.36 0-8 1.5-10.77 4.48-2.9 2.95-4.3 6.75-4.3 11.28 0 4.45 1.4 8.23 4.2 11.26 2.8 2.92 6.4 4.42 10.8 4.42 3 0 5.6-.85 7.8-2.52v.72c0 2.6-.7 4.63-2.1 6.02q-2.1 2.1-5.7 2.1c-3.7 0-6-1.43-8.7-5.2l-5.4 5.17.1.2c1.1 1.6 2.9 3.2 5.3 4.7 2.3 1.5 5.3 2.3 8.7 2.3 4.7 0 8.5-1.5 11.2-4.3C43.5 37.8 45 34 45 29.3V.8h-7.7v2.6z" mask="url(#b)"/>
+    </g>
+    <path fill="#456DA7" d="M1984.97 320.18h7.9v-31.4h-7.9m4.03-13.72c-1.35 0-2.52.47-3.45 1.4-.95.9-1.43 2.06-1.43 3.4 0 1.36.48 2.53 1.42 3.47.94.95 2.1 1.43 3.46 1.43 1.35 0 2.5-.48 3.46-1.43.94-.94 1.42-2.1 1.42-3.45 0-1.36-.48-2.5-1.42-3.4-.95-.95-2.1-1.43-3.46-1.43m21.2 5.25h-7.8v8.5h-4.5v7.2h4.5v13.03c0 4.08.83 7 2.44 8.68 1.6 1.7 4.47 2.6 8.5 2.6 1.3 0 2.6 0 3.85-.1h.3V313l-2.7.14c-1.9 0-3.2-.33-3.8-1-.6-.65-.9-2.05-.9-4.14v-12h7.3v-7.22h-7.4v-8.48m44.4 39.88h7.9V275.6h-7.9m87.7 33.36c-1.4 1.58-2.9 2.95-4 3.67-1.1.7-2.5 1.06-4.1 1.06-2.4 0-4.2-.9-5.7-2.6-1.6-1.8-2.3-4-2.3-6.7s.7-4.9 2.2-6.6c1.5-1.8 3.3-2.6 5.6-2.6 2.5 0 5.2 1.6 7.5 4.3l5.2-5c-3.4-4.5-7.8-6.5-13-6.5-4.4 0-8.1 1.6-11.2 4.7s-4.6 7-4.6 11.7 1.5 8.6 4.6 11.7c3 3.1 6.8 4.7 11.1 4.7 5.7 0 10.3-2.5 13.4-7l-5.2-5m15.1-8.4c.4-1.5 1.1-2.8 2-3.8 1-1.1 2.4-1.6 4.1-1.6 1.9 0 3.4.6 4.4 1.6.9 1 1.4 2.2 1.5 3.7h-12zm17.3-7.4c-1.1-1.6-2.7-2.8-4.6-3.8-1.9-.9-4.1-1.4-6.5-1.4q-6.6 0-10.8 4.8c-2.6 3.1-4 7.1-4 11.7 0 4.7 1.4 8.7 4.3 11.7s6.7 4.5 11.4 4.5c5.3 0 9.7-2.2 13-6.4l.2-.3-5.1-5-1.8 1.8c-.8.7-1.5 1.3-2.3 1.7-1.2.6-2.5.9-4 .9-2.2 0-4-.7-5.4-2-1.3-1.2-2-2.8-2.2-4.8h21l.1-2.9c0-2.1-.3-4-.8-5.9-.6-1.8-1.4-3.6-2.5-5.1zm16.3 15c.9-.7 2.1-1 3.8-1 1.9 0 3.9.4 6 1.1v3q-2.7 2.4-6.9 2.4c-1.4 0-2.5-.3-3.2-.9-.8-.6-1.1-1.3-1.1-2.3 0-1.1.4-1.9 1.3-2.5zm14-17.1c-2.4-2.1-5.7-3.1-9.9-3.1-2.6 0-5.1.6-7.3 1.7-2.1 1-4.1 2.8-5.4 5l.1.1 5 4.8c2.1-3.3 4.4-4.5 7.5-4.5 1.6 0 3 .5 4 1.3s1.5 1.9 1.5 3.3v1.5c-1.9-.6-3.9-.9-5.8-.9-3.9 0-7.1.9-9.5 2.7s-3.6 4.5-3.6 7.8c0 3 1 5.3 3.1 7.1 2.04 1.7 4.6 2.6 7.62 2.6 3 0 5.8-1.3 8.4-3.3v2.6h7.8v-20c0-3.8-1.2-6.8-3.6-8.9zm34 .6c-2.2-2.5-5.3-3.7-9.2-3.7-3.2 0-5.7.9-7.6 2.7v-2h-7.7V320h7.9v-17.3c0-2.4.5-4.3 1.7-5.63 1.1-1.34 2.6-2 4.6-2 1.8 0 3.1.6 4.1 1.8s1.5 2.86 1.5 4.93V320h7.9v-18.2c0-4.35-1.1-7.8-3.3-10.23m-208.5 16.5c.9-.64 2.1-.95 3.7-.95 1.9 0 3.9.4 6 1.14v3.1q-2.55 2.4-6.9 2.4c-1.4 0-2.4-.3-3.2-.9-.7-.6-1.1-1.35-1.1-2.3 0-1.08.4-1.9 1.3-2.5zm14-17.07c-2.4-2.03-5.7-3.07-9.9-3.07-2.6 0-5.1.57-7.3 1.7-2 1.04-4.1 2.77-5.3 5.03v.1l5 4.84c2-3.33 4.4-4.5 7.4-4.5 1.6 0 3 .46 4.1 1.33 1 .87 1.5 1.97 1.5 3.37v1.5c-2-.6-3.9-.9-5.8-.9-4 0-7.2.94-9.5 2.76-2.4 1.87-3.7 4.5-3.7 7.88 0 2.94 1 5.33 3.05 7.12 2.1 1.7 4.65 2.6 7.66 2.6 3 0 5.8-1.25 8.4-3.3v2.56h7.8V300c0-3.82-1.2-6.8-3.63-8.87zm46.5-8.1c-8.2 0-14.9 6.65-14.9 14.85s6.6 14.86 14.8 14.86 14.8-6.6 14.8-14.8-6.7-14.9-14.9-14.9zm0 37.83c-12.7 0-23-10.3-23-23s10.3-23 22.9-23 22.9 10.3 22.9 22.97c0 12.7-10.3 23-23 23z"/>
+    <g fill-rule="nonzero">
+      <path fill="#737373" d="M1183.98 298.84c.18-12.7 10.6-22.87 23.36-22.8 5.88-.1 11.55 2.17 15.73 6.3l-4.54 4.36c-3-2.88-7.02-4.48-11.2-4.45-4.4 0-8.65 1.77-11.74 4.9-3.1 3.15-4.8 7.4-4.7 11.8-.1 4.4 1.6 8.66 4.7 11.8 3 3.14 7.3 4.92 11.7 4.92 4.3.17 8.5-1.5 11.6-4.57 2-2.16 3.2-4.93 3.4-7.86h-15v-6.46h21q.3 1.95.3 3.9c.2 5.4-1.8 10.62-5.4 14.6-4.2 4.3-9.9 6.62-15.9 6.4-12.8.06-23.2-10.13-23.4-22.84zm61.72-6.57c-8.15.02-14.75 6.6-14.74 14.72 0 8.1 6.63 14.7 14.78 14.6 8.16 0 14.76-6.6 14.76-14.7.07-4-1.47-7.7-4.26-10.5-2.8-2.8-6.6-4.3-10.54-4.3zm0 23.6c-2.3-.04-4.5-1-6.1-2.7a8.5 8.5 0 0 1-2.3-6.22c0-4.62 3.77-8.36 8.4-8.36 4.64 0 8.4 3.7 8.4 8.3.12 2.3-.7 4.5-2.3 6.2-1.57 1.7-3.78 2.6-6.1 2.7v-.1zm32.35-23.6c-8.15.03-14.74 6.63-14.72 14.74.02 8.2 6.64 14.7 14.8 14.7 8.14 0 14.75-6.6 14.75-14.7.06-3.9-1.5-7.7-4.28-10.5-2.8-2.7-6.6-4.3-10.55-4.2zm0 23.6c-2.32-.04-4.52-1-6.1-2.7a8.5 8.5 0 0 1-2.3-6.22c0-4.62 3.76-8.36 8.4-8.36 4.63 0 8.4 3.7 8.4 8.3.1 2.3-.7 4.5-2.3 6.2-1.58 1.7-3.78 2.6-6.1 2.7v-.1zm39.67-22.7v2.4h-.22c-2-2.17-4.83-3.37-7.78-3.3-7.9.34-14.13 6.82-14.13 14.7 0 7.86 6.2 14.34 14.1 14.7 2.9.06 5.8-1.16 7.8-3.36h.2v2.2c0 5.6-3 8.7-7.9 8.7-3.3-.1-6.2-2.1-7.4-5.2l-5.6 2.4c2.1 5.3 7.3 8.8 13.1 8.7 7.6 0 14-4.4 14-15.3v-26.4h-6.3zm-7.44 22.72c-2.3-.1-4.46-1.1-6-2.7-1.56-1.7-2.36-3.9-2.23-6.2-.12-2.3.68-4.5 2.22-6.2a8.64 8.64 0 0 1 6-2.8c2.26.1 4.36 1.1 5.85 2.8 1.48 1.7 2.22 3.9 2.05 6.1.14 2.2-.62 4.4-2.1 6s-3.56 2.6-5.8 2.8zm18.08-38.3h6.5v43.1h-6.5zm24.24 38.3c-3.07.1-5.9-1.7-7.15-4.5l19.76-8.2-.6-1.7c-1.8-5.5-6.8-9.2-12.6-9.4-3.8 0-7.5 1.5-10.2 4.3-2.6 2.8-4 6.5-3.8 10.3-.1 3.9 1.5 7.7 4.2 10.4 2.8 2.8 6.6 4.3 10.5 4.2 5 0 9.6-2.4 12.3-6.5l-5-3.4c-1.5 2.5-4.2 4-7.2 4zm-.5-18c2.35-.3 4.58 1 5.6 3.1l-13.2 5.5c-.18-2.2.53-4.3 1.96-6 1.44-1.7 3.47-2.7 5.65-2.8zm25.92 2.9c-.13-5.6 2.02-10.9 5.95-14.9s9.3-6.1 14.87-6c5.63-.1 11.03 2.2 14.7 6.5l-3.57 3.4c-2.7-3.4-6.86-5.3-11.2-5.1-4.22-.1-8.3 1.6-11.25 4.6s-4.5 7.1-4.3 11.3c-.17 4.1 1.4 8.2 4.33 11.2 2.94 3 6.98 4.6 11.18 4.5 4.72 0 9.2-2 12.3-5.6l3.6 3.5c-5.77 6.5-14.96 8.7-23.1 5.7-8.12-3.1-13.5-10.8-13.5-19.5zm40.63 19.9v-39.9h5.15v39.9m32.03-13.7c0 7.7-6.3 14-14.1 14-7.77 0-14.07-6.3-14.07-14.1 0-7.7 6.3-14 14.08-14 7.8 0 14.1 6.3 14.1 14zm-5.15 0c.27-3.4-1.38-6.6-4.26-8.3s-6.5-1.8-9.38 0c-2.88 1.7-4.53 4.9-4.26 8.3 0 4.9 4.02 8.9 9 8.9 4.96 0 9-4 9-9h-.1zm28.4 13.6V317h-.33c-1.93 2.9-5.18 4.66-8.68 4.68-7.05 0-10.46-4.73-10.46-11.47v-16.7h5.2v15.9c0 5.6 2.8 7.7 6.8 7.7 4.3-.3 7.5-4 7.2-8.3v-15.1h5.2V321h-5l.1-.07zm9.07-13.7c-.35-7.6 5.4-14 12.98-14.6 3.7-.1 7.23 1.6 9.35 4.7h.22l-.22-3.8v-12.6h5.15v39.9h-4.93V317h-.22a10.99 10.99 0 0 1-9.35 4.68c-7.57-.54-13.33-7-12.98-14.54zm22.6 0c.4-3.4-1.2-6.6-4.05-8.4a8.77 8.77 0 0 0-9.35 0c-2.86 1.8-4.43 5-4.05 8.4-.38 3.3 1.2 6.6 4.05 8.4 2.86 1.7 6.5 1.7 9.35 0 2.86-1.8 4.44-5.1 4.06-8.4zm18.95 13.6v-39.9h13.65c3.25-.1 6.4 1.1 8.77 3.3 2.35 2.2 3.7 5.3 3.77 8.5-.1 3.2-1.5 6.3-3.8 8.6-2.4 2.2-5.5 3.4-8.8 3.3h-8.4v16.1h-5.2zm13.77-21.1c3.86 0 7-3.2 7-7 0-3.9-3.14-7-7-7h-8.76v13.9h8.8zm16.03 21v-39.9h5.15v39.9m4.42-8.3c0-6.2 5.6-9.6 12.03-9.6 2.58-.1 5.14.5 7.44 1.7v-.8c-.2-3.3-2.57-6-5.78-6.6-3.2-.7-6.46.9-7.93 3.8l-4.7-2c2.58-5 8.2-7.6 13.67-6.4 5.48 1.2 9.44 6 9.67 11.5v16.5h-4.93V317h-.22c-1.97 3.03-5.4 4.8-9 4.68-2.6.24-5.2-.6-7.14-2.34a9.26 9.26 0 0 1-3.1-6.8zm19.58-3.5c-1.93-1.3-4.23-1.9-6.54-1.8-5.4 0-7.5 2.8-7.5 5.4.4 2.7 2.9 4.6 5.6 4.3 4.5 0 8.2-3.5 8.4-8h.1zm12.23 3.4v-14h-4.8v-4.7h4.8V285h5.15v8.37h6.7v4.66h-6.7V312c0 3.06 1.3 4.46 3.7 4.46.8.03 1.6-.12 2.34-.45l1.8 4.4c-1.32.6-2.73.8-4.15.8-2.4.3-4.82-.5-6.55-2.2a7.94 7.94 0 0 1-2.3-6.5zm33.46-31.1-1.7 4.4c-.74-.4-1.54-.5-2.35-.5-1.3-.1-2.6.3-3.4 1.3-.9.9-1.4 2.1-1.2 3.4v3.5h6.9v4.7h-7.2v22.6h-5.2V298h-5.2v-4.7h5.1v-3.63c-.1-2.56.9-5.03 2.8-6.78 1.8-1.8 4.4-2.7 6.9-2.4 1.5-.1 2.9.1 4.3.7zm28 25.7c0 7.7-6.3 14-14.1 14-7.76 0-14.06-6.3-14.06-14 0-7.8 6.3-14 14.08-14s14.1 6.3 14.1 14zm-5.14 0c.27-3.4-1.38-6.6-4.26-8.4s-6.5-1.8-9.38 0c-2.88 1.7-4.53 5-4.26 8.3-.27 3.3 1.38 6.6 4.26 8.3s6.5 1.8 9.38 0 4.53-5 4.26-8.3zm9.3 13.6V293h4.92v4.47h.22a9.03 9.03 0 0 1 7.95-5.14c1.3 0 2.6.2 3.8.7l-2 4.8c-.9-.3-1.9-.47-2.8-.4-2 .06-3.9.96-5.3 2.46s-2 3.4-1.9 5.4v14.9h-5.1zm19.72-27.3h4.92v3.8h.26c1.88-2.8 5-4.5 8.4-4.7 3.7-.3 7.2 1.8 8.66 5.2 2.06-3.3 5.7-5.3 9.57-5.2 6.72 0 9.8 4.7 9.8 11.5v16.7h-5.15v-15.9c0-5.6-2.2-7.6-6.1-7.6-3.92 0-7 4.2-7 8.4v15.1h-5.15v-15.9c0-5.6-2.18-7.6-6.1-7.6-3.9 0-7 4.3-7 8.4v15.1h-5.14V293z"/>
+      <g transform="translate(1355.296 68)">
+        <path fill="#FBBC05" d="M131 143.23 110.5 179H56.8c-4.8 0-9.22-2.57-11.6-6.74l-43.43-76a13.44 13.44 0 0 1 0-13.36L18.3 54l20.4 35.58 30.75 53.65z"/>
+        <path fill="#EA4335" d="m200.22 96.3-43.44 75.96c-2.38 4.17-6.8 6.74-11.6 6.74H112l20.5-35.75 30.8-53.63L132.5 36h40.86l26.85 46.96c2.4 4.12 2.4 9.2.1 13.33z"/>
+        <path fill="#4285F4" d="M173 35.6H70.3L39.47 89 19 53.58 45.98 6.7C48.38 2.57 52.8 0 57.6 0h87.15c4.8 0 9.24 2.56 11.63 6.7z"/>
+        <path fill="#E0E0E0" d="m132 36 31 54-31 54H70L39 90l31-54z"/>
+        <circle cx="101" cy="90" r="27" fill="#FFF"/>
+        <path fill="#FFF" d="M45.98 7.8c2.4-4.15 6.83-6.7 11.63-6.7h87.2c4.8 0 9.3 2.56 11.7 6.7l16 27.7h.7L156.4 6.7A13.44 13.44 0 0 0 144.76 0H57.6C52.8 0 48.38 2.56 46 6.7L19 53.44l.32.56z" opacity=".2"/>
+        <path fill="#1A237E" fill-opacity=".2" d="m39 90 30.72-53.88H172l-.64-1.12H69.72L39 88.88"/>
+        <path fill="#FFF" d="M1.75 83.92 18.3 55.1l20.4 35.46L69.44 144h60.9l.65-1.12H69.4L38.7 89.45 18.3 54 1.74 82.8C.5 85-.1 87.5 0 90c.1-2.13.7-4.22 1.75-6.08" opacity=".2"/>
+        <path fill="#BF360C" d="M111.94 177.75H57.5c-4.8 0-9.24-2.6-11.63-6.8L2.35 94.33C1.3 92.43.7 90.33.6 88.16c-.1 2.55.5 5.08 1.75 7.3l43.52 76.63c2.4 4.2 6.82 6.8 11.62 6.8h53.8l.6-1.2z" opacity=".2"/>
+        <path fill="#3E2723" d="M163.6 89.72 133 36.22h-.63l30.57 53.5m36.73 5.54-43.17 75.8a13.25 13.25 0 0 1-11.52 6.72h-32.33l-.65 1.12h32.98c4.76 0 9.15-2.57 11.52-6.73l43.17-75.8c1.24-2.2 1.84-4.7 1.73-7.2-.1 2.13-.68 4.22-1.73 6.1z" opacity=".2"/>
+        <path fill="#FFF" d="m172.98 37.33 26.7 46.85a13.7 13.7 0 0 1 1.72 6.1c.12-2.53-.5-5.03-1.73-7.22l-26.7-46.85H132.4l.63 1.2m-.63 107 31.2-54.6h-.63l-30.58 53.5-20.4 35.6h.6" opacity=".2"/>
+        <path fill="url(#c)" d="M199.22 82.82 172.3 35.8 155.67 6.75C153.27 2.57 148.85 0 144.04 0h-87.1c-4.8 0-9.23 2.58-11.62 6.75L1.77 82.82a13.49 13.49 0 0 0 0 13.36l43.55 76.07c2.4 4.18 6.82 6.75 11.63 6.75h87.1c4.8 0 9.24-2.58 11.63-6.75l43.55-76.07a13.49 13.49 0 0 0 0-13.36z"/>
+      </g>
+    </g>
+    <g fill="#0078D7" fill-rule="nonzero">
+      <path d="M854.5 174.24c-7.03 0-13 4.2-15.8 10.16H738.24c-16.86 0-30.9-13.67-30.9-30.85 0-17.2 13.7-30.86 30.9-30.86h14.06c.7-3.6 1.75-7.1 3.16-10.2.7-1.1 1.05-2.5 1.75-3.5 7.1-12.3 20.4-20.4 35.5-20.4 13.7 0 25.7 6.6 33 16.5 4.3-2.1 8.8-3.5 13.4-4.6-9.9-15.4-26.7-25.5-46.4-25.5-22.8 0-42.5 14-50.5 34h-3.8c-24.6.3-44.6 20.3-44.6 44.9 0 24.5 20 44.5 44.6 44.5h100.8c2.8 5.9 8.8 10.1 15.8 10.1 9.5 0 17.2-7.7 17.2-17.2-.3-9.5-8.1-17.2-17.5-17.2z"/>
+      <path d="M907.98 251c30.14 0 56.07-25.66 56.07-55.88 0-30.23-24.18-54.48-54.32-54.83-10.16-20.4-30.83-34.1-55-34.1-29.45 0-53.97 20.7-59.93 48.1-14.37 1.4-26.63 9.1-34.34 20h73.23c4.9-6.3 12.6-10.2 21.3-10.2 15 0 27.3 12.3 27.3 27.4s-12.3 27.4-27.4 27.4c-8.8 0-16.1-3.9-21.4-10.2H752c3.16 23.2 21.73 42.2 45.9 42.2h110.04zm-230.33 77h-4.67v-28.08c0-2.12 0-4.95.23-8.02-.4 1.9-.9 3.3-1.1 4L657.8 328h-2.32l-14-31.85c-.47-.95-.7-2.36-1.17-4.25V328h-4.6v-41.76h6.3l12.6 29.02c1 2.12 1.7 4 1.9 4.95h.3c1-2.3 1.4-4 2.1-5.1l12.8-29h6.1v42zm11-37.82c-.92 0-1.62-.23-2.08-.95-.46-.7-.92-1.42-.92-2.14 0-.8.23-1.7.92-2.2.7-.7 1.4-1 2.08-1 .92 0 1.6.2 2.08.9.7.7.92 1.4.92 2.1 0 .9-.23 1.6-.92 2.1-.47.7-1.16.9-2.08.9zm2.3 37.82h-4.6v-30.2h4.6zm29.45-2.1c-2.36 1.4-4.97 2.1-8.3 2.1-4.26 0-7.8-1.4-10.42-4.2-2.6-2.8-4.03-6.3-4.03-10.72 0-4.9 1.42-8.62 4.27-11.65 3.32-2.8 6.87-4.43 11.6-4.43 2.62 0 5 .47 7.13 1.63v4.9c-2.14-1.64-4.5-2.33-7.12-2.33-3.08 0-5.45 1.16-7.58 3.26q-2.85 3.15-2.85 8.4c0 5.25.95 6.05 2.85 8.15s4.27 3.1 7.35 3.1c2.6 0 4.98-.9 7.35-2.5v4.4h-.24zm21.25-22.55c-.96-.7-2.15-.93-3.82-.93-2.15 0-3.82.93-5.26 2.8-1.43 1.85-2.15 4.4-2.15 7.66V328h-4.77v-29.53h4.77v6.04c.72-2 1.68-3.7 3.1-4.8 1.44-1.1 3.1-1.6 4.78-1.6 1.2 0 2.15.3 2.87.5v4.9h.48zM757.03 328c-4.4 0-7.9-1.4-10.44-4.2-2.6-2.8-4-6.3-4-10.95 0-4.9 1.4-8.86 3.9-11.65 2.5-2.8 6.5-4.2 11.1-4.2 4.4 0 7.9 1.4 10.2 3.96 2.5 2.8 3.7 6.53 3.7 11.2 0 4.65-1.4 8.38-4 11.18-2.8 3.03-6.3 4.66-10.7 4.66zm.23-27.04c-3 0-5.33.93-7.2 3.03-1.84 2.1-2.54 4.9-2.54 8.6 0 3.5.93 6.3 2.55 8.1 1.86 2.1 4.18 3 7.2 3 3 0 5.33-1 6.95-3.1 1.63-1.9 2.56-4.7 2.56-8.4s-.93-6.5-2.56-8.4c-1.62-1.9-3.94-3.1-6.96-3.1zm18.4 25.18V321c2.54 1.87 5.32 2.8 8.33 2.8 4.1 0 6.2-1.4 6.2-4.2 0-.7-.3-1.4-.5-2.1l-1.4-1.4c-.7-.45-1.4-.7-2.1-1.15-.7-.24-1.7-.7-2.6-.93-1.4-.47-2.3-.94-3.5-1.64-1-.46-1.9-1.16-2.6-1.86s-1.2-1.4-1.4-2.33c-.3-1-.5-1.9-.5-3.1 0-1.4.2-2.6.9-3.8.5-.5 1.2-1.4 2.3-2.1 1.2-.7 2.3-1.2 3.5-1.7 1.4-.5 2.8-.7 4.2-.7 2.5 0 4.8.4 6.7 1.4v4.7c-2.1-1.4-4.6-2.1-7.4-2.1-.9 0-1.6 0-2.3.2s-1.4.4-1.9.9c-.5.4-.9.7-1.2 1.4-.3.4-.5 1.1-.5 1.6 0 .7.2 1.4.4 1.8s.7.9 1.1 1.4c.4.4 1.1.7 1.8 1.1.7.3 1.6.7 2.5 1.2 1.4.5 2.6.9 3.5 1.6.9.4 1.8 1.1 2.5 1.8s1.4 1.4 1.6 2.3c.5.9.7 1.8.7 3 0 1.4-.2 2.8-.9 3.7-.7 1.1-1.4 1.8-2.6 2.5s-2.3 1.2-3.7 1.6c-1.4.2-2.8.5-4.4.5-2.6 0-5.4-.7-7.5-1.9zm37.37 1.86c-4.4 0-7.9-1.4-10.44-4.2-2.6-2.8-4-6.3-4-10.95 0-4.9 1.4-8.86 3.9-11.65 3-2.8 6.5-4.2 11.1-4.2 4.4 0 7.9 1.4 10.2 3.96 2.5 2.8 3.7 6.53 3.7 11.2 0 4.65-1.4 8.38-4 11.18-2.8 3.03-6.3 4.66-10.7 4.66zm.23-27.04c-3 0-5.33.93-7.2 3.03-1.84 2.1-2.54 4.9-2.54 8.6 0 3.5.93 6.3 2.55 8.1 1.86 2.1 4.18 3 7.2 3 3 0 5.33-1 6.95-3.1 1.63-1.9 2.56-4.7 2.56-8.4s-.93-6.5-2.56-8.4c-1.4-1.9-3.94-3.1-6.96-3.1zm53.4.94v-4.2h-7.7v-8.64l-4.8 1.63v7.2h-13.2v-4.7c0-4.2 1.7-6.3 5.05-6.3 1.2 0 2.2.2 3.2.7v-4.2c-.9-.3-2.1-.5-3.6-.5-2.6 0-5 .9-6.9 2.8-1.9 1.8-2.6 4.2-2.6 7.2v4.6h-5.3v3.9h5.3V327h4.8v-25.4H854v17.47c0 5.82 2.64 8.62 7.92 8.62 1.9 0 3.34-.3 4.54-1V323c-.93.7-1.9.95-3.1.95-1.7 0-2.63-.5-3.35-1.2-.7-.9-1-2.3-1-4.2v-16.7h7.7zm52 26.1h-5.54l-4.57-11.86H890.5L886.2 328h-5.53l16.6-42h5.04l16.4 42zm-11.56-16.37-6.73-17.8q-.36-.705-.72-2.85c-.24 1.2-.48 2.14-.72 2.85l-6.5 17.8z"/>
+      <path d="m941.65 299.42-17.3 24.33h17.07V328h-23.77v-1.42l17.3-24.33h-15.68V298h22.38m29.75 29.3h-4.75v-4.6c-1.9 3.45-5 5.3-9.3 5.3-7.13 0-10.7-4.15-10.7-12.46V298h4.76v16.62c0 6.23 2.4 9.23 7.4 9.23 2.4 0 4.3-.93 5.7-2.54 1.5-1.6 2.4-3.9 2.4-6.6V298h4.8v29.3h-.2zm23.25-23.95c-.97-.7-2.18-.93-3.64-.93-2.1 0-3.8.93-5.3 2.8-1.4 1.85-2.2 4.4-2.2 7.66V328h-4.8v-29.53h4.9v6.04c.8-2 1.7-3.7 3.2-4.8a8.2 8.2 0 0 1 4.9-1.6c1.2 0 2.2.3 2.9.5v4.9h.3zm27 10.32h-21.04c0 3.3 1 5.88 2.6 7.75 1.7 1.88 4.1 2.6 7.1 2.6 3.3 0 6.4-1.2 9.3-3.3v4.46c-2.6 1.88-6.1 2.82-10.4 2.82-4.2 0-7.5-1.4-9.9-4-2.3-2.58-3.5-6.57-3.5-11.27s1.4-8.45 4-11.27 5.9-4.46 9.7-4.46 6.9 1.17 9 3.76c2.1 2.58 3.3 6.1 3.3 10.33v2.5zm-4.97-4c0-2.8-.7-4.92-1.9-6.33-1.4-1.4-3.06-2.35-5.42-2.35-2.37 0-4.26.7-5.68 2.3-1.65 1.6-2.6 3.7-2.83 6.3h15.83z"/>
+    </g>
+    <path fill="#BB2C23" d="m3230.23 200.6-19.15-18.98c.05 0 .15-.06.2-.06l19.2 19c-.1.05-.2.05-.25.05z"/>
+    <path fill="#BD2D24" d="m3230.48 200.56-19.2-19c.26 0 .5-.1.72-.15l19.2 19c-.26.1-.5.2-.72.2z"/>
+    <path fill="#C32E24" d="m3231.2 200.4-19.2-19c.4-.1.7-.24 1.07-.4l19.15 19c-.3.16-.67.3-1.02.4"/>
+    <path fill="#BD2D24" d="m3232.22 200-19.15-19c.25-.15.45-.25.66-.4l19.1 19c-.2.15-.4.3-.6.4z"/>
+    <path fill="#BB2C23" d="m3232.83 199.6-19.15-19c.15-.1.25-.2.35-.3l19.15 19c-.1.1-.2.2-.35.3"/>
+    <path fill="#B62B24" d="m3233.18 199.3-19.15-19c.1-.06.2-.17.3-.27l19.16 19c-.1.1-.2.2-.4.26z"/>
+    <path fill="#B42924" d="m3233.5 199.03-19.16-19c.05-.1.15-.15.2-.25l19.2 19-.25.25z"/>
+    <path fill="#B02824" d="m3233.74 198.78-19.2-19c.1-.1.16-.16.2-.26l19.2 19c-.1.1-.14.15-.2.26"/>
+    <path fill="#AD2823" d="m3233.95 198.52-19.2-19c.1-.05.15-.15.2-.25l19.15 19.05c-.05.05-.1.15-.15.2"/>
+    <path fill="#A82722" d="m3234.1 198.32-19.15-19.05c.05-.05.1-.16.15-.2l19.15 19c-.05.04-.1.14-.15.25"/>
+    <path fill="#A52522" d="m3234.25 198.06-19.15-19c.05-.1.1-.15.16-.25l19.15 19c0 .1-.1.2-.1.3z"/>
+    <path fill="#A02421" d="m3234.4 197.8-19.14-19c0-.1.05-.15.1-.25l19.15 19c0 .1 0 .2-.1.26z"/>
+    <path fill="#9B2420" d="m3234.5 197.55-19.14-19c.05-.05.1-.15.1-.25l19.15 19c0 .1 0 .2-.1.25z"/>
+    <path fill="#982420" d="m3234.6 197.35-19.14-19.05c.05-.06.1-.16.1-.26l19.15 19.05s0 .1-.1.2z"/>
+    <path fill="#952220" d="m3234.7 197.1-19.14-19.06c.05-.05.05-.15.1-.25l19.15 18.9c0 .1 0 .2-.1.3z"/>
+    <path fill="#912120" d="m3234.8 196.78-19.14-19c0-.05.05-.15.05-.25l19.3 19c0 .1 0 .2-.1.25z"/>
+    <path fill="#8E201E" d="m3234.92 196.53-19.2-19c.04-.1.04-.2.1-.3l19.15 19c0 .1-.05.2-.05.3"/>
+    <path fill="#8B1F1E" d="m3234.97 196.22-19.15-19c0-.1 0-.2.05-.35l19.15 19c0 .1-.05.25-.05.35"/>
+    <path fill="#871F1C" d="m3235.02 195.86-19.15-19v-.35l19.15 19v.4z"/>
+    <path fill="#841F1C" d="m3235.02 195.46-19.15-18.95v-.1l19.15 19.1v.1z"/>
+    <use xlink:href="#reuse-0"/>
+    <use xlink:href="#reuse-0"/>
+    <path fill="#871F1C" d="m3235.02 195.4-19.15-19.04v-6.64l19.15 18.94"/>
+    <path fill="#C32E24" d="m3159.02 206.85-19.15-19 71.26-6.23 19.1 19"/>
+    <path fill="#912120" d="m3155.5 205.62-19.14-19c.05.1.1.15.2.15l19.15 19.05-.2-.2z"/>
+    <path fill="#952220" d="m3155.7 205.82-19.14-19.05.3.3 19.16 19c-.1-.1-.2-.14-.3-.25z"/>
+    <path fill="#982420" d="m3156.02 206.08-19.15-19c.05.05.15.1.25.15l19.2 19z"/>
+    <path fill="#9B2420" d="m3156.32 206.23-19.2-19 .3.16 19.16 19c-.1 0-.2-.1-.26-.2z"/>
+    <path fill="#A02421" d="m3156.58 206.4-19.15-19c.1.04.2.1.25.14l19.2 19-.3-.15z"/>
+    <path fill="#A52522" d="m3156.88 206.54-19.2-19c.1 0 .2.05.3.1l19.16 19c-.1-.05-.15-.05-.26-.1"/>
+    <path fill="#A82722" d="m3157.14 206.64-19.15-19c.1.05.2.05.3.1l19.1 19c-.1-.05-.2-.05-.3-.1z"/>
+    <path fill="#AD2823" d="m3157.44 206.74-19.15-19c.1 0 .2.06.3.06l19.1 19c-.1 0-.2-.06-.3-.06z"/>
+    <path fill="#B02824" d="m3157.75 206.8-19.15-19c.1 0 .2.05.3.05l19.16 19c-.1 0-.2 0-.3-.06z"/>
+    <path fill="#B42924" d="m3158.06 206.85-19.16-19h.36l19.15 19.05c-.1 0-.2-.05-.3-.05z"/>
+    <path fill="#B62B24" d="m3158.4 206.9-19.14-19.05c.1.05.26.05.36.05l19.2 19h-.4z"/>
+    <path fill="#BB2C23" d="m3158.82 206.9-19.2-19c.1-.05.15-.05.25-.05l19.15 19c-.1.05-.15.05-.2.05"/>
+    <path fill="#7F1D1C" d="m3127.7 235.6-19.15-19.05c-1.38-1.33-2.24-3.17-2.4-5.26l19.15 18.9c.16 2.1 1.07 4 2.4 5.3z"/>
+    <path fill="#841F1C" d="m3125.3 230.3-19.15-19c-.05-.27-.05-.52-.05-.73l19.2 18.95c-.05.26 0 .5 0 .77z"/>
+    <path fill="#D93023" d="m3263.95 186.1-.05 31.27c0 5.05-4.13 9.55-9.22 10l-120.3 10.58c-5.05.4-9.18-3.32-9.13-8.43l.05-31.2 28.88-2.56v6.7c0 2.6 2.14 4.6 4.8 4.33l71.25-6.3c2.65-.3 4.8-2.6 4.8-5.2v-6.7l28.92-2.6z"/>
+    <use xlink:href="#reuse-1"/>
+    <use xlink:href="#reuse-1"/>
+    <path fill="#871F1C" d="m3125.3 229.52-19.2-18.9.1-31.25 19.16 18.95"/>
+    <path fill="#E63F46" d="m3263.75 133.45.2 45.97-28.93 2.55-.2-45.96"/>
+    <path fill="#E23535" d="m3263.75 133.45.2 45.97-28.93 2.55-.2-45.96"/>
+    <path fill="#871F1C" d="m3235.07 181.97-19.15-18.94-.2-45.97 19.15 19"/>
+    <use xlink:href="#reuse-2"/>
+    <use xlink:href="#reuse-2"/>
+    <path fill="#E63F46" d="m3154.08 143.1.16 45.97-28.94 2.56-.2-46.02"/>
+    <path fill="#E23535" d="m3154.08 143.1.16 45.97-28.94 2.56-.2-46.02"/>
+    <path fill="#871F1C" d="m3125.36 191.63-19.16-19-.2-45.92 19.15 18.9"/>
+    <path fill="#871F1C" d="M3125.1 145.66 3106 126.7l28.98-2.54 19.1 18.95m80.94-13.9-19.15-18.9v-5.8l19.15 19"/>
+    <path fill="#841F1C" d="m3235.02 123.44-19.15-19v-.35l19.15 19v.3z"/>
+    <path fill="#7F1D1C" d="m3235.02 123.1-19.15-18.96c-.1-1.18-.56-2.15-1.28-2.86l19.1 19c.7.7 1.2 1.68 1.3 2.8z"/>
+    <path fill="#BB2C23" d="m3254.83 88-19.15-19h.4l19.16 19h-.4z"/>
+    <path fill="#B62B24" d="m3255.24 88.05-19.15-19c.2-.05.5-.05.7 0l19.1 19h-.7z"/>
+    <path fill="#B42924" d="m3255.95 88-19.15-19c.26 0 .46 0 .66.05l19.2 19c-.25-.05-.45-.05-.7-.05z"/>
+    <path fill="#B02824" d="m3256.67 88.05-19.2-19c.25 0 .45.05.66.05l19.15 19.05c-.2-.05-.4-.1-.6-.1z"/>
+    <path fill="#AD2823" d="m3257.28 88.15-19.15-19.05.56.16 19.1 19c-.2-.06-.4-.1-.6-.1z"/>
+    <path fill="#A82722" d="m3257.84 88.25-19.15-19 .5.16 19.1 19-.6-.1z"/>
+    <path fill="#A52522" d="m3258.4 88.4-19.15-19c.2.06.35.16.56.2l19.2 19c-.1-.04-.3-.1-.5-.2z"/>
+    <path fill="#A02421" d="m3258.96 88.6-19.15-19c.2.12.4.22.6.27l19.2 19-.5-.26z"/>
+    <path fill="#9B2420" d="m3259.52 88.87-19.15-19 .5.3 19.16 19c-.16-.1-.36-.2-.5-.3z"/>
+    <path fill="#982420" d="m3260.03 89.17-19.15-19c.2.16.4.26.56.4l19.15 18.96c-.2-.1-.4-.25-.6-.36z"/>
+    <path fill="#952220" d="m3260.6 89.53-19.16-18.95c.2.1.4.26.6.46L3261.2 90z"/>
+    <path fill="#912120" d="m3261.2 90-19.15-18.96c.1.1.25.2.35.3l19.16 19-.36-.35z"/>
+    <path fill="#871F1C" d="m3125.3 138.77-19.15-18.95.1-30.34 19.16 19"/>
+    <path fill="#C32E24" d="m3134.52 98.52-19.1-18.95L3235.72 69l19.1 19"/>
+    <use xlink:href="#reuse-3"/>
+    <use xlink:href="#reuse-3"/>
+    <path fill="#841F1C" d="m3125.4 108.48-19.15-19v-.2l19.16 19v.2z"/>
+    <path fill="#871F1C" d="m3125.4 108.28-19.15-19c0-.26 0-.5.06-.77l19.2 19.1v.7z"/>
+    <path fill="#8B1F1E" d="M3125.46 107.56 3106.3 88.5c0-.2.06-.4.1-.6l19.16 19c-.05.2-.1.4-.1.66"/>
+    <path fill="#8E201E" d="m3125.56 106.9-19.15-19c0-.2.1-.4.1-.62l19.2 19.05c0 .16-.1.36-.1.57z"/>
+    <path fill="#912120" d="m3125.66 106.33-19.15-19.05c.1-.15.1-.35.2-.5l19.2 19-.1.55z"/>
+    <path fill="#952220" d="m3125.8 105.77-19.14-19 .15-.5 19.2 19-.1.5z"/>
+    <path fill="#982420" d="m3125.97 105.26-19.16-19 .3-.5 19.2 19.04c0 .16-.1.3-.2.46z"/>
+    <path fill="#9B2420" d="m3126.17 104.8-19.15-19.05c.05-.15.1-.3.2-.46l19.15 19c-.05.1-.15.3-.2.5z"/>
+    <path fill="#A02421" d="m3126.37 104.3-19.15-19c.05-.16.16-.3.26-.47l19.15 19c-.1.15-.15.3-.26.46z"/>
+    <path fill="#A52522" d="m3126.63 103.83-19.15-19c.05-.15.15-.3.25-.46l19.15 19c-.1.16-.2.3-.25.46"/>
+    <path fill="#A82722" d="m3126.88 103.37-19.15-19 .3-.46 19.16 19c-.1.2-.2.4-.4.5z"/>
+    <path fill="#AD2823" d="m3127.2 102.9-19.16-19 .3-.45 19.15 19-.3.46z"/>
+    <path fill="#B02824" d="m3127.5 102.45-19.16-19c.1-.15.26-.3.4-.46l19.16 19c-.15.1-.25.3-.4.4z"/>
+    <path fill="#B42924" d="m3127.9 102-19.15-19c.15-.16.26-.3.4-.52l19.2 19.05c-.14.16-.3.3-.45.46z"/>
+    <path fill="#B62B24" d="m3128.36 101.53-19.2-19.05c.2-.15.35-.3.56-.5l19.15 19c-.15.2-.36.35-.5.55z"/>
+    <path fill="#BB2C23" d="m3128.87 100.97-19.15-19 .7-.56 19.16 19c-.25.2-.46.5-.7.6z"/>
+    <path fill="#BD2D24" d="m3129.58 100.4-19.15-19c.36-.24.77-.5 1.17-.7l19.2 18.94c-.45.26-.8.5-1.22.77z"/>
+    <path fill="#C32E24" d="m3130.8 99.64-19.2-19c.66-.3 1.33-.6 2-.8l19.14 19c-.66.2-1.32.5-1.93.8z"/>
+    <path fill="#BD2D24" d="m3132.74 98.83-19.15-19c.4-.1.9-.2 1.3-.26l19.1 19c-.5.05-.9.15-1.4.26z"/>
+    <path fill="#BB2C23" d="m3134.12 98.57-19.16-19c.16-.05.3-.05.46-.05l19.15 19c-.15 0-.3 0-.45.05"/>
+    <path fill="#666769" d="M3164 286.22c0-4.86-.27-7.33-.32-10.64h5.63l.4 5h.2c1.8-3.3 5.1-5.58 9.4-5.58 5.7 0 9.9 4.18 9.9 14.1v27.58h-6.4v-26.43c0-4.9-.9-9.7-5.7-9.7-2.7 0-5.3 2.27-6 6.6-.2 1-.3 2.28-.3 3.73v25.8h-6.6v-30.46zm-13.18 5.68c.05-8.16-2.93-11.8-6.06-11.8-4.3 0-6.4 6.17-6.64 11.8zm-12.8 4.8c0 12.64 4.96 15.32 9.58 15.32 2.9 0 5.15-.73 6.74-1.56l1.1 4.8c-2.26 1.18-5.72 1.95-9 1.95-9.77 0-14.78-8.1-14.78-20.6 0-13.2 5.64-21.5 13.77-21.5 8.23 0 11.65 8.9 11.65 18 0 1.6-.14 2.8-.24 3.8h-18.82zm-31.77 4.97c0 1.2.1 2.38.33 3.4 1.3 5.88 4.3 6.9 6.02 6.9 5.4 0 7.17-7.48 7.17-15.74 0-8.5-2.02-15.64-7.22-15.64-2.98 0-5.68 3.6-6.02 7.3-.2.9-.28 2-.28 3.1v10.5zm-6.36-13.26c0-6.2-.3-9.9-.4-12.8h5.7l.3 5.3h.2c2.2-4.3 5.5-5.9 8.7-5.9 7.1 0 11.7 7.6 11.7 21.1 0 15.3-6.2 21.4-12.6 21.4-3.9 0-6.1-2.4-7.2-4.7h-.2V333h-6.4v-44.6zm-27.4 7.8c0 6.8 1.1 16.1 7 16.1 5.6 0 6.8-9.5 6.8-16 0-6.2-1.2-15.9-7-15.9s-6.9 9.7-6.9 16zm20.2 0c0 15.9-7.2 21.3-13.6 21.3-7.4 0-13.2-6.7-13.2-21.1 0-14.9 6.6-21.2 13.6-21.2 7.3 0 13.1 6.9 13.1 21.2z"/>
+    <path fill="#D02A25" d="M3305.63 294.47h.14c.77-1.6 1.44-3.18 2.2-4.53l8.05-14.43h6.97l-10.8 17.2 11.7 23.6h-7.2l-8.9-19.2-2.4 3.8v15.5h-6.4V258h6.4v36.47zm-11.84 20.84c-1.5.9-3.9 1.6-6.8 1.6-8.9 0-14.9-7.2-14.9-20.7 0-11.7 5.8-21.2 16-21.2 2.2 0 4.5.6 5.7 1.3l-1.3 5.3c-.9-.4-2.5-1-4.7-1-6.6 0-9.4 7.7-9.4 15.8 0 9.5 3.6 15.3 9.5 15.3 1.7 0 3.2-.3 4.7-1.1l.9 5zm-35.3-20.1c-3.4 0-11.2.7-11.2 9.5 0 5.4 2.7 7.3 4.9 7.3 2.8 0 5.2-2.1 5.9-6.1.2-.7.3-1.6.3-2.3v-8.2zm6.3 11.9c0 3.2 0 6.7.4 9.3h-5.8l-.4-4.4h-.3c-1.8 3.2-4.6 5.1-8.2 5.1-5.5 0-9.7-4.6-9.7-11.6 0-10.3 8.2-14.7 17.3-14.8v-1.2c0-5.5-1.5-9.2-6.5-9.2-2.6 0-4.8.8-6.8 2.1l-1.5-4.5c1.8-1.2 5.5-2.7 9.6-2.7 8.1 0 11.6 5.3 11.6 14.5V307zm-35-41v9.6h7.8v4.9h-7.9v24.3c0 5.3 1.9 6.8 4.2 6.8 1 0 1.9-.1 2.6-.2l.3 5c-1.2.5-2.7.7-4.8.7-2.6 0-4.9-.7-6.4-2.4-1.7-1.8-2.5-4.6-2.5-10.3v-23.7h-5v-4.9h5V269l6.4-2.7zm-33.3 43.6c1.4.9 3.9 2.1 6.5 2.1 3.6 0 5.9-2.3 5.9-5.9 0-3.1-1.1-5.2-5.2-8-5.3-3.4-8.2-6.9-8.2-11.5 0-6.6 4.8-11.3 11.1-11.3 3.2 0 5.5 1.1 7.2 2.2l-1.7 4.9c-1.6-1.1-3.3-1.8-5.5-1.8-3.5 0-5.2 2.5-5.2 5.2s1 4.2 5 7c4.7 3.1 8.4 6.7 8.4 12.4 0 8.3-5.6 12.2-12.4 12.2-3 0-6.3-.9-8-2.3l1.6-4.9z"/>
+    <path fill="#CECCC9" d="M3330 313.35h.38c.44 0 .78-.15.78-.5s-.2-.55-.73-.55c-.2 0-.35.05-.44.05v1zm0 1.95h-.8v-3.45c.3-.05.74-.15 1.32-.15.64 0 .93.15 1.13.3.25.15.34.4.34.75 0 .4-.3.7-.7.8v.05c.3.1.5.4.6.85.1.55.2.7.2.85h-.8c-.2-.15-.2-.45-.3-.85-.1-.35-.3-.55-.7-.55h-.4v1.4zm-2.12-1.8c0 1.55 1.18 2.75 2.64 2.75 1.47.05 2.6-1.2 2.6-2.75s-1.13-2.85-2.6-2.85c-1.46 0-2.64 1.3-2.64 2.85m6.12 0c0 1.95-1.52 3.5-3.48 3.5-1.95 0-3.52-1.55-3.52-3.5s1.57-3.5 3.52-3.5c1.96 0 3.48 1.55 3.48 3.5"/>
+    <path fill="#696566" fill-rule="nonzero" d="m2718.36 224.24-15.23-42.43c-.2-.5-.5-1.3-.5-2 0-1.8 1.56-3.6 3.8-3.6 1.93 0 3.2 1.3 3.78 3.1l12.7 36.6 12.7-36.6c.6-1.7 1.8-3 3.7-3h.4c2.1 0 3.3 1.3 3.9 3l12.6 36.7 12.9-36.7c.5-1.5 1.6-2.9 3.6-2.9 2.1 0 3.7 1.7 3.7 3.5 0 .7-.3 1.5-.4 2l-15.3 42.6c-.8 2.3-2.3 3.4-4.1 3.4h-.2c-1.9 0-3.4-1.1-4.1-3.4l-12.5-36-12.7 36.1c-.6 2.2-2.1 3.4-4 3.4h-.2c-1.8 0-3.4-1.2-4.2-3.4m111-44.4c0-2 1.7-3.8 3.7-3.8 2.2 0 3.8 1.7 3.8 3.8v8.6c3.7-8.3 11.9-12.3 17.3-12.3 2.3 0 3.7 1.7 3.7 3.8 0 2-1.3 3.5-3.3 3.8-9.7 1.2-17.7 8.5-17.7 23v17c0 2.1-1.5 3.8-3.6 3.8s-3.8-1.7-3.8-3.8v-44zm52.5 48.2c-13.5 0-24.5-10.5-24.5-25.9v-.2c0-14.3 10-25.9 23.7-25.9 14.6 0 22.9 12 22.9 25.2 0 2-1.6 3.5-3.4 3.5H2865c1.04 10.7 8.56 16.8 17.34 16.8 6.1 0 10.6-2.4 14.2-5.8.6-.5 1.28-.9 2.1-.9 1.8 0 3.28 1.5 3.28 3.2 0 .9-.4 1.7-1.15 2.4-4.65 4.5-10.2 7.5-18.56 7.5zm14.6-28.8c-.7-9-5.9-16.9-15.7-16.9-8.5 0-15 7.3-16 17h31.8zm-120.1 13.2v-.2c0-10.5 8.7-16.2 21.4-16.2 6.4 0 11 .9 15.4 2.2v-1.7c0-9-5.5-13.7-14.9-13.7-5 0-8 .6-11.6 2.3-.5.2-1 .3-1.4.3-1.7 0-3.3-1.4-3.3-3.2 0-1.5.7-2.5 2.1-3.1 5-2.1 8.7-2.8 15.1-2.8 7 0 12.5 1.8 16.1 5.5 3.4 3.4 5.2 8.3 5.2 14.7V224c0 2.14-1.6 3.7-3.6 3.7-2.1 0-3.6-1.56-3.6-3.5v-4.78c-3.5 4.57-9.3 8.63-18.1 8.63-9.3 0-18.7-5.33-18.7-15.6m36.9-3.9v-4.84c-3.7-1-8.6-2.1-14.7-2.1-9.4 0-14.6 4.1-14.6 10.4v.2c0 6.3 5.8 10 12.6 10 9.2 0 16.8-5.6 16.8-13.5M2583 179.5c-1.66-3.6-5.7-5.2-9.5-3.5s-5.2 5.9-3.48 9.5l15.9 34.6c2.5 5.5 5.14 8.3 10.1 8.3 5.27 0 7.58-3.1 10.08-8.2l14-30.5c.16-.3.6-1.3 2-1.3 1.2 0 2.2 1 2.2 2.3V220c0 4.56 2.5 8.3 7.4 8.3 4.8 0 7.48-3.74 7.48-8.3v-24.2c0-4.67 3.3-7.7 7.9-7.7 4.5 0 7.55 3.14 7.55 7.7v24.17c0 4.57 2.53 8.3 7.4 8.3 4.83 0 7.5-3.73 7.5-8.3V195.8c0-4.66 3.33-7.7 7.9-7.7s7.6 3.15 7.6 7.7v24.18c0 4.57 2.5 8.3 7.35 8.3s7.5-3.73 7.5-8.3v-27.6c0-10.1-8.14-17.2-17.9-17.2-9.8 0-15.9 6.8-15.9 6.8-3.3-4.23-7.75-6.77-15.34-6.77-8 0-15 6.8-15 6.8-3.26-4.2-8.8-6.7-13.4-6.7-7.1 0-12.72 3.2-16.16 11l-10.2 24-13-30.7z"/>
+    <path stroke="#979797" stroke-linecap="square" stroke-width="2" d="M2405.6 1v400"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-rolling-deploys.svg b/content/nomad/v0.12.x/img/feature-rolling-deploys.svg
new file mode 100644
index 0000000000..cbbb2cba78
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-rolling-deploys.svg
@@ -0,0 +1,33 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 175">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#FFF" stroke-width="5" d="M33.302 90.566A61.4 61.4 0 0 0 30 110.5c0 33.966 27.534 61.5 61.5 61.5s61.5-27.534 61.5-61.5S125.466 49 91.5 49"/>
+    <path stroke="#FFF" stroke-opacity=".6" stroke-width="5" d="M87.935 49.102c-24.4 1.394-44.99 17.013-53.607 38.69"/>
+    <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+      <text font-size="12" transform="translate(55 88)">
+        <tspan x=".494" y="42">rolling...</tspan>
+      </text>
+      <text font-size="30" transform="translate(55 88)">
+        <tspan x=".494" y="25">9/12</tspan>
+      </text>
+    </g>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M195 109h27.538"/>
+    <path fill="#FFF" d="m231.5 109.037-10.5 6.038V103"/>
+    <g transform="translate(267 49)">
+      <circle cx="61.5" cy="61.5" r="61.5" stroke="#FFF" stroke-width="5"/>
+      <g fill="#FFF" font-family="CourierNewPS-BoldMT, Courier New" font-weight="bold">
+        <text font-size="12" transform="translate(16 39)">
+          <tspan x="27.497" y="42">done!</tspan>
+        </text>
+        <text font-size="30" transform="translate(16 39)">
+          <tspan x=".493" y="25">12/12</tspan>
+        </text>
+      </g>
+    </g>
+    <g fill="#FFF">
+      <path fill-opacity=".6" d="m258.527 1.02-16.33 9.473 16.33 9.474 16.2-9.56"/>
+      <path fill-rule="nonzero" d="M258.527.037 241 10.194v20.27l11.97 6.915v-.985l-11.115-6.4V11.303L258.1 20.69v19.42l.64.384 17.312-10.03v-20.27zm0 19.93-16.33-9.474 16.33-9.474 16.2 9.386-16.2 9.56zm16.67 10.03L259.597 39l-.64.384V20.692l16.242-9.56v18.864z"/>
+    </g>
+    <path d="M27.5 1.02 11.195 10.5 27.5 19.983l16.177-9.567"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M27.5.037 10 10.202V30.49l11.95 6.917v-.982L10.855 30.02V11.312l16.22 9.395V40.14l.64.385L45 30.49V10.2zm0 19.945-16.305-9.48L27.5 1.02l16.177 9.396zM44.146 30.02l-15.58 9.01-.64.385V20.708l16.22-9.566z"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/feature-simplify.svg b/content/nomad/v0.12.x/img/feature-simplify.svg
new file mode 100644
index 0000000000..da08278683
--- /dev/null
+++ b/content/nomad/v0.12.x/img/feature-simplify.svg
@@ -0,0 +1,23 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 694 456">
+  <g fill="none" fill-rule="evenodd">
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M341 63.5v26m0 1v30"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M111 345h232v111H111z"/>
+    <path fill="#1F9967" d="M178.26 385.96a5.7 5.7 0 0 1-1.31.27q-.73.07-1.75.07.96.44 1.44 1.1t.48 1.6q0 1.04-.51 1.84t-1.45 1.26-2.22.46q-.9 0-1.44-.18a1.1 1.1 0 0 0-.34.39q-.12.23-.12.49 0 .8 1.3.8h1.84q1.12 0 2 .38c.88.38 1.043.603 1.37 1.05q.49.67.49 1.51 0 1.58-1.36 2.45t-3.92.87q-1.78 0-2.81-.37t-1.46-1.08-.43-1.83h2q0 .6.23.95t.81.52 1.68.17q1.6 0 2.3-.39t.7-1.15q0-.64-.55-.99t-1.49-.35h-1.82q-1.42 0-2.15-.58t-.73-1.46q0-.54.3-1.04t.86-.86q-.94-.5-1.37-1.21t-.43-1.75q0-1.1.56-1.95t1.56-1.32 2.28-.47q1.72.02 2.73-.24c1.01-.26 1.39-.447 2.15-.82zm-7.04 1.35q-.54.59-.54 1.59 0 1.02.55 1.61t1.61.59q1 0 1.52-.58t.52-1.66q0-2.14-2.06-2.14-1.06 0-1.6.59m18.64-1.87-.38 3.9h-1.6v-2.16q-1.1.02-1.91.88t-1.29 2.42v3.92h2.12v1.6h-5.92v-1.6h1.56v-7.36h-1.56v-1.6h3.26l.4 2.44q.62-1.36 1.51-2.03t2.21-.67q.82 0 1.6.26m10.68 1.21q1.24 1.49 1.24 4.05t-1.26 4.06-3.52 1.5q-2.28 0-3.53-1.47t-1.25-4.07q0-2.52 1.27-4.04c1.27-1.52 2.023-1.52 3.53-1.52q2.28 0 3.52 1.49m-5.35 1.19q-.61.94-.61 2.88 0 1.96.6 2.89t1.82.93 1.82-.94.6-2.9q0-1.94-.6-2.87t-1.8-.93q-1.22 0-1.83.94m11.83 4.98q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm18.76-2.12q0 2.5-1.06 4.03t-3.02 1.53q-1.66 0-2.68-1.16v4.96l-2.24.26v-14.88h1.94l.14 1.36q.6-.8 1.39-1.22t1.69-.42q3.84 0 3.84 5.54m-5.74-3.4q-.58.42-1.02 1.1v4.94q.78 1.18 2.08 1.18 1.16 0 1.74-.92c.58-.92.58-1.573.58-2.88q0-2.02-.52-2.93t-1.58-.91q-.7 0-1.28.42m11.58 5.66q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36m12.69-7.4q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m10.55-.49q0 1.34 1.6 1.34.8 0 1.68-.36l.56 1.56q-1.1.6-2.72.6-1.58 0-2.47-.89t-.89-2.45v-10.08H252v-1.64h5.42zm9.6-.3q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm12.51.93q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m-91.464 30.664.714 1.008q-.491.42-1.176.665-.687.245-1.414.245-1.694 0-2.646-1.043c-.635-.7-.952-1.63-.952-2.8 0-.758.145-1.43.434-2.025a3.34 3.34 0 0 1 1.253-1.4c.54-.34 1.19-.51 1.93-.51q1.47.001 2.562.895l-.73.98q-.896-.615-1.805-.615-.923 0-1.456.665-.532.666-.532 2.01 0 1.315.532 1.93.532.619 1.455.618.883 0 1.82-.63zm8.442-4.81q.869 1.043.868 2.836 0 1.792-.882 2.842t-2.464 1.05q-1.596 0-2.47-1.03-.876-1.028-.876-2.848 0-1.765.89-2.828.888-1.064 2.47-1.064 1.596 0 2.464 1.043zm-3.745.834q-.427.659-.427 2.016 0 1.373.42 2.023t1.274.65 1.274-.657q.42-.659.42-2.03 0-1.358-.42-2.01-.42-.65-1.26-.65-.854 0-1.28.658zm8.28 3.486q0 .645.26.93.26.288.79.288.504 0 .974-.294.469-.294.75-.742v-5.348h1.567V420h-1.358l-.098-.952q-.391.546-1.022.84-.63.294-1.302.294-1.064.001-1.596-.574t-.532-1.638v-5.362h1.568v5.166zm6.833-5.166h1.358l.112.966a3.2 3.2 0 0 1 1.085-.86c.42-.202.86-.302 1.31-.302.68 0 1.2.19 1.54.574.35.383.52.924.52 1.624V420h-1.57v-4.606c0-.457-.02-.81-.07-1.057q-.077-.371-.3-.546c-.15-.11-.374-.17-.673-.17-.335 0-.655.107-.96.31-.3.207-.56.46-.775.77v5.3h-1.57v-7.39zm13.594 7.42a4.4 4.4 0 0 1-1.176.154q-1.261 0-1.946-.65-.686-.652-.686-1.772v-4.004h-1.638v-1.148h1.638v-1.652l1.568-.182v1.834h2.506l-.182 1.148H219.1v3.99q0 .601.308.89.308.286.98.286.742 0 1.372-.35l.56 1.036q-.42.265-.98.42m17.458-5.124h-5.796v-1.288h5.796zm0 2.758h-5.796v-1.274h5.796zm11.816-8.022h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246zm9.275.868q.693.365 1.057.98.364.616.364 1.386 0 .854-.392 1.66-.391.804-1.274 1.777-.883.975-2.492 2.43h4.382l-.168 1.26h-6.006v-1.19c1.213-1.16 2.12-2.08 2.716-2.73q.895-.989 1.26-1.686a3.04 3.04 0 0 0 .364-1.414q0-.73-.42-1.15t-1.148-.42q-.63.001-1.07.23-.441.233-.89.78l-1.008-.785q.573-.741 1.316-1.112.743-.37 1.764-.37.952 0 1.645.363zm5.06-.868h1.71l-.24 3.738h-1.245zm2.465 0h1.708l-.224 3.738h-1.246z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M461 345h232v111H461zM17 174h202v102H17z"/>
+    <path fill="#1F9967" d="m89.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L92.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M137.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm15.3-1.76V232h-8.34v-1.76h3.36v-9.74l-3.04 1.86-.96-1.56 4.24-2.6h1.98v12.04z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M237 174h202v102H237z"/>
+    <path fill="#1F9967" d="m309.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L312.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M357.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm15.3-1.76V232h-8.34v-1.76h3.36v-9.74l-3.04 1.86-.96-1.56 4.24-2.6h1.98v12.04z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="M476 174h202v102H476z"/>
+    <path fill="#1F9967" d="m548.24 232-1.2-7.5-1.28 7.5h-2.74l-1.78-10.56h2.16l1.1 9.16 1.48-7.82h2.24l1.36 7.82 1.1-9.16h2.08L551.04 232zm9.29-2.25q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m12.91-2.04q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m8.75-.65q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36M596.3 232h-2.6l-3.74-10.56h2.42l2.66 8.7 2.7-8.7h2.3zm12.49-13.56q.99.52 1.51 1.4c.52.88.52 1.247.52 1.98a5.36 5.36 0 0 1-.56 2.37q-.56 1.15-1.82 2.54t-3.56 3.47h6.26l-.24 1.8h-8.58v-1.7q2.6-2.5 3.88-3.91t1.8-2.41c.52-1 .52-1.34.52-2.02q0-1.04-.6-1.64t-1.64-.6q-.9 0-1.53.33t-1.27 1.11l-1.44-1.12q.82-1.06 1.88-1.59t2.52-.53q1.36 0 2.35.52"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M227 294.5v52"/>
+    <path fill="#1F9967" d="M528.26 385.96a5.7 5.7 0 0 1-1.31.27q-.73.07-1.75.07.96.44 1.44 1.1t.48 1.6q0 1.04-.51 1.84t-1.45 1.26-2.22.46q-.9 0-1.44-.18a1.1 1.1 0 0 0-.34.39q-.12.23-.12.49 0 .8 1.3.8h1.84q1.12 0 2 .38c.88.38 1.043.603 1.37 1.05q.49.67.49 1.51 0 1.58-1.36 2.45t-3.92.87q-1.78 0-2.81-.37t-1.46-1.08-.43-1.83h2q0 .6.23.95t.81.52 1.68.17q1.6 0 2.3-.39t.7-1.15q0-.64-.55-.99t-1.49-.35h-1.82q-1.42 0-2.15-.58t-.73-1.46q0-.54.3-1.04t.86-.86q-.94-.5-1.37-1.21t-.43-1.75q0-1.1.56-1.95t1.56-1.32 2.28-.47q1.72.02 2.73-.24c1.01-.26 1.39-.447 2.15-.82zm-7.04 1.35q-.54.59-.54 1.59 0 1.02.55 1.61t1.61.59q1 0 1.52-.58t.52-1.66q0-2.14-2.06-2.14-1.06 0-1.6.59m18.64-1.87-.38 3.9h-1.6v-2.16q-1.1.02-1.91.88t-1.29 2.42v3.92h2.12v1.6h-5.92v-1.6h1.56v-7.36h-1.56v-1.6h3.26l.4 2.44q.62-1.36 1.51-2.03t2.21-.67q.82 0 1.6.26m10.68 1.21q1.24 1.49 1.24 4.05t-1.26 4.06-3.52 1.5q-2.28 0-3.53-1.47t-1.25-4.07q0-2.52 1.27-4.04c1.27-1.52 2.023-1.52 3.53-1.52q2.28 0 3.52 1.49m-5.35 1.19q-.61.94-.61 2.88 0 1.96.6 2.89t1.82.93 1.82-.94.6-2.9q0-1.94-.6-2.87t-1.8-.93q-1.22 0-1.83.94m11.83 4.98q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm18.76-2.12q0 2.5-1.06 4.03t-3.02 1.53q-1.66 0-2.68-1.16v4.96l-2.24.26v-14.88h1.94l.14 1.36q.6-.8 1.39-1.22t1.69-.42q3.84 0 3.84 5.54m-5.74-3.4q-.58.42-1.02 1.1v4.94q.78 1.18 2.08 1.18 1.16 0 1.74-.92c.58-.92.58-1.573.58-2.88q0-2.02-.52-2.93t-1.58-.91q-.7 0-1.28.42m11.58 5.66q.56-.56 1.36-.56.82 0 1.38.56t.56 1.36q0 .82-.56 1.38t-1.38.56q-.8 0-1.36-.56a1.88 1.88 0 0 1-.56-1.38q0-.8.56-1.36m12.69-7.4q.75-.4 1.61-.4 2.02 0 2.98 1.46t.96 4.08q0 2.48-1.11 4.02t-3.11 1.54q-1.76 0-2.76-1.3l-.12 1.04h-1.98v-14.8l2.24-.26v5.76q.54-.74 1.29-1.14m2.56 8.05q.61-.95.61-2.89 0-2-.55-2.92t-1.63-.92q-.68 0-1.27.42t-1.01 1.1v4.94q.8 1.22 2.08 1.22 1.16 0 1.77-.95m10.55-.49q0 1.34 1.6 1.34.8 0 1.68-.36l.56 1.56q-1.1.6-2.72.6-1.58 0-2.47-.89t-.89-2.45v-10.08H602v-1.64h5.42zm9.6-.3q0 .92.37 1.33t1.13.41q.72 0 1.39-.42t1.07-1.06v-7.64h2.24V396h-1.94l-.14-1.36q-.56.78-1.46 1.2t-1.86.42q-1.52 0-2.28-.82t-.76-2.34v-7.66h2.24zm12.51.93q.79.77 1.99.77.74 0 1.41-.23a6 6 0 0 0 1.37-.69l.96 1.36a5.4 5.4 0 0 1-1.74.96 6.5 6.5 0 0 1-2.1.34q-2.42 0-3.76-1.51t-1.34-4.03q0-1.58.58-2.85t1.68-1.99c1.1-.72 1.587-.72 2.56-.72q2.1 0 3.33 1.41t1.23 3.87q0 .6-.06 1h-7q.1 1.54.89 2.31m-.13-6.15q-.68.78-.78 2.32h4.9q-.04-1.5-.64-2.3t-1.72-.8q-1.08 0-1.76.78m-91.464 30.664.714 1.008q-.491.42-1.176.665-.687.245-1.414.245-1.693 0-2.646-1.043c-.635-.7-.952-1.63-.952-2.8 0-.758.145-1.43.434-2.025a3.34 3.34 0 0 1 1.253-1.4c.54-.34 1.19-.51 1.93-.51q1.47.001 2.562.895l-.73.98q-.896-.615-1.805-.615-.923 0-1.456.665-.532.666-.532 2.01 0 1.315.532 1.93.532.619 1.455.618c.59 0 1.194-.21 1.82-.63zm8.442-4.81q.869 1.043.868 2.836 0 1.792-.882 2.842t-2.464 1.05q-1.596 0-2.47-1.03-.876-1.028-.876-2.848 0-1.765.89-2.828.888-1.064 2.47-1.064 1.596 0 2.464 1.043zm-3.745.834q-.427.659-.427 2.016 0 1.373.42 2.023t1.274.65 1.274-.657q.42-.659.42-2.03 0-1.358-.42-2.01-.42-.65-1.26-.65-.855 0-1.28.658zm8.28 3.486q0 .645.26.93.26.288.79.288.504 0 .974-.294.469-.294.75-.742v-5.348h1.567V420h-1.358l-.098-.952q-.391.546-1.022.84-.63.294-1.302.294-1.063.001-1.596-.574-.532-.575-.532-1.638v-5.362h1.568zm6.833-5.166h1.358l.112.966a3.2 3.2 0 0 1 1.085-.86c.42-.202.86-.302 1.31-.302.68 0 1.2.19 1.54.574.35.383.52.924.52 1.624V420h-1.57v-4.606c0-.457-.02-.81-.07-1.057q-.077-.371-.3-.546c-.15-.11-.374-.17-.673-.17-.335 0-.655.107-.96.31-.3.207-.56.46-.775.77v5.3h-1.57v-7.39zm13.594 7.42a4.4 4.4 0 0 1-1.176.154q-1.261 0-1.946-.65-.686-.652-.686-1.772v-4.004h-1.638v-1.148h1.638v-1.652l1.568-.182v1.834h2.506l-.182 1.148H569.1v3.99q0 .601.308.89.308.286.98.286.742 0 1.372-.35l.56 1.036q-.42.265-.98.42m17.458-5.124h-5.796v-1.288h5.796zm0 2.758h-5.796v-1.274h5.796zm11.816-8.022h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246zm11.242 9.128V420h-5.838v-1.232h2.352v-6.818l-2.128 1.302-.672-1.092 2.968-1.82h1.386v8.428zm3.094-9.128h1.708l-.238 3.738h-1.246zm2.464 0h1.708l-.224 3.738h-1.246z"/>
+    <path stroke="#FFF" stroke-width="2" d="M1 156h455v137H1z"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M579 294.5v52"/>
+    <path stroke="#FFF" stroke-width="2" d="M461 156h232v137H461z"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m341.5 133 6.5-13h-13"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="M282.5 90h119m0 .5 25.633 25.633"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m435.096 124.096-4.596-13.788-9.192 9.192"/>
+    <path stroke="#FFF" stroke-linecap="square" stroke-width="2" d="m281.5 90.5-26.34 26.34"/>
+    <path fill="#FFF" fill-rule="nonzero" d="m246.904 125.096 4.596-13.788 9.192 9.192M374.9 27.6c.1-.8.1-1.4.1-2.2C375 11.6 363.8.5 350 .5c-11.5 0-21.5 7.9-24.3 19q-3.6-.9-7.2-.9c-14.9 0-27.2 12.1-27.5 27l1-.2V45l1 .5V45h64.8l.1-.6c.1-.9.2-1.5.2-2.2 0-9.5-7.8-17.2-17.3-17.2-6.9 0-13.2 4.2-15.9 10.5l2.1.9c2.4-5.5 7.8-9.1 13.8-9.1 8.3 0 15 6.5 15 14.8 0 .4 0-.1-.1.9h-62.6c1.3-12 12.2-22.7 25.4-22.7 2.6 0 5.2.5 7.7 1.3l1.1.4.2-1.1c2.1-10.7 11.6-18.4 22.5-18.4 12.7 0 23 10.3 23 23 0 .9-.1 1.9-.2 2.9l-.1.8h.8c6.2 2.1 10.6 7.8 11.4 13.8H372v2h15c0-7-4.8-14.6-12.1-17.4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/guide-ui-acl-token-set.png b/content/nomad/v0.12.x/img/guide-ui-acl-token-set.png
new file mode 100644
index 0000000000..cd36638084
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-acl-token-set.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-acl-token.png b/content/nomad/v0.12.x/img/guide-ui-acl-token.png
new file mode 100644
index 0000000000..9f48d05c7e
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-acl-token.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempted.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempted.png
new file mode 100644
index 0000000000..3bf46e4e60
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempted.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempter.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempter.png
new file mode 100644
index 0000000000..4449e9f918
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-preempter.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-details.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-details.png
new file mode 100644
index 0000000000..b949d6371d
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-details.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-icon.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-icon.png
new file mode 100644
index 0000000000..0d964f2044
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-reschedule-icon.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-resource-utilization.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-resource-utilization.png
new file mode 100644
index 0000000000..519585acd6
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-resource-utilization.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-stop-restart.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-stop-restart.png
new file mode 100644
index 0000000000..3b84b36aa4
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-stop-restart.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-alloc-unhealthy-driver.png b/content/nomad/v0.12.x/img/guide-ui-img-alloc-unhealthy-driver.png
new file mode 100644
index 0000000000..7477bd80df
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-alloc-unhealthy-driver.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-allocations.png b/content/nomad/v0.12.x/img/guide-ui-img-client-allocations.png
new file mode 100644
index 0000000000..244b4ca922
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-allocations.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-attributes.png b/content/nomad/v0.12.x/img/guide-ui-img-client-attributes.png
new file mode 100644
index 0000000000..f87d1d45fe
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-attributes.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-detail.png b/content/nomad/v0.12.x/img/guide-ui-img-client-detail.png
new file mode 100644
index 0000000000..28234e93de
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-detail.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-drain.png b/content/nomad/v0.12.x/img/guide-ui-img-client-drain.png
new file mode 100644
index 0000000000..7ef21066c7
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-drain.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-driver-status.png b/content/nomad/v0.12.x/img/guide-ui-img-client-driver-status.png
new file mode 100644
index 0000000000..8eb6e6766a
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-driver-status.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-events.png b/content/nomad/v0.12.x/img/guide-ui-img-client-events.png
new file mode 100644
index 0000000000..0b8c674ac3
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-events.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-client-resource-utilization.png b/content/nomad/v0.12.x/img/guide-ui-img-client-resource-utilization.png
new file mode 100644
index 0000000000..4171f9a57b
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-client-resource-utilization.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-clients-filters.png b/content/nomad/v0.12.x/img/guide-ui-img-clients-filters.png
new file mode 100644
index 0000000000..28e356864f
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-clients-filters.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-clients-list.png b/content/nomad/v0.12.x/img/guide-ui-img-clients-list.png
new file mode 100644
index 0000000000..bd76f1600e
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-clients-list.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-allocations.png b/content/nomad/v0.12.x/img/guide-ui-img-job-allocations.png
new file mode 100644
index 0000000000..66c6afc430
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-allocations.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-definition-edit.png b/content/nomad/v0.12.x/img/guide-ui-img-job-definition-edit.png
new file mode 100644
index 0000000000..b3cebc245c
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-definition-edit.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-definition.png b/content/nomad/v0.12.x/img/guide-ui-img-job-definition.png
new file mode 100644
index 0000000000..b5557ee057
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-definition.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-deployment-canary.png b/content/nomad/v0.12.x/img/guide-ui-img-job-deployment-canary.png
new file mode 100644
index 0000000000..4e77aa9bcb
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-deployment-canary.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-deployments.png b/content/nomad/v0.12.x/img/guide-ui-img-job-deployments.png
new file mode 100644
index 0000000000..cd873b855f
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-deployments.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-evaluations.png b/content/nomad/v0.12.x/img/guide-ui-img-job-evaluations.png
new file mode 100644
index 0000000000..683d195e35
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-evaluations.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-filters.png b/content/nomad/v0.12.x/img/guide-ui-img-job-filters.png
new file mode 100644
index 0000000000..7bf26684c6
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-filters.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-overview-system.png b/content/nomad/v0.12.x/img/guide-ui-img-job-overview-system.png
new file mode 100644
index 0000000000..70e5e38233
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-overview-system.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-plan-placement-failures.png b/content/nomad/v0.12.x/img/guide-ui-img-job-plan-placement-failures.png
new file mode 100644
index 0000000000..6cb000100e
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-plan-placement-failures.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-plan-preemptions.png b/content/nomad/v0.12.x/img/guide-ui-img-job-plan-preemptions.png
new file mode 100644
index 0000000000..5abbd89ef3
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-plan-preemptions.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-plan.png b/content/nomad/v0.12.x/img/guide-ui-img-job-plan.png
new file mode 100644
index 0000000000..0ede71ed69
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-plan.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-run.png b/content/nomad/v0.12.x/img/guide-ui-img-job-run.png
new file mode 100644
index 0000000000..6de945978a
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-run.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-stop.png b/content/nomad/v0.12.x/img/guide-ui-img-job-stop.png
new file mode 100644
index 0000000000..8b6f07b434
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-stop.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-job-versions.png b/content/nomad/v0.12.x/img/guide-ui-img-job-versions.png
new file mode 100644
index 0000000000..748e1620c6
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-job-versions.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-periodic-force.png b/content/nomad/v0.12.x/img/guide-ui-img-periodic-force.png
new file mode 100644
index 0000000000..234ae0fda7
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-periodic-force.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-server-detail.png b/content/nomad/v0.12.x/img/guide-ui-img-server-detail.png
new file mode 100644
index 0000000000..31729fb9bd
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-server-detail.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-servers-list.png b/content/nomad/v0.12.x/img/guide-ui-img-servers-list.png
new file mode 100644
index 0000000000..6b13e5b901
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-servers-list.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-task-events.png b/content/nomad/v0.12.x/img/guide-ui-img-task-events.png
new file mode 100644
index 0000000000..4e2e1480e4
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-task-events.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-img-task-logs.png b/content/nomad/v0.12.x/img/guide-ui-img-task-logs.png
new file mode 100644
index 0000000000..92105b8201
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-img-task-logs.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-jobs-list-unauthorized.png b/content/nomad/v0.12.x/img/guide-ui-jobs-list-unauthorized.png
new file mode 100644
index 0000000000..a4af5bb9b5
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-jobs-list-unauthorized.png differ
diff --git a/content/nomad/v0.12.x/img/guide-ui-jobs-list.png b/content/nomad/v0.12.x/img/guide-ui-jobs-list.png
new file mode 100644
index 0000000000..5e030aa25d
Binary files /dev/null and b/content/nomad/v0.12.x/img/guide-ui-jobs-list.png differ
diff --git a/content/nomad/v0.12.x/img/haproxy_ui.png b/content/nomad/v0.12.x/img/haproxy_ui.png
new file mode 100644
index 0000000000..1ebfcd8b21
Binary files /dev/null and b/content/nomad/v0.12.x/img/haproxy_ui.png differ
diff --git a/content/nomad/v0.12.x/img/intro-ui-alloc-status.png b/content/nomad/v0.12.x/img/intro-ui-alloc-status.png
new file mode 100644
index 0000000000..89ceb91d10
Binary files /dev/null and b/content/nomad/v0.12.x/img/intro-ui-alloc-status.png differ
diff --git a/content/nomad/v0.12.x/img/intro-ui-job-detail.png b/content/nomad/v0.12.x/img/intro-ui-job-detail.png
new file mode 100644
index 0000000000..a067f28311
Binary files /dev/null and b/content/nomad/v0.12.x/img/intro-ui-job-detail.png differ
diff --git a/content/nomad/v0.12.x/img/intro-ui-jobs-list.png b/content/nomad/v0.12.x/img/intro-ui-jobs-list.png
new file mode 100644
index 0000000000..d9acc28c4e
Binary files /dev/null and b/content/nomad/v0.12.x/img/intro-ui-jobs-list.png differ
diff --git a/content/nomad/v0.12.x/img/intro-ui-task-group-detail.png b/content/nomad/v0.12.x/img/intro-ui-task-group-detail.png
new file mode 100644
index 0000000000..ab435d9ef3
Binary files /dev/null and b/content/nomad/v0.12.x/img/intro-ui-task-group-detail.png differ
diff --git a/content/nomad/v0.12.x/img/lb-homepage.png b/content/nomad/v0.12.x/img/lb-homepage.png
new file mode 100644
index 0000000000..75e40a3ee4
Binary files /dev/null and b/content/nomad/v0.12.x/img/lb-homepage.png differ
diff --git a/content/nomad/v0.12.x/img/lb-routing-table.png b/content/nomad/v0.12.x/img/lb-routing-table.png
new file mode 100644
index 0000000000..dc357f520c
Binary files /dev/null and b/content/nomad/v0.12.x/img/lb-routing-table.png differ
diff --git a/content/nomad/v0.12.x/img/logo-hashicorp.svg b/content/nomad/v0.12.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v0.12.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/logo-text.svg b/content/nomad/v0.12.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v0.12.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/new-targets.png b/content/nomad/v0.12.x/img/new-targets.png
new file mode 100644
index 0000000000..55ac0f4e29
Binary files /dev/null and b/content/nomad/v0.12.x/img/new-targets.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-architecture-global.png b/content/nomad/v0.12.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-architecture-region.png b/content/nomad/v0.12.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-data-model.png b/content/nomad/v0.12.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-demo-app.png b/content/nomad/v0.12.x/img/nomad-demo-app.png
new file mode 100644
index 0000000000..0b21f4e877
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad-demo-app.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-evaluation-flow.png b/content/nomad/v0.12.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v0.12.x/img/nomad-hero-pattern.svg b/content/nomad/v0.12.x/img/nomad-hero-pattern.svg
new file mode 100644
index 0000000000..b73292eb68
--- /dev/null
+++ b/content/nomad/v0.12.x/img/nomad-hero-pattern.svg
@@ -0,0 +1,1688 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="509" fill="none" viewBox="0 0 1600 509" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="1600" height="509" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+    <path fill="#00BC7F" d="M0 0h1600v509H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g opacity=".75">
+      <path fill="url(#b)" d="M1363.61 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#c)" d="M1382.37 171.828c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#d)" d="M1401.05 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#e)" d="M1401.05 161.005c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#f)" d="M1288.91 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M1307.58 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#h)" d="M1326.26 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#i)" d="M1326.26 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#j)" d="M1344.94 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#k)" d="M1363.61 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#l)" d="M1344.94 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M1363.61 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#n)" d="M1382.37 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#o)" d="M1401.05 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#p)" d="M1382.37 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#q)" d="M1401.05 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#r)" d="M1232.8 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#s)" d="M1251.55 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#t)" d="M1251.55 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#u)" d="M1270.23 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#v)" d="M1288.91 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#w)" d="M1270.23 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#x)" d="M1288.91 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#y)" d="M1307.58 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#z)" d="M1326.26 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#A)" d="M1307.58 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#B)" d="M1326.26 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#C)" d="M1344.94 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#D)" d="M1363.61 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#E)" d="M1344.94 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#F)" d="M1363.61 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#G)" d="M1382.37 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823a.6.6 0 0 1-.32.081" opacity=".9"/>
+      <path fill="url(#H)" d="M1401.05 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#I)" d="M1382.37 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#J)" d="M1401.05 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#K)" d="M1232.8 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#L)" d="M1251.55 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#M)" d="M1232.8 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#N)" d="M1251.55 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#O)" d="M1270.23 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#P)" d="M1288.91 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#Q)" d="M1270.23 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#R)" d="M1288.91 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#S)" d="M1307.58 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#T)" d="M1326.26 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#U)" d="M1307.58 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#V)" d="M1326.26 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#W)" d="M1344.94 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#X)" d="M1363.61 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.744c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823z" opacity=".8"/>
+      <path fill="url(#Y)" d="M1344.94 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#Z)" d="M1363.61 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aa)" d="M1382.37 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ab)" d="M1401.05 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ac)" d="M1382.37 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ad)" d="M1401.05 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ae)" d="M1232.8 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#af)" d="M1251.55 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ag)" d="M1232.8 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#ah)" d="M1251.55 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ai)" d="M1270.23 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aj)" d="M1288.91 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ak)" d="M1270.23 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#al)" d="M1288.91 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#am)" d="M1307.58 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#an)" d="M1326.26 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ao)" d="M1307.58 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#ap)" d="M1326.26 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aq)" d="M1344.94 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#ar)" d="M1363.61 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#as)" d="M1344.94 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#at)" d="M1363.61 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#au)" d="M1382.37 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#av)" d="M1401.05 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aw)" d="M1382.37 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ax)" d="M1401.05 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ay)" d="M1232.8 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#az)" d="M1251.55 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aA)" d="M1232.8 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#aB)" d="M1251.55 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#aC)" d="M1270.23 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aD)" d="M1288.91 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aE)" d="M1270.23 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#aF)" d="M1288.91 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#aG)" d="M1307.58 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#aH)" d="M1326.26 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aI)" d="M1307.58 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09 0-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#aJ)" d="M1326.26 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aK)" d="M1344.94 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#aL)" d="M1363.61 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aM)" d="M1344.94 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#aN)" d="M1363.61 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.17.081-.33.081" opacity=".8"/>
+      <path fill="url(#aO)" d="M1382.37 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#aP)" d="M1401.05 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aQ)" d="M1382.37 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#aR)" d="M1401.05 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aS)" d="M1232.8 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aT)" d="M1251.55 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aU)" d="M1232.8 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aV)" d="M1251.55 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aW)" d="M1270.23 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aX)" d="M1288.91 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aY)" d="M1270.23 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aZ)" d="M1288.91 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ba)" d="M1307.58 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bb)" d="M1326.26 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bc)" d="M1307.58 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bd)" d="M1326.26 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#be)" d="M1344.94 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bf)" d="M1363.61 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bg)" d="M1344.94 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bh)" d="M1363.61 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bi)" d="M1382.37 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bj)" d="M1401.05 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bk)" d="M1382.37 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bl)" d="M1401.05 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bm)" d="M1232.8 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bn)" d="M1251.55 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#bo)" d="M1232.8 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#bp)" d="M1251.55 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bq)" d="M1270.23 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#br)" d="M1288.91 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#bs)" d="M1270.23 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#bt)" d="M1288.91 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bu)" d="M1307.58 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bv)" d="M1326.26 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#bw)" d="M1307.58 452.354c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.6-10.743c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824z" opacity=".5"/>
+      <path fill="url(#bx)" d="M1326.26 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#by)" d="M1344.94 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bz)" d="M1344.94 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#bA)" d="M1363.61 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bB)" d="M1382.37 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#bC)" d="M1232.8 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bD)" d="M1232.8 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bE)" d="M1251.55 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bF)" d="M1270.23 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bG)" d="M1270.23 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bH)" d="M1288.91 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bI)" d="M1307.58 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.25.08-.33.08" opacity=".5"/>
+    </g>
+    <path fill="url(#bJ)" d="M130.232 9.88c-.08 0-.24 0-.32-.081L110.353-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L112.678-1.505l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bK)" d="M167.585 9.88c-.08 0-.24 0-.32-.081L147.706-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803L150.031-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#bL)" d="M148.909 20.703c-.08 0-.241 0-.321-.08L129.03 9.317l19.558-11.304c.321-.16.642-.08.802.24s.08.641-.241.802L131.354 9.318l17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bM)" d="M130.232 31.526c-.08 0-.24 0-.32-.08L110.353 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L112.678 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.321.321-.481.321"/>
+    <path fill="url(#bN)" d="M204.939 9.879c-.08 0-.241 0-.321-.08L185.06-1.506l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384-1.506l17.795 10.263c.321.16.401.56.241.801-.08.24-.241.32-.481.32"/>
+    <path fill="url(#bO)" d="M186.262 20.703c-.08 0-.24 0-.32-.08L166.383 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L168.708 9.318l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bP)" d="M167.585 31.526c-.08 0-.24 0-.32-.08L147.706 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802L150.031 20.14l17.795 10.262c.321.16.401.562.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bQ)" d="M148.909 42.269c-.08 0-.241 0-.321-.08L129.03 30.884l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bR)" d="M130.232 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.32-.481.32"/>
+    <path fill="url(#bS)" d="M242.292 9.88c-.08 0-.24 0-.32-.081L222.413-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803L224.738-1.505l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#bT)" d="M223.616 20.703c-.081 0-.241 0-.321-.08L203.737 9.317l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.641-.241.802L206.141 9.318l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#bU)" d="M204.939 31.526c-.08 0-.241 0-.321-.08L185.06 20.14l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384 20.14l17.795 10.263c.321.16.401.56.241.801-.08.16-.241.321-.481.321"/>
+    <path fill="url(#bV)" d="M186.262 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bW)" d="M167.585 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bX)" d="M148.909 63.836c-.08 0-.241 0-.321-.08L129.03 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L131.435 52.45l17.794 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32"/>
+    <path fill="url(#bY)" d="M130.232 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.321.321-.481.321"/>
+    <path fill="url(#bZ)" d="M279.726 9.88c-.08 0-.241 0-.321-.081L259.847-1.505l19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803L262.251-1.505l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#ca)" d="M261.049 20.703c-.08 0-.24 0-.321-.08L241.17 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802L243.495 9.318 261.29 19.58c.32.16.4.562.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cb)" d="M242.292 31.526c-.08 0-.24 0-.32-.08L222.413 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L224.738 20.14l17.795 10.263c.32.16.401.56.24.801 0 .16-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cc)" d="M223.616 42.27c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#cd)" d="M204.939 53.093c-.08 0-.241 0-.321-.08L185.06 41.708l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32"/>
+    <path fill="url(#ce)" d="M186.262 63.836c-.08 0-.24 0-.32-.08L166.383 52.45l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L168.788 52.45l17.795 10.262c.321.16.401.562.24.802-.16.24-.32.32-.561.32"/>
+    <path fill="url(#cf)" d="M167.585 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321"/>
+    <path fill="url(#cg)" d="M148.909 85.483c-.08 0-.241 0-.321-.08L129.03 74.097l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802l-17.714 10.262 17.794 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32"/>
+    <path fill="url(#ch)" d="M130.232 96.226c-.08 0-.24 0-.32-.08L110.353 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L112.678 84.84l17.795 10.262c.32.16.4.562.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#ci)" d="M317.079 9.88c-.08 0-.24 0-.32-.081L297.2-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L299.525-1.505 317.32 8.757c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cj)" d="M298.402 20.703c-.08 0-.24 0-.32-.08L278.523 9.317l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L280.848 9.318l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+    <path fill="url(#ck)" d="M279.726 31.526c-.08 0-.241 0-.321-.08L259.847 20.06l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 20.06l17.795 10.262c.321.16.401.561.241.802-.16.24-.401.4-.561.4" opacity=".7"/>
+    <path fill="url(#cl)" d="M261.049 42.27c-.08 0-.24 0-.321-.081L241.17 30.885l19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#cm)" d="M242.292 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cn)" d="M223.616 63.836c-.081 0-.241 0-.321-.08L203.737 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L206.141 52.45l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#co)" d="M204.939 74.659c-.08 0-.241 0-.321-.08L185.06 63.274l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cp)" d="M186.262 85.482c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.16.16-.32.32-.561.32"/>
+    <path fill="url(#cq)" d="M167.585 96.226c-.08 0-.24 0-.32-.08L147.706 84.84l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L150.031 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#cr)" d="M148.909 107.049c-.08 0-.241 0-.321-.08L129.03 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cs)" d="M130.232 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.321.321-.481.321"/>
+    <path fill="url(#ct)" d="M354.433 9.88c-.081 0-.241 0-.321-.081L334.553-1.505l19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803L336.878-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cu)" d="M335.756 20.703c-.08 0-.241 0-.321-.08L315.877 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.201 9.318l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cv)" d="M317.079 31.526c-.08 0-.24 0-.32-.08L297.2 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L299.525 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cw)" d="M298.402 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321" opacity=".6"/>
+    <path fill="url(#cx)" d="M279.726 53.092c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32" opacity=".7"/>
+    <path fill="url(#cy)" d="M261.049 63.836c-.08 0-.24 0-.321-.08L241.09 52.45l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L243.495 52.45l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cz)" d="M242.292 74.66c-.08 0-.24-.001-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801 0 .24-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cA)" d="M223.616 85.482c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32"/>
+    <path fill="url(#cB)" d="M204.939 96.226c-.08 0-.241 0-.321-.08L185.06 84.84l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L187.384 84.84l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cC)" d="M186.262 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#cD)" d="M167.585 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.32.321-.481.321"/>
+    <path fill="url(#cE)" d="M148.909 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cF)" d="M130.232 139.439c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#cG)" d="M373.189 20.703c-.08 0-.24 0-.32-.08L353.31 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L355.635 9.318 373.43 19.58c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+    <path fill="url(#cH)" d="M354.433 31.526c-.081 0-.241 0-.321-.08L334.553 20.14l19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802L336.878 20.14l17.795 10.263c.321.16.401.56.24.801-.08.16-.24.321-.48.321" opacity=".3"/>
+    <path fill="url(#cI)" d="M335.756 42.27c-.08 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cJ)" d="M317.079 53.092c-.08 0-.24 0-.32-.08L297.2 41.708l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262L317.32 51.97c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cK)" d="M298.402 63.836c-.08 0-.24 0-.32-.08L278.523 52.45l19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802L280.928 52.45l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.562.32" opacity=".6"/>
+    <path fill="url(#cL)" d="M279.726 74.659c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#cM)" d="M261.049 85.482c-.08 0-.24 0-.321-.08L241.09 74.098l19.558-11.305c.321-.16.642-.08.802.24.16.322.08.642-.241.803l-17.714 10.262L261.29 84.36c.32.16.4.561.24.802-.08.16-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cN)" d="M242.292 96.225c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L224.738 84.84l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cO)" d="M223.616 107.049c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321"/>
+    <path fill="url(#cP)" d="M204.939 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.241.321-.481.321"/>
+    <path fill="url(#cQ)" d="M186.262 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#cR)" d="M167.585 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#cS)" d="M148.909 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cT)" d="M130.232 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cU)" d="M373.189 42.27c-.08 0-.24 0-.32-.081L353.31 30.885l19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801-.08.241-.32.321-.481.321" opacity=".2"/>
+    <path fill="url(#cV)" d="M354.433 53.092c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cW)" d="M335.756 63.836c-.08 0-.241 0-.321-.08L315.877 52.45l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.281 52.45l17.796 10.262c.32.16.4.562.24.802s-.321.32-.561.32" opacity=".4"/>
+    <path fill="url(#cX)" d="M317.079 74.659c-.08 0-.24 0-.32-.08L297.2 63.275l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cY)" d="M298.402 85.483c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.401.32-.562.32" opacity=".6"/>
+    <path fill="url(#cZ)" d="M279.726 96.226c-.08 0-.241 0-.321-.08L259.847 84.84l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 84.84l17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#da)" d="M261.049 107.049c-.08 0-.24 0-.321-.08L241.17 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#db)" d="M242.292 117.792c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.401.561.24.801 0 .241-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#dc)" d="M223.616 128.615c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#dd)" d="M204.939 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321"/>
+    <path fill="url(#de)" d="M186.262 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#df)" d="M167.585 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#dg)" d="M148.909 171.829c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#dh)" d="M130.232 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321"/>
+    <g opacity=".9">
+      <path fill="url(#di)" d="M373.189 63.836c-.08 0-.24 0-.32-.08L353.23 52.45l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L355.635 52.45l17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dj)" d="M354.433 74.659c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dk)" d="M335.756 85.482c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.321.32-.561.32" opacity=".4"/>
+      <path fill="url(#dl)" d="M317.079 96.226c-.08 0-.24 0-.32-.08L297.2 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L299.525 84.84l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#dm)" d="M298.402 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dn)" d="M279.726 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.801a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#do)" d="M261.049 128.615c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#dp)" d="M242.292 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dq)" d="M223.616 150.182c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321" opacity=".9"/>
+      <path fill="url(#dr)" d="M204.939 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".9"/>
+      <path fill="url(#ds)" d="M186.262 171.828c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dt)" d="M167.586 182.572c-.081 0-.241 0-.321-.081l-19.559-11.304 19.559-11.304c.321-.161.641-.081.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.321-.48.321" opacity=".9"/>
+      <path fill="url(#du)" d="M148.909 193.395c-.08 0-.241 0-.321-.08L129.03 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.161-.321.321-.481.321" opacity=".9"/>
+      <path fill="url(#dv)" d="M130.232 204.138c-.08 0-.24 0-.32-.08l-19.639-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <path fill="url(#dw)" d="M373.189 85.482c-.08 0-.24 0-.32-.08L353.23 74.098l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.715 10.262L373.43 84.36c.32.16.401.561.24.802-.08.16-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dx)" d="M354.433 96.225c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.304c.321-.16.641-.08.801.24s.081.641-.24.802L336.878 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+      <path fill="url(#dy)" d="M335.756 107.049c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#dz)" d="M317.079 117.792c-.08 0-.24 0-.32-.08L297.2 106.408l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dA)" d="M298.402 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+      <path fill="url(#dB)" d="M279.726 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.16.16-.401.321-.561.321" opacity=".7"/>
+      <path fill="url(#dC)" d="M261.049 150.182c-.08 0-.24 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dD)" d="M242.292 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dE)" d="M223.616 171.829c-.081 0-.241 0-.321-.081l-19.558-11.384 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.401-.561.401" opacity=".8"/>
+      <path fill="url(#dF)" d="M204.939 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".8"/>
+      <path fill="url(#dG)" d="M186.262 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.24.321-.481.321" opacity=".8"/>
+      <path fill="url(#dH)" d="M167.586 204.138c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.241s.081.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".8"/>
+      <path fill="url(#dI)" d="M148.909 214.962c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dJ)" d="M130.232 225.785c-.08 0-.24 0-.32-.08L110.353 214.4l19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801L112.678 214.4l17.795 10.262c.32.161.4.562.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <path fill="url(#dK)" d="M373.189 107.049c-.08 0-.24 0-.32-.08L353.31 95.664l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#dL)" d="M354.433 117.792c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dM)" d="M335.756 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#dN)" d="M317.079 139.439c-.08 0-.24 0-.32-.08L297.2 128.054l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.16-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dO)" d="M298.402 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dP)" d="M279.726 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#dQ)" d="M261.049 171.829c-.08 0-.24 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dR)" d="M242.292 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802 0 .241-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#dS)" d="M223.616 193.395c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dT)" d="M204.939 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.714 10.262 17.795 10.262c.32.16.4.561.24.802-.16.24-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dU)" d="M186.262 214.962c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.24.321-.481.321" opacity=".7"/>
+      <path fill="url(#dV)" d="M167.585 225.785c-.08 0-.24 0-.32-.08L147.706 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801L150.031 214.4l17.795 10.262c.321.161.401.562.24.802-.08.16-.32.321-.481.321" opacity=".7"/>
+      <path fill="url(#dW)" d="M148.909 236.528c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.321.321-.481.321" opacity=".7"/>
+      <path fill="url(#dX)" d="M130.232 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.321-.481.321" opacity=".7"/>
+    </g>
+    <g opacity=".6">
+      <path fill="url(#dY)" d="M373.189 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dZ)" d="M354.433 139.439c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.16-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#ea)" d="M335.756 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#eb)" d="M317.079 161.005c-.08 0-.24 0-.32-.08L297.2 149.621l19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#ec)" d="M298.402 171.829c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#ed)" d="M279.726 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#ee)" d="M261.049 193.395c-.08 0-.24 0-.321-.08L241.17 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#ef)" d="M242.292 204.138c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.561.32" opacity=".9"/>
+      <path fill="url(#eg)" d="M223.616 214.962c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.161.24-.321.321-.561.321" opacity=".6"/>
+      <path fill="url(#eh)" d="M204.939 225.785c-.08 0-.241 0-.321-.08L185.06 214.4l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801L187.384 214.4l17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321" opacity=".6"/>
+      <path fill="url(#ei)" d="M186.262 236.528c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".6"/>
+      <path fill="url(#ej)" d="M148.909 258.095c-.08 0-.241 0-.321-.08L129.03 246.71l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#ek)" d="M130.232 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#el)" d="M167.585 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <path fill="url(#em)" d="M373.189 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#en)" d="M354.433 161.005c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#eo)" d="M335.756 171.828c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ep)" d="M317.079 182.572c-.08 0-.24 0-.32-.081L297.2 171.187l19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.24-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#eq)" d="M298.402 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.161-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#er)" d="M279.726 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#es)" d="M261.049 214.961c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.304c.321-.161.642-.081.802.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#et)" d="M242.292 225.785c-.08 0-.24 0-.32-.08L222.413 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.08.641-.24.801L224.738 214.4l17.795 10.262c.32.161.401.562.24.802 0 .16-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#eu)" d="M148.909 279.741c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ev)" d="M130.232 290.484c-.08 0-.24 0-.32-.08L110.353 279.1l19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802L112.678 279.1l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ew)" d="M167.585 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".4"/>
+      <path fill="url(#ex)" d="M186.262 258.095c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.321-.481.321" opacity=".4"/>
+      <path fill="url(#ey)" d="M204.939 247.351c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ez)" d="M223.616 236.528c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.263c.321.16.401.561.241.801-.161.241-.321.321-.561.321" opacity=".4"/>
+    </g>
+    <path fill="#BDBEC2" d="M1587.89 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.08 0-.16.08-.33.08m-18.67-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l37.35-21.567c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-37.35 21.567c-.08.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l56.03-32.389c.32-.161.64-.081.8.24s.08.641-.24.802l-56.03 32.39c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l74.79-43.133c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-74.78 43.133c-.16.081-.25.081-.33.081m-18.67-10.824c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l93.46-53.957c.32-.16.64-.08.8.241s.08.641-.24.802l-93.46 53.956c-.16.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l112.14-64.78c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-112.14 64.78c-.16 0-.24.08-.32.08m-18.76-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l130.82-75.523c.32-.16.64-.08.8.241s.08.641-.24.802l-130.81 75.522c-.08.081-.17.081-.33.081m-18.67-10.744c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l149.49-86.346c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-149.49 86.346c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l168.17-97.09c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-168.17 97.089c-.08.08-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l186.93-107.912c.32-.16.64-.08.8.24s.08.642-.24.802l-186.92 107.913c-.17.08-.25.08-.33.08" opacity=".8"/>
+    <path fill="url(#eA)" d="M111.475 301.308c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.22 64.779c.321.161.401.562.24.802-.16.241-.32.321-.561.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.801.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.081L-.985 193.235c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.161.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .241-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.985 150.102c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .161-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.905 106.969c-.321-.161-.401-.562-.24-.802.16-.321.56-.401.8-.241l112.141 64.78c.321.16.401.561.24.802-.08.16-.32.321-.561.321m0-21.647c-.08 0-.24 0-.32-.08L-.985 85.322c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 63.755c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .24-.24.32-.481.32m0-21.566c-.08 0-.24 0-.32-.08L-.985 42.189c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 20.622c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.08L-.985-1.025c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.56.24.8 0 .241-.24.322-.481.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-22.591c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .24-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.08L-.985-44.158c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.22 64.78c.321.16.401.56.24.8-.08.241-.32.322-.561.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-65.724c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .16-.24.321-.481.321m18.757-10.823c-.08 0-.24 0-.32-.08L20.657-74.865c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24L130.473-12.81c.32.16.4.561.24.802-.08.24-.32.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08L58.01-74.784c-.32-.16-.4-.562-.24-.802.16-.32.561-.401.801-.24l90.578 52.272c.321.16.401.561.241.802-.08.16-.321.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-71.821-41.53c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24l71.821 41.529c.321.16.401.56.241.801-.081.24-.321.321-.481.321m18.676-10.823c-.08 0-.24 0-.32-.08l-53.145-30.707c-.32-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24L186.503-45.2c.32.16.401.562.24.802-.08.24-.24.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08l-34.467-19.884c-.321-.16-.401-.56-.241-.801.16-.32.561-.401.802-.24l34.467 19.882c.321.16.401.561.241.802-.08.16-.241.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-15.791-9.14c-.321-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24l15.791 9.139c.321.16.401.561.241.802-.081.24-.241.32-.481.32"/>
+    <path fill="url(#eB)" d="M1606.57 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eC)" d="M1606.57 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eD)" d="M1587.9 9.88c-.09 0-.25 0-.33-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eE)" d="M1587.9 31.526c-.09 0-.25 0-.33-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eF)" d="M1587.9 53.092c-.09 0-.25 0-.33-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eG)" d="M1569.22 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eH)" d="M1569.22 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eI)" d="M1569.22 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eJ)" d="M1550.54 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eK)" d="M1550.54 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eL)" d="M1550.54 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eM)" d="M1550.54 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eN)" d="M1531.86 20.703c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eO)" d="M1531.86 42.27c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.49.321"/>
+    <path fill="url(#eP)" d="M1531.86 63.836c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eQ)" d="M1513.19 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#eR)" d="M1513.19 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eS)" d="M1513.19 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eT)" d="M1513.19 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.48.321"/>
+    <path fill="url(#eU)" d="M1494.43 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eV)" d="M1494.43 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eW)" d="M1494.43 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eX)" d="M1475.75 9.88c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 8.757c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#eY)" d="M1475.75 31.526c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.49.32"/>
+    <path fill="url(#eZ)" d="M1475.75 53.092c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 51.97c.32.16.4.561.24.802-.08.16-.24.32-.49.32"/>
+    <path fill="url(#fa)" d="M1475.75 74.659c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.49.321"/>
+    <path fill="url(#fb)" d="M1457.08 20.703c-.08 0-.24 0-.32-.08L1437.2 9.317l19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.88 10.262c.32.16.4.561.24.802-.16.24-.32.32-.56.32"/>
+    <path fill="url(#fc)" d="M1457.08 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fd)" d="M1457.08 63.836c-.08 0-.24 0-.32-.08L1437.2 52.45l19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fe)" d="M1438.4 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#ff)" d="M1438.4 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fg)" d="M1438.4 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fh)" d="M1438.4 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fi)" d="M1457.08 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fj)" d="M1438.4 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fk)" d="M1494.43 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .16-.24.32-.48.32"/>
+    <path fill="url(#fl)" d="M1457.08 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.161.4.561.24.802-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fm)" d="M1438.4 117.792c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.561.24.801-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fn)" d="M1475.75 96.226c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#fo)" d="M1457.08 128.615c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.241s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fp)" d="M1438.4 139.438c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.304c.32-.161.64-.081.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fq)" d="M1475.75 117.792c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.561.24.801-.08.241-.24.321-.49.321"/>
+    <path fill="url(#fr)" d="M1494.43 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.161.4.561.24.802 0 .241-.24.321-.48.321"/>
+    <path fill="url(#fs)" d="M1513.19 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#ft)" d="M1531.86 85.482c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.49.32"/>
+    <path fill="url(#fu)" d="M1419.73 150.182c-.09 0-.25 0-.33-.08L1109.6-29.646c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.562.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-51.213c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.801-.08.241-.32.321-.48.321m0-21.566c-.09 0-.25 0-.33-.08L1109.6-72.779c-.32-.16-.4-.562-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.561.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-94.346c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1419.97 84.36c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.668c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.24-.48.24m0-21.567c-.09 0-.25 0-.33-.08L1109.6-137.56c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24l309.81 179.748c.32.16.4.56.24.801-.08.24-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1420.05 19.58c.32.16.4.561.24.802-.16.24-.4.32-.56.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24L1419.97-1.987c.32.16.4.562.24.802-.08.16-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08L1109.6-202.26c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.24L1419.97-45.2c.32.16.4.562.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.321-.48.321m0-21.647c-.09 0-.25 0-.33-.08l-309.8-179.667c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.161.4.561.24.802-.08.16-.32.24-.48.24m0-21.566c-.09 0-.25 0-.33-.08L1109.6-331.74c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.241-.48.241m18.67-10.743c-.08 0-.24 0-.32-.08L1131.16-340.88c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l306.92 178.064c.32.161.4.562.24.802-.08.16-.24.321-.48.321m18.68-10.824c-.08 0-.24 0-.32-.08l-90.58-52.273c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l90.58 52.273c.32.16.4.561.24.802-.08.24-.24.32-.48.32m18.68-10.823c-.09 0-.25 0-.33-.08l-71.82-41.53c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l71.83 41.53c.32.16.4.561.24.801-.08.241-.24.321-.48.321m18.67-10.743c-.08 0-.24 0-.32-.08l-53.14-30.707c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l53.14 30.706c.32.161.4.562.24.802 0 .161-.24.321-.48.321m18.76-10.824c-.08 0-.24 0-.32-.08l-34.47-19.883c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l34.47 19.883c.32.16.4.561.24.802-.08.24-.32.32-.48.32m18.68-10.743c-.08 0-.25 0-.33-.08l-15.79-9.14c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l15.8 9.14c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#fv)" d="M1606.57 538.7c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08L1419.4 387.574c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801-.08.161-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08L1419.4 365.927c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802-.08.24-.32.4-.56.4m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.561-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.81-.24l186.92 107.913c.32.16.4.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.08 0-.24 0-.32-.081l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.912c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l187 107.912c.32.161.4.562.24.802-.08.241-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+    <path fill="#BDBEC2" fill-opacity=".8" d="M92.799 592.656c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.823c.32-.161.641-.081.801.24s.081.641-.24.802l-18.677 10.823c-.08.08-.16.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.24-.801l37.354-21.567c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-37.353 21.567c-.08 0-.24.08-.321.08M55.445 571.09c-.24 0-.4-.08-.56-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.641-.08.801.241s.08.641-.24.802l-56.03 32.39c0 .08-.16.08-.24.08M36.77 560.266c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.24.16.321.08.642-.241.802L37.09 560.186c-.16.08-.24.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.561-.32-.16-.321-.08-.642.24-.802l93.464-53.957c.32-.16.641-.08.801.241s.081.641-.24.802l-93.464 53.956c-.08.08-.16.08-.24.08M-.585 538.7c-.24 0-.4-.08-.48-.321-.161-.321-.08-.641.24-.802l112.14-64.779c.321-.161.641-.08.802.24.16.321.08.642-.241.802L-.264 538.62c-.16.08-.24.08-.32.08m-.08-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.779c.32-.161.641-.081.801.24s.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801L-.344 473.92c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 452.273c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 409.14c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 365.927c-.08.08-.16.161-.32.161m0-21.647c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l93.463-53.956c.32-.16.641-.08.802.241.16.32.08.641-.24.801L-.345 344.361c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l74.787-43.133c.32-.161.64-.08.801.24.16.321.08.642-.24.802L-.344 322.794c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.64-.08.801.241.16.321.08.641-.24.802l-56.03 32.39c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l37.353-21.567c.32-.16.641-.08.801.241s.08.641-.24.802L-.344 279.661c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l18.676-10.823c.32-.161.642-.08.802.24.16.321.08.642-.24.802L-.345 258.014c-.08.081-.16.081-.32.081" opacity=".8"/>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="1368.02" x2="1377.97" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="1386.78" x2="1396.73" y1="174.458" y2="157.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="1405.46" x2="1415.41" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="1405.46" x2="1415.41" y1="163.634" y2="146.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="1293.32" x2="1303.27" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="1311.99" x2="1321.94" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="1330.67" x2="1340.62" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="1330.67" x2="1340.62" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="1349.35" x2="1359.3" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="1368.02" x2="1377.97" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="1349.35" x2="1359.3" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="1368.02" x2="1377.97" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="1386.78" x2="1396.73" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="1405.46" x2="1415.41" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="1386.78" x2="1396.73" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="1405.46" x2="1415.41" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="1237.21" x2="1247.15" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="1255.96" x2="1265.91" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="1255.96" x2="1265.91" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="1274.64" x2="1284.59" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="1293.32" x2="1303.27" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="1274.64" x2="1284.59" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="1293.32" x2="1303.26" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="1311.99" x2="1321.94" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="1330.67" x2="1340.62" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="1311.99" x2="1321.94" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="1330.67" x2="1340.62" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="1349.35" x2="1359.3" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="1368.02" x2="1377.97" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="1349.35" x2="1359.3" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="1368.02" x2="1377.97" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="1386.78" x2="1396.73" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="1405.46" x2="1415.41" y1="271.547" y2="254.32" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="1386.78" x2="1396.73" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="1405.46" x2="1415.41" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="1237.21" x2="1247.15" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="1255.96" x2="1265.91" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="1237.21" x2="1247.15" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="1255.96" x2="1265.91" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="1274.64" x2="1284.59" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="1293.32" x2="1303.26" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="1274.64" x2="1284.59" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="1293.32" x2="1303.27" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="1311.99" x2="1321.94" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="1330.67" x2="1340.62" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="1311.99" x2="1321.94" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="1330.67" x2="1340.62" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="1349.35" x2="1359.3" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="1368.02" x2="1377.87" y1="314.663" y2="297.493" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="1349.35" x2="1359.3" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="1368.02" x2="1377.97" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="1386.78" x2="1396.73" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="1405.46" x2="1415.41" y1="314.68" y2="297.453" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="1386.78" x2="1396.73" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="1405.46" x2="1415.41" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="1237.21" x2="1247.15" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="1255.96" x2="1265.91" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="1237.21" x2="1247.15" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="1255.96" x2="1265.91" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="1274.64" x2="1284.59" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="1293.32" x2="1303.27" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="1274.64" x2="1284.59" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="al" x1="1293.32" x2="1303.26" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="am" x1="1311.99" x2="1321.94" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="an" x1="1330.67" x2="1340.62" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="1311.99" x2="1321.94" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="1330.67" x2="1340.62" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="1349.35" x2="1359.3" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="1368.02" x2="1377.97" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="as" x1="1349.35" x2="1359.3" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="at" x1="1368.02" x2="1377.97" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="au" x1="1386.78" x2="1396.73" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="av" x1="1405.46" x2="1415.41" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="1386.78" x2="1396.73" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="1405.46" x2="1415.41" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="1237.21" x2="1247.15" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="az" x1="1255.96" x2="1265.91" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="1237.21" x2="1247.15" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="1255.96" x2="1265.91" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="1274.64" x2="1284.59" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="1293.32" x2="1303.26" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="1274.64" x2="1284.59" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="1293.32" x2="1303.27" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="1311.99" x2="1321.94" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="1330.67" x2="1340.62" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="1311.99" x2="1321.94" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="1330.67" x2="1340.62" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="1349.35" x2="1359.3" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="1368.02" x2="1377.97" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="1349.35" x2="1359.3" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="1368.02" x2="1377.97" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="1386.78" x2="1396.73" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="1405.46" x2="1415.41" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="1386.78" x2="1396.73" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="1405.46" x2="1415.41" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="1237.21" x2="1247.15" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="1255.96" x2="1265.91" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="1237.21" x2="1247.15" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="1255.96" x2="1265.91" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="1274.64" x2="1284.59" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="1293.32" x2="1303.27" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="1274.64" x2="1284.59" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="1293.32" x2="1303.27" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="1311.99" x2="1321.94" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="1330.67" x2="1340.62" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="1311.99" x2="1321.94" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="1330.67" x2="1340.62" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="be" x1="1349.35" x2="1359.3" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="1368.02" x2="1377.97" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="1349.35" x2="1359.3" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="1368.02" x2="1377.97" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="1386.78" x2="1396.73" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="1405.46" x2="1415.41" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="1386.78" x2="1396.73" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="1405.46" x2="1415.41" y1="422.673" y2="405.446" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="1237.21" x2="1247.15" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="1255.96" x2="1265.91" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="1237.21" x2="1247.15" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="1255.96" x2="1265.91" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="1274.64" x2="1284.59" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="br" x1="1293.32" x2="1303.26" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="1274.64" x2="1284.59" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="1293.32" x2="1303.26" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="1311.99" x2="1321.94" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="1330.67" x2="1340.62" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="1311.97" x2="1321.84" y1="454.965" y2="437.83" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="1330.67" x2="1340.62" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="by" x1="1349.35" x2="1359.3" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="1349.35" x2="1359.3" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="1368.02" x2="1377.97" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="1386.78" x2="1396.73" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="1237.21" x2="1247.15" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="1237.21" x2="1247.15" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="1255.96" x2="1265.91" y1="508.939" y2="491.712" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="1274.64" x2="1284.59" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="1274.64" x2="1284.59" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="1293.32" x2="1303.27" y1="508.939" y2="491.711" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="1311.99" x2="1321.94" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="110.366" x2="130.858" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="147.719" x2="168.212" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bL" x1="129.043" x2="149.535" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bM" x1="110.366" x2="130.858" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bN" x1="185.073" x2="205.565" y1="-1.541" y2="-1.541" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bO" x1="166.396" x2="186.888" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bP" x1="147.719" x2="168.212" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bQ" x1="129.043" x2="149.535" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bR" x1="110.366" x2="130.858" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bS" x1="222.426" x2="242.918" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bT" x1="203.749" x2="224.322" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bU" x1="185.073" x2="205.565" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bV" x1="166.396" x2="186.888" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bW" x1="147.719" x2="168.212" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bX" x1="129.043" x2="149.615" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bY" x1="110.366" x2="130.858" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bZ" x1="259.859" x2="280.432" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ca" x1="241.183" x2="261.675" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cb" x1="222.426" x2="242.918" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cc" x1="203.749" x2="224.322" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cd" x1="185.073" x2="205.565" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ce" x1="166.396" x2="186.969" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cf" x1="147.719" x2="168.212" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cg" x1="129.043" x2="149.615" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ch" x1="110.366" x2="130.858" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ci" x1="297.213" x2="317.705" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cj" x1="278.536" x2="299.029" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ck" x1="259.859" x2="280.432" y1="20.066" y2="20.066" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cl" x1="241.183" x2="261.675" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cm" x1="222.426" x2="242.918" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cn" x1="203.749" x2="224.322" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="co" x1="185.073" x2="205.565" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cp" x1="166.396" x2="186.969" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cq" x1="147.719" x2="168.212" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cr" x1="129.043" x2="149.535" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cs" x1="110.366" x2="130.858" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ct" x1="334.566" x2="355.059" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cu" x1="315.889" x2="336.382" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cv" x1="297.213" x2="317.705" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cw" x1="278.536" x2="299.029" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cx" x1="259.859" x2="280.432" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cy" x1="241.103" x2="261.675" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cz" x1="222.426" x2="242.918" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cA" x1="203.749" x2="224.322" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cB" x1="185.073" x2="205.565" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cC" x1="166.396" x2="186.888" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cD" x1="147.719" x2="168.212" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cE" x1="129.043" x2="149.535" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cF" x1="110.366" x2="130.858" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cG" x1="353.323" x2="373.815" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cH" x1="334.566" x2="355.059" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cI" x1="315.889" x2="336.382" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cJ" x1="297.213" x2="317.705" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cK" x1="278.536" x2="299.109" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cL" x1="259.859" x2="280.432" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cM" x1="241.103" x2="261.675" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cN" x1="222.426" x2="242.918" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cO" x1="203.749" x2="224.322" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cP" x1="185.073" x2="205.565" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cQ" x1="166.396" x2="186.888" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cR" x1="147.719" x2="168.212" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cS" x1="129.043" x2="149.535" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cT" x1="110.366" x2="130.858" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cU" x1="353.323" x2="373.815" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cV" x1="334.566" x2="355.059" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cW" x1="315.889" x2="336.463" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cX" x1="297.213" x2="317.705" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cY" x1="278.536" x2="299.109" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cZ" x1="259.859" x2="280.432" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="da" x1="241.183" x2="261.675" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="db" x1="222.426" x2="242.918" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dc" x1="203.749" x2="224.322" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dd" x1="185.073" x2="205.565" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="de" x1="166.396" x2="186.888" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="df" x1="147.719" x2="168.212" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dg" x1="129.043" x2="149.535" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dh" x1="110.366" x2="130.858" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="di" x1="353.243" x2="373.816" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dj" x1="334.566" x2="355.059" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dk" x1="315.889" x2="336.462" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dl" x1="297.213" x2="317.705" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dm" x1="278.536" x2="299.029" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dn" x1="259.859" x2="280.432" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="do" x1="241.183" x2="261.675" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dp" x1="222.426" x2="242.918" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dq" x1="203.749" x2="224.322" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dr" x1="185.073" x2="205.565" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ds" x1="166.396" x2="186.888" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dt" x1="147.719" x2="168.212" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="du" x1="129.042" x2="149.535" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dv" x1="110.286" x2="130.859" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dw" x1="353.243" x2="373.816" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dx" x1="334.566" x2="355.059" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dy" x1="315.889" x2="336.382" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dz" x1="297.213" x2="317.705" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dA" x1="278.536" x2="299.029" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dB" x1="259.859" x2="280.432" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dC" x1="241.183" x2="261.675" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dD" x1="222.426" x2="242.918" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dE" x1="203.749" x2="224.322" y1="160.369" y2="160.369" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dF" x1="185.073" x2="205.565" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dG" x1="166.396" x2="186.888" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dH" x1="147.719" x2="168.292" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dI" x1="129.043" x2="149.535" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dJ" x1="110.366" x2="130.858" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dK" x1="353.323" x2="373.815" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dL" x1="334.566" x2="355.059" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dM" x1="315.889" x2="336.382" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dN" x1="297.213" x2="317.705" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dO" x1="278.536" x2="299.029" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dP" x1="259.859" x2="280.432" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dQ" x1="241.183" x2="261.675" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dR" x1="222.426" x2="242.918" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dS" x1="203.749" x2="224.322" y1="181.976" y2="181.976" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dT" x1="185.073" x2="205.646" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dU" x1="166.396" x2="186.888" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dV" x1="147.719" x2="168.212" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dW" x1="129.043" x2="149.535" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dX" x1="110.366" x2="130.858" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dY" x1="353.323" x2="373.815" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dZ" x1="334.566" x2="355.059" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ea" x1="315.889" x2="336.382" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eb" x1="297.213" x2="317.705" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ec" x1="278.536" x2="299.029" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ed" x1="259.859" x2="280.432" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ee" x1="241.183" x2="261.675" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ef" x1="222.426" x2="242.999" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eg" x1="203.749" x2="224.322" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eh" x1="185.073" x2="205.565" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ei" x1="166.396" x2="186.888" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ej" x1="129.043" x2="149.535" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ek" x1="110.366" x2="130.858" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="el" x1="147.719" x2="168.212" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="em" x1="353.323" x2="373.815" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="en" x1="334.566" x2="355.059" y1="149.585" y2="149.585" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eo" x1="315.889" x2="336.382" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ep" x1="297.213" x2="317.705" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eq" x1="278.536" x2="299.029" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="er" x1="259.859" x2="280.432" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="es" x1="241.183" x2="261.675" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="et" x1="222.426" x2="242.918" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eu" x1="129.043" x2="149.535" y1="268.322" y2="268.322" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ev" x1="110.366" x2="130.858" y1="279.065" y2="279.065" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ew" x1="147.719" x2="168.212" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ex" x1="166.396" x2="186.888" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ey" x1="185.073" x2="205.565" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ez" x1="203.749" x2="224.322" y1="225.108" y2="225.108" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eA" x1="-1.227" x2="224.241" y1="112.671" y2="112.671" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".25"/>
+      <stop offset=".777" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="eB" x1="1586.71" x2="1607.2" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eC" x1="1586.71" x2="1607.2" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eD" x1="1568.03" x2="1588.52" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eE" x1="1568.03" x2="1588.52" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eF" x1="1568.03" x2="1588.52" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eG" x1="1549.35" x2="1569.84" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eH" x1="1549.35" x2="1569.84" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eI" x1="1549.35" x2="1569.84" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eJ" x1="1530.68" x2="1551.17" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eK" x1="1530.68" x2="1551.17" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eL" x1="1530.68" x2="1551.17" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eM" x1="1530.68" x2="1551.17" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eN" x1="1512" x2="1532.49" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eO" x1="1512" x2="1532.49" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eP" x1="1512" x2="1532.49" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eQ" x1="1493.32" x2="1513.81" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eR" x1="1493.32" x2="1513.81" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eS" x1="1493.32" x2="1513.81" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eT" x1="1493.32" x2="1513.81" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eU" x1="1474.57" x2="1495.06" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eV" x1="1474.57" x2="1495.06" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eW" x1="1474.57" x2="1495.06" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eX" x1="1455.89" x2="1476.38" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eY" x1="1455.89" x2="1476.38" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eZ" x1="1455.89" x2="1476.38" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fa" x1="1455.89" x2="1476.38" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fb" x1="1437.21" x2="1457.78" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fc" x1="1437.21" x2="1457.7" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fd" x1="1437.21" x2="1457.7" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fe" x1="1418.54" x2="1439.03" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ff" x1="1418.54" x2="1439.03" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fg" x1="1418.54" x2="1439.03" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fh" x1="1418.54" x2="1439.03" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fi" x1="1437.21" x2="1457.7" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fj" x1="1418.54" x2="1439.03" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fk" x1="1474.57" x2="1495.06" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fl" x1="1437.21" x2="1457.7" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fm" x1="1418.54" x2="1439.03" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fn" x1="1455.89" x2="1476.38" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fo" x1="1437.21" x2="1457.7" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fp" x1="1418.54" x2="1439.03" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fq" x1="1455.89" x2="1476.38" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fr" x1="1474.57" x2="1495.06" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fs" x1="1493.32" x2="1513.81" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ft" x1="1512" x2="1532.49" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fu" x1="1109.3" x2="1532.45" y1="-95.896" y2="-95.896" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="fv" x1="1513.16" x2="1513.16" y1="538.721" y2="149.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.12.x/img/nomad-panel-learn.svg b/content/nomad/v0.12.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..090a5b337a
--- /dev/null
+++ b/content/nomad/v0.12.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="#BDBEC2" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.12.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v0.12.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v0.12.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v0.12.x/img/nomad_fault_tolerance.png b/content/nomad/v0.12.x/img/nomad_fault_tolerance.png
new file mode 100644
index 0000000000..dcac5802a3
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad_fault_tolerance.png differ
diff --git a/content/nomad/v0.12.x/img/nomad_network_arch.png b/content/nomad/v0.12.x/img/nomad_network_arch.png
new file mode 100644
index 0000000000..554d0b85e1
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad_network_arch.png differ
diff --git a/content/nomad/v0.12.x/img/nomad_reference_diagram.png b/content/nomad/v0.12.x/img/nomad_reference_diagram.png
new file mode 100644
index 0000000000..b6e7ea2894
Binary files /dev/null and b/content/nomad/v0.12.x/img/nomad_reference_diagram.png differ
diff --git a/content/nomad/v0.12.x/img/og-image.png b/content/nomad/v0.12.x/img/og-image.png
new file mode 100644
index 0000000000..7faccf445c
Binary files /dev/null and b/content/nomad/v0.12.x/img/og-image.png differ
diff --git a/content/nomad/v0.12.x/img/pattern.svg b/content/nomad/v0.12.x/img/pattern.svg
new file mode 100644
index 0000000000..ce1eefa887
--- /dev/null
+++ b/content/nomad/v0.12.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="#BDBEC2" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v0.12.x/img/prometheus-targets.png b/content/nomad/v0.12.x/img/prometheus-targets.png
new file mode 100644
index 0000000000..f8c567f162
Binary files /dev/null and b/content/nomad/v0.12.x/img/prometheus-targets.png differ
diff --git a/content/nomad/v0.12.x/img/routing-table.png b/content/nomad/v0.12.x/img/routing-table.png
new file mode 100644
index 0000000000..28de2e8434
Binary files /dev/null and b/content/nomad/v0.12.x/img/routing-table.png differ
diff --git a/content/nomad/v0.12.x/img/running-jobs.png b/content/nomad/v0.12.x/img/running-jobs.png
new file mode 100644
index 0000000000..69e005ae47
Binary files /dev/null and b/content/nomad/v0.12.x/img/running-jobs.png differ
diff --git a/content/nomad/v0.12.x/img/sentinel.jpg b/content/nomad/v0.12.x/img/sentinel.jpg
new file mode 100644
index 0000000000..5ce7fa54b6
Binary files /dev/null and b/content/nomad/v0.12.x/img/sentinel.jpg differ
diff --git a/content/nomad/v0.12.x/img/terminal-circle.svg b/content/nomad/v0.12.x/img/terminal-circle.svg
new file mode 100644
index 0000000000..ea76caabc9
--- /dev/null
+++ b/content/nomad/v0.12.x/img/terminal-circle.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 50 50">
+  <circle cx="25" cy="25" r="25" fill="#FFF"/>
+</svg>
diff --git a/content/nomad/v0.12.x/img/traefik_ui.png b/content/nomad/v0.12.x/img/traefik_ui.png
new file mode 100644
index 0000000000..787a7df67e
Binary files /dev/null and b/content/nomad/v0.12.x/img/traefik_ui.png differ
diff --git a/content/nomad/v1.0.x/content/api-docs/acl-policies.mdx b/content/nomad/v1.0.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..25d7d11301
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,168 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+sidebar_title: ACL Policies
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/acl-tokens.mdx b/content/nomad/v1.0.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..28efc8da9c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,344 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+sidebar_title: ACL Tokens
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](https://learn.hashicorp.com/tutorials/nomad/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/agent.mdx b/content/nomad/v1.0.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..9e76313bc7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/agent.mdx
@@ -0,0 +1,728 @@
+---
+layout: api
+page_title: Agent - HTTP API
+sidebar_title: Agent
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "protocol_version_max": "3",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "protocol_version": "1",
+      "protocol_version_min": "0",
+      "snapshot_version_min": "0",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/allocations.mdx b/content/nomad/v1.0.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..8b763bc3ae
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/allocations.mdx
@@ -0,0 +1,805 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+sidebar_title: Allocations
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": "5000000000"
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2017-07-25T23:36:26.106431265Z",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400,
+    "ModifyTime": 1495747371794276400
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:3.2"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:3.2"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was singled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Task": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method | Path                       | Produces                   |
+| ------ | -------------------------- | -------------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/api/index.html#blocking-queries) and
+[required ACLs](/api/index.html#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`            | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed.  This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
diff --git a/content/nomad/v1.0.x/content/api-docs/client.mdx b/content/nomad/v1.0.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..e534fade8d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/client.mdx
@@ -0,0 +1,671 @@
+---
+layout: api
+page_title: Client - HTTP API
+sidebar_title: Client
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/deployments.mdx b/content/nomad/v1.0.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..250f38c29f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/deployments.mdx
@@ -0,0 +1,539 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+sidebar_title: Deployments
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/evaluations.mdx b/content/nomad/v1.0.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..02c576e2f5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,267 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+sidebar_title: Evaluations
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Priority": 50,
+  "Type": "service",
+  "TriggeredBy": "job-register",
+  "JobID": "example",
+  "JobModifyIndex": 52,
+  "NodeID": "",
+  "NodeModifyIndex": 0,
+  "Status": "complete",
+  "StatusDescription": "",
+  "Wait": 0,
+  "NextEval": "",
+  "PreviousEval": "",
+  "BlockedEval": "",
+  "FailedTGAllocs": null,
+  "ClassEligibility": null,
+  "EscapedComputedClass": false,
+  "AnnotatePlan": false,
+  "SnapshotIndex": 53,
+  "QueuedAllocations": {
+    "cache": 0
+  },
+  "CreateIndex": 53,
+  "ModifyIndex": 55
+}
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/events.mdx b/content/nomad/v1.0.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..3ae665496e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/events.mdx
@@ -0,0 +1,386 @@
+---
+layout: api
+page_title: Events - HTTP API
+sidebar_title: Events
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a servers backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management 
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock": "true",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "mock_driver": {
+              "Attributes": {
+                "driver.mock": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445193068-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/index.mdx b/content/nomad/v1.0.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..f3b3062050
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/index.mdx
@@ -0,0 +1,225 @@
+---
+layout: api
+page_title: HTTP API
+sidebar_title: HTTP API Overview
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+This documentation is only for the v1 API.
+
+~> **Backwards compatibility:** At the current version, Nomad does not yet
+promise backwards compatibility even with the v1 prefix. We'll remove this
+warning when this policy changes. We expect to reach API stability by Nomad
+1.0.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.0.x/content/api-docs/jobs.mdx b/content/nomad/v1.0.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..146d310cf0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2322 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+sidebar_title: Jobs
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "EnforceIndex": false,
+  "PreserveCounts": true,
+  "PolicyOverride": false,
+  "JobModifyIndex": 0,
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 300000000000,
+          "Attempts": 10,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 36000000000000,
+          "MaxDelay": 3600000000000,
+          "Unlimited": false
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300,
+          },
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `purge` `(bool: false)` - Specifies that the job should stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.0.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..e023a1f394
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1064 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+sidebar_title: JSON Jobs
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+This guide covers the JSON syntax for submitting jobs to Nomad. A useful command
+for generating valid JSON versions of HCL jobs is:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+## Syntax
+
+Below is the JSON representation of the job outputted by `$ nomad init`:
+
+```json
+{
+  "Job": {
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Datacenters": ["dc1"],
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Migrate": {
+          "HealthCheck": "checks",
+          "HealthyDeadline": 300000000000,
+          "MaxParallel": 1,
+          "MinHealthyTime": 10000000000
+        },
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "image": "redis:3.2",
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ]
+            },
+            "Services": [
+              {
+                "Id": "",
+                "Name": "redis-cache",
+                "Tags": ["global", "cache"],
+                "Meta": {
+                  "meta": "for my service"
+                },
+                "PortLabel": "db",
+                "AddressMode": "",
+                "Checks": [
+                  {
+                    "Id": "",
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Header": {},
+                    "Method": "",
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": "",
+                    "TLSSkipVerify": false,
+                    "CheckRestart": {
+                      "Limit": 3,
+                      "Grace": 30000000000,
+                      "IgnoreWarnings": false
+                    }
+                  }
+                ]
+              }
+            ],
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 256,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Leader": false
+          }
+        ],
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": {
+          "Attempts": 10,
+          "Delay": 30000000000,
+          "DelayFunction": "exponential",
+          "Interval": 0,
+          "MaxDelay": 3600000000000,
+          "Unlimited": true
+        },
+        "EphemeralDisk": {
+          "SizeMB": 300
+        }
+      }
+    ],
+    "Update": {
+      "MaxParallel": 1,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "AutoRevert": false,
+      "Canary": 0
+    }
+  }
+}
+```
+
+The example JSON could be submitted as a job using the following:
+
+```shell-session
+$ curl -XPUT -d @example.json http://127.0.0.1:4646/v1/job/example
+{
+  "EvalID": "5d6ded54-0b2a-8858-6583-be5f476dec9d",
+  "EvalCreateIndex": 12,
+  "JobModifyIndex": 11,
+  "Warnings": "",
+  "Index": 12,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+  - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+    checks do not have an `auto` address mode as there's no way for
+    Nomad to know which is the best address to use for checks. Consul
+    needs access to the address for any HTTP or TCP checks. Added in
+    Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+    from the `Service`.
+
+  - `PortLabel`: Specifies the label of the port on which the check will
+    be performed. Note this is the _label_ of the port and not the port
+    number unless `AddressMode: "driver"`. The port label must match one
+    defined in the Network stanza. If a port value was declared on the
+    `Service`, this will inherit from that value if not supplied. If
+    supplied, this value takes precedence over the `Service.PortLabel`
+    value. This is useful for services which operate on multiple ports.
+    `http` and `tcp` checks require a port while `script` checks do not.
+    Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+    later numeric ports may be used if `AddressMode: "driver"` is set on
+    the check.
+
+  - `Header`: Headers for HTTP checks. Should be an object where the values are an
+    array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+  - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+    certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update stanza can be specified at the job or task group level.
+When specified at the job, the update stanza is inherited by all task groups.
+When specified in both the job and in a task group, the stanzas are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /docs/commands/node/drain
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v1.0.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.0.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..4b9be86c1c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,38 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+sidebar_title: Libraries &amp; SDKs
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/master/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://godoc.org/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.0.x/content/api-docs/metrics.mdx b/content/nomad/v1.0.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..d2d5407732
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/metrics.mdx
@@ -0,0 +1,97 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+sidebar_title: Metrics
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/namespaces.mdx b/content/nomad/v1.0.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..91648f742b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,186 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+sidebar_title: Namespaces
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 31,
+    "Description": "Production API Servers",
+    "ModifyIndex": 31,
+    "Name": "api-prod",
+    "Quota": ""
+  },
+  {
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 5,
+    "Name": "default",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 31,
+  "Description": "Production API Servers",
+  "Quota": "",
+  "Hash": "N8WvePwqkp6J354eLJMKyhvsFdPELAos0VuBfMoVKoU=",
+  "ModifyIndex": 31,
+  "Name": "api-prod"
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Quota": "prod-quota"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/nodes.mdx b/content/nomad/v1.0.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..715979d002
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1088 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+sidebar_title: Nodes
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "0.10.0-dev",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 0,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2019-08-26T12:22:50+02:00"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 9,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.0.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..80faad2dee
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,216 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+sidebar_title: Autopilot
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:8300",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:8205",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/index.mdx b/content/nomad/v1.0.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..51a158d44a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: api
+page_title: Operator - HTTP API
+sidebar_title: Operator
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheudler configration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](https://learn.hashicorp.com/tutorials/nomad/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/docs/commands/operator) command.
+
+
+Please choose a sub-section in the navigation for more information
+
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/license.mdx b/content/nomad/v1.0.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..dcc554d503
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,106 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+sidebar_title: License
+description: |-
+  The /operator/license endpoints allow for setting and retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "temporary license customer",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "temporary-license",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
+
+## Updating the Nomad Enterprise License
+
+This endpoint updates the Nomad license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `PUT`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Sample Payload
+
+The payload is the raw license blob.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @nomad.license \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.0.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..c8bbbe7b67
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,118 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+sidebar_title: Raft
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[Consensus Protocol Guide]: /docs/internals/consensus
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.0.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..54030debce
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,157 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+sidebar_title: Scheduler
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. This API was introduced in
+Nomad 0.9 and currently supports enabling/disabling preemption. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "ModifyIndex": 5,
+    "SchedulerAlgorithm": "spread",
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler binpacks or spreads allocations on available nodes.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server stanza will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.0.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.0.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..83c712016e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,87 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+sidebar_title: Snapshot
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/docs/internals/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
+
diff --git a/content/nomad/v1.0.x/content/api-docs/plugins.mdx b/content/nomad/v1.0.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..f7e3392a60
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/plugins.mdx
@@ -0,0 +1,138 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+sidebar_title: Plugins
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/quotas.mdx b/content/nomad/v1.0.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..ea690e144c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/quotas.mdx
@@ -0,0 +1,353 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+sidebar_title: Quotas
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://github.com/hashicorp/nomad/blob/master/api/quota.go#L100-L131).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/recommendations.mdx b/content/nomad/v1.0.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..c4a0703c31
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,374 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+sidebar_title: Recommendations
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/regions.mdx b/content/nomad/v1.0.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..dd0559f09d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/regions.mdx
@@ -0,0 +1,37 @@
+---
+layout: api
+page_title: Regions - HTTP API
+sidebar_title: Regions
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.0.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..30edf189aa
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,151 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+sidebar_title: Scaling Policies
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/search.mdx b/content/nomad/v1.0.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..d739b400e9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/search.mdx
@@ -0,0 +1,121 @@
+---
+layout: api
+page_title: Search - HTTP API
+sidebar_title: Search
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```javascript
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.0.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..b60db7b8d3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,180 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+sidebar_title: Sentinel Policies
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+<EnterpriseAlert>
+This API endpoint and functionality only exists in
+Nomad Enterprise. This is not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/status.mdx b/content/nomad/v1.0.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..f56e328ba7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/status.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: Status - HTTP API
+sidebar_title: Status
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/system.mdx b/content/nomad/v1.0.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..6a8d5e4e6b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+sidebar_title: System
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/ui.mdx b/content/nomad/v1.0.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..bf591fe211
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/ui.mdx
@@ -0,0 +1,556 @@
+---
+layout: api
+page_title: UI
+sidebar_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/docs/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
diff --git a/content/nomad/v1.0.x/content/api-docs/validate.mdx b/content/nomad/v1.0.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..92f04330b5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/validate.mdx
@@ -0,0 +1,65 @@
+---
+layout: api
+page_title: Validate - HTTP API
+sidebar_title: Validate
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to a server. In the event a server can't be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.0.x/content/api-docs/volumes.mdx b/content/nomad/v1.0.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..afc447ce26
--- /dev/null
+++ b/content/nomad/v1.0.x/content/api-docs/volumes.mdx
@@ -0,0 +1,375 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+sidebar_title: Volumes
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` endpoints are used to query for and interact with volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "volume-id1",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "volume-id1",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:3.2"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. It is an error
+to register an existing volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that described the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume id1",
+      "Namespace": "default",
+      "ExternalID": "volume-id1",
+      "Topologies": [{ "foo": "bar" }],
+      "AccessMode": "multi-node-single-writer",
+      "AttachmentMode": "file-system",
+      "PluginID": "plugin-id1"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Delete Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)`- Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)`- Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)`- The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/agent.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/agent.mdx
new file mode 100644
index 0000000000..6c4f4c6dcc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/agent.mdx
@@ -0,0 +1,430 @@
+---
+layout: docs
+page_title: Agent
+sidebar_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.conf -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.conf`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+## General Parameters
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+## `http` Block
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+### `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
+
+## `nomad` Block
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+### `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+## `policy` Block
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+}
+```
+
+### `policy` Parameters
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+## `policy_eval` Block
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+### `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
+
+## `telemetry` Block
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+### `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus`
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+## `apm` Block
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+### `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+## `target` Block
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+### `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+## `strategy` Block
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+### `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  plugin_dir. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[nomad_acls]: https://learn.hashicorp.com/collections/nomad/access-control
+[autoscaler_cli_config]: /docs/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /docs/autoscaling/cli#policy-dir
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/api.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/api.mdx
new file mode 100644
index 0000000000..496173d0e4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/api.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: HTTP API
+sidebar_title: API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/cli.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/cli.mdx
new file mode 100644
index 0000000000..04429fa8f6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/cli.mdx
@@ -0,0 +1,176 @@
+---
+layout: docs
+page_title: CLI
+sidebar_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /docs/autoscaling/agent
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/index.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/index.mdx
new file mode 100644
index 0000000000..c5a37ac18e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Autoscaling
+sidebar_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. The source code can be viewed on [GitHub][autoscaler_github] and releases
+are available on the [HashiCorp releases page][autoscaler_releases] or via
+[Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the autoscaler.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/docs/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task stanza using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /docs/job-specification/scaling#scaling-stanza
+[autoscaling_policy]: /docs/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler/tree/master/demo
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/internals/checks.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/internals/checks.mdx
new file mode 100644
index 0000000000..0d19cb3940
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/internals/checks.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: Checks
+sidebar_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Nomad Autoscaler Check Calculations
+
+A scaling policy can include several checks all of which produce a scaling
+suggesting. The checks are executed at the same time during a policy evaluation
+and the results can conflict with each other. In a scenario like this, the
+autoscaler iterates the results the chooses the safest result which results in
+retaining the most capacity of the resource.
+
+In a scenario where two checks return different desired directions, the following
+logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the two same actions are suggested, but with different counts the
+following logic is applied, where the count is the absolute desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/internals/index.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/internals/index.mdx
new file mode 100644
index 0000000000..4def6a4be8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/internals/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Internals
+sidebar_title: Internals
+description: >
+  This section covers the internals of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Internals
+
+This section covers the internals of the Nomad Autoscaler and explains the
+technical details of how it functions, its architecture, and sub-systems.
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/plugins/apm.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/apm.mdx
new file mode 100644
index 0000000000..908cff2527
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/apm.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: APM
+sidebar_title: APM
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+APMs are used to store metrics about an applications performance and current
+state. The APM (Application Performance Management) plugin is responsible for
+querying the APM and returning a value which will be used to determine if
+scaling should occur.
+
+## Prometheus APM Plugin
+
+Use [Prometheus][prometheus_io] metrics to scale your Nomad job task groups or
+cluster.
+
+### Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+### Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}) and (haproxy_server_up{backend=\"http_back\"} == 1))"
+  ...
+}
+```
+
+## Datadog APM Plugin
+
+The [Datadog][datadog_homepage] APM allows using [time series][datadog_timeseries]
+data to make scaling decisions.
+
+### Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+  }
+}
+```
+
+- `dd_api_key` `(string: "")` - The Datadog API key to use for authentication.
+- `dd_app_key` `(string: "")` - The Datadog APP key to use for authentication.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+### Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  ...
+}
+```
+
+## Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+### Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+### Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+### Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "percentage-allocated_cpu"
+  ...
+}
+```
+
+Querying Nomad client node metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[prometheus_io]: https://prometheus.io/
+[prometheus_scaler_function]: https://prometheus.io/docs/prometheus/latest/querying/functions/#scalar
+[nomad_telemetry_stanza]: /docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/plugins/index.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..ab37e4f83e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: Plugins
+sidebar_title: Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task;
+APM plugins retrieve metrics about the workloads being monitored and Strategy
+plugins decide which actions Nomad should execute to keep the policy valid. The
+flexibility of plugins allows the Nomad Autoscaler to be extended to meet specific
+business requirements or technology use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections.
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/plugins/strategy.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/strategy.mdx
new file mode 100644
index 0000000000..5980700679
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/strategy.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: Strategy
+sidebar_title: Strategy
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
+
+## Target Value Strategy Plugin
+
+The target value strategy plugin will perform count calculations in order to keep
+the value resulting from the APM query at or around a specified target.
+
+### Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check {
+  ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  ...
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+## Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the dataset.
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+### Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+## Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+### Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+## Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+### Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/plugins/target.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/target.mdx
new file mode 100644
index 0000000000..083856669d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/plugins/target.mdx
@@ -0,0 +1,362 @@
+---
+layout: docs
+page_title: Target
+sidebar_title: Target
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target Plugins determine where the resource to be autoscaled is located. All
+target plugins support the `dry-run` policy config parameter which allows a policy
+to be evaluated, but will noop any suggested changes.
+
+Below is a list of plugins you can use with the Nomad Autoscaler:
+
+- [Nomad Task Group][nomad_task_group_target]
+- [Dynamic Application Sizing Nomad Task][das_task_target]
+- [AWS AutoScaling Group][aws_asg_target]
+- [Azure Virtual Machine Scale Set][azure_vmss_target]
+
+## Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+### Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad"
+}
+```
+
+### Policy Configuration Options
+
+If using the [Nomad job specification scaling stanza][nomad_scaling_stanza] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` stanza][nomad_job_stanza].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` stanza][nomad_group_stanza].
+
+## Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+### Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+### Policy Configuration Options
+
+If using the [Nomad job specification scaling stanza][nomad_scaling_stanza] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` stanza][nomad_job_stanza].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` stanza][nomad_group_stanza].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` stanza][nomad_task_stanza].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` stanza][nomad_resource_stanza]. Supports either `CPU`
+  or `MemoryMB`.
+
+## AWS AutoScaling Group Target
+
+The AWS ASG target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+### Agent Configuration Options
+
+To use the AWS ASG target plugin, the agent configuration needs to be populated
+with the appropriate target block. Authentication to the AWS API can be supplied
+in a number of ways including EC2 instance roles. It is recommended, if possible
+to use the [Vault AWS Secrets engine][vault_aws_backend] for supplying access
+credentials to the plugin. Credentials should be injected into the configuration
+via a template rather than as environment variables. This ensures the credentials
+are passed only to the plugin, rather than being available for all plugins and
+the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "ec2:TerminateInstances",
+        "ec2:DescribeInstanceStatus",
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DetachInstances",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token which provides
+the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+### Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  ...
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `node_class` `(string: <required>)` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain deadline][nomad_node_drain_deadline]
+  to use when performing node draining actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad clients should
+  be [purged][nomad_node_purge] when performing scale in actions.
+
+## Azure Virtual Machine Scale Set Target
+
+The Azure VMSS target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Azure Virtual Machine Scale Sets][azure_virtual_machine_scale_sets].
+
+~> The Azure VMSS target plugin requires Azure fingerprinting, which became
+available in Nomad 1.0. If you are running a previous version of Nomad you will
+to set a [meta tag][client_meta_tag] in all of your nodes.
+
+### Agent Configuration Options
+
+To use the Azure VMSS target plugin, the agent configuration needs to be populated
+with the appropriate target block. Authentication to the Azure API can be supplied
+in a number of ways.
+
+#### Virtual Machine Identities
+
+When using [virtual machine identities][vm_identity] you will need to provide a
+user-managed identity with the `Contributor` role and set the `subscription_id`
+in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+#### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the
+[Vault Azure Secrets engine][vault_azure_backend] for supplying access
+credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in Azure
+  Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+#### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+### Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  ...
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource group][azure_resource_group]
+  within which the virtual machine scale set resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `node_class` `(string: <required>)` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain deadline][nomad_node_drain_deadline]
+  to use when performing node draining actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad clients should
+  be [purged][nomad_node_purge] when performing scale in actions.
+
+### Client meta tag
+
+The Azure VMSS target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][client_meta_tag_docs] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the
+[Azure Instance Metadata service][azure_instance_metadata].
+
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_scaling_stanza]: /docs/job-specification/scaling
+[nomad_group_stanza]: /docs/job-specification/group#group-stanza
+[nomad_job_stanza]: /docs/job-specification/job#job-stanza
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[vault_aws_backend]: https://www.vaultproject.io/docs/secrets/aws
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[nomad_recommendations_api]: /api-docs/recommendations
+[nomad_task_stanza]: /docs/job-specification/task#task-stanza
+[nomad_resource_stanza]: /docs/job-specification/resources#resources-stanza
+[nomad_namespace_parameter]: /docs/job-specification/job#namespace
+[nomad_region_parameter]: /docs/job-specification/job#region
+[nomad_autoscaler_policy]: /docs/autoscaling/policy
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[vault_azure_backend]: https://www.vaultproject.io/docs/secrets/azure
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[nomad_task_group_target]: /docs/autoscaling/plugins/target#nomad-task-group-target
+[aws_asg_target]: /docs/autoscaling/plugins/target#aws-autoscaling-group-target
+[azure_vmss_target]: /docs/autoscaling/plugins/target#azure-virtual-machine-scale-set-target
+[vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag_docs]: https://www.nomadproject.io/docs/configuration/client#meta
+[client_meta_tag]: /docs/autoscaling/plugins/target#client-meta-tag
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[das_task_target]: /docs/autoscaling/plugins/target#dynamic-application-sizing-nomad-task-target
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/policy.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/policy.mdx
new file mode 100644
index 0000000000..c721756016
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/policy.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: Scaling Policies
+sidebar_title: Policy
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` stanza][jobspec_scaling_stanza]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` stanza can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target_value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+This functionality only exists in Nomad Autoscaler
+Enterprise. This is not present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` stanza][jobspec_scaling_stanza] for Dynamic Application
+Sizing, the stanza requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[policy_default_cooldown_agent]: /docs/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /docs/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /docs/autoscaling/plugins/target
+[strategy_plugin_docs]: /docs/autoscaling/plugins/strategy
+[apm_plugin_docs]: /docs/autoscaling/plugins/apm
+[jobspec_scaling_stanza]: /docs/job-specification/scaling
diff --git a/content/nomad/v1.0.x/content/docs/autoscaling/telemetry.mdx b/content/nomad/v1.0.x/content/docs/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..90b511ed0d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/autoscaling/telemetry.mdx
@@ -0,0 +1,272 @@
+---
+layout: docs
+page_title: Telemetry
+sidebar_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /docs/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..e29c3c18d3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+sidebar_title: bootstrap
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Bootstrap the initial token:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..7c81e4c813
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+sidebar_title: acl
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /docs/commands/acl/bootstrap
+[policyapply]: /docs/commands/acl/policy-apply
+[policydelete]: /docs/commands/acl/policy-delete
+[policyinfo]: /docs/commands/acl/policy-info
+[policylist]: /docs/commands/acl/policy-list
+[tokencreate]: /docs/commands/acl/token-create
+[tokenupdate]: /docs/commands/acl/token-update
+[tokendelete]: /docs/commands/acl/token-delete
+[tokeninfo]: /docs/commands/acl/token-info
+[tokenlist]: /docs/commands/acl/token-list
+[tokenself]: /docs/commands/acl/token-self
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..0eb91ca482
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+sidebar_title: policy apply
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..589ed314a3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+sidebar_title: policy delete
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..534dd72f3e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+sidebar_title: policy info
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..1b36f673ca
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+sidebar_title: policy list
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..c2483074e0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+sidebar_title: token create
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..f9b0b4dec8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+sidebar_title: token delete
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..48d7c99ca9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+sidebar_title: token info
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..88be711418
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+sidebar_title: token list
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..f07b62612f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+sidebar_title: token self
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v1.0.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..af7975f9e8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+sidebar_title: token update
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.0.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..bf14ae6a99
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+sidebar_title: agent-info
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/agent.mdx b/content/nomad/v1.0.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..e21c45b03f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/agent.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+sidebar_title: agent
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /docs/configuration/consul#address
+[alloc_dir]: /docs/configuration/client#alloc_dir
+[auth]: /docs/configuration/consul#auth
+[auto_advertise]: /docs/configuration/consul#auto_advertise
+[bind_addr]: /docs/configuration#bind_addr
+[bootstrap_expect]: /docs/configuration/server#bootstrap_expect
+[ca_file]: /docs/configuration/consul#ca_file
+[cert_file]: /docs/configuration/consul#cert_file
+[checks_use_advertise]: /docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /docs/configuration/consul#client_auto_join
+[client_http_check_name]: /docs/configuration/consul#client_http_check_name
+[client_service_name]: /docs/configuration/consul#client_service_name
+[configuration]: /docs/configuration
+[data_dir]: /docs/configuration#data_dir
+[datacenter]: /docs/configuration#datacenter
+[enabled]: /docs/configuration/acl#enabled
+[encryption overview]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption
+[key_file]: /docs/configuration/consul#key_file
+[log_json]: /docs/configuration#log_json
+[log_level]: /docs/configuration#log_level
+[meta]: /docs/configuration/client#meta
+[name]: /docs/configuration#name
+[network_interface]: /docs/configuration/client#network_interface
+[node_class]: /docs/configuration/client#node_class
+[nomad agent]: /docs/install/production/nomad-agent
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: /docs/configuration#region
+[rejoin_after_leave]: /docs/configuration/server#rejoin_after_leave
+[replication_token]: /docs/configuration/acl#replication_token
+[retry_interval]: /docs/configuration/server#retry_interval
+[retry_max]: /docs/configuration/server#retry_max
+[server_auto_join]: /docs/configuration/consul#server_auto_join
+[server_http_check_name]: /docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /docs/configuration/consul#server_serf_check_name
+[server_service_name]: /docs/configuration/consul#server_service_name
+[servers]: /docs/configuration/client#servers
+[ssl]: /docs/configuration/consul#ssl
+[state_dir]: /docs/configuration/client#state_dir
+[token]: /docs/configuration/consul#token
+[verify_ssl]: /docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..ad2ddcc3e2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+sidebar_title: exec
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..493bfe72c0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+sidebar_title: fs
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..d6f2c4e73e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+sidebar_title: alloc
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..a203576a95
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+sidebar_title: logs
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..40e07ddf8b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+sidebar_title: restart
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be restarted.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..8755565e81
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+sidebar_title: signal
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..111a4f989a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+sidebar_title: status
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.0.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..3e3b0f448e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+sidebar_title: stop
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..fc2ec2391e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+sidebar_title: fail
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..d5eb0bb24c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+sidebar_title: deployment
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /docs/commands/deployment/list 'List all deployments'
+[pause]: /docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..141d3bbf47
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+sidebar_title: list
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..e41fa59e4d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+sidebar_title: pause
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..0d788f9b86
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+sidebar_title: promote
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..efac04be8a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+sidebar_title: resume
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..805ac72f7a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+sidebar_title: status
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       2        2       2        0
+web         2        2       2        0
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       0        0
+web         N/A       2        0         2       2        0
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.0.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..0db68a4f2c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+sidebar_title: unblock
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
diff --git a/content/nomad/v1.0.x/content/docs/commands/eval-status.mdx b/content/nomad/v1.0.x/content/docs/commands/eval-status.mdx
new file mode 100644
index 0000000000..eb7aaeaf76
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/eval-status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+sidebar_title: eval status
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output the evaluation in its JSON format.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/index.mdx b/content/nomad/v1.0.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..affda0b623
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Commands (CLI)
+sidebar_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash or zsh shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.0.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..2535267949
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+sidebar_title: deployments
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.0.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..d7ea4d523d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+sidebar_title: dispatch
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+[eval status]: /docs/commands/eval-status
+[parameterized job]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.0.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..a64f2b4b21
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+sidebar_title: eval
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/history.mdx b/content/nomad/v1.0.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..da12e50f46
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+sidebar_title: history
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/index.mdx b/content/nomad/v1.0.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..8026c0fb74
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: job'
+sidebar_title: job
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /docs/commands/job/promote "Promote a job's canaries"
+[revert]: /docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/init.mdx b/content/nomad/v1.0.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..217f29cb45
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+sidebar_title: init
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[drivers]: /docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.0.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..88cb69e17d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+sidebar_title: inspect
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /api-docs/jobs
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.0.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..6a93007dbd
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+sidebar_title: periodic force
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /docs/commands/eval-status
+[force the evaluation]: /api-docs/jobs#force-new-periodic-instance
+[periodic job]: /docs/job-specification/periodic
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.0.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..e13b1e729b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,210 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+sidebar_title: plan
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:3.2"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+[job specification]: /docs/job-specification
+[hcl job specification]: /docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /docs/commands/job/run#check-index
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.0.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..41db172d06
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+sidebar_title: promote
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`list-jobs`, and `read-job` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.0.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..845ca26be1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,125 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+sidebar_title: revert
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:3.2"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /docs/commands/job/history
+[eval status]: /docs/commands/eval-status
+[consul service identity]: /docs/configuration/consul#allow_unauthenticated
+[vault policy]: /docs/configuration/vault#allow_unauthenticated
+[run]: /docs/commands/job/run
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/run.mdx b/content/nomad/v1.0.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..1586c21338
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,153 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+sidebar_title: run
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions and placement information for the provided job. The monitor will
+exit after scheduling has finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-vault-token`: If set, the passed Vault token is stored in the job before
+  sending to the Nomad servers. This allows passing the Vault token without
+  storing it in the job file. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable and that found in the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement:
+
+```shell-session
+$ nomad job run job1.nomad
+==> Monitoring evaluation "52dee78a"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+    Allocation "5e0b39f0" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "52dee78a" finished with status "complete"
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> Monitoring evaluation "5ef16dff"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "62eb607c"
+    Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5ef16dff" finished with status "complete"
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> Monitoring evaluation "2ae0e6a5"
+    Evaluation triggered by job "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /docs/commands/job/plan
+[eval status]: /docs/commands/eval-status
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.0.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..1e2ecbe2ca
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+sidebar_title: scale
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `scale-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.0.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..008e83de5a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+sidebar_title: scaling-events
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/status.mdx b/content/nomad/v1.0.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..b8c72c6cae
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+sidebar_title: status
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.0.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..2eb262de0d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+sidebar_title: stop
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /docs/commands/eval-status
+[multi-region]: /docs/job-specification/multiregion
diff --git a/content/nomad/v1.0.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.0.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..b5523867c2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+sidebar_title: validate
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## Examples
+
+Validate a job with invalid syntax:
+
+```shell-session
+$ nomad job validate example.nomad
+Job validation errors:
+1 error(s) occurred:
+
+* group "cache" -> task "redis" -> config: 1 error(s) occurred:
+
+* field "image" is required
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v1.0.x/content/docs/commands/license/get.mdx b/content/nomad/v1.0.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..8bd6164173
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+sidebar_title: get
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise license.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/license/index.mdx b/content/nomad/v1.0.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..42e6e6d91f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: license'
+sidebar_title: license
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+- [`license put`][put] - Set the current license
+
+[get]: /docs/commands/license/get 'Get the current license'
+[put]: /docs/commands/license/put 'Set the current license'
diff --git a/content/nomad/v1.0.x/content/docs/commands/license/put.mdx b/content/nomad/v1.0.x/content/docs/commands/license/put.mdx
new file mode 100644
index 0000000000..77e9e74caf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/license/put.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: license put'
+sidebar_title: put
+description: |
+  The license put command is used to set the Nomad Enterprise license.
+---
+
+# Command: license put
+
+The `license put` command is used to set the Nomad Enterprise license.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license put
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Put Options
+
+```plaintext
+Install a new license from a file:
+
+        $ nomad license put <path>
+
+Install a new license from stdin:
+
+        $ nomad license put -
+```
+
+## Examples
+
+Set a license using a path
+
+```shell-session
+$ nomad license put /path/to/my/license.txt
+```
+
+Set a license using a path
+
+```shell-session
+$ nomad license put -
+
+02MV4UU43BK5HGYYTOJZWFQMTMNNEWU33JLJKES6S2NJMXUWLKIV2E2RCCNRMXSMBQLJKFSM2MK5KTKTLKLF2FS6SJPFNFIYZVJV5GI2S2K5LGUSLJO5UVSM2WPJSEOOLULJMEUZTBK5IWST3JJF5E4VCBPJHFIWTMJZJTANCZK5LGUTCXJJVVU2SRORHUIVLYJVBTC2KNNJATCTKEMM2VSMSONBNEISLJJRBUU4DCNZHDAWKXPBZVSWCSOBRDENLGMFLVC2KPNFEXCSLJO5UWCWCOPJSFOVTGMRDWY5C2KNETMSLKJF3U22SBORGUIVLUJVCGQVKNKRITMTLKJU3E26TDOVHHURJRJVVEC52NPJATGV3JJFZUS3SOGBMVQSRQLAZVE4DCK5KWST3JJF4U2RCJO5GFIQJRJRKECNCWIRAXOT3KIF3U62SBO5LWSSLTJFWVMNDDI5WHSWKYKJYGEMRVMZSEO3DULJJUSNSJNJEXOTLKIF2E2RCVORGUI3CVJVCECNSNIRATMTKEIJQUS2LXNFSEOVTZMJLWY5KZLBJHAYRSGVTGIR3MORNFGSJWJFVES52NNJAXITKEKV2E2VCCKVGUIQJWJVCECNSNIRBGCSLJO5UWGSCKOZNEQVTKMRBUSNSJNU2XMYSXIZVUS2LXNFNG26DILIZU22KPNZZWSYSXHFVWIV3YNRRXSSJWK54UU3TCGNNGYY3NGVUGE3KONRGFQQ
+
+<ctrl-d>
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/monitor.mdx b/content/nomad/v1.0.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..1286e2aecc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+sidebar_title: monitor
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..04935a0a62
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+sidebar_title: apply
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <namespace>
+```
+
+The `namespace apply` command requires the name of the namespace to be created
+or updated.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..3a409b8775
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+sidebar_title: delete
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..b2e8a79a85
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+sidebar_title: namespace
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /docs/commands/namespace/list 'List available namespaces'
+[status]: /docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..ac1e936180
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+sidebar_title: inspect
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..7b07e9dde8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+sidebar_title: list
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.0.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..298ca550af
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+sidebar_title: status
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name        = default
+Description = Default shared namespace
+Quota       = shared-default-quota
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/node/config.mdx b/content/nomad/v1.0.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..ddf82c3eae
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+sidebar_title: config
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /docs/configuration/client#servers
diff --git a/content/nomad/v1.0.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.0.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..f77bdc7a29
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+sidebar_title: drain
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] stanza until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are force removed from the
+  node. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Force remove allocations off the node immediately.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node
+  without being force stopped after a certain deadline.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs are stopped
+  last. You should always use this flag when draining a node running
+  [CSI node plugins][internals-csi].
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /docs/commands/node/eligibility
+[migrate]: /docs/job-specification/migrate
+[node status]: /docs/commands/node/status
+[workload migration guide]: https://learn.hashicorp.com/tutorials/nomad/node-drain
+[internals-csi]: /docs/internals/plugins/csi
diff --git a/content/nomad/v1.0.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.0.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..6b1a3c71b7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+sidebar_title: eligibility
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /docs/commands/node/drain
diff --git a/content/nomad/v1.0.x/content/docs/commands/node/index.mdx b/content/nomad/v1.0.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..d5563d4cb8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: node'
+sidebar_title: node
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /docs/commands/node/config 'View or modify client configuration details'
+[drain]: /docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.0.x/content/docs/commands/node/status.mdx b/content/nomad/v1.0.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..1f23d2febf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,367 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+sidebar_title: status
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-get-config.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-get-config.mdx
new file mode 100644
index 0000000000..100464cdff
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-get-config.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+sidebar_title: autopilot get-config
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-set-config.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-set-config.mdx
new file mode 100644
index 0000000000..d4697b87d1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/autopilot-set-config.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+sidebar_title: autopilot set-config
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /docs/configuration/server#upgrade_version
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..70464c801a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+sidebar_title: debug
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to 
+true.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the log monitor command.
+  Defaults to `"2m"`. Logs will be captured from specified servers and
+  nodes at `log-level`.
+
+- `-interval=2m`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included 
+  in the capture.  Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids,
+  to monitor for logs and include pprof profiles. Accepts id prefixes, and 
+  "all" to select all nodes (up to count = max-nodes).
+
+- `pprof-duration=<duration>`: Duration for pprof collection. Defaults to 1s.
+
+- `-server-id=s1,s2`: Comma separated list of Nomad server names, "leader", or
+  "all" to monitor for logs and include pprof profiles.
+
+- `stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped 
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..f44daa7b7f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+sidebar_title: operator
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[get-config]: /docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /api-docs/operator 'Operator API documentation'
+[outage recovery guide]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
+[remove]: /docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
+[snapshot-save]: /docs/commands/operator/snapshot-save 'Snapshot Save command'
+[snapshot-restore]: /docs/commands/operator/snapshot-restore 'Snapshot Restore command'
+[snapshot-inspect]: /docs/commands/operator/snapshot-inspect 'Snapshot Inspect command'
+[snapshot-agent]: /docs/commands/operator/snapshot-agent 'Snapshot Agent command'
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..a752bfe47e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+sidebar_title: keygen
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe" base64
+alphabet. If you use another tool such as OpenSSL to generate the gossip key,
+you should pipe the input through the `base64(1)` command to ensure it is
+safely encoded. For example: `openssl rand 32 | base64`
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[RFC4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..05dfdf91d9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+sidebar_title: keyring
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..7ddf0eac2c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+sidebar_title: metrics
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/raft-list-peers.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/raft-list-peers.mdx
new file mode 100644
index 0000000000..a46b04b7e8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/raft-list-peers.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+sidebar_title: raft list-peers
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The Raft list-peers command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /api-docs/operator
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/raft-remove-peer.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/raft-remove-peer.mdx
new file mode 100644
index 0000000000..75400bede8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/raft-remove-peer.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+sidebar_title: raft remove-peer
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /docs/commands/server/members 'Nomad server members command'
+[operator]: /api-docs/operator 'Nomad Operator API'
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-agent.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-agent.mdx
new file mode 100644
index 0000000000..3c6519ef00
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-agent.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+sidebar_title: snapshot agent
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-inspect.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-inspect.mdx
new file mode 100644
index 0000000000..dc367f9fa5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-inspect.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+sidebar_title: snapshot inspect
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-restore.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-restore.mdx
new file mode 100644
index 0000000000..22d4824670
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-restore.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+sidebar_title: snapshot restore
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-save.mdx b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-save.mdx
new file mode 100644
index 0000000000..0861387d20
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/operator/snapshot-save.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+sidebar_title: snapshot save
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.0.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.0.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..fee7edf365
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+sidebar_title: plugin
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[status]: /docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.0.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.0.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..ce6337cacd
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+sidebar_title: status
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6427deaa59
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+sidebar_title: apply
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..cce052371f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+sidebar_title: delete
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..264e91c1b1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+sidebar_title: quota
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /docs/commands/quota/apply
+[quotadelete]: /docs/commands/quota/delete
+[quotainit]: /docs/commands/quota/init
+[quotainspect]: /docs/commands/quota/inspect
+[quotalist]: /docs/commands/quota/list
+[quotastatus]: /docs/commands/quota/status
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..c0d1168e39
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+sidebar_title: init
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..b7cfa762d6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+sidebar_title: inspect
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..f0c424aa54
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+sidebar_title: list
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.0.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..b59fb0e5e5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+sidebar_title: status
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.0.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..a55c324580
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+sidebar_title: apply
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.0.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..413c8fc340
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+sidebar_title: dismiss
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.0.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..477b3f84a1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+sidebar_title: recommendation
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /docs/commands/recommendation/apply
+[recommendationdismiss]: /docs/commands/recommendation/dismiss
+[recommendationinfo]: /docs/commands/recommendation/info
+[recommendationlist]: /docs/commands/recommendation/list
diff --git a/content/nomad/v1.0.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.0.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..f3598e926b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+sidebar_title: info
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.0.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..39150c218f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+sidebar_title: list
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.0.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..f8a715dd0a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+sidebar_title: scaling
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /docs/commands/scaling/policy-info
+[scalingpolicylist]: /docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.0.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.0.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..d5dd32fbe6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+sidebar_title: policy info
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.0.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..7bab4e5a21
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+sidebar_title: policy list
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.0.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..2331719a8f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+sidebar_title: apply
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.0.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..a10e8bf148
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+sidebar_title: delete
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.0.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..d1db0d0fea
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+sidebar_title: sentinel
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /docs/commands/sentinel/delete
+[list]: /docs/commands/sentinel/list
+[read]: /docs/commands/sentinel/read
+[apply]: /docs/commands/sentinel/apply
diff --git a/content/nomad/v1.0.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.0.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..036a6fe036
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+sidebar_title: list
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.0.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..8c74946ed9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+sidebar_title: read
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.0.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..115a66569e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+sidebar_title: force-leave
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/server/index.mdx b/content/nomad/v1.0.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..a56135439b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: server'
+sidebar_title: server
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /docs/commands/server/join 'Join server nodes together'
+[members]: /docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.0.x/content/docs/commands/server/join.mdx b/content/nomad/v1.0.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..9e39a268ae
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+sidebar_title: join
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/server/members.mdx b/content/nomad/v1.0.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..35daf3079e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+sidebar_title: members
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in the
+  standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name          Addr      Port  Status  Proto  Build     DC   Region
+node1.global  10.0.0.8  4648  alive   2      0.1.0dev  dc1  global
+node2.global  10.0.0.9  4648  alive   2      0.1.0dev  dc1  global
+```
+
+Detailed view:
+
+```shell-session
+$ nomad server members -detailed
+Name   Addr      Port  Tags
+node1  10.0.0.8  4648  bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+node2  10.0.0.9  4648  bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/status.mdx b/content/nomad/v1.0.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..a57901788d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/status.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'Commands: status'
+sidebar_title: status
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.0.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1a81b72723
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+sidebar_title: gc
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/system/index.mdx b/content/nomad/v1.0.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..afdf094f9b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: system'
+sidebar_title: system
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.0.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.0.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..fcddebcf2f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+sidebar_title: reconcile summaries
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/ui.mdx b/content/nomad/v1.0.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..35780ec65f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/ui.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+sidebar_title: ui
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/version.mdx b/content/nomad/v1.0.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b3d756dd9e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/version.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: version'
+sidebar_title: version
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v1.0.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.0.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..399efcf663
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+sidebar_title: deregister
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be deregistered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.0.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.0.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..9f937a1168
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+sidebar_title: detach
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.0.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.0.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..67930c1555
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+sidebar_title: volume
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume register`][register] - Register a volume.
+- [`volume status`][status] - Display status information about a volume
+
+[deregister]: /docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /docs/commands/volume/detach 'Detach a volume'
+[register]: /docs/commands/volume/register 'Register a volume'
+[status]: /docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.0.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.0.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..f6cd65920e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+sidebar_title: register
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume
+must exist on the remote storage provider before it can be registered
+and used by a task.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying
+the path to a file containing a valid [volume
+specification][volume_specification]. This file will be read and the
+job will be submitted to Nomad for scheduling. If the supplied path is
+"-", the job file is read from STDIN. Otherwise it is read from the
+file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+The file may be provided as either HCL or JSON. An example HCL configuration:
+
+```hcl
+id = "ebs_prod_db1"
+name = "database"
+type = "csi"
+external_id = "vol-23452345"
+plugin_id = "ebs-prod"
+access_mode = "single-node-writer"
+attachment_mode = "file-system"
+mount_options {
+   fs_type = "ext4"
+   mount_flags = ["ro"]
+}
+secrets {
+   example_secret = "xyzzy"
+}
+parameters {
+    skuname = "Premium_LRS"
+}
+context {
+    endpoint = "http://192.168.1.101:9425"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This will
+  be how [`volume`][csi_volume] stanzas in a jobspec refer to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only
+  `"csi"` is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume
+  from the storage provider. For example, the volume ID of an AWS EBS
+  volume or Digital Ocean volume.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI
+  plugin][csi_plugin] that manages this volume.
+
+- `access_mode` `(string: <required>)` - Defines whether a volume
+  should be available concurrently. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only
+  single-node modes. Consult the documentation of the storage provider
+  and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. Most storage providers will support `"file-system"`, to mount
+  volumes using the CSI filesystem API. Some storage providers will support
+  `"block-device"`, which will mount the volume with the CSI block device API
+  within the container.
+
+- `mount_options` - Options for mounting `file-system` volumes that don't
+  already have a pre-formatted file system. Consult the documentation for your
+  storage provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `"ro,noatime"`)
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings used as credentials for publishing and
+  unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  configure the volume. The details of these parameters are specific
+  to each storage provider, so please see the specific plugin
+  documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  validate the volume. The details of these parameters are specific to
+  each storage provider, so please see the specific plugin
+  documentation for more information.
+
+[volume_specification]: #volume-specification
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volumes]: /docs/job-specification/volume
diff --git a/content/nomad/v1.0.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.0.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..403d93eff9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+sidebar_title: status
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify
+  times are shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.0.x/content/docs/configuration/acl.mdx b/content/nomad/v1.0.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..3513d2c03d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: acl Stanza - Agent Configuration
+sidebar_title: acl
+description: >-
+  The "acl" stanza configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Stanza
+
+<Placement groups={['acl']} />
+
+The `acl` stanza configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  client configuration options depend on this value.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region.
+
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.0.x/content/docs/configuration/audit.mdx b/content/nomad/v1.0.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..c1e11defd1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,296 @@
+---
+layout: docs
+page_title: audit Stanza - Agent Configuration
+sidebar_title: audit
+description: >-
+  The "audit" stanza configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Stanza
+
+<Placement groups={['audit']} />
+
+The `audit` stanza configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit stanza (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enable = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-stanza): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-stanza)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Stanza
+
+The `sink` stanza is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the stanza corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Stanza
+
+The `filter` stanza is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.0.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.0.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..4aef24733c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: autopilot Stanza - Agent Configuration
+sidebar_title: autopilot
+description: >-
+  The "autopilot" stanza configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Stanza
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` stanza configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.0.x/content/docs/configuration/client.mdx b/content/nomad/v1.0.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..b3c336f56f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/client.mdx
@@ -0,0 +1,458 @@
+---
+layout: docs
+page_title: client Stanza - Agent Configuration
+sidebar_title: client
+description: |-
+  The "client" stanza configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Stanza
+
+<Placement groups={['client']} />
+
+The `client` stanza configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks.
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, 20% of the node's CPU could be reserved to target a CPU utilization
+  of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension.
+
+- `bridge_network name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/docs/job-specification/template) stanzas.
+
+- `host_volume` <code>([host_volume](#host_volume-stanza): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-stanza): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/docs/drivers/exec#chroot) for
+the full list.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+   See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separated the two inclusive ends.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+### `host_volume` Stanza
+
+The `host_volume` stanza is used to make volumes available to jobs.
+
+The key of the stanza corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Stanza
+
+The `host_network` stanza is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the stanza corresponds to the name of the network used in the
+[`host_network`](/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[server-join]: /docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /docs/runtime/environment#task-directories 'Task directories'
diff --git a/content/nomad/v1.0.x/content/docs/configuration/consul.mdx b/content/nomad/v1.0.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..d16433e695
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,216 @@
+---
+layout: docs
+page_title: consul Stanza - Agent Configuration
+sidebar_title: consul
+description: |-
+  The "consul" stanza configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Stanza
+
+<Placement groups={['consul']} />
+
+The `consul` stanza configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` stanza is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the bind address.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](https://www.consul.io/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: https://learn.hashicorp.com/tutorials/nomad/clustering 'Automatic Bootstrapping'
diff --git a/content/nomad/v1.0.x/content/docs/configuration/index.mdx b/content/nomad/v1.0.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..73e1436c6d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/index.mdx
@@ -0,0 +1,375 @@
+---
+layout: docs
+page_title: Agent Configuration
+sidebar_title: Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this stanza take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most common
+    bind address to change.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this stanza take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address advertised to Nomad client nodes. This allows
+    advertising a different RPC address than is used by Nomad Servers such that
+    the clients can connect to the Nomad servers if they are behind a NAT.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+  ~> **WARNING**: This directory **must not** be set to a directory that is
+  [included in the chroot](/docs/drivers/exec#chroot) if you use the
+  [`exec`](/docs/drivers/exec) driver.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin stanza may be repeated, once for each plugin being
+  configured. The key of the stanza is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /docs/configuration/vault#vault-configuration-reloads
+[GH-3885]: https://github.com/hashicorp/nomad/issues/3885
diff --git a/content/nomad/v1.0.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.0.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..6f583cd7dc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: plugin Stanza - Agent Configuration
+sidebar_title: plugin
+description: The "plugin" stanza is used to configure a Nomad plugin.
+---
+
+# `plugin` Stanza
+
+<Placement groups={['plugin']} />
+
+The `plugin` stanza is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.0.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.0.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..f83d147321
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: sentinel Stanza - Agent Configuration
+sidebar_title: sentinel
+description: >-
+  The "sentinel" stanza configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Stanza
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` stanza configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.0.x/content/docs/configuration/server.mdx b/content/nomad/v1.0.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..3248cb8b1f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/server.mdx
@@ -0,0 +1,309 @@
+---
+layout: docs
+page_title: server Stanza - Agent Configuration
+sidebar_title: server
+description: |-
+  The "server" stanza configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Stanza
+
+<Placement groups={['server']} />
+
+The `server` stanza configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use -
+  for server-specific data, including the replicated log. By default, this is -
+  the top-level [data_dir](/docs/configuration#data_dir)
+  suffixed with "server", like `"/opt/nomad/server"`. This must be an absolute
+  path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator keygen`] command. The
+  provided key is automatically persisted to the data directory and loaded
+  automatically whenever the agent is restarted. This means that to encrypt
+  Nomad server's gossip protocol, this option only needs to be provided once
+  on each agent's initial startup sequence. If it is provided after Nomad has
+  been initialized with an encryption key, then the provided key is ignored
+  and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `protocol_version` `(int: 1)` - Specifies the Nomad protocol version to use
+  when communicating with other Nomad servers. This value is typically not
+  required as the agent internally knows the latest version, but may be useful
+  in some upgrade scenarios.
+
+- `raft_protocol` `(int: 2)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/docs/telemetry/metrics) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  stanza][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join stanza][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration stanza. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/tutorials/nomad/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` stanza
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm = "spread"
+
+    preemption_config {
+      batch_scheduler_enabled   = true
+      system_scheduler_enabled  = true
+      service_scheduler_enabled = true
+    }
+  }
+}
+```
+
+[encryption]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /api-docs/operator#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /docs/faq#bootstrapping
+[RFC4648]: https://tools.ietf.org/html/rfc4648#section-5
+[`nomad operator keygen`]: /docs/commands/operator/keygen
diff --git a/content/nomad/v1.0.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.0.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..89b1f1de1d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: server_join Stanza - Agent Configuration
+sidebar_title: server_join
+description: >-
+  The "server_join" stanza specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Stanza
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` stanza specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+"retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.0.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.0.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..2ed3db7e16
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: telemetry Stanza - Agent Configuration
+sidebar_title: telemetry
+description: |-
+  The "telemetry" stanza configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Stanza
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` stanza configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` stanza. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` stanza,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.0.x/content/docs/configuration/tls.mdx b/content/nomad/v1.0.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..78cd272f16
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: tls Stanza - Agent Configuration
+sidebar_title: tls
+description: |-
+  The "tls" stanza configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers, clients, and between.
+---
+
+# `tls` Stanza
+
+<Placement groups={['tls']} />
+
+The `tls` stanza configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` stanza. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` stanzas. Remember that the
+`tls` stanza is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a
+`SIGHUP` signal. Note that this will only reload a subset of the configuration
+file, including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.0.x/content/docs/configuration/vault.mdx b/content/nomad/v1.0.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..785d599219
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Stanza - Agent Configuration
+sidebar_title: vault
+description: |-
+  The "vault" stanza configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Stanza
+
+<Placement groups={['vault']} />
+
+The `vault` stanza configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive child tokens for jobs
+  requesting tokens.
+  Visit the [Vault Integration Guide](/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.0.x/content/docs/devices/external/index.mdx b/content/nomad/v1.0.x/content/docs/devices/external/index.mdx
new file mode 100644
index 0000000000..b2b0837541
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/devices/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Device Plugins.
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+## Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [USB][usb]
+
+## Authoring Device Plugins
+
+Nomad has a plugin system for defining device drivers. External device plugins
+will have the same user experience as built in drivers. For details on
+authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
+[usb]: /docs/devices/external/usb
diff --git a/content/nomad/v1.0.x/content/docs/devices/external/usb.mdx b/content/nomad/v1.0.x/content/docs/devices/external/usb.mdx
new file mode 100644
index 0000000000..a285599bc7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/devices/external/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+sidebar_title: USB <sup>Beta</sup>
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+|------------------|--------|-------------------------------------------------|
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin stanza then needs to be added. A full example of the
+plugin stanza needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.0.x/content/docs/devices/index.mdx b/content/nomad/v1.0.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..bb403ea6d3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/devices/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in Nomad.
+Devices are physical hardware that exists on a node such as a GPU or an FPGA. By
+having extensible device plugins, Nomad has the flexibility to support a broad
+set of devices and allows the community to build additional device plugins as
+needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
+
+For details on authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/internals/plugins
diff --git a/content/nomad/v1.0.x/content/docs/devices/nvidia.mdx b/content/nomad/v1.0.x/content/docs/devices/nvidia.mdx
new file mode 100644
index 0000000000..09a928bc1f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/devices/nvidia.mdx
@@ -0,0 +1,335 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+sidebar_title: Nvidia
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nvidia-gpu`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad. The Nvidia
+plugin is built into Nomad and does not need to be downloaded separately.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nvidia-gpu` the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+
+### Docker Driver Requirements
+
+In order to use the Nvidia driver plugin with the Docker driver, please follow
+the installation instructions for
+[`nvidia-docker`](<https://github.com/NVIDIA/nvidia-docker/wiki/Installation-(version-1.0)>).
+
+## Plugin Configuration
+
+```hcl
+plugin "nvidia-gpu" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nvidia-gpu` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Restrictions
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver] and plans to
+bring support to the built-in [`exec`][exec-driver] and [`java`][java-driver]
+drivers. Support for [`lxc`][lxc-driver] should be possible by installing the
+[Nvidia hook](https://github.com/lxc/lxc/blob/master/hooks/nvidia) but is not
+tested or documented by Nomad.
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m43s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2674/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Allocations
+No allocations placed
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m59s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2673/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+
+Allocations
+No allocations placed
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:9.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+ID                  = d250baed
+Eval ID             = 21bd7584
+Name                = gpu-test.smi[0]
+Node ID             = 4d46e59f
+Job ID              = example
+Job Version         = 0
+Client Status       = complete
+Client Description  = All tasks have completed
+Desired Status      = run
+Desired Description = <none>
+Created             = 7s ago
+Modified            = 2s ago
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[docker-driver]: /docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /docs/drivers/external/lxc 'Nomad lxc Driver'
diff --git a/content/nomad/v1.0.x/content/docs/drivers/docker.mdx b/content/nomad/v1.0.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..9d8eaea763
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1124 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+sidebar_title: Docker
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:3.2"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) stanza, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the client's
+  configuration. We recommend using [`mounts`](#mounts) if you wish to have more
+  control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - *Since 1.0.1* (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (*deprecated*: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-add`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME",
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-drop`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`](#plugin_caps) plugin option key in the client node's configuration.
+  For example:
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD",
+    ]
+  }
+  ```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource stanza and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network stanza and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin stanza][plugin-stanza]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["CHOWN", "NET_RAW"]
+
+    # allow_caps can also be set to "ALL"
+    # allow_caps = ["ALL"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `allow_caps`<a id="plugin_caps"></a> - A list of allowed Linux capabilities.
+  Defaults to
+  `CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP,SETPCAP, NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE` which is the list of
+  capabilities allowed by docker by default, as defined here. Allows the
+  operator to control which capabilities can be obtained by tasks using cap_add
+  and cap_drop options. Supports the value "ALL" as a shortcut for allowlisting
+  all capabilities.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` stanza:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` stanza:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `gc` stanza:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` stanza for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config stanza.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
diff --git a/content/nomad/v1.0.x/content/docs/drivers/exec.mdx b/content/nomad/v1.0.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..8cc258798f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,203 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+sidebar_title: Isolated Fork/Exec
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+ be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+ able to make use of IPC features, like sending unexpected POSIX signals.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+ `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+ disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+ be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+`"private"` to enable IPC namespace isolation for tasks by default,
+ or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+ able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /docs/drivers/exec#default_ipc_mode
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/containerd.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/containerd.mdx
new file mode 100644
index 0000000000..20f19012f4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/containerd.mdx
@@ -0,0 +1,366 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+sidebar_title: containerd
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` stanza in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v0.9.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v0.9.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` stanza.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` stanza.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] stanza documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service stanza instructs Nomad to register a service with Consul.
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /docs/commands/job/init
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[Moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[Docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /docs/job-specification/network
+[`service`]: /docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/firecracker-task-driver.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..0fb5fa2cd2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/firecracker-task-driver.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+sidebar_title: Firecracker driver
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/iis.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/iis.mdx
new file mode 100644
index 0000000000..79d17f7b87
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/iis.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+sidebar_title: Windows IIS
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network stanza port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/index.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/index.mdx
new file mode 100644
index 0000000000..0beaee95dd
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+sidebar_title: Community
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [LXC][lxc]
+- [Rkt][rkt]
+- [Podman][podman]
+- [Singularity][singularity]
+- [Jail task driver][jail-task-driver]
+- [Pot][pot]
+- [Firecracker][firecracker-task-driver]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+- [containerd][nomad-driver-containerd]
+
+[lxc]: /docs/drivers/external/lxc
+[rkt]: /docs/drivers/external/rkt
+[plugin_guide]: /docs/internals/plugins
+[singularity]: /docs/drivers/external/singularity
+[jail-task-driver]: /docs/drivers/external/jail-task-driver
+[podman]: /docs/drivers/external/podman
+[pot]: /docs/drivers/external/pot
+[firecracker-task-driver]: /docs/drivers/external/firecracker-task-driver
+[nspawn-driver]: /docs/drivers/external/nspawn
+[nomad-driver-iis]: /docs/drivers/external/iis
+[nomad-driver-containerd]: /docs/drivers/external/containerd
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/jail-task-driver.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/jail-task-driver.mdx
new file mode 100644
index 0000000000..4c6d524898
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/jail-task-driver.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+sidebar_title: Jailtask driver
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /docs/configuration#plugin_dir
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/lxc.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/lxc.mdx
new file mode 100644
index 0000000000..4fae138242
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/lxc.mdx
@@ -0,0 +1,195 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+sidebar_title: LXC
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` stanza:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: https://learn.hashicorp.com/tutorials/nomad/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/nspawn.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/nspawn.mdx
new file mode 100644
index 0000000000..fdea945e96
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/nspawn.mdx
@@ -0,0 +1,205 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+sidebar_title: systemd-nspawn
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[docker_driver]: /docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /docs/integrations/consul-connect
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/pot.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/pot.mdx
new file mode 100644
index 0000000000..d2cff5da53
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/pot.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+sidebar_title: Pot
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/rkt.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/rkt.mdx
new file mode 100644
index 0000000000..8e947c8dd0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/rkt.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+sidebar_title: 'Rkt <sup>Deprecated</sup> '
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:3.2"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v1.0.x/content/docs/drivers/external/singularity.mdx b/content/nomad/v1.0.x/content/docs/drivers/external/singularity.mdx
new file mode 100644
index 0000000000..f26865850b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/external/singularity.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+sidebar_title: Singularity
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.0.x/content/docs/drivers/index.mdx b/content/nomad/v1.0.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..24a9b6fba4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/index.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Task Drivers
+sidebar_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin stanza][plugin] documentation for examples on how to
+use the `plugin` stanza in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/internals/plugins
+[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.0.x/content/docs/drivers/java.mdx b/content/nomad/v1.0.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..e3f0ac80a8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/java.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+sidebar_title: Java
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+ be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+ able to make use of IPC features, like sending unexpected POSIX signals.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+ `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+ disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+ be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+`"private"` to enable IPC namespace isolation for tasks by default,
+ or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+ able to make use of IPC features, like sending unexpected POSIX signals.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /docs/drivers/java#default_ipc_mode
diff --git a/content/nomad/v1.0.x/content/docs/drivers/podman.mdx b/content/nomad/v1.0.x/content/docs/drivers/podman.mdx
new file mode 100644
index 0000000000..ade411d182
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/podman.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+sidebar_title: Podman
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+See the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be [downloaded][downloaded] onto the client host
+in the configured plugin directory.
+
+- Linux host with [`podman`][podman] installed.
+- [`nomad-driver-podman`][releases] binary in Nomad's [`plugin_dir`][plugin_dir].
+
+You need a varlink enabled Podman binary and a system socket activation unit, see https://podman.io/blogs/2019/01/16/podman-varlink.html.
+
+Since the Nomad agent, nomad-driver-podman plugin binary, and Podman will
+reside on the same host, skip the ssh aspects of the Podman varlink
+documentation above.
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Known Limitations
+
+The Podman task driver is under active development. It currently does not support [stderr logging][stderr-logging] and [devices][devices].
+Podman recently released [Podman v2](https://podman.io/blogs/2020/06/29/podman-v2-announce.html). The task driver currently supports v1
+and will be working on supporting v2 in upcoming releases.
+
+## Task Configuration
+
+Due to Podman's similarity to Docker, the example job created by [`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  network {
+    port  "db"  {
+      to = 6379
+    }
+  }
+
+  group "cache" {
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis:3.2"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+- `image` - The image to run.
+
+```hcl
+config {
+  image = "docker://redis"
+}
+```
+
+- `command` - (Optional) The command to run when starting the container.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  _command_ is specified, the arguments are passed directly to the container.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths.
+
+```hcl
+config {
+  volumes = [
+    "/some/host/data:/container/data"
+  ]
+}
+```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for tmpfs mount
+  points. See `podman run --tmpfs` options for details.
+
+```hcl
+config {
+  tmpfs = [
+    "/var"
+  ]
+}
+```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using count) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - Run an init inside the container that forwards signals and reaps processes.
+
+```hcl
+config {
+  init = true
+}
+```
+
+- `init_path` - Path to the container-init binary.
+
+```hcl
+config {
+  init = true
+  init_path = "/usr/libexec/podman/catatonit"
+}
+```
+
+- `user` - Run the command as a specific user/uid within the container. See
+  [task configuration][task].
+
+- `memory_reservation` - Memory soft limit (unit = b (bytes), k (kilobytes), m
+  (megabytes), or g (gigabytes))
+
+After setting memory reservation, when the system detects memory contention or
+low memory, containers are forced to restrict their consumption to their
+reservation. So you should always set the value below --memory, otherwise the
+hard limit will take precedence. By default, memory reservation will be the
+same as memory limit.
+
+```hcl
+config {
+  memory_reservation = "100m"
+}
+```
+
+- `memory_swap` - A limit value equal to memory plus swap. The swap limit
+  should always be larger than the [memory value][memory-value].
+
+Unit can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you
+don't specify a unit, b is used. Set LIMIT to -1 to enable unlimited swap.
+
+```hcl
+config {
+  memory_swap = "180m"
+}
+```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between 0 and 100.
+
+```hcl
+config {
+  memory_swappiness = 60
+}
+```
+
+- `network_mode` - Set the [network mode][network-mode] for the container. This will be
+  overridden by nomad if a group network is created and passed in by Nomad.
+
+  - `bridge` - (default for rootful) create a network stack on the default bridge
+  - `none` - no networking
+  - `container:id` - reuse another container's network stack
+  - `host` - use the Podman host network stack. Note: the host mode gives the container
+    full access to local system services such as D-bus and is therefore considered insecure.
+  - `slirp4netns` - use `slirp4netns` to create a user network stack. This is the default for
+    rootless containers. Podman currently does not support this option for rootful containers ([issue][slirp-issue])
+
+## Networking
+
+Podman supports forwarding and exposing ports like Docker. See [Docker Driver
+configuration][docker-ports] for details.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+  }
+}
+```
+
+- `gc` stanza:
+
+  - `container` - Defaults to `true`. This option can be used to disable
+    Nomad from removing a container when the task exits.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously managed containers
+  will be reused instead of disposed and recreated.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    recover_stopped = false
+  }
+}
+```
+
+[docker-ports]: /docs/drivers/docker#forwarding-and-exposing-ports
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /docs/job-specification/resources#memory
+[nomad-init]: /docs/commands/job/init
+[plugin_dir]: /docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[task]: /docs/job-specification/task#user
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[stderr-logging]: https://github.com/hashicorp/nomad-driver-podman/issues/4
+[devices]: https://github.com/hashicorp/nomad-driver-podman/issues/41
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
diff --git a/content/nomad/v1.0.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.0.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..aa131f5e1b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,180 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+sidebar_title: QEMU
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. (Note that
+  [prior to qemu 2.10.1](https://github.com/qemu/qemu/commit/ad9579aaa16d5b385922d49edac2c96c79bcfb6),
+  the monitor socket path is limited to 108 characters. Graceful shutdown will
+  be disabled if QEMU is < 2.10.1 and the generated monitor path exceeds this
+  length. You may encounter this issue if you set long
+  [data_dir](/docs/configuration#data_dir)
+  or
+  [alloc_dir](/docs/configuration/client#alloc_dir)
+  paths.) This feature is currently not supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.0.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.0.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..56e5ae9f02
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+sidebar_title: Raw Fork/Exec
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/docs/internals/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin stanza:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v1.0.x/content/docs/ecosystem.mdx b/content/nomad/v1.0.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..d84e320dc5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/ecosystem.mdx
@@ -0,0 +1,200 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+sidebar_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+### Continuous Integration & Delivery
+
+#### GitLab
+
+https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations
+
+#### Codefresh
+
+https://codefresh.io/docs/docs/yaml-examples/examples/nomad/
+
+#### CircleCI
+
+https://circleci.com/docs/2.0/nomad/
+
+#### Drone
+
+https://docs.drone.io/runner/nomad/overview/
+
+#### Jenkins
+
+https://plugins.jenkins.io/nomad/
+
+#### Buildkite
+
+https://buildkite.com/works-with/hashicorp
+
+### Container Runtime
+
+#### Containerd
+
+https://www.nomadproject.io/docs/drivers/external/containerd
+
+#### Windows IIS
+
+https://github.com/Roblox/nomad-driver-iis
+
+#### Jailtask
+
+https://www.nomadproject.io/docs/drivers/external/jail-task-driver
+
+#### Pot
+
+https://github.com/trivago/nomad-pot-driver
+
+#### Singularity
+
+https://www.nomadproject.io/docs/drivers/external/singularity
+
+#### Firecracker
+
+https://www.nomadproject.io/docs/drivers/external/firecracker-task-driver
+
+#### Podman
+
+https://www.nomadproject.io/docs/drivers/podman
+
+#### LXC
+
+https://www.nomadproject.io/docs/drivers/external/lxc
+
+### Application Definition & Image Build
+
+#### Levant
+
+https://github.com/hashicorp/levant
+
+#### Packer
+
+https://www.packer.io/
+
+#### Waypoint
+
+https://learn.hashicorp.com/collections/waypoint/get-started-nomad
+
+### Container Registry
+
+#### JFrog Artifactory
+
+https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/
+
+### Observability and Analysis
+
+#### Prometheus
+
+https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics
+
+https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing?in=nomad/nomad-1-0#start-prometheus
+
+#### Grafana
+
+https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/
+
+#### DataDog
+
+https://docs.datadoghq.com/integrations/nomad/
+
+#### Turbonomics
+
+https://www.youtube.com/watch?v=lwtIaPpdDsc
+
+#### Circonus
+
+https://www.hashicorp.com/integrations/circonus/nomad
+
+#### Flowmill
+
+https://www.flowmill.com/blog/announcing-flowmill-s-integration-with-nomad/
+
+#### Sematext
+
+https://www.hashicorp.com/integrations/sematext/nomad
+
+#### Splunk
+
+https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/
+
+### Secret Management
+
+#### Vault
+
+https://www.nomadproject.io/docs/integrations/vault-integration
+
+### Service Mesh
+
+#### Consul
+
+https://www.nomadproject.io/docs/integrations/consul-integration
+
+### Provisioning
+
+#### Terraform
+
+https://registry.terraform.io/providers/hashicorp/nomad/latest/docs
+
+#### Chef
+
+https://github.com/nathwill/chef-nomad
+
+#### Ansible
+
+https://github.com/ansible-community/ansible-nomad
+
+### Cloud Native Network
+
+#### CNI
+
+https://www.nomadproject.io/docs/integrations/consul-connect#cni-plugins
+
+### Service Proxy
+
+#### Envoy
+
+https://www.nomadproject.io/docs/integrations/consul-connect
+
+#### NGINX
+
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx
+
+#### Traefik
+
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik
+
+### Storage
+
+#### CSI
+
+https://www.nomadproject.io/docs/internals/plugins/csi
+
+#### Portworx
+
+https://www.hashicorp.com/integrations/portworx/nomad
+
+### GPUs
+
+#### NVIDIA
+
+https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/
+
+https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad
+
+### Autoscaling
+
+#### AWS ASGs
+
+Dynamically autoscale your Nomad clusters
+
+https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler
+
+#### Spot
+
+https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/
diff --git a/content/nomad/v1.0.x/content/docs/enterprise.mdx b/content/nomad/v1.0.x/content/docs/enterprise.mdx
new file mode 100644
index 0000000000..0986f62e73
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/enterprise.mdx
@@ -0,0 +1,195 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+sidebar_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+## Nomad Enterprise Licensing
+
+Nomad Enterprise requires a license to run. When a Enterprise server first
+starts it will be set with a temporary license that includes all
+features. This will be valid for 6 hours and allows users to test enterprise
+features and provide enough time for operators to apply their enterprise
+license.
+
+If a server is never given a valid license and the temporary license expires,
+the server will shutdown. If a valid (non-temporary) license expires, the
+cluster will continue to function, but write operations to enterprise features
+will be disabled.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+See the [License commands](/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](https://learn.hashicorp.com/tutorials/nomad/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/docs/commands/operator/snapshot-agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](https://learn.hashicorp.com/tutorials/nomad/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](https://learn.hashicorp.com/tutorials/nomad/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestibile and familiar
+to operators.
+
+See the [Audit Logging Documentation](/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](https://learn.hashicorp.com/tutorials/nomad/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies
+Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel) for a thorough
+overview.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /docs/job-specification/multiregion
+[autoscaling capabilities]: /docs/autoscaling
+[scaling policies]: /docs/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
diff --git a/content/nomad/v1.0.x/content/docs/faq.mdx b/content/nomad/v1.0.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..d81bc680f6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/faq.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+sidebar_title: FAQ
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/docs/internals/consensus) and
+a [gossip protocol](/docs/internals/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+[consul_dc]: https://www.consul.io/docs/agent/options#_datacenter
+[consul_fed]: https://learn.hashicorp.com/tutorials/consul/federarion-gossip-wan
+[nomad_region]: /docs/configuration#datacenter
+[`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.0.x/content/docs/index.mdx b/content/nomad/v1.0.x/content/docs/index.mdx
new file mode 100644
index 0000000000..0fad01e91f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. This documentation is more of a reference
+  guide for all available features and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [HashiCorp Learn "Getting Started" collection][gs]
+instead.
+
+[gs]: https://learn.hashicorp.com/collections/nomad/get-started
diff --git a/content/nomad/v1.0.x/content/docs/install/index.mdx b/content/nomad/v1.0.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..ee125fd4e3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/install/index.mdx
@@ -0,0 +1,272 @@
+---
+layout: docs
+page_title: Installing Nomad
+sidebar_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation">
+
+You can download a [precompiled binary](/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+You can check the locations available on your path by running this command.
+
+```shell-session
+$ echo $PATH
+
+/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
+```
+
+The output is a list of locations separated by colons. You can make Nomad
+available by moving the binary to one of the listed locations, or by adding
+Nomad's location to your `PATH`.
+
+-> **Tip (Linux-based or Mac):** Permanently add a new location to your path by
+editing your shell's settings file (usually called something like `~/.bashrc`,
+where the part of the file name after the `.` and before `rc` is the name of
+your shell). In that file you will see a line that starts with `export PATH=`,
+followed by a colon-separated list of locations. Add the location of the Consul
+binary to that list and save the file. Then reload your shell's configuration
+with the command `source ~/.bashrc`, replacing `bash` with the name of your
+shell.
+
+-> **Tip (Windows):** Add a location to your path via the GUI by navigating to
+`Environment Variables` in your system settings, and looking for the variable
+called `PATH`. You will see a semicolon-separated list of locations. Add the
+Nomad binary's location to that list and then launch a new console window.
+
+</Tab>
+<Tab heading="Linux Packages">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](https://learn.hashicorp.com/consul) and
+[Vault](https://learn.hashicorp.com/vault) with the same command.
+
+</Tab>
+<Tab heading="Homebrew (macOS)">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey (Windows)">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+</Tabs>
+
+---
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+[consul-download]: https://www.consul.io/downloads
+[destroy]: https://www.vagrantup.com/docs/cli/destroy
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+[gpg-key]: https://apt.releases.hashicorp.com/gpg 'HashiCorp GPG key'
diff --git a/content/nomad/v1.0.x/content/docs/install/production/index.mdx b/content/nomad/v1.0.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..6d6fba1137
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/install/production/index.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+sidebar_title: Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/docs/install/production/nomad-agent)
+and [Nomad Agent documentation](/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.0.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.0.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..f3a43feb36
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: Requirements
+sidebar_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges. The Nomad client's data directory should be owned by
+`root` with filesystem permissions set to `0700`.
diff --git a/content/nomad/v1.0.x/content/docs/install/quickstart.mdx b/content/nomad/v1.0.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..87cd59e070
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+sidebar_title: Quickstart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via Learn guides containing embedded Katacoda interactive learning environments.
+
+- [Interactive Labs](https://learn.hashicorp.com/collections/nomad/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](https://www.vagrantup.com/docs/installation/). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[installing-binary]: /docs/install#precompiled-binaries
+[vagrant-environment]: https://learn.hashicorp.com/tutorials/nomad/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.0.x/content/docs/install/windows-service.mdx b/content/nomad/v1.0.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..dba9e7bd9e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+sidebar_title: Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /downloads
+[logging]: /docs/configuration#log_file
diff --git a/content/nomad/v1.0.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.0.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..c56c22e977
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,337 @@
+---
+layout: docs
+page_title: Consul Connect
+sidebar_title: Consul Connect
+description: >-
+  Learn how to use Nomad with Consul Connect to enable secure service to service
+  communication
+---
+
+# Consul Connect
+
+~> **Note:** This guide requires Nomad 0.10.0 or later and Consul 1.6.0 or
+later.
+
+~> **Note:** Nomad's Connect integration requires Linux network namespaces.
+Nomad Connect will not run on Windows or macOS.
+
+[Consul Connect](https://www.consul.io/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of Connect at all.
+
+# Nomad with Consul Connect Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. In order to support Consul Connect, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into Connect integration. When Connect is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul Connect integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in Connect continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul Connect integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+# Nomad Consul Connect Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+Connect integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+**Note**: Nomad's Connect integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use Connect on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Connect.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul Connect sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v0.9.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v0.9.0.tgz
+$ sudo mkdir -p /opt/cni/bin
+$ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Connect-enabled Services
+
+Once Nomad and Consul are running, submit the following Connect-enabled services
+to Nomad by copying the HCL into a file named `connect.nomad` and running:
+`nomad run connect.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul Connect, it does not define
+any ports in its network. The service stanza enables Connect:
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service stanza is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace.
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul Connect:
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` stanza defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul Connect using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+[count-dashboard]: /img/count-dashboard.png
+[gh6120]: https://github.com/hashicorp/nomad/issues/6120
+[gh6701]: https://github.com/hashicorp/nomad/issues/6701
diff --git a/content/nomad/v1.0.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.0.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..f99b561161
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Consul Integration
+sidebar_title: Consul
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](https://learn.hashicorp.com/tutorials/nomad/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` stanza](/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template stanza and how it leverages Consul Template,
+please see the [`template` job specification documentation](/docs/job-specification/template).
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/integrations/index.mdx b/content/nomad/v1.0.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..5778b3e468
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/integrations/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+sidebar_title: Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.0.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.0.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..1575181eb6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,472 @@
+---
+layout: docs
+page_title: Vault Integration
+sidebar_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](https://www.vaultproject.io/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The token can then be set in the server configuration's
+[`vault` stanza][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` stanza of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To Submit this job a token that has the `access-kv` policy in the Namespace `engineering`
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: https://www.vaultproject.io/docs/auth/token 'Vault Authentication Backend'
+[config]: /docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: https://www.vaultproject.io/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: https://www.vaultproject.io/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.0.x/content/docs/internals/architecture.mdx b/content/nomad/v1.0.x/content/docs/internals/architecture.mdx
new file mode 100644
index 0000000000..21185e1cbf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/architecture.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: Architecture
+sidebar_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+- **Job** - A Job is a specification provided by users that declares a workload for
+  Nomad. A Job is a form of _desired state_; the user is expressing that the job should
+  be running, but not where it should be run. The responsibility of Nomad is to make sure
+  the _actual state_ matches the user desired state. A Job is composed of one or more
+  task groups.
+
+- **Task Group** - A Task Group is a set of tasks that must be run together. For example, a
+  web server may require that a log shipping co-process is always running as well. A task
+  group is the unit of scheduling, meaning the entire group must run on the same client node and
+  cannot be split.
+
+- **Driver** – A Driver represents the basic means of executing your **Tasks**.
+  Example Drivers include Docker, QEMU, Java, and static binaries.
+
+- **Task** - A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+  which allow Nomad to be flexible in the types of tasks it supports. Tasks
+  specify their driver, configuration for the driver, constraints, and resources required.
+
+- **Client** - A Client of Nomad is a machine that tasks can be run on. All clients run the
+  Nomad agent. The agent is responsible for registering with the servers, watching for any
+  work to be assigned and executing tasks. The Nomad agent is a long lived process which
+  interfaces with the servers.
+
+- **Allocation** - An Allocation is a mapping between a task group in a job and a client
+  node. A single job may have hundreds or thousands of task groups, meaning an equivalent
+  number of allocations must exist to map the work to client machines. Allocations are created
+  by the Nomad servers as part of scheduling decisions made during an evaluation.
+
+- **Evaluation** - Evaluations are the mechanism by which Nomad makes scheduling decisions.
+  When either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad creates
+  a new evaluation to determine if any actions must be taken. An evaluation may result
+  in changes to allocations if necessary.
+
+- **Server** - Nomad servers are the brains of the cluster. There is a cluster of servers
+  per region and they manage all jobs and clients, run evaluations, and create task allocations.
+  The servers replicate data between each other and perform leader election to ensure high
+  availability. Servers federate across regions to make Nomad globally aware.
+
+- **Regions and Datacenters** - Nomad models infrastructure as regions and
+  datacenters. Regions may contain multiple datacenters. Servers are assigned to
+  a specific region, managing state and making scheduling decisions within that
+  region. Multiple regions can be federated together. For example, you may
+  have a `US` region with the `us-east-1` and `us-west-1` datacenters,
+  connected to the `EU` region with the `eu-fr-1` and `eu-uk-1` datacenters.
+  Requests that are made between regions are forwarded to the appropriate servers.
+  Data is _not_ replicated between regions.
+
+- **Bin Packing** - Bin Packing is the process of filling bins with items in a way that
+  maximizes the utilization of bins. This extends to Nomad, where the clients are "bins"
+  and the items are task groups. Nomad optimizes resources by efficiently bin packing
+  tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/docs/internals/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/docs/internals/consensus),
+[gossip protocol](/docs/internals/gossip), and [scheduler design](/docs/internals/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v1.0.x/content/docs/internals/consensus.mdx b/content/nomad/v1.0.x/content/docs/internals/consensus.mdx
new file mode 100644
index 0000000000..280729ab05
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/consensus.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Consensus Protocol
+sidebar_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.0.x/content/docs/internals/filesystem.mdx b/content/nomad/v1.0.x/content/docs/internals/filesystem.mdx
new file mode 100644
index 0000000000..c4d3aeea63
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/filesystem.mdx
@@ -0,0 +1,461 @@
+---
+layout: docs
+page_title: Filesystem
+sidebar_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./allocs/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. Within the
+  `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] stanza for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    the the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /docs/job-specification/artifact
+[csi volumes]: /docs/internals/plugins/csi
+[dispatch payloads]: /docs/job-specification/dispatch_payload
+[templates]: /docs/job-specification/template
+[`data_dir`]: /docs/configuration#data_dir
+[`ephemeral_disk`]: /docs/job-specification/ephemeral_disk
+[artifact]: /docs/job-specification/artifact
+[chroot contents]: /docs/drivers/exec#chroot
+[filesystem isolation capability]: /docs/internals/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /docs/job-specification/ephemeral_disk#migrate
+[template]: /docs/job-specification/template
+[volume mounts]: /docs/job-specification/volume_mount
diff --git a/content/nomad/v1.0.x/content/docs/internals/gossip.mdx b/content/nomad/v1.0.x/content/docs/internals/gossip.mdx
new file mode 100644
index 0000000000..400e0c6629
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/gossip.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Gossip Protocol
+sidebar_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/internals/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/docs/internals/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.0.x/content/docs/internals/index.mdx b/content/nomad/v1.0.x/content/docs/internals/index.mdx
new file mode 100644
index 0000000000..d9c0711f9c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Internals
+sidebar_title: Internals
+description: >-
+  This section covers the internals of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Internals
+
+This section covers the internals of Nomad and explains the technical
+details of how Nomad functions, its architecture, and sub-systems.
+
+-> **Note:** Knowledge of Nomad internals is not
+required to use Nomad. If you aren't interested in the internals
+of Nomad, you may safely skip this section. If you are operating Nomad,
+we recommend understanding the internals.
diff --git a/content/nomad/v1.0.x/content/docs/internals/plugins/base.mdx b/content/nomad/v1.0.x/content/docs/internals/plugins/base.mdx
new file mode 100644
index 0000000000..8a71735125
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/plugins/base.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Base Plugin
+sidebar_title: Base
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /docs/configuration/plugin
diff --git a/content/nomad/v1.0.x/content/docs/internals/plugins/csi.mdx b/content/nomad/v1.0.x/content/docs/internals/plugins/csi.mdx
new file mode 100644
index 0000000000..f74c16e10c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/plugins/csi.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: Storage Plugins
+sidebar_title: Storage
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the
+industry-standard Container Storage Interface specification unifies
+these APIs in a way that's agnostic to both the storage vendor and the
+container orchestrator. Each storage provider can build its own CSI
+plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
+(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
+Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given
+Nomad client node. A list of available CSI plugins can be found in the
+[Kubernetes CSI documentation][csi-drivers-list]. Any of these plugins
+should work with Nomad out of the box.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+You should always run node plugins as Nomad `system` jobs and use the
+`-ignore-system` flag on the `nomad node drain` command to ensure that the
+node plugins are still running while the node is being drained. Use
+constraints for the node plugin jobs based on the availability of volumes. For
+example, AWS EBS volumes are specific to particular availability zones with a
+region. Controller plugins can be run as `service` jobs.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to the Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes terminal. The
+client will send an "unpublish" RPC to the server, which will send "detach"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from the
+allocation and unmounts the volume from the plugin (if it's not in use by
+another task). The server will then send "unpublish" RPCs to the controller
+plugin (if any), and decrement the claim count for the volume. At this point
+the volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.0.x/content/docs/internals/plugins/devices.mdx b/content/nomad/v1.0.x/content/docs/internals/plugins/devices.mdx
new file mode 100644
index 0000000000..01829331bb
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/plugins/devices.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: Device Plugins
+sidebar_title: Devices
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad/tree/master/devices/gpu/nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/docs/internals/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /docs/internals/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.0.x/content/docs/internals/plugins/index.mdx b/content/nomad/v1.0.x/content/docs/internals/plugins/index.mdx
new file mode 100644
index 0000000000..d9bb9ae245
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/plugins/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Plugins
+sidebar_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/docs/internals/plugins/task-drivers)
+- [Devices](/docs/internals/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.0.x/content/docs/internals/plugins/task-drivers.mdx b/content/nomad/v1.0.x/content/docs/internals/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..b5fe630a1c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/plugins/task-drivers.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+sidebar_title: Task Drivers
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+Capabilities {
+    // Does the driver support sending OS signals to the task? This capability
+    // is used by 'nomad alloc signal'.
+    SendSignals: true,
+
+    // Does the driver support executing a command within the task execution
+    // environment? This capability is used by 'nomad alloc exec'.
+    Exec:        true,
+
+    // What filesystem isolation is supported by the driver. Options include
+    // FSIsolationImage, FSIsolationChroot, and FSIsolationNone. See below for
+    // more details.
+    FSIsolation: FSIsolationImage,
+
+    // NetIsolationModes lists the set of isolation modes supported by the
+    // driver.  Options include NetIsolationModeHost, NetIsolationModeGroup,
+    // NetIsolationModeTask, and NetIsolationModeNone. See below for more
+    // details.
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are
+    // implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver
+    // supports. This is used to check whether mounting host volumes or CSI
+    // volumes is allowed. Options include MountConfigSupportAll (default), or
+    // MountConfigSupportNone.
+    MountConfigs MountConfigSupport
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /docs/internals/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
diff --git a/content/nomad/v1.0.x/content/docs/internals/scheduling/index.mdx b/content/nomad/v1.0.x/content/docs/internals/scheduling/index.mdx
new file mode 100644
index 0000000000..76e2deaf0d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/docs/internals/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/docs/internals/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.0.x/content/docs/internals/scheduling/preemption.mdx b/content/nomad/v1.0.x/content/docs/internals/scheduling/preemption.mdx
new file mode 100644
index 0000000000..150174d88a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/scheduling/preemption.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Preemption
+sidebar_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.0.x/content/docs/internals/scheduling/scheduling.mdx b/content/nomad/v1.0.x/content/docs/internals/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..0283aade26
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/scheduling/scheduling.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Scheduling
+sidebar_title: Internals
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, a `system` scheduler
+that is used to run jobs on every node, and a `core` scheduler which is used
+for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.0.x/content/docs/internals/security.mdx b/content/nomad/v1.0.x/content/docs/internals/security.mdx
new file mode 100644
index 0000000000..c571783c0e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/internals/security.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: Security Model
+sidebar_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](https://www.consul.io/docs/internals/security), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](https://learn.hashicorp.com/collections/nomad/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+
+  - Access to read and write to a namespace can be
+    controlled to allow for granular access to job information managed within a
+    multi-tenant cluster.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](https://www.vaultproject.io/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](https://learn.hashicorp.com/collections/nomad/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+- **[ACLs enabled](https://learn.hashicorp.com/collections/nomad/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code/)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+  (**Enterprise Only**) - This feature allows for a cluster to be shared by
+  multiple teams within a company. Using this logical separation is important
+  for multi-tenant clusters to prevent users without access to that namespace
+  from conflicting with each other. This requires ACLs to be enabled in order
+  to be enforced.
+
+- **[Resource Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](https://learn.hashicorp.com/tutorials/nomad/web-ui-access) and [API](/api-docs) access to agents. |
+| **4647** / TCP       | Servers | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/docs/internals/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.0.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..078513d6b2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: affinity Stanza - Job Specification
+sidebar_title: affinity
+description: |-
+  The "affinity" stanza allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Stanza
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` stanza allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 5
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task stanzas as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` stanzas. Remember that the
+`affinity` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` stanza matches the node.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.0.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..5896cf1a09
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: artifact Stanza - Job Specification
+sidebar_title: artifact
+description: |-
+  The "artifact" stanza instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Stanza
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` stanza instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` stanzas. Remember that the
+`artifact` stanza is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/example/nomad-examples"
+  destination = "local/repo"
+}
+```
+
+To download from private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](https://www.nomadproject.io/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  source      = "git@github.com:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    sshkey = "${base64encode(file(pathexpand("~/.ssh/id_rsa")))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/example/nomad-examples"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/internals/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.0.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..52b85d002d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: check_restart Stanza - Job Specification
+sidebar_title: check_restart
+description: |-
+  The "check_restart" stanza instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` stanza instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` stanza, it is
+restarted according to the task group's [`restart` policy][restart_stanza]. The
+`check_restart` settings apply to [`check`s][check_stanza], but may also be
+placed on [`service`s][service_stanza] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the stanzas are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_stanza] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` stanza][restart_stanza] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` stanza][restart_stanza] for
+details.
+
+[check_stanza]: /docs/job-specification/service#check-parameters 'check stanza'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[service_stanza]: /docs/job-specification/service 'service stanza'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.0.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..8367c841ec
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: connect Stanza - Job Specification
+sidebar_title: connect
+description: The "connect" stanza allows specifying options for Consul Connect integration
+---
+
+# `connect` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` stanza allows configuring various options for
+[Consul Connect](/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](https://www.consul.io/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service stanza for a
+[Consul Connect Native](https://www.consul.io/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect stanza with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service stanza for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[native]: https://www.consul.io/docs/connect/native
+[service_task]: /docs/job-specification/service#task-1 'Nomad service task'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.0.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..c3e8914230
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: constraint Stanza - Job Specification
+sidebar_title: constraint
+description: |-
+  The "constraint" stanza allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Stanza
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` stanzas. Remember that the
+`constraint` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.0.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..359c388d52
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: csi_plugin Stanza - Job Specification
+sidebar_title: csi_plugin <sup>Beta</sup>
+description: >-
+  The "csi_plugin" stanza allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume']} />
+
+The "csi_plugin" stanza allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <required>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+~> **Note:** During node drains, jobs that claim volumes must be moved before
+the `node` or `monolith` plugin for those volumes. You should run `node` or
+`monolith` plugins as [`system`][system] jobs and use the `-ignore-system`
+flag on `nomad node drain` to ensure that the plugins are running while the
+node is being drained.
+
+~> **Note:** Only one plugin instance of a given plugin ID and type
+(controller or node) should be deployed on any given client node. Use a
+constraint as shown below.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:latest"
+
+        args = [
+          "node",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id        = "aws-efs0"
+        type      = "node"
+        mount_dir = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /docs/job-specification/volume
+[system]: /docs/schedulers#system
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/device.mdx b/content/nomad/v1.0.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..9af64218e0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,304 @@
+---
+layout: docs
+page_title: device Stanza - Job Specification
+sidebar_title: device
+description: |-
+  The "device" stanza is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` stanza is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` stanza is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` stanza
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` stanza can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` stanzas. Remember that the
+`device` stanza is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.0.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..15c20b5d5f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: dispatch_payload Stanza - Job Specification
+sidebar_title: dispatch_payload
+description: |-
+  The "dispatch_payload" stanza allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Stanza
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` stanza is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` stanza. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` stanzas. Remember that the
+`dispatch_payload` stanza is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/env.mdx b/content/nomad/v1.0.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..a2fad4bca8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: env Stanza - Job Specification
+sidebar_title: env
+description: |-
+  The "env" stanza configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Stanza
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` stanza configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` stanzas. Remember that the
+`env` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` stanza][template-env].
+
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /docs/job-specification/template#environment-variables 'Nomad template Stanza'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.0.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..0fe40a94c9
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: ephemeral_disk Stanza - Job Specification
+sidebar_title: ephemeral_disk
+description: |-
+  The "ephemeral_disk" stanza describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Stanza
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` stanza describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be
+  removed if an error is encountered.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` stanzas. Remember that the
+`ephemeral_disk` stanza is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.0.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..577be44e09
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: expose Stanza - Job Specification
+sidebar_title: expose
+description: |-
+  The "expose" stanza allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` stanza allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` stanza.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` stanza. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+stanza can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /docs/job-specification/network#to
+[consul-expose-path-config]: https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /docs/job-specification/expose#path-1
+[expose]: /docs/job-specification/service#expose
+[path]: /docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /docs/configuration/client#network_interface
+[learn-consul-connect]: https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh
+[check]: /docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.0.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..876cac38b4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: gateway Stanza - Job Specification
+sidebar_title: gateway
+description: |-
+  The "gateway" stanza allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` stanza allows configuration of [Consul Connect Gateways](https://www.consul.io/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](https://www.consul.io/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` stanza.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](https://www.consul.io/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](https://www.consul.io/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx?in=nomad/load-balancing)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress` or `terminating` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. Either
+  `tcp` or `http`.
+
+  ~> **Note:** If using `http`, preconfiguring a [service-default] in Consul to
+  set the [Protocol](https://www.consul.io/docs/agent/config-entries/service-defaults#protocol)
+  of the service to `http` is recommended.
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+  ~> **Note:** If a well-known port is not used, i.e. a port other than 80 (http) or 443 (https),
+  then the port must be appended to the host to correctly match traffic. This is
+  defined in the [HTTP/1.1 RFC](https://tools.ietf.org/html/rfc2616#section-14.23).
+  If TLS is enabled, then the host **without** the port must be added to the `hosts`
+  field as well. TLS verification only matches against the hostname of the incoming
+  connection, and does not take into account the port.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] stanza.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpnomad/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpnomad/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+[address]: /docs/job-specification/gateway#address-parameters
+[advanced configuration]: https://www.consul.io/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: https://www.consul.io/docs/agent/config-entries/service-resolver#connecttimeout
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /docs/job-specification/gateway#ingress-parameters
+[proxy]: /docs/job-specification/gateway#proxy-parameters
+[linked-service]: /docs/job-specification/gateway#service-parameters-1
+[listener]: /docs/job-specification/gateway#listener-parameters
+[service]: /docs/job-specification/gateway#service-parameters
+[service-default]: https://www.consul.io/docs/agent/config-entries/service-defaults
+[sidecar_task]: /docs/job-specification/sidecar_task
+[terminating]: /docs/job-specification/gateway#terminating-parameters
+[tls]: /docs/job-specification/gateway#tls-parameters
+
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/group.mdx b/content/nomad/v1.0.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..faaabe9bea
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: group Stanza - Job Specification
+sidebar_title: group
+description: |-
+  The "group" stanza defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `group` stanza defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate stanzas.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart stanza documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul](/docs/configuration/consul) for service discovery. 
+  Nomad automatically registers each service when an allocation
+  is started and de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul deregistration
+  and sending each task a shutdown signal. Ideally, services would fail
+  healthchecks once they receive a shutdown signal. Alternatively
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group services. In addition, tasks may have their
+  own [`shutdown_delay`](/docs/job-specification/task#shutdown_delay)
+  which waits between deregistering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration
+  after which a Nomad client that cannot communicate with the servers
+  will stop allocations based on this task group. By default, a client
+  will not stop an allocation until explicitly told to by a server. A
+  client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be
+  marked "lost" and Nomad will schedule replacement
+  allocations. However, these replaced allocations will continue to
+  run on the non-responsive client; an operator may desire that these
+  replaced allocations are also stopped in this case — for example,
+  allocations requiring exclusive access to an external resource. When
+  specified, the Nomad client will stop them after this duration. The
+  Nomad client process must be running for this to occur.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` stanzas. Remember that the
+`group` stanza is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] stanza
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other stanzas. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /docs/configuration/server#heartbeat_grace
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..8d4f177801
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,415 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+sidebar_title: Expressions
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or `key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+service {
+  port = "db" # can use expressions here
+
+  check {
+    # but the "check" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `check` using a
+special `dynamic` block type, which is supported anywhere, example:
+
+```hcl
+locals {
+  check_paths = ["/health", "/"]
+}
+
+job "example" {
+  # ...
+  service {
+    port = "lb" # can use expressions here
+
+    dynamic "check" {
+      for_each = local.check_paths
+
+      content {
+        type     = "http"
+        port     = "lb"
+        path     = check.value
+      }
+    }
+ }
+}
+```
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"check"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"check"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`check` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..f690cc7807
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+sidebar_title: chunklist
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..ee8f3bbd70
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+sidebar_title: coalesce
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..e156414ee6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+sidebar_title: coalescelist
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..16cb751b7a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+sidebar_title: compact
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..762ab3e54c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+sidebar_title: concat
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..c073941c5a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+sidebar_title: contains
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..e949739566
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+sidebar_title: distinct
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..db7188c1ba
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+sidebar_title: element
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..84fa3a11d6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+sidebar_title: flatten
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..ade68192ba
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+sidebar_title: index
+description: The index function finds the element index for a given value in a list.
+---
+
+# `index` Function
+
+`index` finds the element index for a given value in a list.
+
+```hcl
+index(list, value)
+```
+
+The returned index is zero-based. This function produces an error if the given
+value is not present in the list.
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], "b")
+1
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..30086156ab
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+sidebar_title: keys
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..2fcf0cec5b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+sidebar_title: length
+description: The length function determines the length of a collection or string.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or string.
+
+If given a list or map, the result is the number of elements in that collection.
+If given a string, the result is the number of characters in the string.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..c7b2723897
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+sidebar_title: lookup
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..4efc6db347
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+sidebar_title: merge
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..b35583ccdc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+sidebar_title: range
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..4459b2e967
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+sidebar_title: reverse
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..479fbf0898
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+sidebar_title: setintersection
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..222c251fba
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,230 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+sidebar_title: setproduct
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..f6c1bb9b1a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+sidebar_title: setunion
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..e13b2f563c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+sidebar_title: slice
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..a5ec274bf6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+sidebar_title: sort
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..ad40e66416
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+sidebar_title: values
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..952cfddb02
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+sidebar_title: zipmap
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..8da0013504
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+sidebar_title: can
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..48b298a75d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+sidebar_title: convert
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..a454a559c6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+sidebar_title: try
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..7d0d2f88d7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+sidebar_title: bcrypt
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..a86eefb90a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+sidebar_title: md5
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..c9aef65529
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+sidebar_title: rsadecrypt
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..0889c2253a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+sidebar_title: sha1
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..6c60fec88c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+sidebar_title: sha256
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..e896c11ea1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+sidebar_title: sha512
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..ac96a8f698
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+sidebar_title: formatdate
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
+- [`timestamp`](/docs/job-specification/hcl2/functions/datetime/timestamp) returns the current date and time in a format
+  suitable for input to `formatdate`.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..0044771b89
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+sidebar_title: timeadd
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..476d0a1d76
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+sidebar_title: base64decode
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..3cb04099ee
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+sidebar_title: base64encode
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..3e39049f10
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+sidebar_title: csvdecode
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..f13d9c7625
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+sidebar_title: jsondecode
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e3265123c4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+sidebar_title: jsonencode
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..c4650ee6c7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+sidebar_title: urlencode
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..39a284b23d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+sidebar_title: yamldecode
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..adbf4318d7
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+sidebar_title: yamlencode
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b433705cbf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+sidebar_title: abspath
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..5fbc104297
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+sidebar_title: basename
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..37bcee8403
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+sidebar_title: dirname
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..dde4bddc6c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+sidebar_title: file
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+## Related Functions
+
+- [`fileexists`](/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..397e35f79e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+sidebar_title: fileexists
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..033f79cbeb
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+sidebar_title: fileset
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..0db1998abf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+sidebar_title: pathexpand
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..1cff9ed050
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+sidebar_title: Functions
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..523f8572bd
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+sidebar_title: cidrhost
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..fbad904b4b
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+sidebar_title: cidrnetmask
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..78832f9a34
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+sidebar_title: cidrsubnet
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..18ad2ef0a6
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+sidebar_title: cidrsubnets
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..6f7ac269f5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+sidebar_title: abs
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..9f71c923a5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+sidebar_title: ceil
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..5f7e3d495d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+sidebar_title: floor
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..5858366a31
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+sidebar_title: log
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..7d74213fad
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+sidebar_title: max
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..5ab346101a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+sidebar_title: min
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6fb0e68281
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+sidebar_title: parseint
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..b771e02d61
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+sidebar_title: pow
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..0ddb370802
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+sidebar_title: signum
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..2fcb35caeb
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+sidebar_title: chomp
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..2be37b4aaa
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+sidebar_title: format
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..595cceace4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+sidebar_title: formatlist
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..786ad73bd1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+sidebar_title: indent
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..25536402a5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+sidebar_title: join
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..d77a30e89a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+sidebar_title: lower
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..c80a515dad
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+sidebar_title: regex_replace
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W)
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..d2a876c04c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+sidebar_title: replace
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..1731511343
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+sidebar_title: split
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..3b40a07980
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+sidebar_title: strrev
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..96bc115446
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+sidebar_title: substr
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..00e165a7d0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+sidebar_title: title
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..4b2f3dfa9c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+sidebar_title: trim
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..940944399e
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+sidebar_title: trimprefix
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..2fbdcba169
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+sidebar_title: trimspace
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..70d4428328
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+sidebar_title: trimsuffix
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..746d0a18ab
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+sidebar_title: upper
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..1fcad248fc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+sidebar_title: uuidv4
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..6e416eb425
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+sidebar_title: uuidv5
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..184b1509c0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: Configuration Language
+sidebar_title: HCL2
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+<!---
+TODO: Re-Add after guide
+This page describes the features of HCL2 exhaustively, if you would like to give
+a quick try to HCL2, you can also read the quicker [HCL2 getting started
+guide](/guides/hcl).
+--->
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /api-docs/jobs
+
+## Syntax
+
+The main purpose of the HCL language in Nomad is defining jobs. All other
+language features exist only to make the definition of builds more flexible and
+convenient.
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/docs/job-specification/hcl2/syntax)
+- [Expressions](/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/docs/job-specification/meta), and
+[`env`](/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpf_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..950e34c1fa
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+sidebar_title: Locals
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "${local.name_prefix}_loadbalancer" {
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..cf9f24d782
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+sidebar_title: Syntax
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..7fc0ff19f3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,301 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+sidebar_title: Variables
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are often referred to as just
+"variables" or "Nomad variables" when it is clear from context what sort of
+variable is being discussed. Other kinds of variables in Nomad include
+_environment variables_ (set by the shell where Nomad runs) and _expression
+variables_ (used to indirectly represent a value in an
+[expression](/docs/job-specification/hcl2/expressions)).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](https://www.terraform.io/docs/configuration/types.html).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/index.mdx b/content/nomad/v1.0.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..0a7daf5b26
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Job Specification
+sidebar_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+stanza. Alternatively, you can keep reading to see a few examples.
+
+For machine-friendliness, Nomad can also read JSON-equivalent configurations. In
+general, we recommend using the HCL syntax.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` stanza can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+stanza specified at the group level must include a [connect][] stanza, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /docs/job-specification/connect 'Connect Stanza Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/job.mdx b/content/nomad/v1.0.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..167e331590
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: job Stanza - Job Specification
+sidebar_title: job
+description: |-
+  The "job" stanza is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Stanza
+
+<Placement groups={['job']} />
+
+The `job` stanza is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate stanzas.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system` and `batch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, rolling updates are disabled.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] stanza. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` stanzas. Remember that the
+`job` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: https://learn.hashicorp.com/tutorials/nomad/federation
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /docs/schedulers 'Nomad Scheduler Types'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.0.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..8a0dd4dcc3
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: lifecycle Stanza - Job Specification
+sidebar_title: lifecycle
+description: |-
+  The "lifecycle" stanza configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Stanza
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` stanza is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` stanza. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+* prestart tasks are started immediately
+* poststart tasks are started after the main tasks are running
+* poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: https://learn.hashicorp.com/collections/nomad/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/docs/job-specification/template) or
+[`artifact`](/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.0.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..17d39c7356
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: logs Stanza - Job Specification
+sidebar_title: logs
+description: |-
+  The "logs" stanza configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" stanza
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Stanza
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` stanza configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` stanza allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` stanzas. Remember that the
+`logs` stanza is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /docs/commands/alloc/logs 'Nomad logs command'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.0.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..73a24a42a1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: meta Stanza - Job Specification
+sidebar_title: meta
+description: The "meta" stanza allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Stanza
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` stanza allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` stanza at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+## `meta` Parameters
+
+The "parameters" for the `meta` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings.
+
+## `meta` Examples
+
+The following examples only show the `meta` stanzas. Remember that the
+`meta` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.0.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..52311a70fe
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: migrate Stanza - Job Specification
+sidebar_title: migrate
+description: |-
+  The "migrate" stanza specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Stanza
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` stanza specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+stanzas.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+stanza for allocations on that node. The `migrate` stanza is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /docs/job-specification/service#check-parameters
+[count]: /docs/job-specification/group#count
+[drain]: /docs/commands/node/drain
+[deadline]: /docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.0.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..535b251e53
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,267 @@
+---
+layout: docs
+page_title: multiregion Stanza - Job Specification
+sidebar_title: multiregion
+description: |-
+  The "multiregion" stanza specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Stanza
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` stanza specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region
+— the one specified by the `region` field or the `-region` command line
+flag to `nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` stanza. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` stanza.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+stanza has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` stanza] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` stanza (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the the
+[`update` stanza] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta stanza allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta stanza at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` stanza and the other
+stanzas it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` stanza with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
+[`update` stanza]: /docs/job-specification/update
+[update-auto-revert]: /docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: https://learn.hashicorp.com/collections/nomad/job-updates
+[`nomad deployment unblock`]: /docs/commands/deployment/unblock
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/network.mdx b/content/nomad/v1.0.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..03363b45af
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,296 @@
+---
+layout: docs
+page_title: network Stanza - Job Specification
+sidebar_title: network
+description: |-
+  The "network" stanza specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Stanza
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` stanza specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+When the `network` stanza is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+  for the allocations. By default all DNS configuration is inherited from the client host.
+  DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. `-1` sets the mapped port equal to the
+  dynamic port allocated by the scheduler. The `NOMAD_PORT_<label>` environment variable
+  will contain the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined
+  <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+## `network` Examples
+
+The following examples only show the `network` stanzas. Remember that the
+`network` stanza is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network stanza that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network stanza could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port stanzas.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+~> Note: `host_network` does not currently support task-based mapped ports such as the Docker driver's `port_map` configuration.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` stanza can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.0.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..416e474ed8
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,155 @@
+---
+layout: docs
+page_title: parameterized Stanza - Job Specification
+sidebar_title: parameterized
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` stanza is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Stanza
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+stanza is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` stanza allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] stanza that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.0.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..9a79e9298c
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: periodic Stanza - Job Specification
+sidebar_title: periodic
+description: |-
+  The "periodic" stanza allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Stanza
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` stanza allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+## `periodic` Examples
+
+The following examples only show the `periodic` stanzas. Remember that the
+`periodic` stanza is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.0.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..a40c59dbbc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: proxy Stanza - Job Specification
+sidebar_title: proxy
+description: |-
+  The "proxy" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Stanza
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` stanza allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](https://www.consul.io/docs/connect/proxies/envoy#dynamic-configuration)
+  for details.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.0.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..5bc71cc5ae
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Stanza - Job Specification
+sidebar_title: reschedule
+description: >-
+  The "reschedule" stanza specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Stanza
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` stanza specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule stanza is present on both the job and the group, they are merged with
+the group stanza taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the task on another node if any of its allocation
+statuses become "failed". It prefers to create a replacement allocation on a node
+that hasn't previously been used.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule stanza does not apply to `system` jobs because they run on
+every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.0.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..c92b6033b1
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: resources Stanza - Job Specification
+sidebar_title: resources
+description: |-
+  The "resources" stanza describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` stanza describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` stanzas. Remember that the
+`resources` stanza is only valid in the placements listed above.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] stanza
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+
+[device]: /docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.0.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..63c6ba3c71
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,171 @@
+---
+layout: docs
+page_title: restart Stanza - Job Specification
+sidebar_title: restart
+description: The "restart" stanza configures a group's behavior on task failure.
+---
+
+# `restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` stanza configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] stanza.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /docs/job-specification/sidecar_task
+[`reschedule`]: /docs/job-specification/reschedule
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.0.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..c38130eacc
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: scaling Stanza - Job Specification
+sidebar_title: scaling
+description: The "scaling" stanza allows specifying scaling policy for a task group
+---
+
+# `scaling` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `scaling` stanza allows configuring scaling options for a task group, for the purpose
+of supporting external autoscalers like the [Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler)
+and scaling via the Nomad UI. This stanza is not supported within jobs of type `system`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+      }
+    }
+    scaling {
+      enabled = true
+      min = 0
+      max = 10
+      policy {
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [count][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; see autoscaler documentation.
+
+[count]: /docs/job-specification/group#count 'Nomad Task Group specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/service.mdx b/content/nomad/v1.0.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..9efbfb57b0
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,723 @@
+---
+layout: docs
+page_title: service Stanza - Job Specification
+sidebar_title: service
+description: |-
+  The "service" stanza instructs Nomad to register the task as a service using
+  the service discovery integration.
+---
+
+# `service` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` stanza instructs Nomad to register a service with Consul. This
+section of the documentation will discuss the configuration, but please also
+read the [Nomad service discovery documentation][service-discovery] for more
+detailed information about the integration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and stanzas
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` stanza at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `check` <code>([Check](#check-parameters): nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, Nomad supports the
+  `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network stanza.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker or rkt).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] stanza.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](https://www.consul.io/docs/internals/anti-entropy#enable-tag-override)
+  for more information.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. This setting is supported in
+  Docker since Nomad 0.6 and rkt since Nomad 0.7. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker and rkt. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter.
+
+### `check` Parameters
+
+Note that health checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. Added in Nomad 0.7.1. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` stanza][check_restart_stanza].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the originating status of the
+  service. Valid options are the empty string, `passing`, `warning`, and
+  `critical`.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`][type] must be `http` or `grpc`, and check `name` must be set.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] stanza. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` stanzas will apply to the specified task. For `checks` on group
+  level `services` only. Inherits the [`service.task`][service_task] value if not
+  set. May only be set for script or gRPC checks.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+#### `header` Stanza
+
+HTTP checks may include a `header` stanza to set HTTP headers. The `header`
+stanza parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with Consul. It
+is important to understand when each of these steps happens and how they can be
+customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in Consul as well. Consul is updated without restarting a task.
+
+**Deregistering**: If a running task with a service stanza exits, the services
+and checks are immediately deregistered from Consul without delay. If however
+Nomad needs to kill a running task, the task is killed in the following order:
+
+1. Immediately remove the services and checks from Consul. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in Consul, and
+   thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` stanzas. Remember that the
+`service` stanza is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks.
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+This example must be accompanied by a [`network`][network] stanza which defines
+a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+### Script Checks with Shells
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name     = "Postgres Check"
+    type     = "script"
+    command  = "/usr/local/bin/pg-tools"
+    args     = ["verify", "database", "prod", "up"]
+    interval = "5s"
+    timeout  = "2s"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] stanza. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Using Driver Address Mode
+
+The [Docker](/docs/drivers/docker#network_mode) and
+[rkt](/docs/drivers/rkt#net) drivers support the `driver` setting for the
+`address_mode` parameter in both `service` and `check` stanzas. The driver
+address mode allows advertising and health checking the IP and port assigned to
+a task by the driver. This way, if you're using a network plugin like Weave with
+Docker, you can advertise the Weave address in Consul instead of the host's
+address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  network {
+    port "db" {
+      to = 6379
+    }
+  }
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than "host" or "bridge" is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` stanzas default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` stanza's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` stanzas can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` stanza to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` stanzas can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad
+  client does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_stanza]: /docs/job-specification/check_restart
+[consul_grpc]: https://www.consul.io/api/agent/check#grpc
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[service-discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /docs/job-specification/service#type
+[shutdowndelay]: /docs/job-specification/task#shutdown_delay
+[killsignal]: /docs/job-specification/task#kill_signal
+[killtimeout]: /docs/job-specification/task#kill_timeout
+[service_task]: /docs/job-specification/service#task-1
+[network_mode]: /docs/job-specification/network#mode
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.0.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..8a564054f2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: sidecar_service Stanza - Job Specification
+sidebar_title: sidecar_service
+description: |-
+  The "sidecar_service" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` stanza allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags for the sidecar service.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the sidecar proxy service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` stanza with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.0.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..ab2b4ed1db
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Stanza - Job Specification
+sidebar_title: sidecar_task
+description: |-
+  The "sidecar_task" stanza allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` stanza allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpnomad/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /docs/job-specification/gateway
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.0.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..75f0908661
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: spread Stanza - Job Specification
+sidebar_title: spread
+description: >-
+  The "spread" stanza is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread stanza may be specified with relative weights between
+  each.
+---
+
+# `spread` Stanza
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` stanza allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread stanza. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread stanza. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread stanza. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity stanza to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` stanza.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` stanza.
+
+### Even Spread Across Data Center
+
+This example shows a spread stanza across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread stanza that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread stanza that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread stanzas with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread stanza used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/task.mdx b/content/nomad/v1.0.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..694669e913
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,220 @@
+---
+layout: docs
+page_title: task Stanza - Job Specification
+sidebar_title: task
+description: |-
+  The "task" stanza creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Stanza
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` stanza creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to true, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing it from Consul and sending it a shutdown
+  signal. Ideally services would fail healthchecks once they receive a shutdown
+  signal. Alternatively `shutdown_delay` may be set to give in flight requests
+  time to complete before shutting down. In addition, task groups may have their
+  own [`shutdown_delay`](/docs/job-specification/group#shutdown_delay)
+  which waits between deregistering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` stanzas. Remember that the
+`task` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /docs/drivers/exec 'Nomad exec Driver'
+[java]: /docs/drivers/java 'Nomad Java Driver'
+[docker]: /docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /docs/configuration/client#user-checked_drivers
+[user_denylist]: /docs/configuration/client#user-denylist
+[max_kill]: /docs/configuration/client#max_kill_timeout
+[kill_signal]: /docs/job-specification/task#kill_signal
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/template.mdx b/content/nomad/v1.0.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..18704ded56
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,413 @@
+---
+layout: docs
+page_title: template Stanza - Job Specification
+sidebar_title: template
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Stanza
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. Since Nomad
+v0.5.6, the template can reference [Node attributes and metadata][nodevars]. For
+a full list of the API template functions, please refer to the [Consul Template
+README][ct]. Since Nomad v0.6.0, templates can be read as environment variables.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals] documentation.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([see below](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside of a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` stanzas. Remember that the
+`template` stanza is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] stanza to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template stanza:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To workaround this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Similar to KV API v1, if the name of a secret includes the `-` character, you
+must access it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/internals/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/update.mdx b/content/nomad/v1.0.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..74a5bd9146
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Stanza - Job Specification
+sidebar_title: update
+description: |-
+  The "update" stanza specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, rolling updates and canaries are disabled.
+---
+
+# `update` Stanza
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` stanza specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, rolling updates and canaries are disabled. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` stanzas are specified, they are merged with the
+group stanza taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` stanza in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` stanzas. Remember that the
+`update` stanza is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Stanza Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update stanza, each groups update
+stanza may be kept to a minimum. The merged update stanzas for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: https://learn.hashicorp.com/collections/nomad/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.0.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..53dc624d73
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: upstreams Stanza - Job Specification
+sidebar_title: upstreams
+description: |-
+  The "upstreams" stanza allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` stanza allows configuring various options for managing upstream
+services that a [Consul
+Connect](/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` stanza.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc1"
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpnomad/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.0.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..63e801fe99
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: vault Stanza - Job Specification
+sidebar_title: vault
+description: |-
+  The "vault" stanza allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Stanza
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` stanza allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` stanzas are specified, they are merged with the `task` stanza
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/docs/configuration/vault#namespace)
+to use [Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` stanza is specified, the [`template`][template] stanza can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.0.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..30aa010767
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: volume Stanza - Job Specification
+sidebar_title: volume
+description: >-
+  The "volume" stanza allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Stanza
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` stanza allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the stanza is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` stanzas. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] stanza in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `"ro,noatime"`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. You can use the [HCL2]
+syntax in Nomad 1.0 for fine-grained control over how volumes are used.
+
+There are two limitations to using HCL2 interpolation for `volume` blocks:
+
+- The `volume` block is used to schedule workloads, so any interpolation needs
+  to be done before placement. This means that variables like
+  `NOMAD_ALLOC_INDEX` can't be used for interpolation.
+- Nomad does not yet support dynamic volume creation (see [GH-8212]), so volumes
+  must be created and registered before being used as a `volume.source`.
+
+The following job specification demonstrates how to use multiple volumes with
+multiple allocations. It uses a `dynamic` block to create a new task group for
+each of the two volumes. This job specification also shows using HCL2
+variables interpolation to expose information to the task's environment.
+
+```hcl
+variables {
+  volume_index = ["0", "1"]
+  path         = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  dynamic "group" {
+    for_each = var.volume_index
+    labels   = ["cache-${group.value}"]
+
+    content {
+
+      volume "cache-volume" {
+        type   = "csi"
+        source = "test-volume${group.value}"
+      }
+
+      network {
+        port "db" {
+          to = 6379
+        }
+      }
+
+      task "redis" {
+        driver = "docker"
+        config {
+          image = "redis:3.2"
+          ports = ["db"]
+        }
+        resources {
+          cpu    = 500
+          memory = 256
+        }
+
+        env {
+          # this will be available as the MOUNT_PATH environment
+          # variable in the task
+          MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+        }
+
+        volume_mount {
+          volume      = "cache-volume"
+          destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+        }
+
+      }
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status test-volume0
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status test-volume1
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /docs/configuration/client#host_volume-stanza
+[csi_volume]: /docs/commands/volume/register
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume]: /docs/commands/volume/register
+[attachment mode]: /docs/commands/volume/register#attachment_mode
+[volume registration]: /docs/commands/volume/register#mount_options
+[hcl2]: /docs/job-specification/hcl2
+[gh-8212]: https://github.com/hashicorp/nomad/issues/8212
diff --git a/content/nomad/v1.0.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.0.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..85aa401f73
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Stanza - Job Specification
+sidebar_title: volume_mount
+description: |-
+  The "volume_mount" stanza allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` stanza allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /docs/job-specification/volume#volume-interpolation
+[hcl2]: /docs/job-specification/hcl2
diff --git a/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..4172c1df33
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+sidebar_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/docs/ecosystem).
diff --git a/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..4a5410c6bd
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+sidebar_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Docker-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Docker, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..993ad045ee
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+sidebar_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and Github with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![](https://lh3.googleusercontent.com/1iKJRlfp374MHd9vGxdabYebn9eCaXS3Q_aFQNB3kdRte_FMsZOui_zKdBzFofE-vq5oI1NUkgPcuxoCqQyn-Xmd4l7hzE_5XfoKkuanA0qbU_hVoERdRcpE35TDxFCB7VUGHsaG)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.0.x/content/docs/operations/index.mdx b/content/nomad/v1.0.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..ec2de41d9f
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/docs/operations/nomad-agent)
+- [Telemetry Overview](/docs/operations/telemetry)
+- [Metrics](/docs/operations/metrics)
+- [Cluster Management](https://learn.hashicorp.com/collections/nomad/manage-clusters)
+- [Transport Security](https://learn.hashicorp.com/collections/nomad/transport-security)
+- [Access Control](https://learn.hashicorp.com/collections/nomad/access-control)
diff --git a/content/nomad/v1.0.x/content/docs/operations/metrics.mdx b/content/nomad/v1.0.x/content/docs/operations/metrics.mdx
new file mode 100644
index 0000000000..042415e9c4
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/operations/metrics.mdx
@@ -0,0 +1,447 @@
+---
+layout: docs
+page_title: Metrics
+sidebar_title: Metrics
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+|---------|---------------------------------------------------------------------------------------------------------------------|-----------|
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                | Unit                           | Type    |
+|-------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                         | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                           | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                   | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_blocked`           | Evaluations that are blocked until an existing evaluation for the same job completes                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                         | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                          | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                          | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                           | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                      | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                               | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                       | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                       | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                       | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                               | ms / Raft Log Append           | Timer   |
+
+
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/docs/configuration/telemetry)
+page for more details.
+
+As of Nomad 0.9, Nomad will emit additional labels for [parameterized](/docs/job-specification/parameterized) and
+[periodic](/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+|-------------|--------------------------------|
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+|-----------------------------------------|-------------------------------------------------------------------------------------|------------|-------|---------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated_disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations blocked                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating                                                     | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated_memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on the
+task driver; not all task drivers can provide all metrics.
+
+| Metric                                        | Description                                                       | Unit        | Type  | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|-------|--------------------------------------------------|
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+|------------------------------------|------------------------------------------|---------|-------|----------------------------------|
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+|----------------------------------|------------------------|---------|-------|--------|
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                       | Unit                 | Type    | Labels |
+|------------------------------------------------------|-------------------------------------------------------------------|----------------------|---------|--------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                         | Nanoseconds          | Summary | host   |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state                               | Integer              | Gauge   | host   |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes            | Integer              | Gauge   | host   |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits                        | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                        | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                               | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                      | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                             | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                       | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                              | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                 | Integer              | Gauge   | host   |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals in the waiting state                               | Integer              | Gauge   | host   |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                 | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                 | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.alloc_update`                       | Time elapsed to apply `AllocUpdate` raft entry                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                 | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry               | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                              | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                             | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                            | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                          | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Summary` RPC call                           | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition | Nanoseconds          | Summary | host   |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store            | Nanoseconds          | Summary | host   |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store         | Nanoseconds          | Summary | host   |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                      | Nanoseconds          | Summary | host   |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                   | Nanoseconds          | Summary | host   |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                  | Integer              | Gauge   | host   |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                           | Nanoseconds          | Summary | host   |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed for the planner to obtain a snapshot                 | Nanoseconds          | Summary | host   |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                      | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                     | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                | Nanoseconds          | Gauge   | host   |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                           | Integer              | Gauge   | host   |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                | Nanoseconds          | Gauge   | host   |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                     | Integer              | Gauge   | host   |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                 | Nanoseconds          | Gauge   | host   |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                               | Nanoseconds          | Gauge   | host   |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                      | Integer              | Gauge   | host   |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                         | Integer              | Gauge   | host   |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                       | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                  | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                         | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                        | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                    | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                   | Nanoseconds          | Summary | Host   |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                         | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                        | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.invoke_scheduler_service`        | Time elapsed for worker to invoke the scheduler                   | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                   | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                            | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                    | Nanoseconds          | Summary | host   |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed for worker get snapshot                              | Nanoseconds          | Summary | host   |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                      | Integer              | Gauge   | host   |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                  | Integer              | Counter | host   |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                            | Integer              | Gauge   | host   |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                     | Nanoseconds          | Summary | host   |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                | Nanoseconds          | Summary | host   |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                              | Nanoseconds          | Summary | host   |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                            | Integer              | Gauge   | host   |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication  | Nanoseconds          | Summary | host   |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                          | Integer              | Gauge   | host   |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                      | ms / Raft Log Append | Timer   |        |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                 | Integer              | Gauge   | host   |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                  | Integer              | Gauge   | host   |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                    | Integer              | Gauge   | host   |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election               | Integer              | Gauge   | host   |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum              | Integer              | Gauge   | host   |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                 | Integer              | Gauge   | host   |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                         | Nanoseconds          | Summary | host   |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                       | # of bytes           | Gauge   | host   |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                           | Nanoseconds          | Gauge   | host   |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                       | Integer              | Gauge   | host   |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                               | Integer              | Summary | host   |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                       | Integer              | Summary | host   |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                       | Integer              | Summary | host   |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                            | Integer              | Gauge   | host   |
+
+
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
diff --git a/content/nomad/v1.0.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.0.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..5fe4be4460
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: Nomad Agent
+sidebar_title: Operating Nomad Agents
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/docs/internals/consensus) and [gossip protocol](/docs/internals/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default,
+any signal to an agent (interrupt, terminate, kill) will cause the agent
+to forcefully stop. Graceful termination can be configured by either
+setting `leave_on_interrupt` or `leave_on_terminate` to respond to the
+respective signals.
+
+When gracefully exiting, clients will update their status to terminal on
+the servers so that tasks can be migrated to healthy agents. Servers
+will notify their intention to leave the cluster which allows them to
+leave the [consensus](/docs/internals/consensus) peer set.
+
+It is especially important that a server node be allowed to leave gracefully
+so that there will be a minimal impact on availability as the server leaves
+the consensus peer set. If a server does not gracefully leave, and will not
+return into service, the [`server force-leave` command](/docs/commands/server/force-leave)
+should be used to eject it from the consensus peer set.
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/docs/internals/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
diff --git a/content/nomad/v1.0.x/content/docs/operations/telemetry.mdx b/content/nomad/v1.0.x/content/docs/operations/telemetry.mdx
new file mode 100644
index 0000000000..4126835b21
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/operations/telemetry.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: Telemetry Overview
+sidebar_title: Telemetry
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Telemetry Overview
+
+The Nomad client and server agents collect a wide range of runtime metrics
+related to the performance of the system. Operators can use this data to gain
+real-time visibility into their cluster and improve performance. Additionally,
+Nomad operators can set up monitoring and alerting based on these metrics in
+order to respond to any changes in the cluster state.
+
+On the server side, leaders and
+followers have metrics in common as well as metrics that are specific to their
+roles. Clients have separate metrics for the host metrics and for
+allocations/tasks, both of which have to be [explicitly
+enabled][telemetry-stanza]. There are also runtime metrics that are common to
+all servers and clients.
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [Gauges, counters and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/metrics API endpoint][metrics-api-endpoint] to return metrics for
+  the current Nomad process (as of Nomad 0.7). This endpoint supports Prometheus
+  formatted metrics.
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+- Configure Nomad to automatically forward metrics to a third-party provider.
+
+Nomad 0.7 added support for [tagged metrics][tagged-metrics], improving the
+integrations with [DataDog][datadog-telem] and [Prometheus][prometheus-telem].
+Metrics can also be forwarded to [Statsite][statsite-telem],
+[StatsD][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns:
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+The sections below cover a number of important metrics
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking issues
+between the servers or insufficient CPU resources. Users in cloud environments
+often bump their servers up to the next instance class with improved networking
+and CPU to stabilize leader elections. The `nomad.raft.leader.lastContact` metric
+is a general indicator of Raft latency which can be used to observe how Raft
+timing is performing and guide the decision to upgrade to more powerful servers.
+`nomad.raft.leader.lastContact` should not get too close to the leader lease
+timeout of 500ms.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+## Scheduling
+
+The following metrics allow an operator to observe changes in throughput at the
+various points in the scheduling process (evaluation, scheduling/planning, and
+placement):
+
+- **nomad.broker.total_blocked** - The number of blocked evaluations.
+- **nomad.worker.invoke_scheduler.\<type\>** - The time to run the scheduler of
+  the given type.
+- **nomad.plan.evaluate** - The time to evaluate a scheduler Plan.
+- **nomad.plan.submit** - The time to submit a scheduler Plan.
+- **nomad.plan.queue_depth** - The number of scheduler Plans waiting to be
+  evaluated.
+
+Upticks in any of the above metrics indicate a decrease in scheduler throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis:
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+We do not currently surface metrics for job and task/allocation status, although
+we will consider adding metrics where it makes sense.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure:
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /docs/configuration/telemetry#circonus
+[collection-interval]: /docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /docs/configuration/telemetry#datadog
+[prometheus-telem]: /docs/configuration/telemetry#prometheus
+[metrics-api-endpoint]: /api-docs/metrics
+[metric-types]: /docs/telemetry/metrics#metric-types
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /docs/configuration/telemetry#statsd
+[statsite-telem]: /docs/configuration/telemetry#statsite
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[telemetry-stanza]: /docs/configuration/telemetry
diff --git a/content/nomad/v1.0.x/content/docs/runtime/environment.mdx b/content/nomad/v1.0.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..ab2349f8cf
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: Environment - Runtime
+sidebar_title: Runtime Environment
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT` and
+`NOMAD_MEMORY_LIMIT`. Your task should use these values to adapt its behavior to
+fit inside the resource allocation that nomad provides. For example, you can use
+the memory limit to inform how large your in-process cache should be, or to
+decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs and where possible backed by an
+  in-memory filesystem. It can be used to store secret data that should not be
+  visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[vault]: /docs/vault-integration 'Nomad Vault Integration'
+[filesystem internals]: /docs/internals/filesystem
diff --git a/content/nomad/v1.0.x/content/docs/runtime/index.mdx b/content/nomad/v1.0.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..395b323583
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/docs/runtime/environment)
+- [Interpolation](/docs/runtime/interpolation)
+- [Schedulers](/docs/schedulers)
diff --git a/content/nomad/v1.0.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.0.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..b3a873c55d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,341 @@
+---
+layout: docs
+page_title: Variable Interpolation
+sidebar_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.placement.availability-zone}'}</code>
+      </td>
+      <td>Availability Zone of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:3.2"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.0.x/content/docs/schedulers.mdx b/content/nomad/v1.0.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..304f6d60c2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/schedulers.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: Schedulers
+sidebar_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has three scheduler types that can be used when creating your job:
+`service`, `batch` and `system`. Here we will describe the differences between
+each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] stanzas.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+stanzas.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] stanza; system jobs do not have rescheduling.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
+[preemption]: /docs/internals/scheduling/preemption
+[restart]: /docs/job-specification/restart
+[reschedule]: /docs/job-specification/reschedule
diff --git a/content/nomad/v1.0.x/content/docs/upgrade/index.mdx b/content/nomad/v1.0.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..decd7ba44a
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /docs/configuration#data_dir
+[heartbeat_grace]: /docs/configuration/server#heartbeat_grace
+[monitor]: /docs/commands/monitor
+[node-status]: /docs/commands/node/status
+[server-members]: /docs/commands/server/members
+[upgrade-specific]: /docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.0.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.0.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..9365ca880d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1157 @@
+---
+layout: docs
+page_title: Upgrade Guides
+sidebar_title: Specific Version Details
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task.  In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details). The
+`nomad license put` command has been removed.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](https://www.nomadproject.io/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overriden.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. stanzas). Check [HCL](/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` stanza were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` stanza are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/docs/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/docs/configuration/client#host_volume-stanza) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits stanza is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update stanza when a service job is created or updated. This does not
+affect jobs with an update stanza.
+
+In pre-0.10 releases, when updating a service job without an update stanza, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` stanza][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` stanzas:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/docs/job-specification/env) stanza to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] stanzas are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-stanza] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` stanza. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` stanza could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` stanza, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` stanza or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` stanza will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/docs/job-specification/network#to) field on group network port stanzas
+will be interpolated properly. Please see the
+[`network`](/docs/job-specification/network/) stanza documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`](/docs/configuration/server#raft_protocol) option in
+their `server` stanza to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](https://learn.hashicorp.com/tutorials/nomad/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+#### Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3 in Nomad 0.8 and
+higher. Raft protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. See [Raft Protocol Version
+Compatibility](/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility)
+for more details. Also the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+Please note that the Raft protocol is different from Nomad's internal protocol
+as shown in commands like `nomad server members`. To see the version of the Raft
+protocol in use on each server, use the `nomad operator raft list-peers`
+command.
+
+The easiest way to upgrade servers is to have each server leave the cluster,
+upgrade its `raft_protocol` version in the `server` stanza, and then add it
+back. Make sure the new server joins successfully and that the cluster is stable
+before rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the older
+servers in a similar fashion.
+
+When using Raft protocol version 3, servers are identified by their `node-id`
+instead of their IP address when Nomad makes changes to its internal Raft quorum
+configuration. This means that once a cluster has been upgraded with servers all
+running Raft protocol version 3, it will no longer allow servers running any
+older Raft protocol versions to be added. If running a single Nomad server,
+restarting it in-place will result in that server not being able to elect itself
+as a leader. To avoid this, either set the Raft protocol back to 2, or use
+[Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+to map the server to its node ID in the Raft quorum configuration.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] stanza in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` stanza documentation][migrate] and [Decommissioning Nodes
+guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/docs/job-specification/env) and
+[`template`](/docs/job-specification/template) stanzas.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following stanza:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[dangling-containers]: /docs/drivers/docker#dangling-containers
+[drain-api]: /api-docs/nodes#drain-node
+[drain-cli]: /docs/commands/node/drain
+[dst]: /docs/job-specification/periodic#daylight-saving-time
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /docs/configuration#limits
+[lxc]: /docs/drivers/external/lxc
+[migrate]: /docs/job-specification/migrate
+[plugin-stanza]: /docs/configuration/plugin
+[plugins]: /docs/drivers/external
+[preemption-api]: /api-docs/operator#update-scheduler-configuration
+[preemption]: /docs/internals/scheduling/preemption
+[proxy_concurrency]: /docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /docs/configuration/client#reserved-parameters
+[task-config]: /docs/job-specification/task#config
+[tls-guide]: https://learn.hashicorp.com/tutorials/nomad/security-enable-tls
+[tls-vault-guide]: https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad
+[update]: /docs/job-specification/update
+[validate]: /docs/commands/job/validate
+[vault_grace]: /docs/job-specification/template
+[node drain]: https://www.nomadproject.io/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /docs/configuration/client#template-parameters
+[pki]: https://www.vaultproject.io/docs/secrets/pki
+[`volume create`]: /docs/commands/volume/create
+[`volume register`]: /docs/commands/volume/register
+[`volume`]: /docs/job-specification/volume
+[Enterprise licensing]: /docs/enterprise/license
+[`CAP_NET_RAW`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /docs/drivers/docker#allow_caps
+<<<<<<< HEAD
+=======
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /docs/drivers/exec#allow_caps
+[allow_caps_java]: /docs/drivers/java#allow_caps
+[cap_add_exec]: /docs/drivers/exec#cap_add
+[cap_drop_exec]: /docs/drivers/exec#cap_drop
+[`log_file`]: /docs/configuration#log_file
+>>>>>>> d74ab11d2 (Don't timestamp active log file (#11070))
diff --git a/content/nomad/v1.0.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.0.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..0e4f141455
--- /dev/null
+++ b/content/nomad/v1.0.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+sidebar_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, CloudFlare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### CloudFlare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.0.x/content/intro/index.mdx b/content/nomad/v1.0.x/content/intro/index.mdx
new file mode 100644
index 0000000000..10b83dd7db
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/index.mdx
@@ -0,0 +1,57 @@
+---
+layout: intro
+page_title: Introduction
+sidebar_title: What is Nomad?
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/docs) and [HashiCorp Learn guides](https://learn.hashicorp.com/nomad) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/intro/use-cases) and [Who Uses Nomad](/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.0.x/content/intro/use-cases.mdx b/content/nomad/v1.0.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..12a7319e74
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/use-cases.mdx
@@ -0,0 +1,67 @@
+---
+layout: intro
+page_title: Use Cases
+sidebar_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker)
+and integrates seamlessly with [Consul](/docs/integrations/consul-integration)
+and [Vault](/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.0.x/content/intro/vs/ecs.mdx b/content/nomad/v1.0.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..47006274e2
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+sidebar_title: AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.0.x/content/intro/vs/index.mdx b/content/nomad/v1.0.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..c75add3cbe
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/vs/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+sidebar_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.0.x/content/intro/vs/mesos.mdx b/content/nomad/v1.0.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..6d957ab418
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,36 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+sidebar_title: Mesos & Marathon
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.0.x/content/intro/vs/terraform.mdx b/content/nomad/v1.0.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..e1a2f839ee
--- /dev/null
+++ b/content/nomad/v1.0.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,32 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+sidebar_title: Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.0.x/content/partials/envvars.mdx b/content/nomad/v1.0.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..83c3c44a52
--- /dev/null
+++ b/content/nomad/v1.0.x/content/partials/envvars.mdx
@@ -0,0 +1,264 @@
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_DIR</code>
+      </td>
+      <td>
+        The path to the shared <code>alloc/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">
+          here for more
+        </a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_DIR</code>
+      </td>
+      <td>
+        The path to the task <code>local/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_SECRETS_DIR</code>
+      </td>
+      <td>
+        Path to the task's secrets directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_MEMORY_LIMIT</code>
+      </td>
+      <td>Memory limit in MB for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_CPU_LIMIT</code>
+      </td>
+      <td>CPU limit in MHz for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_ID</code>
+      </td>
+      <td>Allocation ID of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_NAME</code>
+      </td>
+      <td>Allocation name of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_INDEX</code>
+      </td>
+      <td>
+        Allocation index; useful to distinguish instances of task groups. From 0
+        to (count - 1). The index is unique within a given version of a job, but
+        canaries or failed tasks in a deployment may reuse the index.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_NAME</code>
+      </td>
+      <td>Task's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_GROUP_NAME</code>
+      </td>
+      <td>Group's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_ID</code>
+      </td>
+      <td>
+        Job's ID, which is equal to the Job name when submitted through
+        CLI but can be different when using the API
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_NAME</code>
+      </td>
+      <td>Job's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_PARENT_ID</code>
+      </td>
+      <td>ID of the Job's parent if it has one</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_DC</code>
+      </td>
+      <td>Datacenter in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_NAMESPACE</code>
+      </td>
+      <td>Namespace in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_REGION</code>
+      </td>
+      <td>Region in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_META_&lt;key&gt;</code>
+      </td>
+      <td>
+        The metadata value given by <code>key</code> on the task's
+        metadata. Note that this is different from
+        <a href="/docs/runtime/interpolation#node-variables-">
+          <code>$&#123;meta.&lt;key&gt;&#125;</code>
+        </a>
+        which are keys in the node's metadata.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>VAULT_TOKEN</code>
+      </td>
+      <td>
+        The task's Vault token. See
+        <a href="/docs/vault-integration">Vault Integration</a>
+        for more details
+      </td>
+    </tr>
+    <tr>
+      <th colspan="2">Network-related Variables</th>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code>. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code>. Driver-specified port when a
+        port map is used, otherwise the host's static or dynamic port
+        allocation. Services should bind to this port. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code>. See
+        <a href="/docs/job-specification/network#mapped-ports">here</a> for more
+        information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group. Driver-specified port when a port map is
+        used, otherwise the host's static or dynamic port allocation.
+        Services should bind to this port.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code> and
+        <code>task</code> for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code> and <code>task</code>
+        for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_IP_&lt;service&gt;</code>
+      </td>
+      <td>
+        IP for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_PORT_&lt;service&gt;</code>
+      </td>
+      <td>
+        Port for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> for the given <code>service</code> when
+        defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ENVOY_ADMIN_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Local address <code>localhost:Port</code> for the admin port of the
+        envoy sidecar for the given <code>service</code> when defined as a
+        Consul Connect enabled service.
+      </td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.0.x/content/partials/general_options.mdx b/content/nomad/v1.0.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..3a2cef9c8d
--- /dev/null
+++ b/content/nomad/v1.0.x/content/partials/general_options.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespacecs authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.0.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.0.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..7ae431c4f5
--- /dev/null
+++ b/content/nomad/v1.0.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,35 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.0.x/data/alert-banner.js b/content/nomad/v1.0.x/data/alert-banner.js
new file mode 100644
index 0000000000..7962af6664
--- /dev/null
+++ b/content/nomad/v1.0.x/data/alert-banner.js
@@ -0,0 +1,13 @@
+export const ALERT_BANNER_ACTIVE = true
+
+// https://github.com/hashicorp/web-components/tree/master/packages/alert-banner
+export default {
+  linkText: 'Let us know!',
+  url: 'https://docs.google.com/forms/d/e/1FAIpQLSeTre9Uvsfohl3yKLdTf0jUACT2GQgvGBsbp4fZvARpFwdv-g/viewform',
+  tag: 'FREE SWAG',
+  text:
+    'Share your Nomad success story for a chance to win special swag.',
+  // Set the `expirationDate prop with a datetime string (e.g. `2020-01-31T12:00:00-07:00`)
+  // if you'd like the component to stop showing at or after a certain date
+  expirationDate: '2021-02-08T09:00:00-07:00',
+}
diff --git a/content/nomad/v1.0.x/data/api-docs-nav-data.json b/content/nomad/v1.0.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..a864be8539
--- /dev/null
+++ b/content/nomad/v1.0.x/data/api-docs-nav-data.json
@@ -0,0 +1,145 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.0.x/data/docs-nav-data.json b/content/nomad/v1.0.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..2ccf2b5c14
--- /dev/null
+++ b/content/nomad/v1.0.x/data/docs-nav-data.json
@@ -0,0 +1,1575 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Connect",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Internals",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "internals"
+      },
+      {
+        "title": "Architecture",
+        "path": "internals/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "internals/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "internals/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "internals/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "internals/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "internals/scheduling"
+          },
+          {
+            "title": "Internals",
+            "path": "internals/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "internals/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "internals/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "internals/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "internals/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "internals/security"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval status",
+        "path": "commands/eval-status"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "put",
+            "path": "commands/license/put"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "autopilot get-config",
+            "path": "commands/operator/autopilot-get-config"
+          },
+          {
+            "title": "autopilot set-config",
+            "path": "commands/operator/autopilot-set-config"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft list-peers",
+            "path": "commands/operator/raft-list-peers"
+          },
+          {
+            "title": "raft remove-peer",
+            "path": "commands/operator/raft-remove-peer"
+          },
+          {
+            "title": "snapshot agent",
+            "path": "commands/operator/snapshot-agent"
+          },
+          {
+            "title": "snapshot inspect",
+            "path": "commands/operator/snapshot-inspect"
+          },
+          {
+            "title": "snapshot restore",
+            "path": "commands/operator/snapshot-restore"
+          },
+          {
+            "title": "snapshot save",
+            "path": "commands/operator/snapshot-save"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin <sup>Beta</sup>",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/external"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/external/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/external/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "path": "drivers/external/jail-task-driver"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/external/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/external/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/external/rkt"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/external/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/external/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/external/iis"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/external"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "path": "devices/external/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Agent",
+        "path": "autoscaling/agent"
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "path": "autoscaling/plugins/apm"
+          },
+          {
+            "title": "Strategy",
+            "path": "autoscaling/plugins/strategy"
+          },
+          {
+            "title": "Target",
+            "path": "autoscaling/plugins/target"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "path": "autoscaling/internals/checks"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Telemetry",
+        "path": "operations/telemetry"
+      },
+      {
+        "title": "Metrics",
+        "path": "operations/metrics"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "path": "enterprise"
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
\ No newline at end of file
diff --git a/content/nomad/v1.0.x/data/guides-navigation.js b/content/nomad/v1.0.x/data/guides-navigation.js
new file mode 100644
index 0000000000..666a86e531
--- /dev/null
+++ b/content/nomad/v1.0.x/data/guides-navigation.js
@@ -0,0 +1,100 @@
+// The root folder for this documentation category is `pages/guides`
+//
+// - A string refers to the name of a file
+// - A "category" value refers to the name of a directory
+// - All directories must have an "index.mdx" file to serve as
+//   the landing page for the category
+
+export default [
+  {
+    category: 'install',
+    content: [
+      { category: 'quickstart' },
+      {
+        category: 'production',
+        content: [
+          'requirements',
+          'nomad-agent',
+          'reference-architecture',
+          'deployment-guide',
+        ],
+      },
+      'windows-service',
+    ],
+  },
+  { category: 'upgrade', content: ['upgrade-specific'] },
+  {
+    category: 'integrations',
+    content: ['consul-integration', 'consul-connect', 'vault-integration'],
+  },
+  '-----------',
+  {
+    category: 'operating-a-job',
+    content: [
+      'configuring-tasks',
+      'submitting-jobs',
+      'inspecting-state',
+      'accessing-logs',
+      'resource-utilization',
+      {
+        category: 'update-strategies',
+        content: [
+          'rolling-upgrades',
+          'blue-green-and-canary-deployments',
+          'handling-signals',
+        ],
+      },
+      {
+        category: 'failure-handling-strategies',
+        content: ['restart', 'check-restart', 'reschedule'],
+      },
+      {
+        category: 'advanced-scheduling',
+        content: ['affinity', 'spread', 'preemption-service-batch'],
+      },
+      { category: 'external', content: ['lxc'] },
+    ],
+  },
+  {
+    category: 'operations',
+    content: [
+      {
+        category: 'cluster',
+        content: ['manual', 'automatic', 'cloud_auto_join'],
+      },
+      'federation',
+      'node-draining',
+      'outage',
+      { category: 'monitoring-and-alerting', content: ['prometheus-metrics'] },
+      'autopilot',
+    ],
+  },
+
+  {
+    category: 'security',
+    content: ['encryption', 'acl', 'securing-nomad', 'vault-pki-integration'],
+  },
+  { category: 'stateful-workloads' },
+  {
+    category: 'analytical-workloads',
+    content: [
+      {
+        category: 'spark',
+        content: [
+          'pre',
+          'customizing',
+          'resource',
+          'dynamic',
+          'submit',
+          'hdfs',
+          'monitoring',
+          'configuration',
+        ],
+      },
+    ],
+  },
+
+  { category: 'load-balancing' },
+  { category: 'governance-and-policy', content: [] },
+  { category: 'web-ui', content: [] },
+]
diff --git a/content/nomad/v1.0.x/data/intro-nav-data.json b/content/nomad/v1.0.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..7abd058898
--- /dev/null
+++ b/content/nomad/v1.0.x/data/intro-nav-data.json
@@ -0,0 +1,56 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "https://learn.hashicorp.com/collections/nomad/get-started"
+      },
+      {
+        "title": "Running Nomad",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-run"
+      },
+      {
+        "title": "Jobs",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs"
+      },
+      {
+        "title": "Clustering",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster"
+      },
+      {
+        "title": "Web UI",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui"
+      },
+      {
+        "title": "Next Steps",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.0.x/data/metadata.js b/content/nomad/v1.0.x/data/metadata.js
new file mode 100644
index 0000000000..2a0c093fa7
--- /dev/null
+++ b/content/nomad/v1.0.x/data/metadata.js
@@ -0,0 +1,2 @@
+export const productName = 'Nomad'
+export const productSlug = 'nomad'
diff --git a/content/nomad/v1.0.x/data/subnav.js b/content/nomad/v1.0.x/data/subnav.js
new file mode 100644
index 0000000000..56ddf5dd05
--- /dev/null
+++ b/content/nomad/v1.0.x/data/subnav.js
@@ -0,0 +1,46 @@
+export default [
+  { text: 'Overview', url: '/', type: 'inbound' },
+  {
+    text: 'Use Cases',
+    submenu: [
+      {
+        text: 'Simple Container Orchestration',
+        url: '/use-cases/simple-container-orchestration',
+      },
+      {
+        text: 'Non-Containerized Application Orchestration',
+        url: '/use-cases/non-containerized-application-orchestration',
+      },
+      {
+        text: 'Automated Service Networking with Consul',
+        url: '/use-cases/automated-service-networking-with-consul',
+      },
+    ],
+  },
+  {
+    text: 'Enterprise',
+    url: 'https://www.hashicorp.com/products/nomad/',
+    type: 'outbound',
+  },
+  'divider',
+  {
+    text: 'Tutorials',
+    url: 'https://learn.hashicorp.com/nomad',
+    type: 'outbound',
+  },
+  {
+    text: 'Docs',
+    url: '/docs',
+    type: 'inbound',
+  },
+  {
+    text: 'API',
+    url: '/api-docs',
+    type: 'inbound',
+  },
+  {
+    text: 'Community',
+    url: '/community',
+    type: 'inbound',
+  },
+]
diff --git a/content/nomad/v1.0.x/data/version.js b/content/nomad/v1.0.x/data/version.js
new file mode 100644
index 0000000000..95621b043c
--- /dev/null
+++ b/content/nomad/v1.0.x/data/version.js
@@ -0,0 +1 @@
+export default '1.0.3'
diff --git a/content/nomad/v1.0.x/img/count-dashboard.png b/content/nomad/v1.0.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.0.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.0.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.0.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.0.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/favicon-16x16.png b/content/nomad/v1.0.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/favicon-194x194.png b/content/nomad/v1.0.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/favicon-32x32.png b/content/nomad/v1.0.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/favicon.ico b/content/nomad/v1.0.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.0.x/img/favicons/mstile-144x144.png b/content/nomad/v1.0.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/mstile-150x150.png b/content/nomad/v1.0.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/mstile-310x150.png b/content/nomad/v1.0.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/mstile-310x310.png b/content/nomad/v1.0.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/mstile-70x70.png b/content/nomad/v1.0.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.0.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.0.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.0.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.0.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.0.x/img/logo-hashicorp.svg b/content/nomad/v1.0.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v1.0.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.0.x/img/logo-text.svg b/content/nomad/v1.0.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.0.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.0.x/img/nomad-architecture-global.png b/content/nomad/v1.0.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.0.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.0.x/img/nomad-architecture-region.png b/content/nomad/v1.0.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.0.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.0.x/img/nomad-data-model.png b/content/nomad/v1.0.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.0.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.0.x/img/nomad-evaluation-flow.png b/content/nomad/v1.0.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.0.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.0.x/img/nomad-hero-pattern.svg b/content/nomad/v1.0.x/img/nomad-hero-pattern.svg
new file mode 100644
index 0000000000..b73292eb68
--- /dev/null
+++ b/content/nomad/v1.0.x/img/nomad-hero-pattern.svg
@@ -0,0 +1,1688 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="509" fill="none" viewBox="0 0 1600 509" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="1600" height="509" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+    <path fill="#00BC7F" d="M0 0h1600v509H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g opacity=".75">
+      <path fill="url(#b)" d="M1363.61 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#c)" d="M1382.37 171.828c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#d)" d="M1401.05 182.572c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#e)" d="M1401.05 161.005c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#f)" d="M1288.91 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M1307.58 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#h)" d="M1326.26 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#i)" d="M1326.26 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#j)" d="M1344.94 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#k)" d="M1363.61 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#l)" d="M1344.94 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M1363.61 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#n)" d="M1382.37 214.961c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#o)" d="M1401.05 225.785c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#p)" d="M1382.37 193.395c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#q)" d="M1401.05 204.138c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#r)" d="M1232.8 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#s)" d="M1251.55 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#t)" d="M1251.55 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#u)" d="M1270.23 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#v)" d="M1288.91 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#w)" d="M1270.23 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#x)" d="M1288.91 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#y)" d="M1307.58 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#z)" d="M1326.26 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#A)" d="M1307.58 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#B)" d="M1326.26 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#C)" d="M1344.94 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#D)" d="M1363.61 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#E)" d="M1344.94 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#F)" d="M1363.61 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#G)" d="M1382.37 258.095c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823a.6.6 0 0 1-.32.081" opacity=".9"/>
+      <path fill="url(#H)" d="M1401.05 268.918c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#I)" d="M1382.37 236.528c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#J)" d="M1401.05 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#K)" d="M1232.8 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#L)" d="M1251.55 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#M)" d="M1232.8 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#N)" d="M1251.55 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#O)" d="M1270.23 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#P)" d="M1288.91 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#Q)" d="M1270.23 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#R)" d="M1288.91 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#S)" d="M1307.58 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#T)" d="M1326.26 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#U)" d="M1307.58 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#V)" d="M1326.26 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#W)" d="M1344.94 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#X)" d="M1363.61 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.744c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823z" opacity=".8"/>
+      <path fill="url(#Y)" d="M1344.94 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#Z)" d="M1363.61 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aa)" d="M1382.37 301.308c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ab)" d="M1401.05 312.051c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ac)" d="M1382.37 279.741c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ad)" d="M1401.05 290.484c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ae)" d="M1232.8 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#af)" d="M1251.55 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ag)" d="M1232.8 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#ah)" d="M1251.55 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#ai)" d="M1270.23 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aj)" d="M1288.91 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ak)" d="M1270.23 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#al)" d="M1288.91 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#am)" d="M1307.58 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#an)" d="M1326.26 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ao)" d="M1307.58 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#ap)" d="M1326.26 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aq)" d="M1344.94 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#ar)" d="M1363.61 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#as)" d="M1344.94 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#at)" d="M1363.61 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#au)" d="M1382.37 344.441c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#av)" d="M1401.05 355.264c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aw)" d="M1382.37 322.874c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#ax)" d="M1401.05 333.698c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#ay)" d="M1232.8 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#az)" d="M1251.55 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aA)" d="M1232.8 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#aB)" d="M1251.55 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#aC)" d="M1270.23 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aD)" d="M1288.91 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aE)" d="M1270.23 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#aF)" d="M1288.91 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#aG)" d="M1307.58 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#aH)" d="M1326.26 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aI)" d="M1307.58 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09 0-.25.081-.33.081" opacity=".5"/>
+      <path fill="url(#aJ)" d="M1326.26 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aK)" d="M1344.94 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#aL)" d="M1363.61 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#aM)" d="M1344.94 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08 0-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#aN)" d="M1363.61 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.09.081-.17.081-.33.081" opacity=".8"/>
+      <path fill="url(#aO)" d="M1382.37 387.654c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#aP)" d="M1401.05 398.397c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#aQ)" d="M1382.37 366.088c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16 0-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#aR)" d="M1401.05 376.831c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#aS)" d="M1232.8 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aT)" d="M1251.55 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aU)" d="M1232.8 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#aV)" d="M1251.55 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17 0-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#aW)" d="M1270.23 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aX)" d="M1288.91 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#aY)" d="M1270.23 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#aZ)" d="M1288.91 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#ba)" d="M1307.58 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bb)" d="M1326.26 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bc)" d="M1307.58 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09.08-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bd)" d="M1326.26 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#be)" d="M1344.94 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bf)" d="M1363.61 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bg)" d="M1344.94 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08.08-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bh)" d="M1363.61 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09 0-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bi)" d="M1382.37 430.787c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bj)" d="M1401.05 441.61c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bk)" d="M1382.37 409.221c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16.08-.24.08-.32.08" opacity=".9"/>
+      <path fill="url(#bl)" d="M1401.05 420.044c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#bm)" d="M1232.8 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bn)" d="M1251.55 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.67 10.823c-.17.081-.25.081-.33.081" opacity=".2"/>
+      <path fill="url(#bo)" d="M1232.8 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".1"/>
+      <path fill="url(#bp)" d="M1251.55 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bq)" d="M1270.23 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.68 10.823c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#br)" d="M1288.91 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.67-10.823c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".4"/>
+      <path fill="url(#bs)" d="M1270.23 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".3"/>
+      <path fill="url(#bt)" d="M1288.91 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bu)" d="M1307.58 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.641-.24.802l-18.67 10.823c-.09 0-.25.08-.33.08" opacity=".5"/>
+      <path fill="url(#bv)" d="M1326.26 484.744c-.24 0-.4-.081-.48-.321-.16-.321-.08-.641.24-.802l18.68-10.823c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.24.081-.32.081" opacity=".6"/>
+      <path fill="url(#bw)" d="M1307.58 452.354c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l18.6-10.743c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824z" opacity=".5"/>
+      <path fill="url(#bx)" d="M1326.26 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.68 10.823c-.08.08-.24.08-.32.08" opacity=".6"/>
+      <path fill="url(#by)" d="M1344.94 474c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.641-.24.802l-18.68 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#bz)" d="M1344.94 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.08.81.24.16.321.08.642-.24.802l-18.68 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#bA)" d="M1363.61 463.177c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.802l-18.67 10.823c-.09.08-.17.08-.33.08" opacity=".8"/>
+      <path fill="url(#bB)" d="M1382.37 452.354c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-18.68 10.823c-.16.081-.24.081-.32.081" opacity=".9"/>
+      <path fill="url(#bC)" d="M1232.8 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.67-10.823c.32-.161.65-.081.81.24s.08.642-.24.802l-18.68 10.823c-.08.08-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bD)" d="M1232.8 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241.16.32.08.641-.24.801l-18.68 10.824c-.08 0-.16.08-.32.08" opacity=".1"/>
+      <path fill="url(#bE)" d="M1251.55 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241s.08.641-.24.802l-18.67 10.823c-.17.08-.25.08-.33.08" opacity=".2"/>
+      <path fill="url(#bF)" d="M1270.23 517.133c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bG)" d="M1270.23 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.68 10.824c-.16 0-.24.08-.32.08" opacity=".3"/>
+      <path fill="url(#bH)" d="M1288.91 506.31c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.67-10.824c.32-.16.65-.08.81.241s.08.641-.24.802l-18.68 10.823c-.16.08-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#bI)" d="M1307.58 495.567c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l18.68-10.824c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-18.67 10.824c-.09 0-.25.08-.33.08" opacity=".5"/>
+    </g>
+    <path fill="url(#bJ)" d="M130.232 9.88c-.08 0-.24 0-.32-.081L110.353-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L112.678-1.505l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bK)" d="M167.585 9.88c-.08 0-.24 0-.32-.081L147.706-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803L150.031-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#bL)" d="M148.909 20.703c-.08 0-.241 0-.321-.08L129.03 9.317l19.558-11.304c.321-.16.642-.08.802.24s.08.641-.241.802L131.354 9.318l17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bM)" d="M130.232 31.526c-.08 0-.24 0-.32-.08L110.353 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L112.678 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.321.321-.481.321"/>
+    <path fill="url(#bN)" d="M204.939 9.879c-.08 0-.241 0-.321-.08L185.06-1.506l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384-1.506l17.795 10.263c.321.16.401.56.241.801-.08.24-.241.32-.481.32"/>
+    <path fill="url(#bO)" d="M186.262 20.703c-.08 0-.24 0-.32-.08L166.383 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L168.708 9.318l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bP)" d="M167.585 31.526c-.08 0-.24 0-.32-.08L147.706 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802L150.031 20.14l17.795 10.262c.321.16.401.562.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bQ)" d="M148.909 42.269c-.08 0-.241 0-.321-.08L129.03 30.884l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#bR)" d="M130.232 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.32-.481.32"/>
+    <path fill="url(#bS)" d="M242.292 9.88c-.08 0-.24 0-.32-.081L222.413-1.505l19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803L224.738-1.505l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#bT)" d="M223.616 20.703c-.081 0-.241 0-.321-.08L203.737 9.317l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.641-.241.802L206.141 9.318l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#bU)" d="M204.939 31.526c-.08 0-.241 0-.321-.08L185.06 20.14l19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802L187.384 20.14l17.795 10.263c.321.16.401.56.241.801-.08.16-.241.321-.481.321"/>
+    <path fill="url(#bV)" d="M186.262 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#bW)" d="M167.585 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#bX)" d="M148.909 63.836c-.08 0-.241 0-.321-.08L129.03 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L131.435 52.45l17.794 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32"/>
+    <path fill="url(#bY)" d="M130.232 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.321.321-.481.321"/>
+    <path fill="url(#bZ)" d="M279.726 9.88c-.08 0-.241 0-.321-.081L259.847-1.505l19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803L262.251-1.505l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#ca)" d="M261.049 20.703c-.08 0-.24 0-.321-.08L241.17 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802L243.495 9.318 261.29 19.58c.32.16.4.562.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cb)" d="M242.292 31.526c-.08 0-.24 0-.32-.08L222.413 20.14l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L224.738 20.14l17.795 10.263c.32.16.401.56.24.801 0 .16-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cc)" d="M223.616 42.27c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#cd)" d="M204.939 53.093c-.08 0-.241 0-.321-.08L185.06 41.708l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32"/>
+    <path fill="url(#ce)" d="M186.262 63.836c-.08 0-.24 0-.32-.08L166.383 52.45l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802L168.788 52.45l17.795 10.262c.321.16.401.562.24.802-.16.24-.32.32-.561.32"/>
+    <path fill="url(#cf)" d="M167.585 74.659c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321"/>
+    <path fill="url(#cg)" d="M148.909 85.483c-.08 0-.241 0-.321-.08L129.03 74.097l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802l-17.714 10.262 17.794 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32"/>
+    <path fill="url(#ch)" d="M130.232 96.226c-.08 0-.24 0-.32-.08L110.353 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L112.678 84.84l17.795 10.262c.32.16.4.562.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#ci)" d="M317.079 9.88c-.08 0-.24 0-.32-.081L297.2-1.505l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803L299.525-1.505 317.32 8.757c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cj)" d="M298.402 20.703c-.08 0-.24 0-.32-.08L278.523 9.317l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L280.848 9.318l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+    <path fill="url(#ck)" d="M279.726 31.526c-.08 0-.241 0-.321-.08L259.847 20.06l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 20.06l17.795 10.262c.321.16.401.561.241.802-.16.24-.401.4-.561.4" opacity=".7"/>
+    <path fill="url(#cl)" d="M261.049 42.27c-.08 0-.24 0-.321-.081L241.17 30.885l19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#cm)" d="M242.292 53.092c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cn)" d="M223.616 63.836c-.081 0-.241 0-.321-.08L203.737 52.45l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L206.141 52.45l17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#co)" d="M204.939 74.659c-.08 0-.241 0-.321-.08L185.06 63.274l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cp)" d="M186.262 85.482c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.322.08.642-.24.803l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.16.16-.32.32-.561.32"/>
+    <path fill="url(#cq)" d="M167.585 96.226c-.08 0-.24 0-.32-.08L147.706 84.84l19.559-11.304c.32-.16.641-.08.801.24s.081.641-.24.802L150.031 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#cr)" d="M148.909 107.049c-.08 0-.241 0-.321-.08L129.03 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cs)" d="M130.232 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.321.321-.481.321"/>
+    <path fill="url(#ct)" d="M354.433 9.88c-.081 0-.241 0-.321-.081L334.553-1.505l19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803L336.878-1.505l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cu)" d="M335.756 20.703c-.08 0-.241 0-.321-.08L315.877 9.318l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.201 9.318l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cv)" d="M317.079 31.526c-.08 0-.24 0-.32-.08L297.2 20.14l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802L299.525 20.14l17.795 10.263c.32.16.4.56.24.801-.08.16-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cw)" d="M298.402 42.27c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.32.321-.481.321" opacity=".6"/>
+    <path fill="url(#cx)" d="M279.726 53.092c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.401.32-.561.32" opacity=".7"/>
+    <path fill="url(#cy)" d="M261.049 63.836c-.08 0-.24 0-.321-.08L241.09 52.45l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L243.495 52.45l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cz)" d="M242.292 74.66c-.08 0-.24-.001-.32-.081l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801 0 .24-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#cA)" d="M223.616 85.482c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32"/>
+    <path fill="url(#cB)" d="M204.939 96.226c-.08 0-.241 0-.321-.08L185.06 84.84l19.558-11.304c.321-.16.642-.08.802.24s.08.642-.241.802L187.384 84.84l17.795 10.262c.321.16.401.562.241.802-.08.24-.241.32-.481.32"/>
+    <path fill="url(#cC)" d="M186.262 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#cD)" d="M167.585 117.792c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.32.321-.481.321"/>
+    <path fill="url(#cE)" d="M148.909 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cF)" d="M130.232 139.439c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#cG)" d="M373.189 20.703c-.08 0-.24 0-.32-.08L353.31 9.317l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L355.635 9.318 373.43 19.58c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+    <path fill="url(#cH)" d="M354.433 31.526c-.081 0-.241 0-.321-.08L334.553 20.14l19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802L336.878 20.14l17.795 10.263c.321.16.401.56.24.801-.08.16-.24.321-.48.321" opacity=".3"/>
+    <path fill="url(#cI)" d="M335.756 42.27c-.08 0-.241 0-.321-.081l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+    <path fill="url(#cJ)" d="M317.079 53.092c-.08 0-.24 0-.32-.08L297.2 41.708l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.795 10.262L317.32 51.97c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".5"/>
+    <path fill="url(#cK)" d="M298.402 63.836c-.08 0-.24 0-.32-.08L278.523 52.45l19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802L280.928 52.45l17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.562.32" opacity=".6"/>
+    <path fill="url(#cL)" d="M279.726 74.659c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#cM)" d="M261.049 85.482c-.08 0-.24 0-.321-.08L241.09 74.098l19.558-11.305c.321-.16.642-.08.802.24.16.322.08.642-.241.803l-17.714 10.262L261.29 84.36c.32.16.4.561.24.802-.08.16-.321.32-.481.32" opacity=".8"/>
+    <path fill="url(#cN)" d="M242.292 96.225c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L224.738 84.84l17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+    <path fill="url(#cO)" d="M223.616 107.049c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321"/>
+    <path fill="url(#cP)" d="M204.939 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.241.321-.481.321"/>
+    <path fill="url(#cQ)" d="M186.262 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32"/>
+    <path fill="url(#cR)" d="M167.585 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.32-.481.32"/>
+    <path fill="url(#cS)" d="M148.909 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321"/>
+    <path fill="url(#cT)" d="M130.232 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32"/>
+    <path fill="url(#cU)" d="M373.189 42.27c-.08 0-.24 0-.32-.081L353.31 30.885l19.559-11.305c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.401.56.24.801-.08.241-.32.321-.481.321" opacity=".2"/>
+    <path fill="url(#cV)" d="M354.433 53.092c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.322.081.642-.24.803l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.24.32-.48.32" opacity=".3"/>
+    <path fill="url(#cW)" d="M335.756 63.836c-.08 0-.241 0-.321-.08L315.877 52.45l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802L318.281 52.45l17.796 10.262c.32.16.4.562.24.802s-.321.32-.561.32" opacity=".4"/>
+    <path fill="url(#cX)" d="M317.079 74.659c-.08 0-.24 0-.32-.08L297.2 63.275l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.56.24.801-.08.24-.24.321-.481.321" opacity=".5"/>
+    <path fill="url(#cY)" d="M298.402 85.483c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.401.32-.562.32" opacity=".6"/>
+    <path fill="url(#cZ)" d="M279.726 96.226c-.08 0-.241 0-.321-.08L259.847 84.84l19.558-11.304c.321-.16.641-.08.802.24.16.32.08.642-.241.802L262.251 84.84l17.795 10.262c.321.16.401.562.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+    <path fill="url(#da)" d="M261.049 107.049c-.08 0-.24 0-.321-.08L241.17 95.664l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+    <path fill="url(#db)" d="M242.292 117.792c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.263c.32.16.401.561.24.801 0 .241-.24.321-.481.321" opacity=".9"/>
+    <path fill="url(#dc)" d="M223.616 128.615c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.32-.561.32"/>
+    <path fill="url(#dd)" d="M204.939 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321"/>
+    <path fill="url(#de)" d="M186.262 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.24.321-.481.321"/>
+    <path fill="url(#df)" d="M167.585 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32"/>
+    <path fill="url(#dg)" d="M148.909 171.829c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.16-.321.321-.481.321"/>
+    <path fill="url(#dh)" d="M130.232 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321"/>
+    <g opacity=".9">
+      <path fill="url(#di)" d="M373.189 63.836c-.08 0-.24 0-.32-.08L353.23 52.45l19.559-11.304c.32-.16.641-.08.801.24s.08.642-.24.802L355.635 52.45l17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dj)" d="M354.433 74.659c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.56.24.801-.08.24-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dk)" d="M335.756 85.482c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.322.08.642-.241.803l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.16.16-.321.32-.561.32" opacity=".4"/>
+      <path fill="url(#dl)" d="M317.079 96.226c-.08 0-.24 0-.32-.08L297.2 84.84l19.559-11.304c.32-.16.641-.08.801.24s.08.641-.24.802L299.525 84.84l17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#dm)" d="M298.402 107.049c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dn)" d="M279.726 117.792c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.263 17.795 10.262c.321.16.401.561.241.801a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#do)" d="M261.049 128.615c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#dp)" d="M242.292 139.438c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dq)" d="M223.616 150.182c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802-.161.241-.321.321-.561.321" opacity=".9"/>
+      <path fill="url(#dr)" d="M204.939 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".9"/>
+      <path fill="url(#ds)" d="M186.262 171.828c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dt)" d="M167.586 182.572c-.081 0-.241 0-.321-.081l-19.559-11.304 19.559-11.304c.321-.161.641-.081.801.24s.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.321-.48.321" opacity=".9"/>
+      <path fill="url(#du)" d="M148.909 193.395c-.08 0-.241 0-.321-.08L129.03 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.161-.321.321-.481.321" opacity=".9"/>
+      <path fill="url(#dv)" d="M130.232 204.138c-.08 0-.24 0-.32-.08l-19.639-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <path fill="url(#dw)" d="M373.189 85.482c-.08 0-.24 0-.32-.08L353.23 74.098l19.559-11.305c.32-.16.641-.08.801.24.16.322.08.642-.24.803l-17.715 10.262L373.43 84.36c.32.16.401.561.24.802-.08.16-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dx)" d="M354.433 96.225c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.304c.321-.16.641-.08.801.24s.081.641-.24.802L336.878 84.84l17.795 10.262c.321.16.401.561.24.802-.08.24-.24.32-.48.32" opacity=".3"/>
+      <path fill="url(#dy)" d="M335.756 107.049c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.263c.321.16.401.561.241.801-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#dz)" d="M317.079 117.792c-.08 0-.24 0-.32-.08L297.2 106.408l19.559-11.305c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dA)" d="M298.402 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.081.641-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".6"/>
+      <path fill="url(#dB)" d="M279.726 139.439c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.16.16-.401.321-.561.321" opacity=".7"/>
+      <path fill="url(#dC)" d="M261.049 150.182c-.08 0-.24 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dD)" d="M242.292 161.005c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.161.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802 0 .24-.24.32-.481.32" opacity=".9"/>
+      <path fill="url(#dE)" d="M223.616 171.829c-.081 0-.241 0-.321-.081l-19.558-11.384 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.24-.321.401-.561.401" opacity=".8"/>
+      <path fill="url(#dF)" d="M204.939 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".8"/>
+      <path fill="url(#dG)" d="M186.262 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.24.321-.481.321" opacity=".8"/>
+      <path fill="url(#dH)" d="M167.586 204.138c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.241s.081.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".8"/>
+      <path fill="url(#dI)" d="M148.909 214.962c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dJ)" d="M130.232 225.785c-.08 0-.24 0-.32-.08L110.353 214.4l19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801L112.678 214.4l17.795 10.262c.32.161.4.562.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <path fill="url(#dK)" d="M373.189 107.049c-.08 0-.24 0-.32-.08L353.31 95.664l19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#dL)" d="M354.433 117.792c-.081 0-.241 0-.321-.08l-19.559-11.304 19.559-11.305c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.263 17.795 10.262c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#dM)" d="M335.756 128.615c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.24-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#dN)" d="M317.079 139.439c-.08 0-.24 0-.32-.08L297.2 128.054l19.559-11.304c.32-.16.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.16-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#dO)" d="M298.402 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#dP)" d="M279.726 161.005c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#dQ)" d="M261.049 171.829c-.08 0-.24 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.16-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#dR)" d="M242.292 182.572c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802 0 .241-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#dS)" d="M223.616 193.395c-.081 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802-.161.16-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dT)" d="M204.939 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.714 10.262 17.795 10.262c.32.16.4.561.24.802-.16.24-.321.32-.561.32" opacity=".7"/>
+      <path fill="url(#dU)" d="M186.262 214.962c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.562.24.802-.08.241-.24.321-.481.321" opacity=".7"/>
+      <path fill="url(#dV)" d="M167.585 225.785c-.08 0-.24 0-.32-.08L147.706 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801L150.031 214.4l17.795 10.262c.321.161.401.562.24.802-.08.16-.32.321-.481.321" opacity=".7"/>
+      <path fill="url(#dW)" d="M148.909 236.528c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241.16.32.08.641-.241.801l-17.795 10.263 17.795 10.262c.321.16.401.561.241.801-.08.241-.321.321-.481.321" opacity=".7"/>
+      <path fill="url(#dX)" d="M130.232 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.16-.321.321-.481.321" opacity=".7"/>
+    </g>
+    <g opacity=".6">
+      <path fill="url(#dY)" d="M373.189 128.615c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.401.561.24.802-.08.24-.32.32-.481.32" opacity=".2"/>
+      <path fill="url(#dZ)" d="M354.433 139.439c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.16-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#ea)" d="M335.756 150.182c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.161.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.241.321-.481.321" opacity=".4"/>
+      <path fill="url(#eb)" d="M317.079 161.005c-.08 0-.24 0-.32-.08L297.2 149.621l19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.32-.481.32" opacity=".5"/>
+      <path fill="url(#ec)" d="M298.402 171.829c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#ed)" d="M279.726 182.572c-.08 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.562.241.802a.7.7 0 0 1-.561.321" opacity=".7"/>
+      <path fill="url(#ee)" d="M261.049 193.395c-.08 0-.24 0-.321-.08L241.17 182.01l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.161-.321.321-.481.321" opacity=".8"/>
+      <path fill="url(#ef)" d="M242.292 204.138c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802l-17.715 10.262 17.795 10.262c.321.16.401.561.24.802-.08.24-.32.32-.561.32" opacity=".9"/>
+      <path fill="url(#eg)" d="M223.616 214.962c-.081 0-.241 0-.321-.081l-19.558-11.304 19.558-11.304c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.161.401.561.241.802-.161.24-.321.321-.561.321" opacity=".6"/>
+      <path fill="url(#eh)" d="M204.939 225.785c-.08 0-.241 0-.321-.08L185.06 214.4l19.558-11.304c.321-.16.642-.08.802.241.16.32.08.641-.241.801L187.384 214.4l17.795 10.262c.321.161.401.562.241.802-.08.16-.241.321-.481.321" opacity=".6"/>
+      <path fill="url(#ei)" d="M186.262 236.528c-.08 0-.24 0-.32-.08l-19.559-11.304 19.559-11.305c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.263 17.795 10.262c.32.16.4.561.24.801-.08.241-.24.321-.481.321" opacity=".6"/>
+      <path fill="url(#ej)" d="M148.909 258.095c-.08 0-.241 0-.321-.08L129.03 246.71l19.558-11.304c.321-.16.642-.08.802.24.16.321.08.642-.241.802l-17.795 10.262 17.795 10.262c.321.161.401.562.241.802-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#ek)" d="M130.232 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-17.795 10.262 17.795 10.263c.32.16.4.561.24.801-.08.241-.321.321-.481.321" opacity=".6"/>
+      <path fill="url(#el)" d="M167.585 247.352c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.16.401.561.24.802-.08.16-.32.321-.481.321" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <path fill="url(#em)" d="M373.189 150.182c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".2"/>
+      <path fill="url(#en)" d="M354.433 161.005c-.081 0-.241 0-.321-.08l-19.559-11.305 19.559-11.304c.321-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.241-.24.321-.48.321" opacity=".3"/>
+      <path fill="url(#eo)" d="M335.756 171.828c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ep)" d="M317.079 182.572c-.08 0-.24 0-.32-.081L297.2 171.187l19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.161.4.561.24.802-.08.24-.24.321-.481.321" opacity=".5"/>
+      <path fill="url(#eq)" d="M298.402 193.395c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-17.795 10.262 17.795 10.263c.321.16.401.561.24.801-.08.161-.32.321-.481.321" opacity=".6"/>
+      <path fill="url(#er)" d="M279.726 204.138c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-17.715 10.262 17.795 10.262c.321.16.401.561.241.802a.7.7 0 0 1-.561.32" opacity=".7"/>
+      <path fill="url(#es)" d="M261.049 214.961c-.08 0-.24 0-.321-.08l-19.558-11.304 19.558-11.304c.321-.161.642-.081.802.24s.08.641-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".8"/>
+      <path fill="url(#et)" d="M242.292 225.785c-.08 0-.24 0-.32-.08L222.413 214.4l19.559-11.304c.32-.16.641-.08.801.241.161.32.08.641-.24.801L224.738 214.4l17.795 10.262c.32.161.401.562.24.802 0 .16-.24.321-.481.321" opacity=".9"/>
+      <path fill="url(#eu)" d="M148.909 279.741c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ev)" d="M130.232 290.484c-.08 0-.24 0-.32-.08L110.353 279.1l19.559-11.305c.32-.16.641-.08.801.241s.08.641-.24.802L112.678 279.1l17.795 10.262c.32.16.4.561.24.802-.08.24-.321.32-.481.32" opacity=".4"/>
+      <path fill="url(#ew)" d="M167.585 268.918c-.08 0-.24 0-.32-.08l-19.559-11.305 19.559-11.304c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-17.795 10.262 17.795 10.262c.321.161.401.562.24.802-.08.241-.32.321-.481.321" opacity=".4"/>
+      <path fill="url(#ex)" d="M186.262 258.095c-.08 0-.24 0-.32-.081l-19.559-11.304 19.559-11.304c.32-.161.641-.081.801.24s.08.642-.24.802l-17.795 10.262 17.795 10.262c.32.16.4.561.24.802-.08.24-.24.321-.481.321" opacity=".4"/>
+      <path fill="url(#ey)" d="M204.939 247.351c-.08 0-.241 0-.321-.08l-19.558-11.304 19.558-11.305c.321-.16.642-.08.802.241s.08.641-.241.802l-17.795 10.262 17.795 10.262c.321.16.401.561.241.802-.08.16-.241.32-.481.32" opacity=".4"/>
+      <path fill="url(#ez)" d="M223.616 236.528c-.081 0-.241 0-.321-.08l-19.558-11.305 19.558-11.304c.321-.16.641-.08.802.24.16.321.08.642-.241.802l-17.715 10.262 17.795 10.263c.321.16.401.561.241.801-.161.241-.321.321-.561.321" opacity=".4"/>
+    </g>
+    <path fill="#BDBEC2" d="M1587.89 247.351c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l18.68-10.823c.32-.161.64-.081.8.24s.08.642-.24.802l-18.67 10.823c-.08 0-.16.08-.33.08m-18.67-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l37.35-21.567c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-37.35 21.567c-.08.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l56.03-32.389c.32-.161.64-.081.8.24s.08.641-.24.802l-56.03 32.39c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.081-.48-.321-.16-.321-.08-.642.24-.802l74.79-43.133c.32-.16.64-.08.8.241.16.32.08.641-.24.801l-74.78 43.133c-.16.081-.25.081-.33.081m-18.67-10.824c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l93.46-53.957c.32-.16.64-.08.8.241s.08.641-.24.802l-93.46 53.956c-.16.08-.24.08-.32.08m-18.68-10.743c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l112.14-64.78c.32-.161.64-.08.8.24.16.321.08.642-.24.802l-112.14 64.78c-.16 0-.24.08-.32.08m-18.76-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l130.82-75.523c.32-.16.64-.08.8.241s.08.641-.24.802l-130.81 75.522c-.08.081-.17.081-.33.081m-18.67-10.744c-.24 0-.4-.08-.48-.32-.16-.321-.08-.642.24-.802l149.49-86.346c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-149.49 86.346c-.08 0-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.32-.08-.641.24-.801l168.17-97.09c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-168.17 97.089c-.08.08-.24.08-.32.08m-18.68-10.823c-.24 0-.4-.08-.48-.321-.16-.321-.08-.641.24-.802l186.93-107.912c.32-.16.64-.08.8.24s.08.642-.24.802l-186.92 107.913c-.17.08-.25.08-.33.08" opacity=".8"/>
+    <path fill="url(#eA)" d="M111.475 301.308c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.22 64.779c.321.161.401.562.24.802-.16.241-.32.321-.561.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.801.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.081L-.985 193.235c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.161.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .241-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.985 150.102c-.321-.161-.401-.562-.241-.802.16-.321.561-.401.802-.241l112.14 64.78c.32.16.401.561.24.802 0 .24-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08l-112.14-64.78c-.321-.16-.401-.561-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.561.24.801 0 .161-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.081L-.905 106.969c-.321-.161-.401-.562-.24-.802.16-.321.56-.401.8-.241l112.141 64.78c.321.16.401.561.24.802-.08.16-.32.321-.561.321m0-21.647c-.08 0-.24 0-.32-.08L-.985 85.322c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 63.755c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .24-.24.32-.481.32m0-21.566c-.08 0-.24 0-.32-.08L-.985 42.189c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.779c.32.161.401.562.24.802 0 .241-.24.321-.481.321m0-21.567c-.08 0-.24 0-.32-.08L-.985 20.622c-.321-.16-.401-.56-.241-.801.16-.321.561-.401.802-.24l112.14 64.779c.32.16.401.561.24.802 0 .16-.24.32-.481.32m0-21.646c-.08 0-.24 0-.32-.08L-.985-1.025c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.14 64.78c.32.16.401.56.24.8 0 .241-.24.322-.481.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-22.591c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .24-.24.321-.481.321m0-21.566c-.08 0-.24 0-.32-.08L-.985-44.158c-.321-.16-.401-.562-.241-.802.16-.32.561-.401.802-.24l112.22 64.78c.321.16.401.56.24.8-.08.241-.32.322-.561.322m0-21.567c-.08 0-.24 0-.32-.08L-.985-65.724c-.321-.16-.401-.561-.241-.802.16-.32.561-.4.802-.24l112.14 64.78c.32.16.401.56.24.801 0 .16-.24.321-.481.321m18.757-10.823c-.08 0-.24 0-.32-.08L20.657-74.865c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24L130.473-12.81c.32.16.4.561.24.802-.08.24-.32.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08L58.01-74.784c-.32-.16-.4-.562-.24-.802.16-.32.561-.401.801-.24l90.578 52.272c.321.16.401.561.241.802-.08.16-.321.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-71.821-41.53c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.801-.24l71.821 41.529c.321.16.401.56.241.801-.081.24-.321.321-.481.321m18.676-10.823c-.08 0-.24 0-.32-.08l-53.145-30.707c-.32-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24L186.503-45.2c.32.16.401.562.24.802-.08.24-.24.32-.481.32m18.677-10.743c-.08 0-.241 0-.321-.08l-34.467-19.884c-.321-.16-.401-.56-.241-.801.16-.32.561-.401.802-.24l34.467 19.882c.321.16.401.561.241.802-.08.16-.241.32-.481.32m18.677-10.824c-.081 0-.241 0-.321-.08l-15.791-9.14c-.321-.16-.401-.56-.24-.801.16-.321.561-.401.801-.24l15.791 9.139c.321.16.401.561.241.802-.081.24-.241.32-.481.32"/>
+    <path fill="url(#eB)" d="M1606.57 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eC)" d="M1606.57 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eD)" d="M1587.9 9.88c-.09 0-.25 0-.33-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eE)" d="M1587.9 31.526c-.09 0-.25 0-.33-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eF)" d="M1587.9 53.092c-.09 0-.25 0-.33-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eG)" d="M1569.22 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eH)" d="M1569.22 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eI)" d="M1569.22 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eJ)" d="M1550.54 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#eK)" d="M1550.54 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eL)" d="M1550.54 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#eM)" d="M1550.54 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#eN)" d="M1531.86 20.703c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eO)" d="M1531.86 42.27c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.49.321"/>
+    <path fill="url(#eP)" d="M1531.86 63.836c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.33-.16.65-.08.81.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.49.32"/>
+    <path fill="url(#eQ)" d="M1513.19 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#eR)" d="M1513.19 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eS)" d="M1513.19 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#eT)" d="M1513.19 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.32.321-.48.321"/>
+    <path fill="url(#eU)" d="M1494.43 20.703c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eV)" d="M1494.43 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801 0 .24-.24.321-.48.321"/>
+    <path fill="url(#eW)" d="M1494.43 63.836c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .24-.24.32-.48.32"/>
+    <path fill="url(#eX)" d="M1475.75 9.88c-.08 0-.24 0-.32-.081l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 8.757c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#eY)" d="M1475.75 31.526c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.262 17.8 10.263c.32.16.4.56.24.801-.08.16-.24.32-.49.32"/>
+    <path fill="url(#eZ)" d="M1475.75 53.092c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262L1476 51.97c.32.16.4.561.24.802-.08.16-.24.32-.49.32"/>
+    <path fill="url(#fa)" d="M1475.75 74.659c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.49.321"/>
+    <path fill="url(#fb)" d="M1457.08 20.703c-.08 0-.24 0-.32-.08L1437.2 9.317l19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.88 10.262c.32.16.4.561.24.802-.16.24-.32.32-.56.32"/>
+    <path fill="url(#fc)" d="M1457.08 42.27c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fd)" d="M1457.08 63.836c-.08 0-.24 0-.32-.08L1437.2 52.45l19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fe)" d="M1438.4 9.88c-.08 0-.24 0-.32-.081l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#ff)" d="M1438.4 31.526c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.262 17.79 10.263c.32.16.4.56.24.801-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fg)" d="M1438.4 53.092c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fh)" d="M1438.4 74.659c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.56.24.801-.08.24-.24.321-.48.321"/>
+    <path fill="url(#fi)" d="M1457.08 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fj)" d="M1438.4 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fk)" d="M1494.43 85.482c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.322.08.642-.24.803l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802 0 .16-.24.32-.48.32"/>
+    <path fill="url(#fl)" d="M1457.08 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.8 10.262 17.8 10.262c.32.161.4.561.24.802-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fm)" d="M1438.4 117.792c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.24.16.321.08.642-.24.802l-17.79 10.263 17.79 10.262c.32.16.4.561.24.801-.08.241-.24.321-.48.321"/>
+    <path fill="url(#fn)" d="M1475.75 96.226c-.08 0-.24 0-.32-.08l-19.55-11.305 19.55-11.304c.32-.16.65-.08.81.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.49.32"/>
+    <path fill="url(#fo)" d="M1457.08 128.615c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.305c.32-.16.64-.08.8.241s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.24.32-.48.32"/>
+    <path fill="url(#fp)" d="M1438.4 139.438c-.08 0-.24 0-.32-.08l-19.56-11.304 19.56-11.304c.32-.161.64-.081.8.24s.08.641-.24.802l-17.79 10.262 17.79 10.262c.32.16.4.561.24.802-.08.16-.24.32-.48.32"/>
+    <path fill="url(#fq)" d="M1475.75 117.792c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.32-.16.65-.08.81.24.16.321.08.642-.24.802l-17.8 10.263 17.8 10.262c.32.16.4.561.24.801-.08.241-.24.321-.49.321"/>
+    <path fill="url(#fr)" d="M1494.43 107.049c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.642-.24.802l-17.79 10.262 17.79 10.262c.32.161.4.561.24.802 0 .241-.24.321-.48.321"/>
+    <path fill="url(#fs)" d="M1513.19 96.226c-.08 0-.24 0-.32-.08l-19.56-11.305 19.56-11.304c.32-.16.64-.08.8.24s.08.641-.24.802l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.24-.32.32-.48.32"/>
+    <path fill="url(#ft)" d="M1531.86 85.482c-.08 0-.24 0-.32-.08l-19.55-11.304 19.55-11.305c.33-.16.65-.08.81.24.16.322.08.642-.24.803l-17.8 10.262 17.8 10.262c.32.16.4.561.24.802-.08.16-.32.32-.49.32"/>
+    <path fill="url(#fu)" d="M1419.73 150.182c-.09 0-.25 0-.33-.08L1109.6-29.646c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.562.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-51.213c-.32-.16-.4-.56-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.801-.08.241-.32.321-.48.321m0-21.566c-.09 0-.25 0-.33-.08L1109.6-72.779c-.32-.16-.4-.562-.24-.802.16-.32.56-.4.8-.24l309.81 179.747c.32.161.4.561.24.802-.08.241-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08L1109.6-94.346c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1419.97 84.36c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.668c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.24-.48.24m0-21.567c-.09 0-.25 0-.33-.08L1109.6-137.56c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24l309.81 179.748c.32.16.4.56.24.801-.08.24-.32.321-.48.321m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241L1420.05 19.58c.32.16.4.561.24.802-.16.24-.4.32-.56.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.401.8-.24L1419.97-1.987c.32.16.4.562.24.802-.08.16-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08L1109.6-202.26c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.16-.32.32-.48.32m0-21.646c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.561-.24-.802.16-.321.56-.401.8-.24L1419.97-45.2c.32.16.4.562.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.566c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.16.4.561.24.802-.08.24-.32.32-.48.32m0-21.567c-.09 0-.25 0-.33-.08l-309.8-179.748c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.321-.48.321m0-21.647c-.09 0-.25 0-.33-.08l-309.8-179.667c-.32-.161-.4-.562-.24-.802.16-.321.56-.401.8-.241l309.81 179.748c.32.161.4.561.24.802-.08.16-.32.24-.48.24m0-21.566c-.09 0-.25 0-.33-.08L1109.6-331.74c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.8-.24l309.81 179.748c.32.16.4.561.24.801-.08.161-.32.241-.48.241m18.67-10.743c-.08 0-.24 0-.32-.08L1131.16-340.88c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l306.92 178.064c.32.161.4.562.24.802-.08.16-.24.321-.48.321m18.68-10.824c-.08 0-.24 0-.32-.08l-90.58-52.273c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l90.58 52.273c.32.16.4.561.24.802-.08.24-.24.32-.48.32m18.68-10.823c-.09 0-.25 0-.33-.08l-71.82-41.53c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l71.83 41.53c.32.16.4.561.24.801-.08.241-.24.321-.48.321m18.67-10.743c-.08 0-.24 0-.32-.08l-53.14-30.707c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l53.14 30.706c.32.161.4.562.24.802 0 .161-.24.321-.48.321m18.76-10.824c-.08 0-.24 0-.32-.08l-34.47-19.883c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l34.47 19.883c.32.16.4.561.24.802-.08.24-.32.32-.48.32m18.68-10.743c-.08 0-.25 0-.33-.08l-15.79-9.14c-.32-.16-.4-.561-.24-.801.16-.321.56-.401.8-.241l15.8 9.14c.32.16.4.561.24.802-.08.16-.32.32-.48.32"/>
+    <path fill="url(#fv)" d="M1606.57 538.7c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08L1419.4 387.574c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.913c.32.16.4.561.24.801-.08.161-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08L1419.4 365.927c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802-.08.24-.32.4-.56.4m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.561-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802.16-.32.56-.4.81-.24l186.92 107.913c.32.16.4.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.08 0-.24 0-.32-.081l-186.93-107.912c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l186.92 107.912c.32.161.4.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.802a.58.58 0 0 1 .81-.24l187 107.912c.32.161.4.562.24.802-.08.241-.32.321-.56.321m0-21.567c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.16-.4-.561-.24-.801a.58.58 0 0 1 .81-.241l186.92 107.913c.32.16.4.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.08 0-.24 0-.32-.08l-186.93-107.913c-.32-.161-.4-.562-.24-.802a.58.58 0 0 1 .81-.241l186.92 107.913c.32.161.4.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+    <path fill="#BDBEC2" fill-opacity=".8" d="M92.799 592.656c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.823c.32-.161.641-.081.801.24s.081.641-.24.802l-18.677 10.823c-.08.08-.16.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.24-.801l37.354-21.567c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-37.353 21.567c-.08 0-.24.08-.321.08M55.445 571.09c-.24 0-.4-.08-.56-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.641-.08.801.241s.08.641-.24.802l-56.03 32.39c0 .08-.16.08-.24.08M36.77 560.266c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.24.16.321.08.642-.241.802L37.09 560.186c-.16.08-.24.08-.32.08m-18.677-10.743c-.24 0-.4-.08-.561-.32-.16-.321-.08-.642.24-.802l93.464-53.957c.32-.16.641-.08.801.241s.081.641-.24.802l-93.464 53.956c-.08.08-.16.08-.24.08M-.585 538.7c-.24 0-.4-.08-.48-.321-.161-.321-.08-.641.24-.802l112.14-64.779c.321-.161.641-.08.802.24.16.321.08.642-.241.802L-.264 538.62c-.16.08-.24.08-.32.08m-.08-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.779c.32-.161.641-.081.801.24s.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241.161.32.081.641-.24.801L-.344 473.92c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.641.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 452.273c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 409.14c-.08.081-.16.081-.32.081m0-21.567c-.24 0-.4-.08-.48-.321-.161-.32-.081-.641.24-.801l112.14-64.78c.32-.16.641-.08.801.24.161.321.081.642-.24.802l-112.14 64.78c-.08 0-.16.08-.32.08m0-21.566c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l112.14-64.78c.32-.16.641-.08.801.241s.081.641-.24.802L-.344 365.927c-.08.08-.16.161-.32.161m0-21.647c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l93.463-53.956c.32-.16.641-.08.802.241.16.32.08.641-.24.801L-.345 344.361c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l74.787-43.133c.32-.161.64-.08.801.24.16.321.08.642-.24.802L-.344 322.794c-.08.08-.16.08-.32.08m0-21.566c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.39c.32-.16.64-.08.801.241.16.321.08.641-.24.802l-56.03 32.39c-.08.08-.16.08-.32.08m0-21.567c-.24 0-.4-.08-.48-.32-.161-.321-.081-.642.24-.802l37.353-21.567c.32-.16.641-.08.801.241s.08.641-.24.802L-.344 279.661c-.08 0-.16.08-.32.08m0-21.646c-.24 0-.4-.081-.48-.321-.161-.321-.081-.642.24-.802l18.676-10.823c.32-.161.642-.08.802.24.16.321.08.642-.24.802L-.345 258.014c-.08.081-.16.081-.32.081" opacity=".8"/>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="1368.02" x2="1377.97" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="1386.78" x2="1396.73" y1="174.458" y2="157.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="1405.46" x2="1415.41" y1="185.201" y2="167.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="1405.46" x2="1415.41" y1="163.634" y2="146.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="1293.32" x2="1303.27" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="1311.99" x2="1321.94" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="1330.67" x2="1340.62" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="1330.67" x2="1340.62" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="1349.35" x2="1359.3" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="1368.02" x2="1377.97" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="1349.35" x2="1359.3" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="1368.02" x2="1377.97" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="1386.78" x2="1396.73" y1="217.591" y2="200.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="1405.46" x2="1415.41" y1="228.414" y2="211.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="1386.78" x2="1396.73" y1="196.024" y2="178.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="1405.46" x2="1415.41" y1="206.768" y2="189.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="1237.21" x2="1247.15" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="1255.96" x2="1265.91" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="1255.96" x2="1265.91" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="1274.64" x2="1284.59" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="1293.32" x2="1303.27" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="1274.64" x2="1284.59" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="1293.32" x2="1303.26" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="1311.99" x2="1321.94" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="1330.67" x2="1340.62" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="1311.99" x2="1321.94" y1="239.157" y2="221.929" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="1330.67" x2="1340.62" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="1349.35" x2="1359.3" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="1368.02" x2="1377.97" y1="271.547" y2="254.319" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="1349.35" x2="1359.3" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="1368.02" x2="1377.97" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="1386.78" x2="1396.73" y1="260.724" y2="243.496" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="1405.46" x2="1415.41" y1="271.547" y2="254.32" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="1386.78" x2="1396.73" y1="239.157" y2="221.93" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="1405.46" x2="1415.41" y1="249.981" y2="232.753" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="1237.21" x2="1247.15" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="1255.96" x2="1265.91" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="1237.21" x2="1247.15" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="1255.96" x2="1265.91" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="1274.64" x2="1284.59" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="1293.32" x2="1303.26" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="1274.64" x2="1284.59" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="1293.32" x2="1303.27" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="1311.99" x2="1321.94" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="1330.67" x2="1340.62" y1="314.68" y2="297.452" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="1311.99" x2="1321.94" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="1330.67" x2="1340.62" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="1349.35" x2="1359.3" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="1368.02" x2="1377.87" y1="314.663" y2="297.493" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="1349.35" x2="1359.3" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="1368.02" x2="1377.97" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="1386.78" x2="1396.73" y1="303.937" y2="286.709" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="1405.46" x2="1415.41" y1="314.68" y2="297.453" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="1386.78" x2="1396.73" y1="282.371" y2="265.143" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="1405.46" x2="1415.41" y1="293.114" y2="275.886" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="1237.21" x2="1247.15" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="1255.96" x2="1265.91" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="1237.21" x2="1247.15" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="1255.96" x2="1265.91" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="1274.64" x2="1284.59" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="1293.32" x2="1303.27" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="1274.64" x2="1284.59" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="al" x1="1293.32" x2="1303.26" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="am" x1="1311.99" x2="1321.94" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="an" x1="1330.67" x2="1340.62" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="1311.99" x2="1321.94" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="1330.67" x2="1340.62" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="1349.35" x2="1359.3" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="1368.02" x2="1377.97" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="as" x1="1349.35" x2="1359.3" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="at" x1="1368.02" x2="1377.97" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="au" x1="1386.78" x2="1396.73" y1="347.07" y2="329.842" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="av" x1="1405.46" x2="1415.41" y1="357.893" y2="340.666" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="1386.78" x2="1396.73" y1="325.504" y2="308.276" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="1405.46" x2="1415.41" y1="336.327" y2="319.099" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="1237.21" x2="1247.15" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="az" x1="1255.96" x2="1265.91" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="1237.21" x2="1247.15" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="1255.96" x2="1265.91" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="1274.64" x2="1284.59" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="1293.32" x2="1303.26" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="1274.64" x2="1284.59" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="1293.32" x2="1303.27" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="1311.99" x2="1321.94" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="1330.67" x2="1340.62" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="1311.99" x2="1321.94" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="1330.67" x2="1340.62" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="1349.35" x2="1359.3" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="1368.02" x2="1377.97" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="1349.35" x2="1359.3" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="1368.02" x2="1377.97" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="1386.78" x2="1396.73" y1="390.283" y2="373.055" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="1405.46" x2="1415.41" y1="401.026" y2="383.799" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="1386.78" x2="1396.73" y1="368.717" y2="351.489" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="1405.46" x2="1415.41" y1="379.46" y2="362.232" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="1237.21" x2="1247.15" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="1255.96" x2="1265.91" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="1237.21" x2="1247.15" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="1255.96" x2="1265.91" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="1274.64" x2="1284.59" y1="433.416" y2="416.188" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="1293.32" x2="1303.27" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="1274.64" x2="1284.59" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="1293.32" x2="1303.27" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="1311.99" x2="1321.94" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="1330.67" x2="1340.62" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="1311.99" x2="1321.94" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="1330.67" x2="1340.62" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="be" x1="1349.35" x2="1359.3" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="1368.02" x2="1377.97" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="1349.35" x2="1359.3" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="1368.02" x2="1377.97" y1="422.673" y2="405.445" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="1386.78" x2="1396.73" y1="433.416" y2="416.189" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="1405.46" x2="1415.41" y1="444.24" y2="427.012" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="1386.78" x2="1396.73" y1="411.85" y2="394.622" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="1405.46" x2="1415.41" y1="422.673" y2="405.446" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="1237.21" x2="1247.15" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="1255.96" x2="1265.91" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="1237.21" x2="1247.15" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="1255.96" x2="1265.91" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="1274.64" x2="1284.59" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="br" x1="1293.32" x2="1303.26" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="1274.64" x2="1284.59" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="1293.32" x2="1303.26" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="1311.99" x2="1321.94" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="1330.67" x2="1340.62" y1="487.373" y2="470.145" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="1311.97" x2="1321.84" y1="454.965" y2="437.83" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="1330.67" x2="1340.62" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="by" x1="1349.35" x2="1359.3" y1="476.63" y2="459.402" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="1349.35" x2="1359.3" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="1368.02" x2="1377.97" y1="465.806" y2="448.578" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="1386.78" x2="1396.73" y1="454.983" y2="437.755" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="1237.21" x2="1247.15" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="1237.21" x2="1247.15" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="1255.96" x2="1265.91" y1="508.939" y2="491.712" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="1274.64" x2="1284.59" y1="519.763" y2="502.535" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="1274.64" x2="1284.59" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="1293.32" x2="1303.27" y1="508.939" y2="491.711" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="1311.99" x2="1321.94" y1="498.196" y2="480.968" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="110.366" x2="130.858" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="147.719" x2="168.212" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bL" x1="129.043" x2="149.535" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bM" x1="110.366" x2="130.858" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bN" x1="185.073" x2="205.565" y1="-1.541" y2="-1.541" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bO" x1="166.396" x2="186.888" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bP" x1="147.719" x2="168.212" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bQ" x1="129.043" x2="149.535" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bR" x1="110.366" x2="130.858" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bS" x1="222.426" x2="242.918" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bT" x1="203.749" x2="224.322" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bU" x1="185.073" x2="205.565" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bV" x1="166.396" x2="186.888" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bW" x1="147.719" x2="168.212" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bX" x1="129.043" x2="149.615" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bY" x1="110.366" x2="130.858" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="bZ" x1="259.859" x2="280.432" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ca" x1="241.183" x2="261.675" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cb" x1="222.426" x2="242.918" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cc" x1="203.749" x2="224.322" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cd" x1="185.073" x2="205.565" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ce" x1="166.396" x2="186.969" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cf" x1="147.719" x2="168.212" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cg" x1="129.043" x2="149.615" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ch" x1="110.366" x2="130.858" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ci" x1="297.213" x2="317.705" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cj" x1="278.536" x2="299.029" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ck" x1="259.859" x2="280.432" y1="20.066" y2="20.066" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cl" x1="241.183" x2="261.675" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cm" x1="222.426" x2="242.918" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cn" x1="203.749" x2="224.322" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="co" x1="185.073" x2="205.565" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cp" x1="166.396" x2="186.969" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cq" x1="147.719" x2="168.212" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cr" x1="129.043" x2="149.535" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cs" x1="110.366" x2="130.858" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ct" x1="334.566" x2="355.059" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cu" x1="315.889" x2="336.382" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cv" x1="297.213" x2="317.705" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cw" x1="278.536" x2="299.029" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cx" x1="259.859" x2="280.432" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cy" x1="241.103" x2="261.675" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cz" x1="222.426" x2="242.918" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cA" x1="203.749" x2="224.322" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cB" x1="185.073" x2="205.565" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cC" x1="166.396" x2="186.888" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cD" x1="147.719" x2="168.212" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cE" x1="129.043" x2="149.535" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cF" x1="110.366" x2="130.858" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cG" x1="353.323" x2="373.815" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cH" x1="334.566" x2="355.059" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cI" x1="315.889" x2="336.382" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cJ" x1="297.213" x2="317.705" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cK" x1="278.536" x2="299.109" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cL" x1="259.859" x2="280.432" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cM" x1="241.103" x2="261.675" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cN" x1="222.426" x2="242.918" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cO" x1="203.749" x2="224.322" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cP" x1="185.073" x2="205.565" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cQ" x1="166.396" x2="186.888" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cR" x1="147.719" x2="168.212" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cS" x1="129.043" x2="149.535" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cT" x1="110.366" x2="130.858" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cU" x1="353.323" x2="373.815" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cV" x1="334.566" x2="355.059" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cW" x1="315.889" x2="336.463" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cX" x1="297.213" x2="317.705" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cY" x1="278.536" x2="299.109" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="cZ" x1="259.859" x2="280.432" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="da" x1="241.183" x2="261.675" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="db" x1="222.426" x2="242.918" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dc" x1="203.749" x2="224.322" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dd" x1="185.073" x2="205.565" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="de" x1="166.396" x2="186.888" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="df" x1="147.719" x2="168.212" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dg" x1="129.043" x2="149.535" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dh" x1="110.366" x2="130.858" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="di" x1="353.243" x2="373.816" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dj" x1="334.566" x2="355.059" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dk" x1="315.889" x2="336.462" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dl" x1="297.213" x2="317.705" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dm" x1="278.536" x2="299.029" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dn" x1="259.859" x2="280.432" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="do" x1="241.183" x2="261.675" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dp" x1="222.426" x2="242.918" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dq" x1="203.749" x2="224.322" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dr" x1="185.073" x2="205.565" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ds" x1="166.396" x2="186.888" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dt" x1="147.719" x2="168.212" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="du" x1="129.042" x2="149.535" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dv" x1="110.286" x2="130.859" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dw" x1="353.243" x2="373.816" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dx" x1="334.566" x2="355.059" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dy" x1="315.889" x2="336.382" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dz" x1="297.213" x2="317.705" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dA" x1="278.536" x2="299.029" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dB" x1="259.859" x2="280.432" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dC" x1="241.183" x2="261.675" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dD" x1="222.426" x2="242.918" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dE" x1="203.749" x2="224.322" y1="160.369" y2="160.369" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dF" x1="185.073" x2="205.565" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dG" x1="166.396" x2="186.888" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dH" x1="147.719" x2="168.292" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dI" x1="129.043" x2="149.535" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dJ" x1="110.366" x2="130.858" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dK" x1="353.323" x2="373.815" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dL" x1="334.566" x2="355.059" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dM" x1="315.889" x2="336.382" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dN" x1="297.213" x2="317.705" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dO" x1="278.536" x2="299.029" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dP" x1="259.859" x2="280.432" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dQ" x1="241.183" x2="261.675" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dR" x1="222.426" x2="242.918" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dS" x1="203.749" x2="224.322" y1="181.976" y2="181.976" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dT" x1="185.073" x2="205.646" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dU" x1="166.396" x2="186.888" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dV" x1="147.719" x2="168.212" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dW" x1="129.043" x2="149.535" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dX" x1="110.366" x2="130.858" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dY" x1="353.323" x2="373.815" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="dZ" x1="334.566" x2="355.059" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ea" x1="315.889" x2="336.382" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eb" x1="297.213" x2="317.705" y1="149.586" y2="149.586" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ec" x1="278.536" x2="299.029" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ed" x1="259.859" x2="280.432" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ee" x1="241.183" x2="261.675" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ef" x1="222.426" x2="242.999" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eg" x1="203.749" x2="224.322" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eh" x1="185.073" x2="205.565" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ei" x1="166.396" x2="186.888" y1="225.109" y2="225.109" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ej" x1="129.043" x2="149.535" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ek" x1="110.366" x2="130.858" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="el" x1="147.719" x2="168.212" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="em" x1="353.323" x2="373.815" y1="138.762" y2="138.762" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="en" x1="334.566" x2="355.059" y1="149.585" y2="149.585" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eo" x1="315.889" x2="336.382" y1="160.409" y2="160.409" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ep" x1="297.213" x2="317.705" y1="171.152" y2="171.152" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eq" x1="278.536" x2="299.029" y1="181.975" y2="181.975" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="er" x1="259.859" x2="280.432" y1="192.719" y2="192.719" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="es" x1="241.183" x2="261.675" y1="203.542" y2="203.542" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="et" x1="222.426" x2="242.918" y1="214.365" y2="214.365" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eu" x1="129.043" x2="149.535" y1="268.322" y2="268.322" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ev" x1="110.366" x2="130.858" y1="279.065" y2="279.065" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ew" x1="147.719" x2="168.212" y1="257.498" y2="257.498" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ex" x1="166.396" x2="186.888" y1="246.675" y2="246.675" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ey" x1="185.073" x2="205.565" y1="235.932" y2="235.932" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="ez" x1="203.749" x2="224.322" y1="225.108" y2="225.108" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+    <linearGradient id="eA" x1="-1.227" x2="224.241" y1="112.671" y2="112.671" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".25"/>
+      <stop offset=".777" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="eB" x1="1586.71" x2="1607.2" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eC" x1="1586.71" x2="1607.2" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eD" x1="1568.03" x2="1588.52" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eE" x1="1568.03" x2="1588.52" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eF" x1="1568.03" x2="1588.52" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eG" x1="1549.35" x2="1569.84" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eH" x1="1549.35" x2="1569.84" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eI" x1="1549.35" x2="1569.84" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eJ" x1="1530.68" x2="1551.17" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eK" x1="1530.68" x2="1551.17" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eL" x1="1530.68" x2="1551.17" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eM" x1="1530.68" x2="1551.17" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eN" x1="1512" x2="1532.49" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eO" x1="1512" x2="1532.49" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eP" x1="1512" x2="1532.49" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eQ" x1="1493.32" x2="1513.81" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eR" x1="1493.32" x2="1513.81" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eS" x1="1493.32" x2="1513.81" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eT" x1="1493.32" x2="1513.81" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eU" x1="1474.57" x2="1495.06" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eV" x1="1474.57" x2="1495.06" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eW" x1="1474.57" x2="1495.06" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eX" x1="1455.89" x2="1476.38" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eY" x1="1455.89" x2="1476.38" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="eZ" x1="1455.89" x2="1476.38" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fa" x1="1455.89" x2="1476.38" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fb" x1="1437.21" x2="1457.78" y1="9.283" y2="9.283" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fc" x1="1437.21" x2="1457.7" y1="30.849" y2="30.849" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fd" x1="1437.21" x2="1457.7" y1="52.416" y2="52.416" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fe" x1="1418.54" x2="1439.03" y1="-1.54" y2="-1.54" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ff" x1="1418.54" x2="1439.03" y1="20.106" y2="20.106" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fg" x1="1418.54" x2="1439.03" y1="41.673" y2="41.673" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fh" x1="1418.54" x2="1439.03" y1="63.239" y2="63.239" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fi" x1="1437.21" x2="1457.7" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fj" x1="1418.54" x2="1439.03" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fk" x1="1474.57" x2="1495.06" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fl" x1="1437.21" x2="1457.7" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fm" x1="1418.54" x2="1439.03" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fn" x1="1455.89" x2="1476.38" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fo" x1="1437.21" x2="1457.7" y1="117.196" y2="117.196" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fp" x1="1418.54" x2="1439.03" y1="128.019" y2="128.019" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fq" x1="1455.89" x2="1476.38" y1="106.372" y2="106.372" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fr" x1="1474.57" x2="1495.06" y1="95.629" y2="95.629" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fs" x1="1493.32" x2="1513.81" y1="84.806" y2="84.806" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="ft" x1="1512" x2="1532.49" y1="74.063" y2="74.063" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".9"/>
+    </linearGradient>
+    <linearGradient id="fu" x1="1109.3" x2="1532.45" y1="-95.896" y2="-95.896" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="fv" x1="1513.16" x2="1513.16" y1="538.721" y2="149.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.0.x/img/nomad-panel-learn.svg b/content/nomad/v1.0.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..090a5b337a
--- /dev/null
+++ b/content/nomad/v1.0.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="#BDBEC2" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".886" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.0.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.0.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.0.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.0.x/img/og-image.png b/content/nomad/v1.0.x/img/og-image.png
new file mode 100644
index 0000000000..7faccf445c
Binary files /dev/null and b/content/nomad/v1.0.x/img/og-image.png differ
diff --git a/content/nomad/v1.0.x/img/pattern.svg b/content/nomad/v1.0.x/img/pattern.svg
new file mode 100644
index 0000000000..ce1eefa887
--- /dev/null
+++ b/content/nomad/v1.0.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="#00BC7F" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="#BDBEC2" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#BDBEC2" stop-opacity=".5"/>
+      <stop offset="1" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset=".825" stop-color="#BDBEC2"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity="0"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#BDBEC2" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#BDBEC2" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.0.x/redirects.jsonc b/content/nomad/v1.0.x/redirects.jsonc
new file mode 100644
index 0000000000..f7986a7065
--- /dev/null
+++ b/content/nomad/v1.0.x/redirects.jsonc
@@ -0,0 +1,1249 @@
+[
+  // Define your custom redirects within this file.
+  // Vercel"s redirect documentation: https://vercel.com/docs/configuration#project/redirects
+  // Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+
+  {
+    "source": "/docs/operations/overview",
+    "destination": "/docs/operations",
+    "permanent": true,
+  },
+
+  // This redirect supports a URL built into the Nomad UI, and should always be
+  // directed someplace valid to support the text "Read about Outage Recovery."
+  {
+    "source": "/guides/outage.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  // Nomad Learn Redirects
+  {
+    "source": "/intro/getting-started",
+    "destination": "https://learn.hashicorp.com/collections/nomad/get-started",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/install",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-install",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/running",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-run",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/ui",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/next-steps",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/vs/kubernetes",
+    "destination": "/docs/nomad-vs-kubernetes",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/who-uses-nomad",
+    "destination": "/docs/who-uses/noamd",
+    "permanent": true,
+  },
+  // Guides
+  {
+    "source": "/guides/load-balancing",
+    "destination": "https://learn.hashicorp.com/collections/nomad/load-balancing",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/fabio",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/nginx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/haproxy",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/traefik",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/stateful-workloads",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/host-volumes",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/portworx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/web-ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/access.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/accessing",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/submitting-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/operating-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/inspecting-the-cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/securing",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/governance-and-policy",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  // /s/* redirects for useful links that need a stable URL but we may need to
+  // change its destination in the future.
+  {
+    "source": "/s/port-plan-failure",
+    "destination": "https://github.com/hashicorp/nomad/issues/9506",
+    "permanent": false,
+  },
+
+  // Spark guide links are all repointed to deprecated nomad-spark repo
+  {
+    "source": "/guides/spark",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/spark/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  // These are subsumed in the splat over analytical-workloads, but I"m keeping them here in case
+  // we want to reclaim the slug "analytical-workloads" at some point and deal with some bad links.
+  // {
+  //   "source": "/guides/analytical-workloads/spark/spark",
+  //   "destination": "https://github.com/hashicorp/nomad-spark",
+  //   "permanent": true,
+  // },
+
+  {
+    "source": "/guides/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspec",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/affinity",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/affinity",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/advanced-scheduling/preemption-service-batch",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/spread",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/spread",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/update-strategies",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/manage-clusters",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/monitoring",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/prometheus-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/vault-pki-integration",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad",
+    "permanent": true,
+  },
+
+  // Multi-part UI guides
+  {
+    "source": "/guides/ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+
+  // Website
+  // Docs
+  {
+    "source": "/docs/index",
+    "destination": "/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api-docs/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/config",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/taskconfig",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/inspecting",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/resources",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/updating",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/servicediscovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/interpreted",
+    "destination": "/docs/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/json",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/environment",
+    "destination": "/docs/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/servicediscovery",
+    "destination": "/docs/job-specification/service",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/networking",
+    "destination": "/docs/job-specification/network",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/job-specification/index",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/requirements",
+    "destination": "/docs/install/production/requirements/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-index",
+    "destination": "/docs/commands/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-list-peers",
+    "destination": "/docs/commands/operator/raft-list-peers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-remove-peer",
+    "destination": "/docs/commands/operator/raft-remove-peer",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/job-dispatch",
+    "destination": "/docs/commands/job/dispatch",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/alloc-status",
+    "destination": "/docs/commands/alloc/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/fs",
+    "destination": "/docs/commands/alloc/fs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/logs",
+    "destination": "/docs/commands/alloc/logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/init",
+    "destination": "/docs/commands/job/init",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/inspect",
+    "destination": "/docs/commands/job/inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/run",
+    "destination": "/docs/commands/job/run",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/stop",
+    "destination": "/docs/commands/job/stop",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/plan",
+    "destination": "/docs/commands/job/plan",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/validate",
+    "destination": "/docs/commands/job/validate",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/client-config",
+    "destination": "/docs/commands/node/config",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-drain",
+    "destination": "/docs/commands/node/drain",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-status",
+    "destination": "/docs/commands/node/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keygen",
+    "destination": "/docs/commands/operator/keygen",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keyring",
+    "destination": "/docs/commands/operator/keyring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-force-leave",
+    "destination": "/docs/commands/server/force-leave",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-join",
+    "destination": "/docs/commands/server/join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-members",
+    "destination": "/docs/commands/server/members",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/runtime/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/internals/scheduling",
+    "destination": "/docs/internals/scheduling/scheduling",
+    "permanent": true,
+  },
+
+  // Sometimes code names are too good not to mention
+  {
+    "source": "/heartyeet",
+    "destination": "/docs/job-specification/group#stop_after_client_disconnect",
+    "permanent": true,
+  },
+
+  // Moved /docs/drivers/external/podman -> /docs/drivers/podman
+  {
+    "source": "/docs/drivers/external/podman",
+    "destination": "/docs/drivers/podman",
+    "permanent": true,
+  },
+
+  // Moved /docs/operating-a-job/ -> /guides/operating-a-job/
+  {
+    "source": "/docs/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/update-strategies",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  // Moved /docs/agent/configuration/ -> /docs/configuration/ 301!
+  {
+    "source": "/docs/agent/configuration",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/acl",
+    "destination": "/docs/configuration/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/autopilot",
+    "destination": "/docs/configuration/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/client",
+    "destination": "/docs/configuration/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/consul",
+    "destination": "/docs/configuration/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/sentinel",
+    "destination": "/docs/configuration/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server",
+    "destination": "/docs/configuration/server",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server_join",
+    "destination": "/docs/configuration/server_join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/telemetry",
+    "destination": "/docs/configuration/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/tls",
+    "destination": "/docs/configuration/tls",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/vault",
+    "destination": "/docs/configuration/vault",
+    "permanent": true,
+  },
+  // Moved telemetry under operations
+  {
+    "source": "/docs/telemetry",
+    "destination": "/docs/operations/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/telemetry/metrics",
+    "destination": "/docs/operations/metrics",
+    "permanent": true,
+  },
+
+  // Moved installing agent under operations as ope
+  {
+    "source": "/docs/install/production/nomad-agent",
+    "destination": "/docs/operations/nomad-agent",
+    "permanent": true,
+  },
+
+  // Moved guide-like docs to /guides
+  {
+    "source": "/docs/agent",
+    "destination": "/docs/install/production/nomad-agent/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/telemetry",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/service-discovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+
+  // Redirect old LXC driver doc to new one in /docs/external
+  {
+    "source": "/docs/drivers/lxc",
+    "destination": "/docs/drivers/external/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/rkt",
+    "destination": "/docs/drivers/external/rkt",
+    "permanent": true,
+  },
+
+  // API
+  {
+    "source": "/docs/http/agent-force-leave",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-join",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-members",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-self",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-servers",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/alloc",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/allocs",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-allocation-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-fs",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/eval",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/evals",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/job",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/jobs",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/json-jobs",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/node",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/nodes",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/operator",
+    "destination": "/api-docs/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/regions",
+    "destination": "/api-docs/regions",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/status",
+    "destination": "/api-docs/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/system",
+    "destination": "/api-docs/system",
+    "permanent": true,
+  },
+
+  // Guides
+
+  // Reorganized Guides by Persona
+  {
+    "source": "/guides/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/install/index",
+    "destination": "/docs/install",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/agent/index",
+    "destination": "/docs/install/production/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/consul-integration/index",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/vault-integration/index",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+
+  // Enterprise
+
+  // Reorganized Enterprise into single pager
+  {
+    "source": "/docs/enterprise/namespaces",
+    "destination": "/docs/enterprise#namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/quotas",
+    "destination": "/docs/enterprise#resource-quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/preemption",
+    "destination": "/docs/enterprise#preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/sentinel",
+    "destination": "/docs/enterprise#sentinel-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/autopilot",
+    "destination": "/docs/enterprise#nomad-enterprise-platform",
+    "permanent": true,
+  },
+
+  // Guide Catch-all Redirects
+  {
+    "source": "/guides/:splat*",
+    "destination": "https://learn.hashicorp.com/nomad",
+    "permanent": true,
+  },
+
+  // Vault Integration
+  {
+    "source": "/docs/vault-integration",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  // Old resources -> Community
+  {
+    "source": "/resources",
+    "destination": "/community",
+    "permanent": true,
+  },
+  // `/<path>/index.html` to /<path>
+  {
+    "source": "/:splat*/index.html",
+    "destination": "/:splat*",
+    "permanent": true,
+  },
+  // `.html` to non-`.html`
+  {
+    "source": "/:splat(.*).html",
+    "destination": "/:splat",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.1.x/content/api-docs/acl-policies.mdx b/content/nomad/v1.1.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..f51e7aeec5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,167 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/acl-tokens.mdx b/content/nomad/v1.1.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..acdf03f7a7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,430 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](https://learn.hashicorp.com/tutorials/nomad/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/agent.mdx b/content/nomad/v1.1.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..e62a451054
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/agent.mdx
@@ -0,0 +1,727 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "protocol_version_max": "3",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "protocol_version": "1",
+      "protocol_version_min": "0",
+      "snapshot_version_min": "0",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/allocations.mdx b/content/nomad/v1.1.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..8f2e296ff9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/allocations.mdx
@@ -0,0 +1,807 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": "5000000000"
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2017-07-25T23:36:26.106431265Z",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400,
+    "ModifyTime": 1495747371794276400
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:3.2"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:3.2"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Task": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Task": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/api/index.html#blocking-queries) and
+[required ACLs](/api/index.html#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/client.mdx b/content/nomad/v1.1.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..1841fbc325
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/client.mdx
@@ -0,0 +1,670 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/deployments.mdx b/content/nomad/v1.1.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..c9db087636
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/deployments.mdx
@@ -0,0 +1,538 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/evaluations.mdx b/content/nomad/v1.1.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..4f5ece72a6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,266 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Priority": 50,
+  "Type": "service",
+  "TriggeredBy": "job-register",
+  "JobID": "example",
+  "JobModifyIndex": 52,
+  "NodeID": "",
+  "NodeModifyIndex": 0,
+  "Status": "complete",
+  "StatusDescription": "",
+  "Wait": 0,
+  "NextEval": "",
+  "PreviousEval": "",
+  "BlockedEval": "",
+  "FailedTGAllocs": null,
+  "ClassEligibility": null,
+  "EscapedComputedClass": false,
+  "AnnotatePlan": false,
+  "SnapshotIndex": 53,
+  "QueuedAllocations": {
+    "cache": 0
+  },
+  "CreateIndex": 53,
+  "ModifyIndex": 55
+}
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/events.mdx b/content/nomad/v1.1.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..d86c045336
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/events.mdx
@@ -0,0 +1,385 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a servers backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management 
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock": "true",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "mock_driver": {
+              "Attributes": {
+                "driver.mock": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445193068-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/index.mdx b/content/nomad/v1.1.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..5f5cf579fe
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/index.mdx
@@ -0,0 +1,217 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.1.x/content/api-docs/jobs.mdx b/content/nomad/v1.1.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..a48ce48b6f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2261 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:3.2",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `purge` `(bool: false)` - Specifies that the job should stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.1.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..1aa1a7bd90
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1158 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /docs/commands/job/inspect
+[job-output]: /docs/commands/job/run#output
+[job-parse]: /api-docs/jobs#parse-job
+[job-run-json]: /docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad
+$ nomad job run -output example.nomad
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "image": "redis:3.2",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Id": "",
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": ""
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` stanza. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update stanza, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network stanza. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update stanza can be specified at the job or task group level.
+When specified at the job, the update stanza is inherited by all task groups.
+When specified in both the job and in a task group, the stanzas are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /docs/commands/node/drain
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v1.1.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.1.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..0f3738ffc7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.1.x/content/api-docs/metrics.mdx b/content/nomad/v1.1.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..ae0dbd6597
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/namespaces.mdx b/content/nomad/v1.1.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..882a279a4b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,185 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 31,
+    "Description": "Production API Servers",
+    "ModifyIndex": 31,
+    "Name": "api-prod",
+    "Quota": ""
+  },
+  {
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 5,
+    "Name": "default",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 31,
+  "Description": "Production API Servers",
+  "Quota": "",
+  "Hash": "N8WvePwqkp6J354eLJMKyhvsFdPELAos0VuBfMoVKoU=",
+  "ModifyIndex": 31,
+  "Name": "api-prod"
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Quota": "prod-quota"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/nodes.mdx b/content/nomad/v1.1.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..a01b1a0b86
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1117 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.1.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..e3660d7b15
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:8300",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:8205",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/index.mdx b/content/nomad/v1.1.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..924b79515c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](https://learn.hashicorp.com/tutorials/nomad/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/license.mdx b/content/nomad/v1.1.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..d03e22290b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.1.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..6be1441363
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /docs/concepts/consensus
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.1.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..cb44b2d0f3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,161 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "ModifyIndex": 5,
+    "SchedulerAlgorithm": "spread",
+    "MemoryOversubscriptionEnabled": true,
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler binpacks or spreads allocations on available nodes.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When `true`, tasks may exceed their reserved memory limit, if the client has excess memory capacity. Tasks must specify [`memory_max`](/docs/job-specification/resources#memory_max) to take advantage of memory oversubscription.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server stanza will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When `true`, tasks may exceed their reserved memory limit, if the client has excess memory capacity. Tasks must specify [`memory_max`](/docs/job-specification/resources#memory_max) to take advantage of memory oversubscription.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.1.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.1.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..81b56fd9a9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.1.x/content/api-docs/plugins.mdx b/content/nomad/v1.1.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..baabbe9f56
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/plugins.mdx
@@ -0,0 +1,137 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/quotas.mdx b/content/nomad/v1.1.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..edeed1de87
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/quotas.mdx
@@ -0,0 +1,352 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/recommendations.mdx b/content/nomad/v1.1.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..401458f896
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/regions.mdx b/content/nomad/v1.1.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..a7896d66c7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.1.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..877c2f6793
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/search.mdx b/content/nomad/v1.1.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..58d470c5c0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/search.mdx
@@ -0,0 +1,589 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given search
+term and context, where a context can be jobs, allocations, nodes, plugins, or namespaces.
+Additionally, fuzzy searching can be done across all contexts. For better control
+over the performance implications of fuzzy searching on Nomad servers, aspects of
+fuzzy searching can be tuned through the <code>[search]</code> stanza in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs, namespace:csi-list-plugin` |
+
+When ACLs are enabled, requests must have a token valid for `node:read`, `plugin:read` or
+`namespace:read-jobs` roles. If the token is only valid for a portion of these
+capabilities, then results will include results including only data readable with
+the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "plugins", or
+  "all", where "all" means every context will be searched. When "all" is selected,
+  additional prefix matches will be included for the "deployments", "evals", and
+  "volumes" types. When searching in the "jobs" context, results that fuzzy match
+  "groups", "services", "tasks", "images", "commands", and "classes" are also
+  included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /docs/configuration/search
diff --git a/content/nomad/v1.1.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.1.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..c1c8ca5166
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/status.mdx b/content/nomad/v1.1.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..6c0ca27dc4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/system.mdx b/content/nomad/v1.1.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..8875274f30
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/system.mdx
@@ -0,0 +1,58 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/ui.mdx b/content/nomad/v1.1.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..71c5f5a020
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/ui.mdx
@@ -0,0 +1,555 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/docs/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
diff --git a/content/nomad/v1.1.x/content/api-docs/validate.mdx b/content/nomad/v1.1.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..d01eef2685
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to a server. In the event a server can't be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.1.x/content/api-docs/volumes.mdx b/content/nomad/v1.1.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..1e4c7f9d32
--- /dev/null
+++ b/content/nomad/v1.1.x/content/api-docs/volumes.mdx
@@ -0,0 +1,761 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:3.2"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `PUT`    | `/v1/volumes/snapshot/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the volume to
+  snapshot. This must be the full ID. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+- `secrets` `(string: "")` - Specifies a list of key/value secrets for listing snapshots.
+  These key/value pairs are comma-separated and are passed directly to the CSI plugin.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2& \
+    secrets=secret-key-1=secret-value-1,secret-key-2=secret-value-2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent.mdx
new file mode 100644
index 0000000000..879acb2599
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.conf -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.conf`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[nomad_acls]: https://learn.hashicorp.com/collections/nomad/access-control
+[autoscaler_agent_nomad]: /docs/autoscaling/agent/nomad
+[autoscaler_cli_config]: /docs/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /docs/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/apm.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..8998f26f9e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+### `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /docs/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..f0f0f29e6d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/http.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..c6db482d29
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+### `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/nomad.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..dd9482aa3c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+### `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..ad6a306614
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: policy Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+}
+```
+
+### `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..63ac73f7f9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+### `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/strategy.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..ecacbe6124
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+### `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /docs/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/target.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..41150e97f9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+### `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /docs/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/agent/telemetry.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..7632668f11
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Stanza - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+### `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus`
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/api.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/api.mdx
new file mode 100644
index 0000000000..e46c4321cf
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/api.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/cli.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/cli.mdx
new file mode 100644
index 0000000000..7a9c054ec0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/cli.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /docs/autoscaling/agent
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/index.mdx
new file mode 100644
index 0000000000..9ffef8eaac
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autocaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The 
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/docs/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task stanza using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /docs/job-specification/scaling#scaling-stanza
+[autoscaling_policy]: /docs/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /tools/autoscaling/agent
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/checks.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/checks.mdx
new file mode 100644
index 0000000000..716ce8633c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/checks.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Nomad Autoscaler Check Calculations
+
+A scaling policy can include several checks all of which produce a scaling
+suggesting. The checks are executed at the same time during a policy evaluation
+and the results can conflict with each other. In a scenario like this, the
+autoscaler iterates the results the chooses the safest result which results in
+retaining the most capacity of the resource.
+
+In a scenario where two checks return different desired directions, the following
+logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the two same actions are suggested, but with different counts the
+following logic is applied, where the count is the absolute desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/index.mdx
new file mode 100644
index 0000000000..eb14454eb0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Internals
+description: >
+  This section covers the internals of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Internals
+
+This section covers the internals of the Nomad Autoscaler and explains the
+technical details of how it functions, its architecture, and sub-systems.
+
+- [Autoscaler plugins](/docs/autoscaling/internals/plugins)
+- [Check calculations](/docs/autoscaling/interals/checks)
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/node-selector-strategy.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/node-selector-strategy.mdx
new file mode 100644
index 0000000000..16cf6a3d1d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /docs/schedulers#system
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/apm.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/apm.mdx
new file mode 100644
index 0000000000..dec6b34b6c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /docs/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /docs/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/base.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/base.mdx
new file mode 100644
index 0000000000..3139970d38
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /docs/autoscaling/agent
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/index.mdx
new file mode 100644
index 0000000000..1f9944f74f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/docs/autoscaling/internals/plugins/apm)
+- [Strategies](/docs/autoscaling/internals/plugins/strategy)
+- [Targets](/docs/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/docs/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/strategy.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/strategy.mdx
new file mode 100644
index 0000000000..cc01cb5d3d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /docs/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/target.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/target.mdx
new file mode 100644
index 0000000000..ca001c901f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/internals/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /docs/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /docs/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..c9b58a7fea
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..2551d54ce7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "percentage-allocated_cpu"
+  ...
+}
+```
+
+Querying Nomad client node metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_stanza]: /docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..89de233c79
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/external/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..89f5583def
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [DigitalOcean Droplets][do-droplets]
+- [OpenStack Senlin][senlin]
+
+[plugin_guide]: /docs/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..4114093814
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /docs/autoscaling/plugins/external
+[plugin_dir_config]: /docs/autoscaling/agent#plugin_dir
+[apm]: /docs/autoscaling/agent/apm#apm-block
+[strategy]: /docs/autoscaling/agent/strategy#strategy-block
+[target]: /docs/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..7be6595179
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin will perform count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..bbfc4d8ad5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-traffic" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound valus to trigger the action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /docs/autoscaling/internals/checks
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..73bfd4519f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling stanza][nomad_scaling_stanza] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` stanza][nomad_job_stanza].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` stanza][nomad_group_stanza].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` stanza][nomad_task_stanza].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` stanza][nomad_resource_stanza]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /docs/autoscaling/policy
+[nomad_group_stanza]: /docs/job-specification/group
+[nomad_job_stanza]: /docs/job-specification/job
+[nomad_namespace_parameter]: /docs/job-specification/job#namespace
+[nomad_recommendations_api]: /api-docs/recommendations
+[nomad_region_parameter]: /docs/job-specification/job#region
+[nomad_resource_stanza]: /docs/job-specification/resources
+[nomad_scaling_stanza]: /docs/job-specification/scaling
+[nomad_task_stanza]: /docs/job-specification/task
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..2519cd85c9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `node_class`.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `datacenter`.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[node_selector_strategy]: /docs/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: https://www.vaultproject.io/docs/secrets/aws
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..e0118df4b1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `node_class`.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `datacenter`.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /docs/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_client_meta_tag]: /docs/configuration/client#meta
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[vault_azure_backend]: https://www.vaultproject.io/docs/secrets/azure
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..70abaf9171
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `node_class`.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource. Conflicts with
+  `datacenter`.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[node_selector_strategy]: /docs/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: https://www.vaultproject.io/docs/secrets/gcp
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/index.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..970b963279
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling stanza][nomad_scaling_stanza] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` stanza][nomad_job_stanza].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` stanza][nomad_group_stanza].
+
+[nomad_job_stanza]: /docs/job-specification/job#job-stanza
+[nomad_group_stanza]: /docs/job-specification/group#group-stanza
+[nomad_namespace_parameter]: /docs/job-specification/job#namespace
+[nomad_scaling_stanza]: /docs/job-specification/scaling
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/policy.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/policy.mdx
new file mode 100644
index 0000000000..0507c7991b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/policy.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` stanza][jobspec_scaling_stanza]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` stanza can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` stanza][jobspec_scaling_stanza] for Dynamic Application
+Sizing, the stanza requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[policy_default_cooldown_agent]: /docs/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /docs/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /docs/autoscaling/plugins/target
+[strategy_plugin_docs]: /docs/autoscaling/plugins/strategy
+[apm_plugin_docs]: /docs/autoscaling/plugins/apm
+[jobspec_scaling_stanza]: /docs/job-specification/scaling
diff --git a/content/nomad/v1.1.x/content/docs/autoscaling/telemetry.mdx b/content/nomad/v1.1.x/content/docs/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..16706d5943
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /docs/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..5d7121cf30
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Bootstrap the initial token:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..a10acdb42d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /docs/commands/acl/bootstrap
+[policyapply]: /docs/commands/acl/policy-apply
+[policydelete]: /docs/commands/acl/policy-delete
+[policyinfo]: /docs/commands/acl/policy-info
+[policylist]: /docs/commands/acl/policy-list
+[tokencreate]: /docs/commands/acl/token-create
+[tokenupdate]: /docs/commands/acl/token-update
+[tokendelete]: /docs/commands/acl/token-delete
+[tokeninfo]: /docs/commands/acl/token-info
+[tokenlist]: /docs/commands/acl/token-list
+[tokenself]: /docs/commands/acl/token-self
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..3a01ca5cb2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..317a91bde9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..13f30637b6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..43b28f8d5c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..c99073608e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..0611a736d9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v1.1.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..4988a4b77e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.1.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/agent.mdx b/content/nomad/v1.1.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..d69ae50395
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/agent.mdx
@@ -0,0 +1,220 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /docs/configuration/consul#address
+[alloc_dir]: /docs/configuration/client#alloc_dir
+[auth]: /docs/configuration/consul#auth
+[auto_advertise]: /docs/configuration/consul#auto_advertise
+[bind_addr]: /docs/configuration#bind_addr
+[bootstrap_expect]: /docs/configuration/server#bootstrap_expect
+[ca_file]: /docs/configuration/consul#ca_file
+[cert_file]: /docs/configuration/consul#cert_file
+[checks_use_advertise]: /docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /docs/configuration/consul#client_auto_join
+[client_http_check_name]: /docs/configuration/consul#client_http_check_name
+[client_service_name]: /docs/configuration/consul#client_service_name
+[configuration]: /docs/configuration
+[data_dir]: /docs/configuration#data_dir
+[datacenter]: /docs/configuration#datacenter
+[enabled]: /docs/configuration/acl#enabled
+[encryption overview]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption
+[key_file]: /docs/configuration/consul#key_file
+[log_json]: /docs/configuration#log_json
+[log_level]: /docs/configuration#log_level
+[meta]: /docs/configuration/client#meta
+[name]: /docs/configuration#name
+[network_interface]: /docs/configuration/client#network_interface
+[node_class]: /docs/configuration/client#node_class
+[nomad agent]: /docs/install/production/nomad-agent
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: /docs/configuration#region
+[rejoin_after_leave]: /docs/configuration/server#rejoin_after_leave
+[replication_token]: /docs/configuration/acl#replication_token
+[retry_interval]: /docs/configuration/server#retry_interval
+[retry_max]: /docs/configuration/server#retry_max
+[server_auto_join]: /docs/configuration/consul#server_auto_join
+[server_http_check_name]: /docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /docs/configuration/consul#server_serf_check_name
+[server_service_name]: /docs/configuration/consul#server_service_name
+[servers]: /docs/configuration/client#servers
+[ssl]: /docs/configuration/consul#ssl
+[state_dir]: /docs/configuration/client#state_dir
+[token]: /docs/configuration/consul#token
+[verify_ssl]: /docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..4226b41827
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..3a99a09125
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..ff71cf69c4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..7fd38a21f4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..a07820567c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be restarted.
+
+Task name may also be specified using the `-task` option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-task`: Specify the individual task to restart.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.1.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..b82195172a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..46d6ded1b8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..da601e8bae
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /docs/commands/deployment/list 'List all deployments'
+[pause]: /docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..5d6bfc6cfc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..5927fe40bf
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3ea4229c7a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..cc54b45d75
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion. 
+When combined with `-verbose`, it will also display the allocations for the given 
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.1.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.1.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..273007c7d1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
diff --git a/content/nomad/v1.1.x/content/docs/commands/eval-status.mdx b/content/nomad/v1.1.x/content/docs/commands/eval-status.mdx
new file mode 100644
index 0000000000..6d93efc469
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/eval-status.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output the evaluation in its JSON format.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/index.mdx b/content/nomad/v1.1.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..581fa142f6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/opt/nomad/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.1.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..77fe845631
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.1.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..41f33be188
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+[eval status]: /docs/commands/eval-status
+[parameterized job]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.1.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..a9170f5b6b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/history.mdx b/content/nomad/v1.1.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..2252b7e932
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/index.mdx b/content/nomad/v1.1.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..355094dee7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /docs/commands/job/promote "Promote a job's canaries"
+[revert]: /docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/init.mdx b/content/nomad/v1.1.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..95e2dc911e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[drivers]: /docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.1.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..86c34ae0f7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /api-docs/jobs
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.1.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..c775b0d00d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /docs/commands/eval-status
+[force the evaluation]: /api-docs/jobs#force-new-periodic-instance
+[periodic job]: /docs/job-specification/periodic
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.1.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..fc913acb82
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:3.2"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+[job specification]: /docs/job-specification
+[hcl job specification]: /docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /docs/commands/job/run#check-index
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.1.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..6d67ac56e2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`list-jobs`, and `read-job` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.1.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..732b6a038e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:3.2"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /docs/commands/job/history
+[eval status]: /docs/commands/eval-status
+[consul service identity]: /docs/configuration/consul#allow_unauthenticated
+[vault policy]: /docs/configuration/vault#allow_unauthenticated
+[run]: /docs/commands/job/run
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/run.mdx b/content/nomad/v1.1.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..d34f81b9d4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,237 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` stanza reading from Consul KV will
+  scoped to the the specified Consul namespace. If Consul ACLs are enabled and the
+  [`allow_unauthenticated`] Nomad server Consul configuration is not enabled, then
+  a Consul token must be supplied with appropriate service and kv Consul ACL policy
+  permissions.
+
+- `-vault-token`: If set, the passed Vault token is stored in the job before
+  sending to the Nomad servers. This allows passing the Vault token without
+  storing it in the job file. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable and that found in the job.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run job1.nomad
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[deployment status]: /docs/commands/deployment#status
+[`batch`]: /docs/schedulers#batch
+[`consul` stanza `allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
+[deployment status]: /docs/commands/deployment#status
+[eval status]: /docs/commands/eval-status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /docs/commands/job/plan
+[job specification]: /docs/job-specification
+[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
+[JSON jobs]: /api-docs/json-jobs
+[`system`]: /docs/schedulers#system
+[`vault` stanza `allow_unauthenticated`]: /docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.1.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..61d6dd09bb
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `scale-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.1.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..98ecb45dd8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/status.mdx b/content/nomad/v1.1.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..e28450bad5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,254 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.1.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..5255e838a0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /docs/commands/eval-status
+[multi-region]: /docs/job-specification/multiregion
diff --git a/content/nomad/v1.1.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.1.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..9b3d172687
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## Examples
+
+Validate a job with invalid syntax:
+
+```shell-session
+$ nomad job validate example.nomad
+Job validation errors:
+1 error(s) occurred:
+
+* group "cache" -> task "redis" -> config: 1 error(s) occurred:
+
+* field "image" is required
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v1.1.x/content/docs/commands/license/get.mdx b/content/nomad/v1.1.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..5a3f9f3684
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/license/index.mdx b/content/nomad/v1.1.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..b22040b158
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+
+[get]: /docs/commands/license/get 'Get the current license'
diff --git a/content/nomad/v1.1.x/content/docs/commands/monitor.mdx b/content/nomad/v1.1.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..ff0738014c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..97f84c6661
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <namespace>
+```
+
+The `namespace apply` command requires the name of the namespace to be created
+or updated.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..14b6cb7196
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..68eac6a6dd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /docs/commands/namespace/list 'List available namespaces'
+[status]: /docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f2cc7c3304
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..0f6eedfba3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.1.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..45362a8407
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name        = default
+Description = Default shared namespace
+Quota       = shared-default-quota
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/node/config.mdx b/content/nomad/v1.1.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..24507070c3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /docs/configuration/client#servers
diff --git a/content/nomad/v1.1.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.1.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..ee9d5576f9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] stanza until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are force removed from the
+  node. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Force remove allocations off the node immediately.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node
+  without being force stopped after a certain deadline.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs are stopped
+  last. You should always use this flag when draining a node running
+  [CSI node plugins][internals-csi].
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /docs/commands/node/eligibility
+[migrate]: /docs/job-specification/migrate
+[node status]: /docs/commands/node/status
+[workload migration guide]: https://learn.hashicorp.com/tutorials/nomad/node-drain
+[internals-csi]: /docs/concepts/plugins/csi
diff --git a/content/nomad/v1.1.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.1.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..92d0692e06
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /docs/commands/node/drain
diff --git a/content/nomad/v1.1.x/content/docs/commands/node/index.mdx b/content/nomad/v1.1.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..b98b6edb45
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /docs/commands/node/config 'View or modify client configuration details'
+[drain]: /docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.1.x/content/docs/commands/node/status.mdx b/content/nomad/v1.1.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..e667299a0f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,366 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..487bfea74e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..155ecaaf76
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /docs/configuration/server#upgrade_version
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..bfb4bf2956
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the log monitor command.
+  Defaults to `"2m"`. Logs will be captured from specified servers and
+  nodes at `log-level`.
+
+- `-interval=2m`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids,
+  to monitor for logs and include pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes).
+
+- `-pprof-duration=<duration>`: Duration for pprof collection. Defaults to 1s.
+
+- `-server-id=s1,s2`: Comma separated list of Nomad server names, "leader", or
+  "all" to monitor for logs and include pprof profiles.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..c800a96435
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /api-docs/operator 'Operator API documentation'
+[outage recovery guide]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
+[remove]: /docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
+[snapshot-save]: /docs/commands/operator/snapshot-save 'Snapshot Save command'
+[snapshot-restore]: /docs/commands/operator/snapshot-restore 'Snapshot Restore command'
+[snapshot-inspect]: /docs/commands/operator/snapshot-inspect 'Snapshot Inspect command'
+[snapshot-agent]: /docs/commands/operator/snapshot-agent 'Snapshot Agent command'
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..e12e18997b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe" base64
+alphabet. If you use another tool such as OpenSSL to generate the gossip key,
+you should pipe the input through the `base64(1)` command to ensure it is
+safely encoded. For example: `openssl rand 32 | base64`
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..4a4200cb99
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..ecb9ebfb8a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..f0c44ef632
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The Raft list-peers command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /api-docs/operator
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..1039c2bb01
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /docs/commands/server/members 'Nomad server members command'
+[operator]: /api-docs/operator 'Nomad Operator API'
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..61e84d2454
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..5c0b8d51ec
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..8513bfc658
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..dc33fa0003
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.1.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.1.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..001d5ae75b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[status]: /docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.1.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.1.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..78de328905
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6746241535
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..0956cba4d5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..823a0c8d12
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /docs/commands/quota/apply
+[quotadelete]: /docs/commands/quota/delete
+[quotainit]: /docs/commands/quota/init
+[quotainspect]: /docs/commands/quota/inspect
+[quotalist]: /docs/commands/quota/list
+[quotastatus]: /docs/commands/quota/status
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..29b226bb43
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..1ff8247c14
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..24e34442cc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.1.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..45ea3a4ca5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.1.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..3660b9f70f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.1.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..8d930e8c57
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.1.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..e95f182d66
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /docs/commands/recommendation/apply
+[recommendationdismiss]: /docs/commands/recommendation/dismiss
+[recommendationinfo]: /docs/commands/recommendation/info
+[recommendationlist]: /docs/commands/recommendation/list
diff --git a/content/nomad/v1.1.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.1.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..a0f80bb60d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.1.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..2111f423b6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.1.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..107273edf8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /docs/commands/scaling/policy-info
+[scalingpolicylist]: /docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.1.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.1.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.1.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.1.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..088b249d0d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.1.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..18263c8338
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.1.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..b30f828cfa
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /docs/commands/sentinel/delete
+[list]: /docs/commands/sentinel/list
+[read]: /docs/commands/sentinel/read
+[apply]: /docs/commands/sentinel/apply
diff --git a/content/nomad/v1.1.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.1.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..75bef2f684
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.1.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..fb97b3cbff
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.1.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d31ab75e70
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/server/index.mdx b/content/nomad/v1.1.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..ca91b4bfef
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /docs/commands/server/join 'Join server nodes together'
+[members]: /docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.1.x/content/docs/commands/server/join.mdx b/content/nomad/v1.1.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..152a102f52
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/server/members.mdx b/content/nomad/v1.1.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..f40c835d25
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in the
+  standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name          Addr      Port  Status  Proto  Build     DC   Region
+node1.global  10.0.0.8  4648  alive   2      0.1.0dev  dc1  global
+node2.global  10.0.0.9  4648  alive   2      0.1.0dev  dc1  global
+```
+
+Detailed view:
+
+```shell-session
+$ nomad server members -detailed
+Name   Addr      Port  Tags
+node1  10.0.0.8  4648  bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+node2  10.0.0.9  4648  bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/status.mdx b/content/nomad/v1.1.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.1.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..0750d31420
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/system/index.mdx b/content/nomad/v1.1.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..babd3de347
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.1.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.1.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/ui.mdx b/content/nomad/v1.1.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..21bc2decc6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/ui.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/version.mdx b/content/nomad/v1.1.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..e5b4ef6160
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/version.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f9e8592eea
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+The file may be provided as either HCL or JSON. An example HCL configuration:
+
+```hcl
+id           = "ebs_prod_db1"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = "noatime"
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume. This field
+  may be used by the external storage provider to tag the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports
+  cloning, the external ID of the volume to clone when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `clone_id` cannot be set if the `snapshot_id` field is set.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a
+  minimum capacity, in bytes. The capacity of a volume may be the
+  physical size of a disk, or a quota, depending on the storage
+  provider. The specific size of the resulting volume will be
+  somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the
+  same value. Accepts human-friendly suffixes such as `"100GiB"`. This
+  field may not be supported by all storage providers.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a
+  maximum capacity, in bytes. The capacity of a volume may be the
+  physical size of a disk, or a quota, depending on the storage
+  provider. The specific size of the resulting volume will be
+  somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the
+  same value. Accepts human-friendly suffixes such as `"100GiB"`. This
+  field may not be supported by all storage providers.
+
+- `capability` `(Capability: <required>)` - Option for validating the
+  capbility of a volume. You must provide at least one `capability` block, and
+  you must provide a block for each capability you intend to use in a job's
+  [`volume`] block. Each `capability` block must have the following fields:
+
+  - `access_mode` `(string: <required>)` - Defines whether a volume should be
+    available concurrently. Can be one of `"single-node-reader-only"`,
+    `"single-node-writer"`, `"multi-node-reader-only"`,
+    `"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI
+    plugins support only single-node modes. Consult the documentation of the
+    storage provider and CSI plugin.
+
+  - `attachment_mode` `(string: <required>)` - The storage API that will be used
+    by the volume. Most storage providers will support `"file-system"`, to mount
+    volumes using the CSI filesystem API. Some storage providers will support
+    `"block-device"`, which will mount the volume with the CSI block device API
+    within the container.
+
+- `mount_options` - Options for mounting `file-system` volumes that don't
+  already have a pre-formatted file system. This block will be validated
+  during volume creation against the `capability` field. The `mount_options`
+  provided in a job specification's [`volume`] block will override this
+  block. Consult the documentation for your storage provider and CSI plugin as
+  to whether these options are required or necessary.
+
+  - `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+  - `mount_flags` `([]string: <optional>)` - The flags passed to `mount`
+    (ex. `["ro", "noatime"]`)
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings used as credentials for publishing and
+  unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  configure the volume. The details of these parameters are specific
+  to each storage provider, so please see the specific plugin
+  documentation for more information.
+
+### Unused Fields
+
+Note that several fields used in the [`volume register`] command are set
+automatically by the plugin when `volume create` is successful. You should not
+set the `external_id` or `context` fields described on that page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: #volume-specification
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume_source]: /docs/job-specification/volume#source
+[registered]: /docs/commands/volume/register
+[`volume register`]: /docs/commands/volume/register
+[`volume`]: /docs/job-specification/volume
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..ae8996f865
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /docs/commands/volume/deregister
+[registered]: /docs/commands/volume/register
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..e98b8208aa
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /docs/commands/volume/delete
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..2fc9eeceda
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /docs/commands/volume/create
+[delete]: /docs/commands/volume/delete
+[deregister]: /docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /docs/commands/volume/detach 'Detach a volume'
+[init]: /docs/commands/volume/init 'Create an example volume specification file'
+[register]: /docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /docs/commands/volume/snapshot-create
+[snapshot-delete]: /docs/commands/volume/snapshot-delete
+[snapshot-list]: /docs/commands/volume/snapshot-list
+[status]: /docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..42accb0fb2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume
+specification][volume_specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job
+file is read from STDIN. Otherwise it is read from the file at the supplied
+path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+The file may be provided as either HCL or JSON. An example HCL configuration:
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = "noatime"
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `capability` `(Capability: <required>)` - Option for validating the
+  capability of a volume. You must provide at least one `capability` block, and
+  you must provide a block for each capability you intend to use in a job's
+  [`volume`] block. Each `capability` block must have the following fields:
+
+  - `access_mode` `(string: <required>)` - Defines whether a volume should be
+    available concurrently. Can be one of `"single-node-reader-only"`,
+    `"single-node-writer"`, `"multi-node-reader-only"`,
+    `"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI
+    plugins support only single-node modes. Consult the documentation of the
+    storage provider and CSI plugin.
+
+  - `attachment_mode` `(string: <required>)` - The storage API that will be used
+    by the volume. Most storage providers will support `"file-system"`, to mount
+    volumes using the CSI filesystem API. Some storage providers will support
+    `"block-device"`, which will mount the volume with the CSI block device API
+    within the container.
+
+- `mount_options` - Options for mounting `file-system` volumes that don't
+  already have a pre-formatted file system. This block will be validated
+  during volume creation against the `capability` field. The `mount_options`
+  provided in a job specification's [`volume`] block will override this
+  block. Consult the documentation for your storage provider and CSI plugin as
+  to whether these options are required or necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings used as credentials for publishing and
+  unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  configure the volume. The details of these parameters are specific
+  to each storage provider, so please see the specific plugin
+  documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional
+  key-value map of strings passed directly to the CSI plugin to
+  validate the volume. The details of these parameters are specific to
+  each storage provider, so please see the specific plugin
+  documentation for more information.
+
+### Unused Fields
+
+Note that several fields used in the [`volume create`] command are set
+automatically by the plugin when `volume create` is successful and cannot be
+set on a pre-existing volume. You should not set the `snapshot_id`,
+`clone_id`, `capacity_min`, or `capacity_max` fields described on that page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: #volume-specification
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume_source]: /docs/job-specification/volume#source
+[`volume`]: /docs/job-specification/volume
+[`volume create`]: /docs/commands/volume/create
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bdadc56f68
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..84c07f4e65
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..50710b10dd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secrets`: A list of comma separated secret key/value pairs to be passed
+  to the CSI driver.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secrets key1=value1,key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.1.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.1.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..6e4a092748
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[`volume create`]: /docs/commands/volume/create
diff --git a/content/nomad/v1.1.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.1.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..96c3babef6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+#### Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+#### Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+#### Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+#### Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+#### Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+#### Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+#### Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+#### Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/docs/install/production/requirements#network-topology).
+
+#### Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+#### Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+#### Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/docs/concepts/consensus),
+[gossip protocol](/docs/concepts/gossip), and [scheduler design](/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v1.1.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.1.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.1.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.1.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..12dcba295f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,465 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. Within the
+  `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] stanza for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /docs/job-specification/artifact
+[csi volumes]: /docs/concepts/plugins/csi
+[dispatch payloads]: /docs/job-specification/dispatch_payload
+[templates]: /docs/job-specification/template
+[`data_dir`]: /docs/configuration#data_dir
+[`ephemeral_disk`]: /docs/job-specification/ephemeral_disk
+[artifact]: /docs/job-specification/artifact
+[chroot contents]: /docs/drivers/exec#chroot
+[filesystem isolation capability]: /docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /docs/job-specification/ephemeral_disk#migrate
+[template]: /docs/job-specification/template
+[volume mounts]: /docs/job-specification/volume_mount
diff --git a/content/nomad/v1.1.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.1.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..ac7349555e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.1.x/content/docs/concepts/index.mdx b/content/nomad/v1.1.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.1.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.1.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..c1e64e2a0f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /docs/configuration/plugin
diff --git a/content/nomad/v1.1.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.1.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..752a34146e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the
+industry-standard Container Storage Interface specification unifies
+these APIs in a way that's agnostic to both the storage vendor and the
+container orchestrator. Each storage provider can build its own CSI
+plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
+(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
+Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given
+Nomad client node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped.
+
+You should always run node plugins as Nomad `system` jobs and use the
+`-ignore-system` flag on the `nomad node drain` command to ensure that the
+node plugins are still running while the node is being drained. Use
+constraints for the node plugin jobs based on the availability of volumes. For
+example, AWS EBS volumes are specific to particular availability zones with a
+region. Controller plugins can be run as `service` jobs.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.1.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.1.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..ac288eefc3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.1.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.1.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c2f1bd8c11
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/docs/concepts/plugins/task-drivers)
+- [Devices](/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.1.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.1.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..b958e71d66
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propogating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but *not* stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /docs/drivers/remote
diff --git a/content/nomad/v1.1.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.1.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..95435ce76b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.1.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.1.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..8aac85c9fb
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.1.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.1.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..c62d532f1e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, a `system` scheduler
+that is used to run jobs on every node, and a `core` scheduler which is used
+for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.1.x/content/docs/concepts/security.mdx b/content/nomad/v1.1.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..247e15d329
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/concepts/security.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](https://www.consul.io/docs/concepts/security), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](https://learn.hashicorp.com/collections/nomad/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+
+  - Access to read and write to a namespace can be
+    controlled to allow for granular access to job information managed within a
+    multi-tenant cluster.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](https://www.vaultproject.io/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](https://learn.hashicorp.com/collections/nomad/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+- **[ACLs enabled](https://learn.hashicorp.com/collections/nomad/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code/)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](https://learn.hashicorp.com/tutorials/nomad/web-ui-access) and [API](/api-docs) access to agents. |
+| **4647** / TCP       | Servers | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
diff --git a/content/nomad/v1.1.x/content/docs/configuration/acl.mdx b/content/nomad/v1.1.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..f67bb1db55
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: acl Stanza - Agent Configuration
+description: >-
+  The "acl" stanza configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Stanza
+
+<Placement groups={['acl']} />
+
+The `acl` stanza configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region.
+
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.1.x/content/docs/configuration/audit.mdx b/content/nomad/v1.1.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..4776e96149
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,295 @@
+---
+layout: docs
+page_title: audit Stanza - Agent Configuration
+description: >-
+  The "audit" stanza configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Stanza
+
+<Placement groups={['audit']} />
+
+The `audit` stanza configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit stanza (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-stanza): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-stanza)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Stanza
+
+The `sink` stanza is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the stanza corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Stanza
+
+The `filter` stanza is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.1.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.1.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..f1b41f0c10
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Stanza - Agent Configuration
+description: >-
+  The "autopilot" stanza configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Stanza
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` stanza configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.1.x/content/docs/configuration/client.mdx b/content/nomad/v1.1.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..93660f32ce
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/client.mdx
@@ -0,0 +1,500 @@
+---
+layout: docs
+page_title: client Stanza - Agent Configuration
+description: |-
+  The "client" stanza configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Stanza
+
+<Placement groups={['client']} />
+
+The `client` stanza configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, 20% of the node's CPU could be reserved to target a CPU utilization
+  of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/docs/job-specification/artifact) stanzas.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/docs/job-specification/template) stanzas.
+
+- `host_volume` <code>([host_volume](#host_volume-stanza): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-stanza): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/docs/drivers/exec#chroot) for
+the full list.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the number of CPU cores to reserve.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-stanza) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+### `host_volume` Stanza
+
+The `host_volume` stanza is used to make volumes available to jobs.
+
+The key of the stanza corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Stanza
+
+The `host_network` stanza is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the stanza corresponds to the name of the network used in the
+[`host_network`](/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[server-join]: /docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
diff --git a/content/nomad/v1.1.x/content/docs/configuration/consul.mdx b/content/nomad/v1.1.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..a1cb05f23e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,220 @@
+---
+layout: docs
+page_title: consul Stanza - Agent Configuration
+description: |-
+  The "consul" stanza configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Stanza
+
+<Placement groups={['consul']} />
+
+The `consul` stanza configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` stanza is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the bind address.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`](https://www.consul.io/docs/agent/options#_grpc_port)
+  listener by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](https://www.consul.io/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: https://learn.hashicorp.com/tutorials/nomad/clustering 'Automatic Bootstrapping'
diff --git a/content/nomad/v1.1.x/content/docs/configuration/index.mdx b/content/nomad/v1.1.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..ececc35c29
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/index.mdx
@@ -0,0 +1,386 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this stanza take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most common
+    bind address to change.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this stanza take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address advertised to Nomad client nodes. This allows
+    advertising a different RPC address than is used by Nomad Servers such that
+    the clients can connect to the Nomad servers if they are behind a NAT.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+  ~> **WARNING**: This directory **must not** be set to a directory that is
+  [included in the chroot](/docs/drivers/exec#chroot) if you use the
+  [`exec`](/docs/drivers/exec) driver.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin stanza may be repeated, once for each plugin being
+  configured. The key of the stanza is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
diff --git a/content/nomad/v1.1.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.1.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..189372069e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Stanza - Agent Configuration
+description: The "plugin" stanza is used to configure a Nomad plugin.
+---
+
+# `plugin` Stanza
+
+<Placement groups={['plugin']} />
+
+The `plugin` stanza is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.1.x/content/docs/configuration/search.mdx b/content/nomad/v1.1.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..061054e7bf
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Stanza - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" stanza specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Stanza
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` stanza specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.1.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.1.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..4ef417f10b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Stanza - Agent Configuration
+description: >-
+  The "sentinel" stanza configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Stanza
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` stanza configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.1.x/content/docs/configuration/server.mdx b/content/nomad/v1.1.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..8ab743e00b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/server.mdx
@@ -0,0 +1,320 @@
+---
+layout: docs
+page_title: server Stanza - Agent Configuration
+description: |-
+  The "server" stanza configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Stanza
+
+<Placement groups={['server']} />
+
+The `server` stanza configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use -
+  for server-specific data, including the replicated log. By default, this is -
+  the top-level [data_dir](/docs/configuration#data_dir)
+  suffixed with "server", like `"/opt/nomad/server"`. This must be an absolute
+  path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator keygen`] command. The
+  provided key is automatically persisted to the data directory and loaded
+  automatically whenever the agent is restarted. This means that to encrypt
+  Nomad server's gossip protocol, this option only needs to be provided once
+  on each agent's initial startup sequence. If it is provided after Nomad has
+  been initialized with an encryption key, then the provided key is ignored
+  and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path (`/opt/nomad/license.hclic`). The
+  license can also be set by setting `NOMAD_LICENSE_PATH` or by setting
+  `NOMAD_LICENSE` as the entire license value. `license_path` has the highest
+  precedence, followed by `NOMAD_LICENSE` and then `NOMAD_LICENSE_PATH`.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `protocol_version` `(int: 1)` - Specifies the Nomad protocol version to use
+  when communicating with other Nomad servers. This value is typically not
+  required as the agent internally knows the latest version, but may be useful
+  in some upgrade scenarios.
+
+- `raft_protocol` `(int: 2)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/docs/telemetry/metrics) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  stanza][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join stanza][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join stanza][server-join].
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration stanza. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/tutorials/nomad/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` stanza
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm = "spread"
+
+    memory_oversubscription_enabled = true
+
+    preemption_config {
+      batch_scheduler_enabled   = true
+      system_scheduler_enabled  = true
+      service_scheduler_enabled = true
+    }
+  }
+}
+```
+
+[encryption]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[`nomad operator keygen`]: /docs/commands/operator/keygen
+[search]: /docs/configuration/search
diff --git a/content/nomad/v1.1.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.1.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..604fcf9930
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: server_join Stanza - Agent Configuration
+description: >-
+  The "server_join" stanza specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Stanza
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` stanza specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.1.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.1.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..404e5cb9f7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: telemetry Stanza - Agent Configuration
+description: |-
+  The "telemetry" stanza configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Stanza
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` stanza configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` stanza. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` stanza,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.1.x/content/docs/configuration/tls.mdx b/content/nomad/v1.1.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..2001d60e76
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: tls Stanza - Agent Configuration
+description: |-
+  The "tls" stanza configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Stanza
+
+<Placement groups={['tls']} />
+
+The `tls` stanza configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` stanza. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` stanzas. Remember that the
+`tls` stanza is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a
+`SIGHUP` signal. Note that this will only reload a subset of the configuration
+file, including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.1.x/content/docs/configuration/vault.mdx b/content/nomad/v1.1.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..51effb228b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: vault Stanza - Agent Configuration
+description: |-
+  The "vault" stanza configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Stanza
+
+<Placement groups={['vault']} />
+
+The `vault` stanza configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive child tokens for jobs
+  requesting tokens.
+  Visit the [Vault Integration Guide](/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.1.x/content/docs/devices/external/index.mdx b/content/nomad/v1.1.x/content/docs/devices/external/index.mdx
new file mode 100644
index 0000000000..b2573aa18f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/devices/external/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: A list of community supported Device Plugins.
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+## Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [USB][usb]
+
+## Authoring Device Plugins
+
+Nomad has a plugin system for defining device drivers. External device plugins
+will have the same user experience as built in drivers. For details on
+authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/concepts/plugins
+[usb]: /docs/devices/external/usb
diff --git a/content/nomad/v1.1.x/content/docs/devices/external/usb.mdx b/content/nomad/v1.1.x/content/docs/devices/external/usb.mdx
new file mode 100644
index 0000000000..1e3bd46942
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/devices/external/usb.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin stanza then needs to be added. A full example of the
+plugin stanza needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.1.x/content/docs/devices/index.mdx b/content/nomad/v1.1.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..e4efb934ea
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/devices/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in Nomad.
+Devices are physical hardware that exists on a node such as a GPU or an FPGA. By
+having extensible device plugins, Nomad has the flexibility to support a broad
+set of devices and allows the community to build additional device plugins as
+needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
+
+For details on authoring a device plugin, please refer to the [plugin authoring
+guide][plugin_guide].
+
+[plugin_guide]: /docs/concepts/plugins
diff --git a/content/nomad/v1.1.x/content/docs/devices/nvidia.mdx b/content/nomad/v1.1.x/content/docs/devices/nvidia.mdx
new file mode 100644
index 0000000000..45398f2255
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/devices/nvidia.mdx
@@ -0,0 +1,334 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nvidia-gpu`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad. The Nvidia
+plugin is built into Nomad and does not need to be downloaded separately.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nvidia-gpu` the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+
+### Docker Driver Requirements
+
+In order to use the Nvidia driver plugin with the Docker driver, please follow
+the installation instructions for
+[`nvidia-docker`](<https://github.com/NVIDIA/nvidia-docker/wiki/Installation-(version-1.0)>).
+
+## Plugin Configuration
+
+```hcl
+plugin "nvidia-gpu" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nvidia-gpu` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Restrictions
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver] and plans to
+bring support to the built-in [`exec`][exec-driver] and [`java`][java-driver]
+drivers. Support for [`lxc`][lxc-driver] should be possible by installing the
+[Nvidia hook](https://github.com/lxc/lxc/blob/master/hooks/nvidia) but is not
+tested or documented by Nomad.
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m43s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2674/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Allocations
+No allocations placed
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+ID            = 4d46e59f
+Name          = nomad
+Class         = <none>
+DC            = dc1
+Drain         = false
+Eligibility   = eligible
+Status        = ready
+Uptime        = 19m59s
+Driver Status = docker,mock_driver,raw_exec
+
+Node Events
+Time                  Subsystem  Message
+2019-01-23T18:25:18Z  Cluster    Node registered
+
+Allocated Resources
+CPU          Memory      Disk
+0/15576 MHz  0 B/55 GiB  0 B/28 GiB
+
+Allocation Resource Utilization
+CPU          Memory
+0/15576 MHz  0 B/55 GiB
+
+Host Resource Utilization
+CPU             Memory          Disk
+2673/15576 MHz  1.5 GiB/55 GiB  3.0 GiB/31 GiB
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+
+Allocations
+No allocations placed
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:9.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+ID                  = d250baed
+Eval ID             = 21bd7584
+Name                = gpu-test.smi[0]
+Node ID             = 4d46e59f
+Job ID              = example
+Job Version         = 0
+Client Status       = complete
+Client Description  = All tasks have completed
+Desired Status      = run
+Desired Description = <none>
+Created             = 7s ago
+Modified            = 2s ago
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[docker-driver]: /docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /docs/drivers/external/lxc 'Nomad lxc Driver'
diff --git a/content/nomad/v1.1.x/content/docs/drivers/docker.mdx b/content/nomad/v1.1.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..d4b73e38e4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1169 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:3.2"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) stanza, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group `network.mode = "bridge"` you should not set the Docker config
+  `network_mode`, or the container will be unable to reach other containers in
+  the task group. This will also prevent [Connect]-enabled tasks from reaching
+  the Envoy sidecar proxy. You must also set any DNS options in the `network.dns`
+  block and not in the task configuration.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-add`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`][allow_caps] plugin option key in the client node's configuration.
+  For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-drop`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`][allow_caps] plugin option key in the client node's configuration.
+  For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource stanza and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network stanza and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin stanza][plugin-stanza]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities can be obtained
+  by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports
+  the value `"all"` as a shortcut for allow-listing all capabilities supported by
+  the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` stanza:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` stanza:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` stanza:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` stanza:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` stanza for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config stanza.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /docs/drivers/docker#cap_add
+[cap_drop]: /docs/drivers/docker#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /docs/drivers/docker#allow_caps
+[Connect]: /docs/job-specification/connect
+[`bridge`]: docs/job-specification/network#bridge
diff --git a/content/nomad/v1.1.x/content/docs/drivers/exec.mdx b/content/nomad/v1.1.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..b2206d7ee6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /docs/drivers/exec#default_ipc_mode
+[cap_add]: /docs/drivers/exec#cap_add
+[cap_drop]: /docs/drivers/exec#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/containerd.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/containerd.mdx
new file mode 100644
index 0000000000..70247c32ed
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` stanza in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v0.9.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v0.9.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` stanza.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` stanza.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] stanza documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service stanza instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` stanza allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` stanza can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+stanza can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /docs/commands/job/init
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /docs/job-specification/network
+[`service`]: /docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/firecracker-task-driver.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..86aba308cd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/iis.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/iis.mdx
new file mode 100644
index 0000000000..3baa889ada
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network stanza port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/index.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/index.mdx
new file mode 100644
index 0000000000..ba1fe734c4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/index.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [LXC][lxc]
+- [Rkt][rkt]
+- [Podman][podman]
+- [Singularity][singularity]
+- [Jail task driver][jail-task-driver]
+- [Pot][pot]
+- [Firecracker][firecracker-task-driver]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+- [containerd][nomad-driver-containerd]
+
+[lxc]: /docs/drivers/external/lxc
+[rkt]: /docs/drivers/external/rkt
+[plugin_guide]: /docs/concepts/plugins
+[singularity]: /docs/drivers/external/singularity
+[jail-task-driver]: /docs/drivers/external/jail-task-driver
+[podman]: /docs/drivers/external/podman
+[pot]: /docs/drivers/external/pot
+[firecracker-task-driver]: /docs/drivers/external/firecracker-task-driver
+[nspawn-driver]: /docs/drivers/external/nspawn
+[nomad-driver-iis]: /docs/drivers/external/iis
+[nomad-driver-containerd]: /docs/drivers/external/containerd
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/jail-task-driver.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/jail-task-driver.mdx
new file mode 100644
index 0000000000..adc5dea14c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /docs/configuration#plugin_dir
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/lxc.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/lxc.mdx
new file mode 100644
index 0000000000..8a06aa346d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` stanza:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: https://learn.hashicorp.com/tutorials/nomad/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/nspawn.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/nspawn.mdx
new file mode 100644
index 0000000000..2e5769d10b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[docker_driver]: /docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /docs/integrations/consul-connect
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/pot.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/pot.mdx
new file mode 100644
index 0000000000..644925cb64
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/rkt.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/rkt.mdx
new file mode 100644
index 0000000000..4f2d725900
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:3.2"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v1.1.x/content/docs/drivers/external/singularity.mdx b/content/nomad/v1.1.x/content/docs/drivers/external/singularity.mdx
new file mode 100644
index 0000000000..4900ed822c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/external/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.1.x/content/docs/drivers/index.mdx b/content/nomad/v1.1.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..16affe6a23
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin stanza][plugin] documentation for examples on how to
+use the `plugin` stanza in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/concepts/plugins
+[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.1.x/content/docs/drivers/java.mdx b/content/nomad/v1.1.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..0ddd3e72ab
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/java.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /docs/drivers/java#default_ipc_mode
+[cap_add]: /docs/drivers/java#cap_add
+[cap_drop]: /docs/drivers/java#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.1.x/content/docs/drivers/podman.mdx b/content/nomad/v1.1.x/content/docs/drivers/podman.mdx
new file mode 100644
index 0000000000..d172c76297
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/podman.mdx
@@ -0,0 +1,264 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+See the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be [downloaded][downloaded] onto the client host
+in the configured plugin directory.
+
+- Linux host with [`podman`][podman] installed.
+- [`nomad-driver-podman`][releases] binary in Nomad's [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Known Limitations
+
+The Podman task driver is under active development. It currently does not support [stderr logging][stderr-logging] and [devices][devices].
+
+## Task Configuration
+
+Due to Podman's similarity to Docker, the example job created by [`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+- `image` - The image to run.
+
+```hcl
+config {
+  image = "docker://redis"
+}
+```
+
+- `command` - (Optional) The command to run when starting the container.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  _command_ is specified, the arguments are passed directly to the container.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths.
+
+```hcl
+config {
+  volumes = [
+    "/some/host/data:/container/data"
+  ]
+}
+```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for tmpfs mount
+  points. See `podman run --tmpfs` options for details.
+
+```hcl
+config {
+  tmpfs = [
+    "/var"
+  ]
+}
+```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using count) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - Run an init inside the container that forwards signals and reaps processes.
+
+```hcl
+config {
+  init = true
+}
+```
+
+- `init_path` - Path to the container-init binary.
+
+```hcl
+config {
+  init = true
+  init_path = "/usr/libexec/podman/catatonit"
+}
+```
+
+- `user` - Run the command as a specific user/uid within the container. See
+  [task configuration][task].
+
+- `memory_reservation` - Memory soft limit (unit = b (bytes), k (kilobytes), m
+  (megabytes), or g (gigabytes))
+
+After setting memory reservation, when the system detects memory contention or
+low memory, containers are forced to restrict their consumption to their
+reservation. So you should always set the value below --memory, otherwise the
+hard limit will take precedence. By default, memory reservation will be the
+same as memory limit.
+
+```hcl
+config {
+  memory_reservation = "100m"
+}
+```
+
+- `memory_swap` - A limit value equal to memory plus swap. The swap limit
+  should always be larger than the [memory value][memory-value].
+
+Unit can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you
+don't specify a unit, b is used. Set LIMIT to -1 to enable unlimited swap.
+
+```hcl
+config {
+  memory_swap = "180m"
+}
+```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between 0 and 100.
+
+```hcl
+config {
+  memory_swappiness = 60
+}
+```
+
+- `network_mode` - Set the [network mode][network-mode] for the container. This will be
+  overridden by nomad if a group network is created and passed in by Nomad.
+
+  - `bridge` - (default for rootful) create a network stack on the default bridge
+  - `none` - no networking
+  - `container:id` - reuse another container's network stack
+  - `host` - use the Podman host network stack. Note: the host mode gives the container
+    full access to local system services such as D-bus and is therefore considered insecure.
+  - `slirp4netns` - use `slirp4netns` to create a user network stack. This is the default for
+    rootless containers. Podman currently does not support this option for rootful containers ([issue][slirp-issue])
+
+## Networking
+
+Podman supports forwarding and exposing ports like Docker. See [Docker Driver
+configuration][docker-ports] for details.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `volumes` stanza:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+  }
+}
+```
+
+- `gc` stanza:
+
+  - `container` - Defaults to `true`. This option can be used to disable
+    Nomad from removing a container when the task exits.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously managed containers
+  will be reused instead of disposed and recreated.
+
+```hcl
+plugin "nomad-driver-podman" {
+  config {
+    recover_stopped = false
+  }
+}
+```
+
+[docker-ports]: /docs/drivers/docker#forwarding-and-exposing-ports
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /docs/job-specification/resources#memory
+[nomad-init]: /docs/commands/job/init
+[plugin_dir]: /docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[task]: /docs/job-specification/task#user
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[stderr-logging]: https://github.com/hashicorp/nomad-driver-podman/issues/4
+[devices]: https://github.com/hashicorp/nomad-driver-podman/issues/41
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
diff --git a/content/nomad/v1.1.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.1.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..c18683a42d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,179 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. (Note that
+  [prior to qemu 2.10.1](https://github.com/qemu/qemu/commit/ad9579aaa16d5b385922d49edac2c96c79bcfb6),
+  the monitor socket path is limited to 108 characters. Graceful shutdown will
+  be disabled if QEMU is < 2.10.1 and the generated monitor path exceeds this
+  length. You may encounter this issue if you set long
+  [data_dir](/docs/configuration#data_dir)
+  or
+  [alloc_dir](/docs/configuration/client#alloc_dir)
+  paths.) This feature is currently not supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.1.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.1.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..6087c93ca1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin stanza:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin stanza][plugin-stanza] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-stanza]: /docs/configuration/plugin
diff --git a/content/nomad/v1.1.x/content/docs/drivers/remote/ecs.mdx b/content/nomad/v1.1.x/content/docs/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..90ece68900
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` stanza defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.1.x/content/docs/drivers/remote/index.mdx b/content/nomad/v1.1.x/content/docs/drivers/remote/index.mdx
new file mode 100644
index 0000000000..29b0166861
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] stanza has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` stanza and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] stanza:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]:  /docs/job-specification/artifact
+[connect]: /docs/job-specification/connect
+[dispatch-payload]: /docs/job-specification/dispatch_payload
+[drain]: /docs/commands/node/drain
+[ephemeral-disk]: /docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /docs/job-specification/network
+[remote-cap]: /docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /docs/job-specification/resources
+[task-config]: /docs/job-specification/task#config
+[template]: /docs/job-specification/template
+[upgrade]: /docs/upgrade/upgrade-specific
+[vault]: /docs/job-specification/vault
+[volume]: /docs/job-specification/volume
diff --git a/content/nomad/v1.1.x/content/docs/ecosystem.mdx b/content/nomad/v1.1.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..64fb68880d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/ecosystem.mdx
@@ -0,0 +1,199 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+### Continuous Integration & Delivery
+
+#### GitLab
+
+https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations
+
+#### Codefresh
+
+https://codefresh.io/docs/docs/yaml-examples/examples/nomad/
+
+#### CircleCI
+
+https://circleci.com/docs/2.0/nomad/
+
+#### Drone
+
+https://docs.drone.io/runner/nomad/overview/
+
+#### Jenkins
+
+https://plugins.jenkins.io/nomad/
+
+#### Buildkite
+
+https://buildkite.com/works-with/hashicorp
+
+### Container Runtime
+
+#### Containerd
+
+https://www.nomadproject.io/docs/drivers/external/containerd
+
+#### Windows IIS
+
+https://github.com/Roblox/nomad-driver-iis
+
+#### Jailtask
+
+https://www.nomadproject.io/docs/drivers/external/jail-task-driver
+
+#### Pot
+
+https://github.com/trivago/nomad-pot-driver
+
+#### Singularity
+
+https://www.nomadproject.io/docs/drivers/external/singularity
+
+#### Firecracker
+
+https://www.nomadproject.io/docs/drivers/external/firecracker-task-driver
+
+#### Podman
+
+https://www.nomadproject.io/docs/drivers/podman
+
+#### LXC
+
+https://www.nomadproject.io/docs/drivers/external/lxc
+
+### Application Definition & Image Build
+
+#### Levant
+
+https://github.com/hashicorp/levant
+
+#### Packer
+
+https://www.packer.io/
+
+#### Waypoint
+
+https://learn.hashicorp.com/collections/waypoint/get-started-nomad
+
+### Container Registry
+
+#### JFrog Artifactory
+
+https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/
+
+### Observability and Analysis
+
+#### Prometheus
+
+https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics
+
+https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing?in=nomad/nomad-1-0#start-prometheus
+
+#### Grafana
+
+https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/
+
+#### DataDog
+
+https://docs.datadoghq.com/integrations/nomad/
+
+#### Turbonomics
+
+https://www.youtube.com/watch?v=lwtIaPpdDsc
+
+#### Circonus
+
+https://www.hashicorp.com/integrations/circonus/nomad
+
+#### Flowmill
+
+https://www.flowmill.com/blog/announcing-flowmill-s-integration-with-nomad/
+
+#### Sematext
+
+https://www.hashicorp.com/integrations/sematext/nomad
+
+#### Splunk
+
+https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/
+
+### Secret Management
+
+#### Vault
+
+https://www.nomadproject.io/docs/integrations/vault-integration
+
+### Service Mesh
+
+#### Consul
+
+https://www.nomadproject.io/docs/integrations/consul-integration
+
+### Provisioning
+
+#### Terraform
+
+https://registry.terraform.io/providers/hashicorp/nomad/latest/docs
+
+#### Chef
+
+https://github.com/nathwill/chef-nomad
+
+#### Ansible
+
+https://github.com/ansible-community/ansible-nomad
+
+### Cloud Native Network
+
+#### CNI
+
+https://www.nomadproject.io/docs/integrations/consul-connect#cni-plugins
+
+### Service Proxy
+
+#### Envoy
+
+https://www.nomadproject.io/docs/integrations/consul-connect
+
+#### NGINX
+
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx
+
+#### Traefik
+
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik
+
+### Storage
+
+#### CSI
+
+https://www.nomadproject.io/docs/concepts/plugins/csi
+
+#### Portworx
+
+https://www.hashicorp.com/integrations/portworx/nomad
+
+### GPUs
+
+#### NVIDIA
+
+https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/
+
+https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad
+
+### Autoscaling
+
+#### AWS ASGs
+
+Dynamically autoscale your Nomad clusters
+
+https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler
+
+#### Spot
+
+https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/
diff --git a/content/nomad/v1.1.x/content/docs/enterprise/index.mdx b/content/nomad/v1.1.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..9a730cdefe
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,178 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](https://learn.hashicorp.com/tutorials/nomad/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/docs/commands/operator/snapshot-agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](https://learn.hashicorp.com/tutorials/nomad/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](https://learn.hashicorp.com/tutorials/nomad/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](https://learn.hashicorp.com/tutorials/nomad/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies
+Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel) for a thorough
+overview.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /docs/job-specification/multiregion
+[autoscaling capabilities]: /docs/autoscaling
+[scaling policies]: /docs/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
diff --git a/content/nomad/v1.1.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.1.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..faac9b88fd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.1.0+ent. 
+Nomad Enterprise automatically load Nomad licenses when a Nomad server agent starts using Nomad Enterprise.
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.1.0, the license enablement process is different.
+
+HashiCorp Enterprise servers will no longer start without a license. When the server instance initializes the license watcher, the server reads from either an environment variable or file. If the license is missing, invalid, or expired, the server will immediately exit. 
+This check is part of the server boot-up process.
+
+In previous versions of HashiCorp enterprise products, one server could distribute a license to other servers via the Raft protocol. 
+This will no longer work since each server must be able to find a valid license during the startup process.
+
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about the license changes introduced in Nomad Enterprise v1.1.0
+
+- [v1.1.0 Upgrade Guide](https://www.nomadproject.io/docs/upgrade/upgrade-specific#enterprise-licenses)
+
+- [Nomad License Documentation](https://www.nomadproject.io/docs/enterprise/license)
+
+- [License configuration values documentation](https://www.nomadproject.io/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license)
+
+## Q: Does this affect Nomad or older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.1.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you follow the steps in the [upgrade guide](https://www.nomadproject.io/docs/upgrade/upgrade-specific#enterprise-licenses), but have misconfigured the licensing steps, the server instances will stop during boot-up sequence. 
+
+If you do not check cluster health after adding new servers, and verify that the new servers have joined properly, then you may accidentally take down old servers without replacing them.
+
+If you are using a trial license in production, this could cause issues as the cluster will fail to start once the trial expires.
+
+If you have built automation around `nomad license put`, this command will fail as it has been removed from Nomad v1.1.0+.
+
+## Q: What are some other gotchas?
+
+You might not have access to your organization's Nomad license. 
+The  6-hour temporary license window is now removed, and a license is required for proper boot-up.
+Running `nomad agent -dev` without a license will fail.
+
+
+## Q: How can a user get their existing license to put on disk for an upgrade?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself. 
+
+## Q: What happens when a license expires?
+If a license expires after a server node joins the cluster, the existing Enterprise features will continue to operate until a grace period expires. 
+The grace period duration is 1 day, and upon the end of the grace period the Nomad servers will shut down. 
+
+## Q: Will on-prem binaries with “baked-in” licenses work?
+
+There is no impact to baked-in licensed binaries.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Visit https://nomadproject.io/trial for a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.1.0 to an earlier version?
+
+Nomad cannot safely be rolled back to an earlier version. 
+This is not a supported operation due to the Nomad state store not having forward compatibility. The end result could be a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license).
diff --git a/content/nomad/v1.1.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.1.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..7536e61c87
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have its own license. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](https://nomadproject.io/trial) to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Expiring Licenses
+
+Nomad Enterprise license have an expiration time. You can read the license on
+a server with the `nomad license get` command:
+
+```
+$ nomad license get
+Product        = nomad
+License Status = valid
+License ID     = eaaecbd5-b598-4fa4-b649-bb234bf49fa3
+Customer ID    = ae94bdd0-39bf-4c58-bf80-8a9468b0467c
+Issued At      = 2021-03-29 14:47:29.024191 -0400 EDT
+Expires At     = 2021-03-29 20:47:29.024191 -0400 EDT
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+        Dynamic Application Sizing
+```
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+Note that if the server is restarted with an expired license, it will
+immediately stop.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license?in=nomad/enterprise) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /docs/configuration/server#license_path
+[license endpoint]: /api-docs/operator/license#updating-the-nomad-enterprise-license
\ No newline at end of file
diff --git a/content/nomad/v1.1.x/content/docs/faq.mdx b/content/nomad/v1.1.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..1ac0743922
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/docs/concepts/consensus) and
+a [gossip protocol](/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: https://www.consul.io/docs/agent/options#_datacenter
+[consul_fed]: https://learn.hashicorp.com/tutorials/consul/federarion-gossip-wan
+[nomad_region]: /docs/configuration#datacenter
+[`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.1.x/content/docs/index.mdx b/content/nomad/v1.1.x/content/docs/index.mdx
new file mode 100644
index 0000000000..0fad01e91f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. This documentation is more of a reference
+  guide for all available features and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [HashiCorp Learn "Getting Started" collection][gs]
+instead.
+
+[gs]: https://learn.hashicorp.com/collections/nomad/get-started
diff --git a/content/nomad/v1.1.x/content/docs/install/index.mdx b/content/nomad/v1.1.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..cc74132045
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/install/index.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation">
+
+You can download a [precompiled binary](/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+You can check the locations available on your path by running this command.
+
+```shell-session
+$ echo $PATH
+
+/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
+```
+
+The output is a list of locations separated by colons. You can make Nomad
+available by moving the binary to one of the listed locations, or by adding
+Nomad's location to your `PATH`.
+
+-> **Tip (Linux-based or Mac):** Permanently add a new location to your path by
+editing your shell's settings file (usually called something like `~/.bashrc`,
+where the part of the file name after the `.` and before `rc` is the name of
+your shell). In that file you will see a line that starts with `export PATH=`,
+followed by a colon-separated list of locations. Add the location of the Nomad
+binary to that list and save the file. Then reload your shell's configuration
+with the command `source ~/.bashrc`, replacing `bash` with the name of your
+shell.
+
+-> **Tip (Windows):** Add a location to your path via the GUI by navigating to
+`Environment Variables` in your system settings, and looking for the variable
+called `PATH`. You will see a semicolon-separated list of locations. Add the
+Nomad binary's location to that list and then launch a new console window.
+
+</Tab>
+<Tab heading="Linux Packages">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](https://learn.hashicorp.com/consul) and
+[Vault](https://learn.hashicorp.com/vault) with the same command.
+
+</Tab>
+<Tab heading="Homebrew (macOS)">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey (Windows)">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+</Tabs>
+
+---
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+[consul-download]: https://www.consul.io/downloads
+[destroy]: https://www.vagrantup.com/docs/cli/destroy
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+[gpg-key]: https://apt.releases.hashicorp.com/gpg 'HashiCorp GPG key'
diff --git a/content/nomad/v1.1.x/content/docs/install/production/index.mdx b/content/nomad/v1.1.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..a0fb3b9ecc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/docs/install/production/nomad-agent)
+and [Nomad Agent documentation](/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.1.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.1.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..738441b457
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+## Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some
+task driver engines. Nomad clients require `CAP_NET_ADMIN` for a variety of
+tasks to set up networking. You should run Nomad as `root`, but running as
+`root` does not grant these required capabilities if Nomad is running in a
+user namespace. Running Nomad clients inside a user namespace is
+unsupported. See the [`capabilities(7)`] man page for details on Linux
+capabilities.
+
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
diff --git a/content/nomad/v1.1.x/content/docs/install/quickstart.mdx b/content/nomad/v1.1.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..206433dfd3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via Learn guides containing embedded Katacoda interactive learning environments.
+
+- [Interactive Labs](https://learn.hashicorp.com/collections/nomad/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](https://www.vagrantup.com/docs/installation/). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /docs/install#precompiled-binaries
+[vagrant-environment]: https://learn.hashicorp.com/tutorials/nomad/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.1.x/content/docs/install/windows-service.mdx b/content/nomad/v1.1.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..94a569de94
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /downloads
+[logging]: /docs/configuration#log_file
diff --git a/content/nomad/v1.1.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.1.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..f53e9b04d3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Consul Connect
+description: >-
+  Learn how to use Nomad with Consul Connect to enable secure service to service
+  communication
+---
+
+# Consul Connect
+
+~> **Note:** This guide requires Nomad 0.10.0 or later and Consul 1.6.0 or
+later.
+
+~> **Note:** Nomad's Connect integration requires Linux network namespaces.
+Nomad Connect will not run on Windows or macOS.
+
+[Consul Connect](https://www.consul.io/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of Connect at all.
+
+# Nomad with Consul Connect Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. In order to support Consul Connect, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into Connect integration. When Connect is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul Connect integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in Connect continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul Connect integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+# Nomad Consul Connect Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+Connect integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+**Note**: Nomad's Connect integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use Connect on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Connect.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul Connect sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v0.9.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v0.9.0.tgz
+$ sudo mkdir -p /opt/cni/bin
+$ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Connect-enabled Services
+
+Once Nomad and Consul are running, submit the following Connect-enabled services
+to Nomad by copying the HCL into a file named `connect.nomad` and running:
+`nomad run connect.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul Connect, it does not define
+any ports in its network. The service stanza enables Connect:
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service stanza is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul Connect:
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` stanza defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul Connect using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+[count-dashboard]: /img/count-dashboard.png
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
diff --git a/content/nomad/v1.1.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.1.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..9b90999be6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](https://learn.hashicorp.com/tutorials/nomad/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` stanza](/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template stanza and how it leverages Consul Template,
+please see the [`template` job specification documentation](/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_acls]: https://www.consul.io/docs/security/acl
+[consul_namespaces]: https://www.consul.io/docs/enterprise/namespaces
+[consul_agent_namespace]: /docs/configuration/consul#namespace
+[consul_group_namespace]: /docs/job-specification/group#namespace
+[consul_run_namespace]: /docs/commands/job/run#consul-namespace
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/integrations/index.mdx b/content/nomad/v1.1.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.1.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.1.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..aecfc383e4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,472 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](https://www.vaultproject.io/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The token can then be set in the server configuration's
+[`vault` stanza][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` stanza of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To Submit this job a token that has the `access-kv` policy in the Namespace `engineering`
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: https://www.vaultproject.io/docs/auth/token 'Vault Authentication Backend'
+[config]: /docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: https://www.vaultproject.io/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: https://www.vaultproject.io/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.1.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..2eac4bf8b6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Stanza - Job Specification
+description: |-
+  The "affinity" stanza allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Stanza
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` stanza allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 5
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task stanzas as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` stanzas. Remember that the
+`affinity` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` stanza matches the node.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.1.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..a87b46e3d2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: artifact Stanza - Job Specification
+description: |-
+  The "artifact" stanza instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Stanza
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` stanza instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` stanzas. Remember that the
+`artifact` stanza is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](https://www.nomadproject.io/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the Nomad user's known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /root/.ssh/known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file(pathexpand("~/.ssh/id_rsa")))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[client_artifact]: /docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/check.mdx b/content/nomad/v1.1.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..2df795025a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,363 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a Consul service.
+---
+
+# `check` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+from the Consul service provider.
+
+```hcl
+job "job" {
+  group "group" {
+    task "task " {
+      service {
+        check {
+          type     = "tcp"
+          port     = 6379
+          interval = "10s"
+          timeout  = "2s"
+        }
+        # ...
+      }
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` stanza][check_restart_stanza].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`][type] must be `http` or `grpc`, and check `name` must be set.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] stanza. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` stanzas will apply to the specified task. For `checks` on group
+  level `services` only. Inherits the [`service.task`][service_task] value if not
+  set. May only be set for script or gRPC checks.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_stanza] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Stanza
+
+HTTP checks may include a `header` stanza to set HTTP headers. The `header`
+stanza parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] stanza. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness vs. Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_stanza]: /docs/job-specification/check_restart
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[service]: /docs/job-specification/service
+[service_task]: /docs/job-specification/service#task-1
+[on_update]: /docs/job-specification/service#on_update
\ No newline at end of file
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.1.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..4708bfabb4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: check_restart Stanza - Job Specification
+description: |-
+  The "check_restart" stanza instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` stanza instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` stanza, it is
+restarted according to the task group's [`restart` policy][restart_stanza]. The
+`check_restart` settings apply to [`check`s][check_stanza], but may also be
+placed on [`service`s][service_stanza] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the stanzas are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_stanza] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` stanza][restart_stanza] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` stanza][restart_stanza] for
+details.
+
+[check_stanza]: /docs/job-specification/service#check-parameters 'check stanza'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[service_stanza]: /docs/job-specification/service 'service stanza'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.1.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..7339322398
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: connect Stanza - Job Specification
+description: The "connect" stanza allows specifying options for Consul Connect integration
+---
+
+# `connect` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` stanza allows configuring various options for
+[Consul Connect](/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](https://www.consul.io/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service stanza for a
+[Consul Connect Native](https://www.consul.io/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect stanza with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service stanza for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[native]: https://www.consul.io/docs/connect/native
+[service_task]: /docs/job-specification/service#task-1 'Nomad service task'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.1.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..5ddc7d6805
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,317 @@
+---
+layout: docs
+page_title: constraint Stanza - Job Specification
+description: |-
+  The "constraint" stanza allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Stanza
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` stanzas. Remember that the
+`constraint` stanza is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.1.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..46633d5644
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: csi_plugin Stanza - Job Specification
+description: >-
+  The "csi_plugin" stanza allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Stanza
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" stanza allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id             = "csi-hostpath"
+  type           = "monolith"
+  mount_dir      = "/csi"
+  health_timeout = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <required>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad.
+
+- `health_timeout` `(duration: <optional>)` - The duration that 
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set. 
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. You should run `node` or `monolith` plugins as
+  [`system`][system] jobs and use the `-ignore-system` flag on `nomad
+  node drain` to ensure that the plugins are running while the node is
+  being drained.
+
+* Only one plugin instance of a given plugin ID and type (controller or node)
+  should be deployed on any given client node. Use a constraint as shown
+  below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount volumes only
+  within the same Availability Zone. You should deploy these plugins with a
+  unique-per-AZ `plugin_id` to allow Nomad to place allocations in the correct
+  AZ.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /docs/job-specification/volume
+[system]: /docs/schedulers#system
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/device.mdx b/content/nomad/v1.1.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..6a975a390d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,303 @@
+---
+layout: docs
+page_title: device Stanza - Job Specification
+description: |-
+  The "device" stanza is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` stanza is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` stanza is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` stanza
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` stanza can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` stanzas. Remember that the
+`device` stanza is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.1.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..4d719a9b41
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: dispatch_payload Stanza - Job Specification
+description: |-
+  The "dispatch_payload" stanza allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Stanza
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` stanza is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` stanza. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` stanzas. Remember that the
+`dispatch_payload` stanza is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/env.mdx b/content/nomad/v1.1.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..d849fe7d4b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: env Stanza - Job Specification
+description: |-
+  The "env" stanza configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Stanza
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` stanza configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` stanzas. Remember that the
+`env` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` stanza][template-env].
+
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /docs/job-specification/template#environment-variables 'Nomad template Stanza'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.1.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..1ebc196274
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: ephemeral_disk Stanza - Job Specification
+description: |-
+  The "ephemeral_disk" stanza describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Stanza
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` stanza describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be
+  removed if an error is encountered.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` stanzas. Remember that the
+`ephemeral_disk` stanza is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.1.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..17fe8b47cd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Stanza - Job Specification
+description: |-
+  The "expose" stanza allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` stanza allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` stanza.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` stanza. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+stanza can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /docs/job-specification/network#to
+[consul-expose-path-config]: https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /docs/job-specification/expose#path-1
+[expose]: /docs/job-specification/service#expose
+[path]: /docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /docs/configuration/client#network_interface
+[learn-consul-connect]: https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh
+[check]: /docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.1.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..f66719d0ec
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,650 @@
+---
+layout: docs
+page_title: gateway Stanza - Job Specification
+description: |-
+  The "gateway" stanza allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` stanza allows configuration of [Consul Connect Gateways](https://www.consul.io/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](https://www.consul.io/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` stanza.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](https://www.consul.io/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](https://www.consul.io/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx?in=nomad/load-balancing)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress` or `terminating` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. Either
+  `tcp` or `http`.
+
+  ~> **Note:** If using `http`, preconfiguring a [service-default] in Consul to
+  set the [Protocol](https://www.consul.io/docs/agent/config-entries/service-defaults#protocol)
+  of the service to `http` is recommended.
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+  ~> **Note:** If a well-known port is not used, i.e. a port other than 80 (http) or 443 (https),
+  then the port must be appended to the host to correctly match traffic. This is
+  defined in the [HTTP/1.1 RFC](https://tools.ietf.org/html/rfc2616#section-14.23).
+  If TLS is enabled, then the host **without** the port must be added to the `hosts`
+  field as well. TLS verification only matches against the hostname of the incoming
+  connection, and does not take into account the port.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+  The `mesh` block currently does not have any configurable parameters.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] stanza.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /docs/job-specification/gateway#address-parameters
+[advanced configuration]: https://www.consul.io/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: https://www.consul.io/docs/agent/config-entries/service-resolver#connecttimeout
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /docs/job-specification/gateway#ingress-parameters
+[proxy]: /docs/job-specification/gateway#proxy-parameters
+[linked-service]: /docs/job-specification/gateway#service-parameters-1
+[listener]: /docs/job-specification/gateway#listener-parameters
+[service]: /docs/job-specification/gateway#service-parameters
+[service-default]: https://www.consul.io/docs/agent/config-entries/service-defaults
+[sidecar_task]: /docs/job-specification/sidecar_task
+[terminating]: /docs/job-specification/gateway#terminating-parameters
+[tls]: /docs/job-specification/gateway#tls-parameters
+[mesh]: /docs/job-specification/gateway#mesh-parameters
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/group.mdx b/content/nomad/v1.1.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..488f3f062b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,276 @@
+---
+layout: docs
+page_title: group Stanza - Job Specification
+description: |-
+  The "group" stanza defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Stanza
+
+<Placement groups={['job', 'group']} />
+
+The `group` stanza defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate stanzas.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart stanza documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul](/docs/configuration/consul) for service discovery.
+  Nomad automatically registers each service when an allocation
+  is started and de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul deregistration
+  and sending each task a shutdown signal. Ideally, services would fail
+  healthchecks once they receive a shutdown signal. Alternatively
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group services. In addition, tasks may have their
+  own [`shutdown_delay`](/docs/job-specification/task#shutdown_delay)
+  which waits between deregistering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration
+  after which a Nomad client that cannot communicate with the servers
+  will stop allocations based on this task group. By default, a client
+  will not stop an allocation until explicitly told to by a server. A
+  client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be
+  marked "lost" and Nomad will schedule replacement
+  allocations. However, these replaced allocations will continue to
+  run on the non-responsive client; an operator may desire that these
+  replaced allocations are also stopped in this case — for example,
+  allocations requiring exclusive access to an external resource. When
+  specified, the Nomad client will stop them after this duration. The
+  Nomad client process must be running for this to occur.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` stanzas. Remember that the
+`group` stanza is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] stanza
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other stanzas. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /docs/job-specification/group#consul-parameters
+[consul_namespace]: /docs/commands/job/run#consul-namespace
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /docs/configuration/server#heartbeat_grace
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..1fa000403c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,413 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or `key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+service {
+  port = "db" # can use expressions here
+
+  check {
+    # but the "check" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `check` using a
+special `dynamic` block type, which is supported anywhere, example:
+
+```hcl
+locals {
+  check_paths = ["/health", "/"]
+}
+
+job "example" {
+  # ...
+  service {
+    port = "lb" # can use expressions here
+
+    dynamic "check" {
+      for_each = local.check_paths
+
+      content {
+        type     = "http"
+        port     = "lb"
+        path     = check.value
+      }
+    }
+ }
+}
+```
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"check"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"check"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`check` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..ed8e3d4ebb
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..0e029eeae8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..786b0caa29
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..4c3d2372ee
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..7ab7753196
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..317853e691
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..70aa9ff1b8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection or string.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or string.
+
+If given a list or map, the result is the number of elements in that collection.
+If given a string, the result is the number of characters in the string.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..472a46cde5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..bb911e06e1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..e1ce175036
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..d74ec56925
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6c74de4758
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..c410370cc8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..67a3022ffc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..649bf5a191
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ca6a5a227e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..24e760c922
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..d41281f49f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..b54db11df1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..a9a70ae3fc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5bea54c6af
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..ac4d0f9be0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..4b86120885
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..d46f784114
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..7df718807b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..a1561575e5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..479598a397
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..3045ba62d0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+## Related Functions
+
+- [`fileexists`](/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..4c569e0577
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..32660de8c3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..b590d24576
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..2975376b5d
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..62241b2f89
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..1528f29673
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..d90e6ce35b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..7d0a4279b9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..d56ad71f78
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..361e4ef0c8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..83e0a662f2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..14850d2f88
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..97b1b2eeac
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..80ad67c306
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..e97a48508f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..0eec2f9b6e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W)
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..9b9f2eb374
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..c456bd76d9
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..fad64d44a6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..5b8efdf95b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..7a1af15367
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..f5fa82b049
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..904a98f921
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..ca8e610629
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..1be5e3d817
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..9586e352fe
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..ff63c13581
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..53d10bad25
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /api-docs/json-jobs
+[run-json]: /docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/docs/job-specification/hcl2/syntax)
+- [Expressions](/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/docs/job-specification/meta), and
+[`env`](/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpf_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..90c23d0079
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..ec80fe394e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..943e41be6f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are often referred to as just
+"variables" or "Nomad variables" when it is clear from context what sort of
+variable is being discussed. Other kinds of variables in Nomad include
+_environment variables_ (set by the shell where Nomad runs) and _expression
+variables_ (used to indirectly represent a value in an
+[expression](/docs/job-specification/hcl2/expressions)).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](https://www.terraform.io/docs/configuration/types.html).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/index.mdx b/content/nomad/v1.1.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..b9bbef6134
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+stanza. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` stanza can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+stanza specified at the group level must include a [connect][] stanza, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /docs/job-specification/connect 'Connect Stanza Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/job.mdx b/content/nomad/v1.1.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..a154938507
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: job Stanza - Job Specification
+description: |-
+  The "job" stanza is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Stanza
+
+<Placement groups={['job']} />
+
+The `job` stanza is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate stanzas.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system` and `batch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] stanza. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` stanzas. Remember that the
+`job` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: https://learn.hashicorp.com/tutorials/nomad/federation
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /docs/schedulers 'Nomad Scheduler Types'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.1.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..ffb455da91
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Stanza - Job Specification
+description: |-
+  The "lifecycle" stanza configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Stanza
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` stanza is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` stanza. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: https://learn.hashicorp.com/collections/nomad/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/docs/job-specification/template) or
+[`artifact`](/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.1.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..c33aae0652
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: logs Stanza - Job Specification
+description: |-
+  The "logs" stanza configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" stanza
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Stanza
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` stanza configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` stanza allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` stanzas. Remember that the
+`logs` stanza is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /docs/commands/alloc/logs 'Nomad logs command'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.1.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..4f108dfb99
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: meta Stanza - Job Specification
+description: The "meta" stanza allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Stanza
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` stanza allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` stanza at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+## `meta` Parameters
+
+The "parameters" for the `meta` stanza can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings.
+
+## `meta` Examples
+
+The following examples only show the `meta` stanzas. Remember that the
+`meta` stanza is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.1.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..b75e4c921e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Stanza - Job Specification
+description: |-
+  The "migrate" stanza specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Stanza
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` stanza specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+stanzas.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+stanza for allocations on that node. The `migrate` stanza is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /docs/job-specification/service#check-parameters
+[count]: /docs/job-specification/group#count
+[drain]: /docs/commands/node/drain
+[deadline]: /docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.1.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..998f6e0f58
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,266 @@
+---
+layout: docs
+page_title: multiregion Stanza - Job Specification
+description: |-
+  The "multiregion" stanza specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Stanza
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` stanza specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region
+— the one specified by the `region` field or the `-region` command line
+flag to `nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` stanza. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` stanza.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+stanza has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` stanza] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` stanza (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the the
+[`update` stanza] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta stanza allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta stanza at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` stanza and the other
+stanzas it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` stanza with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
+[`update` stanza]: /docs/job-specification/update
+[update-auto-revert]: /docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: https://learn.hashicorp.com/collections/nomad/job-updates
+[`nomad deployment unblock`]: /docs/commands/deployment/unblock
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/network.mdx b/content/nomad/v1.1.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..d93fb46ff2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,298 @@
+---
+layout: docs
+page_title: network Stanza - Job Specification
+description: |-
+  The "network" stanza specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Stanza
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` stanza specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+When the `network` stanza is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+  for the allocations. By default all DNS configuration is inherited from the client host.
+  DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+## `network` Examples
+
+The following examples only show the `network` stanzas. Remember that the
+`network` stanza is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network stanza that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network stanza could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port stanzas.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` stanza can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.1.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..8cd48cbac6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: parameterized Stanza - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` stanza is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Stanza
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+stanza is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` stanza allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] stanza that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.1.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..3329bead0f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: periodic Stanza - Job Specification
+description: |-
+  The "periodic" stanza allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Stanza
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` stanza allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` stanzas. Remember that the
+`periodic` stanza is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.1.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..3bda4c0bcc
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: proxy Stanza - Job Specification
+description: |-
+  The "proxy" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Stanza
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` stanza allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](https://www.consul.io/docs/connect/proxies/envoy#dynamic-configuration)
+  for details.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.1.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..cbcb6a5a91
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: reschedule Stanza - Job Specification
+description: >-
+  The "reschedule" stanza specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Stanza
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` stanza specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule stanza is present on both the job and the group, they are merged with
+the group stanza taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the task on another node if any of its allocation
+statuses become "failed". It prefers to create a replacement allocation on a node
+that hasn't previously been used.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule stanza does not apply to `system` jobs because they run on
+every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.1.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..d006a5407a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: resources Stanza - Job Specification
+description: |-
+  The "resources" stanza describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Stanza
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` stanza describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Specifies the number of CPU cores to reserve
+  for the task. This may not be used with `cpu`.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Optionally, specifies the maximum memory the task may use, if the client has excess memory capacity, in MB. See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` stanzas. Remember that the
+`resources` stanza is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this stanza, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource stanza, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] stanza
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad 1.1. lets job authors set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The new max limit attribute is currently supported by the official `docker`,
+`exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory Oversubscription in the scheduler
+configuration](/api-docs/operator/scheduler#update-scheduler-configuration). Enterprise customers can use [Resource
+Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas) to limit the memory
+oversubscription.
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[device]: /docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.1.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..25128302cf
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: restart Stanza - Job Specification
+description: The "restart" stanza configures a group's behavior on task failure.
+---
+
+# `restart` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` stanza configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] stanza.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /docs/job-specification/sidecar_task
+[`reschedule`]: /docs/job-specification/reschedule
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.1.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..6702178ba3
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: scaling Stanza - Job Specification
+description: The "scaling" stanza allows specifying scaling policy for a task group
+---
+
+# `scaling` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+  ]}
+/>
+
+The `scaling` stanza allows configuring scaling options for a task group, for the purpose
+of supporting external autoscalers like the [Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler)
+and scaling via the Nomad UI. This stanza is not supported within jobs of type `system`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+      }
+    }
+    scaling {
+      enabled = true
+      min = 0
+      max = 10
+      policy {
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [count][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; see autoscaler documentation.
+
+[count]: /docs/job-specification/group#count 'Nomad Task Group specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/service.mdx b/content/nomad/v1.1.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..27cd330a1e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,490 @@
+---
+layout: docs
+page_title: service Stanza - Job Specification
+description: |-
+  The "service" stanza instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Stanza
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` stanza instructs Nomad to register a service with Consul. This
+section of the documentation will discuss the configuration, but please also
+read the [Nomad service discovery documentation][service-discovery] for more
+detailed information about the integration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and stanzas
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` stanza at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. Only available where
+  `provider = "consul"`. At this time, the Consul integration supports the `grpc`,
+  `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network stanza.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker or rkt).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] stanza.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](https://www.consul.io/docs/concepts/anti-entropy#enable-tag-override)
+  for more information.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. This setting is supported in
+  Docker since Nomad 0.6 and rkt since Nomad 0.7. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker and rkt. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_stanza] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with Consul. It
+is important to understand when each of these steps happens and how they can be
+customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in Consul as well. Consul is updated without restarting a task.
+
+**Deregistering**: If a running task with a service stanza exits, the services
+and checks are immediately deregistered from Consul without delay. If however
+Nomad needs to kill a running task, the task is killed in the following order:
+
+1. Immediately remove the services and checks from Consul. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in Consul, and
+   thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` stanzas. Remember that the
+`service` stanza is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks.
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+This example must be accompanied by a [`network`][network] stanza which defines
+a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/docs/drivers/docker#network_mode) and
+[rkt](/docs/drivers/rkt#net) drivers support the `driver` setting for the
+`address_mode` parameter in both `service` and `check` stanzas. The driver
+address mode allows advertising and health checking the IP and port assigned to
+a task by the driver. This way, if you're using a network plugin like Weave with
+Docker, you can advertise the Weave address in Consul instead of the host's
+address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than "host" or "bridge" is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` stanzas default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` stanza's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` stanzas can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` stanza to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` stanzas can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /docs/job-specification/check
+[check_restart_stanza]: /docs/job-specification/check_restart
+[consul_grpc]: https://www.consul.io/api/agent/check#grpc
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[service-discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_stanza]: /docs/job-specification/restart 'restart stanza'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /docs/job-specification/service#type
+[shutdowndelay]: /docs/job-specification/task#shutdown_delay
+[killsignal]: /docs/job-specification/task#kill_signal
+[killtimeout]: /docs/job-specification/task#kill_timeout
+[service_task]: /docs/job-specification/service#task-1
+[network_mode]: /docs/job-specification/network#mode
+[on_update]: /docs/job-specification/service#on_update
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.1.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..b430063710
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: sidecar_service Stanza - Job Specification
+description: |-
+  The "sidecar_service" stanza allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` stanza allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` stanza with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.1.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..452e5c2293
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: sidecar_task Stanza - Job Specification
+description: |-
+  The "sidecar_task" stanza allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Stanza
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` stanza allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] stanza.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /docs/job-specification/gateway
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.1.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..3889e56237
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Stanza - Job Specification
+description: >-
+  The "spread" stanza is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread stanza may be specified with relative weights between
+  each.
+---
+
+# `spread` Stanza
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` stanza allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread stanza. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread stanza. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread stanza. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity stanza to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` stanza.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` stanza.
+
+### Even Spread Across Data Center
+
+This example shows a spread stanza across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread stanza that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread stanza that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread stanzas with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread stanza used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/task.mdx b/content/nomad/v1.1.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..d256c67c26
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: task Stanza - Job Specification
+description: |-
+  The "task" stanza creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Stanza
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` stanza creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing it from Consul and sending it a shutdown
+  signal. Ideally services would fail healthchecks once they receive a shutdown
+  signal. Alternatively `shutdown_delay` may be set to give in flight requests
+  time to complete before shutting down. In addition, task groups may have their
+  own [`shutdown_delay`](/docs/job-specification/group#shutdown_delay)
+  which waits between deregistering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` stanzas. Remember that the
+`task` stanza is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /docs/drivers/exec 'Nomad exec Driver'
+[java]: /docs/drivers/java 'Nomad Java Driver'
+[docker]: /docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /docs/configuration/client#user-checked_drivers
+[user_denylist]: /docs/configuration/client#user-denylist
+[max_kill]: /docs/configuration/client#max_kill_timeout
+[kill_signal]: /docs/job-specification/task#kill_signal
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/template.mdx b/content/nomad/v1.1.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..4f1c2abec6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,412 @@
+---
+layout: docs
+page_title: template Stanza - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Stanza
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. Since Nomad
+v0.5.6, the template can reference [Node attributes and metadata][nodevars]. For
+a full list of the API template functions, please refer to the [Consul Template
+README][ct]. Since Nomad v0.6.0, templates can be read as environment variables.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals] documentation.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([see below](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside of a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` stanzas. Remember that the
+`template` stanza is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] stanza to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template stanza:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To workaround this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Similar to KV API v1, if the name of a secret includes the `-` character, you
+must access it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/update.mdx b/content/nomad/v1.1.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..7f60857d9a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Stanza - Job Specification
+description: |-
+  The "update" stanza specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Stanza
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` stanza specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` stanzas are specified, they are merged with the
+group stanza taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` stanza in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with CSI volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` stanzas. Remember that the
+`update` stanza is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Stanza Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update stanza, each groups update
+stanza may be kept to a minimum. The merged update stanzas for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: https://learn.hashicorp.com/collections/nomad/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.1.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..822ce3dfa7
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: upstreams Stanza - Job Specification
+description: |-
+  The "upstreams" stanza allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Stanza
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` stanza allows configuring various options for managing upstream
+services that a [Consul
+Connect](/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` stanza.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: https://www.consul.io/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: https://www.consul.io/docs/connect/gateways/mesh-gateway#mesh-gateways
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.1.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..e6ab5ac6a8
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: vault Stanza - Job Specification
+description: |-
+  The "vault" stanza allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Stanza
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` stanza allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` stanzas are specified, they are merged with the `task` stanza
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/docs/configuration/vault#namespace)
+to use [Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` stanza is specified, the [`template`][template] stanza can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` stanzas. Remember that the
+`vault` stanza is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.1.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..cff31a8dd1
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: volume Stanza - Job Specification
+description: >-
+  The "volume" stanza allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Stanza
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` stanza allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the stanza is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = "noatime"
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` stanzas. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] stanza in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `"ro,noatime"`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /docs/configuration/client#host_volume-stanza
+[csi_volume]: /docs/commands/volume/register
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume]: /docs/commands/volume/register
+[attachment mode]: /docs/commands/volume/register#attachment_mode
+[volume registration]: /docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.1.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.1.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..3a07931161
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: volume_mount Stanza - Job Specification
+description: |-
+  The "volume_mount" stanza allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Stanza
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` stanza allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /docs/job-specification/volume#volume-interpolation
+[hcl2]: /docs/job-specification/hcl2
diff --git a/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..2814bf54d6
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/docs/ecosystem).
diff --git a/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..6f8a9fdacd
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.1.x/content/docs/operations/index.mdx b/content/nomad/v1.1.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..ec2de41d9f
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/docs/operations/nomad-agent)
+- [Telemetry Overview](/docs/operations/telemetry)
+- [Metrics](/docs/operations/metrics)
+- [Cluster Management](https://learn.hashicorp.com/collections/nomad/manage-clusters)
+- [Transport Security](https://learn.hashicorp.com/collections/nomad/transport-security)
+- [Access Control](https://learn.hashicorp.com/collections/nomad/access-control)
diff --git a/content/nomad/v1.1.x/content/docs/operations/metrics.mdx b/content/nomad/v1.1.x/content/docs/operations/metrics.mdx
new file mode 100644
index 0000000000..9ceefbcf61
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/operations/metrics.mdx
@@ -0,0 +1,445 @@
+---
+layout: docs
+page_title: Metrics
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                | Unit                           | Type    |
+| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                         | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                           | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                   | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_blocked`           | Evaluations that are blocked until an existing evaluation for the same job completes                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                         | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                          | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                          | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                           | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                      | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                               | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                       | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                       | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                       | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                               | ms / Raft Log Append           | Timer   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/docs/configuration/telemetry)
+page for more details.
+
+As of Nomad 0.9, Nomad will emit additional labels for [parameterized](/docs/job-specification/parameterized) and
+[periodic](/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+| --------------------------------------- | ----------------------------------------------------------------------------------- | ---------- | ----- | ------------------------------------------------------------------------------------- |
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated_disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations blocked                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating                                                     | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated_memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on the
+task driver; not all task drivers can provide all metrics.
+
+| Metric                                        | Description                                                       | Unit        | Type  | Labels                                           |
+| --------------------------------------------- | ----------------------------------------------------------------- | ----------- | ----- | ------------------------------------------------ |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                       | Unit                 | Type    | Labels                       |
+| ---------------------------------------------------- | ----------------------------------------------------------------- | -------------------- | ------- | ---------------------------- |
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                   | Integer              | Gauge   | datacenter, host, node_class |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                       | Integer              | Gauge   | datacenter, host, node_class |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job          | Integer              | Gauge   | host, job, namespace         |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job              | Integer              | Gauge   | host, job, namespace         |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state                               | Integer              | Gauge   | host                         |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern. | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits                        | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                        | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                               | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                      | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                             | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                       | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                              | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                 | Integer              | Gauge   | host                         |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals in the waiting state                               | Integer              | Gauge   | host                         |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                 | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                 | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.alloc_update`                       | Time elapsed to apply `AllocUpdate` raft entry                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                 | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry               | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                              | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                             | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                          | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Summary` RPC call                           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                  | Integer              | Gauge   | host                         |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                           | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed | Nanoseconds | Summary | host                     |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                      | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                     | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                | Nanoseconds          | Gauge   | host                         |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                           | Integer              | Gauge   | host                         |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                | Nanoseconds          | Gauge   | host                         |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                     | Integer              | Gauge   | host                         |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                 | Nanoseconds          | Gauge   | host                         |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                               | Nanoseconds          | Gauge   | host                         |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                      | Integer              | Gauge   | host                         |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                         | Integer              | Gauge   | host                         |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                       | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                  | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                         | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                        | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.invoke_scheduler_service`        | Time elapsed for worker to invoke the scheduler                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                   | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                            | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                    | Nanoseconds          | Summary | host                         |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed | Nanoseconds | Summary | host                      |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                      | Integer              | Gauge   | host                         |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                  | Integer              | Counter | host                         |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                            | Integer              | Gauge   | host                         |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                     | Nanoseconds          | Summary | host                         |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                | Nanoseconds          | Summary | host                         |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                              | Nanoseconds          | Summary | host                         |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                            | Integer              | Gauge   | host                         |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication  | Nanoseconds          | Summary | host                         |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                          | Integer              | Gauge   | host                         |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                      | ms / Raft Log Append | Timer   |                              |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                 | Integer              | Gauge   | host                         |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                  | Integer              | Gauge   | host                         |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                    | Integer              | Gauge   | host                         |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election               | Integer              | Gauge   | host                         |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum              | Integer              | Gauge   | host                         |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                 | Integer              | Gauge   | host                         |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                         | Nanoseconds          | Summary | host                         |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                       | # of bytes           | Gauge   | host                         |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                           | Nanoseconds          | Gauge   | host                         |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                       | Integer              | Gauge   | host                         |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                               | Integer              | Summary | host                         |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                       | Integer              | Summary | host                         |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                       | Integer              | Summary | host                         |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                            | Integer              | Gauge   | host                         |
+
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
diff --git a/content/nomad/v1.1.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.1.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..efea14cf0b
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/docs/concepts/consensus) and [gossip protocol](/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default,
+any signal to an agent (interrupt, terminate, kill) will cause the agent
+to forcefully stop. Graceful termination can be configured by either
+setting `leave_on_interrupt` or `leave_on_terminate` to respond to the
+respective signals.
+
+When gracefully exiting, clients will update their status to terminal on
+the servers so that tasks can be migrated to healthy agents. Servers
+will notify their intention to leave the cluster which allows them to
+leave the [consensus](/docs/concepts/consensus) peer set.
+
+It is especially important that a server node be allowed to leave gracefully
+so that there will be a minimal impact on availability as the server leaves
+the consensus peer set. If a server does not gracefully leave, and will not
+return into service, the [`server force-leave` command](/docs/commands/server/force-leave)
+should be used to eject it from the consensus peer set.
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
diff --git a/content/nomad/v1.1.x/content/docs/operations/telemetry.mdx b/content/nomad/v1.1.x/content/docs/operations/telemetry.mdx
new file mode 100644
index 0000000000..f558dab736
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/operations/telemetry.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: Telemetry Overview
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Telemetry Overview
+
+The Nomad client and server agents collect a wide range of runtime metrics
+related to the performance of the system. Operators can use this data to gain
+real-time visibility into their cluster and improve performance. Additionally,
+Nomad operators can set up monitoring and alerting based on these metrics in
+order to respond to any changes in the cluster state.
+
+On the server side, leaders and
+followers have metrics in common as well as metrics that are specific to their
+roles. Clients have separate metrics for the host metrics and for
+allocations/tasks, both of which have to be [explicitly
+enabled][telemetry-stanza]. There are also runtime metrics that are common to
+all servers and clients.
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [Gauges, counters and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/metrics API endpoint][metrics-api-endpoint] to return metrics for
+  the current Nomad process (as of Nomad 0.7). This endpoint supports Prometheus
+  formatted metrics.
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+- Configure Nomad to automatically forward metrics to a third-party provider.
+
+Nomad 0.7 added support for [tagged metrics][tagged-metrics], improving the
+integrations with [DataDog][datadog-telem] and [Prometheus][prometheus-telem].
+Metrics can also be forwarded to [Statsite][statsite-telem],
+[StatsD][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns:
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+The sections below cover a number of important metrics
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking issues
+between the servers or insufficient CPU resources. Users in cloud environments
+often bump their servers up to the next instance class with improved networking
+and CPU to stabilize leader elections. The `nomad.raft.leader.lastContact` metric
+is a general indicator of Raft latency which can be used to observe how Raft
+timing is performing and guide the decision to upgrade to more powerful servers.
+`nomad.raft.leader.lastContact` should not get too close to the leader lease
+timeout of 500ms.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+## Scheduling
+
+The following metrics allow an operator to observe changes in throughput at the
+various points in the scheduling process (evaluation, scheduling/planning, and
+placement):
+
+- **nomad.broker.total_blocked** - The number of blocked evaluations.
+- **nomad.worker.invoke_scheduler.\<type\>** - The time to run the scheduler of
+  the given type.
+- **nomad.plan.evaluate** - The time to evaluate a scheduler Plan.
+- **nomad.plan.submit** - The time to submit a scheduler Plan.
+- **nomad.plan.queue_depth** - The number of scheduler Plans waiting to be
+  evaluated.
+
+Upticks in any of the above metrics indicate a decrease in scheduler throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis:
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+We do not currently surface metrics for job and task/allocation status, although
+we will consider adding metrics where it makes sense.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure:
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /docs/configuration/telemetry#circonus
+[collection-interval]: /docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /docs/configuration/telemetry#datadog
+[prometheus-telem]: /docs/configuration/telemetry#prometheus
+[metrics-api-endpoint]: /api-docs/metrics
+[metric-types]: /docs/telemetry/metrics#metric-types
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /docs/configuration/telemetry#statsd
+[statsite-telem]: /docs/configuration/telemetry#statsite
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[telemetry-stanza]: /docs/configuration/telemetry
diff --git a/content/nomad/v1.1.x/content/docs/partnerships.mdx b/content/nomad/v1.1.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..6b02447369
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. For a full description of the current features please refer to the [Nomad Website](/). The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Vault integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/docs/drivers/external)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/docs/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/docs/operations/telemetry)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.1.x/content/docs/runtime/environment.mdx b/content/nomad/v1.1.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..64a5848594
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs and where possible backed by an
+  in-memory filesystem. It can be used to store secret data that should not be
+  visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[vault]: /docs/vault-integration 'Nomad Vault Integration'
+[filesystem internals]: /docs/concepts/filesystem
diff --git a/content/nomad/v1.1.x/content/docs/runtime/index.mdx b/content/nomad/v1.1.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..395b323583
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/docs/runtime/environment)
+- [Interpolation](/docs/runtime/interpolation)
+- [Schedulers](/docs/schedulers)
diff --git a/content/nomad/v1.1.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.1.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..31da7917f4
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.placement.availability-zone}'}</code>
+      </td>
+      <td>Availability Zone of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:3.2"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.1.x/content/docs/schedulers.mdx b/content/nomad/v1.1.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..3956bc1334
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/schedulers.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has three scheduler types that can be used when creating your job:
+`service`, `batch` and `system`. Here we will describe the differences between
+each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] stanzas.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+stanzas.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] stanza; system jobs do not have rescheduling.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
+[preemption]: /docs/concepts/scheduling/preemption
+[restart]: /docs/job-specification/restart
+[reschedule]: /docs/job-specification/reschedule
diff --git a/content/nomad/v1.1.x/content/docs/upgrade/index.mdx b/content/nomad/v1.1.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..7e065df074
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](https://learn.hashicorp.com/tutorials/nomad/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /docs/configuration#data_dir
+[heartbeat_grace]: /docs/configuration/server#heartbeat_grace
+[monitor]: /docs/commands/monitor
+[node-status]: /docs/commands/node/status
+[server-members]: /docs/commands/server/members
+[upgrade-specific]: /docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` stanza (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`raft.peers`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `raft.peers` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /docs/configuration/server#raft_protocol
+
diff --git a/content/nomad/v1.1.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.1.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..659c967f9e
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1191 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+## Nomad 1.1.3
+
+#### Docker Driver
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated
+a hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](https://www.nomadproject.io/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. stanzas). Check [HCL](/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` stanza were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` stanza are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/docs/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/docs/configuration/client#host_volume-stanza) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` stanzas:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits stanza is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update stanza when a service job is created or updated. This does not
+affect jobs with an update stanza.
+
+In pre-0.10 releases, when updating a service job without an update stanza, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` stanza][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` stanzas:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/docs/job-specification/env) stanza to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] stanzas are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-stanza] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config stanza:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` stanza. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` stanza could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` stanza, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` stanza or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` stanza will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/docs/job-specification/network#to) field on group network port stanzas
+will be interpolated properly. Please see the
+[`network`](/docs/job-specification/network/) stanza documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`](/docs/configuration/server#raft_protocol) option in
+their `server` stanza to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](https://learn.hashicorp.com/tutorials/nomad/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+#### Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3 in Nomad 0.8 and
+higher. Raft protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. See [Raft Protocol Version
+Compatibility](/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility)
+for more details. Also the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+Please note that the Raft protocol is different from Nomad's internal protocol
+as shown in commands like `nomad server members`. To see the version of the Raft
+protocol in use on each server, use the `nomad operator raft list-peers`
+command.
+
+The easiest way to upgrade servers is to have each server leave the cluster,
+upgrade its `raft_protocol` version in the `server` stanza, and then add it
+back. Make sure the new server joins successfully and that the cluster is stable
+before rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the older
+servers in a similar fashion.
+
+When using Raft protocol version 3, servers are identified by their `node-id`
+instead of their IP address when Nomad makes changes to its internal Raft quorum
+configuration. This means that once a cluster has been upgraded with servers all
+running Raft protocol version 3, it will no longer allow servers running any
+older Raft protocol versions to be added. If running a single Nomad server,
+restarting it in-place will result in that server not being able to elect itself
+as a leader. To avoid this, either set the Raft protocol back to 2, or use
+[Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+to map the server to its node ID in the Raft quorum configuration.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] stanza in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` stanza documentation][migrate] and [Decommissioning Nodes
+guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/docs/job-specification/env) and
+[`template`](/docs/job-specification/template) stanzas.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following stanza:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[dangling-containers]: /docs/drivers/docker#dangling-containers
+[drain-api]: /api-docs/nodes#drain-node
+[drain-cli]: /docs/commands/node/drain
+[dst]: /docs/job-specification/periodic#daylight-saving-time
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /docs/configuration#limits
+[lxc]: /docs/drivers/external/lxc
+[migrate]: /docs/job-specification/migrate
+[plugin-stanza]: /docs/configuration/plugin
+[plugins]: /docs/drivers/external
+[preemption-api]: /api-docs/operator#update-scheduler-configuration
+[preemption]: /docs/concepts/scheduling/preemption
+[proxy_concurrency]: /docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /docs/configuration/client#reserved-parameters
+[task-config]: /docs/job-specification/task#config
+[tls-guide]: https://learn.hashicorp.com/tutorials/nomad/security-enable-tls
+[tls-vault-guide]: https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad
+[update]: /docs/job-specification/update
+[validate]: /docs/commands/job/validate
+[vault_grace]: /docs/job-specification/template
+[node drain]: https://www.nomadproject.io/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /docs/configuration/client#template-parameters
+[pki]: https://www.vaultproject.io/docs/secrets/pki
+[`volume create`]: /docs/commands/volume/create
+[`volume register`]: /docs/commands/volume/register
+[`volume`]: /docs/job-specification/volume
+[Enterprise licensing]: /docs/enterprise/license
+[`CAP_NET_RAW`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /docs/drivers/docker#allow_caps
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /docs/drivers/exec#allow_caps
+[allow_caps_java]: /docs/drivers/java#allow_caps
+[cap_add_exec]: /docs/drivers/exec#cap_add
+[cap_drop_exec]: /docs/drivers/exec#cap_drop
+[`log_file`]: /docs/configuration#log_file
diff --git a/content/nomad/v1.1.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.1.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..c63e018796
--- /dev/null
+++ b/content/nomad/v1.1.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.1.x/content/intro/index.mdx b/content/nomad/v1.1.x/content/intro/index.mdx
new file mode 100644
index 0000000000..f346673bd2
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/docs) and [HashiCorp Learn guides](https://learn.hashicorp.com/nomad) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/intro/use-cases) and [Who Uses Nomad](/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.1.x/content/intro/use-cases.mdx b/content/nomad/v1.1.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..596d1ec370
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker)
+and integrates seamlessly with [Consul](/docs/integrations/consul-integration)
+and [Vault](/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.1.x/content/intro/vs/ecs.mdx b/content/nomad/v1.1.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.1.x/content/intro/vs/index.mdx b/content/nomad/v1.1.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.1.x/content/intro/vs/mesos.mdx b/content/nomad/v1.1.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.1.x/content/intro/vs/terraform.mdx b/content/nomad/v1.1.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..8bda3512cf
--- /dev/null
+++ b/content/nomad/v1.1.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.1.x/content/partials/envvars.mdx b/content/nomad/v1.1.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..6e8273c6e0
--- /dev/null
+++ b/content/nomad/v1.1.x/content/partials/envvars.mdx
@@ -0,0 +1,368 @@
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_DIR</code>
+      </td>
+      <td>
+        The path to the shared <code>alloc/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">
+          here for more
+        </a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_DIR</code>
+      </td>
+      <td>
+        The path to the task <code>local/</code> directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_SECRETS_DIR</code>
+      </td>
+      <td>
+        Path to the task's secrets directory. See
+        <a href="/docs/runtime/environment#task-directories">here</a> for more information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_MEMORY_LIMIT</code>
+      </td>
+      <td>Memory limit in MB for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_MEMORY_MAX_LIMIT</code>
+      </td>
+      <td>
+        The maximum memory limit the task may use if client has excess memory
+        capacity, in MB. Omitted if task isn't configured with memory oversubscription.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_CPU_LIMIT</code>
+      </td>
+      <td>CPU limit in MHz for the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_ID</code>
+      </td>
+      <td>Allocation ID of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_NAME</code>
+      </td>
+      <td>Allocation name of the task</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ALLOC_INDEX</code>
+      </td>
+      <td>
+        Allocation index; useful to distinguish instances of task groups. From 0
+        to (count - 1). The index is unique within a given version of a job, but
+        canaries or failed tasks in a deployment may reuse the index.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_TASK_NAME</code>
+      </td>
+      <td>Task's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_GROUP_NAME</code>
+      </td>
+      <td>Group's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_ID</code>
+      </td>
+      <td>
+        Job's ID, which is equal to the Job name when submitted through
+        CLI but can be different when using the API
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_NAME</code>
+      </td>
+      <td>Job's name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_JOB_PARENT_ID</code>
+      </td>
+      <td>ID of the Job's parent if it has one</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_DC</code>
+      </td>
+      <td>Datacenter in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_NAMESPACE</code>
+      </td>
+      <td>Namespace in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_REGION</code>
+      </td>
+      <td>Region in which the allocation is running</td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_META_&lt;key&gt;</code>
+      </td>
+      <td>
+        The metadata value given by <code>key</code> on the task's
+        metadata. Note that this is different from
+        <a href="/docs/runtime/interpolation#node-variables-">
+          <code>$&#123;meta.&lt;key&gt;&#125;</code>
+        </a>
+        which are keys in the node's metadata.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>VAULT_TOKEN</code>
+      </td>
+      <td>
+        The task's Vault token. See
+        <a href="/docs/vault-integration">Vault Integration</a>
+        for more details
+      </td>
+    </tr>
+    <tr>
+      <th colspan="2">Network-related Variables</th>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code>. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code>. Driver-specified port when a
+        port map is used, otherwise the host's static or dynamic port
+        allocation. Services should bind to this port. See
+        <a href="/docs/job-specification/network">here for more</a> information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code>. See
+        <a href="/docs/job-specification/network#mapped-ports">here</a> for more
+        information.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_IP_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host IP for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port for the given port <code>label</code> and <code>task</code> for
+        tasks in the same task group. Driver-specified port when a port map is
+        used, otherwise the host's static or dynamic port allocation.
+        Services should bind to this port.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ADDR_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> pair for the given port <code>label</code> and
+        <code>task</code> for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_HOST_PORT_&lt;task&gt;_&lt;label&gt;</code>
+      </td>
+      <td>
+        Port on the host for the port <code>label</code> and <code>task</code>
+        for tasks in the same task group.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_IP_&lt;service&gt;</code>
+      </td>
+      <td>
+        IP for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_PORT_&lt;service&gt;</code>
+      </td>
+      <td>
+        Port for the given <code>service</code> when defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_UPSTREAM_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Host <code>IP:Port</code> for the given <code>service</code> when
+        defined as a Consul Connect
+        <a href="/docs/job-specification/upstreams">upstream</a>.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>NOMAD_ENVOY_ADMIN_ADDR_&lt;service&gt;</code>
+      </td>
+      <td>
+        Local address <code>127.0.0.2:Port</code> for the admin port of the
+        envoy sidecar for the given <code>service</code> when defined as a
+        Consul Connect enabled service. Envoy runs inside the group network
+        namespace unless configured for host networking.
+      </td>
+    </tr>
+      <tr>
+        <td>
+          <code>NOMAD_ENVOY_READY_ADDR_&lt;service&gt;</code>
+        </td>
+        <td>
+          Local address <code>127.0.0.1:Port</code> for the ready port of the
+          envoy sidecar for the given <code>service</code> when defined as a
+          Consul Connect enabled service. Envoy runs inside the group network
+          namespace unless configured for host networking.
+        </td>
+      </tr>
+    <tr>
+      <th colspan="2">Consul-related Variables (only set for connect native tasks)</th>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_HTTP_ADDR</code>
+      </td>
+      <td>
+        Specifies the address to the local Consul agent. Will be automatically
+        set to a unix domain socket in bridge networking mode, or a tcp address in
+        host networking mode.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_HTTP_TOKEN</code>
+      </td>
+      <td>
+        Specifies the Consul ACL token used to authorize with Consul. Will be
+        automatically set to a generated Connect service identity token specific
+        to the service instance if Consul ACLs are enabled.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_HTTP_SSL</code>
+      </td>
+      <td>
+        Specifies whether HTTPS should be used when communicating with consul. Will
+        be automatically set to true if Nomad is configured to communicate with
+        Consul using TLS.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_HTTP_SSL_VERIFY</code>
+      </td>
+      <td>
+        Specifies whether the HTTPS connection with Consul should be mutually
+        verified. Will be automatically set to true if Nomad is configured to
+        verify TLS certificates.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_CACERT</code>
+      </td>
+      <td>
+        Specifies the path to the CA certificate used for Consul communication.
+        Will be automatically set if Nomad is configured with the <code>consul.share_ssl</code>
+        option.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_CLIENT_CERT</code>
+      </td>
+      <td>
+        Specifies the path to the Client certificate used for Consul communication.
+        Will be automatically set if Nomad is configured with the <code>consul.share_ssl</code>
+        option.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_CLIENT_KEY</code>
+      </td>
+      <td>
+        Specifies the path to the CLient Key certificate used for Consul communication.
+        Will be automatically set if Nomad is configured with the <code>consul.share_ssl</code>
+        option.
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>CONSUL_TLS_SERVER_NAME</code>
+      </td>
+      <td>
+        Specifies the server name to use as the SNI host for Consul communication.
+        Will be automatically set if Consul is configured to use TLS and the task
+        is in a group using bridge networking mode.
+      </td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.1.x/content/partials/general_options.mdx b/content/nomad/v1.1.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..fe76ca2ade
--- /dev/null
+++ b/content/nomad/v1.1.x/content/partials/general_options.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespaces authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.1.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.1.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..7ae431c4f5
--- /dev/null
+++ b/content/nomad/v1.1.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,35 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.1.x/data/api-docs-nav-data.json b/content/nomad/v1.1.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..a864be8539
--- /dev/null
+++ b/content/nomad/v1.1.x/data/api-docs-nav-data.json
@@ -0,0 +1,145 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.1.x/data/docs-nav-data.json b/content/nomad/v1.1.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..92a2ff45e0
--- /dev/null
+++ b/content/nomad/v1.1.x/data/docs-nav-data.json
@@ -0,0 +1,1803 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Connect",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval status",
+        "path": "commands/eval-status"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin <sup>Beta</sup>",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/external"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/external/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/external/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "path": "drivers/external/jail-task-driver"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/external/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/external/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/external/rkt"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/external/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/external/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/external/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/external"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "path": "devices/external/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "path": "autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "path": "autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Telemetry",
+        "path": "operations/telemetry"
+      },
+      {
+        "title": "Metrics",
+        "path": "operations/metrics"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.1.x/data/intro-nav-data.json b/content/nomad/v1.1.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..7abd058898
--- /dev/null
+++ b/content/nomad/v1.1.x/data/intro-nav-data.json
@@ -0,0 +1,56 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "https://learn.hashicorp.com/collections/nomad/get-started"
+      },
+      {
+        "title": "Running Nomad",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-run"
+      },
+      {
+        "title": "Jobs",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs"
+      },
+      {
+        "title": "Clustering",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster"
+      },
+      {
+        "title": "Web UI",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui"
+      },
+      {
+        "title": "Next Steps",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.1.x/img/count-dashboard.png b/content/nomad/v1.1.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.1.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.1.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.1.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.1.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/favicon-16x16.png b/content/nomad/v1.1.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/favicon-194x194.png b/content/nomad/v1.1.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/favicon-32x32.png b/content/nomad/v1.1.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/favicon.ico b/content/nomad/v1.1.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.1.x/img/favicons/mstile-144x144.png b/content/nomad/v1.1.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/mstile-150x150.png b/content/nomad/v1.1.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/mstile-310x150.png b/content/nomad/v1.1.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/mstile-310x310.png b/content/nomad/v1.1.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/mstile-70x70.png b/content/nomad/v1.1.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.1.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.1.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.1.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.1.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.1.x/img/logo-hashicorp.svg b/content/nomad/v1.1.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v1.1.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.1.x/img/logo-text.svg b/content/nomad/v1.1.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.1.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.1.x/img/nomad-architecture-global.png b/content/nomad/v1.1.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.1.x/img/nomad-architecture-region.png b/content/nomad/v1.1.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.1.x/img/nomad-bg-pattern.svg b/content/nomad/v1.1.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.1.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.1.x/img/nomad-data-model.png b/content/nomad/v1.1.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.1.x/img/nomad-evaluation-flow.png b/content/nomad/v1.1.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.1.x/img/nomad-kubernetes.png b/content/nomad/v1.1.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.1.x/img/nomad-panel-learn.svg b/content/nomad/v1.1.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.1.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.1.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.1.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.1.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.1.x/img/nomad-workload.png b/content/nomad/v1.1.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.1.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.1.x/img/og-image.png b/content/nomad/v1.1.x/img/og-image.png
new file mode 100644
index 0000000000..7faccf445c
Binary files /dev/null and b/content/nomad/v1.1.x/img/og-image.png differ
diff --git a/content/nomad/v1.1.x/img/pattern.svg b/content/nomad/v1.1.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.1.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.1.x/redirects.jsonc b/content/nomad/v1.1.x/redirects.jsonc
new file mode 100644
index 0000000000..87e1a90ca9
--- /dev/null
+++ b/content/nomad/v1.1.x/redirects.jsonc
@@ -0,0 +1,1255 @@
+[
+  // Define your custom redirects within this file.
+  // Vercel"s redirect documentation: https://vercel.com/docs/configuration#project/redirects
+  // Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+
+  // Friendly URL for trial form redirection
+  {
+    "source": "/trial",
+    "destination": "https://www.hashicorp.com/products/nomad/trial",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/overview",
+    "destination": "/docs/operations",
+    "permanent": true,
+  },
+
+  // This redirect supports a URL built into the Nomad UI, and should always be
+  // directed someplace valid to support the text "Read about Outage Recovery."
+  {
+    "source": "/guides/outage.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  // Nomad Learn Redirects
+  {
+    "source": "/intro/getting-started",
+    "destination": "https://learn.hashicorp.com/collections/nomad/get-started",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/install",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-install",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/running",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-run",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/ui",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/next-steps",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/vs/kubernetes",
+    "destination": "/docs/nomad-vs-kubernetes",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/who-uses-nomad",
+    "destination": "/docs/who-uses/noamd",
+    "permanent": true,
+  },
+  // Guides
+  {
+    "source": "/guides/load-balancing",
+    "destination": "https://learn.hashicorp.com/collections/nomad/load-balancing",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/fabio",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/nginx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/haproxy",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/traefik",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/stateful-workloads",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/host-volumes",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/portworx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/web-ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/access.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/accessing",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/submitting-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/operating-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/inspecting-the-cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/securing",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/governance-and-policy",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  // /s/* redirects for useful links that need a stable URL but we may need to
+  // change its destination in the future.
+  {
+    "source": "/s/port-plan-failure",
+    "destination": "https://github.com/hashicorp/nomad/issues/9506",
+    "permanent": false,
+  },
+
+  // Spark guide links are all repointed to deprecated nomad-spark repo
+  {
+    "source": "/guides/spark",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/spark/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  // These are subsumed in the splat over analytical-workloads, but I"m keeping them here in case
+  // we want to reclaim the slug "analytical-workloads" at some point and deal with some bad links.
+  // {
+  //   "source": "/guides/analytical-workloads/spark/spark",
+  //   "destination": "https://github.com/hashicorp/nomad-spark",
+  //   "permanent": true,
+  // },
+
+  {
+    "source": "/guides/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspec",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/affinity",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/affinity",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/advanced-scheduling/preemption-service-batch",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/spread",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/spread",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/update-strategies",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/manage-clusters",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/monitoring",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/prometheus-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/vault-pki-integration",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad",
+    "permanent": true,
+  },
+
+  // Multi-part UI guides
+  {
+    "source": "/guides/ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+
+  // Website
+  // Docs
+  {
+    "source": "/docs/index",
+    "destination": "/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api-docs/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/config",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/taskconfig",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/inspecting",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/resources",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/updating",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/servicediscovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/interpreted",
+    "destination": "/docs/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/json",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/environment",
+    "destination": "/docs/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/servicediscovery",
+    "destination": "/docs/job-specification/service",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/networking",
+    "destination": "/docs/job-specification/network",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/job-specification/index",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/requirements",
+    "destination": "/docs/install/production/requirements/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-index",
+    "destination": "/docs/commands/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-list-peers",
+    "destination": "/docs/commands/operator/raft-list-peers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-remove-peer",
+    "destination": "/docs/commands/operator/raft-remove-peer",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/job-dispatch",
+    "destination": "/docs/commands/job/dispatch",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/alloc-status",
+    "destination": "/docs/commands/alloc/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/fs",
+    "destination": "/docs/commands/alloc/fs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/logs",
+    "destination": "/docs/commands/alloc/logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/init",
+    "destination": "/docs/commands/job/init",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/inspect",
+    "destination": "/docs/commands/job/inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/run",
+    "destination": "/docs/commands/job/run",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/stop",
+    "destination": "/docs/commands/job/stop",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/plan",
+    "destination": "/docs/commands/job/plan",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/validate",
+    "destination": "/docs/commands/job/validate",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/client-config",
+    "destination": "/docs/commands/node/config",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-drain",
+    "destination": "/docs/commands/node/drain",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-status",
+    "destination": "/docs/commands/node/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keygen",
+    "destination": "/docs/commands/operator/keygen",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keyring",
+    "destination": "/docs/commands/operator/keyring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-force-leave",
+    "destination": "/docs/commands/server/force-leave",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-join",
+    "destination": "/docs/commands/server/join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-members",
+    "destination": "/docs/commands/server/members",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/runtime/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+
+  // Sometimes code names are too good not to mention
+  {
+    "source": "/heartyeet",
+    "destination": "/docs/job-specification/group#stop_after_client_disconnect",
+    "permanent": true,
+  },
+
+  // Moved /docs/drivers/external/podman -> /docs/drivers/podman
+  {
+    "source": "/docs/drivers/external/podman",
+    "destination": "/docs/drivers/podman",
+    "permanent": true,
+  },
+
+  // Moved /docs/operating-a-job/ -> /guides/operating-a-job/
+  {
+    "source": "/docs/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/update-strategies",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  // Moved /docs/agent/configuration/ -> /docs/configuration/ 301!
+  {
+    "source": "/docs/agent/configuration",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/acl",
+    "destination": "/docs/configuration/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/autopilot",
+    "destination": "/docs/configuration/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/client",
+    "destination": "/docs/configuration/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/consul",
+    "destination": "/docs/configuration/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/sentinel",
+    "destination": "/docs/configuration/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server",
+    "destination": "/docs/configuration/server",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server_join",
+    "destination": "/docs/configuration/server_join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/telemetry",
+    "destination": "/docs/configuration/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/tls",
+    "destination": "/docs/configuration/tls",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/vault",
+    "destination": "/docs/configuration/vault",
+    "permanent": true,
+  },
+  // Moved telemetry under operations
+  {
+    "source": "/docs/telemetry",
+    "destination": "/docs/operations/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/telemetry/metrics",
+    "destination": "/docs/operations/metrics",
+    "permanent": true,
+  },
+
+  // Moved installing agent under operations as ope
+  {
+    "source": "/docs/install/production/nomad-agent",
+    "destination": "/docs/operations/nomad-agent",
+    "permanent": true,
+  },
+
+  // Moved guide-like docs to /guides
+  {
+    "source": "/docs/agent",
+    "destination": "/docs/install/production/nomad-agent/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/telemetry",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/service-discovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+
+  // Redirect old LXC driver doc to new one in /docs/external
+  {
+    "source": "/docs/drivers/lxc",
+    "destination": "/docs/drivers/external/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/rkt",
+    "destination": "/docs/drivers/external/rkt",
+    "permanent": true,
+  },
+
+  // API
+  {
+    "source": "/docs/http/agent-force-leave",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-join",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-members",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-self",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-servers",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/alloc",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/allocs",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-allocation-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-fs",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/eval",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/evals",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/job",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/jobs",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/json-jobs",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/node",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/nodes",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/operator",
+    "destination": "/api-docs/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/regions",
+    "destination": "/api-docs/regions",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/status",
+    "destination": "/api-docs/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/system",
+    "destination": "/api-docs/system",
+    "permanent": true,
+  },
+
+  // Guides
+
+  // Reorganized Guides by Persona
+  {
+    "source": "/guides/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/install/index",
+    "destination": "/docs/install",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/agent/index",
+    "destination": "/docs/install/production/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/consul-integration/index",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/vault-integration/index",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+
+  // Enterprise
+
+  // Reorganized Enterprise into single pager
+  {
+    "source": "/docs/enterprise/namespaces",
+    "destination": "/docs/enterprise#namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/quotas",
+    "destination": "/docs/enterprise#resource-quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/preemption",
+    "destination": "/docs/enterprise#preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/sentinel",
+    "destination": "/docs/enterprise#sentinel-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/autopilot",
+    "destination": "/docs/enterprise#nomad-enterprise-platform",
+    "permanent": true,
+  },
+
+  // Guide Catch-all Redirects
+  {
+    "source": "/guides/:splat*",
+    "destination": "https://learn.hashicorp.com/nomad",
+    "permanent": true,
+  },
+
+  // Vault Integration
+  {
+    "source": "/docs/vault-integration",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  // Old resources -> Community
+  {
+    "source": "/resources",
+    "destination": "/community",
+    "permanent": true,
+  },
+  // `/<path>/index.html` to /<path>
+  {
+    "source": "/:splat*/index.html",
+    "destination": "/:splat*",
+    "permanent": true,
+  },
+  // `.html` to non-`.html`
+  {
+    "source": "/:splat(.*).html",
+    "destination": "/:splat",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/concepts/:path*",
+    "destination": "/docs/concepts/:path*",
+    "permanent": true,
+  }
+]
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.10.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..37b871461c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,365 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+@include 'api-docs/auth-method-params.mdx'
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "redacted",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+The parameters are the same as Create.
+
+@include 'api-docs/auth-method-params.mdx'
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "redacted",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                               | Produces       |
+| -------- | ---------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+[private key jwt]: https://oauth.net/private-key-jwt/
+[concepts-assertions]: /nomad/docs/secure/authentication/oidc#client-assertions
+[x5t]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.7
+[x5t#S256]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8
+[pkce]: https://oauth.net/2/pkce/
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.10.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..9ad1c50a13
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/index.mdx b/content/nomad/v1.10.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..86a7bea3f7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/docs/secure/acl).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/login.mdx b/content/nomad/v1.10.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.10.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.10.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..97535fc338
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,231 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | -----   ---------- | ------------------ |
+| `GET`  | `/v1/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                          | Produces       |
+| ------ | ----------------------------- | -------------- |
+| `POST` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given job,
+  group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - Attach the policy to the job in this
+    namespace.  Required if `JobID` is set.
+
+  - `JobID` `(string)` - Attach the policy to this job. Required to use `JobACL`.
+
+  - `Group` `(string: <optional>)` - Attach the policy to this group within the
+    job.  Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - Attach the policy to this task within the job.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Read Self Policy
+
+This endpoint reads the ACL policies associated with the current workload
+identity or any authenticated request.
+
+| Method | Path                  | Produces           |
+|--------|-----------------------|--------------------|
+| `GET`  | `/v1/acl/policy/self` | `application/json` |
+
+This table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+|------------------|-------------------|---------------------------------|
+| `YES`            | `all`             | Any valid Workload Identity JWT |
+
+### Sample Request
+
+```shell-session
+$ curl --header "X-Nomad-Token: eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA" \
+    https://localhost:4646/v1/acl/policy/self
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 22,
+    "Description": "",
+    "Hash": "SmmKR0rW0WA0Bfpk7m3D8wqgrL0dtkY3DwAucF9YN4Y=",
+    "JobACL": {
+      "Group": "nomad",
+      "JobID": "nomad",
+      "Namespace": "default",
+      "Task": ""
+    },
+    "ModifyIndex": 22,
+    "Name": "nomad-policy"
+  }
+]
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                          | Produces       |
+| -------- | ----------------------------- | -------------- |
+| `DELETE` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.10.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..58232ec92e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `POST` | `/v1/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/v1/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                    | Produces       |
+| -------- | ----------------------- | -------------- |
+| `DELETE` | `/v1/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.10.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..768a03ec2e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/docs/secure/acl/bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/v1/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `POST` | `/v1/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/v1/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.10.x/content/api-docs/agent.mdx b/content/nomad/v1.10.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..47c1491200
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/v1/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/v1/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/v1/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/v1/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint          | `enable_debug` | ACLs | **Available?** |
+| ----------------- | -------------- | ---- | -------------- |
+| `/v1/agent/pprof` | unset          | n/a  | no             |
+| `/v1/agent/pprof` | `true`         | n/a  | yes            |
+| `/v1/agent/pprof` | `false`        | n/a  | no             |
+| `/v1/agent/pprof` | unset          | off  | no             |
+| `/v1/agent/pprof` | unset          | on   | **yes**        |
+| `/v1/agent/pprof` | `true`         | off  | yes            |
+| `/v1/agent/pprof` | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.10.x/content/api-docs/allocations.mdx b/content/nomad/v1.10.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..a60d84e859
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/allocations.mdx
@@ -0,0 +1,1075 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`  |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+## Override Pause Schedule State
+
+<EnterpriseAlert />
+
+The endpoint is used to override the [`schedule`][schedule] for tasks using
+time based execution.
+
+| Method         | Path                                    | Produces           |
+| -------------- | --------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:job-submit`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `Task` `(string: <required>)` - Specifies the name of the task whose schedule
+  should be overridden.
+
+- `ScheduleState` `(string: <required>)` - Specifies the pause state to force
+  the task into. One of:
+
+    - `"pause"` - Forces the task to pause.
+
+    - `"run"` - Forces the task to run.
+
+    - `"scheduled"` - Removes any overrides and forces the task to adhere to
+      its schedule.
+
+### Sample Request
+
+```shell-session
+$ echo '{"Task": "schedtask", "ScheduleState": "run"}' | \
+  nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0
+}
+```
+
+## Read Pause Schedule State
+
+<EnterpriseAlert />
+
+Retrieve the [`schedule`][schedule] state for a task using time based execution.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required              |
+| ---------------- | ------------------------- |
+| `NO`             | `namespace:read-job`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the UUID of the allocation.
+  This must be the full UUID, not the short 8-character one. This is
+  specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task from which to
+  retrieve the time-based task execution state.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause?task=schedtask
+```
+
+### Sample Response
+
+```json
+{
+  "ScheduleState": "scheduled_pause"
+}
+```
+
+#### Field Reference
+
+- `ScheduleState` `(string)`: The task's current paused state. It can can have
+  one of the following values:
+
+  - `""` - The task is running. The only state returned for tasks with no
+    schedule.
+
+  - `force_run` - The task's schedule has been overridden to run.
+
+  - `force_pause` - The task's schedule has been overridden to pause.
+
+  - `scheduled_pause` - The task is paused according to its schedule.
+
+  - `schedule_resume` - A schedule override is being removed. Subsequent calls
+    should return running (`""`) or paused (`scheduled_pause`) states. This
+    state is rarely possible to observe since it transitions immediately to
+    another state.
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[schedule]: /nomad/docs/job-specification/schedule
diff --git a/content/nomad/v1.10.x/content/api-docs/client.mdx b/content/nomad/v1.10.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..b58244ad26
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.10.x/content/api-docs/deployments.mdx b/content/nomad/v1.10.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/evaluations.mdx b/content/nomad/v1.10.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..0876c1752f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/reference/metrics
diff --git a/content/nomad/v1.10.x/content/api-docs/events.mdx b/content/nomad/v1.10.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..43fe250143
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/events.mdx
@@ -0,0 +1,406 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](https://github.com/ndjson/ndjson-spec). This means splitting
+the streaming response at every `\n` character will guarantee each message is a valid
+JSON object. Note that each JSON object may include multiple events (high server
+activity) or no events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+
+| Topic        | ACL Required                 |
+|--------------|------------------------------|
+| `*`          | `management`                 |
+| `ACLPolicy`  | `management`                 |
+| `ACLRole`    | `management`                 |
+| `ACLToken`   | `management`                 |
+| `Allocation` | `namespace:read-job`         |
+| `CSIPlugin`  | `namespace:read-job`         |
+| `CSIVolume`  | `namespace:csi-read-volume`  |
+| `Deployment` | `namespace:read-job`         |
+| `Evaluation` | `namespace:read-job`         |
+| `HostVolume` | `namespace:host-volume-read` |
+| `Job`        | `namespace:read-job`         |
+| `NodePool`   | `management`                 |
+| `Node`       | `node:read`                  |
+| `Operator`   | `operator:read`              |
+| `Service`    | `namespace:read-job`         |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                                 |
+|------------|----------------------------------------|
+| ACLPolicy  | ACLPolicy                              |
+| ACLRoles   | ACLRole                                |
+| ACLToken   | ACLToken                               |
+| Allocation | Allocation (no job information)        |
+| CSIPlugin  | CSIPlugin                              |
+| CSIVolume  | CSIVolume                              |
+| Deployment | Deployment                             |
+| Evaluation | Evaluation                             |
+| HostVolume | HostVolume (dynamic host volumes only) |
+| Job        | Job                                    |
+| Node       | Node                                   |
+| NodeDrain  | Node                                   |
+| NodePool   | NodePool                               |
+| Operator   | UtilizationSnapshot <EnterpriseAlert inline/>  |
+| Service    | Service Registrations                  |
+
+### Event Types
+
+| Type                          |
+|-------------------------------|
+| ACLPolicyDeleted              |
+| ACLPolicyUpserted             |
+| ACLRoleDeleted                |
+| ACLRoleUpserted               |
+| ACLTokenDeleted               |
+| ACLTokenUpserted              |
+| AllocationCreated             |
+| AllocationUpdateDesiredStatus |
+| AllocationUpdated             |
+| CSIVolumeDeregistered         |
+| CSIVolumeRegistered           |
+| DeploymentAllocHealth         |
+| DeploymentPromotion           |
+| DeploymentStatusUpdate        |
+| EvaluationUpdated             |
+| HostVolumeDeleted             |
+| HostVolumeRegistered          |
+| JobBatchDeregistered          |
+| JobDeregistered               |
+| JobRegistered                 |
+| NodeDeregistration            |
+| NodeDrain                     |
+| NodeEligibility               |
+| NodeEvent                     |
+| NodePoolDeleted               |
+| NodePoolUpserted              |
+| NodeRegistration              |
+| PlanResult                    |
+| ServiceDeregistration         |
+| ServiceRegistration           |
+| UtilizationSnapshotUpserted   |
+
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.advertise.address": "127.0.0.1:4646",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/index.mdx b/content/nomad/v1.10.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..88ee018527
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/index.mdx
@@ -0,0 +1,731 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter.
+
+Here is an example using curl to query the `qa` namespace:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=qa'
+```
+
+Use a wildcard (`*`) to query all namespaces:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=*'
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> \
+    --data-urlencode 'filter=<filter expression>'
+```
+
+The filter expression can also be specified in the
+[`-filter`][cli_operator_api_filter] flag of the
+[`nomad operator api`][cli_operator_api] command.
+
+```shell-session
+$ nomad operator api -filter '<filter expression>' /v1/<path>
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### List Stubs
+
+Some list endpoints return a reduced version of the resource being queried.
+This smaller version is called a _stub_ and may have different fields than the
+full resource definition. To allow more expressive filtering operations, the
+filter is applied to the full version, not the stub.
+
+If a request returns an error such as `error finding value in datum` the field
+used in filter expression may need to be adjusted. For example, filtering on
+node addresses should use the `HTTPAddr` field of the full node definition
+instead of `Address` field present in the stub.
+
+```shell-session
+$ nomad operator api -filter 'HTTPAddr matches "10.0.0..+"' /v1/nodes
+```
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Datacenters contains "dc2"' /v1/jobs
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Status != "successful"' /v1/deployments
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
+
+[cli_operator_api]: /nomad/commands/operator/api
+[cli_operator_api_filter]: /nomad/commands/operator/api#filter
diff --git a/content/nomad/v1.10.x/content/api-docs/jobs.mdx b/content/nomad/v1.10.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..391434c2ff
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2835 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+- `PreserveResources` `(bool: false)` - If set, existing task resources are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2` or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version. This
+  is specified as a query string parameter.
+
+- `diff_version` `(int: <optional>)`: Specifies the version to to compare against the current version when you create the structured diff for a job with `diffs=true`. This is specified as a query string parameter.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect", null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect": null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect": null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `idempotency_token` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Dispatch Job with raw Payload body
+
+This endpoint dispatches a new instance of a parameterized job using the full
+request body as the `Payload` as described in [Dispatch Job](#dispatch-job).
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch/payload` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+specified as part of the path.
+
+### Sample Payload
+
+```
+any HTTP request body, JSON or otherwise, becomes the dispatch Payload
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data 'anything at all' \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "DispatchedJobID": "param/dispatch-1730920906-81821d1f",
+  "EvalCreateIndex": 179,
+  "EvalID": "5e973383-8d59-3f33-4496-72112a882605",
+  "Index": 179,
+  "JobCreateIndex": 178
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to. Use either
+  this parameter or `TaggedVersion`, but do not use both.
+
+- `TaggedVersion` `(string: "")` - Specifies the tag name of the job version you
+  want to revert to. Use either this parameter or `JobVersion`, but do not use both.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+This example specifies the version.
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+This example specifies the tagged version.
+
+```json
+{
+  "JobID": "my-job",
+  "TaggedVersion": "golden-version"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+  the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if
+  the passed `JobModifyIndex` matches the current job's index. If the index is
+  zero, the register only occurs if the job is new. This paradigm allows
+  check-and-set style job updating.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as
+  part of the scaling event.  Indicates an error state preventing scaling; one
+  of `Message` or `Error` must be provided.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted
+  as part of the scaling event.  Indicates information or reason for scaling;
+  one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+   enabled, this value must match a namespace that the token is allowed to
+   access. This is specified as a query string parameter.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be scaled when it would be
+  denied by policy.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling
+  operation.  Must contain a field `Group` with the name of the task group that
+  is the target of this scaling action.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## List Job Actions
+
+This endpoint lists the actions available to tasks within a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/actions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/job/my-job/actions'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Args": [
+      "-s",
+      "wttr.in/Toronto?format=3"
+    ],
+    "Command": "/usr/bin/curl",
+    "Name": "weather",
+    "TaskGroupName": "group1",
+    "TaskName": "task"
+  },
+  {
+    "Args": [
+      "-c",
+      "nomad alloc status ${NOMAD_ALLOC_ID}"
+    ],
+    "Command": "/bin/sh",
+    "Name": "get-alloc-info",
+    "TaskGroupName": "group2",
+    "TaskName": "task"
+  },
+]
+```
+
+## Run Action
+
+This endpoint executes a predefined action from a job in the
+context of a specific task within an allocation. It opens a WebSocket to
+transmit output from the running action.
+
+
+| Method      | Path                     | Produces               |
+| ----------- | ------------------------ | ---------------------- |
+| `WebSocket` | `/v1/job/:job_id/action` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if task driver does not support [file system isolation](/nomad/plugins/author/task-driver#capabilities-capabilities-error)) |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job containing the
+  action. This is specified as part of the path.
+- `action` `(string: <required>)` - Specifies the name of the action to be
+  executed, as defined within the job's task. Specified as a query parameter.
+- `alloc_id` `(string: <required>)` - Specifies the UUID of the target
+  allocation. Specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task where the action is
+  defined. Specified as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this action.
+  Specified as a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the
+  authentication token in the first frame, as a query parameter.
+
+### WebSocket Upgrade Request
+
+Actions are executed with a WebSocket upgrade request. The request headers
+must include the standard WebSocket upgrade parameters. Example:
+
+```shell-session
+$ curl \
+  -X GET \
+  -H 'Connection: Upgrade' \
+  -H 'Upgrade: websocket' \
+  -H 'Sec-Websocket-Version: 13' \
+  -H 'Sec-Websocket-Key: x3JJHMbDL1EzLkh9GBhXDw==' \
+  'http://127.0.0.1:4646/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+or
+```shell-session
+$ nomad operator api \
+-H "Connection: Upgrade" \
+-H "Upgrade: websocket" \
+-H "Sec-WebSocket-Version: 13" \
+-H "Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==" \
+'/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+
+### Request Frames
+
+Unlike [alloc exec](/nomad/api-docs/allocations#exec-allocation), Actions do
+not take input in the form of request frames using `stdin`. Instead, the name
+of the action is passed as a query parameter and the associated input is handled
+on the allocation apart from the stream.
+
+When `?ws_handshake=true`, the first request frame must contain the
+authentication token. Similarly, when `?tty=true`, a `tty_size` frame may be
+provided to indicate a resize.
+
+The following are valid input frames:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well
+as exit codes. Response frames encompass the full range of terminal emulator outputs, including
+the control characters necessary to render interactive applications.
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+{"exited":true,"result":{}}
+```
+
+The stdout data returned in the response frames from the job action endpoint is
+base64 encoded. This encoding is necessary to ensure that the data can be
+transmitted over WebSocket connections without issues, regardless of its content.
+
+### Sample Request and Response
+
+This example response includes instances of the ANSI "control sequence
+introducer" (CSI), which is ASCII code 27 followed by `[`. The second stdout
+frame includes the desired output from the Action in question, which prints
+the local weather.
+
+```
+# Sample WebSocket request to execute an action
+WebSocket Request: /v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+
+# Toronto: ⛅️  -1°C
+{"stdout":{"data":"VG9yb250bzog4puF77iPICAtMcKwQw0K"}}
+```
+
+## Create Job Version Tag
+
+This endpoint creates a tag for a job version.
+
+@include 'version/tag-reason.mdx'
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part
+  of the path.
+- `:tag_name` `(string: <required>)` - The new tag name for the
+  version specified in the payload. Must be unique per job. Specify `tag_name` as part of the path.
+- `Version`: `(int: <optional>)` - The job version number. If not
+  specified, Nomad tags the latest version. Specify `Version` in the payload.
+- `Description`: `(string: <optional>)` - The tag description. Specify `Description` in the payload.
+
+### Sample Payload
+
+```json
+{
+  "Version": 0,
+  "Description": "The version we can roll back to."
+}
+```
+
+### Sample Request
+
+This example creates a tag named `golden-version` for version zero of the
+`hello-world` job.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "The version we can roll back to."}'
+```
+
+### Sample Response
+
+```json
+{
+  "Name":"golden-version",
+  "Description":"The version we can roll back to.",
+  "TaggedTime":1728325495829793000,
+  "Index":361,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+## Delete Job Version Tag
+
+This endpoint deletes a job version tag.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `DELETE`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part of the path.
+- `:tag_name` `(string: <required>)` - The tag name. Specify `tag_name` as part of the path.
+
+### Sample Request
+
+This example deletes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ curl -X DELETE localhost:4646/v1/job/hello-world/versions/golden-version/tag -H "Content-Type: application/json"
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID":"",
+  "EvalCreateIndex":0,
+  "JobModifyIndex":0,
+  "VolumeEvalID":"",
+  "VolumeEvalIndex":0,
+  "Index":0,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
diff --git a/content/nomad/v1.10.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.10.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..b3c023fc9f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1247 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/commands/job/inspect
+[job-output]: /nomad/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Disconnect": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul service mesh enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/concepts/scheduling/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+- `Ui` - Options to modify the presentation of the Job index page in the Web UI.
+  When specified, a description and any number of links will be added to the top of
+  the job page in question.
+
+  - `Description` - a markdown-enabled string description of the job
+    jobs.
+
+  - `Links` - Anchor link that will appear at the top of the job page.
+
+    - `Label` - The shown name of the link
+    - `Url` - The address that the link will point to
+
+  An example `ui` block:
+
+  ```json
+  "Ui": {
+    "Description": "A job that uses **Nomad Variables** to modify its output",
+    "Links": [
+      {
+        "Label": "Learn more about Nomad Variables",
+        "Url": "https://developer.hashicorp.com/nomad/docs/concepts/variables"
+      },
+      {
+        "Label": "See this job on Github",
+        "Url": "https://github.com/hashicorp/nomad/blob/main/ui/app/utils/default_jobs/variables.js"
+      }
+    ]
+  }
+  ```
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/job-declare/task-driver) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/reference/runtime-variable-interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/networking/service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Unlike `PortLabel`,
+      this setting is _not_ inherited from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. Numeric ports may be
+      used if `AddressMode: "driver"` is set on the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. The template can reference
+[Nomad's runtime environment variables][env]. For a full list of the API template
+functions, please refer to the [Consul Template README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/commands/node/drain
+[env]: /nomad/docs/reference/runtime-environment-settings 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.10.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.10.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..53734a477d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,41 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+- [`nix-nomad`](https://github.com/tristanpemble/nix-nomad) - HashiCorp Nomad job definitions in Nix
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.10.x/content/api-docs/metrics.mdx b/content/nomad/v1.10.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/namespaces.mdx b/content/nomad/v1.10.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/node-pools.mdx b/content/nomad/v1.10.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.10.x/content/api-docs/nodes.mdx b/content/nomad/v1.10.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..9095f90083
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1147 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.advertise.address": "127.0.0.1:4646",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/docs/manage/migrate-workloads) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.10.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..439355effd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,253 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - <EnterpriseAlert inline/> Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ],
+  "Leader": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+  "Voters": [
+    "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+    "e36ee410-cc3c-0a0c-c724-63817ab30303"
+  ],
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+<EnterpriseAlert>
+  This API endpoint returns with more information in Nomad Enterprise. This is
+  not present in Nomad Community Edition.
+</EnterpriseAlert>
+
+When using Nomad Enterprise this endpoint will return more information about the
+underlying actions and state of Autopilot.
+
+```json
+{
+  ...
+  "ReadReplicas": null,
+  "RedundancyZones": {},
+  "Upgrade": {
+    "Status": "idle",
+    "TargetVersion": "1.7.5+ent",
+    "TargetVersionVoters": [
+      "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "e36ee410-cc3c-0a0c-c724-63817ab30303"
+    ],
+    "TargetVersionNonVoters": null,
+    "TargetVersionReadReplicas": null,
+    "OtherVersionVoters": null,
+    "OtherVersionNonVoters": null,
+    "OtherVersionReadReplicas": null,
+    "RedundancyZones": {}
+  },
+  "OptimisticFailureTolerance": 0
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/index.mdx b/content/nomad/v1.10.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..10670871c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/docs/manage/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.10.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..e0d27df525
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,266 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Active Public Keys
+
+This endpoint retrieves a list of active public keys used to sign [workload
+identities][wi]. The response is in the [JWKS][rfc7517] format as is commonly
+used by JWT auth methods.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/.well-known/jwks.json`    | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `none`       |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/jwks.json'
+```
+
+### Sample Response
+
+```json
+{
+  "keys": [
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "15a95f48-001a-8be5-5da9-d94901d022c9",
+      "alg": "RS256",
+      "n": "6sImUQR6A...FB7bKn02dKw",
+      "e": "AQAB"
+    },
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "b7f6a3a7-14f9-4ac5-f713-32c9bce1fa93",
+      "alg": "RS256",
+      "n": "zEdiUB3DFuM...ii3kQvOf_eDApBDWJhfQw",
+      "e": "AQAB"
+    }
+  ]
+}
+```
+
+## OIDC Discovery
+
+This endpoint retrieves [OIDC configuration metadata][oidc-disco] for using
+[workload identities][wi] with third party services. Nomad will act as an
+identity provider (IDP) to allow third parties to authenticate workload
+identity JWTs based on the OIDC configurationa and JWKS.
+
+Most third parties will require this endpoint be accessible through a
+publically resolvable domain name and HTTPS signed by a trusted certificate
+authority.
+
+You must set the [`oidc_issuer`][oidc_issuer] Server agent configuration
+parameter before this endpoint is enabled. In most situations you will also
+need to run a proxy or load balancer for in front of this endpoint to serve the
+contents with HTTPS using a trusted certificate.
+
+| Method | Path                                | Produces           |
+|--------|-------------------------------------|--------------------|
+| `GET`  | `/.well-known/openid-configuration` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `none` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/openid-configuration'
+```
+
+### Sample Response
+
+```json
+{
+  "id_token_signing_alg_values_supported": [
+    "RS256",
+    "EdDSA"
+  ],
+  "issuer": "http://example.com",
+  "jwks_uri": "http://example.com/.well-known/jwks.json",
+  "response_types_supported": [
+    "code"
+  ],
+  "subject_types_supported": [
+    "public"
+  ]
+}
+```
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Parameters
+
+- `force` `(bool: false)` - Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/manage/key-management
+[`nomad operator root keyring`]: /nomad/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[oidc-disco]: https://openid.net/specs/openid-connect-discovery-1_0.html
+[oidc_issuer]: /nomad/docs/configuration/server#oidc_issuer
+[required ACLs]: /nomad/api-docs#acls
+[rfc7517]: https://datatracker.ietf.org/doc/html/rfc7517
+[wi]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/license.mdx b/content/nomad/v1.10.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.10.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..ccc1feee32
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,219 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api /v1/operator/raft/configuration
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+</Tab>
+</Tabs>
+
+### Sample Response
+
+```json
+{
+    "Index": 0,
+    "Servers": [
+        {
+            "Address": "10.1.0.10:4647",
+            "ID": "c13f9998-a0f3-d765-0b52-55a0b3ce5f88",
+            "Leader": false,
+            "Node": "node1.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.20:4647",
+            "ID": "d7927f2b-067f-45a4-6266-af8bb84de082",
+            "Leader": true,
+            "Node": "node2.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.30:4647",
+            "ID": "00d56ef8-938e-abc3-6f8a-f8ac80a80fb9",
+            "Leader": false,
+            "Node": "node3.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        }
+
+    ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. For Raft protocol v2, this is the
+    same as the `Address`. Raft protocol v3 uses GUIDs as the ID.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the server to
+  remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+### Sample Request
+
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X DELETE \
+   /v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    https://127.0.0.1:4646/v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+</Tabs>
+
+## Transfer Leadership to another Raft Peer
+
+This endpoint tells the current cluster leader to transfer leadership
+to the Nomad server with given address or ID in the Raft
+configuration. The return code signifies success or failure.
+
+| Method              | Path                                    | Produces           |
+| ------------------- | --------------------------------------- | ------------------ |
+| `PUT` <br /> `POST` | `/v1/operator/raft/transfer-leadership` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  target server as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the target server
+  as provided in the output of `/v1/operator/raft/configuration` API endpoint or
+  the `nomad operator raft list-peers` command.
+
+<Note>
+
+- The cluster must be running Raft protocol v3 or greater on all server members.
+
+- Either `address` or `id` must be provided, but not both.
+
+</Note>
+
+### Sample Requests
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X PUT \
+    "/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl --request PUT \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    "https://127.0.0.1:4646/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+</Tabs>
+
+[consensus protocol guide]: /nomad/docs/architecture/cluster/consensus
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.10.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.10.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d753600099
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/architecture/cluster/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/upgrade-check.mdx b/content/nomad/v1.10.x/content/api-docs/operator/upgrade-check.mdx
new file mode 100644
index 0000000000..f41e348fe2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/upgrade-check.mdx
@@ -0,0 +1,185 @@
+---
+layout: api
+page_title: Upgrade Check - Operator - HTTP API
+description: |-
+  The /operator/upgrade-check endpoints provide tools for verifying the state
+  of the cluster prior to upgrades.
+---
+
+# Upgrade Check Operator HTTP API
+
+The `/operator/upgrade-check` endpoints provide some predefined verifications
+that can be useful prior to upgrades and changes to Nomad configuration.
+
+<Note>
+
+These endpoints are meant to target specific releases of Nomad and may be
+removed or modified without notice.
+
+</Note>
+
+## Vault Workload Identity
+
+This endpoint retrieves jobs, nodes, and Vault ACL tokens that may be affected
+when migrating a Nomad cluster to use [workload identities for
+Vault][nomad_acl_vault_wid].
+
+| Method | Path                                                 | Produces           |
+| ------ | ---------------------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/upgrade-check/vault-workload-identity` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/operator/upgrade-check/vault-workload-identity
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 20,
+  "JobsWithoutVaultIdentity": [
+    {
+      "CreateIndex": 11,
+      "Datacenters": [
+        "*"
+      ],
+      "ID": "example",
+      "JobModifyIndex": 11,
+      "JobSummary": null,
+      "ModifyIndex": 19,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "default",
+      "ParameterizedJob": false,
+      "ParentID": "",
+      "Periodic": false,
+      "Priority": 50,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1704995322434188000,
+      "Type": "service"
+    }
+  ],
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "OutdatedNodes": [
+    {
+      "Address": "192.168.0.186",
+      "CreateIndex": 8,
+      "Datacenter": "dc1",
+      "Drain": false,
+      "Drivers": {
+        "qemu": {
+          "Attributes": {
+            "driver.qemu": "true",
+            "driver.qemu.version": "8.1.1"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.993541-05:00"
+        },
+        "exec": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "exec driver unsupported on client OS",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.958495-05:00"
+        },
+        "raw_exec": {
+          "Attributes": {
+            "driver.raw_exec": "true"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.958539-05:00"
+        },
+        "java": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.97141-05:00"
+        },
+        "docker": {
+          "Attributes": {
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.runtimes": "io.containerd.runc.v2,runc",
+            "driver.docker.os_type": "linux",
+            "driver.docker": "true",
+            "driver.docker.version": "24.0.7"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.989993-05:00"
+        }
+      },
+      "HostVolumes": null,
+      "ID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "LastDrain": null,
+      "ModifyIndex": 10,
+      "Name": "client-1",
+      "NodeClass": "",
+      "NodePool": "default",
+      "SchedulingEligibility": "eligible",
+      "Status": "ready",
+      "StatusDescription": "",
+      "Version": "1.6.4"
+    }
+  ],
+  "VaultTokens": [
+    {
+      "Accessor": "czh9MPcRXzAhxBL9XKyb3Kh1",
+      "AllocID": "f00893d4-d9ef-4937-6a7a-ab495b68a971",
+      "CreateIndex": 14,
+      "CreationTTL": 60,
+      "NodeID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "Task": "redis"
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `JobsWithoutVaultIdentity` `(array<Job>)` - The list of jobs that have a
+  [`vault`][] block but do not have an [`identity`][] for Vault
+  authentication. These jobs can fail if they are not redeployed with an
+  identity for Vault before the configuration for Nomad servers are updated and
+  their access to Vault is removed.
+
+- `OutdatedNodes` `(array<Node>)` - The list of nodes running a version of
+  Nomad that does not support workload identity authentication for Vault.
+  Allocations placed in these nodes will use the deprecated legacy flow to
+  retrieve Vault tokens. If the Nomad servers configuration is update to remove
+  their access to Vault before these nodes are upgraded, these allocations will
+  fail. Allocations that use workload identity for Vault will not be able to be
+  placed in these nodes until they are upgraded.
+
+- `VaultTokens` `(array<VaultAccessor>)` - The list of Vault ACL tokens created
+  by Nomad servers using the deprecated legacy flow. They will continue to work
+  even after the migration to the workload identities, but they may not be
+  automatically revoked by Nomad and will only expire once their TTL reaches
+  zero.
+
+
+[`identity`]: /nomad/docs/job-specification/identity
+[`vault`]: /nomad/docs/job-specification/vault
+[nomad_acl_vault_wid]: /nomad/docs/secure/vault/acl#nomad-workload-identities
+
diff --git a/content/nomad/v1.10.x/content/api-docs/operator/utilization.mdx b/content/nomad/v1.10.x/content/api-docs/operator/utilization.mdx
new file mode 100644
index 0000000000..bc000d5e3c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/operator/utilization.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: Utilization - Operator - HTTP API
+description: |-
+  The /operator/utilization endpoints provide tools for generating utilization reporting bundles for Nomad Enterprise.
+---
+
+# Operator Utilization HTTP API
+
+The `/operator/utilization` endpoints provide tools for generating utilization
+reporting bundles for Nomad Enterprise.
+
+<EnterpriseAlert />
+
+## Generate Nomad Enterprise Utilization Report Bundle
+
+This endpoint generates a utilization report. If Nomad did not record a
+utilization snapshot in the previous 24 hours, Nomad records a utilization
+snapshot first.
+
+| Method | Path                       | Produces           |
+|--------|----------------------------|--------------------|
+| `POST` | `/v1/operator/utilization` | `application/json` |
+
+This table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required     |
+|------------------|------------------|
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `today` `(bool: false)` - Specifies to return a bundle that only includes
+  utilization snapshots from the previous 24 hours.
+
+### Sample Request
+
+```shell-session
+$ curl -XPOST \
+    https://localhost:4646/v1/operator/utilization?today=true
+```
+
+### Sample Response
+
+The `Bundle` field in the response body is a base64-encoded blob. The exact
+format of this blog is not part of the Nomad API and is subject to change
+between versions. The [`nomad operator utilization`][] command, which uses this
+API, decodes this to a human-readable file in the current working directory.
+
+```json
+{
+  "Bundle": "eyJ2ZXJzaW9uIjoiMiIsIm1vZGUiOiJtYW51Y..."
+}
+```
+
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required  ACLs]: /nomad/api-docs#acls
+[`nomad operator utilization`]: /nomad/commands/operator/utilization
diff --git a/content/nomad/v1.10.x/content/api-docs/plugins.mdx b/content/nomad/v1.10.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/quotas.mdx b/content/nomad/v1.10.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..76c2674281
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/quotas.mdx
@@ -0,0 +1,418 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert product="nomad"/>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+    "Limits": [
+      {
+        "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "Cores": 0,
+          "Devices": [
+            {
+              "Affinities": null,
+              "Constraints": null,
+              "Count": 1,
+              "Name": "nvidia/gpu/Tesla M60"
+            }
+          ],
+          "DiskMB": 0,
+          "IOPS": 0,
+          "MemoryMB": 2000,
+          "MemoryMaxMB": 2000,
+          "NUMA": null,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Limit the shared default namespace",
+  "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+  "Limits": [
+    {
+      "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "Cores": 0,
+        "Devices": [
+          {
+            "Affinities": null,
+            "Constraints": null,
+            "Count": 1,
+            "Name": "nvidia/gpu/Tesla M60"
+          }
+        ],
+        "DiskMB": 0,
+        "IOPS": 0,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "NUMA": null,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 11,
+  "Name": "default-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "default-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1
+          }
+        ],
+        "VariablesLimit": 1000
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "Cores": 0,
+          "MemoryMB": 256,
+          "MemoryMaxMB": 256,
+          "DiskMB": 0,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "Devices": [
+            {
+              "Name": "nvidia/gpu/Tesla M60",
+              "Count": 1,
+              "Constraints": null,
+              "Affinities": null
+            }
+          ],
+          "NUMA": null,
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 0,
+        "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+      }
+    },
+    "Name": "default-quota",
+    "CreateIndex": 11,
+    "ModifyIndex": 38
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "Cores": 0,
+        "MemoryMB": 256,
+        "MemoryMaxMB": 256,
+        "DiskMB": 0,
+        "IOPS": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1,
+            "Constraints": null,
+            "Affinities": null
+          }
+        ],
+        "NUMA": null,
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 0,
+      "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+    }
+  },
+  "Name": "default-quota",
+  "CreateIndex": 11,
+  "ModifyIndex": 38
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/recommendations.mdx b/content/nomad/v1.10.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..1e18b818fd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,370 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/regions.mdx b/content/nomad/v1.10.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.10.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..9e16d80953
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/search.mdx b/content/nomad/v1.10.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..b205ee5269
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/search.mdx
@@ -0,0 +1,639 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evaluations, volumes, and resource quotas. Note that resource quotas is
+an Enterprise feature.
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.10.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.10.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..95a8d37807
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,176 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/docs/govern/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+<EnterpriseAlert product="nomad"/>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/v1/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/v1/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/services.mdx b/content/nomad/v1.10.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..0e6ddf2515
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
diff --git a/content/nomad/v1.10.x/content/api-docs/status.mdx b/content/nomad/v1.10.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..1b8089f846
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/system.mdx b/content/nomad/v1.10.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/task-api.mdx b/content/nomad/v1.10.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..5f644154f6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/task-api.mdx
@@ -0,0 +1,109 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+## Limitations
+
+- Using the Task API Unix Domain Socket on Windows [requires][windows] Windows
+build 17063 or later.
+
+[acl]: /nomad/docs/secure/acl/
+[acl-tokens]: /nomad/docs/secure/acl/#tokens
+[alloc-exec]: /nomad/commands/alloc/exec
+[anon]: /nomad/docs/secure/acl#policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/docs/secure/traffic/tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[dnm]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.10.x/content/api-docs/ui.mdx b/content/nomad/v1.10.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..9a78bef50e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/ui.mdx
@@ -0,0 +1,585 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version, so do not
+prepend `/vi` to this endpoint. A request to `/` redirects to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize <EnterpriseAlert inline/>
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel.
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.10.x/content/api-docs/validate.mdx b/content/nomad/v1.10.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.10.x/content/api-docs/variables/index.mdx b/content/nomad/v1.10.x/content/api-docs/variables/index.mdx
new file mode 100644
index 0000000000..0e29e60455
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/variables/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: |-
+  The /var endpoints are used to query for and interact with variables and variable
+  locking.
+---
+
+# Vars HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables, and set up locks and leases over them.
+
+See the [Variables][] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`][] commands.
+
+Please choose a sub-section in the navigation for more information
+
+[`nomad var`]: /nomad/commands/var
+[Variables]: /nomad/docs/concepts/variables
diff --git a/content/nomad/v1.10.x/content/api-docs/variables/locks.mdx b/content/nomad/v1.10.x/content/api-docs/variables/locks.mdx
new file mode 100644
index 0000000000..8b27be1811
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/variables/locks.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: Variable Locks - HTTP API
+description: The /var endpoints are used to query for and interact with variables and locks.
+---
+
+# Locks HTTP API
+
+The `/var` endpoint is used to hold, renew and release a lock over a variable.
+
+## Lock Variable
+
+The endpoint to create a variable can also be used to hold a lock and interact with
+it through the use of a parameter defining the operation to be performed.
+
+| Method | Path                                 | Produces           |
+|--------|--------------------------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path?<lock-operation>` | `application/json` |
+
+### Parameters
+
+The lock operation parameter can be:
+
+- `lock-acquire`: When used, the call will introduce a lock over the variable if
+it exists, or create a new one if it doesn't. The lock ID will be returned in the
+response and it must be provided to perform any other operation over the lock.
+The variable items can be updated at any time using the lock ID, but the lock
+parameters are unmmutable, attempting to modify them while a lock is present will
+generate an error.
+
+In the case of attempting to acquire a variable that is already locked, a conflict
+response will be returned.
+
+The lock-acquire operation will override the variable items if new values are
+present.
+
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-acquire
+```
+
+#### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "1m"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the created or updated variable including the lock
+parameters and ID, along with metadata created by the server:
+
+```json
+{
+  "CreateIndex": 15,
+  "CreateTime": 1694552155379696000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 16,
+  "ModifyTime": 1694552206138804000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-renew`: A valid call to lock renew needs to be placed before the lock's
+TTL is up in order to mantain the variable locked. A valid call must include the
+lock ID as part of the request body. If the lock TTL is up without a renewal or
+release calls, the variable will remain unlockable for at least the lock delay.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-renew
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body only returns metadata created by the server and the lock
+parameters:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 43,
+  "ModifyTime": 1694556175092779000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-release`: A call to the endpoint with the `lock-release` operation will
+immediately remove the lock over the variable, making it modifiable without
+restrictions again.
+
+The lock-release operation will not override the variable items, if the request
+body contains any item, it will generate a bad request response.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-release
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the released variable along with metadata
+created by the server:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "ModifyIndex": 66,
+  "ModifyTime": 1694556922600469000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+### Sample Response for Conflict
+
+In the case of an attempt to lock, renew or modify a locked variable
+without the correct ID, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "CreateIndex": 0,
+  "CreateTime": 0,
+  "Items": null,
+  "Lock": null,
+  "ModifyIndex": 0,
+  "ModifyTime": 0,
+  "Namespace": "default",
+  "Path": "example/first"
+}
+```
+
+## Restrictions
+
+When creating a new variable using the lock-acquire operation, all the known
+[restrictions][] regarding the path and size of the content apply, but unlike
+regular variables, locked variables can be created with or without any items.
+
+The lock TTL and Delay must be values between 10 seconds and 24 hours.
+
+[Variables]: /nomad/docs/concepts/variables
+[restrictions]: /nomad/api-docs/variables/variables#restrictions
+[`nomad var`]: /nomad/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.10.x/content/api-docs/variables/variables.mdx b/content/nomad/v1.10.x/content/api-docs/variables/variables.mdx
new file mode 100644
index 0000000000..f53b0c7be4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/variables/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables][] documentation for information how these capabilities are
+used. 
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+- `lock-operation` `(string: <unset>)` - This endpoint can also be used to create 
+and hold a lock over a variable, refer to the [locks section][] for more
+information.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+[Variables]: /nomad/docs/concepts/variables
+[locks section]:/nomad/api-docs/variables/locks
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.10.x/content/api-docs/volumes.mdx b/content/nomad/v1.10.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..735cb1f094
--- /dev/null
+++ b/content/nomad/v1.10.x/content/api-docs/volumes.mdx
@@ -0,0 +1,1242 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: |-
+  The Nomad  `/volume` and `/volumes` endpoints query for and interact with Container Storage Interface (CSI) volumes and dynamic host volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints query for and interact with
+Container Storage Interface (CSI) volumes and dynamic host volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                 |
+|------------------|--------------------------------------------------------------|
+| `YES`            | `namespace:csi-list-volume`<br/>`namespace:host-volume-read` |
+
+### Parameters
+
+- `type` `(string: <required>)` - Specifies the type of volume to query. One of
+  `csi` or `host`. The `host` value queries dynamic host volumes. Specify this
+  as a query string parameter.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response for CSI Volumes
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+### Sample Response for dynamic host volumes
+
+```json
+[
+  {
+    "CapacityBytes": 1048576000,
+    "CreateIndex": 42,
+    "CreateTime": 1736191825846395400,
+    "ID": "3735cc2c-cc64-11ef-89ed-bfb5b3bc38ea",
+    "ModifyIndex": 64,
+    "ModifyTime": 1736191825846395400,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "5c5830d0-cc64-11ef-a293-4f03e55969ea",
+    "NodePool": "default",
+    "PluginID": "plugin-id1",
+    "State": "ready"
+  }
+]
+```
+
+## Read CSI Volume
+
+This endpoint reads information about a specific CSI volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register CSI Volume
+
+This endpoint registers an external CSI volume with Nomad. The volume must exist
+in the external storage provider. Refer to the [Create CSI Volume][] section for
+details.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume`. <br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `Volumes` <code>([Volumes][csi-volume-spec]:</code> `<required>`) - Specifies
+  the JSON definition of the CSI volume. You should include the ID field if you
+  are updating an existing volume. Note that you must include the `NodeID` field
+  for the register API.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create CSI Volume
+
+This endpoint creates a CSI volume in an external storage provider and registers
+it with Nomad. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_VOLUME`
+capability support this endpoint.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume`. <br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `Volumes` <code>([Volumes][csi-volume-spec]:</code> `<required>`) - Specifies
+  the JSON definition of the CSI volume. You should include the ID field if you
+  are updating an existing volume. 
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister CSI Volume
+
+This endpoint deregisters an external CSI volume from Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  Specify this as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete CSI Volume
+
+This endpoint deletes an external CSI volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+The volume must still be registered with Nomad in order to be deleted. This API
+call fails if an allocation still claims the volume or if Nomad is unpublishing
+the volume.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach CSI Volume
+
+This endpoint detaches an external CSI volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  Specify this as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External CSI Volumes
+
+This endpoint lists storage CSI volumes that are known to the external storage
+provider but may not be registered with Nomad. Only CSI plugins that implement
+the [Controller][csi_plugins_internals] interface with the `LIST_VOLUMES`
+capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response includes a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create CSI Volume Snapshot
+
+This endpoint creates a snapshot of a CSI volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_SNAPSHOT`
+capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete CSI Volume Snapshot
+
+This endpoint deletes a CSI volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_SNAPSHOT`
+capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). Specify this as a
+  query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. Specify this as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List CSI Volume Snapshots
+
+This endpoint lists CSI volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). Specify this as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response includes a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+## Read Dynamic Host Volume
+
+This endpoint reads information about a specific dynamic host volume.
+
+| Method | Path                         | Produces           |
+|--------|------------------------------|--------------------|
+| `GET`  | `/v1/volume/host/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+|------------------|------------------------------|
+| `YES`            | `namespace:host-volume-read` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/host/c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f
+```
+
+### Sample Response
+
+```json
+{
+  "Allocations": [],
+  "CapacityBytes": 49283072,
+  "CreateIndex": 11,
+  "CreateTime": 1736191993011594200,
+  "HostPath": "/run/nomad/dev/alloc_mounts/c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+  "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+  "ModifyIndex": 12,
+  "ModifyTime": 1736191993011594200,
+  "Name": "external-plugin",
+  "Namespace": "default",
+  "NodeID": "670cb259-bc26-653b-e316-655af04ad260",
+  "NodePool": "default",
+  "Parameters": {
+    "hello": "world"
+  },
+  "PluginID": "example-plugin-mkfs",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    }
+  ],
+  "RequestedCapacityMaxBytes": 50000000,
+  "RequestedCapacityMinBytes": 50000000,
+  "State": "ready"
+}
+```
+
+## Create Dynamic Host Volume
+
+This endpoint creates a dynamic host volume and registers it with Nomad.
+
+The response body includes the volume definition with the `ID` and `NodeID`
+fields populated. Making the same request without the ID creates a new volume on
+a different node. Making a request with the ID set updates the volume to the new
+parameters, if possible.
+
+| Method | Path                     | Produces           |
+|--------|--------------------------|--------------------|
+| `PUT`  | `/v1/volume/host/create` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                                                                                   |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-create` or<br/>`namespace:host-volume-write`.<br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Volume` `(Volume: <required>)` - Specifies the JSON definition of the host
+  volume. You should include the ID field if you are updating an existing
+  volume.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volume": {
+    "Name": "example",
+    "Namespace": "default",
+    "NodePool": "prod",
+    "PluginID": "mkdir",
+    "RequestedCapacityMinBytes": 10737418240,
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "Parameters": {
+      "foo": "bar"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/host/create
+```
+
+### Sample Response
+
+```json
+{
+  "Volume": {
+    "Allocations": [],
+    "CapacityBytes": 21474836480,
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "CreateIndex": 11,
+    "CreateTime": 1736191993011594200,
+    "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+    "ModifyIndex": 11,
+    "ModifyTime": 1736191993011594200,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "45460554-cc67-11ef-84b7-33d383a55487",
+    "NodePool": "prod",
+    "Parameters": {
+      "foo": "bar"
+    },
+    "PluginID": "mkdir",
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapacityMinBytes": 10737418240,
+    "State": "pending"
+  },
+  "Warnings": null
+}
+```
+
+## Register Dynamic Host Volume
+
+This endpoint registers an existing dynamic host volume with Nomad.
+
+| Method | Path                       | Produces           |
+|--------|----------------------------|--------------------|
+| `PUT`  | `/v1/volume/host/register` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                                                                                     |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-register` or<br/>`namespace:host-volume-write`.<br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Volume` `(Volume: <required>)` - Specifies the JSON definition of the host
+  volume. You should include the ID field if you are updating an existing
+  volume.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows registering a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volume": {
+    "Name": "example",
+    "Namespace": "default",
+    "NodePool": "prod",
+    "PluginID": "mkdir",
+    "RequestedCapacityMinBytes": 10737418240,
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "Parameters": {
+      "foo": "bar"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/host/register
+```
+
+### Sample Response
+
+```json
+{
+  "Volume": {
+    "Allocations": [],
+    "CapacityBytes": 21474836480,
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "CreateIndex": 11,
+    "CreateTime": 1736191993011594200,
+    "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+    "ModifyIndex": 31,
+    "ModifyTime": 1736191993721594200,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "45460554-cc67-11ef-84b7-33d383a55487",
+    "NodePool": "prod",
+    "Parameters": {
+      "foo": "bar"
+    },
+    "PluginID": "mkdir",
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapacityMinBytes": 10737418240,
+    "State": "ready"
+  },
+  "Warnings": null
+}
+```
+
+## Delete Dynamic Host Volume
+
+This endpoint deletes a dynamic host volume, and deregisters it from Nomad. It
+is an error to delete a volume that is in use.
+
+| Method   | Path                                | Produces           |
+|----------|-------------------------------------|--------------------|
+| `DELETE` | `/v1/volume/host/:volume_id/delete` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                        |
+|------------------|---------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-write` or<br/>`namespace:host-volume-delete` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/host/ba97ef42-cc68-11ef-a2e7-ffddaecbdb89
+```
+
+## List Task Group Host Volume Claims
+
+This endpoint lists host volume claims made by task groups that
+requested "sticky" volumes.
+
+| Method | Path                 | Produces           |
+|--------|----------------------|--------------------|
+| `GET`  | `/v1/volumes/claims` | `application/json` |
+
+The following table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+|------------------|------------------------------|
+| `YES`            | `namespace:host-volume-read` |
+
+### Parameters
+- `claim_id` `(string: "")` - Specifies the prefix of a task group volume
+claim ID to perform the list. Specify this as a query string parameter.
+
+- `namespace` `(string: <required>)` - Specifies the namespace used to filter
+task group volume claims.
+
+- `job_id` `(string: "")` - Specifies the job ID used to filter task group
+volume claims.
+
+- `task_group` `(string: "")` - Specifies the task group name used to filter
+task group volume claims.
+
+- `volume_name` `(string: "")` - Specifies the volume name used to filter
+task group volume claims.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+`next_token` parameter accepts a string returned in a previous response's
+`NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+return for this request. The response includes a `NextToken` field that
+you can pass to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/claims
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocID": "34e44207-0cf3-a24d-4bbe-6c91cec642ce",
+    "CreateIndex": 15,
+    "ID": "75c417b5-cf90-86e4-8ffc-d18f445e0721",
+    "JobID": "example",
+    "ModifyIndex": 15,
+    "Namespace": "default",
+    "TaskGroupName": "echo",
+    "VolumeID": "0bb42da3-7e09-6937-a83d-69d5c9bfce30",
+    "VolumeName": "sticky-volume"
+  }
+]
+```
+
+## Delete Task Group Host Volume Claims
+
+This endpoint deletes host volume claims made by task groups that
+requested "sticky" volumes.
+
+| Method   | Path                          | Produces       |
+|----------|-------------------------------|----------------|
+| `DELETE` | `/v1/volumes/claim/:claim_id` | `(empty body)` |
+
+The following table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                  |
+|------------------|-------------------------------|
+| `NO`             | `namespace:host-volume-write` |
+
+### Parameters
+
+- `claim_id` `(string: <required>)` - Specifies the ID of task group host volume claim
+to delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/claim/75c417b5-cf90-86e4-8ffc-d18f445e0721
+```
+
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[Create CSI Volume]: #create-csi-volume
+[Volume Expansion]: /nomad/docs/other-specifications/volume/csi#volume-expansion
+[csi-volume-spec]: /nomad/docs/other-specifications/volume/csi  
diff --git a/content/nomad/v1.10.x/content/commands/acl/auth-method/create.mdx b/content/nomad/v1.10.x/content/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..98270e7a53
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/auth-method/create.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method create command reference'
+description: |
+  The `nomad acl auth-method create` command creates new access control list (ACL) authentication methods. Set name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method create` command reference
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration][] in JSON format. You may provide '-'
+  to send the config through stdin, or prefix a file path with '@' to indicate
+  that the config should be loaded from the file.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+This example config uses a private key JWT [client assertion][]
+instead of a client secret.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-keycloak-instance.com/realms/nomad",
+  "OIDCClientID": "my-great-client-id",
+  "OIDCClientAssertion": {
+    "KeySource": "nomad"
+  },
+  "BoundAudiences": [
+    "my-great-client-id"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ListClaimMappings": {
+    "groups": "groups"
+  }
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
+[client assertion]: /nomad/api-docs/acl/auth-methods#oidcclientassertion
diff --git a/content/nomad/v1.10.x/content/commands/acl/auth-method/delete.mdx b/content/nomad/v1.10.x/content/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..74e55c0d40
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method delete command reference'
+description: |
+  The `nomad auth-method delete command` deletes an existing access control list (ACL) authentication method.
+---
+
+# `nomad`acl auth-method delete` command reference
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/auth-method/info.mdx b/content/nomad/v1.10.x/content/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..ea3824cdc7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/auth-method/info.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method info command reference'
+description: |
+  The `nomad auth-method info` command fetches information about an existing access control list (ACL) authentication method. Review name, type, description, locality, time to live (TTL), token name format, and authentication method configuration.
+---
+
+# `nomad acl auth-method info` command reference
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/auth-method/list.mdx b/content/nomad/v1.10.x/content/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..e50819b59d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/auth-method/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method list command reference'
+description: |
+  The `nomad acl auth-method list` command lists existing access control list (ACL) authentication methods.
+---
+
+# `nomad acl auth-method list` command reference
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/auth-method/update.mdx b/content/nomad/v1.10.x/content/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..64189e7ddb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/auth-method/update.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method update command reference'
+description: |
+  The `nomad acl auth-method update` command updates an existing access control list (ACL) authentication method.  Modify name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method update` command reference
+
+The `acl auth-method update` command is used to update existing ACL Auth
+Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and
+  `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration][] in JSON format. You may provide '-'
+  to send the config through stdin, or prefix a file path with '@' to indicate
+  that the config should be loaded from the file.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -token-name-format '${auth_method_name}-${value.user}' -config @config.json example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = global
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_name}-${value.user}
+Default             = false
+Create Index        = 14
+Modify Index        = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.10.x/content/commands/acl/binding-rule/create.mdx b/content/nomad/v1.10.x/content/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..b784b04d97
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule create command reference'
+description: |
+  The `nomad acl binding-rule create` command creates new access control list (ACL) binding rules. Set a description, associated authentication method, selector expression, or bind name. Configure role, policy, or management bind type.
+---
+
+# `nomad acl binding-rule create` command reference
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.10.x/content/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..a9fada487b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule delete command reference'
+description: |
+  The `nomad acl binding-rule delete` command delete an existing access control list (ACL) binding rule.
+---
+
+# `nomad acl binding-rule delete` command reference
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/binding-rule/info.mdx b/content/nomad/v1.10.x/content/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..a437ecc7d7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule info command reference'
+description: |
+  The `nomad acl binding-rule info` command fetches information about an existing access control list (ACL) binding rule. Review ID, description, authentication method, selector, bind type, bind name, and time to live (TTL).
+---
+
+# `nomad acl binding-rule info` command reference
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/binding-rule/list.mdx b/content/nomad/v1.10.x/content/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..4d2238f803
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule list command reference'
+description: |
+  The `nomad acl binding-rule list` command displays access control list (ACL) binding rules.
+---
+
+# `nomad acl binding-rule list` command reference
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/binding-rule/update.mdx b/content/nomad/v1.10.x/content/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..cdc6eec37d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule update command reference'
+description: |
+    The `nomad acl binding-rule update` command modifies an existing access control list (ACL) binding rule. Update description, selector expression, bind name, and bind type.
+---
+
+# `nomad acl binding-rule update` command reference
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/bootstrap.mdx b/content/nomad/v1.10.x/content/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..a59b8b71a0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'nomad acl bootstrap command reference'
+description: |
+  The `nomad acl bootstrap` command creates the initial access control list (ACL) token. Nomad generates the token unless you provide a user-generated token.
+---
+
+# `nomad acl bootstrap` command reference
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways:
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-".
+Please make sure you secure this token in an appropriate manner as it could be written to your terminal history.
+
+## Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/index.mdx b/content/nomad/v1.10.x/content/commands/acl/index.mdx
new file mode 100644
index 0000000000..f58e2a91b6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/index.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'nomad acl command reference'
+description: |
+  The `nomad acl` command interacts with access control list (ACL) policies, roles, tokens, binding rules, and authentication methods.
+---
+
+# `nomad acl` command reference
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+```plaintext
+nomad acl <subcommand> [options]
+```
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl policy self`][policyself] - List ACL policies attached to the current workload
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/commands/acl/bootstrap
+[authmethodcreate]: /nomad/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/commands/acl/auth-method/info
+[authmethodlist]: /nomad/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/commands/acl/binding-rule/update
+[policyapply]: /nomad/commands/acl/policy/apply
+[policydelete]: /nomad/commands/acl/policy/delete
+[policyinfo]: /nomad/commands/acl/policy/info
+[policylist]: /nomad/commands/acl/policy/list
+[policyself]: /nomad/commands/acl/policy/self
+[tokencreate]: /nomad/commands/acl/token/create
+[tokenupdate]: /nomad/commands/acl/token/update
+[tokendelete]: /nomad/commands/acl/token/delete
+[tokeninfo]: /nomad/commands/acl/token/info
+[tokenlist]: /nomad/commands/acl/token/list
+[tokenself]: /nomad/commands/acl/token/self
+[rolecreate]: /nomad/commands/acl/role/create
+[roleupdate]: /nomad/commands/acl/role/update
+[roledelete]: /nomad/commands/acl/role/delete
+[roleinfo]: /nomad/commands/acl/role/info
+[rolelist]: /nomad/commands/acl/role/list
+[secure-guide]: /nomad/docs/secure/acl
+[federated]: /nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.10.x/content/commands/acl/policy/apply.mdx b/content/nomad/v1.10.x/content/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..b804329dcd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/policy/apply.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl policy apply command reference'
+description: |
+  The `nomad acl policy apply` command creates or updates an  access control list (ACL) policy. Set description, job, namespace, group, and task.
+---
+
+# `nomad acl policy apply` command reference
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set. Refer to [Workload Associated ACL Policies][] for more details.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.10.x/content/commands/acl/policy/delete.mdx b/content/nomad/v1.10.x/content/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..4d8dba5607
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad acl policy delete command reference'
+description: |
+  The `nomad acl policy delete` command deletes an access control list (ACL) policy.
+---
+
+# `nomad acl policy delete` command reference
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/policy/info.mdx b/content/nomad/v1.10.x/content/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..77e68fd145
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/policy/info.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad acl policy info command reference'
+description: >
+  The `nomad acl policy info` command fetches information on an access control list (ACL) policy. Review name, description, and workload, as well as access control list (ACL) policies and rules.
+---
+
+# `nomad acl policy info` command reference
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.10.x/content/commands/acl/policy/list.mdx b/content/nomad/v1.10.x/content/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..40db4bbcfe
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad acl policy list command reference'
+description: |
+  The `nomad acl policy list` command displays available access control list (ACL) policies.
+---
+
+# `nomad acl policy list` command reference
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/policy/self.mdx b/content/nomad/v1.10.x/content/commands/acl/policy/self.mdx
new file mode 100644
index 0000000000..3b9260e903
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/policy/self.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad acl policy self command reference'
+description: >
+  The `nomad acl policy self` command fetches information about the currently set access control list (ACL) policies available to the authenticated request.
+---
+
+# `nomad acl policy self` command reference
+
+The `nomad acl policy self` command fetches information about the currently
+set ACL policies attached to the workload or ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl policy self [options]
+```
+
+## Options
+
+- `-json` : Output the ACL policies in a JSON format.
+
+- `-t` : Format and display the ACL policies using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL policies attached to the workload.
+
+```shell-session
+$ echo $NOMAD_TOKEN
+eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA
+$ nomad acl policy self
+Name          Job ID  Group Name  Task Name
+nomad-policy  nomad   nomad       <not specified>
+$ nomad acl policy self -json
+[
+    {
+        "CreateIndex": 22,
+        "Description": "",
+        "JobACL": {
+            "Group": "nomad",
+            "JobID": "nomad",
+            "Namespace": "default",
+            "Task": ""
+        },
+        "ModifyIndex": 22,
+        "Name": "nomad-policy"
+    }
+]
+```
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/role/create.mdx b/content/nomad/v1.10.x/content/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..16bdf70ce5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/role/create.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad acl role create command reference'
+description: |
+    The `nomad acl role create` command creates an access control list (ACL) role. Set name, description, and associated policy.
+---
+
+# `nomad acl role create` command reference
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/role/delete.mdx b/content/nomad/v1.10.x/content/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..429a349b10
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/role/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl role delete command reference'
+description: |
+  The `nomad acl role delete` command deletes an access control list (ACL) role.
+---
+
+# `nomad acl role delete` command reference
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/role/info.mdx b/content/nomad/v1.10.x/content/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..708662f664
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/role/info.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role info command reference'
+description: |
+  The `nomad acl role info` command fetches information about an access control list (ACL) role. Review ID, name, description, and policies.
+---
+
+# `nomad acl role info` command reference
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/role/list.mdx b/content/nomad/v1.10.x/content/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..74fa739f1c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/role/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl role list command reference'
+description: |
+    The `nomad acl role list` displays access control list (ACL) roles.
+---
+
+# `nomad acl role list` command reference
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/role/update.mdx b/content/nomad/v1.10.x/content/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..cb5cc7a31d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/role/update.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role update command reference'
+description: |
+    The `nomad acl role update` command modifies an access control list (ACL) role. Modify name, description, and associated policy.
+---
+
+# `nomad acl role update` command reference
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/create.mdx b/content/nomad/v1.10.x/content/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..fb9f697c6a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'nomad acl token create command reference'
+description: |
+  The `nomad acl token create` command creates an access control list (ACL) token. Set name, client or management type, policy, role, time to live (TTL), and whether the policy should be global.
+---
+
+# `nomad acl token create` command reference
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## Create options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/delete.mdx b/content/nomad/v1.10.x/content/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..1643646792
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad acl token delete command reference'
+description: |
+  The `nomad acl token delete` command deletes an access control list (ACL) token.
+---
+
+# `nomad acl token delete` command reference
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/info.mdx b/content/nomad/v1.10.x/content/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..8f3b4d14cc
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/info.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad acl token info command reference'
+description: >
+  The `nomad acl token info` command fetches information about an access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token info` command reference
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/list.mdx b/content/nomad/v1.10.x/content/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..033ec225b2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl token list command reference'
+description: |
+  The `nomad acl token list` command displays access control list (ACL) tokens.
+---
+
+# `nomad acl token list` command reference
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## List options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/self.mdx b/content/nomad/v1.10.x/content/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..92bb917b06
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/self.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad acl token self command reference'
+description: >
+  The `nomad acl token self` command fetches information about the currently set access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token self` command reference
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
+
+The command also detects if the current Nomad token is a workload identity
+JWT and respond with a hint if that's the case.
+
+```shell-session
+$ echo $NOMAD_TOKEN
+eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA
+$ nomad acl token self
+No ACL token found but there are ACL policies attached to this workload identity. You can query them with acl policy self command.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/acl/token/update.mdx b/content/nomad/v1.10.x/content/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..561709f082
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/acl/token/update.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl token update command reference'
+description: |
+  The `nomad acl token update` command modifies an access control list (ACL) token. Update name, client or management type, policy, and role.
+---
+
+# `nomad acl token update` command reference
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## Update options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens. If any policies are
+  specified, they completely replace the policies on the existing token.
+
+- `-role-id`: ID of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+- `-role-name`: Name of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/agent-info.mdx b/content/nomad/v1.10.x/content/commands/agent-info.mdx
new file mode 100644
index 0000000000..f1f5fa8572
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'nomad agent-info command reference'
+description: |
+  The `nomad agent-info` command retrieves metrics and status information for a running agent. Use this command to review agent data from the client, nomad, serf, raft, and runtime subsystems.
+---
+
+# `nomad agent-info` command reference
+
+The `nomad agent-info` command retrieves metrics and status information for a
+running agent. The information returned pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, the `nomad agent-info` command retrieves
+information from the following subsystems:
+
+- Client: Status of the local Nomad client
+- Nomad: Status of the local Nomad server
+- Serf: Gossip protocol metrics and information
+- Raft: Status information about the Raft consensus protocol
+- Runtime: Various metrics from the runtime environment
+
+## Example
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/agent.mdx b/content/nomad/v1.10.x/content/commands/agent.mdx
new file mode 100644
index 0000000000..ebc840ab16
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/agent.mdx
@@ -0,0 +1,267 @@
+---
+layout: docs
+page_title: 'nomad agent command reference'
+description: |
+  The `nomad agent` command starts the Nomad agent, which handles client or server functionality, including exposing interfaces for client consumption and running jobs. The agent runs until it receives an interrupt signal.
+---
+
+# `nomad agent` command reference
+
+The `nomad agent` command starts the Nomad agent, which handles client or server
+functionality, including exposing interfaces for client consumption and running
+jobs. The agent runs until it receives an interrupt signal.
+
+Refer to [Operating Nomad agents] and [Nomad agent configuration] for more
+information on how to use this command and the options it has.
+
+## Usage
+
+If you are running Nomad on Linux, you need to run client agents as root, or
+with `sudo`, so that cpuset accounting and network namespaces work correctly.
+
+```plaintext
+nomad agent [options]
+```
+
+## Options
+
+We recommend configuring a Nomad agent with configuration files. Refer to [Nomad
+agent configuration] for details.
+
+You may, however, may pass the following configuration options as CLI arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir][] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled][] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token][] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr][] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect][] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address][] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth][] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise][] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file][] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file][] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise][]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join][] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name][]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name][] config option.
+
+- `-consul-client-failures-before-critical=<num>`: Equivalent to the
+  [client_failures_before_critical][] config option.
+
+- `-consul-client-failures-before-warning=<num>`: Equivalent to the
+  [client_failures_before_warning][] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file][] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name][]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name][] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name][] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name][] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join][] config
+  option.
+
+- `-consul-server-failures-before-critical=<num>`: Equivalent to the
+  [server_failures_before_critical][] config option.
+
+- `-consul-server-failures-before-warning=<num>`: Equivalent to the
+  [server_failures_before_warning][] config option.
+
+- `-consul-ssl`: Equivalent to the [ssl][] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token][] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl][] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir][] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter][] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul service mesh. It may be
+  used with `-dev-consul` to configure default workload identities for Consul.
+  This mode is supported only on Linux as root.
+
+- `-dev-consul`: Starts the agent in development mode with a default Consul
+  configuration for Nomad workload identity. It may be used with `-dev-connect`
+  to configure the agent for Consul Service Mesh.
+
+- `-dev-vault`: Starts the agent in development mode with a default Vault
+  configuration for Nomad workload identity.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview][] for
+  more details.
+
+- `-eventlog`: Equivalent to the [eventlog.enabled][] config option.
+
+- `-eventlog-level`: Equivalent to the [eventlog.level][] config option.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level][] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location][] config option.
+
+- `-log-json`: Equivalent to the [log_json][] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta][] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface][] config option.
+
+- `-node=<name>`: Equivalent to the [name][] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class][]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool][]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir][] config option.
+
+- `-region=<region>`: Equivalent to the [region][] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave][] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval][] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max][] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers][] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir][] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_failures_before_critical]: /nomad/docs/configuration/consul#client_failures_before_critical
+[client_failures_before_warning]: /nomad/docs/configuration/consul#client_failures_before_warning
+[server_failures_before_critical]: /nomad/docs/configuration/consul#server_failures_before_critical
+[server_failures_before_warning]: /nomad/docs/configuration/consul#server_failures_before_warning
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/docs/secure/traffic/gossip-encryption
+[eventlog.enabled]: /nomad/docs/configuration#eventlog_enabled
+[eventlog.level]: /nomad/docs/configuration#eventlog_level
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[Operating Nomad agents]: /nomad/docs/deploy/nomad-agent
+[Nomad agent configuration]: /nomad/docs/configuration
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
+
diff --git a/content/nomad/v1.10.x/content/commands/alloc/checks.mdx b/content/nomad/v1.10.x/content/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..d078510b8c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'nomad alloc checks command reference'
+description: |
+  The `nomad alloc checks` command displays service health check status information for an allocation.
+---
+
+# `nomad alloc checks` command reference
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability
+for the allocation's namespace. The 'list-jobs' capability is required to run the
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/exec.mdx b/content/nomad/v1.10.x/content/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..0513ef9d7a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/exec.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: 'nomad alloc exec command reference'
+description: |
+  The `nomad alloc exec` runs a command inside a running task allocation, which is useful for debugging. Execute commands with or without an interactive shell inside the allocation.
+---
+
+# `nomad alloc exec` command reference
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+### Disable remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+### Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+## Options
+
+- `-task=<task-name>`: Sets the task to exec command in.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` `<escape_char>`: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.10.x/content/commands/alloc/fs.mdx b/content/nomad/v1.10.x/content/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..689170f24b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/fs.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: 'nomad alloc fs command reference'
+description: |
+  The `nomad alloc fs` lets you navigate an allocation working directory on a Nomad client.
+---
+
+# `nomad alloc fs` command reference
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad prefers selecting a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad uses a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+## Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best effort number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/index.mdx b/content/nomad/v1.10.x/content/commands/alloc/index.mdx
new file mode 100644
index 0000000000..c4af5cea60
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/index.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'nomad alloc command reference'
+description: |
+  The `nomad alloc` commands interact with allocations. Access allocation directories, display status and health checks, stream task logs, run commands inside an allocation, and signal a running allocation. You can also stop, reschedule, and restart a running allocation.
+---
+
+# `nomad alloc` command reference
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+```plaintext
+nomad alloc <subcommand> [options]
+```
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/logs.mdx b/content/nomad/v1.10.x/content/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..012bf5cbbb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/logs.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'nomad alloc logs command reference'
+description: |
+  The `nomad alloc logs` command streams the task logs from an allocation.
+---
+
+# `nomad alloc logs` command reference
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad prefers selecting a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad uses a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-task=<task-name>`: Specify the task to view the logs.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/pause.mdx b/content/nomad/v1.10.x/content/commands/alloc/pause.mdx
new file mode 100644
index 0000000000..619d769608
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/pause.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'nomad alloc pause command reference'
+description: |
+  The `nomad alloc pause` command overrides the schedule for tasks using time-based execution, forcing the task to either stop or run.
+---
+
+# `nomad alloc pause` command reference
+
+Override the schedule for tasks using time based execution.
+
+<EnterpriseAlert />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+## Usage
+
+```plaintext
+nomad alloc pause [options] <allocation> <command>
+```
+
+The `alloc pause` command allows a user to override the schedule for tasks
+that use time based execution. A user may override a task's
+[`schedule`][schedule] and force it to run or stop. The `schedule` will be
+ignored until a user resets the override.
+
+When ACLs are enabled, this command requires the `job-submit` capability for
+the allocation's namespace.
+
+## Options
+
+- `-state`: Override the current scheduled task state to be the specified state
+  or reset to the scheduled state. Must be one of `pause`, `run`, or
+  `scheduled`. When set to `pause` the task is halted. When set to `run` the
+  task is started. When set to `scheduled` the task respects its
+  [`schedule`][schedule].
+
+- `-status`: Get the current time based task execution state.
+
+- `-task`: Override the schedule of the specified task. May also be specified
+  as a positional argument.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+The following command stops the `schedtask` task of the allocation `4d37a9d1`
+overriding the task's [`schedule`][schedule] block:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command runs the task overriding the tasks current state or
+schedule:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command returns the task to its [`schedule`][schedule]:
+
+```shell-session
+$ nomad alloc pause -state=scheduled 4d37a9d1 schedtask
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[schedule]: /nomad/docs/job-specification/schedule
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.10.x/content/commands/alloc/restart.mdx b/content/nomad/v1.10.x/content/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..f0c5e73057
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad alloc restart command reference'
+description: |
+  The `nomad alloc restart` command restarts a running task or an entire allocation.
+---
+
+# `nomad alloc restart` command reference
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/signal.mdx b/content/nomad/v1.10.x/content/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..aca5f5e3a1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad alloc signal command reference'
+description: |
+  The `nomad alloc signal` command sends a signal to a running allocation or task.
+---
+
+# `nomad alloc signal` command reference
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/status.mdx b/content/nomad/v1.10.x/content/commands/alloc/status.mdx
new file mode 100644
index 0000000000..eff3171fe0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/status.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: 'nomad alloc status command reference'
+description: |
+  The `nomad alloc status` command display status and metadata about existing allocations and their tasks.
+---
+
+# `nomad alloc status` command reference
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full-length IDs, exact timestamps, and placement metrics.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+- `-ui` : Open the allocation status page in the browser.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+The `-verbose` flag includes information about the scheduler's placement
+decision, including the number of nodes evaluated and rejected, and the scoring
+of each node considered.
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-affinity  node-reschedule-penalty  final score
+43c0b14e-7f96-e432-a7da-06605257ce0c  0.0238   0                  0              0                        0.0238
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/alloc/stop.mdx b/content/nomad/v1.10.x/content/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..1d41a1afc2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/alloc/stop.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad alloc stop command reference'
+description: |
+  The `nomad alloc stop` command perform an in-place restart of an entire allocation or an individual task.
+---
+
+# `nomad alloc stop` command reference
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped, otherwise, a list of
+matching allocs and information will be displayed. If the stopped allocation
+belongs to a service or batch job they will rescheduled according to their
+reschedule policy. [System allocs will not][] and will show up as completed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[system allocs will not]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/commands/config/index.mdx b/content/nomad/v1.10.x/content/commands/config/index.mdx
new file mode 100644
index 0000000000..a059419873
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/config/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'nomad config command reference'
+description: |
+  The `nomad config` command interacts with configurations. Validate configuration files.
+---
+
+# `nomad config` command reference
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+```plaintext
+nomad config <subcommand> [options]
+```
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.10.x/content/commands/config/validate.mdx b/content/nomad/v1.10.x/content/commands/config/validate.mdx
new file mode 100644
index 0000000000..98787632c0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'nomad config validate command reference'
+description: |
+  The `nomad config validate` command validates Nomad configuration files so you can test Nomad configuration without starting the agent.
+---
+
+# `nomad config validate` command reference
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/deployment/fail.mdx b/content/nomad/v1.10.x/content/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..7b07211ab1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad deployment fail command reference'
+description: |
+  The `nomad deployment fail` command manually fails a deployment, which stops the placement of new allocations.
+---
+
+# `nomad deployment fail` command reference
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/deployment/index.mdx b/content/nomad/v1.10.x/content/commands/deployment/index.mdx
new file mode 100644
index 0000000000..b2e46d0175
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad deployment command reference'
+description: |
+  The `nomad deployment` command interacts with deployments. List deployments, fetch status, and promote canaries. Pause, resume, and fail deployments.
+---
+
+# `nomad deployment` command reference
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+```plaintext
+nomad deployment <subcommand> [options]
+```
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/commands/deployment/list 'List all deployments'
+[pause]: /nomad/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.10.x/content/commands/deployment/list.mdx b/content/nomad/v1.10.x/content/commands/deployment/list.mdx
new file mode 100644
index 0000000000..dca7210120
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad deployment list command reference'
+description: |
+  The `nomad deployment list` command lists deployments.
+---
+
+# `nomad deployment list` command reference
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/deployment/pause.mdx b/content/nomad/v1.10.x/content/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..9f212712c0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/pause.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad deployment pause command reference'
+description: >
+  The `nomad deployment pause` command pauses a deployment and does not allow new allocations.
+---
+
+# `nomad deployment pause` command reference
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/deployment/promote.mdx b/content/nomad/v1.10.x/content/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..538a8ef49f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'nomad deployment promote command reference'
+description: |
+  The `nomad deployment promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad deployment promote` command reference
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`job revert`]: /nomad/commands/job/revert
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/deployment/resume.mdx b/content/nomad/v1.10.x/content/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..f329148a0f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad deployment resume command reference'
+description: |
+  The `nomad deployment resume` command resumes a paused deployment.
+---
+
+# `nomad deployment resume` command reference
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/deployment/status.mdx b/content/nomad/v1.10.x/content/commands/deployment/status.mdx
new file mode 100644
index 0000000000..0eeaed245e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/status.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'nomad deployment status command reference'
+description: |
+  The `nomad deployment status` command displays the status of a deployment.
+---
+
+# `nomad deployment status` command reference
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+- `-ui`: Open the deployment page in the browser.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully
+Windows compatible so there may be some formatting differences (different margins, no spinner
+indicating deployment is in progress).
+
+## General options
+
+@include 'general_options.mdx'
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
diff --git a/content/nomad/v1.10.x/content/commands/deployment/unblock.mdx b/content/nomad/v1.10.x/content/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..fab3def1a4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'nomad deployment unblock command reference'
+description: |
+  The`nomad deployment unblock` command marks a blocked multi-region deployment as successful so you can force completion when there is a failed peer region.
+---
+
+# `nomad deployment unblock` command reference
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[federated regions]: //nomad/docs/deploy/clusters/federate-regions
diff --git a/content/nomad/v1.10.x/content/commands/eval/delete.mdx b/content/nomad/v1.10.x/content/commands/eval/delete.mdx
new file mode 100644
index 0000000000..a504fc2842
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad eval delete command reference'
+description: |
+  The `nomad eval delete` command deletes an evaluation by ID or a group of evaluations that match a filter.
+---
+
+# `nomad eval delete` command reference
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfully deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfully deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfully deleted 23 evaluations
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[scheduler_get_config]: /nomad/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.10.x/content/commands/eval/index.mdx b/content/nomad/v1.10.x/content/commands/eval/index.mdx
new file mode 100644
index 0000000000..8911c507c7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/eval/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad eval command reference'
+description: |
+  The `nomad eval` command interact with evaluations. Fetch status, delete an evaluation, and list all evaluations.
+---
+
+# `nomad eval` command reference
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+```plaintext
+nomad eval <subcommand> [options]
+```
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/commands/eval/delete 'Delete evals'
+[list]: /nomad/commands/eval/list 'List all evals'
+[status]: /nomad/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.10.x/content/commands/eval/list.mdx b/content/nomad/v1.10.x/content/commands/eval/list.mdx
new file mode 100644
index 0000000000..d94cdc0578
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/eval/list.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'nomad eval list command reference'
+description: |
+  The `nomad eval list` command displays a list of all evaluations or evaluations that match a filter.
+---
+
+# `nomad eval list` command reference
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+- `-ui`: Open the evaluations page in the browser.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/eval/status.mdx b/content/nomad/v1.10.x/content/commands/eval/status.mdx
new file mode 100644
index 0000000000..3bd98a8919
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/eval/status.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'nomad eval status command reference'
+description: >
+  The `nomad eval status` command displays the status and potential failed
+  allocations of an evaluation. Use with the `monitor` flag to start an interactive monitoring session.
+---
+
+# `nomad eval status` command reference
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+- `-ui`: Open the evaluation in the browser.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/fmt.mdx b/content/nomad/v1.10.x/content/commands/fmt.mdx
new file mode 100644
index 0000000000..db766ea90c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/fmt.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad fmt command reference'
+description: |
+  The `nomad fmt` commands rewrites Nomad configuration and job specification
+   files to canonical format. Use this command to improve readability and enforce consistency of style in Nomad files.
+---
+
+# `nomad fmt` command reference
+
+The `nomad fmt` command rewrites Nomad configuration and job specification files
+to canonical format. Use this command to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [options] paths ...
+```
+
+If a path is a directory, the command recursively formats all files with
+`.nomad` and `.hcl` extensions in the directory. If you provide a single dash
+(-) as an argument, the `nomad fmt` command reads from standard input and
+writes the processed text to standard output.
+
+The `nomad fmt` command checks the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 job specification results in errors.
+
+## Options
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.10.x/content/commands/index.mdx b/content/nomad/v1.10.x/content/commands/index.mdx
new file mode 100644
index 0000000000..39da9db98a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/index.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: Nomad command-line interface (CLI) reference
+description: >
+  The Nomad command-line interface (CLI) interacts with a Nomad cluster. This page contains reference information on how to install CLI autocomplete, configure remote usage, and specify CLI options. Review connection, access control list (ACL), mutual TLS (mTLS), and license environment variables.
+---
+
+# Nomad command-line interface (CLI) reference
+
+The Nomad CLI is a well-behaved command-line application. In erroneous cases,
+the CLI returns a non-zero exit status. To view a list of available commands,
+run the `nomad` command with no arguments, `-h`, or `--help`. To access help for
+any specific subcommand, run the subcommand with the `-h` argument.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete.
+
+To install autocomplete, run the `nomad` command with the
+`-autocomplete-install` option.
+
+```shell-session
+$ nomad -autocomplete-install
+```
+
+To uninstall autocomplete, run the `nomad` command with the
+`-autocomplete-uninstall` option.
+
+```shell-session
+$ nomad -autocomplete-uninstall
+```
+
+## Command contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise. For example, the `nomad job run` command runs a new job and the
+`nomad status` command queries information about existing jobs. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote usage
+
+You may use the Nomad CLI to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The Nomad address must be reachable from your local machine. If the Nomad
+port is exposed to the public internet, we recommend configuring TLS. Refer to
+the [`tls` block in agent configuration] for details.
+
+### Environment variables
+
+Nomad can use environment variables to configure command-line tool options. You
+may override these environment variables with individual flags. Except where
+noted, these variables influence the behavior of the Nomad CLI and should not be
+set for Nomad agents.
+
+#### Connection environment variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`. For unix sockets, as with the [task API][],
+  the format is either `unix:/path/to/api.sock` or `unix:///path/to/api.sock`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### Access control list (ACL) environment variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI environment variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+- `NOMAD_CLI_SHOW_HINTS` - Enables ui-hints in common CLI command output.
+
+#### Mutual TLS (mTLS) environment variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise license environment variables
+
+These environment variables influence the Nomad Enterprise license
+configuration. These values are only used for Nomad Enterprise agents, not the
+Nomad CLI.
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
+
+
+[task API]: /nomad/api-docs/task-api
+[`tls` block in agent configuration]: /nomad/docs/configuration/tls
diff --git a/content/nomad/v1.10.x/content/commands/job/action.mdx b/content/nomad/v1.10.x/content/commands/job/action.mdx
new file mode 100644
index 0000000000..6adb072e99
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/action.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'nomad job action command reference'
+description: |
+  The `nomad job action` command executes predefined actions from a job
+  specification in a running task context.
+---
+
+# `nomad job action` command reference
+
+**Alias: `nomad action`**
+
+The `job action` command allows operators to execute predefined actions declared
+in Nomad job specifications. These actions can be defined at task level and are
+intended for specific operational tasks, such as clearing a cache, or migrating
+a database.
+
+An action may self-terminate upon completion (for example, echoing a string),
+or run for an indeterminate amount of time (for example, watching a blocking
+query). In the latter case, an action can be terminated via escape character
+(such as cmd+c / ctrl+c)
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `alloc-exec`, `read-job`, and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Usage
+
+```plaintext
+nomad job action [options] <action>
+```
+
+The `job action` command requires an action name and accepts two ways of
+specifying where it should run:
+- by passing the job name and known allocation ID along with the name of the action
+- by passing the job, task group, and task name along with the name of the action
+(when the allocation ID is not known). A random allocation will be selected if
+multiple are available.
+
+The action name provided must be defined within a task in the [job specification]
+provided. With sufficient privileges, an execution context will be opened and
+the defined action command will be run. No further input is possible, save for
+the escape character to terminate execution, so interactive commands are not
+supported.
+
+## Options
+
+- `-job`: (Required) Specifies the job containing the predefined action.
+
+- `-alloc`: Specifies the allocation within which the action is to be executed.
+  If omitted, `-group` and `-task` must be provided, and a random
+  allocation for the group will be selected.
+
+- `-task`: Specifies the task within the job where the action is defined. This
+  is required either if `-alloc` provided and your group has multiple tasks,
+  or if you specify a `-group`.
+
+- `-group`: Specifies the task group within the job. If present, a random
+  allocation is selected. If omitted, `-alloc` must be provided.
+
+- `-i`: Pass stdin to the action, defaults to `true`. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to `true` if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` `<escape_char>`: Sets the escape character for sessions with a pty,
+  defaults to '~'. The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot (`.`) closes the connection.
+  Setting the character to `none` disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+Execute an action within a specific task in a job:
+
+```shell-session
+$ nomad action \
+  -group=my-group \
+  -task=my-task \
+  -job=my-job \
+  weather
+
+Toronto: ☁️   +3°C
+```
+
+Execute an action within a specific allocation:
+
+```shell-session
+$ nomad action \
+  -alloc=f200a789-6da4-504c-d131-6181764f101e \
+  -job=actions-demo \
+  echo-time
+
+Running for 0 seconds
+Running for 1 seconds
+Running for 2 seconds
+Running for 3 seconds
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.10.x/content/commands/job/allocs.mdx b/content/nomad/v1.10.x/content/commands/job/allocs.mdx
new file mode 100644
index 0000000000..8dcdf2ee23
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/allocs.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad job allocs command reference'
+description: |
+  The `nomad job allocs`  command lists allocations for a job.
+---
+
+# `nomad job allocs` command reference
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With
+Templates](/nomad/docs/manage/format-cli-output) tutorial for
+more examples of using Go templates to format Nomad CLI output.
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/deployments.mdx b/content/nomad/v1.10.x/content/commands/job/deployments.mdx
new file mode 100644
index 0000000000..e6e2b861af
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad job deployments command reference'
+description: |
+  The `nomad job deployments` command lists deployments for a job.
+---
+
+# `nomad job deployments` command reference
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/dispatch.mdx b/content/nomad/v1.10.x/content/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..58ec328aa9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/dispatch.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: 'nomad job dispatch command reference'
+description: |
+  The `nomad job dispatch` creates an instance of a parameterized job.
+---
+
+# `nomad job dispatch` command reference
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+- `-ui`: Open the dispatched job in the browser.
+
+- `-priority`: Optional integer between 1 and [`job_max_priority`],
+  inclusively that overrides any priority value inherited from the parent job.
+  For general usage information on the priority flag see [job parameters].
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[job parameters]: /nomad/docs/job-specification/job#parameters
diff --git a/content/nomad/v1.10.x/content/commands/job/eval.mdx b/content/nomad/v1.10.x/content/commands/job/eval.mdx
new file mode 100644
index 0000000000..87d414b121
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'nomad job eval command reference'
+description: |
+  The `nomad job eval` command forces an evaluation of a job. Optionally, force placement of failed allocations.
+---
+
+# `nomad job eval` command reference
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/job/history.mdx b/content/nomad/v1.10.x/content/commands/job/history.mdx
new file mode 100644
index 0000000000..3754653335
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/history.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'nomad job history command reference'
+description: |
+  The `nomad job history` command displays the history of a single version or all tracked versions of a job. Optionally display the difference between two versions or tags or differences between each job and its predecessor.
+---
+
+# `nomad job history` command reference
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+- `-diff-version`: Compare the job with a specific version.
+- `-diff-tag`: Compare the job with a specific tag.
+
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
+
+Compare the current job with a specific older version:
+
+```shell-session
+$ nomad job history -version=3 -diff-version=1 example
+Version     = 3
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+```
+
+Compare all job versions with a specific version by tag name:
+
+```shell-session
+$ nomad job history -diff-tag=low-energy-version example
+
+Version     = 3
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "4"
+      Task: "task"
+
+Version         = 2
+Stable          = false
+Submit Date     = 2024-09-09T16:41:53-04:00
+Tag Name        = low-energy-version
+Tag Description = test description
+
+Version     = 1
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "2"
+      Task: "task"
+
+Version     = 0
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "1"
+      Task: "task"
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/index.mdx b/content/nomad/v1.10.x/content/commands/job/index.mdx
new file mode 100644
index 0000000000..c57460cbae
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/index.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad job command reference'
+description: |
+  The `nomad job` command interacts with jobs. Create, validate, and plan a job specification. Display allocations, deployments, history, and status. Execute predefined actions, dispatch parameterized jobs, inspect a job, force the evaluation of a periodic job, scale allocations, and promote canaries. Run, restart, revert, and stop a job.
+---
+
+# `nomad job` command reference
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+```plaintext
+nomad job <subcommand> [options]
+```
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job action`][action] - Execute predefined actions
+- [`job allocs`][allocs] - List allocations for a job
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job init`][init] - Create an example job specification
+- [`job inspect`][inspect] - Inspect the contents of a submitted job
+- [`job periodic force`][periodic force] - Force the evaluation of a periodic job
+- [`job plan`][plan] - Schedule a dry run for a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job restart`][restart] - Restart or reschedule allocations for a job
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job run`][run] - Submit a new job
+- [`job scale`][scale] - Update the number of allocations for a task group in a job
+- [`job scaling-events`][scaling-events] - List the recent scaling events for a job
+- [`job status`][status] - Display status information about a job
+- [`job stop`][stop] - Stop a running job and cancel its allocations
+- [`job tag`][tag] - Tag a job with a version
+- [`job validate`][validate] - Check a job specification for syntax errors
+
+
+[action]: /nomad/commands/job/action 'Execute predefined actions'
+[allocs]: /nomad/commands/job/allocs 'List allocations for a job'
+[deployments]: /nomad/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/commands/job/history 'Display all tracked versions of a job'
+[init]: /nomad/commands/job/init 'Create an example job specification'
+[inspect]: /nomad/commands/job/inspect 'Inspect the contents of a submitted job'
+[periodic force]: /nomad/commands/job/periodic-force 'Force the evaluation of a periodic job'
+[plan]: /nomad/commands/job/plan 'Schedule a dry run for a job'
+[restart]: /nomad/commands/job/restart 'Restart or reschedule allocations for a job'
+[revert]: /nomad/commands/job/revert 'Revert to a prior version of the job'
+[run]: /nomad/commands/job/run 'Submit a new job'
+[status]: /nomad/commands/job/status 'Display status information about a job'
+[scale]: /nomad/commands/job/scale 'Update the number of allocations for a task group in a job'
+[scaling-events]: /nomad/commands/job/scaling-events 'List the recent scaling events for a job'
+[stop]: /nomad/commands/job/stop 'Stop a running job and cancel its allocations'
+[tag]: /nomad/commands/job/tag 'Tag a job with a version'
+[validate]: /nomad/commands/job/validate 'Check a job specification for syntax errors'
+[promote]: /nomad/commands/job/promote
diff --git a/content/nomad/v1.10.x/content/commands/job/init.mdx b/content/nomad/v1.10.x/content/commands/job/init.mdx
new file mode 100644
index 0000000000..85c17ad078
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad job init command reference'
+description: |
+  The `nomad job init` command generates a job specification with example configurations for tasks, task groups, runtime constraints, and resource allocation.
+---
+
+# `nomad job init` command reference
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul service mesh integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/job-declare/task-driver 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.10.x/content/commands/job/inspect.mdx b/content/nomad/v1.10.x/content/commands/job/inspect.mdx
new file mode 100644
index 0000000000..798547e0d2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/inspect.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'nomad job inspect command reference'
+description: |
+  The `nomad job inspect` command displays a complete job definition so you can inspect contents.
+---
+
+# `nomad job inspect` command reference
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format. Cannot be used with `-hcl`.
+- `-hcl`: Output the original HCL submitted with the job. Cannot be used with
+  `-json`.
+- `-with-vars`: Include the original HCL2 variables submitted with the job. Can
+    only be used with `-hcl`.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.10.x/content/commands/job/periodic-force.mdx b/content/nomad/v1.10.x/content/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..a32c962b02
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad job periodic force command reference'
+description: >
+  The `nomad job periodic force` command forces the evaluation of a periodic
+  job. Use this command to immediately run a periodic job, even if it violates the job's `prohibit_overlap` setting.
+---
+
+# `nomad job periodic force` command reference
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.10.x/content/commands/job/plan.mdx b/content/nomad/v1.10.x/content/commands/job/plan.mdx
new file mode 100644
index 0000000000..b57ffb2de8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/plan.mdx
@@ -0,0 +1,243 @@
+---
+layout: docs
+page_title: 'nomad job plan command reference'
+description: |
+  The `nomad job plan` command executes a dry run of a job to determine its effects.
+---
+
+# `nomad job plan` command reference
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+## General options
+
+@include 'general_options.mdx'
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
diff --git a/content/nomad/v1.10.x/content/commands/job/promote.mdx b/content/nomad/v1.10.x/content/commands/job/promote.mdx
new file mode 100644
index 0000000000..de8e2b5366
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'nomad job promote command reference'
+description: |
+  The `nomad job promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad job promote` command reference
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job revert]: /nomad/commands/job/revert
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/job/restart.mdx b/content/nomad/v1.10.x/content/commands/job/restart.mdx
new file mode 100644
index 0000000000..3437e90549
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'nomad job restart command reference'
+description: |
+  The `nomad job restart` command restarts or reschedules allocations for a job.
+---
+
+# `nomad job restart` command reference
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular running job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+You may restart in-place or migrated allocations. When restarting in-place, the
+command may target specific tasks in the allocations, restart only tasks that
+are currently running, or restart all tasks, even the ones that have already
+run. Groups and tasks can also target allocations.  When you define both groups
+and tasks, Nomad restarts only the tasks for the allocations of those groups.
+
+When migrating, Nomad stops the current allocations, triggering the Nomad
+scheduler to create new allocations that may be placed in different clients. The
+command waits until the new allocations have client status `ready` before
+proceeding with the remaining batches. The command does not consider service
+health checks.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, Nomad stops and migrates allocations instead of
+  restarting in-place. Since the group is not modified, the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such as
+  [`max_parallel`][], are not considered. This option cannot be used with
+  `-task`. You may only migrate jobs of type `batch`, `service`, and `system`.
+  Note that despite the name of this flag, this command migrates but does not
+  reschedule allocations, so it ignores the `reschedule` block.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.10.x/content/commands/job/revert.mdx b/content/nomad/v1.10.x/content/commands/job/revert.mdx
new file mode 100644
index 0000000000..94235dbe59
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/revert.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'nomad job revert command reference'
+description: |
+  The `nomad job revert` command reverts the current job to a prior version.
+---
+
+# `nomad job revert` command reference
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+## Usage
+
+```shell-session
+nomad job revert [options] <job> <version|tag>
+```
+
+The `job revert` command requires two inputs: the job ID, and the version number
+or tag of the job to revert to.  When you specify a version number, Nomad
+reverts the job to the exact version number. Alternately, when you specify a
+custom tag name as a string, Nomad reverts to the version tagged with that
+name.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`job history`]: /nomad/commands/job/history
+[eval status]: /nomad/commands/eval/status
+[run]: /nomad/commands/job/run
diff --git a/content/nomad/v1.10.x/content/commands/job/run.mdx b/content/nomad/v1.10.x/content/commands/job/run.mdx
new file mode 100644
index 0000000000..099878fef9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/run.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: 'nomad job run command reference'
+description: |
+  The `nomad job run` command submits a job to Nomad for scheduling, which then runs the job.
+---
+
+# `nomad job run` command reference
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and deployment status for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts are preserved when
+  updating a job.
+
+- `-preserve-resources`: If set, the existing task resources are preserved when
+  updating a job, so that autoscaling changes are not overwritten.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. Consul must be configured to authenticate
+  using Nomad Workload Identities.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+- `-ui`: Open the job page in the browser.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`batch`]: /nomad/docs/concepts/scheduling/schedulers#batch
+[eval status]: /nomad/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/concepts/scheduling/schedulers#system
diff --git a/content/nomad/v1.10.x/content/commands/job/scale.mdx b/content/nomad/v1.10.x/content/commands/job/scale.mdx
new file mode 100644
index 0000000000..c346cc29af
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/scale.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'nomad job scale command reference'
+description: |
+  The `nomad job scale` command changes the number of running allocations within
+  a Nomad task group.
+---
+
+# `nomad job scale` command reference
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-check-index`: If set, the job is only scaled if the passed job modify index
+  matches the server side version. Ignored if value of zero is passed. If a
+  non-zero value is passed, it ensures that the job is being updated from a
+  known state.
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.10.x/content/commands/job/scaling-events.mdx b/content/nomad/v1.10.x/content/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..b41324df64
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'nomad job scaling-events command reference'
+description: |
+  The `nomad job scaling-events` command displays scaling events for the specified job.
+---
+
+# `nomad job scaling-events` command reference
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/start.mdx b/content/nomad/v1.10.x/content/commands/job/start.mdx
new file mode 100644
index 0000000000..b3d9e307fa
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/start.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'nomad job start command reference'
+description: |
+  The nomad job start command starts the latest version of an existing job
+  with a status of Stopped.
+---
+
+# nomad job start command reference
+
+Use the `nomad job start` command to start the latest version of an existing job
+with a status of Stopped. Refer to [Job statuses] for status explanations.
+
+## Usage
+
+```shell-session
+nomad job start [options] <job_id>
+```
+
+The `nomad job start` command requires the job ID. Nomad creates new version of
+the job based on its most recent version. This command fails if the job is not
+registered or not currently stopped.
+
+When Nomad uses ACLs, the `nomad job start` command requires a token with one of
+the following capabilities based on the specific scenario:
+
+- The `submit-job`capability for the job's namespace
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. Nomad outputs a new
+  evaluation ID, which you can use to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Start a previously stopped job.
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+example  service  50        dead (stopped)  2025-02-11T15:33:27-05:00
+
+$ nomad job start example
+==> 2025-02-11T15:34:48-05:00: Monitoring evaluation "8b715538"
+    2025-02-11T15:34:48-05:00: Evaluation triggered by job "example"
+    2025-02-11T15:34:49-05:00: Evaluation within deployment: "866ca498"
+    2025-02-11T15:34:49-05:00: Allocation "4d050576" created: node "8e17fa4d", group "echo"
+    2025-02-11T15:34:49-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2025-02-11T15:34:49-05:00: Evaluation "8b715538" finished with status "complete"
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[run]: /nomad/commands/job/run
+[Job statuses]: /nomad/docs/concepts/job#job-statuses
diff --git a/content/nomad/v1.10.x/content/commands/job/status.mdx b/content/nomad/v1.10.x/content/commands/job/status.mdx
new file mode 100644
index 0000000000..60579c2b07
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/status.mdx
@@ -0,0 +1,267 @@
+---
+layout: docs
+page_title: 'nomad job status command reference'
+description: |
+  The `nomad job status` command displays information and status for the specified job.
+---
+
+# `nomad job status` command reference
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. Alloc status also shows allocation
+modification time in addition to create time. When the `-verbose` flag is not set,
+allocation creation and modify times are shown in a shortened relative time format
+like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+@include 'job-status-map.mdx'
+
+## Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-json`: Output the job status in JSON format.
+
+- `-t`: Format and display the job status using a Go template.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+- `-ui`: Open the job status page in the browser.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/stop.mdx b/content/nomad/v1.10.x/content/commands/job/stop.mdx
new file mode 100644
index 0000000000..a3bd91234d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/stop.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad job stop command reference'
+description: |
+  The `nomad job stop` command stops a running job and signals the scheduler
+  to cancel all of the job's running allocations.
+---
+
+# `nomad job stop` command reference
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.10.x/content/commands/job/tag/apply.mdx b/content/nomad/v1.10.x/content/commands/job/tag/apply.mdx
new file mode 100644
index 0000000000..e475669a41
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/tag/apply.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad job tag apply command reference'
+description: |
+  The `nomad job tag apply` command saves a job version tag.
+---
+
+# `nomad job tag apply` command reference
+
+Use `job tag apply` to create or modify a version tag.
+
+@include 'version/tag-reason.mdx'
+
+## Usage
+
+```plaintext
+nomad job tag apply [options] <job_id>
+```
+
+## Options
+
+- `name`: Specifies the name of the tag. Must be unique per job.
+- `description`: If set, specifies a description for the tag.
+- `version`: If set, specifies the version of the job to tag. If not provided,
+  Nomad tags the latest version of the job.
+
+## Examples
+
+This example tags the latest version of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -name "golden-version" \
+		-description "The version we can roll back to." \
+    hello-world
+```
+
+This example tags version zero of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -version 0 \
+      -name "golden-version" \
+      hello-world
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/tag/index.mdx b/content/nomad/v1.10.x/content/commands/job/tag/index.mdx
new file mode 100644
index 0000000000..c7e3a7eca0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/tag/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'nomad job tag command reference'
+description: |
+  The `nomad job tag` command manages versions. The `nomad job tag apply` command saves a job version tag, and the `nomad job tag unset` command removes a job version tag.
+---
+
+# `nomad job tag` command reference
+
+Use the `job tag` command to manage tags for job versions.
+
+@include 'version/tag-reason.mdx'
+
+## Usage
+
+```plaintext
+nomad job tag <subcommand> [options] [args]
+```
+
+`job tag` has the following subcommands:
+
+- [`job tag apply`](/nomad/commands/job/tag/apply): Save a job version tag.
+- [`job tag unset`](/nomad/commands/job/tag/apply): Remove a tag from a job version.
diff --git a/content/nomad/v1.10.x/content/commands/job/tag/unset.mdx b/content/nomad/v1.10.x/content/commands/job/tag/unset.mdx
new file mode 100644
index 0000000000..1d3269b0c9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/tag/unset.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad job tag unset command reference'
+description: |
+  The `nomad job tag unset` command removes a job version tag.
+---
+
+# `nomad job tag unset` command reference
+
+Use `nomad job tag unset` to delete a tag from a version. This command requires
+a job name and a tag name.
+
+## Usage
+
+```plaintext
+nomad job tag unset [options] <job_id>
+```
+
+## Options
+
+- `name`: Specifies the name of the tag to remove from the job version.
+
+## Examples
+
+This example removes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ nomad job tag unset -name "golden-version" hello-world
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/job/validate.mdx b/content/nomad/v1.10.x/content/commands/job/validate.mdx
new file mode 100644
index 0000000000..e9c23ef3f8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/job/validate.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad job validate command reference'
+description: >
+  The `nomad job validate` command checks a job specification for syntax
+  errors and validation problems.
+---
+
+# `nomad job validate` command reference
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.10.x/content/commands/license/get.mdx b/content/nomad/v1.10.x/content/commands/license/get.mdx
new file mode 100644
index 0000000000..94c4130327
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/license/get.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: 'nomad license get command reference'
+description: |
+  The `nomad license get` command fetches the Nomad Enterprise license from the Nomad server.
+---
+
+# `nomad license get` command reference
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+<EnterpriseAlert />
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/license/index.mdx b/content/nomad/v1.10.x/content/commands/license/index.mdx
new file mode 100644
index 0000000000..3c3138e3f7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'nomad license command reference'
+description: |
+  The `nomad license` command gets or inspects a Nomad Enterprise license.
+---
+
+# `nomad license` command reference
+
+The `license` commands can be used to retrieve license information from a
+server, or inspect and validate a license.
+
+<EnterpriseAlert/>
+
+## Usage
+
+```plaintext
+nomad license <subcommand> [options]
+```
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.10.x/content/commands/license/inspect.mdx b/content/nomad/v1.10.x/content/commands/license/inspect.mdx
new file mode 100644
index 0000000000..b6bc5a4a88
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/license/inspect.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad license inspect command reference'
+description: |
+  The `nomad license inspect` command inspects a Nomad Enterprise license to see if it is valid with the installed Nomad binary.
+---
+
+# `nomad license inspect` command reference
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+<EnterpriseAlert />
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.10.x/content/commands/login.mdx b/content/nomad/v1.10.x/content/commands/login.mdx
new file mode 100644
index 0000000000..d8721a5ae5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/login.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad login command reference'
+description: |
+  The `nomad login` command uses OpenID Connect (OIDC) to authenticate a user with a single sign-on (SSO) provider. Nomad creates an access control list (ACL) token after successful authentication.
+---
+
+# `nomad login` command reference
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+
+$ export NOMAD_TOKEN=a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+$ nomad ...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/monitor/export.mdx b/content/nomad/v1.10.x/content/commands/monitor/export.mdx
new file mode 100644
index 0000000000..42feb818e8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/monitor/export.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'nomad monitor export command reference'
+description: |
+  The `nomad monitor export` command returns logs written to disk or journald by a nomad agent.
+---
+
+# `nomad monitor export` command reference
+
+The `nomad monitor export` command returns logs written to disk or journald by a nomad agent.
+
+## Usage
+
+```plaintext
+nomad monitor export [options]
+```
+
+Use the `nomad monitor export` command to export an agent's historic data
+from journald or its Nomad log file. If exporting journald logs, you must
+pass `-service-name` with the name of the systemd unit to query.
+The `-logs-since` and `-follow` options are only valid for journald queries.
+You may pass a duration string to the `-logs-since` option to override the
+default 72h duration. Nomad will accept the following time units in the
+`-logs-since` duration string: "ns", "us" (or "µs"), "ms", "s", "m", "h".
+The `-follow=true` option causes the agent to continue to stream logs until
+interrupted or until the remote agent quits. Nomad only supports journald
+queries on Linux.
+
+If you do not use Linux or you do not run Nomad as a systemd unit, pass the
+`-on-disk=true` option to export the entirety of a given agent's nomad log file.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given, the Nomad server from the `-address` flag is used.
+
+- `-server-id`: Specifies the Nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-service-name`: Specifies the the name of the systemd unit for export.
+  Do not use with `-on-disk`. Must include 'nomad' and conform to systemd
+  naming conventions. You may provide the full systemd file name
+  or omit the suffix. If your service name includes a '.', you must include
+  a valid suffix (e.g. nomad.client.service).
+  
+- `-logs-since`: Duration used to determine how far back to return logs from
+  journald. Ignored if used with `-on-disk` and defaults to `72h` if  not set.
+
+- `-follow`: Boolean that, if true, continues streaming journald logs until
+  interrupted. Do not use with `-on-disk`
+  
+- `-on-disk`: Boolean that, if true, returns the contents of the Nomad log file
+  defined in the agent config.
+
+## Examples
+
+This example returns journald log entries with a specific node ID and service name.
+
+```shell-session
+$ nomad monitor export -node-id=$(nomad node status --quiet) -service-name="nomad"
+Jun 04 20:09:29 nomad-client01 systemd[1]: Starting Nomad...
+Subject: A start job for unit nomad_client.service has begun execution
+```
+
+This example returns the contents of the nomad log file for a specific server.
+
+```shell-session
+$ nomad monitor export -server-id=a57b2adb-1a30-2dda-8df0-25abb0881952 -on-disk=true
+2025-06-20T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2025-06-20T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/monitor/index.mdx b/content/nomad/v1.10.x/content/commands/monitor/index.mdx
new file mode 100644
index 0000000000..4f1f6d1884
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/monitor/index.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'nomad monitor command reference'
+description: |
+  The `nomad monitor` command streams log messages for a given agent. Configure log level, log output, node ID, and server ID.
+---
+
+# `nomad monitor` command reference
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/namespace/apply.mdx b/content/nomad/v1.10.x/content/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..905b771993
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/apply.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad namespace apply command reference'
+description: |
+  The `nomad namespace apply` command creates or updates a Nomad namespace.
+---
+
+# `nomad namespace apply` command reference
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/docs/govern/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers   = ["docker", "exec"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/namespace/delete.mdx b/content/nomad/v1.10.x/content/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..26b13a8b89
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad namespace delete command reference'
+description: |
+  The `nomad namespace delete` command deletes a namespace.
+---
+
+# `nomad namespace delete` command reference
+
+The `namespace delete` command is used delete a namespace.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs or allocations,
+existing CSI volumes or variables attached to it, or quotas associated with it.
+In federated clusters, you cannot delete a namespace that has any of the above
+in any of the federated regions.
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/namespace/index.mdx b/content/nomad/v1.10.x/content/commands/namespace/index.mdx
new file mode 100644
index 0000000000..323d972b17
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad namespace command reference'
+description: |
+  The nomad namespace reference command interact with namespaces. Create, inspect, and delete a namespace. Display status information and list namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+Visit [Create and use namespaces](/nomad/docs/govern/namespaces) for more information.
+
+## Usage
+
+```plaintext
+nomad namespace <subcommand> [options]
+```
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/commands/namespace/list 'List available namespaces'
+[status]: /nomad/commands/namespace/status "Display a namespace's status"
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.10.x/content/commands/namespace/inspect.mdx b/content/nomad/v1.10.x/content/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f3217f9952
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/inspect.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad namespace inspect command reference'
+description: >
+  The `nomad namespace inspect` command displays raw information about a
+  particular namespace.
+---
+
+# `nomad namespace inspect` command reference
+
+The `namespace inspect` command is used to view raw information about a
+particular namespace.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/namespace/list.mdx b/content/nomad/v1.10.x/content/commands/namespace/list.mdx
new file mode 100644
index 0000000000..4676610f90
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/list.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad namespace list command reference'
+description: |
+  The `nomad namespace list` command displays a list of namespaces.
+---
+
+# `nomad namespace list` command reference
+
+The `namespace list` command is used list available namespaces.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/namespace/status.mdx b/content/nomad/v1.10.x/content/commands/namespace/status.mdx
new file mode 100644
index 0000000000..1dea1ba3c0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/namespace/status.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad namespace status command reference'
+description: >
+  The `nomad namespace status` command displays status information for the specified namespace.
+---
+
+# `nomad namespace status` command reference
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name                 = api-prod
+Description          = Prod API servers
+Quota                = prod
+EnabledDrivers       = docker,exec
+DisabledDrivers      = raw_exec
+EnabledNetworkModes  = bridge,cni/custom
+DisabledNetworkModes = host
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/apply.mdx b/content/nomad/v1.10.x/content/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..09e73f90ac
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad node pool apply command reference'
+description: |
+  The `nomad node pool apply` command creates or updates a node pool.
+---
+
+# `nomad node pool apply` command reference
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## Options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/delete.mdx b/content/nomad/v1.10.x/content/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..51772e4b28
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool delete command reference'
+description: |
+  The `nomad node pool delete` command deletes the specified node pool.
+---
+
+# `nomad node pool delete` command reference
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/index.mdx b/content/nomad/v1.10.x/content/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..970d7c64f1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad node pool command reference'
+description: |
+  The `nomad node pool` command interact with node pools. Generate an example node pool specification. Create, update, and delete a node pool. Display a list of node pools and information about a specific node pool. Display jobs and nodes in a node pool.
+---
+
+# `nomad node pool` command reference
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+```plaintext
+nomad node pool <subcommand> [options]
+```
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool init`][init] - Generate an example node pool specification.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/commands/node-pool/apply
+[delete]: /nomad/commands/node-pool/delete
+[info]: /nomad/commands/node-pool/info
+[init]: /nomad/commands/node-pool/init
+[jobs]: /nomad/commands/node-pool/jobs
+[list]: /nomad/commands/node-pool/list
+[nodes]: /nomad/commands/node-pool/nodes
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/info.mdx b/content/nomad/v1.10.x/content/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..9e43022e7e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad node pool info command reference'
+description: |
+  The `nomad node pool info` command displays information about a node pool.
+---
+
+# `nomad node pool info` command reference
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## Options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name        = prod
+Description = Node pool for production workloads.
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/init.mdx b/content/nomad/v1.10.x/content/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..674bd3e742
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool init command reference'
+description: |
+  The `nomad node pool init` command generates an example node pool specification.
+---
+
+# `nomad node pool init` command reference
+
+The `nomad node pool init` command creates an example node pool specification
+file that you can use as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/jobs.mdx b/content/nomad/v1.10.x/content/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..603d070abe
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'nomad node pool jobs command reference'
+description: |
+  The `nomad node pool jobs` command displays jobs in the specified node pool.
+---
+
+# `nomad node pool jobs` command reference
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/list.mdx b/content/nomad/v1.10.x/content/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..0400490886
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'nomad node pool list command reference'
+description: |
+  The `nomad node pool list` command displays all node pools or those matching a filter expression.
+---
+
+# `nomad node pool list` command reference
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options]
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.10.x/content/commands/node-pool/nodes.mdx b/content/nomad/v1.10.x/content/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..beddbbcc05
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad node pool nodes command reference'
+description: |
+  The `nomad node pool nodes` command displays nodes in the specified node pool.
+---
+
+# `nomad node pool nodes` command reference
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.10.x/content/commands/node/config.mdx b/content/nomad/v1.10.x/content/commands/node/config.mdx
new file mode 100644
index 0000000000..9dfb2a1b46
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad node config command reference'
+description: |
+  The `nomad node config` command displays configuration details for the specified client. You can also update the client's server list with this command.
+---
+
+# `nomad node config` command reference
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.10.x/content/commands/node/drain.mdx b/content/nomad/v1.10.x/content/commands/node/drain.mdx
new file mode 100644
index 0000000000..41cd165659
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'nomad node drain command reference'
+description: |
+  The `nomad node drain` command turns on or turns off a node's drain mode. Drain mode prevents any new tasks from being allocated to the node and beings migrating all existing allocations to other nodes.
+---
+
+# `nomad node drain` command reference
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[eligibility]: /nomad/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/commands/node/status
+[workload migration guide]: /nomad/docs/manage/migrate-workloads
+[internals-csi]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.10.x/content/commands/node/eligibility.mdx b/content/nomad/v1.10.x/content/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aa00a4b356
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/eligibility.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad node eligibility command reference'
+description: >
+  The `nomad node eligibility` command turns on or turns off a node's eligibility to receive placements and run new allocations.
+---
+
+# `nomad node eligibility` command reference
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[drain]: /nomad/commands/node/drain
diff --git a/content/nomad/v1.10.x/content/commands/node/index.mdx b/content/nomad/v1.10.x/content/commands/node/index.mdx
new file mode 100644
index 0000000000..063f3cbc3f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node command reference'
+description: |
+  The nomad node reference command interacts with nodes. View or modify client configuration. Toggle scheduling eligibility and node drain mode. Display metadata and status information.
+---
+
+# `nomad node` command reference
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+```plaintext
+nomad node <subcommand> [options]
+```
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.10.x/content/commands/node/meta/apply.mdx b/content/nomad/v1.10.x/content/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..774f85356c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad node meta apply command reference'
+description: |
+  The `nomad node meta apply` command updates node metadata on client agents.
+---
+
+# `nomad node meta apply` command reference
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.10.x/content/commands/node/meta/index.mdx b/content/nomad/v1.10.x/content/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..3a05646727
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/meta/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad node meta command reference'
+description: |
+  The nomad node meta commands read and update node metadata.
+---
+
+# nomad node meta reference
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+```plaintext
+nomad node meta <subcommand> [options]
+```
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[apply]: /nomad/commands/node/meta/apply
+[read]: /nomad/commands/node/meta/read
diff --git a/content/nomad/v1.10.x/content/commands/node/meta/read.mdx b/content/nomad/v1.10.x/content/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..1f7edfb5ad
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad node meta read command reference'
+description: |
+  The nomad node meta read command displays metadata on the specified node.
+---
+
+# nomad node meta read reference
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.10.x/content/commands/node/status.mdx b/content/nomad/v1.10.x/content/commands/node/status.mdx
new file mode 100644
index 0000000000..1160fe024a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/node/status.mdx
@@ -0,0 +1,415 @@
+---
+layout: docs
+page_title: 'nomad node status command reference'
+description: |
+  The `nomad node status` command displays status information about registered client nodes.
+---
+
+# `nomad node status` command reference
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+- `-ui` : Open the node status page in the browser
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view with verbose:
+
+```shell-session
+$ nomad node status -verbose
+ID        Node Pool  DC   Name   Class   Address   Version  Drain  Eligibility  Status
+4d2ba53b  default    dc1  node1  <none>  127.0.0.1  1.10.1  false  eligible     ready
+34dfba32  dev        dc1  node2  <none>  127.0.0.1  1.10.1  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Address   Version  Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  127.0.0.1  1.10.1  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  127.0.0.1  1.10.1  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk              Alloc Count
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB     1/50
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     5/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     5/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     0/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/api.mdx b/content/nomad/v1.10.x/content/commands/operator/api.mdx
new file mode 100644
index 0000000000..5ee5ef5d7a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/api.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'nomad operator api command reference'
+description: |
+  The `nomad operator api` command is a cURL-like utility command for accessing Nomad's HTTP API.
+---
+
+# `nomad operator api` command reference
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.10.x/content/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.10.x/content/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..4625255f40
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot get-config command reference'
+description: |
+  The `nomad operator autopilot get-config` command displays the current Autopilot configuration.
+---
+
+# `nomad operator autopilot get-config` command reference
+
+The Autopilot operator command is used to view the current Autopilot
+settings, which you configure in the [`autopilot` block of the Agent configuration][autopilot-config].
+
+Refer to the [Autopilot Guide][autopilot-guide] for more information about
+Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Example
+
+This example returns the configuration information.
+
+```shell-session
+$ nomad operator autopilot get-config
+
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+Refer to the [`autopilot` block of the Agent
+configuration][autopilot-config] for explanations of the
+returned configuration settings.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[autopilot-guide]: /nomad/docs/manage/autopilot
+[autopilot-config]: /nomad/docs/configuration/autopilot
diff --git a/content/nomad/v1.10.x/content/commands/operator/autopilot/health.mdx b/content/nomad/v1.10.x/content/commands/operator/autopilot/health.mdx
new file mode 100644
index 0000000000..ab837b870a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/autopilot/health.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot health command reference'
+description: |
+  The `nomad operator autopilot health` command displays the current Autopilot internal health.
+---
+
+# `nomad operator autopilot health` command reference
+
+The Autopilot operator command is used to view the current Autopilot state.
+Refer to the [Autopilot Guide][autopilot-guide] for more information about
+Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot health [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Options
+
+- `-json`: Output the Autopilot health in unformatted JSON.
+
+The output will return like below, read about the output of the command in the [API docs][api-docs].
+
+```shell-session
+$ nomad operator autopilot health
+Healthy: true
+FailureTolerance: 0
+Leader: e349749b-3303-3ddf-959c-b5885a0e1f6e
+Voters:
+        e349749b-3303-3ddf-959c-b5885a0e1f6e
+Servers:
+ID                                    Name      Address         SerfStatus  Version   Leader  Voter  Healthy  LastContact  LastTerm  LastIndex  StableSince
+e349749b-3303-3ddf-959c-b5885a0e1f6e  node1     127.0.0.1:4647  alive       1.7.5     true    true   true     0s           2         14         2024-02-20 16:40:55 +0000 UTC
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[autopilot-guide]: /nomad/docs/manage/autopilot
+[api-docs]: /nomad/api-docs/operator/autopilot#read-autopilot-configuration
diff --git a/content/nomad/v1.10.x/content/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.10.x/content/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..79ad24385c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot set-config command reference'
+description: |
+  The `nomad operator autopilot set-config` command modifies the current Autopilot configuration.
+---
+
+# `nomad operator autopilot set-config` command reference
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. Refer to the [Autopilot Guide][autopilot-guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` -  <EnterpriseAlert inline/> Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- <EnterpriseAlert inline/> Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - <EnterpriseAlert inline/> Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+## Example
+
+This example sets `cleanup-dead-servers` to `false`.
+
+```shell-session
+$ nomad operator autopilot set-config -cleanup-dead-servers=false
+Configuration updated!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot-guide]: /nomad/docs/manage/autopilot
diff --git a/content/nomad/v1.10.x/content/commands/operator/client-state.mdx b/content/nomad/v1.10.x/content/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..81d89354c3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'nomad operator client-state command reference'
+description: >
+  The `nomad operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# `nomad operator client-state` command reference
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.10.x/content/commands/operator/debug.mdx b/content/nomad/v1.10.x/content/commands/operator/debug.mdx
new file mode 100644
index 0000000000..5be4a8b7d5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/debug.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: 'nomad operator debug command reference'
+description: |
+  The `nomad operator debug` command builds an archive containing Nomad cluster configuration and state information, Nomad server and client node logs, and pprof profiles from the selected servers and client nodes.
+---
+
+# `nomad operator debug` command reference
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## Options
+
+- `-duration=5m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `5m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=TRACE`: The log level to monitor. Defaults to `TRACE`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-log-file-export`: Include agents' Nomad logfiles in the debug capture.
+  The historical log export monitor runs concurrently with the log monitor
+  and ignores the `-log-level` and `-log-include-location` flags used to
+  configure that monitor. Nomad will return an error if the agent does not
+  have file logging configured. Cannot be used with `-log-lookback`.
+
+- `-log-lookback`: Include historical journald logs in the debug capture. The
+  journald export monitor runs concurrently with the log monitor and ignores
+  the `-log-level` and `-log-include-location` flags passed to that monitor.
+  This flag is only available on Linux systems using systemd, see the
+  `-log-file-export` flag to retrieve historical logs from non-Linux systems,
+  or those without systemd. Cannot be used with `-log-file-export`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..bf07092f64
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring generate command reference'
+description: >
+  The `nomad operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# nomad operator gossip keyring generate reference
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..3632f47d7a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring install command reference'
+description: |
+  The `nomad operator gossip keyring install` command installs a new gossip encryption key.
+---
+
+# `nomad operator gossip keyring install` command reference
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..93e136cd32
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring list command reference'
+description: |
+  The `nomad operator gossip keyring list` command displays all gossip keys currently in use within the cluster.
+---
+
+# `nomad operator gossip keyring list` command reference
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..295fac279f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring remove command reference'
+description: |
+  The `nomad operator gossip keyring remove` command removes the specified, non-primary gossip encryption key from the cluster.
+---
+
+# `nomad operator gossip keyring remove` command reference
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..1e91f3dff9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring use command reference'
+description: |
+  The `nomad operator gossip keyring use` command changes the encryption key that Nomad uses for gossip.
+---
+
+# `nomad operator gossip keyring use` command reference
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/index.mdx b/content/nomad/v1.10.x/content/commands/operator/index.mdx
new file mode 100644
index 0000000000..ee7decb5d2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/index.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: 'nomad operator command reference'
+description: |
+  The `nomad operator` command provides cluster-level tools for Nomad operators.
+---
+
+# `nomad operator` command reference
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator <subcommand> <subcommand> [options]
+```
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/docs/manage/outage-recovery
+[remove]: /nomad/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.10.x/content/commands/operator/metrics.mdx b/content/nomad/v1.10.x/content/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..b5ddf90312
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'nomad operator metrics command reference'
+description: |-
+  The `nomad operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# `nomad operator metrics` command reference
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/info.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..10ee200c77
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad operator raft info command reference'
+description: |
+  The `nomad operator raft info` command displays summary information about the Raft logs persisted in the Nomad data directory.
+---
+
+# `nomad operator raft info` command reference
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/list-peers.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..3a3b9b3e87
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad operator raft list-peers command reference'
+description: |
+  The `nomad operator raft list-peers` command displays the current Raft peer configuration.
+---
+
+# `nomad operator raft list-peers` command reference
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/logs.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..a5cc23391b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad operator raft logs command reference'
+description: |
+  The `nomad operator raft logs` command displays the log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft logs` command reference
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..144148bc41
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad operator raft remove-peer command reference'
+description: |
+  The `nomad operator raft remove-peer` command removes a Nomad server from the Raft configuration.
+---
+
+# `nomad operator raft remove-peer` command reference
+
+Remove the Nomad server with peer ID from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`nomad server force-leave`]: /nomad/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/state.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..73f11acf03
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator raft state command reference'
+description: |
+  The `nomad operator raft state` command displays Raft server state obtained by replaying Raft log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft state` command reference
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.10.x/content/commands/operator/raft/transfer-leadership.mdx b/content/nomad/v1.10.x/content/commands/operator/raft/transfer-leadership.mdx
new file mode 100644
index 0000000000..57052fcd97
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/raft/transfer-leadership.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad operator raft transfer-leadership command reference'
+description: |
+  The `nomad operator raft transfer-leadership` command transfers leadership to a specific Nomad server.
+---
+
+# `nomad operator raft transfer-leadership` command reference
+
+Transfer leadership from the current leader to the given server member.
+
+While performing a [rolling upgrade][] of your Nomad cluster, it might be
+advisable to transfer leadership to a specific node in the cluster. For example,
+setting the leader to the first upgraded server in the cluster can prevent
+leadership churn as you upgrade the remaining server nodes.
+
+The target server's ID or address:port are required and can be obtained by
+running the [`nomad operator raft list-peers`][] command or by calling the
+[Read Raft Configuration][] API endpoint.
+
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator][] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft transfer-leadership [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+<Note>
+
+Provide either `-peer-address` or `-peer-id`, but not both.
+
+</Note>
+
+- `-peer-address`: Specifies the Raft **Address** of the target server as
+  provided in the output of the [`nomad operator raft list-peers`][] command or
+  the [Read Raft Configuration] API endpoint.
+
+- `-peer-id`: Specifies the Raft **ID** of the target server as provided in the
+  output of the [`nomad operator raft list-peers`][] command or the
+  [Read Raft Configuration] API endpoint.
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`nomad operator raft list-peers`]: /nomad/commands/operator/raft/list-peers 'Nomad operator raft list-peers command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[rolling upgrade]: /nomad/docs/upgrade#upgrade-process
+[Read Raft Configuration]: /nomad/api-docs/operator/raft#read-raft-configuration
diff --git a/content/nomad/v1.10.x/content/commands/operator/root/keyring-list.mdx b/content/nomad/v1.10.x/content/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..61af021dfd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring list command reference'
+description: |
+  The `nomad operator root keyring list` command displays encryption key metadata for installed keys. This command does not display sensitive key material.
+---
+
+# `nomad operator root keyring list` command reference
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.10.x/content/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..7cf07561ad
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring remove command reference'
+description: |
+  The `nomad operator root keyring remove` command removes an unused encryption key from the cluster.
+---
+
+# `nomad operator root keyring remove` command reference
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+The `key ID` must be the UUID. Use the `-verbose` option with the
+[`nomad operator root keyring list`
+command](/nomad/commands/operator/root/keyring-list) to fetch the key
+UUID.
+
+## Options
+
+- `-force`: Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.10.x/content/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..ccd39a1d37
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring rotate command reference'
+description: |
+  The `nomad operator root keyring rotate` command rotates the encryption key by generating a new encryption key for all future variables.
+---
+
+# `nomad operator root keyring rotate` command reference
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.10.x/content/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.10.x/content/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..1ed7a39345
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler get-config command reference'
+description: |
+  The `nomad operator scheduler get-config` command displays the current scheduler configuration.
+---
+
+# `nomad operator scheduler get-config` command reference
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.10.x/content/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..eb30e02dcd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler set-config command reference'
+description: |
+  The `nomad operator scheduler set-config` command modifies the scheduler configuration. Set binpack or spread allocation. Enable or disable preemption for batch, service, sysbatch, and system jobs.
+---
+
+# `nomad operator scheduler set-config` command reference
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/agent.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..6b63d275f6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot agent command reference'
+description: |
+  The `nomad operator snapshot agent` command takes snapshots of the state of the Nomad servers and saves them locally or pushes them to an optional remote storage service.
+---
+
+# `nomad operator snapshot agent` command reference
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+<EnterpriseAlert />
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## Options
+
+### Snapshot
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure
+
+Note: Non-Solaris platforms only
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google
+
+- `-google-bucket`: The bucket to use.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..0b11a2b91f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot inspect command reference'
+description: |
+  The `nomad operator snapshot inspect` command displays information about a snapshot file stored on local disk.
+---
+
+# `nomad operator snapshot inspect` command reference
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/redact.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/redact.mdx
new file mode 100644
index 0000000000..bf7a4c0c83
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/redact.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot redact command reference'
+description: |
+ The `nomad operator snapshot redact` command removes key material from an existing snapshot file created by the `operator snapshot save` command so you can transmit a snapshot without exposing key material.
+---
+
+# `nomad operator snapshot redact` command reference
+
+The `operator snapshot redact` command removes key material from an existing
+snapshot file created by the `operator snapshot save` command, when using the
+AEAD keyring provider.
+
+This is useful for situations where you need to transmit a snapshot without
+exposing key material.
+
+<Warning>
+
+When using a [KMS keyring provider][], no cleartext key material is stored in
+snapshots and this command is not necessary. Note that this command requires
+loading the entire snapshot into memory locally and overwrites the existing
+snapshot.
+
+Snapshots made before Nomad 1.9.0 will not include the keyrings.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad operator snapshot redact <file>
+```
+
+
+[KMS keyring provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/restore.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..e099705531
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot restore command reference'
+description: |
+  The `nomad operator snapshot restore` command restores the specified Nomad snapshot.
+---
+
+# `nomad operator snapshot restore` command reference
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
+
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/save.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..30b6d178e0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/save.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot save command reference'
+description: |
+  The `nomad operator snapshot save` command saves an atomic, point-in-time snapshot of state of the Nomad servers, including jobs, nodes, allocations,periodic jobs, ACLs for outage recovery, and the keyring.
+---
+
+# `nomad operator snapshot save` command reference
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command includes Nomad's keyring in the snapshot. If you are not using a
+[KMS provider][] to secure the keyring, you should use the `-redact` flag to
+remove key material before transmitting the snapshot to HashiCorp Support.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## Options
+
+- `-redact`: The redact option will locally edit the snapshot to remove any
+  cleartext key material from the root keyring. Only the AEAD keyring provider
+  has cleartext key material in Raft. Note that this operation requires loading
+  the snapshot into memory locally.
+
+- `-stale`: The stale option defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
+[KMS provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.10.x/content/commands/operator/snapshot/state.mdx b/content/nomad/v1.10.x/content/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..218e99960a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot state command reference'
+description: |
+  The `nomad operator snapshot state` command displays a JSON representation of a Raft snapshot.
+---
+
+# `nomad operator snapshot state` command reference
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.10.x/content/commands/operator/utilization.mdx b/content/nomad/v1.10.x/content/commands/operator/utilization.mdx
new file mode 100644
index 0000000000..30173507cb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/operator/utilization.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: nomad operator utilization command reference
+description: |-
+  The "operator utilization" generates utilization reporting bundles for Nomad Enterprise users.
+---
+
+# `nomad operator utilization` command reference
+
+The `operator utilization` command allows Nomad Enterprise users to generate
+utilization reporting bundles. If you have disabled [automated
+reporting](/nomad/docs/enterprise/license/utilization-reporting), use
+this command to manually generate the report and send it to HashiCorp. Nomad
+takes a new snapshot when there are no snapshots from the past twenty-four
+hours.
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+<EnterpriseAlert />
+
+## Options
+
+- `-message` `(string; "")` - Provide context about the conditions under which
+  the report was generated and submitted. This message is not included in the
+  utilization bundle but is included in the Nomad server logs.
+
+- `-output` `(string; "")` - Specifies the output path for the bundle. Defaults
+  to a time-based generated file name in the current working directory.
+
+- `-today-only` `(bool: false)` - Include snapshots from the previous 24 hours,
+  not historical snapshots.
+
+## Examples
+
+Create a utilization reporting bundle that includes all persisted historical
+snapshots and has the default bundle name
+(`nomad-utilization-<time_stamp>.json`).
+
+```shell-session
+$ nomad operator utilization
+Success! Utilization reporting bundle written to: nomad-utilization-2024-02-16T22-23-25Z.json
+```
+
+Create a utilization reporting bundle with a message about the bundle, and
+output the file at the specified path, `/utilization/reports/latest.json`.
+
+```shell-session
+$ nomad operator utilization \
+    -message="Change Control 654987" \
+    -output="/utilization/reports/latest.json"
+```
+
+**Example output**
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Success! Utilization reporting bundle written to: /utilization/reports/latest.json
+```
+
+</CodeBlockConfig>
+
+The message, `Change Control 654987`, is included in the _server log_, but not
+in the bundle.
+
+**Example entry in the server log**
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+[INFO]  reporting: reporting bundle generated: message="Change Control 654987"
+```
+
+</CodeBlockConfig>
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/plugin/index.mdx b/content/nomad/v1.10.x/content/commands/plugin/index.mdx
new file mode 100644
index 0000000000..dc8fe4507a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/plugin/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad plugin command reference'
+description: |
+  The `nomad plugin` command interacts with external plugins that a job can use, such as Container Storage Interface (CSI) plugins.
+---
+
+# `nomad plugin` command reference
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin <subcommand> [options]
+```
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.10.x/content/commands/plugin/status.mdx b/content/nomad/v1.10.x/content/commands/plugin/status.mdx
new file mode 100644
index 0000000000..2332d64382
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'nomad plugin status command reference'
+description: |
+  The `nomad plugin status` displays information and status for a specific plugin, plugins by type, or all plugins.
+---
+
+# `nomad plugin status` command reference
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.10.x/content/commands/quota/apply.mdx b/content/nomad/v1.10.x/content/commands/quota/apply.mdx
new file mode 100644
index 0000000000..2f576e34e2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/apply.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad quota apply command reference'
+description: |
+  The `nomad quota apply` command creates or updates a Nomad Enterprise quota specification.
+---
+
+# `nomad quota apply` command reference
+
+The `quota apply` command is used to create or update [quota specifications][].
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[quota specifications]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.10.x/content/commands/quota/delete.mdx b/content/nomad/v1.10.x/content/commands/quota/delete.mdx
new file mode 100644
index 0000000000..cd157b0123
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad quota delete command reference'
+description: |
+  The `nomad quota delete` command deletes an existing quota specification in Nomad Enterprise.
+---
+
+# `nomad quota delete` command reference
+
+The `quota delete` command is used to delete an existing quota specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/quota/index.mdx b/content/nomad/v1.10.x/content/commands/quota/index.mdx
new file mode 100644
index 0000000000..05c0679449
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad quota command reference'
+description: |
+  The `nomad quota` command interacts with Nomad Enterprise quota specifications. Generate an example specification. Create, update, delete, and inspect a quota specification. Display quota status and current usage. Retrieve a list of all quota specifications.
+---
+
+# `nomad quota` command reference
+
+The `quota` command is used to interact with quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota <subcommand> [options]
+```
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/commands/quota/apply
+[quotadelete]: /nomad/commands/quota/delete
+[quotainit]: /nomad/commands/quota/init
+[quotainspect]: /nomad/commands/quota/inspect
+[quotalist]: /nomad/commands/quota/list
+[quotastatus]: /nomad/commands/quota/status
diff --git a/content/nomad/v1.10.x/content/commands/quota/init.mdx b/content/nomad/v1.10.x/content/commands/quota/init.mdx
new file mode 100644
index 0000000000..d8fcb02c00
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'nomad quota init command reference'
+description: |
+  The `nomad quota init` command generates an example quota specification that you can customize for your Nomad Enterprise quota specification.
+---
+
+# `nomad quota init` command reference
+
+The `quota init` command is used to create an example [quota specification][]
+file that can be used as a starting point to customize further.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
+
+[quota specification]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.10.x/content/commands/quota/inspect.mdx b/content/nomad/v1.10.x/content/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..64fdafb22f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/inspect.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: 'nomad quota inspect command reference'
+description: >
+  The `nomad quota inspect` command displays raw information about a particular
+  quota specification in Nomad Enterprise.
+---
+
+# `nomad quota inspect` command reference
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 11,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 1000,
+                    "Cores": 1,
+                    "Devices": null,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "MemoryMB": 1000,
+                    "MemoryMaxMB": 0,
+                    "NUMA": null,
+                    "Networks": null
+                },
+                "VariablesLimit": 0
+            }
+        ],
+        "ModifyIndex": 11,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 11,
+            "ModifyIndex": 12,
+            "Name": "default",
+            "Used": {
+                "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=": {
+                    "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 0,
+                        "Cores": 0,
+                        "Devices": null,
+                        "DiskMB": 0,
+                        "IOPS": 0,
+                        "MemoryMB": 0,
+                        "MemoryMaxMB": 0,
+                        "NUMA": null,
+                        "Networks": null
+                    },
+                    "VariablesLimit": 0
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t '{{ .Description }}' default-quota
+Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/quota/list.mdx b/content/nomad/v1.10.x/content/commands/quota/list.mdx
new file mode 100644
index 0000000000..f7500264c4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'nomad quota list command reference'
+description: |
+  The `nomad quota list` command displays a list of available quota specifications in Nomad Enterprise.
+---
+
+# `nomad quota list` command reference
+
+The `quota list` command is used to list available quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/quota/status.mdx b/content/nomad/v1.10.x/content/commands/quota/status.mdx
new file mode 100644
index 0000000000..7daadeedf7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/quota/status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'nomad quota status command reference'
+description: >
+  The `nomad quota status` command displays status information for a particular quota specification in Nomad Enterprise.
+---
+
+# `nomad quota status` command reference
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 1000   0 / 1       0 / 1000      0 / inf           0 / inf
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota status -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota status -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/recommendation/apply.mdx b/content/nomad/v1.10.x/content/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..bccc4a5425
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad recommendation apply command reference'
+description: |
+  The `nomad recommendation apply` command applies one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation apply` command reference
+
+The `recommendation apply` command is used to apply recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/recommendation/dismiss.mdx b/content/nomad/v1.10.x/content/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..165728e4ea
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad recommendation dismiss command reference'
+description: |
+  The `nomad recommendation dismiss` command dismisses one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation dismiss` command reference
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/recommendation/index.mdx b/content/nomad/v1.10.x/content/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..dbae1f81ef
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/recommendation/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad recommendation command reference'
+description: |
+  The `nomad recommendation` command interacts with recommendations in Nomad Enterprise. Display a specific recommendation or a list of recommendations. Apply or dismiss recommendations.
+---
+
+# `nomad recommendation` command reference
+
+The `recommendation` command is used to interact with recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation <subcommand> [options]
+```
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/commands/recommendation/apply
+[recommendationdismiss]: /nomad/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/commands/recommendation/info
+[recommendationlist]: /nomad/commands/recommendation/list
diff --git a/content/nomad/v1.10.x/content/commands/recommendation/info.mdx b/content/nomad/v1.10.x/content/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..8ff4728b99
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad recommendation info command reference'
+description: |
+  The `nomad recommendation info` command displays information about the specified recommendation in Nomad Enterprise.
+---
+
+# `nomad recommendation info` command reference
+
+The `recommendation info` command is used to read the specified recommendation.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/recommendation/list.mdx b/content/nomad/v1.10.x/content/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..cd4e57ee24
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'nomad recommendation list command reference'
+description: |
+  The `nomad recommendation list` command displays a list of available recommendations in Nomad Enterprise. Filter options include job, group, and task.
+---
+
+# `nomad recommendation list` command reference
+
+The `recommendation list` command is used to list the available recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/scaling/index.mdx b/content/nomad/v1.10.x/content/commands/scaling/index.mdx
new file mode 100644
index 0000000000..48733e53d7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'nomad scaling command reference'
+description: |
+  The `nomad scaling` command interacts with scaling policies.
+---
+
+# `nomad scaling` command reference
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+```plaintext
+nomad scaling <subcommand> [options]
+```
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/commands/scaling/policy-list
diff --git a/content/nomad/v1.10.x/content/commands/scaling/policy-info.mdx b/content/nomad/v1.10.x/content/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..87c80daf74
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad scaling policy info command reference'
+description: |
+  The `nomad scaling policy info` command displays detailed information for the specified scaling policy.
+---
+
+# `nomad scaling policy info` command reference
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/scaling/policy-list.mdx b/content/nomad/v1.10.x/content/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..87cf42d46d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad scaling policy list command reference'
+description: |
+  The `nomad scaling policy list` command displays all Nomad scaling policies. Filter options include job and policy type.
+---
+
+# `nomad scaling policy list` command reference
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/sentinel/apply.mdx b/content/nomad/v1.10.x/content/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..c5a354d0cd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/sentinel/apply.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'nomad sentinel apply command reference'
+description: >
+  The `nomad sentinel apply` command creates or updates a Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel apply` command reference
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Additionally, you must specify the `-scope` option. Refer to the [`-scope` field
+description](/nomad/commands/sentinel/apply#scope) for more information.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : Required. Sets the scope of the policy and when it
+  should be enforced. Specify one of the following:
+
+  - The `submit-job` scope for registering jobs
+  - The `submit-host-volume` scope for creating or updating dynamic host
+    volumes.
+  - The `submit-csi-volume` scope for creating or updating CSI volumes.
+
+  Refer to the [Sentinel guide](/nomad/docs/reference/sentinel-policy) for scope details.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -scope "submit-job" -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/sentinel/delete.mdx b/content/nomad/v1.10.x/content/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..ee53e60bab
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad sentinel delete command reference'
+description: |
+  The `nomad sentinel delete` command deletes the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel delete` command reference
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/sentinel/index.mdx b/content/nomad/v1.10.x/content/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..16dd80aba1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/sentinel/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad sentinel command reference'
+description: |
+  The `nomad sentinel` command interacts with Sentinel policies in Nomad Enterprise. Create, update, and delete a policy. Inspect and list policies.
+---
+
+# `nomad sentinel` command reference
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel <subcommand> [options]
+```
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/commands/sentinel/delete
+[list]: /nomad/commands/sentinel/list
+[read]: /nomad/commands/sentinel/read
+[apply]: /nomad/commands/sentinel/apply
diff --git a/content/nomad/v1.10.x/content/commands/sentinel/list.mdx b/content/nomad/v1.10.x/content/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..aa0f6183f1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad sentinel list command reference'
+description: |
+  The `nomad sentinel list` command displays a list all Sentinel policies installed in Nomad Enterprise.
+---
+
+# `nomad sentinel list` command reference
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/sentinel/read.mdx b/content/nomad/v1.10.x/content/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..6e30b6e26c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad sentinel read command reference'
+description: |
+  The `nomad sentinel read` command displays detailed information about the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel read` command reference
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/server/force-leave.mdx b/content/nomad/v1.10.x/content/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..52a32031df
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/server/force-leave.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad server force-leave command reference'
+description: >
+  The `nomad server force-leave` command forces a server into the left state so that you can eject server nodes that have failed.
+---
+
+# `nomad server force-leave` command reference
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`.
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## Options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/server/index.mdx b/content/nomad/v1.10.x/content/commands/server/index.mdx
new file mode 100644
index 0000000000..89e81efeb8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/server/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad server command reference'
+description: |
+  The `nomad server` command interacts with Nomad servers. Display a list of servers, join server nodes together, and force a server into the left state.
+---
+
+# `nomad server` command reference
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+```plaintext
+nomad server <subcommand> [options]
+```
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/commands/server/join 'Join server nodes together'
+[members]: /nomad/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.10.x/content/commands/server/join.mdx b/content/nomad/v1.10.x/content/commands/server/join.mdx
new file mode 100644
index 0000000000..2a329ade41
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad server join command reference'
+description: >
+  The `nomad server join` command joins the local server to one or more Nomad
+  servers.
+---
+
+# `nomad server join` command reference
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: //nomad/docs/deploy/clusters/federate-regions
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/server/members.mdx b/content/nomad/v1.10.x/content/commands/server/members.mdx
new file mode 100644
index 0000000000..b84912cc76
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/server/members.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'nomad server members command reference'
+description: >
+  The `nomad server members` command displays a list of servers in the cluster. Review name, address, port, region, datacenter, Raft version, build version, status, tags, and whether the server is the leader.
+---
+
+# `nomad server members` command reference
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server members in its JSON format.
+
+- `-t`: Format and display the server members using a Go template.
+
+- `-ui`: Open the servers page in the browser.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/service/delete.mdx b/content/nomad/v1.10.x/content/commands/service/delete.mdx
new file mode 100644
index 0000000000..4ea532f530
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'nomad service delete command reference'
+description: |
+  The `nomad service delete` command deletes a Nomad service by name and ID.
+---
+
+# `nomad service delete` command reference
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/service/index.mdx b/content/nomad/v1.10.x/content/commands/service/index.mdx
new file mode 100644
index 0000000000..469d187bd8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/service/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'nomad service command reference'
+description: |
+  The `nomad service` command interacts with Nomad services. Display service  information and delete a registered service.
+---
+
+# `nomad service` command reference
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+```plaintext
+nomad service <subcommand> [options]
+```
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/commands/service/delete
+[serviceinfo]: /nomad/commands/service/info
+[servicelist]: /nomad/commands/service/list
diff --git a/content/nomad/v1.10.x/content/commands/service/info.mdx b/content/nomad/v1.10.x/content/commands/service/info.mdx
new file mode 100644
index 0000000000..9eab949495
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/service/info.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad service info command reference'
+description: |
+  The `nomad service info` command displays information about the specified registered service. Search by service name to review namespace, job, allocation, node, datacenter, address, and tags.
+---
+
+# `nomad service info` command reference
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/service/list.mdx b/content/nomad/v1.10.x/content/commands/service/list.mdx
new file mode 100644
index 0000000000..ebe1dbacb2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad service list command reference'
+description: |
+  The `nomad service list` command displays a list of registered Nomad services.
+---
+
+# `nomad service list` command reference
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/setup/consul.mdx b/content/nomad/v1.10.x/content/commands/setup/consul.mdx
new file mode 100644
index 0000000000..ac943c2868
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/setup/consul.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'nomad setup consul command reference'
+description: |
+  The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup consul` command reference
+
+The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Consul and respects
+`CONSUL_HTTP_TOKEN`, `CONSUL_HTTP_ADDR`, and other [Consul-related environment
+variables][consulenv].
+
+## Usage
+
+```plaintext
+nomad setup consul [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup consul
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Consul ACL using their
+respective workload identities.
+
+First we need to connect to Consul.
+
+[?] Is "127.0.0.1:8500" the correct address of your Consul cluster? [Y/n]
+
+Since you're running Consul Enterprise, we will additionally create
+a namespace "nomad-workloads" and bind the auth methods to that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Consul cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+Nomad needs a JWT auth method for Consul services and tasks. The method for
+services will be called "nomad-workloads".
+
+This is the "nomad-workloads" method configuration:
+
+{
+    "Name": "nomad-workloads",
+    "Type": "jwt",
+    "DisplayName": "nomad-workloads",
+    "Description": "Login method for Nomad workloads using workload identities",
+    "TokenLocality": "local",
+    "Config": {
+        "BoundAudiences": [
+            "consul.io"
+        ],
+        "ClaimMappings": {
+            "consul_namespace": "consul_namespace",
+            "nomad_job_id": "nomad_job_id",
+            "nomad_namespace": "nomad_namespace",
+            "nomad_service": "nomad_service",
+            "nomad_task": "nomad_task"
+        },
+        "JWKSURL": "http://localhost:4646/.well-known/jwks.json",
+        "JWTSupportedAlgs": [
+            "RS256"
+        ]
+    },
+    "CreateIndex": 0,
+    "ModifyIndex": 0,
+    "NamespaceRules": [
+        {
+            "BindNamespace": "${value.consul_namespace}"
+        }
+    ]
+}
+[?] Create "nomad-workloads" auth method in your Consul cluster? [Y/n]
+[✔] Created auth method "nomad-workloads".
+
+Consul uses binding rules to map claims between Nomad's JWTs to Consul service
+identities and ACL roles, so we need to create a two binding rules for the auth
+method we created above: one for services, and one for tasks.
+
+This is the binding rule for services:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad services authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" in value",
+    "BindType": "service",
+    "BindName": "${value.nomad_service}",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n]
+[✔] Created binding rule for auth method "nomad-workloads".
+
+This is the binding rule for tasks:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad tasks authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" not in value",
+    "BindType": "role",
+    "BindName": "nomad-${value.nomad_namespace}-tasks",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Consul
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Auth method: nomad-workloads
+  * Binding rules: 4d80108a-6d77-36e1-71b1-d20a9acf8b17
+  * Namespace: nomad-workloads
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted binding rule "4d80108a-6d77-36e1-71b1-d20a9acf8b17".
+[✔] Deleted auth method "nomad-workloads".
+[✔] Deleted namespace "nomad-workloads".
+
+Consul cluster has not been configured for authenticating Nomad tasks and
+services using workload identitiies.
+
+Run the command again to finish the configuration process.
+```
+
+[consulenv]: /consul/commands#environment-variables
diff --git a/content/nomad/v1.10.x/content/commands/setup/index.mdx b/content/nomad/v1.10.x/content/commands/setup/index.mdx
new file mode 100644
index 0000000000..0463070acf
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/setup/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad setup command reference'
+description: |
+  The `nomad setup` command sets up Consul and Vault integration.
+---
+
+# `nomad setup` command reference
+
+The `setup` command groups helper subcommands used for setting up external
+tools.
+
+<Warning>
+
+These commands are experimental features and may change their behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup <subcommand> [options]
+```
+
+Run `nomad setup <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`setup consul`][consul] - Setup a Consul cluster for Nomad integration.
+- [`setup vault`][vault] - Setup a Vault cluster for Nomad integration.
+
+[consul]: /nomad/commands/setup/consul
+[vault]: /nomad/commands/setup/vault
diff --git a/content/nomad/v1.10.x/content/commands/setup/vault.mdx b/content/nomad/v1.10.x/content/commands/setup/vault.mdx
new file mode 100644
index 0000000000..f1e56cd6da
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/setup/vault.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: 'nomad setup vault command reference'
+description: |
+  The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup vault` command reference
+
+The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Vault and respects
+`VAULT_TOKEN`, `VAULT_ADDR`, and other [Vault-related environment
+variables][vaultenv].
+
+The `-check` option can be used to verify if the Nomad cluster is ready to
+migrate to use Workload Identities with Vault. This option requires
+`operator:read` permission for Nomad.
+
+## Usage
+
+```plaintext
+nomad setup vault [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+- `-check`: Verify if the Nomad cluster is ready to migrate to Workload
+  Identities.
+
+### Options when using `-check`
+
+- `-json`: Output migration status information in its JSON format.
+
+- `-t`: Format and display migration status information using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup vault
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Vault ACL using their
+respective workload identities.
+
+First we need to connect to Vault.
+
+[?] Is "http://127.0.0.1:8200" the correct address of your Vault cluster? [Y/n]
+
+Since you're running Vault Enterprise, we will additionally create
+a namespace "nomad-workloads" and create all configuration within that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Vault cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+We will now enable the JWT credential backend and create a JWT auth method that
+Nomad workloads will use.
+
+This is the method configuration:
+
+{
+    "default_role": "nomad-workloads",
+    "jwks_url": "http://localhost:4646/.well-known/jwks.json",
+    "jwt_supported_algs": [
+        "EdDSA",
+        "RS256"
+    ]
+}
+[?] Create JWT auth method in your Vault cluster? [Y/n]
+[✔] Created JWT auth method "jwt-nomad".
+
+We need to create a role that Nomad workloads will assume while authenticating,
+and a policy associated with that role.
+
+
+These are the rules for the policy "nomad-workloads" that we will create. It uses a templated
+policy to allow Nomad tasks to access secrets in the path
+"secrets/data/<job namespace>/<job name>":
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+
+[?] Create the above policy in your Vault cluster? [Y/n]
+[✔] Created policy "nomad-workloads".
+
+We will now create an ACL role called "nomad-workloads" associated with the policy above.
+
+{
+    "bound_audiences": "vault.io",
+    "claim_mappings": {
+        "nomad_job_id": "nomad_job_id",
+        "nomad_namespace": "nomad_namespace",
+        "nomad_task": "nomad_task"
+    },
+    "role_type": "jwt",
+    "token_period": "30m",
+    "token_policies": [
+        "nomad-workloads"
+    ],
+    "token_type": "service",
+    "user_claim": "/nomad_job_id",
+    "user_claim_json_pointer": true
+}
+[?] Create role in your Vault cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Vault
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Policy: "nomad-workloads"
+  * JWT auth method: "jwt-nomad"
+  * Namespace: "nomad-workloads"
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted policy "nomad-workloads".
+[✔] Disabled JWT auth method "jwt-nomad".
+[✔] Deleted namespace "nomad-workloads".
+
+Vault cluster has not been configured for authenticating Nomad tasks and
+services using workload identities.
+
+Run the command again to finish the configuration process.
+```
+
+The `-check` option can use to verify if a cluster is ready to migrate to using
+workload identities with Vault.
+
+```
+$ nomad setup vault -check
+
+Jobs Without Workload Identity for Vault
+The following jobs access Vault but are not configured for workload identity.
+
+You should redeploy them before fully migrating to workload identities with
+Vault to prevent unexpected errors if their tokens need to be recreated.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID       Namespace  Type     Status
+example  default    service  running
+
+Outdated Nodes
+The following nodes are running a version of Nomad that does not support using
+workload identities with Vault.
+
+You should upgrade them to Nomad 1.7 before fully migrating to workload
+identities with Vault to prevent unexpected errors if they receive allocations
+for jobs that use Vault.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID        Name      Address        Version  Drain  Eligibility  Status
+049f7683  client-1  192.168.0.186  1.6.4    false  eligible     ready
+
+Vault Tokens
+The following Vault ACL tokens were created by Nomad but will not be
+automatically revoked after migrating to workload identities. They will expire
+once their TTL reaches zero.
+
+Accessor ID               Allocation ID  Node ID   Configured TTL
+czh9MPcRXzAhxBL9XKyb3Kh1  f00893d4       049f7683  60
+```
+
+@include 'general_options_no_namespace.mdx'
+
+[vaultenv]: /vault/docs/commands#environment-variables
diff --git a/content/nomad/v1.10.x/content/commands/status.mdx b/content/nomad/v1.10.x/content/commands/status.mdx
new file mode 100644
index 0000000000..7da9b5f121
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/status.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: 'nomad status command reference'
+description: |
+  The `nomad status` command display the status output for any Nomad resource.
+---
+
+# `nomad status` command reference
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/system/gc.mdx b/content/nomad/v1.10.x/content/commands/system/gc.mdx
new file mode 100644
index 0000000000..15ffcaa21e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad system gc command reference'
+description: |
+  The `nomad system gc` command runs the system garbage collection process on jobs, evaluations, allocations, and nodes.
+---
+
+# `nomad system gc` command reference
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/system/index.mdx b/content/nomad/v1.10.x/content/commands/system/index.mdx
new file mode 100644
index 0000000000..99d11156c6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/system/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad system command reference'
+description: |
+  The `nomad system` commands run garbage collection and reconcile job summaries.
+---
+
+# `nomad system` command reference
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+```plaintext
+nomad system <subcommand> [options]
+```
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.10.x/content/commands/system/reconcile-summaries.mdx b/content/nomad/v1.10.x/content/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..021ee3d286
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad system reconcile summaries command reference'
+description: |
+  The `nomad system reconcile summaries` command reconciles the summaries of all registered jobs.
+---
+
+# `nomad system reconcile summaries` command reference
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/tls/ca-create.mdx b/content/nomad/v1.10.x/content/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..b3ea8ff0df
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/tls/ca-create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad tls ca create command reference'
+description: |
+  The `nomad tls ca create` command creates a certificate authority that you then use to create a self-signed certificate for Nomad Transport Layer Security (TLS) configuration.
+---
+
+# `nomad tls ca create` command reference
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.10.x/content/commands/tls/ca-info.mdx b/content/nomad/v1.10.x/content/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..edb0c805fc
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/tls/ca-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad tls ca info command reference'
+description: |
+  The `nomad tls ca info` command displays serial number, issuer, name, expiration date, and permitted DNS domains for the provided certificate authority (CA) file.
+---
+
+# `nomad tls ca info` command reference
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.10.x/content/commands/tls/cert-create.mdx b/content/nomad/v1.10.x/content/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..8ed911330d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'nomad tls cert create command reference'
+description: |
+  The `nomad tls cert create` command creates a server, client, or command-line interface (CLI) certificate for Transport Layer Security (TLS) configuration in your Nomad cluster.
+---
+
+# `nomad tls cert create` command reference
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+```plaintext
+nomad tls cert create [options]
+```
+
+## Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/docs/secure/traffic/tls
diff --git a/content/nomad/v1.10.x/content/commands/tls/cert-info.mdx b/content/nomad/v1.10.x/content/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..12f55e71e6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/tls/cert-info.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad tls cert info command reference'
+description: |
+  The `nomad tls cert info` command displays serial number, issuer, name, expiration date, DNS names, and IP address from a specified certificate file.
+---
+
+# `nomad tls cert info` command reference
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.10.x/content/commands/tls/index.mdx b/content/nomad/v1.10.x/content/commands/tls/index.mdx
new file mode 100644
index 0000000000..f817f2f52f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/tls/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad tls command reference'
+description: |
+  The `nomad tls` command creates and displays information about a certificate authority and self-signed certificate for Nomad's Transport Security Layer (TLS).
+---
+
+# `nomad tls` command reference
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+```plaintext
+nomad tls <subcommand> <subcommand> [options]
+```
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/commands/tls/cert-info 'Display information from a certificate'
diff --git a/content/nomad/v1.10.x/content/commands/ui.mdx b/content/nomad/v1.10.x/content/commands/ui.mdx
new file mode 100644
index 0000000000..30dfa743d6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad ui command reference'
+description: |
+  The `nomad ui` command opens the Nomad Web UI. Provide a node, job, or allocation identifier to open that object's UI page in your browser. Authenticate with an access control list (ACL) token. Use the `show-url` flag to return the UI's URL.
+---
+
+# `nomad ui` command reference
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/var/get.mdx b/content/nomad/v1.10.x/content/commands/var/get.mdx
new file mode 100644
index 0000000000..0410d2d942
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/get.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: nomad var get reference
+description: |-
+  The `nomad var get` command retrieves the variable at the given path from
+  Nomad.
+---
+
+# `nomad var get` command reference
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+- `-ui`: Open the variable page in the browser.
+
+## Examples
+
+@include 'variables/get-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.10.x/content/commands/var/index.mdx b/content/nomad/v1.10.x/content/commands/var/index.mdx
new file mode 100644
index 0000000000..3d4df5282b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/index.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: nomad var reference
+description: |-
+  The `nomad var` commands interact with Nomad variables. Create a variable specification file. Insert, update, delete, or acquire a lock over a variable. Fetch and list variables.
+---
+
+# `nomad var` command reference
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+```plaintext
+nomad var <subcommand> [options] [args]
+```
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+- [`var lock`][lock] - Acquire a lock over a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/commands/var/init
+[get]: /nomad/commands/var/get
+[list]: /nomad/commands/var/list
+[put]: /nomad/commands/var/put
+[purge]: /nomad/commands/var/purge
+[lock]: /nomad/commands/var/lock
diff --git a/content/nomad/v1.10.x/content/commands/var/init.mdx b/content/nomad/v1.10.x/content/commands/var/init.mdx
new file mode 100644
index 0000000000..764cb0b293
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/init.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad var init command reference'
+description: |
+  The `nomad var init` command generates an example variable specification that you can customize for your Nomad variables.
+---
+
+# `nomad var init` command reference
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+@include 'variables/init-example.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/var/list.mdx b/content/nomad/v1.10.x/content/commands/var/list.mdx
new file mode 100644
index 0000000000..a8a4b46daf
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/list.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: nomad var list reference
+description: |-
+  The `nomad var list` command displays data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# `nomad var list` command reference
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+- `-ui`: Open the variable list page in the browser.
+
+## Examples
+
+@include 'variables/list-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.10.x/content/commands/var/lock.mdx b/content/nomad/v1.10.x/content/commands/var/lock.mdx
new file mode 100644
index 0000000000..e576da8181
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/lock.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: nomad var lock reference
+description: |-
+  The `nomad var lock` command locks a variable, only allowing the lock owner to modify it.
+---
+
+# `nomad var lock` command reference
+
+The `var lock` command holds a lock on a [variable][].
+
+## Usage
+
+```plaintext
+nomad var lock [options] <lock spec file reference> child...
+nomad var lock [options] <path to store variable> [<variable spec file reference>] child
+```
+
+The lock command provides a mechanism for simple distributed locking. A lock
+is created in the given variable, and only when held, is a child process invoked.
+
+The lock command can be called on an existing variable or an entire new variable
+specification can be provided to the command from a file by using an
+@-prefixed path to a variable specification file. Items to be stored in the
+variable can be supplied using the specification file as well.
+
+Nomad lock launches its children in a shell. By default, Nomad will use the
+shell defined in the environment variable SHELL. If SHELL is not defined,
+it will default to /bin/sh. It should be noted that not all shells terminate
+child processes when they receive SIGTERM. Under Ubuntu, /bin/sh is linked
+to dash, which does not terminate its children. In order to ensure that
+child processes are killed when the lock is lost, be sure to set the SHELL
+environment variable appropriately, or run without a shell by setting -shell=false.
+
+If [ACLs][] are enabled, this command requires the 'variables:write' capability
+for the destination namespace and path.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## Options
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `ttl`: Optional, TTL for the lock, time the variable will be locked. Defaults to 15s.
+
+- `delay`: Optional, time the variable is blocked from locking when a lease is not renewed.
+	Defaults to 15s.
+
+- `max-retry`:Optional, max-retry up to this number of times if Nomad returns a 500 error
+	while monitoring the lock. This allows riding out brief periods of
+	unavailability without causing leader elections, but increases the amount of
+	time required to detect a lost lock in some cases. Defaults to 5. Set to 0 to
+	disable.
+
+- `shell`: Optional, use a shell to run the command (can set a custom shell via
+	the SHELL environment variable). The default value is true.
+
+## Examples
+
+@include 'variables/lock-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]:  /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
+[ACL]: /nomad/docs/other-specifications/acl-policy#variables
+
diff --git a/content/nomad/v1.10.x/content/commands/var/purge.mdx b/content/nomad/v1.10.x/content/commands/var/purge.mdx
new file mode 100644
index 0000000000..45213ea338
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/purge.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: nomad var purge reference
+description: |-
+  The `nomad var purge` command permanently removes the specified variable
+  from Nomad.
+---
+
+# `nomad var purge` command reference
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+@include 'variables/purge-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.10.x/content/commands/var/put.mdx b/content/nomad/v1.10.x/content/commands/var/put.mdx
new file mode 100644
index 0000000000..7b829fe20e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/var/put.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: nomad var put reference
+description: |-
+  The `nomad var put` command creates or updates a Nomad variable.
+---
+
+# `nomad var put` command reference
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `-ui`: Open the variable page in the browser.
+
+## Examples
+
+@include 'variables/put-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.10.x/content/commands/version.mdx b/content/nomad/v1.10.x/content/commands/version.mdx
new file mode 100644
index 0000000000..eec3c9c626
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad version command reference'
+description: |
+  The `nomad version` command displays the version, build date, and revision information for a Nomad installation.
+---
+
+# `nomad version` command reference
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.10.x/content/commands/volume/claim-delete.mdx b/content/nomad/v1.10.x/content/commands/volume/claim-delete.mdx
new file mode 100644
index 0000000000..706b69f498
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/claim-delete.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad volume claim delete command reference'
+description: |
+  The `nomad volume claim delete` command deletes a task group host volume claim.
+---
+
+# `nomad volume claim delete` command reference
+
+The `volume claim delete` command deletes a task group host volume claim.
+[Stateful deployments][stateful deployments] use these claims.
+
+## Usage
+
+```plaintext
+nomad volume claim delete [options] <claim_id>
+```
+
+This command accepts claim ID or prefix as the sole argument. The command
+deletes the claim if there is an exact match based on the provided claim
+ID or prefix, Otherwise, the command displays a list of matching claims and
+information.
+
+When ACLs are enabled, this command requires a token with the
+`host-volume-write` capability in the volume's namespace.
+
+## Options
+
+- `-y`: Automatically answers "yes" to all the questions, making the deletion
+  non-interactive. Defaults to "false."
+
+## Example
+
+List all volumes.
+
+```shell-session
+$ nomad volume claim delete 3f25be9a
+
+  If you delete a volume claim, the allocation that uses this claim to "stick"
+  to a particular volume ID will no longer use it upon its next reschedule or
+  migration. The deployment of the task group the allocation runs will still
+  claim another feasible volume ID during reschedule or replacement.
+
+[?] Are you sure you want to delete task group host volume claim 3f25be9a? [Y/n]
+Task group host volume claim 3f25be9a-a2ee-3d7f-c248-45099fd54939 successfully deleted
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
diff --git a/content/nomad/v1.10.x/content/commands/volume/claim-list.mdx b/content/nomad/v1.10.x/content/commands/volume/claim-list.mdx
new file mode 100644
index 0000000000..d233652774
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/claim-list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: volume claim list'
+description: |
+  List task group host volume claims.
+---
+
+# Command: volume claim list
+
+The `volume claim list` command displays all task group host volume claims.
+[Stateful deployments][stateful deployments] use these claims.
+
+## Usage
+
+```plaintext
+nomad volume claim list [options] [claim_id]
+```
+
+This command accepts an optional claim ID or prefix as the sole argument. If
+there is an exact match based on the provided volume ID or prefix, then
+the command displays information about the specific claim. Otherwise, the command
+displays a list of matching claims.
+
+If you omit the ID, the command lists out all of the existing claims and a
+few of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the `host-volume-read`
+capability in the volume's namespace.
+
+## Options
+
+- `-job`: Show only volume claims from a particular job ID.
+
+- `-group`: Show only volume claims from a particular task group name.
+
+- `-volume-name`: Show only volume claims from a particular volume name.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List of all task group host volume claim for job ID "example".
+
+```shell-session
+$ nomad volume claim list -job=example
+ID        Namespace  Job ID   Volume ID  Volume Name
+81b43af2  default    example  18377894   sticky-volume
+7ce38017  default    example  c3c27514   example-volume
+```
+
+List of all task group host volume claims, prefix by 81.
+.
+```shell-session
+$ nomad volume claim list 81
+ID        Namespace  Job ID   Volume ID  Volume Name
+81b43af2  default    example  18377894   sticky-volume
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
diff --git a/content/nomad/v1.10.x/content/commands/volume/create.mdx b/content/nomad/v1.10.x/content/commands/volume/create.mdx
new file mode 100644
index 0000000000..33a2992e15
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/create.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: 'nomad volume create command reference'
+description: |
+  The `nomad volume create` command creates storage volumes that are either
+  Container Storage Interface (CSI) volumes or dynamic host volumes.
+---
+
+# `nomad volume create` command reference
+
+The `volume create` command creates storage volumes as either [Container Storage
+Interface (CSI)][csi] volumes or dynamic host volumes.
+
+The `volume create` command can create dynamic host volumes if host volume
+plugins are installed on the node, or CSI volumes if the CSI plugins implement
+the [Controller][csi_plugins_internals] interface. The `volume create` command
+automatically [registers][] the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to a
+file containing a valid [volume specification][volume_specification]. Nomad
+reads the file and submits the volume to the server for placement. If the
+supplied path is "-", the volume file is read from STDIN. Otherwise the file is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-create` for dynamic host volumes.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode for dynamic
+  host volumes. After creating a volume, Nomad prints the volume ID to the
+  screen, which you can use to examine the volume using the `volume status`
+  command. If `-detach` is omitted or false, the command monitors the state of
+  the volume until it has been fingerprinted by the client and is ready to be
+  scheduled. Not valid for CSI volumes.
+
+- `-verbose`: Display full information when monitoring volume state. Used for
+  dynamic host volumes only. Not valid for CSI volumes.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies. 
+
+## Volume specification
+
+Refer to the [CSI Volume Specification][csi_vol_spec] and the [Dynamic Host
+Volume Specification][host_vol_spec] for further information.
+
+## General options
+
+@include 'general_options.mdx'
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[registers]: /nomad/commands/volume/register
+[registered]: /nomad/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
+[csi_vol_spec]: /nomad/docs/other-specifications/volume/csi
+[host_vol_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.10.x/content/commands/volume/delete.mdx b/content/nomad/v1.10.x/content/commands/volume/delete.mdx
new file mode 100644
index 0000000000..c74ae3ee76
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/delete.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad volume delete command reference'
+description: |
+  The `nomad volume delete` command deletes Container Storage Interface (CSI) and dynamic host storage volumes.
+---
+
+# `nomad volume delete` command reference
+
+The `volume delete` command deletes storage volumes that are either [Container
+Storage Interface (CSI)][csi] volumes or dynamic host volumes.
+
+For CSI volumes, only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface support this command. The volume
+is [deregistered][] when it is successfully deleted.
+
+For dynamic host volumes, only volumes with plugins are deleted. Volumes without
+plugins are deregistered without deleting them.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered][] with Nomad in
+order to be deleted. Deleting fails if the volume is still in use by an
+allocation or in the process of being unpublished.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-delete` for dynamic host volumes.
+
+## Options
+
+- `-force`: Delete the volume from the Nomad state store if the node has been
+  garbage collected. You should only use `-force` if the node will never rejoin
+  the cluster. Only available for dynamic host volumes.
+
+- `-secret`: Secrets to pass to the plugin to delete the snapshot. Accepts
+  multiple flags in the form `-secret key=value`. Only available for CSI
+  volumes.
+
+- `-type`: Type of volume to delete. Must be one of "csi" or "host". Defaults to
+  "csi".
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[deregistered]: /nomad/commands/volume/deregister
+[registered]: /nomad/commands/volume/register
diff --git a/content/nomad/v1.10.x/content/commands/volume/deregister.mdx b/content/nomad/v1.10.x/content/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..938bc4ba55
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/deregister.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad volume deregister command reference'
+description: |
+  The `nomad volume deregister` command deregisters Container Storage Interface (CSI) storage volumes.
+---
+
+# `nomad volume deregister` command reference
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+For dynamic host volumes, use the [`volume delete`][] command.
+
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/commands/volume/delete
diff --git a/content/nomad/v1.10.x/content/commands/volume/detach.mdx b/content/nomad/v1.10.x/content/commands/volume/detach.mdx
new file mode 100644
index 0000000000..ed3c39ecd1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad volume detach command reference'
+description: |
+  The `nomad volume detach` command detaches external storage volumes with Container Storage Interface (CSI) plugins.
+---
+
+# `nomad volume detach` command reference
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.10.x/content/commands/volume/index.mdx b/content/nomad/v1.10.x/content/commands/volume/index.mdx
new file mode 100644
index 0000000000..de0db6ef31
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad volume command reference'
+description: |
+  The `nomad volume` command interacts with volumes. Generate an example volume specification. Create, delete, register, and deregister a volume. Create and delete a volume snapshot. Display a list of volumes and status information for a single volume.
+---
+
+# `nomad volume` command reference
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+```plaintext
+nomad volume <subcommand> [options]
+```
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume claim delete`][claim-delete] - Delete a task group host volume claim.
+- [`volume claim list`][claim-list] - List task group host volume claims.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/commands/volume/create
+[claim-delete]: /nomad/commands/volume/claim-delete
+[claim-list]: /nomad/commands/volume/claim-list
+[delete]: /nomad/commands/volume/delete
+[deregister]: /nomad/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/commands/volume/detach 'Detach a volume'
+[init]: /nomad/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/commands/volume/snapshot-list
+[status]: /nomad/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.10.x/content/commands/volume/init.mdx b/content/nomad/v1.10.x/content/commands/volume/init.mdx
new file mode 100644
index 0000000000..30a18f001f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad volume init command reference'
+description: |
+  The `nomad volume init` command generates an example storage volume specification.
+---
+
+# `nomad volume init` command reference
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Options
+
+- `-json`: Create an example JSON volume specification.
+
+- `-type`: Create an example for a specific type of volume. Use either "csi" or
+  "host", defaults to "csi".
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.10.x/content/commands/volume/register.mdx b/content/nomad/v1.10.x/content/commands/volume/register.mdx
new file mode 100644
index 0000000000..a68ff9a3c2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/register.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'nomad volume register command reference'
+description: |
+  The `nomad volume register` command registers existing Container Storage Interface (CSI) and dynamic host storage volumes.
+---
+
+# `nomad volume register` command reference
+
+The `volume register` command registers storage volumes as either [Container
+Storage Interface (CSI)][csi] volumes or dynamic host volumes. The volume must
+already exist on a node or remote storage provider before you can register
+the volume for use in job task.
+
+To instead create a volume that does not already exist, use the [`volume
+create`][] command. The `volume create` command automatically registers the
+volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. Nomad
+reads the file and submits the volume to the server for placement. If the
+supplied path is "-", Nomad reads the volume file from STDIN. Otherwise Nomad
+reads the file from the supplied path.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-register` for dynamic host volumes.
+
+## Options
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies. 
+
+## Volume specification
+
+Refer to the [CSI Volume Specification][csi_vol_spec] and the [Dynamic Host
+Volume Specification][host_vol_spec] for further information.
+
+The `volume register` command allows updating a volume definition. However, you
+can only update some fields after the volume is registered.
+
+For CSI volumes:
+
+- Update the `capacity_min` and `capacity_max` fields and increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+- Add or remove the `capability` blocks, but only if the capability is
+  not currently in use by a mounted volume.
+- Update the `mount_options` block if the volume is not in use.
+- Update the `secrets` block.
+- Update the `context` block. The values for this field are typically provided
+  by the CSI plugin, and you should not update them unless recommended by the
+  CSI plugin's documentation.
+
+For dynamic host volumes:
+
+- Update the `capacity_min` and `capacity_max` fields. The fields are ignored
+  but must be consistent with the `capacity` value if set.
+- Update the `capacity` field to record that you've increased the size of the
+  volume. Reducing volume capacity is not allowed.
+- Update the `constraint` fields on `volume create`, but not after you create the volume.
+- Add or remove the `capability` blocks but only if a mounted volume is not
+  using currently using the capability.
+- Change the `node_pool` field only from empty to the node pool that matches the
+  `node_id` field.
+
+You cannot update the following:
+
+- The `name`, `type`, and `plugin_id` fields.
+- The `node_id` field.
+
+## General options
+
+@include 'general_options.mdx'
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/commands/volume/create
+[csi_vol_spec]: /nomad/docs/other-specifications/volume/csi
+[host_vol_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.10.x/content/commands/volume/snapshot-create.mdx b/content/nomad/v1.10.x/content/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..b2cb9b6e7d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'nomad volume snapshot create command reference'
+description: |
+  The `nomad volume snapshot create` command creates a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot create` command reference
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.10.x/content/commands/volume/snapshot-delete.mdx b/content/nomad/v1.10.x/content/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..1b7fe956b0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot delete command reference'
+description: |
+  The `nomad volume snapshot delete` command deletes a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot delete` command reference
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.10.x/content/commands/volume/snapshot-list.mdx b/content/nomad/v1.10.x/content/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..48702249e7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot list command reference'
+description: |
+  The `nomad volume snapshot list` command displays a list external Container Storage Interface (CSI) volume snapshots along with the source volume ID as known to the external storage provider.
+---
+
+# `nomad volume snapshot list` command reference
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.10.x/content/commands/volume/status.mdx b/content/nomad/v1.10.x/content/commands/volume/status.mdx
new file mode 100644
index 0000000000..bd7d7ad3fc
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/volume/status.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'nomad volume status command reference'
+description: |
+  The `nomad volume status` command displays volume information and status for a single volume or a list of volumes.
+---
+
+# `nomad volume status` command reference
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes or [dynamic host volumes][dhv].
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If
+there is an exact match based on the provided volume ID or prefix, then
+information about the specific volume is queried and displayed. Otherwise, a
+list of matching volumes and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a
+few of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-read-volume` and
+`csi-list-volumes` capability for CSI volumes, or `host-volume-read` for dynamic
+host volumes.
+
+## Options
+
+- `-type`: Display only volumes of a particular type (one of `"host"` or
+  `"csi"`). If omitted, the command will query for both dynamic host volumes and
+  CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume status
+Dynamic Host Volumes
+ID        Name             Namespace  Plugin ID            Node ID   Node Pool  State
+070dc8ca  internal-plugin  default    mkdir                c3c27514  default    ready
+7ce38017  external-plugin  default    example-plugin-mkfs  c3c27514  default    ready
+
+Container Storage Interface
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all CSI volumes, with external provider info:
+
+```shell-session
+$ nomad volume -type csi status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status -verbose ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/commands/volume/create
+[dhv]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.10.x/content/commands/windows/index.mdx b/content/nomad/v1.10.x/content/commands/windows/index.mdx
new file mode 100644
index 0000000000..ea165c3f3e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/windows/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'nomad windows command reference'
+description: |
+  The `nomad windows` command interacts with the Windows host platform. Install or uninstall Nomad as a Windows service.
+---
+
+# `nomad windows` command reference 
+
+Use the `windows` command to interact with Windows host platforms.
+
+## Usage 
+
+Usage: `nomad windows <subcommand> [options]`
+
+Run `nomad windows <subcommand> -h` for help on that subcommand. The following subcommands are available:
+
+- [`windows service install`][install] - Install Nomad as a Windows service
+- [`windows service uninstall`][uninstall] - Uninstall Nomad as a Windows service
+
+[install]: /nomad/commands/windows/service-install
+[uninstall]: /nomad/commands/windows/service-uninstall
diff --git a/content/nomad/v1.10.x/content/commands/windows/service-install.mdx b/content/nomad/v1.10.x/content/commands/windows/service-install.mdx
new file mode 100644
index 0000000000..d10904bac2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/windows/service-install.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'nomad windows service install command reference'
+description: |
+  The `nomad windows service install` command installs the Nomad binary
+  and creates a Windows service.
+---
+
+# `nomad windows service install` command reference
+
+The `windows service install` command installs the Nomad binary and
+creates a Windows service.
+
+## Usage
+
+```plaintext
+nomad windows service install
+```
+
+The `windows service install` command installs the `nomad` binary used to
+run this command, creates a data and configuration directory, writes a basic
+Nomad configuration file, creates a Windows service to run Nomad, and
+registers the service with Windows Event Log.
+
+If Nomad has been previously installed using this command, subsequent
+executions will do the following:
+
+1. Stop the service if it is running
+1. Install the currently executing nomad binary
+1. Ensure data and configuration directories exist
+1. Write a configuration file if no configuration files are found
+1. Update the service if needed
+1. Update the Event Log configuration if needed.
+
+## Options
+
+- `-config-dir <dir>`: Directory to hold the Nomad agent configuration.
+  Defaults to "{{.ProgramFiles}}\HashiCorp\nomad\bin"
+
+- `-data-dir <dir>`: Directory to hold the Nomad agent state. Defaults
+  to "{{.ProgramData}}\HashiCorp\nomad\data"
+
+- `-install-dir <dir>`: Directory to install the Nomad binary. Defaults 
+  to "{{.ProgramData}}\HashiCorp\nomad\config"
+
+- `-reinstall`: Allow the nomad Windows service to be stopped during install.
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.10.x/content/commands/windows/service-uninstall.mdx b/content/nomad/v1.10.x/content/commands/windows/service-uninstall.mdx
new file mode 100644
index 0000000000..f2f560f65b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/commands/windows/service-uninstall.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'nomad windows service uninstall command reference'
+description: |
+  The `nomad windows service uninstall` command removes the Nomad
+  Windows service.
+---
+
+# `nomad windows service uninstall` command reference
+
+The `windows service uninstall` command removes the Nomad Windows service.
+
+## Usage
+
+```plaintext
+nomad windows service uninstall
+```
+
+The `windows service uninstall` command stops the Nomad service if
+it is currently running, deregisters the service with the Windows Event Log,
+and removes the Windows service. This command does not remove the installed
+Nomad binary or the data and configuration directories.
diff --git a/content/nomad/v1.10.x/content/docs/architecture/cluster/consensus.mdx b/content/nomad/v1.10.x/content/docs/architecture/cluster/consensus.mdx
new file mode 100644
index 0000000000..961f023464
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/cluster/consensus.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol based on Raft to manage cluster node state. Learn about logs, Finite State Machine (FSM), peer set, quorum, committed entry, and leader. 
+---
+
+# Consensus Protocol
+
+This page provides conceptual information on Nomad's [consensus
+protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>), which
+provides [Consistency as defined by CAP](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.10.x/content/docs/architecture/cluster/federation.mdx b/content/nomad/v1.10.x/content/docs/architecture/cluster/federation.mdx
new file mode 100644
index 0000000000..aa00cbd3d2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/cluster/federation.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Federation
+description: |-
+  Nomad federation enables multiple Nomad clusters in different regions to work together seamlessly. Learn about cross-region request forwarding, replication, and Nomad Enterprise's multi-region job deployments.
+---
+
+# Federation
+
+This page provides conceptual information about the Nomad federation feature.
+Learn about cross-region request forwarding, replication, and Nomad Enterprise's
+multi-region job deployments.
+
+Nomad federation is a multi-cluster orchestration and management feature that
+enables multiple Nomad clusters running in different regions to work together
+seamlessly. By federating clusters, you benefit from improved scalability, fault
+tolerance, and centralized management of workloads across various data centers
+or geographical locations.
+
+## Cross-Region request forwarding
+
+API calls can include a `region` query parameter that defines the Nomad region
+the query is specified for. If this is not the local region, Nomad transparently
+forwards the request to a server in the requested region. When you omit the
+query parameter, Nomad uses the region of the server that is processing the
+request.
+
+## Replication
+
+Nomad writes the following objects in the authoritative region and replicates
+them to all federated regions:
+
+- ACL [policies][acl_policy], [roles][acl_role], [auth methods][acl_auth_method],
+  [binding rules][acl_binding_rule], and [global tokens][acl_token]
+- [Namespaces][namespace]
+- [Node pools][node_pool]
+- [Quota specifications][quota]
+- [Sentinel policies][sentinel_policies]
+
+When creating, updating, or deleting these objects, Nomad always sends the
+request to the authoritative region using RPC forwarding.
+
+Nomad starts replication routines on each federated cluster's leader server in a
+hub and spoke design. The routines then use blocking queries to receive updates
+from the authoritative region to mirror in their own state store. These routines
+also implement rate limiting, so that busy clusters do not degrade due to overly
+aggressive replication processes.
+
+<Note> Nomad writes ACL local tokens in the region where you make the request
+and  does not replicate those local tokens. </Note>
+
+## Multi-Region job deployments <EnterpriseAlert inline />
+
+Nomad job deployments can use the [`multiregion`][] block when running in
+federated mode. Multiregion configuration instructs Nomad to register and run
+the job on all the specified regions, removing the need for multiple job
+specification copies and registration on each region. Multiregion jobs do not
+provide regional failover in the event of failure.
+
+[acl_policy]: /nomad/docs/secure/acl/#policies
+[acl_role]: /nomad/docs/secure/acl/#roles
+[acl_auth_method]: /nomad/docs/secure/acl/#authentication-methods
+[acl_binding_rule]: /nomad/docs/secure/acl/#binding-rules
+[acl_token]: /nomad/docs/secure/acl/#tokens
+[node_pool]: /nomad/docs/architecture/cluster/node-pools
+[namespace]: /nomad/docs/other-specifications/namespace
+[quota]: /nomad/docs/other-specifications/quota
+[sentinel_policies]: /nomad/docs/reference/sentinel-policy
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.10.x/content/docs/architecture/cluster/node-pools.mdx b/content/nomad/v1.10.x/content/docs/architecture/cluster/node-pools.mdx
new file mode 100644
index 0000000000..d9993bb059
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/cluster/node-pools.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Node pools
+description: Nomad's node pools feature groups clients and segments infrastructure into logical units so that jobs have control over client allocation placement. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+---
+
+# Node pools
+
+This page contains conceptual information about Nomad's node pools feature.
+
+@include 'node-pools.mdx'
diff --git a/content/nomad/v1.10.x/content/docs/architecture/cpu.mdx b/content/nomad/v1.10.x/content/docs/architecture/cpu.mdx
new file mode 100644
index 0000000000..76742b8fb9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/cpu.mdx
@@ -0,0 +1,428 @@
+---
+layout: docs
+page_title: How Nomad Uses CPU
+description: Learn how Nomad discovers and uses CPU resources on nodes in order to place and run workloads. Nomad Enterprise can use non-uniform memory access (NUMA) scheduling, which is optimized for the NUMA topology of a client node.
+---
+
+# How Nomad Uses CPUs
+
+This page provides conceptual information on how Nomad discovers and uses CPU resources on nodes in order to place and run workloads.
+
+Every Nomad node has a Central Processing Unit (CPU) providing the computational
+power needed for running operating system processes. Nomad uses the CPU to
+run tasks defined by the Nomad job submitter. For Nomad to know which nodes
+have sufficient capacity for running a given task, each node in the cluster
+is fingerprinted to gather information about the performance characteristics
+of its CPU. The two metrics associated with each Nomad node with regard to
+CPU performance are its bandwidth (how much it can _compute_) and the number
+of cores.
+
+Modern CPUs may contain heterogeneous core types. Apple introduced the M1 CPU
+in 2020 which contains both _performance_ (P-Core) and _efficiency_ (E-Core)
+types. Each core type operates at a different base frequency. Intel introduced
+a similar topology in its Raptor Lake chips in 2022. When fingerprinting
+the characteristics of a CPU Nomad is capable of taking these advanced CPU
+topologies into account.
+
+[![PE Cores](/img/nomad-pe-cores.png)](/img/nomad-pe-cores.png)
+
+## Calculating CPU resources
+
+The total CPU bandwidth of a Nomad node is the sum of the product between the
+frequency of each core type and the total number of cores of that type in the
+CPU.
+
+```
+bandwidth = (p_cores * p_frequency) + (e_cores * e_frequency)
+```
+
+The total number of cores is computed by summing the number of P-Cores and the
+number of E-Cores.
+
+```
+cores = p_cores + e_cores
+```
+
+Nomad does not distinguish between logical and physical CPU cores. One of the
+defining differences between the P-Core and E-Core types is that the E-Cores
+do not support hyperthreading, whereas P-Cores do. As such a single physical
+P-Core is presented as 2 logical cores, and a single E-Core is presented as 1
+logical core.
+
+The example below is from a Nomad node with an Intel i9-13900 CPU. It is made
+up of mixed core types, with a P-Core base frequency of 2 GHz and an E-Core
+base frequency of 1.5 GHz.
+
+These characteristics are reflected in the `cpu.frequency.performance` and
+`cpu.frequency.efficiency` node attributes respectively.
+
+```text
+cpu.arch                        = amd64
+cpu.frequency.efficiency        = 1500
+cpu.frequency.performance       = 2000
+cpu.modelname                   = 13th Gen Intel(R) Core(TM) i9-13900
+cpu.numcores                    = 32
+cpu.numcores.efficiency         = 16
+cpu.numcores.performance        = 16
+cpu.reservablecores             = 32
+cpu.totalcompute                = 56000
+cpu.usablecompute               = 56000
+```
+
+## Reserving CPU resources
+
+In the fingerprinted node attributes, `cpu.totalcompute` indicates the total
+amount of CPU bandwidth the processor is capable of delivering. In some cases it
+may be beneficial to reserve some amount of a node's CPU resources for use by
+the operating system and other non-Nomad processes. This can be done in client
+configuration.
+
+The amount of reserved CPU can be specified in bandwidth via `cpu`.
+
+```hcl
+client {
+  reserved {
+    cpu = 3000 # mhz
+  }
+}
+```
+
+Or as a specific set of `cores` on which to disallow the scheduling of Nomad
+tasks. This capability is available on Linux systems only.
+
+```hcl
+client {
+  reserved {
+    cores = "0-3"
+  }
+}
+```
+
+When the CPU is constrained by one of the above configurations, the node
+attribute `cpu.usablecompute` indicates the total amount of CPU bandwidth
+available for scheduling of Nomad tasks.
+
+## Allocating CPU Resources
+
+When scheduling jobs, a Task must specify how much CPU resource should be
+allocated on its behalf. This can be done in terms of bandwidth in MHz with the
+`cpu` attribute. On Linux under cgroups v1, Nomad maps this MHz value directly
+into a [cpu.share][]. On Linux under cgroups v2, Nomad converts the MHz value to
+a [cpu.weight][] proportionally the same as the cgroups v1 `cpu.share`.
+
+```hcl
+task {
+  resources {
+    cpu = 2000 # mhz
+  }
+}
+```
+
+Note that the isolation mechanism around CPU resources is dependent on each task
+driver and its configuration. The standard behavior is that Nomad ensures a task
+has access to _at least_ as much of its allocated CPU bandwidth. In which case
+if a node has idle CPU capacity, a task may use additional CPU resources.  Some
+task drivers enable limiting a task to use only the amount of bandwidth
+allocated to the task, described in the [CPU Hard Limits](#cpu-hard-limits)
+section below.
+
+### Relative CPU shares/weights on Linux
+
+Linux cgroups are hierarchical, and the `cpu.share`/`cpu.weight` values reflect
+relative weights within a given subtree. Nomad creates its own cgroup subtree
+(`nomad.slice`) on startup, and all `cpu.share`/`cpu.weight` values that Nomad
+writes are relative between processes within that slice. The `nomad.slice`
+subtree is itself relative to another subtree on the host. For example, a host
+running systemd might have the following slices:
+
+```
+/sys/fs/cgroup
+├── nomad.slice
+│   ├── reserve.slice
+│   └── share.slice
+│       ├── 912dcc05-61e1-53cb-5489-a976a1231960.task.scope
+│       ├── 247e706a-6df8-4123-89b3-1bcf2846b503.task.scope
+│       └── 586c0c58-3d50-4730-b4ad-022076d3c6a4.task.scope
+├── system.slice
+│   ├── journald.service
+│   └── (various system services, etc.)
+└── user-1000.slice
+    ├── session-1.scope
+    └── (various user services, etc.)
+```
+
+If the task `912dcc05` has `resources.cpu = 1024` and tasks `247e706a` and
+`586c0c58` have `resources.cpu = 512`, then `912dcc05` will get 50% of the CPU
+resources available to the `nomad.slice` and tasks `247e706a` and `586c0c58`
+will get 25% each. (The `reserve.slice` and `share.slice` are passthrough for
+cpu shares here.) But together they'll get 33% of the total host's CPU resources
+unless the `nomad.slice`, `system.slice`, or `user-1000.slice` have something
+other than the default 1024 shares. The 1024 value is only meaningful within the
+context of the Nomad slice.
+
+### Allocating cores
+
+On Linux systems, Nomad supports reserving whole CPU cores specifically for a
+task. No task will be allowed to run on a CPU core reserved for another task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+  }
+}
+```
+
+We recommend using `resources.cores` for tasks that require high CPU performance
+to give those tasks exclusive access to CPU bandwidth. Sidecar tasks in the same
+allocations can use `resources.cpu` to get a proportional share of the remaining
+CPU on the node.
+
+Nomad Enterprise supports NUMA aware scheduling, which enables operators to
+more finely control which CPU cores may be reserved for tasks.
+
+### CPU hard limits
+
+Some task drivers support the configuration option `cpu_hard_limit`. If enabled
+this option restricts tasks from bursting above their CPU limit even when there
+is idle capacity on the node. The tradeoff is consistency versus utilization.
+A task with too few CPU resources may operate fine until another task is placed
+on the node causing a reduction in available CPU bandwidth, which could cause
+disruption for the underprovisioned task.
+
+### CPU environment variables
+
+To help tasks understand the resources available to them, Nomad sets the
+following environment variables in their runtime environment.
+
+
+- `NOMAD_CPU_LIMIT` - The amount of CPU bandwidth allocated on behalf of the
+  task.
+- `NOMAD_CPU_CORES` - The set of cores in [cpuset][] notation reserved for the
+  task. This value is only set if `resources.cores` is configured.
+
+```sh
+NOMAD_CPU_CORES=3-5
+NOMAD_CPU_LIMIT=9000
+```
+
+## NUMA
+
+Nomad clients are commonly provisioned on real hardware in an on-premise
+environment or in the cloud on large `.metal` instance types. In either case, it
+is likely the underlying server is designed around a [non-uniform memory access (NUMA) topology][numa_wiki].
+Servers that contain multiple CPU sockets or multiple RAM banks per CPU socket
+are characterized by the non-uniform access times involved in accessing system
+memory.
+
+[![NUMA](/img/nomad-numa.png)](/img/nomad-numa.png)
+
+The simplified example machine above has the following topology:
+- 2 physical CPU sockets
+- 4 system memory banks, 2 per socket
+- 8 physical cpu cores (4 per socket)
+- 2 logical cpu cores per physical core
+- 4 PCI devices, 1 per memory bank
+
+### Optimizing performance
+
+Operating system processes take longer to access memory across a NUMA boundary.
+
+Using the example above if a task is scheduled on Core 0, accessing memory in
+Mem 1 might take 20% longer than accessing memory in Mem 0, and accessing memory
+in Mem 2 might take 300% longer.
+
+The extreme differences are due to various physical hardware limitations. A core
+accessing memory in its own NUMA node is optimal. Programs which perform a high
+throughput of reads or writes to/from system memory will have their performance
+substantially hindered by not optimizing their spatial locality with regard to
+the systems NUMA topology.
+
+### SLIT tables
+
+Modern machines will define System Locality Distance Information (SLIT) tables
+in their firmware. These tables are understood and made referenceable by the
+Linux kernel. There are two key pieces of information provided by SLIT tables:
+- Which CPU cores belong to which NUMA nodes
+- The penalty incurred for accessing each NUMA node from a core in every other
+NUMA node
+
+The `lscpu` command can be used to describe the Core associativity on a machine.
+For example on an `r6a.metal` EC2 instance:
+
+```shell-session
+$ lscpu | grep NUMA
+NUMA node(s):           4
+NUMA node0 CPU(s):      0-23,96-119
+NUMA node1 CPU(s):      24-47,120-143
+NUMA node2 CPU(s):      48-71,144-167
+NUMA node3 CPU(s):      72-95,168-191
+```
+
+And the associated performance degradations are available via `numactl`:
+
+```shell-session
+$ numactl -H
+available: 4 nodes (0-3)
+...
+node distances:
+node   0   1   2   3
+  0:  10  12  32  32
+  1:  12  10  32  32
+  2:  32  32  10  12
+  3:  32  32  12  10
+```
+
+These SLIT table node distance values are presented as approximate relative
+ratios. The value of 10 represents an optimal situation where a memory access
+is occurring from a CPU that is part of the same NUMA node. A value of 20 would
+indicate a 200% performance degradation, 30 for 300%, etc.
+
+### Node Attributes
+
+Nomad clients will fingerprint the machine's NUMA topology and export the
+core associativity as node attributes. This data can provide a Nomad operator
+a better understanding of when it might be useful to make use of NUMA aware
+scheduling for certain workloads.
+
+```
+numa.node.count       = 4
+numa.node0.cores      = 0-23,96-119
+numa.node1.cores      = 24-47,120-143
+numa.node2.cores      = 48-71,144-167
+numa.node3.cores      = 72-95,168-191
+```
+
+## NUMA aware scheduling <EnterpriseAlert inline />
+
+Nomad Enterprise is capable of scheduling tasks in a way that is optimized for
+the NUMA topology of a client node. Nomad is able to correlate CPU cores with
+memory nodes and assign tasks to run on specific CPU cores so as to minimize any
+cross-memory node access patterns. Additionally, Nomad is able to correlate
+devices to memory nodes and enable NUMA-aware scheduling to take device
+associativity into account when making scheduling decisions.
+
+A task may specify a `numa` block indicating its NUMA optimization preference. This example allocates a `1080ti` GPU and ensures it is on the same NUMA node as the 4 CPU cores reserved for the task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+    memory = 2048
+
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+
+    numa {
+      affinity = "require"
+      devices = [
+        "nvidia/gpu/1080ti"
+      ]
+	  }
+  }
+}
+```
+
+### `affinity` options
+
+This is a required field. There are three supported affinity options:
+`none`, `prefer`, and `require`, each with their own advantages and tradeoffs.
+
+#### option `none`
+
+In the `none` mode, the Nomad scheduler leverages the apathy of jobs without
+preference of NUMA affinity to help reduce core fragmentation within NUMA nodes.
+It does so by bin-packing the core request of these jobs onto the NUMA nodes
+with the fewest unused cores available.
+
+The `none` mode is the default mode if the `numa` block is not specified.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "none"
+  }
+}
+```
+
+#### option `prefer`
+
+In the `prefer` mode, the Nomad scheduler uses the hardware topology of a node
+to calculate an optimized selection of available cores, but does not limit
+those cores to come from a single NUMA node.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "prefer"
+  }
+}
+```
+
+#### option `require`
+
+In the `require` mode, the Nomad scheduler uses the topology of each potential
+client to find a set of available CPU cores that belong to the same NUMA node.
+If no such set of cores can be found, that node is marked exhausted for the
+resource of `numa-cores`.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "require"
+  }
+}
+```
+
+### `devices` options
+
+`devices` is an optional list of devices that must be colocated on the NUMA node
+along with allocated CPU cores.
+
+The following diagram shows how a set of devices can be correlated to CPU and memory.
+
+[![How a set of devices can be correlated to CPU and memory](/img/nomad-devices-correlate-cpu-memory.png)](/img/nomad-devices-correlate-cpu-memory.png)
+
+This example declares three devices and configures two in the `numa` block.
+
+```hcl
+task {
+  resources {
+    cores = 8
+    memory = 16384
+
+    device "nvidia/gpu/H100" {
+      count = 2
+    }
+    device "intel/net/XXVDA2" {
+      count = 1
+    }
+    device "xilinx/fpga/X7" {
+      count = 1
+    }
+
+    numa {
+	    affinity = "require"
+	    devices = [
+  	    "nvidia/gpu/H100",
+  	    "intel/net/XXVDA2"
+	    ]
+    }
+  }
+}
+```
+
+## Virtual CPU fingerprinting
+
+When running on a virtualized host such as Amazon EC2 Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions will
+require installing the `dmidecode` package manually.
+
+[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
+[cpu.share]: https://www.redhat.com/sysadmin/cgroups-part-two
+[cpu.weight]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#weights
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
diff --git a/content/nomad/v1.10.x/content/docs/architecture/index.mdx b/content/nomad/v1.10.x/content/docs/architecture/index.mdx
new file mode 100644
index 0000000000..a06acf316d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/index.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Architecture
+description: |-
+  Nomad's system architecture supports a "run any workload anywhere" approach to scheduling and orchestration. Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+---
+
+# Architecture
+
+This page provides conceptual information on Nomad architecture.  Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+
+Nomad is a complex system that has many different pieces. To help both users and
+developers of Nomad build a mental model of how it works, this page documents
+the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/how-scheduling-works).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/architecture/cluster/consensus),
+[gossip protocol](/nomad/docs/architecture/security/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/how-scheduling-works)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.10.x/content/docs/architecture/security/gossip.mdx b/content/nomad/v1.10.x/content/docs/architecture/security/gossip.mdx
new file mode 100644
index 0000000000..2d1b698af6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/security/gossip.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Learn how Nomad's gossip protocol uses the Serf library to provide server membership management, which includes cross-region requests, failure detection, and automatic clustering using a consensus protocol.
+---
+
+# Gossip Protocol
+
+This page provides conceptual information about Nomad's gossip protocol, which
+provides server membership management, cross-region requests, failure detection,
+and automatic clustering using a consensus protocol.
+
+Nomad uses the [Serf library][serf] to provide a [gossip
+protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to manage membership.
+The gossip protocol used by Serf is based on ["SWIM: Scalable Weakly-consistent
+Infection-style Process Group Membership Protocol"][swim], with a few minor
+adaptations. There are more details about [Serf's protocol here][gossip].
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate
+in. Membership information provided by the gossip pool allows servers to perform
+cross region requests. The integrated failure detection allows Nomad to
+gracefully handle an entire region losing connectivity, or just a single server
+in a remote region. Nomad also uses the gossip protocol to detect servers in the
+same region to perform automatic clustering via the [consensus
+protocol](/nomad/docs/architecture/cluster/consensus).
+
+To provide all these features, Nomad uses [Serf][serf] as an embedded
+library. From a user perspective, this is not important, since Nomad masks the
+abstraction. However, developers may find it useful to understand how Nomad
+leverages the Serf library.
+
+
+[serf]: https://github.com/hashicorp/serf
+[gossip]: https://github.com/hashicorp/serf/blob/master/docs/internals/gossip.html.markdown
+[swim]: https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf
diff --git a/content/nomad/v1.10.x/content/docs/architecture/security/index.mdx b/content/nomad/v1.10.x/content/docs/architecture/security/index.mdx
new file mode 100644
index 0000000000..14c751743a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/security/index.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad's security model provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel policies (Enterprise), and resource quotas (Enterprise) to enable fine-grained access within and between clusters. Learn how to secure your Nomad clusters with threat models for internal threats and external threats. Review the network ports used by the security model.
+---
+
+# Security Model
+
+This page provides conceptual information on Nomad's security model, which
+provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel
+policies, and resource quotas to enable fine-grained access within and between
+clusters. Learn how to secure your Nomad clusters, threat models, internal
+threats, and external threats. Review the network ports used by the security
+model.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/docs/secure/traffic/tls)** Mutual
+  authentication of both the TLS server and client x509 certificates prevents
+  internal abuse by preventing unauthenticated access to network components
+  within the cluster.
+
+- **[ACLs](/nomad/docs/secure/acl)** Enables authorization for
+  authenticated connections by granting capabilities to ACL tokens.
+
+- **[Namespaces](/nomad/docs/govern/namespaces)** Access to read
+  and write to a namespace can be controlled to allow for granular access to job
+  information managed within a multi-tenant cluster.
+
+- **[Sentinel Policies]**<EnterpriseAlert inline /> Sentinel
+  policies allow for granular control over components such as task drivers
+  within a cluster.
+
+## Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/docs/secure/acl).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+## Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+### Requirements
+
+- [mTLS enabled](/nomad/docs/secure/traffic/tls)
+  Mutual TLS (mTLS) enables [mutual
+  authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+  security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+    Some API endpoints, such as [`/v1/metrics`][api_metrics] and
+    [`/v1/status/peers`][api_status_peers], can be accessed without an ACL
+    token and may be exposed to anyone with access to the Nomad HTTP address
+    when using `tls.verify_https_client=false`. You can use a reverse proxy or
+    other external means to restrict access to them.
+
+- [ACLs enabled](/nomad/docs/secure/acl) The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- [Namespaces](/nomad/docs/govern/namespaces) This feature
+    allows for a cluster to be shared by multiple teams within a company. Using
+    this logical separation is important for multi-tenant clusters to prevent
+    users without access to that namespace from conflicting with each other.
+    This requires ACLs to be enabled in order to be enforced.
+
+- [Sentinel Policies]<EnterpriseAlert inline />
+  [Sentinel](https://www.hashicorp.com/sentinel/) is a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- [Resource Quotas]<EnterpriseAlert inline /> Can limit a
+  namespace's access to the underlying compute resources in the cluster by
+  setting upper-limits for operators. Access to these resource quotas can be
+  managed via ACLs to ensure read-only access for operators so they can't just
+  change their quotas.
+
+### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/secure/vault) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/job-declare/task-driver/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/job-declare/task-driver/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/job-declare/task-driver/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+## Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec)
+  driver.
+
+### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+## Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                           |
+|----------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                   |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/architecture/security/gossip) protocol to manage server membership using [Serf][serf].                                                                        |
+
+
+[api_metrics]: /nomad/api-docs/metrics
+[api_status_peers]: /nomad/api-docs/status#list-peers
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[serf]: https://github.com/hashicorp/serf
+[Sentinel Policies]: /nomad/docs/govern/sentinel
+[Resource Quotas]: /nomad/docs/govern/resource-quotas
diff --git a/content/nomad/v1.10.x/content/docs/architecture/storage/csi.mdx b/content/nomad/v1.10.x/content/docs/architecture/storage/csi.mdx
new file mode 100644
index 0000000000..a478733c4b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/storage/csi.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: Container Storage Interface (CSI) Plugins
+description: |-
+  Nomad's Container Storage Interface (CSI) plugin support enables scheduling tasks with external storage volumes that conform to the CSI specification, including AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, and Ceph. Learn about controller, node, and monolith storage plugins, as well as storage volume lifecycle and state.
+---
+
+# Container Storage Interface (CSI) Plugins
+
+This page provides conceptual information on Nomad's storage plugin support,
+which enables scheduling tasks with external storage volumes that conform to the
+Container Storage Interface (CSI), including AWS Elastic Block Storage (EBS)
+volumes, Google Cloud Platform (GCP) persistent disks, and Ceph. Learn
+about controller, node, and monolith storage plugins, as well as storage volume
+lifecycle and state.
+
+## Introduction
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+[Container Storage Interface][csi-spec] specification unifies these APIs in a
+way that's agnostic to both the storage vendor and the container orchestrator.
+Each storage provider can build its own CSI plugin. Jobs can claim storage
+volumes from AWS Elastic Block Storage (EBS) volumes, GCP persistent disks,
+and Ceph. The Nomad scheduler will be aware of volumes created by
+CSI plugins and schedule workloads based on the availability of volumes on a
+given Nomad client node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.10.x/content/docs/architecture/storage/host-volumes.mdx b/content/nomad/v1.10.x/content/docs/architecture/storage/host-volumes.mdx
new file mode 100644
index 0000000000..0cb98fc109
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/storage/host-volumes.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Host volumes
+description: |-
+  Host volumes mount paths from the Nomad client into allocations. Learn how Nomad supports static and dynamic host volumes.
+---
+
+# Host volumes
+
+## Introduction
+
+@include 'storage/host-volume-explanation.mdx'
+
+## Resources
+
+- [Considerations for stateful workloads](/nomad/docs/architecture/storage/stateful-workloads)
+- [Use dynamic host volumes](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+- [Create a custom host volume plugin](/nomad/plugins/author/host-volume)
+- [Use static host volumes](/nomad/docs/stateful-workloads/static-host-volumes)
diff --git a/content/nomad/v1.10.x/content/docs/architecture/storage/index.mdx b/content/nomad/v1.10.x/content/docs/architecture/storage/index.mdx
new file mode 100644
index 0000000000..03da12190d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/storage/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: |-
+  Storage plugins help you schedule job tasks with dynamically managed storage volumes. Dynamic host volume plugins provision host volumes on client nodes. Container Storage Interface (CSI) plugins provision volumes in
+  third-party systems, such as AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, and Ceph.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with dynamically managed storage volumes.
+
+Choose between two types of storage plugins:
+
+* [Dynamic host volume (DHV) plugins][dhv] provision host volumes on client
+  nodes, and jobs request placement on any node that has a particular host
+  volume by name.
+  * DHV brings allocations to volumes.
+  * Install DHV plugins on Nomad nodes, similar to task drivers. Creating a
+    host volume ties it to the node until the volume is deleted.
+* [Container Storage Interface (CSI) plugins][csi] provision volumes in
+  third-party systems, such as cloud vendors. Nomad calls on them to make
+  the volume available on any node that Nomad chooses to place an allocation.
+  * CSI brings volumes to allocations.
+  * Deploy CSI plugins as Nomad jobs, often two jobs per plugin. Nomad tracks
+    which clients have instances of a given plugin, so it can call on the
+    plugin to mount the volume.
+
+[dhv]: /nomad/docs/architecture/storage/host-volumes
+[csi]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.10.x/content/docs/architecture/storage/stateful-workloads.mdx b/content/nomad/v1.10.x/content/docs/architecture/storage/stateful-workloads.mdx
new file mode 100644
index 0000000000..9f7a9a466d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/architecture/storage/stateful-workloads.mdx
@@ -0,0 +1,214 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad. Compare AWS, Azure, and Google Cloud Platform (GCP) storage services. Review the advantages and disadvantages of using Container Storage Interface (CSI) volumes, dynamic host volumes, static host volumes, and ephemeral disks.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. Refer to the [Container Storage Interface
+(CSI) plugins page][csi-concepts] for more information.
+
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+guide](/nomad/docs/stateful-workloads/csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+@include 'storage/host-volume-explanation.mdx'
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Dynamic host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost unless the application can restore the data</li></ul>  | <ul><li>Environments with high performance and low latency persistent storage requirements where the application is designed to tolerate node failures.</li></ul>   |
+| Dynamic host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Static host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Static host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/docs/monitor/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/architecture/storage/csi)
+- [Nomad CSI tutorial](/nomad/docs/stateful-workloads/csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
+
+### Dynamic Host Volumes
+
+- [Dynamic host volumes](/nomad/docs/architecture/storage/host-volumes)
+- [Dynamic host volume guide](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+- [Custom host volume plugin](/nomad/plugins/host-volume)
diff --git a/content/nomad/v1.10.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.10.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..ba13892c11
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,495 @@
+---
+layout: docs
+page_title: Allocation Filesystems
+description: |-
+  Learn how Nomad uses allocation working directories to store job task templates, storage volumes, artifacts, dispatch payloads, and logs. Review image and chroot isolation, as well as when Nomad uses isolation mode.
+---
+
+# Allocation Filesystems
+
+This page provides conceptual information about how Nomad uses allocation
+working directories to store job task templates, storage volumes, artifacts,
+dispatch payloads, and logs. Review image and chroot isolation, as well as when
+Nomad does not use any isolation mode.
+
+Nomad creates a working directory for each allocation on a client. Find this
+directory in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, writes logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like this example.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k,noswap)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/architecture/storage/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/deploy/task-driver/exec#chroot
+[filesystem isolation capability]: /nomad/plugins/author/task-driver#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.10.x/content/docs/concepts/job.mdx b/content/nomad/v1.10.x/content/docs/concepts/job.mdx
new file mode 100644
index 0000000000..0ee6026381
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/job.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: Job
+description: |-
+  Learn how a Nomad workload, called a job, deploys your apps, maintenance scripts, cron jobs, and similar tasks. Review job statuses and how Nomad versions your jobs.
+---
+
+# Job
+
+This page contains conceptual information about jobs, which are the main Nomad
+constructs for workloads that run your apps, maintenance scripts, cron jobs, and
+other tasks. Review job statuses and how Nomad versions your jobs.
+
+## Background
+
+In Nomad, a _job_ is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into [task groups][task-groups].
+
+Declare the desired state of your job in a [job specification][job-spec], or _jobspec_, that describes
+the tasks and resources necessary for the job to run. You can also
+include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual
+job state matches your desired state.
+
+## Job statuses
+
+After you submit your job, Nomad assigns a status to indicate how a job is
+performing. This status indicates how the job's current allocations compare to
+the desired job state.
+
+@include 'job-status-map.mdx'
+
+### CLI statuses
+
+Only the CLI returns these job statuses.
+
+#### `running`
+
+The `running` status indicates that the job has non-terminal allocations.
+
+#### `dead`
+
+The `dead` status indicates that all evaluations and allocations are in a
+terminal state.
+
+#### `dead (stopped)`
+
+The `dead (stopped)` status indicates that a user has manually stopped the job.
+You may start this job again.
+
+### UI statuses
+
+These job statuses only appear in the Nomad UI.
+
+#### Complete
+
+The `Complete` status indicates that all expected allocations are complete. This
+status applies to batch and sysbatch jobs only.
+
+#### Degraded
+
+The `Degraded` status indicates that a [deployment] is not taking place. Some
+allocations are failed, lost, or unplaced.
+
+#### Deploying
+
+The `Deploying` status indicates that a deployment is actively taking place.
+
+#### Failed
+
+The `Failed` status indicates that all allocations are failed, lost, or unplaced.
+
+#### Healthy
+
+The `Healthy` status indicates that all expected allocations are running and
+healthy.
+
+#### Recovering
+
+The `Recovering` status indicates that some allocations are pending.
+
+#### Removed
+
+The `Removed` status indicates that the job appeared in the initial query, but
+the garbage collector has since removed the job. This happens when the user
+remains on the page for a long time.
+
+#### Running
+
+The `Running` status indicates that all expected allocations are running. This
+status applies to batch and sysbatch jobs only.
+
+#### Scaled Down
+
+The `Scaled Down` status indicates that a user has scaled all allocations to
+zero. Nomad's garbage collector has not yet removed or purged the job.
+
+#### Stopped
+
+The `Stopped` status indicates that a user has manually stopped the job.
+Nomad's garbage collector has not yet removed or purged the job.
+
+## Job versions
+
+Nomad creates a new version for your job each time you run your job. A job can
+have an unlimited number of versions, and version history is stored in state.
+Over time, Nomad garbage collects dead versions that do not have a version tag.
+
+### Tag a version
+
+When you want to save or pin a specific version, you need to create a version
+tag with a unique name and optional description. Nomad does not garbage collect
+tagged versions even when the tagged version is dead. This lets you revert to
+a previous version regardless of how old the tagged version is.
+
+You can create, modify, and remove tags using the CLI, API, and web UI. Refer to
+the [Job versions guide][job-versions-guide] for examples.
+
+### Compare versions
+
+You can compare the current job version to all previous versions or to a
+specific version. Additionally, you can compare two specific versions.
+
+Run commands like `nomad job history` to review differences between past versions
+of jobs and their immediate predecessors. Additionally, you can run `nomad job
+plan` to review the hypothetical difference of an update against the current job
+version.
+
+Refer to the [Compare versions section][compare-versions-section] of the Job
+versions guide for examples.
+
+### Revert to a previous version
+
+You can revert the current running job to a previous version. Nomad stops the
+running job and deploys the chosen version with a new version number.
+
+Refer to the [Revert to a version section][revert-version-section] of
+the Job versions guide for examples using the CLI, API, and web UI.
+
+### Clone and edit
+
+Using the web UI, you may clone a version as a new version of the same job or as
+a new job. After you select the version to clone, you may edit, plan, and run
+the new version.
+
+Because Nomad passes job version attributes using query parameters, you can copy
+the browser address bar URL on the **Jobs/Run** screen to send a link to an
+editable job spec.
+
+Refer to the [Clone a version section][clone-version-section] of
+the Job versions guide for cloning examples.
+
+## Related resources
+
+Refer to the following Nomad documentation pages for more information about
+jobs:
+
+- The [job specification][job-spec] contains detailed
+  configuration and examples.
+- The [Schedulers] page explains the different types of Nomad schedulers and how
+  those schedulers run jobs.
+- The [Declare jobs][deploy-jobs] section contains guides for creating a job,
+  using task drivers, and deployment strategies.
+
+These tutorial resources contain examples of different kinds of jobs and how to
+configure them:
+
+- The [Quick Start][quickstart] tutorials cover deploying an application and
+  its resources, which include parameterized and periodic jobs.
+- The [Create Nomad Job Specifications][job-spec-tutorial] collection contains
+  guides for migrating a Java application to Nomad.
+
+
+[allocations]: /nomad/docs/glossary#allocation
+[deployment]: /nomad/docs/glossary/#deployment
+[deploy-jobs]: /nomad/docs/job-declare
+[job-spec]: /nomad/docs/job-specification
+[job-spec-tutorial]: /nomad/tutorials/job-specifications
+[quickstart]: /nomad/tutorials/get-started/gs-deploy-job
+[Schedulers]: /nomad/docs/concepts/scheduling/schedulers
+[task-groups]: /nomad/docs/glossary#task-group
+[tasks]: /nomad/docs/glossary#task
+[job-versions-guide]: /nomad/docs/job-run/versions
+[compare-versions-section]: /nomad/docs/job-run/versions#compare-versions
+[revert-version-section]: /nomad/docs/job-run/versions#revert-to-a-version
+[clone-version-section]: /nomad/docs/job-run/versions#clone-a-version
diff --git a/content/nomad/v1.10.x/content/docs/concepts/scheduling/how-scheduling-works.mdx b/content/nomad/v1.10.x/content/docs/concepts/scheduling/how-scheduling-works.mdx
new file mode 100644
index 0000000000..4dad4a9862
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/scheduling/how-scheduling-works.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: How Nomad job scheduling works
+description: Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+---
+
+# How Nomad job scheduling works
+
+This page provides conceptual information on how Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary components in Nomad: jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.10.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.10.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..202383f8cd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Scheduling workloads
+description: Nomad's scheduling component assigns jobs to client machines. Explore scheduling internals, placement, and preemption.
+---
+
+# Scheduling workloads
+
+Scheduling workloads is the process of assigning tasks from jobs to client machines.
+It is one of Nomad's core functions. The design is heavily inspired by Google's
+work on both [Omega: flexible, scalable schedulers for large compute
+clusters][omega] and [Large-scale cluster management at Google with Borg][borg].
+Refer to the links below for implementation details on scheduling in Nomad.
+
+- [How scheduling works](/nomad/docs/concepts/scheduling/how-scheduling-works) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of
+  preemption, an advanced scheduler feature.
+- [Nomad job schedulers](/nomad/docs/concepts/scheduling/schedulers) - Explains the different types of job schedulers.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.10.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.10.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..59cedd36c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Allocation Placement
+description: Nomad uses allocation placement when scheduling jobs to run on clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+---
+
+# Allocation Placement
+
+This page provides conceptual information about job allocation placement on
+clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+## Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+## Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+## Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+## Understanding Evaluation Status
+
+When a job cannot be immediately placed, Nomad creates a chain of evaluations
+to manage placement. First, your initial evaluation may be marked complete even if
+placement fails. Then Nomad creates a blocked evaluation to retry placement when
+resources become available. Your job remains pending until Nomad places all allocations.
+
+For example, if your job has specific constraints that are not available, you
+get an initial completed evaluation and a blocked evaluation. Nomad tracks
+ongoing placement attempts until a node that fits your constraints is available.
+
+To troubleshoot placement issues, use `nomad eval status <eval_id>`. Check the output
+for placement failures and linked evaluations.
+
+[api_client_metadata]: /nomad/api-docs/client#update-dynamic-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/architecture/cluster/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.10.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.10.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..95a85738ee
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: Allocation Preemption
+description: Nomad uses preemption to evict existing allocations in order to place allocations for a higher priority job. Learn how Nomad uses job priority to preempt running allocations and how you can determine whether Nomad preempted an allocation. Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+---
+
+# Allocation Preemption
+
+This page provides conceptual information about preemption, which is evicting
+existing allocations in order to place allocations for a higher priority job.
+Learn how Nomad uses job priorty to determine when to preempt running
+allocations and how you can determine whether Nomad has preempted an allocation.
+Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+
+Preemption allows Nomad to kill existing allocations in order to place
+allocations for a higher priority job. The evicted allocation is temporarily
+displaced until the cluster has capacity to run it. This allows operators to run
+high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+## Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+## Details
+
+Preemption is enabled by default for system jobs. You can use the [scheduler
+config][sched-config-api] API endpoint or [`nomad operator scheduler
+set-config`][sched-config-cli] commands to disable preemption or enable it for
+other job types.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of 10 or greater compared to the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+## Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+## Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
+[sched-config-api]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[sched-config-cli]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.10.x/content/docs/concepts/scheduling/schedulers.mdx b/content/nomad/v1.10.x/content/docs/concepts/scheduling/schedulers.mdx
new file mode 100644
index 0000000000..95373cd979
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/scheduling/schedulers.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Nomad job schedulers
+description: Learn how Nomad's service, batch, system, and system batch job schedulers enable flexible workloads.
+---
+
+# Nomad job schedulers
+
+This page provides conceptual information about Nomad service, batch, system,
+and system batch job schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.10.x/content/docs/concepts/stateful-deployments.mdx b/content/nomad/v1.10.x/content/docs/concepts/stateful-deployments.mdx
new file mode 100644
index 0000000000..bff80bfd57
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/stateful-deployments.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: Stateful deployments
+description: |-
+  Learn how Nomad handles stateful deployments. Use a dynamic host volume for your stateful workload and bind an allocation to a volume ID with the sticky parameter. Learn how Nomad scales jobs with sticky volumes.
+---
+
+# Stateful deployments
+
+<Note>
+
+Stateful deployments support only dynamic host volumes. For CSI volumes, use the
+[`per_alloc` property](/nomad/docs/job-specification/volume#per_alloc),
+which serves a similar purpose.
+
+</Note>
+
+Nomad stateful deployments let you effectively bind your jobs to host [volumes].
+On a lower level, this means taking Nomad's basic unit of workload placement,
+the [allocation], and making it possible for you to have allocations that are
+[sticky] to volume IDs. Since stateful deployments only support dynamic host
+volumes, using them effectively means binding a job to a particular node.
+
+Stateful deployments work on a per-task-group basis. Use the `volume.sticky`
+parameter in your job specification to indicate that each task group requires a
+sticky host volume.
+
+This example sets the volume's `sticky` parameter to `true`.
+
+```hcl
+job "app" {
+  group "example" {
+    # ...
+    volume "example" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+      sticky    = true
+    }
+    # ...
+  }
+}
+```
+
+If you set the volume to sticky, during the deployment the scheduler associates
+its ID with the task group that uses it. Stateful deployments require that any
+allocations belonging to that task group must be places or replaced on nodes
+that have this volume ID available.
+
+Scaling jobs with sticky volumes up results in more volume IDs claimed by the
+task group, but scaling jobs down does not delete unused volumes, nor does it
+touch the data present on them.
+
+If the scheduler cannot find a node that has the right volume ID present,
+perhaps because the node is down or disconnected, Nomad creates a blocked
+evaluation.
+
+## Task group host volume claims
+
+Nomad uses its state store to save associations of host volume IDs and their
+task groups, as well as job IDs, volume names, and namespaces. Use the API to
+[list] and [delete] these associations. If you delete a task group host volume
+claim, Nomad assigns a different volume ID to the task group, assuming the old
+volume ID is unavailable and another feasible host volume with matching name is.
+However, after placement, Nomad once again records the claim in its state store.
+You should only use claim deletions in operational emergency situations or while
+debugging problems with nodes. For example, use claim deletions in situations
+where you want to drain a node with a stateful deployment on it, but do not want
+to stop the job.
+
+## Related resources
+
+Refer to the following Nomad pages for more information about stateful workloads
+and volumes:
+
+- [Considerations for Stateful Workloads](/nomad/docs/architecture/storage/stateful-workloads) explores the options for persistent storage of workloads running in Nomad.
+- The [Nomad volume specification][volumes] defines the schema for creating and registering volumes.
+- The [job specification `volume` block](/nomad/docs/job-specification/volume) lets you configure a group that requires a specific volume from the cluster.
+- The [Stateful Workloads](/nomad/docs/stateful-workloads) guides explore techniques to run jobs that require access to persistent storage.
+
+[allocation]: /nomad/docs/glossary#allocation
+[delete]: /nomad/api-docs/volumes#delete-task-group-host-volume-claims
+[list]: /nomad/api-docs/volumes#list-task-group-host-volume-claims
+[sticky]: /nomad/docs/job-specification/volume#sticky
+[volumes]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.10.x/content/docs/concepts/variables.mdx b/content/nomad/v1.10.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..170253c5e3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Nomad variables
+description: Nomad's variables feature lets you store and use encrypted configuration data in your job specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+---
+
+# Nomad variables
+
+This page contains conceptual information about the Nomad variables feature,
+which lets you store and use encrypted configuration data in your job
+specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+
+## Introduction
+
+Most Nomad workloads need access to configuration values or secrets. Nomad has a
+`template` block to [provide these values to
+tasks](/nomad/docs/job-specification/template#nomad-variables). Nomad variables
+provide the option to store configuration at file-like paths
+directly in Nomad's state store so that you can access these variables directly from
+your task templates. Nomad encrypts and replicates the contents of these variables between servers with Raft communication. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as variables. These should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. Refer to [Key Management][] for details.
+
+## Policies
+
+Every variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. Refer to the [ACL policy
+specification] for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include a wildcard symbol that allows
+a single path policy definition to apply to a set of paths within that
+namespace.
+
+In the following example, the policy allows full access to variables at all
+paths in the `dev` namespace that are prefixed with `project/`, including child
+paths, but only read access to paths prefixed with `system/`. Note that the wildcard
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with `system/` but not a path named `system` (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of variables at this path.                                                         |
+| destroy    | Delete variables at this path.                                                                                        |
+
+## Task access to variables
+
+Tasks can access variables with the [`template`] block or using the [Task API].
+The [workload identity] for each task grants it automatic read and list access to
+variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+## Locks
+
+Nomad provides the ability to block a variable from being updated for a period
+of time by setting a lock on it. Once a variable is locked, it can be read by
+everyone, but it can only be updated by the lock holder.
+
+The locks are designed to provide granular locking and are heavily inspired by
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems][].
+
+A lock is composed of an ID, a TTL, and a lock delay. The ID is generated by
+the Nomad Server and must be provided on every request to modify the variable's
+items or the lock itself. The TTL defines the time the lock will be held; if the
+lock needs to be in place for longer, it can be renewed for as many new periods
+as wanted.
+
+Once it is no longer needed, it must be released. If by the time the TTL expires,
+and no renew or release calls were made, the variable will remain locked for at
+least the lock delay duration, to avoid a possible split-brain situation, where
+there are two holders at the same time.
+
+### Leader election backed by Nomad variable locks
+
+For some applications, like HDFS or the Nomad Autoscaler, it is necessary to
+have multiple instances running to ensure redundancy in case of a failure, but
+only one of them may be active at a time as a leader.
+
+As part of the [Go Package][], Nomad offers a helper that takes one variable and
+uses a lock over it as a sync mechanism to run multiple instances but always
+keeping just one running at any given time, using the following algorithm:
+
+[![Leader Election Helper](/img/nomad-vars-leader-election-sdk.png)](/img/nomad-vars-leader-election-sdk.png)
+
+As soon as any instance starts, it tries to lock the sync variable. If it succeeds,
+it continues to execute while a secondary thread is in charge of keeping track of
+the lock and renewing it when necessary. If by any chance the renewal fails,
+the main process is forced to return, and the instance goes into standby until it
+attempts to acquire the lock over the sync variable.
+
+Only threads 1 and 3 or thread 2 are running at any given time, because every
+instance is either executing as normal while renewing the lock or waiting for a
+chance to acquire it and run.
+
+When the main process, or protected function, returns, the helper releases the
+lock, allowing a second instance to start running.
+
+To see it implemented live, look for the [`nomad var lock`][] command
+implementation or the [Nomad Autoscaler][] High Availability implementation.
+
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/manage/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems]: https://research.google/pubs/pub27897/
+[`nomad var lock`]: /nomad/commands/var
+[Go Package]: https://pkg.go.dev/github.com/hashicorp/nomad/api
+[implementation]: https://github.com/hashicorp/nomad/blob/release/1.7.0/command/var_lock.go#L240
+[Nomad Autoscaler]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.4.0/command/agent.go#L392
+[Task API]: /nomad/api-docs/task-api
diff --git a/content/nomad/v1.10.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.10.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..63e2ab3556
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Nomad's workload identity feature isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+---
+
+# Workload Identity
+
+This page provides conceptual information about Nomad's workload identity
+feature, which isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+
+Every workload running in Nomad is given a default identity. When an
+[allocation][] is accepted by the [plan applier][], the leader generates a
+Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring.
+Additional workload identities may be defined in tasks and services using the
+[`identity`][identity-block] block.
+
+## Workload Identity Claims
+
+Nomad workload identity for tasks include the following identity claims.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+Workload identities for Consul services have a claim with the service name
+instead of the task name.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Workload identities for tasks that use Vault have an additional claim for
+[`vault.role`][jobspec_vault_role] if a role is specified in the job.
+
+-> **Note:** This claim will *not* be added if the role is inherited from
+the [agent configuration][vault_role_agent_config] and is not present
+in the Nomad job specification.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_role": "nomad-jwt-login"
+}
+```
+
+### Nomad Enterprise <EnterpriseAlert inline />
+
+In Nomad Enterprise, tasks and services with a [`consul`][jobspec_consul] block
+that defines a [`namespace`][jobspec_consul_ns] value, or inside a `group`
+block that does it, have an additional claim called `consul_namespace`.
+
+```json
+{
+  "consul_namespace": "prod",
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Similarly, tasks with a [`vault.namespace`][jobspec_vault_ns] value have the additional claim
+`vault_namespace`.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_namespace": "prod"
+}
+```
+
+## Workload Identity for Nomad
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+### Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+### Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+You can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all jobs in the namespace by omitting the
+`-job`, `-group`, and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default redis-policy ./policy.hcl
+```
+
+### Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identity for Consul and Vault
+
+Consul and Vault can be configured to accept workload identities from Nomad for
+authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
+integration pages for more information.
+
+[allocation]: /nomad/docs/glossary#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[jobspec_consul]: /nomad/docs/job-specification/consul
+[jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace
+[jobspec_vault_ns]: /nomad/docs/job-specification/vault#namespace
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[vault_role_agent_config]: /nomad/docs/configuration/vault#create_from_role
+[plan applier]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[taskapi]: /nomad/api-docs/task-api
+[consul_int]: /nomad/docs/secure/acl/consul
+[vault_int]: /nomad/docs/secure/vault
diff --git a/content/nomad/v1.10.x/content/docs/configuration/acl.mdx b/content/nomad/v1.10.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..146a44c57b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block in Agent Configuration
+description: >-
+   Configure Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration. Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+---
+
+# acl Block in Agent Configuration
+
+<Placement groups={['acl']} />
+
+This page provides reference information for configuring Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration.  Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+
+Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/docs/secure/acl
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.10.x/content/docs/configuration/audit.mdx b/content/nomad/v1.10.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..418d5ee8f3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,302 @@
+---
+layout: docs
+page_title: audit Block in Agent Configuration
+description: >-
+  Configure audit logging behavior in the `audit` block of a Nomad agent configuration. Enable audit logs, define a sink to stream audit logs to, and change filter rules to exclude events from the audit log. Review example audit logs.
+---
+
+# `audit` Block in Agent Configuration
+
+<Placement groups={['audit']} />
+
+This page provides reference information for configuring audit logging behavior
+in the `audit` block of a Nomad agent configuration. Enable audit logs, define a
+sink to stream audit logs to, and change filter rules to exclude events from the
+audit log.
+
+<EnterpriseAlert product="nomad"/>
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Example audit logs
+
+The following audit log entries are for a request made to `/v1/job/web/summary`.
+The first entry is for the `OperationReceived` stage. The second entry is for
+the `OperationComplete` stage and includes the contents of the
+`OperationReceived` stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.10.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.10.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..18a90d3e12
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: autopilot Block in Agent Configuration
+description: >-
+  Configure settings for Nomad Autopilot features in the `autopilot` block of a Nomad agent configuration. Enable dead server cleanup, redundancy zones, and custom upgrades. Disable upgrade migration. Tune Raft settings for stable server introduction.
+---
+
+# `autopilot` Block in Agent Configuration
+
+<Placement groups={['autopilot']} />
+
+This page provides reference information for configuring settings for Nomad
+Autopilot features in the `autopilot` block of a Nomad agent configuration.
+Enable dead server cleanup, redundancy zones, and custom upgrades. Disable
+upgrade migration. Tune Raft settings for stable server introduction.
+
+Refer to the [Autopilot Guide](/nomad/docs/manage/autopilot) for
+how to configure and use Autopilot.
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - <EnterpriseAlert inline/> Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - <EnterpriseAlert inline/> Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version)
+  parameter.
diff --git a/content/nomad/v1.10.x/content/docs/configuration/client.mdx b/content/nomad/v1.10.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..0097d0b9dc
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/client.mdx
@@ -0,0 +1,854 @@
+---
+layout: docs
+page_title: client Block in Agent Configuration
+description: |-
+  Configure a Nomad client in the `client` block of a Nomad agent configuration. Enable a client, configure allocation directories, artifact and template behavior, networking, node pools, servers to join, garbage collection, workload behavior, client resources, chroot, host volumes, host network, and driver-specific behavior.
+---
+
+# `client` Block in Agent Configuration
+
+<Placement groups={['client']} />
+
+This page provides reference information for configuring a Nomad client in the
+`client` block of a Nomad agent configuration. Enable a client, configure
+allocation directories, artifact and template behavior, networking, node pools,
+servers to join, garbage collection, workload behavior, client resources,
+chroot, host volumes, host network, and driver-specific behavior.
+
+Refer to the [Set Server and Client Nodes](/nomad/docs/deploy/nomad-agent)
+and [Nomad Agent](/nomad/commands/agent) pages to learn about the Nomad
+agent process and how to configure the server and client nodes in your cluster.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `alloc_mounts_dir` `(string: "")` - Specifies the directory to use for binding
+  mounts for the [unveil file isolation mode][unveil]. When this parameter is
+  empty, Nomad generates the path as a sibling of the [top-level
+  `data_dir`][top_level_data_dir], with the name `alloc_mounts`. For example, if
+  the `data_dir` is `/opt/nomad/data`, then the alloc mounts directory is
+  `/opt/nomad/alloc_mounts`. This must be an absolute path and should not be
+  inside the Nomad data directory. Nomad creates the directory on the host,
+  if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `preferred_address_family` `(string: "")` - Specifies the preferred address family
+  for the network interface. The value can be `ipv4` or `ipv6`. If the selected network
+  interface has both IPv4 and IPv6 addresses, this option will select an IP address of
+  the preferred family. When the option is not specified, the current behavior is conserved:
+  the first IP address is selected no matter the family.
+
+- `cpu_disable_dmidecode` `(bool: false)` - Specifies the client should not use dmidecode
+  as a method of cpu detection. Nomad ignores this field on all platforms except Linux.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_max_allocs` `(int: 0)` - Specifies the maximum number of allocations
+  that may be scheduled on a client node and is not enforced if unset. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations. Note
+  that Nomad immediately garbage collects terminal allocations if garbage
+  collected on the server.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations. Note
+  that Nomad immediately garbage collects terminal allocations if garbage
+  collected on the server.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd. Note that Nomad immediately garbage collects terminal
+  allocations if garbage collected on the server.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `gc_volumes_on_node_gc` `(bool: false)` - Specifies that the server should
+  delete any dynamic host volumes on this node when the node is garbage
+  collected. You should only set this to `true` if you know that garbage
+  collected nodes will never rejoin the cluster, such as with ephemeral cloud
+  hosts.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_subnet_ipv6` `(string: "")` - Enables IPv6 on Nomad's bridge
+  network by specifying the subnet which the client will use to allocate IPv6
+  addresses.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints. When hairpin mode
+  is enabled, allocations are able to reach their own IP and **all ports** bound
+  to it. Changing this value requires a reboot of the client host to take
+  effect.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_volumes_dir` `(string: "")` - Specifies the directory wherein
+  host volume plugins should place volumes. When this parameter is empty, Nomad
+  generates the path using the [top-level `data_dir`][top_level_data_dir]
+  suffixed with `host_volumes`, like `"/opt/nomad/host_volumes"`.
+  This must be an absolute path.
+
+- `host_volume_plugin_dir` `(string: "")` - Specifies the directory to find host
+  volume plugins. When this parameter is empty, Nomad generates the path
+  using the [top-level `data_dir`][top_level_data_dir] suffixed with
+  `host_volume_plugins`, like `"/opt/nomad/host_volume_plugins"`. This must be
+  an absolute path.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+- `users` <code>([Users](#users-block): nil)</code> - Specifies options
+  concerning Nomad client's use of operating system users.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/job-declare/task-driver/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/deploy/task-driver/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver,
+refer to the [drivers documentation](/nomad/docs/job-declare/task-driver).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers. If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers. If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of environment variable keys not to pass to these tasks.
+  Nomad passes the host environment variables to `exec`, `raw_exec` and `java`
+  tasks. If specified, the defaults are overridden. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  CONSUL_HTTP_TOKEN_FILE
+  NOMAD_TOKEN
+  VAULT_TOKEN
+  CONSUL_LICENSE
+  NOMAD_LICENSE
+  VAULT_LICENSE
+  CONSUL_LICENSE_PATH
+  NOMAD_LICENSE_PATH
+  VAULT_LICENSE_PATH
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  AWS_METADATA_URL
+  GOOGLE_APPLICATION_CREDENTIALS
+  GOOGLE_OAUTH_ACCESS_TOKEN
+  ```
+
+- `"user.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated denylist of usernames for which a task is not allowed to run.
+  This only applies if the driver is included in `"user.checked_drivers"`. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of drivers for which to enforce the `"user.denylist"`.
+  For drivers using containers, this enforcement is usually unnecessary. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled. A common use-case for the fingerprint denylist is to disable
+  fingerprinters of irrelevant cloud environments, which can slow down client
+  agent startup time.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "env_aws,env_gce,env_azure,env_digitalocean"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(string: "")` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separating the two inclusive ends. Refer to
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_artifact_inspection` `(bool: false)` - Specifies whether to disable
+  artifact inspection for sandbox escapes. If the platform supports filesystem
+  isolation, and it is not disabled, artifact inspection will not be performed
+  regardless of this value.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `filesystem_isolation_extra_paths` `([]string: nil)` - Allow extra paths
+  in the filesystem isolation. Paths are specified in the form `[kind]:[mode]:[path]`
+  where `kind` must be either `f` or `d` (file or directory) and
+  `mode` must be zero or more of `r`, `w`, `c`, `x` (read, write, create, execute) e.g.
+  `f:r:/dev/urandom` would enable reading the /dev/urandom file,
+  `d:rx:/opt/bin` would enable reading and executing from the /opt/bin directory
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "executeTemplate",
+  "writeToFile"])` - Specifies a list of template rendering functions that
+  should be disallowed in job specs.  By default the `plugin`, `executeTemplate`
+  and `writeToFile` functions are disallowed as they allow unrestricted root
+  access to the host or allow recursive execution.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. Setting
+  both `min` and `max` to `0` disables the feature. This configuration is also exposed
+  in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs. You can also
+configure [dynamic host volumes][] via the [`volume create`][] or [`volume
+register`][] commands.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type
+[`volume`](/nomad/docs/job-specification/volume) and ACLs. A host volume in the
+configuration cannot have the same name as a dynamic host volume on the same node.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path      = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr           = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+### `users` Block
+
+The `users` block controls aspects of Nomad client's use of operating system
+users.
+
+```hcl
+client {
+  users {
+    dynamic_user_min = 80000
+    dynamic_user_max = 89999
+  }
+}
+```
+
+- `dynamic_user_min` `(int: 80000)` - The lowest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+- `dynamic_user_max` `(int: 89999)` - The highest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values in the example are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task directories'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[unveil]: /nomad/plugins/author/task-driver#fsisolation-unveil
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
diff --git a/content/nomad/v1.10.x/content/docs/configuration/consul.mdx b/content/nomad/v1.10.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..8e76cf8e09
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,447 @@
+---
+layout: docs
+page_title: consul Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with Consul in the `consul` block of a Nomad agent configuration for service discovery and key-value integration. Configure cluster name, the Consul namespace, whether Nomad should advertize its services, certificates, tokens, security, health checks, auto join, and workload service and task identity.
+---
+
+# `consul` Block in Agent Configuration
+
+<Placement groups={['consul']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [Consul][consul] in the `consul` block of a Nomad agent
+configuration for service discovery and key-value integration. Configure cluster
+name, the Consul namespace, whether Nomad should advertize its services,
+certificates, tokens, security, health checks, auto join, and workload service
+and task identity.
+
+When configured, tasks can register themselves with Consul, and the Nomad
+cluster can [automatically bootstrap][bootstrap] itself.
+
+Refer to the [Service Discovery on Nomad
+tutorial](/nomad/tutorials/service-discovery) for how to use Consul's service
+discovery.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+In Nomad Enterprise, you may specify multiple `consul` blocks to configure
+access to multiple Consul clusters. Each Consul cluster must have a different
+value for the [`name`](#name) field.
+
+## `consul` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`consul.cluster`][] or [`service.cluster`][] fields. In Nomad
+  Community Edition, only the `"default"` cluster will be used, so this field
+  should be omitted.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the [Consul
+  namespace](/consul/docs/enterprise/namespaces) used by the Consul
+  integration. If non-empty, this namespace will be used on all Consul API calls
+  and for Consul service mesh configurations, unless overridden by the job's
+  [`consul.namespace`][] field. In Nomad Community Edition, only the `"default"`
+  namespace is used, so you should omit this field.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and client services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it defaults to Consul's anonymous policy,
+  which may or may not allow writes. Defaults to the `CONSUL_HTTP_TOKEN`
+  environment variable if set. Nomad cannot refresh this token; if the token is
+  deleted, Nomad is not able to communicate with Consul.
+
+  In Nomad Enterprise, if the Consul agent running alongside Nomad is in a
+  Consul Enterprise admin partition, you must create the Consul token provided
+  to the Nomad client in the same partition.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`][] set to `true`.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover Nomad servers in the same region by searching for the
+  Consul service name defined in the `server_service_name` option. The search
+  occurs if the client is not registered with any Nomad servers or it is unable
+  to heartbeat to the leader of the region, in which case it may be partitioned
+  and searches for other Nomad servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `client_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check is critical.
+
+- `client_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check shows a warning.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+  certificate used for communication between Connect sidecar proxies and Consul
+  agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+  <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. Refer to
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not
+  include the values for the ACL `token` or `auth`. This option should be
+  disabled in environments where Consul ACLs are not enabled.
+
+- `service_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for services.
+
+- `task_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for tasks.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `server_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check is critical.
+
+- `server_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check shows a warning.
+
+- `service_identity` <code>([Identity](#service_identity-parameters): nil)</code> - Specifies
+  a default Workload Identity to use when obtaining Service Identity tokens from
+  Consul to register services. Refer to [Workload Identity](#workload-identity)
+  for a recommended configuration.
+
+- `task_identity` <code>([Identity](#task_identity-parameters): nil)</code> - Specifies a
+  default Workload Identity to use when obtaining Consul tokens from Consul to
+  support [`template`][] blocks. Refer to [Workload
+  Identity](#workload-identity) for a recommended configuration.
+
+## Workload Identity
+
+The `service_identity` and `task_identity` blocks accept all the same values as
+the job specification's [`identity`][identity_block] (except that the
+`service_identity` ignores the `env` and `file` fields). By ensuring these
+blocks are set on the Nomad servers, you can automatically migrate your existing
+jobs to use Workload Identity without modifying the job specification and
+resubmitting them.
+
+The recommended configuration for `service_identity` and `task_identity` is as
+follows. Refer to [Migrating to Using Workload Identity with Consul][] for
+details on how to configure Consul to accept these identities. Note that the
+`ttl` field here refers to the TTL of the Nomad identity and not the Consul
+token.
+
+```hcl
+consul {
+  service_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+
+  task_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+}
+```
+
+### `service_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### `task_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN_consul_default` (or `NOMAD_TOKEN_consul_<name>` depending
+  on the [`name`](#name) field) environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_consul_default.jwt` (or
+  `secrets/nomad_consul_<name>.jwt` depending on the [`name`](#name) field). If
+  the [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul ACL policy for Nomad
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+### Consul Namespace <EnterpriseAlert inline/>
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace.
+
+This Consul policy shows an example policy configuration for a Nomad server.
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+### Consul Admin Partition <EnterpriseAlert inline/>
+
+In Nomad Enterprise, if the Consul agent running alongside Nomad is in a Consul
+Enterprise admin partition, you must create the Consul ACL token and ACL policy
+for Nomad clients in the same partition.
+
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/docs/deploy/clusters/connect-nodes 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`service.cluster`]: /nomad/docs/job-specification/service#cluster
+[identity_block]: /nomad/docs/job-specification/identity
+[`template`]: /nomad/docs/job-specification/template
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/v1.8.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[auth-method]: /consul/docs/security/acl/auth-methods/jwt
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[consul_bound_aud]: /consul/docs/security/acl/auth-methods/jwt#boundaudiences
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[consul_config_entry]: /consul/docs/connect/config-entries
diff --git a/content/nomad/v1.10.x/content/docs/configuration/index.mdx b/content/nomad/v1.10.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..5842eb6f73
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/index.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: Nomad Agent Configuration
+description: This section contains reference information for configuring Nomad agents. Learn how Nomad loads and merges multiple configuration files. Configure networking and advertise addresses, Nomad regions and datacenters, data directories, Consul integration, handshake limits, connections per client, logging, plugins, Sentinel policies, security, update check behavior, and Vault integration. Enable debugging, write to syslog, leave on interrupt or terminate, and cross-origin resource sharing (CORS).
+---
+
+# Nomad Agent Configuration
+
+This page provides an overview of reference information for configuring Nomad
+agents. Learn how Nomad loads and merges multiple configuration files. Configure
+networking and advertise addresses, Nomad regions and data centers, data
+directories, Consul integration, handshake limits, connections per client,
+logging, plugins, Sentinel policies, security, update check behavior, and Vault
+integration. Enable debugging, writing to syslog, leave on interrupt or
+terminate, and cross-origin resource sharing (CORS).
+
+Write configuration files in [HCL][hcl] or specify parameters as command-line
+flags. Nomad can read and combine parameters from multiple configuration files
+or directories to configure the Nomad agent.
+
+## Configuration File Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: refer to explanation)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  refer to the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: refer to explanation)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `eventlog` - This is a nested object that configures the behavior with
+  with Windows Event Log. The following parameters are available:
+
+  - `enabled` - Enable sending Nomad agent logs to the Windows Event Log.
+
+  - `level` -  `(string: "ERROR")` - Specifies the verbosity of logs the Nomad
+    agent outputs. Valid log levels include `ERROR`, `WARN`, or `INFO` in
+    increasing order of verbosity. Level must be of equal or less verbosity as
+    defined for the [`log_level`](#log_level) parameter.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - This is a nested object that configures limits that are enforced by
+   the agent. The following parameters are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: refer to explanation)` - Specifies the network ports used for
+  different services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `rpc` `(`[`RPC`]`: nil)` - Specifies configuration which is specific to RPC.
+	We strongly recommend that you do not configure RPC values. Use the default
+	values, which have been production-proven on clusters of thousands of nodes.
+	You should only configure the `rpc` block if you have a specific reason to
+	believe it will improve your particular use case.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(refer to [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`rpc`]: /nomad/docs/configuration/rpc
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.10.x/content/docs/configuration/keyring/awskms.mdx b/content/nomad/v1.10.x/content/docs/configuration/keyring/awskms.mdx
new file mode 100644
index 0000000000..70bfa1cd6b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/keyring/awskms.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: AWS Key Management Service (KMS) Keyring Configuration
+description: |-
+  Configure an AWS Key Management Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS authentication. Learn how Nomad supports KMS root key rotation.
+---
+
+# AWS Key Management Service (KMS) Keyring Configuration
+
+This page provides reference information for configuring an AWS Key Management
+Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent
+configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS
+authentication. Learn how Nomad supports KMS root key rotation.
+
+The AWS KMS keyring configures Nomad to use AWS KMS to wrap its keyring. This
+example shows configuring an AWS KMS keyring through the Nomad configuration
+file by providing all the required values.
+
+```hcl
+keyring "awskms" {
+  active = true
+  name   = "example"
+
+  # fields specific to awskms
+  region     = "us-east-1"
+  access_key = "AKIAIOSFODNN7EXAMPLE"
+  secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  kms_key_id = "19ec80b0-dfdd-4d97-8164-c6examplekey"
+  endpoint   = "https://vpce-0e1bb1852241f8cc6-pzi0do8n.kms.us-east-1.vpce.amazonaws.com"
+}
+```
+
+## `awskms` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `region` `(string: "us-east-1")`: The AWS region where the encryption key
+  lives. If not provided, may be populated from the `AWS_REGION` or
+  `AWS_DEFAULT_REGION` environment variables, from your `~/.aws/config` file, or
+  from instance metadata.
+
+- `access_key` `(string: <required>)`: The AWS access key ID to use. Alternately
+  specify via the `AWS_ACCESS_KEY_ID` environment variable or as part of the AWS
+  profile from the AWS CLI or instance profile.
+
+- `session_token` `(string: "")`: Specifies the AWS session token. Alternately
+  specify via the environment variable `AWS_SESSION_TOKEN`.
+
+- `secret_key` `(string: <required>)`: The AWS secret access key to
+  use. Alternately specify via the `AWS_SECRET_ACCESS_KEY` environment variable
+  or as part of the AWS profile from the AWS CLI or instance profile.
+
+- `kms_key_id` `(string: <required>)`: The AWS KMS key ID or ARN to use for
+  encryption and decryption. You can alternately use an alias in the format
+  `alias/key-alias-name`.
+
+- `endpoint` `(string: "")`: The KMS API endpoint for AWS KMS
+  requests. Alternately specify via the `AWS_KMS_ENDPOINT` environment
+  variable. This is useful, for example, when connecting to KMS over a [VPC
+  Endpoint][]. If not set, Nomad uses the default API endpoint for your region.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file allows you to pass in
+`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as part of the keyring block's
+parameters, we strongly recommended that you set these values via environment
+variables or instance profile.
+
+AWS authentication values:
+
+- `AWS_REGION` or `AWS_DEFAULT_REGION`
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
+
+Note: The client uses the official AWS SDK and the specified credentials,
+environment credentials, shared file credentials, or IAM role/ECS task
+credentials in that order, if you do not provide the aforementioned AWS-specific
+values. Refer to the [AWS SDK and Tools standard credentials][aws-std-creds]
+documentation.
+
+Nomad needs the following permissions on the KMS key:
+
+- `kms:Encrypt`
+- `kms:Decrypt`
+- `kms:DescribeKey`
+
+Grant these via IAM permissions on the principal that Nomad uses, on the KMS key
+policy for the KMS key, or via KMS Grants on the key.
+
+## Key rotation
+
+This keyring supports rotating the root keys defined in AWS KMS
+[doc][rotate_docs]. Both automatic rotation and manual rotation is supported for
+KMS since the key information is stored with the encrypted data. Old keys must
+not be disabled or deleted and are used to decrypt older data. Any new or
+updated data is encrypted with the current key defined in the keyring
+configuration or set to current under a key alias.
+
+[VPC Endpoint]: https://docs.aws.amazon.com/kms/latest/developerguide/kms-vpc-endpoint.html
+[rotate_docs]: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html
+[aws-std-creds]: https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html
diff --git a/content/nomad/v1.10.x/content/docs/configuration/keyring/azurekeyvault.mdx b/content/nomad/v1.10.x/content/docs/configuration/keyring/azurekeyvault.mdx
new file mode 100644
index 0000000000..7819d1e196
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/keyring/azurekeyvault.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Azure Key Vault Keyring Configuration
+description: >-
+  Configure an Azure Key Vault keyring in the `keyring "azurekeyvault"` block of a Nomad agent configuration. Configure the Key Vault resource's DNS, Azure Cloud environment variables and API endpoints, and vault and key names. Learn how Nomad supports rotating keys defined in Azure Key Vault.
+---
+
+# Azure Key Vault Keyring Configuration
+
+This page provides reference information for configuring an Azure Key Vault
+keyring in the `keyring "azurekeyvault"` block of a Nomad agent
+configuration. Configure the Key Vault resource's DNS, Azure Cloud environment
+API endpoints, vault and key names, tenant and client IDs, and the client secret. Learn how Nomad supports rotating keys defined in Azure Key
+Vault.
+
+The Azure Key Vault keyring configures Nomad to use Azure Key Vault to wrap its
+keyring. This example shows configuring Azure Key Vault keyring through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "azurekeyvault" {
+  active = true
+  name   = "example"
+
+  # fields specific to azurekeyvault
+  tenant_id      = "46646709-b63e-4747-be42-516edeaf1e14"
+  client_id      = "03dc33fc-16d9-4b77-8152-3ec568f8af6e"
+  client_secret  = "DUJDS3..."
+  vault_name     = "nomad"
+  key_name       = "nomad_key"
+}
+```
+
+## `azurekeyvault` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `tenant_id` `(string: <required>)`: The tenant id for the Azure Active
+  Directory organization. Alternately specify via the `AZURE_TENANT_ID`
+  environment variable.
+
+- `client_id` `(string: <required or MSI>)`: The client id for credentials to
+  query the Azure APIs. Alternately specify via the `AZURE_CLIENT_ID`
+  environment variable.
+
+- `client_secret` `(string: <required or MSI>)`: The client secret for
+  credentials to query the Azure APIs. Alternately specify via the
+  `AZURE_CLIENT_SECRET` environment variable.
+
+- `environment` `(string: "AZUREPUBLICCLOUD")`: The Azure Cloud environment API
+  endpoints to use. Alternately specify via the `AZURE_ENVIRONMENT` environment
+  variable.
+
+- `vault_name` `(string: <required>)`: The Key Vault vault to use the encryption
+  keys for encryption and decryption.
+
+- `key_name` `(string: <required>)`: The Key Vault key to use for encryption and
+  decryption.
+
+- `resource` `(string: "vault.azure.net")`: The Key Vault resource's DNS
+  Suffix to connect to. Alternately specify via the `AZURE_AD_RESOURCE`
+  environment variable. Needs to be changed to connect to Azure's Managed HSM
+  KeyVault instance type.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+Azure authentication values:
+
+- `AZURE_TENANT_ID`
+- `AZURE_CLIENT_ID`
+- `AZURE_CLIENT_SECRET`
+- `AZURE_ENVIRONMENT`
+- `AZURE_AD_RESOURCE`
+
+~> **Note:** If Nomad is hosted on Azure, Nomad can use Managed Service
+Identities (MSI) to access Azure instead of an environment and shared client id
+and secret. MSI must be [enabled][msi_enabled] on the VMs hosting Nomad. We
+recommend this configuration since MSI prevents your Azure credentials from
+being stored as clear text.
+
+-> **Note:** If you are using a Managed HSM KeyVault, you must specify
+`AZURE_AD_RESOURCE` or the `resource` configuration parameter; usually this
+should point to `managedhsm.azure.net` but could point to other suffixes
+depending on Azure environment.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Azure Key Vault. Key metadata is
+stored with the encrypted data to ensure the correct key is used during
+decryption operations. Set up Azure Key Vault with [key rotation][] using Azure
+Automation Account so Vault recognizes newly rotated keys.
+
+[msi_enabled]: https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm
+[key rotation]: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-key-rotation-log-monitoring
diff --git a/content/nomad/v1.10.x/content/docs/configuration/keyring/gcpckms.mdx b/content/nomad/v1.10.x/content/docs/configuration/keyring/gcpckms.mdx
new file mode 100644
index 0000000000..00ad5ff915
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/keyring/gcpckms.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: Google Cloud Platform Key Management Service Keyring Configuration
+description: >-
+  Configure a Google Cloud Platform Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block of a Nomad agent configuration. Configure GCP credentials, project, region, key ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP Cloud KMS.
+---
+
+# Google Cloud Platform Key Management Service Keyring Configuration
+
+This page provides reference information for configuring a Google Cloud Platform
+Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block
+of a Nomad agent configuration. Configure GCP credentials, project, region, key
+ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP
+Cloud KMS.
+
+The GCP Cloud KMS keyring configures Nomad to use GCP Cloud KMS to wrap its
+keyring. This example shows configuring GCP Cloud KMS keyring through the Nomad
+configuration file by providing all the required values.
+
+```hcl
+keyring "gcpckms" {
+  active = true
+  name   = "example"
+
+  credentials = "/etc/nomad.d/nomad-user-creds.json"
+  project     = "nomad-project"
+  region      = "global"
+  key_ring    = "nomad-keyring"
+  crypto_key  = "nomad-key"
+}
+```
+
+## `gcpckms` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `credentials` `(string: <required>)`: The path to the credentials JSON file to
+  use. Alternately specify via the `GOOGLE_CREDENTIALS` or
+  `GOOGLE_APPLICATION_CREDENTIALS` environment variable or set automatically if
+  running under Google Compute Engine.
+
+- `project` `(string: <required>)`: The GCP project ID to use. Alternately
+  specify via the `GOOGLE_PROJECT` environment variable.
+
+- `region` `(string: <required>)`: The GCP region/location where the key ring
+  lives. Alternately specify via the `GOOGLE_REGION` environment variable.
+
+- `key_ring` `(string: <required>)`: The GCP KMS key ring to use.
+
+- `crypto_key` `(string: <required>)`: The GCP KMS crypto key to use for
+  encryption and decryption.
+
+## Authentication &amp; permissions
+
+You must provide authentication-related values either as environment
+variables or as configuration parameters.
+
+GCP authentication values:
+
+- `GOOGLE_CREDENTIALS` or `GOOGLE_APPLICATION_CREDENTIALS`
+- `GOOGLE_PROJECT`
+- `GOOGLE_REGION`
+
+Note: The client uses the official Google SDK and the specified credentials,
+environment credentials, or [application default credentials][] in that order,
+if you do not provide the aforementioned GCP-specific values.
+
+The service account needs the following minimum permissions on the crypto key:
+
+```text
+cloudkms.cryptoKeyVersions.useToEncrypt
+cloudkms.cryptoKeyVersions.useToDecrypt
+cloudkms.cryptoKeys.get
+```
+
+These permissions can be described with the following role:
+
+```text
+roles/cloudkms.cryptoKeyEncrypterDecrypter
+cloudkms.cryptoKeys.get
+```
+
+Use `cloudkms.cryptoKeys.get` permission for retrieving metadata information of
+keys from CloudKMS within this engine initialization process.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Google Cloud KMS
+[doc][rotating_keys]. Both scheduled rotation and manual rotation is supported
+for CKMS since the key information. Old keys version must not be disabled or
+deleted and are used to decrypt older data. Any new or updated data is encrypted
+with the primary key version.
+
+
+[application default credentials]: https://developers.google.com/identity/protocols/application-default-credentials
+[rotating_keys]: https://cloud.google.com/kms/docs/rotating-keys
diff --git a/content/nomad/v1.10.x/content/docs/configuration/keyring/index.mdx b/content/nomad/v1.10.x/content/docs/configuration/keyring/index.mdx
new file mode 100644
index 0000000000..a708548cd5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/keyring/index.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: keyring Block in Agent Configuration
+description: >-
+  Configure keyring protection behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring and configure a name. Learn how to configure keyring high availability (HA) and migrate keyrings.
+---
+
+# `keyring` Block in Agent Configuration
+
+<Placement groups={['keyring']} />
+
+This page provides reference information for configuring keyring protection
+behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring
+and configure a name. Learn how to configure keyring high availability (HA) and
+migrate keyrings.
+
+The `keyring` block configures how the Nomad server protects the keyring used
+for encrypting [variables][] and signing [workload identities][]. By default,
+Nomad encrypts the key material with a unique key encryption key (KEK) that is
+not shared between servers, and writes the wrapped key material to disk as
+described in [Key Management][]. Nomad refers to this as `"aead"` (authenticated
+encryption with associated data). Using the `keyring` configuration block, Nomad
+servers can instead use an external key management system (KMS) or Vault transit
+encryption. The encrypted key is stored on disk but is now protected against
+offline attacks because the KEK is not present in the file.
+
+All `keyring` blocks require a label for the KMS type. Each external KMS has its
+own configuration options. The `keyring` block only applies to Nomad servers,
+not Nomad clients.
+
+```hcl
+keyring [TYPE] {
+  name   = "example"
+  active = true
+}
+```
+
+The default `keyring` configuration is as follows:
+
+```hcl
+keyring "aead" {
+  active = true
+}
+```
+
+## `keyring` Parameters
+
+All `keyring` blocks support the following parameters.
+
+- `name` `(string: "")` - A unique identifier for the `keyring` block, used to
+  disambiguate when there are multiple blocks of the same type.
+
+- `active` `(bool: false)` - Indicates which block to use for encrypting
+  keys. For existing servers, changing which block is `active` only impacts new
+  keys created by a [key rotation][]. Existing keys are encrypted with the
+  previous `active` block, so those blocks should not be removed from the
+  configuration until they have been garbage collected and the keys have been
+  removed from the keystore. In Nomad Community Edition, only a single keyring
+  can be `active` at a time.
+
+## Migrating Keyrings
+
+To migrate to a new keyring, add the new `keyring` block to the servers with
+`active=true`, and restart the servers. The server starts using the new keyring
+wrapper when the current key is rotated either periodically or via the [`nomad
+operator root keyring rotate`][keyring_rotate_cmd] command.
+
+Adding or removing a keyring requires restarting the Nomad server. You should
+not remove a keyring until all keys it wraps have been garbage collected. You
+can examine the contents of the `keystore` directory found in the Nomad server's
+data directory and compare this against the output of [`nomad operator root
+keyring list`][keyring_list_cmd].
+
+## High Availability
+
+<EnterpriseAlert product="nomad"/>
+
+Keyring high availability provides the means to configure multiple active
+`keyring` blocks, in order to have resilience against an outage of an external
+KMS. When there are multiple `keyring` blocks with `active = true`, Nomad
+Enterprise encrypts each key it creates in all the active KMS providers. On
+startup, Nomad tries each KMS provider in order until it finds a provider that
+can decrypt each key.
+
+In this example high availability configuration, both `keyring` blocks use the
+`"awskms"` provider, but each block uses a different KMS key in a different AWS
+region.
+
+```hcl
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-1"
+  region     = "us-east-1"
+  kms_key_id = "arn:aws:kms:us-east-1:000000000000:key/7d23633a-4464-11ef-a273-abd12example"
+}
+
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-2"
+  region     = "us-east-2"
+  kms_key_id = "alias/nomad-keyring-us-east-2"
+}
+```
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[Key Management]: /nomad/docs/manage/key-management
+[key rotation]: /nomad/docs/manage/key-management#key-rotation
+[keyring_rotate_cmd]: /nomad/commands/operator/root/keyring-rotate
+[keyring_list_cmd]: /nomad/commands/operator/root/keyring-list
diff --git a/content/nomad/v1.10.x/content/docs/configuration/keyring/transit.mdx b/content/nomad/v1.10.x/content/docs/configuration/keyring/transit.mdx
new file mode 100644
index 0000000000..544ee23f9d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/keyring/transit.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: Vault Transit Keyring Configuration
+description: |-
+  Configure a Vault transit secrets engine keyring in the `keyring "transit"` block of a Nomad agent configuration. Configure the address to the Vault cluster, key name, mount path, namespace, TLS authentication, and whether to disable Vault token automatic renewal. Learn how Nomad supports rotating keys defined in Vault's transit secrets engine.
+---
+
+# Vault Transit Keyring Configuration
+
+This page provides reference information for configuring a Vault transit secrets
+engine keyring in the `keyring "transit"` block of a Nomad agent configuration.
+Configure the address to the Vault cluster, key name, mount path, namespace, TLS
+authentication, and whether to disable Vault token automatic renewal. Learn how
+Nomad supports rotating keys defined in Vault's transit secrets engine.
+
+The Vault transit keyring configures Nomad to use Vault's transit secrets engine
+to wrap its keyring. This example shows configuring Vault transit through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "transit" {
+
+  active = true
+  name   = "example"
+
+  # fields specific to transit
+  address            = "https://vault:8200"
+  token              = "s.Qf1s5zigZ4OX6akYjQXJC1jY"
+  disable_renewal    = "false"
+
+  # Key configuration
+  key_name           = "transit_key_name"
+  mount_path         = "transit/"
+  namespace          = "ns1/"
+
+  # TLS Configuration
+  tls_ca_cert        = "/etc/vault/ca_cert.pem"
+  tls_client_cert    = "/etc/vault/client_cert.pem"
+  tls_client_key     = "/etc/vault/ca_cert.pem"
+  tls_server_name    = "vault"
+  tls_skip_verify    = "false"
+}
+```
+
+## `transit` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `key_name` `(string: <required>)`: The transit key to use for encryption and
+  decryption.
+
+- `key_id_prefix` `(string: "")`: An optional string to add to the key id of
+  values wrapped by this transit keyring. This can help disambiguate between two
+  transit keyring.
+
+- `mount_path` `(string: <required>)`: The mount path to the transit secret
+  engine.
+
+- `disable_renewal` `(string: "false")`: Disables the automatic renewal of the
+  token in case the lifecycle of the token is managed with some other mechanism
+  outside of Vault, such as Vault Agent.
+
+Set the following parameters in the `keyring` block. If not set here, Nomad uses
+the values set in the server's [`vault`][vault_config] block. You must set
+required fields either here or the `vault` block.
+
+- `address` `(string: <required>)`: The full address to the Vault cluster.
+  Alternately specify via the `VAULT_ADDR` environment variable.
+
+- `token` `(string: <required>)`: The Vault token to use. Alternately specify
+  via the `VAULT_TOKEN` environment variable.
+
+- `namespace` `(string: "")`: The namespace path to the transit secret engine.
+   Alternately specify via the `VAULT_NAMESPACE` environment variable.
+
+- `tls_ca_cert` `(string: "")`: Specifies the path to the CA certificate file
+  used for communication with the Vault server. Alternately specify via the
+  `VAULT_CACERT` environment variable.
+
+- `tls_client_cert` `(string: "")`: Specifies the path to the client certificate
+  for communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_CERT` environment variable.
+
+- `tls_client_key` `(string: "")`: Specifies the path to the private key for
+  communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_KEY` environment variable.
+
+- `tls_server_name` `(string: "")`: Name to use as the SNI host when connecting
+  to the Vault server via TLS. Alternately specify via the
+  `VAULT_TLS_SERVER_NAME` environment variable.
+
+- `tls_skip_verify` `(bool: "false")`: Disable verification of TLS certificates.
+  Using this option is highly discouraged and decreases the security of data
+  transmissions to and from the Vault server. Alternately specify via the
+  `VAULT_SKIP_VERIFY` environment variable.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file lets you to pass in `VAULT_TOKEN`
+as part of the keyring's parameters, we strongly recommended that you set these
+values via environment variables.
+
+The Vault authentication token needs the following permissions on the transit
+key:
+
+```hcl
+path "<mount path>/encrypt/<key name>" {
+  capabilities = ["update"]
+}
+
+path "<mount path>/decrypt/<key name>" {
+  capabilities = ["update"]
+}
+```
+
+Other considerations for the token used:
+* It should probably be an [orphan token][], otherwise when the parent token
+  expires or gets revoked the keyring breaks.
+* Consider making it a [periodic token][] and not setting an explicit max TTL,
+  otherwise at some point it ceases to be renewable.
+
+## Key rotation
+
+This keyring supports key rotation using Vault's transit secrets engine's key
+rotation endpoints. Refer to [Vault docs][rotate_doc] for details. Old keys must
+not be disabled or deleted and are used to decrypt older data.
+
+[orphan token]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens
+[periodic token]: /vault/docs/concepts/tokens#periodic-tokens
+[rotate_doc]: /vault/api-docs/secret/transit#rotate-key
+[vault_config]: https://developer.hashicorp.com/nomad/docs/configuration/vault
diff --git a/content/nomad/v1.10.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.10.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..d3d5d4d4a8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: plugin Block in Agent Configuration
+description: Configure task driver and device driver plugins in the `plugin` block of a Nomad agent configuration. Specify arguments to pass to the plugin. Configure values specific to the plugin.
+---
+
+# `plugin` Block in Agent Configuration
+
+<Placement groups={['plugin']} />
+
+This page provides reference information for configuring task driver and device
+driver plugins in the `plugin` block of a Nomad agent configuration. Specify
+arguments to pass to the plugin. Configure values specific to the plugin.
+
+Refer to the [Nomad plugins guide](/nomad/plugins) for details on specific task
+driver and device plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.10.x/content/docs/configuration/reporting.mdx b/content/nomad/v1.10.x/content/docs/configuration/reporting.mdx
new file mode 100644
index 0000000000..c09d679bd9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/reporting.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: reporting Block in Agent Configuration
+description: >-
+  Enable automated license utilization reporting in the `reporting` block of a Nomad agent configuration. Configuration applies to agents running Nomad Enterprise with server mode enabled.
+---
+
+# `reporting` Block in Agent Configuration
+
+<Placement groups={['reporting']} />
+
+This page provides reference information for enabling automated license
+utilization reporting in the `reporting` block of a Nomad agent configuration.
+
+<EnterpriseAlert/>
+
+Configuration applies to agents running with [server mode
+enabled][server_mode_enabled].
+
+Refer to the [Automated license utilization reporting
+guide][automated_license_utilization_reporting] for which ports to open and what
+data is shared.
+
+```hcl
+reporting {
+  license {
+    enabled = true
+  }
+
+  snapshot_retention_time = "9600h"
+}
+```
+
+## `reporting` Parameters
+
+- `license` <code>([license](#license-block): default)</code> - Configures
+  automated license utilization reporting.
+
+- `snapshot_retention_time` `(string: "9600h")` - Configures the maximum amount
+  of time that Nomad retains a utilization reporting snapshot in the Nomad
+  state store. You can export these snapshots with the [`nomad operator
+  utilization`][] command.
+
+- `disable_product_usage_reporting` `(bool: false)` - Specifies whether detailed
+  product usage metrics should be disabled. Review the
+  [full list of metrics](/nomad/docs/enterprise/license/utilization-reporting#full-list-of-metrics)
+  before disabling this option, and share any concerns you may have
+  with your account manager.
+
+## `license` Block
+
+- `enabled` `(bool: true)` - Specifies whether automated license utilization
+  reporting should be enabled and run. License utilization metrics are still
+  gathered for offline reporting.
+
+[server_mode_enabled]: /nomad/docs/configuration/server#enabled
+[automated_license_utilization_reporting]: /nomad/docs/enterprise/license/utilization-reporting
+[`nomad operator utilization`]: /nomad/commands/operator/utilization
diff --git a/content/nomad/v1.10.x/content/docs/configuration/rpc.mdx b/content/nomad/v1.10.x/content/docs/configuration/rpc.mdx
new file mode 100644
index 0000000000..e14204e857
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/rpc.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: rpc Block in Agent Configuration
+description: >-
+   Configure Nomad's RPC behavior in the `rpc` block of a Nomad agent configuration. Modify RPC session configuration, change stream accept backlog, keepalive interval, and open stream timeouts.
+---
+
+# rpc Block in Agent Configuration
+
+<Placement groups={['rpc']} />
+
+This page provides reference information for configuring Nomad's RPC behavior in
+the `rpc` block of a Nomad agent configuration. Modify RPC session
+configuration, stream accept backlog, keepalive interval, and open stream
+timeouts. We strongly recommend leaving these values unconfigured to use the
+default values, which have been production-proven on clusters of thousands of
+nodes. You should only configure the `rpc` block if you have specific reason to
+believe it will improve your specific use case.
+
+```hcl
+rpc {
+  accept_backlog           = 256
+  keep_alive_interval      = "30s"
+  connection_write_timeout = "10s"
+  max_stream_window_size   = 262144
+  stream_open_timeout      = "75s"
+  stream_close_timeout     = "5m"
+}
+```
+
+## `rpc` Parameters
+
+- `accept_backlog` `(int: 256)` - Limits how many RPC streams
+  (requests) can be waiting for acceptance by the RPC server.
+
+- `keep_alive_interval` `(string: 30s)` - How often to perform the keep alive
+
+- `connection_write_timeout` `(string: 10s)` - Safety valve timeout after which
+  you should suspect a problem with the underlying connection and close it. This
+  is only applied to writes, where there is generally an expectation that things
+  move along quickly.
+
+- `max_stream_window_size` `(int: 262144)` - Controls the maximum window size
+  allowed for a stream, in bytes.
+
+- `stream_open_timeout` `(string: 75s)` - Maximum amount of time that a stream
+  remains in pending state while waiting for an ACK from the peer. Once the
+  timeout is reached, Nomad gracefully closes the session. A zero value disables
+  the stream open timeout, allowing unbounded blocking on open stream calls.
+
+- `stream_close_timeout` `(string: 5m)` - When `close` is called, maximum time
+  that a stream is in a half-closed state before forcibly closing the
+  connection. Forcibly closed connections empty the receive buffer, drop any
+  future packets received for that stream, and send an RST to the remote side.
diff --git a/content/nomad/v1.10.x/content/docs/configuration/search.mdx b/content/nomad/v1.10.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..526e0d11c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/search.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: search Block in Agent Configuration
+sidebar_title: search
+description: >-
+  Configure the Nomad server search API in the `search` block of a Nomad agent configuration. Enable fuzzy searching. Configure the minimum size of the search term, the maximum number of Nomad objects to search through per context type, and the max number of matching results.
+---
+
+# `search` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+This page provides reference information for configuring the Nomad server search
+API in the `search` block of a Nomad agent configuration. Enable fuzzy
+searching. Configure the minimum size of the search term, the maximum number of
+Nomad objects to search through per context type, and the max number of matching results.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.10.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.10.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..a41b6ef14e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: sentinel Block in Agent Configuration
+description: >-
+  Configure Sentinel policy engine behavior in the "sentinel" block of a Nomad agent configuration. Configure the path to the plugin that Nomad uses to import Sentinel policies and specify arguments to pass to that plugin on startup.
+---
+
+# `sentinel` Block in Agent Configuration
+
+<Placement groups={['sentinel']} />
+
+This page provides reference information for configuring the Sentinel policy
+engine in the `sentinel` block of a Nomad agent configuration. Configure the
+path to the plugin that Nomad uses to import Sentinel policies and specify
+arguments to pass to that plugin on startup.
+
+<EnterpriseAlert/>
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
+
+## Resources
+
+Refer to these resources for details on using Sentinel policies with
+Nomad:
+
+- [Governance and policy on
+  Nomad](/nomad/docs/govern)
+- [Sentinel policies](/nomad/docs/govern/sentinel)
+- [Sentinel policy
+  reference](https://developer.hashicorp.com/nomad/docs/reference/sentinel-policy)
+
+
+
diff --git a/content/nomad/v1.10.x/content/docs/configuration/server.mdx b/content/nomad/v1.10.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..896f084453
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/server.mdx
@@ -0,0 +1,543 @@
+---
+layout: docs
+page_title: server Block in Agent Configuration
+description: |-
+  Configure Nomad agent server mode in the `server` block of a Nomad agent configuration. Server mode lets the agent participate in scheduling decisions, register with service discovery, and handle join failures. Configure bootstrapping, authoritative region, redundancy zone, data directory, Nomad cluster behavior, client heartbeat period, schedulers, garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity, leader plan rejection, as well as job priority, job source content size, and tracked job versions.
+---
+
+# `server` Block in Agent Configuration
+
+<Placement groups={['server']} />
+
+This page provides reference information for configuring Nomad agent server mode
+in the `server` block of a Nomad agent configuration. Server mode lets the agent
+participate in scheduling decisions, register with service discovery, and handle
+join failures. Configure bootstrapping, authoritative region, redundancy zone,
+data directory, Nomad cluster behavior, client heartbeat period, schedulers,
+garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity,
+and leader plan rejection, as well as job priority, job source content size, and
+tracked job versions.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens in multi-region, federated deployments.
+  Non-authoritative regions will replicate from the authoritative to act as a
+  mirror. By default, the local region is assumed to be authoritative. Setting
+  `authoritative_region` assumes that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [])` - Specifies which sub-schedulers
+  this server  handles. Use this to restrict the evaluations that worker threads
+  dequeue for processing. Nomad treats the empty default value as `["service",
+  "batch", "system", "sysbatch"]`.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. Refer to the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m".
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via
+  `batch_eval_gc_threshold`. Nomad garbage collects allocations with their
+  evaluations, so this field also controls server garbage collection of
+  allocations. Evaluations with non-terminal allocations cannot be garbage
+  collected.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold. Allocations are garbage collected with their
+  evaluations, so this field also controls server garbage collection of
+  allocations. Evaluations with non-terminal allocations cannot be garbage
+  collected.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>(<a href="/nomad/api-docs/operator/scheduler#update-scheduler-configuration">scheduler_configuration:</a></code>`nil`) - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is
+  bootstrapped or value is updated through the [API
+  endpoint][update-scheduler-config]. Refer to [the example
+  section](#configuring-scheduler-config) for more details.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". Refer to the [Client Heartbeats](#client-heartbeats) section for
+  details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients must
+  heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described in the following paragraph. Lower values are used to
+  tighten timing and increase sensitivity while higher values relax timings and
+  reduce sensitivity. Tuning this affects the time it takes Nomad to detect
+  leader failures and to perform leader elections, at the expense of requiring
+  more network and CPU resources for better performance. The maximum allowed
+  value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/reference/metrics) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, refer to the [Autopilot Guide](/nomad/docs/manage/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key from the [JWKS URL][] before
+  it is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. Refer to the [server_join documentation][server-join] for more detail.
+
+- `start_timeout` `(string: "30s")` - A timeout applied to the server setup and
+  startup processes. These processes (keyring decryption) are expected to
+  complete before the server is considered healthy, and if the timeout is
+  reached before they are completed, the server will exit. Without this, the
+  server can hang indefinitely waiting for these.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, refer to the [Autopilot Guide](/nomad/docs/manage/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+- `oidc_issuer` `(string: "")` - Specifies the Issuer URL for [Workload
+    Identity][wi] JWTs. For example, `"https://nomad.example.com"`. If set the
+    `/.well-known/openid-configuration` HTTP endpoint is enabled for third
+    parties to discover Nomad's OIDC configuration.  Once set `oidc_issuer`
+    *cannot be changed* without invalidating Workload Identities that have the
+    old issuer claim. For this reason it is suggested to set `oidc_issuer` to a
+    proxy in front of Nomad's HTTP API to ensure a stable DNS name can be used
+    instead of a potentially ephemeral Nomad server IP.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. Refer to the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. Refer to the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, refer to the
+[automatic Nomad bootstrapping documentation](/nomad/docs/deploy/clusters/connect-nodes).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`disconnect.lost_after`][disconnect.lost_after] is set)
+and replaced.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer Nomad takes to replace a `down`
+  Client's workload.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  replaced.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO                   |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and replaces their
+work.
+
+[encryption]: /nomad/docs/secure/traffic/gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]:/nomad/docs/monitor#progress
+[`nomad operator gossip keyring generate`]: /nomad/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/manage/key-management
+[disconnect.lost_after]: /nomad/docs/job-specification/disconnect#lost_after
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[wi]: /nomad/docs/concepts/workload-identity
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[JWKS URL]: /nomad/api-docs/operator/keyring#list-active-public-keys
diff --git a/content/nomad/v1.10.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.10.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..a9935bf3f8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: server_join Block in Agent Configuration
+description: >-
+  Configure how Nomad agents discover and connect to Nomad servers in Amazon, Microsoft, and Google clouds as well as on-prem. Use the`server_join` block to configure the list of servers to join, retry interval, and max rejoin attempts.
+---
+
+# `server_join` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+This page provides reference information for configuring how Nomad agents
+discover and connect to Nomad servers in Amazon, Microsoft, and Google
+clouds as well as on-prem. Use the`server_join` block to configure the list of
+servers to join, retry interval, and max rejoin attempts.
+
+```hcl
+server_join {
+  retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max      = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of Nomad server
+  addresses and [Cloud Auto-join](#cloud-auto-join) configurations that are
+  joined as cluster members. This is similar to [`start_join`](#start_join),
+  but join attempts are retried up to [retry_max](#retry_max) times.
+  Further, `retry_join` is available to both Nomad servers and clients, while
+  `start_join` is only defined for Nomad servers. This is useful for cases where
+  we know the address will become available eventually. Use `retry_join` with an
+  array as a replacement for `start_join`, **do not use both options**.
+
+  Server addresses must conform to the [server address format](#server-address-format).
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Auto-join configurations must conform to the [Cloud Auto-join format](#cloud-auto-join).
+
+  Cloud-Auto join using `go-discover` to join an AWS EC2 cluster.
+
+  ```hcl
+  server_join {
+    retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Cloud-Auto join using `go-netaddrs` to join a Hetzner cluster of servers
+  labeled with `nomad-server=true` using the `hcloud` CLI.
+
+  ```hcl
+  server_join {
+    retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+  }
+  ```
+
+  Server addresses and Cloud Auto-join configurations may be used together.
+  This is a mixed configuration containing a server address and Cloud Auto-join
+  configuration.
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Refer to [server address format](#server-address-format) for more information
+  about expected server address formats and [Cloud Auto-join](#cloud-auto-join)
+  for more information on expected Cloud Auto-join formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+`retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud provider metadata. Refer to [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+`retry_join`'s Cloud Auto-join allows Nomad to automatically discover cluster
+server addresses using cloud provider metadata. Cloud Auto-join allows both
+[go-discover](https://github.com/hashicorp/go-discover) and
+[go-netaddrs](https://github.com/hashicorp/go-netaddrs) formats.
+
+Configurations prefixed with `provider=` use `go-discover` whereas
+configurations prefixed with `exec=` use `go-netaddrs`. For cloud providers not
+supported by `go-discover`, use `go-netaddrs`.
+
+### `go-discover` Configurations
+
+`go-discover` configurations are prefixed with `provider=`.
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers,
+refer to further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+#### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication. Refer to
+  the following Authentication and Precedence section for details.
+- `secret_access_key` (optional) - the AWS secret access key for authentication.
+ Refer to the following Authentication and Precedence section for details.
+
+##### Authentication and Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+#### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets. If using tags,
+the `tag_key` and `tag_value` must be set on the network interface resource attached to the server
+not on the virtual machine resource itself.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `subscription_id` (required) - the Azure subscription ID.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+<Note>
+
+If the Nomad cluster is hosted on Azure, Nomad can use Managed Service Identities (MSI) to access Azure
+instead of an environment variable, shared client id and secret. MSI must be enabled on the VMs or Virtual
+Machine Scale Sets hosting Nomad. It is the preferred configuration since MSI prevents your Azure credentials
+from being stored in Nomad configuration. When using MSI, the `tag_name`, `tag_value` and `subscription_id` 
+need to be supplied for Virtual machines. Be aware that the amount of time that Azure takes for the VMs to detect
+the MSI permissions can be between a minute to an hour.
+
+</Note>
+
+
+#### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. Refer
+ to the following Authentication and Precedence section for more information.
+
+##### Authentication and Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
+
+
+### `go-netaddrs` Configurations
+
+`go-netaddrs` configurations are prefixed with `exec=`.
+
+What follows the `exec=` prefix may be any executable program and its arguments.
+Commands run by `go-netaddrs` must return a list of space-delimited IPv4 or IPv6
+addresses and exit with code `0` on success and non-zero on failure.
+
+You can refer to the executable by its absolute file system path, or by
+the executable's name if it can be found on the Nomad agent's PATH. Refer to
+[executables in the current directory](https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory)
+for more details on the lookup behavior.
+
+Example `go-netaddrs` configuration.
+
+```hcl
+server_join {
+  retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+}
+```
+
+Here, `hcloud`'s newline-delimited output has been re-formatted as space-
+delimited by piping its output into `tr`.
+
+Output of an example `go-netaddrs` executable
+
+```
+"1.1.1.1 2.2.2.2"
+```
+
+Visit [go-netaddrs](https://github.com/hashicorp/go-netaddrs) for more
+information on go-netaddrs configuration.
diff --git a/content/nomad/v1.10.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.10.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..3ad586cbc5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: telemetry Block in Agent Configuration
+description: |-
+  Configure Nomad telemetry behavior in the `telemetry` block of a Nomad agent configuration. Configure Nomad's publication of metrics and telemetry to Statsite, StatsD, DataDog, Prometheus, and Apica (Circonus).
+---
+
+# `telemetry` Block in Agent Configuration
+
+<Placement groups={['telemetry']} />
+
+This page provides reference information for configuring Nomad telemetry
+behavior in the `telemetry` block of a Nomad agent configuration. Configure
+Nomad's publication of metrics and telemetry to [Statsite], [StatsD], [DataDog],
+[Prometheus], and [Apica (Circonus)][Apica].
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for the
+`telemetry` block. To understand the architecture and metrics themselves,
+refer to the [Telemetry guide](/nomad/docs/monitor).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `in_memory_collection_interval` `(duration: 10s)` Configures the in-memory
+  sink collection interval. This sink is always configured and backs the JSON
+  metrics API endpoint. This option is particularly useful for debugging or
+  development purposes, where aggressive collection is required.
+
+- `in_memory_retention_period` `(duration: 1m)` Configures the in-memory sink
+  retention period. This sink is always configured and backs the JSON metrics
+  API endpoint. This option is particularly useful for debugging or development
+  purposes.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `include_alloc_metadata_in_metrics` `(bool: false)` - This controls whether
+  allocation metadata is included in metric labels. Enabling this option may result in
+  high cardinality labels. You should also configure [allowed_metadata_keys_in_metrics](#allowed_metadata_keys_in_metrics).
+
+- `allowed_metadata_keys_in_metrics` `(list: [])` - This filters the metadata
+  keys to be included in the metric publishing. By default it does not filter
+  out any keys and thus include all metadata.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+- `disable_quota_utilization_metrics` `(bool: false)` - Specifies if Nomad
+  should publish metrics about quota utilization (a Nomad Enterprise feature).
+  Since each quota utilization check requires a relatively expensive check
+  against Nomad's state store, users with many namespaces and many quotas may
+  want to disable these metrics.
+
+- `disable_allocation_hook_metrics` `(bool: false)` - Specifies if the Nomad
+  client should publish metrics related to allocation and task hooks.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog].
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should make
+  Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+  Nomad's Prometheus client retains metrics in memory unless scraped, so you
+  should not enable this field unless you are collecting metrics via Promtheus.
+
+### `circonus` (Apica)
+
+These `telemetry` parameters apply to [Apica], formerly Circonus. Apica acquired Circonus in 2024.
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
+
+
+[Statsite]: https://github.com/armon/statsite
+[StatsD]: https://github.com/etsy/statsd
+[DataDog]: https://github.com/DataDog/datadog-agent
+[Prometheus]: https://prometheus.io
+[Apica]: https://www.apica.io/
diff --git a/content/nomad/v1.10.x/content/docs/configuration/tls.mdx b/content/nomad/v1.10.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..4bdaaf2318
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: tls Block in Agent Configuration
+description: |-
+  Configure secure communication in the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key files. Specify the TLS version. Require client certificates for all incoming HTTPS requests and the server name on all outgoing TLS connections.
+---
+
+# `tls` Block in Agent Configuration
+
+<Placement groups={['tls']} />
+
+This page provides reference information for configuring secure communication in
+the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and
+RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key
+files. Specify the TLS version. Require client certificates for all incoming
+HTTPS requests and verifying the server name on all outgoing TLS connections.
+
+Note that he Nomad documentation uses "TLS" to refer to this communication
+except when it is potentially ambiguous between TLS and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for the `tls` block. To understand how to setup the certificates themselves, refer to
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/docs/secure/traffic/tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+  Nomad does not accept explicit ciphersuite configuration when for TLS 1.3
+  because the Go team has already designated a select set of ciphers that align
+  with the broadly-accepted Mozilla Security/Server Side TLS guidance for
+  [modern TLS configuration][modern-tls].
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12", "tls13".
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
+[modern-tls]: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
diff --git a/content/nomad/v1.10.x/content/docs/configuration/ui.mdx b/content/nomad/v1.10.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..63e74375ad
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: ui Block in Agent Configuration
+description: |-
+  Configure Nomad's web UI in the `ui` block of a Nomad agent configuration. Provide Vault and Consul links, add custom text to Nomad's UI, and define the HTTP Content Security Policy response header.
+---
+
+# `ui` Block in Agent Configuration
+
+<Placement groups={['ui']} />
+
+This page provides reference information for configuring Nomad's web UI in the
+`ui` block of a Nomad agent configuration. Provide Vault and Consul links,
+add custom text to display in Nomad's UI, and define the HTTP Content
+Security Policy response header.
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+- `show_cli_hints` `(bool: true)` - Controls whether CLI commands display hints
+  about equivalent UI pages. For example, when running `nomad server members`,
+  the CLI shows a message indicating where to find server information in
+  the web UI. Set to `false` to disable these hints.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI defaults to a black background. HEX values
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI defaults to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.10.x/content/docs/configuration/vault.mdx b/content/nomad/v1.10.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..09ecb1c9d7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: vault Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with HashiCorp Vault in the `vault` block of a Nomad agent configuration. Configure cluster name and the role for creating tokens. For Nomad clients, configure Vault's address, namespace, and certificate or TLS authentication. Specify the JWT authentication path. For Nomad servers, configure the server's default workload identity, which includes workload identity recipients, workload TTL, and key-value pairs for additional identity claims.
+
+---
+
+# `vault` Block in Agent Configuration
+
+<Placement groups={['vault']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [HashiCorp Vault][vault] in the `vault` block of a Nomad agent
+configuration. Configure cluster name and the role for creating tokens. For
+Nomad clients, configure Vault's address, namespace, and certificate or TLS
+authentication. Specify the JWT authentication path. For Nomad
+servers, configure the server's default workload identity, which includes
+workload identity recipients, workload TTL, and key-value pairs for additional
+identity claims.
+
+When configured, job tasks can use [workload identities][workload_id] to receive
+Vault ACL tokens automatically.
+
+Refer to the [Nomad and Vault Integration][nomad-vault] page for more
+information about the Vault integration.
+
+```hcl
+vault {
+  enabled = true
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+
+    extra_claims {
+      unique_id = "${job.region}:${job.namespace}:${job.id}"
+    }
+  }
+}
+```
+
+In Nomad Enterprise, you may specify multiple `vault` blocks to configure access
+to multiple Vault clusters. Each Vault cluster must have a different value for
+the [`name`](#name) field.
+
+## `vault` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`vault.cluster`][] field. In Nomad Community Edition, only
+  the `"default"` cluster will be used, so this field should be omitted.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`] set to `true`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `jwt_auth_backend_path` - `(string: "jwt-nomad")` - Specifies the mount
+  [path][vault_auth_enable_path] of the JWT authentication method to be used to
+  login with workload identity JWTs.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens
+  from. This field defines the role used to derive task tokens when the job does
+  not define a value for [`vault.role`][jobspec_vault_role]. If empty, the
+  default Vault cluster role is used.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `default_identity` <code>([Identity](#default_identity-parameters): nil)</code> -
+  Specifies the default workload identity configuration to use when a task with
+  a `vault` block does not specify an [`identity`][jobspec_identity] block
+  named `vault_<name>`, where `<name>` matches the value of this `vault` block
+  [`name`](#name) parameter. Setting a default identity causes the value of
+  `allow_unauthenticated` to be ignored.
+
+### `default_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`bound_audiences`][vault_bound_aud]
+  configuration in the Vault JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in
+  the task's `NOMAD_TOKEN_vault` environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_vault.jwt`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+- `extra_claims` `(map[string]string: optional)` - A set of key-value pairs that
+  will be provided as extra identity claims for workloads. You can use the keys
+  as [user claims in Vault role configurations][vault-jwt-user-claim]. The
+  values are interpolated. For example, if you include the extra claim
+  `unique_id = "${job.region}:${job.namespace}:${job.id}"`, you could set the
+  user claim field to `/extra_claims/unique_id` to map that identifier to an
+  entity alias. The available attributes for interpolation are:
+
+  - `${job.region}` - The region where the job is running.
+  - `${job.namespace}` - The job's namespace.
+  - `${job.id}` - The job's ID.
+  - `${job.node_pool}` - The node pool where the allocation is running.
+  - `${group.name}` - The task group name of the task using Vault.
+  - `${alloc.id}` - The allocation's ID.
+  - `${task.name}` - The name of the task using Vault.
+  - `${node.id}` - The ID of the node where the allocation is running.
+  - `${node.datacenter}` - The datacenter of the node where the allocation is running.
+  - `${node.pool}` - The node pool of the node where the allocation is running.
+  - `${node.class` - The class of the node where the allocation is running.
+  - `${vault.cluster}` - The Vault cluster name.
+  - `${vault.namespace}` - The Vault namespace.
+  - `${vault.role}` - The Vault role.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows a Vault configuration for a Nomad server using the workload
+identity authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled = true
+
+  # Provide a default workload identity configuration so jobs don't need to
+  # specify one.
+  default_identity {
+    aud  = ["vault.io"]
+    env  = false
+    file = true
+    ttl  = "1h"
+  }
+}
+```
+
+### Nomad Client
+
+This example shows a Vault configuration for a Nomad client.
+
+```hcl
+client {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  address   = "https://vault.service.consul:8200"
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+}
+```
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[jobspec_identity]: /nomad/docs/job-specification/identity
+[nomad-vault]: /nomad/docs/secure/vault 'Nomad Vault Integration'
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault_bound_aud]: /vault/api-docs/auth/jwt#bound_audiences
+[vault_auth_enable_path]: /vault/docs/commands/auth/enable#path
+[workload_id]: /nomad/docs/concepts/workload-identity
+[vault-jwt-user-claim]: /vault/api-docs/auth/jwt#user_claim
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/connect-nodes.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/connect-nodes.mdx
new file mode 100644
index 0000000000..5d1f406ae8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/connect-nodes.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: Connect nodes into a cluster
+description: |-
+  Connect nodes together to create a Nomad cluster manually
+  or automatically with cloud auto-join on AWS, Azure, and GCP.
+---
+
+# Connect nodes into a cluster
+
+In order to create a Nomad cluster out of individual nodes, you need to
+introduce them to one another. There are several ways to perform this:
+
+- Manually
+- Cloud Auto-Join
+- Consul
+
+This tutorial describes each method and provides configuration snippets, which
+you can use as starting points for your own configuration.
+
+## Manual clustering
+
+Manually bootstrapping a Nomad cluster does not rely on additional tooling, but
+does require operator participation in the cluster formation process. When
+bootstrapping, Nomad servers and clients must be started and informed with the
+address of at least one Nomad server.
+
+As you can tell, this creates a chicken-and-egg problem where one server must
+first be fully bootstrapped and configured before the remaining servers and
+clients can join the cluster. This requirement can add additional provisioning
+time as well as ordered dependencies during provisioning.
+
+First, you need to bootstrap a single Nomad server and capture its IP address.
+Place this address in the configuration once you have that nodes IP address.
+
+For Nomad servers, this configuration may look something like this:
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  # This is the IP address of the first server provisioned
+  server_join {
+    retry_join = ["<known-address>:4648"]
+  }
+}
+```
+
+Alternatively, you can supply a server's address after the servers have all been
+started by running the [`server join` command] on the servers individually to
+cluster the servers. All servers can join one other server, and then rely on the
+gossip protocol to discover the rest.
+
+```shell-session
+$ nomad server join <known-address>
+```
+
+For Nomad clients, the configuration may look something like:
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = ["<known-address>:4647"]
+  }
+}
+```
+
+The client node's server list can be updated at run time using the
+[`node config` command].
+
+```shell-session
+$ nomad node config -update-servers <IP>:4647
+```
+
+The port corresponds to the RPC port. If no port is specified with the IP
+address, the default RPC port of `4647` is assumed.
+
+As servers are added or removed from the cluster, this information is pushed to
+the client. This means only one server must be specified because, after initial
+contact, the full set of servers in the client's region are shared with the
+client.
+
+## Join nodes using cloud auto-join
+
+As of Nomad 0.8.4, [`retry_join`] accepts a unified interface using the
+[go-discover] library for doing automatic cluster joining using cloud metadata.
+To use retry-join with a supported cloud provider, specify the configuration on
+the command line or configuration file as a `key=value key=value ...` string.
+Values are taken literally and must not be URL encoded. If the values contain
+spaces, backslashes or double quotes they need to be double quoted and the usual
+escaping rules apply.
+
+```json
+{
+  "retry_join": ["provider=my-cloud config=val config2=\"some other val\" ..."]
+}
+```
+
+Consult the [cloud provider-specific configurations] in the cloud-autojoin
+documentation. This can be combined with static IP or DNS addresses or even
+multiple configurations for different providers. In order to use discovery
+behind a proxy, you will need to set `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY`
+environment variables per [Golang `net/http` library].
+
+## Use Consul to automatically cluster nodes
+
+To automatically bootstrap a Nomad cluster, Nomad can leverage another HashiCorp
+open source tool, [Consul]. Bootstrapping Nomad is easiest against an existing
+Consul cluster. The Nomad servers and clients will become informed of each
+other's existence when the Consul agent is installed and configured on each
+host. As an added benefit, integrating Consul with Nomad provides service and
+health check registration for applications which later run under Nomad.
+
+Consul models infrastructures as datacenters and multiple Consul datacenters can
+be connected over the WAN so that clients can discover nodes in other
+datacenters. Since Nomad regions can encapsulate many datacenters, you should be
+running a Consul cluster in every Nomad region and connecting them over the
+WAN. Refer to the Consul tutorial for both [bootstrapping] a single
+datacenter and [connecting multiple Consul clusters over the WAN].
+
+If a Consul agent is installed on the host prior to Nomad starting, the Nomad
+agent will register with Consul and discover other nodes.
+
+For servers, you must inform the cluster how many servers you expect to have.
+This is required to form the initial quorum, since Nomad is unaware of how many
+peers to expect. For example, to form a region with three Nomad servers, you
+would use the following Nomad configuration file:
+
+```hcl
+# /etc/nomad.d/server.hcl
+
+# data_dir tends to be environment specific.
+data_dir = "/opt/nomad/data"
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+```
+
+This configuration would be saved to disk and then run:
+
+```shell-session
+$ nomad agent -config=/etc/nomad.d/server.hcl
+```
+
+A similar configuration is available for Nomad clients:
+
+```hcl
+# /etc/nomad.d/client.hcl
+
+datacenter = "dc1"
+
+# data_dir tends to be environment specific.
+data_dir = "/opt/nomad/data"
+
+client {
+  enabled = true
+}
+```
+
+The agent is started in a similar manner:
+
+```shell-session
+$ sudo nomad agent -config=/etc/nomad.d/client.hcl
+```
+
+Nomad clients should always run as root (or with `sudo`). The above
+configurations include no IP or DNS addresses between the clients and
+servers. This is because Nomad detected the existence of Consul and utilized
+service discovery to form the cluster.
+
+### Consul auto-join internals
+
+~> This section discusses the internals of the Consul and Nomad integration at a
+very high level. Reading is only recommended for those curious to the
+implementation.
+
+As discussed in the previous section, Nomad merges multiple configuration files
+together, so the `-config` may be specified more than once:
+
+```shell-session
+$ nomad agent -config=base.hcl -config=server.hcl
+```
+
+In addition to merging configuration on the command line, Nomad also maintains
+its own internal configurations (called "default configs") which include reasonable
+base defaults. One of those default configurations includes a "consul" block,
+which specifies reasonable defaults for connecting to and integrating with Consul. In
+essence, this configuration file resembles the following:
+
+```hcl
+# You do not need to add this to your configuration file. This is an example
+# that is part of Nomad's internal default configuration for Consul integration.
+consul {
+  # The address to the Consul agent.
+  address = "127.0.0.1:8500"
+
+  # The service name to register the server and client with Consul.
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+
+  # Enables automatically registering the services.
+  auto_advertise = true
+
+  # Enabling the server and client to bootstrap using Consul.
+  server_auto_join = true
+  client_auto_join = true
+}
+```
+
+Refer to the [`consul` stanza] documentation for the complete set of configuration
+options.
+
+[`consul` stanza]: /nomad/docs/configuration/consul
+[`node config` command]: /nomad/commands/node/config
+[`retry_join`]: /nomad/docs/configuration/server_join#retry_join
+[`server join` command]: /nomad/commands/server/join
+[bootstrapping]: /consul/docs/deploy/server/vm/bootstrap
+[cloud provider-specific configurations]: /nomad/docs/configuration/server_join#cloud-auto-join
+[connecting multiple consul clusters over the wan]: /consul/docs/east-west/wan-federation
+[consul]: /consul/
+[go-discover]: https://github.com/hashicorp/go-discover
+[golang `net/http` library]: https://golang.org/pkg/net/http/#ProxyFromEnvironment
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/federate-regions.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/federate-regions.mdx
new file mode 100644
index 0000000000..2ae0283062
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/federate-regions.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Federate multi-region clusters
+description: |-
+  Set up multi-region federation to allow job submissions and API
+  interactions from any server in any region.
+---
+
+# Federate multi-region clusters
+
+Nomad operates at a regional level and provides first-class support for
+federation. Federation enables users to submit jobs or interact with the HTTP
+API targeting any region, from any server, even if that server resides in a
+different region.
+
+Federating multiple Nomad clusters requires network connectivity between the
+clusters. Servers in each cluster must be able to communicate over [RPC and
+Serf][ports-used]. Federated clusters are expected to communicate over WANs, so
+they do not need the same low latency as servers within a region.
+
+Once Nomad servers are able to connect over the network, you can issue the
+[nomad server join][server-join] command from any server in one region to a
+server in a remote region to federate the clusters.
+
+[![Multi-Region][multi-region-pic]][multi-region-pic]
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have two Nomad
+environments with ports 4646, 4647, and 4648 exposed. You can use this
+[Terraform environment][nomad-tf] to provision the sandbox environments. This
+guide assumes two clusters with one server node and two client nodes in each
+cluster. While the Terraform code already opens port 4646, you will also need to
+expose ports 4647 and 4648 on the server you wish to run [nomad server
+join][server-join] against (consult the [Nomad Port Requirements][ports-used]
+documentation for more information).
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node in each cluster. Consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+## Verify current regions
+
+Currently, each of your clusters is in the default `global`
+[region][region-config]. You can verify this by running [nomad server
+members][nomad-server-members] on any node in each of your clusters:
+
+```shell-session
+$ nomad server members
+Name                    Address       Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-29-34.global  172.31.29.34  4648  alive   true    2         0.10.1  dc1         global
+```
+
+## Change the regions
+
+Respectively change the region of your individual clusters into `west` and
+`east` by adding the [region][region-config] parameter into the agent
+configuration on the servers and clients (if you are using the provided sandbox
+environment, this configuration is located at `/etc/nomad.d/nomad.hcl`).
+
+Below is a snippet of the configuration file showing the required change on a
+node for one of the clusters (remember to change this value to `east` on the
+servers and clients in your other cluster):
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+region = "west"
+# ...
+```
+
+Once you have made the necessary changes for each cluster, restart the nomad
+service on each node:
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+Re-run the `nomad server members` command on any node in the cluster to verify
+that your server is configured to be the in the correct region. The output below
+is from running the command in the `west` region (make sure to run this command
+in your other cluster to make sure it is in the `east` region):
+
+```shell-session
+$ nomad server members
+Name                  Address       Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-29-34.west  172.31.29.34  4648  alive   true    2         0.10.1  dc1         west
+```
+
+## Federate the regions
+
+Run the [`nomad server join`][server-join] command from a server in one cluster
+and supply it the IP address of the server in your other cluster while
+specifying port 4648.
+
+Below is an example of running the `nomad server join` command from the server
+in the `west` region while targeting the server in the `east` region:
+
+```shell-session
+$ nomad server join 172.31.26.138:4648
+Joined 1 servers successfully
+```
+
+## Verify the clusters have been federated
+
+After you have federated your clusters, the output from the `nomad server members` command will show the servers from both regions:
+
+```shell-session
+$ nomad server members
+Name                     Address        Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-26-138.east    172.31.26.138  4648  alive   true    2         0.10.1  dc1         east
+ip-172-31-29-34.west     172.31.29.34   4648  alive   true    2         0.10.1  dc1         west
+```
+
+## Check job status in remote cluster
+
+From the Nomad cluster in the `west` region, try to run the [`nomad status`][nomad-status] command to check the status of jobs in the `east` region:
+
+```shell-session
+$ nomad status -region="east"
+No running jobs
+```
+
+If your regions were not federated properly, you will receive the following
+output:
+
+```shell-session
+$ nomad status -region="east"
+Error querying jobs: Unexpected response code: 500 (No path to region)
+```
+
+## Learn more about federation
+
+- [Deployment Topology across Multiple Regions][multi-region]
+
+[multi-region]: /nomad/docs/deploy/production/reference-architecture#deployment-topology-across-multiple-regions
+[multi-region-pic]: /img/clusters/nomad-multi-region.png
+[nomad-server-members]: /nomad/commands/server/members
+[nomad-status]: /nomad/commands/status
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[ports-used]: /nomad/docs/deploy/production/requirements#ports-used
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture
+[region-config]: /nomad/docs/configuration#region
+[server-join]: /nomad/commands/server/join
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-considerations.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-considerations.mdx
new file mode 100644
index 0000000000..a3ead6788f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-considerations.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Multi-region federation operational considerations
+description: |-
+  Review operational considerations for running Nomad multi-region federated clusters as well as instructions for migrating the authoritative region to a federated region.
+---
+
+# Multi-region federation operational considerations
+
+This page lists operational considerations for running multi-region federated
+clusters as well as instructions for migrating the authoritative region to a
+federated region.
+
+## Operational considerations
+
+When operating multi-region federated Nomad clusters, consider the following:
+
+* **Regular snapshots**: You can back up Nomad server state using the
+  [`nomad operator snapshot save`][] and [`nomad operator snapshot agent`][] commands. Performing
+  regular backups expedites disaster recovery. The cadence depends on cluster rates of change
+  and your internal SLA’s. You should regularly test snapshots using the
+  [`nomad operator snapshot restore`][] command to ensure they work.
+
+* **Local ACL management tokens**: You need local management tokens to perform federated cluster
+  administration when the authoritative region is down. Make sure you have existing break-glass
+  tokens available for each region.
+
+* **Known paths to creating local ACL tokens**: If the authoritative region fails, creation of
+  global ACL tokens fails. If this happens, having the ability to create local ACL tokens allows
+  you to continue to interact with each available federated region.
+
+## Authoritative and federated regions
+
+* **Can non-authoritative regions continue to operate if the authoritative region is unreachable?**:
+  Yes, running workloads are never interrupted due to federation failures. Scheduling of new
+  workloads and rescheduling of failed workloads is never interrupted due to federation failures.
+  See [Failure Scenarios][failure_scenarios] for details.
+
+* **Can the authoritative region be deployed with servers only?** Yes, deploying the Nomad
+  authoritative region with servers only, without clients, works as expected. This servers-only
+  approach can expedite disaster recovery of the region. Restoration does not include objects such
+  as nodes, jobs, or allocations, which are large and require compute intensive reconciliation
+  after restoration.
+
+* **Can I migrate the authoritative region to a currently federated region?** It is possible by
+  following these steps:
+
+  1. Update the [`authoritative_region`][] configuration parameter on the desired authoritative
+    region servers.
+  1. Restart the server processes in the new authoritative region and ensure all data is present in
+    state as expected. If the network was partitioned as part of the failure of the original
+    authoritative region, writes of replicated objects may not have been successfully replicated to
+    federated regions.
+  1. Update the [`authoritative_region`][] configuration parameter on the federated region servers
+    and restart their processes.
+
+* **Can federated regions be bootstrapped while the authoritative region is down?**  No they
+cannot.
+
+[`nomad operator snapshot save`]: /nomad/commands/operator/snapshot/save
+[`nomad operator snapshot agent`]: /nomad/commands/operator/snapshot/agent
+[`nomad operator snapshot restore`]: /nomad/commands/operator/snapshot/restore
+[failure_scenarios]: /nomad/docs/deploy/clusters/federation-failure-scenarios
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx
new file mode 100644
index 0000000000..ec97736b15
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: Federated cluster failure scenarios
+description: |-
+  Review failure scenarios in multi-region federated cluster deployments.  Learn which Nomad features continue to work under federated and authoritative region failures.
+---
+
+# Federated cluster failure scenarios
+
+When running Nomad in federated mode, failure situations and impacts are different depending on
+whether the authoritative region is the impacted region or not, and what the failure mode is. In
+soft failures, the region's servers have lost quorum but the Nomad processes are still up, running,
+and reachable. In hard failures, the regional servers are completely unreachable and are akin to
+the underlying hardware having been terminated (cloud) or powered-off (on-prem).
+
+The scenarios are based on a Nomad deployment running three federated regions:
+ * `asia-south-1`
+ * `europe-west-1` - authoritative region
+ * `us-east-1`
+
+## Federated region failure: soft
+In this situation the region `asia-south-1` has lost leadership but the servers are reachable and
+up.
+
+All server logs in the impacted region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=d19e6bb5-5ec9-8f75-9caf-47e2513fe28d error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+  fail unless using the `stale=true` flag.
+
+✅ Creation and deletion of replicated objects, such as namespaces, is written to the
+  authoritative region.
+
+✅ Any federated regions with leadership is able to continue to replicate all objects detailed
+  previously.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Federated region failure: hard
+In this situation the region `asia-south-1` has gone down. When this happens, the Nomad server logs
+for the other regions have log entries similar to this example.
+```console
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Initiating push/pull sync with: us-east-1-server-1.us-east-1 192.168.1.193:9002
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+✅ Creation and deletion of replicated objects, such as namespaces, are written to the
+  authoritative region.
+
+✅ Any federated regions with leadership continue to replicate all objects detailed
+  above.
+
+✅ Creation of local ACL tokens continues to work for all regions which are running with
+  leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Authoritative region failure: soft
+In this situation the region `europe-west-1` has lost leadership but the servers are reachable and
+up.
+
+The server logs in the authoritative region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=68b3abe2-5e16-8f04-be5a-f76aebb0e59e error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail unless using the `stale=true` flag.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions are able to read data to replicate as they use the stale flag, but no
+  writes can occur to the authoritative region as described previously.
+
+✅ Creation of local ACL tokens continues to work for all federated regions which are running
+  with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all federated regions which
+  are running with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fails to deploy.
+
+## Authoritative region failure: hard
+In this situation the region `europe-west-1` has gone down. When this happens, the Nomad server
+leader logs for the other regions have log entries similar to this example.
+```console
+[ERROR] nomad/leader.go:544: nomad: failed to fetch namespaces from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1767: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2498: nomad: failed to fetch ACL binding rules from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader_ent.go:226: nomad: failed to fetch quota specifications from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:703: nomad: failed to fetch node pools from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1909: nomad: failed to fetch tokens from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2083: nomad: failed to fetch ACL Roles from authoritative region: error="rpc error: EOF"
+[DEBUG] nomad/leader_ent.go:84: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2292: nomad: failed to fetch ACL auth-methods from authoritative region: error="rpc error: EOF"
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect europe-west-1-server-1.europe-west-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions with leadership is not able to replicate objects detailed in the logs.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/index.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/index.mdx
new file mode 100644
index 0000000000..fc7eef29e7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Nomad clusters
+description: |-
+  This section contains material for creating and federating Nomad clusters.Connect nodes into a cluster, federate multi-region clusters, and configure a web UI reverse proxy. Review multi-region federation considerations and failure scenarios. mplement load balancing using Fabio, HAProxy, NGINX, or Traefik. Manage external traffic with application load balancing.
+
+---
+
+# Nomad clusters
+
+This section contains content for creating and federating Nomad clusters.
+Connect nodes into a cluster, federate multi-region clusters, and configure a
+web UI reverse proxy. Review multi-region federation considerations and
+failure scenarios. Implement load balancing using Fabio, HAProxy, NGINX, or
+Traefik. Manage external traffic with application load balancing.
diff --git a/content/nomad/v1.10.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx b/content/nomad/v1.10.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx
new file mode 100644
index 0000000000..efd7f73e28
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx
@@ -0,0 +1,392 @@
+---
+layout: docs
+page_title: Configure a web UI reverse proxy
+description: |-
+  Run and configure NGINX as a reverse proxy for the Nomad web UI to
+  create a secure way for users to access detailed cluster information.
+---
+
+# Configure a web UI reverse proxy
+
+NGINX can be used to reverse proxy web services and balance load across multiple instances of the same service. A reverse proxy has the added benefits of enabling multiple web services to share a single, memorable domain and authentication to view internal systems.
+
+To ensure every feature in the Nomad UI remains fully functional, you must properly configure your reverse proxy to meet Nomad's specific networking requirements.
+
+This guide will explore common configuration changes necessary when reverse proxying Nomad's Web UI. Issues common to default proxy configurations will be discussed and demonstrated. As you learn about each issue, you will deploy NGINX configuration changes that will address it.
+
+## Prerequisites
+
+This guide assumes basic familiarity with Nomad and NGINX.
+
+Here is what you will need for this guide:
+
+- Nomad 0.11.0 installed locally
+- Docker
+
+## Start Nomad
+
+Because of best practices around least access to nodes, it is typical for Nomad
+UI users to not have direct access to the Nomad client nodes. You can simulate
+that for the purposes of this guide by advertising an incorrect `http` address.
+
+Create a file named `nomad.hcl` with the following configuration snippet.
+
+```hcl
+# Advertise a bogus HTTP address to force the UI
+# to fallback to streaming logs through the proxy.
+advertise {
+  http = "internal-ip:4646"
+}
+```
+
+Start Nomad as a dev agent with this custom configuration file.
+
+```shell-session
+$ sudo nomad agent -dev -config=nomad.hcl
+```
+
+Next, create a service job file that will frequently write logs to `stdout`. This sample job file below can be used if you don't have your own.
+
+```hcl
+# fs-example.nomad.hcl
+
+job "fs-example" {
+  datacenters = ["dc1"]
+
+  task "fs-example" {
+    driver = "docker"
+
+    config {
+      image = "dingoeatingfuzz/fs-example:0.3.0"
+    }
+
+    resources {
+      cpu    = 500
+      memory = 512
+    }
+  }
+}
+```
+
+Run this service job using the Nomad CLI or UI.
+
+```shell-session
+$ nomad run fs-example.nomad.hcl
+```
+
+At this point, you have a Nomad cluster running locally with one job in it. You can visit the Web UI at `http://localhost:4646`.
+
+## Configure NGINX to reverse proxy the web UI
+
+As mentioned earlier, the overarching goal is to configure a proxy from Nomad UI users to the Nomad UI running on the Nomad cluster. To do that, you will configure a NGINX instance as your reverse proxy.
+
+Create a basic NGINX configuration file to reverse proxy the Web UI. It is important to name the NGINX configuration file `nginx.conf` otherwise the file will not bind correctly.
+
+```nginx
+# nginx.conf
+events {}
+
+http {
+  server {
+    location / {
+      proxy_pass http://host.docker.internal:4646;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    }
+  }
+}
+```
+
+<Note>
+
+ If you are not using Docker for Mac or Docker for Windows, the `host.docker.internal` DNS record may not be available.
+
+</Note>
+
+This basic NGINX configuration does two things. The first is forward all traffic into NGINX to the proxy address at `http://host.docker.internal:4646`. Since NGINX will be running in Docker and Nomad is running locally, this address is equivalent to `http://localhost:4646` which is where the Nomad API and Web UI are served. The second thing this configuration does is attach the `X-Forwarded-For` header which allows HTTP requests to be traced back to their origin.
+
+Next in a new terminal session, start NGINX in Docker using this configuration file.
+
+```shell-session
+$ docker run --publish=8080:80 \
+    --mount type=bind,source=$PWD/nginx.conf,target=/etc/nginx/nginx.conf \
+    nginx:latest
+```
+
+NGINX will be started as soon as Docker has finished pulling layers. At that point you can visit `http://localhost:8080` to visit the Nomad Web UI through the NGINX reverse proxy.
+
+## Extend connection timeout
+
+The Nomad Web UI uses long-lived connections for its live-update feature. If the proxy closes the connection early because of a connection timeout, it could prevent the Web UI from continuing to live-reload data.
+
+The Nomad Web UI will live-reload all data to make sure views are always fresh as Nomad's server state changes. This is achieved using the [blocking queries][blocking-queries] to the Nomad API. Blocking queries are an implementation of long-polling which works by keeping HTTP connections open until server-side state has changed. This is advantageous over traditional polling which results in more requests that often return no new information. It is also faster since a connection will close as soon as new information is available rather than having to wait for the next iteration of a polling loop. A consequence of this design is that HTTP requests aren't always expected to be short-lived. NGINX has a [default proxy timeout of 60 seconds](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout) while Nomad's blocking query system will leave connections open for five minutes by default.
+
+To observe the proxy time out a connection, visit the Nomad jobs list through the proxy at `http://localhost:8080/ui/jobs` with your Browser's developer tools open.
+
+<Tabs>
+  <Tab heading="Chrome">
+
+
+With the Nomad UI page open, press the `F12` key to open the Developer tools. If it is not already selected, go to the Developer tools pane and select the **Network** tab. Leaving the tools pane open. Refresh the UI page.
+
+The blocking query connection for jobs will remain in "(pending)" status.
+
+[![Chrome developer tools window showing pending connection.][img-chrome-pending]][img-chrome-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Chrome developer tools window showing connection timeout.][img-chrome-timeout]][img-chrome-timeout]
+
+  </Tab>
+  <Tab heading="Firefox">
+
+
+With the Nomad UI page open, go to the **Tools** menu, **Web Developer** flyout, and **Network** option.
+
+The blocking query connection for jobs will not show a status while it is still active.
+
+[![Firefox developer tools window showing pending connection.][img-firefox-pending]][img-firefox-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Firefox developer tools window showing connection timeout.][img-firefox-pending]][img-firefox-pending]
+
+  </Tab>
+  <Tab heading="Safari">
+
+
+With the Nomad UI page open, go to the **Tools** menu, **Web Developer** flyout, and **Network** option.
+
+The blocking query connection for jobs will have a spinning icon next to the Name while it is still active.
+
+[![Safari developer tools window showing pending connection.][img-safari-pending]][img-safari-pending]
+
+In approximately 60 seconds it will transition to a red error state. Clicking on the red error will show that you received a "504 Gateway Time-out" error.
+
+[![Safari developer tools window showing connection timeout.][img-safari-pending]][img-safari-pending]
+
+  </Tab>
+  <Tab heading="Edge">
+
+
+With the Nomad UI page open, press the `F12` key to open the Developer tools. If it is not already selected, go to the Developer tools pane and select the **Network** tab. Leaving the tools pane open. Refresh the UI page.
+
+The blocking query connection for jobs will remain in "(pending)" status.
+
+[![Edge developer tools window showing pending connection.][img-chrome-pending]][img-chrome-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Edge developer tools window showing connection timeout.][img-chrome-timeout]][img-chrome-timeout]
+
+  </Tab>
+  <Tab heading="Other">
+
+
+Open your browser's developer tools. Locate the network information and wait approximately 60 seconds. The request to `/v1/jobs` will timeout with the following error message.
+
+```plaintext
+Failed to load resource: the server responded with a status of
+504 (Gateway Time-out)
+```
+
+  </Tab>
+</Tabs>
+<hr />
+
+
+To prevent these timeouts, update the NGINX configuration's `location` block to extend the
+`proxy_read_timeout` setting. The Nomad API documentation's [Blocking
+Queries][blocking-queries] section explains that Nomad adds the result of (`wait` / 16) to the declared wait
+time. You should set the `proxy_read_timeout` to slightly exceed Nomad's calculated wait time.
+
+This guide uses the default blocking query `wait` of 300 seconds. Nomad adds
+18.75 seconds to that wait time, so the `proxy_read_timeout` should be greater than 318.75 seconds.
+
+Set the`proxy_read_timeout` to `319s`.
+
+```nginx
+# ...
+proxy_pass http://host.docker.internal:4646;
+proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+
+# Nomad blocking queries will remain open for a default of 5 minutes.
+# Increase the proxy timeout to accommodate this timeout with an
+# additional grace period.
+proxy_read_timeout 319s;
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+## Disable proxy buffering
+
+When possible the Web UI will use a streaming HTTP request to stream logs on the task logs page. NGINX by default will buffer proxy responses in an attempt to free up connections to the backend server being proxied as soon as possible.
+
+Proxy buffering causes logs events to not stream because they will be temporarily captured within NGINX's proxy buffer until either the connection is closed or the proxy buffer size is hit and the data is finally flushed to the client.
+
+Older browsers may not support this technology, in which case logs are streamed using a simple polling mechanism.
+
+To observe this issue, visit the task logs page of your sample job by first visiting the sample job at `http://localhost:8080/jobs/fs-example` then clicking into the most recent allocation, then clicking into the `fs-example` task, then clicking the logs tab.
+
+Logs will not load and eventually the following error will appear in the UI.
+
+[![Error in the UI. Cannot fetch logs. The logs for this task are inaccessible][img-cannot-fetch-logs]][img-cannot-fetch-logs]
+
+There will also be this additional error in the browser developer tools console.
+
+```plaintext
+GET http://internal-ip:4646/v1/client/fs/logs/131f60f7-ef46-9fc0-d80d-29e673f01bd6?follow=true&offset=50000&origin=end&task=ansi&type=stdout net::ERR_NAME_NOT_RESOLVED
+```
+
+This `ERR_NAME_NOT_RESOLVED` error can be safely ignored. To prevent streaming logs through Nomad server nodes when unnecessary, the Web UI optimistically attempts to connect directly to the client node the task is running on. Since the Nomad configuration file used in this guide specifically advertises an address that can't be reached, the UI automatically falls back to requesting logs through the proxy.
+
+To allow log streaming through NGINX, the NGINX configuration needs to be updated to disable proxy buffering. Add the following to the `location` block of the existing NGINX configuration file.
+
+```nginx
+# ...
+proxy_read_timeout 319s;
+
+# Nomad log streaming uses streaming HTTP requests. In order to
+# synchronously stream logs from Nomad to NGINX to the browser
+# proxy buffering needs to be turned off.
+proxy_buffering off;
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+## Enable WebSocket connections
+
+As of Nomad 0.11.0, the Web UI has supported [interactive exec sessions with any running task in the cluster](https://www.hashicorp.com/blog/hashicorp-nomad-remote-exec-web-ui). This is achieved using the exec API which is implemented using WebSockets.
+
+WebSockets are necessary for the exec API because they allow bidirectional data transfer. This is used to receive changes to the remote output as well as send commands and signals from the browser-based terminal.
+
+The way a WebSocket connection is established is through a handshake request. The handshake is an HTTP request with special `Connection` and `Upgrade` headers.
+
+WebSockets also do not support CORS headers. The server-side of a WebSocket connection needs to verify trusted origins on its own. Nomad does this verification by checking if the `Origin` header of the handshake request is equal to the address of the Nomad API.
+
+By default NGINX will not fulfill the handshake or the origin verification. This results in exec sessions immediately terminating. You can experience this in the Web UI by going to `http://localhost:8080/jobs/fs-example`, clicking the Exec button, choosing the task, and attempting to run the command `/bin/sh`.
+
+[![Error in the UI when running /bin/sh. The connection has closed.][img-cannot-remote-exec]][img-cannot-remote-exec]
+
+The fulfill the handshake NGINX will need to forward the `Connection` and `Upgrade` headers. To meet the origin verification required by the Nomad API, NGINX will have to override the existing `Origin` header to match the host address. Add the following to the `location` block of the existing NGINX configuration file.
+
+```nginx
+# ...
+proxy_buffering off;
+
+# The Upgrade and Connection headers are used to establish
+# a WebSockets connection.
+proxy_set_header Upgrade $http_upgrade;
+proxy_set_header Connection "upgrade";
+
+# The default Origin header will be the proxy address, which
+# will be rejected by Nomad. It must be rewritten to be the
+# host address instead.
+proxy_set_header Origin "${scheme}://${proxy_host}";
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+WebSocket connections are also stateful. If you are planning on using NGINX to balance load across all Nomad server nodes, it is important to ensure that WebSocket connections get routed to a consistent host.
+
+This can be done by specifying an upstream in NGINX and using it as the proxy pass. Add the following after the server block in the existing NGINX configuration file.
+
+```nginx
+# ...
+# Since WebSockets are stateful connections but Nomad has multiple
+# server nodes, an upstream with ip_hash declared is required to ensure
+# that connections are always proxied to the same server node when possible.
+upstream nomad-ws {
+  ip_hash;
+  server host.docker.internal:4646;
+}
+# ...
+```
+
+Traffic must also pass through the upstream. To do this, change the `proxy_pass` in the NGINX configuration file.
+
+```nginx
+# ...
+location / {
+  proxy_pass http://nomad-ws
+# ...
+```
+
+Since a dev environment only has one node, this change has no observable effect.
+
+## Review the complete NGINX configuration
+
+At this point all Web UI features are now working through the NGINX proxy. Here is the completed NGINX configuration file.
+
+```nginx
+events {}
+
+http {
+  server {
+    location / {
+      proxy_pass http://nomad-ws;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+
+      # Nomad blocking queries will remain open for a default of 5 minutes.
+      # Increase the proxy timeout to accommodate this timeout with an
+      # additional grace period.
+      proxy_read_timeout 319s;
+
+      # Nomad log streaming uses streaming HTTP requests. In order to
+      # synchronously stream logs from Nomad to NGINX to the browser
+      # proxy buffering needs to be turned off.
+      proxy_buffering off;
+
+      # The Upgrade and Connection headers are used to establish
+      # a WebSockets connection.
+      proxy_set_header Upgrade $http_upgrade;
+      proxy_set_header Connection "upgrade";
+
+      # The default Origin header will be the proxy address, which
+      # will be rejected by Nomad. It must be rewritten to be the
+      # host address instead.
+      proxy_set_header Origin "${scheme}://${proxy_host}";
+    }
+  }
+
+  # Since WebSockets are stateful connections but Nomad has multiple
+  # server nodes, an upstream with ip_hash declared is required to ensure
+  # that connections are always proxied to the same server node when possible.
+  upstream nomad-ws {
+    ip_hash;
+    server host.docker.internal:4646;
+  }
+}
+```
+
+## Next steps
+
+In this guide, you set up a reverse NGINX proxy configured for the Nomad UI.
+You also explored common configuration properties necessary to allow the Nomad
+UI to work properly through a proxy—connection timeouts, proxy buffering,
+WebSocket connections, and Origin header rewriting.
+
+You can use these building blocks to configure your preferred proxy server
+software to work with the Nomad UI. For further information about the NGINX
+specific configuration highlighted in this guide, consult:
+
+- [connection timeout][nginx-proxy-read-timeout]
+- [proxy buffering][nginx-proxy-buffering]
+- [WebSocket proxying][nginx-websocket-proxying]
+- [session persistence][nginx-session-persistence]
+
+[blocking-queries]: /nomad/api-docs#blocking-queries
+[nginx-proxy-buffering]: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering
+[nginx-proxy-read-timeout]: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout
+[nginx-session-persistence]: https://nginx.org/en/docs/http/load_balancing.html#nginx_load_balancing_with_ip_hash
+[nginx-websocket-proxying]: https://nginx.org/en/docs/http/websocket.html
+[img-cannot-fetch-logs]: /img/clusters/cannot-fetch-logs.png
+[img-cannot-remote-exec]: /img/clusters/cannot-remote-exec.png
+[img-chrome-pending]: /img/clusters/chrome-pending.png
+[img-chrome-timeout]: /img/clusters/chrome-timeout.png
+[img-firefox-pending]: /img/clusters/firefox-pending.png
+[img-firefox-timeout]: /img/clusters/firefox-timeout.png
+[img-safari-pending]: /img/clusters/safari-pending.png
+[img-safari-timeout]: /img/clusters/safari-timeout.png
diff --git a/content/nomad/v1.10.x/content/docs/deploy/index.mdx b/content/nomad/v1.10.x/content/docs/deploy/index.mdx
new file mode 100644
index 0000000000..236977daab
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Install Nomad
+description: |-
+  Learn how to install Nomad on Linux, Mac, and Windows. Review Linux post-installation steps such as installing Container Network Interface (CNI) reference plugins, the consul-cni plugin, and the dmidecode tool. Configure bridge network traffic to route through iptables and verify cgroup controllers. Learn how to compile a Nomad binary from source code.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager addrepo --from-repofile=https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Install dmidecode
+
+When running on a virtualized host such as Amazon EC2, Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions
+require installing the dmidecode package manually.
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+
+## Verify the installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.10.x/content/docs/deploy/nomad-agent.mdx b/content/nomad/v1.10.x/content/docs/deploy/nomad-agent.mdx
new file mode 100644
index 0000000000..408151bce8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/nomad-agent.mdx
@@ -0,0 +1,192 @@
+---
+layout: docs
+page_title: Operate a Nomad agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operate a Nomad agent
+
+A Nomad agent is a long running process that runs on every machine in your Nomad
+cluster. The behavior of the agent depends on if it is running in client or
+server mode. Clients run tasks, while servers manage the cluster.
+
+Server agents are part of the [consensus protocol](/nomad/docs/architecture/cluster/consensus) and
+[gossip protocol](/nomad/docs/architecture/security/gossip). The consensus protocol, powered
+by Raft, lets the servers perform leader election and state replication.
+The gossip protocol allows for server clustering and multi-region federation.
+The higher burden on the server nodes means that you should run them on
+dedicated instances because the servers are more resource intensive than a
+client node.
+
+Client agents use fingerprinting to determine the capabilities and resources of
+the host machine, as well as what [drivers](/nomad/docs/job-declare/task-driver) are available.
+Clients register with servers to provide node information and a heartbeat.
+Clients run tasks that the server assigns to them. Client nodes make up the
+majority of the cluster and are very lightweight. They interface with the server
+nodes and maintain very little state of their own. Each cluster has usually 3 or
+5 server agents and potentially thousands of clients.
+
+## Run an agent
+
+Start the agent with the [`nomad agent` command](/nomad/commands/agent).
+This command blocks, running forever or until told to quit. The `nomad agent`
+command takes a variety of configuration options, but most have sane defaults.
+
+<Note title="Linux Users">
+
+You must run client agents as root, or with `sudo`, so that cpuset accounting
+and network namespaces work correctly.
+
+</Note>
+
+This example starts the agent in development mode, which means the agents runs
+as both the server and the client. Do not use `-dev` in a production environment.
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+The `nomad agent` command outputs the following important information:
+
+- **Client**: This indicates whether the agent is running as a client.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Nomad logs only
+  messages with an equal or higher severity.You may turn change the log level to
+  increase verbosity for debugging or reduce to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent runs. Nomad
+  has first-class support for multi-datacenter and multi-region configurations.
+  Use the `-region` and `-dc` flags to set the region and datacenter. The
+  default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent is running as a server. Server
+  nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stop an agent
+
+By default, any stop signal, such as interrupt or terminate, causes the
+agent to exit after ensuring its internal state is written to disk as
+needed. You can configure additional behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when you set `leave_on_interrupt` or `leave_on_terminate`, the
+servers notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there is a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, use the [`server
+force-leave` command][] to eject that server from the consensus peer set.
+
+For clients, when you set `leave_on_interrupt` or `leave_on_terminate` and the
+client is configured with [`drain_on_shutdown`][], the client drains its
+workloads before shutting down.
+
+## Signal handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in the [Stop an agent
+section](#stop-an-agent), Nomad supports special behavior for several other
+signals useful for debugging.
+
+* `SIGHUP` causes Nomad to [reload its configuration][].
+* `SIGUSR1` causes Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime. These the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`.
+
+This example outputs the Nomad agent's metrics.
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent starts, it fingerprints the host machine to identify its
+attributes, capabilities, and [task drivers](/nomad/docs/job-declare/task-driver). The client
+then reports this information to the servers during an initial registration. You
+provide the addresses of known servers to the agent via configuration,
+potentially using DNS for resolution. Use [Consul](https://www.consul.io/)
+to avoid hard coding addresses and instead resolve them on demand.
+
+While a client is running, it sends heartbeats to servers to maintain liveness.
+If the heartbeats fail, the servers assume the client node has failed. The
+server then stops assigning new tasks and migrates existing tasks. It is
+impossible to distinguish between a network failure and an agent crash, so Nomad
+handles both
+cases in the same way. Once the network recovers or a crashed agent
+restarts, Nomad updates the node status and resumes normal operation.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours, Nomad garbage collects that node.
+
+Servers are slightly more complex since they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/architecture/security/gossip) both to cluster
+within a region and to support multi-region configurations. When a server starts, it does not know the address of other servers in the cluster.
+To discover its peers, it must join the cluster. You do this with the
+[`server join` command](/nomad/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server leaves, it specifies its intent to do so, and the cluster marks
+that node as having left the cluster. If the server has left, replication to it
+stops, and it is removed from the consensus peer set. If the server has failed,
+replication attempts to make progress to recover from a software or network
+failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Run Nomad servers with the lowest possible permissions. The servers
+need access to their own data directory and the ability to bind to their ports.
+You should create a `nomad` user with the minimal set of required privileges.
+
+Run Nomad clients as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, you must do careful testing to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/commands/server/force-leave
+[consensus]: /nomad/docs/architecture/cluster/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/reference/metrics
diff --git a/content/nomad/v1.10.x/content/docs/deploy/production/index.mdx b/content/nomad/v1.10.x/content/docs/deploy/production/index.mdx
new file mode 100644
index 0000000000..8c9d995544
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/production/index.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: Deploy Nomad in a production environment
+description: |-
+  This page contains a high-level overview of Nomad production deployment and links review hardware requirements, reference architecture, a deployment guide, and configuration documentation.
+---
+
+# Deploy Nomad in a production environment
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the reference architecture and installation guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify hardware requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/deploy/production/requirements).
+
+## Install Nomad
+
+Visit the [Install Nomad](/nomad/docs/deploy) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad servers and clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/deploy/nomad-agent)
+and [Nomad Agent documentation](/nomad/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/docs/deploy/production/reference-architecture
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.10.x/content/docs/deploy/production/reference-architecture.mdx b/content/nomad/v1.10.x/content/docs/deploy/production/reference-architecture.mdx
new file mode 100644
index 0000000000..7a0e9e165a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/production/reference-architecture.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: Production reference architecture
+description: |-
+  Review the recommended compute and networking resources for provisioning a Nomad Enterprise cluster in a production environment.
+---
+
+# Production reference architecture
+
+This document provides recommended practices and a reference architecture for
+Nomad production deployments. This reference architecture conveys a general
+architecture that should be adapted to accommodate the specific needs of each
+implementation.
+
+The following topics are addressed:
+
+- [Reference Architecture](#ra)
+- [Deployment Topology within a Single Region](#one-region)
+- [Deployment Topology across Multiple Regions](#multi-region)
+- [Network Connectivity Details](#net)
+- [Deployment System Requirements](#system-reqs)
+- [High Availability](#high-availability)
+- [Failure Scenarios](#failure-scenarios)
+
+<!-- vale Google.We = NO -->
+
+This document describes deploying a Nomad cluster in combination with, or with
+access to, a [Consul cluster][]. We recommend the use of Consul with Nomad to
+provide automatic clustering, service discovery, health checking and dynamic
+configuration.
+
+<a name="ra"></a>
+
+## Reference architecture
+
+A Nomad cluster typically comprises three or five servers (but no more than
+seven) and a number of client agents. Nomad differs slightly from Consul in
+that it divides infrastructure into [regions][glossary-regions] which are
+served by one Nomad server cluster, but can manage multiple
+[datacenters][glossary-dc] or availability zones. For example, a _US Region_
+can include datacenters _us-east-1_ and _us-west-2_.
+
+In a Nomad multi-region architecture, communication happens via [WAN gossip][].
+Additionally, Nomad can integrate easily with Consul to provide features such as
+automatic clustering, service discovery, and dynamic configurations. Thus we
+recommend you use Consul in your Nomad deployment to simplify the deployment.
+
+<!-- vale Google.We = YES -->
+
+In cloud environments, a single cluster may be deployed across multiple
+availability zones. For example, in AWS each Nomad server can be deployed to an
+associated EC2 instance, and those EC2 instances distributed across multiple
+AZs. Similarly, Nomad server clusters can be deployed to multiple cloud regions
+to allow for region level HA scenarios.
+
+For more information on Nomad server cluster design, see the [cluster
+requirements documentation][requirements].
+
+The design shared in this document is the recommended architecture for
+production environments, as it provides flexibility and resilience. Nomad
+utilizes an existing Consul server cluster; however, the deployment design of
+the Consul server cluster is outside the scope of this document.
+
+Nomad to Consul connectivity is over HTTP and should be secured with TLS as well as a Consul
+token to provide encryption of all traffic. This is done using Nomad's
+[Automatic Clustering with Consul][consul-clustering].
+
+<a name="one-region"></a>
+
+### Deployment topology within a single region
+
+A single Nomad cluster is recommended for applications deployed in the same region.
+
+Each cluster is expected to have either three or five servers.
+This strikes a balance between availability in the case of failure and
+performance, as [Raft][] consensus gets progressively
+slower as more servers are added.
+
+The time taken by a new server to join an existing large cluster may increase as
+the size of the cluster increases.
+
+#### Reference diagram
+
+[![Reference diagram][img-reference-diagram]][img-reference-diagram]
+
+<a name="multi-region"></a>
+
+### Deployment topology across multiple regions
+
+By deploying Nomad server clusters in multiple regions, the user is able to
+interact with the Nomad servers by targeting any region from any Nomad server
+even if that server resides in a separate region. However, most data is not
+replicated between regions as they are fully independent clusters. The
+exceptions which _are_ replicated between regions are:
+
+- [ACL policies and global tokens][acl]
+- [Sentinel policies in Nomad Enterprise][sentinel]
+
+Nomad server clusters in different datacenters can be federated using WAN links.
+The server clusters can be joined to communicate over the WAN on port `4648`.
+This same port is used for single datacenter deployments over LAN as well.
+
+Additional documentation is available to learn more about Nomad cluster
+[federation][].
+
+<a name="net"></a>
+
+## Network connectivity details
+
+[![Nomad network diagram][img-nomad-net]][img-nomad-net]
+
+Nomad servers are expected to be able to communicate in high bandwidth, low
+latency network environments and have below 10 millisecond latencies between
+cluster members. Nomad servers can be spread across cloud regions or datacenters
+if they satisfy these latency requirements.
+
+Nomad client clusters require the ability to receive traffic as noted in
+the Network Connectivity Details; however, clients can be separated into any
+type of infrastructure (multi-cloud, on-prem, virtual, bare metal, etc.) as long
+as they are reachable and can receive job requests from the Nomad servers.
+
+Additional documentation is available to learn more about [Nomad networking][].
+
+<a name="system-reqs"></a>
+
+## Deployment system requirements
+
+Nomad server agents are responsible for maintaining the cluster state,
+responding to RPC queries (read operations), and for processing all write
+operations. Given that Nomad server agents do most of the heavy lifting, server
+sizing is critical for the overall performance efficiency and health of the
+Nomad cluster.
+
+### Nomad servers
+
+<!-- vale Vale.Spelling = NO --> <!-- vale Google.Colons = NO --> <!-- vale Google.WordList = NO -->
+
+| Type  | CPU       | Memory            | Disk        | Typical Cloud Instance Types               |
+| ----- | --------- | ----------------- | ----------- | ------------------------------------------ |
+| Small | 2-4 core  | 8-16&nbsp;GB RAM  | 50&nbsp;GB  | **AWS**: m5.large, m5.xlarge               |
+|       |           |                   |             | **Azure**: Standard_D2_v3, Standard_D4_v3  |
+|       |           |                   |             | **GCP**: n2-standard-2, n2-standard-4      |
+| Large | 8-16 core | 32-64&nbsp;GB RAM | 100&nbsp;GB | **AWS**: m5.2xlarge, m5.4xlarge            |
+|       |           |                   |             | **Azure**: Standard_D8_v3, Standard_D16_v3 |
+|       |           |                   |             | **GCP**: n2-standard-8, n2-standard-16     |
+
+<!-- vale Vale.Spelling = YES --> <!-- Google.Colons = YES --> <!-- vale Google.WordList = YES -->
+
+#### Hardware sizing considerations
+
+- The small size would be appropriate for most initial production
+  deployments, or for development/testing environments.
+
+- The large size is for production environments where there is a
+  consistently high workload.
+
+<Note>
+
+ For large workloads, ensure that the disks support a high number of
+IOPS to keep up with the rapid Raft log update rate.
+
+</Note>
+
+Nomad clients can be setup with specialized workloads as well. For example, if
+workloads require GPU processing, a Nomad datacenter can be created to serve
+those GPU specific jobs and joined to a Nomad server cluster. For more
+information on specialized workloads, see the documentation on [job
+constraints][] to target specific client nodes.
+
+## High availability
+
+A Nomad server cluster is the highly available unit of deployment within a
+single datacenter. A recommended approach is to deploy a three or five node
+Nomad server cluster. With this configuration, during a Nomad server outage,
+failover is handled immediately without human intervention.
+
+When setting up high availability across regions, multiple Nomad server clusters
+are deployed and connected via WAN gossip. Nomad clusters in regions are fully
+independent from each other and do not share jobs, clients, or state. Data
+residing in a single region-specific cluster is not replicated to other clusters
+in other regions.
+
+## Failure scenarios
+
+Typical distribution in a cloud environment is to spread Nomad server nodes into
+separate Availability Zones (AZs) within a high bandwidth, low latency network,
+such as an AWS Region. The diagram below shows Nomad servers deployed in
+multiple AZs promoting a single voting member per AZ and providing both AZ-level
+and node-level failure protection.
+
+[![Nomad fault tolerance][img-fault-tolerance]][img-fault-tolerance]
+
+Additional documentation is available to learn more about [cluster sizing and
+failure tolerances][sizing] as well as [outage recovery][].
+
+### Availability zone failure
+
+In the event of a single AZ failure, only a single Nomad server is affected
+which would not impact job scheduling as long as there is still a Raft quorum
+(that is, 2 available servers in a 3 server cluster, 3 available servers in a 5
+server cluster, more generally:
+
+<div align="center">quorum = floor( count(members) / 2) + 1</div>
+
+There are two scenarios that could occur should an AZ fail in a multiple AZ
+setup: leader loss or follower loss.
+
+#### Leader server loss
+
+If the AZ containing the Nomad leader server fails, the remaining quorum members
+would elect a new leader. The new leader then begins to accept new log entries and
+replicates these entries to the remaining followers.
+
+#### Follower server loss
+
+If the AZ containing a Nomad follower server fails, there is no immediate impact
+to the Nomad leader server or cluster operations. However, there still must be a
+Raft quorum in order to properly manage a future failure of the Nomad leader
+server.
+
+### Region failure
+
+In the event of a region-level failure (which would contain an entire Nomad
+server cluster), clients are still able to submit jobs to another region
+that is properly federated. However, data loss is likely as Nomad
+server clusters do not replicate their data to other region clusters. See
+[Multi-region Federation][federation] for more setup information.
+
+## Next steps
+
+Read [Deployment Guide][deployment-guide] to learn the steps required to
+install and configure a single HashiCorp Nomad cluster that uses Consul.
+
+[acl]: /nomad/secure/acl/bootstrap
+[consul cluster]: /nomad/docs/networking/consul
+[deployment-guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
+[img-fault-tolerance]: /img/deploy/nomad_fault_tolerance.png
+[img-nomad-net]: /img/deploy/nomad_network_arch_0-1x.png
+[img-reference-diagram]: /img/deploy/nomad_reference_diagram.png
+[job constraints]: /nomad/docs/job-specification/constraint
+[federation]: /nomad/docs/deploy/clusters/federate-regions
+[nomad networking]: /nomad/docs/deploy/production/requirements#network-topology
+[nomad server federation]: /nomad/docs/deploy/clusters/federate-regions
+[outage recovery]: /nomad/docs/manage/outage-recovery
+[raft]: https://raft.github.io/
+[requirements]: /nomad/docs/deploy/production/requirements
+[sentinel]: /nomad/docs/govern/sentinel
+[sizing]: /nomad/docs/architecture/cluster/consensus#deployment_table
+[wan gossip]: /nomad/docs/architecture/security/gossip
+[consul-clustering]: /nomad/docs/deploy/clusters/connect-nodes
+[glossary-regions]: /nomad/docs/glossary#regions
+[glossary-dc]: /nomad/docs/glossary#datacenters
diff --git a/content/nomad/v1.10.x/content/docs/deploy/production/requirements.mdx b/content/nomad/v1.10.x/content/docs/deploy/production/requirements.mdx
new file mode 100644
index 0000000000..66e561ff17
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/production/requirements.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: Nomad installation requirements
+description: |-
+  Learn about the hardware and networking resources that Nomad requires. Review RAM, CPU, network topology and ports, user permissions, and Linux capabilities.
+---
+
+# Nomad installation requirements
+
+This page contains an overview of the hardware and networking resources that
+Nomad requires. Review RAM, CPU, network topology and ports, user
+permissions, and Linux capabilities.
+
+## Resources
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publicly routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/architecture/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/commands/job/plan
+[`nomad fmt`]: /nomad/commands/fmt
+[mTLS]: /nomad/docs/secure/traffic/tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrate
diff --git a/content/nomad/v1.10.x/content/docs/deploy/production/windows-service.mdx b/content/nomad/v1.10.x/content/docs/deploy/production/windows-service.mdx
new file mode 100644
index 0000000000..a56c7ab562
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/production/windows-service.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Install Nomad as a Windows service
+description: |-
+  Learn how to run Nomad as a Windows service. Register Nomad with the Windows Service Control Manager. Configure Nomad to log to file, and increase the non-interactive desktop heap size.
+---
+
+# Install Nomad as a Windows service
+
+You may run Nomad as a native Windows service. Use the [windows service install][]
+command to install Nomad and create the Windows service.
+
+You may also set up the Nomad Windows service manually. Use [`sc.exe`] to register
+the Nomad application with the Windows Service Control Manager, configure Nomad to
+log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start=auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+## Increase the non-interactive desktop heap size
+
+If you run Nomad as a Windows service and you intend to run many allocations,
+such as more than 50, you may encounter issues with Windows terminating Nomad
+plugin processes with errors such as `exit status 0xc0000142` appearing in the
+logs. This is due to Nomad's inability to spawn more concurrent processes, and
+you may fix this by manipulating the value of
+`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
+Manager\SubSystems` Windows registry key.
+
+This key has a `Windows` value which in turn has a `SharedSection` parameter
+that accepts a value of three comma-separated integers, for example,
+`1024,20480,768`. The first integer indicates the maximum size of the
+system-wide heap, the second is the size of each desktop heap, and the third is
+the size of the desktop heap that is associated with a noninteractive Windows
+instance. All values are in kilobytes. For large Windows nodes that run large
+numbers of allocations, we recommend setting the final integer value to 2048 or
+4096 kB. Remember that any registry change requires restarting Windows, a
+restart of Nomad service is not sufficient.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
+[windows service install]: /nomad/docs/commands/windows/service-install
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/docker.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/docker.mdx
new file mode 100644
index 0000000000..9bb3b35b7b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/docker.mdx
@@ -0,0 +1,491 @@
+---
+layout: docs
+page_title: Configure the Docker task driver
+description: Nomad's Docker task driver lets you run Docker-based tasks in your jobs. Modify the Docker task driver plugin configuration. Learn about CPU, memory, filesystem IO, and security resource isolation as well as how Nomad handles dangling containers.
+---
+
+# Configure the Docker task driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+**Note:** If you are using Docker Desktop for Windows or MacOS, check
+[the FAQ][faq-win-mac].
+
+## Capabilities
+
+The `docker` driver implements the following capabilities:
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+Nomad clients manage a cpuset cgroup for each task to reserve or share CPU
+[cores][]. In order for Nomad to be compatible with Docker's own cgroups
+management, it must write to cgroups owned by Docker, which requires running as
+root. If Nomad is not running as root, CPU isolation and NUMA-aware scheduling
+will not function correctly for workloads with `resources.cores`, including
+workloads using task drivers other than `docker` on the same host.
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `registry.k8s.io/pause-<goarch>:3.3`. The image will only be pulled from the
+  container registry if its tag is `latest` or the image doesn't yet exist
+  locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+- `image_pull_timeout` - (Optional) A default time duration that controls how long Nomad
+  waits before cancelling an in-progress pull of the Docker image as specified
+  in `image` across all tasks. Defaults to `"5m"`.
+
+- `windows_allow_insecure_container_admin` - Indicates that on windows, docker
+  checks the `task.user` field or, if unset, the container image manifest after
+  pulling the container, to see if it's running as `ContainerAdmin`. If so, exits
+  with an error unless the task config has `privileged=true`. Defaults to `false`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/job-declare/task-driver/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad has a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+## Next steps
+
+[Use the Docker task driver in a job](/nomad/docs/job-declare/task-driver/docker).
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: /nomad/docs/job-declare/task-driver/docker#auth_soft_fail
+[cap_add]: /nomad/docs/job-declare/task-driver/docker#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/job-declare/task-driver/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/job-declare/task-driver/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/exec.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/exec.mdx
new file mode 100644
index 0000000000..58b52bee08
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/exec.mdx
@@ -0,0 +1,203 @@
+---
+layout: docs
+page_title: Configure the Isolated Fork/Exec task driver
+description: Nomad's Isolated Fork/Exec task driver lets you run binaries using OS isolation primitives. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes. Learn how the Isolated Fork/Exec task driver affects resource isolation, chroot, and CPU resources.
+---
+
+# Configure the Isolated Fork/Exec task driver
+
+Name: `exec`
+
+The `exec` driver is used to execute a particular command for a task. However,
+unlike [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec) it uses the
+underlying isolation primitives of the operating system to limit the task's
+access to resources. While simple, since the `exec` driver can invoke any
+command, it can be used to call scripts or other wrappers which provide higher
+level features.
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+## Next steps
+
+[Use the Isolated Fork/Exec task driver in a job](/nomad/docs/job-declare/task-driver/exec).
+
+[default_pid_mode]: /nomad/docs/job-declare/task-driver/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/job-declare/task-driver/exec#default_ipc_mode
+[cap_add]: /nomad/docs/job-declare/task-driver/exec#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/job-declare/task-driver/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/index.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/index.mdx
new file mode 100644
index 0000000000..1ecd37fd33
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/index.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: Configure Nomad task drivers
+description: Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, configuration, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+---
+
+# Configure Nomad task drivers
+
+Nomad's bundled task drivers integrate with the host OS to run job tasks in
+isolation. Review driver capabilities, client configuration, and reference
+information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec
+task drivers.
+
+@include 'task-driver-intro.mdx'
+
+## Configuration
+
+Refer to the [plugin block documentation][plugin] for examples on how to use the
+plugin block in Nomad's client configuration. Review the [Docker driver's client
+requirements section][docker_plugin] for a detailed example.
+
+## Nomad task drivers
+
+The Nomad binary contains several bundled task drivers. We also support
+additional task driver plugins that you may install separately.
+
+| Bundled with Nomad   | Plugins               |
+|----------------------|-----------------------|
+| [Docker]             | [Exec2]               |
+| [Isolated Fork/Exec] | [Podman]              |
+| [Java]               | [Virt]                |
+| [QEMU]               |                       |
+| [Raw Fork/Exec]      |                       |
+
+## Community task drivers
+
+You may also use [community-supported task driver
+plugins](/nomad/plugins/drivers/community/).
+
+## Use task drivers in jobs
+
+Refer to [Use Nomad task drivers in jobs](/nomad/docs/job-declare/task-driver)
+for usage information.
+
+## Create task drivers
+
+Nomad's task driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/deploy/task-driver/docker#client-requirements
+[plugin_guide]: /nomad/plugins/author/task-driver
+[Docker]: /nomad/docs/deploy/task-driver/docker
+[Exec2]: /nomad/plugins/drivers/exec2
+[Isolated Fork/Exec]: /nomad/docs/deploy/task-driver/exec
+[Podman]: /nomad/plugins/drivers/podman
+[Java]: /nomad/docs/deploy/task-driver/java
+[Virt]: /nomad/plugins/drivers/virt
+[QEMU]: /nomad/docs/deploy/task-driver/qemu
+[Raw Fork/Exec]: /nomad/docs/deploy/task-driver/raw_exec
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/java.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/java.mdx
new file mode 100644
index 0000000000..709b1523ca
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/java.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: Configure the Java task driver
+description: Nomad's Java task driver lets you run JAR files in your workloads. Review the Java task driver capabilities, plugin options, client requirements, and client attributes such as Java version and virtual machine. Learn how the Java task driver affects resource isolation and chroot.
+---
+
+# Configure the Java task driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+## Next steps
+
+[Use the Java task driver in a job](/nomad/docs/job-declare/task-driver/java).
+
+[default_pid_mode]: /nomad/docs/job-declare/task-driver/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/job-declare/task-driver/java#default_ipc_mode
+[cap_add]: /nomad/docs/job-declare/task-driver/java#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/job-declare/task-driver/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[host volume]: /nomad/docs/configuration/client#host_volume-block
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/qemu.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/qemu.mdx
new file mode 100644
index 0000000000..42d1f91eec
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/qemu.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: Configure the QEMU task driver
+description: Nomad's QEMU task driver provides a generic virtual machine runner that can execute any regular QEMU image. Review the QEMU task driver capabilities, plugin options, client requirements, and client attributes such as QEMU version. Learn how the QEMU task driver provides the highest level of workload isolation.
+---
+
+# Configure the QEMU task driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+## Next steps
+
+[Use the Java task driver in a job](/nomad/docs/job-declare/task-driver/qemu).
+
+[`args`]: /nomad/docs/job-declare/task-driver/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.10.x/content/docs/deploy/task-driver/raw_exec.mdx b/content/nomad/v1.10.x/content/docs/deploy/task-driver/raw_exec.mdx
new file mode 100644
index 0000000000..174d21505f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/deploy/task-driver/raw_exec.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Raw Fork/Exec task driver
+description: Nomad's Raw Exec task driver lets you execute commands with no resource isolation. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes.
+---
+
+# Configure the Raw Fork/Exec task driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+- `denied_envvars` - (Optional) Passes a list of environment variables that
+  the driver should scrub from all task environments. Supports globbing with "*"
+  wildcard accepted as prefix and/or suffix.
+
+```hcl
+config {
+  denied_envvars = ["AWS_SECRET_KEY", "*_TOKEN"]
+}
+```
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no filesystem isolation.
+
+If the launched process creates a new process group, it is possible that
+Nomad will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to
+manage the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, and the cgroup system is mounted.
+
+If the cluster is configured with memory oversubscription enabled, a task using
+the `raw_exec` driver can be configured to have no maximum memory limit by
+setting `memory_max = -1`.
+
+```hcl
+resources {
+  cpu        = 500
+  memory     = 128
+  memory_max = -1 # no limit
+}
+```
+
+## Next steps
+
+[Use the `raw_exec` driver in a job](/nomad/docs/job-declare/task-driver/raw_exec).
+
+[hardening]: /nomad/docs/deploy/production/requirements#user-permissions
+[service]: /nomad/docs/deploy/production/windows-service
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.10.x/content/docs/ecosystem.mdx b/content/nomad/v1.10.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..4bde196b5e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/ecosystem.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Learn about the Nomad ecosystem, which includes CI/CD, task drivers, service mesh, service proxy, secrets management, observability, autoscaling, storage, provisioning, GPUs, and cloud native support.
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/secure/vault)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/networking/consul/service-mesh)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](https://www.cni.dev/)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/networking/consul)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/architecture/storage/csi)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.10.x/content/docs/enterprise/index.mdx b/content/nomad/v1.10.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..174bcde169
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  such as resource quotas, Sentinel policies, audit logging, multi-region deployments, and advanced server management using Nomad Autopilot.
+---
+
+# Nomad Enterprise
+
+This page provides an overview of Nomad Enterprise features that
+add operations, collaboration, and governance capabilities such as resource
+quotas, Sentinel policies, audit logging, multi-region deployments, and advanced
+server management using Nomad Autopilot.
+
+Nomad Enterprise is available as a base Platform package with an optional
+Governance & Policy add-on module.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Long Term Support (LTS) Releases
+
+Nomad Enterprise initiated the Long-Term Support (LTS) release program with
+Nomad 1.8. Going forward, the first major release of each calendar year will be
+an LTS release.
+
+LTS releases have the following benefits for Nomad operators:
+
+- **Extended maintenance:** Two years of critical fixes provided through minor
+releases
+- **Efficient upgrades:** Support for direct upgrades from one LTS release
+to the next, reducing major-version upgrade risk and improving operational
+efficiency.
+
+LTS releases reduce operational overhead and risk by letting organizations
+receive critical fixes in minor releases without having to upgrade their major
+version more than once a year. Once you’ve upgraded to Nomad Enterprise 1.8,
+you will be running on a maintained LTS release that will allow you to easily
+upgrade to the next LTS major release when it's available. For more
+information, refer to HashiCorp’s multi-product LTS statement.
+
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/docs/manage/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/docs/manage/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/docs/manage/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+Refer to the [Vault Integration documentation](/nomad/docs/secure/vault/acl#vault-namespaces)) for more information.
+
+### Multiple Vault and Consul Clusters
+
+Nomad Enteprise allows sepcifying multiple integrations for Consul and Vault in
+the [vault](/nomad/docs/configuration/vault) and
+[consul](/nomad/docs/configuration/consul) portions of the Nomad agent
+configuration. After the agents are configured, Nomad jobspec writers can pick
+which Consul or Vault cluster to use in their job. Nomad administrators may
+also set default clusters for each in Nomad namespace configuration, as well as
+deny access to certain clusters by namespace.
+
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define [quota specifications](/nomad/docs/other-specifications/quota)
+and apply them to namespaces. When a quota is attached to a namespace,
+the jobs within the namespace may not consume more resources than the quota
+specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/docs/govern/resource-quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/docs/govern/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/reference/sentinel-policy
diff --git a/content/nomad/v1.10.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.10.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..6a9ae7cc17
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Nomad Enterprise License FAQ
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/commands/license/inspect
diff --git a/content/nomad/v1.10.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.10.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..d335265b51
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn how to configure, apply, and replace your Nomad Enterprise license. Use the `nomad license` command to review your license details.
+---
+
+# Nomad Enterprise Licensing
+
+<EnterpriseAlert product="nomad"/>
+
+This page provides information on how to configure, apply, inspect, and replace
+your Nomad Enterprise license.
+
+Each server in a Nomad Enterprise cluster must have a license to start. Download
+Nomad Enterprise from the [releases site].
+
+[Contact sales](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo
+of Nomad Enterprise.
+
+Refer to the Enterprise license
+[tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) for
+step-by-step license instructions. Review the [Request a trial license section
+](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.10.x/content/docs/enterprise/license/utilization-reporting.mdx b/content/nomad/v1.10.x/content/docs/enterprise/license/utilization-reporting.mdx
new file mode 100644
index 0000000000..8a1f883254
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/enterprise/license/utilization-reporting.mdx
@@ -0,0 +1,345 @@
+---
+layout: docs
+page_title: Automated license utilization reporting
+description: >-
+  Learn what data HashiCorp collects to monitor Enterprise product usage and license utilization. Enable or opt out of automatic reporting. Review sample payloads and logs.
+---
+
+# Automated license utilization reporting
+
+<EnterpriseAlert product="nomad" />
+
+This page provides information on the data HashiCorp collects to monitor
+Enterprise product usage and license utilization. Learn how to enable or
+opt out of automatic reporting. Review sample payloads and logs.
+
+## Introduction
+
+Automated reporting sends product and license utilization data to HashiCorp without
+requiring you to manually collect and report them.
+
+It shares data required to validate license utilization as defined in our contracts.
+The detailed product usage metrics also inform our feature roadmap. They consist of computed
+metrics and never contain Personal Identifiable Information (PII) or other sensitive information,
+which you can verify by reviewing the full [list of metrics](#full-list-of-metrics).
+Inform your account manager if you have concerns with any of the data.
+
+Automated reporting shares the data with HashiCorp using a secure, unidirectional HTTPS API and makes
+an auditable record in the product logs each time it submits a report. The reporting process is GDPR
+compliant and submits reports roughly once every 24 hours.
+
+## Enable automated reporting
+
+To enable automated reporting, you need to make sure that outbound network traffic is configured correctly
+and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or
+network settings are not in place, automated reporting will not work.
+
+### 1. Allow outbound HTTPS traffic on port 443
+
+Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by
+allow-listing the following IP addresses:
+
+- 100.20.70.12
+- 35.166.5.222
+- 23.95.85.111
+- 44.215.244.1
+
+### 2. Upgrade
+
+Upgrade to a release that supports license utilization reporting. These releases include:
+- [Nomad v1.7.0](/nomad/downloads) and later
+
+### 3. Check logs
+
+Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product
+logs for records that the data sent successfully.
+
+Instructions on how to check logs.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: recording audit record
+[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
+[DEBUG] completed recording audit record
+[DEBUG] core.reporting: export finished successfully
+```
+
+If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an
+error.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: error status code received: statusCode=403
+```
+
+In this case, reconfigure your network to allow egress and check back in 24 hours.
+
+## Opt out
+
+If your installation is air-gapped or you want to manually collect and report on the same license
+utilization metrics, you can opt-out of automated reporting.
+
+Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that
+you also opt out from sending license utilization metrics. Customers who opt out of automated reporting are
+still required to manually collect and send license utilization metrics to HashiCorp by using the
+[`nomad operator utilization`](/nomad/commands/operator/utilization) command.
+
+You may disable product usage metrics separately from license utilization reporting, so your
+automated license reporting can exclude product usage metrics, or you can include product usage
+metrics in offline reports.
+
+You have two ways to opt out of automated reporting: HCL configuration or environment variables.
+
+For HCL configuration, use the [`reporting`](/nomad/docs/configuration/reporting) block
+in your Nomad server agent config file.
+
+```hcl
+reporting {
+  license {
+    enabled = false
+  }
+}
+```
+
+The `reporting.license.enabled` option toggles automated reporting.
+Nomad still gathers license utilization data for manual reporting.
+
+To disable detailed product usage metrics for both automated and offline reporting,
+use the `reporting.disable_product_usage_reporting` option.
+
+```hcl
+reporting {
+  disable_product_usage_reporting = true
+}
+```
+
+Alternatively, you can use the following environment variables in your Nomad server agent's environment.
+
+```shell
+export OPTOUT_LICENSE_REPORTING=true
+export OPTOUT_PRODUCT_USAGE_REPORTING=true
+```
+
+If your configuration file and environment variable differ, the environment variable takes precedence.
+
+After changing configuration, follow the ["Run an agent"
+instructions](/nomad/docs/deploy/nomad-agentt#run-an-agent)
+to restart your Nomad server and apply your changes.
+
+The Nomad agent emits logs at startup confirming your settings. This example shows
+automated reporting enabled, but without product usage metrics.
+
+```
+[INFO]  nomad.reporting: reporting agent is enabled and configured
+[DEBUG] nomad.reporting: product usage reporting disabled via agent configuration
+[INFO]  nomad.reporting: product usage reporting is disabled; usage metrics data will not be collected
+```
+
+You can also check your product logs roughly 24 hours after opting out to make sure that the
+system isn’t trying to send reports, or that the detailed usage metrics are all reporting `0`.
+
+## Full list of metrics
+
+This table lists all the metrics that we collect.
+
+Only `nomad.billable.*` metrics are collected if product usage metrics are disabled.
+
+The values are all integers for pre-determined values. We do not collect any strings
+that might identify proprietary information.
+
+<!-- NOTE to maintainers: Generate this table with a CLI tool in the registry repo
+     https://github.com/hashicorp/hashicorp-census-registry/tree/main/nomad/v2/cmd
+-->
+
+| Key                                       | Description                                               |
+|-------------------------------------------|-----------------------------------------------------------|
+| acl.auth.method.count                     | ACL Auth Methods                                          |
+| acl.auth.method.jwt.count                 | ACL Auth Methods of type JWT                              |
+| acl.auth.method.oidc.count                | ACL Auth Methods of type OIDC                             |
+| acl.policy.count                          | ACL policies                                              |
+| acl.role.count                            | ACL roles                                                 |
+| acl.token.count                           | ACL tokens                                                |
+| alloc.count                               | All allocations                                           |
+| alloc.status.complete.count               | Allocations with client status "complete"                 |
+| alloc.status.failed.count                 | Allocations with client status "failed"                   |
+| alloc.status.lost.count                   | Allocations with client status "lost"                     |
+| alloc.status.pending.count                | Allocations with client status "pending"                  |
+| alloc.status.running.count                | Allocations with client status "running"                  |
+| alloc.status.unknown.count                | Allocations with client status "unknown"                  |
+| alloc.task.count                          | All tasks in allocations                                  |
+| alloc.task.running.count                  | Running tasks in allocations                              |
+| client.count                              | Client nodes in the cluster                               |
+| client.driver.docker.count                | Clients with the "docker" driver                          |
+| client.driver.exec.count                  | Clients with the "exec" driver                            |
+| client.driver.exec2.count                 | Clients with the "exec2" driver                           |
+| client.driver.java.count                  | Clients with the "java" driver                            |
+| client.driver.nomad-driver-virt.count     | Clients with the "nomad-driver-virt" driver               |
+| client.driver.other.count                 | Clients with some other driver                            |
+| client.driver.pledge.count                | Clients with the "pledge" driver                          |
+| client.driver.podman.count                | Clients with the "podman" driver                          |
+| client.driver.qemu.count                  | Clients with the "qemu" driver                            |
+| client.driver.raw_exec.count              | Clients with the "raw_exec" driver                        |
+| client.plugin.cni.unique.count            | Unique CNI plugins on client nodes                        |
+| client.plugin.driver.unique.count         | Unique task drivers on client nodes                       |
+| client.plugin.host_volume.unique.count    | Unique host volume plugins on client nodes                |
+| client.plugin.secret.unique.count         | Unique secret plugins on client nodes                     |
+| client.resources.compute                  | Total client compute                                      |
+| client.resources.core.count               | Total client CPU cores                                    |
+| client.resources.memory                   | Total client memory in MB                                 |
+| client.vault.enabled.count                | Clients with Vault enabled                                |
+| job.count                                 | All jobs                                                  |
+| job.driver.docker.count                   | Jobs with the "docker" driver                             |
+| job.driver.exec.count                     | Jobs with the "exec" driver                               |
+| job.driver.exec2.count                    | Jobs with the "exec2" driver                              |
+| job.driver.java.count                     | Jobs with the "java" driver                               |
+| job.driver.nomad-driver-virt.count        | Jobs with the "nomad-driver-virt" driver                  |
+| job.driver.other.count                    | Jobs with some other driver                               |
+| job.driver.pledge.count                   | Jobs with the "pledge" driver                             |
+| job.driver.podman.count                   | Jobs with the "podman" driver                             |
+| job.driver.qemu.count                     | Jobs with the "qemu" driver                               |
+| job.driver.raw_exec.count                 | Jobs with the "raw_exec" driver                           |
+| job.group.count                           | Task groups in jobs                                       |
+| job.network.cni.args.count                | Networks in jobs with custom CNI args                     |
+| job.network.mode.bridge.count             | Networks in jobs with mode "bridge"                       |
+| job.network.mode.cni.count                | Networks in jobs with mode "cni"                          |
+| job.network.mode.host.count               | Networks in jobs with mode "host"                         |
+| job.network.mode.other.count              | Networks in jobs with some other mode                     |
+| job.parameterized.count                   | Parameterized jobs                                        |
+| job.parameterized.dispatched.count        | Dispatched parameterized jobs                             |
+| job.periodic.count                        | Periodic jobs                                             |
+| job.periodic.dispatched.count             | Dispatched periodic jobs                                  |
+| job.service.consul.connect.count          | Connect services in jobs                                  |
+| job.service.consul.count                  | Consul services in jobs                                   |
+| job.service.nomad.count                   | Nomad provider services in jobs                           |
+| job.task.identity.count                   | Tasks in jobs with identity enabled                       |
+| job.task.template.count                   | Tasks in jobs with templates                              |
+| job.task.vault.count                      | Tasks in jobs with Vault enabled                          |
+| job.type.batch.count                      | Jobs of type "batch"                                      |
+| job.type.service.count                    | Jobs of type "service"                                    |
+| job.type.sysbatch.count                   | Jobs of type "sysbatch"                                   |
+| job.type.system.count                     | Jobs of type "system"                                     |
+| job.volume.csi.count                      | CSI volumes in jobs                                       |
+| job.volume.host.count                     | Host volumes in jobs                                      |
+| job.volume.sticky.count                   | Sticky volumes in jobs                                    |
+| namespace.count                           | Namespaces                                                |
+| namespace.quotas.count                    | Quotas                                                    |
+| node.cpu.arch.amd64.count                 | Clients with "amd64" CPU architecture                     |
+| node.cpu.arch.arm64.count                 | Clients with "arm64" CPU architecture                     |
+| node.cpu.arch.other.count                 | Clients with some other CPU architecture                  |
+| node.cpu.arch.s390x.count                 | Clients with "s390x" CPU architecture                     |
+| node.cpu.arch.unique.count                | Unique CPU architectures on client nodes                  |
+| node.kernel.name.aix.count                | Clients with "aix" kernel                                 |
+| node.kernel.name.darwin.count             | Clients with "darwin" kernel                              |
+| node.kernel.name.freebsd.count            | Clients with "freebsd" kernel                             |
+| node.kernel.name.linux.count              | Clients with "linux" kernel                               |
+| node.kernel.name.other.count              | Clients with some other kernel                            |
+| node.kernel.name.plan9.count              | Clients with "plan9" kernel                               |
+| node.kernel.name.solaris.count            | Clients with "solaris" kernel                             |
+| node.kernel.name.unique.count             | Unique kernels on client nodes                            |
+| node.os.name.alpine.count                 | Clients with "alpine" operating system                    |
+| node.os.name.amazon.count                 | Clients with "amazon" operating system                    |
+| node.os.name.arch.count                   | Clients with "arch" operating system                      |
+| node.os.name.centos.count                 | Clients with "centos" operating system                    |
+| node.os.name.cloudlinux.count             | Clients with "cloudlinux" operating system                |
+| node.os.name.coreos.count                 | Clients with "coreos" operating system                    |
+| node.os.name.darwin.count                 | Clients with "darwin" operating system                    |
+| node.os.name.debian.count                 | Clients with "debian" operating system                    |
+| node.os.name.fedora.count                 | Clients with "fedora" operating system                    |
+| node.os.name.gentoo.count                 | Clients with "gentoo" operating system                    |
+| node.os.name.opensuse.count               | Clients with "opensuse" operating system                  |
+| node.os.name.oracle.count                 | Clients with "oracle" operating system                    |
+| node.os.name.other.count                  | Clients with some other operating system                  |
+| node.os.name.raspbian.count               | Clients with "raspbian" operating system                  |
+| node.os.name.redhat.count                 | Clients with "redhat" operating system                    |
+| node.os.name.suse.count                   | Clients with "suse" operating system                      |
+| node.os.name.ubuntu.count                 | Clients with "ubuntu" operating system                    |
+| node.os.name.unique.count                 | Unique operating systems on client nodes                  |
+| node.os.name.windows.count                | Clients with "windows" operating system                   |
+| node.pool.count                           | Node pools                                                |
+| node.status.disconnected.count            | Clients with status "disconnected"                        |
+| node.status.down.count                    | Clients with status "down"                                |
+| node.status.initializing.count            | Clients with status "initializing"                        |
+| node.status.ready.count                   | Clients with status "ready"                               |
+| node.status.unknown.count                 | Clients with status "unknown"                             |
+| nomad.billable.clients                    | Number of client nodes in the cluster                     |
+| nomad.billable.cores.s390x                | Active client s390x CPU cores in the cluster              |
+| nomad.billable.cores.total                | Active client CPU cores in the cluster                    |
+| plugin.csi.unique.count                   | Unique CSI plugins                                        |
+| policy.sentinel.count                     | Sentinel policies                                         |
+| sentinel.enforcement.advisory.count       | Sentinel policies with "advisory" enforcement level       |
+| sentinel.enforcement.hard-mandatory.count | Sentinel policies with "hard-mandatory" enforcement level |
+| sentinel.enforcement.soft-mandatory.count | Sentinel policies with "soft-mandatory" enforcement level |
+| sentinel.scope.submit-csi-volume.count    | Sentinel policies with "submit-csi-volume" scope          |
+| sentinel.scope.submit-host-volume.count   | Sentinel policies with "submit-host-volume" scope         |
+| sentinel.scope.submit-job.count           | Sentinel policies with "submit-job" scope                 |
+| task.driver.docker.count                  | Tasks with the "docker" driver                            |
+| task.driver.exec.count                    | Tasks with the "exec" driver                              |
+| task.driver.exec2.count                   | Tasks with the "exec2" driver                             |
+| task.driver.java.count                    | Tasks with the "java" driver                              |
+| task.driver.nomad-driver-virt.count       | Tasks with the "nomad-driver-virt" driver                 |
+| task.driver.other.count                   | Tasks with some other driver                              |
+| task.driver.pledge.count                  | Tasks with the "pledge" driver                            |
+| task.driver.podman.count                  | Tasks with the "podman" driver                            |
+| task.driver.qemu.count                    | Tasks with the "qemu" driver                              |
+| task.driver.raw_exec.count                | Tasks with the "raw_exec" driver                          |
+| variable.count                            | Nomad Variables                                           |
+| variable.lock.count                       | Nomad Variable Locks                                      |
+| volume.csi.capacity                       | Capacity of all CSI volumes in MB                         |
+| volume.csi.count                          | Number of "csi" volumes                                   |
+| volume.dhv.capacity                       | Capacity of all dynamic host volumes in MB                |
+| volume.dhv.plugin.other.count             | Dynamic host volumes with non-standard plugins            |
+| volume.dynamic.count                      | Number of "dynamic" volumes                               |
+| volume.static.count                       | Number of "static" volumes                                |
+
+
+## Example payload
+
+HashiCorp collects utilization data in the following JSON format.
+
+```json
+{
+  "version": "2",
+  "mode": "manual",
+  "timestamp": "2025-09-26T17:20:41.189292719Z",
+  "signature": "...",
+  "checksum": ...,
+  "snapshots": [
+    {
+      "snapshot_version": 2,
+      "id": "0001MDDJT442VWX01R4K21A22D",
+      "timestamp": "2025-09-26T13:20:04.598859749-04:00",
+      "schema_version": "2.1.0",
+      "product": "nomad",
+      "process_id": "01K63GH92XVS1V95RM7509N303",
+      "metrics": {
+        ...
+        "nomad.billable.clients": {
+          "key": "nomad.billable.clients",
+          "value": 25,
+          "mode": "write"
+        },
+        ...
+      },
+      "product_version": "1.10.6",
+      "license_id": "...",
+      "checksum": ...,
+      "metadata": {}
+    }
+  ]
+}
+```
+
+You can inspect the full payload in the server logs, or by running the
+[`nomad operator utilization`](/nomad/commands/operator/utilization) command.
diff --git a/content/nomad/v1.10.x/content/docs/faq.mdx b/content/nomad/v1.10.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..0b45423b3b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Nomad frequently asked question topics include checkpoint, gossip and consensus protocols, Nomad datacenter versus Consul datacenter, bootstrapping a cluster, and connecting to a host network with Docker Desktop.
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/architecture/cluster/consensus) and
+a [gossip protocol](/nomad/docs/architecture/security/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.10.x/content/docs/glossary.mdx b/content/nomad/v1.10.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..a86a5517e2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Nomad key concepts include allocation, authoritative regions, bin packing, client, datacenters, deployment, driver, evaluation, job, node, node pool, regions, server, task, and task group.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/deploy/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.10.x/content/docs/govern/index.mdx b/content/nomad/v1.10.x/content/docs/govern/index.mdx
new file mode 100644
index 0000000000..076c490f63
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/govern/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: Governance and policy on Nomad
+description: |-
+  This section provides best practices and guidance for operating Nomad securely in a multi-team setting through features such as resource quotas, node pools, and Sentinel policies.
+---
+
+# Governance and policy on Nomad
+
+Nomad Enterprise is aimed at teams and organizations and addresses the organizational complexity of multi-team and multi-cluster deployments with collaboration and governance features.
+
+This section provides best practices and guidance for operating Nomad
+securely in a multi-team setting through features such as resource quotas, node
+pools, and Sentinel policies.
+
+## Resource quotas
+
+<EnterpriseAlert inline />
+
+When many teams or users
+are sharing Nomad clusters, there is the concern that a single user could use
+more than their fair share of resources. Resource quotas provide a mechanism for
+cluster administrators to restrict the resources within a namespace.
+
+Quota specifications are first class objects in Nomad. A quota specification
+has a unique name, an optional human readable description, and a set of quota
+limits. The quota limits define the allowed resource usage within a region.
+
+Quota objects are shareable among namespaces. This allows an operator to define
+higher level quota specifications, such as a `prod-api` quota, and multiple
+namespaces can apply the `prod-api` quota specification.
+
+## Sentinel
+
+<EnterpriseAlert inline />
+
+[![Sentinel Overview][img_sentinel_overview]][img_sentinel_overview]
+
+- **Sentinel Policies** - Policies are able to introspect on request arguments
+  and use complex logic to determine if the request meets policy requirements.
+  For example, a Sentinel policy may restrict Nomad jobs to only using the
+  "docker" driver or prevent jobs from being modified outside of business
+  hours.
+
+- **Policy Scope** - Sentinel policies declare a "scope", which determines when
+  the policies apply. Currently the only supported scope is "submit-job", which
+  applies to any new jobs being submitted, or existing jobs being updated.
+
+- **Enforcement Level** - Sentinel policies support multiple enforcement levels.
+  The `advisory` level emits a warning when the policy fails, while
+  `soft-mandatory` and `hard-mandatory` will prevent the operation. A
+  `soft-mandatory` policy can be overridden if the user has necessary
+  permissions.
+
+### Sentinel policies
+
+Each Sentinel policy has a unique name, an optional description, applicable
+scope, enforcement level, and a Sentinel rule definition. If multiple policies
+are installed for the same scope, all of them are enforced and must pass.
+
+Sentinel policies _cannot_ be used unless the ACL system is enabled.
+
+### Policy scope
+
+Sentinel policies specify an applicable scope, which limits when the policy is
+enforced. This allows policies to govern various aspects of the system.
+
+The following table summarizes the scopes that are available for Sentinel
+policies:
+
+| Scope      | Description                                           |
+| ---------- | ----------------------------------------------------- |
+| submit-job | Applies to any jobs (new or updated) being registered |
+
+### Enforcement level
+
+Sentinel policies specify an enforcement level which changes how a policy is
+enforced. This allows for more flexibility in policy enforcement.
+
+The following table summarizes the enforcement levels that are available:
+
+| Enforcement Level | Description                                                            |
+| ----------------- | ---------------------------------------------------------------------- |
+| advisory          | Issues a warning when a policy fails                                   |
+| soft-mandatory    | Prevents operation when a policy fails, issues a warning if overridden |
+| hard-mandatory    | Prevents operation when a policy fails                                 |
+
+The [`sentinel-override` capability] is required to override a `soft-mandatory`
+policy. This allows a restricted set of users to have override capability when
+necessary.
+
+### Multi-region configuration
+
+Nomad supports multi-datacenter and multi-region configurations. A single region
+is able to service multiple datacenters, and all servers in a region replicate
+their state between each other. In a multi-region configuration, there is a set
+of servers per region. Each region operates independently and is loosely coupled
+to allow jobs to be scheduled in any region and requests to flow transparently
+to the correct region.
+
+When ACLs are enabled, Nomad depends on an "authoritative region" to act as a
+single source of truth for ACL policies, global ACL tokens, and Sentinel
+policies. The authoritative region is configured in the [`server` stanza] of
+agents, and all regions must share a single authoritative source. Any Sentinel
+policies are created in the authoritative region first. All other regions
+replicate Sentinel policies, ACL policies, and global ACL tokens to act as local
+mirrors. This allows policies to be administered centrally, and for enforcement
+to be local to each region for low latency.
+
+
+[img_sentinel_overview]: /img/govern/sentinel.jpg
+[`sentinel-override` capability]: /nomad/docs/secure/acl#sentinel-override
+[`server` stanza]: /nomad/docs/configuration/server
diff --git a/content/nomad/v1.10.x/content/docs/govern/namespaces.mdx b/content/nomad/v1.10.x/content/docs/govern/namespaces.mdx
new file mode 100644
index 0000000000..b9df280cfb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/govern/namespaces.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Create and use namespaces
+description: |-
+  Segment jobs and their associated objects from the jobs of other users of
+  the cluster using Nomad namespaces.
+---
+
+# Create and use namespaces
+
+Nomad has support for namespaces, which allow jobs and their
+associated objects to be segmented from each other and other users of the
+cluster.
+
+Nomad places all jobs and their derived objects into namespaces. These include
+jobs, allocations, deployments, and evaluations.
+
+Nomad does not namespace objects that are shared across multiple namespaces.
+This includes nodes, [ACL policies][acls], [Sentinel policies], and
+[quota specifications][quotas].
+
+In this guide, you'll create and manage a namespace with the CLI. After creating
+the namespace, you then learn how to deploy and manage a job within that
+namespace. Finally, you practice securing the namespace.
+
+## Create and view a namespace
+
+You can manage namespaces with the `nomad namespace` subcommand.
+
+Create the namespace of a cluster.
+
+```shell-session
+$ nomad namespace apply -description "QA instances of webservers" web-qa
+Successfully applied namespace "web-qa"!
+```
+
+List the namespaces of a cluster.
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
+
+## Run a job in a namespace
+
+To run a job in a specific namespace, annotate the job with the `namespace`
+parameter. If omitted, the job will be run in the `default` namespace. Below is
+an example of running the job in the newly created `web-qa` namespace:
+
+```hcl
+job "rails-www" {
+
+    ## Run in the QA environments
+    namespace = "web-qa"
+
+    ## Only run in one datacenter when QAing
+    datacenters = ["us-west1"]
+    # ...
+}
+```
+
+## Use namespaces in the CLI and UI
+
+### Nomad CLI
+
+When using commands that operate on objects that are namespaced, the namespace
+can be specified either with the flag `-namespace` or read from the
+`NOMAD_NAMESPACE` environment variable.
+
+Request job status using the `-namespace` flag.
+
+```shell-session
+$ nomad job status -namespace=web-qa
+ID         Type     Priority  Status   Submit Date
+rails-www  service  50        running  09/17/17 19:17:46 UTC
+```
+
+Export the `NOMAD_NAMESPACE` environment variable.
+
+```shell-session
+$ export NOMAD_NAMESPACE=web-qa
+```
+
+Use the exported environment variable to request job status.
+
+```shell-session
+$ nomad job status
+ID         Type     Priority  Status   Submit Date
+rails-www  service  50        running  09/17/17 19:17:46 UTC
+```
+
+### Nomad UI
+
+The Nomad UI provides a drop-down menu to allow operators to select the
+namespace that they would like to control. The drop-down will appear once there
+are namespaces defined. It is located in the top section of the left-hand column
+of the interface under the "WORKLOAD" label.
+
+[![An image of the Nomad UI showing the location of the namespace drop-down.
+The drop-down is open showing the "Default Namespace" option and an option for a
+"web-qa" namespace.][img_ui_ns_dropdown]][img_ui_ns_dropdown]
+
+## Secure a namespace
+
+Access to namespaces can be restricted using [ACLs]. As an example, you could
+create an ACL policy that allows full access to the QA environment for the web
+namespaces but restrict the production access by creating the following policy:
+
+```hcl
+# Allow read only access to the production namespace
+namespace "web-prod" {
+    policy = "read"
+}
+
+# Allow writing to the QA namespace
+namespace "web-qa" {
+    policy = "write"
+}
+```
+
+## Consul namespaces <EnterpriseAlert inline/>
+
+@include 'consul-namespaces.mdx'
+
+Refer to the [Consul networking integration
+guide](/nomad/docs/networking/consul) for Consul integration instructions.
+
+## Resources
+
+For specific details about working with namespaces, consult the [namespace
+commands] and [HTTP API] documentation.
+
+
+[acls]: /nomad/docs/secure/acl
+[http api]: /nomad/api-docs/namespaces
+[img_ui_ns_dropdown]: /img/govern/nomad-ui-namespace-dropdown.png
+[namespace commands]: /nomad/commands/namespace
+[quotas]: /nomad/docs/govern/resource-quotas
+[sentinel policies]: /nomad/docs/govern/sentinel
diff --git a/content/nomad/v1.10.x/content/docs/govern/resource-quotas.mdx b/content/nomad/v1.10.x/content/docs/govern/resource-quotas.mdx
new file mode 100644
index 0000000000..741140d731
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/govern/resource-quotas.mdx
@@ -0,0 +1,276 @@
+---
+layout: docs
+page_title: Create and use resource quotas
+description: |-
+  Create quotas that you attach to namespaces, and then secure them with ACLs so that you can restrict aggregate resource usage for namespaces.
+---
+
+# Create and use resource quotas
+
+[Nomad Enterprise] provides support for resource quotas, which allow operators
+to restrict the aggregate resource usage of [namespaces]. Once a quota
+specification is attached to a namespace, the Nomad cluster will count all
+resource usage by jobs in that namespace toward the quota limits. If the
+resource is exhausted, allocations within the namespaces will be queued until
+resources become available—by other jobs finishing or the quota being expanded.
+
+In this guide, you'll create a quota that limits resources in the global region.
+You will then assign the quota to a namespace where you will deploy a job.
+Finally, you'll learn how to secure the quota with ACLs.
+
+<EnterpriseAlert />
+
+## Define and create a quota
+
+You can manage resource quotas by using the `nomad quota` subcommand. To
+get started with creating a quota specification, run `nomad quota init` which
+produces an example quota specification.
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
+
+The file `spec.hcl` defines a limit for the global region. Additional limits may
+be specified in order to limit other regions.
+
+```hcl
+# spec.hcl
+name = "default-quota"
+description = "Limit the shared default namespace"
+
+# Create a limit for the global region. Additional limits may
+# be specified in-order to limit other regions.
+limit {
+  region = "global"
+  region_limit {
+    cores      = 0
+    cpu        = 2500
+    memory     = 1000
+    memory_max = 1000
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+  }
+  variables_limit = 1000
+}
+```
+
+### Resource limits
+
+When specifying resource limits the following enforcement behaviors are defined:
+
+- `limit < 0`: A limit less than zero disallows any access to the resource.
+
+- `limit == 0`: A limit of zero allows unlimited access to the resource.
+
+- `limit > 0`: A limit greater than zero enforces that the consumption is less
+  than or equal to the given limit.
+
+-> **Note:** Limits that specify the count of devices work differently. A `count > 0`
+enforces that the consumption is less than or equal to the given limit, and setting
+it to `0` disallows any usage of the given device. Unlike other limits, device count
+cannot be set to a negative value. To allow unlimited access to a device
+resource, remove it from the region limit.
+
+A quota specification is composed of one or more resource limits. Each limit
+applies to a particular Nomad region. Within the limit object, operators can
+specify the allowed CPU and memory usage.
+
+### Create the quota
+
+To create the quota, run `nomad quota apply` with the filename of your quota specification.
+
+```shell-session
+$ nomad quota apply spec.hcl
+Successfully applied quota specification "default-quota"!
+```
+
+Check for success with `nomad quota list`.
+
+```shell-session
+$ nomad quota list
+Name           Description
+default-quota  Limit the shared default namespace
+```
+
+## Attach a quota to a namespace
+
+In order for a quota to be enforced, you have to attach the quota specification
+to a namespace. This can be done using the `nomad namespace apply` command. Add
+the new quota specification to the `default` namespace as follows:
+
+```shell-session
+$ nomad namespace apply -quota default-quota default
+Successfully applied namespace "default"!
+```
+
+## View quota information
+
+Now that you have attached a quota to a namespace, you can run a job in the default namespace.
+
+Initialize the job.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+Run the job in the default namespace.
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: 985a1df8-0221-b891-5dc1-4d31ad4e2dc3
+```
+
+Check the status.
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 2500   0 / inf     0 / 1000      0 / 1000          0 / 1000
+
+Quota Device Limits
+Region  Device Name        Device Usage
+global  nvidia/gpu/1080ti  1 / 1
+```
+
+Notice that the newly created job is accounted against the quota specification
+since it is being run in the namespace attached to the "default-quota" quota.
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: ce8e1941-0189-b866-3dc4-7cd92dc38a69
+```
+
+Now, add more instances of the job by changing `count = 1` to `count = 4` and
+check to see if additional allocations were added.
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 10/16/17 10:51:32 PDT
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         3        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Quota limit hit "memory exhausted (1024 needed > 1000 limit)"
+
+Latest Deployment
+ID          = 7cd98a69
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       4        3       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+6d735236  81f72d90  cache       1        run      running  10/16/17 10:51:32 PDT
+ce8e1941  81f72d90  cache       1        run      running  10/16/17 10:51:32 PDT
+9b8e185e  81f72d90  cache       1        run      running  10/16/17 10:51:24 PDT
+```
+
+The output indicates that Nomad created two more allocations but did not place
+the fourth allocation, which would have caused the quota to be oversubscribed on
+memory.
+
+## Secure quota with ACLs
+
+Access to quotas can be restricted using [ACLs]. As an example, you could create
+an ACL policy that allows read-only access to quotas.
+
+```hcl
+# Allow read only access to quotas.
+quota {
+    policy = "read"
+}
+```
+
+Proper ACLs are necessary to prevent users from bypassing quota enforcement by
+increasing or removing the quota specification.
+
+## Design for federated clusters
+
+Nomad makes working with quotas in a federated cluster simple by replicating
+quota specifications from the [authoritative Nomad region]. This allows
+operators to interact with a single cluster but create quota specifications that
+apply to all Nomad clusters.
+
+As an example, you can create a quota specification that applies to two regions:
+
+```hcl
+name = "federated-example"
+description = "A single quota spec affecting multiple regions"
+
+# Create a limits for two regions
+limit {
+    region = "europe"
+    region_limit {
+        cpu = 20000
+        memory = 10000
+    }
+}
+
+limit {
+    region = "asia"
+    region_limit {
+        cpu = 10000
+        memory = 5000
+    }
+}
+```
+
+Apply the specification.
+
+```shell-session
+$ nomad quota apply spec.hcl
+Successfully applied quota specification "federated-example"!
+```
+
+Now that the specification is applied and attached to a namespace with jobs in each region,
+use the `nomad quota status` command to observe how the enforcement applies
+across federated clusters.
+
+```shell-session
+$ nomad quota status federated-example
+Name        = federated-example
+Description = A single quota spec affecting multiple regions
+Limits      = 2
+
+Quota Limits
+Region  CPU Usage     Memory Usage
+asia    2500 / 10000  1000 / 5000
+europe  8800 / 20000  6000 / 10000
+```
+
+## Learn more about quotas
+
+For specific details about working with quotas, consult the [quota commands] and
+[HTTP API] documentation.
+
+[acls]: /nomad/docs/secure/acl
+[authoritative nomad region]: /nomad/docs/configuration/server#authoritative_region
+[http api]: /nomad/api-docs/quotas
+[namespaces]: /nomad/docs/govern/namespaces
+[nomad enterprise]: https://www.hashicorp.com/products/nomad
+[quota commands]: /nomad/commands/quota
+[quotas]: /nomad/docs/govern/resource-quotas
diff --git a/content/nomad/v1.10.x/content/docs/govern/sentinel.mdx b/content/nomad/v1.10.x/content/docs/govern/sentinel.mdx
new file mode 100644
index 0000000000..909ec72167
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/govern/sentinel.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: Create and manage Sentinel policies
+description: |-
+  Create, install, test, and update Sentinel policies to express your policies
+  as code so that Nomad automatically enforces them.
+---
+
+# Create and manage Sentinel policies
+
+
+[Nomad Enterprise] integrates with [HashiCorp Sentinel][sentinel] for
+fine-grained policy enforcement. Sentinel allows operators to express their
+policies as code and have their policies automatically enforced. This allows
+operators to define a "sandbox" and restrict actions to only those compliant
+with policy.
+
+The Sentinel integration builds on the [ACL System][acls]. The integration
+provides the ability to create fine grained policy enforcements. Users must have
+the appropriate permissions to perform an action and are subject to any
+applicable Sentinel policies.
+
+In this guide, you will create a policy and then practice applying it to a job
+at different enforcement levels. Finally, you'll learn more about Sentinel
+language specifics.
+
+<EnterpriseAlert />
+
+## Prerequisites
+
+The following example demonstrates how to install a Sentinel policy. It assumes
+that ACLs have already been bootstrapped (refer to the [ACL guide][acls]), and
+that a `NOMAD_TOKEN` environment variable is set to a management token.
+
+## Create, install, and test a policy
+
+First, create a Sentinel policy, named `test.sentinel`:
+
+```sentinel
+## Test policy always fails for demonstration purposes
+main = rule { false }
+```
+
+Then, install this as an "advisory" policy which issues a warning on failure:
+
+```shell-session
+$ nomad sentinel apply -level=advisory test-policy test.sentinel
+Successfully wrote "test-policy" Sentinel policy!
+```
+
+Use `nomad job init` to create a job file.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+Attempt to submit that job file with `nomad job run`.
+
+```shell-session
+$ nomad job run example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* test-policy : Result: false (allowed failure based on level)
+
+FALSE - test-policy:2:1 - Rule "main"
+
+
+==> Monitoring evaluation "f43ac28d"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "11e01124"
+    Allocation "2618f3b4" created: node "add8ce93", group "cache"
+    Allocation "5c2674f2" created: node "add8ce93", group "cache"
+    Allocation "9937811f" created: node "add8ce93", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "f43ac28d" finished with status "complete"
+```
+
+The output indicates that the policy failed, but the job was accepted because of
+an "advisory" enforcement level.
+
+## Update and test the policy
+
+Next, change `test.sentinel` to only allow "exec" based drivers:
+
+```sentinel
+# Test policy only allows exec based tasks
+main = rule { all_drivers_exec }
+
+# all_drivers_exec checks that all the drivers in use are exec
+all_drivers_exec = rule {
+    all job.task_groups as tg {
+        all tg.tasks as task {
+            task.driver is "exec"
+        }
+    }
+}
+```
+
+Then updated the policy at a soft mandatory level:
+
+```shell-session
+$ nomad sentinel apply -level=soft-mandatory test-policy test.sentinel
+Successfully wrote "test-policy" Sentinel policy!
+```
+
+With the new policy, attempt to submit the same job, which uses the "docker"
+driver:
+
+```shell-session
+$ nomad run example.nomad.hcl
+Error submitting job: Unexpected response code: 500 (1 error(s) occurred:
+
+* test-policy : Result: false
+
+FALSE - test-policy:2:1 - Rule "main"
+  FALSE - test-policy:6:5 - all job.task_groups as tg {
+  all tg.tasks as task {
+    task.driver is "exec"
+  }
+}
+
+FALSE - test-policy:5:1 - Rule "all_drivers_exec"
+)
+```
+
+The output indicates that the policy and job have failed.
+
+## Override the policy
+
+Because the policy is failing, the job was rejected. Since the policy level is
+"soft-mandatory", you can override it using the `-policy-override` flag.
+
+Submit the job again with the `-policy-override` flag set:
+
+```shell-session
+$ nomad job run -policy-override example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* test-policy : Result: false (allowed failure based on level)
+
+FALSE - test-policy:2:1 - Rule "main"
+  FALSE - test-policy:6:5 - all job.task_groups as tg {
+  all tg.tasks as task {
+    task.driver is "exec"
+  }
+}
+
+FALSE - test-policy:5:1 - Rule "all_drivers_exec"
+
+
+==> Monitoring evaluation "16195b50"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "11e01124"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "16195b50" finished with status "complete"
+```
+
+This time, the job was accepted but with a warning that our policy is failing
+but was overridden.
+
+## Extend your knowledge: policy specification
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+### Sentinel job objects
+
+The `job` object is made available to policies in the `submit-job` scope
+automatically, without an explicit import. The object maps to the
+[JSON job specification], but fields differ slightly for better readability.
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on the job are accessed by the same name, converted to lower case and
+separating camel case to underscores. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+| ---------------------------------------- | ------------------------------------------- |
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+## Learn more about Sentinel
+
+For specific details about working with Sentinel, consult the [`nomad sentinel` sub-commands]
+and [HTTP API] documentation.
+
+[`nomad sentinel` sub-commands]: /nomad/commands/sentinel
+[`sentinel-override` capability]: /nomad/docs/secure/acl#sentinel-override
+[`server` stanza]: /nomad/docs/configuration/server
+[acls]: /nomad/docs/secure/acl
+[http api]: /nomad/api-docs/sentinel-policies
+[json job specification]: /nomad/api-docs/json-jobs
+[nomad enterprise]: https://www.hashicorp.com/products/nomad/
+[sentinel]: https://docs.hashicorp.com/sentinel
diff --git a/content/nomad/v1.10.x/content/docs/govern/use-node-pools.mdx b/content/nomad/v1.10.x/content/docs/govern/use-node-pools.mdx
new file mode 100644
index 0000000000..9edb260251
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/govern/use-node-pools.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Create and use node pools
+description: |-
+  Create node pools. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+---
+
+# Create and use node pools
+
+@include 'node-pools.mdx'
diff --git a/content/nomad/v1.10.x/content/docs/index.mdx b/content/nomad/v1.10.x/content/docs/index.mdx
new file mode 100644
index 0000000000..33bf5f9203
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Nomad is a flexible workload orchestrator to deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run diverse workloads including Docker, non-containerized, microservice, and batch applications.
+---
+
+# Nomad Documentation
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. Nomad can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+If you are just getting started with Nomad, refer to the [Getting
+Started tutorial collection][gs].
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/configure-tasks.mdx b/content/nomad/v1.10.x/content/docs/job-declare/configure-tasks.mdx
new file mode 100644
index 0000000000..931117af73
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/configure-tasks.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Configure job tasks
+description: |-
+  Provide values to a Nomad workload through job specification configuration files, command line arguments, and environment variables.
+---
+
+# Configure job tasks
+
+Most applications require some kind of local configuration. While command line
+arguments are the simplest method, many applications require more complex
+configurations provided via environment variables or configuration files. This
+section explores how to configure Nomad jobs to support many common
+configuration use cases.
+
+## Define application arguments
+
+Many tasks accept configuration via command-line arguments. For example,
+consider the [http-echo](https://github.com/hashicorp/http-echo) server which
+is a small go binary that renders the provided text as a webpage. The binary
+accepts two parameters:
+
+- The `-listen` flag contains the `address:port` to listen on
+- `-text` - the text to render as the HTML page
+
+Outside of Nomad, the server is started like this:
+
+```shell-session
+$ http-echo -listen=":5678" -text="hello world"
+```
+
+The Nomad equivalent job file might look something like this:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+
+    task "server" {
+      driver = "exec"
+
+      config {
+        command = "/bin/http-echo"
+
+        args = [
+          "-listen",
+          ":5678",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+<Note>
+
+ For this job specification, you must install the `http-echo` in
+the `/bin` folder on each of your clients. Nomad can
+also optionally fetch the binary using the `artifact` resource.
+
+</Note>
+
+Nomad has many [drivers], and most support passing arguments to their tasks via
+the `args` parameter. This parameter also supports Nomad variable
+[interpolation]. For example, if you wanted Nomad to dynamically allocate a high
+port to bind the service on instead of relying on a static port for the previous
+job:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+
+    task "server" {
+      driver = "exec"
+
+      config {
+        command = "/bin/http-echo"
+
+        args = [
+          "-listen",
+          ":${NOMAD_PORT_http}",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+## Set environment variables
+
+Some applications can be configured via environment variables. The
+[Twelve-Factor App](https://12factor.net/config) document suggests configuring
+applications through environment variables. Nomad supports custom environment
+variables in two ways:
+
+- Interpolation in an `env` stanza
+- Templated in the a `template` stanza
+
+### `env` stanza
+
+Each task may have an `env` stanza which specifies environment variables:
+
+```hcl
+task "server" {
+  env {
+    my_key = "my-value"
+  }
+}
+```
+
+The `env` stanza also supports [interpolation]:
+
+```hcl
+task "server" {
+  env {
+    LISTEN_PORT = "${NOMAD_PORT_http}"
+  }
+}
+```
+
+Consult the [`env` stanza] documentation for details.
+
+### Build environment variables with templates
+
+Nomad's [`template` stanza] can be used to generate environment variables.
+Environment variables may be templated with [Node attributes and
+metadata][nodevars], the contents of files on disk, Consul keys, or secrets from
+Vault:
+
+```hcl
+template {
+  data = <<EOH
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.key}}{{end}}"
+CERT={{ file "path/to/cert.pem" | to JSON }}
+NODE_ID="{{ env "node.unique.id" }}"
+EOH
+
+  destination = "secrets/config.env"
+  env         = true
+}
+```
+
+The template will be written to disk and then read as environment variables
+before your task is launched.
+
+## Load external configuration files
+
+Many applications use files for configuration. Nomad supports downloading files
+using the [`artifact` stanza] and [templating][`template` stanza] them prior to
+launching tasks. This allows shipping of configuration files and other assets
+that the task needs to run properly.
+
+Here is an example job which pulls down a configuration file as an artifact and
+templates it:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    task "server" {
+      driver = "exec"
+
+      artifact {
+        source      = "http://example.com/config.hcl.tmpl"
+        destination = "local/config.hcl.tmpl"
+      }
+
+      template {
+        source      = "local/config.hcl.tmpl"
+        destination = "local/config.hcl"
+      }
+
+      config {
+        command = "my-app"
+        args = [
+          "-config", "local/config.hcl",
+        ]
+      }
+    }
+  }
+}
+```
+
+For more information on the artifact resource, please consult the [`artifact`
+stanza] documentation.
+
+[`artifact` stanza]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[nodevars]: /nomad/docs/reference/runtime-variable-interpolation
+[`template` stanza]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Variable Interpolation'
+[drivers]: /nomad/docs/job-declare/task-driver
+[`env` stanza]: /nomad/docs/job-specification/env
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/consul-service-mesh.mdx b/content/nomad/v1.10.x/content/docs/job-declare/consul-service-mesh.mdx
new file mode 100644
index 0000000000..5585280ecd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/consul-service-mesh.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: Use Consul service mesh
+description: |-
+  Nomad integrates with Consul service mesh to securely connect and isolate
+  your workloads. Review example job configurations that use service mesh. Learn about the Envoy proxy as well as mesh, ingress, and terminating gateways.
+---
+
+# Use Consul service mesh
+
+This page provides information on using Consul service mesh with
+Nomad to securely connect and isolate your workloads. Review example job
+configurations that use service mesh. Learn about the Envoy proxy as well as
+mesh, ingress, and terminating gateways.
+
+## Introduction
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/networking/consul/service-mesh)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/reference/runtime-environment-settings#network-related-variables
+
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/create-job.mdx b/content/nomad/v1.10.x/content/docs/job-declare/create-job.mdx
new file mode 100644
index 0000000000..77eb3f5194
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/create-job.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: Create and submit a job
+description: |-
+ Create a Nomad job file and follow the job workflow to plan, submit, update,  and run a job.
+---
+
+# Create and submit a job
+
+In Nomad, the description of the job and all its requirements are maintained in
+a single file called the "job file". This job file resides locally on disk and
+it is highly recommended that you check job files into source control.
+
+The general flow for submitting a job in Nomad is:
+
+1. Author a job file according to the job specification
+1. Plan and review changes with a Nomad server
+1. Submit the job file to a Nomad server
+1. (Optional) Review job status and logs
+
+Here is a very basic example to get you started.
+
+## Author a job file
+
+Nomad attempts to strike a balance between ease and expressiveness in its job
+specification. Nomad also provides the `nomad init` command to generate sample
+job files. For more detailed information about the Nomad job specification,
+please consult the [Nomad documentation][job specification].
+
+Here is a sample job file which runs a small docker container web server to
+start with.
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+    task "server" {
+      driver = "docker"
+
+      config {
+        image = "hashicorp/http-echo"
+        ports = ["http"]
+        args = [
+          "-listen",
+          ":5678",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+This job file exists on your local workstation in plain text. When you are
+satisfied with this job file, you will plan and review the scheduler decision.
+It is generally a best practice to commit job files to source control,
+especially if you are working in a team.
+
+## Plan the job
+
+Once the job file is authored, you probably want to preview the changes Nomad
+will make when it runs. The `nomad job plan` command invokes a dry-run of the
+scheduler and output which scheduling decisions would take place.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++ Job: "docs"
++ Task Group: "example" (1 create)
+  + Task: "server" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Note that no action was taken. This job is not running. This is a complete
+dry-run and no allocations have taken place.
+
+## Submit the job
+
+Assuming the output of the plan looks acceptable, now ask Nomad to execute the
+job. This is done via the `nomad job run` command. You can optionally supply the
+modify index provided by the plan command to ensure no changes to this job have
+taken place between our plan and now.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "0d159869"
+    Evaluation triggered by job "docs"
+    Allocation "5cbf23a1" created: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0d159869" finished with status "complete"
+```
+
+Now that the job is scheduled, it may or may not be running. You need to inspect
+the allocation status and logs to make sure the job started correctly. The next
+section on [inspecting state](/nomad/docs/job-run/inspect)
+details ways to examine this job's state.
+
+## Update and plan the job
+
+When making updates to the job, it is best to always run the plan command and
+then the run command. For example:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+   datacenters = ["dc1"]
+
+   group "example" {
++    count = "2"
++
+     task "server" {
+       driver = "docker"
+```
+
+After saving these changes to disk, run the `nomad job plan` command:
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "example" (1 create, 1 in-place update)
+  +/- Count: "1" => "2" (forces create)
+      Task: "server"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 131
+To submit the job with version verification run:
+
+nomad job run -check-index 131 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+#### Reserved port collisions
+
+Because this job uses a static port, it is possible for some instances to not be
+placeable depending on the number of clients you have in your Nomad cluster. If
+your plan output contains:
+
+```plaintext hideClipboard
+Dimension "network: reserved port collision" exhausted on x nodes
+```
+
+This indicates that every feasible client in your cluster has or will have
+something placed at the requested port, leaving no place for some of these
+allocations to run. To resolve this, you need to reduce the requested count,
+add additional clients, or migrate from static ports to dynamic ports in your
+job specification.
+
+## Run the job
+
+Now, assuming the output is okay, execute the `nomad job run` command. Including
+the `check-index` parameter ensures that the job
+was not changed between the plan and run phases.
+
+```shell-session
+$ nomad job run -check-index 131 docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+For more details on advanced job updating strategies such as canary builds and
+build-green deployments, consult the documentation on [job update strategies].
+
+[job specification]: /nomad/docs/job-specification
+[job update strategies]:/nomad/docs/job-declare/strategy
+[inspecting state]: /nomad/docs/job-run/inspect
+
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/exit-signals.mdx b/content/nomad/v1.10.x/content/docs/job-declare/exit-signals.mdx
new file mode 100644
index 0000000000..2d4705a6f2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/exit-signals.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: Configure exit signals
+description: |-
+  Configure the exit signal that Nomad sends to an application to allow it
+  to gracefully terminate before Nomad kills the application.
+---
+
+# Configure exit signals
+
+On operating systems that support signals, Nomad will send the application a
+configurable signal before killing it. This gives the application time to
+gracefully drain connections and conduct other cleanup before shutting down.
+Certain applications take longer to drain than others, and thus Nomad allows
+specifying the amount of time to wait for the application to exit before
+force-killing it.
+
+Before Nomad terminates an application, it will send the `SIGINT` signal to the
+process. Processes running under Nomad should respond to this signal to
+gracefully drain connections. After a configurable timeout, the application
+will be force-terminated.
+
+The signal sent may be configured with the [`kill_signal`][kill_signal] task
+parameter, and the timeout before the task is force-terminated may be
+configured via [`kill_timeout`][kill_timeout].
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+      kill_timeout = "45s"
+    }
+  }
+}
+```
+
+The behavior is slightly different for Docker-based tasks. Nomad will run the
+`docker stop` command with the specified `kill_timeout`. The signal that `docker stop` sends to your container entrypoint is configurable using the
+[`STOPSIGNAL` configuration directive]; however, please note that the default is
+`SIGTERM`.
+
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[`stopsignal` configuration directive]: https://docs.docker.com/engine/reference/builder/#stopsignal
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/failure/check-restart.mdx b/content/nomad/v1.10.x/content/docs/job-declare/failure/check-restart.mdx
new file mode 100644
index 0000000000..548b90448b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/failure/check-restart.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Configure health check restart
+description: |-
+  Configure your Nomad job to restart workloads when health checks
+  fail.
+---
+
+# Configure health check restart
+
+The [`check_restart` stanza][check restart] instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the limit specified in a check_restart stanza, it is restarted
+according to the task group's restart policy. Restarts are local to the node
+running the task based on the tasks `restart` policy.
+
+The `limit` field is used to specify the number of times a failing health check
+is seen before local restarts are attempted. Operators can also specify a
+`grace` duration to wait after a task restarts before checking its health.
+
+You should configure the check restart on services when its likely that a
+restart would resolve the failure. An example of this might be restarting to
+correct a transient connection issue on the service.
+
+The following `check_restart` stanza waits for two consecutive health check
+failures with a grace period and considers both `critical` and `warning`
+statuses as failures.
+
+```hcl
+check_restart {
+  limit           = 2
+  grace           = "10s"
+  ignore_warnings = false
+}
+```
+
+The following CLI example output shows health check failures triggering restarts
+until its restart limit is reached.
+
+```shell-session
+$ nomad alloc status e1b43128-2a0a-6aa3-c375-c7e8a7c48690
+ID                   = e1b43128
+Eval ID              = 249cbfe9
+Name                 = demo.demo[0]
+Node ID              = 221e998e
+Job ID               = demo
+Job Version          = 0
+Client Status        = failed
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 2m59s ago
+Modified             = 39s ago
+
+Task "test" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB  p1: 127.0.0.1:28422
+
+Task Events:
+Started At     = 2018-04-12T22:50:32Z
+Finished At    = 2018-04-12T22:50:54Z
+Total Restarts = 3
+Last Restart   = 2018-04-12T17:50:15-05:00
+
+Recent Events:
+Time                       Type              Description
+2018-04-12T17:50:54-05:00  Not Restarting    Exceeded allowed attempts 3 in interval 30m0s and mode is "fail"
+2018-04-12T17:50:54-05:00  Killed            Task successfully killed
+2018-04-12T17:50:54-05:00  Killing           Sent interrupt. Waiting 5s before force killing
+2018-04-12T17:50:54-05:00  Restart Signaled  health check: check "service: \"demo-service-test\" check" unhealthy
+2018-04-12T17:50:32-05:00  Started           Task started by client
+2018-04-12T17:50:15-05:00  Restarting        Task restarting in 16.887291122s
+2018-04-12T17:50:15-05:00  Killed            Task successfully killed
+2018-04-12T17:50:15-05:00  Killing           Sent interrupt. Waiting 5s before force killing
+2018-04-12T17:50:15-05:00  Restart Signaled  health check: check "service: \"demo-service-test\" check" unhealthy
+2018-04-12T17:49:53-05:00  Started           Task started by client
+```
+
+[check restart]: /nomad/docs/job-specification/check_restart
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/failure/index.mdx b/content/nomad/v1.10.x/content/docs/job-declare/failure/index.mdx
new file mode 100644
index 0000000000..a5d9058de9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/failure/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Failure recovery strategies
+description: |-
+  Discover the available job failure recovery strategies in Nomad so that you
+  can restart or reschedule jobs automatically if they fail.
+---
+
+# Failure recovery strategies
+
+Most applications deployed in Nomad are either long running services or one time
+batch jobs. They can fail for various reasons like:
+
+- A temporary error in the service that resolves when its restarted.
+
+- An upstream dependency might not be available, leading to a health check
+  failure.
+
+- Disk, Memory or CPU contention on the node that the application is running on.
+
+- The application uses Docker and the Docker daemon on that node is
+  unresponsive.
+
+Nomad provides configurable options to enable recovering failed tasks to avoid
+downtime. Nomad will try to restart a failed task on the node it is running on,
+and also try to reschedule it on another node. Please start with one of the
+guides below or use the navigation on the left for details on each option:
+
+- [Local restarts](/nomad/docs/job-declare/failure/restart)
+- [Health check restarts](/nomad/docs/job-declare/failure/check-restart)
+- [Reschedule](/nomad/docs/job-declare/failure/reschedule)
+
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/failure/reschedule.mdx b/content/nomad/v1.10.x/content/docs/job-declare/failure/reschedule.mdx
new file mode 100644
index 0000000000..0676b3b491
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/failure/reschedule.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Configure reschedule
+description: |-
+  Discover how to control the rescheduling behaviors of jobs to allow them
+  to be scheduled on different nodes if needed, such as in the event of a failure.
+---
+
+# Configure reschedule
+
+Tasks can sometimes fail due to network, CPU or memory issues on the node
+running the task. In such situations, Nomad can reschedule the task on another
+node. The [`reschedule` stanza] can be used to configure how Nomad
+should try placing failed tasks on another node in the cluster. Reschedule
+attempts have a delay between each attempt, and the delay can be configured to
+increase between each rescheduling attempt according to a configurable
+`delay_function`. Consult the [`reschedule` stanza] documentation for more
+information.
+
+Service jobs are configured by default to have unlimited reschedule attempts.
+You should use the reschedule stanza to ensure that failed tasks are
+automatically reattempted on another node without needing operator intervention.
+
+The following CLI example shows job and allocation statuses for a task being
+rescheduled by Nomad. The CLI shows the number of previous attempts if there is
+a limit on the number of reschedule attempts. The CLI also shows when the next
+reschedule will be attempted.
+
+```shell-session
+$ nomad job status demo
+ID            = demo
+Name          = demo
+Submit Date   = 2018-04-12T15:48:37-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = pending
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+demo        0       0         0        2       0         0
+
+Future Rescheduling Attempts
+Task Group  Eval ID   Eval Time
+demo        ee3de93f  5s from now
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status  Created  Modified
+39d7823d  f2c2eaa6  demo        0        run      failed  5s ago   5s ago
+fafb011b  f2c2eaa6  demo        0        run      failed  11s ago  10s ago
+
+```
+
+```shell-session
+$ nomad alloc status 3d0b
+ID                     = 3d0bbdb1
+Eval ID                = 79b846a9
+Name                   = demo.demo[0]
+Node ID                = 8a184f31
+Job ID                 = demo
+Job Version            = 0
+Client Status          = failed
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 15s ago
+Modified               = 15s ago
+Reschedule Attempts    = 3/5
+Reschedule Eligibility = 25s from now
+
+Task "demo" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB  p1: 127.0.0.1:27646
+
+Task Events:
+Started At     = 2018-04-12T20:44:25Z
+Finished At    = 2018-04-12T20:44:25Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type            Description
+2018-04-12T15:44:25-05:00  Not Restarting  Policy allows no restarts
+2018-04-12T15:44:25-05:00  Terminated      Exit Code: 127
+2018-04-12T15:44:25-05:00  Started         Task started by client
+2018-04-12T15:44:25-05:00  Task Setup      Building Task Directory
+2018-04-12T15:44:25-05:00  Received        Task received by client
+
+```
+
+[`reschedule` stanza]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Stanza'
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/failure/restart.mdx b/content/nomad/v1.10.x/content/docs/job-declare/failure/restart.mdx
new file mode 100644
index 0000000000..beba1eae51
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/failure/restart.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Configure restart
+description: |-
+  Discover how to control the restart behaviors of jobs so that Nomad schedules
+  them on different nodes if needed, such as in the event of a failure.
+---
+
+# Configure restart
+
+Nomad will [by default][defaults] attempt to restart a job locally on the node
+that it is running or scheduled to be running on. These defaults vary by the
+scheduler type in use for the job: system, service, or batch.
+
+To customize this behavior, the task group can be annotated with configurable
+options using the [`restart` stanza][restart]. Nomad will restart the failed
+task up to `attempts` times within a provided `interval`. Operators can also
+choose whether to keep attempting restarts on the same node, or to fail the task
+so that it can be rescheduled on another node, via the `mode` parameter.
+
+Setting mode to `fail` in the restart stanza allows rescheduling to occur
+potentially moving the task to another node and is best practice.
+
+The following CLI example shows job status and allocation status for a failed
+task that is being restarted by Nomad. Allocations are in the `pending` state
+while restarts are attempted. The `Recent Events` section in the CLI shows
+ongoing restart attempts.
+
+```shell-session
+$ nomad job status demo
+ID            = demo
+Name          = demo
+Submit Date   = 2018-04-12T14:37:18-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+demo        0       3         0        0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce5bf1d1  8a184f31  demo        0        run      pending  27s ago  5s ago
+d5dee7c8  8a184f31  demo        0        run      pending  27s ago  5s ago
+ed815997  8a184f31  demo        0        run      pending  27s ago  5s ago
+```
+
+In the following example, the allocation `ce5bf1d1` is restarted by Nomad
+approximately every ten seconds, with a small random jitter. It eventually
+reaches its limit of three attempts and transitions into a `failed` state, after
+which it becomes eligible for [rescheduling][rescheduling].
+
+```shell-session
+$ nomad alloc status ce5bf1d1
+ID                     = ce5bf1d1
+Eval ID                = 64e45d11
+Name                   = demo.demo[1]
+Node ID                = a0ccdd8b
+Job ID                 = demo
+Job Version            = 0
+Client Status          = failed
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 56s ago
+Modified               = 22s ago
+
+Task "demo" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB
+
+Task Events:
+Started At     = 2018-04-12T22:29:08Z
+Finished At    = 2018-04-12T22:29:08Z
+Total Restarts = 3
+Last Restart   = 2018-04-12T17:28:57-05:00
+
+Recent Events:
+Time                       Type            Description
+2018-04-12T17:29:08-05:00  Not Restarting  Exceeded allowed attempts 3 in interval 5m0s and mode is "fail"
+2018-04-12T17:29:08-05:00  Terminated      Exit Code: 127
+2018-04-12T17:29:08-05:00  Started         Task started by client
+2018-04-12T17:28:57-05:00  Restarting      Task restarting in 10.364602876s
+2018-04-12T17:28:57-05:00  Terminated      Exit Code: 127
+2018-04-12T17:28:57-05:00  Started         Task started by client
+2018-04-12T17:28:47-05:00  Restarting      Task restarting in 10.666963769s
+2018-04-12T17:28:47-05:00  Terminated      Exit Code: 127
+2018-04-12T17:28:47-05:00  Started         Task started by client
+2018-04-12T17:28:35-05:00  Restarting      Task restarting in 11.777324721s
+```
+
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Stanza'
+[defaults]: /nomad/docs/job-specification/restart#restart-parameter-defaults
+[rescheduling]: /nomad/docs/job-specification/reschedule 'Nomad restart Stanza'
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/index.mdx b/content/nomad/v1.10.x/content/docs/job-declare/index.mdx
new file mode 100644
index 0000000000..bbb6e0c2fe
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/index.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Declare a Nomad job
+description: |-
+  This section provides guidance for declaring Nomad job with a job specification.
+---
+
+# Declare a Nomad job
+
+Developers deploy and manage their applications in Nomad via jobs. This section provides guidance for declaring a Nomad job with a job specification.
+
+In Nomad, a job is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into task groups.
+
+Declare the desired state of your job in a [job specification][job-spec], or jobspec, that describes the tasks and resources necessary for the job to run. You can also include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual job state matches your desired
+state.
+
+## Deploy a new Nomad job
+
+The general flow for operating a job in Nomad is:
+
+1. Author the job file according to the [job specification][job-spec].
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+## Update a running job
+
+When updating a job, there are a number of built-in update strategies which may
+be defined in the job file. The general flow for updating an existing job in
+Nomad is:
+
+1. Modify the existing job file with the desired changes.
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Because the job file defines the update strategy (blue-green, rolling updates,
+etc.), the workflow remains the same regardless of whether this is an initial
+deployment or a long-running job.
+
+## Resources
+
+- Refer to the [Job concept page](/nomad/docs/concepts/job) for more information
+  on Nomad jobs.
+- [Nomad job specification][job-spec]
+
+[job-spec]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/multiregion.mdx b/content/nomad/v1.10.x/content/docs/job-declare/multiregion.mdx
new file mode 100644
index 0000000000..11dda700a8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/multiregion.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: Configure multi-region deployments
+description: |-
+  Deploy applications to multiple federated Nomad clusters with configurable
+  rollout and rollback strategies.
+---
+
+# Configure multi-region deployments
+
+Federated Nomad clusters enable you to submit jobs targeting any region
+from any server even if that server resides in a different region. You may submit jobs that are deployed to multiple
+regions. This guide demonstrates multi-region deployments, including
+configurable rollout and rollback strategies.
+
+<EnterpriseAlert/>
+
+You can create a multi-region deployment job by adding a [`multiregion`]
+stanza to the job as shown below.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 1
+    on_failure   = "fail_all"
+  }
+
+  region "west" {
+    count       = 2
+    datacenters = ["west-1"]
+  }
+
+  region "east" {
+    count       = 1
+    datacenters = ["east-1", "east-2"]
+  }
+
+}
+```
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have two Nomad
+environments running Nomad 0.12 or greater with ports 4646, 4647, and 4648 exposed. You can use this
+[Terraform environment][nomad-tf] to provision the sandbox environments. This
+guide assumes two clusters with one server node and two client nodes in each
+cluster. While the Terraform code already opens port 4646, you will also need to
+expose ports 4647 and 4648 on the server you wish to run [nomad server
+join][server-join] against. Consult the [Nomad Port Requirements][ports-used]
+documentation for more information.
+
+Next, you'll need to federate these two regions as described in the [federation guide].
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node in each cluster. Consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+Run the [`nomad server members`][nomad-server-members] command.
+
+```shell-session
+$ nomad server members
+```
+
+After you have federated your clusters, the output should include the servers from both regions.
+
+```plaintext
+Name                     Address        Port  Status  Leader  Protocol  Build       Datacenter  Region
+ip-172-31-26-138.east    172.31.26.138  4648  alive   true    2         0.12.0+ent  east-1      east
+ip-172-31-29-34.west     172.31.29.34   4648  alive   true    2         0.12.0+ent  west-1      west
+```
+
+If you are using [ACLs][acls-track], you'll need to make sure your token has `submit-job`
+permissions with a `global` scope.
+
+You may wish to review the [update strategies guides][updates-track] before
+starting this guide.
+
+## Multi-region concepts
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft/consensus cluster; they don't share their data stores. Each region in a
+multi-region deployment gets an independent copy of the job, parameterized with
+the values of the `region` stanza. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` stanza.
+
+A single region deployment using one of the various [update strategies][updates-track]
+begins in the `running` state and ends in either the `successful` state if it succeeds,
+the `canceled` state if another deployment supersedes it before it's
+complete, or the `failed` state if it fails for any other reason. A failed single
+region deployment may automatically revert to the previous version of the job if
+its [`update` stanza] has the [`auto_revert`][update-auto-revert] setting.
+
+In a multi-region deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point, up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Create a multi-region job
+
+The job below will deploy to both regions. The `max_parallel` field of the
+`strategy` block restricts Nomad to deploy to the regions one at a time. If
+either of the region deployments fail, both regions will be marked as
+failed. The `count` field for each region is interpolated for each region,
+replacing the `count = 0` in the task group count. The job's `update` block
+uses the default ["task states"] value to determine if the job is healthy; if
+you configured a Consul [`service`][consul-service] with health checks you
+could use that instead.
+
+```hcl
+job "example" {
+
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count       = 2
+      datacenters = ["west-1"]
+    }
+
+    region "east" {
+      count       = 1
+      datacenters = ["east-1", "east-2"]
+    }
+
+  }
+
+  update {
+    max_parallel      = 1
+    min_healthy_time  = "10s"
+    healthy_deadline  = "2m"
+    progress_deadline = "3m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+
+
+  group "cache" {
+
+    count = 0
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:6.0"
+
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 256
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+## Run the multi-region job
+
+You can run the job from either region.
+
+```shell-session
+$ nomad job run ./multi.nomad
+```
+
+If successful, you should receive output similar to the following.
+
+```plaintext
+Job registration successful
+Evaluation ID: f71cf273-a29e-65e3-bc5b-9710a3c5bc8f
+```
+
+Check the job status from the east region.
+
+```shell-session
+$ nomad job status -region east example
+```
+
+Note that there are no running allocations in the east region,
+and that the status is "pending" because the east region is waiting
+for the west region to complete.
+
+```plaintext
+...
+Latest Deployment
+ID          = d74a086b
+Status      = pending
+Description = Deployment is pending, waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  pending
+west    48fccef3  running
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       true         1        0       0        0          N/A
+
+Allocations
+No allocations placed
+```
+
+Check the job status from the west region.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+You should observe running allocations.
+
+```plaintext
+...
+Latest Deployment
+ID          = 48fccef3
+Status      = running
+Description = Deployment is running
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  pending
+west    48fccef3  running
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       true         2        2       0        0          2020-06-17T13:35:49Z
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+44b3988a  4786abea  cache       0        run      running  14s ago  13s ago
+7c8a2b80  4786abea  cache       0        run      running  13s ago  12s ago
+```
+
+The west region should be healthy 10s after the task state for all tasks
+switches to "running". To observe, run the following status check.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+At this point, the status for the west region will
+transition to "blocked" and the east region's deployment will become
+"running".
+
+```plaintext
+...
+Latest Deployment
+ID          = 48fccef3
+Status      = blocked
+Description = Deployment is complete but waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  running
+west    48fccef3  blocked
+```
+
+Once the east region's deployment has completed, check the status again.
+
+```shell-session
+$ nomad job status -region east example
+```
+
+Both regions should transition to "successful".
+
+```plaintext
+...
+Latest Deployment
+ID          = d74a086b
+Status      = successful
+Description = Deployment completed successfully
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  successful
+west    48fccef3  successful
+```
+
+## Failed deployments
+
+Next, you'll simulate a failed deployment. First, add a new task group that will
+succeed in the west region but fail in the east region.
+
+```hcl
+group "sidecar" {
+
+  # set the reschedule stanza so that we don't have to wait too long
+  # for the deployment to be marked failed
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+
+  task "sidecar" {
+    driver = "docker"
+
+    config {
+      image   = "busybox:1"
+      command = "/bin/sh"
+      args    = ["local/script.sh"]
+    }
+
+    # this script will always fail in the east region
+    template {
+      destination = "local/script.sh"
+      data        = <<EOT
+if [[ ${NOMAD_REGION} == "east" ]]
+then
+echo FAIL
+exit 1
+fi
+echo OK
+sleep 600
+
+EOT
+
+    }
+
+    resources {
+      cpu    = 128
+      memory = 64
+    }
+  }
+}
+```
+
+Next, change the `on_failure` field of the multiregion strategy to
+`"fail_local"`. This will cause only the failed region to be marked as failed.
+
+```hcl
+strategy {
+  max_parallel = 1
+  on_failure   = "fail_local"
+}
+```
+
+Run the job again.
+
+```shell-session
+$ nomad job run ./multi.nomad
+```
+
+The output should indicate success.
+
+```plaintext
+Job registration successful
+Evaluation ID: e878bb98-6b23-c3de-dce1-10ea37c702f7
+```
+
+Now check the status
+
+```shell-session
+$ nomad job status -region west example
+```
+
+As with the previous version of the job, you should see the deployment in the
+west in the "running" status and the deployment in the east in
+"pending". Eventually, the east region deployment will run and then
+fail. Because `on_failure` was set to `"fail_local"`, the west region remains
+in a "blocked" state:
+
+```plaintext
+Latest Deployment
+ID          = f08122e5
+Status      = blocked
+Description = Deployment is complete but waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    8b12b453  failed
+west    f08122e5  blocked
+```
+
+At this point, the west region will remain in the blocked state. You can
+either fix the job and redeploy, or accept the west deployment in its current
+state by using the [`nomad deployment unblock`] command.
+
+```shell-session
+$ nomad deployment unblock -region west f08122e5
+```
+
+If successful, the output will be similar to the following.
+
+```plaintext
+Deployment "f08122e5-fc7e-f450-f61e-81ac48db55cb" unblocked
+```
+
+Check the status again.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+The west region should now be marked as successful:
+
+```plaintext
+...
+Latest Deployment
+ID          = f08122e5
+Status      = successful
+Description = Deployment completed successfully
+
+Multiregion Deployment
+Region  ID        Status
+east    8b12b453  failed
+west    f08122e5  successful
+```
+
+## Learn more about federation
+
+- [Deployment Topology across Multiple Regions][multi-region-topology]
+
+[`multiregion`]: /nomad/docs/job-specification/multiregion
+[federation guide]: //nomad/docs/deploy/clusters/federate-regions
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform
+[server-join]: /nomad/commands/server/join
+[ports-used]: /nomad/docs/deploy/production/requirements#ports-used
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture
+[nomad-server-members]: /nomad/commands/server/members
+[acls-track]: /nomad/docs/secure/acl
+[updates-track]: /nomad/docs/job-declare/strategy/
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+["task states"]: /nomad/docs/job-specification/update#health_check
+[consul-service]: /nomad/docs/job-specification/service
+[alloc-health-api]: /nomad/api-docs/deployments#set-allocation-health-in-deployment
+[`update` stanza]: /nomad/docs/job-specification/update
+[`nomad deployment unblock`]: /nomad/commands/deployment/unblock
+[multi-region-topology]:/nomad/docs/deploy/production/reference-architecture#multi-region
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/nomad-actions.mdx b/content/nomad/v1.10.x/content/docs/job-declare/nomad-actions.mdx
new file mode 100644
index 0000000000..fce75572b9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/nomad-actions.mdx
@@ -0,0 +1,550 @@
+---
+layout: docs
+page_title: Use Nomad actions in jobs
+description: |-
+  Create a Nomad Action in a job to read from a Redis database. Discover
+  how to use Actions for repeatable workflows and indefinitely running
+  workflows.
+---
+
+# Use Nomad actions in jobs
+
+In this tutorial you will create and run Nomad Actions in a job. Actions are commands that a job author writes, and take the same form as [task config][task-config].
+
+```hcl
+action "hello-world" {
+  command = "echo"
+  args    = ["Hello, world!"]
+}
+```
+
+These actions live at Task level within a jobspec and run without variables or interactive input after execution. Like other executable commands, they may self-terminate or run until manually terminated by the running user. Nomad provides the [CLI command][cli-job-actions], [API][api-run-action], and Web UI to interact with Actions within the context of a Job or Task.
+
+## Challenge
+
+In this tutorial, you will modify a Nomad job that runs a Redis instance and create repeatable Nomad Actions to:
+
+- simplify common workflows to add and remove entries from the database
+- monitor and report on attributes of those entries, as well as latency of the Redis instance
+- modify core behaviour of the database
+
+## Prerequisites
+
+- [Nomad v1.7.0 or greater][install-nomad]
+- Nomad dev agent or [Nomad cluster][setup-cluster]
+- [Docker](https://docs.docker.com/engine/install/) installed and available as a task driver
+
+## Build the starting job file
+
+Create a text file called `redis-actions.nomad.hcl` with the following content:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+job "redis-actions" {
+
+  group "cache" {
+    network {
+      port "db" {}
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image   = "redis:7"
+        ports   = ["db"]
+        command = "/bin/sh"
+        args    = ["-c", "redis-server --port ${NOMAD_PORT_db} & /local/db_log.sh"]
+      }
+
+      template {
+        data        = <<EOF
+          #!/bin/sh
+          while true; do
+            echo "$(date): Current DB Size: $(redis-cli -p ${NOMAD_PORT_db} DBSIZE)"
+            sleep 3
+          done
+EOF
+        destination = "local/db_log.sh"
+        perms       = "0755"
+      }
+
+      resources {
+        cpu    = 128
+        memory = 128
+      }
+
+      service {
+        name     = "redis-service"
+        port     = "db"
+        provider = "nomad"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+This job creates a single Redis instance, with a port called "db" that Nomad dynamically assigns and a Nomad service health check in place. The task's [config][jobspec-task-config-block] and [template][jobspec-task-template-block] blocks start the redis server and report on current database size every 3 seconds.
+
+## Write your first Action
+
+If you were a user with management or `alloc-exec` privileges, you could add data to your Redis instance by ssh-ing into the running instance. However, this has several drawbacks:
+- You might have to ssh into the instance several times to add data at different points, requiring you to remember how to do it. Or worse: another operator less familiar with the process may have to do so.
+- There is no auditable record of manual additions. If you need to repeat or scale the workflow, you would have to do so manually.
+- Your Nomad task may have access to Redis using managed secrets or environment variables, but you as a user may not. Passing credentials manually, either to access Redis or ssh into your Nomad instance, opens up a repeated access hole in the security of your workflow.
+
+Instead of `ssh`ing into the box and executing the `redis-cli SET` command over and over again, you will commit it as an action to the jobspec's task. Add the following to the `service` block of the task:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a specific key-value pair ('hello'/'world') to the Redis database
+action "add-key" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} SET hello world; echo 'Key \"hello\" added with value \"world\"'"]
+}
+```
+</CodeBlockConfig>
+
+This action uses the `redis-cli` command to set a key-value pair and then outputs a confirmation message.
+
+Now, submit your job:
+
+```shell-session
+$ nomad job run redis-actions.nomad.hcl
+```
+
+The job will update with a new action available. Use the Nomad CLI to execute it, supplying the job, group, task, and action name:
+
+```shell-session
+$ nomad action \
+  -job=redis-actions \
+  -group=cache \
+  -task=redis \
+add-key
+```
+
+You should see the output described in our action to indicate the key was added:
+
+```shell-session
+OK
+Key "hello" added with value "world"
+```
+
+You've just executed a command defined in the jobspec of your running Nomad job.
+
+## Simulate a repeatable workflow
+
+An action that applies a constant state can be useful (an action that manually clears a cache, or that puts a site into maintenance mode, for example). However, for this example, simulate an action that someone might want to take many times. Instead of a constant key/value, modify the action to randomly generate strings. You can think of this action as a proxy for a real-world scenario where a persistent artifact is saved upon user sign-up, or another public-facing action.
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a random key/value to the Redis database
+action "add-random-key" {
+  command = "/bin/sh"
+  args    = ["-c", "key=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+}
+```
+</CodeBlockConfig>
+
+This will add a random key/value to the database and report back. We can add a second action that differs only in that it prepends "temp_" to the key, to help illustrate further functionality:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a random key/value with a "temp_" prefix to the Redis database
+action "add-random-temporary-key" {
+  command = "/bin/sh"
+  args    = ["-c", "key=temp_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+}
+```
+</CodeBlockConfig>
+
+Like our `add-random-key` action, this new action might be thought of as a simulation of an application generating persistent artifacts. In the case of these temp keys, a real-world scenario might be keys to indicate user sign-up email verification. Soon, we will create a further Action that treats these random keys differently depending on their prefix.
+
+These two actions will populate the database with random data of two different sorts. Now, create an action to view the keys we've added by appending the following code block:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Lists all keys currently stored in the Redis database.
+action "list-keys" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} KEYS '*'"]
+}
+```
+</CodeBlockConfig>
+
+Now, update your job:
+
+```shell-session
+$ nomad job run redis-actions.nomad.hcl
+```
+
+If you have the [Nomad Web UI][web-ui] running, accessing your Job page should show an Actions drop-down:
+
+[![Nomad Job page with Actions dropdown open][actions-dropdown]][actions-dropdown]
+
+Selecting one of those actions will open a fly-out, complete with output from your selected action:
+
+[![Nomad Job page with Actions flyout open][actions-flyout]][actions-flyout]
+
+Next, append a new action block that creates a "safety valve" action to clear the temporary keys from our database. This uses our earlier `add-random-key` and `add-random-temporary-key` actions by differentiating between the artifacts they generated.
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Deletes all keys with a 'temp_' prefix
+action "flush-temp-keys" {
+  command = "/bin/sh"
+  args    = ["-c", <<EOF
+    keys_to_delete=$(redis-cli -p ${NOMAD_PORT_db} --scan --pattern 'temp_*')
+    if [ -n "$keys_to_delete" ]; then
+      # Count the number of keys to delete
+      deleted_count=$(echo "$keys_to_delete" | wc -l)
+      # Execute the delete command
+      echo "$keys_to_delete" | xargs redis-cli -p ${NOMAD_PORT_db} DEL
+    else
+      deleted_count=0
+    fi
+    remaining_keys=$(redis-cli -p ${NOMAD_PORT_db} DBSIZE)
+    echo "$deleted_count temporary keys removed; $remaining_keys keys remaining in database"
+EOF
+  ]
+}
+```
+</CodeBlockConfig>
+
+In a real-world scenario, for example, an action like this might filter and clear automatically-added entries, and report back on remaining keys or time taken to delete them.
+
+You can run this job from the command line in two ways:
+
+1: When your task is running on a single allocation, or you want to perform the action on a random allocation running your task:
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+flush-temp-keys
+```
+
+2: When you want to perform the action on a specific, known allocation, first get its allocation ID:
+
+```shell-session
+$ nomad job status redis-actions
+```
+
+Nomad CLI should show information about the jobspec, including the following:
+
+```
+ID            = redis-actions
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+d841c716  03a56d12  cache       0        run      running  5m4s ago  4m48s ago
+```
+
+Copy the ID from the Allocation displayed and run the following to perform the `flush-temp-keys` action upon it:
+
+```shell-session
+$ nomad action \
+  -alloc=d841c716 \
+  -job=redis-actions \
+flush-temp-keys
+```
+
+If the action being run is not allocation dependent, use the first method. If your job hosted multiple instances of Redis and you need to clear the cache of a specific one, use the second method. In the real world, the method you chose will depend on your goal.
+
+## Actions can impact the running task
+
+Some actions might not affect the current state of the application. For example, processing logs, reporting and sending server statistics, revoking tokens, etc. But, in this example, the action does impact the active state of the task. The Redis task has been writing its `DBSIZE` to `db_log.sh` and logging it every few seconds. Inspect the running job and get its allocation ID. Then, run the following:
+
+```shell-session
+nomad alloc logs <alloc-id>
+```
+
+Nomad outputs the logs for the allocation ID of the job:
+
+```shell-session
+Tue Nov 28 01:23:46 UTC 2023: Current DB Size: 1
+Tue Nov 28 01:23:49 UTC 2023: Current DB Size: 1
+Tue Nov 28 01:23:52 UTC 2023: Current DB Size: 2
+Tue Nov 28 01:23:55 UTC 2023: Current DB Size: 3
+Tue Nov 28 01:23:58 UTC 2023: Current DB Size: 3
+Tue Nov 28 01:24:01 UTC 2023: Current DB Size: 4
+Tue Nov 28 01:24:04 UTC 2023: Current DB Size: 5
+Tue Nov 28 01:24:07 UTC 2023: Current DB Size: 8
+```
+
+Now add another action to impact a more low-level configuration option for our application. Redis lets us turn its persistence to disk on and off. Write an Action to check this and then flip it. Append the following action block:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Toggles saving to disk (RDB persistence). When enabled, allocation logs will indicate a save every 60 seconds.
+action "toggle-save-to-disk" {
+  command = "/bin/sh"
+  args    = ["-c", <<EOF
+    current_config=$(redis-cli -p ${NOMAD_PORT_db} CONFIG GET save | awk 'NR==2');
+    if [ -z "$current_config" ]; then
+      # Enable saving to disk (example: save after 60 seconds if at least 1 key changed)
+      redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "60 1";
+      echo "Saving to disk enabled: 60 seconds interval if at least 1 key changed";
+    else
+      # Disable saving to disk
+      redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "";
+      echo "Saving to disk disabled";
+    fi;
+EOF
+  ]
+}
+```
+</CodeBlockConfig>
+
+Enabling RDB snapshotting with the above will modify the output in your application logs, too.
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+toggle-save-to-disk
+```
+
+Nomad returns a confirmation that the action run and that saving to disk is enabled.
+
+```shell-session
+OK
+Saving to disk enabled: 60 seconds interval if at least 1 key changed
+```
+
+Access your server logs and find the lines that show Redis saving the snapshot:
+
+```shell-session
+Tue Nov 28 01:31:14 UTC 2023: Current DB Size: 12
+28 Nov 01:31:17.800 * 2 changes in 60 seconds. Saving...
+28 Nov 01:31:17.800 * Background saving started by pid 36652
+28 Nov 01:31:17.810 * DB saved on disk
+28 Nov 01:31:17.810 * RDB: 0 MB of memory used by copy-on-write
+28 Nov 01:31:17.902 * Background saving terminated with success
+Tue Nov 28 01:31:17 UTC 2023: Current DB Size: 12
+```
+
+Nomad Actions can impact the state and behaviour of the very task on which they're running. Keeping this in mind can help developers and platform teams separate business and operational logic in their applications.
+
+## Indefinite and self-terminating actions
+
+All of the actions so far have been self-terminating: they execute a command that completes and signals its completion. However, Actions will wait for completion of the desired task, and the Nomad API and Web UI use websockets to facilitate this.
+
+Add an action that runs until you manually stop it with a signal interruption, like `ctrl + c` to observe the latency of the Redis instance:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Performs a latency check of the Redis server.
+# This action is a non-terminating action, meaning it will run indefinitely until it is stopped.
+# Pass a signal interruption (Ctrl-C) to stop the action.
+action "health-check" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} --latency"]
+}
+```
+</CodeBlockConfig>
+
+Submit the job and run the action with the following:
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+  -t=true \
+health-check
+```
+
+The output should indicate the minimum, maximum, and average latency in ms for our Redis instance. Interrupting the signal or closing the websocket will end the action's execution.
+
+[![Non-terminating Nomad Action run via the UI][actions-health-check]][actions-health-check]
+
+## Wrap-up
+
+Find the complete Redis job with actions (with a few extras thrown in) below:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+job "redis-actions" {
+
+  group "cache" {
+    network {
+      port "db" {}
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image   = "redis:7"
+        ports   = ["db"]
+        command = "/bin/sh"
+        args    = ["-c", "redis-server --port ${NOMAD_PORT_db} & /local/db_log.sh"]
+      }
+
+      template {
+        data        = <<EOF
+#!/bin/sh
+while true; do
+  echo "$(date): Current DB Size: $(redis-cli -p ${NOMAD_PORT_db} DBSIZE)"
+  sleep 3
+done
+EOF
+        destination = "local/db_log.sh"
+        perms       = "0755"
+      }
+
+      resources {
+        cpu    = 128
+        memory = 128
+      }
+
+      service {
+        name     = "redis-service"
+        port     = "db"
+        provider = "nomad"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+
+      # Adds a random key/value to the Redis database
+      action "add-random-key" {
+        command = "/bin/sh"
+        args    = ["-c", "key=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+      }
+
+      # Adds a random key/value with a "temp_" prefix to the Redis database
+      action "add-random-temporary-key" {
+        command = "/bin/sh"
+        args    = ["-c", "key=temp_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+      }
+
+      # Lists all keys currently stored in the Redis database.
+      action "list-keys" {
+        command = "/bin/sh"
+        args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} KEYS '*'"]
+      }
+
+      # Performs a latency check of the Redis server.
+      # This action is a non-terminating action, meaning it will run indefinitely until it is stopped.
+      # Pass a signal interruption (Ctrl-C) to stop the action.
+      action "health-check" {
+        command = "/bin/sh"
+        args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} --latency"]
+      }
+
+      # Deletes all keys with a 'temp_' prefix
+      action "flush-temp-keys" {
+        command = "/bin/sh"
+        args    = ["-c", <<EOF
+keys_to_delete=$(redis-cli -p ${NOMAD_PORT_db} --scan --pattern 'temp_*')
+if [ -n "$keys_to_delete" ]; then
+  # Count the number of keys to delete
+  deleted_count=$(echo "$keys_to_delete" | wc -l)
+  # Execute the delete command
+  echo "$keys_to_delete" | xargs redis-cli -p ${NOMAD_PORT_db} DEL
+else
+  deleted_count=0
+fi
+remaining_keys=$(redis-cli -p ${NOMAD_PORT_db} DBSIZE)
+echo "$deleted_count temporary keys removed; $remaining_keys keys remaining in database"
+EOF
+        ]
+      }
+
+      # Toggles saving to disk (RDB persistence). When enabled, allocation logs will indicate a save every 60 seconds.
+      action "toggle-save-to-disk" {
+        command = "/bin/sh"
+        args    = ["-c", <<EOF
+current_config=$(redis-cli -p ${NOMAD_PORT_db} CONFIG GET save | awk 'NR==2');
+if [ -z "$current_config" ]; then
+  # Enable saving to disk (example: save after 60 seconds if at least 1 key changed)
+  redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "60 1";
+  echo "Saving to disk enabled: 60 seconds interval if at least 1 key changed";
+else
+  # Disable saving to disk
+  redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "";
+  echo "Saving to disk disabled";
+fi;
+EOF
+        ]
+      }
+    }
+  }
+}
+```
+</CodeBlockConfig>
+
+Experiment with duplicating and modifying these actions to explore the potential of an actions-based workflow in Nomad.
+
+To further explore how Actions can be used in your workflows, consider the following:
+
+- The examples above are mostly self-contained in that they run in isolation on a single allocation within a job with only one task group and task. Try creating a job with multiple groups and tasks whose actions can talk to one another by way of service discovery.
+- Try using the [GET job actions endpoint][api-list-job-actions] to see a list of actions available to a job and its groups and tasks
+- Try writing an action that takes advantage of Nomad's environment variables: for example, the following actions are illustrative of how an operator might add shortcuts to their Nomad jobs to get a sense of system state:
+
+```hcl
+action "get-alloc-info" {
+  command = "/bin/sh"
+  args    = ["-c",
+    <<EOT
+    nomad alloc status ${NOMAD_ALLOC_ID}
+    EOT
+  ]
+}
+action "get-event-stream" {
+  command = "/usr/bin/curl"
+  args    = ["-s", "localhost:4646/v1/event/stream", " | ", "jq"]
+}
+```
+
+## Clean up
+
+To stop your Nomad actions job, use the Nomad CLI:
+
+```shell-session
+$ nomad job stop redis-actions
+```
+
+The jobspec you wrote will remain on your filesystem, but the resources used by running the job will free up and Nomad will automatically garbage collect the stopped job after awhile.
+
+
+[api-run-action]: /nomad/api-docs/jobs#run-action
+[api-list-job-actions]: /nomad/api-docs/jobs#list-job-actions
+[cli-job-actions]: /nomad/commands/job/action
+[task-config]: /nomad/docs/job-declare/configure-tasks#define-application-arguments
+[web-ui]: /nomad/tutorials/web-ui
+[actions-dropdown]: /img/nomad/actions/actions-dropdown.png
+[actions-flyout]: /img/nomad/actions/actions-flyout.png
+[actions-health-check]: /img/nomad/actions/actions-health-check.png
+[jobspec-task-template-block]: /nomad/docs/job-specification/template
+[jobspec-task-config-block]: /nomad/docs/job-specification/task#config
+[install-nomad]: /nomad/install
+[setup-cluster]: /nomad/tutorials/get-started/gs-start-a-cluster
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/nomad-variables.mdx b/content/nomad/v1.10.x/content/docs/job-declare/nomad-variables.mdx
new file mode 100644
index 0000000000..63a23e3a4a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/nomad-variables.mdx
@@ -0,0 +1,481 @@
+---
+layout: docs
+page_title: Use Nomad variables in tasks
+description: |-
+  Discover how Nomad's workload identity grants tasks automatic read access to
+  certain Nomad variables.
+---
+
+# Use Nomad variables in tasks
+
+In this tutorial you'll access [Nomad Variables][] from tasks via the
+[`template`][] block. Tasks have implicit ACL policies that allow them to access
+their own variables, and you can add job, group, and task fields to ACL policies
+to extend these permissions.
+
+<Note>
+
+ You should always protect access to variables with Access Control
+Lists (ACLs). Writing ACL policies for variables is covered in the [Nomad
+Variables Access Control][] tutorial
+
+</Note>
+
+For complete documentation on the Nomad Variables feature and related concepts,
+see the [Variables reference documentation][], the [Key Management
+documentation][], and the [Workload Identity documentation][]
+
+## Automatic access
+
+The [workload identity][] for each task grants it automatic read and list access
+to variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed
+by the job ID, task group name, and task name.
+
+If you've completed the [Nomad Variables Access Control][] tutorial, you will
+have a "prod" namespace and a token associated with the "prod-ops" policy. If
+not, you can use a management token for this section and create the "prod"
+namespace.
+
+```shell-session
+$ nomad namespace apply -description "production environment" prod
+Successfully applied namespace "prod"!
+```
+
+In this tutorial you'll be working in the "prod" namespace. Set the
+`NOMAD_NAMESPACE` variable so that the command line writes all variables to that
+namespace.
+
+```shell-session
+export NOMAD_NAMESPACE=prod
+```
+
+Create the following variables to see how different jobs, groups, and tasks can
+access them.
+
+```shell-session
+nomad var put nomad/jobs password=passw0rd1
+nomad var put nomad/jobs/example person_to_greet=alice
+nomad var put nomad/jobs/example/web foo=1 bar=2 baz=3
+nomad var put nomad/jobs/example/web/httpd port=8001
+nomad var put nomad/jobs/example/web/sidecar password=passw0rd2
+```
+
+Create the following job specification. This job `example` has one group `web`
+with two tasks, `httpd` and `sidecar`. It includes templates that access all the
+variables you wrote earlier.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "web" {
+
+    network {
+      port "www" {
+        to = 8001
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "httpd"
+        args    = ["-v", "-f", "-p", "0.0.0.0:${PORT}", "-h", "${NOMAD_ALLOC_DIR}/data"]
+        ports   = ["www"]
+      }
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/env.txt"
+        env         = true
+        data        = <<EOT
+PORT={{ with nomadVar "nomad/jobs/example/web/httpd" }}{{ .port }}{{ end }}
+EOT
+      }
+
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/index.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+    {{- with nomadVar "nomad/jobs/example/web" -}}
+    {{- range $k, $v := . }}
+      <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+EOT
+      }
+    }
+
+    task "sidecar" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "sleep"
+        args    = ["300"]
+      }
+
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/sidecar.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      {{- range nomadVarList "nomad" }}
+      <li>{{ .Path }}</li>
+      {{- end }}
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+EOT
+      }
+    }
+  }
+}
+```
+
+Run this job and wait for the deployment to complete and note the allocation
+short ID. In this example, the allocation short ID is `ec6dc2e4`.
+
+```shell-session
+$ nomad job run ./example.nomad.hcl
+==> 2022-09-19T11:42:20-04:00: Monitoring evaluation "0d8a7587"
+    2022-09-19T11:42:20-04:00: Evaluation triggered by job "example"
+    2022-09-19T11:42:20-04:00: Evaluation within deployment: "b58da4d8"
+    2022-09-19T11:42:20-04:00: Allocation "ec6dc2e4" created: node "9063a25f", group "web"
+    2022-09-19T11:42:20-04:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-09-19T11:42:20-04:00: Evaluation "0d8a7587" finished with status "complete"
+==> 2022-09-19T11:42:20-04:00: Monitoring deployment "b58da4d8"
+  ✓ Deployment "b58da4d8" successful
+
+    2022-09-19T11:42:32-04:00
+    ID          = b58da4d8
+    Job ID      = example
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    web         1        1       1        0          2022-09-19T15:52:31Z
+```
+
+First, use `nomad alloc exec` to enter the `httpd` task and show the command
+line arguments for the processes running in the container.
+
+```shell-session
+$ nomad alloc exec -task httpd ec6dc2e4 ps -ef
+PID   USER     TIME  COMMAND
+    1 root      0:00 httpd -v -f -p 0.0.0.0:8001 -h /alloc/data
+    8 root      0:00 ps -ef
+```
+
+Note that the port number has been interpolated with environment variable that
+you rendered in the following template by using the `env` field:
+
+```hcl
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/env.txt"
+        env         = true
+        data        = <<EOT
+PORT={{ with nomadVar "nomad/jobs/example/web/httpd" }}{{ .port }}{{ end }}
+EOT
+      }
+```
+
+Visit the web page being served by the `httpd` task at port 8001. If you are
+running Nomad on macOS and are using Docker for Mac to run Docker tasks, you can
+reach the webpage at your localhost address.
+
+If you are deploying to a remote Linux host or Vagrant box, you can use the IP
+address found when you run `nomad alloc status`:
+
+```shell-session
+$ nomad alloc status ec6dc2e4
+...
+Allocation Addresses (mode = "bridge"):
+Label  Dynamic  Address
+*www   yes      127.0.0.1:21976 -> 8001
+```
+
+You can also use `curl`:
+
+```shell-session
+
+$ curl 127.0.0.1:21976
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+      <li>bar=2</li>
+      <li>baz=3</li>
+      <li>foo=1</li>
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+```
+
+This corresponds to this template block that reads the variable accessible to
+the job "example" at `nomad/jobs/example` and the variable accessible to the
+group "web" within the job "example" at `nomad/jobs/example/web`.
+
+```hcl
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/index.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+    {{- with nomadVar "nomad/jobs/example/web" -}}
+    {{- range $k, $v := . }}
+      <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+EOT
+```
+
+Visit the webpage rendered by the sidecar task:
+
+```shell-session
+curl -s http://127.0.0.1:21976/sidecar.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      <li>nomad/jobs</li>
+      <li>nomad/jobs/example</li>
+      <li>nomad/jobs/example/web</li>
+      <li>nomad/jobs/example/web/sidecar</li>
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+```
+
+This corresponds to the following template block, which lists all the variables
+this task has access to in its own namespace:
+
+```
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/sidecar.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      {{- range nomadVarList "nomad" }}
+      <li>{{ .Path }}</li>
+      {{- end }}
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+EOT
+      }
+```
+
+Note that `nomad/jobs/example/httpd` does not appear in the list. If you added a
+variable to `nomad/jobs/another-example` it would also not appear in the
+list. If you added `nomad/jobs/example/sidecar` to a different namespace, it
+would not appear in the list.
+
+## Workload associated ACL policies
+
+You may need to give tasks access to variables that are on paths shared by many
+jobs. For example, all jobs in your cluster may need a shared API key for a
+third-party monitoring vendor. You can provide access to these variables secrets
+by creating policies associated with the task's [workload identity][]. See
+[Workload Associated ACL Policies][] for full documentation.
+
+Create a new namespace named `shared`.
+
+```shell-session
+$ nomad namespace apply shared
+Successfully applied namespace "shared"!
+```
+
+Create a variable named `vendor/foo/bar` in the `shared` namespace.
+
+```shell-session
+nomad var put -namespace shared vendor/foo/bar user=me password=passw0rd1
+```
+
+To give the task you wrote earlier access to all secrets in the `shared`
+namespace, you can create the following policy file `shared-policy.hcl`.
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Now, create the policy and associate it with the `httpd` task in the web group
+of the example job, specifying the appropriate flags on the `nomad acl policy
+apply` command.
+
+```shell-session
+nomad acl policy apply \
+   -namespace prod -job example -group web -task httpd \
+   shared-policy ./shared-policy.hcl
+```
+
+You can view the policy to see that it's associated with the workload.
+
+```shell-session
+$ nomad acl policy info shared-policy
+Name        = shared-policy
+Description = <none>
+CreateIndex = 390
+ModifyIndex = 390
+
+Associated Workload
+Namespace = prod
+JobID     = example
+Group     = web
+Task      = httpd
+
+Rules
+
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Change the template for the `httpd` task.
+
+```hcl
+      template {
+        destination = "alloc/index.html"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    {{- with nomadVar "vendor/foo/bar@shared" }}
+    {{- range $k, $v := . }}
+    <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+  </body>
+</html>
+EOT
+```
+
+Update the job and wait for the deployment to complete.
+
+```shell-session
+nomad job run ./example.nomad.hcl
+```
+
+Visit the webpage served by the `httpd` task.
+
+```shell-session
+curl -s http://127.0.0.1:8001/index.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    <li>password=passw0rd1</li>
+    <li>user=me</li>
+    </ul>
+  </body>
+</html>
+```
+
+## Updating task variables
+
+You can update the value of a variable and it will be updated in the templates
+that read that value.
+
+Update the shared variable so that the "password" field changes.
+
+```shell-session
+nomad var put -namespace shared -force vendor/foo/bar user=me password=passw0rd2
+```
+
+After a few moments, the value will be updated on the template.
+
+```shell-session
+curl -s http://127.0.0.1:8001/index.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    <li>password=passw0rd2</li>
+    <li>user=me</li>
+    </ul>
+  </body>
+</html>
+```
+
+You can use the template
+[`change_mode`](/nomad/docs/job-specification/template#change_mode)
+to specify Nomad's behavior when a value changes.
+
+## Next steps
+
+Because Nomad Variables use functions in the template block to emit data to
+Nomad jobs, consider learning more about templates in Nomad with [Nomad Pack](/nomad/tools/nomad-pack).
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[Nomad Variables Access Control]: /nomad/tutorials/variables/variables-acls
+[Variables reference documentation]: /nomad/docs/concepts/variables
+[Key Management documentation]: /nomad/docs/manage/key-management
+[Workload Identity documentation]: /nomad/docs/concepts/workload-identity
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`template`]: /nomad/docs/job-specification/template
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/strategy/blue-green-canary.mdx b/content/nomad/v1.10.x/content/docs/job-declare/strategy/blue-green-canary.mdx
new file mode 100644
index 0000000000..b794016942
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/strategy/blue-green-canary.mdx
@@ -0,0 +1,474 @@
+---
+layout: docs
+page_title: Configure blue-green and canary deployments
+description: |-
+  Set up and configure Nomad jobs to deploy using the blue-green and
+  canary deployment strategies.
+---
+
+# Configure blue-green and canary deployments
+
+Sometimes [rolling updates] do not offer the required flexibility for updating
+an application in production. Often organizations prefer to put a "canary" build
+into production or utilize a technique known as a "blue/green" deployment to
+ensure a safe application roll-out to production while minimizing downtime.
+
+## Blue/Green deployments
+
+Blue/Green deployments have several other names including Red/Black or A/B, but
+the concept is generally the same. In a blue/green deployment, there are two
+application versions. Only one application version is active at a time, except
+during the transition phase from one version to the next. The term "active"
+tends to mean "receiving traffic" or "in service".
+
+Imagine a hypothetical API server which has five instances deployed to
+production at version 1.3, and you want to safely update to version 1.4. You
+want to create five new instances at version 1.4 and in the case that they are
+operating correctly you want to promote them and take down the five versions
+running 1.3. In the event of failure, you can quickly rollback to 1.3.
+
+To start, you examine your job which is running in production:
+
+```hcl
+job "docs" {
+  # ...
+
+  group "api" {
+    count = 5
+
+    update {
+      max_parallel     = 1
+      canary           = 5
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+      auto_revert      = true
+      auto_promote     = false
+    }
+
+    task "api-server" {
+      driver = "docker"
+
+      config {
+        image = "api-server:1.3"
+      }
+    }
+  }
+}
+```
+
+Notice that the job has an `update` stanza with the `canary` count equal to the
+desired count. This allows a Nomad job to model blue/green deployments. When you
+change the job to run the "api-server:1.4" image, Nomad will create five new
+allocations while leaving the original "api-server:1.3" allocations running.
+
+Observe how this works by changing the image to run the new version:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+  group "api" {
+    task "api-server" {
+      config {
+-       image = "api-server:1.3"
++       image = "api-server:1.4"
+```
+
+Next, plan these changes. Save the modified jobspec with the new version of `api-server` to a file name `docs.nomad.hcl`.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "api" (5 canary, 5 ignore)
+  +/- Task: "api-server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "api-server:1.3" => "api-server:1.4"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Run the changes.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+## ...
+```
+
+The plan output states that Nomad is going to create five canaries running the
+"api-server:1.4" image and ignore all the allocations running the older image.
+Now, if you examine the status of the job you will note that both the blue
+("api-server:1.3") and green ("api-server:1.4") set are running.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         10       0       0         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         false     5        5         5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+6d8eec42  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+7051480e  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+36c6610f  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+410ba474  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+85662a7a  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+```
+
+Now that the new version is running in production, you can route traffic to it
+and validate that it is working properly. If so, you would promote the
+deployment and Nomad would stop allocations running the older version. If not,
+you would either troubleshoot one of the running containers or destroy the new
+containers by failing the deployment.
+
+### Promote the deployment
+
+After deploying the new image along side the old version you have determined it
+is functioning properly and you want to transition fully to the new version.
+Doing so is as simple as promoting the deployment:
+
+```shell-session
+$ nomad deployment promote 32a080c1
+==> Monitoring evaluation "61ac2be5"
+    Evaluation triggered by job "docs"
+    Evaluation within deployment: "32a080c1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61ac2be5" finished with status "complete"
+```
+
+If you inspect the job's status, you can observe that after promotion, Nomad
+stopped the older allocations and is only running the new one. This now
+completes the blue/green deployment.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       5         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         true      5        5         5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+6d8eec42  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+7051480e  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+36c6610f  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+410ba474  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+85662a7a  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+```
+
+### Fail a deployment
+
+After deploying the new image alongside the old version you have determined it
+is not functioning properly and you want to roll back to the old version. Doing
+so is as simple as failing the deployment:
+
+```shell-session
+$ nomad deployment fail 32a080c1
+Deployment "32a080c1-de5a-a4e7-0218-521d8344c328" failed. Auto-reverted to job version 0.
+
+==> Monitoring evaluation "6840f512"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "32a080c1"
+    Allocation "0ccb732f" modified: node "36e7a123", group "cache"
+    Allocation "64d4f282" modified: node "36e7a123", group "cache"
+    Allocation "664e33c7" modified: node "36e7a123", group "cache"
+    Allocation "a4cb6a4b" modified: node "36e7a123", group "cache"
+    Allocation "fdd73bdd" modified: node "36e7a123", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6840f512" finished with status "complete"
+```
+
+After failing the deployment, check the job's status. Confirm that Nomad has
+stopped the new allocations and is only running the old ones, and that the working
+copy of the job has reverted back to the original specification running "api-server:1.3".
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       5         0
+
+Latest Deployment
+ID          = 6f3f84b3
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy
+cache       true         5        5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+27dc2a42  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+5b7d34bb  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+983b487d  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+d1cbf45a  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+d6b46def  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+0ccb732f  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+64d4f282  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+664e33c7  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+a4cb6a4b  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+fdd73bdd  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+```
+
+```shell-session
+$ nomad job deployments docs
+ID        Job ID   Job Version  Status      Description
+6f3f84b3  example  2            successful  Deployment completed successfully
+32a080c1  example  1            failed      Deployment marked as failed - rolling back to job version 0
+c4c16494  example  0            successful  Deployment completed successfully
+```
+
+## Deploy with canaries
+
+Canary updates are a useful way to test a new version of a job before beginning
+a rolling update. The `update` stanza supports setting the number of canaries
+the job operator would like Nomad to create when the job changes via the
+`canary` parameter. When the job specification is updated, Nomad creates the
+canaries without stopping any allocations from the previous job.
+
+This pattern allows operators to achieve higher confidence in the new job
+version because they can route traffic, examine logs, etc, to determine the new
+application is performing properly.
+
+```hcl
+job "docs" {
+  # ...
+
+  group "api" {
+    count = 5
+
+    update {
+      max_parallel     = 1
+      canary           = 1
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+      auto_revert      = true
+      auto_promote     = false
+    }
+
+    task "api-server" {
+      driver = "docker"
+
+      config {
+        image = "api-server:1.3"
+      }
+    }
+  }
+}
+```
+
+In the example above, the `update` stanza tells Nomad to create a single canary
+when the job specification is changed.
+
+You can experience how this behaves by changing the image to run the new
+version:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+  group "api" {
+    task "api-server" {
+      config {
+-       image = "api-server:1.3"
++       image = "api-server:1.4"
+```
+
+Next, plan these changes.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "api" (1 canary, 5 ignore)
+  +/- Task: "api-server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "api-server:1.3" => "api-server:1.4"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+
+$ nomad job run docs.nomad.hcl
+# ...
+```
+
+Run the changes.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+## ...
+```
+
+Note from the plan output, Nomad is going to create one canary that will run the
+"api-server:1.4" image and ignore all the allocations running the older image.
+After running the job, The `nomad status` command output shows that the canary
+is running along side the older version of the job:
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         6        0       0         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         false     5        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+85662a7a  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+```
+
+Now if you promote the canary, this will trigger a rolling update to replace the
+remaining allocations running the older image. The rolling update will happen at
+a rate of `max_parallel`, so in this case, one allocation at a time.
+
+```shell-session
+$ nomad deployment promote 37033151
+==> Monitoring evaluation "37033151"
+    Evaluation triggered by job "docs"
+    Evaluation within deployment: "ed28f6c2"
+    Allocation "f5057465" created: node "f6646949", group "cache"
+    Allocation "f5057465" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37033151" finished with status "complete"
+```
+
+Check the status.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 20:28:59 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       2         0
+
+Latest Deployment
+ID          = ed28f6c2
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         true      5        1         2       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+f5057465  f6646949  api         1        run      running   07/26/17 20:29:23 UTC
+b1c88d20  f6646949  api         1        run      running   07/26/17 20:28:59 UTC
+1140bacf  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+1958a34a  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+4bda385a  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+62d96f06  f6646949  api         0        stop     complete  07/26/17 20:28:37 UTC
+f58abbb2  f6646949  api         0        stop     complete  07/26/17 20:28:37 UTC
+```
+
+Alternatively, if the canary was not performing properly, you could abandon the
+change using the `nomad deployment fail` command, similar to the blue/green
+example.
+
+[rolling updates]: /nomad/docs/job-declare/strategy/rolling
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/strategy/index.mdx b/content/nomad/v1.10.x/content/docs/job-declare/strategy/index.mdx
new file mode 100644
index 0000000000..fc78f08b6c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/strategy/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Job deployment strategies
+description: |-
+  Discover common patterns to update running jobs in Nomad, including rolling updates, blue-green deployments, and canary deployments. Nomad  provides built-in support for each strategy.
+---
+
+# Job deployment strategies
+
+Most applications are long-lived and require updates over time. Whether you are
+deploying a new version of your web application or upgrading to a new version of
+Redis, Nomad has built-in support for rolling, blue/green, and canary updates.
+When a job specifies a rolling update, Nomad uses task state and health check
+information in order to detect allocation health and minimize or eliminate
+downtime. This section and subsections will explore how to do so safely with
+Nomad.
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/strategy/rolling.mdx b/content/nomad/v1.10.x/content/docs/job-declare/strategy/rolling.mdx
new file mode 100644
index 0000000000..667f9e5be7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/strategy/rolling.mdx
@@ -0,0 +1,323 @@
+---
+layout: docs
+page_title: Configure rolling updates
+description: |-
+  Enable rolling updates for a Nomad job, inspect the deployment, and set up
+  Nomad to automatically revert failed deployments to a previous working
+  version.
+---
+
+# Configure rolling updates
+
+Nomad supports rolling updates as a first class feature. To enable rolling
+updates a job or task group is annotated with a high-level description of the
+update strategy using the [`update` stanza]. Under the hood, Nomad handles
+limiting parallelism, interfacing with Consul to determine service health and
+even automatically reverting to an older, healthy job when a deployment fails.
+
+## Enable rolling updates for job
+
+Rolling updates are enabled by adding the [`update` stanza] to the job
+specification. The `update` stanza may be placed at the job level or in an
+individual task group. When placed at the job level, the update strategy is
+inherited by all task groups in the job. When placed at both the job and group
+level, the `update` stanzas are merged, with group stanzas taking precedence
+over job level stanzas. There is more information about
+[inheritance][update-stanza-inheritance] in the `update` stanza documentation.
+
+```hcl
+job "geo-api-server" {
+  # ...
+
+  group "api-server" {
+    count = 6
+
+    # Add an update stanza to enable rolling updates of the service
+    update {
+      max_parallel     = 2
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+    }
+
+    task "server" {
+      driver = "docker"
+
+      config {
+        image = "geo-api-server:0.1"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+In this example, by adding the simple `update` stanza to the "api-server" task
+group, you inform Nomad that updates to the group should be handled with a
+rolling update strategy.
+
+Thus when a change is made to the job file that requires new allocations to be
+made, Nomad will deploy 2 allocations at a time and require that the allocations
+be running in a healthy state for 30 seconds before deploying more versions of the
+new group.
+
+By default Nomad determines allocation health by ensuring that all tasks in the
+group are running and that any [service check] the tasks register are passing.
+
+## Check the planned changes
+
+Suppose you make a change to a file to update the version of a Docker container
+that is configured with the same rolling update strategy from above.
+
+```diff
+@@ -2,6 +2,8 @@ job "geo-api-server" {
+   group "api-server" {
+     task "server" {
+       driver = "docker"
+
+       config {
+-        image = "geo-api-server:0.1"
++        image = "geo-api-server:0.2"
+```
+
+The [`nomad job plan` command] allows you to visualize the series of steps the
+scheduler would perform. You can analyze this output to confirm it is correct:
+
+```shell-session
+$ nomad job plan geo-api-server.nomad.hcl
++/- Job: "geo-api-server"
++/- Task Group: "api-server" (2 create/destroy update, 4 ignore)
+  +/- Task: "server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "geo-api-server:0.1" => "geo-api-server:0.2"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 geo-api-server.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Here you can observe that Nomad will begin a rolling update by creating and
+destroying two allocations first; for the time being ignoring four of the old
+allocations, consistent with the configured `max_parallel` count.
+
+## Inspect a deployment
+
+After running the plan you can submit the updated job by running `nomad run`.
+Once run, Nomad will begin the rolling update of the service by placing two
+allocations at a time of the new job and taking two of the old jobs down.
+
+You can inspect the current state of a rolling deployment using `nomad status`:
+
+```shell-session
+$ nomad status geo-api-server
+ID            = geo-api-server
+Name          = geo-api-server
+Submit Date   = 07/26/17 18:08:56 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api-server  0       0         6        0       4         0
+
+Latest Deployment
+ID          = c5b34665
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+api-server  6        4       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+14d288e8  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a134f73c  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a2574bb6  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+496e7aa2  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+9fc96fcc  f7b1ee08  api-server  0        run      running   07/26/17 18:04:30 UTC
+2521c47a  f7b1ee08  api-server  0        run      running   07/26/17 18:04:30 UTC
+6b794fcb  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+9bc11bd7  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+691eea24  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+af115865  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+```
+
+The output indicates that Nomad has created a deployment to conduct the rolling
+update from job version 0 to 1. It has placed four instances of the new job and
+has stopped four of the old instances. Consult the list of deployed allocations,
+and note that Nomad has placed four instances of job version 1 but only
+considers 2 of them healthy. This is because the two newest placed allocations
+haven't been healthy for the required 30 seconds yet.
+
+Wait for the deployment to complete, and then re-issue the command. You will
+receive output similar to the following:
+
+```shell-session
+$ nomad status geo-api-server
+ID            = geo-api-server
+Name          = geo-api-server
+Submit Date   = 07/26/17 18:08:56 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         6        0       6         0
+
+Latest Deployment
+ID          = c5b34665
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       6        6       6        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+d42a1656  f7b1ee08  api-server  1        run      running   07/26/17 18:10:10 UTC
+401daaf9  f7b1ee08  api-server  1        run      running   07/26/17 18:10:00 UTC
+14d288e8  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a134f73c  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a2574bb6  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+496e7aa2  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+9fc96fcc  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+2521c47a  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+6b794fcb  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+9bc11bd7  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+691eea24  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+af115865  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+```
+
+Nomad has successfully transitioned the group to running the updated canary and
+did so with no downtime to your service by ensuring only two allocations were
+changed at a time and the newly placed allocations ran successfully. Had any of
+the newly placed allocations failed their health check, Nomad would have aborted
+the deployment and stopped placing new allocations. If configured, Nomad can
+automatically revert back to the old job definition when the deployment fails.
+
+## Use auto-revert on failed deployments
+
+In the case you do a deployment in which the new allocations are unhealthy,
+Nomad will fail the deployment and stop placing new instances of the job. It
+optionally supports automatically reverting back to the last stable job version
+on deployment failure. Nomad keeps a history of submitted jobs and whether the
+job version was stable. A job is considered stable if all its allocations are
+healthy.
+
+To enable this, add the `auto_revert` parameter to the `update` stanza:
+
+```hcl
+update {
+  max_parallel     = 2
+  min_healthy_time = "30s"
+  healthy_deadline = "10m"
+
+  # Enable automatically reverting to the last stable job on a failed
+  # deployment.
+  auto_revert = true
+}
+```
+
+Now imagine you want to update your image to "geo-api-server:0.3" but you instead
+update it to the below and run the job:
+
+```diff
+@@ -2,6 +2,8 @@ job "geo-api-server" {
+   group "api-server" {
+     task "server" {
+       driver = "docker"
+
+       config {
+-        image = "geo-api-server:0.2"
++        image = "geo-api-server:0.33"
+```
+
+Running `nomad job deployments` will show that the deployment fails, and Nomad
+auto-reverted to the last stable job:
+
+```shell-session
+$ nomad job deployments geo-api-server
+ID        Job ID          Job Version  Status      Description
+0c6f87a5  geo-api-server  3            successful  Deployment completed successfully
+b1712b7f  geo-api-server  2            failed      Failed due to unhealthy allocations - rolling back to job version 1
+3eee83ce  geo-api-server  1            successful  Deployment completed successfully
+72813fcf  geo-api-server  0            successful  Deployment completed successfully
+```
+
+Nomad job versions increment monotonically. Even though Nomad reverted to the
+job specification at version 1, it creates a new job version. You can observe the
+differences between a job's versions and how Nomad auto-reverted the job using
+the `job history` command:
+
+```shell-session
+$ nomad job history -p geo-api-server
+Version     = 3
+Stable      = true
+Submit Date = 07/26/17 18:44:18 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.33" => "geo-api-server:0.2"
+        }
+
+Version     = 2
+Stable      = false
+Submit Date = 07/26/17 18:45:21 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.2" => "geo-api-server:0.33"
+        }
+
+Version     = 1
+Stable      = true
+Submit Date = 07/26/17 18:44:18 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.1" => "geo-api-server:0.2"
+        }
+
+Version     = 0
+Stable      = true
+Submit Date = 07/26/17 18:43:43 UTC
+```
+
+This output describes the process of a reverted deployment. Starting at the end
+of the output and working backwards, Nomad shows that version 0 was submitted.
+Next, version 1 was an image change from 0.1 to 0.2 of geo-api-server and was
+flagged as stable. Version 2 of the job attempted to update geo-api-server from
+0.2 to 0.33; however, the deployment failed and never became stable. Finally,
+version 3 of the job is created when Nomad automatically reverts the failed
+deployment and redeploys the last healthy version--geo-api-server version 0.2.
+
+[`nomad job plan` command]: /nomad/commands/job/plan
+[`update` stanza]: /nomad/docs/job-specification/update
+[service check]: /nomad/docs/job-specification/check
+[update-stanza-inheritance]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-dependencies.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-dependencies.mdx
new file mode 100644
index 0000000000..9a7cfe0688
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-dependencies.mdx
@@ -0,0 +1,385 @@
+---
+layout: docs
+page_title: Configure task dependencies
+description: |-
+  Create, configure, and run two jobs to use init and sidecar tasks. Create a dependency between the jobs and discover how to model complex workload dependency trees.
+---
+
+# Configure task dependencies
+
+
+Nomad task dependencies provide the ability to define prestart tasks.
+
+Prestart tasks have two patterns: init tasks and sidecar tasks. Init
+tasks are tasks that must run to completion before the main workload is started.
+They are commonly used to download assets or to create necessary tables for an
+extract-transform-load (ETL) job. Sidecar tasks are started before main workload
+starts and run for the lifetime of the main workload. Typical sidecars tasks are
+log forwarders, proxies, and for platform abstractions. This tutorial demonstrates
+an init task.
+
+You can create an init task by adding a [`lifecycle` stanza] with `hook` set to
+`prestart` and `sidecar` to `false` as below.
+
+```hcl
+      lifecycle {
+        hook    = "prestart"
+        sidecar = false
+      }
+```
+
+You can model complex job dependency trees by using one or more init tasks to
+delay the job's main tasks from running until a condition is met. In this case,
+until a service is available and advertised in Consul.
+
+In this tutorial you will work with several Nomad objects:
+
+- **mock-app** - a job file that contains two tasks
+
+  - **await-mock-service** - an init task that will wait infinitely for a
+    service named "mock-service" to be advertised over the Consul DNS API. Once
+    found, it will exit successfully.
+
+  - **mock-app-container** - the main workload task that is dependent on the
+    "mock-service" service.
+
+- **mock-service** - a job that contains one task which advertises a service
+  named "mock-service". This is provided as a Nomad job as a convenience, but
+  could be replaced by any means of registering a service named "mock-service"
+  in Consul, like the CLI or API.
+
+In this guide, you will complete the following actions:
+
+- Deploy the "mock-app" job.
+
+- Verify that the "mock-app-container" task remains in pending and unstarted.
+
+- Start the "mock-service" job.
+
+- Verify that the "await-mock-service" container completes successfully and that
+  the "mock-app-container" task starts.
+
+## Prerequisites
+
+To complete this tutorial you will need:
+
+- a Nomad cluster and at least one Consul server.
+- Nomad v0.11.0 or greater
+
+If you do not have an existing Nomad cluster, you can learn how to deploy
+on using the [Install Nomad] guide. Similarly, if you do not have an
+existing Consul datacenter, you can learn how to deploy Consul with the
+[Install Consul] guide.
+
+## Create the mock-app job file
+
+This example uses a looping script, in the `config` stanza, to mock service
+payloads.
+
+Create an HCL file named `mock-app.nomad.hcl` with the following content.
+
+```hcl
+job "mock-app" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mock-app" {
+    # disable deployments
+    update {
+      max_parallel = 0
+    }
+
+    task "await-mock-service" {
+      driver = "docker"
+
+      config {
+        image        = "busybox:1.28"
+        command      = "sh"
+        args         = ["-c", "echo -n 'Waiting for service'; until nslookup mock-service.service.consul 2>&1 >/dev/null; do echo '.'; sleep 2; done"]
+        network_mode = "host"
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+
+      lifecycle {
+        hook    = "prestart"
+        sidecar = false
+      }
+    }
+
+    task "mock-app-container" {
+      driver = "docker"
+
+      config {
+        image   = "busybox"
+        command = "sh"
+        args    = ["-c", "echo The app is running! && sleep 3600"]
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+The job contains two tasks—"await-mock-service" and "mock-app". The
+"await-mock-service" task is configured to busy-wait until the "mock-service"
+service is advertised in Consul. For this guide, this will not happen until you
+run the `mock-service.nomad.hcl` job. In a more real-world case, this could be any
+service dependency that advertises itself in Consul.
+
+You can use this pattern to model more complicated chains of service dependency
+by including more await-style workloads.
+
+### Ensure that name resolution works properly
+
+Since the "await-mock-service" task uses nslookup inside of a Docker container,
+you will need to ensure that your container can perform lookups against your
+Consul DNS API endpoint. This tutorial uses `network_mode = host` to allow the
+container to use the Nomad client nodes DNS resolution pathway.
+
+The nslookup application will only perform queries on the standard DNS port
+(53). You might need to use an application to forward requests from port 53 to
+the Consul DNS API port—port 8600 by default. You can learn several ways to
+accomplish this forwarding in the [Forward DNS] Learn guide.
+
+You could also add a `dns_servers` value to the config stanza of the
+"await-mock-service" task in the mock-app.nomad.hcl file to direct the query to a
+DNS server directly that meets the above criteria.
+
+## Run the mock-app job
+
+Run `nomad run mock-app.nomad.hcl`.
+
+```shell-session
+$ nomad run mock-app.nomad.hcl
+```
+
+The job will launch and provide you an allocation ID in the output.
+
+```shell-session
+$ nomad run mock-app.nomad.hcl
+==> Monitoring evaluation "01c73d5a"
+    Evaluation triggered by job "mock-app"
+    Allocation "3044dda0" created: node "f26809e6", group "mock-app"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "01c73d5a" finished with status "complete"
+```
+
+## Verify mock-app-container is pending
+
+Run the `nomad alloc status` command with the provided allocation ID.
+
+```shell-session
+$ nomad alloc status 3044dda0
+```
+
+The `nomad alloc status` command provides you with useful information about the resource. For this guide, focus on the status
+of each task. Each task's status is output in lines that look like `Task "await-mock-service" is "running"`.
+
+```shell-session
+$ nomad alloc status 3044dda0
+ID                  = 3044dda0-8dc1-1bac-86ea-66a3557c67d3
+Eval ID             = 01c73d5a
+Name                = mock-app.mock-app[0]
+Node ID             = f26809e6
+Node Name           = nomad-client-2.node.consul
+Job ID              = mock-app
+Job Version         = 0
+Client Status       = running
+Client Description  = Tasks are running
+Desired Status      = run
+Desired Description = <none>
+Created             = 43s ago
+Modified            = 42s ago
+
+Task "await-mock-service" (prestart) is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+3/200 MHz  80 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:07:26Z
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:07:26-04:00  Started     Task started by client
+2020-03-18T13:07:26-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+
+Task "mock-app-container" is "pending"
+Task Resources
+CPU      Memory   Disk     Addresses
+200 MHz  128 MiB  300 MiB
+
+Task Events:
+Started At     = N/A
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type      Description
+2020-03-18T13:07:26-04:00  Received  Task received by client
+```
+
+Notice that the await-mock-service task is running and that the
+"mock-app-container" task is pending. The "mock-app-container" task will remain
+in pending until the "await-mock-service" task completes successfully.
+
+## Create the mock-service job file
+
+Create a file named `mock-service.nomad.hcl` with the following content.
+
+```hcl
+job "mock-service" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mock-service" {
+    task "mock-service" {
+      driver = "docker"
+
+      config {
+        image   = "busybox"
+        command = "sh"
+        args    = ["-c", "echo The service is running! && while true; do sleep 2; done"]
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+
+      service {
+        name = "mock-service"
+      }
+    }
+  }
+}
+
+```
+
+This job advertises the "mock-service" service in Consul. When run, this
+will allow the await-mock-service task to complete successfully and let
+the "mock-app-container" task start up.
+
+## Start mock-service job
+
+Run `nomad run mock-service.nomad.hcl`.
+
+```shell-session
+$ nomad run mock-service.nomad.hcl
+```
+
+Nomad will start the job and return information about the scheduling information.
+
+```shell-session
+$ nomad run mock-service.nomad
+==> Monitoring evaluation "f31f8eb1"
+    Evaluation triggered by job "mock-service"
+    Allocation "d7767adf" created: node "f26809e6", group "mock-service"
+    Evaluation within deployment: "3d86e09a"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "f31f8eb1" finished with status "complete"
+```
+
+## Verify mock-app-container is running
+
+Finally, check the output of the `nomad alloc status` command again to check the
+task statuses. Use the allocation ID from when you ran the "mock-app" job.
+
+```shell-session
+$ nomad alloc status 3044dda0
+```
+
+Again, focus on the task status lines for "await-mock-service" and
+"mock-app-container".
+
+```plaintext
+ID                  = 3044dda0-8dc1-1bac-86ea-66a3557c67d3
+Eval ID             = 01c73d5a
+Name                = mock-app.mock-app[0]
+Node ID             = f26809e6
+Node Name           = nomad-client-2.node.consul
+Job ID              = mock-app
+Job Version         = 0
+Client Status       = running
+Client Description  = Tasks are running
+Desired Status      = run
+Desired Description = <none>
+Created             = 21m38s ago
+Modified            = 7m27s ago
+
+Task "await-mock-service" (prestart) is "dead"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/200 MHz  80 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:07:26Z
+Finished At    = 2020-03-18T17:21:35Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:21:35-04:00  Terminated  Exit Code: 0
+2020-03-18T13:07:26-04:00  Started     Task started by client
+2020-03-18T13:07:26-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+
+Task "mock-app-container" is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/200 MHz  32 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:21:37Z
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:21:37-04:00  Started     Task started by client
+2020-03-18T13:21:35-04:00  Driver      Downloading image
+2020-03-18T13:21:35-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+```
+
+Notice, the "await-mock-service" task is dead and based on the "Recent Events"
+table terminated with "Exit Code: 0". This indicates that it completed
+successfully. The "mock-app-container" task has now transitioned to the
+"running" status and the container is running.
+
+## Next steps
+
+Now that you have completed this guide, you have experimented with using Nomad
+task dependencies to model inter-job dependencies.
+
+### Further reading
+
+- [`lifecycle` stanza]
+- [`service` stanza]
+- Consul [Service Definition]
+- Consul [DNS Interface]
+
+[forward dns]: /consul/tutorials/networking/dns-forwarding
+[install consul]: /consul/tutorials/production-deploy/deployment-guide
+[install nomad]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
+[`lifecycle` stanza]: /nomad/docs/job-specification/lifecycle
+[`service` stanza]: /nomad/docs/job-specification/service
+[service definition]: /consul/docs/services/usage/define-services
+[dns interface]: /consul/docs/services/discovery/dns-overview
+[dns interface]: /consul/docs/services/discovery/dns-overview
+
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/docker.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/docker.mdx
new file mode 100644
index 0000000000..31c2e062e1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/docker.mdx
@@ -0,0 +1,832 @@
+---
+layout: docs
+page_title: Use the Docker task driver in a job
+description: Nomad's Docker task driver lets you run Docker-based tasks in your jobs. Learn how to configure job tasks, authenticate against a private repository, use insecure registries, and configure Docker networking.
+---
+
+# Use the Docker task driver in a job
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+**Note:** If you are using Docker Desktop for Windows or MacOS, check
+[the FAQ][faq-win-mac].
+
+Refer to [Configure the Docker task
+driver](/nomad/docs/deploy/task-driver/docker) for capabilities, client
+requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels = {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](/nomad/docs/deploy/task-driver/docker#helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cgroupns` - (Optional) Cgroup namespace to use. Set to `host` or
+  `private`. If not specified, the driver uses Docker's default. Refer to Docker's [dockerd reference](https://docs.docker.com/reference/cli/dockerd/) for more information.
+
+- `container_exists_attempts` - (Optional) A number of attempts to be made to
+  purge a container if during task creation Nomad encounters an existing one in
+  non-running state for the same task. Defaults to `5`.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) Specifies [Windows isolation][] mode: `"hyperv"` or
+  `"process"`. Defaults to `"hyperv"`.
+
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+   <Warning>
+
+   If you are creating your job specification in JSON, you must use wrap the map in an
+   array. Do not use a bare map as you would in HCL.
+
+   ```json
+   config {
+     "sysctl": [
+      {
+       "net.core.somaxconn": "16384",
+       "net.ipv4.tw_reuse": "1"
+      }
+    ]
+   }
+   ```
+
+   </Warning>
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels = {
+      foo = "bar"
+      "quote.dotted.keys" = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](/nomad/docs/deploy/task-driver/docker#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels = {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. Note that `"all"` is not permitted here if the `allow_caps`
+  field in the driver configuration doesn't also allow all capabilities. For
+  example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](/nomad/docs/deploy/task-driver/docker#config)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](/nomad/docs/deploy/task-driver/docker#helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/deploy/task-driver/docker#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/deploy/task-driver/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/deploy/task-driver/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/exec.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/exec.mdx
new file mode 100644
index 0000000000..94760d6561
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/exec.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Use the Isolated Fork/Exec task driver in a job
+description: Nomad's Isolated Fork/Exec task driver lets you run binaries using OS isolation primitives. Learn how to use the Isolated Fork/Exec task driver in your jobs. Configure the command to execute with command arguments, namespace isolation, and Linux capabilities.
+---
+
+# Use the Isolated Fork/Exec task driver in a job
+
+Name: `exec`
+
+The `exec` driver is used to execute a particular command for a task. However,
+unlike [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec) it uses the
+underlying isolation primitives of the operating system to limit the task's
+access to resources. While simple, since the `exec` driver can invoke any
+command, it can be used to call scripts or other wrappers which provide higher
+level features.
+
+Refer to [Configure the Isolated Fork/Exec task
+driver](/nomad/docs/deploy/task-driver/exec) for capabilities, client
+requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](/nomad/docs/deploy/task-driver/exec#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](/nomad/docs/deploy/task-driver/exec#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+
+[default_pid_mode]: /nomad/docs/deploy/task-driver/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/deploy/task-driver/exec#default_ipc_mode
+[cap_add]: /nomad/docs/deploy/task-driver/exec#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/deploy/task-driver/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/index.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/index.mdx
new file mode 100644
index 0000000000..9bceb69a9c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/index.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Use Nomad task drivers in jobs
+description: Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, installation, usage, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+---
+
+# Use Nomad task drivers in jobs
+
+Nomad's bundled task drivers integrate with the host OS to run job tasks in
+isolation. Review job usage for the Docker, Isolated
+Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+
+@include 'task-driver-intro.mdx'
+
+## Nomad task drivers
+
+The Nomad binary contains several bundled task drivers. We also support
+additional task driver plugins that you may install separately.
+
+| Bundled with Nomad   | Plugins               |
+|----------------------|-----------------------|
+| [Docker]             | [Exec2]               |
+| [Isolated Fork/Exec] | [Podman]              |
+| [Java]               | [Virt]                |
+| [QEMU]               |                       |
+| [Raw Fork/Exec]      |                       |
+
+Refer to each task driver's page for detailed usage.
+
+## Configure task driver plugins
+
+Refer to [Configure Nomad task drivers](/nomad/docs/deploy/task-driver) for task
+driver plugin configuration details.
+
+[Docker]: /nomad/docs/job-declare/task-driver/docker
+[Exec2]: /nomad/plugins/drivers/exec2
+[Isolated Fork/Exec]: /nomad/docs/job-declare/task-driver/exec
+[Podman]: /nomad/plugins/drivers/podman
+[Java]: /nomad/docs/job-declare/task-driver/java
+[Virt]: /nomad/plugins/drivers/virt
+[QEMU]: /nomad/docs/job-declare/task-driver/qemu
+[Raw Fork/Exec]: /nomad/docs/job-declare/task-driver/raw_exec
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/java.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/java.mdx
new file mode 100644
index 0000000000..79b2fd2f61
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/java.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: Use the Java task driver in a job
+description: Nomad's Java task driver lets you run JAR files in your workloads. Learn how to configure a job task that uses the Java task driver. Configure paths, JAR args, JVM options, namespace isolation, work directory, and Linux capabilities.
+---
+
+# Use the Java task driver in a job
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+Refer to [Configure the Java task driver](/nomad/docs/deploy/task-driver/java)
+for capabilities, client requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](/nomad/docs/deploy/task-driver/java#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+[default_pid_mode]: /nomad/docs/deploy/task-driver/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/deploy/task-driver/java#default_ipc_mode
+[cap_add]: /nomad/docs/deploy/task-driver/java#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/deploy/task-driver/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[host volume]: /nomad/docs/configuration/client#host_volume-block
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/qemu.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/qemu.mdx
new file mode 100644
index 0000000000..2eee6c2019
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/qemu.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: Use the QEMU task driver in a job
+description: Nomad's QEMU task driver provides a generic virtual machine runner that can execute any regular QEMU image. Learn how to use the QEMU task driver in your jobs. Configure image path, driver interface, accelerator, graceful shutdown, guest agent, and port map.
+---
+
+# Use the QEMU task driver in a job
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+Refer to [Configure the QEMU task driver](/nomad/docs/deploy/task-driver/qemu)
+for capabilities, client requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+[`args`]: /nomad/docs/job-declare/task-driver/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/task-driver/raw_exec.mdx b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/raw_exec.mdx
new file mode 100644
index 0000000000..105dc41ba2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/task-driver/raw_exec.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: Use the Raw Fork/Exec task driver in a job
+description: Nomad's Raw Exec task driver lets you execute commands with no resource isolation. Learn how to use the Raw Fork/Exec task driver in your jobs.
+---
+
+# Use the Raw Fork/Exec task driver in a job
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+Refer to [Configure the Raw Fork/Exec task
+driver](/nomad/docs/deploy/task-driver/raw_exec) for capabilities, client
+requirements, and plugin configuration.
+
+## Task configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `cgroup_v1_override` - (Optional) A map of controller names to paths. The
+  task will be added to these cgroups. The task will fail if these cgroups do
+  not exist. **WARNING:** May conflict with other Nomad driver's cgroups and
+  have unintended side effects.
+
+- `cgroup_v2_override` - (Optional) Adds the task to a unified cgroup path.
+  Paths may be relative to the cgroupfs root or absolute.  **WARNING:** May
+  conflict with other Nomad driver's cgroups and have unintended side
+  effects.
+
+~> On Linux, you cannot set the `task.user` field on a task using the `raw_exec`
+driver if you have hardened the Nomad client according to the
+[production][hardening] guide. On Windows, when Nomad is running as a [system
+service][service], you may specify a less-privileged service user. For example,
+`NT AUTHORITY\LocalService`, `NT AUTHORITY\NetworkService`.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This
+  must be an absolute path. This will also change the working directory when
+  using `nomad alloc exec`.
+
+- `denied_envvars` - (Optional) Passes a list of environment variables that
+  the driver should scrub from the task environment. Supports globbing, with "*"
+  wildcard accepted as prefix and/or suffix.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+[hardening]: /nomad/docs/deploy/production/requirements#user-permissions
+[service]: /nomad/docs/deploy/production/windows-service
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.10.x/content/docs/job-declare/vault.mdx b/content/nomad/v1.10.x/content/docs/job-declare/vault.mdx
new file mode 100644
index 0000000000..87ba7fe281
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-declare/vault.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: Use Vault in a job
+description: |-
+  Use Vault in your Nomad job.
+---
+
+# Use Vault in a job
+
+## Use a Vault namespace
+
+This example job specifies to use the `engineering` namespace in
+Vault. The job authenticates to Vault using its workload identity with the
+`nomad-workloads` Vault role, reads the value at secret/foo, and fetches the
+value for key `bar`.
+
+```hcl
+job "vault" {
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        role      = "nomad-workloads"
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+```
+
+## Resources
+
+- [Job specification `vault` block](/nomad/docs/job-specification/vault)
+- [Vault integration documentation](/nomad/docs/secure/vault)
diff --git a/content/nomad/v1.10.x/content/docs/job-networking/cni.mdx b/content/nomad/v1.10.x/content/docs/job-networking/cni.mdx
new file mode 100644
index 0000000000..021db26938
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-networking/cni.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Use a CNI network with a job
+description: |-
+  Learn how to use CNI networks with Nomad jobs.
+---
+
+# Use a CNI network with a job
+
+## Prerequisites
+
+Make sure your Nomad instance has a configured CNI network. Refer to [CNI
+plugins and bridge networking](/nomad/docs/networking/cni) for instructions.
+
+## Job task configuration
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`.
+
+For example, to use the configuration named `mynet`, you should set the task
+group's network mode to `cni/mynet`.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      mode = "cni/mynet"
+    }
+  }
+}
+```
+
+Nodes that have a network configuration defining a network named `mynet` in
+their `cni_config_dir` are eligible to run the workload. Nomad then schedules
+the workload on client nodes that have fingerprinted a CNI configuration with
+the given name.
+
+Nomad additionally supplies the following arguments via `CNI_ARGS` to the CNI
+network: `NOMAD_REGION`, `NOMAD_NAMESPACE`, `NOMAD_JOB_ID`, `NOMAD_GROUP_NAME`,
+and `NOMAD_ALLOC_ID`.
+
+Since the `CNI_ARGS` do not allow values to contain a semicolon, Nomad will not
+set keys where the value contains a semicolon (this could happen with the job
+ID). CNI plugins utilizing `NOMAD_*` CNI arguments are advised to apply a
+defensive policy or simply error out.
diff --git a/content/nomad/v1.10.x/content/docs/job-networking/index.mdx b/content/nomad/v1.10.x/content/docs/job-networking/index.mdx
new file mode 100644
index 0000000000..ce2cb120b0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-networking/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Workload networking
+description: |-
+  This section provides guidance on networking your Nomad workloads. Topics include using a CNI network and Consul service discovery.
+---
+
+# Workload networking
+
+This section provides guidance on networking your Nomad workloads. Topics
+include using a CNI network and Consul service discovery. Refer to the [Nomad
+networking page](/nomad/docs/networking) to learn more about Nomad's networking capabilities.
diff --git a/content/nomad/v1.10.x/content/docs/job-networking/service-discovery.mdx b/content/nomad/v1.10.x/content/docs/job-networking/service-discovery.mdx
new file mode 100644
index 0000000000..37db5c55db
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-networking/service-discovery.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Nomad service discovery helps you automatically connect workloads. Compare Nomad's built-in service discovery feature to Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+---
+
+# Service discovery
+
+@include 'service-discovery.mdx'
diff --git a/content/nomad/v1.10.x/content/docs/job-run/index.mdx b/content/nomad/v1.10.x/content/docs/job-run/index.mdx
new file mode 100644
index 0000000000..5a8a31a1a8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-run/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Run Nomad jobs
+description: |-
+  This section provides guidance for running Nomad jobs. Inspect job, access logs for troubleshooting, collect resource utilization metrics, and create job versions.
+---
+
+# Run Nomad jobs
+
+This section provides guidance for running Nomad jobs. Inspect job, access logs
+for troubleshooting, collect resource utilization metrics, and create job
+versions.
+
+The following list is the general flow for operating a job in Nomad:
+
+1. Declare the job according to the [job specification](/nomad/docs/job-specification).
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Refer to [Create and submit a job](/nomad/docs/job-declare/create-job) to learn
+how to create a job specification, review the job plan, and submit the job.
+
+## Run a job
+
+Execute the [`nomad job run` command](/nomad/commands/job/run) to run your job.
+
+Now that the job is scheduled, it may or may not be running. You need to inspect
+the allocation status and logs to make sure the job started correctly. Refer to
+the section on [inspecting state](/nomad/docs/job-run/inspect)
+details ways to examine this job's state.
+
+## Update a running job
+
+When updating a job, there are a number of [built-in update
+strategies](/nomad/docs/job-declare/strategy) which may be defined in the job
+file. The general flow for updating an existing job in Nomad is:
+
+1. Modify the existing job file with the desired changes.
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Because the job specification defines the deployment strategy, the workflow
+remains the same regardless of whether this is an initial deployment or a
+long-running job.
+
+## Run a job in the web UI
+
+1. From the **Jobs** page in the web UI, click on the **Run Job** button in the
+top right of the page. 
+1. Enter the job definition in HCL into the **Job Definition** field, upload
+a jobspec file with the **Upload file** button, or choose from a set of
+templated jobspecs with the **Choose from template** button.
+1. Click on the **Plan** button at the bottom of the page. Nomad plans the job
+and displays the scheduler dry-run results.
+1. Click on the **Run** button at the bottom of the page.
+
+## View a running job in the web UI
+
+Nomad serves the web UI alongside the API. You can open the web UI in a web
+browser with the [`nomad ui` command](/nomad/commands/ui) or you can use the
+cluster address and navigate to the `/ui` path.
+
+```shell-session
+$ nomad ui
+Opening URL "https://127.0.0.1:4646"
+```
+
+When accessing the web UI, the first page you see is a listing of all the jobs
+for the default namespace. Clicking on a job takes you to the Job details page.
+
+### View a job from the CLI
+
+You can open the details page for a job by providing the job name to the
+`nomad ui` command.
+
+```shell-session
+$ nomad ui example-job-name
+Opening URL "https://127.0.0.1:4646/ui/jobs/example-job-name"
+```
+
+### View an allocation from the CLI
+
+You can open the details page for an allocation by providing the allocation ID
+to the `nomad ui` command.
+
+```shell-session
+$ nomad ui 7dc9f2d6
+Opening URL "https://127.0.0.1:4646/ui/allocations/7dc9f2d6-15fc-7c39-4692-70fe653d960e"
+```
\ No newline at end of file
diff --git a/content/nomad/v1.10.x/content/docs/job-run/inspect.mdx b/content/nomad/v1.10.x/content/docs/job-run/inspect.mdx
new file mode 100644
index 0000000000..89ff43247b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-run/inspect.mdx
@@ -0,0 +1,233 @@
+---
+layout: docs
+page_title: Inspect running jobs
+description: |-
+  Inspect the status of a running job, the associated evaluation, and allocations to troubleshoot for errors with the Nomad CLI.
+---
+
+# Inspect running jobs
+
+A successful job submission is not an indication of a successfully-running job.
+This is the nature of a highly-optimistic scheduler. A successful job submission
+means the server was able to issue the proper scheduling commands. It does not
+indicate the job is actually running. To verify the job is running and healthy,
+you might need to inspect its state.
+
+This section will utilize the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+## Query the job status
+
+After a job is submitted, you can query the status of that job using the job
+status command:
+
+```shell-session
+$ nomad job status
+ID    Type     Priority  Status
+docs  service  50        running
+```
+
+At a high level, you can observe that the job is currently running, but what
+does "running" actually mean. By supplying the name of a job to the job status
+command, you can ask Nomad for more detailed job information:
+
+```shell-session
+$ nomad job status docs
+ID          = docs
+Name        = docs
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+example     0       0         3        0       0         0
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status    Created At
+04d9627d  42d788a3  a1f934c9  example     run      running   <timestamp>
+e7b8d4f5  42d788a3  012ea79b  example     run      running   <timestamp>
+5cbf23a1  42d788a3  1e1aa1e0  example     run      running   <timestamp>
+```
+
+This output shows that there are three instances of this task running, each with
+its own allocation. For more information on the `status` command, please consult
+the [`nomad job status` command] documentation.
+
+## Fetch an evaluation's status
+
+You can think of an evaluation as a submission to the scheduler. An example
+below shows status output for a job where some allocations were placed
+successfully, but did not have enough resources to place all of the desired
+allocations.
+
+If you issue the status command with the `-evals` flag, the output will show
+that there is an outstanding evaluation for this hypothetical job:
+
+```shell-session
+$ nomad job status -evals docs
+ID          = docs
+Name        = docs
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+
+Evaluations
+ID        Priority  Triggered By  Status    Placement Failures
+5744eb15  50        job-register  blocked   N/A - In Progress
+8e38e6cf  50        job-register  complete  true
+
+Placement Failure
+Task Group "example":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status   Created At
+12681940  8e38e6cf  4beef22f  example       run      running  <timestamp>
+395c5882  8e38e6cf  4beef22f  example       run      running  <timestamp>
+4d7c6f84  8e38e6cf  4beef22f  example       run      running  <timestamp>
+843b07b8  8e38e6cf  4beef22f  example       run      running  <timestamp>
+a8bc6d3e  8e38e6cf  4beef22f  example       run      running  <timestamp>
+b0beb907  8e38e6cf  4beef22f  example       run      running  <timestamp>
+da21c1fd  8e38e6cf  4beef22f  example       run      running  <timestamp>
+```
+
+The output states that the job has a "blocked" evaluation that is in progress.
+When Nomad can not place all the desired allocations, it creates a blocked
+evaluation that waits for more resources to become available.
+
+The `eval status` command enables examination of any evaluation in more detail.
+For the most part this should never be necessary. However, it can be useful to
+understand what triggered a specific evaluation and it's current status. Running
+it on the "complete" evaluation provides output similar to the following:
+
+```shell-session
+$ nomad eval status 8e38e6cf
+ID                 = 8e38e6cf
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = docs
+Priority           = 50
+Placement Failures = true
+
+Failed Placements
+Task Group "example" (failed to place 3 allocations):
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Evaluation "5744eb15" waiting for additional capacity to place remainder
+```
+
+This output indicates that the evaluation was created by a "job-register" event
+and that it had placement failures. The evaluation also has the information on
+why placements failed. Also output is the evaluation of any follow-up
+evaluations created.
+
+If you would like to learn more about this output, consult the documentation for
+[`nomad eval status` command].
+
+## Retrieve an allocation's status
+
+You can think of an allocation as an instruction to schedule. Like an
+application or service, an allocation has logs and state. The `alloc status`
+command gives the most recent events that occurred for a task, its resource
+usage, port allocations and more:
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+Eval ID       = 42d788a3
+Name          = docs.example[2]
+Node ID       = a1f934c9
+Job ID        = docs
+Client Status = running
+
+Task "server" is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/100 MHz  728 KiB/10 MiB  300 MiB  http: 10.1.1.196:5678
+
+Recent Events:
+Time                   Type      Description
+10/09/16 00:36:06 UTC  Started   Task started by client
+10/09/16 00:36:05 UTC  Received  Task received by client
+```
+
+The [`nomad alloc status` command] is a good starting to point for debugging an
+application that did not start. Hypothetically assume a user meant to start a
+Docker container named "redis:2.8", but accidentally put a comma instead of a
+period, typing "redis:2,8".
+
+When the job is executed, it produces a failed allocation. The
+`nomad alloc status` command gives the reason why.
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+...
+
+Recent Events:
+Time                   Type            Description
+06/28/16 15:50:22 UTC  Not Restarting  Error was unrecoverable
+06/28/16 15:50:22 UTC  Driver Failure  failed to create image: Failed to pull `redis:2,8`: API error (500): invalid tag format
+06/28/16 15:50:22 UTC  Received        Task received by client
+```
+
+Unfortunately not all failures are as visible in the allocation status output.
+If the `alloc status` command shows many restarts, there is likely an
+application-level issue during start up. For example:
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+...
+
+Recent Events:
+Time                   Type        Description
+06/28/16 15:56:16 UTC  Restarting  Task restarting in 5.178426031s
+06/28/16 15:56:16 UTC  Terminated  Exit Code: 1, Exit Message: "Docker container exited with non-zero exit code: 1"
+06/28/16 15:56:16 UTC  Started     Task started by client
+06/28/16 15:56:00 UTC  Restarting  Task restarting in 5.00123931s
+06/28/16 15:56:00 UTC  Terminated  Exit Code: 1, Exit Message: "Docker container exited with non-zero exit code: 1"
+06/28/16 15:55:59 UTC  Started     Task started by client
+06/28/16 15:55:48 UTC  Received    Task received by client
+```
+
+To debug these failures, you can use the `nomad alloc logs` command, which is
+discussed in the [accessing logs] section of this documentation.
+
+For more information on the `alloc status` command, please consult the
+documentation for the [`nomad alloc status` command].
+
+## Monitoring a job in the web UI
+
+To view the overview page for a job in the web UI, you can click on the job
+name from the list on the **Jobs** page. The overview page has several linked
+sub-pages at the top for viewing more details about the running job.
+
+- **Overview**: A page with general information about the job including the job
+name, type, priority, namespace, the status of all current and previous
+allocations, any placement failures, and the associated task groups.
+- **Definition**: A page that displays the job definition in JSON.
+- **Versions**: A page with a timeline view of every version of the job. You
+can compare the differences between job versions on this page.
+- **Deployments**: A page with health information about job deployments,
+associated task groups, and allocations.
+- **Allocations**: A page with a list of associated allocations.
+- **Evaluations**: A page with a list of associated evaluations.
+- **Services**: A page with a list of services registered for service discover
+and any associated allocations.
+- **Variables**: A page with associated Nomad Variables used by the job.
+
+[accessing logs]: /nomad/docs/job-run/logs
+[`nomad alloc status` command]: /nomad/commands/alloc/status
+[`nomad eval status` command]: /nomad/commands/eval/status
+[`nomad job status` command]: /nomad/commands/job/status
+
diff --git a/content/nomad/v1.10.x/content/docs/job-run/logs.mdx b/content/nomad/v1.10.x/content/docs/job-run/logs.mdx
new file mode 100644
index 0000000000..e0c845e063
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-run/logs.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: Access job logs for troubleshooting
+description: |-
+  Access logs of applications running in Nomad with the Nomad CLI or API.
+---
+
+# Access job logs for troubleshooting
+
+Viewing application logs is critical for debugging issues, examining performance
+problems, or even verifying the application started correctly. To make this
+as simple as possible, Nomad provides:
+
+- Job specification for [log rotation](/nomad/docs/job-specification/logs)
+- CLI command for [log viewing](/nomad/commands/alloc/logs)
+- API for programmatic [log access](/nomad/api-docs/client#stream-logs)
+
+This section will use the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+As a reminder, here is the output of the run command from the previous example:
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "04d9627d" created: node "a1f934c9", group "example"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+The provided allocation ID (which is also available via the `nomad status`
+command) is required to access the application's logs. To access the logs of our
+application, issue the following command:
+
+```shell-session
+$ nomad alloc logs 04d9627d
+```
+
+The output will look something like this:
+
+```plaintext
+<timestamp> 10.1.1.196:5678 10.1.1.196:33407 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 21.809µs
+<timestamp> 10.1.1.196:5678 10.1.1.196:33408 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 20.241µs
+<timestamp> 10.1.1.196:5678 10.1.1.196:33409 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 13.629µs
+```
+
+By default, this will return the logs of the task. If more than one task is
+defined in the job file, the name of the task is a required argument:
+
+```shell-session
+$ nomad alloc logs 04d9627d server
+```
+
+The logs command supports both displaying the logs as well as following logs,
+blocking for more output, similar to `tail -f`. To follow the logs, use the
+appropriately named `-f` flag:
+
+```shell-session
+$ nomad alloc logs -f 04d9627d
+```
+
+This will stream logs to your console.
+
+If you are only interested in the "tail" of the log, use the `-tail` and `-n`
+flags:
+
+```shell-session
+$ nomad alloc logs -tail -n 25 04d9627d
+```
+
+This will show the last 25 lines. If you omit the `-n` flag, `-tail` will
+default to 10 lines.
+
+By default, only the logs on stdout are displayed. To show the log output from
+stderr, use the `-stderr` flag:
+
+```shell-session
+$ nomad alloc logs -stderr 04d9627d
+```
+
+## Consider the "log shipper" pattern
+
+While the logs command works well for quickly accessing application logs, it
+generally does not scale to large systems or systems that produce a lot of log
+output, especially for the long-term storage of logs. Nomad's retention of log
+files is best effort, so chatty applications should use a better log retention
+strategy.
+
+Since applications log to the `alloc/` directory, all tasks within the same task
+group have access to each others logs. Thus it is possible to have a task group
+as follows:
+
+```hcl
+group "my-group" {
+  task "server" {
+    # ...
+
+    # Setting the server task as the leader of the task group allows Nomad to
+    # signal the log shipper task to gracefully shutdown when the server exits.
+    leader = true
+  }
+
+  task "log-shipper" {
+    # ...
+  }
+}
+```
+
+In the above example, the `server` task is the application that should be run
+and will be producing the logs. The `log-shipper` reads those logs from the
+`alloc/logs/` directory and sends them to a longer-term storage solution such as
+Amazon S3 or an internal log aggregation system.
+
+When using the log shipper pattern, especially for batch jobs, the main task
+should be marked as the [leader task]. By marking the main task as a leader,
+when the task completes all other tasks within the group will be gracefully
+shutdown. This allows the log shipper to finish sending any logs and then
+exiting itself. The log shipper should set a high enough [`kill_timeout`] such
+that it can ship any remaining logs before exiting.
+
+[log rotation]: /nomad/docs/job-specification/logs
+[log viewing]: /nomad/commands/alloc/logs
+[log access]: /nomad/api-docs/client#stream-logs
+[leader task]: /nomad/docs/job-specification/task#leader
+[`kill_timeout`]: /nomad/docs/job-specification/task#kill_timeout
diff --git a/content/nomad/v1.10.x/content/docs/job-run/utilization-metrics.mdx b/content/nomad/v1.10.x/content/docs/job-run/utilization-metrics.mdx
new file mode 100644
index 0000000000..76c243c7e7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-run/utilization-metrics.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Collect resource utilization metrics
+description: |-
+  Inspect the resource consumption and utilization information of a job with
+  the task drivers in Nomad.
+---
+
+# Collect resource utilization metrics
+
+Understanding the resource utilization of an application is important, and Nomad
+supports reporting detailed statistics in many of its drivers. The main
+interface for outputting resource utilization is the `alloc status` command with
+the `-stats` flag.
+
+This section will use the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+Here is the output of the run command for the "docs" job.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "04d9627d" created: node "a1f934c9", group "example"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+To fetch the detailed usage statistics, issue the following command. Your
+allocation id will be different; replace `04d9627d` with the allocation id from
+your running "docs" job:
+
+```shell-session
+$ nomad alloc status -stats 04d9627d
+ID            = 04d9627d
+Eval ID       = 42d788a3
+Name          = docs.example[2]
+Node ID       = a1f934c9
+Job ID        = docs
+Client Status = running
+
+Task "server" is "running"
+Task Resources
+CPU        Memory          Disk      Addresses
+75/100 MHz  784 KiB/10 MiB  300 MiB  http: 10.1.1.196:5678
+
+Memory Stats
+Cache   Max Usage  RSS      Swap
+56 KiB  1.3 MiB    784 KiB  0 B
+
+CPU Stats
+Percent  Throttled Periods  Throttled Time
+0.00%    0                  0
+
+Recent Events:
+Time         Type      Description
+<timestamp>  Started   Task started by client
+<timestamp>  Received  Task received by client
+```
+
+The output indicates that the job is running near the limit of configured CPU
+but has plenty of memory headroom. You can use this information to alter the
+job's resources to better reflect its actual needs:
+
+```hcl
+resources {
+  cpu    = 200
+  memory = 10
+}
+```
+
+Adjusting resources is very important for a variety of reasons:
+
+- Ensuring your application does not get OOM killed if it hits its memory limit.
+- Ensuring the application performs well by ensuring it has some CPU allowance.
+- Optimizing cluster density by reserving what you need and not over-allocating.
+
+While single point in time resource usage measurements are useful, it is often
+more useful to graph resource usage over time to better understand and estimate
+resource usage. Nomad supports outputting resource data to statsite and statsd
+and is the recommended way of monitoring resources. For more information about
+outputting telemetry, consult the [Telemetry Guide].
+
+For more advanced use cases, the resource usage data is also accessible via the
+client's HTTP API. Learn more about it in the [`allocation` API] documentation.
+
+[telemetry guide]:/nomad/docs/monitor
+[`allocation` api]: /nomad/api-docs/client
diff --git a/content/nomad/v1.10.x/content/docs/job-run/versions.mdx b/content/nomad/v1.10.x/content/docs/job-run/versions.mdx
new file mode 100644
index 0000000000..592a687f07
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-run/versions.mdx
@@ -0,0 +1,552 @@
+---
+layout: docs
+page_title: Create and modify job versions
+description: |-
+  Create, modify, delete, compare, and revert job versions with the Nomad CLI, API, or UI.
+---
+
+# Create and modify job versions
+
+Nomad creates a new version for your job each time you run your job. A job can
+have an unlimited number of versions, and version history is stored in state.
+Over time, Nomad garbage collects dead versions that do not have a version tag. Saving a tag to a version prevents Nomad from garbage collecting that version.
+
+This guide demonstrates the following job version features:
+
+- Create, modify, and delete job version tags.
+- Compare versions.
+- Revert a running job to an older version, no matter how much time has passed.
+- Clone a version.
+
+## Prerequisites
+
+- This feature requires Nomad v1.9.0 and later.
+- You are familiar with [job versions and tags][job-concept].
+
+## Create the `hello-world` job
+
+The examples use a job named `hello-world`, which is one of Nomad's job
+templates.
+
+1. On the **Jobs** page, click **Run Job**.
+1. Click **Choose from template**.
+1. Select **Hello world**.
+1. Click **Apply**.
+1. Click **Plan**.
+1. Review the **Job Plan** output.
+1. Click **Run** to run the `hello-world` job.
+
+## Create a version tag
+
+When you create a version tag, you should provide Nomad with these attributes:
+
+- A tag name
+- A job name
+- A version number
+
+The following example creates a tag named `golden-version` for version zero of `hello-world`. It includes a description of the tag.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job tag apply [options] <job_id>` command to create a tag.
+
+```shell-session
+$ nomad job tag apply -version 0 -name "golden-version" \
+    -description "The version we can roll back to." \
+    hello-world
+
+Job version 0 tagged with name "golden-version"
+```
+
+Note that Nomad tags the latest version if you omit the version number.
+
+Refer to the [`job tag apply`][job-tag-apply-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "The version we can roll back to."}'
+```
+
+The JSON response is similar to the following example.
+
+```json
+{
+  "Name":"golden-version",
+  "Description":"The version we can roll back to.",
+  "TaggedTime":1728325495829793000,
+  "Index":361,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+Refer to the Jobs HTTP API [Create Job Version Tag][job-tag-apply-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **Tag this version**.
+1. Enter `golden version` in the **Tag Name** field and `The version we can roll
+   back to.` in the **Tag Description** field.
+1. Click **Save**.
+
+Version zero now has a `golden-version` tag.
+
+![Version tag](/img/nomad/job-version-tag/nomad-ui-version-tag.png)
+
+</Tab>
+</Tabs>
+
+Using the CLI, you can run a new version of your job and create a tag for that
+new version. The following example runs a new version of the hello-world job and
+immediately tags that version.
+
+```shell-session
+$ nomad job run hello-world.nomad.hcl && \
+  nomad job tag apply -name "high-traffic-version" hello-world
+
+==> 2024-10-08T14:42:30-05:00: Monitoring evaluation "90714134"
+    2024-10-08T14:42:30-05:00: Evaluation triggered by job "hello-world"
+    2024-10-08T14:42:31-05:00: Evaluation within deployment: "192ecea1"
+    2024-10-08T14:42:31-05:00: Allocation "ec85c1bd" created: node "d6ee954e", group "servers"
+    2024-10-08T14:42:31-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2024-10-08T14:42:31-05:00: Evaluation "90714134" finished with status "complete"
+==> 2024-10-08T14:42:31-05:00: Monitoring deployment "192ecea1"
+  ✓ Deployment "192ecea1" successful
+
+    2024-10-08T14:42:48-05:00
+    ID          = 192ecea1
+    Job ID      = hello-world
+    Job Version = 4
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    servers     1        1       1        0          2024-10-08T14:52:46-05:00
+Job version 1 tagged with name "high-traffic-version"
+```
+
+## Modify a version tag
+
+The following example updates both the name and description of the `golden-version` tag for a hello-world job.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job tag apply [options] <job_id>` command to modify a tag's attributes.
+
+```shell-session
+$ nomad job tag apply -version 0 -name "golden-version-0" \
+    -description "Low traffic version." \
+    hello-world
+
+Job version 0 tagged with name "golden-version-0"
+```
+
+Refer to the [`job tag apply`][job-tag-apply-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version-0/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "Low traffic version."}'
+```
+
+The response is similar to the following.
+
+```json
+{
+  "Name":"golden-version-0",
+  "Description":"Low traffic version.",
+  "TaggedTime":1728407951089465000,
+  "Index":3460,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+See the Jobs HTTP API [Create Job Version Tag][job-tag-apply-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **golden-version**.
+1. Edit the tag name and description.
+1. Click **Save**.
+
+</Tab>
+</Tabs>
+
+## Delete a version tag
+
+The following example deletes the `golden-version` tag attached to the `hello-world` job.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use `nomad job tag unset -name "<tag_name>" <job_id>` to delete a tag from a version. This command requires a tag name and job ID.
+
+```shell-session
+$ nomad job tag unset -name "golden-version" hello-world
+
+removed from job "hello-world"
+```
+
+Refer to the [`job tag unset`][job-tag-unset-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `DELETE`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X DELETE \
+  localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+  -H "Content-Type: application/json"
+```
+
+The response is similar to the following.
+
+```json
+{
+  "Name":"",
+  "Description":"",
+  "TaggedTime":0,
+  "Index":5135,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
+Refer to the Jobs HTTP API [Delete Job Version Tag][job-tag-unset-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **golden-version**.
+1. Click **Delete** to remove the tag.
+
+</Tab>
+</Tabs>
+
+## Compare versions
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the [`nomad job history -p` command][nomad-job-history-cli] to compare
+different job versions. The `-p` option displays the differences between each
+version and the most recent version. You also have these options:
+
+- `-diff-version`: Specifies the version number of the job to compare against.
+    Mutually exclusive with the `-diff-tag` flag.
+- `-diff-tag`: Specifies the version of the job to compare against, referenced
+  by tag name. Defaults to the latest version. Mutually exclusive with `-diff-version`.
+
+### Show diff based on a version
+
+The `nomad job history -p -diff-version <job_id>` command compares all
+versions against the specified `diff-version`.
+
+The following example compares all job versions to version 4.
+
+```shell-session
+$ nomad job history -p -diff-version=4 hello-world
+```
+
+You can also perform a diff between two specific versions. This example compares
+ version 4 of the hello-world job with version 1 of the job.
+
+```shell-session
+$ nomad job history -p -version=4 -diff-version=1 hello-world
+```
+
+### Show diff based on a tag
+
+The `nomad job history -p -diff-tag <job_id>` command compares all
+versions against the specified `diff-tag`.
+
+The following example compares all job versions to the version tagged with the name `golden-version`.
+
+```shell-session
+$ nomad job history -p -diff-tag="golden-version" hello-world
+```
+
+You can also perform a diff between a tag and a version number. The following
+example compares the current version, `-version=4`, with the version tagged
+`golden-version`.
+
+```shell-session
+$ nomad job history -p -version=4 -diff-tag="golden-version" hello-world
+
+Version     = 4
+Stable      = true
+Submit Date = 2024-10-08T14:42:30-05:00
+Tag Name    = high-traffic-version
+Diff        =
++/- Job: "hello-world"
++/- Task Group: "servers"
+  +   Network {
+        Hostname: ""
+        Mode:     ""
+      + Dynamic Port {
+        + HostNetwork: "default"
+        + Label:       "www"
+        + To:          "8002"
+        }
+      }
+  -   Network {
+        Hostname: ""
+        Mode:     ""
+      - Dynamic Port {
+        - HostNetwork: "default"
+        - Label:       "www"
+        - To:          "8001"
+        }
+      }
+```
+
+</Tab>
+<Tab heading="API">
+
+You can get a version list with the `Diffs` field populated. To compare all
+versions to a specific version, use the `diff_version` query parameter.
+
+This example compares all versions to version one.
+
+```shell-session
+$ curl -X GET \
+  localhost:4646/v1/job/hello-world/versions?diffs=true&diff_version=1
+```
+
+Refer to the Jobs HTTP API [List Job Versions][job-list-diff-api] reference for
+details and complete examples.
+
+</Tab>
+<Tab heading="Web UI">
+
+The job detail's **Versions** tab shows the list of versions.
+
+![Version diff features](/img/nomad/job-version-tag/nomad-ui-version-diff.png)
+
+The two important elements are the **Diff against** dropdown, labeled "1", and
+the changes show or hide toggle, labeled "2".
+
+The **Diff against** dropdown contains versions or tags that change how the UI
+compares the versions against each other.
+
+![Version diff dropdown items](/img/nomad/job-version-tag/nomad-ui-diff-dd.png)
+
+The **Diff against previous version** option means that each version displays
+the difference with the previous version in the list. The **See Change**
+toggle displays the number of changes. Click the **See Change** arrow
+to review the actual difference.
+
+![Version diff previous](/img/nomad/job-version-tag/nomad-ui-diffs-expanded.png)
+
+When you select a version or tag, the UI
+automatically displays the differences each version has with the selected
+version.
+
+![Each version's difference with version seven](/img/nomad/job-version-tag/nomad-ui-diff-changes.png)
+
+</Tab>
+</Tabs>
+
+## Revert to a version
+
+Use job tags to revert the current running job to a prior version.
+
+The following examples revert versions of the `hello-world` job to specific version number or tag names.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job revert [options] <job_id> <version|tag>` command to revert
+the current job to a prior version.
+
+This example reverts the job to version three.
+
+```shell-session
+$ nomad job revert hello-world 3
+```
+
+This example reverts the job to the version with the `golden-version` tag.
+
+```shell-session
+$ nomad job revert hello-world "golden-version"
+```
+
+Refer to the [`job revert`][job-revert-cli] command reference for more examples
+as well as details on including general options such as namespace.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+You can revert a job to a previous version by specifying version number or the
+tag name.
+
+This example reverts the current job to version six.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/revert \
+ -H "Content-Type: application/json" -d \
+ '{"JobID": "hello-world", "JobVersion": 6}'
+```
+
+This example reverts the current job to the version tagged `golden-version`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/revert \
+ -H "Content-Type: application/json" -d \
+ '{"JobID": "hello-world", "TaggedVersion": "golden-version"}'
+```
+
+The JSON response for both examples is similar to the following.
+
+```json
+{
+  "EvalID":"c3b8b0b1-85b5-34f9-de70-80d859c6466a",
+  "EvalCreateIndex":6442,
+  "JobModifyIndex":6442,
+  "Warnings":"",
+  "Index":6442,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
+Refer to the Jobs HTTP API [Revert to older Job Version][job-revert-api]
+reference for details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+In this example, you revert the current job to the version with the
+`golden-version` tag.
+
+![Revert job](/img/nomad/job-version-tag/nomad-ui-revert-job.png)
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find the version with the `golden-version` tag.
+1. Click **Revert Version**. The UI asks you to confirm.
+1. Click **Yes, Revert Version** to complete the reversion process.
+
+The UI then displays the **Overview** tab, where you can review the new version deployment.
+
+</Tab>
+</Tabs>
+
+## Clone a version
+
+Use the web UI to clone a job version.
+
+You can use a cloned version for a new version of the same job or to create a new job.
+
+### Clone as new version
+
+In this example, you clone the `hello-world` job's `golden-version`, edit the
+job spec, plan, and then run the new version.
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click the **Versions** tab.
+1. Under the version with the `golden-version` tag, click **Clone and Edit**.
+1. Click **Clone as New Version of hello-world**.
+1. Edit the job definition.
+
+   Since this job spec was created using HCL, the UI displays the definition in the **Job Spec** tab.
+
+   Change the network port to `8080`.
+
+   <Warning>
+   If you choose to edit the JSON in the <strong>Full Definition</strong> tab,
+   the JSON definition replaces the HCL definition, so you lose the HCL
+   job spec.
+   We recommending using HCL for job specs.
+   </Warning>
+
+1. Click **Plan**.
+1. Review the plan output.
+1. Click **Run** to run the new version.
+
+The **Versions** tab displays the new version.
+
+### Clone as new job
+
+In this example, you clone the `hello-world` job's `golden-version`, edit the
+job name and network port, plan, and then run the new job.
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click the **Versions** tab.
+1. Under the version with the `golden-version` tag, click **Clone and Edit**.
+1. Click **Clone as New Job**.
+1. Edit the job spec.
+
+   Change the job name to `hello-earth` and the network port to `9080`. You must change the job name. Otherwise, Nomad creates a new version of the
+   original job.
+
+1. Click **Plan**.
+1. Review the plan output.
+1. Click **Run** to run the new job.
+
+Nomad loads the **Overview** of the `hello-earth` job so you can review the deployment.
+
+[job-concept]: /nomad/docs/concepts/job#job-versions
+[job-tag-apply-cli]: /nomad/commands/job/tag/apply
+[job-tag-apply-api]: /nomad/api-docs/jobs#create-job-version-tag
+[job-tag-unset-cli]: /nomad/commands/job/tag/unset
+[job-tag-unset-api]: /nomad/api-docs/jobs#delete-job-version-tag
+[nomad-job-history-cli]: /nomad/commands/job/history
+[job-list-diff-api]: /nomad/api-docs/jobs#list-job-versions
+[job-revert-cli]: /nomad/commands/job/revert
+[job-revert-api]: /nomad/api-docs/jobs#revert-to-older-job-version
diff --git a/content/nomad/v1.10.x/content/docs/job-scheduling/affinity.mdx b/content/nomad/v1.10.x/content/docs/job-scheduling/affinity.mdx
new file mode 100644
index 0000000000..df43fef4e8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-scheduling/affinity.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Job placements with affinities
+description: >-
+  Configure affinities to express placement preferences for your jobs. Create a
+  job with an affinity, submit it to Nomad, and monitor it after placement.
+---
+
+# Job placements with affinities
+
+The [affinity][affinity-stanza] stanza allows operators to express placement
+preferences for their jobs on particular types of nodes. Note that there is a
+key difference between the [constraint][constraint] stanza and the affinity
+stanza. The constraint stanza strictly filters where jobs are run based on
+[attributes][attributes] and [client metadata][client-metadata]. If no nodes are
+found to match, the placement does not succeed. The affinity stanza acts like a
+"soft constraint." Nomad will attempt to match the desired affinity, but
+placement will succeed even if no nodes match the desired criteria. This is done
+in conjunction with scoring based on the Nomad scheduler's bin packing algorithm
+which you can read more about [here][scheduling].
+
+In this guide, you will encounter a sample application. Your application can run
+in datacenters `dc1` and `dc2`; however, you have a strong preference to run it in
+dc2. You will learn how to configure the job to inform the scheduler of your
+preference, while still allowing it to place your workload in `dc1` if the
+desired resources aren't available in dc2.
+
+By specify an affinity with the proper [weight], the Nomad scheduler can find
+the best nodes on which to place your job. The affinity weight will be included
+when scoring nodes for placement along with other factors like the bin-packing
+algorithm.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment. This guide will assume a cluster with one server node and
+three client nodes.
+
+<Tip>
+
+ This guide is for demo purposes and is only using a single
+server node. In a production cluster, 3 or 5 server nodes are recommended.
+
+</Tip>
+
+## Place one of the client nodes in a different datacenter
+
+You are going express your job placement preference based on the datacenter your
+nodes are located in. Choose one of your client nodes and edit
+`/etc/nomad.d/nomad.hcl` to change its location to `dc2`. A snippet of an
+example configuration file is show below with the required change is shown
+below.
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+datacenter = "dc2"
+
+# Enable the client
+client {
+  enabled = true
+# ...
+}
+```
+
+After making the change on your chosen client node, restart the Nomad service
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+If everything worked correctly, one of your nodes will now show datacenter `dc2`
+when you run the [`nomad node status`][node-status] command.
+
+```shell-session
+$ nomad node status
+ID        DC   Name              Class   Drain  Eligibility  Status
+3592943e  dc1  ip-172-31-27-159  <none>  false  eligible     ready
+3dea0188  dc1  ip-172-31-16-175  <none>  false  eligible     ready
+6b6e9518  dc2  ip-172-31-27-25   <none>  false  eligible     ready
+```
+
+## Create a job with an affinity
+
+Create a file with the name `redis.nomad.hcl` and place the following content in it:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1", "dc2"]
+  type        = "service"
+
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "dc2"
+    weight    = 100
+  }
+
+  group "cache1" {
+    count = 4
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    service {
+      name = "redis-cache"
+      port = "db"
+
+      check {
+        name     = "alive"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+Observe that the job uses the `affinity` stanza and specifies `dc2` as the value
+for the `${node.datacenter}` [attribute][attributes]. It also uses the value
+`100` for the [weight][weight] which will cause the Nomad scheduler to rank
+nodes in datacenter `dc2` with a higher score. Keep in mind that weights can
+range from -100 to 100, inclusive. Negative weights serve as anti-affinities
+which cause Nomad to avoid placing allocations on nodes that match the criteria.
+
+## Register the redis Nomad job
+
+Run the Nomad job with the following command:
+
+```shell-session
+$ nomad run redis.nomad.hcl
+==> Monitoring evaluation "11388ef2"
+    Evaluation triggered by job "redis"
+    Allocation "0dfcf0ba" created: node "6b6e9518", group "cache1"
+    Allocation "89a9aae9" created: node "3592943e", group "cache1"
+    Allocation "9a00f742" created: node "6b6e9518", group "cache1"
+    Allocation "fc0f21bc" created: node "3dea0188", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "11388ef2" finished with status "complete"
+```
+
+Note that two of the allocations in this example have been placed on node
+`6b6e9518`. This is the node configured to be in datacenter `dc2`. The Nomad
+scheduler selected this node because of the affinity specified. All of the
+allocations have not been placed on this node because the Nomad scheduler
+considers other factors in the scoring such as bin-packing. This helps avoid
+placing too many instances of the same job on a node and prevents reduced
+capacity during a node level failure. You will take a detailed look at the
+scoring in the next few steps.
+
+## Check the status of the job
+
+At this point, Check the status of the job and verify where the allocations
+have been placed. Run the following command:
+
+```shell-session
+$ nomad status redis
+```
+
+There should be four instances of the job running in the `Summary` section of
+the output as shown below:
+
+```plaintext
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache1      0       0         4        0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+0dfcf0ba  6b6e9518  cache1      0        run      running  1h44m ago  1h44m ago
+89a9aae9  3592943e  cache1      0        run      running  1h44m ago  1h44m ago
+9a00f742  6b6e9518  cache1      0        run      running  1h44m ago  1h44m ago
+fc0f21bc  3dea0188  cache1      0        run      running  1h44m ago  1h44m ago
+```
+
+You can cross-check this output with the results of the `nomad node status`
+command to verify that the majority of your workload has been placed on the node
+in `dc2`. In the case of the above output, that node is `6b6e9518`.
+
+## Obtain detailed scoring information on job placement
+
+The Nomad scheduler will not always place all of your workload on nodes you have
+specified in the `affinity` stanza even if the resources are available. This is
+because affinity scoring is combined with other metrics as well before making a
+scheduling decision. In this step, you will take a look at some of those other
+factors.
+
+Using the output from the previous step, find an allocation that has been placed
+on a node in `dc2` and use the [`nomad alloc status`][alloc status] command with
+the [`-verbose`][verbose] option to obtain detailed scoring information on it.
+In this example, the allocation ID to be inspected is `0dfcf0ba` (your
+allocation IDs will be different).
+
+```shell-session
+$ nomad alloc status -verbose 0dfcf0ba
+```
+
+The resulting output will show the `Placement Metrics` section at the bottom.
+
+```plaintext
+...
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+6b6e9518-d2a4-82c8-af3b-6805c8cdc29c  0.33     0                  0                        1              0.665
+3dea0188-ae06-ad98-64dd-a761ab2b1bf3  0.33     0                  0                        0              0.33
+3592943e-67e4-461f-d888-d5842372a4d4  0.33     0                  0                        0              0.33
+```
+
+Note that the results from the `binpack`, `job-anti-affinity`,
+`node-reschedule-penalty`, and `node-affinity` columns are combined to produce
+the numbers listed in the `final score` column for each node. The Nomad
+scheduler uses the final score for each node in deciding where to make
+placements.
+
+## Next steps
+
+Experiment with the weight provided in the `affinity` stanza (the value can be
+from -100 through 100) and observe how the final score given to each node
+changes (use the `nomad alloc status` command as shown in the previous step).
+
+### Reference material
+
+- The [affinity][affinity-stanza] stanza documentation
+- [Scheduling][scheduling] with Nomad
+
+[affinity-stanza]: /nomad/docs/job-specification/affinity
+[alloc status]: /nomad/commands/alloc/status
+[attributes]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[constraint]: /nomad/docs/job-specification/constraint
+[client-metadata]: /nomad/docs/configuration/client#meta
+[node-status]: /nomad/commands/node/status
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[verbose]: /nomad/commands/alloc/status#verbose
+[weight]: /nomad/docs/job-specification/affinity#weight
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
diff --git a/content/nomad/v1.10.x/content/docs/job-scheduling/index.mdx b/content/nomad/v1.10.x/content/docs/job-scheduling/index.mdx
new file mode 100644
index 0000000000..922967e6b7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-scheduling/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Advanced job scheduling
+description: >-
+  Discover the advanced scheduling features available to Nomad jobs including affinity and spread.
+---
+
+# Advanced job scheduling
+
+The Nomad [scheduler][scheduling] uses a bin-packing algorithm to optimize the
+resource utilization and density of applications in your Nomad cluster. Nomad
+0.9 adds new features to allow operators more fine-grained control over
+allocation placement. This enables use cases similar to the following:
+
+- Expressing preference for a certain class of nodes for a specific application
+  via the [affinity stanza][affinity-stanza].
+
+- Spreading allocations across a datacenter, rack or any other node attribute or
+  metadata with the [spread stanza][spread-stanza].
+
+Please refer to the tutorials below for using affinity and spread in Nomad 0.9.
+
+- [Preemption][preemption-guide]
+- [Affinity][affinity-guide]
+- [Spread][spread-guide]
+
+[affinity-guide]: /nomad/docs/job-scheduling/affinity
+[affinity-stanza]: /nomad/docs/job-specification/affinity
+[preemption-guide]: /nomad/docs/job-scheduling/preemption
+[preemption-stanza]: /nomad/docs/job-specification/spread
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[spread-guide]: /nomad/docs/job-scheduling/spread
+[spread-stanza]: /nomad/docs/job-specification/spread
diff --git a/content/nomad/v1.10.x/content/docs/job-scheduling/preemption.mdx b/content/nomad/v1.10.x/content/docs/job-scheduling/preemption.mdx
new file mode 100644
index 0000000000..24dffc0f46
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-scheduling/preemption.mdx
@@ -0,0 +1,502 @@
+---
+layout: docs
+page_title: Use preemption for job priority
+description: >-
+  Deploy a low priority job and a high priority job. Then use preemption
+  to run the higher priority job even when other jobs are running.
+---
+
+# Use preemption for job priority
+
+Preemption allows Nomad to evict running allocations to place allocations of a
+higher priority. Allocations of a job that are blocked temporarily go into
+"pending" status until the cluster has additional capacity to run them. This is
+useful when operators need to run relatively higher priority tasks sooner even
+under resource contention across the cluster.
+
+Nomad v0.9.0 added Preemption for [system][system-job] jobs. Nomad v0.9.3
+[Enterprise][enterprise] added preemption for [service][service-job] and
+[batch][batch-job] jobs. Nomad v0.12.0 made preemption an open source feature
+for all three job types.
+
+Preemption is enabled by default for system jobs. It can be enabled for service
+and batch jobs by sending a [payload][payload-preemption-config] with the
+appropriate options specified to the [scheduler configuration][update-scheduler]
+API endpoint.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment; however, you need to use Nomad v0.12.0 or higher or Nomad
+Enterprise v0.9.3 or higher.
+
+You need a cluster with one server node and three client nodes. To simulate
+resource contention, the nodes in this environment each have 1 GB RAM (For AWS,
+you can choose the [t2.micro][t2-micro] instance type).
+
+<Tip>
+
+ This tutorial is for demo purposes and is only using a
+single server node. Three or five server nodes are recommended for a
+production cluster.
+
+</Tip>
+
+## Create a job with low priority
+
+Start by creating a job with relatively lower priority into your Nomad cluster.
+One of the allocations from this job will be preempted in a subsequent
+deployment when there is a resource contention in the cluster. Copy the
+following job into a file and name it `webserver.nomad.hcl`.
+
+```hcl
+job "webserver" {
+  datacenters = ["dc1"]
+  type        = "service"
+  priority    = 40
+
+  group "webserver" {
+    count = 3
+    network {
+      port "http" {
+        to = 80
+      }
+    }
+
+    service {
+      name = "apache-webserver"
+      port = "http"
+
+      check {
+        name     = "alive"
+        type     = "http"
+        path     = "/"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    task "apache" {
+      driver = "docker"
+
+      config {
+        image = "httpd:latest"
+        ports = ["http"]
+      }
+
+      resources {
+        memory = 600
+      }
+    }
+  }
+}
+```
+
+Note that the [count][count] is 3 and that each allocation is specifying 600 MB
+of [memory][memory]. Remember that each node only has 1 GB of RAM.
+
+## Run the low priority job
+
+Use the [`nomad job run` command][] to start the `webserver.nomad.hcl` job.
+
+```shell-session
+$ nomad job run webserver.nomad.hcl
+==> Monitoring evaluation "35159f00"
+    Evaluation triggered by job "webserver"
+    Evaluation within deployment: "278b2e10"
+    Allocation "0850e103" created: node "cf8487e2", group "webserver"
+    Allocation "551a7283" created: node "ad10ba3b", group "webserver"
+    Allocation "8a3d7e1e" created: node "18997de9", group "webserver"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "35159f00" finished with status "complete"
+```
+
+Check the status of the `webserver` job using the [`nomad job status` command][]
+at this point and verify that an allocation has been placed on each client node
+in the cluster.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+0850e103  cf8487e2  webserver   0        run      running  8s ago   2s ago
+551a7283  ad10ba3b  webserver   0        run      running  8s ago   2s ago
+8a3d7e1e  18997de9  webserver   0        run      running  8s ago   1s ago
+```
+
+## Create a job with high priority
+
+Create another job with a [priority] greater than the "webserver" job. Copy the
+following into a file named `redis.nomad.hcl`.
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+  priority    = 80
+
+  group "cache1" {
+    count = 1
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    service {
+      name = "redis-cache"
+      port = "db"
+
+      check {
+        name     = "alive"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+        ports = ["db"]
+      }
+
+      resources {
+        memory = 700
+      }
+    }
+  }
+}
+```
+
+Note that this job has a priority of 80 (greater than the priority of the
+`webserver` job from earlier) and requires 700 MB of memory. This allocation
+will create a resource contention in the cluster since each node only has 1 GB
+of memory with a 600 MB allocation already placed on it.
+
+## Observe a run before and after enabling preemption
+
+### Try to run `redis.nomad.hcl`
+
+Remember that preemption for service and batch jobs is [not enabled by
+default][preemption-config]. This means that the `redis` job will be queued due
+to resource contention in the cluster. You can verify the resource contention
+before actually registering your job by running the [`nomad job plan` command][].
+
+```shell-session
+$ nomad job plan redis.nomad.hcl
++ Job: "redis"
++ Task Group: "cache1" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache1" (failed to place 1 allocation):
+    * Resources exhausted on 3 nodes
+    * Dimension "memory" exhausted on 3 nodes
+...
+```
+
+Run the `redis.nomad.hcl` job with the [`nomad job run` command][]. Observe that the
+allocation was queued.
+
+```shell-session
+$ nomad job run redis.nomad.hcl
+==> Monitoring evaluation "3c6593b4"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "ae55a4aa"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "3c6593b4" finished with status "complete" but failed to place all allocations:
+    Task Group "cache1" (failed to place 1 allocation):
+      * Resources exhausted on 3 nodes
+      * Dimension "memory" exhausted on 3 nodes
+    Evaluation "249fd21b" waiting for additional capacity to place remainder
+```
+
+You can also verify the allocation has been queued by now by fetching the status
+of the job using the [`nomad job status` command][].
+
+```shell-session
+$ nomad job status redis
+ID            = redis
+Name          = redis
+Submit Date   = 2021-02-11T19:22:55-05:00
+Type          = service
+Priority      = 80
+...
+Placement Failure
+Task Group "cache1":
+  * Resources exhausted on 3 nodes
+  * Dimension "memory" exhausted on 3 nodes
+...
+Allocations
+No allocations placed
+```
+
+Stop the `redis` job for now. In the next steps, you will enable service job
+preemption and re-deploy. Use the [`nomad job stop` command][] with the `-purge`
+flag set.
+
+```shell-session
+$ nomad job stop -purge redis
+==> Monitoring evaluation "a9c9945d"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "ae55a4aa"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a9c9945d" finished with status "complete"
+```
+
+### Enable service job preemption
+
+Get the current [scheduler configuration][scheduler-configuration] using the
+Nomad API. Setting an environment variable with your cluster address makes the
+`curl` commands more reusable. Substitute in the proper address for your Nomad
+cluster.
+
+```shell-session
+$ export NOMAD_ADDR=http://127.0.0.1:4646
+```
+
+If you are enabling preemption in an ACL-enabled Nomad cluster, you will also
+need to [authenticate to the API][api-auth] with a Nomad token via the
+`X-Nomad-Token` header. In this case, you can use an environment variable to add
+the header option and your token value to the command. If you don't use tokens,
+skip this step. The `curl` commands will run correctly when the variable is
+unset.
+
+```shell-session
+$ export NOMAD_AUTH='--header "X-Nomad-Token: «replace with your token»"'
+```
+
+ACLs, consult the
+
+Now, fetch the configuration with the following `curl` command.
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration?pretty
+```
+
+```json
+{
+  "SchedulerConfig": {
+    "SchedulerAlgorithm": "binpack",
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    },
+    "CreateIndex": 5,
+    "ModifyIndex": 5
+  },
+  "Index": 5,
+  "LastContact": 0,
+  "KnownLeader": true
+}
+```
+
+Note that [BatchSchedulerEnabled][batch-enabled] and
+[ServiceSchedulerEnabled][service-enabled] are both set to `false` by default.
+Since you are preempting service jobs in this guide, you need to set
+`ServiceSchedulerEnabled` to `true`. Do this by directly interacting
+with the [API][update-scheduler].
+
+Create the following JSON payload and place it in a file named `scheduler.json`:
+
+```json
+{
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+Note that [ServiceSchedulerEnabled][service-enabled] has been set to `true`.
+
+Run the following command to update the scheduler configuration:
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  --request POST --data @scheduler.json \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration
+```
+
+You should now be able to inspect the scheduler configuration again and verify
+that preemption has been enabled for service jobs (output below is abbreviated):
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration?pretty
+```
+
+```plaintext
+...
+        "PreemptionConfig": {
+            "SystemSchedulerEnabled": true,
+            "BatchSchedulerEnabled": false,
+            "ServiceSchedulerEnabled": true
+        },
+...
+```
+
+### Try running the redis job again
+
+Now that you have enabled preemption on service jobs, deploying your `redis` job
+should evict one of the lower priority `webserver` allocations and place it into
+a queue. You can run `nomad plan` to output a preview of what will happen:
+
+```shell-session
+$ nomad job plan redis.nomad.hcl
++ Job: "redis"
++ Task Group: "cache1" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID     Task Group
+8a3d7e1e-40ee-f731-5135-247d8b7c2901  webserver  webserver
+...
+```
+
+The preceding plan output shows that one of the `webserver` allocations will be
+evicted in order to place the requested `redis` instance.
+
+Now use the [`nomad job run` command][] to run the `redis.nomad.hcl` job file.
+
+```shell-session
+$ nomad job run redis.nomad.hcl
+==> Monitoring evaluation "fef3654f"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "37b37a63"
+    Allocation "6ecc4bbe" created: node "cf8487e2", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "fef3654f" finished with status "complete"
+```
+
+Run the [`nomad job status` command][] on the `webserver` job to verify one of
+the allocations has been evicted.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+webserver   1       0         2        0       1         0
+
+Placement Failure
+Task Group "webserver":
+  * Resources exhausted on 3 nodes
+  * Dimension "memory" exhausted on 3 nodes
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
+0850e103  cf8487e2  webserver   0        evict    complete  21m17s ago  18s ago
+551a7283  ad10ba3b  webserver   0        run      running   21m17s ago  20m55s ago
+8a3d7e1e  18997de9  webserver   0        run      running   21m17s ago  20m57s ago
+```
+
+### Stop the job
+
+Use the [`nomad job stop` command][] on the `redis` job. This will provide the
+capacity necessary to unblock the third `webserver` allocation.
+
+```shell-session
+$ nomad job stop redis
+==> Monitoring evaluation "df368cb1"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "37b37a63"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "df368cb1" finished with status "complete"
+```
+
+Run the [`nomad job status` command][] on the `webserver` job. The output should
+now indicate that a new third allocation was created to replace the one that was
+preempted.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+Datacenters   = dc1
+Namespace     = default
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+webserver   0       0         3        0       1         0
+
+Latest Deployment
+ID          = 278b2e10
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+webserver   3        3       3        0          2021-02-12T00:28:51Z
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
+4e212aec  cf8487e2  webserver   0        run      running   21s ago     3s ago
+0850e103  cf8487e2  webserver   0        evict    complete  22m48s ago  1m49s ago
+551a7283  ad10ba3b  webserver   0        run      running   22m48s ago  22m26s ago
+8a3d7e1e  18997de9  webserver   0        run      running   22m48s ago  22m28s ago
+```
+
+## Next steps
+
+The process you learned in this tutorial can also be applied to
+[batch][batch-enabled] jobs as well. Read more about preemption in the
+[Nomad documentation][preemption].
+
+### Reference material
+
+- [Preemption][preemption]
+
+[batch-enabled]: /nomad/api-docs/operator/scheduler#batchschedulerenabled-1
+[batch-job]: /nomad/docs/concepts/scheduling/schedulers#batch
+[count]: /nomad/docs/job-specification/group#count
+[enterprise]: /nomad/docs/enterprise
+[memory]: /nomad/docs/job-specification/resources#memory
+[payload-preemption-config]: //nomad/api-docs/operator/scheduler#preemptionconfig-1
+[preemption-config]: /nomad/api-docs/operator/scheduler#preemptionconfig-1
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[priority]: /nomad/docs/job-specification/job#priority
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[scheduler-configuration]: /nomad/api-docs/operator/scheduler#read-scheduler-configuration
+[service-enabled]: /nomad/api-docs/operator/scheduler#serviceschedulerenabled-1
+[service-job]: /nomad/docs/concepts/scheduling/schedulers#service
+[step-1]: #create-a-job-with-low-priority
+[system-job]: /nomad/docs/concepts/scheduling/schedulers#system
+[t2-micro]: https://aws.amazon.com/ec2/instance-types/
+[update-scheduler]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[`nomad job plan` command]: /nomad/commands/job/plan
+[`nomad job run` command]: /nomad/commands/job/run
+[`nomad job status` command]: /nomad/commands/job/status
+[`nomad job stop` command]: /nomad/commands/job/stop
+[api-auth]: /nomad/api-docs/#authentication
diff --git a/content/nomad/v1.10.x/content/docs/job-scheduling/spread.mdx b/content/nomad/v1.10.x/content/docs/job-scheduling/spread.mdx
new file mode 100644
index 0000000000..6ca3c50913
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-scheduling/spread.mdx
@@ -0,0 +1,277 @@
+---
+layout: docs
+page_title: Use spread to increase failure tolerance
+description: >-
+  Create a job with the spread stanza to prevent application downtime
+  as a result of a physical domain failure in a datacenter or rack.
+---
+
+# Use spread to increase failure tolerance
+
+The Nomad scheduler uses a bin-packing algorithm when making job placements on
+nodes to optimize resource utilization and density of applications. Although bin
+packing ensures optimal resource utilization, it can lead to some nodes carrying
+a majority of allocations for a given job. This can cause cascading failures
+where the failure of a single node or a single data center can lead to
+application unavailability.
+
+The [spread stanza][spread-stanza] solves this problem by allowing operators to
+distribute their workloads in a customized way based on [attributes] and/or
+[client metadata][client-metadata]. By using spread criteria in their job
+specification, Nomad job operators can ensure that failures across a domain such
+as datacenter or rack don't affect application availability.
+
+Consider a Nomad application that needs to be deployed to multiple datacenters
+within a region. Datacenter `dc1` has four nodes while `dc2` has one node. This
+application has ten instances and seven of them must be deployed to `dc1` since
+it receives more user traffic and you need to make sure the application doesn't
+suffer downtime due to not enough running instances to process requests. The
+remaining 3 allocations can be deployed to `dc2`.
+
+Use the `spread` stanza in the Nomad [job specification][job-specification] to
+ensure the 70% of the workload is being placed in datacenter `dc1` and 30% is
+being placed in `dc2`. The Nomad operator can use the [percent] option with a
+[target] to customize the spread.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment. This guide will assume a cluster with one server node and
+five client nodes.
+
+<Tip>
+
+ This guide is for demo purposes and is only using a single
+server node. In a production cluster, 3 or 5 server nodes are recommended.
+
+</Tip>
+
+## Place one of the client nodes in a different datacenter
+
+In this guide, you are going to customize the spread for our job placement
+between the datacenters our nodes are located in. Choose one of your client
+nodes and edit `/etc/nomad.d/nomad.hcl` to change its location to `dc2`. A
+snippet of an example configuration file is show below with the required change
+is shown below.
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+datacenter = "dc2"
+
+# Enable the client
+client {
+  enabled = true
+# ...
+}
+```
+
+After making the change on your chosen client node, restart the Nomad service
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+If everything is configured correctly, you should be able to run the [`nomad node status`][node-status] command and confirm that one of your nodes is now in
+datacenter `dc2`.
+
+```shell-session
+$ nomad node status
+ID        DC   Name              Class   Drain  Eligibility  Status
+5d16d949  dc2  ip-172-31-62-240  <none>  false  eligible     ready
+7b381152  dc1  ip-172-31-59-115  <none>  false  eligible     ready
+10cc48cc  dc1  ip-172-31-58-46   <none>  false  eligible     ready
+93f1e628  dc1  ip-172-31-58-113  <none>  false  eligible     ready
+12894b80  dc1  ip-172-31-62-90   <none>  false  eligible     ready
+```
+
+## Create a job with the spread stanza
+
+Create a file with the name `redis.nomad.hcl` and place the following content in it:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1", "dc2"]
+  type        = "service"
+
+  spread {
+    attribute = "${node.datacenter}"
+    weight    = 100
+
+    target "dc1" {
+      percent = 70
+    }
+
+    target "dc2" {
+      percent = 30
+    }
+  }
+
+  group "cache1" {
+    count = 10
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+
+        ports = ["db"]
+      }
+
+      service {
+        name = "redis-cache"
+        port = "db"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+Note that the job specifies the `spread` stanza and specified the
+[datacenter][attributes] attribute while targeting `dc1` and `dc2` with the
+percent options. This will tell the Nomad scheduler to make an attempt to
+distribute 70% of the workload on `dc1` and 30% of the workload on `dc2`.
+
+## Register the redis.nomad.hcl job
+
+Run the Nomad job with the following command:
+
+```shell-session
+$ nomad run redis.nomad.hcl
+==> Monitoring evaluation "c3dc5ebd"
+    Evaluation triggered by job "redis"
+    Allocation "7a374183" created: node "5d16d949", group "cache1"
+    Allocation "f4361df1" created: node "7b381152", group "cache1"
+    Allocation "f7af42dc" created: node "5d16d949", group "cache1"
+    Allocation "0638edf2" created: node "10cc48cc", group "cache1"
+    Allocation "49bc6038" created: node "12894b80", group "cache1"
+    Allocation "c7e5679a" created: node "5d16d949", group "cache1"
+    Allocation "cf91bf65" created: node "7b381152", group "cache1"
+    Allocation "d16b606c" created: node "12894b80", group "cache1"
+    Allocation "27866df0" created: node "93f1e628", group "cache1"
+    Allocation "8531a6fc" created: node "7b381152", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+```
+
+Note that three of the ten allocations have been placed on node `5d16d949`. This
+is the node configured to be in datacenter `dc2`. The Nomad scheduler has
+distributed 30% of the workload to `dc2` as specified in the `spread` stanza.
+
+Keep in mind that the Nomad scheduler still factors in other components into the
+overall scoring of nodes when making placements, so you should not expect the
+spread stanza to strictly implement your distribution preferences like a
+[constraint][constraint-stanza]. Now, take a detailed look at the scoring in
+the next few steps.
+
+## Check the status of the job
+
+Check the status of the job and verify where allocations have been placed. Run
+the following command:
+
+```shell-session
+$ nomad status redis
+```
+
+The output should list ten running instances of your job in the `Summary`
+section as show below:
+
+```plaintext
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache1      0       0         10       0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+0638edf2  10cc48cc  cache1      0        run      running  2m20s ago  2m ago
+27866df0  93f1e628  cache1      0        run      running  2m20s ago  1m57s ago
+49bc6038  12894b80  cache1      0        run      running  2m20s ago  1m58s ago
+7a374183  5d16d949  cache1      0        run      running  2m20s ago  2m1s ago
+8531a6fc  7b381152  cache1      0        run      running  2m20s ago  2m2s ago
+c7e5679a  5d16d949  cache1      0        run      running  2m20s ago  1m55s ago
+cf91bf65  7b381152  cache1      0        run      running  2m20s ago  1m57s ago
+d16b606c  12894b80  cache1      0        run      running  2m20s ago  2m1s ago
+f4361df1  7b381152  cache1      0        run      running  2m20s ago  2m3s ago
+f7af42dc  5d16d949  cache1      0        run      running  2m20s ago  1m54s ago
+```
+
+You can cross-check this output with the results of the `nomad node status`
+command to verify that 30% of your workload has been placed on the node in `dc2`
+(in our case, that node is `5d16d949`).
+
+## Obtain detailed scoring information on job placement
+
+The Nomad scheduler will not always spread your workload in the way you have
+specified in the `spread` stanza even if the resources are available. This is
+because spread scoring is factored in with other metrics as well before making a
+scheduling decision. In this step, you will take a look at some of those other
+factors.
+
+Using the output from the previous step, take any allocation that has been
+placed on a node and use the nomad [alloc status][alloc status] command with the
+[verbose][verbose] option to obtain detailed scoring information on it. In this
+example, the guide refers to allocation ID `0638edf2`—your allocation IDs will
+be different.
+
+```shell-session
+$ nomad alloc status -verbose 0638edf2
+```
+
+The resulting output will show the `Placement Metrics` section at the bottom.
+
+```plaintext
+...
+Placement Metrics
+Node                                  node-affinity  allocation-spread  binpack  job-anti-affinity  node-reschedule-penalty  final score
+10cc48cc-2913-af54-74d5-d7559f373ff2  0              0.429              0.33     0                  0                        0.379
+93f1e628-e509-b1ab-05b7-0944056f781d  0              0.429              0.515    -0.2               0                        0.248
+12894b80-4943-4d5c-5716-c626c6b99be3  0              0.429              0.515    -0.2               0                        0.248
+7b381152-3802-258b-4155-6d7dfb344dd4  0              0.429              0.515    -0.2               0                        0.248
+5d16d949-85aa-3fd3-b5f4-51094cbeb77a  0              0.333              0.515    -0.2               0                        0.216
+```
+
+Note that the results from the `allocation-spread`, `binpack`,
+`job-anti-affinity`, `node-reschedule-penalty`, and `node-affinity` columns are
+combined to produce the numbers listed in the `final score` column for each
+node. The Nomad scheduler uses the final score for each node in deciding where
+to make placements.
+
+## Next steps
+
+Change the values of the `percent` options on your targets in the `spread`
+stanza and observe how the placement behavior along with the final score given
+to each node changes (use the `nomad alloc status` command as shown in the
+previous step).
+
+### Reference material
+
+- The [spread][spread-stanza] stanza documentation
+- [Scheduling][scheduling] with Nomad
+
+[alloc status]: /nomad/commands/alloc/status
+[attributes]: /nomad/docs/reference/runtime-variable-interpolation
+[client-metadata]: /nomad/docs/configuration/client#meta
+[constraint-stanza]: /nomad/docs/job-specification/constraint
+[job-specification]: /nomad/docs/job-specification
+[node-status]: /nomad/commands/node/status
+[percent]: /nomad/docs/job-specification/spread#percent
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[spread-stanza]: /nomad/docs/job-specification/spread
+[target]: /nomad/docs/job-specification/spread#target
+[verbose]: /nomad/commands/alloc/status#verbose
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/action.mdx b/content/nomad/v1.10.x/content/docs/job-specification/action.mdx
new file mode 100644
index 0000000000..ca2d99625c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/action.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: action block in the job specification
+description: |-
+  Configure custom commands in the `action` block of the Nomad job specification. Operators may execute these commands on a running allocation as a controlled way to interact with tasks. Review examples that use actions with arguments and templates.
+---
+
+# `action` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'action']} />
+
+The `action` block allows job authors to define custom commands. These commands
+can be executed by operators with the necessary permissions on a running
+allocation, offering a controlled way to interact with tasks.
+
+The name of the action can contain alphanumeric characters and dashes. This
+name must be unique within its task and must not exceed 128 characters.
+
+## `action` Parameters
+
+- `command` `(string: <required>)` - Specifies the command to be executed.
+- `args` `(array<string>: [])` - Provides a list of arguments to pass to the command.
+
+```hcl
+job "my-job" {
+  group "my-group" {
+    task "my-task" {
+      action "get-changelog" {
+        command = "/usr/bin/curl"
+        args = [
+          "-s",
+          "https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md"
+        ]
+      }
+      # ...
+    }
+  }
+}
+```
+
+## `action` Examples
+
+### Basic Action
+This example demonstrates a simple action that prints the current date and time:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "show-date" {
+      # ...
+      action "current-date" {
+        command = "/bin/date"
+      }
+    }
+  }
+}
+```
+
+### Action with Arguments
+Here, an action uses arguments to perform a specific task:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "list-files" {
+      # ...
+      action "list-tmp" {
+        command = "/bin/ls"
+        args    = ["-l", "/tmp"]
+      }
+    }
+  }
+}
+```
+
+### Action with Template
+This advanced example demonstrates an action that fetches and formats the latest
+changelog from the Nomad GitHub repository using a shell script. It showcases
+the use of templating with embedded environment variables and a multi-line script.
+
+```hcl
+action "fetch-latest-nomad-changelog" {
+  command = "/bin/sh"
+  args    = ["-c",
+    <<EOT
+curl -s https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md |
+
+awk 'BEGIN{
+    # Setting record and field separators
+    RS="## "; FS="\n";
+    section=""; count=0
+}
+{
+    # Processing only the first 3 sections after the header
+    if (count < 3 && NR > 1){
+        # Splitting the version line into components
+        split($1, versionInfo, /[()]/);
+        version=versionInfo[1];
+        gsub(" ", "", version); # Removing spaces from version
+        releaseDate=versionInfo[2];
+        # Formatting URL components
+        urlVersion=version; gsub("\\.", "", urlVersion); # Remove dots from version
+        urlDate=releaseDate; gsub(" ", "-", urlDate); gsub(",", "", urlDate); # Replace spaces with hyphens and remove comma
+        # Counting items under each section
+        for(i=1; i<=NF; i++){
+            if($i ~ /^[A-Z ]+:$/){
+                gsub(":", "", $i);
+                section=$i;
+                itemCount[section]=0;
+            }
+            if(section && $i ~ /^\*/){
+                itemCount[section]++;
+            }
+        }
+        # Printing the extracted information
+        printf "Version: %s\nRelease Date: %s\n", version, releaseDate;
+        for (s in itemCount) {
+            printf "%d %s, ", itemCount[s], s;
+        }
+        printf "\nLink: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md#%s-%s\n\n", urlVersion, tolower(urlDate);
+        delete itemCount;  # Clear the itemCount array for the next version
+        count++;
+    }
+}'
+    EOT
+  ]
+}
+```
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.10.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..6e0c81e4c7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,280 @@
+---
+layout: docs
+page_title: affinity block in the job specification
+description: |-
+  Express placement preference for a set of nodes in the `affinity` block of the Nomad job specification. Configure attribute, comparison operator, comparison value, and a scoring weight. Review kernal data, operating system, and metadata examples.
+---
+
+# `affinity` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+Updating the `affinity` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: <required>)` - Specifies the value to compare the attribute
+  against using the specified operation. This can be a literal value, another
+  attribute, or any [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+  The `value` field is required.
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Metadata
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+## Placement details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors:
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
+
+
+[job]: /nomad/docs/job-specification/job
+[group]: /nomad/docs/job-specification/group
+[client-meta]: /nomad/docs/configuration/client#meta
+[task]: /nomad/docs/job-specification/task
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables
+[constraint]: /nomad/docs/job-specification/constraint
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.10.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..211e600ca8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,288 @@
+---
+layout: docs
+page_title: artifact block in the job specification
+description: |-
+  Configure fetching a remote resource in the `artifact` block of the Nomad job specification. Set the artifact destination, the source URL, HTTP headers, fetch options, mode, and whether Nomad should recursively chown the downloaded artifact. Review examples for downloading a file, fetching from a Git repository, unarchiving, verifying checksums, and downloading from an AWS S3-compatible bucket.
+---
+
+# `artifact` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+- `chown` `(bool: false)` - Specifies whether Nomad should recursively `chown`
+  the downloaded artifact to be owned by the [`task.user`][task_user] uid and
+  gid.
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment
+variables set for the Nomad client. Manage inheritance of environment variables
+with the [`artifact.set_environment_variables`][client_artifact] client
+configuration.
+
+## Operation limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download file
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/reference/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and verify checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. Non-Amazon S3-compatible endpoints like [Minio]
+are supported, but you must explicitly set the "s3::" prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[task_user]: /nomad/docs/job-specification/task#user
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.10.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..f7969dd9e4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: change_script block in the job specification
+description: |-
+  Configure template change scripts in the `change_script` block of the Nomad job specification. Nomad executes these scripts when a template changes. Configure the command, arguments, and timeout. Enable fail on error. Review an example of how to embed a script in the data block of a template block.
+---
+
+# `change_script` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/check.mdx b/content/nomad/v1.10.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..c2ad40cdc0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,500 @@
+---
+layout: docs
+page_title: check block in the job specification
+description: |-
+  Configure Nomad to register a service health check in the `check` block of the Nomad job specification. Set the command to use, health check interval, and network values. Configure success and failure behavior. Review HTTP, gRPC, and scripted health checks.
+---
+
+# `check` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `address_mode` `(string: "host")` - Specifies which address (host, alloc,
+  alloc IPv6 or driver-specific) this service should use to make checks, similar
+  to `address_mode` on `service`. When the service uses the Consul provider,
+  Consul needs access to the address for any HTTP or TCP checks. Unlike `port`,
+  this setting is **not** inherited from the `service`. If the service `address`
+  is set, the service `address_mode` is `"auto"`, and the check `address_mode`
+  is not set, Nomad uses the service `address` value for the check address.
+
+  Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address
+     mode uses the IP address inside the namespace. Use only with "bridge" and
+    "cni" [networking modes][network_mode]. You may specify a numeric port for
+    situations where no port mapping is necessary. Set this mode only for checks
+    which are defined in a "group" service block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of
+    dual-stack or IPv6-only.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. You may specify a numeric port since port maps aren't required by
+    all network plugins. Useful for checking SDN and overlay network addresses.
+    Task fails if driver network cannot be determined. Only implemented for
+    Docker. Set this mode only for checks which are defined in a "task" service
+    block. Refer to [Using driver address
+    mode](/nomad/docs/job-specification/service#using-driver-address-mode) for
+    an example of use.
+
+  - `host` - Use the host IP and the exposed port.
+
+  Note there is no `"auto"` mode for checks, unlike services.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_success_before_passing].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_failure_before_critical].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_warning` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`warning`][consul_failure_before_warning].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. Numeric ports may be used if `address_mode="driver"` is set
+  on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider.
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+### `header` block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+## Examples
+
+### HTTP health check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple health checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC health check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block.
+
+### Script checks with shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus readiness checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+## Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_success_before_passing]: /consul/api-docs/agent/check#successbeforepassing
+[consul_failure_before_critical]: /consul/api-docs/agent/check#failuresbeforecritical
+[consul_failure_before_warning]: /consul/api-docs/agent/check#failuresbeforewarning
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
+[network_mode]: /nomad/docs/job-specification/network#mode
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.10.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..3af1a84c9d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: check_restart block in the job specification
+description: |-
+  Configure Nomad to restart tasks with unhealthy service checks in the `check_restart` block of the Nomad job specification. Set the grace period and health check failure limit. Enable ignore warnings. Review an example and how Nomad behaves based on that example.
+---
+
+# `check_restart` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/check
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart
+[service_block]: /nomad/docs/job-specification/service
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.10.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..aed3df6b81
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: connect block in the job specification
+description: |-
+  Configure the `connect` block of the Nomad job specification for Consul service mesh native application integration. Configure sidecar service, sidecar task, and gateway.
+---
+
+# `connect` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+Use the `connect` block to configure various options for Consul service mesh
+(formerly Consul Connect). The `connect` block is valid only within the context
+of a service definition at the task group level.
+
+Refer to the following resources for details on using Consul service mesh with Nomad:
+
+- The [Consul service mesh](/nomad/docs/networking/consul/service-mesh) overview
+  for an introduction and how to configure Consul service mesh in your job.
+- [Secure Nomad jobs with Consul service
+  mesh](/nomad/tutorials/integrate-consul/consul-service-mesh) for using
+  `connect` when Consul ACLs are enabled.
+
+All the examples on this page assume Consul and Nomad are in the same
+datacenter.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as
+  supporting [Consul service mesh native][consul-service-mesh-native]
+  applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul service mesh.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul service mesh.
+
+## Examples
+
+### Using Consul service mesh native
+
+The following example is a minimal service block for a
+[Consul service mesh native][consul-service-mesh-native]
+application implemented by a task named `generate`. Make sure to include the
+[service `name`](/nomad/docs/job-specification/service#name) and [service
+`port`](/nomad/docs/job-specification/service##port) fields so that Consul
+advertizes the service with your desired values.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using sidecar service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul service mesh.  Make sure to include the
+[service `name`](/nomad/docs/job-specification/service#name) and [service
+`port`](/nomad/docs/job-specification/service##port) fields so that Consul
+advertizes the service with your desired values.
+
+```hcl
+service {
+  name = "count-api"
+  port = "9001"
+
+  connect {
+    sidecar_service {}
+  }
+}
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+service {
+  name = "count-api"
+  port = "9001"
+
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+}
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a gateway
+
+The following is an example service block for creating and using a Consul
+service mesh ingress
+gateway. It includes a gateway service definition and an API service fronted by
+the gateway. Once running, the gateway can be used to reach the API service by first
+looking up the gateway Consul DNS address with `curl`.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+
+
+[gateway]: /nomad/docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /nomad/docs/job-specification/group
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[job]: /nomad/docs/job-specification/job
+[service_task]: /nomad/docs/job-specification/service#task-1
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[task]: /nomad/docs/job-specification/task
+[upstreams]: /nomad/docs/job-specification/upstreams
+[consul-service-mesh-native]: /consul/docs/automate/native
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.10.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..4a9ceb184c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: constraint block in the job specification
+description: |-
+  Restrict the set of eligible nodes in the `constraint` block of the Nomad job specification. Configure attribute, comparison operator,and comparison value. Review kernal data, distinct property, operating system, and metadata examples.
+---
+
+# `constraint` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+Updating the `constraint` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars). The
+  value field is required except for when using the `is_set`, `is_not_set`,
+  `distinct_hosts`, or `distinct_property` operators.
+
+### `operator` values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/consul.mdx b/content/nomad/v1.10.x/content/docs/job-specification/consul.mdx
new file mode 100644
index 0000000000..2279e0bace
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/consul.mdx
@@ -0,0 +1,296 @@
+---
+layout: docs
+page_title: consul block in the job specification
+description: |-
+  Configure Consul options in the `consul` block of the Nomad job specification to register them in the Consul catalog. Specify that the group or task requires a Consul token. Configure the Consul cluster, namespace, and partition. Review template, group services, namespace, and admin partition examples.
+
+---
+
+# `consul` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'consul'],
+    ['job', 'group', 'task', 'consul'],
+  ]}
+/>
+
+The `consul` block specifies [Consul][] configuration options specific to a
+task. If specified at the `group` level, the configuration will apply to all
+tasks and services within the group unless a task has its own `consul` block. A
+task-level `consul` block will entirely override a group-level `consul` block.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      consul {
+        cluster   = "default"
+        namespace = "default"
+        partition = "default"
+      }
+    }
+  }
+}
+```
+
+## Workload identity
+
+Starting in Nomad 1.7, Nomad clients will use a task or service's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+service or task when the following conditions are met:
+
+* For services, if either the [`consul.service_identity`][] is configured on the
+  Nomad servers or the service includes an `identity` block.
+* For tasks, if the [`consul.task_identity`][] is configured on the Nomad
+  servers, or the task includes an [`identity`][] block with the `name` field
+  set to `consul_default` (or `consul_$clusterName` for non-default Consul
+  clusters in Nomad Enterprise).
+
+As a fallback if none of these conditions are met, the Nomad client will instead
+use, in order of preference:
+
+* The Consul token as configured in the agent's [`consul.token`][] configuration.
+* The Consul token as configured by the agent's `CONSUL_HTTP_TOKEN` environment variable.
+
+To avoid failed deployments, you should first set up an authentication method
+and binding rules in Consul before configuring the Nomad servers with
+`consul.task_identity` and `consul.service_identity`. Refer to [Configuring Consul
+Authentication][] for more details.
+
+<Warning>
+
+Starting in Nomad 1.10, the fallback options to use the -consul-token flag when
+submitting a job, the agent's consul.token configuration, or the
+CONSUL_HTTP_TOKEN environment variable, will be removed.  This means service and
+template blocks will not be able to use the agent's Consul token or one provided
+by the job submitter. You should be prepared to migrate to the Workload Identity
+workflow for Consul and Vault before upgrading to Nomad 1.10. Refer to
+[Migrating to Using Workload Identity with Consul] for more information.
+
+</Warning>
+
+### Access to token
+
+The Nomad client will make the Consul token available to the task by writing it
+to the secret directory at `secrets/consul_token` and by injecting a
+`CONSUL_TOKEN` environment variable in the task.
+
+If the Nomad cluster is [configured][config_consul_namespace] to use [Consul Namespaces][], a
+`CONSUL_NAMESPACE` environment variable will be injected whenever `CONSUL_TOKEN`
+is set.
+
+The [`template`][template] block can use the Consul token as well.
+
+### Parameters
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use. The Nomad client will retrieve a Consul token from the
+  cluster configured in the agent configuration with the same
+  [`consul.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in
+  which group and task-level services within the group will be registered. Use
+  of `template` to access Consul KV will read from the specified Consul
+  namespace.  Specifying `namespace` takes precedence over the
+  [`-consul-namespace`][flag_consul_namespace] command line argument in `job
+  run`. In Nomad Community Edition, this field is ignored.
+
+- `partition` `(string: "")` - When this field is set, a constraint will be
+  added to the group or task to ensure that the allocation is placed on a Nomad
+  client that has a Consul Enterprise agent in the specified Consul [admin
+  partition][]. Using this field requires the following:
+
+  - [Consul Enterprise]
+  - Workload identity integration. The `partition` field does not work
+    with a legacy Consul token. Refer to [Nomad Workload Identities] for more
+    information on integrating Nomad's workload identity with Consul authentication.
+
+## Examples
+
+The following examples only show the `consul` blocks or other relevant
+blocks. Remember that the `consul` block is only valid in the placements listed
+above.
+
+### Consul token for templates
+
+This example tells the Nomad client to obtain a Consul token using the task's
+Workload Identity. The token is available to the task via the canonical
+environment variable `CONSUL_TOKEN` and written to disk at
+`secrets/consul_token`. The `template` block will use the same Consul
+token. Note that the `identity.name` is set to `"consul_default"`, which tells
+the Nomad client to use this identity when making requests to the default Consul
+cluster.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      identity {
+        name = "consul_default"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.task_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted in this case.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Consul token for group services
+
+This example tells the Nomad client to obtain a Consul Service Identity token
+using the service's Workload Identity. The Consul token will be used to register
+the service with Consul and configure any [Connect][] sidecar tasks for that
+service.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+      identity {}
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.service_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted for the service in this case.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+    }
+  }
+}
+```
+
+### Consul namespace <EnterpriseAlert product="nomad" inline />
+
+This example shows specifying a particular Consul namespace or Consul cluster
+for different tasks within a group.
+
+The `template` block in the `web` task will use the default Consul cluster, and
+will obtain a token that allows it access to the `engineering/frontend` Consul
+namespace. The `template` block in the `app` task will use the Consul cluster
+named `prod-apps`, and will obtain a token that allows it access to the
+`engineering/apps` Consul namespace.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "web" {
+
+      consul {
+        namespace = "engineering/frontend"
+      }
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      consul {
+        namespace = "engineering/apps"
+        cluster   = "prod-apps"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+### Consul admin partition <EnterpriseAlert product="nomad" inline />
+
+This example demonstrates how to configure Consul admin partitions for different
+tasks within a group. The Consul client agent must separately specify the admin
+partition in the agent configuration. Refer to the Consul documentation's
+[agent configuration reference][] for more information.
+
+In the following example, the `web` and `app` tasks use the default Consul cluster
+and obtain a token that allows access to the `prod` admin partition in Consul. The
+Consul configuration occurs at the `group` level because tasks are placed together
+on the same Allocation. If you configure tasks with separate `consul` blocks, the
+`partition` field must be the same in both blocks.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    consul {
+      cluster   = "default"
+      namespace = "default"
+      partition = "prod"
+    }
+
+    task "web" {
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`identity`]: /nomad/docs/job-specification/identity
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.token`]: /nomad/docs/configuration/consul#token
+[Configuring Consul Authentication]: /nomad/docs/secure/acl/consul#configuring-consul-authentication
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/secure/acl/consul#migrating-to-using-workload-identity-with-consul
+[config_consul_namespace]: /nomad/docs/configuration/consul#namespace
+[Consul Namespaces]: /consul/docs/enterprise/namespaces
+[Consul Admin Partitions]: /consul/docs/enterprise/admin-partitions
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[flag_consul_namespace]: /nomad/commands/job/run#consul-namespace
+[Connect]: /nomad/docs/job-specification/connect
+[admin partition]: /consul/docs/enterprise/admin-partitions
+[agent configuration reference]: /consul/docs/agent/config/config-files#partition-1
+[Consul Enterprise]: /consul/docs/enterprise
+[Nomad Workload Identities]: /nomad/docs/secure/acl/consul#nomad-workload-identities
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.10.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..3c04405496
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: csi_plugin block in the job specification
+description: >-
+  Specify that the task provides a Container Storage Interface plugin to the cluster in the `csi_plugin` block of the Nomad job specification. Configure plugin ID, type, mount directory, stage publish base directory, and health timeout. Review recommendations for deploying CSI plugins.
+---
+
+# `csi_plugin` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for deploying CSI plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/concepts/scheduling/schedulers#system
+[`topology_request`]: /nomad/commands/volume/create#topology_request
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/device.mdx b/content/nomad/v1.10.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..3b6a5cc9fb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,328 @@
+---
+layout: docs
+page_title: device block in the job specification
+description: |-
+  Configure task access to devices in the `device` block of the Nomad job specification.
+---
+
+# `device` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/plugins/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/disconnect.mdx b/content/nomad/v1.10.x/content/docs/job-specification/disconnect.mdx
new file mode 100644
index 0000000000..29c6b36ac2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/disconnect.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: disconnect block in the job specification
+description: |-
+  Describe system behavior for disconnected allocations in the `disconnect` block of the Nomad job specification. Specify whether Nomad should replace a disconnected allocation. Configure node reconciliation behavior. Set a duration for Nomad to attempt allocation reconnection and a duration after which a disconnected Nomad client stops its allocations. Review examples for stop after and lost after configuration.
+---
+
+# `disconnect` block in the job specification
+
+<Placement groups={['job', 'group', 'disconnect']} />
+
+The `disconnect` block describes the system's behavior in case of a network
+partition. By default, without a `disconnect` block, if an allocation is on a
+node that misses heartbeats, the allocation will be marked `lost` and will be
+replaced.
+
+Replacement happens when a node is lost. When a node is drained, Nomad
+[migrates][] the allocations instead, and Nomad ignores the `disconnect`
+block. When a Nomad agent fails to set up the allocation or the tasks of an
+allocation fail more than their [`restart`][] block allows, Nomad
+[reschedules][] the allocations and ignores the `disconnect`.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    disconnect {
+      lost_after = "6h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+
+  group "example2" {
+    disconnect {
+      stop_on_client_after = "12h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+}
+```
+
+~> Note that you cannot use both`lost_after` and `stop_on_client_after` in the
+same `disconnect` block.
+
+## Parameters
+
+- `lost_after` `(string: "")` - Specifies a duration during which a Nomad client
+  will attempt to reconnect allocations after it fails to heartbeat in the
+  [`heartbeat_grace`][] window.  It defaults to "", which is equivalent to
+  having the disconnect block be nil.
+
+  You cannot use `lost_after` and `stop_on_client_after` in the same
+  `disconnect` block.
+
+  Refer to [the Lost After section][lost-after] for more details.
+
+- `replace` `(bool: true)` - Specifies if Nomad should replace the disconnected
+  allocation with a new one rescheduled on a different node. Nomad considers the
+  replacement allocation a reschedule and obeys the job's [`reschedule`][]
+  block. If false and the node the allocation is running on disconnects
+  or goes down, Nomad does not replace this allocation and reports `unknown`
+  until the node reconnects, or until you manually stop the allocation.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  If true, a new alloc will be placed immediately upon the node becoming
+  disconnected.
+
+- `stop_on_client_after` `(string: "")` - Specifies a duration after which a
+  disconnected Nomad client will stop its allocations. Setting
+  `stop_on_client_after` shorter than `lost_after` and `replace = false` at the
+  same time is not permitted and will cause a validation error, because this
+  would lead to a state where no allocations can be scheduled.
+
+  The Nomad client process must be running for this to occur.
+
+  You cannot use `stop_on_client_after` and `lost_after` in the same
+  `disconnect` block.
+
+  Refer to [the Stop After section][stop-after] for more details.
+
+- `reconcile` `(string: "best_score")` - Specifies which allocation to keep once
+  the previously disconnected node regains connectivity.
+  It has four possible values which are described below:
+
+    - `keep_original`: Always keep the original allocation. Bear in mind
+    when choosing this option, it can have crashed while the client was
+    disconnected.
+    - `keep_replacement`: Always keep the allocation that was replaced
+    to replace the disconnected one.
+    - `best_score`: Keep the allocation running on the node with the best
+    score.
+    - `longest_running`: Keep the allocation that has been up and running
+    continuously for the longest time.
+
+
+## Examples
+
+The following examples only show the `disconnect` blocks. Remember that the
+`disconnect` block is only valid in the placements listed previously.
+
+### Stop After
+
+This example shows how `stop_on_client_after` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server replaces the allocation. The client waits 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_on_client_after`, so the server replaces the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may replace the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  disconnect {
+    stop_on_client_after = "90s"
+  }
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Lost After
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `lost_after` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost".
+These allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' `replace` settings
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements will
+decide which ones to keep according to the `reconcile` setting.
+If the `lost_after` duration expires before the client reconnects,
+the allocations will be marked "lost". Clients that contain "unknown"
+allocations will transition to "disconnected" rather than "down" until the last
+`lost_after` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `lost_after`
+is twelve hours. Once all groups' `lost_after` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+using the strategy defined by [`reconcile`].
+
+Lost After is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with `stop_on_client_after`.
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "best_score"
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "keep_original"
+  }
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[stop-after]: /nomad/docs/job-specification/disconnect#stop-after
+[lost-after]: /nomad/docs/job-specification/disconnect#lost-after
+[`reconcile`]: /nomad/docs/job-specification/disconnect#reconcile
+[migrates]: /nomad/docs/job-specification/migrate
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.10.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..240a89804b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload block in the job specification
+description: |-
+  Configure a parameterized job task payload in the `dispatch_payload` block of the Nomad job specification.
+---
+
+# `dispatch_payload` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/reference/runtime-environment-settings#local
+[parameterized]: /nomad/docs/job-specification/parameterized
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/env.mdx b/content/nomad/v1.10.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..d60a9874f2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: env block in the job specification
+description: |-
+  Configure environment variables in the `env` block of the Nomad job specification.
+---
+
+# `env` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic environment variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.10.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..49a40db622
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: ephemeral_disk block in the job specification
+description: |-
+  Describe a group's ephemeral disk requirements in the `ephemeral_disk` block of the Nomad job specification. Turn on data migration and allocation placement. Specify disk size.
+---
+
+# `ephemeral_disk` block in the job specification
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.10.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..804f1625b5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,237 @@
+---
+layout: docs
+page_title: expose block in the job specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul service mesh integration
+---
+
+# `expose` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul service mesh][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of Envoy expose path configurations
+  to expose through Envoy.
+
+### `path` parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## Examples
+
+The following example exposes the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+The following example exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+## Exposing service checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/check#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters
+[port]: /nomad/docs/job-specification/network#port-parameters
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate/consul/service-mesh
+[check]: /nomad/docs/job-specification/service#check
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.10.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..d269efb676
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,744 @@
+---
+layout: docs
+page_title: gateway block in the job specification
+description: |-
+  Configure a Consul mesh, ingress, or terminating gateway in the `gateway` block of the Nomad job specification.
+---
+
+# `gateway` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul service mesh gateways](/consul/docs/connect/gateways). Nomad will automatically create the
+necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries) as
+well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making
+  upstream connections before timing out. Defaults to 5 seconds. If the upstream
+  service has the configuration option <code>[connect_timeout_ms]</code> set for
+  the `service-resolver`, that timeout value will take precedence over this
+  gateway proxy option.
+
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the
+  gateway services tagged addresses should be bound to listeners in addition to
+  the default listener address.
+
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A
+  map of additional addresses to be bound.  The keys to this map are the same of
+  the listeners to be created and the values are a map with two keys - address
+  and port, that combined make the address to bind the listener to. These are
+  bound in addition to the default address.  If `bridge` networking is in use,
+  this map is automatically populated with additional listeners enabling the
+  Envoy proxy to work from inside the network namespace.
+
+  ```hcl
+  envoy_gateway_bind_addresses "<service>" {
+    address = "0.0.0.0"
+    port    = <port>
+  }
+  ```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy
+  Documentation][envoy_sd_docs].  This option applies to terminating gateways
+  that route to services addressed by a hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` parameters
+
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners
+  that the ingress gateway should setup, uniquely identified by their port
+  number.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+
+#### `listener` parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or
+  `grpc`), preconfiguring a [service-default][] in Consul to set the
+  [Protocol][service-default-protocol] of the service to the desired protocol is
+  mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[listener-service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### Listener `service` parameters
+
+The `service` blocks for a listener under an `ingress` gateway accept the
+following parameters. Note these are different than the `service` blocks under a
+`terminating` gateway.
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+- `request_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to requests routed to this
+  service. This cannot be used with a tcp listener.
+
+- `response_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to responses from this
+  service. This cannot be used with a tcp listener.
+
+- `max_concurrent_requests` `(int: <optional>)` - Specifies the maximum number
+  of concurrent HTTP/2 traffic requests that are allowed at a single point in
+  time. If unset, will default to the Envoy proxy's default.
+
+- `max_connections` `(int: <optional>)` - Specifies the maximum number of
+  HTTP/1.1 connections a service instance is allowed to establish against the
+  upstream. If unset, will default to the Envoy proxy's default.
+
+- `max_pending_requests` `(int: <optional>)` - Specifies the maximum number of
+  requests that are allowed to queue while waiting to establish a connection.
+  If unset, will default to the Envoy proxy's default.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this service.
+
+#### Header modifier parameters
+
+The `request_headers` and `response_headers` blocks of an `ingress.service`
+block accept the following parameters. For more details, see the [Consul
+documentation][response-headers].
+
+- `add` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  headers, where header names are keys and header values are the values. Header
+  names are not case-sensitive. If header values with the same name already
+  exist, the value is appended and Consul applies both headers.
+
+- `set` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  response header or to replace existing header values with. Use header names as
+  the keys. Header names are not case-sensitive. If header values with the same
+  names already exist, Consul replaces the header values.
+
+- `remove` `array(string): optional` - Defines a list of headers to remove. Consul
+  removes only headers containing exact matches. Header names are not
+  case-sensitive.
+
+#### `tls` parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every
+  listener on the gateway. If TLS is enabled, then each host defined in the
+  `host` field will be added as a DNSSAN to the gateway's x509 certificate.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+- `sds` `(block: optional)` - Defines a set of parameters that configures the
+  listener to load TLS certificates from an external Secret Discovery Service
+  ([SDS][]).
+
+  - `cluster_name` `(string)` - The SDS cluster name to connect to to retrieve
+    certificates.
+
+  - `cert_resource` `(string)` - The SDS resource name to request when fetching
+    the certificate from the SDS service.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+### `terminating` parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### linked `service` parameters
+
+The `service` blocks for a `terminating` gateway accept the following
+parameters. Note these are different than the `service` blocks for listeners
+under an `ingress` gateway.
+
+- `name` `(string: required)` - The name of the service to link with the
+  gateway. If the wildcard specifier `*` is provided, then ALL services within
+  the Consul namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate
+  authority is used to verify the authenticity of the service linked with the
+  gateway. It can be provided along with a `cert_file` and `key_file` for mutual
+  TLS authentication, or on its own for one-way TLS authentication. If none is
+  provided the gateway **will not** encrypt traffic to the destination.
+
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided
+  to servers to verify the gateway's authenticity. It must be provided if a
+  `key_file` is provided.
+
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the
+  certificate to verify the gateway's authenticity. It must be provided if a
+  `cert_file` is provided.
+
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify
+  during the TLS handshake.
+
+### `mesh` parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+## Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+## Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```hcl
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+## Examples
+
+### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul service mesh
+  # . It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#linked-service-parameters
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[listener-service]: /nomad/docs/job-specification/gateway#listener-service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
+[envoy_sd_docs]: https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery
+[SDS]: https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#listeners-services-tls-sds
+[service-default-protocol]: /consul/docs/connect/config-entries/service-defaults#protocol
+[response-headers]: /consul/docs/connect/config-entries/ingress-gateway#listeners-services-responseheaders
+[header modifiers]: /nomad/docs/job-specification/gateway#header-modifier-parameters
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/group.mdx b/content/nomad/v1.10.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..77879a0bae
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: group block in the job specification
+description: |-
+  Define a series of co-located tasks in the `group` block of the Nomad job specification. Specify constraints, affinities, spreads, number of instances, Consul settings, ephemeral disks, disconnect strategy, metadata, migration strategy, network requirements, rescheduling strategy, restart policy, service discovery, shutdown delay, task update strategy, Vault policies, and required volumes. Review count, constraints, metadata, network, and service discovery examples.
+---
+
+# `group` block in the job specification
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group. These options will be applied to all tasks and
+  services in the group unless a task has its own `consul` block.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `disconnect` <code>([disconnect][]: nil)</code> - Specifies the disconnect
+  strategy for the server and client for all tasks in this group in case of a
+  network partition. The tasks can be left unconnected, stopped or replaced
+  when the client disconnects. The policy for reconciliation in case the client
+  regains connectivity is also specified here.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/consul
+[consul_namespace]: /nomad/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`disable_rescheduling`]: /nomad/docs/job-specification/reschedule#disabling-rescheduling
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[disconnect]: /nomad/docs/job-specification/disconnect 'Nomad disconnect Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[disconect_migration]: /nomad/docs/job-specification/group#migration_to_disconnect_block
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.10.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..c339f647af
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,368 @@
+---
+layout: docs
+page_title: identity block in the job specification
+description: |-
+  Configure workload identity in the `identity` block of the Nomad job specification. Review how to configure workload identities for Consul and Vault.
+---
+
+# `identity` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'identity'],
+    ['job', 'group', 'task', 'identity'],
+    ['job', 'group', 'task', 'service', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. Nomad will create a _default_ identity for all
+workloads, but it is *not* exposed to a task. You may also set additional
+identities intended for use with external applications such as Vault, Consul, or
+OIDC authentication.
+
+For example, the following will expose the default Workload Identity as an
+environment variable and file to the task, and a second Workload Identity
+configured for a third-party OIDC provider:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env         = true
+        file        = true
+        filepath    = "local/example.jwt"
+
+        # Restart on token renewal to get the new env var
+        change_mode = "restart"
+      }
+
+      identity {
+        name        = "example"
+        aud         = ["oidc.example.com"]
+        file        = true
+        ttl         = "1h"
+
+        # Send a HUP signal when the token file is updated
+        change_mode   = "signal"
+        change_signal = "SIGHUP"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+- `name` `(string: "default")` - The name of the workload identity, which must
+  be unique per task. Only one `identity` block in a task can omit the `name`
+  field.
+- `aud` `([]string: nil)` - The audience field for the workload identity. This
+  should always be set for non-default identities.
+- `change_mode` `(string: "noop")` - Specifies the behavior Nomad should take when the token changes.
+
+  - `"noop"` - take no action. The default since tasks may choose to reload
+      tokens only when their current token gets rejected or implement their own
+      change detection.
+  - `"restart"` - restart the task.
+  - `"signal"` - send a configurable signal to the task. Must set `change_signal`.
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGHUP"` or `"SIGUSR1"`. This option is required if the
+  `change_mode` is `signal`.
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+- `filepath` `(string: "")` - If not empty and file is `true`, the workload
+  identity is available at the specified location relative to the
+  [task working directory][] instead of the `NOMAD_SECRETS_DIR`.
+- `ttl` `(string: "")` - The lifetime of the identity before it expires. The
+  client will renew the identity at roughly half the TTL. This is specified
+  using a label suffix like "30s" or "1h". You may not set a TTL on the default
+  identity. You should always set a TTL for non-default identities.
+
+## Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload identities for Consul
+
+Jobs that need access to Consul can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task or service that will access Consul.
+
+You can configure Nomad servers to automatically add default identities for
+Consul using the [`consul.service_identity`][] and [`consul.task_identity`][]
+agent configuration. Upon job registration, the Nomad server updates tasks that
+have a [`consul`][] block and services that use the Consul service provider to
+include the default identities.
+
+Job specifications that include [`template`][] blocks are not provided with
+default identities because Nomad is unable to decipher the contents of the
+template data. You must specify the identities required for Consul in the job
+specification.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identities configured in the Nomad servers. Identities for
+tasks must have a [`name`](#name) that follows the pattern
+`consul_<cluster name>`. Identities for services do not need to specify a
+`name`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the task
+identity name should be `consul_default`.
+
+<Warning>
+
+Nomad Enterprise supports multiple Consul clusters. The value of
+`cluster_name` must be the same as the task's [`consul.cluster` parameter value](/nomad/docs/job-specification/consul#cluster).
+
+</Warning>
+
+Refer to [Nomad workload identities][int_consul_wid] section of the Consul
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="3,14-17,30-34">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {}
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_default"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="3-5,16-19,32-36">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {
+      cluster = "prod"
+    }
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_prod"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Workload identities for Vault
+
+Jobs that need access to Vault can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task that will access Vault.
+
+You can configure Nomad servers to automatically add default identities for
+Vault using the [`vault.default_identity`][] agent configuration. Upon job
+registration, the Nomad server updates tasks that have a [`vault`][] block to
+include the default identity.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identity configured in the Nomad servers. The identity
+[`name`](#name) must follow the pattern `vault_<cluster name>`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the
+identity name should be `vault_default`.
+
+<Warning>
+
+Nomad Enterprise supports multiple Vault clusters. The cluster name
+must be the same as the task's [`vault.cluster` parameter value](/nomad/docs/job-specification/vault#cluster).
+
+</Warning>
+
+Refer to [Nomad Workload Identities][int_vault_wid] section of the Vault
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="19,21-25">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      identity {
+        name = "vault_default"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="19-21,23-27">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {
+        cluster = "prod"
+      }
+
+      identity {
+        name = "vault_prod"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`template`]: /nomad/docs/job-specification/template
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault`]: /nomad/docs/job-specification/vault
+[int_consul_wid]: /nomad/docs/secure/acl/consul
+[int_vault_wid]: /nomad/docs/secure/vault/acl
+[taskapi]: /nomad/api-docs/task-api
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/index.mdx b/content/nomad/v1.10.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..f69eec4619
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,153 @@
+---
+layout: docs
+page_title: Nomad job specification
+description: |-
+  This section contains reference information for configuring a Nomad job with HCL. Learn what a job specification is and its format. Review an example job specification.
+---
+
+# Nomad job specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+The `service` block can also be specified at the group level. This allows job specification authors
+to create and register services with Consul Service Mesh. A service block specified at the group
+level must include a [`connect`][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/job.mdx b/content/nomad/v1.10.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..644ca45f65
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: job block in the job specification
+description: |-
+  Define your workload in the `job` block of the Nomad job specification. Specify constraints, affinities, spreads, datacenter, node pool, group, metadata, job name, node migration strategy, namespace, priority, region, rescheduling strategy, job type, task update strategy, and Vault policies.
+  Configure parameterized and periodic jobs. Review examples that use Docker, batch jobs, and secrets.
+---
+
+# `job` block in the job specification
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+
+    task "docs" {
+      # ...
+    }
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  update {
+    # ...
+  }
+}
+```
+
+## Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul service mesh enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/docs/govern/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: //nomad/docs/deploy/clusters/federate-regions
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/concepts/scheduling/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.10.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..9828f9c1ab
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: lifecycle block in the job specification
+description: |-
+  Configure when Nomad runs a task in the `lifecycle` block of the Nomad job configuration. Specify a lifecycle hook of prestart, poststart, or poststop. Define a task as ephemeral or as a long-lived sidecar. Review examples of initialization, cleanup, and auxiliary tasks.
+---
+
+# `lifecycle` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+The `lifecycle` block also controls the order Nomad stops tasks in an
+allocation. Nomad first waits for the group's [shutdown_delay][]. It then stops
+the [leader][] task, if present. Then Nomad stops any non-sidecar and
+non-poststop tasks, and finally any sidecar tasks.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/docs/job-declare/task-dependencies
+[shutdown_delay]: /nomad/docs/job-specification/group#shutdown_delay
+[leader]: /nomad/docs/job-specification/task#leader
+
+## Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init task pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion sidecar pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup task pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.10.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..8640b38629
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: logs block in the job specification
+description: |-
+  Configure a task's log rotation policy in the `logs` block of the Nomad job specification. Set the maximum number of rotated files and the maximum size of each rotated file. Turn off log collection for a task. Review default log rotation values.
+---
+
+# `logs` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/deploy/task-driver/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.10.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..159bbccb56
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: meta block in the job specification
+description: |-
+  Define arbitrary metadata in the `meta` block of the Nomad job specification. Configure runtime environment variables for tasks to consume. Review examples that use Nomad interpolation and templates.
+---
+
+# `meta` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## Template usage example
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/reference/runtime-environment-settings#meta-block-for-arbitrary-configuration
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.10.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..2e9574936e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: migrate block in the job specification
+description: |-
+  Define the group's allocation migration strategy in the `migrate` block of the Nomad job specification. The migration strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+Migrating happens when a Nomad node is drained. When a node is lost, Nomad
+[replaces][] the allocations instead and ignores the `migrate` block.  When the
+agent fails to set up the allocation or the tasks of an allocation more than
+their [`restart`][] block allows, Nomad [reschedules][] the allocations instead
+and ignores the `migrate` block.
+
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/docs/manage/migrate-workloads) for details
+on node draining.
+
+## Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/commands/node/drain
+[deadline]: /nomad/commands/node/drain#deadline
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.10.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..16cb1c8c26
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,289 @@
+---
+layout: docs
+page_title: multiregion block in the job specification
+description: |-
+  Deploy a job to multiple federated regions in the `multiregion` block of the Nomad job specification. Learn about multi-region deployment states, parameterized dispatch, and periodic time zones. Configure region count, datacenters, metadata, and node pool. Specify region rollout strategy parameters. Review examples of max parallel, rollback regions, override counts, and merging metadata.
+---
+
+# `multiregion` block in the job specification
+
+<Placement groups={[['job', 'multi-region']]} />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+<EnterpriseAlert/>
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multi-region deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multi-region deployment states
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multi-region deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic time zones
+
+Multi-region periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multi-region jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multi-region deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multi-region deployments are considered GA.
+
+### `strategy` parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multi-region will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multi-region deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multi-region `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## Examples
+
+The following examples only show the `multi-region` block and the other
+blocks it might be interacting with.
+
+### Max parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multi-region {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/docs/deploy/clusters/federate-regions
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #examples
+[upgrade strategies]: /nomad/docs/job-declare/strategy/
+[`nomad deployment unblock`]: /nomad/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/network.mdx b/content/nomad/v1.10.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..94d21ee410
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,370 @@
+---
+layout: docs
+page_title: network block in the job specification
+description: |-
+  Configure task group networking requirements in the `network` block of the Nomad job specification. Configure network mode, hostname, port, DNS, and Container Network Interface (CNI) arguments. Review configuration examples of dynamic ports, static ports, mapped ports, bridge mode, host networks, DNS, and CNI networks.
+---
+
+# `network` block in the job specification
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul service mesh](/nomad/docs/networking/consul). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+- `cni` <code>([CNIConfig](#cni-parameters): nil)</code> - Sets the custom CNI
+  arguments for a network configuration per allocation, for use with `mode="cni/*`.
+
+### `port` parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+- `ignore_collision` `(bool: false)` - Allows the group to be placed on a node
+  where the port may already be reserved. Intended for programs that support
+  `SO_REUSEPORT` unix socket option, so more than one instance of the program
+  may bind to the same port. Only compatible with [`host`](#host) network mode
+  and `static` ports. Some task drivers (e.g. docker) may also require setting
+  `network_mode = "host"` (or similar) to avoid runtime errors after placement.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+## `cni` parameters
+
+- `args` `(map<string><string>: nil)` - Sets CNI arguments for network configuration.
+   These get turned into `CNI_ARGS` per the
+   [CNI spec](https://www.cni.dev/docs/spec/#parameters).
+
+These parameters support [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+## Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static ports
+
+Static ports place your job on a host where the port is not already reserved
+by another job with the same port.
+
+This example specifies a static port allocation for the port labeled "lb".
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+For programs that support the `SO_REUSEPORT` unix socket option,
+you may set `ignore_collision = true` to place multiple copies on a single node.
+
+### Mapped ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is necessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### CNI args
+
+The following example specifies CNI args for the custom CNI plugin specified above.
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+  cni {
+    args = {
+     "nomad.region" : "${node.region}"
+    }
+  }
+}
+```
+
+### Host networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/job-declare/task-driver/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul service mesh Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/numa.mdx b/content/nomad/v1.10.x/content/docs/job-specification/numa.mdx
new file mode 100644
index 0000000000..7469f21130
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/numa.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: numa block in the job specification
+description: |-
+  Define a NUMA-aware task scheduling strategy in the `numa` block of the Nomad job specification. Configure the affinity strategy and specify a list of devices that must be colocated on the same NUMA node.
+---
+
+# `numa` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources', 'numa']} />
+
+The `numa` block is used to configure how Nomad will assign CPU cores for a task
+while taking the [NUMA hardware topology][numa_wiki] of a node into consideration.
+Workloads that are sensitive to memory latency can perform significantly better
+when pinned to CPU cores on the same NUMA node.
+
+NUMA aware scheduling is currently limited to Linux.
+
+<EnterpriseAlert product="nomad"/>
+
+```hcl
+job "example" {
+  group "group" {
+    task "task" {
+      resources {
+        cores = 8
+        numa {
+          affinity = "require"
+        }
+      }
+    }
+  }
+}
+```
+
+In the example above, the task is requesting Nomad to reserve 8 CPU cores, all
+of which must be colocated on the same hardware NUMA node. The Nomad scheduler
+will ensure the task is placed on a Nomad node with sufficient unused CPU cores
+in a compatible configuration.
+
+Configuring the `numa` block requires the task specifies CPU resources using
+the [`cores`][cores] parameter.
+
+# Parameters
+
+- `affinity` `(string: "none")` - Specifies the strategy Nomad will use when
+  selecting CPU cores to assign to a task. Possible values are `"none"`,
+  `"prefer"`, or `"require"`.
+  - `none` - Nomad is free to allocate CPU cores using any strategy. Nomad uses
+  this freedom to allocate cores in such a way that minimizes the amount of
+  fragmentation of core availability per NUMA node. It does so by bin-packing
+  the chosen cores onto the NUMA nodes with the fewest number of cores available.
+  - `prefer` - Nomad will select the set of CPU cores on a node that minimizes
+  the total distance between those cores, but does not limit those CPU core
+  selections to come from a single NUMA node.
+  - `require` - Nomad will select a set of CPU cores that are strictly colocated
+  on the same hardware NUMA node. If there are no Nomad nodes with a sufficient
+  number of available cores in a compatible configuration, task placement will
+  fail due to exhausted resources.
+
+- `devices` `(list<string>: nil)` - Specifies which devices must be colocated on
+  the name NUMA node, along with allocated CPU cores. Must be a subset of the
+  devices listed in the [resources] block. May only be used with `affinity` set
+  to `require`.
+
+<Note>
+
+  The `require` affinity option causes fragmentation of available CPU cores
+  based on the NUMA node the selected cores are associated with. Use it for
+  workloads known to be highly sensitive to memory latencies. A cluster where
+  all jobs make use of the `require` affinity option will not be able to make
+  efficient use of available resources.
+</Note>
+
+## Examples
+
+This example will allocate a `1080ti` GPU and ensure it is on the same NUMA node
+as the 4 CPU cores reserved for the task.
+
+```hcl
+resources {
+  cores  = 4
+  memory = 2048
+
+  device "nvidia/gpu/1080ti" {
+    count = 1
+  }
+
+  numa {
+    affinity = "require"
+    devices = [
+      "nvidia/gpu/1080ti"
+    ]
+  }
+}
+```
+
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
+[cores]: /nomad/docs/job-specification/resources#cores
+[resources]: /nomad/docs/job-specification/resources
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.10.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..6523cd647e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: parameterized block in the job specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` block in the job specification
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+### Use periodic with parameterized
+
+Nomad uses an internal hierarchy when scheduling a job that is both `parameterized` and [`periodic`][periodic].
+
+```plaintext
+parameterized => periodic => batch
+```
+
+Nomad processes a periodic with parameterized job in the following order:
+
+1. Nomad does not dispatch a periodic job with null parameters in the periodic configuration. This forces the parameterized job to take precedence over the periodic job.
+2. After Nomad dispatches the parameterized job and gives it parameters, Nomad uses the periodic configuration.
+3. Nomad dispatches new jobs according to the periodic configuration that uses thee parameters from the triggering parameterized job.
+
+In this example, the periodic job does not trigger any new jobs
+until the operator dispatches the parameterized job at least once. After that, the
+dispatched child periodically triggers more children with the given parameters.
+
+```hcl
+  periodic {
+    crons = [
+      "*/40 * * * * * *"
+    ]
+  }
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+```
+
+
+
+There are three columns plus comments in this example output, which is for the preceding periodic, parameterized example job. Scroll to the last column to review the comments.
+
+```
+$ nomad job status
+ID                                                     Type                            Submit Date
+sync                                                   batch/periodic/parameterized    2024-11-07T10:43:30+01:00 // Original submitted job
+sync/dispatch-1730972650-247c6e97                      batch/periodic                  2024-11-07T10:44:10+01:00 // First dispatched job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972680  batch                           2024-11-07T10:44:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972760-f79a96e1                      batch/periodic                  2024-11-07T10:46:00+01:00 // Second dispatched job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972800  batch                           2024-11-07T10:46:40+01:00 // Cron job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters B
+```
+The output illustrates the following:
+
+1. The `sync` job is the parameterized and periodic job. However, Nomad doesn't run the periodic job until you submit with the required parameters.
+2. The `sync/dispatch-1730972650-247c6e97` job contains parameters and triggers the batch jobs, named `sync/dispatch-1730972650-247c6e97/periodic-1730972680` and `sync/dispatch-1730972650-247c6e97/periodic-1730972860`.
+3. The `sync/dispatch-1730972760-f79a96e1` job assigns new parameters and triggers new batch jobs that use those parameters.
+
+If you need to force the periodic job, force the the corresponding parameterized job.
+
+This example forces the first dispatched job with parameters A from the preceding example.
+
+```
+$ nomad job periodic force sync/dispatch-1730972650-247c6e97
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
+[periodic]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.10.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..7d2c752a1b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: periodic block in the job specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` block in the job specification
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+Refer to the [parameterized] documentation for how to use parameters with a periodic job.
+
+## Parameters
+
+- `cron` (_deprecated_: Replaced by `crons` in 1.6.2) `(string)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`. Either `cron` or `crons` must be set, but not both.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions. Either `cron` or `crons` must be set, but not both.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set time zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight saving time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
+[parameterized]: /nomad/docs/job-specification/parameterized#use-periodic-with-parameterized
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.10.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..0e0dd2e70d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: proxy block in the job specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul service mesh integration
+---
+
+# `proxy` block in the job specification
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul service mesh][]. It is valid only within the context of
+a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul service mesh documentation][envoy_dynamic_config]
+  for details. Keys and values support [runtime variable interpolation][].
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path
+  configuration for Envoy. See Consul's [Expose Paths Configuration
+  Reference][expose_path_ref] for more information.
+- `local_service_address` `(string: "127.0.0.1")` - The address the local
+  service binds to. Useful to customize in clusters with mixed Connect and
+  non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in
+  clusters with mixed Connect and non-Connect services.
+- `transparent_proxy` <code>([transparent_proxy][]: nil)</code> - Used to enable
+  [transparent proxy][tproxy] mode, which allows the proxy to use Consul service
+  intentions to automatically configure upstreams, and configures iptables rules
+  to force traffic from the allocation to flow through the proxy.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of
+  each upstream service that this sidecar proxy communicates with.
+
+## Examples
+
+The following example is a proxy specification that includes upstreams
+configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+The following example is a proxy specification that includes transparent proxy
+configuration. Note that with transparent proxy, you will not need to configure
+an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+[Consul service mesh]: /nomad/docs/networking/consul
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[runtime variable interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
+[envoy_dynamic_config]: /consul/docs/connect/proxies/envoy#dynamic-configuration
+[expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[transparent_proxy]: /nomad/docs/job-specification/transparent_proxy
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.10.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..d4dfe5784d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: reschedule block in the job specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified
+at the job level, the configuration will apply to all groups within the job. If
+the reschedule block is present on both the job and the group, they are merged
+with the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its task
+statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+Rescheduling happens when the Nomad agent fails to set up the allocation or the
+tasks of an allocation fail more than their [`restart`][] block allows. When a
+node is drained, Nomad [migrates][] the allocations instead and ignores the
+`reschedule` block. When a node is lost, Nomad [replaces][] the allocations
+instead and ignores the `reschedule` block.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is
+  set to `true` the `attempts` and `interval` fields are not used. The [`progress_deadline`][]
+  parameter within the update block is still adhered to when this is set to `true`, meaning no more
+  reschedule attempts are triggered once the [`progress_deadline`][] is reached.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### Parameter defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
+
+[`progress_deadline`]: /nomad/docs/job-specification/update#progress_deadline
+[`restart`]: /nomad/docs/job-specification/restart
+[migrates]: /nomad/docs/job-specification/migrate
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.10.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..396c4d0bc5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,169 @@
+---
+layout: docs
+page_title: resources block in the job specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `numa` <code>([Numa][]: &lt;optional&gt;)</code> - Specifies the
+  NUMA scheduling preference for the task. Requires the use of `cores`.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+- `secrets` <code>(`int`: &lt;optional&gt;)</code> - Specifies the size of the
+  [`secrets/`][] directory in MB, on platforms where the directory is a
+  tmpfs. If set, the scheduler adds the `secrets` value to the `memory` value
+  when allocating resources on a client, and this value will be included in the
+  allocated resources shown by the `nomad alloc status` and `nomad node status`
+  commands. If unset, the client will allocate 1 MB of tmpfs space and it will
+  not be counted for scheduling purposes or included in allocated resources. You
+  should not set this value if the workload will be placed on a platform where
+  tmpfs is unsupported, because it will still be counted for scheduling
+  purposes.
+
+## Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block,
+Nomad finds a client with enough spare capacity to reserve 2 cores exclusively
+for the task. Unlike the `cpu` field, the task does not share CPU time with any
+other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of
+the job fails.
+
+Refer to [How Nomad Uses CPU][concepts-cpu] for more details on Nomad's
+reservation of CPU resources.
+
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2048 MB:
+
+```hcl
+resources {
+  memory = 2048
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`raw_exec`, `exec2`, `exec`, `docker`, `podman`, and `java` task drivers.  Consult the
+documentation of community-supported task drivers for their memory
+oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][quota_spec] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/deploy/task-driver/docker#cpu
+[exec_cpu]: /nomad/docs/deploy/task-driver/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[quota_spec]: /nomad/docs/other-specifications/quota
+[numa]: /nomad/docs/job-specification/numa 'Nomad NUMA Job Specification'
+[`secrets/`]: /nomad/docs/reference/runtime-environment-settings#secrets
+[concepts-cpu]: /nomad/docs/architecture/cpu
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.10.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..aba2dfde20
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: restart block in the job specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task. Restarts are different from
+[rescheduling][], which happens when the tasks run out of restart attempts.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### Parameter defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### Disabling restart
+
+To disable restarting, set the `attempts` parameter to zero and `mode` to `"fail"`.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+  }
+}
+```
+
+### `mode` values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[rescheduling]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.10.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..7ee3281e6a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling block in the job specification
+description: The `scaling` block allows specifying scaling policy for a task group
+---
+
+# `scaling` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/schedule.mdx b/content/nomad/v1.10.x/content/docs/job-specification/schedule.mdx
new file mode 100644
index 0000000000..adc5cfb35b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/schedule.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: schedule block in the job specification
+description: |-
+  Time based task execution is enabled by using the `schedule` task block.
+---
+
+# `schedule` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'periodic']} />
+
+Time based task execution is enabled by using the `schedule` block. The
+`schedule` block controls when a task is allowed to be running.
+
+<EnterpriseAlert product="nomad"/>
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+Unlike [`periodic`][periodic] jobs, the `schedule` block applies to individual
+tasks. The Nomad Client starts and stops tasks at the specified time without
+interaction with the Nomad Servers. This means time based task execution works
+even when a Client is disconnected from Servers. The task's resources remain
+allocated even outside the `schedule` when the task itself is stopped.
+
+```hcl
+job "docs" {
+  group "tbte" {
+    task "scheduled" {
+      schedule {
+        cron {
+          start    = "30 9 * * MON-FRI *"
+          end      = "0 16"
+          timezone = "America/New_York"
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+The `schedule` block must have a `cron` block containing:
+
+- `start` `(string: <required>)` - When the task should be started. Specified in 6 field
+  [cron format][cron] (no seconds) without `,` or `/` characters.
+
+- `end` `(string: <required>)` - When the task should be stopped
+  ([`kill_signal`][kill_signal] and [`kill_timeout`][kill_timeout] apply).
+  Specified in 2 field [cron format][cron] (minute and hour) without `,` or `/`
+  characters.
+
+- `timezone` `(string: "Local")` - What time zone the `start` and `end` times
+  are specified in. Defaults to the local time zone of the Nomad Client the job
+  is scheduled onto.
+
+## Limitations
+
+- Job deployments outside of the specified `schedule` will be unable to
+  succeed. To update a job using time based task execution outside of its
+  schedule, do a [force
+  update](/nomad/docs/job-specification/update#max_parallel-0).
+
+- Overnight schedules are currently not supported. Adjusting the `timezone`
+  should allow converting overnight schedules to times within a single day.
+
+[periodic]: /nomad/docs/job-specification/periodic
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/service.mdx b/content/nomad/v1.10.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..5737d1da64
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,572 @@
+---
+layout: docs
+page_title: service block in the job specification
+description: |-
+  The `service` block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider: Nomad or Consul. This section of the documentation discusses the
+configuration, but you should also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        weights {
+          passing = 5
+          warning = 1
+        }
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+
+        identity {
+          aud = ["consul.io"]
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only covers the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul, refer to
+the [Consul integration documentation][service-discovery].
+
+The `service` block can also be at task group level.
+This enables services in the same task group to opt into [Consul
+service mesh][connect] integration.
+
+## Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use, when the `provider` is `"consul"`. The Nomad client
+  will retrieve a Consul token from the cluster configured in the agent
+  configuration with the same [`consul.name`][]. In Nomad Community Edition,
+  this field is ignored.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `weights` <code>(Weights: nil)</code> - Specifies how a service instance is
+  weighted in a DNS SRV request based on the service's health status, as
+  described in the Consul [weights][] documentation. Only available where
+  `provider = "consul"` The `weight` block supports the following fields:
+  - `passing` <code>int: 1</code> - The weight of services in passing state.
+  - `warning` <code>int: 1</code> - The weight of services in warning state.
+
+- `connect` - Configures the [Consul service mesh][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `kind` `(string: <optional>)` - Configures the [Consul Service
+  Kind][kind] to pass to Consul during service registration. Only available
+  when `provider = "consul"`, and is ignored if a Consul service mesh Gateway is
+  defined.
+
+- `identity` <code>([Identity][identity_block]: nil)</code> - Specifies a
+  Workload Identity to use when obtaining Service Identity tokens from Consul to
+  register the service. Only available where `provider = "consul"`. Typically
+  this can be omitted so that Nomad will fall back to the server's
+  [`consul.service_identity`][] block.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of dual-stack or IPv6-only.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+  | Service kind | Allowed port value type |
+  | -------- | ------- |
+  | Normal       | Numeric or port mapping label |
+  | Uses [`connect` native][connect-native] | Numeric or port mapping label |
+  | Uses [`connect` sidecar][connect-sidecar] | Numeric |
+  | Ingress gateway | Port mapping label (optional) |
+  | Terminating gateway | None (optional) |
+  | Mesh gateway | External port mapping label |
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc, alloc_ipv6 or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of dual-stack or IPv6-only.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul service mesh native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using driver address mode
+
+The [Docker](/nomad/docs/job-declare/task-driver/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/job-declare/task-driver/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/job-declare/task-driver/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect
+[kind]: /consul/api-docs/agent/service#kind
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[identity_block]: /nomad/docs/job-specification/identity
+[weights]: /consul/docs/services/configuration/services-configuration-reference#weights
+[connect-sidecar]: /nomad/docs/job-specification/connect#using-sidecar-service
+[connect-native]: /nomad/docs/job-specification/connect#using-consul-service-mesh-native
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.10.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..8e5f929dba
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service block in the job specification
+description: |-
+  The `sidecar_service` block allows specifying options for configuring
+  sidecar proxies used in Consul service mesh integration
+---
+
+# `sidecar_service` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+service mesh](/nomad/docs/networking/consul) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       test-key = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.10.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..553fa96a7c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: sidecar_task block in the job specification
+description: |-
+  The `sidecar_task` block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul service mesh integration
+---
+
+# `sidecar_task` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+service mesh](/nomad/docs/networking/consul) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+## Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.10.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..79d04f00b9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: spread block in the job specification
+description: >-
+  The `spread` block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter.
+
+By default, when `spread` is omitted, the scheduler will attempt to place
+allocations from the same job on different nodes (and binpacked between
+jobs). When using `spread` the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target
+percentage defined in the spread block. Spread scores are combined with other
+scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to
+express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler. If no
+nodes match a given spread criteria, placement is still successful. To avoid
+scoring every node for every placement, allocations may not be perfectly
+spread. Spread works best on attributes with similar number of nodes:
+identically configured racks or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client
+metadata][client-meta].  Additionally, spread may be specified at the [job][job]
+and [group][group] levels for ultimate flexibility. Job level spread criteria
+are inherited by all task groups in the job.
+
+Updating the `spread` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+### Target parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## Comparison to `spread` scheduling algorithm
+
+The `spread` block is not the same concept as setting the [scheduler
+algorithm][] to `"spread"` instead of `"binpack"`. Setting the scheduler
+algorithm impacts all jobs on a cluster (or node pool), and adjusts the tendency
+of the scheduler to place workloads from different jobs on the same set of nodes
+or not. The `spread` block impacts how the scheduler places allocations for a
+given job.
+
+## Scheduling performance
+
+Using the `spread` block can have significant impact on scheduling
+performance. For each allocation in a `service` and `batch` job, the scheduler
+iterates over nodes until it finds a small number of feasible nodes. Those
+feasible nodes are then scored to find the best placement.
+
+When `spread` is omitted, this limit is 2 for batch jobs and the log<sub>2</sub>
+of the total number of nodes in the datacenter and node pool (with a minimum of
+2) for service jobs. When the `spread` block is present, the scheduler instead
+scores a number of nodes in the datacenter and node pool equal to the task group
+count (with a maximum of 100) per allocation. This can result in
+order-of-magnitude increases in scheduling times.
+
+To monitor scheduling times potentially impacted by `spread` blocks, examine the
+`nomad.nomad.worker.invoke_scheduler.*` found in the [Key Metrics][] table. You
+can reduce scheduling times by avoiding `spread` and instead relying on the
+default distribution of a job across multiple nodes. If this is not possible,
+you may consider reducing the size of the node pool or datacenter to reduce the
+number of nodes available for the scheduler to consider.
+
+## Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even spread across data center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread with target percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread across multiple attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+[Key Metrics]: /nomad/docs/reference/metrics#key-metrics
+[scheduler algorithm]: /nomad/commands/operator/scheduler/set-config#scheduler-algorithm
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/task.mdx b/content/nomad/v1.10.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..fe3eb0ea81
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: task block in the job specification
+description: |-
+  The `task` block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` block in the job specification
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `consul` <code>([Consul][consul_jobspec]: nil)</code> - Specifies Consul
+  configuration options specific to the task.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/job-declare/task-driver) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown process
+  starts by applying the `shutdown_delay` if configured. It then stops the the
+  leader task first, if any, followed by non-sidecar and non-poststop tasks, and
+  finally sidecar tasks. Once this process completes, post-stop tasks are
+  triggered. See the [lifecycle][] documentation for a complete description of
+  task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] images specify their own default users. Clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as [certain
+  users][user_denylist]. On UNIX-like systems, setting `user` also affects
+  the environment variables `HOME`, `USER`, and `LOGNAME` available to the task.
+  On Windows, when Nomad is running as a [system service][service] for the
+  [`raw_exec`][raw_exec] driver, you may specify a less-privileged service user.
+  For example, `NT AUTHORITY\LocalService`, `NT AUTHORITY\NetworkService`.
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul service mesh.
+
+## Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/job-declare/task-driver).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and environment variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_jobspec]: /nomad/docs/job-specification/consul
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/job-declare/task-driver/exec 'Nomad exec Driver'
+[raw_exec]: /nomad/docs/job-declare/task-driver/raw_exec 'Nomad raw_exec Driver'
+[java]: /nomad/docs/job-declare/task-driver/java 'Nomad Java Driver'
+[docker]: /nomad/docs/job-declare/task-driver/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
+[service]: /nomad/docs/deploy/production/windows-service
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/template.mdx b/content/nomad/v1.10.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..174d5ef758
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,836 @@
+---
+layout: docs
+page_title: template block in the job specification
+description: |-
+  The `template` block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `once` `(bool: false)` - Specifies that the client will wait for the template
+  to be rendered, and then no longer watch the dependencies specified in the
+  template. This is useful for templates that do not need to be updated. Once mode
+  implicitly disables wait/quiescence timers for this template, and ignores change
+  mode/signal/script settings.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad integration
+
+### Nomad services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple load balancing with Nomad services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin", "executeTemplate",
+  "writeToFile"])` - Specifies a list of template rendering functions that
+  should be disallowed in job specs. By default, the `plugin` function is
+  disallowed as it allows running arbitrary commands on the host as root (unless
+  Nomad is configured to run as a non-root user), `executeTemplate` is
+  disallowed to prevent accidental or malicious infinitely recursive execution,
+  and `writeToFile` is disallowed.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/docs/reference/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/reference/runtime-environment-settings 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/transparent_proxy.mdx b/content/nomad/v1.10.x/content/docs/job-specification/transparent_proxy.mdx
new file mode 100644
index 0000000000..d40af3315e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/transparent_proxy.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: transparent_proxy block in the job specification
+description: |-
+  The `transparent_proxy` block allows specifying options for configuring Envoy
+  in Consul service mesh transparent proxy mode.
+---
+
+# `transparent_proxy` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'transparent_proxy',
+  ]}
+/>
+
+The `transparent_proxy` block configures the Envoy sidecar proxy to act as a
+Consul service mesh [transparent proxy][tproxy]. This simplifies the configuration of
+Consul service mesh by eliminating the need to configure [`upstreams`][] blocks in
+Nomad. Instead, the Envoy proxy will determines its configuration entirely from
+Consul [service intentions][].
+
+When transparent proxy is enabled traffic will automatically flow through the
+Envoy proxy. If the local Consul agent is serving DNS, Nomad will also set up
+the task's nameservers to use Consul. This lets your workload use the [virtual
+IP][] DNS name from Consul, rather than configuring a `template` block that
+queries services.
+
+Using transparent proxy has some important restrictions:
+
+* You can only have a single `connect` block in any task group that uses
+  transparent proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`](#no_dns), see below).
+* The node where the allocation is placed must be configured as described in
+  the Service Mesh integration documentation for [Transparent Proxy][].
+* The workload's task cannot use the same Unix user ID (UID) as the Envoy
+  sidecar proxy.
+
+## Parameters
+
+* `exclude_inbound_ports` `([]string: nil)` - A list of inbound ports to exclude
+  from the inbound traffic redirection. This allows traffic on these ports to
+  bypass the Envoy proxy. These ports can be specified as either [network port
+  labels][port_labels] or as numeric ports. Nomad will automatically add the
+  following to this list:
+  * The [`local_path_port`][] of any [`expose`][] block.
+  * The port of any service check with [`expose=true`][check_expose] set.
+  * The port of any `network.port` with a [`static`][] value.
+* `exclude_outbound_cidrs` `([]string: nil)` - A list of CIDR subnets that
+  should be excluded from outbound traffic redirection. This allows traffic to
+  these subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_ports`; CIDR subnets listed here are excluded regardless of
+  the port.
+* `exclude_outbound_ports` `([]int: nil)` - A list of port numbers that should
+  be excluded from outbound traffic redirection. This allows traffic to these
+  subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_cidrs`; ports listed here are excluded regardless of the
+  CIDR.
+* `exclude_uids` `([]string: nil)` - A list of Unix user IDs (UIDs) that should
+  be excluded from outbound traffic redirection. When unset, only the Envoy
+  proxy's user will be allowed to bypass the iptables rule.
+* `no_dns` `(bool: false)` - By default, Consul will be set as the nameserver
+  for the workload and IP tables rules will redirect DNS queries to Consul. If
+  you want only external DNS, set `no_dns=true`. You will need to add your own
+  CIDR and port exclusions for your DNS nameserver. You cannot set
+  [`network.dns`][] if `no_dns=false`.
+* `outbound_port` `(int: 15001)` - The port that Envoy will bind on inside the
+  network namespace. The iptables rules created by `consul-cni` will force
+  traffic to flow to this port. You should only set this value if you have
+  specifically set the [`outbound_listener_port`][] in your Consul proxy
+  configuration. You can change the default value for a given node via [client
+  metadata](#client-metadata) (see below).
+* `uid` `(string "101")` - The Unix user ID (UID) used by the Envoy proxy. You
+  should only set this value if you have a custom build of the Envoy container
+  image which uses a different UID. You can change the default value for a given
+  node via [client metadata](#client-metadata) (see below). Note that your
+  workload's task cannot use the same UID as the Envoy sidecar proxy.
+
+## Client metadata
+
+You can change the default [`outbound_port`](#outbound_port) and [`uid`](#uid)
+for a given client node by updating the node metadata via the [`nomad node meta
+apply`][] command. The attributes that can be updated are:
+
+* `connect.transparent_proxy.default_uid`: Sets the default value of
+  [`uid`](#uid) for this node.
+* `connect.transparent_proxy.default_outbound_port`: Sets the default value of
+  [`outbound_port`](#outbound_port) for this node.
+
+For example, to set the default value for the `uid` field to 120:
+
+```shell-session
+$ nomad node meta apply connect.transparent_proxy.default_uid=120
+$ nomad node meta read -json | jq -r '.Dynamic | ."connect.transparent_proxy.default_uid"'
+120
+```
+
+You should not normally need to set these values unless you are using custom
+Envoy images.
+
+## Examples
+
+### Minimal
+
+The following example is a minimal transparent proxy specification. Note that
+with transparent proxy, you will not need to configure an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+If you had a downstream task group `count-dashboard` that needed to connect to
+an upstream task group `count-api` listening on port 9001, you could create a
+Consul service intention with the following specification:
+
+```hcl
+Kind = "service-intentions"
+Name = "count-api"
+Sources = [
+  {
+    Name   = "count-dashboard"
+    Action = "allow"
+  }
+]
+```
+
+And then the downstream service `count-dashboard` could reach the `count-api`
+service by making requests to `http://count-api.virtual.consul`.
+
+### External DNS
+
+The following example is a transparent proxy specification where external DNS is
+used. To find the address of other allocations in this configuration, you will
+need to use a [`template`][] block to query Consul.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+      excluded_outbound_ports = [53]
+      excluded_outbound_cidrs = ["208.67.222.222/32", "208.67.220.220/32"]
+      no_dns                  = true
+    }
+  }
+}
+```
+
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[service intentions]: /consul/docs/connect/config-entries/service-intentions
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[cni_plugins]: /nomad/docs/job-networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[port_labels]: /nomad/docs/job-specification/network#port-parameters
+[`local_path_port`]: /nomad/docs/job-specification/expose#local_path_port
+[`expose`]: /nomad/docs/job-specification/expose
+[check_expose]: /nomad/docs/job-specification/check#expose
+[`static`]: /nomad/docs/job-specification/network#static
+[`outbound_listener_port`]: /consul/docs/connect/proxies/proxy-config-reference#outbound_listener_port
+[`template`]: /nomad/docs/job-specification/template#consul-integration
+[`nomad node meta apply`]: /nomad/commands/node/meta/apply
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[Transparent Proxy]: /nomad/docs/networking/consul/service-mesh#transparent-proxy
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/ui.mdx b/content/nomad/v1.10.x/content/docs/job-specification/ui.mdx
new file mode 100644
index 0000000000..e142068717
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/ui.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: ui block in the job specification
+description: |-
+  The `ui` block adds descriptions and helpful links to a
+  job page in the Nomad Web UI.
+---
+
+# `ui` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'ui'],
+  ]}
+/>
+
+The `ui` block provides options to modify the presentation of the Job index page
+in the Web UI. When specified, a description and any number of links will be
+added to the top of the job page in question.
+
+The following will provide the Web UI with a job description and a pair of links:
+
+## Parameters
+
+- `description` `(string: "")` - The markdown-enabled description of the job. We
+  support [GitHub Flavored Markdown](https://github.github.com/gfm/).
+- `link` `(map<string|string>: nil)` - A link that should show up in the header
+  of the job index page in the Web UI. A job can have any number of links, and
+  they must contain both a string `label` and `url`.
+
+## Example
+
+```hcl
+job "docs" {
+  ui {
+    description = "A job that uses **Nomad Variables**"
+    link {
+      label = "Learn more about Nomad"
+      url   = "https://developer.hashicorp.com/nomad"
+    }
+    link {
+      label = "Nomad on GitHub"
+      url   = "https://github.com/hashicorp/nomad"
+    }
+  }
+  # ...
+}
+```
+
+![Job UI links and description rendered in the Web UI](/img/nomad-ui-block.png)
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/update.mdx b/content/nomad/v1.10.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..2f9ecc423f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update block in the job specification
+description: |-
+  The `update` block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time).
+
+## Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel upgrades based on checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel upgrades based on task state
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update block inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/docs/job-declare/strategy/blue-green-canary
+[checks]: /nomad/docs/job-specification/service#check
+[rolling]: /nomad/docs/job-declare/strategy/rolling
+[strategies]: /nomad/docs/job-declare/strategy
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.10.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..475b634e1f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: upstreams block in the job specification
+description: |-
+  The `upstreams` block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul service mesh][] proxy routes to. It is valid only within the
+context of a `proxy` block.
+
+For Consul-specific details see the [Consul service mesh Guide][]. Note that using
+`upstream` may not be necessary if you have configured the proxy with the
+[`transparent_proxy`][] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul service mesh documentation][consul_expose_path_ref]
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_partition` `(string: "")` - Name of the Cluster admin partition containing the upstream service.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul service mesh the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[Consul service mesh]: /nomad/docs/networking/consul
+[Consul service mesh Guide]: /consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
+[consul_expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.10.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..449608f0b8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: vault block in the job specification
+description: |-
+  The `vault` block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        cluster  = "default"
+        role     = "prod"
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `disable_file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## Parameters
+
+- `allow_token_expiration` `(bool: false)` - Specifies that Nomad clients should
+  not attempt to renew a task's Vault token, allowing it to expire. This should
+  only be used when a secret is requested from Vault once at the start of a task
+  or in a short-lived prestart task. Long-running tasks should never set
+  `allow_token_expiration=true` if they obtain Vault secrets via `template`
+  blocks, as the Vault token will expire and the template runner will continue
+  to make failing requests to Vault until its [`vault_retry`][] attempts are
+  exhausted, at which point the task will fail.
+
+  When Nomad has been configured to use [Workload Identity with Vault][], Nomad
+  clients will automatically detect when tokens cannot be refreshed (for
+  example, when the Vault auth method is configured to issue batch tokens). In
+  this case, the `allow_token_expiration` option will be implicitly set to
+  `true` by the client. The [legacy Vault authentication workflow][] cannot
+  automatically detect this.
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Vault cluster to use. The Nomad client will retrieve a Vault token from the
+  cluster configured in the agent configuration with the same
+  [`vault.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `role` `(string: "")` - Specifies the Vault role used when retrieving a token
+  from Vault using JWT and workload identity. If not specified the client's
+  [`create_from_role`][] value is used.
+
+## Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+Vault policies from the "prod" role attached.
+
+```hcl
+vault {
+  role = "prod"
+}
+```
+
+### Signal task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  role = "prod"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private token and change modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  role         = "prod"
+  change_mode  = "noop"
+  env          = false
+  disable_file = true
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  role      = "prod"
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[`create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[docker]: /nomad/docs/job-declare/task-driver/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
+[`vault.name`]: /nomad/docs/configuration/vault#name
+[`vault_retry`]: /nomad/docs/configuration/client#vault_retry
+[Workload Identity with Vault]: /nomad/docs/secure/vault/acl#nomad-workload-identities
+[legacy Vault authentication workflow]: /nomad/docs/v1.8.x/integrations/vault/acl
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.10.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..1af5d9801c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: volume block in the job specification
+description: >-
+  Configure storage volumes in the `volume` block of a Nomad job specification. Specify dynamic host or Container Storage Interface (CSI) volume type, node access mode, filesystem or block device attachment mode, and mount options. Enable read only access and mounting a unique volume per node. Learn about volume interpolation.
+---
+
+# `volume` block in the job specification
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server ensures that the allocations are only scheduled on hosts
+that have a set of volumes that meet the criteria specified in the `volume`
+blocks. These may be [static host volumes][host_volume] configured on the
+client, [dynamic host volumes][] created via [`volume create`][] or [`volume
+register`][], or [CSI volumes][csi_volume] dynamically mounted by [CSI
+plugins][csi_plugin].
+
+The Nomad client makes the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The valid volume
+  types are `"host"` and `"csi"`. Setting the `"host"` value can request either
+  statically configured host volumes or dynamic host volumes, depending on what
+  is available on a given node.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `sticky` `(bool: false)` - Specifies that this volume sticks to the allocation
+  that uses it. Upon every reschedule and replacement, the task
+  group always receives the volume with the same ID, if available. Use sticky
+  volumes for [stateful deployments]. You may only use the `sticky` field for
+  dynamic host volumes. For CSI volumes, the `per_alloc` field provides similar
+  functionality
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries. `per_alloc` is mutually exclusive with the `sticky`
+  property. Use `per_alloc` only with CSI volumes and `sticky` only
+  with dynamic host volumes.
+
+The following fields are only valid for volumes with `type = "csi"` or dynamic
+host volumes with `type = "host"`:
+
+- `access_mode` `(string)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks.
+
+  - For CSI volumes the `access_mode` is required. Can be one of the following:
+
+    - `"single-node-reader-only"`
+    - `"single-node-writer"`
+    - `"multi-node-reader-only"`
+    - `"multi-node-single-writer"`
+    - `"multi-node-multi-writer"`
+
+    Most CSI plugins support only single-node modes.
+    Consult the documentation of the storage provider and CSI plugin.
+
+  - For dynamic host volumes the `access_mode` is optional. Can be one of the following:
+
+    - `"single-node-writer"`
+    - `"single-node-reader-only"`
+    - `"single-node-single-writer"`
+    - `"single-node-multi-writer"`
+
+    Defaults to `single-node-writer` unless `read_only = true`, in which case it
+    defaults to `single-node-reader-only`.
+
+- `attachment_mode` `(string)` - The storage API used by the
+  volume. One of `"file-system"` or `"block-device"`. The `access_mode` and
+  `attachment_mode` together must exactly match one of the volume's `capability`
+  blocks.
+
+  - For CSI volumes the `attachment_mode` field is required. Most storage
+    providers support `"file-system"`, to mount volumes using the CSI
+    filesystem API. Some storage providers support `"block-device"`, which
+    mounts the volume with the CSI block device API within the container.
+
+  - For dynamic host volumes the `attachment_mode` field is optional and
+    defaults to `"file-system"`.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/commands/volume/register
+[attachment mode]: /nomad/commands/volume/register#attachment_mode
+[volume registration]: /nomad/commands/volume/register#mount_options
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
diff --git a/content/nomad/v1.10.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.10.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..007bd3d434
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: volume_mount block in the job specification
+description: |-
+  The `volume_mount` block allows the task to specify where a group `volume`
+  should be mounted.
+---
+
+# `volume_mount` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+- `selinux_label``(string: "")` - Specifies the SELinux label for the mount.
+  This is only supported on Linux hosts and when supported by the task driver. Refer to the task driver documentation for more information. Possible
+  values are:
+
+  - `Z` -  Specifies that the volume content is private and unshared between
+    containers.
+  - `z` - Specifies that the volume content is shared among containers.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/reference/hcl2
diff --git a/content/nomad/v1.10.x/content/docs/manage/autopilot.mdx b/content/nomad/v1.10.x/content/docs/manage/autopilot.mdx
new file mode 100644
index 0000000000..e534616910
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/autopilot.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: Autopilot
+description: |-
+  Configure and use Autopilot features to help maintain your cluster. Monitor
+  server health, upgrade and clean up servers, and use redundancy zones.
+---
+
+# Autopilot
+
+Autopilot is a set of new features added in Nomad 0.8 to allow for automatic
+operator-friendly management of Nomad servers. It includes cleanup of dead
+servers, monitoring the state of the Raft cluster, and stable server
+introduction.
+
+To enable Autopilot features (with the exception of dead server cleanup), the
+`raft_protocol` setting in the [server stanza] must be set to 3 on all servers.
+
+## Configuration
+
+The configuration of Autopilot is loaded by the leader from the agent's
+[Autopilot settings] when initially bootstrapping the cluster:
+
+```hcl
+autopilot {
+  cleanup_dead_servers      = true
+  last_contact_threshold    = "200ms"
+  max_trailing_logs         = 250
+  server_stabilization_time = "10s"
+  enable_redundancy_zones   = false
+  disable_upgrade_migration = false
+  enable_custom_upgrades    = false
+}
+
+```
+
+After bootstrapping, the configuration can be viewed or modified either via the
+[`operator autopilot`] subcommand or the
+[`/v1/operator/autopilot/configuration`] HTTP endpoint:
+
+View the configuration.
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+EnableRedundancyZones = false
+DisableUpgradeMigration = false
+EnableCustomUpgrades = false
+```
+
+Update the configuration.
+
+```shell-session
+$ nomad operator autopilot set-config -cleanup-dead-servers=false
+Configuration updated!
+```
+
+View the configuration to confirm your changes.
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = false
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+EnableRedundancyZones = false
+DisableUpgradeMigration = false
+EnableCustomUpgrades = false
+```
+
+## Dead server cleanup
+
+Dead servers will periodically be cleaned up and removed from the Raft peer set,
+to prevent them from interfering with the quorum size and leader elections. This
+cleanup will also happen whenever a new server is successfully added to the
+cluster.
+
+Prior to Autopilot, it would take 72 hours for dead servers to be automatically
+reaped, or operators had to script a `nomad force-leave`. If another server
+failure occurred, it could jeopardize the quorum, even if the failed Nomad
+server had been automatically replaced. Autopilot helps prevent these kinds of
+outages by quickly removing failed servers as soon as a replacement Nomad server
+comes online. When servers are removed by the cleanup process they will enter
+the "left" state.
+
+This option can be disabled by running `nomad operator autopilot set-config`
+with the `-cleanup-dead-servers=false` option.
+
+## Server health checking
+
+An internal health check runs on the leader to monitor the stability of servers.
+A server is considered healthy if all of the following conditions are true:
+
+- Its status according to Serf is 'Alive'
+
+- The time since its last contact with the current leader is below
+  `LastContactThreshold`
+
+- Its latest Raft term matches the leader's term
+
+- The number of Raft log entries it trails the leader by does not exceed
+  `MaxTrailingLogs`
+
+The status of these health checks can be viewed through the
+[`/v1/operator/autopilot/health`] HTTP endpoint, with a top level `Healthy`
+field indicating the overall status of the cluster:
+
+```shell-session
+$ curl localhost:4646/v1/operator/autopilot/health
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 10,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-28T18:28:52Z"
+    },
+    {
+      "ID": "e35bde83-4e9c-434f-a6ef-453f44ee21ea",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "35.371007ms",
+      "LastTerm": 2,
+      "LastIndex": 10,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-28T18:29:10Z"
+    }
+  ]
+}
+
+```
+
+## Stable server introduction
+
+When a new server is added to the cluster, there is a waiting period where it
+must be healthy and stable for a certain amount of time before being promoted to
+a full, voting member. This can be configured via the `ServerStabilizationTime`
+setting.
+
+## Server read and scheduling scaling <EnterpriseAlert inline />
+
+With the [`non_voting_server`] option, a server can be explicitly marked as a
+non-voter and will never be promoted to a voting member. This can be useful when
+more read scaling is needed; being a non-voter means that the server will still
+have data replicated to it, but it will not be part of the quorum that the
+leader must wait for before committing log entries. Non voting servers can also
+act as scheduling workers to increase scheduling throughput in large clusters.
+
+## Redundancy zones <EnterpriseAlert inline />
+
+Prior to Autopilot, it was difficult to deploy servers in a way that took
+advantage of isolated failure domains such as AWS Availability Zones; users
+would be forced to either have an overly-large quorum (2-3 nodes per AZ) or give
+up redundancy within an AZ by deploying only one server in each.
+
+If the `EnableRedundancyZones` setting is set, Nomad will use its value to look
+for a zone in each server's specified [`redundancy_zone`] field.
+
+Here's an example showing how to configure this:
+
+```hcl
+/* config.hcl */
+server {
+  redundancy_zone = "west-1"
+}
+```
+
+```shell-session
+$ nomad operator autopilot set-config -enable-redundancy-zones=true
+Configuration updated!
+```
+
+Nomad will then use these values to partition the servers by redundancy zone,
+and will aim to keep one voting server per zone. Extra servers in each zone will
+stay as non-voters on standby to be promoted if the active voter leaves or dies.
+
+## Upgrade migrations <EnterpriseAlert inline />
+
+Autopilot in Nomad Enterprise supports upgrade migrations by default. To disable
+this functionality, set `DisableUpgradeMigration` to true.
+
+When a new server is added and Autopilot detects that its Nomad version is newer
+than that of the existing servers, Autopilot will avoid promoting the new server
+until enough newer-versioned servers have been added to the cluster. When the
+count of new servers equals or exceeds that of the old servers, Autopilot will
+begin promoting the new servers to voters and demoting the old servers. After
+this is finished, the old servers can be safely removed from the cluster.
+
+To check the Nomad version of the servers, either the [autopilot health]
+endpoint or the `nomad members`command can be used:
+
+```shell-session
+$ nomad server members
+Name   Address    Port  Status  Leader  Protocol  Build  Datacenter  Region
+node1  127.0.0.1  4648  alive   true    3         0.7.1  dc1         global
+node2  127.0.0.1  4748  alive   false   3         0.7.1  dc1         global
+node3  127.0.0.1  4848  alive   false   3         0.7.1  dc1         global
+node4  127.0.0.1  4948  alive   false   3         0.8.0  dc1         global
+```
+
+### Migrations without a Nomad version change
+
+The `EnableCustomUpgrades` field can be used to override the version information
+used during a migration, so that the migration logic can be used for updating
+the cluster when changing configuration.
+
+If the `EnableCustomUpgrades` setting is set to `true`, Nomad will use its value
+to look for a version in each server's specified [`upgrade_version`] tag. The
+upgrade logic will follow semantic versioning and the `upgrade_version` must be
+in the form of either `X`, `X.Y`, or `X.Y.Z`.
+
+[`/v1/operator/autopilot/configuration`]: /nomad/api-docs/operator/autopilot
+[`/v1/operator/autopilot/health`]: /nomad/api-docs/operator/autopilot#read-health
+[`non_voting_server`]: /nomad/docs/configuration/server#non_voting_server
+[`operator autopilot`]: /nomad/commands/operator
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot health]: /nomad/api-docs/operator/autopilot#read-health
+[autopilot settings]: /nomad/docs/configuration/autopilot
+[nomad enterprise]: https://www.hashicorp.com/products/nomad
+[server stanza]: /nomad/docs/configuration/server
+[version upgrade section]: /nomad/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility
diff --git a/content/nomad/v1.10.x/content/docs/manage/format-cli-output.mdx b/content/nomad/v1.10.x/content/docs/manage/format-cli-output.mdx
new file mode 100644
index 0000000000..0b99a8271e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/format-cli-output.mdx
@@ -0,0 +1,415 @@
+---
+layout: docs
+page_title: Format CLI output with templates
+description: |-
+  Customize the output of Nomad CLI commands with Go template syntax. Practice
+  interacting with unfamiliar template contexts.
+---
+
+# Format CLI output with templates
+
+When using Nomad at an intermediate to advanced level, you'll need to interface with other systems or customize output generated by Nomad. The `-t` flag is a powerful way to pass a template in Go's text/template format to
+several of the Nomad commands that generate output based on the API. This allows
+you to filter and customize the output to meet your specific needs.
+
+The commands that allow for the -t flag are:
+
+- `nomad acl policy list`
+- `nomad acl token list`
+- `nomad alloc status`
+- `nomad deployment list`
+- `nomad deployment status`
+- `nomad eval status`
+- `nomad job deployments`
+- `nomad job history`
+- `nomad job inspect`
+- `nomad namespace list`
+- `nomad node status`
+- `nomad plugin status`
+- `nomad quota list`
+- `nomad volume status`
+
+This guide will teach you how to explore the objects that are returned to
+the template engine and how to use template syntax to format the output into
+a custom form.
+
+## Prerequisites
+
+This guide assumes the following:
+
+- Familiarity with Go's text/template syntax. You can learn more about it in the
+  [Go template syntax][go-template-syntax] reference.
+
+- That you are running these commands against a Nomad cluster with an active
+  workload. You can create a minimal environment using a dev agent, started with
+  `sudo nomad agent -dev`, then running at least one Nomad job. You can use
+  `nomad init -short` to create a sample Docker job or provide your own Nomad
+  job.
+
+## Note the shell-specific syntax
+
+When using the -t flag, you need to correctly handle string literals based on
+your shell environment. In a POSIX shell, you can run the following with a
+single quote:
+
+```shell-session
+$ nomad node status  -t '{{printf "%#+v" .}}'
+```
+
+In a Windows shell (for example, PowerShell), use single
+quotes but escape the double quotes inside the parameter as follows:
+
+```powershell
+PS> nomad node status  -t '{{printf \"%#+v\" .}}'
+```
+
+In this guide, you can select examples with the proper escaping using the
+tabs above the snippets.
+
+## Start discovering objects
+
+The `printf` function and the `"%#+v"` format string are critical tools for you
+in exploring an unfamiliar template context.
+
+Run the following command to output the context being passed to the template
+in Go object format.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{printf "%#+v" .}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{printf \"%#+v\" .}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+[]*api.NodeListStub{(*api.NodeListStub)(0xc0003fa160), (*api.NodeListStub)(0xc0003fa0b0), (*api.NodeListStub)(0xc0003fa000)}
+```
+
+The output indicates that the context consists of a list (`[]`) of pointers
+(`*`) to `api.NodeListStub` objects. The list will also show one NodeListStub
+object per client node in your cluster's server state.
+
+You can explore these api.NodeListStub object by using the `range` control over
+the list.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{range .}}{{printf "%#+v" .}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{range .}}{{printf \"%#+v\" .}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+If you have a lot of client nodes in your cluster state, this output will be
+unwieldy. In that case, you can use `with` and the index function to get the
+first list item.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{with index . 0}}{{printf "%#+v" .}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{with index . 0}}{{printf \"%#+v\" .}}{{end}}'
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+Finally, output `Name` and `Version` for each client in the cluster.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{range .}}{{printf "%s: %s\n" .Name .Version}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{range .}}{{printf \"%s: %s\n\" .Name .Version}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+nomad-client-2.node.consul: 0.12.0
+nomad-client-3.node.consul: 0.12.0
+nomad-client-1.node.consul: 0.12.0
+```
+
+## Make quiet output
+
+Suppose you want to create a reduced version of the `nomad job status` output
+to show just the running job IDs in your cluster and nothing else.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad job inspect -t '{{range .}}{{if eq .Status "running"}}{{ println .Name}}{{end}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad job inspect -t '{{range .}}{{if eq .Status \"running\"}}{{ println .Name}}{{end}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+Nomad will output the job IDs for every running job in your cluster. For example:
+
+```plaintext
+fabio
+sockshop-carts
+sockshop-catalogue
+sockshop-frontend
+sockshop-infra
+sockshop-orders
+sockshop-payment
+sockshop-shipping
+sockshop-user
+```
+
+### Challenge yourself
+
+Allocations have a slightly different shape. How might you create similar output
+from the `nomad alloc status` command? Make sure that your Nomad cluster has at
+least one allocation running and then use the printf technique from earlier to
+explore the values sent into the template.
+
+<Accordion heading="View Solution" collapse="true">
+
+
+Print the context that you are passed from the command using the printf command.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{printf "%#+v" . }}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{printf \"%#+v\" . }}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+[]*api.AllocationListStub ...
+```
+
+Note that the first thing that you receive is a list (`[]`) of pointers (`*`) to
+`AllocationListStub` objects.
+
+Use `range` to traverse each item in the list.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{range .}}{{printf "%#+v" . }}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{range .}}{{printf \"%#+v\" . }}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.AllocationListStub{ID:"30663b68-4d8a-aada-4ad2-011b1acae3a1", EvalID:"c5eda90b-f675-048e-b2f7-9ced30e4916b", Name:"sockshop-user.userdb[0]", Namespace:"default", NodeID:"3be35c12-70aa-8816-195e-a4630a457727", NodeName:"nomad-client-3.node.consul", JobID:"sockshop-user", JobType:"service", JobVersion:0x0, ...
+```
+
+If you have a lot of allocations running, this could get unwieldy. In that case,
+you can use `with` and the index function to get the first list item.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{with index . 0}}{{printf "%#+v" . }}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{with index . 0}}{{printf \"%#+v\" . }}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.AllocationListStub{ID:"30663b68-4d8a-aada-4ad2-011b1acae3a1", EvalID:"c5eda90b-f675-048e-b2f7-9ced30e4916b", Name:"sockshop-user.userdb[0]", Namespace:"default", NodeID:"3be35c12-70aa-8816-195e-a4630a457727", NodeName:"nomad-client-3.node.consul", JobID:"sockshop-user", JobType:"service", JobVersion:0x0, ...
+```
+
+The fields on the AllocationListStub object that give insight into the running
+state of an allocation are `DesiredStatus` and `ClientStatus`.
+
+-> **Did you know?** The definition of an [AllocationListStub][] object and
+valid values for the DesiredStatus and ClientStatus are located in Nomad's
+[api package][]. Take a moment to look at it and see what other information you
+might be interested in displaying with templates.
+
+Update your template to show items with a DesiredStatus of "run" and a client
+status of "running" or "pending."
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{range .}}{{if and (eq .DesiredStatus "run") (or (eq .ClientStatus "running") (eq .ClientStatus "pending"))}}{{println .ID}}{{end}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{range .}}{{if and (eq .DesiredStatus \"run\") (or (eq .ClientStatus \"running\") (eq .ClientStatus \"pending\"))}}{{println .ID}}{{end}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+30663b68-4d8a-aada-4ad2-011b1acae3a1
+11b916da-d679-1718-26f3-f6cd499bfdb8
+68bcb157-359f-9293-d091-5a8ef71475ad
+...
+```
+
+You now have a list of the IDs for all of the allocations running in your Nomad
+cluster.
+
+</Accordion>
+
+
+## Retrieve a template from file
+
+Using the command line to write templates becomes challenging
+as the template becomes more complex.
+
+By writing a template in its own file, you can use comments, span multiple lines, and indent conditionals in order to make them more readable to you and to other operators.
+
+Consider using some of these techniques
+to include the template data into the command.
+
+<Tabs>
+<Tab heading="Posix Shells" group="posix">
+
+
+Create a file named running_jobs.tmpl with the following content.
+
+```plaintext
+{{- /*
+  Get Running Jobs
+  Run with `nomad job inspect -t "$(cat running_jobs.tmpl)"`
+*/ -}}
+{{- range . -}}
+  {{- if eq .Status "running" -}}
+    {{- println .Name -}}
+  {{- end -}}
+{{- end -}}
+```
+
+Now, use a subshell to read the file into a variable
+
+```shell-session
+$ nomad job inspect -t "$(cat running_jobs.tmpl)"
+```
+
+</Tab>
+<Tab heading="PowerShell" group="ps">
+
+
+Create a file named running_jobs.tmpl with the following content.
+
+```plaintext
+{{- /*
+  Get Running Jobs
+  Run with:
+    $content=Get-Content running_jobs.tmpl -Raw; nomad job inspect -t $content
+*/ -}}
+{{- range . -}}
+  {{- if eq .Status \"running\" -}}
+    {{- println .Name -}}
+  {{- end -}}
+{{- end -}}
+```
+
+Now, use a subshell to read the file into a variable
+
+```powershell
+PS> $content=Get-Content running_jobs.tmpl -Raw; nomad job inspect -t $content
+```
+
+</Tab>
+</Tabs>
+
+
+## Learn more
+
+In this guide, you learned how to:
+
+- Customize the output of several Nomad commands using Go's text/template
+  syntax.
+
+- Use the `printf` function to discover what is available in the template's
+  context.
+
+- Use a template definition contained in a file as part of the command.
+
+
+[go-template-syntax]: /nomad/docs/reference/go-template-syntax
+[allocationliststub]: https://godoc.org/github.com/hashicorp/nomad/api#AllocationListStub
+[api package]: https://godoc.org/github.com/hashicorp/nomad/api
diff --git a/content/nomad/v1.10.x/content/docs/manage/garbage-collection.mdx b/content/nomad/v1.10.x/content/docs/manage/garbage-collection.mdx
new file mode 100644
index 0000000000..68dc653da5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/garbage-collection.mdx
@@ -0,0 +1,225 @@
+---
+layout: docs
+page_title: Garbage collection
+description: |-
+  Nomad garbage collects Access Control List (ACL) tokens, allocations, deployments, encryption root keys, evaluations, jobs, nodes, plugins, and Container Storage Interface (CSI) volumes. Learn about server-side and client-side garbage collection processes, including configuration and triggers.
+---
+
+# Garbage collection
+
+Nomad garbage collection is not the same as garbage collection in a programming
+language, but the motivation behind its design is similar: garbage collection
+frees up memory allocated for objects that the schedular no longer references or
+needs. Nomad only garbage collects objects that are in a terminal state and only
+after a delay to allow inspection or debugging.
+
+Nomad runs garbage collection processes on servers and on client nodes. You may
+also manually trigger garbage collection on the server.
+
+Nomad garbage collects the following objects:
+
+- [ACL token](#configuration)
+- [Allocation](#client-side-garbage-collection)
+- [CSI Plugin](#configuration)
+- [Deployment](#configuration)
+- [Encryption root key](#configuration)
+- [Evaluation](#configuration)
+- [Job](#configuration)
+- [Node](#configuration)
+- [Volume](#configuration)
+
+## Cascading garbage collection
+
+Nomad's scheduled garbage collection processes generally handle each resource
+type independently. However, there is an implicit cascading relationship because
+of how objects reference each other. In practice, when Nomad garbage collects a
+higher-level object, Nomad also removes the object's associated sub-objects to
+prevent orphaned objects.
+
+For example, garbage collecting a job also causes Nomad to drop all of that
+job's remaining evaluations, deployments, and allocation records from the state.
+Nomad garbage collects those objects, either as part of the job garbage
+collection process or by each object's own garbage collection processes running
+immediately after. Nomad's scheduled garbage collection processes only garbage
+collect objects after they are terminal for at least the specified time
+threshold and no longer needed for future scheduling decisions. This also means
+that if a job is stopped it can't be garbage collected until its allocations are
+terminal. Note that when you force garbage collection by running the `nomad
+system gc` command, Nomad ignores the specified time threshold, but all
+other conditions still apply.
+
+## Server-side garbage collection
+
+The Nomad server leader starts periodic garbage collection processes that clean
+objects marked for garbage collection from memory. Nomad automatically marks
+some objects, like evaluations, for garbage collection. Alternatively, you may
+manually mark jobs for garbage collection by running `nomad system gc`, which
+runs the garbage collection process.
+
+### Configuration
+
+These settings govern garbage collection behavior on the server nodes. You may
+review the intervals in the [`config.go`
+class](https://github.com/hashicorp/nomad/blob/b11619010e1c83488e14e2785569e515b2769062/nomad/config.go#L564)
+for objects without a configurable interval setting.
+
+| Object | Interval | Threshold |
+|---|---|---|
+| **ACL token** | 5 minutes | [`acl_token_gc_threshold`](/nomad/docs/configuration/server#acl_token_gc_threshold)<br/>Default: 1 hour |
+| **CSI Plugin** | 5 minutes | [`csi_plugin_gc_threshold`](/nomad/docs/configuration/server#csi_plugin_gc_threshold)<br/>Default: 1 hour |
+| **Deployment** | 5 minutes | [`deployment_gc_threshold`](/nomad/docs/configuration/server#deployment_gc_threshold)<br/>Default: 1 hour |
+| **Encryption root key** | [`root_key_gc_interval`](/nomad/docs/configuration/server#root_key_gc_interval)<br/>Default: 10 minutes | [`root_key_gc_threshold`](/nomad/docs/configuration/server#root_key_gc_threshold)<br/>Default: 1 hour  |
+| **Evaluation** | 5 minutes | [`eval_gc_threshold`](/nomad/docs/configuration/server#eval_gc_threshold) <br/>Default: 1 hour |
+| **Evaluation, batch** |  5 minutes | [`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)<br/>Default: 24 hours |
+| **Job** | [`job_gc_interval`](/nomad/docs/configuration/server#job_gc_interval)<br/>Default: 5 minutes | [`job_gc_threshold`](/nomad/docs/configuration/server#job_gc_threshold)<br/>Default: 4 hours |
+| **Node** | 5 minutes | [`node_gc_threshold`](/nomad/docs/configuration/server#node_gc_threshold)<br/>Default: 24 hours |
+| **Volume** | [`csi_volume_claim_gc_interval`](/nomad/docs/configuration/server#csi_volume_claim_gc_interval)<br/>Default: 5 minutes| [`csi_volume_claim_gc_threshold`](/nomad/docs/configuration/server#csi_volume_claim_gc_threshold)<br/>Default: 1 hour |
+
+Allocations do not have an independent threshold configuration. Because
+specific evaluations create allocations, Nomad garbage collects allocations
+when garbage collecting their evaluations. This also means that Nomad
+cannot garbage collect evaluations until their allocations are terminal.
+
+### Triggers
+
+The server garbage collection processes wake up at configured intervals to scan
+for any expired or terminal objects to permanently delete, provided the object's
+time in a terminal state exceeds its garbage collection threshold. For example,
+a job's default garbage collection threshold is four hours, so the job must be
+in a terminal state for at least four hours before the garbage collection
+process permanently deletes the job and its dependent objects.
+
+When you force garbage collection by manually running the `nomad system gc`
+command, you are telling the garbage collection process to ignore thresholds and
+immediately purge all terminal objects on all servers and clients.
+
+## Client-side garbage collection
+
+On each client node, Nomad must clean up resources from terminated allocations
+to free disk and memory on the machine.
+
+### Configuration
+
+These settings govern allocation garbage collection behavior on each client node.
+
+| Parameter | Default | Description  |
+| -------- | ------- | ------------- |
+| [`gc_interval`](/nomad/docs/configuration/client#gc_interval)  | 1 minute | Interval at which Nomad attempts to garbage collect terminal allocation directories |
+| [ `gc_disk_usage_threshold` ](/nomad/docs/configuration/client#gc_disk_usage_threshold)  | 80 | Disk usage percent which Nomad tries to maintain by garbage collecting terminal allocations |
+| [ `gc_inode_usage_threshold` ](/nomad/docs/configuration/client#gc_inode_usage_threshold) | 70 | Inode usage percent which Nomad tries to maintain by garbage collecting terminal allocations |
+| [ `gc_max_allocs` ](/nomad/docs/configuration/client#gc_max_allocs) | 50 | Maximum number of allocations which a client will track before triggering a garbage collection of terminal allocations |
+| [ `gc_parallel_destroys ` ](/nomad/docs/configuration/client#gc_parallel_destroys) | 2 | Maximum number of parallel destroys allowed by the garbage collector |
+
+Refer to the [client block in agent configuration
+reference](/nomad/docs/configuration/client) for complete parameter descriptions
+and examples.
+
+Note that there is no time-based retention setting for allocations on the
+client. As soon as an allocation is terminal, it becomes eligible for cleanup if
+the configured thresholds demand it or if the allocation is garbage collected on
+the server.
+
+### Triggers
+
+Nomad's client runs allocation garbage collection based on these triggers:
+
+- Scheduled interval
+
+  The garbage collection process launches a ticker based on the configured
+  `gc_interval`. On each tick, the garbage collection process checks to see if
+  it needs to remove terminal allocations.
+
+- Terminal state
+
+  When an allocation transitions to a terminal state, Nomad marks the allocation
+  for garbage collection and then signals the garbage collection process to run
+  immediately. As with the scheduled interval, this may be a no-op if the
+  thresholds have not been reached.
+
+- Allocation placement
+
+  Nomad may preemptively run garbage collection to make room for new
+  allocations. The client garbage collects older, terminal allocations if adding
+  new allocations would exceed the `gc_max_allocs` limit.
+
+- Server garbage collection
+
+  When the server garbage collects an allocation or you force garbage collection
+  by running the `nomad system gc` command, the garbage collection process
+  removes all terminal objects on all servers and clients, ignoring all
+  threshold settings cluster-wide.
+
+Nomad does not continuously monitor disk or inode usage to trigger garbage
+collection. Instead, Nomad only checks disk and inode thresholds when one of the
+aforementioned triggers invokes the garbage collection process. The
+`gc_inode_usage_threshold` and `gc_disk_usage_threshold` values do not trigger
+garbage collection; rather, those values influence how the garbage collector
+behaves during a collection run.
+
+### Allocation selection
+
+When the garbage collection process runs, Nomad destroys as many finished
+allocations as needed to meet the resource thresholds. The client maintains a
+priority queue of terminal allocations ordered by the time they were marked
+finished, oldest first.
+
+The process repeatedly evicts allocations from the queue until the conditions
+are back within configured limits. Specifically, the garbage collection loop
+checks, in order:
+
+1. If disk usage exceeds `gc_disk_usage_threshold` value
+1. If inode usage exceeds `gc_inode_usage_threshold` value
+1. If the count of allocations exceeds `gc_max_allocs` value
+
+If any one of these conditions is true, the garbage collector selects the oldest
+finished allocation for removal.
+
+After deleting one allocation, the loop re-checks the metrics and continues
+removing the next-oldest allocation until all thresholds are satisfied or
+until there are no more terminal allocs. This means in a single run, the
+garbage collection removes multiple allocations back-to-back if the node was
+far over the limits. The evictions happen in termination-time order, which is
+oldest completed allocations first.
+
+If node's usage and allocation count are under the limits, a normal garbage
+collection cycle does not remove any allocations. In other words, periodic and
+event-driven garbage collection does not delete allocations just because they
+are finished. There has to be pressure or a limit reached. The exception is when
+an administrative command or server-side removal triggers client-side garbage
+collection. Aside from that forced scenario, the default behavior is
+threshold-driven: Nomad leaves allocations on disk until it needs to reclaim
+those allocations due to space, inode, or count limits being hit.
+
+### Task driver resources garbage collection
+
+Most task drivers do not have their own garbage collection process. When an
+allocation is terminal, the client garbage collection process communicates with
+the task driver to ensure the task's resources have been cleaned up. Note that
+the Docker task driver periodically cleans up its own resources. Refer to the
+[Docker task driver plugin
+options](https://developer.hashicorp.com/nomad/docs/deploy/task-driver/docker#gc) for
+details.
+
+When a task has configured restart attempts and the task fails, the Nomad client
+attempts an in-place task restart within the same allocation. The task driver
+starts a new process or container for the task. If the task continues to fail
+and exceeds the configured restart attempts, Nomad terminates the task and marks
+the allocation as terminal. The task driver then cleans up its resources, such
+as a Docker container or cgroups. When the garbage collection process runs, it
+makes sure that the task driver cleanup is done before deleting the allocation.
+If a task driver fails to clean up properly, Nomad logs errors but continues the
+garbage collection process. Task driver cleanup failure issues can influence
+when the allocation truly frees up. For instance, if volumes are not detached,
+disk space might not be fully reclaimed until fixed.
+
+## Resources
+
+- [Nomad's internal garbage collection and optimization discovery during the
+  Nomad Bench project blog post](https://www.hashicorp.com/en/blog/nomad-garbage-collection-optimization-discovery-during-nomad-bench)
+- Configuration
+
+  - [client Block in Agent Configuration](/nomad/docs/configuration/client)
+  - [server Block in Agent Configuration](/nomad/docs/configuration/server)
+
+- [the `nomad system gc` command reference](/nomad/commands/system/gc)
+- [System HTTP API Force GC](/nomad/api-docs/system#force-gc)
diff --git a/content/nomad/v1.10.x/content/docs/manage/index.mdx b/content/nomad/v1.10.x/content/docs/manage/index.mdx
new file mode 100644
index 0000000000..ea2ddaf4c9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/index.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Manage Nomad
+description: |-
+  This section provides guidance on the operational management of Nomad. Topics include garbage collection, key management, workload migration, outage recovery, enabling Autopilot, formatting command output, and using namespaces.
+---
+
+# Manage Nomad
+
+This section provides guidance on the operational management of Nomad. Topics include garbage collection, key management, workload migration, outage recovery, enabling Autopilot, formatting command output, and using namespaces.
diff --git a/content/nomad/v1.10.x/content/docs/manage/key-management.mdx b/content/nomad/v1.10.x/content/docs/manage/key-management.mdx
new file mode 100644
index 0000000000..25704c5134
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/key-management.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Key management
+description: |-
+  Learn how Nomad manages its keyring, which Nomad uses to encrypt variables, sign task workload identities, and sign OpenID Connect (OIDC) client assertions. Review key rotation, key decryption, and key redaction in Raft snapshots. Learn how Nomad v1.9+ can replicate keys from older Nomad versions.
+---
+
+# Key management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][],
+sign task [workload identities][], and sign OIDC [client assertion JWTs][].
+The servers encrypt these data encryption keys (DEK) and store the wrapped keys
+in Raft.
+
+The key encryption key (KEK) used to encrypt the DEK is controlled by the
+[`keyring`][] provider. When using an external KMS or Vault transit encryption
+provider, the KEK is securely stored outside of Nomad. For the default AEAD
+provider, the KEK is stored in cleartext in Raft.
+
+<Note>
+
+Default AEAD provider users should be aware that storing the Key Encryption Key
+(KEK) in cleartext in Raft may expose data in case of a breach.
+
+</Note>
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key decryption
+
+When a leader is elected, the leader creates the keyring if it does not already
+exist. When a key is added, the new wrapped key material is replicated via
+Raft. As each server replicates the new key, the server starts a task to decrypt
+the key material. Until this task completes, the server is not able to serve
+requests that require this key.
+
+## Key redaction in Raft scenario snapshots
+
+The default AEAD `keyring` configuration stores the KEK in Raft. Raft snapshots
+contain the cleartext KEK. The `nomad operator snapshot save` command has a
+`-redact` option that removes the key material when creating a snapshot. The
+`nomad operator snapshot redact` command removes key material from an
+existing snapshot.
+
+Redacting key material is not required when using an external KMS.
+
+## Legacy keystore
+
+Versions of Nomad prior to 1.9.0 stored only key metadata in Raft, but the
+encryption key material was stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Each server runs a key replication process that watches for changes to the state
+store and fetches the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election. Nomad 1.9.0 and above can replicate keys
+from older servers.
+
+However, replicating keys from older servers means that to restore an older cluster from snapshot you need to
+also provide the keystore directory with the `.nks.json` key files on at least
+one server. The `.nks.json` key files are unique per server, but only one
+server's key files are needed to recover the cluster. Operators should continue
+to include these files as part of your organization's backup and recovery
+strategy for the cluster until the cluster is fully upgraded to Nomad 1.9.0 and
+at least one [`root_key_gc_interval`][] has passed.
+
+If you are recovering an older Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[client assertion JWTs]: /nomad/docs/secure/authentication/oidc#client-assertions
+[data directory]: /nomad/docs/configuration#data_dir
+[`keyring`]: /nomad/docs/configuration/keyring
+[`nomad operator root keyring rotate -full`]: /nomad/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/commands/operator/root/keyring-rotate
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.10.x/content/docs/manage/migrate-workloads.mdx b/content/nomad/v1.10.x/content/docs/manage/migrate-workloads.mdx
new file mode 100644
index 0000000000..041595a6ee
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/migrate-workloads.mdx
@@ -0,0 +1,361 @@
+---
+layout: docs
+page_title: Migrate workloads
+description: |-
+  Configure jobs to allow Nomad to migrate workloads during events like node
+  drains. Discover how to customize migration configuration for your
+  applications.
+---
+
+# Migrate workloads
+
+Migrating workloads and decommissioning nodes are a normal part of cluster
+operations for a variety of reasons: server maintenance, operating system
+upgrades, etc. Nomad offers a number of parameters for controlling how running
+jobs are migrated off of draining nodes.
+
+## Define how your job is migrated
+
+In Nomad 0.8, a [`migrate`][migrate] stanza was added to jobs to allow control
+over how allocations for a job are migrated off of a draining node. Below is an
+example job that runs a web service and has a Consul health check:
+
+```hcl
+job "webapp" {
+  datacenters = ["dc1"]
+
+  migrate {
+    max_parallel = 2
+    health_check = "checks"
+    min_healthy_time = "15s"
+    healthy_deadline = "5m"
+  }
+
+  group "webapp" {
+    count = 9
+
+    network {
+      port "http" {
+        to = 5678
+      }
+    }
+
+    task "webapp" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo:0.2.3"
+        args  = ["-text", "ok"]
+        ports = ["http"]
+      }
+
+      service {
+        name = "webapp"
+        port = "http"
+        check {
+          name = "http-ok"
+          type = "http"
+          path = "/"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+The above `migrate` stanza ensures only 2 allocations are stopped at a time to
+migrate during node drains. Even if multiple nodes running allocations for this
+job were draining at the same time, only 2 allocations would be migrated at a
+time.
+
+When the job is run it may be placed on multiple nodes. In the following
+example the 9 `webapp` allocations are spread across 2 nodes:
+
+```shell-session
+$ nomad run webapp.nomad.hcl
+==> Monitoring evaluation "5129bc74"
+    Evaluation triggered by job "webapp"
+    Allocation "5b4d6db5" created: node "46f1c6c4", group "webapp"
+    Allocation "670a715f" created: node "f7476465", group "webapp"
+    Allocation "78b6b393" created: node "46f1c6c4", group "webapp"
+    Allocation "85743ff5" created: node "f7476465", group "webapp"
+    Allocation "edf71a5d" created: node "f7476465", group "webapp"
+    Allocation "56f770c0" created: node "46f1c6c4", group "webapp"
+    Allocation "9a51a484" created: node "46f1c6c4", group "webapp"
+    Allocation "f6f6e64c" created: node "f7476465", group "webapp"
+    Allocation "fefe81d0" created: node "f7476465", group "webapp"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5129bc74" finished with status "complete"
+```
+
+If one those nodes needed to be decommissioned, perhaps because of a hardware
+issue, then an operator would issue node drain to migrate the allocations off:
+
+```shell-session
+$ nomad node drain -enable -yes 46f1
+2018-04-11T23:41:56Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-04-11T23:41:56Z: Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" drain strategy set
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" draining
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" draining
+2018-04-11T23:42:03Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" status running -> complete
+2018-04-11T23:42:03Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" status running -> complete
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" marked for migration
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" draining
+2018-04-11T23:42:27Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" status running -> complete
+2018-04-11T23:42:29Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" marked for migration
+2018-04-11T23:42:29Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" draining
+2018-04-11T23:42:29Z: Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" has marked all allocations for migration
+2018-04-11T23:42:34Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" status running -> complete
+2018-04-11T23:42:34Z: All allocations on node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" have stopped.
+```
+
+There are a couple of important events to notice in the output. First, only two
+allocations are migrated initially:
+
+```plaintext
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" marked for migration
+```
+
+This is because `max_parallel = 2` in the job specification. The next
+allocation on the draining node waits to be migrated:
+
+```plaintext
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" marked for migration
+```
+
+Note that this occurs 25 seconds after the initial migrations. The 25 second
+delay is because a replacement allocation took 10 seconds to become healthy and
+then the `min_healthy_time = "15s"` meant node draining waited an additional 15
+seconds. If the replacement allocation had failed within that time the node
+drain would not have continued until a replacement could be successfully made.
+
+### Verify drained node's scheduling eligibility
+
+Now that the example drain has finished you can inspect the state of the drained
+node:
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  eligible     ready
+96b52ad8  dc1  nomad-2  <none>  false  eligible     ready
+46f1c6c4  dc1  nomad-3  <none>  false  ineligible   ready
+```
+
+While node `46f1c6c4` has `Drain = false`, notice that its `Eligibility = ineligible`. Node scheduling eligibility is a new field in Nomad 0.8. When a
+node is ineligible for scheduling the scheduler will not consider it for new
+placements.
+
+While draining, a node will always be ineligible for scheduling. Once draining
+completes it will remain ineligible to prevent refilling a newly drained node.
+
+However, by default canceling a drain with the `-disable` option will reset a
+node to be eligible for scheduling. To cancel a drain and preserving the node's
+ineligible status use the `-keep-ineligible` option.
+
+Scheduling eligibility can be toggled independently of node drains by using the
+[`nomad node eligibility`][eligibility] command:
+
+```shell-session
+$ nomad node eligibility -disable 46f1
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+```
+
+### Use a drain deadline to force completion
+
+Sometimes a drain is unable to proceed and complete normally. This could be
+caused by not enough capacity existing in the cluster to replace the drained
+allocations or by replacement allocations failing to start successfully in a
+timely fashion.
+
+Operators may specify a deadline when enabling a node drain to prevent drains
+from not finishing. Once the deadline is reached, all remaining allocations on
+the node are stopped regardless of `migrate` stanza parameters.
+
+The default deadline is 1 hour and may be changed with the
+[`-deadline`][deadline] command line option. The [`-force`][force] option is an
+instant deadline: all allocations are immediately stopped. The
+[`-no-deadline`][no-deadline] option disables the deadline so a drain may
+continue indefinitely.
+
+Like all other drain parameters, a drain's deadline can be updated by making
+subsequent `nomad node drain ...` calls with updated values.
+
+## Plan a drain strategy for batch and system jobs
+
+So far you have only seen how draining works with service jobs. Both batch and
+system jobs are have different behaviors during node drains.
+
+### Drain batch jobs
+
+Node drains only migrate batch jobs once the drain's deadline has been reached.
+For node drains without a deadline the drain will not complete until all batch
+jobs on the node have completed (or failed).
+
+The goal of this behavior is to avoid losing progress a batch job has made by
+forcing it to exit early.
+
+### Keep system jobs running
+
+Node drains only stop system jobs once all other allocations have exited. This
+way if a node is running a log shipping daemon or metrics collector as a system
+job, it will continue to run as long as there are other allocations running.
+
+The [`-ignore-system`][ignore-system] option leaves system jobs running even
+after all other allocations have exited. This is useful when system jobs are
+used to monitor Nomad or the node itself.
+
+## Drain multiple nodes
+
+A common operation is to decommission an entire class of nodes at once. Prior
+to Nomad 0.7 this was a problematic operation as the first node to begin
+draining may migrate all of their allocations to the next node about to be
+drained. In pathological cases this could repeat on each node to be drained and
+cause allocations to be rescheduled repeatedly.
+
+As of Nomad 0.8 an operator can avoid this churn by marking nodes ineligible
+for scheduling before draining them using the [`nomad node eligibility`][eligibility] command.
+
+Mark a node as ineligible for scheduling with the `-disable` flag.
+
+```shell-session
+$ nomad node eligibility -disable 46f1
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+```
+
+```shell-session
+$ nomad node eligibility -disable 96b5
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Check node status to confirm eligibility.
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  eligible     ready
+46f1c6c4  dc1  nomad-2  <none>  false  ineligible   ready
+96b52ad8  dc1  nomad-3  <none>  false  ineligible   ready
+```
+
+Now that both `nomad-2` and `nomad-3` are ineligible for scheduling, they can
+be drained without risking placing allocations on an _about-to-be-drained_
+node.
+
+Toggling scheduling eligibility can be done totally independently of draining.
+For example when an operator wants to inspect the allocations currently running
+on a node without risking new allocations being scheduled and changing the
+node's state.
+
+Make current node ineligible for scheduling.
+
+```shell-session
+$ nomad node eligibility -self -disable
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Make current node eligible for scheduling again with the `-enable` flag.
+
+```shell-session
+$ nomad node eligibility -self -enable
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: eligible for scheduling
+```
+
+### Example: migrating datacenters
+
+A more complete example of draining multiple nodes would be when migrating from
+an old datacenter (`dc1`) to a new datacenter (`dc2`):
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name     Class   Drain  Eligibility  Status  Running Allocs
+f7476465  dc1  nomad-1  <none>  false  eligible     ready   4
+46f1c6c4  dc1  nomad-2  <none>  false  eligible     ready   1
+96b52ad8  dc1  nomad-3  <none>  false  eligible     ready   4
+168bdd03  dc2  nomad-4  <none>  false  eligible     ready   0
+9ccb3306  dc2  nomad-5  <none>  false  eligible     ready   0
+7a7f9a37  dc2  nomad-6  <none>  false  eligible     ready   0
+```
+
+Before migrating ensure that all jobs in `dc1` have `datacenters = ["dc1", "dc2"]`. Then before draining, mark all nodes in `dc1` as ineligible for
+scheduling.
+
+Shell scripting can help automate manipulating multiple nodes at once.
+
+```shell-session
+$ nomad node status | awk '{ print $2 " " $1 }' | grep ^dc1 | awk '{ system("nomad node eligibility -disable "$2) }'
+Node "f7476465-4d6e-c0de-26d0-e383c49be941" scheduling eligibility set: ineligible for scheduling
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Check status to confirm ineligibility.
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  ineligible   ready
+46f1c6c4  dc1  nomad-2  <none>  false  ineligible   ready
+96b52ad8  dc1  nomad-3  <none>  false  ineligible   ready
+168bdd03  dc2  nomad-4  <none>  false  eligible     ready
+9ccb3306  dc2  nomad-5  <none>  false  eligible     ready
+7a7f9a37  dc2  nomad-6  <none>  false  eligible     ready
+```
+
+Then drain each node in `dc1`.
+
+```shell-session
+$ nomad node drain -enable -yes -detach f7476465
+Node "f7476465-4d6e-c0de-26d0-e383c49be941" drain strategy set
+```
+
+Pass the ID for each node with the flags ``-enable -yes -detach` to initiate the drain.
+
+```shell-session
+$ nomad node drain -enable -yes -detach 46f1c6c4
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" drain strategy set
+```
+
+For this example, only monitor the final node that is draining. Watching `nomad node status -allocs`
+is also a good way to monitor the status of drains.
+
+```shell-session
+$ nomad node drain -enable -yes 9ccb3306
+2018-04-12T22:08:00Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-04-12T22:08:00Z: Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" drain strategy set
+2018-04-12T22:08:15Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" marked for migration
+2018-04-12T22:08:16Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" draining
+2018-04-12T22:08:17Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" marked for migration
+2018-04-12T22:08:17Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" draining
+2018-04-12T22:08:21Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" status running -> complete
+2018-04-12T22:08:22Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" status running -> complete
+2018-04-12T22:09:08Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" marked for migration
+2018-04-12T22:09:09Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" draining
+2018-04-12T22:09:14Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" status running -> complete
+2018-04-12T22:09:33Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" marked for migration
+2018-04-12T22:09:33Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" draining
+2018-04-12T22:09:33Z: Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" has marked all allocations for migration
+2018-04-12T22:09:39Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" status running -> complete
+2018-04-12T22:09:39Z: All allocations on node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" have stopped.
+```
+
+Note that there was a 15 second delay between node `96b52ad8` starting to drain
+and having its first allocation migrated. The delay was due to 2 other
+allocations for the same job already being migrated from the other nodes. Once
+at least 8 out of the 9 allocations are running for the job, another allocation
+could begin draining.
+
+The final node drain command did not exit until 6 seconds after the `drain complete` message because the command line tool blocks until all allocations on
+the node have stopped. This allows operators to script shutting down a node
+once a drain command exits and know all services have already exited.
+
+[deadline]: /nomad/commands/node/drain#deadline
+[eligibility]: /nomad/commands/node/eligibility
+[force]: /nomad/commands/node/drain#force
+[ignore-system]: /nomad/commands/node/drain#ignore-system
+[migrate]: /nomad/docs/job-specification/migrate
+[no-deadline]: /nomad/commands/node/drain#no-deadline
diff --git a/content/nomad/v1.10.x/content/docs/manage/outage-recovery.mdx b/content/nomad/v1.10.x/content/docs/manage/outage-recovery.mdx
new file mode 100644
index 0000000000..8f537382b2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/outage-recovery.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: Recover from an outage
+description: |-
+  Discover techniques and steps to recover from a single node failure,
+  multi-node failure, or a complete loss of quorum.
+---
+
+# Recover from an outage
+
+Don't panic. This is a critical first step.
+
+Depending on your [deployment configuration], it may take only a single server
+failure for cluster unavailability. Recovery requires an operator to intervene,
+but the process is straightforward.
+
+~> This guide is for recovery from a Nomad outage due to a majority of server
+nodes in a datacenter being lost. If you are looking to add or remove servers,
+consult the [bootstrapping guide].
+
+## Failure of a single server cluster
+
+If you had only a single server and it has failed, try to restore operation by
+restarting it. A single server configuration requires the
+[`-bootstrap-expect=1`] flag. If the server cannot be recovered, you need to
+bring up a new server. Consult the [bootstrapping guide] for more detail.
+
+In the case of an unrecoverable server failure in a single server cluster, data
+loss is inevitable since data was not replicated to any other servers. This is
+why a single server deploy is **never** recommended.
+
+## Failure of a server in a multi-server cluster
+
+If you think the failed server is recoverable, the easiest option is to bring it
+back online and have it rejoin the cluster with the same IP address. This will
+return the cluster to a fully healthy state. Similarly, even if you need to
+rebuild a new Nomad server to replace the failed node, you may wish to do that
+immediately. Keep in mind that the rebuilt server needs to have the same IP
+address as the failed server. Again, once this server is online and has
+rejoined, the cluster will return to a fully healthy state.
+
+Both of these strategies involve a potentially lengthy time to reboot or rebuild
+a failed server. If this is impractical or if building a new server with the
+same IP isn't an option, you need to remove the failed server. Usually, you can
+issue a [`nomad server force-leave`] command to remove the failed server if it
+is still a member of the cluster.
+
+<Note>
+
+ Your raft cluster will need to have a quorum of nodes available to
+perform any online modifications to the Raft peer information. Membership
+changes are written to the Raft log, and all Raft log writes require quorum.
+If this is impossible, continue to **Failure of Multiple Servers in a
+Multi-Server Cluster**
+
+</Note>
+
+If, for some reason, the Raft configuration continues to show any stale members,
+you can use the [`nomad operator raft remove-peer`] command to remove the stale
+peer server on the fly with no downtime.
+
+Once you have made the membership changes necessary, you should verify the
+current Raft state with the [`nomad operator raft list-peers`] command:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+## Failure of multiple servers in a multi-server cluster
+
+In the event that multiple servers are lost, causing a loss of quorum and a
+complete outage, partial recovery is possible using data on the remaining
+servers in the cluster. There may be data loss in this situation because
+multiple servers were lost, so information about what's committed could be
+incomplete. The recovery process implicitly commits all outstanding Raft log
+entries, so it's also possible to commit data that was uncommitted before the
+failure.
+
+The [section below][] contains the details of the recovery procedure. You will
+include the remaining servers in the `raft/peers.json` recovery file. The
+cluster should be able to elect a leader once the remaining servers are all
+restarted with an identical `raft/peers.json` configuration.
+
+Any new servers you introduce later can be fresh with totally clean data
+directories and joined using Nomad's `server join` command.
+
+In extreme cases, it should be possible to recover with only a single remaining
+server by starting that single server with itself as the only peer in the
+`raft/peers.json` recovery file.
+
+The `raft/peers.json` recovery file is final, and a snapshot is taken after it
+is ingested, so you are guaranteed to start with your recovered configuration.
+This does implicitly commit all Raft log entries, so should only be used to
+recover from an outage, but it should allow recovery from any situation where
+there's some cluster data available.
+
+## Manual recovery using peers.json
+
+To begin, stop all remaining servers. You can attempt a graceful leave, but it
+will not work in most cases. Do not worry if the leave exits with an error. The
+cluster is in an unhealthy state, so this is expected.
+
+The `peers.json` file is not present by default and is only used when performing
+recovery. This file will be deleted after Nomad starts and ingests this file.
+
+Nomad automatically creates a `raft/peers.info` file on startup to mark that it
+is on the current version of Raft. Do not remove the `raft/peers.info`
+file at any time.
+
+Using `raft/peers.json` for recovery can cause uncommitted Raft log entries to
+be implicitly committed, so this should only be used after an outage where no
+other option is available to recover a lost server. Make sure you don't have any
+automated processes that will put the peers file in place on a periodic basis.
+
+The next step is to go to the [`-data-dir`][] of each Nomad server. Inside that
+directory, there will be a `raft/` sub-directory. Create a `raft/peers.json`
+file. Its contents will depend on the raft protocol version of your cluster.
+
+### Raft protocol 3 peers.json specification
+
+```json
+[
+  {
+    "id": "adf4238a-882b-9ddc-4a9d-5b6758e4159e",
+    "address": "10.1.0.1:4647",
+    "non_voter": false
+  },
+  {
+    "id": "8b6dda82-3103-11e7-93ae-92361f002671",
+    "address": "10.1.0.2:4647",
+    "non_voter": false
+  },
+  {
+    "id": "97e17742-3103-11e7-93ae-92361f002671",
+    "address": "10.1.0.3:4647",
+    "non_voter": false
+  }
+]
+```
+
+- `id` `(string: **required**)` - Specifies the `node ID` of the server. This
+  can be found in the logs when the server starts up, and it can also be found
+  inside the `node-id` file in the server's data directory.
+
+- `address` `(string: **required**)` - Specifies the IP and port of the server
+  in `ip:port` format. The port is the server's RPC port used for cluster
+  communications, typically 4647.
+
+- `non_voter` `(bool: _false_)` - This controls whether the server is a
+  non-voter, which is used in some advanced [Autopilot] configurations. If
+  omitted, it will default to false, which is typical for most clusters.
+
+You can use this `jq` filter to create a `peers.json` file with the list of `alive` servers. Check the generated output and make any necessary changes.
+
+```shell
+$ nomad server members -json | jq '[ .[] | select(.Status == "alive") | {id: .Tags.id, address: "\(.Tags.rpc_addr):\(.Tags.port)", non_voter: false} ]'
+```
+
+### Raft protocol 2 peers.json specification
+
+```json
+["10.0.1.8:4647", "10.0.1.6:4647", "10.0.1.7:4647"]
+```
+
+Raft protocol version 2 peers.json files contain a list of IP:Port addresses for
+each server. Note that the port should refer to the RPC port and not the HTTP
+API port.
+
+### Deploy peers.json to all server nodes
+
+Create entries for all remaining servers. You must confirm that servers you do
+not include here have indeed failed and will not later rejoin the cluster.
+
+Deploy this file is the same across all remaining server nodes.
+
+### Verify keyring on server nodes
+
+<Warning>
+
+Prior to Nomad 1.9.0, [key material][Key material] was never stored in Raft. This meant that
+the `nomad agent snapshot save` command and snapshot agent did not save Nomad's
+keyring. If you are using versions prior to Nomad 1.9.0, you should make sure you have backed up the keyring of at least one
+server.
+
+</Warning>
+
+Go to the [`-data-dir`][] of each Nomad server. Inside that directory, there
+will be a `keystore/` sub-directory with `.nks.json` files. Ensure that these
+files exist on at least one server before continuing.
+
+### Restart cluster nodes
+
+At this point, you can restart all the remaining servers. Log lines will be
+emitted as the servers ingest the recovery file:
+
+```plaintext
+...
+2016/08/16 14:39:20 [INFO] nomad: found peers.json file, recovering Raft configuration...
+2016/08/16 14:39:20 [INFO] nomad.fsm: snapshot created in 12.484µs
+2016/08/16 14:39:20 [INFO] snapshot: Creating new snapshot at /tmp/peers/raft/snapshots/2-5-1471383560779.tmp
+2016/08/16 14:39:20 [INFO] nomad: deleted peers.json file after successful recovery
+2016/08/16 14:39:20 [INFO] raft: Restored from snapshot 2-5-1471383560779
+2016/08/16 14:39:20 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:10.212.15.121:4647 Address:10.212.15.121:4647}]
+...
+```
+
+If any servers managed to perform a graceful leave, you may need to have them
+rejoin the cluster using the [`server join`] command:
+
+```shell-session
+$ nomad server join <Node Address>
+Successfully joined cluster by contacting 1 nodes.
+```
+
+It should be noted that any existing member can be used to rejoin the cluster as
+the gossip protocol will take care of discovering the server nodes.
+
+At this point, the cluster should be in an operable state again. One of the
+nodes should claim leadership and emit a log like:
+
+```plaintext
+[INFO] nomad: cluster leadership acquired
+```
+
+You can use the [`nomad operator raft list-peers`] command to inspect the Raft
+configuration:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+[`-bootstrap-expect=1`]: /nomad/docs/configuration/server#bootstrap_expect
+[`-data-dir`]: /nomad/docs/configuration#data_dir
+[`nomad operator raft list-peers`]: /nomad/commands/operator/raft/list-peers
+[`nomad operator raft remove-peer`]: /nomad/commands/operator/raft/remove-peer
+[`nomad server force-leave`]: /nomad/commands/server/force-leave
+[`nomad server force-leave`]: /nomad/commands/server/force-leave
+[`server join`]: /nomad/commands/server/join
+[autopilot]: /nomad/docs/manage/autopilot
+[bootstrapping guide]: /nomad/docs/deploy/clusters/connect-nodes
+[deployment configuration]: /nomad/docs/architecture/cluster/consensus#deployment_table
+[section below]: #manual-recovery-using-peers-json
+[Key material]: /nomad/docs/manage/key-management
+[restore the keyring]: /nomad/docs/manage/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.10.x/content/docs/manage/variables.mdx b/content/nomad/v1.10.x/content/docs/manage/variables.mdx
new file mode 100644
index 0000000000..a77ea2aab7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/manage/variables.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Create and update Nomad variables
+description: |-
+  Use the Nomad CLI or API to create, store, and update Nomad variables.
+---
+
+# Create and update Nomad variables
+
+This page describes the processes for interacting with Nomad variables. Use the
+[`nomad var` command reference](/nomad/commands/var) or the [Vars HTTP
+API](/nomad/api-docs/variables) to manage Nomad variables.
+
+## Background
+
+Nomad variables provide the option to securely store configuration at
+file-like paths directly in Nomad's state store. For complete documentation on
+the Nomad variables feature and related concepts, refer to the following:
+
+- [Nomad variables concepts](/nomad/docs/concepts/variables)
+- [Nomad variable specification](/nomad/docs/other-specifications/variables)
+- [Key management](/nomad/docs/manage/key-management)
+- [Workload identity](/nomad/docs/concepts/workload-identity)
+
+Nomad scopes a Nomad variable to a namespace and allows access to Nomad
+variables according to ACL policies.
+
+## Generate a Nomad variable specification
+
+Use the [`nomad var init` command](/nomad/commands/var/init) to generate a Nomad
+variable specification that you can customize.
+
+@include 'variables/init-example.mdx'
+
+## Add and update Nomad variables
+
+Use the [`nomad var put` command](/nomad/commands/var/put) to create and update
+Nomad variables. Supply variable items by including a Nomad variable
+specification file, a series of key-value pairs, or both. Refer to the [`nomad
+var put` command reference](/nomad/commands/var/put) for details on formatting
+keys and values. Values that you supply as command line arguments supersede
+values provided in any variable specification piped into the command or loaded
+from file.
+
+You may also use  the `nomad var put` command to overwrite all items in a
+variable. To avoid conflicting with other writes that may have happened since
+you last read the variable, you must use the `-check-index` flag and set it to
+the last modified index.
+
+@include 'variables/put-example.mdx'
+
+## Delete Nomad variables
+
+Use the [`nomad var purge` command](/nomad/commands/var/purge) to permanently
+delete an existing variable.
+
+@include 'variables/purge-example.mdx'
+
+## Query Nomad variables
+
+### Get
+
+Use the [`nomad var get` command](/nomad/commands/var/get) to fetch the contents of an existing variable.
+
+@include 'variables/get-example.mdx'
+
+### List
+
+Use the [`nomad var list` command](/nomad/commands/var/list) to fetch a list of
+variable paths accessible to you.
+
+@include 'variables/list-example.mdx'
+
+## Lock access to a Nomad variable
+
+The [`nomad var lock` command](/nomad/commands/var/lock) provides a mechanism
+for distributed locking. Nomad creates a lock in the given variable, and only
+when held, invokes the specified child process.
+
+@include 'variables/lock-example.mdx'
+
+## Next steps
+
+Refer to the following Nomad variables tutorials for in-depth learning:
+
+- [Create and update Nomad
+  variables](/nomad/tutorials/variables/variables-create) contains advanced
+  examples for updating Nomad variables.
+- [Configure access control for Nomad
+  variables](/nomad/tutorials/variables/variables-acls) shows how to configure
+  ACL policies for Nomad variables.
+
+To learn how to access Nomad variables in your job specification, refer to [Use Nomad variables in tasks](/nomad/docs/job-declare/nomad-variables).
diff --git a/content/nomad/v1.10.x/content/docs/monitor/cluster-topology.mdx b/content/nomad/v1.10.x/content/docs/monitor/cluster-topology.mdx
new file mode 100644
index 0000000000..4aedceea06
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/monitor/cluster-topology.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Cluster state topology
+description: |-
+  Discover and use the topology visualization of the Nomad web UI to observe
+  clients and active workloads on your cluster.
+---
+
+# Cluster state topology
+
+As a Nomad cluster grows, the exact state of allocations and clients can become a mystery. For the most part this is a good thing: it means Nomad is quietly scheduling workloads without any need for intervention. However, as an operator, it is reasonable to still want to know what is going on within your cluster.
+
+The topology visualization is a single view of an entire cluster. It helps you perform preventative maintenance and it can help you understand your cluster's particular behaviors.
+
+## Prerequisites
+
+This tutorial assumes basic familiarity with Nomad. You must have access to an existing cluster that is running one or more jobs.
+
+Here is what you will need for this guide:
+
+- An active Nomad >=1.0.0 cluster
+- Access to the cluster's web UI
+- Read permissions to one or more namespaces
+
+## Navigate to the topology visualization
+
+The global left-hand navigation of the web UI has a Topology link under the cluster section. This link will take you to the topology visualization.
+
+[![The left-hand Nomad UI navigation with the topology link highlighted][topo-viz-link]][topo-viz-link]
+
+## The elements of the visualization
+
+The left-hand information panel contains aggregate cluster statistics. This includes the sum total of memory and CPU (in MHz) available to Nomad. The percentages of memory and CPU tell how much of each resource has been reserved—not how much is currently utilized. For instance, if a Docker container is currently utilizing 30MiB of memory but the task declared the need for 500MiB in the job spec, then the topology visualization will count this allocation as 500MiB.
+
+These aggregate metrics are meant to give a rough sense of scale and can answer immediate forecasting questions. If your cluster is currently at 80% capacity of a total 200GiB of memory and you know your services will only grow in the next year, then you can conclude that the capacity of the cluster will also have to grow.
+
+Be careful not to assume there is room for your allocation just because the aggregate remaining resources are less than what your job requires. Since resources are aggregated but allocations must be placed on a single client, it's possible that no client has room for your allocation. If there is 1500MHz of CPU available across a cluster but only 500MHz available per client, then a task that needs 600MHz of CPU cannot be placed.
+
+[![The info panel of the topology visualization with aggregate cluster statistics included][cluster-panel]][cluster-panel]
+
+The main visualization organizes all of your datacenters and clients and brings focus to your allocations.
+
+The outermost section represents a datacenter (1). Each section is labeled by the datacenter name, capacity, and status. Clients are rendered within their respective datacenter. Clients will also be labeled by their name, capacity, and status (2). This also includes icon indicators of scheduling eligibility and drain state (3).
+
+[![The primary cluster view of the topology visualization. Annotation 1: the datacenter section. Annotation 2: the client name and details. Annotation 3: a lock icon indicator for scheduling ineligibility. Annotation 4: two rows of rectangles representing allocations.][cluster-view]][cluster-view]
+
+Clients across your entire fleet are sized vertically based on their capacity. Clients with more total capacity are taller. This makes scanning a cluster easier.
+
+Within each client container are two rows; one for each primary scheduling unit (CPU and memory). Each row will include each allocation on the client scaled proportionally to the amount of resources reserved for it (4). An allocation for a task group that requires 8GiB of memory on a client that has 32GiB total will occupy 25% of a client row.
+
+## Interact with the visualization
+
+The topology visualization is designed to presennt as much information as possible in a single view. More information can be expanded by hovering or clicking on specific elements.
+
+Hovering over allocations will open a tooltip that gives quick details including the specific allocation reservation requirements and the job the allocation belongs to.
+
+[![The allocation tooltip showing allocation information for the allocation under the cursor][allocation-tooltip]][allocation-tooltip]
+
+Clicking an allocation will select it and swap out the cluster aggregate statistics in the information panel with allocation information. This includes links to the allocation, the job the allocation belongs to, the client the allocation is running on, and the current resource utilization over time.
+
+[![The info panel of the topology visualization with allocation information included][alloc-info-panel]][alloc-info-panel]
+
+In addition to the information shown in the panel, when an allocation is selected, associations among all allocations for the same task group and job will be drawn. This helps convey the distribution of a single task group across a cluster.
+
+[![Lines drawn between allocations to show that they all belong to the same job and task group][alloc-associations]][alloc-associations]
+
+For large clusters, the topology visualization will hide the client labels. When this is the case, clicking a client will expand client details in the information panel.
+
+[![The info panel of the topology visualization with client information included][client-panel]][client-panel]
+
+## Effective use of the topology visualization
+
+The topology visualization is intended to be an open-ended exploration tool. Here are a few example explorations that the visualization is particularly well-suited for.
+
+### Identify excessive client provisioning
+
+Sometimes clients are provisioned separately from application sizing and placement. This can lead to a drift between the expected client requirements and the actual requirements. Clients with no allocations still cost money.
+
+This can be quickly detected with the topology visualization. Empty clients are highlighted in red and labeled as empty.
+
+[![An empty client in the cluster view emphasized in red][empty-clients]][empty-clients]
+
+~> Is this a problem you have? Consider using [horizontal cluster autoscaling](https://github.com/hashicorp/nomad-autoscaler).
+
+### Spot potentially hazardous or flaky allocation distributions
+
+Nomad will automatically place allocations based on the requirements and constraints declared in the job spec. It is not uncommon for jobs to have missing constraints due to human error or unknown caveats. This class of error will often make itself known when the task starts, but sometimes the error is invisible and only surfaces through a peculiar error rate.
+
+For instance, imagine a service Service A that has five allocations. Four are in datacenter West and one is in datacenter East. Service A must talk to Service B, but due to networking rules, they cannot communicate across the datacenter boundary. If Service B is in datacenter West, then 80% of Service A traffic (assuming a uniform distribution) will work as intended while the remaining 20% will error. Or worse than error: silently behave incorrectly.
+
+This is easily remedied with a datacenter constraint in the job spec, but the problem must first be identified. Since the topology visualization will associate all allocations for Service A, this can be quickly spotted.
+
+[![Allocations associated across datacenters][alloc-associations-across-dcs]][alloc-associations-across-dcs]
+
+### Find noisy neighbor risks
+
+By default, tasks in Nomad have soft CPU limits. This lets tasks occasionally spike over their allotted CPU while still allowing for efficient bin-packing of allocations on a single client.
+
+It is possible for many allocations on a single client to exceed their CPU soft-limit—or for one allocation to greatly exceed it—starving other allocations of CPU. This can cause degraded performance and anomalous errors to arise from untested race conditions or timeouts. In this case, the problematic allocation is only problematic due to the external circumstances of the client it was scheduled on.
+
+The topology visualization makes it very clear when an important allocation is scheduled alongside many other allocations on a densely packed client. This alone doesn't mean there is a noisy neighbor problem, but it might be enough to defensively modify the job spec. Adding more CPU headroom or constraints can help stabilize the service.
+
+[![A single client in the topology visualization with many allocations][client-with-many-allocs]][client-with-many-allocs]
+
+## Next steps
+
+The topology visualization is a useful tool for learning to use Nomad and for understanding your cluster at a moment in time. It does _not_ show historical allocation reservation information.
+
+To get deeper utilization and historical data, you will need to set up a monitoring stack using Nomad's telemetry data. The topology visualization may inform your own custom dashboards as you invest in setting up operations tooling for your specific needs.
+
+1. [Use Prometheus to monitor Nomad metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+2. [Review the full set of metrics Nomad exports](/nomad/docs/reference/metrics)
+
+[topo-viz-link]: /img/monitor/topo-viz/topo-viz-link.png
+[cluster-panel]: /img/monitor/topo-viz/cluster-panel.png
+[cluster-view]: /img/monitor/topo-viz/cluster-view.png
+[allocation-tooltip]: /img/monitor/topo-viz/allocation-tooltip.png
+[alloc-info-panel]: /img/monitor/topo-viz/allocation-panel.png
+[alloc-associations]: /img/monitor/topo-viz/allocation-associations.png
+[client-panel]: /img/monitor/topo-viz/client-panel.png
+[empty-clients]: /img/monitor/topo-viz/empty-clients.png
+[alloc-associations-across-dcs]: /img/monitor/topo-viz/alloc-associations-across-dcs.png
+[client-with-many-allocs]: /img/monitor/topo-viz/client-with-many-allocs.png
diff --git a/content/nomad/v1.10.x/content/docs/monitor/event-stream.mdx b/content/nomad/v1.10.x/content/docs/monitor/event-stream.mdx
new file mode 100644
index 0000000000..28933c3877
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/monitor/event-stream.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Monitor Nomad's event stream
+description: |-
+  Subscribe to Nomad's event stream to observe activities in your Nomad cluster.
+---
+
+# Monitor Nomad's event stream
+
+The event stream provides a way to subscribe to Job, Allocation, Evaluation,
+Deployment, and Node changes in near real time. Whenever a state change occurs in
+Nomad via Nomad's Finite State Machine (FSM) a set of events for each updated
+object are created.
+
+Currently, Nomad users must take a number of steps to build a mental model of
+what recent actions have occurred in their cluster. Individual log statements
+often provide a small fragment of information related to a unit of work within
+Nomad. Logs can also be interlaced with other unrelated logs, complicating the
+process of understanding and building context around the issue a user is trying
+to identify. Log statements may also be too specific to a smaller piece of work
+that took place and the larger context around the log or action is missed or
+hard to infer.
+
+Another pain point is that the value of log statements depend on how they are
+managed by an organization. Larger teams with external log aggregators find
+more value out of standard logging than a smaller team who manually scans
+through files to debug issues. Today, an operator might combine the information
+returned by `/v1/nodes`, `/v1/evaluations`, `/v1/allocations`, and then
+`/v1/nodes` again using the Nomad API to try to figure out what exactly
+happened.
+
+This complex workflow has led to a lack of prescriptive guidance when working
+with customers and users on how to best monitor and debug their Nomad clusters.
+Third party tools such as `nomad-firehose` have also emerged to try to solve
+the issue by continuously scraping endpoints to react to changes within Nomad.
+
+The event stream provides a first-class solution to receiving a stream of events
+in Nomad and provides users a much better understanding of how their cluster is
+operating out of the box.
+
+## Access the event stream
+
+The event stream currently exists in the API, so users can access the new event
+stream endpoint from the below command.
+
+```shell-session
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+## Subscribe to all or certain events
+
+Filter on certain topics by specifying a filter key. This example listens
+for Node events only relating to that particular node's ID. It also listens
+to all Deployment events and Job events related to a job named web.
+
+```shell-session
+$ curl -s -v -N \
+  --data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+  --data-urlencode "topic=Deployment" \
+  --data-urlencode "topic=Job:web" \
+  http://127.0.0.1:4646/v1/event/stream
+```
+
+## What is in an event?
+
+Each event contains a `Topic`, `Type`, `Key`, `Namespace`, `FilterKeys`, `Index`,
+and `Payload`. The contents of the Payload depend on the event Topic. An event
+for the Node Topic contains a Node object. For example:
+
+```json
+{
+  "Topic": "Node",
+  "Type": "NodeRegistration",
+  "Key": "afb9c810-d701-875a-b2a6-f2631d7c2f60",
+  "Namespace": "",
+  "FilterKeys": null,
+  "Index": 7,
+  "Payload": {
+    "Node": {
+      "//": "...entire node object"
+    }
+  }
+}
+```
+
+## Develop using event stream
+
+Here are some patterns of how you might use Nomad's event stream.
+
+- Subscribe to all or subset of cluster events
+
+- Add an additional tool in your regular debugging & monitoring workflow as an
+  SRE to gauge the qualitative state and health of your cluster.
+
+- Trace through a specific job deployment as it upgrades from an evaluation to a
+  deployment and uncover any blockers in the path for the scheduler.
+
+- Build a slack bot integration to send deploy notifications.
+  - https://github.com/drewbailey/nomad-deploy-notifier
diff --git a/content/nomad/v1.10.x/content/docs/monitor/index.mdx b/content/nomad/v1.10.x/content/docs/monitor/index.mdx
new file mode 100644
index 0000000000..5e2352103f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/monitor/index.mdx
@@ -0,0 +1,313 @@
+---
+layout: docs
+page_title: Monitor Nomad
+description: |-
+  Learn how to monitor the health and performance of Nomad clusters. Export data to Prometheus or DataDog. Review metrics for the Raft consensus protocol, scheduling, performance, capacity, task resource consumption, job and task status, runtime, and federated deployments.
+---
+
+# Monitor Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+## Key performance indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+## Raft consensus protocol
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://developer.hashicorp.com/nomad/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task resource consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and task status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Serf federated deployments
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/reference/metrics#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus-apica
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/docs/manage/migrate-workloads
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/reference/metrics#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/reference/metrics#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/monitor#raft-consensus-protocol
+[Job Summary Metrics]: /nomad/docs/reference/metrics#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
diff --git a/content/nomad/v1.10.x/content/docs/monitor/inspect-cluster.mdx b/content/nomad/v1.10.x/content/docs/monitor/inspect-cluster.mdx
new file mode 100644
index 0000000000..3b45c08159
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/monitor/inspect-cluster.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Inspect the cluster
+description: |-
+  View the server and client nodes, inspect an individual server or client node,
+  list allocations, and review client events from the Nomad web UI.
+---
+
+# Inspect the cluster
+
+The Web UI can be a powerful tool for monitoring the state of the Nomad cluster
+from an operator's perspective. This includes showing all client nodes, showing
+driver health for client nodes, driver status, resource utilization, allocations
+by client node, and more.
+
+## View cluster clients
+
+From any page, the Clients List page can be accessed from the left-hand
+navigation bar. On narrow screens this navigation bar may need to be opened from
+the top-right menu button. The table lists every client in the cluster and is
+searchable, sortable, and filterable. Each client row in the table shows basic
+information, such as the Node ID, name, state, address, datacenter, and how many
+allocations are running in it.
+
+This view will also live-update as the states of client nodes change.
+
+[![Clients List][img-clients-list]][img-clients-list]
+
+## Filter the client view
+
+If your Nomad cluster has many client nodes, it can be useful to filter the list
+of all client nodes down to only those matching certain facets. The Web UI has
+three facets you can filter by:
+
+1. **Class:** The node of the client, including a dynamically generated list
+   based on the node class of each client node in the cluster.
+
+1. **State:** The state of the cluster, including Initializing, Ready, Down,
+   Ineligible, and Draining.
+
+1. **Datacenter:** The datacenter the client node is in, including a dynamically
+   generated list based on all the datacenters in the cluster.
+
+[![Clients filters][img-clients-filters]][img-clients-filters]
+
+## Inspect an individual client
+
+From the Clients List page, clicking a client node in the table will direct you
+to the Client Detail page for the client node. This page includes all
+information about the client node is live-updated to always present up-to-date
+information.
+
+[![Client Detail][img-client-detail]][img-client-detail]
+
+## Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for client
+nodes. The Web UI uses these metrics to create time-series graphics for the
+current session.
+
+When viewing a client node, resource utilization will automatically start
+logging.
+
+[![Client Resource Utilization][img-client-resource-utilization]][img-client-resource-utilization]
+
+## List client allocations
+
+Allocations belong to jobs and are placed on client nodes. The Client Detail
+page will list all allocations for a client node, including completed, failed,
+and lost allocations, until they are garbage-collected.
+
+This is presented in a searchable table which can additionally be filtered to
+only preempted allocations.
+
+[![Client Allocations][img-client-allocations]][img-client-allocations]
+
+## Review client events
+
+Client nodes will also emit events on meaningful state changes, such as when the
+node becomes ready for scheduling or when a driver becomes unhealthy.
+
+[![Client Events][img-client-events]][img-client-events]
+
+## Check client driver status
+
+Task drivers are additional services running on a client node. Nomad will
+fingerprint and communicate with the task driver to determine if the driver is
+available and healthy. This information is reported through the Web UI on the
+Client Detail page.
+
+[![Client Driver Status][img-client-driver-status]][img-client-driver-status]
+
+## View client attributes
+
+In order to allow job authors to constrain the placement of their jobs, Nomad
+fingerprints the hardware of the node the client agent is running on. This is a
+deeply nested document of properties that the Web UI presents in a scannable
+way.
+
+In addition to the hardware attributes, Nomad operators can annotate a client
+node with [metadata] as part of the client configuration. This metadata is also
+presented on the Client Detail page.
+
+[![Client Attributes][img-client-attributes]][img-client-attributes]
+
+## Monitor a node drain
+
+A routine part of maintaining a Nomad cluster is draining nodes of allocations.
+This can be in preparation of performing operating system upgrades or
+decommissioning an old node in favor of a new VM.
+
+Drains are [performed from the CLI], but the status of a drain can be monitored
+from the Web UI. A client node will state if it is actively draining or
+ineligible for scheduling.
+
+Since drains can be configured in a variety of ways, the Client Detail page will
+also present the details of how the drain is performed.
+
+[![Client Drain][img-client-drain]][img-client-drain]
+
+## View cluster servers
+
+Whereas client nodes are used to run your jobs, server nodes are used to run
+Nomad and maintain availability. From any page, the Servers List page can be
+accessed from the left-hand navigation bar.
+
+The table lists every server node in your cluster. This will be a small list—
+[typically three or five].
+
+[![Servers List][img-servers-list]][img-servers-list]
+
+## Inspect an individual server
+
+Clicking a server node on the Servers List will expand the tags table for the
+server node.
+
+[![Server Detail][img-server-detail]][img-server-detail]
+
+## Secure the UI
+
+Depending on the size of your team and the details of you Nomad deployment, you
+may wish to control which features different internal users have access to. This
+includes limiting who has access to list and manage client nodes and list and
+manage server nodes. You can enforce this with Nomad's access control list
+system.
+
+By default, all features—read and write—are available to all users of the Web
+UI. Check out the [Securing the Web UI with ACLs] tutorial to learn how to prevent
+anonymous users from having write permissions as well as how to continue to use
+Web UI write features as a privileged user.
+
+## Continue your exploration
+
+Now that you have explored how to inspect the state of your cluster through the
+Nomad UI, you will next learn some considerations you should keep in mind when
+using the Nomad UI.
+
+[img-client-allocations]: /img/monitor/guide-ui-img-client-allocations.png
+[img-client-attributes]: /img/monitor/guide-ui-img-client-attributes.png
+[img-client-detail]: /img/monitor/guide-ui-img-client-detail.png
+[img-client-drain]: /img/monitor/guide-ui-img-client-drain.png
+[img-client-driver-status]: /img/monitor/guide-ui-img-client-driver-status.png
+[img-client-events]: /img/monitor/guide-ui-img-client-events.png
+[img-client-resource-utilization]: /img/monitor/guide-ui-img-client-resource-utilization.png
+[img-clients-filters]: /img/monitor/guide-ui-img-clients-filters.png
+[img-clients-list]: /img/monitor/guide-ui-img-clients-list.png
+[img-server-detail]: /img/monitor/guide-ui-img-server-detail.png
+[img-servers-list]: /img/monitor/guide-ui-img-servers-list.png
+[metadata]: /nomad/docs/configuration/client#meta
+[performed from the cli]: /nomad/docs/manage/migrate-workloads
+[securing the web ui with acls]: /nomad/docs/secure/acl
+[typically three or five]: /nomad/docs/architecture/cluster/consensus#deployment-table
diff --git a/content/nomad/v1.10.x/content/docs/monitor/inspect-workloads.mdx b/content/nomad/v1.10.x/content/docs/monitor/inspect-workloads.mdx
new file mode 100644
index 0000000000..7f1388e318
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/monitor/inspect-workloads.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Inspect job workloads
+description: |-
+  Inspect jobs, allocations, and tasks in the Nomad web UI and interact
+  with these objects to perform operations like restart an allocation or
+  stop a job.
+---
+
+# Inspect job workloads
+
+The Web UI can be a powerful companion when monitoring and debugging jobs
+running in Nomad. The Web UI will list all jobs, link jobs to allocations,
+allocations to client nodes, client nodes to driver health, and much more.
+
+## List jobs
+
+The first page you will arrive at in the Web UI is the Jobs List page. Here you
+will find every job for a namespace in a region. The table of jobs is
+searchable, sortable, and filterable. Each job row in the table shows basic
+information, such as job name, status, type, and priority, as well as richer
+information such as a visual representation of all allocation statuses.
+
+This view will also live-update as jobs get submitted, get purged, and change
+status.
+
+[![Jobs List][img-jobs-list]][img-jobs-list]
+
+## Filter job view
+
+If your Nomad cluster has many jobs, it can be useful to filter the list of all
+jobs down to only those matching certain facets. The Web UI has four facets you
+can filter by:
+
+1. **Type:** The type of job, including Batch, Parameterized, Periodic, Service,
+   and System.
+
+1. **Status:** The status of the job, including Pending, Running, and Dead.
+
+1. **Datacenter:** The datacenter the job is running in, including a dynamically
+   generated list based on the jobs in the namespace.
+
+1. **Prefix:** The possible common naming prefix for a job, including a
+   dynamically generated list based on job names up to the first occurrence of
+   `-`, `.`, and `_`. Only prefixes that match multiple jobs are included.
+
+[![Job Filters][img-job-filters]][img-job-filters]
+
+## Inspect an allocation
+
+In Nomad, allocations are the schedulable units of work. This is where runtime
+metrics begin to surface. An allocation is composed of one or more tasks, and
+the utilization metrics for tasks are aggregated so they can be observed at the
+allocation level.
+
+### Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for tasks
+and allocations. The Web UI uses these metrics to create time-series graphs for
+the current session.
+
+When viewing an allocation, resource utilization will automatically start
+logging.
+
+[![Allocation Resource Utilization][img-alloc-resource-utilization]][img-alloc-resource-utilization]
+
+### Review task events
+
+When Nomad places, prepares, and starts a task, a series of task events are
+emitted to help debug issues in the event that the task fails to start.
+
+Task events are listed on the Task Detail page and live-update as Nomad handles
+managing the task.
+
+[![Task Events][img-task-events]][img-task-events]
+
+### View rescheduled allocations
+
+Allocations will be placed on any client node that satisfies the constraints of
+the job definition. There are events, however, that will cause Nomad to
+reschedule allocations, (e.g., node failures).
+
+Allocations can be configured [in the job definition to reschedule] to a
+different client node if the allocation ends in a failed status. This will
+happen after the task has exhausted its [local restart attempts].
+
+The end result of this automatic procedure is a failed allocation and that
+failed allocation's rescheduled successor. Since Nomad handles all of this
+automatically, the Web UI makes sure to explain the state of allocations through
+icons and linking previous and next allocations in a reschedule chain.
+
+[![Allocation Reschedule Icon][img-alloc-reschedule-icon]][img-alloc-reschedule-icon]
+
+[![Allocation Reschedule Details][img-alloc-reschedule-details]][img-alloc-reschedule-details]
+
+### Unhealthy driver
+
+Given the nature of long-lived processes, it's possible for the state of the
+client node an allocation is scheduled on to change during the lifespan of the
+allocation. Nomad attempts to monitor pertinent conditions including driver
+health.
+
+The Web UI denotes when a driver an allocation depends on is unhealthy on the
+client node the allocation is running on.
+
+[![Allocation Unhealthy Driver][img-alloc-unhealthy-driver]][img-alloc-unhealthy-driver]
+
+### Preempted allocations
+
+Much like how Nomad will automatically reschedule allocations, Nomad will
+automatically preempt allocations when necessary. When monitoring allocations in
+Nomad, it's useful to know what allocations were preempted and what job caused
+the preemption.
+
+The Web UI makes sure to tell this full story by showing which allocation caused
+an allocation to be preempted as well as the opposite: what allocations an
+allocation preempted. This makes it possible to traverse down from a job to a
+preempted allocation, to the allocation that caused the preemption, to the job
+that the preempting allocation is for.
+
+[![Allocation Preempter][img-alloc-preempter]][img-alloc-preempter]
+
+[![Allocation Preempted][img-alloc-preempted]][img-alloc-preempted]
+
+## Review task logs
+
+A task will typically emit log information to `stdout` and `stderr`. Nomad
+captures these logs and exposes them through an API. The Web UI uses these APIs
+to offer `head`, `tail`, and streaming logs from the browser.
+
+The Web UI will first attempt to directly connect to the client node the task is
+running on. Typically, client nodes are not accessible from the public internet.
+If this is the case, the Web UI will fall back and proxy to the client node from
+the server node with no loss of functionality.
+
+[![Task Logs][img-task-logs]][img-task-logs]
+
+~> Not all browsers support streaming HTTP requests. In the event that streaming
+is not supported, logs will still be followed using interval polling.
+
+## Restart or stop an allocation or task
+
+Nomad allows for restarting and stopping individual allocations and tasks. When
+a task is restarted, Nomad will perform a local restart of the task. When an
+allocation is stopped, Nomad will mark the allocation as complete and perform a
+reschedule onto a different client node.
+
+Both of these features are also available in the Web UI.
+
+[![Allocation Stop and Restart][img-alloc-stop-restart]][img-alloc-stop-restart]
+
+## Force a periodic instance
+
+Periodic jobs are configured like a cron job. Sometimes, you might want to start
+the job before the its next scheduled run time. Nomad calls this a [periodic
+force] and it can be done from the Web UI on the Job Overview page for a
+periodic job.
+
+[![Periodic Force][img-periodic-force]][img-periodic-force]
+
+## Submit a new version of a job
+
+From the Job Definition page, a job can be edited. After clicking the Edit
+button in the top-right corner of the code window, the job definition JSON
+becomes editable. The edits can then be planned and scheduled.
+
+[![Job Definition Edit][img-job-definition-edit]][img-job-definition-edit]
+
+~> Since each job within a namespace must have a unique name, it is possible to
+submit a new version of a job from the Run Job screen. Always review the plan
+output.
+
+## Monitor a deployment
+
+When a system or service job includes the [`update` stanza], a deployment is
+created upon job submission. Job deployments can be monitored in realtime from
+the Web UI.
+
+The Web UI will show as new allocations become placed, tallying towards the
+expected total, and tally allocations as they become healthy or unhealthy.
+
+Optionally, a job may use canary deployments to allow for additional health
+checks or manual testing before a full roll out. If a job uses canaries and is
+not configured to automatically promote the canary, the canary promotion
+operation can be done from the Job Overview page in the Web UI.
+
+[![Job Deployment with Canary Promotion][img-job-deployment-canary]][img-job-deployment-canary]
+
+## Stop a job
+
+Jobs can be stopped from the Job Overview page. Stopping a job will gracefully
+stop all allocations, marking them as complete, and freeing up resources in the
+cluster.
+
+[![Job Stop][img-job-stop]][img-job-stop]
+
+## Continue your exploration
+
+Now that you have explored operations that can be performed with jobs through
+the Nomad UI, learn how to inspect the state of your cluster using the Nomad UI.
+
+[`update` stanza]: /nomad/docs/job-specification/update
+[img-alloc-preempted]: /img/monitor/guide-ui-img-alloc-preempted.png
+[img-alloc-preempter]: /img/monitor/guide-ui-img-alloc-preempter.png
+[img-alloc-reschedule-details]: /img/monitor/guide-ui-img-alloc-reschedule-details.png
+[img-alloc-reschedule-icon]: /img/monitor/guide-ui-img-alloc-reschedule-icon.png
+[img-alloc-resource-utilization]: /img/monitor/guide-ui-img-alloc-resource-utilization.png
+[img-alloc-stop-restart]: /img/monitor/guide-ui-img-alloc-stop-restart.png
+[img-alloc-unhealthy-driver]: /img/monitor/guide-ui-img-alloc-unhealthy-driver.png
+[img-job-definition-edit]: /img/monitor/guide-ui-img-job-definition-edit.png
+[img-job-deployment-canary]: /img/monitor/guide-ui-img-job-deployment-canary.png
+[img-job-filters]: /img/monitor/guide-ui-img-job-filters.png
+[img-job-stop]: /img/monitor/guide-ui-img-job-stop.png
+[img-jobs-list]: /img/monitor/guide-ui-jobs-list.png
+[img-periodic-force]: /img/monitor/guide-ui-img-periodic-force.png
+[img-task-events]: /img/monitor/guide-ui-img-task-events.png
+[img-task-logs]: /img/monitor/guide-ui-img-task-logs.png
+[in the job definition to reschedule]: /nomad/docs/job-specification/reschedule
+[local restart attempts]: /nomad/docs/job-specification/restart
+[periodic force]: /nomad/commands/job/periodic-force
+[securing the web ui with acls]: /nomad/docs/secure/acl
diff --git a/content/nomad/v1.10.x/content/docs/networking/cni.mdx b/content/nomad/v1.10.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..a77e8d21d5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/cni.mdx
@@ -0,0 +1,387 @@
+---
+layout: docs
+page_title: Container Network Interface plugins and custom bridge networking
+description: |-
+  Install Container Network Interface (CNI) reference plugins. Learn how to configure Nomad's bridge networking. Use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface plugins and custom bridge networking
+
+This page describes the process to install the [Container Network Interface (CNI)
+reference plugins][cni-plugin-docs] on your Linux distribution and configure
+custom CNI bridge networking on your Nomad clients.
+
+You may apply this guide's workflow to installing any network plugin that
+complies with the [CNI Specification][cni-spec], but you should verify plugin
+compatibility with Nomad before deploying in production.
+
+## Background
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+Nomad reads the following extensions from the [`cni_config_dir`][] (`/opt/cni/config` by default):
+
+- `.conflist` files load as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+- `.conf` and `.json` files load as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Install and configure CNI plugins on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, refer to [Use a CNI network
+with a job][] for job configuration.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a custom bridge mode configuration with CNI plugins
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration).
+Refer to that documentation for a complete explanation of the fields.
+
+You can use the following templates as a basis for your own CNI-based bridge
+network configuration in cases where you need access to an unsupported option
+in the default configuration.
+
+### Configuration files
+
+<Tabs>
+  <Tab heading="Default">
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,18,29">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+  <Tab heading="IPv6">
+
+If you [configure IPv6][] on the Nomad client agent using the example range
+`2001:db8::/112`, Nomad adds two more lines to the configuration.
+
+<CodeBlockConfig highlight="19,23">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}],
+          [{"subnet": "2001:db8::/112"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"},
+          {"dst": "::/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+  <Tab heading="Transparent Proxy">
+
+Jobs that use the
+[`transparent_proxy`](/nomad/docs/job-specification/transparent_proxy)
+block add a `consul-cni` plugin to the bottom of the CNI configuration.
+
+Refer to the
+[transparent proxy](/nomad/docs/networking/consul/service-mesh#transparent-proxy)
+section of Nomad's Consul service mesh documentation to ensure that
+the node is configured correctly for this feature.
+
+<CodeBlockConfig highlight="36-39">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    },
+    {
+      "type": "consul-cni",
+      "log_level": "debug"
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+</Tabs>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Next steps
+
+ Refer to [Use a CNI network with a job][] for job configuration details.
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
+[Use a CNI network with a job]: /nomad/docs/job-networking/cni
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[configure IPv6]: /nomad/docs/configuration/client#bridge_network_subnet_ipv6
diff --git a/content/nomad/v1.10.x/content/docs/networking/consul/index.mdx b/content/nomad/v1.10.x/content/docs/networking/consul/index.mdx
new file mode 100644
index 0000000000..650e1bcf21
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/consul/index.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: Consul integration
+description: |-
+  Integrate Consul with Nomad to use Consul features such as automatic clustering, service discovery, service mesh, Consul Template, Consul DNS, Consul ACL, and Consul namespaces with your Nomad clusters and workloads.
+---
+
+# Consul integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and install Consul
+on your nodes alongside Nomad, or schedule it as a system job. Nomad does not
+run Consul for you.
+
+To enable Consul integration, please refer to the [Nomad agent Consul
+configuration][] documentation.
+
+## Automatic clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please refer to the [Automatic Clustering
+with Consul][] guide for more information.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please refer to the
+[`service` job specification documentation][service].
+
+## Service mesh
+
+Consul service mesh provides service-to-service connection authorization and
+encryption using mutual Transport Layer Security (TLS). Nomad can automatically
+provision the components necessary to securely connect your tasks to Consul's
+service mesh.
+
+Refer to the [Consul Service Mesh integration page][int_consul_mesh] for more
+information.
+
+## Dynamic configuration
+
+Nomad's job specification includes a [`template`][] block that uses a Consul
+ecosystem tool called [Consul Template][]. This mechanism creates a convenient
+way to ship configuration files that are populated from environment variables,
+Consul data, Vault secrets, or just general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul
+Template, please see the [`template` job specification documentation][].
+
+## DNS
+
+To provide Consul DNS to Nomad workloads using [bridge or CNI networking
+mode][], you will need to configure Consul's DNS listener to be exposed to the
+workload network namespace, or configure `systemd-resolved`, `dnsmasq`, or
+similar DNS stub resolvers to forward DNS. See [Forward DNS for Consul service
+discovery][] for details.
+
+You can avoid exposing the Consul agent on a public IP by setting the Consul
+`bind_addr` to bind on a private IP address (the default is to use the
+`client_addr`). You will also need to either have Consul bind to port 53 for
+DNS if you are not using DNS forwarding.
+
+You will also need to set the [nameserver][] to the address. This address is
+exposed as the `consul.dns.addr` node attribute or the `DNSStubListener`
+configuration value for `systemd-resolved`.
+
+An simpler solution is to use Consul service mesh [transparent proxy][] mode to
+automatically configure tasks to use Consul DNS.
+
+## Consul access control list (ACL)
+
+The Consul ACL system protects the cluster from unauthorized access. When
+enabled, both Consul and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Consul ACL integration page][int_consul_acl] for more
+information.
+
+## Consul namespaces <EnterpriseAlert inline/>
+
+@include 'consul-namespaces.mdx'
+
+## Multiple Consul clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Consul clusters. They can be
+configured using multiple [`consul`][nomad_config_consul] blocks with different
+`name` values. If a `name` is not provided, the cluster configuration is called
+`default`. Nomad automatic clustering uses the `default` cluster for service
+discovery.
+
+Jobs that need access to Consul may specify which Consul cluster to use with
+the [`consul.cluster`][] parameter.
+
+## Assumptions
+
+* Each Nomad client should have a local Consul agent running on the same host,
+  reachable by Nomad. Nomad clients should never share a Consul agent or talk
+  directly to the Consul servers. Nomad is not compatible with [Consul Data
+  Plane][CDP].
+
+* The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+* Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+* The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+
+* Consul service mesh using network namespaces is only supported on Linux.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Consul.
+
+* Nomad is not compatible with Consul Data Plane.
+
+|               | Consul 1.19.0+ | Consul 1.20.0+ | Consul 1.21.0+ |
+|---------------|----------------|----------------|----------------|
+| Nomad 1.10.0+ | ✅             | ✅             | ✅             |
+| Nomad 1.9.0+  | ✅             | ✅             | ✅             |
+| Nomad 1.8.0+  | ✅             | ✅             | ✅             |
+
+[Automatic Clustering with Consul]: /nomad/docs/deploy/clusters/connect-nodes
+[CDP]: /consul/docs/connect/dataplane
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Nomad agent Consul configuration]: /nomad/docs/configuration/consul
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`template` job specification documentation]: /nomad/docs/job-specification/template#consul-integration
+[`template`]: /nomad/docs/job-specification/template
+[int_consul_acl]: /nomad/docs/secure/acl/consul
+[int_consul_mesh]: /nomad/docs/networking/consul/service-mesh
+[nomad_config_consul]: /nomad/docs/configuration/consul
+[service]: /nomad/docs/job-specification/service
+[bridge or CNI networking mode]: /nomad/docs/job-specification/network#mode
+[nameserver]: /nomad/docs/job-specification/network#servers
+[transparent proxy]: /nomad/docs/job-specification/transparent_proxy
+[Forward DNS for Consul service discovery]: https://developer.hashicorp.com/consul/tutorials/networking/dns-forwarding
diff --git a/content/nomad/v1.10.x/content/docs/networking/consul/service-mesh.mdx b/content/nomad/v1.10.x/content/docs/networking/consul/service-mesh.mdx
new file mode 100644
index 0000000000..b4c8b587dc
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/consul/service-mesh.mdx
@@ -0,0 +1,570 @@
+---
+layout: docs
+page_title: Integrate Consul service mesh
+description: |-
+  Learn how to use Nomad with Consul service mesh to enable secure service-to-service communication. Review an example that enables secure communication with Consul TLS, Consul access control lists (ACLs), and a transparent proxy.
+---
+
+# Consul service mesh
+
+## Introduction
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+## Nomad with Consul service mesh integration
+
+In a production environment, Nomad and Consul exist within the same datacenter.
+
+![Reference diagram](/img/deploy/nomad_reference_diagram.png)
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+## Nomad Consul service mesh example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and the counting service are
+managed by Nomad. Nomad additionally configures Envoy proxies to run along side
+these applications. The dashboard is configured to connect to the counting
+service via localhost on port 9001. The proxy is managed by Nomad, and handles
+mTLS communication to the counting service.
+
+### Prerequisites
+
+#### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+##### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+##### Consul access control lists
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+##### Transparent proxy
+
+Using Nomad's support for [transparent proxy][] configures the task group's
+network namespace so that traffic flows through the Envoy proxy. When the
+[`transparent_proxy`][] block is enabled:
+
+* Nomad will invoke the [`consul-cni`][] CNI plugin to configure `iptables` rules
+  in the network namespace to force outbound traffic from an allocation to flow
+  through the proxy.
+* If the local Consul agent is serving DNS, Nomad will set the IP address of the
+  Consul agent as the nameserver in the task's `/etc/resolv.conf`.
+* Consul will provide a [virtual IP][] for any upstream service the workload
+  has access to, based on the service intentions.
+
+Using transparent proxy has several important requirements:
+
+* You must have the [`consul-cni`][] CNI plugin installed on the client host
+  along with the usual [required CNI plugins][cni_plugins].
+* To use Consul DNS and virtual IPs, you will need to configure Consul's DNS
+  listener to be exposed to the workload network namespace. You can do this
+  without exposing the Consul agent on a public IP by setting the Consul
+  `bind_addr` to bind on a private IP address (the default is to use the
+  `client_addr`).
+* The Consul agent must be configured with [`recursors`][] if you want
+  allocations to make DNS queries for applications outside the service mesh.
+* Your workload's task cannot use the same [Unix user ID (UID)][uid] as the
+  Envoy sidecar proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`][tproxy_no_dns], see below).
+
+For example, a HCL configuration with a [go-sockaddr/template][] binding to the
+subnet `10.37.105.0/20`, with recursive DNS set to OpenDNS nameservers:
+
+```hcl
+bind_addr   = "{{ GetPrivateInterfaces | include \"network\" \"10.37.105.0/20\" | limit 1 | attr \"address\" }}"
+
+recursors = ["208.67.222.222", "208.67.220.220"]
+```
+
+#### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+#### Container Network Interface (CNI) plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/deploy#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+### Run the service mesh-enabled services
+
+Once Nomad and Consul are running, with Consul DNS enabled for transparent proxy
+mode as described above, submit the following service mesh-enabled services to
+Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+#### API service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+group "api" {
+  network {
+    mode = "bridge"
+  }
+
+  # ...
+}
+```
+
+Since the API service is only accessible via Consul service mesh, it does not
+define any ports in its network. The `connect` block enables the service mesh
+and the `transparent_proxy` block ensures that the service will be reachable via
+a virtual IP address when used with Consul DNS.
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {
+        proxy {
+          transparent_proxy {}
+        }
+      }
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+#### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+group "dashboard" {
+  network {
+    mode = "bridge"
+
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        transparent_proxy {}
+      }
+    }
+  }
+}
+```
+
+The `connect` block with `transparent_proxy` configures the web frontend's
+network namespace to route all access to the `count-api` service through the
+Envoy proxy.
+
+The web frontend is configured to communicate with the API service with an
+environment variable `$COUNTING_SERVICE_URL`:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+}
+```
+
+The `transparent_proxy` block ensures that DNS queries are made to Consul so
+that the `count-api.virtual.consul` name resolves to a virtual IP address. Note
+that you don't need to specify a port number because the virtual IP will only be
+directed to the correct service port.
+
+#### Manually configured upstreams
+
+You can also use Connect without Consul DNS and `transparent_proxy` mode. This
+approach is not recommended because it requires duplicating service intention
+information in an `upstreams` block in the Nomad job specification. But Consul
+DNS is not protected by ACLs, so you might want to do this if you don't want to
+expose Consul DNS to untrusted workloads.
+
+In that case, you can add `upstream` blocks to the job spec. You don't need the
+`transparent_proxy` block for the `count-api` service:
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {}
+    }
+  }
+
+  # ...
+
+}
+```
+
+But you'll need to add an `upstreams` block to the `count-dashboard` service:
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        upstreams {
+          destination_name = "count-api"
+          local_bind_port  = 8080
+        }
+      }
+    }
+  }
+}
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend will also need to use an environment variable to communicate
+with the API service:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+}
+```
+
+This environment variable value gets interpolated with the upstream's
+address. Note that dashes (`-`) are converted to underscores (`_`) in
+environment variables so `count-api` becomes `count_api`.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+Bootstrapping the Envoy proxy requires that the Consul ACL token and service
+registration have successfully replicated to whichever Consul server the local
+Consul agent is connected to. Nomad clients poll for this value with exponential
+backoff and a timeout. You can adjust the timeouts on a given node by setting
+node metadata values via the command line or in the [`client.meta`][] agent
+configuration block. The default values are shown below:
+
+```shell-session
+nomad node meta apply -node-id $nodeID \
+    consul.token_preflight_check.timeout=10s \
+    consul.token_preflight_check.base=500ms \
+    consul.service_preflight_check.timeout=60s \
+    consul.service_preflight_check.base=1s
+```
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/deploy#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#install-cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
+[uid]: /nomad/docs/job-specification/transparent_proxy#uid
diff --git a/content/nomad/v1.10.x/content/docs/networking/index.mdx b/content/nomad/v1.10.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..577fcb72e6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/index.mdx
@@ -0,0 +1,341 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Nomad's networking features connect your workloads without running additional component tools like DNS servers and load balancers. Learn about workload allocation networking and bridge networking, which uses Container Network Interface (CNI) plugins or Docker. Review how Nomad networking differs from Kubernetes networking.
+---
+
+# Networking
+
+This page provides conceptual information about Nomad's networking feature, how
+networking works in Nomad, different patterns and configurations, and how Nomad
+networking differs from Kubernetes networking.
+
+## Introduction
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/glossary#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/reference/runtime-environment-settings#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/job-networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+Nomad's bridge network leverages [Container Network Interface (CNI) reference
+plugins](https://www.cni.dev/) to provide an operating-system agnostic interface
+to configure workload networking. Nomad's network plugin support extends Nomad's
+built-in compute resource scheduling to allow scheduling tasks with specialty
+network configurations, which Nomad implements with a combination of CNI
+reference plugins and CNI configuration files. Nomad supports any network plugin
+that complies with the CNI specification, but you should verify plugin
+compatibility with your Nomad version before deploying in production.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/job-networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/job-declare/consul-service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/networking/consul).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/deploy/task-driver/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/job-declare/task-driver/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/job-declare/task-driver/docker#network_mode)
+documentation and the [Networking](/nomad/docs/job-declare/task-driver/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [CConfigure bridge networking](/nomad/docs/networking/cni)
+- [Service discovery](/nomad/docs/networking/service-discovery)
+- [Consul service mesh](/nomad/docs/networking/consul/service-mesh)
+
+## Additional resources
+
+- [Nomad Networking Demystified](https://www.hashicorp.com/en/resources/nomad-networking-demystified)
+- [Multi-Interface Networking and CNI Plugins](https://www.hashicorp.com/en/blog/multi-interface-networking-and-cni-plugins-in-nomad-0-12)
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.10.x/content/docs/networking/ipv6.mdx b/content/nomad/v1.10.x/content/docs/networking/ipv6.mdx
new file mode 100644
index 0000000000..28149ccc08
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/ipv6.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: IPv6 Support in Nomad
+description: |-
+  Learn how Nomad supports IPv6. Configure Nomad to advertise IPv6 addresses. Link Nomad servers and clients that have specific IPv6 addresses. Set up Consul and Vault to use Nomad's IPv6 address. Learn how workload tasks and task drivers can use IPv6 addresses.
+---
+
+# IPv6 Support in Nomad
+
+Nomad supports IPv6 as long as the underlying networks, host machines,
+and operating systems running it support IPv6.
+
+This guide illustrates the different configuration settings you need for different connection contexts.
+
+## Advertise
+
+[Advertise][advertise] Nomad server and client addresses to specify what
+address other servers, clients, or external systems should use to make
+connections back to the agent.
+
+You can use [go-sockaddr][] templating to dynamically select a public IPv6
+address. In this example, for each protocol, fetch one IPv6 address from public
+interfaces and assign it as the protocol's address.
+
+```hcl
+advertise {
+  http = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  rpc  = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  serf = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+}
+```
+
+## Nomad to Nomad
+
+Nomad agent processes connect to one another to make RPC calls for cluster operations.
+
+We recommend using IPv6 on Nomad with DNS that resolves to IPv6 or by
+using cloud auto-join. The following server-to-server and client-to-server
+examples use IPv6 addresses explicitly.
+
+### Server to server
+
+Use the [`server_join`][server_join] block to link servers together.
+
+```hcl
+server {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]"]
+  }
+}
+```
+
+### Client to server
+
+Use the [`servers`][client.servers] parameter or the `server_join` parameter to
+link clients.
+
+```hcl
+client {
+  enabled = true
+  servers = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+}
+```
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+  }
+}
+```
+
+## Nomad to external systems
+
+Most connections between Nomad and other external systems occur via HTTP.
+
+For example, when you set a `NOMAD_ADDR` environment variable like this one:
+
+```
+export NOMAD_ADDR='http://[2001:db8::1]:4646'
+```
+
+You can do the following:
+
+- Use the Nomad CLI, which makes Nomad API calls.
+- Open the Nomad web UI in a browser with the command `nomad ui`.
+- Use [Workload identity][workload-identity].
+  - Nomad can reach Consul and Vault at IPv6 addresses, if they are listening,
+    to register services or fetch secrets.
+  - Configure Consul with the [`nomad setup consul` command][setup-consul].
+
+    ```
+    nomad setup consul -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+
+  - Configure Vault with the [`nomad setup vault` command][setup-vault].
+
+    ```
+    nomad setup vault -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+    ```
+
+Various other third-party services that support OIDC connections should also be
+able to reach Nomad at an IPv6 address, so long as the third-party services
+support IPv6.
+
+## Workloads
+
+Nomad supports arbitrary IPv6 network calls to and from tasks on client nodes.
+
+With host networking, tasks use the same network as the host machine.
+
+- Use these options to register services with an IPv6 address:
+  - Set the [`preferred_address_family`][preferred_address_family-config]
+    client config to `"ipv6"`.
+  - Include a [`service`][service-block] block in your job specification with
+    either the "nomad" or "consul" provider as usual.
+- Use [`bridge_network_subnet_ipv6`][bridge-network-subnet-ipv6] to configure
+  Nomad's [bridge network mode][bridge-network-mode] for IPv6.
+
+[CNI][cni] plugins can work with IPv6 as well. Nomad's bridge network does this.
+
+Some task drivers have their own IPv6 configuration options. If you have enabled
+IPv6 support in the [Docker driver][docker-driver], you can configure IPv6 in
+your job specification. Refer to [IPv6 Docker
+containers][ipv6-docker-containers] for details.
+
+
+[server_join]: /nomad/docs/configuration/server_join
+[client.servers]: /nomad/docs/configuration/client#servers
+[go-sockaddr]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[advertise]: /nomad/docs/configuration#advertise
+[workload-identity]: /nomad/docs/concepts/workload-identity
+[service-block]: /nomad/docs/job-specification/service
+[preferred_address_family-config]: /nomad/docs/configuration/client#preferred_address_family
+[bridge-network-mode]: /nomad/docs/job-specification/network#network-modes
+[bridge-network-subnet-ipv6]: /nomad/docs/configuration/client#bridge_network_subnet_ipv6
+[cni]: /nomad/docs/job-networking/cni
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker
+[ipv6-docker-containers]: /nomad/docs/job-specification/service#ipv6-docker-containers
+[setup-consul]: /nomad/commands/setup/consul
+[setup-vault]: /nomad/commands/setup/vault
diff --git a/content/nomad/v1.10.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.10.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..37db5c55db
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Nomad service discovery helps you automatically connect workloads. Compare Nomad's built-in service discovery feature to Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+---
+
+# Service discovery
+
+@include 'service-discovery.mdx'
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..4625cc3452
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,504 @@
+---
+layout: docs
+page_title: Nomad Access Control List (ACL) policy specification
+description: |-
+  Learn about Nomad's ACL policy specification. Review namespace, node, node pools, agent, operator, resource quota, host volume, and plugin rules policy structure and options. Configure ACLs for the Nomad UI.
+---
+
+# Nomad Access Control List (ACL) policy specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and
+[Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `host-volume-create` - Allows creating dynamic host volumes. This implicitly grants `host-volume-read`.
+- `host-volume-delete` - Allows deleting dynamic host volumes.
+- `host-volume-read` - Allows inspecting dynamic host volumes.
+- `host-volume-register` - Allows registering dynamic host volumes that have been created without a plugin. This implicitly grants `host-volume-read` and `host-volume-create`.
+- `host-volume-write` - Allows all write operations on dynamic host volumes. This implicitly grants `host-volume-read`, `host-volume-create`, `host-volume-register`, and `host-volume-delete`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for these fine-grained namespace capabilities.
+
+
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />host-volume-read<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />host-volume-write<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace. Note that
+variable paths never start with a leading `/`, so Nomad will return an error if
+you submit a policy that has such a path.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configure ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/docs/secure/acl
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..dd3b6f9212
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Nomad object specifications
+description: |-
+  This section contains information on ACL policy, namespace, node pool, resource quota, variable, and volume specifications.
+---
+
+# Nomad object specifications
+
+In addition to
+[Jobs](/nomad/docs/job-specification),
+these Nomad objects have specifications:
+
+- [ACL Policy](/nomad/docs/other-specifications/acl-policy)
+- [Namespace](/nomad/docs/other-specifications/namespace)
+- [Node Pool](/nomad/docs/other-specifications/node-pool)
+- [Resource Quota](/nomad/docs/other-specifications/quota)
+- [Variable](/nomad/docs/other-specifications/variables)
+- [Volume](/nomad/docs/other-specifications/volume)
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..7b707c91f3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: Nomad namespace specification
+description: |-
+  Learn about Nomad's namespace specification. Review namespace parameters. Configure capabilities, node pools, Vault, and Consul.
+---
+
+# Nomad namespace specification
+
+A Nomad namespace is a way to segment jobs and their associated objects from
+other jobs and other cluster users. Specify Nomad namespaces as HCL files and
+submit them with the [`nomad namespace apply`][cli_ns_apply] CLI command.
+Unlike [job specifications][jobspecs], namespace specifications do not support
+[HCL2][hcl2] features like functions.
+
+In [federated][] clusters, Nomad forwards all namespace updates to the
+[`authoritative_region`][] and replicates the updates to non-authoritative
+regions. This requires that you have bootstrapped ACLs in the authoritative
+region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers   = ["java", "docker"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+
+# Vault configuration is a Nomad Enterprise feature.
+vault {
+  default = "default"
+  allowed = ["default", "infra"]
+}
+
+# Consul configuration is a Nomad Enterprise feature.
+consul {
+  default = "default"
+  allowed = ["all", "default"]
+}
+```
+
+## Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+- `vault` <code>([Vault](#vault-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Vault clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+- `consul` <code>([Consul](#consul-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Consul clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+### `capabilities` parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+- `enabled_network_modes` `(array<string>: [])` - List of network modes allowed
+  in the namespace. If empty all network modes are allowed.
+
+- `disabled_network_modes` `(array<string>: [])` - List of network modes disabled
+  in the namespace.
+
+### `node_pool_config` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs or
+  dynamic host volumes in this namespace that don't define a node pool in their
+  specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that jobs or
+  dynamic host volumes in this namespace are allowed to use. By default, all
+  node pools are allowed. If an empty list is provided only the namespace's
+  default node pool is allowed. This field supports wildcard globbing through
+  the use of `*` for multi-character matching. This field cannot be used with
+  `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that jobs or
+  dynamic host volumes in this namespace are not allowed to use. This field
+  supports wildcard globbing through the use of `*` for multi-character
+  matching. If specified, jobs and dynamic host volumes are allowed to use any
+  node pool, except for those that match any of these patterns. This field
+  cannot be used with `allowed`.
+
+### `vault` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Vault cluster to use for jobs
+  in this namespace that don't define a Vault cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Vault clusters that are
+  allowed to be used by jobs in this namespace. By default, all Vault clusters
+  are allowed.  If an empty list is provided only the namespace's default Vault
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Vault clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Vault cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+### `consul` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Consul cluster to use for jobs
+  in this namespace that don't define a Consul cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Consul clusters that are
+  allowed to be used by jobs in this namespace. By default, all Consul clusters
+  are allowed.  If an empty list is provided only the namespace's default Consul
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Consul clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Consul cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+## Resources
+
+Visit the [Nomad namespaces
+tutorial](/nomad/docs/govern/namespaces) to learn how to create
+and use Nomad namespaces
+
+[cli_ns_apply]: /nomad/commands/namespace/apply
+[hcl2]: /nomad/docs/reference/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..e3ee5d1e6a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Nomad node pool specification
+description: |-
+  Learn about Nomad's node pool specification. Review an example node pool specification. Configure description, metadata, and scheduler options.
+---
+
+# Nomad node pool specification
+
+Node pools group nodes, letting you restrict which jobs are able to place
+allocations in a given set of nodes. Specify node pools as HCL files and submit
+them with the [`nomad node pool apply`][pool-apply] CLI command. Unlike [job
+specifications][jobspecs], node pool specifications do not support HCL2
+features like functions.
+
+This example is a node pool specification generated with the [`nomad node pool
+init` command][pool-init].
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/quota.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/quota.mdx
new file mode 100644
index 0000000000..33a00c5aee
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/quota.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Nomad resource quota specification
+description: |-
+  Learn about Nomad's resource quota specification. Review an example resource quota specification. Configure resources, regions, devices, and storage options.
+---
+
+# Nomad resource quota specification
+
+[Resource quotas][] let you limit resource consumption across teams or
+projects to reduce waste and align budgets. Manage resource quotas with the CLI [`quota` command][quota] or with Nomad's [Quota HTTP API][].
+
+<EnterpriseAlert product="nomad" />
+
+## Example resource quota specification
+
+This example is a resource quota specification generated with the [`nomad quota init` command][init].
+
+```hcl
+name        = "default-quota"
+description = "Limit the shared default namespace"
+
+# Create a limit for the global region. Additional limits may
+# be specified in-order to limit other regions.
+limit {
+  region = "global"
+  region_limit {
+    cores      = 0
+    cpu        = 2500
+    memory     = 1000
+    memory_max = 1000
+
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+
+    storage {
+      variables    = 1000 # in MB
+      host_volumes = "1000 GiB"
+    }
+  }
+}
+```
+
+## Parameters
+
+- `name` `(string)` - The name of the Quota. Nomad uses `name` to connect the
+quota a [`Namespace`][].
+- `description` `(string: <optional>)` - A human-readable description.
+- `limit` <code>([QuotaLimit](#limit-parameters))</code> - The resource limit
+in a Nomad region.
+
+### `limit` parameters
+
+- `region` `(string)` - The Nomad `region` that the limit applies to.
+- `region_limit` <code>([RegionLimit](#region_limit-parameters))</code> -
+Resources to limit.
+
+### `region_limit` parameters
+
+Region limits define the limits on cumulative task [`resources`][] blocks for
+allocations in the namespace and region the quota is applied to.
+
+- `cores` `(int: <optional>)` - The limit on total number of CPU cores from all
+`resources.cores` in the namespace. The [CPU concepts][] documentation
+has more details on CPU resources.
+- `cpu` `(int: <optional>)` - The limit on total amount of CPU from all
+`resources.cpu` in the namespace.
+- `memory` `(int: <optional>)` - The limit on total mount of memory in MB from
+all `resources.memory` in the namespace.
+- `memory_max` `(int: <optional>)` - The limit on total mount of hard memory
+limits in MB from all `resources.memory_max` in the namespace.
+- `device` <code>([Device](#device-parameters): nil)</code>
+- `storage` <code>([Storage](#storage-parameters): nil)</code>
+
+### `device` parameters
+
+The `device` label specifies which device(s) the quota applies to,
+equivalent to the [`device`][] block in a job specification.
+
+- `count` `(int)` - How many of this device may be used.
+
+### `storage` parameters
+
+The `storage` block defines limits on provisioned storage.
+
+- `host_volumes` `(int: 0)` - Maximum total size of all [dynamic host volumes][]
+  in MiB. The default `0` means unlimited, and `-1` means variables are fully
+  disabled. This field accepts human-friendly string inputs such as "100
+  GiB". The quota for host volumes is enforced at the time the volume is created
+  via [`volume create`][].
+
+- `variables` `(int: 0)` - Maximum total size of all Nomad [variables][] in
+  MiB. The default `0` means unlimited, and `-1` means variables are fully
+  disabled. This field accepts human-friendly string inputs such as "100 GiB".
+
+## Resources
+
+Visit the [Create and use resource quotas tutorial][tutorial] to learn how to
+create quotas, attach a quota to a namespace, secure a quota with ACL, and
+design quotas for federated clusters.
+
+
+[Resource Quotas]: /nomad/docs/enterprise#resource-quotas
+[quota]: /nomad/commands/quota
+[Quota HTTP API]: /nomad/api-docs/quotas
+[tutorial]: /nomad/docs/govern/resource-quotas
+[`Namespace`]: /nomad/docs/other-specifications/namespace
+[variables]: /nomad/docs/concepts/variables
+[`resources`]: /nomad/docs/job-specification/resources
+[CPU concepts]: /nomad/docs/architecture/cpu
+[`device`]: /nomad/docs/job-specification/device#device-parameters
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[init]: /nomad/commands/quota/init
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f6366ce61c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Nomad variable specification
+description: |-
+  Learn about Nomad's variable specification. Review an example variable specification. Configure path, namespace, and items.
+---
+
+# Nomad variable specification
+
+[Nomad variables][nv] let you store and use encrypted configuration data in your
+job specifications. Specify variables as HCL files and submit them with the
+[`nomad var put` command][var-put]. Unlike [job specifications][jobspecs], Nomad
+variables specifications do not support HCL2 features like functions.
+
+This example is a variable specification generated by [`nomad var init` command][var-init].
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+Refer to the [`nomad var put` restrictions section][var-restrict] for details on `path` and `items` name restrictions.
+
+## Resources
+
+- [Create and update Nomad variables](/nomad/tutorials/variables/variables-create)
+- [Configure access control for Nomad
+  variables](/nomad/tutorials/variables/variables-acls)
+- [Use Nomad variables in tasks](/nomad/docs/job-declare/nomad-variables)
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/commands/var/init
+[var-put]: /nomad/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/commands/var/put#restrictions
+
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..6dd3df44e5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: Nomad volume specification capability block
+description: |-
+  Configure Container Storage Interface (CSI) and dynamic host storage volume capability in the `capability`block of the Nomad volume specification. Set single node or multiple node access and file system or block device attachment mode.
+---
+
+# Nomad volume specification capability block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## Parameters
+
+- `access_mode` `(string)` - Defines whether a volume should be available
+  concurrently. The `access_mode` and `attachment_mode` from the volume request
+  must exactly match one of the volume's `capability` blocks.
+
+  - For CSI volumes the `access_mode` is required. Can be one of the following:
+
+    - `"single-node-reader-only"`: Jobs can only request the volume with
+      read-only access, and only one node can mount the volume at a time.
+    - `"single-node-writer"`: Jobs can request the volume with read/write or
+      read-only access, and only one node can mount the volume at a time.
+    - `"multi-node-reader-only"`: Jobs can only request the volume with
+      read-only access, but multiple nodes can mount the volume simultaneously.
+    - `"multi-node-single-writer"`: Jobs can request the volume with read/write
+      or read-only access, but the scheduler only allows one allocation to have
+      read/write access. Multiple nodes can mount the volume simultaneously.
+    - `"multi-node-multi-writer"`: Jobs can request the volume with read/write
+      or read-only access, and the scheduler allows multiple allocations to have
+      read/write access. Multiple nodes can mount the volume simultaneously.
+
+    Most CSI plugins support only single-node modes. Consult the documentation
+    of the storage provider and CSI plugin.
+
+  - For dynamic host volumes the `access_mode` is optional. Can be one of the following:
+
+    - `"single-node-writer"`: Jobs can only request the volume with read/write access.
+    - `"single-node-reader-only"`: Jobs can only request the volume with read-only access.
+    - `"single-node-single-writer"`: Jobs can request either read/write or
+      read-only access, but the scheduler only allows one allocation to have
+      read/write access.
+    - `"single-node-multi-writer"`: Jobs can request either read/write or
+      read-only access, and the scheduler allows multiple allocations to have
+      read/write access.
+
+    In the job specification, the default is `single-node-writer` unless
+    `read_only = true`, which translates to `single-node-reader-only`.
+
+- `attachment_mode` `(string)` - The storage API used by the volume. One of
+  `"file-system"` or `"block-device"`. The `access_mode` and `attachment_mode`
+  from the volume request must exactly match one of the volume's `capability`
+  blocks.
+
+  - For CSI volumes the `attachment_mode` field is required. Most storage
+    providers support `"file-system"`, to mount volumes using the CSI
+    filesystem API. Some storage providers support `"block-device"`, which
+    mounts the volume with the CSI block device API within the container.
+
+  - For dynamic host volumes the `attachment_mode` field is optional and
+    defaults to `"file-system"`.
+
+## Example
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/csi.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/csi.mdx
new file mode 100644
index 0000000000..35c079db23
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/csi.mdx
@@ -0,0 +1,288 @@
+---
+layout: docs
+page_title: Nomad Container Storage Interface (CSI) volume specification
+description: |-
+  Learn about the Nomad Container Storage Interface (CSI) volume
+  specification. Define capacity, capabilities, mount
+  options, secrets, topology requests, and a context map of values passed
+  directly to the CSI plugin to validate the volume. Learn how volume
+  creation and registration are different. Additionally, learn how to
+  expand the size of a volume and update a volume definition.
+---
+
+# Nomad Container Storage Interface (CSI) volume specification
+
+This page provides reference information for the Nomad Container Storage
+Interface (CSI) volume specification. Create and register CSI volumes using the
+[`volume create`][] and [`volume register`][] commands and the [`PUT
+/v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints. Define capacity,
+capabilities, mount options, secrets, topology requests, and a context map of
+values passed directly to the CSI plugin to validate the volume.  Learn how
+volume creation and registration are different. Additionally, learn how to
+expand the size of a volume and update a volume definition.
+
+Some attributes are only supported by a specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+Provide the file as either HCL or JSON to the commands and as JSON to the API.
+
+## Parameters
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume is somewhere between `capacity_min` and `capacity_max`; the
+  exact behavior is up to the storage provider. If you want to specify an exact
+  size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Increasing this value and reissuing
+  `volume create` or `volume register` may expand the volume, if the CSI plugin
+  supports it.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume is somewhere between `capacity_min` and `capacity_max`; the
+  exact behavior is up to the storage provider. If you want to specify an exact
+  size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume is created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on volume creation.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map of
+  strings passed directly to the CSI plugin to validate the volume. The details
+  of these parameters are specific to each storage provider, so consult the
+  specific plugin documentation for more information. Only allowed on volume
+  registration. Note that, like the rest of the volume specification, this block
+  is declarative, and an update replaces it in its entirety, therefore all
+  parameters need to be specified.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from the
+  storage provider. For example, the volume ID of an AWS EBS volume or Digital
+  Ocean volume. Only allowed on volume registration.
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification refers to
+  the volume.
+
+- `mount_options` <code>([MountOptions][mount_options]:
+  &lt;required&gt;)</code> - Options for mounting `file-system` volumes that
+  don't already have a pre-formatted file system.
+
+- `name` `(string: <required>)` - The name of the volume. On volume creation,
+  the external storage provider may use this field to tag the volume or as an
+  idempotency token, so it must be unique across all namespaces.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map of
+  strings used as credentials for publishing and unpublishing volumes.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume is created from scratch. The `snapshot_id`
+  cannot be set if the `clone_id` field is set. Only allowed on volume creation.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations such as region, zone, and rack where the provisioned volume
+  must be accessible from in the case of volume creation, or the locations where
+  the existing volume is accessible from in the case of volume registration.
+
+- `type` `(string: <required>)` - The type of volume. Must be `"csi"` for CSI
+  volumes.
+
+## Differences between create and register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values if
+they are not supported by the operation.
+
+On **volume registration** you should not set the [`snapshot_id`](#snapshot_id),
+or [`clone_id`](#clone_id) fields.
+
+On **volume creation** you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields.
+
+## Update a volume definition
+
+The `volume register` command allows updating a volume definition. However,
+after volume registration, you are only allowed to update the following fields:
+
+* `capacity_min` and `capacity_max`. You may increase the volume size if the CSI
+  plugin supports it. Expansion may or may not be possible while the volume is
+  in use, again depending on the plugin.  Reducing volume capacity is not
+  allowed per the CSI spec.
+* `mount_options` block if the volume is not in use.
+* `secrets` block
+* `context` block. The values for this field are typically provided by the CSI
+  plugin and should not be updated unless recommended by the CSI plugin's
+  documentation.
+
+Additionally, you may add or remove `capability` blocks, but only if the
+capability is not currently in use by a mounted volume.
+
+## Volume expansion
+
+You may expand CSI Volumes if the CSI controller plugin and node plugin, if
+required, has the `EXPAND_VOLUME` capability.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min) above
+the current real capacity of the volume, as received from the [`volume
+status`][] command, and re-issue either [`volume create`][] or [`volume
+register`][].
+
+Nomad reconciles the requested capacity by issuing expand volume requests to the
+controller plugin, and if required by the controller, also to the node plugins
+for each allocation that has a claim on the volume.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`][] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+
+### Volume expansion
+
+Either [`volume create`][] or [`volume register`][] commands can trigger
+an expand to occur, after the volume has already been created or registered.
+
+This example shows you how to expand a volume using the `volume create` command.
+
+1. Create a volume configuration file called `volume.hcl` that defines ID, name,
+   type, plugin ID, and capacity.
+
+   ```hcl
+   id        = "ebs_prod_db1"
+   name      = "database"
+   type      = "csi"
+   plugin_id = "ebs-prod"
+
+   capacity_min = "50gib"
+   capacity_max = "50gib"
+
+   # ... etc ...
+   ```
+
+1. Create the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created external volume vol-asdf1234 with ID ebs_prod_db1
+   ```
+
+1.  Review the volume's current capacity using the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status ebs_prod_db1 | grep Capacity
+   Capacity             = 50 GiB
+   ```
+
+1. Increase volume capacity in the `volume.hcl` file.
+
+   Update the `capacity_min` and `capacity_max` fields.
+
+   ```hcl
+   id        = "ebs_prod_db1"
+   name      = "database"
+   type      = "csi"
+   plugin_id = "ebs-prod"
+   # all of the above must remain the same
+
+   capacity_min = "100gib" # double
+   capacity_max = "100gib" # increased to match
+
+   # ... etc ...
+   ```
+
+1. Expand the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created external volume vol-asdf1234 with ID ebs_prod_db1
+   ```
+
+1. Review the new capacity by running the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status ebs_prod_db1 | grep Capacity
+   Capacity             = 100 GiB
+   ```
+
+If you encounter errors that are not clear from the command output,
+the CSI plugin allocation logs and Nomad leader server logs may be
+helpful.
+
+[api_volume_create]: /nomad/api-docs/volumes#create-csi-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-csi-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[`volume status`]: /nomad/commands/volume/status
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/host.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/host.mdx
new file mode 100644
index 0000000000..7f474422c6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/host.mdx
@@ -0,0 +1,346 @@
+---
+layout: docs
+page_title: Nomad dynamic host volume specification
+description: |-
+  Learn about the Nomad dynamic host volume specification. Define capacity,
+  capability, constraint, node, node pool, and parameters passed directly
+  to the plugin to configure the volume. Learn how volume creation and
+  registration are different. Additionally, learn how to place a volume on
+  specific nodes, update a volume, and expand a volume's capacity.
+---
+
+# Nomad dynamic host volume specification
+
+This page provides reference information for the Nomad dynamic host volume
+specification. Create and register dynamic host volumes using the [`volume
+create`][] and [`volume register`][] commands and the [`PUT
+/v1/volume/host/create`][api_volume_create] and [`PUT
+/v1/volume/host/register`][api_volume_register] API endpoints.  Define capacity,
+capability, constraint, node, node pool, and parameters passed directly to the
+plugin to configure the volume.  Learn how volume creation and registration are
+different. Additionally, learn how to place a volume on specific nodes, update a
+volume, and expand a volume's capacity.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API.
+
+## Parameters
+
+- `capacity` `(string: <optional>)` - The size of a volume in bytes. Either the
+  physical size of a disk or a quota, depending on the plugin. This field must
+  be between the `capacity_min` and `capacity_max` values unless they are
+  omitted. Accepts human-friendly suffixes such as `"100GiB"`. Only supported
+  for volume registration.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the plugin. The specific size of the resulting
+  volume is somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the plugin. If you want to specify an exact size, set
+  `capacity_min` and `capacity_max` to the same value. Accepts human-friendly
+  suffixes such as `"100GiB"`. Plugins that cannot restrict the size of volumes,
+  such as the built-in [`mkdir`][mkdir_plugin] plugin, may ignore this field.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the plugin. The specific size of the resulting
+  volume is somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the plugin. If you want to specify an exact size, set
+  `capacity_min` and `capacity_max` to the same value. Accepts human-friendly
+  suffixes such as `"100GiB"`. Plugins that cannot restrict the size of volumes,
+  such as the built-in [`mkdir`][mkdir_plugin] plugin, may ignore this field.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `constraint` <code>([Constraint][constraint]: &lt;optional&gt;)</code> - A
+  restriction on the eligible nodes where a volume can be created. Refer to the
+  [volume placement](#volume-placement) section for details. You can provide
+  multiple `constraint` blocks to add more constraints. Optional for volume
+  creation and ignored for volume registration.
+
+- `id` `(string: <optional>)` - The ID of a previously created volume to update
+  via `volume create` or `volume register`. You should never set this field when
+  initially creating or registering a volume, and you should only use the values
+  returned from the Nomad API for the ID.
+
+- `host_path` `(string)` - The path on disk where the volume exists. You should
+  set this only for volume registration. It is ignored for volume creation.
+
+- `name` `(string: <required>)` - The name of the volume, which is used as the
+  [`volume.source`][volume_source] field in job specifications that claim this
+  volume. Host volume names must be unique per node. Names are visible to any
+  user with `node:read` ACL, even across namespaces, so they should not be
+  treated as sensitive values.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `node_id` `(string)` - A specific node where you would like the volume to be
+  created. Refer to the [volume placement](#volume-placement) section for
+  details. Optional for volume creation but required for volume registration.
+
+- `node_pool` `(string: <optional>)` - A specific node pool where you would like
+  the volume to be created. Refer to the [volume placement](#volume-placement)
+  section for details. Optional for volume creation or volume registration. If
+  you also provide `node_id`, the node must be in the provided `node_pool`.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the plugin to configure the volume. The details
+  of these parameters are specific to the plugin.
+
+- `plugin_id` `(string)` - The ID of the [dynamic host volume
+  plugin][dhv_plugin] that manages this volume. Required for volume
+  creation. Nomad has one built-in plugin called [`mkdir`][mkdir_plugin].
+
+- `type` `(string: <required>)` - The type of volume. Must be `"host"` for
+  dynamic host volumes.
+
+## mkdir plugin
+
+Nomad has one built-in plugin called `mkdir`, which creates a directory on the
+host in the Nomad agent's [host_volumes_dir][]. The directory name is the
+volume's ID.
+
+`mkdir` ignores `capacity_min` and `capacity_max` volume configuration,
+since it has no way of enforcing them.
+
+### mkdir parameters
+
+- `mode` `(string: <optional>)` - [Numeric
+notation](https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation)
+to apply to the created directory. Defaults to "0700", so only the owner can
+access it. Must be a string, or you may get unexpected results.
+- `uid` `(int: <optional>)` - User ID to own the directory. Defaults to the
+user running the Nomad client agent, which is commonly `0` (root).
+- `gid` `(int: <optional>)` - Group ID to own the directory. Defaults to the
+user running the Nomad client agent, which is commonly `0` (root).
+
+The user and group IDs must be present on any node that may receive the volume.
+
+### mkdir example
+
+<CodeBlockConfig filename="mkdir.volume.hcl">
+
+```hcl
+type      = "host"
+name      = "cool-host-vol"
+plugin_id = "mkdir"
+parameters = {
+  mode = "0755"
+  uid  = 1000
+  gid  = 1000
+}
+```
+
+</CodeBlockConfig>
+
+## Differences between create and register
+
+Several fields are set automatically by Nomad or the plugin when `volume create`
+or `volume register` commands, or the equivalent APIs, are successful and you
+should not set their values if they are not supported by the operation.
+
+In **volume creation** you must set the [`plugin_id`](#plugin_id) field. The
+[`capacity`](#capacity) and [`host_path`](#host_path) fields are ignored.
+
+In **volume registration** you must set the [`node_id`](#node_id) and
+[`host_path`](#host_path) fields. The [`plugin_id`](#plugin_id) and
+[`constraint`](#constraint) fields are ignored. The [`node_pool`](#node_pool),
+[`capacity_max`](#capacity_max), and [`capacity_min`](#capacity_min) fields are
+ignored but must be consistent if set; the `node_pool` must match the node set
+by `node_id`, and the minimum capacity must be less than the `capacity_max` and
+`capacity`.
+
+## Volume placement
+
+The `volume create` command creates the volume on a single node. If `node_id` is
+set, the volume is created on that node. The `node_pool` must be unset or match
+that node. Otherwise, the Nomad server iterates over the available nodes and
+place the volume on the first available node based on the following factors:
+
+* The node cannot already have a host volume with the same name.
+* If `node_pool` is set, the selected node must be in that node pool.
+* The node must meet any and all constraints defined by the `constraint` fields.
+
+## Update a volume definition
+
+The `volume create` and `volume register` commands allow updating a volume
+definition. However, after volume registration, you are only allowed to update
+the following fields:
+
+- `plugin_id`
+- `capacity_min` and `capacity_max`. You may increase
+  the volume size if the plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.  Reducing
+  volume capacity is not allowed. Only available for volume creation.
+- `capacity`, but only updated for volume registration.
+- `constraint` fields. Ignored after the volume is created.
+
+Additionally, you may add or remove `capability` blocks, but only if the
+capability is not currently in use by a mounted volume.
+
+You cannot update the `name`, `type`, and `node_id` fields. You may only change
+the `node_pool` field from empty to the node pool that matches the `node_id`
+field.
+
+## Volume expansion
+
+Dynamic host volumes may be expanded if the plugin allows. Reducing the size of
+a volume is not permitted.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min) above
+the current real capacity of the volume (as shown with the [`volume status`][]
+command), and re-issue [`volume create`][].
+
+Nomad reconciles the requested capacity by issuing a create request to the
+plugin.
+
+## Examples
+
+### Volume creation
+
+This is an example file used for the [`volume create`][] command.
+
+```hcl
+name            = "database"
+type            = "host"
+plugin_id       = "lvm-thin-provisioner"
+node_pool       = "prod"
+
+capacity_min = "80G"
+capacity_max = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+### Volume registration
+
+This is an example file used for the [`volume register`][] command.
+
+```hcl
+name      = "database"
+type      = "host"
+node_id   = "a7b4c0ca-cc78-11ef-8b5a-cb6ea67b844c"
+host_path = "/var/srv/example"
+capacity  = "80G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+### Volume expansion
+
+This example shows how to expand a volume after it has been created or
+registered.
+
+1. Create a volume configuration file called `volume.hcl` that defines name,
+   type, plugin ID, and capacity.
+
+  ```hcl
+   name      = "database"
+   type      = "host"
+   plugin_id = "external-plugin"
+
+   capacity_min = "30GiB"
+   capacity_max = "50GiB"
+   ```
+
+1. Create the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create ./volume.hcl
+   ==> Created host volume database with ID 0c903229-311d-ba8a-f77e-45c31b83fab3
+   ✓ Host volume "0c903229" ready
+
+    2025-01-06T16:56:09-05:00
+    ID        = 0c903229-311d-ba8a-f77e-45c31b83fab3
+    Name      = database
+    Namespace = default
+    Plugin ID = external-plugin
+    Node ID   = cfe033a7-50de-2c46-cd18-12be7429eeb3
+    Node Pool = default
+    Capacity  = 50 GiB
+    State     = ready
+    Host Path = /run/nomad/dev/alloc_mounts/0c903229-311d-ba8a-f77e-45c31b83fab3
+   ```
+
+1. Review the volume's current capacity using the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status -type=host 0c903229 | grep Capacity
+   Capacity             = 50 GiB
+   ```
+
+1. Increase volume capacity in the `volume.hcl` file.
+
+   Update the `capacity_min` and `capacity_max` fields.
+
+   ```hcl
+   id        = "0c903229-311d-ba8a-f77e-45c31b83fab3"
+   name      = "database"
+   type      = "host"
+   plugin_id = "external-plugin"
+
+   capacity_min = "100GiB" # double
+   capacity_max = "100GiB" # increased to match
+   ```
+
+1. Expand the volume using the [`volume create`] command.
+
+   The `volume create` command can trigger an expansion to occur, after the
+   volume has already been created or registered.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created host volume database with ID 0c903229-311d-ba8a-f77e-45c31b83fab3
+   ```
+
+1. Review the new capacity by running the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status -type=host 0c903229 | grep Capacity
+   Capacity             = 100 GiB
+   ```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-dynamic-host-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-dynamic-host-volume
+[volume_source]: /nomad/docs/job-specification/volume#source
+[capability]: /nomad/docs/other-specifications/volume/capability
+[constraint]: /nomad/docs/job-specification/constraint
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[`volume status`]: /nomad/commands/volume/status
+[dhv_plugin]: /nomad/docs/architecture/storage/host-volumes
+[mkdir_plugin]: #mkdir-plugin
+[host_volumes_dir]: /nomad/docs/configuration/client#host_volumes_dir
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..70ba14d3f0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: Nomad volume specification
+description: |-
+  Learn about the Nomad volume specification. Review an example volume specification. Create and register Container Storage Interface (CSI) and dynamic host volumes. Define capability, mount options, topology requests, secrets, and parameters.
+---
+
+# Nomad volume specification
+
+This page provides reference information for the Nomad volume
+specification. Create and register Container Storage Interface (CSI) and dynamic
+host volumes using the [`volume create`][] and [`volume register`][] commands
+and the equivalent API endpoints. Define capability, mount options, topology
+requests, secrets, and parameters.
+
+Some attributes are only be supported by one volume type or the other, or a
+specific operation, while others may have a different meaning for each action,
+so read the documentation for each attribute carefully.
+
+* [CSI volume specification][csi_spec]
+* [Dynamic host volume specification][dhv_spec]
+
+Provide the file as either HCL or JSON to the commands and as JSON to
+the API.
+
+This example HCL configuration is for a CSI volume.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[csi_spec]: /nomad/docs/other-specifications/volume/csi
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..a653de2880
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Nomad volume specification `mount_options` block
+description: |-
+  Configure Container Storage Interface (CSI) storage volume file system type and mount flags in the `mount_options` block of the Nomad volume specification.
+---
+
+# Nomad volume specification `mount_options` block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` CSI volumes that don't already have a
+pre-formatted file system. The `mount_options` block is not supported for
+dynamic host volumes.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.10.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.10.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..a8a519401d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Nomad volume specification `topology_request` block
+description: |-
+  Configure Container Storage Interface (CSI) storage volume topology in the `topology_request` block of the Nomad volume specification. Specify region, zone, and rack so that Nomad can access a provisioned CSI volume. Review volume creation examples with preferred and required topologies.
+---
+
+# Nomad volume specification `topology_request` block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations such as region, zone, and rack, where a provisioned CSI volume must
+be accessible, or where an existing volume is accessible. The `topology_request`
+block is not supported for dynamic host volumes.
+
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## Example
+
+This example illustrates volume creation with `preferred` and `required`
+topologies. The configuration requires Nomad to create the volume within racks
+`R1` or `R2`, but that you prefer creation within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.10.x/content/docs/partnerships.mdx b/content/nomad/v1.10.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..5bcefcba07
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/partnerships.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: Nomad Integration Program
+description: The HashiCorp Nomad Integration Program is the process for building and certifying products that integrate with Nomad. Review the integration categories and development process.
+---
+
+# Nomad Integration Program
+
+This page provides an overview of the HashiCorp Nomad Integration Program.
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and
+non-containerized applications across on-premises and cloud environments at
+scale. Nomad is widely adopted and used in production by organizations like
+Cloudflare, Roblox, Q2, Pandora, and more. Refer to the [What is Nomad?
+page](/nomad/docs/what-is-nomad) for a full description of the current features.
+
+This diagram depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/job-declare/task-driver)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/plugins/author/task-driver)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/plugins/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/plugins/author/device)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/architecture/storage/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/monitor)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.10.x/content/docs/quickstart.mdx b/content/nomad/v1.10.x/content/docs/quickstart.mdx
new file mode 100644
index 0000000000..bccbef1d36
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/quickstart.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Nomad quickstart
+description: |-
+  The Nomad quickstart page contains links to resources that show you how to get started using Nomad locally or in a cloud environment.
+---
+
+# Nomad quickstart
+
+These installations are designed to get you started with Nomad and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, refer to the [Production Installation
+guide](/nomad/docs/deploy/production).
+
+## Nomad tutorials
+
+We recommend these tutorials, which provision a Nomad cluster for you.
+
+- [Get Started][]: Get up and running with Nomad by learning about scheduling,
+  setting up a cluster, and deploying an example job. Create a Nomad cluster
+  on your local machine or in an AWS, Azure, or Google Cloud Platform (GCP)
+  cloud environment. This tutorial series has an associated code repository so
+  you can review the Terraform provisioning scripts and Nomad job specifications.
+- [Cluster Setup][]: Provision a Nomad cluster on AWS, Azure, or GCP. Enable
+  Consul and access control lists (ACLs). This tutorial series has an associated
+  code repository so you can review the Terraform provisioning scripts.
+
+## Cloud installation
+
+The Nomad repository contains guides and Terraform scripts for provisioning a
+Nomad sandbox environment on AWS, Azure, or GCP with Consul and Vault. You can
+explore Nomad and its integrations with the HashiCorp stack.
+
+- [Provision a Nomad cluster on AWS][]
+- [Provision a Nomad cluster on Azure][]
+- [Provision a Nomad cluster on GCP][]
+
+## Local installation
+
+Use one of the following methods to run a local Nomad sandbox environment:
+
+- Install a binary
+
+  Refer to the [Install Nomad guide][installing-binary] to install the latest
+  Nomad release binary.
+
+  Run Nomad with the `sudo nomad agent -dev` [command][agent-dev], which
+  starts the Nomad agent in development mode.
+
+  If you are using Docker Desktop for Windows or MacOS, refer to [How to connect
+  to my host network when using Docker Desktop (Windows and MacOS)][faq-win-mac]
+  for instructions on binding Nomad to a non-loopback network interface.
+
+- Use Vagrant and VirtualBox
+
+  This option requires AMD hardware.
+
+  The Nomad repository contains a Vagrantfile. Refer to the [Developing with
+  Vagrant section][vagrant] of the [Nomad Codebase
+  Documentation][compile-source] file for instructions.
+
+- Compile and run from source
+
+  This option requires software engineering experience and a workstation set up
+  for Go, Node, and Docker development.
+
+  Refer to the Nomad repository's [Nomad Codebase Documentation][compile-source]
+  file for details.
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/deploy
+[Get Started]: /nomad/tutorials/get-started
+[Cluster Setup]: /nomad/tutorials/cluster-setup
+[Provision a Nomad cluster on AWS]: https://github.com/hashicorp/nomad/blob/main/terraform/aws/README.md
+[Provision a Nomad cluster on Azure]:
+    https://github.com/hashicorp/nomad/blob/main/terraform/azure/README.md
+[Provision a Nomad cluster on GCP]: https://github.com/hashicorp/nomad/blob/main/terraform/gcp/README.md
+[agent-dev]: /nomad/commands/agent#dev
+[vagrant]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md#developing-with-vagrant
+[compile-source]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md
diff --git a/content/nomad/v1.10.x/content/docs/reference/go-template-syntax.mdx b/content/nomad/v1.10.x/content/docs/reference/go-template-syntax.mdx
new file mode 100644
index 0000000000..17a33b806e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/go-template-syntax.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: Go template syntax
+description: |-
+  Discover the syntax of the text and template packages in Go and
+  become comfortable using them to create templates for Nomad
+  jobs.
+---
+
+# Go template syntax
+
+Go's internal templating language, provided by the text/template package, is the
+basis for many commonly used template implementations. Some HashiCorp specific
+examples are:
+
+- Nomad `template` stanzas
+- Consul-template
+- Vault agent templates
+- Nomad Pack
+
+Some other implementations you might have seen are:
+
+- Hugo
+- Helm
+
+Go's template is designed to be extended by developers, and provides access to
+data objects and additional functions that are passed into the template engine
+programmatically. This guide only uses functions universally provided in
+the text/template package, and does not discuss the specifics of data access.
+However, once you have learned the basics of Go templates, implementation
+specific data access is easier to understand.
+
+Early in this guide, you will see elements that you are not familiar with
+yet, but don't panic. Use your intuition and experience with other languages as
+your guide. As the guide progresses, it revisits these examples
+with a more thorough explanation.
+
+## Starting template
+
+Here is a template to get you started on your journey. This guide refers
+to this template while you are learning the names for the syntax.
+
+```plaintext
+This is a simple template
+It can {{ "output" }} something.
+It also
+{{- " demonstrates" }} trim markers.
+{{/* it has a comment */}}
+It can {{ "output" }} something.
+It can demonstrate {{ "output" | print }} using pipelines.
+It also {{ $A := "assigns variables" }}{{ $A }}.
+And conditionals:
+{{ $B := 2 }}{{ if eq $B 1 }}B is 1{{ else }}B is 2{{ end }}
+```
+
+## Nomenclature
+
+Go template uses names for its objects that are not immediately familiar. Once
+you have familiarized yourself with the concepts, the canonical documentation
+becomes easier to read.
+
+### Template
+
+Not surprisingly, the template is the entire text that is submitted to the
+template engine to be rendered. The template consists of text and "actions". All
+text outside of actions is copied to the output unchanged.
+
+### Actions
+
+Actions provide the dynamic components of the template. They are set off from
+the text using delimiters. The actions in the sample template are:
+
+```plaintext
+{{ "output" }}
+{{- " demonstrates" }}
+{{/* it has a comment */}}
+{{ "output" | print }}
+{{ $A := "assigns variables" }}{{ $A }}.
+{{ $B := 2 }}{{ if eq $B 1 }}{{ else }}{{ end }}
+```
+
+Actions are composed of "control structures," or data evaluations through
+"pipelines."
+
+<Note>
+
+ Actions may not span newlines. However, raw-string literals and
+comments may contain newlines. Raw-string literals are a special type of
+string literal discussed later.
+
+</Note>
+
+### Delimiters
+
+As said earlier, actions are set between a left delimiter (`{{` by default)
+and a right delimiter (`}}` by default). The implementation can either use
+alternative delimiters, like Levant's use of `[[` and `]]`; or allow you to
+specify them as in Nomad's `template` stanza.
+
+<Note>
+
+ The HashiCorp Learn tutorials use go template's default delimiters
+of `{{` and `}}` unless specifically stated in the guide itself. Remember
+that these delimiters might need to be customized for your specific use case.
+
+</Note>
+
+#### Trim markers
+
+Go template outputs everything between actions, including whitespace and
+line feeds. This can make it challenging to read nested template code.
+
+If an action's left delimiter is followed immediately by
+a minus sign and ASCII space character `{{- `, all trailing white space
+is trimmed from the immediately preceding text. Similarly, if the right
+delimiter is preceded by a space and minus sign ` -}}`, all
+leading white space is trimmed from the immediately following text.
+
+<Note>
+
+ The ASCII space must be present in these trim markers. `{{-3}}`
+parses as an action containing the number -3.
+
+</Note>
+
+### Comments
+
+Comments are a special action created using a `/*` immediately following the
+left delimiter and a `*/` immediately preceding the right delimiter. The sample
+template has a comment.
+
+```plaintext
+{{/* it has a comment */}}
+```
+
+Comments can span multiple lines. Any elements within the comment start and end
+delimiters is not processed by the rendering engine. Comments can also contain
+trim markers on one or both ends to remove whitespace. Comments with trim markers
+must have a space between the `-` and the start or end of the comment.
+
+```plaintext
+{{- /* example comment with trim markers /* -}}
+```
+
+<Tip>
+
+ Comment out sections of a template while you are debugging it to
+simplify your troubleshooting.
+
+</Tip>
+
+### Pipelines
+
+A pipeline is one or more "commands" chained together using the pipe `|` symbol.
+A command is a:
+
+- simple value (argument)
+- function or method call, possibly with multiple arguments.
+
+For example:
+
+```plaintext
+It can demonstrate {{ "output" | print }} using pipelines.
+```
+
+This template line uses pipelining to send the string literal "output" to the
+print function.
+
+#### Simple values
+
+Simple values are typically used as either the sole element in an action, like a
+string literal
+
+```plaintext
+{{ "output" }}
+```
+
+which is rendered to the template in place. Simple values can also be references
+to data provided as context to the template. This context is represented by a
+period '.' and called "dot".
+
+<Note>
+
+ Implementation-specific tutorials will describe dot and its usage
+in further detail.
+
+</Note>
+
+#### Literals
+
+Go template supports the following types as literals.
+
+| Data type        | Example                          | Specification                                                                      | Notes                                |
+| ---------------- | -------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------ |
+| `string`         | "output"                         | [String literal spec](https://golang.org/ref/spec#String_literals)                 | may not contain unescaped line feeds |
+| `raw string`     | \`"out<br />put"\`               | [String literal spec](https://golang.org/ref/spec#String_literals)                 | can contain raw linefeed characters  |
+| `integer`        | 42 <br />0xBadFace<br />         | [Integer literal Spec](https://golang.org/ref/spec#Integer_literals)               |                                      |
+| `floating point` | 0.<br />72.40<br />2.71828<br /> | [Floating-point literal Spec](https://golang.org/ref/spec#Floating-point_literals) |                                      |
+| `boolean`        | true<br />false                  | [Boolean type](https://golang.org/ref/spec#Boolean_types)                          |                                      |
+
+#### Function calls
+
+Go template provides a very limited number of functions universally, and instead
+relies on the specific implementation to add functions to enhance the user
+experience. However, `print` is one of the available functions.
+
+```plaintext
+{{ "output" | print }}
+```
+
+Later in the guide, there is a list of the built-in functions provided by all
+Go template environments.
+
+#### Method calls
+
+Since Go template provides an empty context to the template by default, there
+are no methods to be called. Refer to an implementation specific guide for more
+information on method calls.
+
+### Control structures
+
+Go template control structures are used to provide branching, iteration, and
+sub-templates. The control structure documentation uses `T0` and `T1` as
+placeholders for the specific template content that would be contained there.
+
+T0 and T1 might see a different version of dot depending on the control
+structure that is generating them. For example, `with` and `range` redefine
+dot to a new scope when their pipeline is non-empty.
+
+## Control structure list
+
+### if
+
+```plaintext
+{{if pipeline}} T1 {{end}}
+```
+
+If the value of the pipeline is empty, no output is generated; otherwise, T1 is
+executed. The empty values are false, 0, any nil pointer or interface value, and
+any array, slice, map, or string of length zero. Dot is unaffected.
+
+```plaintext
+{{if pipeline}} T1 {{else}} T0 {{end}}
+```
+
+If the value of the pipeline is empty, T0 is executed; otherwise, T1 is
+executed. Dot is unaffected.
+
+```plaintext
+{{if pipeline}} T1 {{else if pipeline}} T0 {{end}}
+```
+
+To simplify the appearance of if-else chains, the else action
+of an if may include another if directly; the effect is exactly
+the same as writing:
+
+```plaintext
+{{if pipeline}} T1 {{else}}{{if pipeline}} T0 {{end}}{{end}}
+```
+
+The sample template uses `if` and the `eq` function to branch
+between outputs.
+
+```plaintext
+{{ if eq $B 1 }}B is 1{{ else }}B is not 1{{ end }}
+```
+
+### range
+
+```plaintext
+{{range pipeline}} T1 {{end}}
+```
+
+The value of the pipeline must be an array, slice, map, or channel.
+If the value of the pipeline has length zero, nothing is output;
+otherwise, dot is set to the successive elements of the array,
+slice, or map and T1 is executed. If the value is a map and the
+keys are of basic type with a defined order, the elements are
+visited in sorted key order.
+
+```plaintext
+{{range pipeline}} T1 {{else}} T0 {{end}}
+```
+
+The value of the pipeline must be an array, slice, map, or channel.
+If the value of the pipeline has length zero, dot is unaffected and
+T0 is executed; otherwise, dot is set to the successive elements
+of the array, slice, or map and T1 is executed.
+
+One place you can test range is using the `-t` flag on many of the
+nomad commands. For example, you can retrieve the Node ID and version
+of each client in your cluster with the following command.
+
+```shell-session
+$ nomad node status -t '{{range .}}{{print .ID}} {{println .Version}}{{end}}'
+```
+
+### with
+
+```plaintext
+{{with pipeline}} T1 {{end}}
+```
+
+If the value of the pipeline is empty, no output is generated; otherwise, dot is
+set to the value of the pipeline and T1 is executed.
+
+```plaintext
+{{with pipeline}} T1 {{else}} T0 {{end}}
+```
+
+If the value of the pipeline is empty, dot is unaffected and T0 is executed;
+otherwise, dot is set to the value of the pipeline and T1 is executed.
+
+### define
+
+```plaintext
+{{define "name"}} T1 {{end}}
+```
+
+Create a template with the specified name that can be invoked using a `template`
+control structure
+
+### template
+
+```plaintext
+{{template "name"}}
+```
+
+The template with the specified name is executed with nil data.
+
+```plaintext
+{{template "name" pipeline}}
+```
+
+The template with the specified name is executed with dot set to the value of
+the pipeline.
+
+### block
+
+```plaintext
+{{block "name" pipeline}} T1 {{end}}
+```
+
+A block is shorthand for defining a template
+
+```plaintext
+{{define "name"}} T1 {{end}}
+```
+
+and then executing it in place
+
+```plaintext
+{{template "name" pipeline}}
+```
+
+The typical use is to define a set of root templates that are then customized by
+redefining the block templates within.
+
+## Function list
+
+Go template provides the following functions. Most implementations provide
+additional functions and can optionally override the default implementations.
+Consult the specific application's documentation for more information.
+
+### Functions
+
+| Function name | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| and           | Returns the boolean AND of its arguments by returning the first empty argument or the last argument, that is, "and x y" behaves as "if x then y else x". **All the arguments are evaluated.**                                                                                                                                                                                                                                                                                                                                                                                                 |
+| call          | Returns the result of calling the first argument, which must be a function, with the remaining arguments as parameters. Thus "call .X.Y 1 2" is, in Go notation, dot.X.Y(1, 2) where Y is a func-valued field, map entry, or the like. The first argument must be the result of an evaluation that yields a value of function type (as distinct from a predefined function such as print). The function must return either one or two result values, the second of which is of type error. If the arguments don't match the function or the returned error value is non-nil, execution stops. |
+| index         | Returns the result of indexing its first argument by the following arguments. Thus `index x 1 2 3` is, in Go syntax, `x[1][2][3]`. Each indexed item must be a map, slice, or array.                                                                                                                                                                                                                                                                                                                                                                                                          |
+| slice         | slice returns the result of slicing its first argument by the remaining arguments. Thus:<ul><li>`slice x 1 2` is, in Go syntax, `x[1:2]`</li><li> `slice x` is `x[:]`</li><li> `slice x 1` is `x[1:]`, </li><li>`slice x 1 2 3` is `x[1:2:3]`</li></ul> The first argument must be a string, slice, or array.                                                                                                                                                                                                                                                                                 |
+| len           | Returns the integer length of its argument.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| not           | Returns the boolean negation of its single argument.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| or            | Returns the boolean OR of its arguments by returning the first non-empty argument or the last argument, that is,"or x y" behaves as "if x then x else y". **All the arguments are evaluated.**                                                                                                                                                                                                                                                                                                                                                                                                |
+| print         | An alias for [fmt.Sprint][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| printf        | An alias for [fmt.Sprintf][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| println       | An alias for [fmt.Sprintln][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+### Comparison functions
+
+| Function name | Description                               |
+| ------------- | ----------------------------------------- |
+| eq            | Returns the boolean truth of arg1 == arg2 |
+| ne            | Returns the boolean truth of arg1 != arg2 |
+| lt            | Returns the boolean truth of arg1 < arg2  |
+| le            | Returns the boolean truth of arg1 <= arg2 |
+| gt            | Returns the boolean truth of arg1 > arg2  |
+| ge            | Returns the boolean truth of arg1 >= arg2 |
+
+### Specialized output functions
+
+| Function name | Description                                                                                                               |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| html          | Returns the escaped HTML equivalent of the textual representation of its arguments.                                       |
+| js            | Returns the escaped JavaScript equivalent of the textual representation of its arguments.                                 |
+| urlquery      | Returns the escaped value of the textual representation of its arguments in a form suitable for embedding in a URL query. |
+
+
+[fmt.sprint]: https://golang.org/pkg/fmt/#Sprint
+[fmt.sprintf]: https://golang.org/pkg/fmt/#Sprintf
+[fmt.sprintln]: https://golang.org/pkg/fmt/#Sprintln
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/expressions.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/expressions.mdx
new file mode 100644
index 0000000000..4b8eef91f1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/expressions.mdx
@@ -0,0 +1,440 @@
+---
+layout: docs
+page_title: HCL expressions reference
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# HCL expressions reference
+
+Use HCL expressions to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced type details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/reference/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/reference/hcl2/functions).
+
+## `for` expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+**Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/reference/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
+
+
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..91e08ce6ef
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/reference/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..d5d34fd183
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/reference/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/compact.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/concat.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/contains.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/element.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..2d1ed4b971
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/reference/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/reference/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..ba579570d4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/reference/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..d4bf631d85
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/reference/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/keys.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..95b9caf985
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/reference/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/length.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..44b9563fb5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/reference/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/merge.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/range.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..6322e84f33
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/reference/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..29946b1263
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/reference/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..9d5c9d1e6f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/reference/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/reference/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/reference/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/reference/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..11c29e3ea0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/reference/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/slice.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..f997dbefe5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/reference/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/sort.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/values.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..396362787e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/reference/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/reference/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/can.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..5a1cdad38b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/reference/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/reference/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/reference/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/try.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..816cf73a30
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/reference/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..98ef4832b7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/secure/vault">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..ef918db1c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..93215259d3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/reference/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..07047561fa
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/reference/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..7b6a3529c7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..d11207c514
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/reference/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..394f48712c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/reference/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/reference/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..8a74fe44a6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/reference/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/abspath.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..0a33a9cd1c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/reference/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/basename.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..bff05fe35c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/reference/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/reference/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/dirname.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..544e6e6ab7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/reference/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/reference/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/file.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..fc2955718b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/reference/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..f75370b2f7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/reference/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/reference/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..62fea7cf70
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/reference/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileset.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/index.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..d154d5c452
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..b1f4b7a9c3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/reference/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..c833830894
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/reference/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/reference/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..5fec1f180d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/reference/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..b8952f45a8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/reference/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/log.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/max.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..76a9d70309
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/reference/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/min.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..b258366ca5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/reference/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..51aa325172
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/chomp.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..50c8d79546
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/format.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..65c15530bf
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/reference/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/reference/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..c634b1e33a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/reference/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/indent.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/join.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..7202e32800
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/reference/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/lower.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..7044b162a3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/reference/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/reference/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..42c7e20a5b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/reference/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/replace.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..214fa4bd6d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/reference/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/split.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..4e5879dc82
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/reference/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strlen.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strrev.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..ee395b34ca
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/reference/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/substr.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/title.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..94768462fa
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/reference/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/reference/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trim.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..b17af25f38
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/reference/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/reference/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..587429ca3e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/reference/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/reference/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..39494ef8d2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/reference/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..3b4534b700
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/reference/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/reference/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/upper.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..a95cec5de6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/reference/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/reference/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..e9f81ed79e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/reference/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..0247e8182d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/reference/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://developer.hashicorp.com/nomad/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/reference/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/index.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/index.mdx
new file mode 100644
index 0000000000..5bc7273a4a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/index.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: Hashicorp Configuration Language (HCL) reference
+description: |-
+  This section contains reference material for the Hashicorp Configuration Language (HCL) as it relates to defining a Nomad job specifications. Learn about HCL syntax elements such as arguments, blocks, and expressions. Review heredoc string support and how to format decimals.
+---
+
+# Hashicorp Configuration Language (HCL) reference
+
+Define your job specification with the Hashicorp Configuration Language (HCL),
+which is a syntax specifically designed for building structured configuration
+formats. Refer to the [HCL GitHub repository](https://github.com/hashicorp/hcl)
+to learn more about HCL.
+
+## Parsing context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The
+HCL parser's JSON format is unspecified, so the API format is preferred. You can
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/commands/job/run#json
+
+## Arguments, bocks, and expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/reference/hcl2/syntax)
+- [Expressions](/nomad/docs/reference/hcl2/expressions)
+
+### Blocks
+
+Block syntax is as follows, using unquoted attributes and quoted values:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/job-declare/task-driver/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/job-declare/task-driver/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/job-declare/task-driver/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "heredoc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL.
+
+### Decimals
+
+HCL requires a leading zero for decimal values lower than 1 (e.g. `0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/locals.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/locals.mdx
new file mode 100644
index 0000000000..4c6c026625
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: HCL locals reference
+description: |-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# HCL locals reference
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/reference/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/syntax.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/syntax.mdx
new file mode 100644
index 0000000000..342e1eec00
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: HCL syntax reference
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL syntax reference
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/reference/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.10.x/content/docs/reference/hcl2/variables.mdx b/content/nomad/v1.10.x/content/docs/reference/hcl2/variables.mdx
new file mode 100644
index 0000000000..bc0f5e086e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: HCL input variables reference
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# HCL input variables reference
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/reference/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/reference/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/reference/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/reference/runtime-environment-settings
+[expression]: /nomad/docs/reference/hcl2/expressions
diff --git a/content/nomad/v1.10.x/content/docs/reference/keyboard-commands.mdx b/content/nomad/v1.10.x/content/docs/reference/keyboard-commands.mdx
new file mode 100644
index 0000000000..835c170d1b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/keyboard-commands.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Keyboard commands reference
+description: |-
+  This page contains reference information for the available keyboard shortcut commands in the Nomad web UI.
+---
+
+# Web UI keyboard commands reference
+
+The Nomad Web UI supports keyboard shortcut commands to help you navigate and
+operate Nomad. You can use keyboard commands to inspect jobs, view logs,
+monitor evaluations, and more.
+
+## Open the shortcuts panel
+
+Type a question mark (`?`) on any web UI page to display the
+**Keyboard Shortcuts** panel. The available shortcuts and their corresponding
+commands are shown in the table below. To use commands with two letters
+separated by a space, type the letters one after the other.
+
+|Shortcut|Keyboard command|
+|---|---|
+|Go to the **Jobs** page|`g j`|
+|Go to the **Storage** page|`g r`|
+|Go to the **Variables** page|`g v`|
+|Go to the **Servers** page|`g s`|
+|Go to the **Clients** page|`g c`|
+|Go to the **Topology** page|`g t`|
+|Go to the **Evaluations** page|`g e`|
+|Go to the **Profile** page|`g p`|
+|Go to the **Administration** page|`g a`|
+|Next Subnav|`Shift + right arrow`|
+|Previous Subnav|`Shift + left arrow`|
+|Previous Main Section|`Shift + up arrow`|
+|Next Main Section|`Shift + down arrow`|
+|Show Keyboard Shortcuts|`?`|
+|Hide Keyboard Shortcuts|`Escape key`|
+
+## Toggle shortcut tooltip hints
+
+Hold the `Shift` key on any page in the web UI to overlay inline tooltip hints.
+Tooltips are contextual and will only show certain hints when applicable.
+
+## Disable shortcuts
+
+1. Open the **Keyboard Shortcuts** panel.
+1. At the bottom of the panel, click on the toggle next to the
+**Keyboard shortcuts enabled** option.
+
+## Re-bind shortcuts
+
+You can re-bind a shortcut with the following steps:
+
+1. Open the **Keyboard Shortcuts** panel.
+1. Click on the key combination next to the shortcut that you want to re-bind.
+1. Type the new key combination.
+
+To reset the key combination, click on the red **reset to default** text next
+to the key combination that you want to reset.
+
+## Traverse lists quickly
+
+The web UI has pages that display a lot of data in list form. To navigate to a
+specific item in the list, hold the `Shift` key and type the corresponding
+number in the tooltip hint next to the item that you want to navigate to. Note
+that items with a single digit require a leading zero (0).
\ No newline at end of file
diff --git a/content/nomad/v1.10.x/content/docs/reference/metrics.mdx b/content/nomad/v1.10.x/content/docs/reference/metrics.mdx
new file mode 100644
index 0000000000..dd5b0728f5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/metrics.mdx
@@ -0,0 +1,548 @@
+---
+layout: docs
+page_title: Metrics reference
+description: |-
+  This page contains reference information on the gauge, counter, and timer runtime metrics data that Nomad collects. Use the metrics endpoint to access the metrics data. Learn about the key metrics for monitoring your cluster. Review client, host, allocation, job summary, job status, server, Raft BoltDB, and agent metrics fields.
+---
+
+# Metrics reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------|
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.wait_time`               | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                                                                            | ms / Evaluation Wait           | Timer   |
+| `nomad.nomad.broker.process_time`            | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                                                                            | ms / Evaluation Process        | Timer   |
+| `nomad.nomad.broker.response_time`           | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                                                                                   | ms / Evaluation Response       | Timer   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/periodic) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.pending`              | Number of tasks pending                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.running`              | Number of tasks running                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.dead`                 | Number of tasks dead                                                                 | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+### Client hook metrics
+
+Nomad will emit metrics allowing you to monitor and alert on allocation and task hook performance.
+If you do not need these, they can be disabled via the [`disable_allocation_hook_metrics`][]
+configuration parameter.
+
+| Metric                                    | Description                                           | Unit         | Type    | Labels                                                      |
+|-------------------------------------------|-------------------------------------------------------|--------------|---------|-------------------------------------------------------------|
+| `nomad.client.alloc_hook.prerun.failed`   | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.success`  | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.elapsed`  | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.failed`  | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.success` | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.elapsed` | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+
+## Allocation metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job summary metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job status metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                                  | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                               | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                             | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                       | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                         | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                          | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                            | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                             | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                            | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                         | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                           | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                         | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                       | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                         | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                                | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                           | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                          | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                                | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                                | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`           | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                         | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class, node_pool                            |
+| `nomad.nomad.blocked_evals.memory`                      | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class, node_pool                            |
+| `nomad.nomad.blocked_evals.job.cpu`                     | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`                  | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`               | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`               | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`           | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                        | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                      | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                       | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.process_time`                       | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                 | ms / Evaluation Process  | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.response_time`                      | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                        | ms / Evaluation Response | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.service_ready`                      | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                    | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                       | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                     | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                        | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                      | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.wait_time`                          | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                 | ms / Evaluation Wait     | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.client.batch_deregister`                   | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                         | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                    | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`                 | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                        | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                           | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                         | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`                  | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                           | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                               | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                           | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                              | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                       | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                       | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`                 | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                      | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all`    | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`        | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`                | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`                 | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`                  | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`       | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`       | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`     | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`             | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                    | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                         | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                           | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`                 | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                           | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                          | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                        | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                           | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                            | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`               | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                        | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                                  | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                          | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                               | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                              | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                             | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                                 | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                                 | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                                 | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                              | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                               | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                          | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                          | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                          | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                        | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                   | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`       | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`               | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`               | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`             | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`                | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`                | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`               | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`          | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`                | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`           | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`             | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`         | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`               | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`            | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`        | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                   | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_version_tag`                 | Time elapsed to apply `ApplyJobVersionTag` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`                | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`                | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`                | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`                | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                    | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`                | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                             | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`                  | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`                 | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`               | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                          | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                           | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                        | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                       | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`                | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`             | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                     | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`               | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                    | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                               | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                          | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                         | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                           | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                    | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`                  | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                    | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`                 | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                           | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                      | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                           | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                            | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                              | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                              | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                           | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                      | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                               | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                     | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                                  | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                                  | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                              | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                                | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                          | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                                 | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                                | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                              | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`               | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                            | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                    | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                          | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`               | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                   | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`                  | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`                  | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`               | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                            | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                       | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                      | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                   | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`               | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`               | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                            | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                                | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                             | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                        | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`         | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                          | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                               | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                       | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                             | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                                | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                               | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.quota.utilization.cpu`                     | Utilization of the CPU quota                                                                                                                           | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.cores`                   | Utilization of the CPU Cores quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.memory_mb`               | Utilization of the Memory MB quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.storage.host_volumes_mb` | Utilization of the Host Volumes MB quota                                                                                                               | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.storage.variables_mb`    | Utilization of the Variables MB quota                                                                                                                  | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.scaling.get_policy`                        | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                     | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                      | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                        | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`          | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                        | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                        | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                               | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                       | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`                  | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`                  | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                           | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`      | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                              | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                         | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                                | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                               | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                           | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                          | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                        | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                       | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`            | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                           | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                        | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                        | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                     | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                               | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                    | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                              | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                                 | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                                  | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                                | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                                  | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                         | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                     | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`                  | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                            | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                             | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                               | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`               | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`            | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                              | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                             | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                               | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                       | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                           | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                                | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                               | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                                | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`          | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`              | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`         | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                             | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                        | Description                                            | Unit    | Type    | Labels |
+|-----------------------------------------------|--------------------------------------------------------|---------|---------|--------|
+| `nomad.agent.http.exceeded`                   | Count of HTTP connections exceeding concurrency limit  | Integer | Counter | -      |
+| `nomad.client.consul.check_deregistrations`   | Number of Consul check deregistration operations       | Integer | Counter | host   |
+| `nomad.client.consul.check_registrations`     | Number of Consul check registration operations         | Integer | Counter | host   |
+| `nomad.client.consul.checks`                  | Number of Consul checks currently registered           | Integer | Gauge   | host   |
+| `nomad.client.consul.service_deregistrations` | Number of Consul service deregistration operations     | Integer | Counter | host   |
+| `nomad.client.consul.service_registrations`   | Number of Consul service registration operations       | Integer | Counter | host   |
+| `nomad.client.consul.services`                | Number of Consul services currently registered         | Integer | Gauge   | host   |
+| `nomad.client.consul.sync_failure`            | Number of failed attempts to sync services with Consul | Integer | Counter | host   |
+
+[tagged-metrics]: /nomad/docs/reference/metrics#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://developer.hashicorp.com/nomad/s/port-plan-failure
+[`disable_allocation_hook_metrics`]: /nomad/docs/configuration/telemetry#disable_allocation_hook_metrics
diff --git a/content/nomad/v1.10.x/content/docs/reference/runtime-environment-settings.mdx b/content/nomad/v1.10.x/content/docs/reference/runtime-environment-settings.mdx
new file mode 100644
index 0000000000..4d35a2f36a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/runtime-environment-settings.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: Runtime environment settings
+description: Nomad provides runtime environment variables that you can use in your workloads. Learn about task identifiers, CPU and memory resources, IP addresses, task directories, and host variables. Review job, network, and Consul variables. Supply arbitrary configuration to a job task.
+---
+
+# Runtime Environment Settings
+
+This page provides reference information for runtime environment settings in
+your Nomad job specification. Learn about task identifiers, CPU and memory
+resources, IP addresses, task directories, and host variables. Review job,
+network, and Consul variables. Supply arbitrary configuration to a job task.
+
+## Introduction
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Variables Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta block for arbitrary configuration
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Both the original case and an uppercased
+version are injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks
+when using the `exec`, `raw_exec`, and `java` task drivers. Nomad also modifies
+`HOME`, `USER`, and `LOGNAME` variables for tasks that have the `user` parameter
+set, to reflect the set username. The variables that are passed to the tasks can
+be controlled using the client configuration [`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.10.x/content/docs/reference/runtime-variable-interpolation.mdx b/content/nomad/v1.10.x/content/docs/reference/runtime-variable-interpolation.mdx
new file mode 100644
index 0000000000..bc79e08815
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/runtime-variable-interpolation.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: Runtime variable interpolation
+description: Nomad supports interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review job, network, and Consul environment variables.
+---
+
+# Variable Interpolation
+
+This page provides reference information on interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review Review job, network, and Consul environment variables.
+
+## Introduction
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/job-declare/task-driver/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/job-declare/task-driver/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/job-declare/task-driver) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.10.x/content/docs/reference/sentinel-policy.mdx b/content/nomad/v1.10.x/content/docs/reference/sentinel-policy.mdx
new file mode 100644
index 0000000000..e55a446059
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/reference/sentinel-policy.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: Sentinel policy reference
+description: >-
+  Use the Nomad Enterprise Sentinel policy feature to implement fine-grained control over jobs, such as restricting when jobs can run or ensuring jobs use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+---
+
+# Sentinel Policy Reference
+
+<EnterpriseAlert product="nomad" />
+
+This page provides reference information on using the Nomad Sentinel policy feature to implement fine-grained policies such as restricting when jobs can run or ensuring job use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+
+## Introduction to Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+Refer to the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`][]
+subcommands.
+
+## Sentinel Policy Structure
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies. Nomad supports a `submit-job` scope for registering jobs,
+and a `submit-host-volume` scope for creating or updating dynamic host volumes.
+
+### submit-job scope
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  is always non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+### submit-host-volume scope
+
+The following top-level objects are available to policies in the
+`submit-host-volume` scope automatically, without an explicit import.
+
+* `volume`: the submitted volume. This is a [Sentinel Dynamic Host Volume
+  Object](#sentinel-dynamic-host-volume-objects).
+* `existing_volume`: the previous version of the volume. If `volume_exists` is
+  true, this is always non-nil. This is also a [Sentinel Dynamic Host
+  Volume Object](#sentinel-dynamic-host-volume-objects). `volume_exists`: a
+  boolean field that indicates that a previous version of the volume exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+* `node`: the node the volume has been placed on. This is a [Sentinel Node
+  Object](#sentinel-node-objects).
+* `node_pool`: the node pool of the node the volume has been placed on. This is
+  a [Sentinel Node Pool Object](#sentinel-node-pool-objects).
+
+### submit-csi-volume scope
+
+The following top-level objects are available to policies in the
+`submit-csi-volume` scope automatically, without an explicit import.
+
+- `volume`: the submitted volume. This is a [Sentinel CSI Volume
+  Object](#sentinel-csi-volume-objects).
+- `existing_volume`: the previous version of the volume. If `volume_exists` is
+  true, this is always non-nil. This is also a [Sentinel CSI Volume
+  Object](#sentinel-csi-volume-objects). 
+- `volume_exists`: a boolean field that indicates that a previous version of the
+  volume exists.
+- `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+- `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+## Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+## Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+## Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+## Sentinel Node Objects
+
+The `node` object maps to the [Node][], with the fields converted to the
+Sentinel convention. Here are some examples:
+
+| Node Field         | Sentinel Accessor  |
+|--------------------|--------------------|
+| `node.Class`       | `node.class`       |
+| `node.Meta["foo"]` | `node.meta["foo"]` |
+
+## Sentinel Node Pool Objects
+
+The `node_pool` object maps to the [Node Pool][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Node Pool Field                                       | Sentinel Accessor                                       |
+|-------------------------------------------------------|---------------------------------------------------------|
+| `node_pool.Description`                               | `node_pool.description`                                 |
+| `node_pool.SchedulerConfiguration.SchedulerAlgorithm` | `node_pool.scheduler_configuration.scheduler_algorithm` |
+
+## Sentinel Dynamic Host Volume Objects
+
+The `volume` object maps to the [Dynamic Host Volume][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Dynamic Host Volume Field                    | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `volume.Name`                                | `volume.name`                                  |
+| `volume.RequestedCapabilities[0].AccessMode` | `volume.requested_capabilities[0].access_mode` |
+
+## Sentinel CSI Volume Objects
+
+The `volume` object maps to the [CSI Volume][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| CSI Volume Field                             | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `volume.Name`                                | `volume.name`                                  |
+| `volume.RequestedCapabilities[0].AccessMode` | `volume.requested_capabilities[0].access_mode` |
+
+Note that the `volume.Secrets` values and `volume.MountOptions.MountFlags` are always redacted to prevent credential leaks.
+
+
+[Nomad Sentinel Tutorial]: /nomad/docs/govern/sentinel
+[`nomad sentinel`]: /nomad/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L13502-L13531
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L5578-L5610
+[Node]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L2086-L2210
+[Node Pool]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/node_pool.go#L46-L68
+[Dynamic Host Volume]: https://github.com/hashicorp/nomad/blob/main/nomad/structs/host_volumes.go#L18-L87
+[CSI Volume]: https://github.com/hashicorp/nomad/blob/main/nomad/structs/csi.go#L249-L312 
diff --git a/content/nomad/v1.10.x/content/docs/release-notes/index.mdx b/content/nomad/v1.10.x/content/docs/release-notes/index.mdx
new file mode 100644
index 0000000000..67d880152e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/release-notes/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Release Notes
+description: |-
+  Hashicorp Nomad release notes.
+---
+
+# Release Notes
+
+Choose a version from the navigation sidebar to view the release notes for Nomad.
+
+Documentation for maintenance releases (e.g., 0.1.x) is on the bottom of each
+release notes page.
diff --git a/content/nomad/v1.10.x/content/docs/release-notes/nomad/upcoming.mdx b/content/nomad/v1.10.x/content/docs/release-notes/nomad/upcoming.mdx
new file mode 100644
index 0000000000..ba5169b095
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/release-notes/nomad/upcoming.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Upcoming
+description: >-
+  Review upcoming HashiCorp Nomad release changes.
+---
+
+# Upcoming
+
+Nomad strives to be backward compatible for at least 2 major releases, so for
+example, you can upgrade Nomad v1.6.x to Nomad v1.8.x. In addition, Enterprise
+customers have access to [Long Term Support (LTS)][LTS] releases.
+
+Refer to [Upgrading][] for details of the upgrade process, and [Upgrade
+Guides][] for notes on upgrading specific versions.
+
+However, from time to time it's necessary to make backwards _incompatible_
+changes to Nomad. We announce these on [changelog][], the [Release Notes][], and
+the version-specific [Upgrade Guides][]. In order to help you plan your
+upgrades, this page maintains a list of all planned future changes that might
+cause backwards incompatibilities or require operational changes. It's possible
+that a given change may happen later than intended, at which point we update
+this document. However, we do not move changes earlier than originally published
+unless there's a required change due to a security vulnerability.
+
+## Nomad 1.9.0
+
+* Nomad will remove support for HCL1 job specifications and the `-hcl1` flag on
+  the `nomad job run` and other commands. Refer to [GH-20195][] for more details.
+* Nomad will remove the [`tls_prefer_server_cipher_suites`][] agent configuration.
+* Nomad will remove support for Nomad client agents older than 1.6.0. Older
+  nodes will fail heartbeats. Nomad servers will mark the workloads on those
+  nodes as lost and reschedule them normally according to the job's
+  [`reschedule`][] block.
+
+## Nomad 1.10.0 LTS
+
+Nomad 1.10.0 is a Long-Term Support release for Enterprise customers.
+
+* Nomad will remove support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the integration
+  guide][consul-integration] for details.
+* Nomad will remove support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the integration guide][vault-integration] for
+  details.
+* Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+* Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+* Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+[LTS]: /nomad/docs/enterprise#long-term-support-lts-releases
+[Upgrading]: /nomad/docs/upgrade
+[Upgrade Guides]: /nomad/docs/upgrade/upgrade-specific
+[changelog]: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md
+[Release Notes]: /nomad/docs/release-notes
+[GH-20195]: https://github.com/hashicorp/nomad/issues/20195
+[`tls_prefer_server_cipher_suites`]: /nomad/docs/configuration/tls#tls_prefer_server_cipher_suites
+[consul-integration]: /nomad/docs/secure/acl/consul
+[vault-integration]: /nomad/docs/secure/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/job-specification/disconnect
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1-10-x.mdx b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1-10-x.mdx
new file mode 100644
index 0000000000..bb3d92560c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1-10-x.mdx
@@ -0,0 +1,508 @@
+---
+layout: docs
+page_title: Nomad v1.10.x release notes
+description: >-
+  HashiCorp Nomad version 1.10.x release notes. New features include dynamic host volumes, OIDC Private Key JWT (client assertions), and OIDC Proof Key for Code Exchange (PKCE). Updates to the Container Storage Interface (CSI) volume delete and volume status commands. CSI volume and plugin events added to the event stream. Added UI URL hints to the end of common CLI commands and a -ui flag to auto-open them in a browser.
+---
+
+# Nomad 1.10.x release notes
+
+We are pleased to announce the following Nomad updates.
+
+## 1.10.5 release highlights
+
+### Windows OS enhancements
+
+- Configure Nomad agents to write to the Windows Event Log. Refer to the agent
+  configuration's [`eventlog` parameter](/nomad/docs/configuration#eventlog) for
+  details.
+- Use CLI commands to install and uninstall Nomad as a system service. Refer to
+  the following for more information:
+
+    - [`nomad windows service install` command reference](/nomad/commands/windows/service-install)
+    - [`nomad windows service uninstall` command reference](/nomad/commands/windows/service-uninstall)
+
+
+### Keyring configuration validation
+
+On agent startup, Nomad validates [the keyring configuration type](/nomad/docs/configuration/keyring) against supported values.
+
+### Scheduling performance improvement
+
+We improved scheduling performance when checking reserved ports usage.
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.5)
+for a list of bug and security fixes.
+
+## 1.10.4 release highlights
+
+### Nomad logs and journald output
+
+We have added functionality that enables you to retrieve journald output or the
+contents of the Nomad log file remotely using the CLI.
+
+#### New monitor export command
+
+For a given Nomad agent, this command retrieves journald logs or the
+entire contents of the Nomad log file. Review the [`monitor export` command
+reference](/nomad/commands/monitor/export) for usage, options, and examples.
+
+#### Historical log capture for debugging
+
+We added the following flags to the `nomad operator debug` command:
+
+- [`-log-lookback`](/nomad/commands/operator/debug#log-lookback): Include
+  historical journald logs in the debug capture.
+- [`-log-file-export`](/nomad/commands/operator/debug#log-file-export): Include
+  Nomad agents' logfiles in the debug capture.
+
+Refer to the [`nomad operator debug` command
+reference](/nomad/commands/operator/debug) for details.
+
+### Blocked evaluation metrics
+
+The `nomad.nomad.blocked_evals.cpu` and `nomad.nomad.blocked_evals.memory`
+server metrics now have a `node_pool` label. This helps you determine the node
+pool where a scaling operation is needed.
+
+Review the [server metrics in the Metrics reference](/nomad/docs/reference/metrics#server-metrics).
+
+### Sentinel policy scope for CSI volumes <EnterpriseAlert inline />
+
+We added a new `submit-csi-volume` Sentinel policy scope, which lets you apply
+Sentinel policies to CSI volume creation and registration.
+
+You may override `soft-mandatory` polices assigned to CSI volume creation and
+registration, but you may not override `hard-mandatory` policies. Refer to the
+[`EnforcementLevel`
+parameter](/nomad/api-docs/sentinel-policies#enforcementlevel) in the Sentinel
+Policies API for `soft-mandatory` and `hard-mandatory` definitions.
+
+Refer to the following documentation:
+
+- Sentinel policy reference
+
+  - [submit-csi-volume
+    scope](/nomad/docs/reference/sentinel-policy#submit-csi-volume-scope)
+  - [Sentinel CSI Volume
+    Objects](/nomad/docs/reference/sentinel-policy#sentinel-csi-volume-objects)
+
+- Volumes API reference
+
+  - [Register CSI Volume](/nomad/api-docs/volumes#register-csi-volume)
+  - [Create CSI Volume](/nomad/api-docs/volumes#create-csi-volume)
+
+- CLI command reference
+
+  - [`sentinel apply -scope "submit-csi-volume"`](/nomad/commands/sentinel/apply#scope)
+  - [`volume create -policy-override` option](/nomad/commands/volume/create#policy-override)
+  - [`volume register -policy-override` option](/nomad/commands/volume/register#policy-override)
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.4) for a list of bug fixes.
+
+## 1.10.3 release highlights
+
+### Consul service registrations
+
+We added the `kind` parameter to the `service` block in the job specification.
+You may manually register a Consul service by specifying a Consul service
+kind. Refer to the Consul Register Service HTTP API's [Kind
+parameter](/consul/api-docs/agent/service#kind) for a list of Consul service
+Kind values.
+
+Previously, you configured a Consul service mesh in your job specification's
+`gateway` block. Now you may specify the kind of Consul service in the job
+specification service itself. If you configure both a service kind and a
+gateway in your job specification, the configured Consul service mesh gateway
+takes precedence.
+
+Refer to the [job specification `service` block `kind`
+parameter](/nomad/docs/job-specification/service#kind) for details.
+
+### Docker task driver cgroup namespace support
+
+You may specify the cgroup namespace in your job specification's Docker task
+driver configuration. This lets you run services that require a cgroup
+namespace, such as the Datadog Agent.
+
+Refer to the Docker task driver's [`cgroupns`
+parameter](/nomad/docs/job-declare/task-driver/docker#cgroupns) for details.
+
+### NOMAD_UNIX_ADDR task environment variable
+
+Use the `NOMAD_UNIX_ADDR` value as your `NOMAD_ADDR` when you want to use the
+Nomad CLI with the [task API's](/nomad/api-docs/task-api) Unix socket.
+
+This example sets the `NOMAD_ADDR` to the `NOMAD_UNIX_ADDR` environment
+variable.
+
+```hcl
+task "nomad-cli" {
+  driver = "raw_exec"
+  config { ... run `nomad` commands ... }
+  identity {
+    env = true
+  }
+  env {
+    NOMAD_ADDR = "${NOMAD_UNIX_ADDR}"
+  }
+}
+```
+
+Refer to these resources for details:
+
+- [Nomad CLI environment variables](/nomad/commands#environment-variables)
+- Runtime environment settings [job-related
+  variables](/nomad/docs/reference/runtime-environment-settings#job-related-variables)
+- Runtime variable interpolation [job-related
+  variables](/nomad/docs/reference/runtime-variable-interpolation#job-related-variables)
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.3)
+for a list of bug fixes.
+
+## 1.10.2 release highlights
+
+### Start stopped jobs
+
+The `nomad job start` CLI command starts a stopped job. This differs from the
+`nomad job restart` command, which restarts or reschedules allocations for a
+running job.
+
+Refer to the [`nomad job start` command reference](/nomad/commands/job/start)
+for details.
+
+### Dynamic host volumes garbage collection enhancements
+
+When a node is garbage collected, any dynamic host volumes on the node are
+orphaned in the state store. You generally don't want to automatically collect
+these volumes and risk data loss, so we enhanced garbage collection to let you
+delete orphaned dynamic host volumes.
+
+We added the `-force` flag to the `nomad volume delete` command so that you can
+delete the volume if the node has been garbage collected. Refer to the [`nomad
+volume delete` command reference](/nomad/commands/volume/delete#force) for details.
+
+For clusters running on ephemeral cloud instances, such as AWS
+EC2 in an autoscaling group, deleting host volumes may add excessive friction.
+The `gc_volumes_on_node_gc` client configuration parameter specifies that the
+server should delete any dynamic host volumes on the node when garbage
+collection deletes the node. Refer to the [`gc_volumes_on_node_gc` parameter
+definition](/nomad/docs/configuration/client#gc_volumes_on_node_gc) for details.
+
+### Configure max number of allocations
+
+The `node_max_allocs` parameter sets the maximum number of allocations that
+Nomad may schedule on a client node. Refer to the [`node_max_allocs` parameter
+definition](/nomad/docs/configuration/client#node_max_allocs) for details.
+
+### ACL policy with workload identity enhancements
+
+- Apply an ACL policy to a namespace.
+
+  When you apply an ACL policy to a namespace, Nomad applies the policy to all
+  the jobs within the namespace. Refer to the [workload-associated ACL policies
+  documentation](/nomad/docs/concepts/workload-identity#workload-associated-acl-policies)
+  for details.
+- Find the ACL policies associated with the current workload identity or ACL
+  token.
+
+  This enhancement lets you learn about ACL capabilities from within the
+  workload identity tasks.  Refer to the following resources for details:
+
+  - ACL Polices HTTP API [Read Self Policy
+    endpoint](/nomad/api-docs/acl/policies#read-self-policy)
+  - `nomad acl policy self` [command reference](/nomad/commands/acl/policy/self)
+  - `nomad acl token self` [command reference](/nomad/commands/acl/token/self)
+
+### Normalize IPv6 addresses
+
+Apply [RFC-5942 section 4
+recommendations](https://www.rfc-editor.org/rfc/rfc5952.html#section-4) to IPv6
+addresses. Nomad normalizes the addresses when it parses the configuration file
+so that the change runs through the whole system.
+
+### Option to render a job specification template only once
+
+We added `once` mode to the `template` block. This allows templates to render
+once without watching dependencies. Refer to the following resources for more
+information:
+
+- Consul Template Modes [Once
+  Mode](/consul/docs/automate/consul-template/mode#once-mode) for a thorough
+  description.
+- Job specification `template` block's [`once`
+  parameter](/nomad/docs/job-specification/template#once) for Nomad behavioral
+  changes.
+
+### Offline utilization reporting <EnterpriseAlert inline/>
+
+With this enhancement, Nomad periodically records usage metrics
+snapshots in the state store. Cluster administrators in air-gapped or otherwise
+secured environments may use the API or CLI to generate utilization reporting
+bundles from those usage metrics snapshots.
+
+Refer to the following resources:
+
+- The [Operator Utilization HTTP API](/nomad/api-docs/operator/utilization)
+- The [`nomad operator utilization` command
+  reference](/nomad/commands/operator/utilization)
+- The agent configuration `reporting` block's [`snapshot_retention_time`
+  parameter](/nomad/docs/configuration/reporting#snapshot_retention_time)
+
+### Breaking changes
+
+In templates, we removed support for these non-hermetic Sprig functions:
+`sprig_date`, `sprig_dateInZone`, `sprig_dateModify`, `sprig_htmlDate`,
+`sprig_htmlDateInZone`, `sprig_dateInZone`, `sprig_dateModify`,
+`sprig_randAlphaNum`, `sprig_randAlpha`, `sprig_randAscii`, `sprig_randNumeric`,
+`sprig_randBytes`, `sprig_uuidv4`, `sprig_env`, `sprig_expandenv`, and
+`sprig_getHostByName`.
+
+The aforementioned Sprig functions posed a security risk in that they allowed
+reading environment variables or resolving domain names to IP addresses.
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.2)
+for a list of security and bug fixes.
+
+### Upgrade details
+
+Review the [Nomad 1.10.2 upgrade guide](/nomad/docs/upgrade/upgrade-specific#nomad-1-10-2).
+
+## 1.10.1 release highlights
+
+### Override parameterized job's parent priority
+
+Use the `-priority` flag to override the priority inherited from a parameterized
+job's parent. Refer to the `nomad job dispatch` command's [`-priority`
+parameter](/nomad/commands/job/dispatch#priority) for details.
+
+### Breaking changes
+
+@include 'release-notes/v1-10-1/breaking-raft-peer.mdx'
+
+@include 'release-notes/v1-10-1/breaking-agent-exit.mdx'
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.1)
+for a list of security and bug fixes.
+
+### Upgrade details
+
+Review the [Nomad 1.10.1 upgrade guide](/nomad/docs/upgrade/upgrade-specific#nomad-1-10-1).
+
+## 1.10.0 release highlights
+
+### Dynamic host volumes
+
+The dynamic host volumes feature brings a persistent storage option to your
+workload allocations.
+
+Nomad dynamic host volumes manage storage for stateful workloads without
+requiring a restart of the Nomad nodes to apply configuration changes. You
+create dynamic host volumes via the CLI or API and then configure the job with
+the [`volume`](/nomad/docs/job-specification/volume) and
+[`volume_mount`](/nomad/docs/job-specification/volume_mount) blocks in the job
+specification.
+
+Host volumes mount paths from the Nomad client into allocations. Nomad is aware
+of host volume availability and makes use of it for job scheduling. However,
+Nomad does not know about the volume's underlying characteristics, so you can
+use host volumes for both local persistent storage and for highly
+available networked storage.
+
+#### Dynamic host volume governance <EnterpriseAlert inline product="nomad"/>
+
+Providing guardrails to platform consumers is an important aspect of the storage
+provisioning workflow when leveraging host volumes across a shared Nomad
+cluster.  Nomad Enterprise supports these new capabilities to provide
+governance when provisioning host volumes:
+
+- **Sentinel dynamic host volume objects**
+
+  During volume creation, Nomad can evaluate all of the details within the
+  dynamic host volume specification against Sentinel policies
+  that define and enforce specific patterns.
+
+  For example, a policy that enforces the storage tier based on the environment
+  or namespace specified would allow reserving more expensive NVME storage for
+  specific workloads. Being able to apply policy to the volume specification
+  gives you a method to enforce specific patterns while providing platform
+  consumers with more flexibility around self-service volume provisioning. Refer
+  to the [Sentinel policy reference](/nomad/docs/reference/sentinel-policy#sentinel-dynamic-host-volume-objects) for more information.
+
+- **Resource quota support**
+
+  Nomad’s resource quota system now includes coverage for host volume capacity
+  limits that you can apply to provisioned storage within a specific namespace.
+  This helps control storage consumption within a namespace based on the maximum
+  capacities defined during creation or when making updates to the maximum
+  capacities over the lifecycle of the volume. Refer to the [Resource quota
+  specification](/nomad/docs/other-specifications/quota) for more information.
+
+- **Namespace and node pool validation**:
+
+  Dynamic host volumes live within the context of a specific namespace when
+  created. When Nomad provisions volumes in a namespace targeting a specific
+  node pool, Nomad evaluates the namespace node pool configuration to ensure
+  that volume creation aligns with job placement rules for node pools. Refer to
+  the [Namespace specification](/nomad/docs/other-specifications/namespace) for
+  details on `node_pool_config` parameters.
+
+#### Resources
+
+Refer to the following resources to learn more about dynamic host volumes:
+
+- [Host volumes section](/nomad/docs/architecture/storage/stateful-workloads#host-volumes)
+  in the _Considerations for stateful workloads_ guide for an overview and
+  comparison of storage options
+- [Host volumes plugin
+  specification](/nomad/docs/architecture/storage/host-volumes) for examples
+  of how to write your own plugin to dynamically configure persistent storage on
+  your Nomad client nodes
+- [Use Nomad dynamic host volumes to persist data for stateful workloads
+  tutorial](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+  to learn how to create and use a dynamic host volume for persistent storage
+
+### OpenID Connect (OIDC) enhancements
+
+Nomad 1.10 extends Nomad's OIDC SSO login feature with [Private Key JWT][pkjwt]
+and [Proof Key for Code Exchange (PKCE)][pkce].
+
+#### Private Key JWT
+
+Private Key JWT, also called client assertions, is a more secure alternative for
+client secrets. Instead of sending a simple secret, Nomad builds a JWT and signs
+it with a value that the OIDC provider verifies. In this approach, Nomad asserts
+a valid OIDC client without sending any secret information over the network.
+
+#### Proof Key for Code Exchange (PKCE)
+
+PKCE adds an extra layer of security to any OIDC auth method for both client
+secrets and client assertions.
+
+Set the [ACL auth method `OIDCEnablePKCE`
+parameter](/nomad/api-docs/acl/auth-methods#oidcenablepkce) to `true` to turn
+on this extra security.
+
+Note that not all OIDC providers support PKCE. In addition to enabling PKCE in
+Nomad, you may need to enable it in your OIDC provider's configuration.
+
+#### Resources
+
+- [OIDC auth method guide][oidc-concepts] for details on using OIDC with Nomad
+- [OIDC troubleshooting guide][oidc-trouble] to review common issues and tips
+  for setting up OIDC
+- [Authenticate users with SSO and Keycloak tutorial][oidc-tutorial] to
+  configure Nomad and the Keycloak identity provider to automatically grant
+  permissions in Nomad ACL.
+
+### Container Storage Interface (CSI) enhancements
+
+We added the following:
+
+- CSI volume and plugin events to the event stream
+- Volume capabilities to the `nomad volume status` command output
+- The ability to use a volume ID prefix search and wildcard namespace with the
+  [`nomad volume delete` command](/nomad/commands/volume/delete). Refer to
+  the [GitHub pull request](https://github.com/hashicorp/nomad/pull/24997) for
+  details. Example usage:
+
+  ```shell-session
+  $ nomad volume create ./internal-plugin.volume.hcl
+  ==> Created host volume internal-plugin with ID aeea91a0-06df-c16e-5403-ff82a2f28fd4
+  ✓ Host volume "aeea91a0" ready
+
+    2025-01-31T15:55:14-05:00
+    ID        = aeea91a0-06df-c16e-5403-ff82a2f28fd4
+    Name      = internal-plugin
+    Namespace = default
+    Plugin ID = mkdir
+    Node ID   = b4611abd-d4a8-c83a-b05e-7d9f5b44a179
+    Node Pool = default
+    Capacity  = 0 B
+    State     = ready
+    Host Path = /run/nomad/dev/data/host_volumes/aeea91a0-06df-c16e-5403-ff82a2f28fd4
+
+  $ nomad volume delete -type host aeea91a0
+  Successfully deleted volume "aeea91a0-06df-c16e-5403-ff82a2f28fd4"!
+  ```
+
+### UI URL hints added to CLI commands
+
+We added UI URL hints to the end of common CLI commands and a `-ui` flag to
+automatically open the generated link in your browser.
+
+Showing UI URL hints is enabled by default. You have two options for turning off
+this feature:
+
+- Server: Modify the [`show_cli_hints`
+  parameter](/nomad/docs/configuration/ui#show_cli_hints) in your agent's `ui`
+  block configuration.
+- CLI: Set the `NOMAD_CLI_SHOW_HINTS` environment variable to `0` or `false`.
+
+  ```shell-session
+  $ nomad status
+  No running jobs
+
+  ==> View and manage Nomad jobs in the Web UI: https://localhost:4646/ui/jobs
+
+  $ export NOMAD_CLI_SHOW_HINTS=0
+  $ nomad status
+  No running jobs
+  ```
+
+### Breaking changes
+
+@include 'release-notes/v1-10/breaking-go-sdk.mdx'
+
+@include 'release-notes/v1-10/breaking-plugin-dir.mdx'
+
+@include 'release-notes/v1-10/breaking-vault-consul-token.mdx'
+
+@include 'release-notes/v1-10/breaking-consul-template.mdx'
+
+@include 'release-notes/v1-10/breaking-disconnect-fields-removed.mdx'
+
+@include 'release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx'
+
+@include 'release-notes/v1-10/breaking-sentinel-apply.mdx'
+
+@include 'release-notes/v1-10/breaking-affinity-spread.mdx'
+
+### Deprecations
+
+@include 'release-notes/v1-10/deprecate-variable-limits.mdx'
+
+### Upgrade details
+
+For more detailed information, refer to the [upgrade details
+page][upgrade] and the [GitHub releases changelogs][github-releases].
+
+### Known issues
+
+None.
+
+### Changelog
+
+- [v1.10.0](https://github.com/hashicorp/nomad/releases/tag/v1.10.0)
+
+
+[consul-integration]: /nomad/docs/secure/acl/consul
+[vault-integration]: /nomad/docs/secure/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[upgrade]: /nomad/docs/upgrade/upgrade-specific#nomad-1-10-0
+[github-releases]: https://github.com/hashicorp/nomad/releases/
+[pkjwt]: https://oauth.net/private-key-jwt/
+[pkce]: https://oauth.net/2/pkce/
+[oidc-concepts]: /nomad/docs/secure/authentication/oidc#client-assertions
+[oidc-trouble]: /nomad/docs/secure/authentication/oidc#oidc-configuration-troubleshooting
+[oidc-tutorial]: /nomad/docs/secure/authentication/sso-pkce-jwt
diff --git a/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_8_x.mdx b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_8_x.mdx
new file mode 100644
index 0000000000..44c317c83a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_8_x.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: 1.8.x
+description: >-
+  HashiCorp Nomad version 1.8.x release notes. Long term support release. Exec2 task driver beta, transparent proxy support for Consul service mesh, Consul API Gateway for Nomad support, UI jobs page updates, time-based task execution, Sentinel policy management in the UI, nomad-bench.
+---
+
+# Nomad 1.8.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Long Term Support Release (Enterprise):** Nomad 1.8 introduces a [long term
+  support release](/nomad/docs/v1.8.x/enterprise#long-term-support-lts-releases) which
+  provides extended maintenance (two years of critical fixes provided through
+  minor releases and efficient upgrades (support for direct upgrades from one
+  LTS release to the next).
+
+- **Exec2 Task Driver (beta):** The `exec2` driver is used to execute a
+  command for a task. It offers a security model optimized for running
+  'ordinary' processes with very low startup times and minimal overhead in
+  terms of CPU, disk, and memory utilization. The `exec2` driver leverages
+  kernel features such as the Landlock LSM, cgroups v2, and the unshare system
+  utility. Due these enhancements, tasks no longer require leveraging
+  filesystem isolation based on chroot, which provide an enhanced security
+  profile and improved performance for the Nomad operator. Refer to [Exec2 Task
+  Driver](/nomad/plugins/drivers/exec2) for more details.
+
+- **Transparent proxy support for Consul service mesh:** Transparent Proxy
+  introduces a more seamless way of dialing upstream services when Consul service
+  mesh is enabled. Users can configure services to use transparent proxy with a
+  new [`transparent_proxy`](/nomad/docs/v1.8.x/job-specification/transparent_proxy)
+  block. When a service is configured to use transparent proxy, workloads can now dial the
+  service using a virtual IP Consul DNS name.
+
+- **Consul API Gateway for Nomad:** Consul API Gateway on Nomad is now
+  officially supported. A prescriptive job specification on
+  [hashicorp-guides/consul-api-gateway-on-nomad](https://github.com/hashicorp-guides/consul-api-gateway-on-nomad)
+  along with a supporting [tutorial](/nomad/tutorials/integrate-consul/deploy-api-gateway-on-nomad) on
+  how to securely deploy Consul API gateway on Nomad.
+
+- **Re-worked Jobs page in the web UI with live updates:** Within the [Jobs
+  index](/nomad/docs/monitor/inspect-workloads#list-jobs) page Nomad has
+  made a few improvements:
+
+  - **Prioritize showing the current state over historical state for jobs:**
+  Previously, long-garbage-collected allocation placement failures, lost nodes,
+  and other historical representations of job state were shown alongside
+  currently running allocations. In self-healing jobs, this often meant that a
+  healthy job looked like it had failures, when in fact Nomad had replaced or
+  rescheduled those failures. Now, the jobs list tries to show accurate
+  allocation information and meaningful statuses (like "Degraded", or
+  "Recovering") to better illustrate the current state of a job.
+
+  - **Server-side pagination:** For users with many thousands of jobs, the main
+  landing page for the web UI will no longer have a noticeable delay on
+  rendering. Users can control page length and filter paginated jobs
+  appropriately.
+
+  - **Live updates:** Previously, users had to manually refresh
+  the page to see newly created jobs, or to hide jobs that had been stopped and
+  garbage-collected. Now, the jobs list will update in real-time as jobs are
+  created, updated, or removed. Further, any changes to allocations of jobs
+  on-page will be reflected in the status of that job in real-time.
+
+- **Time based task execution (Enterprise) :** Using a CRON-like syntax, operators can now
+  [schedule](/nomad/docs/v1.8.x/job-specification/schedule) when tasks should execute
+  and when they should stop. This provides governance for tasks executed from
+  jobs, and allows operators to easily opt-in or opt-out of a schedule that
+  governs when the task can run through the web based UI or through the [CLI](/nomad/docs/v1.8.x/commands/alloc/pause).
+
+- **Sentinel policy management in the Web UI (Enterprise):** Enterprise users can manage
+  Sentinel policies directly within the Nomad UI. Users can create a Sentinel
+  policy based on a template provided from the UI or create policies directly
+  using an editor for Sentinel policies. Refer to [Sentinel
+  policies](/nomad/docs/govern/sentinel) to learn more about
+  how to use Sentinel within Nomad.
+
+- **nomad-bench:** Nomad now provides a testing framework through
+  [nomad-bench](https://github.com/hashicorp-forge/nomad-bench) which provisions
+  infrastructure used to run tests and benchmarks against Nomad test
+  clusters. The infrastructure consists of Nomad test clusters that each have a
+  set of servers with hundreds or thousands of simulated nodes created using
+  nomad-nodesim. The Nomad server processes are not simulated and are expected
+  to run on their own hosts, mimicking real-world deployments.  Metrics are then
+  gathered from the Nomad servers for use with benchmarking and load testing.
+
+## What's deprecated
+
+- **LXC Task driver:** The [Community LXC Task
+  Driver](/nomad/plugins/drivers/community/lxc) is now deprecated. Official
+  support will be removed and the repo will be archived when Nomad 1.9 is
+  released. Users are encouraged to migrate their workloads to another task
+  driver such as the built-in Docker task [driver](/nomad/docs/v1.8.x/drivers/docker).
+
+- **ECS Task driver:** The remote [ECS Task
+  Driver](/nomad/plugins/drivers/remote/ecs) is
+  now deprecated. Official support will be removed and the repo will be
+  archived when Nomad 1.9 is released. Users are encouraged to migrate their
+  workloads to Amazon ECS or to another Nomad task driver.
+
+- **`stop_after_client_disconnect`, `max_client_disconnect`,
+  `prevent_reschedule_on_lost`:** Nomad 1.8.0 introduces a
+  [disconnect](/nomad/docs/v1.8.x/job-specification/disconnect) block meant to group
+  all the configuration options related to disconnected client's and server's
+  behavior, causing the deprecation of the fields stop_after_client_disconnect,
+  max_client_disconnect and prevent_reschedule_on_lost. This block also
+  introduces new options for allocations reconciliation if the client regains
+  connectivity.
+
+- **32-bit builds**: Support for 32-bit architectures is now deprecated. Nomad
+  releases will no longer include binaries built for 32-bit platforms starting
+  with Nomad 1.9.
+
+## What's removed
+
+- **raw_exec option `no_cgroups`:** In Nomad 1.7.0 the raw_exec plugin option
+  for no_cgroups became ineffective. Starting in Nomad 1.8.0 attempting to set
+  the no_cgroups in raw_exec plugin configuration will result in an error when
+  starting the agent.
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/v1.8.x/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
+
+## Known issues
+
+The following issues are known to exist in the v1.8.x releases:
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.8.0](https://github.com/hashicorp/nomad/releases/tag/v1.8.0)
diff --git a/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_9_x.mdx b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_9_x.mdx
new file mode 100644
index 0000000000..5dd37782bb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/release-notes/nomad/v1_9_x.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 1.9.x
+description: >-
+  HashiCorp Nomad version 1.9.x release notes. Multi-Instance GPU (MIG) support, quotas for device resources, NUMA-aware scheduling, job versions, Virt task driver beta, Exec2 task driver GA, improved IPv6 support.
+---
+
+# Nomad 1.9.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Multi-Instance GPU (MIG) support added to the NVIDIA device driver**: This
+enhances Nomad’s ability to schedule workloads across your NVIDIA hardware and
+make full use of your GPU investment. The device driver automatically detects
+MIGs. Refer to the [NVIDIA driver docs](/nomad/plugins/devices/nvidia) for
+details.
+
+- **Quotas for device resources <EnterpriseAlert inline/>**: This release extends quotas to
+allow limiting [device resources](/nomad/docs/v1.9.x/job-specification/device). Refer
+to [Resource quotas](/nomad/docs/v1.9.x/other-specifications/quota) for configuration details.
+
+- **NUMA awareness for device resources <EnterpriseAlert inline/>**: Nomad is able to
+  correlate CPU cores with memory nodes and assign tasks to run on specific CPU
+  cores so as to minimize any cross-memory node access patterns. With Nomad 1.9,
+  we are expanding this functionality to also correlate
+  [devices](/nomad/docs/v1.9.x/concepts/plugins/devices) to memory nodes and enable
+  NUMA-aware scheduling to take device associativity into account when making
+  scheduling decisions. Refer to [numa
+  Block](/nomad/docs/v1.9.x/job-specification/numa) for configuration details.
+
+- **Golden job versions**: This feature introduces a way to preserve and compare
+  historical versions of a job. Prior to this, any change to a job would push
+  older versions into garbage collection. Now, you can tag a version to save it
+  from garbage collection. Additionally, you can compare job versions by tag
+  name and revert by tag name. Refer to [Job
+  versions](/nomad/docs/v1.9.x/concepts/job.mdx#job-versions) for details and links to
+  how to use job version tagging.
+
+- **Virt task driver (beta)**: The new Virt task driver uses
+  [libvirt](https://libvirt.org/) to manage virtual machines created by KVM,
+  Xen, VMware ESXi, QEMU, and other virtualization technologies. Using this
+  driver, you can perform the following:
+
+  - Start and stop a virtual machine and run a process on it.
+  - Assign a workload identity to the running task inside the virtual machine.
+  - Pass configuration values from Vault or other services using consul-template.
+  - Mount host directories into virtual machines to procure the allocation and task directories inside them.
+  - Configure port forwarding from the Nomad node to the virtual machine.
+  - Access the running task through the task API.
+
+  Refer to the [Virt driver docs](https://github.com/hashicorp/nomad-driver-virt)
+  for installation and usage guides.
+
+- **Exec2 Task Driver (GA):** The `exec2` driver is used to execute a command
+for a task. It offers a security model optimized for running 'ordinary'
+processes with very low startup times and minimal overhead in terms of CPU,
+disk, and memory utilization. The `exec2` driver leverages kernel features such
+as the Landlock LSM, cgroups v2, and the unshare system utility. Due these
+enhancements, tasks no longer require leveraging filesystem isolation based on
+chroot, which provide an enhanced security profile and improved performance for
+the Nomad operator. Refer to [Exec2 Task Driver](/nomad/plugins/drivers/exec2)
+for more details.
+
+- **Improved IPv6 support**: Nomad has improved support for Nomad's IPv6
+capabilities. We have tested and resolved some known issues with
+server-to-server and server-to-client communications. Additionally we have
+tested the Nomad CLI and UI service integrations with Consul and Vault, workload
+identity, service registration, host networking, bridge networking, and the
+Docker driver. More work will likely need to be done with IPv6 support as we
+explore integrations with Consul service mesh.
+
+
+## What's deprecated
+
+The following are deprecated and will be removed in 1.10.
+
+- Support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the Consul integration
+  guide][consul-integration] for details.
+- Support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the Vault integration guide][vault-integration] for
+  details.
+- Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+- Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+- Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+## What's removed
+
+- Support for HCLv1 job specifications and the `-hcl1` flag on `nomad job run` and other commands. Refer to [GH-20195](https://github.com/hashicorp/nomad/issues/20195) for more details.
+
+- Support for Nomad client agents older than v1.6.0. Older nodes will fail heartbeats. Nomad servers will mark the workloads on Nomad client agents older than 1.6.0 as lost and reschedule them normally according to the job's [reschedule](/nomad/docs/v1.9.x/job-specification/reschedule) block.
+
+- The [LXC task driver](https://github.com/hashicorp/nomad-driver-lxc) and [ECS
+  task driver](https://github.com/hashicorp/nomad-driver-ecs) projects have been
+  archived with the release of Nomad 1.9 and are no longer supported.  Both
+  plug-ins are maintained separately from the Nomad core project and are not
+  subject to the LTS program.
+
+- Nomad has removed the `tls_prefer_server_cipher_suites` agent configuration from the [`tls` block](/nomad/docs/v1.9.x/configuration/tls).
+
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/v1.9.x/upgrade/upgrade-specific#nomad-1-9-0) and the changelogs.
+
+## Known issues
+
+None.
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.9.0](https://github.com/hashicorp/nomad/releases/tag/v1.9.0)
+
+
+[consul-integration]: /nomad/docs/v1.9.x/integrations/consul/acl
+[vault-integration]: /nomad/docs/v1.9.x/integrations/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/v1.9.x/job-specification/disconnect
+[Resource Quotas]: /nomad/docs/v1.9.x/other-specifications/quota
diff --git a/content/nomad/v1.10.x/content/docs/scale/benchmarking.mdx b/content/nomad/v1.10.x/content/docs/scale/benchmarking.mdx
new file mode 100644
index 0000000000..eb545241d4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/scale/benchmarking.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Benchmark and load test Nomad
+description: |-
+  Use the Nomad Bench project to benchmark and load test Nomad servers.
+---
+
+# Benchmark and load test Nomad
+
+The Nomad Bench project provides reusable infrastructure automation to run test
+scenarios in order to collect metrics and data from Nomad clusters running at
+scale. The core goal of the project is to achieve reproducible large scale test
+scenarios so we can better understand how Nomad scales and uncover problems that
+are only detected in large cluster deployments. It is also used to perform
+release soak testing, among other things.
+
+The [repository][bench-repo] contains all the infrastructure and details to get
+started with your own load testing.
+
+[bench-repo]: https://github.com/hashicorp-forge/nomad-bench
diff --git a/content/nomad/v1.10.x/content/docs/scale/index.mdx b/content/nomad/v1.10.x/content/docs/scale/index.mdx
new file mode 100644
index 0000000000..d7c5ea59e6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/scale/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Scale Nomad
+description: |-
+  This section provides information on Nomad Autoscaler and Nomad Bench.
+---
+
+# Scale Nomad
+
+This section provides information on the following standalone products:
+
+- Nomad Autoscaler, a horizontal application and cluster autoscaler
+  for Nomad.
+- Nomad Bench, a project that provides reusable infrastructure automation to
+run test scenarios in order to collect metrics and data from Nomad clusters
+running at scale.
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/bootstrap.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/bootstrap.mdx
new file mode 100644
index 0000000000..a6d39da0d3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/bootstrap.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: Bootstrap the ACL system
+description: |-
+  Enable and bootstrap the Nomad ACL system, deploy an anonymous policy, and create replication tokens for other regions.
+---
+
+# Bootstrap the ACL system
+
+Bootstrapping ACLs on a new cluster requires a few steps, outlined below. For
+multi-region clusters, you will perform the bootstrapping process on the
+authoritative region and set up replication.
+
+## Enable ACLs on Nomad servers
+
+The APIs needed to manage policies and tokens are not enabled until ACLs are
+enabled. To begin, you need to enable the ACLs on the servers. If a multi-region
+setup is used, the authoritative region should be enabled first. For each
+server:
+
+1. Set the [`enabled` value] of the [`acl` stanza] to true. The `acl` stanza is a
+   top-level stanza.
+
+```hcl
+acl {
+  enabled = true
+}
+```
+
+### Configure for multiple regions
+
+For multi-region configurations, you will also need to perform additional
+configuration. The regions must be joined before bootstrapping ACLs.
+If the non-authoritative region was already using ACLs, any existing tokens
+in that region will stop working after federation as they will be overwritten by the authoritative region.
+
+#### Set the authoritative region
+
+For all clusters in a multi-region setup, set the [`authoritative_region`
+value] in the [`server` stanza]. Later, you'll set the [`replication_token`
+value] of the [`acl` stanza]. You will learn how to generate management tokens
+later in this guide.
+
+### Reload your Nomad configuration
+
+Take care to restart the servers one at a time and to ensure each server has
+joined and is operating correctly before restarting another. You can use the
+[`nomad server members` command] to verify that a server is up and ready to
+handle requests.
+
+## Bootstrap and deploy anonymous policy
+
+Once the ACL system is enabled, you need to generate the initial token. This
+first management token is used to bootstrap the system. Care should be taken not
+to lose all of your management tokens. If you do, you will need to re-bootstrap
+the ACL subsystem.
+
+<Warning>
+
+Bootstrapping the ACL subsystem will interrupt access to your
+cluster. Once the [`nomad acl bootstrap` command] is run, Nomad's
+default-deny policy will become enabled. You should have an acceptable anonymous
+policy prepared and ready to submit immediately after bootstrapping.
+
+</Warning>
+
+### Stage an anonymous policy
+
+When the ACL system is enabled, Nomad starts with a default deny-all policy. This means that by default, no permissions are granted. For clients making requests without ACL tokens, you may want to create a transitional anonymous policy to allow traffic to your cluster while you are generating and distributing tokens to your users. This is done by setting rules on the special "anonymous" policy.
+
+<Warning>
+
+The anonymous policy assigns permissions to all unauthenticated requests to Nomad. We recommend using tokens with specific policies rather than an overly permissive anonymous policy. This guide uses it for illustrative purposes.
+
+</Warning>
+
+Create a file named `anonymous.policy.hcl`, add this content to the file, and save the file. This policy allows read-only access.
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["list-jobs", "read-job"]
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+host_volume "*" {
+  policy = "read"
+}
+```
+
+You can use this policy as a transitional anonymous policy, which will minimize time in which requests can not be submitted to the cluster once you bootstrap. Additional information is available for [node rules](/nomad/docs/other-specifications/acl-policy#node-rules), [agent rules](/nomad/docs/other-specifications/acl-policy#agent-rules), [operator rules](/nomad/docs/other-specifications/acl-policy#operator-rules), [quota rules](/nomad/docs/other-specifications/acl-policy#quota-rules), and [host volume rules](/nomad/docs/other-specifications/acl-policy#host-volume-rules).
+
+### Run the bootstrap command
+
+Once the ACL system is enabled, use the [`nomad acl bootstrap` command]:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Once the initial bootstrap is performed, it cannot be performed again unless the
+[reset] procedure is complete. Make sure to save this AccessorID and SecretID.
+The bootstrap token is a `management` type token, meaning it can perform any
+operation. It should be used to setup the ACL policies and create additional ACL
+tokens. The bootstrap token can be deleted and is like any other token, care
+should be taken to not revoke all management tokens.
+
+### Provide a CLI token
+
+If you attempt to run a command at this point without a token provided, you will
+encounter an error.
+
+```shell-session
+$ nomad status
+Error querying jobs: Unexpected response code: 403 (Permission denied)
+```
+
+Save the bootstrap token value to a file named `bootstrap.token`. Replace `BOOTSTRAP_SECRET_ID` in the following command with the Secret ID you received above.
+
+```shell-session
+$ echo "BOOTSTRAP_SECRET_ID" > bootstrap.token
+```
+
+Provide the token for CLI commands by setting the NOMAD_TOKEN environment variable to the bootstrap token value in the `bootstrap.token` file.
+
+```shell-session
+$ export NOMAD_TOKEN=$(cat bootstrap.token)
+```
+
+Run the [`nomad status` command]. It completes successfully because a token value is set.
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+### Deploy your anonymous policy
+
+Next, install the anonymous policy with the [`nomad acl policy apply` command].
+
+```shell-session
+$ nomad acl policy apply -description "Anonymous policy (full-access)" anonymous anonymous.policy.hcl
+Successfully wrote "anonymous" ACL policy!
+```
+
+Once this command has completed, requests to the cluster that do not present a token
+will use this policy.
+
+You can also use the Nomad API to submit policies as JSON objects. Consult the
+Nomad [`acl/policy` API] documentation for more information.
+
+#### Verify anonymous requests succeed
+
+Verify that the anonymous policy is performing as expected.
+
+Unset your NOMAD_TOKEN environment variable to send unauthenticated requests to your cluster.
+
+```shell-session
+$ unset NOMAD_TOKEN
+```
+
+Verify that the token is unset. This command returns an empty response.
+
+```shell-session
+$ echo ${NOMAD_TOKEN}
+
+```
+
+Check the status. This command succeeds without a token set because the anonymous policy has permissions to read job status.
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+### Delete the anonymous policy
+
+Once you have provided your users with tokens, you can update the anonymous
+policy to be more restrictive or delete it completely to deny all requests from unauthenticated users.
+
+Delete the anonymous policy. Set the `NOMAD_TOKEN` environment variable to the bootstrap token value again. This is necessary as the `nomad acl policy delete` command [requires the management token](/nomad/commands/acl/policy/delete).
+
+```shell-session
+$ export NOMAD_TOKEN=$(cat bootstrap.token)
+```
+
+Then, delete the anonymous policy.
+
+```shell-session
+$ nomad acl policy delete anonymous
+Successfully deleted anonymous policy!
+```
+
+## Enable ACLs on Nomad clients
+
+To enforce client endpoints, you need to enable ACLs on clients as well. Do this
+by setting the [`enabled` value] of the [`acl` stanza] to true. Once complete,
+restart the client to read in the new configuration.
+
+## Create management tokens for other regions
+
+Once you have bootstrapped ACLs on the servers of the authoritative region, you
+can create the replication tokens for all of the non-authoritative regions in a
+multi-region configuration. These tokens must be management-type tokens since
+they are used to communicate with ACL API in the authoritative region.
+
+Create the replication token with the [`nomad acl token create` command]. Don't
+forget to provide a management token via the NOMAD_TOKEN environment variable or
+the `-token` flag. As practice, this time use the `-token` flag:
+
+```shell-session
+$ nomad acl token create -type="management" -global=true \
+  -name="Cluster A Replication Token" \
+  -token="c999c4c2-6146-1bac-eb47-3958bbffe9d8"
+Accessor ID  = ec175d30-26ea-4a54-4850-45f833acece5
+Secret ID    = 9e2bb5ed-b3af-6bf3-5bbc-16dc684c5c31
+Name         = Cluster A Replication Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2020-01-08 21:12:43.32324673 +0000 UTC
+Create Index = 2916
+Modify Index = 2916
+```
+
+## Re-bootstrap ACL system
+
+If all management tokens are lost, it is possible to reset the ACL bootstrap so
+that it can be performed again. First, you need to determine the reset index
+with the bootstrap endpoint:
+
+```shell-session
+$ nomad acl bootstrap
+Error bootstrapping: Unexpected response code: 500 (ACL bootstrap already done (reset index: 7))
+```
+
+The error message contains the `reset index`. To reset the ACL system, create
+a file named `acl-bootstrap-reset` containing the value of the "reset index".
+This file should be placed in the data directory of the leader node:
+
+```shell-session
+$ echo 7 >> /nomad-data-dir/server/acl-bootstrap-reset
+```
+
+Once the reset file is in place, you can re-bootstrap the cluster:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 52d3353d-d7b9-d945-0591-1af608732b76
+Secret ID    = 4b0a41ca-6d32-1853-e64b-de0d347e4525
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 18:38:11.929089612 +0000 UTC
+Create Index = 11
+Modify Index = 11
+```
+
+If you attempt to bootstrap again you will get a mismatch on the reset index:
+
+```shell-session
+$ nomad acl bootstrap
+
+Error bootstrapping: Unexpected response code: 500 (Invalid bootstrap reset index (specified 7, reset index: 11))
+```
+
+This is because the reset file is in place, but with the former index. The reset
+file can be deleted. However, if it is left behind, Nomad will not reset the
+bootstrap unless the file's contents match the actual reset index.
+
+## Access an ACL-enabled web UI
+
+If you access the web UI without specifying an ACL token, Nomad grants you
+the permissions of the anonymous policy. You can set an ACL token in the web UI
+or with the CLI.
+
+### Provide a token in the web UI
+
+Open the web UI in your web browser with the cluster address and navigate to
+the `/ui` path. Click on the user icon in the top-right of the page to open the
+**Settings** page. Enter your ACL token in the **Secret ID** field and click
+the **Sign in with secret** button. You can also open this page directly by
+navigating to the `/ui/settings/tokens` path.
+
+### Provide a token with the CLI
+
+You can use the [`nomad ui` command](/nomad/commands/ui) and the token you have
+set for the Nomad CLI to authenticate to the web UI. This exchanges your ACL
+token for a one-time token in the web UI.
+
+```shell-session
+$ nomad ui -authenticate
+Opening URL "https://127.0.0.1:4646" with one-time token
+```
+
+## Next steps
+
+For a single cluster, the process is complete. For multi-region clusters, you
+can generate tokens local to each region to scope policies to a specific
+region, or use tokens with a Global scope so that you can submit jobs from any
+region to any other region.
+
+Now that you have learned about bootstrapping your Nomad cluster, you will learn
+more about how to create Nomad ACL policies.
+
+[`acl/policy` api]: /nomad/api-docs/acl/policies
+[`acl` stanza]: /nomad/docs/configuration/acl
+[`authoritative_region` value]: /nomad/docs/configuration/server#authoritative_region
+[`enabled` value]: /nomad/docs/configuration/acl#enabled
+[`nomad acl bootstrap` command]: /nomad/commands/acl/bootstrap
+[`nomad acl token create` command]: /nomad/commands/acl/token/create
+[`nomad server members` command]: /nomad/commands/server/members
+[`nomad status` command]: /nomad/commands/status
+[`replication_token` value]: /nomad/docs/configuration/acl#replication_token
+[`server` stanza]: /nomad/docs/configuration/server
+[reset]: /nomad/docs/secure/acl/bootstrap#re-bootstrap-acl-system
+[`nomad acl policy apply` command]: /nomad/commands/acl/policy/apply
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/consul.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/consul.mdx
new file mode 100644
index 0000000000..e646a3f4d1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/consul.mdx
@@ -0,0 +1,471 @@
+---
+layout: docs
+page_title: Integrate Consul ACL
+description: |-
+  Learn how to integrate Consul access control list (ACL) with Nomad workload identity. Learn how to migrate to using Nomad workload identity with Consul. Configure Consul so it can receive, validate, and trust workload identities from Nomad. Create binding and namespace rules. Review considerations for using the JSON Web Key Set (JWKS) URL.
+---
+
+# Integrate Consul ACL
+
+The [Consul ACL][consul_acls] system protects the cluster from unauthorized
+access. When enabled, both Consul and Nomad must be properly configured in
+order for their integrations to work.
+
+Nomad agents must be configured with their own Consul ACL token, and Consul
+must be configured to accept workload identities from tasks and services
+running in Nomad.
+
+Refer to the following for details on integrating Consul with Nomad:
+
+- [`consul` block in Agent configuration](/nomad/docs/configuration/consul) for
+  configuring Nomad and Consul.
+- [Consul networking integration guide](/nomad/docs/networking/consul) for
+  details on integrating Consul service discovery and service mesh.
+
+## Nomad Agents
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task or service's [Workload
+Identity][nomad_wid] to authenticate to Consul and obtain an ACL token specific
+to the service or task. When using Nomad workload identities, you no longer
+need to pass in a Consul ACL token to submit a job.
+
+By default, Nomad does not generate workload identities for services, and tasks
+only receive an identity that can be used to access data from Nomad itself,
+such as for reading [Variables][] from a [`template`][] block. To access
+Consul, jobs must have additional workload identities defined as [`identity`][]
+blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure Nomad servers with the [`consul.service_identity`][] and
+[`consul.task_identity`][] agent configuration. Upon job registration, the
+Nomad servers update tasks that have a [`consul`][] block and services that use
+the Consul service provider with these default identities.
+
+Job specifications that include [`template`][] blocks are not provided with
+default identities because Nomad is unable to decipher the contents of the
+template data. You must specify the identities required for Consul in the job
+specification. Refer to the [Workload Identities for Consul][jobspec_identity_consul]
+section of the `identity` block documentation for more information.
+
+You can also specify identities for Consul directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Consul][jobspec_identity_consul] section of the `identity` block
+documentation for more information.
+
+### Configuring Consul Authentication
+
+You must configure Consul so it can receive, validate, and trust workload
+identities from Nomad. Since they are encoded as [JSON Web Tokens (JWTs)][jwt],
+you must create a [JWT ACL auth method][consul_jwt_auth_method]. The auth
+method is an endpoint that Nomad can use to exchange workload identities for
+Consul ACL tokens.
+
+Refer to Consul's [Auth Methods Overview][consul_auth_methods] documentation
+for more information.
+
+#### Consul Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Consul servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Consul is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+Nomad cannot recreate Consul tokens that have been deleted. The auth method
+configuration should never set the `MaxTokenTTL` field. Consul tokens are
+local to the Consul datacenter unless you set `TokenLocality: "global"` in the
+auth method. We recommend using local tokens, which is the default. Global tokens
+require that the primary Consul datacenter is available when allocations start.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `JWKSURL` address must be reachable by all Consul servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `JWKSURL` value.
+
+[![Consul Auth Method][img_consul_auth_method]][img_consul_auth_method]
+
+When an allocation that needs access to Consul starts, the Nomad client running
+it exchanges the Nomad workload identities for tasks and services for Consul
+ACL tokens.
+
+[![Consul JWT Login][img_consul_wid_acl_token]][img_consul_wid_acl_token]
+
+The auth method also defines the list of authorized audience values, which must
+have at least one match with the values defined in the Nomad workload identity
+[`aud`][] parameter. For security reasons, it is recommended to only define a
+single audience value.
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced as dynamic values in Consul ACL configuration. The auth method
+determines which of these claims are made available to the rest of the
+configuration.
+
+<CodeBlockConfig highlight="6-9" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### Consul Binding Rules
+
+Consul auth methods use [binding rules][consul_binding_rules] to determine the
+set of policies applied to the generated ACL token. Nomad workload identities
+can be used in Consul for two main purpose: registering services and retrieving
+configuration values and service addresses from Consul using `template` blocks
+in tasks. Each purpose requires tokens with different permissions so Nomad
+requires two binding rules.
+
+The first binding rule associates the Consul ACL token with a [service
+identity][consul_si], allowing the token to register and manage the lifecyle of
+a given service. This binding rule is only applied to Nomad workload identities
+for services because they are the only ones that have a `nomad_service` claim.
+
+```shell-session
+$ consul acl binding-rule create \
+    -method 'nomad-workloads' \
+    -bind-type 'service' \
+    -bind-name '${value.nomad_service}' \
+    -selector '"nomad_service" in value'
+```
+
+The [`-bind-name`][] flag restricts the token to only be able to modify
+services with the same name as the one defined in the Nomad workload identity
+claim. The [`-selector`][] flag ensures this binding rule only applies to
+workload identities for services.
+
+The second binding rule associates the Consul ACL token with an [ACL
+role][consul_acl_role], which is a collection of [ACL
+policies][consul_acl_policy] that define what the token is authorized to do.
+This binding rule is applied to Nomad workload identities for tasks to access
+information from Consul. The exact ACL policy rules will depend on the level of
+access required by the tasks (typically, accessing service addresses and KV with
+[`template`][] blocks).
+
+```shell-session
+$ consul acl binding-rule create \
+  -method 'nomad-workloads' \
+  -bind-type 'role' \
+  -bind-name 'nomad-tasks-${value.nomad_namespace}' \
+  -selector '"nomad_service" not in value'
+```
+
+The `-bind-name` flag defines which role is used for the token. It may
+reference claim values from the Nomad workload identity to apply different
+roles to different tasks. Similarly to the binding rule for services, the
+`-selector` flag ensures this binding rule only applies to workload identities
+for tasks since they don't have the `nomad_service` claim.
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Consul Auth Overview][img_consul_auth]][img_consul_auth]
+
+The [`consul.service_auth_method`][] and [`consul.task_auth_method`][]
+configuration define the auth method used by Nomad to retrieve Consul ACL
+tokens for services and tasks.
+
+By default, they follow the structure described above and use a single auth
+method for both, but it is possible to use two different auth methods, provided
+the resulting Consul ACL token from each have the expected service identity and
+role applied.
+
+#### Consul Namespace Rules <EnterpriseAlert inline />
+
+Consul Enterprise supports multiple namespaces and Nomad Enterprise allows jobs
+to use the [`consul.namespace`][] parameter to register services and read KV
+data from different Consul namespaces.
+
+In Nomad Enterprise, workload identities for tasks and services placed within
+the scope of a `consul` block with a `namespace` value, have an additional claim
+called `consul_namespace` that represents the Consul namespace defined in Nomad
+for the workload. In a multi-namespace environment, you should configure the
+auth method to include the `consul_namespace` claim mapping.
+
+<CodeBlockConfig highlight="6" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "consul_namespace": "consul_namespace",
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+You should create the auth method and binding rules in the `default` Consul
+namespace and configure the auth method with a set of [`NamespaceRules`][].
+
+```shell-session
+$ consul acl auth-method create \
+  -name 'nomad-workloads' \
+  -type 'jwt' \
+  -config '@auth-method.json' \
+  -namespace-rule-selector '"consul_namespace" in value' \
+  -namespace-rule-bind-namespace '${value.consul_namespace}'
+```
+
+Similarly to binding rules, namespace rules have a [`Selector`][] expression to
+determine when the rule should be applied and a [`BindNamespace`][] value that
+defines the Consul namespace used.
+
+Auth methods with a namespace rule create Consul tokens in that Consul
+namespace. Binding rules with `-bind-type role` also target a role and
+associated policies in that same Consul namespace. So you should create the auth
+method and binding rules in the default Consul namespace, and the role and
+policies in the target Consul namespaces.
+
+<CodeBlockConfig highlight="9-11" filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    consul {
+      namespace = "prod"
+    }
+
+    service {
+      port     = "db"
+      name     = "redis"
+      provider = "consul"
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+If a `consul` block is not defined, then the workload identity will not have
+the `consul_namespace` claim, since Nomad is not able to determine which Consul
+namespace will be used.
+
+Refer to the [Consul Namespaces][int_consul_ns] section for more information.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Consul servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Consul and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Consul auth method.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Consul Servers Not Able to Connect to Nomad
+
+If the Consul servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`JWTValidationPubKeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Consul servers, and use that address as the value for
+`JWKSURL`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional References
+
+The [Consul ACL with Nomad Workload Identities][consul_tutorial_wid] tutorial
+provides guided instructions on how to configure Consul and Nomad for workload
+identities.
+
+The [`nomad setup consul`][nomad_cli_setup_consul] command and the
+[`hashicorp-modules/nomad-setup/consul`][tf_nomad_setup_consul] Terraform
+module can help you automate the process of applying configuration to a Consul
+cluster.
+
+## Migrating to Using Workload Identity with Consul
+
+Nomad version 1.7.0 introduced Workload Identity authentication, and deprecated
+token authentication.  Token authentication was then removed in Nomad 1.10.0.
+Migrating from the legacy (pre-1.7) workflow where workload use the agent's
+Consul token requires configuation on your Consul cluster and your Nomad server
+agents. It does not require updating your running Nomad jobs. To migrate:
+
+* Create the Consul auth method and binding rules on your Consul cluster.
+* Enable [`consul.service_identity`][] blocks in your Nomad server agent configurations.
+* Enable [`consul.task_identity`][] blocks in your Nomad server agent configurations.
+* (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+  different identity because of how your auth method and binding rules are
+  configured.
+
+Note that when using Workload Identity you will no longer need to pass in a
+Consul token to submit a job.
+
+[Variables]: /nomad/docs/concepts/variables
+[`-bind-name`]: /consul/commands/acl/binding-rule/create#bind-name
+[`-selector`]: /consul/commands/acl/binding-rule/create#selector
+[`BindNamespace`]: /consul/api-docs/acl/auth-methods#bindnamespace
+[`JWTValidationPubKeys`]: /consul/docs/security/acl/auth-methods/jwt#jwtvalidationpubkeys
+[`NamespaceRules`]: /consul/api-docs/acl/auth-methods#namespacerules
+[`Selector`]: /consul/api-docs/acl/auth-methods#selector
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[`consul.service_auth_method`]: /nomad/docs/configuration/consul#service_auth_method
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_auth_method`]: /nomad/docs/configuration/consul#task_auth_method
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`identity`]: /nomad/docs/job-specification/identity
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[consul_acl_policy]: /consul/docs/security/acl/acl-policies
+[consul_acl_role]: /consul/docs/security/acl/acl-roles
+[consul_acls]: /consul/docs/security/acl
+[consul_auth_methods]: /consul/docs/security/acl/auth-methods
+[consul_binding_rules]: /consul/api-docs/acl/binding-rules
+[consul_config_entry]: /consul/docs/connect/config-entries
+[consul_jwt_auth_method]: /consul/docs/security/acl/auth-methods/jwt
+[consul_si]: /consul/docs/security/acl/acl-roles#service-identities
+[consul_tutorial_wid]: /nomad/tutorials/integrate-consul/consul-acl
+[img_consul_auth]: /img/consul-integration-wi.png
+[img_consul_auth_method]: /img/consul-integration-auth-method.png
+[img_consul_wid_acl_token]: /img/consul-integration-wid-acl-token.png
+[int_consul_ns]: /nomad/docs/networking/consul#consul-namespaces
+[jobspec_identity_consul]: /nomad/docs/job-specification/identity#workload-identities-for-consul
+[jwt]: https://jwt.io/
+[nomad_cli_setup_consul]: /nomad/commands/setup/consul
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_consul]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/consul/
+[tutorial_mtls]: /nomad/docs/secure/traffic/tls
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/index.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/index.mdx
new file mode 100644
index 0000000000..9699bdcb09
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/index.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: ACL system overview
+description: |-
+  Explore the three major components of Nomad's Access Control Layer (ACL) system: capabilities, policies, and tokens.
+---
+
+# ACL system overview
+
+The ACL system is designed to be intuitive, high-performance, and to provide
+administrative insight. At the highest level, there are three major components to
+the ACL system: tokens, policies, and capabilities. The components are
+illustrated in the diagram below.
+
+[![Image showing that ACL Tokens refer to one or more associated policies and
+that those policies encapsulate capabilities like "Allow Submit Job" or "Allow
+Query Nodes"][img_acl_overview]][img_acl_overview]
+
+## Policies
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy must have a unique name, an optional description, and a rule set.
+The rules define the capabilities of a Nomad ACL token for accessing the objects
+in a Nomad cluster, objects like namespaces, node, agent, operator, quota, etc.
+A client ACL token can be associated with multiple policies; a request is
+allowed if _any_ of the associated policies grant the capability. Management
+tokens cannot be associated with policies because they are granted all
+capabilities.
+
+The special `anonymous` policy can be defined to grant capabilities to anonymous
+requests. An anonymous request is a request made to Nomad without the
+`X-Nomad-Token` header specified. This can be used to allow anonymous users to
+list jobs and view their status, while requiring authenticated requests to
+submit new jobs or modify existing jobs. By default, there is no `anonymous`
+policy set meaning all anonymous requests are denied.
+
+## Roles
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+## Capabilities
+
+Capabilities are the set of actions that can be performed. This
+includes listing jobs, submitting jobs, querying nodes, etc. A management token
+is granted all capabilities, while client tokens are granted specific
+capabilities via ACL policies. The full set of capabilities is discussed in the
+rule specifications.
+
+## Binding rules
+
+Policies are comprised of one or more rules. The rules define the capabilities  of a Nomad ACL token for accessing the objects in a Nomad cluster, objects    like namespaces, node, agent, operator, quota, etc.
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+<Note>
+  Binding rules are evaluated in no specific order, and should there be an
+  overlap in their selectors or scope, a "sum" of all the binding rules will be
+  applied, thus the least granular binding rules will always override the more
+  granular ones, as long as they apply to the same auth method and identity.
+</Note>
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+### Rules and scope
+
+The following table summarizes the rules that are available for constructing
+ACL policies:
+
+| Rule                             | Scope                                        |
+| -------------------------------- | -------------------------------------------- |
+| [agent][rules_agent]             | Utility operations in the Agent API          |
+| [host_volume][rules_host_volume] | Host Volume related operations               |
+| [namespace][rules_namespace]     | Job related operations by namespace          |
+| [node][rules_node]               | Node-level catalog operations                |
+| [operator][rules_operator]       | Cluster-level operations in the Operator API |
+| [plugin][rules_plugin]           | CSI Plugin related operations                |
+| [quota][rules_quota]             | Quota specification related operations       |
+
+Constructing policies from these rules is covered in detail in the
+[Nomad ACL Policy Concepts guide][acl-policy-guide].
+
+## Tokens
+
+ACL tokens are used to authenticate requests and determine if the caller is
+authorized to perform an action. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. Local tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+## Workload Identity
+
+Nomad allocations can receive workload identities in the form of a [JSON Web
+Token (JWT)][jwt]. The [Workload Identity concept page][workload identity] has
+more information on this topic.
+
+## Authentication methods
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+Since both the `oidc` and `jwt` auth methods ultimately operate on JWTs as
+bearer tokens, use the following to determine which method fits your use case:
+
+- **JWT**
+
+  - Ideal for machine-oriented, headless login where an operator may have already
+    arranged for a valid JWT to be dropped on a VM or provided to a container.
+  - User or application performing the Nomad login must have a valid JWT
+    to begin login.
+  - Does not require browser interaction.
+
+- **OIDC**
+
+  - Ideal for human-oriented, interactive login where an operator or administrator
+    may have deployed SSO widely and doesn't want to distribute Nomad ACL tokens
+    to every authorized user.
+  - User performing the Nomad login does not need a JWT.
+  - Requires browser interaction.
+
+## Multi-Region configuration
+
+Nomad supports multi-datacenter and multi-region configurations. A single region
+is able to service multiple datacenters, and all servers in a region replicate
+their state between each other. In a multi-region configuration, there is a set
+of servers per region. Each region operates independently and is loosely coupled
+to allow jobs to be scheduled in any region and requests to flow transparently
+to the correct region.
+
+When ACLs are enabled, Nomad depends on an "authoritative region" to act as a
+single source of truth for ACL policies and global ACL tokens. The authoritative
+region is configured in the [`server` stanza] of agents, and all regions must
+share a single authoritative source. Any ACL policies or global ACL tokens are
+created in the authoritative region first. All other regions replicate ACL
+policies and global ACL tokens to act as local mirrors. This allows policies to
+be administered centrally, and for enforcement to be local to each region for
+low latency.
+
+Global ACL tokens are used to allow cross-region requests. Standard ACL tokens
+are created in a single target region and not replicated. This means if a
+request takes place between regions, global tokens must be used so that both
+regions will have the token registered.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[acl-policy-guide]: /nomad/docs/secure/acl/policies
+[`server` stanza]: /nomad/docs/configuration/server
+[img_acl_overview]: /img/secure/acl.jpg
+[rules_agent]: /nomad/docs/secure/acl/policies#agent-rules
+[rules_host_volume]: /nomad/docs/secure/acl/policies#host-volume-rules
+[rules_namespace]: /nomad/docs/secure/acl/policies#namespace-rules
+[rules_node]: /nomad/docs/secure/acl/policies#node-rules
+[rules_operator]: /nomad/docs/secure/acl/policies#operator-rules
+[rules_plugin]: /nomad/docs/secure/acl/policies#plugin-rules
+[rules_quota]: /nomad/docs/secure/acl/policies#quota-rules
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/policies/create-policy.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/policies/create-policy.mdx
new file mode 100644
index 0000000000..4f64ff2bf3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/policies/create-policy.mdx
@@ -0,0 +1,444 @@
+---
+layout: docs
+page_title: Create ACL policies
+description: |-
+  Create and deploy Nomad ACL policies for application developers and production operators to implement the principle of least privilege.
+---
+
+# Create ACL policies
+
+In this guide, you will create Nomad ACL policies to provide controlled
+access for two different personas to your Nomad Cluster. You will use the sample
+job created with the `nomad init -short` command as a sample job.
+
+To complete this guide, you will need the following:
+
+- A Nomad cluster with the ACL system bootstrapped.
+
+- A management token. You can use the bootstrap token, however, for production
+  systems you should use an user-specific token.
+
+## Meet the personas
+
+In this guide, you will create policies to manage cluster access for two
+different user personas. These are contrived to suit the scenario, and
+you should design your ACL policies around your organization's specific needs.
+
+As a best practice, access should be limited as much as possible given the needs
+of the user's roles.
+
+<Tip title="Challenge">
+
+ Consider extending this scenario to include namespaces.
+
+</Tip>
+
+### Application Developer
+
+The application developer needs to be able to deploy an application into the
+Nomad cluster and control its lifecycle. They should not be able to perform any
+other node operations.
+
+Application developers are allowed to fetch logs from their running containers,
+but should not be allowed to run commands inside of them or access the filesystem for running workloads.
+
+### Production Operations
+
+The production operations team needs to be able to perform cluster
+maintenance and view the workload, including attached resources like
+volumes, in the running cluster. However, because the application
+developers are the owners of the running workload, the production
+operators should not be allowed to run or stop jobs in the cluster.
+
+## Write the policy rules
+
+### Application Developer policy
+
+Considering the requirements listed above, what rules should you add to your
+policy? Nomad will deny all requests that are not explicitly permitted, so focus
+on the policies and capabilities you would like to permit. However, be mindful
+of the coarse-grained permissions in `namespace` rules--they might grant more
+permissions than you need for your use case.
+
+> The application developer needs to be able to deploy an application into the Nomad cluster and control its lifecycle. They should not be able to perform any other node operations.
+
+> Application developers are allowed to fetch logs from their running containers, but should not be allowed to run commands inside of them or access the filesystem for running workloads.
+
+Recall that [`namespace` rules] govern the job application deployment behaviors
+and introspection capabilities for a Nomad cluster.
+
+First define the policy in terms of required capabilities. What capabilities
+from the available options will this policy need to provide to Application
+Developers?
+
+| Capability                                                                                                                                            | Desired |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| **deny** - When multiple policies are associated with a token, deny will take precedence and prevent any capabilities.                                | N/A     |
+| **list-jobs** - Allows listing the jobs and seeing coarse grain status.                                                                               | ✅      |
+| **read-job** - Allows inspecting a job and seeing fine grain status.                                                                                  | ✅      |
+| **submit-job** - Allows jobs to be submitted or modified.                                                                                             | ✅      |
+| **dispatch-job** - Allows jobs to be dispatched                                                                                                       | ✅      |
+| **read-logs** - Allows the logs associated with a job to be viewed.                                                                                   | ✅      |
+| **read-fs** - Allows the filesystem of allocations associated to be viewed.                                                                           | 🚫      |
+| **alloc-exec** - Allows an operator to connect and run commands in running allocations.                                                               | 🚫      |
+| **alloc-node-exec** - Allows an operator to connect and run commands in allocations running without filesystem isolation, for example, raw_exec jobs. | 🚫      |
+| **alloc-lifecycle** - Allows an operator to stop individual allocations manually.                                                                     | 🚫      |
+| **csi-register-plugin** - Allows jobs to be submitted that register themselves as CSI plugins.                                                        | 🚫      |
+| **csi-write-volume** - Allows CSI volumes to be registered or deregistered.                                                                           | 🚫      |
+| **csi-read-volume** - Allows inspecting a CSI volume and seeing fine grain status.                                                                    | 🚫      |
+| **csi-list-volume** - Allows listing CSI volumes and seeing coarse grain status.                                                                      | 🚫      |
+| **csi-mount-volume** - Allows jobs to be submitted that claim a CSI volume.                                                                           | 🚫      |
+| **list-scaling-policies** - Allows listing scaling policies.                                                                                          | 🚫      |
+| **read-scaling-policy** - Allows inspecting a scaling policy.                                                                                         | 🚫      |
+| **read-job-scaling** - Allows inspecting the current scaling of a job.                                                                                | 🚫      |
+| **scale-job** - Allows scaling a job up or down.                                                                                                      | 🚫      |
+| **sentinel-override** - Allows soft mandatory policies to be overridden.                                                                              | 🚫      |
+
+Remember that the coarse-grained `policy` value of a namespace rule is a list of
+capabilities.
+
+
+| policy value | capabilities                                                                                                                                                                                                                                                    |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`       | deny                                                                                                                                                                                                                                                            |
+| `read`       | list-jobs<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                     |
+| `write`      | list-jobs<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale`      | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+| `list`       | (grants listing plugin metadata only)                                                                                                                                                                                                                           |
+
+
+
+Express this in policy form. Create an file named `app-dev.policy.hcl` to write
+your policy.
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job","dispatch-job","read-logs"]
+}
+```
+
+Note that the namespace rule has `policy = "read"`. The **write** policy is not
+suitable because it is overly permissive, granting "read-fs", "alloc-exec", and
+"alloc-lifecycle".
+
+### Production Operations policy
+
+Consider the requirements listed above, what rules should you add to your
+policy? Nomad will deny all requests that are not explicitly supplied, so focus
+on the policies you would like to permit.
+
+> The production operations team needs to be able to perform cluster maintenance and view the workload, including attached resources like volumes, in the running cluster. However, because the application developers are the owners of the running workload, the production operators should not be allowed to run or stop jobs in the cluster.
+
+Recall that [`namespace` rules] govern the job application deployment behaviors
+and introspection capabilities for a Nomad cluster.
+
+First define the policy in terms of required capabilities. What capabilities
+from the available options will this policy need to provide to Production
+Operators?
+
+| Capability                                                                                                                                            | Desired |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| **deny** - When multiple policies are associated with a token, deny will take precedence and prevent any capabilities.                                | N/A     |
+| **list-jobs** - Allows listing the jobs and seeing coarse grain status.                                                                               | ✅      |
+| **read-job** - Allows inspecting a job and seeing fine grain status.                                                                                  | ✅      |
+| **submit-job** - Allows jobs to be submitted or modified.                                                                                             | 🚫      |
+| **dispatch-job** - Allows jobs to be dispatched                                                                                                       | 🚫      |
+| **read-logs** - Allows the logs associated with a job to be viewed.                                                                                   | 🚫      |
+| **read-fs** - Allows the filesystem of allocations associated to be viewed.                                                                           | 🚫      |
+| **alloc-exec** - Allows an operator to connect and run commands in running allocations.                                                               | 🚫      |
+| **alloc-node-exec** - Allows an operator to connect and run commands in allocations running without filesystem isolation, for example, raw_exec jobs. | 🚫      |
+| **alloc-lifecycle** - Allows an operator to stop individual allocations manually.                                                                     | 🚫      |
+| **csi-register-plugin** - Allows jobs to be submitted that register themselves as CSI plugins.                                                        | 🚫      |
+| **csi-write-volume** - Allows CSI volumes to be registered or deregistered.                                                                           | 🚫      |
+| **csi-read-volume** - Allows inspecting a CSI volume and seeing fine grain status.                                                                    | ✅      |
+| **csi-list-volume** - Allows listing CSI volumes and seeing coarse grain status.                                                                      | ✅      |
+| **csi-mount-volume** - Allows jobs to be submitted that claim a CSI volume.                                                                           | 🚫      |
+| **list-scaling-policies** - Allows listing scaling policies.                                                                                          | 🚫      |
+| **read-scaling-policy** - Allows inspecting a scaling policy.                                                                                         | 🚫      |
+| **read-job-scaling** - Allows inspecting the current scaling of a job.                                                                                | 🚫      |
+| **scale-job** - Allows scaling a job up or down.                                                                                                      | 🚫      |
+| **sentinel-override** - Allows soft mandatory policies to be overridden.                                                                              | 🚫      |
+
+Again, the coarse-grained `policy` value of a namespace rule is a list of
+capabilities.
+
+
+
+| policy value | capabilities                                                                                                                                                                                                                                                    |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`       | deny                                                                                                                                                                                                                                                            |
+| `read`       | list-jobs<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                     |
+| `write`      | list-jobs<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale`      | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+| `list`       | (grants listing plugin metadata only)                                                                                                                                                                                                                           |
+
+
+
+Express this in policy form. Create an file named `prod-ops.policy.hcl` to write
+your policy. The capabilities required over the Namespace API is captured with
+the `read` policy value.
+
+```hcl
+namespace "default" {
+  policy = "read"
+}
+```
+
+Operators will also need to have access to several other API endpoints: node,
+agent, operator. Consult the individual API documentation for more details on
+the endpoints.
+
+```hcl
+node {
+  policy = "write"
+}
+
+agent {
+  policy = "write"
+}
+
+operator {
+  policy = "write"
+}
+
+plugin {
+  policy = "list"
+}
+```
+
+Add all of these policy elements to your `prod-ops.policy.hcl` file and save it.
+
+## Upload the policies
+
+Use the `nomad acl policy apply` command to upload your policy specifications.
+Don't forget to provide a management token via the NOMAD_TOKEN environment
+variable or the `-token` flag. As practice, this time use the `-token` flag.
+
+Upload the "Application Developer policy."
+
+```shell-session
+$ nomad acl policy apply -description "Application Developer policy" app-dev app-dev.policy.hcl
+Successfully wrote "app-dev" ACL policy!
+```
+
+Upload the "Production Operations policy."
+
+```shell-session
+$ nomad acl policy apply -description "Production Operations policy" prod-ops prod-ops.policy.hcl
+Successfully wrote "prod-ops" ACL policy!
+```
+
+## Verify the policy
+
+In order to verify the policy works properly, you will need to create tokens and
+check the success case and the failure cases.
+
+Create an app-dev token. For this guide, pipe your output into the tee command
+to save it as `app-dev.token`.
+
+```shell-session
+$ nomad acl token create -name="Test app-dev token" -policy=app-dev -type=client | tee app-dev.token
+Accessor ID  = b8c67cb8-cc3b-2a7c-182a-0bc5dfc3a6ff
+Secret ID    = 17cadb8b-e8a8-2f47-db62-fea0c6a19602
+Name         = Test app-dev token
+Type         = client
+Global       = false
+Policies     = [app-dev]
+Create Time  = 2020-02-10 18:41:43.049735 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Next, create a prod-ops token, piping your output into the tee command to save
+it as `prod-ops.token`.
+
+```shell-session
+$ nomad acl token create -name="Test prod-ops token" -policy=prod-ops -type=client | tee prod-ops.token
+Accessor ID  = 4e3c1ac7-52d0-6c68-94a2-5e75f17e657e
+Secret ID    = 0be3c623-cc90-3645-c29d-5f0629084f68
+Name         = Test prod-ops token
+Type         = client
+Global       = false
+Policies     = [prod-ops]
+Create Time  = 2020-02-10 18:41:53.851133 +0000 UTC
+Create Index = 15
+Modify Index = 15
+```
+
+### Submit a job using each token
+
+First, set the active token to your test app-dev token. You can extract it from
+the files that you created above.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' app-dev.token)
+```
+
+Create the sample job with `nomad init`.
+
+```shell-session
+$ nomad init
+```
+
+Submit the sample job to your Nomad cluster.
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> Monitoring evaluation "0acad62d"
+    Evaluation triggered by job "example"
+    Allocation "8b54bf75" created: node "afcb4e20", group "cache"
+    Evaluation within deployment: "63bbb604"
+    Allocation "8b54bf75" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0acad62d" finished with status "complete"
+```
+
+Verify that the job starts completely using the `nomad job status` command.
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 2020-02-10T13:42:17-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 63bbb604
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       1        1       0        0          2020-02-10T13:52:17-05:00
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+8b54bf75  afcb4e20  cache       0        run      running  26s ago  25s ago
+```
+
+Switch to the prod-ops token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' prod-ops.token)
+```
+
+Try to stop the job; note that you are unable to do so.
+
+```shell-session
+$ nomad stop example
+Error deregistering job: Unexpected response code: 403 (Permission denied)
+```
+
+Switch back to the app-dev token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' app-dev.token)
+
+$ nomad stop example
+==> Monitoring evaluation "2571f9f9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "63bbb604"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2571f9f9" finished with status "complete"
+```
+
+Try again to stop the job; note that this time you are successful.
+
+```shell-session
+$ nomad stop example
+==> Monitoring evaluation "2571f9f9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "63bbb604"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2571f9f9" finished with status "complete"
+```
+
+### Stimulate GC on your cluster
+
+With the app-dev token still active, export your cluster address into a variable for convenience.
+
+```shell-session
+$ export NOMAD_ADDR=http://localhost:4646
+```
+
+Try to use the Nodes API to list out the Nomad clients in the cluster.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/nodes
+Permission denied
+```
+
+Set the active token to your test prod-ops token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' prod-ops.token)
+```
+
+Resubmit your Nodes API query. Expect to have a significant amount of JSON
+returned to your screen which indicates successful API call.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/nodes
+```
+
+## Challenge: Restrict anonymous users
+
+The bootstrapping guide provides a very permissive anonymous user policy to
+minimize user and workload impacts from Nomad's default deny-all policy. This
+allows cluster users and other submitting agents to continue to work while
+tokens are being created and deployed.
+
+As a challenge to yourself, consider the minimum viable set of permissions for
+anonymous users in your organization. Craft a policy that prevents user access
+to capabilities that are not in your user's critical path.
+
+## Clean up
+
+If you would like to remove the objects that you created in this guide, switch
+back to your management token and revoke the tokens that you created above using
+the accessors in the files.
+
+~> If you receive a "Permission denied" error when you are running the delete
+commands, ensure that you have loaded your management token back into the
+NOMAD_TOKEN environment variable.
+
+```shell-session
+$ nomad acl token delete $(awk '/Accessor/ {print $4}' prod-ops.token)
+Token 4e3c1ac7-52d0-6c68-94a2-5e75f17e657e successfully deleted
+```
+
+```shell-session
+$ nomad acl token delete $(awk '/Accessor/ {print $4}' app-dev.token)
+Token b8c67cb8-cc3b-2a7c-182a-0bc5dfc3a6ff successfully deleted
+```
+
+Next, remove the prod-ops and app-dev policies that you created.
+
+```shell-session
+$ nomad acl policy delete prod-ops
+Successfully deleted prod-ops policy!
+```
+
+```shell-session
+$ nomad acl policy delete app-dev
+Successfully deleted app-dev policy!
+```
+
+## Next steps
+
+Now that you have deployed your own policy into the cluster, you will learn
+about Nomad access tokens. Nomad users will need to provide tokens for
+non-anonymous requests. These tokens map to one or more ACL policies which
+define the accessible Nomad objects for that request.
+
+[`namespace` rules]: /nomad/docs/secure/acl/policies/#namespace-rules
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/policies/index.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/policies/index.mdx
new file mode 100644
index 0000000000..d3e0f1d6eb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/policies/index.mdx
@@ -0,0 +1,404 @@
+---
+layout: docs
+page_title: ACL policy overview
+description: |-
+  Become familiar with the coarse-grained rules and fine-grained capabilities that allow operators to allow or restrict access to different Nomad data and APIs.
+---
+
+# ACL policy overview
+
+Nomad provides an optional Access Control List (ACL) system which can be used
+to control access to data and APIs. The ACL system is capability-based,
+relying on tokens which are associated with policies to determine which fine
+grained rules can be applied.
+
+ACL policies are written using [HashiCorp Configuration Language (HCL)][hcl].
+This language is designed for human readability. The HCL interpreter also parses
+JSON which facilitates the use of machine-generated configuration.
+
+An ACL policy contains one or more rules. Rules contain coarse-grained policy
+dispositions. Rules typically have several policy dispositions:
+
+- `read`: allow the resource to be read but not modified
+
+- `write`: allow the resource to be read and modified
+
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+- `list`: allow the resource to be listed but not inspected in
+  detail. Applies only to plugins.
+
+Some rules, such as `namespace` and `host_volume`, also allow the policy designer to
+specify a policy in terms of a coarse-grained policy disposition, fine-grained
+capabilities, or a combination of the two.
+
+## ACL policy specification
+
+An ACL policy is a composition of one or more rules. Its specification in the
+HCL format looks like:
+
+```hcl
+# Allow read only access to the default namespace
+namespace "default" {
+  policy = "read"
+}
+
+# Allow writing to the `foo` namespace
+namespace "foo" {
+  policy = "write"
+}
+
+agent {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+```
+
+The JSON representation of the same policy:
+
+```json
+{
+  "namespace": {
+    "default": {
+      "policy": "read"
+    },
+    "foo": {
+      "policy": "write"
+    }
+  },
+  "agent": {
+    "policy": "read"
+  },
+  "node": {
+    "policy": "read"
+  },
+  "quota": {
+    "policy": "read"
+  }
+}
+```
+
+The [ACL Policy API][api_policy] allows either HCL or JSON to be used to define
+the content of the rules section. Because HCL is designed to be more
+operator-friendly and allows comments, this tutorial will use HCL for all examples
+and snippets.
+
+## Namespace rules
+
+Nomad allows operators to create multiple namespaces to provide granular access to cluster resources.
+
+The `namespace` rule controls access to a namespace. Namespaces contain the
+majority of the active work of the cluster [Jobs API][api_jobs],
+[Deployments API][api_deployments], [Allocations API][api_allocations], and
+[Evaluations API][api_evaluations].
+
+```hcl
+namespace "default" {
+  policy = "write"
+}
+
+namespace "sensitive" {
+  policy = "read"
+}
+```
+
+Namespace rules are keyed by the namespace name they apply to. When no namespace
+is specified, the "default" namespace is the one used. For example, the above
+policy grants write access to the default namespace, and read access to the
+sensitive namespace. To grant access to all namespaces, you can use the wildcard
+namespace (`"*"`). In addition to the coarse-grained `policy` disposition,
+the `namespace` stanza allows setting a more fine grained list of
+`capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status.
+
+- `parse-job` - Allows parsing a job from HCL to JSON.
+
+- `read-job` - Allows inspecting a job and seeing fine grain status.
+
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+
+- `dispatch-job` - Allows jobs to be dispatched
+
+- `read-logs` - Allows the logs associated with a job to be viewed.
+
+- `read-fs` - Allows the filesystem of allocations associated to be viewed.
+
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+
+- `csi-register-plugin` - Allows jobs to be submitted that register
+  themselves as CSI plugins.
+
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered.
+
+- `csi-read-volume` - Allows inspecting a CSI volume and seeing fine grain status.
+
+- `csi-list-volume` - Allows listing CSI volumes and seeing coarse grain status.
+
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume.
+
+- `list-scaling-policies` - Allows listing scaling policies.
+
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+
+- `scale-job`: Allows scaling a job up or down.
+
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+
+The coarse-grained policy dispositions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                    |
+| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`  | deny                                                                                                                                                                                                                                                            |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                      |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+
+<!-- markdownlint-enable -->
+
+When both the policy shorthand and a capabilities list are provided, the
+capabilities are merged. This policy adds the submit-job capability to the read
+policy disposition, which provide the list-job and read-job capabilities:
+
+```hcl
+# Allow reading resources within the "default" namespace as well as submitting
+# jobs to this namespace, without allowing access to view log output or inspect
+# the filesystem.
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+This policy could be expressed as:
+
+```hcl
+# Allow reading resources within the "default" namespace as well as submitting
+# jobs to this namespace, without allowing access to view log output or inspect
+# the filesystem.
+namespace "default" {
+  capabilities = [
+    "csi-read-volume",
+    "csi-list-volume",
+    "submit-job",
+    "list-jobs",
+    "read-job",
+    "parse-job",
+    "read-job-scaling",
+    "list-scaling-policies",
+    "read-scaling-policy",
+  ]
+}
+```
+
+Namespace definitions may also include wildcard symbols, also called globs,
+allowing a single policy definition to apply to a set of namespaces. For
+example, the below policy allows read access to most production namespaces, but
+allows write access to the "production-api" namespace, and rejects any access to
+the "production-web" namespace.
+
+```hcl
+namespace "production-*" {
+  policy = "read"
+}
+
+namespace "production-api" {
+  policy = "write"
+}
+
+namespace "production-web" {
+  policy = "deny"
+}
+```
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. Node rules are specified for all nodes using
+the `node` key:
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+There's only one node rule allowed per Nomad ACL Policy, and its value is set to
+one of the policy dispositions.
+
+## Agent rules
+
+The `agent` rule controls access to the utility operations in the [Agent
+API][api_agent], such as join and leave. Agent rules are specified for all
+agents using the `agent` key:
+
+```hcl
+agent {
+  policy = "write"
+}
+```
+
+There's only one agent rule allowed per Nomad ACL Policy, and its value is set
+to one of the policy dispositions.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator].
+Operator rules look like:
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+There's only one operator rule allowed per Nomad ACL Policy, and its value is
+set to one of the policy dispositions. In the example above, the token could be
+used to query the operator endpoints for diagnostic purposes but not make any
+changes.
+
+## Quota rules
+
+The `quota` policy controls access to the quota specification operations in the
+[Quota API][api_quota], such as quota creation and deletion. Quota rules
+are specified for all quotas using the `quota` key:
+
+```hcl
+quota {
+  policy = "write"
+}
+```
+
+There's only one quota rule allowed per Nomad ACL Policy, and its value is set
+to one of the policy dispositions.
+
+## Host Volume rules
+
+The `host_volume` policy controls access to mounting and accessing host volumes.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are keyed to the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes. In addition to the coarse grained policy specification, the
+`host_volume` stanza allows setting a more fine grained list of capabilities.
+This includes:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+- `deny` policy - ["deny"]
+
+- `read` policy - ["mount-readonly"]
+
+- `write` policy - ["mount-readonly", "mount-readwrite"]
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+<Note>
+
+ Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+</Note>
+
+## Plugin rules
+
+The `plugin` policy controls access to [CSI plugins][api_plugins],
+such as listing plugins or getting plugin status. Plugin rules are
+specified for all plugins using the `plugin` key:
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+There's only one plugin rule allowed per Nomad ACL Policy, and its
+value is set to one of the policy dispositions. In the example above,
+the token could be used to query the plugin endpoints for diagnostic
+purposes. Note that registering plugins is controlled by the
+`csi-register-plugin` policy for the plugin job's namespace.
+
+## Next steps
+
+Now that you have learned the basic building blocks of Nomad's ACL policies, the
+next section allows you to put this knowledge into practice.
+
+[hcl]: https://github.com/hashicorp/hcl/
+[api_agent]: /nomad/api-docs/agent
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_jobs]: /nomad/api-docs/jobs
+[api_node]: /nomad/api-docs/nodes
+[api_operator]: /nomad/api-docs/operator
+[api_quota]: /nomad/api-docs/quotas
+[api_policy]: /nomad/api-docs/acl/policies
+[api_plugins]: /nomad/api-docs/plugins
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/tokens/index.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/tokens/index.mdx
new file mode 100644
index 0000000000..ad4eb9cd62
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/tokens/index.mdx
@@ -0,0 +1,325 @@
+---
+layout: docs
+page_title: ACL tokens overview
+description: |-
+  Create a management token and a client token and use them to submit requests with the Nomad CLI.
+products_used:
+---
+
+# ACL tokens overview
+
+Nomad uses tokens to authenticate requests to the cluster. These tokens are
+created using the `nomad acl token create` command. When a token is being
+created, the operator can specify one or more policies to apply to the token.
+These policies determine if any action specified by the token bearer is
+authorized. This guide will demonstrate this process and teach you how to
+inspect existing tokens.
+
+If you completed the [Bootstrap Nomad ACL System][] guide, you generated a
+management token during bootstrap. For this guide, you will need to have
+either that token or another management token set in the NOMAD_TOKEN environment
+variable. Replace `BOOTSTRAP_SECRET_ID` in the following command with a
+bootstrap or management token:
+
+```shell
+## Store our token secret ID
+$ export NOMAD_TOKEN="BOOTSTRAP_SECRET_ID"
+```
+
+## Examine a token
+
+You can use the `nomad acl token self` command to get the information about your
+current token. Remember, you must have the token in the NOMAD_TOKEN environment
+variable or pass it in via the -token flag.
+
+```shell-session
+$ nomad acl token self
+Accessor ID  = 59baab4d-1c7b-9605-37e5-5690ec7e6c3a
+Secret ID    = 948bb149-8266-904d-8824-58b25529a8ca
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2020-01-23 18:51:33.446571 +0000 UTC
+Create Index = 9
+Modify Index = 9
+```
+
+### Token internals
+
+A token contains:
+
+- **Accessor ID** - The public identifier for a specific token. It can be
+  used to look up information about a token or to revoke a token.
+
+- **Secret ID** - Used to make requests to Nomad and should be kept private
+
+- **Name** (optional) - A user-supplied identifier.
+
+- **Type** - Shows the type of the token. Management tokens are used for
+  administration and can be thought of as root-level tokens. Client tokens are
+  used for applications and can have policies assigned to them at creation.
+
+- **Global** - (bool) Indicates whether or not the token was created with the
+  `--global` flag. Global tokens are replicated from the authoritative region to
+  other connected regions in the cluster.
+
+- **Policies** - ([string]) A list of the policies assigned to the token.
+
+- **Create Time** - Wall clock time on the Nomad server leader when the token
+  was generated.
+
+- **Create/Modification index** - Used by Nomad internally to determine when a
+  token was created and/or modified relative to other system events.
+
+### Token types
+
+You can observe in the output above that the token in question is a management
+token, but what is a Nomad token type?
+
+There are two types of tokens: management and client tokens.
+
+Management tokens can perform any action in your cluster. Because they allow all
+requests, they can not be associated with a policy.
+
+Client tokens are associated with one or more policies when they are created,
+and can perform an action if any associated policy allows it.
+
+Tokens can be associated with policies that do not exist, which is equivalent to
+granting no capabilities.
+
+### Token replication settings
+
+Nomad has two token types: local and global. Local tokens are created and stored
+within the current Nomad region. However, for multi-region clusters, you can
+also create global tokens which are created in the authoritative region and
+replicated to the other regions.
+
+Nomad creates local tokens by default. They can not be used for cross-region
+requests since they are not replicated between regions.
+
+When ACL tokens are created, you can optionally mark them as Global. Global
+tokens are created in the authoritative region and then replicate to all other
+regions.
+
+Use the `-global` flag on the [`nomad acl token create`][cli_create_token]
+command or set the ["Global" parameter] to `true` in your [Create Token API
+call][api_create_token] to create global tokens.
+
+### Token names
+
+Token names are optional information that is provided by the user at creation
+time. Token names can be used for human-readable values, like "Bootstrap Token"
+on tokens that Nomad creates during the bootstrap process. Token names are not
+required to be unique and can not be used for identification of a specific
+token.
+
+You can store up to 256 characters in the token name, so it can also be used for
+machine generated identifiers. You can use Unicode in this field as well:
+
+```shell-session
+$ nomad acl token create -name="🤞"
+Accessor ID  = c46ba94a-0653-4135-a5e7-aaa307e64e9b
+Secret ID    = 1783bc34-ad82-4f82-d36e-e2def1fe8453
+Name         = 🤞
+Type         = client
+Global       = false
+Policies     = []
+Create Time  = 2020-01-23 19:22:51.196728 +0000 UTC
+Create Index = 42
+Modify Index = 42
+```
+
+### Generate a management token
+
+Management tokens are necessary for working with the Nomad ACL API. You can have
+as many management tokens as you like. They are revocable at any time by another
+management token. However, if you lose all of your management tokens, you will
+have to re-bootstrap your ACL subsystem.
+
+Create a management token:
+
+```shell-session
+$ nomad acl token create -name="New Management Token" -type="management"
+Accessor ID  = a57be18f-31ed-a8f9-682c-be9b16d5db77
+Secret ID    = 775b2821-e0f4-3ad9-0f69-44d973daf737
+Name         = New ManagementToken
+Type         = management
+Global       = false
+Policies     = n/a
+Create Time  = 2020-01-23 19:32:25.078669 +0000 UTC
+Create Index = 53
+Modify Index = 53
+```
+
+Your token material will be different. Load this management token into your
+environment for the next step. Replace the token with the **Secret ID** from the
+output of the token create command.
+
+```shell-session
+$ export NOMAD_TOKEN=775b2821-e0f4-3ad9-0f69-44d973daf737
+```
+
+### Generate a client token
+
+The primary token type used in an ACL-enabled cluster is a "client" token.
+Client tokens allow you to specify one or more policies when creating a token.
+The policies determine what Nomad resources that the token-bearer has access to.
+
+Create a client token called "client1" that is associated with the policies
+"app1" and "app2". It does not matter that these policies do not yet exist.
+Nonexistent policies provide no capabilities to a token, but they will not cause
+an error.
+
+```shell-session
+$ nomad acl token create -name="client1" -policy="app1" -policy="app2"
+Accessor ID  = a7bef400-a66c-d163-52c4-5ff4978f19b8
+Secret ID    = 950e462b-b333-dd52-1e18-76837e9b97fa
+Name         = client1
+Type         = client
+Global       = false
+Policies     = [app1 app2]
+Create Time  = 2020-01-23 20:10:11.600915 +0000 UTC
+Create Index = 19
+Modify Index = 19
+```
+
+Generate a global token named "client2" that has access to the app2 policy.
+
+```shell-session
+$ nomad acl token create -name="client2" -global -policy="app2"
+Accessor ID  = ab3b15dc-1647-a81d-c637-90be45440d18
+Secret ID    = 6d164ce7-c8b8-82a2-a350-bb0bcb43010a
+Name         = client2
+Type         = client
+Global       = true
+Policies     = [app2]
+Create Time  = 2020-01-23 20:42:00.683964 +0000 UTC
+Create Index = 53
+Modify Index = 53
+```
+
+## Use a token
+
+You can provide a token for CLI commands in two ways:
+
+- Use the -token flag. Be mindful that flags must come before positional
+  parameters.
+
+  ```shell-session
+  $ nomad acl token self -token=05392bd8-bb8a-8f63-a405-53c87b0d7d63
+  ```
+
+  or
+
+  ```shell-session
+  $ nomad job run -token=05392bd8-bb8a-8f63-a405-53c87b0d7d63 example.nomad.hcl
+  ```
+
+- Set the NOMAD_TOKEN environment variable. An advantage of this approach is
+  that you do no longer have to be concerned with argument ordering.
+
+  ```shell-session
+  $ export NOMAD_TOKEN="«Token to use»"
+  $ nomad status
+  No running jobs
+  ```
+
+For direct API calls, you will need to supply the token using the
+"X-Nomad-Token" header. This can be paired nicely with the NOMAD_TOKEN
+environment variable or can be passed directly. This example requires you to
+have set the NOMAD_ADDR environment variable to the protocol, address, and port
+for your NOMAD API, e.g. `http://127.0.0.1:4646`.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/jobs
+[]
+```
+
+## Inspect a token via accessor
+
+Token accessors are the unique public identifier for a token. They can be safely
+stored in the clear and are used by management token-bearers to get information
+about a token, update a token, or revoke a token.
+
+Use the accessor for the "client1" token to inspect it.
+
+```shell-session
+$ nomad acl token info a7bef400-a66c-d163-52c4-5ff4978f19b8
+Accessor ID  = a7bef400-a66c-d163-52c4-5ff4978f19b8
+Secret ID    = 950e462b-b333-dd52-1e18-76837e9b97fa
+Name         = client1
+Type         = client
+Global       = false
+Policies     = [app1 app2]
+Create Time  = 2020-01-23 20:10:11.600915 +0000 UTC
+Create Index = 19
+Modify Index = 19
+```
+
+You can get this same data from the API:
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  ${NOMAD_ADDR}/v1/acl/token/a7bef400-a66c-d163-52c4-5ff4978f19b8\?pretty
+{
+    "AccessorID": "a7bef400-a66c-d163-52c4-5ff4978f19b8",
+    "CreateIndex": 19,
+    "CreateTime": "2020-01-23T20:10:11.600915Z",
+    "Global": false,
+    "Hash": "bY2538leml33LX7mIIBYT2ngBDMhpie065x+4/pQWJ0=",
+    "ModifyIndex": 19,
+    "Name": "client1",
+    "Policies": [
+        "app1",
+        "app2"
+    ],
+    "SecretID": "950e462b-b333-dd52-1e18-76837e9b97fa",
+    "Type": "client"
+}
+```
+
+## Delete a token via accessor
+
+Sometimes a token needs to be revoked. You can do that by running the `nomad acl token delete` command and supplying the accessor of the token to revoke. You must
+use a management token to run this command.
+
+Clean up the three tokens you made in this guide. Switch to the first token you
+used in the start of the guide:
+
+```shell-session
+$ export NOMAD_TOKEN=«original token»
+```
+
+Run the `nomad acl token delete` command and pass in the accessor of the created
+tokens. The example output below uses the token IDs from the earlier examples.
+
+Revoke the client1 token.
+
+```shell-session
+$ nomad acl token delete a7bef400-a66c-d163-52c4-5ff4978f19b8
+Token a7bef400-a66c-d163-52c4-5ff4978f19b8 successfully deleted
+```
+
+Revoke client2.
+
+```shell-session
+$ nomad acl token delete ab3b15dc-1647-a81d-c637-90be45440d18
+Token ab3b15dc-1647-a81d-c637-90be45440d18 successfully deleted
+```
+
+Revoke the "New Management Token".
+
+```shell-session
+$ nomad acl token delete a57be18f-31ed-a8f9-682c-be9b16d5db77
+Token a57be18f-31ed-a8f9-682c-be9b16d5db77 successfully deleted
+```
+
+## Next steps
+
+Next, you will explore policy creation in Nomad through a scenario.
+
+["global" parameter]: /nomad/api-docs/acl/tokens#global
+[api_create_token]: /nomad/api-docs/acl/tokens#create-token
+[cli_create_token]: /nomad/commands/acl/token/create
+[bootstrap nomad acl system]: /nomad/docs/secure/acl/bootstrap
diff --git a/content/nomad/v1.10.x/content/docs/secure/acl/tokens/vault.mdx b/content/nomad/v1.10.x/content/docs/secure/acl/tokens/vault.mdx
new file mode 100644
index 0000000000..f0fe284932
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/acl/tokens/vault.mdx
@@ -0,0 +1,176 @@
+---
+layout: docs
+page_title: Generate tokens with Vault
+description: |-
+  Configure the Nomad secrets engine in Vault and retrieve Vault-managed tokens
+  for the Nomad ACL system.
+products_used:
+---
+
+# Generate tokens with Vault
+
+HashiCorp Vault has a secrets engine for generating short-lived Nomad tokens. As
+Vault has a number of authentication backends, it could provide a workflow where
+a user or orchestration system authenticates using an pre-existing identity
+service (LDAP, Okta, Amazon IAM, etc.) in order to obtain a short-lived Nomad
+token.
+
+~> HashiCorp Vault is a standalone product with its own set of deployment and
+configuration best practices. You should review the [Vault Deployment Guide]
+before deploying it in production.
+
+In order to configure Vault's Nomad secrets engine, you will need the following:
+
+- A Nomad cluster with bootstrapped ACL system.
+
+- A management token (You can use the bootstrap token; however, for production
+  systems you should use an integration-specific token)
+
+- A set of policies created in Nomad
+
+- An unsealed Vault server running v0.9.3 or later
+
+- For evaluation purposes, a Vault server in "dev" mode can be used.
+
+  ```shell-session
+  $ vault server -dev
+  ==> Vault server configuration:
+
+                       Cgo: disabled
+           Cluster Address: https://127.0.0.1:8201
+                Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
+                 Log Level: info
+                     Mlock: supported: false, enabled: false
+          Redirect Address: http://127.0.0.1:8200
+                   Storage: inmem
+                   Version: Vault v0.8.3
+               Version Sha: a393b20cb6d96c73e52eb5af776c892b8107a45d
+
+  ==> WARNING: Dev mode is enabled!
+
+  In this mode, Vault is completely in-memory and unsealed.
+  Vault is configured to only have a single unseal key. The root
+  token has already been authenticated with the CLI, so you can
+  immediately begin using the Vault CLI.
+
+  The only step you need to take is to set the following
+  environment variables:
+
+      export VAULT_ADDR='http://127.0.0.1:8200'
+
+  The unseal key and root token are reproduced below in case you
+  want to seal/unseal the Vault or play with authentication.
+
+  Unseal Key: YzFfP...
+  Root Token: f84b587e-...
+  ```
+
+## Configure Nomad secrets engine
+
+Enable the [`nomad`][nomad_backend] secrets backend in Vault:
+
+```shell-session
+$ vault secrets enable nomad
+Success! Enabled the nomad secrets engine at: nomad/
+```
+
+For older versions of Vault, you might need to use the `vault mount` command instead.
+
+```shell-session
+$ vault mount nomad
+Successfully mounted 'nomad' at 'nomad'!
+```
+
+Once you have the Nomad secret backend enabled, configure access with Nomad's address and management token:
+
+```shell-session
+$ vault write nomad/config/access \
+    address=http://127.0.0.1:4646 \
+    token=adf4238a-882b-9ddc-4a9d-5b6758e4159e
+Success! Data written to: nomad/config/access
+```
+
+Vault secrets engines have the concept of roles, which are configuration units
+that group one or more Vault policies to a potential identity attribute, (e.g.
+LDAP Group membership). The name of the role is specified on the path, while the
+mapping to policies is done by naming them in a comma separated list, for
+example:
+
+```shell-session
+$ vault write nomad/role/role-name policies=policyone,policytwo
+Success! Data written to: nomad/role/role-name
+```
+
+Similarly, to create management tokens, or global tokens:
+
+```shell-session
+$ vault write nomad/role/role-name type=management global=true
+Success! Data written to: nomad/role/role-name
+```
+
+## Create Vault policy
+
+Create a Vault policy to allow different identities to get tokens associated
+with a particular role:
+
+```shell-session
+$ cat << EOF | vault policy write nomad-user-policy -
+path "nomad/creds/role-name" {
+  capabilities = ["read"]
+}
+EOF
+Policy 'nomad-user-policy' written.
+```
+
+If you have an existing authentication backend (like LDAP), follow the relevant
+instructions to create a role available on the [Authentication backends
+page](/vault/docs/auth). Otherwise, for testing
+purposes, a Vault token can be generated associated with the policy:
+
+```shell-session
+$ vault token create -policy=nomad-user-policy
+Key             Value
+---             -----
+token           deedfa83-99b5-34a1-278d-e8fb76809a5b
+token_accessor  fd185371-7d80-8011-4f45-1bb3af2c2733
+token_duration  768h0m0s
+token_renewable true
+token_policies  [default nomad-user-policy]
+```
+
+## Obtain and test Nomad token
+
+Finally obtain a Nomad Token using the existing Vault Token:
+
+```shell-session
+$ vault read nomad/creds/role-name
+Key             Value
+---             -----
+lease_id        nomad/creds/role-name/6fb22e25-0cd1-b4c9-494e-aba330c317b9
+lease_duration  768h0m0s
+lease_renewable true
+accessor_id     10b8fb49-7024-2126-8683-ab355b581db2
+secret_id       8898d19c-e5b3-35e4-649e-4153d63fbea9
+```
+
+Verify that the token is created correctly in Nomad, looking it up by its
+accessor:
+
+```shell-session
+$ nomad acl token info 10b8fb49-7024-2126-8683-ab355b581db2
+Accessor ID  = 10b8fb49-7024-2126-8683-ab355b581db2
+Secret ID    = 8898d19c-e5b3-35e4-649e-4153d63fbea9
+Name         = Vault test root 1507307164169530060
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-10-06 16:26:04.170633207 +0000 UTC
+Create Index = 228
+Modify Index = 228
+```
+
+Any user or process with access to Vault can now obtain short lived Nomad Tokens
+in order to carry out operations, thus centralizing the access to Nomad tokens.
+
+[nomad_backend]: /vault/docs/secrets/nomad
+[Vault deployment guide]: /vault/tutorials/day-one-raft/raft-deployment-guide
diff --git a/content/nomad/v1.10.x/content/docs/secure/authentication/jwt.mdx b/content/nomad/v1.10.x/content/docs/secure/authentication/jwt.mdx
new file mode 100644
index 0000000000..9691f4d25e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/authentication/jwt.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: JSON Web Token (JWT) Auth Method
+description: >-
+  Use the JWT auth method to authenticate to Nomad with a JSON web token and receive an ACL token with privileges based on JWT identity attributes. Learn how to configure the auth method parameters using this reference page and example configuration.
+---
+
+# JSON Web Token (JWT) Auth Method
+
+Use the `jwt` auth method to authenticate with Nomad by providing a
+[JWT](https://en.wikipedia.org/wiki/JSON_Web_Token) directly. The JWT is
+cryptographically verified using locally-provided keys, or, if configured, you may use an
+OIDC Discovery service to fetch the appropriate keys.
+
+Refer to [auth-method create] for the parameters required to create a JWT auth-method with a given verification method.
+
+## JWT Verification
+
+Nomad verifies JWT signatures against public keys from the issuer. This
+process uses one of these methods:
+
+- **Static Keys** - A set of public keys is stored directly in the
+  configuration.
+
+- **JWKS** - Configure a JSON Web Key Set ([JWKS](https://tools.ietf.org/html/rfc7517))
+  URL and optional certificate chain. Nomad fetches keys from
+  this endpoint during authentication.
+
+- **OIDC Discovery** - Configure an OIDC Discovery URL and optional certificate chain. Nomad fetches keys from this URL during authentication. When you use OIDC Discovery, Nomad applies OIDC validation criteria such as `iss` and `aud`.
+
+If you need multiple methods, create another auth method of this type
+with a different name.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[auth-method create]: /nomad/commands/acl/auth-method/create
diff --git a/content/nomad/v1.10.x/content/docs/secure/authentication/oidc.mdx b/content/nomad/v1.10.x/content/docs/secure/authentication/oidc.mdx
new file mode 100644
index 0000000000..6c7659ce02
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/authentication/oidc.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: OpenID Connect (OIDC) Authentication Method
+description: >-
+  Use the OIDC auth method type to authenticate to Nomad through a web browser with an OpenID Connect provider. Learn how to configure the authentication method parameters using this reference page and example configuration.
+---
+
+# OpenID Connect (OIDC) Authentication Method
+
+Use the `oidc` method to authenticate to Nomad with
+[OIDC](https://en.wikipedia.org/wiki/OpenID_Connect). This method allows
+authentication via a configured OIDC provider using the user's web browser.
+Initiate this method from the Nomad UI or the command line.
+
+## Prerequisites
+
+- General knowledge of [OIDC concepts](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1)
+- [Nomad Access Control List fundamentals][ACL Overview].
+
+Refer to [auth-method create] for the parameters required to create an OIDC auth-method.
+
+## JWT Verification
+
+Nomad uses OIDC discovery to verify JWT signatures against public
+keys from the issuer. Nomad first fetches keys from the OIDC
+Discovery URL during authentication and then applies OIDC
+validation criteria such as `iss` and `aud`.
+
+## OIDC Authentication
+
+Nomad includes two built-in OIDC login flows: the Nomad UI, and the CLI using
+[`nomad login`](/nomad/commands/login).
+
+### Redirect URIs
+
+Properly setting redirect URIs is an important part of OIDC auth method
+configuration. You must configure these in both Nomad and the OIDC
+provider, and these configurations must align.
+
+Specify the redirect URIs for an auth method with the
+`AllowedRedirectURIs` parameter in the auth method config. The Nomad UI
+and CLI use different redirect URIs, so you need to configure one or both,
+depending on your installation.
+
+**Note:** Redirect URI is used interchangeably with callback address.
+
+Logging in via the UI requires the redirect URI
+`http://{host:port}/ui/settings/tokens`.
+
+Logging in via the CLI requires the redirect
+URI `http://{host:port}/oidc/callback`.
+
+### OIDC Login
+
+#### Nomad UI
+
+1. Select one of the provider links in the Nomad homepage or navigate directly to `/ui/settings/tokens`.
+1. Click one of the buttons for your OIDC auth method of choice.
+1. Complete the authentication with the configured provider.
+
+#### CLI
+
+Execute the `nomad login -method=oidc` command to log in.
+If the `-oidc-callback-addr` flag is not specified, it will default to `localhost:4649`.
+
+```shell-session
+$ nomad login -method=oidc -oidc-callback-addr=<host:port>
+
+Complete the login via your OIDC provider. Launching browser to:
+
+    https://myco.auth0.com/authorize?redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&client_id=r3qXc2bix9eF...
+```
+
+Your browser opens to the generated URL to complete the provider's login.
+Enter the URL manually if the browser does not automatically open.
+
+### Client assertions
+
+Also known as "[private key JWT][]", client assertions offer a more secure
+authentication mechanism compared to client secrets.
+
+Instead of sending a simple secret, Nomad builds a JWT and signs it with
+an RSA private key (or HMAC) that the OIDC provider can verify with an
+associated public key (or the same HMAC). In this way, Nomad "asserts"
+that it is a valid OIDC client without sending any secret information over
+the network.
+
+Here are some partial [auth method configuration][] examples. They focus only
+on the client assertion feature; they are not complete, functional examples.
+
+#### Nomad keyring
+
+In this example for Keycloak, Nomad signs the JWT with its own internal private
+key. It sets the JWT's "kid" header as the key ID, as presented by Nomad's
+[jwks.json][] endpoint.
+
+This is arguably the most secure option, because only Nomad has the private key.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://your-keycloak-instance.com/realms/nomad",
+  "OIDCClientID": "{your-client-id}",
+  "BoundAudiences": ["{your-client-id}"],
+  "OIDCClientAssertion": {
+    "Audience": ["https://your-keycloak-instance.com/realms/nomad"],
+    "KeySource": "nomad"
+  }
+}
+```
+
+Notice the distinction between the two "audience" fields:
+* `BoundAudiences` is often the application client ID (Nomad being the client),
+  which Nomad verifies against what the OIDC provider sends to Nomad. Nomad
+  uses this to make sure that requests are for Nomad, and not some other client.
+  This applies to all OIDC configuration, not only client assertions.
+* `OIDCClientAssertion.Audience` is the OIDC provider, because that is the
+  target audience of the client assertion JWT. The provider uses this to make
+  sure that requests are for it and not some other provider. This is often the
+  same as the `OIDCDiscoveryURL`, so defaults to that. This applies to all
+  client assertion configuration.
+
+This option requires that the OIDC provider have network access to Nomad's JWKS,
+either directly or via proxy, but otherwise requires no extra management of key
+material beyond Nomad's built-in [keyring][key-management].
+
+#### User provided key
+
+This Microsoft Entra ID (formerly Azure Active Directory) example uses an RSA
+private key generated separately from Nomad to sign the JWT.
+- The `PemKey` value is the private RSA key contents in PEM format.
+- The `PemCert` value is the contents of an X509 certificate from the key or a
+  CA. Nomad uses this certificate to derive an [x5t#S256][] thumbprint header.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://login.microsoftonline.com/{tenant}/v2.0",
+  "OIDCClientID": "{app-client-id}",
+  "BoundAudiences": ["{app-client-id}"],
+  "OIDCClientAssertion": {
+    "KeySource": "private_key",
+    "KeyAlgorithm": "RS256",
+    "PrivateKey": {
+      "PemKey": "-----BEGIN RSA PRIVATE KEY-----\nMIIE...the-rest-of-the-key...uJ8fR\n-----END RSA PRIVATE KEY-----",
+      "PemCert": "-----BEGIN CERTIFICATE-----\nMIID...the-rest-of-the-cert...GUCk=\n-----END CERTIFICATE-----"
+    }
+  }
+}
+```
+
+Note that if you implement this approach, you must upload the certificate to
+the Entra ID app, so that when you try to log in, Entra ID can use the
+"x5t#S256" header to look up the public key that it has stored.
+
+You may also configure the key and/or certificate as filenames on disk on Nomad
+servers with the `PemKeyFile` and `PemCertFile` options, respectively. This
+approach lets you rotate your key/cert without needing to update the auth
+method, but the files must be present on the disk of any server that may become
+Nomad leader.
+
+Or, depending on your OIDC provider's requirements, you may provide the `KeyID`
+directly, instead of providing a certificate.
+
+This approach lets you bring your own RSA key for the following scenarios:
+- Your OIDC provider does not support JWKS
+- Your network topology does not allow connectivity between the provider and
+Nomad JWKS, even via proxy
+- You want a signing key that is specifically and only for this purpose.
+
+#### Client secret HMAC
+
+This example uses the `OIDCClientSecret` as an HMAC key to sign the JWT.
+This configuration is marginally more secure than a bare client secret, as the
+JWT is time-bound, and signed by the secret rather than sending the secret
+itself over the network. As with a normal client secret, both Nomad and the
+OIDC provider need to have the same secret.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://your-oidc-provider.com/oidc-discovery-url",
+  "OIDCClientID": "your-client-id",
+  "OIDCClientSecret": "long-secret-id-has-to-be-at-least-32-bytes",
+  "OIDCClientAssertion": {
+    "KeySource": "client_secret"
+  }
+}
+```
+
+## OIDC Configuration Troubleshooting
+
+The amount of configuration required for OIDC is relatively small, but it can
+be tricky to debug why things aren't working. The following are tips for setting up OIDC:
+
+- Monitor the log output for the Nomad servers for important
+information about OIDC validation failures.
+
+- Ensure correct redirect URIs in Nomad and on the provider. URIs
+need to match exactly. Check http/https, 127.0.0.1/localhost,
+port numbers, and whether trailing slashes are present.
+
+- The `BoundAudiences` option is typically
+  not required. OIDC providers use the `client_id` as the audience and
+  OIDC validation expects this.
+
+- Check your provider for scopes that are required to receive all of
+  the information you need. You often need to request the scopes
+  `profile` and `groups`, which you may set with
+  `OIDCScopes=["profile", "groups"]` in the auth method configuration.
+
+- If you're seeing claim-related errors in logs, review the provider's docs
+  very carefully to see how they're naming and structuring their claims.
+  Depending on the provider, you may be able to construct a simple `curl`
+  [implicit grant](https://developer.okta.com/blog/2018/05/24/what-is-the-oauth2-implicit-grant-type)
+  request to obtain a JWT that you can inspect. This example decodes the
+  JWT located in the `access_token` field of a JSON response.
+
+      jq --raw-output '.access_token / "." | .[1] | @base64d' jwt.json
+
+- With debug level logging, use the [VerboseLogging] option in the auth
+  method configuration to log the received OIDC token. This can be helpful
+  when debugging provider setup and verifying that the received claims are
+  what you expect. Since claims data is logged verbatim and may contain
+  sensitive information, do not use this option in production.
+
+- For client assertions, if `VerboseLogging` is enabled, then the Nomad leader
+  server logs a JWT when the auth method is created, and when someone makes
+  a login attempt. These JWTs are not 100% identical to what gets sent to the
+  OIDC provider due to being time-bound, but you can check the JWT headers
+  and claims to compare with your OIDC provider's requirements.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[ACL Overview]: /nomad/docs/secure/acl
+[auth-method create]: /nomad/commands/acl/auth-method/create
+[private key jwt]: https://oauth.net/private-key-jwt/
+[auth method configuration]: /nomad/api-docs/acl/auth-methods
+[key-management]: /nomad/docs/manage/key-management
+[x5t#S256]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8
+[jwks.json]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[VerboseLogging]: /nomad/api-docs/acl/auth-methods#verboselogging
diff --git a/content/nomad/v1.10.x/content/docs/secure/authentication/sso-auth0.mdx b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-auth0.mdx
new file mode 100644
index 0000000000..3469ff6584
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-auth0.mdx
@@ -0,0 +1,357 @@
+---
+layout: docs
+page_title: Configure SSO with Auth0
+description: |-
+  Create and configure an Auth0 application for SSO in Nomad, set up Nomad
+  ACL policies and roles, and configure binding rules to assign user permissions
+  automatically.
+---
+
+# Configure SSO with Auth0
+
+OIDC authentication is useful when you want to deploy SSO widely in your
+organization and do not want to manage access solely with Nomad access control
+list (ACL) tokens.
+
+Once implemented, SSO enables an interactive login procedure that users may
+initiate from either the Nomad UI or CLI.
+
+In this guide, you configure [Auth0](https://auth0.com/) as an identity
+provider. Your configuration uses the user metadata in Auth0 to automatically
+grant permissions in Nomad ACL.
+
+This is a multi-step process that includes the following:
+
+- Configuring an application in Auth0 for Nomad integration
+- Creating a role and user in Auth0
+- Setting up Nomad ACL policies and roles to provide permissions to users
+- Using Nomad binding rules to automatically assign permissions to users based on their metadata values
+
+You should be familiar with Auth0 and the following Auth0 documentation:
+
+- [Understand How Metadata Works in User
+  Profiles](https://auth0.com/docs/manage-users/user-accounts/metadata)
+- [Manage User Metadata with the post-login Action
+  Trigger](https://auth0.com/docs/manage-users/user-accounts/metadata/manage-user-metadata)
+- [Login Trigger - Add user roles to ID and Access
+  tokens](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#add-user-roles-to-id-and-access-tokens)
+
+## Prerequisites
+
+In order to complete this guide, you need:
+
+- A Nomad cluster with ACLs enabled and bootstrapped. Refer to [Bootstrap the
+  ACL system](/nomad/docs/secure/acl/bootstrap) for instructions.
+- The [Nomad ACL management token](/nomad/docs/secure/acl/tokens#token-types)
+  for your cluster. Assign the value to an environment variable named
+  `NOMAD_TOKEN` in your local terminal session.
+- A valid [Auth0](https://auth0.com/) account.
+
+Refer to the [Nomad Quick Start tutorial](/nomad/tutorials/get-started) if you
+need to set up a cluster.
+
+## Set up Auth0
+
+1. Create a native application. Refer to the Auth0 [Create Applications
+   guide](https://auth0.com/docs/get-started/auth0-overview/create-applications)
+   for instructions.
+
+   - Note the **Domain**, **Client ID**, and **Client Secret** values. You use
+   these to configure an auth method in Nomad.
+   - Set the callback URLs that Auth0 uses to redirect the user after the
+      authentication process is complete. In the **Allowed Callback URLs**
+      field, enter the following:
+
+      - `<NOMAD_ADDRESS>/ui/settings/tokens`: This is the callback
+     address when you perform OIDC login with the Nomad web UI. If you are
+     running Nomad with a modified [HTTP
+     port](/nomad/docs/configuration#http-2), ensure that the UI address uses
+     this value.
+      - `http://localhost:4649/oidc/callback`: This is the callback address that
+     the Nomad CLI uses when you perform [OIDC login using the
+     CLI](https://developer.hashicorp.com/nomad/commands/login#examples).
+
+     In this example, the Nomad address is `http://3.145.29.13:4646`.
+
+      ```plaintext
+      http://3.145.29.13:4646/ui/settings/tokens,
+      http://localhost:4649/oidc/callback
+      ```
+
+1. Create a role called `engineering`. Refer to the the Auth0 [Create Roles
+   guide](https://auth0.com/docs/manage-users/access-control/configure-core-rbac/roles/create-roles)
+   for instructions.
+1. Create a user with a connection type of `Username-Password-Authentication`.
+   Assign the `engineering` role to that user. Refer to these Auth0 guides for
+   instructions:
+
+   - [Create Users](https://auth0.com/docs/manage-users/user-accounts/create-users)
+   - [Assign Roles to Users](https://auth0.com/docs/manage-users/access-control/configure-core-rbac/rbac-users/assign-roles-to-users)
+
+1. Create a [login
+   trigger](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger)
+   that adds user roles to the token that Auth0 sends back to Nomad.
+
+   1. Create a custom action to add custom claims to the token. Refer to the
+      Auth0 [Create an Action
+      section](https://auth0.com/docs/customize/actions/write-your-first-action#create-an-action)
+      for instructions.
+
+      Give your action these values:
+
+      - **Name**: `Nomad OIDC`
+      - **Trigger**: `Login/Post Login`
+
+      After you create the action, replace the `exports.onExecutePostLogin`
+      method with the method that sets a custom claim to [add user roles to the
+      tokens](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#add-user-roles-to-id-and-access-tokens).
+
+      ```javascript
+      exports.onExecutePostLogin = async (event, api) => {
+        const namespace = 'http://nomad.internal';
+        if (event.authorization) {
+          api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
+          api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
+        }
+      }
+      ```
+
+      You use the `http://nomad.internal` namespace to separate the claims that
+      are not part of the [JWT RFC](https://tools.ietf.org/html/rfc7519). The
+      namespace is arbitrary but must be unique. Auth0 enforces the presence of
+      a unique namespace by discarding claims that are not namespaced and not in
+      the RFC.
+
+      Click **Deploy** to deploy your Nomad OIDC action.
+
+   1. Create a [post-login
+      trigger](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#login-post-login).
+
+      1. From the Auth0 dashboard for your Nomad application, click on
+      **Actions** and then **Triggers**.
+      1. Select **post-login**.
+      1. In the **Add Action** pane's **Custom** tab, select **Nomad OIDC** and
+      drag it to the **Post Login** canvas so that the flow is **Start** ->
+      **Nomad OIDC** -> **Complete**.
+      1. Apply your changes.
+
+      ![Auth0 UI configure callback flow](/img/secure/auth0-configure-callback-flow.png)
+
+
+## Create Nomad ACL policies and roles
+
+After the login procedure confirms the user's identity, it has to then give that
+user privileges when creating their ACL token. Auth methods in Nomad use binding
+rules, which enable Nomad's ACL system to assign privilege to a new token
+through ACL policies and roles.
+
+In order to assign a privilege to a token with an auth method, first
+define the privilege in a policy and then assign that policy to a role. In this
+way, the binding rule can reference the role by name.
+
+### Define policy for Auth0 users
+
+Create a policy named `engineering-read` to allow read-only access to the `“default”` namespace and
+node objects.
+
+Create a policy file named `default-read.hcl`, add the following configuration to it, and save the file.
+
+```hcl
+// Grants read access to the namespace “default”.
+namespace "default" {
+  policy = "read"
+}
+
+// Grants read access to Nomad nodes.
+node {
+  policy = "read"
+}
+```
+
+Submit the policy to Nomad.
+
+-> **Note**: Ensure that the NOMAD_TOKEN environment variable is set to your Nomad management token.
+
+```shell-session
+$ nomad acl policy apply engineering-read default-read.hcl
+Successfully wrote "engineering-read" ACL policy!
+```
+
+
+### Assign the policy to a role
+
+Next, create a role named `engineering-read` and link it to the policy.
+
+```shell-session
+$ nomad acl role create -name=engineering-read -policy=engineering-read
+ID           = fc6d21c9-31cf-fd12-fe9a-7636c07f2d97
+Name         = engineering-read
+Description  = <none>
+Policies     = engineering-read
+Create Index = 18
+Modify Index = 18
+```
+
+
+## Create the OIDC auth method for Nomad
+
+Create a configuration file named `auth-method-config.json` for the new auth
+method and add the following contents to it.
+
+<CodeBlockConfig filename="auth-method-config.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "https://<AUTH0_DOMAIN>/",
+  "OIDCClientID": "<AUTH0_CLIENT_ID>",
+  "OIDCClientSecret": "<AUTH0_CLIENT_SECRET>",
+  "BoundAudiences": ["<AUTH0_CLIENT_ID>"],
+  "AllowedRedirectURIs": [
+     "<NOMAD_ADDRESS>/ui/settings/tokens",
+     "http://localhost:4649/oidc/callback",
+  ],
+  "ListClaimMappings": {
+    "http://nomad.internal/roles": "roles"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Replace `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID`, and `AUTH0_CLIENT_SECRET` with the
+values for **Domain**, **Client ID**, and **Client Secret** that you noted in
+the [Set up your Auth0 application, role, and user
+section](#set-up-auth0).
+
+Make sure the `AllowedRedirectURIs` entries match the callback URLs you
+configured in Auth0.
+
+Create the auth method with the Nomad CLI or API.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad acl auth-method create` command to create the auth method. Note
+that the token time-to-live is set to five minutes. Refer to the [`nomad acl
+auth-method create` command reference](/nomad/commands/acl/auth-method/create)
+for a complete explanation of the options.
+
+```shell-session
+$ nomad acl auth-method create -type=OIDC \
+    -name=auth0 \
+    -default=true \
+    -max-token-ttl=5m \
+    -token-locality=global \
+    -config=@auth-method-config.json
+```
+
+</Tab>
+<Tab heading="API">
+
+Use the [ACL auth methods
+API](http://localhost:3000/nomad/api-docs/acl/auth-methods#create-auth-method)
+to create the auth method. The payload is the `auth-method-config.json` file.
+
+```shell-session
+$ curl -sL --header 'x-nomad-token: <MANAGEMENT_TOKEN>' --request POST \
+    <NOMAD_ADDRESS>/v1/acl/auth-method \
+    --data @auth-method-config.json
+```
+
+Replace the following placeholders:
+
+- `<MANAGEMENT_TOKEN>` with the value of your Nomad management token
+- `<NOMAD_ADDRESS>` with the address of your Nomad cluster, such as
+  `http://3.145.29.13:4646`
+
+</Tab>
+</Tabs>
+
+Once you have configured the auth method, you can automate permissions grants to
+users using the metadata you defined earlier. This means that once auth method
+trust is established, you can configure Nomad to bind attested identities to
+roles or services with no additional work beyond what is required to link the
+identity and the auth method. Configure this with Nomad binding rules.
+
+### Grant ACL role permissions with Auth0 app metadata
+
+Grant users in the `engineering` Auth0 role the Nomad ACL role named `engineering-read`.
+
+```shell-session
+$ nomad acl binding-rule create \
+    -auth-method=auth0 \
+    -bind-type=role \
+    -bind-name=engineering-read \
+    -selector='engineering in list.roles'
+```
+
+```plaintext hideClipboard
+ID           = afb29209-9a87-e042-1983-d4d0f70bf271
+Description  = <none>
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-read
+Create Time  = 2023-01-17 11:34:50.588734 +0000 UTC
+Modify Time  = 2023-01-17 11:34:50.588734 +0000 UTC
+Create Index = 22
+Modify Index = 22
+```
+
+This automatically associates every user with an `engineering` role in their
+Auth0 tokens to the Nomad `engineering-read` ACL Role associated with an ACL policy.
+
+## Log in with OIDC
+
+Now that the configuration is complete, log in to Nomad using Auth0.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the [`nomad login -method=auth0` CLI command](/nomad/commands/login) to log
+into Nomad. The `-oidc-callback-addr` parameter is optional and defaults to `locahost:4649`.
+
+```shell-session
+$ nomad login -method=auth0 -oidc-callback-addr=localhost:4649
+```
+
+The command redirects you to a browser page. When prompted, accept and authorize
+the Nomad access to your Auth0 App. Then log into Auth0 with
+the username and password that you created in the [Set up Auth0 section](#set-up-auth0).
+
+![Nomad UI post login page showing Signed in via OIDC](/img/secure/nomad-ui-oidc-signed-in.png)
+
+The CLI writes your ACL token to the console.
+
+```plaintext hideClipboard
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = f2e78673-cbe5-8a69-1ad1-d16c2b63e9bf
+Secret ID    = e3d937a3-fe2b-f144-8384-e4fcbe7e9a65
+Name         = OIDC-auth0
+Type         = client
+Global       = true
+Create Time  = 2023-01-17 11:40:36.48495 +0000 UTC
+Expiry Time  = 2023-01-17 11:50:36.48495 +0000 UTC
+Create Index = 17
+Modify Index = 17
+Policies     = []
+
+Roles
+ID                                    Name
+db1b4129-3b7b-f2f5-5118-b885a1ff226e  engineering-read
+```
+
+</Tab>
+
+<Tab heading="Nomad UI">
+
+Navigate to your Nomad web UI and click on the **Sign In** button. Then click
+the **Sign in with auth0** button to start the flow.
+
+![Nomad UI login page sso Auth0](/img/secure/nomad-ui-oidc-login-button.png)
+
+![Nomad UI login page sso Auth0](/img/secure/nomad-ui-oidc-login-form.png)
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.10.x/content/docs/secure/authentication/sso-pkce-jwt.mdx b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-pkce-jwt.mdx
new file mode 100644
index 0000000000..c1a3b3f8e6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-pkce-jwt.mdx
@@ -0,0 +1,1032 @@
+---
+layout: docs
+page_title: SSO with PKCE and private key JWT
+description: |-
+  Create and configure a Keycloak OIDC application for SSO in Nomad,
+  configure a Nomad auth method that uses PKCE and Private Key JWT, set up
+  Nomad ACL policies and roles, and configure binding rules to assign user
+  permissions automatically.
+---
+
+# SSO with PKCE and private key JWT
+
+OpenID Connect (OIDC) authentication lets you provide Nomad access control list (ACL) tokens to users when they log in using a single sign-on (SSO) provider.
+
+Nomad's OIDC SSO login feature includes these capabilities:
+- [Proof Key for Code Exchange](https://oauth.net/2/pkce/), also known as PKCE, adds extra security for both
+  traditional client secrets and client assertions.
+- [Private Key JWT](https://oauth.net/private-key-jwt/), also known as client assertions, is a more secure alternative to client secrets.
+
+These options offer extra security during the OIDC login flow. For a summary, refer to the [Nomad OIDC page](/nomad/docs/secure/authentication/oidc).
+
+To demonstrate how to use PKCE and Private Key JWT, this tutorial uses the open source [Keycloak identity provider application](https://www.keycloak.org/) running as a Nomad job. You will configure Nomad and Keycloak to automatically grant permissions in Nomad ACL, enable the Keycloak provider to require PKCE, and reconfigure the Keycloak provider to use client assertions.
+
+
+## Prerequisites
+
+For this tutorial, you will need:
+
+- The [Nomad CLI](/nomad/install) version 1.10.0 or higher installed locally
+- A Nomad v1.10 or higher cluster with ACLs enabled and bootstrapped, as well as:
+  - The ACL management token saved to the `NOMAD_TOKEN` environment variable
+  - Docker installed on the client node
+- [`openssl`](https://openssl-library.org/source/index.html) installed locally to generate client assertion certificates
+
+## Run Keycloak as a Nomad job
+
+This job specification [runs Keycloak in development mode](https://www.keycloak.org/nightly/server/containers#_trying_keycloak_in_development_mode) with the username `admin` and password `admin`. Copy the contents to a file and save the file as `keycloak.nomad.hcl`.
+
+<!--
+TODO: bug mentioned below in keycloak_tag variable
+- update version after this ships: https://github.com/keycloak/keycloak/commit/9ca134931b49932227b24a660cbdf926ba2f59bd
+- available tags: https://quay.io/repository/keycloak/keycloak?tab=tags
+-->
+
+<Tabs>
+
+<Tab group="mac" heading="MacOS">
+
+<CodeBlockConfig filename="keycloak.nomad.hcl">
+
+```hcl
+variable "keycloak_tag" {
+  default = "26.0.8" # newer versions have a certificate upload bug at the moment
+}
+
+job "keycloak" {
+  group "kc" {
+    network {
+      port "http" {
+        static = 8080
+      }
+    }
+    service {
+      name     = "keycloak"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "kc" {
+      driver = "docker"
+      config {
+        image        = "quay.io/keycloak/keycloak:${var.keycloak_tag}"
+        args         = ["start-dev", "--hostname", "http://${NOMAD_IP_http}:${NOMAD_PORT_http}"]
+        ports        = ["http"]
+        # note: keycloak config will be lost unless you use persistent storage.
+        #volumes = [
+        #  # /opt/keycloak-data on the host machine needs to be owned by user 1000
+        #  "/opt/keycloak-data:/opt/keycloak/data",
+        #]
+      }
+      env {
+        KC_BOOTSTRAP_ADMIN_USERNAME = "admin"
+        KC_BOOTSTRAP_ADMIN_PASSWORD = "admin"
+        PROXY_ADDRESS_FORWARDING    = true
+        KC_PROXY_HEADERS            = "xforwarded"
+      }
+      resources {
+        memory = 800
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+</Tab>
+
+<Tab group="linux" heading="Linux">
+
+<CodeBlockConfig filename="keycloak.nomad.hcl">
+
+```hcl
+variable "keycloak_tag" {
+  default = "26.0.8" # newer versions have a certificate upload bug at the moment
+}
+
+job "keycloak" {
+  group "kc" {
+    network {
+      mode = "host"
+      port "http" {
+        static = 8080
+      }
+    }
+    service {
+      name     = "keycloak"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "kc" {
+      driver = "docker"
+      config {
+        image        = "quay.io/keycloak/keycloak:${var.keycloak_tag}"
+        args         = ["start-dev", "--hostname", "http://${NOMAD_IP_http}:${NOMAD_PORT_http}"]
+        ports        = ["http"]
+        network_mode = "host"
+        # note: keycloak config will be lost unless you use persistent storage.
+        #volumes = [
+        #  # /opt/keycloak-data on the host machine needs to be owned by user 1000
+        #  "/opt/keycloak-data:/opt/keycloak/data",
+        #]
+      }
+      env {
+        KC_BOOTSTRAP_ADMIN_USERNAME = "admin"
+        KC_BOOTSTRAP_ADMIN_PASSWORD = "admin"
+        PROXY_ADDRESS_FORWARDING    = true
+        KC_PROXY_HEADERS            = "xforwarded"
+      }
+      resources {
+        memory = 800
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+</Tab>
+
+</Tabs>
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run keycloak.nomad.hcl
+```
+
+## Log in to Keycloak
+
+Retrieve the Keycloak web address and open it in your web browser. In the following example, the address is `192.168.1.201:8080`.
+
+```shell-session
+$ nomad service info keycloak
+Job ID    Address             Tags  Node ID   Alloc ID
+keycloak  192.168.1.201:8080  []    1885c25d  c7f18cc3
+```
+
+At the Keycloak sign in page, enter the username `admin` and the password `admin`, and then click **Sign In**. Keycloak loads the landing page for the **master realm** with the **Welcome to Keycloak** message.
+
+## Configure Keycloak
+
+You will now make the necessary configurations through the Keycloak web UI.
+
+### Create a realm
+
+In Keycloak, a _realm_ manages a set of users, credentials, roles, and groups. It is equivalent to a tenant.
+
+1. At the top left, click the dropdown list that displays **Keycloak** and **master** below it.
+1. Click **Create realm**.
+1. In **Realm name**, enter `Nomad`.
+1. Click **Create**.
+
+Keycloak creates a new realm, redirects you to the landing page for the Nomad realm, and displays the **Welcome to Nomad** message.
+
+### Create a group
+
+A group in Keycloak is a set of attributes and role mappings that you can apply to a user. Users in this group will be given permissions in Nomad.
+
+1. In the left navigation, click **Groups**.
+1. Click **Create group**.
+1. In **Name**, enter `engineering`.
+1. Click **Create**.
+
+### Create a user
+
+1. In the left navigation, click **Users**.
+1. Click **Create new user**.
+1. Enter the following values for each labelled field:
+
+    |Field name|Value|
+    |--|--|
+    |Username|`testuser`|
+    |Email|`testuser@example.com`|
+    |First Name|`Test`|
+    |Last Name|`User`|
+
+1. Click **Join Groups**.
+1. Select the check box for the `engineering` group.
+1. Click **Join**.
+1. Click **Create** to complete the process.
+
+Next, create a password for the new user.
+
+1. From the **User details** page, at the top, click **Credentials**.
+1. Click **Set password**.
+1. Enter `password` in the **Password** and **Password confirmation** fields.
+1. Turn off **Temporary**.
+1. Click **Save**.
+1. In the prompt that appears, click **Save password**.
+
+### Create a client scope
+
+Nomad checks the ID token response from Keycloak for a group. Keycloak adds this group to the response with a client scope.
+
+1. In the left navigation, click **Client scopes**.
+1. Near the top of the page, click **Create client scope**.
+1. For **Name** enter `scope-for-nomad`.
+1. Next to **Type**, click the dropdown and then select **Default**.
+1. Click **Save**.
+
+Keycloak redirects you to the **Client scope details** page.
+
+1. In the top navigation, click **Mappers**.
+1. Click **Configure a new mapper**.
+1. In the **Name** column, click **Group Membership**.
+1. In the **Add mapper** form, for the **Name**, enter `nomad-mapper`.
+1. For **Token Claim Name**, enter `kc-groups`.
+1. Click **Save**.
+
+### Create the client
+
+A client in Keycloak is an application or service that can request authentication of a user. Nomad is a client in Keycloak.
+
+1. In the left navigation, click **Clients**.
+1. Near the top of the page, click **Create client**.
+1. For **Client ID**, enter `nomad-oidc`.
+1. Click **Next** to continue.
+1. Turn on **Client authentication**.
+1. Click **Next** to continue.
+1. For **Valid redirect URIs**, enter `http://localhost:4649/oidc/callback`. Note that the port for this URI is `4649`. This URI is for login attempts with the Nomad CLI.
+1. Click **Add valid redirect URIs** to add another URI.
+1. Enter `https://localhost:4646/ui/settings/tokens`. Note that the port for this URI is `4646`. This URI is for login attempts with the Nomad web UI.
+
+   There are now two URI values in **Valid redirect URIs**. These
+   values are the location that Keycloak redirects users to after they log in.
+
+1. Click **Save**.
+
+### Verify scope for client
+
+1. From the **Clients** page, in the top navigation, click **Client scopes**.
+1. In the **Search by name** search field, enter `scope-for-nomad`.
+1. Click the button with the arrow to search. Note that the **Assigned type** for the `scope-for-nomad` client scope is set to **Default**.
+
+### View credentials
+
+Nomad requires a secret to verify that it has authorization to use this client in Keycloak.
+
+1. In the left navigation, click **Clients**.
+1. In the **Client ID** column, click **nomad-oidc** .
+1. At the top, click **Credentials**. The dropdown under **Client Authenticator** shows that Keycloak uses client ID and secret by default.
+1. Reveal the **Client Secret**.
+1. Copy this value and save it. You will use it in the next section.
+
+## Configure Nomad
+
+Nomad requires the following configuration to complete the set up with Keycloak:
+
+- An [auth method](/nomad/commands/acl/auth-method/create) using the Keycloak details
+- A policy and role to specify user permissions in Nomad
+- A binding rule to associate the Keycloak group to the Nomad role
+
+### Create an auth method
+
+Copy the following example configuration to a file and then replace these placeholder values:
+
+- `_KEYCLOAK_ADDRESS`: the address of the Keycloak service in Nomad, from the [Log in to Keycloak section of this tutorial](#log-in-to-keycloak).
+- `_KEYCLOAK_CLIENT_SECRET`: The client secret value from the [View credentials section of this tutorial](#view-credentials).
+
+Save the file as `auth-method-keycloak.json`.
+
+Note that the `ListClaimMappings` value maps the group `kc-groups` in Keycloak to a value that you will define in the Nomad binding rule named `keycloak_groups`.
+
+<CodeBlockConfig filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Ensure that the `NOMAD_TOKEN` environment variable is set to your Nomad management token, as only management tokens can create auth methods.
+
+<CodeBlockConfig>
+
+```shell-session
+$ nomad acl token self | grep Type
+Type         = management
+```
+
+</CodeBlockConfig>
+
+Create the auth method.
+
+```shell-session
+$ nomad acl auth-method create \
+  -type=OIDC \
+  -name=keycloak \
+  -default=true \
+  -max-token-ttl=5m \
+  -token-locality=global \
+  -config=@auth-method-keycloak.json
+```
+
+The command prints information about the auth method similar to the following example output.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Name              = keycloak
+Type              = OIDC
+Locality          = global
+Max Token TTL     = 5m0s
+Token Name Format = ${auth_method_type}-${auth_method_name}
+Default           = true
+Create Index      = 382
+Modify Index      = 382
+
+Auth Method Config
+
+JWT Validation Public Keys = <none>
+JWKS URL                   = <none>
+OIDC Discovery URL         = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID             = nomad-oidc
+OIDC Client Secret         = redacted
+OIDC Enable PKCE           = false
+OIDC Disable UserInfo      = false
+OIDC Scopes                = openid,scope-for-nomad
+Bound audiences            = nomad-oidc
+Bound issuer               = <none>
+Allowed redirects URIs     = http://localhost:4649/oidc/callback,https://localhost:4646/ui/settings/tokens
+Discovery CA pem           = <none>
+JWKS CA cert               = <none>
+Signing algorithms         = <none>
+Expiration Leeway          = 0s
+NotBefore Leeway           = 0s
+ClockSkew Leeway           = 0s
+Claim mappings             = <none>
+List claim mappings        = {kc-groups: keycloak_groups}
+```
+
+</CodeBlockConfig>
+
+### Create policy and role
+
+Create an ACL policy that grants access to the `default` namespace and Nomad nodes.
+
+First, create the policy file. Copy the following example policy to a file and save it as `engineering-policy.hcl`.
+
+```hcl
+namespace "default" {
+  capabilities = ["list-jobs"]
+}
+```
+
+Create the policy.
+
+```shell-session
+$ nomad acl policy apply engineering-policy engineering-policy.hcl
+Successfully wrote "engineering-policy" ACL policy!
+```
+
+Create a role and associate it to the policy.
+
+```shell-session
+$ nomad acl role create -name=engineering-role -policy=engineering-policy
+ID           = 6987c982-082d-35ac-aff3-57f24e5829a0
+Name         = engineering-role
+Description  = <none>
+Policies     = engineering-policy
+Create Index = 448
+Modify Index = 448
+```
+
+### Create binding rule
+
+Grant users in the `/engineering` Keycloak group the Nomad ACL role named `engineering-role`. Note the single quotes around the whole `selector` value and the backticks around the `/engineering` segment. These are important, as you must include `/` in the selector expression.
+
+```shell-session
+$ nomad acl binding-rule create \
+  -auth-method=keycloak \
+  -bind-type=role \
+  -bind-name=engineering-role \
+  -selector='`/engineering` in list.keycloak_groups'
+```
+
+The command prints information about the binding-rule similar to the following example output.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+ID           = b5d6bc45-0667-868e-7054-a75b45b6676f
+Description  = <none>
+Auth Method  = keycloak
+Selector     = "`/engineering` in list.keycloak_groups"
+Bind Type    = role
+Bind Name    = engineering-role
+Create Time  = 2025-03-25 20:39:25.923021 +0000 UTC
+Modify Time  = 2025-03-25 20:39:25.923021 +0000 UTC
+Create Index = 451
+Modify Index = 451
+```
+
+</CodeBlockConfig>
+
+## Log in to Nomad
+
+In your terminal session, log in to Nomad. You do not need additional arguments since the auth method included the `-default=true` flag. This command opens a web browser window to Keycloak and prompts you to sign in.
+
+```shell-session
+$ nomad login
+```
+
+Enter `testuser` in the **Username or email** field and `password` in the **Password** field.
+
+After a successful login, Keycloak redirects you to a page at `localhost:4649/oidc/callback` that contains text with the message `Signed in via your OIDC provider`.
+
+Open your terminal and note the output from the login command. You are now signed into Nomad via authentication with Keycloak.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+Accessor ID  = 3b45aa90-eeb7-7b55-11d6-fe5d597b1753
+Secret ID    = 83e70c65-54b4-e2a3-3158-6ab59b9bb989
+Name         = OIDC-keycloak
+Type         = client
+Global       = true
+Create Time  = 2025-03-26 14:02:27.365842 +0000 UTC
+Expiry Time  = 2025-03-26 14:07:27.365842 +0000 UTC
+Create Index = 39
+Modify Index = 39
+Policies     = []
+
+Roles
+ID                                    Name
+4d60501e-57c6-07ba-d06d-72f76ab1f650  engineering-role
+```
+
+</CodeBlockConfig>
+
+Refer to the [OIDC auth method page](/nomad/docs/secure/authentication/oidc#oidc-configuration-troubleshooting) for information about OIDC configuration and troubleshooting.
+
+### Test the token
+
+Copy the Secret ID from the output and use it to query Nomad for jobs status. In this example, the Secret ID is `83e70c65-54b4-e2a3-3158-6ab59b9bb989`.
+
+```shell-session
+$ NOMAD_TOKEN=83e70c65-54b4-e2a3-3158-6ab59b9bb989 nomad job status
+ID        Type     Priority  Status   Submit Date
+keycloak  service  50        running  2025-03-26T09:51:59-04:00
+```
+
+Copy the secret ID again and use it to query the status of the `keycloak` job. This command will fail because the OIDC token does not have the required permissions.
+
+```shell-session
+$ NOMAD_TOKEN=83e70c65-54b4-e2a3-3158-6ab59b9bb989 nomad job status keycloak
+Error querying job: Unexpected response code: 403 (Permission denied)
+```
+
+The `-max-token-ttl=5m` flag of the `nomad acl auth-method create` command sets the token validity to expire after five minutes. After the TTL expires, you must run `nomad login` again to get another valid token.
+
+## Enable PKCE
+
+PKCE is an extension to the [Authorization Code flow](https://oauth.net/2/grant-types/authorization-code/) to prevent CSRF and authorization code injection attacks. Beginning with Nomad v1.10.0, Nomad supports PKCE.
+
+To take advantage of the additional security of PKCE, you must enable it in Keycloak.
+
+1. Open the Keycloak web UI. To fetch the address, run `nomad service info keycloak`.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Advanced**.
+1. Scroll to **Advanced settings**.
+1. Find **Proof Key for Code Exchange Code Challenge Method**.
+1. Click the dropdown and then select **S256**.
+1. Scroll to the bottom of the page and then click **Save**.
+
+Keycloak now ensures that any authentication attempt uses PKCE. A login attempt with `nomad login` now returns an error.
+
+```plaintext
+Error performing login: Unexpected response code: 400
+  (invalid OIDC complete-auth request: 1 error occurred:
+        * missing code)
+```
+
+### Configure Nomad to enable PKCE
+
+Update the auth method configuration file to enable PKCE in Nomad. Add the highlighted section for `OIDCEnablePKCE` to the file and then save it.
+
+<CodeBlockConfig highlight="4" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method. Note that the output shows that PKCE is enabled.
+
+<CodeBlockConfig highlight="10">
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = redacted
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+</CodeBlockConfig>
+
+Log in with Nomad to confirm that the functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+## Enable client assertions
+
+A client assertion is a token provided by a client application to confirm the proof of the client's identity.
+
+Keycloak refers to client assertions as *signed JWT* or *signed JWT with client secret*. Nomad supports both methods. Client assertions provide additional security and function as an alternative to using client secrets.
+
+Nomad builds a JWT and signs it with a private key that the OIDC provider can verify with Nomad's accompanying public key. Nomad asserts that it is a valid OIDC client without sending any secret information over the network.
+
+1. Navigate to the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown.
+
+Take note of the available options: **Signed Jwt**, **Client Id and Secret**, **X509 Certificate**, and **Signed Jwt with Client Secret**.
+
+You have set up the **Client Id and Secret** authenticator. In the next section, you can choose how you want to set up a client assertion:
+- Signed JWT with the client secret
+- Signed JWT with Nomad's _built-in_ private key pair
+- Signed JWT with a _new_ private key pair
+
+<Tabs>
+
+<Tab heading="Client secret" group="client_secret">
+
+### Signed JWT with the client secret
+
+This authenticator method uses the client secret as a Hash-Based Message Authentication Code (HMAC) key to sign the client assertion JWT. Nomad sends the signed JWT to Keycloak instead of sending the secret itself over the network.
+
+Keycloak has the same client secret, which it uses to verify the JWT signature. Keycloak knows that Nomad must have the client secret, otherwise it would not have been able to use it to sign the JWT.
+
+To enable the **Signed Jwt with Client Secret** authenticator, complete the following steps:
+
+1. Open the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown  and then select **Signed Jwt with Client Secret**.
+1. Next to **Signature algorithm**, click the dropdown and then select **HS256**.
+1. Click **Save**. In the dialog that appears, click **Yes** to confirm the change.
+
+Attempting to log in with `nomad login` will cause an error as the request from Nomad is missing the `client_assertion_type`.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Error performing login: Unexpected response code: 500
+  (failed to exchange token with provider: Provider.Exchange:
+  unable to exchange auth code with provider: oauth2:
+  "invalid_client" "Parameter client_assertion_type is missing")
+```
+
+</CodeBlockConfig>
+
+Update the auth method configuration file to enable the client assertion in Nomad. Add the highlighted section for `OIDCClientAssertion` to the file and then save it.
+
+The `"KeySource" = "client_secret"` instructs Nomad to use the `OIDCClientSecret` as a client assertion HMAC instead of a normal client secret.
+
+<CodeBlockConfig highlight="4-7" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCClientAssertion": {
+    "KeySource": "client_secret",
+    "Algorithm": "HS256"
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method. Note that the output now includes the client assertion attributes.
+
+<CodeBlockConfig highlight="12-15">
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = <none>
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = redacted
+OIDC Client Assertion KeySource = client_secret
+OIDC Client Assertion Algorithm = HS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+</CodeBlockConfig>
+
+Log in with Nomad to confirm that the functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+Accessor ID  = 001b3ac1-f238-3003-fc94-539fa824b9a9
+Secret ID    = redacted
+Name         = OIDC-keycloak
+Type         = client
+
+# ...
+
+Roles
+ID                                    Name
+19c19cbf-dd6a-6084-bca4-5505cb9028b8  engineering-role
+```
+
+</Tab>
+
+<Tab heading="Built-in key pair" group="builtin_keypair">
+
+### Signed JWT with the built-in key pair
+
+This authenticator method uses a private and public key to sign and verify the JWT. Nomad uses its private key to sign the JWT, and Keycloak uses Nomad's public key to verify the JWT.
+
+Keycloak sends a request to Nomad's JWKS URL to retrieve the public key so that it can verify that the JWT signature is from Nomad. Keycloak requires access to the JWKS URL either directly or through a proxy.
+
+#### Deploy the Nomad API proxy
+
+In this section, you will deploy an API proxy that uses [Nomad's task API](/nomad/api-docs/task-api) to serve the JWKS URL. The task API is convenient as an example, but be aware that it does not work on Windows. This tutorial uses HTTP as for demonstration purposes, but we recommend having a valid TLS certificate and using HTTPS for production implementations.
+
+Copy the following contents to a file and save the file as `jwks-proxy.nomad.hcl`.
+
+<CodeBlockConfig filename="jwks-proxy.nomad.hcl">
+
+```hcl
+variable "caddy_tag" {
+  # https://hub.docker.com/_/caddy
+  default = "2.9.1-alpine"
+}
+
+job "jwks-proxy" {
+  group "proxy" {
+    network {
+      mode = "host"
+      port "http" {
+        static = 4444
+      }
+    }
+    service {
+      name     = "jwks-proxy"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "caddy" {
+      driver = "docker"
+      config {
+        image   = "caddy:${var.caddy_tag}"
+        command = "caddy"
+        args    = ["run", "--config", "${NOMAD_TASK_DIR}/Caddyfile"]
+        ports   = ["http"]
+      }
+      identity {
+        env = true # makes the api.sock unix socket and Nomad token
+      }
+      template {
+        # https://caddyserver.com/docs/caddyfile
+        destination     = "${NOMAD_TASK_DIR}/Caddyfile"
+        left_delimiter  = "[[" # for clarity
+        right_delimiter = "]]"
+        data = <<EOF
+:[[ env `NOMAD_PORT_http` ]] {
+	log {
+		output stdout
+	}
+	# only serve the jwks endpoint
+	reverse_proxy /.well-known/jwks.json {
+		to unix/[[ env `NOMAD_SECRETS_DIR` ]]/api.sock
+		# task api always requires a token, even though
+		# the jwks endpoint is unauthenticated.
+		header_up X-Nomad-Token "[[ env `NOMAD_TOKEN` ]]"
+	}
+}
+EOF
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Submit the proxy job to Nomad.
+
+```shell-session
+$ nomad job run jwks-proxy.nomad.hcl
+```
+
+Get the service address of the proxy.
+
+```shell-session
+$ nomad service info jwks-proxy
+Job ID      Address             Tags  Node ID   Alloc ID
+jwks-proxy  192.168.1.201:4444  []    1885c25d  668f188c
+```
+
+The JWKS URL consists of the the service address of the proxy and the path to the `jwks.json` file. In this example, the JWKS URL is `http://192.168.1.201:4444/.well-known/jwks.json`.
+
+Test connectivity to the JWKS URL.
+
+```shell-session
+$ curl http://192.168.1.201:4444/.well-known/jwks.json
+{"keys":[{"use":"sig","kty":"RSA","kid":"a33560ad-0321-8006-228d-cc759335609b","alg":"RS256","n":"this-is-the-public-key","e":"AQAB"}]}
+```
+
+#### Configure Keycloak with Nomad JWKS
+
+Perform these steps to configure Keycloak:
+
+1. Navigate to the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown and then select **Signed Jwt**.
+1. Next to **Signature algorithm**, click the dropdown and then select **Any algorithm**.
+1. Click **Save**. Then click **Yes** in the dialog that appears.
+1. At the top, click **Keys**.
+1. Turn on **Use JWKS URL**.
+1. For **JWKS URL**, enter the JWKS URL. In this tutorial, the JWKS URL is `http://192.168.1.201:4444/.well-known/jwks.json`.
+1. Click **Save**.
+
+#### Update the Nomad auth method configuration
+
+Update the auth method configuration file to enable the feature in Nomad. Add the highlighted section for `OIDCClientAssertion` to the file and then save it.
+
+Note that the configuration no longer contains any secret value. Nomad has the private key and Keycloak retrieves the public key at the JWKS URL.
+
+<CodeBlockConfig highlight="3-5" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientAssertion": {
+    "KeySource": "nomad"
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method.
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = http://192.168.1.201:4444/.well-known/jwks.json
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = <none>
+OIDC Client Assertion KeySource = nomad
+OIDC Client Assertion Algorithm = RS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+Log in with Nomad to confirm that functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+</Tab>
+
+<Tab heading="New key pair" group="new_keypair">
+
+### Signed JWT with a new key pair
+
+This authenticator method uses a new private and public keypair set to sign the JWT instead of Nomad's built-in one.
+
+You can use this method to manage the keys yourself, but it requires updating the keys manually in both Nomad and the OIDC provider.
+
+#### Generate a key and certificate
+
+Open your terminal and use `openssl` to generate a new private key.
+
+```shell-session
+$ openssl genrsa -out private.pem
+```
+
+Generate a certificate with the private key. Be sure to update the subject values in the `-subj` flag for your environment.
+
+```shell-session
+$ openssl req -new -x509 -key private.pem -days 365 \
+  -subj '/C=US/ST=CA/L=Example/O=ExampleOrg/OU=OrgUnit/CN=example.com' \
+  -out certificate.pem
+```
+
+#### Upload the certificate to Keycloak
+
+1. Open the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Keys**.
+1. Turn off **Use JWKS URL**.
+1. Click **Import**.
+1. Under **Archive format**, click the dropdown and then select **Certificate PEM**.
+1. Under **Import file**, click **Browse**. Navigate to the directory that contains the certificate file and then select it.
+1. Click **Import**. Keycloak automatically fills in the form field with the contents of the certificate.
+1. Click **Save**.
+
+#### Update Nomad with the key and certificate
+
+Open `auth-method-keycloak.json` in your text editor and add the `OIDCClientAssertion` block highlighted below to it. Copy the contents of the private key file and paste them into the value for the `PemKey` attribute. Copy the contents of the certificate key file and paste them into the value for `PemCert`.
+
+<CodeBlockConfig highlight="3-9" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientAssertion": {
+    "KeySource": "private_key",
+    "PrivateKey": {
+      "PemKey": "-----BEGIN PRIVATE KEY-----[EXAMPLE_KEY_CONTENTS]-----END PRIVATE KEY-----",
+      "PemCert": "-----BEGIN CERTIFICATE-----[EXAMPLE_CERTIFICATE_CONTENTS]-----END CERTIFICATE-----"
+    }
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+The contents must be on one line and cannot contain newline characters. You can use the `tr` command to remove newline characters if you are editing the files in your terminal.
+
+```shell-session
+$ tr -d '\n' < _KEY_OR_CERT_FILENAME
+```
+
+Save the file after you update both values.
+
+Update the auth method config to enable the feature in Nomad. Nomad uses the certificate to derive a special JWT header called [x5t#S256](https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8), which Keycloak uses to look up the public key it has saved.
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = http://192.168.1.201:4444/.well-known/jwks.json
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = <none>
+OIDC Client Assertion KeySource = private_key
+OIDC Client Assertion Algorithm = RS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+Log in with Nomad to confirm that functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+</Tab>
+
+</Tabs>
+
+Navigate back to the [Configure Keycloak for client assertions](#enable-client-assertions) section if you want to try out the other client assertion options.
+
+## Next Steps
+
+In this tutorial you learned how to configure Nomad and Keycloak to automatically grant permissions with Nomad's ACL system. Then you enabled the Keycloak provider to require PKCE and reconfigured Keycloak to use client assertions.
+
+To continue your learning, check out these resources:
+- Learn more about the [JWT Auth Method](/nomad/docs/secure/authentication/jwt) in Nomad.
+- Learn more about the [OIDC Auth method](/nomad/docs/secure/authentication/oidc) in Nomad.
+- Learn how to [use Vault as an OIDC
+  provider](/nomad/docs/secure/authentication/sso-vault) with Nomad.
diff --git a/content/nomad/v1.10.x/content/docs/secure/authentication/sso-vault.mdx b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-vault.mdx
new file mode 100644
index 0000000000..4c396af84a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/authentication/sso-vault.mdx
@@ -0,0 +1,584 @@
+---
+layout: docs
+page_title: Configure SSO with Vault
+description: |-
+  Configure Vault as an OIDC provider with authorization code flow and
+  configure Nomad as an OIDC client.
+---
+
+# Configure SSO with Vault
+
+Implementing zero-trust architecture requires providing identity-based access to
+services within an organization. OpenID Connect (OIDC) allows clients to confirm
+their identity through an identity provider. **Vault 1.9.0** introduced the
+ability to configure Vault as an OIDC identity provider with authorization code
+flow, and **Nomad 1.5.0** introduced support for OIDC as a single sign-on
+method. With Nomad 1.5.0, you can use OIDC to authenticate users and map their
+permissions to Nomad ACL roles and policies.
+
+In this guide, you will setup Vault as an OIDC provider and Nomad as its
+client.
+
+-> **Note:** Nomad operates as a confidential OIDC client in this guide. To
+   configure a public OIDC client, refer to the [OIDC
+   Provider](/vault/docs/concepts/oidc-provider#public) documentation.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have:
+
+- A Nomad environment. Refer to the [get started](/nomad/tutorials/get-started) tutorials to install Nomad and create a cluster.
+
+- A Vault environment of **version 1.10** or later. Refer to the [Vault install guide](/vault/install) to install Vault locally
+  or [create a Vault cluster on HCP](/vault/tutorials/cloud/get-started-vault).
+
+  -> **NOTE:** This feature was first introduced in Vault 1.9 as a Technical
+  Preview feature. As of Vault 1.10, it is generally available.
+
+### Policy requirements
+
+For the purpose of this guide, you will use the `root` token to work with Vault
+running in development mode.
+
+When you are working with a non-development Vault environment, your token policy
+must include the following permissions:
+
+```hcl
+# To create an entity and entity alias. Enable and configure Vault as an OIDC provider
+path "identity/*" {
+  capabilities = [ "create", "read", "update", "delete", "list" ]
+}
+
+# To enable userpass auth method
+path "sys/auth/userpass" {
+  capabilities = [ "create", "read", "update", "delete" ]
+}
+
+# To create a new user, "end-user" for userpass
+path "auth/userpass/users/*" {
+   capabilities = [ "create", "read", "update", "delete", "list" ]
+}
+```
+
+Refer to the [Vault policies tutorial](/vault/tutorials/policies/policies) for more information.
+
+## Start Vault
+
+<Tabs>
+<Tab heading="Vault" group="oss">
+
+In your terminal, start a Vault development server with `root` as the root token.
+
+```shell-session
+$ vault server -dev -dev-root-token-id root
+```
+
+The Vault development server defaults to running at `127.0.0.1:8200`. The server is now
+initialized and unsealed.
+
+<Warning>
+
+ Do not run a Vault development server in production. This
+approach starts a Vault server with an in-memory database and is only for testing purposes.
+
+</Warning>
+
+Open another terminal session, and export an environment variable for the address to the Vault server.
+
+```shell-session
+$ export VAULT_ADDR=http://127.0.0.1:8200
+```
+
+Export an environment variable for the Vault token.
+
+```shell-session
+$ export VAULT_TOKEN=root
+```
+
+-> **Note:** For these tasks, you can use Vault's _root_ token. However, we
+recommend that you use root tokens only for the initial setup or in
+emergencies. As a best practice, use an authentication method or token that
+meets the [policy requirements](#policy-requirements).
+
+The Vault server is ready.
+
+</Tab>
+<Tab heading="HCP Vault Dedicated" group="hcp">
+
+
+1. Launch the [HCP Portal](https://portal.cloud.hashicorp.com/) and log in.
+1. Click **Vault** in the left navigation pane.
+1. In the **Vault clusters** pane, click **vault-cluster**.
+1. Under **Cluster URLs**, click **Public** Cluster URL. This copies the URL to your clipboard.
+1. In your terminal, set the `VAULT_ADDR` environment variable to the public cluster URL copied from HCP.
+
+   ```shell-session
+   $ export VAULT_ADDR=<Public_Cluster_URL>
+   ```
+
+1. Return to the **Overview** page and click **Generate token**. It will take a few moments to generate the token.
+1. Copy the **Admin Token** by clicking on **Copy**.
+1. Return to your terminal and set the `VAULT_TOKEN` environment variable to the token copied from HCP.
+
+   ```shell-session
+   $ export VAULT_TOKEN=<token>
+   ```
+
+1. Set the `VAULT_NAMESPACE` environment variable to `admin`.
+
+   ```shell-session
+   $ export VAULT_NAMESPACE=admin
+   ```
+
+   The `admin` namespace is the top-level namespace automatically created by HCP
+   Vault. By default, all CLI operations use the namespace defined in this
+   environment variable.
+
+1. Verify connectivity to the Vault cluster.
+
+   ```shell-session
+   $ vault status
+
+   Key                      Value
+   ---                      -----
+   Recovery Seal Type       shamir
+   Initialized              true
+   Sealed                   false
+   Total Recovery Shares    1
+   Threshold                1
+   Version                  1.9.2+ent
+   Storage Type             raft
+   ...snipped...
+   ```
+
+The Vault Dedicated server is ready.
+
+</Tab>
+</Tabs>
+
+## Configure Vault authentication
+
+Vault [auth methods](/vault/docs/auth) authenticate and assign
+identity and policies to a client. When Vault acts as an OIDC provider, it is
+the source of identity and these auth methods verify that identity.
+
+1. Enable the userpass auth method at the default path.
+
+   ```shell-session
+   $ vault auth enable userpass
+   ```
+
+1. Create a user named `end-user` with the password `password`.
+
+   ```shell-session
+   $ vault write auth/userpass/users/end-user \
+       password="password" \
+       token_ttl="1h"
+   ```
+
+   This user authenticates with Vault and is assigned the default access policy.
+
+   ~> **Learn More:** For more information refer to the [Userpass Auth
+   Method](/vault/docs/auth/userpass) documentation.
+
+## Create Vault identity entity and group
+
+A client may have multiple accounts with various identity providers that are
+enabled on the Vault server. Vault clients can be mapped as entities and their
+corresponding accounts with authentication providers can be mapped as aliases.
+
+1. Create an identity entity with details about the `end-user`.
+
+   ```shell-session
+   $ vault write identity/entity \
+       name="end-user" \
+       disabled=false
+   ```
+
+1. Create an environment variable named `ENTITY_ID` that stores the ID assigned to the entity.
+
+   ```shell-session
+   $ ENTITY_ID=$(vault read -field=id identity/entity/name/end-user)
+   ```
+
+1. Create an identity group with the name `engineering` and add `end-user` as a member.
+
+   ```shell-session
+   $ vault write identity/group \
+       name="engineering" \
+       member_entity_ids="$ENTITY_ID"
+   ```
+
+1. Create an environment variable named `GROUP_ID` that stores the ID assigned to the group.
+
+   ```shell-session
+   $ GROUP_ID=$(vault read -field=id identity/group/name/engineering)
+   ```
+
+   The `end-user` entity is a member of the `engineering` group. An entity alias
+   maps an entity to client of an authentication method. This mapping requires
+   the entity ID and the authentication accessor ID.
+
+1. Create a variable named `USERPASS_ACCESSOR` that stores the accessor value of
+   the userpass authentication method.
+
+   ```shell-session
+   $ USERPASS_ACCESSOR=$(vault auth list -detailed -format json | jq -r '.["userpass/"].accessor')
+   ```
+
+1. Create an entity alias that maps the `end-user` entity with the `end-user` user.
+
+   ```shell-session
+   $ vault write identity/entity-alias \
+       name="end-user" \
+       canonical_id="$ENTITY_ID" \
+       mount_accessor="$USERPASS_ACCESSOR"
+   ```
+
+   The entity and the user are aliases of one another.
+
+~> **Learn More:** Learn more about identity in the [entities and groups tutorial](/vault/tutorials/auth-methods/identity).
+
+## Create a Vault OIDC client
+
+A Vault OIDC client connects a resource called an OIDC assignment, an
+encryption key, a client callback URL and a time-to-live on verification
+together.
+
+An OIDC assignment describes the list of the Vault entities and groups allowed
+to authenticate with this client.
+
+1. Create an assignment named `my-assignment` that authorizes the `end-user` entity
+   and `engineering` group.
+
+   ```shell-session
+   $ vault write identity/oidc/assignment/my-assignment \
+       entity_ids="${ENTITY_ID}" \
+       group_ids="${GROUP_ID}"
+   ```
+
+   The Vault OIDC authentication process requires an encryption key to sign and
+   verify the JSON web tokens (JWT) that are produced by the authentication flow.
+
+1. Create a key named `my-key`.
+
+   ```shell-session
+   $ vault write identity/oidc/key/my-key \
+       allowed_client_ids="*" \
+       verification_ttl="2h" \
+       rotation_period="1h" \
+       algorithm="RS256"
+   ```
+
+   The key is usable by all Vault OIDC clients as `allowed_client_ids` is set to
+   `*`.
+
+1. Create an OIDC client named `nomad`.
+
+   ```shell-session
+   $ vault write identity/oidc/client/nomad \
+       redirect_uris="http://localhost:4649/oidc/callback,http://localhost:4200/ui/settings/tokens" \
+       assignments="my-assignment" \
+       key="my-key" \
+       id_token_ttl="30m" \
+       access_token_ttl="1h"
+   ```
+
+   The `redirect_uris` flag describes the callback URL for the client, the value
+   is the address of a Nomad service running on its default port.
+   The `assignments` flag limits access to only the entities and groups defined in
+   `my-assignment`.
+   The `id_token_ttl` flag sets the expiration on the ID token to 30 minutes.
+   The `access_token_ttl` flag  sets the expiration of the access token to 1 hour.
+
+1. Create an environment variable named CLIENT_ID to store the `client_id` field of the
+  `nomad` client.
+
+   ```shell-session
+   $ CLIENT_ID=$(vault read -field=client_id identity/oidc/client/nomad)
+   ```
+
+## Create a Vault OIDC provider
+
+A Vault OIDC provider supports one or more clients and Vault OIDC scopes. These
+scopes define metadata claims expressed in a template. Claims are key-value
+pairs that contain information about a user and the OIDC service.
+
+1. Create an environment variable named `USER_SCOPE_TEMPLATE` that stores the user scope template.
+
+  ```shell-session
+  $ USER_SCOPE_TEMPLATE='{"username": {{identity.entity.name}}}'
+  ```
+
+1. Define a Vault OIDC scope named `user` with the user scope template.
+
+   ```shell-session
+   $ vault write identity/oidc/scope/user \
+       description="The user scope provides claims using Vault identity entity metadata" \
+       template="$(echo ${USER_SCOPE_TEMPLATE} | base64)"
+   ```
+
+1. Create an environment variable named `GROUPS_SCOPE_TEMPLATE` that stores the group scope.
+   template.
+
+   ```shell-session
+   $ GROUPS_SCOPE_TEMPLATE='{"groups": {{identity.entity.groups.names}}}'
+   ```
+
+   This template retrieves the names of all the groups defined.
+
+1. Define a Vault OIDC scope named `groups` with the groups scope template.
+
+   ```shell-session
+   $ vault write identity/oidc/scope/groups \
+       description="The groups scope provides the groups claim using Vault group membership" \
+       template="$(echo ${GROUPS_SCOPE_TEMPLATE} | base64)"
+   ```
+
+1. Create a Vault OIDC provider named `my-provider` and provide it a list of client IDs and scopes. The provider grants access to the `nomad` client.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ vault write identity/oidc/provider/my-provider \
+       allowed_client_ids="${CLIENT_ID}" \
+       scopes_supported="groups"
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+      Vault Dedicated uses the private address for the `issuer` URL. For this guide, you will override the `issuer` value to match the public URL.
+
+   ```shell-session
+   $ vault write identity/oidc/provider/my-provider \
+       issuer="$(echo $VAULT_ADDR)" \
+       allowed_client_ids="${CLIENT_ID}" \
+       scopes_supported="groups"
+   ```
+
+   </Tab>
+   </Tabs>
+
+
+1. Display the Vault OIDC configuration endpoint.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq
+   ```
+
+   </Tab>
+   </Tabs>
+
+1. Show Vault OIDC public keys.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/keys | jq
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/keys | jq
+   ```
+
+   </Tab>
+   </Tabs>
+
+## Start Nomad
+
+The [Nomad development agent](/nomad/commands/agent#dev) brings up an instance of Nomad with a server and client. Refer to the [start a cluster tutorial](/nomad/tutorials/get-started/gs-start-a-cluster#create-the-cluster) for more information.
+
+In another terminal, start a Nomad agent in development mode with ACL enabled.
+
+```shell-session
+$ sudo nomad agent -dev -acl-enabled
+
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.5.0
+
+...snip...
+```
+
+The Nomad server is ready.
+
+## Configure Nomad OIDC auth
+
+1. Create an environment variable named `ISSUER` that stores the `issuer` field of the Vault OIDC provider named `my-provider`.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ ISSUER=$(curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq -r .issuer)
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ ISSUER=$(curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq -r .issuer)
+   ```
+
+   </Tab>
+   </Tabs>
+
+1. Create an environment variable named `CLIENT_SECRET` that stores the `client_secret` field of the Vault OIDC client named `nomad`.
+
+   ```shell-session
+   $ CLIENT_SECRET=$(vault read -field=client_secret identity/oidc/client/nomad)
+   ```
+
+1. Run the bootstrap process, store the value of the management token, and export it as the `NOMAD_TOKEN` environment variable.
+
+   ```shell-session
+   $ NOMAD_TOKEN=$(nomad acl bootstrap -json | jq -r .SecretID)
+   $ export NOMAD_TOKEN
+   ```
+
+1. Create a Nomad policy that allows read access to the "default" namespace.
+
+   Create a file named `acl_policy_engineering_read.hcl`, add the following contents, and save the file.
+
+   ```hcl
+   namespace "default" {
+     policy = "read"
+   }
+
+   node {
+     policy = "read"
+   }
+   ```
+
+  Apply the policy.
+
+   ```shell-session
+   $ nomad acl policy apply engineering-read acl_policy_engineering_read.hcl
+   ```
+
+1. Create a corresponding role that contains the policies to assign to engineers.
+
+   ```shell-session
+   $ nomad acl role create \
+       -name=engineering-read \
+       -policy=engineering-read
+   ```
+
+1. Create a configuration for the OIDC auth method.
+
+   Create a file named `acl_auth_method.json`, add the following contents, replace `$ISSUER`, `$CLIENT_ID` and `$CLIENT_SECRET` with the values stored in their respective environment variables, and save the file.
+
+   ```json
+   {
+     "OIDCDiscoveryURL": $ISSUER,
+     "OIDCClientID": $CLIENT_ID,
+     "OIDCClientSecret": $CLIENT_SECRET,
+     "BoundAudiences": [$CLIENT_ID],
+     "OIDCScopes": ["groups"],
+     "AllowedRedirectURIs": [
+       "http://localhost:4649/oidc/callback",
+       "http://localhost:4646/ui/settings/tokens"
+     ],
+     "ListClaimMappings": {
+       "groups": "roles"
+     }
+   }
+   ```
+
+   The `ListClaimMappings` field specifies which claims of the OIDC provider
+   should be mapped to which ACL concepts of Nomad. The Vault
+   "group" created before will map to a "role" in Nomad.
+
+1. Create a new OIDC authentication method and configure it to use the Vault OIDC
+   provider.
+
+   ```shell-session
+   $ nomad acl auth-method create \
+       -default=true \
+       -name=vault \
+       -token-locality=global \
+       -max-token-ttl="10m" \
+       -type=oidc \
+       -config @acl_auth_method.json
+   ```
+
+1. Create a binding rule to evaluate OIDC claims into Nomad policies and roles.
+
+   ```shell-session
+   $ nomad acl binding-rule create \
+       -auth-method=vault \
+       -bind-type=role \
+       -bind-name="engineering-read" \
+       -selector="engineering in list.roles"
+   ```
+
+Nomad OIDC authentication is configured and ready for the `end-user` to
+authenticate.
+
+## Authenticate with Nomad
+
+Authenticate to Nomad. The `-method` flag is optional since `vault` has been configured as the default method.
+
+   ```shell-session
+   $ nomad login -method=vault
+   ```
+
+The Vault login screen will open in your browser. Select **Username** from the
+**Method** dropdown selection and enter `end-user` and `password` as the credentials.
+
+The `nomad login` command confirms the authentication was successful and
+displays the Nomad ACL token generated.
+
+   ```shell-session hideClipboard
+   Successfully logged in via OIDC and vault
+
+   Accessor ID  = 48008488-21ae-35d7-f1d6-0066a7eb902a
+   Secret ID    = d7a803e6-abd6-a80e-dd95-5f88d904cc9e
+   Name         = vault
+   Type         = client
+   Global       = true
+   Create Time  = 2023-01-13 10:06:35.933899 +0000 UTC
+   Expiry Time  = 2023-01-13 10:16:35.933899 +0000 UTC
+   Create Index = 19
+   Modify Index = 19
+   Policies     = []
+
+   Roles
+   ID                                    Name
+   197deab1-a963-91fc-2936-05923eecf0c0  engineering-read
+   ```
+
+## Next steps
+
+In this guide, you configured Vault as an OIDC provider with Nomad as a
+client. Learn more about [configuring Vault as an OIDC provider](/vault/docs/secrets/identity/oidc-provider).
diff --git a/content/nomad/v1.10.x/content/docs/secure/index.mdx b/content/nomad/v1.10.x/content/docs/secure/index.mdx
new file mode 100644
index 0000000000..5fe404d208
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/index.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Secure Nomad
+description: |-
+  This section provides guidance on securing Nomad. Configure a Nomad cluster for ACLs, bootstrap the ACL system, author your first policy, and grant a token based on it. Configure SSO options such as OIDC and JWT. Use workload identity to federate access to AWS and GCP.
+---
+
+# Secure Nomad
+
+This section provides guidance on securing Nomad. Configure a Nomad cluster for ACLs, bootstrap the ACL system, author your first policy, and grant a token based on it. Configure SSO options such as OIDC and JWT. Use workload identity to federate access to AWS and GCP.
diff --git a/content/nomad/v1.10.x/content/docs/secure/traffic/gossip-encryption.mdx b/content/nomad/v1.10.x/content/docs/secure/traffic/gossip-encryption.mdx
new file mode 100644
index 0000000000..936722caef
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/traffic/gossip-encryption.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Enable gossip encryption
+description: |-
+  Create an encryption key and then configure Nomad to encrypt the gossip protocol, which communicates membership and node health information between Nomad servers.
+---
+
+# Enable gossip encryption
+
+Nomad server's gossip protocol that is used to communicate membership and
+liveness information can be encrypted with symmetric keys. Enabling gossip
+encryption requires you to set an encryption key when starting the Nomad server.
+The key can be set via the [`encrypt`] parameter or with the [`-encrypt` command
+line option]. The key must be a base64-encoded string of 32 random bytes.
+The same encryption key should be used on every server in a region.
+
+<Note>
+
+To secure RPC and HTTP communication, you will need to configure
+TLS. You can learn how in the [Enable TLS encryption guide][tls-guide].
+
+</Note>
+
+## Generate an encryption key
+
+The Nomad CLI includes a `operator gossip keyring generate` command for generating a new secure
+gossip encryption key.
+
+```shell-session
+$ nomad operator gossip keyring generate
+4kRkFQfcc3LU0BazP1ca+z==
+```
+
+Current and older versions of `nomad operator gossip keyring generate` return 16 bytes; however,
+Nomad supports gossip encryption keys of 32 bytes as well. Supplying a 32 byte key
+enables AES-256 mode, where supplying a 16 byte key enables AES-128 mode.
+
+Alternatively, you can use any method that can create 32 random bytes encoded in
+base64.
+
+```shell-session
+$ openssl rand -base64 32
+4YwLQm6ZMwYgfldNBT5P76tAWMdcBmu+FPYRvCxvsHc=
+```
+
+```shell-session
+$ dd if=/dev/urandom bs=32 count=1 status=none | base64
+IisA4F7Mu/RwGfBZelcsFzMlJ4+twnO5Z7eoTzD0T6c=
+```
+
+## Configure the server to use the key
+
+Put the same generated key into every server's configuration file or command
+line arguments:
+
+```hcl
+server {
+  enabled = true
+
+  # Self-elect, should be 3 or 5 for production. This is only for single node
+  # clusters which are strictly for development/demo.
+  bootstrap_expect = 1
+
+  # Encrypt gossip communication
+  encrypt = "+p7iF56z0EWoSIvhpYHWXZrSAAtnjR9l6XHRzHqQKlg="
+}
+```
+
+## Restart the server to enable encryption
+
+You can perform a rolling restart of the Nomad process on each of your server
+nodes to enable encryption. Restart your servers one at a time in order to
+maintain a quorum of nodes on one side or the other of this soft partition.
+
+Once all of the nodes have been restarted all gossip traffic will be encrypted
+between all of your server nodes.
+
+## Next steps
+
+If you would like to learn more technical information about Nomad's gossip
+protocol, consult the [Serf library] documentation.
+
+[tls-guide]: /nomad/docs/secure/traffic/tls
+[`-encrypt` command line option]: /nomad/commands/agent
+[`encrypt`]: /nomad/docs/configuration/server#encrypt
+[`nomad operator gossip keyring` command]: /nomad/commands/operator/gossip/keyring-generate
+[serf library]: https://www.serf.io/docs/internals/gossip.html
+[tls]: /nomad/docs/configuration/tls
diff --git a/content/nomad/v1.10.x/content/docs/secure/traffic/index.mdx b/content/nomad/v1.10.x/content/docs/secure/traffic/index.mdx
new file mode 100644
index 0000000000..4a3b6be59f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/traffic/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Traffic encryption overview
+description: |-
+  Discover the methods of transport encryption used by Nomad and how
+  they are used to encrypt all network traffic to and from a Nomad
+  agent.
+---
+
+# Traffic encryption overview
+
+The Nomad agent supports encrypting all of its network traffic. There are
+two separate encryption systems, one for gossip traffic, and one for HTTP and
+RPC.
+
+Once you complete this collection you will have configured transport encryption for
+all of Nomad's protocols. RPC and HTTP communication is secured with mTLS.
+Nomad servers also communicate with a gossip protocol, Serf, which is encrypted
+using symmetric encryption and preshared keys.
+
+To review Nomad uses two different encryption schemes for its traffic.
+
+- HTTP - Used to communicate between CLI and Nomad agents. Secured by mTLS.
+- RPC - Used to communicate between Nomad agents. Secured by mTLS.
+- Serf - Used to communicate between Nomad servers. Frequently referred to as
+  "gossip". Secured by a shared key.
+
+Use the [Enable TLS Encryption for Nomad][] guide to configure Nomad for mTLS
+and the [Enable Gossip Encryption for Nomad][] to configure gossip encryption
+using a pre-shared key.
+
+[enable tls encryption for nomad]: /nomad/docs/secure/traffic/tls
+[enable gossip encryption for nomad]: /nomad/docs/secure/traffic/gossip-encryption
diff --git a/content/nomad/v1.10.x/content/docs/secure/traffic/tls.mdx b/content/nomad/v1.10.x/content/docs/secure/traffic/tls.mdx
new file mode 100644
index 0000000000..900f37c526
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/traffic/tls.mdx
@@ -0,0 +1,479 @@
+---
+layout: docs
+page_title: Enable TLS encryption
+description: |-
+  Create mutual TLS (mTLS) certificates and configure Nomad to encrypt API and
+  RPC traffic.
+---
+
+# Enable TLS encryption
+
+Securing Nomad's cluster communication is not only important for security but
+can even ease operations by preventing mistakes and misconfigurations. Nomad
+optionally uses mutual [TLS][tls] (mTLS) for all HTTP and RPC communication.
+Nomad's use of mTLS provides the following properties:
+
+- Prevent unauthorized Nomad access
+- Prevent observing or tampering with Nomad communication
+- Prevent client/server role or region misconfigurations
+- Prevent other services from masquerading as Nomad agents
+
+Preventing region misconfigurations is a property of Nomad's mTLS not commonly
+found in the TLS implementations on the public Internet. While most uses of
+TLS verify the identity of the server you are connecting to based on a domain
+name such as `example.com`, Nomad verifies the node you are connecting to is in
+the expected region and configured for the expected role (e.g.
+`client.us-west.nomad`). This also prevents other services who may have access
+to certificates signed by the same private CA from masquerading as Nomad
+agents. If certificates were identified based on hostname/IP then any other
+service on a host could masquerade as a Nomad agent.
+
+Correctly configuring TLS can be a complex process, especially given the wide
+range of deployment methodologies. If you use the sample
+[Vagrantfile][vagrantfile] from the [Nomad GitHub repository][nomad-repo] - or
+have Nomad installed - this guide will provide you with a production ready
+TLS configuration.
+
+~> Note that while Nomad's TLS configuration will be production ready, key
+management and rotation is a complex subject not covered by this guide.
+[Vault][vault] is the suggested solution for key generation and management.
+
+## Creating certificates
+
+The first step to configuring TLS for Nomad is generating certificates. In
+order to prevent unauthorized cluster access, Nomad requires all certificates
+be signed by the same Certificate Authority (CA). This should be a _private_ CA
+and not a public one like [Let's Encrypt][letsencrypt] as any certificate
+signed by this CA will be allowed to communicate with the cluster.
+
+~> Nomad certificates may be signed by intermediate CAs as long as the root CA
+is the same. Append all intermediate CAs to the `cert_file`.
+
+### Certificate authority
+
+There are a variety of tools for managing your own CA, [like the PKI secret
+backend in Vault][vault-pki], but for the sake of simplicity this guide will
+use the Nomad [`tls ca create`][] command.
+
+Generate the CA's private key and certificate.
+
+```shell-session
+$ nomad tls ca create
+```
+
+The CA key (`nomad-agent-ca-key.pem`) will be used to sign certificates for Nomad
+agents and must be kept private. The CA certificate (`nomad-agent-ca.pem`) contains
+the public key necessary to validate Nomad certificates and therefore must be
+distributed to every node that requires access.
+
+### Agent certificates
+
+Once you have a CA certificate and key you can generate and sign the
+certificates Nomad will use directly. TLS certificates commonly use the
+fully-qualified domain name of the system being identified as the certificate's
+Common Name (CN). However, hosts (and therefore hostnames and IPs) are often
+ephemeral in Nomad clusters. Not only would signing a new certificate per
+Nomad node be difficult, but using a hostname provides no security or
+functional benefits to Nomad. To fulfill the desired security properties
+(above) Nomad certificates are signed with their region and role such as:
+
+- `client.global.nomad` for a client node in the `global` region
+- `server.us-west.nomad` for a server node in the `us-west` region
+
+Generate a certificate for the Nomad server.
+
+```shell-session
+$ nomad tls cert create -server -region global
+```
+
+Generate a certificate for the Nomad client.
+
+```shell-session
+$ nomad tls cert create -client
+```
+
+Generate a certificate for the CLI.
+
+```shell-session
+$ nomad tls cert create -cli
+```
+
+Using `localhost` and `127.0.0.1` as subject alternate names (SANs) allows
+tools like `curl` to be able to communicate with Nomad's HTTP API when run on
+the same host. Other SANs may be added including a DNS resolvable hostname to
+allow remote HTTP requests from third party tools.
+
+You should now have the following files:
+
+- `nomad-agent-ca-key.pem` - CA private key. **Keep safe.**
+
+- `nomad-agent-ca.pem` - CA public certificate.
+
+- `global-cli-nomad-key.pem` - Nomad CLI private key for the `global` region.
+
+- `global-cli-nomad.pem` - Nomad CLI certificate for the `global` region.
+
+- `global-client-nomad-key.pem` - Nomad client node private key for the
+  `global` region.
+
+- `global-client-nomad.pem` - Nomad client node public certificate for the
+  `global` region.
+
+- `global-server-nomad-key.pem` - Nomad server node private key for the
+  `global` region.
+
+- `global-server-nomad.pem` - Nomad server node public certificate for the
+  `global` region.
+
+Each Nomad node should have the appropriate key (`-key.pem`) and certificate
+(`.pem`) file for its region and role. In addition each node needs the CA's
+public certificate (`nomad-agent-ca.pem`).
+
+## Configuring Nomad
+
+Next Nomad must be configured to use the newly-created key and certificates for
+mTLS. Starting with the [server configuration from the Getting Started
+guide][guide-server] add the following TLS configuration options:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/server1"
+
+# Enable the server
+server {
+  enabled = true
+
+  # Self-elect, should be 3 or 5 for production
+  bootstrap_expect = 1
+}
+
+# Require TLS
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-server-nomad.pem"
+  key_file  = "global-server-nomad-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+The new [`tls`][tls_block] section is worth breaking down in more detail:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+  # ...
+}
+```
+
+This enables TLS for the HTTP and RPC protocols. Unlike web servers, Nomad
+doesn't use separate ports for TLS and non-TLS traffic: your cluster should
+either use TLS or not.
+
+```hcl
+tls {
+  # ...
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-server-nomad.pem"
+  key_file  = "global-server-nomad-key.pem"
+
+  # ...
+}
+```
+
+The file lines should point to wherever you placed the certificate files on
+the node. This guide assumes they are in Nomad's current directory.
+
+```hcl
+tls {
+  # ...
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+These two settings are important for ensuring all of Nomad's mTLS security
+properties are met. If [`verify_server_hostname`][verify_server_hostname] is
+set to `false` the node's certificate will be checked to ensure it is signed by
+the same CA, but its role and region will not be verified. This means any
+service with a certificate signed by same CA as Nomad can act as a client or
+server of any region.
+
+[`verify_https_client`][verify_https_client] requires HTTP API clients to
+present a certificate signed by the same CA as Nomad's certificate. It may be
+disabled to allow HTTP API clients (e.g. Nomad CLI, Consul, or curl) to
+communicate with the HTTPS API without presenting a client-side certificate. If
+`verify_https_client` is enabled only HTTP API clients presenting a certificate
+signed by the same CA as Nomad's certificate are allowed to access Nomad.
+
+~> Enabling `verify_https_client` effectively protects Nomad from unauthorized
+network access at the cost of losing Consul HTTPS health checks for agents.
+
+### Client configuration
+
+The Nomad client configuration is similar to the server configuration. The
+biggest difference is in the certificate and key used for configuration.
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/client1"
+
+# Enable the client
+client {
+  enabled = true
+
+  # For demo assume you are talking to server1. For production,
+  # this should be like "nomad.service.consul:4647" and a system
+  # like Consul used for service discovery.
+  server_join {
+    retry_join = ["127.0.0.1:4647"]
+  }
+}
+
+# Modify our port to avoid a collision with server1
+ports {
+  http = 5656
+}
+
+# Require TLS
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-client-nomad.pem"
+  key_file  = "global-client-nomad-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+### Running with TLS
+
+Now that you have certificates generated and configuration for a client and
+server you can test our TLS-enabled cluster!
+
+In separate terminals start a server and client agent:
+
+In one terminal start a server process.
+
+```shell-session
+$ nomad agent -config server1.hcl
+```
+
+And in another terminal, start a client.
+
+```shell-session
+$ nomad agent -config client1.hcl
+```
+
+If you run `nomad node status` now, you'll get an error, like:
+
+```plaintext
+Error querying node status: Unexpected response code: 400 (Client sent an HTTP request to an HTTPS server.)
+```
+
+This is because the Nomad CLI defaults to communicating via HTTP instead of
+HTTPS. You can configure the local Nomad client to connect using TLS and specify
+our custom keys and certificates using the command line:
+
+```shell-session
+$ nomad node status \
+    -ca-cert=nomad-agent-ca.pem \
+    -client-cert=global-cli-nomad.pem \
+    -client-key=global-cli-nomad-key.pem \
+    -address=https://127.0.0.1:4646
+```
+
+This process can be cumbersome to type each time, so the Nomad CLI also
+searches environment variables for default values. Use the following commands to
+set environment variables in your shell.
+
+`NOMAD_ADDR` is the URL of the Nomad agent and sets the default for `-addr`.
+
+```shell-session
+$ export NOMAD_ADDR=https://localhost:4646
+```
+
+`NOMAD_CACERT` is the location of your CA certificate and sets the default for `-ca-cert`.
+
+```shell-session
+$ export NOMAD_CACERT=nomad-agent-ca.pem
+```
+
+`NOMAD_CLIENT_CERT` is the location of your CLI certificate and sets the default for `-client-cert`.
+
+```shell-session
+$ export NOMAD_CLIENT_CERT=global-cli-nomad.pem
+```
+
+`NOMAD_CLIENT_KEY` is the location of your CLI key and sets the default for `-client-key`.
+
+```shell-session
+$ export NOMAD_CLIENT_KEY=global-cli-nomad-key.pem
+```
+
+After these environment variables are correctly configured, the CLI will respond as expected.
+Run `nomad node status`.
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+237cd4c5  dc1  nomad  <none>  false  eligible     ready
+```
+
+Or, generate and run a sample job.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> Monitoring evaluation "e9970e1d"
+    Evaluation triggered by job "example"
+    Allocation "a1f6c3e7" created: node "237cd4c5", group "cache"
+    Evaluation within deployment: "080460ce"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "e9970e1d" finished with status "complete"
+```
+
+## Switching an existing cluster to TLS
+
+Since Nomad does _not_ use different ports for TLS and non-TLS communication,
+the use of TLS must be consistent across the cluster. Switching an existing
+cluster to use TLS everywhere is operationally similar to upgrading between
+versions of Nomad, but requires additional steps to preventing needlessly
+rescheduling allocations.
+
+1. Add the appropriate key and certificates to all nodes. Ensure the private
+   key file is only readable by the Nomad user.
+1. Add the environment variables to all nodes where the CLI is used.
+1. Add the appropriate [`tls`][tls_block] block to the configuration file on
+   all nodes.
+1. Generate a gossip key and add it the Nomad server configuration.
+
+~> Once a quorum of servers are TLS-enabled, clients will no longer be able to
+communicate with the servers until their client configuration is updated and
+reloaded.
+
+At this point a rolling restart of the cluster will enable TLS everywhere.
+However, once servers are restarted clients will be unable to heartbeat. This
+means any client unable to restart with TLS enabled before their heartbeat TTL
+expires will have their allocations marked as `lost` and rescheduled.
+
+While the default heartbeat settings may be sufficient for concurrently
+restarting a small number of nodes without any allocations being marked as
+`lost`, most operators should raise the [`heartbeat_grace`][heartbeat_grace]
+configuration setting before restarting their servers:
+
+1. Set `heartbeat_grace = "1h"` or an appropriate duration on servers.
+1. Restart servers, one at a time.
+1. Restart clients, one or more at a time.
+1. Set [`heartbeat_grace`][heartbeat_grace] back to its previous value (or
+   remove to accept the default).
+1. Restart servers, one at a time.
+
+~> In a future release Nomad will allow upgrading a cluster to use TLS by
+allowing servers to accept TLS and non-TLS connections from clients during
+the migration.
+
+Jobs running in the cluster will _not_ be affected and will continue running
+throughout the switch as long as all clients can restart within their heartbeat
+TTL.
+
+## Changing Nomad certificates on the fly
+
+As of 0.7.1, Nomad supports dynamic certificate reloading via SIGHUP.
+
+Given a prior TLS configuration as follows:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-ca.pem"
+  cert_file = "server.pem"
+  key_file  = "server-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+Nomad's cert_file and key_file can be reloaded via SIGHUP by updating the TLS
+stanza to:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-ca.pem"
+  cert_file = "new_server.pem"
+  key_file  = "new_server_key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+## Migrating a cluster to TLS
+
+### Reloading TLS configuration via SIGHUP
+
+Nomad supports dynamically reloading both client and server TLS configuration.
+To reload an agent's TLS configuration, first update the TLS block in the
+agent's configuration file and then send the Nomad agent a SIGHUP signal.
+Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its TLS
+configuration during a config reload via SIGHUP. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+### RPC upgrade mode for Nomad servers
+
+When migrating to TLS, the [`rpc_upgrade_mode`][rpc_upgrade_mode] option
+(defaults to `false`) in the TLS configuration for a Nomad server can be set
+to true. When set to true, servers will accept both TLS and non-TLS
+connections. By accepting non-TLS connections, operators can upgrade clients
+to TLS without the clients being marked as lost because the server is
+rejecting the client connection due to the connection not being over TLS.
+However, it is important to note that `rpc_upgrade_mode` should be used as a
+temporary solution in the process of migration, and this option should be
+re-set to false (meaning that the server will strictly accept only TLS
+connections) once the entire cluster has been migrated.
+
+[guide-install]: /nomad/tutorials/get-started/get-started-install
+[guide-server]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/server.hcl
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[letsencrypt]: https://letsencrypt.org/
+[nomad-repo]: https://github.com/hashicorp/nomad
+[rpc_upgrade_mode]: /nomad/docs/configuration/tls#rpc_upgrade_mode
+[tls]: https://en.wikipedia.org/wiki/Transport_Layer_Security
+[tls_block]: /nomad/docs/configuration/tls
+[vagrantfile]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+[vault-pki]: /vault/docs/secrets/pki
+[vault]: /vault/
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[verify_server_hostname]: /nomad/docs/configuration/tls#verify_server_hostname
+[`tls ca create`]: /nomad/commands/tls/ca-create
diff --git a/content/nomad/v1.10.x/content/docs/secure/vault/acl.mdx b/content/nomad/v1.10.x/content/docs/secure/vault/acl.mdx
new file mode 100644
index 0000000000..7ff637887e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/vault/acl.mdx
@@ -0,0 +1,376 @@
+---
+layout: docs
+page_title: Integrate Vault ACL
+description: |-
+  Learn how to protect your Nomad cluster with the Vault access control list (ACL) system and use workload identities with Vault. Configure Vault authentication.
+---
+
+# Integrate Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. It must be
+properly configured in order for the Vault and Nomad integrations to work.
+
+## Nomad workload identities
+
+Starting in Nomad 1.10.0, Nomad clients use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault ACL token specific to the task.
+
+By default, Nomad only generates a workload identity for tasks that can be used
+to access Nomad itself, such as for reading [Variables][] from a [`template`][]
+block. To access Vault, jobs must have additional workload identities defined
+as [`identity`][] blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure the Nomad servers with the [`vault.default_identity`][] agent
+configuration. Upon job registration, the Nomad servers update tasks that have
+a [`vault`][] block with this default identity.
+
+You can also specify identities for Vault directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Vault][jobspec_identity_vault] section of the `identity` block
+documentation for more information.
+
+### Configuring Vault authentication
+
+Vault must be configured to receive, validate, and trust these Nomad workload
+identities. Since they are encoded as [JSON Web Tokens (JWTs)][jwt], you must
+create a [JWT ACL auth method][vault_jwt_auth_method]. The auth method is an
+endpoint that Nomad can use to exchange workload identities for Vault ACL
+tokens.
+
+Refer to Vault's [Authentication][vault_auth] documentation for more
+information.
+
+#### Vault auth method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Vault servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Vault is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The `jwks_url` address must be reachable by all Vault servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `jwks_url` value.
+
+[![Vault Auth Method][img_vault_auth_method]][img_vault_auth_method]
+
+When an allocation that needs access to Vault starts, the Nomad client
+running it exchanges the Nomad workload identities for tasks for Vault ACL
+tokens.
+
+[![Vault JWT Login][img_vault_wid_acl_token]][img_vault_wid_acl_token]
+
+#### Vault ACL role
+
+A Vault [ACL role][vault_role] groups multiple ACL policies to apply to a token
+and determine the permissions it receives.
+
+The auth method may define a default ACL role that is applied to the ACL tokens
+it generates. If no default role is set, the role must be provided in the job
+using the [`vault.role`][] parameter or in the Nomad client configuration
+[`vault.create_from_role`][].
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The ACL role specifies the list of authorized audience values using the
+[`bound_audiences`][], which must have at least one match with the values
+defined in the Nomad workload identity [`aud`][] parameter. For security
+reasons, it is recommended to only define a single audience value.
+
+<CodeBlockConfig highlight="3" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced in Vault ACL configuration. The ACL role uses the
+[`claim_mappings`][] parameter to determine which of these claims are made
+available to the rest of the configuration.
+
+The [`bound_claims`][] parameter restricts which workload identities are able
+to use the role based on their claims. Refer to Vault's [Bound
+Claims][vault_bound_claims] documentation for more information.
+
+<CodeBlockConfig highlight="4-7,10-14" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Vault has different [types of ACL tokens][vault_token_types]. Nomad typically
+uses tokens of type `service` since they can be renewed for as long as the
+workload is active. Nomad automatically renews the Vault ACL tokens it generates
+before they expire. To ensure the tokens can be renewed for as long as
+necessary, [`token_explicit_max_ttl`][] must be set to 0.
+
+Alternately, you may use `batch` tokens. This should only be used when a secret
+is requested from Vault once at the start of a task or in a short-lived prestart
+task. Long-running tasks should never set `allow_token_expiration=true` if they
+obtain Vault secrets via `template` blocks, as the Vault token will expire and
+the template runner will continue to make failing requests to Vault until its
+[`vault_retry`][] attempts are exhausted, at which point the task will
+fail. Vault's `batch` tokens cannot be renewed, and Nomad will not attempt to
+renew them when configured to use Workload Identity.
+
+<CodeBlockConfig highlight="16-18" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+#### Vault ACL policy
+
+A Vault ACL role may have one or more ACL policies attached. Vault [ACL
+policies][vault_policies] define the permissions granted to an ACL
+token.
+
+<CodeBlockConfig highlight="15" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+ACL policies can reference dynamic values from Nomad workload identities claims
+exposed from the ACL role in [templated policies][vault_templated_policies].
+The exact ACL policy rules will depend on the level of access required by
+tasks.
+
+The following example ACL policy automatically grants `read` permissions to
+secrets in the path `secret/data/<job namespace>/<job name>/*`, where `<job
+namespace>` and `<job name>` are read from the workload identity claims
+`nomad_namespace` and `nomad_job_id`.
+
+<CodeBlockConfig highlight="1,5,9" filename="acl-policy.hcl">
+
+```hcl
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Vault Auth Overview][img_vault_auth_overview]][img_vault_auth_overview]
+
+#### Vault namespaces <EnterpriseAlert inline />
+
+Vault Enterprise supports multiple namespaces and jobs in Nomad Enterprise can
+use the [`vault.namespace`][] parameter to specify which namespace to use. In a
+multi-namespace environment, the authentication setup described must be applied
+to each Vault namespace used by jobs.
+
+### Important considerations about the JWKS URL
+
+The recommended configuration assumes Vault servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Vault and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Vault auth method. Nomad's CA certificate should be
+specified in the Vault auth method's
+[`jwks_ca_pem`](https://developer.hashicorp.com/vault/api-docs/auth/jwt#jwks_ca_pem)
+parameter.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Vault servers not able to connect to Nomad
+
+If the Vault servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`jwt_validation_pubkeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Vault servers, and use that address as the value for
+`jwks_url`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional references
+
+The [Vault ACL with Nomad Workload Identities][vault_tutorial_wid] tutorial
+provides guided instructions on how to configure Vault and Nomad for workload
+identities.
+
+The [`nomad setup vault`][nomad_cli_setup_vault] command and the
+[`hashicorp-modules/nomad-setup/vault`][tf_nomad_setup_vault] Terraform
+module can help you automate the process of applying configuration to a Vault
+cluster.
+
+
+[Variables]: /nomad/docs/concepts/variables
+[Vault Namespaces]: /vault/docs/enterprise/namespaces
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`bound_audiences`]: /vault/api-docs/auth/jwt#bound_audiences
+[`bound_claims`]: /vault/api-docs/auth/jwt#bound_claims
+[`claim_mappings`]: /vault/api-docs/auth/jwt#claim_mappings
+[`identity`]: /nomad/docs/job-specification/identity
+[`jwt_validation_pubkeys`]: /vault/api-docs/auth/jwt#jwt_validation_pubkeys
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[`token_explicit_max_ttl`]: /vault/api-docs/auth/jwt#token_explicit_max_ttl
+[`vault.create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault.namespace`]: /nomad/docs/job-specification/vault#namespace
+[`vault.role`]: /nomad/docs/job-specification/vault#role
+[`vault`]: /nomad/docs/job-specification/vault
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[docs_upgrade]: /nomad/docs/upgrade#upgrade-process
+[ent]: #enterprise-configuration
+[img_vault_auth_method]: /img/vault-integration-auth-method.png
+[img_vault_auth_overview]: /img/vault-integration-auth-overview.png
+[img_vault_wid_acl_token]: /img/vault-integration-wid-acl-token.png
+[jobspec_identity_vault]: /nomad/docs/job-specification/identity#workload-identities-for-vault
+[jwt]: https://jwt.io/
+[nomad_cli_setup_vault]: /nomad/commands/setup/vault
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_vault]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[tutorial_mtls]: /nomad/docs/secure/traffic/tls
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[vault_auth]: /vault/docs/concepts/auth
+[vault_bound_claims]: /vault/docs/auth/jwt#bound-claims
+[vault_jwt_auth_method]: /vault/api-docs/auth/jwt
+[vault_policies]: /vault/docs/concepts/policies
+[vault_role]: /vault/api-docs/auth/jwt#create-update-role
+[vault_templated_policies]: /vault/tutorials/policies/policy-templating
+[vault_token_types]: /vault/tutorials/tokens/tokens#token-types
+[vault_tutorial_wid]: /nomad/docs/secure/workload-identity/vault
diff --git a/content/nomad/v1.10.x/content/docs/secure/vault/index.mdx b/content/nomad/v1.10.x/content/docs/secure/vault/index.mdx
new file mode 100644
index 0000000000..74492df1b2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/vault/index.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Integrate Vault with Nomad to use tokens, password, certificates, API keys, and secrets stored in Vault. Configure Nomad to use Vault access control lists (ACLs) to secure your cluster. Learn how to configure Nomad agents and use Consul Template in your job specification.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal.
+
+## Configuration
+
+In order to use Vault with Nomad, you will need to configure and install Vault
+separately from Nomad. Nomad does not run Vault for you.
+
+## Agent configuration
+
+To enable Vault integration, Nomad agents must be configured with
+[`vault`][] blocks. Each block can be enabled or disabled and configures how
+Nomad connects to the Vault cluster.
+
+## Dynamic configuration with secrets
+
+Nomad's job specification includes a [`template`][] block that uses a tool
+called [Consul Template][]. When used with Vault, this mechanism creates a
+convenient way to ship configuration files that are populated from Vault
+secrets.
+
+For more information on Nomad's template block please see the
+[`template` job specification documentation][].
+
+## Vault access control list (ACL)
+
+The Vault ACL system protects the cluster from unauthorized access. When
+enabled, both Vault and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Vault ACL integration page][int_vault_acl] for more information.
+
+## Multiple vault clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Vault clusters. They can be
+configured using multiple [`vault`][] blocks with different `name` values. If a
+`name` is not provided, the cluster configuration is called `default`.
+
+Jobs that need access to Vault may specify which Vault cluster to use with the
+[`vault.cluster`][] parameter.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Vault.
+
+|               | Vault 1.18.0+ | Vault 1.19.0+ | Vault 1.20.0+ |
+|---------------|---------------|---------------|---------------|
+| Nomad 1.10.0+ | ✅            | ✅            | ✅            |
+| Nomad 1.9.0+  | ✅            | ✅            | ✅            |
+| Nomad 1.8.0+  | ✅            | ✅            | ✅            |
+
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Vault]:  https://www.vaultproject.io/ 'Vault by HashiCorp'
+[`template` job specification documentation]: /nomad/docs/job-specification/template#vault-integration
+[`template`]: /nomad/docs/job-specification/template
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[int_vault_acl]: /nomad/docs/secure/vault/acl
diff --git a/content/nomad/v1.10.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx b/content/nomad/v1.10.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx
new file mode 100644
index 0000000000..306ffbce70
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx
@@ -0,0 +1,406 @@
+---
+layout: docs
+page_title: Federate access to AWS with Nomad Workload Identity
+description: |-
+  Integrate Nomad as an OpenID Connect (OIDC) provider with AWS IAM identity and use workload identity to federate access to AWS resources and services.
+---
+
+# Federate access to AWS with Nomad Workload Identity
+
+This page describes how to integrate Nomad with AWS IAM as an OpenID Connect (OIDC) provider and
+use [Workload Identity] to federate access to AWS resources and services. In this workflow, Nomad
+is the [OpenID Connect Provider] (OP or OIDC provider) and generates JSON Web Tokens (JWTs) which
+serve as workload identities. AWS IAM is the Relying Party (RP) and validates these workload
+identity tokens with Nomad before it permits federated access to resources and services.
+
+## Prerequisites
+
+To integrate Nomad and AWS IAM identity, you need a running Nomad cluster that
+meets the following prerequisites:
+
+- Nomad v1.7.x or later
+- TLS enabled
+
+The instructions on this page also assume the following:
+
+- Your AWS account has the necessary permissions to create IAM roles, policies, hosted zones,
+  and certificates.
+- You are using Terraform to manage your AWS infrastructure and you have
+  [configured it to communicate with AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication-and-configuration).
+
+## Workflow
+
+The process to integrate Nomad as an OIDC provider with AWS consists of the following steps:
+
+1. Create the required AWS resources:
+    - [Route 53 hosted zone](#create-a-hosted-zone)
+    - [AWS Certificate Manager SSL certificates](#generate-ssl-certificates)
+    - [Load balancer and listener](#create-an-application-load-balancer)
+    - [DNS Alias for the load balancer](#create-a-dns-alias)
+    - [OIDC Identity Provider](#create-an-oidc-identity-provider)
+    - [AWS IAM role](#create-an-iam-policy-for-oidc-federated-users)
+1. Update the Nomad server configuration.
+1. Create a jobspec file that accesses AWS and then run it to verify your configuration.
+
+## Create and configure AWS resources
+
+To use Nomad as an identity provider, you need to have a trusted SSL certificate for the
+domain used by the cluster. The following example uses AWS Certificate Manager (ACM).
+
+### Create a hosted zone
+
+Use the [`aws_route53_zone` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone).
+
+```hcl
+variable "domain_name" {
+    type = string
+    default = "<DOMAIN_NAME>"
+}
+
+resource "aws_route53_zone" "example" {
+    name = var.domain_name
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port. `var.domain_name` is used
+throughout the examples on this page to reference `<DOMAIN_NAME>`.
+
+### Generate SSL certificates
+
+Use the [`aws_acm_certificate`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate)
+and [`aws_acm_certificate_validation`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate_validation) resources to create a request and provide validation for an SSL
+certficiate.
+
+```hcl
+variable "zone_id" {
+  type    = string
+  default = "<HOSTED_ZONE_ID>"
+}
+
+resource "aws_acm_certificate" "example" {
+  domain_name       = var.domain_name
+  validation_method = "DNS"
+
+  lifecycle {
+    create_before_destroy = true
+  }
+}
+
+resource "aws_route53_record" "cert_dns" {
+  allow_overwrite = true
+  name            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_name
+  records         = [tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_value]
+  type            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_type
+  zone_id         = var.zone_id
+  ttl             = 60
+}
+
+resource "aws_acm_certificate_validation" "example" {
+  certificate_arn         = aws_acm_certificate.example.arn
+  validation_record_fqdns = [aws_route53_record.cert_dns.fqdn]
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+
+### Create an Application Load Balancer
+
+Use the [`aws_lb` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb).
+
+```hcl
+resource "aws_lb" "test" {
+  name               = "test-lb-tf"
+  internal           = false
+  load_balancer_type = "application"
+  security_groups    = [<SECURITY_GROUP_ID>]
+  subnets            = [<SUBNET_IDS>]
+
+  enable_deletion_protection = true
+
+  access_logs {
+    bucket  = <S3_BUCKET_ID>
+    prefix  = "test-lb"
+    enabled = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<SECURITY_GROUP_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#security_groups):
+A list of security groups IDs that you want to apply to the load balancer.
+- [`<SUBNET_IDS>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#subnets):
+A list of subnet IDs that you want to attach to the load balancer.
+- [`<S3_BUCKET_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#bucket):
+The ID of an S3 bucket to store the load balancer access logs in.
+
+### Create a load balancer listener
+
+Use the [`aws_lb_listener` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener).
+
+```hcl
+resource "aws_lb_listener" "example" {
+  load_balancer_arn = <LB_ARN>
+  port              = "443"
+  protocol          = "HTTPS"
+  ssl_policy        = "ELBSecurityPolicy-2016-08"
+  certificate_arn   = <CERT_ARN>
+
+  default_action {
+    type             = "forward"
+    target_group_arn = <LB_TARGET_GROUP_ARN>
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<LB_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#load_balancer_arn):
+The AWS resource name of the load balancer. This will be `aws_lb.test.arn` if you are using the
+examples from this page.
+- [`<CERT_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#certificate_arn):
+The AWS resource name of the load balancer's certificate. This will be
+`aws_acm_certificate_validation.example.certificate_arn` if you are using the examples from this
+page.
+- [`<LB_TARGET_GROUP_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#target_group_arn): The AWS resource name of the target group for the load balancer to route traffic to. This group
+includes your Nomad server instances.
+
+### Create a DNS Alias
+
+Use the [`aws_route53_record` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record).
+
+```hcl
+resource "aws_route53_record" "www" {
+  zone_id = <HOSTED_ZONE_ID>
+  name    = var.domain_name
+  type    = "A"
+
+  alias {
+    name                   = <LB_ALIAS_DNS_NAME>
+    zone_id                = <LB_ALIAS_ZONE_ID>
+    evaluate_target_health = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+- [`<LB_ALIAS_DNS_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#name):
+The DNS
+name of the load balancer. This will be `aws_lb.test.dns_name` if you are using the examples
+from this page.
+- [`<LB_ALIAS_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The zone ID of the load balancer. This will be `aws_lb.test.zone_id` if you are using the
+examples from this page.
+
+### Create an OIDC Identity Provider
+
+Use the [`aws_iam_openid_connect_provider` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider).
+
+```hcl
+data "tls_certificate" "example" {
+  url = <CERT_DOMAIN_NAME>
+}
+
+resource "aws_iam_openid_connect_provider" "nomad" {
+  # Nomad HTTPS URL
+  url = <CERT_DOMAIN_NAME>
+
+  client_id_list = [
+    "aws",
+  ]
+
+  thumbprint_list = [data.tls_certificate.example.certificates.0.sha1_fingerprint]
+}
+```
+
+This configuration requires the following information:
+- [`<CERT_DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider#url):
+The domain name of the load balancer certificate. This will be
+`aws_acm_certificate.example.domain_name` if you are using the examples from this page.
+
+### Create an IAM policy for OIDC Federated Users
+
+Use the [`aws_iam_role` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role)
+to create an appropriate IAM role for workloads acting as federated users. This will be
+specific to your use case. The following example allows workloads access to S3 buckets.
+
+```hcl
+# Variables for OIDC provider and AWS account
+variable "oidc_provider" {
+  description = "The OIDC provider URL"
+  type        = string
+  default     = "<DOMAIN_NAME>"
+}
+
+variable "aws_account_id" {
+  description = "AWS account ID"
+  type        = string
+  default     = "<AWS_ACCOUNT_ID>"
+}
+
+data "aws_iam_policy_document" "assume_role" {
+  statement {
+    effect = "Allow"
+
+    principals {
+      type        = "Federated"
+      identifiers = ["arn:aws:iam::${var.aws_account_id}:oidc-provider/${var.oidc_provider}"]
+    }
+
+    actions = ["sts:AssumeRoleWithWebIdentity"]
+
+    condition {
+      test     = "StringEquals"
+      variable = "${var.oidc_provider}:aud"
+      values   = ["aws"]
+    }
+  }
+}
+
+# Create an IAM role with the assume role policy generated above
+resource "aws_iam_role" "s3_all_access_role" {
+  name               = "s3_all_access_role"
+  assume_role_policy = data.aws_iam_policy_document.assume_role.json
+
+  tags = {
+    tag-key = "tag-value"
+  }
+}
+
+# Inline policy that defines what the role can do (full S3 access)
+data "aws_iam_policy_document" "s3_access_policy" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "s3:*",
+      "s3-object-lambda:*"
+    ]
+
+    resources = ["*"] # You can scope this down to specific S3 buckets if necessary
+  }
+}
+
+# Create a policy resource from the inline policy document above
+resource "aws_iam_policy" "policy" {
+  name        = "nomad-oidc-policy"
+  description = "A policy for federated Nomad OIDC"
+  policy      = data.aws_iam_policy_document.s3_access_policy.json
+}
+
+# Attach the S3 access policy to the IAM role
+resource "aws_iam_role_policy_attachment" "test-attach" {
+  role       = aws_iam_role.s3_all_access_role.name
+  policy_arn = aws_iam_policy.policy.arn
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+
+## Update the Nomad server configuration
+
+After you configure AWS, modify the Nomad server configuration file. Add the
+[`oidc_issuer` attribute](/nomad/docs/configuration/server#oidc_issuer) and set the value
+to the domain name for the Nomad cluster. This [enables the HTTP endpoint in Nomad](https://developer.hashicorp.com/nomad/docs/configuration/server#oidc_issuer) that allows third parties to discover Nomad's OIDC
+configuration.
+
+```hcl
+server {
+  enabled = true
+  [...]
+  oidc_issuer = "https://<DOMAIN_NAME>"
+  [...]
+}
+```
+
+This configuration requires the following information:
+- `<DOMAIN_NAME>`: The domain name of your Nomad cluster without the protocol or port.
+
+Restart the Nomad server agent to apply the configuration changes.
+
+## Create and run a sample jobspec file
+
+Create and run a jobspec file to validate your configuration. The following file is named `s3-upload.nomad.hcl`, add the following configuration to it, and
+save the file.
+
+```hcl
+job "s3" {
+  type = "batch"
+  group "bucket" {
+    task "copy" {
+      driver = "docker"
+      config {
+        image = "public.ecr.aws/aws-cli/aws-cli"
+        command = "s3"
+        args = ["cp", "/local/test.txt", "s3://<S3_BUCKET_NAME>/test-nomad.txt"]
+      }
+
+      identity {
+        name = "aws"
+        aud = ["aws"]
+        file = true
+        ttl = "1h"
+
+        # AWS SDKs gracefully handle OIDC/WebIdentity reauthentication when the
+        # session or token expire, therefore a restart isn't needed
+        change_mode = "noop"
+      }
+
+      template {
+        destination = "local/test.txt"
+        change_mode = "restart"
+        data        = <<EOF
+Job:          {{ env "NOMAD_JOB_NAME" }}
+Alloc:        {{ env "NOMAD_ALLOC_ID" }}
+EOF
+      }
+
+      env {
+        AWS_ROLE_ARN = "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>"
+        # The format of the token file is nomad_$NAME_OF_IDENTITY.jwt
+        AWS_WEB_IDENTITY_TOKEN_FILE = "${NOMAD_SECRETS_DIR}/nomad_aws.jwt"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+This configuration requires the following information:
+- `<S3_BUCKET_NAME>`: The name of the S3 bucket where the test file will be saved.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+- `<IAM_ROLE_NAME>`: The name of the IAM role from previous steps. This will be
+`s3_all_access_role` if you are using the examples from this page.
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run s3-upload.nomad.hcl
+```
+
+Verify that the job completed successfully.
+
+```shell-session
+$ nomad job status s3
+```
+
+Verify that the file was also uploaded to the S3 bucket.
+
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[OpenID Connect Provider]: https://openid.net/developers/how-connect-works/
diff --git a/content/nomad/v1.10.x/content/docs/secure/workload-identity/index.mdx b/content/nomad/v1.10.x/content/docs/secure/workload-identity/index.mdx
new file mode 100644
index 0000000000..d9ca2d5dd0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/workload-identity/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Use workload identity to federate cloud access
+description: |-
+  This section provides guidance on using Nomad workload identity to federate access to AWS and GCP.
+---
+
+# Use workload identity to federate cloud access
+
+This section provides guidance on using Nomad workload identity to federate
+access to AWS and GCP.
diff --git a/content/nomad/v1.10.x/content/docs/secure/workload-identity/vault.mdx b/content/nomad/v1.10.x/content/docs/secure/workload-identity/vault.mdx
new file mode 100644
index 0000000000..3ce9ef6ba0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/secure/workload-identity/vault.mdx
@@ -0,0 +1,1343 @@
+---
+layout: docs
+page_title: Use workload identities with Vault
+description: |-
+  Configure Vault to accept Nomad workload identities, run a Nomad job to read
+  secrets from Vault, configure dynamic secrets in Vault, and run a job with a
+  custom Vault ACL role.
+---
+
+# Use workload identities with Vault
+
+Nomad integrates with Vault to retrieve [static][vault_static] and
+[dynamic][vault_dyn] secrets for workloads.
+
+Production deployments of Nomad and Vault must always run with the Access
+Control List (ACL) system enabled since it protects against unauthorized
+access to the cluster. When ACLs are enabled, both Nomad and Vault must be
+properly configured in order for their integrations to work.
+
+Nomad can generate [workload identities][nomad_wid] for tasks, which are
+represented as [JSON Web Tokens (JWT)][jwt] signed by Nomad. These identities
+can be used as proof to third parties that a workload was actually created and
+is managed by Nomad. If the third party is configured to trust Nomad, it can
+automatically grant specific access and permissions to Nomad workloads.
+
+In this guide, you will:
+
+- Start a Nomad and Vault agent with ACL enabled.
+- Generate ACL tokens to access Nomad and Vault.
+- Configure Vault to accept workload identities from Nomad.
+- Configure Nomad to automatically generate and sign workload identities for
+  tasks that need access to Vault.
+- Deploy sample Nomad jobs that interact with Vault.
+
+## Prerequisites
+
+This guide requires you to have basic familiarity with Nomad and Vault. If
+you are new to these tools, complete the [Nomad Get Started][nomad_gs]
+and [Vault Get Started][vault_gs] tutorials before following this one.
+
+You will need the following tools installed:
+
+- [Nomad 1.7 or later installed locally][nomad_install]
+- [Vault 1.12 or later installed locally][vault_install]
+- [Docker installed and running locally][docker_install]
+
+## Start the Vault agent
+
+Start a Vault dev server.
+
+```shell-session
+$ vault server -dev
+==> Vault server configuration:
+
+Administrative Namespace:
+             Api Address: http://127.0.0.1:8200
+                     Cgo: disabled
+         Cluster Address: https://127.0.0.1:8201
+   Environment Variables: CLICOLOR, COLORTERM, COMMAND_MODE, EDITOR, GODEBUG, GOPATH, HOME, LANG, LC_ALL, LOGNAME, LSCOLORS, LaunchInstanceID, OLDPWD, PATH, PWD, SECURITYSESSIONID, SHELL, SHLVL, SSH_AUTH_SOCK, TERM, TERM_PROGRAM, TERM_PROGRAM_VERSION, TMPDIR, USER, WINDOWID, XPC_FLAGS, XPC_SERVICE_NAME, _, __CFBundleIdentifier, __CF_USER_TEXT_ENCODING
+              Go Version: go1.21.3
+              Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
+               Log Level:
+                   Mlock: supported: false, enabled: false
+           Recovery Mode: false
+                 Storage: inmem
+                 Version: Vault v1.15.2, built 2023-11-06T11:33:28Z
+             Version Sha: cf1b5cafa047bc8e4a3f93444fcb4011593b92cb
+
+==> Vault server started! Log data will stream in below:
+
+2023-11-20T20:08:27.583-0500 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
+2023-11-20T20:08:27.583-0500 [INFO]  incrementing seal generation: generation=1
+...
+WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
+and starts unsealed with a single unseal key. The root token is already
+authenticated to the CLI, so you can immediately begin using Vault.
+
+You may need to set the following environment variables:
+
+    $ export VAULT_ADDR='http://127.0.0.1:8200'
+
+...
+```
+
+<Note title="Dev Agents">
+
+This guide uses development agents for Vault and [Nomad][nomad_dev] as a
+quick way to get started. Dev agents have ephemeral state and should not be
+used in production environments. They also run in the foreground of your
+terminal so do not close the terminal window or you will need to rerun the
+agent configuration steps again.
+
+</Note>
+
+Copy the value for `Root Token`.
+
+Open another terminal window in the same directory and set the root token as
+the environment variable `VAULT_TOKEN`. This terminal will act as the main
+terminal session where you will run commands.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export VAULT_TOKEN=...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export VAULT_TOKEN=...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:VAULT_TOKEN = "..."
+```
+
+</Tab>
+</Tabs>
+
+Set the environment variable `VAULT_ADDR`.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export VAULT_ADDR='http://127.0.0.1:8200'
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export VAULT_ADDR='http://127.0.0.1:8200'
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:VAULT_ADDR = "http://127.0.0.1:8200"
+```
+
+</Tab>
+</Tabs>
+
+## Start the Nomad agent
+
+Create a file named `nomad.hcl`. Add the following contents to it and save the
+file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+The [`vault`][nomad_config_vault] block in this configuration file provides
+the information necessary for Nomad to connect to Vault.
+
+It also defines a default workload identity, `default_identity`, that is
+automatically added to jobs that need access to Vault. Without this identity,
+you would need to define an `identity` block in your jobs for every task that
+needs access to Vault.
+
+Open another terminal window in the same directory and start the Nomad dev
+agent.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ sudo nomad agent -dev -config 'nomad.hcl'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ nomad agent -dev -config 'nomad.hcl' -network-interface '{{GetDefaultInterfaces | attr "name"}}'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ nomad agent -dev -config 'nomad.hcl' -network-interface '{{GetDefaultInterfaces | attr \"name\"}}'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+</Tabs>
+
+Return to your main terminal window and bootstrap the Nomad ACL system.
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = d1de8625-8556-0932-a25c-3aa71bfc0134
+Secret ID    = 7f10099a-936c-3f3a-8783-f0980493e54b
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2023-11-16 01:09:26.565422 +0000 UTC
+Expiry Time  = <none>
+Create Index = 23
+Modify Index = 23
+Policies     = n/a
+Roles        = n/a
+```
+
+Copy the value of `Secret ID` and set it as the environment variable
+`NOMAD_TOKEN`.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export NOMAD_TOKEN=...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export NOMAD_TOKEN=...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:NOMAD_TOKEN = "..."
+```
+
+</Tab>
+</Tabs>
+
+<Note title="Using Bootstrap Tokens">
+
+The initial ACL bootstrap tokens from Vault and Nomad have full access to the
+cluster and should not be used for regular day-to-day operations in a
+production environment. They are used in this guide as an illustration.
+We recommend creating [ACL policies][nomad_acl_policies] and
+[tokens][nomad_acl_tokens] with only a level of access necessary to perform the
+required operations.
+
+</Note>
+
+## Configure Vault to accept Nomad workload identities
+
+### Create a Vault ACL auth method
+
+Enable a `jwt` [auth method][vault_auth_method] in Vault under the path
+`jwt-nomad`.
+
+```shell-session
+$ vault auth enable -path 'jwt-nomad' 'jwt'
+Success! Enabled jwt auth method at: jwt-nomad/
+```
+
+The JWT auth method creates an endpoint that Nomad clients use to exchange
+Nomad workload identity JWTs for Vault ACL tokens.
+
+Create a file named `vault-auth-method-jwt-nomad.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-auth-method-jwt-nomad.json">
+
+```json
+{
+  "jwks_url": "http://127.0.0.1:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+This configuration file contains important information.
+
+* `jwks_url` is the URL that Vault uses to contact Nomad and retrieve the data
+  necessary to validate Nomad workload identities. In a production environment,
+  this should resolve to multiple Nomad agents via a reverse proxy, load
+  balancer, or DNS entry to prevent a single point of failure.
+* `default_role` is the Vault ACL role applied by default to tokens generated
+  by this auth method. You will create the `nomad-workloads` role in the next
+  section.
+
+Apply the configuration file `vault-auth-method-jwt-nomad.json` to the
+`jwt-nomad` auth method.
+
+```shell-session
+$ vault write auth/jwt-nomad/config '@vault-auth-method-jwt-nomad.json'
+Success! Data written to: auth/jwt-nomad/config
+```
+
+### Create a Vault ACL role
+
+Create a file named `vault-role-nomad-workloads.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-role-nomad-workloads.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+It defines properties for the Vault ACL tokens that are used for Nomad tasks.
+
+* `bound_audiences` configures Vault to only accept JWTs that have an audience
+  value of `vault.io`. It must match the `aud` value present in the Nomad agent
+  configuration and jobs.
+* `claim_mappings` are values from the Nomad workload identity. You will
+  reference them when creating the Vault ACL policy for this role.
+* `token_period` determines how long the token is valid for before it expires.
+  Nomad automatically renews tokens before they expire.
+* `token_explicit_max_ttl` is the maximum amount of time the token is valid. It
+  must be set to `0` so Nomad can renew them for as long as the workload runs.
+* `token_policies` are the ACL policies applied to the tokens. They specify the
+  permissions that tokens with this role have. You will create the policy
+  `nomad-workloads` policy in the next section.
+
+Create a Vault ACL role named `nomad-workloads` using the
+`vault-role-nomad-workloads.json` file.
+
+```shell-session
+$ vault write auth/jwt-nomad/role/nomad-workloads '@vault-role-nomad-workloads.json'
+Success! Data written to: auth/jwt-nomad/role/nomad-workloads
+```
+
+This role is applied by default to Vault ACL tokens generated from the auth
+method `jwt-nomad`.
+
+### Create a Vault ACL policy
+
+List all of the auth methods registered in Vault.
+
+```shell-session
+$ vault auth list
+Path          Type     Accessor               Description                Version
+----          ----     --------               -----------                -------
+jwt-nomad/    jwt      auth_jwt_d34481ad      n/a                        n/a
+token/        token    auth_token_510d42ca    token based credentials    n/a
+```
+
+Copy the `Accessor` value for the auth method in the `jwt-nomad/` path.
+
+Create a file named `vault-policy-nomad-workloads.hcl`. Add the following
+contents to it, replace all the instances of the `AUTH_METHOD_ACCESSOR`
+placeholder with the `Accessor` value from the output, and save the file. There
+are five occurrences to update.
+
+<CodeBlockConfig filename="vault-policy-nomad-workloads.hcl">
+
+```hcl
+path "kv/data/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "kv/data/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "kv/metadata/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "kv/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+This file is a [templated Vault ACL policy][vault_tpl_policy] that
+automatically grants Nomad workloads access to secrets based on the
+properties mapped in the `claim_mappings` of the Vault ACL role.
+
+More specifically, this policy grants access to secrets in the path
+`kv/data/<job namespace>/<job name>/*` where `<job namespace>` and `<job name>`
+are dynamically set for each workload.
+
+Create a Vault ACL policy named `nomad-workloads` using the file
+`vault-policy-nomad-workloads.hcl`.
+
+```shell-session
+$ vault policy write 'nomad-workloads' 'vault-policy-nomad-workloads.hcl'
+Success! Uploaded policy: nomad-workloads
+```
+
+## Run a Nomad job to read secrets from Vault
+
+Start a MongoDB database with a root password that is read from Vault using the
+Nomad workload identity for the task.
+
+Enable the `kv` secret engine.
+
+```shell-session
+$ vault secrets enable -version '2' 'kv'
+Success! Enabled the kv secrets engine at: kv/
+```
+
+Write a secret in Vault for the database root password in the path
+`default/mongo/config`.
+
+```shell-session
+$ vault kv put -mount 'kv' 'default/mongo/config' 'root_password=secret-password'
+======== Secret Path ========
+kv/data/default/mongo/config
+
+======= Metadata =======
+Key                Value
+---                -----
+created_time       2023-11-21T02:52:42.061092Z
+custom_metadata    <nil>
+deletion_time      n/a
+destroyed          false
+version            1
+```
+
+Create a file named `mongo.nomad.hcl`. Add the following contents to it and
+save the file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+
+        mount {
+          type   = "bind"
+          target = "C:\\mongosh"
+          source = "local/mongosh/mongosh-2.1.0-win32-x64/"
+        }
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+
+      artifact {
+        source      = "https://downloads.mongodb.com/compass/mongosh-2.1.0-win32-x64.zip"
+        destination = "local/mongosh"
+      }
+
+      resources {
+        memory = 1000
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+* The `vault` block indicates that the task needs access to Vault and that
+  Nomad should use the task workload identity to get a Vault ACL token.
+* The `template` block reads the root password secret from Vault under the
+  path `kv/data/default/mongo/config`.
+* The job runs in the Nomad `default` namespace and the job name is `mongo`.
+  The `nomad-workloads` Vault role grants access to secrets in the path
+  `kv/data/default/mongo/*`, which is where the root password exists.
+* The job does not specify any identity for Vault, so Nomad uses the
+  `default_identity` from the agent configuration.
+
+Run the job with the `mongo.nomad.hcl` file and wait for the deployment to
+complete.
+
+```shell-session
+$ nomad job run 'mongo.nomad.hcl'
+==> 2023-11-20T22:09:16-05:00: Monitoring evaluation "34e72e7a"
+    2023-11-20T22:09:16-05:00: Evaluation triggered by job "mongo"
+    2023-11-20T22:09:17-05:00: Evaluation within deployment: "919f658b"
+    2023-11-20T22:09:17-05:00: Allocation "49fc68d8" created: node "b8db12d2", group "db"
+    2023-11-20T22:09:17-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2023-11-20T22:09:17-05:00: Evaluation "34e72e7a" finished with status "complete"
+==> 2023-11-20T22:09:17-05:00: Monitoring deployment "919f658b"
+  ✓ Deployment "919f658b" successful
+
+    2023-11-20T22:09:28-05:00
+    ID          = 919f658b
+    Job ID      = mongo
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    db          1        1       1        0          2023-11-20T22:19:26-05:00
+```
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" mongosh --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" mongosh --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+Create the `root` user, reading the credentials from the environment variables
+set in the job from the Vault secret.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" powershell -command  'C:\mongosh\bin\mongosh.exe mongodb://localhost:27017/admin --quiet --eval ""db.createUser({user: ''$Env:MONGO_INITDB_ROOT_USERNAME'', pwd: ''$Env:MONGO_INITDB_ROOT_PASSWORD'', roles: [{role: ''root'', db: ''admin''}]})""'
+{ ok: 1 }
+```
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" C:\mongosh\bin\mongosh.exe 'mongodb://localhost:27017' --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+</Tabs>
+
+
+Retrieve the job definition from Nomad and filter the output to only display
+its task.
+
+```shell-session
+$ nomad job inspect -t '{{sprig_toPrettyJson (index (index .TaskGroups 0).Tasks 0)}}' 'mongo'
+{
+  "Name": "mongo",
+  "Driver": "docker",
+  "User": "",
+  "Lifecycle": null,
+  "Config": {
+    "image": "mongo:7",
+    "ports": [
+      "db"
+    ]
+  },
+...
+```
+
+The `Identities` list contains the workload identity that Nomad injects
+following the specification in the `default_identity` block from the Nomad
+server configuration file.
+
+<CodeBlockConfig highlight="13-26" hideClipboard>
+
+```json
+{
+  "Name": "mongo",
+  "Driver": "docker",
+  "User": "",
+  "Lifecycle": null,
+  "Config": {
+    "image": "mongo:7",
+    "ports": [
+      "db"
+    ]
+  },
+...
+  "Identities": [
+    {
+      "Name": "vault_default",
+      "Audience": [
+        "vault.io"
+      ],
+      "ChangeMode": "",
+      "ChangeSignal": "",
+      "Env": false,
+      "File": false,
+      "ServiceName": "",
+      "TTL": 3600000000000
+    }
+  ],
+  "Actions": null
+}
+```
+
+</CodeBlockConfig>
+
+By configuring Vault to accept workload identities from Nomad, the Nomad task
+was able to automatically receive a Vault ACL token scoped to the level of
+access defined by the auth method default role. With this method, Nomad agents
+no longer require long-lived, highly permissive Vault tokens.
+
+## Configure Vault dynamic secrets for MongoDB
+
+The MongoDB database reads a secret from Vault using the permissions in the
+default Vault ACL role.
+
+In some situations, it may be necessary to customize the permissions granted to
+a task to be different from this default. This is done by creating additional
+Vault ACL roles for Nomad jobs.
+
+Configure Vault with a [dynamic secret][vault_dyn] for a non-root MongoDB user
+that the default Vault ACL policy does not grant access to then run a Nomad job
+using a custom Vault ACL role to be able to access the dynamic secret.
+
+Enable the Vault database secrets engine.
+
+```shell-session
+$ vault secrets enable database
+Success! Enabled the database secrets engine at: database/
+```
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@127.0.0.1:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+
+Retrieve the IP address for MongoDB from Nomad.
+
+```shell-session
+$ nomad service info mongo
+Job ID  Address              Tags  Node ID   Alloc ID
+mongo   192.168.0.171:27017  []    b8db12d2  49fc68d8
+```
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it, replace the placeholder `MONGO_IP` text with the IP address
+from the Nomad `service info` command, and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@MONGO_IP:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+
+Retrieve the IP address for MongoDB from Nomad.
+
+```shell-session
+$ nomad service info mongo
+Job ID  Address              Tags  Node ID   Alloc ID
+mongo   192.168.0.171:27017  []    b8db12d2  49fc68d8
+```
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it, replace the placeholder `MONGO_IP` text with the IP address
+from the Nomad `service info` command, and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@MONGO_IP:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+Write the `vault-dynamic-secret-mongo.json` configuration for the MongoDB
+dynamic secret to connect to the database.
+
+```shell-session
+$ vault write 'database/config/mongo' '@vault-dynamic-secret-mongo.json'
+Success! Data written to: database/config/mongo
+```
+
+Create a file named `vault-database-role-mongo.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-database-role-mongo.json">
+
+```json
+{
+    "db_name": "mongo",
+    "creation_statements": "{ \"db\": \"admin\", \"roles\": [{ \"role\": \"readWrite\" }, {\"role\": \"read\", \"db\": \"foo\"}] }",
+    "default_ttl": "1h",
+    "max_ttl": "24h"
+}
+```
+
+</CodeBlockConfig>
+
+Create a Vault database role using the `vault-database-role-mongo.json` file.
+
+```shell-session
+$ vault write 'database/roles/mongo' '@vault-database-role-mongo.json'
+Success! Data written to: database/roles/mongo
+```
+
+### Create a Vault ACL role to access the dynamic secret
+
+Create a file named `vault-role-mongo-dynamic-secret.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-role-mongo-dynamic-secret.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo-query"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["mongo-dynamic-secret"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+This role is similar to the one from earlier in the guide but this one uses
+a different policy, called `mongo-dynamic-secret`, which you will create in the
+next section.
+
+It also defines a set of `bound_claims` to restrict which workload identities
+from Nomad are able to use this role. In this example, the role only allows the
+job `mongo-query` in the Nomad namespace `default` to use it.
+
+Create the `mongo-dynamic-secret` ACL role using the
+`vault-role-mongo-dynamic-secret.json` file.
+
+```shell-session
+$ vault write 'auth/jwt-nomad/role/mongo-dynamic-secret' '@vault-role-mongo-dynamic-secret.json'
+Success! Data written to: auth/jwt-nomad/role/mongo-dynamic-secret
+```
+
+Create a file named `vault-policy-mongo-dynamic-secret.hcl`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-policy-mongo-dynamic-secret.hcl">
+
+```hcl
+path "database/creds/mongo" {
+  capabilities = ["read"]
+}
+```
+
+</CodeBlockConfig>
+
+This ACL policy only grants access to the specific path `database/creds/mongo`,
+which is not included in the default role used by the `jwt-nomad` auth method.
+
+Create the `mongo-dynamic-secret` ACL policy using the
+`vault-policy-mongo-dynamic-secret.hcl` file.
+
+```shell-session
+$ vault policy write 'mongo-dynamic-secret' 'vault-policy-mongo-dynamic-secret.hcl'
+Success! Uploaded policy: mongo-dynamic-secret
+```
+
+## Run a Nomad job with a custom Vault ACL role
+
+Create a file named `mongo-query.nomad.hcl`. Add the following contents to it
+and save the file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "mongosh"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "mongosh"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "C:\\mongosh\\bin\\mongosh.exe"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+
+        mount {
+          type   = "bind"
+          target = "C:\\mongosh"
+          source = "local/mongosh/mongosh-2.1.0-win32-x64/"
+        }
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+
+      artifact {
+        source      = "https://downloads.mongodb.com/compass/mongosh-2.1.0-win32-x64.zip"
+        destination = "local/mongosh"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+Note that the `vault` block specifies the `mongo-dynamic-secret` role. The task
+can only access the dynamic credentials for MongoDB.
+
+The `template` block reads these credentials and exposes them as environment
+variables to the task so it can use them.
+
+Run the Nomad job from the file `mongo-query.nomad.hcl`.
+
+```shell-session
+$ nomad job run 'mongo-query.nomad.hcl'
+==> 2023-11-20T23:11:35-05:00: Monitoring evaluation "5fa56c67"
+    2023-11-20T23:11:35-05:00: Evaluation triggered by job "mongo-query"
+    2023-11-20T23:11:36-05:00: Allocation "909f0184" created: node "b8db12d2", group "mongo-query"
+    2023-11-20T23:11:36-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2023-11-20T23:11:36-05:00: Evaluation "5fa56c67" finished with status "complete"
+```
+
+Retrieve the allocation information and wait until the status is `complete`.
+You may need to run the command a few times before the status changes to
+`complete`.
+
+```shell-session
+$ nomad job allocs 'mongo-query'
+ID        Node ID   Task Group   Version  Desired  Status    Created  Modified
+909f0184  b8db12d2  mongo-query  0        run      complete  25s ago  24s ago
+```
+
+Retrieve the query result to confirm the job was able to connect to the MongoDB
+database.
+
+```shell-session
+$ nomad alloc logs $(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' mongo-query)
+{
+  authInfo: {
+    authenticatedUsers: [
+      {
+        user: 'v-jwt-nomad-mongo-mongo-QbF7HWHjwOi6PJWmNo1x-1700544973',
+        db: 'admin'
+      }
+    ],
+    authenticatedUserRoles: [ { role: 'readWrite', db: 'admin' }, { role: 'read', db: 'foo' } ]
+  },
+  ok: 1
+}
+```
+
+Note that the authenticated user is now a dynamic user credential.
+
+Templated Vault ACL policies provide great flexibility when defining access
+rules, but a single policy, or a specific group of policies, may not be enough
+to cover all use cases.
+
+Creating additional Vault ACL roles for specific Nomad jobs can help better
+manage access control to Vault secrets.
+
+## Next steps
+
+In this guide, you configured Nomad and Vault to communicate with ACL
+enabled. You also configured Nomad to automatically add workload identities for
+tasks that need access to Vault.
+
+You then deployed Nomad jobs to read static and dynamic secrets from Vault
+using different Vault ACL roles and policies. Both jobs used their workload
+identities to receive a Vault ACL token properly scoped to the work they
+needed to do.
+
+This process required several steps, with certain values having to match each
+other in order for everything to work properly.
+
+There are two resources available to help you automate these steps.
+
+* The Nomad CLI command `nomad setup vault` can be useful for a quick setup
+  with default values for a development or test cluster.
+* The [`hashicorp-modules/nomad-setup/vault`][tf_module] Terraform module
+  provides a basis for applying these steps with a infrastructure-as-code
+  approach, which is more suitable for a production environment. The
+  [`hashicorp-guides/nomad-workload-identity-terraform-demo`][tf_demo]
+  repository demonstrates how this module can be used.
+
+You may continue exploring additional integrations between Nomad and Vault or
+learn how to similarly [integrate Nomad and Consul][nomad_consul_acl] with ACL
+enabled.
+
+- [Nomad and Vault Integration][nomad_integrations_vault]
+- [Nomad Workload Identity][nomad_wid]
+- [Nomad Agent `vault` Configuration][nomad_config_vault]
+- [Vault ACL policies tutorial][vault_tutorial_policies]
+
+[docker_install]: https://www.docker.com/get-started/
+[jwt]: https://jwt.io/
+[nomad_acl_policies]: /nomad/docs/secure/acl/policies
+[nomad_acl_tokens]: /nomad/docs/secure/acl/tokens
+[nomad_config_vault]: /nomad/docs/configuration/vault
+[nomad_consul_acl]: /nomad/tutorials/integrate-consul/consul-acl
+[nomad_dev]: /nomad/commands/agent#dev
+[nomad_gs]: /nomad/tutorials/get-started
+[nomad_install]: /nomad/install
+[nomad_integrations_vault]: /nomad/docs/secure/vault
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[tf_demo]: https://github.com/hashicorp-guides/nomad-workload-identity-terraform-demo
+[tf_module]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[vault_auth_method]: /vault/docs/auth
+[vault_dyn]: /vault/docs/use-cases#dynamic-secrets
+[vault_gs]: /vault/tutorials/get-started
+[vault_install]: /vault/install
+[vault_static]: /vault/docs/use-cases#static-secrets
+[vault_tpl_policy]: /vault/docs/concepts/policies#templated-policies
+[vault_tutorial_policies]: /vault/tutorials/policies
diff --git a/content/nomad/v1.10.x/content/docs/stateful-workloads/csi-volumes.mdx b/content/nomad/v1.10.x/content/docs/stateful-workloads/csi-volumes.mdx
new file mode 100644
index 0000000000..20896686d1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/stateful-workloads/csi-volumes.mdx
@@ -0,0 +1,661 @@
+---
+layout: docs
+page_title: Use CSI volumes
+description: >-
+  Configure and deploy the AWS EBS volume CSI plugin to connect an EBS volume
+  to a MySQL workload that requires persistent storage.
+---
+
+# Use CSI volumes
+
+Nomad’s [Container Storage Interface (CSI)][csi-spec] integration can manage
+external storage volumes for stateful workloads running inside your
+cluster. CSI providers are third-party plugins that run as Nomad jobs
+and can mount volumes created by your cloud provider. Nomad is aware
+of CSI-managed volumes during the scheduling process, enabling it to
+schedule your workloads based on the availability of volumes on a
+specific client.
+
+Each storage provider builds its own CSI plugin, and you can leverage
+all of them in Nomad. You can launch jobs that claim storage volumes
+from AWS Elastic Block Storage (EBS) or Elastic File System (EFS)
+volumes, GCP persistent disks, Digital Ocean droplet storage volumes,
+or vendor-agnostic third-party providers like Portworx. This also
+means that many plugins written by storage providers to support
+Kubernetes will support Nomad as well. You can find a list of plugins
+in the [Kubernetes CSI Developer Documentation][k8s-drivers].
+
+Unlike Nomad’s [`host_volume`] feature, CSI-managed volumes can be added
+and removed from a Nomad cluster without changing the Nomad client
+configuration.
+
+Using Nomad’s CSI integration consists of three core workflows:
+running CSI plugins, registering volumes for those plugins, and
+running jobs that claim those volumes. In this guide, you'll run the
+AWS Elastic Block Storage (EBS) plugin, register an EBS volume for
+that plugin, and deploy a MySQL workload that claims that volume for
+persistent storage.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need:
+
+- a Nomad environment on AWS with Consul installed. You can use this [Terraform
+  environment][nomad-tf] to provision a sandbox environment. This tutorial will
+  assume a cluster with one server node and two client nodes.
+
+- Nomad v1.3.0 or greater
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node. Consult the [reference architecture][reference-arch] for production
+configuration.
+
+</Note>
+
+### Install the MySQL client
+
+You will use the MySQL client to connect to our MySQL database and
+verify our data. Ensure it is installed on a node with access to port
+3306 on your Nomad clients:
+
+Ubuntu:
+
+```shell-session
+$ sudo apt install mysql-client
+```
+
+CentOS:
+
+```shell-session
+$ sudo yum install mysql
+```
+
+macOS via Homebrew:
+
+```shell-session
+$ brew install mysql-client
+```
+
+### Deploy an AWS EBS volume
+
+Next, create an AWS EBS volume for the CSI plugin to mount where needed
+for your jobs using the same Terraform stack you used
+to create the Nomad cluster.
+
+Add the following new resources to your Terraform stack.
+
+```hcl
+resource "aws_iam_role_policy" "mount_ebs_volumes" {
+  name   = "mount-ebs-volumes"
+  role   = aws_iam_role.instance_role.id
+  policy = data.aws_iam_policy_document.mount_ebs_volumes.json
+}
+
+data "aws_iam_policy_document" "mount_ebs_volumes" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "ec2:DescribeInstances",
+      "ec2:DescribeTags",
+      "ec2:DescribeVolumes",
+      "ec2:AttachVolume",
+      "ec2:DetachVolume",
+    ]
+    resources = ["*"]
+  }
+}
+
+resource "aws_ebs_volume" "mysql" {
+  availability_zone = aws_instance.client[0].availability_zone
+  size              = 40
+}
+
+output "ebs_volume" {
+    value = <<EOM
+# volume registration
+type        = "csi"
+id          = "mysql"
+name        = "mysql"
+external_id = "${aws_ebs_volume.mysql.id}"
+plugin_id   = "aws-ebs0"
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+EOM
+}
+```
+
+Run `terraform plan` and `terraform apply` to create the new IAM
+policy and EBS volume. Then run `terraform output ebs_volume > volume.hcl`. You'll use this file later to register the volume with
+Nomad.
+
+#### Notes about the above Terraform configuration
+
+- The IAM policy document and role policy are being added to the
+  existing instance role for your EC2 instances. This policy will give
+  the EC2 instances the ability to mount the volume you've created in
+  Terraform, but will not give them the ability to create new volumes.
+
+- The EBS volume resource is the data volume you will attach via CSI
+  later. The output will be used to register the volume with Nomad.
+
+## Enable privileged Docker jobs
+
+CSI Node plugins must run as privileged Docker jobs because they use
+bidirectional mount propagation in order to mount disks to the underlying host.
+
+CSI Plugins running as `node` or `monolith` type require root privileges (or
+CAP_SYS_ADMIN on Linux) to mount volumes on the host. With the Docker task
+driver, you can use the `privileged = true` configuration, but no other default
+task drivers currently have this option.
+
+Nomad’s default configuration does not allow privileged Docker jobs, and must be
+edited to allow them.
+
+~> Bidirectional mount propagation can be dangerous and can damage the host
+operating system. For this reason, it is only allowed in privileged containers.
+
+To enable, edit the configuration for all of your Nomad clients, and set
+[`allow_privileged`][] to true inside of the Docker plugin’s configuration.
+Restart the Nomad client process to load this new configuration.
+
+If your Nomad client configuration does not already specify a Docker plugin
+configuration, this minimal one will allow privileged containers. Add it to your
+Nomad client configuration and restart Nomad.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_privileged = true
+  }
+}
+```
+
+There are certain Docker configurations that can prevent privileged containers
+from performing mounts on the host. The error message will likely contain the
+phrase "linux mounts: path ... is mounted on ... but it is not a shared mount".
+More information can be found in the [Docker forums][docker-forums]
+
+If you do not have privileged containers enabled in Nomad, you will receive the
+following error when you submit the plugin-aws-ebs-nodes job:
+
+```plaintext
+Failed to create container configuration for image
+"amazon/aws-ebs-csi-driver:v0.10.1": Docker privileged mode is disabled on this
+Nomad agent
+```
+
+## Deploy the EBS plugin
+
+Plugins for CSI are run as Nomad jobs with a `plugin` stanza. The
+official plugin for AWS EBS can be found on GitHub in the
+[`aws-ebs-csi-driver`][aws-ebs-csi-driver] repository. It’s packaged as a
+Docker container that you can run with the Docker task driver.
+
+Each CSI plugin supports one or more types: Controllers and
+Nodes. Node instances of a plugin need to run on every Nomad client
+node where you want to mount volumes. You'll probably want to run Node
+plugins instances as Nomad `system` jobs. Some plugins also require
+coordinating Controller instances that can run on any Nomad client
+node.
+
+The AWS EBS plugin requires a controller plugin to coordinate access
+to the EBS volume, and node plugins to mount the volume to the EC2
+instance. You'll create a controller job as a nomad `service` job and
+the node job as a Nomad `system` job.
+
+Create a file for the controller job called `plugin-ebs-controller.nomad.hcl` with the following content.
+
+```hcl
+job "plugin-aws-ebs-controller" {
+  datacenters = ["dc1"]
+
+  group "controller" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-ebs-csi-driver:v0.10.1"
+
+        args = [
+          "controller",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+      }
+
+      csi_plugin {
+        id        = "aws-ebs0"
+        type      = "controller"
+        mount_dir = "/csi"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+Create a file for the node job named `plugin-ebs-nodes.nomad.hcl` with the following content.
+
+```hcl
+job "plugin-aws-ebs-nodes" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but this ensures
+  # that all nodes in the DC have a copy.
+  type = "system"
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-ebs-csi-driver:v0.10.1"
+
+        args = [
+          "node",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # node plugins must run as privileged jobs because they
+        # mount disks to the host
+        privileged = true
+      }
+
+      csi_plugin {
+        id        = "aws-ebs0"
+        type      = "node"
+        mount_dir = "/csi"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+## Deploy the plugin jobs
+
+Deploy both jobs with `nomad job run plugin-ebs-controller.nomad.hcl` and
+`nomad job run plugin-ebs-nodes.nomad.hcl`. It will take a few moments
+for the plugins to register themselves as healthy with Nomad after the
+job itself is running. You can check the plugin status with the `nomad plugin status` command.
+
+Note that the plugin does not have a namespace, even though the jobs
+that launched it do. Plugins are treated as resources available to the
+whole cluster in the same way as Nomad clients.
+
+```shell-session
+$ nomad job status
+ID                         Type     Priority  Status   Submit Date
+plugin-aws-ebs-controller  service  50        running  2020-03-20T10:49:13-04:00
+plugin-aws-ebs-nodes       system   50        running  2020-03-20T10:49:17-04:00
+```
+
+```shell-session
+$ nomad plugin status aws-ebs0
+ID                   = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+de2929cc  ac41c184  controller  0        run      running  1m26s ago  1m8s ago
+d1d4831e  ac41c184  nodes       0        run      running  1m22s ago  1m18s ago
+2b815e02  b896731a  nodes       0        run      running  1m22s ago  1m14s ago
+```
+
+## Register the volume
+
+The CSI plugins need to be told about each volume they manage, so for
+each volume you'll run `nomad volume register`. Earlier you used
+Terraform to output a `volume.hcl` file with the volume definition.
+
+```shell-session
+$ nomad volume register volume.hcl
+```
+
+```shell-session
+$ nomad volume status mysql
+ID                   = mysql
+Name                 = mysql
+External ID          = vol-0b756b75620d63af5
+Plugin ID            = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+Access Mode          = <none>
+Attachment Mode      = <none>
+Mount Options        = <none>
+Namespace            = default
+
+Allocations
+No allocations placed
+```
+
+The volume status output above indicates that the volume is
+ready to be scheduled, but has no allocations currently using it.
+
+## Deploy MySQL
+
+### Create the job file
+
+You are now ready to deploy a MySQL database that can use Nomad host
+volumes for storage. Create a file called `mysql.nomad.hcl` and provide it
+the following contents.
+
+```hcl
+job "mysql-server" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mysql-server" {
+    count = 1
+
+    volume "mysql" {
+      type            = "csi"
+      read_only       = false
+      source          = "mysql"
+      access_mode     = "single-node-writer"
+      attachment_mode = "file-system"
+    }
+
+    network {
+      port "db" {
+        static = 3306
+      }
+    }
+
+    restart {
+      attempts = 10
+      interval = "5m"
+      delay    = "25s"
+      mode     = "delay"
+    }
+
+    task "mysql-server" {
+      driver = "docker"
+
+      volume_mount {
+        volume      = "mysql"
+        destination = "/srv"
+        read_only   = false
+      }
+
+      env {
+        MYSQL_ROOT_PASSWORD = "password"
+      }
+
+      config {
+        image = "hashicorp/mysql-portworx-demo:latest"
+        args  = ["--datadir", "/srv/mysql"]
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500
+        memory = 1024
+      }
+
+      service {
+        name = "mysql-server"
+        port = "db"
+
+        check {
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+#### Notes about the above job specification
+
+- The service name is `mysql-server` which you will use later to
+  connect to the database.
+
+- The `read_only` argument is supplied on all of the volume-related
+  stanzas in to help highlight all of the places you would need to
+  change to make a read-only volume mount. Consult the [`volume`],
+  and [`volume_mount`] specifications for more details.
+
+- For lower-memory instances, you might need to reduce the requested
+  memory in the resources stanza to harmonize with available resources
+  in your cluster.
+
+### Run the job
+
+Register the job file you created in the previous step with the
+following command.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "aa478d82"
+    Evaluation triggered by job "mysql-server"
+    Allocation "6c3b3703" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "aa478d82" finished with status "complete"
+```
+
+The allocation status will have a section for the CSI volume, and the
+volume status will show the allocation claiming the volume.
+
+```shell-session
+$ nomad alloc status 6c3b3703
+CSI Volumes:
+ID     Read Only
+mysql  false
+```
+
+```shell-session
+$ nomad volume status mysql
+ID                   = mysql
+Name                 = mysql
+External ID          = vol-0b756b75620d63af5
+Plugin ID            = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = <none>
+Namespace            = default
+
+Allocations
+ID        Node ID   Task Group    Version  Desired  Status   Created    Modified
+6c3b3703  ac41c184  mysql-server  3        run      running  1m40s ago  1m2s ago
+```
+
+## Write data to MySQL
+
+### Connect to MySQL
+
+Using the mysql client (installed [earlier][install_mysql]), connect
+to the database and access the information.
+
+```shell-session
+$ mysql -h mysql-server.service.consul -u web -p -D itemcollection
+```
+
+The password for this demo database is `password`.
+
+<Note>
+
+ This tutorial is for demo purposes and does not
+follow best practices for securing database passwords. Consult [Keeping
+Passwords Secure][password-security] for more information.
+
+</Note>
+
+Consul is installed alongside Nomad in this cluster so you are able to
+connect using the `mysql-server` service name you registered with our
+task in our job file.
+
+### Add test data
+
+Once you are connected to the database, verify the table `items`
+exists.
+
+```sql
+mysql> show tables;
++--------------------------+
+| Tables_in_itemcollection |
++--------------------------+
+| items                    |
++--------------------------+
+1 row in set (0.00 sec)
+```
+
+Display the contents of this table with the following command.
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
++----+----------+
+3 rows in set (0.00 sec)
+```
+
+Now add some data to this table (after you terminate our database in
+Nomad and bring it back up, this data should still be intact).
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('glove');
+```
+
+Run the `INSERT INTO` command as many times as you like with different
+values.
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('hat');
+mysql> INSERT INTO items (name) VALUES ('keyboard');
+```
+
+Once you are done, type `exit` and return back to the Nomad client
+command line.
+
+```sql
+mysql> exit
+Bye
+```
+
+## Destroy the database job
+
+Run the following command to stop and purge the MySQL job from the
+cluster.
+
+```shell-session
+$ nomad stop -purge mysql-server
+==> Monitoring evaluation "6b784149"
+    Evaluation triggered by job "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6b784149" finished with status "complete"
+```
+
+Verify mysql is no longer running in the cluster.
+
+```shell-session
+$ nomad job status mysql
+No job(s) with prefix or id "mysql" found
+```
+
+## Re-deploy and verify
+
+Using the `mysql.nomad.hcl` job file [from earlier][create-job], re-deploy
+the database to the Nomad cluster.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "61b4f648"
+    Evaluation triggered by job "mysql-server"
+    Allocation "8e1324d2" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61b4f648" finished with status "complete"
+```
+
+Once you re-connect to MySQL, you should be able to verify that the
+information you added prior to destroying the database is still
+present.
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
+|  4 | glove    |
+|  5 | hat      |
+|  6 | keyboard |
++----+----------+
+6 rows in set (0.00 sec)
+```
+
+## Cleanup
+
+Once you have completed this guide, you should perform the following
+cleanup steps.
+
+- Stop and purge the `mysql-server` job.
+
+- Unregister the EBS volume from Nomad with `nomad volume deregister mysql`.
+
+- Stop and purge the `plugin-aws-ebs-controller` and `plugin-aws-ebs-nodes` job.
+
+- Destroy the EBS volume with `terraform destroy`.
+
+## Summary
+
+In this guide, you deployed a CSI plugin to Nomad, registered an AWS
+EBS volume for that plugin, and created a job that mounted this volume
+to a Docker MySQL container that wrote data that persisted beyond the
+job’s lifecycle.
+
+[`allow_privileged`]: /nomad/docs/deploy/task-driver/docker#allow_privileged
+[`host_volume`]: /nomad/docs/configuration/client#host_volume
+[`volume_mount`]: /nomad/docs/job-specification/volume_mount
+[`volume`]: /nomad/docs/job-specification/volume
+[aws-ebs-csi-driver]: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
+[create-job]: #create-the-job-file
+[csi-spec]: https://github.com/container-storage-interface/spec
+[docker-forums]: https://forums.docker.com/t/make-mount-point-accesible-from-container-to-host-rshared-not-working/108759
+[install_mysql]: #install-the-mysql-client
+[k8s-drivers]: https://kubernetes-csi.github.io/docs/drivers.html
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[password-security]: https://dev.mysql.com/doc/refman/8.0/en/password-security.html
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture#high-availability
diff --git a/content/nomad/v1.10.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx b/content/nomad/v1.10.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx
new file mode 100644
index 0000000000..ece0fca76d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Use dynamic host volumes
+description: >-
+  Create, configure, and deploy a dynamic host volume. Run a Nomad job with a workload that uses the dynamic host volume for the persistent storage of application data.
+---
+
+# Use dynamic host volumes
+
+This page describes how to to create and configure a dynamic host volume and use
+it to persist application data.
+
+## Introduction
+
+Nomad dynamic host volumes manage storage for stateful workloads without
+requiring a restart of the Nomad nodes to apply configuration changes. They
+provide a workload-agnostic way to specify resources and work with the `exec`,
+`java`, and `docker` task drivers. You create dynamic host volumes via the CLI
+or API and then configure the job with the
+[`volume`](/nomad/docs/job-specification/volume) and
+[`volume_mount`](/nomad/docs/job-specification/volume_mount) blocks in the job
+specification.
+
+Refer to the [dynamic host volume
+specification][dhv_spec] for more information on specifying dynamic host
+volumes.
+
+## Requirements
+
+A Nomad cluster v1.10.0 or greater with the Docker task driver enabled.
+
+## Create the volume specification
+
+
+Create a file with the name `volume.hcl`, add the following content to it, and
+save the file.
+
+<CodeBlockConfig filename="volume.hcl">
+
+```hcl
+namespace = "default"
+name      = "example"
+type      = "host"
+
+# mkdir is the default built-in plugin
+plugin_id = "mkdir"
+
+# allows mounting by only one allocation at a time
+capability {
+  access_mode     = "single-node-single-writer"
+  attachment_mode = "file-system"
+}
+```
+
+</CodeBlockConfig>
+
+Create the volume.
+
+```shell-session
+$ nomad volume create ./volume.hcl
+==> Created host volume example with ID 02eb1d8e-945e-50ee-7640-68b92f622870
+  ✓ Host volume "02eb1d8e" ready
+
+    2025-01-21T14:56:35-05:00
+    ID        = 02eb1d8e-945e-50ee-7640-68b92f622870
+    Name      = example
+    Namespace = default
+    Plugin ID = mkdir
+    Node ID   = d87c86d7-d22b-f811-c329-09e263995e86
+    Node Pool = default
+    Capacity  = 0 B
+    State     = ready
+    Host Path = /run/nomad/dev/alloc_mounts/02eb1d8e-945e-50ee-7640-68b92f622870
+```
+
+Verify the volume was fingerprinted on the node with the node ID from the output.
+
+```shell-session
+$ nomad node status -verbose d87c86d7-d22b-f811-c329-09e263995e86
+...
+Host Volumes
+Name         ReadOnly  Source
+example      false     /run/nomad/dev/alloc_mounts/02eb1d8e-945e-50ee-7640-68b92f622870
+...
+```
+
+Set the volume ID as an environment variable.
+
+```shell-session
+$ VOLUME_ID=02eb1d8e-945e-50ee-7640-68b92f622870
+```
+
+## Create and run the job
+
+The following job specification mounts the volume with the name `example` from
+the dynamic host volume specification.
+
+Create a file with the name `example.nomad.hcl`, add the following content to
+it, and save the file.
+
+<CodeBlockConfig filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+
+  group "group" {
+
+    # claim the dynamic host volume for the allocation
+    volume "groupvol" {
+      type            = "host"
+      source          = "example"
+      access_mode     = "single-node-single-writer"
+      attachment_mode = "file-system"
+    }
+
+    network {
+      port "www" {
+        to = 8001
+      }
+    }
+
+    task "task" {
+
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "httpd"
+        args    = ["-vv", "-f", "-p", "8001", "-h", "/srv"]
+        ports   = ["www"]
+      }
+
+      # mount the claimed volume to the task
+      volume_mount {
+        volume      = "groupvol"
+        destination = "/srv"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Run the job.
+
+```shell-session
+$ nomad run ./example.nomad.hcl
+```
+
+## Interact with the host volume
+
+Export the Allocation ID of the job into an environment variable with the name `ALLOC_ID`.
+
+```shell-session
+$ ALLOC_ID=$(nomad alloc status -t '{{ range . }}{{if eq .JobID "example"}}{{if eq .DesiredStatus "run"}}{{ .ID }}{{end}}{{end}}{{end}}')
+```
+
+Open a shell session in the allocation.
+
+```shell-session
+$ nomad alloc exec -job example /bin/sh
+```
+
+In the allocation's shell prompt, write a file to the mounted volume.
+
+```shell-session
+$ echo '<html>hello, world</html>' > /srv/index.html
+```
+
+Exit the allocation's shell session.
+
+```shell-session
+exit
+```
+
+Get the address of the HTTP server running in the allocation.
+
+```shell-session
+$ nomad alloc status $ALLOC_ID
+...
+Allocation Addresses (mode = "bridge"):
+Label  Dynamic  Address
+*www   yes      192.168.1.160:26512 -> 8001
+```
+
+
+Open the address in your web browser or use a tool like `curl` to see the change.
+
+```shell-session
+$ curl -s "http://192.168.1.160:26512"
+<html>hello, world</html>
+```
+
+## Reschedule the allocation
+
+Stop the allocation to force Nomad to reschedule it.
+
+```shell-session
+$ nomad alloc stop $ALLOC_ID
+```
+
+Open a shell session in the replacement allocation.
+
+```shell-session
+$ nomad alloc exec -job example /bin/sh
+```
+
+In the allocation's shell prompt, read the file previously written to the
+mounted volume.
+
+```shell-session
+$ cat /srv/index.html
+<html>hello, world</html>
+```
+
+Exit the allocation's shell session.
+
+```shell-session
+exit
+```
+
+## Clean up
+
+Stop the `example` job.
+
+```shell-session
+$ nomad job stop example
+```
+
+Delete the dynamic host volume.
+
+```shell-session
+$ nomad volume delete -type host $VOLUME_ID
+```
+
+## Next steps
+
+
+Refer to the following resources for more information on dynamic host volumes
+and related concepts.
+
+- [The Nomad Volume Specification][dhv_spec]
+- [The `nomad alloc exec` command][alloc_exec]
+
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
+[config_static_host_vol]: /nomad/docs/configuration/client#host_volume-block
+[tutorial_static_host_vol]: /nomad/docs/stateful-workloads/static-host-volumes
+[tf]: https://github.com/hashicorp/nomad/tree/main/terraform#provision-a-nomad-cluster-in-the-cloud
+[alloc_exec]: /nomad/commands/alloc/exec
diff --git a/content/nomad/v1.10.x/content/docs/stateful-workloads/index.mdx b/content/nomad/v1.10.x/content/docs/stateful-workloads/index.mdx
new file mode 100644
index 0000000000..5a5e679a61
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/stateful-workloads/index.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Stateful workloads
+description: >-
+  Discover how to create and configure workloads requiring persistent
+  storage with Nomad's CSI integration, Docker volumes support, and
+  host volumes support.
+---
+
+# Stateful workloads
+
+Nomad allows users to mount persistent data from local or remote storage volumes
+into task environments in several ways:
+
+- Container Storage Interface (CSI) plugins
+- Nomad dynamic host volumes
+- Nomad static host volumes
+- Task driver specific volumes, such as Docker volume drivers
+
+Nomad's [Container Storage Interface (CSI)][csi-spec] integration can manage
+external storage volumes for stateful workloads running inside your cluster. CSI
+providers are third-party plugins that run as Nomad jobs and can orchestrate the creation and
+mounting of volumes created by your cloud or storage provider. [AWS Elastic Block Storage],
+[Azure disk], [GCE Persistent Disk], and [Alicloud Disk] are a few of the available
+block-device plugins available as CSI plugins. You can find a more comprehensive list
+in the [CSI Developer Documentation][csi-drivers]
+
+Nomad is aware of CSI-managed volumes during the
+scheduling process, enabling it to schedule your workloads based on the
+availability of volumes on a specific client.
+
+Nomad's host volumes come in two types - dynamic and static. Dynamic host volumes are, similar
+to CSI volumes, managed by Nomad with the help of [plugins][dhv_plugins]. The plugin creates the volumes
+and mounts them on the client, and Nomad makes the volumes available to the task group. Plugins follow a
+[specification][dhv_spec] that allows anyone to write a plugin for their storage needs.
+
+Static Host volumes allow you to mount any existing directory on the Nomad client into an allocation.
+These directories can be directories on a client, but can also be mounted networked or clustered
+filesystems like NFS, SeaweedFS or GlusterFS. Static host volumes are defined in the [client configuration][config_static_host_vol]
+file and are available to all tasks running on that client.
+
+The Docker task driver's support for [volumes][docker-volumes] enables Nomad to
+integrate with software-defined storage (SDS) solutions that have native support for Docker. Keep in mind that
+Nomad does not actually manage storage pools or replication as these tasks are
+delegated to the SDS providers. Please assess all factors and risks when
+utilizing such providers to run stateful workloads (such as your production
+database).
+
+For more information on the various options for stateful storage in Nomad, refer to the [Considerations for Stateful Workloads
+Workloads guide][considerations_stateful_workloads].
+
+In these guides, you will deploy a stateful application to a Nomad cluster and
+demonstrate that the data is persisted beyond the life of the allocation.
+
+
+[docker-volumes]: /nomad/docs/job-declare/task-driver/docker#volumes
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers]: https://kubernetes-csi.github.io/docs/drivers.html
+[aws elastic block storage]: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
+[azure disk]: https://github.com/kubernetes-sigs/azuredisk-csi-driver
+[gce persistent disk]: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver
+[alicloud disk]: https://github.com/AliyunContainerService/csi-plugin
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
+[dhv_plugins]: /nomad/docs/architecture/storage/host-volumes
+[config_static_host_vol]: /nomad/docs/configuration/client#host_volume-block
+[considerations_stateful_workloads]: /nomad/docs/architecture/storage/stateful-workloads
diff --git a/content/nomad/v1.10.x/content/docs/stateful-workloads/static-host-volumes.mdx b/content/nomad/v1.10.x/content/docs/stateful-workloads/static-host-volumes.mdx
new file mode 100644
index 0000000000..03a2f25a39
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/stateful-workloads/static-host-volumes.mdx
@@ -0,0 +1,389 @@
+---
+layout: docs
+page_title: Use static host volumes
+description: >-
+  Configure and deploy a host volume to support a MySQL workload that requires
+  persistent storage.
+---
+
+# Use static host volumes
+
+Static host volumes can manage storage for stateful workloads running inside your
+Nomad cluster. This tutorial walks you through deploying a MySQL workload using
+a static host volume for persistent storage. Unlike [dynamic host volumes][dhv_tutorial], static
+host volumes are defined in the Nomad client configuration and their lifecycle is
+managed outside of Nomad.
+
+Static host volumes provide a workload-agnostic way to specify resources,
+available for Nomad drivers like `exec`, `java`, and `docker`. Refer to the
+[`host_volume` specification][`host_volume`] for more information.
+Nomad is aware of host volumes during the scheduling process,
+which enables it to make scheduling decisions based on the availability of
+static host volumes on a specific client.
+
+This can be contrasted with Nomad support for Docker volumes. Because Docker
+volumes are managed outside of Nomad and the Nomad scheduler is not aware of
+them, Docker volumes have to either be deployed to all clients or operators have
+to use an additional, manually-maintained constraint to inform the scheduler
+where they are present.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. Consul is used for service discovery and is not necessary for
+static host volumes. You can use this [Terraform environment][nomad-tf] to provision a
+sandbox environment. This tutorial will assume a cluster with one server node and three
+client nodes.
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node. Please consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+### Install the MySQL client
+
+You will use the MySQL client to connect to our MySQL database and verify our data.
+Ensure it is installed on a node with access to port 3306 on your Nomad clients:
+
+Ubuntu:
+
+```shell-session
+$ sudo apt install mysql-client
+```
+
+CentOS:
+
+```shell-session
+$ sudo yum install mysql
+```
+
+macOS via Homebrew:
+
+```shell-session
+$ brew install mysql-client
+```
+
+## Build the static host volume
+
+### Create a target directory
+
+On a Nomad client node in your cluster, create a directory that will be used for
+persisting the MySQL data. For this example, let's create the directory
+`/opt/mysql/data`.
+
+```shell-session
+$ sudo mkdir -p /opt/mysql/data
+```
+
+You might need to change the owner on this folder if the Nomad client does not
+run as the `root` user.
+
+```shell-session
+$ sudo chown «Nomad user» /opt/mysql/data
+```
+
+### Configure the client
+
+Edit the Nomad configuration on this Nomad client to create the static host volume
+definition.
+
+Add a [`host_volume`] block to the `client` block of your Nomad configuration:
+
+```hcl
+  host_volume "mysql" {
+    path      = "/opt/mysql/data"
+    read_only = false
+  }
+```
+
+Save this change, and then restart the Nomad service on this client to make the
+static host volume active. While still on the client, you can verify that the host
+volume is configured by using the `nomad node status` command as shown below:
+
+```shell-session
+$ nomad node status -short -self
+ID           = 12937fa7
+Name         = ip-172-31-15-65
+Class        = <none>
+DC           = dc1
+Drain        = false
+Eligibility  = eligible
+Status       = ready
+Host Volumes = mysql
+Drivers      = docker,exec,java,mock_driver,raw_exec,rkt
+...
+```
+
+## Deploy MySQL
+
+### Create the job file
+
+You are now ready to deploy a MySQL database that can use the static host volumes for
+storage. Create a file called `mysql.nomad.hcl` and provide it the following
+contents:
+
+```hcl
+job "mysql-server" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mysql-server" {
+    count = 1
+
+    volume "mysql" {
+      type      = "host"
+      read_only = false
+      source    = "mysql"
+    }
+
+    restart {
+      attempts = 10
+      interval = "5m"
+      delay    = "25s"
+      mode     = "delay"
+    }
+
+    task "mysql-server" {
+      driver = "docker"
+
+      volume_mount {
+        volume      = "mysql"
+        destination = "/var/lib/mysql"
+        read_only   = false
+      }
+
+      env = {
+        "MYSQL_ROOT_PASSWORD" = "password"
+      }
+
+      config {
+        image = "hashicorp/mysql-portworx-demo:latest"
+
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500
+        memory = 1024
+      }
+
+      service {
+        name = "mysql-server"
+        port = "db"
+
+        check {
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+    network {
+      port "db" {
+        static = 3306
+      }
+    }
+  }
+}
+```
+
+#### Notes about the above job specification
+
+- The service name is `mysql-server` which you will use later to connect to the
+  database.
+
+- The `read_only` argument is supplied on all of the volume-related stanzas in
+  to help highlight all of the places you would need to change to make a
+  read-only volume mount. Please see the [`host_volume`], [`volume`], and
+  [`volume_mount`] specifications for more details.
+
+- For lower-memory instances, you might need to reduce the requested memory in
+  the resources stanza to harmonize with available resources in your cluster.
+
+### Run the job
+
+Register the job file you created in the previous step with the following
+command:
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "aa478d82"
+    Evaluation triggered by job "mysql-server"
+    Allocation "6c3b3703" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "aa478d82" finished with status "complete"
+```
+
+Check the status of the allocation and ensure the task is running:
+
+```shell-session
+$ nomad status mysql-server
+ID            = mysql-server
+...
+Summary
+Task Group    Queued  Starting  Running  Failed  Complete  Lost
+mysql-server  0       0         1        0       0         0
+```
+
+## Write data to MySQL
+
+### Connect to MySQL
+
+Using the mysql client (installed [earlier][install_mysql]), connect to the
+database and access the information:
+
+```shell-session
+$ mysql -h mysql-server.service.consul -u web -p -D itemcollection
+```
+
+The password for this demo database is `password`.
+
+<Note>
+
+ This tutorial is for demo purposes and does not follow best
+practices for securing database passwords. See [Keeping Passwords
+Secure][password-security] for more information.
+
+</Note>
+
+Consul is installed alongside Nomad in this cluster so you are able to
+connect using the `mysql-server` service name you registered with our task in
+our job file.
+
+### Add test data
+
+Once you are connected to the database, verify the table `items` exists:
+
+```sql
+mysql> show tables;
++--------------------------+
+| Tables_in_itemcollection |
++--------------------------+
+| items                    |
++--------------------------+
+1 row in set (0.00 sec)
+```
+
+Display the contents of this table with the following command:
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
++----+----------+
+3 rows in set (0.00 sec)
+```
+
+Now add some data to this table (after you terminate our database in Nomad and
+bring it back up, this data should still be intact):
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('glove');
+```
+
+Run the `INSERT INTO` command as many times as you like with different values.
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('hat');
+mysql> INSERT INTO items (name) VALUES ('keyboard');
+```
+
+Once you are done, type `exit` and return back to the Nomad client command
+line:
+
+```sql
+mysql> exit
+Bye
+```
+
+## Destroy the database job
+
+Run the following command to stop and purge the MySQL job from the cluster:
+
+```shell-session
+$ nomad stop -purge mysql-server
+==> Monitoring evaluation "6b784149"
+    Evaluation triggered by job "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6b784149" finished with status "complete"
+```
+
+Verify no jobs are running in the cluster:
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+In more advanced cases, the directory backing the static host volume could be a mounted
+network filesystem, like NFS, or cluster-aware filesystem, like GlusterFS or SeaweedFS. This
+can enable more complex, automatic failure-recovery scenarios in the event of a
+node failure.
+
+## Re-deploy and verify
+
+Using the `mysql.nomad.hcl` job file [from earlier][create_job], re-deploy the
+database to the Nomad cluster.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "61b4f648"
+    Evaluation triggered by job "mysql-server"
+    Allocation "8e1324d2" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61b4f648" finished with status "complete"
+```
+
+Once you re-connect to MySQL, you should be able to see that the information you
+added prior to destroying the database is still present:
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
+|  4 | glove    |
+|  5 | hat      |
+|  6 | keyboard |
++----+----------+
+6 rows in set (0.00 sec)
+```
+
+## Clean up
+
+Once you have completed this guide, you should perform the following cleanup steps:
+
+- Stop and purge the `mysql-server` job.
+
+- Remove the `host_volume "mysql"` stanza from your Nomad client configuration
+  and restart the Nomad service on that client
+
+- Remove the /opt/mysql/data folder and as much of the directory tree that you
+  no longer require.
+
+## Summary
+
+In this guide, you configured a static host volume on a Nomad client using a client-local
+directory. You created a job that mounted this volume to a Docker MySQL container
+and wrote data that persisted beyond the job's lifecycle.
+
+[`host_volume`]: /nomad/docs/configuration/client#host_volume-block
+[`volume_mount`]: /nomad/docs/job-specification/volume_mount
+[`volume`]: /nomad/docs/job-specification/volume
+[create_job]: #create-the-job-file
+[install_mysql]: #install-the-mysql-client
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[password-security]: https://dev.mysql.com/doc/refman/8.0/en/password-security.html
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture#high-availability
+[dhv_tutorial]: /nomad/docs/stateful-workloads/dynamic-host-volumes
+
diff --git a/content/nomad/v1.10.x/content/docs/upgrade/index.mdx b/content/nomad/v1.10.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..2314bd7fdb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Upgrade Nomad'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Upgrade HashiCorp Nomad without causing an outage. Review the upgrade process for a new version, for moving from Nomad community edition to Nomad Enterprise, and for Raft protocol version three.
+---
+
+# Upgrade Nomad
+
+This page provides guidance on upgrading HashiCorp Nomad without causing an
+outage. Review the upgrade process for a new version, for moving from Nomad
+Community to Nomad Enterprise, and for Raft protocol version three.
+
+## Introduction
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](//nomad/docs/deploy/clusters/federate-regions),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/docs/manage/migrate-workloads) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/commands/monitor
+[node-status]: /nomad/commands/node/status
+[server-members]: /nomad/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/docs/manage/outage-recovery#manual-recovery-using-peers-json)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/docs/manage/outage-recovery#manual-recovery-using-peers-json
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.10.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.10.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..66881586c4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1769 @@
+---
+layout: docs
+page_title: Nomad version-specific upgrade guides
+description: |-
+  Review upgrade details for specific versions of Nomad.
+---
+
+# Nomad version-specific upgrade guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.10.6
+
+#### ACL policies no longer silently ignore duplicate or invalid keys
+
+Nomad 1.10.6 introduces stricter validation for ACL policies. Policy writes that
+include duplicate or invalid keys will be rejected with an error instead of
+being silently ignored. Any existing policies with duplicate or invalid keys
+will continue to work, but the source policy document will need to be updated
+to be valid before it can be written to Nomad.
+
+#### Enterprise product usage reporting <EnterpriseAlert inline />
+
+Nomad Enterprise 1.10.6 adds detailed product usage information to
+[automated license utilization reporting](/nomad/docs/enterprise/license/utilization-reporting).
+
+## Nomad 1.10.2
+
+#### Clients respect `telemetry.publish_allocation_metrics`
+
+Nomad 1.10.2 fixed a bug where allocation metrics were collected and published
+even if the
+[`telemetry.publish_allocation_metrics`](/nomad/docs/configuration/telemetry#publish_allocation_metrics)
+configuration field was unset or set to `false`. If you are monitoring
+allocation metrics, you will need to ensure your Nomad clients set this field to
+`true`.
+
+## Nomad 1.10.1
+
+@include 'release-notes/v1-10-1/breaking-raft-peer.mdx'
+
+@include 'release-notes/v1-10-1/breaking-agent-exit.mdx'
+
+#### Added Server `start_timeout` Configuration Option
+
+Nomad 1.10.1 introduces a new server configuration option named `start_timeout`
+with a default value of `30s`. This duration is used to monitor the server setup
+and startup processes which must complete before it is considered healthy, such
+as keyring decryption. If these processes do not complete before the timeout is
+reached, the server process will exit and any errors logged to the console.
+
+#### Corrected `/v1/acl/token/self` response codes
+
+Nomad 1.10.1 responds with different HTTP response codes to API calls sent to
+`/v1/acl/token/self`. For users that do not have ACLs enabled, the endpoint
+responds with 200 code and a response body that indicates that ACLs are
+disabled. Previously, the response code in such a scenario was 404.
+
+For users that do have ACLs enabled and do not have a valid ACL token present,
+the endpoint responds with 403 code. Previously, the response code in such a
+scenario was 404.
+
+## Nomad 1.10.0
+
+@include 'release-notes/v1-10/deprecate-variable-limits.mdx'
+
+@include 'release-notes/v1-10/breaking-disconnect-fields-removed.mdx'
+
+@include 'release-notes/v1-10/breaking-go-sdk.mdx'
+
+@include 'release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx'
+
+@include 'release-notes/v1-10/breaking-plugin-dir.mdx'
+
+@include 'release-notes/v1-10/breaking-sentinel-apply.mdx'
+
+@include 'release-notes/v1-10/breaking-affinity-spread.mdx'
+
+@include 'release-notes/v1-10/breaking-vault-consul-token.mdx'
+
+## Nomad 1.9.9
+
+#### Added Server `start_timeout` Configuration Option
+
+Nomad 1.9.9 introduces a new server configuration option named `start_timeout`
+with a default value of `30s`. This duration is used to monitor the server setup
+and startup processes which must complete before it is considered healthy, such
+as keyring decryption. If these processes do not complete before the timeout is
+reached, the server process will exit and any errors logged to the console.
+
+## Nomad 1.9.5
+
+#### CNI plugins
+
+Nomad 1.9.5 includes a bug fix for restoring allocation networking after a
+client host reboot. This fix requires recent versions of the CNI reference
+plugins (minimum 1.2.0) and will fallback to the existing behavior if the CNI
+reference plugins cannot support the fix.
+
+We recommend installing the CNI reference plugins from the [CNI project release
+page](https://github.com/containernetworking/plugins/releases) rather than your
+Linux distribution's package manager.
+
+## Nomad 1.9.4
+
+#### Security updates to default deny lists
+
+In Nomad 1.9.4, the default `function_denylist` includes `executeTemplate`, as
+a measure to prevent accidental or malicious infinitely recursive execution.
+Users that require `executeTemplate` should update their
+[configuration](/nomad/docs/v1.9.x/job-specification/template#function_denylist).
+
+Additionally, the [default client env deny
+list](/nomad/docs/v1.9.x/configuration/client#env-denylist) includes more environment
+variables. Users who need some of these secure environment variables passed to
+their tasks should consult the list and overwrite it in the configuration.
+
+## Nomad 1.9.3
+
+In Nomad 1.9.3, the mechanism used for calculating when objects are eligible
+for garbage collection changes to a clock-based one. This has two consequences.
+First, it allows to set arbitrarily long GC intervals. Second, it requires that
+Nomad servers are kept roughly in sync time-wise, because GC can originate in a
+follower.
+
+Nomad 1.9.2 contained a bug that could drop all cluster state on upgrade and
+has been removed from downloads.
+
+## Nomad 1.9.0
+
+#### Dropped support for older clients
+
+Nomad 1.9.0 removes support for Nomad client agents older than 1.6.0. Older
+nodes fail heartbeats. Nomad servers mark the workloads on those nodes
+as lost and reschedule them normally according to the job's [reschedule][]
+block.
+
+#### Keyring In Raft
+
+Nomad 1.9.0 stores keys used for signing Workload Identity and encrypting
+Variables in Raft, instead of storing key material in the external
+keystore. When using external KMS or Vault transit encryption for the
+[`keyring`](/nomad/docs/v1.9.x/configuration/keyring) provider, the key encryption key
+(KEK) is stored outside of Nomad and no cleartext key material exists on disk.
+When using the default AEAD provider, the key encryption key (KEK) is stored in
+Raft alongside the encrypted data encryption keys (DEK).
+
+Nomad automatically migrates the key storage for all key material on the
+first [`root_key_gc_interval`](/nomad/docs/v1.9.x/configuration/server#root_key_gc_interval) after all servers are upgraded to 1.9.0. The
+existing on-disk keystore is required to restore servers from older snapshots,
+so you should continue to back up the on-disk keystore until you no longer need
+those older snapshots.
+
+#### Support for HCLv1 removed
+
+Nomad 1.9.0 no longer supports the HCLv1 format for job specifications. Using
+the `-hcl1` option for the `job run`, `job plan`, and `job validate` commands
+will no longer work.
+
+One common use of `-hcl1` was when specifying [Docker
+labels](/nomad/docs/v1.9.x/drivers/docker#labels) with dots in their keys such as for
+DataDog autodiscovery:
+
+```hcl
+labels {
+  "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+  "com.datadoghq.ad.init_configs" = "[{}]"
+  # ...
+}
+```
+
+Quoted keys are invalid in HCLv2 blocks and must be specified with a
+list-of-maps syntax:
+
+```hcl
+labels = [
+  {
+    "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+    "com.datadoghq.ad.init_configs" = "[{}]"
+    # ...
+  }
+]
+```
+
+## Nomad 1.8.18
+
+#### ACL policies no longer silently ignore duplicate or invalid keys
+
+Nomad 1.8.18 introduces stricter validation for ACL policies. Policy writes that
+include duplicate or invalid keys will be rejected with an error instead of
+being silently ignored. Any existing policies with duplicate or invalid keys
+will continue to work, but the source policy document will need to be updated
+to be valid before it can be written to Nomad.
+
+#### Enterprise product usage reporting <EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.18 adds detailed product usage information to
+[automated license utilization reporting](/nomad/docs/enterprise/license/utilization-reporting).
+
+## Nomad 1.8.4
+
+#### Default Docker `infra_image` changed
+
+Due to the deprecation of the third-party `gcr.io` registry, the default Docker
+[`infra_image`](/nomad/docs/v1.8.x/drivers/docker#infra_image) is now `registry.k8s.io/pause-<arch>:3.3`. If you do not
+override the default, clients using the `docker` driver will make outbound
+requests to the new registry.
+
+## Nomad 1.8.3
+
+#### Nomad keyring rotation
+
+In Nomad 1.8.3, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.8.2
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.8.2, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`. We made
+this change as a result of regressions introduced by mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.8.2 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment. We made this change as a result of regressions introduced by
+mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+## Nomad 1.8.1
+
+<EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.1 includes an updated version of the Sentinel library. Users
+that have built custom Sentinel plugins must recompile them using an SDK
+supporting Sentinel Plugin Protocol Version 3. Consult the Sentinel
+[SDK Compatibility Matrix](https://github.com/hashicorp/sentinel-sdk?tab=readme-ov-file#sdk-compatibility-matrix) for appropriate Sentinel SDK versions.
+
+## Nomad 1.8.0
+
+#### Deprecated Disconnect Fields
+
+Nomad 1.8.0 introduces a `disconnect` block meant to group all the configuration
+options related to disconnected client's and server's behavior, causing the
+deprecation of the fields `stop_after_client_disconnect`, `max_client_disconnect`
+and `prevent_reschedule_on_lost`. This block also introduces new options for
+allocations reconciliation if the client regains connectivity.
+
+#### CNI Constraints
+
+In Nomad 1.8.0, jobs with `bridge` networking will have constraints added during
+job submit that require CNI plugins to be present on the node. Nodes have
+fingerprinted the available CNI plugins starting in Nomad 1.5.0.
+
+If you are upgrading from Nomad 1.5.0 or later to 1.8.0 or later, there's
+nothing additional for you to do. It's not recommended to skip more than 2
+versions of Nomad. But if you upgrade from earlier than 1.5.0 to 1.8.0 or later,
+you will need to ensure that clients have been upgraded before submitting any
+jobs that use `bridge` networking.
+
+#### Removal of `raw_exec` option `no_cgroups`
+
+In Nomad 1.7.0 the `raw_exec` plugin option for `no_cgroups` became ineffective.
+Starting in Nomad 1.8.0 attempting to set the `no_cgroups` in `raw_exec` plugin
+configuration will result in an error when starting the agent.
+
+## Nomad 1.7.11
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.7.11, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.7.10
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.7.10, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.7.10 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.7.2
+
+Nomad 1.7.2 fixes a critical bug in CPU fingerprinting in Nomad 1.7.0 and
+1.7.1. You should not install Nomad 1.7.0 or 1.7.1 and instead install the
+latest Nomad 1.7.x version.
+
+## Nomad 1.7.0
+
+<Warning>
+
+Nomad 1.7.0 contains a critical bug in keyring replication. You should not
+install Nomad 1.7.0 and instead install the latest Nomad 1.7.x version.
+
+</Warning>
+
+#### Keyring Replication Failure After Leader Election
+
+Nomad 1.7.0 introduced new RSA keys to the keyring for use in signing workload
+identities. These keys were not correctly replicated from leader to
+followers. This results in all workload identity verification failing after a
+leader election.
+
+This bug was fixed in Nomad 1.7.1.
+
+#### Vault Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault token specific to the task.
+
+The existing workflow using a Vault token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`vault.policies`](/nomad/docs/v1.7.x/job-specification/vault#policies) field is also deprecated and will work
+only with the existing workflow. Instead, you should configure a suitable Vault
+role and use that.
+
+The following agent configuration fields are deprecated:
+- [`vault.allow_unauthenticated`](/nomad/docs/v1.7.x/configuration/vault#allow_unauthenticated) will be removed in Nomad 1.10. Tasks will use
+  the workload identity without the user supplying a Vault token.
+- [`vault.task_token_ttl`](/nomad/docs/v1.7.x/configuration/vault#task_token_ttl) will be removed in Nomad 1.10. With workload
+  identity, tasks will receive their TTL configuration from the Vault role.
+- [`vault.token`](/nomad/docs/v1.7.x/configuration/vault#token) will be removed in Nomad 1.10. Nomad agents will no longer
+  make requests to authenticated endpoints except with a task's workload
+  identity.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Vault to work with workload identity. Refer to [Migrating to Using Workload
+Identity with Vault](/nomad/docs/v1.7.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault) for more details.
+
+#### Consul Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a service's or task's [Workload
+Identity](/nomad/docs/v1.7.x/concepts/workload-identity) to authenticate to Consul and obtain a Consul token specific to the
+workload.
+
+The existing workflow using a Consul token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`consul.allow_unauthenticated`](/nomad/docs/v1.7.x/configuration/consul#allow_unauthenticated) agent configuration field
+will be removed in Nomad 1.10. Tasks will use the workload identity without the
+user supplying a Consul token.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Consul to work with workload identity. See [Migrating to Using Workload
+Identity with
+Consul](/nomad/docs/v1.7.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
+for more details.
+
+#### RS256 JWT Signing Algorithm Support
+
+Prior to Nomad 1.7, workload identity JWTs were signed with the `EdDSA`
+algorithm. While `EdDSA` has numerous advantages as a signing algorithm, most
+third parties that accept JWTs expect the `RS256` signing algorithm to be used.
+
+Therefore starting in Nomad 1.7 *new* signing keys will generate an RSA key and
+sign workload identities with the `RS256` signing algorithm.
+
+Before setting up third party authentication methods to use workload
+identities, it is recommended to run [`nomad operator root keyring
+rotate`](/nomad/commands/operator/root/keyring-rotate) to ensure you
+generate a new RSA key.
+
+To verify an RSA key is present you may check the [`/.well-known/jwks.json`
+endpoint](/nomad/api-docs/operator/keyring#list-active-public-keys) on any
+Nomad agent. If you see `"kty": "RSA"`, then an RSA key exists and you do not
+need to rotate keys.
+
+New Nomad clusters will use RSA by default and are not affected.
+
+#### CPU Fingerprinting Changes
+
+Starting in Nomad 1.7, Nomad clients improve the accuracy of detected CPU
+performance metrics. The fingerprinter now takes into account heterogeneous core
+types on applicable processors. In addition, Nomad will attempt to detect and
+use the base frequency of the processor rather than the turbo frequency when
+calculating the total available CPU bandwidth. The net result of these behaviors
+is that the calculated total CPU bandwidth available on a node may change when
+upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
+meets expectations before upgrading. The [cpu concepts][cpu] documentation
+contains guidance in understanding how Nomad detects CPU metrics.
+
+#### CPU EC2 Detection Changes
+
+Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
+performance data for every EC2 instance type. In 1.7 and later Nomad instead
+gathers this data by executing the `dmidecode` command. The `dmidecode` package
+must be installed manually on some Linux distributions before the Nomad agent
+is started.
+
+#### CPU Core Isolation
+
+Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`
+attribute will be restricted to using only the CPU cores assigned to them. In
+previous versions of Nomad these tasks could also make use of other non-reserved
+CPU cores. However this feature would cause severe performance problems for
+the Linux kernel as the number of tasks increased. Operators are encouraged
+to ensure tasks making use of the `cores` attribute are given sufficient CPU
+resources before upgrading.
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.7.0 changes the behavior of the [`distinct_hosts`](/nomad/docs/v1.7.x/job-specification/constraint#distinct_hosts) constraint such that
+namespaces are taken into account when choosing feasible clients for allocation
+placement. The previous, less-expected behavior would cause **any** job with the
+same name running on a client to cause that node to be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`](/nomad/docs/v1.7.x/job-specification/constraint#distinct_property)
+constraint over [`${node.pool}`](/nomad/docs/v1.7.x/runtime/interpolation#node-attributes).
+
+#### Loading Binaries from `plugin_dir` Without Configuration
+
+Starting with Nomad 1.7.0, loading plugins that are not referenced in the agent
+configuration file is deprecated. Future versions of Nomad will only load
+plugins that have a corresponding [`plugin`](/nomad/docs/v1.7.x/configuration/plugin)
+block in the agent configuration file.
+
+#### Changes to `raw_exec`
+
+The `raw_exec` task driver now enforces memory limits via cgroups on Linux
+platforms similar to the `exec` and `docker` task drivers. The driver does
+support memory [oversubscription](/nomad/docs/v1.7.x/job-specification/resources#memory-oversubscription), which can be configured in such a
+way to nearly replicate the previously unlimited behavior.
+
+The `no_cgroups` configuration option no longer has any effect. Previously,
+setting `no_cgroups` would disable the mechanism where Nomad used the freezer
+cgroup to halt the process group of a Task before issuing a kill signal to each
+process. Starting in Nomad 1.7.0 this behavior is always enabled (and a similar
+mechanism has always been enabled on cgroups v2 systems).
+
+## Nomad 1.6.14
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.6.14, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.6.13
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.6.13, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.6.13 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/v1.6.x/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration](/nomad/docs/v1.6.x/drivers/exec#allow_caps):
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task](/nomad/docs/v1.6.x/drivers/exec#cap_add) that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide](/nomad/docs/v1.5.x/install/production/requirements#hardening-nomad)
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation](/nomad/docs/v1.5.x/drivers/docker#enabled).
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock](https://docs.kernel.org/userspace-api/landlock.html) capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`](/nomad/docs/v1.5.x/job-specification/artifact#artifact-parameters)
+and `headers` fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`](/nomad/docs/v1.5.x/configuration/client#set_environment_variables).
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`](/nomad/docs/v1.5.x/configuration/client#disable_filesystem_isolation).
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`](/nomad/docs/v1.5.x/configuration/client#decompression_size_limit) and
+[`decompression_file_count_limit`]( /nomad/docs/v1.5.x/configuration/client#decompression_file_count_limit).
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/v1.5.x/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`](/nomad/docs/v1.5.x/configuration/server#rejoin_after_leave) configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/v1.5.x/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation](/nomad/docs/v1.4.x/drivers/docker#enabled).
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/v1.4.x/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process](/nomad/docs/v1.4.x/upgrade) closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`](/nomad/docs/v1.4.x/configuration/server#raft_protocol) version is explicitly set, it must now be set to `3`.
+For more information refer to the [Upgrading to Raft Protocol 3](/nomad/docs/v1.4.x/upgrade#upgrading-to-raft-protocol-3) guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly]( https://github.com/hashicorp/nomad/issues/10440).
+
+[Nomad 1.4.0 fixes this behavior](https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906) so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues](https://github.com/hashicorp/nomad/issues/new/choose).
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`](/nomad/docs/v1.3.x/job-specification/template#uid) and
+[`gid`](/nomad/docs/v1.3.x/job-specification/template#gid) in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`](/nomad/docs/v1.3.x/configuration/client#max_kill_timeout)
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`](/nomad/docs/v1.3.x/job-specification/task#kill_timeout)
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new `artifact` client configuration and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`](/nomad/docs/v1.3.x/configuration/server#raft_protocol) version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. Refer to the [Upgrading to Raft Protocol 3](/nomad/docs/v1.3.x/upgrade#upgrading-to-raft-protocol-3) guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/v1.3.x/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/v1.3.x/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as local tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with default anonymous ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in [Consul issue 7414](https://github.com/hashicorp/consul/issues/7414)
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html)
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default
+parent](/nomad/docs/v1.3.x/configuration/client#cgroup_parent) for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse](/nomad/api-docs/v1.2.x/jobs#parse-job) API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug](https://github.com/hashicorp/nomad/issues/11563) present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`](/nomad/docs/v1.1.x/configuration#log_file) configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands]( https://github.com/hashicorp/nomad/pull/10875).
+
+For users of [`api.Client`](https://pkg.go.dev/github.com/hashicorp/nomad/api#Client) who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`](/nomad/docs/v1.1.x/drivers/docker#extra_hosts) values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`](/nomad/docs/v1.1.x/job-specification/sidecar_task#config) block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment. Refer to the Enterprise licensing documentation for details.
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Visit the [Enterprise licensing page](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/v1.1.x/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`](/nomad/docs/v1.1.x/commands/volume/create) and [`volume register`](/nomad/docs/v1.1.x/commands/volume/register) commands.
+
+The [`volume`](/nomad/docs/v1.1.x/job-specification/volume) block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation](/nomad/docs/v1.1.x/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12) in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`]( https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`](/nomad/docs/v1.1.x/drivers/java#allow_caps) task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`](/nomad/docs/v1.1.x/drivers/exec#cap_add) and [`cap_drop`](/nomad/docs/v1.1.x/drivers/exec#cap_drop)
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the `CAP_NET_RAW` Linux capability is disabled
+by default. This is one of the Linux capabilities that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`](/nomad/docs/v1.1.0/drivers/docker#allow_caps) driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as PKI, or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`](https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency) is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/v1.0.x/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain](/nomad/docs/v1.0.x/commands/node/drain) and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain](/nomad/docs/v1.0.x/upgrade#5-upgrade-clients) at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`](https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency) argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`](/nomad/docs/v1.0.x/job-specification/sidecar_task#proxy_concurrency) property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`](/nomad/docs/v0.12.x/configuration/client#template-parameters) field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/9148) in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v0.12.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/8457) in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/v0.12.x/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/v0.12.x/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/v0.11.x/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/9148) in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources](/nomad/docs/v0.11.x/configuration/client#reserved-parameters)
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time](/nomad/docs/v0.11.x/job-specification/periodic#daylight-saving-time) documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`](/nomad/docs/v0.11.x/job-specification/template) option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in the [external `nomad-driver-rkt` repository](https://github.com/hashicorp/nomad-driver-rk), it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10 and earlier
+
+Refer to the [Nomad releases page](https://github.com/hashicorp/nomad/releases) in the Nomad repo for prior release changelogs.
diff --git a/content/nomad/v1.10.x/content/docs/use-cases.mdx b/content/nomad/v1.10.x/content/docs/use-cases.mdx
new file mode 100644
index 0000000000..09f24a6983
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/use-cases.mdx
@@ -0,0 +1,174 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  Learn about Nomad's core use cases, such as Docker container orchestration, legacy application deployment, microservices, batch processing workloads, and multi-cloud federated deployemnts.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker container orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/job-declare/task-driver/docker)
+and integrates seamlessly with [Consul](/nomad/docs/networking/consul)
+and [Vault](/nomad/docs/secure/vault) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy application deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/networking/consul)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch processing workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and multi-cloud federated deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
+
+Nomad now enables [Proof Key for Code Exchange
+(PKCE)](https://oauth.net/2/pkce/) by default for new or updated OIDC auth
+methods.
+
+## Company-specific use cases
+
+This section features talks from companies on how they use Nomad to solve critical, real-world business objectives.
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
diff --git a/content/nomad/v1.10.x/content/docs/what-is-nomad.mdx b/content/nomad/v1.10.x/content/docs/what-is-nomad.mdx
new file mode 100644
index 0000000000..a60774c8d1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/docs/what-is-nomad.mdx
@@ -0,0 +1,198 @@
+---
+layout: intro
+page_title: What is Nomad?
+description: >-
+  Learn what Nomad is, what problems it can solve, its key features, and how it
+  compares to Kubernetes and AWS ECS.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<VideoEmbed url="https://www.youtube.com/embed/s_Fm9UtL4YU"/>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/job-declare/task-driver).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/plugins/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad compares to other tools
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external
+  dependencies. Operators can easily provision, manage, and scale Nomad.
+  Developers can easily define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of
+  containers per second, scale to thousands of nodes in a single cluster, and
+  easily federate across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for
+  secrets management and Consul for service discovery and dynamic configuration.
+  Nomad's Consul-like architecture and Terraform-like job specification lower
+  the barrier to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire
+space.
+
+## Nomad versus Kubernetes
+
+Kubernetes and Nomad support similar core use cases for application deployment
+and management, but they differ in a few key ways. Kubernetes aims to provide
+all the features needed to run Linux container-based applications including
+cluster management, scheduling, service discovery, monitoring, and secrets
+management. Nomad only aims to focus on cluster management and scheduling, and
+Nomad is designed with the Unix philosophy of having a small scope while
+composing with tools like Consul for service discovery/service mesh and Vault
+for secret management.
+
+<VideoEmbed url="https://www.youtube.com/embed/ZfSuted4pcA?si=IyqGzqOAnYO06398"/>
+
+### Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+### Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+### Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+### Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
+
+### Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+- High budget and full-time staffing to maintain Kubernetes
+- High-profile projects with significant investment and long-term timeline (multi-year)
+- Deploying and managing new, cloud-native applications
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+- Deploying and managing core, existing applications
+- On-premises environment, or hybrid environments
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single
+orchestrator given the natural staffing and organizational constraints. There
+are not enough DevOps members to maintain more than one orchestrator, not enough
+developers to warrant diverging workflows, or simply not enough workload
+diversity to require more than one orchestrator.
+
+### Resources
+
+Review the following resources for in-depth comparisons between Nomad and
+Kubernetes:
+
+- [A Kubernetes User's Guide to HashiCorp
+  Nomad](https://www.hashicorp.com/en/blog/a-kubernetes-user-s-guide-to-hashicorp-nomad)
+- [The Kubernetes to Nomad Cheat
+  Sheet](https://www.hashicorp.com/en/blog/the-kubernetes-to-nomad-cheat-sheet)
+- [A Kubernetes User's Guide to HashiCorp Nomad Secret Management](https://www.hashicorp.com/en/blog/a-kubernetes-user-s-guide-to-hashicorp-nomad-secret-management)
+
+## Nomad versus AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
+
+## Nomad versus Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and
+versioning infrastructure safely and efficiently. Configuration files describe
+to Terraform the components needed to run a single application or your entire
+datacenter. Terraform generates an execution plan describing what it will do to
+reach the desired state, and then executes it to build the described
+infrastructure. As the configuration changes, Terraform is able to determine
+what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to
+support any type of resource including low-level components such as compute
+instances, storage, and networking, as well as high-level components such as DNS
+entries, SaaS features, etc. Terraform knows how to create, provision, and
+manage the lifecycle of these resources. Nomad runs on existing infrastructure
+and manages the lifecycle of applications running on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to
+completion, while Nomad is an online system with long lived servers. Nomad
+allows new jobs to be submitted, existing jobs updated or deleted, and can
+handle node failures. This requires operating continuously instead of in a
+single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the
+complexity of Nomad may not outweigh simply using Terraform to statically assign
+applications to machines. At larger scales, Terraform should be used to
+provision capacity for Nomad, and Nomad used to manage scheduling applications
+to machines dynamically.
+
+## Next steps
+
+Review [use cases](/nomad/docs/use-cases) to understand the many ways
+Nomad is used in production today across many industries to solve critical,
+real-world business objectives.
diff --git a/content/nomad/v1.10.x/content/intro/README.md b/content/nomad/v1.10.x/content/intro/README.md
new file mode 100644
index 0000000000..0842885fc5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/intro/README.md
@@ -0,0 +1 @@
+delete this file and directory after publication
diff --git a/content/nomad/v1.10.x/content/intro/index.mdx b/content/nomad/v1.10.x/content/intro/index.mdx
new file mode 100644
index 0000000000..17530be7c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/intro/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: intro
+page_title: Introduction to Nomad
+description: >-
+  Learn what Nomad is, what problems it can solve, its key features, and how it
+  compares to existing software.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameBorder="0"
+  allowFullScreen={true}
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/ddeploy/task-driver).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/plugins/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad compares to other tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+## Next steps
+
+Review the [Use Cases](/nomad/docs/use-cases) page to understand the many ways
+Nomad is used in production today across many industries to solve critical,
+real-world business objectives.
diff --git a/content/nomad/v1.10.x/content/partials/api-docs/auth-method-params.mdx b/content/nomad/v1.10.x/content/partials/api-docs/auth-method-params.mdx
new file mode 100644
index 0000000000..4fa934ce4d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/api-docs/auth-method-params.mdx
@@ -0,0 +1,162 @@
+<!--
+parameters for create/update auth method APIs
+used in website/content/api-docs/acl/auth-methods.mdx
+-->
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+The name can contain alphanumeric characters and dashes. This name must be
+unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and
+`JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+creates a local or global token when performing SSO login. This field must be
+set to either `local` or `global`.
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for
+the generated tokens This can be lightly templated using HIL `${foo}` syntax.
+Defaults to `${auth_method_type}-${auth_method_name}`.
+
+ - `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token
+created by this method. When set, it will initialize the `ExpirationTime` field
+on all tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This
+field is not persisted beyond its initial use. Can be specified in the form of
+`"60s"` or `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use
+for the auth method.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+  any `.well-known` component (base path). Required for `OIDC` method type.
+  Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+  `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+  your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+  configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientAssertion` `(OIDCClientAssertion)` - Optionally send a signed
+  JWT ("[private key jwt][]") as a client assertion to the OIDC provider.
+  Browse to the [OIDC concepts][concepts-assertions] page to learn more.
+
+    - `Audience` `(array<string>)` - Who processes the assertion.
+    Defaults to the parent `ACLAuthMethodConfig`'s `OIDCDiscoveryURL`
+
+    - `KeySource` `(string: <required>)` - Specifies where to get the private
+    key to sign the JWT.
+    Available sources:
+      - "nomad": Use current active key in Nomad's keyring
+      - "private_key": Use key material in the `PrivateKey` field
+      - "client_secret": Use the `OIDCClientSecret` inherited from the parent
+      `ACLAuthMethodConfig` as an HMAC key
+
+    - `KeyAlgorithm` `(string)` is the key's algorithm. Its default values are
+    based on the `KeySource`:
+      - "nomad": "RS256"; this is from Nomad's keyring and must not be changed
+      - "private_key": "RS256"; must be RS256, RS384, or RS512
+      - "client_secret": "HS256"; must be HS256, HS384, or HS512
+
+    - `PrivateKey` `(OIDCClientAssertionKey)` - External key material to sign
+    the JWT. `KeySource` must be "private_key" to enable this.
+
+      - `PemKey` `(string)` - An RSA private key, in pem format. It is used to
+      sign the JWT. Mutually exclusive with `PemKeyFile`.
+
+      - `PemKeyFile` `(string)` - An absolute path to a private key on Nomad
+      servers' disk, in pem format. It is used to sign the JWT.
+      Mutually exclusive with `PemKey`.
+
+      - `KeyIDHeader` `(string)` - Which header the provider uses to find
+      the public key to verify the signed JWT.
+      The default and allowed values depend on whether you set `KeyID`,
+      `PemCert`, or `PemCertFile`. You must set exactly one of those options,
+      so refer to them for their requirements.
+
+      - `KeyID` `(string)` - Becomes the JWT's "kid" header.
+      Mutually exclusive with `PemCert` and `PemCertFile`.
+      Allowed `KeyIDHeader` values: "kid" (the default)
+
+      - `PemCert` `(string)` - An x509 certificate, signed by the private key
+      or a CA, in pem format. Nomad uses this certificate to derive an
+      [x5t#S256][] (or [x5t][]) KeyID.
+      Mutually exclusive with `PemCertFile` and `KeyID`.
+      Allowed `KeyIDHeader` values: "x5t", "x5t#S256" (default "x5t#S256")
+
+      - `PemCertFile` `(string)` - An absolute path to an x509 certificate on
+      Nomad servers' disk, signed by the private key or a CA, in pem format.
+      Nomad uses this certificate to derive an [x5t#S256][] (or [x5t][])
+      header. Mutually exclusive with `PemCert` and KeyID.
+      Allowed `KeyIDHeader` values: "x5t", "x5t#S256" (default "x5t#S256")
+
+    - `ExtraHeaders` `(map[string]string)` - Added to the JWT headers,
+    alongside "kid" and "type". Setting the "kid" header here is not allowed;
+    use `PrivateKey.KeyID`.
+
+  - `OIDCEnablePKCE` `(bool: false)` - When set to `true`, Nomad will include
+  [PKCE][] verification in the auth flow. Even with PKCE enabled in Nomad,
+  you may still need to enable it in your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not
+  make a request to the identity provider to get OIDC UserInfo. You may wish to
+  set this if your identity provider doesn't send any additional claims from the
+  UserInfo endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+  to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+  `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+  signatures. Either this, the `JWTValidationPubKeys` or the
+  `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+  login; any match is sufficient.
+
+  - `BoundIssuer` `(array<string>)` - The value against which to match the iss
+  claim in a JWT.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+  redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+  client used to talk with the OIDC discovery URL. If not set, system
+  certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+  to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+  Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+  validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+  validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+  validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+  be copied to a metadata field (value). Use this if the claim you are capturing
+  is singular (such as an attribute).
+
+  When mapped, the values in each list can be any of a number, string, or
+  boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+  copied to a metadata field (value). Use this if the claim you are capturing is
+  list-like (such as groups).
+
+  - `VerboseLogging` `(bool: false)` - When set to `true`, Nomad will log token
+  claims, information related to binding-rule and role/policy evaluations,
+  and client assertion JWTs, if applicable. Not recommended in production,
+  since sensitive information may be present.
diff --git a/content/nomad/v1.10.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.10.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.10.x/content/partials/consul-namespaces.mdx b/content/nomad/v1.10.x/content/partials/consul-namespaces.mdx
new file mode 100644
index 0000000000..10df413723
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/consul-namespaces.mdx
@@ -0,0 +1,44 @@
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for
+service registrations specified in `service` blocks and Consul KV reads in
+`template` blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations
+or KV store reads, which Consul then implicitly resolves to the `"default"`
+namespace.  This default namespace behavior can be modified by setting the
+[`namespace`][consul_agent_namespace] field in the Nomad agent Consul
+configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring
+the Consul [namespace][consul_jobspec_namespace] at the group or task level in
+the Nomad job spec as well as the [`-consul-namespace`][consul_run_namespace]
+command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations
+within a group, as well as `template` KV store access is determined from the
+following hierarchy from highest to lowest precedence:
+
+* group and task configuration: Consul
+  [namespace field][consul_jobspec_namespace] defined in the job at the task or
+  group level.
+
+* job run command option: Consul namespace defined in the
+  [`-consul-namespace`][consul_run_namespace] command line option on job
+  submission.
+
+* job run command environment various: Consul namespace defined as the
+  [`CONSUL_NAMESPACE`][consul_env_namespace] environment variable on job
+  submission.
+
+* agent configuration: Consul namespace defined in the
+  [`namespace`][consul_agent_namespace] Nomad agent Consul configuration
+  parameter.
+
+* Consul default: If no Consul namespace options are configured, Consul will
+  automatically make use of the `"default"` namespace.
+
+
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_jobspec_namespace]: /nomad/docs/job-specification/consul#namespace
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_run_namespace]: /nomad/commands/job/run#consul-namespace
+[consul_env_namespace]: /consul/commands#consul_namespace
diff --git a/content/nomad/v1.10.x/content/partials/envvars.mdx b/content/nomad/v1.10.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..c50025ad25
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/envvars.mdx
@@ -0,0 +1,77 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                              |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                          |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                                    |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                            |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                         |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                                |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                                  |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                                   |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index.          |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                              |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                             |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                            |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                               |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                                     |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                            |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                              |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                             |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                                |
+| `NOMAD_UNIX_ADDR`        | Use this value as your `NOMAD_ADDR` to use `nomad` CLI with the [task API][]'s unix socket. The value is equivalent to `"unix://${NOMAD_SECRETS_DIR}/api.sock"`
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/reference/runtime-variable-interpolation#node-variables-) which are keys in the node's metadata. |
+| `CONSUL_HTTP_TOKEN`      | The tasks' Consul token. See [Consul Integration][consul] documentation for more details.                                                                                                                                                                                                |
+| `CONSUL_TOKEN`           | The tasks' Consul token. See [Consul Integration][consul] documentation for more details. This variable is deprecated and exists only for backwards compatibility.                                                                                                                       |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                                |
+
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_INTERFACE_<label>`    | The configured network namespace interface for the given port `label` when using bridged or CNI networking.                                                                                                                                             |
+| `NOMAD_ALLOC_IP_<label>`           | The configured network namespace IP for the given port `label` when using bridged or CNI networking.                                                                                                                                                    |
+| `NOMAD_ALLOC_ADDR_<label>`         | The configured network namespace `IP:Port` pair for the given port `label` when using bridged or CNI networking.                                                                                                                                        |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[task API]: /nomad/api-docs/task-api
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/reference/runtime-environment-settings#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/secure/vault
+[consul]: /nomad/docs/networking/consul
diff --git a/content/nomad/v1.10.x/content/partials/general_options.mdx b/content/nomad/v1.10.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.10.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.10.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.10.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.10.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.10.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.10.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..c4c0d45199
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/deploy/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.10.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.10.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..cf133a47b2
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,27 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.6.2
+release](https://github.com/containernetworking/plugins/releases/tag/v1.6.2),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.6.2
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Your Linux distribution's package manager may provide the CNI reference plugins
+but we recommend installing the most recent stable version to ensure you have
+fixes for known bugs shipping in those versions.
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.10.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.10.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.10.x/content/partials/install/manual-install.mdx b/content/nomad/v1.10.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.10.x/content/partials/job-status-map.mdx b/content/nomad/v1.10.x/content/partials/job-status-map.mdx
new file mode 100644
index 0000000000..16322a24f3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/job-status-map.mdx
@@ -0,0 +1,17 @@
+Nomad uses one of these values to describe a job's status:
+
+- `dead`
+- `running`
+
+The CLI returns these rigid statuses, which are useful for scheduling and
+garbage collection. However, the Nomad UI displays additional human-readable
+statuses to help you manage jobs.
+
+The following table maps the CLI statuses to the statuses that appear in the
+Nomad UI.
+
+| CLI status       | UI status |
+| ---------------- | --------- |
+| `dead`           | `Complete`, `Failed`, `Scaled Down` |
+| `dead (stopped)` | `Stopped` |
+| `running`        | `Degraded`, `Deploying`, `Healthy`, `Recovering`, `Running`, `Scaled Down` |
diff --git a/content/nomad/v1.10.x/content/partials/jwt_claim_mapping_details.mdx b/content/nomad/v1.10.x/content/partials/jwt_claim_mapping_details.mdx
new file mode 100644
index 0000000000..84ee135609
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/jwt_claim_mapping_details.mdx
@@ -0,0 +1,80 @@
+## Trusted Identity Attributes via Claim Mappings
+
+The authentication step can return data from JWT claims as trusted
+identity attributes for use in binding rule selectors and bind name
+interpolation.
+
+The `ClaimMappings` and `ListClaimMappings` attributes control how Nomad maps claims
+to identity attributes. Both are maps of items to copy,
+with elements of the form `"<JWT claim>":"<attribute suffix>"`.
+
+Use `ClaimMappings` to map singular values and `ListClaimMappings` to map lists of values.
+
+This examples contains `ClaimMappings` and `ListClaimMappings`. The configuration
+instructs Nomad to copy the values in the JWT claims `"givenName"` and `"surname"`
+to attributes named `"value.first_name"` and `"value.last_name"` respectively.
+Additionally, Nomad should copy the list of values in the JWT
+claim `"groups"`  to an attribute named `"list.roles"`.
+
+```json
+{
+  "Name": "example-auth-method",
+  "Type": "<jwt|oidc>",
+  "Description": "Example auth method",
+  "Config": {
+    "ClaimMappings": {
+      "givenName": "first_name",
+      "surname": "last_name"
+    },
+    "ListClaimMappings": {
+      "groups": "roles"
+    }
+  }
+}
+```
+
+The following table shows the resulting attributes and
+the ways they may be used in rule bindings:
+
+| Attributes         | Supported selector operations                      | Can be interpolated |
+| ------------------ | -------------------------------------------------- | ------------------- |
+| `value.first_name` | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `value.last_name`  | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `list.groups`      | In, Not In, Is Empty, Is Not Empty                 | no                  |
+
+Refer to the [binding-rule] documentation for more examples on using selectors.
+
+### Claim Specifications and JSON Pointer
+
+Use the `ClaimMappings` and `ListClaimMappings` fields to point to data
+within the JWT. If the desired key is at the top of level of the JWT, you may
+provide the name directly. If it is nested at a lower level, you may use a JSON
+Pointer.
+
+This example shows decoded JWT claims.
+
+```json
+{
+  "division": "North America",
+  "groups": {
+    "primary": "Engineering",
+    "secondary": "Software"
+  },
+  "iss": "https://my-corp-app-name.auth0.com/",
+  "sub": "auth0|eiw7OWoh5ieSh7ieyahC3ief0uyuraphaengae9d",
+  "aud": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "iat": 1589224148,
+  "exp": 1589260148,
+  "nonce": "eKiihooH3Fah8Ieshah4leeti6ien3"
+}
+```
+
+Use the following syntax to reference data:
+
+- Top-level key: Use direct reference. For example, `"division"` refers to `"North America"`.
+- Nested key: Use JSON Pointer syntax. For example, `"/groups/primary"` refers to `"Engineering"`.
+
+You may use any valid JSON Pointer as a selector. Refer to the [JSON Pointer
+RFC](https://tools.ietf.org/html/rfc6901) for a full description of the syntax.
+
+[binding-rule]: /nomad/commands/acl/binding-rule/create#examples
diff --git a/content/nomad/v1.10.x/content/partials/node-pools.mdx b/content/nomad/v1.10.x/content/partials/node-pools.mdx
new file mode 100644
index 0000000000..a9812af045
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/node-pools.mdx
@@ -0,0 +1,373 @@
+Use node pools to group clients and segment infrastructure into logical units so
+that jobs control allocation placement. Review node pool replication in
+multi-region clusters, built-in node pools, node pool patterns, and enterprise
+features such as scheduler configuration, node pool governance, and multi-region
+jobs.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+Create a node pool using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config` block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/commands/node-pool/apply
+[cli_agent_np]: /nomad/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.10.x/content/partials/plugins/base.mdx b/content/nomad/v1.10.x/content/partials/plugins/base.mdx
new file mode 100644
index 0000000000..48314bcd08
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/plugins/base.mdx
@@ -0,0 +1,35 @@
+### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first,
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration,
+which is given to all plugins.
+
+### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.10.x/content/partials/plugins/hcl-specifications.mdx b/content/nomad/v1.10.x/content/partials/plugins/hcl-specifications.mdx
new file mode 100644
index 0000000000..cc672c20ce
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/plugins/hcl-specifications.mdx
@@ -0,0 +1,32 @@
+## HCL specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. Find the full documentation of the different HCL attribute types in the [hclspec godoc][hclspec].
+
+For a basic example, review the driver configuration for the raw_exec
+driver.
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. The
+`command` key takes a string attribute, and the `args` key takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx
new file mode 100644
index 0000000000..24338c0cda
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx
@@ -0,0 +1,7 @@
+#### Agent exit on reloading configuration errors
+
+Errors encountered when reloading agent configuration now cause agents to exit.
+In prior versions, Nomad only logged configuration errors during reloads. This
+could lead to agents running but unable to communicate. Any other errors when
+parsing the new configuration are logged and the reload is aborted, consistent
+with the current behavior.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx
new file mode 100644
index 0000000000..ea3533dae5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx
@@ -0,0 +1,8 @@
+
+#### Remove Raft peer by address removed
+
+Nomad 1.4.0 removed support for Raft Protocol v2, and this removed the ability
+to remove Raft peers by address instead of peer ID. Nomad 1.10.1 removes the
+non-functional `-peer-address` option for the [`operator raft
+peer-remove`](/nomad/commands/operator/raft/remove-peer) command, and the
+`address` parameter for the `DELETE /v1/operator/raft/peer` API.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx
new file mode 100644
index 0000000000..a8e3851ccb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx
@@ -0,0 +1,8 @@
+#### Affinity and spread updates are non-destructive
+
+We fixed a scheduler bug so that updates to `affinity` and
+`spread` blocks are no longer destructive. After a job update that changes only
+these blocks, existing allocations remain running with their job version
+incremented. If you were relying on the previous behavior to redistribute
+workloads, you can force a destructive update by changing fields that require
+one, such as the `meta` block.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx
new file mode 100644
index 0000000000..166027bc65
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx
@@ -0,0 +1,6 @@
+#### Consul template implicit workload identity removal
+
+Nomad no longer creates an implicit Consul identity for workloads that don't
+register services with Consul. Tasks that require Consul tokens for template
+rendering must include a [`consul` block](/nomad/docs/job-specification/consul)
+or specify an [`identity`](/nomad/docs/job-specification/identity#identity-block).
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx
new file mode 100644
index 0000000000..e49266d5c8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx
@@ -0,0 +1,7 @@
+#### Nomad 1.8 deprecated `disconnect` fields removed
+
+In Nomad 1.8, we introduced the `disconnect` block to replace the
+`max_client_disconnect`, `stop_after_client_disconnect`, and
+`prevent_reschedule_on_list` fields. In Nomad 1.10, we removed these fields, and
+Nomad will ignore them if specified. Jobs should migrate to using the
+[`disconnect` block](/nomad/docs/job-specification/disconnect) prior to upgrading.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx
new file mode 100644
index 0000000000..a1ebfaa321
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx
@@ -0,0 +1,6 @@
+#### Go SDK API change for quota limits
+
+In Nomad 1.10.0, the Go API for quotas has a breaking change. The
+`QuotaSpec.RegionLimit` field is now of type `QuotaResources` instead of
+`Resources`. The `QuotaSpec.VariablesLimit` field is deprecated in lieu of
+`QuotaSpec.RegionLimit.Storage.Variables` and will be removed in Nomad 1.12.0.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx
new file mode 100644
index 0000000000..416ad303f3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx
@@ -0,0 +1,6 @@
+#### Loading binaries from `plugin_dir` without configuration
+
+Plugins stored within the [`plugin_dir`](/nomad/docs/configuration#plugin_dir)
+will now only be loaded when they have a corresponding
+[`plugin`](/nomad/docs/configuration/plugin) block in the agent configuration
+file. Nomad now skips any plugin found without a corresponding configuration block.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx
new file mode 100644
index 0000000000..8b83a24b80
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx
@@ -0,0 +1,7 @@
+#### Remote task driver support removed
+
+In Nomad 1.10.0, we removed all support for remote task driver
+capabilities. Nomad no longer detaches drivers with the `RemoteTasks` capability
+when an allocation is lost. Also, Nomad does not detach remote tasks
+when a node is drained. Workloads running as remote tasks should be migrated
+prior to upgrading.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx
new file mode 100644
index 0000000000..14b35f01ee
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx
@@ -0,0 +1,5 @@
+#### Sentinel apply command requires scope <EnterpriseAlert product="nomad" inline/>
+
+To prevent accidentally adding policies for volumes to the job scope, the [`nomad sentinel apply` command](/nomad/commands/sentinel/apply) now
+requires the `-scope` option.  Refer to the [GitHub pull
+request](https://github.com/hashicorp/nomad/pull/24601) for details.
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx
new file mode 100644
index 0000000000..0a6abd4a87
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx
@@ -0,0 +1,25 @@
+#### Vault and Consul integration changes
+
+Nomad 1.10.0 removes the previously deprecated token-based authentication
+workflow for Vault and Consul. Nomad clients must now use a task's [workload
+identity](/nomad/docs/concepts/workload-identity) to authenticate to Vault and
+Consul and obtain a token specific to the task.
+
+This table lists removed Vault fields and the new workflow.
+
+| Field | Configuration | New Workflow |
+| ------ | ------------ | ------------ |
+| [`vault.allow_unauthenticated`](/nomad/docs/v1.9.x/configuration/vault#allow_unauthenticated) | Agent | Tasks should use a workload identity. Do not use a Vault token. |
+| [`vault.task_token_ttl`]( /nomad/docs/v1.9.x/configuration/vault#task_token_ttl) | Agent | With workload identity, tasks receive their TTL configuration from the Vault role. |
+| [`vault.token`](/nomad/docs/v1.9.x/configuration/vault#token) | Agent | Nomad agents use the workload identity when making requests to authenticated endpoints. |
+| [`vault.policies`](/nomad/docs/v1.9.x/job-specification/vault#policies) | Job specification  |  Configure and use a Vault role.  |
+
+Before upgrading to Nomad 1.10, perform the following tasks:
+
+1. Configure Vault and Consul to work with workload identity.
+1. Migrate all workloads to use workload identity.
+
+Refer to the following guides for more information:
+
+- [Migrating to using workload identity with Vault](/nomad/docs/v1.9.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault)
+- [Migrating to using workload identity with Consul](/nomad/docs/v1.9.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
diff --git a/content/nomad/v1.10.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx
new file mode 100644
index 0000000000..4f4abcff9f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx
@@ -0,0 +1,7 @@
+#### Quota specification variable_limits deprecated <EnterpriseAlert product="nomad" inline/>
+
+The quota specification's `variable_limits` field is deprecated. We replaced it
+with a new [`storage` block](/nomad/docs/other-specifications/quota#storage)
+with a `variables` field, under the `region_limit` block. Existing quotas will
+be automatically migrated during server upgrade. We will remove the
+`variables_limit` field from the quota specification in Nomad 1.12.0.
diff --git a/content/nomad/v1.10.x/content/partials/service-discovery.mdx b/content/nomad/v1.10.x/content/partials/service-discovery.mdx
new file mode 100644
index 0000000000..4832a1123a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/service-discovery.mdx
@@ -0,0 +1,140 @@
+
+This page provides information about Nomad service discovery. Compare Nomad's built-in service discovery feature to using Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+
+## Introduction
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/job-declare/consul-service-mesh
diff --git a/content/nomad/v1.10.x/content/partials/storage/host-volume-explanation.mdx b/content/nomad/v1.10.x/content/partials/storage/host-volume-explanation.mdx
new file mode 100644
index 0000000000..4576907f4c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/storage/host-volume-explanation.mdx
@@ -0,0 +1,39 @@
+Host volumes mount paths from the Nomad client into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+if it is backed by a distributed networked storage such as GlusterFS, or if it is a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore,
+you can use host volumes for both local semi-persistent storage and for
+highly persistent networked storage. Host volumes may be _dynamic_ or _static_.
+
+Host volumes backed by local storage help persist data that is neither critical nor
+readily restorable. Examples include an on-disk cache that can be rebuilt, or a
+clustered application where a single node can rebuild its state from the rest of
+the cluster. When backed by networked storage such as NFS/CIFS-mounted volumes
+or distributed storage with GlusterFS or Ceph, host volumes provide a quick
+option to consume highly available and reliable storage.
+
+#### Dynamic host volumes
+
+Provision dynamic host volumes
+with the [`volume create`](/nomad/commands/volume/create) command or
+API. [ACL policies](/nomad/docs/other-specifications/acl-policy#namespace-rules)
+allow delegation of control for storage within a namespace to Nomad
+Operators. The [dynamic host volume plugin
+specification](/nomad/plugins/author/host-volume) allows you to
+develop plugins specific to your local storage environment. For example, in an
+on-prem cluster you could write a plugin to perform LVM thin-provisioning.
+
+#### Static host volumes
+
+Declare static host volumes in the Nomad agent's configuration file. You
+must restart the Nomad client to reconfigure them. These restarts make static host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/architecture/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add, update, and remove host volumes to make them
+available for consumption by Nomad Operators. Or, with networked host volumes, a
+Storage Administrator needs to provision the volumes and makes them available to
+the Nomad clients. A System Administrator then mounts them on the Nomad clients.
diff --git a/content/nomad/v1.10.x/content/partials/task-driver-intro.mdx b/content/nomad/v1.10.x/content/partials/task-driver-intro.mdx
new file mode 100644
index 0000000000..a79e1ad080
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/task-driver-intro.mdx
@@ -0,0 +1,14 @@
+## Introduction
+
+Nomad clients use task drivers to execute a task and provide resource isolation.
+Extensible task drivers provide Nomad the flexibility to support a broad
+set of workloads across all major operating systems.
+
+Task driver resource isolation provides a degree of separation for Nomad's
+client CPU, memory, and storage between tasks. Resource isolation effectiveness
+depends upon individual task driver implementations and underlying client
+operating systems. Task drivers include various security-related controls but do
+not use the Nomad client-to-task interface as a security boundary. Refer to the
+[access control guide](/nomad/docs/secure/acl) for more information on
+how to protect Nomad cluster operations.
+
diff --git a/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-approval.mdx b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-approval.mdx
new file mode 100644
index 0000000000..2654bbfd80
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-approval.mdx
@@ -0,0 +1,4 @@
+### Approval options
+
+- `-auto-approve`: Automatically answer confirmation prompts in the
+  affirmative.
diff --git a/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx
new file mode 100644
index 0000000000..f6e94cbef5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx
@@ -0,0 +1,25 @@
+### Nomad cluster options
+
+- `-address=<string>`: The address of the Nomad server.	Overrides the NOMAD_ADDR
+  environment variable if set.
+- `-namespace=<string>`: The target namespace for queries and actions bound to a
+  namespace.	Overrides the NOMAD_NAMESPACE environment variable if set.
+- `-region=<string>`: The region of the Nomad servers to forward commands to.
+  Overrides the NOMAD_REGION environment variable if set.
+- `-ca-cert=<string>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the NOMAD_CACERT environment variable
+  if set.
+- `-client-cert=<string>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `--client-key`.
+  Overrides	the NOMAD_CLIENT_CERT environment variable if set.
+- `-client-key=<string>`: Path to an unencrypted PEM encoded private key
+  matching the	client certificate from `--client-cert`. Overrides the
+  NOMAD_CLIENT_KEY environment variable if set.
+- `-tls-server-name=<string>`: The server name to use as the SNI host when
+  connecting via	TLS. Overrides the NOMAD_TLS_SERVER_NAME environment variable
+  if set.
+- `-token=<string>`: The SecretID of an ACL token to use to authenticate API
+  requests with.	Overrides the NOMAD_TOKEN environment variable if set.
+- `-tls-skip-verify`: Do not verify TLS certificate. We do not recommend this.
+  Verification is also skipped if you set the NOMAD_SKIP_VERIFY environment
+  variable.
diff --git a/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-operations.mdx b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-operations.mdx
new file mode 100644
index 0000000000..0e51d2fca5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/tools/nomad-pack/options-operations.mdx
@@ -0,0 +1,24 @@
+### Operation options
+
+- `-var-file=<string>`: Specifies the path to a variable override file. You may
+  provide this multiple times on a single command for multiple files.
+- `-allow-unset-vars`: Suppress errors from unset variables without default
+  values. Equivalent of setting the NOMAD_PACK_ALLOW_UNSET_VARS	environment
+  variable to `1` or `true`.
+- `-ignore-missing-vars`: Determines whether the command should override
+  variables not present in the pack or should produce an error.
+- `-var=<key=value>`: Specifies single override variables in the form of HCL
+  syntax. You may specify multiple times per command.
+- `-name=<string>`: If set, this is the unique identifier of this deployed
+  instance of the specified pack. If not set, the pack name becomes the	unique
+  identifier. Setting a name is useful for running more than one	instance of a
+  pack	within the same cluster. Note that this name must	be globally unique
+  within a cluster. Running the run command multiple	times with the same	name
+  re-submits the same pack and applies changes if you have	made any to the
+  underlying pack. Be mindful that, whether	you have made changes or not, the
+  underlying allocations are replaced.When	managing packs, the name specified
+  here is the name that you should be	pass to Nomad Packs' `plan` and `destroy`
+  commands.
+- `-parser-v1`: Use the legacy syntax parser to parse your job. This enables
+  pack to run packs for earlier versions while you are	migrating them to the
+  new syntax
diff --git a/content/nomad/v1.10.x/content/partials/variables/get-example.mdx b/content/nomad/v1.10.x/content/partials/variables/get-example.mdx
new file mode 100644
index 0000000000..78c2e1bd04
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/get-example.mdx
@@ -0,0 +1,19 @@
+This example retrieves the variable stored at path `secret/foo`.
+
+```shell-session
+$ nomad var get secret/foo
+Namespace   = default
+Path        = secret/foo
+Create Time = 2025-11-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the `passcode` item from the variable stored at `secret/foo`.
+
+```shell-session
+$ nomad var get -item=passcode secret/foo
+my-long-passcode
+```
diff --git a/content/nomad/v1.10.x/content/partials/variables/init-example.mdx b/content/nomad/v1.10.x/content/partials/variables/init-example.mdx
new file mode 100644
index 0000000000..b40a5dcfb6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/init-example.mdx
@@ -0,0 +1,6 @@
+Generate an example variable specification in the current directory.
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.10.x/content/partials/variables/list-example.mdx b/content/nomad/v1.10.x/content/partials/variables/list-example.mdx
new file mode 100644
index 0000000000..65c3213d7a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/list-example.mdx
@@ -0,0 +1,113 @@
+List the variables in the namespace `prod`.
+
+```shell-session
+$ nomad var list -namespace prod
+Namespace  Path                     Last Updated
+prod       project/another-example  2025-09-19T11:21:56-04:00
+prod       project/example          2025-09-19T11:29:03-04:00
+```
+
+List the variables in namespace `prod` that match the prefix filter `project/ex`.
+
+```shell-session
+$ nomad var list -namespace prod project/ex
+Namespace  Path             Last Updated
+prod       project/example  2025-09-19T11:29:03-04:00
+```
+
+Use the wildcard namespace indicator (`*`) to list all the variables you have
+access to. For many shells, the `*` character is significant, so you might need
+to wrap it in double (`"`) or single (`'`) quotation marks.
+
+```shell-session
+$ nomad var list -namespace '*'
+Namespace  Path                     Last Updated
+dev        another-project/example  2022-09-19T11:29:54-04:00
+dev        project/example          2022-09-19T11:29:54-04:00
+dev        system/config            2022-09-19T11:29:54-04:00
+prod       project/another-example  2022-09-19T11:21:56-04:00
+prod       project/example          2022-09-19T11:29:03-04:00
+```
+
+List values under the key `nomad/jobs`.
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key `nomad/jobs/variable/www` in JSON format.
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query.
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page, include the next page token.
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting.
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
diff --git a/content/nomad/v1.10.x/content/partials/variables/lock-example.mdx b/content/nomad/v1.10.x/content/partials/variables/lock-example.mdx
new file mode 100644
index 0000000000..f5de5b84c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/lock-example.mdx
@@ -0,0 +1,13 @@
+Lock the variable at path `secret/foo` for a time of
+fifteen seconds. Execute `nomad job run webapp.nomad.hcl` if the lock succeeds.
+
+```shell-session
+$ nomad var lock -ttl=15s secret/foo "nomad job run webapp.nomad.hcl"
+```
+
+You may also pass in file, prefixed with the "@" symbol. This example store and
+locks the variables in the `spec.nv.json` file. Execute `nomad job run webapp.nomad.hcl` if the lock succeeds.
+
+```shell-session
+$ nomad var lock secret/foo @spec.nv.json `nomad job run webapp.nomad.hcl`
+```
diff --git a/content/nomad/v1.10.x/content/partials/variables/purge-example.mdx b/content/nomad/v1.10.x/content/partials/variables/purge-example.mdx
new file mode 100644
index 0000000000..0bfd80b4fb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/purge-example.mdx
@@ -0,0 +1,5 @@
+Purge all the variables at the `secret/foo` path.
+
+```shell-session
+$ nomad var purge secret/foo
+```
diff --git a/content/nomad/v1.10.x/content/partials/variables/put-example.mdx b/content/nomad/v1.10.x/content/partials/variables/put-example.mdx
new file mode 100644
index 0000000000..96467a4531
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/variables/put-example.mdx
@@ -0,0 +1,53 @@
+
+This example writes the Nomad variables `passcode=my-long-passcode` and
+`user=me` to the path `secret/foo`. The variables are scoped to the `prod`
+namespace.
+
+```shell-session
+$ nomad var put -namespace prod secret/foo passcode=my-long-passcode user=me
+```
+
+This example uses a Nomad variable specification file, prefixed with the "@"
+symbol.
+
+```shell-session
+$ nomad var put -namespace prod secret/foo @spec.nv.json
+```
+
+Use a hyphen (`-`) to instruct the command to read the variable value from
+standard input. The `-out` option displays the command's output.
+
+```shell-session
+$ echo "abcd1234" | nomad var put -namespace prod -out secret/foo bar=-
+Namespace   = prod
+Path        = secret/foo
+Create Time = 2025-11-19T11:21:56-04:00
+Check Index = 28
+
+Items
+bar = abcd1234
+```
+
+This example updates the `bar` value in the `secret/foo` path and outputs the
+updated variable in JSON format. You must include the `check-index` value when
+you update a Nomad variable.
+
+```shell-session
+$ nomad var put -namespace prod -out json -check-index 28 secret/foo bar=efgh5678
+```
+
+Output is similar to this snippet.
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "secret/foo",
+  "CreateIndex": 28,
+  "ModifyIndex": 39,
+  "CreateTime": 1663600883130070567,
+  "ModifyTime": 1663601343585644939,
+  "Items": {
+    "bar": "efgh5678",
+  }
+}
+```
diff --git a/content/nomad/v1.10.x/content/partials/version/tag-reason.mdx b/content/nomad/v1.10.x/content/partials/version/tag-reason.mdx
new file mode 100644
index 0000000000..aad3aba7cd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/version/tag-reason.mdx
@@ -0,0 +1,4 @@
+Applying a tag to a version prevents Nomad from garbage collecting that version.
+You can compare versions by tag name as well as version number.
+
+Tag names must be unique per job.
diff --git a/content/nomad/v1.10.x/content/partials/virt-beta-callout.mdx b/content/nomad/v1.10.x/content/partials/virt-beta-callout.mdx
new file mode 100644
index 0000000000..23c97213e3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/partials/virt-beta-callout.mdx
@@ -0,0 +1,6 @@
+<Note title="Beta Feature">
+
+The Virt task driver is under active development. Refer to the [repo
+README](https://github.com/hashicorp/nomad-driver-virt) for the latest updates. Do not use this driver in production environments.
+
+</Note>
diff --git a/content/nomad/v1.10.x/content/plugins/author/device.mdx b/content/nomad/v1.10.x/content/plugins/author/device.mdx
new file mode 100644
index 0000000000..0061b9ebb0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/author/device.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Create a device plugin for Nomad
+description: |-
+  Learn how to create a Nomad device plugin so you can schedule workload tasks with other devices, such as GPUs. Review device plugin lifecycle and the device plugin API functions that you must implement in your device plugin.
+---
+
+# Create a device plugin
+
+This page provides conceptual information for creating a device driver plugin to extend Nomad's workload execution functionality.
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Use Nomad device driver plugins to support scheduling tasks with
+other devices, such as GPUs. Device driver plugins are responsible for
+fingerprinting these devices and working with the Nomad client to make them
+available to assigned tasks.
+
+For a real world example of a Nomad device plugin implementation, refer to the
+[Nvidia GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring a device plugin
+
+Authoring a device plugin in Nomad consists of implementing the
+[BasePlugin][base-plugin] and [DevicePlugin][deviceplugin] interfaces alongside
+a main package to launch the plugin.
+
+The [nomad-skeleton-device-plugin][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and state
+
+A device plugin is long-lived. Nomad ensures that one instance of the plugin
+is running. If the plugin crashes or otherwise terminates, Nomad launches
+another instance of it.
+
+However, unlike [task driver plugins](/nomad/plugins/author/task-driver), device
+plugins do not currently have an interface for persisting state to the Nomad
+client. Instead, the device plugin API emphasizes fingerprinting devices and
+reporting their status. After helping to provision a task with a scheduled
+device, a device plugin does not have any responsibility, or ability, to monitor
+the task.
+
+## Base plugin API
+
+@include 'plugins/base.mdx'
+
+## Device driver plugin API
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The client calls the `Fingerprint` [function][fingerprintfn] when the plugin is
+started. This function allows the plugin to provide Nomad with a list of
+discovered devices, along with their attributes, for the purpose of scheduling
+workloads using devices. The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at an
+appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device
+groups. A _device group_ is a list of detected devices that are identical for the
+purpose of scheduling, which means they have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsResponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the
+information necessary for the client to make those devices available to a task.
+Currently, the `ContainerReservation` object allows the plugin to specify
+environment variables for the task, as well as a list of host devices and files
+to be mounted into the task's filesystem. Any orchestration required to prepare
+the device for use should also be performed in this function.
+
+@include 'plugins/hcl-specifications.mdx'
+
+[base-plugin]: https://github.com/hashicorp/nomad/blob/main/plugins/base/base.go#L17
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/main/plugins/device/device.go#L28
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]:https://github.com/hashicorp/nomad/blob/main/plugins/device/device.go#L45
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L162
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L172
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L192
+[dimensioned]: https://github.com/hashicorp/nomad/blob/main/plugins/shared/structs/stats.go#L37
diff --git a/content/nomad/v1.10.x/content/plugins/author/host-volume.mdx b/content/nomad/v1.10.x/content/plugins/author/host-volume.mdx
new file mode 100644
index 0000000000..c139622afd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/author/host-volume.mdx
@@ -0,0 +1,433 @@
+---
+layout: docs
+page_title: Create a host volume plugin
+description: |-
+  Use Nomad's dynamic host volume plugins specification to create a host volume plugin so that you can dynamically configure persistent storage on your client nodes. Review examples that create a directory and a Linux filesystem. Reference plugin arguments and environment variables.
+---
+
+# Create a host volume plugin
+
+This page describes the plugin specification for
+[dynamic host volumes][stateful-workloads], with examples, so you can write
+your own plugin to dynamically configure persistent storage on your Nomad
+client nodes.
+
+If you do not need to write your own plugin, consider Nomad's built-in
+[`mkdir` plugin][mkdir_plugin], which creates a directory on the host.
+
+If you have more complex needs, review the following examples to get a
+sense of the specification in action. A plugin can be as basic as a short shell
+script.
+
+The full [specification](#specification) follows the examples,
+and is followed by a list of [general considerations](#considerations).
+
+## Examples
+
+The specification is lean enough to be readily fulfilled in any language.
+The following examples are written in `bash`.
+
+The `custom-mkdir` plugin creates a directory, and `mkfs-ext4` creates a Linux
+filesystem. You may imagine others, such as an NFS mount or another
+storage infrastructure API.
+
+Each example includes a minimal [volume specification][], which assumes that
+you have placed the plugin in the [host volume plugin directory][plugin_dir]
+and made it executable.
+
+<Tabs>
+<Tab heading="custom-mkdir">
+
+`custom-mkdir` only creates a directory. There is a plugin built into Nomad that
+does this called "mkdir", but this serves as a minimal example.
+
+Volume specification:
+
+```hcl
+type      = "host"
+name      = "mkdir-vol"
+plugin_id = "custom-mkdir" # plugin filename
+```
+
+Plugin code:
+
+```bash
+#!/usr/bin/env bash
+
+# set -u to error by name if an env var is not set
+set -eu
+
+# echo to stderr, because Nomad expects stdout to match the spec.
+# this (and stdout) show up in Nomad agent debug logs.
+stderr() {
+  1>&2 echo "$@"
+}
+
+get_path() {
+  # since delete runs `rm -rf` (frightening), check to make sure
+  # the path is something sensible.
+  if [ -z "$DHV_VOLUMES_DIR" ]; then
+    stderr "DHV_VOLUMES_DIR must not be empty"
+    exit 1
+  fi
+  if [ -z "$DHV_VOLUME_ID" ]; then
+    stderr "DHV_VOLUME_ID must not be empty"
+    exit 1
+  fi
+  # create and delete assign this echo output to a variable
+  echo "$DHV_VOLUMES_DIR/$DHV_VOLUME_ID"
+}
+
+case "$DHV_OPERATION" in
+  "fingerprint")
+    echo '{"version": "0.0.1"}'
+    ;;
+  "create")
+    path="$(get_path)"
+    stderr "creating directory: $path"
+    # `mkdir -p` may be run repeatedly with the same result;
+    # it is idempotent.
+    mkdir -p "$path"
+    # 0 bytes because plain directories are not any particular size.
+    printf '{"path": "%s", "bytes": 0}' "$path"
+    ;;
+  "delete")
+    path="$(get_path)"
+    stderr "deleting directory: $path"
+    rm -rf "$path" # `rm -f` is also idempotent.
+    ;;
+  *)
+    echo "unknown operation: '$DHV_OPERATION'"
+    exit 1
+    ;;
+esac
+```
+
+</Tab>
+<Tab heading="mkfs-ext4">
+
+`mkfs-ext4` creates a Linux ext4 filesystem with the `mkfs.ext4` command and
+mounts it  as a loopback device. Unlike `mkdir`, `mkfs` can restrict the size
+of the volume.
+
+Volume specification:
+
+```hcl
+type         = "host"
+name         = "mkfs-vol"
+plugin_id    = "mkfs-ext4" # plugin filename
+capacity_min = "50MB" # capacity values are required by this plugin
+capacity_max = "50MB"
+```
+
+Plugin code:
+
+```bash
+#!/usr/bin/env bash
+set -euo pipefail
+
+version='0.0.1'
+
+stderr() {
+  1>&2 echo "$@"
+}
+
+get_path() {
+  if [ -z "$DHV_VOLUMES_DIR" ]; then
+    stderr "DHV_VOLUMES_DIR must not be empty"
+    exit 1
+  fi
+  if [ -z "$DHV_VOLUME_ID" ]; then
+    stderr "DHV_VOLUME_ID must not be empty"
+    exit 1
+  fi
+  echo "$DHV_VOLUMES_DIR/$DHV_VOLUME_ID"
+}
+
+is_mounted() {
+  mount | grep -q " $1 "
+}
+
+create_volume() {
+    local path="$1"
+    local bytes="$2"
+
+    # translate to mb for dd block size
+    local megs=$((bytes / 1024 / 1024)) # lazy, approximate
+    if [ $megs -le 0 ]; then
+      stderr "minimum capacity must be greater than zero."
+      exit 2
+    fi
+
+    mkdir -p "$path"
+    # the if statements ensure idempotency
+    if [ ! -f "$path.ext4" ]; then
+      # dd only writes to stderr, so safe to run without redirection
+      dd if=/dev/zero of="$path.ext4" bs=1M count="$megs"
+      # mkfs includes stdout, so we need to redirect that to stderr
+      mkfs.ext4 "$path.ext4" 1>&2
+    fi
+    if ! is_mounted "$path"; then
+      mount "$path.ext4" "$path"
+    fi
+}
+
+delete_volume() {
+  local path="$1"
+  is_mounted "$path" && umount "$path"
+  rm -rf "$path"
+  rm -f "$path.ext4"
+}
+
+case "$1" in
+  "fingerprint")
+    printf '{"version": "%s"}' "$version"
+    ;;
+  "create")
+    path="$(get_path)"
+    stderr "creating volume at $path"
+    create_volume "$path" "$DHV_CAPACITY_MIN_BYTES"
+    # output what Nomad expects
+    bytes="$(stat --format='%s' "$path.ext4")"
+    printf '{"path": "%s", "bytes": %s}' "$path" "$bytes"
+    ;;
+  "delete")
+    path="$(get_path)"
+    stderr "deleting volume at $path"
+    delete_volume "$path" ;;
+  *)
+    echo "unknown operation: $1"
+    exit 1 ;;
+esac
+```
+
+</Tab>
+</Tabs>
+
+## Specification
+
+A host volume plugin is registered with Nomad if it:
+
+- Is an executable file, such as a script or binary
+- Is located in the [`client.host_volume_plugin_dir`][plugin_dir] directory
+  on Nomad client nodes
+- Responds appropriately to a `fingerprint` call
+
+### Operations
+
+To fully manage the lifecycle of a volume, plugins must fulfill all of the
+following operations:
+
+- [fingerprint](#fingerprint)
+- [create](#create)
+- [delete](#delete)
+
+Nomad passes the operation as the first positional argument to the plugin.
+That and other information are passed as environment variables. Environment
+variables are prefixed with `"DHV_"`, which stands for "Dynamic Host Volume."
+
+Some variables may be required for certain plugins, such as `DHV_CAPACITY_*`
+for plugins that can restrict size. Most variables are for plugin author convenience.
+
+#### fingerprint
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `fingerprint` to discover valid plugins when the client agent 
+starts or is reloaded with a SIGHUP. The version it returns is used to register
+the plugin on the Nomad node for volume scheduling.
+
+**CLI arguments:** `$1=fingerprint`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=fingerprint
+```
+
+**Expected stdout:**
+
+```
+{"version": "0.0.1"}
+```
+
+**Requirements:**
+
+- Must complete within 5 seconds, or Nomad will kill it. It should be much
+  faster, as no actual work should be done.
+- "version" value must be valid per the [hashicorp/go-version][go-version]
+  golang package.
+
+</blockquote>
+
+#### create
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `create` when you run [`nomad volume create`][cli-create] CLI or
+use the [create API][api-create]).
+
+You can run `create` again for the same volume if you include the volume
+`id` in the volume specification.
+
+When the agent starts, Nomad also calls `create` for each volume that was
+previously created on the node so that plugins can ensure the volumes are available
+after an agent restart or host reboot.
+
+**CLI Arguments:** `$1=create`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=create
+DHV_VOLUMES_DIR={directory to put the volume in}
+DHV_PLUGIN_DIR={path to directory containing plugins}
+DHV_NAMESPACE={volume namespace}
+DHV_VOLUME_NAME={name from the volume specification}
+DHV_VOLUME_ID={volume ID generated by Nomad}
+DHV_NODE_ID={Nomad node ID}
+DHV_NODE_POOL={Nomad node pool}
+DHV_CAPACITY_MIN_BYTES={capacity_min from the volume spec, expressed in bytes}
+DHV_CAPACITY_MAX_BYTES={capacity_max from the volume spec, expressed in bytes}
+DHV_PARAMETERS={stringified json of parameters from the volume spec}
+```
+
+**Expected stdout:**
+
+```
+{"path": "/path/to/created/volume", "bytes": 50000000}
+```
+
+**Expected stdout on error:**
+
+```
+{"error": "error message"}
+```
+
+Returning an error message is optional. Nomad returns the error message in any
+error returned to the user.
+
+**Requirements:**
+
+- Must complete within 60 seconds, or Nomad will kill it.
+- Must create a path on disk, within `DHV_VOLUMES_DIR` or otherwise, and return
+  it as `"path"`. Nomad will mount this path into workloads that request the
+  volume, and it will also be sent to `delete` later as `DHV_CREATED_PATH`.
+- Must be idempotent - running create with the same inputs should produce the
+  same result.
+- Must be safe to run concurrently, per volume name per node.
+- If the plugin fails partway through create, it must clean up after itself
+  and exit non-0. Nomad will not attempt to delete partial creates.
+- However, if during an _initial_ create, Nomad fails to save the volume in its
+  own state, it will issue `delete` automatically to avoid leaving any
+  stray volumes on disk.
+
+</blockquote>
+
+#### delete
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `delete` when you run [`nomad volume delete`][cli-delete] CLI or
+use the [delete API][api-delete].
+
+**CLI Arguments:** `$1=delete`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=delete
+DHV_CREATED_PATH={path that `create` returned}
+DHV_VOLUMES_DIR={directory that volumes should be put in}
+DHV_PLUGIN_DIR={path to directory containing plugins}
+DHV_NAMESPACE={volume namespace}
+DHV_VOLUME_NAME={name from the volume specification}
+DHV_VOLUME_ID={volume ID generated by Nomad}
+DHV_NODE_ID={Nomad node ID}
+DHV_NODE_POOL={Nomad node pool}
+DHV_PARAMETERS={stringified json of parameters from the volume spec}
+```
+
+**Expected stdout:** none (stdout is discarded)
+
+**Expected stdout on error:**
+
+```
+{"error": "error message"}
+```
+
+Returning an error message is optional. Nomad returns the error message in any
+error returned to the user.
+
+**Requirements:**
+
+- Must complete within 60 seconds, or Nomad will kill it.
+- Must remove the `DHV_CREATED_PATH` that was returned by `create`,
+  or derive the path from other variables the same way that `create` did.
+- Must be idempotent - calling delete on an already deleted volume must not
+  return an error.
+- Must be safe to run concurrently, per volume name per node.
+- Will be run after a failed `create` operation during initial volume creation.
+
+</blockquote>
+
+## Considerations
+
+Plugin authors should consider these details when writing plugins.
+
+### Execution
+
+- The plugin is executed as the same user as the `nomad` agent (likely root).
+- Plugin `stdout` and `stderr` are exposed as client agent debug logs,
+  so plugins should not output sensitive information.
+- Nomad does not retry automatically on error. The caller of create/delete
+  must retry manually. The plugin may do so internally with its own retry
+  logic, provided it still completes within the deadline.
+- Errors from `create` while restoring a volume during Nomad agent start
+  do not halt the client. The error will be in client logs, and the volume
+  is not registered as available on the node.
+- Be aware that the `DHV_VOLUME_NAME` and `DHV_PARAMETERS` fields are controlled
+  by the volume author. If the expected volume authors are not the Nomad
+  administrators, you should ensure your plugin handles these fields safely or
+  ignores them.
+
+### Uniqueness
+
+- Volume `name` is unique per _node_, and volume `ID` is unique per _region_.
+- Only one create/delete operation at a time is executed per volume `name`
+  per node, and similarly by `id` on Nomad servers, but many create/delete
+  operations for different volume IDs may run concurrently, even on the same
+  node.
+- We suggest placing volumes in `DHV_VOLUMES_DIR` for consistency, but it is not
+  required. The built-in `mkdir` plugin uses `$DHV_VOLUMES_DIR/$DHV_VOLUME_ID`
+  to ensure uniqueness across the cluster. We recommend against using
+  `DHV_VOLUME_NAME` in the path unless the plugin guards against path
+  traversal.
+- Plugins that write into network storage need to take care not to delete
+  remote/shared state by `name`, unless they know that there are no other
+  volumes with workloads using that name.
+
+### Configuration
+
+- Per-_volume_ configuration should be set in the volume specification file's
+  `parameters`. Per-_node_ configuration should be put in config file(s) as
+  described next.
+- There is no mechanism built into Nomad for plugin configuration. As a
+  convention, we suggest placing any necessary configuration file(s) next to
+  the executable plugin in the plugin directory. You may use `DHV_PLUGIN_DIR`
+  to refer to the directory.
+- If a plugin needs to retain state across operations (e.g. delete needs
+  some value that was generated during create), then you may store that on
+  the host filesystem, or some external data store of your choosing, perhaps
+  even Nomad variables.
+
+[stateful-workloads]: /nomad/docs/architecture/storage/host-volumes
+[plugin_dir]: /nomad/docs/configuration/client#host_volume_plugin_dir
+[volume specification]: /nomad/docs/other-specifications/volume/host
+[go-version]: https://pkg.go.dev/github.com/hashicorp/go-version#pkg-constants
+[cli-create]: /nomad/commands/volume/create
+[api-create]: /nomad/api-docs/volumes#create-dynamic-host-volume
+[cli-delete]: /nomad/commands/volume/delete
+[api-delete]: /nomad/api-docs/volumes#delete-dynamic-host-volume
+[mkdir_plugin]: /nomad/docs/other-specifications/volume/host#mkdir-plugin
+[host_volumes_dir]: /nomad/docs/configuration/client#host_volumes_dir
diff --git a/content/nomad/v1.10.x/content/plugins/author/index.mdx b/content/nomad/v1.10.x/content/plugins/author/index.mdx
new file mode 100644
index 0000000000..df9cb3f6c3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/author/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Nomad plugin authoring guide
+description: |-
+  Expand Nomad functionality by authoring your own plugins.
+---
+
+# Nomad plugin authoring guide
+
+Nomad implements a plugin framework that lets you extend the functionality of
+some components within Nomad. The design of the plugin system is inspired by the
+lessons learned from plugin systems implemented in other HashiCorp products such
+as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Device](/nomad/plugins/author/device): Extend workload functionality with a
+  custom hardware device.
+- [Host volume](/nomad/plugins/author/host-volume): Extend workload storage
+  functionality with a plugin specific to your local storage environment.
+- [Task driver](/nomad/plugins/author/task-driver): Extend task execution
+  functionality with a custom task driver.
+
+## Architecture
+
+The Nomad task driver and device plugin framework uses the [go-plugin][goplugin]
+project to expose a language-independent plugin interface. Plugins implement a
+set of gRPC services and methods that Nomad manages by running the plugin and
+calling the implemented RPCs. As a result, plugins are free to be implemented
+in the author's language of choice. To facilitate plugin development, a set of
+Go interfaces and structs exist for each plugin type that abstracts away
+go-plugin and the gRPC interface. The guides in this documentation reference
+these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.10.x/content/plugins/author/task-driver.mdx b/content/nomad/v1.10.x/content/plugins/author/task-driver.mdx
new file mode 100644
index 0000000000..9b41a61fca
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/author/task-driver.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Create task driver plugin for Nomad
+description: Learn how to create a Nomad task driver plugin to extend Nomad's workload execution functionality.
+---
+
+# Create a task driver plugin
+
+This page provides conceptual information for creating a task driver plugin to
+extend Nomad's workload execution functionality.
+
+Task drivers in Nomad are the runtime components that execute workloads. For a
+real world example of a Nomad task driver plugin implementation, refer to the
+[exec2 driver][].
+
+## Authoring a task driver plugin
+
+Authoring a task driver consists of implementing the [BasePlugin][base-plugin]
+and [DriverPlugin][driverplugin] interfaces and adding a main package to launch
+the plugin.
+
+The [nomad-skeleton-driver-plugin project][skeletonproject] exists to help
+bootstrap the development of new task driver plugins. It provides most of the
+boilerplate necessary for a task driver plugin, along with detailed comments.
+
+### Lifecycle and state
+
+A task driver plugin is long-lived and its lifetime is not bound to the Nomad
+client. This means that the Nomad client can restart without restarting the
+driver. Nomad ensures that one instance of the task driver is running. If
+the task driver crashes or otherwise terminates, Nomad launches another instance
+of it.
+
+Task drivers should maintain as little state as possible. State for a task is
+stored by the Nomad client on task creation. This enables a pattern where the
+task driver can maintain an in-memory state of the running tasks, and if
+necessary the Nomad client can recover tasks into the task driver state.
+
+## Base plugin API
+
+@include 'plugins/base.mdx'
+
+## Task driver plugin API
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the task driver configuration of the task.
+For more information on `hclspec.Spec`, refer to the [HCL specifications
+section](#hcl-specifications).
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the task driver implements.
+
+```go
+type Capabilities struct {
+    // SendSignals marks the task driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the task driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the task driver supports.
+    FSIsolation fsisolation.Mode
+
+    //NetIsolationModes lists the set of isolation modes supported by the task driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the task driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the task driver supports.
+    MountConfigs MountConfigSupport
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+
+    // DynamicWorkloadUsers indicates this driver is capable (but not required)
+    // of making use of a UID/GID not backed by a user known to the operating
+    // system. The allocation of a unique, not-in-use UID/GID is managed by the
+    // Nomad client ensuring no overlap.
+    DynamicWorkloadUsers bool
+}
+```
+
+The file system isolation options are the following:
+
+- `fsisolation.Image`: The task driver isolates tasks as machine images.
+- `fsisolation.Chroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `fsisolation.Unveil`: The task driver isolates tasks with the
+  [Landlock LSM][landlock] or other [`unveil`][unveil] like system.
+- `fsisolation.None`: The task driver has no filesystem isolation.
+
+The network isolation modes are the following:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the task driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available for
+the task driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of the following states:
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the task driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] that includes all of the
+configuration needed to launch the task. Additionally, the task driver
+configuration can be decoded from the `TaskConfig` by calling
+`*TaskConfig.DecodeDriverConfig(t interface{})`, passing in a pointer to the
+task driver specific configuration struct. The `TaskConfig` includes an `ID`
+field which future operations on the task are referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] that contains the required
+information for the task driver to reattach to the running task in the case of
+plugin crashes or restarts. Some of this required state is specific to the
+task driver implementation, thus a `DriverState` field exists to allow the task
+driver to encode custom state into the struct. Helper fields exist on the
+`TaskHandle` to `GetDriverState` and `SetDriverState` removing the need for the
+task driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the task driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the task driver cleans up any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the task driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the task driver in
+the `TaskConfig`. Use the [`fifo` package][fifopackage] to support cross
+platform writing to these paths.
+
+#### Dynamic workload users
+
+Nomad is capable of dynamically allocating unused UID/GID values for use by
+task drivers when launching a task. These UID/GID values are deallocated when
+the task is destroyed. The pool of available UID/GID values can be controlled
+in client config via the [users][users] block.
+
+#### TaskHandle schema versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but it allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted, it is not expected to persist any internal state to
+disk. To support this, Nomad attempts to recover a task that was previously
+started if the task driver does not recognize the task ID. During task recovery,
+Nomad calls `RecoverTask`, passing the `TaskHandle` that was returned by the
+`StartTask` function. If no error is returned, it is expected that the task
+driver can now operate on the task by referencing the task ID. If an error
+occurs, the Nomad client marks the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that sends an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task
+immediately sends an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the task
+driver must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the task driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the task driver should send
+stats to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the task driver to publish driver specific events
+about tasks and the Nomad client associates them with the correct
+allocation.
+
+An `Eventer` utility, available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package, implements an event
+loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers that support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the task driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+@include 'plugins/hcl-specifications.mdx'
+
+[exec2 driver]: https://github.com/hashicorp/nomad-driver-exec2
+[base-plugin]: https://github.com/hashicorp/nomad/blob/main/plugins/base/base.go#L17
+[driverplugin]: https://github.com/hashicorp/nomad/blob/main/plugins/drivers/driver.go#L51
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[unveil]: https://man.openbsd.org/unveil
+[users]: /nomad/docs/configuration/client#users-block
diff --git a/content/nomad/v1.10.x/content/plugins/devices/index.mdx b/content/nomad/v1.10.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..387e683f37
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/devices/index.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: Nomad device driver plugins
+description: |-
+  Use device driver plugins to detect your Nomad client's physical hardware devices, such as graphical processing units (GPUs), field programmable gate arrays (FPGAs), tensor processing units (TPUs), and universal serial buses (USBs). You can then use those devices in your Nomad workloads. Review conceptual, installation, usage, and reference information for the NVIDIA and USB device driver plugins.
+---
+
+# Nomad device driver plugins
+
+Use device driver plugins to detect physical hardware devices, such as graph
+processing units (GPUs), a field-programmable gate arrays (FPGAs), and universal
+serial buses (USBs), on your Nomad clients. You can then use those devices in
+your Nomad workloads.
+
+By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+## Nomad device drivers
+
+We support the [NVIDIA] device driver plugin, which you must install
+separately. Refer to the [NVIDIA] documentation for instructions.
+
+## Community Device Drivers
+
+The community supports the [USB] device driver plugin.
+
+## Create device drivers
+
+Nomad's device driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[NVIDIA]: /nomad/plugins/devices/nvidia
+[USB]: /nomad/plugins/devices/usb
+[plugin_guide]: /nomad/plugins/author/device
diff --git a/content/nomad/v1.10.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.10.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..c10a83b9f3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: NVIDIA GPU device plugin
+description: The NVIDIA GPU device plugin exposes NVIDIA GPUs to Nomad so you can run workloads on GPU hardware. Install and configure the plugin on your Nomad clients. Configure job tasks to use GPUs
+---
+
+# NVIDIA GPU device plugin
+
+Name: `nomad-device-nvidia`
+
+Use the NVIDIA device plugin to expose NVIDIA graphical processing units (GPUs)
+to Nomad. The driver automatically supports [Multi-Instance GPU (MIG)][mig].
+
+The NVIDIA device plugin uses [NVML] bindings to get data regarding available
+NVIDIA devices and then exposes them via [Fingerprint RPC]. Consult [NVIDIA's
+documentation](https://docs.nvidia.com/deploy/nvml-api/nvml-api-reference.html#nvml-api-reference)
+for a list of supported cards. The plugin detects
+whether the GPU has Multi-Instance GPU enabled, and when enabled, the plugin
+fingerprints all instances as individual GPUs. You may exclude GPUs from
+fingerprinting by setting the [`ignored_gpu_ids` field](#plugin-configuration).
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit     |
+|------------------|----------|
+| memory           | MiB      |
+| power            | W (Watt) |
+| bar1             | MiB      |
+| driver_version   | string   |
+| cores_clock      | MHz      |
+| memory_clock     | MHz      |
+| pci_bandwidth    | MB/s     |
+| display_state    | string   |
+| persistence_mode | string   |
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of NVIDIA GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. Refer to [NVIDIA's
+documentation](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. 64 bit GNU/Linux with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from NVIDIA to prepare a machine to use docker containers with NVIDIA GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:12.8.1-base-ubuntu22.04 nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The NVIDIA integration only works with drivers who natively integrate with
+NVIDIA's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container) and cards that are [supported
+by NVML](https://docs.nvidia.com/deploy/nvml-api/nvml-api-reference.html#nvml-api-reference).
+
+Nomad has tested support with the [`docker` driver][docker-driver].
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download]. To
+install the plugin, download the binary or compile from source. Then place the
+binary in the [plugin directory][`plugin_dir`].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:12.8.1-base-ubuntu22.04"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[NVML]: https://github.com/NVIDIA/go-nvml
+[Fingerprint RPC]: /nomad/plugins/author/device#fingerprint-context-context-chan-fingerprintresponse-error
+[mig]: https://www.nvidia.com/en-us/technologies/multi-instance-gpu/
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/job-declare/task-driver/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/job-declare/task-driver/java 'Nomad java Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.10.x/content/plugins/devices/usb.mdx b/content/nomad/v1.10.x/content/plugins/devices/usb.mdx
new file mode 100644
index 0000000000..23ffa463eb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/devices/usb.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: USB device plugin
+description: |-
+  The USB Device Plugin detects USB devices so you can use them in your Nomad workloads. Learn how to configure and install the plugin. Review the plugin's fingerprinted attributes and exposed runtime environment variables.
+---
+
+# USB device plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.10.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..f64e0eb03e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Community task driver plugins
+description: Learn about the community-supported task driver plugins that extend Nomad job features. Review installation, usage, and reference information for containerd, Firecracker, Jail, Pledge, Pot, Rookout, Singularity, system-nspawn, and Windows IIS task driver plugins.
+---
+
+# Community task driver plugins
+
+Task driver plugins authored and maintained by the Nomad community are listed on
+the [Nomad integrations page](/nomad/integrations). On that page, select
+**Community** from the **Tiers** list and **Task Drivers** from the **Types**
+list to review Community-authored task driver plugins.
+
+If you have authored a task driver plugin that you believe is useful to the
+broader Nomad community and are committed to maintaining the plugin,
+create a [Nomad GitHub issue](https://github.com/hashicorp/nomad/issues) so we can add your plugin to the Nomad Integrations page.
+
+For details on authoring a task driver plugin, refer to the [plugin
+authoring guide](/nomad/docs/concepts/plugins).
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/exec2.mdx b/content/nomad/v1.10.x/content/plugins/drivers/exec2.mdx
new file mode 100644
index 0000000000..218be4de26
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/exec2.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Exec2 task driver plugin
+description: >-
+  The Exec2 task driver executes a command for a job task and leverages Linux kernel features such as Landlock LSM, cgroups v2, and the `unshare` system utility. Learn how to configure and install the Exec2 task driver plugin. Review capabilities, client requirements, and concepts such as filesystem and resource isolation. Learn how to use the Exec2 task driver in your Nomad job. Configure command, command args, paths, memory, CPU resources, and out-of-memory (OOM) behavior.
+---
+
+# Exec2 task driver plugin
+
+Name: `exec2`
+
+The `exec2` driver is used to execute a command for a task. It offers a security
+model optimized for running 'ordinary' processes with very low startup times
+and minimal overhead in terms of CPU, disk, and memory utilization. The `exec2`
+driver leverages kernel features such as the [Landlock LSM][landlock], cgroups
+v2, and the [`unshare`][unshare] system utility.
+
+Review the source on [GitHub][github].
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-exec2/) and verify the binary using the
+available SHA-256 sums. After downloading nomad-driver-exec2 driver, unzip the package. Make sure
+that the `nomad-driver-exec2` binary is available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path, specified by the client's config file, before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-exec2
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-exec2
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example below is a short demonstration of what a task making use of the
+exec2 task driver looks like:
+
+```hcl
+job "http" {
+  group "web" {
+    task "python" {
+      driver = "exec2"
+      config {
+        command = "python3"
+        args    = ["-m", "http.server", "8080", "--directory", "${NOMAD_TASK_DIR}"]
+        unveil  = ["r:/etc/mime.types"]
+      }
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `exec2` task driver is not built into Nomad. It must be [downloaded][releases]
+onto the client host in the configured plugin directory.
+
+- Linux 5.15+
+- Cgroups v2 enabled
+- Landlock LSM enabled
+- Commands `nsenter` and `unshare`
+- Nomad client running as root
+
+## Capabilities
+
+The `exec2` task driver implements the following driver [capabilities][capabilities]
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | false             |
+| filesystem isolation | unveil            |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+## Concepts
+
+### Filesystem Isolation
+
+##### landlock
+
+The `exec2` task driver makes use of [`go-landlock`][landlock] for providing
+filesystem isolation, making the host filesystem unreachable except where
+explicitly allowed.
+
+By default a task is enabled to access its task directory and its shared alloc
+directory. The paths to these directories are accessible by reading the environment
+variables `$NOMAD_TASK_DIR` and `$NOMAD_ALLOC_DIR` respectively.
+
+A file access mode must also be specified when granting additional filesystem
+access to a path. This is done by prefix the path with `'r'`, `'w'`, `'x'`,
+and/or `'c'` indicating read, write, executable, and create permissions,
+respectively. e.g.,
+
+- <code>r:/srv/www</code> - read-only access to `/srv/www`
+- <code>rwc:/tmp</code> - read, write, and create files in `/tmp`
+- <code>rx:/opt/bin/application</code> - read and execute a specific application
+- <code>wc:/var/log</code> - write and create files in `/var/log`
+
+This style of permission control is modeled after the [`unveil`][unveil] system
+call pioneered by the OpenBSD project. In configuration parameters we refer to
+"unveil"-ing of filesystem paths as `exec2` is leveraging landlock to emulate
+the semantics of `unveil`.
+
+##### dynamic workload users
+
+While landlock prevents tasks from accessing the host filesystem, Nomad 1.8
+introduces `dynamic workload users` which enable tasks to be run as a UID/GID
+that is not assigned to any user. This provides protection from non-root users
+getting access inside the task and allocation directories created for the task.
+
+To make use of a dynamic workload user, simply leave the `user` field blank in
+the task definition of an `exec2` task.
+
+### Resource Isolation
+
+Similar to `exec` and other container runtimes, `exec2` makes use of cgroups for
+limiting the amount of CPU and RAM a task may consume.
+
+## Configuration
+
+### Plugin Configuration
+
+The default plugin configuration is shown below. System default paths are enabled,
+but nothing else. These default paths enable basic functionality like reading
+system TLS certificates, executing programs in `/bin`, `/usr/bin`, and accessing
+system shared object files. The exact set of paths is system dependent, and can
+be disabled or customized in plugin config.
+
+The default set of paths are listed below. These paths are enabled only if they
+are found to exist at the time of the task launching.
+
+##### shared objects
+
+```
+rx:/lib
+rx:/lib64
+rx:/usr/lib
+rx:/usr/libexec
+rx:/usr/local/lib
+rx:/usr/local/lib64
+r:/etc/ld.so.conf
+r:/etc/ld.so.cache
+r:/etc/ld.so.conf.d
+```
+
+##### io, common
+
+```
+rwc:/tmp
+rw:/dev/null
+r:/dev/zero
+r:/dev/fd
+rw:/dev/stdin
+rw:/dev/stdout
+r:/dev/urandom
+w:/dev/log
+r:/usr/share/locale
+r:/proc/self/cmdline
+r:/usr/share/zoneinfo
+r:/usr/share/common-licenses
+r:/proc/sys/kernel/ngroups_max
+r:/proc/sys/kernel/cap_last_cap
+r:/proc/sys/vm/overcommit_memory
+```
+
+##### dns
+
+```
+r:/etc/hosts
+r:/hostname
+r:/etc/services
+r:/etc/protocols
+r:/etc/resolv.conf
+```
+
+##### certificates
+
+```
+r:/etc/ssl/certs
+r:/etc/pki/tls/certs
+r:/etc/ssl/ca-bundle.pem
+r:/etc/pki/tls/cacert.pem
+r:/etc/pki/ca-trust-extracted/pem/tls-ca-bundle.pem
+r:/etc/ssl/cert.pem
+```
+
+Additional allowable paths can be specified at the plugin level, which applies
+to all tasks making use of the `exec2` task driver, or at the task level, which
+will apply specifically to each task.
+
+```hcl
+plugin "nomad-driver-exec2" {
+  config {
+    unveil_defaults = true
+    unveil_paths    = []
+    unveil_by_task  = false
+  }
+}
+```
+
+- `unveil_defaults` - (default: `true`) - enable or disable default system paths
+  useful for running basic commands
+- `unveil_paths` - (default: `[]`) - a list of filesystem paths with permissions
+  to grant all tasks
+  ```hcl
+  unveil_paths = ["rx:/opt/bin", "r:/srv/certs"]
+  ```
+- `unveil_by_task` - (default: `false`) - enable or disable job submitters to
+  specify additional filesystem path access within task config
+
+### Task Configuration
+
+##### config
+
+Task configuration for an exec2 task includes setting a `command`, `args` for
+the command, and additional `unveil` filesystem paths if `unveil_by_task` is
+enabled in plugin configuration.
+
+```hcl
+config {
+  command       = "/usr/bin/cat"
+  args          = ["/etc/os-release"]
+  unveil        = ["r:/etc/os-release"]
+  oom_score_adj = 500
+}
+```
+
+- `command` - (string: required) - command to run
+- `args` - (list(string): optional) - list of arguments to provide
+  to `command`
+- `unveil` - (list(string): optional) - list of additional filesystem paths to
+  provide access to the task (requires `unveil_by_task` in plugin config).
+- `oom_score_adj` - (optional) - The likelihood of the task being OOM killed,
+  must be a positive integer. Defaults to `0`.
+
+##### cpu
+
+Tasks are limited in CPU resources by setting the `cpu` or `cores` values in the
+task `resources` block.
+
+- `cpu` - (default: `100`) - limits the CPU bandwidth allowable for the task to
+  make use of in MHz, may not be used with `cores`.
+- `cores` - (int: optional) - specifies the number of CPU cores to reserve
+  specifically for the task, may not be used with `cpu`
+
+##### memory
+
+Tasks are limited in memory resources by setting `memory` and optionally the
+`memory_max` values in the task `resources` block.
+
+### Node Attributes
+
+When installed, the `exec2` plugin provides the following node attributes which
+can be used as constraints when authoring jobs.
+
+```
+driver.exec2.unveil.defaults    = true
+driver.exec2.unveil.tasks       = true
+```
+
+[capabilities]: /nomad/plugins/author/task-driver#task-driver-plugin-api
+[github]: https://github.com/hashicorp/nomad-driver-exec2
+[landlock]: https://github.com/shoenig/go-landlock
+[releases]: https://releases.hashicorp.com/nomad-driver-exec2
+[unshare]: https://www.man7.org/linux/man-pages/man1/unshare.1.html
+[unveil]: https://man.openbsd.org/unveil
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/index.mdx b/content/nomad/v1.10.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..77dbdbe7ff
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Task driver plugins
+description: Task driver plugins extend Nomad functionality to provide resource isolation when executing job tasks. Review the Exec2, Podman, and Virt task driver reference. Explore plugins developed by the Nomad user community.
+---
+
+# Task driver plugins
+
+This section provides reference information for task driver plugins.
+
+@include 'task-driver-intro.mdx'
+
+## Configuration
+
+Refer to individual task driver documentation for agent configuration and job
+specification usage.
+
+## Create task drivers
+
+Nomad's task driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][/nomad/plugins/author/task-driver] for details.
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.10.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..4c366e1b7e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,737 @@
+---
+layout: docs
+page_title: Podman task driver plugin
+description: >-
+  The Podman task driver plugin uses the Pod Manager daemonless container runtime to execute Nomad workload tasks. Learn how to configure and install the Podman task driver plugin. Review capabilities, client requirements, plugin options, and network configuration. Learn how to use the Podman task driver in your Nomad job. Configure image registry authentication, Linux capabilities, host devices, entrypoint, paths, image, labels, logging, memory, network mode, ports, volumes, working directory, and container privileges.
+---
+
+# Podman task driver plugin
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-podman/) and verify the
+binary using the available SHA-256 sums. After downloading nomad-driver-podman
+driver, unzip the package. Make sure that the `nomad-driver-podman` binary is
+available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path,
+specified by the client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install -y nomad-driver-podman
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-podman
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `apparmor_profile` - (Optional) Name of an AppArmor profile to use instead of
+  the default profile. The special value `unconfined` disables AppArmor for this container.
+
+  ```hcl
+  config {
+    apparmor_profile = "your-profile"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting `tls_verify` to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tls_verify = false
+    }
+  }
+  ```
+
+- `auth_soft_fail` - (Optional) Ignore errors returned from auth backend so Podman can fall back to a different auth method.
+
+  ```hcl
+  config {
+    auth_soft_fail = true
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `cpu_hard_limit` (Optional) `true` or `false`. Use hard CPU limiting instead
+  of soft limiting. By default this is `false`, which means Podman uses soft
+  limiting so that containers are able to burst above their CPU limit when there
+  is idle capacity.
+
+- `cpu_cfs_period` - (Optional) Set the CPU period for the [Completely Fair
+  Scheduler (CFS)](https://docs.kernel.org/scheduler/sched-design-CFS.html),
+  which is a duration in microseconds. Refer to [`podman run
+  --cpu-period`](https://docs.podman.io/en/latest/markdown/podman-run.1.html#cpu-period-limit)
+  for details.
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container.
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specified the PID limit for
+  the container.
+
+  ```hcl
+  config {
+    pids_limit = 64
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `security_opt` - (Optional) A list of security-related options that Podman sets
+  in the container.
+
+  ```hcl
+  config {
+    security_opt = [
+      "no-new-privileges"
+    ]
+
+  }
+  ```
+
+- `selinux_opts` - (Optional) A list of process labels that the container uses.
+
+  ```hcl
+  config {
+    selinux_opts = [
+      "type:my_container.process"
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) Set the size of `/dev/shm`. Refer to [`podman run
+  --shm-size](https://docs.podman.io/en/latest/markdown/podman-run.1.html#shm-size-number-unit)
+  for more details.
+
+- `socket` - (Optional) The name of the socket as defined in the socket block in
+  the client agent's plugin configuration. Defaults to the socket named "default".
+
+  ```hcl
+  config {
+    socket = "app1"
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `userns` - (Optional) Ser the user namespace mode for the container.
+
+  ```hcl
+  config {
+    userns = "keep-id:uid=200,gid=210"
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+If you need to configure authorization to an external registry, you can write a
+file containing the details in a location such as
+`/etc/nomad.d/registry/auth.json`:
+```json
+{
+  "auths": {
+    "yourregistry": {
+      "auth": "token"
+    }
+  }
+}
+```
+
+You can then instruct Nomad and the Podman driver to use this information by
+adding the following to the `/etc/nomad.d/nomad.env` file:
+```env
+REGISTRY_AUTH_FILE=/etc/nomad.d/registry/auth.json
+```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/job-declare/task-driver/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/job-declare/task-driver/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: https://docs.podman.io/en/latest/markdown/podman-run.1.html#network-mode-net
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/virt/index.mdx b/content/nomad/v1.10.x/content/plugins/drivers/virt/index.mdx
new file mode 100644
index 0000000000..af6eefdca8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/virt/index.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: Virt task driver plugin
+description: >-
+  The Virt task driver leverages Linux capabilities and runs virtual machines using the libvirt API and hypervisors such as QEMU. Learn about Nomad client requirements, installation, capabilities, and Nomad client node attributes.
+---
+
+# Virt task driver plugin
+
+Name: `virt`
+
+The Virt task driver utilizes the [libvirt][] API to run and manage virtual
+machines using hypervisors such as [QEMU][]. The task driver supports a wide
+variety of Nomad features including [workload identity][], [task templates][],
+and [service discovery][].
+
+@include 'virt-beta-callout.mdx'
+
+## Driver Capabilities
+
+The Virt task driver implements these driver [capabilities][capabilities].
+
+| Feature              | Implementation |
+|----------------------|----------------|
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | host           |
+| volume mounting      | false          |
+
+## Nomad Client Node Attributes
+
+The Virt task driver provides these node attributes that you can use as
+constraints when authoring jobs.
+
+```
+driver.virt                              = true
+driver.virt.active                       = 0
+driver.virt.emulator.version             = 8002002
+driver.virt.inactive                     = 0bytes
+driver.virt.libvirt.version              = 10000000
+driver.virt.network.default.bridge_name  = virbr0
+driver.virt.network.default.state        = active
+```
+
+## Reference
+
+- [Install and configure the Virt task driver][install].
+- [Configure a virt task in your job specification][task-config].
+
+
+[libvirt]: https://libvirt.org/
+[QEMU]: https://www.qemu.org/
+[workload identity]: /nomad/docs/concepts/workload-identity
+[task templates]: /nomad/docs/job-specification/template
+[service discovery]: /nomad/docs/job-networking/service-discovery
+[github]: https://github.com/hashicorp/nomad-driver-virt
+[capabilities]: /nomad/plugins/author/task-driver#task-driver-plugin-api
+[install]: /nomad/plugins/drivers/virt/install
+[task-config]: /nomad/plugins/drivers/virt/task-config
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/virt/install.mdx b/content/nomad/v1.10.x/content/plugins/drivers/virt/install.mdx
new file mode 100644
index 0000000000..baa9ef1849
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/virt/install.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Install the Virt task driver plugin
+description: >-
+  Install and configure the Virt task driver plugin on your Nomad clients. Review manual instructions and those for Ubuntu, Debian, CentOS, and RHEL. Add the Virt task driver plugin to Nomad.
+---
+
+# Install the Virt task driver plugin
+
+The Virt task driver plugin for Linux operating systems is not bundled with
+Nomad. You must install the driver into each Nomad client's [configured plugin
+directory][plugin_dir].
+
+@include 'virt-beta-callout.mdx'
+
+## Prerequisites
+
+Your Nomad client must meet these requirements:
+
+- Run as root.
+- Able to run hardware-accelerated KVM virtual machines. Run the [kvm-ok][]
+  command to verify your client capabilities.
+
+The Virt driver requires the following packages:
+
+- bridge-utils
+- cloudinit
+- dnsmasq
+- iptables
+- [libvirt daemon][]
+- [QEMU][]
+
+## Install the Virt task driver plugin
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+Download a [precompiled binary][releases] and verify the binary using the
+available SHA-256 sums. Unzip the package. Make sure that the
+`nomad-driver-virt` binary is on your
+[plugin_dir] path, specified by the
+client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install -y \
+  wget \
+  gpg \
+  coreutils \
+  bridge-utils \
+  cloud-init \
+  dnsmasq \
+  iptables \
+  libvirt-daemon-system \
+  qemu-system \
+  qemu-system-x86 \
+  qemu-utils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-virt
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-virt
+```
+
+</Tab>
+</Tabs>
+
+## Add the Virt task driver plugin to Nomad
+
+This example shows the default plugin configuration.
+
+```hcl
+plugin "nomad-driver-virt" {
+  config {
+    data_dir     = "/var/lib/virt"
+    image_paths  = ["/var/lib/virt", "${ALLOC_DIR}"]
+
+    emulator {
+      uri      = "qemu:///system"
+      user     = ""
+      password = ""
+    }
+  }
+}
+```
+
+- `data_dir` - (default: `"/var/lib/virt"`) - the directory for storing VM configuration files and
+  intermediate files.
+
+- `image_paths` - (default: `["/var/lib/virt", "${ALLOC_DIR}"]`) - an allow-list of paths the driver
+  is allowed to load an image from.
+
+- `emulator` - (block)
+  - `uri` - (default: `"qemu:///system"`) - The `uri` specifies which hypervisor to connect to.
+  - `user` - (default: `""`) - the username to use for authentication.
+  - `password` - (default: `""`) - the password to use for authentication.
+
+## Next steps
+
+[Learn how to use the Virt task driver in your Nomad job specification][task-config].
+
+[releases]: https://releases.hashicorp.com/nomad-driver-virt
+[kvm-ok]: https://manpages.ubuntu.com/manpages/bionic/man1/kvm-ok.1.html
+[libvirt daemon]: https://libvirt.org/daemons.html
+[QEMU]: https://www.qemu.org/
+[task-config]: /nomad/plugins/drivers/virt/task-config
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
diff --git a/content/nomad/v1.10.x/content/plugins/drivers/virt/task-config.mdx b/content/nomad/v1.10.x/content/plugins/drivers/virt/task-config.mdx
new file mode 100644
index 0000000000..6a496798da
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/drivers/virt/task-config.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: Configure a Virt job task
+description: Learn how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+---
+
+# Configure a Virt job task
+
+This page provides reference information on how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+
+@include 'virt-beta-callout.mdx'
+
+## Parameters
+
+Task configuration for a virt task includes setting an `image` to provide the base VM image as
+well as other parameters required for bootstrapping a VM instance.
+
+- `image` - (string: required) - Path to an `.img` cloud image to base the VM disk on. The image should
+  be located in an allowed path. The cloud image needs to include cloud-init, otherwise certain
+  task features are not available. You may also downloaded via the [artifact block][].
+
+- `use_thin_copy` - (bool: `false`) - Make a thin copy of the image using QEMU, and use it as the
+  backing cloud image for the VM.
+
+- `hostname` - (string: `"nomad-<task-name>"`) - The hostname to assign to the VM. As this value is
+  used as a network host name, it must be a valid DNS label according to RFC 1123. Nomad generates the default
+  value using the Nomad task name.
+
+- `cmds` - (list(string): optional) - List of commands to execute on the VM once it is running.
+  These commands can provide you with a quick way to start a process on the newly created
+  VM. When used in conjunction with the template, this command list can be a powerful start up tool.
+
+- `default_user_password` - (string: `""`) - Initial password for the default user
+  on the newly created VM. When set, the user must update the password on first connect.
+
+- `default_user_authorized_ssh_key` - (string: `""`) - SSH public key  added to the SSH
+  configuration for the default user of the cloud image distribution.
+
+- `user_data` - (string: `""`) - Path to a cloud-init compliant user data file used as the user-data for the cloud-init configuration.
+
+- `primary_disk_size` - (int: required) - Disk space to assign to the VM. Must fit the VM's OS.
+
+Example:
+```hcl
+config {
+  image                           = "local/focal-server-cloudimg-amd64.img"
+  use_thin_copy                   = false
+  hostname                        = ""
+  cmds                            = ["python -m http.server 8000"]
+  #default_user_password          = "CHANGE-ME"
+  default_user_authorized_ssh_key = ""
+  user_data                       = ""
+  primary_disk_size               = 10000
+}
+```
+
+### os
+
+The VM architecture and machine can be different from the client host. When this is the case, you must set the
+`os` block. By default, this information matches the client host where the driver
+plugin is running.
+
+- `arch` - (string: `""`) - The VM architecture.
+
+- `machine` - (string: `""`) - The machine type.
+
+Example:
+```hcl
+config {
+  os {
+    arch    = "x86_64"
+    machine = "pc-i440fx-2.9"
+  }
+}
+```
+
+### network_interface
+
+You need to attach tasks to a libvirt network in order to access the internet and route
+from the local network. The `network_interface` block enables this as a list of network interfaces
+that the driver should attach to the VM. This feature only supports a single entry.
+
+- `bridge` - (block) - Attach the VM to a bridge network. `virbr0`, the default libvirt
+  network, is a bridge network.
+
+  - `name` - The name of the bridge interface to use. This relates to the output from commands
+  such as `virsh net-info`.
+
+  - `ports` - A list of port labels to expose on the host via mapping to the network
+  interface. These labels must exist within the job specification [network block][].
+
+Example:
+```hcl
+config {
+  network_interface {
+    bridge {
+      name  = "virbr0"
+      ports = ["ssh", "http"]
+    }
+  }
+}
+```
+
+## Example configuration
+
+The following job specification displays use of all the configuration options, as well as other
+blocks that are useful when deploying tasks via the virt driver. You need to modify parameters, such as the
+`default_user_authorized_ssh_key`, before use depending on your
+requirements and Nomad setup.
+
+```hcl
+job "virt-example" {
+
+  group "virt-group" {
+
+    network {
+      mode     = "host"
+      port "ssh" {
+        to = 22
+      }
+    }
+
+    task "virt-task" {
+
+      driver = "nomad-driver-virt"
+
+      artifact {
+        source      = "http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img"
+        destination = "local/focal-server-cloudimg-amd64.img"
+        mode        = "file"
+      }
+
+      config {
+        image                           = "local/focal-server-cloudimg-amd64.img"
+        primary_disk_size               = 26000
+        #default_user_password          = "CHANGE-ME"
+        default_user_authorized_ssh_key = "ssh-ed25519 AAAAC3NzaC1lZDI..."
+
+        network_interface {
+          bridge {
+            name  = "virbr0"
+            ports = ["ssh"]
+          }
+        }
+      }
+
+      resources {
+        cores  = 2
+        memory = 4096
+      }
+    }
+  }
+}
+
+```
+
+[artifact block]: https://developer.hashicorp.com/nomad/docs/job-specification/artifact
+[network block]: https://developer.hashicorp.com/nomad/docs/job-specification/network
diff --git a/content/nomad/v1.10.x/content/plugins/index.mdx b/content/nomad/v1.10.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..7cc17ddc0b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/plugins/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Nomad plugins
+description: Plugins extend Nomad's functionality.
+---
+
+# Nomad plugins
+
+Plugins extend Nomad's functionality. Review configuration, installation, usage,
+and reference information for device and task driver plugins that are not
+bundled with Nomad.
+
+Consult the [Plugin authoring guide](/nomad/plugins/author) for details on how
+to create your own device, task driver, and host volume plugins.
+
diff --git a/content/nomad/v1.10.x/content/security.mdx b/content/nomad/v1.10.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.10.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..2ca63b7659
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+You can configure Nomad Autoscaler to use a [Nomad namespace][nomad_namespaces]
+using the agent's [`nomad`][autoscaler_agent_nomad] configuration block. The
+Autoscaler retrieves scaling policies and perform autoscaling only for jobs in
+that namespace. If you use the special wildcard namespace value `*`, the
+Autoscaler agent retrieves scaling policies from all namespaces. A future
+version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+When utilizing the High-Availability feature added in v0.4.0, the ACL policy
+needs to include capabilities that allow the Nomad Autoscaler to obtain and release Nomad variable
+locks. The namespace identifier should match the configured
+[`high_availability.lock_namespace`][autoscaler_ha_lock_namespace] parameter,
+and the path should match the [`high_availability.lock_path`][autoscaler_ha_lock_path]
+parameter.
+
+```hcl
+namespace "default" {
+  variables {
+    path "nomad-autoscaler/lock" {
+      capabilities = ["write"]
+    }
+  }
+}
+```
+
+<Note>
+
+If you are running Nomad Autoscaler Enterprise, add this ACL policy to ensure Nomad Autoscaler Enterprise is able to read the Nomad Enterprise license.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+</Note>
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/docs/govern/namespaces
+[nomad_acls]: /nomad/docs/secure/acl
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
+[autoscaler_ha_lock_namespace]: /nomad/tools/autoscaling/agent/high_availability#lock_namespace
+[autoscaler_ha_lock_path]: /nomad/tools/autoscaling/agent/high_availability#lock_path
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..04f9f34b0a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/high_availability.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/high_availability.mdx
new file mode 100644
index 0000000000..0d8df1ac85
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/high_availability.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: high_availability Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "high_availability" block is used to configure the Nomad Autoscaler agent
+  in high availability (HA) mode. In this mode, multiple agents participate in
+  leadership election, with only the leader conducting autoscaling calculations
+  and actions.
+---
+
+# `high_availability` Block
+
+<Placement groups={['high_availability']} />
+
+The `high_availability` block is used to configure the Nomad Autoscaler agent
+in high availability (HA) mode. In this mode, multiple agents participate in
+leadership election, with only the leader conducting autoscaling calculations
+and actions.
+
+```hcl
+high_availability {
+  enabled        = true
+  lock_namespace = "prod"
+  lock_path      = "custom/lock/path"
+  lock_ttl       = "30s"
+  lock_delay     = "15s"
+}
+```
+
+## `high_availability` Parameters
+
+- `enabled` `(bool: false)` - Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired.
+
+- `lock_namespace` `(string: "default")` - Defines the namespace of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process.
+
+- `lock_path` `(string: "nomad-autoscaler/lock")` - Defines the path of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad Autoscaler
+  agents expected to take part in the same leadership election process.
+
+- `lock_ttl` `(string: "60s")` - Defines the lease period or TTL of the lock used
+  to sync the leader when running in high availability mode. If the Nomad Autoscaler
+  agent does not renew the lock within this period, the lock is considered lost.
+
+- `lock_delay` `(string: "30s")` - Defines the period that the lock will be blocked
+  after the TTL expired without being renewed. This helps prevent split brain
+  situations.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..124dba0a93
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace. If set to `*` all namespaces are queried.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..7dfc60b409
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  the following queues:
+   - `cluster`
+   - `horizontal`
+   - `vertical_mem` <EnterpriseAlert inline/>
+   - `vertical_cpu` <EnterpriseAlert inline/>
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+- `-high-availability-enabled`: Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired. It defaults to `false`.
+
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
+- `-high-availability-lock-path`: Defines the path of the Nomad variable that
+  will be used to sync the leader when running in high availability mode. This
+  parameter needs to be the same on all Nomad Autoscaler agents expected to
+  take part in the same leadership election process. Defaults to
+  `nomad-autoscaler/lock`.
+
+- `-high-availability-lock-ttl`: Defines the lease period or TTL of the lock used
+  to sync the leader when running on high availability mode. If the Nomad
+  Autoscaler agent does not renew the lock within this period, the lock is
+  considered lost. Defaults to `60s`.
+
+- `-high-availability-lock-delay`: Defines the period that the lock will be
+  blocked after the TTL expired without being renewed. This helps prevent split
+  brain situations. Defaults to `30s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..09033669eb
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/concepts/scheduling/schedulers#system
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..d2abb89c94
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..dc2554d004
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..9fdbbead9a
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..d934049925
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered within bounds. This value is always **inclusive**, meaning a
+  metric with the exact same value as `lower_bound` is considered within
+  bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds. This value is always **exclusive**, meaning a
+  metric with the exact same value as `upper_bound` is considered **out** of
+  bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above or
+equal to `lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..4cdbf110b4
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Note that currently Prometheus is the only APM available for dynamic application sizing.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..656fb74905
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+- `retry_attempts` `(int: "15")` - The number of attempts to make while waiting
+  for the cluster to stabilize after a scaling action. It may need to be tuned
+  up if errors such as `failed to ensure all activities completed` occur.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. It may be overridden per policy.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. If set, it overrides the plugin configuration.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_scale_in_protection]: https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..c5960ea9be
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..0d4f106125
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..714d0bb875
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `query_window_offset` - Defines a time offset from the current time to apply
+  to the query window. A short offset (for example, `1m`) can be used to avoid
+  reading unstable and incomplete data from the APM. A long offset (`168h`,
+  representing 7 days ago) can be used for predictive scaling based on past
+  data.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task `policy` options for dynamic application sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.10.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.10.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..52c484463c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.10.x/content/tools/index.mdx b/content/nomad/v1.10.x/content/tools/index.mdx
new file mode 100644
index 0000000000..7c053e8177
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://github.com/bitrockteam/caravan/wiki) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Port Forward](https://github.com/Mongey/nomad-port-forward) - A tool for forwarding ports from a Nomad job to your local machine
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Tools](https://github.com/Kamilcuk/nomad-tools) - Set of tools and utilities to ease interacting with HashiCorp Nomad scheduling solution.
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/advanced-usage.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/advanced-usage.mdx
new file mode 100644
index 0000000000..748c05969e
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/advanced-usage.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: Nomad Pack advanced usage
+description: |-
+  Generate a variables files, render a Nomad Pack, plan a Pack deployment, and
+  manage your local Pack registry.
+---
+
+# Nomad Pack advanced usage
+
+In the [Nomad Pack overview guide][pack-intro] you learned about Nomad Pack, how to deploy applications with it, and how to discover community packs.
+
+In this guide, you will learn about more advanced usage including:
+
+- Generating a variable file
+- Rendering a Pack
+- Advanced `run` options
+- Planning with `plan`
+- Registry management
+
+## Generating a variable file
+
+You can pass in variables to a pack with a variables file.
+
+```shell-session
+$ nomad-pack run hello_world -f ./my-variables.hcl
+```
+
+The `generate var-file` command can generate variable files from a pack.
+
+```shell-session
+$ nomad-pack generate var-file hello_world -o ./my-variables.hcl
+```
+
+You can also use the path to a pack instead of a pack name.
+
+```shell-session
+$ nomad-pack generate var-file ./my-local-pack -o ./my-variables.hcl
+```
+
+## Rendering a Pack
+
+At times, you may wish to use Nomad Pack to render jobspecs, but you will not want to immediately deploy these to Nomad.
+
+This can be useful when writing a pack, debugging deployments, integrating Nomad Pack into a CI/CD environment, or if you have another mechanism for handling Nomad deploys.
+
+The `render` command takes the same `--var` and `--var-file` flags that `run` takes.
+
+The `--to-dir` flag determines the directory where the rendered templates will be written.
+
+You can pass the `--render-output-template` flag to additionally render the output template. Some output templates rely on a deployment for information. In these cases, the output template may not render with all the necessary information.
+
+```shell-session
+$ nomad-pack render hello_world --to-dir ./tmp --var greeting=hola --render-output-template
+```
+
+## Advanced `run` options
+
+To deploy the resources in a pack to Nomad, use the `run` command.
+
+```shell-session
+$ nomad-pack run hello_world
+```
+
+By passing a `--name` value into `run`, Nomad Pack deploys each resource in the
+pack with a metadata value for pack name. If no name is given, the pack name
+is used by default.
+
+This allows Nomad Pack to manage multiple deployments of the same pack.
+
+```shell-session
+$ nomad-pack run hello_world --name hola-mundo
+```
+
+It is also possible to run a local pack directly from the pack directory by passing in the directory instead of the pack name.
+This can be helpful while developing a pack.
+
+```
+nomad pack run .
+```
+
+## Planning with `plan`
+
+If you want see details on how Nomad Pack will deploy a pack but are not ready to immediately deploy the pack, run the `plan` command.
+
+This invokes Nomad in a dry-run mode using the [Nomad Plan](/nomad/api-docs/jobs#create-job-plan) API endpoint.
+
+```
+nomad-pack plan hello_world
+```
+
+Similar to `run`, `plan` takes the `--name` flag to look for packs deployments with that name. Nomad Pack uses the pack name by default.
+
+```
+nomad-pack plan hello_world --name hola-mundo
+```
+
+The `plan` command also takes the `--var` and `-f` flags like the `run` command.
+
+```
+nomad-pack plan hello_world -f ./my-variables.hcl --var greeting=hallo
+```
+
+## Registry management
+
+The [Introduction to Nomad Pack guide][pack-intro] explains the basics of adding to and listing packs in the registry. The following section provides additional details on registry management.
+
+### Initialization and directory structure
+
+The first time you run `list`, Nomad Pack will add a `nomad/packs`
+directory to your desktop user's cache directory—`$XDG_CACHE_DIR` on Linux,
+`~/Library/Caches` on macOS, `%AppData%` on Windows, etc. This folder stores
+information about cloned registries and their available packs.
+
+During initialization, Nomad Pack downloads a default registry of packs from the
+[Nomad Pack community registry][community-registry].
+
+The directory structure is as follows:
+
+```
+parent-directories (see above)
+└── nomad
+    └── packs
+        ├── <REGISTRY>
+            ├── <REGISTRY-TAG>
+                ├── <PACK-NAME@REF>
+                    ├── ...files containing pack contents...
+```
+
+Nomad Pack requires the contents of the pack cache directory to work properly, but you should not manually manage or change these files. Instead, you can use the `registry` commands.
+
+### Adding new registries
+
+The `registry` command includes several sub-commands for interacting with registries.
+
+Add custom registries with the `registry add` command. Any `git` based
+registry supported by [`go-getter`](https://github.com/hashicorp/go-getter) should
+work.
+
+For example, to add the entire [Nomad Pack Community Registry](https://github.com/hashicorp/nomad-pack-community-registry), use the `registry add` command to download the registry.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry
+```
+
+### Adding an individual pack from a registry
+
+To add a single pack from the registry, use the `--target` flag.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry --target=nginx
+```
+
+### Adding a registry at a specific commit
+
+To download a single pack or an entire registry at a specific version/SHA, use the `--ref` flag.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry --ref=v0.0.1
+```
+
+### Removing a registry
+
+To remove a registry or pack from your local cache, use the `registry delete` command.
+This command also supports the `--target` and `--ref` flags.
+
+```shell-session
+$ nomad-pack registry delete community
+```
+
+### Updating a registry
+
+To update a registry, use the `add` command and Nomad Pack will re-download the registry and replace the contents.
+
+```shell-session
+$ nomad-pack registry add default github.com/hashicorp/nomad-pack-community-registry
+```
+
+## Next steps
+
+In this guide you learned how to interact with Nomad Pack in an advanced way. You learned how to generate a variable file, render a pack, use additional `run` options, use the `plan` command, and interact with Nomad Pack registries.
+
+The official and community packs available to Nomad Pack are valuable because it allows you to quickly deploy apps using the best practices and leverage the knowledge of the Nomad community.
+
+To learn how to write your own Nomad Packs or convert your existing Nomad job
+specifications into reusable packs, continue on to the [Creating packs
+guide][writing-packs].
+
+[nomad-site]: /nomad/
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[pack-intro]: /nomad/tools/nomad-pack/
+[writing-packs]: /nomad/tools/nomad-pack/create-packs
+[community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/index.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/index.mdx
new file mode 100644
index 0000000000..e28b9fbf74
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack deps command reference
+description: |-
+  Use the `nomad-pack deps` command to manage dependencies for a Nomad pack.
+---
+
+# nomad-pack deps command reference
+
+Use the `nomad-pack deps` command to manage dependencies for a Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack deps <subcommand> [options]
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/vendor.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/vendor.mdx
new file mode 100644
index 0000000000..71183ed217
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/deps/vendor.mdx
@@ -0,0 +1,34 @@
+---
+layout: commands
+page_title: nomad-pack deps vendor command reference
+description: |-
+  Use the `nomad-pack deps vendor` command to download vendor dependencies for a pack.
+---
+
+# nomad-pack deps vendor command reference
+
+Use the `nomad-pack deps vendor` command to download vendor dependencies for a pack.
+
+## Usage
+
+```plaintext
+nomad-pack deps vendor [options]
+```
+
+## Options
+
+- `--path=<string>`: Full path to the pack that contains vendor dependencies.
+  All the dependencies are then downloaded into a `deps/` subdirectory of that
+  path.
+
+- `--timeout=<int> (default 30)`:  Timeout in seconds for downloading
+  dependencies. Defaults to 30.
+
+## Examples
+
+Download vendor dependencies for a pack in the current directory, with a timeout
+of 180 seconds.
+
+```shell
+nomad-pack deps vendor --timeout=180
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/destroy.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/destroy.mdx
new file mode 100644
index 0000000000..c968d36e50
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/destroy.mdx
@@ -0,0 +1,53 @@
+---
+layout: commands
+page_title: nomad-pack destroy command reference
+description: |-
+  Use the `nomad-pack destroy` command to stop and delete the specified Nomad pack from the configured Nomad cluster.
+---
+
+# nomad-pack destroy command reference
+
+Use the `nomad-pack destroy` command to stop and delete the specified Nomad pack
+from the configured Nomad cluster. This is the same as using the command
+`nomad-pack stop <pack_name> --purge`.
+
+By default, the `nomad-pack destroy` command deletes all jobs in the pack
+deployment. If you ran a pack with var overrides to specify the job name, you
+must provide the var override when destroying the pack to guarantee this command
+targets the correct job in the pack deployment.
+
+## Usage
+
+```plaintext
+nomad-pack destroy <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be
+					destroyed.
+- `-ref=<string>`: Specific Git reference of the pack to destroy.
+					Supports tags, SHA, and latest. If no ref is specified,
+					defaults to latest.	Using `ref` with a file path is not supported.
+- `-global`: Destroy multi-region pack in all its regions. By default,
+					 `destroy` only destroys a single region at a time. Ignored for single-region packs.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Stop an example pack in deployment "dev" and delete it from the cluster.
+
+```shell
+nomad-pack destroy example --name=dev
+```
+
+Stop and delete an example pack in deployment "dev" that has a job named "test".
+If you have installed the same pack in deployment "dev" but override the job
+name to "hello", this command only destroys "test".
+
+```shell
+nomad-pack destroy example --name=dev --var=job_name=test
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/index.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/index.mdx
new file mode 100644
index 0000000000..01fd297ff0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack generate command reference
+description: |-
+  Use the `nomad-pack generate` subcommands to generate a sample registry, pack, or variable overrides file for a Nomad pack.
+---
+
+# nomad-pack generate command reference
+
+Use the `nomad-pack generate` subcommands to generate a sample registry, pack, or variable overrides file for a Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate <subcommand> [options]
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/pack.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/pack.mdx
new file mode 100644
index 0000000000..cc9d11e8d9
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/pack.mdx
@@ -0,0 +1,31 @@
+---
+layout: commands
+page_title: nomad-pack generate pack command reference
+description: |-
+  Use the `nomad-pack generate pack` command to create a new Nomad pack.
+---
+
+# nomad-pack generate pack command reference
+
+Use the `nomad-pack generate pack` command to create a new Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate pack <pack_name>
+```
+
+## Options
+
+- `-to-dir=<string>`: Path to write generated pack to.
+- `-overwrite`: If the output directory is not empty, should we overwrite?
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Create a new pack named "my-new-pack" in the current directory.
+
+```shell
+nomad-pack generate pack my-new-pack
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/registry.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/registry.mdx
new file mode 100644
index 0000000000..1ac19c85ed
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/registry.mdx
@@ -0,0 +1,31 @@
+---
+layout: commands
+page_title: nomad-pack generate registry command reference
+description: |-
+  Use the `nomad-pack generate registry` command to generate a new registry.
+---
+
+# nomad-pack generate registry command reference
+
+Use the `nomad-pack generate registry` command to generate a new registry.
+
+## Usage
+
+```plaintext
+nomad-pack generate registry <name>
+```
+
+## Options
+
+- `-to-dir=<string>`: Path to write generated registry to.
+- `-with-sample-pack`: Generate a sample "hello_world" pack in the registry.
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Create a new registry named "my-new-registry" in the current directory.
+
+```shell
+nomad-pack generate registry my-new-registry
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/var-file.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/var-file.mdx
new file mode 100644
index 0000000000..600e24c950
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/generate/var-file.mdx
@@ -0,0 +1,63 @@
+---
+layout: commands
+page_title: nomad-pack generate var-file command reference
+description: |-
+  Use the `nomad-pack generate registry` command to generate a variable override file for a pack.
+---
+
+# nomad-pack generate var-file command reference
+
+Use the `nomad-pack generate registry` command to generate a variable override file for a pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate var-file <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the target pack. If
+  not specified, the default registry is used.
+- `-ref=<string>`: Specific Git reference of the target pack. Supports tags,
+  SHA, and `@latest`. If you do not specify a reference, the command defaults to
+  `@latest`.	Using `ref` with a file path is not supported.
+- `-to-file=<string>`: Path to write generated variable override file to in
+  addition to	standard output.
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Generate a variables override file for the given pack to standard output.
+
+```shell
+nomad-pack generate var-file example
+```
+
+Generate a variable override for the example pack. Output to a file in
+addition to the terminal.
+
+```shell
+nomad-pack generate var-file example --to-file ./overrides.hcl
+```
+
+Generate a variable override for the `example` pack. Output to a file in
+addition to the terminal. Setting the `auto-approve` option allows the command
+to overwrite existing files.
+
+```shell
+nomad-pack generate var-file example --to-file ./overrides.hcl --auto-approve
+```
+
+Generate a variable override pack under development from the current working directory.
+
+```shell
+nomad-pack generate var-file .
+```
+
+Generate a variable override pack under development from the specified relative path.
+
+```shell
+nomad-pack generate var-file ../../my-pack
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/index.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/index.mdx
new file mode 100644
index 0000000000..7c3641b0b1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/index.mdx
@@ -0,0 +1,14 @@
+---
+layout: docs
+page_title: Nomad Pack command-line interface (CLI) reference
+description: >
+  The Nomad Pack command-line interface (CLI) interacts with the Nomad Pack product. This section contains reference information on how to use the Nomad Pack CLI to generate, register, and list packs.
+---
+
+# Nomad Pack command-line interface (CLI) reference
+
+The Nomad Pack CLI is a well-behaved command-line application. In erroneous
+cases, the CLI returns a non-zero exit status. To view a list of available
+commands, run the `nomad-pack` command with no arguments, `-h`, or `--help`. To
+access help for any specific subcommand, run the subcommand with the `-h`
+argument.
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/info.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/info.mdx
new file mode 100644
index 0000000000..9acb346011
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/info.mdx
@@ -0,0 +1,34 @@
+---
+layout: commands
+page_title: nomad-pack info command reference
+description: |-
+  Use the `nomad-pack info` command to fetch information on the given pack including name, description, and variable details.
+---
+
+# nomad-pack info command reference
+
+Use the `nomad-pack info` command to fetch information on the given pack including name, description, and variable details.
+
+## Usage
+
+```plaintext
+nomad-pack info <pack_name>
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to retrieve
+  info about. If not specified, this command targets the default registry.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info
+  about. Supports tags, SHA, and `@latest`. If you do not specify a reference,
+  the value defaults to `@latest`. Using `ref` with a file path is not supported.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+## Examples
+
+Fetch information on the "hello_world" pack.
+
+```shell
+nomad-pack info hello_world
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/list.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/list.mdx
new file mode 100644
index 0000000000..4da1f386f1
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/list.mdx
@@ -0,0 +1,33 @@
+---
+layout: commands
+page_title: nomad-pack list command reference
+description: |-
+  Use the `nomad-pack list` command to list packs available in the local environment.
+---
+
+# nomad-pack list command reference
+
+Use the `nomad-pack list` command to list packs available in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack list
+```
+
+## Options
+
+- `-registry=<string>`: Registry name to filter packs by.
+- `-ref=<string>`: Registry ref to filter packs by.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+List all available packs.
+
+```shell
+nomad-pack list
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/plan.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/plan.mdx
new file mode 100644
index 0000000000..8b748739d0
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/plan.mdx
@@ -0,0 +1,75 @@
+---
+layout: commands
+page_title: nomad-pack plan command reference
+description: |-
+  Use the `nomad-pack plan` command to perform a dry run that determines the effects of submitting a new or updated Nomad Pack.
+---
+
+# nomad-pack plan command reference
+
+Use the `nomad-pack plan` command to perform a dry run that determines the effects of submitting a new or updated Nomad Pack.
+
+The `nomad-pack plan` command returns one of the following exit codes:
+
+  - `0`:   No objects will be created or destroyed.
+  - `1`:   Objects will be created or destroyed.
+  - `255`: An error occurred determining the plan.
+
+## Usage
+
+```plaintext
+nomad-pack plan <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-diff`: Determines whether to output the diff between the remote job and
+  planned job. Defaults to true.
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+- `-verbose`: Increase diff verbosity.
+- `-exit-code-no-changes=<int>`: Override exit code returned when the plan shown
+  no changes.
+- `-exit-code-makes-changes=<int>`: Override exit code returned when the plan
+  shows changes.
+- `-exit-code-error=<int>`: Override exit code returned when there is an error.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Plan an example pack with the default deployment name.
+
+```shell
+nomad-pack plan example
+```
+
+Plan an example pack at a specific ref.
+
+```shell
+nomad-pack plan example --ref=v0.0.1
+```
+
+Plan a pack from a registry other than the default registry.
+
+```shell
+nomad-pack plan traefik --registry=community --ref=v0.0.1
+```
+
+Plan an example pack without showing the diff.
+
+```shell
+nomad-pack plan example --diff=false
+```
+
+Plan a pack under development from the current filesystem.
+
+```shell
+nomad-pack plan .
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/add.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/add.mdx
new file mode 100644
index 0000000000..a460fa7729
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/add.mdx
@@ -0,0 +1,51 @@
+---
+layout: commands
+page_title: nomad-pack registry add command reference
+description: |-
+  Use the `nomad-pack registry add` command to add registries or packs to the local environment.
+---
+
+# nomad-pack registry add command reference
+
+Use the `nomad-pack registry add` command to add registries or packs to the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry add <name> <source> [options]
+```
+
+## Options
+
+- `-target=<string>`: A specific pack within the registry.
+- `-ref=<string>`: Specific Git reference of the registry or pack. Supports
+tags, SHA, and `latest`. If you do not specify a reference, the command defaults
+to `@latest`. Running `nomad registry add` multiple times for the same ref is
+idempotent. However, running`nomad-pack registry add` without specifying a
+reference or when specifying `@latest` is destructive and overwrites current
+`@latest` in the global cache. Using `ref` with a file path is not supported.
+
+## Examples
+
+Download latest reference of the Nomad Pack registry to the global cache.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry
+```
+
+Download latest reference of a specific pack from the registry to the global cache.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry \
+           --target=nomad_example
+```
+
+Download packs from a registry at a specific tag, release, or SHA.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry \
+           --ref=v0.1.0
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/delete.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/delete.mdx
new file mode 100644
index 0000000000..f5458f1f6f
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: commands
+page_title: nomad-pack registry delete command reference
+description: |-
+  Use the `nomad-pack registry delete` command to delete registries or packs from the local environment.
+---
+
+# nomad-pack registry delete command reference
+
+Use the `nomad-pack registry delete` command to delete registries or packs from the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry delete <name> [options]
+```
+
+## Options
+
+- `-target=<string>`: A specific pack within the registry. If you add a
+  reference flag, the command only deletes that reference of the target pack.
+- `-ref=<string>`: Specific Git reference of the registry or pack. Supports
+  tags, SHA, and `@latest`. If you do not specify a reference, the command defaults to `@latest`. Using `ref` with a file path is not supported.
+
+<Warning>
+
+If you do not specify `target` or `ref`, this command deletes the entire
+specified registry.
+
+</Warning>
+
+## Examples
+
+Delete the Traefik pack with tag `v0.0.1` from your local `community` registry.
+
+```shell
+nomad-pack registry delete community --target=traefik --ref=v0.0.1
+```
+
+Delete the `community` registry from the local environment.
+
+```shell
+nomad-pack registry delete community
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/index.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/index.mdx
new file mode 100644
index 0000000000..1ddc10e238
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack registry command reference
+description: |-
+  Use the ` nomad-pack registry` subcommands to add, delete, or list registries and packs in the local environment.
+---
+
+# nomad-pack registry command reference
+
+Use the `nomad-pack registry` subcommands to add, delete, or list registries and packs in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry <subcommand> [options]
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/list.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/list.mdx
new file mode 100644
index 0000000000..416566f7bf
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/registry/list.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack registry list command reference
+description: |-
+  Use the `nomad-pack registry list` command to list registries configured in the local environment.
+---
+
+# nomad-pack registry list command reference
+
+Use the `nomad-pack registry list` command to list registries configured in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry list
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/render.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/render.mdx
new file mode 100644
index 0000000000..3333892df6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/render.mdx
@@ -0,0 +1,71 @@
+---
+layout: commands
+page_title: nomad-pack render command reference
+description: |-
+  Use the `nomad-pack render` command to render the specified Nomad Pack and review the results.
+---
+
+# nomad-pack render command reference
+
+Use the `nomad-pack render` command to render the specified Nomad Pack and review the results.
+
+## Usage
+
+```plaintext
+nomad-pack render <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack. If not
+  specified, the default registry is used.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-render-output-template`: Controls whether or not to render and display the
+  output template file within the pack.
+- `-skip-aux-files`: Controls whether or not the rendered output contains
+  auxiliary	files found in the `templates` folder.
+- `-no-format`: Controls whether or not to format templates before outputting.
+- `-to-dir=<string>`: Path to write rendered job files to in addition to
+  standard output.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Render an example pack with override variables in a variable file.
+
+```shell
+nomad-pack render example --var-file="./overrides.hcl"
+```
+
+Render an example pack with CLI variable overrides.
+
+```shell
+nomad-pack render example --var="redis_image_version=latest" \
+           --var="redis_resources={"cpu": "1000", "memory": "512"}"
+```
+
+Render an example pack including the outputs template file.
+
+```shell
+nomad-pack render example --render-output-template
+```
+
+Render an example pack, outputting the rendered templates to file in
+addition to the terminal. Setting `auto-approve` allows the command to
+overwrite existing files.
+
+```shell
+nomad-pack render example --to-dir ~/out --auto-approve
+```
+
+Render a pack under development from the filesystem. Supports current
+working directory or relative path.
+
+```shell
+nomad-pack render .
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/run.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/run.mdx
new file mode 100644
index 0000000000..b9bfcb33d3
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/run.mdx
@@ -0,0 +1,85 @@
+---
+layout: commands
+page_title: nomad-pack run command reference
+description: |-
+  Use the `nomad-pack run` command to install the specified Nomad Pack to a configured Nomad cluster.
+---
+
+# nomad-pack run command reference
+
+Use the `nomad-pack run` command to install the specified Nomad Pack to a configured Nomad cluster.
+
+## Usage
+
+```plaintext
+nomad-pack run <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be run.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-check-index=<uint>`: If set, the job is only registered or updated if the
+  passed job modify index matches the server side version. If you pass a value
+  of zero, the job is only registered if it does not yet exist.  Passing a
+  non-zero value ensures that the job is being updated from a known state. The
+  use of this flag is most common in conjunction with `nomad job plan` command.
+- `-consul-token=<string>`: If set, the passed Consul token is stored in the job
+  before	sending to the Nomad servers. This allows passing the Consul token
+  without storing it in the job file. This overrides the token found in the
+  $CONSUL_HTTP_TOKEN environment variable	and that found in the job.
+- `-consul-namespace=<string>`: If set, any services in the job are registered
+  into the	specified Consul namespace. Any template block reading from Consul
+  KV are scoped to the the specified Consul	namespace. If Consul ACLs are
+  enabled and the	`allow_unauthenticated` Nomad server Consul configuration is
+  not enabled, then you must supply a Consul token with appropriate service and
+  KV Consul ACL policy permissions.
+- `-vault-token=<string>`: If set, the passed Vault token is stored in the job
+  before	sending to the Nomad servers. This allows passing the Vault token
+  without storing it in the job file. This overrides the token found in the
+  $VAULT_TOKEN environment variable and that found in the job.
+- `-vault-namespace=<string>`: If set, the passed Vault namespace is stored in
+  the job before sending to the Nomad servers.
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+- `-preserve-counts`: If set, the existing task group count is preserved when
+  updating a job.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Run an example pack with the default deployment name "example".
+
+```shell
+nomad-pack run example
+```
+
+Run an example pack with the specified deployment name "dev".
+
+```shell
+nomad-pack run example --name=dev
+```
+
+Run an example pack with override variables in a variable file.
+
+```shell
+nomad-pack run example --var-file="./overrides.hcl"
+```
+
+Run an example pack with CLI variable overrides.
+
+```shell
+nomad-pack run example --var="redis_image_version=latest" \
+           --var="redis_resources={"cpu": "1000", "memory": "512"}"
+```
+
+Run a pack under development from the current filesystem.
+
+```shell
+nomad-pack run .
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/status.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/status.mdx
new file mode 100644
index 0000000000..4a2df0a1c5
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/status.mdx
@@ -0,0 +1,62 @@
+---
+layout: commands
+page_title: nomad-pack status command reference
+description: |-
+  Use the `nomad-pack status` command to fetch information on deployed Nomad packs.
+---
+
+# nomad-pack status command reference
+
+Use the `nomad-pack status` command to fetch information on deployed Nomad packs.
+
+## Usage
+
+```plaintext
+nomad-pack status <pack_name> [options]
+```
+
+If you do not specify a pack name, the `nomad-pack status` command returns	a
+list of all deployed packs. If you do specify a pack name, this command returns
+a list of all deployed jobs belonging to that pack, along with their status and
+deployment names.
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to inspect.If
+  not specified, the command uses the default registry.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+# Examples
+
+Get a list of all deployed packs and their registries.
+
+```shell
+nomad-pack status
+```
+
+Get a list of all deployed jobs in pack example, along with their status
+and deployment names.
+
+```shell
+nomad-pack status example
+```
+
+Get a list of all deployed jobs and their status for an example pack in
+the deployment name "dev".
+
+```shell
+nomad-pack status example --name=dev
+```
+
+Get a list of all deployed jobs and their status for an example pack in
+the deployment name "dev".
+
+```shell
+nomad-pack status example --name=dev --registry=community
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/stop.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/stop.mdx
new file mode 100644
index 0000000000..5dbf99c55c
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/stop.mdx
@@ -0,0 +1,63 @@
+---
+layout: commands
+page_title: nomad-pack stop command reference
+description: |-
+  Use the `nomad-pack stop` command to stop the specified Nomad Pack in the configured Nomad cluster.
+---
+
+# nomad-pack stop command reference
+
+Use the `nomad-pack stop` command to stop the specified Nomad Pack in the configured Nomad cluster.
+
+By default, the `stop` command stops all jobs in the pack deployment. If you ran
+a pack with variable overrides to specify the job name, you must provide the
+same variable overrides when stopping the pack to guarantee that this command
+targets the correct job in the pack deployment.
+
+## Usage
+
+```plaintext
+nomad-pack stop <pack_name> [options]
+```
+
+To delete the pack from the cluster, specify `--purge`, or use the [`nomad-pack
+destroy` command](/nomad/tools/nomad-pack/commands/destroy).
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be
+  stopped.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-purge`: Purge is used to stop a pack and purge it from the system.	If not
+  set, you can still query the pack until the garbage collector purges the pack.
+- `-global`: Stop a multi-region pack in all its regions. By default, `pack
+  stop` only stops a single region at a time. Ignored for	single-region jobs.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Stop an example pack in deployment "dev".
+
+```shell
+nomad-pack stop example --name=dev
+```
+
+Stop the `example` pack in deployment "dev" and purge it from the system.
+
+```shell
+nomad-pack stop example --name=dev --purge
+```
+
+Stop an example pack in deployment "dev" that has a job named "test"
+If the same pack has been installed in deployment "dev" but overriding the
+job name to "hello", only "test" is stopped.
+
+```shell
+nomad-pack stop example --name=dev --var=job_name=test
+```
+
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/commands/version.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/version.mdx
new file mode 100644
index 0000000000..a525d97b2b
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/commands/version.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack version command reference
+description: |-
+  Use `nomad-pack version` to return the Nomad Pack version.
+---
+
+# nomad-pack stop command reference
+
+Use `nomad-pack version` to return the Nomad Pack version.
+
+## Usage
+
+```plaintext
+nomad-pack version
+```
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/create-packs.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/create-packs.mdx
new file mode 100644
index 0000000000..37d588e144
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/create-packs.mdx
@@ -0,0 +1,456 @@
+---
+layout: docs
+page_title: Create custom packs
+description: |-
+  Create a custom Nomad Pack registry, add a pack, create a template, publish the registry, and deploy a custom pack from your custom registry.
+---
+
+# Create custom packs
+
+This guide will walk you through the steps involved in writing your own packs and registries for [Nomad Pack][pack-repo].
+
+In this guide, you will learn:
+
+- how packs and pack registries are structured
+- how to write a custom pack
+- how to test your pack locally
+- how to deploy a custom pack
+
+## Create a custom registry
+
+First, you need to create a pack registry. This will be a repository that provides the structure, templates,
+and metadata that define your custom packs.
+
+To get started, use the `generate` command to create a new registry. Then, move into the directory of the registry.
+
+```shell-session
+$ nomad-pack generate registry my_nomad_packs
+$ cd my_nomad_packs/
+```
+
+Each registry should have a `README.md` file that describes the packs in it, and top-level directories
+for each pack. Conventionally, the directory name matches the pack name.
+
+The top level of a pack registry looks like the following:
+
+```plaintext
+.
+└── README.md
+└── CHANGELOG.md
+└── packs
+    └── <PACK-NAME-A>
+        └── ...pack contents...
+    └── <PACK-NAME-B>
+        └── ...pack contents...
+    └── ...packs...
+```
+
+## Add a new pack
+
+To add a new pack to your registry, create a new directory in the `packs` subdirectory.
+
+```shell-session
+$ mkdir -p packs/hello_pack && cd packs/hello_pack/
+```
+
+The directory should have the following contents:
+
+- A `README.md` file containing a human-readable description of the pack, often including any dependency information.
+- A `metadata.hcl` file containing information about the pack.
+- A `variables.hcl` file that defines the variables in a pack.
+- An optional, but _highly encouraged_ `CHANGELOG.md` file that lists changes for each version of the pack.
+- An optional `outputs.tpl` file that defines an output to be printed when a pack is deployed.
+- A `templates` subdirectory containing the HCL templates used to render one or more Nomad job specifications.
+
+To streamline pack creation, you can use the `generate pack` command to scaffold the above files with boilerplate and example data:
+
+```shell-session
+$ nomad-pack generate pack hello_pack
+Creating "hello_pack" Pack in "."...
+```
+
+Next, you will create each of these files for your custom pack.
+
+#### metadata.hcl
+
+The `metadata.hcl` file contains important key value information about the pack. It contains the following blocks and their associated fields:
+
+- `app` - Information about the application that the pack deploys
+  - `url` - The HTTP(S) URL of the homepage of the application. This attribute can also be used to provide a reference to the documentation and help pages.
+- `pack` - Metadata about the pack itself
+  - `name` - The name of the pack.
+  - `description` - A small overview of the application that is deployed by the pack.
+  - `version` - The version of the pack.
+- `dependency` - The dependencies that the pack has on other packs. Multiple dependencies can be supplied.
+  - `alias` - Name to refer to this specific dependency instance. Helpful when importing multiple versions of the same dependency.
+  - `source` - The source URL for this dependency. Dependencies with different names can refer to the same source pack.
+
+Add a `metadata.hcl` file with the following contents:
+
+
+<CodeBlockConfig filename="metadata.hcl">
+
+
+```hcl
+  app {
+    url = "https://learn.hashicorp.com/tutorials/nomad/nomad-pack-writing-packs"
+  }
+
+  pack {
+    name = "hello_pack"
+    description = "This is an example pack created to learn about Nomad Pack"
+    version = "0.0.1"
+  }
+```
+
+</CodeBlockConfig>
+
+#### variables.hcl
+
+The `variables.hcl` file defines the variables required to fully render and deploy all the templates found within the "templates" directory.
+
+Add a `variables.hcl` file with the following contents:
+
+<CodeBlockConfig filename="variables.hcl">
+
+
+```hcl
+variable "datacenters" {
+  description = "A list of datacenters in the region which are eligible for task placement."
+  type        = list(string)
+  default     = ["dc1"]
+}
+
+variable "region" {
+  description = "The region where the job should be placed."
+  type        = string
+  default     = "global"
+}
+
+variable "app_count" {
+  description = "The number of instances to deploy"
+  type        = number
+  default     = 3
+}
+
+variable "resources" {
+  description = "The resource to assign to the application."
+  type = object({
+    cpu    = number
+    memory = number
+  })
+  default = {
+    cpu    = 500,
+    memory = 256
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### outputs.tpl
+
+The `outputs.tpl` is an optional file that defines an output to be printed when a pack is deployed.
+
+Output files have access to the pack variables defined in `variables.hcl`, metadata, and any
+helper templates (see below). A simple example:
+
+```
+Congrats on deploying [[ meta "pack.name" . ]].
+
+There are [[ var "count" . ]] instances of your job now running on Nomad.
+```
+
+#### README and CHANGELOG
+
+No specific format is required for the `README.md` or `CHANGELOG.md` files.
+
+Create a simple `README.md` and empty `CHANGELOG.md` for now:
+
+```shell-session
+$ touch CHANGELOG && echo "#Hello Packs" >> README.md
+```
+
+## Write the templates
+
+Each file at the top level of the `templates` directory that uses the extension ".nomad.tpl" defines a resource (such as a job) that will be applied to Nomad. These files can use any UTF-8 encoded prefix as the name.
+
+Helper templates, which can be included within larger templates, have names prefixed with an underscore “\_” and use a ".tpl" extension.
+
+In a deployment, Nomad Pack will render each job template using the variables provided and apply it to Nomad.
+
+Nomad Pack will render any files ending in `.tpl` but without `.nomad` when calling the `render` command. This can be useful for templatizing configuration files for other non-jobspec files for a job. Nomad Pack will not do anything with these files other than render them.
+
+#### Template basics
+
+Templates are written using [Go Template Syntax](/nomad/docs/reference/go-template-syntax). This enables templates to have complex logic where necessary.
+
+Unlike default Go Template syntax, Nomad Pack uses `"[["` and `"]]"` as delimiters.
+
+Go ahead make your first template at `./templates/hello_pack.nomad.tpl` with the content below. This defines
+a job called "hello_pack" and allows you to provide variable values for `region`, `datacenters`,
+`app_count`, and `resources`.
+
+<CodeBlockConfig filename="hello_pack.nomad.tpl">
+
+```hcl
+job "hello_pack" {
+  type   = "service"
+  region = "[[ var "region" . ]]"
+  datacenters = [ [[ range $idx, $dc := (var "datacenters" .) ]][[if $idx]],[[end]][[ $dc | quote ]][[ end ]] ]
+
+  group "app" {
+    count = [[ var "count" . ]]
+
+    network {
+      port "http" {
+        static = 80
+      }
+    }
+
+    [[/* this is a go template comment */]]
+
+    task "server" {
+      driver = "docker"
+      config {
+        image        = "mnomitch/hello_world_server"
+        network_mode = "host"
+        ports        = ["http"]
+      }
+
+      resources {
+        cpu    = [[ var "resources.cpu" . ]]
+        memory = [[ var "resources.memory" . ]]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `datacenters` value shows a more complex usage of the Go Template, which allows for
+[control structures](/nomad/docs/reference/go-template-syntax#control-structure-list) like `range`
+and [pipelines](/nomad/docs/reference/go-template-syntax#pipelines).
+
+<Note>
+
+A simpler (but less informative) option of `datacenters = [[ var "datacenters" . | toStringList ]]`
+is possible as well.
+
+</Note>
+
+#### Template functions
+
+The [`masterminds/sprig`](https://github.com/Masterminds/sprig) library supplements the standard Go Template set of template functions. This adds helper functions for various use cases such as string manipulation, cryptography, and data conversion (for instance to and from JSON).
+
+Custom Nomad-specific and debugging functions are also provided:
+
+- `nomadRegions` returns the API object from `/v1/regions`.
+- `nomadNamespaces` returns the API object from `/v1/namespaces`.
+- `nomadNamespace` takes a single string parameter of a namespace ID which will be read via `/v1/namespace/:namespace`.
+- `spewDump` dumps the entirety of the passed object as a string. The output includes the content types and values. This uses the `spew.SDump` function.
+- `spewPrintf` dumps the supplied arguments into a string according to the supplied format. This uses the `spew.Printf` function.
+- `fileContents` takes an argument to a file of the local host, reads its contents and provides this as a string.
+
+A custom function within a template is called like any other:
+
+```
+[[ nomadRegions ]]
+[[ nomadRegions | spewDump ]]
+```
+
+You will not use any of the helper functions in this tutorial, but they are available to help you write custom packs in the future.
+
+#### Helper templates
+
+For more complex packs, you may want to reuse template snippets across multiple resources.
+
+For instance, suppose you have two jobs defined in your pack and both jobs reuse
+the same `region` logic. You can create a helper template to centralize that
+logic.
+
+Helper template names are prepended with an underscore `_` and end in `.tpl`.
+
+Go ahead and define your first helper template at `./templates/_region.tpl`.
+
+<CodeBlockConfig filename="_region.tp">
+
+```hcl
+[[ define "region" -]]
+[[- if var "region" . -]]
+  region = [[ (var "region" .) | quote ]]
+[[- end -]]
+[[- end -]]
+```
+
+</CodeBlockConfig>
+
+This template will only specify the "region" value on the job if the `region` variable
+has been passed into Nomad Pack.
+
+You can now use this helper template in your job file.
+
+<CodeBlockConfig filename="hello_pack.nomad.tpl">
+
+```hcl
+job "hello_pack" {
+  type = "service"
+
+  [[ template "region" . ]]
+
+  datacenters = [[ var "datacenters" . | toStringList ]]
+
+  ...
+}
+```
+
+</CodeBlockConfig>
+
+If this pack defined multiple jobs, this logic could now be reused throughout the pack.
+
+#### Conditional jobs
+
+Some packs will have multiple jobs, and occasionally some of these jobs should only be run
+if certain variable values are provided.
+
+If a template is empty, Nomad Pack will not run any job. This allows for conditional jobs:
+
+```hcl
+[[ if var "use-own-database" . ]]
+job "postgres" {
+  ...
+}
+[[ end ]]
+```
+
+#### Pack dependencies
+
+Packs can depend on content from other packs.
+
+You must place copies of dependent packs into the `deps` directory. This process is known as vendoring. The file structure for dependent packs looks like the following:
+
+```plaintext
+<PACK-A>
+  └── ...Pack A's contents...
+  └── deps
+    └── <PACK-B>
+      └── ...Pack B's contents...
+```
+
+This allows Pack A to use any helper templates defined in Pack B, and Pack A will
+automatically deploy any jobs defined in Pack B when it deploys.
+
+In addition to the filesystem, packs must define their dependencies in `metadata.hcl`.
+An example pack block with a dependency looks like the following.
+
+<CodeBlockConfig filename="metadata.hcl" lineNumbers highlight="11-14">
+
+```hcl
+app {
+  url    = "https://some-url-for-the-application.dev"
+}
+
+pack {
+  name        = "hello_pack_with_deps"
+  description = "This pack contains a simple service job, and depends on another pack."
+  version     = "0.2.1"
+}
+
+dependency "demo_dep" {
+  source = "git::https://github.com/org-name/repo-name.git//packs/demo_dep"
+}
+```
+
+</CodeBlockConfig>
+
+Nomad Pack provides a helper command to take packs defined as dependencies and vendor them.
+Running this command from a pack's root directory will download the files associated with any
+pack dependency and put them in the `deps` directory.
+
+```shell-session
+$ nomad-pack deps vendor
+```
+
+<Note>
+
+While developing a dependent pack alongside a parent pack, it can be helpful to symlink
+a reference to the dependent pack in the `deps` directory.
+
+</Note>
+
+This allows templates of `hello_pack_with_deps` to use `demo_dep`'s helper templates, and deploy
+any jobs in demo_dep when running `hello_pack_with_deps`.
+
+```hcl
+[[ template "helper_data" . ]]
+```
+
+You can pass in variables for a dependent pack with a reference to their name or alias value.
+
+```shell-session
+$ nomad-pack run hello_pack_with_deps --var demo_dep.message="example"
+```
+
+## Testing your pack
+
+As you write packs, you may want to test them. To do this, pass the
+directory path as the name of the pack to the `run`, `plan`, `render`, `info`,
+`stop`, or `destroy` commands. Relative paths are supported.
+
+```shell-session
+$ nomad-pack info .
+```
+
+```shell-session
+$ nomad-pack render .
+```
+
+```shell-session
+$ nomad-pack run .
+```
+
+## Publish and find your custom repository
+
+To use and share your new pack, push the git repository to a URL
+accessible by your command line tool. In this demo you will push to a GitHub repository.
+
+If you wish to share your packs with the Nomad community, please consider adding them to the
+[Nomad Pack Community Registry][nomad-pack-community-registry].
+
+## Deploy your custom pack from a custom registry
+
+If you have added your own registry to GitHub, add it to your local Nomad Pack using the
+`nomad-pack registry add` command.
+
+```shell-session
+$ nomad-pack registry add my_packs git@github.com/<YOUR_ORG>/<YOUR_REPO>
+```
+
+This will download the packs defined in the GitHub repository to your local
+filesystem. They will be found using the registry value "my_packs".
+
+Deploy your custom pack.
+
+```shell-session
+$ nomad-pack run hello_pack --var app_count=1 --registry=my_packs
+```
+
+## Next steps
+
+In this tutorial you learned:
+
+- how packs and pack registries are structured
+- how to write a custom pack
+- how to test your pack locally
+- how to deploy a custom pack
+
+As you write packs, consider contributing them to the [Nomad Pack Community Registry][nomad-pack-community-registry].
+This is a great source of feedback, best-practices, and shared-knowledge.
+
+To help speed up your pack development and testing, check out the [Setup HashiCorp Nomad Pack][nomad-pack-github-action] GitHub Action - it takes care of setting up the Nomad Pack binary and making it available to your GitHub Actions workflow.
+
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[example-nomad-pack-registry]: https://github.com/hashicorp/example-nomad-pack-registry
+[nomad-pack-community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
+[nomad-pack-github-action]: https://github.com/marketplace/actions/setup-hashicorp-nomad-pack
diff --git a/content/nomad/v1.10.x/content/tools/nomad-pack/index.mdx b/content/nomad/v1.10.x/content/tools/nomad-pack/index.mdx
new file mode 100644
index 0000000000..5a05f4c9f6
--- /dev/null
+++ b/content/nomad/v1.10.x/content/tools/nomad-pack/index.mdx
@@ -0,0 +1,268 @@
+---
+layout: docs
+page_title: Nomad Pack
+description: |-
+  Discover what Nomad Pack does, how it helps speed up deployment, and deploy an
+  application to Nomad using Nomad Pack.
+---
+
+# Nomad Pack
+
+This guide will walk you through basic usage of [Nomad Pack][pack-repo], a
+package manager and templating tool for Nomad.
+
+By the end of this guide, you will know what Nomad Pack does, be able to deploy
+applications to Nomad using Nomad Pack, and discover packs built by the Nomad community.
+
+## What is Nomad Pack?
+
+Nomad Pack is a templating and packaging tool used with [HashiCorp Nomad][nomad-site].
+
+Nomad Pack is used to:
+
+- Easily deploy popular applications to Nomad
+- Re-use common patterns across internal applications
+- Find and share job specifications with the Nomad community
+
+Nomad Pack can be thought of as a templating and deployment tool like [Levant](https://github.com/hashicorp/levant)
+with the ability to pull from remote registries and deploy multiple resources together, like [Helm](https://helm.sh/).
+
+## Requirements
+
+- A Nomad cluster available
+- Nomad cluster address defined in the `NOMAD_ADDR` environment variable.
+
+<Note>
+
+ If Nomad ACLs are enabled, a token with proper permissions must be defined in the `NOMAD_TOKEN` environment variable.
+
+</Note>
+
+## Installing Nomad Pack
+
+To use Nomad Pack, download the binary for your system from [HashiCorp Releases][releases].
+
+After downloading Nomad Pack, unzip the package, and make sure that the `nomad-pack` binary is available on your PATH.
+
+Alternatively, you can install it with Homebrew if you are on MacOS.
+
+```shell-session
+$ brew tap hashicorp/tap
+$ brew install hashicorp/tap/nomad-pack
+```
+
+You can now run `nomad-pack`.
+
+## Basic use
+
+To get started, run the `list` command to see which packs are available to deploy.
+
+```shell-session
+$ nomad-pack list
+          PACK NAME          | METADATA VERSION |                  REGISTRY NAME
+-----------------------------+------------------+---------------------------------------------------
+  alertmanager               | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  aws_ebs_csi                | 0.1.0            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  aws_efs_csi                | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  backstage                  | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  boundary                   | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  caddy                      | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  ceph                       | 0.1.0            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  [...]
+```
+
+The first time you run the `list` command, Nomad Pack will add a `nomad/packs`
+directory to your desktop user's cache directory—`$XDG_CACHE_DIR` on Linux,
+`~/Library/Caches` on macOS, `%AppData%` on Windows, etc. This folder stores
+information about cloned registries and their available packs.
+
+During initializing, Nomad Pack downloads a default registry of packs from the
+[Nomad Pack community registry][community-registry].
+
+To deploy one of these packs, use the `run` command. This deploys each job defined in the pack to Nomad.
+To deploy the `hello_world` pack, you would run the following command:
+
+```shell-session
+$ nomad-pack run hello_world
+
+  Evaluation ID: 67835384-763b-62b0-7c41-eb98a5417e9c
+  Job 'hello_world' in pack deployment 'hello_world@latest' registered successfully
+Pack successfully deployed. Use --name=hello_world@latest to manage this this deployed instance with run, plan, or destroy
+
+Congrats! You deployed a simple service on Nomad.
+```
+
+<Note>
+
+The syntax for Nomad Pack is different in version 0.1. To run packs written with the old syntax, provide the `--parser-v1` flag.
+
+</Note>
+
+Each pack defines a set of variables that can be provided by the user. To get information on the pack
+and to see which variables can be passed in, run the `info` command.
+
+```shell-session
+$ nomad-pack info hello_world
+
+Pack Name          hello_world
+Description        This deploys a simple application as a service with an optional associated consul service.
+Application URL    https://learn.hashicorp.com/tutorials/nomad/get-started-run?in=nomad/get-started
+Application Author HashiCorp
+
+Pack "hello_world" Variables:
+  - "message" (string) - The message your application will render
+  - "register_consul_service" (bool) - If you want to register a consul service for the job
+  - "consul_service_name" (string) - The consul service name for the hello-world application
+  - "consul_service_tags" (list of string) - The consul service name for the hello-world application
+  - "job_name" (string) - The name to use as the job name which overrides using the pack name
+  - "region" (string) - The region where jobs will be deployed
+  - "datacenters" (list of string) - A list of datacenters in the region which are eligible for task placement
+  - "count" (number) - The number of app instances to deploy
+```
+
+Values for these variables are provided using the `--var` flag. Update your pack using
+the following command:
+
+```shell-session
+$ nomad-pack run hello_world --var message=hola
+```
+
+Values can also be provided by passing in a variables file with the `-f` flag.
+
+```shell-session
+$ tee -a ./my-variables.hcl << END
+message=bonjour
+END
+```
+
+```shell-session
+$ nomad-pack run hello_world -f ./my-variables.hcl
+```
+
+To see a list of deployed packs, run the `status` command
+
+```shell-session
+$ nomad-pack status
+
+   PACK NAME  | REGISTRY NAME
+--------------+----------------
+  hello_world | default
+
+```
+
+To see the status of the jobs deployed by a pack, run the `status` command with the pack name.
+
+```shell-session
+$ nomad-pack status hello_world
+
+   PACK NAME  | REGISTRY NAME |  DEPLOYMENT NAME   |  JOB NAME   | STATUS
+--------------+---------------+--------------------+-------------+----------
+  hello_world | default       | hello_world@latest | hello_world | pending
+
+```
+
+To remove all the resources deployed by a pack, run the `destroy` command with the
+pack name.
+
+```shell-session
+$ nomad-pack destroy hello_world
+```
+
+To stop the jobs without removing them from Nomad, use the `stop` command:
+
+```shell-session
+$ nomad-pack stop hello_world
+```
+
+### Adding non-default Pack registries
+
+When using Nomad Pack, the default registry for packs is
+[the Nomad Pack Community Registry][community-registry].
+Packs from this registry will be made automatically available.
+
+You can add more registries by using the `registry add` command. For instance, if you want to add a registry from GitLab with the alias `my_packs`, you can run the following command to download the registry and its contents.
+
+```shell-session
+$ nomad-pack registry add my_packs gitlab.com/mikenomitch/pack-registry
+```
+
+<CodeBlockConfig hideClipboard>
+
+```shell-session
+go-getter URL is gitlab.com/mikenomitch/pack-registry
+Registry successfully cloned at /Users/arusso/Library/Caches/nomad/packs/nomad-pack-tmp
+Processing pack entries at /Users/arusso/Library/Caches/nomad/packs/nomad-pack-tmp
+found pack entry fabio
+Processing pack fabio@latest
+Updating pack
+Removing previous latest
+Writing pack to /Users/arusso/Library/Caches/nomad/packs/my_packs/fabio@latest
+Loading cloned pack from /Users/arusso/Library/Caches/nomad/packs/my_packs/fabio@latest
+Calculating SHA for latest
+found pack entry grafana
+Processing pack grafana@latest
+Updating pack
+Removing previous latest
+Writing pack to /Users/arusso/Library/Caches/nomad/packs/my_packs/grafana@latest
+Loading cloned pack from /Users/arusso/Library/Caches/nomad/packs/my_packs/grafana@latest
+Calculating SHA for latest
+[...]
+  Try running one the packs you just added liked this
+
+    nomad-pack run fabio --registry=my_packs --ref=latest
+```
+
+</CodeBlockConfig>
+
+To view the available registries, including yours, run the `registry list` command.
+
+```shell-session
+$ nomad-pack registry list
+  REGISTRY NAME |  REF   | LOCAL REF |                    REGISTRY URL
+----------------+--------+-----------+-----------------------------------------------------
+  default       | latest | 6bac78a9  | github.com/hashicorp/nomad-pack-community-registry
+  my_packs      | latest | 7ca313c7  | gitlab.com/mikenomitch/pack-registry
+```
+
+To view the available packs, including yours, run the `list` command.
+
+```shell-session
+$ nomad-pack list
+[...]
+  fabio                      | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  grafana                    | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  haproxy                    | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  hello_world                | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  loki                       | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  nginx                      | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  nomad_autoscaler           | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  traefik                    | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+```
+
+You can deploy packs from this registry with the `run` command and the alias given
+to the registry, in this case `my_packs`.
+
+```shell-session
+$ nomad-pack run nginx --registry=my_packs
+  Evaluation ID: aaa3c319-1928-7c35-54b0-2358841c0e96
+  Job 'nginx' in pack deployment 'nginx@latest' registered successfully
+Pack successfully deployed. Use nginx with --ref=latest to manage this this deployed instance with plan, stop, destroy, or info
+
+Nginx successfully deployed.
+
+See the Load Balancing with Nginx tutorial for more information:
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx
+```
+
+## Next steps
+
+In this tutorial you learned what Nomad Pack does, how to deploy applications to Nomad
+using Nomad Pack, and how to discover packs built by the Nomad community.
+
+Continue on to the [Usage guide][detailed-usage] for more detailed information about how to use Nomad Pack.
+
+[nomad-site]: /nomad/
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[detailed-usage]: /nomad/tools/nomad-pack/advanced-usage
+[community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
+[releases]: https://releases.hashicorp.com/nomad-pack
diff --git a/content/nomad/v1.10.x/data/api-docs-nav-data.json b/content/nomad/v1.10.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..5b78b65f4e
--- /dev/null
+++ b/content/nomad/v1.10.x/data/api-docs-nav-data.json
@@ -0,0 +1,240 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      },
+      {
+        "title": "Upgrade Check",
+        "path": "operator/upgrade-check"
+      },
+      {
+        "title": "Utilization Reporting",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/utilization"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "variables"
+      },
+      {
+        "title": "Variables",
+        "path": "variables/variables"
+      },
+      {
+        "title": "Locks",
+        "path": "variables/locks"
+      }
+    ]
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.10.x/data/commands-nav-data.json b/content/nomad/v1.10.x/data/commands-nav-data.json
new file mode 100644
index 0000000000..8d81dac3f1
--- /dev/null
+++ b/content/nomad/v1.10.x/data/commands-nav-data.json
@@ -0,0 +1,1048 @@
+[
+  {
+    "title": "Commands (CLI)",
+    "path": "index"
+  },
+  {
+    "title": "acl",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "bootstrap",
+        "path": "acl/bootstrap"
+      },
+      {
+        "title": "auth-method",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/auth-method/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/auth-method/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/auth-method/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/auth-method/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/auth-method/update"
+          }
+        ]
+      },
+      {
+        "title": "binding-rule",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/binding-rule/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/binding-rule/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/binding-rule/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/binding-rule/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/binding-rule/update"
+          }
+        ]
+      },
+      {
+        "title": "policy",
+        "routes": [
+          {
+            "title": "apply",
+            "path": "acl/policy/apply"
+          },
+          {
+            "title": "delete",
+            "path": "acl/policy/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/policy/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/policy/list"
+          },
+          {
+            "title": "self",
+            "path": "acl/policy/self"
+          }
+        ]
+      },
+      {
+        "title": "role",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/role/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/role/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/role/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/role/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/role/update"
+          }
+        ]
+      },
+      {
+        "title": "token",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/token/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/token/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/token/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/token/list"
+          },
+          {
+            "title": "self",
+            "path": "acl/token/self"
+          },
+          {
+            "title": "update",
+            "path": "acl/token/update"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "agent",
+    "path": "agent"
+  },
+  {
+    "title": "agent-info",
+    "path": "agent-info"
+  },
+  {
+    "title": "alloc",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "alloc"
+      },
+      {
+        "title": "checks",
+        "path": "alloc/checks"
+      },
+      {
+        "title": "exec",
+        "path": "alloc/exec"
+      },
+      {
+        "title": "fs",
+        "path": "alloc/fs"
+      },
+      {
+        "title": "logs",
+        "path": "alloc/logs"
+      },
+      {
+        "title": "pause",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "alloc/pause"
+      },
+      {
+        "title": "restart",
+        "path": "alloc/restart"
+      },
+      {
+        "title": "signal",
+        "path": "alloc/signal"
+      },
+      {
+        "title": "status",
+        "path": "alloc/status"
+      },
+      {
+        "title": "stop",
+        "path": "alloc/stop"
+      }
+    ]
+  },
+  {
+    "title": "config",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "config"
+      },
+      {
+        "title": "validate",
+        "path": "config/validate"
+      }
+    ]
+  },
+  {
+    "title": "deployment",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "deployment"
+      },
+      {
+        "title": "fail",
+        "path": "deployment/fail"
+      },
+      {
+        "title": "list",
+        "path": "deployment/list"
+      },
+      {
+        "title": "pause",
+        "path": "deployment/pause"
+      },
+      {
+        "title": "promote",
+        "path": "deployment/promote"
+      },
+      {
+        "title": "resume",
+        "path": "deployment/resume"
+      },
+      {
+        "title": "status",
+        "path": "deployment/status"
+      },
+      {
+        "title": "unblock",
+        "path": "deployment/unblock"
+      }
+    ]
+  },
+  {
+    "title": "eval",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "eval"
+      },
+      {
+        "title": "delete",
+        "path": "eval/delete"
+      },
+      {
+        "title": "list",
+        "path": "eval/list"
+      },
+      {
+        "title": "status",
+        "path": "eval/status"
+      }
+    ]
+  },
+  {
+    "title": "fmt",
+    "path": "fmt"
+  },
+  {
+    "title": "job",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job"
+      },
+      {
+        "title": "action",
+        "path": "job/action"
+      },
+      {
+        "title": "allocs",
+        "path": "job/allocs"
+      },
+      {
+        "title": "deployments",
+        "path": "job/deployments"
+      },
+      {
+        "title": "dispatch",
+        "path": "job/dispatch"
+      },
+      {
+        "title": "eval",
+        "path": "job/eval"
+      },
+      {
+        "title": "history",
+        "path": "job/history"
+      },
+      {
+        "title": "init",
+        "path": "job/init"
+      },
+      {
+        "title": "inspect",
+        "path": "job/inspect"
+      },
+      {
+        "title": "plan",
+        "path": "job/plan"
+      },
+      {
+        "title": "periodic force",
+        "path": "job/periodic-force"
+      },
+      {
+        "title": "promote",
+        "path": "job/promote"
+      },
+      {
+        "title": "restart",
+        "path": "job/restart"
+      },
+      {
+        "title": "revert",
+        "path": "job/revert"
+      },
+      {
+        "title": "run",
+        "path": "job/run"
+      },
+      {
+        "title": "scale",
+        "path": "job/scale"
+      },
+      {
+        "title": "scaling-events",
+        "path": "job/scaling-events"
+      },
+      {
+        "title": "start",
+        "path": "job/start"
+      },
+      {
+        "title": "status",
+        "path": "job/status"
+      },
+      {
+        "title": "stop",
+        "path": "job/stop"
+      },
+      {
+        "title": "tag",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job/tag"
+          },
+          {
+            "title": "apply",
+            "path": "job/tag/apply"
+          },
+          {
+            "title": "unset",
+            "path": "job/tag/unset"
+          }
+        ]
+      },
+      {
+        "title": "validate",
+        "path": "job/validate"
+      }
+    ]
+  },
+  {
+    "title": "license",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "license"
+      },
+      {
+        "title": "get",
+        "path": "license/get"
+      },
+      {
+        "title": "inspect",
+        "path": "license/inspect"
+      }
+    ]
+  },
+  {
+    "title": "login",
+    "path": "login"
+  },
+  {
+    "title": "monitor",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "monitor"
+      },
+      { "title": "export", "path": "monitor/export" }
+    ]
+  },
+  {
+    "title": "namespace",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "namespace"
+      },
+      {
+        "title": "apply",
+        "path": "namespace/apply"
+      },
+      {
+        "title": "delete",
+        "path": "namespace/delete"
+      },
+      {
+        "title": "inspect",
+        "path": "namespace/inspect"
+      },
+      {
+        "title": "list",
+        "path": "namespace/list"
+      },
+      {
+        "title": "status",
+        "path": "namespace/status"
+      }
+    ]
+  },
+  {
+    "title": "node",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "node"
+      },
+      {
+        "title": "config",
+        "path": "node/config"
+      },
+      {
+        "title": "drain",
+        "path": "node/drain"
+      },
+      {
+        "title": "eligibility",
+        "path": "node/eligibility"
+      },
+      {
+        "title": "meta",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "node/meta"
+          },
+          {
+            "title": "apply",
+            "path": "node/meta/apply"
+          },
+          {
+            "title": "read",
+            "path": "node/meta/read"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "node/status"
+      }
+    ]
+  },
+  {
+    "title": "node pool",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "node-pool"
+      },
+      {
+        "title": "apply",
+        "path": "node-pool/apply"
+      },
+      {
+        "title": "delete",
+        "path": "node-pool/delete"
+      },
+      {
+        "title": "info",
+        "path": "node-pool/info"
+      },
+      {
+        "title": "init",
+        "path": "node-pool/init"
+      },
+      {
+        "title": "jobs",
+        "path": "node-pool/jobs"
+      },
+      {
+        "title": "list",
+        "path": "node-pool/list"
+      },
+      {
+        "title": "nodes",
+        "path": "node-pool/nodes"
+      }
+    ]
+  },
+  {
+    "title": "operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "api",
+        "path": "operator/api"
+      },
+      {
+        "title": "autopilot",
+        "routes": [
+          {
+            "title": "get-config",
+            "path": "operator/autopilot/get-config"
+          },
+          {
+            "title": "set-config",
+            "path": "operator/autopilot/set-config"
+          },
+          {
+            "title": "health",
+            "path": "operator/autopilot/health"
+          }
+        ]
+      },
+      {
+        "title": "client-state",
+        "path": "operator/client-state"
+      },
+      {
+        "title": "debug",
+        "path": "operator/debug"
+      },
+      {
+        "title": "gossip",
+        "routes": [
+          {
+            "title": "keyring generate",
+            "path": "operator/gossip/keyring-generate"
+          },
+          {
+            "title": "keyring install",
+            "path": "operator/gossip/keyring-install"
+          },
+          {
+            "title": "keyring list",
+            "path": "operator/gossip/keyring-list"
+          },
+          {
+            "title": "keyring remove",
+            "path": "operator/gossip/keyring-remove"
+          },
+          {
+            "title": "keyring use",
+            "path": "operator/gossip/keyring-use"
+          }
+        ]
+      },
+      {
+        "title": "metrics",
+        "path": "operator/metrics"
+      },
+      {
+        "title": "raft",
+        "routes": [
+          {
+            "title": "info",
+            "path": "operator/raft/info"
+          },
+          {
+            "title": "list-peers",
+            "path": "operator/raft/list-peers"
+          },
+          {
+            "title": "logs",
+            "path": "operator/raft/logs"
+          },
+          {
+            "title": "remove-peer",
+            "path": "operator/raft/remove-peer"
+          },
+          {
+            "title": "state",
+            "path": "operator/raft/state"
+          },
+          {
+            "title": "transfer-leadership",
+            "path": "operator/raft/transfer-leadership"
+          }
+        ]
+      },
+      {
+        "title": "root",
+        "routes": [
+          {
+            "title": "keyring list",
+            "path": "operator/root/keyring-list"
+          },
+          {
+            "title": "keyring remove",
+            "path": "operator/root/keyring-remove"
+          },
+          {
+            "title": "keyring rotate",
+            "path": "operator/root/keyring-rotate"
+          }
+        ]
+      },
+      {
+        "title": "scheduler",
+        "routes": [
+          {
+            "title": "get-config",
+            "path": "operator/scheduler/get-config"
+          },
+          {
+            "title": "set-config",
+            "path": "operator/scheduler/set-config"
+          }
+        ]
+      },
+      {
+        "title": "snapshot",
+        "routes": [
+          {
+            "title": "agent",
+            "badge": {
+              "text": "ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "operator/snapshot/agent"
+          },
+          {
+            "title": "inspect",
+            "path": "operator/snapshot/inspect"
+          },
+          {
+            "title": "redact",
+            "path": "operator/snapshot/redact"
+          },
+          {
+            "title": "restore",
+            "path": "operator/snapshot/restore"
+          },
+          {
+            "title": "save",
+            "path": "operator/snapshot/save"
+          },
+          {
+            "title": "state",
+            "path": "operator/snapshot/state"
+          }
+        ]
+      },
+      {
+        "title": "utilization",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/utilization"
+      }
+    ]
+  },
+  {
+    "title": "plugin",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "plugin"
+      },
+      {
+        "title": "status",
+        "path": "plugin/status"
+      }
+    ]
+  },
+  {
+    "title": "quota",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "quota"
+      },
+      {
+        "title": "apply",
+        "path": "quota/apply"
+      },
+      {
+        "title": "delete",
+        "path": "quota/delete"
+      },
+      {
+        "title": "init",
+        "path": "quota/init"
+      },
+      {
+        "title": "inspect",
+        "path": "quota/inspect"
+      },
+      {
+        "title": "list",
+        "path": "quota/list"
+      },
+      {
+        "title": "status",
+        "path": "quota/status"
+      }
+    ]
+  },
+  {
+    "title": "recommendation",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "recommendation"
+      },
+      {
+        "title": "apply",
+        "path": "recommendation/apply"
+      },
+      {
+        "title": "dismiss",
+        "path": "recommendation/dismiss"
+      },
+      {
+        "title": "info",
+        "path": "recommendation/info"
+      },
+      {
+        "title": "list",
+        "path": "recommendation/list"
+      }
+    ]
+  },
+  {
+    "title": "setup",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "setup"
+      },
+      {
+        "title": "consul",
+        "path": "setup/consul"
+      },
+      {
+        "title": "vault",
+        "path": "setup/vault"
+      }
+    ]
+  },
+  {
+    "title": "scaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "scaling"
+      },
+      {
+        "title": "policy info",
+        "path": "scaling/policy-info"
+      },
+      {
+        "title": "policy list",
+        "path": "scaling/policy-list"
+      }
+    ]
+  },
+  {
+    "title": "sentinel",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "sentinel"
+      },
+      {
+        "title": "apply",
+        "path": "sentinel/apply"
+      },
+      {
+        "title": "delete",
+        "path": "sentinel/delete"
+      },
+      {
+        "title": "list",
+        "path": "sentinel/list"
+      },
+      {
+        "title": "read",
+        "path": "sentinel/read"
+      }
+    ]
+  },
+  {
+    "title": "server",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "server"
+      },
+      {
+        "title": "force-leave",
+        "path": "server/force-leave"
+      },
+      {
+        "title": "join",
+        "path": "server/join"
+      },
+      {
+        "title": "members",
+        "path": "server/members"
+      }
+    ]
+  },
+  {
+    "title": "service",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "service"
+      },
+      {
+        "title": "service delete",
+        "path": "service/delete"
+      },
+      {
+        "title": "service info",
+        "path": "service/info"
+      },
+      {
+        "title": "service list",
+        "path": "service/list"
+      }
+    ]
+  },
+  {
+    "title": "status",
+    "path": "status"
+  },
+  {
+    "title": "system",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "system"
+      },
+      {
+        "title": "gc",
+        "path": "system/gc"
+      },
+      {
+        "title": "reconcile summaries",
+        "path": "system/reconcile-summaries"
+      }
+    ]
+  },
+  {
+    "title": "tls",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "tls"
+      },
+      {
+        "title": "ca create",
+        "path": "tls/ca-create"
+      },
+      {
+        "title": "ca info",
+        "path": "tls/ca-info"
+      },
+      {
+        "title": "cert create",
+        "path": "tls/cert-create"
+      },
+      {
+        "title": "cert info",
+        "path": "tls/cert-info"
+      }
+    ]
+  },
+  {
+    "title": "ui",
+    "path": "ui"
+  },
+  {
+    "title": "var",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "var"
+      },
+      {
+        "title": "get",
+        "path": "var/get"
+      },
+      {
+        "title": "init",
+        "path": "var/init"
+      },
+      {
+        "title": "list",
+        "path": "var/list"
+      },
+      {
+        "title": "put",
+        "path": "var/put"
+      },
+      {
+        "title": "lock",
+        "path": "var/lock"
+      },
+      {
+        "title": "purge",
+        "path": "var/purge"
+      }
+    ]
+  },
+  {
+    "title": "version",
+    "path": "version"
+  },
+  {
+    "title": "volume",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "volume"
+      },
+      {
+        "title": "claim delete",
+        "path": "volume/claim-delete"
+      },
+      {
+        "title": "claim list",
+        "path": "volume/claim-list"
+      },
+      {
+        "title": "create",
+        "path": "volume/create"
+      },
+      {
+        "title": "delete",
+        "path": "volume/delete"
+      },
+      {
+        "title": "deregister",
+        "path": "volume/deregister"
+      },
+      {
+        "title": "detach",
+        "path": "volume/detach"
+      },
+      {
+        "title": "init",
+        "path": "volume/init"
+      },
+      {
+        "title": "register",
+        "path": "volume/register"
+      },
+      {
+        "title": "snapshot create",
+        "path": "volume/snapshot-create"
+      },
+      {
+        "title": "snapshot delete",
+        "path": "volume/snapshot-delete"
+      },
+      {
+        "title": "snapshot list",
+        "path": "volume/snapshot-list"
+      },
+      {
+        "title": "status",
+        "path": "volume/status"
+      }
+    ]
+  },
+  {
+    "title": "windows",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "windows"
+      },
+      {
+        "title": "service install",
+        "path": "windows/service-install"
+      },
+      {
+        "title": "service uninstall",
+        "path": "windows/service-uninstall"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.10.x/data/docs-nav-data.json b/content/nomad/v1.10.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..0d6b0e6790
--- /dev/null
+++ b/content/nomad/v1.10.x/data/docs-nav-data.json
@@ -0,0 +1,1740 @@
+[
+  {
+    "heading": "Get started"
+  },
+  {
+    "title": "What is Nomad?",
+    "path": "what-is-nomad"
+  },
+  {
+    "title": "Quickstart",
+    "path": "quickstart"
+  },
+  {
+    "title": "Use cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Architecture",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "architecture"
+      },
+      {
+        "title": "Cluster",
+        "routes": [
+          {
+            "title": "Cluster Consensus",
+            "path": "architecture/cluster/consensus"
+          },
+          {
+            "title": "Multi-cluster federation",
+            "path": "architecture/cluster/federation"
+          },
+          {
+            "title": "Node pools",
+            "path": "architecture/cluster/node-pools"
+          }
+        ]
+      },
+      {
+        "title": "CPU",
+        "path": "architecture/cpu"
+      },
+      {
+        "title": "Security",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "architecture/security"
+          },
+          {
+            "title": "Cluster Gossip",
+            "path": "architecture/security/gossip"
+          }
+        ]
+      },
+      {
+        "title": "Storage",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "architecture/storage"
+          },
+          {
+            "title": "CSI",
+            "path": "architecture/storage/csi"
+          },
+          {
+            "title": "Host volumes",
+            "path": "architecture/storage/host-volumes"
+          },
+          {
+            "title": "Stateful workload considerations",
+            "path": "architecture/storage/stateful-workloads"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Allocation filesystem",
+        "path": "concepts/filesystem"
+      },
+
+      {
+        "title": "Job",
+        "path": "concepts/job"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "concepts/variables"
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "How scheduling works",
+            "path": "concepts/scheduling/how-scheduling-works"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          },
+          {
+            "title": "Job schedulers",
+            "path": "concepts/scheduling/schedulers"
+          }
+        ]
+      },
+      {
+        "title": "Stateful deployments",
+        "path": "concepts/stateful-deployments"
+      },
+      {
+        "title": "Workload identity",
+        "path": "concepts/workload-identity"
+      }
+    ]
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Nomad operations"
+  },
+
+  {
+    "title": "Deploy and run Nomad",
+    "routes": [
+      {
+        "title": "Install Nomad",
+        "path": "deploy"
+      },
+      {
+        "title": "Production deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "deploy/production/requirements"
+          },
+          {
+            "title": "Reference architecture",
+            "path": "deploy/production/reference-architecture"
+          },
+          {
+            "title": "Deployment guide",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul"
+          },
+          {
+            "title": "Windows service",
+            "path": "deploy/production/windows-service"
+          }
+        ]
+      },
+      {
+        "title": "Operate a Nomad agent",
+        "path": "deploy/nomad-agent"
+      },
+      {
+        "title": "Build Nomad clusters",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/clusters"
+          },
+          {
+            "title": "Connect nodes into a cluster",
+            "path": "deploy/clusters/connect-nodes"
+          },
+          {
+            "title": "Multi-region federation considerations",
+            "path": "deploy/clusters/federation-considerations"
+          },
+          {
+            "title": "Federation failure scenarios",
+            "path": "deploy/clusters/federation-failure-scenarios"
+          },
+          {
+            "title": "Federate multi-region clusters",
+            "path": "deploy/clusters/federate-regions"
+          },
+          {
+            "title": "Load balancing",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/load-balancing"
+          },
+          {
+            "title": "Configure a web UI reverse proxy",
+            "path": "deploy/clusters/reverse-proxy-ui"
+          }
+        ]
+      },
+      {
+        "title": "Configure task drivers",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/task-driver"
+          },
+          {
+            "title": "Docker",
+            "path": "deploy/task-driver/docker"
+          },
+          {
+            "title": "Isolated Fork/Exec",
+            "path": "deploy/task-driver/exec"
+          },
+          {
+            "title": "Java",
+            "path": "deploy/task-driver/java"
+          },
+          {
+            "title": "QEMU",
+            "path": "deploy/task-driver/qemu"
+          },
+          {
+            "title": "Raw Fork/Exec",
+            "path": "deploy/task-driver/raw_exec"
+          },
+          {
+            "title": "Task driver plugins",
+            "routes": [
+              {
+                "title": "Exec2",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/exec2"
+              },
+              {
+                "title": "Podman",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/podman"
+              },
+              {
+                "title": "Virt <sup>Beta</sup>",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/virt"
+              },
+              {
+                "title": "Community",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/community"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Govern Nomad's use",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "govern"
+      },
+      {
+        "title": "Namespaces",
+        "path": "govern/namespaces"
+      },
+      {
+        "title": "Node pools",
+        "path": "govern/use-node-pools"
+      },
+      {
+        "title": "Resource quotas",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "govern/resource-quotas"
+      },
+      {
+        "title": "Sentinel policies",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "govern/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "Manage Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "manage"
+      },
+      {
+        "title": "Autopilot",
+        "path": "manage/autopilot"
+      },
+      {
+        "title": "Format CLI output",
+        "path": "manage/format-cli-output"
+      },
+      {
+        "title": "Garbage collection",
+        "path": "manage/garbage-collection"
+      },
+      {
+        "title": "Key management",
+        "path": "manage/key-management"
+      },
+      {
+        "title": "Migrate workloads",
+        "path": "manage/migrate-workloads"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "manage/variables"
+      },
+      {
+        "title": "Recovery",
+        "path": "manage/outage-recovery"
+      }
+    ]
+  },
+  {
+    "title": "Monitor Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "monitor"
+      },
+      {
+        "title": "Event stream",
+        "path": "monitor/event-stream"
+      },
+      {
+        "title": "Inspect job workloads",
+        "path": "monitor/inspect-workloads"
+      },
+      {
+        "title": "Inspect clusters",
+        "path": "monitor/inspect-cluster"
+      },
+      {
+        "title": "Cluster topology",
+        "path": "monitor/cluster-topology"
+      },
+      {
+        "title": "Use Prometheus",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/manage-clusters/prometheus-metrics"
+      },
+      {
+        "title": "Monitor job service metrics",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/manage-clusters/prometheus-service-mesh-metrics"
+      }
+    ]
+  },
+  {
+    "title": "Network Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Bridge networking with CNI",
+        "path": "networking/cni"
+      },
+      {
+        "title": "Service discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Consul",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "networking/consul"
+          },
+          {
+            "title": "Service mesh",
+            "path": "networking/consul/service-mesh"
+          }
+        ]
+      },
+      {
+        "title": "IPv6 support",
+        "path": "networking/ipv6"
+      }
+    ]
+  },
+  {
+    "title": "Scale Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "scale"
+      },
+      {
+        "title": "Nomad Autoscaler",
+        "href": "https://developer.hashicorp.com/nomad/tools/autoscaling"
+      },
+      {
+        "title": "Benchmark and load test",
+        "path": "scale/benchmarking"
+      }
+    ]
+  },
+  {
+    "title": "Secure Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "secure"
+      },
+      {
+        "title": "Access control list",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/acl"
+          },
+          {
+            "title": "Bootstrap the ACL system",
+            "path": "secure/acl/bootstrap"
+          },
+          {
+            "title": "Integrate Consul ACL",
+            "path": "secure/acl/consul"
+          },
+          {
+            "title": "Policies",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "secure/acl/policies"
+              },
+              {
+                "title": "Create policies",
+                "path": "secure/acl/policies/create-policy"
+              }
+            ]
+          },
+          {
+            "title": "Tokens",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "secure/acl/tokens"
+              },
+              {
+                "title": "Generate tokens with Vault",
+                "path": "secure/acl/tokens/vault"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Authentication",
+        "routes": [
+          {
+            "title": "Configure JWT",
+            "path": "secure/authentication/jwt"
+          },
+          {
+            "title": "Configure OIDC",
+            "path": "secure/authentication/oidc"
+          },
+          {
+            "title": "SSO with Auth0",
+            "path": "secure/authentication/sso-auth0"
+          },
+          {
+            "title": "SSO with Vault",
+            "path": "secure/authentication/sso-vault"
+          },
+          {
+            "title": "SSO with PKCE and private key JWT ",
+            "path": "secure/authentication/sso-pkce-jwt"
+          }
+        ]
+      },
+      {
+        "title": "Traffic encryption",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/traffic"
+          },
+          {
+            "title": "Enable gossip encryption",
+            "path": "secure/traffic/gossip-encryption"
+          },
+          {
+            "title": "Enable TLS",
+            "path": "secure/traffic/tls"
+          }
+        ]
+      },
+      {
+        "title": "Vault",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/vault"
+          },
+          {
+            "title": "ACL",
+            "path": "secure/vault/acl"
+          }
+        ]
+      },
+      {
+        "title": "Workload identity",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/workload-identity"
+          },
+          {
+            "title": "Federate AWS Access",
+            "path": "secure/workload-identity/aws-oidc-provider"
+          },
+          {
+            "title": "Federate GCP access",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/fed-workload-identity/integration-gcp"
+          },
+          {
+            "title": "Use workload identities with Vault",
+            "path": "secure/workload-identity/vault"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Upgrade Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific version details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Release notes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "release-notes"
+      },
+      {
+        "title": "Nomad",
+        "routes": [
+          {
+            "title": "Upcoming",
+            "path": "release-notes/nomad/upcoming"
+          },
+          {
+            "title": "v1.10.x",
+            "path": "release-notes/nomad/v1-10-x"
+          },
+          {
+            "title": "v1.9.x",
+            "path": "release-notes/nomad/v1_9_x"
+          },
+          {
+            "title": "v1.8.x",
+            "path": "release-notes/nomad/v1_8_x"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Agent configuration reference",
+    "href": "https://developer.hashicorp.com/nomad/docs/configuration/"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Jobs"
+  },
+  {
+    "title": "Declare jobs",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-declare"
+      },
+      {
+        "title": "Create a job specification",
+        "path": "job-declare/create-job"
+      },
+      {
+        "title": "Configure tasks",
+        "path": "job-declare/configure-tasks"
+      },
+      {
+        "title": "Create a parameterized job",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/job-specifications/job-spec-parameterized"
+      },
+      {
+        "title": "Use task drivers",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/task-driver"
+          },
+          {
+            "title": "Docker",
+            "path": "job-declare/task-driver/docker"
+          },
+          {
+            "title": "Isolated Fork/Exec",
+            "path": "job-declare/task-driver/exec"
+          },
+          {
+            "title": "Java",
+            "path": "job-declare/task-driver/java"
+          },
+          {
+            "title": "QEMU",
+            "path": "job-declare/task-driver/qemu"
+          },
+          {
+            "title": "Raw Fork/Exec",
+            "path": "job-declare/task-driver/raw_exec"
+          },
+          {
+            "title": "Task driver plugins",
+            "routes": [
+              {
+                "title": "Exec2",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/exec2"
+              },
+              {
+                "title": "Podman",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/podman"
+              },
+              {
+                "title": "Virt <sup>Beta</sup>",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/virt"
+              },
+              {
+                "title": "Community",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/community"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Use device plugins",
+        "href": "https://developer.hashicorp.com/nomad/plugins/devices"
+      },
+      {
+        "title": "Use Consul service mesh",
+        "path": "job-declare/consul-service-mesh"
+      },
+      {
+        "title": "Use Vault",
+        "path": "job-declare/vault"
+      },
+      {
+        "title": "Configure deployment strategies",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/strategy"
+          },
+          {
+            "title": "Configure blue/green and canary",
+            "path": "job-declare/strategy/blue-green-canary"
+          },
+          {
+            "title": "Configure rolling",
+            "path": "job-declare/strategy/rolling"
+          }
+        ]
+      },
+      {
+        "title": "Configure multi-region deployments",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-declare/multiregion"
+      },
+      {
+        "title": "Configure task dependencies",
+        "path": "job-declare/task-dependencies"
+      },
+      {
+        "title": "Use Nomad actions",
+        "path": "job-declare/nomad-actions"
+      },
+      {
+        "title": "Use Nomad variables",
+        "path": "job-declare/nomad-variables"
+      },
+      {
+        "title": "Configure exit signals",
+        "path": "job-declare/exit-signals"
+      },
+      {
+        "title": "Handle failure",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/failure"
+          },
+          {
+            "title": "Local restarts",
+            "path": "job-declare/failure/restart"
+          },
+          {
+            "title": "Health check restarts",
+            "path": "job-declare/failure/check-restart"
+          },
+          {
+            "title": "Reschedule",
+            "path": "job-declare/failure/reschedule"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Run jobs",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-run"
+      },
+      {
+        "title": "Inspect running jobs",
+        "path": "job-run/inspect"
+      },
+      {
+        "title": "Access logs for troubleshooting",
+        "path": "job-run/logs"
+      },
+      {
+        "title": "Collect resource utilization metrics",
+        "path": "job-run/utilization-metrics"
+      },
+      {
+        "title": "Create job versions",
+        "path": "job-run/versions"
+      }
+    ]
+  },
+  {
+    "title": "Stateful workloads",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "stateful-workloads"
+      },
+      {
+        "title": "Use CSI volumes",
+        "path": "stateful-workloads/csi-volumes"
+      },
+      {
+        "title": "Use dynamic host volumes",
+        "path": "stateful-workloads/dynamic-host-volumes"
+      },
+      {
+        "title": "Use static host volumes",
+        "path": "stateful-workloads/static-host-volumes"
+      }
+    ]
+  },
+  {
+    "title": "Workload networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-networking"
+      },
+      {
+        "title": "Service discovery",
+        "path": "job-networking/service-discovery"
+      },
+      {
+        "title": "Use a CNI network",
+        "path": "job-networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Advanced scheduling for efficiency",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-scheduling"
+      },
+      {
+        "title": "Fault tolerance with spread",
+        "path": "job-scheduling/spread"
+      },
+      {
+        "title": "Job placement with affinities",
+        "path": "job-scheduling/affinity"
+      },
+      {
+        "title": "Job priority with preemption",
+        "path": "job-scheduling/preemption"
+      },
+      {
+        "title": "Memory oversubscription",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/advanced-scheduling/memory-oversubscription"
+      }
+    ]
+  },
+  {
+    "title": "Job templates with Nomad Pack",
+    "href": "/tools/nomad-pack/create-packs#write-the-templates"
+  },
+  {
+    "title": "Job specification reference",
+    "href": "https://developer.hashicorp.com/nomad/docs/job-specification/"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Enterprise solutions"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Features",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "Automated license utilization reporting",
+            "path": "enterprise/license/utilization-reporting"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Nomad ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad partnerships",
+    "path": "partnerships"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Reference docs"
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "title": "Agent configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "keyring",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "configuration/keyring"
+          },
+          {
+            "title": "AWS KMS",
+            "path": "configuration/keyring/awskms"
+          },
+          {
+            "title": "Azure Key Vault",
+            "path": "configuration/keyring/azurekeyvault"
+          },
+          {
+            "title": "GCP Cloud KMS",
+            "path": "configuration/keyring/gcpckms"
+          },
+          {
+            "title": "Vault Transit",
+            "path": "configuration/keyring/transit"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "reporting",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/reporting"
+      },
+      {
+        "title": "rpc",
+        "path": "configuration/rpc"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "sentinel",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Job specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "action",
+        "path": "job-specification/action"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "consul",
+        "path": "job-specification/consul"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "disconnect",
+        "path": "job-specification/disconnect"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "numa",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/numa"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "schedule",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/schedule"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "transparent_proxy",
+        "path": "job-specification/transparent_proxy"
+      },
+      {
+        "title": "ui",
+        "path": "job-specification/ui"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Nomad object specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Resource quota",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "other-specifications/quota"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "CSI",
+            "path": "other-specifications/volume/csi"
+          },
+          {
+            "title": "Dynamic host volumes",
+            "path": "other-specifications/volume/host"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Reference",
+    "routes": [
+      {
+        "title": "Metrics",
+        "path": "reference/metrics"
+      },
+      {
+        "title": "Runtime environment settings",
+        "path": "reference/runtime-environment-settings"
+      },
+      {
+        "title": "Runtime variable interpolation",
+        "path": "reference/runtime-variable-interpolation"
+      },
+      {
+        "title": "Web UI keyboard shortcuts",
+        "path": "reference/keyboard-commands"
+      },
+      {
+        "title": "Sentinel policy",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "reference/sentinel-policy"
+      },
+      {
+        "title": "Go template syntax",
+        "path": "reference/go-template-syntax"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "reference/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "reference/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "reference/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "reference/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "reference/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "reference/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "reference/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "reference/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "reference/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "reference/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "reference/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "reference/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "reference/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "reference/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "reference/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "reference/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "reference/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "reference/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "reference/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "reference/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "reference/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "reference/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "reference/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "reference/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "reference/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "reference/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "reference/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "reference/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "reference/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "reference/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "reference/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "reference/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "reference/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "reference/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "reference/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "reference/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "reference/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "reference/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "reference/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "reference/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "reference/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "reference/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "reference/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "reference/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "reference/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "reference/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "reference/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "reference/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "reference/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "reference/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "reference/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "reference/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "reference/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "reference/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "reference/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "reference/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "reference/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "reference/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "reference/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "reference/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "reference/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "reference/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "reference/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "reference/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "reference/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "reference/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "reference/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "reference/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "reference/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "reference/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "reference/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "reference/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "reference/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "reference/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "reference/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "reference/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "reference/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "reference/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "reference/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "reference/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "reference/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "reference/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "reference/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "reference/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "reference/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "reference/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "reference/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "reference/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "reference/hcl2/variables"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.10.x/data/intro-nav-data.json b/content/nomad/v1.10.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..749e6ff77f
--- /dev/null
+++ b/content/nomad/v1.10.x/data/intro-nav-data.json
@@ -0,0 +1,6 @@
+[
+  {
+    "title": "What is Nomad?",
+    "href": "/docs/what-is-nomad"
+  }
+]
diff --git a/content/nomad/v1.10.x/data/plugins-nav-data.json b/content/nomad/v1.10.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..1d04df33fb
--- /dev/null
+++ b/content/nomad/v1.10.x/data/plugins-nav-data.json
@@ -0,0 +1,137 @@
+[
+  {
+    "title": "Task drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Exec2",
+        "path": "drivers/exec2"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Virt",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/virt"
+          },
+          {
+            "title": "Install",
+            "path": "drivers/virt/install"
+          },
+          {
+            "title": "Task config",
+            "path": "drivers/virt/task-config"
+          }
+        ]
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "https://github.com/Roblox/nomad-driver-containerd"
+          },
+          {
+            "title": "Pledge",
+            "href": "https://github.com/shoenig/nomad-pledge-driver"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "https://github.com/cneira/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "href": "https://github.com/cneira/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "https://docs.lightrun.com/integrations/nomad/"
+          },
+          {
+            "title": "Pot",
+            "href": "https://github.com/bsdpot/nomad-pot-driver"
+          },
+          {
+            "title": "Rookout",
+            "href": "https://github.com/Rookout/rookout-nomad-driver"
+          },
+          {
+            "title": "Singularity",
+            "href": "https://github.com/hpcng/nomad-driver-singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "https://github.com/JanMa/nomad-driver-nspawn"
+          },
+          {
+            "title": "Windows IIS - Roblox",
+            "href": "https://github.com/Roblox/nomad-driver-iis"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "https://nomad-iis.sevensolutions.cc/"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Devices",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "NVIDIA",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "USB",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "devices/usb"
+      }
+    ]
+  },
+  {
+    "title": "Plugin authoring guide",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "author"
+      },
+      {
+        "title": "Device",
+        "path": "author/device"
+      },
+      {
+        "title": "Host volume",
+        "path": "author/host-volume"
+      },
+      {
+        "title": "Task driver",
+        "path": "author/task-driver"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.10.x/data/tools-nav-data.json b/content/nomad/v1.10.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..31a682842e
--- /dev/null
+++ b/content/nomad/v1.10.x/data/tools-nav-data.json
@@ -0,0 +1,373 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Nomad Autoscaler",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "badge": {
+              "text": "ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "high_availability",
+            "path": "autoscaling/agent/high_availability"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Nomad Pack",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-pack"
+      },
+      {
+        "title": "Advanced usage",
+        "path": "nomad-pack/advanced-usage"
+      },
+      {
+        "title": "Create packs",
+        "path": "nomad-pack/create-packs"
+      },
+      {
+        "title": "CLI reference",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "nomad-pack/commands"
+          },
+          {
+            "title": "deps",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/deps"
+              },
+              {
+                "title": "vendor",
+                "path": "nomad-pack/commands/deps/vendor"
+              }
+            ]
+          },
+          {
+            "title": "destroy",
+            "path": "nomad-pack/commands/destroy"
+          },
+          {
+            "title": "generate",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/generate"
+              },
+              {
+                "title": "pack",
+                "path": "nomad-pack/commands/generate/pack"
+              },
+              {
+                "title": "registry",
+                "path": "nomad-pack/commands/generate/registry"
+              },
+              {
+                "title": "var-file",
+                "path": "nomad-pack/commands/generate/var-file"
+              }
+            ]
+          },
+          {
+            "title": "info",
+            "path": "nomad-pack/commands/info"
+          },
+          {
+            "title": "list",
+            "path": "nomad-pack/commands/list"
+          },
+          {
+            "title": "plan",
+            "path": "nomad-pack/commands/plan"
+          },
+          {
+            "title": "registry",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/registry"
+              },
+              {
+                "title": "add",
+                "path": "nomad-pack/commands/registry/add"
+              },
+              {
+                "title": "delete",
+                "path": "nomad-pack/commands/registry/delete"
+              },
+              {
+                "title": "list",
+                "path": "nomad-pack/commands/registry/list"
+              }
+            ]
+          },
+          {
+            "title": "render",
+            "path": "nomad-pack/commands/render"
+          },
+          {
+            "title": "run",
+            "path": "nomad-pack/commands/run"
+          },
+          {
+            "title": "status",
+            "path": "nomad-pack/commands/status"
+          },
+          {
+            "title": "stop",
+            "path": "nomad-pack/commands/stop"
+          },
+          {
+            "title": "version",
+            "path": "nomad-pack/commands/version"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.10.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.10.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.10.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.10.x/img/autoscaling/control-loop.png b/content/nomad/v1.10.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.10.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.10.x/img/autoscaling/policy-eval.png b/content/nomad/v1.10.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.10.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/active-alert.png b/content/nomad/v1.10.x/img/clusters/active-alert.png
new file mode 100644
index 0000000000..15baa8b333
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/active-alert.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/alertmanager-webui.png b/content/nomad/v1.10.x/img/clusters/alertmanager-webui.png
new file mode 100644
index 0000000000..c2d7b33385
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/alertmanager-webui.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/alerts.png b/content/nomad/v1.10.x/img/clusters/alerts.png
new file mode 100644
index 0000000000..5bc5e15333
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/alerts.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/cannot-fetch-logs.png b/content/nomad/v1.10.x/img/clusters/cannot-fetch-logs.png
new file mode 100644
index 0000000000..c781b60a5b
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/cannot-fetch-logs.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/cannot-remote-exec.png b/content/nomad/v1.10.x/img/clusters/cannot-remote-exec.png
new file mode 100644
index 0000000000..8cfff1e819
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/cannot-remote-exec.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/chrome-pending.png b/content/nomad/v1.10.x/img/clusters/chrome-pending.png
new file mode 100644
index 0000000000..fa5b18d11c
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/chrome-pending.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/chrome-timeout.png b/content/nomad/v1.10.x/img/clusters/chrome-timeout.png
new file mode 100644
index 0000000000..2a5aa3b7c1
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/chrome-timeout.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/firefox-pending.png b/content/nomad/v1.10.x/img/clusters/firefox-pending.png
new file mode 100644
index 0000000000..168022409e
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/firefox-pending.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/firefox-timeout.png b/content/nomad/v1.10.x/img/clusters/firefox-timeout.png
new file mode 100644
index 0000000000..db192125ce
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/firefox-timeout.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/new-targets.png b/content/nomad/v1.10.x/img/clusters/new-targets.png
new file mode 100644
index 0000000000..a535407eeb
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/new-targets.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/nomad-multi-region.png b/content/nomad/v1.10.x/img/clusters/nomad-multi-region.png
new file mode 100644
index 0000000000..448e87f475
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/nomad-multi-region.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/prometheus-targets.png b/content/nomad/v1.10.x/img/clusters/prometheus-targets.png
new file mode 100644
index 0000000000..79a92169fe
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/prometheus-targets.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/running-jobs.png b/content/nomad/v1.10.x/img/clusters/running-jobs.png
new file mode 100644
index 0000000000..11d64198b8
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/running-jobs.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/safari-pending.png b/content/nomad/v1.10.x/img/clusters/safari-pending.png
new file mode 100644
index 0000000000..4cae311361
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/safari-pending.png differ
diff --git a/content/nomad/v1.10.x/img/clusters/safart-timeout.png b/content/nomad/v1.10.x/img/clusters/safart-timeout.png
new file mode 100644
index 0000000000..925ccf691c
Binary files /dev/null and b/content/nomad/v1.10.x/img/clusters/safart-timeout.png differ
diff --git a/content/nomad/v1.10.x/img/consul-integration-auth-method.png b/content/nomad/v1.10.x/img/consul-integration-auth-method.png
new file mode 100644
index 0000000000..485cb5d6ac
Binary files /dev/null and b/content/nomad/v1.10.x/img/consul-integration-auth-method.png differ
diff --git a/content/nomad/v1.10.x/img/consul-integration-wi.png b/content/nomad/v1.10.x/img/consul-integration-wi.png
new file mode 100644
index 0000000000..b20fcc3863
Binary files /dev/null and b/content/nomad/v1.10.x/img/consul-integration-wi.png differ
diff --git a/content/nomad/v1.10.x/img/consul-integration-wid-acl-token.png b/content/nomad/v1.10.x/img/consul-integration-wid-acl-token.png
new file mode 100644
index 0000000000..bfb587564b
Binary files /dev/null and b/content/nomad/v1.10.x/img/consul-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.10.x/img/count-dashboard.png b/content/nomad/v1.10.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.10.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.10.x/img/deploy/nomad_fault_tolerance.png b/content/nomad/v1.10.x/img/deploy/nomad_fault_tolerance.png
new file mode 100644
index 0000000000..dcac5802a3
Binary files /dev/null and b/content/nomad/v1.10.x/img/deploy/nomad_fault_tolerance.png differ
diff --git a/content/nomad/v1.10.x/img/deploy/nomad_network_arch.png b/content/nomad/v1.10.x/img/deploy/nomad_network_arch.png
new file mode 100644
index 0000000000..554d0b85e1
Binary files /dev/null and b/content/nomad/v1.10.x/img/deploy/nomad_network_arch.png differ
diff --git a/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1x.png b/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1x.png
new file mode 100644
index 0000000000..6f43b5ce16
Binary files /dev/null and b/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1x.png differ
diff --git a/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1y.png b/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1y.png
new file mode 100644
index 0000000000..9001f17651
Binary files /dev/null and b/content/nomad/v1.10.x/img/deploy/nomad_network_arch_0-1y.png differ
diff --git a/content/nomad/v1.10.x/img/deploy/nomad_reference_diagram.png b/content/nomad/v1.10.x/img/deploy/nomad_reference_diagram.png
new file mode 100644
index 0000000000..b6e7ea2894
Binary files /dev/null and b/content/nomad/v1.10.x/img/deploy/nomad_reference_diagram.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.10.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.10.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.10.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/favicon-16x16.png b/content/nomad/v1.10.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/favicon-194x194.png b/content/nomad/v1.10.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/favicon-32x32.png b/content/nomad/v1.10.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/favicon.ico b/content/nomad/v1.10.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.10.x/img/favicons/mstile-144x144.png b/content/nomad/v1.10.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/mstile-150x150.png b/content/nomad/v1.10.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/mstile-310x150.png b/content/nomad/v1.10.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/mstile-310x310.png b/content/nomad/v1.10.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/mstile-70x70.png b/content/nomad/v1.10.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.10.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.10.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.10.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.10.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.10.x/img/govern/nomad-ui-namespace-dropdown.png b/content/nomad/v1.10.x/img/govern/nomad-ui-namespace-dropdown.png
new file mode 100644
index 0000000000..6a5f534f3a
Binary files /dev/null and b/content/nomad/v1.10.x/img/govern/nomad-ui-namespace-dropdown.png differ
diff --git a/content/nomad/v1.10.x/img/govern/sentinel.jpg b/content/nomad/v1.10.x/img/govern/sentinel.jpg
new file mode 100644
index 0000000000..5ce7fa54b6
Binary files /dev/null and b/content/nomad/v1.10.x/img/govern/sentinel.jpg differ
diff --git a/content/nomad/v1.10.x/img/home-hero-pattern.svg b/content/nomad/v1.10.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.10.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/logo-hashicorp.svg b/content/nomad/v1.10.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.10.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.10.x/img/logo-text.svg b/content/nomad/v1.10.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.10.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempted.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempted.png
new file mode 100644
index 0000000000..b27a4587c9
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempted.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempter.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempter.png
new file mode 100644
index 0000000000..98732b35c8
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-preempter.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-details.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-details.png
new file mode 100644
index 0000000000..a05a0848e1
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-details.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png
new file mode 100644
index 0000000000..8206c0a837
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-resource-utilization.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-resource-utilization.png
new file mode 100644
index 0000000000..f0b9a7dfd9
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-resource-utilization.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-stop-restart.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-stop-restart.png
new file mode 100644
index 0000000000..8cf7246fa9
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-stop-restart.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png
new file mode 100644
index 0000000000..848613275a
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-allocations.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-allocations.png
new file mode 100644
index 0000000000..244b4ca922
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-allocations.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-attributes.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-attributes.png
new file mode 100644
index 0000000000..f87d1d45fe
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-attributes.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-detail.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-detail.png
new file mode 100644
index 0000000000..28234e93de
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-detail.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-drain.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-drain.png
new file mode 100644
index 0000000000..7ef21066c7
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-drain.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-driver-status.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-driver-status.png
new file mode 100644
index 0000000000..8eb6e6766a
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-driver-status.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-events.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-events.png
new file mode 100644
index 0000000000..0b8c674ac3
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-events.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-resource-utilization.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-resource-utilization.png
new file mode 100644
index 0000000000..4171f9a57b
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-client-resource-utilization.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-filters.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-filters.png
new file mode 100644
index 0000000000..735f339c44
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-filters.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-list.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-list.png
new file mode 100644
index 0000000000..bd76f1600e
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-clients-list.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-definition-edit.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-definition-edit.png
new file mode 100644
index 0000000000..b3cebc245c
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-definition-edit.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-deployment-canary.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-deployment-canary.png
new file mode 100644
index 0000000000..e3007d1814
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-deployment-canary.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-filters.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-filters.png
new file mode 100644
index 0000000000..4746eac662
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-filters.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-stop.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-stop.png
new file mode 100644
index 0000000000..b52c057a0b
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-job-stop.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-periodic-force.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-periodic-force.png
new file mode 100644
index 0000000000..234ae0fda7
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-periodic-force.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-server-detail.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-server-detail.png
new file mode 100644
index 0000000000..31729fb9bd
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-server-detail.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-servers-list.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-servers-list.png
new file mode 100644
index 0000000000..6b13e5b901
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-servers-list.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-events.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-events.png
new file mode 100644
index 0000000000..3369dde69d
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-events.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-logs.png b/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-logs.png
new file mode 100644
index 0000000000..a5f94b3b38
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-img-task-logs.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/guide-ui-jobs-list.png b/content/nomad/v1.10.x/img/monitor/guide-ui-jobs-list.png
new file mode 100644
index 0000000000..5e030aa25d
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/guide-ui-jobs-list.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/inspect-cluster.mdx b/content/nomad/v1.10.x/img/monitor/inspect-cluster.mdx
new file mode 100644
index 0000000000..f5c5e725a6
--- /dev/null
+++ b/content/nomad/v1.10.x/img/monitor/inspect-cluster.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Inspect the cluster
+description: |-
+  View the server and client nodes, inspect an individual server or client node,
+  list allocations, and review client events from the Nomad web UI.
+---
+
+# Inspect the cluster
+
+The Web UI can be a powerful tool for monitoring the state of the Nomad cluster
+from an operator's perspective. This includes showing all client nodes, showing
+driver health for client nodes, driver status, resource utilization, allocations
+by client node, and more.
+
+## View cluster clients
+
+From any page, the Clients List page can be accessed from the left-hand
+navigation bar. On narrow screens this navigation bar may need to be opened from
+the top-right menu button. The table lists every client in the cluster and is
+searchable, sortable, and filterable. Each client row in the table shows basic
+information, such as the Node ID, name, state, address, datacenter, and how many
+allocations are running in it.
+
+This view will also live-update as the states of client nodes change.
+
+[![Clients List][img-clients-list]][img-clients-list]
+
+## Filter the client view
+
+If your Nomad cluster has many client nodes, it can be useful to filter the list
+of all client nodes down to only those matching certain facets. The Web UI has
+three facets you can filter by:
+
+1. **Class:** The node of the client, including a dynamically generated list
+   based on the node class of each client node in the cluster.
+
+1. **State:** The state of the cluster, including Initializing, Ready, Down,
+   Ineligible, and Draining.
+
+1. **Datacenter:** The datacenter the client node is in, including a dynamically
+   generated list based on all the datacenters in the cluster.
+
+[![Clients filters][img-clients-filters]][img-clients-filters]
+
+## Inspect an individual client
+
+From the Clients List page, clicking a client node in the table will direct you
+to the Client Detail page for the client node. This page includes all
+information about the client node is live-updated to always present up-to-date
+information.
+
+[![Client Detail][img-client-detail]][img-client-detail]
+
+## Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for client
+nodes. The Web UI uses these metrics to create time-series graphics for the
+current session.
+
+When viewing a client node, resource utilization will automatically start
+logging.
+
+[![Client Resource Utilization][img-client-resource-utilization]][img-client-resource-utilization]
+
+## List client allocations
+
+Allocations belong to jobs and are placed on client nodes. The Client Detail
+page will list all allocations for a client node, including completed, failed,
+and lost allocations, until they are garbage-collected.
+
+This is presented in a searchable table which can additionally be filtered to
+only preempted allocations.
+
+[![Client Allocations][img-client-allocations]][img-client-allocations]
+
+## Review client events
+
+Client nodes will also emit events on meaningful state changes, such as when the
+node becomes ready for scheduling or when a driver becomes unhealthy.
+
+[![Client Events][img-client-events]][img-client-events]
+
+## Check client driver status
+
+Task drivers are additional services running on a client node. Nomad will
+fingerprint and communicate with the task driver to determine if the driver is
+available and healthy. This information is reported through the Web UI on the
+Client Detail page.
+
+[![Client Driver Status][img-client-driver-status]][img-client-driver-status]
+
+## View client attributes
+
+In order to allow job authors to constrain the placement of their jobs, Nomad
+fingerprints the hardware of the node the client agent is running on. This is a
+deeply nested document of properties that the Web UI presents in a scannable
+way.
+
+In addition to the hardware attributes, Nomad operators can annotate a client
+node with [metadata] as part of the client configuration. This metadata is also
+presented on the Client Detail page.
+
+[![Client Attributes][img-client-attributes]][img-client-attributes]
+
+## Monitor a node drain
+
+A routine part of maintaining a Nomad cluster is draining nodes of allocations.
+This can be in preparation of performing operating system upgrades or
+decommissioning an old node in favor of a new VM.
+
+Drains are [performed from the CLI], but the status of a drain can be monitored
+from the Web UI. A client node will state if it is actively draining or
+ineligible for scheduling.
+
+Since drains can be configured in a variety of ways, the Client Detail page will
+also present the details of how the drain is performed.
+
+[![Client Drain][img-client-drain]][img-client-drain]
+
+## View cluster servers
+
+Whereas client nodes are used to run your jobs, server nodes are used to run
+Nomad and maintain availability. From any page, the Servers List page can be
+accessed from the left-hand navigation bar.
+
+The table lists every server node in your cluster. This will be a small list—
+[typically three or five].
+
+[![Servers List][img-servers-list]][img-servers-list]
+
+## Inspect an individual server
+
+Clicking a server node on the Servers List will expand the tags table for the
+server node.
+
+[![Server Detail][img-server-detail]][img-server-detail]
+
+## Secure the UI
+
+Depending on the size of your team and the details of you Nomad deployment, you
+may wish to control which features different internal users have access to. This
+includes limiting who has access to list and manage client nodes and list and
+manage server nodes. You can enforce this with Nomad's access control list
+system.
+
+By default, all features—read and write—are available to all users of the Web
+UI. Check out the [Securing the Web UI with ACLs] tutorial to learn how to prevent
+anonymous users from having write permissions as well as how to continue to use
+Web UI write features as a privileged user.
+
+## Continue your exploration
+
+Now that you have explored how to inspect the state of your cluster through the
+Nomad UI, you will next learn some considerations you should keep in mind when
+using the Nomad UI.
+
+[img-client-allocations]: /img/nomad/web-ui/guide-ui-img-client-allocations.png
+[img-client-attributes]: /img/nomad/web-ui/guide-ui-img-client-attributes.png
+[img-client-detail]: /img/nomad/web-ui/guide-ui-img-client-detail.png
+[img-client-drain]: /img/nomad/web-ui/guide-ui-img-client-drain.png
+[img-client-driver-status]: /img/nomad/web-ui/guide-ui-img-client-driver-status.png
+[img-client-events]: /img/nomad/web-ui/guide-ui-img-client-events.png
+[img-client-resource-utilization]: /img/nomad/web-ui/guide-ui-img-client-resource-utilization.png
+[img-clients-filters]: /img/nomad/web-ui/guide-ui-img-clients-filters.png
+[img-clients-list]: /img/nomad/web-ui/guide-ui-img-clients-list.png
+[img-server-detail]: /img/nomad/web-ui/guide-ui-img-server-detail.png
+[img-servers-list]: /img/nomad/web-ui/guide-ui-img-servers-list.png
+[metadata]: /nomad/docs/configuration/client#meta
+[performed from the cli]: /nomad/tutorials/manage-clusters/node-drain
+[securing the web ui with acls]: /nomad/tutorials/access-control
+[typically three or five]: /nomad/docs/architecture/consensus#deployment-table
diff --git a/content/nomad/v1.10.x/img/monitor/inspect-workloads.mdx b/content/nomad/v1.10.x/img/monitor/inspect-workloads.mdx
new file mode 100644
index 0000000000..84c49e0d31
--- /dev/null
+++ b/content/nomad/v1.10.x/img/monitor/inspect-workloads.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Inspect job workloads
+description: |-
+  Inspect jobs, allocations, and tasks in the Nomad web UI and interact
+  with these objects to perform operations like restart an allocation or
+  stop a job.
+---
+
+# Inspect job workloads
+
+The Web UI can be a powerful companion when monitoring and debugging jobs
+running in Nomad. The Web UI will list all jobs, link jobs to allocations,
+allocations to client nodes, client nodes to driver health, and much more.
+
+## List jobs
+
+The first page you will arrive at in the Web UI is the Jobs List page. Here you
+will find every job for a namespace in a region. The table of jobs is
+searchable, sortable, and filterable. Each job row in the table shows basic
+information, such as job name, status, type, and priority, as well as richer
+information such as a visual representation of all allocation statuses.
+
+This view will also live-update as jobs get submitted, get purged, and change
+status.
+
+[![Jobs List][img-jobs-list]][img-jobs-list]
+
+## Filter job view
+
+If your Nomad cluster has many jobs, it can be useful to filter the list of all
+jobs down to only those matching certain facets. The Web UI has four facets you
+can filter by:
+
+1. **Type:** The type of job, including Batch, Parameterized, Periodic, Service,
+   and System.
+
+1. **Status:** The status of the job, including Pending, Running, and Dead.
+
+1. **Datacenter:** The datacenter the job is running in, including a dynamically
+   generated list based on the jobs in the namespace.
+
+1. **Prefix:** The possible common naming prefix for a job, including a
+   dynamically generated list based on job names up to the first occurrence of
+   `-`, `.`, and `_`. Only prefixes that match multiple jobs are included.
+
+[![Job Filters][img-job-filters]][img-job-filters]
+
+## Inspect an allocation
+
+In Nomad, allocations are the schedulable units of work. This is where runtime
+metrics begin to surface. An allocation is composed of one or more tasks, and
+the utilization metrics for tasks are aggregated so they can be observed at the
+allocation level.
+
+### Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for tasks
+and allocations. The Web UI uses these metrics to create time-series graphs for
+the current session.
+
+When viewing an allocation, resource utilization will automatically start
+logging.
+
+[![Allocation Resource Utilization][img-alloc-resource-utilization]][img-alloc-resource-utilization]
+
+### Review task events
+
+When Nomad places, prepares, and starts a task, a series of task events are
+emitted to help debug issues in the event that the task fails to start.
+
+Task events are listed on the Task Detail page and live-update as Nomad handles
+managing the task.
+
+[![Task Events][img-task-events]][img-task-events]
+
+### View rescheduled allocations
+
+Allocations will be placed on any client node that satisfies the constraints of
+the job definition. There are events, however, that will cause Nomad to
+reschedule allocations, (e.g., node failures).
+
+Allocations can be configured [in the job definition to reschedule] to a
+different client node if the allocation ends in a failed status. This will
+happen after the task has exhausted its [local restart attempts].
+
+The end result of this automatic procedure is a failed allocation and that
+failed allocation's rescheduled successor. Since Nomad handles all of this
+automatically, the Web UI makes sure to explain the state of allocations through
+icons and linking previous and next allocations in a reschedule chain.
+
+[![Allocation Reschedule Icon][img-alloc-reschedule-icon]][img-alloc-reschedule-icon]
+
+[![Allocation Reschedule Details][img-alloc-reschedule-details]][img-alloc-reschedule-details]
+
+### Unhealthy driver
+
+Given the nature of long-lived processes, it's possible for the state of the
+client node an allocation is scheduled on to change during the lifespan of the
+allocation. Nomad attempts to monitor pertinent conditions including driver
+health.
+
+The Web UI denotes when a driver an allocation depends on is unhealthy on the
+client node the allocation is running on.
+
+[![Allocation Unhealthy Driver][img-alloc-unhealthy-driver]][img-alloc-unhealthy-driver]
+
+### Preempted allocations
+
+Much like how Nomad will automatically reschedule allocations, Nomad will
+automatically preempt allocations when necessary. When monitoring allocations in
+Nomad, it's useful to know what allocations were preempted and what job caused
+the preemption.
+
+The Web UI makes sure to tell this full story by showing which allocation caused
+an allocation to be preempted as well as the opposite: what allocations an
+allocation preempted. This makes it possible to traverse down from a job to a
+preempted allocation, to the allocation that caused the preemption, to the job
+that the preempting allocation is for.
+
+[![Allocation Preempter][img-alloc-preempter]][img-alloc-preempter]
+
+[![Allocation Preempted][img-alloc-preempted]][img-alloc-preempted]
+
+## Review task logs
+
+A task will typically emit log information to `stdout` and `stderr`. Nomad
+captures these logs and exposes them through an API. The Web UI uses these APIs
+to offer `head`, `tail`, and streaming logs from the browser.
+
+The Web UI will first attempt to directly connect to the client node the task is
+running on. Typically, client nodes are not accessible from the public internet.
+If this is the case, the Web UI will fall back and proxy to the client node from
+the server node with no loss of functionality.
+
+[![Task Logs][img-task-logs]][img-task-logs]
+
+~> Not all browsers support streaming HTTP requests. In the event that streaming
+is not supported, logs will still be followed using interval polling.
+
+## Restart or stop an allocation or task
+
+Nomad allows for restarting and stopping individual allocations and tasks. When
+a task is restarted, Nomad will perform a local restart of the task. When an
+allocation is stopped, Nomad will mark the allocation as complete and perform a
+reschedule onto a different client node.
+
+Both of these features are also available in the Web UI.
+
+[![Allocation Stop and Restart][img-alloc-stop-restart]][img-alloc-stop-restart]
+
+## Force a periodic instance
+
+Periodic jobs are configured like a cron job. Sometimes, you might want to start
+the job before the its next scheduled run time. Nomad calls this a [periodic
+force] and it can be done from the Web UI on the Job Overview page for a
+periodic job.
+
+[![Periodic Force][img-periodic-force]][img-periodic-force]
+
+## Submit a new version of a job
+
+From the Job Definition page, a job can be edited. After clicking the Edit
+button in the top-right corner of the code window, the job definition JSON
+becomes editable. The edits can then be planned and scheduled.
+
+[![Job Definition Edit][img-job-definition-edit]][img-job-definition-edit]
+
+~> Since each job within a namespace must have a unique name, it is possible to
+submit a new version of a job from the Run Job screen. Always review the plan
+output.
+
+## Monitor a deployment
+
+When a system or service job includes the [`update` stanza], a deployment is
+created upon job submission. Job deployments can be monitored in realtime from
+the Web UI.
+
+The Web UI will show as new allocations become placed, tallying towards the
+expected total, and tally allocations as they become healthy or unhealthy.
+
+Optionally, a job may use canary deployments to allow for additional health
+checks or manual testing before a full roll out. If a job uses canaries and is
+not configured to automatically promote the canary, the canary promotion
+operation can be done from the Job Overview page in the Web UI.
+
+[![Job Deployment with Canary Promotion][img-job-deployment-canary]][img-job-deployment-canary]
+
+## Stop a job
+
+Jobs can be stopped from the Job Overview page. Stopping a job will gracefully
+stop all allocations, marking them as complete, and freeing up resources in the
+cluster.
+
+[![Job Stop][img-job-stop]][img-job-stop]
+
+## Continue your exploration
+
+Now that you have explored operations that can be performed with jobs through
+the Nomad UI, learn how to inspect the state of your cluster using the Nomad UI.
+
+[`update` stanza]: /nomad/docs/job-specification/update
+[img-alloc-preempted]: /img/nomad/web-ui/guide-ui-img-alloc-preempted.png
+[img-alloc-preempter]: /img/nomad/web-ui/guide-ui-img-alloc-preempter.png
+[img-alloc-reschedule-details]: /img/nomad/web-ui/guide-ui-img-alloc-reschedule-details.png
+[img-alloc-reschedule-icon]: /img/nomad/web-ui/guide-ui-img-alloc-reschedule-icon.png
+[img-alloc-resource-utilization]: /img/nomad/web-ui/guide-ui-img-alloc-resource-utilization.png
+[img-alloc-stop-restart]: /img/nomad/web-ui/guide-ui-img-alloc-stop-restart.png
+[img-alloc-unhealthy-driver]: /img/nomad/web-ui/guide-ui-img-alloc-unhealthy-driver.png
+[img-job-definition-edit]: /img/nomad/web-ui/guide-ui-img-job-definition-edit.png
+[img-job-deployment-canary]: /img/nomad/web-ui/guide-ui-img-job-deployment-canary.png
+[img-job-filters]: /img/nomad/web-ui/guide-ui-img-job-filters.png
+[img-job-stop]: /img/nomad/web-ui/guide-ui-img-job-stop.png
+[img-jobs-list]: /img/nomad/web-ui/guide-ui-jobs-list.png
+[img-periodic-force]: /img/nomad/web-ui/guide-ui-img-periodic-force.png
+[img-task-events]: /img/nomad/web-ui/guide-ui-img-task-events.png
+[img-task-logs]: /img/nomad/web-ui/guide-ui-img-task-logs.png
+[in the job definition to reschedule]: /nomad/docs/job-specification/reschedule
+[local restart attempts]: /nomad/docs/job-specification/restart
+[periodic force]: /nomad/commands/job/periodic-force
+[securing the web ui with acls]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/alloc-associations-across-dcs.png b/content/nomad/v1.10.x/img/monitor/topo-viz/alloc-associations-across-dcs.png
new file mode 100644
index 0000000000..3fd762d215
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/alloc-associations-across-dcs.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-associations.png b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-associations.png
new file mode 100644
index 0000000000..0a80af4890
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-associations.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-panel.png b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-panel.png
new file mode 100644
index 0000000000..c278b6ec5a
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-panel.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-tooltip.png b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-tooltip.png
new file mode 100644
index 0000000000..f7b21ae092
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/allocation-tooltip.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/client-panel.png b/content/nomad/v1.10.x/img/monitor/topo-viz/client-panel.png
new file mode 100644
index 0000000000..da4cda160d
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/client-panel.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/client-with-many-allocs.png b/content/nomad/v1.10.x/img/monitor/topo-viz/client-with-many-allocs.png
new file mode 100644
index 0000000000..cc3b763d82
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/client-with-many-allocs.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-panel.png b/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-panel.png
new file mode 100644
index 0000000000..549c5a3bcf
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-panel.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-view.png b/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-view.png
new file mode 100644
index 0000000000..c55fb6cbcc
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/cluster-view.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/empty-clients.png b/content/nomad/v1.10.x/img/monitor/topo-viz/empty-clients.png
new file mode 100644
index 0000000000..95de8d36ea
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/empty-clients.png differ
diff --git a/content/nomad/v1.10.x/img/monitor/topo-viz/topo-viz-link.png b/content/nomad/v1.10.x/img/monitor/topo-viz/topo-viz-link.png
new file mode 100644
index 0000000000..4e560410d6
Binary files /dev/null and b/content/nomad/v1.10.x/img/monitor/topo-viz/topo-viz-link.png differ
diff --git a/content/nomad/v1.10.x/img/networking/bridge.png b/content/nomad/v1.10.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.10.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.10.x/img/networking/docker_bridge.png b/content/nomad/v1.10.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.10.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.10.x/img/networking/port_mapping.png b/content/nomad/v1.10.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.10.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-architecture-global.png b/content/nomad/v1.10.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-architecture-region.png b/content/nomad/v1.10.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-bg-pattern.svg b/content/nomad/v1.10.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.10.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.10.x/img/nomad-bridge-network.png b/content/nomad/v1.10.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-data-model.png b/content/nomad/v1.10.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-evaluation-flow.png b/content/nomad/v1.10.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-kubernetes.png b/content/nomad/v1.10.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-numa.png b/content/nomad/v1.10.x/img/nomad-numa.png
new file mode 100644
index 0000000000..0609d7e196
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-numa.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-panel-learn.svg b/content/nomad/v1.10.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.10.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.10.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.10.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.10.x/img/nomad-pe-cores.png b/content/nomad/v1.10.x/img/nomad-pe-cores.png
new file mode 100644
index 0000000000..e11c011d6e
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-pe-cores.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-ui-block.png b/content/nomad/v1.10.x/img/nomad-ui-block.png
new file mode 100644
index 0000000000..c33ac81cea
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-ui-block.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-vars-leader-election-sdk.png b/content/nomad/v1.10.x/img/nomad-vars-leader-election-sdk.png
new file mode 100644
index 0000000000..a547218579
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-vars-leader-election-sdk.png differ
diff --git a/content/nomad/v1.10.x/img/nomad-workload.png b/content/nomad/v1.10.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.10.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.10.x/img/og-image.png b/content/nomad/v1.10.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.10.x/img/og-image.png differ
diff --git a/content/nomad/v1.10.x/img/pattern.svg b/content/nomad/v1.10.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.10.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/practice-pattern.svg b/content/nomad/v1.10.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.10.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/secure/acl.jpg b/content/nomad/v1.10.x/img/secure/acl.jpg
new file mode 100644
index 0000000000..c892dd3928
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/acl.jpg differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-configure-callback-action.png b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-action.png
new file mode 100644
index 0000000000..60ef05bbdc
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-action.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-configure-callback-flow.png b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-flow.png
new file mode 100644
index 0000000000..74c6343818
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-flow.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-configure-callback-rule.png b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-rule.png
new file mode 100644
index 0000000000..01d3d632b1
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-rule.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-configure-callback-urls.png b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-urls.png
new file mode 100644
index 0000000000..496812fe8a
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-configure-callback-urls.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-configure-user-metadata.png b/content/nomad/v1.10.x/img/secure/auth0-configure-user-metadata.png
new file mode 100644
index 0000000000..6a33389ae5
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-configure-user-metadata.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-create-user.png b/content/nomad/v1.10.x/img/secure/auth0-create-user.png
new file mode 100644
index 0000000000..116bfd6af2
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-create-user.png differ
diff --git a/content/nomad/v1.10.x/img/secure/auth0-get-application-params.png b/content/nomad/v1.10.x/img/secure/auth0-get-application-params.png
new file mode 100644
index 0000000000..6fbb48c471
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/auth0-get-application-params.png differ
diff --git a/content/nomad/v1.10.x/img/secure/nomad-ui-jobs-signed-in.png b/content/nomad/v1.10.x/img/secure/nomad-ui-jobs-signed-in.png
new file mode 100644
index 0000000000..43083d5e8d
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/nomad-ui-jobs-signed-in.png differ
diff --git a/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-button.png b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-button.png
new file mode 100644
index 0000000000..f6a6d53436
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-button.png differ
diff --git a/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-form.png b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-form.png
new file mode 100644
index 0000000000..daf1184a38
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-login-form.png differ
diff --git a/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-signed-in.png b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-signed-in.png
new file mode 100644
index 0000000000..0fca433b82
Binary files /dev/null and b/content/nomad/v1.10.x/img/secure/nomad-ui-oidc-signed-in.png differ
diff --git a/content/nomad/v1.10.x/img/usecase-callout-pattern.svg b/content/nomad/v1.10.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.10.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/usecase-hero-pattern.svg b/content/nomad/v1.10.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.10.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.10.x/img/vault-integration-auth-method.png b/content/nomad/v1.10.x/img/vault-integration-auth-method.png
new file mode 100644
index 0000000000..b6c1d601b9
Binary files /dev/null and b/content/nomad/v1.10.x/img/vault-integration-auth-method.png differ
diff --git a/content/nomad/v1.10.x/img/vault-integration-auth-overview.png b/content/nomad/v1.10.x/img/vault-integration-auth-overview.png
new file mode 100644
index 0000000000..ad26bed43a
Binary files /dev/null and b/content/nomad/v1.10.x/img/vault-integration-auth-overview.png differ
diff --git a/content/nomad/v1.10.x/img/vault-integration-wid-acl-token.png b/content/nomad/v1.10.x/img/vault-integration-wid-acl-token.png
new file mode 100644
index 0000000000..7fd4b406ea
Binary files /dev/null and b/content/nomad/v1.10.x/img/vault-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.10.x/redirects.jsonc b/content/nomad/v1.10.x/redirects.jsonc
new file mode 100644
index 0000000000..0f754b9bb7
--- /dev/null
+++ b/content/nomad/v1.10.x/redirects.jsonc
@@ -0,0 +1,1053 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+
+  /**
+   * /s/* redirects for useful links that need a stable URL but we may need to
+   * change its destination in the future. Some of these used in CLI output.
+   */
+  {
+    "source": "/nomad/s/envoy-bootstrap-error",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/networking/consul/service-mesh#troubleshooting",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/vault-workload-identity-migration",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/v1.8.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/port-plan-failure",
+    "destination": "https://github.com/hashicorp/nomad/issues/9506",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination":
+      "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/vault-integration",
+    "destination": "/nomad/docs/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-integration",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-connect",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/agent/source",
+    "destination": "/nomad/tools/autoscaling/agent/policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/remote/:slug*",
+    "destination": "nomad/plugins/drivers/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/community/lxc",
+    "destination": "/nomad/plugins/drivers/community/",
+    "permanent": true,
+  },
+  // CSI plugins moved under new storage path alongside new host volume plugins
+  {
+    "source": "/nomad/docs/concepts/plugins/csi",
+    "destination": "/nomad/docs/concepts/plugins/storage/csi",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/client",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/installation",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/devices",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community/usb",
+    "destination": "/nomad/plugins/devices/usb",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/containerd",
+    "destination": "https://github.com/Roblox/nomad-driver-containerd",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/pledge",
+    "destination": "https://github.com/shoenig/nomad-pledge-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/firecracker-task-driver",
+    "destination": "https://github.com/cneira/firecracker-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/jail-task-driver",
+    "destination": "https://github.com/cneira/jail-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/lightrun",
+    "destination": "https://docs.lightrun.com/integrations/nomad/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/pot",
+    "destination": "https://github.com/bsdpot/nomad-pot-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/rookout",
+    "destination": "https://github.com/Rookout/rookout-nomad-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/singularity",
+    "destination": "https://github.com/hpcng/nomad-driver-singularity",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/nspawn",
+    "destination": "https://github.com/JanMa/nomad-driver-nspawn",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/iis",
+    "destination": "https://github.com/Roblox/nomad-driver-iis",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/nomad-iis",
+    "destination": "https://nomad-iis.sevensolutions.cc/",
+    "permanent": true,
+  },
+  /**
+   * Nomad IA redirects
+   */
+  {
+    "source": "/nomad/intro",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/intro/use-cases",
+    "destination": "/nomad/docs/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/intro/vs/:path*",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/nomad-vs-kubernetes/:path*",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/quickstart",
+    "destination": "/nomad/docs/quickstart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/windows-service",
+    "destination": "/nomad/docs/deploy/production/windows-service",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/production/:path*",
+    "destination": "/nomad/docs/deploy/production/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/architecture",
+    "destination": "/nomad/docs/architecture",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/architecture/federation",
+    "destination": "/nomad/docs/architecture/cluster/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl",
+    "destination": "/nomad/docs/secure/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/architecture/acl",
+    "destination": "/nomad/docs/secure/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/consensus",
+    "destination": "/nomad/docs/architecture/cluster/consensus",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/cpu",
+    "destination": "/nomad/docs/architecture/cpu",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/gossip",
+    "destination": "/nomad/docs/architecture/security/gossip",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/node-pools",
+    "destination": "/nomad/docs/architecture/cluster/node-pools",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/security",
+    "destination": "/nomad/docs/architecture/security",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/stateful-workloads",
+    "destination": "/nomad/docs/architecture/storage/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/storage/:path*",
+    "destination": "/nomad/docs/architecture/storage/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/job-specification/hcl2/:path*",
+    "destination": "/nomad/docs/reference/hcl2/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/metrics-reference",
+    "destination": "/nomad/docs/reference/metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime",
+    "destination": "/nomad/docs/reference/runtime-environment-settings",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime/environment",
+    "destination": "/nomad/docs/reference/runtime-environment-settings",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime/interpolation",
+    "destination": "/nomad/docs/reference/runtime-variable-interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/enterprise/sentinel",
+    "destination": "/nomad/docs/reference/sentinel-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/drivers/:path*",
+    "destination": "/nomad/docs/deploy/task-driver/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/nomad-agent",
+    "destination": "/nomad/docs/deploy/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/federation",
+    "destination": "/nomad/docs/deploy/clusters/federation-considerations",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/federation/failure",
+    "destination": "/nomad/docs/deploy/clusters/federation-failure-scenarios",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/garbage-collection",
+    "destination": "/nomad/docs/manage/garbage-collection",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/key-management",
+    "destination": "/nomad/docs/manage/key-management",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/benchmarking",
+    "destination": "/nomad/docs/scale/benchmarking",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/scheduling/scheduling",
+    "destination": "/nomad/docs/concepts/scheduling/how-scheduling-works",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/schedulers",
+    "destination": "/nomad/docs/concepts/scheduling/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/ipv6-support",
+    "destination": "/nomad/docs/networking/ipv6",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/monitoring-nomad",
+    "destination": "/nomad/docs/monitor",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl/auth-methods/oidc",
+    "destination": "/nomad/docs/secure/authentication/oidc",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl/auth-methods/jwt",
+    "destination": "/nomad/docs/secure/authentication/jwt",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/aws-oidc-provider",
+    "destination": "/nomad/docs/secure/workload-identity/aws-oidc-provider",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/who-uses-nomad",
+    "destination": "/nomad/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/networking/service-mesh",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul/acl",
+    "destination": "/nomad/docs/secure/acl/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul/service-mesh",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/vault/:path*",
+    "destination": "/nomad/docs/secure/vault/:path*",
+    "permanent": true,
+  },
+  // section index pages no longer in existence
+  {
+    "source": "/nomad/docs/operations",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  /* redirects for versioned docs in 1.9, 1.8 */
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/what-is-nomad/",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/quickstart/",
+    "destination": "/nomad/docs/:version/install/quickstart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/",
+    "destination": "/nomad/docs/:version/concepts/architecture",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/consensus/",
+    "destination": "/nomad/docs/:version/concepts/consensus",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/federation/",
+    "destination": "/nomad/docs/:version/concepts/architecture/federation",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/node-pools/",
+    "destination": "/nomad/docs/:version/concepts/node-pools",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cpu/",
+    "destination": "/nomad/docs/:version/concepts/cpu",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/security/",
+    "destination": "/nomad/docs/:version/concepts/security",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/security/gossip/",
+    "destination": "/nomad/docs/:version/concepts/gossip",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/storage/:slug*",
+    "destination": "/nomad/docs/:version/concepts/plugins/storage/:slug*",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/concepts/scheduling/how-scheduling-works/",
+    "destination": "/nomad/docs/:version/concepts/scheduling/scheduling",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/concepts/scheduling/schedulers/",
+    "destination": "/nomad/docs/:version/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/intro/use-cases/",
+    "destination": "/nomad/docs/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/:slug*",
+    "destination": "/nomad/docs/:version/install/:slug*",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/production/windows-service/",
+    "destination": "/nomad/docs/:version/install/windows-service",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/nomad-agent/",
+    "destination": "/nomad/docs/:version/operations/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federation-considerations/",
+    "destination": "/nomad/docs/:version/operations/federation",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federation-failure-scenarios/",
+    "destination": "/nomad/docs/:version/operations/federation/failure",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/task-driver/:slug*",
+    "destination": "/nomad/docs/:version/drivers/:slug*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/",
+    "destination": "/nomad/docs/:version/integrations",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/garbage-collection/",
+    "destination": "/nomad/docs/:version/operations/garbage-collection",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/key-management/",
+    "destination": "/nomad/docs/:version/operations/key-management",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/",
+    "destination": "/nomad/docs/:version/operations/monitoring-nomad",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/service-mesh/",
+    "destination": "/nomad/docs/:version/networking/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/",
+    "destination": "/nomad/docs/:version/integrations/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/consul/",
+    "destination": "/nomad/docs/:version/integrations/consul/acl",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/service-mesh/",
+    "destination": "/nomad/docs/:version/integrations/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/scale/benchmarking/",
+    "destination": "/nomad/docs/:version/operations/benchmarking",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/jwt/",
+    "destination": "/nomad/docs/:version/concepts/acl/auth-methods/jwt",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/oidc/",
+    "destination": "/nomad/docs/:version/concepts/acl/auth-methods/oidc",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/",
+    "destination": "/nomad/docs/:version/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/",
+    "destination": "/nomad/docs/:version/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/acl/",
+    "destination": "/nomad/docs/:version/integrations/vault/acl",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/workload-identity/aws-oidc-provider/",
+    "destination": "/nomad/docs/:version/operations/aws-oidc-provider",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/task-driver/",
+    "destination": "/nomad/docs/:version/drivers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/hcl2/",
+    "destination": "/nomad/docs/:version/job-specification/hcl2",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/metrics/",
+    "destination": "/nomad/docs/:version/operations/metrics-reference",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-settings/",
+    "destination": "/nomad/docs/:version/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-variable-interpolation/",
+    "destination": "/nomad/docs/:version/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/sentinel-policy/",
+    "destination": "/nomad/docs/:version/enterprise/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/use-cases/",
+    "destination": "/nomad/docs/:version/who-uses-nomad",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-variables/",
+    "destination": "/nomad/docs/:version/runtime/",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-settings/",
+    "destination": "/nomad/docs/:version/runtime",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/",
+    "destination": "/nomad/tutorials/archive/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/bootstrap/",
+    "destination": "/nomad/tutorials/archive/access-control-bootstrap",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/policies/create-policy/",
+    "destination": "/nomad/tutorials/archive/access-control-create-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/policies/",
+    "destination": "/nomad/tutorials/archive/access-control-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/",
+    "destination": "/nomad/tutorials/archive/access-control-tokens",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-auth0/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-auth0",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-pkce-jwt/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-keycloak",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/vault/",
+    "destination": "/nomad/tutorials/archive/vault-nomad-secrets",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/",
+    "destination": "/nomad/tutorials/archive/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/affinity/",
+    "destination": "/nomad/tutorials/archive/affinity",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/preemption/",
+    "destination": "/nomad/tutorials/archive/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/spread/",
+    "destination": "/nomad/tutorials/archive/spread",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/",
+    "destination": "/nomad/tutorials/archive/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/resource-quotas/",
+    "destination": "/nomad/tutorials/archive/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/sentinel/",
+    "destination": "/nomad/tutorials/archive/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/event-stream/",
+    "destination": "/nomad/tutorials/archive/event-stream",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/workload-identity/vault-acl/",
+    "destination": "/nomad/tutorials/archive/vault-acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/vault/",
+    "destination": "/nomad/tutorials/archive/vault-nomad-secrets",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/",
+    "destination": "/nomad/tutorials/archive/failures",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/check-restart/",
+    "destination": "/nomad/tutorials/archive/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/reschedule/",
+    "destination": "/nomad/tutorials/archive/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/restart/",
+    "destination": "/nomad/tutorials/archive/failures-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/nomad-actions/",
+    "destination": "/nomad/tutorials/archive/job-spec-actions",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/blue-green-canary/",
+    "destination":
+      "/nomad/tutorials/archive/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/rolling/",
+    "destination": "/nomad/tutorials/archive/job-rolling-update",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/exit-signals/",
+    "destination": "/nomad/tutorials/archive/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/",
+    "destination": "/nomad/tutorials/archive/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/autopilot/",
+    "destination": "/nomad/tutorials/archive/autopilot",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/connect-nodes/",
+    "destination": "/nomad/tutorials/archive/clustering",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federate-regions/",
+    "destination": "/nomad/tutorials/archive/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/multiregion/",
+    "destination": "/nomad/tutorials/archive/multiregion-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/namespaces/",
+    "destination": "/nomad/tutorials/archive/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/migrate-workloads/",
+    "destination": "/nomad/tutorials/archive/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/outage-recovery/",
+    "destination": "/nomad/tutorials/archive/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/reverse-proxy-ui/",
+    "destination": "/nomad/tutorials/archive/reverse-proxy-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/",
+    "destination": "/nomad/tutorials/archive/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/logs/",
+    "destination": "/nomad/tutorials/archive/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/configure-tasks/",
+    "destination": "/nomad/tutorials/archive/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/inspect/",
+    "destination": "/nomad/tutorials/archive/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/create-job/",
+    "destination": "/nomad/tutorials/archive/jobs-submit",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/utilization-metrics/",
+    "destination": "/nomad/tutorials/archive/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/versions/",
+    "destination": "/nomad/tutorials/archive/jobs-version",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/advanced-usage/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-detailed-usage",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-intro",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/create-packs/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-writing-packs",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)archiving b/c LXC plugin removed a while ago/",
+    "destination": "/nomad/tutorials/archive/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-vault/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-vault",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/static-host-volumes/",
+    "destination": "/nomad/tutorials/archive/exec-users-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/csi-volumes/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads-csi-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/dynamic-host-volumes/",
+    "destination":
+      "/nomad/tutorials/archive/stateful-workloads-dynamic-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/static-host-volumes/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/task-dependencies/",
+    "destination": "/nomad/tutorials/archive/task-dependencies-interjob",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/format-cli-output/",
+    "destination": "/nomad/tutorials/archive/format-output-with-templates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/go-template-syntax/",
+    "destination": "/nomad/tutorials/archive/go-template-syntax",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/",
+    "destination": "/nomad/tutorials/archive/security-concepts",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/tls/",
+    "destination": "/nomad/tutorials/archive/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/gossip-encryption/",
+    "destination": "/nomad/tutorials/archive/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/nomad-variables/",
+    "destination": "/nomad/tutorials/archive/variables-tasks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/cluster-topology/",
+    "destination": "/nomad/tutorials/archive/topology-visualization",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/inspect-cluster/",
+    "destination": "/nomad/tutorials/archive/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/inspect-workloads/",
+    "destination": "/nomad/tutorials/archive/web-ui-workload-info",
+    "permanent": true,
+  },
+  // Move content to new plugin authoring guide
+  {
+    "source": "/nomad/docs/concepts/plugins",
+    "destination": "/nomad/plugins/author",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/base",
+    "destination": "/nomad/plugins/author",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/task-drivers",
+    "destination": "/nomad/plugins/author/task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/devices",
+    "destination": "/nomad/plugins/author/device",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/cni",
+    "destination": "/nomad/docs/networking/cni",
+    "permanent": true,
+  },
+  /* commands redirects grouped together */
+  {
+    "source": "/nomad/docs/commands/:path*",
+    "destination": "/nomad/commands/:path*",
+    "permanent": true,
+  },
+  /* redirect incoming nomad/docs/v1.8.x/commands to
+   * new /commands path in 1.9, 1.8
+   */
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/commands/:path*",
+    "destination": "/nomad/commands/:version/:path*",
+    "permanent": true,
+  },
+  /* redirects to commands prior to version 1.8 for version pick list entries */
+  {
+    "source": "/nomad/commands/:version(v1\\.(?:7|6|5|4|3|2|1|0)\\.x)/:path*",
+    "destination": "/nomad/docs/:version/commands/:path*",
+    "permanent": true,
+  },
+  // redirects for v0.11.x, 0.12.x
+  {
+    "source": "/nomad/commands/:version(v0\\.(?:11|12)\\.x)/:path*",
+    "destination": "/nomad/docs/:version/commands/:path*",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.11.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..37b871461c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,365 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+@include 'api-docs/auth-method-params.mdx'
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "redacted",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+The parameters are the same as Create.
+
+@include 'api-docs/auth-method-params.mdx'
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "redacted",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                               | Produces       |
+| -------- | ---------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+[private key jwt]: https://oauth.net/private-key-jwt/
+[concepts-assertions]: /nomad/docs/secure/authentication/oidc#client-assertions
+[x5t]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.7
+[x5t#S256]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8
+[pkce]: https://oauth.net/2/pkce/
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.11.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..9ad1c50a13
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/identities.mdx b/content/nomad/v1.11.x/content/api-docs/acl/identities.mdx
new file mode 100644
index 0000000000..05652a3ccd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/identities.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: ACL Identities - HTTP API
+description: |-
+  Use the `/acl/identity` endpoint to create client introduction identity tokens.
+---
+
+# ACL identities HTTP API
+
+Use the `/acl/identity` endpoint to create client introduction identity tokens.
+
+## Create client introduction identity
+
+This endpoint creates an ACL identity for use with client introduction.
+
+| Method | Path                                         | Produces           |
+|--------|----------------------------------------------|--------------------|
+| `POST` | `/v1/acl/identity/client-introduction-token` | `application/json` |
+
+The following table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `NodeName` `(string: <optional>)` - The name of the node to which the introduction token is
+  scoped. If not specified, the value is left empty.
+
+- `NodePool` `(string: <optional>)` - The node pool to which the introduction token is scoped.
+  If not specified, the value is `default`.
+
+- `TTL` `(string: <optional>)` - The TTL to apply to the introduction token. If not specified, the
+  server configured default value is used.
+
+### Sample payload
+
+```json
+{
+  "NodeName": "node-338ef6e9",
+  "NodePool": "platform",
+  "TTL": "15m"
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/identity/client-introduction-token
+```
+
+### Sample response
+
+```json
+{
+  "JWT":"eyJhbGciOiJSUzI1NiIsImtpZCI6IjFlMGJhMmM3LWE5ODktNzI2Ni1kZDdlLWMyYzBkZmU3OTg4OSIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJleHAiOjE3NTUwNzE2NDgsImlhdCI6MTc1NTA3MDc0OCwianRpIjoiYWVmMGE3NzUtNzQ0MS1jNjA2LTIyY2UtNGRhZGY4YzExYzlmIiwibmJmIjoxNzU1MDcwNzQ4LCJub21hZF9ub2RlX25hbWUiOiJub2RlLTMzOGVmNmU5Iiwibm9tYWRfbm9kZV9wb29sIjoicGxhdGZvcm0iLCJzdWIiOiJub2RlLWludHJvZHVjdGlvbjpnbG9iYWw6cGxhdGZvcm06bm9kZS0zMzhlZjZlOTpkZWZhdWx0In0.nCyqdlqStkjoX64p-AN0DA90eIbwVj9A-cYRtabEdTmqkocz-31YY9MlCKv0v6oU4AYHwUF-kBXG7LWYQgk2RKgWh-KttjfT1kJaS0k9jfiyVFxrLuz2F_KZO8kBzZFGS4bQw6nw0-6uR0tkkZvKVwrq6L3hyFUWpgB-gI2BidIZz7Y02RNtcpStjv0e-1DVyzFxInIuTnX-Z2fRAZz7w5e1nMtDFpnZgPM3nrjg2ZAKKiX9GiZT9IPip_KRsqdAN5TWkHlNQ7WmdzrIBZNe1IX15JWC7wSyCJn-n-FSSRc71X1P2ZYaOUzmJiGr-x7M95jDZD6CGDykfsD9pFQR_A"
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/index.mdx b/content/nomad/v1.11.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..86a7bea3f7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/docs/secure/acl).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/login.mdx b/content/nomad/v1.11.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.11.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.11.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..97535fc338
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,231 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | -----   ---------- | ------------------ |
+| `GET`  | `/v1/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                          | Produces       |
+| ------ | ----------------------------- | -------------- |
+| `POST` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given job,
+  group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - Attach the policy to the job in this
+    namespace.  Required if `JobID` is set.
+
+  - `JobID` `(string)` - Attach the policy to this job. Required to use `JobACL`.
+
+  - `Group` `(string: <optional>)` - Attach the policy to this group within the
+    job.  Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - Attach the policy to this task within the job.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Read Self Policy
+
+This endpoint reads the ACL policies associated with the current workload
+identity or any authenticated request.
+
+| Method | Path                  | Produces           |
+|--------|-----------------------|--------------------|
+| `GET`  | `/v1/acl/policy/self` | `application/json` |
+
+This table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+|------------------|-------------------|---------------------------------|
+| `YES`            | `all`             | Any valid Workload Identity JWT |
+
+### Sample Request
+
+```shell-session
+$ curl --header "X-Nomad-Token: eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA" \
+    https://localhost:4646/v1/acl/policy/self
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 22,
+    "Description": "",
+    "Hash": "SmmKR0rW0WA0Bfpk7m3D8wqgrL0dtkY3DwAucF9YN4Y=",
+    "JobACL": {
+      "Group": "nomad",
+      "JobID": "nomad",
+      "Namespace": "default",
+      "Task": ""
+    },
+    "ModifyIndex": 22,
+    "Name": "nomad-policy"
+  }
+]
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                          | Produces       |
+| -------- | ----------------------------- | -------------- |
+| `DELETE` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.11.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..58232ec92e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `POST` | `/v1/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/v1/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                    | Produces       |
+| -------- | ----------------------- | -------------- |
+| `DELETE` | `/v1/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.11.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..768a03ec2e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/docs/secure/acl/bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/v1/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `POST` | `/v1/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/v1/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.11.x/content/api-docs/agent.mdx b/content/nomad/v1.11.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..47c1491200
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/v1/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/v1/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/v1/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/v1/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint          | `enable_debug` | ACLs | **Available?** |
+| ----------------- | -------------- | ---- | -------------- |
+| `/v1/agent/pprof` | unset          | n/a  | no             |
+| `/v1/agent/pprof` | `true`         | n/a  | yes            |
+| `/v1/agent/pprof` | `false`        | n/a  | no             |
+| `/v1/agent/pprof` | unset          | off  | no             |
+| `/v1/agent/pprof` | unset          | on   | **yes**        |
+| `/v1/agent/pprof` | `true`         | off  | yes            |
+| `/v1/agent/pprof` | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.11.x/content/api-docs/allocations.mdx b/content/nomad/v1.11.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..a60d84e859
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/allocations.mdx
@@ -0,0 +1,1075 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`  |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+## Override Pause Schedule State
+
+<EnterpriseAlert />
+
+The endpoint is used to override the [`schedule`][schedule] for tasks using
+time based execution.
+
+| Method         | Path                                    | Produces           |
+| -------------- | --------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:job-submit`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `Task` `(string: <required>)` - Specifies the name of the task whose schedule
+  should be overridden.
+
+- `ScheduleState` `(string: <required>)` - Specifies the pause state to force
+  the task into. One of:
+
+    - `"pause"` - Forces the task to pause.
+
+    - `"run"` - Forces the task to run.
+
+    - `"scheduled"` - Removes any overrides and forces the task to adhere to
+      its schedule.
+
+### Sample Request
+
+```shell-session
+$ echo '{"Task": "schedtask", "ScheduleState": "run"}' | \
+  nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0
+}
+```
+
+## Read Pause Schedule State
+
+<EnterpriseAlert />
+
+Retrieve the [`schedule`][schedule] state for a task using time based execution.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required              |
+| ---------------- | ------------------------- |
+| `NO`             | `namespace:read-job`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the UUID of the allocation.
+  This must be the full UUID, not the short 8-character one. This is
+  specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task from which to
+  retrieve the time-based task execution state.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause?task=schedtask
+```
+
+### Sample Response
+
+```json
+{
+  "ScheduleState": "scheduled_pause"
+}
+```
+
+#### Field Reference
+
+- `ScheduleState` `(string)`: The task's current paused state. It can can have
+  one of the following values:
+
+  - `""` - The task is running. The only state returned for tasks with no
+    schedule.
+
+  - `force_run` - The task's schedule has been overridden to run.
+
+  - `force_pause` - The task's schedule has been overridden to pause.
+
+  - `scheduled_pause` - The task is paused according to its schedule.
+
+  - `schedule_resume` - A schedule override is being removed. Subsequent calls
+    should return running (`""`) or paused (`scheduled_pause`) states. This
+    state is rarely possible to observe since it transitions immediately to
+    another state.
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[schedule]: /nomad/docs/job-specification/schedule
diff --git a/content/nomad/v1.11.x/content/api-docs/client.mdx b/content/nomad/v1.11.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..f828647021
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/client.mdx
@@ -0,0 +1,926 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+## Read a Node's Identity Claims
+
+This endpoint reads the identity claims for a node.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/identity` | `application/json` |
+
+This table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server that is specified as part
+  of the path (`?node_id=...`). Note, this must be the full node ID, not the
+  short 8-character one.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+  /v1/client/identity?node_id=c172799d-1592-06c9-ffc8-308ed12f8080
+```
+
+### Sample Response
+
+```json
+{
+  "Claims": {
+    "aud": "nomadproject.io",
+    "exp": 1758032770,
+    "jti": "a881c528-64f5-4fdd-70cb-c759c3427bb8",
+    "nomad_node_datacenter": "dc1",
+    "nomad_node_id": "c172799d-1592-06c9-ffc8-308ed12f8080",
+    "nomad_node_pool": "default",
+    "iat": 1757946370,
+    "nbf": 1757946370,
+    "sub": "node:global:default:c172799d-1592-06c9-ffc8-308ed12f8080:default"
+  }
+}
+```
+
+## Renew a Node's Identity
+
+This endpoint instructs a node to renew its identity at the next heartbeat.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/client/identity/renew` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to target.
+  This is required when the endpoint is being accessed via a server. This may be
+  specified as part of the path (`?node_id=...`) or request body
+  (`NodeID: "..."`), with the query parameter taking precedence when both are
+  provided. Note, this must be the full node ID, not the short 8-character one.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+  -X POST \
+  /v1/client/identity/renew?node_id=c172799d-1592-06c9-ffc8-308ed12f8080
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.11.x/content/api-docs/deployments.mdx b/content/nomad/v1.11.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/evaluations.mdx b/content/nomad/v1.11.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..0876c1752f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/reference/metrics
diff --git a/content/nomad/v1.11.x/content/api-docs/events.mdx b/content/nomad/v1.11.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..3747075dd9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/events.mdx
@@ -0,0 +1,369 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](https://github.com/ndjson/ndjson-spec). This means splitting
+the streaming response at every `\n` character will guarantee each message is a valid
+JSON object. Note that each JSON object may include multiple events (high server
+activity) or no events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+
+| Topic        | ACL Required                 |
+|--------------|------------------------------|
+| `*`          | `management`                 |
+| `ACLPolicy`  | `management`                 |
+| `ACLRole`    | `management`                 |
+| `ACLToken`   | `management`                 |
+| `Allocation` | `namespace:read-job`         |
+| `CSIPlugin`  | `namespace:read-job`         |
+| `CSIVolume`  | `namespace:csi-read-volume`  |
+| `Deployment` | `namespace:read-job`         |
+| `Evaluation` | `namespace:read-job`         |
+| `HostVolume` | `namespace:host-volume-read` |
+| `Job`        | `namespace:read-job`         |
+| `NodePool`   | `management`                 |
+| `Node`       | `node:read`                  |
+| `Operator`   | `operator:read`              |
+| `Service`    | `namespace:read-job`         |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                                 |
+|------------|----------------------------------------|
+| ACLPolicy  | ACLPolicy                              |
+| ACLRoles   | ACLRole                                |
+| ACLToken   | ACLToken                               |
+| Allocation | Allocation (no job information)        |
+| CSIPlugin  | CSIPlugin                              |
+| CSIVolume  | CSIVolume                              |
+| Deployment | Deployment                             |
+| Evaluation | Evaluation                             |
+| HostVolume | HostVolume (dynamic host volumes only) |
+| Job        | Job                                    |
+| Node       | Node                                   |
+| NodeDrain  | Node                                   |
+| NodePool   | NodePool                               |
+| Operator   | UtilizationSnapshot <EnterpriseAlert inline/>  |
+| Service    | Service Registrations                  |
+
+### Event Types
+
+| Type                          |
+|-------------------------------|
+| ACLPolicyDeleted              |
+| ACLPolicyUpserted             |
+| ACLRoleDeleted                |
+| ACLRoleUpserted               |
+| ACLTokenDeleted               |
+| ACLTokenUpserted              |
+| AllocationCreated             |
+| AllocationUpdateDesiredStatus |
+| AllocationUpdated             |
+| CSIVolumeDeregistered         |
+| CSIVolumeRegistered           |
+| DeploymentAllocHealth         |
+| DeploymentPromotion           |
+| DeploymentStatusUpdate        |
+| EvaluationUpdated             |
+| HostVolumeDeleted             |
+| HostVolumeRegistered          |
+| JobBatchDeregistered          |
+| JobDeregistered               |
+| JobRegistered                 |
+| NodeDeregistration            |
+| NodeDrain                     |
+| NodeEligibility               |
+| NodeEvent                     |
+| NodePoolDeleted               |
+| NodePoolUpserted              |
+| NodeRegistration              |
+| PlanResult                    |
+| ServiceDeregistration         |
+| ServiceRegistration           |
+| UtilizationSnapshotUpserted   |
+
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.advertise.address": "127.0.0.1:4646",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/index.mdx b/content/nomad/v1.11.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..88ee018527
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/index.mdx
@@ -0,0 +1,731 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter.
+
+Here is an example using curl to query the `qa` namespace:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=qa'
+```
+
+Use a wildcard (`*`) to query all namespaces:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=*'
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> \
+    --data-urlencode 'filter=<filter expression>'
+```
+
+The filter expression can also be specified in the
+[`-filter`][cli_operator_api_filter] flag of the
+[`nomad operator api`][cli_operator_api] command.
+
+```shell-session
+$ nomad operator api -filter '<filter expression>' /v1/<path>
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### List Stubs
+
+Some list endpoints return a reduced version of the resource being queried.
+This smaller version is called a _stub_ and may have different fields than the
+full resource definition. To allow more expressive filtering operations, the
+filter is applied to the full version, not the stub.
+
+If a request returns an error such as `error finding value in datum` the field
+used in filter expression may need to be adjusted. For example, filtering on
+node addresses should use the `HTTPAddr` field of the full node definition
+instead of `Address` field present in the stub.
+
+```shell-session
+$ nomad operator api -filter 'HTTPAddr matches "10.0.0..+"' /v1/nodes
+```
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Datacenters contains "dc2"' /v1/jobs
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Status != "successful"' /v1/deployments
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
+
+[cli_operator_api]: /nomad/commands/operator/api
+[cli_operator_api_filter]: /nomad/commands/operator/api#filter
diff --git a/content/nomad/v1.11.x/content/api-docs/jobs.mdx b/content/nomad/v1.11.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..391434c2ff
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2835 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+- `PreserveResources` `(bool: false)` - If set, existing task resources are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2` or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version. This
+  is specified as a query string parameter.
+
+- `diff_version` `(int: <optional>)`: Specifies the version to to compare against the current version when you create the structured diff for a job with `diffs=true`. This is specified as a query string parameter.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect", null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect": null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "Disconnect": null,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `idempotency_token` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Dispatch Job with raw Payload body
+
+This endpoint dispatches a new instance of a parameterized job using the full
+request body as the `Payload` as described in [Dispatch Job](#dispatch-job).
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch/payload` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+specified as part of the path.
+
+### Sample Payload
+
+```
+any HTTP request body, JSON or otherwise, becomes the dispatch Payload
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data 'anything at all' \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "DispatchedJobID": "param/dispatch-1730920906-81821d1f",
+  "EvalCreateIndex": 179,
+  "EvalID": "5e973383-8d59-3f33-4496-72112a882605",
+  "Index": 179,
+  "JobCreateIndex": 178
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to. Use either
+  this parameter or `TaggedVersion`, but do not use both.
+
+- `TaggedVersion` `(string: "")` - Specifies the tag name of the job version you
+  want to revert to. Use either this parameter or `JobVersion`, but do not use both.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+This example specifies the version.
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+This example specifies the tagged version.
+
+```json
+{
+  "JobID": "my-job",
+  "TaggedVersion": "golden-version"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+  the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if
+  the passed `JobModifyIndex` matches the current job's index. If the index is
+  zero, the register only occurs if the job is new. This paradigm allows
+  check-and-set style job updating.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as
+  part of the scaling event.  Indicates an error state preventing scaling; one
+  of `Message` or `Error` must be provided.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted
+  as part of the scaling event.  Indicates information or reason for scaling;
+  one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+   enabled, this value must match a namespace that the token is allowed to
+   access. This is specified as a query string parameter.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be scaled when it would be
+  denied by policy.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling
+  operation.  Must contain a field `Group` with the name of the task group that
+  is the target of this scaling action.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## List Job Actions
+
+This endpoint lists the actions available to tasks within a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/actions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/job/my-job/actions'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Args": [
+      "-s",
+      "wttr.in/Toronto?format=3"
+    ],
+    "Command": "/usr/bin/curl",
+    "Name": "weather",
+    "TaskGroupName": "group1",
+    "TaskName": "task"
+  },
+  {
+    "Args": [
+      "-c",
+      "nomad alloc status ${NOMAD_ALLOC_ID}"
+    ],
+    "Command": "/bin/sh",
+    "Name": "get-alloc-info",
+    "TaskGroupName": "group2",
+    "TaskName": "task"
+  },
+]
+```
+
+## Run Action
+
+This endpoint executes a predefined action from a job in the
+context of a specific task within an allocation. It opens a WebSocket to
+transmit output from the running action.
+
+
+| Method      | Path                     | Produces               |
+| ----------- | ------------------------ | ---------------------- |
+| `WebSocket` | `/v1/job/:job_id/action` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if task driver does not support [file system isolation](/nomad/plugins/author/task-driver#capabilities-capabilities-error)) |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job containing the
+  action. This is specified as part of the path.
+- `action` `(string: <required>)` - Specifies the name of the action to be
+  executed, as defined within the job's task. Specified as a query parameter.
+- `alloc_id` `(string: <required>)` - Specifies the UUID of the target
+  allocation. Specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task where the action is
+  defined. Specified as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this action.
+  Specified as a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the
+  authentication token in the first frame, as a query parameter.
+
+### WebSocket Upgrade Request
+
+Actions are executed with a WebSocket upgrade request. The request headers
+must include the standard WebSocket upgrade parameters. Example:
+
+```shell-session
+$ curl \
+  -X GET \
+  -H 'Connection: Upgrade' \
+  -H 'Upgrade: websocket' \
+  -H 'Sec-Websocket-Version: 13' \
+  -H 'Sec-Websocket-Key: x3JJHMbDL1EzLkh9GBhXDw==' \
+  'http://127.0.0.1:4646/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+or
+```shell-session
+$ nomad operator api \
+-H "Connection: Upgrade" \
+-H "Upgrade: websocket" \
+-H "Sec-WebSocket-Version: 13" \
+-H "Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==" \
+'/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+
+### Request Frames
+
+Unlike [alloc exec](/nomad/api-docs/allocations#exec-allocation), Actions do
+not take input in the form of request frames using `stdin`. Instead, the name
+of the action is passed as a query parameter and the associated input is handled
+on the allocation apart from the stream.
+
+When `?ws_handshake=true`, the first request frame must contain the
+authentication token. Similarly, when `?tty=true`, a `tty_size` frame may be
+provided to indicate a resize.
+
+The following are valid input frames:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well
+as exit codes. Response frames encompass the full range of terminal emulator outputs, including
+the control characters necessary to render interactive applications.
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+{"exited":true,"result":{}}
+```
+
+The stdout data returned in the response frames from the job action endpoint is
+base64 encoded. This encoding is necessary to ensure that the data can be
+transmitted over WebSocket connections without issues, regardless of its content.
+
+### Sample Request and Response
+
+This example response includes instances of the ANSI "control sequence
+introducer" (CSI), which is ASCII code 27 followed by `[`. The second stdout
+frame includes the desired output from the Action in question, which prints
+the local weather.
+
+```
+# Sample WebSocket request to execute an action
+WebSocket Request: /v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+
+# Toronto: ⛅️  -1°C
+{"stdout":{"data":"VG9yb250bzog4puF77iPICAtMcKwQw0K"}}
+```
+
+## Create Job Version Tag
+
+This endpoint creates a tag for a job version.
+
+@include 'version/tag-reason.mdx'
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part
+  of the path.
+- `:tag_name` `(string: <required>)` - The new tag name for the
+  version specified in the payload. Must be unique per job. Specify `tag_name` as part of the path.
+- `Version`: `(int: <optional>)` - The job version number. If not
+  specified, Nomad tags the latest version. Specify `Version` in the payload.
+- `Description`: `(string: <optional>)` - The tag description. Specify `Description` in the payload.
+
+### Sample Payload
+
+```json
+{
+  "Version": 0,
+  "Description": "The version we can roll back to."
+}
+```
+
+### Sample Request
+
+This example creates a tag named `golden-version` for version zero of the
+`hello-world` job.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "The version we can roll back to."}'
+```
+
+### Sample Response
+
+```json
+{
+  "Name":"golden-version",
+  "Description":"The version we can roll back to.",
+  "TaggedTime":1728325495829793000,
+  "Index":361,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+## Delete Job Version Tag
+
+This endpoint deletes a job version tag.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `DELETE`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part of the path.
+- `:tag_name` `(string: <required>)` - The tag name. Specify `tag_name` as part of the path.
+
+### Sample Request
+
+This example deletes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ curl -X DELETE localhost:4646/v1/job/hello-world/versions/golden-version/tag -H "Content-Type: application/json"
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID":"",
+  "EvalCreateIndex":0,
+  "JobModifyIndex":0,
+  "VolumeEvalID":"",
+  "VolumeEvalIndex":0,
+  "Index":0,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
diff --git a/content/nomad/v1.11.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.11.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..b3c023fc9f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1247 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/commands/job/inspect
+[job-output]: /nomad/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Disconnect": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul service mesh enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/concepts/scheduling/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+- `Ui` - Options to modify the presentation of the Job index page in the Web UI.
+  When specified, a description and any number of links will be added to the top of
+  the job page in question.
+
+  - `Description` - a markdown-enabled string description of the job
+    jobs.
+
+  - `Links` - Anchor link that will appear at the top of the job page.
+
+    - `Label` - The shown name of the link
+    - `Url` - The address that the link will point to
+
+  An example `ui` block:
+
+  ```json
+  "Ui": {
+    "Description": "A job that uses **Nomad Variables** to modify its output",
+    "Links": [
+      {
+        "Label": "Learn more about Nomad Variables",
+        "Url": "https://developer.hashicorp.com/nomad/docs/concepts/variables"
+      },
+      {
+        "Label": "See this job on Github",
+        "Url": "https://github.com/hashicorp/nomad/blob/main/ui/app/utils/default_jobs/variables.js"
+      }
+    ]
+  }
+  ```
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/job-declare/task-driver) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/reference/runtime-variable-interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/networking/service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Unlike `PortLabel`,
+      this setting is _not_ inherited from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. Numeric ports may be
+      used if `AddressMode: "driver"` is set on the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. The template can reference
+[Nomad's runtime environment variables][env]. For a full list of the API template
+functions, please refer to the [Consul Template README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/commands/node/drain
+[env]: /nomad/docs/reference/runtime-environment-settings 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.11.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.11.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..53734a477d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,41 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+- [`nix-nomad`](https://github.com/tristanpemble/nix-nomad) - HashiCorp Nomad job definitions in Nix
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.11.x/content/api-docs/metrics.mdx b/content/nomad/v1.11.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/namespaces.mdx b/content/nomad/v1.11.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/node-pools.mdx b/content/nomad/v1.11.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.11.x/content/api-docs/nodes.mdx b/content/nomad/v1.11.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..c0766f4252
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1112 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.advertise.address": "127.0.0.1:4646",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/docs/manage/migrate-workloads) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.11.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..439355effd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,253 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - <EnterpriseAlert inline/> Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ],
+  "Leader": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+  "Voters": [
+    "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+    "e36ee410-cc3c-0a0c-c724-63817ab30303"
+  ],
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+<EnterpriseAlert>
+  This API endpoint returns with more information in Nomad Enterprise. This is
+  not present in Nomad Community Edition.
+</EnterpriseAlert>
+
+When using Nomad Enterprise this endpoint will return more information about the
+underlying actions and state of Autopilot.
+
+```json
+{
+  ...
+  "ReadReplicas": null,
+  "RedundancyZones": {},
+  "Upgrade": {
+    "Status": "idle",
+    "TargetVersion": "1.7.5+ent",
+    "TargetVersionVoters": [
+      "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "e36ee410-cc3c-0a0c-c724-63817ab30303"
+    ],
+    "TargetVersionNonVoters": null,
+    "TargetVersionReadReplicas": null,
+    "OtherVersionVoters": null,
+    "OtherVersionNonVoters": null,
+    "OtherVersionReadReplicas": null,
+    "RedundancyZones": {}
+  },
+  "OptimisticFailureTolerance": 0
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/index.mdx b/content/nomad/v1.11.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..10670871c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/docs/manage/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.11.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..e0d27df525
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,266 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Active Public Keys
+
+This endpoint retrieves a list of active public keys used to sign [workload
+identities][wi]. The response is in the [JWKS][rfc7517] format as is commonly
+used by JWT auth methods.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/.well-known/jwks.json`    | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `none`       |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/jwks.json'
+```
+
+### Sample Response
+
+```json
+{
+  "keys": [
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "15a95f48-001a-8be5-5da9-d94901d022c9",
+      "alg": "RS256",
+      "n": "6sImUQR6A...FB7bKn02dKw",
+      "e": "AQAB"
+    },
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "b7f6a3a7-14f9-4ac5-f713-32c9bce1fa93",
+      "alg": "RS256",
+      "n": "zEdiUB3DFuM...ii3kQvOf_eDApBDWJhfQw",
+      "e": "AQAB"
+    }
+  ]
+}
+```
+
+## OIDC Discovery
+
+This endpoint retrieves [OIDC configuration metadata][oidc-disco] for using
+[workload identities][wi] with third party services. Nomad will act as an
+identity provider (IDP) to allow third parties to authenticate workload
+identity JWTs based on the OIDC configurationa and JWKS.
+
+Most third parties will require this endpoint be accessible through a
+publically resolvable domain name and HTTPS signed by a trusted certificate
+authority.
+
+You must set the [`oidc_issuer`][oidc_issuer] Server agent configuration
+parameter before this endpoint is enabled. In most situations you will also
+need to run a proxy or load balancer for in front of this endpoint to serve the
+contents with HTTPS using a trusted certificate.
+
+| Method | Path                                | Produces           |
+|--------|-------------------------------------|--------------------|
+| `GET`  | `/.well-known/openid-configuration` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `none` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/openid-configuration'
+```
+
+### Sample Response
+
+```json
+{
+  "id_token_signing_alg_values_supported": [
+    "RS256",
+    "EdDSA"
+  ],
+  "issuer": "http://example.com",
+  "jwks_uri": "http://example.com/.well-known/jwks.json",
+  "response_types_supported": [
+    "code"
+  ],
+  "subject_types_supported": [
+    "public"
+  ]
+}
+```
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Parameters
+
+- `force` `(bool: false)` - Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/manage/key-management
+[`nomad operator root keyring`]: /nomad/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[oidc-disco]: https://openid.net/specs/openid-connect-discovery-1_0.html
+[oidc_issuer]: /nomad/docs/configuration/server#oidc_issuer
+[required ACLs]: /nomad/api-docs#acls
+[rfc7517]: https://datatracker.ietf.org/doc/html/rfc7517
+[wi]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/license.mdx b/content/nomad/v1.11.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.11.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..ccc1feee32
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,219 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api /v1/operator/raft/configuration
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+</Tab>
+</Tabs>
+
+### Sample Response
+
+```json
+{
+    "Index": 0,
+    "Servers": [
+        {
+            "Address": "10.1.0.10:4647",
+            "ID": "c13f9998-a0f3-d765-0b52-55a0b3ce5f88",
+            "Leader": false,
+            "Node": "node1.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.20:4647",
+            "ID": "d7927f2b-067f-45a4-6266-af8bb84de082",
+            "Leader": true,
+            "Node": "node2.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.30:4647",
+            "ID": "00d56ef8-938e-abc3-6f8a-f8ac80a80fb9",
+            "Leader": false,
+            "Node": "node3.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        }
+
+    ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. For Raft protocol v2, this is the
+    same as the `Address`. Raft protocol v3 uses GUIDs as the ID.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the server to
+  remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+### Sample Request
+
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X DELETE \
+   /v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    https://127.0.0.1:4646/v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+</Tabs>
+
+## Transfer Leadership to another Raft Peer
+
+This endpoint tells the current cluster leader to transfer leadership
+to the Nomad server with given address or ID in the Raft
+configuration. The return code signifies success or failure.
+
+| Method              | Path                                    | Produces           |
+| ------------------- | --------------------------------------- | ------------------ |
+| `PUT` <br /> `POST` | `/v1/operator/raft/transfer-leadership` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  target server as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the target server
+  as provided in the output of `/v1/operator/raft/configuration` API endpoint or
+  the `nomad operator raft list-peers` command.
+
+<Note>
+
+- The cluster must be running Raft protocol v3 or greater on all server members.
+
+- Either `address` or `id` must be provided, but not both.
+
+</Note>
+
+### Sample Requests
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X PUT \
+    "/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl --request PUT \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    "https://127.0.0.1:4646/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+</Tabs>
+
+[consensus protocol guide]: /nomad/docs/architecture/cluster/consensus
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.11.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.11.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d753600099
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/architecture/cluster/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/upgrade-check.mdx b/content/nomad/v1.11.x/content/api-docs/operator/upgrade-check.mdx
new file mode 100644
index 0000000000..f41e348fe2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/upgrade-check.mdx
@@ -0,0 +1,185 @@
+---
+layout: api
+page_title: Upgrade Check - Operator - HTTP API
+description: |-
+  The /operator/upgrade-check endpoints provide tools for verifying the state
+  of the cluster prior to upgrades.
+---
+
+# Upgrade Check Operator HTTP API
+
+The `/operator/upgrade-check` endpoints provide some predefined verifications
+that can be useful prior to upgrades and changes to Nomad configuration.
+
+<Note>
+
+These endpoints are meant to target specific releases of Nomad and may be
+removed or modified without notice.
+
+</Note>
+
+## Vault Workload Identity
+
+This endpoint retrieves jobs, nodes, and Vault ACL tokens that may be affected
+when migrating a Nomad cluster to use [workload identities for
+Vault][nomad_acl_vault_wid].
+
+| Method | Path                                                 | Produces           |
+| ------ | ---------------------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/upgrade-check/vault-workload-identity` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/operator/upgrade-check/vault-workload-identity
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 20,
+  "JobsWithoutVaultIdentity": [
+    {
+      "CreateIndex": 11,
+      "Datacenters": [
+        "*"
+      ],
+      "ID": "example",
+      "JobModifyIndex": 11,
+      "JobSummary": null,
+      "ModifyIndex": 19,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "default",
+      "ParameterizedJob": false,
+      "ParentID": "",
+      "Periodic": false,
+      "Priority": 50,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1704995322434188000,
+      "Type": "service"
+    }
+  ],
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "OutdatedNodes": [
+    {
+      "Address": "192.168.0.186",
+      "CreateIndex": 8,
+      "Datacenter": "dc1",
+      "Drain": false,
+      "Drivers": {
+        "qemu": {
+          "Attributes": {
+            "driver.qemu": "true",
+            "driver.qemu.version": "8.1.1"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.993541-05:00"
+        },
+        "exec": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "exec driver unsupported on client OS",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.958495-05:00"
+        },
+        "raw_exec": {
+          "Attributes": {
+            "driver.raw_exec": "true"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.958539-05:00"
+        },
+        "java": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.97141-05:00"
+        },
+        "docker": {
+          "Attributes": {
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.runtimes": "io.containerd.runc.v2,runc",
+            "driver.docker.os_type": "linux",
+            "driver.docker": "true",
+            "driver.docker.version": "24.0.7"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.989993-05:00"
+        }
+      },
+      "HostVolumes": null,
+      "ID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "LastDrain": null,
+      "ModifyIndex": 10,
+      "Name": "client-1",
+      "NodeClass": "",
+      "NodePool": "default",
+      "SchedulingEligibility": "eligible",
+      "Status": "ready",
+      "StatusDescription": "",
+      "Version": "1.6.4"
+    }
+  ],
+  "VaultTokens": [
+    {
+      "Accessor": "czh9MPcRXzAhxBL9XKyb3Kh1",
+      "AllocID": "f00893d4-d9ef-4937-6a7a-ab495b68a971",
+      "CreateIndex": 14,
+      "CreationTTL": 60,
+      "NodeID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "Task": "redis"
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `JobsWithoutVaultIdentity` `(array<Job>)` - The list of jobs that have a
+  [`vault`][] block but do not have an [`identity`][] for Vault
+  authentication. These jobs can fail if they are not redeployed with an
+  identity for Vault before the configuration for Nomad servers are updated and
+  their access to Vault is removed.
+
+- `OutdatedNodes` `(array<Node>)` - The list of nodes running a version of
+  Nomad that does not support workload identity authentication for Vault.
+  Allocations placed in these nodes will use the deprecated legacy flow to
+  retrieve Vault tokens. If the Nomad servers configuration is update to remove
+  their access to Vault before these nodes are upgraded, these allocations will
+  fail. Allocations that use workload identity for Vault will not be able to be
+  placed in these nodes until they are upgraded.
+
+- `VaultTokens` `(array<VaultAccessor>)` - The list of Vault ACL tokens created
+  by Nomad servers using the deprecated legacy flow. They will continue to work
+  even after the migration to the workload identities, but they may not be
+  automatically revoked by Nomad and will only expire once their TTL reaches
+  zero.
+
+
+[`identity`]: /nomad/docs/job-specification/identity
+[`vault`]: /nomad/docs/job-specification/vault
+[nomad_acl_vault_wid]: /nomad/docs/secure/vault/acl#nomad-workload-identities
+
diff --git a/content/nomad/v1.11.x/content/api-docs/operator/utilization.mdx b/content/nomad/v1.11.x/content/api-docs/operator/utilization.mdx
new file mode 100644
index 0000000000..bc000d5e3c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/operator/utilization.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: Utilization - Operator - HTTP API
+description: |-
+  The /operator/utilization endpoints provide tools for generating utilization reporting bundles for Nomad Enterprise.
+---
+
+# Operator Utilization HTTP API
+
+The `/operator/utilization` endpoints provide tools for generating utilization
+reporting bundles for Nomad Enterprise.
+
+<EnterpriseAlert />
+
+## Generate Nomad Enterprise Utilization Report Bundle
+
+This endpoint generates a utilization report. If Nomad did not record a
+utilization snapshot in the previous 24 hours, Nomad records a utilization
+snapshot first.
+
+| Method | Path                       | Produces           |
+|--------|----------------------------|--------------------|
+| `POST` | `/v1/operator/utilization` | `application/json` |
+
+This table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required     |
+|------------------|------------------|
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `today` `(bool: false)` - Specifies to return a bundle that only includes
+  utilization snapshots from the previous 24 hours.
+
+### Sample Request
+
+```shell-session
+$ curl -XPOST \
+    https://localhost:4646/v1/operator/utilization?today=true
+```
+
+### Sample Response
+
+The `Bundle` field in the response body is a base64-encoded blob. The exact
+format of this blog is not part of the Nomad API and is subject to change
+between versions. The [`nomad operator utilization`][] command, which uses this
+API, decodes this to a human-readable file in the current working directory.
+
+```json
+{
+  "Bundle": "eyJ2ZXJzaW9uIjoiMiIsIm1vZGUiOiJtYW51Y..."
+}
+```
+
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required  ACLs]: /nomad/api-docs#acls
+[`nomad operator utilization`]: /nomad/commands/operator/utilization
diff --git a/content/nomad/v1.11.x/content/api-docs/plugins.mdx b/content/nomad/v1.11.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/quotas.mdx b/content/nomad/v1.11.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..76c2674281
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/quotas.mdx
@@ -0,0 +1,418 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert product="nomad"/>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+    "Limits": [
+      {
+        "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "Cores": 0,
+          "Devices": [
+            {
+              "Affinities": null,
+              "Constraints": null,
+              "Count": 1,
+              "Name": "nvidia/gpu/Tesla M60"
+            }
+          ],
+          "DiskMB": 0,
+          "IOPS": 0,
+          "MemoryMB": 2000,
+          "MemoryMaxMB": 2000,
+          "NUMA": null,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Limit the shared default namespace",
+  "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+  "Limits": [
+    {
+      "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "Cores": 0,
+        "Devices": [
+          {
+            "Affinities": null,
+            "Constraints": null,
+            "Count": 1,
+            "Name": "nvidia/gpu/Tesla M60"
+          }
+        ],
+        "DiskMB": 0,
+        "IOPS": 0,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "NUMA": null,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 11,
+  "Name": "default-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "default-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1
+          }
+        ],
+        "VariablesLimit": 1000
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "Cores": 0,
+          "MemoryMB": 256,
+          "MemoryMaxMB": 256,
+          "DiskMB": 0,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "Devices": [
+            {
+              "Name": "nvidia/gpu/Tesla M60",
+              "Count": 1,
+              "Constraints": null,
+              "Affinities": null
+            }
+          ],
+          "NUMA": null,
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 0,
+        "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+      }
+    },
+    "Name": "default-quota",
+    "CreateIndex": 11,
+    "ModifyIndex": 38
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "Cores": 0,
+        "MemoryMB": 256,
+        "MemoryMaxMB": 256,
+        "DiskMB": 0,
+        "IOPS": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1,
+            "Constraints": null,
+            "Affinities": null
+          }
+        ],
+        "NUMA": null,
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 0,
+      "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+    }
+  },
+  "Name": "default-quota",
+  "CreateIndex": 11,
+  "ModifyIndex": 38
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/recommendations.mdx b/content/nomad/v1.11.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..1e18b818fd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,370 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/regions.mdx b/content/nomad/v1.11.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.11.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..9e16d80953
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/search.mdx b/content/nomad/v1.11.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..b205ee5269
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/search.mdx
@@ -0,0 +1,639 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evaluations, volumes, and resource quotas. Note that resource quotas is
+an Enterprise feature.
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.11.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.11.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..95a8d37807
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,176 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/docs/govern/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/docs/secure/acl).
+
+<EnterpriseAlert product="nomad"/>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/v1/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/v1/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/services.mdx b/content/nomad/v1.11.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..0e6ddf2515
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
diff --git a/content/nomad/v1.11.x/content/api-docs/status.mdx b/content/nomad/v1.11.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..1b8089f846
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/system.mdx b/content/nomad/v1.11.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/task-api.mdx b/content/nomad/v1.11.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..5f644154f6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/task-api.mdx
@@ -0,0 +1,109 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+## Limitations
+
+- Using the Task API Unix Domain Socket on Windows [requires][windows] Windows
+build 17063 or later.
+
+[acl]: /nomad/docs/secure/acl/
+[acl-tokens]: /nomad/docs/secure/acl/#tokens
+[alloc-exec]: /nomad/commands/alloc/exec
+[anon]: /nomad/docs/secure/acl#policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/docs/secure/traffic/tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[dnm]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.11.x/content/api-docs/ui.mdx b/content/nomad/v1.11.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..9a78bef50e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/ui.mdx
@@ -0,0 +1,585 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version, so do not
+prepend `/vi` to this endpoint. A request to `/` redirects to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize <EnterpriseAlert inline/>
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel.
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.11.x/content/api-docs/validate.mdx b/content/nomad/v1.11.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.11.x/content/api-docs/variables/index.mdx b/content/nomad/v1.11.x/content/api-docs/variables/index.mdx
new file mode 100644
index 0000000000..0e29e60455
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/variables/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: |-
+  The /var endpoints are used to query for and interact with variables and variable
+  locking.
+---
+
+# Vars HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables, and set up locks and leases over them.
+
+See the [Variables][] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`][] commands.
+
+Please choose a sub-section in the navigation for more information
+
+[`nomad var`]: /nomad/commands/var
+[Variables]: /nomad/docs/concepts/variables
diff --git a/content/nomad/v1.11.x/content/api-docs/variables/locks.mdx b/content/nomad/v1.11.x/content/api-docs/variables/locks.mdx
new file mode 100644
index 0000000000..8b27be1811
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/variables/locks.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: Variable Locks - HTTP API
+description: The /var endpoints are used to query for and interact with variables and locks.
+---
+
+# Locks HTTP API
+
+The `/var` endpoint is used to hold, renew and release a lock over a variable.
+
+## Lock Variable
+
+The endpoint to create a variable can also be used to hold a lock and interact with
+it through the use of a parameter defining the operation to be performed.
+
+| Method | Path                                 | Produces           |
+|--------|--------------------------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path?<lock-operation>` | `application/json` |
+
+### Parameters
+
+The lock operation parameter can be:
+
+- `lock-acquire`: When used, the call will introduce a lock over the variable if
+it exists, or create a new one if it doesn't. The lock ID will be returned in the
+response and it must be provided to perform any other operation over the lock.
+The variable items can be updated at any time using the lock ID, but the lock
+parameters are unmmutable, attempting to modify them while a lock is present will
+generate an error.
+
+In the case of attempting to acquire a variable that is already locked, a conflict
+response will be returned.
+
+The lock-acquire operation will override the variable items if new values are
+present.
+
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-acquire
+```
+
+#### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "1m"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the created or updated variable including the lock
+parameters and ID, along with metadata created by the server:
+
+```json
+{
+  "CreateIndex": 15,
+  "CreateTime": 1694552155379696000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 16,
+  "ModifyTime": 1694552206138804000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-renew`: A valid call to lock renew needs to be placed before the lock's
+TTL is up in order to mantain the variable locked. A valid call must include the
+lock ID as part of the request body. If the lock TTL is up without a renewal or
+release calls, the variable will remain unlockable for at least the lock delay.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-renew
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body only returns metadata created by the server and the lock
+parameters:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 43,
+  "ModifyTime": 1694556175092779000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-release`: A call to the endpoint with the `lock-release` operation will
+immediately remove the lock over the variable, making it modifiable without
+restrictions again.
+
+The lock-release operation will not override the variable items, if the request
+body contains any item, it will generate a bad request response.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-release
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the released variable along with metadata
+created by the server:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "ModifyIndex": 66,
+  "ModifyTime": 1694556922600469000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+### Sample Response for Conflict
+
+In the case of an attempt to lock, renew or modify a locked variable
+without the correct ID, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "CreateIndex": 0,
+  "CreateTime": 0,
+  "Items": null,
+  "Lock": null,
+  "ModifyIndex": 0,
+  "ModifyTime": 0,
+  "Namespace": "default",
+  "Path": "example/first"
+}
+```
+
+## Restrictions
+
+When creating a new variable using the lock-acquire operation, all the known
+[restrictions][] regarding the path and size of the content apply, but unlike
+regular variables, locked variables can be created with or without any items.
+
+The lock TTL and Delay must be values between 10 seconds and 24 hours.
+
+[Variables]: /nomad/docs/concepts/variables
+[restrictions]: /nomad/api-docs/variables/variables#restrictions
+[`nomad var`]: /nomad/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.11.x/content/api-docs/variables/variables.mdx b/content/nomad/v1.11.x/content/api-docs/variables/variables.mdx
new file mode 100644
index 0000000000..f53b0c7be4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/variables/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables][] documentation for information how these capabilities are
+used. 
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+- `lock-operation` `(string: <unset>)` - This endpoint can also be used to create 
+and hold a lock over a variable, refer to the [locks section][] for more
+information.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+[Variables]: /nomad/docs/concepts/variables
+[locks section]:/nomad/api-docs/variables/locks
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.11.x/content/api-docs/volumes.mdx b/content/nomad/v1.11.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..735cb1f094
--- /dev/null
+++ b/content/nomad/v1.11.x/content/api-docs/volumes.mdx
@@ -0,0 +1,1242 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: |-
+  The Nomad  `/volume` and `/volumes` endpoints query for and interact with Container Storage Interface (CSI) volumes and dynamic host volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints query for and interact with
+Container Storage Interface (CSI) volumes and dynamic host volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                 |
+|------------------|--------------------------------------------------------------|
+| `YES`            | `namespace:csi-list-volume`<br/>`namespace:host-volume-read` |
+
+### Parameters
+
+- `type` `(string: <required>)` - Specifies the type of volume to query. One of
+  `csi` or `host`. The `host` value queries dynamic host volumes. Specify this
+  as a query string parameter.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response for CSI Volumes
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+### Sample Response for dynamic host volumes
+
+```json
+[
+  {
+    "CapacityBytes": 1048576000,
+    "CreateIndex": 42,
+    "CreateTime": 1736191825846395400,
+    "ID": "3735cc2c-cc64-11ef-89ed-bfb5b3bc38ea",
+    "ModifyIndex": 64,
+    "ModifyTime": 1736191825846395400,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "5c5830d0-cc64-11ef-a293-4f03e55969ea",
+    "NodePool": "default",
+    "PluginID": "plugin-id1",
+    "State": "ready"
+  }
+]
+```
+
+## Read CSI Volume
+
+This endpoint reads information about a specific CSI volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register CSI Volume
+
+This endpoint registers an external CSI volume with Nomad. The volume must exist
+in the external storage provider. Refer to the [Create CSI Volume][] section for
+details.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume`. <br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `Volumes` <code>([Volumes][csi-volume-spec]:</code> `<required>`) - Specifies
+  the JSON definition of the CSI volume. You should include the ID field if you
+  are updating an existing volume. Note that you must include the `NodeID` field
+  for the register API.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create CSI Volume
+
+This endpoint creates a CSI volume in an external storage provider and registers
+it with Nomad. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_VOLUME`
+capability support this endpoint.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume`. <br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `Volumes` <code>([Volumes][csi-volume-spec]:</code> `<required>`) - Specifies
+  the JSON definition of the CSI volume. You should include the ID field if you
+  are updating an existing volume. 
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister CSI Volume
+
+This endpoint deregisters an external CSI volume from Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  Specify this as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete CSI Volume
+
+This endpoint deletes an external CSI volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+The volume must still be registered with Nomad in order to be deleted. This API
+call fails if an allocation still claims the volume or if Nomad is unpublishing
+the volume.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach CSI Volume
+
+This endpoint detaches an external CSI volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  Specify this as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External CSI Volumes
+
+This endpoint lists storage CSI volumes that are known to the external storage
+provider but may not be registered with Nomad. Only CSI plugins that implement
+the [Controller][csi_plugins_internals] interface with the `LIST_VOLUMES`
+capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). Specify this as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response includes a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create CSI Volume Snapshot
+
+This endpoint creates a snapshot of a CSI volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_SNAPSHOT`
+capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete CSI Volume Snapshot
+
+This endpoint deletes a CSI volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_SNAPSHOT`
+capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). Specify this as a
+  query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. Specify this as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List CSI Volume Snapshots
+
+This endpoint lists CSI volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). Specify this as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response includes a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+## Read Dynamic Host Volume
+
+This endpoint reads information about a specific dynamic host volume.
+
+| Method | Path                         | Produces           |
+|--------|------------------------------|--------------------|
+| `GET`  | `/v1/volume/host/:volume_id` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                 |
+|------------------|------------------------------|
+| `YES`            | `namespace:host-volume-read` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/host/c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f
+```
+
+### Sample Response
+
+```json
+{
+  "Allocations": [],
+  "CapacityBytes": 49283072,
+  "CreateIndex": 11,
+  "CreateTime": 1736191993011594200,
+  "HostPath": "/run/nomad/dev/alloc_mounts/c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+  "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+  "ModifyIndex": 12,
+  "ModifyTime": 1736191993011594200,
+  "Name": "external-plugin",
+  "Namespace": "default",
+  "NodeID": "670cb259-bc26-653b-e316-655af04ad260",
+  "NodePool": "default",
+  "Parameters": {
+    "hello": "world"
+  },
+  "PluginID": "example-plugin-mkfs",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    }
+  ],
+  "RequestedCapacityMaxBytes": 50000000,
+  "RequestedCapacityMinBytes": 50000000,
+  "State": "ready"
+}
+```
+
+## Create Dynamic Host Volume
+
+This endpoint creates a dynamic host volume and registers it with Nomad.
+
+The response body includes the volume definition with the `ID` and `NodeID`
+fields populated. Making the same request without the ID creates a new volume on
+a different node. Making a request with the ID set updates the volume to the new
+parameters, if possible.
+
+| Method | Path                     | Produces           |
+|--------|--------------------------|--------------------|
+| `PUT`  | `/v1/volume/host/create` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                                                                                   |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-create` or<br/>`namespace:host-volume-write`.<br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Volume` `(Volume: <required>)` - Specifies the JSON definition of the host
+  volume. You should include the ID field if you are updating an existing
+  volume.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows creating a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volume": {
+    "Name": "example",
+    "Namespace": "default",
+    "NodePool": "prod",
+    "PluginID": "mkdir",
+    "RequestedCapacityMinBytes": 10737418240,
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "Parameters": {
+      "foo": "bar"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/host/create
+```
+
+### Sample Response
+
+```json
+{
+  "Volume": {
+    "Allocations": [],
+    "CapacityBytes": 21474836480,
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "CreateIndex": 11,
+    "CreateTime": 1736191993011594200,
+    "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+    "ModifyIndex": 11,
+    "ModifyTime": 1736191993011594200,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "45460554-cc67-11ef-84b7-33d383a55487",
+    "NodePool": "prod",
+    "Parameters": {
+      "foo": "bar"
+    },
+    "PluginID": "mkdir",
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapacityMinBytes": 10737418240,
+    "State": "pending"
+  },
+  "Warnings": null
+}
+```
+
+## Register Dynamic Host Volume
+
+This endpoint registers an existing dynamic host volume with Nomad.
+
+| Method | Path                       | Produces           |
+|--------|----------------------------|--------------------|
+| `PUT`  | `/v1/volume/host/register` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                                                                                     |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-register` or<br/>`namespace:host-volume-write`.<br/>`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Volume` `(Volume: <required>)` - Specifies the JSON definition of the host
+  volume. You should include the ID field if you are updating an existing
+  volume.
+
+- `PolicyOverride` `(bool: false)` - If set, Nomad overrides any soft mandatory
+  Sentinel policies. This field allows registering a volume when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "PolicyOverride": false,
+  "Volume": {
+    "Name": "example",
+    "Namespace": "default",
+    "NodePool": "prod",
+    "PluginID": "mkdir",
+    "RequestedCapacityMinBytes": 10737418240,
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "Parameters": {
+      "foo": "bar"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/host/register
+```
+
+### Sample Response
+
+```json
+{
+  "Volume": {
+    "Allocations": [],
+    "CapacityBytes": 21474836480,
+    "Constraints": [
+      {
+        "LTarget": "${attr.kernel.name}",
+        "RTarget": "linux",
+        "Operand": "="
+      }
+    ],
+    "CreateIndex": 11,
+    "CreateTime": 1736191993011594200,
+    "ID": "c0f7ee7d-5cc6-92fd-f2b5-14b79f01979f",
+    "ModifyIndex": 31,
+    "ModifyTime": 1736191993721594200,
+    "Name": "example",
+    "Namespace": "default",
+    "NodeID": "45460554-cc67-11ef-84b7-33d383a55487",
+    "NodePool": "prod",
+    "Parameters": {
+      "foo": "bar"
+    },
+    "PluginID": "mkdir",
+    "RequestedCapabilities": [
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "file-system"
+      },
+      {
+        "AccessMode": "single-node-writer",
+        "AttachmentMode": "block-device"
+      }
+    ],
+    "RequestedCapacityMaxBytes": 21474836480,
+    "RequestedCapacityMinBytes": 10737418240,
+    "State": "ready"
+  },
+  "Warnings": null
+}
+```
+
+## Delete Dynamic Host Volume
+
+This endpoint deletes a dynamic host volume, and deregisters it from Nomad. It
+is an error to delete a volume that is in use.
+
+| Method   | Path                                | Produces           |
+|----------|-------------------------------------|--------------------|
+| `DELETE` | `/v1/volume/host/:volume_id/delete` | `application/json` |
+
+The following table shows this endpoint's support for [blocking queries][] and
+[required ACLs][].
+
+| Blocking Queries | ACL Required                                                        |
+|------------------|---------------------------------------------------------------------|
+| `NO`             | `namespace:host-volume-write` or<br/>`namespace:host-volume-delete` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. Specify this as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/host/ba97ef42-cc68-11ef-a2e7-ffddaecbdb89
+```
+
+## List Task Group Host Volume Claims
+
+This endpoint lists host volume claims made by task groups that
+requested "sticky" volumes.
+
+| Method | Path                 | Produces           |
+|--------|----------------------|--------------------|
+| `GET`  | `/v1/volumes/claims` | `application/json` |
+
+The following table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+|------------------|------------------------------|
+| `YES`            | `namespace:host-volume-read` |
+
+### Parameters
+- `claim_id` `(string: "")` - Specifies the prefix of a task group volume
+claim ID to perform the list. Specify this as a query string parameter.
+
+- `namespace` `(string: <required>)` - Specifies the namespace used to filter
+task group volume claims.
+
+- `job_id` `(string: "")` - Specifies the job ID used to filter task group
+volume claims.
+
+- `task_group` `(string: "")` - Specifies the task group name used to filter
+task group volume claims.
+
+- `volume_name` `(string: "")` - Specifies the volume name used to filter
+task group volume claims.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+`next_token` parameter accepts a string returned in a previous response's
+`NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+return for this request. The response includes a `NextToken` field that
+you can pass to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/claims
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocID": "34e44207-0cf3-a24d-4bbe-6c91cec642ce",
+    "CreateIndex": 15,
+    "ID": "75c417b5-cf90-86e4-8ffc-d18f445e0721",
+    "JobID": "example",
+    "ModifyIndex": 15,
+    "Namespace": "default",
+    "TaskGroupName": "echo",
+    "VolumeID": "0bb42da3-7e09-6937-a83d-69d5c9bfce30",
+    "VolumeName": "sticky-volume"
+  }
+]
+```
+
+## Delete Task Group Host Volume Claims
+
+This endpoint deletes host volume claims made by task groups that
+requested "sticky" volumes.
+
+| Method   | Path                          | Produces       |
+|----------|-------------------------------|----------------|
+| `DELETE` | `/v1/volumes/claim/:claim_id` | `(empty body)` |
+
+The following table shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                  |
+|------------------|-------------------------------|
+| `NO`             | `namespace:host-volume-write` |
+
+### Parameters
+
+- `claim_id` `(string: <required>)` - Specifies the ID of task group host volume claim
+to delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/claim/75c417b5-cf90-86e4-8ffc-d18f445e0721
+```
+
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[Create CSI Volume]: #create-csi-volume
+[Volume Expansion]: /nomad/docs/other-specifications/volume/csi#volume-expansion
+[csi-volume-spec]: /nomad/docs/other-specifications/volume/csi  
diff --git a/content/nomad/v1.11.x/content/commands/acl/auth-method/create.mdx b/content/nomad/v1.11.x/content/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..98270e7a53
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/auth-method/create.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method create command reference'
+description: |
+  The `nomad acl auth-method create` command creates new access control list (ACL) authentication methods. Set name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method create` command reference
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration][] in JSON format. You may provide '-'
+  to send the config through stdin, or prefix a file path with '@' to indicate
+  that the config should be loaded from the file.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+This example config uses a private key JWT [client assertion][]
+instead of a client secret.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-keycloak-instance.com/realms/nomad",
+  "OIDCClientID": "my-great-client-id",
+  "OIDCClientAssertion": {
+    "KeySource": "nomad"
+  },
+  "BoundAudiences": [
+    "my-great-client-id"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ListClaimMappings": {
+    "groups": "groups"
+  }
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
+[client assertion]: /nomad/api-docs/acl/auth-methods#oidcclientassertion
diff --git a/content/nomad/v1.11.x/content/commands/acl/auth-method/delete.mdx b/content/nomad/v1.11.x/content/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..74e55c0d40
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method delete command reference'
+description: |
+  The `nomad auth-method delete command` deletes an existing access control list (ACL) authentication method.
+---
+
+# `nomad`acl auth-method delete` command reference
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/auth-method/info.mdx b/content/nomad/v1.11.x/content/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..ea3824cdc7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/auth-method/info.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method info command reference'
+description: |
+  The `nomad auth-method info` command fetches information about an existing access control list (ACL) authentication method. Review name, type, description, locality, time to live (TTL), token name format, and authentication method configuration.
+---
+
+# `nomad acl auth-method info` command reference
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/auth-method/list.mdx b/content/nomad/v1.11.x/content/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..e50819b59d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/auth-method/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method list command reference'
+description: |
+  The `nomad acl auth-method list` command lists existing access control list (ACL) authentication methods.
+---
+
+# `nomad acl auth-method list` command reference
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/auth-method/update.mdx b/content/nomad/v1.11.x/content/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..64189e7ddb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/auth-method/update.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method update command reference'
+description: |
+  The `nomad acl auth-method update` command updates an existing access control list (ACL) authentication method.  Modify name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method update` command reference
+
+The `acl auth-method update` command is used to update existing ACL Auth
+Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and
+  `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration][] in JSON format. You may provide '-'
+  to send the config through stdin, or prefix a file path with '@' to indicate
+  that the config should be loaded from the file.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -token-name-format '${auth_method_name}-${value.user}' -config @config.json example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = global
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_name}-${value.user}
+Default             = false
+Create Index        = 14
+Modify Index        = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.11.x/content/commands/acl/binding-rule/create.mdx b/content/nomad/v1.11.x/content/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..b784b04d97
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule create command reference'
+description: |
+  The `nomad acl binding-rule create` command creates new access control list (ACL) binding rules. Set a description, associated authentication method, selector expression, or bind name. Configure role, policy, or management bind type.
+---
+
+# `nomad acl binding-rule create` command reference
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.11.x/content/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..a9fada487b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule delete command reference'
+description: |
+  The `nomad acl binding-rule delete` command delete an existing access control list (ACL) binding rule.
+---
+
+# `nomad acl binding-rule delete` command reference
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/binding-rule/info.mdx b/content/nomad/v1.11.x/content/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..a437ecc7d7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule info command reference'
+description: |
+  The `nomad acl binding-rule info` command fetches information about an existing access control list (ACL) binding rule. Review ID, description, authentication method, selector, bind type, bind name, and time to live (TTL).
+---
+
+# `nomad acl binding-rule info` command reference
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/binding-rule/list.mdx b/content/nomad/v1.11.x/content/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..4d2238f803
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule list command reference'
+description: |
+  The `nomad acl binding-rule list` command displays access control list (ACL) binding rules.
+---
+
+# `nomad acl binding-rule list` command reference
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/binding-rule/update.mdx b/content/nomad/v1.11.x/content/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..cdc6eec37d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule update command reference'
+description: |
+    The `nomad acl binding-rule update` command modifies an existing access control list (ACL) binding rule. Update description, selector expression, bind name, and bind type.
+---
+
+# `nomad acl binding-rule update` command reference
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/bootstrap.mdx b/content/nomad/v1.11.x/content/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..a59b8b71a0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'nomad acl bootstrap command reference'
+description: |
+  The `nomad acl bootstrap` command creates the initial access control list (ACL) token. Nomad generates the token unless you provide a user-generated token.
+---
+
+# `nomad acl bootstrap` command reference
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways:
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-".
+Please make sure you secure this token in an appropriate manner as it could be written to your terminal history.
+
+## Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/index.mdx b/content/nomad/v1.11.x/content/commands/acl/index.mdx
new file mode 100644
index 0000000000..f58e2a91b6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/index.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'nomad acl command reference'
+description: |
+  The `nomad acl` command interacts with access control list (ACL) policies, roles, tokens, binding rules, and authentication methods.
+---
+
+# `nomad acl` command reference
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+```plaintext
+nomad acl <subcommand> [options]
+```
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl policy self`][policyself] - List ACL policies attached to the current workload
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/commands/acl/bootstrap
+[authmethodcreate]: /nomad/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/commands/acl/auth-method/info
+[authmethodlist]: /nomad/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/commands/acl/binding-rule/update
+[policyapply]: /nomad/commands/acl/policy/apply
+[policydelete]: /nomad/commands/acl/policy/delete
+[policyinfo]: /nomad/commands/acl/policy/info
+[policylist]: /nomad/commands/acl/policy/list
+[policyself]: /nomad/commands/acl/policy/self
+[tokencreate]: /nomad/commands/acl/token/create
+[tokenupdate]: /nomad/commands/acl/token/update
+[tokendelete]: /nomad/commands/acl/token/delete
+[tokeninfo]: /nomad/commands/acl/token/info
+[tokenlist]: /nomad/commands/acl/token/list
+[tokenself]: /nomad/commands/acl/token/self
+[rolecreate]: /nomad/commands/acl/role/create
+[roleupdate]: /nomad/commands/acl/role/update
+[roledelete]: /nomad/commands/acl/role/delete
+[roleinfo]: /nomad/commands/acl/role/info
+[rolelist]: /nomad/commands/acl/role/list
+[secure-guide]: /nomad/docs/secure/acl
+[federated]: /nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.11.x/content/commands/acl/policy/apply.mdx b/content/nomad/v1.11.x/content/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..b804329dcd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/policy/apply.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl policy apply command reference'
+description: |
+  The `nomad acl policy apply` command creates or updates an  access control list (ACL) policy. Set description, job, namespace, group, and task.
+---
+
+# `nomad acl policy apply` command reference
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set. Refer to [Workload Associated ACL Policies][] for more details.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.11.x/content/commands/acl/policy/delete.mdx b/content/nomad/v1.11.x/content/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..4d8dba5607
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad acl policy delete command reference'
+description: |
+  The `nomad acl policy delete` command deletes an access control list (ACL) policy.
+---
+
+# `nomad acl policy delete` command reference
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/policy/info.mdx b/content/nomad/v1.11.x/content/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..77e68fd145
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/policy/info.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad acl policy info command reference'
+description: >
+  The `nomad acl policy info` command fetches information on an access control list (ACL) policy. Review name, description, and workload, as well as access control list (ACL) policies and rules.
+---
+
+# `nomad acl policy info` command reference
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.11.x/content/commands/acl/policy/list.mdx b/content/nomad/v1.11.x/content/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..40db4bbcfe
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad acl policy list command reference'
+description: |
+  The `nomad acl policy list` command displays available access control list (ACL) policies.
+---
+
+# `nomad acl policy list` command reference
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/policy/self.mdx b/content/nomad/v1.11.x/content/commands/acl/policy/self.mdx
new file mode 100644
index 0000000000..3b9260e903
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/policy/self.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad acl policy self command reference'
+description: >
+  The `nomad acl policy self` command fetches information about the currently set access control list (ACL) policies available to the authenticated request.
+---
+
+# `nomad acl policy self` command reference
+
+The `nomad acl policy self` command fetches information about the currently
+set ACL policies attached to the workload or ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl policy self [options]
+```
+
+## Options
+
+- `-json` : Output the ACL policies in a JSON format.
+
+- `-t` : Format and display the ACL policies using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL policies attached to the workload.
+
+```shell-session
+$ echo $NOMAD_TOKEN
+eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA
+$ nomad acl policy self
+Name          Job ID  Group Name  Task Name
+nomad-policy  nomad   nomad       <not specified>
+$ nomad acl policy self -json
+[
+    {
+        "CreateIndex": 22,
+        "Description": "",
+        "JobACL": {
+            "Group": "nomad",
+            "JobID": "nomad",
+            "Namespace": "default",
+            "Task": ""
+        },
+        "ModifyIndex": 22,
+        "Name": "nomad-policy"
+    }
+]
+```
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/role/create.mdx b/content/nomad/v1.11.x/content/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..16bdf70ce5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/role/create.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad acl role create command reference'
+description: |
+    The `nomad acl role create` command creates an access control list (ACL) role. Set name, description, and associated policy.
+---
+
+# `nomad acl role create` command reference
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/role/delete.mdx b/content/nomad/v1.11.x/content/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..429a349b10
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/role/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl role delete command reference'
+description: |
+  The `nomad acl role delete` command deletes an access control list (ACL) role.
+---
+
+# `nomad acl role delete` command reference
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/role/info.mdx b/content/nomad/v1.11.x/content/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..708662f664
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/role/info.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role info command reference'
+description: |
+  The `nomad acl role info` command fetches information about an access control list (ACL) role. Review ID, name, description, and policies.
+---
+
+# `nomad acl role info` command reference
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/role/list.mdx b/content/nomad/v1.11.x/content/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..74fa739f1c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/role/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl role list command reference'
+description: |
+    The `nomad acl role list` displays access control list (ACL) roles.
+---
+
+# `nomad acl role list` command reference
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/role/update.mdx b/content/nomad/v1.11.x/content/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..cb5cc7a31d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/role/update.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role update command reference'
+description: |
+    The `nomad acl role update` command modifies an access control list (ACL) role. Modify name, description, and associated policy.
+---
+
+# `nomad acl role update` command reference
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/create.mdx b/content/nomad/v1.11.x/content/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..fb9f697c6a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'nomad acl token create command reference'
+description: |
+  The `nomad acl token create` command creates an access control list (ACL) token. Set name, client or management type, policy, role, time to live (TTL), and whether the policy should be global.
+---
+
+# `nomad acl token create` command reference
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## Create options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/delete.mdx b/content/nomad/v1.11.x/content/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..1643646792
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad acl token delete command reference'
+description: |
+  The `nomad acl token delete` command deletes an access control list (ACL) token.
+---
+
+# `nomad acl token delete` command reference
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/info.mdx b/content/nomad/v1.11.x/content/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..8f3b4d14cc
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/info.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad acl token info command reference'
+description: >
+  The `nomad acl token info` command fetches information about an access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token info` command reference
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/list.mdx b/content/nomad/v1.11.x/content/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..033ec225b2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl token list command reference'
+description: |
+  The `nomad acl token list` command displays access control list (ACL) tokens.
+---
+
+# `nomad acl token list` command reference
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## List options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/self.mdx b/content/nomad/v1.11.x/content/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..92bb917b06
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/self.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad acl token self command reference'
+description: >
+  The `nomad acl token self` command fetches information about the currently set access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token self` command reference
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
+
+The command also detects if the current Nomad token is a workload identity
+JWT and respond with a hint if that's the case.
+
+```shell-session
+$ echo $NOMAD_TOKEN
+eyJhbGciOiJSUzI1NiIsImtpZCI6ImJiMmUwYjI5LTIyZTYtYjk0My0yN2M1LThkYmNmMjc5ODM0MCIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJpYXQiOjE3NDM2OTI5NzksImp0aSI6IjJmOWI3ZGRmLWU1M2ItZGMxNS1kMzU4LTAyMDk5NjE1NThlMyIsIm5iZiI6MTc0MzY5Mjk3OSwibm9tYWRfYWxsb2NhdGlvbl9pZCI6IjhjMGJjMWFjLWRlMzMtYTNlYi03YWUwLTZiZjM3OGY5YzcxYiIsIm5vbWFkX2pvYl9pZCI6Im5vbWFkIiwibm9tYWRfbmFtZXNwYWNlIjoiZGVmYXVsdCIsIm5vbWFkX3Rhc2siOiJzZXJ2ZXIiLCJzdWIiOiJnbG9iYWw6ZGVmYXVsdDpub21hZDpub21hZDpzZXJ2ZXI6ZGVmYXVsdCJ9.IDZWTqGWRURDwI5OvO3LLjCsU1qzg6LEG4q5S7CfZawUXzMqAOoYajI_nynOGJp2aU77MqUyJmdFtrIBMoQnIxclEwNl9DkhfOrgjBsWefn9JqKEpORGD-0OLzaoYUgbu0k6aXCNktfpvHZN5uUsfL6nLOG-osQvHn9ZdboT31tjp1v6d-MfP96ZLG0NrXgLWMfwan2AAzuqMabIS9iO6OrZDNp2-TeeY_sqM-7sNEgfDo33GAeyhqTi8CAZhsDOv4wtJuFfMhrsbb33wHdAiltjXlafBtncMMaLHr07gbLvOMfty2_193i4Yi3H2PgPr7c4BYHoXyQJhFchDyYmFA
+$ nomad acl token self
+No ACL token found but there are ACL policies attached to this workload identity. You can query them with acl policy self command.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/acl/token/update.mdx b/content/nomad/v1.11.x/content/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..561709f082
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/acl/token/update.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl token update command reference'
+description: |
+  The `nomad acl token update` command modifies an access control list (ACL) token. Update name, client or management type, policy, and role.
+---
+
+# `nomad acl token update` command reference
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## Update options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens. If any policies are
+  specified, they completely replace the policies on the existing token.
+
+- `-role-id`: ID of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+- `-role-name`: Name of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/agent-info.mdx b/content/nomad/v1.11.x/content/commands/agent-info.mdx
new file mode 100644
index 0000000000..f1f5fa8572
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'nomad agent-info command reference'
+description: |
+  The `nomad agent-info` command retrieves metrics and status information for a running agent. Use this command to review agent data from the client, nomad, serf, raft, and runtime subsystems.
+---
+
+# `nomad agent-info` command reference
+
+The `nomad agent-info` command retrieves metrics and status information for a
+running agent. The information returned pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, the `nomad agent-info` command retrieves
+information from the following subsystems:
+
+- Client: Status of the local Nomad client
+- Nomad: Status of the local Nomad server
+- Serf: Gossip protocol metrics and information
+- Raft: Status information about the Raft consensus protocol
+- Runtime: Various metrics from the runtime environment
+
+## Example
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/agent.mdx b/content/nomad/v1.11.x/content/commands/agent.mdx
new file mode 100644
index 0000000000..a7739bb92c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/agent.mdx
@@ -0,0 +1,274 @@
+---
+layout: docs
+page_title: 'nomad agent command reference'
+description: |
+  The `nomad agent` command starts the Nomad agent, which handles client or server functionality, including exposing interfaces for client consumption and running jobs. The agent runs until it receives an interrupt signal.
+---
+
+# `nomad agent` command reference
+
+The `nomad agent` command starts the Nomad agent, which handles client or server
+functionality, including exposing interfaces for client consumption and running
+jobs. The agent runs until it receives an interrupt signal.
+
+Refer to [Operating Nomad agents] and [Nomad agent configuration] for more
+information on how to use this command and the options it has.
+
+## Usage
+
+If you are running Nomad on Linux, you need to run client agents as root, or
+with `sudo`, so that cpuset accounting and network namespaces work correctly.
+
+```plaintext
+nomad agent [options]
+```
+
+## Options
+
+We recommend configuring a Nomad agent with configuration files. Refer to [Nomad
+agent configuration] for details.
+
+You may, however, may pass the following configuration options as CLI arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir][] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled][] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token][] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr][] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect][] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-client-intro-token`: The JWT token used to authenticate with servers during
+  the client's initial registration. You may also set the token via the
+  `NOMAD_CLIENT_INTRO_TOKEN` environment variable, which overrides this flag. If
+  neither is set, the agent looks for an `intro_token.jwt` file within the
+  [`client_state_dir`][]. It is not possible to set the intro token via a
+  configuration file.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address][] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth][] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise][] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file][] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file][] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise][]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join][] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name][]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name][] config option.
+
+- `-consul-client-failures-before-critical=<num>`: Equivalent to the
+  [client_failures_before_critical][] config option.
+
+- `-consul-client-failures-before-warning=<num>`: Equivalent to the
+  [client_failures_before_warning][] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file][] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name][]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name][] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name][] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name][] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join][] config
+  option.
+
+- `-consul-server-failures-before-critical=<num>`: Equivalent to the
+  [server_failures_before_critical][] config option.
+
+- `-consul-server-failures-before-warning=<num>`: Equivalent to the
+  [server_failures_before_warning][] config option.
+
+- `-consul-ssl`: Equivalent to the [ssl][] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token][] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl][] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir][] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter][] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul service mesh. It may be
+  used with `-dev-consul` to configure default workload identities for Consul.
+  This mode is supported only on Linux as root.
+
+- `-dev-consul`: Starts the agent in development mode with a default Consul
+  configuration for Nomad workload identity. It may be used with `-dev-connect`
+  to configure the agent for Consul Service Mesh.
+
+- `-dev-vault`: Starts the agent in development mode with a default Vault
+  configuration for Nomad workload identity.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview][] for
+  more details.
+
+- `-eventlog`: Equivalent to the [eventlog.enabled][] config option.
+
+- `-eventlog-level`: Equivalent to the [eventlog.level][] config option.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level][] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location][] config option.
+
+- `-log-json`: Equivalent to the [log_json][] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta][] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface][] config option.
+
+- `-node=<name>`: Equivalent to the [name][] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class][]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool][]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir][] config option.
+
+- `-region=<region>`: Equivalent to the [region][] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave][] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval][] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max][] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers][] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir][] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_failures_before_critical]: /nomad/docs/configuration/consul#client_failures_before_critical
+[client_failures_before_warning]: /nomad/docs/configuration/consul#client_failures_before_warning
+[server_failures_before_critical]: /nomad/docs/configuration/consul#server_failures_before_critical
+[server_failures_before_warning]: /nomad/docs/configuration/consul#server_failures_before_warning
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[`client_state_dir`]: /nomad/docs/configuration/client#state_dir
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/docs/secure/traffic/gossip-encryption
+[eventlog.enabled]: /nomad/docs/configuration#eventlog_enabled
+[eventlog.level]: /nomad/docs/configuration#eventlog_level
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[Operating Nomad agents]: /nomad/docs/deploy/nomad-agent
+[Nomad agent configuration]: /nomad/docs/configuration
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.11.x/content/commands/alloc/checks.mdx b/content/nomad/v1.11.x/content/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..d078510b8c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'nomad alloc checks command reference'
+description: |
+  The `nomad alloc checks` command displays service health check status information for an allocation.
+---
+
+# `nomad alloc checks` command reference
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability
+for the allocation's namespace. The 'list-jobs' capability is required to run the
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/exec.mdx b/content/nomad/v1.11.x/content/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..0513ef9d7a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/exec.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: 'nomad alloc exec command reference'
+description: |
+  The `nomad alloc exec` runs a command inside a running task allocation, which is useful for debugging. Execute commands with or without an interactive shell inside the allocation.
+---
+
+# `nomad alloc exec` command reference
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+### Disable remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+### Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+## Options
+
+- `-task=<task-name>`: Sets the task to exec command in.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` `<escape_char>`: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.11.x/content/commands/alloc/fs.mdx b/content/nomad/v1.11.x/content/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..689170f24b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/fs.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: 'nomad alloc fs command reference'
+description: |
+  The `nomad alloc fs` lets you navigate an allocation working directory on a Nomad client.
+---
+
+# `nomad alloc fs` command reference
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad prefers selecting a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad uses a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+## Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best effort number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/index.mdx b/content/nomad/v1.11.x/content/commands/alloc/index.mdx
new file mode 100644
index 0000000000..c4af5cea60
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/index.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'nomad alloc command reference'
+description: |
+  The `nomad alloc` commands interact with allocations. Access allocation directories, display status and health checks, stream task logs, run commands inside an allocation, and signal a running allocation. You can also stop, reschedule, and restart a running allocation.
+---
+
+# `nomad alloc` command reference
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+```plaintext
+nomad alloc <subcommand> [options]
+```
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/logs.mdx b/content/nomad/v1.11.x/content/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..012bf5cbbb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/logs.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'nomad alloc logs command reference'
+description: |
+  The `nomad alloc logs` command streams the task logs from an allocation.
+---
+
+# `nomad alloc logs` command reference
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+### Use Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad prefers selecting a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad uses a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job=<job-name|job-id>`: Use a random allocation from the specified job or
+  job ID prefix, preferring a running allocation.
+
+- `-task=<task-name>`: Specify the task to view the logs.
+
+- `-group=<group-name>`: Specifies the task group where the task is located
+  when a random allocation is selected
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/pause.mdx b/content/nomad/v1.11.x/content/commands/alloc/pause.mdx
new file mode 100644
index 0000000000..619d769608
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/pause.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'nomad alloc pause command reference'
+description: |
+  The `nomad alloc pause` command overrides the schedule for tasks using time-based execution, forcing the task to either stop or run.
+---
+
+# `nomad alloc pause` command reference
+
+Override the schedule for tasks using time based execution.
+
+<EnterpriseAlert />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+## Usage
+
+```plaintext
+nomad alloc pause [options] <allocation> <command>
+```
+
+The `alloc pause` command allows a user to override the schedule for tasks
+that use time based execution. A user may override a task's
+[`schedule`][schedule] and force it to run or stop. The `schedule` will be
+ignored until a user resets the override.
+
+When ACLs are enabled, this command requires the `job-submit` capability for
+the allocation's namespace.
+
+## Options
+
+- `-state`: Override the current scheduled task state to be the specified state
+  or reset to the scheduled state. Must be one of `pause`, `run`, or
+  `scheduled`. When set to `pause` the task is halted. When set to `run` the
+  task is started. When set to `scheduled` the task respects its
+  [`schedule`][schedule].
+
+- `-status`: Get the current time based task execution state.
+
+- `-task`: Override the schedule of the specified task. May also be specified
+  as a positional argument.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+The following command stops the `schedtask` task of the allocation `4d37a9d1`
+overriding the task's [`schedule`][schedule] block:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command runs the task overriding the tasks current state or
+schedule:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command returns the task to its [`schedule`][schedule]:
+
+```shell-session
+$ nomad alloc pause -state=scheduled 4d37a9d1 schedtask
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[schedule]: /nomad/docs/job-specification/schedule
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.11.x/content/commands/alloc/restart.mdx b/content/nomad/v1.11.x/content/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..f0c5e73057
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad alloc restart command reference'
+description: |
+  The `nomad alloc restart` command restarts a running task or an entire allocation.
+---
+
+# `nomad alloc restart` command reference
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/signal.mdx b/content/nomad/v1.11.x/content/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..aca5f5e3a1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad alloc signal command reference'
+description: |
+  The `nomad alloc signal` command sends a signal to a running allocation or task.
+---
+
+# `nomad alloc signal` command reference
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/status.mdx b/content/nomad/v1.11.x/content/commands/alloc/status.mdx
new file mode 100644
index 0000000000..eff3171fe0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/status.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: 'nomad alloc status command reference'
+description: |
+  The `nomad alloc status` command display status and metadata about existing allocations and their tasks.
+---
+
+# `nomad alloc status` command reference
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full-length IDs, exact timestamps, and placement metrics.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+- `-ui` : Open the allocation status page in the browser.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+The `-verbose` flag includes information about the scheduler's placement
+decision, including the number of nodes evaluated and rejected, and the scoring
+of each node considered.
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-affinity  node-reschedule-penalty  final score
+43c0b14e-7f96-e432-a7da-06605257ce0c  0.0238   0                  0              0                        0.0238
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/alloc/stop.mdx b/content/nomad/v1.11.x/content/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..1d41a1afc2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/alloc/stop.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad alloc stop command reference'
+description: |
+  The `nomad alloc stop` command perform an in-place restart of an entire allocation or an individual task.
+---
+
+# `nomad alloc stop` command reference
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped, otherwise, a list of
+matching allocs and information will be displayed. If the stopped allocation
+belongs to a service or batch job they will rescheduled according to their
+reschedule policy. [System allocs will not][] and will show up as completed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[system allocs will not]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/commands/config/index.mdx b/content/nomad/v1.11.x/content/commands/config/index.mdx
new file mode 100644
index 0000000000..a059419873
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/config/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'nomad config command reference'
+description: |
+  The `nomad config` command interacts with configurations. Validate configuration files.
+---
+
+# `nomad config` command reference
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+```plaintext
+nomad config <subcommand> [options]
+```
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.11.x/content/commands/config/validate.mdx b/content/nomad/v1.11.x/content/commands/config/validate.mdx
new file mode 100644
index 0000000000..98787632c0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'nomad config validate command reference'
+description: |
+  The `nomad config validate` command validates Nomad configuration files so you can test Nomad configuration without starting the agent.
+---
+
+# `nomad config validate` command reference
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/deployment/fail.mdx b/content/nomad/v1.11.x/content/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..7b07211ab1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad deployment fail command reference'
+description: |
+  The `nomad deployment fail` command manually fails a deployment, which stops the placement of new allocations.
+---
+
+# `nomad deployment fail` command reference
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/deployment/index.mdx b/content/nomad/v1.11.x/content/commands/deployment/index.mdx
new file mode 100644
index 0000000000..b2e46d0175
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad deployment command reference'
+description: |
+  The `nomad deployment` command interacts with deployments. List deployments, fetch status, and promote canaries. Pause, resume, and fail deployments.
+---
+
+# `nomad deployment` command reference
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+```plaintext
+nomad deployment <subcommand> [options]
+```
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/commands/deployment/list 'List all deployments'
+[pause]: /nomad/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.11.x/content/commands/deployment/list.mdx b/content/nomad/v1.11.x/content/commands/deployment/list.mdx
new file mode 100644
index 0000000000..dca7210120
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad deployment list command reference'
+description: |
+  The `nomad deployment list` command lists deployments.
+---
+
+# `nomad deployment list` command reference
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/deployment/pause.mdx b/content/nomad/v1.11.x/content/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..9f212712c0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/pause.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad deployment pause command reference'
+description: >
+  The `nomad deployment pause` command pauses a deployment and does not allow new allocations.
+---
+
+# `nomad deployment pause` command reference
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/deployment/promote.mdx b/content/nomad/v1.11.x/content/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..538a8ef49f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'nomad deployment promote command reference'
+description: |
+  The `nomad deployment promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad deployment promote` command reference
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`job revert`]: /nomad/commands/job/revert
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/deployment/resume.mdx b/content/nomad/v1.11.x/content/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..f329148a0f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad deployment resume command reference'
+description: |
+  The `nomad deployment resume` command resumes a paused deployment.
+---
+
+# `nomad deployment resume` command reference
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/deployment/status.mdx b/content/nomad/v1.11.x/content/commands/deployment/status.mdx
new file mode 100644
index 0000000000..0eeaed245e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/status.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'nomad deployment status command reference'
+description: |
+  The `nomad deployment status` command displays the status of a deployment.
+---
+
+# `nomad deployment status` command reference
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+- `-ui`: Open the deployment page in the browser.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully
+Windows compatible so there may be some formatting differences (different margins, no spinner
+indicating deployment is in progress).
+
+## General options
+
+@include 'general_options.mdx'
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
diff --git a/content/nomad/v1.11.x/content/commands/deployment/unblock.mdx b/content/nomad/v1.11.x/content/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..fab3def1a4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'nomad deployment unblock command reference'
+description: |
+  The`nomad deployment unblock` command marks a blocked multi-region deployment as successful so you can force completion when there is a failed peer region.
+---
+
+# `nomad deployment unblock` command reference
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[federated regions]: //nomad/docs/deploy/clusters/federate-regions
diff --git a/content/nomad/v1.11.x/content/commands/eval/delete.mdx b/content/nomad/v1.11.x/content/commands/eval/delete.mdx
new file mode 100644
index 0000000000..a504fc2842
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad eval delete command reference'
+description: |
+  The `nomad eval delete` command deletes an evaluation by ID or a group of evaluations that match a filter.
+---
+
+# `nomad eval delete` command reference
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfully deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfully deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfully deleted 23 evaluations
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[scheduler_get_config]: /nomad/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.11.x/content/commands/eval/index.mdx b/content/nomad/v1.11.x/content/commands/eval/index.mdx
new file mode 100644
index 0000000000..8911c507c7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/eval/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad eval command reference'
+description: |
+  The `nomad eval` command interact with evaluations. Fetch status, delete an evaluation, and list all evaluations.
+---
+
+# `nomad eval` command reference
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+```plaintext
+nomad eval <subcommand> [options]
+```
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/commands/eval/delete 'Delete evals'
+[list]: /nomad/commands/eval/list 'List all evals'
+[status]: /nomad/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.11.x/content/commands/eval/list.mdx b/content/nomad/v1.11.x/content/commands/eval/list.mdx
new file mode 100644
index 0000000000..d94cdc0578
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/eval/list.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'nomad eval list command reference'
+description: |
+  The `nomad eval list` command displays a list of all evaluations or evaluations that match a filter.
+---
+
+# `nomad eval list` command reference
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+- `-ui`: Open the evaluations page in the browser.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/eval/status.mdx b/content/nomad/v1.11.x/content/commands/eval/status.mdx
new file mode 100644
index 0000000000..a8db500197
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/eval/status.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'nomad eval status command reference'
+description: >
+  The `nomad eval status` command displays the status and potential failed
+  allocations of an evaluation. Use with the `monitor` flag to start an interactive monitoring session.
+---
+
+# `nomad eval status` command reference
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full-length IDs, exact timestamps, and all reconciler
+  annotation fields.
+- `-json`: Output the evaluation in its JSON format. This format will not
+    include placed allocations.
+- `-t` : Format and display evaluation using a Go template. This format will not
+  include placed allocations.
+- `-ui`: Open the evaluation in the browser.
+
+## Examples
+
+Show the status of an evaluation with related evaluations, successful
+placements, scheduler annotations, failed placements, and preemptions.
+
+The plan annotations table shows the output of the scheduler's reconciliation
+stage, which produces a desired set of changes that later stages of the
+scheduler attempt. The [`update.max_parallel`][] field or placement failures may
+result in a difference between these numbers and the updates made to the
+job. This table will always include the count for allocations to ignore, place,
+stop, inplace update, and destructively update. It may also include the count of
+canary allocations or allocations that were rescheduled, migrated, preemptted,
+reconnected, or disconnected. Any of these counts may overlap so that, for
+example, an allocation can be both migrated and stopped.
+
+```shell-session
+$ nomad eval status 8f6af533
+ID                 = 8f6af533
+Create Time        = 11s ago
+Modify Time        = 10s ago
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+Previous Eval      = c324b46f
+Next Eval          = <none>
+Blocked Eval       = 2b83d3af
+
+Related Evaluations
+ID        Priority  Triggered By   Node ID  Status   Description
+fd6f3091  50        queued-allocs  <none>   pending  <none>
+
+Plan Annotations
+Task Group  Ignore  Place  Stop  InPlace  Destructive  Migrate  Canary  Preemptions
+group       0       3      0     0        0            0        0       1
+
+Preempted Allocations
+ID        Job ID    Node ID   Task Group  Version  Desired  Status   Created   Modified
+116e9046  example1  24c15262  group       0        run      running  1m9s ago  2s ago
+
+Placed Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+b7e298fa  24c15262  web         2        run      running  10s ago  2s ago
+108841a9  41f70903  web         2        run      pending  3s ago   1s ago
+4869a26d  d372b337  web         2        run      pending  4s ago   0s ago
+
+Failed Placements
+Task Group "web" (failed to place 1 allocation):
+  * Constraint "${attr.kernel.name} = linux": 2 nodes excluded by filter
+  * Resources exhausted on 2 nodes
+  * Dimension "memory" exhausted on 2 nodes
+
+Evaluation "2b83d3af" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`update.max_parallel`]: /nomad/docs/job-specification/update#max_parallel
diff --git a/content/nomad/v1.11.x/content/commands/fmt.mdx b/content/nomad/v1.11.x/content/commands/fmt.mdx
new file mode 100644
index 0000000000..db766ea90c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/fmt.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad fmt command reference'
+description: |
+  The `nomad fmt` commands rewrites Nomad configuration and job specification
+   files to canonical format. Use this command to improve readability and enforce consistency of style in Nomad files.
+---
+
+# `nomad fmt` command reference
+
+The `nomad fmt` command rewrites Nomad configuration and job specification files
+to canonical format. Use this command to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [options] paths ...
+```
+
+If a path is a directory, the command recursively formats all files with
+`.nomad` and `.hcl` extensions in the directory. If you provide a single dash
+(-) as an argument, the `nomad fmt` command reads from standard input and
+writes the processed text to standard output.
+
+The `nomad fmt` command checks the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 job specification results in errors.
+
+## Options
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.11.x/content/commands/index.mdx b/content/nomad/v1.11.x/content/commands/index.mdx
new file mode 100644
index 0000000000..39da9db98a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/index.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: Nomad command-line interface (CLI) reference
+description: >
+  The Nomad command-line interface (CLI) interacts with a Nomad cluster. This page contains reference information on how to install CLI autocomplete, configure remote usage, and specify CLI options. Review connection, access control list (ACL), mutual TLS (mTLS), and license environment variables.
+---
+
+# Nomad command-line interface (CLI) reference
+
+The Nomad CLI is a well-behaved command-line application. In erroneous cases,
+the CLI returns a non-zero exit status. To view a list of available commands,
+run the `nomad` command with no arguments, `-h`, or `--help`. To access help for
+any specific subcommand, run the subcommand with the `-h` argument.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete.
+
+To install autocomplete, run the `nomad` command with the
+`-autocomplete-install` option.
+
+```shell-session
+$ nomad -autocomplete-install
+```
+
+To uninstall autocomplete, run the `nomad` command with the
+`-autocomplete-uninstall` option.
+
+```shell-session
+$ nomad -autocomplete-uninstall
+```
+
+## Command contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise. For example, the `nomad job run` command runs a new job and the
+`nomad status` command queries information about existing jobs. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote usage
+
+You may use the Nomad CLI to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The Nomad address must be reachable from your local machine. If the Nomad
+port is exposed to the public internet, we recommend configuring TLS. Refer to
+the [`tls` block in agent configuration] for details.
+
+### Environment variables
+
+Nomad can use environment variables to configure command-line tool options. You
+may override these environment variables with individual flags. Except where
+noted, these variables influence the behavior of the Nomad CLI and should not be
+set for Nomad agents.
+
+#### Connection environment variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`. For unix sockets, as with the [task API][],
+  the format is either `unix:/path/to/api.sock` or `unix:///path/to/api.sock`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### Access control list (ACL) environment variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI environment variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+- `NOMAD_CLI_SHOW_HINTS` - Enables ui-hints in common CLI command output.
+
+#### Mutual TLS (mTLS) environment variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise license environment variables
+
+These environment variables influence the Nomad Enterprise license
+configuration. These values are only used for Nomad Enterprise agents, not the
+Nomad CLI.
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
+
+
+[task API]: /nomad/api-docs/task-api
+[`tls` block in agent configuration]: /nomad/docs/configuration/tls
diff --git a/content/nomad/v1.11.x/content/commands/job/action.mdx b/content/nomad/v1.11.x/content/commands/job/action.mdx
new file mode 100644
index 0000000000..6adb072e99
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/action.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'nomad job action command reference'
+description: |
+  The `nomad job action` command executes predefined actions from a job
+  specification in a running task context.
+---
+
+# `nomad job action` command reference
+
+**Alias: `nomad action`**
+
+The `job action` command allows operators to execute predefined actions declared
+in Nomad job specifications. These actions can be defined at task level and are
+intended for specific operational tasks, such as clearing a cache, or migrating
+a database.
+
+An action may self-terminate upon completion (for example, echoing a string),
+or run for an indeterminate amount of time (for example, watching a blocking
+query). In the latter case, an action can be terminated via escape character
+(such as cmd+c / ctrl+c)
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `alloc-exec`, `read-job`, and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Usage
+
+```plaintext
+nomad job action [options] <action>
+```
+
+The `job action` command requires an action name and accepts two ways of
+specifying where it should run:
+- by passing the job name and known allocation ID along with the name of the action
+- by passing the job, task group, and task name along with the name of the action
+(when the allocation ID is not known). A random allocation will be selected if
+multiple are available.
+
+The action name provided must be defined within a task in the [job specification]
+provided. With sufficient privileges, an execution context will be opened and
+the defined action command will be run. No further input is possible, save for
+the escape character to terminate execution, so interactive commands are not
+supported.
+
+## Options
+
+- `-job`: (Required) Specifies the job containing the predefined action.
+
+- `-alloc`: Specifies the allocation within which the action is to be executed.
+  If omitted, `-group` and `-task` must be provided, and a random
+  allocation for the group will be selected.
+
+- `-task`: Specifies the task within the job where the action is defined. This
+  is required either if `-alloc` provided and your group has multiple tasks,
+  or if you specify a `-group`.
+
+- `-group`: Specifies the task group within the job. If present, a random
+  allocation is selected. If omitted, `-alloc` must be provided.
+
+- `-i`: Pass stdin to the action, defaults to `true`. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to `true` if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` `<escape_char>`: Sets the escape character for sessions with a pty,
+  defaults to '~'. The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot (`.`) closes the connection.
+  Setting the character to `none` disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+Execute an action within a specific task in a job:
+
+```shell-session
+$ nomad action \
+  -group=my-group \
+  -task=my-task \
+  -job=my-job \
+  weather
+
+Toronto: ☁️   +3°C
+```
+
+Execute an action within a specific allocation:
+
+```shell-session
+$ nomad action \
+  -alloc=f200a789-6da4-504c-d131-6181764f101e \
+  -job=actions-demo \
+  echo-time
+
+Running for 0 seconds
+Running for 1 seconds
+Running for 2 seconds
+Running for 3 seconds
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.11.x/content/commands/job/allocs.mdx b/content/nomad/v1.11.x/content/commands/job/allocs.mdx
new file mode 100644
index 0000000000..8dcdf2ee23
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/allocs.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad job allocs command reference'
+description: |
+  The `nomad job allocs`  command lists allocations for a job.
+---
+
+# `nomad job allocs` command reference
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With
+Templates](/nomad/docs/manage/format-cli-output) tutorial for
+more examples of using Go templates to format Nomad CLI output.
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/deployments.mdx b/content/nomad/v1.11.x/content/commands/job/deployments.mdx
new file mode 100644
index 0000000000..e6e2b861af
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad job deployments command reference'
+description: |
+  The `nomad job deployments` command lists deployments for a job.
+---
+
+# `nomad job deployments` command reference
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/dispatch.mdx b/content/nomad/v1.11.x/content/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..58ec328aa9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/dispatch.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: 'nomad job dispatch command reference'
+description: |
+  The `nomad job dispatch` creates an instance of a parameterized job.
+---
+
+# `nomad job dispatch` command reference
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+- `-ui`: Open the dispatched job in the browser.
+
+- `-priority`: Optional integer between 1 and [`job_max_priority`],
+  inclusively that overrides any priority value inherited from the parent job.
+  For general usage information on the priority flag see [job parameters].
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[job parameters]: /nomad/docs/job-specification/job#parameters
diff --git a/content/nomad/v1.11.x/content/commands/job/eval.mdx b/content/nomad/v1.11.x/content/commands/job/eval.mdx
new file mode 100644
index 0000000000..87d414b121
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'nomad job eval command reference'
+description: |
+  The `nomad job eval` command forces an evaluation of a job. Optionally, force placement of failed allocations.
+---
+
+# `nomad job eval` command reference
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/job/history.mdx b/content/nomad/v1.11.x/content/commands/job/history.mdx
new file mode 100644
index 0000000000..3754653335
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/history.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'nomad job history command reference'
+description: |
+  The `nomad job history` command displays the history of a single version or all tracked versions of a job. Optionally display the difference between two versions or tags or differences between each job and its predecessor.
+---
+
+# `nomad job history` command reference
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+- `-diff-version`: Compare the job with a specific version.
+- `-diff-tag`: Compare the job with a specific tag.
+
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
+
+Compare the current job with a specific older version:
+
+```shell-session
+$ nomad job history -version=3 -diff-version=1 example
+Version     = 3
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+```
+
+Compare all job versions with a specific version by tag name:
+
+```shell-session
+$ nomad job history -diff-tag=low-energy-version example
+
+Version     = 3
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "4"
+      Task: "task"
+
+Version         = 2
+Stable          = false
+Submit Date     = 2024-09-09T16:41:53-04:00
+Tag Name        = low-energy-version
+Tag Description = test description
+
+Version     = 1
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "2"
+      Task: "task"
+
+Version     = 0
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "1"
+      Task: "task"
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/index.mdx b/content/nomad/v1.11.x/content/commands/job/index.mdx
new file mode 100644
index 0000000000..c57460cbae
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/index.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad job command reference'
+description: |
+  The `nomad job` command interacts with jobs. Create, validate, and plan a job specification. Display allocations, deployments, history, and status. Execute predefined actions, dispatch parameterized jobs, inspect a job, force the evaluation of a periodic job, scale allocations, and promote canaries. Run, restart, revert, and stop a job.
+---
+
+# `nomad job` command reference
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+```plaintext
+nomad job <subcommand> [options]
+```
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job action`][action] - Execute predefined actions
+- [`job allocs`][allocs] - List allocations for a job
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job init`][init] - Create an example job specification
+- [`job inspect`][inspect] - Inspect the contents of a submitted job
+- [`job periodic force`][periodic force] - Force the evaluation of a periodic job
+- [`job plan`][plan] - Schedule a dry run for a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job restart`][restart] - Restart or reschedule allocations for a job
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job run`][run] - Submit a new job
+- [`job scale`][scale] - Update the number of allocations for a task group in a job
+- [`job scaling-events`][scaling-events] - List the recent scaling events for a job
+- [`job status`][status] - Display status information about a job
+- [`job stop`][stop] - Stop a running job and cancel its allocations
+- [`job tag`][tag] - Tag a job with a version
+- [`job validate`][validate] - Check a job specification for syntax errors
+
+
+[action]: /nomad/commands/job/action 'Execute predefined actions'
+[allocs]: /nomad/commands/job/allocs 'List allocations for a job'
+[deployments]: /nomad/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/commands/job/history 'Display all tracked versions of a job'
+[init]: /nomad/commands/job/init 'Create an example job specification'
+[inspect]: /nomad/commands/job/inspect 'Inspect the contents of a submitted job'
+[periodic force]: /nomad/commands/job/periodic-force 'Force the evaluation of a periodic job'
+[plan]: /nomad/commands/job/plan 'Schedule a dry run for a job'
+[restart]: /nomad/commands/job/restart 'Restart or reschedule allocations for a job'
+[revert]: /nomad/commands/job/revert 'Revert to a prior version of the job'
+[run]: /nomad/commands/job/run 'Submit a new job'
+[status]: /nomad/commands/job/status 'Display status information about a job'
+[scale]: /nomad/commands/job/scale 'Update the number of allocations for a task group in a job'
+[scaling-events]: /nomad/commands/job/scaling-events 'List the recent scaling events for a job'
+[stop]: /nomad/commands/job/stop 'Stop a running job and cancel its allocations'
+[tag]: /nomad/commands/job/tag 'Tag a job with a version'
+[validate]: /nomad/commands/job/validate 'Check a job specification for syntax errors'
+[promote]: /nomad/commands/job/promote
diff --git a/content/nomad/v1.11.x/content/commands/job/init.mdx b/content/nomad/v1.11.x/content/commands/job/init.mdx
new file mode 100644
index 0000000000..85c17ad078
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad job init command reference'
+description: |
+  The `nomad job init` command generates a job specification with example configurations for tasks, task groups, runtime constraints, and resource allocation.
+---
+
+# `nomad job init` command reference
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul service mesh integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/job-declare/task-driver 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.11.x/content/commands/job/inspect.mdx b/content/nomad/v1.11.x/content/commands/job/inspect.mdx
new file mode 100644
index 0000000000..798547e0d2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/inspect.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'nomad job inspect command reference'
+description: |
+  The `nomad job inspect` command displays a complete job definition so you can inspect contents.
+---
+
+# `nomad job inspect` command reference
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format. Cannot be used with `-hcl`.
+- `-hcl`: Output the original HCL submitted with the job. Cannot be used with
+  `-json`.
+- `-with-vars`: Include the original HCL2 variables submitted with the job. Can
+    only be used with `-hcl`.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.11.x/content/commands/job/periodic-force.mdx b/content/nomad/v1.11.x/content/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..a32c962b02
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad job periodic force command reference'
+description: >
+  The `nomad job periodic force` command forces the evaluation of a periodic
+  job. Use this command to immediately run a periodic job, even if it violates the job's `prohibit_overlap` setting.
+---
+
+# `nomad job periodic force` command reference
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.11.x/content/commands/job/plan.mdx b/content/nomad/v1.11.x/content/commands/job/plan.mdx
new file mode 100644
index 0000000000..b57ffb2de8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/plan.mdx
@@ -0,0 +1,243 @@
+---
+layout: docs
+page_title: 'nomad job plan command reference'
+description: |
+  The `nomad job plan` command executes a dry run of a job to determine its effects.
+---
+
+# `nomad job plan` command reference
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+## General options
+
+@include 'general_options.mdx'
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
diff --git a/content/nomad/v1.11.x/content/commands/job/promote.mdx b/content/nomad/v1.11.x/content/commands/job/promote.mdx
new file mode 100644
index 0000000000..de8e2b5366
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'nomad job promote command reference'
+description: |
+  The `nomad job promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad job promote` command reference
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[job revert]: /nomad/commands/job/revert
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/job/restart.mdx b/content/nomad/v1.11.x/content/commands/job/restart.mdx
new file mode 100644
index 0000000000..3437e90549
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'nomad job restart command reference'
+description: |
+  The `nomad job restart` command restarts or reschedules allocations for a job.
+---
+
+# `nomad job restart` command reference
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular running job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+You may restart in-place or migrated allocations. When restarting in-place, the
+command may target specific tasks in the allocations, restart only tasks that
+are currently running, or restart all tasks, even the ones that have already
+run. Groups and tasks can also target allocations.  When you define both groups
+and tasks, Nomad restarts only the tasks for the allocations of those groups.
+
+When migrating, Nomad stops the current allocations, triggering the Nomad
+scheduler to create new allocations that may be placed in different clients. The
+command waits until the new allocations have client status `ready` before
+proceeding with the remaining batches. The command does not consider service
+health checks.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, Nomad stops and migrates allocations instead of
+  restarting in-place. Since the group is not modified, the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such as
+  [`max_parallel`][], are not considered. This option cannot be used with
+  `-task`. You may only migrate jobs of type `batch`, `service`, and `system`.
+  Note that despite the name of this flag, this command migrates but does not
+  reschedule allocations, so it ignores the `reschedule` block.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.11.x/content/commands/job/revert.mdx b/content/nomad/v1.11.x/content/commands/job/revert.mdx
new file mode 100644
index 0000000000..94235dbe59
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/revert.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'nomad job revert command reference'
+description: |
+  The `nomad job revert` command reverts the current job to a prior version.
+---
+
+# `nomad job revert` command reference
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+## Usage
+
+```shell-session
+nomad job revert [options] <job> <version|tag>
+```
+
+The `job revert` command requires two inputs: the job ID, and the version number
+or tag of the job to revert to.  When you specify a version number, Nomad
+reverts the job to the exact version number. Alternately, when you specify a
+custom tag name as a string, Nomad reverts to the version tagged with that
+name.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`job history`]: /nomad/commands/job/history
+[eval status]: /nomad/commands/eval/status
+[run]: /nomad/commands/job/run
diff --git a/content/nomad/v1.11.x/content/commands/job/run.mdx b/content/nomad/v1.11.x/content/commands/job/run.mdx
new file mode 100644
index 0000000000..099878fef9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/run.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: 'nomad job run command reference'
+description: |
+  The `nomad job run` command submits a job to Nomad for scheduling, which then runs the job.
+---
+
+# `nomad job run` command reference
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and deployment status for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts are preserved when
+  updating a job.
+
+- `-preserve-resources`: If set, the existing task resources are preserved when
+  updating a job, so that autoscaling changes are not overwritten.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. Consul must be configured to authenticate
+  using Nomad Workload Identities.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+- `-ui`: Open the job page in the browser.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`batch`]: /nomad/docs/concepts/scheduling/schedulers#batch
+[eval status]: /nomad/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/concepts/scheduling/schedulers#system
diff --git a/content/nomad/v1.11.x/content/commands/job/scale.mdx b/content/nomad/v1.11.x/content/commands/job/scale.mdx
new file mode 100644
index 0000000000..c346cc29af
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/scale.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'nomad job scale command reference'
+description: |
+  The `nomad job scale` command changes the number of running allocations within
+  a Nomad task group.
+---
+
+# `nomad job scale` command reference
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## Options
+
+- `-check-index`: If set, the job is only scaled if the passed job modify index
+  matches the server side version. Ignored if value of zero is passed. If a
+  non-zero value is passed, it ensures that the job is being updated from a
+  known state.
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
diff --git a/content/nomad/v1.11.x/content/commands/job/scaling-events.mdx b/content/nomad/v1.11.x/content/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..b41324df64
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'nomad job scaling-events command reference'
+description: |
+  The `nomad job scaling-events` command displays scaling events for the specified job.
+---
+
+# `nomad job scaling-events` command reference
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/start.mdx b/content/nomad/v1.11.x/content/commands/job/start.mdx
new file mode 100644
index 0000000000..b3d9e307fa
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/start.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'nomad job start command reference'
+description: |
+  The nomad job start command starts the latest version of an existing job
+  with a status of Stopped.
+---
+
+# nomad job start command reference
+
+Use the `nomad job start` command to start the latest version of an existing job
+with a status of Stopped. Refer to [Job statuses] for status explanations.
+
+## Usage
+
+```shell-session
+nomad job start [options] <job_id>
+```
+
+The `nomad job start` command requires the job ID. Nomad creates new version of
+the job based on its most recent version. This command fails if the job is not
+registered or not currently stopped.
+
+When Nomad uses ACLs, the `nomad job start` command requires a token with one of
+the following capabilities based on the specific scenario:
+
+- The `submit-job`capability for the job's namespace
+
+## Options
+
+- `-detach`: Return immediately instead of monitoring. Nomad outputs a new
+  evaluation ID, which you can use to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Start a previously stopped job.
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+example  service  50        dead (stopped)  2025-02-11T15:33:27-05:00
+
+$ nomad job start example
+==> 2025-02-11T15:34:48-05:00: Monitoring evaluation "8b715538"
+    2025-02-11T15:34:48-05:00: Evaluation triggered by job "example"
+    2025-02-11T15:34:49-05:00: Evaluation within deployment: "866ca498"
+    2025-02-11T15:34:49-05:00: Allocation "4d050576" created: node "8e17fa4d", group "echo"
+    2025-02-11T15:34:49-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2025-02-11T15:34:49-05:00: Evaluation "8b715538" finished with status "complete"
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[run]: /nomad/commands/job/run
+[Job statuses]: /nomad/docs/concepts/job#job-statuses
diff --git a/content/nomad/v1.11.x/content/commands/job/status.mdx b/content/nomad/v1.11.x/content/commands/job/status.mdx
new file mode 100644
index 0000000000..60579c2b07
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/status.mdx
@@ -0,0 +1,267 @@
+---
+layout: docs
+page_title: 'nomad job status command reference'
+description: |
+  The `nomad job status` command displays information and status for the specified job.
+---
+
+# `nomad job status` command reference
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. Alloc status also shows allocation
+modification time in addition to create time. When the `-verbose` flag is not set,
+allocation creation and modify times are shown in a shortened relative time format
+like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+@include 'job-status-map.mdx'
+
+## Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-json`: Output the job status in JSON format.
+
+- `-t`: Format and display the job status using a Go template.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+- `-ui`: Open the job status page in the browser.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/stop.mdx b/content/nomad/v1.11.x/content/commands/job/stop.mdx
new file mode 100644
index 0000000000..a3bd91234d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/stop.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad job stop command reference'
+description: |
+  The `nomad job stop` command stops a running job and signals the scheduler
+  to cancel all of the job's running allocations.
+---
+
+# `nomad job stop` command reference
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[eval status]: /nomad/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.11.x/content/commands/job/tag/apply.mdx b/content/nomad/v1.11.x/content/commands/job/tag/apply.mdx
new file mode 100644
index 0000000000..e475669a41
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/tag/apply.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad job tag apply command reference'
+description: |
+  The `nomad job tag apply` command saves a job version tag.
+---
+
+# `nomad job tag apply` command reference
+
+Use `job tag apply` to create or modify a version tag.
+
+@include 'version/tag-reason.mdx'
+
+## Usage
+
+```plaintext
+nomad job tag apply [options] <job_id>
+```
+
+## Options
+
+- `name`: Specifies the name of the tag. Must be unique per job.
+- `description`: If set, specifies a description for the tag.
+- `version`: If set, specifies the version of the job to tag. If not provided,
+  Nomad tags the latest version of the job.
+
+## Examples
+
+This example tags the latest version of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -name "golden-version" \
+		-description "The version we can roll back to." \
+    hello-world
+```
+
+This example tags version zero of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -version 0 \
+      -name "golden-version" \
+      hello-world
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/tag/index.mdx b/content/nomad/v1.11.x/content/commands/job/tag/index.mdx
new file mode 100644
index 0000000000..c7e3a7eca0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/tag/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'nomad job tag command reference'
+description: |
+  The `nomad job tag` command manages versions. The `nomad job tag apply` command saves a job version tag, and the `nomad job tag unset` command removes a job version tag.
+---
+
+# `nomad job tag` command reference
+
+Use the `job tag` command to manage tags for job versions.
+
+@include 'version/tag-reason.mdx'
+
+## Usage
+
+```plaintext
+nomad job tag <subcommand> [options] [args]
+```
+
+`job tag` has the following subcommands:
+
+- [`job tag apply`](/nomad/commands/job/tag/apply): Save a job version tag.
+- [`job tag unset`](/nomad/commands/job/tag/apply): Remove a tag from a job version.
diff --git a/content/nomad/v1.11.x/content/commands/job/tag/unset.mdx b/content/nomad/v1.11.x/content/commands/job/tag/unset.mdx
new file mode 100644
index 0000000000..1d3269b0c9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/tag/unset.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad job tag unset command reference'
+description: |
+  The `nomad job tag unset` command removes a job version tag.
+---
+
+# `nomad job tag unset` command reference
+
+Use `nomad job tag unset` to delete a tag from a version. This command requires
+a job name and a tag name.
+
+## Usage
+
+```plaintext
+nomad job tag unset [options] <job_id>
+```
+
+## Options
+
+- `name`: Specifies the name of the tag to remove from the job version.
+
+## Examples
+
+This example removes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ nomad job tag unset -name "golden-version" hello-world
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/job/validate.mdx b/content/nomad/v1.11.x/content/commands/job/validate.mdx
new file mode 100644
index 0000000000..e9c23ef3f8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/job/validate.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad job validate command reference'
+description: >
+  The `nomad job validate` command checks a job specification for syntax
+  errors and validation problems.
+---
+
+# `nomad job validate` command reference
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.11.x/content/commands/license/get.mdx b/content/nomad/v1.11.x/content/commands/license/get.mdx
new file mode 100644
index 0000000000..94c4130327
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/license/get.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: 'nomad license get command reference'
+description: |
+  The `nomad license get` command fetches the Nomad Enterprise license from the Nomad server.
+---
+
+# `nomad license get` command reference
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+<EnterpriseAlert />
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/license/index.mdx b/content/nomad/v1.11.x/content/commands/license/index.mdx
new file mode 100644
index 0000000000..3c3138e3f7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'nomad license command reference'
+description: |
+  The `nomad license` command gets or inspects a Nomad Enterprise license.
+---
+
+# `nomad license` command reference
+
+The `license` commands can be used to retrieve license information from a
+server, or inspect and validate a license.
+
+<EnterpriseAlert/>
+
+## Usage
+
+```plaintext
+nomad license <subcommand> [options]
+```
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.11.x/content/commands/license/inspect.mdx b/content/nomad/v1.11.x/content/commands/license/inspect.mdx
new file mode 100644
index 0000000000..b6bc5a4a88
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/license/inspect.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad license inspect command reference'
+description: |
+  The `nomad license inspect` command inspects a Nomad Enterprise license to see if it is valid with the installed Nomad binary.
+---
+
+# `nomad license inspect` command reference
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+<EnterpriseAlert />
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.11.x/content/commands/login.mdx b/content/nomad/v1.11.x/content/commands/login.mdx
new file mode 100644
index 0000000000..d8721a5ae5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/login.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad login command reference'
+description: |
+  The `nomad login` command uses OpenID Connect (OIDC) to authenticate a user with a single sign-on (SSO) provider. Nomad creates an access control list (ACL) token after successful authentication.
+---
+
+# `nomad login` command reference
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+
+$ export NOMAD_TOKEN=a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+$ nomad ...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/monitor/export.mdx b/content/nomad/v1.11.x/content/commands/monitor/export.mdx
new file mode 100644
index 0000000000..42feb818e8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/monitor/export.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'nomad monitor export command reference'
+description: |
+  The `nomad monitor export` command returns logs written to disk or journald by a nomad agent.
+---
+
+# `nomad monitor export` command reference
+
+The `nomad monitor export` command returns logs written to disk or journald by a nomad agent.
+
+## Usage
+
+```plaintext
+nomad monitor export [options]
+```
+
+Use the `nomad monitor export` command to export an agent's historic data
+from journald or its Nomad log file. If exporting journald logs, you must
+pass `-service-name` with the name of the systemd unit to query.
+The `-logs-since` and `-follow` options are only valid for journald queries.
+You may pass a duration string to the `-logs-since` option to override the
+default 72h duration. Nomad will accept the following time units in the
+`-logs-since` duration string: "ns", "us" (or "µs"), "ms", "s", "m", "h".
+The `-follow=true` option causes the agent to continue to stream logs until
+interrupted or until the remote agent quits. Nomad only supports journald
+queries on Linux.
+
+If you do not use Linux or you do not run Nomad as a systemd unit, pass the
+`-on-disk=true` option to export the entirety of a given agent's nomad log file.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given, the Nomad server from the `-address` flag is used.
+
+- `-server-id`: Specifies the Nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-service-name`: Specifies the the name of the systemd unit for export.
+  Do not use with `-on-disk`. Must include 'nomad' and conform to systemd
+  naming conventions. You may provide the full systemd file name
+  or omit the suffix. If your service name includes a '.', you must include
+  a valid suffix (e.g. nomad.client.service).
+  
+- `-logs-since`: Duration used to determine how far back to return logs from
+  journald. Ignored if used with `-on-disk` and defaults to `72h` if  not set.
+
+- `-follow`: Boolean that, if true, continues streaming journald logs until
+  interrupted. Do not use with `-on-disk`
+  
+- `-on-disk`: Boolean that, if true, returns the contents of the Nomad log file
+  defined in the agent config.
+
+## Examples
+
+This example returns journald log entries with a specific node ID and service name.
+
+```shell-session
+$ nomad monitor export -node-id=$(nomad node status --quiet) -service-name="nomad"
+Jun 04 20:09:29 nomad-client01 systemd[1]: Starting Nomad...
+Subject: A start job for unit nomad_client.service has begun execution
+```
+
+This example returns the contents of the nomad log file for a specific server.
+
+```shell-session
+$ nomad monitor export -server-id=a57b2adb-1a30-2dda-8df0-25abb0881952 -on-disk=true
+2025-06-20T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2025-06-20T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/monitor/index.mdx b/content/nomad/v1.11.x/content/commands/monitor/index.mdx
new file mode 100644
index 0000000000..4f1f6d1884
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/monitor/index.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'nomad monitor command reference'
+description: |
+  The `nomad monitor` command streams log messages for a given agent. Configure log level, log output, node ID, and server ID.
+---
+
+# `nomad monitor` command reference
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/namespace/apply.mdx b/content/nomad/v1.11.x/content/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..905b771993
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/apply.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad namespace apply command reference'
+description: |
+  The `nomad namespace apply` command creates or updates a Nomad namespace.
+---
+
+# `nomad namespace apply` command reference
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/docs/govern/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers   = ["docker", "exec"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/namespace/delete.mdx b/content/nomad/v1.11.x/content/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..26b13a8b89
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad namespace delete command reference'
+description: |
+  The `nomad namespace delete` command deletes a namespace.
+---
+
+# `nomad namespace delete` command reference
+
+The `namespace delete` command is used delete a namespace.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs or allocations,
+existing CSI volumes or variables attached to it, or quotas associated with it.
+In federated clusters, you cannot delete a namespace that has any of the above
+in any of the federated regions.
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/namespace/index.mdx b/content/nomad/v1.11.x/content/commands/namespace/index.mdx
new file mode 100644
index 0000000000..323d972b17
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad namespace command reference'
+description: |
+  The nomad namespace reference command interact with namespaces. Create, inspect, and delete a namespace. Display status information and list namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+Visit [Create and use namespaces](/nomad/docs/govern/namespaces) for more information.
+
+## Usage
+
+```plaintext
+nomad namespace <subcommand> [options]
+```
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/commands/namespace/list 'List available namespaces'
+[status]: /nomad/commands/namespace/status "Display a namespace's status"
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.11.x/content/commands/namespace/inspect.mdx b/content/nomad/v1.11.x/content/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f3217f9952
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/inspect.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad namespace inspect command reference'
+description: >
+  The `nomad namespace inspect` command displays raw information about a
+  particular namespace.
+---
+
+# `nomad namespace inspect` command reference
+
+The `namespace inspect` command is used to view raw information about a
+particular namespace.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/namespace/list.mdx b/content/nomad/v1.11.x/content/commands/namespace/list.mdx
new file mode 100644
index 0000000000..4676610f90
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/list.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad namespace list command reference'
+description: |
+  The `nomad namespace list` command displays a list of namespaces.
+---
+
+# `nomad namespace list` command reference
+
+The `namespace list` command is used list available namespaces.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/namespace/status.mdx b/content/nomad/v1.11.x/content/commands/namespace/status.mdx
new file mode 100644
index 0000000000..1dea1ba3c0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/namespace/status.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad namespace status command reference'
+description: >
+  The `nomad namespace status` command displays status information for the specified namespace.
+---
+
+# `nomad namespace status` command reference
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name                 = api-prod
+Description          = Prod API servers
+Quota                = prod
+EnabledDrivers       = docker,exec
+DisabledDrivers      = raw_exec
+EnabledNetworkModes  = bridge,cni/custom
+DisabledNetworkModes = host
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/apply.mdx b/content/nomad/v1.11.x/content/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..41b819391b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/apply.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'nomad node pool apply command reference'
+description: |
+  The `nomad node pool apply` command creates or updates a node pool.
+---
+
+# `nomad node pool apply` command reference
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## Options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  node_pool_identity = "720h"
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/delete.mdx b/content/nomad/v1.11.x/content/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..51772e4b28
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool delete command reference'
+description: |
+  The `nomad node pool delete` command deletes the specified node pool.
+---
+
+# `nomad node pool delete` command reference
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/index.mdx b/content/nomad/v1.11.x/content/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..970d7c64f1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad node pool command reference'
+description: |
+  The `nomad node pool` command interact with node pools. Generate an example node pool specification. Create, update, and delete a node pool. Display a list of node pools and information about a specific node pool. Display jobs and nodes in a node pool.
+---
+
+# `nomad node pool` command reference
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+```plaintext
+nomad node pool <subcommand> [options]
+```
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool init`][init] - Generate an example node pool specification.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/commands/node-pool/apply
+[delete]: /nomad/commands/node-pool/delete
+[info]: /nomad/commands/node-pool/info
+[init]: /nomad/commands/node-pool/init
+[jobs]: /nomad/commands/node-pool/jobs
+[list]: /nomad/commands/node-pool/list
+[nodes]: /nomad/commands/node-pool/nodes
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/info.mdx b/content/nomad/v1.11.x/content/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..e3c137e6b0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/info.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad node pool info command reference'
+description: |
+  The `nomad node pool info` command displays information about a node pool.
+---
+
+# `nomad node pool info` command reference
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## Options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name              = prod
+Description       = Node pool for production workloads.
+Node Identity TTL = "24h0m0s"
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "NodeIdentityTTL": "24h0m0s",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/init.mdx b/content/nomad/v1.11.x/content/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..674bd3e742
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool init command reference'
+description: |
+  The `nomad node pool init` command generates an example node pool specification.
+---
+
+# `nomad node pool init` command reference
+
+The `nomad node pool init` command creates an example node pool specification
+file that you can use as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/jobs.mdx b/content/nomad/v1.11.x/content/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..603d070abe
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'nomad node pool jobs command reference'
+description: |
+  The `nomad node pool jobs` command displays jobs in the specified node pool.
+---
+
+# `nomad node pool jobs` command reference
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/list.mdx b/content/nomad/v1.11.x/content/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..0400490886
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'nomad node pool list command reference'
+description: |
+  The `nomad node pool list` command displays all node pools or those matching a filter expression.
+---
+
+# `nomad node pool list` command reference
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options]
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.11.x/content/commands/node-pool/nodes.mdx b/content/nomad/v1.11.x/content/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..beddbbcc05
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad node pool nodes command reference'
+description: |
+  The `nomad node pool nodes` command displays nodes in the specified node pool.
+---
+
+# `nomad node pool nodes` command reference
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.11.x/content/commands/node/config.mdx b/content/nomad/v1.11.x/content/commands/node/config.mdx
new file mode 100644
index 0000000000..9dfb2a1b46
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad node config command reference'
+description: |
+  The `nomad node config` command displays configuration details for the specified client. You can also update the client's server list with this command.
+---
+
+# `nomad node config` command reference
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.11.x/content/commands/node/drain.mdx b/content/nomad/v1.11.x/content/commands/node/drain.mdx
new file mode 100644
index 0000000000..41cd165659
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'nomad node drain command reference'
+description: |
+  The `nomad node drain` command turns on or turns off a node's drain mode. Drain mode prevents any new tasks from being allocated to the node and beings migrating all existing allocations to other nodes.
+---
+
+# `nomad node drain` command reference
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[eligibility]: /nomad/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/commands/node/status
+[workload migration guide]: /nomad/docs/manage/migrate-workloads
+[internals-csi]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.11.x/content/commands/node/eligibility.mdx b/content/nomad/v1.11.x/content/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aa00a4b356
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/eligibility.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad node eligibility command reference'
+description: >
+  The `nomad node eligibility` command turns on or turns off a node's eligibility to receive placements and run new allocations.
+---
+
+# `nomad node eligibility` command reference
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[drain]: /nomad/commands/node/drain
diff --git a/content/nomad/v1.11.x/content/commands/node/identity/get.mdx b/content/nomad/v1.11.x/content/commands/node/identity/get.mdx
new file mode 100644
index 0000000000..1b35f7db77
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/identity/get.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'nomad node identity get command reference'
+description: |
+  The `nomad node identity get` command returns the identity claims for a specific node.
+---
+
+# `nomad node identity get` command reference
+
+Get the identity claims for a node. This command only applies to client agents.
+
+If ACLs are enabled, this command requires a token with the `node:read` capability.
+
+## Usage
+
+```plaintext
+nomad node identity get [options] <node_id>
+```
+
+## Examples
+
+Get the identity claims of a specific node.
+
+```shell-session
+$ nomad node identity renew da86421c-7de9-85e4-2f50-3b2bf95102c1
+Claim Key              Claim Value
+aud                    nomadproject.io
+exp                    2025-09-23T10:37:39+01:00
+iat                    2025-09-22T10:37:39+01:00
+jti                    6b3ccaac-9e23-088f-405b-23797ca64c1a
+nbf                    2025-09-22T10:37:39+01:00
+sub                    node:global:default:da86421c-7de9-85e4-2f50-3b2bf95102c1:default
+nomad_node_datacenter  dc1
+nomad_node_id          da86421c-7de9-85e4-2f50-3b2bf95102c1
+nomad_node_pool        default
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node/identity/index.mdx b/content/nomad/v1.11.x/content/commands/node/identity/index.mdx
new file mode 100644
index 0000000000..de975e2b66
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/identity/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'nomad node identity command reference'
+description: |
+  The `nomad node identity` commands allow for interaction with a specific node's identity.
+---
+
+# `nomad node identity` command reference
+
+Use the `node identity` command to interact with a specific node's identity.
+
+## Usage
+
+```plaintext
+nomad node identity <subcommand> [options]
+```
+
+Interact with a node's identity. All commands interact directly with a client and require setting
+the target node via its 36-character ID.
+
+Refer to the individual subcommand help for detailed usage information.
+
+Subcommands:
+
+ - [`renew`][renew] - Force a node to renew its identity
+
+[renew]: /nomad/commands/node/identity/renew
diff --git a/content/nomad/v1.11.x/content/commands/node/identity/renew.mdx b/content/nomad/v1.11.x/content/commands/node/identity/renew.mdx
new file mode 100644
index 0000000000..c4b4fcd6dc
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/identity/renew.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad node identity renew command reference'
+description: |
+  The `nomad node identity renew` command instructs a node to renew its identity.
+---
+
+# `nomad node identity renew` command reference
+
+Instruct a node to renew its identity at the next heartbeat. This command only applies to client
+agents.
+
+If ACLs are enabled, this command requires a token with the `node:write` capability.
+
+## Usage
+
+```plaintext
+nomad node identity renew [options] <node_id>
+```
+
+## Examples
+
+Instruct a specific node to renew its identity.
+
+```shell-session
+$ nomad node identity renew da86421c-7de9-85e4-2f50-3b2bf95102c1
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node/index.mdx b/content/nomad/v1.11.x/content/commands/node/index.mdx
new file mode 100644
index 0000000000..063f3cbc3f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node command reference'
+description: |
+  The nomad node reference command interacts with nodes. View or modify client configuration. Toggle scheduling eligibility and node drain mode. Display metadata and status information.
+---
+
+# `nomad node` command reference
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+```plaintext
+nomad node <subcommand> [options]
+```
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.11.x/content/commands/node/intro/create.mdx b/content/nomad/v1.11.x/content/commands/node/intro/create.mdx
new file mode 100644
index 0000000000..91a22aa61f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/intro/create.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad node intro create command reference'
+description: |
+  The `nomad node intro create` command creates a new node introduction token.
+---
+
+# `nomad node intro create` command reference
+
+Use the `nomad node intro create` command to generates a new node introduction
+token. The Nomad cluster uses this token to authenticate a new Nomad client
+node. When possible, we recommend specifying the optional `-node-name` flag, so
+that the token is scoped to a specific node.
+
+If ACLs are enabled, this command requires a token with the `node:write` capability.
+
+## Usage
+
+```plaintext
+nomad node intro create [options]
+```
+
+## Options
+
+- `-node-name`: The name of the node to which the introduction token is scoped. If not
+  specified, the value is left empty.
+
+- `-node-pool`: The node pool to which the introduction token is scoped. If not specified, the
+  value `default` is used.
+
+- `-ttl`: The TTL to apply to the introduction token. If not specified, the server configured
+  default value is used.
+
+- `-json`: Output the response object in JSON format.
+
+- `-t`: Format and display the response object using a Go template.
+
+## Examples
+
+Create a node introduction token with a specific node name, node pool, and TTL.
+
+```shell-session
+$ nomad node intro create -node-name=node-338ef6e9 -node-pool=platform -ttl=15m
+
+Successfully generated client introduction token:
+
+eyJhbGciOiJSUzI1NiIsImtpZCI6IjFlMGJhMmM3LWE5ODktNzI2Ni1kZDdlLWMyYzBkZmU3OTg4OSIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJleHAiOjE3NTUwNzE2NDgsImlhdCI6MTc1NTA3MDc0OCwianRpIjoiYWVmMGE3NzUtNzQ0MS1jNjA2LTIyY2UtNGRhZGY4YzExYzlmIiwibmJmIjoxNzU1MDcwNzQ4LCJub21hZF9ub2RlX25hbWUiOiJub2RlLTMzOGVmNmU5Iiwibm9tYWRfbm9kZV9wb29sIjoicGxhdGZvcm0iLCJzdWIiOiJub2RlLWludHJvZHVjdGlvbjpnbG9iYWw6cGxhdGZvcm06bm9kZS0zMzhlZjZlOTpkZWZhdWx0In0.nCyqdlqStkjoX64p-AN0DA90eIbwVj9A-cYRtabEdTmqkocz-31YY9MlCKv0v6oU4AYHwUF-kBXG7LWYQgk2RKgWh-KttjfT1kJaS0k9jfiyVFxrLuz2F_KZO8kBzZFGS4bQw6nw0-6uR0tkkZvKVwrq6L3hyFUWpgB-gI2BidIZz7Y02RNtcpStjv0e-1DVyzFxInIuTnX-Z2fRAZz7w5e1nMtDFpnZgPM3nrjg2ZAKKiX9GiZT9IPip_KRsqdAN5TWkHlNQ7WmdzrIBZNe1IX15JWC7wSyCJn-n-FSSRc71X1P2ZYaOUzmJiGr-x7M95jDZD6CGDykfsD9pFQR_A
+```
+
+Create a node introduction token with a specific node name, node pool, and TTL with the output in
+JSON format.
+
+```shell-session
+$ nomad node intro create -node-name=node-338ef6e9 -node-pool=platform -ttl=15m -json
+{
+    "JWT": "eyJhbGciOiJSUzI1NiIsImtpZCI6IjFlMGJhMmM3LWE5ODktNzI2Ni1kZDdlLWMyYzBkZmU3OTg4OSIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJub21hZHByb2plY3QuaW8iLCJleHAiOjE3NTUwNzE3MzUsImlhdCI6MTc1NTA3MDgzNSwianRpIjoiZTYxYjhlYTUtZjkyYy05YmJmLWU0OWQtYmMxNTg2NDIyNjhhIiwibmJmIjoxNzU1MDcwODM1LCJub21hZF9ub2RlX25hbWUiOiJub2RlLTMzOGVmNmU5Iiwibm9tYWRfbm9kZV9wb29sIjoicGxhdGZvcm0iLCJzdWIiOiJub2RlLWludHJvZHVjdGlvbjpnbG9iYWw6cGxhdGZvcm06bm9kZS0zMzhlZjZlOTpkZWZhdWx0In0.Rij4lcI-vBT6C60oUmR_Qdx3LY6vYh-3OwLRjW-_cAZrl1OaoTUHwfinaUDZza4fY8UZo48ZXjcEw_9sHBYMnX9qByYbdtJUIsBCUn_VAIkMvZFLY4nR5zhB4XotQARqPNY0WENlEb0LhtQcIeFDPJOuDrDCrUk6QqKX5W-ZwFNLZe269LtQjlZDZT-AiNaJfhd8skNipdDW1XhusZucn3nIFQ-iQHqwb7zFB1vIxiNzJqPq_K2SYXIv41uEfWlcp9FTr_1XYQKfukzVg-GQq0nV74VVZSIh5TZLrEIB69GGoOy0t3CY7yDBfrqyKyw4B1fNPEz5o7G4VzoihmbGbA"
+}
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/node/intro/index.mdx b/content/nomad/v1.11.x/content/commands/node/intro/index.mdx
new file mode 100644
index 0000000000..7ddf979319
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/intro/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'nomad node intro command reference'
+description: |
+  The `nomad node intro` commands allow for the creation of node introduction tokens.
+---
+
+# nomad node intro reference
+
+Use the `nomad node intro` command to manage node introduction tokens. The Nomad
+cluster uses these tokens to authenticate new Nomad clients.
+
+## Usage
+
+```plaintext
+nomad node intro <subcommand> [options]
+```
+
+This command groups subcommands for managing node introduction tokens. The Nomad
+cluster uses these tokens to authenticate new Nomad clients.
+
+Refer to the individual subcommand help for detailed usage information.
+
+Subcommands:
+
+ - [`create`][create] - Generate a new node introduction token
+
+[create]: /nomad/commands/node/intro/create
diff --git a/content/nomad/v1.11.x/content/commands/node/meta/apply.mdx b/content/nomad/v1.11.x/content/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..774f85356c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad node meta apply command reference'
+description: |
+  The `nomad node meta apply` command updates node metadata on client agents.
+---
+
+# `nomad node meta apply` command reference
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.11.x/content/commands/node/meta/index.mdx b/content/nomad/v1.11.x/content/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..3a05646727
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/meta/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad node meta command reference'
+description: |
+  The nomad node meta commands read and update node metadata.
+---
+
+# nomad node meta reference
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+```plaintext
+nomad node meta <subcommand> [options]
+```
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[apply]: /nomad/commands/node/meta/apply
+[read]: /nomad/commands/node/meta/read
diff --git a/content/nomad/v1.11.x/content/commands/node/meta/read.mdx b/content/nomad/v1.11.x/content/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..1f7edfb5ad
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad node meta read command reference'
+description: |
+  The nomad node meta read command displays metadata on the specified node.
+---
+
+# nomad node meta read reference
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[api]: /nomad/api-docs/client#update-dynamic-node-metadata
diff --git a/content/nomad/v1.11.x/content/commands/node/status.mdx b/content/nomad/v1.11.x/content/commands/node/status.mdx
new file mode 100644
index 0000000000..1160fe024a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/node/status.mdx
@@ -0,0 +1,415 @@
+---
+layout: docs
+page_title: 'nomad node status command reference'
+description: |
+  The `nomad node status` command displays status information about registered client nodes.
+---
+
+# `nomad node status` command reference
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+- `-ui` : Open the node status page in the browser
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view with verbose:
+
+```shell-session
+$ nomad node status -verbose
+ID        Node Pool  DC   Name   Class   Address   Version  Drain  Eligibility  Status
+4d2ba53b  default    dc1  node1  <none>  127.0.0.1  1.10.1  false  eligible     ready
+34dfba32  dev        dc1  node2  <none>  127.0.0.1  1.10.1  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Address   Version  Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  127.0.0.1  1.10.1  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  127.0.0.1  1.10.1  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk              Alloc Count
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB     1/50
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     5/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     5/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk               Alloc Count
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB     0/50
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/api.mdx b/content/nomad/v1.11.x/content/commands/operator/api.mdx
new file mode 100644
index 0000000000..5ee5ef5d7a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/api.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'nomad operator api command reference'
+description: |
+  The `nomad operator api` command is a cURL-like utility command for accessing Nomad's HTTP API.
+---
+
+# `nomad operator api` command reference
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.11.x/content/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.11.x/content/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..4625255f40
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot get-config command reference'
+description: |
+  The `nomad operator autopilot get-config` command displays the current Autopilot configuration.
+---
+
+# `nomad operator autopilot get-config` command reference
+
+The Autopilot operator command is used to view the current Autopilot
+settings, which you configure in the [`autopilot` block of the Agent configuration][autopilot-config].
+
+Refer to the [Autopilot Guide][autopilot-guide] for more information about
+Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Example
+
+This example returns the configuration information.
+
+```shell-session
+$ nomad operator autopilot get-config
+
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+Refer to the [`autopilot` block of the Agent
+configuration][autopilot-config] for explanations of the
+returned configuration settings.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[autopilot-guide]: /nomad/docs/manage/autopilot
+[autopilot-config]: /nomad/docs/configuration/autopilot
diff --git a/content/nomad/v1.11.x/content/commands/operator/autopilot/health.mdx b/content/nomad/v1.11.x/content/commands/operator/autopilot/health.mdx
new file mode 100644
index 0000000000..ab837b870a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/autopilot/health.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot health command reference'
+description: |
+  The `nomad operator autopilot health` command displays the current Autopilot internal health.
+---
+
+# `nomad operator autopilot health` command reference
+
+The Autopilot operator command is used to view the current Autopilot state.
+Refer to the [Autopilot Guide][autopilot-guide] for more information about
+Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot health [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Options
+
+- `-json`: Output the Autopilot health in unformatted JSON.
+
+The output will return like below, read about the output of the command in the [API docs][api-docs].
+
+```shell-session
+$ nomad operator autopilot health
+Healthy: true
+FailureTolerance: 0
+Leader: e349749b-3303-3ddf-959c-b5885a0e1f6e
+Voters:
+        e349749b-3303-3ddf-959c-b5885a0e1f6e
+Servers:
+ID                                    Name      Address         SerfStatus  Version   Leader  Voter  Healthy  LastContact  LastTerm  LastIndex  StableSince
+e349749b-3303-3ddf-959c-b5885a0e1f6e  node1     127.0.0.1:4647  alive       1.7.5     true    true   true     0s           2         14         2024-02-20 16:40:55 +0000 UTC
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[autopilot-guide]: /nomad/docs/manage/autopilot
+[api-docs]: /nomad/api-docs/operator/autopilot#read-autopilot-configuration
diff --git a/content/nomad/v1.11.x/content/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.11.x/content/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..79ad24385c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot set-config command reference'
+description: |
+  The `nomad operator autopilot set-config` command modifies the current Autopilot configuration.
+---
+
+# `nomad operator autopilot set-config` command reference
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. Refer to the [Autopilot Guide][autopilot-guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` -  <EnterpriseAlert inline/> Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- <EnterpriseAlert inline/> Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - <EnterpriseAlert inline/> Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+## Example
+
+This example sets `cleanup-dead-servers` to `false`.
+
+```shell-session
+$ nomad operator autopilot set-config -cleanup-dead-servers=false
+Configuration updated!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot-guide]: /nomad/docs/manage/autopilot
diff --git a/content/nomad/v1.11.x/content/commands/operator/client-state.mdx b/content/nomad/v1.11.x/content/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..81d89354c3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'nomad operator client-state command reference'
+description: >
+  The `nomad operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# `nomad operator client-state` command reference
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.11.x/content/commands/operator/debug.mdx b/content/nomad/v1.11.x/content/commands/operator/debug.mdx
new file mode 100644
index 0000000000..5be4a8b7d5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/debug.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: 'nomad operator debug command reference'
+description: |
+  The `nomad operator debug` command builds an archive containing Nomad cluster configuration and state information, Nomad server and client node logs, and pprof profiles from the selected servers and client nodes.
+---
+
+# `nomad operator debug` command reference
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## Options
+
+- `-duration=5m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `5m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=TRACE`: The log level to monitor. Defaults to `TRACE`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-log-file-export`: Include agents' Nomad logfiles in the debug capture.
+  The historical log export monitor runs concurrently with the log monitor
+  and ignores the `-log-level` and `-log-include-location` flags used to
+  configure that monitor. Nomad will return an error if the agent does not
+  have file logging configured. Cannot be used with `-log-lookback`.
+
+- `-log-lookback`: Include historical journald logs in the debug capture. The
+  journald export monitor runs concurrently with the log monitor and ignores
+  the `-log-level` and `-log-include-location` flags passed to that monitor.
+  This flag is only available on Linux systems using systemd, see the
+  `-log-file-export` flag to retrieve historical logs from non-Linux systems,
+  or those without systemd. Cannot be used with `-log-file-export`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..bf07092f64
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring generate command reference'
+description: >
+  The `nomad operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# nomad operator gossip keyring generate reference
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..3632f47d7a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring install command reference'
+description: |
+  The `nomad operator gossip keyring install` command installs a new gossip encryption key.
+---
+
+# `nomad operator gossip keyring install` command reference
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..93e136cd32
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring list command reference'
+description: |
+  The `nomad operator gossip keyring list` command displays all gossip keys currently in use within the cluster.
+---
+
+# `nomad operator gossip keyring list` command reference
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..295fac279f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring remove command reference'
+description: |
+  The `nomad operator gossip keyring remove` command removes the specified, non-primary gossip encryption key from the cluster.
+---
+
+# `nomad operator gossip keyring remove` command reference
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..1e91f3dff9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring use command reference'
+description: |
+  The `nomad operator gossip keyring use` command changes the encryption key that Nomad uses for gossip.
+---
+
+# `nomad operator gossip keyring use` command reference
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/index.mdx b/content/nomad/v1.11.x/content/commands/operator/index.mdx
new file mode 100644
index 0000000000..ee7decb5d2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/index.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: 'nomad operator command reference'
+description: |
+  The `nomad operator` command provides cluster-level tools for Nomad operators.
+---
+
+# `nomad operator` command reference
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator <subcommand> <subcommand> [options]
+```
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/docs/manage/outage-recovery
+[remove]: /nomad/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.11.x/content/commands/operator/metrics.mdx b/content/nomad/v1.11.x/content/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..b5ddf90312
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'nomad operator metrics command reference'
+description: |-
+  The `nomad operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# `nomad operator metrics` command reference
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/info.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..10ee200c77
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad operator raft info command reference'
+description: |
+  The `nomad operator raft info` command displays summary information about the Raft logs persisted in the Nomad data directory.
+---
+
+# `nomad operator raft info` command reference
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/list-peers.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..3a3b9b3e87
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad operator raft list-peers command reference'
+description: |
+  The `nomad operator raft list-peers` command displays the current Raft peer configuration.
+---
+
+# `nomad operator raft list-peers` command reference
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/logs.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..a5cc23391b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad operator raft logs command reference'
+description: |
+  The `nomad operator raft logs` command displays the log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft logs` command reference
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..144148bc41
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad operator raft remove-peer command reference'
+description: |
+  The `nomad operator raft remove-peer` command removes a Nomad server from the Raft configuration.
+---
+
+# `nomad operator raft remove-peer` command reference
+
+Remove the Nomad server with peer ID from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`nomad server force-leave`]: /nomad/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/state.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..73f11acf03
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator raft state command reference'
+description: |
+  The `nomad operator raft state` command displays Raft server state obtained by replaying Raft log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft state` command reference
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.11.x/content/commands/operator/raft/transfer-leadership.mdx b/content/nomad/v1.11.x/content/commands/operator/raft/transfer-leadership.mdx
new file mode 100644
index 0000000000..57052fcd97
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/raft/transfer-leadership.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad operator raft transfer-leadership command reference'
+description: |
+  The `nomad operator raft transfer-leadership` command transfers leadership to a specific Nomad server.
+---
+
+# `nomad operator raft transfer-leadership` command reference
+
+Transfer leadership from the current leader to the given server member.
+
+While performing a [rolling upgrade][] of your Nomad cluster, it might be
+advisable to transfer leadership to a specific node in the cluster. For example,
+setting the leader to the first upgraded server in the cluster can prevent
+leadership churn as you upgrade the remaining server nodes.
+
+The target server's ID or address:port are required and can be obtained by
+running the [`nomad operator raft list-peers`][] command or by calling the
+[Read Raft Configuration][] API endpoint.
+
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator][] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft transfer-leadership [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## Options
+
+<Note>
+
+Provide either `-peer-address` or `-peer-id`, but not both.
+
+</Note>
+
+- `-peer-address`: Specifies the Raft **Address** of the target server as
+  provided in the output of the [`nomad operator raft list-peers`][] command or
+  the [Read Raft Configuration] API endpoint.
+
+- `-peer-id`: Specifies the Raft **ID** of the target server as provided in the
+  output of the [`nomad operator raft list-peers`][] command or the
+  [Read Raft Configuration] API endpoint.
+
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`nomad operator raft list-peers`]: /nomad/commands/operator/raft/list-peers 'Nomad operator raft list-peers command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[rolling upgrade]: /nomad/docs/upgrade#upgrade-process
+[Read Raft Configuration]: /nomad/api-docs/operator/raft#read-raft-configuration
diff --git a/content/nomad/v1.11.x/content/commands/operator/root/keyring-list.mdx b/content/nomad/v1.11.x/content/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..61af021dfd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring list command reference'
+description: |
+  The `nomad operator root keyring list` command displays encryption key metadata for installed keys. This command does not display sensitive key material.
+---
+
+# `nomad operator root keyring list` command reference
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.11.x/content/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..8b5fc9b71d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring remove command reference'
+description: |
+  The `nomad operator root keyring remove` command removes an unused encryption key from the cluster.
+---
+
+# `nomad operator root keyring remove` command reference
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+The `key ID` must be the UUID. Use the `-verbose` option with the
+[`nomad operator root keyring list`
+command](/nomad/commands/operator/root/keyring-list) to fetch the key
+UUID.
+
+## Options
+
+- `-force`: Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.11.x/content/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..ccd39a1d37
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring rotate command reference'
+description: |
+  The `nomad operator root keyring rotate` command rotates the encryption key by generating a new encryption key for all future variables.
+---
+
+# `nomad operator root keyring rotate` command reference
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.11.x/content/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.11.x/content/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..1ed7a39345
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler get-config command reference'
+description: |
+  The `nomad operator scheduler get-config` command displays the current scheduler configuration.
+---
+
+# `nomad operator scheduler get-config` command reference
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.11.x/content/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..eb30e02dcd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler set-config command reference'
+description: |
+  The `nomad operator scheduler set-config` command modifies the scheduler configuration. Set binpack or spread allocation. Enable or disable preemption for batch, service, sysbatch, and system jobs.
+---
+
+# `nomad operator scheduler set-config` command reference
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/agent.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..6b63d275f6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot agent command reference'
+description: |
+  The `nomad operator snapshot agent` command takes snapshots of the state of the Nomad servers and saves them locally or pushes them to an optional remote storage service.
+---
+
+# `nomad operator snapshot agent` command reference
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+<EnterpriseAlert />
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## Options
+
+### Snapshot
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure
+
+Note: Non-Solaris platforms only
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google
+
+- `-google-bucket`: The bucket to use.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..0b11a2b91f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot inspect command reference'
+description: |
+  The `nomad operator snapshot inspect` command displays information about a snapshot file stored on local disk.
+---
+
+# `nomad operator snapshot inspect` command reference
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/redact.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/redact.mdx
new file mode 100644
index 0000000000..bf7a4c0c83
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/redact.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot redact command reference'
+description: |
+ The `nomad operator snapshot redact` command removes key material from an existing snapshot file created by the `operator snapshot save` command so you can transmit a snapshot without exposing key material.
+---
+
+# `nomad operator snapshot redact` command reference
+
+The `operator snapshot redact` command removes key material from an existing
+snapshot file created by the `operator snapshot save` command, when using the
+AEAD keyring provider.
+
+This is useful for situations where you need to transmit a snapshot without
+exposing key material.
+
+<Warning>
+
+When using a [KMS keyring provider][], no cleartext key material is stored in
+snapshots and this command is not necessary. Note that this command requires
+loading the entire snapshot into memory locally and overwrites the existing
+snapshot.
+
+Snapshots made before Nomad 1.9.0 will not include the keyrings.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad operator snapshot redact <file>
+```
+
+
+[KMS keyring provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/restore.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..e099705531
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot restore command reference'
+description: |
+  The `nomad operator snapshot restore` command restores the specified Nomad snapshot.
+---
+
+# `nomad operator snapshot restore` command reference
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
+
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/save.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..30b6d178e0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/save.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot save command reference'
+description: |
+  The `nomad operator snapshot save` command saves an atomic, point-in-time snapshot of state of the Nomad servers, including jobs, nodes, allocations,periodic jobs, ACLs for outage recovery, and the keyring.
+---
+
+# `nomad operator snapshot save` command reference
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command includes Nomad's keyring in the snapshot. If you are not using a
+[KMS provider][] to secure the keyring, you should use the `-redact` flag to
+remove key material before transmitting the snapshot to HashiCorp Support.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## Options
+
+- `-redact`: The redact option will locally edit the snapshot to remove any
+  cleartext key material from the root keyring. Only the AEAD keyring provider
+  has cleartext key material in Raft. Note that this operation requires loading
+  the snapshot into memory locally.
+
+- `-stale`: The stale option defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/docs/manage/outage-recovery
+[KMS provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.11.x/content/commands/operator/snapshot/state.mdx b/content/nomad/v1.11.x/content/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..218e99960a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot state command reference'
+description: |
+  The `nomad operator snapshot state` command displays a JSON representation of a Raft snapshot.
+---
+
+# `nomad operator snapshot state` command reference
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.11.x/content/commands/operator/utilization.mdx b/content/nomad/v1.11.x/content/commands/operator/utilization.mdx
new file mode 100644
index 0000000000..30173507cb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/operator/utilization.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: nomad operator utilization command reference
+description: |-
+  The "operator utilization" generates utilization reporting bundles for Nomad Enterprise users.
+---
+
+# `nomad operator utilization` command reference
+
+The `operator utilization` command allows Nomad Enterprise users to generate
+utilization reporting bundles. If you have disabled [automated
+reporting](/nomad/docs/enterprise/license/utilization-reporting), use
+this command to manually generate the report and send it to HashiCorp. Nomad
+takes a new snapshot when there are no snapshots from the past twenty-four
+hours.
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+<EnterpriseAlert />
+
+## Options
+
+- `-message` `(string; "")` - Provide context about the conditions under which
+  the report was generated and submitted. This message is not included in the
+  utilization bundle but is included in the Nomad server logs.
+
+- `-output` `(string; "")` - Specifies the output path for the bundle. Defaults
+  to a time-based generated file name in the current working directory.
+
+- `-today-only` `(bool: false)` - Include snapshots from the previous 24 hours,
+  not historical snapshots.
+
+## Examples
+
+Create a utilization reporting bundle that includes all persisted historical
+snapshots and has the default bundle name
+(`nomad-utilization-<time_stamp>.json`).
+
+```shell-session
+$ nomad operator utilization
+Success! Utilization reporting bundle written to: nomad-utilization-2024-02-16T22-23-25Z.json
+```
+
+Create a utilization reporting bundle with a message about the bundle, and
+output the file at the specified path, `/utilization/reports/latest.json`.
+
+```shell-session
+$ nomad operator utilization \
+    -message="Change Control 654987" \
+    -output="/utilization/reports/latest.json"
+```
+
+**Example output**
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Success! Utilization reporting bundle written to: /utilization/reports/latest.json
+```
+
+</CodeBlockConfig>
+
+The message, `Change Control 654987`, is included in the _server log_, but not
+in the bundle.
+
+**Example entry in the server log**
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+[INFO]  reporting: reporting bundle generated: message="Change Control 654987"
+```
+
+</CodeBlockConfig>
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/plugin/index.mdx b/content/nomad/v1.11.x/content/commands/plugin/index.mdx
new file mode 100644
index 0000000000..dc8fe4507a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/plugin/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad plugin command reference'
+description: |
+  The `nomad plugin` command interacts with external plugins that a job can use, such as Container Storage Interface (CSI) plugins.
+---
+
+# `nomad plugin` command reference
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin <subcommand> [options]
+```
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.11.x/content/commands/plugin/status.mdx b/content/nomad/v1.11.x/content/commands/plugin/status.mdx
new file mode 100644
index 0000000000..2332d64382
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'nomad plugin status command reference'
+description: |
+  The `nomad plugin status` displays information and status for a specific plugin, plugins by type, or all plugins.
+---
+
+# `nomad plugin status` command reference
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.11.x/content/commands/quota/apply.mdx b/content/nomad/v1.11.x/content/commands/quota/apply.mdx
new file mode 100644
index 0000000000..2f576e34e2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/apply.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad quota apply command reference'
+description: |
+  The `nomad quota apply` command creates or updates a Nomad Enterprise quota specification.
+---
+
+# `nomad quota apply` command reference
+
+The `quota apply` command is used to create or update [quota specifications][].
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[quota specifications]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.11.x/content/commands/quota/delete.mdx b/content/nomad/v1.11.x/content/commands/quota/delete.mdx
new file mode 100644
index 0000000000..cd157b0123
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad quota delete command reference'
+description: |
+  The `nomad quota delete` command deletes an existing quota specification in Nomad Enterprise.
+---
+
+# `nomad quota delete` command reference
+
+The `quota delete` command is used to delete an existing quota specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/quota/index.mdx b/content/nomad/v1.11.x/content/commands/quota/index.mdx
new file mode 100644
index 0000000000..05c0679449
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad quota command reference'
+description: |
+  The `nomad quota` command interacts with Nomad Enterprise quota specifications. Generate an example specification. Create, update, delete, and inspect a quota specification. Display quota status and current usage. Retrieve a list of all quota specifications.
+---
+
+# `nomad quota` command reference
+
+The `quota` command is used to interact with quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota <subcommand> [options]
+```
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/commands/quota/apply
+[quotadelete]: /nomad/commands/quota/delete
+[quotainit]: /nomad/commands/quota/init
+[quotainspect]: /nomad/commands/quota/inspect
+[quotalist]: /nomad/commands/quota/list
+[quotastatus]: /nomad/commands/quota/status
diff --git a/content/nomad/v1.11.x/content/commands/quota/init.mdx b/content/nomad/v1.11.x/content/commands/quota/init.mdx
new file mode 100644
index 0000000000..d8fcb02c00
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'nomad quota init command reference'
+description: |
+  The `nomad quota init` command generates an example quota specification that you can customize for your Nomad Enterprise quota specification.
+---
+
+# `nomad quota init` command reference
+
+The `quota init` command is used to create an example [quota specification][]
+file that can be used as a starting point to customize further.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
+
+[quota specification]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.11.x/content/commands/quota/inspect.mdx b/content/nomad/v1.11.x/content/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..64fdafb22f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/inspect.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: 'nomad quota inspect command reference'
+description: >
+  The `nomad quota inspect` command displays raw information about a particular
+  quota specification in Nomad Enterprise.
+---
+
+# `nomad quota inspect` command reference
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 11,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 1000,
+                    "Cores": 1,
+                    "Devices": null,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "MemoryMB": 1000,
+                    "MemoryMaxMB": 0,
+                    "NUMA": null,
+                    "Networks": null
+                },
+                "VariablesLimit": 0
+            }
+        ],
+        "ModifyIndex": 11,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 11,
+            "ModifyIndex": 12,
+            "Name": "default",
+            "Used": {
+                "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=": {
+                    "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 0,
+                        "Cores": 0,
+                        "Devices": null,
+                        "DiskMB": 0,
+                        "IOPS": 0,
+                        "MemoryMB": 0,
+                        "MemoryMaxMB": 0,
+                        "NUMA": null,
+                        "Networks": null
+                    },
+                    "VariablesLimit": 0
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t '{{ .Description }}' default-quota
+Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/quota/list.mdx b/content/nomad/v1.11.x/content/commands/quota/list.mdx
new file mode 100644
index 0000000000..f7500264c4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'nomad quota list command reference'
+description: |
+  The `nomad quota list` command displays a list of available quota specifications in Nomad Enterprise.
+---
+
+# `nomad quota list` command reference
+
+The `quota list` command is used to list available quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/quota/status.mdx b/content/nomad/v1.11.x/content/commands/quota/status.mdx
new file mode 100644
index 0000000000..7daadeedf7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/quota/status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'nomad quota status command reference'
+description: >
+  The `nomad quota status` command displays status information for a particular quota specification in Nomad Enterprise.
+---
+
+# `nomad quota status` command reference
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 1000   0 / 1       0 / 1000      0 / inf           0 / inf
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota status -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota status -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/recommendation/apply.mdx b/content/nomad/v1.11.x/content/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..bccc4a5425
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad recommendation apply command reference'
+description: |
+  The `nomad recommendation apply` command applies one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation apply` command reference
+
+The `recommendation apply` command is used to apply recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/recommendation/dismiss.mdx b/content/nomad/v1.11.x/content/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..165728e4ea
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad recommendation dismiss command reference'
+description: |
+  The `nomad recommendation dismiss` command dismisses one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation dismiss` command reference
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/recommendation/index.mdx b/content/nomad/v1.11.x/content/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..dbae1f81ef
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/recommendation/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad recommendation command reference'
+description: |
+  The `nomad recommendation` command interacts with recommendations in Nomad Enterprise. Display a specific recommendation or a list of recommendations. Apply or dismiss recommendations.
+---
+
+# `nomad recommendation` command reference
+
+The `recommendation` command is used to interact with recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation <subcommand> [options]
+```
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/commands/recommendation/apply
+[recommendationdismiss]: /nomad/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/commands/recommendation/info
+[recommendationlist]: /nomad/commands/recommendation/list
diff --git a/content/nomad/v1.11.x/content/commands/recommendation/info.mdx b/content/nomad/v1.11.x/content/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..8ff4728b99
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad recommendation info command reference'
+description: |
+  The `nomad recommendation info` command displays information about the specified recommendation in Nomad Enterprise.
+---
+
+# `nomad recommendation info` command reference
+
+The `recommendation info` command is used to read the specified recommendation.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/recommendation/list.mdx b/content/nomad/v1.11.x/content/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..cd4e57ee24
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'nomad recommendation list command reference'
+description: |
+  The `nomad recommendation list` command displays a list of available recommendations in Nomad Enterprise. Filter options include job, group, and task.
+---
+
+# `nomad recommendation list` command reference
+
+The `recommendation list` command is used to list the available recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/scaling/index.mdx b/content/nomad/v1.11.x/content/commands/scaling/index.mdx
new file mode 100644
index 0000000000..48733e53d7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'nomad scaling command reference'
+description: |
+  The `nomad scaling` command interacts with scaling policies.
+---
+
+# `nomad scaling` command reference
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+```plaintext
+nomad scaling <subcommand> [options]
+```
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/commands/scaling/policy-list
diff --git a/content/nomad/v1.11.x/content/commands/scaling/policy-info.mdx b/content/nomad/v1.11.x/content/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..87c80daf74
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad scaling policy info command reference'
+description: |
+  The `nomad scaling policy info` command displays detailed information for the specified scaling policy.
+---
+
+# `nomad scaling policy info` command reference
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/scaling/policy-list.mdx b/content/nomad/v1.11.x/content/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..87cf42d46d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad scaling policy list command reference'
+description: |
+  The `nomad scaling policy list` command displays all Nomad scaling policies. Filter options include job and policy type.
+---
+
+# `nomad scaling policy list` command reference
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/sentinel/apply.mdx b/content/nomad/v1.11.x/content/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..c5a354d0cd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/sentinel/apply.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'nomad sentinel apply command reference'
+description: >
+  The `nomad sentinel apply` command creates or updates a Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel apply` command reference
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Additionally, you must specify the `-scope` option. Refer to the [`-scope` field
+description](/nomad/commands/sentinel/apply#scope) for more information.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : Required. Sets the scope of the policy and when it
+  should be enforced. Specify one of the following:
+
+  - The `submit-job` scope for registering jobs
+  - The `submit-host-volume` scope for creating or updating dynamic host
+    volumes.
+  - The `submit-csi-volume` scope for creating or updating CSI volumes.
+
+  Refer to the [Sentinel guide](/nomad/docs/reference/sentinel-policy) for scope details.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -scope "submit-job" -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/sentinel/delete.mdx b/content/nomad/v1.11.x/content/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..ee53e60bab
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad sentinel delete command reference'
+description: |
+  The `nomad sentinel delete` command deletes the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel delete` command reference
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/sentinel/index.mdx b/content/nomad/v1.11.x/content/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..16dd80aba1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/sentinel/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad sentinel command reference'
+description: |
+  The `nomad sentinel` command interacts with Sentinel policies in Nomad Enterprise. Create, update, and delete a policy. Inspect and list policies.
+---
+
+# `nomad sentinel` command reference
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel <subcommand> [options]
+```
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/commands/sentinel/delete
+[list]: /nomad/commands/sentinel/list
+[read]: /nomad/commands/sentinel/read
+[apply]: /nomad/commands/sentinel/apply
diff --git a/content/nomad/v1.11.x/content/commands/sentinel/list.mdx b/content/nomad/v1.11.x/content/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..aa0f6183f1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad sentinel list command reference'
+description: |
+  The `nomad sentinel list` command displays a list all Sentinel policies installed in Nomad Enterprise.
+---
+
+# `nomad sentinel list` command reference
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/sentinel/read.mdx b/content/nomad/v1.11.x/content/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..6e30b6e26c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad sentinel read command reference'
+description: |
+  The `nomad sentinel read` command displays detailed information about the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel read` command reference
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/server/force-leave.mdx b/content/nomad/v1.11.x/content/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..52a32031df
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/server/force-leave.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad server force-leave command reference'
+description: >
+  The `nomad server force-leave` command forces a server into the left state so that you can eject server nodes that have failed.
+---
+
+# `nomad server force-leave` command reference
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`.
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## Options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/server/index.mdx b/content/nomad/v1.11.x/content/commands/server/index.mdx
new file mode 100644
index 0000000000..89e81efeb8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/server/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad server command reference'
+description: |
+  The `nomad server` command interacts with Nomad servers. Display a list of servers, join server nodes together, and force a server into the left state.
+---
+
+# `nomad server` command reference
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+```plaintext
+nomad server <subcommand> [options]
+```
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/commands/server/join 'Join server nodes together'
+[members]: /nomad/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.11.x/content/commands/server/join.mdx b/content/nomad/v1.11.x/content/commands/server/join.mdx
new file mode 100644
index 0000000000..2a329ade41
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad server join command reference'
+description: >
+  The `nomad server join` command joins the local server to one or more Nomad
+  servers.
+---
+
+# `nomad server join` command reference
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: //nomad/docs/deploy/clusters/federate-regions
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/server/members.mdx b/content/nomad/v1.11.x/content/commands/server/members.mdx
new file mode 100644
index 0000000000..b84912cc76
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/server/members.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'nomad server members command reference'
+description: >
+  The `nomad server members` command displays a list of servers in the cluster. Review name, address, port, region, datacenter, Raft version, build version, status, tags, and whether the server is the leader.
+---
+
+# `nomad server members` command reference
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server members in its JSON format.
+
+- `-t`: Format and display the server members using a Go template.
+
+- `-ui`: Open the servers page in the browser.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/service/delete.mdx b/content/nomad/v1.11.x/content/commands/service/delete.mdx
new file mode 100644
index 0000000000..4ea532f530
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'nomad service delete command reference'
+description: |
+  The `nomad service delete` command deletes a Nomad service by name and ID.
+---
+
+# `nomad service delete` command reference
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/service/index.mdx b/content/nomad/v1.11.x/content/commands/service/index.mdx
new file mode 100644
index 0000000000..469d187bd8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/service/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'nomad service command reference'
+description: |
+  The `nomad service` command interacts with Nomad services. Display service  information and delete a registered service.
+---
+
+# `nomad service` command reference
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+```plaintext
+nomad service <subcommand> [options]
+```
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/commands/service/delete
+[serviceinfo]: /nomad/commands/service/info
+[servicelist]: /nomad/commands/service/list
diff --git a/content/nomad/v1.11.x/content/commands/service/info.mdx b/content/nomad/v1.11.x/content/commands/service/info.mdx
new file mode 100644
index 0000000000..9eab949495
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/service/info.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad service info command reference'
+description: |
+  The `nomad service info` command displays information about the specified registered service. Search by service name to review namespace, job, allocation, node, datacenter, address, and tags.
+---
+
+# `nomad service info` command reference
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/service/list.mdx b/content/nomad/v1.11.x/content/commands/service/list.mdx
new file mode 100644
index 0000000000..ebe1dbacb2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad service list command reference'
+description: |
+  The `nomad service list` command displays a list of registered Nomad services.
+---
+
+# `nomad service list` command reference
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/setup/consul.mdx b/content/nomad/v1.11.x/content/commands/setup/consul.mdx
new file mode 100644
index 0000000000..ac943c2868
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/setup/consul.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'nomad setup consul command reference'
+description: |
+  The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup consul` command reference
+
+The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Consul and respects
+`CONSUL_HTTP_TOKEN`, `CONSUL_HTTP_ADDR`, and other [Consul-related environment
+variables][consulenv].
+
+## Usage
+
+```plaintext
+nomad setup consul [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup consul
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Consul ACL using their
+respective workload identities.
+
+First we need to connect to Consul.
+
+[?] Is "127.0.0.1:8500" the correct address of your Consul cluster? [Y/n]
+
+Since you're running Consul Enterprise, we will additionally create
+a namespace "nomad-workloads" and bind the auth methods to that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Consul cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+Nomad needs a JWT auth method for Consul services and tasks. The method for
+services will be called "nomad-workloads".
+
+This is the "nomad-workloads" method configuration:
+
+{
+    "Name": "nomad-workloads",
+    "Type": "jwt",
+    "DisplayName": "nomad-workloads",
+    "Description": "Login method for Nomad workloads using workload identities",
+    "TokenLocality": "local",
+    "Config": {
+        "BoundAudiences": [
+            "consul.io"
+        ],
+        "ClaimMappings": {
+            "consul_namespace": "consul_namespace",
+            "nomad_job_id": "nomad_job_id",
+            "nomad_namespace": "nomad_namespace",
+            "nomad_service": "nomad_service",
+            "nomad_task": "nomad_task"
+        },
+        "JWKSURL": "http://localhost:4646/.well-known/jwks.json",
+        "JWTSupportedAlgs": [
+            "RS256"
+        ]
+    },
+    "CreateIndex": 0,
+    "ModifyIndex": 0,
+    "NamespaceRules": [
+        {
+            "BindNamespace": "${value.consul_namespace}"
+        }
+    ]
+}
+[?] Create "nomad-workloads" auth method in your Consul cluster? [Y/n]
+[✔] Created auth method "nomad-workloads".
+
+Consul uses binding rules to map claims between Nomad's JWTs to Consul service
+identities and ACL roles, so we need to create a two binding rules for the auth
+method we created above: one for services, and one for tasks.
+
+This is the binding rule for services:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad services authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" in value",
+    "BindType": "service",
+    "BindName": "${value.nomad_service}",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n]
+[✔] Created binding rule for auth method "nomad-workloads".
+
+This is the binding rule for tasks:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad tasks authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" not in value",
+    "BindType": "role",
+    "BindName": "nomad-${value.nomad_namespace}-tasks",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Consul
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Auth method: nomad-workloads
+  * Binding rules: 4d80108a-6d77-36e1-71b1-d20a9acf8b17
+  * Namespace: nomad-workloads
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted binding rule "4d80108a-6d77-36e1-71b1-d20a9acf8b17".
+[✔] Deleted auth method "nomad-workloads".
+[✔] Deleted namespace "nomad-workloads".
+
+Consul cluster has not been configured for authenticating Nomad tasks and
+services using workload identitiies.
+
+Run the command again to finish the configuration process.
+```
+
+[consulenv]: /consul/commands#environment-variables
diff --git a/content/nomad/v1.11.x/content/commands/setup/index.mdx b/content/nomad/v1.11.x/content/commands/setup/index.mdx
new file mode 100644
index 0000000000..0463070acf
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/setup/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad setup command reference'
+description: |
+  The `nomad setup` command sets up Consul and Vault integration.
+---
+
+# `nomad setup` command reference
+
+The `setup` command groups helper subcommands used for setting up external
+tools.
+
+<Warning>
+
+These commands are experimental features and may change their behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup <subcommand> [options]
+```
+
+Run `nomad setup <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`setup consul`][consul] - Setup a Consul cluster for Nomad integration.
+- [`setup vault`][vault] - Setup a Vault cluster for Nomad integration.
+
+[consul]: /nomad/commands/setup/consul
+[vault]: /nomad/commands/setup/vault
diff --git a/content/nomad/v1.11.x/content/commands/setup/vault.mdx b/content/nomad/v1.11.x/content/commands/setup/vault.mdx
new file mode 100644
index 0000000000..f1e56cd6da
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/setup/vault.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: 'nomad setup vault command reference'
+description: |
+  The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup vault` command reference
+
+The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Vault and respects
+`VAULT_TOKEN`, `VAULT_ADDR`, and other [Vault-related environment
+variables][vaultenv].
+
+The `-check` option can be used to verify if the Nomad cluster is ready to
+migrate to use Workload Identities with Vault. This option requires
+`operator:read` permission for Nomad.
+
+## Usage
+
+```plaintext
+nomad setup vault [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+- `-check`: Verify if the Nomad cluster is ready to migrate to Workload
+  Identities.
+
+### Options when using `-check`
+
+- `-json`: Output migration status information in its JSON format.
+
+- `-t`: Format and display migration status information using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup vault
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Vault ACL using their
+respective workload identities.
+
+First we need to connect to Vault.
+
+[?] Is "http://127.0.0.1:8200" the correct address of your Vault cluster? [Y/n]
+
+Since you're running Vault Enterprise, we will additionally create
+a namespace "nomad-workloads" and create all configuration within that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Vault cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+We will now enable the JWT credential backend and create a JWT auth method that
+Nomad workloads will use.
+
+This is the method configuration:
+
+{
+    "default_role": "nomad-workloads",
+    "jwks_url": "http://localhost:4646/.well-known/jwks.json",
+    "jwt_supported_algs": [
+        "EdDSA",
+        "RS256"
+    ]
+}
+[?] Create JWT auth method in your Vault cluster? [Y/n]
+[✔] Created JWT auth method "jwt-nomad".
+
+We need to create a role that Nomad workloads will assume while authenticating,
+and a policy associated with that role.
+
+
+These are the rules for the policy "nomad-workloads" that we will create. It uses a templated
+policy to allow Nomad tasks to access secrets in the path
+"secrets/data/<job namespace>/<job name>":
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+
+[?] Create the above policy in your Vault cluster? [Y/n]
+[✔] Created policy "nomad-workloads".
+
+We will now create an ACL role called "nomad-workloads" associated with the policy above.
+
+{
+    "bound_audiences": "vault.io",
+    "claim_mappings": {
+        "nomad_job_id": "nomad_job_id",
+        "nomad_namespace": "nomad_namespace",
+        "nomad_task": "nomad_task"
+    },
+    "role_type": "jwt",
+    "token_period": "30m",
+    "token_policies": [
+        "nomad-workloads"
+    ],
+    "token_type": "service",
+    "user_claim": "/nomad_job_id",
+    "user_claim_json_pointer": true
+}
+[?] Create role in your Vault cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Vault
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Policy: "nomad-workloads"
+  * JWT auth method: "jwt-nomad"
+  * Namespace: "nomad-workloads"
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted policy "nomad-workloads".
+[✔] Disabled JWT auth method "jwt-nomad".
+[✔] Deleted namespace "nomad-workloads".
+
+Vault cluster has not been configured for authenticating Nomad tasks and
+services using workload identities.
+
+Run the command again to finish the configuration process.
+```
+
+The `-check` option can use to verify if a cluster is ready to migrate to using
+workload identities with Vault.
+
+```
+$ nomad setup vault -check
+
+Jobs Without Workload Identity for Vault
+The following jobs access Vault but are not configured for workload identity.
+
+You should redeploy them before fully migrating to workload identities with
+Vault to prevent unexpected errors if their tokens need to be recreated.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID       Namespace  Type     Status
+example  default    service  running
+
+Outdated Nodes
+The following nodes are running a version of Nomad that does not support using
+workload identities with Vault.
+
+You should upgrade them to Nomad 1.7 before fully migrating to workload
+identities with Vault to prevent unexpected errors if they receive allocations
+for jobs that use Vault.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID        Name      Address        Version  Drain  Eligibility  Status
+049f7683  client-1  192.168.0.186  1.6.4    false  eligible     ready
+
+Vault Tokens
+The following Vault ACL tokens were created by Nomad but will not be
+automatically revoked after migrating to workload identities. They will expire
+once their TTL reaches zero.
+
+Accessor ID               Allocation ID  Node ID   Configured TTL
+czh9MPcRXzAhxBL9XKyb3Kh1  f00893d4       049f7683  60
+```
+
+@include 'general_options_no_namespace.mdx'
+
+[vaultenv]: /vault/docs/commands#environment-variables
diff --git a/content/nomad/v1.11.x/content/commands/status.mdx b/content/nomad/v1.11.x/content/commands/status.mdx
new file mode 100644
index 0000000000..7da9b5f121
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/status.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: 'nomad status command reference'
+description: |
+  The `nomad status` command display the status output for any Nomad resource.
+---
+
+# `nomad status` command reference
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/system/gc.mdx b/content/nomad/v1.11.x/content/commands/system/gc.mdx
new file mode 100644
index 0000000000..15ffcaa21e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad system gc command reference'
+description: |
+  The `nomad system gc` command runs the system garbage collection process on jobs, evaluations, allocations, and nodes.
+---
+
+# `nomad system gc` command reference
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/system/index.mdx b/content/nomad/v1.11.x/content/commands/system/index.mdx
new file mode 100644
index 0000000000..99d11156c6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/system/index.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: 'nomad system command reference'
+description: |
+  The `nomad system` commands run garbage collection and reconcile job summaries.
+---
+
+# `nomad system` command reference
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+```plaintext
+nomad system <subcommand> [options]
+```
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.11.x/content/commands/system/reconcile-summaries.mdx b/content/nomad/v1.11.x/content/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..021ee3d286
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad system reconcile summaries command reference'
+description: |
+  The `nomad system reconcile summaries` command reconciles the summaries of all registered jobs.
+---
+
+# `nomad system reconcile summaries` command reference
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/tls/ca-create.mdx b/content/nomad/v1.11.x/content/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..b3ea8ff0df
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/tls/ca-create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad tls ca create command reference'
+description: |
+  The `nomad tls ca create` command creates a certificate authority that you then use to create a self-signed certificate for Nomad Transport Layer Security (TLS) configuration.
+---
+
+# `nomad tls ca create` command reference
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.11.x/content/commands/tls/ca-info.mdx b/content/nomad/v1.11.x/content/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..edb0c805fc
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/tls/ca-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad tls ca info command reference'
+description: |
+  The `nomad tls ca info` command displays serial number, issuer, name, expiration date, and permitted DNS domains for the provided certificate authority (CA) file.
+---
+
+# `nomad tls ca info` command reference
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.11.x/content/commands/tls/cert-create.mdx b/content/nomad/v1.11.x/content/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..8ed911330d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'nomad tls cert create command reference'
+description: |
+  The `nomad tls cert create` command creates a server, client, or command-line interface (CLI) certificate for Transport Layer Security (TLS) configuration in your Nomad cluster.
+---
+
+# `nomad tls cert create` command reference
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+```plaintext
+nomad tls cert create [options]
+```
+
+## Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/docs/secure/traffic/tls
diff --git a/content/nomad/v1.11.x/content/commands/tls/cert-info.mdx b/content/nomad/v1.11.x/content/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..12f55e71e6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/tls/cert-info.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad tls cert info command reference'
+description: |
+  The `nomad tls cert info` command displays serial number, issuer, name, expiration date, DNS names, and IP address from a specified certificate file.
+---
+
+# `nomad tls cert info` command reference
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.11.x/content/commands/tls/index.mdx b/content/nomad/v1.11.x/content/commands/tls/index.mdx
new file mode 100644
index 0000000000..f817f2f52f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/tls/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad tls command reference'
+description: |
+  The `nomad tls` command creates and displays information about a certificate authority and self-signed certificate for Nomad's Transport Security Layer (TLS).
+---
+
+# `nomad tls` command reference
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+```plaintext
+nomad tls <subcommand> <subcommand> [options]
+```
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/commands/tls/cert-info 'Display information from a certificate'
diff --git a/content/nomad/v1.11.x/content/commands/ui.mdx b/content/nomad/v1.11.x/content/commands/ui.mdx
new file mode 100644
index 0000000000..30dfa743d6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad ui command reference'
+description: |
+  The `nomad ui` command opens the Nomad Web UI. Provide a node, job, or allocation identifier to open that object's UI page in your browser. Authenticate with an access control list (ACL) token. Use the `show-url` flag to return the UI's URL.
+---
+
+# `nomad ui` command reference
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/var/get.mdx b/content/nomad/v1.11.x/content/commands/var/get.mdx
new file mode 100644
index 0000000000..0410d2d942
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/get.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: nomad var get reference
+description: |-
+  The `nomad var get` command retrieves the variable at the given path from
+  Nomad.
+---
+
+# `nomad var get` command reference
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+- `-ui`: Open the variable page in the browser.
+
+## Examples
+
+@include 'variables/get-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.11.x/content/commands/var/index.mdx b/content/nomad/v1.11.x/content/commands/var/index.mdx
new file mode 100644
index 0000000000..3d4df5282b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/index.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: nomad var reference
+description: |-
+  The `nomad var` commands interact with Nomad variables. Create a variable specification file. Insert, update, delete, or acquire a lock over a variable. Fetch and list variables.
+---
+
+# `nomad var` command reference
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+```plaintext
+nomad var <subcommand> [options] [args]
+```
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+- [`var lock`][lock] - Acquire a lock over a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/commands/var/init
+[get]: /nomad/commands/var/get
+[list]: /nomad/commands/var/list
+[put]: /nomad/commands/var/put
+[purge]: /nomad/commands/var/purge
+[lock]: /nomad/commands/var/lock
diff --git a/content/nomad/v1.11.x/content/commands/var/init.mdx b/content/nomad/v1.11.x/content/commands/var/init.mdx
new file mode 100644
index 0000000000..764cb0b293
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/init.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad var init command reference'
+description: |
+  The `nomad var init` command generates an example variable specification that you can customize for your Nomad variables.
+---
+
+# `nomad var init` command reference
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+@include 'variables/init-example.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/var/list.mdx b/content/nomad/v1.11.x/content/commands/var/list.mdx
new file mode 100644
index 0000000000..a8a4b46daf
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/list.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: nomad var list reference
+description: |-
+  The `nomad var list` command displays data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# `nomad var list` command reference
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+- `-ui`: Open the variable list page in the browser.
+
+## Examples
+
+@include 'variables/list-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.11.x/content/commands/var/lock.mdx b/content/nomad/v1.11.x/content/commands/var/lock.mdx
new file mode 100644
index 0000000000..e576da8181
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/lock.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: nomad var lock reference
+description: |-
+  The `nomad var lock` command locks a variable, only allowing the lock owner to modify it.
+---
+
+# `nomad var lock` command reference
+
+The `var lock` command holds a lock on a [variable][].
+
+## Usage
+
+```plaintext
+nomad var lock [options] <lock spec file reference> child...
+nomad var lock [options] <path to store variable> [<variable spec file reference>] child
+```
+
+The lock command provides a mechanism for simple distributed locking. A lock
+is created in the given variable, and only when held, is a child process invoked.
+
+The lock command can be called on an existing variable or an entire new variable
+specification can be provided to the command from a file by using an
+@-prefixed path to a variable specification file. Items to be stored in the
+variable can be supplied using the specification file as well.
+
+Nomad lock launches its children in a shell. By default, Nomad will use the
+shell defined in the environment variable SHELL. If SHELL is not defined,
+it will default to /bin/sh. It should be noted that not all shells terminate
+child processes when they receive SIGTERM. Under Ubuntu, /bin/sh is linked
+to dash, which does not terminate its children. In order to ensure that
+child processes are killed when the lock is lost, be sure to set the SHELL
+environment variable appropriately, or run without a shell by setting -shell=false.
+
+If [ACLs][] are enabled, this command requires the 'variables:write' capability
+for the destination namespace and path.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## Options
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `ttl`: Optional, TTL for the lock, time the variable will be locked. Defaults to 15s.
+
+- `delay`: Optional, time the variable is blocked from locking when a lease is not renewed.
+	Defaults to 15s.
+
+- `max-retry`:Optional, max-retry up to this number of times if Nomad returns a 500 error
+	while monitoring the lock. This allows riding out brief periods of
+	unavailability without causing leader elections, but increases the amount of
+	time required to detect a lost lock in some cases. Defaults to 5. Set to 0 to
+	disable.
+
+- `shell`: Optional, use a shell to run the command (can set a custom shell via
+	the SHELL environment variable). The default value is true.
+
+## Examples
+
+@include 'variables/lock-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]:  /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
+[ACL]: /nomad/docs/other-specifications/acl-policy#variables
+
diff --git a/content/nomad/v1.11.x/content/commands/var/purge.mdx b/content/nomad/v1.11.x/content/commands/var/purge.mdx
new file mode 100644
index 0000000000..45213ea338
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/purge.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: nomad var purge reference
+description: |-
+  The `nomad var purge` command permanently removes the specified variable
+  from Nomad.
+---
+
+# `nomad var purge` command reference
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+@include 'variables/purge-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.11.x/content/commands/var/put.mdx b/content/nomad/v1.11.x/content/commands/var/put.mdx
new file mode 100644
index 0000000000..7b829fe20e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/var/put.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: nomad var put reference
+description: |-
+  The `nomad var put` command creates or updates a Nomad variable.
+---
+
+# `nomad var put` command reference
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `-ui`: Open the variable page in the browser.
+
+## Examples
+
+@include 'variables/put-example.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.11.x/content/commands/version.mdx b/content/nomad/v1.11.x/content/commands/version.mdx
new file mode 100644
index 0000000000..eec3c9c626
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad version command reference'
+description: |
+  The `nomad version` command displays the version, build date, and revision information for a Nomad installation.
+---
+
+# `nomad version` command reference
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.11.x/content/commands/volume/claim-delete.mdx b/content/nomad/v1.11.x/content/commands/volume/claim-delete.mdx
new file mode 100644
index 0000000000..706b69f498
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/claim-delete.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad volume claim delete command reference'
+description: |
+  The `nomad volume claim delete` command deletes a task group host volume claim.
+---
+
+# `nomad volume claim delete` command reference
+
+The `volume claim delete` command deletes a task group host volume claim.
+[Stateful deployments][stateful deployments] use these claims.
+
+## Usage
+
+```plaintext
+nomad volume claim delete [options] <claim_id>
+```
+
+This command accepts claim ID or prefix as the sole argument. The command
+deletes the claim if there is an exact match based on the provided claim
+ID or prefix, Otherwise, the command displays a list of matching claims and
+information.
+
+When ACLs are enabled, this command requires a token with the
+`host-volume-write` capability in the volume's namespace.
+
+## Options
+
+- `-y`: Automatically answers "yes" to all the questions, making the deletion
+  non-interactive. Defaults to "false."
+
+## Example
+
+List all volumes.
+
+```shell-session
+$ nomad volume claim delete 3f25be9a
+
+  If you delete a volume claim, the allocation that uses this claim to "stick"
+  to a particular volume ID will no longer use it upon its next reschedule or
+  migration. The deployment of the task group the allocation runs will still
+  claim another feasible volume ID during reschedule or replacement.
+
+[?] Are you sure you want to delete task group host volume claim 3f25be9a? [Y/n]
+Task group host volume claim 3f25be9a-a2ee-3d7f-c248-45099fd54939 successfully deleted
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
diff --git a/content/nomad/v1.11.x/content/commands/volume/claim-list.mdx b/content/nomad/v1.11.x/content/commands/volume/claim-list.mdx
new file mode 100644
index 0000000000..d233652774
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/claim-list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: volume claim list'
+description: |
+  List task group host volume claims.
+---
+
+# Command: volume claim list
+
+The `volume claim list` command displays all task group host volume claims.
+[Stateful deployments][stateful deployments] use these claims.
+
+## Usage
+
+```plaintext
+nomad volume claim list [options] [claim_id]
+```
+
+This command accepts an optional claim ID or prefix as the sole argument. If
+there is an exact match based on the provided volume ID or prefix, then
+the command displays information about the specific claim. Otherwise, the command
+displays a list of matching claims.
+
+If you omit the ID, the command lists out all of the existing claims and a
+few of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the `host-volume-read`
+capability in the volume's namespace.
+
+## Options
+
+- `-job`: Show only volume claims from a particular job ID.
+
+- `-group`: Show only volume claims from a particular task group name.
+
+- `-volume-name`: Show only volume claims from a particular volume name.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List of all task group host volume claim for job ID "example".
+
+```shell-session
+$ nomad volume claim list -job=example
+ID        Namespace  Job ID   Volume ID  Volume Name
+81b43af2  default    example  18377894   sticky-volume
+7ce38017  default    example  c3c27514   example-volume
+```
+
+List of all task group host volume claims, prefix by 81.
+.
+```shell-session
+$ nomad volume claim list 81
+ID        Namespace  Job ID   Volume ID  Volume Name
+81b43af2  default    example  18377894   sticky-volume
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
diff --git a/content/nomad/v1.11.x/content/commands/volume/create.mdx b/content/nomad/v1.11.x/content/commands/volume/create.mdx
new file mode 100644
index 0000000000..33a2992e15
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/create.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: 'nomad volume create command reference'
+description: |
+  The `nomad volume create` command creates storage volumes that are either
+  Container Storage Interface (CSI) volumes or dynamic host volumes.
+---
+
+# `nomad volume create` command reference
+
+The `volume create` command creates storage volumes as either [Container Storage
+Interface (CSI)][csi] volumes or dynamic host volumes.
+
+The `volume create` command can create dynamic host volumes if host volume
+plugins are installed on the node, or CSI volumes if the CSI plugins implement
+the [Controller][csi_plugins_internals] interface. The `volume create` command
+automatically [registers][] the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to a
+file containing a valid [volume specification][volume_specification]. Nomad
+reads the file and submits the volume to the server for placement. If the
+supplied path is "-", the volume file is read from STDIN. Otherwise the file is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-create` for dynamic host volumes.
+
+## Options
+
+- `-detach`: Return immediately instead of entering monitor mode for dynamic
+  host volumes. After creating a volume, Nomad prints the volume ID to the
+  screen, which you can use to examine the volume using the `volume status`
+  command. If `-detach` is omitted or false, the command monitors the state of
+  the volume until it has been fingerprinted by the client and is ready to be
+  scheduled. Not valid for CSI volumes.
+
+- `-verbose`: Display full information when monitoring volume state. Used for
+  dynamic host volumes only. Not valid for CSI volumes.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies. 
+
+## Volume specification
+
+Refer to the [CSI Volume Specification][csi_vol_spec] and the [Dynamic Host
+Volume Specification][host_vol_spec] for further information.
+
+## General options
+
+@include 'general_options.mdx'
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[registers]: /nomad/commands/volume/register
+[registered]: /nomad/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
+[csi_vol_spec]: /nomad/docs/other-specifications/volume/csi
+[host_vol_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.11.x/content/commands/volume/delete.mdx b/content/nomad/v1.11.x/content/commands/volume/delete.mdx
new file mode 100644
index 0000000000..c74ae3ee76
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/delete.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad volume delete command reference'
+description: |
+  The `nomad volume delete` command deletes Container Storage Interface (CSI) and dynamic host storage volumes.
+---
+
+# `nomad volume delete` command reference
+
+The `volume delete` command deletes storage volumes that are either [Container
+Storage Interface (CSI)][csi] volumes or dynamic host volumes.
+
+For CSI volumes, only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface support this command. The volume
+is [deregistered][] when it is successfully deleted.
+
+For dynamic host volumes, only volumes with plugins are deleted. Volumes without
+plugins are deregistered without deleting them.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered][] with Nomad in
+order to be deleted. Deleting fails if the volume is still in use by an
+allocation or in the process of being unpublished.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-delete` for dynamic host volumes.
+
+## Options
+
+- `-force`: Delete the volume from the Nomad state store if the node has been
+  garbage collected. You should only use `-force` if the node will never rejoin
+  the cluster. Only available for dynamic host volumes.
+
+- `-secret`: Secrets to pass to the plugin to delete the snapshot. Accepts
+  multiple flags in the form `-secret key=value`. Only available for CSI
+  volumes.
+
+- `-type`: Type of volume to delete. Must be one of "csi" or "host". Defaults to
+  "csi".
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[deregistered]: /nomad/commands/volume/deregister
+[registered]: /nomad/commands/volume/register
diff --git a/content/nomad/v1.11.x/content/commands/volume/deregister.mdx b/content/nomad/v1.11.x/content/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..938bc4ba55
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/deregister.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad volume deregister command reference'
+description: |
+  The `nomad volume deregister` command deregisters Container Storage Interface (CSI) storage volumes.
+---
+
+# `nomad volume deregister` command reference
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+For dynamic host volumes, use the [`volume delete`][] command.
+
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/commands/volume/delete
diff --git a/content/nomad/v1.11.x/content/commands/volume/detach.mdx b/content/nomad/v1.11.x/content/commands/volume/detach.mdx
new file mode 100644
index 0000000000..ed3c39ecd1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad volume detach command reference'
+description: |
+  The `nomad volume detach` command detaches external storage volumes with Container Storage Interface (CSI) plugins.
+---
+
+# `nomad volume detach` command reference
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.11.x/content/commands/volume/index.mdx b/content/nomad/v1.11.x/content/commands/volume/index.mdx
new file mode 100644
index 0000000000..de0db6ef31
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/index.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad volume command reference'
+description: |
+  The `nomad volume` command interacts with volumes. Generate an example volume specification. Create, delete, register, and deregister a volume. Create and delete a volume snapshot. Display a list of volumes and status information for a single volume.
+---
+
+# `nomad volume` command reference
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+```plaintext
+nomad volume <subcommand> [options]
+```
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume claim delete`][claim-delete] - Delete a task group host volume claim.
+- [`volume claim list`][claim-list] - List task group host volume claims.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/commands/volume/create
+[claim-delete]: /nomad/commands/volume/claim-delete
+[claim-list]: /nomad/commands/volume/claim-list
+[delete]: /nomad/commands/volume/delete
+[deregister]: /nomad/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/commands/volume/detach 'Detach a volume'
+[init]: /nomad/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/commands/volume/snapshot-list
+[status]: /nomad/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.11.x/content/commands/volume/init.mdx b/content/nomad/v1.11.x/content/commands/volume/init.mdx
new file mode 100644
index 0000000000..30a18f001f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad volume init command reference'
+description: |
+  The `nomad volume init` command generates an example storage volume specification.
+---
+
+# `nomad volume init` command reference
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Options
+
+- `-json`: Create an example JSON volume specification.
+
+- `-type`: Create an example for a specific type of volume. Use either "csi" or
+  "host", defaults to "csi".
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.11.x/content/commands/volume/register.mdx b/content/nomad/v1.11.x/content/commands/volume/register.mdx
new file mode 100644
index 0000000000..a68ff9a3c2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/register.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'nomad volume register command reference'
+description: |
+  The `nomad volume register` command registers existing Container Storage Interface (CSI) and dynamic host storage volumes.
+---
+
+# `nomad volume register` command reference
+
+The `volume register` command registers storage volumes as either [Container
+Storage Interface (CSI)][csi] volumes or dynamic host volumes. The volume must
+already exist on a node or remote storage provider before you can register
+the volume for use in job task.
+
+To instead create a volume that does not already exist, use the [`volume
+create`][] command. The `volume create` command automatically registers the
+volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. Nomad
+reads the file and submits the volume to the server for placement. If the
+supplied path is "-", Nomad reads the volume file from STDIN. Otherwise Nomad
+reads the file from the supplied path.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-write-volume` capability for CSI
+volumes or `host-volume-register` for dynamic host volumes.
+
+## Options
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies. 
+
+## Volume specification
+
+Refer to the [CSI Volume Specification][csi_vol_spec] and the [Dynamic Host
+Volume Specification][host_vol_spec] for further information.
+
+The `volume register` command allows updating a volume definition. However, you
+can only update some fields after the volume is registered.
+
+For CSI volumes:
+
+- Update the `capacity_min` and `capacity_max` fields and increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+- Add or remove the `capability` blocks, but only if the capability is
+  not currently in use by a mounted volume.
+- Update the `mount_options` block if the volume is not in use.
+- Update the `secrets` block.
+- Update the `context` block. The values for this field are typically provided
+  by the CSI plugin, and you should not update them unless recommended by the
+  CSI plugin's documentation.
+
+For dynamic host volumes:
+
+- Update the `capacity_min` and `capacity_max` fields. The fields are ignored
+  but must be consistent with the `capacity` value if set.
+- Update the `capacity` field to record that you've increased the size of the
+  volume. Reducing volume capacity is not allowed.
+- Update the `constraint` fields on `volume create`, but not after you create the volume.
+- Add or remove the `capability` blocks but only if a mounted volume is not
+  using currently using the capability.
+- Change the `node_pool` field only from empty to the node pool that matches the
+  `node_id` field.
+
+You cannot update the following:
+
+- The `name`, `type`, and `plugin_id` fields.
+- The `node_id` field.
+
+## General options
+
+@include 'general_options.mdx'
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/commands/volume/create
+[csi_vol_spec]: /nomad/docs/other-specifications/volume/csi
+[host_vol_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.11.x/content/commands/volume/snapshot-create.mdx b/content/nomad/v1.11.x/content/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..b2cb9b6e7d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'nomad volume snapshot create command reference'
+description: |
+  The `nomad volume snapshot create` command creates a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot create` command reference
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.11.x/content/commands/volume/snapshot-delete.mdx b/content/nomad/v1.11.x/content/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..1b7fe956b0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot delete command reference'
+description: |
+  The `nomad volume snapshot delete` command deletes a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot delete` command reference
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.11.x/content/commands/volume/snapshot-list.mdx b/content/nomad/v1.11.x/content/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..48702249e7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot list command reference'
+description: |
+  The `nomad volume snapshot list` command displays a list external Container Storage Interface (CSI) volume snapshots along with the source volume ID as known to the external storage provider.
+---
+
+# `nomad volume snapshot list` command reference
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.11.x/content/commands/volume/status.mdx b/content/nomad/v1.11.x/content/commands/volume/status.mdx
new file mode 100644
index 0000000000..bd7d7ad3fc
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/volume/status.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'nomad volume status command reference'
+description: |
+  The `nomad volume status` command displays volume information and status for a single volume or a list of volumes.
+---
+
+# `nomad volume status` command reference
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes or [dynamic host volumes][dhv].
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If
+there is an exact match based on the provided volume ID or prefix, then
+information about the specific volume is queried and displayed. Otherwise, a
+list of matching volumes and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a
+few of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the appropriate
+capability in the volume's namespace: the `csi-read-volume` and
+`csi-list-volumes` capability for CSI volumes, or `host-volume-read` for dynamic
+host volumes.
+
+## Options
+
+- `-type`: Display only volumes of a particular type (one of `"host"` or
+  `"csi"`). If omitted, the command will query for both dynamic host volumes and
+  CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume status
+Dynamic Host Volumes
+ID        Name             Namespace  Plugin ID            Node ID   Node Pool  State
+070dc8ca  internal-plugin  default    mkdir                c3c27514  default    ready
+7ce38017  external-plugin  default    example-plugin-mkfs  c3c27514  default    ready
+
+Container Storage Interface
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all CSI volumes, with external provider info:
+
+```shell-session
+$ nomad volume -type csi status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status -verbose ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/commands/volume/create
+[dhv]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.11.x/content/commands/windows/index.mdx b/content/nomad/v1.11.x/content/commands/windows/index.mdx
new file mode 100644
index 0000000000..ea165c3f3e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/windows/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'nomad windows command reference'
+description: |
+  The `nomad windows` command interacts with the Windows host platform. Install or uninstall Nomad as a Windows service.
+---
+
+# `nomad windows` command reference 
+
+Use the `windows` command to interact with Windows host platforms.
+
+## Usage 
+
+Usage: `nomad windows <subcommand> [options]`
+
+Run `nomad windows <subcommand> -h` for help on that subcommand. The following subcommands are available:
+
+- [`windows service install`][install] - Install Nomad as a Windows service
+- [`windows service uninstall`][uninstall] - Uninstall Nomad as a Windows service
+
+[install]: /nomad/commands/windows/service-install
+[uninstall]: /nomad/commands/windows/service-uninstall
diff --git a/content/nomad/v1.11.x/content/commands/windows/service-install.mdx b/content/nomad/v1.11.x/content/commands/windows/service-install.mdx
new file mode 100644
index 0000000000..d10904bac2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/windows/service-install.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'nomad windows service install command reference'
+description: |
+  The `nomad windows service install` command installs the Nomad binary
+  and creates a Windows service.
+---
+
+# `nomad windows service install` command reference
+
+The `windows service install` command installs the Nomad binary and
+creates a Windows service.
+
+## Usage
+
+```plaintext
+nomad windows service install
+```
+
+The `windows service install` command installs the `nomad` binary used to
+run this command, creates a data and configuration directory, writes a basic
+Nomad configuration file, creates a Windows service to run Nomad, and
+registers the service with Windows Event Log.
+
+If Nomad has been previously installed using this command, subsequent
+executions will do the following:
+
+1. Stop the service if it is running
+1. Install the currently executing nomad binary
+1. Ensure data and configuration directories exist
+1. Write a configuration file if no configuration files are found
+1. Update the service if needed
+1. Update the Event Log configuration if needed.
+
+## Options
+
+- `-config-dir <dir>`: Directory to hold the Nomad agent configuration.
+  Defaults to "{{.ProgramFiles}}\HashiCorp\nomad\bin"
+
+- `-data-dir <dir>`: Directory to hold the Nomad agent state. Defaults
+  to "{{.ProgramData}}\HashiCorp\nomad\data"
+
+- `-install-dir <dir>`: Directory to install the Nomad binary. Defaults 
+  to "{{.ProgramData}}\HashiCorp\nomad\config"
+
+- `-reinstall`: Allow the nomad Windows service to be stopped during install.
+
+## General options
+
+@include 'general_options.mdx'
diff --git a/content/nomad/v1.11.x/content/commands/windows/service-uninstall.mdx b/content/nomad/v1.11.x/content/commands/windows/service-uninstall.mdx
new file mode 100644
index 0000000000..f2f560f65b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/commands/windows/service-uninstall.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'nomad windows service uninstall command reference'
+description: |
+  The `nomad windows service uninstall` command removes the Nomad
+  Windows service.
+---
+
+# `nomad windows service uninstall` command reference
+
+The `windows service uninstall` command removes the Nomad Windows service.
+
+## Usage
+
+```plaintext
+nomad windows service uninstall
+```
+
+The `windows service uninstall` command stops the Nomad service if
+it is currently running, deregisters the service with the Windows Event Log,
+and removes the Windows service. This command does not remove the installed
+Nomad binary or the data and configuration directories.
diff --git a/content/nomad/v1.11.x/content/docs/architecture/cluster/consensus.mdx b/content/nomad/v1.11.x/content/docs/architecture/cluster/consensus.mdx
new file mode 100644
index 0000000000..961f023464
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/cluster/consensus.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol based on Raft to manage cluster node state. Learn about logs, Finite State Machine (FSM), peer set, quorum, committed entry, and leader. 
+---
+
+# Consensus Protocol
+
+This page provides conceptual information on Nomad's [consensus
+protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>), which
+provides [Consistency as defined by CAP](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.11.x/content/docs/architecture/cluster/federation.mdx b/content/nomad/v1.11.x/content/docs/architecture/cluster/federation.mdx
new file mode 100644
index 0000000000..aa00cbd3d2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/cluster/federation.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Federation
+description: |-
+  Nomad federation enables multiple Nomad clusters in different regions to work together seamlessly. Learn about cross-region request forwarding, replication, and Nomad Enterprise's multi-region job deployments.
+---
+
+# Federation
+
+This page provides conceptual information about the Nomad federation feature.
+Learn about cross-region request forwarding, replication, and Nomad Enterprise's
+multi-region job deployments.
+
+Nomad federation is a multi-cluster orchestration and management feature that
+enables multiple Nomad clusters running in different regions to work together
+seamlessly. By federating clusters, you benefit from improved scalability, fault
+tolerance, and centralized management of workloads across various data centers
+or geographical locations.
+
+## Cross-Region request forwarding
+
+API calls can include a `region` query parameter that defines the Nomad region
+the query is specified for. If this is not the local region, Nomad transparently
+forwards the request to a server in the requested region. When you omit the
+query parameter, Nomad uses the region of the server that is processing the
+request.
+
+## Replication
+
+Nomad writes the following objects in the authoritative region and replicates
+them to all federated regions:
+
+- ACL [policies][acl_policy], [roles][acl_role], [auth methods][acl_auth_method],
+  [binding rules][acl_binding_rule], and [global tokens][acl_token]
+- [Namespaces][namespace]
+- [Node pools][node_pool]
+- [Quota specifications][quota]
+- [Sentinel policies][sentinel_policies]
+
+When creating, updating, or deleting these objects, Nomad always sends the
+request to the authoritative region using RPC forwarding.
+
+Nomad starts replication routines on each federated cluster's leader server in a
+hub and spoke design. The routines then use blocking queries to receive updates
+from the authoritative region to mirror in their own state store. These routines
+also implement rate limiting, so that busy clusters do not degrade due to overly
+aggressive replication processes.
+
+<Note> Nomad writes ACL local tokens in the region where you make the request
+and  does not replicate those local tokens. </Note>
+
+## Multi-Region job deployments <EnterpriseAlert inline />
+
+Nomad job deployments can use the [`multiregion`][] block when running in
+federated mode. Multiregion configuration instructs Nomad to register and run
+the job on all the specified regions, removing the need for multiple job
+specification copies and registration on each region. Multiregion jobs do not
+provide regional failover in the event of failure.
+
+[acl_policy]: /nomad/docs/secure/acl/#policies
+[acl_role]: /nomad/docs/secure/acl/#roles
+[acl_auth_method]: /nomad/docs/secure/acl/#authentication-methods
+[acl_binding_rule]: /nomad/docs/secure/acl/#binding-rules
+[acl_token]: /nomad/docs/secure/acl/#tokens
+[node_pool]: /nomad/docs/architecture/cluster/node-pools
+[namespace]: /nomad/docs/other-specifications/namespace
+[quota]: /nomad/docs/other-specifications/quota
+[sentinel_policies]: /nomad/docs/reference/sentinel-policy
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.11.x/content/docs/architecture/cluster/node-identity.mdx b/content/nomad/v1.11.x/content/docs/architecture/cluster/node-identity.mdx
new file mode 100644
index 0000000000..530643bc60
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/cluster/node-identity.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: Node identity
+description: Nomad's node identity feature uniquely identities each Nomad client node and provides an authentication mechanism for nodes to make RPC calls to the Nomad servers.
+---
+
+# Node identity
+
+This page provides conceptual information about Nomad's node identity feature,
+which uniquely identities each Nomad client node and provides an authentication
+mechanism for nodes to make RPC calls to the Nomad servers.
+
+The Nomad cluster gives every node a default identity once the cluster is able
+to fully support the feature with a defined lifetime. This node identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring and is
+generated as part of the node's registration and heartbeat process.
+
+## Node identity claims
+
+Alongside the standard JWT claims such as `exp` (expiration time), `iat` (issued
+at time), and `aud` (audience), Nomad node identity includes the
+`nomad_node_id`, `nomad_node_pool`, and `nomad_node_datacenter` identity claims.
+
+```json
+{
+  "nomad_node_id": "f6e8c9d4-5b6a-4c3d-8e2f-1a2b3c4d5e6f",
+  "nomad_node_pool": "default",
+  "nomad_node_datacenter": "dc1"
+}
+```
+
+To review all identity claims for a specific node, run the
+[`node identity get` command][cli_node_identity_get].
+
+## Node identity renewal
+
+The node pool specification's [`node_identity_ttl`][config_node_identity_ttl]
+parameter dictates the identity's expiration, which defaults to 24 hours. When a
+node's identity exceeds 67% of its lifetime, the Nomad server issues a new
+identity to the node at its next heartbeat.
+
+You may force a node to renew its identity at its next heartbeat by running the
+[`node identity renew` command][cli_node_identity_renew], which ensure the 67%
+lifetime check is bypassed.
+
+## Node identity persistence
+
+A node's identity is stored within its local database, which is persisted within the
+configured [`data_dir`][client_cfg_state_dir]. To view the stored identity,
+along with other state resouces, run the
+[`operator client-state` command][cli_operattor_client_state].
+
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[config_node_identity_ttl]: /nomad/docs/other-specifications/node-pool#node_identity_ttl
+[cli_node_identity_get]: /nomad/commands/node/identity/get
+[cli_node_identity_renew]: /nomad/commands/node/identity/renew
+[client_cfg_state_dir]: /nomad/docs/configuration/client#state_dir
+[cli_operattor_client_state]: /nomad/commands/operator/client-state
diff --git a/content/nomad/v1.11.x/content/docs/architecture/cluster/node-pools.mdx b/content/nomad/v1.11.x/content/docs/architecture/cluster/node-pools.mdx
new file mode 100644
index 0000000000..d9993bb059
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/cluster/node-pools.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Node pools
+description: Nomad's node pools feature groups clients and segments infrastructure into logical units so that jobs have control over client allocation placement. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+---
+
+# Node pools
+
+This page contains conceptual information about Nomad's node pools feature.
+
+@include 'node-pools.mdx'
diff --git a/content/nomad/v1.11.x/content/docs/architecture/cpu.mdx b/content/nomad/v1.11.x/content/docs/architecture/cpu.mdx
new file mode 100644
index 0000000000..76742b8fb9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/cpu.mdx
@@ -0,0 +1,428 @@
+---
+layout: docs
+page_title: How Nomad Uses CPU
+description: Learn how Nomad discovers and uses CPU resources on nodes in order to place and run workloads. Nomad Enterprise can use non-uniform memory access (NUMA) scheduling, which is optimized for the NUMA topology of a client node.
+---
+
+# How Nomad Uses CPUs
+
+This page provides conceptual information on how Nomad discovers and uses CPU resources on nodes in order to place and run workloads.
+
+Every Nomad node has a Central Processing Unit (CPU) providing the computational
+power needed for running operating system processes. Nomad uses the CPU to
+run tasks defined by the Nomad job submitter. For Nomad to know which nodes
+have sufficient capacity for running a given task, each node in the cluster
+is fingerprinted to gather information about the performance characteristics
+of its CPU. The two metrics associated with each Nomad node with regard to
+CPU performance are its bandwidth (how much it can _compute_) and the number
+of cores.
+
+Modern CPUs may contain heterogeneous core types. Apple introduced the M1 CPU
+in 2020 which contains both _performance_ (P-Core) and _efficiency_ (E-Core)
+types. Each core type operates at a different base frequency. Intel introduced
+a similar topology in its Raptor Lake chips in 2022. When fingerprinting
+the characteristics of a CPU Nomad is capable of taking these advanced CPU
+topologies into account.
+
+[![PE Cores](/img/nomad-pe-cores.png)](/img/nomad-pe-cores.png)
+
+## Calculating CPU resources
+
+The total CPU bandwidth of a Nomad node is the sum of the product between the
+frequency of each core type and the total number of cores of that type in the
+CPU.
+
+```
+bandwidth = (p_cores * p_frequency) + (e_cores * e_frequency)
+```
+
+The total number of cores is computed by summing the number of P-Cores and the
+number of E-Cores.
+
+```
+cores = p_cores + e_cores
+```
+
+Nomad does not distinguish between logical and physical CPU cores. One of the
+defining differences between the P-Core and E-Core types is that the E-Cores
+do not support hyperthreading, whereas P-Cores do. As such a single physical
+P-Core is presented as 2 logical cores, and a single E-Core is presented as 1
+logical core.
+
+The example below is from a Nomad node with an Intel i9-13900 CPU. It is made
+up of mixed core types, with a P-Core base frequency of 2 GHz and an E-Core
+base frequency of 1.5 GHz.
+
+These characteristics are reflected in the `cpu.frequency.performance` and
+`cpu.frequency.efficiency` node attributes respectively.
+
+```text
+cpu.arch                        = amd64
+cpu.frequency.efficiency        = 1500
+cpu.frequency.performance       = 2000
+cpu.modelname                   = 13th Gen Intel(R) Core(TM) i9-13900
+cpu.numcores                    = 32
+cpu.numcores.efficiency         = 16
+cpu.numcores.performance        = 16
+cpu.reservablecores             = 32
+cpu.totalcompute                = 56000
+cpu.usablecompute               = 56000
+```
+
+## Reserving CPU resources
+
+In the fingerprinted node attributes, `cpu.totalcompute` indicates the total
+amount of CPU bandwidth the processor is capable of delivering. In some cases it
+may be beneficial to reserve some amount of a node's CPU resources for use by
+the operating system and other non-Nomad processes. This can be done in client
+configuration.
+
+The amount of reserved CPU can be specified in bandwidth via `cpu`.
+
+```hcl
+client {
+  reserved {
+    cpu = 3000 # mhz
+  }
+}
+```
+
+Or as a specific set of `cores` on which to disallow the scheduling of Nomad
+tasks. This capability is available on Linux systems only.
+
+```hcl
+client {
+  reserved {
+    cores = "0-3"
+  }
+}
+```
+
+When the CPU is constrained by one of the above configurations, the node
+attribute `cpu.usablecompute` indicates the total amount of CPU bandwidth
+available for scheduling of Nomad tasks.
+
+## Allocating CPU Resources
+
+When scheduling jobs, a Task must specify how much CPU resource should be
+allocated on its behalf. This can be done in terms of bandwidth in MHz with the
+`cpu` attribute. On Linux under cgroups v1, Nomad maps this MHz value directly
+into a [cpu.share][]. On Linux under cgroups v2, Nomad converts the MHz value to
+a [cpu.weight][] proportionally the same as the cgroups v1 `cpu.share`.
+
+```hcl
+task {
+  resources {
+    cpu = 2000 # mhz
+  }
+}
+```
+
+Note that the isolation mechanism around CPU resources is dependent on each task
+driver and its configuration. The standard behavior is that Nomad ensures a task
+has access to _at least_ as much of its allocated CPU bandwidth. In which case
+if a node has idle CPU capacity, a task may use additional CPU resources.  Some
+task drivers enable limiting a task to use only the amount of bandwidth
+allocated to the task, described in the [CPU Hard Limits](#cpu-hard-limits)
+section below.
+
+### Relative CPU shares/weights on Linux
+
+Linux cgroups are hierarchical, and the `cpu.share`/`cpu.weight` values reflect
+relative weights within a given subtree. Nomad creates its own cgroup subtree
+(`nomad.slice`) on startup, and all `cpu.share`/`cpu.weight` values that Nomad
+writes are relative between processes within that slice. The `nomad.slice`
+subtree is itself relative to another subtree on the host. For example, a host
+running systemd might have the following slices:
+
+```
+/sys/fs/cgroup
+├── nomad.slice
+│   ├── reserve.slice
+│   └── share.slice
+│       ├── 912dcc05-61e1-53cb-5489-a976a1231960.task.scope
+│       ├── 247e706a-6df8-4123-89b3-1bcf2846b503.task.scope
+│       └── 586c0c58-3d50-4730-b4ad-022076d3c6a4.task.scope
+├── system.slice
+│   ├── journald.service
+│   └── (various system services, etc.)
+└── user-1000.slice
+    ├── session-1.scope
+    └── (various user services, etc.)
+```
+
+If the task `912dcc05` has `resources.cpu = 1024` and tasks `247e706a` and
+`586c0c58` have `resources.cpu = 512`, then `912dcc05` will get 50% of the CPU
+resources available to the `nomad.slice` and tasks `247e706a` and `586c0c58`
+will get 25% each. (The `reserve.slice` and `share.slice` are passthrough for
+cpu shares here.) But together they'll get 33% of the total host's CPU resources
+unless the `nomad.slice`, `system.slice`, or `user-1000.slice` have something
+other than the default 1024 shares. The 1024 value is only meaningful within the
+context of the Nomad slice.
+
+### Allocating cores
+
+On Linux systems, Nomad supports reserving whole CPU cores specifically for a
+task. No task will be allowed to run on a CPU core reserved for another task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+  }
+}
+```
+
+We recommend using `resources.cores` for tasks that require high CPU performance
+to give those tasks exclusive access to CPU bandwidth. Sidecar tasks in the same
+allocations can use `resources.cpu` to get a proportional share of the remaining
+CPU on the node.
+
+Nomad Enterprise supports NUMA aware scheduling, which enables operators to
+more finely control which CPU cores may be reserved for tasks.
+
+### CPU hard limits
+
+Some task drivers support the configuration option `cpu_hard_limit`. If enabled
+this option restricts tasks from bursting above their CPU limit even when there
+is idle capacity on the node. The tradeoff is consistency versus utilization.
+A task with too few CPU resources may operate fine until another task is placed
+on the node causing a reduction in available CPU bandwidth, which could cause
+disruption for the underprovisioned task.
+
+### CPU environment variables
+
+To help tasks understand the resources available to them, Nomad sets the
+following environment variables in their runtime environment.
+
+
+- `NOMAD_CPU_LIMIT` - The amount of CPU bandwidth allocated on behalf of the
+  task.
+- `NOMAD_CPU_CORES` - The set of cores in [cpuset][] notation reserved for the
+  task. This value is only set if `resources.cores` is configured.
+
+```sh
+NOMAD_CPU_CORES=3-5
+NOMAD_CPU_LIMIT=9000
+```
+
+## NUMA
+
+Nomad clients are commonly provisioned on real hardware in an on-premise
+environment or in the cloud on large `.metal` instance types. In either case, it
+is likely the underlying server is designed around a [non-uniform memory access (NUMA) topology][numa_wiki].
+Servers that contain multiple CPU sockets or multiple RAM banks per CPU socket
+are characterized by the non-uniform access times involved in accessing system
+memory.
+
+[![NUMA](/img/nomad-numa.png)](/img/nomad-numa.png)
+
+The simplified example machine above has the following topology:
+- 2 physical CPU sockets
+- 4 system memory banks, 2 per socket
+- 8 physical cpu cores (4 per socket)
+- 2 logical cpu cores per physical core
+- 4 PCI devices, 1 per memory bank
+
+### Optimizing performance
+
+Operating system processes take longer to access memory across a NUMA boundary.
+
+Using the example above if a task is scheduled on Core 0, accessing memory in
+Mem 1 might take 20% longer than accessing memory in Mem 0, and accessing memory
+in Mem 2 might take 300% longer.
+
+The extreme differences are due to various physical hardware limitations. A core
+accessing memory in its own NUMA node is optimal. Programs which perform a high
+throughput of reads or writes to/from system memory will have their performance
+substantially hindered by not optimizing their spatial locality with regard to
+the systems NUMA topology.
+
+### SLIT tables
+
+Modern machines will define System Locality Distance Information (SLIT) tables
+in their firmware. These tables are understood and made referenceable by the
+Linux kernel. There are two key pieces of information provided by SLIT tables:
+- Which CPU cores belong to which NUMA nodes
+- The penalty incurred for accessing each NUMA node from a core in every other
+NUMA node
+
+The `lscpu` command can be used to describe the Core associativity on a machine.
+For example on an `r6a.metal` EC2 instance:
+
+```shell-session
+$ lscpu | grep NUMA
+NUMA node(s):           4
+NUMA node0 CPU(s):      0-23,96-119
+NUMA node1 CPU(s):      24-47,120-143
+NUMA node2 CPU(s):      48-71,144-167
+NUMA node3 CPU(s):      72-95,168-191
+```
+
+And the associated performance degradations are available via `numactl`:
+
+```shell-session
+$ numactl -H
+available: 4 nodes (0-3)
+...
+node distances:
+node   0   1   2   3
+  0:  10  12  32  32
+  1:  12  10  32  32
+  2:  32  32  10  12
+  3:  32  32  12  10
+```
+
+These SLIT table node distance values are presented as approximate relative
+ratios. The value of 10 represents an optimal situation where a memory access
+is occurring from a CPU that is part of the same NUMA node. A value of 20 would
+indicate a 200% performance degradation, 30 for 300%, etc.
+
+### Node Attributes
+
+Nomad clients will fingerprint the machine's NUMA topology and export the
+core associativity as node attributes. This data can provide a Nomad operator
+a better understanding of when it might be useful to make use of NUMA aware
+scheduling for certain workloads.
+
+```
+numa.node.count       = 4
+numa.node0.cores      = 0-23,96-119
+numa.node1.cores      = 24-47,120-143
+numa.node2.cores      = 48-71,144-167
+numa.node3.cores      = 72-95,168-191
+```
+
+## NUMA aware scheduling <EnterpriseAlert inline />
+
+Nomad Enterprise is capable of scheduling tasks in a way that is optimized for
+the NUMA topology of a client node. Nomad is able to correlate CPU cores with
+memory nodes and assign tasks to run on specific CPU cores so as to minimize any
+cross-memory node access patterns. Additionally, Nomad is able to correlate
+devices to memory nodes and enable NUMA-aware scheduling to take device
+associativity into account when making scheduling decisions.
+
+A task may specify a `numa` block indicating its NUMA optimization preference. This example allocates a `1080ti` GPU and ensures it is on the same NUMA node as the 4 CPU cores reserved for the task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+    memory = 2048
+
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+
+    numa {
+      affinity = "require"
+      devices = [
+        "nvidia/gpu/1080ti"
+      ]
+	  }
+  }
+}
+```
+
+### `affinity` options
+
+This is a required field. There are three supported affinity options:
+`none`, `prefer`, and `require`, each with their own advantages and tradeoffs.
+
+#### option `none`
+
+In the `none` mode, the Nomad scheduler leverages the apathy of jobs without
+preference of NUMA affinity to help reduce core fragmentation within NUMA nodes.
+It does so by bin-packing the core request of these jobs onto the NUMA nodes
+with the fewest unused cores available.
+
+The `none` mode is the default mode if the `numa` block is not specified.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "none"
+  }
+}
+```
+
+#### option `prefer`
+
+In the `prefer` mode, the Nomad scheduler uses the hardware topology of a node
+to calculate an optimized selection of available cores, but does not limit
+those cores to come from a single NUMA node.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "prefer"
+  }
+}
+```
+
+#### option `require`
+
+In the `require` mode, the Nomad scheduler uses the topology of each potential
+client to find a set of available CPU cores that belong to the same NUMA node.
+If no such set of cores can be found, that node is marked exhausted for the
+resource of `numa-cores`.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "require"
+  }
+}
+```
+
+### `devices` options
+
+`devices` is an optional list of devices that must be colocated on the NUMA node
+along with allocated CPU cores.
+
+The following diagram shows how a set of devices can be correlated to CPU and memory.
+
+[![How a set of devices can be correlated to CPU and memory](/img/nomad-devices-correlate-cpu-memory.png)](/img/nomad-devices-correlate-cpu-memory.png)
+
+This example declares three devices and configures two in the `numa` block.
+
+```hcl
+task {
+  resources {
+    cores = 8
+    memory = 16384
+
+    device "nvidia/gpu/H100" {
+      count = 2
+    }
+    device "intel/net/XXVDA2" {
+      count = 1
+    }
+    device "xilinx/fpga/X7" {
+      count = 1
+    }
+
+    numa {
+	    affinity = "require"
+	    devices = [
+  	    "nvidia/gpu/H100",
+  	    "intel/net/XXVDA2"
+	    ]
+    }
+  }
+}
+```
+
+## Virtual CPU fingerprinting
+
+When running on a virtualized host such as Amazon EC2 Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions will
+require installing the `dmidecode` package manually.
+
+[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
+[cpu.share]: https://www.redhat.com/sysadmin/cgroups-part-two
+[cpu.weight]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#weights
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
diff --git a/content/nomad/v1.11.x/content/docs/architecture/index.mdx b/content/nomad/v1.11.x/content/docs/architecture/index.mdx
new file mode 100644
index 0000000000..a06acf316d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/index.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Architecture
+description: |-
+  Nomad's system architecture supports a "run any workload anywhere" approach to scheduling and orchestration. Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+---
+
+# Architecture
+
+This page provides conceptual information on Nomad architecture.  Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+
+Nomad is a complex system that has many different pieces. To help both users and
+developers of Nomad build a mental model of how it works, this page documents
+the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/how-scheduling-works).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/architecture/cluster/consensus),
+[gossip protocol](/nomad/docs/architecture/security/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/how-scheduling-works)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.11.x/content/docs/architecture/security/gossip.mdx b/content/nomad/v1.11.x/content/docs/architecture/security/gossip.mdx
new file mode 100644
index 0000000000..2d1b698af6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/security/gossip.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Learn how Nomad's gossip protocol uses the Serf library to provide server membership management, which includes cross-region requests, failure detection, and automatic clustering using a consensus protocol.
+---
+
+# Gossip Protocol
+
+This page provides conceptual information about Nomad's gossip protocol, which
+provides server membership management, cross-region requests, failure detection,
+and automatic clustering using a consensus protocol.
+
+Nomad uses the [Serf library][serf] to provide a [gossip
+protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to manage membership.
+The gossip protocol used by Serf is based on ["SWIM: Scalable Weakly-consistent
+Infection-style Process Group Membership Protocol"][swim], with a few minor
+adaptations. There are more details about [Serf's protocol here][gossip].
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate
+in. Membership information provided by the gossip pool allows servers to perform
+cross region requests. The integrated failure detection allows Nomad to
+gracefully handle an entire region losing connectivity, or just a single server
+in a remote region. Nomad also uses the gossip protocol to detect servers in the
+same region to perform automatic clustering via the [consensus
+protocol](/nomad/docs/architecture/cluster/consensus).
+
+To provide all these features, Nomad uses [Serf][serf] as an embedded
+library. From a user perspective, this is not important, since Nomad masks the
+abstraction. However, developers may find it useful to understand how Nomad
+leverages the Serf library.
+
+
+[serf]: https://github.com/hashicorp/serf
+[gossip]: https://github.com/hashicorp/serf/blob/master/docs/internals/gossip.html.markdown
+[swim]: https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf
diff --git a/content/nomad/v1.11.x/content/docs/architecture/security/index.mdx b/content/nomad/v1.11.x/content/docs/architecture/security/index.mdx
new file mode 100644
index 0000000000..14c751743a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/security/index.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad's security model provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel policies (Enterprise), and resource quotas (Enterprise) to enable fine-grained access within and between clusters. Learn how to secure your Nomad clusters with threat models for internal threats and external threats. Review the network ports used by the security model.
+---
+
+# Security Model
+
+This page provides conceptual information on Nomad's security model, which
+provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel
+policies, and resource quotas to enable fine-grained access within and between
+clusters. Learn how to secure your Nomad clusters, threat models, internal
+threats, and external threats. Review the network ports used by the security
+model.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/docs/secure/traffic/tls)** Mutual
+  authentication of both the TLS server and client x509 certificates prevents
+  internal abuse by preventing unauthenticated access to network components
+  within the cluster.
+
+- **[ACLs](/nomad/docs/secure/acl)** Enables authorization for
+  authenticated connections by granting capabilities to ACL tokens.
+
+- **[Namespaces](/nomad/docs/govern/namespaces)** Access to read
+  and write to a namespace can be controlled to allow for granular access to job
+  information managed within a multi-tenant cluster.
+
+- **[Sentinel Policies]**<EnterpriseAlert inline /> Sentinel
+  policies allow for granular control over components such as task drivers
+  within a cluster.
+
+## Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/docs/secure/acl).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+## Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+### Requirements
+
+- [mTLS enabled](/nomad/docs/secure/traffic/tls)
+  Mutual TLS (mTLS) enables [mutual
+  authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+  security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+    Some API endpoints, such as [`/v1/metrics`][api_metrics] and
+    [`/v1/status/peers`][api_status_peers], can be accessed without an ACL
+    token and may be exposed to anyone with access to the Nomad HTTP address
+    when using `tls.verify_https_client=false`. You can use a reverse proxy or
+    other external means to restrict access to them.
+
+- [ACLs enabled](/nomad/docs/secure/acl) The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- [Namespaces](/nomad/docs/govern/namespaces) This feature
+    allows for a cluster to be shared by multiple teams within a company. Using
+    this logical separation is important for multi-tenant clusters to prevent
+    users without access to that namespace from conflicting with each other.
+    This requires ACLs to be enabled in order to be enforced.
+
+- [Sentinel Policies]<EnterpriseAlert inline />
+  [Sentinel](https://www.hashicorp.com/sentinel/) is a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- [Resource Quotas]<EnterpriseAlert inline /> Can limit a
+  namespace's access to the underlying compute resources in the cluster by
+  setting upper-limits for operators. Access to these resource quotas can be
+  managed via ACLs to ensure read-only access for operators so they can't just
+  change their quotas.
+
+### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/secure/vault) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/job-declare/task-driver/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/job-declare/task-driver/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/job-declare/task-driver/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+## Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec)
+  driver.
+
+### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+## Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                           |
+|----------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                   |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/architecture/security/gossip) protocol to manage server membership using [Serf][serf].                                                                        |
+
+
+[api_metrics]: /nomad/api-docs/metrics
+[api_status_peers]: /nomad/api-docs/status#list-peers
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[serf]: https://github.com/hashicorp/serf
+[Sentinel Policies]: /nomad/docs/govern/sentinel
+[Resource Quotas]: /nomad/docs/govern/resource-quotas
diff --git a/content/nomad/v1.11.x/content/docs/architecture/storage/csi.mdx b/content/nomad/v1.11.x/content/docs/architecture/storage/csi.mdx
new file mode 100644
index 0000000000..a478733c4b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/storage/csi.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: Container Storage Interface (CSI) Plugins
+description: |-
+  Nomad's Container Storage Interface (CSI) plugin support enables scheduling tasks with external storage volumes that conform to the CSI specification, including AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, and Ceph. Learn about controller, node, and monolith storage plugins, as well as storage volume lifecycle and state.
+---
+
+# Container Storage Interface (CSI) Plugins
+
+This page provides conceptual information on Nomad's storage plugin support,
+which enables scheduling tasks with external storage volumes that conform to the
+Container Storage Interface (CSI), including AWS Elastic Block Storage (EBS)
+volumes, Google Cloud Platform (GCP) persistent disks, and Ceph. Learn
+about controller, node, and monolith storage plugins, as well as storage volume
+lifecycle and state.
+
+## Introduction
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+[Container Storage Interface][csi-spec] specification unifies these APIs in a
+way that's agnostic to both the storage vendor and the container orchestrator.
+Each storage provider can build its own CSI plugin. Jobs can claim storage
+volumes from AWS Elastic Block Storage (EBS) volumes, GCP persistent disks,
+and Ceph. The Nomad scheduler will be aware of volumes created by
+CSI plugins and schedule workloads based on the availability of volumes on a
+given Nomad client node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.11.x/content/docs/architecture/storage/host-volumes.mdx b/content/nomad/v1.11.x/content/docs/architecture/storage/host-volumes.mdx
new file mode 100644
index 0000000000..0cb98fc109
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/storage/host-volumes.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Host volumes
+description: |-
+  Host volumes mount paths from the Nomad client into allocations. Learn how Nomad supports static and dynamic host volumes.
+---
+
+# Host volumes
+
+## Introduction
+
+@include 'storage/host-volume-explanation.mdx'
+
+## Resources
+
+- [Considerations for stateful workloads](/nomad/docs/architecture/storage/stateful-workloads)
+- [Use dynamic host volumes](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+- [Create a custom host volume plugin](/nomad/plugins/author/host-volume)
+- [Use static host volumes](/nomad/docs/stateful-workloads/static-host-volumes)
diff --git a/content/nomad/v1.11.x/content/docs/architecture/storage/index.mdx b/content/nomad/v1.11.x/content/docs/architecture/storage/index.mdx
new file mode 100644
index 0000000000..03da12190d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/storage/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: |-
+  Storage plugins help you schedule job tasks with dynamically managed storage volumes. Dynamic host volume plugins provision host volumes on client nodes. Container Storage Interface (CSI) plugins provision volumes in
+  third-party systems, such as AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, and Ceph.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with dynamically managed storage volumes.
+
+Choose between two types of storage plugins:
+
+* [Dynamic host volume (DHV) plugins][dhv] provision host volumes on client
+  nodes, and jobs request placement on any node that has a particular host
+  volume by name.
+  * DHV brings allocations to volumes.
+  * Install DHV plugins on Nomad nodes, similar to task drivers. Creating a
+    host volume ties it to the node until the volume is deleted.
+* [Container Storage Interface (CSI) plugins][csi] provision volumes in
+  third-party systems, such as cloud vendors. Nomad calls on them to make
+  the volume available on any node that Nomad chooses to place an allocation.
+  * CSI brings volumes to allocations.
+  * Deploy CSI plugins as Nomad jobs, often two jobs per plugin. Nomad tracks
+    which clients have instances of a given plugin, so it can call on the
+    plugin to mount the volume.
+
+[dhv]: /nomad/docs/architecture/storage/host-volumes
+[csi]: /nomad/docs/architecture/storage/csi
diff --git a/content/nomad/v1.11.x/content/docs/architecture/storage/stateful-workloads.mdx b/content/nomad/v1.11.x/content/docs/architecture/storage/stateful-workloads.mdx
new file mode 100644
index 0000000000..9f7a9a466d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/architecture/storage/stateful-workloads.mdx
@@ -0,0 +1,214 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad. Compare AWS, Azure, and Google Cloud Platform (GCP) storage services. Review the advantages and disadvantages of using Container Storage Interface (CSI) volumes, dynamic host volumes, static host volumes, and ephemeral disks.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. Refer to the [Container Storage Interface
+(CSI) plugins page][csi-concepts] for more information.
+
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+guide](/nomad/docs/stateful-workloads/csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+@include 'storage/host-volume-explanation.mdx'
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Dynamic host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost unless the application can restore the data</li></ul>  | <ul><li>Environments with high performance and low latency persistent storage requirements where the application is designed to tolerate node failures.</li></ul>   |
+| Dynamic host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Static host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Static host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/docs/monitor/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/architecture/storage/csi)
+- [Nomad CSI tutorial](/nomad/docs/stateful-workloads/csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
+
+### Dynamic Host Volumes
+
+- [Dynamic host volumes](/nomad/docs/architecture/storage/host-volumes)
+- [Dynamic host volume guide](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+- [Custom host volume plugin](/nomad/plugins/host-volume)
diff --git a/content/nomad/v1.11.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.11.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..ba13892c11
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,495 @@
+---
+layout: docs
+page_title: Allocation Filesystems
+description: |-
+  Learn how Nomad uses allocation working directories to store job task templates, storage volumes, artifacts, dispatch payloads, and logs. Review image and chroot isolation, as well as when Nomad uses isolation mode.
+---
+
+# Allocation Filesystems
+
+This page provides conceptual information about how Nomad uses allocation
+working directories to store job task templates, storage volumes, artifacts,
+dispatch payloads, and logs. Review image and chroot isolation, as well as when
+Nomad does not use any isolation mode.
+
+Nomad creates a working directory for each allocation on a client. Find this
+directory in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, writes logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like this example.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k,noswap)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/architecture/storage/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/deploy/task-driver/exec#chroot
+[filesystem isolation capability]: /nomad/plugins/author/task-driver#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.11.x/content/docs/concepts/job.mdx b/content/nomad/v1.11.x/content/docs/concepts/job.mdx
new file mode 100644
index 0000000000..0ee6026381
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/job.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: Job
+description: |-
+  Learn how a Nomad workload, called a job, deploys your apps, maintenance scripts, cron jobs, and similar tasks. Review job statuses and how Nomad versions your jobs.
+---
+
+# Job
+
+This page contains conceptual information about jobs, which are the main Nomad
+constructs for workloads that run your apps, maintenance scripts, cron jobs, and
+other tasks. Review job statuses and how Nomad versions your jobs.
+
+## Background
+
+In Nomad, a _job_ is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into [task groups][task-groups].
+
+Declare the desired state of your job in a [job specification][job-spec], or _jobspec_, that describes
+the tasks and resources necessary for the job to run. You can also
+include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual
+job state matches your desired state.
+
+## Job statuses
+
+After you submit your job, Nomad assigns a status to indicate how a job is
+performing. This status indicates how the job's current allocations compare to
+the desired job state.
+
+@include 'job-status-map.mdx'
+
+### CLI statuses
+
+Only the CLI returns these job statuses.
+
+#### `running`
+
+The `running` status indicates that the job has non-terminal allocations.
+
+#### `dead`
+
+The `dead` status indicates that all evaluations and allocations are in a
+terminal state.
+
+#### `dead (stopped)`
+
+The `dead (stopped)` status indicates that a user has manually stopped the job.
+You may start this job again.
+
+### UI statuses
+
+These job statuses only appear in the Nomad UI.
+
+#### Complete
+
+The `Complete` status indicates that all expected allocations are complete. This
+status applies to batch and sysbatch jobs only.
+
+#### Degraded
+
+The `Degraded` status indicates that a [deployment] is not taking place. Some
+allocations are failed, lost, or unplaced.
+
+#### Deploying
+
+The `Deploying` status indicates that a deployment is actively taking place.
+
+#### Failed
+
+The `Failed` status indicates that all allocations are failed, lost, or unplaced.
+
+#### Healthy
+
+The `Healthy` status indicates that all expected allocations are running and
+healthy.
+
+#### Recovering
+
+The `Recovering` status indicates that some allocations are pending.
+
+#### Removed
+
+The `Removed` status indicates that the job appeared in the initial query, but
+the garbage collector has since removed the job. This happens when the user
+remains on the page for a long time.
+
+#### Running
+
+The `Running` status indicates that all expected allocations are running. This
+status applies to batch and sysbatch jobs only.
+
+#### Scaled Down
+
+The `Scaled Down` status indicates that a user has scaled all allocations to
+zero. Nomad's garbage collector has not yet removed or purged the job.
+
+#### Stopped
+
+The `Stopped` status indicates that a user has manually stopped the job.
+Nomad's garbage collector has not yet removed or purged the job.
+
+## Job versions
+
+Nomad creates a new version for your job each time you run your job. A job can
+have an unlimited number of versions, and version history is stored in state.
+Over time, Nomad garbage collects dead versions that do not have a version tag.
+
+### Tag a version
+
+When you want to save or pin a specific version, you need to create a version
+tag with a unique name and optional description. Nomad does not garbage collect
+tagged versions even when the tagged version is dead. This lets you revert to
+a previous version regardless of how old the tagged version is.
+
+You can create, modify, and remove tags using the CLI, API, and web UI. Refer to
+the [Job versions guide][job-versions-guide] for examples.
+
+### Compare versions
+
+You can compare the current job version to all previous versions or to a
+specific version. Additionally, you can compare two specific versions.
+
+Run commands like `nomad job history` to review differences between past versions
+of jobs and their immediate predecessors. Additionally, you can run `nomad job
+plan` to review the hypothetical difference of an update against the current job
+version.
+
+Refer to the [Compare versions section][compare-versions-section] of the Job
+versions guide for examples.
+
+### Revert to a previous version
+
+You can revert the current running job to a previous version. Nomad stops the
+running job and deploys the chosen version with a new version number.
+
+Refer to the [Revert to a version section][revert-version-section] of
+the Job versions guide for examples using the CLI, API, and web UI.
+
+### Clone and edit
+
+Using the web UI, you may clone a version as a new version of the same job or as
+a new job. After you select the version to clone, you may edit, plan, and run
+the new version.
+
+Because Nomad passes job version attributes using query parameters, you can copy
+the browser address bar URL on the **Jobs/Run** screen to send a link to an
+editable job spec.
+
+Refer to the [Clone a version section][clone-version-section] of
+the Job versions guide for cloning examples.
+
+## Related resources
+
+Refer to the following Nomad documentation pages for more information about
+jobs:
+
+- The [job specification][job-spec] contains detailed
+  configuration and examples.
+- The [Schedulers] page explains the different types of Nomad schedulers and how
+  those schedulers run jobs.
+- The [Declare jobs][deploy-jobs] section contains guides for creating a job,
+  using task drivers, and deployment strategies.
+
+These tutorial resources contain examples of different kinds of jobs and how to
+configure them:
+
+- The [Quick Start][quickstart] tutorials cover deploying an application and
+  its resources, which include parameterized and periodic jobs.
+- The [Create Nomad Job Specifications][job-spec-tutorial] collection contains
+  guides for migrating a Java application to Nomad.
+
+
+[allocations]: /nomad/docs/glossary#allocation
+[deployment]: /nomad/docs/glossary/#deployment
+[deploy-jobs]: /nomad/docs/job-declare
+[job-spec]: /nomad/docs/job-specification
+[job-spec-tutorial]: /nomad/tutorials/job-specifications
+[quickstart]: /nomad/tutorials/get-started/gs-deploy-job
+[Schedulers]: /nomad/docs/concepts/scheduling/schedulers
+[task-groups]: /nomad/docs/glossary#task-group
+[tasks]: /nomad/docs/glossary#task
+[job-versions-guide]: /nomad/docs/job-run/versions
+[compare-versions-section]: /nomad/docs/job-run/versions#compare-versions
+[revert-version-section]: /nomad/docs/job-run/versions#revert-to-a-version
+[clone-version-section]: /nomad/docs/job-run/versions#clone-a-version
diff --git a/content/nomad/v1.11.x/content/docs/concepts/scheduling/how-scheduling-works.mdx b/content/nomad/v1.11.x/content/docs/concepts/scheduling/how-scheduling-works.mdx
new file mode 100644
index 0000000000..4dad4a9862
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/scheduling/how-scheduling-works.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: How Nomad job scheduling works
+description: Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+---
+
+# How Nomad job scheduling works
+
+This page provides conceptual information on how Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary components in Nomad: jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.11.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.11.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..202383f8cd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Scheduling workloads
+description: Nomad's scheduling component assigns jobs to client machines. Explore scheduling internals, placement, and preemption.
+---
+
+# Scheduling workloads
+
+Scheduling workloads is the process of assigning tasks from jobs to client machines.
+It is one of Nomad's core functions. The design is heavily inspired by Google's
+work on both [Omega: flexible, scalable schedulers for large compute
+clusters][omega] and [Large-scale cluster management at Google with Borg][borg].
+Refer to the links below for implementation details on scheduling in Nomad.
+
+- [How scheduling works](/nomad/docs/concepts/scheduling/how-scheduling-works) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of
+  preemption, an advanced scheduler feature.
+- [Nomad job schedulers](/nomad/docs/concepts/scheduling/schedulers) - Explains the different types of job schedulers.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.11.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.11.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..59cedd36c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Allocation Placement
+description: Nomad uses allocation placement when scheduling jobs to run on clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+---
+
+# Allocation Placement
+
+This page provides conceptual information about job allocation placement on
+clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+## Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+## Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+## Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+## Understanding Evaluation Status
+
+When a job cannot be immediately placed, Nomad creates a chain of evaluations
+to manage placement. First, your initial evaluation may be marked complete even if
+placement fails. Then Nomad creates a blocked evaluation to retry placement when
+resources become available. Your job remains pending until Nomad places all allocations.
+
+For example, if your job has specific constraints that are not available, you
+get an initial completed evaluation and a blocked evaluation. Nomad tracks
+ongoing placement attempts until a node that fits your constraints is available.
+
+To troubleshoot placement issues, use `nomad eval status <eval_id>`. Check the output
+for placement failures and linked evaluations.
+
+[api_client_metadata]: /nomad/api-docs/client#update-dynamic-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/architecture/cluster/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.11.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.11.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..95a85738ee
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: Allocation Preemption
+description: Nomad uses preemption to evict existing allocations in order to place allocations for a higher priority job. Learn how Nomad uses job priority to preempt running allocations and how you can determine whether Nomad preempted an allocation. Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+---
+
+# Allocation Preemption
+
+This page provides conceptual information about preemption, which is evicting
+existing allocations in order to place allocations for a higher priority job.
+Learn how Nomad uses job priorty to determine when to preempt running
+allocations and how you can determine whether Nomad has preempted an allocation.
+Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+
+Preemption allows Nomad to kill existing allocations in order to place
+allocations for a higher priority job. The evicted allocation is temporarily
+displaced until the cluster has capacity to run it. This allows operators to run
+high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+## Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+## Details
+
+Preemption is enabled by default for system jobs. You can use the [scheduler
+config][sched-config-api] API endpoint or [`nomad operator scheduler
+set-config`][sched-config-cli] commands to disable preemption or enable it for
+other job types.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of 10 or greater compared to the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+## Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+## Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
+[sched-config-api]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[sched-config-cli]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.11.x/content/docs/concepts/scheduling/schedulers.mdx b/content/nomad/v1.11.x/content/docs/concepts/scheduling/schedulers.mdx
new file mode 100644
index 0000000000..95373cd979
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/scheduling/schedulers.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Nomad job schedulers
+description: Learn how Nomad's service, batch, system, and system batch job schedulers enable flexible workloads.
+---
+
+# Nomad job schedulers
+
+This page provides conceptual information about Nomad service, batch, system,
+and system batch job schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.11.x/content/docs/concepts/stateful-deployments.mdx b/content/nomad/v1.11.x/content/docs/concepts/stateful-deployments.mdx
new file mode 100644
index 0000000000..bff80bfd57
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/stateful-deployments.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: Stateful deployments
+description: |-
+  Learn how Nomad handles stateful deployments. Use a dynamic host volume for your stateful workload and bind an allocation to a volume ID with the sticky parameter. Learn how Nomad scales jobs with sticky volumes.
+---
+
+# Stateful deployments
+
+<Note>
+
+Stateful deployments support only dynamic host volumes. For CSI volumes, use the
+[`per_alloc` property](/nomad/docs/job-specification/volume#per_alloc),
+which serves a similar purpose.
+
+</Note>
+
+Nomad stateful deployments let you effectively bind your jobs to host [volumes].
+On a lower level, this means taking Nomad's basic unit of workload placement,
+the [allocation], and making it possible for you to have allocations that are
+[sticky] to volume IDs. Since stateful deployments only support dynamic host
+volumes, using them effectively means binding a job to a particular node.
+
+Stateful deployments work on a per-task-group basis. Use the `volume.sticky`
+parameter in your job specification to indicate that each task group requires a
+sticky host volume.
+
+This example sets the volume's `sticky` parameter to `true`.
+
+```hcl
+job "app" {
+  group "example" {
+    # ...
+    volume "example" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+      sticky    = true
+    }
+    # ...
+  }
+}
+```
+
+If you set the volume to sticky, during the deployment the scheduler associates
+its ID with the task group that uses it. Stateful deployments require that any
+allocations belonging to that task group must be places or replaced on nodes
+that have this volume ID available.
+
+Scaling jobs with sticky volumes up results in more volume IDs claimed by the
+task group, but scaling jobs down does not delete unused volumes, nor does it
+touch the data present on them.
+
+If the scheduler cannot find a node that has the right volume ID present,
+perhaps because the node is down or disconnected, Nomad creates a blocked
+evaluation.
+
+## Task group host volume claims
+
+Nomad uses its state store to save associations of host volume IDs and their
+task groups, as well as job IDs, volume names, and namespaces. Use the API to
+[list] and [delete] these associations. If you delete a task group host volume
+claim, Nomad assigns a different volume ID to the task group, assuming the old
+volume ID is unavailable and another feasible host volume with matching name is.
+However, after placement, Nomad once again records the claim in its state store.
+You should only use claim deletions in operational emergency situations or while
+debugging problems with nodes. For example, use claim deletions in situations
+where you want to drain a node with a stateful deployment on it, but do not want
+to stop the job.
+
+## Related resources
+
+Refer to the following Nomad pages for more information about stateful workloads
+and volumes:
+
+- [Considerations for Stateful Workloads](/nomad/docs/architecture/storage/stateful-workloads) explores the options for persistent storage of workloads running in Nomad.
+- The [Nomad volume specification][volumes] defines the schema for creating and registering volumes.
+- The [job specification `volume` block](/nomad/docs/job-specification/volume) lets you configure a group that requires a specific volume from the cluster.
+- The [Stateful Workloads](/nomad/docs/stateful-workloads) guides explore techniques to run jobs that require access to persistent storage.
+
+[allocation]: /nomad/docs/glossary#allocation
+[delete]: /nomad/api-docs/volumes#delete-task-group-host-volume-claims
+[list]: /nomad/api-docs/volumes#list-task-group-host-volume-claims
+[sticky]: /nomad/docs/job-specification/volume#sticky
+[volumes]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.11.x/content/docs/concepts/variables.mdx b/content/nomad/v1.11.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..170253c5e3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Nomad variables
+description: Nomad's variables feature lets you store and use encrypted configuration data in your job specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+---
+
+# Nomad variables
+
+This page contains conceptual information about the Nomad variables feature,
+which lets you store and use encrypted configuration data in your job
+specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+
+## Introduction
+
+Most Nomad workloads need access to configuration values or secrets. Nomad has a
+`template` block to [provide these values to
+tasks](/nomad/docs/job-specification/template#nomad-variables). Nomad variables
+provide the option to store configuration at file-like paths
+directly in Nomad's state store so that you can access these variables directly from
+your task templates. Nomad encrypts and replicates the contents of these variables between servers with Raft communication. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as variables. These should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. Refer to [Key Management][] for details.
+
+## Policies
+
+Every variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. Refer to the [ACL policy
+specification] for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include a wildcard symbol that allows
+a single path policy definition to apply to a set of paths within that
+namespace.
+
+In the following example, the policy allows full access to variables at all
+paths in the `dev` namespace that are prefixed with `project/`, including child
+paths, but only read access to paths prefixed with `system/`. Note that the wildcard
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with `system/` but not a path named `system` (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of variables at this path.                                                         |
+| destroy    | Delete variables at this path.                                                                                        |
+
+## Task access to variables
+
+Tasks can access variables with the [`template`] block or using the [Task API].
+The [workload identity] for each task grants it automatic read and list access to
+variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+## Locks
+
+Nomad provides the ability to block a variable from being updated for a period
+of time by setting a lock on it. Once a variable is locked, it can be read by
+everyone, but it can only be updated by the lock holder.
+
+The locks are designed to provide granular locking and are heavily inspired by
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems][].
+
+A lock is composed of an ID, a TTL, and a lock delay. The ID is generated by
+the Nomad Server and must be provided on every request to modify the variable's
+items or the lock itself. The TTL defines the time the lock will be held; if the
+lock needs to be in place for longer, it can be renewed for as many new periods
+as wanted.
+
+Once it is no longer needed, it must be released. If by the time the TTL expires,
+and no renew or release calls were made, the variable will remain locked for at
+least the lock delay duration, to avoid a possible split-brain situation, where
+there are two holders at the same time.
+
+### Leader election backed by Nomad variable locks
+
+For some applications, like HDFS or the Nomad Autoscaler, it is necessary to
+have multiple instances running to ensure redundancy in case of a failure, but
+only one of them may be active at a time as a leader.
+
+As part of the [Go Package][], Nomad offers a helper that takes one variable and
+uses a lock over it as a sync mechanism to run multiple instances but always
+keeping just one running at any given time, using the following algorithm:
+
+[![Leader Election Helper](/img/nomad-vars-leader-election-sdk.png)](/img/nomad-vars-leader-election-sdk.png)
+
+As soon as any instance starts, it tries to lock the sync variable. If it succeeds,
+it continues to execute while a secondary thread is in charge of keeping track of
+the lock and renewing it when necessary. If by any chance the renewal fails,
+the main process is forced to return, and the instance goes into standby until it
+attempts to acquire the lock over the sync variable.
+
+Only threads 1 and 3 or thread 2 are running at any given time, because every
+instance is either executing as normal while renewing the lock or waiting for a
+chance to acquire it and run.
+
+When the main process, or protected function, returns, the helper releases the
+lock, allowing a second instance to start running.
+
+To see it implemented live, look for the [`nomad var lock`][] command
+implementation or the [Nomad Autoscaler][] High Availability implementation.
+
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/manage/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems]: https://research.google/pubs/pub27897/
+[`nomad var lock`]: /nomad/commands/var
+[Go Package]: https://pkg.go.dev/github.com/hashicorp/nomad/api
+[implementation]: https://github.com/hashicorp/nomad/blob/release/1.7.0/command/var_lock.go#L240
+[Nomad Autoscaler]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.4.0/command/agent.go#L392
+[Task API]: /nomad/api-docs/task-api
diff --git a/content/nomad/v1.11.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.11.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..63e2ab3556
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Nomad's workload identity feature isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+---
+
+# Workload Identity
+
+This page provides conceptual information about Nomad's workload identity
+feature, which isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+
+Every workload running in Nomad is given a default identity. When an
+[allocation][] is accepted by the [plan applier][], the leader generates a
+Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring.
+Additional workload identities may be defined in tasks and services using the
+[`identity`][identity-block] block.
+
+## Workload Identity Claims
+
+Nomad workload identity for tasks include the following identity claims.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+Workload identities for Consul services have a claim with the service name
+instead of the task name.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Workload identities for tasks that use Vault have an additional claim for
+[`vault.role`][jobspec_vault_role] if a role is specified in the job.
+
+-> **Note:** This claim will *not* be added if the role is inherited from
+the [agent configuration][vault_role_agent_config] and is not present
+in the Nomad job specification.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_role": "nomad-jwt-login"
+}
+```
+
+### Nomad Enterprise <EnterpriseAlert inline />
+
+In Nomad Enterprise, tasks and services with a [`consul`][jobspec_consul] block
+that defines a [`namespace`][jobspec_consul_ns] value, or inside a `group`
+block that does it, have an additional claim called `consul_namespace`.
+
+```json
+{
+  "consul_namespace": "prod",
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Similarly, tasks with a [`vault.namespace`][jobspec_vault_ns] value have the additional claim
+`vault_namespace`.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_namespace": "prod"
+}
+```
+
+## Workload Identity for Nomad
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+### Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+### Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+You can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all jobs in the namespace by omitting the
+`-job`, `-group`, and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default redis-policy ./policy.hcl
+```
+
+### Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identity for Consul and Vault
+
+Consul and Vault can be configured to accept workload identities from Nomad for
+authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
+integration pages for more information.
+
+[allocation]: /nomad/docs/glossary#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[jobspec_consul]: /nomad/docs/job-specification/consul
+[jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace
+[jobspec_vault_ns]: /nomad/docs/job-specification/vault#namespace
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[vault_role_agent_config]: /nomad/docs/configuration/vault#create_from_role
+[plan applier]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[taskapi]: /nomad/api-docs/task-api
+[consul_int]: /nomad/docs/secure/acl/consul
+[vault_int]: /nomad/docs/secure/vault
diff --git a/content/nomad/v1.11.x/content/docs/configuration/acl.mdx b/content/nomad/v1.11.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..146a44c57b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block in Agent Configuration
+description: >-
+   Configure Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration. Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+---
+
+# acl Block in Agent Configuration
+
+<Placement groups={['acl']} />
+
+This page provides reference information for configuring Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration.  Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+
+Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/docs/secure/acl
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.11.x/content/docs/configuration/audit.mdx b/content/nomad/v1.11.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..418d5ee8f3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,302 @@
+---
+layout: docs
+page_title: audit Block in Agent Configuration
+description: >-
+  Configure audit logging behavior in the `audit` block of a Nomad agent configuration. Enable audit logs, define a sink to stream audit logs to, and change filter rules to exclude events from the audit log. Review example audit logs.
+---
+
+# `audit` Block in Agent Configuration
+
+<Placement groups={['audit']} />
+
+This page provides reference information for configuring audit logging behavior
+in the `audit` block of a Nomad agent configuration. Enable audit logs, define a
+sink to stream audit logs to, and change filter rules to exclude events from the
+audit log.
+
+<EnterpriseAlert product="nomad"/>
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Example audit logs
+
+The following audit log entries are for a request made to `/v1/job/web/summary`.
+The first entry is for the `OperationReceived` stage. The second entry is for
+the `OperationComplete` stage and includes the contents of the
+`OperationReceived` stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.11.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.11.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..18a90d3e12
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: autopilot Block in Agent Configuration
+description: >-
+  Configure settings for Nomad Autopilot features in the `autopilot` block of a Nomad agent configuration. Enable dead server cleanup, redundancy zones, and custom upgrades. Disable upgrade migration. Tune Raft settings for stable server introduction.
+---
+
+# `autopilot` Block in Agent Configuration
+
+<Placement groups={['autopilot']} />
+
+This page provides reference information for configuring settings for Nomad
+Autopilot features in the `autopilot` block of a Nomad agent configuration.
+Enable dead server cleanup, redundancy zones, and custom upgrades. Disable
+upgrade migration. Tune Raft settings for stable server introduction.
+
+Refer to the [Autopilot Guide](/nomad/docs/manage/autopilot) for
+how to configure and use Autopilot.
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - <EnterpriseAlert inline/> Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - <EnterpriseAlert inline/> Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - <EnterpriseAlert inline/> Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version)
+  parameter.
diff --git a/content/nomad/v1.11.x/content/docs/configuration/client.mdx b/content/nomad/v1.11.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..74274bc9bb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/client.mdx
@@ -0,0 +1,861 @@
+---
+layout: docs
+page_title: client Block in Agent Configuration
+description: |-
+  Configure a Nomad client in the `client` block of a Nomad agent configuration. Enable a client, configure allocation directories, artifact and template behavior, networking, node pools, servers to join, garbage collection, workload behavior, client resources, chroot, host volumes, host network, and driver-specific behavior.
+---
+
+# `client` Block in Agent Configuration
+
+<Placement groups={['client']} />
+
+This page provides reference information for configuring a Nomad client in the
+`client` block of a Nomad agent configuration. Enable a client, configure
+allocation directories, artifact and template behavior, networking, node pools,
+servers to join, garbage collection, workload behavior, client resources,
+chroot, host volumes, host network, and driver-specific behavior.
+
+Refer to the [Set Server and Client Nodes](/nomad/docs/deploy/nomad-agent)
+and [Nomad Agent](/nomad/commands/agent) pages to learn about the Nomad
+agent process and how to configure the server and client nodes in your cluster.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `alloc_mounts_dir` `(string: "")` - Specifies the directory to use for binding
+  mounts for the [unveil file isolation mode][unveil]. When this parameter is
+  empty, Nomad generates the path as a sibling of the [top-level
+  `data_dir`][top_level_data_dir], with the name `alloc_mounts`. For example, if
+  the `data_dir` is `/opt/nomad/data`, then the alloc mounts directory is
+  `/opt/nomad/alloc_mounts`. This must be an absolute path and should not be
+  inside the Nomad data directory. Nomad creates the directory on the host,
+  if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `preferred_address_family` `(string: "")` - Specifies the preferred address family
+  for the network interface. The value can be `ipv4` or `ipv6`. If the selected network
+  interface has both IPv4 and IPv6 addresses, this option will select an IP address of
+  the preferred family. When the option is not specified, the current behavior is conserved:
+  the first IP address is selected no matter the family.
+
+- `cpu_disable_dmidecode` `(bool: false)` - Specifies the client should not use dmidecode
+  as a method of cpu detection. Nomad ignores this field on all platforms except Linux.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_max_allocs` `(int: 0)` - Specifies the maximum number of allocations
+  that may be scheduled on a client node and is not enforced if unset. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations. Note
+  that Nomad immediately garbage collects terminal allocations if garbage
+  collected on the server.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations. Note
+  that Nomad immediately garbage collects terminal allocations if garbage
+  collected on the server.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd. Note that Nomad immediately garbage collects terminal
+  allocations if garbage collected on the server.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `gc_volumes_on_node_gc` `(bool: false)` - Specifies that the server should
+  delete any dynamic host volumes on this node when the node is garbage
+  collected. You should only set this to `true` if you know that garbage
+  collected nodes will never rejoin the cluster, such as with ephemeral cloud
+  hosts.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_subnet_ipv6` `(string: "")` - Enables IPv6 on Nomad's bridge
+  network by specifying the subnet which the client will use to allocate IPv6
+  addresses.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints. When hairpin mode
+  is enabled, allocations are able to reach their own IP and **all ports** bound
+  to it. Changing this value requires a reboot of the client host to take
+  effect.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `common_plugin_dir` `(string: "")` - Specifies the directory where you should
+  place plugins that conform to the [common plugins interface][common_plugins_interface]. When this
+  parameter is empty, Nomad generates the path using the [top-level
+  `data-dir`][top_level_data_dir] suffixed with `common_plugins`, like
+  `"/opt/nomad/common_plugins"`. This must be an absolute path.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_volumes_dir` `(string: "")` - Specifies the directory wherein
+  host volume plugins should place volumes. When this parameter is empty, Nomad
+  generates the path using the [top-level `data_dir`][top_level_data_dir]
+  suffixed with `host_volumes`, like `"/opt/nomad/host_volumes"`.
+  This must be an absolute path.
+
+- `host_volume_plugin_dir` `(string: "")` - Specifies the directory to find host
+  volume plugins. When this parameter is empty, Nomad generates the path
+  using the [top-level `data_dir`][top_level_data_dir] suffixed with
+  `host_volume_plugins`, like `"/opt/nomad/host_volume_plugins"`. This must be
+  an absolute path.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+- `users` <code>([Users](#users-block): nil)</code> - Specifies options
+  concerning Nomad client's use of operating system users.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/job-declare/task-driver/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/deploy/task-driver/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver,
+refer to the [drivers documentation](/nomad/docs/job-declare/task-driver).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers. If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers. If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of environment variable keys not to pass to these tasks.
+  Nomad passes the host environment variables to `exec`, `raw_exec` and `java`
+  tasks. If specified, the defaults are overridden. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  CONSUL_HTTP_TOKEN_FILE
+  NOMAD_TOKEN
+  VAULT_TOKEN
+  CONSUL_LICENSE
+  NOMAD_LICENSE
+  VAULT_LICENSE
+  CONSUL_LICENSE_PATH
+  NOMAD_LICENSE_PATH
+  VAULT_LICENSE_PATH
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  AWS_METADATA_URL
+  GOOGLE_APPLICATION_CREDENTIALS
+  GOOGLE_OAUTH_ACCESS_TOKEN
+  ```
+
+- `"user.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated denylist of usernames for which a task is not allowed to run.
+  This only applies if the driver is included in `"user.checked_drivers"`. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of drivers for which to enforce the `"user.denylist"`.
+  For drivers using containers, this enforcement is usually unnecessary. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled. A common use-case for the fingerprint denylist is to disable
+  fingerprinters of irrelevant cloud environments, which can slow down client
+  agent startup time.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "env_aws,env_gce,env_azure,env_digitalocean"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(string: "")` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separating the two inclusive ends. Refer to
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_artifact_inspection` `(bool: false)` - Specifies whether to disable
+  artifact inspection for sandbox escapes. If the platform supports filesystem
+  isolation, and it is not disabled, artifact inspection will not be performed
+  regardless of this value.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `filesystem_isolation_extra_paths` `([]string: nil)` - Allow extra paths
+  in the filesystem isolation. Paths are specified in the form `[kind]:[mode]:[path]`
+  where `kind` must be either `f` or `d` (file or directory) and
+  `mode` must be zero or more of `r`, `w`, `c`, `x` (read, write, create, execute) e.g.
+  `f:r:/dev/urandom` would enable reading the /dev/urandom file,
+  `d:rx:/opt/bin` would enable reading and executing from the /opt/bin directory
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "executeTemplate",
+  "writeToFile"])` - Specifies a list of template rendering functions that
+  should be disallowed in job specs.  By default the `plugin`, `executeTemplate`
+  and `writeToFile` functions are disallowed as they allow unrestricted root
+  access to the host or allow recursive execution.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. Setting
+  both `min` and `max` to `0` disables the feature. This configuration is also exposed
+  in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs. You can also
+configure [dynamic host volumes][] via the [`volume create`][] or [`volume
+register`][] commands.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type
+[`volume`](/nomad/docs/job-specification/volume) and ACLs. A host volume in the
+configuration cannot have the same name as a dynamic host volume on the same node.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path      = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr           = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+### `users` Block
+
+The `users` block controls aspects of Nomad client's use of operating system
+users.
+
+```hcl
+client {
+  users {
+    dynamic_user_min = 80000
+    dynamic_user_max = 89999
+  }
+}
+```
+
+- `dynamic_user_min` `(int: 80000)` - The lowest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+- `dynamic_user_max` `(int: 89999)` - The highest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values in the example are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task directories'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[unveil]: /nomad/plugins/author/task-driver#fsisolation-unveil
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[common_plugins_interface]: /nomad/plugins/author#common-plugin-interface
diff --git a/content/nomad/v1.11.x/content/docs/configuration/consul.mdx b/content/nomad/v1.11.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..8e76cf8e09
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,447 @@
+---
+layout: docs
+page_title: consul Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with Consul in the `consul` block of a Nomad agent configuration for service discovery and key-value integration. Configure cluster name, the Consul namespace, whether Nomad should advertize its services, certificates, tokens, security, health checks, auto join, and workload service and task identity.
+---
+
+# `consul` Block in Agent Configuration
+
+<Placement groups={['consul']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [Consul][consul] in the `consul` block of a Nomad agent
+configuration for service discovery and key-value integration. Configure cluster
+name, the Consul namespace, whether Nomad should advertize its services,
+certificates, tokens, security, health checks, auto join, and workload service
+and task identity.
+
+When configured, tasks can register themselves with Consul, and the Nomad
+cluster can [automatically bootstrap][bootstrap] itself.
+
+Refer to the [Service Discovery on Nomad
+tutorial](/nomad/tutorials/service-discovery) for how to use Consul's service
+discovery.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+In Nomad Enterprise, you may specify multiple `consul` blocks to configure
+access to multiple Consul clusters. Each Consul cluster must have a different
+value for the [`name`](#name) field.
+
+## `consul` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`consul.cluster`][] or [`service.cluster`][] fields. In Nomad
+  Community Edition, only the `"default"` cluster will be used, so this field
+  should be omitted.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the [Consul
+  namespace](/consul/docs/enterprise/namespaces) used by the Consul
+  integration. If non-empty, this namespace will be used on all Consul API calls
+  and for Consul service mesh configurations, unless overridden by the job's
+  [`consul.namespace`][] field. In Nomad Community Edition, only the `"default"`
+  namespace is used, so you should omit this field.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and client services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it defaults to Consul's anonymous policy,
+  which may or may not allow writes. Defaults to the `CONSUL_HTTP_TOKEN`
+  environment variable if set. Nomad cannot refresh this token; if the token is
+  deleted, Nomad is not able to communicate with Consul.
+
+  In Nomad Enterprise, if the Consul agent running alongside Nomad is in a
+  Consul Enterprise admin partition, you must create the Consul token provided
+  to the Nomad client in the same partition.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`][] set to `true`.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover Nomad servers in the same region by searching for the
+  Consul service name defined in the `server_service_name` option. The search
+  occurs if the client is not registered with any Nomad servers or it is unable
+  to heartbeat to the leader of the region, in which case it may be partitioned
+  and searches for other Nomad servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `client_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check is critical.
+
+- `client_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check shows a warning.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+  certificate used for communication between Connect sidecar proxies and Consul
+  agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+  <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. Refer to
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not
+  include the values for the ACL `token` or `auth`. This option should be
+  disabled in environments where Consul ACLs are not enabled.
+
+- `service_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for services.
+
+- `task_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for tasks.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `server_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check is critical.
+
+- `server_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check shows a warning.
+
+- `service_identity` <code>([Identity](#service_identity-parameters): nil)</code> - Specifies
+  a default Workload Identity to use when obtaining Service Identity tokens from
+  Consul to register services. Refer to [Workload Identity](#workload-identity)
+  for a recommended configuration.
+
+- `task_identity` <code>([Identity](#task_identity-parameters): nil)</code> - Specifies a
+  default Workload Identity to use when obtaining Consul tokens from Consul to
+  support [`template`][] blocks. Refer to [Workload
+  Identity](#workload-identity) for a recommended configuration.
+
+## Workload Identity
+
+The `service_identity` and `task_identity` blocks accept all the same values as
+the job specification's [`identity`][identity_block] (except that the
+`service_identity` ignores the `env` and `file` fields). By ensuring these
+blocks are set on the Nomad servers, you can automatically migrate your existing
+jobs to use Workload Identity without modifying the job specification and
+resubmitting them.
+
+The recommended configuration for `service_identity` and `task_identity` is as
+follows. Refer to [Migrating to Using Workload Identity with Consul][] for
+details on how to configure Consul to accept these identities. Note that the
+`ttl` field here refers to the TTL of the Nomad identity and not the Consul
+token.
+
+```hcl
+consul {
+  service_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+
+  task_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+}
+```
+
+### `service_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### `task_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN_consul_default` (or `NOMAD_TOKEN_consul_<name>` depending
+  on the [`name`](#name) field) environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_consul_default.jwt` (or
+  `secrets/nomad_consul_<name>.jwt` depending on the [`name`](#name) field). If
+  the [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul ACL policy for Nomad
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+### Consul Namespace <EnterpriseAlert inline/>
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace.
+
+This Consul policy shows an example policy configuration for a Nomad server.
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+### Consul Admin Partition <EnterpriseAlert inline/>
+
+In Nomad Enterprise, if the Consul agent running alongside Nomad is in a Consul
+Enterprise admin partition, you must create the Consul ACL token and ACL policy
+for Nomad clients in the same partition.
+
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/docs/deploy/clusters/connect-nodes 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`service.cluster`]: /nomad/docs/job-specification/service#cluster
+[identity_block]: /nomad/docs/job-specification/identity
+[`template`]: /nomad/docs/job-specification/template
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/v1.8.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[auth-method]: /consul/docs/security/acl/auth-methods/jwt
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[consul_bound_aud]: /consul/docs/security/acl/auth-methods/jwt#boundaudiences
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[consul_config_entry]: /consul/docs/connect/config-entries
diff --git a/content/nomad/v1.11.x/content/docs/configuration/index.mdx b/content/nomad/v1.11.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..95c0942d4d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/index.mdx
@@ -0,0 +1,428 @@
+---
+layout: docs
+page_title: Nomad agent configuration
+description: This section contains reference information for configuring Nomad agents. Learn how Nomad loads and merges multiple configuration files. Configure networking and advertise addresses, Nomad regions and datacenters, data directories, Consul integration, handshake limits, connections per client, logging, plugins, Sentinel policies, security, update check behavior, and Vault integration. Enable debugging, write to syslog, leave on interrupt or terminate, and cross-origin resource sharing (CORS).
+---
+
+# Nomad agent configuration
+
+This page provides an overview of reference information for configuring Nomad
+agents. Learn how Nomad loads and merges multiple configuration files. Configure
+networking and advertise addresses, Nomad regions and data centers, data
+directories, Consul integration, handshake limits, connections per client,
+logging, plugins, Sentinel policies, security, update check behavior, and Vault
+integration. Enable debugging, writing to syslog, leave on interrupt or
+terminate, and cross-origin resource sharing (CORS).
+
+Write configuration files in [HCL][hcl] or specify parameters as command-line
+flags. Nomad can read and combine parameters from multiple configuration files
+or directories to configure the Nomad agent.
+
+## Configuration file load order and merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## Configure plugin directories
+
+@include 'plugins/config-dirs.mdx'
+
+## General parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: refer to explanation)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  refer to the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: refer to explanation)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `eventlog` - This is a nested object that configures the behavior with
+  with Windows Event Log. The following parameters are available:
+
+  - `enabled` - Enable sending Nomad agent logs to the Windows Event Log.
+
+  - `level` -  `(string: "ERROR")` - Specifies the verbosity of logs the Nomad
+    agent outputs. Valid log levels include `ERROR`, `WARN`, or `INFO` in
+    increasing order of verbosity. Level must be of equal or less verbosity as
+    defined for the [`log_level`](#log_level) parameter.
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - This is a nested object that configures limits that are enforced by
+   the agent. The following parameters are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: refer to explanation)` - Specifies the network ports used for
+  different services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `rpc` `(`[`RPC`]`: nil)` - Specifies configuration which is specific to RPC.
+	We strongly recommend that you do not configure RPC values. Use the default
+	values, which have been production-proven on clusters of thousands of nodes.
+	You should only configure the `rpc` block if you have a specific reason to
+	believe it will improve your particular use case.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(refer to [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom region and datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`rpc`]: /nomad/docs/configuration/rpc
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.11.x/content/docs/configuration/keyring/awskms.mdx b/content/nomad/v1.11.x/content/docs/configuration/keyring/awskms.mdx
new file mode 100644
index 0000000000..70bfa1cd6b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/keyring/awskms.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: AWS Key Management Service (KMS) Keyring Configuration
+description: |-
+  Configure an AWS Key Management Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS authentication. Learn how Nomad supports KMS root key rotation.
+---
+
+# AWS Key Management Service (KMS) Keyring Configuration
+
+This page provides reference information for configuring an AWS Key Management
+Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent
+configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS
+authentication. Learn how Nomad supports KMS root key rotation.
+
+The AWS KMS keyring configures Nomad to use AWS KMS to wrap its keyring. This
+example shows configuring an AWS KMS keyring through the Nomad configuration
+file by providing all the required values.
+
+```hcl
+keyring "awskms" {
+  active = true
+  name   = "example"
+
+  # fields specific to awskms
+  region     = "us-east-1"
+  access_key = "AKIAIOSFODNN7EXAMPLE"
+  secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  kms_key_id = "19ec80b0-dfdd-4d97-8164-c6examplekey"
+  endpoint   = "https://vpce-0e1bb1852241f8cc6-pzi0do8n.kms.us-east-1.vpce.amazonaws.com"
+}
+```
+
+## `awskms` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `region` `(string: "us-east-1")`: The AWS region where the encryption key
+  lives. If not provided, may be populated from the `AWS_REGION` or
+  `AWS_DEFAULT_REGION` environment variables, from your `~/.aws/config` file, or
+  from instance metadata.
+
+- `access_key` `(string: <required>)`: The AWS access key ID to use. Alternately
+  specify via the `AWS_ACCESS_KEY_ID` environment variable or as part of the AWS
+  profile from the AWS CLI or instance profile.
+
+- `session_token` `(string: "")`: Specifies the AWS session token. Alternately
+  specify via the environment variable `AWS_SESSION_TOKEN`.
+
+- `secret_key` `(string: <required>)`: The AWS secret access key to
+  use. Alternately specify via the `AWS_SECRET_ACCESS_KEY` environment variable
+  or as part of the AWS profile from the AWS CLI or instance profile.
+
+- `kms_key_id` `(string: <required>)`: The AWS KMS key ID or ARN to use for
+  encryption and decryption. You can alternately use an alias in the format
+  `alias/key-alias-name`.
+
+- `endpoint` `(string: "")`: The KMS API endpoint for AWS KMS
+  requests. Alternately specify via the `AWS_KMS_ENDPOINT` environment
+  variable. This is useful, for example, when connecting to KMS over a [VPC
+  Endpoint][]. If not set, Nomad uses the default API endpoint for your region.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file allows you to pass in
+`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as part of the keyring block's
+parameters, we strongly recommended that you set these values via environment
+variables or instance profile.
+
+AWS authentication values:
+
+- `AWS_REGION` or `AWS_DEFAULT_REGION`
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
+
+Note: The client uses the official AWS SDK and the specified credentials,
+environment credentials, shared file credentials, or IAM role/ECS task
+credentials in that order, if you do not provide the aforementioned AWS-specific
+values. Refer to the [AWS SDK and Tools standard credentials][aws-std-creds]
+documentation.
+
+Nomad needs the following permissions on the KMS key:
+
+- `kms:Encrypt`
+- `kms:Decrypt`
+- `kms:DescribeKey`
+
+Grant these via IAM permissions on the principal that Nomad uses, on the KMS key
+policy for the KMS key, or via KMS Grants on the key.
+
+## Key rotation
+
+This keyring supports rotating the root keys defined in AWS KMS
+[doc][rotate_docs]. Both automatic rotation and manual rotation is supported for
+KMS since the key information is stored with the encrypted data. Old keys must
+not be disabled or deleted and are used to decrypt older data. Any new or
+updated data is encrypted with the current key defined in the keyring
+configuration or set to current under a key alias.
+
+[VPC Endpoint]: https://docs.aws.amazon.com/kms/latest/developerguide/kms-vpc-endpoint.html
+[rotate_docs]: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html
+[aws-std-creds]: https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html
diff --git a/content/nomad/v1.11.x/content/docs/configuration/keyring/azurekeyvault.mdx b/content/nomad/v1.11.x/content/docs/configuration/keyring/azurekeyvault.mdx
new file mode 100644
index 0000000000..7819d1e196
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/keyring/azurekeyvault.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Azure Key Vault Keyring Configuration
+description: >-
+  Configure an Azure Key Vault keyring in the `keyring "azurekeyvault"` block of a Nomad agent configuration. Configure the Key Vault resource's DNS, Azure Cloud environment variables and API endpoints, and vault and key names. Learn how Nomad supports rotating keys defined in Azure Key Vault.
+---
+
+# Azure Key Vault Keyring Configuration
+
+This page provides reference information for configuring an Azure Key Vault
+keyring in the `keyring "azurekeyvault"` block of a Nomad agent
+configuration. Configure the Key Vault resource's DNS, Azure Cloud environment
+API endpoints, vault and key names, tenant and client IDs, and the client secret. Learn how Nomad supports rotating keys defined in Azure Key
+Vault.
+
+The Azure Key Vault keyring configures Nomad to use Azure Key Vault to wrap its
+keyring. This example shows configuring Azure Key Vault keyring through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "azurekeyvault" {
+  active = true
+  name   = "example"
+
+  # fields specific to azurekeyvault
+  tenant_id      = "46646709-b63e-4747-be42-516edeaf1e14"
+  client_id      = "03dc33fc-16d9-4b77-8152-3ec568f8af6e"
+  client_secret  = "DUJDS3..."
+  vault_name     = "nomad"
+  key_name       = "nomad_key"
+}
+```
+
+## `azurekeyvault` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `tenant_id` `(string: <required>)`: The tenant id for the Azure Active
+  Directory organization. Alternately specify via the `AZURE_TENANT_ID`
+  environment variable.
+
+- `client_id` `(string: <required or MSI>)`: The client id for credentials to
+  query the Azure APIs. Alternately specify via the `AZURE_CLIENT_ID`
+  environment variable.
+
+- `client_secret` `(string: <required or MSI>)`: The client secret for
+  credentials to query the Azure APIs. Alternately specify via the
+  `AZURE_CLIENT_SECRET` environment variable.
+
+- `environment` `(string: "AZUREPUBLICCLOUD")`: The Azure Cloud environment API
+  endpoints to use. Alternately specify via the `AZURE_ENVIRONMENT` environment
+  variable.
+
+- `vault_name` `(string: <required>)`: The Key Vault vault to use the encryption
+  keys for encryption and decryption.
+
+- `key_name` `(string: <required>)`: The Key Vault key to use for encryption and
+  decryption.
+
+- `resource` `(string: "vault.azure.net")`: The Key Vault resource's DNS
+  Suffix to connect to. Alternately specify via the `AZURE_AD_RESOURCE`
+  environment variable. Needs to be changed to connect to Azure's Managed HSM
+  KeyVault instance type.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+Azure authentication values:
+
+- `AZURE_TENANT_ID`
+- `AZURE_CLIENT_ID`
+- `AZURE_CLIENT_SECRET`
+- `AZURE_ENVIRONMENT`
+- `AZURE_AD_RESOURCE`
+
+~> **Note:** If Nomad is hosted on Azure, Nomad can use Managed Service
+Identities (MSI) to access Azure instead of an environment and shared client id
+and secret. MSI must be [enabled][msi_enabled] on the VMs hosting Nomad. We
+recommend this configuration since MSI prevents your Azure credentials from
+being stored as clear text.
+
+-> **Note:** If you are using a Managed HSM KeyVault, you must specify
+`AZURE_AD_RESOURCE` or the `resource` configuration parameter; usually this
+should point to `managedhsm.azure.net` but could point to other suffixes
+depending on Azure environment.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Azure Key Vault. Key metadata is
+stored with the encrypted data to ensure the correct key is used during
+decryption operations. Set up Azure Key Vault with [key rotation][] using Azure
+Automation Account so Vault recognizes newly rotated keys.
+
+[msi_enabled]: https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm
+[key rotation]: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-key-rotation-log-monitoring
diff --git a/content/nomad/v1.11.x/content/docs/configuration/keyring/gcpckms.mdx b/content/nomad/v1.11.x/content/docs/configuration/keyring/gcpckms.mdx
new file mode 100644
index 0000000000..00ad5ff915
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/keyring/gcpckms.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: Google Cloud Platform Key Management Service Keyring Configuration
+description: >-
+  Configure a Google Cloud Platform Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block of a Nomad agent configuration. Configure GCP credentials, project, region, key ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP Cloud KMS.
+---
+
+# Google Cloud Platform Key Management Service Keyring Configuration
+
+This page provides reference information for configuring a Google Cloud Platform
+Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block
+of a Nomad agent configuration. Configure GCP credentials, project, region, key
+ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP
+Cloud KMS.
+
+The GCP Cloud KMS keyring configures Nomad to use GCP Cloud KMS to wrap its
+keyring. This example shows configuring GCP Cloud KMS keyring through the Nomad
+configuration file by providing all the required values.
+
+```hcl
+keyring "gcpckms" {
+  active = true
+  name   = "example"
+
+  credentials = "/etc/nomad.d/nomad-user-creds.json"
+  project     = "nomad-project"
+  region      = "global"
+  key_ring    = "nomad-keyring"
+  crypto_key  = "nomad-key"
+}
+```
+
+## `gcpckms` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `credentials` `(string: <required>)`: The path to the credentials JSON file to
+  use. Alternately specify via the `GOOGLE_CREDENTIALS` or
+  `GOOGLE_APPLICATION_CREDENTIALS` environment variable or set automatically if
+  running under Google Compute Engine.
+
+- `project` `(string: <required>)`: The GCP project ID to use. Alternately
+  specify via the `GOOGLE_PROJECT` environment variable.
+
+- `region` `(string: <required>)`: The GCP region/location where the key ring
+  lives. Alternately specify via the `GOOGLE_REGION` environment variable.
+
+- `key_ring` `(string: <required>)`: The GCP KMS key ring to use.
+
+- `crypto_key` `(string: <required>)`: The GCP KMS crypto key to use for
+  encryption and decryption.
+
+## Authentication &amp; permissions
+
+You must provide authentication-related values either as environment
+variables or as configuration parameters.
+
+GCP authentication values:
+
+- `GOOGLE_CREDENTIALS` or `GOOGLE_APPLICATION_CREDENTIALS`
+- `GOOGLE_PROJECT`
+- `GOOGLE_REGION`
+
+Note: The client uses the official Google SDK and the specified credentials,
+environment credentials, or [application default credentials][] in that order,
+if you do not provide the aforementioned GCP-specific values.
+
+The service account needs the following minimum permissions on the crypto key:
+
+```text
+cloudkms.cryptoKeyVersions.useToEncrypt
+cloudkms.cryptoKeyVersions.useToDecrypt
+cloudkms.cryptoKeys.get
+```
+
+These permissions can be described with the following role:
+
+```text
+roles/cloudkms.cryptoKeyEncrypterDecrypter
+cloudkms.cryptoKeys.get
+```
+
+Use `cloudkms.cryptoKeys.get` permission for retrieving metadata information of
+keys from CloudKMS within this engine initialization process.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Google Cloud KMS
+[doc][rotating_keys]. Both scheduled rotation and manual rotation is supported
+for CKMS since the key information. Old keys version must not be disabled or
+deleted and are used to decrypt older data. Any new or updated data is encrypted
+with the primary key version.
+
+
+[application default credentials]: https://developers.google.com/identity/protocols/application-default-credentials
+[rotating_keys]: https://cloud.google.com/kms/docs/rotating-keys
diff --git a/content/nomad/v1.11.x/content/docs/configuration/keyring/index.mdx b/content/nomad/v1.11.x/content/docs/configuration/keyring/index.mdx
new file mode 100644
index 0000000000..a708548cd5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/keyring/index.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: keyring Block in Agent Configuration
+description: >-
+  Configure keyring protection behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring and configure a name. Learn how to configure keyring high availability (HA) and migrate keyrings.
+---
+
+# `keyring` Block in Agent Configuration
+
+<Placement groups={['keyring']} />
+
+This page provides reference information for configuring keyring protection
+behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring
+and configure a name. Learn how to configure keyring high availability (HA) and
+migrate keyrings.
+
+The `keyring` block configures how the Nomad server protects the keyring used
+for encrypting [variables][] and signing [workload identities][]. By default,
+Nomad encrypts the key material with a unique key encryption key (KEK) that is
+not shared between servers, and writes the wrapped key material to disk as
+described in [Key Management][]. Nomad refers to this as `"aead"` (authenticated
+encryption with associated data). Using the `keyring` configuration block, Nomad
+servers can instead use an external key management system (KMS) or Vault transit
+encryption. The encrypted key is stored on disk but is now protected against
+offline attacks because the KEK is not present in the file.
+
+All `keyring` blocks require a label for the KMS type. Each external KMS has its
+own configuration options. The `keyring` block only applies to Nomad servers,
+not Nomad clients.
+
+```hcl
+keyring [TYPE] {
+  name   = "example"
+  active = true
+}
+```
+
+The default `keyring` configuration is as follows:
+
+```hcl
+keyring "aead" {
+  active = true
+}
+```
+
+## `keyring` Parameters
+
+All `keyring` blocks support the following parameters.
+
+- `name` `(string: "")` - A unique identifier for the `keyring` block, used to
+  disambiguate when there are multiple blocks of the same type.
+
+- `active` `(bool: false)` - Indicates which block to use for encrypting
+  keys. For existing servers, changing which block is `active` only impacts new
+  keys created by a [key rotation][]. Existing keys are encrypted with the
+  previous `active` block, so those blocks should not be removed from the
+  configuration until they have been garbage collected and the keys have been
+  removed from the keystore. In Nomad Community Edition, only a single keyring
+  can be `active` at a time.
+
+## Migrating Keyrings
+
+To migrate to a new keyring, add the new `keyring` block to the servers with
+`active=true`, and restart the servers. The server starts using the new keyring
+wrapper when the current key is rotated either periodically or via the [`nomad
+operator root keyring rotate`][keyring_rotate_cmd] command.
+
+Adding or removing a keyring requires restarting the Nomad server. You should
+not remove a keyring until all keys it wraps have been garbage collected. You
+can examine the contents of the `keystore` directory found in the Nomad server's
+data directory and compare this against the output of [`nomad operator root
+keyring list`][keyring_list_cmd].
+
+## High Availability
+
+<EnterpriseAlert product="nomad"/>
+
+Keyring high availability provides the means to configure multiple active
+`keyring` blocks, in order to have resilience against an outage of an external
+KMS. When there are multiple `keyring` blocks with `active = true`, Nomad
+Enterprise encrypts each key it creates in all the active KMS providers. On
+startup, Nomad tries each KMS provider in order until it finds a provider that
+can decrypt each key.
+
+In this example high availability configuration, both `keyring` blocks use the
+`"awskms"` provider, but each block uses a different KMS key in a different AWS
+region.
+
+```hcl
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-1"
+  region     = "us-east-1"
+  kms_key_id = "arn:aws:kms:us-east-1:000000000000:key/7d23633a-4464-11ef-a273-abd12example"
+}
+
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-2"
+  region     = "us-east-2"
+  kms_key_id = "alias/nomad-keyring-us-east-2"
+}
+```
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[Key Management]: /nomad/docs/manage/key-management
+[key rotation]: /nomad/docs/manage/key-management#key-rotation
+[keyring_rotate_cmd]: /nomad/commands/operator/root/keyring-rotate
+[keyring_list_cmd]: /nomad/commands/operator/root/keyring-list
diff --git a/content/nomad/v1.11.x/content/docs/configuration/keyring/transit.mdx b/content/nomad/v1.11.x/content/docs/configuration/keyring/transit.mdx
new file mode 100644
index 0000000000..544ee23f9d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/keyring/transit.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: Vault Transit Keyring Configuration
+description: |-
+  Configure a Vault transit secrets engine keyring in the `keyring "transit"` block of a Nomad agent configuration. Configure the address to the Vault cluster, key name, mount path, namespace, TLS authentication, and whether to disable Vault token automatic renewal. Learn how Nomad supports rotating keys defined in Vault's transit secrets engine.
+---
+
+# Vault Transit Keyring Configuration
+
+This page provides reference information for configuring a Vault transit secrets
+engine keyring in the `keyring "transit"` block of a Nomad agent configuration.
+Configure the address to the Vault cluster, key name, mount path, namespace, TLS
+authentication, and whether to disable Vault token automatic renewal. Learn how
+Nomad supports rotating keys defined in Vault's transit secrets engine.
+
+The Vault transit keyring configures Nomad to use Vault's transit secrets engine
+to wrap its keyring. This example shows configuring Vault transit through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "transit" {
+
+  active = true
+  name   = "example"
+
+  # fields specific to transit
+  address            = "https://vault:8200"
+  token              = "s.Qf1s5zigZ4OX6akYjQXJC1jY"
+  disable_renewal    = "false"
+
+  # Key configuration
+  key_name           = "transit_key_name"
+  mount_path         = "transit/"
+  namespace          = "ns1/"
+
+  # TLS Configuration
+  tls_ca_cert        = "/etc/vault/ca_cert.pem"
+  tls_client_cert    = "/etc/vault/client_cert.pem"
+  tls_client_key     = "/etc/vault/ca_cert.pem"
+  tls_server_name    = "vault"
+  tls_skip_verify    = "false"
+}
+```
+
+## `transit` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `key_name` `(string: <required>)`: The transit key to use for encryption and
+  decryption.
+
+- `key_id_prefix` `(string: "")`: An optional string to add to the key id of
+  values wrapped by this transit keyring. This can help disambiguate between two
+  transit keyring.
+
+- `mount_path` `(string: <required>)`: The mount path to the transit secret
+  engine.
+
+- `disable_renewal` `(string: "false")`: Disables the automatic renewal of the
+  token in case the lifecycle of the token is managed with some other mechanism
+  outside of Vault, such as Vault Agent.
+
+Set the following parameters in the `keyring` block. If not set here, Nomad uses
+the values set in the server's [`vault`][vault_config] block. You must set
+required fields either here or the `vault` block.
+
+- `address` `(string: <required>)`: The full address to the Vault cluster.
+  Alternately specify via the `VAULT_ADDR` environment variable.
+
+- `token` `(string: <required>)`: The Vault token to use. Alternately specify
+  via the `VAULT_TOKEN` environment variable.
+
+- `namespace` `(string: "")`: The namespace path to the transit secret engine.
+   Alternately specify via the `VAULT_NAMESPACE` environment variable.
+
+- `tls_ca_cert` `(string: "")`: Specifies the path to the CA certificate file
+  used for communication with the Vault server. Alternately specify via the
+  `VAULT_CACERT` environment variable.
+
+- `tls_client_cert` `(string: "")`: Specifies the path to the client certificate
+  for communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_CERT` environment variable.
+
+- `tls_client_key` `(string: "")`: Specifies the path to the private key for
+  communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_KEY` environment variable.
+
+- `tls_server_name` `(string: "")`: Name to use as the SNI host when connecting
+  to the Vault server via TLS. Alternately specify via the
+  `VAULT_TLS_SERVER_NAME` environment variable.
+
+- `tls_skip_verify` `(bool: "false")`: Disable verification of TLS certificates.
+  Using this option is highly discouraged and decreases the security of data
+  transmissions to and from the Vault server. Alternately specify via the
+  `VAULT_SKIP_VERIFY` environment variable.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file lets you to pass in `VAULT_TOKEN`
+as part of the keyring's parameters, we strongly recommended that you set these
+values via environment variables.
+
+The Vault authentication token needs the following permissions on the transit
+key:
+
+```hcl
+path "<mount path>/encrypt/<key name>" {
+  capabilities = ["update"]
+}
+
+path "<mount path>/decrypt/<key name>" {
+  capabilities = ["update"]
+}
+```
+
+Other considerations for the token used:
+* It should probably be an [orphan token][], otherwise when the parent token
+  expires or gets revoked the keyring breaks.
+* Consider making it a [periodic token][] and not setting an explicit max TTL,
+  otherwise at some point it ceases to be renewable.
+
+## Key rotation
+
+This keyring supports key rotation using Vault's transit secrets engine's key
+rotation endpoints. Refer to [Vault docs][rotate_doc] for details. Old keys must
+not be disabled or deleted and are used to decrypt older data.
+
+[orphan token]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens
+[periodic token]: /vault/docs/concepts/tokens#periodic-tokens
+[rotate_doc]: /vault/api-docs/secret/transit#rotate-key
+[vault_config]: https://developer.hashicorp.com/nomad/docs/configuration/vault
diff --git a/content/nomad/v1.11.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.11.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..d3d5d4d4a8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: plugin Block in Agent Configuration
+description: Configure task driver and device driver plugins in the `plugin` block of a Nomad agent configuration. Specify arguments to pass to the plugin. Configure values specific to the plugin.
+---
+
+# `plugin` Block in Agent Configuration
+
+<Placement groups={['plugin']} />
+
+This page provides reference information for configuring task driver and device
+driver plugins in the `plugin` block of a Nomad agent configuration. Specify
+arguments to pass to the plugin. Configure values specific to the plugin.
+
+Refer to the [Nomad plugins guide](/nomad/plugins) for details on specific task
+driver and device plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.11.x/content/docs/configuration/reporting.mdx b/content/nomad/v1.11.x/content/docs/configuration/reporting.mdx
new file mode 100644
index 0000000000..c09d679bd9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/reporting.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: reporting Block in Agent Configuration
+description: >-
+  Enable automated license utilization reporting in the `reporting` block of a Nomad agent configuration. Configuration applies to agents running Nomad Enterprise with server mode enabled.
+---
+
+# `reporting` Block in Agent Configuration
+
+<Placement groups={['reporting']} />
+
+This page provides reference information for enabling automated license
+utilization reporting in the `reporting` block of a Nomad agent configuration.
+
+<EnterpriseAlert/>
+
+Configuration applies to agents running with [server mode
+enabled][server_mode_enabled].
+
+Refer to the [Automated license utilization reporting
+guide][automated_license_utilization_reporting] for which ports to open and what
+data is shared.
+
+```hcl
+reporting {
+  license {
+    enabled = true
+  }
+
+  snapshot_retention_time = "9600h"
+}
+```
+
+## `reporting` Parameters
+
+- `license` <code>([license](#license-block): default)</code> - Configures
+  automated license utilization reporting.
+
+- `snapshot_retention_time` `(string: "9600h")` - Configures the maximum amount
+  of time that Nomad retains a utilization reporting snapshot in the Nomad
+  state store. You can export these snapshots with the [`nomad operator
+  utilization`][] command.
+
+- `disable_product_usage_reporting` `(bool: false)` - Specifies whether detailed
+  product usage metrics should be disabled. Review the
+  [full list of metrics](/nomad/docs/enterprise/license/utilization-reporting#full-list-of-metrics)
+  before disabling this option, and share any concerns you may have
+  with your account manager.
+
+## `license` Block
+
+- `enabled` `(bool: true)` - Specifies whether automated license utilization
+  reporting should be enabled and run. License utilization metrics are still
+  gathered for offline reporting.
+
+[server_mode_enabled]: /nomad/docs/configuration/server#enabled
+[automated_license_utilization_reporting]: /nomad/docs/enterprise/license/utilization-reporting
+[`nomad operator utilization`]: /nomad/commands/operator/utilization
diff --git a/content/nomad/v1.11.x/content/docs/configuration/rpc.mdx b/content/nomad/v1.11.x/content/docs/configuration/rpc.mdx
new file mode 100644
index 0000000000..e14204e857
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/rpc.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: rpc Block in Agent Configuration
+description: >-
+   Configure Nomad's RPC behavior in the `rpc` block of a Nomad agent configuration. Modify RPC session configuration, change stream accept backlog, keepalive interval, and open stream timeouts.
+---
+
+# rpc Block in Agent Configuration
+
+<Placement groups={['rpc']} />
+
+This page provides reference information for configuring Nomad's RPC behavior in
+the `rpc` block of a Nomad agent configuration. Modify RPC session
+configuration, stream accept backlog, keepalive interval, and open stream
+timeouts. We strongly recommend leaving these values unconfigured to use the
+default values, which have been production-proven on clusters of thousands of
+nodes. You should only configure the `rpc` block if you have specific reason to
+believe it will improve your specific use case.
+
+```hcl
+rpc {
+  accept_backlog           = 256
+  keep_alive_interval      = "30s"
+  connection_write_timeout = "10s"
+  max_stream_window_size   = 262144
+  stream_open_timeout      = "75s"
+  stream_close_timeout     = "5m"
+}
+```
+
+## `rpc` Parameters
+
+- `accept_backlog` `(int: 256)` - Limits how many RPC streams
+  (requests) can be waiting for acceptance by the RPC server.
+
+- `keep_alive_interval` `(string: 30s)` - How often to perform the keep alive
+
+- `connection_write_timeout` `(string: 10s)` - Safety valve timeout after which
+  you should suspect a problem with the underlying connection and close it. This
+  is only applied to writes, where there is generally an expectation that things
+  move along quickly.
+
+- `max_stream_window_size` `(int: 262144)` - Controls the maximum window size
+  allowed for a stream, in bytes.
+
+- `stream_open_timeout` `(string: 75s)` - Maximum amount of time that a stream
+  remains in pending state while waiting for an ACK from the peer. Once the
+  timeout is reached, Nomad gracefully closes the session. A zero value disables
+  the stream open timeout, allowing unbounded blocking on open stream calls.
+
+- `stream_close_timeout` `(string: 5m)` - When `close` is called, maximum time
+  that a stream is in a half-closed state before forcibly closing the
+  connection. Forcibly closed connections empty the receive buffer, drop any
+  future packets received for that stream, and send an RST to the remote side.
diff --git a/content/nomad/v1.11.x/content/docs/configuration/search.mdx b/content/nomad/v1.11.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..526e0d11c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/search.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: search Block in Agent Configuration
+sidebar_title: search
+description: >-
+  Configure the Nomad server search API in the `search` block of a Nomad agent configuration. Enable fuzzy searching. Configure the minimum size of the search term, the maximum number of Nomad objects to search through per context type, and the max number of matching results.
+---
+
+# `search` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+This page provides reference information for configuring the Nomad server search
+API in the `search` block of a Nomad agent configuration. Enable fuzzy
+searching. Configure the minimum size of the search term, the maximum number of
+Nomad objects to search through per context type, and the max number of matching results.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.11.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.11.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..a41b6ef14e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: sentinel Block in Agent Configuration
+description: >-
+  Configure Sentinel policy engine behavior in the "sentinel" block of a Nomad agent configuration. Configure the path to the plugin that Nomad uses to import Sentinel policies and specify arguments to pass to that plugin on startup.
+---
+
+# `sentinel` Block in Agent Configuration
+
+<Placement groups={['sentinel']} />
+
+This page provides reference information for configuring the Sentinel policy
+engine in the `sentinel` block of a Nomad agent configuration. Configure the
+path to the plugin that Nomad uses to import Sentinel policies and specify
+arguments to pass to that plugin on startup.
+
+<EnterpriseAlert/>
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
+
+## Resources
+
+Refer to these resources for details on using Sentinel policies with
+Nomad:
+
+- [Governance and policy on
+  Nomad](/nomad/docs/govern)
+- [Sentinel policies](/nomad/docs/govern/sentinel)
+- [Sentinel policy
+  reference](https://developer.hashicorp.com/nomad/docs/reference/sentinel-policy)
+
+
+
diff --git a/content/nomad/v1.11.x/content/docs/configuration/server.mdx b/content/nomad/v1.11.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..a1af96ddb0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/server.mdx
@@ -0,0 +1,587 @@
+---
+layout: docs
+page_title: server Block in Agent Configuration
+description: |-
+  Configure Nomad agent server mode in the `server` block of a Nomad agent configuration. Server mode lets the agent participate in scheduling decisions, register with service discovery, and handle join failures. Configure bootstrapping, authoritative region, redundancy zone, data directory, Nomad cluster behavior, client heartbeat period, schedulers, garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity, leader plan rejection, as well as job priority, job source content size, and tracked job versions.
+---
+
+# `server` Block in Agent Configuration
+
+<Placement groups={['server']} />
+
+This page provides reference information for configuring Nomad agent server mode
+in the `server` block of a Nomad agent configuration. Server mode lets the agent
+participate in scheduling decisions, register with service discovery, and handle
+join failures. Configure bootstrapping, authoritative region, redundancy zone,
+data directory, Nomad cluster behavior, client heartbeat period, schedulers,
+garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity,
+and leader plan rejection, as well as job priority, job source content size, and
+tracked job versions.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens in multi-region, federated deployments.
+  Non-authoritative regions will replicate from the authoritative to act as a
+  mirror. By default, the local region is assumed to be authoritative. Setting
+  `authoritative_region` assumes that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [])` - Specifies which sub-schedulers
+  this server  handles. Use this to restrict the evaluations that worker threads
+  dequeue for processing. Nomad treats the empty default value as `["service",
+  "batch", "system", "sysbatch"]`.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. Refer to the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m".
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via
+  `batch_eval_gc_threshold`. Nomad garbage collects allocations with their
+  evaluations, so this field also controls server garbage collection of
+  allocations. Evaluations with non-terminal allocations cannot be garbage
+  collected.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold. Allocations are garbage collected with their
+  evaluations, so this field also controls server garbage collection of
+  allocations. Evaluations with non-terminal allocations cannot be garbage
+  collected.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `client_introduction` <code>([ClientIntroduction](#client_introduction-parameters))</code> -
+  Configuration for how the Nomad server handles client introduction
+  requests.
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>(<a href="/nomad/api-docs/operator/scheduler#update-scheduler-configuration">scheduler_configuration:</a></code>`nil`) - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is
+  bootstrapped or value is updated through the [API
+  endpoint][update-scheduler-config]. Refer to [the example
+  section](#configuring-scheduler-config) for more details.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". Refer to the [Client Heartbeats](#client-heartbeats) section for
+  details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients must
+  heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described in the following paragraph. Lower values are used to
+  tighten timing and increase sensitivity while higher values relax timings and
+  reduce sensitivity. Tuning this affects the time it takes Nomad to detect
+  leader failures and to perform leader elections, at the expense of requiring
+  more network and CPU resources for better performance. The maximum allowed
+  value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/reference/metrics) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, refer to the [Autopilot Guide](/nomad/docs/manage/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key from the [JWKS URL][] before
+  it is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. Refer to the [server_join documentation][server-join] for more detail.
+
+- `start_timeout` `(string: "30s")` - A timeout applied to the server setup and
+  startup processes. These processes (keyring decryption) are expected to
+  complete before the server is considered healthy, and if the timeout is
+  reached before they are completed, the server will exit. Without this, the
+  server can hang indefinitely waiting for these.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, refer to the [Autopilot Guide](/nomad/docs/manage/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_count` `(int: 50000)` - Specifies the maximum number of allocations
+   for a job, as represented by the sum of its task group `count` fields. Jobs
+   of type `system` ignore this value. The child jobs of dispatched batch jobs
+   or periodic jobs are counted separately from their parent job. This value
+   must be non-negative. If set to 0, no limit is enforced. This value is enforced
+   at the time the job is submitted or scaled, and updating the value will not
+   impact existing jobs.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+- `oidc_issuer` `(string: "")` - Specifies the Issuer URL for [Workload
+    Identity][wi] JWTs. For example, `"https://nomad.example.com"`. If set the
+    `/.well-known/openid-configuration` HTTP endpoint is enabled for third
+    parties to discover Nomad's OIDC configuration.  Once set `oidc_issuer`
+    *cannot be changed* without invalidating Workload Identities that have the
+    old issuer claim. For this reason it is suggested to set `oidc_issuer` to a
+    proxy in front of Nomad's HTTP API to ensure a stable DNS name can be used
+    instead of a potentially ephemeral Nomad server IP.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. Refer to the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. Refer to the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `client_introduction` Parameters
+
+The `client_introduction` block controls how the Nomad server should generate
+introduction tokens for new clients and what enforcement to apply when new
+clients attempt to register with the server.
+
+- `enforcement` `(string: "warn")` - Specifics how the server handles new client
+  registration requests. The valid options are `none`, `warn`, and `strict`.
+
+  - `none`: The server does not enforce any client registration behaviour.
+  - `warn`: The server logs a warning message and emits a telemetry metric when
+    a client attempts to register without an introduction token. However, the
+    server does allow the registration to proceed.
+  - `strict`: The server rejects any client registration attempts that do not
+    include a valid introduction token. The server also logs a warning message
+    and emits a telemetry  metric.
+
+- `default_identity_ttl` `(string: "5m")` - The default TTL assigned to
+  generated client introduction tokens when the caller does not specify a TTL.
+  Specify this value with a label suffix like "30s" or "1h". Must be less
+  than `max_identity_ttl`.
+
+- `max_identity_ttl` `(string: "30m")` - The maximum TTL that can be requested
+  by a caller when generating client introduction tokens. Specify this value
+  with a label suffix like "30s" or "1h". Must be greater than
+  `default_identity_ttl`.
+
+Refer to the [Client introduction section][monitoring_nomad_client_introduction]
+of the Monitor Nomad guide for details on the client introduction metric that is
+emitted.
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, refer to the
+[automatic Nomad bootstrapping documentation](/nomad/docs/deploy/clusters/connect-nodes).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`disconnect.lost_after`][disconnect.lost_after] is set)
+and replaced.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer Nomad takes to replace a `down`
+  Client's workload.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  replaced.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO                   |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and replaces their
+work.
+
+[encryption]: /nomad/docs/secure/traffic/gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]:/nomad/docs/monitor#progress
+[`nomad operator gossip keyring generate`]: /nomad/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/manage/key-management
+[disconnect.lost_after]: /nomad/docs/job-specification/disconnect#lost_after
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[wi]: /nomad/docs/concepts/workload-identity
+[Configure for multiple regions]: /nomad/docs/secure/acl/bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[JWKS URL]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[monitoring_nomad_client_introduction]:/nomad/docs/monitor#client-introduction
diff --git a/content/nomad/v1.11.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.11.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..a9935bf3f8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: server_join Block in Agent Configuration
+description: >-
+  Configure how Nomad agents discover and connect to Nomad servers in Amazon, Microsoft, and Google clouds as well as on-prem. Use the`server_join` block to configure the list of servers to join, retry interval, and max rejoin attempts.
+---
+
+# `server_join` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+This page provides reference information for configuring how Nomad agents
+discover and connect to Nomad servers in Amazon, Microsoft, and Google
+clouds as well as on-prem. Use the`server_join` block to configure the list of
+servers to join, retry interval, and max rejoin attempts.
+
+```hcl
+server_join {
+  retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max      = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of Nomad server
+  addresses and [Cloud Auto-join](#cloud-auto-join) configurations that are
+  joined as cluster members. This is similar to [`start_join`](#start_join),
+  but join attempts are retried up to [retry_max](#retry_max) times.
+  Further, `retry_join` is available to both Nomad servers and clients, while
+  `start_join` is only defined for Nomad servers. This is useful for cases where
+  we know the address will become available eventually. Use `retry_join` with an
+  array as a replacement for `start_join`, **do not use both options**.
+
+  Server addresses must conform to the [server address format](#server-address-format).
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Auto-join configurations must conform to the [Cloud Auto-join format](#cloud-auto-join).
+
+  Cloud-Auto join using `go-discover` to join an AWS EC2 cluster.
+
+  ```hcl
+  server_join {
+    retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Cloud-Auto join using `go-netaddrs` to join a Hetzner cluster of servers
+  labeled with `nomad-server=true` using the `hcloud` CLI.
+
+  ```hcl
+  server_join {
+    retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+  }
+  ```
+
+  Server addresses and Cloud Auto-join configurations may be used together.
+  This is a mixed configuration containing a server address and Cloud Auto-join
+  configuration.
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Refer to [server address format](#server-address-format) for more information
+  about expected server address formats and [Cloud Auto-join](#cloud-auto-join)
+  for more information on expected Cloud Auto-join formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+`retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud provider metadata. Refer to [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+`retry_join`'s Cloud Auto-join allows Nomad to automatically discover cluster
+server addresses using cloud provider metadata. Cloud Auto-join allows both
+[go-discover](https://github.com/hashicorp/go-discover) and
+[go-netaddrs](https://github.com/hashicorp/go-netaddrs) formats.
+
+Configurations prefixed with `provider=` use `go-discover` whereas
+configurations prefixed with `exec=` use `go-netaddrs`. For cloud providers not
+supported by `go-discover`, use `go-netaddrs`.
+
+### `go-discover` Configurations
+
+`go-discover` configurations are prefixed with `provider=`.
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers,
+refer to further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+#### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication. Refer to
+  the following Authentication and Precedence section for details.
+- `secret_access_key` (optional) - the AWS secret access key for authentication.
+ Refer to the following Authentication and Precedence section for details.
+
+##### Authentication and Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+#### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets. If using tags,
+the `tag_key` and `tag_value` must be set on the network interface resource attached to the server
+not on the virtual machine resource itself.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `subscription_id` (required) - the Azure subscription ID.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+<Note>
+
+If the Nomad cluster is hosted on Azure, Nomad can use Managed Service Identities (MSI) to access Azure
+instead of an environment variable, shared client id and secret. MSI must be enabled on the VMs or Virtual
+Machine Scale Sets hosting Nomad. It is the preferred configuration since MSI prevents your Azure credentials
+from being stored in Nomad configuration. When using MSI, the `tag_name`, `tag_value` and `subscription_id` 
+need to be supplied for Virtual machines. Be aware that the amount of time that Azure takes for the VMs to detect
+the MSI permissions can be between a minute to an hour.
+
+</Note>
+
+
+#### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. Refer
+ to the following Authentication and Precedence section for more information.
+
+##### Authentication and Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
+
+
+### `go-netaddrs` Configurations
+
+`go-netaddrs` configurations are prefixed with `exec=`.
+
+What follows the `exec=` prefix may be any executable program and its arguments.
+Commands run by `go-netaddrs` must return a list of space-delimited IPv4 or IPv6
+addresses and exit with code `0` on success and non-zero on failure.
+
+You can refer to the executable by its absolute file system path, or by
+the executable's name if it can be found on the Nomad agent's PATH. Refer to
+[executables in the current directory](https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory)
+for more details on the lookup behavior.
+
+Example `go-netaddrs` configuration.
+
+```hcl
+server_join {
+  retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+}
+```
+
+Here, `hcloud`'s newline-delimited output has been re-formatted as space-
+delimited by piping its output into `tr`.
+
+Output of an example `go-netaddrs` executable
+
+```
+"1.1.1.1 2.2.2.2"
+```
+
+Visit [go-netaddrs](https://github.com/hashicorp/go-netaddrs) for more
+information on go-netaddrs configuration.
diff --git a/content/nomad/v1.11.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.11.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..3ad586cbc5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: telemetry Block in Agent Configuration
+description: |-
+  Configure Nomad telemetry behavior in the `telemetry` block of a Nomad agent configuration. Configure Nomad's publication of metrics and telemetry to Statsite, StatsD, DataDog, Prometheus, and Apica (Circonus).
+---
+
+# `telemetry` Block in Agent Configuration
+
+<Placement groups={['telemetry']} />
+
+This page provides reference information for configuring Nomad telemetry
+behavior in the `telemetry` block of a Nomad agent configuration. Configure
+Nomad's publication of metrics and telemetry to [Statsite], [StatsD], [DataDog],
+[Prometheus], and [Apica (Circonus)][Apica].
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for the
+`telemetry` block. To understand the architecture and metrics themselves,
+refer to the [Telemetry guide](/nomad/docs/monitor).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `in_memory_collection_interval` `(duration: 10s)` Configures the in-memory
+  sink collection interval. This sink is always configured and backs the JSON
+  metrics API endpoint. This option is particularly useful for debugging or
+  development purposes, where aggressive collection is required.
+
+- `in_memory_retention_period` `(duration: 1m)` Configures the in-memory sink
+  retention period. This sink is always configured and backs the JSON metrics
+  API endpoint. This option is particularly useful for debugging or development
+  purposes.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `include_alloc_metadata_in_metrics` `(bool: false)` - This controls whether
+  allocation metadata is included in metric labels. Enabling this option may result in
+  high cardinality labels. You should also configure [allowed_metadata_keys_in_metrics](#allowed_metadata_keys_in_metrics).
+
+- `allowed_metadata_keys_in_metrics` `(list: [])` - This filters the metadata
+  keys to be included in the metric publishing. By default it does not filter
+  out any keys and thus include all metadata.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+- `disable_quota_utilization_metrics` `(bool: false)` - Specifies if Nomad
+  should publish metrics about quota utilization (a Nomad Enterprise feature).
+  Since each quota utilization check requires a relatively expensive check
+  against Nomad's state store, users with many namespaces and many quotas may
+  want to disable these metrics.
+
+- `disable_allocation_hook_metrics` `(bool: false)` - Specifies if the Nomad
+  client should publish metrics related to allocation and task hooks.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog].
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should make
+  Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+  Nomad's Prometheus client retains metrics in memory unless scraped, so you
+  should not enable this field unless you are collecting metrics via Promtheus.
+
+### `circonus` (Apica)
+
+These `telemetry` parameters apply to [Apica], formerly Circonus. Apica acquired Circonus in 2024.
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
+
+
+[Statsite]: https://github.com/armon/statsite
+[StatsD]: https://github.com/etsy/statsd
+[DataDog]: https://github.com/DataDog/datadog-agent
+[Prometheus]: https://prometheus.io
+[Apica]: https://www.apica.io/
diff --git a/content/nomad/v1.11.x/content/docs/configuration/tls.mdx b/content/nomad/v1.11.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..4bdaaf2318
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: tls Block in Agent Configuration
+description: |-
+  Configure secure communication in the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key files. Specify the TLS version. Require client certificates for all incoming HTTPS requests and the server name on all outgoing TLS connections.
+---
+
+# `tls` Block in Agent Configuration
+
+<Placement groups={['tls']} />
+
+This page provides reference information for configuring secure communication in
+the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and
+RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key
+files. Specify the TLS version. Require client certificates for all incoming
+HTTPS requests and verifying the server name on all outgoing TLS connections.
+
+Note that he Nomad documentation uses "TLS" to refer to this communication
+except when it is potentially ambiguous between TLS and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for the `tls` block. To understand how to setup the certificates themselves, refer to
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/docs/secure/traffic/tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+  Nomad does not accept explicit ciphersuite configuration when for TLS 1.3
+  because the Go team has already designated a select set of ciphers that align
+  with the broadly-accepted Mozilla Security/Server Side TLS guidance for
+  [modern TLS configuration][modern-tls].
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12", "tls13".
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
+[modern-tls]: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
diff --git a/content/nomad/v1.11.x/content/docs/configuration/ui.mdx b/content/nomad/v1.11.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..63e74375ad
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: ui Block in Agent Configuration
+description: |-
+  Configure Nomad's web UI in the `ui` block of a Nomad agent configuration. Provide Vault and Consul links, add custom text to Nomad's UI, and define the HTTP Content Security Policy response header.
+---
+
+# `ui` Block in Agent Configuration
+
+<Placement groups={['ui']} />
+
+This page provides reference information for configuring Nomad's web UI in the
+`ui` block of a Nomad agent configuration. Provide Vault and Consul links,
+add custom text to display in Nomad's UI, and define the HTTP Content
+Security Policy response header.
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+- `show_cli_hints` `(bool: true)` - Controls whether CLI commands display hints
+  about equivalent UI pages. For example, when running `nomad server members`,
+  the CLI shows a message indicating where to find server information in
+  the web UI. Set to `false` to disable these hints.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI defaults to a black background. HEX values
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI defaults to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.11.x/content/docs/configuration/vault.mdx b/content/nomad/v1.11.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..09ecb1c9d7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: vault Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with HashiCorp Vault in the `vault` block of a Nomad agent configuration. Configure cluster name and the role for creating tokens. For Nomad clients, configure Vault's address, namespace, and certificate or TLS authentication. Specify the JWT authentication path. For Nomad servers, configure the server's default workload identity, which includes workload identity recipients, workload TTL, and key-value pairs for additional identity claims.
+
+---
+
+# `vault` Block in Agent Configuration
+
+<Placement groups={['vault']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [HashiCorp Vault][vault] in the `vault` block of a Nomad agent
+configuration. Configure cluster name and the role for creating tokens. For
+Nomad clients, configure Vault's address, namespace, and certificate or TLS
+authentication. Specify the JWT authentication path. For Nomad
+servers, configure the server's default workload identity, which includes
+workload identity recipients, workload TTL, and key-value pairs for additional
+identity claims.
+
+When configured, job tasks can use [workload identities][workload_id] to receive
+Vault ACL tokens automatically.
+
+Refer to the [Nomad and Vault Integration][nomad-vault] page for more
+information about the Vault integration.
+
+```hcl
+vault {
+  enabled = true
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+
+    extra_claims {
+      unique_id = "${job.region}:${job.namespace}:${job.id}"
+    }
+  }
+}
+```
+
+In Nomad Enterprise, you may specify multiple `vault` blocks to configure access
+to multiple Vault clusters. Each Vault cluster must have a different value for
+the [`name`](#name) field.
+
+## `vault` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`vault.cluster`][] field. In Nomad Community Edition, only
+  the `"default"` cluster will be used, so this field should be omitted.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`] set to `true`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `jwt_auth_backend_path` - `(string: "jwt-nomad")` - Specifies the mount
+  [path][vault_auth_enable_path] of the JWT authentication method to be used to
+  login with workload identity JWTs.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens
+  from. This field defines the role used to derive task tokens when the job does
+  not define a value for [`vault.role`][jobspec_vault_role]. If empty, the
+  default Vault cluster role is used.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `default_identity` <code>([Identity](#default_identity-parameters): nil)</code> -
+  Specifies the default workload identity configuration to use when a task with
+  a `vault` block does not specify an [`identity`][jobspec_identity] block
+  named `vault_<name>`, where `<name>` matches the value of this `vault` block
+  [`name`](#name) parameter. Setting a default identity causes the value of
+  `allow_unauthenticated` to be ignored.
+
+### `default_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`bound_audiences`][vault_bound_aud]
+  configuration in the Vault JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in
+  the task's `NOMAD_TOKEN_vault` environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_vault.jwt`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+- `extra_claims` `(map[string]string: optional)` - A set of key-value pairs that
+  will be provided as extra identity claims for workloads. You can use the keys
+  as [user claims in Vault role configurations][vault-jwt-user-claim]. The
+  values are interpolated. For example, if you include the extra claim
+  `unique_id = "${job.region}:${job.namespace}:${job.id}"`, you could set the
+  user claim field to `/extra_claims/unique_id` to map that identifier to an
+  entity alias. The available attributes for interpolation are:
+
+  - `${job.region}` - The region where the job is running.
+  - `${job.namespace}` - The job's namespace.
+  - `${job.id}` - The job's ID.
+  - `${job.node_pool}` - The node pool where the allocation is running.
+  - `${group.name}` - The task group name of the task using Vault.
+  - `${alloc.id}` - The allocation's ID.
+  - `${task.name}` - The name of the task using Vault.
+  - `${node.id}` - The ID of the node where the allocation is running.
+  - `${node.datacenter}` - The datacenter of the node where the allocation is running.
+  - `${node.pool}` - The node pool of the node where the allocation is running.
+  - `${node.class` - The class of the node where the allocation is running.
+  - `${vault.cluster}` - The Vault cluster name.
+  - `${vault.namespace}` - The Vault namespace.
+  - `${vault.role}` - The Vault role.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows a Vault configuration for a Nomad server using the workload
+identity authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled = true
+
+  # Provide a default workload identity configuration so jobs don't need to
+  # specify one.
+  default_identity {
+    aud  = ["vault.io"]
+    env  = false
+    file = true
+    ttl  = "1h"
+  }
+}
+```
+
+### Nomad Client
+
+This example shows a Vault configuration for a Nomad client.
+
+```hcl
+client {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  address   = "https://vault.service.consul:8200"
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+}
+```
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[jobspec_identity]: /nomad/docs/job-specification/identity
+[nomad-vault]: /nomad/docs/secure/vault 'Nomad Vault Integration'
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault_bound_aud]: /vault/api-docs/auth/jwt#bound_audiences
+[vault_auth_enable_path]: /vault/docs/commands/auth/enable#path
+[workload_id]: /nomad/docs/concepts/workload-identity
+[vault-jwt-user-claim]: /vault/api-docs/auth/jwt#user_claim
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/connect-nodes.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/connect-nodes.mdx
new file mode 100644
index 0000000000..5d1f406ae8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/connect-nodes.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: Connect nodes into a cluster
+description: |-
+  Connect nodes together to create a Nomad cluster manually
+  or automatically with cloud auto-join on AWS, Azure, and GCP.
+---
+
+# Connect nodes into a cluster
+
+In order to create a Nomad cluster out of individual nodes, you need to
+introduce them to one another. There are several ways to perform this:
+
+- Manually
+- Cloud Auto-Join
+- Consul
+
+This tutorial describes each method and provides configuration snippets, which
+you can use as starting points for your own configuration.
+
+## Manual clustering
+
+Manually bootstrapping a Nomad cluster does not rely on additional tooling, but
+does require operator participation in the cluster formation process. When
+bootstrapping, Nomad servers and clients must be started and informed with the
+address of at least one Nomad server.
+
+As you can tell, this creates a chicken-and-egg problem where one server must
+first be fully bootstrapped and configured before the remaining servers and
+clients can join the cluster. This requirement can add additional provisioning
+time as well as ordered dependencies during provisioning.
+
+First, you need to bootstrap a single Nomad server and capture its IP address.
+Place this address in the configuration once you have that nodes IP address.
+
+For Nomad servers, this configuration may look something like this:
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  # This is the IP address of the first server provisioned
+  server_join {
+    retry_join = ["<known-address>:4648"]
+  }
+}
+```
+
+Alternatively, you can supply a server's address after the servers have all been
+started by running the [`server join` command] on the servers individually to
+cluster the servers. All servers can join one other server, and then rely on the
+gossip protocol to discover the rest.
+
+```shell-session
+$ nomad server join <known-address>
+```
+
+For Nomad clients, the configuration may look something like:
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = ["<known-address>:4647"]
+  }
+}
+```
+
+The client node's server list can be updated at run time using the
+[`node config` command].
+
+```shell-session
+$ nomad node config -update-servers <IP>:4647
+```
+
+The port corresponds to the RPC port. If no port is specified with the IP
+address, the default RPC port of `4647` is assumed.
+
+As servers are added or removed from the cluster, this information is pushed to
+the client. This means only one server must be specified because, after initial
+contact, the full set of servers in the client's region are shared with the
+client.
+
+## Join nodes using cloud auto-join
+
+As of Nomad 0.8.4, [`retry_join`] accepts a unified interface using the
+[go-discover] library for doing automatic cluster joining using cloud metadata.
+To use retry-join with a supported cloud provider, specify the configuration on
+the command line or configuration file as a `key=value key=value ...` string.
+Values are taken literally and must not be URL encoded. If the values contain
+spaces, backslashes or double quotes they need to be double quoted and the usual
+escaping rules apply.
+
+```json
+{
+  "retry_join": ["provider=my-cloud config=val config2=\"some other val\" ..."]
+}
+```
+
+Consult the [cloud provider-specific configurations] in the cloud-autojoin
+documentation. This can be combined with static IP or DNS addresses or even
+multiple configurations for different providers. In order to use discovery
+behind a proxy, you will need to set `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY`
+environment variables per [Golang `net/http` library].
+
+## Use Consul to automatically cluster nodes
+
+To automatically bootstrap a Nomad cluster, Nomad can leverage another HashiCorp
+open source tool, [Consul]. Bootstrapping Nomad is easiest against an existing
+Consul cluster. The Nomad servers and clients will become informed of each
+other's existence when the Consul agent is installed and configured on each
+host. As an added benefit, integrating Consul with Nomad provides service and
+health check registration for applications which later run under Nomad.
+
+Consul models infrastructures as datacenters and multiple Consul datacenters can
+be connected over the WAN so that clients can discover nodes in other
+datacenters. Since Nomad regions can encapsulate many datacenters, you should be
+running a Consul cluster in every Nomad region and connecting them over the
+WAN. Refer to the Consul tutorial for both [bootstrapping] a single
+datacenter and [connecting multiple Consul clusters over the WAN].
+
+If a Consul agent is installed on the host prior to Nomad starting, the Nomad
+agent will register with Consul and discover other nodes.
+
+For servers, you must inform the cluster how many servers you expect to have.
+This is required to form the initial quorum, since Nomad is unaware of how many
+peers to expect. For example, to form a region with three Nomad servers, you
+would use the following Nomad configuration file:
+
+```hcl
+# /etc/nomad.d/server.hcl
+
+# data_dir tends to be environment specific.
+data_dir = "/opt/nomad/data"
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+```
+
+This configuration would be saved to disk and then run:
+
+```shell-session
+$ nomad agent -config=/etc/nomad.d/server.hcl
+```
+
+A similar configuration is available for Nomad clients:
+
+```hcl
+# /etc/nomad.d/client.hcl
+
+datacenter = "dc1"
+
+# data_dir tends to be environment specific.
+data_dir = "/opt/nomad/data"
+
+client {
+  enabled = true
+}
+```
+
+The agent is started in a similar manner:
+
+```shell-session
+$ sudo nomad agent -config=/etc/nomad.d/client.hcl
+```
+
+Nomad clients should always run as root (or with `sudo`). The above
+configurations include no IP or DNS addresses between the clients and
+servers. This is because Nomad detected the existence of Consul and utilized
+service discovery to form the cluster.
+
+### Consul auto-join internals
+
+~> This section discusses the internals of the Consul and Nomad integration at a
+very high level. Reading is only recommended for those curious to the
+implementation.
+
+As discussed in the previous section, Nomad merges multiple configuration files
+together, so the `-config` may be specified more than once:
+
+```shell-session
+$ nomad agent -config=base.hcl -config=server.hcl
+```
+
+In addition to merging configuration on the command line, Nomad also maintains
+its own internal configurations (called "default configs") which include reasonable
+base defaults. One of those default configurations includes a "consul" block,
+which specifies reasonable defaults for connecting to and integrating with Consul. In
+essence, this configuration file resembles the following:
+
+```hcl
+# You do not need to add this to your configuration file. This is an example
+# that is part of Nomad's internal default configuration for Consul integration.
+consul {
+  # The address to the Consul agent.
+  address = "127.0.0.1:8500"
+
+  # The service name to register the server and client with Consul.
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+
+  # Enables automatically registering the services.
+  auto_advertise = true
+
+  # Enabling the server and client to bootstrap using Consul.
+  server_auto_join = true
+  client_auto_join = true
+}
+```
+
+Refer to the [`consul` stanza] documentation for the complete set of configuration
+options.
+
+[`consul` stanza]: /nomad/docs/configuration/consul
+[`node config` command]: /nomad/commands/node/config
+[`retry_join`]: /nomad/docs/configuration/server_join#retry_join
+[`server join` command]: /nomad/commands/server/join
+[bootstrapping]: /consul/docs/deploy/server/vm/bootstrap
+[cloud provider-specific configurations]: /nomad/docs/configuration/server_join#cloud-auto-join
+[connecting multiple consul clusters over the wan]: /consul/docs/east-west/wan-federation
+[consul]: /consul/
+[go-discover]: https://github.com/hashicorp/go-discover
+[golang `net/http` library]: https://golang.org/pkg/net/http/#ProxyFromEnvironment
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/federate-regions.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/federate-regions.mdx
new file mode 100644
index 0000000000..2ae0283062
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/federate-regions.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Federate multi-region clusters
+description: |-
+  Set up multi-region federation to allow job submissions and API
+  interactions from any server in any region.
+---
+
+# Federate multi-region clusters
+
+Nomad operates at a regional level and provides first-class support for
+federation. Federation enables users to submit jobs or interact with the HTTP
+API targeting any region, from any server, even if that server resides in a
+different region.
+
+Federating multiple Nomad clusters requires network connectivity between the
+clusters. Servers in each cluster must be able to communicate over [RPC and
+Serf][ports-used]. Federated clusters are expected to communicate over WANs, so
+they do not need the same low latency as servers within a region.
+
+Once Nomad servers are able to connect over the network, you can issue the
+[nomad server join][server-join] command from any server in one region to a
+server in a remote region to federate the clusters.
+
+[![Multi-Region][multi-region-pic]][multi-region-pic]
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have two Nomad
+environments with ports 4646, 4647, and 4648 exposed. You can use this
+[Terraform environment][nomad-tf] to provision the sandbox environments. This
+guide assumes two clusters with one server node and two client nodes in each
+cluster. While the Terraform code already opens port 4646, you will also need to
+expose ports 4647 and 4648 on the server you wish to run [nomad server
+join][server-join] against (consult the [Nomad Port Requirements][ports-used]
+documentation for more information).
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node in each cluster. Consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+## Verify current regions
+
+Currently, each of your clusters is in the default `global`
+[region][region-config]. You can verify this by running [nomad server
+members][nomad-server-members] on any node in each of your clusters:
+
+```shell-session
+$ nomad server members
+Name                    Address       Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-29-34.global  172.31.29.34  4648  alive   true    2         0.10.1  dc1         global
+```
+
+## Change the regions
+
+Respectively change the region of your individual clusters into `west` and
+`east` by adding the [region][region-config] parameter into the agent
+configuration on the servers and clients (if you are using the provided sandbox
+environment, this configuration is located at `/etc/nomad.d/nomad.hcl`).
+
+Below is a snippet of the configuration file showing the required change on a
+node for one of the clusters (remember to change this value to `east` on the
+servers and clients in your other cluster):
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+region = "west"
+# ...
+```
+
+Once you have made the necessary changes for each cluster, restart the nomad
+service on each node:
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+Re-run the `nomad server members` command on any node in the cluster to verify
+that your server is configured to be the in the correct region. The output below
+is from running the command in the `west` region (make sure to run this command
+in your other cluster to make sure it is in the `east` region):
+
+```shell-session
+$ nomad server members
+Name                  Address       Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-29-34.west  172.31.29.34  4648  alive   true    2         0.10.1  dc1         west
+```
+
+## Federate the regions
+
+Run the [`nomad server join`][server-join] command from a server in one cluster
+and supply it the IP address of the server in your other cluster while
+specifying port 4648.
+
+Below is an example of running the `nomad server join` command from the server
+in the `west` region while targeting the server in the `east` region:
+
+```shell-session
+$ nomad server join 172.31.26.138:4648
+Joined 1 servers successfully
+```
+
+## Verify the clusters have been federated
+
+After you have federated your clusters, the output from the `nomad server members` command will show the servers from both regions:
+
+```shell-session
+$ nomad server members
+Name                     Address        Port  Status  Leader  Protocol  Build   Datacenter  Region
+ip-172-31-26-138.east    172.31.26.138  4648  alive   true    2         0.10.1  dc1         east
+ip-172-31-29-34.west     172.31.29.34   4648  alive   true    2         0.10.1  dc1         west
+```
+
+## Check job status in remote cluster
+
+From the Nomad cluster in the `west` region, try to run the [`nomad status`][nomad-status] command to check the status of jobs in the `east` region:
+
+```shell-session
+$ nomad status -region="east"
+No running jobs
+```
+
+If your regions were not federated properly, you will receive the following
+output:
+
+```shell-session
+$ nomad status -region="east"
+Error querying jobs: Unexpected response code: 500 (No path to region)
+```
+
+## Learn more about federation
+
+- [Deployment Topology across Multiple Regions][multi-region]
+
+[multi-region]: /nomad/docs/deploy/production/reference-architecture#deployment-topology-across-multiple-regions
+[multi-region-pic]: /img/clusters/nomad-multi-region.png
+[nomad-server-members]: /nomad/commands/server/members
+[nomad-status]: /nomad/commands/status
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[ports-used]: /nomad/docs/deploy/production/requirements#ports-used
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture
+[region-config]: /nomad/docs/configuration#region
+[server-join]: /nomad/commands/server/join
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-considerations.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-considerations.mdx
new file mode 100644
index 0000000000..a3ead6788f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-considerations.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Multi-region federation operational considerations
+description: |-
+  Review operational considerations for running Nomad multi-region federated clusters as well as instructions for migrating the authoritative region to a federated region.
+---
+
+# Multi-region federation operational considerations
+
+This page lists operational considerations for running multi-region federated
+clusters as well as instructions for migrating the authoritative region to a
+federated region.
+
+## Operational considerations
+
+When operating multi-region federated Nomad clusters, consider the following:
+
+* **Regular snapshots**: You can back up Nomad server state using the
+  [`nomad operator snapshot save`][] and [`nomad operator snapshot agent`][] commands. Performing
+  regular backups expedites disaster recovery. The cadence depends on cluster rates of change
+  and your internal SLA’s. You should regularly test snapshots using the
+  [`nomad operator snapshot restore`][] command to ensure they work.
+
+* **Local ACL management tokens**: You need local management tokens to perform federated cluster
+  administration when the authoritative region is down. Make sure you have existing break-glass
+  tokens available for each region.
+
+* **Known paths to creating local ACL tokens**: If the authoritative region fails, creation of
+  global ACL tokens fails. If this happens, having the ability to create local ACL tokens allows
+  you to continue to interact with each available federated region.
+
+## Authoritative and federated regions
+
+* **Can non-authoritative regions continue to operate if the authoritative region is unreachable?**:
+  Yes, running workloads are never interrupted due to federation failures. Scheduling of new
+  workloads and rescheduling of failed workloads is never interrupted due to federation failures.
+  See [Failure Scenarios][failure_scenarios] for details.
+
+* **Can the authoritative region be deployed with servers only?** Yes, deploying the Nomad
+  authoritative region with servers only, without clients, works as expected. This servers-only
+  approach can expedite disaster recovery of the region. Restoration does not include objects such
+  as nodes, jobs, or allocations, which are large and require compute intensive reconciliation
+  after restoration.
+
+* **Can I migrate the authoritative region to a currently federated region?** It is possible by
+  following these steps:
+
+  1. Update the [`authoritative_region`][] configuration parameter on the desired authoritative
+    region servers.
+  1. Restart the server processes in the new authoritative region and ensure all data is present in
+    state as expected. If the network was partitioned as part of the failure of the original
+    authoritative region, writes of replicated objects may not have been successfully replicated to
+    federated regions.
+  1. Update the [`authoritative_region`][] configuration parameter on the federated region servers
+    and restart their processes.
+
+* **Can federated regions be bootstrapped while the authoritative region is down?**  No they
+cannot.
+
+[`nomad operator snapshot save`]: /nomad/commands/operator/snapshot/save
+[`nomad operator snapshot agent`]: /nomad/commands/operator/snapshot/agent
+[`nomad operator snapshot restore`]: /nomad/commands/operator/snapshot/restore
+[failure_scenarios]: /nomad/docs/deploy/clusters/federation-failure-scenarios
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx
new file mode 100644
index 0000000000..ec97736b15
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/federation-failure-scenarios.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: Federated cluster failure scenarios
+description: |-
+  Review failure scenarios in multi-region federated cluster deployments.  Learn which Nomad features continue to work under federated and authoritative region failures.
+---
+
+# Federated cluster failure scenarios
+
+When running Nomad in federated mode, failure situations and impacts are different depending on
+whether the authoritative region is the impacted region or not, and what the failure mode is. In
+soft failures, the region's servers have lost quorum but the Nomad processes are still up, running,
+and reachable. In hard failures, the regional servers are completely unreachable and are akin to
+the underlying hardware having been terminated (cloud) or powered-off (on-prem).
+
+The scenarios are based on a Nomad deployment running three federated regions:
+ * `asia-south-1`
+ * `europe-west-1` - authoritative region
+ * `us-east-1`
+
+## Federated region failure: soft
+In this situation the region `asia-south-1` has lost leadership but the servers are reachable and
+up.
+
+All server logs in the impacted region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=d19e6bb5-5ec9-8f75-9caf-47e2513fe28d error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+  fail unless using the `stale=true` flag.
+
+✅ Creation and deletion of replicated objects, such as namespaces, is written to the
+  authoritative region.
+
+✅ Any federated regions with leadership is able to continue to replicate all objects detailed
+  previously.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Federated region failure: hard
+In this situation the region `asia-south-1` has gone down. When this happens, the Nomad server logs
+for the other regions have log entries similar to this example.
+```console
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Initiating push/pull sync with: us-east-1-server-1.us-east-1 192.168.1.193:9002
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+✅ Creation and deletion of replicated objects, such as namespaces, are written to the
+  authoritative region.
+
+✅ Any federated regions with leadership continue to replicate all objects detailed
+  above.
+
+✅ Creation of local ACL tokens continues to work for all regions which are running with
+  leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Authoritative region failure: soft
+In this situation the region `europe-west-1` has lost leadership but the servers are reachable and
+up.
+
+The server logs in the authoritative region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=68b3abe2-5e16-8f04-be5a-f76aebb0e59e error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail unless using the `stale=true` flag.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions are able to read data to replicate as they use the stale flag, but no
+  writes can occur to the authoritative region as described previously.
+
+✅ Creation of local ACL tokens continues to work for all federated regions which are running
+  with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all federated regions which
+  are running with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fails to deploy.
+
+## Authoritative region failure: hard
+In this situation the region `europe-west-1` has gone down. When this happens, the Nomad server
+leader logs for the other regions have log entries similar to this example.
+```console
+[ERROR] nomad/leader.go:544: nomad: failed to fetch namespaces from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1767: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2498: nomad: failed to fetch ACL binding rules from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader_ent.go:226: nomad: failed to fetch quota specifications from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:703: nomad: failed to fetch node pools from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1909: nomad: failed to fetch tokens from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2083: nomad: failed to fetch ACL Roles from authoritative region: error="rpc error: EOF"
+[DEBUG] nomad/leader_ent.go:84: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2292: nomad: failed to fetch ACL auth-methods from authoritative region: error="rpc error: EOF"
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect europe-west-1-server-1.europe-west-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions with leadership is not able to replicate objects detailed in the logs.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/index.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/index.mdx
new file mode 100644
index 0000000000..fc7eef29e7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Nomad clusters
+description: |-
+  This section contains material for creating and federating Nomad clusters.Connect nodes into a cluster, federate multi-region clusters, and configure a web UI reverse proxy. Review multi-region federation considerations and failure scenarios. mplement load balancing using Fabio, HAProxy, NGINX, or Traefik. Manage external traffic with application load balancing.
+
+---
+
+# Nomad clusters
+
+This section contains content for creating and federating Nomad clusters.
+Connect nodes into a cluster, federate multi-region clusters, and configure a
+web UI reverse proxy. Review multi-region federation considerations and
+failure scenarios. Implement load balancing using Fabio, HAProxy, NGINX, or
+Traefik. Manage external traffic with application load balancing.
diff --git a/content/nomad/v1.11.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx b/content/nomad/v1.11.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx
new file mode 100644
index 0000000000..efd7f73e28
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/clusters/reverse-proxy-ui.mdx
@@ -0,0 +1,392 @@
+---
+layout: docs
+page_title: Configure a web UI reverse proxy
+description: |-
+  Run and configure NGINX as a reverse proxy for the Nomad web UI to
+  create a secure way for users to access detailed cluster information.
+---
+
+# Configure a web UI reverse proxy
+
+NGINX can be used to reverse proxy web services and balance load across multiple instances of the same service. A reverse proxy has the added benefits of enabling multiple web services to share a single, memorable domain and authentication to view internal systems.
+
+To ensure every feature in the Nomad UI remains fully functional, you must properly configure your reverse proxy to meet Nomad's specific networking requirements.
+
+This guide will explore common configuration changes necessary when reverse proxying Nomad's Web UI. Issues common to default proxy configurations will be discussed and demonstrated. As you learn about each issue, you will deploy NGINX configuration changes that will address it.
+
+## Prerequisites
+
+This guide assumes basic familiarity with Nomad and NGINX.
+
+Here is what you will need for this guide:
+
+- Nomad 0.11.0 installed locally
+- Docker
+
+## Start Nomad
+
+Because of best practices around least access to nodes, it is typical for Nomad
+UI users to not have direct access to the Nomad client nodes. You can simulate
+that for the purposes of this guide by advertising an incorrect `http` address.
+
+Create a file named `nomad.hcl` with the following configuration snippet.
+
+```hcl
+# Advertise a bogus HTTP address to force the UI
+# to fallback to streaming logs through the proxy.
+advertise {
+  http = "internal-ip:4646"
+}
+```
+
+Start Nomad as a dev agent with this custom configuration file.
+
+```shell-session
+$ sudo nomad agent -dev -config=nomad.hcl
+```
+
+Next, create a service job file that will frequently write logs to `stdout`. This sample job file below can be used if you don't have your own.
+
+```hcl
+# fs-example.nomad.hcl
+
+job "fs-example" {
+  datacenters = ["dc1"]
+
+  task "fs-example" {
+    driver = "docker"
+
+    config {
+      image = "dingoeatingfuzz/fs-example:0.3.0"
+    }
+
+    resources {
+      cpu    = 500
+      memory = 512
+    }
+  }
+}
+```
+
+Run this service job using the Nomad CLI or UI.
+
+```shell-session
+$ nomad run fs-example.nomad.hcl
+```
+
+At this point, you have a Nomad cluster running locally with one job in it. You can visit the Web UI at `http://localhost:4646`.
+
+## Configure NGINX to reverse proxy the web UI
+
+As mentioned earlier, the overarching goal is to configure a proxy from Nomad UI users to the Nomad UI running on the Nomad cluster. To do that, you will configure a NGINX instance as your reverse proxy.
+
+Create a basic NGINX configuration file to reverse proxy the Web UI. It is important to name the NGINX configuration file `nginx.conf` otherwise the file will not bind correctly.
+
+```nginx
+# nginx.conf
+events {}
+
+http {
+  server {
+    location / {
+      proxy_pass http://host.docker.internal:4646;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    }
+  }
+}
+```
+
+<Note>
+
+ If you are not using Docker for Mac or Docker for Windows, the `host.docker.internal` DNS record may not be available.
+
+</Note>
+
+This basic NGINX configuration does two things. The first is forward all traffic into NGINX to the proxy address at `http://host.docker.internal:4646`. Since NGINX will be running in Docker and Nomad is running locally, this address is equivalent to `http://localhost:4646` which is where the Nomad API and Web UI are served. The second thing this configuration does is attach the `X-Forwarded-For` header which allows HTTP requests to be traced back to their origin.
+
+Next in a new terminal session, start NGINX in Docker using this configuration file.
+
+```shell-session
+$ docker run --publish=8080:80 \
+    --mount type=bind,source=$PWD/nginx.conf,target=/etc/nginx/nginx.conf \
+    nginx:latest
+```
+
+NGINX will be started as soon as Docker has finished pulling layers. At that point you can visit `http://localhost:8080` to visit the Nomad Web UI through the NGINX reverse proxy.
+
+## Extend connection timeout
+
+The Nomad Web UI uses long-lived connections for its live-update feature. If the proxy closes the connection early because of a connection timeout, it could prevent the Web UI from continuing to live-reload data.
+
+The Nomad Web UI will live-reload all data to make sure views are always fresh as Nomad's server state changes. This is achieved using the [blocking queries][blocking-queries] to the Nomad API. Blocking queries are an implementation of long-polling which works by keeping HTTP connections open until server-side state has changed. This is advantageous over traditional polling which results in more requests that often return no new information. It is also faster since a connection will close as soon as new information is available rather than having to wait for the next iteration of a polling loop. A consequence of this design is that HTTP requests aren't always expected to be short-lived. NGINX has a [default proxy timeout of 60 seconds](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout) while Nomad's blocking query system will leave connections open for five minutes by default.
+
+To observe the proxy time out a connection, visit the Nomad jobs list through the proxy at `http://localhost:8080/ui/jobs` with your Browser's developer tools open.
+
+<Tabs>
+  <Tab heading="Chrome">
+
+
+With the Nomad UI page open, press the `F12` key to open the Developer tools. If it is not already selected, go to the Developer tools pane and select the **Network** tab. Leaving the tools pane open. Refresh the UI page.
+
+The blocking query connection for jobs will remain in "(pending)" status.
+
+[![Chrome developer tools window showing pending connection.][img-chrome-pending]][img-chrome-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Chrome developer tools window showing connection timeout.][img-chrome-timeout]][img-chrome-timeout]
+
+  </Tab>
+  <Tab heading="Firefox">
+
+
+With the Nomad UI page open, go to the **Tools** menu, **Web Developer** flyout, and **Network** option.
+
+The blocking query connection for jobs will not show a status while it is still active.
+
+[![Firefox developer tools window showing pending connection.][img-firefox-pending]][img-firefox-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Firefox developer tools window showing connection timeout.][img-firefox-pending]][img-firefox-pending]
+
+  </Tab>
+  <Tab heading="Safari">
+
+
+With the Nomad UI page open, go to the **Tools** menu, **Web Developer** flyout, and **Network** option.
+
+The blocking query connection for jobs will have a spinning icon next to the Name while it is still active.
+
+[![Safari developer tools window showing pending connection.][img-safari-pending]][img-safari-pending]
+
+In approximately 60 seconds it will transition to a red error state. Clicking on the red error will show that you received a "504 Gateway Time-out" error.
+
+[![Safari developer tools window showing connection timeout.][img-safari-pending]][img-safari-pending]
+
+  </Tab>
+  <Tab heading="Edge">
+
+
+With the Nomad UI page open, press the `F12` key to open the Developer tools. If it is not already selected, go to the Developer tools pane and select the **Network** tab. Leaving the tools pane open. Refresh the UI page.
+
+The blocking query connection for jobs will remain in "(pending)" status.
+
+[![Edge developer tools window showing pending connection.][img-chrome-pending]][img-chrome-pending]
+
+In approximately 60 seconds it will transition to a "504 Gateway Time-out" status.
+
+[![Edge developer tools window showing connection timeout.][img-chrome-timeout]][img-chrome-timeout]
+
+  </Tab>
+  <Tab heading="Other">
+
+
+Open your browser's developer tools. Locate the network information and wait approximately 60 seconds. The request to `/v1/jobs` will timeout with the following error message.
+
+```plaintext
+Failed to load resource: the server responded with a status of
+504 (Gateway Time-out)
+```
+
+  </Tab>
+</Tabs>
+<hr />
+
+
+To prevent these timeouts, update the NGINX configuration's `location` block to extend the
+`proxy_read_timeout` setting. The Nomad API documentation's [Blocking
+Queries][blocking-queries] section explains that Nomad adds the result of (`wait` / 16) to the declared wait
+time. You should set the `proxy_read_timeout` to slightly exceed Nomad's calculated wait time.
+
+This guide uses the default blocking query `wait` of 300 seconds. Nomad adds
+18.75 seconds to that wait time, so the `proxy_read_timeout` should be greater than 318.75 seconds.
+
+Set the`proxy_read_timeout` to `319s`.
+
+```nginx
+# ...
+proxy_pass http://host.docker.internal:4646;
+proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+
+# Nomad blocking queries will remain open for a default of 5 minutes.
+# Increase the proxy timeout to accommodate this timeout with an
+# additional grace period.
+proxy_read_timeout 319s;
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+## Disable proxy buffering
+
+When possible the Web UI will use a streaming HTTP request to stream logs on the task logs page. NGINX by default will buffer proxy responses in an attempt to free up connections to the backend server being proxied as soon as possible.
+
+Proxy buffering causes logs events to not stream because they will be temporarily captured within NGINX's proxy buffer until either the connection is closed or the proxy buffer size is hit and the data is finally flushed to the client.
+
+Older browsers may not support this technology, in which case logs are streamed using a simple polling mechanism.
+
+To observe this issue, visit the task logs page of your sample job by first visiting the sample job at `http://localhost:8080/jobs/fs-example` then clicking into the most recent allocation, then clicking into the `fs-example` task, then clicking the logs tab.
+
+Logs will not load and eventually the following error will appear in the UI.
+
+[![Error in the UI. Cannot fetch logs. The logs for this task are inaccessible][img-cannot-fetch-logs]][img-cannot-fetch-logs]
+
+There will also be this additional error in the browser developer tools console.
+
+```plaintext
+GET http://internal-ip:4646/v1/client/fs/logs/131f60f7-ef46-9fc0-d80d-29e673f01bd6?follow=true&offset=50000&origin=end&task=ansi&type=stdout net::ERR_NAME_NOT_RESOLVED
+```
+
+This `ERR_NAME_NOT_RESOLVED` error can be safely ignored. To prevent streaming logs through Nomad server nodes when unnecessary, the Web UI optimistically attempts to connect directly to the client node the task is running on. Since the Nomad configuration file used in this guide specifically advertises an address that can't be reached, the UI automatically falls back to requesting logs through the proxy.
+
+To allow log streaming through NGINX, the NGINX configuration needs to be updated to disable proxy buffering. Add the following to the `location` block of the existing NGINX configuration file.
+
+```nginx
+# ...
+proxy_read_timeout 319s;
+
+# Nomad log streaming uses streaming HTTP requests. In order to
+# synchronously stream logs from Nomad to NGINX to the browser
+# proxy buffering needs to be turned off.
+proxy_buffering off;
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+## Enable WebSocket connections
+
+As of Nomad 0.11.0, the Web UI has supported [interactive exec sessions with any running task in the cluster](https://www.hashicorp.com/blog/hashicorp-nomad-remote-exec-web-ui). This is achieved using the exec API which is implemented using WebSockets.
+
+WebSockets are necessary for the exec API because they allow bidirectional data transfer. This is used to receive changes to the remote output as well as send commands and signals from the browser-based terminal.
+
+The way a WebSocket connection is established is through a handshake request. The handshake is an HTTP request with special `Connection` and `Upgrade` headers.
+
+WebSockets also do not support CORS headers. The server-side of a WebSocket connection needs to verify trusted origins on its own. Nomad does this verification by checking if the `Origin` header of the handshake request is equal to the address of the Nomad API.
+
+By default NGINX will not fulfill the handshake or the origin verification. This results in exec sessions immediately terminating. You can experience this in the Web UI by going to `http://localhost:8080/jobs/fs-example`, clicking the Exec button, choosing the task, and attempting to run the command `/bin/sh`.
+
+[![Error in the UI when running /bin/sh. The connection has closed.][img-cannot-remote-exec]][img-cannot-remote-exec]
+
+The fulfill the handshake NGINX will need to forward the `Connection` and `Upgrade` headers. To meet the origin verification required by the Nomad API, NGINX will have to override the existing `Origin` header to match the host address. Add the following to the `location` block of the existing NGINX configuration file.
+
+```nginx
+# ...
+proxy_buffering off;
+
+# The Upgrade and Connection headers are used to establish
+# a WebSockets connection.
+proxy_set_header Upgrade $http_upgrade;
+proxy_set_header Connection "upgrade";
+
+# The default Origin header will be the proxy address, which
+# will be rejected by Nomad. It must be rewritten to be the
+# host address instead.
+proxy_set_header Origin "${scheme}://${proxy_host}";
+# ...
+```
+
+Restart the NGINX docker container to load these configuration changes.
+
+WebSocket connections are also stateful. If you are planning on using NGINX to balance load across all Nomad server nodes, it is important to ensure that WebSocket connections get routed to a consistent host.
+
+This can be done by specifying an upstream in NGINX and using it as the proxy pass. Add the following after the server block in the existing NGINX configuration file.
+
+```nginx
+# ...
+# Since WebSockets are stateful connections but Nomad has multiple
+# server nodes, an upstream with ip_hash declared is required to ensure
+# that connections are always proxied to the same server node when possible.
+upstream nomad-ws {
+  ip_hash;
+  server host.docker.internal:4646;
+}
+# ...
+```
+
+Traffic must also pass through the upstream. To do this, change the `proxy_pass` in the NGINX configuration file.
+
+```nginx
+# ...
+location / {
+  proxy_pass http://nomad-ws
+# ...
+```
+
+Since a dev environment only has one node, this change has no observable effect.
+
+## Review the complete NGINX configuration
+
+At this point all Web UI features are now working through the NGINX proxy. Here is the completed NGINX configuration file.
+
+```nginx
+events {}
+
+http {
+  server {
+    location / {
+      proxy_pass http://nomad-ws;
+      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+
+      # Nomad blocking queries will remain open for a default of 5 minutes.
+      # Increase the proxy timeout to accommodate this timeout with an
+      # additional grace period.
+      proxy_read_timeout 319s;
+
+      # Nomad log streaming uses streaming HTTP requests. In order to
+      # synchronously stream logs from Nomad to NGINX to the browser
+      # proxy buffering needs to be turned off.
+      proxy_buffering off;
+
+      # The Upgrade and Connection headers are used to establish
+      # a WebSockets connection.
+      proxy_set_header Upgrade $http_upgrade;
+      proxy_set_header Connection "upgrade";
+
+      # The default Origin header will be the proxy address, which
+      # will be rejected by Nomad. It must be rewritten to be the
+      # host address instead.
+      proxy_set_header Origin "${scheme}://${proxy_host}";
+    }
+  }
+
+  # Since WebSockets are stateful connections but Nomad has multiple
+  # server nodes, an upstream with ip_hash declared is required to ensure
+  # that connections are always proxied to the same server node when possible.
+  upstream nomad-ws {
+    ip_hash;
+    server host.docker.internal:4646;
+  }
+}
+```
+
+## Next steps
+
+In this guide, you set up a reverse NGINX proxy configured for the Nomad UI.
+You also explored common configuration properties necessary to allow the Nomad
+UI to work properly through a proxy—connection timeouts, proxy buffering,
+WebSocket connections, and Origin header rewriting.
+
+You can use these building blocks to configure your preferred proxy server
+software to work with the Nomad UI. For further information about the NGINX
+specific configuration highlighted in this guide, consult:
+
+- [connection timeout][nginx-proxy-read-timeout]
+- [proxy buffering][nginx-proxy-buffering]
+- [WebSocket proxying][nginx-websocket-proxying]
+- [session persistence][nginx-session-persistence]
+
+[blocking-queries]: /nomad/api-docs#blocking-queries
+[nginx-proxy-buffering]: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering
+[nginx-proxy-read-timeout]: http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout
+[nginx-session-persistence]: https://nginx.org/en/docs/http/load_balancing.html#nginx_load_balancing_with_ip_hash
+[nginx-websocket-proxying]: https://nginx.org/en/docs/http/websocket.html
+[img-cannot-fetch-logs]: /img/clusters/cannot-fetch-logs.png
+[img-cannot-remote-exec]: /img/clusters/cannot-remote-exec.png
+[img-chrome-pending]: /img/clusters/chrome-pending.png
+[img-chrome-timeout]: /img/clusters/chrome-timeout.png
+[img-firefox-pending]: /img/clusters/firefox-pending.png
+[img-firefox-timeout]: /img/clusters/firefox-timeout.png
+[img-safari-pending]: /img/clusters/safari-pending.png
+[img-safari-timeout]: /img/clusters/safari-timeout.png
diff --git a/content/nomad/v1.11.x/content/docs/deploy/index.mdx b/content/nomad/v1.11.x/content/docs/deploy/index.mdx
new file mode 100644
index 0000000000..236977daab
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Install Nomad
+description: |-
+  Learn how to install Nomad on Linux, Mac, and Windows. Review Linux post-installation steps such as installing Container Network Interface (CNI) reference plugins, the consul-cni plugin, and the dmidecode tool. Configure bridge network traffic to route through iptables and verify cgroup controllers. Learn how to compile a Nomad binary from source code.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager addrepo --from-repofile=https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Install dmidecode
+
+When running on a virtualized host such as Amazon EC2, Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions
+require installing the dmidecode package manually.
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+
+## Verify the installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.11.x/content/docs/deploy/nomad-agent.mdx b/content/nomad/v1.11.x/content/docs/deploy/nomad-agent.mdx
new file mode 100644
index 0000000000..408151bce8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/nomad-agent.mdx
@@ -0,0 +1,192 @@
+---
+layout: docs
+page_title: Operate a Nomad agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operate a Nomad agent
+
+A Nomad agent is a long running process that runs on every machine in your Nomad
+cluster. The behavior of the agent depends on if it is running in client or
+server mode. Clients run tasks, while servers manage the cluster.
+
+Server agents are part of the [consensus protocol](/nomad/docs/architecture/cluster/consensus) and
+[gossip protocol](/nomad/docs/architecture/security/gossip). The consensus protocol, powered
+by Raft, lets the servers perform leader election and state replication.
+The gossip protocol allows for server clustering and multi-region federation.
+The higher burden on the server nodes means that you should run them on
+dedicated instances because the servers are more resource intensive than a
+client node.
+
+Client agents use fingerprinting to determine the capabilities and resources of
+the host machine, as well as what [drivers](/nomad/docs/job-declare/task-driver) are available.
+Clients register with servers to provide node information and a heartbeat.
+Clients run tasks that the server assigns to them. Client nodes make up the
+majority of the cluster and are very lightweight. They interface with the server
+nodes and maintain very little state of their own. Each cluster has usually 3 or
+5 server agents and potentially thousands of clients.
+
+## Run an agent
+
+Start the agent with the [`nomad agent` command](/nomad/commands/agent).
+This command blocks, running forever or until told to quit. The `nomad agent`
+command takes a variety of configuration options, but most have sane defaults.
+
+<Note title="Linux Users">
+
+You must run client agents as root, or with `sudo`, so that cpuset accounting
+and network namespaces work correctly.
+
+</Note>
+
+This example starts the agent in development mode, which means the agents runs
+as both the server and the client. Do not use `-dev` in a production environment.
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+The `nomad agent` command outputs the following important information:
+
+- **Client**: This indicates whether the agent is running as a client.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Nomad logs only
+  messages with an equal or higher severity.You may turn change the log level to
+  increase verbosity for debugging or reduce to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent runs. Nomad
+  has first-class support for multi-datacenter and multi-region configurations.
+  Use the `-region` and `-dc` flags to set the region and datacenter. The
+  default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent is running as a server. Server
+  nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stop an agent
+
+By default, any stop signal, such as interrupt or terminate, causes the
+agent to exit after ensuring its internal state is written to disk as
+needed. You can configure additional behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when you set `leave_on_interrupt` or `leave_on_terminate`, the
+servers notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there is a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, use the [`server
+force-leave` command][] to eject that server from the consensus peer set.
+
+For clients, when you set `leave_on_interrupt` or `leave_on_terminate` and the
+client is configured with [`drain_on_shutdown`][], the client drains its
+workloads before shutting down.
+
+## Signal handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in the [Stop an agent
+section](#stop-an-agent), Nomad supports special behavior for several other
+signals useful for debugging.
+
+* `SIGHUP` causes Nomad to [reload its configuration][].
+* `SIGUSR1` causes Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime. These the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`.
+
+This example outputs the Nomad agent's metrics.
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent starts, it fingerprints the host machine to identify its
+attributes, capabilities, and [task drivers](/nomad/docs/job-declare/task-driver). The client
+then reports this information to the servers during an initial registration. You
+provide the addresses of known servers to the agent via configuration,
+potentially using DNS for resolution. Use [Consul](https://www.consul.io/)
+to avoid hard coding addresses and instead resolve them on demand.
+
+While a client is running, it sends heartbeats to servers to maintain liveness.
+If the heartbeats fail, the servers assume the client node has failed. The
+server then stops assigning new tasks and migrates existing tasks. It is
+impossible to distinguish between a network failure and an agent crash, so Nomad
+handles both
+cases in the same way. Once the network recovers or a crashed agent
+restarts, Nomad updates the node status and resumes normal operation.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours, Nomad garbage collects that node.
+
+Servers are slightly more complex since they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/architecture/security/gossip) both to cluster
+within a region and to support multi-region configurations. When a server starts, it does not know the address of other servers in the cluster.
+To discover its peers, it must join the cluster. You do this with the
+[`server join` command](/nomad/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server leaves, it specifies its intent to do so, and the cluster marks
+that node as having left the cluster. If the server has left, replication to it
+stops, and it is removed from the consensus peer set. If the server has failed,
+replication attempts to make progress to recover from a software or network
+failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Run Nomad servers with the lowest possible permissions. The servers
+need access to their own data directory and the ability to bind to their ports.
+You should create a `nomad` user with the minimal set of required privileges.
+
+Run Nomad clients as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, you must do careful testing to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/commands/server/force-leave
+[consensus]: /nomad/docs/architecture/cluster/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/reference/metrics
diff --git a/content/nomad/v1.11.x/content/docs/deploy/production/index.mdx b/content/nomad/v1.11.x/content/docs/deploy/production/index.mdx
new file mode 100644
index 0000000000..8c9d995544
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/production/index.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: Deploy Nomad in a production environment
+description: |-
+  This page contains a high-level overview of Nomad production deployment and links review hardware requirements, reference architecture, a deployment guide, and configuration documentation.
+---
+
+# Deploy Nomad in a production environment
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the reference architecture and installation guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify hardware requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/deploy/production/requirements).
+
+## Install Nomad
+
+Visit the [Install Nomad](/nomad/docs/deploy) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad servers and clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/deploy/nomad-agent)
+and [Nomad Agent documentation](/nomad/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/docs/deploy/production/reference-architecture
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.11.x/content/docs/deploy/production/reference-architecture.mdx b/content/nomad/v1.11.x/content/docs/deploy/production/reference-architecture.mdx
new file mode 100644
index 0000000000..7a0e9e165a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/production/reference-architecture.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: Production reference architecture
+description: |-
+  Review the recommended compute and networking resources for provisioning a Nomad Enterprise cluster in a production environment.
+---
+
+# Production reference architecture
+
+This document provides recommended practices and a reference architecture for
+Nomad production deployments. This reference architecture conveys a general
+architecture that should be adapted to accommodate the specific needs of each
+implementation.
+
+The following topics are addressed:
+
+- [Reference Architecture](#ra)
+- [Deployment Topology within a Single Region](#one-region)
+- [Deployment Topology across Multiple Regions](#multi-region)
+- [Network Connectivity Details](#net)
+- [Deployment System Requirements](#system-reqs)
+- [High Availability](#high-availability)
+- [Failure Scenarios](#failure-scenarios)
+
+<!-- vale Google.We = NO -->
+
+This document describes deploying a Nomad cluster in combination with, or with
+access to, a [Consul cluster][]. We recommend the use of Consul with Nomad to
+provide automatic clustering, service discovery, health checking and dynamic
+configuration.
+
+<a name="ra"></a>
+
+## Reference architecture
+
+A Nomad cluster typically comprises three or five servers (but no more than
+seven) and a number of client agents. Nomad differs slightly from Consul in
+that it divides infrastructure into [regions][glossary-regions] which are
+served by one Nomad server cluster, but can manage multiple
+[datacenters][glossary-dc] or availability zones. For example, a _US Region_
+can include datacenters _us-east-1_ and _us-west-2_.
+
+In a Nomad multi-region architecture, communication happens via [WAN gossip][].
+Additionally, Nomad can integrate easily with Consul to provide features such as
+automatic clustering, service discovery, and dynamic configurations. Thus we
+recommend you use Consul in your Nomad deployment to simplify the deployment.
+
+<!-- vale Google.We = YES -->
+
+In cloud environments, a single cluster may be deployed across multiple
+availability zones. For example, in AWS each Nomad server can be deployed to an
+associated EC2 instance, and those EC2 instances distributed across multiple
+AZs. Similarly, Nomad server clusters can be deployed to multiple cloud regions
+to allow for region level HA scenarios.
+
+For more information on Nomad server cluster design, see the [cluster
+requirements documentation][requirements].
+
+The design shared in this document is the recommended architecture for
+production environments, as it provides flexibility and resilience. Nomad
+utilizes an existing Consul server cluster; however, the deployment design of
+the Consul server cluster is outside the scope of this document.
+
+Nomad to Consul connectivity is over HTTP and should be secured with TLS as well as a Consul
+token to provide encryption of all traffic. This is done using Nomad's
+[Automatic Clustering with Consul][consul-clustering].
+
+<a name="one-region"></a>
+
+### Deployment topology within a single region
+
+A single Nomad cluster is recommended for applications deployed in the same region.
+
+Each cluster is expected to have either three or five servers.
+This strikes a balance between availability in the case of failure and
+performance, as [Raft][] consensus gets progressively
+slower as more servers are added.
+
+The time taken by a new server to join an existing large cluster may increase as
+the size of the cluster increases.
+
+#### Reference diagram
+
+[![Reference diagram][img-reference-diagram]][img-reference-diagram]
+
+<a name="multi-region"></a>
+
+### Deployment topology across multiple regions
+
+By deploying Nomad server clusters in multiple regions, the user is able to
+interact with the Nomad servers by targeting any region from any Nomad server
+even if that server resides in a separate region. However, most data is not
+replicated between regions as they are fully independent clusters. The
+exceptions which _are_ replicated between regions are:
+
+- [ACL policies and global tokens][acl]
+- [Sentinel policies in Nomad Enterprise][sentinel]
+
+Nomad server clusters in different datacenters can be federated using WAN links.
+The server clusters can be joined to communicate over the WAN on port `4648`.
+This same port is used for single datacenter deployments over LAN as well.
+
+Additional documentation is available to learn more about Nomad cluster
+[federation][].
+
+<a name="net"></a>
+
+## Network connectivity details
+
+[![Nomad network diagram][img-nomad-net]][img-nomad-net]
+
+Nomad servers are expected to be able to communicate in high bandwidth, low
+latency network environments and have below 10 millisecond latencies between
+cluster members. Nomad servers can be spread across cloud regions or datacenters
+if they satisfy these latency requirements.
+
+Nomad client clusters require the ability to receive traffic as noted in
+the Network Connectivity Details; however, clients can be separated into any
+type of infrastructure (multi-cloud, on-prem, virtual, bare metal, etc.) as long
+as they are reachable and can receive job requests from the Nomad servers.
+
+Additional documentation is available to learn more about [Nomad networking][].
+
+<a name="system-reqs"></a>
+
+## Deployment system requirements
+
+Nomad server agents are responsible for maintaining the cluster state,
+responding to RPC queries (read operations), and for processing all write
+operations. Given that Nomad server agents do most of the heavy lifting, server
+sizing is critical for the overall performance efficiency and health of the
+Nomad cluster.
+
+### Nomad servers
+
+<!-- vale Vale.Spelling = NO --> <!-- vale Google.Colons = NO --> <!-- vale Google.WordList = NO -->
+
+| Type  | CPU       | Memory            | Disk        | Typical Cloud Instance Types               |
+| ----- | --------- | ----------------- | ----------- | ------------------------------------------ |
+| Small | 2-4 core  | 8-16&nbsp;GB RAM  | 50&nbsp;GB  | **AWS**: m5.large, m5.xlarge               |
+|       |           |                   |             | **Azure**: Standard_D2_v3, Standard_D4_v3  |
+|       |           |                   |             | **GCP**: n2-standard-2, n2-standard-4      |
+| Large | 8-16 core | 32-64&nbsp;GB RAM | 100&nbsp;GB | **AWS**: m5.2xlarge, m5.4xlarge            |
+|       |           |                   |             | **Azure**: Standard_D8_v3, Standard_D16_v3 |
+|       |           |                   |             | **GCP**: n2-standard-8, n2-standard-16     |
+
+<!-- vale Vale.Spelling = YES --> <!-- Google.Colons = YES --> <!-- vale Google.WordList = YES -->
+
+#### Hardware sizing considerations
+
+- The small size would be appropriate for most initial production
+  deployments, or for development/testing environments.
+
+- The large size is for production environments where there is a
+  consistently high workload.
+
+<Note>
+
+ For large workloads, ensure that the disks support a high number of
+IOPS to keep up with the rapid Raft log update rate.
+
+</Note>
+
+Nomad clients can be setup with specialized workloads as well. For example, if
+workloads require GPU processing, a Nomad datacenter can be created to serve
+those GPU specific jobs and joined to a Nomad server cluster. For more
+information on specialized workloads, see the documentation on [job
+constraints][] to target specific client nodes.
+
+## High availability
+
+A Nomad server cluster is the highly available unit of deployment within a
+single datacenter. A recommended approach is to deploy a three or five node
+Nomad server cluster. With this configuration, during a Nomad server outage,
+failover is handled immediately without human intervention.
+
+When setting up high availability across regions, multiple Nomad server clusters
+are deployed and connected via WAN gossip. Nomad clusters in regions are fully
+independent from each other and do not share jobs, clients, or state. Data
+residing in a single region-specific cluster is not replicated to other clusters
+in other regions.
+
+## Failure scenarios
+
+Typical distribution in a cloud environment is to spread Nomad server nodes into
+separate Availability Zones (AZs) within a high bandwidth, low latency network,
+such as an AWS Region. The diagram below shows Nomad servers deployed in
+multiple AZs promoting a single voting member per AZ and providing both AZ-level
+and node-level failure protection.
+
+[![Nomad fault tolerance][img-fault-tolerance]][img-fault-tolerance]
+
+Additional documentation is available to learn more about [cluster sizing and
+failure tolerances][sizing] as well as [outage recovery][].
+
+### Availability zone failure
+
+In the event of a single AZ failure, only a single Nomad server is affected
+which would not impact job scheduling as long as there is still a Raft quorum
+(that is, 2 available servers in a 3 server cluster, 3 available servers in a 5
+server cluster, more generally:
+
+<div align="center">quorum = floor( count(members) / 2) + 1</div>
+
+There are two scenarios that could occur should an AZ fail in a multiple AZ
+setup: leader loss or follower loss.
+
+#### Leader server loss
+
+If the AZ containing the Nomad leader server fails, the remaining quorum members
+would elect a new leader. The new leader then begins to accept new log entries and
+replicates these entries to the remaining followers.
+
+#### Follower server loss
+
+If the AZ containing a Nomad follower server fails, there is no immediate impact
+to the Nomad leader server or cluster operations. However, there still must be a
+Raft quorum in order to properly manage a future failure of the Nomad leader
+server.
+
+### Region failure
+
+In the event of a region-level failure (which would contain an entire Nomad
+server cluster), clients are still able to submit jobs to another region
+that is properly federated. However, data loss is likely as Nomad
+server clusters do not replicate their data to other region clusters. See
+[Multi-region Federation][federation] for more setup information.
+
+## Next steps
+
+Read [Deployment Guide][deployment-guide] to learn the steps required to
+install and configure a single HashiCorp Nomad cluster that uses Consul.
+
+[acl]: /nomad/secure/acl/bootstrap
+[consul cluster]: /nomad/docs/networking/consul
+[deployment-guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
+[img-fault-tolerance]: /img/deploy/nomad_fault_tolerance.png
+[img-nomad-net]: /img/deploy/nomad_network_arch_0-1x.png
+[img-reference-diagram]: /img/deploy/nomad_reference_diagram.png
+[job constraints]: /nomad/docs/job-specification/constraint
+[federation]: /nomad/docs/deploy/clusters/federate-regions
+[nomad networking]: /nomad/docs/deploy/production/requirements#network-topology
+[nomad server federation]: /nomad/docs/deploy/clusters/federate-regions
+[outage recovery]: /nomad/docs/manage/outage-recovery
+[raft]: https://raft.github.io/
+[requirements]: /nomad/docs/deploy/production/requirements
+[sentinel]: /nomad/docs/govern/sentinel
+[sizing]: /nomad/docs/architecture/cluster/consensus#deployment_table
+[wan gossip]: /nomad/docs/architecture/security/gossip
+[consul-clustering]: /nomad/docs/deploy/clusters/connect-nodes
+[glossary-regions]: /nomad/docs/glossary#regions
+[glossary-dc]: /nomad/docs/glossary#datacenters
diff --git a/content/nomad/v1.11.x/content/docs/deploy/production/requirements.mdx b/content/nomad/v1.11.x/content/docs/deploy/production/requirements.mdx
new file mode 100644
index 0000000000..66e561ff17
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/production/requirements.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: Nomad installation requirements
+description: |-
+  Learn about the hardware and networking resources that Nomad requires. Review RAM, CPU, network topology and ports, user permissions, and Linux capabilities.
+---
+
+# Nomad installation requirements
+
+This page contains an overview of the hardware and networking resources that
+Nomad requires. Review RAM, CPU, network topology and ports, user
+permissions, and Linux capabilities.
+
+## Resources
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publicly routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/architecture/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/commands/job/plan
+[`nomad fmt`]: /nomad/commands/fmt
+[mTLS]: /nomad/docs/secure/traffic/tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrate
diff --git a/content/nomad/v1.11.x/content/docs/deploy/production/windows-service.mdx b/content/nomad/v1.11.x/content/docs/deploy/production/windows-service.mdx
new file mode 100644
index 0000000000..a56c7ab562
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/production/windows-service.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Install Nomad as a Windows service
+description: |-
+  Learn how to run Nomad as a Windows service. Register Nomad with the Windows Service Control Manager. Configure Nomad to log to file, and increase the non-interactive desktop heap size.
+---
+
+# Install Nomad as a Windows service
+
+You may run Nomad as a native Windows service. Use the [windows service install][]
+command to install Nomad and create the Windows service.
+
+You may also set up the Nomad Windows service manually. Use [`sc.exe`] to register
+the Nomad application with the Windows Service Control Manager, configure Nomad to
+log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start=auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+## Increase the non-interactive desktop heap size
+
+If you run Nomad as a Windows service and you intend to run many allocations,
+such as more than 50, you may encounter issues with Windows terminating Nomad
+plugin processes with errors such as `exit status 0xc0000142` appearing in the
+logs. This is due to Nomad's inability to spawn more concurrent processes, and
+you may fix this by manipulating the value of
+`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
+Manager\SubSystems` Windows registry key.
+
+This key has a `Windows` value which in turn has a `SharedSection` parameter
+that accepts a value of three comma-separated integers, for example,
+`1024,20480,768`. The first integer indicates the maximum size of the
+system-wide heap, the second is the size of each desktop heap, and the third is
+the size of the desktop heap that is associated with a noninteractive Windows
+instance. All values are in kilobytes. For large Windows nodes that run large
+numbers of allocations, we recommend setting the final integer value to 2048 or
+4096 kB. Remember that any registry change requires restarting Windows, a
+restart of Nomad service is not sufficient.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
+[windows service install]: /nomad/docs/commands/windows/service-install
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/docker.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/docker.mdx
new file mode 100644
index 0000000000..9bb3b35b7b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/docker.mdx
@@ -0,0 +1,491 @@
+---
+layout: docs
+page_title: Configure the Docker task driver
+description: Nomad's Docker task driver lets you run Docker-based tasks in your jobs. Modify the Docker task driver plugin configuration. Learn about CPU, memory, filesystem IO, and security resource isolation as well as how Nomad handles dangling containers.
+---
+
+# Configure the Docker task driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+**Note:** If you are using Docker Desktop for Windows or MacOS, check
+[the FAQ][faq-win-mac].
+
+## Capabilities
+
+The `docker` driver implements the following capabilities:
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+Nomad clients manage a cpuset cgroup for each task to reserve or share CPU
+[cores][]. In order for Nomad to be compatible with Docker's own cgroups
+management, it must write to cgroups owned by Docker, which requires running as
+root. If Nomad is not running as root, CPU isolation and NUMA-aware scheduling
+will not function correctly for workloads with `resources.cores`, including
+workloads using task drivers other than `docker` on the same host.
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `registry.k8s.io/pause-<goarch>:3.3`. The image will only be pulled from the
+  container registry if its tag is `latest` or the image doesn't yet exist
+  locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+- `image_pull_timeout` - (Optional) A default time duration that controls how long Nomad
+  waits before cancelling an in-progress pull of the Docker image as specified
+  in `image` across all tasks. Defaults to `"5m"`.
+
+- `windows_allow_insecure_container_admin` - Indicates that on windows, docker
+  checks the `task.user` field or, if unset, the container image manifest after
+  pulling the container, to see if it's running as `ContainerAdmin`. If so, exits
+  with an error unless the task config has `privileged=true`. Defaults to `false`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/job-declare/task-driver/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad has a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+## Next steps
+
+[Use the Docker task driver in a job](/nomad/docs/job-declare/task-driver/docker).
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: /nomad/docs/job-declare/task-driver/docker#auth_soft_fail
+[cap_add]: /nomad/docs/job-declare/task-driver/docker#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/job-declare/task-driver/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/job-declare/task-driver/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/exec.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/exec.mdx
new file mode 100644
index 0000000000..58b52bee08
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/exec.mdx
@@ -0,0 +1,203 @@
+---
+layout: docs
+page_title: Configure the Isolated Fork/Exec task driver
+description: Nomad's Isolated Fork/Exec task driver lets you run binaries using OS isolation primitives. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes. Learn how the Isolated Fork/Exec task driver affects resource isolation, chroot, and CPU resources.
+---
+
+# Configure the Isolated Fork/Exec task driver
+
+Name: `exec`
+
+The `exec` driver is used to execute a particular command for a task. However,
+unlike [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec) it uses the
+underlying isolation primitives of the operating system to limit the task's
+access to resources. While simple, since the `exec` driver can invoke any
+command, it can be used to call scripts or other wrappers which provide higher
+level features.
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+## Next steps
+
+[Use the Isolated Fork/Exec task driver in a job](/nomad/docs/job-declare/task-driver/exec).
+
+[default_pid_mode]: /nomad/docs/job-declare/task-driver/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/job-declare/task-driver/exec#default_ipc_mode
+[cap_add]: /nomad/docs/job-declare/task-driver/exec#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/job-declare/task-driver/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/index.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/index.mdx
new file mode 100644
index 0000000000..1ecd37fd33
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/index.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: Configure Nomad task drivers
+description: Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, configuration, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+---
+
+# Configure Nomad task drivers
+
+Nomad's bundled task drivers integrate with the host OS to run job tasks in
+isolation. Review driver capabilities, client configuration, and reference
+information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec
+task drivers.
+
+@include 'task-driver-intro.mdx'
+
+## Configuration
+
+Refer to the [plugin block documentation][plugin] for examples on how to use the
+plugin block in Nomad's client configuration. Review the [Docker driver's client
+requirements section][docker_plugin] for a detailed example.
+
+## Nomad task drivers
+
+The Nomad binary contains several bundled task drivers. We also support
+additional task driver plugins that you may install separately.
+
+| Bundled with Nomad   | Plugins               |
+|----------------------|-----------------------|
+| [Docker]             | [Exec2]               |
+| [Isolated Fork/Exec] | [Podman]              |
+| [Java]               | [Virt]                |
+| [QEMU]               |                       |
+| [Raw Fork/Exec]      |                       |
+
+## Community task drivers
+
+You may also use [community-supported task driver
+plugins](/nomad/plugins/drivers/community/).
+
+## Use task drivers in jobs
+
+Refer to [Use Nomad task drivers in jobs](/nomad/docs/job-declare/task-driver)
+for usage information.
+
+## Create task drivers
+
+Nomad's task driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/deploy/task-driver/docker#client-requirements
+[plugin_guide]: /nomad/plugins/author/task-driver
+[Docker]: /nomad/docs/deploy/task-driver/docker
+[Exec2]: /nomad/plugins/drivers/exec2
+[Isolated Fork/Exec]: /nomad/docs/deploy/task-driver/exec
+[Podman]: /nomad/plugins/drivers/podman
+[Java]: /nomad/docs/deploy/task-driver/java
+[Virt]: /nomad/plugins/drivers/virt
+[QEMU]: /nomad/docs/deploy/task-driver/qemu
+[Raw Fork/Exec]: /nomad/docs/deploy/task-driver/raw_exec
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/java.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/java.mdx
new file mode 100644
index 0000000000..709b1523ca
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/java.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: Configure the Java task driver
+description: Nomad's Java task driver lets you run JAR files in your workloads. Review the Java task driver capabilities, plugin options, client requirements, and client attributes such as Java version and virtual machine. Learn how the Java task driver affects resource isolation and chroot.
+---
+
+# Configure the Java task driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+## Next steps
+
+[Use the Java task driver in a job](/nomad/docs/job-declare/task-driver/java).
+
+[default_pid_mode]: /nomad/docs/job-declare/task-driver/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/job-declare/task-driver/java#default_ipc_mode
+[cap_add]: /nomad/docs/job-declare/task-driver/java#cap_add
+[cap_drop]: /nomad/docs/job-declare/task-driver/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/job-declare/task-driver/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[host volume]: /nomad/docs/configuration/client#host_volume-block
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/qemu.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/qemu.mdx
new file mode 100644
index 0000000000..42d1f91eec
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/qemu.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: Configure the QEMU task driver
+description: Nomad's QEMU task driver provides a generic virtual machine runner that can execute any regular QEMU image. Review the QEMU task driver capabilities, plugin options, client requirements, and client attributes such as QEMU version. Learn how the QEMU task driver provides the highest level of workload isolation.
+---
+
+# Configure the QEMU task driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+## Next steps
+
+[Use the Java task driver in a job](/nomad/docs/job-declare/task-driver/qemu).
+
+[`args`]: /nomad/docs/job-declare/task-driver/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.11.x/content/docs/deploy/task-driver/raw_exec.mdx b/content/nomad/v1.11.x/content/docs/deploy/task-driver/raw_exec.mdx
new file mode 100644
index 0000000000..174d21505f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/deploy/task-driver/raw_exec.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Raw Fork/Exec task driver
+description: Nomad's Raw Exec task driver lets you execute commands with no resource isolation. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes.
+---
+
+# Configure the Raw Fork/Exec task driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+- `denied_envvars` - (Optional) Passes a list of environment variables that
+  the driver should scrub from all task environments. Supports globbing with "*"
+  wildcard accepted as prefix and/or suffix.
+
+```hcl
+config {
+  denied_envvars = ["AWS_SECRET_KEY", "*_TOKEN"]
+}
+```
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no filesystem isolation.
+
+If the launched process creates a new process group, it is possible that
+Nomad will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to
+manage the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, and the cgroup system is mounted.
+
+If the cluster is configured with memory oversubscription enabled, a task using
+the `raw_exec` driver can be configured to have no maximum memory limit by
+setting `memory_max = -1`.
+
+```hcl
+resources {
+  cpu        = 500
+  memory     = 128
+  memory_max = -1 # no limit
+}
+```
+
+## Next steps
+
+[Use the `raw_exec` driver in a job](/nomad/docs/job-declare/task-driver/raw_exec).
+
+[hardening]: /nomad/docs/deploy/production/requirements#user-permissions
+[service]: /nomad/docs/deploy/production/windows-service
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.11.x/content/docs/ecosystem.mdx b/content/nomad/v1.11.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..4bde196b5e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/ecosystem.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Learn about the Nomad ecosystem, which includes CI/CD, task drivers, service mesh, service proxy, secrets management, observability, autoscaling, storage, provisioning, GPUs, and cloud native support.
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/secure/vault)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/networking/consul/service-mesh)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](https://www.cni.dev/)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/networking/consul)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/architecture/storage/csi)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.11.x/content/docs/enterprise/index.mdx b/content/nomad/v1.11.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..174bcde169
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  such as resource quotas, Sentinel policies, audit logging, multi-region deployments, and advanced server management using Nomad Autopilot.
+---
+
+# Nomad Enterprise
+
+This page provides an overview of Nomad Enterprise features that
+add operations, collaboration, and governance capabilities such as resource
+quotas, Sentinel policies, audit logging, multi-region deployments, and advanced
+server management using Nomad Autopilot.
+
+Nomad Enterprise is available as a base Platform package with an optional
+Governance & Policy add-on module.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Long Term Support (LTS) Releases
+
+Nomad Enterprise initiated the Long-Term Support (LTS) release program with
+Nomad 1.8. Going forward, the first major release of each calendar year will be
+an LTS release.
+
+LTS releases have the following benefits for Nomad operators:
+
+- **Extended maintenance:** Two years of critical fixes provided through minor
+releases
+- **Efficient upgrades:** Support for direct upgrades from one LTS release
+to the next, reducing major-version upgrade risk and improving operational
+efficiency.
+
+LTS releases reduce operational overhead and risk by letting organizations
+receive critical fixes in minor releases without having to upgrade their major
+version more than once a year. Once you’ve upgraded to Nomad Enterprise 1.8,
+you will be running on a maintained LTS release that will allow you to easily
+upgrade to the next LTS major release when it's available. For more
+information, refer to HashiCorp’s multi-product LTS statement.
+
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/docs/manage/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/docs/manage/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/docs/manage/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+Refer to the [Vault Integration documentation](/nomad/docs/secure/vault/acl#vault-namespaces)) for more information.
+
+### Multiple Vault and Consul Clusters
+
+Nomad Enteprise allows sepcifying multiple integrations for Consul and Vault in
+the [vault](/nomad/docs/configuration/vault) and
+[consul](/nomad/docs/configuration/consul) portions of the Nomad agent
+configuration. After the agents are configured, Nomad jobspec writers can pick
+which Consul or Vault cluster to use in their job. Nomad administrators may
+also set default clusters for each in Nomad namespace configuration, as well as
+deny access to certain clusters by namespace.
+
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define [quota specifications](/nomad/docs/other-specifications/quota)
+and apply them to namespaces. When a quota is attached to a namespace,
+the jobs within the namespace may not consume more resources than the quota
+specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/docs/govern/resource-quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/docs/govern/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/reference/sentinel-policy
diff --git a/content/nomad/v1.11.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.11.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..6a9ae7cc17
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Nomad Enterprise License FAQ
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/commands/license/inspect
diff --git a/content/nomad/v1.11.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.11.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..d335265b51
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn how to configure, apply, and replace your Nomad Enterprise license. Use the `nomad license` command to review your license details.
+---
+
+# Nomad Enterprise Licensing
+
+<EnterpriseAlert product="nomad"/>
+
+This page provides information on how to configure, apply, inspect, and replace
+your Nomad Enterprise license.
+
+Each server in a Nomad Enterprise cluster must have a license to start. Download
+Nomad Enterprise from the [releases site].
+
+[Contact sales](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo
+of Nomad Enterprise.
+
+Refer to the Enterprise license
+[tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) for
+step-by-step license instructions. Review the [Request a trial license section
+](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.11.x/content/docs/enterprise/license/utilization-reporting.mdx b/content/nomad/v1.11.x/content/docs/enterprise/license/utilization-reporting.mdx
new file mode 100644
index 0000000000..8a1f883254
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/enterprise/license/utilization-reporting.mdx
@@ -0,0 +1,345 @@
+---
+layout: docs
+page_title: Automated license utilization reporting
+description: >-
+  Learn what data HashiCorp collects to monitor Enterprise product usage and license utilization. Enable or opt out of automatic reporting. Review sample payloads and logs.
+---
+
+# Automated license utilization reporting
+
+<EnterpriseAlert product="nomad" />
+
+This page provides information on the data HashiCorp collects to monitor
+Enterprise product usage and license utilization. Learn how to enable or
+opt out of automatic reporting. Review sample payloads and logs.
+
+## Introduction
+
+Automated reporting sends product and license utilization data to HashiCorp without
+requiring you to manually collect and report them.
+
+It shares data required to validate license utilization as defined in our contracts.
+The detailed product usage metrics also inform our feature roadmap. They consist of computed
+metrics and never contain Personal Identifiable Information (PII) or other sensitive information,
+which you can verify by reviewing the full [list of metrics](#full-list-of-metrics).
+Inform your account manager if you have concerns with any of the data.
+
+Automated reporting shares the data with HashiCorp using a secure, unidirectional HTTPS API and makes
+an auditable record in the product logs each time it submits a report. The reporting process is GDPR
+compliant and submits reports roughly once every 24 hours.
+
+## Enable automated reporting
+
+To enable automated reporting, you need to make sure that outbound network traffic is configured correctly
+and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or
+network settings are not in place, automated reporting will not work.
+
+### 1. Allow outbound HTTPS traffic on port 443
+
+Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by
+allow-listing the following IP addresses:
+
+- 100.20.70.12
+- 35.166.5.222
+- 23.95.85.111
+- 44.215.244.1
+
+### 2. Upgrade
+
+Upgrade to a release that supports license utilization reporting. These releases include:
+- [Nomad v1.7.0](/nomad/downloads) and later
+
+### 3. Check logs
+
+Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product
+logs for records that the data sent successfully.
+
+Instructions on how to check logs.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: recording audit record
+[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
+[DEBUG] completed recording audit record
+[DEBUG] core.reporting: export finished successfully
+```
+
+If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an
+error.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: error status code received: statusCode=403
+```
+
+In this case, reconfigure your network to allow egress and check back in 24 hours.
+
+## Opt out
+
+If your installation is air-gapped or you want to manually collect and report on the same license
+utilization metrics, you can opt-out of automated reporting.
+
+Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that
+you also opt out from sending license utilization metrics. Customers who opt out of automated reporting are
+still required to manually collect and send license utilization metrics to HashiCorp by using the
+[`nomad operator utilization`](/nomad/commands/operator/utilization) command.
+
+You may disable product usage metrics separately from license utilization reporting, so your
+automated license reporting can exclude product usage metrics, or you can include product usage
+metrics in offline reports.
+
+You have two ways to opt out of automated reporting: HCL configuration or environment variables.
+
+For HCL configuration, use the [`reporting`](/nomad/docs/configuration/reporting) block
+in your Nomad server agent config file.
+
+```hcl
+reporting {
+  license {
+    enabled = false
+  }
+}
+```
+
+The `reporting.license.enabled` option toggles automated reporting.
+Nomad still gathers license utilization data for manual reporting.
+
+To disable detailed product usage metrics for both automated and offline reporting,
+use the `reporting.disable_product_usage_reporting` option.
+
+```hcl
+reporting {
+  disable_product_usage_reporting = true
+}
+```
+
+Alternatively, you can use the following environment variables in your Nomad server agent's environment.
+
+```shell
+export OPTOUT_LICENSE_REPORTING=true
+export OPTOUT_PRODUCT_USAGE_REPORTING=true
+```
+
+If your configuration file and environment variable differ, the environment variable takes precedence.
+
+After changing configuration, follow the ["Run an agent"
+instructions](/nomad/docs/deploy/nomad-agentt#run-an-agent)
+to restart your Nomad server and apply your changes.
+
+The Nomad agent emits logs at startup confirming your settings. This example shows
+automated reporting enabled, but without product usage metrics.
+
+```
+[INFO]  nomad.reporting: reporting agent is enabled and configured
+[DEBUG] nomad.reporting: product usage reporting disabled via agent configuration
+[INFO]  nomad.reporting: product usage reporting is disabled; usage metrics data will not be collected
+```
+
+You can also check your product logs roughly 24 hours after opting out to make sure that the
+system isn’t trying to send reports, or that the detailed usage metrics are all reporting `0`.
+
+## Full list of metrics
+
+This table lists all the metrics that we collect.
+
+Only `nomad.billable.*` metrics are collected if product usage metrics are disabled.
+
+The values are all integers for pre-determined values. We do not collect any strings
+that might identify proprietary information.
+
+<!-- NOTE to maintainers: Generate this table with a CLI tool in the registry repo
+     https://github.com/hashicorp/hashicorp-census-registry/tree/main/nomad/v2/cmd
+-->
+
+| Key                                       | Description                                               |
+|-------------------------------------------|-----------------------------------------------------------|
+| acl.auth.method.count                     | ACL Auth Methods                                          |
+| acl.auth.method.jwt.count                 | ACL Auth Methods of type JWT                              |
+| acl.auth.method.oidc.count                | ACL Auth Methods of type OIDC                             |
+| acl.policy.count                          | ACL policies                                              |
+| acl.role.count                            | ACL roles                                                 |
+| acl.token.count                           | ACL tokens                                                |
+| alloc.count                               | All allocations                                           |
+| alloc.status.complete.count               | Allocations with client status "complete"                 |
+| alloc.status.failed.count                 | Allocations with client status "failed"                   |
+| alloc.status.lost.count                   | Allocations with client status "lost"                     |
+| alloc.status.pending.count                | Allocations with client status "pending"                  |
+| alloc.status.running.count                | Allocations with client status "running"                  |
+| alloc.status.unknown.count                | Allocations with client status "unknown"                  |
+| alloc.task.count                          | All tasks in allocations                                  |
+| alloc.task.running.count                  | Running tasks in allocations                              |
+| client.count                              | Client nodes in the cluster                               |
+| client.driver.docker.count                | Clients with the "docker" driver                          |
+| client.driver.exec.count                  | Clients with the "exec" driver                            |
+| client.driver.exec2.count                 | Clients with the "exec2" driver                           |
+| client.driver.java.count                  | Clients with the "java" driver                            |
+| client.driver.nomad-driver-virt.count     | Clients with the "nomad-driver-virt" driver               |
+| client.driver.other.count                 | Clients with some other driver                            |
+| client.driver.pledge.count                | Clients with the "pledge" driver                          |
+| client.driver.podman.count                | Clients with the "podman" driver                          |
+| client.driver.qemu.count                  | Clients with the "qemu" driver                            |
+| client.driver.raw_exec.count              | Clients with the "raw_exec" driver                        |
+| client.plugin.cni.unique.count            | Unique CNI plugins on client nodes                        |
+| client.plugin.driver.unique.count         | Unique task drivers on client nodes                       |
+| client.plugin.host_volume.unique.count    | Unique host volume plugins on client nodes                |
+| client.plugin.secret.unique.count         | Unique secret plugins on client nodes                     |
+| client.resources.compute                  | Total client compute                                      |
+| client.resources.core.count               | Total client CPU cores                                    |
+| client.resources.memory                   | Total client memory in MB                                 |
+| client.vault.enabled.count                | Clients with Vault enabled                                |
+| job.count                                 | All jobs                                                  |
+| job.driver.docker.count                   | Jobs with the "docker" driver                             |
+| job.driver.exec.count                     | Jobs with the "exec" driver                               |
+| job.driver.exec2.count                    | Jobs with the "exec2" driver                              |
+| job.driver.java.count                     | Jobs with the "java" driver                               |
+| job.driver.nomad-driver-virt.count        | Jobs with the "nomad-driver-virt" driver                  |
+| job.driver.other.count                    | Jobs with some other driver                               |
+| job.driver.pledge.count                   | Jobs with the "pledge" driver                             |
+| job.driver.podman.count                   | Jobs with the "podman" driver                             |
+| job.driver.qemu.count                     | Jobs with the "qemu" driver                               |
+| job.driver.raw_exec.count                 | Jobs with the "raw_exec" driver                           |
+| job.group.count                           | Task groups in jobs                                       |
+| job.network.cni.args.count                | Networks in jobs with custom CNI args                     |
+| job.network.mode.bridge.count             | Networks in jobs with mode "bridge"                       |
+| job.network.mode.cni.count                | Networks in jobs with mode "cni"                          |
+| job.network.mode.host.count               | Networks in jobs with mode "host"                         |
+| job.network.mode.other.count              | Networks in jobs with some other mode                     |
+| job.parameterized.count                   | Parameterized jobs                                        |
+| job.parameterized.dispatched.count        | Dispatched parameterized jobs                             |
+| job.periodic.count                        | Periodic jobs                                             |
+| job.periodic.dispatched.count             | Dispatched periodic jobs                                  |
+| job.service.consul.connect.count          | Connect services in jobs                                  |
+| job.service.consul.count                  | Consul services in jobs                                   |
+| job.service.nomad.count                   | Nomad provider services in jobs                           |
+| job.task.identity.count                   | Tasks in jobs with identity enabled                       |
+| job.task.template.count                   | Tasks in jobs with templates                              |
+| job.task.vault.count                      | Tasks in jobs with Vault enabled                          |
+| job.type.batch.count                      | Jobs of type "batch"                                      |
+| job.type.service.count                    | Jobs of type "service"                                    |
+| job.type.sysbatch.count                   | Jobs of type "sysbatch"                                   |
+| job.type.system.count                     | Jobs of type "system"                                     |
+| job.volume.csi.count                      | CSI volumes in jobs                                       |
+| job.volume.host.count                     | Host volumes in jobs                                      |
+| job.volume.sticky.count                   | Sticky volumes in jobs                                    |
+| namespace.count                           | Namespaces                                                |
+| namespace.quotas.count                    | Quotas                                                    |
+| node.cpu.arch.amd64.count                 | Clients with "amd64" CPU architecture                     |
+| node.cpu.arch.arm64.count                 | Clients with "arm64" CPU architecture                     |
+| node.cpu.arch.other.count                 | Clients with some other CPU architecture                  |
+| node.cpu.arch.s390x.count                 | Clients with "s390x" CPU architecture                     |
+| node.cpu.arch.unique.count                | Unique CPU architectures on client nodes                  |
+| node.kernel.name.aix.count                | Clients with "aix" kernel                                 |
+| node.kernel.name.darwin.count             | Clients with "darwin" kernel                              |
+| node.kernel.name.freebsd.count            | Clients with "freebsd" kernel                             |
+| node.kernel.name.linux.count              | Clients with "linux" kernel                               |
+| node.kernel.name.other.count              | Clients with some other kernel                            |
+| node.kernel.name.plan9.count              | Clients with "plan9" kernel                               |
+| node.kernel.name.solaris.count            | Clients with "solaris" kernel                             |
+| node.kernel.name.unique.count             | Unique kernels on client nodes                            |
+| node.os.name.alpine.count                 | Clients with "alpine" operating system                    |
+| node.os.name.amazon.count                 | Clients with "amazon" operating system                    |
+| node.os.name.arch.count                   | Clients with "arch" operating system                      |
+| node.os.name.centos.count                 | Clients with "centos" operating system                    |
+| node.os.name.cloudlinux.count             | Clients with "cloudlinux" operating system                |
+| node.os.name.coreos.count                 | Clients with "coreos" operating system                    |
+| node.os.name.darwin.count                 | Clients with "darwin" operating system                    |
+| node.os.name.debian.count                 | Clients with "debian" operating system                    |
+| node.os.name.fedora.count                 | Clients with "fedora" operating system                    |
+| node.os.name.gentoo.count                 | Clients with "gentoo" operating system                    |
+| node.os.name.opensuse.count               | Clients with "opensuse" operating system                  |
+| node.os.name.oracle.count                 | Clients with "oracle" operating system                    |
+| node.os.name.other.count                  | Clients with some other operating system                  |
+| node.os.name.raspbian.count               | Clients with "raspbian" operating system                  |
+| node.os.name.redhat.count                 | Clients with "redhat" operating system                    |
+| node.os.name.suse.count                   | Clients with "suse" operating system                      |
+| node.os.name.ubuntu.count                 | Clients with "ubuntu" operating system                    |
+| node.os.name.unique.count                 | Unique operating systems on client nodes                  |
+| node.os.name.windows.count                | Clients with "windows" operating system                   |
+| node.pool.count                           | Node pools                                                |
+| node.status.disconnected.count            | Clients with status "disconnected"                        |
+| node.status.down.count                    | Clients with status "down"                                |
+| node.status.initializing.count            | Clients with status "initializing"                        |
+| node.status.ready.count                   | Clients with status "ready"                               |
+| node.status.unknown.count                 | Clients with status "unknown"                             |
+| nomad.billable.clients                    | Number of client nodes in the cluster                     |
+| nomad.billable.cores.s390x                | Active client s390x CPU cores in the cluster              |
+| nomad.billable.cores.total                | Active client CPU cores in the cluster                    |
+| plugin.csi.unique.count                   | Unique CSI plugins                                        |
+| policy.sentinel.count                     | Sentinel policies                                         |
+| sentinel.enforcement.advisory.count       | Sentinel policies with "advisory" enforcement level       |
+| sentinel.enforcement.hard-mandatory.count | Sentinel policies with "hard-mandatory" enforcement level |
+| sentinel.enforcement.soft-mandatory.count | Sentinel policies with "soft-mandatory" enforcement level |
+| sentinel.scope.submit-csi-volume.count    | Sentinel policies with "submit-csi-volume" scope          |
+| sentinel.scope.submit-host-volume.count   | Sentinel policies with "submit-host-volume" scope         |
+| sentinel.scope.submit-job.count           | Sentinel policies with "submit-job" scope                 |
+| task.driver.docker.count                  | Tasks with the "docker" driver                            |
+| task.driver.exec.count                    | Tasks with the "exec" driver                              |
+| task.driver.exec2.count                   | Tasks with the "exec2" driver                             |
+| task.driver.java.count                    | Tasks with the "java" driver                              |
+| task.driver.nomad-driver-virt.count       | Tasks with the "nomad-driver-virt" driver                 |
+| task.driver.other.count                   | Tasks with some other driver                              |
+| task.driver.pledge.count                  | Tasks with the "pledge" driver                            |
+| task.driver.podman.count                  | Tasks with the "podman" driver                            |
+| task.driver.qemu.count                    | Tasks with the "qemu" driver                              |
+| task.driver.raw_exec.count                | Tasks with the "raw_exec" driver                          |
+| variable.count                            | Nomad Variables                                           |
+| variable.lock.count                       | Nomad Variable Locks                                      |
+| volume.csi.capacity                       | Capacity of all CSI volumes in MB                         |
+| volume.csi.count                          | Number of "csi" volumes                                   |
+| volume.dhv.capacity                       | Capacity of all dynamic host volumes in MB                |
+| volume.dhv.plugin.other.count             | Dynamic host volumes with non-standard plugins            |
+| volume.dynamic.count                      | Number of "dynamic" volumes                               |
+| volume.static.count                       | Number of "static" volumes                                |
+
+
+## Example payload
+
+HashiCorp collects utilization data in the following JSON format.
+
+```json
+{
+  "version": "2",
+  "mode": "manual",
+  "timestamp": "2025-09-26T17:20:41.189292719Z",
+  "signature": "...",
+  "checksum": ...,
+  "snapshots": [
+    {
+      "snapshot_version": 2,
+      "id": "0001MDDJT442VWX01R4K21A22D",
+      "timestamp": "2025-09-26T13:20:04.598859749-04:00",
+      "schema_version": "2.1.0",
+      "product": "nomad",
+      "process_id": "01K63GH92XVS1V95RM7509N303",
+      "metrics": {
+        ...
+        "nomad.billable.clients": {
+          "key": "nomad.billable.clients",
+          "value": 25,
+          "mode": "write"
+        },
+        ...
+      },
+      "product_version": "1.10.6",
+      "license_id": "...",
+      "checksum": ...,
+      "metadata": {}
+    }
+  ]
+}
+```
+
+You can inspect the full payload in the server logs, or by running the
+[`nomad operator utilization`](/nomad/commands/operator/utilization) command.
diff --git a/content/nomad/v1.11.x/content/docs/faq.mdx b/content/nomad/v1.11.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..0b45423b3b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Nomad frequently asked question topics include checkpoint, gossip and consensus protocols, Nomad datacenter versus Consul datacenter, bootstrapping a cluster, and connecting to a host network with Docker Desktop.
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/architecture/cluster/consensus) and
+a [gossip protocol](/nomad/docs/architecture/security/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.11.x/content/docs/glossary.mdx b/content/nomad/v1.11.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..a86a5517e2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Nomad key concepts include allocation, authoritative regions, bin packing, client, datacenters, deployment, driver, evaluation, job, node, node pool, regions, server, task, and task group.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/deploy/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.11.x/content/docs/govern/index.mdx b/content/nomad/v1.11.x/content/docs/govern/index.mdx
new file mode 100644
index 0000000000..076c490f63
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/govern/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: Governance and policy on Nomad
+description: |-
+  This section provides best practices and guidance for operating Nomad securely in a multi-team setting through features such as resource quotas, node pools, and Sentinel policies.
+---
+
+# Governance and policy on Nomad
+
+Nomad Enterprise is aimed at teams and organizations and addresses the organizational complexity of multi-team and multi-cluster deployments with collaboration and governance features.
+
+This section provides best practices and guidance for operating Nomad
+securely in a multi-team setting through features such as resource quotas, node
+pools, and Sentinel policies.
+
+## Resource quotas
+
+<EnterpriseAlert inline />
+
+When many teams or users
+are sharing Nomad clusters, there is the concern that a single user could use
+more than their fair share of resources. Resource quotas provide a mechanism for
+cluster administrators to restrict the resources within a namespace.
+
+Quota specifications are first class objects in Nomad. A quota specification
+has a unique name, an optional human readable description, and a set of quota
+limits. The quota limits define the allowed resource usage within a region.
+
+Quota objects are shareable among namespaces. This allows an operator to define
+higher level quota specifications, such as a `prod-api` quota, and multiple
+namespaces can apply the `prod-api` quota specification.
+
+## Sentinel
+
+<EnterpriseAlert inline />
+
+[![Sentinel Overview][img_sentinel_overview]][img_sentinel_overview]
+
+- **Sentinel Policies** - Policies are able to introspect on request arguments
+  and use complex logic to determine if the request meets policy requirements.
+  For example, a Sentinel policy may restrict Nomad jobs to only using the
+  "docker" driver or prevent jobs from being modified outside of business
+  hours.
+
+- **Policy Scope** - Sentinel policies declare a "scope", which determines when
+  the policies apply. Currently the only supported scope is "submit-job", which
+  applies to any new jobs being submitted, or existing jobs being updated.
+
+- **Enforcement Level** - Sentinel policies support multiple enforcement levels.
+  The `advisory` level emits a warning when the policy fails, while
+  `soft-mandatory` and `hard-mandatory` will prevent the operation. A
+  `soft-mandatory` policy can be overridden if the user has necessary
+  permissions.
+
+### Sentinel policies
+
+Each Sentinel policy has a unique name, an optional description, applicable
+scope, enforcement level, and a Sentinel rule definition. If multiple policies
+are installed for the same scope, all of them are enforced and must pass.
+
+Sentinel policies _cannot_ be used unless the ACL system is enabled.
+
+### Policy scope
+
+Sentinel policies specify an applicable scope, which limits when the policy is
+enforced. This allows policies to govern various aspects of the system.
+
+The following table summarizes the scopes that are available for Sentinel
+policies:
+
+| Scope      | Description                                           |
+| ---------- | ----------------------------------------------------- |
+| submit-job | Applies to any jobs (new or updated) being registered |
+
+### Enforcement level
+
+Sentinel policies specify an enforcement level which changes how a policy is
+enforced. This allows for more flexibility in policy enforcement.
+
+The following table summarizes the enforcement levels that are available:
+
+| Enforcement Level | Description                                                            |
+| ----------------- | ---------------------------------------------------------------------- |
+| advisory          | Issues a warning when a policy fails                                   |
+| soft-mandatory    | Prevents operation when a policy fails, issues a warning if overridden |
+| hard-mandatory    | Prevents operation when a policy fails                                 |
+
+The [`sentinel-override` capability] is required to override a `soft-mandatory`
+policy. This allows a restricted set of users to have override capability when
+necessary.
+
+### Multi-region configuration
+
+Nomad supports multi-datacenter and multi-region configurations. A single region
+is able to service multiple datacenters, and all servers in a region replicate
+their state between each other. In a multi-region configuration, there is a set
+of servers per region. Each region operates independently and is loosely coupled
+to allow jobs to be scheduled in any region and requests to flow transparently
+to the correct region.
+
+When ACLs are enabled, Nomad depends on an "authoritative region" to act as a
+single source of truth for ACL policies, global ACL tokens, and Sentinel
+policies. The authoritative region is configured in the [`server` stanza] of
+agents, and all regions must share a single authoritative source. Any Sentinel
+policies are created in the authoritative region first. All other regions
+replicate Sentinel policies, ACL policies, and global ACL tokens to act as local
+mirrors. This allows policies to be administered centrally, and for enforcement
+to be local to each region for low latency.
+
+
+[img_sentinel_overview]: /img/govern/sentinel.jpg
+[`sentinel-override` capability]: /nomad/docs/secure/acl#sentinel-override
+[`server` stanza]: /nomad/docs/configuration/server
diff --git a/content/nomad/v1.11.x/content/docs/govern/namespaces.mdx b/content/nomad/v1.11.x/content/docs/govern/namespaces.mdx
new file mode 100644
index 0000000000..b9df280cfb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/govern/namespaces.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Create and use namespaces
+description: |-
+  Segment jobs and their associated objects from the jobs of other users of
+  the cluster using Nomad namespaces.
+---
+
+# Create and use namespaces
+
+Nomad has support for namespaces, which allow jobs and their
+associated objects to be segmented from each other and other users of the
+cluster.
+
+Nomad places all jobs and their derived objects into namespaces. These include
+jobs, allocations, deployments, and evaluations.
+
+Nomad does not namespace objects that are shared across multiple namespaces.
+This includes nodes, [ACL policies][acls], [Sentinel policies], and
+[quota specifications][quotas].
+
+In this guide, you'll create and manage a namespace with the CLI. After creating
+the namespace, you then learn how to deploy and manage a job within that
+namespace. Finally, you practice securing the namespace.
+
+## Create and view a namespace
+
+You can manage namespaces with the `nomad namespace` subcommand.
+
+Create the namespace of a cluster.
+
+```shell-session
+$ nomad namespace apply -description "QA instances of webservers" web-qa
+Successfully applied namespace "web-qa"!
+```
+
+List the namespaces of a cluster.
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
+
+## Run a job in a namespace
+
+To run a job in a specific namespace, annotate the job with the `namespace`
+parameter. If omitted, the job will be run in the `default` namespace. Below is
+an example of running the job in the newly created `web-qa` namespace:
+
+```hcl
+job "rails-www" {
+
+    ## Run in the QA environments
+    namespace = "web-qa"
+
+    ## Only run in one datacenter when QAing
+    datacenters = ["us-west1"]
+    # ...
+}
+```
+
+## Use namespaces in the CLI and UI
+
+### Nomad CLI
+
+When using commands that operate on objects that are namespaced, the namespace
+can be specified either with the flag `-namespace` or read from the
+`NOMAD_NAMESPACE` environment variable.
+
+Request job status using the `-namespace` flag.
+
+```shell-session
+$ nomad job status -namespace=web-qa
+ID         Type     Priority  Status   Submit Date
+rails-www  service  50        running  09/17/17 19:17:46 UTC
+```
+
+Export the `NOMAD_NAMESPACE` environment variable.
+
+```shell-session
+$ export NOMAD_NAMESPACE=web-qa
+```
+
+Use the exported environment variable to request job status.
+
+```shell-session
+$ nomad job status
+ID         Type     Priority  Status   Submit Date
+rails-www  service  50        running  09/17/17 19:17:46 UTC
+```
+
+### Nomad UI
+
+The Nomad UI provides a drop-down menu to allow operators to select the
+namespace that they would like to control. The drop-down will appear once there
+are namespaces defined. It is located in the top section of the left-hand column
+of the interface under the "WORKLOAD" label.
+
+[![An image of the Nomad UI showing the location of the namespace drop-down.
+The drop-down is open showing the "Default Namespace" option and an option for a
+"web-qa" namespace.][img_ui_ns_dropdown]][img_ui_ns_dropdown]
+
+## Secure a namespace
+
+Access to namespaces can be restricted using [ACLs]. As an example, you could
+create an ACL policy that allows full access to the QA environment for the web
+namespaces but restrict the production access by creating the following policy:
+
+```hcl
+# Allow read only access to the production namespace
+namespace "web-prod" {
+    policy = "read"
+}
+
+# Allow writing to the QA namespace
+namespace "web-qa" {
+    policy = "write"
+}
+```
+
+## Consul namespaces <EnterpriseAlert inline/>
+
+@include 'consul-namespaces.mdx'
+
+Refer to the [Consul networking integration
+guide](/nomad/docs/networking/consul) for Consul integration instructions.
+
+## Resources
+
+For specific details about working with namespaces, consult the [namespace
+commands] and [HTTP API] documentation.
+
+
+[acls]: /nomad/docs/secure/acl
+[http api]: /nomad/api-docs/namespaces
+[img_ui_ns_dropdown]: /img/govern/nomad-ui-namespace-dropdown.png
+[namespace commands]: /nomad/commands/namespace
+[quotas]: /nomad/docs/govern/resource-quotas
+[sentinel policies]: /nomad/docs/govern/sentinel
diff --git a/content/nomad/v1.11.x/content/docs/govern/resource-quotas.mdx b/content/nomad/v1.11.x/content/docs/govern/resource-quotas.mdx
new file mode 100644
index 0000000000..741140d731
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/govern/resource-quotas.mdx
@@ -0,0 +1,276 @@
+---
+layout: docs
+page_title: Create and use resource quotas
+description: |-
+  Create quotas that you attach to namespaces, and then secure them with ACLs so that you can restrict aggregate resource usage for namespaces.
+---
+
+# Create and use resource quotas
+
+[Nomad Enterprise] provides support for resource quotas, which allow operators
+to restrict the aggregate resource usage of [namespaces]. Once a quota
+specification is attached to a namespace, the Nomad cluster will count all
+resource usage by jobs in that namespace toward the quota limits. If the
+resource is exhausted, allocations within the namespaces will be queued until
+resources become available—by other jobs finishing or the quota being expanded.
+
+In this guide, you'll create a quota that limits resources in the global region.
+You will then assign the quota to a namespace where you will deploy a job.
+Finally, you'll learn how to secure the quota with ACLs.
+
+<EnterpriseAlert />
+
+## Define and create a quota
+
+You can manage resource quotas by using the `nomad quota` subcommand. To
+get started with creating a quota specification, run `nomad quota init` which
+produces an example quota specification.
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
+
+The file `spec.hcl` defines a limit for the global region. Additional limits may
+be specified in order to limit other regions.
+
+```hcl
+# spec.hcl
+name = "default-quota"
+description = "Limit the shared default namespace"
+
+# Create a limit for the global region. Additional limits may
+# be specified in-order to limit other regions.
+limit {
+  region = "global"
+  region_limit {
+    cores      = 0
+    cpu        = 2500
+    memory     = 1000
+    memory_max = 1000
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+  }
+  variables_limit = 1000
+}
+```
+
+### Resource limits
+
+When specifying resource limits the following enforcement behaviors are defined:
+
+- `limit < 0`: A limit less than zero disallows any access to the resource.
+
+- `limit == 0`: A limit of zero allows unlimited access to the resource.
+
+- `limit > 0`: A limit greater than zero enforces that the consumption is less
+  than or equal to the given limit.
+
+-> **Note:** Limits that specify the count of devices work differently. A `count > 0`
+enforces that the consumption is less than or equal to the given limit, and setting
+it to `0` disallows any usage of the given device. Unlike other limits, device count
+cannot be set to a negative value. To allow unlimited access to a device
+resource, remove it from the region limit.
+
+A quota specification is composed of one or more resource limits. Each limit
+applies to a particular Nomad region. Within the limit object, operators can
+specify the allowed CPU and memory usage.
+
+### Create the quota
+
+To create the quota, run `nomad quota apply` with the filename of your quota specification.
+
+```shell-session
+$ nomad quota apply spec.hcl
+Successfully applied quota specification "default-quota"!
+```
+
+Check for success with `nomad quota list`.
+
+```shell-session
+$ nomad quota list
+Name           Description
+default-quota  Limit the shared default namespace
+```
+
+## Attach a quota to a namespace
+
+In order for a quota to be enforced, you have to attach the quota specification
+to a namespace. This can be done using the `nomad namespace apply` command. Add
+the new quota specification to the `default` namespace as follows:
+
+```shell-session
+$ nomad namespace apply -quota default-quota default
+Successfully applied namespace "default"!
+```
+
+## View quota information
+
+Now that you have attached a quota to a namespace, you can run a job in the default namespace.
+
+Initialize the job.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+Run the job in the default namespace.
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: 985a1df8-0221-b891-5dc1-4d31ad4e2dc3
+```
+
+Check the status.
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 2500   0 / inf     0 / 1000      0 / 1000          0 / 1000
+
+Quota Device Limits
+Region  Device Name        Device Usage
+global  nvidia/gpu/1080ti  1 / 1
+```
+
+Notice that the newly created job is accounted against the quota specification
+since it is being run in the namespace attached to the "default-quota" quota.
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: ce8e1941-0189-b866-3dc4-7cd92dc38a69
+```
+
+Now, add more instances of the job by changing `count = 1` to `count = 4` and
+check to see if additional allocations were added.
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 10/16/17 10:51:32 PDT
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         3        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Quota limit hit "memory exhausted (1024 needed > 1000 limit)"
+
+Latest Deployment
+ID          = 7cd98a69
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       4        3       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+6d735236  81f72d90  cache       1        run      running  10/16/17 10:51:32 PDT
+ce8e1941  81f72d90  cache       1        run      running  10/16/17 10:51:32 PDT
+9b8e185e  81f72d90  cache       1        run      running  10/16/17 10:51:24 PDT
+```
+
+The output indicates that Nomad created two more allocations but did not place
+the fourth allocation, which would have caused the quota to be oversubscribed on
+memory.
+
+## Secure quota with ACLs
+
+Access to quotas can be restricted using [ACLs]. As an example, you could create
+an ACL policy that allows read-only access to quotas.
+
+```hcl
+# Allow read only access to quotas.
+quota {
+    policy = "read"
+}
+```
+
+Proper ACLs are necessary to prevent users from bypassing quota enforcement by
+increasing or removing the quota specification.
+
+## Design for federated clusters
+
+Nomad makes working with quotas in a federated cluster simple by replicating
+quota specifications from the [authoritative Nomad region]. This allows
+operators to interact with a single cluster but create quota specifications that
+apply to all Nomad clusters.
+
+As an example, you can create a quota specification that applies to two regions:
+
+```hcl
+name = "federated-example"
+description = "A single quota spec affecting multiple regions"
+
+# Create a limits for two regions
+limit {
+    region = "europe"
+    region_limit {
+        cpu = 20000
+        memory = 10000
+    }
+}
+
+limit {
+    region = "asia"
+    region_limit {
+        cpu = 10000
+        memory = 5000
+    }
+}
+```
+
+Apply the specification.
+
+```shell-session
+$ nomad quota apply spec.hcl
+Successfully applied quota specification "federated-example"!
+```
+
+Now that the specification is applied and attached to a namespace with jobs in each region,
+use the `nomad quota status` command to observe how the enforcement applies
+across federated clusters.
+
+```shell-session
+$ nomad quota status federated-example
+Name        = federated-example
+Description = A single quota spec affecting multiple regions
+Limits      = 2
+
+Quota Limits
+Region  CPU Usage     Memory Usage
+asia    2500 / 10000  1000 / 5000
+europe  8800 / 20000  6000 / 10000
+```
+
+## Learn more about quotas
+
+For specific details about working with quotas, consult the [quota commands] and
+[HTTP API] documentation.
+
+[acls]: /nomad/docs/secure/acl
+[authoritative nomad region]: /nomad/docs/configuration/server#authoritative_region
+[http api]: /nomad/api-docs/quotas
+[namespaces]: /nomad/docs/govern/namespaces
+[nomad enterprise]: https://www.hashicorp.com/products/nomad
+[quota commands]: /nomad/commands/quota
+[quotas]: /nomad/docs/govern/resource-quotas
diff --git a/content/nomad/v1.11.x/content/docs/govern/sentinel.mdx b/content/nomad/v1.11.x/content/docs/govern/sentinel.mdx
new file mode 100644
index 0000000000..909ec72167
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/govern/sentinel.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: Create and manage Sentinel policies
+description: |-
+  Create, install, test, and update Sentinel policies to express your policies
+  as code so that Nomad automatically enforces them.
+---
+
+# Create and manage Sentinel policies
+
+
+[Nomad Enterprise] integrates with [HashiCorp Sentinel][sentinel] for
+fine-grained policy enforcement. Sentinel allows operators to express their
+policies as code and have their policies automatically enforced. This allows
+operators to define a "sandbox" and restrict actions to only those compliant
+with policy.
+
+The Sentinel integration builds on the [ACL System][acls]. The integration
+provides the ability to create fine grained policy enforcements. Users must have
+the appropriate permissions to perform an action and are subject to any
+applicable Sentinel policies.
+
+In this guide, you will create a policy and then practice applying it to a job
+at different enforcement levels. Finally, you'll learn more about Sentinel
+language specifics.
+
+<EnterpriseAlert />
+
+## Prerequisites
+
+The following example demonstrates how to install a Sentinel policy. It assumes
+that ACLs have already been bootstrapped (refer to the [ACL guide][acls]), and
+that a `NOMAD_TOKEN` environment variable is set to a management token.
+
+## Create, install, and test a policy
+
+First, create a Sentinel policy, named `test.sentinel`:
+
+```sentinel
+## Test policy always fails for demonstration purposes
+main = rule { false }
+```
+
+Then, install this as an "advisory" policy which issues a warning on failure:
+
+```shell-session
+$ nomad sentinel apply -level=advisory test-policy test.sentinel
+Successfully wrote "test-policy" Sentinel policy!
+```
+
+Use `nomad job init` to create a job file.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+Attempt to submit that job file with `nomad job run`.
+
+```shell-session
+$ nomad job run example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* test-policy : Result: false (allowed failure based on level)
+
+FALSE - test-policy:2:1 - Rule "main"
+
+
+==> Monitoring evaluation "f43ac28d"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "11e01124"
+    Allocation "2618f3b4" created: node "add8ce93", group "cache"
+    Allocation "5c2674f2" created: node "add8ce93", group "cache"
+    Allocation "9937811f" created: node "add8ce93", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "f43ac28d" finished with status "complete"
+```
+
+The output indicates that the policy failed, but the job was accepted because of
+an "advisory" enforcement level.
+
+## Update and test the policy
+
+Next, change `test.sentinel` to only allow "exec" based drivers:
+
+```sentinel
+# Test policy only allows exec based tasks
+main = rule { all_drivers_exec }
+
+# all_drivers_exec checks that all the drivers in use are exec
+all_drivers_exec = rule {
+    all job.task_groups as tg {
+        all tg.tasks as task {
+            task.driver is "exec"
+        }
+    }
+}
+```
+
+Then updated the policy at a soft mandatory level:
+
+```shell-session
+$ nomad sentinel apply -level=soft-mandatory test-policy test.sentinel
+Successfully wrote "test-policy" Sentinel policy!
+```
+
+With the new policy, attempt to submit the same job, which uses the "docker"
+driver:
+
+```shell-session
+$ nomad run example.nomad.hcl
+Error submitting job: Unexpected response code: 500 (1 error(s) occurred:
+
+* test-policy : Result: false
+
+FALSE - test-policy:2:1 - Rule "main"
+  FALSE - test-policy:6:5 - all job.task_groups as tg {
+  all tg.tasks as task {
+    task.driver is "exec"
+  }
+}
+
+FALSE - test-policy:5:1 - Rule "all_drivers_exec"
+)
+```
+
+The output indicates that the policy and job have failed.
+
+## Override the policy
+
+Because the policy is failing, the job was rejected. Since the policy level is
+"soft-mandatory", you can override it using the `-policy-override` flag.
+
+Submit the job again with the `-policy-override` flag set:
+
+```shell-session
+$ nomad job run -policy-override example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* test-policy : Result: false (allowed failure based on level)
+
+FALSE - test-policy:2:1 - Rule "main"
+  FALSE - test-policy:6:5 - all job.task_groups as tg {
+  all tg.tasks as task {
+    task.driver is "exec"
+  }
+}
+
+FALSE - test-policy:5:1 - Rule "all_drivers_exec"
+
+
+==> Monitoring evaluation "16195b50"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "11e01124"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "16195b50" finished with status "complete"
+```
+
+This time, the job was accepted but with a warning that our policy is failing
+but was overridden.
+
+## Extend your knowledge: policy specification
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+### Sentinel job objects
+
+The `job` object is made available to policies in the `submit-job` scope
+automatically, without an explicit import. The object maps to the
+[JSON job specification], but fields differ slightly for better readability.
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on the job are accessed by the same name, converted to lower case and
+separating camel case to underscores. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+| ---------------------------------------- | ------------------------------------------- |
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+## Learn more about Sentinel
+
+For specific details about working with Sentinel, consult the [`nomad sentinel` sub-commands]
+and [HTTP API] documentation.
+
+[`nomad sentinel` sub-commands]: /nomad/commands/sentinel
+[`sentinel-override` capability]: /nomad/docs/secure/acl#sentinel-override
+[`server` stanza]: /nomad/docs/configuration/server
+[acls]: /nomad/docs/secure/acl
+[http api]: /nomad/api-docs/sentinel-policies
+[json job specification]: /nomad/api-docs/json-jobs
+[nomad enterprise]: https://www.hashicorp.com/products/nomad/
+[sentinel]: https://docs.hashicorp.com/sentinel
diff --git a/content/nomad/v1.11.x/content/docs/govern/use-node-pools.mdx b/content/nomad/v1.11.x/content/docs/govern/use-node-pools.mdx
new file mode 100644
index 0000000000..9edb260251
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/govern/use-node-pools.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Create and use node pools
+description: |-
+  Create node pools. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+---
+
+# Create and use node pools
+
+@include 'node-pools.mdx'
diff --git a/content/nomad/v1.11.x/content/docs/index.mdx b/content/nomad/v1.11.x/content/docs/index.mdx
new file mode 100644
index 0000000000..33bf5f9203
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Nomad is a flexible workload orchestrator to deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run diverse workloads including Docker, non-containerized, microservice, and batch applications.
+---
+
+# Nomad Documentation
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. Nomad can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+If you are just getting started with Nomad, refer to the [Getting
+Started tutorial collection][gs].
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/configure-tasks.mdx b/content/nomad/v1.11.x/content/docs/job-declare/configure-tasks.mdx
new file mode 100644
index 0000000000..931117af73
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/configure-tasks.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Configure job tasks
+description: |-
+  Provide values to a Nomad workload through job specification configuration files, command line arguments, and environment variables.
+---
+
+# Configure job tasks
+
+Most applications require some kind of local configuration. While command line
+arguments are the simplest method, many applications require more complex
+configurations provided via environment variables or configuration files. This
+section explores how to configure Nomad jobs to support many common
+configuration use cases.
+
+## Define application arguments
+
+Many tasks accept configuration via command-line arguments. For example,
+consider the [http-echo](https://github.com/hashicorp/http-echo) server which
+is a small go binary that renders the provided text as a webpage. The binary
+accepts two parameters:
+
+- The `-listen` flag contains the `address:port` to listen on
+- `-text` - the text to render as the HTML page
+
+Outside of Nomad, the server is started like this:
+
+```shell-session
+$ http-echo -listen=":5678" -text="hello world"
+```
+
+The Nomad equivalent job file might look something like this:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+
+    task "server" {
+      driver = "exec"
+
+      config {
+        command = "/bin/http-echo"
+
+        args = [
+          "-listen",
+          ":5678",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+<Note>
+
+ For this job specification, you must install the `http-echo` in
+the `/bin` folder on each of your clients. Nomad can
+also optionally fetch the binary using the `artifact` resource.
+
+</Note>
+
+Nomad has many [drivers], and most support passing arguments to their tasks via
+the `args` parameter. This parameter also supports Nomad variable
+[interpolation]. For example, if you wanted Nomad to dynamically allocate a high
+port to bind the service on instead of relying on a static port for the previous
+job:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+
+    task "server" {
+      driver = "exec"
+
+      config {
+        command = "/bin/http-echo"
+
+        args = [
+          "-listen",
+          ":${NOMAD_PORT_http}",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+## Set environment variables
+
+Some applications can be configured via environment variables. The
+[Twelve-Factor App](https://12factor.net/config) document suggests configuring
+applications through environment variables. Nomad supports custom environment
+variables in two ways:
+
+- Interpolation in an `env` stanza
+- Templated in the a `template` stanza
+
+### `env` stanza
+
+Each task may have an `env` stanza which specifies environment variables:
+
+```hcl
+task "server" {
+  env {
+    my_key = "my-value"
+  }
+}
+```
+
+The `env` stanza also supports [interpolation]:
+
+```hcl
+task "server" {
+  env {
+    LISTEN_PORT = "${NOMAD_PORT_http}"
+  }
+}
+```
+
+Consult the [`env` stanza] documentation for details.
+
+### Build environment variables with templates
+
+Nomad's [`template` stanza] can be used to generate environment variables.
+Environment variables may be templated with [Node attributes and
+metadata][nodevars], the contents of files on disk, Consul keys, or secrets from
+Vault:
+
+```hcl
+template {
+  data = <<EOH
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.key}}{{end}}"
+CERT={{ file "path/to/cert.pem" | to JSON }}
+NODE_ID="{{ env "node.unique.id" }}"
+EOH
+
+  destination = "secrets/config.env"
+  env         = true
+}
+```
+
+The template will be written to disk and then read as environment variables
+before your task is launched.
+
+## Load external configuration files
+
+Many applications use files for configuration. Nomad supports downloading files
+using the [`artifact` stanza] and [templating][`template` stanza] them prior to
+launching tasks. This allows shipping of configuration files and other assets
+that the task needs to run properly.
+
+Here is an example job which pulls down a configuration file as an artifact and
+templates it:
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    task "server" {
+      driver = "exec"
+
+      artifact {
+        source      = "http://example.com/config.hcl.tmpl"
+        destination = "local/config.hcl.tmpl"
+      }
+
+      template {
+        source      = "local/config.hcl.tmpl"
+        destination = "local/config.hcl"
+      }
+
+      config {
+        command = "my-app"
+        args = [
+          "-config", "local/config.hcl",
+        ]
+      }
+    }
+  }
+}
+```
+
+For more information on the artifact resource, please consult the [`artifact`
+stanza] documentation.
+
+[`artifact` stanza]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[nodevars]: /nomad/docs/reference/runtime-variable-interpolation
+[`template` stanza]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Variable Interpolation'
+[drivers]: /nomad/docs/job-declare/task-driver
+[`env` stanza]: /nomad/docs/job-specification/env
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/consul-service-mesh.mdx b/content/nomad/v1.11.x/content/docs/job-declare/consul-service-mesh.mdx
new file mode 100644
index 0000000000..90c4c61764
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/consul-service-mesh.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Use Consul service mesh
+description: |-
+  Nomad integrates with Consul service mesh to securely connect and isolate
+  your workloads. Review example job configurations that use service mesh. Learn about the Envoy proxy as well as mesh, ingress, and terminating gateways.
+---
+
+# Use Consul service mesh
+
+This page provides information on using Consul service mesh with
+Nomad to securely connect and isolate your workloads. Review example job
+configurations that use service mesh. Learn about the Envoy proxy as well as
+mesh, ingress, and terminating gateways.
+
+## Introduction
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block. All incoming external traffic is handled by the
+sidecar.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+Consul service mesh requires network isolation to function, so you must set
+job group's `network` [`mode`](/nomad/docs/job-specification/network#mode)
+to `bridge`, or an [appropriately configured `cni/*`
+network](/nomad/docs/networking/consul/service-mesh#network-mode).
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/networking/consul/service-mesh)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/reference/runtime-environment-settings#network-related-variables
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/create-job.mdx b/content/nomad/v1.11.x/content/docs/job-declare/create-job.mdx
new file mode 100644
index 0000000000..77eb3f5194
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/create-job.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: Create and submit a job
+description: |-
+ Create a Nomad job file and follow the job workflow to plan, submit, update,  and run a job.
+---
+
+# Create and submit a job
+
+In Nomad, the description of the job and all its requirements are maintained in
+a single file called the "job file". This job file resides locally on disk and
+it is highly recommended that you check job files into source control.
+
+The general flow for submitting a job in Nomad is:
+
+1. Author a job file according to the job specification
+1. Plan and review changes with a Nomad server
+1. Submit the job file to a Nomad server
+1. (Optional) Review job status and logs
+
+Here is a very basic example to get you started.
+
+## Author a job file
+
+Nomad attempts to strike a balance between ease and expressiveness in its job
+specification. Nomad also provides the `nomad init` command to generate sample
+job files. For more detailed information about the Nomad job specification,
+please consult the [Nomad documentation][job specification].
+
+Here is a sample job file which runs a small docker container web server to
+start with.
+
+```hcl
+job "docs" {
+  datacenters = ["dc1"]
+
+  group "example" {
+    network {
+      port "http" {
+        static = "5678"
+      }
+    }
+    task "server" {
+      driver = "docker"
+
+      config {
+        image = "hashicorp/http-echo"
+        ports = ["http"]
+        args = [
+          "-listen",
+          ":5678",
+          "-text",
+          "hello world",
+        ]
+      }
+    }
+  }
+}
+```
+
+This job file exists on your local workstation in plain text. When you are
+satisfied with this job file, you will plan and review the scheduler decision.
+It is generally a best practice to commit job files to source control,
+especially if you are working in a team.
+
+## Plan the job
+
+Once the job file is authored, you probably want to preview the changes Nomad
+will make when it runs. The `nomad job plan` command invokes a dry-run of the
+scheduler and output which scheduling decisions would take place.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++ Job: "docs"
++ Task Group: "example" (1 create)
+  + Task: "server" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Note that no action was taken. This job is not running. This is a complete
+dry-run and no allocations have taken place.
+
+## Submit the job
+
+Assuming the output of the plan looks acceptable, now ask Nomad to execute the
+job. This is done via the `nomad job run` command. You can optionally supply the
+modify index provided by the plan command to ensure no changes to this job have
+taken place between our plan and now.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "0d159869"
+    Evaluation triggered by job "docs"
+    Allocation "5cbf23a1" created: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0d159869" finished with status "complete"
+```
+
+Now that the job is scheduled, it may or may not be running. You need to inspect
+the allocation status and logs to make sure the job started correctly. The next
+section on [inspecting state](/nomad/docs/job-run/inspect)
+details ways to examine this job's state.
+
+## Update and plan the job
+
+When making updates to the job, it is best to always run the plan command and
+then the run command. For example:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+   datacenters = ["dc1"]
+
+   group "example" {
++    count = "2"
++
+     task "server" {
+       driver = "docker"
+```
+
+After saving these changes to disk, run the `nomad job plan` command:
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "example" (1 create, 1 in-place update)
+  +/- Count: "1" => "2" (forces create)
+      Task: "server"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 131
+To submit the job with version verification run:
+
+nomad job run -check-index 131 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+#### Reserved port collisions
+
+Because this job uses a static port, it is possible for some instances to not be
+placeable depending on the number of clients you have in your Nomad cluster. If
+your plan output contains:
+
+```plaintext hideClipboard
+Dimension "network: reserved port collision" exhausted on x nodes
+```
+
+This indicates that every feasible client in your cluster has or will have
+something placed at the requested port, leaving no place for some of these
+allocations to run. To resolve this, you need to reduce the requested count,
+add additional clients, or migrate from static ports to dynamic ports in your
+job specification.
+
+## Run the job
+
+Now, assuming the output is okay, execute the `nomad job run` command. Including
+the `check-index` parameter ensures that the job
+was not changed between the plan and run phases.
+
+```shell-session
+$ nomad job run -check-index 131 docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+For more details on advanced job updating strategies such as canary builds and
+build-green deployments, consult the documentation on [job update strategies].
+
+[job specification]: /nomad/docs/job-specification
+[job update strategies]:/nomad/docs/job-declare/strategy
+[inspecting state]: /nomad/docs/job-run/inspect
+
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/exit-signals.mdx b/content/nomad/v1.11.x/content/docs/job-declare/exit-signals.mdx
new file mode 100644
index 0000000000..2d4705a6f2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/exit-signals.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: Configure exit signals
+description: |-
+  Configure the exit signal that Nomad sends to an application to allow it
+  to gracefully terminate before Nomad kills the application.
+---
+
+# Configure exit signals
+
+On operating systems that support signals, Nomad will send the application a
+configurable signal before killing it. This gives the application time to
+gracefully drain connections and conduct other cleanup before shutting down.
+Certain applications take longer to drain than others, and thus Nomad allows
+specifying the amount of time to wait for the application to exit before
+force-killing it.
+
+Before Nomad terminates an application, it will send the `SIGINT` signal to the
+process. Processes running under Nomad should respond to this signal to
+gracefully drain connections. After a configurable timeout, the application
+will be force-terminated.
+
+The signal sent may be configured with the [`kill_signal`][kill_signal] task
+parameter, and the timeout before the task is force-terminated may be
+configured via [`kill_timeout`][kill_timeout].
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+      kill_timeout = "45s"
+    }
+  }
+}
+```
+
+The behavior is slightly different for Docker-based tasks. Nomad will run the
+`docker stop` command with the specified `kill_timeout`. The signal that `docker stop` sends to your container entrypoint is configurable using the
+[`STOPSIGNAL` configuration directive]; however, please note that the default is
+`SIGTERM`.
+
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[`stopsignal` configuration directive]: https://docs.docker.com/engine/reference/builder/#stopsignal
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/failure/check-restart.mdx b/content/nomad/v1.11.x/content/docs/job-declare/failure/check-restart.mdx
new file mode 100644
index 0000000000..548b90448b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/failure/check-restart.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Configure health check restart
+description: |-
+  Configure your Nomad job to restart workloads when health checks
+  fail.
+---
+
+# Configure health check restart
+
+The [`check_restart` stanza][check restart] instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the limit specified in a check_restart stanza, it is restarted
+according to the task group's restart policy. Restarts are local to the node
+running the task based on the tasks `restart` policy.
+
+The `limit` field is used to specify the number of times a failing health check
+is seen before local restarts are attempted. Operators can also specify a
+`grace` duration to wait after a task restarts before checking its health.
+
+You should configure the check restart on services when its likely that a
+restart would resolve the failure. An example of this might be restarting to
+correct a transient connection issue on the service.
+
+The following `check_restart` stanza waits for two consecutive health check
+failures with a grace period and considers both `critical` and `warning`
+statuses as failures.
+
+```hcl
+check_restart {
+  limit           = 2
+  grace           = "10s"
+  ignore_warnings = false
+}
+```
+
+The following CLI example output shows health check failures triggering restarts
+until its restart limit is reached.
+
+```shell-session
+$ nomad alloc status e1b43128-2a0a-6aa3-c375-c7e8a7c48690
+ID                   = e1b43128
+Eval ID              = 249cbfe9
+Name                 = demo.demo[0]
+Node ID              = 221e998e
+Job ID               = demo
+Job Version          = 0
+Client Status        = failed
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 2m59s ago
+Modified             = 39s ago
+
+Task "test" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB  p1: 127.0.0.1:28422
+
+Task Events:
+Started At     = 2018-04-12T22:50:32Z
+Finished At    = 2018-04-12T22:50:54Z
+Total Restarts = 3
+Last Restart   = 2018-04-12T17:50:15-05:00
+
+Recent Events:
+Time                       Type              Description
+2018-04-12T17:50:54-05:00  Not Restarting    Exceeded allowed attempts 3 in interval 30m0s and mode is "fail"
+2018-04-12T17:50:54-05:00  Killed            Task successfully killed
+2018-04-12T17:50:54-05:00  Killing           Sent interrupt. Waiting 5s before force killing
+2018-04-12T17:50:54-05:00  Restart Signaled  health check: check "service: \"demo-service-test\" check" unhealthy
+2018-04-12T17:50:32-05:00  Started           Task started by client
+2018-04-12T17:50:15-05:00  Restarting        Task restarting in 16.887291122s
+2018-04-12T17:50:15-05:00  Killed            Task successfully killed
+2018-04-12T17:50:15-05:00  Killing           Sent interrupt. Waiting 5s before force killing
+2018-04-12T17:50:15-05:00  Restart Signaled  health check: check "service: \"demo-service-test\" check" unhealthy
+2018-04-12T17:49:53-05:00  Started           Task started by client
+```
+
+[check restart]: /nomad/docs/job-specification/check_restart
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/failure/index.mdx b/content/nomad/v1.11.x/content/docs/job-declare/failure/index.mdx
new file mode 100644
index 0000000000..a5d9058de9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/failure/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: Failure recovery strategies
+description: |-
+  Discover the available job failure recovery strategies in Nomad so that you
+  can restart or reschedule jobs automatically if they fail.
+---
+
+# Failure recovery strategies
+
+Most applications deployed in Nomad are either long running services or one time
+batch jobs. They can fail for various reasons like:
+
+- A temporary error in the service that resolves when its restarted.
+
+- An upstream dependency might not be available, leading to a health check
+  failure.
+
+- Disk, Memory or CPU contention on the node that the application is running on.
+
+- The application uses Docker and the Docker daemon on that node is
+  unresponsive.
+
+Nomad provides configurable options to enable recovering failed tasks to avoid
+downtime. Nomad will try to restart a failed task on the node it is running on,
+and also try to reschedule it on another node. Please start with one of the
+guides below or use the navigation on the left for details on each option:
+
+- [Local restarts](/nomad/docs/job-declare/failure/restart)
+- [Health check restarts](/nomad/docs/job-declare/failure/check-restart)
+- [Reschedule](/nomad/docs/job-declare/failure/reschedule)
+
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/failure/reschedule.mdx b/content/nomad/v1.11.x/content/docs/job-declare/failure/reschedule.mdx
new file mode 100644
index 0000000000..0676b3b491
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/failure/reschedule.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Configure reschedule
+description: |-
+  Discover how to control the rescheduling behaviors of jobs to allow them
+  to be scheduled on different nodes if needed, such as in the event of a failure.
+---
+
+# Configure reschedule
+
+Tasks can sometimes fail due to network, CPU or memory issues on the node
+running the task. In such situations, Nomad can reschedule the task on another
+node. The [`reschedule` stanza] can be used to configure how Nomad
+should try placing failed tasks on another node in the cluster. Reschedule
+attempts have a delay between each attempt, and the delay can be configured to
+increase between each rescheduling attempt according to a configurable
+`delay_function`. Consult the [`reschedule` stanza] documentation for more
+information.
+
+Service jobs are configured by default to have unlimited reschedule attempts.
+You should use the reschedule stanza to ensure that failed tasks are
+automatically reattempted on another node without needing operator intervention.
+
+The following CLI example shows job and allocation statuses for a task being
+rescheduled by Nomad. The CLI shows the number of previous attempts if there is
+a limit on the number of reschedule attempts. The CLI also shows when the next
+reschedule will be attempted.
+
+```shell-session
+$ nomad job status demo
+ID            = demo
+Name          = demo
+Submit Date   = 2018-04-12T15:48:37-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = pending
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+demo        0       0         0        2       0         0
+
+Future Rescheduling Attempts
+Task Group  Eval ID   Eval Time
+demo        ee3de93f  5s from now
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status  Created  Modified
+39d7823d  f2c2eaa6  demo        0        run      failed  5s ago   5s ago
+fafb011b  f2c2eaa6  demo        0        run      failed  11s ago  10s ago
+
+```
+
+```shell-session
+$ nomad alloc status 3d0b
+ID                     = 3d0bbdb1
+Eval ID                = 79b846a9
+Name                   = demo.demo[0]
+Node ID                = 8a184f31
+Job ID                 = demo
+Job Version            = 0
+Client Status          = failed
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 15s ago
+Modified               = 15s ago
+Reschedule Attempts    = 3/5
+Reschedule Eligibility = 25s from now
+
+Task "demo" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB  p1: 127.0.0.1:27646
+
+Task Events:
+Started At     = 2018-04-12T20:44:25Z
+Finished At    = 2018-04-12T20:44:25Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type            Description
+2018-04-12T15:44:25-05:00  Not Restarting  Policy allows no restarts
+2018-04-12T15:44:25-05:00  Terminated      Exit Code: 127
+2018-04-12T15:44:25-05:00  Started         Task started by client
+2018-04-12T15:44:25-05:00  Task Setup      Building Task Directory
+2018-04-12T15:44:25-05:00  Received        Task received by client
+
+```
+
+[`reschedule` stanza]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Stanza'
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/failure/restart.mdx b/content/nomad/v1.11.x/content/docs/job-declare/failure/restart.mdx
new file mode 100644
index 0000000000..beba1eae51
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/failure/restart.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Configure restart
+description: |-
+  Discover how to control the restart behaviors of jobs so that Nomad schedules
+  them on different nodes if needed, such as in the event of a failure.
+---
+
+# Configure restart
+
+Nomad will [by default][defaults] attempt to restart a job locally on the node
+that it is running or scheduled to be running on. These defaults vary by the
+scheduler type in use for the job: system, service, or batch.
+
+To customize this behavior, the task group can be annotated with configurable
+options using the [`restart` stanza][restart]. Nomad will restart the failed
+task up to `attempts` times within a provided `interval`. Operators can also
+choose whether to keep attempting restarts on the same node, or to fail the task
+so that it can be rescheduled on another node, via the `mode` parameter.
+
+Setting mode to `fail` in the restart stanza allows rescheduling to occur
+potentially moving the task to another node and is best practice.
+
+The following CLI example shows job status and allocation status for a failed
+task that is being restarted by Nomad. Allocations are in the `pending` state
+while restarts are attempted. The `Recent Events` section in the CLI shows
+ongoing restart attempts.
+
+```shell-session
+$ nomad job status demo
+ID            = demo
+Name          = demo
+Submit Date   = 2018-04-12T14:37:18-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+demo        0       3         0        0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce5bf1d1  8a184f31  demo        0        run      pending  27s ago  5s ago
+d5dee7c8  8a184f31  demo        0        run      pending  27s ago  5s ago
+ed815997  8a184f31  demo        0        run      pending  27s ago  5s ago
+```
+
+In the following example, the allocation `ce5bf1d1` is restarted by Nomad
+approximately every ten seconds, with a small random jitter. It eventually
+reaches its limit of three attempts and transitions into a `failed` state, after
+which it becomes eligible for [rescheduling][rescheduling].
+
+```shell-session
+$ nomad alloc status ce5bf1d1
+ID                     = ce5bf1d1
+Eval ID                = 64e45d11
+Name                   = demo.demo[1]
+Node ID                = a0ccdd8b
+Job ID                 = demo
+Job Version            = 0
+Client Status          = failed
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 56s ago
+Modified               = 22s ago
+
+Task "demo" is "dead"
+Task Resources
+CPU      Memory   Disk     Addresses
+100 MHz  300 MiB  300 MiB
+
+Task Events:
+Started At     = 2018-04-12T22:29:08Z
+Finished At    = 2018-04-12T22:29:08Z
+Total Restarts = 3
+Last Restart   = 2018-04-12T17:28:57-05:00
+
+Recent Events:
+Time                       Type            Description
+2018-04-12T17:29:08-05:00  Not Restarting  Exceeded allowed attempts 3 in interval 5m0s and mode is "fail"
+2018-04-12T17:29:08-05:00  Terminated      Exit Code: 127
+2018-04-12T17:29:08-05:00  Started         Task started by client
+2018-04-12T17:28:57-05:00  Restarting      Task restarting in 10.364602876s
+2018-04-12T17:28:57-05:00  Terminated      Exit Code: 127
+2018-04-12T17:28:57-05:00  Started         Task started by client
+2018-04-12T17:28:47-05:00  Restarting      Task restarting in 10.666963769s
+2018-04-12T17:28:47-05:00  Terminated      Exit Code: 127
+2018-04-12T17:28:47-05:00  Started         Task started by client
+2018-04-12T17:28:35-05:00  Restarting      Task restarting in 11.777324721s
+```
+
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Stanza'
+[defaults]: /nomad/docs/job-specification/restart#restart-parameter-defaults
+[rescheduling]: /nomad/docs/job-specification/reschedule 'Nomad restart Stanza'
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/index.mdx b/content/nomad/v1.11.x/content/docs/job-declare/index.mdx
new file mode 100644
index 0000000000..bbb6e0c2fe
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/index.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Declare a Nomad job
+description: |-
+  This section provides guidance for declaring Nomad job with a job specification.
+---
+
+# Declare a Nomad job
+
+Developers deploy and manage their applications in Nomad via jobs. This section provides guidance for declaring a Nomad job with a job specification.
+
+In Nomad, a job is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into task groups.
+
+Declare the desired state of your job in a [job specification][job-spec], or jobspec, that describes the tasks and resources necessary for the job to run. You can also include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual job state matches your desired
+state.
+
+## Deploy a new Nomad job
+
+The general flow for operating a job in Nomad is:
+
+1. Author the job file according to the [job specification][job-spec].
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+## Update a running job
+
+When updating a job, there are a number of built-in update strategies which may
+be defined in the job file. The general flow for updating an existing job in
+Nomad is:
+
+1. Modify the existing job file with the desired changes.
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Because the job file defines the update strategy (blue-green, rolling updates,
+etc.), the workflow remains the same regardless of whether this is an initial
+deployment or a long-running job.
+
+## Resources
+
+- Refer to the [Job concept page](/nomad/docs/concepts/job) for more information
+  on Nomad jobs.
+- [Nomad job specification][job-spec]
+
+[job-spec]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/multiregion.mdx b/content/nomad/v1.11.x/content/docs/job-declare/multiregion.mdx
new file mode 100644
index 0000000000..11dda700a8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/multiregion.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: Configure multi-region deployments
+description: |-
+  Deploy applications to multiple federated Nomad clusters with configurable
+  rollout and rollback strategies.
+---
+
+# Configure multi-region deployments
+
+Federated Nomad clusters enable you to submit jobs targeting any region
+from any server even if that server resides in a different region. You may submit jobs that are deployed to multiple
+regions. This guide demonstrates multi-region deployments, including
+configurable rollout and rollback strategies.
+
+<EnterpriseAlert/>
+
+You can create a multi-region deployment job by adding a [`multiregion`]
+stanza to the job as shown below.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 1
+    on_failure   = "fail_all"
+  }
+
+  region "west" {
+    count       = 2
+    datacenters = ["west-1"]
+  }
+
+  region "east" {
+    count       = 1
+    datacenters = ["east-1", "east-2"]
+  }
+
+}
+```
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have two Nomad
+environments running Nomad 0.12 or greater with ports 4646, 4647, and 4648 exposed. You can use this
+[Terraform environment][nomad-tf] to provision the sandbox environments. This
+guide assumes two clusters with one server node and two client nodes in each
+cluster. While the Terraform code already opens port 4646, you will also need to
+expose ports 4647 and 4648 on the server you wish to run [nomad server
+join][server-join] against. Consult the [Nomad Port Requirements][ports-used]
+documentation for more information.
+
+Next, you'll need to federate these two regions as described in the [federation guide].
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node in each cluster. Consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+Run the [`nomad server members`][nomad-server-members] command.
+
+```shell-session
+$ nomad server members
+```
+
+After you have federated your clusters, the output should include the servers from both regions.
+
+```plaintext
+Name                     Address        Port  Status  Leader  Protocol  Build       Datacenter  Region
+ip-172-31-26-138.east    172.31.26.138  4648  alive   true    2         0.12.0+ent  east-1      east
+ip-172-31-29-34.west     172.31.29.34   4648  alive   true    2         0.12.0+ent  west-1      west
+```
+
+If you are using [ACLs][acls-track], you'll need to make sure your token has `submit-job`
+permissions with a `global` scope.
+
+You may wish to review the [update strategies guides][updates-track] before
+starting this guide.
+
+## Multi-region concepts
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft/consensus cluster; they don't share their data stores. Each region in a
+multi-region deployment gets an independent copy of the job, parameterized with
+the values of the `region` stanza. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` stanza.
+
+A single region deployment using one of the various [update strategies][updates-track]
+begins in the `running` state and ends in either the `successful` state if it succeeds,
+the `canceled` state if another deployment supersedes it before it's
+complete, or the `failed` state if it fails for any other reason. A failed single
+region deployment may automatically revert to the previous version of the job if
+its [`update` stanza] has the [`auto_revert`][update-auto-revert] setting.
+
+In a multi-region deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point, up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Create a multi-region job
+
+The job below will deploy to both regions. The `max_parallel` field of the
+`strategy` block restricts Nomad to deploy to the regions one at a time. If
+either of the region deployments fail, both regions will be marked as
+failed. The `count` field for each region is interpolated for each region,
+replacing the `count = 0` in the task group count. The job's `update` block
+uses the default ["task states"] value to determine if the job is healthy; if
+you configured a Consul [`service`][consul-service] with health checks you
+could use that instead.
+
+```hcl
+job "example" {
+
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count       = 2
+      datacenters = ["west-1"]
+    }
+
+    region "east" {
+      count       = 1
+      datacenters = ["east-1", "east-2"]
+    }
+
+  }
+
+  update {
+    max_parallel      = 1
+    min_healthy_time  = "10s"
+    healthy_deadline  = "2m"
+    progress_deadline = "3m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+
+
+  group "cache" {
+
+    count = 0
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:6.0"
+
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 256
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+## Run the multi-region job
+
+You can run the job from either region.
+
+```shell-session
+$ nomad job run ./multi.nomad
+```
+
+If successful, you should receive output similar to the following.
+
+```plaintext
+Job registration successful
+Evaluation ID: f71cf273-a29e-65e3-bc5b-9710a3c5bc8f
+```
+
+Check the job status from the east region.
+
+```shell-session
+$ nomad job status -region east example
+```
+
+Note that there are no running allocations in the east region,
+and that the status is "pending" because the east region is waiting
+for the west region to complete.
+
+```plaintext
+...
+Latest Deployment
+ID          = d74a086b
+Status      = pending
+Description = Deployment is pending, waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  pending
+west    48fccef3  running
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       true         1        0       0        0          N/A
+
+Allocations
+No allocations placed
+```
+
+Check the job status from the west region.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+You should observe running allocations.
+
+```plaintext
+...
+Latest Deployment
+ID          = 48fccef3
+Status      = running
+Description = Deployment is running
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  pending
+west    48fccef3  running
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       true         2        2       0        0          2020-06-17T13:35:49Z
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+44b3988a  4786abea  cache       0        run      running  14s ago  13s ago
+7c8a2b80  4786abea  cache       0        run      running  13s ago  12s ago
+```
+
+The west region should be healthy 10s after the task state for all tasks
+switches to "running". To observe, run the following status check.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+At this point, the status for the west region will
+transition to "blocked" and the east region's deployment will become
+"running".
+
+```plaintext
+...
+Latest Deployment
+ID          = 48fccef3
+Status      = blocked
+Description = Deployment is complete but waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  running
+west    48fccef3  blocked
+```
+
+Once the east region's deployment has completed, check the status again.
+
+```shell-session
+$ nomad job status -region east example
+```
+
+Both regions should transition to "successful".
+
+```plaintext
+...
+Latest Deployment
+ID          = d74a086b
+Status      = successful
+Description = Deployment completed successfully
+
+Multiregion Deployment
+Region  ID        Status
+east    d74a086b  successful
+west    48fccef3  successful
+```
+
+## Failed deployments
+
+Next, you'll simulate a failed deployment. First, add a new task group that will
+succeed in the west region but fail in the east region.
+
+```hcl
+group "sidecar" {
+
+  # set the reschedule stanza so that we don't have to wait too long
+  # for the deployment to be marked failed
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+
+  task "sidecar" {
+    driver = "docker"
+
+    config {
+      image   = "busybox:1"
+      command = "/bin/sh"
+      args    = ["local/script.sh"]
+    }
+
+    # this script will always fail in the east region
+    template {
+      destination = "local/script.sh"
+      data        = <<EOT
+if [[ ${NOMAD_REGION} == "east" ]]
+then
+echo FAIL
+exit 1
+fi
+echo OK
+sleep 600
+
+EOT
+
+    }
+
+    resources {
+      cpu    = 128
+      memory = 64
+    }
+  }
+}
+```
+
+Next, change the `on_failure` field of the multiregion strategy to
+`"fail_local"`. This will cause only the failed region to be marked as failed.
+
+```hcl
+strategy {
+  max_parallel = 1
+  on_failure   = "fail_local"
+}
+```
+
+Run the job again.
+
+```shell-session
+$ nomad job run ./multi.nomad
+```
+
+The output should indicate success.
+
+```plaintext
+Job registration successful
+Evaluation ID: e878bb98-6b23-c3de-dce1-10ea37c702f7
+```
+
+Now check the status
+
+```shell-session
+$ nomad job status -region west example
+```
+
+As with the previous version of the job, you should see the deployment in the
+west in the "running" status and the deployment in the east in
+"pending". Eventually, the east region deployment will run and then
+fail. Because `on_failure` was set to `"fail_local"`, the west region remains
+in a "blocked" state:
+
+```plaintext
+Latest Deployment
+ID          = f08122e5
+Status      = blocked
+Description = Deployment is complete but waiting for peer region
+
+Multiregion Deployment
+Region  ID        Status
+east    8b12b453  failed
+west    f08122e5  blocked
+```
+
+At this point, the west region will remain in the blocked state. You can
+either fix the job and redeploy, or accept the west deployment in its current
+state by using the [`nomad deployment unblock`] command.
+
+```shell-session
+$ nomad deployment unblock -region west f08122e5
+```
+
+If successful, the output will be similar to the following.
+
+```plaintext
+Deployment "f08122e5-fc7e-f450-f61e-81ac48db55cb" unblocked
+```
+
+Check the status again.
+
+```shell-session
+$ nomad job status -region west example
+```
+
+The west region should now be marked as successful:
+
+```plaintext
+...
+Latest Deployment
+ID          = f08122e5
+Status      = successful
+Description = Deployment completed successfully
+
+Multiregion Deployment
+Region  ID        Status
+east    8b12b453  failed
+west    f08122e5  successful
+```
+
+## Learn more about federation
+
+- [Deployment Topology across Multiple Regions][multi-region-topology]
+
+[`multiregion`]: /nomad/docs/job-specification/multiregion
+[federation guide]: //nomad/docs/deploy/clusters/federate-regions
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform
+[server-join]: /nomad/commands/server/join
+[ports-used]: /nomad/docs/deploy/production/requirements#ports-used
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture
+[nomad-server-members]: /nomad/commands/server/members
+[acls-track]: /nomad/docs/secure/acl
+[updates-track]: /nomad/docs/job-declare/strategy/
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+["task states"]: /nomad/docs/job-specification/update#health_check
+[consul-service]: /nomad/docs/job-specification/service
+[alloc-health-api]: /nomad/api-docs/deployments#set-allocation-health-in-deployment
+[`update` stanza]: /nomad/docs/job-specification/update
+[`nomad deployment unblock`]: /nomad/commands/deployment/unblock
+[multi-region-topology]:/nomad/docs/deploy/production/reference-architecture#multi-region
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/nomad-actions.mdx b/content/nomad/v1.11.x/content/docs/job-declare/nomad-actions.mdx
new file mode 100644
index 0000000000..fce75572b9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/nomad-actions.mdx
@@ -0,0 +1,550 @@
+---
+layout: docs
+page_title: Use Nomad actions in jobs
+description: |-
+  Create a Nomad Action in a job to read from a Redis database. Discover
+  how to use Actions for repeatable workflows and indefinitely running
+  workflows.
+---
+
+# Use Nomad actions in jobs
+
+In this tutorial you will create and run Nomad Actions in a job. Actions are commands that a job author writes, and take the same form as [task config][task-config].
+
+```hcl
+action "hello-world" {
+  command = "echo"
+  args    = ["Hello, world!"]
+}
+```
+
+These actions live at Task level within a jobspec and run without variables or interactive input after execution. Like other executable commands, they may self-terminate or run until manually terminated by the running user. Nomad provides the [CLI command][cli-job-actions], [API][api-run-action], and Web UI to interact with Actions within the context of a Job or Task.
+
+## Challenge
+
+In this tutorial, you will modify a Nomad job that runs a Redis instance and create repeatable Nomad Actions to:
+
+- simplify common workflows to add and remove entries from the database
+- monitor and report on attributes of those entries, as well as latency of the Redis instance
+- modify core behaviour of the database
+
+## Prerequisites
+
+- [Nomad v1.7.0 or greater][install-nomad]
+- Nomad dev agent or [Nomad cluster][setup-cluster]
+- [Docker](https://docs.docker.com/engine/install/) installed and available as a task driver
+
+## Build the starting job file
+
+Create a text file called `redis-actions.nomad.hcl` with the following content:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+job "redis-actions" {
+
+  group "cache" {
+    network {
+      port "db" {}
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image   = "redis:7"
+        ports   = ["db"]
+        command = "/bin/sh"
+        args    = ["-c", "redis-server --port ${NOMAD_PORT_db} & /local/db_log.sh"]
+      }
+
+      template {
+        data        = <<EOF
+          #!/bin/sh
+          while true; do
+            echo "$(date): Current DB Size: $(redis-cli -p ${NOMAD_PORT_db} DBSIZE)"
+            sleep 3
+          done
+EOF
+        destination = "local/db_log.sh"
+        perms       = "0755"
+      }
+
+      resources {
+        cpu    = 128
+        memory = 128
+      }
+
+      service {
+        name     = "redis-service"
+        port     = "db"
+        provider = "nomad"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+This job creates a single Redis instance, with a port called "db" that Nomad dynamically assigns and a Nomad service health check in place. The task's [config][jobspec-task-config-block] and [template][jobspec-task-template-block] blocks start the redis server and report on current database size every 3 seconds.
+
+## Write your first Action
+
+If you were a user with management or `alloc-exec` privileges, you could add data to your Redis instance by ssh-ing into the running instance. However, this has several drawbacks:
+- You might have to ssh into the instance several times to add data at different points, requiring you to remember how to do it. Or worse: another operator less familiar with the process may have to do so.
+- There is no auditable record of manual additions. If you need to repeat or scale the workflow, you would have to do so manually.
+- Your Nomad task may have access to Redis using managed secrets or environment variables, but you as a user may not. Passing credentials manually, either to access Redis or ssh into your Nomad instance, opens up a repeated access hole in the security of your workflow.
+
+Instead of `ssh`ing into the box and executing the `redis-cli SET` command over and over again, you will commit it as an action to the jobspec's task. Add the following to the `service` block of the task:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a specific key-value pair ('hello'/'world') to the Redis database
+action "add-key" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} SET hello world; echo 'Key \"hello\" added with value \"world\"'"]
+}
+```
+</CodeBlockConfig>
+
+This action uses the `redis-cli` command to set a key-value pair and then outputs a confirmation message.
+
+Now, submit your job:
+
+```shell-session
+$ nomad job run redis-actions.nomad.hcl
+```
+
+The job will update with a new action available. Use the Nomad CLI to execute it, supplying the job, group, task, and action name:
+
+```shell-session
+$ nomad action \
+  -job=redis-actions \
+  -group=cache \
+  -task=redis \
+add-key
+```
+
+You should see the output described in our action to indicate the key was added:
+
+```shell-session
+OK
+Key "hello" added with value "world"
+```
+
+You've just executed a command defined in the jobspec of your running Nomad job.
+
+## Simulate a repeatable workflow
+
+An action that applies a constant state can be useful (an action that manually clears a cache, or that puts a site into maintenance mode, for example). However, for this example, simulate an action that someone might want to take many times. Instead of a constant key/value, modify the action to randomly generate strings. You can think of this action as a proxy for a real-world scenario where a persistent artifact is saved upon user sign-up, or another public-facing action.
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a random key/value to the Redis database
+action "add-random-key" {
+  command = "/bin/sh"
+  args    = ["-c", "key=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+}
+```
+</CodeBlockConfig>
+
+This will add a random key/value to the database and report back. We can add a second action that differs only in that it prepends "temp_" to the key, to help illustrate further functionality:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Adds a random key/value with a "temp_" prefix to the Redis database
+action "add-random-temporary-key" {
+  command = "/bin/sh"
+  args    = ["-c", "key=temp_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+}
+```
+</CodeBlockConfig>
+
+Like our `add-random-key` action, this new action might be thought of as a simulation of an application generating persistent artifacts. In the case of these temp keys, a real-world scenario might be keys to indicate user sign-up email verification. Soon, we will create a further Action that treats these random keys differently depending on their prefix.
+
+These two actions will populate the database with random data of two different sorts. Now, create an action to view the keys we've added by appending the following code block:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Lists all keys currently stored in the Redis database.
+action "list-keys" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} KEYS '*'"]
+}
+```
+</CodeBlockConfig>
+
+Now, update your job:
+
+```shell-session
+$ nomad job run redis-actions.nomad.hcl
+```
+
+If you have the [Nomad Web UI][web-ui] running, accessing your Job page should show an Actions drop-down:
+
+[![Nomad Job page with Actions dropdown open][actions-dropdown]][actions-dropdown]
+
+Selecting one of those actions will open a fly-out, complete with output from your selected action:
+
+[![Nomad Job page with Actions flyout open][actions-flyout]][actions-flyout]
+
+Next, append a new action block that creates a "safety valve" action to clear the temporary keys from our database. This uses our earlier `add-random-key` and `add-random-temporary-key` actions by differentiating between the artifacts they generated.
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Deletes all keys with a 'temp_' prefix
+action "flush-temp-keys" {
+  command = "/bin/sh"
+  args    = ["-c", <<EOF
+    keys_to_delete=$(redis-cli -p ${NOMAD_PORT_db} --scan --pattern 'temp_*')
+    if [ -n "$keys_to_delete" ]; then
+      # Count the number of keys to delete
+      deleted_count=$(echo "$keys_to_delete" | wc -l)
+      # Execute the delete command
+      echo "$keys_to_delete" | xargs redis-cli -p ${NOMAD_PORT_db} DEL
+    else
+      deleted_count=0
+    fi
+    remaining_keys=$(redis-cli -p ${NOMAD_PORT_db} DBSIZE)
+    echo "$deleted_count temporary keys removed; $remaining_keys keys remaining in database"
+EOF
+  ]
+}
+```
+</CodeBlockConfig>
+
+In a real-world scenario, for example, an action like this might filter and clear automatically-added entries, and report back on remaining keys or time taken to delete them.
+
+You can run this job from the command line in two ways:
+
+1: When your task is running on a single allocation, or you want to perform the action on a random allocation running your task:
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+flush-temp-keys
+```
+
+2: When you want to perform the action on a specific, known allocation, first get its allocation ID:
+
+```shell-session
+$ nomad job status redis-actions
+```
+
+Nomad CLI should show information about the jobspec, including the following:
+
+```
+ID            = redis-actions
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+d841c716  03a56d12  cache       0        run      running  5m4s ago  4m48s ago
+```
+
+Copy the ID from the Allocation displayed and run the following to perform the `flush-temp-keys` action upon it:
+
+```shell-session
+$ nomad action \
+  -alloc=d841c716 \
+  -job=redis-actions \
+flush-temp-keys
+```
+
+If the action being run is not allocation dependent, use the first method. If your job hosted multiple instances of Redis and you need to clear the cache of a specific one, use the second method. In the real world, the method you chose will depend on your goal.
+
+## Actions can impact the running task
+
+Some actions might not affect the current state of the application. For example, processing logs, reporting and sending server statistics, revoking tokens, etc. But, in this example, the action does impact the active state of the task. The Redis task has been writing its `DBSIZE` to `db_log.sh` and logging it every few seconds. Inspect the running job and get its allocation ID. Then, run the following:
+
+```shell-session
+nomad alloc logs <alloc-id>
+```
+
+Nomad outputs the logs for the allocation ID of the job:
+
+```shell-session
+Tue Nov 28 01:23:46 UTC 2023: Current DB Size: 1
+Tue Nov 28 01:23:49 UTC 2023: Current DB Size: 1
+Tue Nov 28 01:23:52 UTC 2023: Current DB Size: 2
+Tue Nov 28 01:23:55 UTC 2023: Current DB Size: 3
+Tue Nov 28 01:23:58 UTC 2023: Current DB Size: 3
+Tue Nov 28 01:24:01 UTC 2023: Current DB Size: 4
+Tue Nov 28 01:24:04 UTC 2023: Current DB Size: 5
+Tue Nov 28 01:24:07 UTC 2023: Current DB Size: 8
+```
+
+Now add another action to impact a more low-level configuration option for our application. Redis lets us turn its persistence to disk on and off. Write an Action to check this and then flip it. Append the following action block:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Toggles saving to disk (RDB persistence). When enabled, allocation logs will indicate a save every 60 seconds.
+action "toggle-save-to-disk" {
+  command = "/bin/sh"
+  args    = ["-c", <<EOF
+    current_config=$(redis-cli -p ${NOMAD_PORT_db} CONFIG GET save | awk 'NR==2');
+    if [ -z "$current_config" ]; then
+      # Enable saving to disk (example: save after 60 seconds if at least 1 key changed)
+      redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "60 1";
+      echo "Saving to disk enabled: 60 seconds interval if at least 1 key changed";
+    else
+      # Disable saving to disk
+      redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "";
+      echo "Saving to disk disabled";
+    fi;
+EOF
+  ]
+}
+```
+</CodeBlockConfig>
+
+Enabling RDB snapshotting with the above will modify the output in your application logs, too.
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+toggle-save-to-disk
+```
+
+Nomad returns a confirmation that the action run and that saving to disk is enabled.
+
+```shell-session
+OK
+Saving to disk enabled: 60 seconds interval if at least 1 key changed
+```
+
+Access your server logs and find the lines that show Redis saving the snapshot:
+
+```shell-session
+Tue Nov 28 01:31:14 UTC 2023: Current DB Size: 12
+28 Nov 01:31:17.800 * 2 changes in 60 seconds. Saving...
+28 Nov 01:31:17.800 * Background saving started by pid 36652
+28 Nov 01:31:17.810 * DB saved on disk
+28 Nov 01:31:17.810 * RDB: 0 MB of memory used by copy-on-write
+28 Nov 01:31:17.902 * Background saving terminated with success
+Tue Nov 28 01:31:17 UTC 2023: Current DB Size: 12
+```
+
+Nomad Actions can impact the state and behaviour of the very task on which they're running. Keeping this in mind can help developers and platform teams separate business and operational logic in their applications.
+
+## Indefinite and self-terminating actions
+
+All of the actions so far have been self-terminating: they execute a command that completes and signals its completion. However, Actions will wait for completion of the desired task, and the Nomad API and Web UI use websockets to facilitate this.
+
+Add an action that runs until you manually stop it with a signal interruption, like `ctrl + c` to observe the latency of the Redis instance:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+# Performs a latency check of the Redis server.
+# This action is a non-terminating action, meaning it will run indefinitely until it is stopped.
+# Pass a signal interruption (Ctrl-C) to stop the action.
+action "health-check" {
+  command = "/bin/sh"
+  args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} --latency"]
+}
+```
+</CodeBlockConfig>
+
+Submit the job and run the action with the following:
+
+```shell-session
+$ nomad action \
+  -group=cache \
+  -task=redis \
+  -job=redis-actions \
+  -t=true \
+health-check
+```
+
+The output should indicate the minimum, maximum, and average latency in ms for our Redis instance. Interrupting the signal or closing the websocket will end the action's execution.
+
+[![Non-terminating Nomad Action run via the UI][actions-health-check]][actions-health-check]
+
+## Wrap-up
+
+Find the complete Redis job with actions (with a few extras thrown in) below:
+
+<CodeBlockConfig filename="redis-actions.nomad.hcl">
+
+```hcl
+job "redis-actions" {
+
+  group "cache" {
+    network {
+      port "db" {}
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image   = "redis:7"
+        ports   = ["db"]
+        command = "/bin/sh"
+        args    = ["-c", "redis-server --port ${NOMAD_PORT_db} & /local/db_log.sh"]
+      }
+
+      template {
+        data        = <<EOF
+#!/bin/sh
+while true; do
+  echo "$(date): Current DB Size: $(redis-cli -p ${NOMAD_PORT_db} DBSIZE)"
+  sleep 3
+done
+EOF
+        destination = "local/db_log.sh"
+        perms       = "0755"
+      }
+
+      resources {
+        cpu    = 128
+        memory = 128
+      }
+
+      service {
+        name     = "redis-service"
+        port     = "db"
+        provider = "nomad"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+
+      # Adds a random key/value to the Redis database
+      action "add-random-key" {
+        command = "/bin/sh"
+        args    = ["-c", "key=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+      }
+
+      # Adds a random key/value with a "temp_" prefix to the Redis database
+      action "add-random-temporary-key" {
+        command = "/bin/sh"
+        args    = ["-c", "key=temp_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); value=$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13); redis-cli -p ${NOMAD_PORT_db} SET $key $value; echo Key $key added with value $value"]
+      }
+
+      # Lists all keys currently stored in the Redis database.
+      action "list-keys" {
+        command = "/bin/sh"
+        args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} KEYS '*'"]
+      }
+
+      # Performs a latency check of the Redis server.
+      # This action is a non-terminating action, meaning it will run indefinitely until it is stopped.
+      # Pass a signal interruption (Ctrl-C) to stop the action.
+      action "health-check" {
+        command = "/bin/sh"
+        args    = ["-c", "redis-cli -p ${NOMAD_PORT_db} --latency"]
+      }
+
+      # Deletes all keys with a 'temp_' prefix
+      action "flush-temp-keys" {
+        command = "/bin/sh"
+        args    = ["-c", <<EOF
+keys_to_delete=$(redis-cli -p ${NOMAD_PORT_db} --scan --pattern 'temp_*')
+if [ -n "$keys_to_delete" ]; then
+  # Count the number of keys to delete
+  deleted_count=$(echo "$keys_to_delete" | wc -l)
+  # Execute the delete command
+  echo "$keys_to_delete" | xargs redis-cli -p ${NOMAD_PORT_db} DEL
+else
+  deleted_count=0
+fi
+remaining_keys=$(redis-cli -p ${NOMAD_PORT_db} DBSIZE)
+echo "$deleted_count temporary keys removed; $remaining_keys keys remaining in database"
+EOF
+        ]
+      }
+
+      # Toggles saving to disk (RDB persistence). When enabled, allocation logs will indicate a save every 60 seconds.
+      action "toggle-save-to-disk" {
+        command = "/bin/sh"
+        args    = ["-c", <<EOF
+current_config=$(redis-cli -p ${NOMAD_PORT_db} CONFIG GET save | awk 'NR==2');
+if [ -z "$current_config" ]; then
+  # Enable saving to disk (example: save after 60 seconds if at least 1 key changed)
+  redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "60 1";
+  echo "Saving to disk enabled: 60 seconds interval if at least 1 key changed";
+else
+  # Disable saving to disk
+  redis-cli -p ${NOMAD_PORT_db} CONFIG SET save "";
+  echo "Saving to disk disabled";
+fi;
+EOF
+        ]
+      }
+    }
+  }
+}
+```
+</CodeBlockConfig>
+
+Experiment with duplicating and modifying these actions to explore the potential of an actions-based workflow in Nomad.
+
+To further explore how Actions can be used in your workflows, consider the following:
+
+- The examples above are mostly self-contained in that they run in isolation on a single allocation within a job with only one task group and task. Try creating a job with multiple groups and tasks whose actions can talk to one another by way of service discovery.
+- Try using the [GET job actions endpoint][api-list-job-actions] to see a list of actions available to a job and its groups and tasks
+- Try writing an action that takes advantage of Nomad's environment variables: for example, the following actions are illustrative of how an operator might add shortcuts to their Nomad jobs to get a sense of system state:
+
+```hcl
+action "get-alloc-info" {
+  command = "/bin/sh"
+  args    = ["-c",
+    <<EOT
+    nomad alloc status ${NOMAD_ALLOC_ID}
+    EOT
+  ]
+}
+action "get-event-stream" {
+  command = "/usr/bin/curl"
+  args    = ["-s", "localhost:4646/v1/event/stream", " | ", "jq"]
+}
+```
+
+## Clean up
+
+To stop your Nomad actions job, use the Nomad CLI:
+
+```shell-session
+$ nomad job stop redis-actions
+```
+
+The jobspec you wrote will remain on your filesystem, but the resources used by running the job will free up and Nomad will automatically garbage collect the stopped job after awhile.
+
+
+[api-run-action]: /nomad/api-docs/jobs#run-action
+[api-list-job-actions]: /nomad/api-docs/jobs#list-job-actions
+[cli-job-actions]: /nomad/commands/job/action
+[task-config]: /nomad/docs/job-declare/configure-tasks#define-application-arguments
+[web-ui]: /nomad/tutorials/web-ui
+[actions-dropdown]: /img/nomad/actions/actions-dropdown.png
+[actions-flyout]: /img/nomad/actions/actions-flyout.png
+[actions-health-check]: /img/nomad/actions/actions-health-check.png
+[jobspec-task-template-block]: /nomad/docs/job-specification/template
+[jobspec-task-config-block]: /nomad/docs/job-specification/task#config
+[install-nomad]: /nomad/install
+[setup-cluster]: /nomad/tutorials/get-started/gs-start-a-cluster
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/nomad-variables.mdx b/content/nomad/v1.11.x/content/docs/job-declare/nomad-variables.mdx
new file mode 100644
index 0000000000..63a23e3a4a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/nomad-variables.mdx
@@ -0,0 +1,481 @@
+---
+layout: docs
+page_title: Use Nomad variables in tasks
+description: |-
+  Discover how Nomad's workload identity grants tasks automatic read access to
+  certain Nomad variables.
+---
+
+# Use Nomad variables in tasks
+
+In this tutorial you'll access [Nomad Variables][] from tasks via the
+[`template`][] block. Tasks have implicit ACL policies that allow them to access
+their own variables, and you can add job, group, and task fields to ACL policies
+to extend these permissions.
+
+<Note>
+
+ You should always protect access to variables with Access Control
+Lists (ACLs). Writing ACL policies for variables is covered in the [Nomad
+Variables Access Control][] tutorial
+
+</Note>
+
+For complete documentation on the Nomad Variables feature and related concepts,
+see the [Variables reference documentation][], the [Key Management
+documentation][], and the [Workload Identity documentation][]
+
+## Automatic access
+
+The [workload identity][] for each task grants it automatic read and list access
+to variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed
+by the job ID, task group name, and task name.
+
+If you've completed the [Nomad Variables Access Control][] tutorial, you will
+have a "prod" namespace and a token associated with the "prod-ops" policy. If
+not, you can use a management token for this section and create the "prod"
+namespace.
+
+```shell-session
+$ nomad namespace apply -description "production environment" prod
+Successfully applied namespace "prod"!
+```
+
+In this tutorial you'll be working in the "prod" namespace. Set the
+`NOMAD_NAMESPACE` variable so that the command line writes all variables to that
+namespace.
+
+```shell-session
+export NOMAD_NAMESPACE=prod
+```
+
+Create the following variables to see how different jobs, groups, and tasks can
+access them.
+
+```shell-session
+nomad var put nomad/jobs password=passw0rd1
+nomad var put nomad/jobs/example person_to_greet=alice
+nomad var put nomad/jobs/example/web foo=1 bar=2 baz=3
+nomad var put nomad/jobs/example/web/httpd port=8001
+nomad var put nomad/jobs/example/web/sidecar password=passw0rd2
+```
+
+Create the following job specification. This job `example` has one group `web`
+with two tasks, `httpd` and `sidecar`. It includes templates that access all the
+variables you wrote earlier.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "web" {
+
+    network {
+      port "www" {
+        to = 8001
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "httpd"
+        args    = ["-v", "-f", "-p", "0.0.0.0:${PORT}", "-h", "${NOMAD_ALLOC_DIR}/data"]
+        ports   = ["www"]
+      }
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/env.txt"
+        env         = true
+        data        = <<EOT
+PORT={{ with nomadVar "nomad/jobs/example/web/httpd" }}{{ .port }}{{ end }}
+EOT
+      }
+
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/index.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+    {{- with nomadVar "nomad/jobs/example/web" -}}
+    {{- range $k, $v := . }}
+      <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+EOT
+      }
+    }
+
+    task "sidecar" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "sleep"
+        args    = ["300"]
+      }
+
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/sidecar.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      {{- range nomadVarList "nomad" }}
+      <li>{{ .Path }}</li>
+      {{- end }}
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+EOT
+      }
+    }
+  }
+}
+```
+
+Run this job and wait for the deployment to complete and note the allocation
+short ID. In this example, the allocation short ID is `ec6dc2e4`.
+
+```shell-session
+$ nomad job run ./example.nomad.hcl
+==> 2022-09-19T11:42:20-04:00: Monitoring evaluation "0d8a7587"
+    2022-09-19T11:42:20-04:00: Evaluation triggered by job "example"
+    2022-09-19T11:42:20-04:00: Evaluation within deployment: "b58da4d8"
+    2022-09-19T11:42:20-04:00: Allocation "ec6dc2e4" created: node "9063a25f", group "web"
+    2022-09-19T11:42:20-04:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-09-19T11:42:20-04:00: Evaluation "0d8a7587" finished with status "complete"
+==> 2022-09-19T11:42:20-04:00: Monitoring deployment "b58da4d8"
+  ✓ Deployment "b58da4d8" successful
+
+    2022-09-19T11:42:32-04:00
+    ID          = b58da4d8
+    Job ID      = example
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    web         1        1       1        0          2022-09-19T15:52:31Z
+```
+
+First, use `nomad alloc exec` to enter the `httpd` task and show the command
+line arguments for the processes running in the container.
+
+```shell-session
+$ nomad alloc exec -task httpd ec6dc2e4 ps -ef
+PID   USER     TIME  COMMAND
+    1 root      0:00 httpd -v -f -p 0.0.0.0:8001 -h /alloc/data
+    8 root      0:00 ps -ef
+```
+
+Note that the port number has been interpolated with environment variable that
+you rendered in the following template by using the `env` field:
+
+```hcl
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/env.txt"
+        env         = true
+        data        = <<EOT
+PORT={{ with nomadVar "nomad/jobs/example/web/httpd" }}{{ .port }}{{ end }}
+EOT
+      }
+```
+
+Visit the web page being served by the `httpd` task at port 8001. If you are
+running Nomad on macOS and are using Docker for Mac to run Docker tasks, you can
+reach the webpage at your localhost address.
+
+If you are deploying to a remote Linux host or Vagrant box, you can use the IP
+address found when you run `nomad alloc status`:
+
+```shell-session
+$ nomad alloc status ec6dc2e4
+...
+Allocation Addresses (mode = "bridge"):
+Label  Dynamic  Address
+*www   yes      127.0.0.1:21976 -> 8001
+```
+
+You can also use `curl`:
+
+```shell-session
+
+$ curl 127.0.0.1:21976
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+      <li>bar=2</li>
+      <li>baz=3</li>
+      <li>foo=1</li>
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+```
+
+This corresponds to this template block that reads the variable accessible to
+the job "example" at `nomad/jobs/example` and the variable accessible to the
+group "web" within the job "example" at `nomad/jobs/example/web`.
+
+```hcl
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/index.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the group variable:</p>
+    <ul>
+    {{- with nomadVar "nomad/jobs/example/web" -}}
+    {{- range $k, $v := . }}
+      <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+    <p><a href="/sidecar.html">View the output from the sidecar task.</a></p>
+  </body>
+</html>
+EOT
+```
+
+Visit the webpage rendered by the sidecar task:
+
+```shell-session
+curl -s http://127.0.0.1:21976/sidecar.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      <li>nomad/jobs</li>
+      <li>nomad/jobs/example</li>
+      <li>nomad/jobs/example/web</li>
+      <li>nomad/jobs/example/web/sidecar</li>
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+```
+
+This corresponds to the following template block, which lists all the variables
+this task has access to in its own namespace:
+
+```
+      template {
+        destination = "${NOMAD_ALLOC_DIR}/data/sidecar.html"
+        change_mode = "noop"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Sidecar</title></head>
+  <body>
+    <p>The task has access to the following variables:</p>
+    <ul>
+      {{- range nomadVarList "nomad" }}
+      <li>{{ .Path }}</li>
+      {{- end }}
+    </ul>
+    <p><a href="/">View the index page.</a></p>
+  </body>
+</html>
+EOT
+      }
+```
+
+Note that `nomad/jobs/example/httpd` does not appear in the list. If you added a
+variable to `nomad/jobs/another-example` it would also not appear in the
+list. If you added `nomad/jobs/example/sidecar` to a different namespace, it
+would not appear in the list.
+
+## Workload associated ACL policies
+
+You may need to give tasks access to variables that are on paths shared by many
+jobs. For example, all jobs in your cluster may need a shared API key for a
+third-party monitoring vendor. You can provide access to these variables secrets
+by creating policies associated with the task's [workload identity][]. See
+[Workload Associated ACL Policies][] for full documentation.
+
+Create a new namespace named `shared`.
+
+```shell-session
+$ nomad namespace apply shared
+Successfully applied namespace "shared"!
+```
+
+Create a variable named `vendor/foo/bar` in the `shared` namespace.
+
+```shell-session
+nomad var put -namespace shared vendor/foo/bar user=me password=passw0rd1
+```
+
+To give the task you wrote earlier access to all secrets in the `shared`
+namespace, you can create the following policy file `shared-policy.hcl`.
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Now, create the policy and associate it with the `httpd` task in the web group
+of the example job, specifying the appropriate flags on the `nomad acl policy
+apply` command.
+
+```shell-session
+nomad acl policy apply \
+   -namespace prod -job example -group web -task httpd \
+   shared-policy ./shared-policy.hcl
+```
+
+You can view the policy to see that it's associated with the workload.
+
+```shell-session
+$ nomad acl policy info shared-policy
+Name        = shared-policy
+Description = <none>
+CreateIndex = 390
+ModifyIndex = 390
+
+Associated Workload
+Namespace = prod
+JobID     = example
+Group     = web
+Task      = httpd
+
+Rules
+
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Change the template for the `httpd` task.
+
+```hcl
+      template {
+        destination = "alloc/index.html"
+        data        = <<EOT
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, {{ with nomadVar "nomad/jobs/example" }}{{ .person_to_greet }}{{ end }}!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    {{- with nomadVar "vendor/foo/bar@shared" }}
+    {{- range $k, $v := . }}
+    <li>{{ $k }}={{ $v }}</li>
+    {{- end }}
+    {{- end }}
+    </ul>
+  </body>
+</html>
+EOT
+```
+
+Update the job and wait for the deployment to complete.
+
+```shell-session
+nomad job run ./example.nomad.hcl
+```
+
+Visit the webpage served by the `httpd` task.
+
+```shell-session
+curl -s http://127.0.0.1:8001/index.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    <li>password=passw0rd1</li>
+    <li>user=me</li>
+    </ul>
+  </body>
+</html>
+```
+
+## Updating task variables
+
+You can update the value of a variable and it will be updated in the templates
+that read that value.
+
+Update the shared variable so that the "password" field changes.
+
+```shell-session
+nomad var put -namespace shared -force vendor/foo/bar user=me password=passw0rd2
+```
+
+After a few moments, the value will be updated on the template.
+
+```shell-session
+curl -s http://127.0.0.1:8001/index.html
+<!DOCTYPE html>
+<html lang="en">
+  <head><meta charset="utf-8"><title>Hello Variables - Index</title></head>
+  <body>
+    <p>Hello, alice!</p>
+    <p>Here is the shared variable:</p>
+    <ul>
+    <li>password=passw0rd2</li>
+    <li>user=me</li>
+    </ul>
+  </body>
+</html>
+```
+
+You can use the template
+[`change_mode`](/nomad/docs/job-specification/template#change_mode)
+to specify Nomad's behavior when a value changes.
+
+## Next steps
+
+Because Nomad Variables use functions in the template block to emit data to
+Nomad jobs, consider learning more about templates in Nomad with [Nomad Pack](/nomad/tools/nomad-pack).
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[Nomad Variables Access Control]: /nomad/tutorials/variables/variables-acls
+[Variables reference documentation]: /nomad/docs/concepts/variables
+[Key Management documentation]: /nomad/docs/manage/key-management
+[Workload Identity documentation]: /nomad/docs/concepts/workload-identity
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`template`]: /nomad/docs/job-specification/template
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/strategy/blue-green-canary.mdx b/content/nomad/v1.11.x/content/docs/job-declare/strategy/blue-green-canary.mdx
new file mode 100644
index 0000000000..b794016942
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/strategy/blue-green-canary.mdx
@@ -0,0 +1,474 @@
+---
+layout: docs
+page_title: Configure blue-green and canary deployments
+description: |-
+  Set up and configure Nomad jobs to deploy using the blue-green and
+  canary deployment strategies.
+---
+
+# Configure blue-green and canary deployments
+
+Sometimes [rolling updates] do not offer the required flexibility for updating
+an application in production. Often organizations prefer to put a "canary" build
+into production or utilize a technique known as a "blue/green" deployment to
+ensure a safe application roll-out to production while minimizing downtime.
+
+## Blue/Green deployments
+
+Blue/Green deployments have several other names including Red/Black or A/B, but
+the concept is generally the same. In a blue/green deployment, there are two
+application versions. Only one application version is active at a time, except
+during the transition phase from one version to the next. The term "active"
+tends to mean "receiving traffic" or "in service".
+
+Imagine a hypothetical API server which has five instances deployed to
+production at version 1.3, and you want to safely update to version 1.4. You
+want to create five new instances at version 1.4 and in the case that they are
+operating correctly you want to promote them and take down the five versions
+running 1.3. In the event of failure, you can quickly rollback to 1.3.
+
+To start, you examine your job which is running in production:
+
+```hcl
+job "docs" {
+  # ...
+
+  group "api" {
+    count = 5
+
+    update {
+      max_parallel     = 1
+      canary           = 5
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+      auto_revert      = true
+      auto_promote     = false
+    }
+
+    task "api-server" {
+      driver = "docker"
+
+      config {
+        image = "api-server:1.3"
+      }
+    }
+  }
+}
+```
+
+Notice that the job has an `update` stanza with the `canary` count equal to the
+desired count. This allows a Nomad job to model blue/green deployments. When you
+change the job to run the "api-server:1.4" image, Nomad will create five new
+allocations while leaving the original "api-server:1.3" allocations running.
+
+Observe how this works by changing the image to run the new version:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+  group "api" {
+    task "api-server" {
+      config {
+-       image = "api-server:1.3"
++       image = "api-server:1.4"
+```
+
+Next, plan these changes. Save the modified jobspec with the new version of `api-server` to a file name `docs.nomad.hcl`.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "api" (5 canary, 5 ignore)
+  +/- Task: "api-server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "api-server:1.3" => "api-server:1.4"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Run the changes.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+## ...
+```
+
+The plan output states that Nomad is going to create five canaries running the
+"api-server:1.4" image and ignore all the allocations running the older image.
+Now, if you examine the status of the job you will note that both the blue
+("api-server:1.3") and green ("api-server:1.4") set are running.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         10       0       0         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         false     5        5         5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+6d8eec42  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+7051480e  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+36c6610f  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+410ba474  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+85662a7a  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+```
+
+Now that the new version is running in production, you can route traffic to it
+and validate that it is working properly. If so, you would promote the
+deployment and Nomad would stop allocations running the older version. If not,
+you would either troubleshoot one of the running containers or destroy the new
+containers by failing the deployment.
+
+### Promote the deployment
+
+After deploying the new image along side the old version you have determined it
+is functioning properly and you want to transition fully to the new version.
+Doing so is as simple as promoting the deployment:
+
+```shell-session
+$ nomad deployment promote 32a080c1
+==> Monitoring evaluation "61ac2be5"
+    Evaluation triggered by job "docs"
+    Evaluation within deployment: "32a080c1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61ac2be5" finished with status "complete"
+```
+
+If you inspect the job's status, you can observe that after promotion, Nomad
+stopped the older allocations and is only running the new one. This now
+completes the blue/green deployment.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       5         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         true      5        5         5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+6d8eec42  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+7051480e  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+36c6610f  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+410ba474  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+85662a7a  087852e2  api         1        run      running   07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        stop     complete  07/26/17 19:53:56 UTC
+```
+
+### Fail a deployment
+
+After deploying the new image alongside the old version you have determined it
+is not functioning properly and you want to roll back to the old version. Doing
+so is as simple as failing the deployment:
+
+```shell-session
+$ nomad deployment fail 32a080c1
+Deployment "32a080c1-de5a-a4e7-0218-521d8344c328" failed. Auto-reverted to job version 0.
+
+==> Monitoring evaluation "6840f512"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "32a080c1"
+    Allocation "0ccb732f" modified: node "36e7a123", group "cache"
+    Allocation "64d4f282" modified: node "36e7a123", group "cache"
+    Allocation "664e33c7" modified: node "36e7a123", group "cache"
+    Allocation "a4cb6a4b" modified: node "36e7a123", group "cache"
+    Allocation "fdd73bdd" modified: node "36e7a123", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6840f512" finished with status "complete"
+```
+
+After failing the deployment, check the job's status. Confirm that Nomad has
+stopped the new allocations and is only running the old ones, and that the working
+copy of the job has reverted back to the original specification running "api-server:1.3".
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       5         0
+
+Latest Deployment
+ID          = 6f3f84b3
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy
+cache       true         5        5       5        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+27dc2a42  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+5b7d34bb  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+983b487d  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+d1cbf45a  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+d6b46def  36e7a123  api         1        stop     complete  07/26/17 20:07:31 UTC
+0ccb732f  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+64d4f282  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+664e33c7  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+a4cb6a4b  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+fdd73bdd  36e7a123  api         2        run      running   07/26/17 20:06:29 UTC
+```
+
+```shell-session
+$ nomad job deployments docs
+ID        Job ID   Job Version  Status      Description
+6f3f84b3  example  2            successful  Deployment completed successfully
+32a080c1  example  1            failed      Deployment marked as failed - rolling back to job version 0
+c4c16494  example  0            successful  Deployment completed successfully
+```
+
+## Deploy with canaries
+
+Canary updates are a useful way to test a new version of a job before beginning
+a rolling update. The `update` stanza supports setting the number of canaries
+the job operator would like Nomad to create when the job changes via the
+`canary` parameter. When the job specification is updated, Nomad creates the
+canaries without stopping any allocations from the previous job.
+
+This pattern allows operators to achieve higher confidence in the new job
+version because they can route traffic, examine logs, etc, to determine the new
+application is performing properly.
+
+```hcl
+job "docs" {
+  # ...
+
+  group "api" {
+    count = 5
+
+    update {
+      max_parallel     = 1
+      canary           = 1
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+      auto_revert      = true
+      auto_promote     = false
+    }
+
+    task "api-server" {
+      driver = "docker"
+
+      config {
+        image = "api-server:1.3"
+      }
+    }
+  }
+}
+```
+
+In the example above, the `update` stanza tells Nomad to create a single canary
+when the job specification is changed.
+
+You can experience how this behaves by changing the image to run the new
+version:
+
+```diff
+@@ -2,6 +2,8 @@ job "docs" {
+  group "api" {
+    task "api-server" {
+      config {
+-       image = "api-server:1.3"
++       image = "api-server:1.4"
+```
+
+Next, plan these changes.
+
+```shell-session
+$ nomad job plan docs.nomad.hcl
++/- Job: "docs"
++/- Task Group: "api" (1 canary, 5 ignore)
+  +/- Task: "api-server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "api-server:1.3" => "api-server:1.4"
+        }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 docs.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+
+$ nomad job run docs.nomad.hcl
+# ...
+```
+
+Run the changes.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+## ...
+```
+
+Note from the plan output, Nomad is going to create one canary that will run the
+"api-server:1.4" image and ignore all the allocations running the older image.
+After running the job, The `nomad status` command output shows that the canary
+is running along side the older version of the job:
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 19:57:47 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         6        0       0         0
+
+Latest Deployment
+ID          = 32a080c1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         false     5        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+85662a7a  087852e2  api         1        run      running  07/26/17 19:57:47 UTC
+3ac3fe05  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+4bd51979  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+2998387b  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+35b813ee  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+b53b4289  087852e2  api         0        run      running  07/26/17 19:53:56 UTC
+```
+
+Now if you promote the canary, this will trigger a rolling update to replace the
+remaining allocations running the older image. The rolling update will happen at
+a rate of `max_parallel`, so in this case, one allocation at a time.
+
+```shell-session
+$ nomad deployment promote 37033151
+==> Monitoring evaluation "37033151"
+    Evaluation triggered by job "docs"
+    Evaluation within deployment: "ed28f6c2"
+    Allocation "f5057465" created: node "f6646949", group "cache"
+    Allocation "f5057465" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37033151" finished with status "complete"
+```
+
+Check the status.
+
+```shell-session
+$ nomad status docs
+ID            = docs
+Name          = docs
+Submit Date   = 07/26/17 20:28:59 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api         0       0         5        0       2         0
+
+Latest Deployment
+ID          = ed28f6c2
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Auto Revert  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+api         true         true      5        1         2       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+f5057465  f6646949  api         1        run      running   07/26/17 20:29:23 UTC
+b1c88d20  f6646949  api         1        run      running   07/26/17 20:28:59 UTC
+1140bacf  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+1958a34a  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+4bda385a  f6646949  api         0        run      running   07/26/17 20:28:37 UTC
+62d96f06  f6646949  api         0        stop     complete  07/26/17 20:28:37 UTC
+f58abbb2  f6646949  api         0        stop     complete  07/26/17 20:28:37 UTC
+```
+
+Alternatively, if the canary was not performing properly, you could abandon the
+change using the `nomad deployment fail` command, similar to the blue/green
+example.
+
+[rolling updates]: /nomad/docs/job-declare/strategy/rolling
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/strategy/index.mdx b/content/nomad/v1.11.x/content/docs/job-declare/strategy/index.mdx
new file mode 100644
index 0000000000..fc78f08b6c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/strategy/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Job deployment strategies
+description: |-
+  Discover common patterns to update running jobs in Nomad, including rolling updates, blue-green deployments, and canary deployments. Nomad  provides built-in support for each strategy.
+---
+
+# Job deployment strategies
+
+Most applications are long-lived and require updates over time. Whether you are
+deploying a new version of your web application or upgrading to a new version of
+Redis, Nomad has built-in support for rolling, blue/green, and canary updates.
+When a job specifies a rolling update, Nomad uses task state and health check
+information in order to detect allocation health and minimize or eliminate
+downtime. This section and subsections will explore how to do so safely with
+Nomad.
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/strategy/rolling.mdx b/content/nomad/v1.11.x/content/docs/job-declare/strategy/rolling.mdx
new file mode 100644
index 0000000000..667f9e5be7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/strategy/rolling.mdx
@@ -0,0 +1,323 @@
+---
+layout: docs
+page_title: Configure rolling updates
+description: |-
+  Enable rolling updates for a Nomad job, inspect the deployment, and set up
+  Nomad to automatically revert failed deployments to a previous working
+  version.
+---
+
+# Configure rolling updates
+
+Nomad supports rolling updates as a first class feature. To enable rolling
+updates a job or task group is annotated with a high-level description of the
+update strategy using the [`update` stanza]. Under the hood, Nomad handles
+limiting parallelism, interfacing with Consul to determine service health and
+even automatically reverting to an older, healthy job when a deployment fails.
+
+## Enable rolling updates for job
+
+Rolling updates are enabled by adding the [`update` stanza] to the job
+specification. The `update` stanza may be placed at the job level or in an
+individual task group. When placed at the job level, the update strategy is
+inherited by all task groups in the job. When placed at both the job and group
+level, the `update` stanzas are merged, with group stanzas taking precedence
+over job level stanzas. There is more information about
+[inheritance][update-stanza-inheritance] in the `update` stanza documentation.
+
+```hcl
+job "geo-api-server" {
+  # ...
+
+  group "api-server" {
+    count = 6
+
+    # Add an update stanza to enable rolling updates of the service
+    update {
+      max_parallel     = 2
+      min_healthy_time = "30s"
+      healthy_deadline = "10m"
+    }
+
+    task "server" {
+      driver = "docker"
+
+      config {
+        image = "geo-api-server:0.1"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+In this example, by adding the simple `update` stanza to the "api-server" task
+group, you inform Nomad that updates to the group should be handled with a
+rolling update strategy.
+
+Thus when a change is made to the job file that requires new allocations to be
+made, Nomad will deploy 2 allocations at a time and require that the allocations
+be running in a healthy state for 30 seconds before deploying more versions of the
+new group.
+
+By default Nomad determines allocation health by ensuring that all tasks in the
+group are running and that any [service check] the tasks register are passing.
+
+## Check the planned changes
+
+Suppose you make a change to a file to update the version of a Docker container
+that is configured with the same rolling update strategy from above.
+
+```diff
+@@ -2,6 +2,8 @@ job "geo-api-server" {
+   group "api-server" {
+     task "server" {
+       driver = "docker"
+
+       config {
+-        image = "geo-api-server:0.1"
++        image = "geo-api-server:0.2"
+```
+
+The [`nomad job plan` command] allows you to visualize the series of steps the
+scheduler would perform. You can analyze this output to confirm it is correct:
+
+```shell-session
+$ nomad job plan geo-api-server.nomad.hcl
++/- Job: "geo-api-server"
++/- Task Group: "api-server" (2 create/destroy update, 4 ignore)
+  +/- Task: "server" (forces create/destroy update)
+    +/- Config {
+      +/- image: "geo-api-server:0.1" => "geo-api-server:0.2"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 geo-api-server.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Here you can observe that Nomad will begin a rolling update by creating and
+destroying two allocations first; for the time being ignoring four of the old
+allocations, consistent with the configured `max_parallel` count.
+
+## Inspect a deployment
+
+After running the plan you can submit the updated job by running `nomad run`.
+Once run, Nomad will begin the rolling update of the service by placing two
+allocations at a time of the new job and taking two of the old jobs down.
+
+You can inspect the current state of a rolling deployment using `nomad status`:
+
+```shell-session
+$ nomad status geo-api-server
+ID            = geo-api-server
+Name          = geo-api-server
+Submit Date   = 07/26/17 18:08:56 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+api-server  0       0         6        0       4         0
+
+Latest Deployment
+ID          = c5b34665
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+api-server  6        4       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+14d288e8  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a134f73c  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a2574bb6  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+496e7aa2  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+9fc96fcc  f7b1ee08  api-server  0        run      running   07/26/17 18:04:30 UTC
+2521c47a  f7b1ee08  api-server  0        run      running   07/26/17 18:04:30 UTC
+6b794fcb  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+9bc11bd7  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+691eea24  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+af115865  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+```
+
+The output indicates that Nomad has created a deployment to conduct the rolling
+update from job version 0 to 1. It has placed four instances of the new job and
+has stopped four of the old instances. Consult the list of deployed allocations,
+and note that Nomad has placed four instances of job version 1 but only
+considers 2 of them healthy. This is because the two newest placed allocations
+haven't been healthy for the required 30 seconds yet.
+
+Wait for the deployment to complete, and then re-issue the command. You will
+receive output similar to the following:
+
+```shell-session
+$ nomad status geo-api-server
+ID            = geo-api-server
+Name          = geo-api-server
+Submit Date   = 07/26/17 18:08:56 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         6        0       6         0
+
+Latest Deployment
+ID          = c5b34665
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       6        6       6        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+d42a1656  f7b1ee08  api-server  1        run      running   07/26/17 18:10:10 UTC
+401daaf9  f7b1ee08  api-server  1        run      running   07/26/17 18:10:00 UTC
+14d288e8  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a134f73c  f7b1ee08  api-server  1        run      running   07/26/17 18:09:17 UTC
+a2574bb6  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+496e7aa2  f7b1ee08  api-server  1        run      running   07/26/17 18:08:56 UTC
+9fc96fcc  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+2521c47a  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+6b794fcb  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+9bc11bd7  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+691eea24  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+af115865  f7b1ee08  api-server  0        stop     complete  07/26/17 18:04:30 UTC
+```
+
+Nomad has successfully transitioned the group to running the updated canary and
+did so with no downtime to your service by ensuring only two allocations were
+changed at a time and the newly placed allocations ran successfully. Had any of
+the newly placed allocations failed their health check, Nomad would have aborted
+the deployment and stopped placing new allocations. If configured, Nomad can
+automatically revert back to the old job definition when the deployment fails.
+
+## Use auto-revert on failed deployments
+
+In the case you do a deployment in which the new allocations are unhealthy,
+Nomad will fail the deployment and stop placing new instances of the job. It
+optionally supports automatically reverting back to the last stable job version
+on deployment failure. Nomad keeps a history of submitted jobs and whether the
+job version was stable. A job is considered stable if all its allocations are
+healthy.
+
+To enable this, add the `auto_revert` parameter to the `update` stanza:
+
+```hcl
+update {
+  max_parallel     = 2
+  min_healthy_time = "30s"
+  healthy_deadline = "10m"
+
+  # Enable automatically reverting to the last stable job on a failed
+  # deployment.
+  auto_revert = true
+}
+```
+
+Now imagine you want to update your image to "geo-api-server:0.3" but you instead
+update it to the below and run the job:
+
+```diff
+@@ -2,6 +2,8 @@ job "geo-api-server" {
+   group "api-server" {
+     task "server" {
+       driver = "docker"
+
+       config {
+-        image = "geo-api-server:0.2"
++        image = "geo-api-server:0.33"
+```
+
+Running `nomad job deployments` will show that the deployment fails, and Nomad
+auto-reverted to the last stable job:
+
+```shell-session
+$ nomad job deployments geo-api-server
+ID        Job ID          Job Version  Status      Description
+0c6f87a5  geo-api-server  3            successful  Deployment completed successfully
+b1712b7f  geo-api-server  2            failed      Failed due to unhealthy allocations - rolling back to job version 1
+3eee83ce  geo-api-server  1            successful  Deployment completed successfully
+72813fcf  geo-api-server  0            successful  Deployment completed successfully
+```
+
+Nomad job versions increment monotonically. Even though Nomad reverted to the
+job specification at version 1, it creates a new job version. You can observe the
+differences between a job's versions and how Nomad auto-reverted the job using
+the `job history` command:
+
+```shell-session
+$ nomad job history -p geo-api-server
+Version     = 3
+Stable      = true
+Submit Date = 07/26/17 18:44:18 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.33" => "geo-api-server:0.2"
+        }
+
+Version     = 2
+Stable      = false
+Submit Date = 07/26/17 18:45:21 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.2" => "geo-api-server:0.33"
+        }
+
+Version     = 1
+Stable      = true
+Submit Date = 07/26/17 18:44:18 UTC
+Diff        =
++/- Job: "geo-api-server"
++/- Task Group: "api-server"
+  +/- Task: "server"
+    +/- Config {
+      +/- image: "geo-api-server:0.1" => "geo-api-server:0.2"
+        }
+
+Version     = 0
+Stable      = true
+Submit Date = 07/26/17 18:43:43 UTC
+```
+
+This output describes the process of a reverted deployment. Starting at the end
+of the output and working backwards, Nomad shows that version 0 was submitted.
+Next, version 1 was an image change from 0.1 to 0.2 of geo-api-server and was
+flagged as stable. Version 2 of the job attempted to update geo-api-server from
+0.2 to 0.33; however, the deployment failed and never became stable. Finally,
+version 3 of the job is created when Nomad automatically reverts the failed
+deployment and redeploys the last healthy version--geo-api-server version 0.2.
+
+[`nomad job plan` command]: /nomad/commands/job/plan
+[`update` stanza]: /nomad/docs/job-specification/update
+[service check]: /nomad/docs/job-specification/check
+[update-stanza-inheritance]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-dependencies.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-dependencies.mdx
new file mode 100644
index 0000000000..9a7cfe0688
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-dependencies.mdx
@@ -0,0 +1,385 @@
+---
+layout: docs
+page_title: Configure task dependencies
+description: |-
+  Create, configure, and run two jobs to use init and sidecar tasks. Create a dependency between the jobs and discover how to model complex workload dependency trees.
+---
+
+# Configure task dependencies
+
+
+Nomad task dependencies provide the ability to define prestart tasks.
+
+Prestart tasks have two patterns: init tasks and sidecar tasks. Init
+tasks are tasks that must run to completion before the main workload is started.
+They are commonly used to download assets or to create necessary tables for an
+extract-transform-load (ETL) job. Sidecar tasks are started before main workload
+starts and run for the lifetime of the main workload. Typical sidecars tasks are
+log forwarders, proxies, and for platform abstractions. This tutorial demonstrates
+an init task.
+
+You can create an init task by adding a [`lifecycle` stanza] with `hook` set to
+`prestart` and `sidecar` to `false` as below.
+
+```hcl
+      lifecycle {
+        hook    = "prestart"
+        sidecar = false
+      }
+```
+
+You can model complex job dependency trees by using one or more init tasks to
+delay the job's main tasks from running until a condition is met. In this case,
+until a service is available and advertised in Consul.
+
+In this tutorial you will work with several Nomad objects:
+
+- **mock-app** - a job file that contains two tasks
+
+  - **await-mock-service** - an init task that will wait infinitely for a
+    service named "mock-service" to be advertised over the Consul DNS API. Once
+    found, it will exit successfully.
+
+  - **mock-app-container** - the main workload task that is dependent on the
+    "mock-service" service.
+
+- **mock-service** - a job that contains one task which advertises a service
+  named "mock-service". This is provided as a Nomad job as a convenience, but
+  could be replaced by any means of registering a service named "mock-service"
+  in Consul, like the CLI or API.
+
+In this guide, you will complete the following actions:
+
+- Deploy the "mock-app" job.
+
+- Verify that the "mock-app-container" task remains in pending and unstarted.
+
+- Start the "mock-service" job.
+
+- Verify that the "await-mock-service" container completes successfully and that
+  the "mock-app-container" task starts.
+
+## Prerequisites
+
+To complete this tutorial you will need:
+
+- a Nomad cluster and at least one Consul server.
+- Nomad v0.11.0 or greater
+
+If you do not have an existing Nomad cluster, you can learn how to deploy
+on using the [Install Nomad] guide. Similarly, if you do not have an
+existing Consul datacenter, you can learn how to deploy Consul with the
+[Install Consul] guide.
+
+## Create the mock-app job file
+
+This example uses a looping script, in the `config` stanza, to mock service
+payloads.
+
+Create an HCL file named `mock-app.nomad.hcl` with the following content.
+
+```hcl
+job "mock-app" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mock-app" {
+    # disable deployments
+    update {
+      max_parallel = 0
+    }
+
+    task "await-mock-service" {
+      driver = "docker"
+
+      config {
+        image        = "busybox:1.28"
+        command      = "sh"
+        args         = ["-c", "echo -n 'Waiting for service'; until nslookup mock-service.service.consul 2>&1 >/dev/null; do echo '.'; sleep 2; done"]
+        network_mode = "host"
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+
+      lifecycle {
+        hook    = "prestart"
+        sidecar = false
+      }
+    }
+
+    task "mock-app-container" {
+      driver = "docker"
+
+      config {
+        image   = "busybox"
+        command = "sh"
+        args    = ["-c", "echo The app is running! && sleep 3600"]
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+The job contains two tasks—"await-mock-service" and "mock-app". The
+"await-mock-service" task is configured to busy-wait until the "mock-service"
+service is advertised in Consul. For this guide, this will not happen until you
+run the `mock-service.nomad.hcl` job. In a more real-world case, this could be any
+service dependency that advertises itself in Consul.
+
+You can use this pattern to model more complicated chains of service dependency
+by including more await-style workloads.
+
+### Ensure that name resolution works properly
+
+Since the "await-mock-service" task uses nslookup inside of a Docker container,
+you will need to ensure that your container can perform lookups against your
+Consul DNS API endpoint. This tutorial uses `network_mode = host` to allow the
+container to use the Nomad client nodes DNS resolution pathway.
+
+The nslookup application will only perform queries on the standard DNS port
+(53). You might need to use an application to forward requests from port 53 to
+the Consul DNS API port—port 8600 by default. You can learn several ways to
+accomplish this forwarding in the [Forward DNS] Learn guide.
+
+You could also add a `dns_servers` value to the config stanza of the
+"await-mock-service" task in the mock-app.nomad.hcl file to direct the query to a
+DNS server directly that meets the above criteria.
+
+## Run the mock-app job
+
+Run `nomad run mock-app.nomad.hcl`.
+
+```shell-session
+$ nomad run mock-app.nomad.hcl
+```
+
+The job will launch and provide you an allocation ID in the output.
+
+```shell-session
+$ nomad run mock-app.nomad.hcl
+==> Monitoring evaluation "01c73d5a"
+    Evaluation triggered by job "mock-app"
+    Allocation "3044dda0" created: node "f26809e6", group "mock-app"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "01c73d5a" finished with status "complete"
+```
+
+## Verify mock-app-container is pending
+
+Run the `nomad alloc status` command with the provided allocation ID.
+
+```shell-session
+$ nomad alloc status 3044dda0
+```
+
+The `nomad alloc status` command provides you with useful information about the resource. For this guide, focus on the status
+of each task. Each task's status is output in lines that look like `Task "await-mock-service" is "running"`.
+
+```shell-session
+$ nomad alloc status 3044dda0
+ID                  = 3044dda0-8dc1-1bac-86ea-66a3557c67d3
+Eval ID             = 01c73d5a
+Name                = mock-app.mock-app[0]
+Node ID             = f26809e6
+Node Name           = nomad-client-2.node.consul
+Job ID              = mock-app
+Job Version         = 0
+Client Status       = running
+Client Description  = Tasks are running
+Desired Status      = run
+Desired Description = <none>
+Created             = 43s ago
+Modified            = 42s ago
+
+Task "await-mock-service" (prestart) is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+3/200 MHz  80 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:07:26Z
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:07:26-04:00  Started     Task started by client
+2020-03-18T13:07:26-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+
+Task "mock-app-container" is "pending"
+Task Resources
+CPU      Memory   Disk     Addresses
+200 MHz  128 MiB  300 MiB
+
+Task Events:
+Started At     = N/A
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type      Description
+2020-03-18T13:07:26-04:00  Received  Task received by client
+```
+
+Notice that the await-mock-service task is running and that the
+"mock-app-container" task is pending. The "mock-app-container" task will remain
+in pending until the "await-mock-service" task completes successfully.
+
+## Create the mock-service job file
+
+Create a file named `mock-service.nomad.hcl` with the following content.
+
+```hcl
+job "mock-service" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mock-service" {
+    task "mock-service" {
+      driver = "docker"
+
+      config {
+        image   = "busybox"
+        command = "sh"
+        args    = ["-c", "echo The service is running! && while true; do sleep 2; done"]
+      }
+
+      resources {
+        cpu    = 200
+        memory = 128
+      }
+
+      service {
+        name = "mock-service"
+      }
+    }
+  }
+}
+
+```
+
+This job advertises the "mock-service" service in Consul. When run, this
+will allow the await-mock-service task to complete successfully and let
+the "mock-app-container" task start up.
+
+## Start mock-service job
+
+Run `nomad run mock-service.nomad.hcl`.
+
+```shell-session
+$ nomad run mock-service.nomad.hcl
+```
+
+Nomad will start the job and return information about the scheduling information.
+
+```shell-session
+$ nomad run mock-service.nomad
+==> Monitoring evaluation "f31f8eb1"
+    Evaluation triggered by job "mock-service"
+    Allocation "d7767adf" created: node "f26809e6", group "mock-service"
+    Evaluation within deployment: "3d86e09a"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "f31f8eb1" finished with status "complete"
+```
+
+## Verify mock-app-container is running
+
+Finally, check the output of the `nomad alloc status` command again to check the
+task statuses. Use the allocation ID from when you ran the "mock-app" job.
+
+```shell-session
+$ nomad alloc status 3044dda0
+```
+
+Again, focus on the task status lines for "await-mock-service" and
+"mock-app-container".
+
+```plaintext
+ID                  = 3044dda0-8dc1-1bac-86ea-66a3557c67d3
+Eval ID             = 01c73d5a
+Name                = mock-app.mock-app[0]
+Node ID             = f26809e6
+Node Name           = nomad-client-2.node.consul
+Job ID              = mock-app
+Job Version         = 0
+Client Status       = running
+Client Description  = Tasks are running
+Desired Status      = run
+Desired Description = <none>
+Created             = 21m38s ago
+Modified            = 7m27s ago
+
+Task "await-mock-service" (prestart) is "dead"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/200 MHz  80 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:07:26Z
+Finished At    = 2020-03-18T17:21:35Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:21:35-04:00  Terminated  Exit Code: 0
+2020-03-18T13:07:26-04:00  Started     Task started by client
+2020-03-18T13:07:26-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+
+Task "mock-app-container" is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/200 MHz  32 KiB/128 MiB  300 MiB
+
+Task Events:
+Started At     = 2020-03-18T17:21:37Z
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                       Type        Description
+2020-03-18T13:21:37-04:00  Started     Task started by client
+2020-03-18T13:21:35-04:00  Driver      Downloading image
+2020-03-18T13:21:35-04:00  Task Setup  Building Task Directory
+2020-03-18T13:07:26-04:00  Received    Task received by client
+```
+
+Notice, the "await-mock-service" task is dead and based on the "Recent Events"
+table terminated with "Exit Code: 0". This indicates that it completed
+successfully. The "mock-app-container" task has now transitioned to the
+"running" status and the container is running.
+
+## Next steps
+
+Now that you have completed this guide, you have experimented with using Nomad
+task dependencies to model inter-job dependencies.
+
+### Further reading
+
+- [`lifecycle` stanza]
+- [`service` stanza]
+- Consul [Service Definition]
+- Consul [DNS Interface]
+
+[forward dns]: /consul/tutorials/networking/dns-forwarding
+[install consul]: /consul/tutorials/production-deploy/deployment-guide
+[install nomad]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
+[`lifecycle` stanza]: /nomad/docs/job-specification/lifecycle
+[`service` stanza]: /nomad/docs/job-specification/service
+[service definition]: /consul/docs/services/usage/define-services
+[dns interface]: /consul/docs/services/discovery/dns-overview
+[dns interface]: /consul/docs/services/discovery/dns-overview
+
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/docker.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/docker.mdx
new file mode 100644
index 0000000000..31c2e062e1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/docker.mdx
@@ -0,0 +1,832 @@
+---
+layout: docs
+page_title: Use the Docker task driver in a job
+description: Nomad's Docker task driver lets you run Docker-based tasks in your jobs. Learn how to configure job tasks, authenticate against a private repository, use insecure registries, and configure Docker networking.
+---
+
+# Use the Docker task driver in a job
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+**Note:** If you are using Docker Desktop for Windows or MacOS, check
+[the FAQ][faq-win-mac].
+
+Refer to [Configure the Docker task
+driver](/nomad/docs/deploy/task-driver/docker) for capabilities, client
+requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels = {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](/nomad/docs/deploy/task-driver/docker#helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cgroupns` - (Optional) Cgroup namespace to use. Set to `host` or
+  `private`. If not specified, the driver uses Docker's default. Refer to Docker's [dockerd reference](https://docs.docker.com/reference/cli/dockerd/) for more information.
+
+- `container_exists_attempts` - (Optional) A number of attempts to be made to
+  purge a container if during task creation Nomad encounters an existing one in
+  non-running state for the same task. Defaults to `5`.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) Specifies [Windows isolation][] mode: `"hyperv"` or
+  `"process"`. Defaults to `"hyperv"`.
+
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+   <Warning>
+
+   If you are creating your job specification in JSON, you must use wrap the map in an
+   array. Do not use a bare map as you would in HCL.
+
+   ```json
+   config {
+     "sysctl": [
+      {
+       "net.core.somaxconn": "16384",
+       "net.ipv4.tw_reuse": "1"
+      }
+    ]
+   }
+   ```
+
+   </Warning>
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels = {
+      foo = "bar"
+      "quote.dotted.keys" = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](/nomad/docs/deploy/task-driver/docker#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels = {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. Note that `"all"` is not permitted here if the `allow_caps`
+  field in the driver configuration doesn't also allow all capabilities. For
+  example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](/nomad/docs/deploy/task-driver/docker#config)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](/nomad/docs/deploy/task-driver/docker#helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/deploy/task-driver/docker#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/deploy/task-driver/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/deploy/task-driver/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/exec.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/exec.mdx
new file mode 100644
index 0000000000..94760d6561
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/exec.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Use the Isolated Fork/Exec task driver in a job
+description: Nomad's Isolated Fork/Exec task driver lets you run binaries using OS isolation primitives. Learn how to use the Isolated Fork/Exec task driver in your jobs. Configure the command to execute with command arguments, namespace isolation, and Linux capabilities.
+---
+
+# Use the Isolated Fork/Exec task driver in a job
+
+Name: `exec`
+
+The `exec` driver is used to execute a particular command for a task. However,
+unlike [`raw_exec`](/nomad/docs/job-declare/task-driver/raw_exec) it uses the
+underlying isolation primitives of the operating system to limit the task's
+access to resources. While simple, since the `exec` driver can invoke any
+command, it can be used to call scripts or other wrappers which provide higher
+level features.
+
+Refer to [Configure the Isolated Fork/Exec task
+driver](/nomad/docs/deploy/task-driver/exec) for capabilities, client
+requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](/nomad/docs/deploy/task-driver/exec#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](/nomad/docs/deploy/task-driver/exec#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+
+[default_pid_mode]: /nomad/docs/deploy/task-driver/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/deploy/task-driver/exec#default_ipc_mode
+[cap_add]: /nomad/docs/deploy/task-driver/exec#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/deploy/task-driver/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/reference/runtime-environment-settings#job-related-variables
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/index.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/index.mdx
new file mode 100644
index 0000000000..9bceb69a9c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/index.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: Use Nomad task drivers in jobs
+description: Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, installation, usage, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+---
+
+# Use Nomad task drivers in jobs
+
+Nomad's bundled task drivers integrate with the host OS to run job tasks in
+isolation. Review job usage for the Docker, Isolated
+Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+
+@include 'task-driver-intro.mdx'
+
+## Nomad task drivers
+
+The Nomad binary contains several bundled task drivers. We also support
+additional task driver plugins that you may install separately.
+
+| Bundled with Nomad   | Plugins               |
+|----------------------|-----------------------|
+| [Docker]             | [Exec2]               |
+| [Isolated Fork/Exec] | [Podman]              |
+| [Java]               | [Virt]                |
+| [QEMU]               |                       |
+| [Raw Fork/Exec]      |                       |
+
+Refer to each task driver's page for detailed usage.
+
+## Configure task driver plugins
+
+Refer to [Configure Nomad task drivers](/nomad/docs/deploy/task-driver) for task
+driver plugin configuration details.
+
+[Docker]: /nomad/docs/job-declare/task-driver/docker
+[Exec2]: /nomad/plugins/drivers/exec2
+[Isolated Fork/Exec]: /nomad/docs/job-declare/task-driver/exec
+[Podman]: /nomad/plugins/drivers/podman
+[Java]: /nomad/docs/job-declare/task-driver/java
+[Virt]: /nomad/plugins/drivers/virt
+[QEMU]: /nomad/docs/job-declare/task-driver/qemu
+[Raw Fork/Exec]: /nomad/docs/job-declare/task-driver/raw_exec
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/java.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/java.mdx
new file mode 100644
index 0000000000..79b2fd2f61
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/java.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: Use the Java task driver in a job
+description: Nomad's Java task driver lets you run JAR files in your workloads. Learn how to configure a job task that uses the Java task driver. Configure paths, JAR args, JVM options, namespace isolation, work directory, and Linux capabilities.
+---
+
+# Use the Java task driver in a job
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+Refer to [Configure the Java task driver](/nomad/docs/deploy/task-driver/java)
+for capabilities, client requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](/nomad/docs/deploy/task-driver/java#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+[default_pid_mode]: /nomad/docs/deploy/task-driver/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/deploy/task-driver/java#default_ipc_mode
+[cap_add]: /nomad/docs/deploy/task-driver/java#cap_add
+[cap_drop]: /nomad/docs/deploy/task-driver/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/deploy/task-driver/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/deploy/production/requirements#hardening-nomad
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[host volume]: /nomad/docs/configuration/client#host_volume-block
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/qemu.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/qemu.mdx
new file mode 100644
index 0000000000..2eee6c2019
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/qemu.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: Use the QEMU task driver in a job
+description: Nomad's QEMU task driver provides a generic virtual machine runner that can execute any regular QEMU image. Learn how to use the QEMU task driver in your jobs. Configure image path, driver interface, accelerator, graceful shutdown, guest agent, and port map.
+---
+
+# Use the QEMU task driver in a job
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+Refer to [Configure the QEMU task driver](/nomad/docs/deploy/task-driver/qemu)
+for capabilities, client requirements, and plugin configuration.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+[`args`]: /nomad/docs/job-declare/task-driver/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/task-driver/raw_exec.mdx b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/raw_exec.mdx
new file mode 100644
index 0000000000..105dc41ba2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/task-driver/raw_exec.mdx
@@ -0,0 +1,109 @@
+---
+layout: docs
+page_title: Use the Raw Fork/Exec task driver in a job
+description: Nomad's Raw Exec task driver lets you execute commands with no resource isolation. Learn how to use the Raw Fork/Exec task driver in your jobs.
+---
+
+# Use the Raw Fork/Exec task driver in a job
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+Refer to [Configure the Raw Fork/Exec task
+driver](/nomad/docs/deploy/task-driver/raw_exec) for capabilities, client
+requirements, and plugin configuration.
+
+## Task configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/reference/runtime-variable-interpolation) will be interpreted before
+  launching the task.
+
+- `cgroup_v1_override` - (Optional) A map of controller names to paths. The
+  task will be added to these cgroups. The task will fail if these cgroups do
+  not exist. **WARNING:** May conflict with other Nomad driver's cgroups and
+  have unintended side effects.
+
+- `cgroup_v2_override` - (Optional) Adds the task to a unified cgroup path.
+  Paths may be relative to the cgroupfs root or absolute.  **WARNING:** May
+  conflict with other Nomad driver's cgroups and have unintended side
+  effects.
+
+~> On Linux, you cannot set the `task.user` field on a task using the `raw_exec`
+driver if you have hardened the Nomad client according to the
+[production][hardening] guide. On Windows, when Nomad is running as a [system
+service][service], you may specify a less-privileged service user. For example,
+`NT AUTHORITY\LocalService`, `NT AUTHORITY\NetworkService`.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This
+  must be an absolute path. This will also change the working directory when
+  using `nomad alloc exec`.
+
+- `denied_envvars` - (Optional) Passes a list of environment variables that
+  the driver should scrub from the task environment. Supports globbing, with "*"
+  wildcard accepted as prefix and/or suffix.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+[hardening]: /nomad/docs/deploy/production/requirements#user-permissions
+[service]: /nomad/docs/deploy/production/windows-service
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.11.x/content/docs/job-declare/vault.mdx b/content/nomad/v1.11.x/content/docs/job-declare/vault.mdx
new file mode 100644
index 0000000000..87ba7fe281
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-declare/vault.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: Use Vault in a job
+description: |-
+  Use Vault in your Nomad job.
+---
+
+# Use Vault in a job
+
+## Use a Vault namespace
+
+This example job specifies to use the `engineering` namespace in
+Vault. The job authenticates to Vault using its workload identity with the
+`nomad-workloads` Vault role, reads the value at secret/foo, and fetches the
+value for key `bar`.
+
+```hcl
+job "vault" {
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        role      = "nomad-workloads"
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+```
+
+## Resources
+
+- [Job specification `vault` block](/nomad/docs/job-specification/vault)
+- [Vault integration documentation](/nomad/docs/secure/vault)
diff --git a/content/nomad/v1.11.x/content/docs/job-networking/cni.mdx b/content/nomad/v1.11.x/content/docs/job-networking/cni.mdx
new file mode 100644
index 0000000000..021db26938
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-networking/cni.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Use a CNI network with a job
+description: |-
+  Learn how to use CNI networks with Nomad jobs.
+---
+
+# Use a CNI network with a job
+
+## Prerequisites
+
+Make sure your Nomad instance has a configured CNI network. Refer to [CNI
+plugins and bridge networking](/nomad/docs/networking/cni) for instructions.
+
+## Job task configuration
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`.
+
+For example, to use the configuration named `mynet`, you should set the task
+group's network mode to `cni/mynet`.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      mode = "cni/mynet"
+    }
+  }
+}
+```
+
+Nodes that have a network configuration defining a network named `mynet` in
+their `cni_config_dir` are eligible to run the workload. Nomad then schedules
+the workload on client nodes that have fingerprinted a CNI configuration with
+the given name.
+
+Nomad additionally supplies the following arguments via `CNI_ARGS` to the CNI
+network: `NOMAD_REGION`, `NOMAD_NAMESPACE`, `NOMAD_JOB_ID`, `NOMAD_GROUP_NAME`,
+and `NOMAD_ALLOC_ID`.
+
+Since the `CNI_ARGS` do not allow values to contain a semicolon, Nomad will not
+set keys where the value contains a semicolon (this could happen with the job
+ID). CNI plugins utilizing `NOMAD_*` CNI arguments are advised to apply a
+defensive policy or simply error out.
diff --git a/content/nomad/v1.11.x/content/docs/job-networking/index.mdx b/content/nomad/v1.11.x/content/docs/job-networking/index.mdx
new file mode 100644
index 0000000000..ce2cb120b0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-networking/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Workload networking
+description: |-
+  This section provides guidance on networking your Nomad workloads. Topics include using a CNI network and Consul service discovery.
+---
+
+# Workload networking
+
+This section provides guidance on networking your Nomad workloads. Topics
+include using a CNI network and Consul service discovery. Refer to the [Nomad
+networking page](/nomad/docs/networking) to learn more about Nomad's networking capabilities.
diff --git a/content/nomad/v1.11.x/content/docs/job-networking/service-discovery.mdx b/content/nomad/v1.11.x/content/docs/job-networking/service-discovery.mdx
new file mode 100644
index 0000000000..37db5c55db
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-networking/service-discovery.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Nomad service discovery helps you automatically connect workloads. Compare Nomad's built-in service discovery feature to Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+---
+
+# Service discovery
+
+@include 'service-discovery.mdx'
diff --git a/content/nomad/v1.11.x/content/docs/job-run/index.mdx b/content/nomad/v1.11.x/content/docs/job-run/index.mdx
new file mode 100644
index 0000000000..5a8a31a1a8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-run/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Run Nomad jobs
+description: |-
+  This section provides guidance for running Nomad jobs. Inspect job, access logs for troubleshooting, collect resource utilization metrics, and create job versions.
+---
+
+# Run Nomad jobs
+
+This section provides guidance for running Nomad jobs. Inspect job, access logs
+for troubleshooting, collect resource utilization metrics, and create job
+versions.
+
+The following list is the general flow for operating a job in Nomad:
+
+1. Declare the job according to the [job specification](/nomad/docs/job-specification).
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Refer to [Create and submit a job](/nomad/docs/job-declare/create-job) to learn
+how to create a job specification, review the job plan, and submit the job.
+
+## Run a job
+
+Execute the [`nomad job run` command](/nomad/commands/job/run) to run your job.
+
+Now that the job is scheduled, it may or may not be running. You need to inspect
+the allocation status and logs to make sure the job started correctly. Refer to
+the section on [inspecting state](/nomad/docs/job-run/inspect)
+details ways to examine this job's state.
+
+## Update a running job
+
+When updating a job, there are a number of [built-in update
+strategies](/nomad/docs/job-declare/strategy) which may be defined in the job
+file. The general flow for updating an existing job in Nomad is:
+
+1. Modify the existing job file with the desired changes.
+1. Plan and review the changes with a Nomad server.
+1. Submit the job file to a Nomad server.
+1. (Optional) Review job status and logs.
+
+Because the job specification defines the deployment strategy, the workflow
+remains the same regardless of whether this is an initial deployment or a
+long-running job.
+
+## Run a job in the web UI
+
+1. From the **Jobs** page in the web UI, click on the **Run Job** button in the
+top right of the page. 
+1. Enter the job definition in HCL into the **Job Definition** field, upload
+a jobspec file with the **Upload file** button, or choose from a set of
+templated jobspecs with the **Choose from template** button.
+1. Click on the **Plan** button at the bottom of the page. Nomad plans the job
+and displays the scheduler dry-run results.
+1. Click on the **Run** button at the bottom of the page.
+
+## View a running job in the web UI
+
+Nomad serves the web UI alongside the API. You can open the web UI in a web
+browser with the [`nomad ui` command](/nomad/commands/ui) or you can use the
+cluster address and navigate to the `/ui` path.
+
+```shell-session
+$ nomad ui
+Opening URL "https://127.0.0.1:4646"
+```
+
+When accessing the web UI, the first page you see is a listing of all the jobs
+for the default namespace. Clicking on a job takes you to the Job details page.
+
+### View a job from the CLI
+
+You can open the details page for a job by providing the job name to the
+`nomad ui` command.
+
+```shell-session
+$ nomad ui example-job-name
+Opening URL "https://127.0.0.1:4646/ui/jobs/example-job-name"
+```
+
+### View an allocation from the CLI
+
+You can open the details page for an allocation by providing the allocation ID
+to the `nomad ui` command.
+
+```shell-session
+$ nomad ui 7dc9f2d6
+Opening URL "https://127.0.0.1:4646/ui/allocations/7dc9f2d6-15fc-7c39-4692-70fe653d960e"
+```
\ No newline at end of file
diff --git a/content/nomad/v1.11.x/content/docs/job-run/inspect.mdx b/content/nomad/v1.11.x/content/docs/job-run/inspect.mdx
new file mode 100644
index 0000000000..89ff43247b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-run/inspect.mdx
@@ -0,0 +1,233 @@
+---
+layout: docs
+page_title: Inspect running jobs
+description: |-
+  Inspect the status of a running job, the associated evaluation, and allocations to troubleshoot for errors with the Nomad CLI.
+---
+
+# Inspect running jobs
+
+A successful job submission is not an indication of a successfully-running job.
+This is the nature of a highly-optimistic scheduler. A successful job submission
+means the server was able to issue the proper scheduling commands. It does not
+indicate the job is actually running. To verify the job is running and healthy,
+you might need to inspect its state.
+
+This section will utilize the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+## Query the job status
+
+After a job is submitted, you can query the status of that job using the job
+status command:
+
+```shell-session
+$ nomad job status
+ID    Type     Priority  Status
+docs  service  50        running
+```
+
+At a high level, you can observe that the job is currently running, but what
+does "running" actually mean. By supplying the name of a job to the job status
+command, you can ask Nomad for more detailed job information:
+
+```shell-session
+$ nomad job status docs
+ID          = docs
+Name        = docs
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+example     0       0         3        0       0         0
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status    Created At
+04d9627d  42d788a3  a1f934c9  example     run      running   <timestamp>
+e7b8d4f5  42d788a3  012ea79b  example     run      running   <timestamp>
+5cbf23a1  42d788a3  1e1aa1e0  example     run      running   <timestamp>
+```
+
+This output shows that there are three instances of this task running, each with
+its own allocation. For more information on the `status` command, please consult
+the [`nomad job status` command] documentation.
+
+## Fetch an evaluation's status
+
+You can think of an evaluation as a submission to the scheduler. An example
+below shows status output for a job where some allocations were placed
+successfully, but did not have enough resources to place all of the desired
+allocations.
+
+If you issue the status command with the `-evals` flag, the output will show
+that there is an outstanding evaluation for this hypothetical job:
+
+```shell-session
+$ nomad job status -evals docs
+ID          = docs
+Name        = docs
+Type        = service
+Priority    = 50
+Datacenters = dc1
+Status      = running
+Periodic    = false
+
+Evaluations
+ID        Priority  Triggered By  Status    Placement Failures
+5744eb15  50        job-register  blocked   N/A - In Progress
+8e38e6cf  50        job-register  complete  true
+
+Placement Failure
+Task Group "example":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Allocations
+ID        Eval ID   Node ID   Task Group  Desired  Status   Created At
+12681940  8e38e6cf  4beef22f  example       run      running  <timestamp>
+395c5882  8e38e6cf  4beef22f  example       run      running  <timestamp>
+4d7c6f84  8e38e6cf  4beef22f  example       run      running  <timestamp>
+843b07b8  8e38e6cf  4beef22f  example       run      running  <timestamp>
+a8bc6d3e  8e38e6cf  4beef22f  example       run      running  <timestamp>
+b0beb907  8e38e6cf  4beef22f  example       run      running  <timestamp>
+da21c1fd  8e38e6cf  4beef22f  example       run      running  <timestamp>
+```
+
+The output states that the job has a "blocked" evaluation that is in progress.
+When Nomad can not place all the desired allocations, it creates a blocked
+evaluation that waits for more resources to become available.
+
+The `eval status` command enables examination of any evaluation in more detail.
+For the most part this should never be necessary. However, it can be useful to
+understand what triggered a specific evaluation and it's current status. Running
+it on the "complete" evaluation provides output similar to the following:
+
+```shell-session
+$ nomad eval status 8e38e6cf
+ID                 = 8e38e6cf
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = docs
+Priority           = 50
+Placement Failures = true
+
+Failed Placements
+Task Group "example" (failed to place 3 allocations):
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Evaluation "5744eb15" waiting for additional capacity to place remainder
+```
+
+This output indicates that the evaluation was created by a "job-register" event
+and that it had placement failures. The evaluation also has the information on
+why placements failed. Also output is the evaluation of any follow-up
+evaluations created.
+
+If you would like to learn more about this output, consult the documentation for
+[`nomad eval status` command].
+
+## Retrieve an allocation's status
+
+You can think of an allocation as an instruction to schedule. Like an
+application or service, an allocation has logs and state. The `alloc status`
+command gives the most recent events that occurred for a task, its resource
+usage, port allocations and more:
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+Eval ID       = 42d788a3
+Name          = docs.example[2]
+Node ID       = a1f934c9
+Job ID        = docs
+Client Status = running
+
+Task "server" is "running"
+Task Resources
+CPU        Memory          Disk     Addresses
+0/100 MHz  728 KiB/10 MiB  300 MiB  http: 10.1.1.196:5678
+
+Recent Events:
+Time                   Type      Description
+10/09/16 00:36:06 UTC  Started   Task started by client
+10/09/16 00:36:05 UTC  Received  Task received by client
+```
+
+The [`nomad alloc status` command] is a good starting to point for debugging an
+application that did not start. Hypothetically assume a user meant to start a
+Docker container named "redis:2.8", but accidentally put a comma instead of a
+period, typing "redis:2,8".
+
+When the job is executed, it produces a failed allocation. The
+`nomad alloc status` command gives the reason why.
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+...
+
+Recent Events:
+Time                   Type            Description
+06/28/16 15:50:22 UTC  Not Restarting  Error was unrecoverable
+06/28/16 15:50:22 UTC  Driver Failure  failed to create image: Failed to pull `redis:2,8`: API error (500): invalid tag format
+06/28/16 15:50:22 UTC  Received        Task received by client
+```
+
+Unfortunately not all failures are as visible in the allocation status output.
+If the `alloc status` command shows many restarts, there is likely an
+application-level issue during start up. For example:
+
+```shell-session
+$ nomad alloc status 04d9627d
+ID            = 04d9627d
+...
+
+Recent Events:
+Time                   Type        Description
+06/28/16 15:56:16 UTC  Restarting  Task restarting in 5.178426031s
+06/28/16 15:56:16 UTC  Terminated  Exit Code: 1, Exit Message: "Docker container exited with non-zero exit code: 1"
+06/28/16 15:56:16 UTC  Started     Task started by client
+06/28/16 15:56:00 UTC  Restarting  Task restarting in 5.00123931s
+06/28/16 15:56:00 UTC  Terminated  Exit Code: 1, Exit Message: "Docker container exited with non-zero exit code: 1"
+06/28/16 15:55:59 UTC  Started     Task started by client
+06/28/16 15:55:48 UTC  Received    Task received by client
+```
+
+To debug these failures, you can use the `nomad alloc logs` command, which is
+discussed in the [accessing logs] section of this documentation.
+
+For more information on the `alloc status` command, please consult the
+documentation for the [`nomad alloc status` command].
+
+## Monitoring a job in the web UI
+
+To view the overview page for a job in the web UI, you can click on the job
+name from the list on the **Jobs** page. The overview page has several linked
+sub-pages at the top for viewing more details about the running job.
+
+- **Overview**: A page with general information about the job including the job
+name, type, priority, namespace, the status of all current and previous
+allocations, any placement failures, and the associated task groups.
+- **Definition**: A page that displays the job definition in JSON.
+- **Versions**: A page with a timeline view of every version of the job. You
+can compare the differences between job versions on this page.
+- **Deployments**: A page with health information about job deployments,
+associated task groups, and allocations.
+- **Allocations**: A page with a list of associated allocations.
+- **Evaluations**: A page with a list of associated evaluations.
+- **Services**: A page with a list of services registered for service discover
+and any associated allocations.
+- **Variables**: A page with associated Nomad Variables used by the job.
+
+[accessing logs]: /nomad/docs/job-run/logs
+[`nomad alloc status` command]: /nomad/commands/alloc/status
+[`nomad eval status` command]: /nomad/commands/eval/status
+[`nomad job status` command]: /nomad/commands/job/status
+
diff --git a/content/nomad/v1.11.x/content/docs/job-run/logs.mdx b/content/nomad/v1.11.x/content/docs/job-run/logs.mdx
new file mode 100644
index 0000000000..e0c845e063
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-run/logs.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: Access job logs for troubleshooting
+description: |-
+  Access logs of applications running in Nomad with the Nomad CLI or API.
+---
+
+# Access job logs for troubleshooting
+
+Viewing application logs is critical for debugging issues, examining performance
+problems, or even verifying the application started correctly. To make this
+as simple as possible, Nomad provides:
+
+- Job specification for [log rotation](/nomad/docs/job-specification/logs)
+- CLI command for [log viewing](/nomad/commands/alloc/logs)
+- API for programmatic [log access](/nomad/api-docs/client#stream-logs)
+
+This section will use the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+As a reminder, here is the output of the run command from the previous example:
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "04d9627d" created: node "a1f934c9", group "example"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+The provided allocation ID (which is also available via the `nomad status`
+command) is required to access the application's logs. To access the logs of our
+application, issue the following command:
+
+```shell-session
+$ nomad alloc logs 04d9627d
+```
+
+The output will look something like this:
+
+```plaintext
+<timestamp> 10.1.1.196:5678 10.1.1.196:33407 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 21.809µs
+<timestamp> 10.1.1.196:5678 10.1.1.196:33408 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 20.241µs
+<timestamp> 10.1.1.196:5678 10.1.1.196:33409 "GET / HTTP/1.1" 200 12 "curl/7.35.0" 13.629µs
+```
+
+By default, this will return the logs of the task. If more than one task is
+defined in the job file, the name of the task is a required argument:
+
+```shell-session
+$ nomad alloc logs 04d9627d server
+```
+
+The logs command supports both displaying the logs as well as following logs,
+blocking for more output, similar to `tail -f`. To follow the logs, use the
+appropriately named `-f` flag:
+
+```shell-session
+$ nomad alloc logs -f 04d9627d
+```
+
+This will stream logs to your console.
+
+If you are only interested in the "tail" of the log, use the `-tail` and `-n`
+flags:
+
+```shell-session
+$ nomad alloc logs -tail -n 25 04d9627d
+```
+
+This will show the last 25 lines. If you omit the `-n` flag, `-tail` will
+default to 10 lines.
+
+By default, only the logs on stdout are displayed. To show the log output from
+stderr, use the `-stderr` flag:
+
+```shell-session
+$ nomad alloc logs -stderr 04d9627d
+```
+
+## Consider the "log shipper" pattern
+
+While the logs command works well for quickly accessing application logs, it
+generally does not scale to large systems or systems that produce a lot of log
+output, especially for the long-term storage of logs. Nomad's retention of log
+files is best effort, so chatty applications should use a better log retention
+strategy.
+
+Since applications log to the `alloc/` directory, all tasks within the same task
+group have access to each others logs. Thus it is possible to have a task group
+as follows:
+
+```hcl
+group "my-group" {
+  task "server" {
+    # ...
+
+    # Setting the server task as the leader of the task group allows Nomad to
+    # signal the log shipper task to gracefully shutdown when the server exits.
+    leader = true
+  }
+
+  task "log-shipper" {
+    # ...
+  }
+}
+```
+
+In the above example, the `server` task is the application that should be run
+and will be producing the logs. The `log-shipper` reads those logs from the
+`alloc/logs/` directory and sends them to a longer-term storage solution such as
+Amazon S3 or an internal log aggregation system.
+
+When using the log shipper pattern, especially for batch jobs, the main task
+should be marked as the [leader task]. By marking the main task as a leader,
+when the task completes all other tasks within the group will be gracefully
+shutdown. This allows the log shipper to finish sending any logs and then
+exiting itself. The log shipper should set a high enough [`kill_timeout`] such
+that it can ship any remaining logs before exiting.
+
+[log rotation]: /nomad/docs/job-specification/logs
+[log viewing]: /nomad/commands/alloc/logs
+[log access]: /nomad/api-docs/client#stream-logs
+[leader task]: /nomad/docs/job-specification/task#leader
+[`kill_timeout`]: /nomad/docs/job-specification/task#kill_timeout
diff --git a/content/nomad/v1.11.x/content/docs/job-run/utilization-metrics.mdx b/content/nomad/v1.11.x/content/docs/job-run/utilization-metrics.mdx
new file mode 100644
index 0000000000..76c243c7e7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-run/utilization-metrics.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Collect resource utilization metrics
+description: |-
+  Inspect the resource consumption and utilization information of a job with
+  the task drivers in Nomad.
+---
+
+# Collect resource utilization metrics
+
+Understanding the resource utilization of an application is important, and Nomad
+supports reporting detailed statistics in many of its drivers. The main
+interface for outputting resource utilization is the `alloc status` command with
+the `-stats` flag.
+
+This section will use the job named "docs", but
+these operations and command largely apply to all jobs in Nomad.
+
+Here is the output of the run command for the "docs" job.
+
+```shell-session
+$ nomad job run docs.nomad.hcl
+==> Monitoring evaluation "42d788a3"
+    Evaluation triggered by job "docs"
+    Allocation "04d9627d" created: node "a1f934c9", group "example"
+    Allocation "e7b8d4f5" created: node "012ea79b", group "example"
+    Allocation "5cbf23a1" modified: node "1e1aa1e0", group "example"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "42d788a3" finished with status "complete"
+```
+
+To fetch the detailed usage statistics, issue the following command. Your
+allocation id will be different; replace `04d9627d` with the allocation id from
+your running "docs" job:
+
+```shell-session
+$ nomad alloc status -stats 04d9627d
+ID            = 04d9627d
+Eval ID       = 42d788a3
+Name          = docs.example[2]
+Node ID       = a1f934c9
+Job ID        = docs
+Client Status = running
+
+Task "server" is "running"
+Task Resources
+CPU        Memory          Disk      Addresses
+75/100 MHz  784 KiB/10 MiB  300 MiB  http: 10.1.1.196:5678
+
+Memory Stats
+Cache   Max Usage  RSS      Swap
+56 KiB  1.3 MiB    784 KiB  0 B
+
+CPU Stats
+Percent  Throttled Periods  Throttled Time
+0.00%    0                  0
+
+Recent Events:
+Time         Type      Description
+<timestamp>  Started   Task started by client
+<timestamp>  Received  Task received by client
+```
+
+The output indicates that the job is running near the limit of configured CPU
+but has plenty of memory headroom. You can use this information to alter the
+job's resources to better reflect its actual needs:
+
+```hcl
+resources {
+  cpu    = 200
+  memory = 10
+}
+```
+
+Adjusting resources is very important for a variety of reasons:
+
+- Ensuring your application does not get OOM killed if it hits its memory limit.
+- Ensuring the application performs well by ensuring it has some CPU allowance.
+- Optimizing cluster density by reserving what you need and not over-allocating.
+
+While single point in time resource usage measurements are useful, it is often
+more useful to graph resource usage over time to better understand and estimate
+resource usage. Nomad supports outputting resource data to statsite and statsd
+and is the recommended way of monitoring resources. For more information about
+outputting telemetry, consult the [Telemetry Guide].
+
+For more advanced use cases, the resource usage data is also accessible via the
+client's HTTP API. Learn more about it in the [`allocation` API] documentation.
+
+[telemetry guide]:/nomad/docs/monitor
+[`allocation` api]: /nomad/api-docs/client
diff --git a/content/nomad/v1.11.x/content/docs/job-run/versions.mdx b/content/nomad/v1.11.x/content/docs/job-run/versions.mdx
new file mode 100644
index 0000000000..592a687f07
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-run/versions.mdx
@@ -0,0 +1,552 @@
+---
+layout: docs
+page_title: Create and modify job versions
+description: |-
+  Create, modify, delete, compare, and revert job versions with the Nomad CLI, API, or UI.
+---
+
+# Create and modify job versions
+
+Nomad creates a new version for your job each time you run your job. A job can
+have an unlimited number of versions, and version history is stored in state.
+Over time, Nomad garbage collects dead versions that do not have a version tag. Saving a tag to a version prevents Nomad from garbage collecting that version.
+
+This guide demonstrates the following job version features:
+
+- Create, modify, and delete job version tags.
+- Compare versions.
+- Revert a running job to an older version, no matter how much time has passed.
+- Clone a version.
+
+## Prerequisites
+
+- This feature requires Nomad v1.9.0 and later.
+- You are familiar with [job versions and tags][job-concept].
+
+## Create the `hello-world` job
+
+The examples use a job named `hello-world`, which is one of Nomad's job
+templates.
+
+1. On the **Jobs** page, click **Run Job**.
+1. Click **Choose from template**.
+1. Select **Hello world**.
+1. Click **Apply**.
+1. Click **Plan**.
+1. Review the **Job Plan** output.
+1. Click **Run** to run the `hello-world` job.
+
+## Create a version tag
+
+When you create a version tag, you should provide Nomad with these attributes:
+
+- A tag name
+- A job name
+- A version number
+
+The following example creates a tag named `golden-version` for version zero of `hello-world`. It includes a description of the tag.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job tag apply [options] <job_id>` command to create a tag.
+
+```shell-session
+$ nomad job tag apply -version 0 -name "golden-version" \
+    -description "The version we can roll back to." \
+    hello-world
+
+Job version 0 tagged with name "golden-version"
+```
+
+Note that Nomad tags the latest version if you omit the version number.
+
+Refer to the [`job tag apply`][job-tag-apply-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "The version we can roll back to."}'
+```
+
+The JSON response is similar to the following example.
+
+```json
+{
+  "Name":"golden-version",
+  "Description":"The version we can roll back to.",
+  "TaggedTime":1728325495829793000,
+  "Index":361,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+Refer to the Jobs HTTP API [Create Job Version Tag][job-tag-apply-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **Tag this version**.
+1. Enter `golden version` in the **Tag Name** field and `The version we can roll
+   back to.` in the **Tag Description** field.
+1. Click **Save**.
+
+Version zero now has a `golden-version` tag.
+
+![Version tag](/img/nomad/job-version-tag/nomad-ui-version-tag.png)
+
+</Tab>
+</Tabs>
+
+Using the CLI, you can run a new version of your job and create a tag for that
+new version. The following example runs a new version of the hello-world job and
+immediately tags that version.
+
+```shell-session
+$ nomad job run hello-world.nomad.hcl && \
+  nomad job tag apply -name "high-traffic-version" hello-world
+
+==> 2024-10-08T14:42:30-05:00: Monitoring evaluation "90714134"
+    2024-10-08T14:42:30-05:00: Evaluation triggered by job "hello-world"
+    2024-10-08T14:42:31-05:00: Evaluation within deployment: "192ecea1"
+    2024-10-08T14:42:31-05:00: Allocation "ec85c1bd" created: node "d6ee954e", group "servers"
+    2024-10-08T14:42:31-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2024-10-08T14:42:31-05:00: Evaluation "90714134" finished with status "complete"
+==> 2024-10-08T14:42:31-05:00: Monitoring deployment "192ecea1"
+  ✓ Deployment "192ecea1" successful
+
+    2024-10-08T14:42:48-05:00
+    ID          = 192ecea1
+    Job ID      = hello-world
+    Job Version = 4
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    servers     1        1       1        0          2024-10-08T14:52:46-05:00
+Job version 1 tagged with name "high-traffic-version"
+```
+
+## Modify a version tag
+
+The following example updates both the name and description of the `golden-version` tag for a hello-world job.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job tag apply [options] <job_id>` command to modify a tag's attributes.
+
+```shell-session
+$ nomad job tag apply -version 0 -name "golden-version-0" \
+    -description "Low traffic version." \
+    hello-world
+
+Job version 0 tagged with name "golden-version-0"
+```
+
+Refer to the [`job tag apply`][job-tag-apply-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version-0/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "Low traffic version."}'
+```
+
+The response is similar to the following.
+
+```json
+{
+  "Name":"golden-version-0",
+  "Description":"Low traffic version.",
+  "TaggedTime":1728407951089465000,
+  "Index":3460,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+See the Jobs HTTP API [Create Job Version Tag][job-tag-apply-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **golden-version**.
+1. Edit the tag name and description.
+1. Click **Save**.
+
+</Tab>
+</Tabs>
+
+## Delete a version tag
+
+The following example deletes the `golden-version` tag attached to the `hello-world` job.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use `nomad job tag unset -name "<tag_name>" <job_id>` to delete a tag from a version. This command requires a tag name and job ID.
+
+```shell-session
+$ nomad job tag unset -name "golden-version" hello-world
+
+removed from job "hello-world"
+```
+
+Refer to the [`job tag unset`][job-tag-unset-cli] command reference for details on
+including general options such as `namespace`.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `DELETE`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+This example assumes the Nomad API is accessible on `localhost:4646`.
+
+```shell-session
+$ curl -X DELETE \
+  localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+  -H "Content-Type: application/json"
+```
+
+The response is similar to the following.
+
+```json
+{
+  "Name":"",
+  "Description":"",
+  "TaggedTime":0,
+  "Index":5135,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
+Refer to the Jobs HTTP API [Delete Job Version Tag][job-tag-unset-api] reference for
+details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find **Version #0** in the list.
+1. Click **golden-version**.
+1. Click **Delete** to remove the tag.
+
+</Tab>
+</Tabs>
+
+## Compare versions
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the [`nomad job history -p` command][nomad-job-history-cli] to compare
+different job versions. The `-p` option displays the differences between each
+version and the most recent version. You also have these options:
+
+- `-diff-version`: Specifies the version number of the job to compare against.
+    Mutually exclusive with the `-diff-tag` flag.
+- `-diff-tag`: Specifies the version of the job to compare against, referenced
+  by tag name. Defaults to the latest version. Mutually exclusive with `-diff-version`.
+
+### Show diff based on a version
+
+The `nomad job history -p -diff-version <job_id>` command compares all
+versions against the specified `diff-version`.
+
+The following example compares all job versions to version 4.
+
+```shell-session
+$ nomad job history -p -diff-version=4 hello-world
+```
+
+You can also perform a diff between two specific versions. This example compares
+ version 4 of the hello-world job with version 1 of the job.
+
+```shell-session
+$ nomad job history -p -version=4 -diff-version=1 hello-world
+```
+
+### Show diff based on a tag
+
+The `nomad job history -p -diff-tag <job_id>` command compares all
+versions against the specified `diff-tag`.
+
+The following example compares all job versions to the version tagged with the name `golden-version`.
+
+```shell-session
+$ nomad job history -p -diff-tag="golden-version" hello-world
+```
+
+You can also perform a diff between a tag and a version number. The following
+example compares the current version, `-version=4`, with the version tagged
+`golden-version`.
+
+```shell-session
+$ nomad job history -p -version=4 -diff-tag="golden-version" hello-world
+
+Version     = 4
+Stable      = true
+Submit Date = 2024-10-08T14:42:30-05:00
+Tag Name    = high-traffic-version
+Diff        =
++/- Job: "hello-world"
++/- Task Group: "servers"
+  +   Network {
+        Hostname: ""
+        Mode:     ""
+      + Dynamic Port {
+        + HostNetwork: "default"
+        + Label:       "www"
+        + To:          "8002"
+        }
+      }
+  -   Network {
+        Hostname: ""
+        Mode:     ""
+      - Dynamic Port {
+        - HostNetwork: "default"
+        - Label:       "www"
+        - To:          "8001"
+        }
+      }
+```
+
+</Tab>
+<Tab heading="API">
+
+You can get a version list with the `Diffs` field populated. To compare all
+versions to a specific version, use the `diff_version` query parameter.
+
+This example compares all versions to version one.
+
+```shell-session
+$ curl -X GET \
+  localhost:4646/v1/job/hello-world/versions?diffs=true&diff_version=1
+```
+
+Refer to the Jobs HTTP API [List Job Versions][job-list-diff-api] reference for
+details and complete examples.
+
+</Tab>
+<Tab heading="Web UI">
+
+The job detail's **Versions** tab shows the list of versions.
+
+![Version diff features](/img/nomad/job-version-tag/nomad-ui-version-diff.png)
+
+The two important elements are the **Diff against** dropdown, labeled "1", and
+the changes show or hide toggle, labeled "2".
+
+The **Diff against** dropdown contains versions or tags that change how the UI
+compares the versions against each other.
+
+![Version diff dropdown items](/img/nomad/job-version-tag/nomad-ui-diff-dd.png)
+
+The **Diff against previous version** option means that each version displays
+the difference with the previous version in the list. The **See Change**
+toggle displays the number of changes. Click the **See Change** arrow
+to review the actual difference.
+
+![Version diff previous](/img/nomad/job-version-tag/nomad-ui-diffs-expanded.png)
+
+When you select a version or tag, the UI
+automatically displays the differences each version has with the selected
+version.
+
+![Each version's difference with version seven](/img/nomad/job-version-tag/nomad-ui-diff-changes.png)
+
+</Tab>
+</Tabs>
+
+## Revert to a version
+
+Use job tags to revert the current running job to a prior version.
+
+The following examples revert versions of the `hello-world` job to specific version number or tag names.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad job revert [options] <job_id> <version|tag>` command to revert
+the current job to a prior version.
+
+This example reverts the job to version three.
+
+```shell-session
+$ nomad job revert hello-world 3
+```
+
+This example reverts the job to the version with the `golden-version` tag.
+
+```shell-session
+$ nomad job revert hello-world "golden-version"
+```
+
+Refer to the [`job revert`][job-revert-cli] command reference for more examples
+as well as details on including general options such as namespace.
+
+</Tab>
+<Tab heading="API">
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+You can revert a job to a previous version by specifying version number or the
+tag name.
+
+This example reverts the current job to version six.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/revert \
+ -H "Content-Type: application/json" -d \
+ '{"JobID": "hello-world", "JobVersion": 6}'
+```
+
+This example reverts the current job to the version tagged `golden-version`.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/revert \
+ -H "Content-Type: application/json" -d \
+ '{"JobID": "hello-world", "TaggedVersion": "golden-version"}'
+```
+
+The JSON response for both examples is similar to the following.
+
+```json
+{
+  "EvalID":"c3b8b0b1-85b5-34f9-de70-80d859c6466a",
+  "EvalCreateIndex":6442,
+  "JobModifyIndex":6442,
+  "Warnings":"",
+  "Index":6442,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
+Refer to the Jobs HTTP API [Revert to older Job Version][job-revert-api]
+reference for details on path and payload parameters.
+
+</Tab>
+<Tab heading="Web UI">
+
+In this example, you revert the current job to the version with the
+`golden-version` tag.
+
+![Revert job](/img/nomad/job-version-tag/nomad-ui-revert-job.png)
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click **Versions**.
+1. Find the version with the `golden-version` tag.
+1. Click **Revert Version**. The UI asks you to confirm.
+1. Click **Yes, Revert Version** to complete the reversion process.
+
+The UI then displays the **Overview** tab, where you can review the new version deployment.
+
+</Tab>
+</Tabs>
+
+## Clone a version
+
+Use the web UI to clone a job version.
+
+You can use a cloned version for a new version of the same job or to create a new job.
+
+### Clone as new version
+
+In this example, you clone the `hello-world` job's `golden-version`, edit the
+job spec, plan, and then run the new version.
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click the **Versions** tab.
+1. Under the version with the `golden-version` tag, click **Clone and Edit**.
+1. Click **Clone as New Version of hello-world**.
+1. Edit the job definition.
+
+   Since this job spec was created using HCL, the UI displays the definition in the **Job Spec** tab.
+
+   Change the network port to `8080`.
+
+   <Warning>
+   If you choose to edit the JSON in the <strong>Full Definition</strong> tab,
+   the JSON definition replaces the HCL definition, so you lose the HCL
+   job spec.
+   We recommending using HCL for job specs.
+   </Warning>
+
+1. Click **Plan**.
+1. Review the plan output.
+1. Click **Run** to run the new version.
+
+The **Versions** tab displays the new version.
+
+### Clone as new job
+
+In this example, you clone the `hello-world` job's `golden-version`, edit the
+job name and network port, plan, and then run the new job.
+
+1. From the **Jobs** screen, click the **hello-world** job to display job details.
+1. Click the **Versions** tab.
+1. Under the version with the `golden-version` tag, click **Clone and Edit**.
+1. Click **Clone as New Job**.
+1. Edit the job spec.
+
+   Change the job name to `hello-earth` and the network port to `9080`. You must change the job name. Otherwise, Nomad creates a new version of the
+   original job.
+
+1. Click **Plan**.
+1. Review the plan output.
+1. Click **Run** to run the new job.
+
+Nomad loads the **Overview** of the `hello-earth` job so you can review the deployment.
+
+[job-concept]: /nomad/docs/concepts/job#job-versions
+[job-tag-apply-cli]: /nomad/commands/job/tag/apply
+[job-tag-apply-api]: /nomad/api-docs/jobs#create-job-version-tag
+[job-tag-unset-cli]: /nomad/commands/job/tag/unset
+[job-tag-unset-api]: /nomad/api-docs/jobs#delete-job-version-tag
+[nomad-job-history-cli]: /nomad/commands/job/history
+[job-list-diff-api]: /nomad/api-docs/jobs#list-job-versions
+[job-revert-cli]: /nomad/commands/job/revert
+[job-revert-api]: /nomad/api-docs/jobs#revert-to-older-job-version
diff --git a/content/nomad/v1.11.x/content/docs/job-scheduling/affinity.mdx b/content/nomad/v1.11.x/content/docs/job-scheduling/affinity.mdx
new file mode 100644
index 0000000000..df43fef4e8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-scheduling/affinity.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Job placements with affinities
+description: >-
+  Configure affinities to express placement preferences for your jobs. Create a
+  job with an affinity, submit it to Nomad, and monitor it after placement.
+---
+
+# Job placements with affinities
+
+The [affinity][affinity-stanza] stanza allows operators to express placement
+preferences for their jobs on particular types of nodes. Note that there is a
+key difference between the [constraint][constraint] stanza and the affinity
+stanza. The constraint stanza strictly filters where jobs are run based on
+[attributes][attributes] and [client metadata][client-metadata]. If no nodes are
+found to match, the placement does not succeed. The affinity stanza acts like a
+"soft constraint." Nomad will attempt to match the desired affinity, but
+placement will succeed even if no nodes match the desired criteria. This is done
+in conjunction with scoring based on the Nomad scheduler's bin packing algorithm
+which you can read more about [here][scheduling].
+
+In this guide, you will encounter a sample application. Your application can run
+in datacenters `dc1` and `dc2`; however, you have a strong preference to run it in
+dc2. You will learn how to configure the job to inform the scheduler of your
+preference, while still allowing it to place your workload in `dc1` if the
+desired resources aren't available in dc2.
+
+By specify an affinity with the proper [weight], the Nomad scheduler can find
+the best nodes on which to place your job. The affinity weight will be included
+when scoring nodes for placement along with other factors like the bin-packing
+algorithm.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment. This guide will assume a cluster with one server node and
+three client nodes.
+
+<Tip>
+
+ This guide is for demo purposes and is only using a single
+server node. In a production cluster, 3 or 5 server nodes are recommended.
+
+</Tip>
+
+## Place one of the client nodes in a different datacenter
+
+You are going express your job placement preference based on the datacenter your
+nodes are located in. Choose one of your client nodes and edit
+`/etc/nomad.d/nomad.hcl` to change its location to `dc2`. A snippet of an
+example configuration file is show below with the required change is shown
+below.
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+datacenter = "dc2"
+
+# Enable the client
+client {
+  enabled = true
+# ...
+}
+```
+
+After making the change on your chosen client node, restart the Nomad service
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+If everything worked correctly, one of your nodes will now show datacenter `dc2`
+when you run the [`nomad node status`][node-status] command.
+
+```shell-session
+$ nomad node status
+ID        DC   Name              Class   Drain  Eligibility  Status
+3592943e  dc1  ip-172-31-27-159  <none>  false  eligible     ready
+3dea0188  dc1  ip-172-31-16-175  <none>  false  eligible     ready
+6b6e9518  dc2  ip-172-31-27-25   <none>  false  eligible     ready
+```
+
+## Create a job with an affinity
+
+Create a file with the name `redis.nomad.hcl` and place the following content in it:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1", "dc2"]
+  type        = "service"
+
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "dc2"
+    weight    = 100
+  }
+
+  group "cache1" {
+    count = 4
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    service {
+      name = "redis-cache"
+      port = "db"
+
+      check {
+        name     = "alive"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+Observe that the job uses the `affinity` stanza and specifies `dc2` as the value
+for the `${node.datacenter}` [attribute][attributes]. It also uses the value
+`100` for the [weight][weight] which will cause the Nomad scheduler to rank
+nodes in datacenter `dc2` with a higher score. Keep in mind that weights can
+range from -100 to 100, inclusive. Negative weights serve as anti-affinities
+which cause Nomad to avoid placing allocations on nodes that match the criteria.
+
+## Register the redis Nomad job
+
+Run the Nomad job with the following command:
+
+```shell-session
+$ nomad run redis.nomad.hcl
+==> Monitoring evaluation "11388ef2"
+    Evaluation triggered by job "redis"
+    Allocation "0dfcf0ba" created: node "6b6e9518", group "cache1"
+    Allocation "89a9aae9" created: node "3592943e", group "cache1"
+    Allocation "9a00f742" created: node "6b6e9518", group "cache1"
+    Allocation "fc0f21bc" created: node "3dea0188", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "11388ef2" finished with status "complete"
+```
+
+Note that two of the allocations in this example have been placed on node
+`6b6e9518`. This is the node configured to be in datacenter `dc2`. The Nomad
+scheduler selected this node because of the affinity specified. All of the
+allocations have not been placed on this node because the Nomad scheduler
+considers other factors in the scoring such as bin-packing. This helps avoid
+placing too many instances of the same job on a node and prevents reduced
+capacity during a node level failure. You will take a detailed look at the
+scoring in the next few steps.
+
+## Check the status of the job
+
+At this point, Check the status of the job and verify where the allocations
+have been placed. Run the following command:
+
+```shell-session
+$ nomad status redis
+```
+
+There should be four instances of the job running in the `Summary` section of
+the output as shown below:
+
+```plaintext
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache1      0       0         4        0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+0dfcf0ba  6b6e9518  cache1      0        run      running  1h44m ago  1h44m ago
+89a9aae9  3592943e  cache1      0        run      running  1h44m ago  1h44m ago
+9a00f742  6b6e9518  cache1      0        run      running  1h44m ago  1h44m ago
+fc0f21bc  3dea0188  cache1      0        run      running  1h44m ago  1h44m ago
+```
+
+You can cross-check this output with the results of the `nomad node status`
+command to verify that the majority of your workload has been placed on the node
+in `dc2`. In the case of the above output, that node is `6b6e9518`.
+
+## Obtain detailed scoring information on job placement
+
+The Nomad scheduler will not always place all of your workload on nodes you have
+specified in the `affinity` stanza even if the resources are available. This is
+because affinity scoring is combined with other metrics as well before making a
+scheduling decision. In this step, you will take a look at some of those other
+factors.
+
+Using the output from the previous step, find an allocation that has been placed
+on a node in `dc2` and use the [`nomad alloc status`][alloc status] command with
+the [`-verbose`][verbose] option to obtain detailed scoring information on it.
+In this example, the allocation ID to be inspected is `0dfcf0ba` (your
+allocation IDs will be different).
+
+```shell-session
+$ nomad alloc status -verbose 0dfcf0ba
+```
+
+The resulting output will show the `Placement Metrics` section at the bottom.
+
+```plaintext
+...
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+6b6e9518-d2a4-82c8-af3b-6805c8cdc29c  0.33     0                  0                        1              0.665
+3dea0188-ae06-ad98-64dd-a761ab2b1bf3  0.33     0                  0                        0              0.33
+3592943e-67e4-461f-d888-d5842372a4d4  0.33     0                  0                        0              0.33
+```
+
+Note that the results from the `binpack`, `job-anti-affinity`,
+`node-reschedule-penalty`, and `node-affinity` columns are combined to produce
+the numbers listed in the `final score` column for each node. The Nomad
+scheduler uses the final score for each node in deciding where to make
+placements.
+
+## Next steps
+
+Experiment with the weight provided in the `affinity` stanza (the value can be
+from -100 through 100) and observe how the final score given to each node
+changes (use the `nomad alloc status` command as shown in the previous step).
+
+### Reference material
+
+- The [affinity][affinity-stanza] stanza documentation
+- [Scheduling][scheduling] with Nomad
+
+[affinity-stanza]: /nomad/docs/job-specification/affinity
+[alloc status]: /nomad/commands/alloc/status
+[attributes]: /nomad/docs/reference/runtime-variable-interpolation#node-attributes
+[constraint]: /nomad/docs/job-specification/constraint
+[client-metadata]: /nomad/docs/configuration/client#meta
+[node-status]: /nomad/commands/node/status
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[verbose]: /nomad/commands/alloc/status#verbose
+[weight]: /nomad/docs/job-specification/affinity#weight
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
diff --git a/content/nomad/v1.11.x/content/docs/job-scheduling/index.mdx b/content/nomad/v1.11.x/content/docs/job-scheduling/index.mdx
new file mode 100644
index 0000000000..922967e6b7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-scheduling/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Advanced job scheduling
+description: >-
+  Discover the advanced scheduling features available to Nomad jobs including affinity and spread.
+---
+
+# Advanced job scheduling
+
+The Nomad [scheduler][scheduling] uses a bin-packing algorithm to optimize the
+resource utilization and density of applications in your Nomad cluster. Nomad
+0.9 adds new features to allow operators more fine-grained control over
+allocation placement. This enables use cases similar to the following:
+
+- Expressing preference for a certain class of nodes for a specific application
+  via the [affinity stanza][affinity-stanza].
+
+- Spreading allocations across a datacenter, rack or any other node attribute or
+  metadata with the [spread stanza][spread-stanza].
+
+Please refer to the tutorials below for using affinity and spread in Nomad 0.9.
+
+- [Preemption][preemption-guide]
+- [Affinity][affinity-guide]
+- [Spread][spread-guide]
+
+[affinity-guide]: /nomad/docs/job-scheduling/affinity
+[affinity-stanza]: /nomad/docs/job-specification/affinity
+[preemption-guide]: /nomad/docs/job-scheduling/preemption
+[preemption-stanza]: /nomad/docs/job-specification/spread
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[spread-guide]: /nomad/docs/job-scheduling/spread
+[spread-stanza]: /nomad/docs/job-specification/spread
diff --git a/content/nomad/v1.11.x/content/docs/job-scheduling/preemption.mdx b/content/nomad/v1.11.x/content/docs/job-scheduling/preemption.mdx
new file mode 100644
index 0000000000..24dffc0f46
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-scheduling/preemption.mdx
@@ -0,0 +1,502 @@
+---
+layout: docs
+page_title: Use preemption for job priority
+description: >-
+  Deploy a low priority job and a high priority job. Then use preemption
+  to run the higher priority job even when other jobs are running.
+---
+
+# Use preemption for job priority
+
+Preemption allows Nomad to evict running allocations to place allocations of a
+higher priority. Allocations of a job that are blocked temporarily go into
+"pending" status until the cluster has additional capacity to run them. This is
+useful when operators need to run relatively higher priority tasks sooner even
+under resource contention across the cluster.
+
+Nomad v0.9.0 added Preemption for [system][system-job] jobs. Nomad v0.9.3
+[Enterprise][enterprise] added preemption for [service][service-job] and
+[batch][batch-job] jobs. Nomad v0.12.0 made preemption an open source feature
+for all three job types.
+
+Preemption is enabled by default for system jobs. It can be enabled for service
+and batch jobs by sending a [payload][payload-preemption-config] with the
+appropriate options specified to the [scheduler configuration][update-scheduler]
+API endpoint.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment; however, you need to use Nomad v0.12.0 or higher or Nomad
+Enterprise v0.9.3 or higher.
+
+You need a cluster with one server node and three client nodes. To simulate
+resource contention, the nodes in this environment each have 1 GB RAM (For AWS,
+you can choose the [t2.micro][t2-micro] instance type).
+
+<Tip>
+
+ This tutorial is for demo purposes and is only using a
+single server node. Three or five server nodes are recommended for a
+production cluster.
+
+</Tip>
+
+## Create a job with low priority
+
+Start by creating a job with relatively lower priority into your Nomad cluster.
+One of the allocations from this job will be preempted in a subsequent
+deployment when there is a resource contention in the cluster. Copy the
+following job into a file and name it `webserver.nomad.hcl`.
+
+```hcl
+job "webserver" {
+  datacenters = ["dc1"]
+  type        = "service"
+  priority    = 40
+
+  group "webserver" {
+    count = 3
+    network {
+      port "http" {
+        to = 80
+      }
+    }
+
+    service {
+      name = "apache-webserver"
+      port = "http"
+
+      check {
+        name     = "alive"
+        type     = "http"
+        path     = "/"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    task "apache" {
+      driver = "docker"
+
+      config {
+        image = "httpd:latest"
+        ports = ["http"]
+      }
+
+      resources {
+        memory = 600
+      }
+    }
+  }
+}
+```
+
+Note that the [count][count] is 3 and that each allocation is specifying 600 MB
+of [memory][memory]. Remember that each node only has 1 GB of RAM.
+
+## Run the low priority job
+
+Use the [`nomad job run` command][] to start the `webserver.nomad.hcl` job.
+
+```shell-session
+$ nomad job run webserver.nomad.hcl
+==> Monitoring evaluation "35159f00"
+    Evaluation triggered by job "webserver"
+    Evaluation within deployment: "278b2e10"
+    Allocation "0850e103" created: node "cf8487e2", group "webserver"
+    Allocation "551a7283" created: node "ad10ba3b", group "webserver"
+    Allocation "8a3d7e1e" created: node "18997de9", group "webserver"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "35159f00" finished with status "complete"
+```
+
+Check the status of the `webserver` job using the [`nomad job status` command][]
+at this point and verify that an allocation has been placed on each client node
+in the cluster.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+0850e103  cf8487e2  webserver   0        run      running  8s ago   2s ago
+551a7283  ad10ba3b  webserver   0        run      running  8s ago   2s ago
+8a3d7e1e  18997de9  webserver   0        run      running  8s ago   1s ago
+```
+
+## Create a job with high priority
+
+Create another job with a [priority] greater than the "webserver" job. Copy the
+following into a file named `redis.nomad.hcl`.
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+  priority    = 80
+
+  group "cache1" {
+    count = 1
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    service {
+      name = "redis-cache"
+      port = "db"
+
+      check {
+        name     = "alive"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+        ports = ["db"]
+      }
+
+      resources {
+        memory = 700
+      }
+    }
+  }
+}
+```
+
+Note that this job has a priority of 80 (greater than the priority of the
+`webserver` job from earlier) and requires 700 MB of memory. This allocation
+will create a resource contention in the cluster since each node only has 1 GB
+of memory with a 600 MB allocation already placed on it.
+
+## Observe a run before and after enabling preemption
+
+### Try to run `redis.nomad.hcl`
+
+Remember that preemption for service and batch jobs is [not enabled by
+default][preemption-config]. This means that the `redis` job will be queued due
+to resource contention in the cluster. You can verify the resource contention
+before actually registering your job by running the [`nomad job plan` command][].
+
+```shell-session
+$ nomad job plan redis.nomad.hcl
++ Job: "redis"
++ Task Group: "cache1" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache1" (failed to place 1 allocation):
+    * Resources exhausted on 3 nodes
+    * Dimension "memory" exhausted on 3 nodes
+...
+```
+
+Run the `redis.nomad.hcl` job with the [`nomad job run` command][]. Observe that the
+allocation was queued.
+
+```shell-session
+$ nomad job run redis.nomad.hcl
+==> Monitoring evaluation "3c6593b4"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "ae55a4aa"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "3c6593b4" finished with status "complete" but failed to place all allocations:
+    Task Group "cache1" (failed to place 1 allocation):
+      * Resources exhausted on 3 nodes
+      * Dimension "memory" exhausted on 3 nodes
+    Evaluation "249fd21b" waiting for additional capacity to place remainder
+```
+
+You can also verify the allocation has been queued by now by fetching the status
+of the job using the [`nomad job status` command][].
+
+```shell-session
+$ nomad job status redis
+ID            = redis
+Name          = redis
+Submit Date   = 2021-02-11T19:22:55-05:00
+Type          = service
+Priority      = 80
+...
+Placement Failure
+Task Group "cache1":
+  * Resources exhausted on 3 nodes
+  * Dimension "memory" exhausted on 3 nodes
+...
+Allocations
+No allocations placed
+```
+
+Stop the `redis` job for now. In the next steps, you will enable service job
+preemption and re-deploy. Use the [`nomad job stop` command][] with the `-purge`
+flag set.
+
+```shell-session
+$ nomad job stop -purge redis
+==> Monitoring evaluation "a9c9945d"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "ae55a4aa"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a9c9945d" finished with status "complete"
+```
+
+### Enable service job preemption
+
+Get the current [scheduler configuration][scheduler-configuration] using the
+Nomad API. Setting an environment variable with your cluster address makes the
+`curl` commands more reusable. Substitute in the proper address for your Nomad
+cluster.
+
+```shell-session
+$ export NOMAD_ADDR=http://127.0.0.1:4646
+```
+
+If you are enabling preemption in an ACL-enabled Nomad cluster, you will also
+need to [authenticate to the API][api-auth] with a Nomad token via the
+`X-Nomad-Token` header. In this case, you can use an environment variable to add
+the header option and your token value to the command. If you don't use tokens,
+skip this step. The `curl` commands will run correctly when the variable is
+unset.
+
+```shell-session
+$ export NOMAD_AUTH='--header "X-Nomad-Token: «replace with your token»"'
+```
+
+ACLs, consult the
+
+Now, fetch the configuration with the following `curl` command.
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration?pretty
+```
+
+```json
+{
+  "SchedulerConfig": {
+    "SchedulerAlgorithm": "binpack",
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    },
+    "CreateIndex": 5,
+    "ModifyIndex": 5
+  },
+  "Index": 5,
+  "LastContact": 0,
+  "KnownLeader": true
+}
+```
+
+Note that [BatchSchedulerEnabled][batch-enabled] and
+[ServiceSchedulerEnabled][service-enabled] are both set to `false` by default.
+Since you are preempting service jobs in this guide, you need to set
+`ServiceSchedulerEnabled` to `true`. Do this by directly interacting
+with the [API][update-scheduler].
+
+Create the following JSON payload and place it in a file named `scheduler.json`:
+
+```json
+{
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+Note that [ServiceSchedulerEnabled][service-enabled] has been set to `true`.
+
+Run the following command to update the scheduler configuration:
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  --request POST --data @scheduler.json \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration
+```
+
+You should now be able to inspect the scheduler configuration again and verify
+that preemption has been enabled for service jobs (output below is abbreviated):
+
+```shell-session
+$ curl --silent ${NOMAD_AUTH} \
+  ${NOMAD_ADDR}/v1/operator/scheduler/configuration?pretty
+```
+
+```plaintext
+...
+        "PreemptionConfig": {
+            "SystemSchedulerEnabled": true,
+            "BatchSchedulerEnabled": false,
+            "ServiceSchedulerEnabled": true
+        },
+...
+```
+
+### Try running the redis job again
+
+Now that you have enabled preemption on service jobs, deploying your `redis` job
+should evict one of the lower priority `webserver` allocations and place it into
+a queue. You can run `nomad plan` to output a preview of what will happen:
+
+```shell-session
+$ nomad job plan redis.nomad.hcl
++ Job: "redis"
++ Task Group: "cache1" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID     Task Group
+8a3d7e1e-40ee-f731-5135-247d8b7c2901  webserver  webserver
+...
+```
+
+The preceding plan output shows that one of the `webserver` allocations will be
+evicted in order to place the requested `redis` instance.
+
+Now use the [`nomad job run` command][] to run the `redis.nomad.hcl` job file.
+
+```shell-session
+$ nomad job run redis.nomad.hcl
+==> Monitoring evaluation "fef3654f"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "37b37a63"
+    Allocation "6ecc4bbe" created: node "cf8487e2", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "fef3654f" finished with status "complete"
+```
+
+Run the [`nomad job status` command][] on the `webserver` job to verify one of
+the allocations has been evicted.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+webserver   1       0         2        0       1         0
+
+Placement Failure
+Task Group "webserver":
+  * Resources exhausted on 3 nodes
+  * Dimension "memory" exhausted on 3 nodes
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
+0850e103  cf8487e2  webserver   0        evict    complete  21m17s ago  18s ago
+551a7283  ad10ba3b  webserver   0        run      running   21m17s ago  20m55s ago
+8a3d7e1e  18997de9  webserver   0        run      running   21m17s ago  20m57s ago
+```
+
+### Stop the job
+
+Use the [`nomad job stop` command][] on the `redis` job. This will provide the
+capacity necessary to unblock the third `webserver` allocation.
+
+```shell-session
+$ nomad job stop redis
+==> Monitoring evaluation "df368cb1"
+    Evaluation triggered by job "redis"
+    Evaluation within deployment: "37b37a63"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "df368cb1" finished with status "complete"
+```
+
+Run the [`nomad job status` command][] on the `webserver` job. The output should
+now indicate that a new third allocation was created to replace the one that was
+preempted.
+
+```shell-session
+$ nomad job status webserver
+ID            = webserver
+Name          = webserver
+Submit Date   = 2021-02-11T19:18:29-05:00
+Type          = service
+Priority      = 40
+Datacenters   = dc1
+Namespace     = default
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+webserver   0       0         3        0       1         0
+
+Latest Deployment
+ID          = 278b2e10
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+webserver   3        3       3        0          2021-02-12T00:28:51Z
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created     Modified
+4e212aec  cf8487e2  webserver   0        run      running   21s ago     3s ago
+0850e103  cf8487e2  webserver   0        evict    complete  22m48s ago  1m49s ago
+551a7283  ad10ba3b  webserver   0        run      running   22m48s ago  22m26s ago
+8a3d7e1e  18997de9  webserver   0        run      running   22m48s ago  22m28s ago
+```
+
+## Next steps
+
+The process you learned in this tutorial can also be applied to
+[batch][batch-enabled] jobs as well. Read more about preemption in the
+[Nomad documentation][preemption].
+
+### Reference material
+
+- [Preemption][preemption]
+
+[batch-enabled]: /nomad/api-docs/operator/scheduler#batchschedulerenabled-1
+[batch-job]: /nomad/docs/concepts/scheduling/schedulers#batch
+[count]: /nomad/docs/job-specification/group#count
+[enterprise]: /nomad/docs/enterprise
+[memory]: /nomad/docs/job-specification/resources#memory
+[payload-preemption-config]: //nomad/api-docs/operator/scheduler#preemptionconfig-1
+[preemption-config]: /nomad/api-docs/operator/scheduler#preemptionconfig-1
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[priority]: /nomad/docs/job-specification/job#priority
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[scheduler-configuration]: /nomad/api-docs/operator/scheduler#read-scheduler-configuration
+[service-enabled]: /nomad/api-docs/operator/scheduler#serviceschedulerenabled-1
+[service-job]: /nomad/docs/concepts/scheduling/schedulers#service
+[step-1]: #create-a-job-with-low-priority
+[system-job]: /nomad/docs/concepts/scheduling/schedulers#system
+[t2-micro]: https://aws.amazon.com/ec2/instance-types/
+[update-scheduler]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[`nomad job plan` command]: /nomad/commands/job/plan
+[`nomad job run` command]: /nomad/commands/job/run
+[`nomad job status` command]: /nomad/commands/job/status
+[`nomad job stop` command]: /nomad/commands/job/stop
+[api-auth]: /nomad/api-docs/#authentication
diff --git a/content/nomad/v1.11.x/content/docs/job-scheduling/spread.mdx b/content/nomad/v1.11.x/content/docs/job-scheduling/spread.mdx
new file mode 100644
index 0000000000..6ca3c50913
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-scheduling/spread.mdx
@@ -0,0 +1,277 @@
+---
+layout: docs
+page_title: Use spread to increase failure tolerance
+description: >-
+  Create a job with the spread stanza to prevent application downtime
+  as a result of a physical domain failure in a datacenter or rack.
+---
+
+# Use spread to increase failure tolerance
+
+The Nomad scheduler uses a bin-packing algorithm when making job placements on
+nodes to optimize resource utilization and density of applications. Although bin
+packing ensures optimal resource utilization, it can lead to some nodes carrying
+a majority of allocations for a given job. This can cause cascading failures
+where the failure of a single node or a single data center can lead to
+application unavailability.
+
+The [spread stanza][spread-stanza] solves this problem by allowing operators to
+distribute their workloads in a customized way based on [attributes] and/or
+[client metadata][client-metadata]. By using spread criteria in their job
+specification, Nomad job operators can ensure that failures across a domain such
+as datacenter or rack don't affect application availability.
+
+Consider a Nomad application that needs to be deployed to multiple datacenters
+within a region. Datacenter `dc1` has four nodes while `dc2` has one node. This
+application has ten instances and seven of them must be deployed to `dc1` since
+it receives more user traffic and you need to make sure the application doesn't
+suffer downtime due to not enough running instances to process requests. The
+remaining 3 allocations can be deployed to `dc2`.
+
+Use the `spread` stanza in the Nomad [job specification][job-specification] to
+ensure the 70% of the workload is being placed in datacenter `dc1` and 30% is
+being placed in `dc2`. The Nomad operator can use the [percent] option with a
+[target] to customize the spread.
+
+### Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. You can use this [repository] to provision a
+sandbox environment. This guide will assume a cluster with one server node and
+five client nodes.
+
+<Tip>
+
+ This guide is for demo purposes and is only using a single
+server node. In a production cluster, 3 or 5 server nodes are recommended.
+
+</Tip>
+
+## Place one of the client nodes in a different datacenter
+
+In this guide, you are going to customize the spread for our job placement
+between the datacenters our nodes are located in. Choose one of your client
+nodes and edit `/etc/nomad.d/nomad.hcl` to change its location to `dc2`. A
+snippet of an example configuration file is show below with the required change
+is shown below.
+
+```hcl
+data_dir = "/opt/nomad/data"
+bind_addr = "0.0.0.0"
+datacenter = "dc2"
+
+# Enable the client
+client {
+  enabled = true
+# ...
+}
+```
+
+After making the change on your chosen client node, restart the Nomad service
+
+```shell-session
+$ sudo systemctl restart nomad
+```
+
+If everything is configured correctly, you should be able to run the [`nomad node status`][node-status] command and confirm that one of your nodes is now in
+datacenter `dc2`.
+
+```shell-session
+$ nomad node status
+ID        DC   Name              Class   Drain  Eligibility  Status
+5d16d949  dc2  ip-172-31-62-240  <none>  false  eligible     ready
+7b381152  dc1  ip-172-31-59-115  <none>  false  eligible     ready
+10cc48cc  dc1  ip-172-31-58-46   <none>  false  eligible     ready
+93f1e628  dc1  ip-172-31-58-113  <none>  false  eligible     ready
+12894b80  dc1  ip-172-31-62-90   <none>  false  eligible     ready
+```
+
+## Create a job with the spread stanza
+
+Create a file with the name `redis.nomad.hcl` and place the following content in it:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1", "dc2"]
+  type        = "service"
+
+  spread {
+    attribute = "${node.datacenter}"
+    weight    = 100
+
+    target "dc1" {
+      percent = 70
+    }
+
+    target "dc2" {
+      percent = 30
+    }
+  }
+
+  group "cache1" {
+    count = 10
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:latest"
+
+        ports = ["db"]
+      }
+
+      service {
+        name = "redis-cache"
+        port = "db"
+
+        check {
+          name     = "alive"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+Note that the job specifies the `spread` stanza and specified the
+[datacenter][attributes] attribute while targeting `dc1` and `dc2` with the
+percent options. This will tell the Nomad scheduler to make an attempt to
+distribute 70% of the workload on `dc1` and 30% of the workload on `dc2`.
+
+## Register the redis.nomad.hcl job
+
+Run the Nomad job with the following command:
+
+```shell-session
+$ nomad run redis.nomad.hcl
+==> Monitoring evaluation "c3dc5ebd"
+    Evaluation triggered by job "redis"
+    Allocation "7a374183" created: node "5d16d949", group "cache1"
+    Allocation "f4361df1" created: node "7b381152", group "cache1"
+    Allocation "f7af42dc" created: node "5d16d949", group "cache1"
+    Allocation "0638edf2" created: node "10cc48cc", group "cache1"
+    Allocation "49bc6038" created: node "12894b80", group "cache1"
+    Allocation "c7e5679a" created: node "5d16d949", group "cache1"
+    Allocation "cf91bf65" created: node "7b381152", group "cache1"
+    Allocation "d16b606c" created: node "12894b80", group "cache1"
+    Allocation "27866df0" created: node "93f1e628", group "cache1"
+    Allocation "8531a6fc" created: node "7b381152", group "cache1"
+    Evaluation status changed: "pending" -> "complete"
+```
+
+Note that three of the ten allocations have been placed on node `5d16d949`. This
+is the node configured to be in datacenter `dc2`. The Nomad scheduler has
+distributed 30% of the workload to `dc2` as specified in the `spread` stanza.
+
+Keep in mind that the Nomad scheduler still factors in other components into the
+overall scoring of nodes when making placements, so you should not expect the
+spread stanza to strictly implement your distribution preferences like a
+[constraint][constraint-stanza]. Now, take a detailed look at the scoring in
+the next few steps.
+
+## Check the status of the job
+
+Check the status of the job and verify where allocations have been placed. Run
+the following command:
+
+```shell-session
+$ nomad status redis
+```
+
+The output should list ten running instances of your job in the `Summary`
+section as show below:
+
+```plaintext
+...
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache1      0       0         10       0       0         0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+0638edf2  10cc48cc  cache1      0        run      running  2m20s ago  2m ago
+27866df0  93f1e628  cache1      0        run      running  2m20s ago  1m57s ago
+49bc6038  12894b80  cache1      0        run      running  2m20s ago  1m58s ago
+7a374183  5d16d949  cache1      0        run      running  2m20s ago  2m1s ago
+8531a6fc  7b381152  cache1      0        run      running  2m20s ago  2m2s ago
+c7e5679a  5d16d949  cache1      0        run      running  2m20s ago  1m55s ago
+cf91bf65  7b381152  cache1      0        run      running  2m20s ago  1m57s ago
+d16b606c  12894b80  cache1      0        run      running  2m20s ago  2m1s ago
+f4361df1  7b381152  cache1      0        run      running  2m20s ago  2m3s ago
+f7af42dc  5d16d949  cache1      0        run      running  2m20s ago  1m54s ago
+```
+
+You can cross-check this output with the results of the `nomad node status`
+command to verify that 30% of your workload has been placed on the node in `dc2`
+(in our case, that node is `5d16d949`).
+
+## Obtain detailed scoring information on job placement
+
+The Nomad scheduler will not always spread your workload in the way you have
+specified in the `spread` stanza even if the resources are available. This is
+because spread scoring is factored in with other metrics as well before making a
+scheduling decision. In this step, you will take a look at some of those other
+factors.
+
+Using the output from the previous step, take any allocation that has been
+placed on a node and use the nomad [alloc status][alloc status] command with the
+[verbose][verbose] option to obtain detailed scoring information on it. In this
+example, the guide refers to allocation ID `0638edf2`—your allocation IDs will
+be different.
+
+```shell-session
+$ nomad alloc status -verbose 0638edf2
+```
+
+The resulting output will show the `Placement Metrics` section at the bottom.
+
+```plaintext
+...
+Placement Metrics
+Node                                  node-affinity  allocation-spread  binpack  job-anti-affinity  node-reschedule-penalty  final score
+10cc48cc-2913-af54-74d5-d7559f373ff2  0              0.429              0.33     0                  0                        0.379
+93f1e628-e509-b1ab-05b7-0944056f781d  0              0.429              0.515    -0.2               0                        0.248
+12894b80-4943-4d5c-5716-c626c6b99be3  0              0.429              0.515    -0.2               0                        0.248
+7b381152-3802-258b-4155-6d7dfb344dd4  0              0.429              0.515    -0.2               0                        0.248
+5d16d949-85aa-3fd3-b5f4-51094cbeb77a  0              0.333              0.515    -0.2               0                        0.216
+```
+
+Note that the results from the `allocation-spread`, `binpack`,
+`job-anti-affinity`, `node-reschedule-penalty`, and `node-affinity` columns are
+combined to produce the numbers listed in the `final score` column for each
+node. The Nomad scheduler uses the final score for each node in deciding where
+to make placements.
+
+## Next steps
+
+Change the values of the `percent` options on your targets in the `spread`
+stanza and observe how the placement behavior along with the final score given
+to each node changes (use the `nomad alloc status` command as shown in the
+previous step).
+
+### Reference material
+
+- The [spread][spread-stanza] stanza documentation
+- [Scheduling][scheduling] with Nomad
+
+[alloc status]: /nomad/commands/alloc/status
+[attributes]: /nomad/docs/reference/runtime-variable-interpolation
+[client-metadata]: /nomad/docs/configuration/client#meta
+[constraint-stanza]: /nomad/docs/job-specification/constraint
+[job-specification]: /nomad/docs/job-specification
+[node-status]: /nomad/commands/node/status
+[percent]: /nomad/docs/job-specification/spread#percent
+[repository]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[spread-stanza]: /nomad/docs/job-specification/spread
+[target]: /nomad/docs/job-specification/spread#target
+[verbose]: /nomad/commands/alloc/status#verbose
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/action.mdx b/content/nomad/v1.11.x/content/docs/job-specification/action.mdx
new file mode 100644
index 0000000000..ca2d99625c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/action.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: action block in the job specification
+description: |-
+  Configure custom commands in the `action` block of the Nomad job specification. Operators may execute these commands on a running allocation as a controlled way to interact with tasks. Review examples that use actions with arguments and templates.
+---
+
+# `action` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'action']} />
+
+The `action` block allows job authors to define custom commands. These commands
+can be executed by operators with the necessary permissions on a running
+allocation, offering a controlled way to interact with tasks.
+
+The name of the action can contain alphanumeric characters and dashes. This
+name must be unique within its task and must not exceed 128 characters.
+
+## `action` Parameters
+
+- `command` `(string: <required>)` - Specifies the command to be executed.
+- `args` `(array<string>: [])` - Provides a list of arguments to pass to the command.
+
+```hcl
+job "my-job" {
+  group "my-group" {
+    task "my-task" {
+      action "get-changelog" {
+        command = "/usr/bin/curl"
+        args = [
+          "-s",
+          "https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md"
+        ]
+      }
+      # ...
+    }
+  }
+}
+```
+
+## `action` Examples
+
+### Basic Action
+This example demonstrates a simple action that prints the current date and time:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "show-date" {
+      # ...
+      action "current-date" {
+        command = "/bin/date"
+      }
+    }
+  }
+}
+```
+
+### Action with Arguments
+Here, an action uses arguments to perform a specific task:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "list-files" {
+      # ...
+      action "list-tmp" {
+        command = "/bin/ls"
+        args    = ["-l", "/tmp"]
+      }
+    }
+  }
+}
+```
+
+### Action with Template
+This advanced example demonstrates an action that fetches and formats the latest
+changelog from the Nomad GitHub repository using a shell script. It showcases
+the use of templating with embedded environment variables and a multi-line script.
+
+```hcl
+action "fetch-latest-nomad-changelog" {
+  command = "/bin/sh"
+  args    = ["-c",
+    <<EOT
+curl -s https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md |
+
+awk 'BEGIN{
+    # Setting record and field separators
+    RS="## "; FS="\n";
+    section=""; count=0
+}
+{
+    # Processing only the first 3 sections after the header
+    if (count < 3 && NR > 1){
+        # Splitting the version line into components
+        split($1, versionInfo, /[()]/);
+        version=versionInfo[1];
+        gsub(" ", "", version); # Removing spaces from version
+        releaseDate=versionInfo[2];
+        # Formatting URL components
+        urlVersion=version; gsub("\\.", "", urlVersion); # Remove dots from version
+        urlDate=releaseDate; gsub(" ", "-", urlDate); gsub(",", "", urlDate); # Replace spaces with hyphens and remove comma
+        # Counting items under each section
+        for(i=1; i<=NF; i++){
+            if($i ~ /^[A-Z ]+:$/){
+                gsub(":", "", $i);
+                section=$i;
+                itemCount[section]=0;
+            }
+            if(section && $i ~ /^\*/){
+                itemCount[section]++;
+            }
+        }
+        # Printing the extracted information
+        printf "Version: %s\nRelease Date: %s\n", version, releaseDate;
+        for (s in itemCount) {
+            printf "%d %s, ", itemCount[s], s;
+        }
+        printf "\nLink: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md#%s-%s\n\n", urlVersion, tolower(urlDate);
+        delete itemCount;  # Clear the itemCount array for the next version
+        count++;
+    }
+}'
+    EOT
+  ]
+}
+```
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.11.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..6e0c81e4c7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,280 @@
+---
+layout: docs
+page_title: affinity block in the job specification
+description: |-
+  Express placement preference for a set of nodes in the `affinity` block of the Nomad job specification. Configure attribute, comparison operator, comparison value, and a scoring weight. Review kernal data, operating system, and metadata examples.
+---
+
+# `affinity` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+Updating the `affinity` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: <required>)` - Specifies the value to compare the attribute
+  against using the specified operation. This can be a literal value, another
+  attribute, or any [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+  The `value` field is required.
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Metadata
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+## Placement details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors:
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
+
+
+[job]: /nomad/docs/job-specification/job
+[group]: /nomad/docs/job-specification/group
+[client-meta]: /nomad/docs/configuration/client#meta
+[task]: /nomad/docs/job-specification/task
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables
+[constraint]: /nomad/docs/job-specification/constraint
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.11.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..211e600ca8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,288 @@
+---
+layout: docs
+page_title: artifact block in the job specification
+description: |-
+  Configure fetching a remote resource in the `artifact` block of the Nomad job specification. Set the artifact destination, the source URL, HTTP headers, fetch options, mode, and whether Nomad should recursively chown the downloaded artifact. Review examples for downloading a file, fetching from a Git repository, unarchiving, verifying checksums, and downloading from an AWS S3-compatible bucket.
+---
+
+# `artifact` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+- `chown` `(bool: false)` - Specifies whether Nomad should recursively `chown`
+  the downloaded artifact to be owned by the [`task.user`][task_user] uid and
+  gid.
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment
+variables set for the Nomad client. Manage inheritance of environment variables
+with the [`artifact.set_environment_variables`][client_artifact] client
+configuration.
+
+## Operation limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download file
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/reference/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and verify checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. Non-Amazon S3-compatible endpoints like [Minio]
+are supported, but you must explicitly set the "s3::" prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[task_user]: /nomad/docs/job-specification/task#user
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.11.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..f7969dd9e4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: change_script block in the job specification
+description: |-
+  Configure template change scripts in the `change_script` block of the Nomad job specification. Nomad executes these scripts when a template changes. Configure the command, arguments, and timeout. Enable fail on error. Review an example of how to embed a script in the data block of a template block.
+---
+
+# `change_script` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/check.mdx b/content/nomad/v1.11.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..c2ad40cdc0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,500 @@
+---
+layout: docs
+page_title: check block in the job specification
+description: |-
+  Configure Nomad to register a service health check in the `check` block of the Nomad job specification. Set the command to use, health check interval, and network values. Configure success and failure behavior. Review HTTP, gRPC, and scripted health checks.
+---
+
+# `check` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `address_mode` `(string: "host")` - Specifies which address (host, alloc,
+  alloc IPv6 or driver-specific) this service should use to make checks, similar
+  to `address_mode` on `service`. When the service uses the Consul provider,
+  Consul needs access to the address for any HTTP or TCP checks. Unlike `port`,
+  this setting is **not** inherited from the `service`. If the service `address`
+  is set, the service `address_mode` is `"auto"`, and the check `address_mode`
+  is not set, Nomad uses the service `address` value for the check address.
+
+  Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address
+     mode uses the IP address inside the namespace. Use only with "bridge" and
+    "cni" [networking modes][network_mode]. You may specify a numeric port for
+    situations where no port mapping is necessary. Set this mode only for checks
+    which are defined in a "group" service block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of
+    dual-stack or IPv6-only.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. You may specify a numeric port since port maps aren't required by
+    all network plugins. Useful for checking SDN and overlay network addresses.
+    Task fails if driver network cannot be determined. Only implemented for
+    Docker. Set this mode only for checks which are defined in a "task" service
+    block. Refer to [Using driver address
+    mode](/nomad/docs/job-specification/service#using-driver-address-mode) for
+    an example of use.
+
+  - `host` - Use the host IP and the exposed port.
+
+  Note there is no `"auto"` mode for checks, unlike services.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_success_before_passing].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_failure_before_critical].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_warning` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`warning`][consul_failure_before_warning].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. Numeric ports may be used if `address_mode="driver"` is set
+  on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider.
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+### `header` block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+## Examples
+
+### HTTP health check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple health checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC health check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block.
+
+### Script checks with shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus readiness checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+## Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_success_before_passing]: /consul/api-docs/agent/check#successbeforepassing
+[consul_failure_before_critical]: /consul/api-docs/agent/check#failuresbeforecritical
+[consul_failure_before_warning]: /consul/api-docs/agent/check#failuresbeforewarning
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
+[network_mode]: /nomad/docs/job-specification/network#mode
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.11.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..3af1a84c9d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: check_restart block in the job specification
+description: |-
+  Configure Nomad to restart tasks with unhealthy service checks in the `check_restart` block of the Nomad job specification. Set the grace period and health check failure limit. Enable ignore warnings. Review an example and how Nomad behaves based on that example.
+---
+
+# `check_restart` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/check
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart
+[service_block]: /nomad/docs/job-specification/service
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.11.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..aed3df6b81
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: connect block in the job specification
+description: |-
+  Configure the `connect` block of the Nomad job specification for Consul service mesh native application integration. Configure sidecar service, sidecar task, and gateway.
+---
+
+# `connect` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+Use the `connect` block to configure various options for Consul service mesh
+(formerly Consul Connect). The `connect` block is valid only within the context
+of a service definition at the task group level.
+
+Refer to the following resources for details on using Consul service mesh with Nomad:
+
+- The [Consul service mesh](/nomad/docs/networking/consul/service-mesh) overview
+  for an introduction and how to configure Consul service mesh in your job.
+- [Secure Nomad jobs with Consul service
+  mesh](/nomad/tutorials/integrate-consul/consul-service-mesh) for using
+  `connect` when Consul ACLs are enabled.
+
+All the examples on this page assume Consul and Nomad are in the same
+datacenter.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as
+  supporting [Consul service mesh native][consul-service-mesh-native]
+  applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul service mesh.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul service mesh.
+
+## Examples
+
+### Using Consul service mesh native
+
+The following example is a minimal service block for a
+[Consul service mesh native][consul-service-mesh-native]
+application implemented by a task named `generate`. Make sure to include the
+[service `name`](/nomad/docs/job-specification/service#name) and [service
+`port`](/nomad/docs/job-specification/service##port) fields so that Consul
+advertizes the service with your desired values.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using sidecar service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul service mesh.  Make sure to include the
+[service `name`](/nomad/docs/job-specification/service#name) and [service
+`port`](/nomad/docs/job-specification/service##port) fields so that Consul
+advertizes the service with your desired values.
+
+```hcl
+service {
+  name = "count-api"
+  port = "9001"
+
+  connect {
+    sidecar_service {}
+  }
+}
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+service {
+  name = "count-api"
+  port = "9001"
+
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+}
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a gateway
+
+The following is an example service block for creating and using a Consul
+service mesh ingress
+gateway. It includes a gateway service definition and an API service fronted by
+the gateway. Once running, the gateway can be used to reach the API service by first
+looking up the gateway Consul DNS address with `curl`.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+
+
+[gateway]: /nomad/docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /nomad/docs/job-specification/group
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[job]: /nomad/docs/job-specification/job
+[service_task]: /nomad/docs/job-specification/service#task-1
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[task]: /nomad/docs/job-specification/task
+[upstreams]: /nomad/docs/job-specification/upstreams
+[consul-service-mesh-native]: /consul/docs/automate/native
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.11.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..4a9ceb184c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: constraint block in the job specification
+description: |-
+  Restrict the set of eligible nodes in the `constraint` block of the Nomad job specification. Configure attribute, comparison operator,and comparison value. Review kernal data, distinct property, operating system, and metadata examples.
+---
+
+# `constraint` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+Updating the `constraint` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars). The
+  value field is required except for when using the `is_set`, `is_not_set`,
+  `distinct_hosts`, or `distinct_property` operators.
+
+### `operator` values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/consul.mdx b/content/nomad/v1.11.x/content/docs/job-specification/consul.mdx
new file mode 100644
index 0000000000..2279e0bace
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/consul.mdx
@@ -0,0 +1,296 @@
+---
+layout: docs
+page_title: consul block in the job specification
+description: |-
+  Configure Consul options in the `consul` block of the Nomad job specification to register them in the Consul catalog. Specify that the group or task requires a Consul token. Configure the Consul cluster, namespace, and partition. Review template, group services, namespace, and admin partition examples.
+
+---
+
+# `consul` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'consul'],
+    ['job', 'group', 'task', 'consul'],
+  ]}
+/>
+
+The `consul` block specifies [Consul][] configuration options specific to a
+task. If specified at the `group` level, the configuration will apply to all
+tasks and services within the group unless a task has its own `consul` block. A
+task-level `consul` block will entirely override a group-level `consul` block.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      consul {
+        cluster   = "default"
+        namespace = "default"
+        partition = "default"
+      }
+    }
+  }
+}
+```
+
+## Workload identity
+
+Starting in Nomad 1.7, Nomad clients will use a task or service's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+service or task when the following conditions are met:
+
+* For services, if either the [`consul.service_identity`][] is configured on the
+  Nomad servers or the service includes an `identity` block.
+* For tasks, if the [`consul.task_identity`][] is configured on the Nomad
+  servers, or the task includes an [`identity`][] block with the `name` field
+  set to `consul_default` (or `consul_$clusterName` for non-default Consul
+  clusters in Nomad Enterprise).
+
+As a fallback if none of these conditions are met, the Nomad client will instead
+use, in order of preference:
+
+* The Consul token as configured in the agent's [`consul.token`][] configuration.
+* The Consul token as configured by the agent's `CONSUL_HTTP_TOKEN` environment variable.
+
+To avoid failed deployments, you should first set up an authentication method
+and binding rules in Consul before configuring the Nomad servers with
+`consul.task_identity` and `consul.service_identity`. Refer to [Configuring Consul
+Authentication][] for more details.
+
+<Warning>
+
+Starting in Nomad 1.10, the fallback options to use the -consul-token flag when
+submitting a job, the agent's consul.token configuration, or the
+CONSUL_HTTP_TOKEN environment variable, will be removed.  This means service and
+template blocks will not be able to use the agent's Consul token or one provided
+by the job submitter. You should be prepared to migrate to the Workload Identity
+workflow for Consul and Vault before upgrading to Nomad 1.10. Refer to
+[Migrating to Using Workload Identity with Consul] for more information.
+
+</Warning>
+
+### Access to token
+
+The Nomad client will make the Consul token available to the task by writing it
+to the secret directory at `secrets/consul_token` and by injecting a
+`CONSUL_TOKEN` environment variable in the task.
+
+If the Nomad cluster is [configured][config_consul_namespace] to use [Consul Namespaces][], a
+`CONSUL_NAMESPACE` environment variable will be injected whenever `CONSUL_TOKEN`
+is set.
+
+The [`template`][template] block can use the Consul token as well.
+
+### Parameters
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use. The Nomad client will retrieve a Consul token from the
+  cluster configured in the agent configuration with the same
+  [`consul.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in
+  which group and task-level services within the group will be registered. Use
+  of `template` to access Consul KV will read from the specified Consul
+  namespace.  Specifying `namespace` takes precedence over the
+  [`-consul-namespace`][flag_consul_namespace] command line argument in `job
+  run`. In Nomad Community Edition, this field is ignored.
+
+- `partition` `(string: "")` - When this field is set, a constraint will be
+  added to the group or task to ensure that the allocation is placed on a Nomad
+  client that has a Consul Enterprise agent in the specified Consul [admin
+  partition][]. Using this field requires the following:
+
+  - [Consul Enterprise]
+  - Workload identity integration. The `partition` field does not work
+    with a legacy Consul token. Refer to [Nomad Workload Identities] for more
+    information on integrating Nomad's workload identity with Consul authentication.
+
+## Examples
+
+The following examples only show the `consul` blocks or other relevant
+blocks. Remember that the `consul` block is only valid in the placements listed
+above.
+
+### Consul token for templates
+
+This example tells the Nomad client to obtain a Consul token using the task's
+Workload Identity. The token is available to the task via the canonical
+environment variable `CONSUL_TOKEN` and written to disk at
+`secrets/consul_token`. The `template` block will use the same Consul
+token. Note that the `identity.name` is set to `"consul_default"`, which tells
+the Nomad client to use this identity when making requests to the default Consul
+cluster.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      identity {
+        name = "consul_default"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.task_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted in this case.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Consul token for group services
+
+This example tells the Nomad client to obtain a Consul Service Identity token
+using the service's Workload Identity. The Consul token will be used to register
+the service with Consul and configure any [Connect][] sidecar tasks for that
+service.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+      identity {}
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.service_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted for the service in this case.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+    }
+  }
+}
+```
+
+### Consul namespace <EnterpriseAlert product="nomad" inline />
+
+This example shows specifying a particular Consul namespace or Consul cluster
+for different tasks within a group.
+
+The `template` block in the `web` task will use the default Consul cluster, and
+will obtain a token that allows it access to the `engineering/frontend` Consul
+namespace. The `template` block in the `app` task will use the Consul cluster
+named `prod-apps`, and will obtain a token that allows it access to the
+`engineering/apps` Consul namespace.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "web" {
+
+      consul {
+        namespace = "engineering/frontend"
+      }
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      consul {
+        namespace = "engineering/apps"
+        cluster   = "prod-apps"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+### Consul admin partition <EnterpriseAlert product="nomad" inline />
+
+This example demonstrates how to configure Consul admin partitions for different
+tasks within a group. The Consul client agent must separately specify the admin
+partition in the agent configuration. Refer to the Consul documentation's
+[agent configuration reference][] for more information.
+
+In the following example, the `web` and `app` tasks use the default Consul cluster
+and obtain a token that allows access to the `prod` admin partition in Consul. The
+Consul configuration occurs at the `group` level because tasks are placed together
+on the same Allocation. If you configure tasks with separate `consul` blocks, the
+`partition` field must be the same in both blocks.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    consul {
+      cluster   = "default"
+      namespace = "default"
+      partition = "prod"
+    }
+
+    task "web" {
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`identity`]: /nomad/docs/job-specification/identity
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.token`]: /nomad/docs/configuration/consul#token
+[Configuring Consul Authentication]: /nomad/docs/secure/acl/consul#configuring-consul-authentication
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/secure/acl/consul#migrating-to-using-workload-identity-with-consul
+[config_consul_namespace]: /nomad/docs/configuration/consul#namespace
+[Consul Namespaces]: /consul/docs/enterprise/namespaces
+[Consul Admin Partitions]: /consul/docs/enterprise/admin-partitions
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[flag_consul_namespace]: /nomad/commands/job/run#consul-namespace
+[Connect]: /nomad/docs/job-specification/connect
+[admin partition]: /consul/docs/enterprise/admin-partitions
+[agent configuration reference]: /consul/docs/agent/config/config-files#partition-1
+[Consul Enterprise]: /consul/docs/enterprise
+[Nomad Workload Identities]: /nomad/docs/secure/acl/consul#nomad-workload-identities
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.11.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..3c04405496
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: csi_plugin block in the job specification
+description: >-
+  Specify that the task provides a Container Storage Interface plugin to the cluster in the `csi_plugin` block of the Nomad job specification. Configure plugin ID, type, mount directory, stage publish base directory, and health timeout. Review recommendations for deploying CSI plugins.
+---
+
+# `csi_plugin` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for deploying CSI plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/concepts/scheduling/schedulers#system
+[`topology_request`]: /nomad/commands/volume/create#topology_request
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/device.mdx b/content/nomad/v1.11.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..3b6a5cc9fb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,328 @@
+---
+layout: docs
+page_title: device block in the job specification
+description: |-
+  Configure task access to devices in the `device` block of the Nomad job specification.
+---
+
+# `device` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/plugins/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/disconnect.mdx b/content/nomad/v1.11.x/content/docs/job-specification/disconnect.mdx
new file mode 100644
index 0000000000..29c6b36ac2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/disconnect.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: disconnect block in the job specification
+description: |-
+  Describe system behavior for disconnected allocations in the `disconnect` block of the Nomad job specification. Specify whether Nomad should replace a disconnected allocation. Configure node reconciliation behavior. Set a duration for Nomad to attempt allocation reconnection and a duration after which a disconnected Nomad client stops its allocations. Review examples for stop after and lost after configuration.
+---
+
+# `disconnect` block in the job specification
+
+<Placement groups={['job', 'group', 'disconnect']} />
+
+The `disconnect` block describes the system's behavior in case of a network
+partition. By default, without a `disconnect` block, if an allocation is on a
+node that misses heartbeats, the allocation will be marked `lost` and will be
+replaced.
+
+Replacement happens when a node is lost. When a node is drained, Nomad
+[migrates][] the allocations instead, and Nomad ignores the `disconnect`
+block. When a Nomad agent fails to set up the allocation or the tasks of an
+allocation fail more than their [`restart`][] block allows, Nomad
+[reschedules][] the allocations and ignores the `disconnect`.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    disconnect {
+      lost_after = "6h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+
+  group "example2" {
+    disconnect {
+      stop_on_client_after = "12h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+}
+```
+
+~> Note that you cannot use both`lost_after` and `stop_on_client_after` in the
+same `disconnect` block.
+
+## Parameters
+
+- `lost_after` `(string: "")` - Specifies a duration during which a Nomad client
+  will attempt to reconnect allocations after it fails to heartbeat in the
+  [`heartbeat_grace`][] window.  It defaults to "", which is equivalent to
+  having the disconnect block be nil.
+
+  You cannot use `lost_after` and `stop_on_client_after` in the same
+  `disconnect` block.
+
+  Refer to [the Lost After section][lost-after] for more details.
+
+- `replace` `(bool: true)` - Specifies if Nomad should replace the disconnected
+  allocation with a new one rescheduled on a different node. Nomad considers the
+  replacement allocation a reschedule and obeys the job's [`reschedule`][]
+  block. If false and the node the allocation is running on disconnects
+  or goes down, Nomad does not replace this allocation and reports `unknown`
+  until the node reconnects, or until you manually stop the allocation.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  If true, a new alloc will be placed immediately upon the node becoming
+  disconnected.
+
+- `stop_on_client_after` `(string: "")` - Specifies a duration after which a
+  disconnected Nomad client will stop its allocations. Setting
+  `stop_on_client_after` shorter than `lost_after` and `replace = false` at the
+  same time is not permitted and will cause a validation error, because this
+  would lead to a state where no allocations can be scheduled.
+
+  The Nomad client process must be running for this to occur.
+
+  You cannot use `stop_on_client_after` and `lost_after` in the same
+  `disconnect` block.
+
+  Refer to [the Stop After section][stop-after] for more details.
+
+- `reconcile` `(string: "best_score")` - Specifies which allocation to keep once
+  the previously disconnected node regains connectivity.
+  It has four possible values which are described below:
+
+    - `keep_original`: Always keep the original allocation. Bear in mind
+    when choosing this option, it can have crashed while the client was
+    disconnected.
+    - `keep_replacement`: Always keep the allocation that was replaced
+    to replace the disconnected one.
+    - `best_score`: Keep the allocation running on the node with the best
+    score.
+    - `longest_running`: Keep the allocation that has been up and running
+    continuously for the longest time.
+
+
+## Examples
+
+The following examples only show the `disconnect` blocks. Remember that the
+`disconnect` block is only valid in the placements listed previously.
+
+### Stop After
+
+This example shows how `stop_on_client_after` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server replaces the allocation. The client waits 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_on_client_after`, so the server replaces the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may replace the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  disconnect {
+    stop_on_client_after = "90s"
+  }
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Lost After
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `lost_after` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost".
+These allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' `replace` settings
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements will
+decide which ones to keep according to the `reconcile` setting.
+If the `lost_after` duration expires before the client reconnects,
+the allocations will be marked "lost". Clients that contain "unknown"
+allocations will transition to "disconnected" rather than "down" until the last
+`lost_after` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `lost_after`
+is twelve hours. Once all groups' `lost_after` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+using the strategy defined by [`reconcile`].
+
+Lost After is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with `stop_on_client_after`.
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "best_score"
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "keep_original"
+  }
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[stop-after]: /nomad/docs/job-specification/disconnect#stop-after
+[lost-after]: /nomad/docs/job-specification/disconnect#lost-after
+[`reconcile`]: /nomad/docs/job-specification/disconnect#reconcile
+[migrates]: /nomad/docs/job-specification/migrate
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.11.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..240a89804b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload block in the job specification
+description: |-
+  Configure a parameterized job task payload in the `dispatch_payload` block of the Nomad job specification.
+---
+
+# `dispatch_payload` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/reference/runtime-environment-settings#local
+[parameterized]: /nomad/docs/job-specification/parameterized
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/env.mdx b/content/nomad/v1.11.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..d60a9874f2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: env block in the job specification
+description: |-
+  Configure environment variables in the `env` block of the Nomad job specification.
+---
+
+# `env` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic environment variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.11.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..49a40db622
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: ephemeral_disk block in the job specification
+description: |-
+  Describe a group's ephemeral disk requirements in the `ephemeral_disk` block of the Nomad job specification. Turn on data migration and allocation placement. Specify disk size.
+---
+
+# `ephemeral_disk` block in the job specification
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.11.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..804f1625b5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,237 @@
+---
+layout: docs
+page_title: expose block in the job specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul service mesh integration
+---
+
+# `expose` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul service mesh][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of Envoy expose path configurations
+  to expose through Envoy.
+
+### `path` parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## Examples
+
+The following example exposes the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+The following example exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+## Exposing service checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/check#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters
+[port]: /nomad/docs/job-specification/network#port-parameters
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate/consul/service-mesh
+[check]: /nomad/docs/job-specification/service#check
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.11.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..d269efb676
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,744 @@
+---
+layout: docs
+page_title: gateway block in the job specification
+description: |-
+  Configure a Consul mesh, ingress, or terminating gateway in the `gateway` block of the Nomad job specification.
+---
+
+# `gateway` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul service mesh gateways](/consul/docs/connect/gateways). Nomad will automatically create the
+necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries) as
+well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making
+  upstream connections before timing out. Defaults to 5 seconds. If the upstream
+  service has the configuration option <code>[connect_timeout_ms]</code> set for
+  the `service-resolver`, that timeout value will take precedence over this
+  gateway proxy option.
+
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the
+  gateway services tagged addresses should be bound to listeners in addition to
+  the default listener address.
+
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A
+  map of additional addresses to be bound.  The keys to this map are the same of
+  the listeners to be created and the values are a map with two keys - address
+  and port, that combined make the address to bind the listener to. These are
+  bound in addition to the default address.  If `bridge` networking is in use,
+  this map is automatically populated with additional listeners enabling the
+  Envoy proxy to work from inside the network namespace.
+
+  ```hcl
+  envoy_gateway_bind_addresses "<service>" {
+    address = "0.0.0.0"
+    port    = <port>
+  }
+  ```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy
+  Documentation][envoy_sd_docs].  This option applies to terminating gateways
+  that route to services addressed by a hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` parameters
+
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners
+  that the ingress gateway should setup, uniquely identified by their port
+  number.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+
+#### `listener` parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or
+  `grpc`), preconfiguring a [service-default][] in Consul to set the
+  [Protocol][service-default-protocol] of the service to the desired protocol is
+  mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[listener-service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### Listener `service` parameters
+
+The `service` blocks for a listener under an `ingress` gateway accept the
+following parameters. Note these are different than the `service` blocks under a
+`terminating` gateway.
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+- `request_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to requests routed to this
+  service. This cannot be used with a tcp listener.
+
+- `response_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to responses from this
+  service. This cannot be used with a tcp listener.
+
+- `max_concurrent_requests` `(int: <optional>)` - Specifies the maximum number
+  of concurrent HTTP/2 traffic requests that are allowed at a single point in
+  time. If unset, will default to the Envoy proxy's default.
+
+- `max_connections` `(int: <optional>)` - Specifies the maximum number of
+  HTTP/1.1 connections a service instance is allowed to establish against the
+  upstream. If unset, will default to the Envoy proxy's default.
+
+- `max_pending_requests` `(int: <optional>)` - Specifies the maximum number of
+  requests that are allowed to queue while waiting to establish a connection.
+  If unset, will default to the Envoy proxy's default.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this service.
+
+#### Header modifier parameters
+
+The `request_headers` and `response_headers` blocks of an `ingress.service`
+block accept the following parameters. For more details, see the [Consul
+documentation][response-headers].
+
+- `add` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  headers, where header names are keys and header values are the values. Header
+  names are not case-sensitive. If header values with the same name already
+  exist, the value is appended and Consul applies both headers.
+
+- `set` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  response header or to replace existing header values with. Use header names as
+  the keys. Header names are not case-sensitive. If header values with the same
+  names already exist, Consul replaces the header values.
+
+- `remove` `array(string): optional` - Defines a list of headers to remove. Consul
+  removes only headers containing exact matches. Header names are not
+  case-sensitive.
+
+#### `tls` parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every
+  listener on the gateway. If TLS is enabled, then each host defined in the
+  `host` field will be added as a DNSSAN to the gateway's x509 certificate.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+- `sds` `(block: optional)` - Defines a set of parameters that configures the
+  listener to load TLS certificates from an external Secret Discovery Service
+  ([SDS][]).
+
+  - `cluster_name` `(string)` - The SDS cluster name to connect to to retrieve
+    certificates.
+
+  - `cert_resource` `(string)` - The SDS resource name to request when fetching
+    the certificate from the SDS service.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+### `terminating` parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### linked `service` parameters
+
+The `service` blocks for a `terminating` gateway accept the following
+parameters. Note these are different than the `service` blocks for listeners
+under an `ingress` gateway.
+
+- `name` `(string: required)` - The name of the service to link with the
+  gateway. If the wildcard specifier `*` is provided, then ALL services within
+  the Consul namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate
+  authority is used to verify the authenticity of the service linked with the
+  gateway. It can be provided along with a `cert_file` and `key_file` for mutual
+  TLS authentication, or on its own for one-way TLS authentication. If none is
+  provided the gateway **will not** encrypt traffic to the destination.
+
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided
+  to servers to verify the gateway's authenticity. It must be provided if a
+  `key_file` is provided.
+
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the
+  certificate to verify the gateway's authenticity. It must be provided if a
+  `cert_file` is provided.
+
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify
+  during the TLS handshake.
+
+### `mesh` parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+## Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+## Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```hcl
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+## Examples
+
+### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul service mesh
+  # . It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#linked-service-parameters
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[listener-service]: /nomad/docs/job-specification/gateway#listener-service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
+[envoy_sd_docs]: https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery
+[SDS]: https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#listeners-services-tls-sds
+[service-default-protocol]: /consul/docs/connect/config-entries/service-defaults#protocol
+[response-headers]: /consul/docs/connect/config-entries/ingress-gateway#listeners-services-responseheaders
+[header modifiers]: /nomad/docs/job-specification/gateway#header-modifier-parameters
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/group.mdx b/content/nomad/v1.11.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..77879a0bae
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: group block in the job specification
+description: |-
+  Define a series of co-located tasks in the `group` block of the Nomad job specification. Specify constraints, affinities, spreads, number of instances, Consul settings, ephemeral disks, disconnect strategy, metadata, migration strategy, network requirements, rescheduling strategy, restart policy, service discovery, shutdown delay, task update strategy, Vault policies, and required volumes. Review count, constraints, metadata, network, and service discovery examples.
+---
+
+# `group` block in the job specification
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group. These options will be applied to all tasks and
+  services in the group unless a task has its own `consul` block.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `disconnect` <code>([disconnect][]: nil)</code> - Specifies the disconnect
+  strategy for the server and client for all tasks in this group in case of a
+  network partition. The tasks can be left unconnected, stopped or replaced
+  when the client disconnects. The policy for reconciliation in case the client
+  regains connectivity is also specified here.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/consul
+[consul_namespace]: /nomad/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`disable_rescheduling`]: /nomad/docs/job-specification/reschedule#disabling-rescheduling
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[disconnect]: /nomad/docs/job-specification/disconnect 'Nomad disconnect Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[disconect_migration]: /nomad/docs/job-specification/group#migration_to_disconnect_block
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.11.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..c339f647af
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,368 @@
+---
+layout: docs
+page_title: identity block in the job specification
+description: |-
+  Configure workload identity in the `identity` block of the Nomad job specification. Review how to configure workload identities for Consul and Vault.
+---
+
+# `identity` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'identity'],
+    ['job', 'group', 'task', 'identity'],
+    ['job', 'group', 'task', 'service', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. Nomad will create a _default_ identity for all
+workloads, but it is *not* exposed to a task. You may also set additional
+identities intended for use with external applications such as Vault, Consul, or
+OIDC authentication.
+
+For example, the following will expose the default Workload Identity as an
+environment variable and file to the task, and a second Workload Identity
+configured for a third-party OIDC provider:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env         = true
+        file        = true
+        filepath    = "local/example.jwt"
+
+        # Restart on token renewal to get the new env var
+        change_mode = "restart"
+      }
+
+      identity {
+        name        = "example"
+        aud         = ["oidc.example.com"]
+        file        = true
+        ttl         = "1h"
+
+        # Send a HUP signal when the token file is updated
+        change_mode   = "signal"
+        change_signal = "SIGHUP"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+- `name` `(string: "default")` - The name of the workload identity, which must
+  be unique per task. Only one `identity` block in a task can omit the `name`
+  field.
+- `aud` `([]string: nil)` - The audience field for the workload identity. This
+  should always be set for non-default identities.
+- `change_mode` `(string: "noop")` - Specifies the behavior Nomad should take when the token changes.
+
+  - `"noop"` - take no action. The default since tasks may choose to reload
+      tokens only when their current token gets rejected or implement their own
+      change detection.
+  - `"restart"` - restart the task.
+  - `"signal"` - send a configurable signal to the task. Must set `change_signal`.
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGHUP"` or `"SIGUSR1"`. This option is required if the
+  `change_mode` is `signal`.
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+- `filepath` `(string: "")` - If not empty and file is `true`, the workload
+  identity is available at the specified location relative to the
+  [task working directory][] instead of the `NOMAD_SECRETS_DIR`.
+- `ttl` `(string: "")` - The lifetime of the identity before it expires. The
+  client will renew the identity at roughly half the TTL. This is specified
+  using a label suffix like "30s" or "1h". You may not set a TTL on the default
+  identity. You should always set a TTL for non-default identities.
+
+## Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload identities for Consul
+
+Jobs that need access to Consul can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task or service that will access Consul.
+
+You can configure Nomad servers to automatically add default identities for
+Consul using the [`consul.service_identity`][] and [`consul.task_identity`][]
+agent configuration. Upon job registration, the Nomad server updates tasks that
+have a [`consul`][] block and services that use the Consul service provider to
+include the default identities.
+
+Job specifications that include [`template`][] blocks are not provided with
+default identities because Nomad is unable to decipher the contents of the
+template data. You must specify the identities required for Consul in the job
+specification.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identities configured in the Nomad servers. Identities for
+tasks must have a [`name`](#name) that follows the pattern
+`consul_<cluster name>`. Identities for services do not need to specify a
+`name`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the task
+identity name should be `consul_default`.
+
+<Warning>
+
+Nomad Enterprise supports multiple Consul clusters. The value of
+`cluster_name` must be the same as the task's [`consul.cluster` parameter value](/nomad/docs/job-specification/consul#cluster).
+
+</Warning>
+
+Refer to [Nomad workload identities][int_consul_wid] section of the Consul
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="3,14-17,30-34">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {}
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_default"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="3-5,16-19,32-36">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {
+      cluster = "prod"
+    }
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_prod"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Workload identities for Vault
+
+Jobs that need access to Vault can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task that will access Vault.
+
+You can configure Nomad servers to automatically add default identities for
+Vault using the [`vault.default_identity`][] agent configuration. Upon job
+registration, the Nomad server updates tasks that have a [`vault`][] block to
+include the default identity.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identity configured in the Nomad servers. The identity
+[`name`](#name) must follow the pattern `vault_<cluster name>`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the
+identity name should be `vault_default`.
+
+<Warning>
+
+Nomad Enterprise supports multiple Vault clusters. The cluster name
+must be the same as the task's [`vault.cluster` parameter value](/nomad/docs/job-specification/vault#cluster).
+
+</Warning>
+
+Refer to [Nomad Workload Identities][int_vault_wid] section of the Vault
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="19,21-25">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      identity {
+        name = "vault_default"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="19-21,23-27">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {
+        cluster = "prod"
+      }
+
+      identity {
+        name = "vault_prod"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`template`]: /nomad/docs/job-specification/template
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault`]: /nomad/docs/job-specification/vault
+[int_consul_wid]: /nomad/docs/secure/acl/consul
+[int_vault_wid]: /nomad/docs/secure/vault/acl
+[taskapi]: /nomad/api-docs/task-api
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/index.mdx b/content/nomad/v1.11.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..f69eec4619
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,153 @@
+---
+layout: docs
+page_title: Nomad job specification
+description: |-
+  This section contains reference information for configuring a Nomad job with HCL. Learn what a job specification is and its format. Review an example job specification.
+---
+
+# Nomad job specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+The `service` block can also be specified at the group level. This allows job specification authors
+to create and register services with Consul Service Mesh. A service block specified at the group
+level must include a [`connect`][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/job.mdx b/content/nomad/v1.11.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..644ca45f65
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: job block in the job specification
+description: |-
+  Define your workload in the `job` block of the Nomad job specification. Specify constraints, affinities, spreads, datacenter, node pool, group, metadata, job name, node migration strategy, namespace, priority, region, rescheduling strategy, job type, task update strategy, and Vault policies.
+  Configure parameterized and periodic jobs. Review examples that use Docker, batch jobs, and secrets.
+---
+
+# `job` block in the job specification
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+
+    task "docs" {
+      # ...
+    }
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  update {
+    # ...
+  }
+}
+```
+
+## Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul service mesh enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/docs/govern/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: //nomad/docs/deploy/clusters/federate-regions
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/concepts/scheduling/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.11.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..9828f9c1ab
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: lifecycle block in the job specification
+description: |-
+  Configure when Nomad runs a task in the `lifecycle` block of the Nomad job configuration. Specify a lifecycle hook of prestart, poststart, or poststop. Define a task as ephemeral or as a long-lived sidecar. Review examples of initialization, cleanup, and auxiliary tasks.
+---
+
+# `lifecycle` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+The `lifecycle` block also controls the order Nomad stops tasks in an
+allocation. Nomad first waits for the group's [shutdown_delay][]. It then stops
+the [leader][] task, if present. Then Nomad stops any non-sidecar and
+non-poststop tasks, and finally any sidecar tasks.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/docs/job-declare/task-dependencies
+[shutdown_delay]: /nomad/docs/job-specification/group#shutdown_delay
+[leader]: /nomad/docs/job-specification/task#leader
+
+## Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init task pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion sidecar pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup task pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.11.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..8640b38629
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: logs block in the job specification
+description: |-
+  Configure a task's log rotation policy in the `logs` block of the Nomad job specification. Set the maximum number of rotated files and the maximum size of each rotated file. Turn off log collection for a task. Review default log rotation values.
+---
+
+# `logs` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/deploy/task-driver/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.11.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..159bbccb56
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: meta block in the job specification
+description: |-
+  Define arbitrary metadata in the `meta` block of the Nomad job specification. Configure runtime environment variables for tasks to consume. Review examples that use Nomad interpolation and templates.
+---
+
+# `meta` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## Template usage example
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/reference/runtime-environment-settings#meta-block-for-arbitrary-configuration
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.11.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..2e9574936e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: migrate block in the job specification
+description: |-
+  Define the group's allocation migration strategy in the `migrate` block of the Nomad job specification. The migration strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+Migrating happens when a Nomad node is drained. When a node is lost, Nomad
+[replaces][] the allocations instead and ignores the `migrate` block.  When the
+agent fails to set up the allocation or the tasks of an allocation more than
+their [`restart`][] block allows, Nomad [reschedules][] the allocations instead
+and ignores the `migrate` block.
+
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/docs/manage/migrate-workloads) for details
+on node draining.
+
+## Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/commands/node/drain
+[deadline]: /nomad/commands/node/drain#deadline
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.11.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..16cb1c8c26
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,289 @@
+---
+layout: docs
+page_title: multiregion block in the job specification
+description: |-
+  Deploy a job to multiple federated regions in the `multiregion` block of the Nomad job specification. Learn about multi-region deployment states, parameterized dispatch, and periodic time zones. Configure region count, datacenters, metadata, and node pool. Specify region rollout strategy parameters. Review examples of max parallel, rollback regions, override counts, and merging metadata.
+---
+
+# `multiregion` block in the job specification
+
+<Placement groups={[['job', 'multi-region']]} />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+<EnterpriseAlert/>
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multi-region deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multi-region deployment states
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multi-region deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic time zones
+
+Multi-region periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multi-region jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multi-region deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multi-region deployments are considered GA.
+
+### `strategy` parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multi-region will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multi-region deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multi-region `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## Examples
+
+The following examples only show the `multi-region` block and the other
+blocks it might be interacting with.
+
+### Max parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multi-region {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/docs/deploy/clusters/federate-regions
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #examples
+[upgrade strategies]: /nomad/docs/job-declare/strategy/
+[`nomad deployment unblock`]: /nomad/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/network.mdx b/content/nomad/v1.11.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..94d21ee410
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,370 @@
+---
+layout: docs
+page_title: network block in the job specification
+description: |-
+  Configure task group networking requirements in the `network` block of the Nomad job specification. Configure network mode, hostname, port, DNS, and Container Network Interface (CNI) arguments. Review configuration examples of dynamic ports, static ports, mapped ports, bridge mode, host networks, DNS, and CNI networks.
+---
+
+# `network` block in the job specification
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul service mesh](/nomad/docs/networking/consul). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+- `cni` <code>([CNIConfig](#cni-parameters): nil)</code> - Sets the custom CNI
+  arguments for a network configuration per allocation, for use with `mode="cni/*`.
+
+### `port` parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+- `ignore_collision` `(bool: false)` - Allows the group to be placed on a node
+  where the port may already be reserved. Intended for programs that support
+  `SO_REUSEPORT` unix socket option, so more than one instance of the program
+  may bind to the same port. Only compatible with [`host`](#host) network mode
+  and `static` ports. Some task drivers (e.g. docker) may also require setting
+  `network_mode = "host"` (or similar) to avoid runtime errors after placement.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+## `cni` parameters
+
+- `args` `(map<string><string>: nil)` - Sets CNI arguments for network configuration.
+   These get turned into `CNI_ARGS` per the
+   [CNI spec](https://www.cni.dev/docs/spec/#parameters).
+
+These parameters support [interpolation](/nomad/docs/reference/runtime-variable-interpolation).
+
+## Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static ports
+
+Static ports place your job on a host where the port is not already reserved
+by another job with the same port.
+
+This example specifies a static port allocation for the port labeled "lb".
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+For programs that support the `SO_REUSEPORT` unix socket option,
+you may set `ignore_collision = true` to place multiple copies on a single node.
+
+### Mapped ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is necessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### CNI args
+
+The following example specifies CNI args for the custom CNI plugin specified above.
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+  cni {
+    args = {
+     "nomad.region" : "${node.region}"
+    }
+  }
+}
+```
+
+### Host networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/job-declare/task-driver/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul service mesh Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/numa.mdx b/content/nomad/v1.11.x/content/docs/job-specification/numa.mdx
new file mode 100644
index 0000000000..7469f21130
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/numa.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: numa block in the job specification
+description: |-
+  Define a NUMA-aware task scheduling strategy in the `numa` block of the Nomad job specification. Configure the affinity strategy and specify a list of devices that must be colocated on the same NUMA node.
+---
+
+# `numa` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources', 'numa']} />
+
+The `numa` block is used to configure how Nomad will assign CPU cores for a task
+while taking the [NUMA hardware topology][numa_wiki] of a node into consideration.
+Workloads that are sensitive to memory latency can perform significantly better
+when pinned to CPU cores on the same NUMA node.
+
+NUMA aware scheduling is currently limited to Linux.
+
+<EnterpriseAlert product="nomad"/>
+
+```hcl
+job "example" {
+  group "group" {
+    task "task" {
+      resources {
+        cores = 8
+        numa {
+          affinity = "require"
+        }
+      }
+    }
+  }
+}
+```
+
+In the example above, the task is requesting Nomad to reserve 8 CPU cores, all
+of which must be colocated on the same hardware NUMA node. The Nomad scheduler
+will ensure the task is placed on a Nomad node with sufficient unused CPU cores
+in a compatible configuration.
+
+Configuring the `numa` block requires the task specifies CPU resources using
+the [`cores`][cores] parameter.
+
+# Parameters
+
+- `affinity` `(string: "none")` - Specifies the strategy Nomad will use when
+  selecting CPU cores to assign to a task. Possible values are `"none"`,
+  `"prefer"`, or `"require"`.
+  - `none` - Nomad is free to allocate CPU cores using any strategy. Nomad uses
+  this freedom to allocate cores in such a way that minimizes the amount of
+  fragmentation of core availability per NUMA node. It does so by bin-packing
+  the chosen cores onto the NUMA nodes with the fewest number of cores available.
+  - `prefer` - Nomad will select the set of CPU cores on a node that minimizes
+  the total distance between those cores, but does not limit those CPU core
+  selections to come from a single NUMA node.
+  - `require` - Nomad will select a set of CPU cores that are strictly colocated
+  on the same hardware NUMA node. If there are no Nomad nodes with a sufficient
+  number of available cores in a compatible configuration, task placement will
+  fail due to exhausted resources.
+
+- `devices` `(list<string>: nil)` - Specifies which devices must be colocated on
+  the name NUMA node, along with allocated CPU cores. Must be a subset of the
+  devices listed in the [resources] block. May only be used with `affinity` set
+  to `require`.
+
+<Note>
+
+  The `require` affinity option causes fragmentation of available CPU cores
+  based on the NUMA node the selected cores are associated with. Use it for
+  workloads known to be highly sensitive to memory latencies. A cluster where
+  all jobs make use of the `require` affinity option will not be able to make
+  efficient use of available resources.
+</Note>
+
+## Examples
+
+This example will allocate a `1080ti` GPU and ensure it is on the same NUMA node
+as the 4 CPU cores reserved for the task.
+
+```hcl
+resources {
+  cores  = 4
+  memory = 2048
+
+  device "nvidia/gpu/1080ti" {
+    count = 1
+  }
+
+  numa {
+    affinity = "require"
+    devices = [
+      "nvidia/gpu/1080ti"
+    ]
+  }
+}
+```
+
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
+[cores]: /nomad/docs/job-specification/resources#cores
+[resources]: /nomad/docs/job-specification/resources
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.11.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..6523cd647e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: parameterized block in the job specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` block in the job specification
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+### Use periodic with parameterized
+
+Nomad uses an internal hierarchy when scheduling a job that is both `parameterized` and [`periodic`][periodic].
+
+```plaintext
+parameterized => periodic => batch
+```
+
+Nomad processes a periodic with parameterized job in the following order:
+
+1. Nomad does not dispatch a periodic job with null parameters in the periodic configuration. This forces the parameterized job to take precedence over the periodic job.
+2. After Nomad dispatches the parameterized job and gives it parameters, Nomad uses the periodic configuration.
+3. Nomad dispatches new jobs according to the periodic configuration that uses thee parameters from the triggering parameterized job.
+
+In this example, the periodic job does not trigger any new jobs
+until the operator dispatches the parameterized job at least once. After that, the
+dispatched child periodically triggers more children with the given parameters.
+
+```hcl
+  periodic {
+    crons = [
+      "*/40 * * * * * *"
+    ]
+  }
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+```
+
+
+
+There are three columns plus comments in this example output, which is for the preceding periodic, parameterized example job. Scroll to the last column to review the comments.
+
+```
+$ nomad job status
+ID                                                     Type                            Submit Date
+sync                                                   batch/periodic/parameterized    2024-11-07T10:43:30+01:00 // Original submitted job
+sync/dispatch-1730972650-247c6e97                      batch/periodic                  2024-11-07T10:44:10+01:00 // First dispatched job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972680  batch                           2024-11-07T10:44:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972760-f79a96e1                      batch/periodic                  2024-11-07T10:46:00+01:00 // Second dispatched job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972800  batch                           2024-11-07T10:46:40+01:00 // Cron job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters B
+```
+The output illustrates the following:
+
+1. The `sync` job is the parameterized and periodic job. However, Nomad doesn't run the periodic job until you submit with the required parameters.
+2. The `sync/dispatch-1730972650-247c6e97` job contains parameters and triggers the batch jobs, named `sync/dispatch-1730972650-247c6e97/periodic-1730972680` and `sync/dispatch-1730972650-247c6e97/periodic-1730972860`.
+3. The `sync/dispatch-1730972760-f79a96e1` job assigns new parameters and triggers new batch jobs that use those parameters.
+
+If you need to force the periodic job, force the the corresponding parameterized job.
+
+This example forces the first dispatched job with parameters A from the preceding example.
+
+```
+$ nomad job periodic force sync/dispatch-1730972650-247c6e97
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
+[periodic]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.11.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..7d2c752a1b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: periodic block in the job specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` block in the job specification
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+Refer to the [parameterized] documentation for how to use parameters with a periodic job.
+
+## Parameters
+
+- `cron` (_deprecated_: Replaced by `crons` in 1.6.2) `(string)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`. Either `cron` or `crons` must be set, but not both.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions. Either `cron` or `crons` must be set, but not both.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set time zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight saving time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
+[parameterized]: /nomad/docs/job-specification/parameterized#use-periodic-with-parameterized
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.11.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..0e0dd2e70d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: proxy block in the job specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul service mesh integration
+---
+
+# `proxy` block in the job specification
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul service mesh][]. It is valid only within the context of
+a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul service mesh documentation][envoy_dynamic_config]
+  for details. Keys and values support [runtime variable interpolation][].
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path
+  configuration for Envoy. See Consul's [Expose Paths Configuration
+  Reference][expose_path_ref] for more information.
+- `local_service_address` `(string: "127.0.0.1")` - The address the local
+  service binds to. Useful to customize in clusters with mixed Connect and
+  non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in
+  clusters with mixed Connect and non-Connect services.
+- `transparent_proxy` <code>([transparent_proxy][]: nil)</code> - Used to enable
+  [transparent proxy][tproxy] mode, which allows the proxy to use Consul service
+  intentions to automatically configure upstreams, and configures iptables rules
+  to force traffic from the allocation to flow through the proxy.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of
+  each upstream service that this sidecar proxy communicates with.
+
+## Examples
+
+The following example is a proxy specification that includes upstreams
+configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+The following example is a proxy specification that includes transparent proxy
+configuration. Note that with transparent proxy, you will not need to configure
+an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+[Consul service mesh]: /nomad/docs/networking/consul
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[runtime variable interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
+[envoy_dynamic_config]: /consul/docs/connect/proxies/envoy#dynamic-configuration
+[expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[transparent_proxy]: /nomad/docs/job-specification/transparent_proxy
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.11.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..d4dfe5784d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: reschedule block in the job specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified
+at the job level, the configuration will apply to all groups within the job. If
+the reschedule block is present on both the job and the group, they are merged
+with the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its task
+statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+Rescheduling happens when the Nomad agent fails to set up the allocation or the
+tasks of an allocation fail more than their [`restart`][] block allows. When a
+node is drained, Nomad [migrates][] the allocations instead and ignores the
+`reschedule` block. When a node is lost, Nomad [replaces][] the allocations
+instead and ignores the `reschedule` block.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is
+  set to `true` the `attempts` and `interval` fields are not used. The [`progress_deadline`][]
+  parameter within the update block is still adhered to when this is set to `true`, meaning no more
+  reschedule attempts are triggered once the [`progress_deadline`][] is reached.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### Parameter defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
+
+[`progress_deadline`]: /nomad/docs/job-specification/update#progress_deadline
+[`restart`]: /nomad/docs/job-specification/restart
+[migrates]: /nomad/docs/job-specification/migrate
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.11.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..396c4d0bc5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,169 @@
+---
+layout: docs
+page_title: resources block in the job specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `numa` <code>([Numa][]: &lt;optional&gt;)</code> - Specifies the
+  NUMA scheduling preference for the task. Requires the use of `cores`.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+- `secrets` <code>(`int`: &lt;optional&gt;)</code> - Specifies the size of the
+  [`secrets/`][] directory in MB, on platforms where the directory is a
+  tmpfs. If set, the scheduler adds the `secrets` value to the `memory` value
+  when allocating resources on a client, and this value will be included in the
+  allocated resources shown by the `nomad alloc status` and `nomad node status`
+  commands. If unset, the client will allocate 1 MB of tmpfs space and it will
+  not be counted for scheduling purposes or included in allocated resources. You
+  should not set this value if the workload will be placed on a platform where
+  tmpfs is unsupported, because it will still be counted for scheduling
+  purposes.
+
+## Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block,
+Nomad finds a client with enough spare capacity to reserve 2 cores exclusively
+for the task. Unlike the `cpu` field, the task does not share CPU time with any
+other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of
+the job fails.
+
+Refer to [How Nomad Uses CPU][concepts-cpu] for more details on Nomad's
+reservation of CPU resources.
+
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2048 MB:
+
+```hcl
+resources {
+  memory = 2048
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`raw_exec`, `exec2`, `exec`, `docker`, `podman`, and `java` task drivers.  Consult the
+documentation of community-supported task drivers for their memory
+oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][quota_spec] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/deploy/task-driver/docker#cpu
+[exec_cpu]: /nomad/docs/deploy/task-driver/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[quota_spec]: /nomad/docs/other-specifications/quota
+[numa]: /nomad/docs/job-specification/numa 'Nomad NUMA Job Specification'
+[`secrets/`]: /nomad/docs/reference/runtime-environment-settings#secrets
+[concepts-cpu]: /nomad/docs/architecture/cpu
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.11.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..aba2dfde20
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: restart block in the job specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task. Restarts are different from
+[rescheduling][], which happens when the tasks run out of restart attempts.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### Parameter defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### Disabling restart
+
+To disable restarting, set the `attempts` parameter to zero and `mode` to `"fail"`.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+  }
+}
+```
+
+### `mode` values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[rescheduling]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.11.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..7ee3281e6a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling block in the job specification
+description: The `scaling` block allows specifying scaling policy for a task group
+---
+
+# `scaling` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/schedule.mdx b/content/nomad/v1.11.x/content/docs/job-specification/schedule.mdx
new file mode 100644
index 0000000000..adc5cfb35b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/schedule.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: schedule block in the job specification
+description: |-
+  Time based task execution is enabled by using the `schedule` task block.
+---
+
+# `schedule` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'periodic']} />
+
+Time based task execution is enabled by using the `schedule` block. The
+`schedule` block controls when a task is allowed to be running.
+
+<EnterpriseAlert product="nomad"/>
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+Unlike [`periodic`][periodic] jobs, the `schedule` block applies to individual
+tasks. The Nomad Client starts and stops tasks at the specified time without
+interaction with the Nomad Servers. This means time based task execution works
+even when a Client is disconnected from Servers. The task's resources remain
+allocated even outside the `schedule` when the task itself is stopped.
+
+```hcl
+job "docs" {
+  group "tbte" {
+    task "scheduled" {
+      schedule {
+        cron {
+          start    = "30 9 * * MON-FRI *"
+          end      = "0 16"
+          timezone = "America/New_York"
+        }
+      }
+    }
+  }
+}
+```
+
+## Parameters
+
+The `schedule` block must have a `cron` block containing:
+
+- `start` `(string: <required>)` - When the task should be started. Specified in 6 field
+  [cron format][cron] (no seconds) without `,` or `/` characters.
+
+- `end` `(string: <required>)` - When the task should be stopped
+  ([`kill_signal`][kill_signal] and [`kill_timeout`][kill_timeout] apply).
+  Specified in 2 field [cron format][cron] (minute and hour) without `,` or `/`
+  characters.
+
+- `timezone` `(string: "Local")` - What time zone the `start` and `end` times
+  are specified in. Defaults to the local time zone of the Nomad Client the job
+  is scheduled onto.
+
+## Limitations
+
+- Job deployments outside of the specified `schedule` will be unable to
+  succeed. To update a job using time based task execution outside of its
+  schedule, do a [force
+  update](/nomad/docs/job-specification/update#max_parallel-0).
+
+- Overnight schedules are currently not supported. Adjusting the `timezone`
+  should allow converting overnight schedules to times within a single day.
+
+[periodic]: /nomad/docs/job-specification/periodic
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/secret.mdx b/content/nomad/v1.11.x/content/docs/job-specification/secret.mdx
new file mode 100644
index 0000000000..4bbb0cb190
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/secret.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: secret block in the job specification
+description: |-
+  The `secret` block allows the task to specify that it requires a secret from a
+  specified location. Nomad automatically retrieves the secret for the task
+  and provides it for variable interpretation.
+---
+
+# `secret` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'secret'],
+    ['job', 'group', 'secret'],
+    ['job', 'group', 'task', 'secret'],
+  ]}
+/>
+
+The `secret` block allows a task to specify that it requires a secret from
+a specified location. Nomad automatically retrieves the contents of the
+secret, which you may reference as a variable within the task specification.
+If specified at the `group` level, the secret is available to every task
+within the group. If specified at the `job` level, every task in the job
+fetches the secret and is able to interpret it within the task specification.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      secret "my_secret" {
+        provider = "vault"
+        path     = "path/to/secret"
+        config {
+          engine = "kv_v2"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad parses the key value pairs in a secret and makes them available for
+variable interpolation in the following format:
+`secret.<secret_name>.<secret_key>`. To use the preceding task specification
+as an example, you would reference the value in the secret key "foo"  as
+`${secret.my_secret.foo}`.
+
+## Parameters
+
+- `provider` `(string: "")` - Specifies the underlying implementation to use in
+  order for Nomad to interact with a specific secret store.
+
+- `path` `(string: "")` - Specifies the location of the secret within the given
+  secret store.
+
+- `config` `(block: {})` - Specifies any custom attributes used by built-in
+  providers order to fetch the secret. Only available for built-in `vault` and
+  `nomad` providers.
+
+- `env` `(map[string]string)` - Specifies any environment variables to pass to a
+  custom plugin provider. Only available for custom providers.
+
+## Built-in providers
+
+- `nomad` - Query variables from Nomad. Nomad uses the task's [Workload
+  Identity] [Workload Identity] token in order to fetch the variable, so the
+  task must have the necessary access via ACLs to read the variable.
+
+  Config parameters:
+
+   - `namespace` `(string: "default")` - Specifies the namespace where the
+  variable is located.
+
+
+- `vault` - Query secrets from Vault. Similar to the template block, making
+  requests to Vault requires a vault token, which is generated via the
+  [vault][vault] block.
+
+  Config parameters:
+
+    - `engine` `(string: "kv_v2")` - Specifies what Vault storage engine to
+  query. Options are `kv_v1` and `kv_v2`.
+
+
+## Custom providers
+
+Nomad extends the provider list via the use of custom providers plugins. Custom
+providers must implement both the `fingerprint` and `fetch` functionality. You
+must place custom providers in the `common_plugin_dir/secrets/` subdirectory. On
+startup, the Nomad client fingerprints executables in the secrets directory by
+executing it with the first argument of `fingerblock`. When using a custom
+plugin "foo", Nomad looks for an executable "foo" and runs it with the first
+argument being "fetch", and the second argument being the secret's path
+parameter. Refer to the [plugin authoring][secret-provider] guide on secret providers
+for an example custom provider.
+
+A custom provider should print to stdout a fingerprint response:
+
+```json
+{
+  "type": "secrets",
+  "version": "0.0.1" (use appropriate version)
+}
+```
+
+And a valid "fetch" response should have the form:
+
+```json
+{
+  "result": {
+    "key1": "value1",
+    "key2": "value2"
+  },
+  "error": ""
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[vault]: /nomad/docs/job-specification/vault
+[common_plugin_dir]: /nomad/docs/configuration/client#custom_plugin_dir
+[secret-provider]: /nomad/plugins/author/secret-provider
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/service.mdx b/content/nomad/v1.11.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..5737d1da64
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,572 @@
+---
+layout: docs
+page_title: service block in the job specification
+description: |-
+  The `service` block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider: Nomad or Consul. This section of the documentation discusses the
+configuration, but you should also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        weights {
+          passing = 5
+          warning = 1
+        }
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+
+        identity {
+          aud = ["consul.io"]
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only covers the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul, refer to
+the [Consul integration documentation][service-discovery].
+
+The `service` block can also be at task group level.
+This enables services in the same task group to opt into [Consul
+service mesh][connect] integration.
+
+## Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use, when the `provider` is `"consul"`. The Nomad client
+  will retrieve a Consul token from the cluster configured in the agent
+  configuration with the same [`consul.name`][]. In Nomad Community Edition,
+  this field is ignored.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `weights` <code>(Weights: nil)</code> - Specifies how a service instance is
+  weighted in a DNS SRV request based on the service's health status, as
+  described in the Consul [weights][] documentation. Only available where
+  `provider = "consul"` The `weight` block supports the following fields:
+  - `passing` <code>int: 1</code> - The weight of services in passing state.
+  - `warning` <code>int: 1</code> - The weight of services in warning state.
+
+- `connect` - Configures the [Consul service mesh][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `kind` `(string: <optional>)` - Configures the [Consul Service
+  Kind][kind] to pass to Consul during service registration. Only available
+  when `provider = "consul"`, and is ignored if a Consul service mesh Gateway is
+  defined.
+
+- `identity` <code>([Identity][identity_block]: nil)</code> - Specifies a
+  Workload Identity to use when obtaining Service Identity tokens from Consul to
+  register the service. Only available where `provider = "consul"`. Typically
+  this can be omitted so that Nomad will fall back to the server's
+  [`consul.service_identity`][] block.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of dual-stack or IPv6-only.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+  | Service kind | Allowed port value type |
+  | -------- | ------- |
+  | Normal       | Numeric or port mapping label |
+  | Uses [`connect` native][connect-native] | Numeric or port mapping label |
+  | Uses [`connect` sidecar][connect-sidecar] | Numeric |
+  | Ingress gateway | Port mapping label (optional) |
+  | Terminating gateway | None (optional) |
+  | Mesh gateway | External port mapping label |
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc, alloc_ipv6 or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `alloc_ipv6` - Same as `alloc` but use the IPv6 address in case of dual-stack or IPv6-only.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul service mesh native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using driver address mode
+
+The [Docker](/nomad/docs/job-declare/task-driver/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/job-declare/task-driver/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/job-declare/task-driver/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect
+[kind]: /consul/api-docs/agent/service#kind
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[identity_block]: /nomad/docs/job-specification/identity
+[weights]: /consul/docs/services/configuration/services-configuration-reference#weights
+[connect-sidecar]: /nomad/docs/job-specification/connect#using-sidecar-service
+[connect-native]: /nomad/docs/job-specification/connect#using-consul-service-mesh-native
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.11.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..8e5f929dba
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service block in the job specification
+description: |-
+  The `sidecar_service` block allows specifying options for configuring
+  sidecar proxies used in Consul service mesh integration
+---
+
+# `sidecar_service` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+service mesh](/nomad/docs/networking/consul) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       test-key = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.11.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..553fa96a7c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: sidecar_task block in the job specification
+description: |-
+  The `sidecar_task` block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul service mesh integration
+---
+
+# `sidecar_task` block in the job specification
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+service mesh](/nomad/docs/networking/consul) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+## Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.11.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..79d04f00b9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: spread block in the job specification
+description: >-
+  The `spread` block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter.
+
+By default, when `spread` is omitted, the scheduler will attempt to place
+allocations from the same job on different nodes (and binpacked between
+jobs). When using `spread` the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target
+percentage defined in the spread block. Spread scores are combined with other
+scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to
+express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler. If no
+nodes match a given spread criteria, placement is still successful. To avoid
+scoring every node for every placement, allocations may not be perfectly
+spread. Spread works best on attributes with similar number of nodes:
+identically configured racks or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client
+metadata][client-meta].  Additionally, spread may be specified at the [job][job]
+and [group][group] levels for ultimate flexibility. Job level spread criteria
+are inherited by all task groups in the job.
+
+Updating the `spread` block is non-destructive. Updating a job specification
+with only non-destructive updates will not migrate or replace existing
+allocations.
+
+## Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+### Target parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## Comparison to `spread` scheduling algorithm
+
+The `spread` block is not the same concept as setting the [scheduler
+algorithm][] to `"spread"` instead of `"binpack"`. Setting the scheduler
+algorithm impacts all jobs on a cluster (or node pool), and adjusts the tendency
+of the scheduler to place workloads from different jobs on the same set of nodes
+or not. The `spread` block impacts how the scheduler places allocations for a
+given job.
+
+## Scheduling performance
+
+Using the `spread` block can have significant impact on scheduling
+performance. For each allocation in a `service` and `batch` job, the scheduler
+iterates over nodes until it finds a small number of feasible nodes. Those
+feasible nodes are then scored to find the best placement.
+
+When `spread` is omitted, this limit is 2 for batch jobs and the log<sub>2</sub>
+of the total number of nodes in the datacenter and node pool (with a minimum of
+2) for service jobs. When the `spread` block is present, the scheduler instead
+scores a number of nodes in the datacenter and node pool equal to the task group
+count (with a maximum of 100) per allocation. This can result in
+order-of-magnitude increases in scheduling times.
+
+To monitor scheduling times potentially impacted by `spread` blocks, examine the
+`nomad.nomad.worker.invoke_scheduler.*` found in the [Key Metrics][] table. You
+can reduce scheduling times by avoiding `spread` and instead relying on the
+default distribution of a job across multiple nodes. If this is not possible,
+you may consider reducing the size of the node pool or datacenter to reduce the
+number of nodes available for the scheduler to consider.
+
+## Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even spread across data center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread with target percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread across multiple attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/reference/runtime-variable-interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+[Key Metrics]: /nomad/docs/reference/metrics#key-metrics
+[scheduler algorithm]: /nomad/commands/operator/scheduler/set-config#scheduler-algorithm
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/task.mdx b/content/nomad/v1.11.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..fe3eb0ea81
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: task block in the job specification
+description: |-
+  The `task` block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` block in the job specification
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `consul` <code>([Consul][consul_jobspec]: nil)</code> - Specifies Consul
+  configuration options specific to the task.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/job-declare/task-driver) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown process
+  starts by applying the `shutdown_delay` if configured. It then stops the the
+  leader task first, if any, followed by non-sidecar and non-poststop tasks, and
+  finally sidecar tasks. Once this process completes, post-stop tasks are
+  triggered. See the [lifecycle][] documentation for a complete description of
+  task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] images specify their own default users. Clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as [certain
+  users][user_denylist]. On UNIX-like systems, setting `user` also affects
+  the environment variables `HOME`, `USER`, and `LOGNAME` available to the task.
+  On Windows, when Nomad is running as a [system service][service] for the
+  [`raw_exec`][raw_exec] driver, you may specify a less-privileged service user.
+  For example, `NT AUTHORITY\LocalService`, `NT AUTHORITY\NetworkService`.
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul service mesh.
+
+## Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/job-declare/task-driver).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and environment variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_jobspec]: /nomad/docs/job-specification/consul
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/job-declare/task-driver/exec 'Nomad exec Driver'
+[raw_exec]: /nomad/docs/job-declare/task-driver/raw_exec 'Nomad raw_exec Driver'
+[java]: /nomad/docs/job-declare/task-driver/java 'Nomad Java Driver'
+[docker]: /nomad/docs/job-declare/task-driver/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/networking/service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
+[service]: /nomad/docs/deploy/production/windows-service
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/template.mdx b/content/nomad/v1.11.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..174d5ef758
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,836 @@
+---
+layout: docs
+page_title: template block in the job specification
+description: |-
+  The `template` block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `once` `(bool: false)` - Specifies that the client will wait for the template
+  to be rendered, and then no longer watch the dependencies specified in the
+  template. This is useful for templates that do not need to be updated. Once mode
+  implicitly disables wait/quiescence timers for this template, and ignores change
+  mode/signal/script settings.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad integration
+
+### Nomad services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple load balancing with Nomad services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin", "executeTemplate",
+  "writeToFile"])` - Specifies a list of template rendering functions that
+  should be disallowed in job specs. By default, the `plugin` function is
+  disallowed as it allows running arbitrary commands on the host as root (unless
+  Nomad is configured to run as a non-root user), `executeTemplate` is
+  disallowed to prevent accidental or malicious infinitely recursive execution,
+  and `writeToFile` is disallowed.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/docs/reference/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/reference/runtime-environment-settings 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/reference/runtime-variable-interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/reference/runtime-environment-settings#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/transparent_proxy.mdx b/content/nomad/v1.11.x/content/docs/job-specification/transparent_proxy.mdx
new file mode 100644
index 0000000000..d40af3315e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/transparent_proxy.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: transparent_proxy block in the job specification
+description: |-
+  The `transparent_proxy` block allows specifying options for configuring Envoy
+  in Consul service mesh transparent proxy mode.
+---
+
+# `transparent_proxy` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'transparent_proxy',
+  ]}
+/>
+
+The `transparent_proxy` block configures the Envoy sidecar proxy to act as a
+Consul service mesh [transparent proxy][tproxy]. This simplifies the configuration of
+Consul service mesh by eliminating the need to configure [`upstreams`][] blocks in
+Nomad. Instead, the Envoy proxy will determines its configuration entirely from
+Consul [service intentions][].
+
+When transparent proxy is enabled traffic will automatically flow through the
+Envoy proxy. If the local Consul agent is serving DNS, Nomad will also set up
+the task's nameservers to use Consul. This lets your workload use the [virtual
+IP][] DNS name from Consul, rather than configuring a `template` block that
+queries services.
+
+Using transparent proxy has some important restrictions:
+
+* You can only have a single `connect` block in any task group that uses
+  transparent proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`](#no_dns), see below).
+* The node where the allocation is placed must be configured as described in
+  the Service Mesh integration documentation for [Transparent Proxy][].
+* The workload's task cannot use the same Unix user ID (UID) as the Envoy
+  sidecar proxy.
+
+## Parameters
+
+* `exclude_inbound_ports` `([]string: nil)` - A list of inbound ports to exclude
+  from the inbound traffic redirection. This allows traffic on these ports to
+  bypass the Envoy proxy. These ports can be specified as either [network port
+  labels][port_labels] or as numeric ports. Nomad will automatically add the
+  following to this list:
+  * The [`local_path_port`][] of any [`expose`][] block.
+  * The port of any service check with [`expose=true`][check_expose] set.
+  * The port of any `network.port` with a [`static`][] value.
+* `exclude_outbound_cidrs` `([]string: nil)` - A list of CIDR subnets that
+  should be excluded from outbound traffic redirection. This allows traffic to
+  these subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_ports`; CIDR subnets listed here are excluded regardless of
+  the port.
+* `exclude_outbound_ports` `([]int: nil)` - A list of port numbers that should
+  be excluded from outbound traffic redirection. This allows traffic to these
+  subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_cidrs`; ports listed here are excluded regardless of the
+  CIDR.
+* `exclude_uids` `([]string: nil)` - A list of Unix user IDs (UIDs) that should
+  be excluded from outbound traffic redirection. When unset, only the Envoy
+  proxy's user will be allowed to bypass the iptables rule.
+* `no_dns` `(bool: false)` - By default, Consul will be set as the nameserver
+  for the workload and IP tables rules will redirect DNS queries to Consul. If
+  you want only external DNS, set `no_dns=true`. You will need to add your own
+  CIDR and port exclusions for your DNS nameserver. You cannot set
+  [`network.dns`][] if `no_dns=false`.
+* `outbound_port` `(int: 15001)` - The port that Envoy will bind on inside the
+  network namespace. The iptables rules created by `consul-cni` will force
+  traffic to flow to this port. You should only set this value if you have
+  specifically set the [`outbound_listener_port`][] in your Consul proxy
+  configuration. You can change the default value for a given node via [client
+  metadata](#client-metadata) (see below).
+* `uid` `(string "101")` - The Unix user ID (UID) used by the Envoy proxy. You
+  should only set this value if you have a custom build of the Envoy container
+  image which uses a different UID. You can change the default value for a given
+  node via [client metadata](#client-metadata) (see below). Note that your
+  workload's task cannot use the same UID as the Envoy sidecar proxy.
+
+## Client metadata
+
+You can change the default [`outbound_port`](#outbound_port) and [`uid`](#uid)
+for a given client node by updating the node metadata via the [`nomad node meta
+apply`][] command. The attributes that can be updated are:
+
+* `connect.transparent_proxy.default_uid`: Sets the default value of
+  [`uid`](#uid) for this node.
+* `connect.transparent_proxy.default_outbound_port`: Sets the default value of
+  [`outbound_port`](#outbound_port) for this node.
+
+For example, to set the default value for the `uid` field to 120:
+
+```shell-session
+$ nomad node meta apply connect.transparent_proxy.default_uid=120
+$ nomad node meta read -json | jq -r '.Dynamic | ."connect.transparent_proxy.default_uid"'
+120
+```
+
+You should not normally need to set these values unless you are using custom
+Envoy images.
+
+## Examples
+
+### Minimal
+
+The following example is a minimal transparent proxy specification. Note that
+with transparent proxy, you will not need to configure an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+If you had a downstream task group `count-dashboard` that needed to connect to
+an upstream task group `count-api` listening on port 9001, you could create a
+Consul service intention with the following specification:
+
+```hcl
+Kind = "service-intentions"
+Name = "count-api"
+Sources = [
+  {
+    Name   = "count-dashboard"
+    Action = "allow"
+  }
+]
+```
+
+And then the downstream service `count-dashboard` could reach the `count-api`
+service by making requests to `http://count-api.virtual.consul`.
+
+### External DNS
+
+The following example is a transparent proxy specification where external DNS is
+used. To find the address of other allocations in this configuration, you will
+need to use a [`template`][] block to query Consul.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+      excluded_outbound_ports = [53]
+      excluded_outbound_cidrs = ["208.67.222.222/32", "208.67.220.220/32"]
+      no_dns                  = true
+    }
+  }
+}
+```
+
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[service intentions]: /consul/docs/connect/config-entries/service-intentions
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[cni_plugins]: /nomad/docs/job-networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[port_labels]: /nomad/docs/job-specification/network#port-parameters
+[`local_path_port`]: /nomad/docs/job-specification/expose#local_path_port
+[`expose`]: /nomad/docs/job-specification/expose
+[check_expose]: /nomad/docs/job-specification/check#expose
+[`static`]: /nomad/docs/job-specification/network#static
+[`outbound_listener_port`]: /consul/docs/connect/proxies/proxy-config-reference#outbound_listener_port
+[`template`]: /nomad/docs/job-specification/template#consul-integration
+[`nomad node meta apply`]: /nomad/commands/node/meta/apply
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[Transparent Proxy]: /nomad/docs/networking/consul/service-mesh#transparent-proxy
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/ui.mdx b/content/nomad/v1.11.x/content/docs/job-specification/ui.mdx
new file mode 100644
index 0000000000..e142068717
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/ui.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: ui block in the job specification
+description: |-
+  The `ui` block adds descriptions and helpful links to a
+  job page in the Nomad Web UI.
+---
+
+# `ui` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'ui'],
+  ]}
+/>
+
+The `ui` block provides options to modify the presentation of the Job index page
+in the Web UI. When specified, a description and any number of links will be
+added to the top of the job page in question.
+
+The following will provide the Web UI with a job description and a pair of links:
+
+## Parameters
+
+- `description` `(string: "")` - The markdown-enabled description of the job. We
+  support [GitHub Flavored Markdown](https://github.github.com/gfm/).
+- `link` `(map<string|string>: nil)` - A link that should show up in the header
+  of the job index page in the Web UI. A job can have any number of links, and
+  they must contain both a string `label` and `url`.
+
+## Example
+
+```hcl
+job "docs" {
+  ui {
+    description = "A job that uses **Nomad Variables**"
+    link {
+      label = "Learn more about Nomad"
+      url   = "https://developer.hashicorp.com/nomad"
+    }
+    link {
+      label = "Nomad on GitHub"
+      url   = "https://github.com/hashicorp/nomad"
+    }
+  }
+  # ...
+}
+```
+
+![Job UI links and description rendered in the Web UI](/img/nomad-ui-block.png)
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/update.mdx b/content/nomad/v1.11.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..ac95dc15c3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,292 @@
+---
+layout: docs
+page_title: update block in the job specification
+description: |-
+  The `update` block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+## Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task
+  group that can be destructively updated at the same time. The task groups themselves are
+  updated in parallel. In-place updates are performed all at once.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates
+    instead of deployments
+
+  ~> **Note:** System jobs only support one allocation per node. When `canary`
+  is set, system job updates make up to `max_parallel` destructive updates *or*
+  destructively update enough allocations to place on `canary` percent of
+  feasible nodes, whichever is lower. You should adjust the `max_parallel` value
+  to allow deploying all desired canaries.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+  In system jobs, the `canary` setting indicates the percentage of feasible
+  nodes to which Nomad makes destructive allocation updates. System jobs do
+  not support more than one allocation per node, so effectively setting `canary`
+  to a positive integer means this percentage of feasible nodes gets a new
+  version of the job if the update is destructive. Non-destructive updates
+  ignore the `canary` field. Setting `canary` to 100 updates the job on all
+  nodes. Percentage of nodes is always rounded up to the nearest integer. If
+  `canary` is set, nodes that register during a deployment do not receive
+  placements until after the deployment is promoted.
+
+  ~> **Note:** Updates when `canary` is set make up to `max_parallel`
+  destructive updates *or* destructively update enough allocations to place on
+  `canary` percent of feasible nodes, whichever is lower. You should adjust the
+  `max_parallel` value to allow deploying all desired canaries.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting is being deprecated, and is equivalent to
+  [`min_healthy_time`](#min_healthy_time).
+
+## Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel upgrades based on checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel upgrades based on task state
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update block inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/docs/job-declare/strategy/blue-green-canary
+[checks]: /nomad/docs/job-specification/service#check
+[rolling]: /nomad/docs/job-declare/strategy/rolling
+[strategies]: /nomad/docs/job-declare/strategy
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.11.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..475b634e1f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: upstreams block in the job specification
+description: |-
+  The `upstreams` block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` block in the job specification
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul service mesh][] proxy routes to. It is valid only within the
+context of a `proxy` block.
+
+For Consul-specific details see the [Consul service mesh Guide][]. Note that using
+`upstream` may not be necessary if you have configured the proxy with the
+[`transparent_proxy`][] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul service mesh documentation][consul_expose_path_ref]
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_partition` `(string: "")` - Name of the Cluster admin partition containing the upstream service.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul service mesh the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[Consul service mesh]: /nomad/docs/networking/consul
+[Consul service mesh Guide]: /consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
+[consul_expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.11.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..449608f0b8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: vault block in the job specification
+description: |-
+  The `vault` block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` block in the job specification
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        cluster  = "default"
+        role     = "prod"
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `disable_file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## Parameters
+
+- `allow_token_expiration` `(bool: false)` - Specifies that Nomad clients should
+  not attempt to renew a task's Vault token, allowing it to expire. This should
+  only be used when a secret is requested from Vault once at the start of a task
+  or in a short-lived prestart task. Long-running tasks should never set
+  `allow_token_expiration=true` if they obtain Vault secrets via `template`
+  blocks, as the Vault token will expire and the template runner will continue
+  to make failing requests to Vault until its [`vault_retry`][] attempts are
+  exhausted, at which point the task will fail.
+
+  When Nomad has been configured to use [Workload Identity with Vault][], Nomad
+  clients will automatically detect when tokens cannot be refreshed (for
+  example, when the Vault auth method is configured to issue batch tokens). In
+  this case, the `allow_token_expiration` option will be implicitly set to
+  `true` by the client. The [legacy Vault authentication workflow][] cannot
+  automatically detect this.
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Vault cluster to use. The Nomad client will retrieve a Vault token from the
+  cluster configured in the agent configuration with the same
+  [`vault.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `role` `(string: "")` - Specifies the Vault role used when retrieving a token
+  from Vault using JWT and workload identity. If not specified the client's
+  [`create_from_role`][] value is used.
+
+## Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+Vault policies from the "prod" role attached.
+
+```hcl
+vault {
+  role = "prod"
+}
+```
+
+### Signal task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  role = "prod"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private token and change modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  role         = "prod"
+  change_mode  = "noop"
+  env          = false
+  disable_file = true
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  role      = "prod"
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[`create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[docker]: /nomad/docs/job-declare/task-driver/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
+[`vault.name`]: /nomad/docs/configuration/vault#name
+[`vault_retry`]: /nomad/docs/configuration/client#vault_retry
+[Workload Identity with Vault]: /nomad/docs/secure/vault/acl#nomad-workload-identities
+[legacy Vault authentication workflow]: /nomad/docs/v1.8.x/integrations/vault/acl
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.11.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..1af5d9801c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: volume block in the job specification
+description: >-
+  Configure storage volumes in the `volume` block of a Nomad job specification. Specify dynamic host or Container Storage Interface (CSI) volume type, node access mode, filesystem or block device attachment mode, and mount options. Enable read only access and mounting a unique volume per node. Learn about volume interpolation.
+---
+
+# `volume` block in the job specification
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server ensures that the allocations are only scheduled on hosts
+that have a set of volumes that meet the criteria specified in the `volume`
+blocks. These may be [static host volumes][host_volume] configured on the
+client, [dynamic host volumes][] created via [`volume create`][] or [`volume
+register`][], or [CSI volumes][csi_volume] dynamically mounted by [CSI
+plugins][csi_plugin].
+
+The Nomad client makes the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The valid volume
+  types are `"host"` and `"csi"`. Setting the `"host"` value can request either
+  statically configured host volumes or dynamic host volumes, depending on what
+  is available on a given node.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `sticky` `(bool: false)` - Specifies that this volume sticks to the allocation
+  that uses it. Upon every reschedule and replacement, the task
+  group always receives the volume with the same ID, if available. Use sticky
+  volumes for [stateful deployments]. You may only use the `sticky` field for
+  dynamic host volumes. For CSI volumes, the `per_alloc` field provides similar
+  functionality
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries. `per_alloc` is mutually exclusive with the `sticky`
+  property. Use `per_alloc` only with CSI volumes and `sticky` only
+  with dynamic host volumes.
+
+The following fields are only valid for volumes with `type = "csi"` or dynamic
+host volumes with `type = "host"`:
+
+- `access_mode` `(string)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks.
+
+  - For CSI volumes the `access_mode` is required. Can be one of the following:
+
+    - `"single-node-reader-only"`
+    - `"single-node-writer"`
+    - `"multi-node-reader-only"`
+    - `"multi-node-single-writer"`
+    - `"multi-node-multi-writer"`
+
+    Most CSI plugins support only single-node modes.
+    Consult the documentation of the storage provider and CSI plugin.
+
+  - For dynamic host volumes the `access_mode` is optional. Can be one of the following:
+
+    - `"single-node-writer"`
+    - `"single-node-reader-only"`
+    - `"single-node-single-writer"`
+    - `"single-node-multi-writer"`
+
+    Defaults to `single-node-writer` unless `read_only = true`, in which case it
+    defaults to `single-node-reader-only`.
+
+- `attachment_mode` `(string)` - The storage API used by the
+  volume. One of `"file-system"` or `"block-device"`. The `access_mode` and
+  `attachment_mode` together must exactly match one of the volume's `capability`
+  blocks.
+
+  - For CSI volumes the `attachment_mode` field is required. Most storage
+    providers support `"file-system"`, to mount volumes using the CSI
+    filesystem API. Some storage providers support `"block-device"`, which
+    mounts the volume with the CSI block device API within the container.
+
+  - For dynamic host volumes the `attachment_mode` field is optional and
+    defaults to `"file-system"`.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/commands/volume/register
+[attachment mode]: /nomad/commands/volume/register#attachment_mode
+[volume registration]: /nomad/commands/volume/register#mount_options
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[stateful deployments]: /nomad/docs/concepts/stateful-deployments
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
diff --git a/content/nomad/v1.11.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.11.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..007bd3d434
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: volume_mount block in the job specification
+description: |-
+  The `volume_mount` block allows the task to specify where a group `volume`
+  should be mounted.
+---
+
+# `volume_mount` block in the job specification
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+- `selinux_label``(string: "")` - Specifies the SELinux label for the mount.
+  This is only supported on Linux hosts and when supported by the task driver. Refer to the task driver documentation for more information. Possible
+  values are:
+
+  - `Z` -  Specifies that the volume content is private and unshared between
+    containers.
+  - `z` - Specifies that the volume content is shared among containers.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/reference/hcl2
diff --git a/content/nomad/v1.11.x/content/docs/manage/autopilot.mdx b/content/nomad/v1.11.x/content/docs/manage/autopilot.mdx
new file mode 100644
index 0000000000..e534616910
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/autopilot.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: Autopilot
+description: |-
+  Configure and use Autopilot features to help maintain your cluster. Monitor
+  server health, upgrade and clean up servers, and use redundancy zones.
+---
+
+# Autopilot
+
+Autopilot is a set of new features added in Nomad 0.8 to allow for automatic
+operator-friendly management of Nomad servers. It includes cleanup of dead
+servers, monitoring the state of the Raft cluster, and stable server
+introduction.
+
+To enable Autopilot features (with the exception of dead server cleanup), the
+`raft_protocol` setting in the [server stanza] must be set to 3 on all servers.
+
+## Configuration
+
+The configuration of Autopilot is loaded by the leader from the agent's
+[Autopilot settings] when initially bootstrapping the cluster:
+
+```hcl
+autopilot {
+  cleanup_dead_servers      = true
+  last_contact_threshold    = "200ms"
+  max_trailing_logs         = 250
+  server_stabilization_time = "10s"
+  enable_redundancy_zones   = false
+  disable_upgrade_migration = false
+  enable_custom_upgrades    = false
+}
+
+```
+
+After bootstrapping, the configuration can be viewed or modified either via the
+[`operator autopilot`] subcommand or the
+[`/v1/operator/autopilot/configuration`] HTTP endpoint:
+
+View the configuration.
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+EnableRedundancyZones = false
+DisableUpgradeMigration = false
+EnableCustomUpgrades = false
+```
+
+Update the configuration.
+
+```shell-session
+$ nomad operator autopilot set-config -cleanup-dead-servers=false
+Configuration updated!
+```
+
+View the configuration to confirm your changes.
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = false
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+EnableRedundancyZones = false
+DisableUpgradeMigration = false
+EnableCustomUpgrades = false
+```
+
+## Dead server cleanup
+
+Dead servers will periodically be cleaned up and removed from the Raft peer set,
+to prevent them from interfering with the quorum size and leader elections. This
+cleanup will also happen whenever a new server is successfully added to the
+cluster.
+
+Prior to Autopilot, it would take 72 hours for dead servers to be automatically
+reaped, or operators had to script a `nomad force-leave`. If another server
+failure occurred, it could jeopardize the quorum, even if the failed Nomad
+server had been automatically replaced. Autopilot helps prevent these kinds of
+outages by quickly removing failed servers as soon as a replacement Nomad server
+comes online. When servers are removed by the cleanup process they will enter
+the "left" state.
+
+This option can be disabled by running `nomad operator autopilot set-config`
+with the `-cleanup-dead-servers=false` option.
+
+## Server health checking
+
+An internal health check runs on the leader to monitor the stability of servers.
+A server is considered healthy if all of the following conditions are true:
+
+- Its status according to Serf is 'Alive'
+
+- The time since its last contact with the current leader is below
+  `LastContactThreshold`
+
+- Its latest Raft term matches the leader's term
+
+- The number of Raft log entries it trails the leader by does not exceed
+  `MaxTrailingLogs`
+
+The status of these health checks can be viewed through the
+[`/v1/operator/autopilot/health`] HTTP endpoint, with a top level `Healthy`
+field indicating the overall status of the cluster:
+
+```shell-session
+$ curl localhost:4646/v1/operator/autopilot/health
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 10,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-28T18:28:52Z"
+    },
+    {
+      "ID": "e35bde83-4e9c-434f-a6ef-453f44ee21ea",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "35.371007ms",
+      "LastTerm": 2,
+      "LastIndex": 10,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-28T18:29:10Z"
+    }
+  ]
+}
+
+```
+
+## Stable server introduction
+
+When a new server is added to the cluster, there is a waiting period where it
+must be healthy and stable for a certain amount of time before being promoted to
+a full, voting member. This can be configured via the `ServerStabilizationTime`
+setting.
+
+## Server read and scheduling scaling <EnterpriseAlert inline />
+
+With the [`non_voting_server`] option, a server can be explicitly marked as a
+non-voter and will never be promoted to a voting member. This can be useful when
+more read scaling is needed; being a non-voter means that the server will still
+have data replicated to it, but it will not be part of the quorum that the
+leader must wait for before committing log entries. Non voting servers can also
+act as scheduling workers to increase scheduling throughput in large clusters.
+
+## Redundancy zones <EnterpriseAlert inline />
+
+Prior to Autopilot, it was difficult to deploy servers in a way that took
+advantage of isolated failure domains such as AWS Availability Zones; users
+would be forced to either have an overly-large quorum (2-3 nodes per AZ) or give
+up redundancy within an AZ by deploying only one server in each.
+
+If the `EnableRedundancyZones` setting is set, Nomad will use its value to look
+for a zone in each server's specified [`redundancy_zone`] field.
+
+Here's an example showing how to configure this:
+
+```hcl
+/* config.hcl */
+server {
+  redundancy_zone = "west-1"
+}
+```
+
+```shell-session
+$ nomad operator autopilot set-config -enable-redundancy-zones=true
+Configuration updated!
+```
+
+Nomad will then use these values to partition the servers by redundancy zone,
+and will aim to keep one voting server per zone. Extra servers in each zone will
+stay as non-voters on standby to be promoted if the active voter leaves or dies.
+
+## Upgrade migrations <EnterpriseAlert inline />
+
+Autopilot in Nomad Enterprise supports upgrade migrations by default. To disable
+this functionality, set `DisableUpgradeMigration` to true.
+
+When a new server is added and Autopilot detects that its Nomad version is newer
+than that of the existing servers, Autopilot will avoid promoting the new server
+until enough newer-versioned servers have been added to the cluster. When the
+count of new servers equals or exceeds that of the old servers, Autopilot will
+begin promoting the new servers to voters and demoting the old servers. After
+this is finished, the old servers can be safely removed from the cluster.
+
+To check the Nomad version of the servers, either the [autopilot health]
+endpoint or the `nomad members`command can be used:
+
+```shell-session
+$ nomad server members
+Name   Address    Port  Status  Leader  Protocol  Build  Datacenter  Region
+node1  127.0.0.1  4648  alive   true    3         0.7.1  dc1         global
+node2  127.0.0.1  4748  alive   false   3         0.7.1  dc1         global
+node3  127.0.0.1  4848  alive   false   3         0.7.1  dc1         global
+node4  127.0.0.1  4948  alive   false   3         0.8.0  dc1         global
+```
+
+### Migrations without a Nomad version change
+
+The `EnableCustomUpgrades` field can be used to override the version information
+used during a migration, so that the migration logic can be used for updating
+the cluster when changing configuration.
+
+If the `EnableCustomUpgrades` setting is set to `true`, Nomad will use its value
+to look for a version in each server's specified [`upgrade_version`] tag. The
+upgrade logic will follow semantic versioning and the `upgrade_version` must be
+in the form of either `X`, `X.Y`, or `X.Y.Z`.
+
+[`/v1/operator/autopilot/configuration`]: /nomad/api-docs/operator/autopilot
+[`/v1/operator/autopilot/health`]: /nomad/api-docs/operator/autopilot#read-health
+[`non_voting_server`]: /nomad/docs/configuration/server#non_voting_server
+[`operator autopilot`]: /nomad/commands/operator
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot health]: /nomad/api-docs/operator/autopilot#read-health
+[autopilot settings]: /nomad/docs/configuration/autopilot
+[nomad enterprise]: https://www.hashicorp.com/products/nomad
+[server stanza]: /nomad/docs/configuration/server
+[version upgrade section]: /nomad/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility
diff --git a/content/nomad/v1.11.x/content/docs/manage/format-cli-output.mdx b/content/nomad/v1.11.x/content/docs/manage/format-cli-output.mdx
new file mode 100644
index 0000000000..0b99a8271e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/format-cli-output.mdx
@@ -0,0 +1,415 @@
+---
+layout: docs
+page_title: Format CLI output with templates
+description: |-
+  Customize the output of Nomad CLI commands with Go template syntax. Practice
+  interacting with unfamiliar template contexts.
+---
+
+# Format CLI output with templates
+
+When using Nomad at an intermediate to advanced level, you'll need to interface with other systems or customize output generated by Nomad. The `-t` flag is a powerful way to pass a template in Go's text/template format to
+several of the Nomad commands that generate output based on the API. This allows
+you to filter and customize the output to meet your specific needs.
+
+The commands that allow for the -t flag are:
+
+- `nomad acl policy list`
+- `nomad acl token list`
+- `nomad alloc status`
+- `nomad deployment list`
+- `nomad deployment status`
+- `nomad eval status`
+- `nomad job deployments`
+- `nomad job history`
+- `nomad job inspect`
+- `nomad namespace list`
+- `nomad node status`
+- `nomad plugin status`
+- `nomad quota list`
+- `nomad volume status`
+
+This guide will teach you how to explore the objects that are returned to
+the template engine and how to use template syntax to format the output into
+a custom form.
+
+## Prerequisites
+
+This guide assumes the following:
+
+- Familiarity with Go's text/template syntax. You can learn more about it in the
+  [Go template syntax][go-template-syntax] reference.
+
+- That you are running these commands against a Nomad cluster with an active
+  workload. You can create a minimal environment using a dev agent, started with
+  `sudo nomad agent -dev`, then running at least one Nomad job. You can use
+  `nomad init -short` to create a sample Docker job or provide your own Nomad
+  job.
+
+## Note the shell-specific syntax
+
+When using the -t flag, you need to correctly handle string literals based on
+your shell environment. In a POSIX shell, you can run the following with a
+single quote:
+
+```shell-session
+$ nomad node status  -t '{{printf "%#+v" .}}'
+```
+
+In a Windows shell (for example, PowerShell), use single
+quotes but escape the double quotes inside the parameter as follows:
+
+```powershell
+PS> nomad node status  -t '{{printf \"%#+v\" .}}'
+```
+
+In this guide, you can select examples with the proper escaping using the
+tabs above the snippets.
+
+## Start discovering objects
+
+The `printf` function and the `"%#+v"` format string are critical tools for you
+in exploring an unfamiliar template context.
+
+Run the following command to output the context being passed to the template
+in Go object format.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{printf "%#+v" .}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{printf \"%#+v\" .}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+[]*api.NodeListStub{(*api.NodeListStub)(0xc0003fa160), (*api.NodeListStub)(0xc0003fa0b0), (*api.NodeListStub)(0xc0003fa000)}
+```
+
+The output indicates that the context consists of a list (`[]`) of pointers
+(`*`) to `api.NodeListStub` objects. The list will also show one NodeListStub
+object per client node in your cluster's server state.
+
+You can explore these api.NodeListStub object by using the `range` control over
+the list.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{range .}}{{printf "%#+v" .}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{range .}}{{printf \"%#+v\" .}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+If you have a lot of client nodes in your cluster state, this output will be
+unwieldy. In that case, you can use `with` and the index function to get the
+first list item.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{with index . 0}}{{printf "%#+v" .}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{with index . 0}}{{printf \"%#+v\" .}}{{end}}'
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.NodeListStub{Address:"10.0.2.52", ID:"4f60bc83-71a2-7790-b120-4e55d0e6ed34", Datacenter:"dc1", Name:"nomad-client-2.node.consul", NodeClass:"", Version:"0.12.0", Drain:false, SchedulingEligibility:"eligible", Status:"ready", ...
+```
+
+Finally, output `Name` and `Version` for each client in the cluster.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad node status -t '{{range .}}{{printf "%s: %s\n" .Name .Version}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad node status -t '{{range .}}{{printf \"%s: %s\n\" .Name .Version}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+nomad-client-2.node.consul: 0.12.0
+nomad-client-3.node.consul: 0.12.0
+nomad-client-1.node.consul: 0.12.0
+```
+
+## Make quiet output
+
+Suppose you want to create a reduced version of the `nomad job status` output
+to show just the running job IDs in your cluster and nothing else.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad job inspect -t '{{range .}}{{if eq .Status "running"}}{{ println .Name}}{{end}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad job inspect -t '{{range .}}{{if eq .Status \"running\"}}{{ println .Name}}{{end}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+Nomad will output the job IDs for every running job in your cluster. For example:
+
+```plaintext
+fabio
+sockshop-carts
+sockshop-catalogue
+sockshop-frontend
+sockshop-infra
+sockshop-orders
+sockshop-payment
+sockshop-shipping
+sockshop-user
+```
+
+### Challenge yourself
+
+Allocations have a slightly different shape. How might you create similar output
+from the `nomad alloc status` command? Make sure that your Nomad cluster has at
+least one allocation running and then use the printf technique from earlier to
+explore the values sent into the template.
+
+<Accordion heading="View Solution" collapse="true">
+
+
+Print the context that you are passed from the command using the printf command.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{printf "%#+v" . }}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{printf \"%#+v\" . }}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+[]*api.AllocationListStub ...
+```
+
+Note that the first thing that you receive is a list (`[]`) of pointers (`*`) to
+`AllocationListStub` objects.
+
+Use `range` to traverse each item in the list.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{range .}}{{printf "%#+v" . }}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{range .}}{{printf \"%#+v\" . }}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.AllocationListStub{ID:"30663b68-4d8a-aada-4ad2-011b1acae3a1", EvalID:"c5eda90b-f675-048e-b2f7-9ced30e4916b", Name:"sockshop-user.userdb[0]", Namespace:"default", NodeID:"3be35c12-70aa-8816-195e-a4630a457727", NodeName:"nomad-client-3.node.consul", JobID:"sockshop-user", JobType:"service", JobVersion:0x0, ...
+```
+
+If you have a lot of allocations running, this could get unwieldy. In that case,
+you can use `with` and the index function to get the first list item.
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{with index . 0}}{{printf "%#+v" . }}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{with index . 0}}{{printf \"%#+v\" . }}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+&api.AllocationListStub{ID:"30663b68-4d8a-aada-4ad2-011b1acae3a1", EvalID:"c5eda90b-f675-048e-b2f7-9ced30e4916b", Name:"sockshop-user.userdb[0]", Namespace:"default", NodeID:"3be35c12-70aa-8816-195e-a4630a457727", NodeName:"nomad-client-3.node.consul", JobID:"sockshop-user", JobType:"service", JobVersion:0x0, ...
+```
+
+The fields on the AllocationListStub object that give insight into the running
+state of an allocation are `DesiredStatus` and `ClientStatus`.
+
+-> **Did you know?** The definition of an [AllocationListStub][] object and
+valid values for the DesiredStatus and ClientStatus are located in Nomad's
+[api package][]. Take a moment to look at it and see what other information you
+might be interested in displaying with templates.
+
+Update your template to show items with a DesiredStatus of "run" and a client
+status of "running" or "pending."
+
+<Tabs><Tab heading="Posix Shells" group="posix">
+
+
+```shell-session
+$ nomad alloc status -t '{{range .}}{{if and (eq .DesiredStatus "run") (or (eq .ClientStatus "running") (eq .ClientStatus "pending"))}}{{println .ID}}{{end}}{{end}}'
+```
+
+</Tab><Tab heading="PowerShell" group="ps">
+
+
+```powershell
+PS> nomad alloc status -t '{{range .}}{{if and (eq .DesiredStatus \"run\") (or (eq .ClientStatus \"running\") (eq .ClientStatus \"pending\"))}}{{println .ID}}{{end}}{{end}}'
+```
+
+</Tab></Tabs>
+
+
+```plaintext
+30663b68-4d8a-aada-4ad2-011b1acae3a1
+11b916da-d679-1718-26f3-f6cd499bfdb8
+68bcb157-359f-9293-d091-5a8ef71475ad
+...
+```
+
+You now have a list of the IDs for all of the allocations running in your Nomad
+cluster.
+
+</Accordion>
+
+
+## Retrieve a template from file
+
+Using the command line to write templates becomes challenging
+as the template becomes more complex.
+
+By writing a template in its own file, you can use comments, span multiple lines, and indent conditionals in order to make them more readable to you and to other operators.
+
+Consider using some of these techniques
+to include the template data into the command.
+
+<Tabs>
+<Tab heading="Posix Shells" group="posix">
+
+
+Create a file named running_jobs.tmpl with the following content.
+
+```plaintext
+{{- /*
+  Get Running Jobs
+  Run with `nomad job inspect -t "$(cat running_jobs.tmpl)"`
+*/ -}}
+{{- range . -}}
+  {{- if eq .Status "running" -}}
+    {{- println .Name -}}
+  {{- end -}}
+{{- end -}}
+```
+
+Now, use a subshell to read the file into a variable
+
+```shell-session
+$ nomad job inspect -t "$(cat running_jobs.tmpl)"
+```
+
+</Tab>
+<Tab heading="PowerShell" group="ps">
+
+
+Create a file named running_jobs.tmpl with the following content.
+
+```plaintext
+{{- /*
+  Get Running Jobs
+  Run with:
+    $content=Get-Content running_jobs.tmpl -Raw; nomad job inspect -t $content
+*/ -}}
+{{- range . -}}
+  {{- if eq .Status \"running\" -}}
+    {{- println .Name -}}
+  {{- end -}}
+{{- end -}}
+```
+
+Now, use a subshell to read the file into a variable
+
+```powershell
+PS> $content=Get-Content running_jobs.tmpl -Raw; nomad job inspect -t $content
+```
+
+</Tab>
+</Tabs>
+
+
+## Learn more
+
+In this guide, you learned how to:
+
+- Customize the output of several Nomad commands using Go's text/template
+  syntax.
+
+- Use the `printf` function to discover what is available in the template's
+  context.
+
+- Use a template definition contained in a file as part of the command.
+
+
+[go-template-syntax]: /nomad/docs/reference/go-template-syntax
+[allocationliststub]: https://godoc.org/github.com/hashicorp/nomad/api#AllocationListStub
+[api package]: https://godoc.org/github.com/hashicorp/nomad/api
diff --git a/content/nomad/v1.11.x/content/docs/manage/garbage-collection.mdx b/content/nomad/v1.11.x/content/docs/manage/garbage-collection.mdx
new file mode 100644
index 0000000000..68dc653da5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/garbage-collection.mdx
@@ -0,0 +1,225 @@
+---
+layout: docs
+page_title: Garbage collection
+description: |-
+  Nomad garbage collects Access Control List (ACL) tokens, allocations, deployments, encryption root keys, evaluations, jobs, nodes, plugins, and Container Storage Interface (CSI) volumes. Learn about server-side and client-side garbage collection processes, including configuration and triggers.
+---
+
+# Garbage collection
+
+Nomad garbage collection is not the same as garbage collection in a programming
+language, but the motivation behind its design is similar: garbage collection
+frees up memory allocated for objects that the schedular no longer references or
+needs. Nomad only garbage collects objects that are in a terminal state and only
+after a delay to allow inspection or debugging.
+
+Nomad runs garbage collection processes on servers and on client nodes. You may
+also manually trigger garbage collection on the server.
+
+Nomad garbage collects the following objects:
+
+- [ACL token](#configuration)
+- [Allocation](#client-side-garbage-collection)
+- [CSI Plugin](#configuration)
+- [Deployment](#configuration)
+- [Encryption root key](#configuration)
+- [Evaluation](#configuration)
+- [Job](#configuration)
+- [Node](#configuration)
+- [Volume](#configuration)
+
+## Cascading garbage collection
+
+Nomad's scheduled garbage collection processes generally handle each resource
+type independently. However, there is an implicit cascading relationship because
+of how objects reference each other. In practice, when Nomad garbage collects a
+higher-level object, Nomad also removes the object's associated sub-objects to
+prevent orphaned objects.
+
+For example, garbage collecting a job also causes Nomad to drop all of that
+job's remaining evaluations, deployments, and allocation records from the state.
+Nomad garbage collects those objects, either as part of the job garbage
+collection process or by each object's own garbage collection processes running
+immediately after. Nomad's scheduled garbage collection processes only garbage
+collect objects after they are terminal for at least the specified time
+threshold and no longer needed for future scheduling decisions. This also means
+that if a job is stopped it can't be garbage collected until its allocations are
+terminal. Note that when you force garbage collection by running the `nomad
+system gc` command, Nomad ignores the specified time threshold, but all
+other conditions still apply.
+
+## Server-side garbage collection
+
+The Nomad server leader starts periodic garbage collection processes that clean
+objects marked for garbage collection from memory. Nomad automatically marks
+some objects, like evaluations, for garbage collection. Alternatively, you may
+manually mark jobs for garbage collection by running `nomad system gc`, which
+runs the garbage collection process.
+
+### Configuration
+
+These settings govern garbage collection behavior on the server nodes. You may
+review the intervals in the [`config.go`
+class](https://github.com/hashicorp/nomad/blob/b11619010e1c83488e14e2785569e515b2769062/nomad/config.go#L564)
+for objects without a configurable interval setting.
+
+| Object | Interval | Threshold |
+|---|---|---|
+| **ACL token** | 5 minutes | [`acl_token_gc_threshold`](/nomad/docs/configuration/server#acl_token_gc_threshold)<br/>Default: 1 hour |
+| **CSI Plugin** | 5 minutes | [`csi_plugin_gc_threshold`](/nomad/docs/configuration/server#csi_plugin_gc_threshold)<br/>Default: 1 hour |
+| **Deployment** | 5 minutes | [`deployment_gc_threshold`](/nomad/docs/configuration/server#deployment_gc_threshold)<br/>Default: 1 hour |
+| **Encryption root key** | [`root_key_gc_interval`](/nomad/docs/configuration/server#root_key_gc_interval)<br/>Default: 10 minutes | [`root_key_gc_threshold`](/nomad/docs/configuration/server#root_key_gc_threshold)<br/>Default: 1 hour  |
+| **Evaluation** | 5 minutes | [`eval_gc_threshold`](/nomad/docs/configuration/server#eval_gc_threshold) <br/>Default: 1 hour |
+| **Evaluation, batch** |  5 minutes | [`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)<br/>Default: 24 hours |
+| **Job** | [`job_gc_interval`](/nomad/docs/configuration/server#job_gc_interval)<br/>Default: 5 minutes | [`job_gc_threshold`](/nomad/docs/configuration/server#job_gc_threshold)<br/>Default: 4 hours |
+| **Node** | 5 minutes | [`node_gc_threshold`](/nomad/docs/configuration/server#node_gc_threshold)<br/>Default: 24 hours |
+| **Volume** | [`csi_volume_claim_gc_interval`](/nomad/docs/configuration/server#csi_volume_claim_gc_interval)<br/>Default: 5 minutes| [`csi_volume_claim_gc_threshold`](/nomad/docs/configuration/server#csi_volume_claim_gc_threshold)<br/>Default: 1 hour |
+
+Allocations do not have an independent threshold configuration. Because
+specific evaluations create allocations, Nomad garbage collects allocations
+when garbage collecting their evaluations. This also means that Nomad
+cannot garbage collect evaluations until their allocations are terminal.
+
+### Triggers
+
+The server garbage collection processes wake up at configured intervals to scan
+for any expired or terminal objects to permanently delete, provided the object's
+time in a terminal state exceeds its garbage collection threshold. For example,
+a job's default garbage collection threshold is four hours, so the job must be
+in a terminal state for at least four hours before the garbage collection
+process permanently deletes the job and its dependent objects.
+
+When you force garbage collection by manually running the `nomad system gc`
+command, you are telling the garbage collection process to ignore thresholds and
+immediately purge all terminal objects on all servers and clients.
+
+## Client-side garbage collection
+
+On each client node, Nomad must clean up resources from terminated allocations
+to free disk and memory on the machine.
+
+### Configuration
+
+These settings govern allocation garbage collection behavior on each client node.
+
+| Parameter | Default | Description  |
+| -------- | ------- | ------------- |
+| [`gc_interval`](/nomad/docs/configuration/client#gc_interval)  | 1 minute | Interval at which Nomad attempts to garbage collect terminal allocation directories |
+| [ `gc_disk_usage_threshold` ](/nomad/docs/configuration/client#gc_disk_usage_threshold)  | 80 | Disk usage percent which Nomad tries to maintain by garbage collecting terminal allocations |
+| [ `gc_inode_usage_threshold` ](/nomad/docs/configuration/client#gc_inode_usage_threshold) | 70 | Inode usage percent which Nomad tries to maintain by garbage collecting terminal allocations |
+| [ `gc_max_allocs` ](/nomad/docs/configuration/client#gc_max_allocs) | 50 | Maximum number of allocations which a client will track before triggering a garbage collection of terminal allocations |
+| [ `gc_parallel_destroys ` ](/nomad/docs/configuration/client#gc_parallel_destroys) | 2 | Maximum number of parallel destroys allowed by the garbage collector |
+
+Refer to the [client block in agent configuration
+reference](/nomad/docs/configuration/client) for complete parameter descriptions
+and examples.
+
+Note that there is no time-based retention setting for allocations on the
+client. As soon as an allocation is terminal, it becomes eligible for cleanup if
+the configured thresholds demand it or if the allocation is garbage collected on
+the server.
+
+### Triggers
+
+Nomad's client runs allocation garbage collection based on these triggers:
+
+- Scheduled interval
+
+  The garbage collection process launches a ticker based on the configured
+  `gc_interval`. On each tick, the garbage collection process checks to see if
+  it needs to remove terminal allocations.
+
+- Terminal state
+
+  When an allocation transitions to a terminal state, Nomad marks the allocation
+  for garbage collection and then signals the garbage collection process to run
+  immediately. As with the scheduled interval, this may be a no-op if the
+  thresholds have not been reached.
+
+- Allocation placement
+
+  Nomad may preemptively run garbage collection to make room for new
+  allocations. The client garbage collects older, terminal allocations if adding
+  new allocations would exceed the `gc_max_allocs` limit.
+
+- Server garbage collection
+
+  When the server garbage collects an allocation or you force garbage collection
+  by running the `nomad system gc` command, the garbage collection process
+  removes all terminal objects on all servers and clients, ignoring all
+  threshold settings cluster-wide.
+
+Nomad does not continuously monitor disk or inode usage to trigger garbage
+collection. Instead, Nomad only checks disk and inode thresholds when one of the
+aforementioned triggers invokes the garbage collection process. The
+`gc_inode_usage_threshold` and `gc_disk_usage_threshold` values do not trigger
+garbage collection; rather, those values influence how the garbage collector
+behaves during a collection run.
+
+### Allocation selection
+
+When the garbage collection process runs, Nomad destroys as many finished
+allocations as needed to meet the resource thresholds. The client maintains a
+priority queue of terminal allocations ordered by the time they were marked
+finished, oldest first.
+
+The process repeatedly evicts allocations from the queue until the conditions
+are back within configured limits. Specifically, the garbage collection loop
+checks, in order:
+
+1. If disk usage exceeds `gc_disk_usage_threshold` value
+1. If inode usage exceeds `gc_inode_usage_threshold` value
+1. If the count of allocations exceeds `gc_max_allocs` value
+
+If any one of these conditions is true, the garbage collector selects the oldest
+finished allocation for removal.
+
+After deleting one allocation, the loop re-checks the metrics and continues
+removing the next-oldest allocation until all thresholds are satisfied or
+until there are no more terminal allocs. This means in a single run, the
+garbage collection removes multiple allocations back-to-back if the node was
+far over the limits. The evictions happen in termination-time order, which is
+oldest completed allocations first.
+
+If node's usage and allocation count are under the limits, a normal garbage
+collection cycle does not remove any allocations. In other words, periodic and
+event-driven garbage collection does not delete allocations just because they
+are finished. There has to be pressure or a limit reached. The exception is when
+an administrative command or server-side removal triggers client-side garbage
+collection. Aside from that forced scenario, the default behavior is
+threshold-driven: Nomad leaves allocations on disk until it needs to reclaim
+those allocations due to space, inode, or count limits being hit.
+
+### Task driver resources garbage collection
+
+Most task drivers do not have their own garbage collection process. When an
+allocation is terminal, the client garbage collection process communicates with
+the task driver to ensure the task's resources have been cleaned up. Note that
+the Docker task driver periodically cleans up its own resources. Refer to the
+[Docker task driver plugin
+options](https://developer.hashicorp.com/nomad/docs/deploy/task-driver/docker#gc) for
+details.
+
+When a task has configured restart attempts and the task fails, the Nomad client
+attempts an in-place task restart within the same allocation. The task driver
+starts a new process or container for the task. If the task continues to fail
+and exceeds the configured restart attempts, Nomad terminates the task and marks
+the allocation as terminal. The task driver then cleans up its resources, such
+as a Docker container or cgroups. When the garbage collection process runs, it
+makes sure that the task driver cleanup is done before deleting the allocation.
+If a task driver fails to clean up properly, Nomad logs errors but continues the
+garbage collection process. Task driver cleanup failure issues can influence
+when the allocation truly frees up. For instance, if volumes are not detached,
+disk space might not be fully reclaimed until fixed.
+
+## Resources
+
+- [Nomad's internal garbage collection and optimization discovery during the
+  Nomad Bench project blog post](https://www.hashicorp.com/en/blog/nomad-garbage-collection-optimization-discovery-during-nomad-bench)
+- Configuration
+
+  - [client Block in Agent Configuration](/nomad/docs/configuration/client)
+  - [server Block in Agent Configuration](/nomad/docs/configuration/server)
+
+- [the `nomad system gc` command reference](/nomad/commands/system/gc)
+- [System HTTP API Force GC](/nomad/api-docs/system#force-gc)
diff --git a/content/nomad/v1.11.x/content/docs/manage/index.mdx b/content/nomad/v1.11.x/content/docs/manage/index.mdx
new file mode 100644
index 0000000000..ea2ddaf4c9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/index.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Manage Nomad
+description: |-
+  This section provides guidance on the operational management of Nomad. Topics include garbage collection, key management, workload migration, outage recovery, enabling Autopilot, formatting command output, and using namespaces.
+---
+
+# Manage Nomad
+
+This section provides guidance on the operational management of Nomad. Topics include garbage collection, key management, workload migration, outage recovery, enabling Autopilot, formatting command output, and using namespaces.
diff --git a/content/nomad/v1.11.x/content/docs/manage/key-management.mdx b/content/nomad/v1.11.x/content/docs/manage/key-management.mdx
new file mode 100644
index 0000000000..25704c5134
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/key-management.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Key management
+description: |-
+  Learn how Nomad manages its keyring, which Nomad uses to encrypt variables, sign task workload identities, and sign OpenID Connect (OIDC) client assertions. Review key rotation, key decryption, and key redaction in Raft snapshots. Learn how Nomad v1.9+ can replicate keys from older Nomad versions.
+---
+
+# Key management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][],
+sign task [workload identities][], and sign OIDC [client assertion JWTs][].
+The servers encrypt these data encryption keys (DEK) and store the wrapped keys
+in Raft.
+
+The key encryption key (KEK) used to encrypt the DEK is controlled by the
+[`keyring`][] provider. When using an external KMS or Vault transit encryption
+provider, the KEK is securely stored outside of Nomad. For the default AEAD
+provider, the KEK is stored in cleartext in Raft.
+
+<Note>
+
+Default AEAD provider users should be aware that storing the Key Encryption Key
+(KEK) in cleartext in Raft may expose data in case of a breach.
+
+</Note>
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key decryption
+
+When a leader is elected, the leader creates the keyring if it does not already
+exist. When a key is added, the new wrapped key material is replicated via
+Raft. As each server replicates the new key, the server starts a task to decrypt
+the key material. Until this task completes, the server is not able to serve
+requests that require this key.
+
+## Key redaction in Raft scenario snapshots
+
+The default AEAD `keyring` configuration stores the KEK in Raft. Raft snapshots
+contain the cleartext KEK. The `nomad operator snapshot save` command has a
+`-redact` option that removes the key material when creating a snapshot. The
+`nomad operator snapshot redact` command removes key material from an
+existing snapshot.
+
+Redacting key material is not required when using an external KMS.
+
+## Legacy keystore
+
+Versions of Nomad prior to 1.9.0 stored only key metadata in Raft, but the
+encryption key material was stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Each server runs a key replication process that watches for changes to the state
+store and fetches the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election. Nomad 1.9.0 and above can replicate keys
+from older servers.
+
+However, replicating keys from older servers means that to restore an older cluster from snapshot you need to
+also provide the keystore directory with the `.nks.json` key files on at least
+one server. The `.nks.json` key files are unique per server, but only one
+server's key files are needed to recover the cluster. Operators should continue
+to include these files as part of your organization's backup and recovery
+strategy for the cluster until the cluster is fully upgraded to Nomad 1.9.0 and
+at least one [`root_key_gc_interval`][] has passed.
+
+If you are recovering an older Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[client assertion JWTs]: /nomad/docs/secure/authentication/oidc#client-assertions
+[data directory]: /nomad/docs/configuration#data_dir
+[`keyring`]: /nomad/docs/configuration/keyring
+[`nomad operator root keyring rotate -full`]: /nomad/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/commands/operator/root/keyring-rotate
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.11.x/content/docs/manage/migrate-workloads.mdx b/content/nomad/v1.11.x/content/docs/manage/migrate-workloads.mdx
new file mode 100644
index 0000000000..041595a6ee
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/migrate-workloads.mdx
@@ -0,0 +1,361 @@
+---
+layout: docs
+page_title: Migrate workloads
+description: |-
+  Configure jobs to allow Nomad to migrate workloads during events like node
+  drains. Discover how to customize migration configuration for your
+  applications.
+---
+
+# Migrate workloads
+
+Migrating workloads and decommissioning nodes are a normal part of cluster
+operations for a variety of reasons: server maintenance, operating system
+upgrades, etc. Nomad offers a number of parameters for controlling how running
+jobs are migrated off of draining nodes.
+
+## Define how your job is migrated
+
+In Nomad 0.8, a [`migrate`][migrate] stanza was added to jobs to allow control
+over how allocations for a job are migrated off of a draining node. Below is an
+example job that runs a web service and has a Consul health check:
+
+```hcl
+job "webapp" {
+  datacenters = ["dc1"]
+
+  migrate {
+    max_parallel = 2
+    health_check = "checks"
+    min_healthy_time = "15s"
+    healthy_deadline = "5m"
+  }
+
+  group "webapp" {
+    count = 9
+
+    network {
+      port "http" {
+        to = 5678
+      }
+    }
+
+    task "webapp" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo:0.2.3"
+        args  = ["-text", "ok"]
+        ports = ["http"]
+      }
+
+      service {
+        name = "webapp"
+        port = "http"
+        check {
+          name = "http-ok"
+          type = "http"
+          path = "/"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+The above `migrate` stanza ensures only 2 allocations are stopped at a time to
+migrate during node drains. Even if multiple nodes running allocations for this
+job were draining at the same time, only 2 allocations would be migrated at a
+time.
+
+When the job is run it may be placed on multiple nodes. In the following
+example the 9 `webapp` allocations are spread across 2 nodes:
+
+```shell-session
+$ nomad run webapp.nomad.hcl
+==> Monitoring evaluation "5129bc74"
+    Evaluation triggered by job "webapp"
+    Allocation "5b4d6db5" created: node "46f1c6c4", group "webapp"
+    Allocation "670a715f" created: node "f7476465", group "webapp"
+    Allocation "78b6b393" created: node "46f1c6c4", group "webapp"
+    Allocation "85743ff5" created: node "f7476465", group "webapp"
+    Allocation "edf71a5d" created: node "f7476465", group "webapp"
+    Allocation "56f770c0" created: node "46f1c6c4", group "webapp"
+    Allocation "9a51a484" created: node "46f1c6c4", group "webapp"
+    Allocation "f6f6e64c" created: node "f7476465", group "webapp"
+    Allocation "fefe81d0" created: node "f7476465", group "webapp"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5129bc74" finished with status "complete"
+```
+
+If one those nodes needed to be decommissioned, perhaps because of a hardware
+issue, then an operator would issue node drain to migrate the allocations off:
+
+```shell-session
+$ nomad node drain -enable -yes 46f1
+2018-04-11T23:41:56Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-04-11T23:41:56Z: Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" drain strategy set
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" draining
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" draining
+2018-04-11T23:42:03Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" status running -> complete
+2018-04-11T23:42:03Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" status running -> complete
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" marked for migration
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" draining
+2018-04-11T23:42:27Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" status running -> complete
+2018-04-11T23:42:29Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" marked for migration
+2018-04-11T23:42:29Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" draining
+2018-04-11T23:42:29Z: Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" has marked all allocations for migration
+2018-04-11T23:42:34Z: Alloc "9a51a484-8c43-aa4e-d60a-46cfd1450780" status running -> complete
+2018-04-11T23:42:34Z: All allocations on node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" have stopped.
+```
+
+There are a couple of important events to notice in the output. First, only two
+allocations are migrated initially:
+
+```plaintext
+2018-04-11T23:41:57Z: Alloc "5b4d6db5-3fcb-eb7d-0415-23eefcd78b6a" marked for migration
+2018-04-11T23:41:57Z: Alloc "56f770c0-f8aa-4565-086d-01faa977f82d" marked for migration
+```
+
+This is because `max_parallel = 2` in the job specification. The next
+allocation on the draining node waits to be migrated:
+
+```plaintext
+2018-04-11T23:42:22Z: Alloc "78b6b393-d29c-d8f8-e8e8-28931c0013ee" marked for migration
+```
+
+Note that this occurs 25 seconds after the initial migrations. The 25 second
+delay is because a replacement allocation took 10 seconds to become healthy and
+then the `min_healthy_time = "15s"` meant node draining waited an additional 15
+seconds. If the replacement allocation had failed within that time the node
+drain would not have continued until a replacement could be successfully made.
+
+### Verify drained node's scheduling eligibility
+
+Now that the example drain has finished you can inspect the state of the drained
+node:
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  eligible     ready
+96b52ad8  dc1  nomad-2  <none>  false  eligible     ready
+46f1c6c4  dc1  nomad-3  <none>  false  ineligible   ready
+```
+
+While node `46f1c6c4` has `Drain = false`, notice that its `Eligibility = ineligible`. Node scheduling eligibility is a new field in Nomad 0.8. When a
+node is ineligible for scheduling the scheduler will not consider it for new
+placements.
+
+While draining, a node will always be ineligible for scheduling. Once draining
+completes it will remain ineligible to prevent refilling a newly drained node.
+
+However, by default canceling a drain with the `-disable` option will reset a
+node to be eligible for scheduling. To cancel a drain and preserving the node's
+ineligible status use the `-keep-ineligible` option.
+
+Scheduling eligibility can be toggled independently of node drains by using the
+[`nomad node eligibility`][eligibility] command:
+
+```shell-session
+$ nomad node eligibility -disable 46f1
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+```
+
+### Use a drain deadline to force completion
+
+Sometimes a drain is unable to proceed and complete normally. This could be
+caused by not enough capacity existing in the cluster to replace the drained
+allocations or by replacement allocations failing to start successfully in a
+timely fashion.
+
+Operators may specify a deadline when enabling a node drain to prevent drains
+from not finishing. Once the deadline is reached, all remaining allocations on
+the node are stopped regardless of `migrate` stanza parameters.
+
+The default deadline is 1 hour and may be changed with the
+[`-deadline`][deadline] command line option. The [`-force`][force] option is an
+instant deadline: all allocations are immediately stopped. The
+[`-no-deadline`][no-deadline] option disables the deadline so a drain may
+continue indefinitely.
+
+Like all other drain parameters, a drain's deadline can be updated by making
+subsequent `nomad node drain ...` calls with updated values.
+
+## Plan a drain strategy for batch and system jobs
+
+So far you have only seen how draining works with service jobs. Both batch and
+system jobs are have different behaviors during node drains.
+
+### Drain batch jobs
+
+Node drains only migrate batch jobs once the drain's deadline has been reached.
+For node drains without a deadline the drain will not complete until all batch
+jobs on the node have completed (or failed).
+
+The goal of this behavior is to avoid losing progress a batch job has made by
+forcing it to exit early.
+
+### Keep system jobs running
+
+Node drains only stop system jobs once all other allocations have exited. This
+way if a node is running a log shipping daemon or metrics collector as a system
+job, it will continue to run as long as there are other allocations running.
+
+The [`-ignore-system`][ignore-system] option leaves system jobs running even
+after all other allocations have exited. This is useful when system jobs are
+used to monitor Nomad or the node itself.
+
+## Drain multiple nodes
+
+A common operation is to decommission an entire class of nodes at once. Prior
+to Nomad 0.7 this was a problematic operation as the first node to begin
+draining may migrate all of their allocations to the next node about to be
+drained. In pathological cases this could repeat on each node to be drained and
+cause allocations to be rescheduled repeatedly.
+
+As of Nomad 0.8 an operator can avoid this churn by marking nodes ineligible
+for scheduling before draining them using the [`nomad node eligibility`][eligibility] command.
+
+Mark a node as ineligible for scheduling with the `-disable` flag.
+
+```shell-session
+$ nomad node eligibility -disable 46f1
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+```
+
+```shell-session
+$ nomad node eligibility -disable 96b5
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Check node status to confirm eligibility.
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  eligible     ready
+46f1c6c4  dc1  nomad-2  <none>  false  ineligible   ready
+96b52ad8  dc1  nomad-3  <none>  false  ineligible   ready
+```
+
+Now that both `nomad-2` and `nomad-3` are ineligible for scheduling, they can
+be drained without risking placing allocations on an _about-to-be-drained_
+node.
+
+Toggling scheduling eligibility can be done totally independently of draining.
+For example when an operator wants to inspect the allocations currently running
+on a node without risking new allocations being scheduled and changing the
+node's state.
+
+Make current node ineligible for scheduling.
+
+```shell-session
+$ nomad node eligibility -self -disable
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Make current node eligible for scheduling again with the `-enable` flag.
+
+```shell-session
+$ nomad node eligibility -self -enable
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: eligible for scheduling
+```
+
+### Example: migrating datacenters
+
+A more complete example of draining multiple nodes would be when migrating from
+an old datacenter (`dc1`) to a new datacenter (`dc2`):
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name     Class   Drain  Eligibility  Status  Running Allocs
+f7476465  dc1  nomad-1  <none>  false  eligible     ready   4
+46f1c6c4  dc1  nomad-2  <none>  false  eligible     ready   1
+96b52ad8  dc1  nomad-3  <none>  false  eligible     ready   4
+168bdd03  dc2  nomad-4  <none>  false  eligible     ready   0
+9ccb3306  dc2  nomad-5  <none>  false  eligible     ready   0
+7a7f9a37  dc2  nomad-6  <none>  false  eligible     ready   0
+```
+
+Before migrating ensure that all jobs in `dc1` have `datacenters = ["dc1", "dc2"]`. Then before draining, mark all nodes in `dc1` as ineligible for
+scheduling.
+
+Shell scripting can help automate manipulating multiple nodes at once.
+
+```shell-session
+$ nomad node status | awk '{ print $2 " " $1 }' | grep ^dc1 | awk '{ system("nomad node eligibility -disable "$2) }'
+Node "f7476465-4d6e-c0de-26d0-e383c49be941" scheduling eligibility set: ineligible for scheduling
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" scheduling eligibility set: ineligible for scheduling
+Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" scheduling eligibility set: ineligible for scheduling
+```
+
+Check status to confirm ineligibility.
+
+```shell-session
+$ nomad node status
+ID        DC   Name     Class   Drain  Eligibility  Status
+f7476465  dc1  nomad-1  <none>  false  ineligible   ready
+46f1c6c4  dc1  nomad-2  <none>  false  ineligible   ready
+96b52ad8  dc1  nomad-3  <none>  false  ineligible   ready
+168bdd03  dc2  nomad-4  <none>  false  eligible     ready
+9ccb3306  dc2  nomad-5  <none>  false  eligible     ready
+7a7f9a37  dc2  nomad-6  <none>  false  eligible     ready
+```
+
+Then drain each node in `dc1`.
+
+```shell-session
+$ nomad node drain -enable -yes -detach f7476465
+Node "f7476465-4d6e-c0de-26d0-e383c49be941" drain strategy set
+```
+
+Pass the ID for each node with the flags ``-enable -yes -detach` to initiate the drain.
+
+```shell-session
+$ nomad node drain -enable -yes -detach 46f1c6c4
+Node "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806" drain strategy set
+```
+
+For this example, only monitor the final node that is draining. Watching `nomad node status -allocs`
+is also a good way to monitor the status of drains.
+
+```shell-session
+$ nomad node drain -enable -yes 9ccb3306
+2018-04-12T22:08:00Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-04-12T22:08:00Z: Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" drain strategy set
+2018-04-12T22:08:15Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" marked for migration
+2018-04-12T22:08:16Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" draining
+2018-04-12T22:08:17Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" marked for migration
+2018-04-12T22:08:17Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" draining
+2018-04-12T22:08:21Z: Alloc "392ee2ec-d517-c170-e7b1-d93b2d44642c" status running -> complete
+2018-04-12T22:08:22Z: Alloc "6a833b3b-c062-1f5e-8dc2-8b6af18a5b94" status running -> complete
+2018-04-12T22:09:08Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" marked for migration
+2018-04-12T22:09:09Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" draining
+2018-04-12T22:09:14Z: Alloc "d572d7a3-024b-fcb7-128b-1932a49c8d79" status running -> complete
+2018-04-12T22:09:33Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" marked for migration
+2018-04-12T22:09:33Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" draining
+2018-04-12T22:09:33Z: Node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" has marked all allocations for migration
+2018-04-12T22:09:39Z: Alloc "f3f24277-4435-56a3-7ee1-1b1eff5e3aa1" status running -> complete
+2018-04-12T22:09:39Z: All allocations on node "96b52ad8-e9ad-1084-c14f-0e11f10772e4" have stopped.
+```
+
+Note that there was a 15 second delay between node `96b52ad8` starting to drain
+and having its first allocation migrated. The delay was due to 2 other
+allocations for the same job already being migrated from the other nodes. Once
+at least 8 out of the 9 allocations are running for the job, another allocation
+could begin draining.
+
+The final node drain command did not exit until 6 seconds after the `drain complete` message because the command line tool blocks until all allocations on
+the node have stopped. This allows operators to script shutting down a node
+once a drain command exits and know all services have already exited.
+
+[deadline]: /nomad/commands/node/drain#deadline
+[eligibility]: /nomad/commands/node/eligibility
+[force]: /nomad/commands/node/drain#force
+[ignore-system]: /nomad/commands/node/drain#ignore-system
+[migrate]: /nomad/docs/job-specification/migrate
+[no-deadline]: /nomad/commands/node/drain#no-deadline
diff --git a/content/nomad/v1.11.x/content/docs/manage/outage-recovery.mdx b/content/nomad/v1.11.x/content/docs/manage/outage-recovery.mdx
new file mode 100644
index 0000000000..8f537382b2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/outage-recovery.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: Recover from an outage
+description: |-
+  Discover techniques and steps to recover from a single node failure,
+  multi-node failure, or a complete loss of quorum.
+---
+
+# Recover from an outage
+
+Don't panic. This is a critical first step.
+
+Depending on your [deployment configuration], it may take only a single server
+failure for cluster unavailability. Recovery requires an operator to intervene,
+but the process is straightforward.
+
+~> This guide is for recovery from a Nomad outage due to a majority of server
+nodes in a datacenter being lost. If you are looking to add or remove servers,
+consult the [bootstrapping guide].
+
+## Failure of a single server cluster
+
+If you had only a single server and it has failed, try to restore operation by
+restarting it. A single server configuration requires the
+[`-bootstrap-expect=1`] flag. If the server cannot be recovered, you need to
+bring up a new server. Consult the [bootstrapping guide] for more detail.
+
+In the case of an unrecoverable server failure in a single server cluster, data
+loss is inevitable since data was not replicated to any other servers. This is
+why a single server deploy is **never** recommended.
+
+## Failure of a server in a multi-server cluster
+
+If you think the failed server is recoverable, the easiest option is to bring it
+back online and have it rejoin the cluster with the same IP address. This will
+return the cluster to a fully healthy state. Similarly, even if you need to
+rebuild a new Nomad server to replace the failed node, you may wish to do that
+immediately. Keep in mind that the rebuilt server needs to have the same IP
+address as the failed server. Again, once this server is online and has
+rejoined, the cluster will return to a fully healthy state.
+
+Both of these strategies involve a potentially lengthy time to reboot or rebuild
+a failed server. If this is impractical or if building a new server with the
+same IP isn't an option, you need to remove the failed server. Usually, you can
+issue a [`nomad server force-leave`] command to remove the failed server if it
+is still a member of the cluster.
+
+<Note>
+
+ Your raft cluster will need to have a quorum of nodes available to
+perform any online modifications to the Raft peer information. Membership
+changes are written to the Raft log, and all Raft log writes require quorum.
+If this is impossible, continue to **Failure of Multiple Servers in a
+Multi-Server Cluster**
+
+</Note>
+
+If, for some reason, the Raft configuration continues to show any stale members,
+you can use the [`nomad operator raft remove-peer`] command to remove the stale
+peer server on the fly with no downtime.
+
+Once you have made the membership changes necessary, you should verify the
+current Raft state with the [`nomad operator raft list-peers`] command:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+## Failure of multiple servers in a multi-server cluster
+
+In the event that multiple servers are lost, causing a loss of quorum and a
+complete outage, partial recovery is possible using data on the remaining
+servers in the cluster. There may be data loss in this situation because
+multiple servers were lost, so information about what's committed could be
+incomplete. The recovery process implicitly commits all outstanding Raft log
+entries, so it's also possible to commit data that was uncommitted before the
+failure.
+
+The [section below][] contains the details of the recovery procedure. You will
+include the remaining servers in the `raft/peers.json` recovery file. The
+cluster should be able to elect a leader once the remaining servers are all
+restarted with an identical `raft/peers.json` configuration.
+
+Any new servers you introduce later can be fresh with totally clean data
+directories and joined using Nomad's `server join` command.
+
+In extreme cases, it should be possible to recover with only a single remaining
+server by starting that single server with itself as the only peer in the
+`raft/peers.json` recovery file.
+
+The `raft/peers.json` recovery file is final, and a snapshot is taken after it
+is ingested, so you are guaranteed to start with your recovered configuration.
+This does implicitly commit all Raft log entries, so should only be used to
+recover from an outage, but it should allow recovery from any situation where
+there's some cluster data available.
+
+## Manual recovery using peers.json
+
+To begin, stop all remaining servers. You can attempt a graceful leave, but it
+will not work in most cases. Do not worry if the leave exits with an error. The
+cluster is in an unhealthy state, so this is expected.
+
+The `peers.json` file is not present by default and is only used when performing
+recovery. This file will be deleted after Nomad starts and ingests this file.
+
+Nomad automatically creates a `raft/peers.info` file on startup to mark that it
+is on the current version of Raft. Do not remove the `raft/peers.info`
+file at any time.
+
+Using `raft/peers.json` for recovery can cause uncommitted Raft log entries to
+be implicitly committed, so this should only be used after an outage where no
+other option is available to recover a lost server. Make sure you don't have any
+automated processes that will put the peers file in place on a periodic basis.
+
+The next step is to go to the [`-data-dir`][] of each Nomad server. Inside that
+directory, there will be a `raft/` sub-directory. Create a `raft/peers.json`
+file. Its contents will depend on the raft protocol version of your cluster.
+
+### Raft protocol 3 peers.json specification
+
+```json
+[
+  {
+    "id": "adf4238a-882b-9ddc-4a9d-5b6758e4159e",
+    "address": "10.1.0.1:4647",
+    "non_voter": false
+  },
+  {
+    "id": "8b6dda82-3103-11e7-93ae-92361f002671",
+    "address": "10.1.0.2:4647",
+    "non_voter": false
+  },
+  {
+    "id": "97e17742-3103-11e7-93ae-92361f002671",
+    "address": "10.1.0.3:4647",
+    "non_voter": false
+  }
+]
+```
+
+- `id` `(string: **required**)` - Specifies the `node ID` of the server. This
+  can be found in the logs when the server starts up, and it can also be found
+  inside the `node-id` file in the server's data directory.
+
+- `address` `(string: **required**)` - Specifies the IP and port of the server
+  in `ip:port` format. The port is the server's RPC port used for cluster
+  communications, typically 4647.
+
+- `non_voter` `(bool: _false_)` - This controls whether the server is a
+  non-voter, which is used in some advanced [Autopilot] configurations. If
+  omitted, it will default to false, which is typical for most clusters.
+
+You can use this `jq` filter to create a `peers.json` file with the list of `alive` servers. Check the generated output and make any necessary changes.
+
+```shell
+$ nomad server members -json | jq '[ .[] | select(.Status == "alive") | {id: .Tags.id, address: "\(.Tags.rpc_addr):\(.Tags.port)", non_voter: false} ]'
+```
+
+### Raft protocol 2 peers.json specification
+
+```json
+["10.0.1.8:4647", "10.0.1.6:4647", "10.0.1.7:4647"]
+```
+
+Raft protocol version 2 peers.json files contain a list of IP:Port addresses for
+each server. Note that the port should refer to the RPC port and not the HTTP
+API port.
+
+### Deploy peers.json to all server nodes
+
+Create entries for all remaining servers. You must confirm that servers you do
+not include here have indeed failed and will not later rejoin the cluster.
+
+Deploy this file is the same across all remaining server nodes.
+
+### Verify keyring on server nodes
+
+<Warning>
+
+Prior to Nomad 1.9.0, [key material][Key material] was never stored in Raft. This meant that
+the `nomad agent snapshot save` command and snapshot agent did not save Nomad's
+keyring. If you are using versions prior to Nomad 1.9.0, you should make sure you have backed up the keyring of at least one
+server.
+
+</Warning>
+
+Go to the [`-data-dir`][] of each Nomad server. Inside that directory, there
+will be a `keystore/` sub-directory with `.nks.json` files. Ensure that these
+files exist on at least one server before continuing.
+
+### Restart cluster nodes
+
+At this point, you can restart all the remaining servers. Log lines will be
+emitted as the servers ingest the recovery file:
+
+```plaintext
+...
+2016/08/16 14:39:20 [INFO] nomad: found peers.json file, recovering Raft configuration...
+2016/08/16 14:39:20 [INFO] nomad.fsm: snapshot created in 12.484µs
+2016/08/16 14:39:20 [INFO] snapshot: Creating new snapshot at /tmp/peers/raft/snapshots/2-5-1471383560779.tmp
+2016/08/16 14:39:20 [INFO] nomad: deleted peers.json file after successful recovery
+2016/08/16 14:39:20 [INFO] raft: Restored from snapshot 2-5-1471383560779
+2016/08/16 14:39:20 [INFO] raft: Initial configuration (index=1): [{Suffrage:Voter ID:10.212.15.121:4647 Address:10.212.15.121:4647}]
+...
+```
+
+If any servers managed to perform a graceful leave, you may need to have them
+rejoin the cluster using the [`server join`] command:
+
+```shell-session
+$ nomad server join <Node Address>
+Successfully joined cluster by contacting 1 nodes.
+```
+
+It should be noted that any existing member can be used to rejoin the cluster as
+the gossip protocol will take care of discovering the server nodes.
+
+At this point, the cluster should be in an operable state again. One of the
+nodes should claim leadership and emit a log like:
+
+```plaintext
+[INFO] nomad: cluster leadership acquired
+```
+
+You can use the [`nomad operator raft list-peers`] command to inspect the Raft
+configuration:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+[`-bootstrap-expect=1`]: /nomad/docs/configuration/server#bootstrap_expect
+[`-data-dir`]: /nomad/docs/configuration#data_dir
+[`nomad operator raft list-peers`]: /nomad/commands/operator/raft/list-peers
+[`nomad operator raft remove-peer`]: /nomad/commands/operator/raft/remove-peer
+[`nomad server force-leave`]: /nomad/commands/server/force-leave
+[`nomad server force-leave`]: /nomad/commands/server/force-leave
+[`server join`]: /nomad/commands/server/join
+[autopilot]: /nomad/docs/manage/autopilot
+[bootstrapping guide]: /nomad/docs/deploy/clusters/connect-nodes
+[deployment configuration]: /nomad/docs/architecture/cluster/consensus#deployment_table
+[section below]: #manual-recovery-using-peers-json
+[Key material]: /nomad/docs/manage/key-management
+[restore the keyring]: /nomad/docs/manage/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.11.x/content/docs/manage/variables.mdx b/content/nomad/v1.11.x/content/docs/manage/variables.mdx
new file mode 100644
index 0000000000..a77ea2aab7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/manage/variables.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Create and update Nomad variables
+description: |-
+  Use the Nomad CLI or API to create, store, and update Nomad variables.
+---
+
+# Create and update Nomad variables
+
+This page describes the processes for interacting with Nomad variables. Use the
+[`nomad var` command reference](/nomad/commands/var) or the [Vars HTTP
+API](/nomad/api-docs/variables) to manage Nomad variables.
+
+## Background
+
+Nomad variables provide the option to securely store configuration at
+file-like paths directly in Nomad's state store. For complete documentation on
+the Nomad variables feature and related concepts, refer to the following:
+
+- [Nomad variables concepts](/nomad/docs/concepts/variables)
+- [Nomad variable specification](/nomad/docs/other-specifications/variables)
+- [Key management](/nomad/docs/manage/key-management)
+- [Workload identity](/nomad/docs/concepts/workload-identity)
+
+Nomad scopes a Nomad variable to a namespace and allows access to Nomad
+variables according to ACL policies.
+
+## Generate a Nomad variable specification
+
+Use the [`nomad var init` command](/nomad/commands/var/init) to generate a Nomad
+variable specification that you can customize.
+
+@include 'variables/init-example.mdx'
+
+## Add and update Nomad variables
+
+Use the [`nomad var put` command](/nomad/commands/var/put) to create and update
+Nomad variables. Supply variable items by including a Nomad variable
+specification file, a series of key-value pairs, or both. Refer to the [`nomad
+var put` command reference](/nomad/commands/var/put) for details on formatting
+keys and values. Values that you supply as command line arguments supersede
+values provided in any variable specification piped into the command or loaded
+from file.
+
+You may also use  the `nomad var put` command to overwrite all items in a
+variable. To avoid conflicting with other writes that may have happened since
+you last read the variable, you must use the `-check-index` flag and set it to
+the last modified index.
+
+@include 'variables/put-example.mdx'
+
+## Delete Nomad variables
+
+Use the [`nomad var purge` command](/nomad/commands/var/purge) to permanently
+delete an existing variable.
+
+@include 'variables/purge-example.mdx'
+
+## Query Nomad variables
+
+### Get
+
+Use the [`nomad var get` command](/nomad/commands/var/get) to fetch the contents of an existing variable.
+
+@include 'variables/get-example.mdx'
+
+### List
+
+Use the [`nomad var list` command](/nomad/commands/var/list) to fetch a list of
+variable paths accessible to you.
+
+@include 'variables/list-example.mdx'
+
+## Lock access to a Nomad variable
+
+The [`nomad var lock` command](/nomad/commands/var/lock) provides a mechanism
+for distributed locking. Nomad creates a lock in the given variable, and only
+when held, invokes the specified child process.
+
+@include 'variables/lock-example.mdx'
+
+## Next steps
+
+Refer to the following Nomad variables tutorials for in-depth learning:
+
+- [Create and update Nomad
+  variables](/nomad/tutorials/variables/variables-create) contains advanced
+  examples for updating Nomad variables.
+- [Configure access control for Nomad
+  variables](/nomad/tutorials/variables/variables-acls) shows how to configure
+  ACL policies for Nomad variables.
+
+To learn how to access Nomad variables in your job specification, refer to [Use Nomad variables in tasks](/nomad/docs/job-declare/nomad-variables).
diff --git a/content/nomad/v1.11.x/content/docs/monitor/cluster-topology.mdx b/content/nomad/v1.11.x/content/docs/monitor/cluster-topology.mdx
new file mode 100644
index 0000000000..4aedceea06
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/monitor/cluster-topology.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Cluster state topology
+description: |-
+  Discover and use the topology visualization of the Nomad web UI to observe
+  clients and active workloads on your cluster.
+---
+
+# Cluster state topology
+
+As a Nomad cluster grows, the exact state of allocations and clients can become a mystery. For the most part this is a good thing: it means Nomad is quietly scheduling workloads without any need for intervention. However, as an operator, it is reasonable to still want to know what is going on within your cluster.
+
+The topology visualization is a single view of an entire cluster. It helps you perform preventative maintenance and it can help you understand your cluster's particular behaviors.
+
+## Prerequisites
+
+This tutorial assumes basic familiarity with Nomad. You must have access to an existing cluster that is running one or more jobs.
+
+Here is what you will need for this guide:
+
+- An active Nomad >=1.0.0 cluster
+- Access to the cluster's web UI
+- Read permissions to one or more namespaces
+
+## Navigate to the topology visualization
+
+The global left-hand navigation of the web UI has a Topology link under the cluster section. This link will take you to the topology visualization.
+
+[![The left-hand Nomad UI navigation with the topology link highlighted][topo-viz-link]][topo-viz-link]
+
+## The elements of the visualization
+
+The left-hand information panel contains aggregate cluster statistics. This includes the sum total of memory and CPU (in MHz) available to Nomad. The percentages of memory and CPU tell how much of each resource has been reserved—not how much is currently utilized. For instance, if a Docker container is currently utilizing 30MiB of memory but the task declared the need for 500MiB in the job spec, then the topology visualization will count this allocation as 500MiB.
+
+These aggregate metrics are meant to give a rough sense of scale and can answer immediate forecasting questions. If your cluster is currently at 80% capacity of a total 200GiB of memory and you know your services will only grow in the next year, then you can conclude that the capacity of the cluster will also have to grow.
+
+Be careful not to assume there is room for your allocation just because the aggregate remaining resources are less than what your job requires. Since resources are aggregated but allocations must be placed on a single client, it's possible that no client has room for your allocation. If there is 1500MHz of CPU available across a cluster but only 500MHz available per client, then a task that needs 600MHz of CPU cannot be placed.
+
+[![The info panel of the topology visualization with aggregate cluster statistics included][cluster-panel]][cluster-panel]
+
+The main visualization organizes all of your datacenters and clients and brings focus to your allocations.
+
+The outermost section represents a datacenter (1). Each section is labeled by the datacenter name, capacity, and status. Clients are rendered within their respective datacenter. Clients will also be labeled by their name, capacity, and status (2). This also includes icon indicators of scheduling eligibility and drain state (3).
+
+[![The primary cluster view of the topology visualization. Annotation 1: the datacenter section. Annotation 2: the client name and details. Annotation 3: a lock icon indicator for scheduling ineligibility. Annotation 4: two rows of rectangles representing allocations.][cluster-view]][cluster-view]
+
+Clients across your entire fleet are sized vertically based on their capacity. Clients with more total capacity are taller. This makes scanning a cluster easier.
+
+Within each client container are two rows; one for each primary scheduling unit (CPU and memory). Each row will include each allocation on the client scaled proportionally to the amount of resources reserved for it (4). An allocation for a task group that requires 8GiB of memory on a client that has 32GiB total will occupy 25% of a client row.
+
+## Interact with the visualization
+
+The topology visualization is designed to presennt as much information as possible in a single view. More information can be expanded by hovering or clicking on specific elements.
+
+Hovering over allocations will open a tooltip that gives quick details including the specific allocation reservation requirements and the job the allocation belongs to.
+
+[![The allocation tooltip showing allocation information for the allocation under the cursor][allocation-tooltip]][allocation-tooltip]
+
+Clicking an allocation will select it and swap out the cluster aggregate statistics in the information panel with allocation information. This includes links to the allocation, the job the allocation belongs to, the client the allocation is running on, and the current resource utilization over time.
+
+[![The info panel of the topology visualization with allocation information included][alloc-info-panel]][alloc-info-panel]
+
+In addition to the information shown in the panel, when an allocation is selected, associations among all allocations for the same task group and job will be drawn. This helps convey the distribution of a single task group across a cluster.
+
+[![Lines drawn between allocations to show that they all belong to the same job and task group][alloc-associations]][alloc-associations]
+
+For large clusters, the topology visualization will hide the client labels. When this is the case, clicking a client will expand client details in the information panel.
+
+[![The info panel of the topology visualization with client information included][client-panel]][client-panel]
+
+## Effective use of the topology visualization
+
+The topology visualization is intended to be an open-ended exploration tool. Here are a few example explorations that the visualization is particularly well-suited for.
+
+### Identify excessive client provisioning
+
+Sometimes clients are provisioned separately from application sizing and placement. This can lead to a drift between the expected client requirements and the actual requirements. Clients with no allocations still cost money.
+
+This can be quickly detected with the topology visualization. Empty clients are highlighted in red and labeled as empty.
+
+[![An empty client in the cluster view emphasized in red][empty-clients]][empty-clients]
+
+~> Is this a problem you have? Consider using [horizontal cluster autoscaling](https://github.com/hashicorp/nomad-autoscaler).
+
+### Spot potentially hazardous or flaky allocation distributions
+
+Nomad will automatically place allocations based on the requirements and constraints declared in the job spec. It is not uncommon for jobs to have missing constraints due to human error or unknown caveats. This class of error will often make itself known when the task starts, but sometimes the error is invisible and only surfaces through a peculiar error rate.
+
+For instance, imagine a service Service A that has five allocations. Four are in datacenter West and one is in datacenter East. Service A must talk to Service B, but due to networking rules, they cannot communicate across the datacenter boundary. If Service B is in datacenter West, then 80% of Service A traffic (assuming a uniform distribution) will work as intended while the remaining 20% will error. Or worse than error: silently behave incorrectly.
+
+This is easily remedied with a datacenter constraint in the job spec, but the problem must first be identified. Since the topology visualization will associate all allocations for Service A, this can be quickly spotted.
+
+[![Allocations associated across datacenters][alloc-associations-across-dcs]][alloc-associations-across-dcs]
+
+### Find noisy neighbor risks
+
+By default, tasks in Nomad have soft CPU limits. This lets tasks occasionally spike over their allotted CPU while still allowing for efficient bin-packing of allocations on a single client.
+
+It is possible for many allocations on a single client to exceed their CPU soft-limit—or for one allocation to greatly exceed it—starving other allocations of CPU. This can cause degraded performance and anomalous errors to arise from untested race conditions or timeouts. In this case, the problematic allocation is only problematic due to the external circumstances of the client it was scheduled on.
+
+The topology visualization makes it very clear when an important allocation is scheduled alongside many other allocations on a densely packed client. This alone doesn't mean there is a noisy neighbor problem, but it might be enough to defensively modify the job spec. Adding more CPU headroom or constraints can help stabilize the service.
+
+[![A single client in the topology visualization with many allocations][client-with-many-allocs]][client-with-many-allocs]
+
+## Next steps
+
+The topology visualization is a useful tool for learning to use Nomad and for understanding your cluster at a moment in time. It does _not_ show historical allocation reservation information.
+
+To get deeper utilization and historical data, you will need to set up a monitoring stack using Nomad's telemetry data. The topology visualization may inform your own custom dashboards as you invest in setting up operations tooling for your specific needs.
+
+1. [Use Prometheus to monitor Nomad metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+2. [Review the full set of metrics Nomad exports](/nomad/docs/reference/metrics)
+
+[topo-viz-link]: /img/monitor/topo-viz/topo-viz-link.png
+[cluster-panel]: /img/monitor/topo-viz/cluster-panel.png
+[cluster-view]: /img/monitor/topo-viz/cluster-view.png
+[allocation-tooltip]: /img/monitor/topo-viz/allocation-tooltip.png
+[alloc-info-panel]: /img/monitor/topo-viz/allocation-panel.png
+[alloc-associations]: /img/monitor/topo-viz/allocation-associations.png
+[client-panel]: /img/monitor/topo-viz/client-panel.png
+[empty-clients]: /img/monitor/topo-viz/empty-clients.png
+[alloc-associations-across-dcs]: /img/monitor/topo-viz/alloc-associations-across-dcs.png
+[client-with-many-allocs]: /img/monitor/topo-viz/client-with-many-allocs.png
diff --git a/content/nomad/v1.11.x/content/docs/monitor/event-stream.mdx b/content/nomad/v1.11.x/content/docs/monitor/event-stream.mdx
new file mode 100644
index 0000000000..28933c3877
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/monitor/event-stream.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Monitor Nomad's event stream
+description: |-
+  Subscribe to Nomad's event stream to observe activities in your Nomad cluster.
+---
+
+# Monitor Nomad's event stream
+
+The event stream provides a way to subscribe to Job, Allocation, Evaluation,
+Deployment, and Node changes in near real time. Whenever a state change occurs in
+Nomad via Nomad's Finite State Machine (FSM) a set of events for each updated
+object are created.
+
+Currently, Nomad users must take a number of steps to build a mental model of
+what recent actions have occurred in their cluster. Individual log statements
+often provide a small fragment of information related to a unit of work within
+Nomad. Logs can also be interlaced with other unrelated logs, complicating the
+process of understanding and building context around the issue a user is trying
+to identify. Log statements may also be too specific to a smaller piece of work
+that took place and the larger context around the log or action is missed or
+hard to infer.
+
+Another pain point is that the value of log statements depend on how they are
+managed by an organization. Larger teams with external log aggregators find
+more value out of standard logging than a smaller team who manually scans
+through files to debug issues. Today, an operator might combine the information
+returned by `/v1/nodes`, `/v1/evaluations`, `/v1/allocations`, and then
+`/v1/nodes` again using the Nomad API to try to figure out what exactly
+happened.
+
+This complex workflow has led to a lack of prescriptive guidance when working
+with customers and users on how to best monitor and debug their Nomad clusters.
+Third party tools such as `nomad-firehose` have also emerged to try to solve
+the issue by continuously scraping endpoints to react to changes within Nomad.
+
+The event stream provides a first-class solution to receiving a stream of events
+in Nomad and provides users a much better understanding of how their cluster is
+operating out of the box.
+
+## Access the event stream
+
+The event stream currently exists in the API, so users can access the new event
+stream endpoint from the below command.
+
+```shell-session
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+## Subscribe to all or certain events
+
+Filter on certain topics by specifying a filter key. This example listens
+for Node events only relating to that particular node's ID. It also listens
+to all Deployment events and Job events related to a job named web.
+
+```shell-session
+$ curl -s -v -N \
+  --data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+  --data-urlencode "topic=Deployment" \
+  --data-urlencode "topic=Job:web" \
+  http://127.0.0.1:4646/v1/event/stream
+```
+
+## What is in an event?
+
+Each event contains a `Topic`, `Type`, `Key`, `Namespace`, `FilterKeys`, `Index`,
+and `Payload`. The contents of the Payload depend on the event Topic. An event
+for the Node Topic contains a Node object. For example:
+
+```json
+{
+  "Topic": "Node",
+  "Type": "NodeRegistration",
+  "Key": "afb9c810-d701-875a-b2a6-f2631d7c2f60",
+  "Namespace": "",
+  "FilterKeys": null,
+  "Index": 7,
+  "Payload": {
+    "Node": {
+      "//": "...entire node object"
+    }
+  }
+}
+```
+
+## Develop using event stream
+
+Here are some patterns of how you might use Nomad's event stream.
+
+- Subscribe to all or subset of cluster events
+
+- Add an additional tool in your regular debugging & monitoring workflow as an
+  SRE to gauge the qualitative state and health of your cluster.
+
+- Trace through a specific job deployment as it upgrades from an evaluation to a
+  deployment and uncover any blockers in the path for the scheduler.
+
+- Build a slack bot integration to send deploy notifications.
+  - https://github.com/drewbailey/nomad-deploy-notifier
diff --git a/content/nomad/v1.11.x/content/docs/monitor/index.mdx b/content/nomad/v1.11.x/content/docs/monitor/index.mdx
new file mode 100644
index 0000000000..f9ae7bd57a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/monitor/index.mdx
@@ -0,0 +1,325 @@
+---
+layout: docs
+page_title: Monitor Nomad
+description: |-
+  Learn how to monitor the health and performance of Nomad clusters. Export data to Prometheus or DataDog. Review metrics for the Raft consensus protocol, scheduling, performance, capacity, task resource consumption, job and task status, runtime, and federated deployments.
+---
+
+# Monitor Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+## Key performance indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+## Raft consensus protocol
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://developer.hashicorp.com/nomad/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task resource consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and task status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Serf federated deployments
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+## Client introduction
+
+When you configure Nomad with [`client_introduction.enforcement`] set to either
+`warn` or `strict`, the server handling the client registration request
+increments the `nomad.client.introduction.enforcement` counter each time a new
+registration is made without an introduction token.
+
+Monitoring this metric can help identify clients that are not registering with
+an introduction token, which is important when migrating to a tougher
+enforcement level.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/reference/metrics#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus-apica
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/docs/manage/migrate-workloads
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/reference/metrics#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/reference/metrics#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/monitor#raft-consensus-protocol
+[Job Summary Metrics]: /nomad/docs/reference/metrics#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/how-scheduling-works
+[`client_introduction.enforcement`]: /nomad/docs/configuration/server#client_introduction-parameters
diff --git a/content/nomad/v1.11.x/content/docs/monitor/inspect-cluster.mdx b/content/nomad/v1.11.x/content/docs/monitor/inspect-cluster.mdx
new file mode 100644
index 0000000000..3b45c08159
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/monitor/inspect-cluster.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Inspect the cluster
+description: |-
+  View the server and client nodes, inspect an individual server or client node,
+  list allocations, and review client events from the Nomad web UI.
+---
+
+# Inspect the cluster
+
+The Web UI can be a powerful tool for monitoring the state of the Nomad cluster
+from an operator's perspective. This includes showing all client nodes, showing
+driver health for client nodes, driver status, resource utilization, allocations
+by client node, and more.
+
+## View cluster clients
+
+From any page, the Clients List page can be accessed from the left-hand
+navigation bar. On narrow screens this navigation bar may need to be opened from
+the top-right menu button. The table lists every client in the cluster and is
+searchable, sortable, and filterable. Each client row in the table shows basic
+information, such as the Node ID, name, state, address, datacenter, and how many
+allocations are running in it.
+
+This view will also live-update as the states of client nodes change.
+
+[![Clients List][img-clients-list]][img-clients-list]
+
+## Filter the client view
+
+If your Nomad cluster has many client nodes, it can be useful to filter the list
+of all client nodes down to only those matching certain facets. The Web UI has
+three facets you can filter by:
+
+1. **Class:** The node of the client, including a dynamically generated list
+   based on the node class of each client node in the cluster.
+
+1. **State:** The state of the cluster, including Initializing, Ready, Down,
+   Ineligible, and Draining.
+
+1. **Datacenter:** The datacenter the client node is in, including a dynamically
+   generated list based on all the datacenters in the cluster.
+
+[![Clients filters][img-clients-filters]][img-clients-filters]
+
+## Inspect an individual client
+
+From the Clients List page, clicking a client node in the table will direct you
+to the Client Detail page for the client node. This page includes all
+information about the client node is live-updated to always present up-to-date
+information.
+
+[![Client Detail][img-client-detail]][img-client-detail]
+
+## Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for client
+nodes. The Web UI uses these metrics to create time-series graphics for the
+current session.
+
+When viewing a client node, resource utilization will automatically start
+logging.
+
+[![Client Resource Utilization][img-client-resource-utilization]][img-client-resource-utilization]
+
+## List client allocations
+
+Allocations belong to jobs and are placed on client nodes. The Client Detail
+page will list all allocations for a client node, including completed, failed,
+and lost allocations, until they are garbage-collected.
+
+This is presented in a searchable table which can additionally be filtered to
+only preempted allocations.
+
+[![Client Allocations][img-client-allocations]][img-client-allocations]
+
+## Review client events
+
+Client nodes will also emit events on meaningful state changes, such as when the
+node becomes ready for scheduling or when a driver becomes unhealthy.
+
+[![Client Events][img-client-events]][img-client-events]
+
+## Check client driver status
+
+Task drivers are additional services running on a client node. Nomad will
+fingerprint and communicate with the task driver to determine if the driver is
+available and healthy. This information is reported through the Web UI on the
+Client Detail page.
+
+[![Client Driver Status][img-client-driver-status]][img-client-driver-status]
+
+## View client attributes
+
+In order to allow job authors to constrain the placement of their jobs, Nomad
+fingerprints the hardware of the node the client agent is running on. This is a
+deeply nested document of properties that the Web UI presents in a scannable
+way.
+
+In addition to the hardware attributes, Nomad operators can annotate a client
+node with [metadata] as part of the client configuration. This metadata is also
+presented on the Client Detail page.
+
+[![Client Attributes][img-client-attributes]][img-client-attributes]
+
+## Monitor a node drain
+
+A routine part of maintaining a Nomad cluster is draining nodes of allocations.
+This can be in preparation of performing operating system upgrades or
+decommissioning an old node in favor of a new VM.
+
+Drains are [performed from the CLI], but the status of a drain can be monitored
+from the Web UI. A client node will state if it is actively draining or
+ineligible for scheduling.
+
+Since drains can be configured in a variety of ways, the Client Detail page will
+also present the details of how the drain is performed.
+
+[![Client Drain][img-client-drain]][img-client-drain]
+
+## View cluster servers
+
+Whereas client nodes are used to run your jobs, server nodes are used to run
+Nomad and maintain availability. From any page, the Servers List page can be
+accessed from the left-hand navigation bar.
+
+The table lists every server node in your cluster. This will be a small list—
+[typically three or five].
+
+[![Servers List][img-servers-list]][img-servers-list]
+
+## Inspect an individual server
+
+Clicking a server node on the Servers List will expand the tags table for the
+server node.
+
+[![Server Detail][img-server-detail]][img-server-detail]
+
+## Secure the UI
+
+Depending on the size of your team and the details of you Nomad deployment, you
+may wish to control which features different internal users have access to. This
+includes limiting who has access to list and manage client nodes and list and
+manage server nodes. You can enforce this with Nomad's access control list
+system.
+
+By default, all features—read and write—are available to all users of the Web
+UI. Check out the [Securing the Web UI with ACLs] tutorial to learn how to prevent
+anonymous users from having write permissions as well as how to continue to use
+Web UI write features as a privileged user.
+
+## Continue your exploration
+
+Now that you have explored how to inspect the state of your cluster through the
+Nomad UI, you will next learn some considerations you should keep in mind when
+using the Nomad UI.
+
+[img-client-allocations]: /img/monitor/guide-ui-img-client-allocations.png
+[img-client-attributes]: /img/monitor/guide-ui-img-client-attributes.png
+[img-client-detail]: /img/monitor/guide-ui-img-client-detail.png
+[img-client-drain]: /img/monitor/guide-ui-img-client-drain.png
+[img-client-driver-status]: /img/monitor/guide-ui-img-client-driver-status.png
+[img-client-events]: /img/monitor/guide-ui-img-client-events.png
+[img-client-resource-utilization]: /img/monitor/guide-ui-img-client-resource-utilization.png
+[img-clients-filters]: /img/monitor/guide-ui-img-clients-filters.png
+[img-clients-list]: /img/monitor/guide-ui-img-clients-list.png
+[img-server-detail]: /img/monitor/guide-ui-img-server-detail.png
+[img-servers-list]: /img/monitor/guide-ui-img-servers-list.png
+[metadata]: /nomad/docs/configuration/client#meta
+[performed from the cli]: /nomad/docs/manage/migrate-workloads
+[securing the web ui with acls]: /nomad/docs/secure/acl
+[typically three or five]: /nomad/docs/architecture/cluster/consensus#deployment-table
diff --git a/content/nomad/v1.11.x/content/docs/monitor/inspect-workloads.mdx b/content/nomad/v1.11.x/content/docs/monitor/inspect-workloads.mdx
new file mode 100644
index 0000000000..7f1388e318
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/monitor/inspect-workloads.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Inspect job workloads
+description: |-
+  Inspect jobs, allocations, and tasks in the Nomad web UI and interact
+  with these objects to perform operations like restart an allocation or
+  stop a job.
+---
+
+# Inspect job workloads
+
+The Web UI can be a powerful companion when monitoring and debugging jobs
+running in Nomad. The Web UI will list all jobs, link jobs to allocations,
+allocations to client nodes, client nodes to driver health, and much more.
+
+## List jobs
+
+The first page you will arrive at in the Web UI is the Jobs List page. Here you
+will find every job for a namespace in a region. The table of jobs is
+searchable, sortable, and filterable. Each job row in the table shows basic
+information, such as job name, status, type, and priority, as well as richer
+information such as a visual representation of all allocation statuses.
+
+This view will also live-update as jobs get submitted, get purged, and change
+status.
+
+[![Jobs List][img-jobs-list]][img-jobs-list]
+
+## Filter job view
+
+If your Nomad cluster has many jobs, it can be useful to filter the list of all
+jobs down to only those matching certain facets. The Web UI has four facets you
+can filter by:
+
+1. **Type:** The type of job, including Batch, Parameterized, Periodic, Service,
+   and System.
+
+1. **Status:** The status of the job, including Pending, Running, and Dead.
+
+1. **Datacenter:** The datacenter the job is running in, including a dynamically
+   generated list based on the jobs in the namespace.
+
+1. **Prefix:** The possible common naming prefix for a job, including a
+   dynamically generated list based on job names up to the first occurrence of
+   `-`, `.`, and `_`. Only prefixes that match multiple jobs are included.
+
+[![Job Filters][img-job-filters]][img-job-filters]
+
+## Inspect an allocation
+
+In Nomad, allocations are the schedulable units of work. This is where runtime
+metrics begin to surface. An allocation is composed of one or more tasks, and
+the utilization metrics for tasks are aggregated so they can be observed at the
+allocation level.
+
+### Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for tasks
+and allocations. The Web UI uses these metrics to create time-series graphs for
+the current session.
+
+When viewing an allocation, resource utilization will automatically start
+logging.
+
+[![Allocation Resource Utilization][img-alloc-resource-utilization]][img-alloc-resource-utilization]
+
+### Review task events
+
+When Nomad places, prepares, and starts a task, a series of task events are
+emitted to help debug issues in the event that the task fails to start.
+
+Task events are listed on the Task Detail page and live-update as Nomad handles
+managing the task.
+
+[![Task Events][img-task-events]][img-task-events]
+
+### View rescheduled allocations
+
+Allocations will be placed on any client node that satisfies the constraints of
+the job definition. There are events, however, that will cause Nomad to
+reschedule allocations, (e.g., node failures).
+
+Allocations can be configured [in the job definition to reschedule] to a
+different client node if the allocation ends in a failed status. This will
+happen after the task has exhausted its [local restart attempts].
+
+The end result of this automatic procedure is a failed allocation and that
+failed allocation's rescheduled successor. Since Nomad handles all of this
+automatically, the Web UI makes sure to explain the state of allocations through
+icons and linking previous and next allocations in a reschedule chain.
+
+[![Allocation Reschedule Icon][img-alloc-reschedule-icon]][img-alloc-reschedule-icon]
+
+[![Allocation Reschedule Details][img-alloc-reschedule-details]][img-alloc-reschedule-details]
+
+### Unhealthy driver
+
+Given the nature of long-lived processes, it's possible for the state of the
+client node an allocation is scheduled on to change during the lifespan of the
+allocation. Nomad attempts to monitor pertinent conditions including driver
+health.
+
+The Web UI denotes when a driver an allocation depends on is unhealthy on the
+client node the allocation is running on.
+
+[![Allocation Unhealthy Driver][img-alloc-unhealthy-driver]][img-alloc-unhealthy-driver]
+
+### Preempted allocations
+
+Much like how Nomad will automatically reschedule allocations, Nomad will
+automatically preempt allocations when necessary. When monitoring allocations in
+Nomad, it's useful to know what allocations were preempted and what job caused
+the preemption.
+
+The Web UI makes sure to tell this full story by showing which allocation caused
+an allocation to be preempted as well as the opposite: what allocations an
+allocation preempted. This makes it possible to traverse down from a job to a
+preempted allocation, to the allocation that caused the preemption, to the job
+that the preempting allocation is for.
+
+[![Allocation Preempter][img-alloc-preempter]][img-alloc-preempter]
+
+[![Allocation Preempted][img-alloc-preempted]][img-alloc-preempted]
+
+## Review task logs
+
+A task will typically emit log information to `stdout` and `stderr`. Nomad
+captures these logs and exposes them through an API. The Web UI uses these APIs
+to offer `head`, `tail`, and streaming logs from the browser.
+
+The Web UI will first attempt to directly connect to the client node the task is
+running on. Typically, client nodes are not accessible from the public internet.
+If this is the case, the Web UI will fall back and proxy to the client node from
+the server node with no loss of functionality.
+
+[![Task Logs][img-task-logs]][img-task-logs]
+
+~> Not all browsers support streaming HTTP requests. In the event that streaming
+is not supported, logs will still be followed using interval polling.
+
+## Restart or stop an allocation or task
+
+Nomad allows for restarting and stopping individual allocations and tasks. When
+a task is restarted, Nomad will perform a local restart of the task. When an
+allocation is stopped, Nomad will mark the allocation as complete and perform a
+reschedule onto a different client node.
+
+Both of these features are also available in the Web UI.
+
+[![Allocation Stop and Restart][img-alloc-stop-restart]][img-alloc-stop-restart]
+
+## Force a periodic instance
+
+Periodic jobs are configured like a cron job. Sometimes, you might want to start
+the job before the its next scheduled run time. Nomad calls this a [periodic
+force] and it can be done from the Web UI on the Job Overview page for a
+periodic job.
+
+[![Periodic Force][img-periodic-force]][img-periodic-force]
+
+## Submit a new version of a job
+
+From the Job Definition page, a job can be edited. After clicking the Edit
+button in the top-right corner of the code window, the job definition JSON
+becomes editable. The edits can then be planned and scheduled.
+
+[![Job Definition Edit][img-job-definition-edit]][img-job-definition-edit]
+
+~> Since each job within a namespace must have a unique name, it is possible to
+submit a new version of a job from the Run Job screen. Always review the plan
+output.
+
+## Monitor a deployment
+
+When a system or service job includes the [`update` stanza], a deployment is
+created upon job submission. Job deployments can be monitored in realtime from
+the Web UI.
+
+The Web UI will show as new allocations become placed, tallying towards the
+expected total, and tally allocations as they become healthy or unhealthy.
+
+Optionally, a job may use canary deployments to allow for additional health
+checks or manual testing before a full roll out. If a job uses canaries and is
+not configured to automatically promote the canary, the canary promotion
+operation can be done from the Job Overview page in the Web UI.
+
+[![Job Deployment with Canary Promotion][img-job-deployment-canary]][img-job-deployment-canary]
+
+## Stop a job
+
+Jobs can be stopped from the Job Overview page. Stopping a job will gracefully
+stop all allocations, marking them as complete, and freeing up resources in the
+cluster.
+
+[![Job Stop][img-job-stop]][img-job-stop]
+
+## Continue your exploration
+
+Now that you have explored operations that can be performed with jobs through
+the Nomad UI, learn how to inspect the state of your cluster using the Nomad UI.
+
+[`update` stanza]: /nomad/docs/job-specification/update
+[img-alloc-preempted]: /img/monitor/guide-ui-img-alloc-preempted.png
+[img-alloc-preempter]: /img/monitor/guide-ui-img-alloc-preempter.png
+[img-alloc-reschedule-details]: /img/monitor/guide-ui-img-alloc-reschedule-details.png
+[img-alloc-reschedule-icon]: /img/monitor/guide-ui-img-alloc-reschedule-icon.png
+[img-alloc-resource-utilization]: /img/monitor/guide-ui-img-alloc-resource-utilization.png
+[img-alloc-stop-restart]: /img/monitor/guide-ui-img-alloc-stop-restart.png
+[img-alloc-unhealthy-driver]: /img/monitor/guide-ui-img-alloc-unhealthy-driver.png
+[img-job-definition-edit]: /img/monitor/guide-ui-img-job-definition-edit.png
+[img-job-deployment-canary]: /img/monitor/guide-ui-img-job-deployment-canary.png
+[img-job-filters]: /img/monitor/guide-ui-img-job-filters.png
+[img-job-stop]: /img/monitor/guide-ui-img-job-stop.png
+[img-jobs-list]: /img/monitor/guide-ui-jobs-list.png
+[img-periodic-force]: /img/monitor/guide-ui-img-periodic-force.png
+[img-task-events]: /img/monitor/guide-ui-img-task-events.png
+[img-task-logs]: /img/monitor/guide-ui-img-task-logs.png
+[in the job definition to reschedule]: /nomad/docs/job-specification/reschedule
+[local restart attempts]: /nomad/docs/job-specification/restart
+[periodic force]: /nomad/commands/job/periodic-force
+[securing the web ui with acls]: /nomad/docs/secure/acl
diff --git a/content/nomad/v1.11.x/content/docs/networking/cni.mdx b/content/nomad/v1.11.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..a77e8d21d5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/cni.mdx
@@ -0,0 +1,387 @@
+---
+layout: docs
+page_title: Container Network Interface plugins and custom bridge networking
+description: |-
+  Install Container Network Interface (CNI) reference plugins. Learn how to configure Nomad's bridge networking. Use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface plugins and custom bridge networking
+
+This page describes the process to install the [Container Network Interface (CNI)
+reference plugins][cni-plugin-docs] on your Linux distribution and configure
+custom CNI bridge networking on your Nomad clients.
+
+You may apply this guide's workflow to installing any network plugin that
+complies with the [CNI Specification][cni-spec], but you should verify plugin
+compatibility with Nomad before deploying in production.
+
+## Background
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+Nomad reads the following extensions from the [`cni_config_dir`][] (`/opt/cni/config` by default):
+
+- `.conflist` files load as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+- `.conf` and `.json` files load as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Install and configure CNI plugins on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, refer to [Use a CNI network
+with a job][] for job configuration.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a custom bridge mode configuration with CNI plugins
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration).
+Refer to that documentation for a complete explanation of the fields.
+
+You can use the following templates as a basis for your own CNI-based bridge
+network configuration in cases where you need access to an unsupported option
+in the default configuration.
+
+### Configuration files
+
+<Tabs>
+  <Tab heading="Default">
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,18,29">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+  <Tab heading="IPv6">
+
+If you [configure IPv6][] on the Nomad client agent using the example range
+`2001:db8::/112`, Nomad adds two more lines to the configuration.
+
+<CodeBlockConfig highlight="19,23">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}],
+          [{"subnet": "2001:db8::/112"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"},
+          {"dst": "::/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+  <Tab heading="Transparent Proxy">
+
+Jobs that use the
+[`transparent_proxy`](/nomad/docs/job-specification/transparent_proxy)
+block add a `consul-cni` plugin to the bottom of the CNI configuration.
+
+Refer to the
+[transparent proxy](/nomad/docs/networking/consul/service-mesh#transparent-proxy)
+section of Nomad's Consul service mesh documentation to ensure that
+the node is configured correctly for this feature.
+
+<CodeBlockConfig highlight="36-39">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [{"subnet": "172.26.64.0/20"}]
+        ],
+        "routes": [
+          {"dst": "0.0.0.0/0"}
+        ],
+        "dataDir": "/var/run/cni"
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    },
+    {
+      "type": "consul-cni",
+      "log_level": "debug"
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+  </Tab>
+</Tabs>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Next steps
+
+ Refer to [Use a CNI network with a job][] for job configuration details.
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
+[Use a CNI network with a job]: /nomad/docs/job-networking/cni
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[configure IPv6]: /nomad/docs/configuration/client#bridge_network_subnet_ipv6
diff --git a/content/nomad/v1.11.x/content/docs/networking/consul/index.mdx b/content/nomad/v1.11.x/content/docs/networking/consul/index.mdx
new file mode 100644
index 0000000000..1471e1322c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/consul/index.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: Consul integration
+description: |-
+  Integrate Consul with Nomad to use Consul features such as automatic clustering, service discovery, service mesh, Consul Template, Consul DNS, Consul ACL, and Consul namespaces with your Nomad clusters and workloads.
+---
+
+# Consul integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and install Consul
+on your nodes alongside Nomad, or schedule it as a system job. Nomad does not
+run Consul for you.
+
+To enable Consul integration, please refer to the [Nomad agent Consul
+configuration][] documentation.
+
+## Automatic clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please refer to the [Automatic Clustering
+with Consul][] guide for more information.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please refer to the
+[`service` job specification documentation][service].
+
+## Service mesh
+
+Consul service mesh provides service-to-service connection authorization and
+encryption using mutual Transport Layer Security (TLS). Nomad can automatically
+provision the components necessary to securely connect your tasks to Consul's
+service mesh.
+
+Refer to the [Consul Service Mesh integration page][int_consul_mesh] for more
+information.
+
+## Dynamic configuration
+
+Nomad's job specification includes a [`template`][] block that uses a Consul
+ecosystem tool called [Consul Template][]. This mechanism creates a convenient
+way to ship configuration files that are populated from environment variables,
+Consul data, Vault secrets, or just general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul
+Template, please see the [`template` job specification documentation][].
+
+## DNS
+
+To provide Consul DNS to Nomad workloads using [bridge or CNI networking
+mode][], you will need to configure Consul's DNS listener to be exposed to the
+workload network namespace, or configure `systemd-resolved`, `dnsmasq`, or
+similar DNS stub resolvers to forward DNS. See [Forward DNS for Consul service
+discovery][] for details.
+
+You can avoid exposing the Consul agent on a public IP by setting the Consul
+`bind_addr` to bind on a private IP address (the default is to use the
+`client_addr`). You will also need to either have Consul bind to port 53 for
+DNS if you are not using DNS forwarding.
+
+You will also need to set the [nameserver][] to the address. This address is
+exposed as the `consul.dns.addr` node attribute or the `DNSStubListener`
+configuration value for `systemd-resolved`.
+
+An simpler solution is to use Consul service mesh [transparent proxy][] mode to
+automatically configure tasks to use Consul DNS.
+
+## Consul access control list (ACL)
+
+The Consul ACL system protects the cluster from unauthorized access. When
+enabled, both Consul and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Consul ACL integration page][int_consul_acl] for more
+information.
+
+## Consul namespaces <EnterpriseAlert inline/>
+
+@include 'consul-namespaces.mdx'
+
+## Multiple Consul clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Consul clusters. They can be
+configured using multiple [`consul`][nomad_config_consul] blocks with different
+`name` values. If a `name` is not provided, the cluster configuration is called
+`default`. Nomad automatic clustering uses the `default` cluster for service
+discovery.
+
+Jobs that need access to Consul may specify which Consul cluster to use with
+the [`consul.cluster`][] parameter.
+
+## Assumptions
+
+* Each Nomad client should have a local Consul agent running on the same host,
+  reachable by Nomad. Nomad clients should never share a Consul agent or talk
+  directly to the Consul servers. Nomad is not compatible with [Consul Data
+  Plane][CDP].
+
+* The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+* Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+* The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+
+* Consul service mesh using network namespaces is only supported on Linux.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Consul.
+
+* Nomad is not compatible with Consul Data Plane.
+
+|               | Consul 1.19.0+ | Consul 1.20.0+ | Consul 1.21.0+ | Consul 1.22.0+ |
+|---------------|----------------|----------------|----------------|----------------|
+| Nomad 1.11.0+ | ✅             | ✅             | ✅             | ✅             |
+| Nomad 1.10.0+ | ✅             | ✅             | ✅             | ✅             |
+| Nomad 1.8.0+  | ✅             | ✅             | ✅             | ✅             |
+
+[Automatic Clustering with Consul]: /nomad/docs/deploy/clusters/connect-nodes
+[CDP]: /consul/docs/connect/dataplane
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Nomad agent Consul configuration]: /nomad/docs/configuration/consul
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`template` job specification documentation]: /nomad/docs/job-specification/template#consul-integration
+[`template`]: /nomad/docs/job-specification/template
+[int_consul_acl]: /nomad/docs/secure/acl/consul
+[int_consul_mesh]: /nomad/docs/networking/consul/service-mesh
+[nomad_config_consul]: /nomad/docs/configuration/consul
+[service]: /nomad/docs/job-specification/service
+[bridge or CNI networking mode]: /nomad/docs/job-specification/network#mode
+[nameserver]: /nomad/docs/job-specification/network#servers
+[transparent proxy]: /nomad/docs/job-specification/transparent_proxy
+[Forward DNS for Consul service discovery]: https://developer.hashicorp.com/consul/tutorials/networking/dns-forwarding
diff --git a/content/nomad/v1.11.x/content/docs/networking/consul/service-mesh.mdx b/content/nomad/v1.11.x/content/docs/networking/consul/service-mesh.mdx
new file mode 100644
index 0000000000..7f863e660d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/consul/service-mesh.mdx
@@ -0,0 +1,599 @@
+---
+layout: docs
+page_title: Integrate Consul service mesh
+description: |-
+  Learn how to use Nomad with Consul service mesh to enable secure service-to-service communication. Review an example that enables secure communication with Consul TLS, Consul access control lists (ACLs), and a transparent proxy.
+---
+
+# Consul service mesh
+
+## Introduction
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+## Nomad with Consul service mesh integration
+
+In a production environment, Nomad and Consul exist within the same datacenter.
+
+![Reference diagram](/img/deploy/nomad_reference_diagram.png)
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+### Network mode
+
+Consul service mesh requires network isolation to function, so you must set
+job group's `network` [`mode`](/nomad/docs/job-specification/network#mode)
+to `bridge`, or an appropriately configured `cni/*` network.
+
+<details>
+<summary style={{ cursor: "pointer" }}>
+  Using a custom <code>cni/*</code> network with Consul service mesh requires
+  extra care.
+</summary>
+
+Given the variety of network configurations, the Nomad team and enterprise
+support are limited in our ability to support custom network configurations.
+Use custom CNI networks with Consul service mesh at your own risk. That said,
+you may model your network configuration on Nomad's [`bridge`
+network](/nomad/docs/networking/cni#create-a-custom-bridge-mode-configuration-with-cni-plugins).
+
+Consider these qualities when configuring your network:
+
+ * Nomad provides an isolated network namespace, but your CNI configuration
+   should not expose the main task(s) to the host network.
+ * Incoming traffic needs to be able to reach the sidecar at the IP:port
+   which will be advertised on the sidecar service.
+ * Traffic needs to be able to flow from different allocs' sidecars to
+   one another.
+
+</details>
+
+## Nomad Consul service mesh example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and the counting service are
+managed by Nomad. Nomad additionally configures Envoy proxies to run along side
+these applications. The dashboard is configured to connect to the counting
+service via localhost on port 9001. The proxy is managed by Nomad, and handles
+mTLS communication to the counting service.
+
+### Prerequisites
+
+#### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+##### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+##### Consul access control lists
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+##### Transparent proxy
+
+Using Nomad's support for [transparent proxy][] configures the task group's
+network namespace so that traffic flows through the Envoy proxy. When the
+[`transparent_proxy`][] block is enabled:
+
+* Nomad will invoke the [`consul-cni`][] CNI plugin to configure `iptables` rules
+  in the network namespace to force outbound traffic from an allocation to flow
+  through the proxy.
+* If the local Consul agent is serving DNS, Nomad will set the IP address of the
+  Consul agent as the nameserver in the task's `/etc/resolv.conf`.
+* Consul will provide a [virtual IP][] for any upstream service the workload
+  has access to, based on the service intentions.
+
+Using transparent proxy has several important requirements:
+
+* You must have the [`consul-cni`][] CNI plugin installed on the client host
+  along with the usual [required CNI plugins][cni_plugins].
+* To use Consul DNS and virtual IPs, you will need to configure Consul's DNS
+  listener to be exposed to the workload network namespace. You can do this
+  without exposing the Consul agent on a public IP by setting the Consul
+  `bind_addr` to bind on a private IP address (the default is to use the
+  `client_addr`).
+* The Consul agent must be configured with [`recursors`][] if you want
+  allocations to make DNS queries for applications outside the service mesh.
+* Your workload's task cannot use the same [Unix user ID (UID)][uid] as the
+  Envoy sidecar proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`][tproxy_no_dns], see below).
+
+For example, a HCL configuration with a [go-sockaddr/template][] binding to the
+subnet `10.37.105.0/20`, with recursive DNS set to OpenDNS nameservers:
+
+```hcl
+bind_addr   = "{{ GetPrivateInterfaces | include \"network\" \"10.37.105.0/20\" | limit 1 | attr \"address\" }}"
+
+recursors = ["208.67.222.222", "208.67.220.220"]
+```
+
+#### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+#### Container Network Interface (CNI) plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/deploy#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+### Run the service mesh-enabled services
+
+Once Nomad and Consul are running, with Consul DNS enabled for transparent proxy
+mode as described above, submit the following service mesh-enabled services to
+Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+#### API service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+group "api" {
+  network {
+    mode = "bridge"
+  }
+
+  # ...
+}
+```
+
+Since the API service is only accessible via Consul service mesh, it does not
+define any ports in its network. The `connect` block enables the service mesh
+and the `transparent_proxy` block ensures that the service will be reachable via
+a virtual IP address when used with Consul DNS.
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {
+        proxy {
+          transparent_proxy {}
+        }
+      }
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+#### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+group "dashboard" {
+  network {
+    mode = "bridge"
+
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        transparent_proxy {}
+      }
+    }
+  }
+}
+```
+
+The `connect` block with `transparent_proxy` configures the web frontend's
+network namespace to route all access to the `count-api` service through the
+Envoy proxy.
+
+The web frontend is configured to communicate with the API service with an
+environment variable `$COUNTING_SERVICE_URL`:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+}
+```
+
+The `transparent_proxy` block ensures that DNS queries are made to Consul so
+that the `count-api.virtual.consul` name resolves to a virtual IP address. Note
+that you don't need to specify a port number because the virtual IP will only be
+directed to the correct service port.
+
+#### Manually configured upstreams
+
+You can also use Connect without Consul DNS and `transparent_proxy` mode. This
+approach is not recommended because it requires duplicating service intention
+information in an `upstreams` block in the Nomad job specification. But Consul
+DNS is not protected by ACLs, so you might want to do this if you don't want to
+expose Consul DNS to untrusted workloads.
+
+In that case, you can add `upstream` blocks to the job spec. You don't need the
+`transparent_proxy` block for the `count-api` service:
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {}
+    }
+  }
+
+  # ...
+
+}
+```
+
+But you'll need to add an `upstreams` block to the `count-dashboard` service:
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        upstreams {
+          destination_name = "count-api"
+          local_bind_port  = 8080
+        }
+      }
+    }
+  }
+}
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend will also need to use an environment variable to communicate
+with the API service:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+}
+```
+
+This environment variable value gets interpolated with the upstream's
+address. Note that dashes (`-`) are converted to underscores (`_`) in
+environment variables so `count-api` becomes `count_api`.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+Bootstrapping the Envoy proxy requires that the Consul ACL token and service
+registration have successfully replicated to whichever Consul server the local
+Consul agent is connected to. Nomad clients poll for this value with exponential
+backoff and a timeout. You can adjust the timeouts on a given node by setting
+node metadata values via the command line or in the [`client.meta`][] agent
+configuration block. The default values are shown below:
+
+```shell-session
+nomad node meta apply -node-id $nodeID \
+    consul.token_preflight_check.timeout=10s \
+    consul.token_preflight_check.base=500ms \
+    consul.service_preflight_check.timeout=60s \
+    consul.service_preflight_check.base=1s
+```
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/deploy#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#install-cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
+[uid]: /nomad/docs/job-specification/transparent_proxy#uid
diff --git a/content/nomad/v1.11.x/content/docs/networking/index.mdx b/content/nomad/v1.11.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..577fcb72e6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/index.mdx
@@ -0,0 +1,341 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Nomad's networking features connect your workloads without running additional component tools like DNS servers and load balancers. Learn about workload allocation networking and bridge networking, which uses Container Network Interface (CNI) plugins or Docker. Review how Nomad networking differs from Kubernetes networking.
+---
+
+# Networking
+
+This page provides conceptual information about Nomad's networking feature, how
+networking works in Nomad, different patterns and configurations, and how Nomad
+networking differs from Kubernetes networking.
+
+## Introduction
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/glossary#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/reference/runtime-environment-settings#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/job-networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+Nomad's bridge network leverages [Container Network Interface (CNI) reference
+plugins](https://www.cni.dev/) to provide an operating-system agnostic interface
+to configure workload networking. Nomad's network plugin support extends Nomad's
+built-in compute resource scheduling to allow scheduling tasks with specialty
+network configurations, which Nomad implements with a combination of CNI
+reference plugins and CNI configuration files. Nomad supports any network plugin
+that complies with the CNI specification, but you should verify plugin
+compatibility with your Nomad version before deploying in production.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/job-networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/job-declare/consul-service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/networking/consul).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/deploy/task-driver/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/job-declare/task-driver/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/job-declare/task-driver/docker#network_mode)
+documentation and the [Networking](/nomad/docs/job-declare/task-driver/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [CConfigure bridge networking](/nomad/docs/networking/cni)
+- [Service discovery](/nomad/docs/networking/service-discovery)
+- [Consul service mesh](/nomad/docs/networking/consul/service-mesh)
+
+## Additional resources
+
+- [Nomad Networking Demystified](https://www.hashicorp.com/en/resources/nomad-networking-demystified)
+- [Multi-Interface Networking and CNI Plugins](https://www.hashicorp.com/en/blog/multi-interface-networking-and-cni-plugins-in-nomad-0-12)
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.11.x/content/docs/networking/ipv6.mdx b/content/nomad/v1.11.x/content/docs/networking/ipv6.mdx
new file mode 100644
index 0000000000..28149ccc08
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/ipv6.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: IPv6 Support in Nomad
+description: |-
+  Learn how Nomad supports IPv6. Configure Nomad to advertise IPv6 addresses. Link Nomad servers and clients that have specific IPv6 addresses. Set up Consul and Vault to use Nomad's IPv6 address. Learn how workload tasks and task drivers can use IPv6 addresses.
+---
+
+# IPv6 Support in Nomad
+
+Nomad supports IPv6 as long as the underlying networks, host machines,
+and operating systems running it support IPv6.
+
+This guide illustrates the different configuration settings you need for different connection contexts.
+
+## Advertise
+
+[Advertise][advertise] Nomad server and client addresses to specify what
+address other servers, clients, or external systems should use to make
+connections back to the agent.
+
+You can use [go-sockaddr][] templating to dynamically select a public IPv6
+address. In this example, for each protocol, fetch one IPv6 address from public
+interfaces and assign it as the protocol's address.
+
+```hcl
+advertise {
+  http = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  rpc  = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  serf = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+}
+```
+
+## Nomad to Nomad
+
+Nomad agent processes connect to one another to make RPC calls for cluster operations.
+
+We recommend using IPv6 on Nomad with DNS that resolves to IPv6 or by
+using cloud auto-join. The following server-to-server and client-to-server
+examples use IPv6 addresses explicitly.
+
+### Server to server
+
+Use the [`server_join`][server_join] block to link servers together.
+
+```hcl
+server {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]"]
+  }
+}
+```
+
+### Client to server
+
+Use the [`servers`][client.servers] parameter or the `server_join` parameter to
+link clients.
+
+```hcl
+client {
+  enabled = true
+  servers = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+}
+```
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+  }
+}
+```
+
+## Nomad to external systems
+
+Most connections between Nomad and other external systems occur via HTTP.
+
+For example, when you set a `NOMAD_ADDR` environment variable like this one:
+
+```
+export NOMAD_ADDR='http://[2001:db8::1]:4646'
+```
+
+You can do the following:
+
+- Use the Nomad CLI, which makes Nomad API calls.
+- Open the Nomad web UI in a browser with the command `nomad ui`.
+- Use [Workload identity][workload-identity].
+  - Nomad can reach Consul and Vault at IPv6 addresses, if they are listening,
+    to register services or fetch secrets.
+  - Configure Consul with the [`nomad setup consul` command][setup-consul].
+
+    ```
+    nomad setup consul -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+
+  - Configure Vault with the [`nomad setup vault` command][setup-vault].
+
+    ```
+    nomad setup vault -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+    ```
+
+Various other third-party services that support OIDC connections should also be
+able to reach Nomad at an IPv6 address, so long as the third-party services
+support IPv6.
+
+## Workloads
+
+Nomad supports arbitrary IPv6 network calls to and from tasks on client nodes.
+
+With host networking, tasks use the same network as the host machine.
+
+- Use these options to register services with an IPv6 address:
+  - Set the [`preferred_address_family`][preferred_address_family-config]
+    client config to `"ipv6"`.
+  - Include a [`service`][service-block] block in your job specification with
+    either the "nomad" or "consul" provider as usual.
+- Use [`bridge_network_subnet_ipv6`][bridge-network-subnet-ipv6] to configure
+  Nomad's [bridge network mode][bridge-network-mode] for IPv6.
+
+[CNI][cni] plugins can work with IPv6 as well. Nomad's bridge network does this.
+
+Some task drivers have their own IPv6 configuration options. If you have enabled
+IPv6 support in the [Docker driver][docker-driver], you can configure IPv6 in
+your job specification. Refer to [IPv6 Docker
+containers][ipv6-docker-containers] for details.
+
+
+[server_join]: /nomad/docs/configuration/server_join
+[client.servers]: /nomad/docs/configuration/client#servers
+[go-sockaddr]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[advertise]: /nomad/docs/configuration#advertise
+[workload-identity]: /nomad/docs/concepts/workload-identity
+[service-block]: /nomad/docs/job-specification/service
+[preferred_address_family-config]: /nomad/docs/configuration/client#preferred_address_family
+[bridge-network-mode]: /nomad/docs/job-specification/network#network-modes
+[bridge-network-subnet-ipv6]: /nomad/docs/configuration/client#bridge_network_subnet_ipv6
+[cni]: /nomad/docs/job-networking/cni
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker
+[ipv6-docker-containers]: /nomad/docs/job-specification/service#ipv6-docker-containers
+[setup-consul]: /nomad/commands/setup/consul
+[setup-vault]: /nomad/commands/setup/vault
diff --git a/content/nomad/v1.11.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.11.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..37db5c55db
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Nomad service discovery helps you automatically connect workloads. Compare Nomad's built-in service discovery feature to Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+---
+
+# Service discovery
+
+@include 'service-discovery.mdx'
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..4625cc3452
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,504 @@
+---
+layout: docs
+page_title: Nomad Access Control List (ACL) policy specification
+description: |-
+  Learn about Nomad's ACL policy specification. Review namespace, node, node pools, agent, operator, resource quota, host volume, and plugin rules policy structure and options. Configure ACLs for the Nomad UI.
+---
+
+# Nomad Access Control List (ACL) policy specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and
+[Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `host-volume-create` - Allows creating dynamic host volumes. This implicitly grants `host-volume-read`.
+- `host-volume-delete` - Allows deleting dynamic host volumes.
+- `host-volume-read` - Allows inspecting dynamic host volumes.
+- `host-volume-register` - Allows registering dynamic host volumes that have been created without a plugin. This implicitly grants `host-volume-read` and `host-volume-create`.
+- `host-volume-write` - Allows all write operations on dynamic host volumes. This implicitly grants `host-volume-read`, `host-volume-create`, `host-volume-register`, and `host-volume-delete`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for these fine-grained namespace capabilities.
+
+
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />host-volume-read<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />host-volume-write<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace. Note that
+variable paths never start with a leading `/`, so Nomad will return an error if
+you submit a policy that has such a path.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configure ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/docs/secure/acl
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..dd3b6f9212
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Nomad object specifications
+description: |-
+  This section contains information on ACL policy, namespace, node pool, resource quota, variable, and volume specifications.
+---
+
+# Nomad object specifications
+
+In addition to
+[Jobs](/nomad/docs/job-specification),
+these Nomad objects have specifications:
+
+- [ACL Policy](/nomad/docs/other-specifications/acl-policy)
+- [Namespace](/nomad/docs/other-specifications/namespace)
+- [Node Pool](/nomad/docs/other-specifications/node-pool)
+- [Resource Quota](/nomad/docs/other-specifications/quota)
+- [Variable](/nomad/docs/other-specifications/variables)
+- [Volume](/nomad/docs/other-specifications/volume)
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..7b707c91f3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: Nomad namespace specification
+description: |-
+  Learn about Nomad's namespace specification. Review namespace parameters. Configure capabilities, node pools, Vault, and Consul.
+---
+
+# Nomad namespace specification
+
+A Nomad namespace is a way to segment jobs and their associated objects from
+other jobs and other cluster users. Specify Nomad namespaces as HCL files and
+submit them with the [`nomad namespace apply`][cli_ns_apply] CLI command.
+Unlike [job specifications][jobspecs], namespace specifications do not support
+[HCL2][hcl2] features like functions.
+
+In [federated][] clusters, Nomad forwards all namespace updates to the
+[`authoritative_region`][] and replicates the updates to non-authoritative
+regions. This requires that you have bootstrapped ACLs in the authoritative
+region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers   = ["java", "docker"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+
+# Vault configuration is a Nomad Enterprise feature.
+vault {
+  default = "default"
+  allowed = ["default", "infra"]
+}
+
+# Consul configuration is a Nomad Enterprise feature.
+consul {
+  default = "default"
+  allowed = ["all", "default"]
+}
+```
+
+## Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+- `vault` <code>([Vault](#vault-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Vault clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+- `consul` <code>([Consul](#consul-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Consul clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+### `capabilities` parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+- `enabled_network_modes` `(array<string>: [])` - List of network modes allowed
+  in the namespace. If empty all network modes are allowed.
+
+- `disabled_network_modes` `(array<string>: [])` - List of network modes disabled
+  in the namespace.
+
+### `node_pool_config` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs or
+  dynamic host volumes in this namespace that don't define a node pool in their
+  specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that jobs or
+  dynamic host volumes in this namespace are allowed to use. By default, all
+  node pools are allowed. If an empty list is provided only the namespace's
+  default node pool is allowed. This field supports wildcard globbing through
+  the use of `*` for multi-character matching. This field cannot be used with
+  `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that jobs or
+  dynamic host volumes in this namespace are not allowed to use. This field
+  supports wildcard globbing through the use of `*` for multi-character
+  matching. If specified, jobs and dynamic host volumes are allowed to use any
+  node pool, except for those that match any of these patterns. This field
+  cannot be used with `allowed`.
+
+### `vault` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Vault cluster to use for jobs
+  in this namespace that don't define a Vault cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Vault clusters that are
+  allowed to be used by jobs in this namespace. By default, all Vault clusters
+  are allowed.  If an empty list is provided only the namespace's default Vault
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Vault clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Vault cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+### `consul` parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Consul cluster to use for jobs
+  in this namespace that don't define a Consul cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Consul clusters that are
+  allowed to be used by jobs in this namespace. By default, all Consul clusters
+  are allowed.  If an empty list is provided only the namespace's default Consul
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Consul clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Consul cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+## Resources
+
+Visit the [Nomad namespaces
+tutorial](/nomad/docs/govern/namespaces) to learn how to create
+and use Nomad namespaces
+
+[cli_ns_apply]: /nomad/commands/namespace/apply
+[hcl2]: /nomad/docs/reference/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: //nomad/docs/deploy/clusters/federate-regions
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..42a1bccbba
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad node pool specification
+description: |-
+  Learn about Nomad's node pool specification. Review an example node pool specification. Configure description, metadata, and scheduler options.
+---
+
+# Nomad node pool specification
+
+Node pools group nodes, letting you restrict which jobs are able to place
+allocations in a given set of nodes. Specify node pools as HCL files and submit
+them with the [`nomad node pool apply`][pool-apply] CLI command. Unlike [job
+specifications][jobspecs], node pool specifications do not support HCL2
+features like functions.
+
+This example is a node pool specification generated with the [`nomad node pool
+init` command][pool-init].
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # node_identity_ttl is an optional parameter that sets the TTL for all node
+  # identities issued to nodes in this node pool. The value must be a valid
+  # duration string (e.g. "30m", "1h", "24h"). If not set, the default value is
+  # "24h".
+  # node_identity_ttl = "24h"
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `node_identity_ttl` `(string: <optional>)` - Sets the TTL for node identities
+  issued to nodes in this node pool. The value must be a valid duration string
+  (e.g. "30m", "1h", "24h"). If not set, the default value is "24h".
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/quota.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/quota.mdx
new file mode 100644
index 0000000000..33a00c5aee
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/quota.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Nomad resource quota specification
+description: |-
+  Learn about Nomad's resource quota specification. Review an example resource quota specification. Configure resources, regions, devices, and storage options.
+---
+
+# Nomad resource quota specification
+
+[Resource quotas][] let you limit resource consumption across teams or
+projects to reduce waste and align budgets. Manage resource quotas with the CLI [`quota` command][quota] or with Nomad's [Quota HTTP API][].
+
+<EnterpriseAlert product="nomad" />
+
+## Example resource quota specification
+
+This example is a resource quota specification generated with the [`nomad quota init` command][init].
+
+```hcl
+name        = "default-quota"
+description = "Limit the shared default namespace"
+
+# Create a limit for the global region. Additional limits may
+# be specified in-order to limit other regions.
+limit {
+  region = "global"
+  region_limit {
+    cores      = 0
+    cpu        = 2500
+    memory     = 1000
+    memory_max = 1000
+
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+
+    storage {
+      variables    = 1000 # in MB
+      host_volumes = "1000 GiB"
+    }
+  }
+}
+```
+
+## Parameters
+
+- `name` `(string)` - The name of the Quota. Nomad uses `name` to connect the
+quota a [`Namespace`][].
+- `description` `(string: <optional>)` - A human-readable description.
+- `limit` <code>([QuotaLimit](#limit-parameters))</code> - The resource limit
+in a Nomad region.
+
+### `limit` parameters
+
+- `region` `(string)` - The Nomad `region` that the limit applies to.
+- `region_limit` <code>([RegionLimit](#region_limit-parameters))</code> -
+Resources to limit.
+
+### `region_limit` parameters
+
+Region limits define the limits on cumulative task [`resources`][] blocks for
+allocations in the namespace and region the quota is applied to.
+
+- `cores` `(int: <optional>)` - The limit on total number of CPU cores from all
+`resources.cores` in the namespace. The [CPU concepts][] documentation
+has more details on CPU resources.
+- `cpu` `(int: <optional>)` - The limit on total amount of CPU from all
+`resources.cpu` in the namespace.
+- `memory` `(int: <optional>)` - The limit on total mount of memory in MB from
+all `resources.memory` in the namespace.
+- `memory_max` `(int: <optional>)` - The limit on total mount of hard memory
+limits in MB from all `resources.memory_max` in the namespace.
+- `device` <code>([Device](#device-parameters): nil)</code>
+- `storage` <code>([Storage](#storage-parameters): nil)</code>
+
+### `device` parameters
+
+The `device` label specifies which device(s) the quota applies to,
+equivalent to the [`device`][] block in a job specification.
+
+- `count` `(int)` - How many of this device may be used.
+
+### `storage` parameters
+
+The `storage` block defines limits on provisioned storage.
+
+- `host_volumes` `(int: 0)` - Maximum total size of all [dynamic host volumes][]
+  in MiB. The default `0` means unlimited, and `-1` means variables are fully
+  disabled. This field accepts human-friendly string inputs such as "100
+  GiB". The quota for host volumes is enforced at the time the volume is created
+  via [`volume create`][].
+
+- `variables` `(int: 0)` - Maximum total size of all Nomad [variables][] in
+  MiB. The default `0` means unlimited, and `-1` means variables are fully
+  disabled. This field accepts human-friendly string inputs such as "100 GiB".
+
+## Resources
+
+Visit the [Create and use resource quotas tutorial][tutorial] to learn how to
+create quotas, attach a quota to a namespace, secure a quota with ACL, and
+design quotas for federated clusters.
+
+
+[Resource Quotas]: /nomad/docs/enterprise#resource-quotas
+[quota]: /nomad/commands/quota
+[Quota HTTP API]: /nomad/api-docs/quotas
+[tutorial]: /nomad/docs/govern/resource-quotas
+[`Namespace`]: /nomad/docs/other-specifications/namespace
+[variables]: /nomad/docs/concepts/variables
+[`resources`]: /nomad/docs/job-specification/resources
+[CPU concepts]: /nomad/docs/architecture/cpu
+[`device`]: /nomad/docs/job-specification/device#device-parameters
+[dynamic host volumes]: /nomad/docs/other-specifications/volume/host
+[init]: /nomad/commands/quota/init
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f6366ce61c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Nomad variable specification
+description: |-
+  Learn about Nomad's variable specification. Review an example variable specification. Configure path, namespace, and items.
+---
+
+# Nomad variable specification
+
+[Nomad variables][nv] let you store and use encrypted configuration data in your
+job specifications. Specify variables as HCL files and submit them with the
+[`nomad var put` command][var-put]. Unlike [job specifications][jobspecs], Nomad
+variables specifications do not support HCL2 features like functions.
+
+This example is a variable specification generated by [`nomad var init` command][var-init].
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+Refer to the [`nomad var put` restrictions section][var-restrict] for details on `path` and `items` name restrictions.
+
+## Resources
+
+- [Create and update Nomad variables](/nomad/tutorials/variables/variables-create)
+- [Configure access control for Nomad
+  variables](/nomad/tutorials/variables/variables-acls)
+- [Use Nomad variables in tasks](/nomad/docs/job-declare/nomad-variables)
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/commands/var/init
+[var-put]: /nomad/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/commands/var/put#restrictions
+
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..6dd3df44e5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: Nomad volume specification capability block
+description: |-
+  Configure Container Storage Interface (CSI) and dynamic host storage volume capability in the `capability`block of the Nomad volume specification. Set single node or multiple node access and file system or block device attachment mode.
+---
+
+# Nomad volume specification capability block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## Parameters
+
+- `access_mode` `(string)` - Defines whether a volume should be available
+  concurrently. The `access_mode` and `attachment_mode` from the volume request
+  must exactly match one of the volume's `capability` blocks.
+
+  - For CSI volumes the `access_mode` is required. Can be one of the following:
+
+    - `"single-node-reader-only"`: Jobs can only request the volume with
+      read-only access, and only one node can mount the volume at a time.
+    - `"single-node-writer"`: Jobs can request the volume with read/write or
+      read-only access, and only one node can mount the volume at a time.
+    - `"multi-node-reader-only"`: Jobs can only request the volume with
+      read-only access, but multiple nodes can mount the volume simultaneously.
+    - `"multi-node-single-writer"`: Jobs can request the volume with read/write
+      or read-only access, but the scheduler only allows one allocation to have
+      read/write access. Multiple nodes can mount the volume simultaneously.
+    - `"multi-node-multi-writer"`: Jobs can request the volume with read/write
+      or read-only access, and the scheduler allows multiple allocations to have
+      read/write access. Multiple nodes can mount the volume simultaneously.
+
+    Most CSI plugins support only single-node modes. Consult the documentation
+    of the storage provider and CSI plugin.
+
+  - For dynamic host volumes the `access_mode` is optional. Can be one of the following:
+
+    - `"single-node-writer"`: Jobs can only request the volume with read/write access.
+    - `"single-node-reader-only"`: Jobs can only request the volume with read-only access.
+    - `"single-node-single-writer"`: Jobs can request either read/write or
+      read-only access, but the scheduler only allows one allocation to have
+      read/write access.
+    - `"single-node-multi-writer"`: Jobs can request either read/write or
+      read-only access, and the scheduler allows multiple allocations to have
+      read/write access.
+
+    In the job specification, the default is `single-node-writer` unless
+    `read_only = true`, which translates to `single-node-reader-only`.
+
+- `attachment_mode` `(string)` - The storage API used by the volume. One of
+  `"file-system"` or `"block-device"`. The `access_mode` and `attachment_mode`
+  from the volume request must exactly match one of the volume's `capability`
+  blocks.
+
+  - For CSI volumes the `attachment_mode` field is required. Most storage
+    providers support `"file-system"`, to mount volumes using the CSI
+    filesystem API. Some storage providers support `"block-device"`, which
+    mounts the volume with the CSI block device API within the container.
+
+  - For dynamic host volumes the `attachment_mode` field is optional and
+    defaults to `"file-system"`.
+
+## Example
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/csi.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/csi.mdx
new file mode 100644
index 0000000000..35c079db23
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/csi.mdx
@@ -0,0 +1,288 @@
+---
+layout: docs
+page_title: Nomad Container Storage Interface (CSI) volume specification
+description: |-
+  Learn about the Nomad Container Storage Interface (CSI) volume
+  specification. Define capacity, capabilities, mount
+  options, secrets, topology requests, and a context map of values passed
+  directly to the CSI plugin to validate the volume. Learn how volume
+  creation and registration are different. Additionally, learn how to
+  expand the size of a volume and update a volume definition.
+---
+
+# Nomad Container Storage Interface (CSI) volume specification
+
+This page provides reference information for the Nomad Container Storage
+Interface (CSI) volume specification. Create and register CSI volumes using the
+[`volume create`][] and [`volume register`][] commands and the [`PUT
+/v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints. Define capacity,
+capabilities, mount options, secrets, topology requests, and a context map of
+values passed directly to the CSI plugin to validate the volume.  Learn how
+volume creation and registration are different. Additionally, learn how to
+expand the size of a volume and update a volume definition.
+
+Some attributes are only supported by a specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+Provide the file as either HCL or JSON to the commands and as JSON to the API.
+
+## Parameters
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume is somewhere between `capacity_min` and `capacity_max`; the
+  exact behavior is up to the storage provider. If you want to specify an exact
+  size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Increasing this value and reissuing
+  `volume create` or `volume register` may expand the volume, if the CSI plugin
+  supports it.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume is somewhere between `capacity_min` and `capacity_max`; the
+  exact behavior is up to the storage provider. If you want to specify an exact
+  size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume is created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on volume creation.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map of
+  strings passed directly to the CSI plugin to validate the volume. The details
+  of these parameters are specific to each storage provider, so consult the
+  specific plugin documentation for more information. Only allowed on volume
+  registration. Note that, like the rest of the volume specification, this block
+  is declarative, and an update replaces it in its entirety, therefore all
+  parameters need to be specified.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from the
+  storage provider. For example, the volume ID of an AWS EBS volume or Digital
+  Ocean volume. Only allowed on volume registration.
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification refers to
+  the volume.
+
+- `mount_options` <code>([MountOptions][mount_options]:
+  &lt;required&gt;)</code> - Options for mounting `file-system` volumes that
+  don't already have a pre-formatted file system.
+
+- `name` `(string: <required>)` - The name of the volume. On volume creation,
+  the external storage provider may use this field to tag the volume or as an
+  idempotency token, so it must be unique across all namespaces.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map of
+  strings used as credentials for publishing and unpublishing volumes.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume is created from scratch. The `snapshot_id`
+  cannot be set if the `clone_id` field is set. Only allowed on volume creation.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations such as region, zone, and rack where the provisioned volume
+  must be accessible from in the case of volume creation, or the locations where
+  the existing volume is accessible from in the case of volume registration.
+
+- `type` `(string: <required>)` - The type of volume. Must be `"csi"` for CSI
+  volumes.
+
+## Differences between create and register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values if
+they are not supported by the operation.
+
+On **volume registration** you should not set the [`snapshot_id`](#snapshot_id),
+or [`clone_id`](#clone_id) fields.
+
+On **volume creation** you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields.
+
+## Update a volume definition
+
+The `volume register` command allows updating a volume definition. However,
+after volume registration, you are only allowed to update the following fields:
+
+* `capacity_min` and `capacity_max`. You may increase the volume size if the CSI
+  plugin supports it. Expansion may or may not be possible while the volume is
+  in use, again depending on the plugin.  Reducing volume capacity is not
+  allowed per the CSI spec.
+* `mount_options` block if the volume is not in use.
+* `secrets` block
+* `context` block. The values for this field are typically provided by the CSI
+  plugin and should not be updated unless recommended by the CSI plugin's
+  documentation.
+
+Additionally, you may add or remove `capability` blocks, but only if the
+capability is not currently in use by a mounted volume.
+
+## Volume expansion
+
+You may expand CSI Volumes if the CSI controller plugin and node plugin, if
+required, has the `EXPAND_VOLUME` capability.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min) above
+the current real capacity of the volume, as received from the [`volume
+status`][] command, and re-issue either [`volume create`][] or [`volume
+register`][].
+
+Nomad reconciles the requested capacity by issuing expand volume requests to the
+controller plugin, and if required by the controller, also to the node plugins
+for each allocation that has a claim on the volume.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`][] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+
+### Volume expansion
+
+Either [`volume create`][] or [`volume register`][] commands can trigger
+an expand to occur, after the volume has already been created or registered.
+
+This example shows you how to expand a volume using the `volume create` command.
+
+1. Create a volume configuration file called `volume.hcl` that defines ID, name,
+   type, plugin ID, and capacity.
+
+   ```hcl
+   id        = "ebs_prod_db1"
+   name      = "database"
+   type      = "csi"
+   plugin_id = "ebs-prod"
+
+   capacity_min = "50gib"
+   capacity_max = "50gib"
+
+   # ... etc ...
+   ```
+
+1. Create the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created external volume vol-asdf1234 with ID ebs_prod_db1
+   ```
+
+1.  Review the volume's current capacity using the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status ebs_prod_db1 | grep Capacity
+   Capacity             = 50 GiB
+   ```
+
+1. Increase volume capacity in the `volume.hcl` file.
+
+   Update the `capacity_min` and `capacity_max` fields.
+
+   ```hcl
+   id        = "ebs_prod_db1"
+   name      = "database"
+   type      = "csi"
+   plugin_id = "ebs-prod"
+   # all of the above must remain the same
+
+   capacity_min = "100gib" # double
+   capacity_max = "100gib" # increased to match
+
+   # ... etc ...
+   ```
+
+1. Expand the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created external volume vol-asdf1234 with ID ebs_prod_db1
+   ```
+
+1. Review the new capacity by running the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status ebs_prod_db1 | grep Capacity
+   Capacity             = 100 GiB
+   ```
+
+If you encounter errors that are not clear from the command output,
+the CSI plugin allocation logs and Nomad leader server logs may be
+helpful.
+
+[api_volume_create]: /nomad/api-docs/volumes#create-csi-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-csi-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[`volume status`]: /nomad/commands/volume/status
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/host.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/host.mdx
new file mode 100644
index 0000000000..7f474422c6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/host.mdx
@@ -0,0 +1,346 @@
+---
+layout: docs
+page_title: Nomad dynamic host volume specification
+description: |-
+  Learn about the Nomad dynamic host volume specification. Define capacity,
+  capability, constraint, node, node pool, and parameters passed directly
+  to the plugin to configure the volume. Learn how volume creation and
+  registration are different. Additionally, learn how to place a volume on
+  specific nodes, update a volume, and expand a volume's capacity.
+---
+
+# Nomad dynamic host volume specification
+
+This page provides reference information for the Nomad dynamic host volume
+specification. Create and register dynamic host volumes using the [`volume
+create`][] and [`volume register`][] commands and the [`PUT
+/v1/volume/host/create`][api_volume_create] and [`PUT
+/v1/volume/host/register`][api_volume_register] API endpoints.  Define capacity,
+capability, constraint, node, node pool, and parameters passed directly to the
+plugin to configure the volume.  Learn how volume creation and registration are
+different. Additionally, learn how to place a volume on specific nodes, update a
+volume, and expand a volume's capacity.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API.
+
+## Parameters
+
+- `capacity` `(string: <optional>)` - The size of a volume in bytes. Either the
+  physical size of a disk or a quota, depending on the plugin. This field must
+  be between the `capacity_min` and `capacity_max` values unless they are
+  omitted. Accepts human-friendly suffixes such as `"100GiB"`. Only supported
+  for volume registration.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the plugin. The specific size of the resulting
+  volume is somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the plugin. If you want to specify an exact size, set
+  `capacity_min` and `capacity_max` to the same value. Accepts human-friendly
+  suffixes such as `"100GiB"`. Plugins that cannot restrict the size of volumes,
+  such as the built-in [`mkdir`][mkdir_plugin] plugin, may ignore this field.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the plugin. The specific size of the resulting
+  volume is somewhere between `capacity_min` and `capacity_max`; the exact
+  behavior is up to the plugin. If you want to specify an exact size, set
+  `capacity_min` and `capacity_max` to the same value. Accepts human-friendly
+  suffixes such as `"100GiB"`. Plugins that cannot restrict the size of volumes,
+  such as the built-in [`mkdir`][mkdir_plugin] plugin, may ignore this field.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `constraint` <code>([Constraint][constraint]: &lt;optional&gt;)</code> - A
+  restriction on the eligible nodes where a volume can be created. Refer to the
+  [volume placement](#volume-placement) section for details. You can provide
+  multiple `constraint` blocks to add more constraints. Optional for volume
+  creation and ignored for volume registration.
+
+- `id` `(string: <optional>)` - The ID of a previously created volume to update
+  via `volume create` or `volume register`. You should never set this field when
+  initially creating or registering a volume, and you should only use the values
+  returned from the Nomad API for the ID.
+
+- `host_path` `(string)` - The path on disk where the volume exists. You should
+  set this only for volume registration. It is ignored for volume creation.
+
+- `name` `(string: <required>)` - The name of the volume, which is used as the
+  [`volume.source`][volume_source] field in job specifications that claim this
+  volume. Host volume names must be unique per node. Names are visible to any
+  user with `node:read` ACL, even across namespaces, so they should not be
+  treated as sensitive values.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `node_id` `(string)` - A specific node where you would like the volume to be
+  created. Refer to the [volume placement](#volume-placement) section for
+  details. Optional for volume creation but required for volume registration.
+
+- `node_pool` `(string: <optional>)` - A specific node pool where you would like
+  the volume to be created. Refer to the [volume placement](#volume-placement)
+  section for details. Optional for volume creation or volume registration. If
+  you also provide `node_id`, the node must be in the provided `node_pool`.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the plugin to configure the volume. The details
+  of these parameters are specific to the plugin.
+
+- `plugin_id` `(string)` - The ID of the [dynamic host volume
+  plugin][dhv_plugin] that manages this volume. Required for volume
+  creation. Nomad has one built-in plugin called [`mkdir`][mkdir_plugin].
+
+- `type` `(string: <required>)` - The type of volume. Must be `"host"` for
+  dynamic host volumes.
+
+## mkdir plugin
+
+Nomad has one built-in plugin called `mkdir`, which creates a directory on the
+host in the Nomad agent's [host_volumes_dir][]. The directory name is the
+volume's ID.
+
+`mkdir` ignores `capacity_min` and `capacity_max` volume configuration,
+since it has no way of enforcing them.
+
+### mkdir parameters
+
+- `mode` `(string: <optional>)` - [Numeric
+notation](https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation)
+to apply to the created directory. Defaults to "0700", so only the owner can
+access it. Must be a string, or you may get unexpected results.
+- `uid` `(int: <optional>)` - User ID to own the directory. Defaults to the
+user running the Nomad client agent, which is commonly `0` (root).
+- `gid` `(int: <optional>)` - Group ID to own the directory. Defaults to the
+user running the Nomad client agent, which is commonly `0` (root).
+
+The user and group IDs must be present on any node that may receive the volume.
+
+### mkdir example
+
+<CodeBlockConfig filename="mkdir.volume.hcl">
+
+```hcl
+type      = "host"
+name      = "cool-host-vol"
+plugin_id = "mkdir"
+parameters = {
+  mode = "0755"
+  uid  = 1000
+  gid  = 1000
+}
+```
+
+</CodeBlockConfig>
+
+## Differences between create and register
+
+Several fields are set automatically by Nomad or the plugin when `volume create`
+or `volume register` commands, or the equivalent APIs, are successful and you
+should not set their values if they are not supported by the operation.
+
+In **volume creation** you must set the [`plugin_id`](#plugin_id) field. The
+[`capacity`](#capacity) and [`host_path`](#host_path) fields are ignored.
+
+In **volume registration** you must set the [`node_id`](#node_id) and
+[`host_path`](#host_path) fields. The [`plugin_id`](#plugin_id) and
+[`constraint`](#constraint) fields are ignored. The [`node_pool`](#node_pool),
+[`capacity_max`](#capacity_max), and [`capacity_min`](#capacity_min) fields are
+ignored but must be consistent if set; the `node_pool` must match the node set
+by `node_id`, and the minimum capacity must be less than the `capacity_max` and
+`capacity`.
+
+## Volume placement
+
+The `volume create` command creates the volume on a single node. If `node_id` is
+set, the volume is created on that node. The `node_pool` must be unset or match
+that node. Otherwise, the Nomad server iterates over the available nodes and
+place the volume on the first available node based on the following factors:
+
+* The node cannot already have a host volume with the same name.
+* If `node_pool` is set, the selected node must be in that node pool.
+* The node must meet any and all constraints defined by the `constraint` fields.
+
+## Update a volume definition
+
+The `volume create` and `volume register` commands allow updating a volume
+definition. However, after volume registration, you are only allowed to update
+the following fields:
+
+- `plugin_id`
+- `capacity_min` and `capacity_max`. You may increase
+  the volume size if the plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.  Reducing
+  volume capacity is not allowed. Only available for volume creation.
+- `capacity`, but only updated for volume registration.
+- `constraint` fields. Ignored after the volume is created.
+
+Additionally, you may add or remove `capability` blocks, but only if the
+capability is not currently in use by a mounted volume.
+
+You cannot update the `name`, `type`, and `node_id` fields. You may only change
+the `node_pool` field from empty to the node pool that matches the `node_id`
+field.
+
+## Volume expansion
+
+Dynamic host volumes may be expanded if the plugin allows. Reducing the size of
+a volume is not permitted.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min) above
+the current real capacity of the volume (as shown with the [`volume status`][]
+command), and re-issue [`volume create`][].
+
+Nomad reconciles the requested capacity by issuing a create request to the
+plugin.
+
+## Examples
+
+### Volume creation
+
+This is an example file used for the [`volume create`][] command.
+
+```hcl
+name            = "database"
+type            = "host"
+plugin_id       = "lvm-thin-provisioner"
+node_pool       = "prod"
+
+capacity_min = "80G"
+capacity_max = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+### Volume registration
+
+This is an example file used for the [`volume register`][] command.
+
+```hcl
+name      = "database"
+type      = "host"
+node_id   = "a7b4c0ca-cc78-11ef-8b5a-cb6ea67b844c"
+host_path = "/var/srv/example"
+capacity  = "80G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+### Volume expansion
+
+This example shows how to expand a volume after it has been created or
+registered.
+
+1. Create a volume configuration file called `volume.hcl` that defines name,
+   type, plugin ID, and capacity.
+
+  ```hcl
+   name      = "database"
+   type      = "host"
+   plugin_id = "external-plugin"
+
+   capacity_min = "30GiB"
+   capacity_max = "50GiB"
+   ```
+
+1. Create the volume using the [`volume create`] command.
+
+   ```shell-session
+   $ nomad volume create ./volume.hcl
+   ==> Created host volume database with ID 0c903229-311d-ba8a-f77e-45c31b83fab3
+   ✓ Host volume "0c903229" ready
+
+    2025-01-06T16:56:09-05:00
+    ID        = 0c903229-311d-ba8a-f77e-45c31b83fab3
+    Name      = database
+    Namespace = default
+    Plugin ID = external-plugin
+    Node ID   = cfe033a7-50de-2c46-cd18-12be7429eeb3
+    Node Pool = default
+    Capacity  = 50 GiB
+    State     = ready
+    Host Path = /run/nomad/dev/alloc_mounts/0c903229-311d-ba8a-f77e-45c31b83fab3
+   ```
+
+1. Review the volume's current capacity using the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status -type=host 0c903229 | grep Capacity
+   Capacity             = 50 GiB
+   ```
+
+1. Increase volume capacity in the `volume.hcl` file.
+
+   Update the `capacity_min` and `capacity_max` fields.
+
+   ```hcl
+   id        = "0c903229-311d-ba8a-f77e-45c31b83fab3"
+   name      = "database"
+   type      = "host"
+   plugin_id = "external-plugin"
+
+   capacity_min = "100GiB" # double
+   capacity_max = "100GiB" # increased to match
+   ```
+
+1. Expand the volume using the [`volume create`] command.
+
+   The `volume create` command can trigger an expansion to occur, after the
+   volume has already been created or registered.
+
+   ```shell-session
+   $ nomad volume create volume.hcl
+   Created host volume database with ID 0c903229-311d-ba8a-f77e-45c31b83fab3
+   ```
+
+1. Review the new capacity by running the [`volume status`] command.
+
+   ```shell-session
+   $ nomad volume status -type=host 0c903229 | grep Capacity
+   Capacity             = 100 GiB
+   ```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-dynamic-host-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-dynamic-host-volume
+[volume_source]: /nomad/docs/job-specification/volume#source
+[capability]: /nomad/docs/other-specifications/volume/capability
+[constraint]: /nomad/docs/job-specification/constraint
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[`volume status`]: /nomad/commands/volume/status
+[dhv_plugin]: /nomad/docs/architecture/storage/host-volumes
+[mkdir_plugin]: #mkdir-plugin
+[host_volumes_dir]: /nomad/docs/configuration/client#host_volumes_dir
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..70ba14d3f0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: Nomad volume specification
+description: |-
+  Learn about the Nomad volume specification. Review an example volume specification. Create and register Container Storage Interface (CSI) and dynamic host volumes. Define capability, mount options, topology requests, secrets, and parameters.
+---
+
+# Nomad volume specification
+
+This page provides reference information for the Nomad volume
+specification. Create and register Container Storage Interface (CSI) and dynamic
+host volumes using the [`volume create`][] and [`volume register`][] commands
+and the equivalent API endpoints. Define capability, mount options, topology
+requests, secrets, and parameters.
+
+Some attributes are only be supported by one volume type or the other, or a
+specific operation, while others may have a different meaning for each action,
+so read the documentation for each attribute carefully.
+
+* [CSI volume specification][csi_spec]
+* [Dynamic host volume specification][dhv_spec]
+
+Provide the file as either HCL or JSON to the commands and as JSON to
+the API.
+
+This example HCL configuration is for a CSI volume.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+[`volume create`]: /nomad/commands/volume/create
+[`volume register`]: /nomad/commands/volume/register
+[csi_spec]: /nomad/docs/other-specifications/volume/csi
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..a653de2880
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Nomad volume specification `mount_options` block
+description: |-
+  Configure Container Storage Interface (CSI) storage volume file system type and mount flags in the `mount_options` block of the Nomad volume specification.
+---
+
+# Nomad volume specification `mount_options` block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` CSI volumes that don't already have a
+pre-formatted file system. The `mount_options` block is not supported for
+dynamic host volumes.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.11.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.11.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..a8a519401d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Nomad volume specification `topology_request` block
+description: |-
+  Configure Container Storage Interface (CSI) storage volume topology in the `topology_request` block of the Nomad volume specification. Specify region, zone, and rack so that Nomad can access a provisioned CSI volume. Review volume creation examples with preferred and required topologies.
+---
+
+# Nomad volume specification `topology_request` block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations such as region, zone, and rack, where a provisioned CSI volume must
+be accessible, or where an existing volume is accessible. The `topology_request`
+block is not supported for dynamic host volumes.
+
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## Example
+
+This example illustrates volume creation with `preferred` and `required`
+topologies. The configuration requires Nomad to create the volume within racks
+`R1` or `R2`, but that you prefer creation within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.11.x/content/docs/partnerships.mdx b/content/nomad/v1.11.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..5bcefcba07
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/partnerships.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: Nomad Integration Program
+description: The HashiCorp Nomad Integration Program is the process for building and certifying products that integrate with Nomad. Review the integration categories and development process.
+---
+
+# Nomad Integration Program
+
+This page provides an overview of the HashiCorp Nomad Integration Program.
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and
+non-containerized applications across on-premises and cloud environments at
+scale. Nomad is widely adopted and used in production by organizations like
+Cloudflare, Roblox, Q2, Pandora, and more. Refer to the [What is Nomad?
+page](/nomad/docs/what-is-nomad) for a full description of the current features.
+
+This diagram depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/job-declare/task-driver)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/plugins/author/task-driver)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/plugins/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/plugins/author/device)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/architecture/storage/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/monitor)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.11.x/content/docs/quickstart.mdx b/content/nomad/v1.11.x/content/docs/quickstart.mdx
new file mode 100644
index 0000000000..bccbef1d36
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/quickstart.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: Nomad quickstart
+description: |-
+  The Nomad quickstart page contains links to resources that show you how to get started using Nomad locally or in a cloud environment.
+---
+
+# Nomad quickstart
+
+These installations are designed to get you started with Nomad and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, refer to the [Production Installation
+guide](/nomad/docs/deploy/production).
+
+## Nomad tutorials
+
+We recommend these tutorials, which provision a Nomad cluster for you.
+
+- [Get Started][]: Get up and running with Nomad by learning about scheduling,
+  setting up a cluster, and deploying an example job. Create a Nomad cluster
+  on your local machine or in an AWS, Azure, or Google Cloud Platform (GCP)
+  cloud environment. This tutorial series has an associated code repository so
+  you can review the Terraform provisioning scripts and Nomad job specifications.
+- [Cluster Setup][]: Provision a Nomad cluster on AWS, Azure, or GCP. Enable
+  Consul and access control lists (ACLs). This tutorial series has an associated
+  code repository so you can review the Terraform provisioning scripts.
+
+## Cloud installation
+
+The Nomad repository contains guides and Terraform scripts for provisioning a
+Nomad sandbox environment on AWS, Azure, or GCP with Consul and Vault. You can
+explore Nomad and its integrations with the HashiCorp stack.
+
+- [Provision a Nomad cluster on AWS][]
+- [Provision a Nomad cluster on Azure][]
+- [Provision a Nomad cluster on GCP][]
+
+## Local installation
+
+Use one of the following methods to run a local Nomad sandbox environment:
+
+- Install a binary
+
+  Refer to the [Install Nomad guide][installing-binary] to install the latest
+  Nomad release binary.
+
+  Run Nomad with the `sudo nomad agent -dev` [command][agent-dev], which
+  starts the Nomad agent in development mode.
+
+  If you are using Docker Desktop for Windows or MacOS, refer to [How to connect
+  to my host network when using Docker Desktop (Windows and MacOS)][faq-win-mac]
+  for instructions on binding Nomad to a non-loopback network interface.
+
+- Use Vagrant and VirtualBox
+
+  This option requires AMD hardware.
+
+  The Nomad repository contains a Vagrantfile. Refer to the [Developing with
+  Vagrant section][vagrant] of the [Nomad Codebase
+  Documentation][compile-source] file for instructions.
+
+- Compile and run from source
+
+  This option requires software engineering experience and a workstation set up
+  for Go, Node, and Docker development.
+
+  Refer to the Nomad repository's [Nomad Codebase Documentation][compile-source]
+  file for details.
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/deploy
+[Get Started]: /nomad/tutorials/get-started
+[Cluster Setup]: /nomad/tutorials/cluster-setup
+[Provision a Nomad cluster on AWS]: https://github.com/hashicorp/nomad/blob/main/terraform/aws/README.md
+[Provision a Nomad cluster on Azure]:
+    https://github.com/hashicorp/nomad/blob/main/terraform/azure/README.md
+[Provision a Nomad cluster on GCP]: https://github.com/hashicorp/nomad/blob/main/terraform/gcp/README.md
+[agent-dev]: /nomad/commands/agent#dev
+[vagrant]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md#developing-with-vagrant
+[compile-source]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md
diff --git a/content/nomad/v1.11.x/content/docs/reference/go-template-syntax.mdx b/content/nomad/v1.11.x/content/docs/reference/go-template-syntax.mdx
new file mode 100644
index 0000000000..17a33b806e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/go-template-syntax.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: Go template syntax
+description: |-
+  Discover the syntax of the text and template packages in Go and
+  become comfortable using them to create templates for Nomad
+  jobs.
+---
+
+# Go template syntax
+
+Go's internal templating language, provided by the text/template package, is the
+basis for many commonly used template implementations. Some HashiCorp specific
+examples are:
+
+- Nomad `template` stanzas
+- Consul-template
+- Vault agent templates
+- Nomad Pack
+
+Some other implementations you might have seen are:
+
+- Hugo
+- Helm
+
+Go's template is designed to be extended by developers, and provides access to
+data objects and additional functions that are passed into the template engine
+programmatically. This guide only uses functions universally provided in
+the text/template package, and does not discuss the specifics of data access.
+However, once you have learned the basics of Go templates, implementation
+specific data access is easier to understand.
+
+Early in this guide, you will see elements that you are not familiar with
+yet, but don't panic. Use your intuition and experience with other languages as
+your guide. As the guide progresses, it revisits these examples
+with a more thorough explanation.
+
+## Starting template
+
+Here is a template to get you started on your journey. This guide refers
+to this template while you are learning the names for the syntax.
+
+```plaintext
+This is a simple template
+It can {{ "output" }} something.
+It also
+{{- " demonstrates" }} trim markers.
+{{/* it has a comment */}}
+It can {{ "output" }} something.
+It can demonstrate {{ "output" | print }} using pipelines.
+It also {{ $A := "assigns variables" }}{{ $A }}.
+And conditionals:
+{{ $B := 2 }}{{ if eq $B 1 }}B is 1{{ else }}B is 2{{ end }}
+```
+
+## Nomenclature
+
+Go template uses names for its objects that are not immediately familiar. Once
+you have familiarized yourself with the concepts, the canonical documentation
+becomes easier to read.
+
+### Template
+
+Not surprisingly, the template is the entire text that is submitted to the
+template engine to be rendered. The template consists of text and "actions". All
+text outside of actions is copied to the output unchanged.
+
+### Actions
+
+Actions provide the dynamic components of the template. They are set off from
+the text using delimiters. The actions in the sample template are:
+
+```plaintext
+{{ "output" }}
+{{- " demonstrates" }}
+{{/* it has a comment */}}
+{{ "output" | print }}
+{{ $A := "assigns variables" }}{{ $A }}.
+{{ $B := 2 }}{{ if eq $B 1 }}{{ else }}{{ end }}
+```
+
+Actions are composed of "control structures," or data evaluations through
+"pipelines."
+
+<Note>
+
+ Actions may not span newlines. However, raw-string literals and
+comments may contain newlines. Raw-string literals are a special type of
+string literal discussed later.
+
+</Note>
+
+### Delimiters
+
+As said earlier, actions are set between a left delimiter (`{{` by default)
+and a right delimiter (`}}` by default). The implementation can either use
+alternative delimiters, like Levant's use of `[[` and `]]`; or allow you to
+specify them as in Nomad's `template` stanza.
+
+<Note>
+
+ The HashiCorp Learn tutorials use go template's default delimiters
+of `{{` and `}}` unless specifically stated in the guide itself. Remember
+that these delimiters might need to be customized for your specific use case.
+
+</Note>
+
+#### Trim markers
+
+Go template outputs everything between actions, including whitespace and
+line feeds. This can make it challenging to read nested template code.
+
+If an action's left delimiter is followed immediately by
+a minus sign and ASCII space character `{{- `, all trailing white space
+is trimmed from the immediately preceding text. Similarly, if the right
+delimiter is preceded by a space and minus sign ` -}}`, all
+leading white space is trimmed from the immediately following text.
+
+<Note>
+
+ The ASCII space must be present in these trim markers. `{{-3}}`
+parses as an action containing the number -3.
+
+</Note>
+
+### Comments
+
+Comments are a special action created using a `/*` immediately following the
+left delimiter and a `*/` immediately preceding the right delimiter. The sample
+template has a comment.
+
+```plaintext
+{{/* it has a comment */}}
+```
+
+Comments can span multiple lines. Any elements within the comment start and end
+delimiters is not processed by the rendering engine. Comments can also contain
+trim markers on one or both ends to remove whitespace. Comments with trim markers
+must have a space between the `-` and the start or end of the comment.
+
+```plaintext
+{{- /* example comment with trim markers /* -}}
+```
+
+<Tip>
+
+ Comment out sections of a template while you are debugging it to
+simplify your troubleshooting.
+
+</Tip>
+
+### Pipelines
+
+A pipeline is one or more "commands" chained together using the pipe `|` symbol.
+A command is a:
+
+- simple value (argument)
+- function or method call, possibly with multiple arguments.
+
+For example:
+
+```plaintext
+It can demonstrate {{ "output" | print }} using pipelines.
+```
+
+This template line uses pipelining to send the string literal "output" to the
+print function.
+
+#### Simple values
+
+Simple values are typically used as either the sole element in an action, like a
+string literal
+
+```plaintext
+{{ "output" }}
+```
+
+which is rendered to the template in place. Simple values can also be references
+to data provided as context to the template. This context is represented by a
+period '.' and called "dot".
+
+<Note>
+
+ Implementation-specific tutorials will describe dot and its usage
+in further detail.
+
+</Note>
+
+#### Literals
+
+Go template supports the following types as literals.
+
+| Data type        | Example                          | Specification                                                                      | Notes                                |
+| ---------------- | -------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------ |
+| `string`         | "output"                         | [String literal spec](https://golang.org/ref/spec#String_literals)                 | may not contain unescaped line feeds |
+| `raw string`     | \`"out<br />put"\`               | [String literal spec](https://golang.org/ref/spec#String_literals)                 | can contain raw linefeed characters  |
+| `integer`        | 42 <br />0xBadFace<br />         | [Integer literal Spec](https://golang.org/ref/spec#Integer_literals)               |                                      |
+| `floating point` | 0.<br />72.40<br />2.71828<br /> | [Floating-point literal Spec](https://golang.org/ref/spec#Floating-point_literals) |                                      |
+| `boolean`        | true<br />false                  | [Boolean type](https://golang.org/ref/spec#Boolean_types)                          |                                      |
+
+#### Function calls
+
+Go template provides a very limited number of functions universally, and instead
+relies on the specific implementation to add functions to enhance the user
+experience. However, `print` is one of the available functions.
+
+```plaintext
+{{ "output" | print }}
+```
+
+Later in the guide, there is a list of the built-in functions provided by all
+Go template environments.
+
+#### Method calls
+
+Since Go template provides an empty context to the template by default, there
+are no methods to be called. Refer to an implementation specific guide for more
+information on method calls.
+
+### Control structures
+
+Go template control structures are used to provide branching, iteration, and
+sub-templates. The control structure documentation uses `T0` and `T1` as
+placeholders for the specific template content that would be contained there.
+
+T0 and T1 might see a different version of dot depending on the control
+structure that is generating them. For example, `with` and `range` redefine
+dot to a new scope when their pipeline is non-empty.
+
+## Control structure list
+
+### if
+
+```plaintext
+{{if pipeline}} T1 {{end}}
+```
+
+If the value of the pipeline is empty, no output is generated; otherwise, T1 is
+executed. The empty values are false, 0, any nil pointer or interface value, and
+any array, slice, map, or string of length zero. Dot is unaffected.
+
+```plaintext
+{{if pipeline}} T1 {{else}} T0 {{end}}
+```
+
+If the value of the pipeline is empty, T0 is executed; otherwise, T1 is
+executed. Dot is unaffected.
+
+```plaintext
+{{if pipeline}} T1 {{else if pipeline}} T0 {{end}}
+```
+
+To simplify the appearance of if-else chains, the else action
+of an if may include another if directly; the effect is exactly
+the same as writing:
+
+```plaintext
+{{if pipeline}} T1 {{else}}{{if pipeline}} T0 {{end}}{{end}}
+```
+
+The sample template uses `if` and the `eq` function to branch
+between outputs.
+
+```plaintext
+{{ if eq $B 1 }}B is 1{{ else }}B is not 1{{ end }}
+```
+
+### range
+
+```plaintext
+{{range pipeline}} T1 {{end}}
+```
+
+The value of the pipeline must be an array, slice, map, or channel.
+If the value of the pipeline has length zero, nothing is output;
+otherwise, dot is set to the successive elements of the array,
+slice, or map and T1 is executed. If the value is a map and the
+keys are of basic type with a defined order, the elements are
+visited in sorted key order.
+
+```plaintext
+{{range pipeline}} T1 {{else}} T0 {{end}}
+```
+
+The value of the pipeline must be an array, slice, map, or channel.
+If the value of the pipeline has length zero, dot is unaffected and
+T0 is executed; otherwise, dot is set to the successive elements
+of the array, slice, or map and T1 is executed.
+
+One place you can test range is using the `-t` flag on many of the
+nomad commands. For example, you can retrieve the Node ID and version
+of each client in your cluster with the following command.
+
+```shell-session
+$ nomad node status -t '{{range .}}{{print .ID}} {{println .Version}}{{end}}'
+```
+
+### with
+
+```plaintext
+{{with pipeline}} T1 {{end}}
+```
+
+If the value of the pipeline is empty, no output is generated; otherwise, dot is
+set to the value of the pipeline and T1 is executed.
+
+```plaintext
+{{with pipeline}} T1 {{else}} T0 {{end}}
+```
+
+If the value of the pipeline is empty, dot is unaffected and T0 is executed;
+otherwise, dot is set to the value of the pipeline and T1 is executed.
+
+### define
+
+```plaintext
+{{define "name"}} T1 {{end}}
+```
+
+Create a template with the specified name that can be invoked using a `template`
+control structure
+
+### template
+
+```plaintext
+{{template "name"}}
+```
+
+The template with the specified name is executed with nil data.
+
+```plaintext
+{{template "name" pipeline}}
+```
+
+The template with the specified name is executed with dot set to the value of
+the pipeline.
+
+### block
+
+```plaintext
+{{block "name" pipeline}} T1 {{end}}
+```
+
+A block is shorthand for defining a template
+
+```plaintext
+{{define "name"}} T1 {{end}}
+```
+
+and then executing it in place
+
+```plaintext
+{{template "name" pipeline}}
+```
+
+The typical use is to define a set of root templates that are then customized by
+redefining the block templates within.
+
+## Function list
+
+Go template provides the following functions. Most implementations provide
+additional functions and can optionally override the default implementations.
+Consult the specific application's documentation for more information.
+
+### Functions
+
+| Function name | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| and           | Returns the boolean AND of its arguments by returning the first empty argument or the last argument, that is, "and x y" behaves as "if x then y else x". **All the arguments are evaluated.**                                                                                                                                                                                                                                                                                                                                                                                                 |
+| call          | Returns the result of calling the first argument, which must be a function, with the remaining arguments as parameters. Thus "call .X.Y 1 2" is, in Go notation, dot.X.Y(1, 2) where Y is a func-valued field, map entry, or the like. The first argument must be the result of an evaluation that yields a value of function type (as distinct from a predefined function such as print). The function must return either one or two result values, the second of which is of type error. If the arguments don't match the function or the returned error value is non-nil, execution stops. |
+| index         | Returns the result of indexing its first argument by the following arguments. Thus `index x 1 2 3` is, in Go syntax, `x[1][2][3]`. Each indexed item must be a map, slice, or array.                                                                                                                                                                                                                                                                                                                                                                                                          |
+| slice         | slice returns the result of slicing its first argument by the remaining arguments. Thus:<ul><li>`slice x 1 2` is, in Go syntax, `x[1:2]`</li><li> `slice x` is `x[:]`</li><li> `slice x 1` is `x[1:]`, </li><li>`slice x 1 2 3` is `x[1:2:3]`</li></ul> The first argument must be a string, slice, or array.                                                                                                                                                                                                                                                                                 |
+| len           | Returns the integer length of its argument.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| not           | Returns the boolean negation of its single argument.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| or            | Returns the boolean OR of its arguments by returning the first non-empty argument or the last argument, that is,"or x y" behaves as "if x then x else y". **All the arguments are evaluated.**                                                                                                                                                                                                                                                                                                                                                                                                |
+| print         | An alias for [fmt.Sprint][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| printf        | An alias for [fmt.Sprintf][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| println       | An alias for [fmt.Sprintln][]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+### Comparison functions
+
+| Function name | Description                               |
+| ------------- | ----------------------------------------- |
+| eq            | Returns the boolean truth of arg1 == arg2 |
+| ne            | Returns the boolean truth of arg1 != arg2 |
+| lt            | Returns the boolean truth of arg1 < arg2  |
+| le            | Returns the boolean truth of arg1 <= arg2 |
+| gt            | Returns the boolean truth of arg1 > arg2  |
+| ge            | Returns the boolean truth of arg1 >= arg2 |
+
+### Specialized output functions
+
+| Function name | Description                                                                                                               |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| html          | Returns the escaped HTML equivalent of the textual representation of its arguments.                                       |
+| js            | Returns the escaped JavaScript equivalent of the textual representation of its arguments.                                 |
+| urlquery      | Returns the escaped value of the textual representation of its arguments in a form suitable for embedding in a URL query. |
+
+
+[fmt.sprint]: https://golang.org/pkg/fmt/#Sprint
+[fmt.sprintf]: https://golang.org/pkg/fmt/#Sprintf
+[fmt.sprintln]: https://golang.org/pkg/fmt/#Sprintln
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/expressions.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/expressions.mdx
new file mode 100644
index 0000000000..4b8eef91f1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/expressions.mdx
@@ -0,0 +1,440 @@
+---
+layout: docs
+page_title: HCL expressions reference
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# HCL expressions reference
+
+Use HCL expressions to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced type details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/reference/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/reference/hcl2/functions).
+
+## `for` expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+**Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/reference/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
+
+
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..91e08ce6ef
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/reference/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..d5d34fd183
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/reference/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/compact.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/concat.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/contains.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/element.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..2d1ed4b971
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/reference/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/reference/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..ba579570d4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/reference/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..d4bf631d85
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/reference/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/keys.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..95b9caf985
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/reference/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/length.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..44b9563fb5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/reference/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/merge.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/range.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..6322e84f33
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/reference/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..29946b1263
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/reference/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..9d5c9d1e6f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/reference/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/reference/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/reference/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/reference/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..11c29e3ea0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/reference/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/reference/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/reference/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/slice.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..f997dbefe5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/reference/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/sort.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/values.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..396362787e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/reference/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/reference/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/can.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..5a1cdad38b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/reference/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/reference/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/reference/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/try.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..816cf73a30
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/reference/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..98ef4832b7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/secure/vault">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..ef918db1c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..93215259d3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/reference/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..07047561fa
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/reference/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..7b6a3529c7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..d11207c514
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/reference/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..394f48712c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/reference/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/reference/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..8a74fe44a6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/reference/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/reference/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/reference/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/abspath.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..0a33a9cd1c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/reference/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/basename.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..bff05fe35c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/reference/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/reference/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/dirname.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..544e6e6ab7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/reference/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/reference/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/file.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..fc2955718b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/reference/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..f75370b2f7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/reference/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/reference/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..62fea7cf70
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/reference/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileset.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/index.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..d154d5c452
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..b1f4b7a9c3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/reference/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..c833830894
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/reference/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/reference/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/reference/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/reference/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..5fec1f180d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/reference/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..b8952f45a8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/reference/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/log.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/max.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..76a9d70309
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/reference/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/min.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..b258366ca5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/reference/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..51aa325172
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/chomp.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..50c8d79546
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/format.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..65c15530bf
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/reference/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/reference/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..c634b1e33a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/reference/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/reference/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/indent.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/join.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..7202e32800
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/reference/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/lower.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..7044b162a3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/reference/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/reference/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..42c7e20a5b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/reference/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/replace.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..214fa4bd6d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/reference/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/split.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..4e5879dc82
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/reference/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strlen.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strrev.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..ee395b34ca
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/reference/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/substr.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/title.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..94768462fa
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/reference/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/reference/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trim.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..b17af25f38
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/reference/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/reference/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..587429ca3e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/reference/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/reference/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..39494ef8d2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/reference/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..3b4534b700
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/reference/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/reference/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/reference/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/upper.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..a95cec5de6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/reference/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/reference/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..e9f81ed79e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/reference/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..0247e8182d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/reference/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://developer.hashicorp.com/nomad/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/reference/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/index.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/index.mdx
new file mode 100644
index 0000000000..5bc7273a4a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/index.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: Hashicorp Configuration Language (HCL) reference
+description: |-
+  This section contains reference material for the Hashicorp Configuration Language (HCL) as it relates to defining a Nomad job specifications. Learn about HCL syntax elements such as arguments, blocks, and expressions. Review heredoc string support and how to format decimals.
+---
+
+# Hashicorp Configuration Language (HCL) reference
+
+Define your job specification with the Hashicorp Configuration Language (HCL),
+which is a syntax specifically designed for building structured configuration
+formats. Refer to the [HCL GitHub repository](https://github.com/hashicorp/hcl)
+to learn more about HCL.
+
+## Parsing context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The
+HCL parser's JSON format is unspecified, so the API format is preferred. You can
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/commands/job/run#json
+
+## Arguments, bocks, and expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/reference/hcl2/syntax)
+- [Expressions](/nomad/docs/reference/hcl2/expressions)
+
+### Blocks
+
+Block syntax is as follows, using unquoted attributes and quoted values:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/job-declare/task-driver/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/job-declare/task-driver/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/job-declare/task-driver/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "heredoc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL.
+
+### Decimals
+
+HCL requires a leading zero for decimal values lower than 1 (e.g. `0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/locals.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/locals.mdx
new file mode 100644
index 0000000000..4c6c026625
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: HCL locals reference
+description: |-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# HCL locals reference
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/reference/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/syntax.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/syntax.mdx
new file mode 100644
index 0000000000..342e1eec00
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: HCL syntax reference
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL syntax reference
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/reference/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.11.x/content/docs/reference/hcl2/variables.mdx b/content/nomad/v1.11.x/content/docs/reference/hcl2/variables.mdx
new file mode 100644
index 0000000000..bc0f5e086e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: HCL input variables reference
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# HCL input variables reference
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/reference/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/reference/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/reference/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/reference/runtime-environment-settings
+[expression]: /nomad/docs/reference/hcl2/expressions
diff --git a/content/nomad/v1.11.x/content/docs/reference/keyboard-commands.mdx b/content/nomad/v1.11.x/content/docs/reference/keyboard-commands.mdx
new file mode 100644
index 0000000000..835c170d1b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/keyboard-commands.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Keyboard commands reference
+description: |-
+  This page contains reference information for the available keyboard shortcut commands in the Nomad web UI.
+---
+
+# Web UI keyboard commands reference
+
+The Nomad Web UI supports keyboard shortcut commands to help you navigate and
+operate Nomad. You can use keyboard commands to inspect jobs, view logs,
+monitor evaluations, and more.
+
+## Open the shortcuts panel
+
+Type a question mark (`?`) on any web UI page to display the
+**Keyboard Shortcuts** panel. The available shortcuts and their corresponding
+commands are shown in the table below. To use commands with two letters
+separated by a space, type the letters one after the other.
+
+|Shortcut|Keyboard command|
+|---|---|
+|Go to the **Jobs** page|`g j`|
+|Go to the **Storage** page|`g r`|
+|Go to the **Variables** page|`g v`|
+|Go to the **Servers** page|`g s`|
+|Go to the **Clients** page|`g c`|
+|Go to the **Topology** page|`g t`|
+|Go to the **Evaluations** page|`g e`|
+|Go to the **Profile** page|`g p`|
+|Go to the **Administration** page|`g a`|
+|Next Subnav|`Shift + right arrow`|
+|Previous Subnav|`Shift + left arrow`|
+|Previous Main Section|`Shift + up arrow`|
+|Next Main Section|`Shift + down arrow`|
+|Show Keyboard Shortcuts|`?`|
+|Hide Keyboard Shortcuts|`Escape key`|
+
+## Toggle shortcut tooltip hints
+
+Hold the `Shift` key on any page in the web UI to overlay inline tooltip hints.
+Tooltips are contextual and will only show certain hints when applicable.
+
+## Disable shortcuts
+
+1. Open the **Keyboard Shortcuts** panel.
+1. At the bottom of the panel, click on the toggle next to the
+**Keyboard shortcuts enabled** option.
+
+## Re-bind shortcuts
+
+You can re-bind a shortcut with the following steps:
+
+1. Open the **Keyboard Shortcuts** panel.
+1. Click on the key combination next to the shortcut that you want to re-bind.
+1. Type the new key combination.
+
+To reset the key combination, click on the red **reset to default** text next
+to the key combination that you want to reset.
+
+## Traverse lists quickly
+
+The web UI has pages that display a lot of data in list form. To navigate to a
+specific item in the list, hold the `Shift` key and type the corresponding
+number in the tooltip hint next to the item that you want to navigate to. Note
+that items with a single digit require a leading zero (0).
\ No newline at end of file
diff --git a/content/nomad/v1.11.x/content/docs/reference/metrics.mdx b/content/nomad/v1.11.x/content/docs/reference/metrics.mdx
new file mode 100644
index 0000000000..dd5b0728f5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/metrics.mdx
@@ -0,0 +1,548 @@
+---
+layout: docs
+page_title: Metrics reference
+description: |-
+  This page contains reference information on the gauge, counter, and timer runtime metrics data that Nomad collects. Use the metrics endpoint to access the metrics data. Learn about the key metrics for monitoring your cluster. Review client, host, allocation, job summary, job status, server, Raft BoltDB, and agent metrics fields.
+---
+
+# Metrics reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------|
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.wait_time`               | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                                                                            | ms / Evaluation Wait           | Timer   |
+| `nomad.nomad.broker.process_time`            | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                                                                            | ms / Evaluation Process        | Timer   |
+| `nomad.nomad.broker.response_time`           | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                                                                                   | ms / Evaluation Response       | Timer   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/periodic) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.pending`              | Number of tasks pending                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.running`              | Number of tasks running                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.dead`                 | Number of tasks dead                                                                 | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+### Client hook metrics
+
+Nomad will emit metrics allowing you to monitor and alert on allocation and task hook performance.
+If you do not need these, they can be disabled via the [`disable_allocation_hook_metrics`][]
+configuration parameter.
+
+| Metric                                    | Description                                           | Unit         | Type    | Labels                                                      |
+|-------------------------------------------|-------------------------------------------------------|--------------|---------|-------------------------------------------------------------|
+| `nomad.client.alloc_hook.prerun.failed`   | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.success`  | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.elapsed`  | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.failed`  | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.success` | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.elapsed` | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+
+## Allocation metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job summary metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job status metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                                  | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                               | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                             | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                       | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                         | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                          | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                            | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                             | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                            | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                         | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                           | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                         | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                       | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                         | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                                | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                           | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                          | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                                | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                                | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`           | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                         | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class, node_pool                            |
+| `nomad.nomad.blocked_evals.memory`                      | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class, node_pool                            |
+| `nomad.nomad.blocked_evals.job.cpu`                     | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`                  | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`               | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`               | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`           | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                        | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                      | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                       | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.process_time`                       | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                 | ms / Evaluation Process  | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.response_time`                      | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                        | ms / Evaluation Response | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.service_ready`                      | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                    | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                       | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                     | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                        | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                      | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.wait_time`                          | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                 | ms / Evaluation Wait     | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.client.batch_deregister`                   | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                         | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                    | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`                 | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                        | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                           | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                         | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`                  | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                           | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                               | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                           | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                              | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                       | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                       | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`                 | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                      | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all`    | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`        | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`                | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`                 | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`                  | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`       | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`       | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`     | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`             | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                    | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                         | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                           | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`                 | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                           | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                          | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                        | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                           | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                            | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`               | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                        | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                                  | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                          | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                               | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                              | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                             | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                                 | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                                 | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                                 | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                              | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                               | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                          | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                          | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                          | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                        | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                   | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`       | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`               | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`               | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`             | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`                | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`                | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`               | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`          | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`                | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`           | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`             | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`         | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`               | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`            | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`        | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                   | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_version_tag`                 | Time elapsed to apply `ApplyJobVersionTag` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`                | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`                | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`                | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`                | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                    | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`                | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                             | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`                  | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`                 | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`               | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                          | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                           | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                        | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                       | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`                | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`             | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                     | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`               | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                    | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                               | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                          | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                         | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                           | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                    | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`                  | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                    | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`                 | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                           | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                      | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                           | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                            | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                              | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                              | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                           | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                      | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                               | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                     | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                                  | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                                  | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                              | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                                | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                          | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                                 | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                                | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                              | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`               | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                            | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                    | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                          | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`               | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                   | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`                  | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`                  | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`               | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                            | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                       | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                      | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                   | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`               | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`               | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                            | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                                | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                             | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                        | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`         | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                          | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                               | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                       | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                             | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                                | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                               | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.quota.utilization.cpu`                     | Utilization of the CPU quota                                                                                                                           | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.cores`                   | Utilization of the CPU Cores quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.memory_mb`               | Utilization of the Memory MB quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.storage.host_volumes_mb` | Utilization of the Host Volumes MB quota                                                                                                               | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.storage.variables_mb`    | Utilization of the Variables MB quota                                                                                                                  | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.scaling.get_policy`                        | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                     | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                      | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                        | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`          | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                        | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                        | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                               | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                       | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`                  | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`                  | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                           | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`      | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                              | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                         | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                                | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                               | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                           | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                          | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                        | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                       | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`            | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                           | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                        | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                        | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                     | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                               | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                    | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                              | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                                 | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                                  | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                                | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                                  | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                         | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                     | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`                  | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                            | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                             | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                               | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`               | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`            | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                              | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                             | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                               | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                       | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                           | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                                | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                               | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                                | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`          | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`              | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`         | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                             | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                        | Description                                            | Unit    | Type    | Labels |
+|-----------------------------------------------|--------------------------------------------------------|---------|---------|--------|
+| `nomad.agent.http.exceeded`                   | Count of HTTP connections exceeding concurrency limit  | Integer | Counter | -      |
+| `nomad.client.consul.check_deregistrations`   | Number of Consul check deregistration operations       | Integer | Counter | host   |
+| `nomad.client.consul.check_registrations`     | Number of Consul check registration operations         | Integer | Counter | host   |
+| `nomad.client.consul.checks`                  | Number of Consul checks currently registered           | Integer | Gauge   | host   |
+| `nomad.client.consul.service_deregistrations` | Number of Consul service deregistration operations     | Integer | Counter | host   |
+| `nomad.client.consul.service_registrations`   | Number of Consul service registration operations       | Integer | Counter | host   |
+| `nomad.client.consul.services`                | Number of Consul services currently registered         | Integer | Gauge   | host   |
+| `nomad.client.consul.sync_failure`            | Number of failed attempts to sync services with Consul | Integer | Counter | host   |
+
+[tagged-metrics]: /nomad/docs/reference/metrics#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://developer.hashicorp.com/nomad/s/port-plan-failure
+[`disable_allocation_hook_metrics`]: /nomad/docs/configuration/telemetry#disable_allocation_hook_metrics
diff --git a/content/nomad/v1.11.x/content/docs/reference/runtime-environment-settings.mdx b/content/nomad/v1.11.x/content/docs/reference/runtime-environment-settings.mdx
new file mode 100644
index 0000000000..4d35a2f36a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/runtime-environment-settings.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: Runtime environment settings
+description: Nomad provides runtime environment variables that you can use in your workloads. Learn about task identifiers, CPU and memory resources, IP addresses, task directories, and host variables. Review job, network, and Consul variables. Supply arbitrary configuration to a job task.
+---
+
+# Runtime Environment Settings
+
+This page provides reference information for runtime environment settings in
+your Nomad job specification. Learn about task identifiers, CPU and memory
+resources, IP addresses, task directories, and host variables. Review job,
+network, and Consul variables. Supply arbitrary configuration to a job task.
+
+## Introduction
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Variables Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta block for arbitrary configuration
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Both the original case and an uppercased
+version are injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks
+when using the `exec`, `raw_exec`, and `java` task drivers. Nomad also modifies
+`HOME`, `USER`, and `LOGNAME` variables for tasks that have the `user` parameter
+set, to reflect the set username. The variables that are passed to the tasks can
+be controlled using the client configuration [`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.11.x/content/docs/reference/runtime-variable-interpolation.mdx b/content/nomad/v1.11.x/content/docs/reference/runtime-variable-interpolation.mdx
new file mode 100644
index 0000000000..bc79e08815
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/runtime-variable-interpolation.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: Runtime variable interpolation
+description: Nomad supports interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review job, network, and Consul environment variables.
+---
+
+# Variable Interpolation
+
+This page provides reference information on interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review Review job, network, and Consul environment variables.
+
+## Introduction
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/job-declare/task-driver/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/job-declare/task-driver/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/job-declare/task-driver) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.11.x/content/docs/reference/sentinel-policy.mdx b/content/nomad/v1.11.x/content/docs/reference/sentinel-policy.mdx
new file mode 100644
index 0000000000..e55a446059
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/reference/sentinel-policy.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: Sentinel policy reference
+description: >-
+  Use the Nomad Enterprise Sentinel policy feature to implement fine-grained control over jobs, such as restricting when jobs can run or ensuring jobs use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+---
+
+# Sentinel Policy Reference
+
+<EnterpriseAlert product="nomad" />
+
+This page provides reference information on using the Nomad Sentinel policy feature to implement fine-grained policies such as restricting when jobs can run or ensuring job use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+
+## Introduction to Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+Refer to the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`][]
+subcommands.
+
+## Sentinel Policy Structure
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies. Nomad supports a `submit-job` scope for registering jobs,
+and a `submit-host-volume` scope for creating or updating dynamic host volumes.
+
+### submit-job scope
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  is always non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+### submit-host-volume scope
+
+The following top-level objects are available to policies in the
+`submit-host-volume` scope automatically, without an explicit import.
+
+* `volume`: the submitted volume. This is a [Sentinel Dynamic Host Volume
+  Object](#sentinel-dynamic-host-volume-objects).
+* `existing_volume`: the previous version of the volume. If `volume_exists` is
+  true, this is always non-nil. This is also a [Sentinel Dynamic Host
+  Volume Object](#sentinel-dynamic-host-volume-objects). `volume_exists`: a
+  boolean field that indicates that a previous version of the volume exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+* `node`: the node the volume has been placed on. This is a [Sentinel Node
+  Object](#sentinel-node-objects).
+* `node_pool`: the node pool of the node the volume has been placed on. This is
+  a [Sentinel Node Pool Object](#sentinel-node-pool-objects).
+
+### submit-csi-volume scope
+
+The following top-level objects are available to policies in the
+`submit-csi-volume` scope automatically, without an explicit import.
+
+- `volume`: the submitted volume. This is a [Sentinel CSI Volume
+  Object](#sentinel-csi-volume-objects).
+- `existing_volume`: the previous version of the volume. If `volume_exists` is
+  true, this is always non-nil. This is also a [Sentinel CSI Volume
+  Object](#sentinel-csi-volume-objects). 
+- `volume_exists`: a boolean field that indicates that a previous version of the
+  volume exists.
+- `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-acl-token-objects).
+- `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+## Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+## Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+## Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+## Sentinel Node Objects
+
+The `node` object maps to the [Node][], with the fields converted to the
+Sentinel convention. Here are some examples:
+
+| Node Field         | Sentinel Accessor  |
+|--------------------|--------------------|
+| `node.Class`       | `node.class`       |
+| `node.Meta["foo"]` | `node.meta["foo"]` |
+
+## Sentinel Node Pool Objects
+
+The `node_pool` object maps to the [Node Pool][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Node Pool Field                                       | Sentinel Accessor                                       |
+|-------------------------------------------------------|---------------------------------------------------------|
+| `node_pool.Description`                               | `node_pool.description`                                 |
+| `node_pool.SchedulerConfiguration.SchedulerAlgorithm` | `node_pool.scheduler_configuration.scheduler_algorithm` |
+
+## Sentinel Dynamic Host Volume Objects
+
+The `volume` object maps to the [Dynamic Host Volume][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Dynamic Host Volume Field                    | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `volume.Name`                                | `volume.name`                                  |
+| `volume.RequestedCapabilities[0].AccessMode` | `volume.requested_capabilities[0].access_mode` |
+
+## Sentinel CSI Volume Objects
+
+The `volume` object maps to the [CSI Volume][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| CSI Volume Field                             | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `volume.Name`                                | `volume.name`                                  |
+| `volume.RequestedCapabilities[0].AccessMode` | `volume.requested_capabilities[0].access_mode` |
+
+Note that the `volume.Secrets` values and `volume.MountOptions.MountFlags` are always redacted to prevent credential leaks.
+
+
+[Nomad Sentinel Tutorial]: /nomad/docs/govern/sentinel
+[`nomad sentinel`]: /nomad/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L13502-L13531
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L5578-L5610
+[Node]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/structs.go#L2086-L2210
+[Node Pool]: https://github.com/hashicorp/nomad/blob/v1.9.4/nomad/structs/node_pool.go#L46-L68
+[Dynamic Host Volume]: https://github.com/hashicorp/nomad/blob/main/nomad/structs/host_volumes.go#L18-L87
+[CSI Volume]: https://github.com/hashicorp/nomad/blob/main/nomad/structs/csi.go#L249-L312 
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/index.mdx b/content/nomad/v1.11.x/content/docs/release-notes/index.mdx
new file mode 100644
index 0000000000..67d880152e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Release Notes
+description: |-
+  Hashicorp Nomad release notes.
+---
+
+# Release Notes
+
+Choose a version from the navigation sidebar to view the release notes for Nomad.
+
+Documentation for maintenance releases (e.g., 0.1.x) is on the bottom of each
+release notes page.
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/nomad/upcoming.mdx b/content/nomad/v1.11.x/content/docs/release-notes/nomad/upcoming.mdx
new file mode 100644
index 0000000000..ba5169b095
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/nomad/upcoming.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Upcoming
+description: >-
+  Review upcoming HashiCorp Nomad release changes.
+---
+
+# Upcoming
+
+Nomad strives to be backward compatible for at least 2 major releases, so for
+example, you can upgrade Nomad v1.6.x to Nomad v1.8.x. In addition, Enterprise
+customers have access to [Long Term Support (LTS)][LTS] releases.
+
+Refer to [Upgrading][] for details of the upgrade process, and [Upgrade
+Guides][] for notes on upgrading specific versions.
+
+However, from time to time it's necessary to make backwards _incompatible_
+changes to Nomad. We announce these on [changelog][], the [Release Notes][], and
+the version-specific [Upgrade Guides][]. In order to help you plan your
+upgrades, this page maintains a list of all planned future changes that might
+cause backwards incompatibilities or require operational changes. It's possible
+that a given change may happen later than intended, at which point we update
+this document. However, we do not move changes earlier than originally published
+unless there's a required change due to a security vulnerability.
+
+## Nomad 1.9.0
+
+* Nomad will remove support for HCL1 job specifications and the `-hcl1` flag on
+  the `nomad job run` and other commands. Refer to [GH-20195][] for more details.
+* Nomad will remove the [`tls_prefer_server_cipher_suites`][] agent configuration.
+* Nomad will remove support for Nomad client agents older than 1.6.0. Older
+  nodes will fail heartbeats. Nomad servers will mark the workloads on those
+  nodes as lost and reschedule them normally according to the job's
+  [`reschedule`][] block.
+
+## Nomad 1.10.0 LTS
+
+Nomad 1.10.0 is a Long-Term Support release for Enterprise customers.
+
+* Nomad will remove support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the integration
+  guide][consul-integration] for details.
+* Nomad will remove support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the integration guide][vault-integration] for
+  details.
+* Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+* Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+* Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+[LTS]: /nomad/docs/enterprise#long-term-support-lts-releases
+[Upgrading]: /nomad/docs/upgrade
+[Upgrade Guides]: /nomad/docs/upgrade/upgrade-specific
+[changelog]: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md
+[Release Notes]: /nomad/docs/release-notes
+[GH-20195]: https://github.com/hashicorp/nomad/issues/20195
+[`tls_prefer_server_cipher_suites`]: /nomad/docs/configuration/tls#tls_prefer_server_cipher_suites
+[consul-integration]: /nomad/docs/secure/acl/consul
+[vault-integration]: /nomad/docs/secure/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/job-specification/disconnect
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-10-x.mdx b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-10-x.mdx
new file mode 100644
index 0000000000..bb3d92560c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-10-x.mdx
@@ -0,0 +1,508 @@
+---
+layout: docs
+page_title: Nomad v1.10.x release notes
+description: >-
+  HashiCorp Nomad version 1.10.x release notes. New features include dynamic host volumes, OIDC Private Key JWT (client assertions), and OIDC Proof Key for Code Exchange (PKCE). Updates to the Container Storage Interface (CSI) volume delete and volume status commands. CSI volume and plugin events added to the event stream. Added UI URL hints to the end of common CLI commands and a -ui flag to auto-open them in a browser.
+---
+
+# Nomad 1.10.x release notes
+
+We are pleased to announce the following Nomad updates.
+
+## 1.10.5 release highlights
+
+### Windows OS enhancements
+
+- Configure Nomad agents to write to the Windows Event Log. Refer to the agent
+  configuration's [`eventlog` parameter](/nomad/docs/configuration#eventlog) for
+  details.
+- Use CLI commands to install and uninstall Nomad as a system service. Refer to
+  the following for more information:
+
+    - [`nomad windows service install` command reference](/nomad/commands/windows/service-install)
+    - [`nomad windows service uninstall` command reference](/nomad/commands/windows/service-uninstall)
+
+
+### Keyring configuration validation
+
+On agent startup, Nomad validates [the keyring configuration type](/nomad/docs/configuration/keyring) against supported values.
+
+### Scheduling performance improvement
+
+We improved scheduling performance when checking reserved ports usage.
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.5)
+for a list of bug and security fixes.
+
+## 1.10.4 release highlights
+
+### Nomad logs and journald output
+
+We have added functionality that enables you to retrieve journald output or the
+contents of the Nomad log file remotely using the CLI.
+
+#### New monitor export command
+
+For a given Nomad agent, this command retrieves journald logs or the
+entire contents of the Nomad log file. Review the [`monitor export` command
+reference](/nomad/commands/monitor/export) for usage, options, and examples.
+
+#### Historical log capture for debugging
+
+We added the following flags to the `nomad operator debug` command:
+
+- [`-log-lookback`](/nomad/commands/operator/debug#log-lookback): Include
+  historical journald logs in the debug capture.
+- [`-log-file-export`](/nomad/commands/operator/debug#log-file-export): Include
+  Nomad agents' logfiles in the debug capture.
+
+Refer to the [`nomad operator debug` command
+reference](/nomad/commands/operator/debug) for details.
+
+### Blocked evaluation metrics
+
+The `nomad.nomad.blocked_evals.cpu` and `nomad.nomad.blocked_evals.memory`
+server metrics now have a `node_pool` label. This helps you determine the node
+pool where a scaling operation is needed.
+
+Review the [server metrics in the Metrics reference](/nomad/docs/reference/metrics#server-metrics).
+
+### Sentinel policy scope for CSI volumes <EnterpriseAlert inline />
+
+We added a new `submit-csi-volume` Sentinel policy scope, which lets you apply
+Sentinel policies to CSI volume creation and registration.
+
+You may override `soft-mandatory` polices assigned to CSI volume creation and
+registration, but you may not override `hard-mandatory` policies. Refer to the
+[`EnforcementLevel`
+parameter](/nomad/api-docs/sentinel-policies#enforcementlevel) in the Sentinel
+Policies API for `soft-mandatory` and `hard-mandatory` definitions.
+
+Refer to the following documentation:
+
+- Sentinel policy reference
+
+  - [submit-csi-volume
+    scope](/nomad/docs/reference/sentinel-policy#submit-csi-volume-scope)
+  - [Sentinel CSI Volume
+    Objects](/nomad/docs/reference/sentinel-policy#sentinel-csi-volume-objects)
+
+- Volumes API reference
+
+  - [Register CSI Volume](/nomad/api-docs/volumes#register-csi-volume)
+  - [Create CSI Volume](/nomad/api-docs/volumes#create-csi-volume)
+
+- CLI command reference
+
+  - [`sentinel apply -scope "submit-csi-volume"`](/nomad/commands/sentinel/apply#scope)
+  - [`volume create -policy-override` option](/nomad/commands/volume/create#policy-override)
+  - [`volume register -policy-override` option](/nomad/commands/volume/register#policy-override)
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.4) for a list of bug fixes.
+
+## 1.10.3 release highlights
+
+### Consul service registrations
+
+We added the `kind` parameter to the `service` block in the job specification.
+You may manually register a Consul service by specifying a Consul service
+kind. Refer to the Consul Register Service HTTP API's [Kind
+parameter](/consul/api-docs/agent/service#kind) for a list of Consul service
+Kind values.
+
+Previously, you configured a Consul service mesh in your job specification's
+`gateway` block. Now you may specify the kind of Consul service in the job
+specification service itself. If you configure both a service kind and a
+gateway in your job specification, the configured Consul service mesh gateway
+takes precedence.
+
+Refer to the [job specification `service` block `kind`
+parameter](/nomad/docs/job-specification/service#kind) for details.
+
+### Docker task driver cgroup namespace support
+
+You may specify the cgroup namespace in your job specification's Docker task
+driver configuration. This lets you run services that require a cgroup
+namespace, such as the Datadog Agent.
+
+Refer to the Docker task driver's [`cgroupns`
+parameter](/nomad/docs/job-declare/task-driver/docker#cgroupns) for details.
+
+### NOMAD_UNIX_ADDR task environment variable
+
+Use the `NOMAD_UNIX_ADDR` value as your `NOMAD_ADDR` when you want to use the
+Nomad CLI with the [task API's](/nomad/api-docs/task-api) Unix socket.
+
+This example sets the `NOMAD_ADDR` to the `NOMAD_UNIX_ADDR` environment
+variable.
+
+```hcl
+task "nomad-cli" {
+  driver = "raw_exec"
+  config { ... run `nomad` commands ... }
+  identity {
+    env = true
+  }
+  env {
+    NOMAD_ADDR = "${NOMAD_UNIX_ADDR}"
+  }
+}
+```
+
+Refer to these resources for details:
+
+- [Nomad CLI environment variables](/nomad/commands#environment-variables)
+- Runtime environment settings [job-related
+  variables](/nomad/docs/reference/runtime-environment-settings#job-related-variables)
+- Runtime variable interpolation [job-related
+  variables](/nomad/docs/reference/runtime-variable-interpolation#job-related-variables)
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.3)
+for a list of bug fixes.
+
+## 1.10.2 release highlights
+
+### Start stopped jobs
+
+The `nomad job start` CLI command starts a stopped job. This differs from the
+`nomad job restart` command, which restarts or reschedules allocations for a
+running job.
+
+Refer to the [`nomad job start` command reference](/nomad/commands/job/start)
+for details.
+
+### Dynamic host volumes garbage collection enhancements
+
+When a node is garbage collected, any dynamic host volumes on the node are
+orphaned in the state store. You generally don't want to automatically collect
+these volumes and risk data loss, so we enhanced garbage collection to let you
+delete orphaned dynamic host volumes.
+
+We added the `-force` flag to the `nomad volume delete` command so that you can
+delete the volume if the node has been garbage collected. Refer to the [`nomad
+volume delete` command reference](/nomad/commands/volume/delete#force) for details.
+
+For clusters running on ephemeral cloud instances, such as AWS
+EC2 in an autoscaling group, deleting host volumes may add excessive friction.
+The `gc_volumes_on_node_gc` client configuration parameter specifies that the
+server should delete any dynamic host volumes on the node when garbage
+collection deletes the node. Refer to the [`gc_volumes_on_node_gc` parameter
+definition](/nomad/docs/configuration/client#gc_volumes_on_node_gc) for details.
+
+### Configure max number of allocations
+
+The `node_max_allocs` parameter sets the maximum number of allocations that
+Nomad may schedule on a client node. Refer to the [`node_max_allocs` parameter
+definition](/nomad/docs/configuration/client#node_max_allocs) for details.
+
+### ACL policy with workload identity enhancements
+
+- Apply an ACL policy to a namespace.
+
+  When you apply an ACL policy to a namespace, Nomad applies the policy to all
+  the jobs within the namespace. Refer to the [workload-associated ACL policies
+  documentation](/nomad/docs/concepts/workload-identity#workload-associated-acl-policies)
+  for details.
+- Find the ACL policies associated with the current workload identity or ACL
+  token.
+
+  This enhancement lets you learn about ACL capabilities from within the
+  workload identity tasks.  Refer to the following resources for details:
+
+  - ACL Polices HTTP API [Read Self Policy
+    endpoint](/nomad/api-docs/acl/policies#read-self-policy)
+  - `nomad acl policy self` [command reference](/nomad/commands/acl/policy/self)
+  - `nomad acl token self` [command reference](/nomad/commands/acl/token/self)
+
+### Normalize IPv6 addresses
+
+Apply [RFC-5942 section 4
+recommendations](https://www.rfc-editor.org/rfc/rfc5952.html#section-4) to IPv6
+addresses. Nomad normalizes the addresses when it parses the configuration file
+so that the change runs through the whole system.
+
+### Option to render a job specification template only once
+
+We added `once` mode to the `template` block. This allows templates to render
+once without watching dependencies. Refer to the following resources for more
+information:
+
+- Consul Template Modes [Once
+  Mode](/consul/docs/automate/consul-template/mode#once-mode) for a thorough
+  description.
+- Job specification `template` block's [`once`
+  parameter](/nomad/docs/job-specification/template#once) for Nomad behavioral
+  changes.
+
+### Offline utilization reporting <EnterpriseAlert inline/>
+
+With this enhancement, Nomad periodically records usage metrics
+snapshots in the state store. Cluster administrators in air-gapped or otherwise
+secured environments may use the API or CLI to generate utilization reporting
+bundles from those usage metrics snapshots.
+
+Refer to the following resources:
+
+- The [Operator Utilization HTTP API](/nomad/api-docs/operator/utilization)
+- The [`nomad operator utilization` command
+  reference](/nomad/commands/operator/utilization)
+- The agent configuration `reporting` block's [`snapshot_retention_time`
+  parameter](/nomad/docs/configuration/reporting#snapshot_retention_time)
+
+### Breaking changes
+
+In templates, we removed support for these non-hermetic Sprig functions:
+`sprig_date`, `sprig_dateInZone`, `sprig_dateModify`, `sprig_htmlDate`,
+`sprig_htmlDateInZone`, `sprig_dateInZone`, `sprig_dateModify`,
+`sprig_randAlphaNum`, `sprig_randAlpha`, `sprig_randAscii`, `sprig_randNumeric`,
+`sprig_randBytes`, `sprig_uuidv4`, `sprig_env`, `sprig_expandenv`, and
+`sprig_getHostByName`.
+
+The aforementioned Sprig functions posed a security risk in that they allowed
+reading environment variables or resolving domain names to IP addresses.
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.2)
+for a list of security and bug fixes.
+
+### Upgrade details
+
+Review the [Nomad 1.10.2 upgrade guide](/nomad/docs/upgrade/upgrade-specific#nomad-1-10-2).
+
+## 1.10.1 release highlights
+
+### Override parameterized job's parent priority
+
+Use the `-priority` flag to override the priority inherited from a parameterized
+job's parent. Refer to the `nomad job dispatch` command's [`-priority`
+parameter](/nomad/commands/job/dispatch#priority) for details.
+
+### Breaking changes
+
+@include 'release-notes/v1-10-1/breaking-raft-peer.mdx'
+
+@include 'release-notes/v1-10-1/breaking-agent-exit.mdx'
+
+### Changelog
+
+Review [the changelog](https://github.com/hashicorp/nomad/releases/tag/v1.10.1)
+for a list of security and bug fixes.
+
+### Upgrade details
+
+Review the [Nomad 1.10.1 upgrade guide](/nomad/docs/upgrade/upgrade-specific#nomad-1-10-1).
+
+## 1.10.0 release highlights
+
+### Dynamic host volumes
+
+The dynamic host volumes feature brings a persistent storage option to your
+workload allocations.
+
+Nomad dynamic host volumes manage storage for stateful workloads without
+requiring a restart of the Nomad nodes to apply configuration changes. You
+create dynamic host volumes via the CLI or API and then configure the job with
+the [`volume`](/nomad/docs/job-specification/volume) and
+[`volume_mount`](/nomad/docs/job-specification/volume_mount) blocks in the job
+specification.
+
+Host volumes mount paths from the Nomad client into allocations. Nomad is aware
+of host volume availability and makes use of it for job scheduling. However,
+Nomad does not know about the volume's underlying characteristics, so you can
+use host volumes for both local persistent storage and for highly
+available networked storage.
+
+#### Dynamic host volume governance <EnterpriseAlert inline product="nomad"/>
+
+Providing guardrails to platform consumers is an important aspect of the storage
+provisioning workflow when leveraging host volumes across a shared Nomad
+cluster.  Nomad Enterprise supports these new capabilities to provide
+governance when provisioning host volumes:
+
+- **Sentinel dynamic host volume objects**
+
+  During volume creation, Nomad can evaluate all of the details within the
+  dynamic host volume specification against Sentinel policies
+  that define and enforce specific patterns.
+
+  For example, a policy that enforces the storage tier based on the environment
+  or namespace specified would allow reserving more expensive NVME storage for
+  specific workloads. Being able to apply policy to the volume specification
+  gives you a method to enforce specific patterns while providing platform
+  consumers with more flexibility around self-service volume provisioning. Refer
+  to the [Sentinel policy reference](/nomad/docs/reference/sentinel-policy#sentinel-dynamic-host-volume-objects) for more information.
+
+- **Resource quota support**
+
+  Nomad’s resource quota system now includes coverage for host volume capacity
+  limits that you can apply to provisioned storage within a specific namespace.
+  This helps control storage consumption within a namespace based on the maximum
+  capacities defined during creation or when making updates to the maximum
+  capacities over the lifecycle of the volume. Refer to the [Resource quota
+  specification](/nomad/docs/other-specifications/quota) for more information.
+
+- **Namespace and node pool validation**:
+
+  Dynamic host volumes live within the context of a specific namespace when
+  created. When Nomad provisions volumes in a namespace targeting a specific
+  node pool, Nomad evaluates the namespace node pool configuration to ensure
+  that volume creation aligns with job placement rules for node pools. Refer to
+  the [Namespace specification](/nomad/docs/other-specifications/namespace) for
+  details on `node_pool_config` parameters.
+
+#### Resources
+
+Refer to the following resources to learn more about dynamic host volumes:
+
+- [Host volumes section](/nomad/docs/architecture/storage/stateful-workloads#host-volumes)
+  in the _Considerations for stateful workloads_ guide for an overview and
+  comparison of storage options
+- [Host volumes plugin
+  specification](/nomad/docs/architecture/storage/host-volumes) for examples
+  of how to write your own plugin to dynamically configure persistent storage on
+  your Nomad client nodes
+- [Use Nomad dynamic host volumes to persist data for stateful workloads
+  tutorial](/nomad/docs/stateful-workloads/dynamic-host-volumes)
+  to learn how to create and use a dynamic host volume for persistent storage
+
+### OpenID Connect (OIDC) enhancements
+
+Nomad 1.10 extends Nomad's OIDC SSO login feature with [Private Key JWT][pkjwt]
+and [Proof Key for Code Exchange (PKCE)][pkce].
+
+#### Private Key JWT
+
+Private Key JWT, also called client assertions, is a more secure alternative for
+client secrets. Instead of sending a simple secret, Nomad builds a JWT and signs
+it with a value that the OIDC provider verifies. In this approach, Nomad asserts
+a valid OIDC client without sending any secret information over the network.
+
+#### Proof Key for Code Exchange (PKCE)
+
+PKCE adds an extra layer of security to any OIDC auth method for both client
+secrets and client assertions.
+
+Set the [ACL auth method `OIDCEnablePKCE`
+parameter](/nomad/api-docs/acl/auth-methods#oidcenablepkce) to `true` to turn
+on this extra security.
+
+Note that not all OIDC providers support PKCE. In addition to enabling PKCE in
+Nomad, you may need to enable it in your OIDC provider's configuration.
+
+#### Resources
+
+- [OIDC auth method guide][oidc-concepts] for details on using OIDC with Nomad
+- [OIDC troubleshooting guide][oidc-trouble] to review common issues and tips
+  for setting up OIDC
+- [Authenticate users with SSO and Keycloak tutorial][oidc-tutorial] to
+  configure Nomad and the Keycloak identity provider to automatically grant
+  permissions in Nomad ACL.
+
+### Container Storage Interface (CSI) enhancements
+
+We added the following:
+
+- CSI volume and plugin events to the event stream
+- Volume capabilities to the `nomad volume status` command output
+- The ability to use a volume ID prefix search and wildcard namespace with the
+  [`nomad volume delete` command](/nomad/commands/volume/delete). Refer to
+  the [GitHub pull request](https://github.com/hashicorp/nomad/pull/24997) for
+  details. Example usage:
+
+  ```shell-session
+  $ nomad volume create ./internal-plugin.volume.hcl
+  ==> Created host volume internal-plugin with ID aeea91a0-06df-c16e-5403-ff82a2f28fd4
+  ✓ Host volume "aeea91a0" ready
+
+    2025-01-31T15:55:14-05:00
+    ID        = aeea91a0-06df-c16e-5403-ff82a2f28fd4
+    Name      = internal-plugin
+    Namespace = default
+    Plugin ID = mkdir
+    Node ID   = b4611abd-d4a8-c83a-b05e-7d9f5b44a179
+    Node Pool = default
+    Capacity  = 0 B
+    State     = ready
+    Host Path = /run/nomad/dev/data/host_volumes/aeea91a0-06df-c16e-5403-ff82a2f28fd4
+
+  $ nomad volume delete -type host aeea91a0
+  Successfully deleted volume "aeea91a0-06df-c16e-5403-ff82a2f28fd4"!
+  ```
+
+### UI URL hints added to CLI commands
+
+We added UI URL hints to the end of common CLI commands and a `-ui` flag to
+automatically open the generated link in your browser.
+
+Showing UI URL hints is enabled by default. You have two options for turning off
+this feature:
+
+- Server: Modify the [`show_cli_hints`
+  parameter](/nomad/docs/configuration/ui#show_cli_hints) in your agent's `ui`
+  block configuration.
+- CLI: Set the `NOMAD_CLI_SHOW_HINTS` environment variable to `0` or `false`.
+
+  ```shell-session
+  $ nomad status
+  No running jobs
+
+  ==> View and manage Nomad jobs in the Web UI: https://localhost:4646/ui/jobs
+
+  $ export NOMAD_CLI_SHOW_HINTS=0
+  $ nomad status
+  No running jobs
+  ```
+
+### Breaking changes
+
+@include 'release-notes/v1-10/breaking-go-sdk.mdx'
+
+@include 'release-notes/v1-10/breaking-plugin-dir.mdx'
+
+@include 'release-notes/v1-10/breaking-vault-consul-token.mdx'
+
+@include 'release-notes/v1-10/breaking-consul-template.mdx'
+
+@include 'release-notes/v1-10/breaking-disconnect-fields-removed.mdx'
+
+@include 'release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx'
+
+@include 'release-notes/v1-10/breaking-sentinel-apply.mdx'
+
+@include 'release-notes/v1-10/breaking-affinity-spread.mdx'
+
+### Deprecations
+
+@include 'release-notes/v1-10/deprecate-variable-limits.mdx'
+
+### Upgrade details
+
+For more detailed information, refer to the [upgrade details
+page][upgrade] and the [GitHub releases changelogs][github-releases].
+
+### Known issues
+
+None.
+
+### Changelog
+
+- [v1.10.0](https://github.com/hashicorp/nomad/releases/tag/v1.10.0)
+
+
+[consul-integration]: /nomad/docs/secure/acl/consul
+[vault-integration]: /nomad/docs/secure/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[upgrade]: /nomad/docs/upgrade/upgrade-specific#nomad-1-10-0
+[github-releases]: https://github.com/hashicorp/nomad/releases/
+[pkjwt]: https://oauth.net/private-key-jwt/
+[pkce]: https://oauth.net/2/pkce/
+[oidc-concepts]: /nomad/docs/secure/authentication/oidc#client-assertions
+[oidc-trouble]: /nomad/docs/secure/authentication/oidc#oidc-configuration-troubleshooting
+[oidc-tutorial]: /nomad/docs/secure/authentication/sso-pkce-jwt
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-11-x.mdx b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-11-x.mdx
new file mode 100644
index 0000000000..b7bd093b19
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1-11-x.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: Nomad v1.11.x release notes
+description: >-
+  HashiCorp Nomad version 1.11.x release notes. Release highlights include client node identity, client node introduction, job specification secret block, and system job deployment support.
+---
+
+# Nomad 1.11.x release notes
+
+We are pleased to announce the following Nomad updates.
+
+## 1.11.0 release highlights
+
+### Client node introduction and identity
+
+Nomad's client node identity feature uniquely identities each Nomad client node
+and provides an authentication mechanism for nodes to make RPC calls to the
+Nomad servers.
+
+Introduce Nomad clients to the cluster with JWT tokens. Configure Nomad servers
+with introduction enforcement levels that dictate how clients join the cluster.
+This approach results in logs and metrics to detail introduction violations.
+Once registered, Nomad clients are now provided with an identity token, used for
+RPC communication which is periodically renewed.
+
+#### Relevant documentation
+
+- [Client node identity concepts](/nomad/docs/architecture/cluster/node-identity)
+- [Client identity node pool TTL configuration option](/nomad/docs/other-specifications/node-pool#node_identity_ttl)
+- [Client Introduction server configuration options](/nomad/docs/configuration/server#client_introduction-parameters)
+- [Client introduction monitoring detail](/nomad/docs/monitor#client-introduction)
+- [Client introduction agent CLI token flag](/nomad/commands/agent#client-intro-token)
+
+Commands:
+
+- [`nomad node intro create`](/nomad/commands/node/intro/create): Generates a node introduction token which is a signed JWT.
+- [`nomad node identity get`](/nomad/commands/node/identity/get): View the identity claims for a node.
+- [`nomad node identity renew`](/nomad/commands/node/identity/renew):  Instruct a node to renew its identity of its next heartbeat.
+- [`nomad node pool info`](/nomad/commands/node-pool/info): View the identity TTL for nodes in the provided pool.
+- [`nomad operator client-state`](/nomad/commands/operator/client-state): View
+  the client persistent state in JSON, which includes the client identity.
+- [`nomad agent` command's `-client-intro-token` parameter](/nomad/commands/agent#client-intro-token): Set the JWT token used  to authenticate with servers during the client's initial registration.
+
+API:
+
+- [`/v1/acl/identity/client-introduction-token`](/nomad/api-docs/acl/identities#create-client-introduction-identity): Generates a node introduction token which is a signed JWT.
+- [`/v1/client/identity`](/nomad/api-docs/client#read-a-node-s-identity-claims): View the identity claims for a node.
+- [`/v1/client/identity/renew`](/nomad/api-docs/client#renew-a-node-s-identity): Instruct a node to renew its identity of its next heartbeat.
+- [`/v1/node/pool/:node_pool`](/nomad/api-docs/node-pools#read-node-pool): View the identity TTL for nodes in the provided pool.
+
+### Artifact secrets
+
+Use the new job specification secrets block to fetch and interpolate secrets
+from a specified location. Nomad automatically retrieves the contents of the
+secret. In your task specification, reference the variable with
+`${secret.secret_name.key}` format.
+
+Nomad provides built-in support to fetch secrets from Nomad and
+Vault. Alternately, you may build your own custom secret provider.
+
+#### Relevant documentation
+
+- [Job specification `secret` block](/nomad/docs/job-specification/secret)
+- [Secret provider plugin authoring guide](/nomad/plugins/author/secret-provider)
+
+
+### System job deployments
+
+Jobs of type “system” now support deployment functionality, so you may roll out
+job updates in a more controlled manner. Additionally, you may now view system
+job deployment status in the web UI.
+
+#### Relevant documentation
+
+- [Job specification `update` block](/nomad/docs/job-specification/update)
+- [Blue/Green deployment detail](/nomad/docs/job-declare/strategy/blue-green-canary)
+- [`nomad deployment` commands](/nomad/commands/deployment) for interacting with Nomad job deployments
+
+### Scheduler improvements
+
+We improved Nomad's scheduler observability for job authors.
+
+#### Relevant documentation
+
+- [`nomad eval status` command](/nomad/commands/eval/status): View more details
+  on an evaluation including related evaluations, successful placements,
+  scheduler annotations, failed placements, and preemptions.
+
+   - The **Plan Annotations** table represents the intended plan before Nomad
+     checks nodes for feasibility. This can help you narrow down where in the
+     scheduling pipeline unexpected results are coming from.
+   - The [Nomad repository scheduler
+     README](https://github.com/hashicorp/nomad/blob/v1.11.0/scheduler/README.md)
+     has architectural details.
+- [`nomad alloc status` command](/nomad/commands/alloc/status): When you run the
+  command with the `-verbose` flag, the output includes information about the
+  scheduler's placement decision, including the number of nodes evaluated and
+  rejected, and the scoring of each node considered.
+
+### Additional census usage metrics <EnterpriseAlert inline/>
+
+We added several Enterprise reporting metrics.
+
+#### Relevant documentation
+
+- [Automated license utilization
+  reporting](/nomad/docs/enterprise/license/utilization-reporting)
+- Agent reporting configuration [`disable_product_usage_reporting`
+  parameter](/nomad/docs/configuration/reporting#disable_product_usage_reporting):
+  Disable detailed product usage metrics.
+- [`nomad operator utilization` command](/nomad/commands/operator/utilization):
+  If you have disabled automated reporting, use this command to manually
+  generate the report and send it to HashiCorp.
+
+### Upgrade details
+
+Refer to the [upgrade details
+page](/nomad/docs/upgrade/upgrade-specific#nomad-1-11-0) for more information.
+
+### Changelog
+
+Review improvements, security fixes, and breaking changes in the changelog.
+
+- [v1.11.0](https://github.com/hashicorp/nomad/releases/tag/v1.11.0)
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_8_x.mdx b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_8_x.mdx
new file mode 100644
index 0000000000..44c317c83a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_8_x.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: 1.8.x
+description: >-
+  HashiCorp Nomad version 1.8.x release notes. Long term support release. Exec2 task driver beta, transparent proxy support for Consul service mesh, Consul API Gateway for Nomad support, UI jobs page updates, time-based task execution, Sentinel policy management in the UI, nomad-bench.
+---
+
+# Nomad 1.8.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Long Term Support Release (Enterprise):** Nomad 1.8 introduces a [long term
+  support release](/nomad/docs/v1.8.x/enterprise#long-term-support-lts-releases) which
+  provides extended maintenance (two years of critical fixes provided through
+  minor releases and efficient upgrades (support for direct upgrades from one
+  LTS release to the next).
+
+- **Exec2 Task Driver (beta):** The `exec2` driver is used to execute a
+  command for a task. It offers a security model optimized for running
+  'ordinary' processes with very low startup times and minimal overhead in
+  terms of CPU, disk, and memory utilization. The `exec2` driver leverages
+  kernel features such as the Landlock LSM, cgroups v2, and the unshare system
+  utility. Due these enhancements, tasks no longer require leveraging
+  filesystem isolation based on chroot, which provide an enhanced security
+  profile and improved performance for the Nomad operator. Refer to [Exec2 Task
+  Driver](/nomad/plugins/drivers/exec2) for more details.
+
+- **Transparent proxy support for Consul service mesh:** Transparent Proxy
+  introduces a more seamless way of dialing upstream services when Consul service
+  mesh is enabled. Users can configure services to use transparent proxy with a
+  new [`transparent_proxy`](/nomad/docs/v1.8.x/job-specification/transparent_proxy)
+  block. When a service is configured to use transparent proxy, workloads can now dial the
+  service using a virtual IP Consul DNS name.
+
+- **Consul API Gateway for Nomad:** Consul API Gateway on Nomad is now
+  officially supported. A prescriptive job specification on
+  [hashicorp-guides/consul-api-gateway-on-nomad](https://github.com/hashicorp-guides/consul-api-gateway-on-nomad)
+  along with a supporting [tutorial](/nomad/tutorials/integrate-consul/deploy-api-gateway-on-nomad) on
+  how to securely deploy Consul API gateway on Nomad.
+
+- **Re-worked Jobs page in the web UI with live updates:** Within the [Jobs
+  index](/nomad/docs/monitor/inspect-workloads#list-jobs) page Nomad has
+  made a few improvements:
+
+  - **Prioritize showing the current state over historical state for jobs:**
+  Previously, long-garbage-collected allocation placement failures, lost nodes,
+  and other historical representations of job state were shown alongside
+  currently running allocations. In self-healing jobs, this often meant that a
+  healthy job looked like it had failures, when in fact Nomad had replaced or
+  rescheduled those failures. Now, the jobs list tries to show accurate
+  allocation information and meaningful statuses (like "Degraded", or
+  "Recovering") to better illustrate the current state of a job.
+
+  - **Server-side pagination:** For users with many thousands of jobs, the main
+  landing page for the web UI will no longer have a noticeable delay on
+  rendering. Users can control page length and filter paginated jobs
+  appropriately.
+
+  - **Live updates:** Previously, users had to manually refresh
+  the page to see newly created jobs, or to hide jobs that had been stopped and
+  garbage-collected. Now, the jobs list will update in real-time as jobs are
+  created, updated, or removed. Further, any changes to allocations of jobs
+  on-page will be reflected in the status of that job in real-time.
+
+- **Time based task execution (Enterprise) :** Using a CRON-like syntax, operators can now
+  [schedule](/nomad/docs/v1.8.x/job-specification/schedule) when tasks should execute
+  and when they should stop. This provides governance for tasks executed from
+  jobs, and allows operators to easily opt-in or opt-out of a schedule that
+  governs when the task can run through the web based UI or through the [CLI](/nomad/docs/v1.8.x/commands/alloc/pause).
+
+- **Sentinel policy management in the Web UI (Enterprise):** Enterprise users can manage
+  Sentinel policies directly within the Nomad UI. Users can create a Sentinel
+  policy based on a template provided from the UI or create policies directly
+  using an editor for Sentinel policies. Refer to [Sentinel
+  policies](/nomad/docs/govern/sentinel) to learn more about
+  how to use Sentinel within Nomad.
+
+- **nomad-bench:** Nomad now provides a testing framework through
+  [nomad-bench](https://github.com/hashicorp-forge/nomad-bench) which provisions
+  infrastructure used to run tests and benchmarks against Nomad test
+  clusters. The infrastructure consists of Nomad test clusters that each have a
+  set of servers with hundreds or thousands of simulated nodes created using
+  nomad-nodesim. The Nomad server processes are not simulated and are expected
+  to run on their own hosts, mimicking real-world deployments.  Metrics are then
+  gathered from the Nomad servers for use with benchmarking and load testing.
+
+## What's deprecated
+
+- **LXC Task driver:** The [Community LXC Task
+  Driver](/nomad/plugins/drivers/community/lxc) is now deprecated. Official
+  support will be removed and the repo will be archived when Nomad 1.9 is
+  released. Users are encouraged to migrate their workloads to another task
+  driver such as the built-in Docker task [driver](/nomad/docs/v1.8.x/drivers/docker).
+
+- **ECS Task driver:** The remote [ECS Task
+  Driver](/nomad/plugins/drivers/remote/ecs) is
+  now deprecated. Official support will be removed and the repo will be
+  archived when Nomad 1.9 is released. Users are encouraged to migrate their
+  workloads to Amazon ECS or to another Nomad task driver.
+
+- **`stop_after_client_disconnect`, `max_client_disconnect`,
+  `prevent_reschedule_on_lost`:** Nomad 1.8.0 introduces a
+  [disconnect](/nomad/docs/v1.8.x/job-specification/disconnect) block meant to group
+  all the configuration options related to disconnected client's and server's
+  behavior, causing the deprecation of the fields stop_after_client_disconnect,
+  max_client_disconnect and prevent_reschedule_on_lost. This block also
+  introduces new options for allocations reconciliation if the client regains
+  connectivity.
+
+- **32-bit builds**: Support for 32-bit architectures is now deprecated. Nomad
+  releases will no longer include binaries built for 32-bit platforms starting
+  with Nomad 1.9.
+
+## What's removed
+
+- **raw_exec option `no_cgroups`:** In Nomad 1.7.0 the raw_exec plugin option
+  for no_cgroups became ineffective. Starting in Nomad 1.8.0 attempting to set
+  the no_cgroups in raw_exec plugin configuration will result in an error when
+  starting the agent.
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/v1.8.x/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
+
+## Known issues
+
+The following issues are known to exist in the v1.8.x releases:
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.8.0](https://github.com/hashicorp/nomad/releases/tag/v1.8.0)
diff --git a/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_9_x.mdx b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_9_x.mdx
new file mode 100644
index 0000000000..5dd37782bb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/release-notes/nomad/v1_9_x.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 1.9.x
+description: >-
+  HashiCorp Nomad version 1.9.x release notes. Multi-Instance GPU (MIG) support, quotas for device resources, NUMA-aware scheduling, job versions, Virt task driver beta, Exec2 task driver GA, improved IPv6 support.
+---
+
+# Nomad 1.9.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Multi-Instance GPU (MIG) support added to the NVIDIA device driver**: This
+enhances Nomad’s ability to schedule workloads across your NVIDIA hardware and
+make full use of your GPU investment. The device driver automatically detects
+MIGs. Refer to the [NVIDIA driver docs](/nomad/plugins/devices/nvidia) for
+details.
+
+- **Quotas for device resources <EnterpriseAlert inline/>**: This release extends quotas to
+allow limiting [device resources](/nomad/docs/v1.9.x/job-specification/device). Refer
+to [Resource quotas](/nomad/docs/v1.9.x/other-specifications/quota) for configuration details.
+
+- **NUMA awareness for device resources <EnterpriseAlert inline/>**: Nomad is able to
+  correlate CPU cores with memory nodes and assign tasks to run on specific CPU
+  cores so as to minimize any cross-memory node access patterns. With Nomad 1.9,
+  we are expanding this functionality to also correlate
+  [devices](/nomad/docs/v1.9.x/concepts/plugins/devices) to memory nodes and enable
+  NUMA-aware scheduling to take device associativity into account when making
+  scheduling decisions. Refer to [numa
+  Block](/nomad/docs/v1.9.x/job-specification/numa) for configuration details.
+
+- **Golden job versions**: This feature introduces a way to preserve and compare
+  historical versions of a job. Prior to this, any change to a job would push
+  older versions into garbage collection. Now, you can tag a version to save it
+  from garbage collection. Additionally, you can compare job versions by tag
+  name and revert by tag name. Refer to [Job
+  versions](/nomad/docs/v1.9.x/concepts/job.mdx#job-versions) for details and links to
+  how to use job version tagging.
+
+- **Virt task driver (beta)**: The new Virt task driver uses
+  [libvirt](https://libvirt.org/) to manage virtual machines created by KVM,
+  Xen, VMware ESXi, QEMU, and other virtualization technologies. Using this
+  driver, you can perform the following:
+
+  - Start and stop a virtual machine and run a process on it.
+  - Assign a workload identity to the running task inside the virtual machine.
+  - Pass configuration values from Vault or other services using consul-template.
+  - Mount host directories into virtual machines to procure the allocation and task directories inside them.
+  - Configure port forwarding from the Nomad node to the virtual machine.
+  - Access the running task through the task API.
+
+  Refer to the [Virt driver docs](https://github.com/hashicorp/nomad-driver-virt)
+  for installation and usage guides.
+
+- **Exec2 Task Driver (GA):** The `exec2` driver is used to execute a command
+for a task. It offers a security model optimized for running 'ordinary'
+processes with very low startup times and minimal overhead in terms of CPU,
+disk, and memory utilization. The `exec2` driver leverages kernel features such
+as the Landlock LSM, cgroups v2, and the unshare system utility. Due these
+enhancements, tasks no longer require leveraging filesystem isolation based on
+chroot, which provide an enhanced security profile and improved performance for
+the Nomad operator. Refer to [Exec2 Task Driver](/nomad/plugins/drivers/exec2)
+for more details.
+
+- **Improved IPv6 support**: Nomad has improved support for Nomad's IPv6
+capabilities. We have tested and resolved some known issues with
+server-to-server and server-to-client communications. Additionally we have
+tested the Nomad CLI and UI service integrations with Consul and Vault, workload
+identity, service registration, host networking, bridge networking, and the
+Docker driver. More work will likely need to be done with IPv6 support as we
+explore integrations with Consul service mesh.
+
+
+## What's deprecated
+
+The following are deprecated and will be removed in 1.10.
+
+- Support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the Consul integration
+  guide][consul-integration] for details.
+- Support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the Vault integration guide][vault-integration] for
+  details.
+- Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+- Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+- Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+## What's removed
+
+- Support for HCLv1 job specifications and the `-hcl1` flag on `nomad job run` and other commands. Refer to [GH-20195](https://github.com/hashicorp/nomad/issues/20195) for more details.
+
+- Support for Nomad client agents older than v1.6.0. Older nodes will fail heartbeats. Nomad servers will mark the workloads on Nomad client agents older than 1.6.0 as lost and reschedule them normally according to the job's [reschedule](/nomad/docs/v1.9.x/job-specification/reschedule) block.
+
+- The [LXC task driver](https://github.com/hashicorp/nomad-driver-lxc) and [ECS
+  task driver](https://github.com/hashicorp/nomad-driver-ecs) projects have been
+  archived with the release of Nomad 1.9 and are no longer supported.  Both
+  plug-ins are maintained separately from the Nomad core project and are not
+  subject to the LTS program.
+
+- Nomad has removed the `tls_prefer_server_cipher_suites` agent configuration from the [`tls` block](/nomad/docs/v1.9.x/configuration/tls).
+
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/v1.9.x/upgrade/upgrade-specific#nomad-1-9-0) and the changelogs.
+
+## Known issues
+
+None.
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.9.0](https://github.com/hashicorp/nomad/releases/tag/v1.9.0)
+
+
+[consul-integration]: /nomad/docs/v1.9.x/integrations/consul/acl
+[vault-integration]: /nomad/docs/v1.9.x/integrations/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/v1.9.x/job-specification/disconnect
+[Resource Quotas]: /nomad/docs/v1.9.x/other-specifications/quota
diff --git a/content/nomad/v1.11.x/content/docs/scale/benchmarking.mdx b/content/nomad/v1.11.x/content/docs/scale/benchmarking.mdx
new file mode 100644
index 0000000000..eb545241d4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/scale/benchmarking.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Benchmark and load test Nomad
+description: |-
+  Use the Nomad Bench project to benchmark and load test Nomad servers.
+---
+
+# Benchmark and load test Nomad
+
+The Nomad Bench project provides reusable infrastructure automation to run test
+scenarios in order to collect metrics and data from Nomad clusters running at
+scale. The core goal of the project is to achieve reproducible large scale test
+scenarios so we can better understand how Nomad scales and uncover problems that
+are only detected in large cluster deployments. It is also used to perform
+release soak testing, among other things.
+
+The [repository][bench-repo] contains all the infrastructure and details to get
+started with your own load testing.
+
+[bench-repo]: https://github.com/hashicorp-forge/nomad-bench
diff --git a/content/nomad/v1.11.x/content/docs/scale/index.mdx b/content/nomad/v1.11.x/content/docs/scale/index.mdx
new file mode 100644
index 0000000000..d7c5ea59e6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/scale/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: docs
+page_title: Scale Nomad
+description: |-
+  This section provides information on Nomad Autoscaler and Nomad Bench.
+---
+
+# Scale Nomad
+
+This section provides information on the following standalone products:
+
+- Nomad Autoscaler, a horizontal application and cluster autoscaler
+  for Nomad.
+- Nomad Bench, a project that provides reusable infrastructure automation to
+run test scenarios in order to collect metrics and data from Nomad clusters
+running at scale.
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/bootstrap.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/bootstrap.mdx
new file mode 100644
index 0000000000..a6d39da0d3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/bootstrap.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: Bootstrap the ACL system
+description: |-
+  Enable and bootstrap the Nomad ACL system, deploy an anonymous policy, and create replication tokens for other regions.
+---
+
+# Bootstrap the ACL system
+
+Bootstrapping ACLs on a new cluster requires a few steps, outlined below. For
+multi-region clusters, you will perform the bootstrapping process on the
+authoritative region and set up replication.
+
+## Enable ACLs on Nomad servers
+
+The APIs needed to manage policies and tokens are not enabled until ACLs are
+enabled. To begin, you need to enable the ACLs on the servers. If a multi-region
+setup is used, the authoritative region should be enabled first. For each
+server:
+
+1. Set the [`enabled` value] of the [`acl` stanza] to true. The `acl` stanza is a
+   top-level stanza.
+
+```hcl
+acl {
+  enabled = true
+}
+```
+
+### Configure for multiple regions
+
+For multi-region configurations, you will also need to perform additional
+configuration. The regions must be joined before bootstrapping ACLs.
+If the non-authoritative region was already using ACLs, any existing tokens
+in that region will stop working after federation as they will be overwritten by the authoritative region.
+
+#### Set the authoritative region
+
+For all clusters in a multi-region setup, set the [`authoritative_region`
+value] in the [`server` stanza]. Later, you'll set the [`replication_token`
+value] of the [`acl` stanza]. You will learn how to generate management tokens
+later in this guide.
+
+### Reload your Nomad configuration
+
+Take care to restart the servers one at a time and to ensure each server has
+joined and is operating correctly before restarting another. You can use the
+[`nomad server members` command] to verify that a server is up and ready to
+handle requests.
+
+## Bootstrap and deploy anonymous policy
+
+Once the ACL system is enabled, you need to generate the initial token. This
+first management token is used to bootstrap the system. Care should be taken not
+to lose all of your management tokens. If you do, you will need to re-bootstrap
+the ACL subsystem.
+
+<Warning>
+
+Bootstrapping the ACL subsystem will interrupt access to your
+cluster. Once the [`nomad acl bootstrap` command] is run, Nomad's
+default-deny policy will become enabled. You should have an acceptable anonymous
+policy prepared and ready to submit immediately after bootstrapping.
+
+</Warning>
+
+### Stage an anonymous policy
+
+When the ACL system is enabled, Nomad starts with a default deny-all policy. This means that by default, no permissions are granted. For clients making requests without ACL tokens, you may want to create a transitional anonymous policy to allow traffic to your cluster while you are generating and distributing tokens to your users. This is done by setting rules on the special "anonymous" policy.
+
+<Warning>
+
+The anonymous policy assigns permissions to all unauthenticated requests to Nomad. We recommend using tokens with specific policies rather than an overly permissive anonymous policy. This guide uses it for illustrative purposes.
+
+</Warning>
+
+Create a file named `anonymous.policy.hcl`, add this content to the file, and save the file. This policy allows read-only access.
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["list-jobs", "read-job"]
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+host_volume "*" {
+  policy = "read"
+}
+```
+
+You can use this policy as a transitional anonymous policy, which will minimize time in which requests can not be submitted to the cluster once you bootstrap. Additional information is available for [node rules](/nomad/docs/other-specifications/acl-policy#node-rules), [agent rules](/nomad/docs/other-specifications/acl-policy#agent-rules), [operator rules](/nomad/docs/other-specifications/acl-policy#operator-rules), [quota rules](/nomad/docs/other-specifications/acl-policy#quota-rules), and [host volume rules](/nomad/docs/other-specifications/acl-policy#host-volume-rules).
+
+### Run the bootstrap command
+
+Once the ACL system is enabled, use the [`nomad acl bootstrap` command]:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Once the initial bootstrap is performed, it cannot be performed again unless the
+[reset] procedure is complete. Make sure to save this AccessorID and SecretID.
+The bootstrap token is a `management` type token, meaning it can perform any
+operation. It should be used to setup the ACL policies and create additional ACL
+tokens. The bootstrap token can be deleted and is like any other token, care
+should be taken to not revoke all management tokens.
+
+### Provide a CLI token
+
+If you attempt to run a command at this point without a token provided, you will
+encounter an error.
+
+```shell-session
+$ nomad status
+Error querying jobs: Unexpected response code: 403 (Permission denied)
+```
+
+Save the bootstrap token value to a file named `bootstrap.token`. Replace `BOOTSTRAP_SECRET_ID` in the following command with the Secret ID you received above.
+
+```shell-session
+$ echo "BOOTSTRAP_SECRET_ID" > bootstrap.token
+```
+
+Provide the token for CLI commands by setting the NOMAD_TOKEN environment variable to the bootstrap token value in the `bootstrap.token` file.
+
+```shell-session
+$ export NOMAD_TOKEN=$(cat bootstrap.token)
+```
+
+Run the [`nomad status` command]. It completes successfully because a token value is set.
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+### Deploy your anonymous policy
+
+Next, install the anonymous policy with the [`nomad acl policy apply` command].
+
+```shell-session
+$ nomad acl policy apply -description "Anonymous policy (full-access)" anonymous anonymous.policy.hcl
+Successfully wrote "anonymous" ACL policy!
+```
+
+Once this command has completed, requests to the cluster that do not present a token
+will use this policy.
+
+You can also use the Nomad API to submit policies as JSON objects. Consult the
+Nomad [`acl/policy` API] documentation for more information.
+
+#### Verify anonymous requests succeed
+
+Verify that the anonymous policy is performing as expected.
+
+Unset your NOMAD_TOKEN environment variable to send unauthenticated requests to your cluster.
+
+```shell-session
+$ unset NOMAD_TOKEN
+```
+
+Verify that the token is unset. This command returns an empty response.
+
+```shell-session
+$ echo ${NOMAD_TOKEN}
+
+```
+
+Check the status. This command succeeds without a token set because the anonymous policy has permissions to read job status.
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+### Delete the anonymous policy
+
+Once you have provided your users with tokens, you can update the anonymous
+policy to be more restrictive or delete it completely to deny all requests from unauthenticated users.
+
+Delete the anonymous policy. Set the `NOMAD_TOKEN` environment variable to the bootstrap token value again. This is necessary as the `nomad acl policy delete` command [requires the management token](/nomad/commands/acl/policy/delete).
+
+```shell-session
+$ export NOMAD_TOKEN=$(cat bootstrap.token)
+```
+
+Then, delete the anonymous policy.
+
+```shell-session
+$ nomad acl policy delete anonymous
+Successfully deleted anonymous policy!
+```
+
+## Enable ACLs on Nomad clients
+
+To enforce client endpoints, you need to enable ACLs on clients as well. Do this
+by setting the [`enabled` value] of the [`acl` stanza] to true. Once complete,
+restart the client to read in the new configuration.
+
+## Create management tokens for other regions
+
+Once you have bootstrapped ACLs on the servers of the authoritative region, you
+can create the replication tokens for all of the non-authoritative regions in a
+multi-region configuration. These tokens must be management-type tokens since
+they are used to communicate with ACL API in the authoritative region.
+
+Create the replication token with the [`nomad acl token create` command]. Don't
+forget to provide a management token via the NOMAD_TOKEN environment variable or
+the `-token` flag. As practice, this time use the `-token` flag:
+
+```shell-session
+$ nomad acl token create -type="management" -global=true \
+  -name="Cluster A Replication Token" \
+  -token="c999c4c2-6146-1bac-eb47-3958bbffe9d8"
+Accessor ID  = ec175d30-26ea-4a54-4850-45f833acece5
+Secret ID    = 9e2bb5ed-b3af-6bf3-5bbc-16dc684c5c31
+Name         = Cluster A Replication Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2020-01-08 21:12:43.32324673 +0000 UTC
+Create Index = 2916
+Modify Index = 2916
+```
+
+## Re-bootstrap ACL system
+
+If all management tokens are lost, it is possible to reset the ACL bootstrap so
+that it can be performed again. First, you need to determine the reset index
+with the bootstrap endpoint:
+
+```shell-session
+$ nomad acl bootstrap
+Error bootstrapping: Unexpected response code: 500 (ACL bootstrap already done (reset index: 7))
+```
+
+The error message contains the `reset index`. To reset the ACL system, create
+a file named `acl-bootstrap-reset` containing the value of the "reset index".
+This file should be placed in the data directory of the leader node:
+
+```shell-session
+$ echo 7 >> /nomad-data-dir/server/acl-bootstrap-reset
+```
+
+Once the reset file is in place, you can re-bootstrap the cluster:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 52d3353d-d7b9-d945-0591-1af608732b76
+Secret ID    = 4b0a41ca-6d32-1853-e64b-de0d347e4525
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 18:38:11.929089612 +0000 UTC
+Create Index = 11
+Modify Index = 11
+```
+
+If you attempt to bootstrap again you will get a mismatch on the reset index:
+
+```shell-session
+$ nomad acl bootstrap
+
+Error bootstrapping: Unexpected response code: 500 (Invalid bootstrap reset index (specified 7, reset index: 11))
+```
+
+This is because the reset file is in place, but with the former index. The reset
+file can be deleted. However, if it is left behind, Nomad will not reset the
+bootstrap unless the file's contents match the actual reset index.
+
+## Access an ACL-enabled web UI
+
+If you access the web UI without specifying an ACL token, Nomad grants you
+the permissions of the anonymous policy. You can set an ACL token in the web UI
+or with the CLI.
+
+### Provide a token in the web UI
+
+Open the web UI in your web browser with the cluster address and navigate to
+the `/ui` path. Click on the user icon in the top-right of the page to open the
+**Settings** page. Enter your ACL token in the **Secret ID** field and click
+the **Sign in with secret** button. You can also open this page directly by
+navigating to the `/ui/settings/tokens` path.
+
+### Provide a token with the CLI
+
+You can use the [`nomad ui` command](/nomad/commands/ui) and the token you have
+set for the Nomad CLI to authenticate to the web UI. This exchanges your ACL
+token for a one-time token in the web UI.
+
+```shell-session
+$ nomad ui -authenticate
+Opening URL "https://127.0.0.1:4646" with one-time token
+```
+
+## Next steps
+
+For a single cluster, the process is complete. For multi-region clusters, you
+can generate tokens local to each region to scope policies to a specific
+region, or use tokens with a Global scope so that you can submit jobs from any
+region to any other region.
+
+Now that you have learned about bootstrapping your Nomad cluster, you will learn
+more about how to create Nomad ACL policies.
+
+[`acl/policy` api]: /nomad/api-docs/acl/policies
+[`acl` stanza]: /nomad/docs/configuration/acl
+[`authoritative_region` value]: /nomad/docs/configuration/server#authoritative_region
+[`enabled` value]: /nomad/docs/configuration/acl#enabled
+[`nomad acl bootstrap` command]: /nomad/commands/acl/bootstrap
+[`nomad acl token create` command]: /nomad/commands/acl/token/create
+[`nomad server members` command]: /nomad/commands/server/members
+[`nomad status` command]: /nomad/commands/status
+[`replication_token` value]: /nomad/docs/configuration/acl#replication_token
+[`server` stanza]: /nomad/docs/configuration/server
+[reset]: /nomad/docs/secure/acl/bootstrap#re-bootstrap-acl-system
+[`nomad acl policy apply` command]: /nomad/commands/acl/policy/apply
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/consul.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/consul.mdx
new file mode 100644
index 0000000000..e646a3f4d1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/consul.mdx
@@ -0,0 +1,471 @@
+---
+layout: docs
+page_title: Integrate Consul ACL
+description: |-
+  Learn how to integrate Consul access control list (ACL) with Nomad workload identity. Learn how to migrate to using Nomad workload identity with Consul. Configure Consul so it can receive, validate, and trust workload identities from Nomad. Create binding and namespace rules. Review considerations for using the JSON Web Key Set (JWKS) URL.
+---
+
+# Integrate Consul ACL
+
+The [Consul ACL][consul_acls] system protects the cluster from unauthorized
+access. When enabled, both Consul and Nomad must be properly configured in
+order for their integrations to work.
+
+Nomad agents must be configured with their own Consul ACL token, and Consul
+must be configured to accept workload identities from tasks and services
+running in Nomad.
+
+Refer to the following for details on integrating Consul with Nomad:
+
+- [`consul` block in Agent configuration](/nomad/docs/configuration/consul) for
+  configuring Nomad and Consul.
+- [Consul networking integration guide](/nomad/docs/networking/consul) for
+  details on integrating Consul service discovery and service mesh.
+
+## Nomad Agents
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task or service's [Workload
+Identity][nomad_wid] to authenticate to Consul and obtain an ACL token specific
+to the service or task. When using Nomad workload identities, you no longer
+need to pass in a Consul ACL token to submit a job.
+
+By default, Nomad does not generate workload identities for services, and tasks
+only receive an identity that can be used to access data from Nomad itself,
+such as for reading [Variables][] from a [`template`][] block. To access
+Consul, jobs must have additional workload identities defined as [`identity`][]
+blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure Nomad servers with the [`consul.service_identity`][] and
+[`consul.task_identity`][] agent configuration. Upon job registration, the
+Nomad servers update tasks that have a [`consul`][] block and services that use
+the Consul service provider with these default identities.
+
+Job specifications that include [`template`][] blocks are not provided with
+default identities because Nomad is unable to decipher the contents of the
+template data. You must specify the identities required for Consul in the job
+specification. Refer to the [Workload Identities for Consul][jobspec_identity_consul]
+section of the `identity` block documentation for more information.
+
+You can also specify identities for Consul directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Consul][jobspec_identity_consul] section of the `identity` block
+documentation for more information.
+
+### Configuring Consul Authentication
+
+You must configure Consul so it can receive, validate, and trust workload
+identities from Nomad. Since they are encoded as [JSON Web Tokens (JWTs)][jwt],
+you must create a [JWT ACL auth method][consul_jwt_auth_method]. The auth
+method is an endpoint that Nomad can use to exchange workload identities for
+Consul ACL tokens.
+
+Refer to Consul's [Auth Methods Overview][consul_auth_methods] documentation
+for more information.
+
+#### Consul Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Consul servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Consul is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+Nomad cannot recreate Consul tokens that have been deleted. The auth method
+configuration should never set the `MaxTokenTTL` field. Consul tokens are
+local to the Consul datacenter unless you set `TokenLocality: "global"` in the
+auth method. We recommend using local tokens, which is the default. Global tokens
+require that the primary Consul datacenter is available when allocations start.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `JWKSURL` address must be reachable by all Consul servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `JWKSURL` value.
+
+[![Consul Auth Method][img_consul_auth_method]][img_consul_auth_method]
+
+When an allocation that needs access to Consul starts, the Nomad client running
+it exchanges the Nomad workload identities for tasks and services for Consul
+ACL tokens.
+
+[![Consul JWT Login][img_consul_wid_acl_token]][img_consul_wid_acl_token]
+
+The auth method also defines the list of authorized audience values, which must
+have at least one match with the values defined in the Nomad workload identity
+[`aud`][] parameter. For security reasons, it is recommended to only define a
+single audience value.
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced as dynamic values in Consul ACL configuration. The auth method
+determines which of these claims are made available to the rest of the
+configuration.
+
+<CodeBlockConfig highlight="6-9" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### Consul Binding Rules
+
+Consul auth methods use [binding rules][consul_binding_rules] to determine the
+set of policies applied to the generated ACL token. Nomad workload identities
+can be used in Consul for two main purpose: registering services and retrieving
+configuration values and service addresses from Consul using `template` blocks
+in tasks. Each purpose requires tokens with different permissions so Nomad
+requires two binding rules.
+
+The first binding rule associates the Consul ACL token with a [service
+identity][consul_si], allowing the token to register and manage the lifecyle of
+a given service. This binding rule is only applied to Nomad workload identities
+for services because they are the only ones that have a `nomad_service` claim.
+
+```shell-session
+$ consul acl binding-rule create \
+    -method 'nomad-workloads' \
+    -bind-type 'service' \
+    -bind-name '${value.nomad_service}' \
+    -selector '"nomad_service" in value'
+```
+
+The [`-bind-name`][] flag restricts the token to only be able to modify
+services with the same name as the one defined in the Nomad workload identity
+claim. The [`-selector`][] flag ensures this binding rule only applies to
+workload identities for services.
+
+The second binding rule associates the Consul ACL token with an [ACL
+role][consul_acl_role], which is a collection of [ACL
+policies][consul_acl_policy] that define what the token is authorized to do.
+This binding rule is applied to Nomad workload identities for tasks to access
+information from Consul. The exact ACL policy rules will depend on the level of
+access required by the tasks (typically, accessing service addresses and KV with
+[`template`][] blocks).
+
+```shell-session
+$ consul acl binding-rule create \
+  -method 'nomad-workloads' \
+  -bind-type 'role' \
+  -bind-name 'nomad-tasks-${value.nomad_namespace}' \
+  -selector '"nomad_service" not in value'
+```
+
+The `-bind-name` flag defines which role is used for the token. It may
+reference claim values from the Nomad workload identity to apply different
+roles to different tasks. Similarly to the binding rule for services, the
+`-selector` flag ensures this binding rule only applies to workload identities
+for tasks since they don't have the `nomad_service` claim.
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Consul Auth Overview][img_consul_auth]][img_consul_auth]
+
+The [`consul.service_auth_method`][] and [`consul.task_auth_method`][]
+configuration define the auth method used by Nomad to retrieve Consul ACL
+tokens for services and tasks.
+
+By default, they follow the structure described above and use a single auth
+method for both, but it is possible to use two different auth methods, provided
+the resulting Consul ACL token from each have the expected service identity and
+role applied.
+
+#### Consul Namespace Rules <EnterpriseAlert inline />
+
+Consul Enterprise supports multiple namespaces and Nomad Enterprise allows jobs
+to use the [`consul.namespace`][] parameter to register services and read KV
+data from different Consul namespaces.
+
+In Nomad Enterprise, workload identities for tasks and services placed within
+the scope of a `consul` block with a `namespace` value, have an additional claim
+called `consul_namespace` that represents the Consul namespace defined in Nomad
+for the workload. In a multi-namespace environment, you should configure the
+auth method to include the `consul_namespace` claim mapping.
+
+<CodeBlockConfig highlight="6" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "consul_namespace": "consul_namespace",
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+You should create the auth method and binding rules in the `default` Consul
+namespace and configure the auth method with a set of [`NamespaceRules`][].
+
+```shell-session
+$ consul acl auth-method create \
+  -name 'nomad-workloads' \
+  -type 'jwt' \
+  -config '@auth-method.json' \
+  -namespace-rule-selector '"consul_namespace" in value' \
+  -namespace-rule-bind-namespace '${value.consul_namespace}'
+```
+
+Similarly to binding rules, namespace rules have a [`Selector`][] expression to
+determine when the rule should be applied and a [`BindNamespace`][] value that
+defines the Consul namespace used.
+
+Auth methods with a namespace rule create Consul tokens in that Consul
+namespace. Binding rules with `-bind-type role` also target a role and
+associated policies in that same Consul namespace. So you should create the auth
+method and binding rules in the default Consul namespace, and the role and
+policies in the target Consul namespaces.
+
+<CodeBlockConfig highlight="9-11" filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    consul {
+      namespace = "prod"
+    }
+
+    service {
+      port     = "db"
+      name     = "redis"
+      provider = "consul"
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+If a `consul` block is not defined, then the workload identity will not have
+the `consul_namespace` claim, since Nomad is not able to determine which Consul
+namespace will be used.
+
+Refer to the [Consul Namespaces][int_consul_ns] section for more information.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Consul servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Consul and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Consul auth method.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Consul Servers Not Able to Connect to Nomad
+
+If the Consul servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`JWTValidationPubKeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Consul servers, and use that address as the value for
+`JWKSURL`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional References
+
+The [Consul ACL with Nomad Workload Identities][consul_tutorial_wid] tutorial
+provides guided instructions on how to configure Consul and Nomad for workload
+identities.
+
+The [`nomad setup consul`][nomad_cli_setup_consul] command and the
+[`hashicorp-modules/nomad-setup/consul`][tf_nomad_setup_consul] Terraform
+module can help you automate the process of applying configuration to a Consul
+cluster.
+
+## Migrating to Using Workload Identity with Consul
+
+Nomad version 1.7.0 introduced Workload Identity authentication, and deprecated
+token authentication.  Token authentication was then removed in Nomad 1.10.0.
+Migrating from the legacy (pre-1.7) workflow where workload use the agent's
+Consul token requires configuation on your Consul cluster and your Nomad server
+agents. It does not require updating your running Nomad jobs. To migrate:
+
+* Create the Consul auth method and binding rules on your Consul cluster.
+* Enable [`consul.service_identity`][] blocks in your Nomad server agent configurations.
+* Enable [`consul.task_identity`][] blocks in your Nomad server agent configurations.
+* (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+  different identity because of how your auth method and binding rules are
+  configured.
+
+Note that when using Workload Identity you will no longer need to pass in a
+Consul token to submit a job.
+
+[Variables]: /nomad/docs/concepts/variables
+[`-bind-name`]: /consul/commands/acl/binding-rule/create#bind-name
+[`-selector`]: /consul/commands/acl/binding-rule/create#selector
+[`BindNamespace`]: /consul/api-docs/acl/auth-methods#bindnamespace
+[`JWTValidationPubKeys`]: /consul/docs/security/acl/auth-methods/jwt#jwtvalidationpubkeys
+[`NamespaceRules`]: /consul/api-docs/acl/auth-methods#namespacerules
+[`Selector`]: /consul/api-docs/acl/auth-methods#selector
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[`consul.service_auth_method`]: /nomad/docs/configuration/consul#service_auth_method
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_auth_method`]: /nomad/docs/configuration/consul#task_auth_method
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`identity`]: /nomad/docs/job-specification/identity
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[consul_acl_policy]: /consul/docs/security/acl/acl-policies
+[consul_acl_role]: /consul/docs/security/acl/acl-roles
+[consul_acls]: /consul/docs/security/acl
+[consul_auth_methods]: /consul/docs/security/acl/auth-methods
+[consul_binding_rules]: /consul/api-docs/acl/binding-rules
+[consul_config_entry]: /consul/docs/connect/config-entries
+[consul_jwt_auth_method]: /consul/docs/security/acl/auth-methods/jwt
+[consul_si]: /consul/docs/security/acl/acl-roles#service-identities
+[consul_tutorial_wid]: /nomad/tutorials/integrate-consul/consul-acl
+[img_consul_auth]: /img/consul-integration-wi.png
+[img_consul_auth_method]: /img/consul-integration-auth-method.png
+[img_consul_wid_acl_token]: /img/consul-integration-wid-acl-token.png
+[int_consul_ns]: /nomad/docs/networking/consul#consul-namespaces
+[jobspec_identity_consul]: /nomad/docs/job-specification/identity#workload-identities-for-consul
+[jwt]: https://jwt.io/
+[nomad_cli_setup_consul]: /nomad/commands/setup/consul
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_consul]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/consul/
+[tutorial_mtls]: /nomad/docs/secure/traffic/tls
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/index.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/index.mdx
new file mode 100644
index 0000000000..9699bdcb09
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/index.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: ACL system overview
+description: |-
+  Explore the three major components of Nomad's Access Control Layer (ACL) system: capabilities, policies, and tokens.
+---
+
+# ACL system overview
+
+The ACL system is designed to be intuitive, high-performance, and to provide
+administrative insight. At the highest level, there are three major components to
+the ACL system: tokens, policies, and capabilities. The components are
+illustrated in the diagram below.
+
+[![Image showing that ACL Tokens refer to one or more associated policies and
+that those policies encapsulate capabilities like "Allow Submit Job" or "Allow
+Query Nodes"][img_acl_overview]][img_acl_overview]
+
+## Policies
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy must have a unique name, an optional description, and a rule set.
+The rules define the capabilities of a Nomad ACL token for accessing the objects
+in a Nomad cluster, objects like namespaces, node, agent, operator, quota, etc.
+A client ACL token can be associated with multiple policies; a request is
+allowed if _any_ of the associated policies grant the capability. Management
+tokens cannot be associated with policies because they are granted all
+capabilities.
+
+The special `anonymous` policy can be defined to grant capabilities to anonymous
+requests. An anonymous request is a request made to Nomad without the
+`X-Nomad-Token` header specified. This can be used to allow anonymous users to
+list jobs and view their status, while requiring authenticated requests to
+submit new jobs or modify existing jobs. By default, there is no `anonymous`
+policy set meaning all anonymous requests are denied.
+
+## Roles
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+## Capabilities
+
+Capabilities are the set of actions that can be performed. This
+includes listing jobs, submitting jobs, querying nodes, etc. A management token
+is granted all capabilities, while client tokens are granted specific
+capabilities via ACL policies. The full set of capabilities is discussed in the
+rule specifications.
+
+## Binding rules
+
+Policies are comprised of one or more rules. The rules define the capabilities  of a Nomad ACL token for accessing the objects in a Nomad cluster, objects    like namespaces, node, agent, operator, quota, etc.
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+<Note>
+  Binding rules are evaluated in no specific order, and should there be an
+  overlap in their selectors or scope, a "sum" of all the binding rules will be
+  applied, thus the least granular binding rules will always override the more
+  granular ones, as long as they apply to the same auth method and identity.
+</Note>
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+### Rules and scope
+
+The following table summarizes the rules that are available for constructing
+ACL policies:
+
+| Rule                             | Scope                                        |
+| -------------------------------- | -------------------------------------------- |
+| [agent][rules_agent]             | Utility operations in the Agent API          |
+| [host_volume][rules_host_volume] | Host Volume related operations               |
+| [namespace][rules_namespace]     | Job related operations by namespace          |
+| [node][rules_node]               | Node-level catalog operations                |
+| [operator][rules_operator]       | Cluster-level operations in the Operator API |
+| [plugin][rules_plugin]           | CSI Plugin related operations                |
+| [quota][rules_quota]             | Quota specification related operations       |
+
+Constructing policies from these rules is covered in detail in the
+[Nomad ACL Policy Concepts guide][acl-policy-guide].
+
+## Tokens
+
+ACL tokens are used to authenticate requests and determine if the caller is
+authorized to perform an action. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. Local tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+## Workload Identity
+
+Nomad allocations can receive workload identities in the form of a [JSON Web
+Token (JWT)][jwt]. The [Workload Identity concept page][workload identity] has
+more information on this topic.
+
+## Authentication methods
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+Since both the `oidc` and `jwt` auth methods ultimately operate on JWTs as
+bearer tokens, use the following to determine which method fits your use case:
+
+- **JWT**
+
+  - Ideal for machine-oriented, headless login where an operator may have already
+    arranged for a valid JWT to be dropped on a VM or provided to a container.
+  - User or application performing the Nomad login must have a valid JWT
+    to begin login.
+  - Does not require browser interaction.
+
+- **OIDC**
+
+  - Ideal for human-oriented, interactive login where an operator or administrator
+    may have deployed SSO widely and doesn't want to distribute Nomad ACL tokens
+    to every authorized user.
+  - User performing the Nomad login does not need a JWT.
+  - Requires browser interaction.
+
+## Multi-Region configuration
+
+Nomad supports multi-datacenter and multi-region configurations. A single region
+is able to service multiple datacenters, and all servers in a region replicate
+their state between each other. In a multi-region configuration, there is a set
+of servers per region. Each region operates independently and is loosely coupled
+to allow jobs to be scheduled in any region and requests to flow transparently
+to the correct region.
+
+When ACLs are enabled, Nomad depends on an "authoritative region" to act as a
+single source of truth for ACL policies and global ACL tokens. The authoritative
+region is configured in the [`server` stanza] of agents, and all regions must
+share a single authoritative source. Any ACL policies or global ACL tokens are
+created in the authoritative region first. All other regions replicate ACL
+policies and global ACL tokens to act as local mirrors. This allows policies to
+be administered centrally, and for enforcement to be local to each region for
+low latency.
+
+Global ACL tokens are used to allow cross-region requests. Standard ACL tokens
+are created in a single target region and not replicated. This means if a
+request takes place between regions, global tokens must be used so that both
+regions will have the token registered.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[acl-policy-guide]: /nomad/docs/secure/acl/policies
+[`server` stanza]: /nomad/docs/configuration/server
+[img_acl_overview]: /img/secure/acl.jpg
+[rules_agent]: /nomad/docs/secure/acl/policies#agent-rules
+[rules_host_volume]: /nomad/docs/secure/acl/policies#host-volume-rules
+[rules_namespace]: /nomad/docs/secure/acl/policies#namespace-rules
+[rules_node]: /nomad/docs/secure/acl/policies#node-rules
+[rules_operator]: /nomad/docs/secure/acl/policies#operator-rules
+[rules_plugin]: /nomad/docs/secure/acl/policies#plugin-rules
+[rules_quota]: /nomad/docs/secure/acl/policies#quota-rules
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/policies/create-policy.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/policies/create-policy.mdx
new file mode 100644
index 0000000000..4f64ff2bf3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/policies/create-policy.mdx
@@ -0,0 +1,444 @@
+---
+layout: docs
+page_title: Create ACL policies
+description: |-
+  Create and deploy Nomad ACL policies for application developers and production operators to implement the principle of least privilege.
+---
+
+# Create ACL policies
+
+In this guide, you will create Nomad ACL policies to provide controlled
+access for two different personas to your Nomad Cluster. You will use the sample
+job created with the `nomad init -short` command as a sample job.
+
+To complete this guide, you will need the following:
+
+- A Nomad cluster with the ACL system bootstrapped.
+
+- A management token. You can use the bootstrap token, however, for production
+  systems you should use an user-specific token.
+
+## Meet the personas
+
+In this guide, you will create policies to manage cluster access for two
+different user personas. These are contrived to suit the scenario, and
+you should design your ACL policies around your organization's specific needs.
+
+As a best practice, access should be limited as much as possible given the needs
+of the user's roles.
+
+<Tip title="Challenge">
+
+ Consider extending this scenario to include namespaces.
+
+</Tip>
+
+### Application Developer
+
+The application developer needs to be able to deploy an application into the
+Nomad cluster and control its lifecycle. They should not be able to perform any
+other node operations.
+
+Application developers are allowed to fetch logs from their running containers,
+but should not be allowed to run commands inside of them or access the filesystem for running workloads.
+
+### Production Operations
+
+The production operations team needs to be able to perform cluster
+maintenance and view the workload, including attached resources like
+volumes, in the running cluster. However, because the application
+developers are the owners of the running workload, the production
+operators should not be allowed to run or stop jobs in the cluster.
+
+## Write the policy rules
+
+### Application Developer policy
+
+Considering the requirements listed above, what rules should you add to your
+policy? Nomad will deny all requests that are not explicitly permitted, so focus
+on the policies and capabilities you would like to permit. However, be mindful
+of the coarse-grained permissions in `namespace` rules--they might grant more
+permissions than you need for your use case.
+
+> The application developer needs to be able to deploy an application into the Nomad cluster and control its lifecycle. They should not be able to perform any other node operations.
+
+> Application developers are allowed to fetch logs from their running containers, but should not be allowed to run commands inside of them or access the filesystem for running workloads.
+
+Recall that [`namespace` rules] govern the job application deployment behaviors
+and introspection capabilities for a Nomad cluster.
+
+First define the policy in terms of required capabilities. What capabilities
+from the available options will this policy need to provide to Application
+Developers?
+
+| Capability                                                                                                                                            | Desired |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| **deny** - When multiple policies are associated with a token, deny will take precedence and prevent any capabilities.                                | N/A     |
+| **list-jobs** - Allows listing the jobs and seeing coarse grain status.                                                                               | ✅      |
+| **read-job** - Allows inspecting a job and seeing fine grain status.                                                                                  | ✅      |
+| **submit-job** - Allows jobs to be submitted or modified.                                                                                             | ✅      |
+| **dispatch-job** - Allows jobs to be dispatched                                                                                                       | ✅      |
+| **read-logs** - Allows the logs associated with a job to be viewed.                                                                                   | ✅      |
+| **read-fs** - Allows the filesystem of allocations associated to be viewed.                                                                           | 🚫      |
+| **alloc-exec** - Allows an operator to connect and run commands in running allocations.                                                               | 🚫      |
+| **alloc-node-exec** - Allows an operator to connect and run commands in allocations running without filesystem isolation, for example, raw_exec jobs. | 🚫      |
+| **alloc-lifecycle** - Allows an operator to stop individual allocations manually.                                                                     | 🚫      |
+| **csi-register-plugin** - Allows jobs to be submitted that register themselves as CSI plugins.                                                        | 🚫      |
+| **csi-write-volume** - Allows CSI volumes to be registered or deregistered.                                                                           | 🚫      |
+| **csi-read-volume** - Allows inspecting a CSI volume and seeing fine grain status.                                                                    | 🚫      |
+| **csi-list-volume** - Allows listing CSI volumes and seeing coarse grain status.                                                                      | 🚫      |
+| **csi-mount-volume** - Allows jobs to be submitted that claim a CSI volume.                                                                           | 🚫      |
+| **list-scaling-policies** - Allows listing scaling policies.                                                                                          | 🚫      |
+| **read-scaling-policy** - Allows inspecting a scaling policy.                                                                                         | 🚫      |
+| **read-job-scaling** - Allows inspecting the current scaling of a job.                                                                                | 🚫      |
+| **scale-job** - Allows scaling a job up or down.                                                                                                      | 🚫      |
+| **sentinel-override** - Allows soft mandatory policies to be overridden.                                                                              | 🚫      |
+
+Remember that the coarse-grained `policy` value of a namespace rule is a list of
+capabilities.
+
+
+| policy value | capabilities                                                                                                                                                                                                                                                    |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`       | deny                                                                                                                                                                                                                                                            |
+| `read`       | list-jobs<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                     |
+| `write`      | list-jobs<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale`      | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+| `list`       | (grants listing plugin metadata only)                                                                                                                                                                                                                           |
+
+
+
+Express this in policy form. Create an file named `app-dev.policy.hcl` to write
+your policy.
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job","dispatch-job","read-logs"]
+}
+```
+
+Note that the namespace rule has `policy = "read"`. The **write** policy is not
+suitable because it is overly permissive, granting "read-fs", "alloc-exec", and
+"alloc-lifecycle".
+
+### Production Operations policy
+
+Consider the requirements listed above, what rules should you add to your
+policy? Nomad will deny all requests that are not explicitly supplied, so focus
+on the policies you would like to permit.
+
+> The production operations team needs to be able to perform cluster maintenance and view the workload, including attached resources like volumes, in the running cluster. However, because the application developers are the owners of the running workload, the production operators should not be allowed to run or stop jobs in the cluster.
+
+Recall that [`namespace` rules] govern the job application deployment behaviors
+and introspection capabilities for a Nomad cluster.
+
+First define the policy in terms of required capabilities. What capabilities
+from the available options will this policy need to provide to Production
+Operators?
+
+| Capability                                                                                                                                            | Desired |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| **deny** - When multiple policies are associated with a token, deny will take precedence and prevent any capabilities.                                | N/A     |
+| **list-jobs** - Allows listing the jobs and seeing coarse grain status.                                                                               | ✅      |
+| **read-job** - Allows inspecting a job and seeing fine grain status.                                                                                  | ✅      |
+| **submit-job** - Allows jobs to be submitted or modified.                                                                                             | 🚫      |
+| **dispatch-job** - Allows jobs to be dispatched                                                                                                       | 🚫      |
+| **read-logs** - Allows the logs associated with a job to be viewed.                                                                                   | 🚫      |
+| **read-fs** - Allows the filesystem of allocations associated to be viewed.                                                                           | 🚫      |
+| **alloc-exec** - Allows an operator to connect and run commands in running allocations.                                                               | 🚫      |
+| **alloc-node-exec** - Allows an operator to connect and run commands in allocations running without filesystem isolation, for example, raw_exec jobs. | 🚫      |
+| **alloc-lifecycle** - Allows an operator to stop individual allocations manually.                                                                     | 🚫      |
+| **csi-register-plugin** - Allows jobs to be submitted that register themselves as CSI plugins.                                                        | 🚫      |
+| **csi-write-volume** - Allows CSI volumes to be registered or deregistered.                                                                           | 🚫      |
+| **csi-read-volume** - Allows inspecting a CSI volume and seeing fine grain status.                                                                    | ✅      |
+| **csi-list-volume** - Allows listing CSI volumes and seeing coarse grain status.                                                                      | ✅      |
+| **csi-mount-volume** - Allows jobs to be submitted that claim a CSI volume.                                                                           | 🚫      |
+| **list-scaling-policies** - Allows listing scaling policies.                                                                                          | 🚫      |
+| **read-scaling-policy** - Allows inspecting a scaling policy.                                                                                         | 🚫      |
+| **read-job-scaling** - Allows inspecting the current scaling of a job.                                                                                | 🚫      |
+| **scale-job** - Allows scaling a job up or down.                                                                                                      | 🚫      |
+| **sentinel-override** - Allows soft mandatory policies to be overridden.                                                                              | 🚫      |
+
+Again, the coarse-grained `policy` value of a namespace rule is a list of
+capabilities.
+
+
+
+| policy value | capabilities                                                                                                                                                                                                                                                    |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`       | deny                                                                                                                                                                                                                                                            |
+| `read`       | list-jobs<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                     |
+| `write`      | list-jobs<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale`      | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+| `list`       | (grants listing plugin metadata only)                                                                                                                                                                                                                           |
+
+
+
+Express this in policy form. Create an file named `prod-ops.policy.hcl` to write
+your policy. The capabilities required over the Namespace API is captured with
+the `read` policy value.
+
+```hcl
+namespace "default" {
+  policy = "read"
+}
+```
+
+Operators will also need to have access to several other API endpoints: node,
+agent, operator. Consult the individual API documentation for more details on
+the endpoints.
+
+```hcl
+node {
+  policy = "write"
+}
+
+agent {
+  policy = "write"
+}
+
+operator {
+  policy = "write"
+}
+
+plugin {
+  policy = "list"
+}
+```
+
+Add all of these policy elements to your `prod-ops.policy.hcl` file and save it.
+
+## Upload the policies
+
+Use the `nomad acl policy apply` command to upload your policy specifications.
+Don't forget to provide a management token via the NOMAD_TOKEN environment
+variable or the `-token` flag. As practice, this time use the `-token` flag.
+
+Upload the "Application Developer policy."
+
+```shell-session
+$ nomad acl policy apply -description "Application Developer policy" app-dev app-dev.policy.hcl
+Successfully wrote "app-dev" ACL policy!
+```
+
+Upload the "Production Operations policy."
+
+```shell-session
+$ nomad acl policy apply -description "Production Operations policy" prod-ops prod-ops.policy.hcl
+Successfully wrote "prod-ops" ACL policy!
+```
+
+## Verify the policy
+
+In order to verify the policy works properly, you will need to create tokens and
+check the success case and the failure cases.
+
+Create an app-dev token. For this guide, pipe your output into the tee command
+to save it as `app-dev.token`.
+
+```shell-session
+$ nomad acl token create -name="Test app-dev token" -policy=app-dev -type=client | tee app-dev.token
+Accessor ID  = b8c67cb8-cc3b-2a7c-182a-0bc5dfc3a6ff
+Secret ID    = 17cadb8b-e8a8-2f47-db62-fea0c6a19602
+Name         = Test app-dev token
+Type         = client
+Global       = false
+Policies     = [app-dev]
+Create Time  = 2020-02-10 18:41:43.049735 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Next, create a prod-ops token, piping your output into the tee command to save
+it as `prod-ops.token`.
+
+```shell-session
+$ nomad acl token create -name="Test prod-ops token" -policy=prod-ops -type=client | tee prod-ops.token
+Accessor ID  = 4e3c1ac7-52d0-6c68-94a2-5e75f17e657e
+Secret ID    = 0be3c623-cc90-3645-c29d-5f0629084f68
+Name         = Test prod-ops token
+Type         = client
+Global       = false
+Policies     = [prod-ops]
+Create Time  = 2020-02-10 18:41:53.851133 +0000 UTC
+Create Index = 15
+Modify Index = 15
+```
+
+### Submit a job using each token
+
+First, set the active token to your test app-dev token. You can extract it from
+the files that you created above.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' app-dev.token)
+```
+
+Create the sample job with `nomad init`.
+
+```shell-session
+$ nomad init
+```
+
+Submit the sample job to your Nomad cluster.
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> Monitoring evaluation "0acad62d"
+    Evaluation triggered by job "example"
+    Allocation "8b54bf75" created: node "afcb4e20", group "cache"
+    Evaluation within deployment: "63bbb604"
+    Allocation "8b54bf75" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0acad62d" finished with status "complete"
+```
+
+Verify that the job starts completely using the `nomad job status` command.
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 2020-02-10T13:42:17-05:00
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 63bbb604
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       1        1       0        0          2020-02-10T13:52:17-05:00
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+8b54bf75  afcb4e20  cache       0        run      running  26s ago  25s ago
+```
+
+Switch to the prod-ops token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' prod-ops.token)
+```
+
+Try to stop the job; note that you are unable to do so.
+
+```shell-session
+$ nomad stop example
+Error deregistering job: Unexpected response code: 403 (Permission denied)
+```
+
+Switch back to the app-dev token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' app-dev.token)
+
+$ nomad stop example
+==> Monitoring evaluation "2571f9f9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "63bbb604"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2571f9f9" finished with status "complete"
+```
+
+Try again to stop the job; note that this time you are successful.
+
+```shell-session
+$ nomad stop example
+==> Monitoring evaluation "2571f9f9"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "63bbb604"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "2571f9f9" finished with status "complete"
+```
+
+### Stimulate GC on your cluster
+
+With the app-dev token still active, export your cluster address into a variable for convenience.
+
+```shell-session
+$ export NOMAD_ADDR=http://localhost:4646
+```
+
+Try to use the Nodes API to list out the Nomad clients in the cluster.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/nodes
+Permission denied
+```
+
+Set the active token to your test prod-ops token.
+
+```shell-session
+$ export NOMAD_TOKEN=$(awk '/Secret/ {print $4}' prod-ops.token)
+```
+
+Resubmit your Nodes API query. Expect to have a significant amount of JSON
+returned to your screen which indicates successful API call.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/nodes
+```
+
+## Challenge: Restrict anonymous users
+
+The bootstrapping guide provides a very permissive anonymous user policy to
+minimize user and workload impacts from Nomad's default deny-all policy. This
+allows cluster users and other submitting agents to continue to work while
+tokens are being created and deployed.
+
+As a challenge to yourself, consider the minimum viable set of permissions for
+anonymous users in your organization. Craft a policy that prevents user access
+to capabilities that are not in your user's critical path.
+
+## Clean up
+
+If you would like to remove the objects that you created in this guide, switch
+back to your management token and revoke the tokens that you created above using
+the accessors in the files.
+
+~> If you receive a "Permission denied" error when you are running the delete
+commands, ensure that you have loaded your management token back into the
+NOMAD_TOKEN environment variable.
+
+```shell-session
+$ nomad acl token delete $(awk '/Accessor/ {print $4}' prod-ops.token)
+Token 4e3c1ac7-52d0-6c68-94a2-5e75f17e657e successfully deleted
+```
+
+```shell-session
+$ nomad acl token delete $(awk '/Accessor/ {print $4}' app-dev.token)
+Token b8c67cb8-cc3b-2a7c-182a-0bc5dfc3a6ff successfully deleted
+```
+
+Next, remove the prod-ops and app-dev policies that you created.
+
+```shell-session
+$ nomad acl policy delete prod-ops
+Successfully deleted prod-ops policy!
+```
+
+```shell-session
+$ nomad acl policy delete app-dev
+Successfully deleted app-dev policy!
+```
+
+## Next steps
+
+Now that you have deployed your own policy into the cluster, you will learn
+about Nomad access tokens. Nomad users will need to provide tokens for
+non-anonymous requests. These tokens map to one or more ACL policies which
+define the accessible Nomad objects for that request.
+
+[`namespace` rules]: /nomad/docs/secure/acl/policies/#namespace-rules
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/policies/index.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/policies/index.mdx
new file mode 100644
index 0000000000..d3e0f1d6eb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/policies/index.mdx
@@ -0,0 +1,404 @@
+---
+layout: docs
+page_title: ACL policy overview
+description: |-
+  Become familiar with the coarse-grained rules and fine-grained capabilities that allow operators to allow or restrict access to different Nomad data and APIs.
+---
+
+# ACL policy overview
+
+Nomad provides an optional Access Control List (ACL) system which can be used
+to control access to data and APIs. The ACL system is capability-based,
+relying on tokens which are associated with policies to determine which fine
+grained rules can be applied.
+
+ACL policies are written using [HashiCorp Configuration Language (HCL)][hcl].
+This language is designed for human readability. The HCL interpreter also parses
+JSON which facilitates the use of machine-generated configuration.
+
+An ACL policy contains one or more rules. Rules contain coarse-grained policy
+dispositions. Rules typically have several policy dispositions:
+
+- `read`: allow the resource to be read but not modified
+
+- `write`: allow the resource to be read and modified
+
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+- `list`: allow the resource to be listed but not inspected in
+  detail. Applies only to plugins.
+
+Some rules, such as `namespace` and `host_volume`, also allow the policy designer to
+specify a policy in terms of a coarse-grained policy disposition, fine-grained
+capabilities, or a combination of the two.
+
+## ACL policy specification
+
+An ACL policy is a composition of one or more rules. Its specification in the
+HCL format looks like:
+
+```hcl
+# Allow read only access to the default namespace
+namespace "default" {
+  policy = "read"
+}
+
+# Allow writing to the `foo` namespace
+namespace "foo" {
+  policy = "write"
+}
+
+agent {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+```
+
+The JSON representation of the same policy:
+
+```json
+{
+  "namespace": {
+    "default": {
+      "policy": "read"
+    },
+    "foo": {
+      "policy": "write"
+    }
+  },
+  "agent": {
+    "policy": "read"
+  },
+  "node": {
+    "policy": "read"
+  },
+  "quota": {
+    "policy": "read"
+  }
+}
+```
+
+The [ACL Policy API][api_policy] allows either HCL or JSON to be used to define
+the content of the rules section. Because HCL is designed to be more
+operator-friendly and allows comments, this tutorial will use HCL for all examples
+and snippets.
+
+## Namespace rules
+
+Nomad allows operators to create multiple namespaces to provide granular access to cluster resources.
+
+The `namespace` rule controls access to a namespace. Namespaces contain the
+majority of the active work of the cluster [Jobs API][api_jobs],
+[Deployments API][api_deployments], [Allocations API][api_allocations], and
+[Evaluations API][api_evaluations].
+
+```hcl
+namespace "default" {
+  policy = "write"
+}
+
+namespace "sensitive" {
+  policy = "read"
+}
+```
+
+Namespace rules are keyed by the namespace name they apply to. When no namespace
+is specified, the "default" namespace is the one used. For example, the above
+policy grants write access to the default namespace, and read access to the
+sensitive namespace. To grant access to all namespaces, you can use the wildcard
+namespace (`"*"`). In addition to the coarse-grained `policy` disposition,
+the `namespace` stanza allows setting a more fine grained list of
+`capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status.
+
+- `parse-job` - Allows parsing a job from HCL to JSON.
+
+- `read-job` - Allows inspecting a job and seeing fine grain status.
+
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+
+- `dispatch-job` - Allows jobs to be dispatched
+
+- `read-logs` - Allows the logs associated with a job to be viewed.
+
+- `read-fs` - Allows the filesystem of allocations associated to be viewed.
+
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+
+- `csi-register-plugin` - Allows jobs to be submitted that register
+  themselves as CSI plugins.
+
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered.
+
+- `csi-read-volume` - Allows inspecting a CSI volume and seeing fine grain status.
+
+- `csi-list-volume` - Allows listing CSI volumes and seeing coarse grain status.
+
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume.
+
+- `list-scaling-policies` - Allows listing scaling policies.
+
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+
+- `scale-job`: Allows scaling a job up or down.
+
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+
+The coarse-grained policy dispositions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                    |
+| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`  | deny                                                                                                                                                                                                                                                            |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                      |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+
+<!-- markdownlint-enable -->
+
+When both the policy shorthand and a capabilities list are provided, the
+capabilities are merged. This policy adds the submit-job capability to the read
+policy disposition, which provide the list-job and read-job capabilities:
+
+```hcl
+# Allow reading resources within the "default" namespace as well as submitting
+# jobs to this namespace, without allowing access to view log output or inspect
+# the filesystem.
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+This policy could be expressed as:
+
+```hcl
+# Allow reading resources within the "default" namespace as well as submitting
+# jobs to this namespace, without allowing access to view log output or inspect
+# the filesystem.
+namespace "default" {
+  capabilities = [
+    "csi-read-volume",
+    "csi-list-volume",
+    "submit-job",
+    "list-jobs",
+    "read-job",
+    "parse-job",
+    "read-job-scaling",
+    "list-scaling-policies",
+    "read-scaling-policy",
+  ]
+}
+```
+
+Namespace definitions may also include wildcard symbols, also called globs,
+allowing a single policy definition to apply to a set of namespaces. For
+example, the below policy allows read access to most production namespaces, but
+allows write access to the "production-api" namespace, and rejects any access to
+the "production-web" namespace.
+
+```hcl
+namespace "production-*" {
+  policy = "read"
+}
+
+namespace "production-api" {
+  policy = "write"
+}
+
+namespace "production-web" {
+  policy = "deny"
+}
+```
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. Node rules are specified for all nodes using
+the `node` key:
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+There's only one node rule allowed per Nomad ACL Policy, and its value is set to
+one of the policy dispositions.
+
+## Agent rules
+
+The `agent` rule controls access to the utility operations in the [Agent
+API][api_agent], such as join and leave. Agent rules are specified for all
+agents using the `agent` key:
+
+```hcl
+agent {
+  policy = "write"
+}
+```
+
+There's only one agent rule allowed per Nomad ACL Policy, and its value is set
+to one of the policy dispositions.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator].
+Operator rules look like:
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+There's only one operator rule allowed per Nomad ACL Policy, and its value is
+set to one of the policy dispositions. In the example above, the token could be
+used to query the operator endpoints for diagnostic purposes but not make any
+changes.
+
+## Quota rules
+
+The `quota` policy controls access to the quota specification operations in the
+[Quota API][api_quota], such as quota creation and deletion. Quota rules
+are specified for all quotas using the `quota` key:
+
+```hcl
+quota {
+  policy = "write"
+}
+```
+
+There's only one quota rule allowed per Nomad ACL Policy, and its value is set
+to one of the policy dispositions.
+
+## Host Volume rules
+
+The `host_volume` policy controls access to mounting and accessing host volumes.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are keyed to the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes. In addition to the coarse grained policy specification, the
+`host_volume` stanza allows setting a more fine grained list of capabilities.
+This includes:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+- `deny` policy - ["deny"]
+
+- `read` policy - ["mount-readonly"]
+
+- `write` policy - ["mount-readonly", "mount-readwrite"]
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+<Note>
+
+ Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+</Note>
+
+## Plugin rules
+
+The `plugin` policy controls access to [CSI plugins][api_plugins],
+such as listing plugins or getting plugin status. Plugin rules are
+specified for all plugins using the `plugin` key:
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+There's only one plugin rule allowed per Nomad ACL Policy, and its
+value is set to one of the policy dispositions. In the example above,
+the token could be used to query the plugin endpoints for diagnostic
+purposes. Note that registering plugins is controlled by the
+`csi-register-plugin` policy for the plugin job's namespace.
+
+## Next steps
+
+Now that you have learned the basic building blocks of Nomad's ACL policies, the
+next section allows you to put this knowledge into practice.
+
+[hcl]: https://github.com/hashicorp/hcl/
+[api_agent]: /nomad/api-docs/agent
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_jobs]: /nomad/api-docs/jobs
+[api_node]: /nomad/api-docs/nodes
+[api_operator]: /nomad/api-docs/operator
+[api_quota]: /nomad/api-docs/quotas
+[api_policy]: /nomad/api-docs/acl/policies
+[api_plugins]: /nomad/api-docs/plugins
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/tokens/index.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/tokens/index.mdx
new file mode 100644
index 0000000000..ad4eb9cd62
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/tokens/index.mdx
@@ -0,0 +1,325 @@
+---
+layout: docs
+page_title: ACL tokens overview
+description: |-
+  Create a management token and a client token and use them to submit requests with the Nomad CLI.
+products_used:
+---
+
+# ACL tokens overview
+
+Nomad uses tokens to authenticate requests to the cluster. These tokens are
+created using the `nomad acl token create` command. When a token is being
+created, the operator can specify one or more policies to apply to the token.
+These policies determine if any action specified by the token bearer is
+authorized. This guide will demonstrate this process and teach you how to
+inspect existing tokens.
+
+If you completed the [Bootstrap Nomad ACL System][] guide, you generated a
+management token during bootstrap. For this guide, you will need to have
+either that token or another management token set in the NOMAD_TOKEN environment
+variable. Replace `BOOTSTRAP_SECRET_ID` in the following command with a
+bootstrap or management token:
+
+```shell
+## Store our token secret ID
+$ export NOMAD_TOKEN="BOOTSTRAP_SECRET_ID"
+```
+
+## Examine a token
+
+You can use the `nomad acl token self` command to get the information about your
+current token. Remember, you must have the token in the NOMAD_TOKEN environment
+variable or pass it in via the -token flag.
+
+```shell-session
+$ nomad acl token self
+Accessor ID  = 59baab4d-1c7b-9605-37e5-5690ec7e6c3a
+Secret ID    = 948bb149-8266-904d-8824-58b25529a8ca
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2020-01-23 18:51:33.446571 +0000 UTC
+Create Index = 9
+Modify Index = 9
+```
+
+### Token internals
+
+A token contains:
+
+- **Accessor ID** - The public identifier for a specific token. It can be
+  used to look up information about a token or to revoke a token.
+
+- **Secret ID** - Used to make requests to Nomad and should be kept private
+
+- **Name** (optional) - A user-supplied identifier.
+
+- **Type** - Shows the type of the token. Management tokens are used for
+  administration and can be thought of as root-level tokens. Client tokens are
+  used for applications and can have policies assigned to them at creation.
+
+- **Global** - (bool) Indicates whether or not the token was created with the
+  `--global` flag. Global tokens are replicated from the authoritative region to
+  other connected regions in the cluster.
+
+- **Policies** - ([string]) A list of the policies assigned to the token.
+
+- **Create Time** - Wall clock time on the Nomad server leader when the token
+  was generated.
+
+- **Create/Modification index** - Used by Nomad internally to determine when a
+  token was created and/or modified relative to other system events.
+
+### Token types
+
+You can observe in the output above that the token in question is a management
+token, but what is a Nomad token type?
+
+There are two types of tokens: management and client tokens.
+
+Management tokens can perform any action in your cluster. Because they allow all
+requests, they can not be associated with a policy.
+
+Client tokens are associated with one or more policies when they are created,
+and can perform an action if any associated policy allows it.
+
+Tokens can be associated with policies that do not exist, which is equivalent to
+granting no capabilities.
+
+### Token replication settings
+
+Nomad has two token types: local and global. Local tokens are created and stored
+within the current Nomad region. However, for multi-region clusters, you can
+also create global tokens which are created in the authoritative region and
+replicated to the other regions.
+
+Nomad creates local tokens by default. They can not be used for cross-region
+requests since they are not replicated between regions.
+
+When ACL tokens are created, you can optionally mark them as Global. Global
+tokens are created in the authoritative region and then replicate to all other
+regions.
+
+Use the `-global` flag on the [`nomad acl token create`][cli_create_token]
+command or set the ["Global" parameter] to `true` in your [Create Token API
+call][api_create_token] to create global tokens.
+
+### Token names
+
+Token names are optional information that is provided by the user at creation
+time. Token names can be used for human-readable values, like "Bootstrap Token"
+on tokens that Nomad creates during the bootstrap process. Token names are not
+required to be unique and can not be used for identification of a specific
+token.
+
+You can store up to 256 characters in the token name, so it can also be used for
+machine generated identifiers. You can use Unicode in this field as well:
+
+```shell-session
+$ nomad acl token create -name="🤞"
+Accessor ID  = c46ba94a-0653-4135-a5e7-aaa307e64e9b
+Secret ID    = 1783bc34-ad82-4f82-d36e-e2def1fe8453
+Name         = 🤞
+Type         = client
+Global       = false
+Policies     = []
+Create Time  = 2020-01-23 19:22:51.196728 +0000 UTC
+Create Index = 42
+Modify Index = 42
+```
+
+### Generate a management token
+
+Management tokens are necessary for working with the Nomad ACL API. You can have
+as many management tokens as you like. They are revocable at any time by another
+management token. However, if you lose all of your management tokens, you will
+have to re-bootstrap your ACL subsystem.
+
+Create a management token:
+
+```shell-session
+$ nomad acl token create -name="New Management Token" -type="management"
+Accessor ID  = a57be18f-31ed-a8f9-682c-be9b16d5db77
+Secret ID    = 775b2821-e0f4-3ad9-0f69-44d973daf737
+Name         = New ManagementToken
+Type         = management
+Global       = false
+Policies     = n/a
+Create Time  = 2020-01-23 19:32:25.078669 +0000 UTC
+Create Index = 53
+Modify Index = 53
+```
+
+Your token material will be different. Load this management token into your
+environment for the next step. Replace the token with the **Secret ID** from the
+output of the token create command.
+
+```shell-session
+$ export NOMAD_TOKEN=775b2821-e0f4-3ad9-0f69-44d973daf737
+```
+
+### Generate a client token
+
+The primary token type used in an ACL-enabled cluster is a "client" token.
+Client tokens allow you to specify one or more policies when creating a token.
+The policies determine what Nomad resources that the token-bearer has access to.
+
+Create a client token called "client1" that is associated with the policies
+"app1" and "app2". It does not matter that these policies do not yet exist.
+Nonexistent policies provide no capabilities to a token, but they will not cause
+an error.
+
+```shell-session
+$ nomad acl token create -name="client1" -policy="app1" -policy="app2"
+Accessor ID  = a7bef400-a66c-d163-52c4-5ff4978f19b8
+Secret ID    = 950e462b-b333-dd52-1e18-76837e9b97fa
+Name         = client1
+Type         = client
+Global       = false
+Policies     = [app1 app2]
+Create Time  = 2020-01-23 20:10:11.600915 +0000 UTC
+Create Index = 19
+Modify Index = 19
+```
+
+Generate a global token named "client2" that has access to the app2 policy.
+
+```shell-session
+$ nomad acl token create -name="client2" -global -policy="app2"
+Accessor ID  = ab3b15dc-1647-a81d-c637-90be45440d18
+Secret ID    = 6d164ce7-c8b8-82a2-a350-bb0bcb43010a
+Name         = client2
+Type         = client
+Global       = true
+Policies     = [app2]
+Create Time  = 2020-01-23 20:42:00.683964 +0000 UTC
+Create Index = 53
+Modify Index = 53
+```
+
+## Use a token
+
+You can provide a token for CLI commands in two ways:
+
+- Use the -token flag. Be mindful that flags must come before positional
+  parameters.
+
+  ```shell-session
+  $ nomad acl token self -token=05392bd8-bb8a-8f63-a405-53c87b0d7d63
+  ```
+
+  or
+
+  ```shell-session
+  $ nomad job run -token=05392bd8-bb8a-8f63-a405-53c87b0d7d63 example.nomad.hcl
+  ```
+
+- Set the NOMAD_TOKEN environment variable. An advantage of this approach is
+  that you do no longer have to be concerned with argument ordering.
+
+  ```shell-session
+  $ export NOMAD_TOKEN="«Token to use»"
+  $ nomad status
+  No running jobs
+  ```
+
+For direct API calls, you will need to supply the token using the
+"X-Nomad-Token" header. This can be paired nicely with the NOMAD_TOKEN
+environment variable or can be passed directly. This example requires you to
+have set the NOMAD_ADDR environment variable to the protocol, address, and port
+for your NOMAD API, e.g. `http://127.0.0.1:4646`.
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" ${NOMAD_ADDR}/v1/jobs
+[]
+```
+
+## Inspect a token via accessor
+
+Token accessors are the unique public identifier for a token. They can be safely
+stored in the clear and are used by management token-bearers to get information
+about a token, update a token, or revoke a token.
+
+Use the accessor for the "client1" token to inspect it.
+
+```shell-session
+$ nomad acl token info a7bef400-a66c-d163-52c4-5ff4978f19b8
+Accessor ID  = a7bef400-a66c-d163-52c4-5ff4978f19b8
+Secret ID    = 950e462b-b333-dd52-1e18-76837e9b97fa
+Name         = client1
+Type         = client
+Global       = false
+Policies     = [app1 app2]
+Create Time  = 2020-01-23 20:10:11.600915 +0000 UTC
+Create Index = 19
+Modify Index = 19
+```
+
+You can get this same data from the API:
+
+```shell-session
+$ curl --header "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  ${NOMAD_ADDR}/v1/acl/token/a7bef400-a66c-d163-52c4-5ff4978f19b8\?pretty
+{
+    "AccessorID": "a7bef400-a66c-d163-52c4-5ff4978f19b8",
+    "CreateIndex": 19,
+    "CreateTime": "2020-01-23T20:10:11.600915Z",
+    "Global": false,
+    "Hash": "bY2538leml33LX7mIIBYT2ngBDMhpie065x+4/pQWJ0=",
+    "ModifyIndex": 19,
+    "Name": "client1",
+    "Policies": [
+        "app1",
+        "app2"
+    ],
+    "SecretID": "950e462b-b333-dd52-1e18-76837e9b97fa",
+    "Type": "client"
+}
+```
+
+## Delete a token via accessor
+
+Sometimes a token needs to be revoked. You can do that by running the `nomad acl token delete` command and supplying the accessor of the token to revoke. You must
+use a management token to run this command.
+
+Clean up the three tokens you made in this guide. Switch to the first token you
+used in the start of the guide:
+
+```shell-session
+$ export NOMAD_TOKEN=«original token»
+```
+
+Run the `nomad acl token delete` command and pass in the accessor of the created
+tokens. The example output below uses the token IDs from the earlier examples.
+
+Revoke the client1 token.
+
+```shell-session
+$ nomad acl token delete a7bef400-a66c-d163-52c4-5ff4978f19b8
+Token a7bef400-a66c-d163-52c4-5ff4978f19b8 successfully deleted
+```
+
+Revoke client2.
+
+```shell-session
+$ nomad acl token delete ab3b15dc-1647-a81d-c637-90be45440d18
+Token ab3b15dc-1647-a81d-c637-90be45440d18 successfully deleted
+```
+
+Revoke the "New Management Token".
+
+```shell-session
+$ nomad acl token delete a57be18f-31ed-a8f9-682c-be9b16d5db77
+Token a57be18f-31ed-a8f9-682c-be9b16d5db77 successfully deleted
+```
+
+## Next steps
+
+Next, you will explore policy creation in Nomad through a scenario.
+
+["global" parameter]: /nomad/api-docs/acl/tokens#global
+[api_create_token]: /nomad/api-docs/acl/tokens#create-token
+[cli_create_token]: /nomad/commands/acl/token/create
+[bootstrap nomad acl system]: /nomad/docs/secure/acl/bootstrap
diff --git a/content/nomad/v1.11.x/content/docs/secure/acl/tokens/vault.mdx b/content/nomad/v1.11.x/content/docs/secure/acl/tokens/vault.mdx
new file mode 100644
index 0000000000..f0fe284932
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/acl/tokens/vault.mdx
@@ -0,0 +1,176 @@
+---
+layout: docs
+page_title: Generate tokens with Vault
+description: |-
+  Configure the Nomad secrets engine in Vault and retrieve Vault-managed tokens
+  for the Nomad ACL system.
+products_used:
+---
+
+# Generate tokens with Vault
+
+HashiCorp Vault has a secrets engine for generating short-lived Nomad tokens. As
+Vault has a number of authentication backends, it could provide a workflow where
+a user or orchestration system authenticates using an pre-existing identity
+service (LDAP, Okta, Amazon IAM, etc.) in order to obtain a short-lived Nomad
+token.
+
+~> HashiCorp Vault is a standalone product with its own set of deployment and
+configuration best practices. You should review the [Vault Deployment Guide]
+before deploying it in production.
+
+In order to configure Vault's Nomad secrets engine, you will need the following:
+
+- A Nomad cluster with bootstrapped ACL system.
+
+- A management token (You can use the bootstrap token; however, for production
+  systems you should use an integration-specific token)
+
+- A set of policies created in Nomad
+
+- An unsealed Vault server running v0.9.3 or later
+
+- For evaluation purposes, a Vault server in "dev" mode can be used.
+
+  ```shell-session
+  $ vault server -dev
+  ==> Vault server configuration:
+
+                       Cgo: disabled
+           Cluster Address: https://127.0.0.1:8201
+                Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", tls: "disabled")
+                 Log Level: info
+                     Mlock: supported: false, enabled: false
+          Redirect Address: http://127.0.0.1:8200
+                   Storage: inmem
+                   Version: Vault v0.8.3
+               Version Sha: a393b20cb6d96c73e52eb5af776c892b8107a45d
+
+  ==> WARNING: Dev mode is enabled!
+
+  In this mode, Vault is completely in-memory and unsealed.
+  Vault is configured to only have a single unseal key. The root
+  token has already been authenticated with the CLI, so you can
+  immediately begin using the Vault CLI.
+
+  The only step you need to take is to set the following
+  environment variables:
+
+      export VAULT_ADDR='http://127.0.0.1:8200'
+
+  The unseal key and root token are reproduced below in case you
+  want to seal/unseal the Vault or play with authentication.
+
+  Unseal Key: YzFfP...
+  Root Token: f84b587e-...
+  ```
+
+## Configure Nomad secrets engine
+
+Enable the [`nomad`][nomad_backend] secrets backend in Vault:
+
+```shell-session
+$ vault secrets enable nomad
+Success! Enabled the nomad secrets engine at: nomad/
+```
+
+For older versions of Vault, you might need to use the `vault mount` command instead.
+
+```shell-session
+$ vault mount nomad
+Successfully mounted 'nomad' at 'nomad'!
+```
+
+Once you have the Nomad secret backend enabled, configure access with Nomad's address and management token:
+
+```shell-session
+$ vault write nomad/config/access \
+    address=http://127.0.0.1:4646 \
+    token=adf4238a-882b-9ddc-4a9d-5b6758e4159e
+Success! Data written to: nomad/config/access
+```
+
+Vault secrets engines have the concept of roles, which are configuration units
+that group one or more Vault policies to a potential identity attribute, (e.g.
+LDAP Group membership). The name of the role is specified on the path, while the
+mapping to policies is done by naming them in a comma separated list, for
+example:
+
+```shell-session
+$ vault write nomad/role/role-name policies=policyone,policytwo
+Success! Data written to: nomad/role/role-name
+```
+
+Similarly, to create management tokens, or global tokens:
+
+```shell-session
+$ vault write nomad/role/role-name type=management global=true
+Success! Data written to: nomad/role/role-name
+```
+
+## Create Vault policy
+
+Create a Vault policy to allow different identities to get tokens associated
+with a particular role:
+
+```shell-session
+$ cat << EOF | vault policy write nomad-user-policy -
+path "nomad/creds/role-name" {
+  capabilities = ["read"]
+}
+EOF
+Policy 'nomad-user-policy' written.
+```
+
+If you have an existing authentication backend (like LDAP), follow the relevant
+instructions to create a role available on the [Authentication backends
+page](/vault/docs/auth). Otherwise, for testing
+purposes, a Vault token can be generated associated with the policy:
+
+```shell-session
+$ vault token create -policy=nomad-user-policy
+Key             Value
+---             -----
+token           deedfa83-99b5-34a1-278d-e8fb76809a5b
+token_accessor  fd185371-7d80-8011-4f45-1bb3af2c2733
+token_duration  768h0m0s
+token_renewable true
+token_policies  [default nomad-user-policy]
+```
+
+## Obtain and test Nomad token
+
+Finally obtain a Nomad Token using the existing Vault Token:
+
+```shell-session
+$ vault read nomad/creds/role-name
+Key             Value
+---             -----
+lease_id        nomad/creds/role-name/6fb22e25-0cd1-b4c9-494e-aba330c317b9
+lease_duration  768h0m0s
+lease_renewable true
+accessor_id     10b8fb49-7024-2126-8683-ab355b581db2
+secret_id       8898d19c-e5b3-35e4-649e-4153d63fbea9
+```
+
+Verify that the token is created correctly in Nomad, looking it up by its
+accessor:
+
+```shell-session
+$ nomad acl token info 10b8fb49-7024-2126-8683-ab355b581db2
+Accessor ID  = 10b8fb49-7024-2126-8683-ab355b581db2
+Secret ID    = 8898d19c-e5b3-35e4-649e-4153d63fbea9
+Name         = Vault test root 1507307164169530060
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-10-06 16:26:04.170633207 +0000 UTC
+Create Index = 228
+Modify Index = 228
+```
+
+Any user or process with access to Vault can now obtain short lived Nomad Tokens
+in order to carry out operations, thus centralizing the access to Nomad tokens.
+
+[nomad_backend]: /vault/docs/secrets/nomad
+[Vault deployment guide]: /vault/tutorials/day-one-raft/raft-deployment-guide
diff --git a/content/nomad/v1.11.x/content/docs/secure/authentication/jwt.mdx b/content/nomad/v1.11.x/content/docs/secure/authentication/jwt.mdx
new file mode 100644
index 0000000000..9691f4d25e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/authentication/jwt.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: JSON Web Token (JWT) Auth Method
+description: >-
+  Use the JWT auth method to authenticate to Nomad with a JSON web token and receive an ACL token with privileges based on JWT identity attributes. Learn how to configure the auth method parameters using this reference page and example configuration.
+---
+
+# JSON Web Token (JWT) Auth Method
+
+Use the `jwt` auth method to authenticate with Nomad by providing a
+[JWT](https://en.wikipedia.org/wiki/JSON_Web_Token) directly. The JWT is
+cryptographically verified using locally-provided keys, or, if configured, you may use an
+OIDC Discovery service to fetch the appropriate keys.
+
+Refer to [auth-method create] for the parameters required to create a JWT auth-method with a given verification method.
+
+## JWT Verification
+
+Nomad verifies JWT signatures against public keys from the issuer. This
+process uses one of these methods:
+
+- **Static Keys** - A set of public keys is stored directly in the
+  configuration.
+
+- **JWKS** - Configure a JSON Web Key Set ([JWKS](https://tools.ietf.org/html/rfc7517))
+  URL and optional certificate chain. Nomad fetches keys from
+  this endpoint during authentication.
+
+- **OIDC Discovery** - Configure an OIDC Discovery URL and optional certificate chain. Nomad fetches keys from this URL during authentication. When you use OIDC Discovery, Nomad applies OIDC validation criteria such as `iss` and `aud`.
+
+If you need multiple methods, create another auth method of this type
+with a different name.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[auth-method create]: /nomad/commands/acl/auth-method/create
diff --git a/content/nomad/v1.11.x/content/docs/secure/authentication/oidc.mdx b/content/nomad/v1.11.x/content/docs/secure/authentication/oidc.mdx
new file mode 100644
index 0000000000..6c7659ce02
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/authentication/oidc.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: OpenID Connect (OIDC) Authentication Method
+description: >-
+  Use the OIDC auth method type to authenticate to Nomad through a web browser with an OpenID Connect provider. Learn how to configure the authentication method parameters using this reference page and example configuration.
+---
+
+# OpenID Connect (OIDC) Authentication Method
+
+Use the `oidc` method to authenticate to Nomad with
+[OIDC](https://en.wikipedia.org/wiki/OpenID_Connect). This method allows
+authentication via a configured OIDC provider using the user's web browser.
+Initiate this method from the Nomad UI or the command line.
+
+## Prerequisites
+
+- General knowledge of [OIDC concepts](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1)
+- [Nomad Access Control List fundamentals][ACL Overview].
+
+Refer to [auth-method create] for the parameters required to create an OIDC auth-method.
+
+## JWT Verification
+
+Nomad uses OIDC discovery to verify JWT signatures against public
+keys from the issuer. Nomad first fetches keys from the OIDC
+Discovery URL during authentication and then applies OIDC
+validation criteria such as `iss` and `aud`.
+
+## OIDC Authentication
+
+Nomad includes two built-in OIDC login flows: the Nomad UI, and the CLI using
+[`nomad login`](/nomad/commands/login).
+
+### Redirect URIs
+
+Properly setting redirect URIs is an important part of OIDC auth method
+configuration. You must configure these in both Nomad and the OIDC
+provider, and these configurations must align.
+
+Specify the redirect URIs for an auth method with the
+`AllowedRedirectURIs` parameter in the auth method config. The Nomad UI
+and CLI use different redirect URIs, so you need to configure one or both,
+depending on your installation.
+
+**Note:** Redirect URI is used interchangeably with callback address.
+
+Logging in via the UI requires the redirect URI
+`http://{host:port}/ui/settings/tokens`.
+
+Logging in via the CLI requires the redirect
+URI `http://{host:port}/oidc/callback`.
+
+### OIDC Login
+
+#### Nomad UI
+
+1. Select one of the provider links in the Nomad homepage or navigate directly to `/ui/settings/tokens`.
+1. Click one of the buttons for your OIDC auth method of choice.
+1. Complete the authentication with the configured provider.
+
+#### CLI
+
+Execute the `nomad login -method=oidc` command to log in.
+If the `-oidc-callback-addr` flag is not specified, it will default to `localhost:4649`.
+
+```shell-session
+$ nomad login -method=oidc -oidc-callback-addr=<host:port>
+
+Complete the login via your OIDC provider. Launching browser to:
+
+    https://myco.auth0.com/authorize?redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&client_id=r3qXc2bix9eF...
+```
+
+Your browser opens to the generated URL to complete the provider's login.
+Enter the URL manually if the browser does not automatically open.
+
+### Client assertions
+
+Also known as "[private key JWT][]", client assertions offer a more secure
+authentication mechanism compared to client secrets.
+
+Instead of sending a simple secret, Nomad builds a JWT and signs it with
+an RSA private key (or HMAC) that the OIDC provider can verify with an
+associated public key (or the same HMAC). In this way, Nomad "asserts"
+that it is a valid OIDC client without sending any secret information over
+the network.
+
+Here are some partial [auth method configuration][] examples. They focus only
+on the client assertion feature; they are not complete, functional examples.
+
+#### Nomad keyring
+
+In this example for Keycloak, Nomad signs the JWT with its own internal private
+key. It sets the JWT's "kid" header as the key ID, as presented by Nomad's
+[jwks.json][] endpoint.
+
+This is arguably the most secure option, because only Nomad has the private key.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://your-keycloak-instance.com/realms/nomad",
+  "OIDCClientID": "{your-client-id}",
+  "BoundAudiences": ["{your-client-id}"],
+  "OIDCClientAssertion": {
+    "Audience": ["https://your-keycloak-instance.com/realms/nomad"],
+    "KeySource": "nomad"
+  }
+}
+```
+
+Notice the distinction between the two "audience" fields:
+* `BoundAudiences` is often the application client ID (Nomad being the client),
+  which Nomad verifies against what the OIDC provider sends to Nomad. Nomad
+  uses this to make sure that requests are for Nomad, and not some other client.
+  This applies to all OIDC configuration, not only client assertions.
+* `OIDCClientAssertion.Audience` is the OIDC provider, because that is the
+  target audience of the client assertion JWT. The provider uses this to make
+  sure that requests are for it and not some other provider. This is often the
+  same as the `OIDCDiscoveryURL`, so defaults to that. This applies to all
+  client assertion configuration.
+
+This option requires that the OIDC provider have network access to Nomad's JWKS,
+either directly or via proxy, but otherwise requires no extra management of key
+material beyond Nomad's built-in [keyring][key-management].
+
+#### User provided key
+
+This Microsoft Entra ID (formerly Azure Active Directory) example uses an RSA
+private key generated separately from Nomad to sign the JWT.
+- The `PemKey` value is the private RSA key contents in PEM format.
+- The `PemCert` value is the contents of an X509 certificate from the key or a
+  CA. Nomad uses this certificate to derive an [x5t#S256][] thumbprint header.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://login.microsoftonline.com/{tenant}/v2.0",
+  "OIDCClientID": "{app-client-id}",
+  "BoundAudiences": ["{app-client-id}"],
+  "OIDCClientAssertion": {
+    "KeySource": "private_key",
+    "KeyAlgorithm": "RS256",
+    "PrivateKey": {
+      "PemKey": "-----BEGIN RSA PRIVATE KEY-----\nMIIE...the-rest-of-the-key...uJ8fR\n-----END RSA PRIVATE KEY-----",
+      "PemCert": "-----BEGIN CERTIFICATE-----\nMIID...the-rest-of-the-cert...GUCk=\n-----END CERTIFICATE-----"
+    }
+  }
+}
+```
+
+Note that if you implement this approach, you must upload the certificate to
+the Entra ID app, so that when you try to log in, Entra ID can use the
+"x5t#S256" header to look up the public key that it has stored.
+
+You may also configure the key and/or certificate as filenames on disk on Nomad
+servers with the `PemKeyFile` and `PemCertFile` options, respectively. This
+approach lets you rotate your key/cert without needing to update the auth
+method, but the files must be present on the disk of any server that may become
+Nomad leader.
+
+Or, depending on your OIDC provider's requirements, you may provide the `KeyID`
+directly, instead of providing a certificate.
+
+This approach lets you bring your own RSA key for the following scenarios:
+- Your OIDC provider does not support JWKS
+- Your network topology does not allow connectivity between the provider and
+Nomad JWKS, even via proxy
+- You want a signing key that is specifically and only for this purpose.
+
+#### Client secret HMAC
+
+This example uses the `OIDCClientSecret` as an HMAC key to sign the JWT.
+This configuration is marginally more secure than a bare client secret, as the
+JWT is time-bound, and signed by the secret rather than sending the secret
+itself over the network. As with a normal client secret, both Nomad and the
+OIDC provider need to have the same secret.
+
+```json
+{
+  "OIDCDiscoveryURL": "https://your-oidc-provider.com/oidc-discovery-url",
+  "OIDCClientID": "your-client-id",
+  "OIDCClientSecret": "long-secret-id-has-to-be-at-least-32-bytes",
+  "OIDCClientAssertion": {
+    "KeySource": "client_secret"
+  }
+}
+```
+
+## OIDC Configuration Troubleshooting
+
+The amount of configuration required for OIDC is relatively small, but it can
+be tricky to debug why things aren't working. The following are tips for setting up OIDC:
+
+- Monitor the log output for the Nomad servers for important
+information about OIDC validation failures.
+
+- Ensure correct redirect URIs in Nomad and on the provider. URIs
+need to match exactly. Check http/https, 127.0.0.1/localhost,
+port numbers, and whether trailing slashes are present.
+
+- The `BoundAudiences` option is typically
+  not required. OIDC providers use the `client_id` as the audience and
+  OIDC validation expects this.
+
+- Check your provider for scopes that are required to receive all of
+  the information you need. You often need to request the scopes
+  `profile` and `groups`, which you may set with
+  `OIDCScopes=["profile", "groups"]` in the auth method configuration.
+
+- If you're seeing claim-related errors in logs, review the provider's docs
+  very carefully to see how they're naming and structuring their claims.
+  Depending on the provider, you may be able to construct a simple `curl`
+  [implicit grant](https://developer.okta.com/blog/2018/05/24/what-is-the-oauth2-implicit-grant-type)
+  request to obtain a JWT that you can inspect. This example decodes the
+  JWT located in the `access_token` field of a JSON response.
+
+      jq --raw-output '.access_token / "." | .[1] | @base64d' jwt.json
+
+- With debug level logging, use the [VerboseLogging] option in the auth
+  method configuration to log the received OIDC token. This can be helpful
+  when debugging provider setup and verifying that the received claims are
+  what you expect. Since claims data is logged verbatim and may contain
+  sensitive information, do not use this option in production.
+
+- For client assertions, if `VerboseLogging` is enabled, then the Nomad leader
+  server logs a JWT when the auth method is created, and when someone makes
+  a login attempt. These JWTs are not 100% identical to what gets sent to the
+  OIDC provider due to being time-bound, but you can check the JWT headers
+  and claims to compare with your OIDC provider's requirements.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[ACL Overview]: /nomad/docs/secure/acl
+[auth-method create]: /nomad/commands/acl/auth-method/create
+[private key jwt]: https://oauth.net/private-key-jwt/
+[auth method configuration]: /nomad/api-docs/acl/auth-methods
+[key-management]: /nomad/docs/manage/key-management
+[x5t#S256]: https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8
+[jwks.json]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[VerboseLogging]: /nomad/api-docs/acl/auth-methods#verboselogging
diff --git a/content/nomad/v1.11.x/content/docs/secure/authentication/sso-auth0.mdx b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-auth0.mdx
new file mode 100644
index 0000000000..3469ff6584
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-auth0.mdx
@@ -0,0 +1,357 @@
+---
+layout: docs
+page_title: Configure SSO with Auth0
+description: |-
+  Create and configure an Auth0 application for SSO in Nomad, set up Nomad
+  ACL policies and roles, and configure binding rules to assign user permissions
+  automatically.
+---
+
+# Configure SSO with Auth0
+
+OIDC authentication is useful when you want to deploy SSO widely in your
+organization and do not want to manage access solely with Nomad access control
+list (ACL) tokens.
+
+Once implemented, SSO enables an interactive login procedure that users may
+initiate from either the Nomad UI or CLI.
+
+In this guide, you configure [Auth0](https://auth0.com/) as an identity
+provider. Your configuration uses the user metadata in Auth0 to automatically
+grant permissions in Nomad ACL.
+
+This is a multi-step process that includes the following:
+
+- Configuring an application in Auth0 for Nomad integration
+- Creating a role and user in Auth0
+- Setting up Nomad ACL policies and roles to provide permissions to users
+- Using Nomad binding rules to automatically assign permissions to users based on their metadata values
+
+You should be familiar with Auth0 and the following Auth0 documentation:
+
+- [Understand How Metadata Works in User
+  Profiles](https://auth0.com/docs/manage-users/user-accounts/metadata)
+- [Manage User Metadata with the post-login Action
+  Trigger](https://auth0.com/docs/manage-users/user-accounts/metadata/manage-user-metadata)
+- [Login Trigger - Add user roles to ID and Access
+  tokens](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#add-user-roles-to-id-and-access-tokens)
+
+## Prerequisites
+
+In order to complete this guide, you need:
+
+- A Nomad cluster with ACLs enabled and bootstrapped. Refer to [Bootstrap the
+  ACL system](/nomad/docs/secure/acl/bootstrap) for instructions.
+- The [Nomad ACL management token](/nomad/docs/secure/acl/tokens#token-types)
+  for your cluster. Assign the value to an environment variable named
+  `NOMAD_TOKEN` in your local terminal session.
+- A valid [Auth0](https://auth0.com/) account.
+
+Refer to the [Nomad Quick Start tutorial](/nomad/tutorials/get-started) if you
+need to set up a cluster.
+
+## Set up Auth0
+
+1. Create a native application. Refer to the Auth0 [Create Applications
+   guide](https://auth0.com/docs/get-started/auth0-overview/create-applications)
+   for instructions.
+
+   - Note the **Domain**, **Client ID**, and **Client Secret** values. You use
+   these to configure an auth method in Nomad.
+   - Set the callback URLs that Auth0 uses to redirect the user after the
+      authentication process is complete. In the **Allowed Callback URLs**
+      field, enter the following:
+
+      - `<NOMAD_ADDRESS>/ui/settings/tokens`: This is the callback
+     address when you perform OIDC login with the Nomad web UI. If you are
+     running Nomad with a modified [HTTP
+     port](/nomad/docs/configuration#http-2), ensure that the UI address uses
+     this value.
+      - `http://localhost:4649/oidc/callback`: This is the callback address that
+     the Nomad CLI uses when you perform [OIDC login using the
+     CLI](https://developer.hashicorp.com/nomad/commands/login#examples).
+
+     In this example, the Nomad address is `http://3.145.29.13:4646`.
+
+      ```plaintext
+      http://3.145.29.13:4646/ui/settings/tokens,
+      http://localhost:4649/oidc/callback
+      ```
+
+1. Create a role called `engineering`. Refer to the the Auth0 [Create Roles
+   guide](https://auth0.com/docs/manage-users/access-control/configure-core-rbac/roles/create-roles)
+   for instructions.
+1. Create a user with a connection type of `Username-Password-Authentication`.
+   Assign the `engineering` role to that user. Refer to these Auth0 guides for
+   instructions:
+
+   - [Create Users](https://auth0.com/docs/manage-users/user-accounts/create-users)
+   - [Assign Roles to Users](https://auth0.com/docs/manage-users/access-control/configure-core-rbac/rbac-users/assign-roles-to-users)
+
+1. Create a [login
+   trigger](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger)
+   that adds user roles to the token that Auth0 sends back to Nomad.
+
+   1. Create a custom action to add custom claims to the token. Refer to the
+      Auth0 [Create an Action
+      section](https://auth0.com/docs/customize/actions/write-your-first-action#create-an-action)
+      for instructions.
+
+      Give your action these values:
+
+      - **Name**: `Nomad OIDC`
+      - **Trigger**: `Login/Post Login`
+
+      After you create the action, replace the `exports.onExecutePostLogin`
+      method with the method that sets a custom claim to [add user roles to the
+      tokens](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#add-user-roles-to-id-and-access-tokens).
+
+      ```javascript
+      exports.onExecutePostLogin = async (event, api) => {
+        const namespace = 'http://nomad.internal';
+        if (event.authorization) {
+          api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
+          api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
+        }
+      }
+      ```
+
+      You use the `http://nomad.internal` namespace to separate the claims that
+      are not part of the [JWT RFC](https://tools.ietf.org/html/rfc7519). The
+      namespace is arbitrary but must be unique. Auth0 enforces the presence of
+      a unique namespace by discarding claims that are not namespaced and not in
+      the RFC.
+
+      Click **Deploy** to deploy your Nomad OIDC action.
+
+   1. Create a [post-login
+      trigger](https://auth0.com/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger#login-post-login).
+
+      1. From the Auth0 dashboard for your Nomad application, click on
+      **Actions** and then **Triggers**.
+      1. Select **post-login**.
+      1. In the **Add Action** pane's **Custom** tab, select **Nomad OIDC** and
+      drag it to the **Post Login** canvas so that the flow is **Start** ->
+      **Nomad OIDC** -> **Complete**.
+      1. Apply your changes.
+
+      ![Auth0 UI configure callback flow](/img/secure/auth0-configure-callback-flow.png)
+
+
+## Create Nomad ACL policies and roles
+
+After the login procedure confirms the user's identity, it has to then give that
+user privileges when creating their ACL token. Auth methods in Nomad use binding
+rules, which enable Nomad's ACL system to assign privilege to a new token
+through ACL policies and roles.
+
+In order to assign a privilege to a token with an auth method, first
+define the privilege in a policy and then assign that policy to a role. In this
+way, the binding rule can reference the role by name.
+
+### Define policy for Auth0 users
+
+Create a policy named `engineering-read` to allow read-only access to the `“default”` namespace and
+node objects.
+
+Create a policy file named `default-read.hcl`, add the following configuration to it, and save the file.
+
+```hcl
+// Grants read access to the namespace “default”.
+namespace "default" {
+  policy = "read"
+}
+
+// Grants read access to Nomad nodes.
+node {
+  policy = "read"
+}
+```
+
+Submit the policy to Nomad.
+
+-> **Note**: Ensure that the NOMAD_TOKEN environment variable is set to your Nomad management token.
+
+```shell-session
+$ nomad acl policy apply engineering-read default-read.hcl
+Successfully wrote "engineering-read" ACL policy!
+```
+
+
+### Assign the policy to a role
+
+Next, create a role named `engineering-read` and link it to the policy.
+
+```shell-session
+$ nomad acl role create -name=engineering-read -policy=engineering-read
+ID           = fc6d21c9-31cf-fd12-fe9a-7636c07f2d97
+Name         = engineering-read
+Description  = <none>
+Policies     = engineering-read
+Create Index = 18
+Modify Index = 18
+```
+
+
+## Create the OIDC auth method for Nomad
+
+Create a configuration file named `auth-method-config.json` for the new auth
+method and add the following contents to it.
+
+<CodeBlockConfig filename="auth-method-config.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "https://<AUTH0_DOMAIN>/",
+  "OIDCClientID": "<AUTH0_CLIENT_ID>",
+  "OIDCClientSecret": "<AUTH0_CLIENT_SECRET>",
+  "BoundAudiences": ["<AUTH0_CLIENT_ID>"],
+  "AllowedRedirectURIs": [
+     "<NOMAD_ADDRESS>/ui/settings/tokens",
+     "http://localhost:4649/oidc/callback",
+  ],
+  "ListClaimMappings": {
+    "http://nomad.internal/roles": "roles"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Replace `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID`, and `AUTH0_CLIENT_SECRET` with the
+values for **Domain**, **Client ID**, and **Client Secret** that you noted in
+the [Set up your Auth0 application, role, and user
+section](#set-up-auth0).
+
+Make sure the `AllowedRedirectURIs` entries match the callback URLs you
+configured in Auth0.
+
+Create the auth method with the Nomad CLI or API.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the `nomad acl auth-method create` command to create the auth method. Note
+that the token time-to-live is set to five minutes. Refer to the [`nomad acl
+auth-method create` command reference](/nomad/commands/acl/auth-method/create)
+for a complete explanation of the options.
+
+```shell-session
+$ nomad acl auth-method create -type=OIDC \
+    -name=auth0 \
+    -default=true \
+    -max-token-ttl=5m \
+    -token-locality=global \
+    -config=@auth-method-config.json
+```
+
+</Tab>
+<Tab heading="API">
+
+Use the [ACL auth methods
+API](http://localhost:3000/nomad/api-docs/acl/auth-methods#create-auth-method)
+to create the auth method. The payload is the `auth-method-config.json` file.
+
+```shell-session
+$ curl -sL --header 'x-nomad-token: <MANAGEMENT_TOKEN>' --request POST \
+    <NOMAD_ADDRESS>/v1/acl/auth-method \
+    --data @auth-method-config.json
+```
+
+Replace the following placeholders:
+
+- `<MANAGEMENT_TOKEN>` with the value of your Nomad management token
+- `<NOMAD_ADDRESS>` with the address of your Nomad cluster, such as
+  `http://3.145.29.13:4646`
+
+</Tab>
+</Tabs>
+
+Once you have configured the auth method, you can automate permissions grants to
+users using the metadata you defined earlier. This means that once auth method
+trust is established, you can configure Nomad to bind attested identities to
+roles or services with no additional work beyond what is required to link the
+identity and the auth method. Configure this with Nomad binding rules.
+
+### Grant ACL role permissions with Auth0 app metadata
+
+Grant users in the `engineering` Auth0 role the Nomad ACL role named `engineering-read`.
+
+```shell-session
+$ nomad acl binding-rule create \
+    -auth-method=auth0 \
+    -bind-type=role \
+    -bind-name=engineering-read \
+    -selector='engineering in list.roles'
+```
+
+```plaintext hideClipboard
+ID           = afb29209-9a87-e042-1983-d4d0f70bf271
+Description  = <none>
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-read
+Create Time  = 2023-01-17 11:34:50.588734 +0000 UTC
+Modify Time  = 2023-01-17 11:34:50.588734 +0000 UTC
+Create Index = 22
+Modify Index = 22
+```
+
+This automatically associates every user with an `engineering` role in their
+Auth0 tokens to the Nomad `engineering-read` ACL Role associated with an ACL policy.
+
+## Log in with OIDC
+
+Now that the configuration is complete, log in to Nomad using Auth0.
+
+<Tabs>
+<Tab heading="CLI">
+
+Use the [`nomad login -method=auth0` CLI command](/nomad/commands/login) to log
+into Nomad. The `-oidc-callback-addr` parameter is optional and defaults to `locahost:4649`.
+
+```shell-session
+$ nomad login -method=auth0 -oidc-callback-addr=localhost:4649
+```
+
+The command redirects you to a browser page. When prompted, accept and authorize
+the Nomad access to your Auth0 App. Then log into Auth0 with
+the username and password that you created in the [Set up Auth0 section](#set-up-auth0).
+
+![Nomad UI post login page showing Signed in via OIDC](/img/secure/nomad-ui-oidc-signed-in.png)
+
+The CLI writes your ACL token to the console.
+
+```plaintext hideClipboard
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = f2e78673-cbe5-8a69-1ad1-d16c2b63e9bf
+Secret ID    = e3d937a3-fe2b-f144-8384-e4fcbe7e9a65
+Name         = OIDC-auth0
+Type         = client
+Global       = true
+Create Time  = 2023-01-17 11:40:36.48495 +0000 UTC
+Expiry Time  = 2023-01-17 11:50:36.48495 +0000 UTC
+Create Index = 17
+Modify Index = 17
+Policies     = []
+
+Roles
+ID                                    Name
+db1b4129-3b7b-f2f5-5118-b885a1ff226e  engineering-read
+```
+
+</Tab>
+
+<Tab heading="Nomad UI">
+
+Navigate to your Nomad web UI and click on the **Sign In** button. Then click
+the **Sign in with auth0** button to start the flow.
+
+![Nomad UI login page sso Auth0](/img/secure/nomad-ui-oidc-login-button.png)
+
+![Nomad UI login page sso Auth0](/img/secure/nomad-ui-oidc-login-form.png)
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.11.x/content/docs/secure/authentication/sso-pkce-jwt.mdx b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-pkce-jwt.mdx
new file mode 100644
index 0000000000..c1a3b3f8e6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-pkce-jwt.mdx
@@ -0,0 +1,1032 @@
+---
+layout: docs
+page_title: SSO with PKCE and private key JWT
+description: |-
+  Create and configure a Keycloak OIDC application for SSO in Nomad,
+  configure a Nomad auth method that uses PKCE and Private Key JWT, set up
+  Nomad ACL policies and roles, and configure binding rules to assign user
+  permissions automatically.
+---
+
+# SSO with PKCE and private key JWT
+
+OpenID Connect (OIDC) authentication lets you provide Nomad access control list (ACL) tokens to users when they log in using a single sign-on (SSO) provider.
+
+Nomad's OIDC SSO login feature includes these capabilities:
+- [Proof Key for Code Exchange](https://oauth.net/2/pkce/), also known as PKCE, adds extra security for both
+  traditional client secrets and client assertions.
+- [Private Key JWT](https://oauth.net/private-key-jwt/), also known as client assertions, is a more secure alternative to client secrets.
+
+These options offer extra security during the OIDC login flow. For a summary, refer to the [Nomad OIDC page](/nomad/docs/secure/authentication/oidc).
+
+To demonstrate how to use PKCE and Private Key JWT, this tutorial uses the open source [Keycloak identity provider application](https://www.keycloak.org/) running as a Nomad job. You will configure Nomad and Keycloak to automatically grant permissions in Nomad ACL, enable the Keycloak provider to require PKCE, and reconfigure the Keycloak provider to use client assertions.
+
+
+## Prerequisites
+
+For this tutorial, you will need:
+
+- The [Nomad CLI](/nomad/install) version 1.10.0 or higher installed locally
+- A Nomad v1.10 or higher cluster with ACLs enabled and bootstrapped, as well as:
+  - The ACL management token saved to the `NOMAD_TOKEN` environment variable
+  - Docker installed on the client node
+- [`openssl`](https://openssl-library.org/source/index.html) installed locally to generate client assertion certificates
+
+## Run Keycloak as a Nomad job
+
+This job specification [runs Keycloak in development mode](https://www.keycloak.org/nightly/server/containers#_trying_keycloak_in_development_mode) with the username `admin` and password `admin`. Copy the contents to a file and save the file as `keycloak.nomad.hcl`.
+
+<!--
+TODO: bug mentioned below in keycloak_tag variable
+- update version after this ships: https://github.com/keycloak/keycloak/commit/9ca134931b49932227b24a660cbdf926ba2f59bd
+- available tags: https://quay.io/repository/keycloak/keycloak?tab=tags
+-->
+
+<Tabs>
+
+<Tab group="mac" heading="MacOS">
+
+<CodeBlockConfig filename="keycloak.nomad.hcl">
+
+```hcl
+variable "keycloak_tag" {
+  default = "26.0.8" # newer versions have a certificate upload bug at the moment
+}
+
+job "keycloak" {
+  group "kc" {
+    network {
+      port "http" {
+        static = 8080
+      }
+    }
+    service {
+      name     = "keycloak"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "kc" {
+      driver = "docker"
+      config {
+        image        = "quay.io/keycloak/keycloak:${var.keycloak_tag}"
+        args         = ["start-dev", "--hostname", "http://${NOMAD_IP_http}:${NOMAD_PORT_http}"]
+        ports        = ["http"]
+        # note: keycloak config will be lost unless you use persistent storage.
+        #volumes = [
+        #  # /opt/keycloak-data on the host machine needs to be owned by user 1000
+        #  "/opt/keycloak-data:/opt/keycloak/data",
+        #]
+      }
+      env {
+        KC_BOOTSTRAP_ADMIN_USERNAME = "admin"
+        KC_BOOTSTRAP_ADMIN_PASSWORD = "admin"
+        PROXY_ADDRESS_FORWARDING    = true
+        KC_PROXY_HEADERS            = "xforwarded"
+      }
+      resources {
+        memory = 800
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+</Tab>
+
+<Tab group="linux" heading="Linux">
+
+<CodeBlockConfig filename="keycloak.nomad.hcl">
+
+```hcl
+variable "keycloak_tag" {
+  default = "26.0.8" # newer versions have a certificate upload bug at the moment
+}
+
+job "keycloak" {
+  group "kc" {
+    network {
+      mode = "host"
+      port "http" {
+        static = 8080
+      }
+    }
+    service {
+      name     = "keycloak"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "kc" {
+      driver = "docker"
+      config {
+        image        = "quay.io/keycloak/keycloak:${var.keycloak_tag}"
+        args         = ["start-dev", "--hostname", "http://${NOMAD_IP_http}:${NOMAD_PORT_http}"]
+        ports        = ["http"]
+        network_mode = "host"
+        # note: keycloak config will be lost unless you use persistent storage.
+        #volumes = [
+        #  # /opt/keycloak-data on the host machine needs to be owned by user 1000
+        #  "/opt/keycloak-data:/opt/keycloak/data",
+        #]
+      }
+      env {
+        KC_BOOTSTRAP_ADMIN_USERNAME = "admin"
+        KC_BOOTSTRAP_ADMIN_PASSWORD = "admin"
+        PROXY_ADDRESS_FORWARDING    = true
+        KC_PROXY_HEADERS            = "xforwarded"
+      }
+      resources {
+        memory = 800
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+</Tab>
+
+</Tabs>
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run keycloak.nomad.hcl
+```
+
+## Log in to Keycloak
+
+Retrieve the Keycloak web address and open it in your web browser. In the following example, the address is `192.168.1.201:8080`.
+
+```shell-session
+$ nomad service info keycloak
+Job ID    Address             Tags  Node ID   Alloc ID
+keycloak  192.168.1.201:8080  []    1885c25d  c7f18cc3
+```
+
+At the Keycloak sign in page, enter the username `admin` and the password `admin`, and then click **Sign In**. Keycloak loads the landing page for the **master realm** with the **Welcome to Keycloak** message.
+
+## Configure Keycloak
+
+You will now make the necessary configurations through the Keycloak web UI.
+
+### Create a realm
+
+In Keycloak, a _realm_ manages a set of users, credentials, roles, and groups. It is equivalent to a tenant.
+
+1. At the top left, click the dropdown list that displays **Keycloak** and **master** below it.
+1. Click **Create realm**.
+1. In **Realm name**, enter `Nomad`.
+1. Click **Create**.
+
+Keycloak creates a new realm, redirects you to the landing page for the Nomad realm, and displays the **Welcome to Nomad** message.
+
+### Create a group
+
+A group in Keycloak is a set of attributes and role mappings that you can apply to a user. Users in this group will be given permissions in Nomad.
+
+1. In the left navigation, click **Groups**.
+1. Click **Create group**.
+1. In **Name**, enter `engineering`.
+1. Click **Create**.
+
+### Create a user
+
+1. In the left navigation, click **Users**.
+1. Click **Create new user**.
+1. Enter the following values for each labelled field:
+
+    |Field name|Value|
+    |--|--|
+    |Username|`testuser`|
+    |Email|`testuser@example.com`|
+    |First Name|`Test`|
+    |Last Name|`User`|
+
+1. Click **Join Groups**.
+1. Select the check box for the `engineering` group.
+1. Click **Join**.
+1. Click **Create** to complete the process.
+
+Next, create a password for the new user.
+
+1. From the **User details** page, at the top, click **Credentials**.
+1. Click **Set password**.
+1. Enter `password` in the **Password** and **Password confirmation** fields.
+1. Turn off **Temporary**.
+1. Click **Save**.
+1. In the prompt that appears, click **Save password**.
+
+### Create a client scope
+
+Nomad checks the ID token response from Keycloak for a group. Keycloak adds this group to the response with a client scope.
+
+1. In the left navigation, click **Client scopes**.
+1. Near the top of the page, click **Create client scope**.
+1. For **Name** enter `scope-for-nomad`.
+1. Next to **Type**, click the dropdown and then select **Default**.
+1. Click **Save**.
+
+Keycloak redirects you to the **Client scope details** page.
+
+1. In the top navigation, click **Mappers**.
+1. Click **Configure a new mapper**.
+1. In the **Name** column, click **Group Membership**.
+1. In the **Add mapper** form, for the **Name**, enter `nomad-mapper`.
+1. For **Token Claim Name**, enter `kc-groups`.
+1. Click **Save**.
+
+### Create the client
+
+A client in Keycloak is an application or service that can request authentication of a user. Nomad is a client in Keycloak.
+
+1. In the left navigation, click **Clients**.
+1. Near the top of the page, click **Create client**.
+1. For **Client ID**, enter `nomad-oidc`.
+1. Click **Next** to continue.
+1. Turn on **Client authentication**.
+1. Click **Next** to continue.
+1. For **Valid redirect URIs**, enter `http://localhost:4649/oidc/callback`. Note that the port for this URI is `4649`. This URI is for login attempts with the Nomad CLI.
+1. Click **Add valid redirect URIs** to add another URI.
+1. Enter `https://localhost:4646/ui/settings/tokens`. Note that the port for this URI is `4646`. This URI is for login attempts with the Nomad web UI.
+
+   There are now two URI values in **Valid redirect URIs**. These
+   values are the location that Keycloak redirects users to after they log in.
+
+1. Click **Save**.
+
+### Verify scope for client
+
+1. From the **Clients** page, in the top navigation, click **Client scopes**.
+1. In the **Search by name** search field, enter `scope-for-nomad`.
+1. Click the button with the arrow to search. Note that the **Assigned type** for the `scope-for-nomad` client scope is set to **Default**.
+
+### View credentials
+
+Nomad requires a secret to verify that it has authorization to use this client in Keycloak.
+
+1. In the left navigation, click **Clients**.
+1. In the **Client ID** column, click **nomad-oidc** .
+1. At the top, click **Credentials**. The dropdown under **Client Authenticator** shows that Keycloak uses client ID and secret by default.
+1. Reveal the **Client Secret**.
+1. Copy this value and save it. You will use it in the next section.
+
+## Configure Nomad
+
+Nomad requires the following configuration to complete the set up with Keycloak:
+
+- An [auth method](/nomad/commands/acl/auth-method/create) using the Keycloak details
+- A policy and role to specify user permissions in Nomad
+- A binding rule to associate the Keycloak group to the Nomad role
+
+### Create an auth method
+
+Copy the following example configuration to a file and then replace these placeholder values:
+
+- `_KEYCLOAK_ADDRESS`: the address of the Keycloak service in Nomad, from the [Log in to Keycloak section of this tutorial](#log-in-to-keycloak).
+- `_KEYCLOAK_CLIENT_SECRET`: The client secret value from the [View credentials section of this tutorial](#view-credentials).
+
+Save the file as `auth-method-keycloak.json`.
+
+Note that the `ListClaimMappings` value maps the group `kc-groups` in Keycloak to a value that you will define in the Nomad binding rule named `keycloak_groups`.
+
+<CodeBlockConfig filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Ensure that the `NOMAD_TOKEN` environment variable is set to your Nomad management token, as only management tokens can create auth methods.
+
+<CodeBlockConfig>
+
+```shell-session
+$ nomad acl token self | grep Type
+Type         = management
+```
+
+</CodeBlockConfig>
+
+Create the auth method.
+
+```shell-session
+$ nomad acl auth-method create \
+  -type=OIDC \
+  -name=keycloak \
+  -default=true \
+  -max-token-ttl=5m \
+  -token-locality=global \
+  -config=@auth-method-keycloak.json
+```
+
+The command prints information about the auth method similar to the following example output.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Name              = keycloak
+Type              = OIDC
+Locality          = global
+Max Token TTL     = 5m0s
+Token Name Format = ${auth_method_type}-${auth_method_name}
+Default           = true
+Create Index      = 382
+Modify Index      = 382
+
+Auth Method Config
+
+JWT Validation Public Keys = <none>
+JWKS URL                   = <none>
+OIDC Discovery URL         = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID             = nomad-oidc
+OIDC Client Secret         = redacted
+OIDC Enable PKCE           = false
+OIDC Disable UserInfo      = false
+OIDC Scopes                = openid,scope-for-nomad
+Bound audiences            = nomad-oidc
+Bound issuer               = <none>
+Allowed redirects URIs     = http://localhost:4649/oidc/callback,https://localhost:4646/ui/settings/tokens
+Discovery CA pem           = <none>
+JWKS CA cert               = <none>
+Signing algorithms         = <none>
+Expiration Leeway          = 0s
+NotBefore Leeway           = 0s
+ClockSkew Leeway           = 0s
+Claim mappings             = <none>
+List claim mappings        = {kc-groups: keycloak_groups}
+```
+
+</CodeBlockConfig>
+
+### Create policy and role
+
+Create an ACL policy that grants access to the `default` namespace and Nomad nodes.
+
+First, create the policy file. Copy the following example policy to a file and save it as `engineering-policy.hcl`.
+
+```hcl
+namespace "default" {
+  capabilities = ["list-jobs"]
+}
+```
+
+Create the policy.
+
+```shell-session
+$ nomad acl policy apply engineering-policy engineering-policy.hcl
+Successfully wrote "engineering-policy" ACL policy!
+```
+
+Create a role and associate it to the policy.
+
+```shell-session
+$ nomad acl role create -name=engineering-role -policy=engineering-policy
+ID           = 6987c982-082d-35ac-aff3-57f24e5829a0
+Name         = engineering-role
+Description  = <none>
+Policies     = engineering-policy
+Create Index = 448
+Modify Index = 448
+```
+
+### Create binding rule
+
+Grant users in the `/engineering` Keycloak group the Nomad ACL role named `engineering-role`. Note the single quotes around the whole `selector` value and the backticks around the `/engineering` segment. These are important, as you must include `/` in the selector expression.
+
+```shell-session
+$ nomad acl binding-rule create \
+  -auth-method=keycloak \
+  -bind-type=role \
+  -bind-name=engineering-role \
+  -selector='`/engineering` in list.keycloak_groups'
+```
+
+The command prints information about the binding-rule similar to the following example output.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+ID           = b5d6bc45-0667-868e-7054-a75b45b6676f
+Description  = <none>
+Auth Method  = keycloak
+Selector     = "`/engineering` in list.keycloak_groups"
+Bind Type    = role
+Bind Name    = engineering-role
+Create Time  = 2025-03-25 20:39:25.923021 +0000 UTC
+Modify Time  = 2025-03-25 20:39:25.923021 +0000 UTC
+Create Index = 451
+Modify Index = 451
+```
+
+</CodeBlockConfig>
+
+## Log in to Nomad
+
+In your terminal session, log in to Nomad. You do not need additional arguments since the auth method included the `-default=true` flag. This command opens a web browser window to Keycloak and prompts you to sign in.
+
+```shell-session
+$ nomad login
+```
+
+Enter `testuser` in the **Username or email** field and `password` in the **Password** field.
+
+After a successful login, Keycloak redirects you to a page at `localhost:4649/oidc/callback` that contains text with the message `Signed in via your OIDC provider`.
+
+Open your terminal and note the output from the login command. You are now signed into Nomad via authentication with Keycloak.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+Accessor ID  = 3b45aa90-eeb7-7b55-11d6-fe5d597b1753
+Secret ID    = 83e70c65-54b4-e2a3-3158-6ab59b9bb989
+Name         = OIDC-keycloak
+Type         = client
+Global       = true
+Create Time  = 2025-03-26 14:02:27.365842 +0000 UTC
+Expiry Time  = 2025-03-26 14:07:27.365842 +0000 UTC
+Create Index = 39
+Modify Index = 39
+Policies     = []
+
+Roles
+ID                                    Name
+4d60501e-57c6-07ba-d06d-72f76ab1f650  engineering-role
+```
+
+</CodeBlockConfig>
+
+Refer to the [OIDC auth method page](/nomad/docs/secure/authentication/oidc#oidc-configuration-troubleshooting) for information about OIDC configuration and troubleshooting.
+
+### Test the token
+
+Copy the Secret ID from the output and use it to query Nomad for jobs status. In this example, the Secret ID is `83e70c65-54b4-e2a3-3158-6ab59b9bb989`.
+
+```shell-session
+$ NOMAD_TOKEN=83e70c65-54b4-e2a3-3158-6ab59b9bb989 nomad job status
+ID        Type     Priority  Status   Submit Date
+keycloak  service  50        running  2025-03-26T09:51:59-04:00
+```
+
+Copy the secret ID again and use it to query the status of the `keycloak` job. This command will fail because the OIDC token does not have the required permissions.
+
+```shell-session
+$ NOMAD_TOKEN=83e70c65-54b4-e2a3-3158-6ab59b9bb989 nomad job status keycloak
+Error querying job: Unexpected response code: 403 (Permission denied)
+```
+
+The `-max-token-ttl=5m` flag of the `nomad acl auth-method create` command sets the token validity to expire after five minutes. After the TTL expires, you must run `nomad login` again to get another valid token.
+
+## Enable PKCE
+
+PKCE is an extension to the [Authorization Code flow](https://oauth.net/2/grant-types/authorization-code/) to prevent CSRF and authorization code injection attacks. Beginning with Nomad v1.10.0, Nomad supports PKCE.
+
+To take advantage of the additional security of PKCE, you must enable it in Keycloak.
+
+1. Open the Keycloak web UI. To fetch the address, run `nomad service info keycloak`.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Advanced**.
+1. Scroll to **Advanced settings**.
+1. Find **Proof Key for Code Exchange Code Challenge Method**.
+1. Click the dropdown and then select **S256**.
+1. Scroll to the bottom of the page and then click **Save**.
+
+Keycloak now ensures that any authentication attempt uses PKCE. A login attempt with `nomad login` now returns an error.
+
+```plaintext
+Error performing login: Unexpected response code: 400
+  (invalid OIDC complete-auth request: 1 error occurred:
+        * missing code)
+```
+
+### Configure Nomad to enable PKCE
+
+Update the auth method configuration file to enable PKCE in Nomad. Add the highlighted section for `OIDCEnablePKCE` to the file and then save it.
+
+<CodeBlockConfig highlight="4" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method. Note that the output shows that PKCE is enabled.
+
+<CodeBlockConfig highlight="10">
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = redacted
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+</CodeBlockConfig>
+
+Log in with Nomad to confirm that the functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+## Enable client assertions
+
+A client assertion is a token provided by a client application to confirm the proof of the client's identity.
+
+Keycloak refers to client assertions as *signed JWT* or *signed JWT with client secret*. Nomad supports both methods. Client assertions provide additional security and function as an alternative to using client secrets.
+
+Nomad builds a JWT and signs it with a private key that the OIDC provider can verify with Nomad's accompanying public key. Nomad asserts that it is a valid OIDC client without sending any secret information over the network.
+
+1. Navigate to the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown.
+
+Take note of the available options: **Signed Jwt**, **Client Id and Secret**, **X509 Certificate**, and **Signed Jwt with Client Secret**.
+
+You have set up the **Client Id and Secret** authenticator. In the next section, you can choose how you want to set up a client assertion:
+- Signed JWT with the client secret
+- Signed JWT with Nomad's _built-in_ private key pair
+- Signed JWT with a _new_ private key pair
+
+<Tabs>
+
+<Tab heading="Client secret" group="client_secret">
+
+### Signed JWT with the client secret
+
+This authenticator method uses the client secret as a Hash-Based Message Authentication Code (HMAC) key to sign the client assertion JWT. Nomad sends the signed JWT to Keycloak instead of sending the secret itself over the network.
+
+Keycloak has the same client secret, which it uses to verify the JWT signature. Keycloak knows that Nomad must have the client secret, otherwise it would not have been able to use it to sign the JWT.
+
+To enable the **Signed Jwt with Client Secret** authenticator, complete the following steps:
+
+1. Open the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown  and then select **Signed Jwt with Client Secret**.
+1. Next to **Signature algorithm**, click the dropdown and then select **HS256**.
+1. Click **Save**. In the dialog that appears, click **Yes** to confirm the change.
+
+Attempting to log in with `nomad login` will cause an error as the request from Nomad is missing the `client_assertion_type`.
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Error performing login: Unexpected response code: 500
+  (failed to exchange token with provider: Provider.Exchange:
+  unable to exchange auth code with provider: oauth2:
+  "invalid_client" "Parameter client_assertion_type is missing")
+```
+
+</CodeBlockConfig>
+
+Update the auth method configuration file to enable the client assertion in Nomad. Add the highlighted section for `OIDCClientAssertion` to the file and then save it.
+
+The `"KeySource" = "client_secret"` instructs Nomad to use the `OIDCClientSecret` as a client assertion HMAC instead of a normal client secret.
+
+<CodeBlockConfig highlight="4-7" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientSecret": "_KEYCLOAK_CLIENT_SECRET",
+  "OIDCClientAssertion": {
+    "KeySource": "client_secret",
+    "Algorithm": "HS256"
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method. Note that the output now includes the client assertion attributes.
+
+<CodeBlockConfig highlight="12-15">
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = <none>
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = redacted
+OIDC Client Assertion KeySource = client_secret
+OIDC Client Assertion Algorithm = HS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+</CodeBlockConfig>
+
+Log in with Nomad to confirm that the functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+Accessor ID  = 001b3ac1-f238-3003-fc94-539fa824b9a9
+Secret ID    = redacted
+Name         = OIDC-keycloak
+Type         = client
+
+# ...
+
+Roles
+ID                                    Name
+19c19cbf-dd6a-6084-bca4-5505cb9028b8  engineering-role
+```
+
+</Tab>
+
+<Tab heading="Built-in key pair" group="builtin_keypair">
+
+### Signed JWT with the built-in key pair
+
+This authenticator method uses a private and public key to sign and verify the JWT. Nomad uses its private key to sign the JWT, and Keycloak uses Nomad's public key to verify the JWT.
+
+Keycloak sends a request to Nomad's JWKS URL to retrieve the public key so that it can verify that the JWT signature is from Nomad. Keycloak requires access to the JWKS URL either directly or through a proxy.
+
+#### Deploy the Nomad API proxy
+
+In this section, you will deploy an API proxy that uses [Nomad's task API](/nomad/api-docs/task-api) to serve the JWKS URL. The task API is convenient as an example, but be aware that it does not work on Windows. This tutorial uses HTTP as for demonstration purposes, but we recommend having a valid TLS certificate and using HTTPS for production implementations.
+
+Copy the following contents to a file and save the file as `jwks-proxy.nomad.hcl`.
+
+<CodeBlockConfig filename="jwks-proxy.nomad.hcl">
+
+```hcl
+variable "caddy_tag" {
+  # https://hub.docker.com/_/caddy
+  default = "2.9.1-alpine"
+}
+
+job "jwks-proxy" {
+  group "proxy" {
+    network {
+      mode = "host"
+      port "http" {
+        static = 4444
+      }
+    }
+    service {
+      name     = "jwks-proxy"
+      port     = "http"
+      provider = "nomad"
+    }
+    task "caddy" {
+      driver = "docker"
+      config {
+        image   = "caddy:${var.caddy_tag}"
+        command = "caddy"
+        args    = ["run", "--config", "${NOMAD_TASK_DIR}/Caddyfile"]
+        ports   = ["http"]
+      }
+      identity {
+        env = true # makes the api.sock unix socket and Nomad token
+      }
+      template {
+        # https://caddyserver.com/docs/caddyfile
+        destination     = "${NOMAD_TASK_DIR}/Caddyfile"
+        left_delimiter  = "[[" # for clarity
+        right_delimiter = "]]"
+        data = <<EOF
+:[[ env `NOMAD_PORT_http` ]] {
+	log {
+		output stdout
+	}
+	# only serve the jwks endpoint
+	reverse_proxy /.well-known/jwks.json {
+		to unix/[[ env `NOMAD_SECRETS_DIR` ]]/api.sock
+		# task api always requires a token, even though
+		# the jwks endpoint is unauthenticated.
+		header_up X-Nomad-Token "[[ env `NOMAD_TOKEN` ]]"
+	}
+}
+EOF
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Submit the proxy job to Nomad.
+
+```shell-session
+$ nomad job run jwks-proxy.nomad.hcl
+```
+
+Get the service address of the proxy.
+
+```shell-session
+$ nomad service info jwks-proxy
+Job ID      Address             Tags  Node ID   Alloc ID
+jwks-proxy  192.168.1.201:4444  []    1885c25d  668f188c
+```
+
+The JWKS URL consists of the the service address of the proxy and the path to the `jwks.json` file. In this example, the JWKS URL is `http://192.168.1.201:4444/.well-known/jwks.json`.
+
+Test connectivity to the JWKS URL.
+
+```shell-session
+$ curl http://192.168.1.201:4444/.well-known/jwks.json
+{"keys":[{"use":"sig","kty":"RSA","kid":"a33560ad-0321-8006-228d-cc759335609b","alg":"RS256","n":"this-is-the-public-key","e":"AQAB"}]}
+```
+
+#### Configure Keycloak with Nomad JWKS
+
+Perform these steps to configure Keycloak:
+
+1. Navigate to the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Credentials**.
+1. Next to **Client Authenticator**, click the dropdown and then select **Signed Jwt**.
+1. Next to **Signature algorithm**, click the dropdown and then select **Any algorithm**.
+1. Click **Save**. Then click **Yes** in the dialog that appears.
+1. At the top, click **Keys**.
+1. Turn on **Use JWKS URL**.
+1. For **JWKS URL**, enter the JWKS URL. In this tutorial, the JWKS URL is `http://192.168.1.201:4444/.well-known/jwks.json`.
+1. Click **Save**.
+
+#### Update the Nomad auth method configuration
+
+Update the auth method configuration file to enable the feature in Nomad. Add the highlighted section for `OIDCClientAssertion` to the file and then save it.
+
+Note that the configuration no longer contains any secret value. Nomad has the private key and Keycloak retrieves the public key at the JWKS URL.
+
+<CodeBlockConfig highlight="3-5" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientAssertion": {
+    "KeySource": "nomad"
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+Update the auth method.
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = http://192.168.1.201:4444/.well-known/jwks.json
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = <none>
+OIDC Client Assertion KeySource = nomad
+OIDC Client Assertion Algorithm = RS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+Log in with Nomad to confirm that functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+</Tab>
+
+<Tab heading="New key pair" group="new_keypair">
+
+### Signed JWT with a new key pair
+
+This authenticator method uses a new private and public keypair set to sign the JWT instead of Nomad's built-in one.
+
+You can use this method to manage the keys yourself, but it requires updating the keys manually in both Nomad and the OIDC provider.
+
+#### Generate a key and certificate
+
+Open your terminal and use `openssl` to generate a new private key.
+
+```shell-session
+$ openssl genrsa -out private.pem
+```
+
+Generate a certificate with the private key. Be sure to update the subject values in the `-subj` flag for your environment.
+
+```shell-session
+$ openssl req -new -x509 -key private.pem -days 365 \
+  -subj '/C=US/ST=CA/L=Example/O=ExampleOrg/OU=OrgUnit/CN=example.com' \
+  -out certificate.pem
+```
+
+#### Upload the certificate to Keycloak
+
+1. Open the Keycloak web UI.
+1. In the left navigation, click **Clients**.
+1. Under **Client ID**, click `nomad-oidc`.
+1. At the top, click **Keys**.
+1. Turn off **Use JWKS URL**.
+1. Click **Import**.
+1. Under **Archive format**, click the dropdown and then select **Certificate PEM**.
+1. Under **Import file**, click **Browse**. Navigate to the directory that contains the certificate file and then select it.
+1. Click **Import**. Keycloak automatically fills in the form field with the contents of the certificate.
+1. Click **Save**.
+
+#### Update Nomad with the key and certificate
+
+Open `auth-method-keycloak.json` in your text editor and add the `OIDCClientAssertion` block highlighted below to it. Copy the contents of the private key file and paste them into the value for the `PemKey` attribute. Copy the contents of the certificate key file and paste them into the value for `PemCert`.
+
+<CodeBlockConfig highlight="3-9" filename="auth-method-keycloak.json">
+
+```json
+{
+  "OIDCDiscoveryURL": "http://_KEYCLOAK_ADDRESS/realms/Nomad",
+  "OIDCClientAssertion": {
+    "KeySource": "private_key",
+    "PrivateKey": {
+      "PemKey": "-----BEGIN PRIVATE KEY-----[EXAMPLE_KEY_CONTENTS]-----END PRIVATE KEY-----",
+      "PemCert": "-----BEGIN CERTIFICATE-----[EXAMPLE_CERTIFICATE_CONTENTS]-----END CERTIFICATE-----"
+    }
+  },
+  "OIDCEnablePKCE": true,
+  "OIDCClientID": "nomad-oidc",
+  "BoundAudiences": ["nomad-oidc"],
+  "AllowedRedirectURIs": [
+    "http://localhost:4649/oidc/callback",
+    "https://localhost:4646/ui/settings/tokens"
+  ],
+  "OIDCScopes": [
+    "openid",
+    "scope-for-nomad"
+  ],
+  "ListClaimMappings": {
+    "kc-groups": "keycloak_groups"
+  },
+  "VerboseLogging": true
+}
+```
+
+</CodeBlockConfig>
+
+The contents must be on one line and cannot contain newline characters. You can use the `tr` command to remove newline characters if you are editing the files in your terminal.
+
+```shell-session
+$ tr -d '\n' < _KEY_OR_CERT_FILENAME
+```
+
+Save the file after you update both values.
+
+Update the auth method config to enable the feature in Nomad. Nomad uses the certificate to derive a special JWT header called [x5t#S256](https://datatracker.ietf.org/doc/html/rfc7515#section-4.1.8), which Keycloak uses to look up the public key it has saved.
+
+```shell-session
+$ nomad acl auth-method update -config @auth-method-keycloak.json keycloak
+Name              = keycloak
+Type              = OIDC
+
+# ...
+
+Auth Method Config
+JWT Validation Public Keys      = <none>
+JWKS URL                        = http://192.168.1.201:4444/.well-known/jwks.json
+OIDC Discovery URL              = http://192.168.1.201:8080/realms/Nomad
+OIDC Client ID                  = nomad-oidc
+OIDC Client Secret              = <none>
+OIDC Client Assertion KeySource = private_key
+OIDC Client Assertion Algorithm = RS256
+OIDC Client Assertion Audience  = http://192.168.1.201:8080/realms/Nomad
+OIDC Enable PKCE                = true
+OIDC Disable UserInfo           = false
+
+# ...
+```
+
+Log in with Nomad to confirm that functionality works.
+
+```shell-session
+$ nomad login
+Successfully logged in via OIDC and keycloak
+
+# ...
+```
+
+</Tab>
+
+</Tabs>
+
+Navigate back to the [Configure Keycloak for client assertions](#enable-client-assertions) section if you want to try out the other client assertion options.
+
+## Next Steps
+
+In this tutorial you learned how to configure Nomad and Keycloak to automatically grant permissions with Nomad's ACL system. Then you enabled the Keycloak provider to require PKCE and reconfigured Keycloak to use client assertions.
+
+To continue your learning, check out these resources:
+- Learn more about the [JWT Auth Method](/nomad/docs/secure/authentication/jwt) in Nomad.
+- Learn more about the [OIDC Auth method](/nomad/docs/secure/authentication/oidc) in Nomad.
+- Learn how to [use Vault as an OIDC
+  provider](/nomad/docs/secure/authentication/sso-vault) with Nomad.
diff --git a/content/nomad/v1.11.x/content/docs/secure/authentication/sso-vault.mdx b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-vault.mdx
new file mode 100644
index 0000000000..4c396af84a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/authentication/sso-vault.mdx
@@ -0,0 +1,584 @@
+---
+layout: docs
+page_title: Configure SSO with Vault
+description: |-
+  Configure Vault as an OIDC provider with authorization code flow and
+  configure Nomad as an OIDC client.
+---
+
+# Configure SSO with Vault
+
+Implementing zero-trust architecture requires providing identity-based access to
+services within an organization. OpenID Connect (OIDC) allows clients to confirm
+their identity through an identity provider. **Vault 1.9.0** introduced the
+ability to configure Vault as an OIDC identity provider with authorization code
+flow, and **Nomad 1.5.0** introduced support for OIDC as a single sign-on
+method. With Nomad 1.5.0, you can use OIDC to authenticate users and map their
+permissions to Nomad ACL roles and policies.
+
+In this guide, you will setup Vault as an OIDC provider and Nomad as its
+client.
+
+-> **Note:** Nomad operates as a confidential OIDC client in this guide. To
+   configure a public OIDC client, refer to the [OIDC
+   Provider](/vault/docs/concepts/oidc-provider#public) documentation.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have:
+
+- A Nomad environment. Refer to the [get started](/nomad/tutorials/get-started) tutorials to install Nomad and create a cluster.
+
+- A Vault environment of **version 1.10** or later. Refer to the [Vault install guide](/vault/install) to install Vault locally
+  or [create a Vault cluster on HCP](/vault/tutorials/cloud/get-started-vault).
+
+  -> **NOTE:** This feature was first introduced in Vault 1.9 as a Technical
+  Preview feature. As of Vault 1.10, it is generally available.
+
+### Policy requirements
+
+For the purpose of this guide, you will use the `root` token to work with Vault
+running in development mode.
+
+When you are working with a non-development Vault environment, your token policy
+must include the following permissions:
+
+```hcl
+# To create an entity and entity alias. Enable and configure Vault as an OIDC provider
+path "identity/*" {
+  capabilities = [ "create", "read", "update", "delete", "list" ]
+}
+
+# To enable userpass auth method
+path "sys/auth/userpass" {
+  capabilities = [ "create", "read", "update", "delete" ]
+}
+
+# To create a new user, "end-user" for userpass
+path "auth/userpass/users/*" {
+   capabilities = [ "create", "read", "update", "delete", "list" ]
+}
+```
+
+Refer to the [Vault policies tutorial](/vault/tutorials/policies/policies) for more information.
+
+## Start Vault
+
+<Tabs>
+<Tab heading="Vault" group="oss">
+
+In your terminal, start a Vault development server with `root` as the root token.
+
+```shell-session
+$ vault server -dev -dev-root-token-id root
+```
+
+The Vault development server defaults to running at `127.0.0.1:8200`. The server is now
+initialized and unsealed.
+
+<Warning>
+
+ Do not run a Vault development server in production. This
+approach starts a Vault server with an in-memory database and is only for testing purposes.
+
+</Warning>
+
+Open another terminal session, and export an environment variable for the address to the Vault server.
+
+```shell-session
+$ export VAULT_ADDR=http://127.0.0.1:8200
+```
+
+Export an environment variable for the Vault token.
+
+```shell-session
+$ export VAULT_TOKEN=root
+```
+
+-> **Note:** For these tasks, you can use Vault's _root_ token. However, we
+recommend that you use root tokens only for the initial setup or in
+emergencies. As a best practice, use an authentication method or token that
+meets the [policy requirements](#policy-requirements).
+
+The Vault server is ready.
+
+</Tab>
+<Tab heading="HCP Vault Dedicated" group="hcp">
+
+
+1. Launch the [HCP Portal](https://portal.cloud.hashicorp.com/) and log in.
+1. Click **Vault** in the left navigation pane.
+1. In the **Vault clusters** pane, click **vault-cluster**.
+1. Under **Cluster URLs**, click **Public** Cluster URL. This copies the URL to your clipboard.
+1. In your terminal, set the `VAULT_ADDR` environment variable to the public cluster URL copied from HCP.
+
+   ```shell-session
+   $ export VAULT_ADDR=<Public_Cluster_URL>
+   ```
+
+1. Return to the **Overview** page and click **Generate token**. It will take a few moments to generate the token.
+1. Copy the **Admin Token** by clicking on **Copy**.
+1. Return to your terminal and set the `VAULT_TOKEN` environment variable to the token copied from HCP.
+
+   ```shell-session
+   $ export VAULT_TOKEN=<token>
+   ```
+
+1. Set the `VAULT_NAMESPACE` environment variable to `admin`.
+
+   ```shell-session
+   $ export VAULT_NAMESPACE=admin
+   ```
+
+   The `admin` namespace is the top-level namespace automatically created by HCP
+   Vault. By default, all CLI operations use the namespace defined in this
+   environment variable.
+
+1. Verify connectivity to the Vault cluster.
+
+   ```shell-session
+   $ vault status
+
+   Key                      Value
+   ---                      -----
+   Recovery Seal Type       shamir
+   Initialized              true
+   Sealed                   false
+   Total Recovery Shares    1
+   Threshold                1
+   Version                  1.9.2+ent
+   Storage Type             raft
+   ...snipped...
+   ```
+
+The Vault Dedicated server is ready.
+
+</Tab>
+</Tabs>
+
+## Configure Vault authentication
+
+Vault [auth methods](/vault/docs/auth) authenticate and assign
+identity and policies to a client. When Vault acts as an OIDC provider, it is
+the source of identity and these auth methods verify that identity.
+
+1. Enable the userpass auth method at the default path.
+
+   ```shell-session
+   $ vault auth enable userpass
+   ```
+
+1. Create a user named `end-user` with the password `password`.
+
+   ```shell-session
+   $ vault write auth/userpass/users/end-user \
+       password="password" \
+       token_ttl="1h"
+   ```
+
+   This user authenticates with Vault and is assigned the default access policy.
+
+   ~> **Learn More:** For more information refer to the [Userpass Auth
+   Method](/vault/docs/auth/userpass) documentation.
+
+## Create Vault identity entity and group
+
+A client may have multiple accounts with various identity providers that are
+enabled on the Vault server. Vault clients can be mapped as entities and their
+corresponding accounts with authentication providers can be mapped as aliases.
+
+1. Create an identity entity with details about the `end-user`.
+
+   ```shell-session
+   $ vault write identity/entity \
+       name="end-user" \
+       disabled=false
+   ```
+
+1. Create an environment variable named `ENTITY_ID` that stores the ID assigned to the entity.
+
+   ```shell-session
+   $ ENTITY_ID=$(vault read -field=id identity/entity/name/end-user)
+   ```
+
+1. Create an identity group with the name `engineering` and add `end-user` as a member.
+
+   ```shell-session
+   $ vault write identity/group \
+       name="engineering" \
+       member_entity_ids="$ENTITY_ID"
+   ```
+
+1. Create an environment variable named `GROUP_ID` that stores the ID assigned to the group.
+
+   ```shell-session
+   $ GROUP_ID=$(vault read -field=id identity/group/name/engineering)
+   ```
+
+   The `end-user` entity is a member of the `engineering` group. An entity alias
+   maps an entity to client of an authentication method. This mapping requires
+   the entity ID and the authentication accessor ID.
+
+1. Create a variable named `USERPASS_ACCESSOR` that stores the accessor value of
+   the userpass authentication method.
+
+   ```shell-session
+   $ USERPASS_ACCESSOR=$(vault auth list -detailed -format json | jq -r '.["userpass/"].accessor')
+   ```
+
+1. Create an entity alias that maps the `end-user` entity with the `end-user` user.
+
+   ```shell-session
+   $ vault write identity/entity-alias \
+       name="end-user" \
+       canonical_id="$ENTITY_ID" \
+       mount_accessor="$USERPASS_ACCESSOR"
+   ```
+
+   The entity and the user are aliases of one another.
+
+~> **Learn More:** Learn more about identity in the [entities and groups tutorial](/vault/tutorials/auth-methods/identity).
+
+## Create a Vault OIDC client
+
+A Vault OIDC client connects a resource called an OIDC assignment, an
+encryption key, a client callback URL and a time-to-live on verification
+together.
+
+An OIDC assignment describes the list of the Vault entities and groups allowed
+to authenticate with this client.
+
+1. Create an assignment named `my-assignment` that authorizes the `end-user` entity
+   and `engineering` group.
+
+   ```shell-session
+   $ vault write identity/oidc/assignment/my-assignment \
+       entity_ids="${ENTITY_ID}" \
+       group_ids="${GROUP_ID}"
+   ```
+
+   The Vault OIDC authentication process requires an encryption key to sign and
+   verify the JSON web tokens (JWT) that are produced by the authentication flow.
+
+1. Create a key named `my-key`.
+
+   ```shell-session
+   $ vault write identity/oidc/key/my-key \
+       allowed_client_ids="*" \
+       verification_ttl="2h" \
+       rotation_period="1h" \
+       algorithm="RS256"
+   ```
+
+   The key is usable by all Vault OIDC clients as `allowed_client_ids` is set to
+   `*`.
+
+1. Create an OIDC client named `nomad`.
+
+   ```shell-session
+   $ vault write identity/oidc/client/nomad \
+       redirect_uris="http://localhost:4649/oidc/callback,http://localhost:4200/ui/settings/tokens" \
+       assignments="my-assignment" \
+       key="my-key" \
+       id_token_ttl="30m" \
+       access_token_ttl="1h"
+   ```
+
+   The `redirect_uris` flag describes the callback URL for the client, the value
+   is the address of a Nomad service running on its default port.
+   The `assignments` flag limits access to only the entities and groups defined in
+   `my-assignment`.
+   The `id_token_ttl` flag sets the expiration on the ID token to 30 minutes.
+   The `access_token_ttl` flag  sets the expiration of the access token to 1 hour.
+
+1. Create an environment variable named CLIENT_ID to store the `client_id` field of the
+  `nomad` client.
+
+   ```shell-session
+   $ CLIENT_ID=$(vault read -field=client_id identity/oidc/client/nomad)
+   ```
+
+## Create a Vault OIDC provider
+
+A Vault OIDC provider supports one or more clients and Vault OIDC scopes. These
+scopes define metadata claims expressed in a template. Claims are key-value
+pairs that contain information about a user and the OIDC service.
+
+1. Create an environment variable named `USER_SCOPE_TEMPLATE` that stores the user scope template.
+
+  ```shell-session
+  $ USER_SCOPE_TEMPLATE='{"username": {{identity.entity.name}}}'
+  ```
+
+1. Define a Vault OIDC scope named `user` with the user scope template.
+
+   ```shell-session
+   $ vault write identity/oidc/scope/user \
+       description="The user scope provides claims using Vault identity entity metadata" \
+       template="$(echo ${USER_SCOPE_TEMPLATE} | base64)"
+   ```
+
+1. Create an environment variable named `GROUPS_SCOPE_TEMPLATE` that stores the group scope.
+   template.
+
+   ```shell-session
+   $ GROUPS_SCOPE_TEMPLATE='{"groups": {{identity.entity.groups.names}}}'
+   ```
+
+   This template retrieves the names of all the groups defined.
+
+1. Define a Vault OIDC scope named `groups` with the groups scope template.
+
+   ```shell-session
+   $ vault write identity/oidc/scope/groups \
+       description="The groups scope provides the groups claim using Vault group membership" \
+       template="$(echo ${GROUPS_SCOPE_TEMPLATE} | base64)"
+   ```
+
+1. Create a Vault OIDC provider named `my-provider` and provide it a list of client IDs and scopes. The provider grants access to the `nomad` client.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ vault write identity/oidc/provider/my-provider \
+       allowed_client_ids="${CLIENT_ID}" \
+       scopes_supported="groups"
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+      Vault Dedicated uses the private address for the `issuer` URL. For this guide, you will override the `issuer` value to match the public URL.
+
+   ```shell-session
+   $ vault write identity/oidc/provider/my-provider \
+       issuer="$(echo $VAULT_ADDR)" \
+       allowed_client_ids="${CLIENT_ID}" \
+       scopes_supported="groups"
+   ```
+
+   </Tab>
+   </Tabs>
+
+
+1. Display the Vault OIDC configuration endpoint.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq
+   ```
+
+   </Tab>
+   </Tabs>
+
+1. Show Vault OIDC public keys.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/keys | jq
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/keys | jq
+   ```
+
+   </Tab>
+   </Tabs>
+
+## Start Nomad
+
+The [Nomad development agent](/nomad/commands/agent#dev) brings up an instance of Nomad with a server and client. Refer to the [start a cluster tutorial](/nomad/tutorials/get-started/gs-start-a-cluster#create-the-cluster) for more information.
+
+In another terminal, start a Nomad agent in development mode with ACL enabled.
+
+```shell-session
+$ sudo nomad agent -dev -acl-enabled
+
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.5.0
+
+...snip...
+```
+
+The Nomad server is ready.
+
+## Configure Nomad OIDC auth
+
+1. Create an environment variable named `ISSUER` that stores the `issuer` field of the Vault OIDC provider named `my-provider`.
+
+   <Tabs>
+   <Tab heading="Vault" group="oss">
+
+   ```shell-session
+   $ ISSUER=$(curl -s $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq -r .issuer)
+   ```
+
+   </Tab>
+   <Tab heading="HCP Vault Dedicated" group="hcp">
+
+   ```shell-session
+   $ ISSUER=$(curl --header "X-Vault-Token: $VAULT_TOKEN" --request GET \
+       --header "X-Vault-Namespace: $VAULT_NAMESPACE" \
+       $VAULT_ADDR/v1/identity/oidc/provider/my-provider/.well-known/openid-configuration | jq -r .issuer)
+   ```
+
+   </Tab>
+   </Tabs>
+
+1. Create an environment variable named `CLIENT_SECRET` that stores the `client_secret` field of the Vault OIDC client named `nomad`.
+
+   ```shell-session
+   $ CLIENT_SECRET=$(vault read -field=client_secret identity/oidc/client/nomad)
+   ```
+
+1. Run the bootstrap process, store the value of the management token, and export it as the `NOMAD_TOKEN` environment variable.
+
+   ```shell-session
+   $ NOMAD_TOKEN=$(nomad acl bootstrap -json | jq -r .SecretID)
+   $ export NOMAD_TOKEN
+   ```
+
+1. Create a Nomad policy that allows read access to the "default" namespace.
+
+   Create a file named `acl_policy_engineering_read.hcl`, add the following contents, and save the file.
+
+   ```hcl
+   namespace "default" {
+     policy = "read"
+   }
+
+   node {
+     policy = "read"
+   }
+   ```
+
+  Apply the policy.
+
+   ```shell-session
+   $ nomad acl policy apply engineering-read acl_policy_engineering_read.hcl
+   ```
+
+1. Create a corresponding role that contains the policies to assign to engineers.
+
+   ```shell-session
+   $ nomad acl role create \
+       -name=engineering-read \
+       -policy=engineering-read
+   ```
+
+1. Create a configuration for the OIDC auth method.
+
+   Create a file named `acl_auth_method.json`, add the following contents, replace `$ISSUER`, `$CLIENT_ID` and `$CLIENT_SECRET` with the values stored in their respective environment variables, and save the file.
+
+   ```json
+   {
+     "OIDCDiscoveryURL": $ISSUER,
+     "OIDCClientID": $CLIENT_ID,
+     "OIDCClientSecret": $CLIENT_SECRET,
+     "BoundAudiences": [$CLIENT_ID],
+     "OIDCScopes": ["groups"],
+     "AllowedRedirectURIs": [
+       "http://localhost:4649/oidc/callback",
+       "http://localhost:4646/ui/settings/tokens"
+     ],
+     "ListClaimMappings": {
+       "groups": "roles"
+     }
+   }
+   ```
+
+   The `ListClaimMappings` field specifies which claims of the OIDC provider
+   should be mapped to which ACL concepts of Nomad. The Vault
+   "group" created before will map to a "role" in Nomad.
+
+1. Create a new OIDC authentication method and configure it to use the Vault OIDC
+   provider.
+
+   ```shell-session
+   $ nomad acl auth-method create \
+       -default=true \
+       -name=vault \
+       -token-locality=global \
+       -max-token-ttl="10m" \
+       -type=oidc \
+       -config @acl_auth_method.json
+   ```
+
+1. Create a binding rule to evaluate OIDC claims into Nomad policies and roles.
+
+   ```shell-session
+   $ nomad acl binding-rule create \
+       -auth-method=vault \
+       -bind-type=role \
+       -bind-name="engineering-read" \
+       -selector="engineering in list.roles"
+   ```
+
+Nomad OIDC authentication is configured and ready for the `end-user` to
+authenticate.
+
+## Authenticate with Nomad
+
+Authenticate to Nomad. The `-method` flag is optional since `vault` has been configured as the default method.
+
+   ```shell-session
+   $ nomad login -method=vault
+   ```
+
+The Vault login screen will open in your browser. Select **Username** from the
+**Method** dropdown selection and enter `end-user` and `password` as the credentials.
+
+The `nomad login` command confirms the authentication was successful and
+displays the Nomad ACL token generated.
+
+   ```shell-session hideClipboard
+   Successfully logged in via OIDC and vault
+
+   Accessor ID  = 48008488-21ae-35d7-f1d6-0066a7eb902a
+   Secret ID    = d7a803e6-abd6-a80e-dd95-5f88d904cc9e
+   Name         = vault
+   Type         = client
+   Global       = true
+   Create Time  = 2023-01-13 10:06:35.933899 +0000 UTC
+   Expiry Time  = 2023-01-13 10:16:35.933899 +0000 UTC
+   Create Index = 19
+   Modify Index = 19
+   Policies     = []
+
+   Roles
+   ID                                    Name
+   197deab1-a963-91fc-2936-05923eecf0c0  engineering-read
+   ```
+
+## Next steps
+
+In this guide, you configured Vault as an OIDC provider with Nomad as a
+client. Learn more about [configuring Vault as an OIDC provider](/vault/docs/secrets/identity/oidc-provider).
diff --git a/content/nomad/v1.11.x/content/docs/secure/index.mdx b/content/nomad/v1.11.x/content/docs/secure/index.mdx
new file mode 100644
index 0000000000..5fe404d208
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/index.mdx
@@ -0,0 +1,10 @@
+---
+layout: docs
+page_title: Secure Nomad
+description: |-
+  This section provides guidance on securing Nomad. Configure a Nomad cluster for ACLs, bootstrap the ACL system, author your first policy, and grant a token based on it. Configure SSO options such as OIDC and JWT. Use workload identity to federate access to AWS and GCP.
+---
+
+# Secure Nomad
+
+This section provides guidance on securing Nomad. Configure a Nomad cluster for ACLs, bootstrap the ACL system, author your first policy, and grant a token based on it. Configure SSO options such as OIDC and JWT. Use workload identity to federate access to AWS and GCP.
diff --git a/content/nomad/v1.11.x/content/docs/secure/traffic/gossip-encryption.mdx b/content/nomad/v1.11.x/content/docs/secure/traffic/gossip-encryption.mdx
new file mode 100644
index 0000000000..936722caef
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/traffic/gossip-encryption.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Enable gossip encryption
+description: |-
+  Create an encryption key and then configure Nomad to encrypt the gossip protocol, which communicates membership and node health information between Nomad servers.
+---
+
+# Enable gossip encryption
+
+Nomad server's gossip protocol that is used to communicate membership and
+liveness information can be encrypted with symmetric keys. Enabling gossip
+encryption requires you to set an encryption key when starting the Nomad server.
+The key can be set via the [`encrypt`] parameter or with the [`-encrypt` command
+line option]. The key must be a base64-encoded string of 32 random bytes.
+The same encryption key should be used on every server in a region.
+
+<Note>
+
+To secure RPC and HTTP communication, you will need to configure
+TLS. You can learn how in the [Enable TLS encryption guide][tls-guide].
+
+</Note>
+
+## Generate an encryption key
+
+The Nomad CLI includes a `operator gossip keyring generate` command for generating a new secure
+gossip encryption key.
+
+```shell-session
+$ nomad operator gossip keyring generate
+4kRkFQfcc3LU0BazP1ca+z==
+```
+
+Current and older versions of `nomad operator gossip keyring generate` return 16 bytes; however,
+Nomad supports gossip encryption keys of 32 bytes as well. Supplying a 32 byte key
+enables AES-256 mode, where supplying a 16 byte key enables AES-128 mode.
+
+Alternatively, you can use any method that can create 32 random bytes encoded in
+base64.
+
+```shell-session
+$ openssl rand -base64 32
+4YwLQm6ZMwYgfldNBT5P76tAWMdcBmu+FPYRvCxvsHc=
+```
+
+```shell-session
+$ dd if=/dev/urandom bs=32 count=1 status=none | base64
+IisA4F7Mu/RwGfBZelcsFzMlJ4+twnO5Z7eoTzD0T6c=
+```
+
+## Configure the server to use the key
+
+Put the same generated key into every server's configuration file or command
+line arguments:
+
+```hcl
+server {
+  enabled = true
+
+  # Self-elect, should be 3 or 5 for production. This is only for single node
+  # clusters which are strictly for development/demo.
+  bootstrap_expect = 1
+
+  # Encrypt gossip communication
+  encrypt = "+p7iF56z0EWoSIvhpYHWXZrSAAtnjR9l6XHRzHqQKlg="
+}
+```
+
+## Restart the server to enable encryption
+
+You can perform a rolling restart of the Nomad process on each of your server
+nodes to enable encryption. Restart your servers one at a time in order to
+maintain a quorum of nodes on one side or the other of this soft partition.
+
+Once all of the nodes have been restarted all gossip traffic will be encrypted
+between all of your server nodes.
+
+## Next steps
+
+If you would like to learn more technical information about Nomad's gossip
+protocol, consult the [Serf library] documentation.
+
+[tls-guide]: /nomad/docs/secure/traffic/tls
+[`-encrypt` command line option]: /nomad/commands/agent
+[`encrypt`]: /nomad/docs/configuration/server#encrypt
+[`nomad operator gossip keyring` command]: /nomad/commands/operator/gossip/keyring-generate
+[serf library]: https://www.serf.io/docs/internals/gossip.html
+[tls]: /nomad/docs/configuration/tls
diff --git a/content/nomad/v1.11.x/content/docs/secure/traffic/index.mdx b/content/nomad/v1.11.x/content/docs/secure/traffic/index.mdx
new file mode 100644
index 0000000000..4a3b6be59f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/traffic/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Traffic encryption overview
+description: |-
+  Discover the methods of transport encryption used by Nomad and how
+  they are used to encrypt all network traffic to and from a Nomad
+  agent.
+---
+
+# Traffic encryption overview
+
+The Nomad agent supports encrypting all of its network traffic. There are
+two separate encryption systems, one for gossip traffic, and one for HTTP and
+RPC.
+
+Once you complete this collection you will have configured transport encryption for
+all of Nomad's protocols. RPC and HTTP communication is secured with mTLS.
+Nomad servers also communicate with a gossip protocol, Serf, which is encrypted
+using symmetric encryption and preshared keys.
+
+To review Nomad uses two different encryption schemes for its traffic.
+
+- HTTP - Used to communicate between CLI and Nomad agents. Secured by mTLS.
+- RPC - Used to communicate between Nomad agents. Secured by mTLS.
+- Serf - Used to communicate between Nomad servers. Frequently referred to as
+  "gossip". Secured by a shared key.
+
+Use the [Enable TLS Encryption for Nomad][] guide to configure Nomad for mTLS
+and the [Enable Gossip Encryption for Nomad][] to configure gossip encryption
+using a pre-shared key.
+
+[enable tls encryption for nomad]: /nomad/docs/secure/traffic/tls
+[enable gossip encryption for nomad]: /nomad/docs/secure/traffic/gossip-encryption
diff --git a/content/nomad/v1.11.x/content/docs/secure/traffic/tls.mdx b/content/nomad/v1.11.x/content/docs/secure/traffic/tls.mdx
new file mode 100644
index 0000000000..900f37c526
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/traffic/tls.mdx
@@ -0,0 +1,479 @@
+---
+layout: docs
+page_title: Enable TLS encryption
+description: |-
+  Create mutual TLS (mTLS) certificates and configure Nomad to encrypt API and
+  RPC traffic.
+---
+
+# Enable TLS encryption
+
+Securing Nomad's cluster communication is not only important for security but
+can even ease operations by preventing mistakes and misconfigurations. Nomad
+optionally uses mutual [TLS][tls] (mTLS) for all HTTP and RPC communication.
+Nomad's use of mTLS provides the following properties:
+
+- Prevent unauthorized Nomad access
+- Prevent observing or tampering with Nomad communication
+- Prevent client/server role or region misconfigurations
+- Prevent other services from masquerading as Nomad agents
+
+Preventing region misconfigurations is a property of Nomad's mTLS not commonly
+found in the TLS implementations on the public Internet. While most uses of
+TLS verify the identity of the server you are connecting to based on a domain
+name such as `example.com`, Nomad verifies the node you are connecting to is in
+the expected region and configured for the expected role (e.g.
+`client.us-west.nomad`). This also prevents other services who may have access
+to certificates signed by the same private CA from masquerading as Nomad
+agents. If certificates were identified based on hostname/IP then any other
+service on a host could masquerade as a Nomad agent.
+
+Correctly configuring TLS can be a complex process, especially given the wide
+range of deployment methodologies. If you use the sample
+[Vagrantfile][vagrantfile] from the [Nomad GitHub repository][nomad-repo] - or
+have Nomad installed - this guide will provide you with a production ready
+TLS configuration.
+
+~> Note that while Nomad's TLS configuration will be production ready, key
+management and rotation is a complex subject not covered by this guide.
+[Vault][vault] is the suggested solution for key generation and management.
+
+## Creating certificates
+
+The first step to configuring TLS for Nomad is generating certificates. In
+order to prevent unauthorized cluster access, Nomad requires all certificates
+be signed by the same Certificate Authority (CA). This should be a _private_ CA
+and not a public one like [Let's Encrypt][letsencrypt] as any certificate
+signed by this CA will be allowed to communicate with the cluster.
+
+~> Nomad certificates may be signed by intermediate CAs as long as the root CA
+is the same. Append all intermediate CAs to the `cert_file`.
+
+### Certificate authority
+
+There are a variety of tools for managing your own CA, [like the PKI secret
+backend in Vault][vault-pki], but for the sake of simplicity this guide will
+use the Nomad [`tls ca create`][] command.
+
+Generate the CA's private key and certificate.
+
+```shell-session
+$ nomad tls ca create
+```
+
+The CA key (`nomad-agent-ca-key.pem`) will be used to sign certificates for Nomad
+agents and must be kept private. The CA certificate (`nomad-agent-ca.pem`) contains
+the public key necessary to validate Nomad certificates and therefore must be
+distributed to every node that requires access.
+
+### Agent certificates
+
+Once you have a CA certificate and key you can generate and sign the
+certificates Nomad will use directly. TLS certificates commonly use the
+fully-qualified domain name of the system being identified as the certificate's
+Common Name (CN). However, hosts (and therefore hostnames and IPs) are often
+ephemeral in Nomad clusters. Not only would signing a new certificate per
+Nomad node be difficult, but using a hostname provides no security or
+functional benefits to Nomad. To fulfill the desired security properties
+(above) Nomad certificates are signed with their region and role such as:
+
+- `client.global.nomad` for a client node in the `global` region
+- `server.us-west.nomad` for a server node in the `us-west` region
+
+Generate a certificate for the Nomad server.
+
+```shell-session
+$ nomad tls cert create -server -region global
+```
+
+Generate a certificate for the Nomad client.
+
+```shell-session
+$ nomad tls cert create -client
+```
+
+Generate a certificate for the CLI.
+
+```shell-session
+$ nomad tls cert create -cli
+```
+
+Using `localhost` and `127.0.0.1` as subject alternate names (SANs) allows
+tools like `curl` to be able to communicate with Nomad's HTTP API when run on
+the same host. Other SANs may be added including a DNS resolvable hostname to
+allow remote HTTP requests from third party tools.
+
+You should now have the following files:
+
+- `nomad-agent-ca-key.pem` - CA private key. **Keep safe.**
+
+- `nomad-agent-ca.pem` - CA public certificate.
+
+- `global-cli-nomad-key.pem` - Nomad CLI private key for the `global` region.
+
+- `global-cli-nomad.pem` - Nomad CLI certificate for the `global` region.
+
+- `global-client-nomad-key.pem` - Nomad client node private key for the
+  `global` region.
+
+- `global-client-nomad.pem` - Nomad client node public certificate for the
+  `global` region.
+
+- `global-server-nomad-key.pem` - Nomad server node private key for the
+  `global` region.
+
+- `global-server-nomad.pem` - Nomad server node public certificate for the
+  `global` region.
+
+Each Nomad node should have the appropriate key (`-key.pem`) and certificate
+(`.pem`) file for its region and role. In addition each node needs the CA's
+public certificate (`nomad-agent-ca.pem`).
+
+## Configuring Nomad
+
+Next Nomad must be configured to use the newly-created key and certificates for
+mTLS. Starting with the [server configuration from the Getting Started
+guide][guide-server] add the following TLS configuration options:
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/server1"
+
+# Enable the server
+server {
+  enabled = true
+
+  # Self-elect, should be 3 or 5 for production
+  bootstrap_expect = 1
+}
+
+# Require TLS
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-server-nomad.pem"
+  key_file  = "global-server-nomad-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+The new [`tls`][tls_block] section is worth breaking down in more detail:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+  # ...
+}
+```
+
+This enables TLS for the HTTP and RPC protocols. Unlike web servers, Nomad
+doesn't use separate ports for TLS and non-TLS traffic: your cluster should
+either use TLS or not.
+
+```hcl
+tls {
+  # ...
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-server-nomad.pem"
+  key_file  = "global-server-nomad-key.pem"
+
+  # ...
+}
+```
+
+The file lines should point to wherever you placed the certificate files on
+the node. This guide assumes they are in Nomad's current directory.
+
+```hcl
+tls {
+  # ...
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+These two settings are important for ensuring all of Nomad's mTLS security
+properties are met. If [`verify_server_hostname`][verify_server_hostname] is
+set to `false` the node's certificate will be checked to ensure it is signed by
+the same CA, but its role and region will not be verified. This means any
+service with a certificate signed by same CA as Nomad can act as a client or
+server of any region.
+
+[`verify_https_client`][verify_https_client] requires HTTP API clients to
+present a certificate signed by the same CA as Nomad's certificate. It may be
+disabled to allow HTTP API clients (e.g. Nomad CLI, Consul, or curl) to
+communicate with the HTTPS API without presenting a client-side certificate. If
+`verify_https_client` is enabled only HTTP API clients presenting a certificate
+signed by the same CA as Nomad's certificate are allowed to access Nomad.
+
+~> Enabling `verify_https_client` effectively protects Nomad from unauthorized
+network access at the cost of losing Consul HTTPS health checks for agents.
+
+### Client configuration
+
+The Nomad client configuration is similar to the server configuration. The
+biggest difference is in the certificate and key used for configuration.
+
+```hcl
+# Increase log verbosity
+log_level = "DEBUG"
+
+# Setup data dir
+data_dir = "/tmp/client1"
+
+# Enable the client
+client {
+  enabled = true
+
+  # For demo assume you are talking to server1. For production,
+  # this should be like "nomad.service.consul:4647" and a system
+  # like Consul used for service discovery.
+  server_join {
+    retry_join = ["127.0.0.1:4647"]
+  }
+}
+
+# Modify our port to avoid a collision with server1
+ports {
+  http = 5656
+}
+
+# Require TLS
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-agent-ca.pem"
+  cert_file = "global-client-nomad.pem"
+  key_file  = "global-client-nomad-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+### Running with TLS
+
+Now that you have certificates generated and configuration for a client and
+server you can test our TLS-enabled cluster!
+
+In separate terminals start a server and client agent:
+
+In one terminal start a server process.
+
+```shell-session
+$ nomad agent -config server1.hcl
+```
+
+And in another terminal, start a client.
+
+```shell-session
+$ nomad agent -config client1.hcl
+```
+
+If you run `nomad node status` now, you'll get an error, like:
+
+```plaintext
+Error querying node status: Unexpected response code: 400 (Client sent an HTTP request to an HTTPS server.)
+```
+
+This is because the Nomad CLI defaults to communicating via HTTP instead of
+HTTPS. You can configure the local Nomad client to connect using TLS and specify
+our custom keys and certificates using the command line:
+
+```shell-session
+$ nomad node status \
+    -ca-cert=nomad-agent-ca.pem \
+    -client-cert=global-cli-nomad.pem \
+    -client-key=global-cli-nomad-key.pem \
+    -address=https://127.0.0.1:4646
+```
+
+This process can be cumbersome to type each time, so the Nomad CLI also
+searches environment variables for default values. Use the following commands to
+set environment variables in your shell.
+
+`NOMAD_ADDR` is the URL of the Nomad agent and sets the default for `-addr`.
+
+```shell-session
+$ export NOMAD_ADDR=https://localhost:4646
+```
+
+`NOMAD_CACERT` is the location of your CA certificate and sets the default for `-ca-cert`.
+
+```shell-session
+$ export NOMAD_CACERT=nomad-agent-ca.pem
+```
+
+`NOMAD_CLIENT_CERT` is the location of your CLI certificate and sets the default for `-client-cert`.
+
+```shell-session
+$ export NOMAD_CLIENT_CERT=global-cli-nomad.pem
+```
+
+`NOMAD_CLIENT_KEY` is the location of your CLI key and sets the default for `-client-key`.
+
+```shell-session
+$ export NOMAD_CLIENT_KEY=global-cli-nomad-key.pem
+```
+
+After these environment variables are correctly configured, the CLI will respond as expected.
+Run `nomad node status`.
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+237cd4c5  dc1  nomad  <none>  false  eligible     ready
+```
+
+Or, generate and run a sample job.
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> Monitoring evaluation "e9970e1d"
+    Evaluation triggered by job "example"
+    Allocation "a1f6c3e7" created: node "237cd4c5", group "cache"
+    Evaluation within deployment: "080460ce"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "e9970e1d" finished with status "complete"
+```
+
+## Switching an existing cluster to TLS
+
+Since Nomad does _not_ use different ports for TLS and non-TLS communication,
+the use of TLS must be consistent across the cluster. Switching an existing
+cluster to use TLS everywhere is operationally similar to upgrading between
+versions of Nomad, but requires additional steps to preventing needlessly
+rescheduling allocations.
+
+1. Add the appropriate key and certificates to all nodes. Ensure the private
+   key file is only readable by the Nomad user.
+1. Add the environment variables to all nodes where the CLI is used.
+1. Add the appropriate [`tls`][tls_block] block to the configuration file on
+   all nodes.
+1. Generate a gossip key and add it the Nomad server configuration.
+
+~> Once a quorum of servers are TLS-enabled, clients will no longer be able to
+communicate with the servers until their client configuration is updated and
+reloaded.
+
+At this point a rolling restart of the cluster will enable TLS everywhere.
+However, once servers are restarted clients will be unable to heartbeat. This
+means any client unable to restart with TLS enabled before their heartbeat TTL
+expires will have their allocations marked as `lost` and rescheduled.
+
+While the default heartbeat settings may be sufficient for concurrently
+restarting a small number of nodes without any allocations being marked as
+`lost`, most operators should raise the [`heartbeat_grace`][heartbeat_grace]
+configuration setting before restarting their servers:
+
+1. Set `heartbeat_grace = "1h"` or an appropriate duration on servers.
+1. Restart servers, one at a time.
+1. Restart clients, one or more at a time.
+1. Set [`heartbeat_grace`][heartbeat_grace] back to its previous value (or
+   remove to accept the default).
+1. Restart servers, one at a time.
+
+~> In a future release Nomad will allow upgrading a cluster to use TLS by
+allowing servers to accept TLS and non-TLS connections from clients during
+the migration.
+
+Jobs running in the cluster will _not_ be affected and will continue running
+throughout the switch as long as all clients can restart within their heartbeat
+TTL.
+
+## Changing Nomad certificates on the fly
+
+As of 0.7.1, Nomad supports dynamic certificate reloading via SIGHUP.
+
+Given a prior TLS configuration as follows:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-ca.pem"
+  cert_file = "server.pem"
+  key_file  = "server-key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+Nomad's cert_file and key_file can be reloaded via SIGHUP by updating the TLS
+stanza to:
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "nomad-ca.pem"
+  cert_file = "new_server.pem"
+  key_file  = "new_server_key.pem"
+
+  verify_server_hostname = true
+  verify_https_client    = true
+}
+```
+
+## Migrating a cluster to TLS
+
+### Reloading TLS configuration via SIGHUP
+
+Nomad supports dynamically reloading both client and server TLS configuration.
+To reload an agent's TLS configuration, first update the TLS block in the
+agent's configuration file and then send the Nomad agent a SIGHUP signal.
+Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its TLS
+configuration during a config reload via SIGHUP. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+### RPC upgrade mode for Nomad servers
+
+When migrating to TLS, the [`rpc_upgrade_mode`][rpc_upgrade_mode] option
+(defaults to `false`) in the TLS configuration for a Nomad server can be set
+to true. When set to true, servers will accept both TLS and non-TLS
+connections. By accepting non-TLS connections, operators can upgrade clients
+to TLS without the clients being marked as lost because the server is
+rejecting the client connection due to the connection not being over TLS.
+However, it is important to note that `rpc_upgrade_mode` should be used as a
+temporary solution in the process of migration, and this option should be
+re-set to false (meaning that the server will strictly accept only TLS
+connections) once the entire cluster has been migrated.
+
+[guide-install]: /nomad/tutorials/get-started/get-started-install
+[guide-server]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/server.hcl
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[letsencrypt]: https://letsencrypt.org/
+[nomad-repo]: https://github.com/hashicorp/nomad
+[rpc_upgrade_mode]: /nomad/docs/configuration/tls#rpc_upgrade_mode
+[tls]: https://en.wikipedia.org/wiki/Transport_Layer_Security
+[tls_block]: /nomad/docs/configuration/tls
+[vagrantfile]: https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+[vault-pki]: /vault/docs/secrets/pki
+[vault]: /vault/
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[verify_server_hostname]: /nomad/docs/configuration/tls#verify_server_hostname
+[`tls ca create`]: /nomad/commands/tls/ca-create
diff --git a/content/nomad/v1.11.x/content/docs/secure/vault/acl.mdx b/content/nomad/v1.11.x/content/docs/secure/vault/acl.mdx
new file mode 100644
index 0000000000..7ff637887e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/vault/acl.mdx
@@ -0,0 +1,376 @@
+---
+layout: docs
+page_title: Integrate Vault ACL
+description: |-
+  Learn how to protect your Nomad cluster with the Vault access control list (ACL) system and use workload identities with Vault. Configure Vault authentication.
+---
+
+# Integrate Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. It must be
+properly configured in order for the Vault and Nomad integrations to work.
+
+## Nomad workload identities
+
+Starting in Nomad 1.10.0, Nomad clients use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault ACL token specific to the task.
+
+By default, Nomad only generates a workload identity for tasks that can be used
+to access Nomad itself, such as for reading [Variables][] from a [`template`][]
+block. To access Vault, jobs must have additional workload identities defined
+as [`identity`][] blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure the Nomad servers with the [`vault.default_identity`][] agent
+configuration. Upon job registration, the Nomad servers update tasks that have
+a [`vault`][] block with this default identity.
+
+You can also specify identities for Vault directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Vault][jobspec_identity_vault] section of the `identity` block
+documentation for more information.
+
+### Configuring Vault authentication
+
+Vault must be configured to receive, validate, and trust these Nomad workload
+identities. Since they are encoded as [JSON Web Tokens (JWTs)][jwt], you must
+create a [JWT ACL auth method][vault_jwt_auth_method]. The auth method is an
+endpoint that Nomad can use to exchange workload identities for Vault ACL
+tokens.
+
+Refer to Vault's [Authentication][vault_auth] documentation for more
+information.
+
+#### Vault auth method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Vault servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Vault is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The `jwks_url` address must be reachable by all Vault servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `jwks_url` value.
+
+[![Vault Auth Method][img_vault_auth_method]][img_vault_auth_method]
+
+When an allocation that needs access to Vault starts, the Nomad client
+running it exchanges the Nomad workload identities for tasks for Vault ACL
+tokens.
+
+[![Vault JWT Login][img_vault_wid_acl_token]][img_vault_wid_acl_token]
+
+#### Vault ACL role
+
+A Vault [ACL role][vault_role] groups multiple ACL policies to apply to a token
+and determine the permissions it receives.
+
+The auth method may define a default ACL role that is applied to the ACL tokens
+it generates. If no default role is set, the role must be provided in the job
+using the [`vault.role`][] parameter or in the Nomad client configuration
+[`vault.create_from_role`][].
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The ACL role specifies the list of authorized audience values using the
+[`bound_audiences`][], which must have at least one match with the values
+defined in the Nomad workload identity [`aud`][] parameter. For security
+reasons, it is recommended to only define a single audience value.
+
+<CodeBlockConfig highlight="3" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced in Vault ACL configuration. The ACL role uses the
+[`claim_mappings`][] parameter to determine which of these claims are made
+available to the rest of the configuration.
+
+The [`bound_claims`][] parameter restricts which workload identities are able
+to use the role based on their claims. Refer to Vault's [Bound
+Claims][vault_bound_claims] documentation for more information.
+
+<CodeBlockConfig highlight="4-7,10-14" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Vault has different [types of ACL tokens][vault_token_types]. Nomad typically
+uses tokens of type `service` since they can be renewed for as long as the
+workload is active. Nomad automatically renews the Vault ACL tokens it generates
+before they expire. To ensure the tokens can be renewed for as long as
+necessary, [`token_explicit_max_ttl`][] must be set to 0.
+
+Alternately, you may use `batch` tokens. This should only be used when a secret
+is requested from Vault once at the start of a task or in a short-lived prestart
+task. Long-running tasks should never set `allow_token_expiration=true` if they
+obtain Vault secrets via `template` blocks, as the Vault token will expire and
+the template runner will continue to make failing requests to Vault until its
+[`vault_retry`][] attempts are exhausted, at which point the task will
+fail. Vault's `batch` tokens cannot be renewed, and Nomad will not attempt to
+renew them when configured to use Workload Identity.
+
+<CodeBlockConfig highlight="16-18" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+#### Vault ACL policy
+
+A Vault ACL role may have one or more ACL policies attached. Vault [ACL
+policies][vault_policies] define the permissions granted to an ACL
+token.
+
+<CodeBlockConfig highlight="15" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+ACL policies can reference dynamic values from Nomad workload identities claims
+exposed from the ACL role in [templated policies][vault_templated_policies].
+The exact ACL policy rules will depend on the level of access required by
+tasks.
+
+The following example ACL policy automatically grants `read` permissions to
+secrets in the path `secret/data/<job namespace>/<job name>/*`, where `<job
+namespace>` and `<job name>` are read from the workload identity claims
+`nomad_namespace` and `nomad_job_id`.
+
+<CodeBlockConfig highlight="1,5,9" filename="acl-policy.hcl">
+
+```hcl
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Vault Auth Overview][img_vault_auth_overview]][img_vault_auth_overview]
+
+#### Vault namespaces <EnterpriseAlert inline />
+
+Vault Enterprise supports multiple namespaces and jobs in Nomad Enterprise can
+use the [`vault.namespace`][] parameter to specify which namespace to use. In a
+multi-namespace environment, the authentication setup described must be applied
+to each Vault namespace used by jobs.
+
+### Important considerations about the JWKS URL
+
+The recommended configuration assumes Vault servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Vault and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Vault auth method. Nomad's CA certificate should be
+specified in the Vault auth method's
+[`jwks_ca_pem`](https://developer.hashicorp.com/vault/api-docs/auth/jwt#jwks_ca_pem)
+parameter.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Vault servers not able to connect to Nomad
+
+If the Vault servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`jwt_validation_pubkeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Vault servers, and use that address as the value for
+`jwks_url`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional references
+
+The [Vault ACL with Nomad Workload Identities][vault_tutorial_wid] tutorial
+provides guided instructions on how to configure Vault and Nomad for workload
+identities.
+
+The [`nomad setup vault`][nomad_cli_setup_vault] command and the
+[`hashicorp-modules/nomad-setup/vault`][tf_nomad_setup_vault] Terraform
+module can help you automate the process of applying configuration to a Vault
+cluster.
+
+
+[Variables]: /nomad/docs/concepts/variables
+[Vault Namespaces]: /vault/docs/enterprise/namespaces
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`bound_audiences`]: /vault/api-docs/auth/jwt#bound_audiences
+[`bound_claims`]: /vault/api-docs/auth/jwt#bound_claims
+[`claim_mappings`]: /vault/api-docs/auth/jwt#claim_mappings
+[`identity`]: /nomad/docs/job-specification/identity
+[`jwt_validation_pubkeys`]: /vault/api-docs/auth/jwt#jwt_validation_pubkeys
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[`token_explicit_max_ttl`]: /vault/api-docs/auth/jwt#token_explicit_max_ttl
+[`vault.create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault.namespace`]: /nomad/docs/job-specification/vault#namespace
+[`vault.role`]: /nomad/docs/job-specification/vault#role
+[`vault`]: /nomad/docs/job-specification/vault
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[docs_upgrade]: /nomad/docs/upgrade#upgrade-process
+[ent]: #enterprise-configuration
+[img_vault_auth_method]: /img/vault-integration-auth-method.png
+[img_vault_auth_overview]: /img/vault-integration-auth-overview.png
+[img_vault_wid_acl_token]: /img/vault-integration-wid-acl-token.png
+[jobspec_identity_vault]: /nomad/docs/job-specification/identity#workload-identities-for-vault
+[jwt]: https://jwt.io/
+[nomad_cli_setup_vault]: /nomad/commands/setup/vault
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_vault]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[tutorial_mtls]: /nomad/docs/secure/traffic/tls
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[vault_auth]: /vault/docs/concepts/auth
+[vault_bound_claims]: /vault/docs/auth/jwt#bound-claims
+[vault_jwt_auth_method]: /vault/api-docs/auth/jwt
+[vault_policies]: /vault/docs/concepts/policies
+[vault_role]: /vault/api-docs/auth/jwt#create-update-role
+[vault_templated_policies]: /vault/tutorials/policies/policy-templating
+[vault_token_types]: /vault/tutorials/tokens/tokens#token-types
+[vault_tutorial_wid]: /nomad/docs/secure/workload-identity/vault
diff --git a/content/nomad/v1.11.x/content/docs/secure/vault/index.mdx b/content/nomad/v1.11.x/content/docs/secure/vault/index.mdx
new file mode 100644
index 0000000000..74492df1b2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/vault/index.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Integrate Vault with Nomad to use tokens, password, certificates, API keys, and secrets stored in Vault. Configure Nomad to use Vault access control lists (ACLs) to secure your cluster. Learn how to configure Nomad agents and use Consul Template in your job specification.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal.
+
+## Configuration
+
+In order to use Vault with Nomad, you will need to configure and install Vault
+separately from Nomad. Nomad does not run Vault for you.
+
+## Agent configuration
+
+To enable Vault integration, Nomad agents must be configured with
+[`vault`][] blocks. Each block can be enabled or disabled and configures how
+Nomad connects to the Vault cluster.
+
+## Dynamic configuration with secrets
+
+Nomad's job specification includes a [`template`][] block that uses a tool
+called [Consul Template][]. When used with Vault, this mechanism creates a
+convenient way to ship configuration files that are populated from Vault
+secrets.
+
+For more information on Nomad's template block please see the
+[`template` job specification documentation][].
+
+## Vault access control list (ACL)
+
+The Vault ACL system protects the cluster from unauthorized access. When
+enabled, both Vault and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Vault ACL integration page][int_vault_acl] for more information.
+
+## Multiple vault clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Vault clusters. They can be
+configured using multiple [`vault`][] blocks with different `name` values. If a
+`name` is not provided, the cluster configuration is called `default`.
+
+Jobs that need access to Vault may specify which Vault cluster to use with the
+[`vault.cluster`][] parameter.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Vault.
+
+|               | Vault 1.18.0+ | Vault 1.19.0+ | Vault 1.20.0+ |
+|---------------|---------------|---------------|---------------|
+| Nomad 1.10.0+ | ✅            | ✅            | ✅            |
+| Nomad 1.9.0+  | ✅            | ✅            | ✅            |
+| Nomad 1.8.0+  | ✅            | ✅            | ✅            |
+
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Vault]:  https://www.vaultproject.io/ 'Vault by HashiCorp'
+[`template` job specification documentation]: /nomad/docs/job-specification/template#vault-integration
+[`template`]: /nomad/docs/job-specification/template
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[int_vault_acl]: /nomad/docs/secure/vault/acl
diff --git a/content/nomad/v1.11.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx b/content/nomad/v1.11.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx
new file mode 100644
index 0000000000..306ffbce70
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/workload-identity/aws-oidc-provider.mdx
@@ -0,0 +1,406 @@
+---
+layout: docs
+page_title: Federate access to AWS with Nomad Workload Identity
+description: |-
+  Integrate Nomad as an OpenID Connect (OIDC) provider with AWS IAM identity and use workload identity to federate access to AWS resources and services.
+---
+
+# Federate access to AWS with Nomad Workload Identity
+
+This page describes how to integrate Nomad with AWS IAM as an OpenID Connect (OIDC) provider and
+use [Workload Identity] to federate access to AWS resources and services. In this workflow, Nomad
+is the [OpenID Connect Provider] (OP or OIDC provider) and generates JSON Web Tokens (JWTs) which
+serve as workload identities. AWS IAM is the Relying Party (RP) and validates these workload
+identity tokens with Nomad before it permits federated access to resources and services.
+
+## Prerequisites
+
+To integrate Nomad and AWS IAM identity, you need a running Nomad cluster that
+meets the following prerequisites:
+
+- Nomad v1.7.x or later
+- TLS enabled
+
+The instructions on this page also assume the following:
+
+- Your AWS account has the necessary permissions to create IAM roles, policies, hosted zones,
+  and certificates.
+- You are using Terraform to manage your AWS infrastructure and you have
+  [configured it to communicate with AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication-and-configuration).
+
+## Workflow
+
+The process to integrate Nomad as an OIDC provider with AWS consists of the following steps:
+
+1. Create the required AWS resources:
+    - [Route 53 hosted zone](#create-a-hosted-zone)
+    - [AWS Certificate Manager SSL certificates](#generate-ssl-certificates)
+    - [Load balancer and listener](#create-an-application-load-balancer)
+    - [DNS Alias for the load balancer](#create-a-dns-alias)
+    - [OIDC Identity Provider](#create-an-oidc-identity-provider)
+    - [AWS IAM role](#create-an-iam-policy-for-oidc-federated-users)
+1. Update the Nomad server configuration.
+1. Create a jobspec file that accesses AWS and then run it to verify your configuration.
+
+## Create and configure AWS resources
+
+To use Nomad as an identity provider, you need to have a trusted SSL certificate for the
+domain used by the cluster. The following example uses AWS Certificate Manager (ACM).
+
+### Create a hosted zone
+
+Use the [`aws_route53_zone` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone).
+
+```hcl
+variable "domain_name" {
+    type = string
+    default = "<DOMAIN_NAME>"
+}
+
+resource "aws_route53_zone" "example" {
+    name = var.domain_name
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port. `var.domain_name` is used
+throughout the examples on this page to reference `<DOMAIN_NAME>`.
+
+### Generate SSL certificates
+
+Use the [`aws_acm_certificate`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate)
+and [`aws_acm_certificate_validation`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate_validation) resources to create a request and provide validation for an SSL
+certficiate.
+
+```hcl
+variable "zone_id" {
+  type    = string
+  default = "<HOSTED_ZONE_ID>"
+}
+
+resource "aws_acm_certificate" "example" {
+  domain_name       = var.domain_name
+  validation_method = "DNS"
+
+  lifecycle {
+    create_before_destroy = true
+  }
+}
+
+resource "aws_route53_record" "cert_dns" {
+  allow_overwrite = true
+  name            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_name
+  records         = [tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_value]
+  type            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_type
+  zone_id         = var.zone_id
+  ttl             = 60
+}
+
+resource "aws_acm_certificate_validation" "example" {
+  certificate_arn         = aws_acm_certificate.example.arn
+  validation_record_fqdns = [aws_route53_record.cert_dns.fqdn]
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+
+### Create an Application Load Balancer
+
+Use the [`aws_lb` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb).
+
+```hcl
+resource "aws_lb" "test" {
+  name               = "test-lb-tf"
+  internal           = false
+  load_balancer_type = "application"
+  security_groups    = [<SECURITY_GROUP_ID>]
+  subnets            = [<SUBNET_IDS>]
+
+  enable_deletion_protection = true
+
+  access_logs {
+    bucket  = <S3_BUCKET_ID>
+    prefix  = "test-lb"
+    enabled = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<SECURITY_GROUP_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#security_groups):
+A list of security groups IDs that you want to apply to the load balancer.
+- [`<SUBNET_IDS>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#subnets):
+A list of subnet IDs that you want to attach to the load balancer.
+- [`<S3_BUCKET_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#bucket):
+The ID of an S3 bucket to store the load balancer access logs in.
+
+### Create a load balancer listener
+
+Use the [`aws_lb_listener` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener).
+
+```hcl
+resource "aws_lb_listener" "example" {
+  load_balancer_arn = <LB_ARN>
+  port              = "443"
+  protocol          = "HTTPS"
+  ssl_policy        = "ELBSecurityPolicy-2016-08"
+  certificate_arn   = <CERT_ARN>
+
+  default_action {
+    type             = "forward"
+    target_group_arn = <LB_TARGET_GROUP_ARN>
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<LB_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#load_balancer_arn):
+The AWS resource name of the load balancer. This will be `aws_lb.test.arn` if you are using the
+examples from this page.
+- [`<CERT_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#certificate_arn):
+The AWS resource name of the load balancer's certificate. This will be
+`aws_acm_certificate_validation.example.certificate_arn` if you are using the examples from this
+page.
+- [`<LB_TARGET_GROUP_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#target_group_arn): The AWS resource name of the target group for the load balancer to route traffic to. This group
+includes your Nomad server instances.
+
+### Create a DNS Alias
+
+Use the [`aws_route53_record` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record).
+
+```hcl
+resource "aws_route53_record" "www" {
+  zone_id = <HOSTED_ZONE_ID>
+  name    = var.domain_name
+  type    = "A"
+
+  alias {
+    name                   = <LB_ALIAS_DNS_NAME>
+    zone_id                = <LB_ALIAS_ZONE_ID>
+    evaluate_target_health = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+- [`<LB_ALIAS_DNS_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#name):
+The DNS
+name of the load balancer. This will be `aws_lb.test.dns_name` if you are using the examples
+from this page.
+- [`<LB_ALIAS_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The zone ID of the load balancer. This will be `aws_lb.test.zone_id` if you are using the
+examples from this page.
+
+### Create an OIDC Identity Provider
+
+Use the [`aws_iam_openid_connect_provider` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider).
+
+```hcl
+data "tls_certificate" "example" {
+  url = <CERT_DOMAIN_NAME>
+}
+
+resource "aws_iam_openid_connect_provider" "nomad" {
+  # Nomad HTTPS URL
+  url = <CERT_DOMAIN_NAME>
+
+  client_id_list = [
+    "aws",
+  ]
+
+  thumbprint_list = [data.tls_certificate.example.certificates.0.sha1_fingerprint]
+}
+```
+
+This configuration requires the following information:
+- [`<CERT_DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider#url):
+The domain name of the load balancer certificate. This will be
+`aws_acm_certificate.example.domain_name` if you are using the examples from this page.
+
+### Create an IAM policy for OIDC Federated Users
+
+Use the [`aws_iam_role` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role)
+to create an appropriate IAM role for workloads acting as federated users. This will be
+specific to your use case. The following example allows workloads access to S3 buckets.
+
+```hcl
+# Variables for OIDC provider and AWS account
+variable "oidc_provider" {
+  description = "The OIDC provider URL"
+  type        = string
+  default     = "<DOMAIN_NAME>"
+}
+
+variable "aws_account_id" {
+  description = "AWS account ID"
+  type        = string
+  default     = "<AWS_ACCOUNT_ID>"
+}
+
+data "aws_iam_policy_document" "assume_role" {
+  statement {
+    effect = "Allow"
+
+    principals {
+      type        = "Federated"
+      identifiers = ["arn:aws:iam::${var.aws_account_id}:oidc-provider/${var.oidc_provider}"]
+    }
+
+    actions = ["sts:AssumeRoleWithWebIdentity"]
+
+    condition {
+      test     = "StringEquals"
+      variable = "${var.oidc_provider}:aud"
+      values   = ["aws"]
+    }
+  }
+}
+
+# Create an IAM role with the assume role policy generated above
+resource "aws_iam_role" "s3_all_access_role" {
+  name               = "s3_all_access_role"
+  assume_role_policy = data.aws_iam_policy_document.assume_role.json
+
+  tags = {
+    tag-key = "tag-value"
+  }
+}
+
+# Inline policy that defines what the role can do (full S3 access)
+data "aws_iam_policy_document" "s3_access_policy" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "s3:*",
+      "s3-object-lambda:*"
+    ]
+
+    resources = ["*"] # You can scope this down to specific S3 buckets if necessary
+  }
+}
+
+# Create a policy resource from the inline policy document above
+resource "aws_iam_policy" "policy" {
+  name        = "nomad-oidc-policy"
+  description = "A policy for federated Nomad OIDC"
+  policy      = data.aws_iam_policy_document.s3_access_policy.json
+}
+
+# Attach the S3 access policy to the IAM role
+resource "aws_iam_role_policy_attachment" "test-attach" {
+  role       = aws_iam_role.s3_all_access_role.name
+  policy_arn = aws_iam_policy.policy.arn
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+
+## Update the Nomad server configuration
+
+After you configure AWS, modify the Nomad server configuration file. Add the
+[`oidc_issuer` attribute](/nomad/docs/configuration/server#oidc_issuer) and set the value
+to the domain name for the Nomad cluster. This [enables the HTTP endpoint in Nomad](https://developer.hashicorp.com/nomad/docs/configuration/server#oidc_issuer) that allows third parties to discover Nomad's OIDC
+configuration.
+
+```hcl
+server {
+  enabled = true
+  [...]
+  oidc_issuer = "https://<DOMAIN_NAME>"
+  [...]
+}
+```
+
+This configuration requires the following information:
+- `<DOMAIN_NAME>`: The domain name of your Nomad cluster without the protocol or port.
+
+Restart the Nomad server agent to apply the configuration changes.
+
+## Create and run a sample jobspec file
+
+Create and run a jobspec file to validate your configuration. The following file is named `s3-upload.nomad.hcl`, add the following configuration to it, and
+save the file.
+
+```hcl
+job "s3" {
+  type = "batch"
+  group "bucket" {
+    task "copy" {
+      driver = "docker"
+      config {
+        image = "public.ecr.aws/aws-cli/aws-cli"
+        command = "s3"
+        args = ["cp", "/local/test.txt", "s3://<S3_BUCKET_NAME>/test-nomad.txt"]
+      }
+
+      identity {
+        name = "aws"
+        aud = ["aws"]
+        file = true
+        ttl = "1h"
+
+        # AWS SDKs gracefully handle OIDC/WebIdentity reauthentication when the
+        # session or token expire, therefore a restart isn't needed
+        change_mode = "noop"
+      }
+
+      template {
+        destination = "local/test.txt"
+        change_mode = "restart"
+        data        = <<EOF
+Job:          {{ env "NOMAD_JOB_NAME" }}
+Alloc:        {{ env "NOMAD_ALLOC_ID" }}
+EOF
+      }
+
+      env {
+        AWS_ROLE_ARN = "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>"
+        # The format of the token file is nomad_$NAME_OF_IDENTITY.jwt
+        AWS_WEB_IDENTITY_TOKEN_FILE = "${NOMAD_SECRETS_DIR}/nomad_aws.jwt"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+This configuration requires the following information:
+- `<S3_BUCKET_NAME>`: The name of the S3 bucket where the test file will be saved.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+- `<IAM_ROLE_NAME>`: The name of the IAM role from previous steps. This will be
+`s3_all_access_role` if you are using the examples from this page.
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run s3-upload.nomad.hcl
+```
+
+Verify that the job completed successfully.
+
+```shell-session
+$ nomad job status s3
+```
+
+Verify that the file was also uploaded to the S3 bucket.
+
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[OpenID Connect Provider]: https://openid.net/developers/how-connect-works/
diff --git a/content/nomad/v1.11.x/content/docs/secure/workload-identity/index.mdx b/content/nomad/v1.11.x/content/docs/secure/workload-identity/index.mdx
new file mode 100644
index 0000000000..d9ca2d5dd0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/workload-identity/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Use workload identity to federate cloud access
+description: |-
+  This section provides guidance on using Nomad workload identity to federate access to AWS and GCP.
+---
+
+# Use workload identity to federate cloud access
+
+This section provides guidance on using Nomad workload identity to federate
+access to AWS and GCP.
diff --git a/content/nomad/v1.11.x/content/docs/secure/workload-identity/vault.mdx b/content/nomad/v1.11.x/content/docs/secure/workload-identity/vault.mdx
new file mode 100644
index 0000000000..3ce9ef6ba0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/secure/workload-identity/vault.mdx
@@ -0,0 +1,1343 @@
+---
+layout: docs
+page_title: Use workload identities with Vault
+description: |-
+  Configure Vault to accept Nomad workload identities, run a Nomad job to read
+  secrets from Vault, configure dynamic secrets in Vault, and run a job with a
+  custom Vault ACL role.
+---
+
+# Use workload identities with Vault
+
+Nomad integrates with Vault to retrieve [static][vault_static] and
+[dynamic][vault_dyn] secrets for workloads.
+
+Production deployments of Nomad and Vault must always run with the Access
+Control List (ACL) system enabled since it protects against unauthorized
+access to the cluster. When ACLs are enabled, both Nomad and Vault must be
+properly configured in order for their integrations to work.
+
+Nomad can generate [workload identities][nomad_wid] for tasks, which are
+represented as [JSON Web Tokens (JWT)][jwt] signed by Nomad. These identities
+can be used as proof to third parties that a workload was actually created and
+is managed by Nomad. If the third party is configured to trust Nomad, it can
+automatically grant specific access and permissions to Nomad workloads.
+
+In this guide, you will:
+
+- Start a Nomad and Vault agent with ACL enabled.
+- Generate ACL tokens to access Nomad and Vault.
+- Configure Vault to accept workload identities from Nomad.
+- Configure Nomad to automatically generate and sign workload identities for
+  tasks that need access to Vault.
+- Deploy sample Nomad jobs that interact with Vault.
+
+## Prerequisites
+
+This guide requires you to have basic familiarity with Nomad and Vault. If
+you are new to these tools, complete the [Nomad Get Started][nomad_gs]
+and [Vault Get Started][vault_gs] tutorials before following this one.
+
+You will need the following tools installed:
+
+- [Nomad 1.7 or later installed locally][nomad_install]
+- [Vault 1.12 or later installed locally][vault_install]
+- [Docker installed and running locally][docker_install]
+
+## Start the Vault agent
+
+Start a Vault dev server.
+
+```shell-session
+$ vault server -dev
+==> Vault server configuration:
+
+Administrative Namespace:
+             Api Address: http://127.0.0.1:8200
+                     Cgo: disabled
+         Cluster Address: https://127.0.0.1:8201
+   Environment Variables: CLICOLOR, COLORTERM, COMMAND_MODE, EDITOR, GODEBUG, GOPATH, HOME, LANG, LC_ALL, LOGNAME, LSCOLORS, LaunchInstanceID, OLDPWD, PATH, PWD, SECURITYSESSIONID, SHELL, SHLVL, SSH_AUTH_SOCK, TERM, TERM_PROGRAM, TERM_PROGRAM_VERSION, TMPDIR, USER, WINDOWID, XPC_FLAGS, XPC_SERVICE_NAME, _, __CFBundleIdentifier, __CF_USER_TEXT_ENCODING
+              Go Version: go1.21.3
+              Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
+               Log Level:
+                   Mlock: supported: false, enabled: false
+           Recovery Mode: false
+                 Storage: inmem
+                 Version: Vault v1.15.2, built 2023-11-06T11:33:28Z
+             Version Sha: cf1b5cafa047bc8e4a3f93444fcb4011593b92cb
+
+==> Vault server started! Log data will stream in below:
+
+2023-11-20T20:08:27.583-0500 [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
+2023-11-20T20:08:27.583-0500 [INFO]  incrementing seal generation: generation=1
+...
+WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
+and starts unsealed with a single unseal key. The root token is already
+authenticated to the CLI, so you can immediately begin using Vault.
+
+You may need to set the following environment variables:
+
+    $ export VAULT_ADDR='http://127.0.0.1:8200'
+
+...
+```
+
+<Note title="Dev Agents">
+
+This guide uses development agents for Vault and [Nomad][nomad_dev] as a
+quick way to get started. Dev agents have ephemeral state and should not be
+used in production environments. They also run in the foreground of your
+terminal so do not close the terminal window or you will need to rerun the
+agent configuration steps again.
+
+</Note>
+
+Copy the value for `Root Token`.
+
+Open another terminal window in the same directory and set the root token as
+the environment variable `VAULT_TOKEN`. This terminal will act as the main
+terminal session where you will run commands.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export VAULT_TOKEN=...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export VAULT_TOKEN=...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:VAULT_TOKEN = "..."
+```
+
+</Tab>
+</Tabs>
+
+Set the environment variable `VAULT_ADDR`.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export VAULT_ADDR='http://127.0.0.1:8200'
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export VAULT_ADDR='http://127.0.0.1:8200'
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:VAULT_ADDR = "http://127.0.0.1:8200"
+```
+
+</Tab>
+</Tabs>
+
+## Start the Nomad agent
+
+Create a file named `nomad.hcl`. Add the following contents to it and save the
+file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="nomad.hcl">
+
+```hcl
+acl {
+  enabled = true
+}
+
+vault {
+  enabled = true
+  address = "http://127.0.0.1:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+The [`vault`][nomad_config_vault] block in this configuration file provides
+the information necessary for Nomad to connect to Vault.
+
+It also defines a default workload identity, `default_identity`, that is
+automatically added to jobs that need access to Vault. Without this identity,
+you would need to define an `identity` block in your jobs for every task that
+needs access to Vault.
+
+Open another terminal window in the same directory and start the Nomad dev
+agent.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ sudo nomad agent -dev -config 'nomad.hcl'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ nomad agent -dev -config 'nomad.hcl' -network-interface '{{GetDefaultInterfaces | attr "name"}}'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ nomad agent -dev -config 'nomad.hcl' -network-interface '{{GetDefaultInterfaces | attr \"name\"}}'
+==> Loaded configuration from nomad.hcl
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+       Advertise Addrs: HTTP: 127.0.0.1:4646; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+            Bind Addrs: HTTP: [127.0.0.1:4646]; RPC: 127.0.0.1:4647; Serf: 127.0.0.1:4648
+                Client: true
+             Log Level: DEBUG
+               Node Id: af9bef00-2e83-b704-2d6c-c62bc005431f
+                Region: global (DC: dc1)
+                Server: true
+               Version: 1.7.0
+
+==> Nomad agent started! Log data will stream in below:
+...
+```
+
+</Tab>
+</Tabs>
+
+Return to your main terminal window and bootstrap the Nomad ACL system.
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = d1de8625-8556-0932-a25c-3aa71bfc0134
+Secret ID    = 7f10099a-936c-3f3a-8783-f0980493e54b
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2023-11-16 01:09:26.565422 +0000 UTC
+Expiry Time  = <none>
+Create Index = 23
+Modify Index = 23
+Policies     = n/a
+Roles        = n/a
+```
+
+Copy the value of `Secret ID` and set it as the environment variable
+`NOMAD_TOKEN`.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+```shell-session
+$ export NOMAD_TOKEN=...
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+```shell-session
+$ export NOMAD_TOKEN=...
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+```shell-session
+$ $Env:NOMAD_TOKEN = "..."
+```
+
+</Tab>
+</Tabs>
+
+<Note title="Using Bootstrap Tokens">
+
+The initial ACL bootstrap tokens from Vault and Nomad have full access to the
+cluster and should not be used for regular day-to-day operations in a
+production environment. They are used in this guide as an illustration.
+We recommend creating [ACL policies][nomad_acl_policies] and
+[tokens][nomad_acl_tokens] with only a level of access necessary to perform the
+required operations.
+
+</Note>
+
+## Configure Vault to accept Nomad workload identities
+
+### Create a Vault ACL auth method
+
+Enable a `jwt` [auth method][vault_auth_method] in Vault under the path
+`jwt-nomad`.
+
+```shell-session
+$ vault auth enable -path 'jwt-nomad' 'jwt'
+Success! Enabled jwt auth method at: jwt-nomad/
+```
+
+The JWT auth method creates an endpoint that Nomad clients use to exchange
+Nomad workload identity JWTs for Vault ACL tokens.
+
+Create a file named `vault-auth-method-jwt-nomad.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-auth-method-jwt-nomad.json">
+
+```json
+{
+  "jwks_url": "http://127.0.0.1:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+This configuration file contains important information.
+
+* `jwks_url` is the URL that Vault uses to contact Nomad and retrieve the data
+  necessary to validate Nomad workload identities. In a production environment,
+  this should resolve to multiple Nomad agents via a reverse proxy, load
+  balancer, or DNS entry to prevent a single point of failure.
+* `default_role` is the Vault ACL role applied by default to tokens generated
+  by this auth method. You will create the `nomad-workloads` role in the next
+  section.
+
+Apply the configuration file `vault-auth-method-jwt-nomad.json` to the
+`jwt-nomad` auth method.
+
+```shell-session
+$ vault write auth/jwt-nomad/config '@vault-auth-method-jwt-nomad.json'
+Success! Data written to: auth/jwt-nomad/config
+```
+
+### Create a Vault ACL role
+
+Create a file named `vault-role-nomad-workloads.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-role-nomad-workloads.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+It defines properties for the Vault ACL tokens that are used for Nomad tasks.
+
+* `bound_audiences` configures Vault to only accept JWTs that have an audience
+  value of `vault.io`. It must match the `aud` value present in the Nomad agent
+  configuration and jobs.
+* `claim_mappings` are values from the Nomad workload identity. You will
+  reference them when creating the Vault ACL policy for this role.
+* `token_period` determines how long the token is valid for before it expires.
+  Nomad automatically renews tokens before they expire.
+* `token_explicit_max_ttl` is the maximum amount of time the token is valid. It
+  must be set to `0` so Nomad can renew them for as long as the workload runs.
+* `token_policies` are the ACL policies applied to the tokens. They specify the
+  permissions that tokens with this role have. You will create the policy
+  `nomad-workloads` policy in the next section.
+
+Create a Vault ACL role named `nomad-workloads` using the
+`vault-role-nomad-workloads.json` file.
+
+```shell-session
+$ vault write auth/jwt-nomad/role/nomad-workloads '@vault-role-nomad-workloads.json'
+Success! Data written to: auth/jwt-nomad/role/nomad-workloads
+```
+
+This role is applied by default to Vault ACL tokens generated from the auth
+method `jwt-nomad`.
+
+### Create a Vault ACL policy
+
+List all of the auth methods registered in Vault.
+
+```shell-session
+$ vault auth list
+Path          Type     Accessor               Description                Version
+----          ----     --------               -----------                -------
+jwt-nomad/    jwt      auth_jwt_d34481ad      n/a                        n/a
+token/        token    auth_token_510d42ca    token based credentials    n/a
+```
+
+Copy the `Accessor` value for the auth method in the `jwt-nomad/` path.
+
+Create a file named `vault-policy-nomad-workloads.hcl`. Add the following
+contents to it, replace all the instances of the `AUTH_METHOD_ACCESSOR`
+placeholder with the `Accessor` value from the output, and save the file. There
+are five occurrences to update.
+
+<CodeBlockConfig filename="vault-policy-nomad-workloads.hcl">
+
+```hcl
+path "kv/data/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "kv/data/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "kv/metadata/{{identity.entity.aliases.AUTH_METHOD_ACCESSOR.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "kv/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+This file is a [templated Vault ACL policy][vault_tpl_policy] that
+automatically grants Nomad workloads access to secrets based on the
+properties mapped in the `claim_mappings` of the Vault ACL role.
+
+More specifically, this policy grants access to secrets in the path
+`kv/data/<job namespace>/<job name>/*` where `<job namespace>` and `<job name>`
+are dynamically set for each workload.
+
+Create a Vault ACL policy named `nomad-workloads` using the file
+`vault-policy-nomad-workloads.hcl`.
+
+```shell-session
+$ vault policy write 'nomad-workloads' 'vault-policy-nomad-workloads.hcl'
+Success! Uploaded policy: nomad-workloads
+```
+
+## Run a Nomad job to read secrets from Vault
+
+Start a MongoDB database with a root password that is read from Vault using the
+Nomad workload identity for the task.
+
+Enable the `kv` secret engine.
+
+```shell-session
+$ vault secrets enable -version '2' 'kv'
+Success! Enabled the kv secrets engine at: kv/
+```
+
+Write a secret in Vault for the database root password in the path
+`default/mongo/config`.
+
+```shell-session
+$ vault kv put -mount 'kv' 'default/mongo/config' 'root_password=secret-password'
+======== Secret Path ========
+kv/data/default/mongo/config
+
+======= Metadata =======
+Key                Value
+---                -----
+created_time       2023-11-21T02:52:42.061092Z
+custom_metadata    <nil>
+deletion_time      n/a
+destroyed          false
+version            1
+```
+
+Create a file named `mongo.nomad.hcl`. Add the following contents to it and
+save the file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="mongo.nomad.hcl">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        static = 27017
+      }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "mongo"
+      port     = "db"
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+
+        mount {
+          type   = "bind"
+          target = "C:\\mongosh"
+          source = "local/mongosh/mongosh-2.1.0-win32-x64/"
+        }
+      }
+
+      vault {}
+
+      template {
+        data        = <<EOF
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{with secret "kv/data/default/mongo/config"}}{{.Data.data.root_password}}{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+
+      artifact {
+        source      = "https://downloads.mongodb.com/compass/mongosh-2.1.0-win32-x64.zip"
+        destination = "local/mongosh"
+      }
+
+      resources {
+        memory = 1000
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+* The `vault` block indicates that the task needs access to Vault and that
+  Nomad should use the task workload identity to get a Vault ACL token.
+* The `template` block reads the root password secret from Vault under the
+  path `kv/data/default/mongo/config`.
+* The job runs in the Nomad `default` namespace and the job name is `mongo`.
+  The `nomad-workloads` Vault role grants access to secrets in the path
+  `kv/data/default/mongo/*`, which is where the root password exists.
+* The job does not specify any identity for Vault, so Nomad uses the
+  `default_identity` from the agent configuration.
+
+Run the job with the `mongo.nomad.hcl` file and wait for the deployment to
+complete.
+
+```shell-session
+$ nomad job run 'mongo.nomad.hcl'
+==> 2023-11-20T22:09:16-05:00: Monitoring evaluation "34e72e7a"
+    2023-11-20T22:09:16-05:00: Evaluation triggered by job "mongo"
+    2023-11-20T22:09:17-05:00: Evaluation within deployment: "919f658b"
+    2023-11-20T22:09:17-05:00: Allocation "49fc68d8" created: node "b8db12d2", group "db"
+    2023-11-20T22:09:17-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2023-11-20T22:09:17-05:00: Evaluation "34e72e7a" finished with status "complete"
+==> 2023-11-20T22:09:17-05:00: Monitoring deployment "919f658b"
+  ✓ Deployment "919f658b" successful
+
+    2023-11-20T22:09:28-05:00
+    ID          = 919f658b
+    Job ID      = mongo
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    db          1        1       1        0          2023-11-20T22:19:26-05:00
+```
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" mongosh --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+<Tab heading="macOS" group="mac">
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" mongosh --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+<Tab heading="Windows" group="win">
+
+Create the `root` user, reading the credentials from the environment variables
+set in the job from the Vault secret.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" powershell -command  'C:\mongosh\bin\mongosh.exe mongodb://localhost:27017/admin --quiet --eval ""db.createUser({user: ''$Env:MONGO_INITDB_ROOT_USERNAME'', pwd: ''$Env:MONGO_INITDB_ROOT_PASSWORD'', roles: [{role: ''root'', db: ''admin''}]})""'
+{ ok: 1 }
+```
+
+Verify that you are able to execute a query against the database using the
+`root` user credentials.
+
+```shell-session
+$ nomad alloc exec "$(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' 'mongo')" C:\mongosh\bin\mongosh.exe 'mongodb://localhost:27017' --username 'root' --password 'secret-password' --eval 'db.runCommand({connectionStatus : 1})' --quiet
+{
+  authInfo: {
+    authenticatedUsers: [ { user: 'root', db: 'admin' } ],
+    authenticatedUserRoles: [ { role: 'root', db: 'admin' } ]
+  },
+  ok: 1
+}
+```
+
+</Tab>
+</Tabs>
+
+
+Retrieve the job definition from Nomad and filter the output to only display
+its task.
+
+```shell-session
+$ nomad job inspect -t '{{sprig_toPrettyJson (index (index .TaskGroups 0).Tasks 0)}}' 'mongo'
+{
+  "Name": "mongo",
+  "Driver": "docker",
+  "User": "",
+  "Lifecycle": null,
+  "Config": {
+    "image": "mongo:7",
+    "ports": [
+      "db"
+    ]
+  },
+...
+```
+
+The `Identities` list contains the workload identity that Nomad injects
+following the specification in the `default_identity` block from the Nomad
+server configuration file.
+
+<CodeBlockConfig highlight="13-26" hideClipboard>
+
+```json
+{
+  "Name": "mongo",
+  "Driver": "docker",
+  "User": "",
+  "Lifecycle": null,
+  "Config": {
+    "image": "mongo:7",
+    "ports": [
+      "db"
+    ]
+  },
+...
+  "Identities": [
+    {
+      "Name": "vault_default",
+      "Audience": [
+        "vault.io"
+      ],
+      "ChangeMode": "",
+      "ChangeSignal": "",
+      "Env": false,
+      "File": false,
+      "ServiceName": "",
+      "TTL": 3600000000000
+    }
+  ],
+  "Actions": null
+}
+```
+
+</CodeBlockConfig>
+
+By configuring Vault to accept workload identities from Nomad, the Nomad task
+was able to automatically receive a Vault ACL token scoped to the level of
+access defined by the auth method default role. With this method, Nomad agents
+no longer require long-lived, highly permissive Vault tokens.
+
+## Configure Vault dynamic secrets for MongoDB
+
+The MongoDB database reads a secret from Vault using the permissions in the
+default Vault ACL role.
+
+In some situations, it may be necessary to customize the permissions granted to
+a task to be different from this default. This is done by creating additional
+Vault ACL roles for Nomad jobs.
+
+Configure Vault with a [dynamic secret][vault_dyn] for a non-root MongoDB user
+that the default Vault ACL policy does not grant access to then run a Nomad job
+using a custom Vault ACL role to be able to access the dynamic secret.
+
+Enable the Vault database secrets engine.
+
+```shell-session
+$ vault secrets enable database
+Success! Enabled the database secrets engine at: database/
+```
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@127.0.0.1:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+
+Retrieve the IP address for MongoDB from Nomad.
+
+```shell-session
+$ nomad service info mongo
+Job ID  Address              Tags  Node ID   Alloc ID
+mongo   192.168.0.171:27017  []    b8db12d2  49fc68d8
+```
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it, replace the placeholder `MONGO_IP` text with the IP address
+from the Nomad `service info` command, and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@MONGO_IP:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+
+Retrieve the IP address for MongoDB from Nomad.
+
+```shell-session
+$ nomad service info mongo
+Job ID  Address              Tags  Node ID   Alloc ID
+mongo   192.168.0.171:27017  []    b8db12d2  49fc68d8
+```
+
+Create a file named `vault-dynamic-secret-mongo.json`. Add the following
+contents to it, replace the placeholder `MONGO_IP` text with the IP address
+from the Nomad `service info` command, and save the file.
+
+<CodeBlockConfig filename="vault-dynamic-secret-mongo.json">
+
+```json
+{
+    "plugin_name": "mongodb-database-plugin",
+    "allowed_roles": "mongo",
+    "connection_url": "mongodb://{{username}}:{{password}}@MONGO_IP:27017/admin",
+    "username": "root",
+    "password": "secret-password"
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+Write the `vault-dynamic-secret-mongo.json` configuration for the MongoDB
+dynamic secret to connect to the database.
+
+```shell-session
+$ vault write 'database/config/mongo' '@vault-dynamic-secret-mongo.json'
+Success! Data written to: database/config/mongo
+```
+
+Create a file named `vault-database-role-mongo.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-database-role-mongo.json">
+
+```json
+{
+    "db_name": "mongo",
+    "creation_statements": "{ \"db\": \"admin\", \"roles\": [{ \"role\": \"readWrite\" }, {\"role\": \"read\", \"db\": \"foo\"}] }",
+    "default_ttl": "1h",
+    "max_ttl": "24h"
+}
+```
+
+</CodeBlockConfig>
+
+Create a Vault database role using the `vault-database-role-mongo.json` file.
+
+```shell-session
+$ vault write 'database/roles/mongo' '@vault-database-role-mongo.json'
+Success! Data written to: database/roles/mongo
+```
+
+### Create a Vault ACL role to access the dynamic secret
+
+Create a file named `vault-role-mongo-dynamic-secret.json`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-role-mongo-dynamic-secret.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo-query"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["mongo-dynamic-secret"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+This role is similar to the one from earlier in the guide but this one uses
+a different policy, called `mongo-dynamic-secret`, which you will create in the
+next section.
+
+It also defines a set of `bound_claims` to restrict which workload identities
+from Nomad are able to use this role. In this example, the role only allows the
+job `mongo-query` in the Nomad namespace `default` to use it.
+
+Create the `mongo-dynamic-secret` ACL role using the
+`vault-role-mongo-dynamic-secret.json` file.
+
+```shell-session
+$ vault write 'auth/jwt-nomad/role/mongo-dynamic-secret' '@vault-role-mongo-dynamic-secret.json'
+Success! Data written to: auth/jwt-nomad/role/mongo-dynamic-secret
+```
+
+Create a file named `vault-policy-mongo-dynamic-secret.hcl`. Add the following
+contents to it and save the file.
+
+<CodeBlockConfig filename="vault-policy-mongo-dynamic-secret.hcl">
+
+```hcl
+path "database/creds/mongo" {
+  capabilities = ["read"]
+}
+```
+
+</CodeBlockConfig>
+
+This ACL policy only grants access to the specific path `database/creds/mongo`,
+which is not included in the default role used by the `jwt-nomad` auth method.
+
+Create the `mongo-dynamic-secret` ACL policy using the
+`vault-policy-mongo-dynamic-secret.hcl` file.
+
+```shell-session
+$ vault policy write 'mongo-dynamic-secret' 'vault-policy-mongo-dynamic-secret.hcl'
+Success! Uploaded policy: mongo-dynamic-secret
+```
+
+## Run a Nomad job with a custom Vault ACL role
+
+Create a file named `mongo-query.nomad.hcl`. Add the following contents to it
+and save the file.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "mongosh"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="macOS" group="mac">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "mongosh"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Windows" group="win">
+<CodeBlockConfig filename="mongo-query.nomad.hcl">
+
+```hcl
+job "mongo-query" {
+  namespace = "default"
+  type      = "batch"
+
+  group "mongo-query" {
+    task "mongo-query" {
+      driver = "docker"
+
+      config {
+        image   = "mongo:7"
+        command = "C:\\mongosh\\bin\\mongosh.exe"
+        args = [
+          "--username", "${MONGO_USERNAME}",
+          "--password", "${MONGO_PASSWORD}",
+          "--eval", "db.runCommand({connectionStatus : 1})",
+          "--quiet",
+          "${MONGO_URL}",
+        ]
+
+        mount {
+          type   = "bind"
+          target = "C:\\mongosh"
+          source = "local/mongosh/mongosh-2.1.0-win32-x64/"
+        }
+      }
+
+      vault {
+        role = "mongo-dynamic-secret"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "database/creds/mongo"}}
+MONGO_USERNAME={{.Data.username}}
+MONGO_PASSWORD={{.Data.password}}
+{{end}}
+{{range nomadService 1 (env "NOMAD_ALLOC_ID") "mongo"}}
+MONGO_URL=mongodb://{{.Address}}:{{.Port}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+
+      artifact {
+        source      = "https://downloads.mongodb.com/compass/mongosh-2.1.0-win32-x64.zip"
+        destination = "local/mongosh"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+Note that the `vault` block specifies the `mongo-dynamic-secret` role. The task
+can only access the dynamic credentials for MongoDB.
+
+The `template` block reads these credentials and exposes them as environment
+variables to the task so it can use them.
+
+Run the Nomad job from the file `mongo-query.nomad.hcl`.
+
+```shell-session
+$ nomad job run 'mongo-query.nomad.hcl'
+==> 2023-11-20T23:11:35-05:00: Monitoring evaluation "5fa56c67"
+    2023-11-20T23:11:35-05:00: Evaluation triggered by job "mongo-query"
+    2023-11-20T23:11:36-05:00: Allocation "909f0184" created: node "b8db12d2", group "mongo-query"
+    2023-11-20T23:11:36-05:00: Evaluation status changed: "pending" -> "complete"
+==> 2023-11-20T23:11:36-05:00: Evaluation "5fa56c67" finished with status "complete"
+```
+
+Retrieve the allocation information and wait until the status is `complete`.
+You may need to run the command a few times before the status changes to
+`complete`.
+
+```shell-session
+$ nomad job allocs 'mongo-query'
+ID        Node ID   Task Group   Version  Desired  Status    Created  Modified
+909f0184  b8db12d2  mongo-query  0        run      complete  25s ago  24s ago
+```
+
+Retrieve the query result to confirm the job was able to connect to the MongoDB
+database.
+
+```shell-session
+$ nomad alloc logs $(nomad job allocs -t '{{with (index . 0)}}{{.ID}}{{end}}' mongo-query)
+{
+  authInfo: {
+    authenticatedUsers: [
+      {
+        user: 'v-jwt-nomad-mongo-mongo-QbF7HWHjwOi6PJWmNo1x-1700544973',
+        db: 'admin'
+      }
+    ],
+    authenticatedUserRoles: [ { role: 'readWrite', db: 'admin' }, { role: 'read', db: 'foo' } ]
+  },
+  ok: 1
+}
+```
+
+Note that the authenticated user is now a dynamic user credential.
+
+Templated Vault ACL policies provide great flexibility when defining access
+rules, but a single policy, or a specific group of policies, may not be enough
+to cover all use cases.
+
+Creating additional Vault ACL roles for specific Nomad jobs can help better
+manage access control to Vault secrets.
+
+## Next steps
+
+In this guide, you configured Nomad and Vault to communicate with ACL
+enabled. You also configured Nomad to automatically add workload identities for
+tasks that need access to Vault.
+
+You then deployed Nomad jobs to read static and dynamic secrets from Vault
+using different Vault ACL roles and policies. Both jobs used their workload
+identities to receive a Vault ACL token properly scoped to the work they
+needed to do.
+
+This process required several steps, with certain values having to match each
+other in order for everything to work properly.
+
+There are two resources available to help you automate these steps.
+
+* The Nomad CLI command `nomad setup vault` can be useful for a quick setup
+  with default values for a development or test cluster.
+* The [`hashicorp-modules/nomad-setup/vault`][tf_module] Terraform module
+  provides a basis for applying these steps with a infrastructure-as-code
+  approach, which is more suitable for a production environment. The
+  [`hashicorp-guides/nomad-workload-identity-terraform-demo`][tf_demo]
+  repository demonstrates how this module can be used.
+
+You may continue exploring additional integrations between Nomad and Vault or
+learn how to similarly [integrate Nomad and Consul][nomad_consul_acl] with ACL
+enabled.
+
+- [Nomad and Vault Integration][nomad_integrations_vault]
+- [Nomad Workload Identity][nomad_wid]
+- [Nomad Agent `vault` Configuration][nomad_config_vault]
+- [Vault ACL policies tutorial][vault_tutorial_policies]
+
+[docker_install]: https://www.docker.com/get-started/
+[jwt]: https://jwt.io/
+[nomad_acl_policies]: /nomad/docs/secure/acl/policies
+[nomad_acl_tokens]: /nomad/docs/secure/acl/tokens
+[nomad_config_vault]: /nomad/docs/configuration/vault
+[nomad_consul_acl]: /nomad/tutorials/integrate-consul/consul-acl
+[nomad_dev]: /nomad/commands/agent#dev
+[nomad_gs]: /nomad/tutorials/get-started
+[nomad_install]: /nomad/install
+[nomad_integrations_vault]: /nomad/docs/secure/vault
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[tf_demo]: https://github.com/hashicorp-guides/nomad-workload-identity-terraform-demo
+[tf_module]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[vault_auth_method]: /vault/docs/auth
+[vault_dyn]: /vault/docs/use-cases#dynamic-secrets
+[vault_gs]: /vault/tutorials/get-started
+[vault_install]: /vault/install
+[vault_static]: /vault/docs/use-cases#static-secrets
+[vault_tpl_policy]: /vault/docs/concepts/policies#templated-policies
+[vault_tutorial_policies]: /vault/tutorials/policies
diff --git a/content/nomad/v1.11.x/content/docs/stateful-workloads/csi-volumes.mdx b/content/nomad/v1.11.x/content/docs/stateful-workloads/csi-volumes.mdx
new file mode 100644
index 0000000000..20896686d1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/stateful-workloads/csi-volumes.mdx
@@ -0,0 +1,661 @@
+---
+layout: docs
+page_title: Use CSI volumes
+description: >-
+  Configure and deploy the AWS EBS volume CSI plugin to connect an EBS volume
+  to a MySQL workload that requires persistent storage.
+---
+
+# Use CSI volumes
+
+Nomad’s [Container Storage Interface (CSI)][csi-spec] integration can manage
+external storage volumes for stateful workloads running inside your
+cluster. CSI providers are third-party plugins that run as Nomad jobs
+and can mount volumes created by your cloud provider. Nomad is aware
+of CSI-managed volumes during the scheduling process, enabling it to
+schedule your workloads based on the availability of volumes on a
+specific client.
+
+Each storage provider builds its own CSI plugin, and you can leverage
+all of them in Nomad. You can launch jobs that claim storage volumes
+from AWS Elastic Block Storage (EBS) or Elastic File System (EFS)
+volumes, GCP persistent disks, Digital Ocean droplet storage volumes,
+or vendor-agnostic third-party providers like Portworx. This also
+means that many plugins written by storage providers to support
+Kubernetes will support Nomad as well. You can find a list of plugins
+in the [Kubernetes CSI Developer Documentation][k8s-drivers].
+
+Unlike Nomad’s [`host_volume`] feature, CSI-managed volumes can be added
+and removed from a Nomad cluster without changing the Nomad client
+configuration.
+
+Using Nomad’s CSI integration consists of three core workflows:
+running CSI plugins, registering volumes for those plugins, and
+running jobs that claim those volumes. In this guide, you'll run the
+AWS Elastic Block Storage (EBS) plugin, register an EBS volume for
+that plugin, and deploy a MySQL workload that claims that volume for
+persistent storage.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need:
+
+- a Nomad environment on AWS with Consul installed. You can use this [Terraform
+  environment][nomad-tf] to provision a sandbox environment. This tutorial will
+  assume a cluster with one server node and two client nodes.
+
+- Nomad v1.3.0 or greater
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node. Consult the [reference architecture][reference-arch] for production
+configuration.
+
+</Note>
+
+### Install the MySQL client
+
+You will use the MySQL client to connect to our MySQL database and
+verify our data. Ensure it is installed on a node with access to port
+3306 on your Nomad clients:
+
+Ubuntu:
+
+```shell-session
+$ sudo apt install mysql-client
+```
+
+CentOS:
+
+```shell-session
+$ sudo yum install mysql
+```
+
+macOS via Homebrew:
+
+```shell-session
+$ brew install mysql-client
+```
+
+### Deploy an AWS EBS volume
+
+Next, create an AWS EBS volume for the CSI plugin to mount where needed
+for your jobs using the same Terraform stack you used
+to create the Nomad cluster.
+
+Add the following new resources to your Terraform stack.
+
+```hcl
+resource "aws_iam_role_policy" "mount_ebs_volumes" {
+  name   = "mount-ebs-volumes"
+  role   = aws_iam_role.instance_role.id
+  policy = data.aws_iam_policy_document.mount_ebs_volumes.json
+}
+
+data "aws_iam_policy_document" "mount_ebs_volumes" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "ec2:DescribeInstances",
+      "ec2:DescribeTags",
+      "ec2:DescribeVolumes",
+      "ec2:AttachVolume",
+      "ec2:DetachVolume",
+    ]
+    resources = ["*"]
+  }
+}
+
+resource "aws_ebs_volume" "mysql" {
+  availability_zone = aws_instance.client[0].availability_zone
+  size              = 40
+}
+
+output "ebs_volume" {
+    value = <<EOM
+# volume registration
+type        = "csi"
+id          = "mysql"
+name        = "mysql"
+external_id = "${aws_ebs_volume.mysql.id}"
+plugin_id   = "aws-ebs0"
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+EOM
+}
+```
+
+Run `terraform plan` and `terraform apply` to create the new IAM
+policy and EBS volume. Then run `terraform output ebs_volume > volume.hcl`. You'll use this file later to register the volume with
+Nomad.
+
+#### Notes about the above Terraform configuration
+
+- The IAM policy document and role policy are being added to the
+  existing instance role for your EC2 instances. This policy will give
+  the EC2 instances the ability to mount the volume you've created in
+  Terraform, but will not give them the ability to create new volumes.
+
+- The EBS volume resource is the data volume you will attach via CSI
+  later. The output will be used to register the volume with Nomad.
+
+## Enable privileged Docker jobs
+
+CSI Node plugins must run as privileged Docker jobs because they use
+bidirectional mount propagation in order to mount disks to the underlying host.
+
+CSI Plugins running as `node` or `monolith` type require root privileges (or
+CAP_SYS_ADMIN on Linux) to mount volumes on the host. With the Docker task
+driver, you can use the `privileged = true` configuration, but no other default
+task drivers currently have this option.
+
+Nomad’s default configuration does not allow privileged Docker jobs, and must be
+edited to allow them.
+
+~> Bidirectional mount propagation can be dangerous and can damage the host
+operating system. For this reason, it is only allowed in privileged containers.
+
+To enable, edit the configuration for all of your Nomad clients, and set
+[`allow_privileged`][] to true inside of the Docker plugin’s configuration.
+Restart the Nomad client process to load this new configuration.
+
+If your Nomad client configuration does not already specify a Docker plugin
+configuration, this minimal one will allow privileged containers. Add it to your
+Nomad client configuration and restart Nomad.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_privileged = true
+  }
+}
+```
+
+There are certain Docker configurations that can prevent privileged containers
+from performing mounts on the host. The error message will likely contain the
+phrase "linux mounts: path ... is mounted on ... but it is not a shared mount".
+More information can be found in the [Docker forums][docker-forums]
+
+If you do not have privileged containers enabled in Nomad, you will receive the
+following error when you submit the plugin-aws-ebs-nodes job:
+
+```plaintext
+Failed to create container configuration for image
+"amazon/aws-ebs-csi-driver:v0.10.1": Docker privileged mode is disabled on this
+Nomad agent
+```
+
+## Deploy the EBS plugin
+
+Plugins for CSI are run as Nomad jobs with a `plugin` stanza. The
+official plugin for AWS EBS can be found on GitHub in the
+[`aws-ebs-csi-driver`][aws-ebs-csi-driver] repository. It’s packaged as a
+Docker container that you can run with the Docker task driver.
+
+Each CSI plugin supports one or more types: Controllers and
+Nodes. Node instances of a plugin need to run on every Nomad client
+node where you want to mount volumes. You'll probably want to run Node
+plugins instances as Nomad `system` jobs. Some plugins also require
+coordinating Controller instances that can run on any Nomad client
+node.
+
+The AWS EBS plugin requires a controller plugin to coordinate access
+to the EBS volume, and node plugins to mount the volume to the EC2
+instance. You'll create a controller job as a nomad `service` job and
+the node job as a Nomad `system` job.
+
+Create a file for the controller job called `plugin-ebs-controller.nomad.hcl` with the following content.
+
+```hcl
+job "plugin-aws-ebs-controller" {
+  datacenters = ["dc1"]
+
+  group "controller" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-ebs-csi-driver:v0.10.1"
+
+        args = [
+          "controller",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+      }
+
+      csi_plugin {
+        id        = "aws-ebs0"
+        type      = "controller"
+        mount_dir = "/csi"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+Create a file for the node job named `plugin-ebs-nodes.nomad.hcl` with the following content.
+
+```hcl
+job "plugin-aws-ebs-nodes" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but this ensures
+  # that all nodes in the DC have a copy.
+  type = "system"
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-ebs-csi-driver:v0.10.1"
+
+        args = [
+          "node",
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # node plugins must run as privileged jobs because they
+        # mount disks to the host
+        privileged = true
+      }
+
+      csi_plugin {
+        id        = "aws-ebs0"
+        type      = "node"
+        mount_dir = "/csi"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+## Deploy the plugin jobs
+
+Deploy both jobs with `nomad job run plugin-ebs-controller.nomad.hcl` and
+`nomad job run plugin-ebs-nodes.nomad.hcl`. It will take a few moments
+for the plugins to register themselves as healthy with Nomad after the
+job itself is running. You can check the plugin status with the `nomad plugin status` command.
+
+Note that the plugin does not have a namespace, even though the jobs
+that launched it do. Plugins are treated as resources available to the
+whole cluster in the same way as Nomad clients.
+
+```shell-session
+$ nomad job status
+ID                         Type     Priority  Status   Submit Date
+plugin-aws-ebs-controller  service  50        running  2020-03-20T10:49:13-04:00
+plugin-aws-ebs-nodes       system   50        running  2020-03-20T10:49:17-04:00
+```
+
+```shell-session
+$ nomad plugin status aws-ebs0
+ID                   = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created    Modified
+de2929cc  ac41c184  controller  0        run      running  1m26s ago  1m8s ago
+d1d4831e  ac41c184  nodes       0        run      running  1m22s ago  1m18s ago
+2b815e02  b896731a  nodes       0        run      running  1m22s ago  1m14s ago
+```
+
+## Register the volume
+
+The CSI plugins need to be told about each volume they manage, so for
+each volume you'll run `nomad volume register`. Earlier you used
+Terraform to output a `volume.hcl` file with the volume definition.
+
+```shell-session
+$ nomad volume register volume.hcl
+```
+
+```shell-session
+$ nomad volume status mysql
+ID                   = mysql
+Name                 = mysql
+External ID          = vol-0b756b75620d63af5
+Plugin ID            = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+Access Mode          = <none>
+Attachment Mode      = <none>
+Mount Options        = <none>
+Namespace            = default
+
+Allocations
+No allocations placed
+```
+
+The volume status output above indicates that the volume is
+ready to be scheduled, but has no allocations currently using it.
+
+## Deploy MySQL
+
+### Create the job file
+
+You are now ready to deploy a MySQL database that can use Nomad host
+volumes for storage. Create a file called `mysql.nomad.hcl` and provide it
+the following contents.
+
+```hcl
+job "mysql-server" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mysql-server" {
+    count = 1
+
+    volume "mysql" {
+      type            = "csi"
+      read_only       = false
+      source          = "mysql"
+      access_mode     = "single-node-writer"
+      attachment_mode = "file-system"
+    }
+
+    network {
+      port "db" {
+        static = 3306
+      }
+    }
+
+    restart {
+      attempts = 10
+      interval = "5m"
+      delay    = "25s"
+      mode     = "delay"
+    }
+
+    task "mysql-server" {
+      driver = "docker"
+
+      volume_mount {
+        volume      = "mysql"
+        destination = "/srv"
+        read_only   = false
+      }
+
+      env {
+        MYSQL_ROOT_PASSWORD = "password"
+      }
+
+      config {
+        image = "hashicorp/mysql-portworx-demo:latest"
+        args  = ["--datadir", "/srv/mysql"]
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500
+        memory = 1024
+      }
+
+      service {
+        name = "mysql-server"
+        port = "db"
+
+        check {
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+#### Notes about the above job specification
+
+- The service name is `mysql-server` which you will use later to
+  connect to the database.
+
+- The `read_only` argument is supplied on all of the volume-related
+  stanzas in to help highlight all of the places you would need to
+  change to make a read-only volume mount. Consult the [`volume`],
+  and [`volume_mount`] specifications for more details.
+
+- For lower-memory instances, you might need to reduce the requested
+  memory in the resources stanza to harmonize with available resources
+  in your cluster.
+
+### Run the job
+
+Register the job file you created in the previous step with the
+following command.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "aa478d82"
+    Evaluation triggered by job "mysql-server"
+    Allocation "6c3b3703" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "aa478d82" finished with status "complete"
+```
+
+The allocation status will have a section for the CSI volume, and the
+volume status will show the allocation claiming the volume.
+
+```shell-session
+$ nomad alloc status 6c3b3703
+CSI Volumes:
+ID     Read Only
+mysql  false
+```
+
+```shell-session
+$ nomad volume status mysql
+ID                   = mysql
+Name                 = mysql
+External ID          = vol-0b756b75620d63af5
+Plugin ID            = aws-ebs0
+Provider             = ebs.csi.aws.com
+Version              = v0.10.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 2
+Nodes Expected       = 2
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = <none>
+Namespace            = default
+
+Allocations
+ID        Node ID   Task Group    Version  Desired  Status   Created    Modified
+6c3b3703  ac41c184  mysql-server  3        run      running  1m40s ago  1m2s ago
+```
+
+## Write data to MySQL
+
+### Connect to MySQL
+
+Using the mysql client (installed [earlier][install_mysql]), connect
+to the database and access the information.
+
+```shell-session
+$ mysql -h mysql-server.service.consul -u web -p -D itemcollection
+```
+
+The password for this demo database is `password`.
+
+<Note>
+
+ This tutorial is for demo purposes and does not
+follow best practices for securing database passwords. Consult [Keeping
+Passwords Secure][password-security] for more information.
+
+</Note>
+
+Consul is installed alongside Nomad in this cluster so you are able to
+connect using the `mysql-server` service name you registered with our
+task in our job file.
+
+### Add test data
+
+Once you are connected to the database, verify the table `items`
+exists.
+
+```sql
+mysql> show tables;
++--------------------------+
+| Tables_in_itemcollection |
++--------------------------+
+| items                    |
++--------------------------+
+1 row in set (0.00 sec)
+```
+
+Display the contents of this table with the following command.
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
++----+----------+
+3 rows in set (0.00 sec)
+```
+
+Now add some data to this table (after you terminate our database in
+Nomad and bring it back up, this data should still be intact).
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('glove');
+```
+
+Run the `INSERT INTO` command as many times as you like with different
+values.
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('hat');
+mysql> INSERT INTO items (name) VALUES ('keyboard');
+```
+
+Once you are done, type `exit` and return back to the Nomad client
+command line.
+
+```sql
+mysql> exit
+Bye
+```
+
+## Destroy the database job
+
+Run the following command to stop and purge the MySQL job from the
+cluster.
+
+```shell-session
+$ nomad stop -purge mysql-server
+==> Monitoring evaluation "6b784149"
+    Evaluation triggered by job "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6b784149" finished with status "complete"
+```
+
+Verify mysql is no longer running in the cluster.
+
+```shell-session
+$ nomad job status mysql
+No job(s) with prefix or id "mysql" found
+```
+
+## Re-deploy and verify
+
+Using the `mysql.nomad.hcl` job file [from earlier][create-job], re-deploy
+the database to the Nomad cluster.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "61b4f648"
+    Evaluation triggered by job "mysql-server"
+    Allocation "8e1324d2" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61b4f648" finished with status "complete"
+```
+
+Once you re-connect to MySQL, you should be able to verify that the
+information you added prior to destroying the database is still
+present.
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
+|  4 | glove    |
+|  5 | hat      |
+|  6 | keyboard |
++----+----------+
+6 rows in set (0.00 sec)
+```
+
+## Cleanup
+
+Once you have completed this guide, you should perform the following
+cleanup steps.
+
+- Stop and purge the `mysql-server` job.
+
+- Unregister the EBS volume from Nomad with `nomad volume deregister mysql`.
+
+- Stop and purge the `plugin-aws-ebs-controller` and `plugin-aws-ebs-nodes` job.
+
+- Destroy the EBS volume with `terraform destroy`.
+
+## Summary
+
+In this guide, you deployed a CSI plugin to Nomad, registered an AWS
+EBS volume for that plugin, and created a job that mounted this volume
+to a Docker MySQL container that wrote data that persisted beyond the
+job’s lifecycle.
+
+[`allow_privileged`]: /nomad/docs/deploy/task-driver/docker#allow_privileged
+[`host_volume`]: /nomad/docs/configuration/client#host_volume
+[`volume_mount`]: /nomad/docs/job-specification/volume_mount
+[`volume`]: /nomad/docs/job-specification/volume
+[aws-ebs-csi-driver]: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
+[create-job]: #create-the-job-file
+[csi-spec]: https://github.com/container-storage-interface/spec
+[docker-forums]: https://forums.docker.com/t/make-mount-point-accesible-from-container-to-host-rshared-not-working/108759
+[install_mysql]: #install-the-mysql-client
+[k8s-drivers]: https://kubernetes-csi.github.io/docs/drivers.html
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[password-security]: https://dev.mysql.com/doc/refman/8.0/en/password-security.html
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture#high-availability
diff --git a/content/nomad/v1.11.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx b/content/nomad/v1.11.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx
new file mode 100644
index 0000000000..ece0fca76d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/stateful-workloads/dynamic-host-volumes.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Use dynamic host volumes
+description: >-
+  Create, configure, and deploy a dynamic host volume. Run a Nomad job with a workload that uses the dynamic host volume for the persistent storage of application data.
+---
+
+# Use dynamic host volumes
+
+This page describes how to to create and configure a dynamic host volume and use
+it to persist application data.
+
+## Introduction
+
+Nomad dynamic host volumes manage storage for stateful workloads without
+requiring a restart of the Nomad nodes to apply configuration changes. They
+provide a workload-agnostic way to specify resources and work with the `exec`,
+`java`, and `docker` task drivers. You create dynamic host volumes via the CLI
+or API and then configure the job with the
+[`volume`](/nomad/docs/job-specification/volume) and
+[`volume_mount`](/nomad/docs/job-specification/volume_mount) blocks in the job
+specification.
+
+Refer to the [dynamic host volume
+specification][dhv_spec] for more information on specifying dynamic host
+volumes.
+
+## Requirements
+
+A Nomad cluster v1.10.0 or greater with the Docker task driver enabled.
+
+## Create the volume specification
+
+
+Create a file with the name `volume.hcl`, add the following content to it, and
+save the file.
+
+<CodeBlockConfig filename="volume.hcl">
+
+```hcl
+namespace = "default"
+name      = "example"
+type      = "host"
+
+# mkdir is the default built-in plugin
+plugin_id = "mkdir"
+
+# allows mounting by only one allocation at a time
+capability {
+  access_mode     = "single-node-single-writer"
+  attachment_mode = "file-system"
+}
+```
+
+</CodeBlockConfig>
+
+Create the volume.
+
+```shell-session
+$ nomad volume create ./volume.hcl
+==> Created host volume example with ID 02eb1d8e-945e-50ee-7640-68b92f622870
+  ✓ Host volume "02eb1d8e" ready
+
+    2025-01-21T14:56:35-05:00
+    ID        = 02eb1d8e-945e-50ee-7640-68b92f622870
+    Name      = example
+    Namespace = default
+    Plugin ID = mkdir
+    Node ID   = d87c86d7-d22b-f811-c329-09e263995e86
+    Node Pool = default
+    Capacity  = 0 B
+    State     = ready
+    Host Path = /run/nomad/dev/alloc_mounts/02eb1d8e-945e-50ee-7640-68b92f622870
+```
+
+Verify the volume was fingerprinted on the node with the node ID from the output.
+
+```shell-session
+$ nomad node status -verbose d87c86d7-d22b-f811-c329-09e263995e86
+...
+Host Volumes
+Name         ReadOnly  Source
+example      false     /run/nomad/dev/alloc_mounts/02eb1d8e-945e-50ee-7640-68b92f622870
+...
+```
+
+Set the volume ID as an environment variable.
+
+```shell-session
+$ VOLUME_ID=02eb1d8e-945e-50ee-7640-68b92f622870
+```
+
+## Create and run the job
+
+The following job specification mounts the volume with the name `example` from
+the dynamic host volume specification.
+
+Create a file with the name `example.nomad.hcl`, add the following content to
+it, and save the file.
+
+<CodeBlockConfig filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+
+  group "group" {
+
+    # claim the dynamic host volume for the allocation
+    volume "groupvol" {
+      type            = "host"
+      source          = "example"
+      access_mode     = "single-node-single-writer"
+      attachment_mode = "file-system"
+    }
+
+    network {
+      port "www" {
+        to = 8001
+      }
+    }
+
+    task "task" {
+
+      driver = "docker"
+
+      config {
+        image   = "busybox:1"
+        command = "httpd"
+        args    = ["-vv", "-f", "-p", "8001", "-h", "/srv"]
+        ports   = ["www"]
+      }
+
+      # mount the claimed volume to the task
+      volume_mount {
+        volume      = "groupvol"
+        destination = "/srv"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Run the job.
+
+```shell-session
+$ nomad run ./example.nomad.hcl
+```
+
+## Interact with the host volume
+
+Export the Allocation ID of the job into an environment variable with the name `ALLOC_ID`.
+
+```shell-session
+$ ALLOC_ID=$(nomad alloc status -t '{{ range . }}{{if eq .JobID "example"}}{{if eq .DesiredStatus "run"}}{{ .ID }}{{end}}{{end}}{{end}}')
+```
+
+Open a shell session in the allocation.
+
+```shell-session
+$ nomad alloc exec -job example /bin/sh
+```
+
+In the allocation's shell prompt, write a file to the mounted volume.
+
+```shell-session
+$ echo '<html>hello, world</html>' > /srv/index.html
+```
+
+Exit the allocation's shell session.
+
+```shell-session
+exit
+```
+
+Get the address of the HTTP server running in the allocation.
+
+```shell-session
+$ nomad alloc status $ALLOC_ID
+...
+Allocation Addresses (mode = "bridge"):
+Label  Dynamic  Address
+*www   yes      192.168.1.160:26512 -> 8001
+```
+
+
+Open the address in your web browser or use a tool like `curl` to see the change.
+
+```shell-session
+$ curl -s "http://192.168.1.160:26512"
+<html>hello, world</html>
+```
+
+## Reschedule the allocation
+
+Stop the allocation to force Nomad to reschedule it.
+
+```shell-session
+$ nomad alloc stop $ALLOC_ID
+```
+
+Open a shell session in the replacement allocation.
+
+```shell-session
+$ nomad alloc exec -job example /bin/sh
+```
+
+In the allocation's shell prompt, read the file previously written to the
+mounted volume.
+
+```shell-session
+$ cat /srv/index.html
+<html>hello, world</html>
+```
+
+Exit the allocation's shell session.
+
+```shell-session
+exit
+```
+
+## Clean up
+
+Stop the `example` job.
+
+```shell-session
+$ nomad job stop example
+```
+
+Delete the dynamic host volume.
+
+```shell-session
+$ nomad volume delete -type host $VOLUME_ID
+```
+
+## Next steps
+
+
+Refer to the following resources for more information on dynamic host volumes
+and related concepts.
+
+- [The Nomad Volume Specification][dhv_spec]
+- [The `nomad alloc exec` command][alloc_exec]
+
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
+[config_static_host_vol]: /nomad/docs/configuration/client#host_volume-block
+[tutorial_static_host_vol]: /nomad/docs/stateful-workloads/static-host-volumes
+[tf]: https://github.com/hashicorp/nomad/tree/main/terraform#provision-a-nomad-cluster-in-the-cloud
+[alloc_exec]: /nomad/commands/alloc/exec
diff --git a/content/nomad/v1.11.x/content/docs/stateful-workloads/index.mdx b/content/nomad/v1.11.x/content/docs/stateful-workloads/index.mdx
new file mode 100644
index 0000000000..5a5e679a61
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/stateful-workloads/index.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Stateful workloads
+description: >-
+  Discover how to create and configure workloads requiring persistent
+  storage with Nomad's CSI integration, Docker volumes support, and
+  host volumes support.
+---
+
+# Stateful workloads
+
+Nomad allows users to mount persistent data from local or remote storage volumes
+into task environments in several ways:
+
+- Container Storage Interface (CSI) plugins
+- Nomad dynamic host volumes
+- Nomad static host volumes
+- Task driver specific volumes, such as Docker volume drivers
+
+Nomad's [Container Storage Interface (CSI)][csi-spec] integration can manage
+external storage volumes for stateful workloads running inside your cluster. CSI
+providers are third-party plugins that run as Nomad jobs and can orchestrate the creation and
+mounting of volumes created by your cloud or storage provider. [AWS Elastic Block Storage],
+[Azure disk], [GCE Persistent Disk], and [Alicloud Disk] are a few of the available
+block-device plugins available as CSI plugins. You can find a more comprehensive list
+in the [CSI Developer Documentation][csi-drivers]
+
+Nomad is aware of CSI-managed volumes during the
+scheduling process, enabling it to schedule your workloads based on the
+availability of volumes on a specific client.
+
+Nomad's host volumes come in two types - dynamic and static. Dynamic host volumes are, similar
+to CSI volumes, managed by Nomad with the help of [plugins][dhv_plugins]. The plugin creates the volumes
+and mounts them on the client, and Nomad makes the volumes available to the task group. Plugins follow a
+[specification][dhv_spec] that allows anyone to write a plugin for their storage needs.
+
+Static Host volumes allow you to mount any existing directory on the Nomad client into an allocation.
+These directories can be directories on a client, but can also be mounted networked or clustered
+filesystems like NFS, SeaweedFS or GlusterFS. Static host volumes are defined in the [client configuration][config_static_host_vol]
+file and are available to all tasks running on that client.
+
+The Docker task driver's support for [volumes][docker-volumes] enables Nomad to
+integrate with software-defined storage (SDS) solutions that have native support for Docker. Keep in mind that
+Nomad does not actually manage storage pools or replication as these tasks are
+delegated to the SDS providers. Please assess all factors and risks when
+utilizing such providers to run stateful workloads (such as your production
+database).
+
+For more information on the various options for stateful storage in Nomad, refer to the [Considerations for Stateful Workloads
+Workloads guide][considerations_stateful_workloads].
+
+In these guides, you will deploy a stateful application to a Nomad cluster and
+demonstrate that the data is persisted beyond the life of the allocation.
+
+
+[docker-volumes]: /nomad/docs/job-declare/task-driver/docker#volumes
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers]: https://kubernetes-csi.github.io/docs/drivers.html
+[aws elastic block storage]: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
+[azure disk]: https://github.com/kubernetes-sigs/azuredisk-csi-driver
+[gce persistent disk]: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver
+[alicloud disk]: https://github.com/AliyunContainerService/csi-plugin
+[dhv_spec]: /nomad/docs/other-specifications/volume/host
+[dhv_plugins]: /nomad/docs/architecture/storage/host-volumes
+[config_static_host_vol]: /nomad/docs/configuration/client#host_volume-block
+[considerations_stateful_workloads]: /nomad/docs/architecture/storage/stateful-workloads
diff --git a/content/nomad/v1.11.x/content/docs/stateful-workloads/static-host-volumes.mdx b/content/nomad/v1.11.x/content/docs/stateful-workloads/static-host-volumes.mdx
new file mode 100644
index 0000000000..03a2f25a39
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/stateful-workloads/static-host-volumes.mdx
@@ -0,0 +1,389 @@
+---
+layout: docs
+page_title: Use static host volumes
+description: >-
+  Configure and deploy a host volume to support a MySQL workload that requires
+  persistent storage.
+---
+
+# Use static host volumes
+
+Static host volumes can manage storage for stateful workloads running inside your
+Nomad cluster. This tutorial walks you through deploying a MySQL workload using
+a static host volume for persistent storage. Unlike [dynamic host volumes][dhv_tutorial], static
+host volumes are defined in the Nomad client configuration and their lifecycle is
+managed outside of Nomad.
+
+Static host volumes provide a workload-agnostic way to specify resources,
+available for Nomad drivers like `exec`, `java`, and `docker`. Refer to the
+[`host_volume` specification][`host_volume`] for more information.
+Nomad is aware of host volumes during the scheduling process,
+which enables it to make scheduling decisions based on the availability of
+static host volumes on a specific client.
+
+This can be contrasted with Nomad support for Docker volumes. Because Docker
+volumes are managed outside of Nomad and the Nomad scheduler is not aware of
+them, Docker volumes have to either be deployed to all clients or operators have
+to use an additional, manually-maintained constraint to inform the scheduler
+where they are present.
+
+## Prerequisites
+
+To perform the tasks described in this guide, you need to have a Nomad
+environment with Consul installed. Consul is used for service discovery and is not necessary for
+static host volumes. You can use this [Terraform environment][nomad-tf] to provision a
+sandbox environment. This tutorial will assume a cluster with one server node and three
+client nodes.
+
+<Note>
+
+ This tutorial is for demo purposes and only assumes a single server
+node. Please consult the [reference architecture][reference-arch] for
+production configuration.
+
+</Note>
+
+### Install the MySQL client
+
+You will use the MySQL client to connect to our MySQL database and verify our data.
+Ensure it is installed on a node with access to port 3306 on your Nomad clients:
+
+Ubuntu:
+
+```shell-session
+$ sudo apt install mysql-client
+```
+
+CentOS:
+
+```shell-session
+$ sudo yum install mysql
+```
+
+macOS via Homebrew:
+
+```shell-session
+$ brew install mysql-client
+```
+
+## Build the static host volume
+
+### Create a target directory
+
+On a Nomad client node in your cluster, create a directory that will be used for
+persisting the MySQL data. For this example, let's create the directory
+`/opt/mysql/data`.
+
+```shell-session
+$ sudo mkdir -p /opt/mysql/data
+```
+
+You might need to change the owner on this folder if the Nomad client does not
+run as the `root` user.
+
+```shell-session
+$ sudo chown «Nomad user» /opt/mysql/data
+```
+
+### Configure the client
+
+Edit the Nomad configuration on this Nomad client to create the static host volume
+definition.
+
+Add a [`host_volume`] block to the `client` block of your Nomad configuration:
+
+```hcl
+  host_volume "mysql" {
+    path      = "/opt/mysql/data"
+    read_only = false
+  }
+```
+
+Save this change, and then restart the Nomad service on this client to make the
+static host volume active. While still on the client, you can verify that the host
+volume is configured by using the `nomad node status` command as shown below:
+
+```shell-session
+$ nomad node status -short -self
+ID           = 12937fa7
+Name         = ip-172-31-15-65
+Class        = <none>
+DC           = dc1
+Drain        = false
+Eligibility  = eligible
+Status       = ready
+Host Volumes = mysql
+Drivers      = docker,exec,java,mock_driver,raw_exec,rkt
+...
+```
+
+## Deploy MySQL
+
+### Create the job file
+
+You are now ready to deploy a MySQL database that can use the static host volumes for
+storage. Create a file called `mysql.nomad.hcl` and provide it the following
+contents:
+
+```hcl
+job "mysql-server" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "mysql-server" {
+    count = 1
+
+    volume "mysql" {
+      type      = "host"
+      read_only = false
+      source    = "mysql"
+    }
+
+    restart {
+      attempts = 10
+      interval = "5m"
+      delay    = "25s"
+      mode     = "delay"
+    }
+
+    task "mysql-server" {
+      driver = "docker"
+
+      volume_mount {
+        volume      = "mysql"
+        destination = "/var/lib/mysql"
+        read_only   = false
+      }
+
+      env = {
+        "MYSQL_ROOT_PASSWORD" = "password"
+      }
+
+      config {
+        image = "hashicorp/mysql-portworx-demo:latest"
+
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500
+        memory = 1024
+      }
+
+      service {
+        name = "mysql-server"
+        port = "db"
+
+        check {
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+    network {
+      port "db" {
+        static = 3306
+      }
+    }
+  }
+}
+```
+
+#### Notes about the above job specification
+
+- The service name is `mysql-server` which you will use later to connect to the
+  database.
+
+- The `read_only` argument is supplied on all of the volume-related stanzas in
+  to help highlight all of the places you would need to change to make a
+  read-only volume mount. Please see the [`host_volume`], [`volume`], and
+  [`volume_mount`] specifications for more details.
+
+- For lower-memory instances, you might need to reduce the requested memory in
+  the resources stanza to harmonize with available resources in your cluster.
+
+### Run the job
+
+Register the job file you created in the previous step with the following
+command:
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "aa478d82"
+    Evaluation triggered by job "mysql-server"
+    Allocation "6c3b3703" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "aa478d82" finished with status "complete"
+```
+
+Check the status of the allocation and ensure the task is running:
+
+```shell-session
+$ nomad status mysql-server
+ID            = mysql-server
+...
+Summary
+Task Group    Queued  Starting  Running  Failed  Complete  Lost
+mysql-server  0       0         1        0       0         0
+```
+
+## Write data to MySQL
+
+### Connect to MySQL
+
+Using the mysql client (installed [earlier][install_mysql]), connect to the
+database and access the information:
+
+```shell-session
+$ mysql -h mysql-server.service.consul -u web -p -D itemcollection
+```
+
+The password for this demo database is `password`.
+
+<Note>
+
+ This tutorial is for demo purposes and does not follow best
+practices for securing database passwords. See [Keeping Passwords
+Secure][password-security] for more information.
+
+</Note>
+
+Consul is installed alongside Nomad in this cluster so you are able to
+connect using the `mysql-server` service name you registered with our task in
+our job file.
+
+### Add test data
+
+Once you are connected to the database, verify the table `items` exists:
+
+```sql
+mysql> show tables;
++--------------------------+
+| Tables_in_itemcollection |
++--------------------------+
+| items                    |
++--------------------------+
+1 row in set (0.00 sec)
+```
+
+Display the contents of this table with the following command:
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
++----+----------+
+3 rows in set (0.00 sec)
+```
+
+Now add some data to this table (after you terminate our database in Nomad and
+bring it back up, this data should still be intact):
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('glove');
+```
+
+Run the `INSERT INTO` command as many times as you like with different values.
+
+```sql
+mysql> INSERT INTO items (name) VALUES ('hat');
+mysql> INSERT INTO items (name) VALUES ('keyboard');
+```
+
+Once you are done, type `exit` and return back to the Nomad client command
+line:
+
+```sql
+mysql> exit
+Bye
+```
+
+## Destroy the database job
+
+Run the following command to stop and purge the MySQL job from the cluster:
+
+```shell-session
+$ nomad stop -purge mysql-server
+==> Monitoring evaluation "6b784149"
+    Evaluation triggered by job "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6b784149" finished with status "complete"
+```
+
+Verify no jobs are running in the cluster:
+
+```shell-session
+$ nomad status
+No running jobs
+```
+
+In more advanced cases, the directory backing the static host volume could be a mounted
+network filesystem, like NFS, or cluster-aware filesystem, like GlusterFS or SeaweedFS. This
+can enable more complex, automatic failure-recovery scenarios in the event of a
+node failure.
+
+## Re-deploy and verify
+
+Using the `mysql.nomad.hcl` job file [from earlier][create_job], re-deploy the
+database to the Nomad cluster.
+
+```shell-session
+$ nomad run mysql.nomad.hcl
+==> Monitoring evaluation "61b4f648"
+    Evaluation triggered by job "mysql-server"
+    Allocation "8e1324d2" created: node "be8aad4e", group "mysql-server"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "61b4f648" finished with status "complete"
+```
+
+Once you re-connect to MySQL, you should be able to see that the information you
+added prior to destroying the database is still present:
+
+```sql
+mysql> select * from items;
++----+----------+
+| id | name     |
++----+----------+
+|  1 | bike     |
+|  2 | baseball |
+|  3 | chair    |
+|  4 | glove    |
+|  5 | hat      |
+|  6 | keyboard |
++----+----------+
+6 rows in set (0.00 sec)
+```
+
+## Clean up
+
+Once you have completed this guide, you should perform the following cleanup steps:
+
+- Stop and purge the `mysql-server` job.
+
+- Remove the `host_volume "mysql"` stanza from your Nomad client configuration
+  and restart the Nomad service on that client
+
+- Remove the /opt/mysql/data folder and as much of the directory tree that you
+  no longer require.
+
+## Summary
+
+In this guide, you configured a static host volume on a Nomad client using a client-local
+directory. You created a job that mounted this volume to a Docker MySQL container
+and wrote data that persisted beyond the job's lifecycle.
+
+[`host_volume`]: /nomad/docs/configuration/client#host_volume-block
+[`volume_mount`]: /nomad/docs/job-specification/volume_mount
+[`volume`]: /nomad/docs/job-specification/volume
+[create_job]: #create-the-job-file
+[install_mysql]: #install-the-mysql-client
+[nomad-tf]: https://github.com/hashicorp/nomad/tree/master/terraform#provision-a-nomad-cluster-in-the-cloud
+[password-security]: https://dev.mysql.com/doc/refman/8.0/en/password-security.html
+[reference-arch]: /nomad/docs/deploy/production/reference-architecture#high-availability
+[dhv_tutorial]: /nomad/docs/stateful-workloads/dynamic-host-volumes
+
diff --git a/content/nomad/v1.11.x/content/docs/upgrade/index.mdx b/content/nomad/v1.11.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..2314bd7fdb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Upgrade Nomad'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Upgrade HashiCorp Nomad without causing an outage. Review the upgrade process for a new version, for moving from Nomad community edition to Nomad Enterprise, and for Raft protocol version three.
+---
+
+# Upgrade Nomad
+
+This page provides guidance on upgrading HashiCorp Nomad without causing an
+outage. Review the upgrade process for a new version, for moving from Nomad
+Community to Nomad Enterprise, and for Raft protocol version three.
+
+## Introduction
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](//nomad/docs/deploy/clusters/federate-regions),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/docs/manage/migrate-workloads) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/commands/monitor
+[node-status]: /nomad/commands/node/status
+[server-members]: /nomad/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/docs/manage/outage-recovery#manual-recovery-using-peers-json)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/docs/manage/outage-recovery#manual-recovery-using-peers-json
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.11.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.11.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..81a90bda07
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1816 @@
+---
+layout: docs
+page_title: Nomad version-specific upgrade guides
+description: |-
+  Review upgrade details for specific versions of Nomad.
+---
+
+# Nomad version-specific upgrade guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.11.0
+
+#### Sysbatch jobs will no longer accept `reschedule` blocks
+
+In Nomad 1.11.0, submitting a sysbatch job with a `reschedule` block returns
+an error instead of being silently ignored, as it was in previous versions. The
+same behavior applies to system jobs.
+
+#### Eval broker metrics for dispatch and periodic jobs
+
+The leader records metrics for the eval broker. In Nomad 1.11.0 the `job` label
+on the `nomad.nomad.broker.wait_time`, `nomad.nomad.broker.process_time`,
+`nomad.nomad.broker.response_time`, and `nomad.nomad.broker.eval_waiting`
+metrics refers to the parent job ID for dispatch and periodic jobs. The
+`nomad.nomad.broker.eval_waiting` no longer has an `eval_id` label. For clusters
+running high volume dispatch workloads, this change significantly reduces
+metrics cardinality and memory usage on the leader.
+
+#### ACL policies no longer silently ignore duplicate or invalid keys
+
+Nomad 1.11.0 introduces stricter validation for ACL policies. Policy writes that
+include duplicate or invalid keys will be rejected with an error instead of
+being silently ignored. Any existing policies with duplicate or invalid keys
+will continue to work, but the source policy document will need to be updated
+to be valid before it can be written to Nomad.
+
+#### Maximum number of allocations per job is limited by default
+
+Nomad 1.11.0 limits the maximum number of allocations for a job to the value of
+the new [`job_max_count`](/nomad/docs/configuration/server#job_max_count) server
+configuration option, which defaults to 50000. The number of allocations is
+determined from the sum of the job's task group `count` fields. This limit is
+enforced at the time the job is submitted or scaled, and updating the value will
+not impact existing jobs.
+
+#### Deprecated resource fields on Node API
+
+The `Resources` and `Reserved` fields on the Go API's `Node` struct, as well as
+the equivalent fileds on the [Read Node](/nomad/api-docs/nodes#read-node) API,
+are deprecated. These fields are never populated. Use the `NodeResources` and
+`ReservedResources` fields instead.
+
+#### Enterprise product usage reporting <EnterpriseAlert inline />
+
+Nomad Enterprise 1.11.0 adds detailed product usage information to
+[automated license utilization reporting](/nomad/docs/enterprise/license/utilization-reporting).
+
+## Nomad 1.10.6
+
+#### ACL policies no longer silently ignore duplicate or invalid keys
+
+Nomad 1.10.6 introduces stricter validation for ACL policies. Policy writes that
+include duplicate or invalid keys will be rejected with an error instead of
+being silently ignored. Any existing policies with duplicate or invalid keys
+will continue to work, but the source policy document will need to be updated
+to be valid before it can be written to Nomad.
+
+#### Enterprise product usage reporting <EnterpriseAlert inline />
+
+Nomad Enterprise 1.10.6 adds detailed product usage information to
+[automated license utilization reporting](/nomad/docs/enterprise/license/utilization-reporting).
+
+## Nomad 1.10.2
+
+#### Clients respect `telemetry.publish_allocation_metrics`
+
+Nomad 1.10.2 fixed a bug where allocation metrics were collected and published
+even if the
+[`telemetry.publish_allocation_metrics`](/nomad/docs/configuration/telemetry#publish_allocation_metrics)
+configuration field was unset or set to `false`. If you are monitoring
+allocation metrics, you will need to ensure your Nomad clients set this field to
+`true`.
+
+## Nomad 1.10.1
+
+@include 'release-notes/v1-10-1/breaking-raft-peer.mdx'
+
+@include 'release-notes/v1-10-1/breaking-agent-exit.mdx'
+
+#### Added Server `start_timeout` Configuration Option
+
+Nomad 1.10.1 introduces a new server configuration option named `start_timeout`
+with a default value of `30s`. This duration is used to monitor the server setup
+and startup processes which must complete before it is considered healthy, such
+as keyring decryption. If these processes do not complete before the timeout is
+reached, the server process will exit and any errors logged to the console.
+
+#### Corrected `/v1/acl/token/self` response codes
+
+Nomad 1.10.1 responds with different HTTP response codes to API calls sent to
+`/v1/acl/token/self`. For users that do not have ACLs enabled, the endpoint
+responds with 200 code and a response body that indicates that ACLs are
+disabled. Previously, the response code in such a scenario was 404.
+
+For users that do have ACLs enabled and do not have a valid ACL token present,
+the endpoint responds with 403 code. Previously, the response code in such a
+scenario was 404.
+
+## Nomad 1.10.0
+
+@include 'release-notes/v1-10/deprecate-variable-limits.mdx'
+
+@include 'release-notes/v1-10/breaking-disconnect-fields-removed.mdx'
+
+@include 'release-notes/v1-10/breaking-go-sdk.mdx'
+
+@include 'release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx'
+
+@include 'release-notes/v1-10/breaking-plugin-dir.mdx'
+
+@include 'release-notes/v1-10/breaking-sentinel-apply.mdx'
+
+@include 'release-notes/v1-10/breaking-affinity-spread.mdx'
+
+@include 'release-notes/v1-10/breaking-vault-consul-token.mdx'
+
+## Nomad 1.9.9
+
+#### Added Server `start_timeout` Configuration Option
+
+Nomad 1.9.9 introduces a new server configuration option named `start_timeout`
+with a default value of `30s`. This duration is used to monitor the server setup
+and startup processes which must complete before it is considered healthy, such
+as keyring decryption. If these processes do not complete before the timeout is
+reached, the server process will exit and any errors logged to the console.
+
+## Nomad 1.9.5
+
+#### CNI plugins
+
+Nomad 1.9.5 includes a bug fix for restoring allocation networking after a
+client host reboot. This fix requires recent versions of the CNI reference
+plugins (minimum 1.2.0) and will fallback to the existing behavior if the CNI
+reference plugins cannot support the fix.
+
+We recommend installing the CNI reference plugins from the [CNI project release
+page](https://github.com/containernetworking/plugins/releases) rather than your
+Linux distribution's package manager.
+
+## Nomad 1.9.4
+
+#### Security updates to default deny lists
+
+In Nomad 1.9.4, the default `function_denylist` includes `executeTemplate`, as
+a measure to prevent accidental or malicious infinitely recursive execution.
+Users that require `executeTemplate` should update their
+[configuration](/nomad/docs/v1.9.x/job-specification/template#function_denylist).
+
+Additionally, the [default client env deny
+list](/nomad/docs/v1.9.x/configuration/client#env-denylist) includes more environment
+variables. Users who need some of these secure environment variables passed to
+their tasks should consult the list and overwrite it in the configuration.
+
+## Nomad 1.9.3
+
+In Nomad 1.9.3, the mechanism used for calculating when objects are eligible
+for garbage collection changes to a clock-based one. This has two consequences.
+First, it allows to set arbitrarily long GC intervals. Second, it requires that
+Nomad servers are kept roughly in sync time-wise, because GC can originate in a
+follower.
+
+Nomad 1.9.2 contained a bug that could drop all cluster state on upgrade and
+has been removed from downloads.
+
+## Nomad 1.9.0
+
+#### Dropped support for older clients
+
+Nomad 1.9.0 removes support for Nomad client agents older than 1.6.0. Older
+nodes fail heartbeats. Nomad servers mark the workloads on those nodes
+as lost and reschedule them normally according to the job's [reschedule][]
+block.
+
+#### Keyring In Raft
+
+Nomad 1.9.0 stores keys used for signing Workload Identity and encrypting
+Variables in Raft, instead of storing key material in the external
+keystore. When using external KMS or Vault transit encryption for the
+[`keyring`](/nomad/docs/v1.9.x/configuration/keyring) provider, the key encryption key
+(KEK) is stored outside of Nomad and no cleartext key material exists on disk.
+When using the default AEAD provider, the key encryption key (KEK) is stored in
+Raft alongside the encrypted data encryption keys (DEK).
+
+Nomad automatically migrates the key storage for all key material on the
+first [`root_key_gc_interval`](/nomad/docs/v1.9.x/configuration/server#root_key_gc_interval) after all servers are upgraded to 1.9.0. The
+existing on-disk keystore is required to restore servers from older snapshots,
+so you should continue to back up the on-disk keystore until you no longer need
+those older snapshots.
+
+#### Support for HCLv1 removed
+
+Nomad 1.9.0 no longer supports the HCLv1 format for job specifications. Using
+the `-hcl1` option for the `job run`, `job plan`, and `job validate` commands
+will no longer work.
+
+One common use of `-hcl1` was when specifying [Docker
+labels](/nomad/docs/v1.9.x/drivers/docker#labels) with dots in their keys such as for
+DataDog autodiscovery:
+
+```hcl
+labels {
+  "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+  "com.datadoghq.ad.init_configs" = "[{}]"
+  # ...
+}
+```
+
+Quoted keys are invalid in HCLv2 blocks and must be specified with a
+list-of-maps syntax:
+
+```hcl
+labels = [
+  {
+    "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+    "com.datadoghq.ad.init_configs" = "[{}]"
+    # ...
+  }
+]
+```
+
+## Nomad 1.8.18
+
+#### ACL policies no longer silently ignore duplicate or invalid keys
+
+Nomad 1.8.18 introduces stricter validation for ACL policies. Policy writes that
+include duplicate or invalid keys will be rejected with an error instead of
+being silently ignored. Any existing policies with duplicate or invalid keys
+will continue to work, but the source policy document will need to be updated
+to be valid before it can be written to Nomad.
+
+#### Enterprise product usage reporting <EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.18 adds detailed product usage information to
+[automated license utilization reporting](/nomad/docs/enterprise/license/utilization-reporting).
+
+## Nomad 1.8.4
+
+#### Default Docker `infra_image` changed
+
+Due to the deprecation of the third-party `gcr.io` registry, the default Docker
+[`infra_image`](/nomad/docs/v1.8.x/drivers/docker#infra_image) is now `registry.k8s.io/pause-<arch>:3.3`. If you do not
+override the default, clients using the `docker` driver will make outbound
+requests to the new registry.
+
+## Nomad 1.8.3
+
+#### Nomad keyring rotation
+
+In Nomad 1.8.3, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.8.2
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.8.2, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`. We made
+this change as a result of regressions introduced by mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.8.2 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment. We made this change as a result of regressions introduced by
+mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+## Nomad 1.8.1
+
+<EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.1 includes an updated version of the Sentinel library. Users
+that have built custom Sentinel plugins must recompile them using an SDK
+supporting Sentinel Plugin Protocol Version 3. Consult the Sentinel
+[SDK Compatibility Matrix](https://github.com/hashicorp/sentinel-sdk?tab=readme-ov-file#sdk-compatibility-matrix) for appropriate Sentinel SDK versions.
+
+## Nomad 1.8.0
+
+#### Deprecated Disconnect Fields
+
+Nomad 1.8.0 introduces a `disconnect` block meant to group all the configuration
+options related to disconnected client's and server's behavior, causing the
+deprecation of the fields `stop_after_client_disconnect`, `max_client_disconnect`
+and `prevent_reschedule_on_lost`. This block also introduces new options for
+allocations reconciliation if the client regains connectivity.
+
+#### CNI Constraints
+
+In Nomad 1.8.0, jobs with `bridge` networking will have constraints added during
+job submit that require CNI plugins to be present on the node. Nodes have
+fingerprinted the available CNI plugins starting in Nomad 1.5.0.
+
+If you are upgrading from Nomad 1.5.0 or later to 1.8.0 or later, there's
+nothing additional for you to do. It's not recommended to skip more than 2
+versions of Nomad. But if you upgrade from earlier than 1.5.0 to 1.8.0 or later,
+you will need to ensure that clients have been upgraded before submitting any
+jobs that use `bridge` networking.
+
+#### Removal of `raw_exec` option `no_cgroups`
+
+In Nomad 1.7.0 the `raw_exec` plugin option for `no_cgroups` became ineffective.
+Starting in Nomad 1.8.0 attempting to set the `no_cgroups` in `raw_exec` plugin
+configuration will result in an error when starting the agent.
+
+## Nomad 1.7.11
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.7.11, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.7.10
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.7.10, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.7.10 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.7.2
+
+Nomad 1.7.2 fixes a critical bug in CPU fingerprinting in Nomad 1.7.0 and
+1.7.1. You should not install Nomad 1.7.0 or 1.7.1 and instead install the
+latest Nomad 1.7.x version.
+
+## Nomad 1.7.0
+
+<Warning>
+
+Nomad 1.7.0 contains a critical bug in keyring replication. You should not
+install Nomad 1.7.0 and instead install the latest Nomad 1.7.x version.
+
+</Warning>
+
+#### Keyring Replication Failure After Leader Election
+
+Nomad 1.7.0 introduced new RSA keys to the keyring for use in signing workload
+identities. These keys were not correctly replicated from leader to
+followers. This results in all workload identity verification failing after a
+leader election.
+
+This bug was fixed in Nomad 1.7.1.
+
+#### Vault Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault token specific to the task.
+
+The existing workflow using a Vault token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`vault.policies`](/nomad/docs/v1.7.x/job-specification/vault#policies) field is also deprecated and will work
+only with the existing workflow. Instead, you should configure a suitable Vault
+role and use that.
+
+The following agent configuration fields are deprecated:
+- [`vault.allow_unauthenticated`](/nomad/docs/v1.7.x/configuration/vault#allow_unauthenticated) will be removed in Nomad 1.10. Tasks will use
+  the workload identity without the user supplying a Vault token.
+- [`vault.task_token_ttl`](/nomad/docs/v1.7.x/configuration/vault#task_token_ttl) will be removed in Nomad 1.10. With workload
+  identity, tasks will receive their TTL configuration from the Vault role.
+- [`vault.token`](/nomad/docs/v1.7.x/configuration/vault#token) will be removed in Nomad 1.10. Nomad agents will no longer
+  make requests to authenticated endpoints except with a task's workload
+  identity.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Vault to work with workload identity. Refer to [Migrating to Using Workload
+Identity with Vault](/nomad/docs/v1.7.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault) for more details.
+
+#### Consul Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a service's or task's [Workload
+Identity](/nomad/docs/v1.7.x/concepts/workload-identity) to authenticate to Consul and obtain a Consul token specific to the
+workload.
+
+The existing workflow using a Consul token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`consul.allow_unauthenticated`](/nomad/docs/v1.7.x/configuration/consul#allow_unauthenticated) agent configuration field
+will be removed in Nomad 1.10. Tasks will use the workload identity without the
+user supplying a Consul token.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Consul to work with workload identity. See [Migrating to Using Workload
+Identity with
+Consul](/nomad/docs/v1.7.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
+for more details.
+
+#### RS256 JWT Signing Algorithm Support
+
+Prior to Nomad 1.7, workload identity JWTs were signed with the `EdDSA`
+algorithm. While `EdDSA` has numerous advantages as a signing algorithm, most
+third parties that accept JWTs expect the `RS256` signing algorithm to be used.
+
+Therefore starting in Nomad 1.7 *new* signing keys will generate an RSA key and
+sign workload identities with the `RS256` signing algorithm.
+
+Before setting up third party authentication methods to use workload
+identities, it is recommended to run [`nomad operator root keyring
+rotate`](/nomad/commands/operator/root/keyring-rotate) to ensure you
+generate a new RSA key.
+
+To verify an RSA key is present you may check the [`/.well-known/jwks.json`
+endpoint](/nomad/api-docs/operator/keyring#list-active-public-keys) on any
+Nomad agent. If you see `"kty": "RSA"`, then an RSA key exists and you do not
+need to rotate keys.
+
+New Nomad clusters will use RSA by default and are not affected.
+
+#### CPU Fingerprinting Changes
+
+Starting in Nomad 1.7, Nomad clients improve the accuracy of detected CPU
+performance metrics. The fingerprinter now takes into account heterogeneous core
+types on applicable processors. In addition, Nomad will attempt to detect and
+use the base frequency of the processor rather than the turbo frequency when
+calculating the total available CPU bandwidth. The net result of these behaviors
+is that the calculated total CPU bandwidth available on a node may change when
+upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
+meets expectations before upgrading. The [cpu concepts][cpu] documentation
+contains guidance in understanding how Nomad detects CPU metrics.
+
+#### CPU EC2 Detection Changes
+
+Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
+performance data for every EC2 instance type. In 1.7 and later Nomad instead
+gathers this data by executing the `dmidecode` command. The `dmidecode` package
+must be installed manually on some Linux distributions before the Nomad agent
+is started.
+
+#### CPU Core Isolation
+
+Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`
+attribute will be restricted to using only the CPU cores assigned to them. In
+previous versions of Nomad these tasks could also make use of other non-reserved
+CPU cores. However this feature would cause severe performance problems for
+the Linux kernel as the number of tasks increased. Operators are encouraged
+to ensure tasks making use of the `cores` attribute are given sufficient CPU
+resources before upgrading.
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.7.0 changes the behavior of the [`distinct_hosts`](/nomad/docs/v1.7.x/job-specification/constraint#distinct_hosts) constraint such that
+namespaces are taken into account when choosing feasible clients for allocation
+placement. The previous, less-expected behavior would cause **any** job with the
+same name running on a client to cause that node to be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`](/nomad/docs/v1.7.x/job-specification/constraint#distinct_property)
+constraint over [`${node.pool}`](/nomad/docs/v1.7.x/runtime/interpolation#node-attributes).
+
+#### Loading Binaries from `plugin_dir` Without Configuration
+
+Starting with Nomad 1.7.0, loading plugins that are not referenced in the agent
+configuration file is deprecated. Future versions of Nomad will only load
+plugins that have a corresponding [`plugin`](/nomad/docs/v1.7.x/configuration/plugin)
+block in the agent configuration file.
+
+#### Changes to `raw_exec`
+
+The `raw_exec` task driver now enforces memory limits via cgroups on Linux
+platforms similar to the `exec` and `docker` task drivers. The driver does
+support memory [oversubscription](/nomad/docs/v1.7.x/job-specification/resources#memory-oversubscription), which can be configured in such a
+way to nearly replicate the previously unlimited behavior.
+
+The `no_cgroups` configuration option no longer has any effect. Previously,
+setting `no_cgroups` would disable the mechanism where Nomad used the freezer
+cgroup to halt the process group of a Task before issuing a kill signal to each
+process. Starting in Nomad 1.7.0 this behavior is always enabled (and a similar
+mechanism has always been enabled on cgroups v2 systems).
+
+## Nomad 1.6.14
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.6.14, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.6.13
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.6.13, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process
+Isolation](https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation)
+that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.6.13 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/v1.6.x/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration](/nomad/docs/v1.6.x/drivers/exec#allow_caps):
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task](/nomad/docs/v1.6.x/drivers/exec#cap_add) that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide](/nomad/docs/v1.5.x/install/production/requirements#hardening-nomad)
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation](/nomad/docs/v1.5.x/drivers/docker#enabled).
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock](https://docs.kernel.org/userspace-api/landlock.html) capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`](/nomad/docs/v1.5.x/job-specification/artifact#artifact-parameters)
+and `headers` fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`](/nomad/docs/v1.5.x/configuration/client#set_environment_variables).
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`](/nomad/docs/v1.5.x/configuration/client#disable_filesystem_isolation).
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`](/nomad/docs/v1.5.x/configuration/client#decompression_size_limit) and
+[`decompression_file_count_limit`]( /nomad/docs/v1.5.x/configuration/client#decompression_file_count_limit).
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/v1.5.x/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`](/nomad/docs/v1.5.x/configuration/server#rejoin_after_leave) configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/v1.5.x/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation](/nomad/docs/v1.4.x/drivers/docker#enabled).
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/v1.4.x/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process](/nomad/docs/v1.4.x/upgrade) closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`](/nomad/docs/v1.4.x/configuration/server#raft_protocol) version is explicitly set, it must now be set to `3`.
+For more information refer to the [Upgrading to Raft Protocol 3](/nomad/docs/v1.4.x/upgrade#upgrading-to-raft-protocol-3) guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly]( https://github.com/hashicorp/nomad/issues/10440).
+
+[Nomad 1.4.0 fixes this behavior](https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906) so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues](https://github.com/hashicorp/nomad/issues/new/choose).
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`](/nomad/docs/v1.3.x/job-specification/template#uid) and
+[`gid`](/nomad/docs/v1.3.x/job-specification/template#gid) in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`](/nomad/docs/v1.3.x/configuration/client#max_kill_timeout)
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`](/nomad/docs/v1.3.x/job-specification/task#kill_timeout)
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new `artifact` client configuration and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`](/nomad/docs/v1.3.x/configuration/server#raft_protocol) version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. Refer to the [Upgrading to Raft Protocol 3](/nomad/docs/v1.3.x/upgrade#upgrading-to-raft-protocol-3) guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/v1.3.x/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/v1.3.x/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as local tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with default anonymous ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in [Consul issue 7414](https://github.com/hashicorp/consul/issues/7414)
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html)
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default
+parent](/nomad/docs/v1.3.x/configuration/client#cgroup_parent) for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse](/nomad/api-docs/v1.2.x/jobs#parse-job) API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug](https://github.com/hashicorp/nomad/issues/11563) present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`](/nomad/docs/v1.1.x/configuration#log_file) configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands]( https://github.com/hashicorp/nomad/pull/10875).
+
+For users of [`api.Client`](https://pkg.go.dev/github.com/hashicorp/nomad/api#Client) who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`](/nomad/docs/v1.1.x/drivers/docker#extra_hosts) values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`](/nomad/docs/v1.1.x/job-specification/sidecar_task#config) block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment. Refer to the Enterprise licensing documentation for details.
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Visit the [Enterprise licensing page](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/v1.1.x/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`](/nomad/docs/v1.1.x/commands/volume/create) and [`volume register`](/nomad/docs/v1.1.x/commands/volume/register) commands.
+
+The [`volume`](/nomad/docs/v1.1.x/job-specification/volume) block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation](/nomad/docs/v1.1.x/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12) in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`]( https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities) (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`](/nomad/docs/v1.1.x/drivers/java#allow_caps) task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`](/nomad/docs/v1.1.x/drivers/exec#cap_add) and [`cap_drop`](/nomad/docs/v1.1.x/drivers/exec#cap_drop)
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the `CAP_NET_RAW` Linux capability is disabled
+by default. This is one of the Linux capabilities that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`](/nomad/docs/v1.1.0/drivers/docker#allow_caps) driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as PKI, or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`](https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency) is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/v1.0.x/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain](/nomad/docs/v1.0.x/commands/node/drain) and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain](/nomad/docs/v1.0.x/upgrade#5-upgrade-clients) at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`](https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency) argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`](/nomad/docs/v1.0.x/job-specification/sidecar_task#proxy_concurrency) property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`](/nomad/docs/v0.12.x/configuration/client#template-parameters) field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/9148) in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v0.12.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/8457) in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/v0.12.x/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/v0.12.x/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/v0.11.x/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug](https://github.com/hashicorp/nomad/issues/9148) in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources](/nomad/docs/v0.11.x/configuration/client#reserved-parameters)
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time](/nomad/docs/v0.11.x/job-specification/periodic#daylight-saving-time) documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`](/nomad/docs/v0.11.x/job-specification/template) option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in the [external `nomad-driver-rkt` repository](https://github.com/hashicorp/nomad-driver-rk), it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10 and earlier
+
+Refer to the [Nomad releases page](https://github.com/hashicorp/nomad/releases) in the Nomad repo for prior release changelogs.
diff --git a/content/nomad/v1.11.x/content/docs/use-cases.mdx b/content/nomad/v1.11.x/content/docs/use-cases.mdx
new file mode 100644
index 0000000000..09f24a6983
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/use-cases.mdx
@@ -0,0 +1,174 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  Learn about Nomad's core use cases, such as Docker container orchestration, legacy application deployment, microservices, batch processing workloads, and multi-cloud federated deployemnts.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker container orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/job-declare/task-driver/docker)
+and integrates seamlessly with [Consul](/nomad/docs/networking/consul)
+and [Vault](/nomad/docs/secure/vault) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy application deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/networking/consul)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch processing workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and multi-cloud federated deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
+
+Nomad now enables [Proof Key for Code Exchange
+(PKCE)](https://oauth.net/2/pkce/) by default for new or updated OIDC auth
+methods.
+
+## Company-specific use cases
+
+This section features talks from companies on how they use Nomad to solve critical, real-world business objectives.
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
diff --git a/content/nomad/v1.11.x/content/docs/what-is-nomad.mdx b/content/nomad/v1.11.x/content/docs/what-is-nomad.mdx
new file mode 100644
index 0000000000..a60774c8d1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/docs/what-is-nomad.mdx
@@ -0,0 +1,198 @@
+---
+layout: intro
+page_title: What is Nomad?
+description: >-
+  Learn what Nomad is, what problems it can solve, its key features, and how it
+  compares to Kubernetes and AWS ECS.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<VideoEmbed url="https://www.youtube.com/embed/s_Fm9UtL4YU"/>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/job-declare/task-driver).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/plugins/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad compares to other tools
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external
+  dependencies. Operators can easily provision, manage, and scale Nomad.
+  Developers can easily define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of
+  containers per second, scale to thousands of nodes in a single cluster, and
+  easily federate across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for
+  secrets management and Consul for service discovery and dynamic configuration.
+  Nomad's Consul-like architecture and Terraform-like job specification lower
+  the barrier to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire
+space.
+
+## Nomad versus Kubernetes
+
+Kubernetes and Nomad support similar core use cases for application deployment
+and management, but they differ in a few key ways. Kubernetes aims to provide
+all the features needed to run Linux container-based applications including
+cluster management, scheduling, service discovery, monitoring, and secrets
+management. Nomad only aims to focus on cluster management and scheduling, and
+Nomad is designed with the Unix philosophy of having a small scope while
+composing with tools like Consul for service discovery/service mesh and Vault
+for secret management.
+
+<VideoEmbed url="https://www.youtube.com/embed/ZfSuted4pcA?si=IyqGzqOAnYO06398"/>
+
+### Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+### Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+### Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+### Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
+
+### Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+- High budget and full-time staffing to maintain Kubernetes
+- High-profile projects with significant investment and long-term timeline (multi-year)
+- Deploying and managing new, cloud-native applications
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+- Deploying and managing core, existing applications
+- On-premises environment, or hybrid environments
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single
+orchestrator given the natural staffing and organizational constraints. There
+are not enough DevOps members to maintain more than one orchestrator, not enough
+developers to warrant diverging workflows, or simply not enough workload
+diversity to require more than one orchestrator.
+
+### Resources
+
+Review the following resources for in-depth comparisons between Nomad and
+Kubernetes:
+
+- [A Kubernetes User's Guide to HashiCorp
+  Nomad](https://www.hashicorp.com/en/blog/a-kubernetes-user-s-guide-to-hashicorp-nomad)
+- [The Kubernetes to Nomad Cheat
+  Sheet](https://www.hashicorp.com/en/blog/the-kubernetes-to-nomad-cheat-sheet)
+- [A Kubernetes User's Guide to HashiCorp Nomad Secret Management](https://www.hashicorp.com/en/blog/a-kubernetes-user-s-guide-to-hashicorp-nomad-secret-management)
+
+## Nomad versus AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
+
+## Nomad versus Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and
+versioning infrastructure safely and efficiently. Configuration files describe
+to Terraform the components needed to run a single application or your entire
+datacenter. Terraform generates an execution plan describing what it will do to
+reach the desired state, and then executes it to build the described
+infrastructure. As the configuration changes, Terraform is able to determine
+what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to
+support any type of resource including low-level components such as compute
+instances, storage, and networking, as well as high-level components such as DNS
+entries, SaaS features, etc. Terraform knows how to create, provision, and
+manage the lifecycle of these resources. Nomad runs on existing infrastructure
+and manages the lifecycle of applications running on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to
+completion, while Nomad is an online system with long lived servers. Nomad
+allows new jobs to be submitted, existing jobs updated or deleted, and can
+handle node failures. This requires operating continuously instead of in a
+single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the
+complexity of Nomad may not outweigh simply using Terraform to statically assign
+applications to machines. At larger scales, Terraform should be used to
+provision capacity for Nomad, and Nomad used to manage scheduling applications
+to machines dynamically.
+
+## Next steps
+
+Review [use cases](/nomad/docs/use-cases) to understand the many ways
+Nomad is used in production today across many industries to solve critical,
+real-world business objectives.
diff --git a/content/nomad/v1.11.x/content/intro/README.md b/content/nomad/v1.11.x/content/intro/README.md
new file mode 100644
index 0000000000..0842885fc5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/intro/README.md
@@ -0,0 +1 @@
+delete this file and directory after publication
diff --git a/content/nomad/v1.11.x/content/intro/index.mdx b/content/nomad/v1.11.x/content/intro/index.mdx
new file mode 100644
index 0000000000..d99f81d704
--- /dev/null
+++ b/content/nomad/v1.11.x/content/intro/index.mdx
@@ -0,0 +1,48 @@
+---
+layout: intro
+page_title: Introduction to Nomad
+description: >-
+  Learn what Nomad is, what problems it can solve, its key features, and how it
+  compares to existing software.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<VideoEmbed url="https://www.youtube.com/embed/s_Fm9UtL4YU"/>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/ddeploy/task-driver).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/plugins/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad compares to other tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+## Next steps
+
+Review the [Use Cases](/nomad/docs/use-cases) page to understand the many ways
+Nomad is used in production today across many industries to solve critical,
+real-world business objectives.
diff --git a/content/nomad/v1.11.x/content/partials/api-docs/auth-method-params.mdx b/content/nomad/v1.11.x/content/partials/api-docs/auth-method-params.mdx
new file mode 100644
index 0000000000..4fa934ce4d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/api-docs/auth-method-params.mdx
@@ -0,0 +1,162 @@
+<!--
+parameters for create/update auth method APIs
+used in website/content/api-docs/acl/auth-methods.mdx
+-->
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+The name can contain alphanumeric characters and dashes. This name must be
+unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and
+`JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+creates a local or global token when performing SSO login. This field must be
+set to either `local` or `global`.
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for
+the generated tokens This can be lightly templated using HIL `${foo}` syntax.
+Defaults to `${auth_method_type}-${auth_method_name}`.
+
+ - `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token
+created by this method. When set, it will initialize the `ExpirationTime` field
+on all tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This
+field is not persisted beyond its initial use. Can be specified in the form of
+`"60s"` or `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use
+for the auth method.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+  any `.well-known` component (base path). Required for `OIDC` method type.
+  Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+  `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+  your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+  configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientAssertion` `(OIDCClientAssertion)` - Optionally send a signed
+  JWT ("[private key jwt][]") as a client assertion to the OIDC provider.
+  Browse to the [OIDC concepts][concepts-assertions] page to learn more.
+
+    - `Audience` `(array<string>)` - Who processes the assertion.
+    Defaults to the parent `ACLAuthMethodConfig`'s `OIDCDiscoveryURL`
+
+    - `KeySource` `(string: <required>)` - Specifies where to get the private
+    key to sign the JWT.
+    Available sources:
+      - "nomad": Use current active key in Nomad's keyring
+      - "private_key": Use key material in the `PrivateKey` field
+      - "client_secret": Use the `OIDCClientSecret` inherited from the parent
+      `ACLAuthMethodConfig` as an HMAC key
+
+    - `KeyAlgorithm` `(string)` is the key's algorithm. Its default values are
+    based on the `KeySource`:
+      - "nomad": "RS256"; this is from Nomad's keyring and must not be changed
+      - "private_key": "RS256"; must be RS256, RS384, or RS512
+      - "client_secret": "HS256"; must be HS256, HS384, or HS512
+
+    - `PrivateKey` `(OIDCClientAssertionKey)` - External key material to sign
+    the JWT. `KeySource` must be "private_key" to enable this.
+
+      - `PemKey` `(string)` - An RSA private key, in pem format. It is used to
+      sign the JWT. Mutually exclusive with `PemKeyFile`.
+
+      - `PemKeyFile` `(string)` - An absolute path to a private key on Nomad
+      servers' disk, in pem format. It is used to sign the JWT.
+      Mutually exclusive with `PemKey`.
+
+      - `KeyIDHeader` `(string)` - Which header the provider uses to find
+      the public key to verify the signed JWT.
+      The default and allowed values depend on whether you set `KeyID`,
+      `PemCert`, or `PemCertFile`. You must set exactly one of those options,
+      so refer to them for their requirements.
+
+      - `KeyID` `(string)` - Becomes the JWT's "kid" header.
+      Mutually exclusive with `PemCert` and `PemCertFile`.
+      Allowed `KeyIDHeader` values: "kid" (the default)
+
+      - `PemCert` `(string)` - An x509 certificate, signed by the private key
+      or a CA, in pem format. Nomad uses this certificate to derive an
+      [x5t#S256][] (or [x5t][]) KeyID.
+      Mutually exclusive with `PemCertFile` and `KeyID`.
+      Allowed `KeyIDHeader` values: "x5t", "x5t#S256" (default "x5t#S256")
+
+      - `PemCertFile` `(string)` - An absolute path to an x509 certificate on
+      Nomad servers' disk, signed by the private key or a CA, in pem format.
+      Nomad uses this certificate to derive an [x5t#S256][] (or [x5t][])
+      header. Mutually exclusive with `PemCert` and KeyID.
+      Allowed `KeyIDHeader` values: "x5t", "x5t#S256" (default "x5t#S256")
+
+    - `ExtraHeaders` `(map[string]string)` - Added to the JWT headers,
+    alongside "kid" and "type". Setting the "kid" header here is not allowed;
+    use `PrivateKey.KeyID`.
+
+  - `OIDCEnablePKCE` `(bool: false)` - When set to `true`, Nomad will include
+  [PKCE][] verification in the auth flow. Even with PKCE enabled in Nomad,
+  you may still need to enable it in your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not
+  make a request to the identity provider to get OIDC UserInfo. You may wish to
+  set this if your identity provider doesn't send any additional claims from the
+  UserInfo endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+  to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+  `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+  signatures. Either this, the `JWTValidationPubKeys` or the
+  `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+  login; any match is sufficient.
+
+  - `BoundIssuer` `(array<string>)` - The value against which to match the iss
+  claim in a JWT.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+  redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+  client used to talk with the OIDC discovery URL. If not set, system
+  certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+  to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+  Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+  validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+  validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+  validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+  be copied to a metadata field (value). Use this if the claim you are capturing
+  is singular (such as an attribute).
+
+  When mapped, the values in each list can be any of a number, string, or
+  boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+  copied to a metadata field (value). Use this if the claim you are capturing is
+  list-like (such as groups).
+
+  - `VerboseLogging` `(bool: false)` - When set to `true`, Nomad will log token
+  claims, information related to binding-rule and role/policy evaluations,
+  and client assertion JWTs, if applicable. Not recommended in production,
+  since sensitive information may be present.
diff --git a/content/nomad/v1.11.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.11.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.11.x/content/partials/consul-namespaces.mdx b/content/nomad/v1.11.x/content/partials/consul-namespaces.mdx
new file mode 100644
index 0000000000..10df413723
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/consul-namespaces.mdx
@@ -0,0 +1,44 @@
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for
+service registrations specified in `service` blocks and Consul KV reads in
+`template` blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations
+or KV store reads, which Consul then implicitly resolves to the `"default"`
+namespace.  This default namespace behavior can be modified by setting the
+[`namespace`][consul_agent_namespace] field in the Nomad agent Consul
+configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring
+the Consul [namespace][consul_jobspec_namespace] at the group or task level in
+the Nomad job spec as well as the [`-consul-namespace`][consul_run_namespace]
+command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations
+within a group, as well as `template` KV store access is determined from the
+following hierarchy from highest to lowest precedence:
+
+* group and task configuration: Consul
+  [namespace field][consul_jobspec_namespace] defined in the job at the task or
+  group level.
+
+* job run command option: Consul namespace defined in the
+  [`-consul-namespace`][consul_run_namespace] command line option on job
+  submission.
+
+* job run command environment various: Consul namespace defined as the
+  [`CONSUL_NAMESPACE`][consul_env_namespace] environment variable on job
+  submission.
+
+* agent configuration: Consul namespace defined in the
+  [`namespace`][consul_agent_namespace] Nomad agent Consul configuration
+  parameter.
+
+* Consul default: If no Consul namespace options are configured, Consul will
+  automatically make use of the `"default"` namespace.
+
+
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_jobspec_namespace]: /nomad/docs/job-specification/consul#namespace
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_run_namespace]: /nomad/commands/job/run#consul-namespace
+[consul_env_namespace]: /consul/commands#consul_namespace
diff --git a/content/nomad/v1.11.x/content/partials/envvars.mdx b/content/nomad/v1.11.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..c50025ad25
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/envvars.mdx
@@ -0,0 +1,77 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                              |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                          |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                                    |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                            |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                         |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                                |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                                  |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                                   |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index.          |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                              |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                             |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                            |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                               |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                                     |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                            |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                              |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                             |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                                |
+| `NOMAD_UNIX_ADDR`        | Use this value as your `NOMAD_ADDR` to use `nomad` CLI with the [task API][]'s unix socket. The value is equivalent to `"unix://${NOMAD_SECRETS_DIR}/api.sock"`
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/reference/runtime-variable-interpolation#node-variables-) which are keys in the node's metadata. |
+| `CONSUL_HTTP_TOKEN`      | The tasks' Consul token. See [Consul Integration][consul] documentation for more details.                                                                                                                                                                                                |
+| `CONSUL_TOKEN`           | The tasks' Consul token. See [Consul Integration][consul] documentation for more details. This variable is deprecated and exists only for backwards compatibility.                                                                                                                       |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                                |
+
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_INTERFACE_<label>`    | The configured network namespace interface for the given port `label` when using bridged or CNI networking.                                                                                                                                             |
+| `NOMAD_ALLOC_IP_<label>`           | The configured network namespace IP for the given port `label` when using bridged or CNI networking.                                                                                                                                                    |
+| `NOMAD_ALLOC_ADDR_<label>`         | The configured network namespace `IP:Port` pair for the given port `label` when using bridged or CNI networking.                                                                                                                                        |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[task API]: /nomad/api-docs/task-api
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/reference/runtime-environment-settings#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/secure/vault
+[consul]: /nomad/docs/networking/consul
diff --git a/content/nomad/v1.11.x/content/partials/general_options.mdx b/content/nomad/v1.11.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.11.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.11.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.11.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.11.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.11.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.11.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..c4c0d45199
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/deploy/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.11.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.11.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..cf133a47b2
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,27 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.6.2
+release](https://github.com/containernetworking/plugins/releases/tag/v1.6.2),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.6.2
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Your Linux distribution's package manager may provide the CNI reference plugins
+but we recommend installing the most recent stable version to ensure you have
+fixes for known bugs shipping in those versions.
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.11.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.11.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.11.x/content/partials/install/manual-install.mdx b/content/nomad/v1.11.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.11.x/content/partials/job-status-map.mdx b/content/nomad/v1.11.x/content/partials/job-status-map.mdx
new file mode 100644
index 0000000000..16322a24f3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/job-status-map.mdx
@@ -0,0 +1,17 @@
+Nomad uses one of these values to describe a job's status:
+
+- `dead`
+- `running`
+
+The CLI returns these rigid statuses, which are useful for scheduling and
+garbage collection. However, the Nomad UI displays additional human-readable
+statuses to help you manage jobs.
+
+The following table maps the CLI statuses to the statuses that appear in the
+Nomad UI.
+
+| CLI status       | UI status |
+| ---------------- | --------- |
+| `dead`           | `Complete`, `Failed`, `Scaled Down` |
+| `dead (stopped)` | `Stopped` |
+| `running`        | `Degraded`, `Deploying`, `Healthy`, `Recovering`, `Running`, `Scaled Down` |
diff --git a/content/nomad/v1.11.x/content/partials/jwt_claim_mapping_details.mdx b/content/nomad/v1.11.x/content/partials/jwt_claim_mapping_details.mdx
new file mode 100644
index 0000000000..84ee135609
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/jwt_claim_mapping_details.mdx
@@ -0,0 +1,80 @@
+## Trusted Identity Attributes via Claim Mappings
+
+The authentication step can return data from JWT claims as trusted
+identity attributes for use in binding rule selectors and bind name
+interpolation.
+
+The `ClaimMappings` and `ListClaimMappings` attributes control how Nomad maps claims
+to identity attributes. Both are maps of items to copy,
+with elements of the form `"<JWT claim>":"<attribute suffix>"`.
+
+Use `ClaimMappings` to map singular values and `ListClaimMappings` to map lists of values.
+
+This examples contains `ClaimMappings` and `ListClaimMappings`. The configuration
+instructs Nomad to copy the values in the JWT claims `"givenName"` and `"surname"`
+to attributes named `"value.first_name"` and `"value.last_name"` respectively.
+Additionally, Nomad should copy the list of values in the JWT
+claim `"groups"`  to an attribute named `"list.roles"`.
+
+```json
+{
+  "Name": "example-auth-method",
+  "Type": "<jwt|oidc>",
+  "Description": "Example auth method",
+  "Config": {
+    "ClaimMappings": {
+      "givenName": "first_name",
+      "surname": "last_name"
+    },
+    "ListClaimMappings": {
+      "groups": "roles"
+    }
+  }
+}
+```
+
+The following table shows the resulting attributes and
+the ways they may be used in rule bindings:
+
+| Attributes         | Supported selector operations                      | Can be interpolated |
+| ------------------ | -------------------------------------------------- | ------------------- |
+| `value.first_name` | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `value.last_name`  | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `list.groups`      | In, Not In, Is Empty, Is Not Empty                 | no                  |
+
+Refer to the [binding-rule] documentation for more examples on using selectors.
+
+### Claim Specifications and JSON Pointer
+
+Use the `ClaimMappings` and `ListClaimMappings` fields to point to data
+within the JWT. If the desired key is at the top of level of the JWT, you may
+provide the name directly. If it is nested at a lower level, you may use a JSON
+Pointer.
+
+This example shows decoded JWT claims.
+
+```json
+{
+  "division": "North America",
+  "groups": {
+    "primary": "Engineering",
+    "secondary": "Software"
+  },
+  "iss": "https://my-corp-app-name.auth0.com/",
+  "sub": "auth0|eiw7OWoh5ieSh7ieyahC3ief0uyuraphaengae9d",
+  "aud": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "iat": 1589224148,
+  "exp": 1589260148,
+  "nonce": "eKiihooH3Fah8Ieshah4leeti6ien3"
+}
+```
+
+Use the following syntax to reference data:
+
+- Top-level key: Use direct reference. For example, `"division"` refers to `"North America"`.
+- Nested key: Use JSON Pointer syntax. For example, `"/groups/primary"` refers to `"Engineering"`.
+
+You may use any valid JSON Pointer as a selector. Refer to the [JSON Pointer
+RFC](https://tools.ietf.org/html/rfc6901) for a full description of the syntax.
+
+[binding-rule]: /nomad/commands/acl/binding-rule/create#examples
diff --git a/content/nomad/v1.11.x/content/partials/node-pools.mdx b/content/nomad/v1.11.x/content/partials/node-pools.mdx
new file mode 100644
index 0000000000..a9812af045
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/node-pools.mdx
@@ -0,0 +1,373 @@
+Use node pools to group clients and segment infrastructure into logical units so
+that jobs control allocation placement. Review node pool replication in
+multi-region clusters, built-in node pools, node pool patterns, and enterprise
+features such as scheduler configuration, node pool governance, and multi-region
+jobs.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+Create a node pool using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config` block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/commands/node-pool/apply
+[cli_agent_np]: /nomad/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.11.x/content/partials/plugins/base.mdx b/content/nomad/v1.11.x/content/partials/plugins/base.mdx
new file mode 100644
index 0000000000..48314bcd08
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/plugins/base.mdx
@@ -0,0 +1,35 @@
+### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first,
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration,
+which is given to all plugins.
+
+### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.11.x/content/partials/plugins/config-dirs.mdx b/content/nomad/v1.11.x/content/partials/plugins/config-dirs.mdx
new file mode 100644
index 0000000000..02c691c6af
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/plugins/config-dirs.mdx
@@ -0,0 +1,13 @@
+You may configure the directories where you place plugin executable binaries.
+The following table lists the Agent configuration field as well as the default
+directory for each plugin type. Note that the default directories use the value
+of the configured [`data_dir`](/nomad/docs/configuration#data_dir) parameter,
+which specifies a local directory.
+
+| Type                                                     | Plugin directory configuration parameter                                                   | Default plugin directory         | Plugin configuration                                                       |
+|----------------------------------------------------------|--------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------------------------------------|
+| [Device driver](/nomad/plugins/devices)                  | [`plugin_dir`](/nomad/docs/configuration#plugin_dir)                                       | `<data_dir>/plugins`             | [`plugin` block](/nomad/docs/configuration/plugin)                         |
+| [Task driver](/nomad/plugins/drivers)                    | [`plugin_dir`](/nomad/docs/configuration#plugin_dir)                                       | `<data_dir>/plugins`             | [`plugin` block](/nomad/docs/configuration/plugin)                         |
+| [Dynamic host volume](/nomad/plugins/author/host-volume) | [`client.host_volume_plugin_dir`](/nomad/docs/configuration/client#host_volume_plugin_dir) | `<data_dir>/host_volume_plugins` | [ `plugin`  block](/nomad/docs/configuration/plugin)                       |
+| [Secret provider](/nomad/plugins/author/secret-provider) | [`client.common_plugin_dir`/secrets](/nomad/docs/configuration/client#common_plugin_dir)   | `<data_dir>/common_plugins`      | [ `plugin`  block](/nomad/docs/configuration/plugin)                       |
+| [CNI reference](https://www.cni.dev/plugins/current/)    | [`client.cni_path`](/nomad/docs/configuration/client#cni_path)                             | `/opt/cni/bin`                   | [`client.cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) |
diff --git a/content/nomad/v1.11.x/content/partials/plugins/hcl-specifications.mdx b/content/nomad/v1.11.x/content/partials/plugins/hcl-specifications.mdx
new file mode 100644
index 0000000000..cc672c20ce
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/plugins/hcl-specifications.mdx
@@ -0,0 +1,32 @@
+## HCL specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. Find the full documentation of the different HCL attribute types in the [hclspec godoc][hclspec].
+
+For a basic example, review the driver configuration for the raw_exec
+driver.
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. The
+`command` key takes a string attribute, and the `args` key takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx
new file mode 100644
index 0000000000..24338c0cda
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-agent-exit.mdx
@@ -0,0 +1,7 @@
+#### Agent exit on reloading configuration errors
+
+Errors encountered when reloading agent configuration now cause agents to exit.
+In prior versions, Nomad only logged configuration errors during reloads. This
+could lead to agents running but unable to communicate. Any other errors when
+parsing the new configuration are logged and the reload is aborted, consistent
+with the current behavior.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx
new file mode 100644
index 0000000000..ea3533dae5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10-1/breaking-raft-peer.mdx
@@ -0,0 +1,8 @@
+
+#### Remove Raft peer by address removed
+
+Nomad 1.4.0 removed support for Raft Protocol v2, and this removed the ability
+to remove Raft peers by address instead of peer ID. Nomad 1.10.1 removes the
+non-functional `-peer-address` option for the [`operator raft
+peer-remove`](/nomad/commands/operator/raft/remove-peer) command, and the
+`address` parameter for the `DELETE /v1/operator/raft/peer` API.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx
new file mode 100644
index 0000000000..a8e3851ccb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-affinity-spread.mdx
@@ -0,0 +1,8 @@
+#### Affinity and spread updates are non-destructive
+
+We fixed a scheduler bug so that updates to `affinity` and
+`spread` blocks are no longer destructive. After a job update that changes only
+these blocks, existing allocations remain running with their job version
+incremented. If you were relying on the previous behavior to redistribute
+workloads, you can force a destructive update by changing fields that require
+one, such as the `meta` block.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx
new file mode 100644
index 0000000000..166027bc65
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-consul-template.mdx
@@ -0,0 +1,6 @@
+#### Consul template implicit workload identity removal
+
+Nomad no longer creates an implicit Consul identity for workloads that don't
+register services with Consul. Tasks that require Consul tokens for template
+rendering must include a [`consul` block](/nomad/docs/job-specification/consul)
+or specify an [`identity`](/nomad/docs/job-specification/identity#identity-block).
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx
new file mode 100644
index 0000000000..e49266d5c8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-disconnect-fields-removed.mdx
@@ -0,0 +1,7 @@
+#### Nomad 1.8 deprecated `disconnect` fields removed
+
+In Nomad 1.8, we introduced the `disconnect` block to replace the
+`max_client_disconnect`, `stop_after_client_disconnect`, and
+`prevent_reschedule_on_list` fields. In Nomad 1.10, we removed these fields, and
+Nomad will ignore them if specified. Jobs should migrate to using the
+[`disconnect` block](/nomad/docs/job-specification/disconnect) prior to upgrading.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx
new file mode 100644
index 0000000000..a1ebfaa321
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-go-sdk.mdx
@@ -0,0 +1,6 @@
+#### Go SDK API change for quota limits
+
+In Nomad 1.10.0, the Go API for quotas has a breaking change. The
+`QuotaSpec.RegionLimit` field is now of type `QuotaResources` instead of
+`Resources`. The `QuotaSpec.VariablesLimit` field is deprecated in lieu of
+`QuotaSpec.RegionLimit.Storage.Variables` and will be removed in Nomad 1.12.0.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx
new file mode 100644
index 0000000000..416ad303f3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-plugin-dir.mdx
@@ -0,0 +1,6 @@
+#### Loading binaries from `plugin_dir` without configuration
+
+Plugins stored within the [`plugin_dir`](/nomad/docs/configuration#plugin_dir)
+will now only be loaded when they have a corresponding
+[`plugin`](/nomad/docs/configuration/plugin) block in the agent configuration
+file. Nomad now skips any plugin found without a corresponding configuration block.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx
new file mode 100644
index 0000000000..8b83a24b80
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-remove-remote-task-driver-support.mdx
@@ -0,0 +1,7 @@
+#### Remote task driver support removed
+
+In Nomad 1.10.0, we removed all support for remote task driver
+capabilities. Nomad no longer detaches drivers with the `RemoteTasks` capability
+when an allocation is lost. Also, Nomad does not detach remote tasks
+when a node is drained. Workloads running as remote tasks should be migrated
+prior to upgrading.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx
new file mode 100644
index 0000000000..14b35f01ee
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-sentinel-apply.mdx
@@ -0,0 +1,5 @@
+#### Sentinel apply command requires scope <EnterpriseAlert product="nomad" inline/>
+
+To prevent accidentally adding policies for volumes to the job scope, the [`nomad sentinel apply` command](/nomad/commands/sentinel/apply) now
+requires the `-scope` option.  Refer to the [GitHub pull
+request](https://github.com/hashicorp/nomad/pull/24601) for details.
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx
new file mode 100644
index 0000000000..0a6abd4a87
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/breaking-vault-consul-token.mdx
@@ -0,0 +1,25 @@
+#### Vault and Consul integration changes
+
+Nomad 1.10.0 removes the previously deprecated token-based authentication
+workflow for Vault and Consul. Nomad clients must now use a task's [workload
+identity](/nomad/docs/concepts/workload-identity) to authenticate to Vault and
+Consul and obtain a token specific to the task.
+
+This table lists removed Vault fields and the new workflow.
+
+| Field | Configuration | New Workflow |
+| ------ | ------------ | ------------ |
+| [`vault.allow_unauthenticated`](/nomad/docs/v1.9.x/configuration/vault#allow_unauthenticated) | Agent | Tasks should use a workload identity. Do not use a Vault token. |
+| [`vault.task_token_ttl`]( /nomad/docs/v1.9.x/configuration/vault#task_token_ttl) | Agent | With workload identity, tasks receive their TTL configuration from the Vault role. |
+| [`vault.token`](/nomad/docs/v1.9.x/configuration/vault#token) | Agent | Nomad agents use the workload identity when making requests to authenticated endpoints. |
+| [`vault.policies`](/nomad/docs/v1.9.x/job-specification/vault#policies) | Job specification  |  Configure and use a Vault role.  |
+
+Before upgrading to Nomad 1.10, perform the following tasks:
+
+1. Configure Vault and Consul to work with workload identity.
+1. Migrate all workloads to use workload identity.
+
+Refer to the following guides for more information:
+
+- [Migrating to using workload identity with Vault](/nomad/docs/v1.9.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault)
+- [Migrating to using workload identity with Consul](/nomad/docs/v1.9.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
diff --git a/content/nomad/v1.11.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx
new file mode 100644
index 0000000000..4f4abcff9f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/release-notes/v1-10/deprecate-variable-limits.mdx
@@ -0,0 +1,7 @@
+#### Quota specification variable_limits deprecated <EnterpriseAlert product="nomad" inline/>
+
+The quota specification's `variable_limits` field is deprecated. We replaced it
+with a new [`storage` block](/nomad/docs/other-specifications/quota#storage)
+with a `variables` field, under the `region_limit` block. Existing quotas will
+be automatically migrated during server upgrade. We will remove the
+`variables_limit` field from the quota specification in Nomad 1.12.0.
diff --git a/content/nomad/v1.11.x/content/partials/service-discovery.mdx b/content/nomad/v1.11.x/content/partials/service-discovery.mdx
new file mode 100644
index 0000000000..4832a1123a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/service-discovery.mdx
@@ -0,0 +1,140 @@
+
+This page provides information about Nomad service discovery. Compare Nomad's built-in service discovery feature to using Consul service discovery, which adds a DNS interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+
+## Introduction
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/job-declare/consul-service-mesh
diff --git a/content/nomad/v1.11.x/content/partials/storage/host-volume-explanation.mdx b/content/nomad/v1.11.x/content/partials/storage/host-volume-explanation.mdx
new file mode 100644
index 0000000000..4576907f4c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/storage/host-volume-explanation.mdx
@@ -0,0 +1,39 @@
+Host volumes mount paths from the Nomad client into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+if it is backed by a distributed networked storage such as GlusterFS, or if it is a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore,
+you can use host volumes for both local semi-persistent storage and for
+highly persistent networked storage. Host volumes may be _dynamic_ or _static_.
+
+Host volumes backed by local storage help persist data that is neither critical nor
+readily restorable. Examples include an on-disk cache that can be rebuilt, or a
+clustered application where a single node can rebuild its state from the rest of
+the cluster. When backed by networked storage such as NFS/CIFS-mounted volumes
+or distributed storage with GlusterFS or Ceph, host volumes provide a quick
+option to consume highly available and reliable storage.
+
+#### Dynamic host volumes
+
+Provision dynamic host volumes
+with the [`volume create`](/nomad/commands/volume/create) command or
+API. [ACL policies](/nomad/docs/other-specifications/acl-policy#namespace-rules)
+allow delegation of control for storage within a namespace to Nomad
+Operators. The [dynamic host volume plugin
+specification](/nomad/plugins/author/host-volume) allows you to
+develop plugins specific to your local storage environment. For example, in an
+on-prem cluster you could write a plugin to perform LVM thin-provisioning.
+
+#### Static host volumes
+
+Declare static host volumes in the Nomad agent's configuration file. You
+must restart the Nomad client to reconfigure them. These restarts make static host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/architecture/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add, update, and remove host volumes to make them
+available for consumption by Nomad Operators. Or, with networked host volumes, a
+Storage Administrator needs to provision the volumes and makes them available to
+the Nomad clients. A System Administrator then mounts them on the Nomad clients.
diff --git a/content/nomad/v1.11.x/content/partials/task-driver-intro.mdx b/content/nomad/v1.11.x/content/partials/task-driver-intro.mdx
new file mode 100644
index 0000000000..a79e1ad080
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/task-driver-intro.mdx
@@ -0,0 +1,14 @@
+## Introduction
+
+Nomad clients use task drivers to execute a task and provide resource isolation.
+Extensible task drivers provide Nomad the flexibility to support a broad
+set of workloads across all major operating systems.
+
+Task driver resource isolation provides a degree of separation for Nomad's
+client CPU, memory, and storage between tasks. Resource isolation effectiveness
+depends upon individual task driver implementations and underlying client
+operating systems. Task drivers include various security-related controls but do
+not use the Nomad client-to-task interface as a security boundary. Refer to the
+[access control guide](/nomad/docs/secure/acl) for more information on
+how to protect Nomad cluster operations.
+
diff --git a/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-approval.mdx b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-approval.mdx
new file mode 100644
index 0000000000..2654bbfd80
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-approval.mdx
@@ -0,0 +1,4 @@
+### Approval options
+
+- `-auto-approve`: Automatically answer confirmation prompts in the
+  affirmative.
diff --git a/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx
new file mode 100644
index 0000000000..f6e94cbef5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-nomad-cluster.mdx
@@ -0,0 +1,25 @@
+### Nomad cluster options
+
+- `-address=<string>`: The address of the Nomad server.	Overrides the NOMAD_ADDR
+  environment variable if set.
+- `-namespace=<string>`: The target namespace for queries and actions bound to a
+  namespace.	Overrides the NOMAD_NAMESPACE environment variable if set.
+- `-region=<string>`: The region of the Nomad servers to forward commands to.
+  Overrides the NOMAD_REGION environment variable if set.
+- `-ca-cert=<string>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the NOMAD_CACERT environment variable
+  if set.
+- `-client-cert=<string>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `--client-key`.
+  Overrides	the NOMAD_CLIENT_CERT environment variable if set.
+- `-client-key=<string>`: Path to an unencrypted PEM encoded private key
+  matching the	client certificate from `--client-cert`. Overrides the
+  NOMAD_CLIENT_KEY environment variable if set.
+- `-tls-server-name=<string>`: The server name to use as the SNI host when
+  connecting via	TLS. Overrides the NOMAD_TLS_SERVER_NAME environment variable
+  if set.
+- `-token=<string>`: The SecretID of an ACL token to use to authenticate API
+  requests with.	Overrides the NOMAD_TOKEN environment variable if set.
+- `-tls-skip-verify`: Do not verify TLS certificate. We do not recommend this.
+  Verification is also skipped if you set the NOMAD_SKIP_VERIFY environment
+  variable.
diff --git a/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-operations.mdx b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-operations.mdx
new file mode 100644
index 0000000000..0e51d2fca5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/tools/nomad-pack/options-operations.mdx
@@ -0,0 +1,24 @@
+### Operation options
+
+- `-var-file=<string>`: Specifies the path to a variable override file. You may
+  provide this multiple times on a single command for multiple files.
+- `-allow-unset-vars`: Suppress errors from unset variables without default
+  values. Equivalent of setting the NOMAD_PACK_ALLOW_UNSET_VARS	environment
+  variable to `1` or `true`.
+- `-ignore-missing-vars`: Determines whether the command should override
+  variables not present in the pack or should produce an error.
+- `-var=<key=value>`: Specifies single override variables in the form of HCL
+  syntax. You may specify multiple times per command.
+- `-name=<string>`: If set, this is the unique identifier of this deployed
+  instance of the specified pack. If not set, the pack name becomes the	unique
+  identifier. Setting a name is useful for running more than one	instance of a
+  pack	within the same cluster. Note that this name must	be globally unique
+  within a cluster. Running the run command multiple	times with the same	name
+  re-submits the same pack and applies changes if you have	made any to the
+  underlying pack. Be mindful that, whether	you have made changes or not, the
+  underlying allocations are replaced.When	managing packs, the name specified
+  here is the name that you should be	pass to Nomad Packs' `plan` and `destroy`
+  commands.
+- `-parser-v1`: Use the legacy syntax parser to parse your job. This enables
+  pack to run packs for earlier versions while you are	migrating them to the
+  new syntax
diff --git a/content/nomad/v1.11.x/content/partials/variables/get-example.mdx b/content/nomad/v1.11.x/content/partials/variables/get-example.mdx
new file mode 100644
index 0000000000..78c2e1bd04
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/get-example.mdx
@@ -0,0 +1,19 @@
+This example retrieves the variable stored at path `secret/foo`.
+
+```shell-session
+$ nomad var get secret/foo
+Namespace   = default
+Path        = secret/foo
+Create Time = 2025-11-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the `passcode` item from the variable stored at `secret/foo`.
+
+```shell-session
+$ nomad var get -item=passcode secret/foo
+my-long-passcode
+```
diff --git a/content/nomad/v1.11.x/content/partials/variables/init-example.mdx b/content/nomad/v1.11.x/content/partials/variables/init-example.mdx
new file mode 100644
index 0000000000..b40a5dcfb6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/init-example.mdx
@@ -0,0 +1,6 @@
+Generate an example variable specification in the current directory.
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.11.x/content/partials/variables/list-example.mdx b/content/nomad/v1.11.x/content/partials/variables/list-example.mdx
new file mode 100644
index 0000000000..65c3213d7a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/list-example.mdx
@@ -0,0 +1,113 @@
+List the variables in the namespace `prod`.
+
+```shell-session
+$ nomad var list -namespace prod
+Namespace  Path                     Last Updated
+prod       project/another-example  2025-09-19T11:21:56-04:00
+prod       project/example          2025-09-19T11:29:03-04:00
+```
+
+List the variables in namespace `prod` that match the prefix filter `project/ex`.
+
+```shell-session
+$ nomad var list -namespace prod project/ex
+Namespace  Path             Last Updated
+prod       project/example  2025-09-19T11:29:03-04:00
+```
+
+Use the wildcard namespace indicator (`*`) to list all the variables you have
+access to. For many shells, the `*` character is significant, so you might need
+to wrap it in double (`"`) or single (`'`) quotation marks.
+
+```shell-session
+$ nomad var list -namespace '*'
+Namespace  Path                     Last Updated
+dev        another-project/example  2022-09-19T11:29:54-04:00
+dev        project/example          2022-09-19T11:29:54-04:00
+dev        system/config            2022-09-19T11:29:54-04:00
+prod       project/another-example  2022-09-19T11:21:56-04:00
+prod       project/example          2022-09-19T11:29:03-04:00
+```
+
+List values under the key `nomad/jobs`.
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key `nomad/jobs/variable/www` in JSON format.
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query.
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page, include the next page token.
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting.
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
diff --git a/content/nomad/v1.11.x/content/partials/variables/lock-example.mdx b/content/nomad/v1.11.x/content/partials/variables/lock-example.mdx
new file mode 100644
index 0000000000..f5de5b84c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/lock-example.mdx
@@ -0,0 +1,13 @@
+Lock the variable at path `secret/foo` for a time of
+fifteen seconds. Execute `nomad job run webapp.nomad.hcl` if the lock succeeds.
+
+```shell-session
+$ nomad var lock -ttl=15s secret/foo "nomad job run webapp.nomad.hcl"
+```
+
+You may also pass in file, prefixed with the "@" symbol. This example store and
+locks the variables in the `spec.nv.json` file. Execute `nomad job run webapp.nomad.hcl` if the lock succeeds.
+
+```shell-session
+$ nomad var lock secret/foo @spec.nv.json `nomad job run webapp.nomad.hcl`
+```
diff --git a/content/nomad/v1.11.x/content/partials/variables/purge-example.mdx b/content/nomad/v1.11.x/content/partials/variables/purge-example.mdx
new file mode 100644
index 0000000000..0bfd80b4fb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/purge-example.mdx
@@ -0,0 +1,5 @@
+Purge all the variables at the `secret/foo` path.
+
+```shell-session
+$ nomad var purge secret/foo
+```
diff --git a/content/nomad/v1.11.x/content/partials/variables/put-example.mdx b/content/nomad/v1.11.x/content/partials/variables/put-example.mdx
new file mode 100644
index 0000000000..96467a4531
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/variables/put-example.mdx
@@ -0,0 +1,53 @@
+
+This example writes the Nomad variables `passcode=my-long-passcode` and
+`user=me` to the path `secret/foo`. The variables are scoped to the `prod`
+namespace.
+
+```shell-session
+$ nomad var put -namespace prod secret/foo passcode=my-long-passcode user=me
+```
+
+This example uses a Nomad variable specification file, prefixed with the "@"
+symbol.
+
+```shell-session
+$ nomad var put -namespace prod secret/foo @spec.nv.json
+```
+
+Use a hyphen (`-`) to instruct the command to read the variable value from
+standard input. The `-out` option displays the command's output.
+
+```shell-session
+$ echo "abcd1234" | nomad var put -namespace prod -out secret/foo bar=-
+Namespace   = prod
+Path        = secret/foo
+Create Time = 2025-11-19T11:21:56-04:00
+Check Index = 28
+
+Items
+bar = abcd1234
+```
+
+This example updates the `bar` value in the `secret/foo` path and outputs the
+updated variable in JSON format. You must include the `check-index` value when
+you update a Nomad variable.
+
+```shell-session
+$ nomad var put -namespace prod -out json -check-index 28 secret/foo bar=efgh5678
+```
+
+Output is similar to this snippet.
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "secret/foo",
+  "CreateIndex": 28,
+  "ModifyIndex": 39,
+  "CreateTime": 1663600883130070567,
+  "ModifyTime": 1663601343585644939,
+  "Items": {
+    "bar": "efgh5678",
+  }
+}
+```
diff --git a/content/nomad/v1.11.x/content/partials/version/tag-reason.mdx b/content/nomad/v1.11.x/content/partials/version/tag-reason.mdx
new file mode 100644
index 0000000000..aad3aba7cd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/version/tag-reason.mdx
@@ -0,0 +1,4 @@
+Applying a tag to a version prevents Nomad from garbage collecting that version.
+You can compare versions by tag name as well as version number.
+
+Tag names must be unique per job.
diff --git a/content/nomad/v1.11.x/content/partials/virt-beta-callout.mdx b/content/nomad/v1.11.x/content/partials/virt-beta-callout.mdx
new file mode 100644
index 0000000000..23c97213e3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/partials/virt-beta-callout.mdx
@@ -0,0 +1,6 @@
+<Note title="Beta Feature">
+
+The Virt task driver is under active development. Refer to the [repo
+README](https://github.com/hashicorp/nomad-driver-virt) for the latest updates. Do not use this driver in production environments.
+
+</Note>
diff --git a/content/nomad/v1.11.x/content/plugins/author/device.mdx b/content/nomad/v1.11.x/content/plugins/author/device.mdx
new file mode 100644
index 0000000000..0061b9ebb0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/author/device.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: Create a device plugin for Nomad
+description: |-
+  Learn how to create a Nomad device plugin so you can schedule workload tasks with other devices, such as GPUs. Review device plugin lifecycle and the device plugin API functions that you must implement in your device plugin.
+---
+
+# Create a device plugin
+
+This page provides conceptual information for creating a device driver plugin to extend Nomad's workload execution functionality.
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Use Nomad device driver plugins to support scheduling tasks with
+other devices, such as GPUs. Device driver plugins are responsible for
+fingerprinting these devices and working with the Nomad client to make them
+available to assigned tasks.
+
+For a real world example of a Nomad device plugin implementation, refer to the
+[Nvidia GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring a device plugin
+
+Authoring a device plugin in Nomad consists of implementing the
+[BasePlugin][base-plugin] and [DevicePlugin][deviceplugin] interfaces alongside
+a main package to launch the plugin.
+
+The [nomad-skeleton-device-plugin][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and state
+
+A device plugin is long-lived. Nomad ensures that one instance of the plugin
+is running. If the plugin crashes or otherwise terminates, Nomad launches
+another instance of it.
+
+However, unlike [task driver plugins](/nomad/plugins/author/task-driver), device
+plugins do not currently have an interface for persisting state to the Nomad
+client. Instead, the device plugin API emphasizes fingerprinting devices and
+reporting their status. After helping to provision a task with a scheduled
+device, a device plugin does not have any responsibility, or ability, to monitor
+the task.
+
+## Base plugin API
+
+@include 'plugins/base.mdx'
+
+## Device driver plugin API
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The client calls the `Fingerprint` [function][fingerprintfn] when the plugin is
+started. This function allows the plugin to provide Nomad with a list of
+discovered devices, along with their attributes, for the purpose of scheduling
+workloads using devices. The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at an
+appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device
+groups. A _device group_ is a list of detected devices that are identical for the
+purpose of scheduling, which means they have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsResponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the
+information necessary for the client to make those devices available to a task.
+Currently, the `ContainerReservation` object allows the plugin to specify
+environment variables for the task, as well as a list of host devices and files
+to be mounted into the task's filesystem. Any orchestration required to prepare
+the device for use should also be performed in this function.
+
+@include 'plugins/hcl-specifications.mdx'
+
+[base-plugin]: https://github.com/hashicorp/nomad/blob/main/plugins/base/base.go#L17
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/main/plugins/device/device.go#L28
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]:https://github.com/hashicorp/nomad/blob/main/plugins/device/device.go#L45
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L162
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L172
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/main/device/device.go#L192
+[dimensioned]: https://github.com/hashicorp/nomad/blob/main/plugins/shared/structs/stats.go#L37
diff --git a/content/nomad/v1.11.x/content/plugins/author/host-volume.mdx b/content/nomad/v1.11.x/content/plugins/author/host-volume.mdx
new file mode 100644
index 0000000000..c139622afd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/author/host-volume.mdx
@@ -0,0 +1,433 @@
+---
+layout: docs
+page_title: Create a host volume plugin
+description: |-
+  Use Nomad's dynamic host volume plugins specification to create a host volume plugin so that you can dynamically configure persistent storage on your client nodes. Review examples that create a directory and a Linux filesystem. Reference plugin arguments and environment variables.
+---
+
+# Create a host volume plugin
+
+This page describes the plugin specification for
+[dynamic host volumes][stateful-workloads], with examples, so you can write
+your own plugin to dynamically configure persistent storage on your Nomad
+client nodes.
+
+If you do not need to write your own plugin, consider Nomad's built-in
+[`mkdir` plugin][mkdir_plugin], which creates a directory on the host.
+
+If you have more complex needs, review the following examples to get a
+sense of the specification in action. A plugin can be as basic as a short shell
+script.
+
+The full [specification](#specification) follows the examples,
+and is followed by a list of [general considerations](#considerations).
+
+## Examples
+
+The specification is lean enough to be readily fulfilled in any language.
+The following examples are written in `bash`.
+
+The `custom-mkdir` plugin creates a directory, and `mkfs-ext4` creates a Linux
+filesystem. You may imagine others, such as an NFS mount or another
+storage infrastructure API.
+
+Each example includes a minimal [volume specification][], which assumes that
+you have placed the plugin in the [host volume plugin directory][plugin_dir]
+and made it executable.
+
+<Tabs>
+<Tab heading="custom-mkdir">
+
+`custom-mkdir` only creates a directory. There is a plugin built into Nomad that
+does this called "mkdir", but this serves as a minimal example.
+
+Volume specification:
+
+```hcl
+type      = "host"
+name      = "mkdir-vol"
+plugin_id = "custom-mkdir" # plugin filename
+```
+
+Plugin code:
+
+```bash
+#!/usr/bin/env bash
+
+# set -u to error by name if an env var is not set
+set -eu
+
+# echo to stderr, because Nomad expects stdout to match the spec.
+# this (and stdout) show up in Nomad agent debug logs.
+stderr() {
+  1>&2 echo "$@"
+}
+
+get_path() {
+  # since delete runs `rm -rf` (frightening), check to make sure
+  # the path is something sensible.
+  if [ -z "$DHV_VOLUMES_DIR" ]; then
+    stderr "DHV_VOLUMES_DIR must not be empty"
+    exit 1
+  fi
+  if [ -z "$DHV_VOLUME_ID" ]; then
+    stderr "DHV_VOLUME_ID must not be empty"
+    exit 1
+  fi
+  # create and delete assign this echo output to a variable
+  echo "$DHV_VOLUMES_DIR/$DHV_VOLUME_ID"
+}
+
+case "$DHV_OPERATION" in
+  "fingerprint")
+    echo '{"version": "0.0.1"}'
+    ;;
+  "create")
+    path="$(get_path)"
+    stderr "creating directory: $path"
+    # `mkdir -p` may be run repeatedly with the same result;
+    # it is idempotent.
+    mkdir -p "$path"
+    # 0 bytes because plain directories are not any particular size.
+    printf '{"path": "%s", "bytes": 0}' "$path"
+    ;;
+  "delete")
+    path="$(get_path)"
+    stderr "deleting directory: $path"
+    rm -rf "$path" # `rm -f` is also idempotent.
+    ;;
+  *)
+    echo "unknown operation: '$DHV_OPERATION'"
+    exit 1
+    ;;
+esac
+```
+
+</Tab>
+<Tab heading="mkfs-ext4">
+
+`mkfs-ext4` creates a Linux ext4 filesystem with the `mkfs.ext4` command and
+mounts it  as a loopback device. Unlike `mkdir`, `mkfs` can restrict the size
+of the volume.
+
+Volume specification:
+
+```hcl
+type         = "host"
+name         = "mkfs-vol"
+plugin_id    = "mkfs-ext4" # plugin filename
+capacity_min = "50MB" # capacity values are required by this plugin
+capacity_max = "50MB"
+```
+
+Plugin code:
+
+```bash
+#!/usr/bin/env bash
+set -euo pipefail
+
+version='0.0.1'
+
+stderr() {
+  1>&2 echo "$@"
+}
+
+get_path() {
+  if [ -z "$DHV_VOLUMES_DIR" ]; then
+    stderr "DHV_VOLUMES_DIR must not be empty"
+    exit 1
+  fi
+  if [ -z "$DHV_VOLUME_ID" ]; then
+    stderr "DHV_VOLUME_ID must not be empty"
+    exit 1
+  fi
+  echo "$DHV_VOLUMES_DIR/$DHV_VOLUME_ID"
+}
+
+is_mounted() {
+  mount | grep -q " $1 "
+}
+
+create_volume() {
+    local path="$1"
+    local bytes="$2"
+
+    # translate to mb for dd block size
+    local megs=$((bytes / 1024 / 1024)) # lazy, approximate
+    if [ $megs -le 0 ]; then
+      stderr "minimum capacity must be greater than zero."
+      exit 2
+    fi
+
+    mkdir -p "$path"
+    # the if statements ensure idempotency
+    if [ ! -f "$path.ext4" ]; then
+      # dd only writes to stderr, so safe to run without redirection
+      dd if=/dev/zero of="$path.ext4" bs=1M count="$megs"
+      # mkfs includes stdout, so we need to redirect that to stderr
+      mkfs.ext4 "$path.ext4" 1>&2
+    fi
+    if ! is_mounted "$path"; then
+      mount "$path.ext4" "$path"
+    fi
+}
+
+delete_volume() {
+  local path="$1"
+  is_mounted "$path" && umount "$path"
+  rm -rf "$path"
+  rm -f "$path.ext4"
+}
+
+case "$1" in
+  "fingerprint")
+    printf '{"version": "%s"}' "$version"
+    ;;
+  "create")
+    path="$(get_path)"
+    stderr "creating volume at $path"
+    create_volume "$path" "$DHV_CAPACITY_MIN_BYTES"
+    # output what Nomad expects
+    bytes="$(stat --format='%s' "$path.ext4")"
+    printf '{"path": "%s", "bytes": %s}' "$path" "$bytes"
+    ;;
+  "delete")
+    path="$(get_path)"
+    stderr "deleting volume at $path"
+    delete_volume "$path" ;;
+  *)
+    echo "unknown operation: $1"
+    exit 1 ;;
+esac
+```
+
+</Tab>
+</Tabs>
+
+## Specification
+
+A host volume plugin is registered with Nomad if it:
+
+- Is an executable file, such as a script or binary
+- Is located in the [`client.host_volume_plugin_dir`][plugin_dir] directory
+  on Nomad client nodes
+- Responds appropriately to a `fingerprint` call
+
+### Operations
+
+To fully manage the lifecycle of a volume, plugins must fulfill all of the
+following operations:
+
+- [fingerprint](#fingerprint)
+- [create](#create)
+- [delete](#delete)
+
+Nomad passes the operation as the first positional argument to the plugin.
+That and other information are passed as environment variables. Environment
+variables are prefixed with `"DHV_"`, which stands for "Dynamic Host Volume."
+
+Some variables may be required for certain plugins, such as `DHV_CAPACITY_*`
+for plugins that can restrict size. Most variables are for plugin author convenience.
+
+#### fingerprint
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `fingerprint` to discover valid plugins when the client agent 
+starts or is reloaded with a SIGHUP. The version it returns is used to register
+the plugin on the Nomad node for volume scheduling.
+
+**CLI arguments:** `$1=fingerprint`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=fingerprint
+```
+
+**Expected stdout:**
+
+```
+{"version": "0.0.1"}
+```
+
+**Requirements:**
+
+- Must complete within 5 seconds, or Nomad will kill it. It should be much
+  faster, as no actual work should be done.
+- "version" value must be valid per the [hashicorp/go-version][go-version]
+  golang package.
+
+</blockquote>
+
+#### create
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `create` when you run [`nomad volume create`][cli-create] CLI or
+use the [create API][api-create]).
+
+You can run `create` again for the same volume if you include the volume
+`id` in the volume specification.
+
+When the agent starts, Nomad also calls `create` for each volume that was
+previously created on the node so that plugins can ensure the volumes are available
+after an agent restart or host reboot.
+
+**CLI Arguments:** `$1=create`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=create
+DHV_VOLUMES_DIR={directory to put the volume in}
+DHV_PLUGIN_DIR={path to directory containing plugins}
+DHV_NAMESPACE={volume namespace}
+DHV_VOLUME_NAME={name from the volume specification}
+DHV_VOLUME_ID={volume ID generated by Nomad}
+DHV_NODE_ID={Nomad node ID}
+DHV_NODE_POOL={Nomad node pool}
+DHV_CAPACITY_MIN_BYTES={capacity_min from the volume spec, expressed in bytes}
+DHV_CAPACITY_MAX_BYTES={capacity_max from the volume spec, expressed in bytes}
+DHV_PARAMETERS={stringified json of parameters from the volume spec}
+```
+
+**Expected stdout:**
+
+```
+{"path": "/path/to/created/volume", "bytes": 50000000}
+```
+
+**Expected stdout on error:**
+
+```
+{"error": "error message"}
+```
+
+Returning an error message is optional. Nomad returns the error message in any
+error returned to the user.
+
+**Requirements:**
+
+- Must complete within 60 seconds, or Nomad will kill it.
+- Must create a path on disk, within `DHV_VOLUMES_DIR` or otherwise, and return
+  it as `"path"`. Nomad will mount this path into workloads that request the
+  volume, and it will also be sent to `delete` later as `DHV_CREATED_PATH`.
+- Must be idempotent - running create with the same inputs should produce the
+  same result.
+- Must be safe to run concurrently, per volume name per node.
+- If the plugin fails partway through create, it must clean up after itself
+  and exit non-0. Nomad will not attempt to delete partial creates.
+- However, if during an _initial_ create, Nomad fails to save the volume in its
+  own state, it will issue `delete` automatically to avoid leaving any
+  stray volumes on disk.
+
+</blockquote>
+
+#### delete
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `delete` when you run [`nomad volume delete`][cli-delete] CLI or
+use the [delete API][api-delete].
+
+**CLI Arguments:** `$1=delete`
+
+**Environment variables:**
+
+```
+DHV_OPERATION=delete
+DHV_CREATED_PATH={path that `create` returned}
+DHV_VOLUMES_DIR={directory that volumes should be put in}
+DHV_PLUGIN_DIR={path to directory containing plugins}
+DHV_NAMESPACE={volume namespace}
+DHV_VOLUME_NAME={name from the volume specification}
+DHV_VOLUME_ID={volume ID generated by Nomad}
+DHV_NODE_ID={Nomad node ID}
+DHV_NODE_POOL={Nomad node pool}
+DHV_PARAMETERS={stringified json of parameters from the volume spec}
+```
+
+**Expected stdout:** none (stdout is discarded)
+
+**Expected stdout on error:**
+
+```
+{"error": "error message"}
+```
+
+Returning an error message is optional. Nomad returns the error message in any
+error returned to the user.
+
+**Requirements:**
+
+- Must complete within 60 seconds, or Nomad will kill it.
+- Must remove the `DHV_CREATED_PATH` that was returned by `create`,
+  or derive the path from other variables the same way that `create` did.
+- Must be idempotent - calling delete on an already deleted volume must not
+  return an error.
+- Must be safe to run concurrently, per volume name per node.
+- Will be run after a failed `create` operation during initial volume creation.
+
+</blockquote>
+
+## Considerations
+
+Plugin authors should consider these details when writing plugins.
+
+### Execution
+
+- The plugin is executed as the same user as the `nomad` agent (likely root).
+- Plugin `stdout` and `stderr` are exposed as client agent debug logs,
+  so plugins should not output sensitive information.
+- Nomad does not retry automatically on error. The caller of create/delete
+  must retry manually. The plugin may do so internally with its own retry
+  logic, provided it still completes within the deadline.
+- Errors from `create` while restoring a volume during Nomad agent start
+  do not halt the client. The error will be in client logs, and the volume
+  is not registered as available on the node.
+- Be aware that the `DHV_VOLUME_NAME` and `DHV_PARAMETERS` fields are controlled
+  by the volume author. If the expected volume authors are not the Nomad
+  administrators, you should ensure your plugin handles these fields safely or
+  ignores them.
+
+### Uniqueness
+
+- Volume `name` is unique per _node_, and volume `ID` is unique per _region_.
+- Only one create/delete operation at a time is executed per volume `name`
+  per node, and similarly by `id` on Nomad servers, but many create/delete
+  operations for different volume IDs may run concurrently, even on the same
+  node.
+- We suggest placing volumes in `DHV_VOLUMES_DIR` for consistency, but it is not
+  required. The built-in `mkdir` plugin uses `$DHV_VOLUMES_DIR/$DHV_VOLUME_ID`
+  to ensure uniqueness across the cluster. We recommend against using
+  `DHV_VOLUME_NAME` in the path unless the plugin guards against path
+  traversal.
+- Plugins that write into network storage need to take care not to delete
+  remote/shared state by `name`, unless they know that there are no other
+  volumes with workloads using that name.
+
+### Configuration
+
+- Per-_volume_ configuration should be set in the volume specification file's
+  `parameters`. Per-_node_ configuration should be put in config file(s) as
+  described next.
+- There is no mechanism built into Nomad for plugin configuration. As a
+  convention, we suggest placing any necessary configuration file(s) next to
+  the executable plugin in the plugin directory. You may use `DHV_PLUGIN_DIR`
+  to refer to the directory.
+- If a plugin needs to retain state across operations (e.g. delete needs
+  some value that was generated during create), then you may store that on
+  the host filesystem, or some external data store of your choosing, perhaps
+  even Nomad variables.
+
+[stateful-workloads]: /nomad/docs/architecture/storage/host-volumes
+[plugin_dir]: /nomad/docs/configuration/client#host_volume_plugin_dir
+[volume specification]: /nomad/docs/other-specifications/volume/host
+[go-version]: https://pkg.go.dev/github.com/hashicorp/go-version#pkg-constants
+[cli-create]: /nomad/commands/volume/create
+[api-create]: /nomad/api-docs/volumes#create-dynamic-host-volume
+[cli-delete]: /nomad/commands/volume/delete
+[api-delete]: /nomad/api-docs/volumes#delete-dynamic-host-volume
+[mkdir_plugin]: /nomad/docs/other-specifications/volume/host#mkdir-plugin
+[host_volumes_dir]: /nomad/docs/configuration/client#host_volumes_dir
diff --git a/content/nomad/v1.11.x/content/plugins/author/index.mdx b/content/nomad/v1.11.x/content/plugins/author/index.mdx
new file mode 100644
index 0000000000..7e4d64661d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/author/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: Nomad plugin authoring guide
+description: |-
+  Expand Nomad functionality by authoring your own plugins.
+---
+
+# Nomad plugin authoring guide
+
+Nomad implements a plugin framework that lets you extend the functionality of
+some components within Nomad. The design of the plugin system is inspired by the
+lessons learned from plugin systems implemented in other HashiCorp products such
+as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Device](/nomad/plugins/author/device): Extend workload functionality with a
+  custom hardware device.
+- [Host volume](/nomad/plugins/author/host-volume): Extend workload storage
+  functionality with a plugin specific to your local storage environment.
+- [Secret provider](/nomad/plugins/author/secret-provider): Extend task
+  execution functionality with a custom secret provider.
+- [Task driver](/nomad/plugins/author/task-driver): Extend task execution
+  functionality with a custom task driver.
+
+## Architecture
+
+### Go-plugin
+
+The Nomad task driver and device plugin framework uses the [go-plugin][goplugin]
+project to expose a language-independent plugin interface. Plugins implement a
+set of gRPC services and methods that Nomad manages by running the plugin and
+calling the implemented RPCs. As a result, plugins are free to be implemented
+in the author's language of choice. To facilitate plugin development, a set of
+Go interfaces and structs exist for each plugin type that abstracts away
+go-plugin and the gRPC interface. The guides in this documentation reference
+these abstractions for ease of use.
+
+### Common plugin interface
+
+The Nomad secret provider formalized a pattern first introduced with dynamic
+host volume plugins into a common plugin interface. These plugins differ from
+Go-plugins in that they generally perform a simple task and exit, not needing to
+run for extended periods of time or needing to manage other resources similar to
+task and device drivers. Common plugins must implement a `fingerprint` command
+and implementation-specific commands.
+
+The parent directory of all common plugin implementations is managed via the
+[common_plugin_dir][common_plugin_dir], with each implementation residing in a
+specific subdirectory. Check the specific plugin's documentation for directory details.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[common_plugin_dir]: /nomad/docs/configuration/client#common_plugin_dir
+[host_volume_plugin_dir]: /nomad/docs/configuration/client#host_volume_plugin_dir
diff --git a/content/nomad/v1.11.x/content/plugins/author/secret-provider.mdx b/content/nomad/v1.11.x/content/plugins/author/secret-provider.mdx
new file mode 100644
index 0000000000..4f6c8cd972
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/author/secret-provider.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: Create a secret provider plugin
+description: |-
+  Use Nomad's secret provider plugins specification to create a secret provider plugin so that you can use secrets in your tasks from any secrets store.
+---
+
+# Create a secret provider plugin
+
+This page describes the plugin specification for
+[custom secret providers][custom-providers], with examples, so you can write
+your own plugin to utilize secrets from any secrets store.
+
+The full [specification](#specification) follows the examples,
+and is followed by a list of [general considerations](#considerations).
+
+Follow this workflow to create and use a custom secret provider:
+
+1. Develop the plugin code based on the [specification](#specification).
+1. Compile your plugin into an executable binary.
+1. Place the binary in the
+   [`client.common_plugin_dir/secrets/`][common_plugin_dir] directory on each
+   Nomad client node.
+1. Configure the `secret` block in your job specification.
+
+## Example
+
+We wrote the example in Go, but the specification is lean enough to be
+readily fulfilled in any language. The example code is not meant to be inclusive of all error handling.
+
+In this example code, the `aws` secret provider plugin fetches a secret from AWS
+Secret Manager. Refer to the external [AWS Secrets Manager User
+Guide](https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html)
+for details on AWS Secrets Manager and [how to fetch secrets in various languages](https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets.html).
+
+### Plugin code
+
+<CodeBlockConfig heading="aws.go" lineNumbers="true">
+
+```golang
+package main
+
+import (
+	"context"
+	"fmt"
+	"os"
+
+	"github.com/aws/aws-sdk-go-v2/config"
+	"github.com/aws/aws-sdk-go-v2/service/secretsmanager"
+	"github.com/aws/aws-sdk-go/aws"
+)
+
+const generalUsage = "You must run with either 'fingerprint' or 'fetch'. \nYou must pass 'fetch' to the path of the secret."
+
+func returnErr(err string) {
+	fmt.Printf(`{"error": "%s"}`, err)
+	os.Exit(1)
+}
+
+func main() {
+	if len(os.Args) < 2 {
+		returnErr("internal error not enough args")
+	}
+
+	switch os.Args[1] {
+	case "fingerprint":
+		fingerprint()
+	case "fetch":
+		// fetch should be called with the correct secret path
+		if len(os.Args) < 3 {
+			returnErr("internal error no path specified")
+		}
+		fetch(os.Args[2])
+	default:
+		returnErr("internal error incorrect function")
+	}
+}
+
+func fingerprint() {
+	fmt.Println(`{"type": "secrets", "version": "0.0.1"}`)
+}
+
+// resource: https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieving-secrets-go-sdk.html
+func fetch(secretName string) {
+	ctx := context.Background()
+
+	config, err := config.LoadDefaultConfig(ctx, config.WithRegion(os.Getenv("AWS_REGION")))
+	if err != nil {
+		returnErr("error loading default aws config")
+	}
+
+	// Create Secrets Manager client
+	svc := secretsmanager.NewFromConfig(config)
+
+	input := &secretsmanager.GetSecretValueInput{
+		SecretId:     aws.String(secretName),
+		VersionStage: aws.String("AWSCURRENT"),
+	}
+
+	result, err := svc.GetSecretValue(ctx, input)
+	if err != nil {
+		returnErr(err.Error())
+	}
+
+	// Decrypts secret using the associated KMS key.
+	var secretString string = *result.SecretString
+
+	fmt.Printf(`{"result": "%s"}`, secretString)
+}
+```
+
+</CodeBlockConfig>
+
+### Task configuration
+
+Configure your task to fetch the secret with your customer `aws` secret
+provider. Make sure the `provider` value matches the name of your plugin
+executable.
+
+In this example job specification, the task uses your custom `aws`
+secret provider to fetch an AWS secret named `my-aws-secret` from the AWS
+Secrets Manager in region `us-east-2`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      secret "my_secret" {
+        provider = "aws"
+        path     = "my-aws-secret"
+        env {
+          AWS_REGION = "us-east-2"
+        }
+      }
+    }
+  }
+}
+```
+
+## Specification
+
+Nomad registers a  secret provider plugin if the plugin meets all of the
+following criteria:
+
+- Is an executable file, such as a script or binary
+- Is located in the [`client.common_plugin_dir/secrets/`][common_plugin_dir]
+  directory on Nomad client nodes
+- Responds appropriately to a `fingerprint` call
+
+### Operations
+
+A secret provider plugin must fulfill all of the following operations:
+
+- [fingerprint](#fingerprint)
+- [fetch](#fetch)
+
+Nomad passes the operation as the first positional argument to the plugin and as
+an environment variable prefixed with `CPI_`.
+
+#### fingerprint
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `fingerprint` to discover valid plugins when the client agent
+starts or is reloaded with a SIGHUP. The version it returns is used to register
+the plugin on the Nomad node.
+
+**CLI arguments:** `$1=fingerprint`
+
+**Environment variables:**
+
+```
+CPI_OPERATION=fingerprint
+```
+
+**Expected stdout:**
+
+```
+{"type": "secrets", "version": "0.0.1"}
+```
+
+**Requirements:**
+
+- Must complete within 10 seconds, or Nomad kills it. It should be much
+  faster, as no actual work should be done.
+- "type" registers this as a secret provider plugin.
+- "version" value must be valid per the [hashicorp/go-version][go-version]
+  golang package.
+
+</blockquote>
+
+#### fetch
+
+<blockquote style={{borderLeft: "solid 1px #00ca8e"}}>
+
+Nomad calls `fetch` when a Nomad job includes a secret block with a provider
+registered as a plugin. When calling fetch, Nomad includes the secret path as
+the second CLI argument. If the `env{}` block was specified, any key/values are
+supplied as environment variables to the plugin process.
+
+**CLI Arguments:** `$1=fetch $2=path`
+
+**Environment variables:**
+
+```
+CPI_OPERATION=fetch
+```
+
+**Expected stdout:**
+
+```
+{"result": {"key1": "value1", "key2": "value2"}}
+```
+
+**Expected stdout on error:**
+
+```
+{"result": {}, "error": "error message"}
+```
+
+Returning an error message is optional. Nomad returns the error message in any
+error returned to the user.
+
+**Requirements:**
+
+- Must complete within 10 seconds, or Nomad kills it.
+- Must return secret contents as a key/value object, even if the secret
+  was not originally in key/value format.
+
+</blockquote>
+
+## Considerations
+
+### Execution
+
+- The plugin is executed as the same user as the Nomad agent (likely root).
+
+[custom-providers]: /nomad/docs/job-specification/secret#custom-providers
+[go-version]: https://pkg.go.dev/github.com/hashicorp/go-version#pkg-constants
+[common_plugin_dir]: /nomad/docs/configuration/client#common_plugin_dir
diff --git a/content/nomad/v1.11.x/content/plugins/author/task-driver.mdx b/content/nomad/v1.11.x/content/plugins/author/task-driver.mdx
new file mode 100644
index 0000000000..9b41a61fca
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/author/task-driver.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Create task driver plugin for Nomad
+description: Learn how to create a Nomad task driver plugin to extend Nomad's workload execution functionality.
+---
+
+# Create a task driver plugin
+
+This page provides conceptual information for creating a task driver plugin to
+extend Nomad's workload execution functionality.
+
+Task drivers in Nomad are the runtime components that execute workloads. For a
+real world example of a Nomad task driver plugin implementation, refer to the
+[exec2 driver][].
+
+## Authoring a task driver plugin
+
+Authoring a task driver consists of implementing the [BasePlugin][base-plugin]
+and [DriverPlugin][driverplugin] interfaces and adding a main package to launch
+the plugin.
+
+The [nomad-skeleton-driver-plugin project][skeletonproject] exists to help
+bootstrap the development of new task driver plugins. It provides most of the
+boilerplate necessary for a task driver plugin, along with detailed comments.
+
+### Lifecycle and state
+
+A task driver plugin is long-lived and its lifetime is not bound to the Nomad
+client. This means that the Nomad client can restart without restarting the
+driver. Nomad ensures that one instance of the task driver is running. If
+the task driver crashes or otherwise terminates, Nomad launches another instance
+of it.
+
+Task drivers should maintain as little state as possible. State for a task is
+stored by the Nomad client on task creation. This enables a pattern where the
+task driver can maintain an in-memory state of the running tasks, and if
+necessary the Nomad client can recover tasks into the task driver state.
+
+## Base plugin API
+
+@include 'plugins/base.mdx'
+
+## Task driver plugin API
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the task driver configuration of the task.
+For more information on `hclspec.Spec`, refer to the [HCL specifications
+section](#hcl-specifications).
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the task driver implements.
+
+```go
+type Capabilities struct {
+    // SendSignals marks the task driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the task driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the task driver supports.
+    FSIsolation fsisolation.Mode
+
+    //NetIsolationModes lists the set of isolation modes supported by the task driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the task driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the task driver supports.
+    MountConfigs MountConfigSupport
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+
+    // DynamicWorkloadUsers indicates this driver is capable (but not required)
+    // of making use of a UID/GID not backed by a user known to the operating
+    // system. The allocation of a unique, not-in-use UID/GID is managed by the
+    // Nomad client ensuring no overlap.
+    DynamicWorkloadUsers bool
+}
+```
+
+The file system isolation options are the following:
+
+- `fsisolation.Image`: The task driver isolates tasks as machine images.
+- `fsisolation.Chroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `fsisolation.Unveil`: The task driver isolates tasks with the
+  [Landlock LSM][landlock] or other [`unveil`][unveil] like system.
+- `fsisolation.None`: The task driver has no filesystem isolation.
+
+The network isolation modes are the following:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the task driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available for
+the task driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of the following states:
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the task driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] that includes all of the
+configuration needed to launch the task. Additionally, the task driver
+configuration can be decoded from the `TaskConfig` by calling
+`*TaskConfig.DecodeDriverConfig(t interface{})`, passing in a pointer to the
+task driver specific configuration struct. The `TaskConfig` includes an `ID`
+field which future operations on the task are referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] that contains the required
+information for the task driver to reattach to the running task in the case of
+plugin crashes or restarts. Some of this required state is specific to the
+task driver implementation, thus a `DriverState` field exists to allow the task
+driver to encode custom state into the struct. Helper fields exist on the
+`TaskHandle` to `GetDriverState` and `SetDriverState` removing the need for the
+task driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the task driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the task driver cleans up any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the task driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the task driver in
+the `TaskConfig`. Use the [`fifo` package][fifopackage] to support cross
+platform writing to these paths.
+
+#### Dynamic workload users
+
+Nomad is capable of dynamically allocating unused UID/GID values for use by
+task drivers when launching a task. These UID/GID values are deallocated when
+the task is destroyed. The pool of available UID/GID values can be controlled
+in client config via the [users][users] block.
+
+#### TaskHandle schema versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but it allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted, it is not expected to persist any internal state to
+disk. To support this, Nomad attempts to recover a task that was previously
+started if the task driver does not recognize the task ID. During task recovery,
+Nomad calls `RecoverTask`, passing the `TaskHandle` that was returned by the
+`StartTask` function. If no error is returned, it is expected that the task
+driver can now operate on the task by referencing the task ID. If an error
+occurs, the Nomad client marks the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that sends an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task
+immediately sends an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the task
+driver must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the task driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the task driver should send
+stats to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the task driver to publish driver specific events
+about tasks and the Nomad client associates them with the correct
+allocation.
+
+An `Eventer` utility, available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package, implements an event
+loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers that support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the task driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+@include 'plugins/hcl-specifications.mdx'
+
+[exec2 driver]: https://github.com/hashicorp/nomad-driver-exec2
+[base-plugin]: https://github.com/hashicorp/nomad/blob/main/plugins/base/base.go#L17
+[driverplugin]: https://github.com/hashicorp/nomad/blob/main/plugins/drivers/driver.go#L51
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[unveil]: https://man.openbsd.org/unveil
+[users]: /nomad/docs/configuration/client#users-block
diff --git a/content/nomad/v1.11.x/content/plugins/devices/index.mdx b/content/nomad/v1.11.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..387e683f37
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/devices/index.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: Nomad device driver plugins
+description: |-
+  Use device driver plugins to detect your Nomad client's physical hardware devices, such as graphical processing units (GPUs), field programmable gate arrays (FPGAs), tensor processing units (TPUs), and universal serial buses (USBs). You can then use those devices in your Nomad workloads. Review conceptual, installation, usage, and reference information for the NVIDIA and USB device driver plugins.
+---
+
+# Nomad device driver plugins
+
+Use device driver plugins to detect physical hardware devices, such as graph
+processing units (GPUs), a field-programmable gate arrays (FPGAs), and universal
+serial buses (USBs), on your Nomad clients. You can then use those devices in
+your Nomad workloads.
+
+By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+## Nomad device drivers
+
+We support the [NVIDIA] device driver plugin, which you must install
+separately. Refer to the [NVIDIA] documentation for instructions.
+
+## Community Device Drivers
+
+The community supports the [USB] device driver plugin.
+
+## Create device drivers
+
+Nomad's device driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[NVIDIA]: /nomad/plugins/devices/nvidia
+[USB]: /nomad/plugins/devices/usb
+[plugin_guide]: /nomad/plugins/author/device
diff --git a/content/nomad/v1.11.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.11.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..c10a83b9f3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: NVIDIA GPU device plugin
+description: The NVIDIA GPU device plugin exposes NVIDIA GPUs to Nomad so you can run workloads on GPU hardware. Install and configure the plugin on your Nomad clients. Configure job tasks to use GPUs
+---
+
+# NVIDIA GPU device plugin
+
+Name: `nomad-device-nvidia`
+
+Use the NVIDIA device plugin to expose NVIDIA graphical processing units (GPUs)
+to Nomad. The driver automatically supports [Multi-Instance GPU (MIG)][mig].
+
+The NVIDIA device plugin uses [NVML] bindings to get data regarding available
+NVIDIA devices and then exposes them via [Fingerprint RPC]. Consult [NVIDIA's
+documentation](https://docs.nvidia.com/deploy/nvml-api/nvml-api-reference.html#nvml-api-reference)
+for a list of supported cards. The plugin detects
+whether the GPU has Multi-Instance GPU enabled, and when enabled, the plugin
+fingerprints all instances as individual GPUs. You may exclude GPUs from
+fingerprinting by setting the [`ignored_gpu_ids` field](#plugin-configuration).
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit     |
+|------------------|----------|
+| memory           | MiB      |
+| power            | W (Watt) |
+| bar1             | MiB      |
+| driver_version   | string   |
+| cores_clock      | MHz      |
+| memory_clock     | MHz      |
+| pci_bandwidth    | MB/s     |
+| display_state    | string   |
+| persistence_mode | string   |
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of NVIDIA GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. Refer to [NVIDIA's
+documentation](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. 64 bit GNU/Linux with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from NVIDIA to prepare a machine to use docker containers with NVIDIA GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:12.8.1-base-ubuntu22.04 nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The NVIDIA integration only works with drivers who natively integrate with
+NVIDIA's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container) and cards that are [supported
+by NVML](https://docs.nvidia.com/deploy/nvml-api/nvml-api-reference.html#nvml-api-reference).
+
+Nomad has tested support with the [`docker` driver][docker-driver].
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download]. To
+install the plugin, download the binary or compile from source. Then place the
+binary in the [plugin directory][`plugin_dir`].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:12.8.1-base-ubuntu22.04"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[NVML]: https://github.com/NVIDIA/go-nvml
+[Fingerprint RPC]: /nomad/plugins/author/device#fingerprint-context-context-chan-fingerprintresponse-error
+[mig]: https://www.nvidia.com/en-us/technologies/multi-instance-gpu/
+[docker-driver]: /nomad/docs/job-declare/task-driver/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/job-declare/task-driver/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/job-declare/task-driver/java 'Nomad java Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.11.x/content/plugins/devices/usb.mdx b/content/nomad/v1.11.x/content/plugins/devices/usb.mdx
new file mode 100644
index 0000000000..23ffa463eb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/devices/usb.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: USB device plugin
+description: |-
+  The USB Device Plugin detects USB devices so you can use them in your Nomad workloads. Learn how to configure and install the plugin. Review the plugin's fingerprinted attributes and exposed runtime environment variables.
+---
+
+# USB device plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.11.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..f64e0eb03e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Community task driver plugins
+description: Learn about the community-supported task driver plugins that extend Nomad job features. Review installation, usage, and reference information for containerd, Firecracker, Jail, Pledge, Pot, Rookout, Singularity, system-nspawn, and Windows IIS task driver plugins.
+---
+
+# Community task driver plugins
+
+Task driver plugins authored and maintained by the Nomad community are listed on
+the [Nomad integrations page](/nomad/integrations). On that page, select
+**Community** from the **Tiers** list and **Task Drivers** from the **Types**
+list to review Community-authored task driver plugins.
+
+If you have authored a task driver plugin that you believe is useful to the
+broader Nomad community and are committed to maintaining the plugin,
+create a [Nomad GitHub issue](https://github.com/hashicorp/nomad/issues) so we can add your plugin to the Nomad Integrations page.
+
+For details on authoring a task driver plugin, refer to the [plugin
+authoring guide](/nomad/docs/concepts/plugins).
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/exec2.mdx b/content/nomad/v1.11.x/content/plugins/drivers/exec2.mdx
new file mode 100644
index 0000000000..218be4de26
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/exec2.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Exec2 task driver plugin
+description: >-
+  The Exec2 task driver executes a command for a job task and leverages Linux kernel features such as Landlock LSM, cgroups v2, and the `unshare` system utility. Learn how to configure and install the Exec2 task driver plugin. Review capabilities, client requirements, and concepts such as filesystem and resource isolation. Learn how to use the Exec2 task driver in your Nomad job. Configure command, command args, paths, memory, CPU resources, and out-of-memory (OOM) behavior.
+---
+
+# Exec2 task driver plugin
+
+Name: `exec2`
+
+The `exec2` driver is used to execute a command for a task. It offers a security
+model optimized for running 'ordinary' processes with very low startup times
+and minimal overhead in terms of CPU, disk, and memory utilization. The `exec2`
+driver leverages kernel features such as the [Landlock LSM][landlock], cgroups
+v2, and the [`unshare`][unshare] system utility.
+
+Review the source on [GitHub][github].
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-exec2/) and verify the binary using the
+available SHA-256 sums. After downloading nomad-driver-exec2 driver, unzip the package. Make sure
+that the `nomad-driver-exec2` binary is available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path, specified by the client's config file, before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-exec2
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-exec2
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example below is a short demonstration of what a task making use of the
+exec2 task driver looks like:
+
+```hcl
+job "http" {
+  group "web" {
+    task "python" {
+      driver = "exec2"
+      config {
+        command = "python3"
+        args    = ["-m", "http.server", "8080", "--directory", "${NOMAD_TASK_DIR}"]
+        unveil  = ["r:/etc/mime.types"]
+      }
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `exec2` task driver is not built into Nomad. It must be [downloaded][releases]
+onto the client host in the configured plugin directory.
+
+- Linux 5.15+
+- Cgroups v2 enabled
+- Landlock LSM enabled
+- Commands `nsenter` and `unshare`
+- Nomad client running as root
+
+## Capabilities
+
+The `exec2` task driver implements the following driver [capabilities][capabilities]
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | false             |
+| filesystem isolation | unveil            |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+## Concepts
+
+### Filesystem Isolation
+
+##### landlock
+
+The `exec2` task driver makes use of [`go-landlock`][landlock] for providing
+filesystem isolation, making the host filesystem unreachable except where
+explicitly allowed.
+
+By default a task is enabled to access its task directory and its shared alloc
+directory. The paths to these directories are accessible by reading the environment
+variables `$NOMAD_TASK_DIR` and `$NOMAD_ALLOC_DIR` respectively.
+
+A file access mode must also be specified when granting additional filesystem
+access to a path. This is done by prefix the path with `'r'`, `'w'`, `'x'`,
+and/or `'c'` indicating read, write, executable, and create permissions,
+respectively. e.g.,
+
+- <code>r:/srv/www</code> - read-only access to `/srv/www`
+- <code>rwc:/tmp</code> - read, write, and create files in `/tmp`
+- <code>rx:/opt/bin/application</code> - read and execute a specific application
+- <code>wc:/var/log</code> - write and create files in `/var/log`
+
+This style of permission control is modeled after the [`unveil`][unveil] system
+call pioneered by the OpenBSD project. In configuration parameters we refer to
+"unveil"-ing of filesystem paths as `exec2` is leveraging landlock to emulate
+the semantics of `unveil`.
+
+##### dynamic workload users
+
+While landlock prevents tasks from accessing the host filesystem, Nomad 1.8
+introduces `dynamic workload users` which enable tasks to be run as a UID/GID
+that is not assigned to any user. This provides protection from non-root users
+getting access inside the task and allocation directories created for the task.
+
+To make use of a dynamic workload user, simply leave the `user` field blank in
+the task definition of an `exec2` task.
+
+### Resource Isolation
+
+Similar to `exec` and other container runtimes, `exec2` makes use of cgroups for
+limiting the amount of CPU and RAM a task may consume.
+
+## Configuration
+
+### Plugin Configuration
+
+The default plugin configuration is shown below. System default paths are enabled,
+but nothing else. These default paths enable basic functionality like reading
+system TLS certificates, executing programs in `/bin`, `/usr/bin`, and accessing
+system shared object files. The exact set of paths is system dependent, and can
+be disabled or customized in plugin config.
+
+The default set of paths are listed below. These paths are enabled only if they
+are found to exist at the time of the task launching.
+
+##### shared objects
+
+```
+rx:/lib
+rx:/lib64
+rx:/usr/lib
+rx:/usr/libexec
+rx:/usr/local/lib
+rx:/usr/local/lib64
+r:/etc/ld.so.conf
+r:/etc/ld.so.cache
+r:/etc/ld.so.conf.d
+```
+
+##### io, common
+
+```
+rwc:/tmp
+rw:/dev/null
+r:/dev/zero
+r:/dev/fd
+rw:/dev/stdin
+rw:/dev/stdout
+r:/dev/urandom
+w:/dev/log
+r:/usr/share/locale
+r:/proc/self/cmdline
+r:/usr/share/zoneinfo
+r:/usr/share/common-licenses
+r:/proc/sys/kernel/ngroups_max
+r:/proc/sys/kernel/cap_last_cap
+r:/proc/sys/vm/overcommit_memory
+```
+
+##### dns
+
+```
+r:/etc/hosts
+r:/hostname
+r:/etc/services
+r:/etc/protocols
+r:/etc/resolv.conf
+```
+
+##### certificates
+
+```
+r:/etc/ssl/certs
+r:/etc/pki/tls/certs
+r:/etc/ssl/ca-bundle.pem
+r:/etc/pki/tls/cacert.pem
+r:/etc/pki/ca-trust-extracted/pem/tls-ca-bundle.pem
+r:/etc/ssl/cert.pem
+```
+
+Additional allowable paths can be specified at the plugin level, which applies
+to all tasks making use of the `exec2` task driver, or at the task level, which
+will apply specifically to each task.
+
+```hcl
+plugin "nomad-driver-exec2" {
+  config {
+    unveil_defaults = true
+    unveil_paths    = []
+    unveil_by_task  = false
+  }
+}
+```
+
+- `unveil_defaults` - (default: `true`) - enable or disable default system paths
+  useful for running basic commands
+- `unveil_paths` - (default: `[]`) - a list of filesystem paths with permissions
+  to grant all tasks
+  ```hcl
+  unveil_paths = ["rx:/opt/bin", "r:/srv/certs"]
+  ```
+- `unveil_by_task` - (default: `false`) - enable or disable job submitters to
+  specify additional filesystem path access within task config
+
+### Task Configuration
+
+##### config
+
+Task configuration for an exec2 task includes setting a `command`, `args` for
+the command, and additional `unveil` filesystem paths if `unveil_by_task` is
+enabled in plugin configuration.
+
+```hcl
+config {
+  command       = "/usr/bin/cat"
+  args          = ["/etc/os-release"]
+  unveil        = ["r:/etc/os-release"]
+  oom_score_adj = 500
+}
+```
+
+- `command` - (string: required) - command to run
+- `args` - (list(string): optional) - list of arguments to provide
+  to `command`
+- `unveil` - (list(string): optional) - list of additional filesystem paths to
+  provide access to the task (requires `unveil_by_task` in plugin config).
+- `oom_score_adj` - (optional) - The likelihood of the task being OOM killed,
+  must be a positive integer. Defaults to `0`.
+
+##### cpu
+
+Tasks are limited in CPU resources by setting the `cpu` or `cores` values in the
+task `resources` block.
+
+- `cpu` - (default: `100`) - limits the CPU bandwidth allowable for the task to
+  make use of in MHz, may not be used with `cores`.
+- `cores` - (int: optional) - specifies the number of CPU cores to reserve
+  specifically for the task, may not be used with `cpu`
+
+##### memory
+
+Tasks are limited in memory resources by setting `memory` and optionally the
+`memory_max` values in the task `resources` block.
+
+### Node Attributes
+
+When installed, the `exec2` plugin provides the following node attributes which
+can be used as constraints when authoring jobs.
+
+```
+driver.exec2.unveil.defaults    = true
+driver.exec2.unveil.tasks       = true
+```
+
+[capabilities]: /nomad/plugins/author/task-driver#task-driver-plugin-api
+[github]: https://github.com/hashicorp/nomad-driver-exec2
+[landlock]: https://github.com/shoenig/go-landlock
+[releases]: https://releases.hashicorp.com/nomad-driver-exec2
+[unshare]: https://www.man7.org/linux/man-pages/man1/unshare.1.html
+[unveil]: https://man.openbsd.org/unveil
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/index.mdx b/content/nomad/v1.11.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..77dbdbe7ff
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Task driver plugins
+description: Task driver plugins extend Nomad functionality to provide resource isolation when executing job tasks. Review the Exec2, Podman, and Virt task driver reference. Explore plugins developed by the Nomad user community.
+---
+
+# Task driver plugins
+
+This section provides reference information for task driver plugins.
+
+@include 'task-driver-intro.mdx'
+
+## Configuration
+
+Refer to individual task driver documentation for agent configuration and job
+specification usage.
+
+## Create task drivers
+
+Nomad's task driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][/nomad/plugins/author/task-driver] for details.
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.11.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..4c366e1b7e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,737 @@
+---
+layout: docs
+page_title: Podman task driver plugin
+description: >-
+  The Podman task driver plugin uses the Pod Manager daemonless container runtime to execute Nomad workload tasks. Learn how to configure and install the Podman task driver plugin. Review capabilities, client requirements, plugin options, and network configuration. Learn how to use the Podman task driver in your Nomad job. Configure image registry authentication, Linux capabilities, host devices, entrypoint, paths, image, labels, logging, memory, network mode, ports, volumes, working directory, and container privileges.
+---
+
+# Podman task driver plugin
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-podman/) and verify the
+binary using the available SHA-256 sums. After downloading nomad-driver-podman
+driver, unzip the package. Make sure that the `nomad-driver-podman` binary is
+available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path,
+specified by the client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install -y nomad-driver-podman
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-podman
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/plugins/author/task-driver#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `apparmor_profile` - (Optional) Name of an AppArmor profile to use instead of
+  the default profile. The special value `unconfined` disables AppArmor for this container.
+
+  ```hcl
+  config {
+    apparmor_profile = "your-profile"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting `tls_verify` to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tls_verify = false
+    }
+  }
+  ```
+
+- `auth_soft_fail` - (Optional) Ignore errors returned from auth backend so Podman can fall back to a different auth method.
+
+  ```hcl
+  config {
+    auth_soft_fail = true
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `cpu_hard_limit` (Optional) `true` or `false`. Use hard CPU limiting instead
+  of soft limiting. By default this is `false`, which means Podman uses soft
+  limiting so that containers are able to burst above their CPU limit when there
+  is idle capacity.
+
+- `cpu_cfs_period` - (Optional) Set the CPU period for the [Completely Fair
+  Scheduler (CFS)](https://docs.kernel.org/scheduler/sched-design-CFS.html),
+  which is a duration in microseconds. Refer to [`podman run
+  --cpu-period`](https://docs.podman.io/en/latest/markdown/podman-run.1.html#cpu-period-limit)
+  for details.
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container.
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specified the PID limit for
+  the container.
+
+  ```hcl
+  config {
+    pids_limit = 64
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `security_opt` - (Optional) A list of security-related options that Podman sets
+  in the container.
+
+  ```hcl
+  config {
+    security_opt = [
+      "no-new-privileges"
+    ]
+
+  }
+  ```
+
+- `selinux_opts` - (Optional) A list of process labels that the container uses.
+
+  ```hcl
+  config {
+    selinux_opts = [
+      "type:my_container.process"
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) Set the size of `/dev/shm`. Refer to [`podman run
+  --shm-size](https://docs.podman.io/en/latest/markdown/podman-run.1.html#shm-size-number-unit)
+  for more details.
+
+- `socket` - (Optional) The name of the socket as defined in the socket block in
+  the client agent's plugin configuration. Defaults to the socket named "default".
+
+  ```hcl
+  config {
+    socket = "app1"
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `userns` - (Optional) Ser the user namespace mode for the container.
+
+  ```hcl
+  config {
+    userns = "keep-id:uid=200,gid=210"
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+If you need to configure authorization to an external registry, you can write a
+file containing the details in a location such as
+`/etc/nomad.d/registry/auth.json`:
+```json
+{
+  "auths": {
+    "yourregistry": {
+      "auth": "token"
+    }
+  }
+}
+```
+
+You can then instruct Nomad and the Podman driver to use this information by
+adding the following to the `/etc/nomad.d/nomad.env` file:
+```env
+REGISTRY_AUTH_FILE=/etc/nomad.d/registry/auth.json
+```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/job-declare/task-driver/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/job-declare/task-driver/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: https://docs.podman.io/en/latest/markdown/podman-run.1.html#network-mode-net
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/virt/index.mdx b/content/nomad/v1.11.x/content/plugins/drivers/virt/index.mdx
new file mode 100644
index 0000000000..af6eefdca8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/virt/index.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: Virt task driver plugin
+description: >-
+  The Virt task driver leverages Linux capabilities and runs virtual machines using the libvirt API and hypervisors such as QEMU. Learn about Nomad client requirements, installation, capabilities, and Nomad client node attributes.
+---
+
+# Virt task driver plugin
+
+Name: `virt`
+
+The Virt task driver utilizes the [libvirt][] API to run and manage virtual
+machines using hypervisors such as [QEMU][]. The task driver supports a wide
+variety of Nomad features including [workload identity][], [task templates][],
+and [service discovery][].
+
+@include 'virt-beta-callout.mdx'
+
+## Driver Capabilities
+
+The Virt task driver implements these driver [capabilities][capabilities].
+
+| Feature              | Implementation |
+|----------------------|----------------|
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | host           |
+| volume mounting      | false          |
+
+## Nomad Client Node Attributes
+
+The Virt task driver provides these node attributes that you can use as
+constraints when authoring jobs.
+
+```
+driver.virt                              = true
+driver.virt.active                       = 0
+driver.virt.emulator.version             = 8002002
+driver.virt.inactive                     = 0bytes
+driver.virt.libvirt.version              = 10000000
+driver.virt.network.default.bridge_name  = virbr0
+driver.virt.network.default.state        = active
+```
+
+## Reference
+
+- [Install and configure the Virt task driver][install].
+- [Configure a virt task in your job specification][task-config].
+
+
+[libvirt]: https://libvirt.org/
+[QEMU]: https://www.qemu.org/
+[workload identity]: /nomad/docs/concepts/workload-identity
+[task templates]: /nomad/docs/job-specification/template
+[service discovery]: /nomad/docs/job-networking/service-discovery
+[github]: https://github.com/hashicorp/nomad-driver-virt
+[capabilities]: /nomad/plugins/author/task-driver#task-driver-plugin-api
+[install]: /nomad/plugins/drivers/virt/install
+[task-config]: /nomad/plugins/drivers/virt/task-config
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/virt/install.mdx b/content/nomad/v1.11.x/content/plugins/drivers/virt/install.mdx
new file mode 100644
index 0000000000..baa9ef1849
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/virt/install.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Install the Virt task driver plugin
+description: >-
+  Install and configure the Virt task driver plugin on your Nomad clients. Review manual instructions and those for Ubuntu, Debian, CentOS, and RHEL. Add the Virt task driver plugin to Nomad.
+---
+
+# Install the Virt task driver plugin
+
+The Virt task driver plugin for Linux operating systems is not bundled with
+Nomad. You must install the driver into each Nomad client's [configured plugin
+directory][plugin_dir].
+
+@include 'virt-beta-callout.mdx'
+
+## Prerequisites
+
+Your Nomad client must meet these requirements:
+
+- Run as root.
+- Able to run hardware-accelerated KVM virtual machines. Run the [kvm-ok][]
+  command to verify your client capabilities.
+
+The Virt driver requires the following packages:
+
+- bridge-utils
+- cloudinit
+- dnsmasq
+- iptables
+- [libvirt daemon][]
+- [QEMU][]
+
+## Install the Virt task driver plugin
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+Download a [precompiled binary][releases] and verify the binary using the
+available SHA-256 sums. Unzip the package. Make sure that the
+`nomad-driver-virt` binary is on your
+[plugin_dir] path, specified by the
+client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install -y \
+  wget \
+  gpg \
+  coreutils \
+  bridge-utils \
+  cloud-init \
+  dnsmasq \
+  iptables \
+  libvirt-daemon-system \
+  qemu-system \
+  qemu-system-x86 \
+  qemu-utils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-virt
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-virt
+```
+
+</Tab>
+</Tabs>
+
+## Add the Virt task driver plugin to Nomad
+
+This example shows the default plugin configuration.
+
+```hcl
+plugin "nomad-driver-virt" {
+  config {
+    data_dir     = "/var/lib/virt"
+    image_paths  = ["/var/lib/virt", "${ALLOC_DIR}"]
+
+    emulator {
+      uri      = "qemu:///system"
+      user     = ""
+      password = ""
+    }
+  }
+}
+```
+
+- `data_dir` - (default: `"/var/lib/virt"`) - the directory for storing VM configuration files and
+  intermediate files.
+
+- `image_paths` - (default: `["/var/lib/virt", "${ALLOC_DIR}"]`) - an allow-list of paths the driver
+  is allowed to load an image from.
+
+- `emulator` - (block)
+  - `uri` - (default: `"qemu:///system"`) - The `uri` specifies which hypervisor to connect to.
+  - `user` - (default: `""`) - the username to use for authentication.
+  - `password` - (default: `""`) - the password to use for authentication.
+
+## Next steps
+
+[Learn how to use the Virt task driver in your Nomad job specification][task-config].
+
+[releases]: https://releases.hashicorp.com/nomad-driver-virt
+[kvm-ok]: https://manpages.ubuntu.com/manpages/bionic/man1/kvm-ok.1.html
+[libvirt daemon]: https://libvirt.org/daemons.html
+[QEMU]: https://www.qemu.org/
+[task-config]: /nomad/plugins/drivers/virt/task-config
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
diff --git a/content/nomad/v1.11.x/content/plugins/drivers/virt/task-config.mdx b/content/nomad/v1.11.x/content/plugins/drivers/virt/task-config.mdx
new file mode 100644
index 0000000000..6a496798da
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/drivers/virt/task-config.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: Configure a Virt job task
+description: Learn how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+---
+
+# Configure a Virt job task
+
+This page provides reference information on how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+
+@include 'virt-beta-callout.mdx'
+
+## Parameters
+
+Task configuration for a virt task includes setting an `image` to provide the base VM image as
+well as other parameters required for bootstrapping a VM instance.
+
+- `image` - (string: required) - Path to an `.img` cloud image to base the VM disk on. The image should
+  be located in an allowed path. The cloud image needs to include cloud-init, otherwise certain
+  task features are not available. You may also downloaded via the [artifact block][].
+
+- `use_thin_copy` - (bool: `false`) - Make a thin copy of the image using QEMU, and use it as the
+  backing cloud image for the VM.
+
+- `hostname` - (string: `"nomad-<task-name>"`) - The hostname to assign to the VM. As this value is
+  used as a network host name, it must be a valid DNS label according to RFC 1123. Nomad generates the default
+  value using the Nomad task name.
+
+- `cmds` - (list(string): optional) - List of commands to execute on the VM once it is running.
+  These commands can provide you with a quick way to start a process on the newly created
+  VM. When used in conjunction with the template, this command list can be a powerful start up tool.
+
+- `default_user_password` - (string: `""`) - Initial password for the default user
+  on the newly created VM. When set, the user must update the password on first connect.
+
+- `default_user_authorized_ssh_key` - (string: `""`) - SSH public key  added to the SSH
+  configuration for the default user of the cloud image distribution.
+
+- `user_data` - (string: `""`) - Path to a cloud-init compliant user data file used as the user-data for the cloud-init configuration.
+
+- `primary_disk_size` - (int: required) - Disk space to assign to the VM. Must fit the VM's OS.
+
+Example:
+```hcl
+config {
+  image                           = "local/focal-server-cloudimg-amd64.img"
+  use_thin_copy                   = false
+  hostname                        = ""
+  cmds                            = ["python -m http.server 8000"]
+  #default_user_password          = "CHANGE-ME"
+  default_user_authorized_ssh_key = ""
+  user_data                       = ""
+  primary_disk_size               = 10000
+}
+```
+
+### os
+
+The VM architecture and machine can be different from the client host. When this is the case, you must set the
+`os` block. By default, this information matches the client host where the driver
+plugin is running.
+
+- `arch` - (string: `""`) - The VM architecture.
+
+- `machine` - (string: `""`) - The machine type.
+
+Example:
+```hcl
+config {
+  os {
+    arch    = "x86_64"
+    machine = "pc-i440fx-2.9"
+  }
+}
+```
+
+### network_interface
+
+You need to attach tasks to a libvirt network in order to access the internet and route
+from the local network. The `network_interface` block enables this as a list of network interfaces
+that the driver should attach to the VM. This feature only supports a single entry.
+
+- `bridge` - (block) - Attach the VM to a bridge network. `virbr0`, the default libvirt
+  network, is a bridge network.
+
+  - `name` - The name of the bridge interface to use. This relates to the output from commands
+  such as `virsh net-info`.
+
+  - `ports` - A list of port labels to expose on the host via mapping to the network
+  interface. These labels must exist within the job specification [network block][].
+
+Example:
+```hcl
+config {
+  network_interface {
+    bridge {
+      name  = "virbr0"
+      ports = ["ssh", "http"]
+    }
+  }
+}
+```
+
+## Example configuration
+
+The following job specification displays use of all the configuration options, as well as other
+blocks that are useful when deploying tasks via the virt driver. You need to modify parameters, such as the
+`default_user_authorized_ssh_key`, before use depending on your
+requirements and Nomad setup.
+
+```hcl
+job "virt-example" {
+
+  group "virt-group" {
+
+    network {
+      mode     = "host"
+      port "ssh" {
+        to = 22
+      }
+    }
+
+    task "virt-task" {
+
+      driver = "nomad-driver-virt"
+
+      artifact {
+        source      = "http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img"
+        destination = "local/focal-server-cloudimg-amd64.img"
+        mode        = "file"
+      }
+
+      config {
+        image                           = "local/focal-server-cloudimg-amd64.img"
+        primary_disk_size               = 26000
+        #default_user_password          = "CHANGE-ME"
+        default_user_authorized_ssh_key = "ssh-ed25519 AAAAC3NzaC1lZDI..."
+
+        network_interface {
+          bridge {
+            name  = "virbr0"
+            ports = ["ssh"]
+          }
+        }
+      }
+
+      resources {
+        cores  = 2
+        memory = 4096
+      }
+    }
+  }
+}
+
+```
+
+[artifact block]: https://developer.hashicorp.com/nomad/docs/job-specification/artifact
+[network block]: https://developer.hashicorp.com/nomad/docs/job-specification/network
diff --git a/content/nomad/v1.11.x/content/plugins/index.mdx b/content/nomad/v1.11.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..3ce3ca37e8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/plugins/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Nomad plugins
+description: Plugins extend Nomad's functionality.
+---
+
+# Nomad plugins
+
+Plugins extend Nomad's functionality. Review configuration, installation, usage,
+and reference information for device and task driver plugins that are not
+bundled with Nomad.
+
+Consult the [Plugin authoring guide](/nomad/plugins/author) for details on how
+to create your own device, task driver, and host volume plugins.
+
+## Configure plugin directories
+
+@include 'plugins/config-dirs.mdx'
diff --git a/content/nomad/v1.11.x/content/security.mdx b/content/nomad/v1.11.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.11.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..2ca63b7659
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+You can configure Nomad Autoscaler to use a [Nomad namespace][nomad_namespaces]
+using the agent's [`nomad`][autoscaler_agent_nomad] configuration block. The
+Autoscaler retrieves scaling policies and perform autoscaling only for jobs in
+that namespace. If you use the special wildcard namespace value `*`, the
+Autoscaler agent retrieves scaling policies from all namespaces. A future
+version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+When utilizing the High-Availability feature added in v0.4.0, the ACL policy
+needs to include capabilities that allow the Nomad Autoscaler to obtain and release Nomad variable
+locks. The namespace identifier should match the configured
+[`high_availability.lock_namespace`][autoscaler_ha_lock_namespace] parameter,
+and the path should match the [`high_availability.lock_path`][autoscaler_ha_lock_path]
+parameter.
+
+```hcl
+namespace "default" {
+  variables {
+    path "nomad-autoscaler/lock" {
+      capabilities = ["write"]
+    }
+  }
+}
+```
+
+<Note>
+
+If you are running Nomad Autoscaler Enterprise, add this ACL policy to ensure Nomad Autoscaler Enterprise is able to read the Nomad Enterprise license.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+</Note>
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/docs/govern/namespaces
+[nomad_acls]: /nomad/docs/secure/acl
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
+[autoscaler_ha_lock_namespace]: /nomad/tools/autoscaling/agent/high_availability#lock_namespace
+[autoscaler_ha_lock_path]: /nomad/tools/autoscaling/agent/high_availability#lock_path
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..04f9f34b0a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/high_availability.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/high_availability.mdx
new file mode 100644
index 0000000000..0d8df1ac85
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/high_availability.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: high_availability Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "high_availability" block is used to configure the Nomad Autoscaler agent
+  in high availability (HA) mode. In this mode, multiple agents participate in
+  leadership election, with only the leader conducting autoscaling calculations
+  and actions.
+---
+
+# `high_availability` Block
+
+<Placement groups={['high_availability']} />
+
+The `high_availability` block is used to configure the Nomad Autoscaler agent
+in high availability (HA) mode. In this mode, multiple agents participate in
+leadership election, with only the leader conducting autoscaling calculations
+and actions.
+
+```hcl
+high_availability {
+  enabled        = true
+  lock_namespace = "prod"
+  lock_path      = "custom/lock/path"
+  lock_ttl       = "30s"
+  lock_delay     = "15s"
+}
+```
+
+## `high_availability` Parameters
+
+- `enabled` `(bool: false)` - Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired.
+
+- `lock_namespace` `(string: "default")` - Defines the namespace of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process.
+
+- `lock_path` `(string: "nomad-autoscaler/lock")` - Defines the path of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad Autoscaler
+  agents expected to take part in the same leadership election process.
+
+- `lock_ttl` `(string: "60s")` - Defines the lease period or TTL of the lock used
+  to sync the leader when running in high availability mode. If the Nomad Autoscaler
+  agent does not renew the lock within this period, the lock is considered lost.
+
+- `lock_delay` `(string: "30s")` - Defines the period that the lock will be blocked
+  after the TTL expired without being renewed. This helps prevent split brain
+  situations.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..124dba0a93
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace. If set to `*` all namespaces are queried.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..7dfc60b409
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  the following queues:
+   - `cluster`
+   - `horizontal`
+   - `vertical_mem` <EnterpriseAlert inline/>
+   - `vertical_cpu` <EnterpriseAlert inline/>
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+- `-high-availability-enabled`: Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired. It defaults to `false`.
+
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
+- `-high-availability-lock-path`: Defines the path of the Nomad variable that
+  will be used to sync the leader when running in high availability mode. This
+  parameter needs to be the same on all Nomad Autoscaler agents expected to
+  take part in the same leadership election process. Defaults to
+  `nomad-autoscaler/lock`.
+
+- `-high-availability-lock-ttl`: Defines the lease period or TTL of the lock used
+  to sync the leader when running on high availability mode. If the Nomad
+  Autoscaler agent does not renew the lock within this period, the lock is
+  considered lost. Defaults to `60s`.
+
+- `-high-availability-lock-delay`: Defines the period that the lock will be
+  blocked after the TTL expired without being renewed. This helps prevent split
+  brain situations. Defaults to `30s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..09033669eb
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/concepts/scheduling/schedulers#system
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..d2abb89c94
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..9c00c1eba6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+    dd_api_rate_per_second = "200"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `dd_api_rate_per_second` `(string: "")` - Maximum rate limit to apply to the 
+  underlying HTTP client used to query the Datadog API.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..dc2554d004
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..9fdbbead9a
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..d934049925
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered within bounds. This value is always **inclusive**, meaning a
+  metric with the exact same value as `lower_bound` is considered within
+  bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds. This value is always **exclusive**, meaning a
+  metric with the exact same value as `upper_bound` is considered **out** of
+  bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above or
+equal to `lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..4cdbf110b4
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Note that currently Prometheus is the only APM available for dynamic application sizing.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..656fb74905
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+- `retry_attempts` `(int: "15")` - The number of attempts to make while waiting
+  for the cluster to stabilize after a scaling action. It may need to be tuned
+  up if errors such as `failed to ensure all activities completed` occur.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. It may be overridden per policy.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. If set, it overrides the plugin configuration.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_scale_in_protection]: https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..c5960ea9be
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..0d4f106125
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..714d0bb875
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `query_window_offset` - Defines a time offset from the current time to apply
+  to the query window. A short offset (for example, `1m`) can be used to avoid
+  reading unstable and incomplete data from the APM. A long offset (`168h`,
+  representing 7 days ago) can be used for predictive scaling based on past
+  data.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task `policy` options for dynamic application sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the Community Edition of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.11.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.11.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..65f7ac0e67
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,287 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.queue.horizontal</code>
+      </td>
+      <td>The number of scaling actions currently being executed for horizontal scaling</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.queue.cluster</code>
+      </td>
+      <td>The number of scaling actions currently being executed for cluster scaling</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.11.x/content/tools/index.mdx b/content/nomad/v1.11.x/content/tools/index.mdx
new file mode 100644
index 0000000000..4d35695a58
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/index.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://github.com/bitrockteam/caravan/wiki) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad MCP Server](https://github.com/kocierik/mcp-nomad) - An MCP server that exposes Nomad APIs to AI agents, enabling LLM-driven automation, job management, diagnostics, and cluster operations.
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Port Forward](https://github.com/Mongey/nomad-port-forward) - A tool for forwarding ports from a Nomad job to your local machine
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Tools](https://github.com/Kamilcuk/nomad-tools) - Set of tools and utilities to ease interacting with HashiCorp Nomad scheduling solution.
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/advanced-usage.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/advanced-usage.mdx
new file mode 100644
index 0000000000..748c05969e
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/advanced-usage.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: Nomad Pack advanced usage
+description: |-
+  Generate a variables files, render a Nomad Pack, plan a Pack deployment, and
+  manage your local Pack registry.
+---
+
+# Nomad Pack advanced usage
+
+In the [Nomad Pack overview guide][pack-intro] you learned about Nomad Pack, how to deploy applications with it, and how to discover community packs.
+
+In this guide, you will learn about more advanced usage including:
+
+- Generating a variable file
+- Rendering a Pack
+- Advanced `run` options
+- Planning with `plan`
+- Registry management
+
+## Generating a variable file
+
+You can pass in variables to a pack with a variables file.
+
+```shell-session
+$ nomad-pack run hello_world -f ./my-variables.hcl
+```
+
+The `generate var-file` command can generate variable files from a pack.
+
+```shell-session
+$ nomad-pack generate var-file hello_world -o ./my-variables.hcl
+```
+
+You can also use the path to a pack instead of a pack name.
+
+```shell-session
+$ nomad-pack generate var-file ./my-local-pack -o ./my-variables.hcl
+```
+
+## Rendering a Pack
+
+At times, you may wish to use Nomad Pack to render jobspecs, but you will not want to immediately deploy these to Nomad.
+
+This can be useful when writing a pack, debugging deployments, integrating Nomad Pack into a CI/CD environment, or if you have another mechanism for handling Nomad deploys.
+
+The `render` command takes the same `--var` and `--var-file` flags that `run` takes.
+
+The `--to-dir` flag determines the directory where the rendered templates will be written.
+
+You can pass the `--render-output-template` flag to additionally render the output template. Some output templates rely on a deployment for information. In these cases, the output template may not render with all the necessary information.
+
+```shell-session
+$ nomad-pack render hello_world --to-dir ./tmp --var greeting=hola --render-output-template
+```
+
+## Advanced `run` options
+
+To deploy the resources in a pack to Nomad, use the `run` command.
+
+```shell-session
+$ nomad-pack run hello_world
+```
+
+By passing a `--name` value into `run`, Nomad Pack deploys each resource in the
+pack with a metadata value for pack name. If no name is given, the pack name
+is used by default.
+
+This allows Nomad Pack to manage multiple deployments of the same pack.
+
+```shell-session
+$ nomad-pack run hello_world --name hola-mundo
+```
+
+It is also possible to run a local pack directly from the pack directory by passing in the directory instead of the pack name.
+This can be helpful while developing a pack.
+
+```
+nomad pack run .
+```
+
+## Planning with `plan`
+
+If you want see details on how Nomad Pack will deploy a pack but are not ready to immediately deploy the pack, run the `plan` command.
+
+This invokes Nomad in a dry-run mode using the [Nomad Plan](/nomad/api-docs/jobs#create-job-plan) API endpoint.
+
+```
+nomad-pack plan hello_world
+```
+
+Similar to `run`, `plan` takes the `--name` flag to look for packs deployments with that name. Nomad Pack uses the pack name by default.
+
+```
+nomad-pack plan hello_world --name hola-mundo
+```
+
+The `plan` command also takes the `--var` and `-f` flags like the `run` command.
+
+```
+nomad-pack plan hello_world -f ./my-variables.hcl --var greeting=hallo
+```
+
+## Registry management
+
+The [Introduction to Nomad Pack guide][pack-intro] explains the basics of adding to and listing packs in the registry. The following section provides additional details on registry management.
+
+### Initialization and directory structure
+
+The first time you run `list`, Nomad Pack will add a `nomad/packs`
+directory to your desktop user's cache directory—`$XDG_CACHE_DIR` on Linux,
+`~/Library/Caches` on macOS, `%AppData%` on Windows, etc. This folder stores
+information about cloned registries and their available packs.
+
+During initialization, Nomad Pack downloads a default registry of packs from the
+[Nomad Pack community registry][community-registry].
+
+The directory structure is as follows:
+
+```
+parent-directories (see above)
+└── nomad
+    └── packs
+        ├── <REGISTRY>
+            ├── <REGISTRY-TAG>
+                ├── <PACK-NAME@REF>
+                    ├── ...files containing pack contents...
+```
+
+Nomad Pack requires the contents of the pack cache directory to work properly, but you should not manually manage or change these files. Instead, you can use the `registry` commands.
+
+### Adding new registries
+
+The `registry` command includes several sub-commands for interacting with registries.
+
+Add custom registries with the `registry add` command. Any `git` based
+registry supported by [`go-getter`](https://github.com/hashicorp/go-getter) should
+work.
+
+For example, to add the entire [Nomad Pack Community Registry](https://github.com/hashicorp/nomad-pack-community-registry), use the `registry add` command to download the registry.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry
+```
+
+### Adding an individual pack from a registry
+
+To add a single pack from the registry, use the `--target` flag.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry --target=nginx
+```
+
+### Adding a registry at a specific commit
+
+To download a single pack or an entire registry at a specific version/SHA, use the `--ref` flag.
+
+```shell-session
+$ nomad-pack registry add community github.com/hashicorp/nomad-pack-community-registry --ref=v0.0.1
+```
+
+### Removing a registry
+
+To remove a registry or pack from your local cache, use the `registry delete` command.
+This command also supports the `--target` and `--ref` flags.
+
+```shell-session
+$ nomad-pack registry delete community
+```
+
+### Updating a registry
+
+To update a registry, use the `add` command and Nomad Pack will re-download the registry and replace the contents.
+
+```shell-session
+$ nomad-pack registry add default github.com/hashicorp/nomad-pack-community-registry
+```
+
+## Next steps
+
+In this guide you learned how to interact with Nomad Pack in an advanced way. You learned how to generate a variable file, render a pack, use additional `run` options, use the `plan` command, and interact with Nomad Pack registries.
+
+The official and community packs available to Nomad Pack are valuable because it allows you to quickly deploy apps using the best practices and leverage the knowledge of the Nomad community.
+
+To learn how to write your own Nomad Packs or convert your existing Nomad job
+specifications into reusable packs, continue on to the [Creating packs
+guide][writing-packs].
+
+[nomad-site]: /nomad/
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[pack-intro]: /nomad/tools/nomad-pack/
+[writing-packs]: /nomad/tools/nomad-pack/create-packs
+[community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/index.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/index.mdx
new file mode 100644
index 0000000000..e28b9fbf74
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack deps command reference
+description: |-
+  Use the `nomad-pack deps` command to manage dependencies for a Nomad pack.
+---
+
+# nomad-pack deps command reference
+
+Use the `nomad-pack deps` command to manage dependencies for a Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack deps <subcommand> [options]
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/vendor.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/vendor.mdx
new file mode 100644
index 0000000000..71183ed217
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/deps/vendor.mdx
@@ -0,0 +1,34 @@
+---
+layout: commands
+page_title: nomad-pack deps vendor command reference
+description: |-
+  Use the `nomad-pack deps vendor` command to download vendor dependencies for a pack.
+---
+
+# nomad-pack deps vendor command reference
+
+Use the `nomad-pack deps vendor` command to download vendor dependencies for a pack.
+
+## Usage
+
+```plaintext
+nomad-pack deps vendor [options]
+```
+
+## Options
+
+- `--path=<string>`: Full path to the pack that contains vendor dependencies.
+  All the dependencies are then downloaded into a `deps/` subdirectory of that
+  path.
+
+- `--timeout=<int> (default 30)`:  Timeout in seconds for downloading
+  dependencies. Defaults to 30.
+
+## Examples
+
+Download vendor dependencies for a pack in the current directory, with a timeout
+of 180 seconds.
+
+```shell
+nomad-pack deps vendor --timeout=180
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/destroy.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/destroy.mdx
new file mode 100644
index 0000000000..c968d36e50
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/destroy.mdx
@@ -0,0 +1,53 @@
+---
+layout: commands
+page_title: nomad-pack destroy command reference
+description: |-
+  Use the `nomad-pack destroy` command to stop and delete the specified Nomad pack from the configured Nomad cluster.
+---
+
+# nomad-pack destroy command reference
+
+Use the `nomad-pack destroy` command to stop and delete the specified Nomad pack
+from the configured Nomad cluster. This is the same as using the command
+`nomad-pack stop <pack_name> --purge`.
+
+By default, the `nomad-pack destroy` command deletes all jobs in the pack
+deployment. If you ran a pack with var overrides to specify the job name, you
+must provide the var override when destroying the pack to guarantee this command
+targets the correct job in the pack deployment.
+
+## Usage
+
+```plaintext
+nomad-pack destroy <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be
+					destroyed.
+- `-ref=<string>`: Specific Git reference of the pack to destroy.
+					Supports tags, SHA, and latest. If no ref is specified,
+					defaults to latest.	Using `ref` with a file path is not supported.
+- `-global`: Destroy multi-region pack in all its regions. By default,
+					 `destroy` only destroys a single region at a time. Ignored for single-region packs.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Stop an example pack in deployment "dev" and delete it from the cluster.
+
+```shell
+nomad-pack destroy example --name=dev
+```
+
+Stop and delete an example pack in deployment "dev" that has a job named "test".
+If you have installed the same pack in deployment "dev" but override the job
+name to "hello", this command only destroys "test".
+
+```shell
+nomad-pack destroy example --name=dev --var=job_name=test
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/index.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/index.mdx
new file mode 100644
index 0000000000..01fd297ff0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack generate command reference
+description: |-
+  Use the `nomad-pack generate` subcommands to generate a sample registry, pack, or variable overrides file for a Nomad pack.
+---
+
+# nomad-pack generate command reference
+
+Use the `nomad-pack generate` subcommands to generate a sample registry, pack, or variable overrides file for a Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate <subcommand> [options]
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/pack.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/pack.mdx
new file mode 100644
index 0000000000..cc9d11e8d9
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/pack.mdx
@@ -0,0 +1,31 @@
+---
+layout: commands
+page_title: nomad-pack generate pack command reference
+description: |-
+  Use the `nomad-pack generate pack` command to create a new Nomad pack.
+---
+
+# nomad-pack generate pack command reference
+
+Use the `nomad-pack generate pack` command to create a new Nomad pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate pack <pack_name>
+```
+
+## Options
+
+- `-to-dir=<string>`: Path to write generated pack to.
+- `-overwrite`: If the output directory is not empty, should we overwrite?
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Create a new pack named "my-new-pack" in the current directory.
+
+```shell
+nomad-pack generate pack my-new-pack
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/registry.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/registry.mdx
new file mode 100644
index 0000000000..1ac19c85ed
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/registry.mdx
@@ -0,0 +1,31 @@
+---
+layout: commands
+page_title: nomad-pack generate registry command reference
+description: |-
+  Use the `nomad-pack generate registry` command to generate a new registry.
+---
+
+# nomad-pack generate registry command reference
+
+Use the `nomad-pack generate registry` command to generate a new registry.
+
+## Usage
+
+```plaintext
+nomad-pack generate registry <name>
+```
+
+## Options
+
+- `-to-dir=<string>`: Path to write generated registry to.
+- `-with-sample-pack`: Generate a sample "hello_world" pack in the registry.
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Create a new registry named "my-new-registry" in the current directory.
+
+```shell
+nomad-pack generate registry my-new-registry
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/var-file.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/var-file.mdx
new file mode 100644
index 0000000000..600e24c950
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/generate/var-file.mdx
@@ -0,0 +1,63 @@
+---
+layout: commands
+page_title: nomad-pack generate var-file command reference
+description: |-
+  Use the `nomad-pack generate registry` command to generate a variable override file for a pack.
+---
+
+# nomad-pack generate var-file command reference
+
+Use the `nomad-pack generate registry` command to generate a variable override file for a pack.
+
+## Usage
+
+```plaintext
+nomad-pack generate var-file <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the target pack. If
+  not specified, the default registry is used.
+- `-ref=<string>`: Specific Git reference of the target pack. Supports tags,
+  SHA, and `@latest`. If you do not specify a reference, the command defaults to
+  `@latest`.	Using `ref` with a file path is not supported.
+- `-to-file=<string>`: Path to write generated variable override file to in
+  addition to	standard output.
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Generate a variables override file for the given pack to standard output.
+
+```shell
+nomad-pack generate var-file example
+```
+
+Generate a variable override for the example pack. Output to a file in
+addition to the terminal.
+
+```shell
+nomad-pack generate var-file example --to-file ./overrides.hcl
+```
+
+Generate a variable override for the `example` pack. Output to a file in
+addition to the terminal. Setting the `auto-approve` option allows the command
+to overwrite existing files.
+
+```shell
+nomad-pack generate var-file example --to-file ./overrides.hcl --auto-approve
+```
+
+Generate a variable override pack under development from the current working directory.
+
+```shell
+nomad-pack generate var-file .
+```
+
+Generate a variable override pack under development from the specified relative path.
+
+```shell
+nomad-pack generate var-file ../../my-pack
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/index.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/index.mdx
new file mode 100644
index 0000000000..7c3641b0b1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/index.mdx
@@ -0,0 +1,14 @@
+---
+layout: docs
+page_title: Nomad Pack command-line interface (CLI) reference
+description: >
+  The Nomad Pack command-line interface (CLI) interacts with the Nomad Pack product. This section contains reference information on how to use the Nomad Pack CLI to generate, register, and list packs.
+---
+
+# Nomad Pack command-line interface (CLI) reference
+
+The Nomad Pack CLI is a well-behaved command-line application. In erroneous
+cases, the CLI returns a non-zero exit status. To view a list of available
+commands, run the `nomad-pack` command with no arguments, `-h`, or `--help`. To
+access help for any specific subcommand, run the subcommand with the `-h`
+argument.
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/info.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/info.mdx
new file mode 100644
index 0000000000..9acb346011
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/info.mdx
@@ -0,0 +1,34 @@
+---
+layout: commands
+page_title: nomad-pack info command reference
+description: |-
+  Use the `nomad-pack info` command to fetch information on the given pack including name, description, and variable details.
+---
+
+# nomad-pack info command reference
+
+Use the `nomad-pack info` command to fetch information on the given pack including name, description, and variable details.
+
+## Usage
+
+```plaintext
+nomad-pack info <pack_name>
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to retrieve
+  info about. If not specified, this command targets the default registry.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info
+  about. Supports tags, SHA, and `@latest`. If you do not specify a reference,
+  the value defaults to `@latest`. Using `ref` with a file path is not supported.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+## Examples
+
+Fetch information on the "hello_world" pack.
+
+```shell
+nomad-pack info hello_world
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/list.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/list.mdx
new file mode 100644
index 0000000000..4da1f386f1
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/list.mdx
@@ -0,0 +1,33 @@
+---
+layout: commands
+page_title: nomad-pack list command reference
+description: |-
+  Use the `nomad-pack list` command to list packs available in the local environment.
+---
+
+# nomad-pack list command reference
+
+Use the `nomad-pack list` command to list packs available in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack list
+```
+
+## Options
+
+- `-registry=<string>`: Registry name to filter packs by.
+- `-ref=<string>`: Registry ref to filter packs by.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+List all available packs.
+
+```shell
+nomad-pack list
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/plan.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/plan.mdx
new file mode 100644
index 0000000000..8b748739d0
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/plan.mdx
@@ -0,0 +1,75 @@
+---
+layout: commands
+page_title: nomad-pack plan command reference
+description: |-
+  Use the `nomad-pack plan` command to perform a dry run that determines the effects of submitting a new or updated Nomad Pack.
+---
+
+# nomad-pack plan command reference
+
+Use the `nomad-pack plan` command to perform a dry run that determines the effects of submitting a new or updated Nomad Pack.
+
+The `nomad-pack plan` command returns one of the following exit codes:
+
+  - `0`:   No objects will be created or destroyed.
+  - `1`:   Objects will be created or destroyed.
+  - `255`: An error occurred determining the plan.
+
+## Usage
+
+```plaintext
+nomad-pack plan <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-diff`: Determines whether to output the diff between the remote job and
+  planned job. Defaults to true.
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+- `-verbose`: Increase diff verbosity.
+- `-exit-code-no-changes=<int>`: Override exit code returned when the plan shown
+  no changes.
+- `-exit-code-makes-changes=<int>`: Override exit code returned when the plan
+  shows changes.
+- `-exit-code-error=<int>`: Override exit code returned when there is an error.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Plan an example pack with the default deployment name.
+
+```shell
+nomad-pack plan example
+```
+
+Plan an example pack at a specific ref.
+
+```shell
+nomad-pack plan example --ref=v0.0.1
+```
+
+Plan a pack from a registry other than the default registry.
+
+```shell
+nomad-pack plan traefik --registry=community --ref=v0.0.1
+```
+
+Plan an example pack without showing the diff.
+
+```shell
+nomad-pack plan example --diff=false
+```
+
+Plan a pack under development from the current filesystem.
+
+```shell
+nomad-pack plan .
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/add.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/add.mdx
new file mode 100644
index 0000000000..a460fa7729
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/add.mdx
@@ -0,0 +1,51 @@
+---
+layout: commands
+page_title: nomad-pack registry add command reference
+description: |-
+  Use the `nomad-pack registry add` command to add registries or packs to the local environment.
+---
+
+# nomad-pack registry add command reference
+
+Use the `nomad-pack registry add` command to add registries or packs to the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry add <name> <source> [options]
+```
+
+## Options
+
+- `-target=<string>`: A specific pack within the registry.
+- `-ref=<string>`: Specific Git reference of the registry or pack. Supports
+tags, SHA, and `latest`. If you do not specify a reference, the command defaults
+to `@latest`. Running `nomad registry add` multiple times for the same ref is
+idempotent. However, running`nomad-pack registry add` without specifying a
+reference or when specifying `@latest` is destructive and overwrites current
+`@latest` in the global cache. Using `ref` with a file path is not supported.
+
+## Examples
+
+Download latest reference of the Nomad Pack registry to the global cache.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry
+```
+
+Download latest reference of a specific pack from the registry to the global cache.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry \
+           --target=nomad_example
+```
+
+Download packs from a registry at a specific tag, release, or SHA.
+
+```shell
+nomad-pack registry add community \
+           github.com/hashicorp/nomad-pack-community-registry \
+           --ref=v0.1.0
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/delete.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/delete.mdx
new file mode 100644
index 0000000000..f5458f1f6f
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: commands
+page_title: nomad-pack registry delete command reference
+description: |-
+  Use the `nomad-pack registry delete` command to delete registries or packs from the local environment.
+---
+
+# nomad-pack registry delete command reference
+
+Use the `nomad-pack registry delete` command to delete registries or packs from the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry delete <name> [options]
+```
+
+## Options
+
+- `-target=<string>`: A specific pack within the registry. If you add a
+  reference flag, the command only deletes that reference of the target pack.
+- `-ref=<string>`: Specific Git reference of the registry or pack. Supports
+  tags, SHA, and `@latest`. If you do not specify a reference, the command defaults to `@latest`. Using `ref` with a file path is not supported.
+
+<Warning>
+
+If you do not specify `target` or `ref`, this command deletes the entire
+specified registry.
+
+</Warning>
+
+## Examples
+
+Delete the Traefik pack with tag `v0.0.1` from your local `community` registry.
+
+```shell
+nomad-pack registry delete community --target=traefik --ref=v0.0.1
+```
+
+Delete the `community` registry from the local environment.
+
+```shell
+nomad-pack registry delete community
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/index.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/index.mdx
new file mode 100644
index 0000000000..1ddc10e238
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/index.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack registry command reference
+description: |-
+  Use the ` nomad-pack registry` subcommands to add, delete, or list registries and packs in the local environment.
+---
+
+# nomad-pack registry command reference
+
+Use the `nomad-pack registry` subcommands to add, delete, or list registries and packs in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry <subcommand> [options]
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/list.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/list.mdx
new file mode 100644
index 0000000000..416566f7bf
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/registry/list.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack registry list command reference
+description: |-
+  Use the `nomad-pack registry list` command to list registries configured in the local environment.
+---
+
+# nomad-pack registry list command reference
+
+Use the `nomad-pack registry list` command to list registries configured in the local environment.
+
+## Usage
+
+```plaintext
+nomad-pack registry list
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/render.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/render.mdx
new file mode 100644
index 0000000000..3333892df6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/render.mdx
@@ -0,0 +1,71 @@
+---
+layout: commands
+page_title: nomad-pack render command reference
+description: |-
+  Use the `nomad-pack render` command to render the specified Nomad Pack and review the results.
+---
+
+# nomad-pack render command reference
+
+Use the `nomad-pack render` command to render the specified Nomad Pack and review the results.
+
+## Usage
+
+```plaintext
+nomad-pack render <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack. If not
+  specified, the default registry is used.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-render-output-template`: Controls whether or not to render and display the
+  output template file within the pack.
+- `-skip-aux-files`: Controls whether or not the rendered output contains
+  auxiliary	files found in the `templates` folder.
+- `-no-format`: Controls whether or not to format templates before outputting.
+- `-to-dir=<string>`: Path to write rendered job files to in addition to
+  standard output.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-approval.mdx'
+
+## Examples
+
+Render an example pack with override variables in a variable file.
+
+```shell
+nomad-pack render example --var-file="./overrides.hcl"
+```
+
+Render an example pack with CLI variable overrides.
+
+```shell
+nomad-pack render example --var="redis_image_version=latest" \
+           --var="redis_resources={"cpu": "1000", "memory": "512"}"
+```
+
+Render an example pack including the outputs template file.
+
+```shell
+nomad-pack render example --render-output-template
+```
+
+Render an example pack, outputting the rendered templates to file in
+addition to the terminal. Setting `auto-approve` allows the command to
+overwrite existing files.
+
+```shell
+nomad-pack render example --to-dir ~/out --auto-approve
+```
+
+Render a pack under development from the filesystem. Supports current
+working directory or relative path.
+
+```shell
+nomad-pack render .
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/run.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/run.mdx
new file mode 100644
index 0000000000..b9bfcb33d3
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/run.mdx
@@ -0,0 +1,85 @@
+---
+layout: commands
+page_title: nomad-pack run command reference
+description: |-
+  Use the `nomad-pack run` command to install the specified Nomad Pack to a configured Nomad cluster.
+---
+
+# nomad-pack run command reference
+
+Use the `nomad-pack run` command to install the specified Nomad Pack to a configured Nomad cluster.
+
+## Usage
+
+```plaintext
+nomad-pack run <pack_name> [options]
+```
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be run.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-check-index=<uint>`: If set, the job is only registered or updated if the
+  passed job modify index matches the server side version. If you pass a value
+  of zero, the job is only registered if it does not yet exist.  Passing a
+  non-zero value ensures that the job is being updated from a known state. The
+  use of this flag is most common in conjunction with `nomad job plan` command.
+- `-consul-token=<string>`: If set, the passed Consul token is stored in the job
+  before	sending to the Nomad servers. This allows passing the Consul token
+  without storing it in the job file. This overrides the token found in the
+  $CONSUL_HTTP_TOKEN environment variable	and that found in the job.
+- `-consul-namespace=<string>`: If set, any services in the job are registered
+  into the	specified Consul namespace. Any template block reading from Consul
+  KV are scoped to the the specified Consul	namespace. If Consul ACLs are
+  enabled and the	`allow_unauthenticated` Nomad server Consul configuration is
+  not enabled, then you must supply a Consul token with appropriate service and
+  KV Consul ACL policy permissions.
+- `-vault-token=<string>`: If set, the passed Vault token is stored in the job
+  before	sending to the Nomad servers. This allows passing the Vault token
+  without storing it in the job file. This overrides the token found in the
+  $VAULT_TOKEN environment variable and that found in the job.
+- `-vault-namespace=<string>`: If set, the passed Vault namespace is stored in
+  the job before sending to the Nomad servers.
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+- `-preserve-counts`: If set, the existing task group count is preserved when
+  updating a job.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Run an example pack with the default deployment name "example".
+
+```shell
+nomad-pack run example
+```
+
+Run an example pack with the specified deployment name "dev".
+
+```shell
+nomad-pack run example --name=dev
+```
+
+Run an example pack with override variables in a variable file.
+
+```shell
+nomad-pack run example --var-file="./overrides.hcl"
+```
+
+Run an example pack with CLI variable overrides.
+
+```shell
+nomad-pack run example --var="redis_image_version=latest" \
+           --var="redis_resources={"cpu": "1000", "memory": "512"}"
+```
+
+Run a pack under development from the current filesystem.
+
+```shell
+nomad-pack run .
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/status.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/status.mdx
new file mode 100644
index 0000000000..4a2df0a1c5
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/status.mdx
@@ -0,0 +1,62 @@
+---
+layout: commands
+page_title: nomad-pack status command reference
+description: |-
+  Use the `nomad-pack status` command to fetch information on deployed Nomad packs.
+---
+
+# nomad-pack status command reference
+
+Use the `nomad-pack status` command to fetch information on deployed Nomad packs.
+
+## Usage
+
+```plaintext
+nomad-pack status <pack_name> [options]
+```
+
+If you do not specify a pack name, the `nomad-pack status` command returns	a
+list of all deployed packs. If you do specify a pack name, this command returns
+a list of all deployed jobs belonging to that pack, along with their status and
+deployment names.
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to inspect.If
+  not specified, the command uses the default registry.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+# Examples
+
+Get a list of all deployed packs and their registries.
+
+```shell
+nomad-pack status
+```
+
+Get a list of all deployed jobs in pack example, along with their status
+and deployment names.
+
+```shell
+nomad-pack status example
+```
+
+Get a list of all deployed jobs and their status for an example pack in
+the deployment name "dev".
+
+```shell
+nomad-pack status example --name=dev
+```
+
+Get a list of all deployed jobs and their status for an example pack in
+the deployment name "dev".
+
+```shell
+nomad-pack status example --name=dev --registry=community
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/stop.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/stop.mdx
new file mode 100644
index 0000000000..5dbf99c55c
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/stop.mdx
@@ -0,0 +1,63 @@
+---
+layout: commands
+page_title: nomad-pack stop command reference
+description: |-
+  Use the `nomad-pack stop` command to stop the specified Nomad Pack in the configured Nomad cluster.
+---
+
+# nomad-pack stop command reference
+
+Use the `nomad-pack stop` command to stop the specified Nomad Pack in the configured Nomad cluster.
+
+By default, the `stop` command stops all jobs in the pack deployment. If you ran
+a pack with variable overrides to specify the job name, you must provide the
+same variable overrides when stopping the pack to guarantee that this command
+targets the correct job in the pack deployment.
+
+## Usage
+
+```plaintext
+nomad-pack stop <pack_name> [options]
+```
+
+To delete the pack from the cluster, specify `--purge`, or use the [`nomad-pack
+destroy` command](/nomad/tools/nomad-pack/commands/destroy).
+
+## Options
+
+- `-registry=<string>`: Specific registry name containing the pack to be
+  stopped.
+- `-ref=<string>`: Specific Git reference of the pack to retrieve info about.
+  Supports tags, SHA, and `@latest`. If you do not specify a reference, the
+  value defaults to `@latest`. Using `ref` with a file path is not supported.
+- `-purge`: Purge is used to stop a pack and purge it from the system.	If not
+  set, you can still query the pack until the garbage collector purges the pack.
+- `-global`: Stop a multi-region pack in all its regions. By default, `pack
+  stop` only stops a single region at a time. Ignored for	single-region jobs.
+
+@include 'tools/nomad-pack/options-operations.mdx'
+
+@include 'tools/nomad-pack/options-nomad-cluster.mdx'
+
+## Examples
+
+Stop an example pack in deployment "dev".
+
+```shell
+nomad-pack stop example --name=dev
+```
+
+Stop the `example` pack in deployment "dev" and purge it from the system.
+
+```shell
+nomad-pack stop example --name=dev --purge
+```
+
+Stop an example pack in deployment "dev" that has a job named "test"
+If the same pack has been installed in deployment "dev" but overriding the
+job name to "hello", only "test" is stopped.
+
+```shell
+nomad-pack stop example --name=dev --var=job_name=test
+```
+
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/commands/version.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/version.mdx
new file mode 100644
index 0000000000..a525d97b2b
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/commands/version.mdx
@@ -0,0 +1,16 @@
+---
+layout: commands
+page_title: nomad-pack version command reference
+description: |-
+  Use `nomad-pack version` to return the Nomad Pack version.
+---
+
+# nomad-pack stop command reference
+
+Use `nomad-pack version` to return the Nomad Pack version.
+
+## Usage
+
+```plaintext
+nomad-pack version
+```
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/create-packs.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/create-packs.mdx
new file mode 100644
index 0000000000..37d588e144
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/create-packs.mdx
@@ -0,0 +1,456 @@
+---
+layout: docs
+page_title: Create custom packs
+description: |-
+  Create a custom Nomad Pack registry, add a pack, create a template, publish the registry, and deploy a custom pack from your custom registry.
+---
+
+# Create custom packs
+
+This guide will walk you through the steps involved in writing your own packs and registries for [Nomad Pack][pack-repo].
+
+In this guide, you will learn:
+
+- how packs and pack registries are structured
+- how to write a custom pack
+- how to test your pack locally
+- how to deploy a custom pack
+
+## Create a custom registry
+
+First, you need to create a pack registry. This will be a repository that provides the structure, templates,
+and metadata that define your custom packs.
+
+To get started, use the `generate` command to create a new registry. Then, move into the directory of the registry.
+
+```shell-session
+$ nomad-pack generate registry my_nomad_packs
+$ cd my_nomad_packs/
+```
+
+Each registry should have a `README.md` file that describes the packs in it, and top-level directories
+for each pack. Conventionally, the directory name matches the pack name.
+
+The top level of a pack registry looks like the following:
+
+```plaintext
+.
+└── README.md
+└── CHANGELOG.md
+└── packs
+    └── <PACK-NAME-A>
+        └── ...pack contents...
+    └── <PACK-NAME-B>
+        └── ...pack contents...
+    └── ...packs...
+```
+
+## Add a new pack
+
+To add a new pack to your registry, create a new directory in the `packs` subdirectory.
+
+```shell-session
+$ mkdir -p packs/hello_pack && cd packs/hello_pack/
+```
+
+The directory should have the following contents:
+
+- A `README.md` file containing a human-readable description of the pack, often including any dependency information.
+- A `metadata.hcl` file containing information about the pack.
+- A `variables.hcl` file that defines the variables in a pack.
+- An optional, but _highly encouraged_ `CHANGELOG.md` file that lists changes for each version of the pack.
+- An optional `outputs.tpl` file that defines an output to be printed when a pack is deployed.
+- A `templates` subdirectory containing the HCL templates used to render one or more Nomad job specifications.
+
+To streamline pack creation, you can use the `generate pack` command to scaffold the above files with boilerplate and example data:
+
+```shell-session
+$ nomad-pack generate pack hello_pack
+Creating "hello_pack" Pack in "."...
+```
+
+Next, you will create each of these files for your custom pack.
+
+#### metadata.hcl
+
+The `metadata.hcl` file contains important key value information about the pack. It contains the following blocks and their associated fields:
+
+- `app` - Information about the application that the pack deploys
+  - `url` - The HTTP(S) URL of the homepage of the application. This attribute can also be used to provide a reference to the documentation and help pages.
+- `pack` - Metadata about the pack itself
+  - `name` - The name of the pack.
+  - `description` - A small overview of the application that is deployed by the pack.
+  - `version` - The version of the pack.
+- `dependency` - The dependencies that the pack has on other packs. Multiple dependencies can be supplied.
+  - `alias` - Name to refer to this specific dependency instance. Helpful when importing multiple versions of the same dependency.
+  - `source` - The source URL for this dependency. Dependencies with different names can refer to the same source pack.
+
+Add a `metadata.hcl` file with the following contents:
+
+
+<CodeBlockConfig filename="metadata.hcl">
+
+
+```hcl
+  app {
+    url = "https://learn.hashicorp.com/tutorials/nomad/nomad-pack-writing-packs"
+  }
+
+  pack {
+    name = "hello_pack"
+    description = "This is an example pack created to learn about Nomad Pack"
+    version = "0.0.1"
+  }
+```
+
+</CodeBlockConfig>
+
+#### variables.hcl
+
+The `variables.hcl` file defines the variables required to fully render and deploy all the templates found within the "templates" directory.
+
+Add a `variables.hcl` file with the following contents:
+
+<CodeBlockConfig filename="variables.hcl">
+
+
+```hcl
+variable "datacenters" {
+  description = "A list of datacenters in the region which are eligible for task placement."
+  type        = list(string)
+  default     = ["dc1"]
+}
+
+variable "region" {
+  description = "The region where the job should be placed."
+  type        = string
+  default     = "global"
+}
+
+variable "app_count" {
+  description = "The number of instances to deploy"
+  type        = number
+  default     = 3
+}
+
+variable "resources" {
+  description = "The resource to assign to the application."
+  type = object({
+    cpu    = number
+    memory = number
+  })
+  default = {
+    cpu    = 500,
+    memory = 256
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### outputs.tpl
+
+The `outputs.tpl` is an optional file that defines an output to be printed when a pack is deployed.
+
+Output files have access to the pack variables defined in `variables.hcl`, metadata, and any
+helper templates (see below). A simple example:
+
+```
+Congrats on deploying [[ meta "pack.name" . ]].
+
+There are [[ var "count" . ]] instances of your job now running on Nomad.
+```
+
+#### README and CHANGELOG
+
+No specific format is required for the `README.md` or `CHANGELOG.md` files.
+
+Create a simple `README.md` and empty `CHANGELOG.md` for now:
+
+```shell-session
+$ touch CHANGELOG && echo "#Hello Packs" >> README.md
+```
+
+## Write the templates
+
+Each file at the top level of the `templates` directory that uses the extension ".nomad.tpl" defines a resource (such as a job) that will be applied to Nomad. These files can use any UTF-8 encoded prefix as the name.
+
+Helper templates, which can be included within larger templates, have names prefixed with an underscore “\_” and use a ".tpl" extension.
+
+In a deployment, Nomad Pack will render each job template using the variables provided and apply it to Nomad.
+
+Nomad Pack will render any files ending in `.tpl` but without `.nomad` when calling the `render` command. This can be useful for templatizing configuration files for other non-jobspec files for a job. Nomad Pack will not do anything with these files other than render them.
+
+#### Template basics
+
+Templates are written using [Go Template Syntax](/nomad/docs/reference/go-template-syntax). This enables templates to have complex logic where necessary.
+
+Unlike default Go Template syntax, Nomad Pack uses `"[["` and `"]]"` as delimiters.
+
+Go ahead make your first template at `./templates/hello_pack.nomad.tpl` with the content below. This defines
+a job called "hello_pack" and allows you to provide variable values for `region`, `datacenters`,
+`app_count`, and `resources`.
+
+<CodeBlockConfig filename="hello_pack.nomad.tpl">
+
+```hcl
+job "hello_pack" {
+  type   = "service"
+  region = "[[ var "region" . ]]"
+  datacenters = [ [[ range $idx, $dc := (var "datacenters" .) ]][[if $idx]],[[end]][[ $dc | quote ]][[ end ]] ]
+
+  group "app" {
+    count = [[ var "count" . ]]
+
+    network {
+      port "http" {
+        static = 80
+      }
+    }
+
+    [[/* this is a go template comment */]]
+
+    task "server" {
+      driver = "docker"
+      config {
+        image        = "mnomitch/hello_world_server"
+        network_mode = "host"
+        ports        = ["http"]
+      }
+
+      resources {
+        cpu    = [[ var "resources.cpu" . ]]
+        memory = [[ var "resources.memory" . ]]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `datacenters` value shows a more complex usage of the Go Template, which allows for
+[control structures](/nomad/docs/reference/go-template-syntax#control-structure-list) like `range`
+and [pipelines](/nomad/docs/reference/go-template-syntax#pipelines).
+
+<Note>
+
+A simpler (but less informative) option of `datacenters = [[ var "datacenters" . | toStringList ]]`
+is possible as well.
+
+</Note>
+
+#### Template functions
+
+The [`masterminds/sprig`](https://github.com/Masterminds/sprig) library supplements the standard Go Template set of template functions. This adds helper functions for various use cases such as string manipulation, cryptography, and data conversion (for instance to and from JSON).
+
+Custom Nomad-specific and debugging functions are also provided:
+
+- `nomadRegions` returns the API object from `/v1/regions`.
+- `nomadNamespaces` returns the API object from `/v1/namespaces`.
+- `nomadNamespace` takes a single string parameter of a namespace ID which will be read via `/v1/namespace/:namespace`.
+- `spewDump` dumps the entirety of the passed object as a string. The output includes the content types and values. This uses the `spew.SDump` function.
+- `spewPrintf` dumps the supplied arguments into a string according to the supplied format. This uses the `spew.Printf` function.
+- `fileContents` takes an argument to a file of the local host, reads its contents and provides this as a string.
+
+A custom function within a template is called like any other:
+
+```
+[[ nomadRegions ]]
+[[ nomadRegions | spewDump ]]
+```
+
+You will not use any of the helper functions in this tutorial, but they are available to help you write custom packs in the future.
+
+#### Helper templates
+
+For more complex packs, you may want to reuse template snippets across multiple resources.
+
+For instance, suppose you have two jobs defined in your pack and both jobs reuse
+the same `region` logic. You can create a helper template to centralize that
+logic.
+
+Helper template names are prepended with an underscore `_` and end in `.tpl`.
+
+Go ahead and define your first helper template at `./templates/_region.tpl`.
+
+<CodeBlockConfig filename="_region.tp">
+
+```hcl
+[[ define "region" -]]
+[[- if var "region" . -]]
+  region = [[ (var "region" .) | quote ]]
+[[- end -]]
+[[- end -]]
+```
+
+</CodeBlockConfig>
+
+This template will only specify the "region" value on the job if the `region` variable
+has been passed into Nomad Pack.
+
+You can now use this helper template in your job file.
+
+<CodeBlockConfig filename="hello_pack.nomad.tpl">
+
+```hcl
+job "hello_pack" {
+  type = "service"
+
+  [[ template "region" . ]]
+
+  datacenters = [[ var "datacenters" . | toStringList ]]
+
+  ...
+}
+```
+
+</CodeBlockConfig>
+
+If this pack defined multiple jobs, this logic could now be reused throughout the pack.
+
+#### Conditional jobs
+
+Some packs will have multiple jobs, and occasionally some of these jobs should only be run
+if certain variable values are provided.
+
+If a template is empty, Nomad Pack will not run any job. This allows for conditional jobs:
+
+```hcl
+[[ if var "use-own-database" . ]]
+job "postgres" {
+  ...
+}
+[[ end ]]
+```
+
+#### Pack dependencies
+
+Packs can depend on content from other packs.
+
+You must place copies of dependent packs into the `deps` directory. This process is known as vendoring. The file structure for dependent packs looks like the following:
+
+```plaintext
+<PACK-A>
+  └── ...Pack A's contents...
+  └── deps
+    └── <PACK-B>
+      └── ...Pack B's contents...
+```
+
+This allows Pack A to use any helper templates defined in Pack B, and Pack A will
+automatically deploy any jobs defined in Pack B when it deploys.
+
+In addition to the filesystem, packs must define their dependencies in `metadata.hcl`.
+An example pack block with a dependency looks like the following.
+
+<CodeBlockConfig filename="metadata.hcl" lineNumbers highlight="11-14">
+
+```hcl
+app {
+  url    = "https://some-url-for-the-application.dev"
+}
+
+pack {
+  name        = "hello_pack_with_deps"
+  description = "This pack contains a simple service job, and depends on another pack."
+  version     = "0.2.1"
+}
+
+dependency "demo_dep" {
+  source = "git::https://github.com/org-name/repo-name.git//packs/demo_dep"
+}
+```
+
+</CodeBlockConfig>
+
+Nomad Pack provides a helper command to take packs defined as dependencies and vendor them.
+Running this command from a pack's root directory will download the files associated with any
+pack dependency and put them in the `deps` directory.
+
+```shell-session
+$ nomad-pack deps vendor
+```
+
+<Note>
+
+While developing a dependent pack alongside a parent pack, it can be helpful to symlink
+a reference to the dependent pack in the `deps` directory.
+
+</Note>
+
+This allows templates of `hello_pack_with_deps` to use `demo_dep`'s helper templates, and deploy
+any jobs in demo_dep when running `hello_pack_with_deps`.
+
+```hcl
+[[ template "helper_data" . ]]
+```
+
+You can pass in variables for a dependent pack with a reference to their name or alias value.
+
+```shell-session
+$ nomad-pack run hello_pack_with_deps --var demo_dep.message="example"
+```
+
+## Testing your pack
+
+As you write packs, you may want to test them. To do this, pass the
+directory path as the name of the pack to the `run`, `plan`, `render`, `info`,
+`stop`, or `destroy` commands. Relative paths are supported.
+
+```shell-session
+$ nomad-pack info .
+```
+
+```shell-session
+$ nomad-pack render .
+```
+
+```shell-session
+$ nomad-pack run .
+```
+
+## Publish and find your custom repository
+
+To use and share your new pack, push the git repository to a URL
+accessible by your command line tool. In this demo you will push to a GitHub repository.
+
+If you wish to share your packs with the Nomad community, please consider adding them to the
+[Nomad Pack Community Registry][nomad-pack-community-registry].
+
+## Deploy your custom pack from a custom registry
+
+If you have added your own registry to GitHub, add it to your local Nomad Pack using the
+`nomad-pack registry add` command.
+
+```shell-session
+$ nomad-pack registry add my_packs git@github.com/<YOUR_ORG>/<YOUR_REPO>
+```
+
+This will download the packs defined in the GitHub repository to your local
+filesystem. They will be found using the registry value "my_packs".
+
+Deploy your custom pack.
+
+```shell-session
+$ nomad-pack run hello_pack --var app_count=1 --registry=my_packs
+```
+
+## Next steps
+
+In this tutorial you learned:
+
+- how packs and pack registries are structured
+- how to write a custom pack
+- how to test your pack locally
+- how to deploy a custom pack
+
+As you write packs, consider contributing them to the [Nomad Pack Community Registry][nomad-pack-community-registry].
+This is a great source of feedback, best-practices, and shared-knowledge.
+
+To help speed up your pack development and testing, check out the [Setup HashiCorp Nomad Pack][nomad-pack-github-action] GitHub Action - it takes care of setting up the Nomad Pack binary and making it available to your GitHub Actions workflow.
+
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[example-nomad-pack-registry]: https://github.com/hashicorp/example-nomad-pack-registry
+[nomad-pack-community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
+[nomad-pack-github-action]: https://github.com/marketplace/actions/setup-hashicorp-nomad-pack
diff --git a/content/nomad/v1.11.x/content/tools/nomad-pack/index.mdx b/content/nomad/v1.11.x/content/tools/nomad-pack/index.mdx
new file mode 100644
index 0000000000..5a05f4c9f6
--- /dev/null
+++ b/content/nomad/v1.11.x/content/tools/nomad-pack/index.mdx
@@ -0,0 +1,268 @@
+---
+layout: docs
+page_title: Nomad Pack
+description: |-
+  Discover what Nomad Pack does, how it helps speed up deployment, and deploy an
+  application to Nomad using Nomad Pack.
+---
+
+# Nomad Pack
+
+This guide will walk you through basic usage of [Nomad Pack][pack-repo], a
+package manager and templating tool for Nomad.
+
+By the end of this guide, you will know what Nomad Pack does, be able to deploy
+applications to Nomad using Nomad Pack, and discover packs built by the Nomad community.
+
+## What is Nomad Pack?
+
+Nomad Pack is a templating and packaging tool used with [HashiCorp Nomad][nomad-site].
+
+Nomad Pack is used to:
+
+- Easily deploy popular applications to Nomad
+- Re-use common patterns across internal applications
+- Find and share job specifications with the Nomad community
+
+Nomad Pack can be thought of as a templating and deployment tool like [Levant](https://github.com/hashicorp/levant)
+with the ability to pull from remote registries and deploy multiple resources together, like [Helm](https://helm.sh/).
+
+## Requirements
+
+- A Nomad cluster available
+- Nomad cluster address defined in the `NOMAD_ADDR` environment variable.
+
+<Note>
+
+ If Nomad ACLs are enabled, a token with proper permissions must be defined in the `NOMAD_TOKEN` environment variable.
+
+</Note>
+
+## Installing Nomad Pack
+
+To use Nomad Pack, download the binary for your system from [HashiCorp Releases][releases].
+
+After downloading Nomad Pack, unzip the package, and make sure that the `nomad-pack` binary is available on your PATH.
+
+Alternatively, you can install it with Homebrew if you are on MacOS.
+
+```shell-session
+$ brew tap hashicorp/tap
+$ brew install hashicorp/tap/nomad-pack
+```
+
+You can now run `nomad-pack`.
+
+## Basic use
+
+To get started, run the `list` command to see which packs are available to deploy.
+
+```shell-session
+$ nomad-pack list
+          PACK NAME          | METADATA VERSION |                  REGISTRY NAME
+-----------------------------+------------------+---------------------------------------------------
+  alertmanager               | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  aws_ebs_csi                | 0.1.0            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  aws_efs_csi                | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  backstage                  | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  boundary                   | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  caddy                      | 0.0.1            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  ceph                       | 0.1.0            | default@6bac78a905b7966ed93078cba1604fafe0fa2334
+  [...]
+```
+
+The first time you run the `list` command, Nomad Pack will add a `nomad/packs`
+directory to your desktop user's cache directory—`$XDG_CACHE_DIR` on Linux,
+`~/Library/Caches` on macOS, `%AppData%` on Windows, etc. This folder stores
+information about cloned registries and their available packs.
+
+During initializing, Nomad Pack downloads a default registry of packs from the
+[Nomad Pack community registry][community-registry].
+
+To deploy one of these packs, use the `run` command. This deploys each job defined in the pack to Nomad.
+To deploy the `hello_world` pack, you would run the following command:
+
+```shell-session
+$ nomad-pack run hello_world
+
+  Evaluation ID: 67835384-763b-62b0-7c41-eb98a5417e9c
+  Job 'hello_world' in pack deployment 'hello_world@latest' registered successfully
+Pack successfully deployed. Use --name=hello_world@latest to manage this this deployed instance with run, plan, or destroy
+
+Congrats! You deployed a simple service on Nomad.
+```
+
+<Note>
+
+The syntax for Nomad Pack is different in version 0.1. To run packs written with the old syntax, provide the `--parser-v1` flag.
+
+</Note>
+
+Each pack defines a set of variables that can be provided by the user. To get information on the pack
+and to see which variables can be passed in, run the `info` command.
+
+```shell-session
+$ nomad-pack info hello_world
+
+Pack Name          hello_world
+Description        This deploys a simple application as a service with an optional associated consul service.
+Application URL    https://learn.hashicorp.com/tutorials/nomad/get-started-run?in=nomad/get-started
+Application Author HashiCorp
+
+Pack "hello_world" Variables:
+  - "message" (string) - The message your application will render
+  - "register_consul_service" (bool) - If you want to register a consul service for the job
+  - "consul_service_name" (string) - The consul service name for the hello-world application
+  - "consul_service_tags" (list of string) - The consul service name for the hello-world application
+  - "job_name" (string) - The name to use as the job name which overrides using the pack name
+  - "region" (string) - The region where jobs will be deployed
+  - "datacenters" (list of string) - A list of datacenters in the region which are eligible for task placement
+  - "count" (number) - The number of app instances to deploy
+```
+
+Values for these variables are provided using the `--var` flag. Update your pack using
+the following command:
+
+```shell-session
+$ nomad-pack run hello_world --var message=hola
+```
+
+Values can also be provided by passing in a variables file with the `-f` flag.
+
+```shell-session
+$ tee -a ./my-variables.hcl << END
+message=bonjour
+END
+```
+
+```shell-session
+$ nomad-pack run hello_world -f ./my-variables.hcl
+```
+
+To see a list of deployed packs, run the `status` command
+
+```shell-session
+$ nomad-pack status
+
+   PACK NAME  | REGISTRY NAME
+--------------+----------------
+  hello_world | default
+
+```
+
+To see the status of the jobs deployed by a pack, run the `status` command with the pack name.
+
+```shell-session
+$ nomad-pack status hello_world
+
+   PACK NAME  | REGISTRY NAME |  DEPLOYMENT NAME   |  JOB NAME   | STATUS
+--------------+---------------+--------------------+-------------+----------
+  hello_world | default       | hello_world@latest | hello_world | pending
+
+```
+
+To remove all the resources deployed by a pack, run the `destroy` command with the
+pack name.
+
+```shell-session
+$ nomad-pack destroy hello_world
+```
+
+To stop the jobs without removing them from Nomad, use the `stop` command:
+
+```shell-session
+$ nomad-pack stop hello_world
+```
+
+### Adding non-default Pack registries
+
+When using Nomad Pack, the default registry for packs is
+[the Nomad Pack Community Registry][community-registry].
+Packs from this registry will be made automatically available.
+
+You can add more registries by using the `registry add` command. For instance, if you want to add a registry from GitLab with the alias `my_packs`, you can run the following command to download the registry and its contents.
+
+```shell-session
+$ nomad-pack registry add my_packs gitlab.com/mikenomitch/pack-registry
+```
+
+<CodeBlockConfig hideClipboard>
+
+```shell-session
+go-getter URL is gitlab.com/mikenomitch/pack-registry
+Registry successfully cloned at /Users/arusso/Library/Caches/nomad/packs/nomad-pack-tmp
+Processing pack entries at /Users/arusso/Library/Caches/nomad/packs/nomad-pack-tmp
+found pack entry fabio
+Processing pack fabio@latest
+Updating pack
+Removing previous latest
+Writing pack to /Users/arusso/Library/Caches/nomad/packs/my_packs/fabio@latest
+Loading cloned pack from /Users/arusso/Library/Caches/nomad/packs/my_packs/fabio@latest
+Calculating SHA for latest
+found pack entry grafana
+Processing pack grafana@latest
+Updating pack
+Removing previous latest
+Writing pack to /Users/arusso/Library/Caches/nomad/packs/my_packs/grafana@latest
+Loading cloned pack from /Users/arusso/Library/Caches/nomad/packs/my_packs/grafana@latest
+Calculating SHA for latest
+[...]
+  Try running one the packs you just added liked this
+
+    nomad-pack run fabio --registry=my_packs --ref=latest
+```
+
+</CodeBlockConfig>
+
+To view the available registries, including yours, run the `registry list` command.
+
+```shell-session
+$ nomad-pack registry list
+  REGISTRY NAME |  REF   | LOCAL REF |                    REGISTRY URL
+----------------+--------+-----------+-----------------------------------------------------
+  default       | latest | 6bac78a9  | github.com/hashicorp/nomad-pack-community-registry
+  my_packs      | latest | 7ca313c7  | gitlab.com/mikenomitch/pack-registry
+```
+
+To view the available packs, including yours, run the `list` command.
+
+```shell-session
+$ nomad-pack list
+[...]
+  fabio                      | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  grafana                    | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  haproxy                    | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  hello_world                | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  loki                       | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  nginx                      | 0.0.1            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  nomad_autoscaler           | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+  traefik                    | 0.1.0            | my_packs@7ca313c705b7966ed93078cba1604fafe0fa2334
+```
+
+You can deploy packs from this registry with the `run` command and the alias given
+to the registry, in this case `my_packs`.
+
+```shell-session
+$ nomad-pack run nginx --registry=my_packs
+  Evaluation ID: aaa3c319-1928-7c35-54b0-2358841c0e96
+  Job 'nginx' in pack deployment 'nginx@latest' registered successfully
+Pack successfully deployed. Use nginx with --ref=latest to manage this this deployed instance with plan, stop, destroy, or info
+
+Nginx successfully deployed.
+
+See the Load Balancing with Nginx tutorial for more information:
+https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx
+```
+
+## Next steps
+
+In this tutorial you learned what Nomad Pack does, how to deploy applications to Nomad
+using Nomad Pack, and how to discover packs built by the Nomad community.
+
+Continue on to the [Usage guide][detailed-usage] for more detailed information about how to use Nomad Pack.
+
+[nomad-site]: /nomad/
+[pack-repo]: https://github.com/hashicorp/nomad-pack
+[detailed-usage]: /nomad/tools/nomad-pack/advanced-usage
+[community-registry]: https://github.com/hashicorp/nomad-pack-community-registry
+[releases]: https://releases.hashicorp.com/nomad-pack
diff --git a/content/nomad/v1.11.x/data/api-docs-nav-data.json b/content/nomad/v1.11.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..4219b07ebc
--- /dev/null
+++ b/content/nomad/v1.11.x/data/api-docs-nav-data.json
@@ -0,0 +1,244 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Identities",
+        "path": "acl/identities"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      },
+      {
+        "title": "Upgrade Check",
+        "path": "operator/upgrade-check"
+      },
+      {
+        "title": "Utilization Reporting",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/utilization"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "variables"
+      },
+      {
+        "title": "Variables",
+        "path": "variables/variables"
+      },
+      {
+        "title": "Locks",
+        "path": "variables/locks"
+      }
+    ]
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.11.x/data/commands-nav-data.json b/content/nomad/v1.11.x/data/commands-nav-data.json
new file mode 100644
index 0000000000..f07853163f
--- /dev/null
+++ b/content/nomad/v1.11.x/data/commands-nav-data.json
@@ -0,0 +1,1078 @@
+[
+  {
+    "title": "Commands (CLI)",
+    "path": "index"
+  },
+  {
+    "title": "acl",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "bootstrap",
+        "path": "acl/bootstrap"
+      },
+      {
+        "title": "auth-method",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/auth-method/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/auth-method/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/auth-method/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/auth-method/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/auth-method/update"
+          }
+        ]
+      },
+      {
+        "title": "binding-rule",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/binding-rule/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/binding-rule/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/binding-rule/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/binding-rule/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/binding-rule/update"
+          }
+        ]
+      },
+      {
+        "title": "policy",
+        "routes": [
+          {
+            "title": "apply",
+            "path": "acl/policy/apply"
+          },
+          {
+            "title": "delete",
+            "path": "acl/policy/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/policy/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/policy/list"
+          },
+          {
+            "title": "self",
+            "path": "acl/policy/self"
+          }
+        ]
+      },
+      {
+        "title": "role",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/role/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/role/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/role/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/role/list"
+          },
+          {
+            "title": "update",
+            "path": "acl/role/update"
+          }
+        ]
+      },
+      {
+        "title": "token",
+        "routes": [
+          {
+            "title": "create",
+            "path": "acl/token/create"
+          },
+          {
+            "title": "delete",
+            "path": "acl/token/delete"
+          },
+          {
+            "title": "info",
+            "path": "acl/token/info"
+          },
+          {
+            "title": "list",
+            "path": "acl/token/list"
+          },
+          {
+            "title": "self",
+            "path": "acl/token/self"
+          },
+          {
+            "title": "update",
+            "path": "acl/token/update"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "agent",
+    "path": "agent"
+  },
+  {
+    "title": "agent-info",
+    "path": "agent-info"
+  },
+  {
+    "title": "alloc",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "alloc"
+      },
+      {
+        "title": "checks",
+        "path": "alloc/checks"
+      },
+      {
+        "title": "exec",
+        "path": "alloc/exec"
+      },
+      {
+        "title": "fs",
+        "path": "alloc/fs"
+      },
+      {
+        "title": "logs",
+        "path": "alloc/logs"
+      },
+      {
+        "title": "pause",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "alloc/pause"
+      },
+      {
+        "title": "restart",
+        "path": "alloc/restart"
+      },
+      {
+        "title": "signal",
+        "path": "alloc/signal"
+      },
+      {
+        "title": "status",
+        "path": "alloc/status"
+      },
+      {
+        "title": "stop",
+        "path": "alloc/stop"
+      }
+    ]
+  },
+  {
+    "title": "config",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "config"
+      },
+      {
+        "title": "validate",
+        "path": "config/validate"
+      }
+    ]
+  },
+  {
+    "title": "deployment",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "deployment"
+      },
+      {
+        "title": "fail",
+        "path": "deployment/fail"
+      },
+      {
+        "title": "list",
+        "path": "deployment/list"
+      },
+      {
+        "title": "pause",
+        "path": "deployment/pause"
+      },
+      {
+        "title": "promote",
+        "path": "deployment/promote"
+      },
+      {
+        "title": "resume",
+        "path": "deployment/resume"
+      },
+      {
+        "title": "status",
+        "path": "deployment/status"
+      },
+      {
+        "title": "unblock",
+        "path": "deployment/unblock"
+      }
+    ]
+  },
+  {
+    "title": "eval",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "eval"
+      },
+      {
+        "title": "delete",
+        "path": "eval/delete"
+      },
+      {
+        "title": "list",
+        "path": "eval/list"
+      },
+      {
+        "title": "status",
+        "path": "eval/status"
+      }
+    ]
+  },
+  {
+    "title": "fmt",
+    "path": "fmt"
+  },
+  {
+    "title": "job",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job"
+      },
+      {
+        "title": "action",
+        "path": "job/action"
+      },
+      {
+        "title": "allocs",
+        "path": "job/allocs"
+      },
+      {
+        "title": "deployments",
+        "path": "job/deployments"
+      },
+      {
+        "title": "dispatch",
+        "path": "job/dispatch"
+      },
+      {
+        "title": "eval",
+        "path": "job/eval"
+      },
+      {
+        "title": "history",
+        "path": "job/history"
+      },
+      {
+        "title": "init",
+        "path": "job/init"
+      },
+      {
+        "title": "inspect",
+        "path": "job/inspect"
+      },
+      {
+        "title": "plan",
+        "path": "job/plan"
+      },
+      {
+        "title": "periodic force",
+        "path": "job/periodic-force"
+      },
+      {
+        "title": "promote",
+        "path": "job/promote"
+      },
+      {
+        "title": "restart",
+        "path": "job/restart"
+      },
+      {
+        "title": "revert",
+        "path": "job/revert"
+      },
+      {
+        "title": "run",
+        "path": "job/run"
+      },
+      {
+        "title": "scale",
+        "path": "job/scale"
+      },
+      {
+        "title": "scaling-events",
+        "path": "job/scaling-events"
+      },
+      {
+        "title": "start",
+        "path": "job/start"
+      },
+      {
+        "title": "status",
+        "path": "job/status"
+      },
+      {
+        "title": "stop",
+        "path": "job/stop"
+      },
+      {
+        "title": "tag",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job/tag"
+          },
+          {
+            "title": "apply",
+            "path": "job/tag/apply"
+          },
+          {
+            "title": "unset",
+            "path": "job/tag/unset"
+          }
+        ]
+      },
+      {
+        "title": "validate",
+        "path": "job/validate"
+      }
+    ]
+  },
+  {
+    "title": "license",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "license"
+      },
+      {
+        "title": "get",
+        "path": "license/get"
+      },
+      {
+        "title": "inspect",
+        "path": "license/inspect"
+      }
+    ]
+  },
+  {
+    "title": "login",
+    "path": "login"
+  },
+  {
+    "title": "monitor",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "monitor"
+      },
+      { "title": "export", "path": "monitor/export" }
+    ]
+  },
+  {
+    "title": "namespace",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "namespace"
+      },
+      {
+        "title": "apply",
+        "path": "namespace/apply"
+      },
+      {
+        "title": "delete",
+        "path": "namespace/delete"
+      },
+      {
+        "title": "inspect",
+        "path": "namespace/inspect"
+      },
+      {
+        "title": "list",
+        "path": "namespace/list"
+      },
+      {
+        "title": "status",
+        "path": "namespace/status"
+      }
+    ]
+  },
+  {
+    "title": "node",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "node"
+      },
+      {
+        "title": "config",
+        "path": "node/config"
+      },
+      {
+        "title": "drain",
+        "path": "node/drain"
+      },
+      {
+        "title": "eligibility",
+        "path": "node/eligibility"
+      },
+      {
+        "title": "identity",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "node/identity"
+          },
+          {
+            "title": "get",
+            "path": "node/identity/get"
+          },
+          {
+            "title": "renew",
+            "path": "node/identity/renew"
+          }
+        ]
+      },
+      {
+        "title": "intro",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "node/intro"
+          },
+          {
+            "title": "create",
+            "path": "node/intro/create"
+          }
+        ]
+      },
+      {
+        "title": "meta",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "node/meta"
+          },
+          {
+            "title": "apply",
+            "path": "node/meta/apply"
+          },
+          {
+            "title": "read",
+            "path": "node/meta/read"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "node/status"
+      }
+    ]
+  },
+  {
+    "title": "node pool",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "node-pool"
+      },
+      {
+        "title": "apply",
+        "path": "node-pool/apply"
+      },
+      {
+        "title": "delete",
+        "path": "node-pool/delete"
+      },
+      {
+        "title": "info",
+        "path": "node-pool/info"
+      },
+      {
+        "title": "init",
+        "path": "node-pool/init"
+      },
+      {
+        "title": "jobs",
+        "path": "node-pool/jobs"
+      },
+      {
+        "title": "list",
+        "path": "node-pool/list"
+      },
+      {
+        "title": "nodes",
+        "path": "node-pool/nodes"
+      }
+    ]
+  },
+  {
+    "title": "operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "api",
+        "path": "operator/api"
+      },
+      {
+        "title": "autopilot",
+        "routes": [
+          {
+            "title": "get-config",
+            "path": "operator/autopilot/get-config"
+          },
+          {
+            "title": "set-config",
+            "path": "operator/autopilot/set-config"
+          },
+          {
+            "title": "health",
+            "path": "operator/autopilot/health"
+          }
+        ]
+      },
+      {
+        "title": "client-state",
+        "path": "operator/client-state"
+      },
+      {
+        "title": "debug",
+        "path": "operator/debug"
+      },
+      {
+        "title": "gossip",
+        "routes": [
+          {
+            "title": "keyring generate",
+            "path": "operator/gossip/keyring-generate"
+          },
+          {
+            "title": "keyring install",
+            "path": "operator/gossip/keyring-install"
+          },
+          {
+            "title": "keyring list",
+            "path": "operator/gossip/keyring-list"
+          },
+          {
+            "title": "keyring remove",
+            "path": "operator/gossip/keyring-remove"
+          },
+          {
+            "title": "keyring use",
+            "path": "operator/gossip/keyring-use"
+          }
+        ]
+      },
+      {
+        "title": "metrics",
+        "path": "operator/metrics"
+      },
+      {
+        "title": "raft",
+        "routes": [
+          {
+            "title": "info",
+            "path": "operator/raft/info"
+          },
+          {
+            "title": "list-peers",
+            "path": "operator/raft/list-peers"
+          },
+          {
+            "title": "logs",
+            "path": "operator/raft/logs"
+          },
+          {
+            "title": "remove-peer",
+            "path": "operator/raft/remove-peer"
+          },
+          {
+            "title": "state",
+            "path": "operator/raft/state"
+          },
+          {
+            "title": "transfer-leadership",
+            "path": "operator/raft/transfer-leadership"
+          }
+        ]
+      },
+      {
+        "title": "root",
+        "routes": [
+          {
+            "title": "keyring list",
+            "path": "operator/root/keyring-list"
+          },
+          {
+            "title": "keyring remove",
+            "path": "operator/root/keyring-remove"
+          },
+          {
+            "title": "keyring rotate",
+            "path": "operator/root/keyring-rotate"
+          }
+        ]
+      },
+      {
+        "title": "scheduler",
+        "routes": [
+          {
+            "title": "get-config",
+            "path": "operator/scheduler/get-config"
+          },
+          {
+            "title": "set-config",
+            "path": "operator/scheduler/set-config"
+          }
+        ]
+      },
+      {
+        "title": "snapshot",
+        "routes": [
+          {
+            "title": "agent",
+            "badge": {
+              "text": "ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "operator/snapshot/agent"
+          },
+          {
+            "title": "inspect",
+            "path": "operator/snapshot/inspect"
+          },
+          {
+            "title": "redact",
+            "path": "operator/snapshot/redact"
+          },
+          {
+            "title": "restore",
+            "path": "operator/snapshot/restore"
+          },
+          {
+            "title": "save",
+            "path": "operator/snapshot/save"
+          },
+          {
+            "title": "state",
+            "path": "operator/snapshot/state"
+          }
+        ]
+      },
+      {
+        "title": "utilization",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "operator/utilization"
+      }
+    ]
+  },
+  {
+    "title": "plugin",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "plugin"
+      },
+      {
+        "title": "status",
+        "path": "plugin/status"
+      }
+    ]
+  },
+  {
+    "title": "quota",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "quota"
+      },
+      {
+        "title": "apply",
+        "path": "quota/apply"
+      },
+      {
+        "title": "delete",
+        "path": "quota/delete"
+      },
+      {
+        "title": "init",
+        "path": "quota/init"
+      },
+      {
+        "title": "inspect",
+        "path": "quota/inspect"
+      },
+      {
+        "title": "list",
+        "path": "quota/list"
+      },
+      {
+        "title": "status",
+        "path": "quota/status"
+      }
+    ]
+  },
+  {
+    "title": "recommendation",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "recommendation"
+      },
+      {
+        "title": "apply",
+        "path": "recommendation/apply"
+      },
+      {
+        "title": "dismiss",
+        "path": "recommendation/dismiss"
+      },
+      {
+        "title": "info",
+        "path": "recommendation/info"
+      },
+      {
+        "title": "list",
+        "path": "recommendation/list"
+      }
+    ]
+  },
+  {
+    "title": "setup",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "setup"
+      },
+      {
+        "title": "consul",
+        "path": "setup/consul"
+      },
+      {
+        "title": "vault",
+        "path": "setup/vault"
+      }
+    ]
+  },
+  {
+    "title": "scaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "scaling"
+      },
+      {
+        "title": "policy info",
+        "path": "scaling/policy-info"
+      },
+      {
+        "title": "policy list",
+        "path": "scaling/policy-list"
+      }
+    ]
+  },
+  {
+    "title": "sentinel",
+    "badge": {
+      "text": "ENT",
+      "type": "outlined",
+      "color": "neutral"
+    },
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "sentinel"
+      },
+      {
+        "title": "apply",
+        "path": "sentinel/apply"
+      },
+      {
+        "title": "delete",
+        "path": "sentinel/delete"
+      },
+      {
+        "title": "list",
+        "path": "sentinel/list"
+      },
+      {
+        "title": "read",
+        "path": "sentinel/read"
+      }
+    ]
+  },
+  {
+    "title": "server",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "server"
+      },
+      {
+        "title": "force-leave",
+        "path": "server/force-leave"
+      },
+      {
+        "title": "join",
+        "path": "server/join"
+      },
+      {
+        "title": "members",
+        "path": "server/members"
+      }
+    ]
+  },
+  {
+    "title": "service",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "service"
+      },
+      {
+        "title": "service delete",
+        "path": "service/delete"
+      },
+      {
+        "title": "service info",
+        "path": "service/info"
+      },
+      {
+        "title": "service list",
+        "path": "service/list"
+      }
+    ]
+  },
+  {
+    "title": "status",
+    "path": "status"
+  },
+  {
+    "title": "system",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "system"
+      },
+      {
+        "title": "gc",
+        "path": "system/gc"
+      },
+      {
+        "title": "reconcile summaries",
+        "path": "system/reconcile-summaries"
+      }
+    ]
+  },
+  {
+    "title": "tls",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "tls"
+      },
+      {
+        "title": "ca create",
+        "path": "tls/ca-create"
+      },
+      {
+        "title": "ca info",
+        "path": "tls/ca-info"
+      },
+      {
+        "title": "cert create",
+        "path": "tls/cert-create"
+      },
+      {
+        "title": "cert info",
+        "path": "tls/cert-info"
+      }
+    ]
+  },
+  {
+    "title": "ui",
+    "path": "ui"
+  },
+  {
+    "title": "var",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "var"
+      },
+      {
+        "title": "get",
+        "path": "var/get"
+      },
+      {
+        "title": "init",
+        "path": "var/init"
+      },
+      {
+        "title": "list",
+        "path": "var/list"
+      },
+      {
+        "title": "put",
+        "path": "var/put"
+      },
+      {
+        "title": "lock",
+        "path": "var/lock"
+      },
+      {
+        "title": "purge",
+        "path": "var/purge"
+      }
+    ]
+  },
+  {
+    "title": "version",
+    "path": "version"
+  },
+  {
+    "title": "volume",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "volume"
+      },
+      {
+        "title": "claim delete",
+        "path": "volume/claim-delete"
+      },
+      {
+        "title": "claim list",
+        "path": "volume/claim-list"
+      },
+      {
+        "title": "create",
+        "path": "volume/create"
+      },
+      {
+        "title": "delete",
+        "path": "volume/delete"
+      },
+      {
+        "title": "deregister",
+        "path": "volume/deregister"
+      },
+      {
+        "title": "detach",
+        "path": "volume/detach"
+      },
+      {
+        "title": "init",
+        "path": "volume/init"
+      },
+      {
+        "title": "register",
+        "path": "volume/register"
+      },
+      {
+        "title": "snapshot create",
+        "path": "volume/snapshot-create"
+      },
+      {
+        "title": "snapshot delete",
+        "path": "volume/snapshot-delete"
+      },
+      {
+        "title": "snapshot list",
+        "path": "volume/snapshot-list"
+      },
+      {
+        "title": "status",
+        "path": "volume/status"
+      }
+    ]
+  },
+  {
+    "title": "windows",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "windows"
+      },
+      {
+        "title": "service install",
+        "path": "windows/service-install"
+      },
+      {
+        "title": "service uninstall",
+        "path": "windows/service-uninstall"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.11.x/data/docs-nav-data.json b/content/nomad/v1.11.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..e2a2fdcb15
--- /dev/null
+++ b/content/nomad/v1.11.x/data/docs-nav-data.json
@@ -0,0 +1,1752 @@
+[
+  {
+    "heading": "Get started"
+  },
+  {
+    "title": "What is Nomad?",
+    "path": "what-is-nomad"
+  },
+  {
+    "title": "Quickstart",
+    "path": "quickstart"
+  },
+  {
+    "title": "Use cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Architecture",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "architecture"
+      },
+      {
+        "title": "Cluster",
+        "routes": [
+          {
+            "title": "Cluster Consensus",
+            "path": "architecture/cluster/consensus"
+          },
+          {
+            "title": "Multi-cluster federation",
+            "path": "architecture/cluster/federation"
+          },
+          {
+            "title": "Node identity",
+            "path": "architecture/cluster/node-identity"
+          },
+          {
+            "title": "Node pools",
+            "path": "architecture/cluster/node-pools"
+          }
+        ]
+      },
+      {
+        "title": "CPU",
+        "path": "architecture/cpu"
+      },
+      {
+        "title": "Security",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "architecture/security"
+          },
+          {
+            "title": "Cluster Gossip",
+            "path": "architecture/security/gossip"
+          }
+        ]
+      },
+      {
+        "title": "Storage",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "architecture/storage"
+          },
+          {
+            "title": "CSI",
+            "path": "architecture/storage/csi"
+          },
+          {
+            "title": "Host volumes",
+            "path": "architecture/storage/host-volumes"
+          },
+          {
+            "title": "Stateful workload considerations",
+            "path": "architecture/storage/stateful-workloads"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Allocation filesystem",
+        "path": "concepts/filesystem"
+      },
+
+      {
+        "title": "Job",
+        "path": "concepts/job"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "concepts/variables"
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "How scheduling works",
+            "path": "concepts/scheduling/how-scheduling-works"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          },
+          {
+            "title": "Job schedulers",
+            "path": "concepts/scheduling/schedulers"
+          }
+        ]
+      },
+      {
+        "title": "Stateful deployments",
+        "path": "concepts/stateful-deployments"
+      },
+      {
+        "title": "Workload identity",
+        "path": "concepts/workload-identity"
+      }
+    ]
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Nomad operations"
+  },
+
+  {
+    "title": "Deploy and run Nomad",
+    "routes": [
+      {
+        "title": "Install Nomad",
+        "path": "deploy"
+      },
+      {
+        "title": "Production deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "deploy/production/requirements"
+          },
+          {
+            "title": "Reference architecture",
+            "path": "deploy/production/reference-architecture"
+          },
+          {
+            "title": "Deployment guide",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul"
+          },
+          {
+            "title": "Windows service",
+            "path": "deploy/production/windows-service"
+          }
+        ]
+      },
+      {
+        "title": "Operate a Nomad agent",
+        "path": "deploy/nomad-agent"
+      },
+      {
+        "title": "Build Nomad clusters",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/clusters"
+          },
+          {
+            "title": "Connect nodes into a cluster",
+            "path": "deploy/clusters/connect-nodes"
+          },
+          {
+            "title": "Multi-region federation considerations",
+            "path": "deploy/clusters/federation-considerations"
+          },
+          {
+            "title": "Federation failure scenarios",
+            "path": "deploy/clusters/federation-failure-scenarios"
+          },
+          {
+            "title": "Federate multi-region clusters",
+            "path": "deploy/clusters/federate-regions"
+          },
+          {
+            "title": "Load balancing",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/load-balancing"
+          },
+          {
+            "title": "Configure a web UI reverse proxy",
+            "path": "deploy/clusters/reverse-proxy-ui"
+          }
+        ]
+      },
+      {
+        "title": "Configure task drivers",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "deploy/task-driver"
+          },
+          {
+            "title": "Docker",
+            "path": "deploy/task-driver/docker"
+          },
+          {
+            "title": "Isolated Fork/Exec",
+            "path": "deploy/task-driver/exec"
+          },
+          {
+            "title": "Java",
+            "path": "deploy/task-driver/java"
+          },
+          {
+            "title": "QEMU",
+            "path": "deploy/task-driver/qemu"
+          },
+          {
+            "title": "Raw Fork/Exec",
+            "path": "deploy/task-driver/raw_exec"
+          },
+          {
+            "title": "Task driver plugins",
+            "routes": [
+              {
+                "title": "Exec2",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/exec2"
+              },
+              {
+                "title": "Podman",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/podman"
+              },
+              {
+                "title": "Virt <sup>Beta</sup>",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/virt"
+              },
+              {
+                "title": "Community",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/community"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Govern Nomad's use",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "govern"
+      },
+      {
+        "title": "Namespaces",
+        "path": "govern/namespaces"
+      },
+      {
+        "title": "Node pools",
+        "path": "govern/use-node-pools"
+      },
+      {
+        "title": "Resource quotas",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "govern/resource-quotas"
+      },
+      {
+        "title": "Sentinel policies",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "govern/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "Manage Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "manage"
+      },
+      {
+        "title": "Autopilot",
+        "path": "manage/autopilot"
+      },
+      {
+        "title": "Format CLI output",
+        "path": "manage/format-cli-output"
+      },
+      {
+        "title": "Garbage collection",
+        "path": "manage/garbage-collection"
+      },
+      {
+        "title": "Key management",
+        "path": "manage/key-management"
+      },
+      {
+        "title": "Migrate workloads",
+        "path": "manage/migrate-workloads"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "manage/variables"
+      },
+      {
+        "title": "Recovery",
+        "path": "manage/outage-recovery"
+      }
+    ]
+  },
+  {
+    "title": "Monitor Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "monitor"
+      },
+      {
+        "title": "Event stream",
+        "path": "monitor/event-stream"
+      },
+      {
+        "title": "Inspect job workloads",
+        "path": "monitor/inspect-workloads"
+      },
+      {
+        "title": "Inspect clusters",
+        "path": "monitor/inspect-cluster"
+      },
+      {
+        "title": "Cluster topology",
+        "path": "monitor/cluster-topology"
+      },
+      {
+        "title": "Use Prometheus",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/manage-clusters/prometheus-metrics"
+      },
+      {
+        "title": "Monitor job service metrics",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/manage-clusters/prometheus-service-mesh-metrics"
+      }
+    ]
+  },
+  {
+    "title": "Network Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Bridge networking with CNI",
+        "path": "networking/cni"
+      },
+      {
+        "title": "Service discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Consul",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "networking/consul"
+          },
+          {
+            "title": "Service mesh",
+            "path": "networking/consul/service-mesh"
+          }
+        ]
+      },
+      {
+        "title": "IPv6 support",
+        "path": "networking/ipv6"
+      }
+    ]
+  },
+  {
+    "title": "Scale Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "scale"
+      },
+      {
+        "title": "Nomad Autoscaler",
+        "href": "https://developer.hashicorp.com/nomad/tools/autoscaling"
+      },
+      {
+        "title": "Benchmark and load test",
+        "path": "scale/benchmarking"
+      }
+    ]
+  },
+  {
+    "title": "Secure Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "secure"
+      },
+      {
+        "title": "Access control list",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/acl"
+          },
+          {
+            "title": "Bootstrap the ACL system",
+            "path": "secure/acl/bootstrap"
+          },
+          {
+            "title": "Integrate Consul ACL",
+            "path": "secure/acl/consul"
+          },
+          {
+            "title": "Policies",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "secure/acl/policies"
+              },
+              {
+                "title": "Create policies",
+                "path": "secure/acl/policies/create-policy"
+              }
+            ]
+          },
+          {
+            "title": "Tokens",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "secure/acl/tokens"
+              },
+              {
+                "title": "Generate tokens with Vault",
+                "path": "secure/acl/tokens/vault"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Authentication",
+        "routes": [
+          {
+            "title": "Configure JWT",
+            "path": "secure/authentication/jwt"
+          },
+          {
+            "title": "Configure OIDC",
+            "path": "secure/authentication/oidc"
+          },
+          {
+            "title": "SSO with Auth0",
+            "path": "secure/authentication/sso-auth0"
+          },
+          {
+            "title": "SSO with Vault",
+            "path": "secure/authentication/sso-vault"
+          },
+          {
+            "title": "SSO with PKCE and private key JWT ",
+            "path": "secure/authentication/sso-pkce-jwt"
+          }
+        ]
+      },
+      {
+        "title": "Traffic encryption",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/traffic"
+          },
+          {
+            "title": "Enable gossip encryption",
+            "path": "secure/traffic/gossip-encryption"
+          },
+          {
+            "title": "Enable TLS",
+            "path": "secure/traffic/tls"
+          }
+        ]
+      },
+      {
+        "title": "Vault",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/vault"
+          },
+          {
+            "title": "ACL",
+            "path": "secure/vault/acl"
+          }
+        ]
+      },
+      {
+        "title": "Workload identity",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "secure/workload-identity"
+          },
+          {
+            "title": "Federate AWS Access",
+            "path": "secure/workload-identity/aws-oidc-provider"
+          },
+          {
+            "title": "Federate GCP access",
+            "href": "https://developer.hashicorp.com/nomad/tutorials/fed-workload-identity/integration-gcp"
+          },
+          {
+            "title": "Use workload identities with Vault",
+            "path": "secure/workload-identity/vault"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Upgrade Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific version details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Release notes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "release-notes"
+      },
+      {
+        "title": "Nomad",
+        "routes": [
+          {
+            "title": "Upcoming",
+            "path": "release-notes/nomad/upcoming"
+          },
+          {
+            "title": "v1.11.x",
+            "path": "release-notes/nomad/v1-11-x"
+          },
+          {
+            "title": "v1.10.x",
+            "path": "release-notes/nomad/v1-10-x"
+          },
+          {
+            "title": "v1.9.x",
+            "path": "release-notes/nomad/v1_9_x"
+          },
+          {
+            "title": "v1.8.x",
+            "path": "release-notes/nomad/v1_8_x"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Agent configuration reference",
+    "href": "https://developer.hashicorp.com/nomad/docs/configuration/"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Jobs"
+  },
+  {
+    "title": "Declare jobs",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-declare"
+      },
+      {
+        "title": "Create a job specification",
+        "path": "job-declare/create-job"
+      },
+      {
+        "title": "Configure tasks",
+        "path": "job-declare/configure-tasks"
+      },
+      {
+        "title": "Create a parameterized job",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/job-specifications/job-spec-parameterized"
+      },
+      {
+        "title": "Use task drivers",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/task-driver"
+          },
+          {
+            "title": "Docker",
+            "path": "job-declare/task-driver/docker"
+          },
+          {
+            "title": "Isolated Fork/Exec",
+            "path": "job-declare/task-driver/exec"
+          },
+          {
+            "title": "Java",
+            "path": "job-declare/task-driver/java"
+          },
+          {
+            "title": "QEMU",
+            "path": "job-declare/task-driver/qemu"
+          },
+          {
+            "title": "Raw Fork/Exec",
+            "path": "job-declare/task-driver/raw_exec"
+          },
+          {
+            "title": "Task driver plugins",
+            "routes": [
+              {
+                "title": "Exec2",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/exec2"
+              },
+              {
+                "title": "Podman",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/podman"
+              },
+              {
+                "title": "Virt <sup>Beta</sup>",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/virt"
+              },
+              {
+                "title": "Community",
+                "href": "https://developer.hashicorp.com/nomad/plugins/drivers/community"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Use device plugins",
+        "href": "https://developer.hashicorp.com/nomad/plugins/devices"
+      },
+      {
+        "title": "Use Consul service mesh",
+        "path": "job-declare/consul-service-mesh"
+      },
+      {
+        "title": "Use Vault",
+        "path": "job-declare/vault"
+      },
+      {
+        "title": "Configure deployment strategies",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/strategy"
+          },
+          {
+            "title": "Configure blue/green and canary",
+            "path": "job-declare/strategy/blue-green-canary"
+          },
+          {
+            "title": "Configure rolling",
+            "path": "job-declare/strategy/rolling"
+          }
+        ]
+      },
+      {
+        "title": "Configure multi-region deployments",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-declare/multiregion"
+      },
+      {
+        "title": "Configure task dependencies",
+        "path": "job-declare/task-dependencies"
+      },
+      {
+        "title": "Use Nomad actions",
+        "path": "job-declare/nomad-actions"
+      },
+      {
+        "title": "Use Nomad variables",
+        "path": "job-declare/nomad-variables"
+      },
+      {
+        "title": "Configure exit signals",
+        "path": "job-declare/exit-signals"
+      },
+      {
+        "title": "Handle failure",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-declare/failure"
+          },
+          {
+            "title": "Local restarts",
+            "path": "job-declare/failure/restart"
+          },
+          {
+            "title": "Health check restarts",
+            "path": "job-declare/failure/check-restart"
+          },
+          {
+            "title": "Reschedule",
+            "path": "job-declare/failure/reschedule"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Run jobs",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-run"
+      },
+      {
+        "title": "Inspect running jobs",
+        "path": "job-run/inspect"
+      },
+      {
+        "title": "Access logs for troubleshooting",
+        "path": "job-run/logs"
+      },
+      {
+        "title": "Collect resource utilization metrics",
+        "path": "job-run/utilization-metrics"
+      },
+      {
+        "title": "Create job versions",
+        "path": "job-run/versions"
+      }
+    ]
+  },
+  {
+    "title": "Stateful workloads",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "stateful-workloads"
+      },
+      {
+        "title": "Use CSI volumes",
+        "path": "stateful-workloads/csi-volumes"
+      },
+      {
+        "title": "Use dynamic host volumes",
+        "path": "stateful-workloads/dynamic-host-volumes"
+      },
+      {
+        "title": "Use static host volumes",
+        "path": "stateful-workloads/static-host-volumes"
+      }
+    ]
+  },
+  {
+    "title": "Workload networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-networking"
+      },
+      {
+        "title": "Service discovery",
+        "path": "job-networking/service-discovery"
+      },
+      {
+        "title": "Use a CNI network",
+        "path": "job-networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Advanced scheduling for efficiency",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-scheduling"
+      },
+      {
+        "title": "Fault tolerance with spread",
+        "path": "job-scheduling/spread"
+      },
+      {
+        "title": "Job placement with affinities",
+        "path": "job-scheduling/affinity"
+      },
+      {
+        "title": "Job priority with preemption",
+        "path": "job-scheduling/preemption"
+      },
+      {
+        "title": "Memory oversubscription",
+        "href": "https://developer.hashicorp.com/nomad/tutorials/advanced-scheduling/memory-oversubscription"
+      }
+    ]
+  },
+  {
+    "title": "Job templates with Nomad Pack",
+    "href": "/tools/nomad-pack/create-packs#write-the-templates"
+  },
+  {
+    "title": "Job specification reference",
+    "href": "https://developer.hashicorp.com/nomad/docs/job-specification/"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Enterprise solutions"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Features",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "Automated license utilization reporting",
+            "path": "enterprise/license/utilization-reporting"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Nomad ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad partnerships",
+    "path": "partnerships"
+  },
+  {
+    "divider": "true"
+  },
+  {
+    "heading": "Reference docs"
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "title": "Agent configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "keyring",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "configuration/keyring"
+          },
+          {
+            "title": "AWS KMS",
+            "path": "configuration/keyring/awskms"
+          },
+          {
+            "title": "Azure Key Vault",
+            "path": "configuration/keyring/azurekeyvault"
+          },
+          {
+            "title": "GCP Cloud KMS",
+            "path": "configuration/keyring/gcpckms"
+          },
+          {
+            "title": "Vault Transit",
+            "path": "configuration/keyring/transit"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "reporting",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/reporting"
+      },
+      {
+        "title": "rpc",
+        "path": "configuration/rpc"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "sentinel",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Job specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "action",
+        "path": "job-specification/action"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "consul",
+        "path": "job-specification/consul"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "disconnect",
+        "path": "job-specification/disconnect"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "numa",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/numa"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "schedule",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "job-specification/schedule"
+      },
+      {
+        "title": "secret",
+        "path": "job-specification/secret"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "transparent_proxy",
+        "path": "job-specification/transparent_proxy"
+      },
+      {
+        "title": "ui",
+        "path": "job-specification/ui"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Nomad object specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Resource quota",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "other-specifications/quota"
+      },
+      {
+        "title": "Nomad variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "CSI",
+            "path": "other-specifications/volume/csi"
+          },
+          {
+            "title": "Dynamic host volumes",
+            "path": "other-specifications/volume/host"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Reference",
+    "routes": [
+      {
+        "title": "Metrics",
+        "path": "reference/metrics"
+      },
+      {
+        "title": "Runtime environment settings",
+        "path": "reference/runtime-environment-settings"
+      },
+      {
+        "title": "Runtime variable interpolation",
+        "path": "reference/runtime-variable-interpolation"
+      },
+      {
+        "title": "Web UI keyboard shortcuts",
+        "path": "reference/keyboard-commands"
+      },
+      {
+        "title": "Sentinel policy",
+        "badge": {
+          "text": "ENT",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "reference/sentinel-policy"
+      },
+      {
+        "title": "Go template syntax",
+        "path": "reference/go-template-syntax"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "reference/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "reference/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "reference/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "reference/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "reference/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "reference/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "reference/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "reference/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "reference/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "reference/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "reference/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "reference/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "reference/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "reference/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "reference/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "reference/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "reference/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "reference/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "reference/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "reference/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "reference/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "reference/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "reference/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "reference/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "reference/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "reference/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "reference/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "reference/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "reference/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "reference/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "reference/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "reference/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "reference/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "reference/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "reference/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "reference/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "reference/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "reference/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "reference/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "reference/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "reference/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "reference/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "reference/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "reference/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "reference/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "reference/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "reference/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "reference/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "reference/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "reference/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "reference/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "reference/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "reference/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "reference/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "reference/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "reference/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "reference/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "reference/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "reference/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "reference/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "reference/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "reference/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "reference/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "reference/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "reference/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "reference/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "reference/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "reference/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "reference/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "reference/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "reference/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "reference/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "reference/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "reference/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "reference/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "reference/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "reference/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "reference/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "reference/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "reference/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "reference/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "reference/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "reference/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "reference/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "reference/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "reference/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "reference/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "reference/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "reference/hcl2/variables"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.11.x/data/intro-nav-data.json b/content/nomad/v1.11.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..749e6ff77f
--- /dev/null
+++ b/content/nomad/v1.11.x/data/intro-nav-data.json
@@ -0,0 +1,6 @@
+[
+  {
+    "title": "What is Nomad?",
+    "href": "/docs/what-is-nomad"
+  }
+]
diff --git a/content/nomad/v1.11.x/data/plugins-nav-data.json b/content/nomad/v1.11.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..5ca7133fc3
--- /dev/null
+++ b/content/nomad/v1.11.x/data/plugins-nav-data.json
@@ -0,0 +1,141 @@
+[
+  {
+    "title": "Task drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Exec2",
+        "path": "drivers/exec2"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Virt",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/virt"
+          },
+          {
+            "title": "Install",
+            "path": "drivers/virt/install"
+          },
+          {
+            "title": "Task config",
+            "path": "drivers/virt/task-config"
+          }
+        ]
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "https://github.com/Roblox/nomad-driver-containerd"
+          },
+          {
+            "title": "Pledge",
+            "href": "https://github.com/shoenig/nomad-pledge-driver"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "https://github.com/cneira/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "href": "https://github.com/cneira/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "https://docs.lightrun.com/integrations/nomad/"
+          },
+          {
+            "title": "Pot",
+            "href": "https://github.com/bsdpot/nomad-pot-driver"
+          },
+          {
+            "title": "Rookout",
+            "href": "https://github.com/Rookout/rookout-nomad-driver"
+          },
+          {
+            "title": "Singularity",
+            "href": "https://github.com/hpcng/nomad-driver-singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "https://github.com/JanMa/nomad-driver-nspawn"
+          },
+          {
+            "title": "Windows IIS - Roblox",
+            "href": "https://github.com/Roblox/nomad-driver-iis"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "https://nomad-iis.sevensolutions.cc/"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Devices",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "NVIDIA",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "USB",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "devices/usb"
+      }
+    ]
+  },
+  {
+    "title": "Plugin authoring guide",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "author"
+      },
+      {
+        "title": "Device",
+        "path": "author/device"
+      },
+      {
+        "title": "Host volume",
+        "path": "author/host-volume"
+      },
+      {
+        "title": "Secret provider",
+        "path": "author/secret-provider"
+      },
+      {
+        "title": "Task driver",
+        "path": "author/task-driver"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.11.x/data/tools-nav-data.json b/content/nomad/v1.11.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..31a682842e
--- /dev/null
+++ b/content/nomad/v1.11.x/data/tools-nav-data.json
@@ -0,0 +1,373 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Nomad Autoscaler",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "badge": {
+              "text": "ENT",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "high_availability",
+            "path": "autoscaling/agent/high_availability"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "badge": {
+                  "text": "ENT",
+                  "type": "outlined",
+                  "color": "neutral"
+                },
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Nomad Pack",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-pack"
+      },
+      {
+        "title": "Advanced usage",
+        "path": "nomad-pack/advanced-usage"
+      },
+      {
+        "title": "Create packs",
+        "path": "nomad-pack/create-packs"
+      },
+      {
+        "title": "CLI reference",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "nomad-pack/commands"
+          },
+          {
+            "title": "deps",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/deps"
+              },
+              {
+                "title": "vendor",
+                "path": "nomad-pack/commands/deps/vendor"
+              }
+            ]
+          },
+          {
+            "title": "destroy",
+            "path": "nomad-pack/commands/destroy"
+          },
+          {
+            "title": "generate",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/generate"
+              },
+              {
+                "title": "pack",
+                "path": "nomad-pack/commands/generate/pack"
+              },
+              {
+                "title": "registry",
+                "path": "nomad-pack/commands/generate/registry"
+              },
+              {
+                "title": "var-file",
+                "path": "nomad-pack/commands/generate/var-file"
+              }
+            ]
+          },
+          {
+            "title": "info",
+            "path": "nomad-pack/commands/info"
+          },
+          {
+            "title": "list",
+            "path": "nomad-pack/commands/list"
+          },
+          {
+            "title": "plan",
+            "path": "nomad-pack/commands/plan"
+          },
+          {
+            "title": "registry",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "nomad-pack/commands/registry"
+              },
+              {
+                "title": "add",
+                "path": "nomad-pack/commands/registry/add"
+              },
+              {
+                "title": "delete",
+                "path": "nomad-pack/commands/registry/delete"
+              },
+              {
+                "title": "list",
+                "path": "nomad-pack/commands/registry/list"
+              }
+            ]
+          },
+          {
+            "title": "render",
+            "path": "nomad-pack/commands/render"
+          },
+          {
+            "title": "run",
+            "path": "nomad-pack/commands/run"
+          },
+          {
+            "title": "status",
+            "path": "nomad-pack/commands/status"
+          },
+          {
+            "title": "stop",
+            "path": "nomad-pack/commands/stop"
+          },
+          {
+            "title": "version",
+            "path": "nomad-pack/commands/version"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.11.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.11.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.11.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.11.x/img/autoscaling/control-loop.png b/content/nomad/v1.11.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.11.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.11.x/img/autoscaling/policy-eval.png b/content/nomad/v1.11.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.11.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/active-alert.png b/content/nomad/v1.11.x/img/clusters/active-alert.png
new file mode 100644
index 0000000000..15baa8b333
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/active-alert.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/alertmanager-webui.png b/content/nomad/v1.11.x/img/clusters/alertmanager-webui.png
new file mode 100644
index 0000000000..c2d7b33385
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/alertmanager-webui.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/alerts.png b/content/nomad/v1.11.x/img/clusters/alerts.png
new file mode 100644
index 0000000000..5bc5e15333
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/alerts.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/cannot-fetch-logs.png b/content/nomad/v1.11.x/img/clusters/cannot-fetch-logs.png
new file mode 100644
index 0000000000..c781b60a5b
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/cannot-fetch-logs.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/cannot-remote-exec.png b/content/nomad/v1.11.x/img/clusters/cannot-remote-exec.png
new file mode 100644
index 0000000000..8cfff1e819
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/cannot-remote-exec.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/chrome-pending.png b/content/nomad/v1.11.x/img/clusters/chrome-pending.png
new file mode 100644
index 0000000000..fa5b18d11c
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/chrome-pending.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/chrome-timeout.png b/content/nomad/v1.11.x/img/clusters/chrome-timeout.png
new file mode 100644
index 0000000000..2a5aa3b7c1
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/chrome-timeout.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/firefox-pending.png b/content/nomad/v1.11.x/img/clusters/firefox-pending.png
new file mode 100644
index 0000000000..168022409e
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/firefox-pending.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/firefox-timeout.png b/content/nomad/v1.11.x/img/clusters/firefox-timeout.png
new file mode 100644
index 0000000000..db192125ce
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/firefox-timeout.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/new-targets.png b/content/nomad/v1.11.x/img/clusters/new-targets.png
new file mode 100644
index 0000000000..a535407eeb
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/new-targets.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/nomad-multi-region.png b/content/nomad/v1.11.x/img/clusters/nomad-multi-region.png
new file mode 100644
index 0000000000..448e87f475
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/nomad-multi-region.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/prometheus-targets.png b/content/nomad/v1.11.x/img/clusters/prometheus-targets.png
new file mode 100644
index 0000000000..79a92169fe
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/prometheus-targets.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/running-jobs.png b/content/nomad/v1.11.x/img/clusters/running-jobs.png
new file mode 100644
index 0000000000..11d64198b8
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/running-jobs.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/safari-pending.png b/content/nomad/v1.11.x/img/clusters/safari-pending.png
new file mode 100644
index 0000000000..4cae311361
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/safari-pending.png differ
diff --git a/content/nomad/v1.11.x/img/clusters/safart-timeout.png b/content/nomad/v1.11.x/img/clusters/safart-timeout.png
new file mode 100644
index 0000000000..925ccf691c
Binary files /dev/null and b/content/nomad/v1.11.x/img/clusters/safart-timeout.png differ
diff --git a/content/nomad/v1.11.x/img/consul-integration-auth-method.png b/content/nomad/v1.11.x/img/consul-integration-auth-method.png
new file mode 100644
index 0000000000..485cb5d6ac
Binary files /dev/null and b/content/nomad/v1.11.x/img/consul-integration-auth-method.png differ
diff --git a/content/nomad/v1.11.x/img/consul-integration-wi.png b/content/nomad/v1.11.x/img/consul-integration-wi.png
new file mode 100644
index 0000000000..b20fcc3863
Binary files /dev/null and b/content/nomad/v1.11.x/img/consul-integration-wi.png differ
diff --git a/content/nomad/v1.11.x/img/consul-integration-wid-acl-token.png b/content/nomad/v1.11.x/img/consul-integration-wid-acl-token.png
new file mode 100644
index 0000000000..bfb587564b
Binary files /dev/null and b/content/nomad/v1.11.x/img/consul-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.11.x/img/count-dashboard.png b/content/nomad/v1.11.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.11.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.11.x/img/deploy/nomad_fault_tolerance.png b/content/nomad/v1.11.x/img/deploy/nomad_fault_tolerance.png
new file mode 100644
index 0000000000..dcac5802a3
Binary files /dev/null and b/content/nomad/v1.11.x/img/deploy/nomad_fault_tolerance.png differ
diff --git a/content/nomad/v1.11.x/img/deploy/nomad_network_arch.png b/content/nomad/v1.11.x/img/deploy/nomad_network_arch.png
new file mode 100644
index 0000000000..554d0b85e1
Binary files /dev/null and b/content/nomad/v1.11.x/img/deploy/nomad_network_arch.png differ
diff --git a/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1x.png b/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1x.png
new file mode 100644
index 0000000000..6f43b5ce16
Binary files /dev/null and b/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1x.png differ
diff --git a/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1y.png b/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1y.png
new file mode 100644
index 0000000000..9001f17651
Binary files /dev/null and b/content/nomad/v1.11.x/img/deploy/nomad_network_arch_0-1y.png differ
diff --git a/content/nomad/v1.11.x/img/deploy/nomad_reference_diagram.png b/content/nomad/v1.11.x/img/deploy/nomad_reference_diagram.png
new file mode 100644
index 0000000000..b6e7ea2894
Binary files /dev/null and b/content/nomad/v1.11.x/img/deploy/nomad_reference_diagram.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.11.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.11.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.11.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/favicon-16x16.png b/content/nomad/v1.11.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/favicon-194x194.png b/content/nomad/v1.11.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/favicon-32x32.png b/content/nomad/v1.11.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/favicon.ico b/content/nomad/v1.11.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.11.x/img/favicons/mstile-144x144.png b/content/nomad/v1.11.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/mstile-150x150.png b/content/nomad/v1.11.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/mstile-310x150.png b/content/nomad/v1.11.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/mstile-310x310.png b/content/nomad/v1.11.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/mstile-70x70.png b/content/nomad/v1.11.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.11.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.11.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.11.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.11.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.11.x/img/govern/nomad-ui-namespace-dropdown.png b/content/nomad/v1.11.x/img/govern/nomad-ui-namespace-dropdown.png
new file mode 100644
index 0000000000..6a5f534f3a
Binary files /dev/null and b/content/nomad/v1.11.x/img/govern/nomad-ui-namespace-dropdown.png differ
diff --git a/content/nomad/v1.11.x/img/govern/sentinel.jpg b/content/nomad/v1.11.x/img/govern/sentinel.jpg
new file mode 100644
index 0000000000..5ce7fa54b6
Binary files /dev/null and b/content/nomad/v1.11.x/img/govern/sentinel.jpg differ
diff --git a/content/nomad/v1.11.x/img/home-hero-pattern.svg b/content/nomad/v1.11.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.11.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/logo-hashicorp.svg b/content/nomad/v1.11.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.11.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.11.x/img/logo-text.svg b/content/nomad/v1.11.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.11.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempted.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempted.png
new file mode 100644
index 0000000000..b27a4587c9
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempted.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempter.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempter.png
new file mode 100644
index 0000000000..98732b35c8
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-preempter.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-details.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-details.png
new file mode 100644
index 0000000000..a05a0848e1
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-details.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png
new file mode 100644
index 0000000000..8206c0a837
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-reschedule-icon.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-resource-utilization.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-resource-utilization.png
new file mode 100644
index 0000000000..f0b9a7dfd9
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-resource-utilization.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-stop-restart.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-stop-restart.png
new file mode 100644
index 0000000000..8cf7246fa9
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-stop-restart.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png
new file mode 100644
index 0000000000..848613275a
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-alloc-unhealthy-driver.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-allocations.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-allocations.png
new file mode 100644
index 0000000000..244b4ca922
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-allocations.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-attributes.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-attributes.png
new file mode 100644
index 0000000000..f87d1d45fe
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-attributes.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-detail.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-detail.png
new file mode 100644
index 0000000000..28234e93de
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-detail.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-drain.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-drain.png
new file mode 100644
index 0000000000..7ef21066c7
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-drain.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-driver-status.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-driver-status.png
new file mode 100644
index 0000000000..8eb6e6766a
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-driver-status.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-events.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-events.png
new file mode 100644
index 0000000000..0b8c674ac3
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-events.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-resource-utilization.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-resource-utilization.png
new file mode 100644
index 0000000000..4171f9a57b
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-client-resource-utilization.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-filters.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-filters.png
new file mode 100644
index 0000000000..735f339c44
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-filters.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-list.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-list.png
new file mode 100644
index 0000000000..bd76f1600e
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-clients-list.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-definition-edit.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-definition-edit.png
new file mode 100644
index 0000000000..b3cebc245c
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-definition-edit.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-deployment-canary.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-deployment-canary.png
new file mode 100644
index 0000000000..e3007d1814
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-deployment-canary.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-filters.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-filters.png
new file mode 100644
index 0000000000..4746eac662
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-filters.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-stop.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-stop.png
new file mode 100644
index 0000000000..b52c057a0b
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-job-stop.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-periodic-force.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-periodic-force.png
new file mode 100644
index 0000000000..234ae0fda7
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-periodic-force.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-server-detail.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-server-detail.png
new file mode 100644
index 0000000000..31729fb9bd
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-server-detail.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-servers-list.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-servers-list.png
new file mode 100644
index 0000000000..6b13e5b901
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-servers-list.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-events.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-events.png
new file mode 100644
index 0000000000..3369dde69d
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-events.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-logs.png b/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-logs.png
new file mode 100644
index 0000000000..a5f94b3b38
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-img-task-logs.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/guide-ui-jobs-list.png b/content/nomad/v1.11.x/img/monitor/guide-ui-jobs-list.png
new file mode 100644
index 0000000000..5e030aa25d
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/guide-ui-jobs-list.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/inspect-cluster.mdx b/content/nomad/v1.11.x/img/monitor/inspect-cluster.mdx
new file mode 100644
index 0000000000..f5c5e725a6
--- /dev/null
+++ b/content/nomad/v1.11.x/img/monitor/inspect-cluster.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Inspect the cluster
+description: |-
+  View the server and client nodes, inspect an individual server or client node,
+  list allocations, and review client events from the Nomad web UI.
+---
+
+# Inspect the cluster
+
+The Web UI can be a powerful tool for monitoring the state of the Nomad cluster
+from an operator's perspective. This includes showing all client nodes, showing
+driver health for client nodes, driver status, resource utilization, allocations
+by client node, and more.
+
+## View cluster clients
+
+From any page, the Clients List page can be accessed from the left-hand
+navigation bar. On narrow screens this navigation bar may need to be opened from
+the top-right menu button. The table lists every client in the cluster and is
+searchable, sortable, and filterable. Each client row in the table shows basic
+information, such as the Node ID, name, state, address, datacenter, and how many
+allocations are running in it.
+
+This view will also live-update as the states of client nodes change.
+
+[![Clients List][img-clients-list]][img-clients-list]
+
+## Filter the client view
+
+If your Nomad cluster has many client nodes, it can be useful to filter the list
+of all client nodes down to only those matching certain facets. The Web UI has
+three facets you can filter by:
+
+1. **Class:** The node of the client, including a dynamically generated list
+   based on the node class of each client node in the cluster.
+
+1. **State:** The state of the cluster, including Initializing, Ready, Down,
+   Ineligible, and Draining.
+
+1. **Datacenter:** The datacenter the client node is in, including a dynamically
+   generated list based on all the datacenters in the cluster.
+
+[![Clients filters][img-clients-filters]][img-clients-filters]
+
+## Inspect an individual client
+
+From the Clients List page, clicking a client node in the table will direct you
+to the Client Detail page for the client node. This page includes all
+information about the client node is live-updated to always present up-to-date
+information.
+
+[![Client Detail][img-client-detail]][img-client-detail]
+
+## Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for client
+nodes. The Web UI uses these metrics to create time-series graphics for the
+current session.
+
+When viewing a client node, resource utilization will automatically start
+logging.
+
+[![Client Resource Utilization][img-client-resource-utilization]][img-client-resource-utilization]
+
+## List client allocations
+
+Allocations belong to jobs and are placed on client nodes. The Client Detail
+page will list all allocations for a client node, including completed, failed,
+and lost allocations, until they are garbage-collected.
+
+This is presented in a searchable table which can additionally be filtered to
+only preempted allocations.
+
+[![Client Allocations][img-client-allocations]][img-client-allocations]
+
+## Review client events
+
+Client nodes will also emit events on meaningful state changes, such as when the
+node becomes ready for scheduling or when a driver becomes unhealthy.
+
+[![Client Events][img-client-events]][img-client-events]
+
+## Check client driver status
+
+Task drivers are additional services running on a client node. Nomad will
+fingerprint and communicate with the task driver to determine if the driver is
+available and healthy. This information is reported through the Web UI on the
+Client Detail page.
+
+[![Client Driver Status][img-client-driver-status]][img-client-driver-status]
+
+## View client attributes
+
+In order to allow job authors to constrain the placement of their jobs, Nomad
+fingerprints the hardware of the node the client agent is running on. This is a
+deeply nested document of properties that the Web UI presents in a scannable
+way.
+
+In addition to the hardware attributes, Nomad operators can annotate a client
+node with [metadata] as part of the client configuration. This metadata is also
+presented on the Client Detail page.
+
+[![Client Attributes][img-client-attributes]][img-client-attributes]
+
+## Monitor a node drain
+
+A routine part of maintaining a Nomad cluster is draining nodes of allocations.
+This can be in preparation of performing operating system upgrades or
+decommissioning an old node in favor of a new VM.
+
+Drains are [performed from the CLI], but the status of a drain can be monitored
+from the Web UI. A client node will state if it is actively draining or
+ineligible for scheduling.
+
+Since drains can be configured in a variety of ways, the Client Detail page will
+also present the details of how the drain is performed.
+
+[![Client Drain][img-client-drain]][img-client-drain]
+
+## View cluster servers
+
+Whereas client nodes are used to run your jobs, server nodes are used to run
+Nomad and maintain availability. From any page, the Servers List page can be
+accessed from the left-hand navigation bar.
+
+The table lists every server node in your cluster. This will be a small list—
+[typically three or five].
+
+[![Servers List][img-servers-list]][img-servers-list]
+
+## Inspect an individual server
+
+Clicking a server node on the Servers List will expand the tags table for the
+server node.
+
+[![Server Detail][img-server-detail]][img-server-detail]
+
+## Secure the UI
+
+Depending on the size of your team and the details of you Nomad deployment, you
+may wish to control which features different internal users have access to. This
+includes limiting who has access to list and manage client nodes and list and
+manage server nodes. You can enforce this with Nomad's access control list
+system.
+
+By default, all features—read and write—are available to all users of the Web
+UI. Check out the [Securing the Web UI with ACLs] tutorial to learn how to prevent
+anonymous users from having write permissions as well as how to continue to use
+Web UI write features as a privileged user.
+
+## Continue your exploration
+
+Now that you have explored how to inspect the state of your cluster through the
+Nomad UI, you will next learn some considerations you should keep in mind when
+using the Nomad UI.
+
+[img-client-allocations]: /img/nomad/web-ui/guide-ui-img-client-allocations.png
+[img-client-attributes]: /img/nomad/web-ui/guide-ui-img-client-attributes.png
+[img-client-detail]: /img/nomad/web-ui/guide-ui-img-client-detail.png
+[img-client-drain]: /img/nomad/web-ui/guide-ui-img-client-drain.png
+[img-client-driver-status]: /img/nomad/web-ui/guide-ui-img-client-driver-status.png
+[img-client-events]: /img/nomad/web-ui/guide-ui-img-client-events.png
+[img-client-resource-utilization]: /img/nomad/web-ui/guide-ui-img-client-resource-utilization.png
+[img-clients-filters]: /img/nomad/web-ui/guide-ui-img-clients-filters.png
+[img-clients-list]: /img/nomad/web-ui/guide-ui-img-clients-list.png
+[img-server-detail]: /img/nomad/web-ui/guide-ui-img-server-detail.png
+[img-servers-list]: /img/nomad/web-ui/guide-ui-img-servers-list.png
+[metadata]: /nomad/docs/configuration/client#meta
+[performed from the cli]: /nomad/tutorials/manage-clusters/node-drain
+[securing the web ui with acls]: /nomad/tutorials/access-control
+[typically three or five]: /nomad/docs/architecture/consensus#deployment-table
diff --git a/content/nomad/v1.11.x/img/monitor/inspect-workloads.mdx b/content/nomad/v1.11.x/img/monitor/inspect-workloads.mdx
new file mode 100644
index 0000000000..84c49e0d31
--- /dev/null
+++ b/content/nomad/v1.11.x/img/monitor/inspect-workloads.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Inspect job workloads
+description: |-
+  Inspect jobs, allocations, and tasks in the Nomad web UI and interact
+  with these objects to perform operations like restart an allocation or
+  stop a job.
+---
+
+# Inspect job workloads
+
+The Web UI can be a powerful companion when monitoring and debugging jobs
+running in Nomad. The Web UI will list all jobs, link jobs to allocations,
+allocations to client nodes, client nodes to driver health, and much more.
+
+## List jobs
+
+The first page you will arrive at in the Web UI is the Jobs List page. Here you
+will find every job for a namespace in a region. The table of jobs is
+searchable, sortable, and filterable. Each job row in the table shows basic
+information, such as job name, status, type, and priority, as well as richer
+information such as a visual representation of all allocation statuses.
+
+This view will also live-update as jobs get submitted, get purged, and change
+status.
+
+[![Jobs List][img-jobs-list]][img-jobs-list]
+
+## Filter job view
+
+If your Nomad cluster has many jobs, it can be useful to filter the list of all
+jobs down to only those matching certain facets. The Web UI has four facets you
+can filter by:
+
+1. **Type:** The type of job, including Batch, Parameterized, Periodic, Service,
+   and System.
+
+1. **Status:** The status of the job, including Pending, Running, and Dead.
+
+1. **Datacenter:** The datacenter the job is running in, including a dynamically
+   generated list based on the jobs in the namespace.
+
+1. **Prefix:** The possible common naming prefix for a job, including a
+   dynamically generated list based on job names up to the first occurrence of
+   `-`, `.`, and `_`. Only prefixes that match multiple jobs are included.
+
+[![Job Filters][img-job-filters]][img-job-filters]
+
+## Inspect an allocation
+
+In Nomad, allocations are the schedulable units of work. This is where runtime
+metrics begin to surface. An allocation is composed of one or more tasks, and
+the utilization metrics for tasks are aggregated so they can be observed at the
+allocation level.
+
+### Monitor resource utilization
+
+Nomad has APIs for reading point-in-time resource utilization metrics for tasks
+and allocations. The Web UI uses these metrics to create time-series graphs for
+the current session.
+
+When viewing an allocation, resource utilization will automatically start
+logging.
+
+[![Allocation Resource Utilization][img-alloc-resource-utilization]][img-alloc-resource-utilization]
+
+### Review task events
+
+When Nomad places, prepares, and starts a task, a series of task events are
+emitted to help debug issues in the event that the task fails to start.
+
+Task events are listed on the Task Detail page and live-update as Nomad handles
+managing the task.
+
+[![Task Events][img-task-events]][img-task-events]
+
+### View rescheduled allocations
+
+Allocations will be placed on any client node that satisfies the constraints of
+the job definition. There are events, however, that will cause Nomad to
+reschedule allocations, (e.g., node failures).
+
+Allocations can be configured [in the job definition to reschedule] to a
+different client node if the allocation ends in a failed status. This will
+happen after the task has exhausted its [local restart attempts].
+
+The end result of this automatic procedure is a failed allocation and that
+failed allocation's rescheduled successor. Since Nomad handles all of this
+automatically, the Web UI makes sure to explain the state of allocations through
+icons and linking previous and next allocations in a reschedule chain.
+
+[![Allocation Reschedule Icon][img-alloc-reschedule-icon]][img-alloc-reschedule-icon]
+
+[![Allocation Reschedule Details][img-alloc-reschedule-details]][img-alloc-reschedule-details]
+
+### Unhealthy driver
+
+Given the nature of long-lived processes, it's possible for the state of the
+client node an allocation is scheduled on to change during the lifespan of the
+allocation. Nomad attempts to monitor pertinent conditions including driver
+health.
+
+The Web UI denotes when a driver an allocation depends on is unhealthy on the
+client node the allocation is running on.
+
+[![Allocation Unhealthy Driver][img-alloc-unhealthy-driver]][img-alloc-unhealthy-driver]
+
+### Preempted allocations
+
+Much like how Nomad will automatically reschedule allocations, Nomad will
+automatically preempt allocations when necessary. When monitoring allocations in
+Nomad, it's useful to know what allocations were preempted and what job caused
+the preemption.
+
+The Web UI makes sure to tell this full story by showing which allocation caused
+an allocation to be preempted as well as the opposite: what allocations an
+allocation preempted. This makes it possible to traverse down from a job to a
+preempted allocation, to the allocation that caused the preemption, to the job
+that the preempting allocation is for.
+
+[![Allocation Preempter][img-alloc-preempter]][img-alloc-preempter]
+
+[![Allocation Preempted][img-alloc-preempted]][img-alloc-preempted]
+
+## Review task logs
+
+A task will typically emit log information to `stdout` and `stderr`. Nomad
+captures these logs and exposes them through an API. The Web UI uses these APIs
+to offer `head`, `tail`, and streaming logs from the browser.
+
+The Web UI will first attempt to directly connect to the client node the task is
+running on. Typically, client nodes are not accessible from the public internet.
+If this is the case, the Web UI will fall back and proxy to the client node from
+the server node with no loss of functionality.
+
+[![Task Logs][img-task-logs]][img-task-logs]
+
+~> Not all browsers support streaming HTTP requests. In the event that streaming
+is not supported, logs will still be followed using interval polling.
+
+## Restart or stop an allocation or task
+
+Nomad allows for restarting and stopping individual allocations and tasks. When
+a task is restarted, Nomad will perform a local restart of the task. When an
+allocation is stopped, Nomad will mark the allocation as complete and perform a
+reschedule onto a different client node.
+
+Both of these features are also available in the Web UI.
+
+[![Allocation Stop and Restart][img-alloc-stop-restart]][img-alloc-stop-restart]
+
+## Force a periodic instance
+
+Periodic jobs are configured like a cron job. Sometimes, you might want to start
+the job before the its next scheduled run time. Nomad calls this a [periodic
+force] and it can be done from the Web UI on the Job Overview page for a
+periodic job.
+
+[![Periodic Force][img-periodic-force]][img-periodic-force]
+
+## Submit a new version of a job
+
+From the Job Definition page, a job can be edited. After clicking the Edit
+button in the top-right corner of the code window, the job definition JSON
+becomes editable. The edits can then be planned and scheduled.
+
+[![Job Definition Edit][img-job-definition-edit]][img-job-definition-edit]
+
+~> Since each job within a namespace must have a unique name, it is possible to
+submit a new version of a job from the Run Job screen. Always review the plan
+output.
+
+## Monitor a deployment
+
+When a system or service job includes the [`update` stanza], a deployment is
+created upon job submission. Job deployments can be monitored in realtime from
+the Web UI.
+
+The Web UI will show as new allocations become placed, tallying towards the
+expected total, and tally allocations as they become healthy or unhealthy.
+
+Optionally, a job may use canary deployments to allow for additional health
+checks or manual testing before a full roll out. If a job uses canaries and is
+not configured to automatically promote the canary, the canary promotion
+operation can be done from the Job Overview page in the Web UI.
+
+[![Job Deployment with Canary Promotion][img-job-deployment-canary]][img-job-deployment-canary]
+
+## Stop a job
+
+Jobs can be stopped from the Job Overview page. Stopping a job will gracefully
+stop all allocations, marking them as complete, and freeing up resources in the
+cluster.
+
+[![Job Stop][img-job-stop]][img-job-stop]
+
+## Continue your exploration
+
+Now that you have explored operations that can be performed with jobs through
+the Nomad UI, learn how to inspect the state of your cluster using the Nomad UI.
+
+[`update` stanza]: /nomad/docs/job-specification/update
+[img-alloc-preempted]: /img/nomad/web-ui/guide-ui-img-alloc-preempted.png
+[img-alloc-preempter]: /img/nomad/web-ui/guide-ui-img-alloc-preempter.png
+[img-alloc-reschedule-details]: /img/nomad/web-ui/guide-ui-img-alloc-reschedule-details.png
+[img-alloc-reschedule-icon]: /img/nomad/web-ui/guide-ui-img-alloc-reschedule-icon.png
+[img-alloc-resource-utilization]: /img/nomad/web-ui/guide-ui-img-alloc-resource-utilization.png
+[img-alloc-stop-restart]: /img/nomad/web-ui/guide-ui-img-alloc-stop-restart.png
+[img-alloc-unhealthy-driver]: /img/nomad/web-ui/guide-ui-img-alloc-unhealthy-driver.png
+[img-job-definition-edit]: /img/nomad/web-ui/guide-ui-img-job-definition-edit.png
+[img-job-deployment-canary]: /img/nomad/web-ui/guide-ui-img-job-deployment-canary.png
+[img-job-filters]: /img/nomad/web-ui/guide-ui-img-job-filters.png
+[img-job-stop]: /img/nomad/web-ui/guide-ui-img-job-stop.png
+[img-jobs-list]: /img/nomad/web-ui/guide-ui-jobs-list.png
+[img-periodic-force]: /img/nomad/web-ui/guide-ui-img-periodic-force.png
+[img-task-events]: /img/nomad/web-ui/guide-ui-img-task-events.png
+[img-task-logs]: /img/nomad/web-ui/guide-ui-img-task-logs.png
+[in the job definition to reschedule]: /nomad/docs/job-specification/reschedule
+[local restart attempts]: /nomad/docs/job-specification/restart
+[periodic force]: /nomad/commands/job/periodic-force
+[securing the web ui with acls]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/alloc-associations-across-dcs.png b/content/nomad/v1.11.x/img/monitor/topo-viz/alloc-associations-across-dcs.png
new file mode 100644
index 0000000000..3fd762d215
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/alloc-associations-across-dcs.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-associations.png b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-associations.png
new file mode 100644
index 0000000000..0a80af4890
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-associations.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-panel.png b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-panel.png
new file mode 100644
index 0000000000..c278b6ec5a
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-panel.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-tooltip.png b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-tooltip.png
new file mode 100644
index 0000000000..f7b21ae092
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/allocation-tooltip.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/client-panel.png b/content/nomad/v1.11.x/img/monitor/topo-viz/client-panel.png
new file mode 100644
index 0000000000..da4cda160d
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/client-panel.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/client-with-many-allocs.png b/content/nomad/v1.11.x/img/monitor/topo-viz/client-with-many-allocs.png
new file mode 100644
index 0000000000..cc3b763d82
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/client-with-many-allocs.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-panel.png b/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-panel.png
new file mode 100644
index 0000000000..549c5a3bcf
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-panel.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-view.png b/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-view.png
new file mode 100644
index 0000000000..c55fb6cbcc
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/cluster-view.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/empty-clients.png b/content/nomad/v1.11.x/img/monitor/topo-viz/empty-clients.png
new file mode 100644
index 0000000000..95de8d36ea
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/empty-clients.png differ
diff --git a/content/nomad/v1.11.x/img/monitor/topo-viz/topo-viz-link.png b/content/nomad/v1.11.x/img/monitor/topo-viz/topo-viz-link.png
new file mode 100644
index 0000000000..4e560410d6
Binary files /dev/null and b/content/nomad/v1.11.x/img/monitor/topo-viz/topo-viz-link.png differ
diff --git a/content/nomad/v1.11.x/img/networking/bridge.png b/content/nomad/v1.11.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.11.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.11.x/img/networking/docker_bridge.png b/content/nomad/v1.11.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.11.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.11.x/img/networking/port_mapping.png b/content/nomad/v1.11.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.11.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-architecture-global.png b/content/nomad/v1.11.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-architecture-region.png b/content/nomad/v1.11.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-bg-pattern.svg b/content/nomad/v1.11.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.11.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.11.x/img/nomad-bridge-network.png b/content/nomad/v1.11.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-data-model.png b/content/nomad/v1.11.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-evaluation-flow.png b/content/nomad/v1.11.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-kubernetes.png b/content/nomad/v1.11.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-numa.png b/content/nomad/v1.11.x/img/nomad-numa.png
new file mode 100644
index 0000000000..0609d7e196
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-numa.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-panel-learn.svg b/content/nomad/v1.11.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.11.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.11.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.11.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.11.x/img/nomad-pe-cores.png b/content/nomad/v1.11.x/img/nomad-pe-cores.png
new file mode 100644
index 0000000000..e11c011d6e
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-pe-cores.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-ui-block.png b/content/nomad/v1.11.x/img/nomad-ui-block.png
new file mode 100644
index 0000000000..c33ac81cea
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-ui-block.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-vars-leader-election-sdk.png b/content/nomad/v1.11.x/img/nomad-vars-leader-election-sdk.png
new file mode 100644
index 0000000000..a547218579
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-vars-leader-election-sdk.png differ
diff --git a/content/nomad/v1.11.x/img/nomad-workload.png b/content/nomad/v1.11.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.11.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.11.x/img/og-image.png b/content/nomad/v1.11.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.11.x/img/og-image.png differ
diff --git a/content/nomad/v1.11.x/img/pattern.svg b/content/nomad/v1.11.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.11.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/practice-pattern.svg b/content/nomad/v1.11.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.11.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/secure/acl.jpg b/content/nomad/v1.11.x/img/secure/acl.jpg
new file mode 100644
index 0000000000..c892dd3928
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/acl.jpg differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-configure-callback-action.png b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-action.png
new file mode 100644
index 0000000000..60ef05bbdc
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-action.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-configure-callback-flow.png b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-flow.png
new file mode 100644
index 0000000000..74c6343818
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-flow.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-configure-callback-rule.png b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-rule.png
new file mode 100644
index 0000000000..01d3d632b1
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-rule.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-configure-callback-urls.png b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-urls.png
new file mode 100644
index 0000000000..496812fe8a
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-configure-callback-urls.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-configure-user-metadata.png b/content/nomad/v1.11.x/img/secure/auth0-configure-user-metadata.png
new file mode 100644
index 0000000000..6a33389ae5
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-configure-user-metadata.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-create-user.png b/content/nomad/v1.11.x/img/secure/auth0-create-user.png
new file mode 100644
index 0000000000..116bfd6af2
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-create-user.png differ
diff --git a/content/nomad/v1.11.x/img/secure/auth0-get-application-params.png b/content/nomad/v1.11.x/img/secure/auth0-get-application-params.png
new file mode 100644
index 0000000000..6fbb48c471
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/auth0-get-application-params.png differ
diff --git a/content/nomad/v1.11.x/img/secure/nomad-ui-jobs-signed-in.png b/content/nomad/v1.11.x/img/secure/nomad-ui-jobs-signed-in.png
new file mode 100644
index 0000000000..43083d5e8d
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/nomad-ui-jobs-signed-in.png differ
diff --git a/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-button.png b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-button.png
new file mode 100644
index 0000000000..f6a6d53436
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-button.png differ
diff --git a/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-form.png b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-form.png
new file mode 100644
index 0000000000..daf1184a38
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-login-form.png differ
diff --git a/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-signed-in.png b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-signed-in.png
new file mode 100644
index 0000000000..0fca433b82
Binary files /dev/null and b/content/nomad/v1.11.x/img/secure/nomad-ui-oidc-signed-in.png differ
diff --git a/content/nomad/v1.11.x/img/usecase-callout-pattern.svg b/content/nomad/v1.11.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.11.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/usecase-hero-pattern.svg b/content/nomad/v1.11.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.11.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.11.x/img/vault-integration-auth-method.png b/content/nomad/v1.11.x/img/vault-integration-auth-method.png
new file mode 100644
index 0000000000..b6c1d601b9
Binary files /dev/null and b/content/nomad/v1.11.x/img/vault-integration-auth-method.png differ
diff --git a/content/nomad/v1.11.x/img/vault-integration-auth-overview.png b/content/nomad/v1.11.x/img/vault-integration-auth-overview.png
new file mode 100644
index 0000000000..ad26bed43a
Binary files /dev/null and b/content/nomad/v1.11.x/img/vault-integration-auth-overview.png differ
diff --git a/content/nomad/v1.11.x/img/vault-integration-wid-acl-token.png b/content/nomad/v1.11.x/img/vault-integration-wid-acl-token.png
new file mode 100644
index 0000000000..7fd4b406ea
Binary files /dev/null and b/content/nomad/v1.11.x/img/vault-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.11.x/redirects.jsonc b/content/nomad/v1.11.x/redirects.jsonc
new file mode 100644
index 0000000000..0f754b9bb7
--- /dev/null
+++ b/content/nomad/v1.11.x/redirects.jsonc
@@ -0,0 +1,1053 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+
+  /**
+   * /s/* redirects for useful links that need a stable URL but we may need to
+   * change its destination in the future. Some of these used in CLI output.
+   */
+  {
+    "source": "/nomad/s/envoy-bootstrap-error",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/networking/consul/service-mesh#troubleshooting",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/vault-workload-identity-migration",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/v1.8.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/port-plan-failure",
+    "destination": "https://github.com/hashicorp/nomad/issues/9506",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination":
+      "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/vault-integration",
+    "destination": "/nomad/docs/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-integration",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-connect",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/agent/source",
+    "destination": "/nomad/tools/autoscaling/agent/policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/remote/:slug*",
+    "destination": "nomad/plugins/drivers/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/community/lxc",
+    "destination": "/nomad/plugins/drivers/community/",
+    "permanent": true,
+  },
+  // CSI plugins moved under new storage path alongside new host volume plugins
+  {
+    "source": "/nomad/docs/concepts/plugins/csi",
+    "destination": "/nomad/docs/concepts/plugins/storage/csi",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/client",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/installation",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/devices",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community/usb",
+    "destination": "/nomad/plugins/devices/usb",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/containerd",
+    "destination": "https://github.com/Roblox/nomad-driver-containerd",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/pledge",
+    "destination": "https://github.com/shoenig/nomad-pledge-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/firecracker-task-driver",
+    "destination": "https://github.com/cneira/firecracker-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/jail-task-driver",
+    "destination": "https://github.com/cneira/jail-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/lightrun",
+    "destination": "https://docs.lightrun.com/integrations/nomad/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/pot",
+    "destination": "https://github.com/bsdpot/nomad-pot-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/rookout",
+    "destination": "https://github.com/Rookout/rookout-nomad-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/singularity",
+    "destination": "https://github.com/hpcng/nomad-driver-singularity",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/nspawn",
+    "destination": "https://github.com/JanMa/nomad-driver-nspawn",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/iis",
+    "destination": "https://github.com/Roblox/nomad-driver-iis",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/drivers/community/nomad-iis",
+    "destination": "https://nomad-iis.sevensolutions.cc/",
+    "permanent": true,
+  },
+  /**
+   * Nomad IA redirects
+   */
+  {
+    "source": "/nomad/intro",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/intro/use-cases",
+    "destination": "/nomad/docs/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/intro/vs/:path*",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/nomad-vs-kubernetes/:path*",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/quickstart",
+    "destination": "/nomad/docs/quickstart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/windows-service",
+    "destination": "/nomad/docs/deploy/production/windows-service",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/install/production/:path*",
+    "destination": "/nomad/docs/deploy/production/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/architecture",
+    "destination": "/nomad/docs/architecture",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/architecture/federation",
+    "destination": "/nomad/docs/architecture/cluster/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl",
+    "destination": "/nomad/docs/secure/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/architecture/acl",
+    "destination": "/nomad/docs/secure/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/consensus",
+    "destination": "/nomad/docs/architecture/cluster/consensus",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/cpu",
+    "destination": "/nomad/docs/architecture/cpu",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/gossip",
+    "destination": "/nomad/docs/architecture/security/gossip",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/node-pools",
+    "destination": "/nomad/docs/architecture/cluster/node-pools",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/security",
+    "destination": "/nomad/docs/architecture/security",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/stateful-workloads",
+    "destination": "/nomad/docs/architecture/storage/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/storage/:path*",
+    "destination": "/nomad/docs/architecture/storage/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/job-specification/hcl2/:path*",
+    "destination": "/nomad/docs/reference/hcl2/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/metrics-reference",
+    "destination": "/nomad/docs/reference/metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime",
+    "destination": "/nomad/docs/reference/runtime-environment-settings",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime/environment",
+    "destination": "/nomad/docs/reference/runtime-environment-settings",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/runtime/interpolation",
+    "destination": "/nomad/docs/reference/runtime-variable-interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/enterprise/sentinel",
+    "destination": "/nomad/docs/reference/sentinel-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/drivers/:path*",
+    "destination": "/nomad/docs/deploy/task-driver/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/nomad-agent",
+    "destination": "/nomad/docs/deploy/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/federation",
+    "destination": "/nomad/docs/deploy/clusters/federation-considerations",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/federation/failure",
+    "destination": "/nomad/docs/deploy/clusters/federation-failure-scenarios",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/garbage-collection",
+    "destination": "/nomad/docs/manage/garbage-collection",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/key-management",
+    "destination": "/nomad/docs/manage/key-management",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/benchmarking",
+    "destination": "/nomad/docs/scale/benchmarking",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/scheduling/scheduling",
+    "destination": "/nomad/docs/concepts/scheduling/how-scheduling-works",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/schedulers",
+    "destination": "/nomad/docs/concepts/scheduling/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/ipv6-support",
+    "destination": "/nomad/docs/networking/ipv6",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/monitoring-nomad",
+    "destination": "/nomad/docs/monitor",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl/auth-methods/oidc",
+    "destination": "/nomad/docs/secure/authentication/oidc",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/acl/auth-methods/jwt",
+    "destination": "/nomad/docs/secure/authentication/jwt",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/operations/aws-oidc-provider",
+    "destination": "/nomad/docs/secure/workload-identity/aws-oidc-provider",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/who-uses-nomad",
+    "destination": "/nomad/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/networking/service-mesh",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul",
+    "destination": "/nomad/docs/networking/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul/acl",
+    "destination": "/nomad/docs/secure/acl/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul/service-mesh",
+    "destination": "/nomad/docs/networking/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/vault/:path*",
+    "destination": "/nomad/docs/secure/vault/:path*",
+    "permanent": true,
+  },
+  // section index pages no longer in existence
+  {
+    "source": "/nomad/docs/operations",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts",
+    "destination": "/nomad/docs",
+    "permanent": true,
+  },
+  /* redirects for versioned docs in 1.9, 1.8 */
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/what-is-nomad/",
+    "destination": "/nomad/docs/what-is-nomad",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/quickstart/",
+    "destination": "/nomad/docs/:version/install/quickstart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/",
+    "destination": "/nomad/docs/:version/concepts/architecture",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/consensus/",
+    "destination": "/nomad/docs/:version/concepts/consensus",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/federation/",
+    "destination": "/nomad/docs/:version/concepts/architecture/federation",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cluster/node-pools/",
+    "destination": "/nomad/docs/:version/concepts/node-pools",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/cpu/",
+    "destination": "/nomad/docs/:version/concepts/cpu",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/security/",
+    "destination": "/nomad/docs/:version/concepts/security",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/security/gossip/",
+    "destination": "/nomad/docs/:version/concepts/gossip",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/architecture/storage/:slug*",
+    "destination": "/nomad/docs/:version/concepts/plugins/storage/:slug*",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/concepts/scheduling/how-scheduling-works/",
+    "destination": "/nomad/docs/:version/concepts/scheduling/scheduling",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/concepts/scheduling/schedulers/",
+    "destination": "/nomad/docs/:version/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/intro/use-cases/",
+    "destination": "/nomad/docs/use-cases",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/:slug*",
+    "destination": "/nomad/docs/:version/install/:slug*",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/production/windows-service/",
+    "destination": "/nomad/docs/:version/install/windows-service",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/nomad-agent/",
+    "destination": "/nomad/docs/:version/operations/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federation-considerations/",
+    "destination": "/nomad/docs/:version/operations/federation",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federation-failure-scenarios/",
+    "destination": "/nomad/docs/:version/operations/federation/failure",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/task-driver/:slug*",
+    "destination": "/nomad/docs/:version/drivers/:slug*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/",
+    "destination": "/nomad/docs/:version/integrations",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/garbage-collection/",
+    "destination": "/nomad/docs/:version/operations/garbage-collection",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/key-management/",
+    "destination": "/nomad/docs/:version/operations/key-management",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/",
+    "destination": "/nomad/docs/:version/operations/monitoring-nomad",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/service-mesh/",
+    "destination": "/nomad/docs/:version/networking/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/",
+    "destination": "/nomad/docs/:version/integrations/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/consul/",
+    "destination": "/nomad/docs/:version/integrations/consul/acl",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/networking/consul/service-mesh/",
+    "destination": "/nomad/docs/:version/integrations/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/scale/benchmarking/",
+    "destination": "/nomad/docs/:version/operations/benchmarking",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/jwt/",
+    "destination": "/nomad/docs/:version/concepts/acl/auth-methods/jwt",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/oidc/",
+    "destination": "/nomad/docs/:version/concepts/acl/auth-methods/oidc",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/",
+    "destination": "/nomad/docs/:version/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/",
+    "destination": "/nomad/docs/:version/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/vault/acl/",
+    "destination": "/nomad/docs/:version/integrations/vault/acl",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/workload-identity/aws-oidc-provider/",
+    "destination": "/nomad/docs/:version/operations/aws-oidc-provider",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/task-driver/",
+    "destination": "/nomad/docs/:version/drivers",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/hcl2/",
+    "destination": "/nomad/docs/:version/job-specification/hcl2",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/metrics/",
+    "destination": "/nomad/docs/:version/operations/metrics-reference",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-settings/",
+    "destination": "/nomad/docs/:version/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-variable-interpolation/",
+    "destination": "/nomad/docs/:version/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/sentinel-policy/",
+    "destination": "/nomad/docs/:version/enterprise/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/use-cases/",
+    "destination": "/nomad/docs/:version/who-uses-nomad",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-variables/",
+    "destination": "/nomad/docs/:version/runtime/",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/runtime-environment-settings/",
+    "destination": "/nomad/docs/:version/runtime",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/",
+    "destination": "/nomad/tutorials/archive/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/bootstrap/",
+    "destination": "/nomad/tutorials/archive/access-control-bootstrap",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/policies/create-policy/",
+    "destination": "/nomad/tutorials/archive/access-control-create-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/policies/",
+    "destination": "/nomad/tutorials/archive/access-control-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/",
+    "destination": "/nomad/tutorials/archive/access-control-tokens",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-auth0/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-auth0",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-pkce-jwt/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-keycloak",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/vault/",
+    "destination": "/nomad/tutorials/archive/vault-nomad-secrets",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/",
+    "destination": "/nomad/tutorials/archive/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/affinity/",
+    "destination": "/nomad/tutorials/archive/affinity",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/preemption/",
+    "destination": "/nomad/tutorials/archive/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-scheduling/spread/",
+    "destination": "/nomad/tutorials/archive/spread",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/",
+    "destination": "/nomad/tutorials/archive/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/resource-quotas/",
+    "destination": "/nomad/tutorials/archive/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/sentinel/",
+    "destination": "/nomad/tutorials/archive/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/event-stream/",
+    "destination": "/nomad/tutorials/archive/event-stream",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/workload-identity/vault-acl/",
+    "destination": "/nomad/tutorials/archive/vault-acl",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/acl/tokens/vault/",
+    "destination": "/nomad/tutorials/archive/vault-nomad-secrets",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/",
+    "destination": "/nomad/tutorials/archive/failures",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/check-restart/",
+    "destination": "/nomad/tutorials/archive/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/reschedule/",
+    "destination": "/nomad/tutorials/archive/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/failure/restart/",
+    "destination": "/nomad/tutorials/archive/failures-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/nomad-actions/",
+    "destination": "/nomad/tutorials/archive/job-spec-actions",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/blue-green-canary/",
+    "destination":
+      "/nomad/tutorials/archive/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/rolling/",
+    "destination": "/nomad/tutorials/archive/job-rolling-update",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/exit-signals/",
+    "destination": "/nomad/tutorials/archive/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/strategy/",
+    "destination": "/nomad/tutorials/archive/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/autopilot/",
+    "destination": "/nomad/tutorials/archive/autopilot",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/connect-nodes/",
+    "destination": "/nomad/tutorials/archive/clustering",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/federate-regions/",
+    "destination": "/nomad/tutorials/archive/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/multiregion/",
+    "destination": "/nomad/tutorials/archive/multiregion-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/govern/namespaces/",
+    "destination": "/nomad/tutorials/archive/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/migrate-workloads/",
+    "destination": "/nomad/tutorials/archive/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/outage-recovery/",
+    "destination": "/nomad/tutorials/archive/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/deploy/clusters/reverse-proxy-ui/",
+    "destination": "/nomad/tutorials/archive/reverse-proxy-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/",
+    "destination": "/nomad/tutorials/archive/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/logs/",
+    "destination": "/nomad/tutorials/archive/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/configure-tasks/",
+    "destination": "/nomad/tutorials/archive/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/inspect/",
+    "destination": "/nomad/tutorials/archive/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/create-job/",
+    "destination": "/nomad/tutorials/archive/jobs-submit",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/utilization-metrics/",
+    "destination": "/nomad/tutorials/archive/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-run/versions/",
+    "destination": "/nomad/tutorials/archive/jobs-version",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/advanced-usage/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-detailed-usage",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-intro",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)s/nomad-pack/create-packs/",
+    "destination": "/nomad/tutorials/archive/nomad-pack-writing-packs",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)archiving b/c LXC plugin removed a while ago/",
+    "destination": "/nomad/tutorials/archive/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/authentication/sso-vault/",
+    "destination": "/nomad/tutorials/archive/sso-oidc-vault",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/static-host-volumes/",
+    "destination": "/nomad/tutorials/archive/exec-users-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/csi-volumes/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads-csi-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/dynamic-host-volumes/",
+    "destination":
+      "/nomad/tutorials/archive/stateful-workloads-dynamic-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/stateful-workloads/static-host-volumes/",
+    "destination": "/nomad/tutorials/archive/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/task-dependencies/",
+    "destination": "/nomad/tutorials/archive/task-dependencies-interjob",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/manage/format-cli-output/",
+    "destination": "/nomad/tutorials/archive/format-output-with-templates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/reference/go-template-syntax/",
+    "destination": "/nomad/tutorials/archive/go-template-syntax",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/",
+    "destination": "/nomad/tutorials/archive/security-concepts",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/tls/",
+    "destination": "/nomad/tutorials/archive/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/secure/traffic/gossip-encryption/",
+    "destination": "/nomad/tutorials/archive/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/job-declare/nomad-variables/",
+    "destination": "/nomad/tutorials/archive/variables-tasks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/cluster-topology/",
+    "destination": "/nomad/tutorials/archive/topology-visualization",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/inspect-cluster/",
+    "destination": "/nomad/tutorials/archive/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/monitor/inspect-workloads/",
+    "destination": "/nomad/tutorials/archive/web-ui-workload-info",
+    "permanent": true,
+  },
+  // Move content to new plugin authoring guide
+  {
+    "source": "/nomad/docs/concepts/plugins",
+    "destination": "/nomad/plugins/author",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/base",
+    "destination": "/nomad/plugins/author",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/task-drivers",
+    "destination": "/nomad/plugins/author/task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/devices",
+    "destination": "/nomad/plugins/author/device",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/concepts/plugins/cni",
+    "destination": "/nomad/docs/networking/cni",
+    "permanent": true,
+  },
+  /* commands redirects grouped together */
+  {
+    "source": "/nomad/docs/commands/:path*",
+    "destination": "/nomad/commands/:path*",
+    "permanent": true,
+  },
+  /* redirect incoming nomad/docs/v1.8.x/commands to
+   * new /commands path in 1.9, 1.8
+   */
+  {
+    "source": "/nomad/docs/:version(v1\\.(?:8|9)\\.x)/commands/:path*",
+    "destination": "/nomad/commands/:version/:path*",
+    "permanent": true,
+  },
+  /* redirects to commands prior to version 1.8 for version pick list entries */
+  {
+    "source": "/nomad/commands/:version(v1\\.(?:7|6|5|4|3|2|1|0)\\.x)/:path*",
+    "destination": "/nomad/docs/:version/commands/:path*",
+    "permanent": true,
+  },
+  // redirects for v0.11.x, 0.12.x
+  {
+    "source": "/nomad/commands/:version(v0\\.(?:11|12)\\.x)/:path*",
+    "destination": "/nomad/docs/:version/commands/:path*",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.2.x/content/api-docs/acl-policies.mdx b/content/nomad/v1.2.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..f51e7aeec5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,167 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/acl-tokens.mdx b/content/nomad/v1.2.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..acdf03f7a7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,430 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](https://learn.hashicorp.com/tutorials/nomad/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/agent.mdx b/content/nomad/v1.2.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..db51a4a7f0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/agent.mdx
@@ -0,0 +1,928 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "protocol_version_max": "3",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "protocol_version": "1",
+      "protocol_version_min": "0",
+      "snapshot_version_min": "0",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /docs/configuration/server#num_schedulers
diff --git a/content/nomad/v1.2.x/content/api-docs/allocations.mdx b/content/nomad/v1.2.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..c9262192cd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/allocations.mdx
@@ -0,0 +1,826 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:3.2"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:3.2"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/client.mdx b/content/nomad/v1.2.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..1841fbc325
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/client.mdx
@@ -0,0 +1,670 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/deployments.mdx b/content/nomad/v1.2.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..a608ab357d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/deployments.mdx
@@ -0,0 +1,553 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter.
+
+- `namespace` `(string: "default")` - Specifies the target
+  namespace. Specifying `*` will return all evaluations across all
+  authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/evaluations.mdx b/content/nomad/v1.2.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..ab78127eae
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,288 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target
+  namespace. Specifying `*` will return all evaluations across all
+  authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Priority": 50,
+  "Type": "service",
+  "TriggeredBy": "job-register",
+  "JobID": "example",
+  "JobModifyIndex": 52,
+  "NodeID": "",
+  "NodeModifyIndex": 0,
+  "Status": "complete",
+  "StatusDescription": "",
+  "Wait": 0,
+  "NextEval": "",
+  "PreviousEval": "",
+  "BlockedEval": "",
+  "FailedTGAllocs": null,
+  "ClassEligibility": null,
+  "EscapedComputedClass": false,
+  "AnnotatePlan": false,
+  "SnapshotIndex": 53,
+  "QueuedAllocations": {
+    "cache": 0
+  },
+  "CreateIndex": 53,
+  "ModifyIndex": 55
+}
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/events.mdx b/content/nomad/v1.2.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..5cf0b0cdfa
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/events.mdx
@@ -0,0 +1,389 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object. 
+Note that each JSON object may include multiple events (high server activity) or no 
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management 
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock": "true",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "mock_driver": {
+              "Attributes": {
+                "driver.mock": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445193068-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/index.mdx b/content/nomad/v1.2.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..5f5cf579fe
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/index.mdx
@@ -0,0 +1,217 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.2.x/content/api-docs/jobs.mdx b/content/nomad/v1.2.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..46cbabf428
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2285 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:3.2",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:3.2",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:3.2"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `idempotency_token` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.2.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..b6386d9ff1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1158 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /docs/commands/job/inspect
+[job-output]: /docs/commands/job/run#output
+[job-parse]: /api-docs/jobs#parse-job
+[job-run-json]: /docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad
+$ nomad job run -output example.nomad
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "image": "redis:3.2",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Id": "",
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": ""
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /docs/commands/node/drain
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v1.2.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.2.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..0f3738ffc7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.2.x/content/api-docs/metrics.mdx b/content/nomad/v1.2.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..ae0dbd6597
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/namespaces.mdx b/content/nomad/v1.2.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..882a279a4b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,185 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 31,
+    "Description": "Production API Servers",
+    "ModifyIndex": 31,
+    "Name": "api-prod",
+    "Quota": ""
+  },
+  {
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 5,
+    "Name": "default",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 31,
+  "Description": "Production API Servers",
+  "Quota": "",
+  "Hash": "N8WvePwqkp6J354eLJMKyhvsFdPELAos0VuBfMoVKoU=",
+  "ModifyIndex": 31,
+  "Name": "api-prod"
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Quota": "prod-quota"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/nodes.mdx b/content/nomad/v1.2.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..7c234b623d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1125 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.2.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..62449d1f28
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/index.mdx b/content/nomad/v1.2.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..924b79515c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](https://learn.hashicorp.com/tutorials/nomad/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/license.mdx b/content/nomad/v1.2.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..d03e22290b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.2.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..6be1441363
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /docs/concepts/consensus
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.2.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..c09907c7fa
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,165 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "ModifyIndex": 5,
+    "SchedulerAlgorithm": "spread",
+    "MemoryOversubscriptionEnabled": true,
+    "RejectJobRegistration": false,
+    "PreemptionConfig": {
+      "SystemSchedulerEnabled": true,
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler binpacks or spreads allocations on available nodes.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When `true`, tasks may exceed their reserved memory limit, if the client has excess memory capacity. Tasks must specify [`memory_max`](/docs/job-specification/resources#memory_max) to take advantage of memory oversubscription.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When `true`, tasks may exceed their reserved memory limit, if the client has excess memory capacity. Tasks must specify [`memory_max`](/docs/job-specification/resources#memory_max) to take advantage of memory oversubscription.
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return permission denied errors for job registration, job dispatch, and job scale APIs, unless the ACL token for the request is a management token. If ACLs are disabled, no user will be able to register jobs. This allows operators to shed load from automated proceses during incident response.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.2.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.2.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..81b56fd9a9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.2.x/content/api-docs/plugins.mdx b/content/nomad/v1.2.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..baabbe9f56
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/plugins.mdx
@@ -0,0 +1,137 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/quotas.mdx b/content/nomad/v1.2.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..edeed1de87
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/quotas.mdx
@@ -0,0 +1,352 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/recommendations.mdx b/content/nomad/v1.2.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..401458f896
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/regions.mdx b/content/nomad/v1.2.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..a7896d66c7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.2.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..877c2f6793
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/search.mdx b/content/nomad/v1.2.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..aa967f5fb5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/search.mdx
@@ -0,0 +1,589 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given search
+term and context, where a context can be jobs, allocations, nodes, plugins, or namespaces.
+Additionally, fuzzy searching can be done across all contexts. For better control
+over the performance implications of fuzzy searching on Nomad servers, aspects of
+fuzzy searching can be tuned through the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs, namespace:csi-list-plugin` |
+
+When ACLs are enabled, requests must have a token valid for `node:read`, `plugin:read` or
+`namespace:read-jobs` roles. If the token is only valid for a portion of these
+capabilities, then results will include results including only data readable with
+the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "plugins", or
+  "all", where "all" means every context will be searched. When "all" is selected,
+  additional prefix matches will be included for the "deployments", "evals", and
+  "volumes" types. When searching in the "jobs" context, results that fuzzy match
+  "groups", "services", "tasks", "images", "commands", and "classes" are also
+  included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /docs/configuration/search
diff --git a/content/nomad/v1.2.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.2.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..c1c8ca5166
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries), [consistency modes](/api-docs#consistency-modes) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/status.mdx b/content/nomad/v1.2.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..6c0ca27dc4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/system.mdx b/content/nomad/v1.2.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..2b6c6aa644
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/ui.mdx b/content/nomad/v1.2.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..675ffd4911
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/ui.mdx
@@ -0,0 +1,555 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
diff --git a/content/nomad/v1.2.x/content/api-docs/validate.mdx b/content/nomad/v1.2.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..d01eef2685
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to a server. In the event a server can't be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.2.x/content/api-docs/volumes.mdx b/content/nomad/v1.2.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..7f8db7418f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/api-docs/volumes.mdx
@@ -0,0 +1,757 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:3.2"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/api-docs#blocking-queries) and
+[required ACLs](/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+- `secrets` `(string: "")` - Specifies a list of key/value secrets for listing snapshots.
+  These key/value pairs are comma-separated and are passed directly to the CSI plugin.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2& \
+    secrets=secret-key-1=secret-value-1,secret-key-2=secret-value-2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..cdc04845a5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..a10acdb42d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /docs/commands/acl/bootstrap
+[policyapply]: /docs/commands/acl/policy-apply
+[policydelete]: /docs/commands/acl/policy-delete
+[policyinfo]: /docs/commands/acl/policy-info
+[policylist]: /docs/commands/acl/policy-list
+[tokencreate]: /docs/commands/acl/token-create
+[tokenupdate]: /docs/commands/acl/token-update
+[tokendelete]: /docs/commands/acl/token-delete
+[tokeninfo]: /docs/commands/acl/token-info
+[tokenlist]: /docs/commands/acl/token-list
+[tokenself]: /docs/commands/acl/token-self
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..3a01ca5cb2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..317a91bde9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..13f30637b6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..43b28f8d5c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..c99073608e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..0611a736d9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v1.2.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..4988a4b77e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.2.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/agent.mdx b/content/nomad/v1.2.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..05c53aa5b4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/agent.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /docs/configuration/consul#address
+[alloc_dir]: /docs/configuration/client#alloc_dir
+[auth]: /docs/configuration/consul#auth
+[auto_advertise]: /docs/configuration/consul#auto_advertise
+[bind_addr]: /docs/configuration#bind_addr
+[bootstrap_expect]: /docs/configuration/server#bootstrap_expect
+[ca_file]: /docs/configuration/consul#ca_file
+[cert_file]: /docs/configuration/consul#cert_file
+[checks_use_advertise]: /docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /docs/configuration/consul#client_auto_join
+[client_http_check_name]: /docs/configuration/consul#client_http_check_name
+[client_service_name]: /docs/configuration/consul#client_service_name
+[configuration]: /docs/configuration
+[data_dir]: /docs/configuration#data_dir
+[datacenter]: /docs/configuration#datacenter
+[enabled]: /docs/configuration/acl#enabled
+[encryption overview]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption
+[key_file]: /docs/configuration/consul#key_file
+[log_json]: /docs/configuration#log_json
+[log_level]: /docs/configuration#log_level
+[meta]: /docs/configuration/client#meta
+[name]: /docs/configuration#name
+[network_interface]: /docs/configuration/client#network_interface
+[node_class]: /docs/configuration/client#node_class
+[nomad agent]: /docs/install/production/nomad-agent
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: /docs/configuration#region
+[rejoin_after_leave]: /docs/configuration/server#rejoin_after_leave
+[replication_token]: /docs/configuration/acl#replication_token
+[retry_interval]: /docs/configuration/server#retry_interval
+[retry_max]: /docs/configuration/server#retry_max
+[server_auto_join]: /docs/configuration/consul#server_auto_join
+[server_http_check_name]: /docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /docs/configuration/consul#server_serf_check_name
+[server_service_name]: /docs/configuration/consul#server_service_name
+[servers]: /docs/configuration/client#servers
+[ssl]: /docs/configuration/consul#ssl
+[state_dir]: /docs/configuration/client#state_dir
+[token]: /docs/configuration/consul#token
+[verify_ssl]: /docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..4226b41827
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..3a99a09125
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..ff71cf69c4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..7fd38a21f4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..a07820567c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be restarted.
+
+Task name may also be specified using the `-task` option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-task`: Specify the individual task to restart.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.2.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..060d47ad4d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /docs/commands/eval-status
+[`shutdown_delay`]: /docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..46d6ded1b8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..da601e8bae
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /docs/commands/deployment/list 'List all deployments'
+[pause]: /docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..5d6bfc6cfc
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..5927fe40bf
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3ea4229c7a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..cc54b45d75
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion. 
+When combined with `-verbose`, it will also display the allocations for the given 
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.2.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.2.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..273007c7d1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /docs/commands/eval-status
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
diff --git a/content/nomad/v1.2.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.2.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..504cd8a177
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[list]: /docs/commands/eval/list 'List all evals'
+[status]: /docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.2.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.2.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..467fbb90b9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Status    Placement Failures
+456e37aa  50        deployment-watcher  example  complete  false
+1a1eafe6  50        alloc-stop          example  complete  false
+3411e37b  50        job-register        example  complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.2.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..f89bb603b0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/index.mdx b/content/nomad/v1.2.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.2.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..c5bdaf8e4a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: https://learn.hashicorp.com/tutorials/nomad/format-output-with-templates
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.2.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..77fe845631
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.2.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..d87dd4c00c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+[eval status]: /docs/commands/eval-status
+[parameterized job]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.2.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..a9170f5b6b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/history.mdx b/content/nomad/v1.2.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..2252b7e932
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/index.mdx b/content/nomad/v1.2.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..355094dee7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /docs/commands/job/promote "Promote a job's canaries"
+[revert]: /docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/init.mdx b/content/nomad/v1.2.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..95e2dc911e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[drivers]: /docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.2.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..86c34ae0f7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /api-docs/jobs
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.2.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..c775b0d00d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /docs/commands/eval-status
+[force the evaluation]: /api-docs/jobs#force-new-periodic-instance
+[periodic job]: /docs/job-specification/periodic
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.2.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..fd09bc5894
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:3.2"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /docs/job-specification
+[hcl job specification]: /docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.2.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..6d67ac56e2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`list-jobs`, and `read-job` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /docs/commands/job/revert
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.2.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..732b6a038e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:3.2"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:3.2" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /docs/commands/job/history
+[eval status]: /docs/commands/eval-status
+[consul service identity]: /docs/configuration/consul#allow_unauthenticated
+[vault policy]: /docs/configuration/vault#allow_unauthenticated
+[run]: /docs/commands/job/run
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/run.mdx b/content/nomad/v1.2.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..a5184a291a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,242 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  scoped to the the specified Consul namespace. If Consul ACLs are enabled and the
+  [`allow_unauthenticated`] Nomad server Consul configuration is not enabled, then
+  a Consul token must be supplied with appropriate service and kv Consul ACL policy
+  permissions.
+
+- `-vault-token`: If set, the passed Vault token is stored in the job before
+  sending to the Nomad servers. This allows passing the Vault token without
+  storing it in the job file. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable and that found in the job.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run job1.nomad
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
+[deployment status]: /docs/commands/deployment#status
+[eval status]: /docs/commands/eval-status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /docs/commands/job/plan
+[job specification]: /docs/job-specification
+[JSON jobs]: /api-docs/json-jobs
+[`system`]: /docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.2.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..61d6dd09bb
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `scale-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /docs/commands/eval-status
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.2.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..98ecb45dd8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/status.mdx b/content/nomad/v1.2.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..e28450bad5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,254 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.2.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..134715ffe6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /docs/commands/eval-status
+[multi-region]: /docs/job-specification/multiregion
+[`shutdown_delay`]: /docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.2.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.2.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..ed10d2322e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## Validate Options
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+a variable has been supplied which is not defined within the root variables.
+Defaults to true.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a job with invalid syntax:
+
+```shell-session
+$ nomad job validate example.nomad
+Job validation errors:
+1 error(s) occurred:
+
+* group "cache" -> task "redis" -> config: 1 error(s) occurred:
+
+* field "image" is required
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /docs/job-specification
diff --git a/content/nomad/v1.2.x/content/docs/commands/license/get.mdx b/content/nomad/v1.2.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..5a3f9f3684
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/license/index.mdx b/content/nomad/v1.2.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..b22040b158
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+
+[get]: /docs/commands/license/get 'Get the current license'
diff --git a/content/nomad/v1.2.x/content/docs/commands/monitor.mdx b/content/nomad/v1.2.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..ff0738014c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..97f84c6661
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <namespace>
+```
+
+The `namespace apply` command requires the name of the namespace to be created
+or updated.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..14b6cb7196
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..68eac6a6dd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /docs/commands/namespace/list 'List available namespaces'
+[status]: /docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f2cc7c3304
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..0f6eedfba3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.2.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..45362a8407
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name        = default
+Description = Default shared namespace
+Quota       = shared-default-quota
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/node/config.mdx b/content/nomad/v1.2.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..24507070c3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /docs/configuration/client#servers
diff --git a/content/nomad/v1.2.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.2.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..1c10b2ef67
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] block until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are force removed from the
+  node. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Force remove allocations off the node immediately.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node
+  without being force stopped after a certain deadline.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs are stopped
+  last. You should always use this flag when draining a node running
+  [CSI node plugins][internals-csi].
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /docs/commands/node/eligibility
+[migrate]: /docs/job-specification/migrate
+[node status]: /docs/commands/node/status
+[workload migration guide]: https://learn.hashicorp.com/tutorials/nomad/node-drain
+[internals-csi]: /docs/concepts/plugins/csi
diff --git a/content/nomad/v1.2.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.2.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..92d0692e06
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /docs/commands/node/drain
diff --git a/content/nomad/v1.2.x/content/docs/commands/node/index.mdx b/content/nomad/v1.2.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..b98b6edb45
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /docs/commands/node/config 'View or modify client configuration details'
+[drain]: /docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.2.x/content/docs/commands/node/status.mdx b/content/nomad/v1.2.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..e667299a0f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,366 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..487bfea74e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..155ecaaf76
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /docs/configuration/server#upgrade_version
+[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..d6507ee722
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,169 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof collection. Defaults to 1s.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event 
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..c800a96435
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /api-docs/operator 'Operator API documentation'
+[outage recovery guide]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
+[remove]: /docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
+[snapshot-save]: /docs/commands/operator/snapshot-save 'Snapshot Save command'
+[snapshot-restore]: /docs/commands/operator/snapshot-restore 'Snapshot Restore command'
+[snapshot-inspect]: /docs/commands/operator/snapshot-inspect 'Snapshot Inspect command'
+[snapshot-agent]: /docs/commands/operator/snapshot-agent 'Snapshot Agent command'
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..e12e18997b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe" base64
+alphabet. If you use another tool such as OpenSSL to generate the gossip key,
+you should pipe the input through the `base64(1)` command to ensure it is
+safely encoded. For example: `openssl rand 32 | base64`
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..4a4200cb99
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..ecb9ebfb8a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..fc17543468
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /docs/configuration#data_dir
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..63fee11d12
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /api-docs/operator
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..ec8c2a53f8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /docs/configuration#data_dir
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..1039c2bb01
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /docs/commands/server/members 'Nomad server members command'
+[operator]: /api-docs/operator 'Nomad Operator API'
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..e97fb8949c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /docs/configuration#data_dir
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..61e84d2454
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..5c0b8d51ec
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..8513bfc658
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..dc33fa0003
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery
diff --git a/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.2.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..001d5ae75b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[status]: /docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.2.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.2.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..78de328905
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6746241535
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..0956cba4d5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..823a0c8d12
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /docs/commands/quota/apply
+[quotadelete]: /docs/commands/quota/delete
+[quotainit]: /docs/commands/quota/init
+[quotainspect]: /docs/commands/quota/inspect
+[quotalist]: /docs/commands/quota/list
+[quotastatus]: /docs/commands/quota/status
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..29b226bb43
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..1ff8247c14
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..24e34442cc
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.2.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..45ea3a4ca5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.2.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..3660b9f70f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.2.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..8d930e8c57
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.2.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..e95f182d66
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /docs/commands/recommendation/apply
+[recommendationdismiss]: /docs/commands/recommendation/dismiss
+[recommendationinfo]: /docs/commands/recommendation/info
+[recommendationlist]: /docs/commands/recommendation/list
diff --git a/content/nomad/v1.2.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.2.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..a0f80bb60d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.2.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..2111f423b6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.2.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..107273edf8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /docs/commands/scaling/policy-info
+[scalingpolicylist]: /docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.2.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.2.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.2.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.2.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..088b249d0d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.2.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..18263c8338
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.2.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..b30f828cfa
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /docs/commands/sentinel/delete
+[list]: /docs/commands/sentinel/list
+[read]: /docs/commands/sentinel/read
+[apply]: /docs/commands/sentinel/apply
diff --git a/content/nomad/v1.2.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.2.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..75bef2f684
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.2.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..fb97b3cbff
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.2.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d31ab75e70
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/server/index.mdx b/content/nomad/v1.2.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..ca91b4bfef
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /docs/commands/server/join 'Join server nodes together'
+[members]: /docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.2.x/content/docs/commands/server/join.mdx b/content/nomad/v1.2.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..152a102f52
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/server/members.mdx b/content/nomad/v1.2.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..f40c835d25
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in the
+  standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name          Addr      Port  Status  Proto  Build     DC   Region
+node1.global  10.0.0.8  4648  alive   2      0.1.0dev  dc1  global
+node2.global  10.0.0.9  4648  alive   2      0.1.0dev  dc1  global
+```
+
+Detailed view:
+
+```shell-session
+$ nomad server members -detailed
+Name   Addr      Port  Tags
+node1  10.0.0.8  4648  bootstrap=1,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+node2  10.0.0.9  4648  bootstrap=0,build=0.1.0dev,vsn=1,vsn_max=1,dc=dc1,port=4647,region=global,role=nomad,vsn_min=1
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/status.mdx b/content/nomad/v1.2.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.2.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..0750d31420
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/system/index.mdx b/content/nomad/v1.2.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..babd3de347
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.2.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.2.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/ui.mdx b/content/nomad/v1.2.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/version.mdx b/content/nomad/v1.2.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..e5b4ef6160
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/version.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..c154d044e1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[registered]: /docs/commands/volume/register
+[volume_specification]: /docs/other-specifications/volume
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..ae8996f865
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /docs/commands/volume/deregister
+[registered]: /docs/commands/volume/register
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..e98b8208aa
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /docs/commands/volume/delete
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..2fc9eeceda
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /docs/commands/volume/create
+[delete]: /docs/commands/volume/delete
+[deregister]: /docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /docs/commands/volume/detach 'Detach a volume'
+[init]: /docs/commands/volume/init 'Create an example volume specification file'
+[register]: /docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /docs/commands/volume/snapshot-create
+[snapshot-delete]: /docs/commands/volume/snapshot-delete
+[snapshot-list]: /docs/commands/volume/snapshot-list
+[status]: /docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..a728a6abe5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /docs/other-specifications/volume
+[`volume create`]: /docs/commands/volume/create
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bdadc56f68
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..84c07f4e65
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..50710b10dd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secrets`: A list of comma separated secret key/value pairs to be passed
+  to the CSI driver.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secrets key1=value1,key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[registered]: /docs/commands/volume/register
+[csi_plugins_internals]: /docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.2.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.2.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..6e4a092748
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /docs/job-specification/csi_plugin
+[`volume create`]: /docs/commands/volume/create
diff --git a/content/nomad/v1.2.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.2.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..96c3babef6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+#### Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+#### Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+#### Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+#### Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+#### Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+#### Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+#### Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+#### Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/docs/install/production/requirements#network-topology).
+
+#### Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+#### Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+#### Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/docs/concepts/consensus),
+[gossip protocol](/docs/concepts/gossip), and [scheduler design](/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v1.2.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.2.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.2.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.2.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..361a2fdd02
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,469 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /docs/job-specification/artifact
+[csi volumes]: /docs/concepts/plugins/csi
+[dispatch payloads]: /docs/job-specification/dispatch_payload
+[templates]: /docs/job-specification/template
+[`data_dir`]: /docs/configuration#data_dir
+[`ephemeral_disk`]: /docs/job-specification/ephemeral_disk
+[artifact]: /docs/job-specification/artifact
+[chroot contents]: /docs/drivers/exec#chroot
+[filesystem isolation capability]: /docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /docs/job-specification/ephemeral_disk#migrate
+[template]: /docs/job-specification/template
+[volume mounts]: /docs/job-specification/volume_mount
diff --git a/content/nomad/v1.2.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.2.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..ac7349555e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.2.x/content/docs/concepts/index.mdx b/content/nomad/v1.2.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.2.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.2.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..c1e64e2a0f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /docs/configuration/plugin
diff --git a/content/nomad/v1.2.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.2.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..752a34146e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the
+industry-standard Container Storage Interface specification unifies
+these APIs in a way that's agnostic to both the storage vendor and the
+container orchestrator. Each storage provider can build its own CSI
+plugin. Jobs can claim storage volumes from AWS Elastic Block Storage
+(EBS) volumes, GCP persistent disks, Ceph, Portworx, vSphere, etc. The
+Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given
+Nomad client node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id        = "csi-hostpath"
+  type      = "monolith"
+  mount_dir = "/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped.
+
+You should always run node plugins as Nomad `system` jobs and use the
+`-ignore-system` flag on the `nomad node drain` command to ensure that the
+node plugins are still running while the node is being drained. Use
+constraints for the node plugin jobs based on the availability of volumes. For
+example, AWS EBS volumes are specific to particular availability zones with a
+region. Controller plugins can be run as `service` jobs.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.2.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.2.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..71defa9c9b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.2.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.2.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c2f1bd8c11
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/docs/concepts/plugins/task-drivers)
+- [Devices](/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.2.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.2.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..4d0d8ca6c7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propogating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /plugins/drivers/remote
diff --git a/content/nomad/v1.2.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.2.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..95435ce76b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.2.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.2.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..8aac85c9fb
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.2.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.2.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..9c07454ff5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.2.x/content/docs/concepts/security.mdx b/content/nomad/v1.2.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..247e15d329
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/concepts/security.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](https://www.consul.io/docs/concepts/security), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](https://learn.hashicorp.com/collections/nomad/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+
+  - Access to read and write to a namespace can be
+    controlled to allow for granular access to job information managed within a
+    multi-tenant cluster.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](https://www.vaultproject.io/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](https://learn.hashicorp.com/collections/nomad/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+- **[ACLs enabled](https://learn.hashicorp.com/collections/nomad/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](https://learn.hashicorp.com/tutorials/nomad/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code/)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](https://learn.hashicorp.com/tutorials/nomad/web-ui-access) and [API](/api-docs) access to agents. |
+| **4647** / TCP       | Servers | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
diff --git a/content/nomad/v1.2.x/content/docs/configuration/acl.mdx b/content/nomad/v1.2.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..4faf6dd812
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. Note that the Nomad command
+  line client will send requests for client endpoints such as `alloc exec`
+  directly to Nomad clients whenever they are accessible. In this scenario, the
+  client will enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region from [authoritative_region][authoritative-region].
+
+[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control
+[authoritative-region]: /docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.2.x/content/docs/configuration/audit.mdx b/content/nomad/v1.2.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1d00ff3727
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.2.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.2.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..932acc708d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.2.x/content/docs/configuration/client.mdx b/content/nomad/v1.2.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..d6821cc782
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/client.mdx
@@ -0,0 +1,607 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/docs/drivers/exec#chroot) for
+the full list.
+
+As of Nomad 1.2, Nomad will never attempt to embed the `alloc_dir` in the
+chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the number of CPU cores to reserve.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: nil)` - Specifies the maximum amount of
+  data that will be decompressed before triggering an error and cancelling the
+  operation. E.g. "10GB". By default this value is not set and no limit is enforced.
+
+- `decompression_file_count_limit` `(int: nil)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling
+  the operation. By default this value is not set and no limit is enforced.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "")` - # This is the maximum interval to allow "stale"
+  data. By default, only the Consul leader will respond to queries. Requests to
+  a follower will forward to the leader. In large clusters with many requests,
+  this is not as scalable. This option allows any follower to respond to a query,
+  so long as the last-replicated data is within this bound. Higher values result
+  in less cluster load, but are more likely to have outdated data.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This configuration is
+  also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `wait_bounds` `(Code: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "60s")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(Code: nil)` - This controls the retry behavior when an error is
+  returned from Consul. Consul Template is highly fault tolerant, meaning it does
+  not exit in the face of failure. Instead, it uses exponential back-off and retry
+  functions to wait for the cluster to become available, as is customary in distributed
+  systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(Code: nil)` - This controls the retry behavior when an error is
+  returned from Vault. Consul Template is highly fault tolerant, meaning it does
+  not exit in the face of failure. Instead, it uses exponential back-off and retry
+  functions to wait for the cluster to become available, as is customary in distributed
+  systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-block]: /docs/configuration/plugin
+[server-join]: /docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
diff --git a/content/nomad/v1.2.x/content/docs/configuration/consul.mdx b/content/nomad/v1.2.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..11bba86f40
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+   certificate used for communication between Connect sidecar proxies and Consul
+   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](https://www.nomadproject.io/docs/configuration#http). If no
+  [HTTP address](https://www.nomadproject.io/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](https://www.nomadproject.io/docs/configuration#bind_addr).
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](https://www.consul.io/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: https://learn.hashicorp.com/tutorials/nomad/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: https://developer.hashicorp.com/consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: https://developer.hashicorp.com/consul/docs/agent/config/config-files#grpc_tls_port
diff --git a/content/nomad/v1.2.x/content/docs/configuration/index.mdx b/content/nomad/v1.2.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..f0ae1008e9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/index.mdx
@@ -0,0 +1,384 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address advertised to Nomad client nodes. This allows
+    advertising a different RPC address than is used by Nomad Servers such that
+    the clients can connect to the Nomad servers if they are behind a NAT.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
diff --git a/content/nomad/v1.2.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.2.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..986aeaf183
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.2.x/content/docs/configuration/search.mdx b/content/nomad/v1.2.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dd58bb70b8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.2.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.2.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.2.x/content/docs/configuration/server.mdx b/content/nomad/v1.2.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..13ca38acf2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/server.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use
+  for server-specific data, including the replicated log. By default, this is
+  the top-level [data_dir](/docs/configuration#data_dir) suffixed with "server",
+  like `"/opt/nomad/server"`. The top-level option must be set, even when
+  setting this value. This must be an absolute path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator keygen`] command. The
+  provided key is automatically persisted to the data directory and loaded
+  automatically whenever the agent is restarted. This means that to encrypt
+  Nomad server's gossip protocol, this option only needs to be provided once
+  on each agent's initial startup sequence. If it is provided after Nomad has
+  been initialized with an encryption key, then the provided key is ignored
+  and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - Specifies the TTL applied to
+	heartbeats after a new leader is elected, since we no longer know the status
+	of all the heartbeats. This is specified using a label suffix like "30s" or
+	"1h".
+
+  ~> Lowering the `failover_heartbeat_ttl` is a tradeoff as it lowers failure
+  detection time of nodes at the tradeoff of false positives. False positives
+  could cause all clients to stop their allocations if a leadership transition
+  lasts longer than `heartbeat_grace + failover_heartbeat_ttl`.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `protocol_version` `(int: 1)` - Specifies the Nomad protocol version to use
+  when communicating with other Nomad servers. This value is typically not
+  required as the agent internally knows the latest version, but may be useful
+  in some upgrade scenarios.
+
+- `raft_protocol` `(int: 2)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/docs/telemetry/metrics) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/tutorials/nomad/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm = "spread"
+
+    memory_oversubscription_enabled = true
+
+    reject_job_registration = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true # New in Nomad 1.2
+    }
+  }
+}
+```
+
+[encryption]: https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[`nomad operator keygen`]: /docs/commands/operator/keygen
+[search]: /docs/configuration/search
diff --git a/content/nomad/v1.2.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.2.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..f4184645b2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.2.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.2.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..342c4734f7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.2.x/content/docs/configuration/tls.mdx b/content/nomad/v1.2.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..b0e9af332f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a
+`SIGHUP` signal. Note that this will only reload a subset of the configuration
+file, including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.2.x/content/docs/configuration/ui.mdx b/content/nomad/v1.2.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..ce081b2c36
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  consul {
+    ui_url = "https://consul.example.com:8500/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8500/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+
+[web UI]: https://learn.hashicorp.com/collections/nomad/web-ui
+[Consul]: /docs/configuration/ui#consul-parameters
+[Vault]: /docs/configuration/ui#vault-parameters
+[`consul.address`]: /docs/configuration/consul#address
+[`vault.address`]: /docs/configuration/vault#address
diff --git a/content/nomad/v1.2.x/content/docs/configuration/vault.mdx b/content/nomad/v1.2.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..ae3e5bd082
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](https://www.vaultproject.io/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.2.x/content/docs/devices/index.mdx b/content/nomad/v1.2.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.2.x/content/docs/drivers/docker.mdx b/content/nomad/v1.2.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..e4a68f6026
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1192 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:3.2"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group `network.mode = "bridge"` you should not set the Docker config
+  `network_mode`, or the container will be unable to reach other containers in
+  the task group. This will also prevent [Connect]-enabled tasks from reaching
+  the Envoy sidecar proxy. You must also set any DNS options in the `network.dns`
+  block and not in the task configuration.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  client's configuration. We recommend using [`mount`](#mount) if you
+  wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-add`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`][allow_caps] plugin option key in the client node's configuration.
+  For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass directly to
+  [`--cap-drop`](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Effective capabilities (computed from `cap_add` and `cap_drop`) have to match the configured allowlist.
+  The allowlist can be customized using the [`allow_caps`][allow_caps] plugin option key in the client node's configuration.
+  For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities can be obtained
+  by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports
+  the value `"all"` as a shortcut for allow-listing all capabilities supported by
+  the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /docs/configuration/plugin
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /docs/drivers/docker#cap_add
+[cap_drop]: /docs/drivers/docker#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /docs/drivers/docker#allow_caps
+[Connect]: /docs/job-specification/connect
+[`bridge`]: /docs/job-specification/network#bridge
+[network block]: /docs/job-specification/network#bridge-mode
+[`pids_limit`]: /docs/drivers/docker#pids_limit
diff --git a/content/nomad/v1.2.x/content/docs/drivers/exec.mdx b/content/nomad/v1.2.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..b2206d7ee6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /docs/drivers/exec#default_ipc_mode
+[cap_add]: /docs/drivers/exec#cap_add
+[cap_drop]: /docs/drivers/exec#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.2.x/content/docs/drivers/index.mdx b/content/nomad/v1.2.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..180e098e05
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/concepts/plugins
+[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.2.x/content/docs/drivers/java.mdx b/content/nomad/v1.2.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..5d9d810d2a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/java.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /docs/drivers/java#default_ipc_mode
+[cap_add]: /docs/drivers/java#cap_add
+[cap_drop]: /docs/drivers/java#cap_drop
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.2.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.2.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..c18683a42d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,179 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. (Note that
+  [prior to qemu 2.10.1](https://github.com/qemu/qemu/commit/ad9579aaa16d5b385922d49edac2c96c79bcfb6),
+  the monitor socket path is limited to 108 characters. Graceful shutdown will
+  be disabled if QEMU is < 2.10.1 and the generated monitor path exceeds this
+  length. You may encounter this issue if you set long
+  [data_dir](/docs/configuration#data_dir)
+  or
+  [alloc_dir](/docs/configuration/client#alloc_dir)
+  paths.) This feature is currently not supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.2.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.2.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..d2f5a9b0f5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-block]: /docs/configuration/plugin
diff --git a/content/nomad/v1.2.x/content/docs/ecosystem.mdx b/content/nomad/v1.2.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..9d53db39d1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](https://www.nomadproject.io/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](https://www.nomadproject.io/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](https://www.nomadproject.io/plugins/drivers/community/singularity)
+- [Firecracker](https://www.nomadproject.io/plugins/drivers/community/firecracker-task-driver)
+- [Podman](https://www.nomadproject.io/plugins/drivers/podman)
+- [LXC](https://www.nomadproject.io/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](https://learn.hashicorp.com/collections/waypoint/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics)
+  - [Start Prometheus](https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing?in=nomad/nomad-1-0#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](https://www.nomadproject.io/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](https://www.nomadproject.io/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](https://www.nomadproject.io/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](https://www.nomadproject.io/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](https://www.nomadproject.io/docs/integrations/consul-connect)
+- [NGINX](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx)
+- [Traefik](https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik)
+
+## Storage
+
+- [CSI](https://www.nomadproject.io/docs/concepts/plugins/csi)
+- [Portworx](https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.2.x/content/docs/enterprise/index.mdx b/content/nomad/v1.2.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..78ebf806a3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,178 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](https://learn.hashicorp.com/tutorials/nomad/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/docs/commands/operator/snapshot-agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](https://learn.hashicorp.com/tutorials/nomad/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](https://learn.hashicorp.com/tutorials/nomad/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](https://learn.hashicorp.com/tutorials/nomad/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies
+Guide](https://learn.hashicorp.com/tutorials/nomad/sentinel) for a thorough
+overview.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /docs/job-specification/multiregion
+[autoscaling capabilities]: /tools/autoscaling
+[scaling policies]: /tools/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
diff --git a/content/nomad/v1.2.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.2.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..faac9b88fd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.1.0+ent. 
+Nomad Enterprise automatically load Nomad licenses when a Nomad server agent starts using Nomad Enterprise.
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.1.0, the license enablement process is different.
+
+HashiCorp Enterprise servers will no longer start without a license. When the server instance initializes the license watcher, the server reads from either an environment variable or file. If the license is missing, invalid, or expired, the server will immediately exit. 
+This check is part of the server boot-up process.
+
+In previous versions of HashiCorp enterprise products, one server could distribute a license to other servers via the Raft protocol. 
+This will no longer work since each server must be able to find a valid license during the startup process.
+
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about the license changes introduced in Nomad Enterprise v1.1.0
+
+- [v1.1.0 Upgrade Guide](https://www.nomadproject.io/docs/upgrade/upgrade-specific#enterprise-licenses)
+
+- [Nomad License Documentation](https://www.nomadproject.io/docs/enterprise/license)
+
+- [License configuration values documentation](https://www.nomadproject.io/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license)
+
+## Q: Does this affect Nomad or older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.1.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you follow the steps in the [upgrade guide](https://www.nomadproject.io/docs/upgrade/upgrade-specific#enterprise-licenses), but have misconfigured the licensing steps, the server instances will stop during boot-up sequence. 
+
+If you do not check cluster health after adding new servers, and verify that the new servers have joined properly, then you may accidentally take down old servers without replacing them.
+
+If you are using a trial license in production, this could cause issues as the cluster will fail to start once the trial expires.
+
+If you have built automation around `nomad license put`, this command will fail as it has been removed from Nomad v1.1.0+.
+
+## Q: What are some other gotchas?
+
+You might not have access to your organization's Nomad license. 
+The  6-hour temporary license window is now removed, and a license is required for proper boot-up.
+Running `nomad agent -dev` without a license will fail.
+
+
+## Q: How can a user get their existing license to put on disk for an upgrade?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself. 
+
+## Q: What happens when a license expires?
+If a license expires after a server node joins the cluster, the existing Enterprise features will continue to operate until a grace period expires. 
+The grace period duration is 1 day, and upon the end of the grace period the Nomad servers will shut down. 
+
+## Q: Will on-prem binaries with “baked-in” licenses work?
+
+There is no impact to baked-in licensed binaries.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Visit https://nomadproject.io/trial for a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.1.0 to an earlier version?
+
+Nomad cannot safely be rolled back to an earlier version. 
+This is not a supported operation due to the Nomad state store not having forward compatibility. The end result could be a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license).
diff --git a/content/nomad/v1.2.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.2.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..7536e61c87
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have its own license. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](https://nomadproject.io/trial) to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Expiring Licenses
+
+Nomad Enterprise license have an expiration time. You can read the license on
+a server with the `nomad license get` command:
+
+```
+$ nomad license get
+Product        = nomad
+License Status = valid
+License ID     = eaaecbd5-b598-4fa4-b649-bb234bf49fa3
+Customer ID    = ae94bdd0-39bf-4c58-bf80-8a9468b0467c
+Issued At      = 2021-03-29 14:47:29.024191 -0400 EDT
+Expires At     = 2021-03-29 20:47:29.024191 -0400 EDT
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+        Dynamic Application Sizing
+```
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+Note that if the server is restarted with an expired license, it will
+immediately stop.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license?in=nomad/enterprise) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /docs/configuration/server#license_path
+[license endpoint]: /api-docs/operator/license#updating-the-nomad-enterprise-license
\ No newline at end of file
diff --git a/content/nomad/v1.2.x/content/docs/faq.mdx b/content/nomad/v1.2.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..1ac0743922
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/docs/concepts/consensus) and
+a [gossip protocol](/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: https://www.consul.io/docs/agent/options#_datacenter
+[consul_fed]: https://learn.hashicorp.com/tutorials/consul/federarion-gossip-wan
+[nomad_region]: /docs/configuration#datacenter
+[`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.2.x/content/docs/index.mdx b/content/nomad/v1.2.x/content/docs/index.mdx
new file mode 100644
index 0000000000..b1f7f523b2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [HashiCorp Learn "Getting Started" collection][gs]
+instead.
+
+[gs]: https://learn.hashicorp.com/collections/nomad/get-started
diff --git a/content/nomad/v1.2.x/content/docs/install/index.mdx b/content/nomad/v1.2.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..4ce81bcd98
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/install/index.mdx
@@ -0,0 +1,380 @@
+---
+layout: docs
+page_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Homebrew on macOS" group="homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Linux Packages" group="linux">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](https://learn.hashicorp.com/consul) and
+[Vault](https://learn.hashicorp.com/vault) with the same command.
+
+</Tab>
+</Tabs>
+
+## Post-installation steps
+
+These steps are considered optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+<Tabs>
+<Tab heading="Linux Packages">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+
+<Tab heading="macOS">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+</Tab>
+
+<Tab heading="Windows">
+
+<h3>Add the Nomad binary to your system path</h3>
+
+Add a location to your path via the GUI by navigating to `Environment
+Variables` in your system settings, and looking for the variable called `PATH`.
+You should see a semicolon-separated list of locations. Add the Nomad binary's
+location to that list and then launch a new console window.
+</Tab>
+</Tabs>
+</Tab>
+
+<Tab heading="Homebrew on macOS" group="homebrew">
+No additional steps necessary after installing Nomad using Homebrew.
+</Tab>
+
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+No additional steps necessary after installing Nomad using Chocolatey.
+</Tab>
+
+<Tab heading="Linux" group="linux">
+
+Note that if you are running Nomad on Linux, you'll need to run client agents as
+root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+[consul-download]: https://www.consul.io/downloads
+[destroy]: https://www.vagrantup.com/docs/cli/destroy
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+[gpg-key]: https://apt.releases.hashicorp.com/gpg 'HashiCorp GPG key'
diff --git a/content/nomad/v1.2.x/content/docs/install/production/index.mdx b/content/nomad/v1.2.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..a0fb3b9ecc
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/docs/install/production/nomad-agent)
+and [Nomad Agent documentation](/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.2.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.2.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..3fecd6c2f9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,197 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+[Security Model]: /docs/concepts/security
+[production deployment guide]: https://developer.hashicorp.com/nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
diff --git a/content/nomad/v1.2.x/content/docs/install/quickstart.mdx b/content/nomad/v1.2.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..c6ac839c8c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via Learn guides containing embedded Katacoda interactive learning environments.
+
+- [Interactive Labs](https://learn.hashicorp.com/collections/nomad/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](https://www.vagrantup.com/docs/installation/). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /docs/install#precompiled-binaries
+[vagrant-environment]: https://learn.hashicorp.com/tutorials/nomad/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.2.x/content/docs/install/windows-service.mdx b/content/nomad/v1.2.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..94a569de94
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /downloads
+[logging]: /docs/configuration#log_file
diff --git a/content/nomad/v1.2.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.2.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..1ba079e2f1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,364 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** This guide requires Nomad 0.10.0 or later and Consul 1.6.0 or
+later.
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](https://www.consul.io/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+**Note**: Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](consul_ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+sudo mkdir -p /opt/cni/bin
+sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad` and running:
+`nomad job run servicemesh.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+[count-dashboard]: /img/count-dashboard.png
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: https://developer.hashicorp.com/consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: https://developer.hashicorp.com/consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: https://developer.hashicorp.com/consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: https://developer.hashicorp.com/consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
diff --git a/content/nomad/v1.2.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.2.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..0b07498fca
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](https://learn.hashicorp.com/tutorials/nomad/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` block](/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul Template,
+please see the [`template` job specification documentation](/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_acls]: https://www.consul.io/docs/security/acl
+[consul_namespaces]: https://www.consul.io/docs/enterprise/namespaces
+[consul_agent_namespace]: /docs/configuration/consul#namespace
+[consul_group_namespace]: /docs/job-specification/group#namespace
+[consul_run_namespace]: /docs/commands/job/run#consul-namespace
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/integrations/index.mdx b/content/nomad/v1.2.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.2.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.2.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..3ab4c07b62
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,472 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](https://www.vaultproject.io/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup.
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` block of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To Submit this job a token that has the `access-kv` policy in the Namespace `engineering`
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: https://www.vaultproject.io/docs/auth/token 'Vault Authentication Backend'
+[config]: /docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: https://www.vaultproject.io/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: https://www.vaultproject.io/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.2.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..57b1079816
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.2.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..fdc9107056
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](https://www.nomadproject.io/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the Nomad user's known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /root/.ssh/known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file(pathexpand("~/.ssh/id_rsa")))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[client_artifact]: /docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/check.mdx b/content/nomad/v1.2.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..fe0d111c92
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,363 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a Consul service.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+from the Consul service provider.
+
+```hcl
+job "job" {
+  group "group" {
+    task "task " {
+      service {
+        check {
+          type     = "tcp"
+          port     = 6379
+          interval = "10s"
+          timeout  = "2s"
+        }
+        # ...
+      }
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`][type] must be `http` or `grpc`, and check `name` must be set.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. For `checks` on group
+  level `services` only. Inherits the [`service.task`][service_task] value if not
+  set. May only be set for script or gRPC checks.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness vs. Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /docs/job-specification/check_restart
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[service]: /docs/job-specification/service
+[service_task]: /docs/job-specification/service#task-1
+[on_update]: /docs/job-specification/service#on_update
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.2.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..d38e12c837
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` block instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` block, it is
+restarted according to the task group's [`restart` policy][restart_block]. The
+`check_restart` settings apply to [`check`s][check_block], but may also be
+placed on [`service`s][service_block] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the blocks are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /docs/job-specification/restart 'restart block'
+[service_block]: /docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.2.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..02984231bb
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](https://www.consul.io/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](https://www.consul.io/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[native]: https://www.consul.io/docs/connect/native
+[service_task]: /docs/job-specification/service#task-1 'Nomad service task'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.2.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..00e910aeb4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,317 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.2.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..ada6285815
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id             = "csi-hostpath"
+  type           = "monolith"
+  mount_dir      = "/csi"
+  health_timeout = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <required>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. You should run `node` or `monolith` plugins as
+  [`system`][system] jobs and use the `-ignore-system` flag on `nomad
+  node drain` to ensure that the plugins are running while the node is
+  being drained.
+
+* Only one plugin instance of a given plugin ID and type (controller or node)
+  should be deployed on any given client node. Use a constraint as shown
+  below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount volumes only
+  within the same Availability Zone. You should deploy these plugins with a
+  unique-per-AZ `plugin_id` to allow Nomad to place allocations in the correct
+  AZ.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /docs/job-specification/volume
+[system]: /docs/schedulers#system
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/device.mdx b/content/nomad/v1.2.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..9d23d867a9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,303 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.2.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..0ecb164f9d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` blocks. Remember that the
+`dispatch_payload` block is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/env.mdx b/content/nomad/v1.2.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..dc9d763177
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.2.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..6ea9270226
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be
+  removed if an error is encountered.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.2.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..ff6c792576
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /docs/job-specification/network#to
+[consul-expose-path-config]: https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /docs/job-specification/expose#path-1
+[expose]: /docs/job-specification/service#expose
+[path]: /docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /docs/configuration/client#network_interface
+[learn-consul-connect]: https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh
+[check]: /docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.2.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..04ddb22c3f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,650 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect Gateways](https://www.consul.io/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](https://www.consul.io/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](https://www.consul.io/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](https://www.consul.io/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx?in=nomad/load-balancing)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - 'The protocol associated with the listener. 
+   One of `tcp`, `http`, `http2`, or `grpc`.',
+  
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or `grpc`), preconfiguring a [service-default] in Consul to
+  set the [Protocol](https://www.consul.io/docs/agent/config-entries/service-defaults#protocol)
+  of the service to the desired protocol is mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /docs/job-specification/gateway#address-parameters
+[advanced configuration]: https://www.consul.io/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: https://www.consul.io/docs/agent/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: https://www.consul.io/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /docs/job-specification/gateway#ingress-parameters
+[proxy]: /docs/job-specification/gateway#proxy-parameters
+[linked-service]: /docs/job-specification/gateway#service-parameters-1
+[listener]: /docs/job-specification/gateway#listener-parameters
+[service]: /docs/job-specification/gateway#service-parameters
+[service-default]: https://www.consul.io/docs/agent/config-entries/service-defaults
+[sidecar_task]: /docs/job-specification/sidecar_task
+[terminating]: /docs/job-specification/gateway#terminating-parameters
+[tls]: /docs/job-specification/gateway#tls-parameters
+[mesh]: /docs/job-specification/gateway#mesh-parameters
+[meta]: /docs/job-specification/service#meta
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/group.mdx b/content/nomad/v1.2.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..6d3499720d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,276 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul](/docs/configuration/consul) for service discovery.
+  Nomad automatically registers each service when an allocation
+  is started and de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul deregistration
+  and sending each task a shutdown signal. Ideally, services would fail
+  healthchecks once they receive a shutdown signal. Alternatively
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group services. In addition, tasks may have their
+  own [`shutdown_delay`](/docs/job-specification/task#shutdown_delay)
+  which waits between deregistering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration
+  after which a Nomad client that cannot communicate with the servers
+  will stop allocations based on this task group. By default, a client
+  will not stop an allocation until explicitly told to by a server. A
+  client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be
+  marked "lost" and Nomad will schedule replacement
+  allocations. However, these replaced allocations will continue to
+  run on the non-responsive client; an operator may desire that these
+  replaced allocations are also stopped in this case — for example,
+  allocations requiring exclusive access to an external resource. When
+  specified, the Nomad client will stop them after this duration. The
+  Nomad client process must be running for this to occur.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /docs/job-specification/group#consul-parameters
+[consul_namespace]: /docs/commands/job/run#consul-namespace
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /docs/configuration/server#heartbeat_grace
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..1f2e84fb9b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,425 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or `key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+service {
+  port = "db" # can use expressions here
+
+  check {
+    # but the "check" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `check` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  check_paths = ["/health", "/"]
+}
+
+job "example" {
+  # ...
+  service {
+    port = "lb" # can use expressions here
+
+    dynamic "check" {
+      for_each = local.check_paths
+
+      content {
+        type     = "http"
+        port     = "lb"
+        path     = check.value
+      }
+    }
+ }
+}
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"check"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"check"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`check` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..ed8e3d4ebb
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..0e029eeae8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..786b0caa29
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..4c3d2372ee
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..7ab7753196
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..317853e691
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..70aa9ff1b8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection or string.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or string.
+
+If given a list or map, the result is the number of elements in that collection.
+If given a string, the result is the number of characters in the string.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..472a46cde5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..bb911e06e1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..e1ce175036
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..d74ec56925
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6c74de4758
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..c410370cc8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..67a3022ffc
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..649bf5a191
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ca6a5a227e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..24e760c922
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..d41281f49f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..b54db11df1
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..a9a70ae3fc
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5bea54c6af
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..ac4d0f9be0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..4b86120885
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..d46f784114
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..7df718807b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..a1561575e5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..479598a397
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..3045ba62d0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+## Related Functions
+
+- [`fileexists`](/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..4c569e0577
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..32660de8c3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..b590d24576
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..2975376b5d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..62241b2f89
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..1528f29673
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..d90e6ce35b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..7d0a4279b9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..d56ad71f78
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..361e4ef0c8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..83e0a662f2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..14850d2f88
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..97b1b2eeac
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..80ad67c306
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..e97a48508f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..0eec2f9b6e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W)
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..9b9f2eb374
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..c456bd76d9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..fad64d44a6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..5b8efdf95b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..7a1af15367
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..f5fa82b049
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..904a98f921
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..ca8e610629
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..1be5e3d817
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..9586e352fe
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..ff63c13581
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..53d10bad25
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /api-docs/json-jobs
+[run-json]: /docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/docs/job-specification/hcl2/syntax)
+- [Expressions](/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/docs/job-specification/meta), and
+[`env`](/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpf_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..90c23d0079
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..ec80fe394e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..943e41be6f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are often referred to as just
+"variables" or "Nomad variables" when it is clear from context what sort of
+variable is being discussed. Other kinds of variables in Nomad include
+_environment variables_ (set by the shell where Nomad runs) and _expression
+variables_ (used to indirectly represent a value in an
+[expression](/docs/job-specification/hcl2/expressions)).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](https://www.terraform.io/docs/configuration/types.html).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/index.mdx b/content/nomad/v1.2.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..3c3dfc9eb9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/job.mdx b/content/nomad/v1.2.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..ab7ddc11a0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,257 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[parameterized]: /docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: https://learn.hashicorp.com/tutorials/nomad/federation
+[reschedule]: /docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /docs/schedulers 'Nomad Scheduler Types'
+[spread]: /docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[update]: /docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.2.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c097175bb8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: https://learn.hashicorp.com/collections/nomad/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/docs/job-specification/template) or
+[`artifact`](/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.2.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..c5e8e6b4cf
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` block allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /docs/commands/alloc/logs 'Nomad logs command'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.2.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..5aab588721
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any `-` character existing in the key
+will also be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /docs/runtime/environment#meta
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.2.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..0a8105568d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /docs/job-specification/service#check-parameters
+[count]: /docs/job-specification/group#count
+[drain]: /docs/commands/node/drain
+[deadline]: /docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.2.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..be62befc26
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,266 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region
+— the one specified by the `region` field or the `-region` command line
+flag to `nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation
+[`update` block]: /docs/job-specification/update
+[update-auto-revert]: /docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: https://learn.hashicorp.com/collections/nomad/job-updates
+[`nomad deployment unblock`]: /docs/commands/deployment/unblock
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/network.mdx b/content/nomad/v1.2.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..3bfa1168ab
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,311 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+  for the allocations. By default all DNS configuration is inherited from the client host.
+  DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /docs/configuration/client#cni_path
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.2.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..7ef6137dea
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.2.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..fada7ea3a3
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+[batch-type]: /docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.2.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..4ed2ae7abf
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](https://www.consul.io/docs/connect/proxies/envoy#dynamic-configuration)
+  for details.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.2.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..6798fcd615
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.2.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..7f7a7f2f37
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Specifies the number of CPU cores to reserve
+  for the task. This may not be used with `cpu`.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Optionally, specifies the maximum memory the task may use, if the client has excess memory capacity, in MB. See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad 1.1. lets job authors set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The new max limit attribute is currently supported by the official `docker`,
+`exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory Oversubscription in the scheduler
+configuration](/api-docs/operator/scheduler#update-scheduler-configuration). Enterprise customers can use [Resource
+Quotas](https://learn.hashicorp.com/tutorials/nomad/quotas) to limit the memory
+oversubscription.
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[device]: /docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.2.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..3f085cccc8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /docs/job-specification/sidecar_task
+[`reschedule`]: /docs/job-specification/reschedule
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.2.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..45785b7281
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /tools/autoscaling/policy
+[`count`]: /docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/service.mdx b/content/nomad/v1.2.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..841f5a0c17
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,490 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with Consul. This
+section of the documentation will discuss the configuration, but please also
+read the [Nomad service discovery documentation][service-discovery] for more
+detailed information about the integration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. Only available where
+  `provider = "consul"`. At this time, the Consul integration supports the `grpc`,
+  `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker or rkt).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](https://www.consul.io/docs/internals/anti-entropy#enable-tag-override)
+  for more information.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. This setting is supported in
+  Docker since Nomad 0.6 and rkt since Nomad 0.7. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker and rkt. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with Consul. It
+is important to understand when each of these steps happens and how they can be
+customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in Consul as well. Consul is updated without restarting a task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from Consul without delay. If however
+Nomad needs to kill a running task, the task is killed in the following order:
+
+1. Immediately remove the services and checks from Consul. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in Consul, and
+   thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks.
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+This example must be accompanied by a [`network`][network] block which defines
+a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/docs/drivers/docker#network_mode) and
+[rkt](/docs/drivers/rkt#net) drivers support the `driver` setting for the
+`address_mode` parameter in both `service` and `check` blocks. The driver
+address mode allows advertising and health checking the IP and port assigned to
+a task by the driver. This way, if you're using a network plugin like Weave with
+Docker, you can advertise the Weave address in Consul instead of the host's
+address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than "host" or "bridge" is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:3.2"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /docs/job-specification/check
+[check_restart_block]: /docs/job-specification/check_restart
+[consul_grpc]: https://www.consul.io/api/agent/check#grpc
+[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical
+[service-discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /docs/job-specification/restart 'restart block'
+[connect]: /docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /docs/job-specification/service#type
+[shutdowndelay]: /docs/job-specification/task#shutdown_delay
+[killsignal]: /docs/job-specification/task#kill_signal
+[killtimeout]: /docs/job-specification/task#kill_timeout
+[service_task]: /docs/job-specification/service#task-1
+[network_mode]: /docs/job-specification/network#mode
+[on_update]: /docs/job-specification/service#on_update
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.2.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..37a298b946
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.2.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..4beafe8c36
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /docs/job-specification/gateway
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.2.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..73411abf7c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/task.mdx b/content/nomad/v1.2.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..8445dec458
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with
+  [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing it from Consul and sending it a shutdown
+  signal. Ideally services would fail healthchecks once they receive a shutdown
+  signal. Alternatively `shutdown_delay` may be set to give in flight requests
+  time to complete before shutting down. In addition, task groups may have their
+  own [`shutdown_delay`](/docs/job-specification/group#shutdown_delay)
+  which waits between deregistering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /docs/drivers/exec 'Nomad exec Driver'
+[java]: /docs/drivers/java 'Nomad Java Driver'
+[docker]: /docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /docs/configuration/client#user-checked_drivers
+[user_denylist]: /docs/configuration/client#user-denylist
+[max_kill]: /docs/configuration/client#max_kill_timeout
+[kill_signal]: /docs/job-specification/task#kill_signal
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/template.mdx b/content/nomad/v1.2.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..6a719536d6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,530 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Since Nomad v0.5.3, the template can reference [Nomad's runtime
+environment variables][env], and since Nomad v0.5.6, the template can reference
+[Node attributes and metadata][nodevars]. Since Nomad v0.6.0, templates can be
+read as environment variables.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] Learn guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals] documentation.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([see below](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to `consul-template`.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To workaround this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+## Nomad Integration
+
+### Nomad Services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Consul Integration
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Similar to KV API v1, if the name of a secret includes the `-` character, you
+must access it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: https://learn.hashicorp.com/tutorials/nomad/go-template-syntax
+[artifact]: /docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /docs/configuration/client#wait_bounds
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/update.mdx b/content/nomad/v1.2.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..301012de98
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with CSI volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: https://learn.hashicorp.com/collections/nomad/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.2.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..443e148b1b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /docs/job-specification/job 'Nomad job Job Specification'
+[group]: /docs/job-specification/group 'Nomad group Job Specification'
+[task]: /docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: https://www.consul.io/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: https://www.consul.io/docs/connect/gateways/mesh-gateway#mesh-gateways
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.2.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..629ed11201
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/docs/configuration/vault#namespace)
+to use [Vault Namespaces](https://www.vaultproject.io/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.2.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..8fe508e0e9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:3.2"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /docs/configuration/client#host_volume-block
+[csi_volume]: /docs/commands/volume/register
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume]: /docs/commands/volume/register
+[attachment mode]: /docs/commands/volume/register#attachment_mode
+[volume registration]: /docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.2.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.2.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..b6a6c7f657
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /docs/job-specification/volume#volume-interpolation
+[hcl2]: /docs/job-specification/hcl2
diff --git a/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..2814bf54d6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/docs/ecosystem).
diff --git a/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..6f8a9fdacd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.2.x/content/docs/operations/index.mdx b/content/nomad/v1.2.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..ec2de41d9f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/docs/operations/nomad-agent)
+- [Telemetry Overview](/docs/operations/telemetry)
+- [Metrics](/docs/operations/metrics)
+- [Cluster Management](https://learn.hashicorp.com/collections/nomad/manage-clusters)
+- [Transport Security](https://learn.hashicorp.com/collections/nomad/transport-security)
+- [Access Control](https://learn.hashicorp.com/collections/nomad/access-control)
diff --git a/content/nomad/v1.2.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.2.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..c281c5893d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,455 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_blocked`           | Evaluations that are blocked until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/docs/job-specification/parameterized) and
+[periodic](/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+| --------------------------------------- | ----------------------------------------------------------------------------------- | ---------- | ----- | ------------------------------------------------------------------------------------- |
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated_disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations waiting for previous versions to exit                         | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating data from previous versions (see [`sticky`][sticky])| Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending (received by the client but not yet running)          | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on the
+task driver; not all task drivers can provide all metrics.
+
+| Metric                                        | Description                                                       | Unit        | Type  | Labels                                           |
+| --------------------------------------------- | ----------------------------------------------------------------- | ----------- | ----- | ------------------------------------------------ |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                    | Unit                 | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------|----------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                    | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                       | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                           | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits) | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern. | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer | Gauge | host |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                     | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                            | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                            | Nanoseconds          | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                   | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                    | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                           | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_update`                       | Time elapsed to apply `AllocUpdate` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Summary` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                 | Integer              | Counter | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                               | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                        | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                  | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                              | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                            | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                   | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                      | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler_service`        | Time elapsed for worker to invoke the scheduler                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                   | Integer              | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                               | Integer              | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication               | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                       | Integer              | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                   | ms / Raft Log Append | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                               | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                 | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                            | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                           | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                              | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                    | # of bytes           | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                        | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                    | Integer              | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                            | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                    | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                    | Integer              | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                  | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                         | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                             | Float                | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                         | Integer              | Gauge   | host                                                    |
+
+
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[sticky]: /docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: /s/port-plan-failure
diff --git a/content/nomad/v1.2.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.2.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..71e7827482
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,289 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+If this log *does* appear repeatedly with the same `node_id` referenced, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.broker.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed. Nomad also emits a similar metric for each
+  individual scheduler. For example `nomad.broker.batch_blocked` shows
+  the number of blocked evaluations for the batch scheduler.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /docs/configuration/telemetry#circonus
+[collection-interval]: /docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /docs/configuration/telemetry#datadog
+[draining]: https://learn.hashicorp.com/tutorials/nomad/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /docs/telemetry/metrics#metric-types
+[metrics-api-endpoint]: /api-docs/metrics
+[prometheus-telem]: /docs/configuration/telemetry#prometheus
+[serf]: /docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /docs/configuration/telemetry#statsd
+[statsite-telem]: /docs/configuration/telemetry#statsite
+[tagged-metrics]: /docs/telemetry/metrics#tagged-metrics
+[telemetry-block]: /docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /docs/operations/telemetry#consensus-protocol-raft
+[Job Summary Metrics]: /docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.2.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.2.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..a25945ca34
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/docs/concepts/consensus) and [gossip protocol](/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default,
+any signal to an agent (interrupt, terminate, kill) will cause the agent
+to forcefully stop. Graceful termination can be configured by either
+setting `leave_on_interrupt` or `leave_on_terminate` to respond to the
+respective signals.
+
+When gracefully exiting, clients will update their status to terminal on
+the servers so that tasks can be migrated to healthy agents. Servers
+will notify their intention to leave the cluster which allows them to
+leave the [consensus](/docs/concepts/consensus) peer set.
+
+It is especially important that a server node be allowed to leave gracefully
+so that there will be a minimal impact on availability as the server leaves
+the consensus peer set. If a server does not gracefully leave, and will not
+return into service, the [`server force-leave` command](/docs/commands/server/force-leave)
+should be used to eject it from the consensus peer set.
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
diff --git a/content/nomad/v1.2.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.2.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..9b31228e43
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,350 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "write"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When an action is checked against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, the matching rule with the greatest number of matched characters will be
+chosen.
+
+For example the following policy will evaluate to deny for `production-web`,
+because it is 9 characters different from the `"*-web"` rule, but 13 characters
+different from the `"*"` rule.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, or both.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be viewed.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered.
+- `csi-read-volume` - Allows inspecting a CSI volume and seeing fine grain
+  status.
+- `csi-list-volume` - Allows listing CSI volumes and seeing coarse grain status.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                    |
+| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`  | deny                                                                                                                                                                                                                                                            |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                      |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+
+[Secure Nomad with Access Control]: https://learn.hashicorp.com/collections/nomad/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /api-docs/jobs
+[api_allocations]: /api-docs/allocations
+[api_deployments]: /api-docs/deployments
+[api_evaluations]: /api-docs/evaluations
+[api_recommendations]: /api-docs/recommendations
+[api_scaling_policies]: /api-docs/scaling-policies
+[api_services]: /api-docs/services
+[api_volumes]: /api-docs/volumes
+[api_events]: /api-docs/events
+[api_search]: /api-docs/search
+[api_agent]: /api-docs/agent/
+[api_node]: /api-docs/nodes/
+[api_operator]: /api-docs/operator/
+[api_quota]: /api-docs/quotas/
+[host_volumes]: /docs/configuration/client#host_volume-block
+[api_plugins]: /api-docs/plugins/
diff --git a/content/nomad/v1.2.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.2.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..54fbc2db36
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /docs/job-specification
+[acl_policy_spec]: /docs/other-specifications/acl-policy
+[volume_spec]: /docs/other-specifications/volume
diff --git a/content/nomad/v1.2.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.2.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..3278c73d00
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /docs/job-specification/volume
diff --git a/content/nomad/v1.2.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.2.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..0f4b2b9541
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,187 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), [`clone_id`](#clone_id),
+[`capacity_min`](#capacity_min), or [`capacity_max`](#capacity_max) fields on
+**volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+[api_volume_create]: /api-docs/volumes#create-volume
+[api_volume_register]: /api-docs/volumes#register-volume
+[capability]: /docs/other-specifications/volume/capability
+[csi_plugin]: /docs/job-specification/csi_plugin
+[csi_volume_source]: /docs/job-specification/volume#source
+[mount_options]: /docs/other-specifications/volume/mount_options
+[`volume create`]: /docs/commands/volume/create
+[`volume register`]: /docs/commands/volume/register
diff --git a/content/nomad/v1.2.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.2.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..9b4f1c7194
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /docs/job-specification/volume
diff --git a/content/nomad/v1.2.x/content/docs/partnerships.mdx b/content/nomad/v1.2.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..ec63583eb6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. For a full description of the current features please refer to the [Nomad Website](/). The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/docs/operations/telemetry)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.2.x/content/docs/runtime/environment.mdx b/content/nomad/v1.2.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..90ed25160e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs and where possible backed by an
+  in-memory filesystem. It can be used to store secret data that should not be
+  visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /docs/job-specification 'Nomad Job Specification'
+[vault]: /docs/vault-integration 'Nomad Vault Integration'
+[filesystem internals]: /docs/concepts/filesystem
+[`env.denylist`]: /docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.2.x/content/docs/runtime/index.mdx b/content/nomad/v1.2.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..395b323583
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/docs/runtime/environment)
+- [Interpolation](/docs/runtime/interpolation)
+- [Schedulers](/docs/schedulers)
diff --git a/content/nomad/v1.2.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.2.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..31da7917f4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.placement.availability-zone}'}</code>
+      </td>
+      <td>Availability Zone of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:3.2"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.2.x/content/docs/schedulers.mdx b/content/nomad/v1.2.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..3601f92966
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/schedulers.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+## System Batch
+
+~> System Batch scheduling is new in Nomad 1.2.
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exists successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /docs/job-specification/parameterized
+[periodic]: /docs/job-specification/periodic
+[preemption]: /docs/concepts/scheduling/preemption
+[restart]: /docs/job-specification/restart
+[reschedule]: /docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.2.x/content/docs/upgrade/index.mdx b/content/nomad/v1.2.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..6a4ba62a7e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,240 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](https://learn.hashicorp.com/tutorials/nomad/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /docs/configuration#data_dir
+[heartbeat_grace]: /docs/configuration/server#heartbeat_grace
+[monitor]: /docs/commands/monitor
+[node-status]: /docs/commands/node/status
+[server-members]: /docs/commands/server/members
+[upgrade-specific]: /docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`raft.peers`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `raft.peers` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /docs/configuration/server#raft_protocol
+
diff --git a/content/nomad/v1.2.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.2.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..cb73d86f67
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1250 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](https://www.nomadproject.io/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/docs/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`](/docs/configuration/server#raft_protocol) option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](https://learn.hashicorp.com/tutorials/nomad/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+#### Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3 in Nomad 0.8 and
+higher. Raft protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. See [Raft Protocol Version
+Compatibility](/docs/upgrade/upgrade-specific#raft-protocol-version-compatibility)
+for more details. Also the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+Please note that the Raft protocol is different from Nomad's internal protocol
+as shown in commands like `nomad server members`. To see the version of the Raft
+protocol in use on each server, use the `nomad operator raft list-peers`
+command.
+
+The easiest way to upgrade servers is to have each server leave the cluster,
+upgrade its `raft_protocol` version in the `server` block, and then add it
+back. Make sure the new server joins successfully and that the cluster is stable
+before rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the older
+servers in a similar fashion.
+
+When using Raft protocol version 3, servers are identified by their `node-id`
+instead of their IP address when Nomad makes changes to its internal Raft quorum
+configuration. This means that once a cluster has been upgraded with servers all
+running Raft protocol version 3, it will no longer allow servers running any
+older Raft protocol versions to be added. If running a single Nomad server,
+restarting it in-place will result in that server not being able to elect itself
+as a leader. To avoid this, either set the Raft protocol back to 2, or use
+[Manual Recovery Using
+peers.json](https://learn.hashicorp.com/tutorials/nomad/outage-recovery#manual-recovery-using-peersjson)
+to map the server to its node ID in the Raft quorum configuration.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/docs/job-specification/env) and
+[`template`](/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[dangling-containers]: /docs/drivers/docker#dangling-containers
+[drain-api]: /api-docs/nodes#drain-node
+[drain-cli]: /docs/commands/node/drain
+[dst]: /docs/job-specification/periodic#daylight-saving-time
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /docs/configuration#limits
+[lxc]: /plugins/drivers/community/lxc
+[migrate]: /docs/job-specification/migrate
+[nvidia]: /plugins/devices/nvidia
+[plugin-block]: /docs/configuration/plugin
+[plugins]: /plugins/drivers/community
+[preemption-api]: /api-docs/operator#update-scheduler-configuration
+[preemption]: /docs/concepts/scheduling/preemption
+[proxy_concurrency]: /docs/job-specification/sidecar_task#proxy_concurrency
+[`sidecar_task.config`]: /docs/job-specification/sidecar_task#config
+[reserved]: /docs/configuration/client#reserved-parameters
+[task-config]: /docs/job-specification/task#config
+[tls-guide]: https://learn.hashicorp.com/tutorials/nomad/security-enable-tls
+[tls-vault-guide]: https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad
+[update]: /docs/job-specification/update
+[validate]: /docs/commands/job/validate
+[vault_grace]: /docs/job-specification/template
+[node drain]: https://www.nomadproject.io/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /docs/configuration/client#template-parameters
+[pki]: https://www.vaultproject.io/docs/secrets/pki
+[`volume create`]: /docs/commands/volume/create
+[`volume register`]: /docs/commands/volume/register
+[`volume`]: /docs/job-specification/volume
+[enterprise licensing]: /docs/enterprise/license
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /docs/drivers/docker#allow_caps
+[`extra_hosts`]: /docs/drivers/docker#extra_hosts
+[no_net_raw]: /docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /docs/drivers/exec#allow_caps
+[allow_caps_java]: /docs/drivers/java#allow_caps
+[cap_add_exec]: /docs/drivers/exec#cap_add
+[cap_drop_exec]: /docs/drivers/exec#cap_drop
+[`log_file`]: /docs/configuration#log_file
diff --git a/content/nomad/v1.2.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.2.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..c63e018796
--- /dev/null
+++ b/content/nomad/v1.2.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.2.x/content/intro/index.mdx b/content/nomad/v1.2.x/content/intro/index.mdx
new file mode 100644
index 0000000000..f346673bd2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/docs) and [HashiCorp Learn guides](https://learn.hashicorp.com/nomad) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/intro/use-cases) and [Who Uses Nomad](/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.2.x/content/intro/use-cases.mdx b/content/nomad/v1.2.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..596d1ec370
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/docs/drivers/docker)
+and integrates seamlessly with [Consul](/docs/integrations/consul-integration)
+and [Vault](/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.2.x/content/intro/vs/ecs.mdx b/content/nomad/v1.2.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.2.x/content/intro/vs/index.mdx b/content/nomad/v1.2.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.2.x/content/intro/vs/mesos.mdx b/content/nomad/v1.2.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.2.x/content/intro/vs/terraform.mdx b/content/nomad/v1.2.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..8bda3512cf
--- /dev/null
+++ b/content/nomad/v1.2.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.2.x/content/partials/envvars.mdx b/content/nomad/v1.2.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..2c48b44c46
--- /dev/null
+++ b/content/nomad/v1.2.x/content/partials/envvars.mdx
@@ -0,0 +1,61 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                   |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                     |
+| `NOMAD_SECRETS_DIR`      | Path to the task's secrets directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                        |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                 |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                           |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                   |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request cpu cores. E.g. `0-2,7,12-14`                                                                                                                                        |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                       |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                          |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index. |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                     |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                    |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through CLI but can be different when using the API                                                                                                                                                                     |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                      |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                            |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                   |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                    |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                       |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Note that this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata.                                                                          |
+| `VAULT_TOKEN`            | The task's Vault token. See [Vault Integration](/nomad/docs/integrations/vault-integration) for more details                                                                                                                                                                    |
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                                                                                          |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See [here for more](/docs/job-specification/network) information.                                                                                                                                                                                                                |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See [here for more](/docs/job-specification/network) information.                                                                         |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                                                                                      |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See [here](/docs/job-specification/network#mapped-ports) for more information.                                                                                                                                                                                                |
+| `NOMAD_IP_<task>_<label>`          | **Deprecated**. Host IP for the given port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                                        |
+| `NOMAD_PORT_<task>_<label>`        | **Deprecated**. Port for the given port `label` and `task` for tasks in the same task group. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. Only available when setting ports via the task resource network port mapping. |
+| `NOMAD_ADDR_<task>_<label>`        | **Deprecated**. Host `IP:Port` pair for the given port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                            |
+| `NOMAD_HOST_PORT_<task>_<label>`   | **Deprecated**.  Port on the host for the port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                                    |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul Connect [upstream](/docs/job-specification/upstreams).                                                                                                                                                                                                           |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul Connect [upstream](/docs/job-specification/upstreams).                                                                                                                                                                                                         |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul Connect [upstream](/docs/job-specification/upstreams).                                                                                                                                                                                               |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+
+~> **Note:** Port labels and task names will have any non-alphanumeric or
+  underscore characters in their names replaced by underscores `_` when they're
+  used in environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+### Consul-related Variables
+
+This variables are only set for Connect native tasks.
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a tcp address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Connect service identity token specific to the service instance if Consul ACLs are enabled. |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the CLient Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
diff --git a/content/nomad/v1.2.x/content/partials/general_options.mdx b/content/nomad/v1.2.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..bb9ece3878
--- /dev/null
+++ b/content/nomad/v1.2.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespaces authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.2.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.2.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.2.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.2.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.2.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..993b989254
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /docs/concepts/plugins
+[usb]: /plugins/devices/community/usb
diff --git a/content/nomad/v1.2.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.2.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..ce8e643982
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.2.x/content/plugins/devices/index.mdx b/content/nomad/v1.2.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..9bccef0831
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /docs/concepts/plugins
+[nvidia]: /plugins/devices/nvidia
diff --git a/content/nomad/v1.2.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.2.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..b1106a4ac6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /docs/configuration/plugin
+[`plugin_dir`]: /docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
\ No newline at end of file
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..15c60ebf31
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /docs/commands/job/init
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /docs/job-specification/network
+[`service`]: /docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..86aba308cd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..0615d02df8
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..2e681ae7b5
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[rookout]: /plugins/drivers/community/rookout
+[lxc]: /plugins/drivers/community/lxc
+[rkt]: /plugins/drivers/community/rkt
+[plugin_guide]: /docs/concepts/plugins
+[singularity]: /plugins/drivers/community/singularity
+[jail-task-driver]: /plugins/drivers/community/jail-task-driver
+[pot]: /plugins/drivers/community/pot
+[firecracker-task-driver]: /plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /plugins/drivers/community/nspawn
+[nomad-driver-iis]: /plugins/drivers/community/iis
+[nomad-driver-containerd]: /plugins/drivers/community/containerd
+[lightrun]: /plugins/drivers/community/lightrun
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..adc5dea14c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /docs/configuration#plugin_dir
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..9308166150
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionaly, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /docs/drivers/java
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..5b06a67b8b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: https://learn.hashicorp.com/tutorials/nomad/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[allocation working directory]: /docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..2e5769d10b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /docs/configuration/client#options
+[docker_driver]: /docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /docs/integrations/consul-connect
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..644925cb64
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..1c2279bc05
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:3.2"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:3.2"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /docs/configuration/plugin
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..5fff163f08
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](https://www.nomadproject.io/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](https://www.nomadproject.io/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.2.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..4900ed822c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /docs/configuration/plugin
+[plugin_dir]: /docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/index.mdx b/content/nomad/v1.2.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..180e098e05
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /docs/configuration/plugin
+[docker_plugin]: /docs/drivers/docker#client-requirements
+[plugin_guide]: /docs/concepts/plugins
+[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.2.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..fa9531062f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,519 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+Due to Podman's similarity to Docker, the example job created by
+[`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- [Nomad][nomad_download] 0.12.9+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroup V2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a 3.0.x podman binary and a system socket activation unit, refer to
+[https://www.redhat.com/sysadmin/podmans-new-rest-api](https://www.redhat.com/sysadmin/podmans-new-rest-api).
+
+Nomad agent, `nomad-driver-podman` and `podman` will reside on the same client,
+so you do not have to worry about the `ssh` aspects of the Podman api.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed the the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart. Consider a
+  simple single node system and a complete reboot. All previously managed
+  containers will be reused instead of disposed and recreated.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[`count`]: /docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /docs/job-specification/resources#memory
+[`network`]: /docs/job-specification/network
+[nomad-init]: /docs/commands/job/init
+[nomad_download]: /downloads.html
+[nomad_driver_ports]: /docs/drivers/docker.html#forwarding-and-exposing-ports
+[nomad_group_network]: /docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /docs/job-specification/lifecycle
+[plugin_dir]: /docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.2.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..e2d5fbf1af
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.2.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.2.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..bb20b51d6c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]:  /docs/job-specification/artifact
+[connect]: /docs/job-specification/connect
+[dispatch-payload]: /docs/job-specification/dispatch_payload
+[drain]: /docs/commands/node/drain
+[ephemeral-disk]: /docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /docs/job-specification/network
+[remote-cap]: /docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /docs/job-specification/resources
+[task-config]: /docs/job-specification/task#config
+[template]: /docs/job-specification/template
+[upgrade]: /docs/upgrade/upgrade-specific
+[vault]: /docs/job-specification/vault
+[volume]: /docs/job-specification/volume
diff --git a/content/nomad/v1.2.x/content/plugins/index.mdx b/content/nomad/v1.2.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..ca69e8e589
--- /dev/null
+++ b/content/nomad/v1.2.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/plugins/drivers)
+- [Devices](/plugins/devices)
diff --git a/content/nomad/v1.2.x/content/security.mdx b/content/nomad/v1.2.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.2.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..e6b899ff85
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.conf -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.conf`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: https://learn.hashicorp.com/tutorials/nomad/namespaces
+[nomad_acls]: https://learn.hashicorp.com/collections/nomad/access-control
+[autoscaler_agent_nomad]: /tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /tools/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..96ffce14ea
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+### `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..964d3d679f
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: https://learn.hashicorp.com/tutorials/nomad/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..0b9d8d8bcd
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+### `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..53b856fba9
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+### `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..b260938ade
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+}
+```
+
+### `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7dc1b03f3d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+### `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/source.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/source.mdx
new file mode 100644
index 0000000000..ac6796fc0b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/source.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: source Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "source" block is used to configure scaling target sources.
+---
+
+# `source` Block
+
+<Placement groups={['policy', 'source']} />
+
+The `source` block is used to configure scaling target sources.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+Supported sources are `file` and `nomad`.
+
+### `source` Parameters
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..990cf27446
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+### `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..4921294377
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+### `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..37f6cb7f90
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+### `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus`
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e46c4321cf
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..71e167689a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,191 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /tools/autoscaling/agent
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..0303b82718
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autocaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The 
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /tools/autoscaling/agent
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/checks.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/checks.mdx
new file mode 100644
index 0000000000..716ce8633c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/checks.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Nomad Autoscaler Check Calculations
+
+A scaling policy can include several checks all of which produce a scaling
+suggesting. The checks are executed at the same time during a policy evaluation
+and the results can conflict with each other. In a scenario like this, the
+autoscaler iterates the results the chooses the safest result which results in
+retaining the most capacity of the resource.
+
+In a scenario where two checks return different desired directions, the following
+logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the two same actions are suggested, but with different counts the
+following logic is applied, where the count is the absolute desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/index.mdx
new file mode 100644
index 0000000000..b7844e1294
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Internals
+description: >
+  This section covers the internals of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Internals
+
+This section covers the internals of the Nomad Autoscaler and explains the
+technical details of how it functions, its architecture, and sub-systems.
+
+- [Autoscaler plugins](/tools/autoscaling/internals/plugins)
+- [Check calculations](/tools/autoscaling/internals/checks)
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/node-selector-strategy.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/node-selector-strategy.mdx
new file mode 100644
index 0000000000..16cf6a3d1d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /docs/schedulers#system
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/apm.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/apm.mdx
new file mode 100644
index 0000000000..b3ce155137
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/base.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/base.mdx
new file mode 100644
index 0000000000..750c612539
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /tools/autoscaling/agent
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/index.mdx
new file mode 100644
index 0000000000..6f415e2a1d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/strategy.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/strategy.mdx
new file mode 100644
index 0000000000..102b4969b4
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/target.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/target.mdx
new file mode 100644
index 0000000000..25b46ec489
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/internals/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..a2e8fb0ee2
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "percentage-allocated_cpu"
+  ...
+}
+```
+
+Querying Nomad client node metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+  for the allocation.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+  allocated for the allocation.
+
+[nomad_telemetry_block]: /docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..9b31b08be7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [DigitalOcean Droplets][do-droplets]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[plugin_guide]: /tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..f532ea4181
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /tools/autoscaling/plugins/external
+[plugin_dir_config]: /tools/autoscaling/agent#plugin_dir
+[apm]: /tools/autoscaling/agent/apm#apm-block
+[strategy]: /tools/autoscaling/agent/strategy#strategy-block
+[target]: /tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..715b99f950
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin will perform count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..e5692ead0b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-traffic" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound valus to trigger the action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /tools/autoscaling/internals/checks
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..7796e7f000
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /tools/autoscaling/policy
+[nomad_group_block]: /docs/job-specification/group
+[nomad_job_block]: /docs/job-specification/job
+[nomad_namespace_parameter]: /docs/job-specification/job#namespace
+[nomad_recommendations_api]: /api-docs/recommendations
+[nomad_region_parameter]: /docs/job-specification/job#region
+[nomad_resource_block]: /docs/job-specification/resources
+[nomad_scaling_block]: /docs/job-specification/scaling
+[nomad_task_block]: /docs/job-specification/task
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..dfa3eca34c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[node_selector_strategy]: /tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: https://www.vaultproject.io/docs/secrets/aws
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..7458d793c6
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_client_meta_tag]: /docs/configuration/client#meta
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[vault_azure_backend]: https://www.vaultproject.io/docs/secrets/azure
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..368fb2c54c
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /docs/configuration#datacenter
+[nomad_node_class]: /docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /api-docs/nodes#deadline
+[nomad_node_purge]: /api-docs/nodes#purge-node
+[node_selector_strategy]: /tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: https://www.vaultproject.io/docs/secrets/gcp
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..110770bc98
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /docs/job-specification/job#job-block
+[nomad_group_block]: /docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /docs/job-specification/job#namespace
+[nomad_scaling_block]: /docs/job-specification/scaling
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..930319692b
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,230 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[das]: /tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /docs/job-specification/scaling
diff --git a/content/nomad/v1.2.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.2.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..ef2ff9bdcb
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.2.x/content/tools/index.mdx b/content/nomad/v1.2.x/content/tools/index.mdx
new file mode 100644
index 0000000000..6a778d486a
--- /dev/null
+++ b/content/nomad/v1.2.x/content/tools/index.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
diff --git a/content/nomad/v1.2.x/data/api-docs-nav-data.json b/content/nomad/v1.2.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..a864be8539
--- /dev/null
+++ b/content/nomad/v1.2.x/data/api-docs-nav-data.json
@@ -0,0 +1,145 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.2.x/data/docs-nav-data.json b/content/nomad/v1.2.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..dd0c542715
--- /dev/null
+++ b/content/nomad/v1.2.x/data/docs-nav-data.json
@@ -0,0 +1,1881 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Service Mesh",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin <sup>Beta</sup>",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.2.x/data/intro-nav-data.json b/content/nomad/v1.2.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..7abd058898
--- /dev/null
+++ b/content/nomad/v1.2.x/data/intro-nav-data.json
@@ -0,0 +1,56 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "https://learn.hashicorp.com/collections/nomad/get-started"
+      },
+      {
+        "title": "Running Nomad",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-run"
+      },
+      {
+        "title": "Jobs",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs"
+      },
+      {
+        "title": "Clustering",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster"
+      },
+      {
+        "title": "Web UI",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui"
+      },
+      {
+        "title": "Next Steps",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.2.x/data/plugins-nav-data.json b/content/nomad/v1.2.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..2e1b3e9fcc
--- /dev/null
+++ b/content/nomad/v1.2.x/data/plugins-nav-data.json
@@ -0,0 +1,107 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.2.x/data/tools-nav-data.json b/content/nomad/v1.2.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..cc589f40e7
--- /dev/null
+++ b/content/nomad/v1.2.x/data/tools-nav-data.json
@@ -0,0 +1,218 @@
+[
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "path": "autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "path": "autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "path": "autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.2.x/img/count-dashboard.png b/content/nomad/v1.2.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.2.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.2.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.2.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.2.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/favicon-16x16.png b/content/nomad/v1.2.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/favicon-194x194.png b/content/nomad/v1.2.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/favicon-32x32.png b/content/nomad/v1.2.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/favicon.ico b/content/nomad/v1.2.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.2.x/img/favicons/mstile-144x144.png b/content/nomad/v1.2.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/mstile-150x150.png b/content/nomad/v1.2.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/mstile-310x150.png b/content/nomad/v1.2.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/mstile-310x310.png b/content/nomad/v1.2.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/mstile-70x70.png b/content/nomad/v1.2.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.2.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.2.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.2.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.2.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.2.x/img/logo-hashicorp.svg b/content/nomad/v1.2.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v1.2.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.2.x/img/logo-text.svg b/content/nomad/v1.2.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.2.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.2.x/img/nomad-architecture-global.png b/content/nomad/v1.2.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.2.x/img/nomad-architecture-region.png b/content/nomad/v1.2.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.2.x/img/nomad-bg-pattern.svg b/content/nomad/v1.2.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.2.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.2.x/img/nomad-data-model.png b/content/nomad/v1.2.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.2.x/img/nomad-evaluation-flow.png b/content/nomad/v1.2.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.2.x/img/nomad-kubernetes.png b/content/nomad/v1.2.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.2.x/img/nomad-panel-learn.svg b/content/nomad/v1.2.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.2.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.2.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.2.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.2.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.2.x/img/nomad-workload.png b/content/nomad/v1.2.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.2.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.2.x/img/og-image.png b/content/nomad/v1.2.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.2.x/img/og-image.png differ
diff --git a/content/nomad/v1.2.x/img/pattern.svg b/content/nomad/v1.2.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.2.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.2.x/redirects.jsonc b/content/nomad/v1.2.x/redirects.jsonc
new file mode 100644
index 0000000000..cdf664e6fe
--- /dev/null
+++ b/content/nomad/v1.2.x/redirects.jsonc
@@ -0,0 +1,1389 @@
+[
+  // Define your custom redirects within this file.
+  // Vercel"s redirect documentation: https://vercel.com/docs/configuration#project/redirects
+  // Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+  {
+    "source": "/home",
+    "destination": "/",
+    "permanent": true,
+  },
+
+  // Friendly URL for trial form redirection
+  {
+    "source": "/trial",
+    "destination": "https://www.hashicorp.com/products/nomad/trial",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/overview",
+    "destination": "/docs/operations",
+    "permanent": true,
+  },
+
+  // This redirect supports a URL built into the Nomad UI, and should always be
+  // directed someplace valid to support the text "Read about Outage Recovery."
+  {
+    "source": "/guides/outage.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  // Nomad Learn Redirects
+  {
+    "source": "/intro/getting-started",
+    "destination": "https://learn.hashicorp.com/collections/nomad/get-started",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/install",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-install",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/running",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-run",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/ui",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/next-steps",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/vs/kubernetes",
+    "destination": "/docs/nomad-vs-kubernetes",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/who-uses-nomad",
+    "destination": "/docs/who-uses/noamd",
+    "permanent": true,
+  },
+  // Guides
+  {
+    "source": "/guides/load-balancing",
+    "destination": "https://learn.hashicorp.com/collections/nomad/load-balancing",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/fabio",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/nginx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/haproxy",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/traefik",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/stateful-workloads",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/host-volumes",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/portworx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/web-ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/access.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/accessing",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/submitting-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/operating-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/inspecting-the-cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/securing",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/governance-and-policy",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  // /s/* redirects for useful links that need a stable URL but we may need to
+  // change its destination in the future.
+  {
+    "source": "/s/port-plan-failure",
+    "destination": "/docs/operations/monitoring-nomad#progress",
+    "permanent": false,
+  },
+
+  // Spark guide links are all repointed to deprecated nomad-spark repo
+  {
+    "source": "/guides/spark",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/spark/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  // These are subsumed in the splat over analytical-workloads, but I"m keeping them here in case
+  // we want to reclaim the slug "analytical-workloads" at some point and deal with some bad links.
+  // {
+  //   "source": "/guides/analytical-workloads/spark/spark",
+  //   "destination": "https://github.com/hashicorp/nomad-spark",
+  //   "permanent": true,
+  // },
+
+  {
+    "source": "/guides/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspec",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/affinity",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/affinity",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/advanced-scheduling/preemption-service-batch",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/spread",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/spread",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/update-strategies",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/manage-clusters",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/monitoring",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/prometheus-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/vault-pki-integration",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad",
+    "permanent": true,
+  },
+
+  // Multi-part UI guides
+  {
+    "source": "/guides/ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+
+  // Website
+  // Docs
+  {
+    "source": "/docs/index",
+    "destination": "/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api-docs/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/config",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/nvidia",
+    "destination": "/plugins/devices/nvidia",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/taskconfig",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/inspecting",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/resources",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/updating",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/servicediscovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/interpreted",
+    "destination": "/docs/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/json",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/environment",
+    "destination": "/docs/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/servicediscovery",
+    "destination": "/docs/job-specification/service",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/networking",
+    "destination": "/docs/job-specification/network",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/job-specification/index",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/requirements",
+    "destination": "/docs/install/production/requirements/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-index",
+    "destination": "/docs/commands/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-list-peers",
+    "destination": "/docs/commands/operator/raft-list-peers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-remove-peer",
+    "destination": "/docs/commands/operator/raft-remove-peer",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/job-dispatch",
+    "destination": "/docs/commands/job/dispatch",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/alloc-status",
+    "destination": "/docs/commands/alloc/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/eval-status",
+    "destination": "/docs/commands/eval/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/fs",
+    "destination": "/docs/commands/alloc/fs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/logs",
+    "destination": "/docs/commands/alloc/logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/init",
+    "destination": "/docs/commands/job/init",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/inspect",
+    "destination": "/docs/commands/job/inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/run",
+    "destination": "/docs/commands/job/run",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/stop",
+    "destination": "/docs/commands/job/stop",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/plan",
+    "destination": "/docs/commands/job/plan",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/validate",
+    "destination": "/docs/commands/job/validate",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/client-config",
+    "destination": "/docs/commands/node/config",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-drain",
+    "destination": "/docs/commands/node/drain",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-status",
+    "destination": "/docs/commands/node/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keygen",
+    "destination": "/docs/commands/operator/keygen",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keyring",
+    "destination": "/docs/commands/operator/keyring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-force-leave",
+    "destination": "/docs/commands/server/force-leave",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-join",
+    "destination": "/docs/commands/server/join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-members",
+    "destination": "/docs/commands/server/members",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/runtime/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+
+  // Sometimes code names are too good not to mention
+  {
+    "source": "/heartyeet",
+    "destination": "/docs/job-specification/group#stop_after_client_disconnect",
+    "permanent": true,
+  },
+
+  // Moved /docs/drivers/external/podman -> /docs/drivers/podman
+  {
+    "source": "/docs/drivers/external/podman",
+    "destination": "/plugins/drivers/podman",
+    "permanent": true,
+  },
+
+  // Moved /docs/operating-a-job/ -> /guides/operating-a-job/
+  {
+    "source": "/docs/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/update-strategies",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  // Moved /docs/agent/configuration/ -> /docs/configuration/ 301!
+  {
+    "source": "/docs/agent/configuration",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/acl",
+    "destination": "/docs/configuration/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/autopilot",
+    "destination": "/docs/configuration/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/client",
+    "destination": "/docs/configuration/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/consul",
+    "destination": "/docs/configuration/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/sentinel",
+    "destination": "/docs/configuration/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server",
+    "destination": "/docs/configuration/server",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server_join",
+    "destination": "/docs/configuration/server_join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/telemetry",
+    "destination": "/docs/configuration/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/tls",
+    "destination": "/docs/configuration/tls",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/vault",
+    "destination": "/docs/configuration/vault",
+    "permanent": true,
+  },
+  // Moved telemetry under operations
+  {
+    "source": "/docs/telemetry",
+    "destination": "/docs/operations/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/telemetry/metrics",
+    "destination": "/docs/operations/metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/metrics",
+    "destination": "/docs/operations/metrics-reference",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/telemetry",
+    "destination": "/docs/operations/monitoring-nomad",
+    "permanent": true,
+  },
+
+  // Moved installing agent under operations as ope
+  {
+    "source": "/docs/install/production/nomad-agent",
+    "destination": "/docs/operations/nomad-agent",
+    "permanent": true,
+  },
+
+  // Moved guide-like docs to /guides
+  {
+    "source": "/docs/agent",
+    "destination": "/docs/install/production/nomad-agent/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/telemetry",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/service-discovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+
+  // Redirect old LXC driver doc to new one in /docs/external
+  {
+    "source": "/docs/drivers/lxc",
+    "destination": "/plugins/drivers/community/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/rkt",
+    "destination": "/plugins/drivers/community/rkt",
+    "permanent": true,
+  },
+
+  // API
+  {
+    "source": "/docs/http/agent-force-leave",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-join",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-members",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-self",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-servers",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/alloc",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/allocs",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-allocation-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-fs",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/eval",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/evals",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/job",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/jobs",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/json-jobs",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/node",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/nodes",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/operator",
+    "destination": "/api-docs/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/regions",
+    "destination": "/api-docs/regions",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/status",
+    "destination": "/api-docs/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/system",
+    "destination": "/api-docs/system",
+    "permanent": true,
+  },
+
+  // Guides
+
+  // Reorganized Guides by Persona
+  {
+    "source": "/guides/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/install/index",
+    "destination": "/docs/install",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/agent/index",
+    "destination": "/docs/install/production/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/consul-integration/index",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/vault-integration/index",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+
+  // Enterprise
+
+  // Reorganized Enterprise into single pager
+  {
+    "source": "/docs/enterprise/namespaces",
+    "destination": "/docs/enterprise#namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/quotas",
+    "destination": "/docs/enterprise#resource-quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/preemption",
+    "destination": "/docs/enterprise#preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/sentinel",
+    "destination": "/docs/enterprise#sentinel-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/autopilot",
+    "destination": "/docs/enterprise#nomad-enterprise-platform",
+    "permanent": true,
+  },
+
+  // Guide Catch-all Redirects
+  {
+    "source": "/guides/:splat*",
+    "destination": "https://learn.hashicorp.com/nomad",
+    "permanent": true,
+  },
+
+  // Vault Integration
+  {
+    "source": "/docs/vault-integration",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  // Old resources -> Community
+  {
+    "source": "/resources",
+    "destination": "/community",
+    "permanent": true,
+  },
+  // `/<path>/index.html` to /<path>
+  {
+    "source": "/:splat*/index.html",
+    "destination": "/:splat*",
+    "permanent": true,
+  },
+  // `.html` to non-`.html`
+  {
+    "source": "/:splat(.*).html",
+    "destination": "/:splat",
+    "permanent": true,
+  },
+  // Extracted content into `/plugins` & `/tools`
+  {
+    "source": "/docs/autoscaling",
+    "destination": "/tools/autoscaling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/autoscaling/:splat*",
+    "destination": "/tools/autoscaling/:splat*",
+    "permanent": true,
+  },
+  // Extracted content into `/plugins` & `/tools`
+  // - Redirect individual pages so we don"t conflict with
+  //   "built-in plugins" pages
+  {
+    "source": "/docs/devices/external",
+    "destination": "/plugins/devices/community",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/external/usb",
+    "destination": "/plugins/devices/community/usb",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/external/nvidia",
+    "destination": "/plugins/devices/nvidia",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/containerd",
+    "destination": "/plugins/drivers/community/containerd",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/firecracker-task-driver",
+    "destination": "/plugins/drivers/community/firecracker-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/iis",
+    "destination": "/plugins/drivers/community/iis",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external",
+    "destination": "/plugins/drivers/community",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/jail-task-driver",
+    "destination": "/plugins/drivers/community/jail-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/lightrun",
+    "destination": "/plugins/drivers/community/lightrun",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/lxc",
+    "destination": "/plugins/drivers/community/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/nspawn",
+    "destination": "/plugins/drivers/community/nspawn",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/pot",
+    "destination": "/plugins/drivers/community/pot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/rkt",
+    "destination": "/plugins/drivers/community/rkt",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/rookout",
+    "destination": "/plugins/drivers/community/rookout",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/singularity",
+    "destination": "/plugins/drivers/community/singularity",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/podman",
+    "destination": "/plugins/drivers/podman",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/remote/ecs",
+    "destination": "/plugins/drivers/remote/ecs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/remote",
+    "destination": "/plugins/drivers/remote",
+    "permanent": true,
+  },
+  {
+    "source": "/api/:path*",
+    "destination": "/api-docs/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/internals/:path*",
+    "destination": "/docs/concepts/:path*",
+    "permanent": true,
+  }
+]
diff --git a/content/nomad/v1.3.x/content/api-docs/acl-policies.mdx b/content/nomad/v1.3.x/content/api-docs/acl-policies.mdx
new file mode 100644
index 0000000000..7dd35ace75
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/acl-policies.mdx
@@ -0,0 +1,167 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": ""
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/acl-tokens.mdx b/content/nomad/v1.3.x/content/api-docs/acl-tokens.mdx
new file mode 100644
index 0000000000..4c5845147e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/acl-tokens.mdx
@@ -0,0 +1,488 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token. 
+An operator created token can be provided in the body of the request to bootstrap the cluster 
+if required. If no header is provided the cluster will return a generated management token. 
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be replicated globally to all regions. Otherwise, this token is created local to the target region.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/agent.mdx b/content/nomad/v1.3.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..4321d5d5e4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/agent.mdx
@@ -0,0 +1,923 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader
+
+$ curl \
+    https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`](/nomad/docs/configuration#enable_debug)
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a Server ID, name, or `leader` to target a specific remote
+  server or leader for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 1)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/agent/trace?&seconds=5&server_id=server1.global
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
diff --git a/content/nomad/v1.3.x/content/api-docs/allocations.mdx b/content/nomad/v1.3.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..88aa46d826
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/allocations.mdx
@@ -0,0 +1,914 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.3.x/content/api-docs/client.mdx b/content/nomad/v1.3.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..a03ef02c1d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/client.mdx
@@ -0,0 +1,670 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/deployments.mdx b/content/nomad/v1.3.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/evaluations.mdx b/content/nomad/v1.3.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..e4253fe1b1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,385 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
diff --git a/content/nomad/v1.3.x/content/api-docs/events.mdx b/content/nomad/v1.3.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..75fb6b38e4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/events.mdx
@@ -0,0 +1,393 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock": "true",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "mock_driver": {
+              "Attributes": {
+                "driver.mock": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445193068-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/index.mdx b/content/nomad/v1.3.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..55713ae728
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/index.mdx
@@ -0,0 +1,699 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> --data-urlencode 'filter=<filter expression>'
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/jobs \
+    --data-urlencode 'filter=Datacenters contains "dc2"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/deployments \
+    --data-urlencode 'filter=Status != "successful"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.3.x/content/api-docs/jobs.mdx b/content/nomad/v1.3.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..5d1090d86b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2356 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `idempotency_token` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.3.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..a8ea3c0ab2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1193 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad
+$ nomad job run -output example.nomad
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Id": "",
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": ""
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v1.3.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.3.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..0f3738ffc7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.3.x/content/api-docs/metrics.mdx b/content/nomad/v1.3.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/namespaces.mdx b/content/nomad/v1.3.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f1050081cc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,205 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota"
+}
+```
+
+Note that the `Quota` key is Enterprise-only.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/nodes.mdx b/content/nomad/v1.3.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..893da76437
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1150 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.3.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..76bc8d1346
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/index.mdx b/content/nomad/v1.3.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/license.mdx b/content/nomad/v1.3.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.3.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..b6313223f0
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.3.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..fdad37cda3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,202 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+    `true`, tasks may exceed their reserved memory limit, if the client has excess
+    memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+  `true`, tasks may exceed their reserved memory limit, if the client has excess
+  memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription.
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.3.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.3.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.3.x/content/api-docs/plugins.mdx b/content/nomad/v1.3.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..f6676906c1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/plugins.mdx
@@ -0,0 +1,137 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/quotas.mdx b/content/nomad/v1.3.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..52171b55fe
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/quotas.mdx
@@ -0,0 +1,352 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        }
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      }
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/recommendations.mdx b/content/nomad/v1.3.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/regions.mdx b/content/nomad/v1.3.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.3.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/search.mdx b/content/nomad/v1.3.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..4c3762ffb0
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/search.mdx
@@ -0,0 +1,589 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given search
+term and context, where a context can be jobs, allocations, nodes, plugins, or namespaces.
+Additionally, fuzzy searching can be done across all contexts. For better control
+over the performance implications of fuzzy searching on Nomad servers, aspects of
+fuzzy searching can be tuned through the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs, namespace:csi-list-plugin` |
+
+When ACLs are enabled, requests must have a token valid for `node:read`, `plugin:read` or
+`namespace:read-jobs` roles. If the token is only valid for a portion of these
+capabilities, then results will include results including only data readable with
+the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "plugins", or
+  "all", where "all" means every context will be searched. When "all" is selected,
+  additional prefix matches will be included for the "deployments", "evals", and
+  "volumes" types. When searching in the "jobs" context, results that fuzzy match
+  "groups", "services", "tasks", "images", "commands", and "classes" are also
+  included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.3.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.3.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/services.mdx b/content/nomad/v1.3.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.3.x/content/api-docs/status.mdx b/content/nomad/v1.3.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/system.mdx b/content/nomad/v1.3.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/ui.mdx b/content/nomad/v1.3.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.3.x/content/api-docs/validate.mdx b/content/nomad/v1.3.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..2311f97ef4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.3.x/content/api-docs/volumes.mdx b/content/nomad/v1.3.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..5b0866626e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/api-docs/volumes.mdx
@@ -0,0 +1,783 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..f797d33d2e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an apropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..bb6c933a63
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[policyapply]: /nomad/docs/commands/acl/policy-apply
+[policydelete]: /nomad/docs/commands/acl/policy-delete
+[policyinfo]: /nomad/docs/commands/acl/policy-info
+[policylist]: /nomad/docs/commands/acl/policy-list
+[tokencreate]: /nomad/docs/commands/acl/token-create
+[tokenupdate]: /nomad/docs/commands/acl/token-update
+[tokendelete]: /nomad/docs/commands/acl/token-delete
+[tokeninfo]: /nomad/docs/commands/acl/token-info
+[tokenlist]: /nomad/docs/commands/acl/token-list
+[tokenself]: /nomad/docs/commands/acl/token-self
+[secure-guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/policy-apply.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/policy-apply.mdx
new file mode 100644
index 0000000000..3a01ca5cb2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/policy-apply.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/policy-delete.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/policy-delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/policy-delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/policy-info.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/policy-info.mdx
new file mode 100644
index 0000000000..317a91bde9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/policy-info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+Rules       = {
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+CreateIndex = 749
+ModifyIndex = 758
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/policy-list.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/policy-list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/policy-list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-create.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-create.mdx
new file mode 100644
index 0000000000..13f30637b6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-create.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Create a new ACL token:
+
+```shell-session
+$ nomad acl token create -name="my token" -policy=foo -policy=bar
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-delete.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-info.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-info.mdx
new file mode 100644
index 0000000000..43b28f8d5c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-info.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-list.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-list.mdx
new file mode 100644
index 0000000000..c99073608e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name             Type        Global  Accessor ID
+Bootstrap Token  management  true    32b61154-47f1-3694-1430-a5544bafcd3e
+<none>           client      false   fcf2bf84-a257-8f39-9d16-a954ed25b5be
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-self.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-self.mdx
new file mode 100644
index 0000000000..0611a736d9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-self.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/acl/token-update.mdx b/content/nomad/v1.3.x/content/docs/commands/acl/token-update.mdx
new file mode 100644
index 0000000000..4988a4b77e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/acl/token-update.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="my updated token" -policy=foo -policy=bar d532c40a-30f1-695c-19e5-c35b882b0efd
+Accessor ID  = d532c40a-30f1-695c-19e5-c35b882b0efd
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = my updated token
+Type         = client
+Global       = false
+Policies     = [foo bar]
+Create Time  = 2017-09-15 05:04:41.814954949 +0000 UTC
+Create Index = 8
+Modify Index = 8
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.3.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/agent.mdx b/content/nomad/v1.3.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..671bf043d0
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/agent.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[nomad agent]: /nomad/docs/install/production/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..9cee1bda49
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..b03e3ae9a6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..92652b0177
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..7fd38a21f4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.3.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..0426d820f9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval-status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.3.x/content/docs/commands/config/index.mdx b/content/nomad/v1.3.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.3.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.3.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..960ac0c9c8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..4be99818d6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..5ad8e9c310
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..617b0129cc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion. 
+When combined with `-verbose`, it will also display the allocations for the given 
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.3.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.3.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..393ecebef4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval-status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.3.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..846d8f6990
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfuly deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Do you want to list evals (3) before deletion? [y/N] y
+
+ID        Priority  Triggered By  Job ID   Namespace   Node ID   Status   Placement Failures
+cef92121  50        job-register  example  default     <none>    pending  false
+1c905ca0  50        job-register  example  default     <none>    pending  false
+b9e77692  50        job-register  example  default     <none>    pending  false
+
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfuly deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfuly deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler-get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler-set-config
diff --git a/content/nomad/v1.3.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.3.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.3.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.3.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.3.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/index.mdx b/content/nomad/v1.3.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.3.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..3b2d7e3a7d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.3.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..77fe845631
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.3.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..2ff11b81b1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+[eval status]: /nomad/docs/commands/eval-status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.3.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..84ab16a1dd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/history.mdx b/content/nomad/v1.3.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..2252b7e932
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/index.mdx b/content/nomad/v1.3.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..47ff5c79d8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/init.mdx b/content/nomad/v1.3.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..36cd12f5c9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.3.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..e181e61937
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.3.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..d768d18935
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval-status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.3.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..b45d45b1c6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,264 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.3.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..b4d011115c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`list-jobs`, and `read-job` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.3.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..fd7073962d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval-status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/run.mdx b/content/nomad/v1.3.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..8780e73bf8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  scoped to the the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and kv Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run job1.nomad
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval-status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.3.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..b58b5195b3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `scale-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval-status
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.3.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..98ecb45dd8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/status.mdx b/content/nomad/v1.3.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..e28450bad5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,254 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.3.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..b0ab578419
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all of the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval-status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.3.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.3.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..94d0273d87
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.3.x/content/docs/commands/license/get.mdx b/content/nomad/v1.3.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..5a3f9f3684
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/license/index.mdx b/content/nomad/v1.3.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..f08fd21f06
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license'
diff --git a/content/nomad/v1.3.x/content/docs/commands/monitor.mdx b/content/nomad/v1.3.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..ff0738014c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..d9f4a854af
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers  = ["docker", "exec"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..14b6cb7196
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..e2ab326c7d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f2cc7c3304
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..0f6eedfba3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.3.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..5a51e3ac6e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name            = api-prod
+Description     = Prod API servers
+Quota           = prod
+EnabledDrivers  = docker,exec
+DisabledDrivers = raw_exec
+ 
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/node/config.mdx b/content/nomad/v1.3.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.3.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.3.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..eff783e134
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,151 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] block until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block.
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[migrate]: /nomad/docs/job-specification/migrate
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.3.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.3.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.3.x/content/docs/commands/node/index.mdx b/content/nomad/v1.3.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..b315f5fb77
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.3.x/content/docs/commands/node/status.mdx b/content/nomad/v1.3.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..2a7075d8c4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,397 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjuction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..a36e35b537
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,175 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=<pprof-interval>`: The interval between pprof
+    collections. Set interval equal to duration to capture a single
+    snapshot. Defaults to 250ms or `-pprof-duration`, whichever is
+    less.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..a796431fbb
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot-get-config 'Autopilot Get Config command'
+[keygen]: /nomad/docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /nomad/docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /nomad/docs/commands/operator/raft-list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft-remove-peer 'Raft Remove Peer command'
+[set-config]: /nomad/docs/commands/operator/autopilot-set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot-save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot-restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot-inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot-agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler-get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler-set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..e12e18997b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe" base64
+alphabet. If you use another tool such as OpenSSL to generate the gossip key,
+you should pipe the input through the `base64(1)` command to ensure it is
+safely encoded. For example: `openssl rand 32 | base64`
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..4a4200cb99
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+---
+
+# Command: operator keyring
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..593d6ed48a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..61e84d2454
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..221452f1d2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..0d813786d7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..7da70d95f9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.3.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.3.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.3.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6746241535
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..0956cba4d5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..afc21d99d1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..29b226bb43
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..1ff8247c14
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..24e34442cc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.3.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..45ea3a4ca5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.3.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..3660b9f70f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.3.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..8d930e8c57
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.3.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..7b2665192c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.3.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.3.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..a0f80bb60d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.3.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..2111f423b6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.3.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..1f70f5d317
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.3.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.3.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.3.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.3.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..088b249d0d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..18263c8338
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.3.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f904c7b714
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.3.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.3.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..75bef2f684
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.3.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..fb97b3cbff
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.3.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d31ab75e70
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/server/index.mdx b/content/nomad/v1.3.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.3.x/content/docs/commands/server/join.mdx b/content/nomad/v1.3.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..152a102f52
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/server/members.mdx b/content/nomad/v1.3.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..bfd9ce255b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..0eb973622c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/service/index.mdx b/content/nomad/v1.3.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..a6f207b0a8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.3.x/content/docs/commands/service/info.mdx b/content/nomad/v1.3.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..9287f4da0f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/service/list.mdx b/content/nomad/v1.3.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..7c09b6acb4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/status.mdx b/content/nomad/v1.3.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.3.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/system/index.mdx b/content/nomad/v1.3.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.3.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.3.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/ui.mdx b/content/nomad/v1.3.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/version.mdx b/content/nomad/v1.3.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..e5b4ef6160
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/version.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..47bd3ff3e5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..e95c8dbc08
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.3.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.3.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..d371d7f455
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.3.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.3.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..25bca1184d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+#### Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+#### Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+#### Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+#### Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+#### Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+#### Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+#### Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+#### Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+#### Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+#### Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+#### Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v1.3.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.3.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.3.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.3.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..c0514750e9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,470 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.3.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.3.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..d5b2f7cf42
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/nomad/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.3.x/content/docs/concepts/index.mdx b/content/nomad/v1.3.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.3.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.3.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.3.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.3.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..837520bad9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable. 
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging 
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.3.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.3.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.3.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.3.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..79e2aa1a75
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.3.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.3.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..308da7a1ff
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propogating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
diff --git a/content/nomad/v1.3.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.3.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..9c17dc0d8d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.3.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.3.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..5307339993
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.3.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.3.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..9c07454ff5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.3.x/content/docs/concepts/security.mdx b/content/nomad/v1.3.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..57abd036e8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/concepts/security.mdx
@@ -0,0 +1,327 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/concepts/security), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - Access to read and write to a namespace can be
+    controlled to allow for granular access to job information managed within a
+    multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code/)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
diff --git a/content/nomad/v1.3.x/content/docs/configuration/acl.mdx b/content/nomad/v1.3.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..9aeb5803ea
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled = true
+  token_ttl = "30s"
+  policy_ttl = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. Note that the Nomad command
+  line client will send requests for client endpoints such as `alloc exec`
+  directly to Nomad clients whenever they are accessible. In this scenario, the
+  client will enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region from [authoritative_region][authoritative-region].
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.3.x/content/docs/configuration/audit.mdx b/content/nomad/v1.3.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.3.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.3.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.3.x/content/docs/configuration/client.mdx b/content/nomad/v1.3.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..e0802b672c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/client.mdx
@@ -0,0 +1,642 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/nomad/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/nomad/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+As of Nomad 1.2, Nomad will never attempt to embed the `alloc_dir` in the
+chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the number of CPU cores to reserve.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: nil)` - Specifies the maximum amount of
+  data that will be decompressed before triggering an error and cancelling the
+  operation. E.g. "10GB". By default this value is not set and no limit is enforced.
+
+- `decompression_file_count_limit` `(int: nil)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling
+  the operation. By default this value is not set and no limit is enforced.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
diff --git a/content/nomad/v1.3.x/content/docs/configuration/consul.mdx b/content/nomad/v1.3.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..d52c61da2d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+   certificate used for communication between Connect sidecar proxies and Consul
+   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](/consul/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
diff --git a/content/nomad/v1.3.x/content/docs/configuration/index.mdx b/content/nomad/v1.3.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..d6d78d8540
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/index.mdx
@@ -0,0 +1,387 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
diff --git a/content/nomad/v1.3.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.3.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.3.x/content/docs/configuration/search.mdx b/content/nomad/v1.3.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.3.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.3.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.3.x/content/docs/configuration/server.mdx b/content/nomad/v1.3.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..547fdbb9d8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/server.mdx
@@ -0,0 +1,372 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use
+  for server-specific data, including the replicated log. By default, this is
+  the top-level [data_dir](/nomad/docs/configuration#data_dir) suffixed with "server",
+  like `"/opt/nomad/server"`. The top-level option must be set, even when
+  setting this value. This must be an absolute path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator keygen`] command. The
+  provided key is automatically persisted to the data directory and loaded
+  automatically whenever the agent is restarted. This means that to encrypt
+  Nomad server's gossip protocol, this option only needs to be provided once
+  on each agent's initial startup sequence. If it is provided after Nomad has
+  been initialized with an encryption key, then the provided key is ignored
+  and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given as a
+  grace period beyond the heartbeat TTL of nodes to account for network and
+  processing delays as well as clock skew. This is specified using a label
+  suffix like "30s" or "1h".
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  node heartbeats. This is used as a floor to prevent excessive updates. This is
+  specified using a label suffix like "30s" or "1h". Lowering the minimum TTL is
+  a tradeoff as it lowers failure detection time of nodes at the tradeoff of
+  false positives and increased load on the leader.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - Specifies the TTL applied to
+	heartbeats after a new leader is elected, since we no longer know the status
+	of all the heartbeats. This is specified using a label suffix like "30s" or
+	"1h".
+
+  ~> Lowering the `failover_heartbeat_ttl` is a tradeoff as it lowers failure
+  detection time of nodes at the tradeoff of false positives. False positives
+  could cause all clients to stop their allocations if a leadership transition
+  lasts longer than `heartbeat_grace + failover_heartbeat_ttl`.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Increasing the maximum heartbeats per
+  second is a tradeoff as it lowers failure detection time of nodes at the
+  tradeoff of false positives and increased load on the leader.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/telemetry/metrics) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false # New in Nomad 1.3.2
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true # New in Nomad 1.2
+    }
+  }
+}
+```
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator keygen`]: /nomad/docs/commands/operator/keygen
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.3.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.3.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..f4184645b2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.3.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.3.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..2da59d9942
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/telemetry).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.3.x/content/docs/configuration/tls.mdx b/content/nomad/v1.3.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..118d8c93ab
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Specifies if TLS should be enabled on the RPC
+  endpoints and [Raft][raft] traffic between the Nomad servers. Enabling this on
+  a Nomad client makes the client use TLS for making RPC requests to the Nomad
+  servers.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a
+`SIGHUP` signal. Note that this will only reload a subset of the configuration
+file, including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.3.x/content/docs/configuration/ui.mdx b/content/nomad/v1.3.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..9525aab116
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  consul {
+    ui_url = "https://consul.example.com:8500/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8500/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.3.x/content/docs/configuration/vault.mdx b/content/nomad/v1.3.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..3bc0ec0107
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /nomad/docs/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.3.x/content/docs/devices/index.mdx b/content/nomad/v1.3.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.3.x/content/docs/drivers/docker.mdx b/content/nomad/v1.3.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..436b77726e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1219 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group `network.mode = "bridge"` you should not set the Docker config
+  `network_mode`, or the container will be unable to reach other containers in
+  the task group. This will also prevent [Connect]-enabled tasks from reaching
+  the Envoy sidecar proxy. You must also set any DNS options in the `network.dns`
+  block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  timeout the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credHelpers` or `credsStore`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`. The image will only be pulled from
+  the container registry if its tag is `latest` or the image doesn't yet exist locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credHelpers` or `credsStore`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`][](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)
+[`--cap-drop`][](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)
diff --git a/content/nomad/v1.3.x/content/docs/drivers/exec.mdx b/content/nomad/v1.3.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..87cf8ffc71
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot). If executing a binary that is downloaded from
+  an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocations's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.3.x/content/docs/drivers/index.mdx b/content/nomad/v1.3.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.3.x/content/docs/drivers/java.mdx b/content/nomad/v1.3.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..9de1accc68
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/java.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.3.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.3.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..b37f880939
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.3.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.3.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..b8b2db68e7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.3.x/content/docs/ecosystem.mdx b/content/nomad/v1.3.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.3.x/content/docs/enterprise/index.mdx b/content/nomad/v1.3.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..868a4db4f9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,178 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot-agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies
+Guide](/nomad/tutorials/governance-and-policy/sentinel) for a thorough
+overview.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
diff --git a/content/nomad/v1.3.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.3.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..0b0d39eef5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.1.0+ent.
+Nomad Enterprise automatically load Nomad licenses when a Nomad server agent starts using Nomad Enterprise.
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.1.0, the license enablement process is different.
+
+HashiCorp Enterprise servers will no longer start without a license. When the
+server instance initializes the license watcher, the server reads from either an
+environment variable or file. If the license is missing, invalid, or terminated,
+the server will immediately exit. This check is part of the server boot-up
+process.
+
+In previous versions of HashiCorp enterprise products, one server could
+distribute a license to other servers via the Raft protocol. This will no longer
+work since each server must be able to find a valid license during the startup
+process.
+
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about the license changes introduced in Nomad Enterprise v1.1.0
+
+- [v1.1.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect Nomad or older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.1.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you follow the steps in the [upgrade guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses), but have misconfigured the licensing steps, the server instances will stop during boot-up sequence.
+
+If you do not check cluster health after adding new servers, and verify that the new servers have joined properly, then you may accidentally take down old servers without replacing them.
+
+If you are using a trial license in production, this could cause issues as the cluster will fail to start once the trial expires.
+
+If you have built automation around `nomad license put`, this command will fail as it has been removed from Nomad v1.1.0+.
+
+## Q: What are some other gotchas?
+
+You might not have access to your organization's Nomad license.
+The  6-hour temporary license window is now removed, and a license is required for proper boot-up.
+Running `nomad agent -dev` without a license will fail.
+
+
+## Q: How can a user get their existing license to put on disk for an upgrade?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires or terminates?
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. The grace
+period is defined as the time between license expiration and license
+termination. (This is typically very short for evaluation licenses, and much longer
+for non-evaluation licenses.) Customers must provide a valid license before the
+grace period expires.
+
+When the license terminates, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write operations
+will return an error. Note that if the server is restarted with a terminated
+license, it will immediately stop.
+
+Clients are unaffected by terminated licenses because clients do not read the
+license.
+
+## Q: Will on-prem binaries with "baked-in" licenses work?
+
+There is no impact to baked-in licensed binaries.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Visit https://nomadproject.io/trial for a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.1.0 to an earlier version?
+
+Nomad cannot safely be rolled back to an earlier version.
+This is not a supported operation due to the Nomad state store not having forward compatibility. The end result could be a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
diff --git a/content/nomad/v1.3.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.3.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..a42ba0b564
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have its own license. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time and a termination time. You
+can read the license on a server with the `nomad license get` command:
+
+```
+$ nomad license get
+Product        = nomad
+License Status = valid
+License ID     = eaaecbd5-b598-4fa4-b649-bb234bf49fa3
+Customer ID    = ae94bdd0-39bf-4c58-bf80-8a9468b0467c
+Issued At      = 2021-03-29 14:47:29.024191 -0400 EDT
+Expires At     = 2021-03-29 20:47:29.024191 -0400 EDT
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+        Dynamic Application Sizing
+```
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. Below shows
+log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license reaches the termination time, enterprise functionality will
+become limited. Only read operations on enterprise endpoints will be supported,
+and write operations will return an error.
+
+Note that if the server is restarted with a terminated license, it will
+immediately stop.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.3.x/content/docs/faq.mdx b/content/nomad/v1.3.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..96cf689e99
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/options#_datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.3.x/content/docs/index.mdx b/content/nomad/v1.3.x/content/docs/index.mdx
new file mode 100644
index 0000000000..38d2a93985
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [HashiCorp Learn "Getting Started" collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.3.x/content/docs/install/index.mdx b/content/nomad/v1.3.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..158fe09457
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/install/index.mdx
@@ -0,0 +1,387 @@
+---
+layout: docs
+page_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/nomad/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](/nomad/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Homebrew on macOS" group="homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Linux Packages" group="linux">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](/consul/tutorials) and
+[Vault](/vault/tutorials) with the same command.
+
+</Tab>
+</Tabs>
+
+## Post-installation steps
+
+These steps are considered optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+<Tabs>
+<Tab heading="Linux Packages">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+
+<Tab heading="macOS">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+</Tab>
+
+<Tab heading="Windows">
+
+<h3>Add the Nomad binary to your system path</h3>
+
+Add a location to your path via the GUI by navigating to `Environment
+Variables` in your system settings, and looking for the variable called `PATH`.
+You should see a semicolon-separated list of locations. Add the Nomad binary's
+location to that list and then launch a new console window.
+</Tab>
+</Tabs>
+</Tab>
+
+<Tab heading="Homebrew on macOS" group="homebrew">
+No additional steps necessary after installing Nomad using Homebrew.
+</Tab>
+
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+No additional steps necessary after installing Nomad using Chocolatey.
+</Tab>
+
+<Tab heading="Linux" group="linux">
+
+Note that if you are running Nomad on Linux, you'll need to run client agents as
+root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+[consul-download]: /consul/downloads
+[destroy]: /vagrant/docs/cli/destroy
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+[gpg-key]: https://apt.releases.hashicorp.com/gpg 'HashiCorp GPG key'
diff --git a/content/nomad/v1.3.x/content/docs/install/production/index.mdx b/content/nomad/v1.3.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..d848748514
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/install/production/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.3.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.3.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..bb12a1a9c1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,197 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
diff --git a/content/nomad/v1.3.x/content/docs/install/quickstart.mdx b/content/nomad/v1.3.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..cbcee32218
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via Learn guides containing embedded Katacoda interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.3.x/content/docs/install/windows-service.mdx b/content/nomad/v1.3.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.3.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.3.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..4576c06ec7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,380 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://nomadproject.io/consul_ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+sudo mkdir -p /opt/cni/bin
+sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad` and running:
+`nomad job run servicemesh.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
diff --git a/content/nomad/v1.3.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.3.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..163ec35904
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/nomad/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](/nomad/tutorials/manage-clusters/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` block](/nomad/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul Template,
+please see the [`template` job specification documentation](/nomad/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_acls]: /consul/docs/security/acl
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_group_namespace]: /nomad/docs/job-specification/group#namespace
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/integrations/index.mdx b/content/nomad/v1.3.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.3.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.3.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..e4f8b2e77f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,475 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` block of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To Submit this job a token that has the `access-kv` policy in the Namespace `engineering`
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /nomad/docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /nomad/docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /nomad/docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.3.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.3.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..539c2f0f88
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the Nomad user's known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /root/.ssh/known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file(pathexpand("~/.ssh/id_rsa")))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.3.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/check.mdx b/content/nomad/v1.3.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..4c42e143e9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,363 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a Consul service.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+from the Consul service provider.
+
+```hcl
+job "job" {
+  group "group" {
+    task "task " {
+      service {
+        check {
+          type     = "tcp"
+          port     = 6379
+          interval = "10s"
+          timeout  = "2s"
+        }
+        # ...
+      }
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul will perform. This is specified using a label suffix like "30s"
+  or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+  If you have more than one check you must specify the name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  Consul will query to query the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`][type] must be `http` or `grpc`, and check `name` must be set.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: <required>)` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. For `checks` on group
+  level `services` only. Inherits the [`service.task`][service_task] value if not
+  set. May only be set for script or gRPC checks.
+
+- `timeout` `(string: <required>)` - Specifies how long Consul will wait for a
+  health check query to succeed. This is specified using a label suffix like
+  "30s" or "1h". This must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. Valid options are `grpc`, `http`, `script`, and `tcp`. gRPC health
+  checks require Consul 1.0.5 or later.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Requires Consul >= 0.7.2.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check. gRPC health checks
+require Consul 1.0.5 or later.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness vs. Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_passfail]: /consul/docs/agent/checks#success-failures-before-passing-critical
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.3.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..1281a64edd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+As of Nomad 0.7 the `check_restart` block instructs Nomad when to restart
+tasks with unhealthy service checks. When a health check in Consul has been
+unhealthy for the `limit` specified in a `check_restart` block, it is
+restarted according to the task group's [`restart` policy][restart_block]. The
+`check_restart` settings apply to [`check`s][check_block], but may also be
+placed on [`service`s][service_block] to apply to all checks on a service.
+If `check_restart` is set on both the check and service, the blocks are
+merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true` treats a `warning` status like `passing` and will not trigger a restart.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`) to pass before a restart is triggered. Once a restart is
+triggered the task group's [`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.3.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..36d3f88a32
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[native]: /consul/docs/connect/native
+[service_task]: /nomad/docs/job-specification/service#task-1 'Nomad service task'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task 'Nomad sidecar task config Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad sidecar service upstreams Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.3.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..18a417002f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,317 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.3.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..f29bc2bfa6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                      = "csi-hostpath"
+  type                    = "monolith"
+  mount_dir               = "/csi"
+  stage_publish__base_dir = "/local/csi"
+  health_timeout          = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/device.mdx b/content/nomad/v1.3.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..c5b55f5059
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,303 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.3.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..482fe10047
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` blocks. Remember that the
+`dispatch_payload` block is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/env.mdx b/content/nomad/v1.3.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.3.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..5b3378b3af
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be removed
+  if an error is encountered. Note that data migration will not take place if a
+  client garbage collects a failed allocation or if the allocation has been
+  intentionally stopped via `nomad alloc stop`, because the original allocation
+  has already been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.3.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..e709e4c464
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.3.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..29d55db1c7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,666 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect Gateways](/consul/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or `grpc`), preconfiguring a [service-default] in Consul to
+  set the [Protocol](/consul/docs/agent/config-entries/service-defaults#protocol)
+  of the service to the desired protocol is mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/agent/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#service-parameters-1
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[service]: /nomad/docs/job-specification/gateway#service-parameters
+[service-default]: /consul/docs/agent/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/group.mdx b/content/nomad/v1.3.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..a64fe83225
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,360 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost". These
+allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' reschedule policy
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements and keep
+the one with the best node score. If the `max_client_disconnect` duration
+expires before the client reconnects, the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+~> **Note:** The `max_client_disconnect` feature is only supported on Nomad
+version 1.3.0 and above. If you run a job with `max_client_disconnect` on servers
+where some servers are not upgraded to 1.3.0, the `max_client_disconnect`
+flag will be _ignored_. Deploying a job with `max_client_disconnect` to a
+`datacenter` of Nomad clients where all clients are not 1.3.0 or above is unsupported.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/group#consul-parameters
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..3ce884109b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..d57583954d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..70aa9ff1b8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection or string.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or string.
+
+If given a list or map, the result is the number of elements in that collection.
+If given a string, the result is the number of characters in the string.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..e535ede487
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..24e760c922
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..0c6e1f1184
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..894ccd891e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..511b20f584
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W)
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..667174c8a1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..47aa267184
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..9db1afc44d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are often referred to as just
+"variables" or "Nomad variables" when it is clear from context what sort of
+variable is being discussed. Other kinds of variables in Nomad include
+_environment variables_ (set by the shell where Nomad runs) and _expression
+variables_ (used to indirectly represent a value in an
+[expression](/nomad/docs/job-specification/hcl2/expressions)).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/docs/configuration/types).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/index.mdx b/content/nomad/v1.3.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..6ba2b01ff1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on a machine.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/job.mdx b/content/nomad/v1.3.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..d1c66c49bf
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,257 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.3.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..ee30bcc11a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about Nomad's task dependencies on the [HashiCorp Learn website][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.3.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..7ace3f6530
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` block allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.3.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..dfca686f51
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any `-` character existing in the key
+will also be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.3.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.3.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..085c191458
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,266 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region
+— the one specified by the `region` field or the `-region` command line
+flag to `nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/network.mdx b/content/nomad/v1.3.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..11eb0b2fda
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,326 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+  for the allocations. By default all DNS configuration is inherited from the client host.
+  DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is neccessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.3.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..a17e72ae87
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.3.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..986c0bb676
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.3.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..fb92934572
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](/consul/docs/connect/proxies/envoy#dynamic-configuration)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.3.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.3.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..72e12ea0f9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Specifies the number of CPU cores to reserve
+  for the task. This may not be used with `cpu`.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Optionally, specifies the maximum memory the task may use, if the client has excess memory capacity, in MB. See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad 1.1. lets job authors set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The new max limit attribute is currently supported by the official `docker`,
+`exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory Oversubscription in the scheduler
+configuration](/nomad/api-docs/operator/scheduler#update-scheduler-configuration). Enterprise customers can use [Resource
+Quotas](/nomad/tutorials/governance-and-policy/quotas) to limit the memory
+oversubscription.
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.3.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..927529d3aa
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a tasks's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.3.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/service.mdx b/content/nomad/v1.3.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..9b56efe404
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,515 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. Only available where
+  `provider = "consul"`. At this time, the Consul integration supports the `grpc`,
+  `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/agent/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.3.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..8197da3029
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.3.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..df7508f636
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.3.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..a99ed8cbfa
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/task.mdx b/content/nomad/v1.3.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..6c027ab4ca
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/docs/drivers/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/template.mdx b/content/nomad/v1.3.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..adc4bced67
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,589 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Since Nomad v0.5.3, the template can reference [Nomad's runtime
+environment variables][env], and since Nomad v0.5.6, the template can reference
+[Node attributes and metadata][nodevars]. Since Nomad v0.6.0, templates can be
+read as environment variables.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] Learn guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The possible values below describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([ChangeScript][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([see below](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user wil be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template inside a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to `consul-template`.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+As of Nomad v0.5.6 it is possible to access the Node's attributes and metadata.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Since v0.6.0 templates may be used to create environment variables for tasks.
+Env templates work exactly like other templates except once the templates are
+written, they are parsed as `KEY=value` pairs. Those key value pairs are
+included in the task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all of the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad:
+
+```
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to task unchanged:
+
+```
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To workaround this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+## Nomad Integration
+
+### Nomad Services
+
+~> Nomad Services are new in Nomad 1.3.
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+~> Simple load balancing with Nomad Services is new in Nomad 1.3.2.
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+## Consul Integration
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault PKI
+role.<br /><br /> Failure to do so will cause the template to frequently render a new
+certificate, approximately every minute. This creates a significant number of
+certificates to be expired in Vault and could ultimately lead to Vault performance
+impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Similar to KV API v1, if the name of a secret includes the `-` character, you
+must access it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default templates can
+  access files only within the [task working directory].
+
+[changescript]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/update.mdx b/content/nomad/v1.3.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..1f196f412a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with CSI volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting no longer applies to service jobs which use
+  [deployments.][strategies]
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.3.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..e00de96680
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/nomad/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway#mesh-gateways
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.3.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..4194450564
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.3.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..ae75f0322b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.3.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.3.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..545379bd62
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.3.x/content/docs/operations/index.mdx b/content/nomad/v1.3.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..96689c203d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/telemetry)
+- [Metrics](/nomad/docs/operations/metrics)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.3.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.3.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..66cb6974cc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,493 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_blocked`           | Evaluations that are blocked until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+| --------------------------------------- | ----------------------------------------------------------------------------------- | ---------- | ----- | ------------------------------------------------------------------------------------- |
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated_disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations waiting for previous versions to exit                         | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating data from previous versions (see [`sticky`][sticky])| Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending (received by the client but not yet running)          | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on the
+task driver; not all task drivers can provide all metrics.
+
+| Metric                                        | Description                                                       | Unit        | Type  | Labels                                           |
+| --------------------------------------------- | ----------------------------------------------------------------- | ----------- | ----- | ------------------------------------------------ |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                    | Unit                 | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------|----------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                    | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                       | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                           | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits) | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern. | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer | Gauge | host |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                     | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                            | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                            | Nanoseconds          | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                   | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                    | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                           | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_update`                       | Time elapsed to apply `AllocUpdate` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Summary` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                 | Integer              | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window       | Integer              | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                               | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                        | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                  | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                              | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                            | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                 | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                    | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                   | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                      | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler_service`        | Time elapsed for worker to invoke the scheduler                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                   | Integer              | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                               | Integer              | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication               | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                       | Integer              | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                   | ms / Raft Log Append | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                               | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                 | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                            | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                           | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                              | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                    | # of bytes           | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                        | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                    | Integer              | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                            | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                    | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                    | Integer              | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                  | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                         | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                             | Float                | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                         | Integer              | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/telemetry/metrics#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://nomadproject.io/s/port-plan-failure
diff --git a/content/nomad/v1.3.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.3.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..81f909b89c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,314 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://www.nomadproject.io/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.broker.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed. Nomad also emits a similar metric for each
+  individual scheduler. For example `nomad.broker.batch_blocked` shows
+  the number of blocked evaluations for the batch scheduler.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/telemetry/metrics#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/telemetry/metrics#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/telemetry/metrics#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/telemetry#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.3.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.3.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..eaa18aad80
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default, any
+stop signal to an agent (interrupt, terminate, kill) will cause the agent to
+forcefully stop. Graceful termination can be configured by either setting
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+When gracefully exiting, servers will notify their intention to leave the
+cluster which allows them to leave the [consensus][] peer set.
+
+It is especially important that a server node be allowed to leave gracefully so
+that there will be a minimal impact on availability as the server leaves the
+consensus peer set. If a server does not gracefully leave, and will not return
+into service, the [`server force-leave` command][] should be used to eject it
+from the consensus peer set.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent][#stopping-an-agent], Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..f6529f0519
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,366 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "write"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When an action is checked against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, the matching rule with the greatest number of matched characters will be
+chosen.
+
+For example the following policy will evaluate to deny for `production-web`,
+because it is 9 characters different from the `"*-web"` rule, but 13 characters
+different from the `"*"` rule.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, or both.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be viewed.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered.
+- `csi-read-volume` - Allows inspecting a CSI volume and seeing fine grain
+  status.
+- `csi-list-volume` - Allows listing CSI volumes and seeing coarse grain status.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                    |
+| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`  | deny                                                                                                                                                                                                                                                            |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                      |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..e094b863be
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,216 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), [`clone_id`](#clone_id),
+[`capacity_min`](#capacity_min), or [`capacity_max`](#capacity_max) fields on
+**volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.3.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.3.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.3.x/content/docs/partnerships.mdx b/content/nomad/v1.3.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..91b42294da
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. For a full description of the current features please refer to the [Nomad Website](/). The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/telemetry)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.3.x/content/docs/runtime/environment.mdx b/content/nomad/v1.3.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..a8d62a66cd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+~> Port labels and task names will have any non-alphanumeric or underscore
+characters in their names replaced by underscores `_` when they're used in
+environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[vault]: /nomad/docs/vault-integration 'Nomad Vault Integration'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.3.x/content/docs/runtime/index.mdx b/content/nomad/v1.3.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..21e6416ae3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.3.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.3.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..b9f852258e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,354 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${node.unique.id}'}</code>
+      </td>
+      <td>36 character unique client identifier</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.region}'}</code>
+      </td>
+      <td>Client's region</td>
+      <td>
+        <code>global</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.datacenter}'}</code>
+      </td>
+      <td>Client's datacenter</td>
+      <td>
+        <code>dc1</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.unique.name}'}</code>
+      </td>
+      <td>Client's name</td>
+      <td>
+        <code>nomad-client-10-1-2-4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${node.class}'}</code>
+      </td>
+      <td>Client's class</td>
+      <td>
+        <code>linux-64bit</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Property given by <code>property</code> on the client
+      </td>
+      <td>
+        <code>{'${attr.cpu.arch} => amd64'}</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}meta.&lt;key&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        Metadata value given by <code>key</code> on the client
+      </td>
+      <td>
+        <code>{'${meta.foo} => bar'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Below is a table documenting common node properties:
+
+<table>
+  <thead>
+    <tr>
+      <th>Property</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.arch}'}</code>
+      </td>
+      <td>
+        CPU architecture of the client (e.g. <code>amd64</code>,{' '}
+        <code>386</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.numcores}'}</code>
+      </td>
+      <td>Number of CPU cores on the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.cpu.totalcompute}'}</code>
+      </td>
+      <td>
+        <code>cpu.frequency &times; cpu.numcores</code> but may be overridden by{' '}
+        <code>client.cpu_total_compute</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.consul.datacenter}'}</code>
+      </td>
+      <td>The Consul datacenter of the client (if Consul is found)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}attr.driver.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>
+        See the <a href="/docs/drivers">task drivers</a> for property
+        documentation
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.hostname}'}</code>
+      </td>
+      <td>Hostname of the client</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.unique.network.ip-address}'}</code>
+      </td>
+      <td>
+        The IP address fingerprinted by the client and from which task ports are
+        allocated
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.arch}'}</code>
+      </td>
+      <td>
+        Kernel architecture of the client (e.g. <code>x86_64</code>, <code>aarch64</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.name}'}</code>
+      </td>
+      <td>
+        Kernel of the client (e.g. <code>linux</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.kernel.version}'}</code>
+      </td>
+      <td>
+        Version of the client kernel (e.g. <code>3.19.0-25-generic</code>,{' '}
+        <code>15.0.0</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.ami-id}'}</code>
+      </td>
+      <td>AMI ID of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-life-cycle}'}</code>
+      </td>
+      <td>Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.instance-type}'}</code>
+      </td>
+      <td>Instance type of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.platform.aws.placement.availability-zone}'}</code>
+      </td>
+      <td>Availability Zone of the client (if on AWS EC2)</td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.name}'}</code>
+      </td>
+      <td>
+        Operating system of the client (e.g. <code>ubuntu</code>,{' '}
+        <code>windows</code>, <code>darwin</code>)
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${attr.os.version}'}</code>
+      </td>
+      <td>Version of the client OS</td>
+    </tr>
+  </tbody>
+</table>
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:7"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.3.x/content/docs/schedulers.mdx b/content/nomad/v1.3.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..48506abccf
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/schedulers.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+## System Batch
+
+~> System Batch scheduling is new in Nomad 1.2.
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.3.x/content/docs/upgrade/index.mdx b/content/nomad/v1.3.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..3314cf3e79
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8
+  to v0.10) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`raft.peers`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `raft.peers` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
diff --git a/content/nomad/v1.3.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.3.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..d42d7dde7f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1468 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol_version`] is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[cores]: /nomad/docs/job-specification/resources#cores
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[migrate]: /nomad/docs/job-specification/migrate
+[nvidia]: /nomad/plugins/devices/nvidia
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`raft_protocol_version`]: /nomad/docs/configuration/server#raft_protocol
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[pki]: /vault/docs/secrets/pki
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[enterprise licensing]: /nomad/docs/enterprise/license
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[`log_file`]: /nomad/docs/configuration#log_file
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
diff --git a/content/nomad/v1.3.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.3.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..4dd4b333dd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.3.x/content/intro/index.mdx b/content/nomad/v1.3.x/content/intro/index.mdx
new file mode 100644
index 0000000000..901b2c71e9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [HashiCorp Learn guides](/nomad/tutorials) provides a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) and [Who Uses Nomad](/nomad/intro/who-uses-nomad) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.3.x/content/intro/use-cases.mdx b/content/nomad/v1.3.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..35d1aec940
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.3.x/content/intro/vs/ecs.mdx b/content/nomad/v1.3.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.3.x/content/intro/vs/index.mdx b/content/nomad/v1.3.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.3.x/content/intro/vs/mesos.mdx b/content/nomad/v1.3.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.3.x/content/intro/vs/terraform.mdx b/content/nomad/v1.3.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.3.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.3.x/content/partials/envvars.mdx b/content/nomad/v1.3.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..b13911dd85
--- /dev/null
+++ b/content/nomad/v1.3.x/content/partials/envvars.mdx
@@ -0,0 +1,63 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                   |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                     |
+| `NOMAD_SECRETS_DIR`      | Path to the task's secrets directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                        |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                 |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                           |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                   |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request cpu cores. E.g. `0-2,7,12-14`                                                                                                                                        |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                       |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                          |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index. |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                     |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                    |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through CLI but can be different when using the API                                                                                                                                                                     |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                      |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                            |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                   |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                     |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                    |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                       |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Note that this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata.                                                                          |
+| `VAULT_TOKEN`            | The task's Vault token. See [Vault Integration](/nomad/docs/integrations/vault-integration) for more details                                                                                                                                                                    |
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                                                                                          |
+|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See [here for more](/nomad/docs/job-specification/network) information.                                                                                                                                                                                                                |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See [here for more](/nomad/docs/job-specification/network) information.                                                                         |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                                                                                      |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See [here](/nomad/docs/job-specification/network#mapped-ports) for more information.                                                                                                                                                                                                |
+| `NOMAD_IP_<task>_<label>`          | **Deprecated**. Host IP for the given port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                                        |
+| `NOMAD_PORT_<task>_<label>`        | **Deprecated**. Port for the given port `label` and `task` for tasks in the same task group. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. Only available when setting ports via the task resource network port mapping. |
+| `NOMAD_ADDR_<task>_<label>`        | **Deprecated**. Host `IP:Port` pair for the given port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                            |
+| `NOMAD_HOST_PORT_<task>_<label>`   | **Deprecated**.  Port on the host for the port `label` and `task` for tasks in the same task group. Only available when setting ports via the task resource network port mapping.                                                                                                                                    |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                                           |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                                         |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                               |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+
+~> **Note:** Port labels and task names will have any non-alphanumeric or
+  underscore characters in their names replaced by underscores `_` when they're
+  used in environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+### Consul-related Variables
+
+This variables are only set for Connect native tasks.
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a tcp address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Connect service identity token specific to the service instance if Consul ACLs are enabled. |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the CLient Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
diff --git a/content/nomad/v1.3.x/content/partials/general_options.mdx b/content/nomad/v1.3.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..bb9ece3878
--- /dev/null
+++ b/content/nomad/v1.3.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespaces authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.3.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.3.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.3.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.3.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.3.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.3.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.3.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.3.x/content/plugins/devices/index.mdx b/content/nomad/v1.3.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.3.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.3.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..06dcbc2076
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
\ No newline at end of file
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..5aa129c9cd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..6620f08eec
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[rkt]: /nomad/plugins/drivers/community/rkt
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..3a0a46f932
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionaly, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..0bc5c66b99
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..dfbb3dfb11
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:7"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /nomad/docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.3.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/index.mdx b/content/nomad/v1.3.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.3.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..66a7735a3a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,580 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+Due to Podman's similarity to Docker, the example job created by
+[`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- [Nomad][nomad_download] 0.12.9+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroup V2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a 3.0.x podman binary and a system socket activation unit, refer to
+[https://www.redhat.com/sysadmin/podmans-new-rest-api](https://www.redhat.com/sysadmin/podmans-new-rest-api).
+
+Nomad agent, `nomad-driver-podman` and `podman` will reside on the same client,
+so you do not have to worry about the `ssh` aspects of the Podman api.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed the the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart. Consider a
+  simple single node system and a complete reboot. All previously managed
+  containers will be reused instead of disposed and recreated.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads.html
+[nomad_driver_ports]: /nomad/docs/drivers/docker.html#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.3.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..b4346bd020
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.3.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.3.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..d2c3a0eff1
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]:  /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.3.x/content/plugins/index.mdx b/content/nomad/v1.3.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..87d3059efd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.3.x/content/security.mdx b/content/nomad/v1.3.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.3.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..a3e1b2b40d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..3be91a4592
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+### `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..ca630dff4c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..0b9d8d8bcd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+### `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..53b856fba9
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+### `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..b260938ade
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+}
+```
+
+### `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7dc1b03f3d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+### `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/source.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/source.mdx
new file mode 100644
index 0000000000..ac6796fc0b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/source.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: source Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "source" block is used to configure scaling target sources.
+---
+
+# `source` Block
+
+<Placement groups={['policy', 'source']} />
+
+The `source` block is used to configure scaling target sources.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+Supported sources are `file` and `nomad`.
+
+### `source` Parameters
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..3df89428c7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+### `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..9a0b2b0e2a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+### `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..37f6cb7f90
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+### `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus`
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e46c4321cf
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..6cdefb0e78
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,191 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/checks.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/checks.mdx
new file mode 100644
index 0000000000..716ce8633c
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/checks.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Nomad Autoscaler Check Calculations
+
+A scaling policy can include several checks all of which produce a scaling
+suggesting. The checks are executed at the same time during a policy evaluation
+and the results can conflict with each other. In a scenario like this, the
+autoscaler iterates the results the chooses the safest result which results in
+retaining the most capacity of the resource.
+
+In a scenario where two checks return different desired directions, the following
+logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the two same actions are suggested, but with different counts the
+following logic is applied, where the count is the absolute desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/index.mdx
new file mode 100644
index 0000000000..9b59013203
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: docs
+page_title: Internals
+description: >
+  This section covers the internals of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Internals
+
+This section covers the internals of the Nomad Autoscaler and explains the
+technical details of how it functions, its architecture, and sub-systems.
+
+- [Autoscaler plugins](/nomad/tools/autoscaling/internals/plugins)
+- [Check calculations](/nomad/tools/autoscaling/internals/checks)
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/node-selector-strategy.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/apm.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/base.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/strategy.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/target.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/internals/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..b27c91f8cc
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "percentage-allocated_cpu"
+  ...
+}
+```
+
+Querying Nomad client node metrics is be done using the `operation_metric` syntax,
+where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+  for the allocation.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+  allocated for the allocation.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..e8b5372bfa
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..715b99f950
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin will perform count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..b63165282a
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-traffic" {
+    # ...
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound valus to trigger the action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d91143a086
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..be73d89137
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..93b9adf014
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..1fff32c1d2
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..70ab2f9654
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,245 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.3.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.3.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..9113f451e7
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.3.x/content/tools/index.mdx b/content/nomad/v1.3.x/content/tools/index.mdx
new file mode 100644
index 0000000000..21ca93893e
--- /dev/null
+++ b/content/nomad/v1.3.x/content/tools/index.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+- [OpenAPI](https://github.com/hashicorp/nomad-openapi) - An OpenAPI/Swagger spec for Nomad, allowing for programmatic generation of SDKs and documentation. Includes a reference implementation in Go built on top of a generated client.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.3.x/data/api-docs-nav-data.json b/content/nomad/v1.3.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..95efba8cc2
--- /dev/null
+++ b/content/nomad/v1.3.x/data/api-docs-nav-data.json
@@ -0,0 +1,149 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL Policies",
+    "path": "acl-policies"
+  },
+  {
+    "title": "ACL Tokens",
+    "path": "acl-tokens"
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.3.x/data/docs-nav-data.json b/content/nomad/v1.3.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..1e2d4f8b02
--- /dev/null
+++ b/content/nomad/v1.3.x/data/docs-nav-data.json
@@ -0,0 +1,1948 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Service Mesh",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy apply",
+            "path": "commands/acl/policy-apply"
+          },
+          {
+            "title": "policy delete",
+            "path": "commands/acl/policy-delete"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/acl/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/acl/policy-list"
+          },
+          {
+            "title": "token create",
+            "path": "commands/acl/token-create"
+          },
+          {
+            "title": "token delete",
+            "path": "commands/acl/token-delete"
+          },
+          {
+            "title": "token info",
+            "path": "commands/acl/token-info"
+          },
+          {
+            "title": "token list",
+            "path": "commands/acl/token-list"
+          },
+          {
+            "title": "token self",
+            "path": "commands/acl/token-self"
+          },
+          {
+            "title": "token update",
+            "path": "commands/acl/token-update"
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.3.x/data/intro-nav-data.json b/content/nomad/v1.3.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..7abd058898
--- /dev/null
+++ b/content/nomad/v1.3.x/data/intro-nav-data.json
@@ -0,0 +1,56 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "https://learn.hashicorp.com/collections/nomad/get-started"
+      },
+      {
+        "title": "Running Nomad",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-run"
+      },
+      {
+        "title": "Jobs",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs"
+      },
+      {
+        "title": "Clustering",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster"
+      },
+      {
+        "title": "Web UI",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui"
+      },
+      {
+        "title": "Next Steps",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.3.x/data/plugins-nav-data.json b/content/nomad/v1.3.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..2e1b3e9fcc
--- /dev/null
+++ b/content/nomad/v1.3.x/data/plugins-nav-data.json
@@ -0,0 +1,107 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt <sup>Deprecated</sup> ",
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB <sup>Beta</sup>",
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.3.x/data/tools-nav-data.json b/content/nomad/v1.3.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..cc589f40e7
--- /dev/null
+++ b/content/nomad/v1.3.x/data/tools-nav-data.json
@@ -0,0 +1,218 @@
+[
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "path": "autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "path": "autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "path": "autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.3.x/img/count-dashboard.png b/content/nomad/v1.3.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.3.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.3.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.3.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.3.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/favicon-16x16.png b/content/nomad/v1.3.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/favicon-194x194.png b/content/nomad/v1.3.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/favicon-32x32.png b/content/nomad/v1.3.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/favicon.ico b/content/nomad/v1.3.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.3.x/img/favicons/mstile-144x144.png b/content/nomad/v1.3.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/mstile-150x150.png b/content/nomad/v1.3.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/mstile-310x150.png b/content/nomad/v1.3.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/mstile-310x310.png b/content/nomad/v1.3.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/mstile-70x70.png b/content/nomad/v1.3.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.3.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.3.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.3.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.3.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.3.x/img/home-hero-pattern.svg b/content/nomad/v1.3.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.3.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/img/logo-hashicorp.svg b/content/nomad/v1.3.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..070d9732c2
--- /dev/null
+++ b/content/nomad/v1.3.x/img/logo-hashicorp.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11zM77 7.86V4.63h-3v3.23h-1.42V.11h1.51v3.25h3V.11h1.51v7.75zm7 0h-1.2l-.11-.38A3.3 3.3 0 0 1 81 8c-1.06 0-1.52-.7-1.52-1.66 0-1.14.51-1.57 1.7-1.57h1.4v-.62c0-.62-.18-.84-1.11-.84-.54.005-1.08.062-1.61.17l-.18-1.07a8 8 0 0 1 2-.26c1.83 0 2.37.62 2.37 2zm-1.39-2.11h-1.07c-.48 0-.61.13-.61.55s.13.56.59.56a2.4 2.4 0 0 0 1.1-.29zM87.13 8a7.1 7.1 0 0 1-2-.32l.2-1.07a6.8 6.8 0 0 0 1.73.24c.65 0 .74-.14.74-.56s-.07-.52-1-.73c-1.42-.33-1.59-.68-1.59-1.76s.51-1.62 2.18-1.62q.887.004 1.75.2L89 3.46a10.6 10.6 0 0 0-1.6-.16c-.63 0-.74.14-.74.48s0 .48.82.68c1.63.41 1.78.62 1.78 1.77S88.88 8 87.13 8m6.68-.11V4c0-.3-.13-.45-.47-.45-.53.05-1.047.203-1.52.45v3.86h-1.46V0l1.46.22v2.47a5.3 5.3 0 0 1 2.13-.54c1 0 1.32.65 1.32 1.65v4.06zm2.68-6.38V.11h1.46v1.37zm0 6.38V2.27h1.46v5.59zm2.62-5.54c0-1.4.85-2.22 2.83-2.22.727 0 1.452.083 2.16.25l-.17 1.25a12 12 0 0 0-1.95-.2c-1 0-1.37.34-1.37 1.16V5.5c0 .81.33 1.16 1.37 1.16a12 12 0 0 0 1.95-.2l.17 1.25a9.4 9.4 0 0 1-2.16.25c-2 0-2.83-.81-2.83-2.22zM107.33 8c-2 0-2.53-1.06-2.53-2.2V4.36c0-1.15.54-2.2 2.53-2.2s2.53 1.06 2.53 2.2v1.41c0 1.15-.54 2.23-2.53 2.23m0-4.63c-.78 0-1.08.33-1.08 1v1.5c0 .63.3 1 1.08 1s1.08-.33 1.08-1V4.31c-.01-.63-.3-.96-1.08-.96zm6.64.09a11.5 11.5 0 0 0-1.54.81v3.6H111v-5.6h1.23l.1.62c.477-.308.99-.553 1.53-.73zM119.8 6a1.72 1.72 0 0 1-.46 1.48 1.72 1.72 0 0 1-1.46.52 8.5 8.5 0 0 1-1.55-.16v2.26l-1.46.22v-8H116l.14.47a3.16 3.16 0 0 1 1.86-.64c1.17 0 1.79.67 1.79 1.94zm-3.48.63q.637.138 1.29.15c.53 0 .73-.24.73-.75v-2c0-.46-.18-.71-.72-.71-.48.018-.937.197-1.3.51z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.3.x/img/logo-text.svg b/content/nomad/v1.3.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.3.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.3.x/img/nomad-architecture-global.png b/content/nomad/v1.3.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.3.x/img/nomad-architecture-region.png b/content/nomad/v1.3.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.3.x/img/nomad-bg-pattern.svg b/content/nomad/v1.3.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.3.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.3.x/img/nomad-data-model.png b/content/nomad/v1.3.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.3.x/img/nomad-evaluation-flow.png b/content/nomad/v1.3.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.3.x/img/nomad-kubernetes.png b/content/nomad/v1.3.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.3.x/img/nomad-panel-learn.svg b/content/nomad/v1.3.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.3.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.3.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.3.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.3.x/img/nomad-workload.png b/content/nomad/v1.3.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.3.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.3.x/img/og-image.png b/content/nomad/v1.3.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.3.x/img/og-image.png differ
diff --git a/content/nomad/v1.3.x/img/pattern.svg b/content/nomad/v1.3.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.3.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/img/practice-pattern.svg b/content/nomad/v1.3.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.3.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/img/usecase-callout-pattern.svg b/content/nomad/v1.3.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.3.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/img/usecase-hero-pattern.svg b/content/nomad/v1.3.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.3.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.3.x/redirects.jsonc b/content/nomad/v1.3.x/redirects.jsonc
new file mode 100644
index 0000000000..7171e4287c
--- /dev/null
+++ b/content/nomad/v1.3.x/redirects.jsonc
@@ -0,0 +1,1406 @@
+[
+  // Define your custom redirects within this file.
+  // Vercel"s redirect documentation: https://nextjs.org/docs/api-reference/next.config.js/redirects
+  // Relative paths with fragments (#) are not supported. For destinations with fragments use an absolute URL.
+  // Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+  {
+    "source": "/home",
+    "destination": "/",
+    "permanent": true,
+  },
+
+  // Friendly URL for trial form redirection
+  {
+    "source": "/trial",
+    "destination": "https://www.hashicorp.com/products/nomad/trial",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/overview",
+    "destination": "/docs/operations",
+    "permanent": true,
+  },
+
+  // This redirect supports a URL built into the Nomad UI, and should always be
+  // directed someplace valid to support the text "Read about Outage Recovery."
+  {
+    "source": "/guides/outage.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  // Nomad Learn Redirects
+  {
+    "source": "/intro/getting-started",
+    "destination": "https://learn.hashicorp.com/collections/nomad/get-started",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/install",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-install",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/running",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-run",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-cluster",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/ui",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/getting-started/next-steps",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/vs/kubernetes",
+    "destination": "/docs/nomad-vs-kubernetes",
+    "permanent": true,
+  },
+  {
+    "source": "/intro/who-uses-nomad",
+    "destination": "/docs/who-uses/noamd",
+    "permanent": true,
+  },
+  // Guides
+  {
+    "source": "/guides/load-balancing",
+    "destination": "https://learn.hashicorp.com/collections/nomad/load-balancing",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/fabio",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/nginx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/haproxy",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/load-balancing/traefik",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/stateful-workloads",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/stateful-workloads",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/host-volumes",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/stateful-workloads/portworx",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/web-ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/access.html",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/accessing",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/web-ui-access",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/submitting-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/operating-a-job",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/inspecting-the-cluster",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/web-ui/securing",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/governance-and-policy",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/governance-and-policy",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/governance-and-policy/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  // /s/* redirects for useful links that need a stable URL but we may need to
+  // change its destination in the future.
+  {
+    "source": "/s/port-plan-failure",
+    "destination":
+      "https://www.nomadproject.io/docs/operations/monitoring-nomad#progress",
+    "permanent": false,
+  },
+
+  // Spark guide links are all repointed to deprecated nomad-spark repo
+  {
+    "source": "/guides/spark",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/spark/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/analytical-workloads/:splat*",
+    "destination": "https://github.com/hashicorp/nomad-spark",
+    "permanent": true,
+  },
+  // These are subsumed in the splat over analytical-workloads, but I"m keeping them here in case
+  // we want to reclaim the slug "analytical-workloads" at some point and deal with some bad links.
+  // {
+  //   "source": "/guides/analytical-workloads/spark/spark",
+  //   "destination": "https://github.com/hashicorp/nomad-spark",
+  //   "permanent": true,
+  // },
+
+  {
+    "source": "/guides/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspec",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/affinity",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/affinity",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/advanced-scheduling/preemption-service-batch",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/advanced-scheduling/spread",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/spread",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operating-a-job/update-strategies",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-strategies",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/manage-clusters",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/monitoring",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring-and-alerting/prometheus-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/monitoring/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/vault-pki-integration",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad",
+    "permanent": true,
+  },
+
+  // Multi-part UI guides
+  {
+    "source": "/guides/ui",
+    "destination": "https://learn.hashicorp.com/collections/nomad/web-ui",
+    "permanent": true,
+  },
+
+  // Website
+  // Docs
+  {
+    "source": "/docs/index",
+    "destination": "/docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/api-docs/index",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/config",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/nvidia",
+    "destination": "/plugins/devices/nvidia",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/taskconfig",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/inspecting",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/resources",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/updating",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobops/servicediscovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/interpreted",
+    "destination": "/docs/runtime/interpolation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/json",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/environment",
+    "destination": "/docs/runtime/environment",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/servicediscovery",
+    "destination": "/docs/job-specification/service",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/jobspec/networking",
+    "destination": "/docs/job-specification/network",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/job-specification/index",
+    "destination": "/docs/job-specification",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/cluster/requirements",
+    "destination": "/docs/install/production/requirements/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-index",
+    "destination": "/docs/commands/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-list-peers",
+    "destination": "/docs/commands/operator/raft-list-peers",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/operator-raft-remove-peer",
+    "destination": "/docs/commands/operator/raft-remove-peer",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/job-dispatch",
+    "destination": "/docs/commands/job/dispatch",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/alloc-status",
+    "destination": "/docs/commands/alloc/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/eval-status",
+    "destination": "/docs/commands/eval/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/fs",
+    "destination": "/docs/commands/alloc/fs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/logs",
+    "destination": "/docs/commands/alloc/logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/init",
+    "destination": "/docs/commands/job/init",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/inspect",
+    "destination": "/docs/commands/job/inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/run",
+    "destination": "/docs/commands/job/run",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/stop",
+    "destination": "/docs/commands/job/stop",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/plan",
+    "destination": "/docs/commands/job/plan",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/validate",
+    "destination": "/docs/commands/job/validate",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/client-config",
+    "destination": "/docs/commands/node/config",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-drain",
+    "destination": "/docs/commands/node/drain",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/node-status",
+    "destination": "/docs/commands/node/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keygen",
+    "destination": "/docs/commands/operator/keygen",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/keyring",
+    "destination": "/docs/commands/operator/keyring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-force-leave",
+    "destination": "/docs/commands/server/force-leave",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-join",
+    "destination": "/docs/commands/server/join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/commands/server-members",
+    "destination": "/docs/commands/server/members",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/runtime/schedulers",
+    "destination": "/docs/schedulers",
+    "permanent": true,
+  },
+
+  // Sometimes code names are too good not to mention
+  {
+    "source": "/heartyeet",
+    "destination":
+      "https://www.nomadproject.io/docs/job-specification/group#stop_after_client_disconnect",
+    "permanent": true,
+  },
+
+  // Moved /docs/drivers/external/podman -> /docs/drivers/podman
+  {
+    "source": "/docs/drivers/external/podman",
+    "destination": "/plugins/drivers/podman",
+    "permanent": true,
+  },
+
+  // Moved /docs/operating-a-job/ -> /guides/operating-a-job/
+  {
+    "source": "/docs/operating-a-job",
+    "destination": "https://learn.hashicorp.com/collections/nomad/manage-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/accessing-logs",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/inspecting-state",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-inspect",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/resource-utilization",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-utilization",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/configuring-tasks",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-configuring",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/submitting-jobs",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/jobs-submit",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/job-failure-handling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/check-restart",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-check-restart",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/reschedule",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/failures-reschedule",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/failure-handling-strategies/restart",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/failures-restart",
+    "permanent": true,
+  },
+
+  {
+    "source": "/docs/operating-a-job/update-strategies",
+    "destination": "https://learn.hashicorp.com/collections/nomad/job-updates",
+    "permanent": true,
+  },
+  {
+    "source":
+      "/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/handling-signals",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operating-a-job/update-strategies/rolling-upgrades",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/job-rolling-update",
+    "permanent": true,
+  },
+
+  // Moved /docs/agent/configuration/ -> /docs/configuration/ 301!
+  {
+    "source": "/docs/agent/configuration",
+    "destination": "/docs/configuration",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/acl",
+    "destination": "/docs/configuration/acl",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/autopilot",
+    "destination": "/docs/configuration/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/client",
+    "destination": "/docs/configuration/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/consul",
+    "destination": "/docs/configuration/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/sentinel",
+    "destination": "/docs/configuration/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server",
+    "destination": "/docs/configuration/server",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/server_join",
+    "destination": "/docs/configuration/server_join",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/telemetry",
+    "destination": "/docs/configuration/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/tls",
+    "destination": "/docs/configuration/tls",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/configuration/vault",
+    "destination": "/docs/configuration/vault",
+    "permanent": true,
+  },
+  // Moved telemetry under operations
+  {
+    "source": "/docs/telemetry",
+    "destination": "/docs/operations/telemetry",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/telemetry/metrics",
+    "destination": "/docs/operations/metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/metrics",
+    "destination": "/docs/operations/metrics-reference",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/operations/telemetry",
+    "destination": "/docs/operations/monitoring-nomad",
+    "permanent": true,
+  },
+
+  // Moved installing agent under operations as ope
+  {
+    "source": "/docs/install/production/nomad-agent",
+    "destination": "/docs/operations/nomad-agent",
+    "permanent": true,
+  },
+
+  // Moved guide-like docs to /guides
+  {
+    "source": "/docs/agent",
+    "destination": "/docs/install/production/nomad-agent/",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/cloud_auto_join",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/telemetry",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/agent/encryption",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/service-discovery",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+
+  // Redirect old LXC driver doc to new one in /docs/external
+  {
+    "source": "/docs/drivers/lxc",
+    "destination": "/plugins/drivers/community/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/rkt",
+    "destination": "/plugins/drivers/community/rkt",
+    "permanent": true,
+  },
+
+  // API
+  {
+    "source": "/docs/http/agent-force-leave",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-join",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-members",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-self",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/agent-servers",
+    "destination": "/api-docs/agent",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/alloc",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/allocs",
+    "destination": "/api-docs/allocations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-allocation-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-fs",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/client-stats",
+    "destination": "/api-docs/client",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/eval",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/evals",
+    "destination": "/api-docs/evaluations",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http",
+    "destination": "/api-docs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/job",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/jobs",
+    "destination": "/api-docs/jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/json-jobs",
+    "destination": "/api-docs/json-jobs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/node",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/nodes",
+    "destination": "/api-docs/nodes",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/operator",
+    "destination": "/api-docs/operator",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/regions",
+    "destination": "/api-docs/regions",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/status",
+    "destination": "/api-docs/status",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/http/system",
+    "destination": "/api-docs/system",
+    "permanent": true,
+  },
+
+  // Guides
+
+  // Reorganized Guides by Persona
+  {
+    "source": "/guides/autopilot",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/autopilot",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/automatic",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/cluster/bootstrapping",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/manual",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/clustering",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/federation",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/federation",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/cluster/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/nomad-metrics",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/node-draining",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/node-drain",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/outage",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/outage-recovery",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/acl",
+    "destination": "https://learn.hashicorp.com/collections/nomad/access-control",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/securing-nomad",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/security-enable-tls",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/security/namespaces",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/quotas",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel/job",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/security/sentinel-policy",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/sentinel",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/install/index",
+    "destination": "/docs/install",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/agent/index",
+    "destination": "/docs/install/production/nomad-agent",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/requirements",
+    "destination": "/docs/install/production/requirements",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/consul-integration/index",
+    "destination": "/docs/integrations/consul-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/vault-integration/index",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/advanced-scheduling",
+    "destination":
+      "https://learn.hashicorp.com/collections/nomad/advanced-scheduling",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external",
+    "destination": "https://learn.hashicorp.com/collections/nomad/plugins",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/external/lxc",
+    "destination": "https://learn.hashicorp.com/tutorials/nomad/plugin-lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade",
+    "destination": "/docs/upgrade",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/upgrade/upgrade-specific",
+    "destination": "/docs/upgrade/upgrade-specific",
+    "permanent": true,
+  },
+
+  {
+    "source": "/guides/operations/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/guides/operations/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/deployment-guide",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/install/production/reference-architecture",
+    "destination":
+      "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul",
+    "permanent": true,
+  },
+
+  // Enterprise
+
+  // Reorganized Enterprise into single pager
+  {
+    "source": "/docs/enterprise/namespaces",
+    "destination": "https://www.nomadproject.io/docs/enterprise#namespaces",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/quotas",
+    "destination": "https://www.nomadproject.io/docs/enterprise#resource-quotas",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/preemption",
+    "destination": "https://www.nomadproject.io/docs/enterprise#preemption",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/sentinel",
+    "destination":
+      "https://www.nomadproject.io/docs/enterprise#sentinel-policies",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/enterprise/autopilot",
+    "destination":
+      "https://www.nomadproject.io/docs/enterprise#nomad-enterprise-platform",
+    "permanent": true,
+  },
+
+  // Guide Catch-all Redirects
+  {
+    "source": "/guides/:splat*",
+    "destination": "https://learn.hashicorp.com/nomad",
+    "permanent": true,
+  },
+
+  // Vault Integration
+  {
+    "source": "/docs/vault-integration",
+    "destination": "/docs/integrations/vault-integration",
+    "permanent": true,
+  },
+  // Old resources -> Community
+  {
+    "source": "/resources",
+    "destination": "/community",
+    "permanent": true,
+  },
+  // `/<path>/index.html` to /<path>
+  {
+    "source": "/:splat*/index.html",
+    "destination": "/:splat*",
+    "permanent": true,
+  },
+  // `.html` to non-`.html`
+  {
+    "source": "/:splat(.*).html",
+    "destination": "/:splat",
+    "permanent": true,
+  },
+  // Extracted content into `/plugins` & `/tools`
+  {
+    "source": "/docs/autoscaling",
+    "destination": "/tools/autoscaling",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/autoscaling/:splat*",
+    "destination": "/tools/autoscaling/:splat*",
+    "permanent": true,
+  },
+  // Extracted content into `/plugins` & `/tools`
+  // - Redirect individual pages so we don"t conflict with
+  //   "built-in plugins" pages
+  {
+    "source": "/docs/devices/external",
+    "destination": "/plugins/devices/community",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/external/usb",
+    "destination": "/plugins/devices/community/usb",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/devices/external/nvidia",
+    "destination": "/plugins/devices/nvidia",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/containerd",
+    "destination": "/plugins/drivers/community/containerd",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/firecracker-task-driver",
+    "destination": "/plugins/drivers/community/firecracker-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/iis",
+    "destination": "/plugins/drivers/community/iis",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external",
+    "destination": "/plugins/drivers/community",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/jail-task-driver",
+    "destination": "/plugins/drivers/community/jail-task-driver",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/lightrun",
+    "destination": "/plugins/drivers/community/lightrun",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/lxc",
+    "destination": "/plugins/drivers/community/lxc",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/nspawn",
+    "destination": "/plugins/drivers/community/nspawn",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/pot",
+    "destination": "/plugins/drivers/community/pot",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/rkt",
+    "destination": "/plugins/drivers/community/rkt",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/rookout",
+    "destination": "/plugins/drivers/community/rookout",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/external/singularity",
+    "destination": "/plugins/drivers/community/singularity",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/podman",
+    "destination": "/plugins/drivers/podman",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/remote/ecs",
+    "destination": "/plugins/drivers/remote/ecs",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/drivers/remote",
+    "destination": "/plugins/drivers/remote",
+    "permanent": true,
+  },
+  {
+    "source": "/api/:path*",
+    "destination": "/api-docs/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/internals/:path*",
+    "destination": "/docs/concepts/:path*",
+    "permanent": true,
+  },
+
+  // Redirects for exact versioned-docs to respective generic versions
+  {
+    "source": "/:base(docs|api-docs)/v1.:minor([0-2]{1,}).(\\d+)",
+    "destination": "/:base/v1.:minor.x",
+    "permanent": true,
+  },
+  {
+    "source": "/:base(docs|api-docs)/v1.:minor([0-2]{1,}).(\\d+)/:path*",
+    "destination": "/:base/v1.:minor.x/:path",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.4.x/content/api-docs/acl/index.mdx b/content/nomad/v1.4.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..a48dfb6875
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes
+ACL bootstrapping, ACL Policies, ACL Roles, and ACL Tokens. For more details
+about ACLs, please see the
+[ACL Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.4.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.4.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..4e07722b8c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,188 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given
+  namespace, job, group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - The namespace to attach the policy.
+    Required if `JobID` is set.
+
+  - `JobID` `(string: <optional>)` - The job to attach to the policy. Required
+    if `Group` is set.
+
+  - `Group` `(string: <optional>)` - The group to attach to the policy.
+    Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - The task to attach to the policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.4.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.4.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..d99aa9efaf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `POST` | `/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                 | Produces       |
+| -------- | -------------------- | -------------- |
+| `DELETE` | `/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.4.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..6b4d014a0c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.4.x/content/api-docs/agent.mdx b/content/nomad/v1.4.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..5e70a2af66
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/agent.mdx
@@ -0,0 +1,927 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.4.x/content/api-docs/allocations.mdx b/content/nomad/v1.4.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..b008dbbe51
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/allocations.mdx
@@ -0,0 +1,960 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.4.x/content/api-docs/client.mdx b/content/nomad/v1.4.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..a03ef02c1d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/client.mdx
@@ -0,0 +1,670 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client statistics and inspect
+  allocations running on a particular client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Since Nomad 0.8.0, both a client and server can handle client endpoints. This is
+particularly useful for when a direct connection to a client is not possible due
+to the network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node should
+be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                       | Produces     |
+| ------ | -------------------------- | ------------ |
+| `GET`  | `/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                      | Produces     |
+| ------ | ------------------------- | ------------ |
+| `GET`  | `/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                        | Produces     |
+| ------ | --------------------------- | ------------ |
+| `GET`  | `/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://nomad.rocks/v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path         | Produces     |
+| ------ | ------------ | ------------ |
+| `GET`  | `/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/client/gc
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/deployments.mdx b/content/nomad/v1.4.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/evaluations.mdx b/content/nomad/v1.4.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..db1bce0e4b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,446 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.4.x/content/api-docs/events.mdx b/content/nomad/v1.4.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..aa826c6b4e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/events.mdx
@@ -0,0 +1,397 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock": "true",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "mock_driver": {
+              "Attributes": {
+                "driver.mock": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445193068-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/index.mdx b/content/nomad/v1.4.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..55713ae728
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/index.mdx
@@ -0,0 +1,699 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> --data-urlencode 'filter=<filter expression>'
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/jobs \
+    --data-urlencode 'filter=Datacenters contains "dc2"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/deployments \
+    --data-urlencode 'filter=Status != "successful"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.4.x/content/api-docs/jobs.mdx b/content/nomad/v1.4.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..914a605570
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2366 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and reregistered.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `IdempotencyToken` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their reschedule limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.4.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..a8ea3c0ab2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1193 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad
+$ nomad job run -output example.nomad
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Id": "",
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": ""
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
diff --git a/content/nomad/v1.4.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.4.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..0f3738ffc7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.4.x/content/api-docs/metrics.mdx b/content/nomad/v1.4.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/namespaces.mdx b/content/nomad/v1.4.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f1050081cc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,205 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota"
+}
+```
+
+Note that the `Quota` key is Enterprise-only.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/nodes.mdx b/content/nomad/v1.4.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..893da76437
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1150 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "mock_driver": {
+      "Attributes": {
+        "driver.mock": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687978919+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.4.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..76bc8d1346
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/index.mdx b/content/nomad/v1.4.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.4.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..ad4975c121
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,157 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/license.mdx b/content/nomad/v1.4.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.4.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..b6313223f0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.4.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..fdad37cda3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,202 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+    `true`, tasks may exceed their reserved memory limit, if the client has excess
+    memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+  `true`, tasks may exceed their reserved memory limit, if the client has excess
+  memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription.
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.4.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.4.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.4.x/content/api-docs/plugins.mdx b/content/nomad/v1.4.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..f6676906c1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/plugins.mdx
@@ -0,0 +1,137 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/quotas.mdx b/content/nomad/v1.4.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..112d80d7e9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/quotas.mdx
@@ -0,0 +1,354 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/recommendations.mdx b/content/nomad/v1.4.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/regions.mdx b/content/nomad/v1.4.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.4.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/search.mdx b/content/nomad/v1.4.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..4c3762ffb0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/search.mdx
@@ -0,0 +1,589 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                     |
+| ---------------- | -------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs` |
+
+When ACLs are enabled, requests must have a token valid for `node:read` or
+`namespace:read-jobs` roles. If the token is only valid for `node:read`, then
+job related results will not be returned. If the token is only valid for
+`namespace:read-jobs`, then node results will not be returned.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given search
+term and context, where a context can be jobs, allocations, nodes, plugins, or namespaces.
+Additionally, fuzzy searching can be done across all contexts. For better control
+over the performance implications of fuzzy searching on Nomad servers, aspects of
+fuzzy searching can be tuned through the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `node:read, namespace:read-jobs, namespace:csi-list-plugin` |
+
+When ACLs are enabled, requests must have a token valid for `node:read`, `plugin:read` or
+`namespace:read-jobs` roles. If the token is only valid for a portion of these
+capabilities, then results will include results including only data readable with
+the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "plugins", or
+  "all", where "all" means every context will be searched. When "all" is selected,
+  additional prefix matches will be included for the "deployments", "evals", and
+  "volumes" types. When searching in the "jobs" context, results that fuzzy match
+  "groups", "services", "tasks", "images", "commands", and "classes" are also
+  included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.4.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.4.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/services.mdx b/content/nomad/v1.4.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.4.x/content/api-docs/status.mdx b/content/nomad/v1.4.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/system.mdx b/content/nomad/v1.4.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/ui.mdx b/content/nomad/v1.4.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.4.x/content/api-docs/validate.mdx b/content/nomad/v1.4.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..2311f97ef4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.4.x/content/api-docs/variables.mdx b/content/nomad/v1.4.x/content/api-docs/variables.mdx
new file mode 100644
index 0000000000..f3c954a438
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/variables.mdx
@@ -0,0 +1,302 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`] commands.
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 16KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+
+[Variables]: /nomad/docs/concepts/variables
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.4.x/content/api-docs/volumes.mdx b/content/nomad/v1.4.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..5b0866626e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/api-docs/volumes.mdx
@@ -0,0 +1,783 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..f797d33d2e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an apropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..62588c1b78
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..af000cd896
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..b9e9e99a4b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..64d72c4b0c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl role create'
+description: The role create command is used to create new ACL Roles.
+---
+
+# Command: acl role create
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..f4e4a93b9f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl role delete'
+description: The role delete command is used to delete existing ACL Roles.
+---
+
+# Command: acl role delete
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..7a2f40a8bd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl role info'
+description: |
+  The role info command is used to fetch information about an existing ACL
+  Role.
+---
+
+# Command: acl role info
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..6f36f8d065
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl role list'
+description: The role list command is used to list existing ACL Roles.
+---
+
+# Command: acl role list
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..cc808f8386
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl role update'
+description: The role update command is used to update existing ACL Roles.
+---
+
+# Command: acl role update
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..aeac4ee876
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..33e442126e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..fb8fc94ac2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..b58a7193b8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.4.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..bf13ae093b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-global`: Toggles the global mode of the token. Global tokens are replicated
+  to all regions. Defaults false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.4.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/agent.mdx b/content/nomad/v1.4.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..c391423566
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/agent.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[nomad agent]: /nomad/docs/operations/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..9cee1bda49
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..b03e3ae9a6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..92652b0177
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..7fd38a21f4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.4.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..718d962d57
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.4.x/content/docs/commands/config/index.mdx b/content/nomad/v1.4.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.4.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.4.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..9c72af2dce
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..d40b151754
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3369798607
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..86542733e2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.4.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.4.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..9214e1adf4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.4.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..a4900f08ff
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfuly deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfuly deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfuly deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.4.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.4.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.4.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.4.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.4.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/fmt.mdx b/content/nomad/v1.4.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..d40d17c95a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: fmt'
+description: |
+  Rewrite Nomad config and job files to canonical format
+---
+
+# Command: fmt
+
+The `fmt` commands check the syntax and rewrites Nomad configuration and jobspec
+files to canonical format. It can be used to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [flags] paths ...
+```
+
+Formats Nomad agent configuration and job file to a canonical format. If a path
+is a directory, it will recursively format all files with .nomad and .hcl
+extensions in the directory.
+
+If you provide a single dash (-) as argument, fmt will read from standard input
+(STDIN) and output the processed output to standard output (STDOUT).
+
+Note that, this command will check the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 jobspec will result in errors.
+
+## Format Options:
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/index.mdx b/content/nomad/v1.4.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.4.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..3b2d7e3a7d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.4.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..77fe845631
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.4.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..d88806b0ba
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.4.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..3f22111fdb
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/history.mdx b/content/nomad/v1.4.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..2252b7e932
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/index.mdx b/content/nomad/v1.4.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..47ff5c79d8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/init.mdx b/content/nomad/v1.4.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..36cd12f5c9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.4.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..e181e61937
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.4.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..2ace88951f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.4.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..b45d45b1c6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,264 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan job1.nomad
+nomad job plan example.nomad
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.4.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..6584224940
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`list-jobs`, and `read-job` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.4.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..3c7dfc8b2a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/run.mdx b/content/nomad/v1.4.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..3f68ecf6b7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `job1.nomad`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run job1.nomad
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `job1.nomad` and return immediately:
+
+```shell-session
+$ nomad job run -detach job1.nomad
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.4.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..bb4c10d79b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `scale-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.4.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..98ecb45dd8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/status.mdx b/content/nomad/v1.4.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..e28450bad5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,254 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.4.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..6e2772028d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job>
+```
+
+The `job stop` command requires a single argument, specifying the job ID or
+prefix to cancel. If there is an exact match based on the provided job ID or
+prefix, then the job will be cancelled. Otherwise, a list of matching jobs and
+information will be displayed.
+
+Stop will issue a request to deregister the matched job and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the request. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `list-jobs` capabilities for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.4.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.4.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..94d0273d87
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.4.x/content/docs/commands/license/get.mdx b/content/nomad/v1.4.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..5a3f9f3684
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/license/index.mdx b/content/nomad/v1.4.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..f08fd21f06
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license'
diff --git a/content/nomad/v1.4.x/content/docs/commands/monitor.mdx b/content/nomad/v1.4.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..ff0738014c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..347fa969cd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers  = ["docker", "exec"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..5e2edef272
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs. In federated clusters,
+you cannot delete a namespace that has non-terminal jobs in any of the federated
+regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..e2ab326c7d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f2cc7c3304
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..0f6eedfba3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.4.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..5a51e3ac6e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name            = api-prod
+Description     = Prod API servers
+Quota           = prod
+EnabledDrivers  = docker,exec
+DisabledDrivers = raw_exec
+ 
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/node/config.mdx b/content/nomad/v1.4.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.4.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.4.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..af162841a1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,155 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] block until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[migrate]: /nomad/docs/job-specification/migrate
+[`migrate`]: /nomad/docs/job-specification/migrate
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.4.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.4.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.4.x/content/docs/commands/node/index.mdx b/content/nomad/v1.4.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..b315f5fb77
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.4.x/content/docs/commands/node/status.mdx b/content/nomad/v1.4.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..2a7075d8c4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,397 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjuction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..a36e35b537
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,175 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=<pprof-interval>`: The interval between pprof
+    collections. Set interval equal to duration to capture a single
+    snapshot. Defaults to 250ms or `-pprof-duration`, whichever is
+    less.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..d703f46ae8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring generate'
+description: >
+  The `operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator gossip keyring generate
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..e30c21b5b4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring install'
+description: |
+  Install a new gossip encryption key
+---
+
+# Command: operator gossip keyring install
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..e05d940bd9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring list'
+description: |
+  List gossip keys
+---
+
+# Command: operator gossip keyring list
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..97009d769f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring remove'
+description: |
+  Remove a new gossip encryption key
+---
+
+# Command: operator gossip keyring remove
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..708b506787
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring use'
+description: |
+  Use a new gossip encryption key
+---
+
+# Command: operator gossip keyring use
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..4a084dc86d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator keygen`][keygen] - Generates a new encryption key
+
+- [`operator keyring`][keyring] - Manages gossip layer encryption keys
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[keygen]: /nomad/docs/commands/operator/keygen 'Generates a new encryption key'
+[keyring]: /nomad/docs/commands/operator/keyring 'Manages gossip layer encryption keys'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/keygen.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/keygen.mdx
new file mode 100644
index 0000000000..35347abda4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/keygen.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator keygen'
+description: >
+  The `operator keygen` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator keygen
+
+~> **Warning:** This command is deprecated and will be removed in
+   Nomad 1.5.0. Use the `nomad operator gossip keyring generate`
+   subcommand instead.
+
+The `operator keygen` command generates an encryption key that can be used for
+Nomad server's gossip traffic encryption. The keygen command uses a
+cryptographically strong pseudo-random number generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe" base64
+alphabet. If you use another tool such as OpenSSL to generate the gossip key,
+you should pipe the input through the `base64(1)` command to ensure it is
+safely encoded. For example: `openssl rand 32 | base64`
+
+## Usage
+
+```plaintext
+nomad operator keygen
+```
+
+## Example
+
+```shell-session
+$ nomad operator keygen
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/keyring.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/keyring.mdx
new file mode 100644
index 0000000000..d9bfb13943
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/keyring.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: operator keyring'
+---
+
+# Command: operator keyring
+
+~> **Warning:** This command is deprecated and will be removed in
+   Nomad 1.5.0. Use the `nomad operator gossip keyring` subcommands
+   instead.
+
+The `operator keyring` command is used to examine and modify the encryption keys
+used in Nomad server. It is capable of distributing new encryption keys to the
+cluster, retiring old encryption keys, and changing the keys used by the cluster
+to encrypt messages.
+
+Nomad allows multiple encryption keys to be in use simultaneously. This is
+intended to provide a transition state while the cluster converges. It is the
+responsibility of the operator to ensure that only the required encryption keys
+are installed on the cluster. You can review the installed keys using the
+`-list` argument, and remove unneeded keys with `-remove`.
+
+All operations performed by this command can only be run against server nodes
+and will effect the entire cluster.
+
+All variations of the `keyring` command return 0 if all nodes reply and there
+are no errors. If any node fails to reply or reports failure, the exit code
+will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator keyring [options]
+```
+
+Only one actionable argument may be specified per run, including `-list`,
+`-install`, `-remove`, and `-use`.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The list of available flags are:
+
+- `-list` - List all keys currently in use within the cluster.
+
+- `-install` - Install a new encryption key. This will broadcast the new key to
+  all members in the cluster.
+
+- `-use` - Change the primary encryption key, which is used to encrypt messages.
+  The key must already be installed before this operation can succeed.
+
+- `-remove` - Remove the given key from the cluster. This operation may only be
+  performed on keys which are not currently the primary key.
+
+## Output
+
+The output of the `nomad operator keyring -list` command consolidates
+information from all the Nomad servers from all datacenters and regions to
+provide a simple and easy to understand view of the cluster.
+
+```shell-session
+$ nomad operator keyring -list
+==> Gathering installed encryption keys...
+Key
+PGm64/neoebUBqYR/lZTbA==
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..593d6ed48a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..e049b8b795
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring list'
+description: |
+  List encryption key metadata
+---
+
+# Command: operator root keyring list
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..bcf701378e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring remove'
+description: |
+  Remove an unused encryption key
+---
+
+# Command: operator root keyring remove
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..2ba424ef24
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring rotate'
+description: |
+  Rotate encryption key
+---
+
+# Command: operator root keyring rotate
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Rotate Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+    command will immediately return and the re-encryption process will run
+    asynchronously on the leader.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate
+Key       State   Create Time
+f19f6029  active  2022-07-11T19:14:36Z
+
+$ nomad operator root keyring rotate -verbose
+Key                                   State   Create Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..61e84d2454
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..221452f1d2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..d25a05a6bc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+This command only restores the Raft snapshot. If you are recovering a cluster,
+you will also need to [restore the keyring][] onto at least one server.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..ac0142e962
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+This command only saves a Raft snapshot. If you use this snapshot to recover a
+cluster, you will also need to [restore the keyring][] onto at least one server.
+
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backu
diff --git a/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.4.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.4.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.4.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6746241535
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..0956cba4d5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..afc21d99d1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..29b226bb43
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..1ff8247c14
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..24e34442cc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.4.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..45ea3a4ca5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.4.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..3660b9f70f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.4.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..8d930e8c57
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.4.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..7b2665192c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.4.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.4.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..a0f80bb60d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.4.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..2111f423b6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.4.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..1f70f5d317
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.4.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.4.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.4.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.4.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..088b249d0d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..18263c8338
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.4.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f904c7b714
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.4.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.4.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..75bef2f684
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.4.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..fb97b3cbff
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.4.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d31ab75e70
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/server/index.mdx b/content/nomad/v1.4.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.4.x/content/docs/commands/server/join.mdx b/content/nomad/v1.4.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..152a102f52
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/server/members.mdx b/content/nomad/v1.4.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..bfd9ce255b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..0eb973622c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/service/index.mdx b/content/nomad/v1.4.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..a6f207b0a8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.4.x/content/docs/commands/service/info.mdx b/content/nomad/v1.4.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..9287f4da0f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/service/list.mdx b/content/nomad/v1.4.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..7c09b6acb4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/status.mdx b/content/nomad/v1.4.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.4.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/system/index.mdx b/content/nomad/v1.4.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.4.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.4.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.4.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..01deb51ec0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: tls ca create'
+description: |
+  This command creates a Certificate Authority that can be used to create
+  self signed certificates to be used for Nomad TLS setup.
+---
+
+# Command: nomad tls ca create
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## CA Create Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.4.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..0261571b19
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: tls ca info'
+description: |
+  This command displays relevant information that is contained within a
+  Certificate Authority certificate.
+---
+
+# Command: nomad tls ca info
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.4.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..aae4c0339b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Create'
+description: |
+  This command creates a Certificate that can be used for Nomad TLS setup.
+---
+
+# Command: nomad tls cert create
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Command Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-dc=<string>`: Provide the datacenter. Matters only for `-server`
+  certificates. Defaults to `dc1`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-node=<string>`: When generating a server cert and this server is set an
+  additional DNS name is included of the form
+  `<node>.server.<datacenter>.<domain>`.
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.4.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.4.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..c37f6a54c0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Info'
+description: |
+  This command displays relevant information that is contained within a
+  certificate.
+---
+
+# Command: nomad tls cert info
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.4.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..1e580053ee
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: tls'
+description: |
+  The tls command is used to help with creating a Certificate Authority 
+  and up self signed certificates for Nomad TLS configuration.
+---
+
+# Command: tls
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
\ No newline at end of file
diff --git a/content/nomad/v1.4.x/content/docs/commands/ui.mdx b/content/nomad/v1.4.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/get.mdx b/content/nomad/v1.4.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..3639942887
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: "Command: var get"
+description: |-
+  The "var get" command retrieves the variable at the given path from
+  Nomad. If no variable exists at that path, an error is returned.
+---
+
+# Command: var get
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/index.mdx b/content/nomad/v1.4.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..16f7bd5334
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: "Commands: var"
+description: |-
+  The "var" command groups subcommands for interacting with Nomad variables.
+---
+
+# Command: var
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/init.mdx b/content/nomad/v1.4.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..8a99bf81fa
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: var init'
+description: |
+  Generate an example variable specification.
+---
+
+# Command: var init
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/list.mdx b/content/nomad/v1.4.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d8974ffff2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: "Command: var list"
+description: |-
+  The "var list" command lists data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# Command: var list
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.4.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..c924fa77ab
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: "Command: var purge"
+description: |-
+  The "var purge" command permanently removes the specified variable
+  from Nomad.
+---
+
+# Command: var purge
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Command Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.4.x/content/docs/commands/var/put.mdx b/content/nomad/v1.4.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..4909ca8d53
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: "Command: var put"
+description: |-
+  The "var put" command writes a variable to the given path in Nomad.
+---
+
+# Command: var put
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a variable specification, by
+using command arguments, or by a combination of the two techniques. An entire
+variable specification can be provided to the command via standard input (stdin)
+by setting the first argument to "-" or from a file by using an @-prefixed path
+to a variable specification file. When providing variable data via stdin, you
+must provide the `-in` flag with the format of the specification, which must be
+either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 16KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.4.x/content/docs/commands/version.mdx b/content/nomad/v1.4.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..e5b4ef6160
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/version.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v0.0.0-615-gcf3c6aa-dev (cf3c6aa8a75a689987b689d75ae2ba73458465cb+CHANGES)
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..39b0b39c93
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..726ed55b84
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.4.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.4.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..d371d7f455
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.4.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.4.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..25bca1184d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+#### Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+#### Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+#### Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+#### Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+#### Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+#### Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+#### Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+#### Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+#### Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+#### Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+#### Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
diff --git a/content/nomad/v1.4.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.4.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.4.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.4.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..c0514750e9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,470 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.4.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.4.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..d5b2f7cf42
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/nomad/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.4.x/content/docs/concepts/index.mdx b/content/nomad/v1.4.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..9c0dbb461c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Network Plugins
+description: Learn how Nomad manages custom user-specified network configurations.
+---
+
+# Network plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..a7f5a4ed19
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..79e2aa1a75
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.4.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.4.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..308da7a1ff
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propogating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
diff --git a/content/nomad/v1.4.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.4.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..9c17dc0d8d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.4.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.4.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..5307339993
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.4.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.4.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..9c07454ff5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.4.x/content/docs/concepts/security.mdx b/content/nomad/v1.4.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..99526dea77
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/security.mdx
@@ -0,0 +1,333 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** - 
+  Access to read and write to a namespace can be
+  controlled to allow for granular access to job information managed within a
+  multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
+
+
+[Variables]: /nomad/docs/concepts/variables
diff --git a/content/nomad/v1.4.x/content/docs/concepts/variables.mdx b/content/nomad/v1.4.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..35e5b4ca59
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,195 @@
+---
+layout: docs
+page_title: Variables
+description: Learn about the Nomad Variables feature
+---
+
+# Nomad Variables
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to provide such configuration to tasks, but has left the role
+of storing that configuration to external services such as [HashiCorp Consul]
+and [HashiCorp Vault].
+
+Nomad Variables provide the option to securely store configuration at file-like
+paths directly in Nomad's state store. The contents of these secrets are
+encrypted and replicated between servers via raft. Access to secrets is
+controlled by ACL policies, and tasks have implicit ACL policies that allow them
+to access their own secrets. You can create, read, update, or delete secrets via
+the command line, the Nomad API, or in the Nomad web UI.
+
+Note that the Variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as Variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. If you need powerful options like dynamic
+secrets or transit encryption, continue using Vault.
+
+## ACL for Variables
+
+Every Variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to Variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for Variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+In Nomad 1.4.0 tasks can only access Variables with the [`template`] block. The
+[workload identity] for each task grants it automatic read and list access to
+Variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to Variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
diff --git a/content/nomad/v1.4.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.4.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..41853625b1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Learn about Nomad's workload identity feature
+---
+
+# Workload Identity
+
+When an [allocation][] is accepted by the [plan applier][], the leader generates
+a Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring. The
+workload identity includes the following identity claims:
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+## Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+## Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+## Using Workload Identity
+
+In Nomad 1.4.0 the workload identity is used only for `template`
+access to [Variables][] and not exposed outside of Nomad.
+
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[Variables]: /nomad/docs/concepts/variables
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
diff --git a/content/nomad/v1.4.x/content/docs/configuration/acl.mdx b/content/nomad/v1.4.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..19db95fcc2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. Note that the Nomad command
+  line client will send requests for client endpoints such as `alloc exec`
+  directly to Nomad clients whenever they are accessible. In this scenario, the
+  client will enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in non-authoritative
+  region to mirror the policies and tokens into the local region from [authoritative_region][authoritative-region].
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.4.x/content/docs/configuration/audit.mdx b/content/nomad/v1.4.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.4.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.4.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.4.x/content/docs/configuration/client.mdx b/content/nomad/v1.4.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..ea36c82015
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/client.mdx
@@ -0,0 +1,644 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "[data_dir]/alloc")` - Specifies the directory to use
+  for allocation data. By default, this is the top-level
+  [data_dir](/nomad/docs/configuration#data_dir) suffixed with
+  "alloc", like `"/opt/nomad/alloc"`. This must be an absolute path.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "[data_dir]/client")` - Specifies the directory to use
+  to store client state. By default, this is - the top-level
+  [data_dir](/nomad/docs/configuration#data_dir) suffixed with
+  "client", like `"/opt/nomad/client"`. This must be an absolute path.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+As of Nomad 1.2, Nomad will never attempt to embed the `alloc_dir` in the
+chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the number of CPU cores to reserve.
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: nil)` - Specifies the maximum amount of
+  data that will be decompressed before triggering an error and cancelling the
+  operation. E.g. "10GB". By default this value is not set and no limit is enforced.
+
+- `decompression_file_count_limit` `(int: nil)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling
+  the operation. By default this value is not set and no limit is enforced.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
diff --git a/content/nomad/v1.4.x/content/docs/configuration/consul.mdx b/content/nomad/v1.4.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..fe4dde236a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sane defaults automatically enable Consul integration if
+Consul is detected on the system. This allows for seamless bootstrapping of the
+cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will automatically connect and configure with Consul.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+   certificate used for communication between Connect sidecar proxies and Consul
+   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](/consul/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes. Will default to the `CONSUL_HTTP_TOKEN`
+  environment variable if set.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
diff --git a/content/nomad/v1.4.x/content/docs/configuration/index.mdx b/content/nomad/v1.4.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..d6d78d8540
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/index.mdx
@@ -0,0 +1,387 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent.
+  All members of a datacenter should share a local LAN connection.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the interrupt signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should
+  gracefully leave when receiving the terminate signal. By default, the agent
+  will exit forcefully on any signal. This value should only be set to true on
+  server agents if it is expected that a terminated server instance will never
+  join the cluster again.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "[data_dir]/plugins")` - Specifies the directory to
+  use for looking up plugins. By default, this is the top-level
+  [data_dir](#data_dir) suffixed with "plugins", like `"/opt/nomad/plugins"`.
+  This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
diff --git a/content/nomad/v1.4.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.4.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.4.x/content/docs/configuration/search.mdx b/content/nomad/v1.4.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.4.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.4.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.4.x/content/docs/configuration/server.mdx b/content/nomad/v1.4.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..22b4e89a1d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/server.mdx
@@ -0,0 +1,468 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region, which
+  provides a single source of truth for global configurations such as ACL Policies and
+  global ACL tokens. Non-authoritative regions will replicate from the authoritative
+  to act as a mirror. By default, the local region is assumed to be authoritative.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "[data_dir]/server")` - Specifies the directory to use
+  for server-specific data, including the replicated log. By default, this is
+  the top-level [data_dir](/nomad/docs/configuration#data_dir) suffixed with "server",
+  like `"/opt/nomad/server"`. The top-level option must be set, even when
+  setting this value. This must be an absolute path.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator keygen`] command. The
+  provided key is automatically persisted to the data directory and loaded
+  automatically whenever the agent is restarted. This means that to encrypt
+  Nomad server's gossip protocol, this option only needs to be provided once
+  on each agent's initial startup sequence. If it is provided after Nomad has
+  been initialized with an encryption key, then the provided key is ignored
+  and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". See [Client Heartbeats](#client-heartbeats) below for details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients
+  must heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". See [Client Heartbeats](#client-heartbeats) below
+  for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The tradeoff
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and raft latency.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time that an
+  [encryption key][] must exist before it can be eligible for garbage
+  collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the minimum time
+  that an [encryption key][] must exist before it is automatically rotated on
+  the next garbage collection interval.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false # New in Nomad 1.3.2
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true # New in Nomad 1.2
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`max_client_disconnect`][max_client_disconnect] is set)
+and rescheduled.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer a `down` Client's workload will
+  take to be rescheduled.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  rescheduled.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO (see below)       |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election.  However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and reschedules their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator keygen`]: /nomad/docs/commands/operator/keygen
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[max_client_disconnect]: /nomad/docs/job-specification/group#max-client-disconnect
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
diff --git a/content/nomad/v1.4.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.4.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..f4184645b2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.4.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.4.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..53d2231d8c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,189 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.4.x/content/docs/configuration/tls.mdx b/content/nomad/v1.4.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..d858b25291
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to
+enforce secure cluster communication between servers, clients, and between.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if mTLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints 
+   and [Raft][raft] traffic. When this setting is activated, it establishes protection 
+   both between Nomad servers and from the clients back to the servers, ensuring 
+   mutual authentication.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require
+  client certificates for all incoming HTTPS requests. The client certificates
+  must be signed by the same CA as Nomad.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables TLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a
+`SIGHUP` signal. Note that this will only reload a subset of the configuration
+file, including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.4.x/content/docs/configuration/ui.mdx b/content/nomad/v1.4.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..9525aab116
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  consul {
+    ui_url = "https://consul.example.com:8500/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8500/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.4.x/content/docs/configuration/vault.mdx b/content/nomad/v1.4.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..dad303682c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.4.x/content/docs/devices/index.mdx b/content/nomad/v1.4.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.4.x/content/docs/drivers/docker.mdx b/content/nomad/v1.4.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..4c64a8fc7d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1219 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group `network.mode = "bridge"` you should not set the Docker config
+  `network_mode`, or the container will be unable to reach other containers in
+  the task group. This will also prevent [Connect]-enabled tasks from reaching
+  the Envoy sidecar proxy. You must also set any DNS options in the `network.dns`
+  block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent. Nomad was developed against Docker `1.8.2` and `1.9`.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`. The image will only be pulled from
+  the container registry if its tag is `latest` or the image doesn't yet exist locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading `NOMAD_MEMORY_LIMIT`, but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.4.x/content/docs/drivers/exec.mdx b/content/nomad/v1.4.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..271095ccec
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,257 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.4.x/content/docs/drivers/index.mdx b/content/nomad/v1.4.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.4.x/content/docs/drivers/java.mdx b/content/nomad/v1.4.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..9de1accc68
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/java.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.4.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.4.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..4a86628ff0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.4.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.4.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..b8b2db68e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.4.x/content/docs/ecosystem.mdx b/content/nomad/v1.4.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.4.x/content/docs/enterprise/index.mdx b/content/nomad/v1.4.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..a5e20ce30e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,178 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies
+Guide](/nomad/tutorials/governance-and-policy/sentinel) for a thorough
+overview.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
diff --git a/content/nomad/v1.4.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.4.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..0b0d39eef5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.1.0+ent.
+Nomad Enterprise automatically load Nomad licenses when a Nomad server agent starts using Nomad Enterprise.
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.1.0, the license enablement process is different.
+
+HashiCorp Enterprise servers will no longer start without a license. When the
+server instance initializes the license watcher, the server reads from either an
+environment variable or file. If the license is missing, invalid, or terminated,
+the server will immediately exit. This check is part of the server boot-up
+process.
+
+In previous versions of HashiCorp enterprise products, one server could
+distribute a license to other servers via the Raft protocol. This will no longer
+work since each server must be able to find a valid license during the startup
+process.
+
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about the license changes introduced in Nomad Enterprise v1.1.0
+
+- [v1.1.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect Nomad or older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.1.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you follow the steps in the [upgrade guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses), but have misconfigured the licensing steps, the server instances will stop during boot-up sequence.
+
+If you do not check cluster health after adding new servers, and verify that the new servers have joined properly, then you may accidentally take down old servers without replacing them.
+
+If you are using a trial license in production, this could cause issues as the cluster will fail to start once the trial expires.
+
+If you have built automation around `nomad license put`, this command will fail as it has been removed from Nomad v1.1.0+.
+
+## Q: What are some other gotchas?
+
+You might not have access to your organization's Nomad license.
+The  6-hour temporary license window is now removed, and a license is required for proper boot-up.
+Running `nomad agent -dev` without a license will fail.
+
+
+## Q: How can a user get their existing license to put on disk for an upgrade?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires or terminates?
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. The grace
+period is defined as the time between license expiration and license
+termination. (This is typically very short for evaluation licenses, and much longer
+for non-evaluation licenses.) Customers must provide a valid license before the
+grace period expires.
+
+When the license terminates, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write operations
+will return an error. Note that if the server is restarted with a terminated
+license, it will immediately stop.
+
+Clients are unaffected by terminated licenses because clients do not read the
+license.
+
+## Q: Will on-prem binaries with "baked-in" licenses work?
+
+There is no impact to baked-in licensed binaries.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Visit https://nomadproject.io/trial for a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.1.0 to an earlier version?
+
+Nomad cannot safely be rolled back to an earlier version.
+This is not a supported operation due to the Nomad state store not having forward compatibility. The end result could be a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
diff --git a/content/nomad/v1.4.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.4.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..8c6162a1b3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have its own license. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time and a termination time. You
+can read the license on a server with the `nomad license get` command:
+
+```
+$ nomad license get
+Product        = nomad
+License Status = valid
+License ID     = eaaecbd5-b598-4fa4-b649-bb234bf49fa3
+Customer ID    = ae94bdd0-39bf-4c58-bf80-8a9468b0467c
+Issued At      = 2021-03-29 14:47:29.024191 -0400 EDT
+Expires At     = 2021-03-29 20:47:29.024191 -0400 EDT
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+        Dynamic Application Sizing
+```
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. Below shows
+log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license reaches the termination time, enterprise functionality will
+become limited. Only read operations on enterprise endpoints will be supported,
+and write operations will return an error.
+
+Note that if the server is restarted with a terminated license, it will
+immediately stop.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.4.x/content/docs/faq.mdx b/content/nomad/v1.4.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..a9c683b8b6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.4.x/content/docs/index.mdx b/content/nomad/v1.4.x/content/docs/index.mdx
new file mode 100644
index 0000000000..3296277979
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [Getting Started collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.4.x/content/docs/install/index.mdx b/content/nomad/v1.4.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..2f9e5e7127
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/install/index.mdx
@@ -0,0 +1,391 @@
+---
+layout: docs
+page_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/nomad/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](/nomad/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Homebrew on macOS" group="homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Linux Packages" group="linux">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](/consul/tutorials) and
+[Vault](/vault/tutorials) with the same command.
+
+</Tab>
+</Tabs>
+
+## Post-installation steps
+
+These steps are considered optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+<Tabs>
+<Tab heading="Linux Packages">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+
+<Tab heading="macOS">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+</Tab>
+
+<Tab heading="Windows">
+
+<h3>Add the Nomad binary to your system path</h3>
+
+Add a location to your path via the GUI by navigating to `Environment
+Variables` in your system settings, and looking for the variable called `PATH`.
+You should see a semicolon-separated list of locations. Add the Nomad binary's
+location to that list and then launch a new console window.
+</Tab>
+</Tabs>
+</Tab>
+
+<Tab heading="Homebrew on macOS" group="homebrew">
+No additional steps necessary after installing Nomad using Homebrew.
+</Tab>
+
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+No additional steps necessary after installing Nomad using Chocolatey.
+</Tab>
+
+<Tab heading="Linux" group="linux">
+
+Note that if you are running Nomad on Linux, you'll need to run client agents as
+root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl             Interact with ACL policies and tokens
+    agent-info      Display status information about the local agent
+    deployment      Interact with deployments
+    eval            Interact with evaluations
+    exec            Execute commands in task
+    monitor         Stream logs from a Nomad agent
+    namespace       Interact with namespaces
+    operator        Provides cluster-level tools for Nomad operators
+    quota           Interact with quotas
+    sentinel        Interact with Sentinel policies
+    server          Interact with servers
+    system          Interact with the system API
+    ui              Open the Nomad Web UI
+    version         Prints the Nomad version
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed and
+configured properly (including a `GOPATH` environment variable set), as well
+as a copy of [`git`](https://www.git-scm.com/) in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
diff --git a/content/nomad/v1.4.x/content/docs/install/production/index.mdx b/content/nomad/v1.4.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..2d8e7350d4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.4.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.4.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..5cddb5a1fd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,233 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publically routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrate
diff --git a/content/nomad/v1.4.x/content/docs/install/quickstart.mdx b/content/nomad/v1.4.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..571ba79333
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via guides containing embedded interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.4.x/content/docs/install/windows-service.mdx b/content/nomad/v1.4.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.4.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.4.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..34f968cb7d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,406 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://nomadproject.io/consul_ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+sudo mkdir -p /opt/cni/bin
+sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad` and running:
+`nomad job run servicemesh.nomad`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
diff --git a/content/nomad/v1.4.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.4.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..61414160ee
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/nomad/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](/nomad/tutorials/manage-clusters/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` block](/nomad/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul Template,
+please see the [`template` job specification documentation](/nomad/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+
+[consul]: https://www.consul.io/ "Consul by HashiCorp"
+
+[consul_acls]: /consul/docs/security/acl
+
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+
+[consul_group_namespace]: /nomad/docs/job-specification/group#namespace
+
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
diff --git a/content/nomad/v1.4.x/content/docs/integrations/index.mdx b/content/nomad/v1.4.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.4.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.4.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..9fb9016bec
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,475 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` block of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To submit this job, a token that has the `access-kv` policy in the `engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /nomad/docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /nomad/docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /nomad/docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.4.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.4.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..539c2f0f88
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the Nomad user's known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /root/.ssh/known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file(pathexpand("~/.ssh/id_rsa")))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.4.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/check.mdx b/content/nomad/v1.4.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..e1e344aa94
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,442 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for http-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`][type] must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the http-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivelent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Only supported in the Consul service provider.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness vs. Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```
+➜ nomad alloc status <allocation-id>
+```
+
+```
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```
+➜ noamd alloc checks <allocation-id>
+```
+
+```
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.4.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.4.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.4.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..3f2f947f57
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+~> **It is possible to define irreconcilable constraints in a job.**
+For example, because all [tasks within a group are scheduled on the same client node][group],
+specifying different [`${attr.unique.hostname}`][node-variables] constraints at
+the task level will cause a job to be unplaceable.
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.4.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..f29bc2bfa6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                      = "csi-hostpath"
+  type                    = "monolith"
+  mount_dir               = "/csi"
+  stage_publish__base_dir = "/local/csi"
+  health_timeout          = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/device.mdx b/content/nomad/v1.4.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..0748bf8ec4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.4.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..482fe10047
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` blocks. Remember that the
+`dispatch_payload` block is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/env.mdx b/content/nomad/v1.4.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..18d67f659f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template block'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.4.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..5b3378b3af
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - When `sticky` is true, this specifies that the
+  Nomad client should make a best-effort attempt to migrate the data from a
+  remote machine if placement cannot be made on the original node. During data
+  migration, the task will block starting until the data migration has
+  completed. Migration is atomic and any partially migrated data will be removed
+  if an error is encountered. Note that data migration will not take place if a
+  client garbage collects a failed allocation or if the allocation has been
+  intentionally stopped via `nomad alloc stop`, because the original allocation
+  has already been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.4.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..e709e4c464
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.4.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..16889f4114
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,666 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect Gateways](/consul/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or `grpc`), preconfiguring a [service-default] in Consul to
+  set the [Protocol](/consul/docs/connect/config-entries/service-defaults#protocol)
+  of the service to the desired protocol is mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#service-parameters-1
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[service]: /nomad/docs/job-specification/gateway#service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/group.mdx b/content/nomad/v1.4.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..a64fe83225
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,360 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost". These
+allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' reschedule policy
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements and keep
+the one with the best node score. If the `max_client_disconnect` duration
+expires before the client reconnects, the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+~> **Note:** The `max_client_disconnect` feature is only supported on Nomad
+version 1.3.0 and above. If you run a job with `max_client_disconnect` on servers
+where some servers are not upgraded to 1.3.0, the `max_client_disconnect`
+flag will be _ignored_. Deploying a job with `max_client_disconnect` to a
+`datacenter` of Nomad clients where all clients are not 1.3.0 or above is unsupported.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/group#consul-parameters
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..3ce884109b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..d57583954d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..e535ede487
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..24e760c922
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..667174c8a1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..47aa267184
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..43b0506d4e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are often referred to as just
+"variables" or "Nomad variables" when it is clear from context what sort of
+variable is being discussed. Other kinds of variables in Nomad include
+_environment variables_ (set by the shell where Nomad runs) and _expression
+variables_ (used to indirectly represent a value in an
+[expression](/nomad/docs/job-specification/hcl2/expressions)).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/index.mdx b/content/nomad/v1.4.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..7f30018833
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect block Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/job.mdx b/content/nomad/v1.4.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..d1c66c49bf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,257 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: <required>)` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources. Must be between 1 and 100
+  inclusively, with a larger value corresponding to a higher priority.
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.4.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.4.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..7ace3f6530
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with sane defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with sane defaults (provided in the
+parameters section below), and there is currently no way to disable logging for
+tasks. The `logs` block allows for finer-grained control over how Nomad handles
+log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with sane defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.4.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..dfca686f51
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any `-` character existing in the key
+will also be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.4.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.4.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..53f5ee4b4d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,287 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/network.mdx b/content/nomad/v1.4.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..ada5550781
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,332 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS configuration
+  for the allocations. By default all DNS configuration is inherited from the client host.
+  DNS configuration is only supported on Linux clients at this time.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is neccessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.4.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..bf914761dc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.4.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..e91f04b915
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.4.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..fb92934572
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that's opaque to Nomad and
+  passed directly to Consul. See [Consul Connect's
+  documentation](/consul/docs/connect/proxies/envoy#dynamic-configuration)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.4.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.4.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..72e12ea0f9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Specifies the number of CPU cores to reserve
+  for the task. This may not be used with `cpu`.
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> <sup>1.1 Beta</sup> - Optionally, specifies the maximum memory the task may use, if the client has excess memory capacity, in MB. See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad 1.1. lets job authors set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The new max limit attribute is currently supported by the official `docker`,
+`exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory Oversubscription in the scheduler
+configuration](/nomad/api-docs/operator/scheduler#update-scheduler-configuration). Enterprise customers can use [Resource
+Quotas](/nomad/tutorials/governance-and-policy/quotas) to limit the memory
+oversubscription.
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.4.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..683254e7fd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.4.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/service.mdx b/content/nomad/v1.4.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..22d5cf6d3f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,519 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.4.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..8197da3029
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.4.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..df7508f636
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.4.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..6fc0455de3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/task.mdx b/content/nomad/v1.4.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..4f68089ebc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/template.mdx b/content/nomad/v1.4.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..94b4e4885d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,776 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can
+  optionally be fetched using an [`artifact`][artifact] resource. This template
+  must exist on the machine prior to starting the task; it is not possible to
+  reference a template that's source is inside a Docker container, for example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+## Nomad Integration
+
+### Nomad Services
+
+~> Nomad Services are new in Nomad 1.3.
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+~> Simple load balancing with Nomad Services is new in Nomad 1.3.2.
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+Nomad [variables] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault
+PKI role.<br /><br /> Failure to do so will cause the template to frequently
+render a new certificate, approximately every minute. This creates a significant
+number of certificates to be expired in Vault and could ultimately lead to Vault
+performance impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.certificate -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.issuing_ca -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Data.private_key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with secret "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Data.certificate }}
+{{ .Data.issuing_ca }}
+{{ .Data.private_key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/update.mdx b/content/nomad/v1.4.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..0d3d1e4148
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with CSI volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.4.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..963f0e7b64
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/nomad/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](https://learn.hashicorp.com/consul/getting-started/connect#register-a-dependent-service-and-proxy).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.4.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..20fe3ab27c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.4.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..ae75f0322b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.4.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.4.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..545379bd62
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.4.x/content/docs/networking/cni.mdx b/content/nomad/v1.4.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..b3e436f4fc
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/networking/cni.mdx
@@ -0,0 +1,217 @@
+---
+layout: docs
+page_title: CNI
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Container Network Interface (CNI)
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+The CNI specification defines a network configuration format for administrators.
+It contains directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by Nomad
+and transformed into arguments for the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Using CNI networks with Nomad jobs
+
+To specify that a job should use a CNI network, set the task group's
+network [`mode`][] attribute to the value `cni/<your_cni_config_name>`.
+Nomad will then schedule the workload on client nodes that have fingerprinted a
+CNI configuration with the given name. For example, to use the configuration
+named `mynet`, you should set the task group's network mode to `cni/mynet`.
+Nodes that have a network configuration defining a network named `mynet` in
+their [`cni_config_dir`][] will be eligible to run the workload.
+
+## Nomad's `bridge` configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the [loopback][], [bridge][], [firewall][],
+and [portmap][] CNI plugins configured together to create Nomad's bridge
+network.
+
+The following is the configuration template Nomad uses when setting up these
+networks with the template placeholders replaced with the default configuration
+values for [`bridge_network_name`][], [`bridge_network_subnet`][], and an
+internal constant that provides the value for `iptablesAdminChainName`. This is
+a convenient jumping off point to discuss a worked example.
+
+```json
+{
+  "cniVersion": "0.4.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+<!-- Source: https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1 -->
+[![Visual example of Nomad bridge network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+For a more thorough understanding of this configuration, consider each CNI
+plugin's configuration in turn.
+
+### loopback
+
+The `loopback` plugin sets the default local interface, `lo0`, created inside
+the bridge network's network namespace to **UP**. This allows workload running
+inside the namespace to bind to a namespace-specific loopback interface.
+
+### bridge
+
+The `bridge` plugin creates a bridge (virtual switch) named `nomad` that resides
+in the host network namespace. Because this bridge is intended to provide
+network connectivity to allocations, it's configured to be a gateway by setting
+`isGateway` to `true`. This tells the plugin to assign an IP address to the
+bridge interface
+
+The bridge plugin connects allocations (on the same host) into a bridge (virtual
+switch) that resides in the host network namespace. By default Nomad creates a
+single bridge for each client. Since Nomad's bridge network is designed to
+provide network connectivity to the allocations, it configures the bridge
+interface to be a gateway for outgoing traffic by providing it with an address
+using an `ipam` configuration. The default configuration creates a host-local
+address for the host side of the bridge in the `172.26.64.0/20` subnet at
+`172.26.64.1`. When associating allocations to the bridge, it creates addresses
+for the allocations from that same subnet using the host-local plugin. The
+configuration also specifies a default route for the allocations of the
+host-side bridge address.
+
+### firewall
+
+The firewall plugin creates firewall rules to allow traffic to/from the
+allocation's IP address via the host network. Nomad uses the iptables backend
+for the firewall plugin. This configuration creates two new iptables chains,
+`CNI-FORWARD` and `NOMAD-ADMIN`, in the filter table and add rules that allow
+the given interface to send/receive traffic.
+
+The firewall creates an admin chain using the name provided in the
+`iptablesAdminChainName` attribute. For this case, it's called `NOMAD-ADMIN`.
+The admin chain is a user-controlled chain for custom rules that run before
+rules managed by the firewall plugin. The firewall plugin does not add, delete,
+or modify rules in the admin chain.
+
+A new chain, `CNI-FORWARD` is added to the `FORWARD` chain. `CNI-FORWARD` is
+the chain where rules will be added when allocations are created and from where
+rules will be removed when those allocations stop. The `CNI-FORWARD` chain
+first sends all traffic to `NOMAD-ADMIN` chain.
+
+You can use the following command to list the iptables rules present in each
+chain.
+
+```shell-session
+$ sudo iptables -L
+```
+
+### portmap
+
+Nomad needs to be able to map specific ports from the host to tasks running in
+the allocation namespace. The `portmap` plugin forwards traffic from one or more
+ports on the host to the allocation using network address translation (NAT)
+rules.
+
+The plugin sets up two sequences of chains and rules:
+
+- One “primary” `DNAT` (destination NAT) sequence to rewrite the destination.
+- One `SNAT` (source NAT) sequence that will masquerade traffic as needed.
+
+You can use the following command to list the iptables rules in the NAT table.
+
+```shell-session
+$ sudo iptables -t nat -L
+```
+
+## Create your own
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode. When making your own bridge network
+based on this template, ensure that you change the `iptablesAdminChainName` to
+a unique value for your configuration.
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`bridge_network_name`]: /nomad/docs/configuration/client#bridge_network_name
+[`bridge_network_subnet`]: /nomad/docs/configuration/client#bridge_network_subnet
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[`mode`]: /nomad/docs/job-specification/network#mode
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[loopback]: https://github.com/containernetworking/plugins#main-interface-creating
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.4.x/content/docs/networking/index.mdx b/content/nomad/v1.4.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..9183bf5424
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/networking/index.mdx
@@ -0,0 +1,331 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Learn about Nomad's networking internals and how it compares with other
+  tools.
+---
+
+# Networking
+
+Nomad is a workload orchestrator and so it focuses on the scheduling aspects of
+a deployment, touching areas such as networking as little as possible.
+
+**Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_**. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+This can be confusing at first since it is quite different from what you may
+be used to from other tools. This section explains how networking works in
+Nomad, some of the different patterns and configurations you are likely to find
+and use, and how Nomad differs from other tools in this aspect.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an [allocation][], which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the [`network`][jobspec_network] block. At its
+simplest configuration, a `network` block can be defined as:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between [`min_dynamic_port`][] and
+[`max_dynamic_port`][] that has not been allocated yet and creates a port
+mapping from the host network interface to the allocation.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Port Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+The selected port number can be accessed by tasks using the
+[`NOMAD_PORT_<label>`][runtime_environment] environment variable to bind and
+expose the workload at the client's IP address and the given port.
+
+The specific configuration process depends on what you are running, but it is
+usually done using a configuration file rendered from a [`template`][] or
+passed directly via command line arguments:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+It is also possible to request a specific port number, instead of a random one,
+by setting a [`static`][] value for the `port`. **This should only be used by
+specialized workloads**, such as load balancers and system jobs, since it can
+be hard to manage them manually to avoid scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can
+access it directly using the client's IP and port, but first they need to find
+these values. This process is called [service discovery][].
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network [`mode`][network_mode] called [`bridge`][]. A
+bridge network acts like a virtual network switch allowing processes connected
+to the bridge to reach each other while isolating them from others.
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in [`bridge_network_name`][]) using the
+[`bridge` CNI plugin][cni_bridge] if one doesn't exist yet. Before using this
+mode you must first [install the CNI plugins][cni_install] into your clients.
+By default a single bridge is created in each Nomad client.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random
+ports from the host to specific port numbers inside the allocation that are
+expected by the tasks.
+
+For example, an HTTP server that listens on port `3000` by default can be
+configured with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only.
+
+Bridge networking is at the core of [service mesh][] and a requirement when
+using [Consul Service Mesh][consul_service_mesh].
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network][docker_bridge], network namespaces, and [`iptable`
+rules][docker_iptables]. Tasks using the `docker` task driver connect to the
+Docker bridge instead of using the one created by Nomad and, by default, each
+container runs in its own Docker managed network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`][] to initialize a Docker network namespace
+that is shared by all tasks in the allocation to allow them to communicate with
+each other.
+
+The Docker task driver has its own task-level
+[`network_mode`][docker_network_mode] configuration. Its default value depends
+on the group-level [`network.mode`][network_mode] configuration.
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+   `network.mode` configuration and generate unexpected results. If you set the
+   group `network.mode = "bridge"` you should not set the Docker config
+   `network_mode`.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+The diagram below illustrates what happens when a Docker task is configured
+incorrectly.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container
+to establish a shared network namespace for all tasks, but setting the
+task-level `network_mode` to `bridge` places the task in a different namespace.
+This prevents, for example, a task from communicating with its sidecar proxy in
+a [service mesh][] deployment.
+
+Refer to the [`network_mode`][docker_network_mode] documentation and the
+[Networking][docker_networking] section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ][faq_docker] for more details.
+
+## Comparing with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS services][docker_dns] and a
+load balancer that is transparent to user. When running in Swarm mode, Docker
+Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the [`Service`][k8s_service] abstraction that can be used
+to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service][k8s_dns] which is an add-on that runs in all nodes. Along with this
+service, each node also runs a [`kube-proxy`][k8s_kubeproxy] instance to
+distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface][consul_dns] and configuring your clients with [DNS
+forwarding][consul_dns_forwarding], and deploying a [load
+balancer][nomad_load_balancer].
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical
+IP addresses to virtual ones. In case of Docker Compose in Swarm mode an
+[`overlay`][docker_overlay] is also required to enable traffic across multiple
+hosts. This allows multiple containers running the same service to listen on
+the same port number.
+
+In Nomad, allocations use the IP address of the client they are running and are
+assigned random port numbers and so Nomad service discovery with DNS uses
+[`SRV` records][dns_srv] instead of `A` or `AAA` records.
+
+## Next topics
+
+- [Service Discovery][service discovery]
+- [Service Mesh][service mesh]
+- [Container Network Interface][cni]
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada 2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
+
+[`bridge_network_name`]: /nomad/docs/configuration/client#bridge_network_name
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[`infra_image`]: /nomad/docs/drivers/docker#infra_image
+[`max_dynamic_port`]: /nomad/docs/configuration/client#max_dynamic_port
+[`min_dynamic_port`]: /nomad/docs/configuration/client#min_dynamic_port
+[`static`]: /nomad/docs/job-specification/network#static
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[cni]: /nomad/docs/networking/cni
+[cni_bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[cni_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
+[consul_dns]: /consul/docs/discovery/dns
+[consul_dns_forwarding]: /consul/tutorials/networking/dns-forwarding
+[consul_service_mesh]: /nomad/docs/integrations/consul-connect
+[dns_srv]: https://en.wikipedia.org/wiki/SRV_record
+[docker_bridge]: https://docs.docker.com/network/bridge/
+[docker_compose]: https://docs.docker.com/compose/
+[docker_dns]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[docker_iptables]: https://docs.docker.com/network/iptables/
+[docker_network_mode]: https://nomadproject.io/drivers/docker#network_mode
+[docker_networking]: /nomad/docs/drivers/docker#networking
+[docker_overlay]: https://docs.docker.com/network/overlay/
+[docker_swarm]: https://docs.docker.com/engine/swarm/
+[faq_docker]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[jobspec_network]: /nomad/docs/job-specification/network
+[k8s_dns]: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
+[k8s_ingress]: https://kubernetes.io/docs/concepts/services-networking/ingress/
+[k8s_kubeproxy]: https://kubernetes.io/docs/concepts/overview/components/#kube-proxy
+[k8s_service]: https://kubernetes.io/docs/concepts/services-networking/service/
+[network_mode]: /nomad/docs/job-specification/network#mode
+[nomad_load_balancer]: /nomad/tutorials/load-balancing
+[runtime_environment]: /nomad/docs/runtime/environment#network-related-variables
+[service discovery]: /nomad/docs/networking/service-discovery
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.4.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.4.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..d0e726a85d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Learn about how service discovery works in Nomad to connect workloads.
+---
+
+# Service discovery
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/discovery/dns
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.4.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.4.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2828748c9f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Learn about how service mesh works in Nomad to securely connect and isolate
+  your workloads.
+---
+
+# Service mesh
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.4.x/content/docs/operations/index.mdx b/content/nomad/v1.4.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.4.x/content/docs/operations/key-management.mdx b/content/nomad/v1.4.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..2f8b92165f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers store key metadata in raft, but
+the encryption key material is stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Replication
+
+When a leader is elected, it creates the keyring if it does not already
+exist. When a key is added, the metadata will be replicated via raft. Each
+server runs a key replication process that watches for changes to the state
+store and will fetch the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election.
+
+## Restoring the Keyring from Backup
+
+Key material is never stored in raft. This prevents an attacker with a backup of
+the state store from getting access to encrypted variables. It also allows the
+HashiCorp engineering and support organization to safely handle cluster
+snapshots you might provide without exposing any of your keys or variables.
+
+However, this means that to restore a cluster from snapshot you need to also
+provide the keystore directory with the `.nks.json` key files on at least one
+server. The `.nks.json` key files are unique per server, but only one server's
+key files are needed to recover the cluster. Operators should include these
+files as part of your organization's backup and recovery strategy for the
+cluster.
+
+If you are recovering a Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
diff --git a/content/nomad/v1.4.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.4.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..1f65ccc989
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,497 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_blocked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_blocked`           | Evaluations that are blocked until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+| --------------------------------------- | ----------------------------------------------------------------------------------- | ---------- | ----- | ------------------------------------------------------------------------------------- |
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations waiting for previous versions to exit                         | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating data from previous versions (see [`sticky`][sticky])| Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending (received by the client but not yet running)          | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                    | Unit                 | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------|----------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                    | Integer              | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                       | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                           | Integer              | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits) | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern. | Integer | Gauge | host |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer | Gauge | host |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                     | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                            | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                            | Nanoseconds          | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                   | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                    | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                           | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                          | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                            | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                          | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                       | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Summary` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition              | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                 | Integer              | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window       | Integer              | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                               | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                        | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                   | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                        | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                             | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                  | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                              | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                            | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                 | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                    | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                   | Milliseconds         | Gauge   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                      | Integer              | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                    | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                               | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                     | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler_service`        | Time elapsed for worker to invoke the scheduler                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                         | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                 | Nanoseconds          | Summary | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                   | Integer              | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                               | Integer              | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                  | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                             | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                           | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                         | Integer              | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication               | Nanoseconds          | Summary | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                       | Integer              | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                   | ms / Raft Log Append | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                              | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                               | Integer              | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                 | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                            | Integer              | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                           | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                              | Integer              | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                      | Nanoseconds          | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                    | # of bytes           | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                        | Nanoseconds          | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                    | Integer              | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                            | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                    | Integer              | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                    | Integer              | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                  | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                         | Integer              | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                             | Float                | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                         | Integer              | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://nomadproject.io/s/port-plan-failure
diff --git a/content/nomad/v1.4.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.4.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..56b641c531
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://www.nomadproject.io/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_blocked** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.4.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.4.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..18c8f3ba5c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+An agent can be stopped in two ways: gracefully or forcefully. By default, any
+stop signal to an agent (interrupt, terminate, kill) will cause the agent to
+forcefully stop. Graceful termination can be configured by either setting
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+When gracefully exiting, servers will notify their intention to leave the
+cluster which allows them to leave the [consensus][] peer set.
+
+It is especially important that a server node be allowed to leave gracefully so
+that there will be a minimal impact on availability as the server leaves the
+consensus peer set. If a server does not gracefully leave, and will not return
+into service, the [`server force-leave` command][] should be used to eject it
+from the consensus peer set.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..3a248237b6
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,421 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "write"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When an action is checked against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, the matching rule with the greatest number of matched characters will be
+chosen.
+
+For example the following policy will evaluate to deny for `production-web`,
+because it is 9 characters different from the `"*-web"` rule, but 13 characters
+different from the `"*"` rule.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be viewed.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered.
+- `csi-read-volume` - Allows inspecting a CSI volume and seeing fine grain
+  status.
+- `csi-list-volume` - Allows listing CSI volumes and seeing coarse grain status.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                    |
+| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `deny`  | deny                                                                                                                                                                                                                                                            |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                      |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                             |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..f1a2de1149
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,232 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), [`clone_id`](#clone_id),
+[`capacity_min`](#capacity_min), or [`capacity_max`](#capacity_max) fields on
+**volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.4.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.4.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.4.x/content/docs/partnerships.mdx b/content/nomad/v1.4.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..2defd3998d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. For a full description of the current features please refer to the [Nomad Website](/). The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.4.x/content/docs/runtime/environment.mdx b/content/nomad/v1.4.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..0da20d94b4
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale down/up as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IPs and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply arbitrary
+configuration to a task. This allows you to easily provide job-specific
+configuration even if you use the same executable unit in multiple jobs. These
+key-value pairs are passed through to the job as `NOMAD_META_<key>=<value>`
+environment variables. Prior to Nomad 0.5.5 the key was uppercased and since
+then both the original case and an uppercased version are injected. The
+uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.4.x/content/docs/runtime/index.mdx b/content/nomad/v1.4.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..21e6416ae3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.4.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.4.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..322c399054
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+The syntax for interpreting variables is `${variable}`. An example and a
+comprehensive list of interpretable fields can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Variables ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable                  | Description                                 | Example Value                          |
+| ------------------------- | ------------------------------------------- | -------------------------------------- |
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${attr.<property>}`        | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`        |
+| `${meta.<key>}`        | Metadata value given by `key` on the client | `${meta.foo} => bar`               |
+
+Below is a table documenting common node properties:
+
+| Property                                               | Description                                                                                                                                            |
+| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                              |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client avaible for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.          |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                              | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                       |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                 |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                               |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation.
+
+### Dots in Variables ((#dots_in_vars))
+
+Starting in Nomad 0.9, task configuration interpolation requires variables to
+be valid identifiers. While this does not affect default variables or common
+custom variables, it is possible to define a variable that is not a valid
+identifier:
+
+```hcl
+env {
+  "valid.name"     = "ok"
+  "invalid...name" = "not a valid identifier"
+}
+```
+
+The environment variable `invalid...name` cannot be interpolated using the
+standard `"${invalid...name}"` syntax. The dots will be interpreted as object
+notation so multiple consecutive dots are invalid.
+
+To continue supporting all user environment variables Nomad 0.9 added a new
+`env` variable which allows accessing any environment variable through index
+syntax:
+
+```hcl
+task "redis" {
+  driver = "docker"
+  config {
+    image  = "redis:7"
+    labels {
+      label1 = "${env["invalid...name"]}"
+      label2 = "${env["valid.name"]}"
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.4.x/content/docs/schedulers.mdx b/content/nomad/v1.4.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..48506abccf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/schedulers.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+Since Nomad 0.9, the system scheduler will preempt eligible lower priority
+tasks running on a node if there isn't enough capacity to place a system job.
+See [preemption] for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+## System Batch
+
+~> System Batch scheduling is new in Nomad 1.2.
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.4.x/content/docs/upgrade/index.mdx b/content/nomad/v1.4.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..315f2696fe
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 1 point release, so
+  Nomad v1.6.x hosts work with v1.5.x hosts. Upgrading 2 point releases
+  (for example, from v1.4.0 to v1.6.0) may work but is untested and unsupported.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`raft.peers`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `raft.peers` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
diff --git a/content/nomad/v1.4.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.4.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..b46cd7d30c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1590 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.4.11 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined without
+a label, and the documented behavior in this case was that the policy would be
+applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[cores]: /nomad/docs/job-specification/resources#cores
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hcl2]: https://github.com/hashicorp/hcl2
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[migrate]: /nomad/docs/job-specification/migrate
+[nvidia]: /nomad/plugins/devices/nvidia
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[pki]: /vault/docs/secrets/pki
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[enterprise licensing]: /nomad/docs/enterprise/license
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[`log_file`]: /nomad/docs/configuration#log_file
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
diff --git a/content/nomad/v1.4.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.4.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..4dd4b333dd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.4.x/content/intro/index.mdx b/content/nomad/v1.4.x/content/intro/index.mdx
new file mode 100644
index 0000000000..44757a5182
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.4.x/content/intro/use-cases.mdx b/content/nomad/v1.4.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..7082888c5d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.4.x/content/intro/vs/ecs.mdx b/content/nomad/v1.4.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.4.x/content/intro/vs/index.mdx b/content/nomad/v1.4.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.4.x/content/intro/vs/mesos.mdx b/content/nomad/v1.4.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.4.x/content/intro/vs/terraform.mdx b/content/nomad/v1.4.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.4.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.4.x/content/partials/envvars.mdx b/content/nomad/v1.4.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..4263657ee5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/partials/envvars.mdx
@@ -0,0 +1,59 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                   |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                     |
+| `NOMAD_SECRETS_DIR`      | Path to the task's secrets directory. See [here](/nomad/docs/runtime/environment#task-directories) for more information.                                                                                                                                                        |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                 |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                           |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                   |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request cpu cores. E.g. `0-2,7,12-14`                                                                                                                                        |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                       |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                          |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index. |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                     |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                    |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through CLI but can be different when using the API                                                                                                                                                                     |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                      |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                            |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                   |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                     |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                    |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                       |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Note that this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata.                                                                          |
+| `VAULT_TOKEN`            | The task's Vault token. See [Vault Integration](/nomad/docs/integrations/vault-integration) for more details                                                                                                                                                                    |
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                                                                                          |
+| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See [here for more](/nomad/docs/job-specification/network) information.                                                                                                                                                                                                                |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See [here for more](/nomad/docs/job-specification/network) information.                                                                         |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                                                                                      |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See [here](/nomad/docs/job-specification/network#mapped-ports) for more information.                                                                                                                                                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                                           |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                                         |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul Connect [upstream](/nomad/docs/job-specification/upstreams).                                                                                                                                                                                               |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul Connect enabled service. Envoy runs inside the group network namespace unless configured for host networking.                                                                                |
+
+~> **Note:** Port labels and task names will have any non-alphanumeric or
+  underscore characters in their names replaced by underscores `_` when they're
+  used in environment variable names such as `NOMAD_ADDR_<task>_<label>`.
+
+### Consul-related Variables
+
+This variables are only set for Connect native tasks.
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a tcp address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Connect service identity token specific to the service instance if Consul ACLs are enabled. |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the CLient Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
diff --git a/content/nomad/v1.4.x/content/partials/general_options.mdx b/content/nomad/v1.4.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..bb9ece3878
--- /dev/null
+++ b/content/nomad/v1.4.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespaces authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.4.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.4.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.4.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.4.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.4.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.4.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.4.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.4.x/content/plugins/devices/index.mdx b/content/nomad/v1.4.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.4.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.4.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..0302bf9fcd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..5aa129c9cd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..6620f08eec
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[rkt]: /nomad/plugins/drivers/community/rkt
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..3a0a46f932
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionaly, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..0bc5c66b99
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..dfbb3dfb11
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:7"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /nomad/docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.4.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/index.mdx b/content/nomad/v1.4.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.4.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..7f8107cadf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,580 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+Due to Podman's similarity to Docker, the example job created by
+[`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- [Nomad][nomad_download] 0.12.9+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroup V2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a 3.0.x podman binary and a system socket activation unit, refer to
+[https://www.redhat.com/sysadmin/podmans-new-rest-api](https://www.redhat.com/sysadmin/podmans-new-rest-api).
+
+Nomad agent, `nomad-driver-podman` and `podman` will reside on the same client,
+so you do not have to worry about the `ssh` aspects of the Podman api.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart. Consider a
+  simple single node system and a complete reboot. All previously managed
+  containers will be reused instead of disposed and recreated.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.4.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..b4346bd020
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.4.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.4.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..d2c3a0eff1
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]:  /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.4.x/content/plugins/index.mdx b/content/nomad/v1.4.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..87d3059efd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.4.x/content/security.mdx b/content/nomad/v1.4.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.4.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..6d2ae9d188
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..ca630dff4c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..01be84617b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..5340d70b45
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..7745568465
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+  for the allocation.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+  allocated for the allocation.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..13ef0a2aab
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..b8b626e869
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d91143a086
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..a702f00bde
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..7bf2dbc6d7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+
+[client_meta_tag]: #client-meta-tag
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..f7df5bd0e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..fcf2188daf
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.4.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.4.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..9113f451e7
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.4.x/content/tools/index.mdx b/content/nomad/v1.4.x/content/tools/index.mdx
new file mode 100644
index 0000000000..b983db640f
--- /dev/null
+++ b/content/nomad/v1.4.x/content/tools/index.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+- [OpenAPI](https://github.com/hashicorp/nomad-openapi) - An OpenAPI/Swagger spec for Nomad, allowing for programmatic generation of SDKs and documentation. Includes a reference implementation in Go built on top of a generated client.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata.
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.4.x/data/api-docs-nav-data.json b/content/nomad/v1.4.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..58e3ca94f4
--- /dev/null
+++ b/content/nomad/v1.4.x/data/api-docs-nav-data.json
@@ -0,0 +1,170 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "path": "variables"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.4.x/data/docs-nav-data.json b/content/nomad/v1.4.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..e0c38e726d
--- /dev/null
+++ b/content/nomad/v1.4.x/data/docs-nav-data.json
@@ -0,0 +1,2138 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Service Mesh",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          }
+        ]
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "keygen",
+            "path": "commands/operator/keygen"
+          },
+          {
+            "title": "keyring",
+            "path": "commands/operator/keyring"
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.4.x/data/intro-nav-data.json b/content/nomad/v1.4.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..23d2019f14
--- /dev/null
+++ b/content/nomad/v1.4.x/data/intro-nav-data.json
@@ -0,0 +1,56 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "https://learn.hashicorp.com/collections/nomad/get-started"
+      },
+      {
+        "title": "Running Nomad",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-run"
+      },
+      {
+        "title": "Jobs",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-jobs"
+      },
+      {
+        "title": "Clustering",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/clustering"
+      },
+      {
+        "title": "Web UI",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-ui"
+      },
+      {
+        "title": "Next Steps",
+        "href": "https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.4.x/data/plugins-nav-data.json b/content/nomad/v1.4.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..76f9127194
--- /dev/null
+++ b/content/nomad/v1.4.x/data/plugins-nav-data.json
@@ -0,0 +1,117 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.4.x/data/tools-nav-data.json b/content/nomad/v1.4.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..51a278df1f
--- /dev/null
+++ b/content/nomad/v1.4.x/data/tools-nav-data.json
@@ -0,0 +1,227 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.4.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.4.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.4.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.4.x/img/autoscaling/control-loop.png b/content/nomad/v1.4.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.4.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.4.x/img/autoscaling/policy-eval.png b/content/nomad/v1.4.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.4.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.4.x/img/count-dashboard.png b/content/nomad/v1.4.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.4.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.4.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.4.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.4.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/favicon-16x16.png b/content/nomad/v1.4.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/favicon-194x194.png b/content/nomad/v1.4.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/favicon-32x32.png b/content/nomad/v1.4.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/favicon.ico b/content/nomad/v1.4.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.4.x/img/favicons/mstile-144x144.png b/content/nomad/v1.4.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/mstile-150x150.png b/content/nomad/v1.4.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/mstile-310x150.png b/content/nomad/v1.4.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/mstile-310x310.png b/content/nomad/v1.4.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/mstile-70x70.png b/content/nomad/v1.4.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.4.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.4.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.4.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.4.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.4.x/img/home-hero-pattern.svg b/content/nomad/v1.4.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.4.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/img/logo-hashicorp.svg b/content/nomad/v1.4.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.4.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.4.x/img/logo-text.svg b/content/nomad/v1.4.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.4.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.4.x/img/networking/bridge.png b/content/nomad/v1.4.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.4.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.4.x/img/networking/docker_bridge.png b/content/nomad/v1.4.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.4.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.4.x/img/networking/port_mapping.png b/content/nomad/v1.4.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.4.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-architecture-global.png b/content/nomad/v1.4.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-architecture-region.png b/content/nomad/v1.4.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-bg-pattern.svg b/content/nomad/v1.4.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.4.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.4.x/img/nomad-bridge-network.png b/content/nomad/v1.4.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-data-model.png b/content/nomad/v1.4.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-evaluation-flow.png b/content/nomad/v1.4.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-kubernetes.png b/content/nomad/v1.4.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.4.x/img/nomad-panel-learn.svg b/content/nomad/v1.4.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.4.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.4.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.4.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.4.x/img/nomad-workload.png b/content/nomad/v1.4.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.4.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.4.x/img/og-image.png b/content/nomad/v1.4.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.4.x/img/og-image.png differ
diff --git a/content/nomad/v1.4.x/img/pattern.svg b/content/nomad/v1.4.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.4.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/img/practice-pattern.svg b/content/nomad/v1.4.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.4.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/img/usecase-callout-pattern.svg b/content/nomad/v1.4.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.4.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/img/usecase-hero-pattern.svg b/content/nomad/v1.4.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.4.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.4.x/redirects.jsonc b/content/nomad/v1.4.x/redirects.jsonc
new file mode 100644
index 0000000000..6a64fb18a0
--- /dev/null
+++ b/content/nomad/v1.4.x/redirects.jsonc
@@ -0,0 +1,18 @@
+[
+  // Rename and re-arrange Autoscaling Internals section
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.5.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..f302563459
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,497 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+  The name can contain alphanumeric characters, dashes, and underscores. This
+  name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and `JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either `local` or `global`.
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set, it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+    any `.well-known` component (base path). Required for `OIDC` method type.
+    Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+    `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+    your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+    configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+    to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+    `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+    signatures. Either this, the `JWTValidationPubKeys` or the
+    `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+    to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+    validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+    validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+    validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Names is the identifier of the ACL auth
+  method.  The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth role SSO identifier. Currently, the
+  only supported Type is "OIDC."
+
+- `TokenLocality` `(string: "")` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either "local" or "global"
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL auth method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: nil)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: "")` - The OIDC discovery URL, without
+    any .well-known component (base path).
+
+  - `OIDCClientID` `(string: "")` - The OAuth client ID configured with
+    your OIDC provider.
+
+  - `OIDCClientSecret` `(string: "")` - The OAuth client secret
+    configured with your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.5.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..93451a8704
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `POST` | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/index.mdx b/content/nomad/v1.5.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..318f42b704
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/login.mdx b/content/nomad/v1.5.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..eea54db196
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.5.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.5.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..4e07722b8c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,188 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given
+  namespace, job, group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - The namespace to attach the policy.
+    Required if `JobID` is set.
+
+  - `JobID` `(string: <optional>)` - The job to attach to the policy. Required
+    if `Group` is set.
+
+  - `Group` `(string: <optional>)` - The group to attach to the policy.
+    Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - The task to attach to the policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.5.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..d99aa9efaf
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `POST` | `/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                 | Produces       |
+| -------- | -------------------- | -------------- |
+| `DELETE` | `/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.5.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..9d81cee9c9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.5.x/content/api-docs/agent.mdx b/content/nomad/v1.5.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..5e70a2af66
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/agent.mdx
@@ -0,0 +1,927 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.5.x/content/api-docs/allocations.mdx b/content/nomad/v1.5.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..b008dbbe51
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/allocations.mdx
@@ -0,0 +1,960 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.5.x/content/api-docs/client.mdx b/content/nomad/v1.5.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..f5898ef79c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node recieving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node recieving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.5.x/content/api-docs/deployments.mdx b/content/nomad/v1.5.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/evaluations.mdx b/content/nomad/v1.5.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..db1bce0e4b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,446 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.5.x/content/api-docs/events.mdx b/content/nomad/v1.5.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..1a811f887e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/events.mdx
@@ -0,0 +1,387 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/index.mdx b/content/nomad/v1.5.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..55713ae728
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/index.mdx
@@ -0,0 +1,699 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> --data-urlencode 'filter=<filter expression>'
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/jobs \
+    --data-urlencode 'filter=Datacenters contains "dc2"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/deployments \
+    --data-urlencode 'filter=Status != "successful"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.5.x/content/api-docs/jobs.mdx b/content/nomad/v1.5.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..de095e367f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2430 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+## Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client gets an allocation.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```
+
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `IdempotencyToken` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.5.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..20766dd3a5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1210 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.5.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.5.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..828cb1af80
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.5.x/content/api-docs/metrics.mdx b/content/nomad/v1.5.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/namespaces.mdx b/content/nomad/v1.5.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f1050081cc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,205 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+~> Prior to Nomad 1.0 Namespaces were an Enterprise-only feature.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` - Specifies an quota to attach to the namespace.
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota"
+}
+```
+
+Note that the `Quota` key is Enterprise-only.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/nodes.mdx b/content/nomad/v1.5.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..834e35388b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1144 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.5.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..76bc8d1346
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/index.mdx b/content/nomad/v1.5.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.5.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..ad4975c121
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,157 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/license.mdx b/content/nomad/v1.5.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.5.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..b6313223f0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.5.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..fdad37cda3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,202 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+    `true`, tasks may exceed their reserved memory limit, if the client has excess
+    memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` <sup>1.1 Beta</sup> - When
+  `true`, tasks may exceed their reserved memory limit, if the client has excess
+  memory capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription.
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
diff --git a/content/nomad/v1.5.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.5.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.5.x/content/api-docs/plugins.mdx b/content/nomad/v1.5.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..f6676906c1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/plugins.mdx
@@ -0,0 +1,137 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-plugin` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-plugin` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/quotas.mdx b/content/nomad/v1.5.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..112d80d7e9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/quotas.mdx
@@ -0,0 +1,354 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/recommendations.mdx b/content/nomad/v1.5.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/regions.mdx b/content/nomad/v1.5.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.5.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/search.mdx b/content/nomad/v1.5.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..4e6a0f7ad9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/search.mdx
@@ -0,0 +1,591 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, deployments, plugins,
+namespaces, or volumes. When using Nomad Enterprise, the allowed contexts
+include quotas. Additionally, a prefix can be searched for within every
+context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "deployment", "plugins", "volumes" or "all", where "all" means every
+  context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given search
+term and context, where a context can be jobs, allocations, nodes, plugins, or namespaces.
+Additionally, fuzzy searching can be done across all contexts. For better control
+over the performance implications of fuzzy searching on Nomad servers, aspects of
+fuzzy searching can be tuned through the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "plugins", or
+  "all", where "all" means every context will be searched. When "all" is selected,
+  additional prefix matches will be included for the "deployments", "evals", and
+  "volumes" types. When searching in the "jobs" context, results that fuzzy match
+  "groups", "services", "tasks", "images", "commands", and "classes" are also
+  included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.5.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.5.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/services.mdx b/content/nomad/v1.5.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/api-docs/status.mdx b/content/nomad/v1.5.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/system.mdx b/content/nomad/v1.5.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/task-api.mdx b/content/nomad/v1.5.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..31f8038074
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/task-api.mdx
@@ -0,0 +1,103 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+[acl]: /nomad/docs/concepts/acl
+[acl-tokens]: /nomad/docs/concepts/acl#token
+[alloc-exec]: /nomad/docs/commands/alloc/exec
+[anon]: /nomad/tutorials/access-control/access-control#acl-policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[dnm]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.5.x/content/api-docs/ui.mdx b/content/nomad/v1.5.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.5.x/content/api-docs/validate.mdx b/content/nomad/v1.5.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.5.x/content/api-docs/variables.mdx b/content/nomad/v1.5.x/content/api-docs/variables.mdx
new file mode 100644
index 0000000000..f68c0fbd54
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/variables.mdx
@@ -0,0 +1,298 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`] commands.
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+
+[Variables]: /nomad/docs/concepts/variables
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.5.x/content/api-docs/volumes.mdx b/content/nomad/v1.5.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..a7569a5464
--- /dev/null
+++ b/content/nomad/v1.5.x/content/api-docs/volumes.mdx
@@ -0,0 +1,783 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/create.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..8cc6519a78
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/create.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method create'
+description: The auth-method create command is used to create new ACL Auth Methods.
+---
+
+# Command: acl auth-method create
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = local
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..45303a5658
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method delete'
+description: The auth-method delete command is used to delete existing ACL Auth Methods.
+---
+
+# Command: acl auth-method delete
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/info.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..1f7605213a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/info.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method info'
+description: |
+  The auth-method info command is used to fetch information about an existing
+  ACL Auth Method.
+---
+
+# Command: acl auth-method info
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = local
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/list.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..0cb15df8e6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method list'
+description: The auth-method list command is used to list existing ACL Auth Methods.
+---
+
+# Command: acl auth-method list
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/update.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..2dd8a9d668
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/auth-method/update.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method update'
+description: The auth-method update command is used to update existing ACL Auth Methods.
+---
+
+# Command: acl auth-method update
+
+The `acl auth-method update` command is used to update existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -config @config.json example-acl-auth-method
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = global
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/create.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..1f3c56f39f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule create'
+description: The binding-rule create command is used to create new ACL Binding Rules.
+---
+
+# Command: acl binding-rule create
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..0bdafd9689
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule delete'
+description: The binding-rule delete command is used to delete existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule delete
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/info.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..38dcfb2eeb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule info'
+description: |
+  The binding-rule info command is used to fetch information about an existing
+  ACL Binding Rule.
+---
+
+# Command: acl binding-rule info
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/list.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..d506f8a8d2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule list'
+description: The binding-rule list command is used to list existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule list
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/update.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..03bacdd24d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule update'
+description: The binding-rule update command is used to update existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule update
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..f797d33d2e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an apropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..d079e2ca12
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[authmethodcreate]: /nomad/docs/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/docs/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/docs/commands/acl/auth-method/info
+[authmethodlist]: /nomad/docs/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/docs/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/docs/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/docs/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/docs/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/docs/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/docs/commands/acl/binding-rule/update
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..af000cd896
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..f0622d92c4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..64d72c4b0c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl role create'
+description: The role create command is used to create new ACL Roles.
+---
+
+# Command: acl role create
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..f4e4a93b9f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl role delete'
+description: The role delete command is used to delete existing ACL Roles.
+---
+
+# Command: acl role delete
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..7a2f40a8bd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl role info'
+description: |
+  The role info command is used to fetch information about an existing ACL
+  Role.
+---
+
+# Command: acl role info
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..6f36f8d065
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl role list'
+description: The role list command is used to list existing ACL Roles.
+---
+
+# Command: acl role list
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..cc808f8386
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl role update'
+description: The role update command is used to update existing ACL Roles.
+---
+
+# Command: acl role update
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..5c0c77d051
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..33e442126e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..fb8fc94ac2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..b58a7193b8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.5.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..57c293382f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.5.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/agent.mdx b/content/nomad/v1.5.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..c391423566
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/agent.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[nomad agent]: /nomad/docs/operations/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/checks.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..fc1b02c1e2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: alloc checks'
+description: |
+  Outputs service health check status information.
+---
+
+# Command: alloc checks
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability 
+for the allocation's namespace. The 'list-jobs' capability is required to run the 
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Checks Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..b62c55d4cf
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be use to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job ID.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..b03e3ae9a6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..b673a63f04
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/docs/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..c94a7f4f0c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job, preferring a running
+  allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.5.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..718d962d57
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.5.x/content/docs/commands/config/index.mdx b/content/nomad/v1.5.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.5.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.5.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..9c72af2dce
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..d40b151754
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3369798607
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..86542733e2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.5.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..9214e1adf4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.5.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..a4900f08ff
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfuly deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfuly deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfuly deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.5.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.5.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.5.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.5.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.5.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/fmt.mdx b/content/nomad/v1.5.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..d40d17c95a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: fmt'
+description: |
+  Rewrite Nomad config and job files to canonical format
+---
+
+# Command: fmt
+
+The `fmt` commands check the syntax and rewrites Nomad configuration and jobspec
+files to canonical format. It can be used to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [flags] paths ...
+```
+
+Formats Nomad agent configuration and job file to a canonical format. If a path
+is a directory, it will recursively format all files with .nomad and .hcl
+extensions in the directory.
+
+If you provide a single dash (-) as argument, fmt will read from standard input
+(STDIN) and output the processed output to standard output (STDOUT).
+
+Note that, this command will check the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 jobspec will result in errors.
+
+## Format Options:
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/index.mdx b/content/nomad/v1.5.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.5.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..72f2e9a443
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.5.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..ccfcf28be1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.5.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..235cc952c3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.5.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..05199a5499
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/history.mdx b/content/nomad/v1.5.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..9544f64140
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/index.mdx b/content/nomad/v1.5.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..47ff5c79d8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/init.mdx b/content/nomad/v1.5.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..1c5a7d5ecc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.5.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..a96593f779
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.5.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..8aca82eb80
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.5.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..2d62783d19
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,263 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.5.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..28dab1fc76
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/restart.mdx b/content/nomad/v1.5.x/content/docs/commands/job/restart.mdx
new file mode 100644
index 0000000000..6f87e40a82
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'Commands: job restart'
+description: |
+  The job restart command is used to restart allocations for a job.
+---
+
+# Command: job restart
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+Allocations can be restarted in-place or rescheduled. When restarting
+in-place the command may target specific tasks in the allocations, restart
+only tasks that are currently running, or restart all tasks, even the ones
+that have already run. Allocations can also be targeted by groups and tasks.
+When both groups and tasks are defined only the tasks for the allocations of
+those groups are restarted.
+
+When rescheduling, the current allocations are stopped triggering the Nomad
+scheduler to create replacement allocations that may be placed in different
+clients. The command waits until the new allocations have client status `ready`
+before proceeding with the remaining batches. Services health checks are not
+taken into account.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, allocations are stopped and rescheduled instead of
+  restarted in-place. Since the group is not modified the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such
+  as [`max_parallel`][], are not taken into account. This option cannot be used
+  with `-task`. Only jobs of type `batch`, `service`, and `system` can be
+  rescheduled.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.5.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..f0bd4efa60
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/run.mdx b/content/nomad/v1.5.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..36f2c87f85
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.5.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..f3171dc5f3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.5.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..dd639766f6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/status.mdx b/content/nomad/v1.5.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..5842f80592
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.5.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..ad19f5afac
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.5.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.5.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..738f7f759f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.5.x/content/docs/commands/license/get.mdx b/content/nomad/v1.5.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..e890fb74fe
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/license/index.mdx b/content/nomad/v1.5.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..f08fd21f06
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are new in Nomad 0.12.0 and are only available with Nomad Enterprise.
+
+The `license` command provides cluster level management of the Nomad Enterprise license.
+
+If ACLs are enabled then a token with operator privileges may be required in order to use
+this command.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license'
diff --git a/content/nomad/v1.5.x/content/docs/commands/login.mdx b/content/nomad/v1.5.x/content/docs/commands/login.mdx
new file mode 100644
index 0000000000..1dd2bf1645
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/login.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: login'
+description: |
+  Login to Nomad using an authentication method
+---
+
+# Command: login
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Login Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/monitor.mdx b/content/nomad/v1.5.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..ff0738014c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..347fa969cd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers  = ["docker", "exec"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..5e2edef272
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs. In federated clusters,
+you cannot delete a namespace that has non-terminal jobs in any of the federated
+regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..5117fa50bb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..f2cc7c3304
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..0f6eedfba3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.5.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..2c0fc2cd2e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+~> Namespaces are open source in Nomad 1.0. Namespaces were Enterprise-only
+when introduced in Nomad 0.7.
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name            = api-prod
+Description     = Prod API servers
+Quota           = prod
+EnabledDrivers  = docker,exec
+DisabledDrivers = raw_exec
+ 
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default                                                             
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/config.mdx b/content/nomad/v1.5.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.5.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..af162841a1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,155 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away. Allocations will be migrated according
+to their [`migrate`][migrate] block until the drain's deadline is reached.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[migrate]: /nomad/docs/job-specification/migrate
+[`migrate`]: /nomad/docs/job-specification/migrate
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.5.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/index.mdx b/content/nomad/v1.5.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..289d1a027f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/docs/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/meta/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..5b67230336
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: node meta apply'
+description: |
+  The node meta apply command updates node metadata.
+---
+
+# Command: node meta apply
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Apply Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+[api]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/meta/index.mdx b/content/nomad/v1.5.x/content/docs/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..2b65048e5b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/meta/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: node meta'
+description: |
+  The node meta commands are used to read and update node metadata.
+---
+
+# Command: node meta
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+Usage: `nomad node meta <subcommand> [options]`
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/runtime/interpolation#node-attributes
+[apply]: /nomad/docs/commands/node/meta/apply
+[read]: /nomad/docs/commands/node/meta/read
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/meta/read.mdx b/content/nomad/v1.5.x/content/docs/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..8564cf7e5e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: node meta read'
+description: |
+  The node meta read command reads node metadata.
+---
+
+# Command: node meta read
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Read Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+[api]: /nomad/api-docs/client#read-node-metadata
diff --git a/content/nomad/v1.5.x/content/docs/commands/node/status.mdx b/content/nomad/v1.5.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..2a7075d8c4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,397 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjuction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID     = c754da1f
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID     = c754da1f
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Uptime  = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID     = c754da1f
+Name   = nomad-client01
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID     = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name   = nomad
+Class  = <none>
+DC     = dc1
+Drain  = false
+Status = ready
+Uptime = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/client-state.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..6475fe5477
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'Commands: operator client-state'
+description: >
+  The `operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# Command: operator client-state
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..7121935fa8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..d703f46ae8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring generate'
+description: >
+  The `operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator gossip keyring generate
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..e30c21b5b4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring install'
+description: |
+  Install a new gossip encryption key
+---
+
+# Command: operator gossip keyring install
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..e05d940bd9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring list'
+description: |
+  List gossip keys
+---
+
+# Command: operator gossip keyring list
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..97009d769f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring remove'
+description: |
+  Remove a new gossip encryption key
+---
+
+# Command: operator gossip keyring remove
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..708b506787
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring use'
+description: |
+  Use a new gossip encryption key
+---
+
+# Command: operator gossip keyring use
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..fd097a007a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/docs/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/docs/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/docs/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/docs/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/docs/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/docs/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/docs/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/docs/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..e5f337b373
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+description: |-
+  The `operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..e049b8b795
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring list'
+description: |
+  List encryption key metadata
+---
+
+# Command: operator root keyring list
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..bcf701378e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring remove'
+description: |
+  Remove an unused encryption key
+---
+
+# Command: operator root keyring remove
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..2ba424ef24
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring rotate'
+description: |
+  Rotate encryption key
+---
+
+# Command: operator root keyring rotate
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Rotate Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+    command will immediately return and the re-encryption process will run
+    asynchronously on the leader.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate
+Key       State   Create Time
+f19f6029  active  2022-07-11T19:14:36Z
+
+$ nomad operator root keyring rotate -verbose
+Key                                   State   Create Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..b3d7049f73
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+<Warning>
+
+This snapshot agent only saves a Raft snapshot. Key material for the Nomad
+keyring is stored on disk and must be saved separately. To use a snapshot saved
+by the agent to recover a cluster, you will also need to [restore the keyring][]
+onto at least one server.
+
+</Warning>
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
+
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..221452f1d2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file on disk.
+
+To inspect the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+ID       2-19-1592495928936
+Size     3902
+Index    19
+Term     2
+Version  1
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect <file>
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..53ab825206
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+Restores an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This command is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+This command only restores the Raft snapshot. If you are recovering a cluster,
+you will also need to [restore the keyring][] onto at least one server.
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+To restore a snapshot from the file "backup.snap":
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..9f7a2bfbe6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+Retrieves an atomic, point-in-time snapshot of the state of the Nomad servers
+which includes jobs, nodes, allocations, periodic jobs, and ACLs for [outage
+recovery].
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+<Warning>
+
+This command only saves a Raft snapshot. If you use this snapshot to recover a
+cluster, you will also need to [restore the keyring][] onto at least one server.
+
+</Warning>
+
+To create a snapshot from the leader server and save it to "backup.snap":
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+To create a potentially stale snapshot from any available server (useful if no
+leader is available):
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.5.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.5.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.5.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..6746241535
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..0956cba4d5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..afc21d99d1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..29b226bb43
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..97aaa16bb5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..24e34442cc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.5.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..c9a8ec7dbb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..3660b9f70f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.5.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..8d930e8c57
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.5.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..7b2665192c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.5.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.5.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..a0f80bb60d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.5.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..2111f423b6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are new in Nomad 1.0 and are only available with
+Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.5.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..1f70f5d317
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+~> Scaling commands are new in Nomad 1.0.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.5.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.5.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.5.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.5.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..088b249d0d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..18263c8338
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.5.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f904c7b714
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.5.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.5.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..75bef2f684
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.5.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..fb97b3cbff
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are new in Nomad 0.7 and are only available with Nomad
+Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.5.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d31ab75e70
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/server/index.mdx b/content/nomad/v1.5.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.5.x/content/docs/commands/server/join.mdx b/content/nomad/v1.5.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..a5a6661ec8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: /nomad/tutorials/manage-clusters/federation
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.5.x/content/docs/commands/server/members.mdx b/content/nomad/v1.5.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..3ace4d8db8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server memebers in its JSON format.
+
+- `-t`: Format and display the server memebers using a Go template.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..0eb973622c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/service/index.mdx b/content/nomad/v1.5.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..a6f207b0a8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.5.x/content/docs/commands/service/info.mdx b/content/nomad/v1.5.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..9287f4da0f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/service/list.mdx b/content/nomad/v1.5.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..7c09b6acb4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+~> Service commands are new in Nomad 1.3.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/status.mdx b/content/nomad/v1.5.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.5.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/system/index.mdx b/content/nomad/v1.5.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.5.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.5.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.5.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..01deb51ec0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'Commands: tls ca create'
+description: |
+  This command creates a Certificate Authority that can be used to create
+  self signed certificates to be used for Nomad TLS setup.
+---
+
+# Command: nomad tls ca create
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## CA Create Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.5.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..0261571b19
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: tls ca info'
+description: |
+  This command displays relevant information that is contained within a
+  Certificate Authority certificate.
+---
+
+# Command: nomad tls ca info
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.5.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..d0fc2d5bb0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Create'
+description: |
+  This command creates a Certificate that can be used for Nomad TLS setup.
+---
+
+# Command: nomad tls cert create
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Command Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-cluster-region=<string>`: DEPRECATED please use `-region`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.5.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.5.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..c37f6a54c0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Info'
+description: |
+  This command displays relevant information that is contained within a
+  certificate.
+---
+
+# Command: nomad tls cert info
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.5.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..1e580053ee
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: tls'
+description: |
+  The tls command is used to help with creating a Certificate Authority 
+  and up self signed certificates for Nomad TLS configuration.
+---
+
+# Command: tls
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
\ No newline at end of file
diff --git a/content/nomad/v1.5.x/content/docs/commands/ui.mdx b/content/nomad/v1.5.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/get.mdx b/content/nomad/v1.5.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..3639942887
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: "Command: var get"
+description: |-
+  The "var get" command retrieves the variable at the given path from
+  Nomad. If no variable exists at that path, an error is returned.
+---
+
+# Command: var get
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/index.mdx b/content/nomad/v1.5.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..16f7bd5334
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: "Commands: var"
+description: |-
+  The "var" command groups subcommands for interacting with Nomad variables.
+---
+
+# Command: var
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/init.mdx b/content/nomad/v1.5.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..8a99bf81fa
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: var init'
+description: |
+  Generate an example variable specification.
+---
+
+# Command: var init
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/list.mdx b/content/nomad/v1.5.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d8974ffff2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: "Command: var list"
+description: |-
+  The "var list" command lists data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# Command: var list
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.5.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..c924fa77ab
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: "Command: var purge"
+description: |-
+  The "var purge" command permanently removes the specified variable
+  from Nomad.
+---
+
+# Command: var purge
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Command Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.5.x/content/docs/commands/var/put.mdx b/content/nomad/v1.5.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..34a361ad3a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: "Command: var put"
+description: |-
+  The "var put" command writes a variable to the given path in Nomad.
+---
+
+# Command: var put
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.5.x/content/docs/commands/version.mdx b/content/nomad/v1.5.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b58b9ae222
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..39b0b39c93
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..726ed55b84
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.5.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.5.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..d371d7f455
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.5.x/content/docs/concepts/acl.mdx b/content/nomad/v1.5.x/content/docs/concepts/acl.mdx
new file mode 100644
index 0000000000..aee744db85
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/acl.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Access Control List (ACL)
+description: Learn about Nomad's ACL subsystem
+---
+
+# Access Control List (ACL)
+
+The Nomad ACL system is designed to be intuitive, high-performance, and to
+provide administrative insight. At the highest level, there are four major
+components to the ACL system: tokens, policies, roles, and capabilities. The
+two components named auth methods and binding rules are specific to Nomad's
+Single Sign-On (SSO) ACL capabilities.
+
+The Nomad [access control tutorials][] provide detailed information and
+guidance on Nomad ACL system.
+
+### Policy
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy comprises one or more rules. The rules define the capabilities of a
+Nomad ACL token for accessing the objects in a Nomad cluster, objects like
+namespaces, node, agent, operator, quota, etc. For more information on writing
+policies, see the [ACL policy reference doc][].
+
+### Role
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+### Token
+
+Requests to Nomad are authenticated using a bearer token. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. `Local` tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+### Workload Identity
+
+Nomad allocations can receive workload identities in the form of a
+[JSON Web Token (JWT)][jwt]. The
+[Workload Identity concept page][workload identity] has more information on
+this topic.
+
+### Auth Method
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+### Binding Rule
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[access control tutorials]: /nomad/tutorials/access-control
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
+[vault]: https://www.vaultproject.io/
diff --git a/content/nomad/v1.5.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.5.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..7549bf4d88
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,175 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+# Glossary
+
+Before describing the architecture, we provide a glossary of terms to help
+clarify what is being discussed:
+
+#### Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+#### Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+#### Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+#### Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+#### Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+#### Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+#### Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+#### Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+#### Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+#### Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+#### Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+#### Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+# High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+# Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, ask in IRC or reach out to the mailing list.
+
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.5.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.5.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.5.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.5.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..c0514750e9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,470 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.5.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.5.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..d5b2f7cf42
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/nomad/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.5.x/content/docs/concepts/index.mdx b/content/nomad/v1.5.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..9c0dbb461c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Network Plugins
+description: Learn how Nomad manages custom user-specified network configurations.
+---
+
+# Network plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..a7f5a4ed19
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..79e2aa1a75
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.5.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.5.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..308da7a1ff
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,256 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propogating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
diff --git a/content/nomad/v1.5.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.5.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..9c17dc0d8d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.5.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.5.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..291008f78b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.5.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.5.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..9c07454ff5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering unhealthy nodes, those missing necessary drivers, and those failing
+the specified constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.5.x/content/docs/concepts/security.mdx b/content/nomad/v1.5.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..739932e206
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/security.mdx
@@ -0,0 +1,339 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** -
+  Access to read and write to a namespace can be
+  controlled to allow for granular access to job information managed within a
+  multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
+
+
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
diff --git a/content/nomad/v1.5.x/content/docs/concepts/variables.mdx b/content/nomad/v1.5.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..85016a45e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Variables
+description: Learn about the Nomad Variables feature
+---
+
+# Nomad Variables
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to [provide such configuration to tasks](/nomad/docs/job-specification/template#nomad-variables),
+but prior to Nomad 1.4 has left the role of storing that configuration to
+external services such as [HashiCorp Consul] and [HashiCorp Vault].
+
+Nomad Variables provide the option to store configuration at file-like paths
+directly in Nomad's state store. You can [access these variables](/nomad/docs/job-specification/template#nomad-variables) directly from
+your task `template`s. The contents of these variables are encrypted
+and replicated between servers via raft. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the Variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as Variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. See [Key Management][] for details.
+
+## ACL for Variables
+
+Every Variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to Variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for Variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+In Nomad 1.4.0 tasks can only access Variables with the [`template`] block. The
+[workload identity] for each task grants it automatic read and list access to
+Variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to Variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
diff --git a/content/nomad/v1.5.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.5.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..b1c22ab2bd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Learn about Nomad's workload identity feature
+---
+
+# Workload Identity
+
+Every workload running in Nomad is given an identity. When an [allocation][] is
+accepted by the [plan applier][], the leader generates a Workload Identity for
+each task in the allocation. This workload identity is a [JSON Web Token
+(JWT)][] that has been signed by the leader's keyring. The workload identity
+includes the following identity claims:
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+## Using Workload Identity
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+## Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+## Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
diff --git a/content/nomad/v1.5.x/content/docs/configuration/acl.mdx b/content/nomad/v1.5.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..64c0263182
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. Note that the Nomad command
+  line client will send requests for client endpoints such as `alloc exec`
+  directly to Nomad clients whenever they are accessible. In this scenario, the
+  client will enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. See [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.5.x/content/docs/configuration/audit.mdx b/content/nomad/v1.5.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.5.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.5.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.5.x/content/docs/configuration/client.mdx b/content/nomad/v1.5.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..716a1ca24d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/client.mdx
@@ -0,0 +1,736 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This can be used during job
+  placement as a filter.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+Drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file
+system isolation using chroot on Linux. The `chroot_env` map allows the chroot
+environment to be configured using source paths on the host operating system.
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+When `chroot_env` is unspecified, the `exec` driver will use a default chroot
+environment with the most commonly used parts of the operating system. Please
+see the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+As of Nomad 1.2, Nomad will never attempt to embed the `alloc_dir` in the
+chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata, Network Speed, and Node Class
+
+This example shows a client configuration which customizes the metadata, network
+speed, and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/docs/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.5.x/content/docs/configuration/consul.mdx b/content/nomad/v1.5.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..cda50bede1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,247 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+   certificate used for communication between Connect sidecar proxies and Consul
+   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+   <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. See
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](/consul/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes. Will default to the `CONSUL_HTTP_TOKEN`
+  environment variable if set.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
diff --git a/content/nomad/v1.5.x/content/docs/configuration/index.mdx b/content/nomad/v1.5.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..2989c5bed7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/index.mdx
@@ -0,0 +1,398 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, or `DEBUG` in
+  increasing order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.5.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.5.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.5.x/content/docs/configuration/search.mdx b/content/nomad/v1.5.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.5.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.5.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.5.x/content/docs/configuration/server.mdx b/content/nomad/v1.5.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..630d599d5c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/server.mdx
@@ -0,0 +1,503 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens. Non-authoritative regions will replicate from
+  the authoritative to act as a mirror. By default, the local region is assumed
+  to be authoritative. Setting `authoritative_region` assumes that ACLs have
+  been bootstrapped in the authoritative region. See [Configure for multiple
+  regions][] in the ACLs tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". See [Client Heartbeats](#client-heartbeats) below for details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients
+  must heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". See [Client Heartbeats](#client-heartbeats) below
+  for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. See [Client Heartbeats](#client-heartbeats)
+  below for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time that an
+  [encryption key][] must exist before it can be eligible for garbage
+  collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the minimum time
+  that an [encryption key][] must exist before it is automatically rotated on
+  the next garbage collection interval.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false # New in Nomad 1.3.2
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true # New in Nomad 1.2
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`max_client_disconnect`][max_client_disconnect] is set)
+and rescheduled.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer a `down` Client's workload will
+  take to be rescheduled.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  rescheduled.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO (see below)       |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and reschedules their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator gossip keyring generate`]: /nomad/docs/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[max_client_disconnect]: /nomad/docs/job-specification/group#max-client-disconnect
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.5.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.5.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..01ab823304
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.5.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.5.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..fe073731ed
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,191 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.5.x/content/docs/configuration/tls.mdx b/content/nomad/v1.5.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..b63b92f84b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to enforce
+secure cluster communication between servers, clients, and between. Note that in
+most cases, this is mutual TLS (mTLS) where both ends of the connection
+authenticate each other. The Nomad documentation will typically use "TLS" to
+refer to this communication except when it is potentially ambiguous between TLS
+and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.5.x/content/docs/configuration/ui.mdx b/content/nomad/v1.5.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..312e9e9798
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI will default to a black background. HEX values  
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI will default to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.5.x/content/docs/configuration/vault.mdx b/content/nomad/v1.5.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..dad303682c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.5.x/content/docs/devices/index.mdx b/content/nomad/v1.5.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.5.x/content/docs/drivers/docker.mdx b/content/nomad/v1.5.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..c04edabd36
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1230 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) One of `"hyper-v"`, `"process"`, or `"default"`
+  (which is the same as `process`). Enables [Windows isolation][] modes.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group `network.mode = "bridge"` you should not set the Docker config
+  `network_mode`, or the container will be unable to reach other containers in
+  the task group. This will also prevent [Connect]-enabled tasks from reaching
+  the Envoy sidecar proxy. You must also set any DNS options in the `network.dns`
+  block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `SSL` - (Optional) If this is set to true, Nomad uses SSL to talk to the
+  repository. The default value is `true`. **Deprecated as of 0.5.3**
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+_New in Nomad 0.6._
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`. The image will only be pulled from
+  the container registry if its tag is `latest` or the image doesn't yet exist locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.5.x/content/docs/drivers/exec.mdx b/content/nomad/v1.5.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..02efcff25c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,280 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver is used to run binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot is populated with data in the following directories from the host
+machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.5.x/content/docs/drivers/index.mdx b/content/nomad/v1.5.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.5.x/content/docs/drivers/java.mdx b/content/nomad/v1.5.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..3c1050c668
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/java.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.5.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.5.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..4a86628ff0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.5.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.5.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..b8b2db68e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.5.x/content/docs/ecosystem.mdx b/content/nomad/v1.5.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.5.x/content/docs/enterprise/index.mdx b/content/nomad/v1.5.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..34fc5391a4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,180 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[Sentinel Policies Guide]: /nomad/tutorials/governance-and-policy/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/enterprise/sentinel
diff --git a/content/nomad/v1.5.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.5.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..d0986d8651
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.1.0+ent.
+Nomad Enterprise automatically load Nomad licenses when a Nomad server agent starts using Nomad Enterprise.
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.1.0, the license enablement process is different.
+
+HashiCorp Enterprise servers will no longer start without a license. When the
+server instance initializes the license watcher, the server reads from either an
+environment variable or file. If the license is missing, invalid, or terminated,
+the server will immediately exit. This check is part of the server boot-up
+process.
+
+In previous versions of HashiCorp enterprise products, one server could
+distribute a license to other servers via the Raft protocol. This will no longer
+work since each server must be able to find a valid license during the startup
+process.
+
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about the license changes introduced in Nomad Enterprise v1.1.0
+
+- [v1.1.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect Nomad or older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.1.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you follow the steps in the [upgrade guide](/nomad/docs/upgrade/upgrade-specific#enterprise-licenses), but have misconfigured the licensing steps, the server instances will stop during boot-up sequence.
+
+If you do not check cluster health after adding new servers, and verify that the new servers have joined properly, then you may accidentally take down old servers without replacing them.
+
+If you are using a trial license in production, this could cause issues as the cluster will fail to start once the trial expires.
+
+If you have built automation around `nomad license put`, this command will fail as it has been removed from Nomad v1.1.0+.
+
+## Q: What are some other gotchas?
+
+You might not have access to your organization's Nomad license.
+The  6-hour temporary license window is now removed, and a license is required for proper boot-up.
+Running `nomad agent -dev` without a license will fail.
+
+
+## Q: How can a user get their existing license to put on disk for an upgrade?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires or terminates?
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. The grace
+period is defined as the time between license expiration and license
+termination. (This is typically very short for evaluation licenses, and much longer
+for non-evaluation licenses.) Customers must provide a valid license before the
+grace period expires.
+
+When the license terminates, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write operations
+will return an error. Note that if the server is restarted with a terminated
+license, it will immediately stop.
+
+Clients are unaffected by terminated licenses because clients do not read the
+license.
+
+## Q: Will on-prem binaries with "baked-in" licenses work?
+
+There is no impact to baked-in licensed binaries.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.1.0 to an earlier version?
+
+Nomad cannot safely be rolled back to an earlier version.
+This is not a supported operation due to the Nomad state store not having forward compatibility. The end result could be a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
diff --git a/content/nomad/v1.5.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.5.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..8c6162a1b3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have its own license. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster. See issue [gh-9958]
+for more details.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time and a termination time. You
+can read the license on a server with the `nomad license get` command:
+
+```
+$ nomad license get
+Product        = nomad
+License Status = valid
+License ID     = eaaecbd5-b598-4fa4-b649-bb234bf49fa3
+Customer ID    = ae94bdd0-39bf-4c58-bf80-8a9468b0467c
+Issued At      = 2021-03-29 14:47:29.024191 -0400 EDT
+Expires At     = 2021-03-29 20:47:29.024191 -0400 EDT
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+        Dynamic Application Sizing
+```
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers will
+periodically log a warning message about the approaching expiration. Below shows
+log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license reaches the termination time, enterprise functionality will
+become limited. Only read operations on enterprise endpoints will be supported,
+and write operations will return an error.
+
+Note that if the server is restarted with a terminated license, it will
+immediately stop.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[gh-9958]: https://github.com/hashicorp/nomad/issues/9958
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.5.x/content/docs/enterprise/sentinel.mdx b/content/nomad/v1.5.x/content/docs/enterprise/sentinel.mdx
new file mode 100644
index 0000000000..6ca332992a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/enterprise/sentinel.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Sentinel Policy Reference
+description: >-
+  Learn about Nomad Sentinel Policy Objects
+---
+
+## Sentinel
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+See the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`
+subcommands][]
+
+### Sentinel Policies
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  will always be non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-nomad-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+### Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+
+### Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+### Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+[Nomad Sentinel Tutorial]: /nomad/tutorials/governance-and-policy/sentinel
+[`nomad sentinel` sub-commands]: /nomad/docs/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L12991-L13020
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L5306-L5338
diff --git a/content/nomad/v1.5.x/content/docs/faq.mdx b/content/nomad/v1.5.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..a9c683b8b6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.5.x/content/docs/index.mdx b/content/nomad/v1.5.x/content/docs/index.mdx
new file mode 100644
index 0000000000..3296277979
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [Getting Started collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.5.x/content/docs/install/index.mdx b/content/nomad/v1.5.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..7f19d8556e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/install/index.mdx
@@ -0,0 +1,437 @@
+---
+layout: docs
+page_title: Installing Nomad
+description: Learn how to install Nomad.
+---
+
+# Installing Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see the
+[Quickstart](/nomad/docs/install/quickstart) for options to get started with Nomad.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](/nomad/downloads) and
+run it on your machine locally. You can also verify the binary using the
+available SHA-256 sums. After downloading Nomad, unzip the package. Make sure
+that the `nomad` binary is available on your `PATH` before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Homebrew on macOS" group="homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+~> **NOTE:** This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+
+</Tab>
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+~> **NOTE:** Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Linux Packages" group="linux">
+
+HashiCorp officially maintains and signs packages for the following Linux
+distributions.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+</Tabs>
+
+-> **TIP:** Now that you have added the HashiCorp repository, you can install
+[Consul](/consul/tutorials) and
+[Vault](/vault/tutorials) with the same command.
+
+</Tab>
+</Tabs>
+
+## Post-installation steps
+
+These steps are considered optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+<Tabs>
+<Tab heading="Linux Packages">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+
+<h3>Verify cgroup controllers</h3>
+
+On Linux, Nomad uses cgroups to control resource usage of tasks. If one or more
+required cgroups are unavailable, Nomad will disable resource controls that
+require cgroups entirely. With cgroups v2, you can verify that you have all
+required controllers as follows:
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+See the documentation on [cgroup controller requirements][] for more details.
+
+</Tab>
+
+<Tab heading="macOS">
+<h3>Add the Nomad binary to your system path</h3>
+
+Permanently add a new location to your path by editing your shell's settings
+file (usually called something like `~/.bashrc`, where the part of the filename
+after the `.` and before `rc` is the name of your shell). In that file you
+should see a line that starts with `export PATH=`, followed by a
+colon-separated list of locations. Add the location of the Nomad binary to that
+list and save the file. Then reload your shell's configuration with the command
+`source ~/.bashrc`, replacing `bash` with the name of your shell.
+</Tab>
+
+<Tab heading="Windows">
+
+<h3>Add the Nomad binary to your system path</h3>
+
+Add a location to your path via the GUI by navigating to `Environment
+Variables` in your system settings, and looking for the variable called `PATH`.
+You should see a semicolon-separated list of locations. Add the Nomad binary's
+location to that list and then launch a new console window.
+</Tab>
+</Tabs>
+</Tab>
+
+<Tab heading="Homebrew on macOS" group="homebrew">
+No additional steps necessary after installing Nomad using Homebrew.
+</Tab>
+
+<Tab heading="Chocolatey on Windows" group="chocolatey">
+No additional steps necessary after installing Nomad using Chocolatey.
+</Tab>
+
+<Tab heading="Linux" group="linux">
+
+Note that if you are running Nomad on Linux, you'll need to run client agents as
+root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+<h3>Install CNI plugins</h3>
+
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. All Linux Nomad client nodes using network namespaces must have
+CNI plugins installed.
+
+The following commands install the CNI reference plugins.
+
+```shell-session
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows.
+
+```shell-session
+$ echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables && \
+  echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
+
+<h3>Verify cgroup controllers</h3>
+
+On Linux, Nomad uses cgroups to control resource usage of tasks. If one or more
+required cgroups are unavailable, Nomad will disable resource controls that
+require cgroups entirely. With cgroups v2, you can verify that you have all
+required controllers as follows:
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+See the documentation on [cgroup controller requirements][] for more details.
+
+</Tab>
+</Tabs>
+
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.5.x/content/docs/install/production/index.mdx b/content/nomad/v1.5.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..2d8e7350d4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.5.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.5.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..c6a551e75b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,264 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publically routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+Nomad's task group networks and Consul Connect integration use bridge networking and iptables to send traffic between containers. The Linux kernel bridge module has three "tunables" that control whether traffic crossing the bridge are processed by iptables. Some operating systems (RedHat, CentOS, and Fedora in particular) configure these tunables to optimize for VM workloads where iptables rules might not be correctly configured for guest traffic.
+
+These tunables can be set to allow iptables processing for the bridge network as follows:
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in that directory.
+
+```text
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Cgroup Controllers
+
+On Linux, Nomad uses cgroups to control access to resources like CPU and
+memory. Nomad can support both [cgroups v2][] and the legacy [cgroups
+v1][]. When Nomad clients start, they will determine the available cgroup
+controllers and include the attribute `os.cgroups.version` in their
+fingerprint.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. You will most often see
+missing controllers on platforms used outside of datacenters, such as Raspberry
+Pi or similar hobbyist computers.
+
+On cgroups v2, you can verify that you have all required controllers as follows:
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, you can look for this same list of required controllers as
+directories under the directory `/sys/fs/cgroup`.
+
+To enable missing cgroups, add the appropriate boot command line arguments. For
+example, to enable the `cpuset` cgroup, you'll need to add `cgroup_cpuset=1
+cgroup_enable=cpuset`. These arguments should be added wherever specified by
+your bootloader.
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrat
+[cgroups v1]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html
+[cgroups v2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
diff --git a/content/nomad/v1.5.x/content/docs/install/quickstart.mdx b/content/nomad/v1.5.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..fb04b6eb39
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via guides containing embedded interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.5.x/content/docs/install/windows-service.mdx b/content/nomad/v1.5.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.5.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.5.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..b9ced018d9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,406 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have CNI plugins installed.
+
+The following commands install CNI plugins:
+
+```shell-session
+curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+sudo mkdir -p /opt/cni/bin
+sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Ensure the your Linux operating system distribution has been configured to allow
+container traffic through the bridge network to be routed via iptables. These
+tunables can be set as follows:
+
+```shell-session
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-arptables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-ip6tables
+echo 1 | sudo tee /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file including the
+following to `/etc/sysctl.d/` or remove the file your Linux distribution puts in
+that directory.
+
+```
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
diff --git a/content/nomad/v1.5.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.5.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..61414160ee
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/nomad/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](/nomad/tutorials/manage-clusters/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` block](/nomad/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul Template,
+please see the [`template` job specification documentation](/nomad/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+
+[consul]: https://www.consul.io/ "Consul by HashiCorp"
+
+[consul_acls]: /consul/docs/security/acl
+
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+
+[consul_group_namespace]: /nomad/docs/job-specification/group#namespace
+
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
diff --git a/content/nomad/v1.5.x/content/docs/integrations/index.mdx b/content/nomad/v1.5.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.5.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.5.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..9fb9016bec
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,475 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` block of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To submit this job, a token that has the `access-kv` policy in the `engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /nomad/docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /nomad/docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /nomad/docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.5.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.5.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..b1cd31ebfa
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,284 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment variables
+set for the Nomad client. Inheritence of environment variables can be managed through the [`artifact.set_environment_variables`][client_artifact]
+client configuration.
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.5.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/check.mdx b/content/nomad/v1.5.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..1108a420bb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_skip_verify` `(bool: false)` - Skip verifying TLS certificates for HTTPS
+  checks. Only supported in the Consul service provider.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.5.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.5.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.5.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..565adf7c87
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,322 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-network-speed-and-node-class 'Nomad Custom Metadata, Network Speed, and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.5.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..d1ada0e150
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                      = "csi-hostpath"
+  type                    = "monolith"
+  mount_dir               = "/csi"
+  stage_publish__base_dir = "/local/csi"
+  health_timeout          = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/device.mdx b/content/nomad/v1.5.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..0748bf8ec4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.5.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..482fe10047
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+  to
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Examples
+
+The following examples only show the `dispatch_payload` blocks. Remember that the
+`dispatch_payload` block is only valid in the placements listed above.
+
+### Write Payload to a File
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/env.mdx b/content/nomad/v1.5.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.5.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..dca9fc6523
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.5.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..e709e4c464
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.5.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..16889f4114
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,666 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect Gateways](/consul/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or `grpc`), preconfiguring a [service-default] in Consul to
+  set the [Protocol](/consul/docs/connect/config-entries/service-defaults#protocol)
+  of the service to the desired protocol is mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#service-parameters-1
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[service]: /nomad/docs/job-specification/gateway#service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/group.mdx b/content/nomad/v1.5.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..a64fe83225
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,360 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost". These
+allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' reschedule policy
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements and keep
+the one with the best node score. If the `max_client_disconnect` duration
+expires before the client reconnects, the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+~> **Note:** The `max_client_disconnect` feature is only supported on Nomad
+version 1.3.0 and above. If you run a job with `max_client_disconnect` on servers
+where some servers are not upgraded to 1.3.0, the `max_client_disconnect`
+flag will be _ignored_. Deploying a job with `max_client_disconnect` to a
+`datacenter` of Nomad clients where all clients are not 1.3.0 or above is unsupported.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/group#consul-parameters
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..91ea784340
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..734fbf6589
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..6cf8bcbd89
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..24e760c922
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..667174c8a1
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..ab2f14ad6d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..fb820cf5b8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/runtime/environment
+[expression]: /nomad/docs/job-specification/hcl2/expressions
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.5.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..8e0c162d9d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: identity Block - Job Specification
+description: |-
+  The "identity" block allows tasks to use their Nomad Workload Identity via an
+  environment variable or file.
+---
+
+# `identity` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. By default Nomad will create an identity for all
+workloads, but it is *not* exposed to a task.
+
+The following will expose the Workload Identity as an environment variable and
+file to the task:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env  = true
+        file = true
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## `identity` Parameters
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/index.mdx b/content/nomad/v1.5.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..dc0478fb08
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/job.mdx b/content/nomad/v1.5.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..8b0b5b5985
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,263 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  datacenters = ["default"]
+
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.5.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.5.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..bb361fd493
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with reasonable defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/drivers/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.5.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..6f32810932
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## `meta` Usage Examples
+
+### Templates
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.5.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.5.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..53f5ee4b4d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,287 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/network.mdx b/content/nomad/v1.5.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..cfd6b6094f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,334 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is neccessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.5.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..bf914761dc
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.5.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..e91f04b915
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.5.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..9b86faf3c2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and
+  passed directly to Consul. See [Consul Connect documentation](/consul/docs/connect/proxies/envoy#dynamic-configuration)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.5.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.5.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..3e2be15ac3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad 1.1. lets job authors set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The new max limit attribute is currently supported by the official `docker`,
+`exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory Oversubscription in the scheduler
+configuration](/nomad/api-docs/operator/scheduler#update-scheduler-configuration). Enterprise customers can use [Resource
+Quotas](/nomad/tutorials/governance-and-policy/quotas) to limit the memory
+oversubscription.
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/drivers/docker#cpu
+[exec_cpu]: /nomad/docs/drivers/exec#cpu
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.5.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..683254e7fd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,170 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 2
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval = "30m"
+  attempts = 5
+  delay    = "15s"
+  mode     = "fail"
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts = 3
+    delay    = "15s"
+    interval = "24h"
+    mode     = "fail"
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval = "30m"
+    attempts = 2
+    delay    = "15s"
+    mode     = "fail"
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.5.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/service.mdx b/content/nomad/v1.5.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..22d5cf6d3f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,519 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.5.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..584ef6cf02
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       "test-key" = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.5.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..df7508f636
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.5.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..6fc0455de3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/task.mdx b/content/nomad/v1.5.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..40006df9aa
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,231 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/template.mdx b/content/nomad/v1.5.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..b53006c364
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,837 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad Integration
+
+### Nomad Services
+
+~> Nomad Services are new in Nomad 1.3.
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+~> Simple load balancing with Nomad Services is new in Nomad 1.3.2.
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault
+PKI role.<br /><br /> Failure to do so will cause the template to frequently
+render a new certificate, approximately every minute. This creates a significant
+number of certificates to be expired in Vault and could ultimately lead to Vault
+performance impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/update.mdx b/content/nomad/v1.5.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..3e1243a165
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.5.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..261bbb4ca5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/nomad/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](/consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.5.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..20fe3ab27c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.5.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..58ec2bd352
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.5.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.5.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..545379bd62
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.5.x/content/docs/networking/cni.mdx b/content/nomad/v1.5.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..d46bbaeb7e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/networking/cni.mdx
@@ -0,0 +1,218 @@
+---
+layout: docs
+page_title: CNI
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Container Network Interface (CNI)
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+The CNI specification defines a network configuration format for administrators.
+It contains directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by Nomad
+and transformed into arguments for the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Using CNI networks with Nomad jobs
+
+To specify that a job should use a CNI network, set the task group's
+network [`mode`][] attribute to the value `cni/<your_cni_config_name>`.
+Nomad will then schedule the workload on client nodes that have fingerprinted a
+CNI configuration with the given name. For example, to use the configuration
+named `mynet`, you should set the task group's network mode to `cni/mynet`.
+Nodes that have a network configuration defining a network named `mynet` in
+their [`cni_config_dir`][] will be eligible to run the workload.
+
+## Nomad's `bridge` configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the [loopback][], [bridge][], [firewall][],
+and [portmap][] CNI plugins configured together to create Nomad's bridge
+network.
+
+The following is the configuration template Nomad uses when setting up these
+networks with the template placeholders replaced with the default configuration
+values for [`bridge_network_name`][], [`bridge_network_subnet`][], and an
+internal constant that provides the value for `iptablesAdminChainName`. This is
+a convenient jumping off point to discuss a worked example.
+
+```json
+{
+  "cniVersion": "0.4.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+<!-- Source: https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1 -->
+[![Visual example of Nomad bridge network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+For a more thorough understanding of this configuration, consider each CNI
+plugin's configuration in turn.
+
+### loopback
+
+The `loopback` plugin sets the default local interface, `lo0`, created inside
+the bridge network's network namespace to **UP**. This allows workload running
+inside the namespace to bind to a namespace-specific loopback interface.
+
+### bridge
+
+The `bridge` plugin creates a bridge (virtual switch) named `nomad` that resides
+in the host network namespace. Because this bridge is intended to provide
+network connectivity to allocations, it's configured to be a gateway by setting
+`isGateway` to `true`. This tells the plugin to assign an IP address to the
+bridge interface
+
+The bridge plugin connects allocations (on the same host) into a bridge (virtual
+switch) that resides in the host network namespace. By default Nomad creates a
+single bridge for each client. Since Nomad's bridge network is designed to
+provide network connectivity to the allocations, it configures the bridge
+interface to be a gateway for outgoing traffic by providing it with an address
+using an `ipam` configuration. The default configuration creates a host-local
+address for the host side of the bridge in the `172.26.64.0/20` subnet at
+`172.26.64.1`. When associating allocations to the bridge, it creates addresses
+for the allocations from that same subnet using the host-local plugin. The
+configuration also specifies a default route for the allocations of the
+host-side bridge address.
+
+### firewall
+
+The firewall plugin creates firewall rules to allow traffic to/from the
+allocation's IP address via the host network. Nomad uses the iptables backend
+for the firewall plugin. This configuration creates two new iptables chains,
+`CNI-FORWARD` and `NOMAD-ADMIN`, in the filter table and add rules that allow
+the given interface to send/receive traffic.
+
+The firewall creates an admin chain using the name provided in the
+`iptablesAdminChainName` attribute. For this case, it's called `NOMAD-ADMIN`.
+The admin chain is a user-controlled chain for custom rules that run before
+rules managed by the firewall plugin. The firewall plugin does not add, delete,
+or modify rules in the admin chain.
+
+A new chain, `CNI-FORWARD` is added to the `FORWARD` chain. `CNI-FORWARD` is
+the chain where rules will be added when allocations are created and from where
+rules will be removed when those allocations stop. The `CNI-FORWARD` chain
+first sends all traffic to `NOMAD-ADMIN` chain.
+
+You can use the following command to list the iptables rules present in each
+chain.
+
+```shell-session
+$ sudo iptables -L
+```
+
+### portmap
+
+Nomad needs to be able to map specific ports from the host to tasks running in
+the allocation namespace. The `portmap` plugin forwards traffic from one or more
+ports on the host to the allocation using network address translation (NAT)
+rules.
+
+The plugin sets up two sequences of chains and rules:
+
+- One “primary” `DNAT` (destination NAT) sequence to rewrite the destination.
+- One `SNAT` (source NAT) sequence that will masquerade traffic as needed.
+
+You can use the following command to list the iptables rules in the NAT table.
+
+```shell-session
+$ sudo iptables -t nat -L
+```
+
+## Create your own
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode. When making your own bridge network
+based on this template, ensure that you change the `iptablesAdminChainName` to
+a unique value for your configuration.
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`bridge_network_name`]: /nomad/docs/configuration/client#bridge_network_name
+[`bridge_network_subnet`]: /nomad/docs/configuration/client#bridge_network_subnet
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[`mode`]: /nomad/docs/job-specification/network#mode
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[loopback]: https://github.com/containernetworking/plugins#main-interface-creating
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.5.x/content/docs/networking/index.mdx b/content/nomad/v1.5.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..ee9db82d48
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/networking/index.mdx
@@ -0,0 +1,331 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Learn about Nomad's networking internals and how it compares with other
+  tools.
+---
+
+# Networking
+
+Nomad is a workload orchestrator and so it focuses on the scheduling aspects of
+a deployment, touching areas such as networking as little as possible.
+
+**Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_**. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+This can be confusing at first since it is quite different from what you may
+be used to from other tools. This section explains how networking works in
+Nomad, some of the different patterns and configurations you are likely to find
+and use, and how Nomad differs from other tools in this aspect.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an [allocation][], which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the [`network`][jobspec_network] block. At its
+simplest configuration, a `network` block can be defined as:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between [`min_dynamic_port`][] and
+[`max_dynamic_port`][] that has not been allocated yet and creates a port
+mapping from the host network interface to the allocation.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Port Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+The selected port number can be accessed by tasks using the
+[`NOMAD_PORT_<label>`][runtime_environment] environment variable to bind and
+expose the workload at the client's IP address and the given port.
+
+The specific configuration process depends on what you are running, but it is
+usually done using a configuration file rendered from a [`template`][] or
+passed directly via command line arguments:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+It is also possible to request a specific port number, instead of a random one,
+by setting a [`static`][] value for the `port`. **This should only be used by
+specialized workloads**, such as load balancers and system jobs, since it can
+be hard to manage them manually to avoid scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can
+access it directly using the client's IP and port, but first they need to find
+these values. This process is called [service discovery][].
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network [`mode`][network_mode] called [`bridge`][]. A
+bridge network acts like a virtual network switch allowing processes connected
+to the bridge to reach each other while isolating them from others.
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in [`bridge_network_name`][]) using the
+[`bridge` CNI plugin][cni_bridge] if one doesn't exist yet. Before using this
+mode you must first [install the CNI plugins][cni_install] into your clients.
+By default a single bridge is created in each Nomad client.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random
+ports from the host to specific port numbers inside the allocation that are
+expected by the tasks.
+
+For example, an HTTP server that listens on port `3000` by default can be
+configured with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only.
+
+Bridge networking is at the core of [service mesh][] and a requirement when
+using [Consul Service Mesh][consul_service_mesh].
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network][docker_bridge], network namespaces, and [`iptable`
+rules][docker_iptables]. Tasks using the `docker` task driver connect to the
+Docker bridge instead of using the one created by Nomad and, by default, each
+container runs in its own Docker managed network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`][] to initialize a Docker network namespace
+that is shared by all tasks in the allocation to allow them to communicate with
+each other.
+
+The Docker task driver has its own task-level
+[`network_mode`][docker_network_mode] configuration. Its default value depends
+on the group-level [`network.mode`][network_mode] configuration.
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+   `network.mode` configuration and generate unexpected results. If you set the
+   group `network.mode = "bridge"` you should not set the Docker config
+   `network_mode`.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+The diagram below illustrates what happens when a Docker task is configured
+incorrectly.
+
+<!-- Source: https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link -->
+[![Nomad Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container
+to establish a shared network namespace for all tasks, but setting the
+task-level `network_mode` to `bridge` places the task in a different namespace.
+This prevents, for example, a task from communicating with its sidecar proxy in
+a [service mesh][] deployment.
+
+Refer to the [`network_mode`][docker_network_mode] documentation and the
+[Networking][docker_networking] section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ][faq_docker] for more details.
+
+## Comparing with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS services][docker_dns] and a
+load balancer that is transparent to user. When running in Swarm mode, Docker
+Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the [`Service`][k8s_service] abstraction that can be used
+to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service][k8s_dns] which is an add-on that runs in all nodes. Along with this
+service, each node also runs a [`kube-proxy`][k8s_kubeproxy] instance to
+distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface][consul_dns] and configuring your clients with [DNS
+forwarding][consul_dns_forwarding], and deploying a [load
+balancer][nomad_load_balancer].
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical
+IP addresses to virtual ones. In case of Docker Compose in Swarm mode an
+[`overlay`][docker_overlay] is also required to enable traffic across multiple
+hosts. This allows multiple containers running the same service to listen on
+the same port number.
+
+In Nomad, allocations use the IP address of the client they are running and are
+assigned random port numbers and so Nomad service discovery with DNS uses
+[`SRV` records][dns_srv] instead of `A` or `AAA` records.
+
+## Next topics
+
+- [Service Discovery][service discovery]
+- [Service Mesh][service mesh]
+- [Container Network Interface][cni]
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada 2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
+
+[`bridge_network_name`]: /nomad/docs/configuration/client#bridge_network_name
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[`infra_image`]: /nomad/docs/drivers/docker#infra_image
+[`max_dynamic_port`]: /nomad/docs/configuration/client#max_dynamic_port
+[`min_dynamic_port`]: /nomad/docs/configuration/client#min_dynamic_port
+[`static`]: /nomad/docs/job-specification/network#static
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[cni]: /nomad/docs/networking/cni
+[cni_bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[cni_install]: /nomad/tutorials/get-started/get-started-install#post-installation-steps
+[consul_dns]: /consul/docs/discovery/dns
+[consul_dns_forwarding]: /consul/tutorials/networking/dns-forwarding
+[consul_service_mesh]: /nomad/docs/integrations/consul-connect
+[dns_srv]: https://en.wikipedia.org/wiki/SRV_record
+[docker_bridge]: https://docs.docker.com/network/bridge/
+[docker_compose]: https://docs.docker.com/compose/
+[docker_dns]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[docker_iptables]: https://docs.docker.com/network/iptables/
+[docker_network_mode]: /nomad/docs/drivers/docker#network_mode
+[docker_networking]: /nomad/docs/drivers/docker#networking
+[docker_overlay]: https://docs.docker.com/network/overlay/
+[docker_swarm]: https://docs.docker.com/engine/swarm/
+[faq_docker]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[jobspec_network]: /nomad/docs/job-specification/network
+[k8s_dns]: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
+[k8s_ingress]: https://kubernetes.io/docs/concepts/services-networking/ingress/
+[k8s_kubeproxy]: https://kubernetes.io/docs/concepts/overview/components/#kube-proxy
+[k8s_service]: https://kubernetes.io/docs/concepts/services-networking/service/
+[network_mode]: /nomad/docs/job-specification/network#mode
+[nomad_load_balancer]: /nomad/tutorials/load-balancing
+[runtime_environment]: /nomad/docs/runtime/environment#network-related-variables
+[service discovery]: /nomad/docs/networking/service-discovery
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.5.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.5.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..d0e726a85d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Learn about how service discovery works in Nomad to connect workloads.
+---
+
+# Service discovery
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/discovery/dns
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.5.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.5.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2828748c9f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Learn about how service mesh works in Nomad to securely connect and isolate
+  your workloads.
+---
+
+# Service mesh
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.5.x/content/docs/operations/index.mdx b/content/nomad/v1.5.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.5.x/content/docs/operations/key-management.mdx b/content/nomad/v1.5.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..2f8b92165f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers store key metadata in raft, but
+the encryption key material is stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Replication
+
+When a leader is elected, it creates the keyring if it does not already
+exist. When a key is added, the metadata will be replicated via raft. Each
+server runs a key replication process that watches for changes to the state
+store and will fetch the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election.
+
+## Restoring the Keyring from Backup
+
+Key material is never stored in raft. This prevents an attacker with a backup of
+the state store from getting access to encrypted variables. It also allows the
+HashiCorp engineering and support organization to safely handle cluster
+snapshots you might provide without exposing any of your keys or variables.
+
+However, this means that to restore a cluster from snapshot you need to also
+provide the keystore directory with the `.nks.json` key files on at least one
+server. The `.nks.json` key files are unique per server, but only one server's
+key files are needed to recover the cluster. Operators should include these
+files as part of your organization's backup and recovery strategy for the
+cluster.
+
+If you are recovering a Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
diff --git a/content/nomad/v1.5.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.5.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..3d36b5b5b9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,497 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                  | Description                                                                         | Unit       | Type  | Labels                                                                                |
+| --------------------------------------- | ----------------------------------------------------------------------------------- | ---------- | ----- | ------------------------------------------------------------------------------------- |
+| `nomad.client.allocated.cpu`            | Total amount of CPU shares the scheduler has allocated to tasks                     | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`         | Total amount of memory the scheduler has allocated to tasks                         | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`           | Total amount of disk space the scheduler has allocated to tasks                     | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`      | Number of allocations waiting for previous versions to exit                         | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`    | Number of allocations migrating data from previous versions (see [`sticky`][sticky])| Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`      | Number of allocations pending (received by the client but not yet running)          | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`      | Number of allocations running                                                       | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`        | Number of allocations starting                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`     | Number of allocations terminal                                                      | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`        | Number of allocations OOM killed                                                    | Integer    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`            | CPU utilization in idle state                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`          | CPU utilization in system space                                                     | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total`           | Total CPU utilization                                                               | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`            | CPU utilization in user space                                                       | Percentage | Gauge | cpu, datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`      | Amount of space which is available                                                  | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent` | Disk space consumed by the inodes                                                   | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`           | Total size of the device                                                            | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`   | Percentage of disk space used                                                       | Percentage | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`           | Amount of space which has been used                                                 | Bytes      | Gauge | datacenter, disk, host, node_class, node_id, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`    | Total amount of memory available to processes which includes free and cached memory | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`         | Amount of memory which is free                                                      | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`        | Total amount of physical memory on the node                                         | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`         | Amount of memory used by processes                                                  | Bytes      | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`          | Total amount of CPU shares free for the scheduler to allocate to tasks              | Mhz        | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`         | Total amount of disk space free for the scheduler to allocate to tasks              | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`       | Total amount of memory free for the scheduler to allocate to tasks                  | Megabytes  | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                   | Uptime of the host running the Nomad client                                         | Seconds    | Gauge | datacenter, host, node_class, node_id, node_scheduling_eligibility, node_status       |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`         | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://nomadproject.io/s/port-plan-failure
diff --git a/content/nomad/v1.5.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.5.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..6dd813a86c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://www.nomadproject.io/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.5.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.5.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..474eed327e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,188 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+By default, any stop signal to an agent (interrupt or terminate) will cause the
+agent to exit after ensuring its internal state is committed to disk as
+needed. You can configuration additonal behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when `leave_on_interrupt` or `leave_on_terminate` are set the
+server will notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there will be a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, the [`server
+force-leave` command][] should be used to eject it from the consensus peer set.
+
+For clients, when `leave_on_interrupt` or `leave_on_terminate` are set and the
+client is configured with [`drain_on_shutdown`][], the client will drain its
+workloads before shutting down.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.5.x/content/docs/operations/stateful-workloads.mdx b/content/nomad/v1.5.x/content/docs/operations/stateful-workloads.mdx
new file mode 100644
index 0000000000..d8ecf7db08
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/operations/stateful-workloads.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Portworx or Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. More information can be found on the CSI
+concepts [documentation page](/nomad/docs/concepts/plugins/csi).
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+Host volumes mount paths from the host (the Nomad client) into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+backed by a distributed networked storage such as GlusterFS, or a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore
+you can use host volumes for both local somewhat persistent storage and for
+highly persistent networked storage.
+
+Because you need to declare host volumes in the Nomad agent's configuration
+file, you must restart the Nomad client to reconfigure them. This makes host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/concepts/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add/update/remove host volumes to make them available for
+consumption by Nomad Operators. Or, with networked host volumes, a Storage
+Administrator will need to provision the volumes and make them available to the
+Nomad clients. A System Administrator will then mount them on the Nomad clients.
+
+Host volumes backed by local storage help persist data that is not critical, for
+example an on-disk cache that can be rebuilt if needed. When backed by networked
+storage such as NFS/CIFS-mounted volumes or distributed storage via
+GlusterFS/Ceph, host volumes provide a quick option to consume highly available
+and reliable storage.
+
+Refer to the [Stateful workloads with Nomad host
+volumes](/nomad/tutorials/stateful-workloads/stateful-workloads-host-volumes)
+tutorial to learn more about using host volumes with Nomad.
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/tutorials/integrate-nomad/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/concepts/plugins/csi)
+- [Nomad CSI
+  tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [Portworx on
+  Nomad](https://docs.portworx.com/portworx-enterprise/install-portworx/install-with-other/nomad#operate-and-utilize-portworx-on-nomad)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..7a360b4021
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,431 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "write"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When an action is checked against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, the matching rule with the greatest number of matched characters will be
+chosen.
+
+For example the following policy will evaluate to deny for `production-web`,
+because it is 9 characters different from the `"*-web"` rule, but 13 characters
+different from the `"*"` rule.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..5422693c69
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**. Note that, like the rest of the volume specification, 
+  this block is declarative, and an update replaces it in its entirety, therefore 
+  all parameters need to be specified.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), [`clone_id`](#clone_id),
+[`capacity_min`](#capacity_min), or [`capacity_max`](#capacity_max) fields on
+**volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.5.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.5.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.5.x/content/docs/partnerships.mdx b/content/nomad/v1.5.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..b8c95e0b93
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. See the [Introduction](/nomad/intro) page for a full description of the current features. The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.5.x/content/docs/runtime/environment.mdx b/content/nomad/v1.5.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..a765f8a3b0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Prior to Nomad 0.5.5 the key was
+uppercased and since then both the original case and an uppercased version are
+injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.5.x/content/docs/runtime/index.mdx b/content/nomad/v1.5.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..86b05c6076
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details Nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.5.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.5.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..ac17e42402
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,200 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/drivers/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/drivers/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+| ----------------------| ------------------------------------------- | -------------------------------------- |
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.5.x/content/docs/schedulers.mdx b/content/nomad/v1.5.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..b403fcf14b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/schedulers.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count` 
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.5.x/content/docs/upgrade/index.mdx b/content/nomad/v1.5.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..0342ea54d4
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,246 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+The process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`raft.peers`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `raft.peers` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.5.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.5.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..08ad4e1023
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1777 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.5.11
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.5.11 change the behavior of the [`distinct_hosts`][]
+constraint such that namespaces are taken into account when choosing feasible
+clients for allocation placement. The previous, less-expected behavior would
+cause **any** job with the same name running on a client to cause that node to
+be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider upgrading to Nomad 1.6 and using [node pools] and constrain the jobs
+with a [`distinct_property`][] constraint over `${node.pool}`.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide][hard_guide]
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock] capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`][artifact_params]
+and [`headers`][artifact_params] fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`][artifact_env].
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`][artifact_fs_isolation].
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`][decompression_size_limit] and
+[`decompression_file_count_limit`][decompression_file_count_limit].
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`] configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`distinct_hosts`]: /nomad/docs/job-specification/constraint#distinct_hosts
+[`distinct_property`]: /nomad/docs/job-specification/constraint#distinct_property
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[`log_file`]: /nomad/docs/configuration#log_file
+[`rejoin_after_leave`]: /nomad/docs/configuration/server#rejoin_after_leave
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[artifact_params]: /nomad/docs/job-specification/artifact#artifact-parameters
+[artifacts]: /nomad/docs/job-specification/artifact
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[cores]: /nomad/docs/job-specification/resources#cores
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[enterprise licensing]: /nomad/docs/enterprise/license
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
+[hcl2]: https://github.com/hashicorp/hcl2
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[migrate]: /nomad/docs/job-specification/migrate
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[nvidia]: /nomad/plugins/devices/nvidia
+[pki]: /vault/docs/secrets/pki
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
diff --git a/content/nomad/v1.5.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.5.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..4dd4b333dd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,116 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.5.x/content/intro/index.mdx b/content/nomad/v1.5.x/content/intro/index.mdx
new file mode 100644
index 0000000000..44757a5182
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.5.x/content/intro/use-cases.mdx b/content/nomad/v1.5.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..7082888c5d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.5.x/content/intro/vs/ecs.mdx b/content/nomad/v1.5.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.5.x/content/intro/vs/index.mdx b/content/nomad/v1.5.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.5.x/content/intro/vs/mesos.mdx b/content/nomad/v1.5.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.5.x/content/intro/vs/terraform.mdx b/content/nomad/v1.5.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.5.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.5.x/content/partials/envvars.mdx b/content/nomad/v1.5.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..d79b69159a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/partials/envvars.mdx
@@ -0,0 +1,68 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                     |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                       |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                       |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                 |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                           |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                   |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                       |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                          |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index. |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                     |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                    |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                   |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                      |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                            |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                   |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                     |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                    |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                       |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata.                                                                    |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                       |
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/runtime/environment#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/integrations/vault-integration
diff --git a/content/nomad/v1.5.x/content/partials/general_options.mdx b/content/nomad/v1.5.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..bb9ece3878
--- /dev/null
+++ b/content/nomad/v1.5.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, job and alloc subcommands query all namespaces authorized to
+  user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.5.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.5.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.5.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.5.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.5.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.5.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.5.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.5.x/content/plugins/devices/index.mdx b/content/nomad/v1.5.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.5.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.5.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..a73e98adb7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..5aa129c9cd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..6620f08eec
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[rkt]: /nomad/plugins/drivers/community/rkt
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..3a0a46f932
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionaly, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..0bc5c66b99
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..dfbb3dfb11
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:7"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /nomad/docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.5.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/index.mdx b/content/nomad/v1.5.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.5.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..7f8107cadf
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,580 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+Homepage: https://github.com/hashicorp/nomad-driver-podman
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement for
+Docker's][podman-cli].
+
+Due to Podman's similarity to Docker, the example job created by
+[`nomad init -short`][nomad-init] is easily adapted to use Podman instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+  type        = "service"
+
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+
+      config {
+        image = "docker://redis"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not builtin to Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- [Nomad][nomad_download] 0.12.9+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroup V2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a 3.0.x podman binary and a system socket activation unit, refer to
+[https://www.redhat.com/sysadmin/podmans-new-rest-api](https://www.redhat.com/sysadmin/podmans-new-rest-api).
+
+Nomad agent, `nomad-driver-podman` and `podman` will reside on the same client,
+so you do not have to worry about the `ssh` aspects of the Podman api.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | false                   |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | none                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - Defaults to `true`. Allows the driver to start and reuse
+  a previously stopped container after a Nomad client restart. Consider a
+  simple single node system and a complete reboot. All previously managed
+  containers will be reused instead of disposed and recreated.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.5.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..b4346bd020
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.5.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.5.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..52c652d745
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]: /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.5.x/content/plugins/index.mdx b/content/nomad/v1.5.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..87d3059efd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.5.x/content/security.mdx b/content/nomad/v1.5.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.5.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..6d2ae9d188
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..ca630dff4c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..01be84617b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..5340d70b45
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..7745568465
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency. When using this APM, it is advised to monitor Nomad carefully
+ensuring it is not put under excessive load pressure.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+  for the allocation.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+  allocated for the allocation.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..13ef0a2aab
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..b8b626e869
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d91143a086
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..a702f00bde
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..7bf2dbc6d7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+
+[client_meta_tag]: #client-meta-tag
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..f7df5bd0e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..fcf2188daf
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.5.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.5.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..9113f451e7
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.5.x/content/tools/index.mdx b/content/nomad/v1.5.x/content/tools/index.mdx
new file mode 100644
index 0000000000..d5374f55e6
--- /dev/null
+++ b/content/nomad/v1.5.x/content/tools/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+- [OpenAPI](https://github.com/hashicorp/nomad-openapi) - An OpenAPI/Swagger spec for Nomad, allowing for programmatic generation of SDKs and documentation. Includes a reference implementation in Go built on top of a generated client.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.5.x/data/api-docs-nav-data.json b/content/nomad/v1.5.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..a14d91ba00
--- /dev/null
+++ b/content/nomad/v1.5.x/data/api-docs-nav-data.json
@@ -0,0 +1,190 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "path": "variables"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.5.x/data/docs-nav-data.json b/content/nomad/v1.5.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..ef5d2f4a90
--- /dev/null
+++ b/content/nomad/v1.5.x/data/docs-nav-data.json
@@ -0,0 +1,2229 @@
+[
+  {
+    "title": "Installing Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Service Mesh",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "ACL",
+        "path": "concepts/acl"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "auth-method",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/auth-method/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/auth-method/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/auth-method/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/auth-method/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/auth-method/update"
+              }
+            ]
+          },
+          {
+            "title": "binding-rule",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/binding-rule/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/binding-rule/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/binding-rule/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/binding-rule/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/binding-rule/update"
+              }
+            ]
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "checks",
+            "path": "commands/alloc/checks"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "restart",
+            "path": "commands/job/restart"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          }
+        ]
+      },
+      {
+        "title": "login",
+        "path": "commands/login"
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "meta",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "commands/node/meta"
+              },
+              {
+                "title": "apply",
+                "path": "commands/node/meta/apply"
+              },
+              {
+                "title": "read",
+                "path": "commands/node/meta/read"
+              }
+            ]
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "client-state",
+            "path": "commands/operator/client-state"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt"
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      },
+      {
+        "title": "Considerations for Stateful Workloads",
+        "path": "operations/stateful-workloads"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      },
+      {
+        "title": "Sentinel",
+        "path": "enterprise/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.5.x/data/intro-nav-data.json b/content/nomad/v1.5.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..0fdab4c70f
--- /dev/null
+++ b/content/nomad/v1.5.x/data/intro-nav-data.json
@@ -0,0 +1,31 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "href": "https://developer.hashicorp.com/nomad/tutorials/get-started"
+  }
+]
diff --git a/content/nomad/v1.5.x/data/plugins-nav-data.json b/content/nomad/v1.5.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..76f9127194
--- /dev/null
+++ b/content/nomad/v1.5.x/data/plugins-nav-data.json
@@ -0,0 +1,117 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.5.x/data/tools-nav-data.json b/content/nomad/v1.5.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..51a278df1f
--- /dev/null
+++ b/content/nomad/v1.5.x/data/tools-nav-data.json
@@ -0,0 +1,227 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.5.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.5.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.5.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.5.x/img/autoscaling/control-loop.png b/content/nomad/v1.5.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.5.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.5.x/img/autoscaling/policy-eval.png b/content/nomad/v1.5.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.5.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.5.x/img/count-dashboard.png b/content/nomad/v1.5.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.5.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.5.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.5.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.5.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/favicon-16x16.png b/content/nomad/v1.5.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/favicon-194x194.png b/content/nomad/v1.5.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/favicon-32x32.png b/content/nomad/v1.5.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/favicon.ico b/content/nomad/v1.5.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.5.x/img/favicons/mstile-144x144.png b/content/nomad/v1.5.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/mstile-150x150.png b/content/nomad/v1.5.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/mstile-310x150.png b/content/nomad/v1.5.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/mstile-310x310.png b/content/nomad/v1.5.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/mstile-70x70.png b/content/nomad/v1.5.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.5.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.5.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.5.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.5.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.5.x/img/home-hero-pattern.svg b/content/nomad/v1.5.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.5.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/img/logo-hashicorp.svg b/content/nomad/v1.5.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.5.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.5.x/img/logo-text.svg b/content/nomad/v1.5.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.5.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.5.x/img/networking/bridge.png b/content/nomad/v1.5.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.5.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.5.x/img/networking/docker_bridge.png b/content/nomad/v1.5.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.5.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.5.x/img/networking/port_mapping.png b/content/nomad/v1.5.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.5.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-architecture-global.png b/content/nomad/v1.5.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-architecture-region.png b/content/nomad/v1.5.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-bg-pattern.svg b/content/nomad/v1.5.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.5.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.5.x/img/nomad-bridge-network.png b/content/nomad/v1.5.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-data-model.png b/content/nomad/v1.5.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-evaluation-flow.png b/content/nomad/v1.5.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-kubernetes.png b/content/nomad/v1.5.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.5.x/img/nomad-panel-learn.svg b/content/nomad/v1.5.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.5.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.5.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.5.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.5.x/img/nomad-workload.png b/content/nomad/v1.5.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.5.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.5.x/img/og-image.png b/content/nomad/v1.5.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.5.x/img/og-image.png differ
diff --git a/content/nomad/v1.5.x/img/pattern.svg b/content/nomad/v1.5.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.5.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/img/practice-pattern.svg b/content/nomad/v1.5.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.5.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/img/usecase-callout-pattern.svg b/content/nomad/v1.5.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.5.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/img/usecase-hero-pattern.svg b/content/nomad/v1.5.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.5.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.5.x/redirects.jsonc b/content/nomad/v1.5.x/redirects.jsonc
new file mode 100644
index 0000000000..e3ec97df94
--- /dev/null
+++ b/content/nomad/v1.5.x/redirects.jsonc
@@ -0,0 +1,48 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+  // Rename and re-arrange Autoscaling Internals section
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.6.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..f302563459
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,497 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+  The name can contain alphanumeric characters, dashes, and underscores. This
+  name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and `JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either `local` or `global`.
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set, it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+    any `.well-known` component (base path). Required for `OIDC` method type.
+    Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+    `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+    your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+    configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+    to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+    `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+    signatures. Either this, the `JWTValidationPubKeys` or the
+    `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+    to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+    validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+    validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+    validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Names is the identifier of the ACL auth
+  method.  The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth role SSO identifier. Currently, the
+  only supported Type is "OIDC."
+
+- `TokenLocality` `(string: "")` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either "local" or "global"
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL auth method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: nil)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: "")` - The OIDC discovery URL, without
+    any .well-known component (base path).
+
+  - `OIDCClientID` `(string: "")` - The OAuth client ID configured with
+    your OIDC provider.
+
+  - `OIDCClientSecret` `(string: "")` - The OAuth client secret
+    configured with your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.6.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..93451a8704
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `POST` | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/index.mdx b/content/nomad/v1.6.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..318f42b704
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/login.mdx b/content/nomad/v1.6.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.6.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.6.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..4e07722b8c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,188 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given
+  namespace, job, group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - The namespace to attach the policy.
+    Required if `JobID` is set.
+
+  - `JobID` `(string: <optional>)` - The job to attach to the policy. Required
+    if `Group` is set.
+
+  - `Group` `(string: <optional>)` - The group to attach to the policy.
+    Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - The task to attach to the policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.6.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..7e2e2ca580
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `POST` | `/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters, dashes, and underscores.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                 | Produces       |
+| -------- | -------------------- | -------------- |
+| `DELETE` | `/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.6.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..9d81cee9c9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.6.x/content/api-docs/agent.mdx b/content/nomad/v1.6.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..0331407b2b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.6.x/content/api-docs/allocations.mdx b/content/nomad/v1.6.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..5176a3b38c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/allocations.mdx
@@ -0,0 +1,961 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.6.x/content/api-docs/client.mdx b/content/nomad/v1.6.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..52993fb4d4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node recieving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node recieving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.6.x/content/api-docs/deployments.mdx b/content/nomad/v1.6.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/evaluations.mdx b/content/nomad/v1.6.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..2984cdaf1e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.6.x/content/api-docs/events.mdx b/content/nomad/v1.6.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..e99bf630d7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/events.mdx
@@ -0,0 +1,391 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `NodePool`   | `management`         |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| NodePool   | NodePool                        |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| NodePoolUpserted              |
+| NodePoolDeleted               |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/index.mdx b/content/nomad/v1.6.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..55713ae728
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/index.mdx
@@ -0,0 +1,699 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl:
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=qa
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> --data-urlencode 'filter=<filter expression>'
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/jobs \
+    --data-urlencode 'filter=Datacenters contains "dc2"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ curl --request GET https://localhost:4646/v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell
+curl --get https://localhost:4646/v1/deployments \
+    --data-urlencode 'filter=Status != "successful"'
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
diff --git a/content/nomad/v1.6.x/content/api-docs/jobs.mdx b/content/nomad/v1.6.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..649321e507
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2507 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+- `VariableFlags` `(map[string]string: nil)` - Specifies HCL2 variables to use
+  during parsing of the job in key = value format.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2`, `hcl1`, or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `IdempotencyToken` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job (as specified
+  in the job file during submission). This is specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+- the job file during submission). This is specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+  the job file during submission). This is specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job (as specified in
+the job file during submission). This is specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.6.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..f35168cb02
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1221 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.6.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.6.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..828cb1af80
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,39 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.6.x/content/api-docs/metrics.mdx b/content/nomad/v1.6.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/namespaces.mdx b/content/nomad/v1.6.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/node-pools.mdx b/content/nomad/v1.6.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.6.x/content/api-docs/nodes.mdx b/content/nomad/v1.6.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..2acff9d512
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1147 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.6.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..76bc8d1346
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,215 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ]
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/index.mdx b/content/nomad/v1.6.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.6.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..ad4975c121
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,157 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/license.mdx b/content/nomad/v1.6.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.6.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..b6313223f0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,117 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of  the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 1,
+  "Servers": [
+    {
+      "Address": "127.0.0.1:4647",
+      "ID": "127.0.0.1:4647",
+      "Leader": true,
+      "Node": "bacon-mac.global",
+      "RaftProtocol": 2,
+      "Voter": true
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. This is the same as the `Address`
+    but may be upgraded to a GUID in a future version of Nomad.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the server to remove as
+  `ip:port`. This cannot be provided along with the `id` parameter.
+
+- `id` `(string: <optional>)` - Specifies the server to remove as
+  `id`. This cannot be provided along with the `address` parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/operator/raft/peer?address=1.2.3.4:4646
+```
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.6.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.6.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.6.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.6.x/content/api-docs/plugins.mdx b/content/nomad/v1.6.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/quotas.mdx b/content/nomad/v1.6.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..112d80d7e9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/quotas.mdx
@@ -0,0 +1,354 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/recommendations.mdx b/content/nomad/v1.6.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/regions.mdx b/content/nomad/v1.6.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.6.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/search.mdx b/content/nomad/v1.6.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..247ed39453
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/search.mdx
@@ -0,0 +1,638 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.6.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.6.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/services.mdx b/content/nomad/v1.6.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/api-docs/status.mdx b/content/nomad/v1.6.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/system.mdx b/content/nomad/v1.6.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/task-api.mdx b/content/nomad/v1.6.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..31f8038074
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/task-api.mdx
@@ -0,0 +1,103 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+[acl]: /nomad/docs/concepts/acl
+[acl-tokens]: /nomad/docs/concepts/acl#token
+[alloc-exec]: /nomad/docs/commands/alloc/exec
+[anon]: /nomad/tutorials/access-control/access-control#acl-policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[dnm]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.6.x/content/api-docs/ui.mdx b/content/nomad/v1.6.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.6.x/content/api-docs/validate.mdx b/content/nomad/v1.6.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.6.x/content/api-docs/variables.mdx b/content/nomad/v1.6.x/content/api-docs/variables.mdx
new file mode 100644
index 0000000000..f68c0fbd54
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/variables.mdx
@@ -0,0 +1,298 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`] commands.
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+
+[Variables]: /nomad/docs/concepts/variables
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.6.x/content/api-docs/volumes.mdx b/content/nomad/v1.6.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..a7569a5464
--- /dev/null
+++ b/content/nomad/v1.6.x/content/api-docs/volumes.mdx
@@ -0,0 +1,783 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below). It is an error
+to register an already registered volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. It is an error to create an already-registered volume. Only CSI
+plugins that implement the [Controller][csi_plugins_internals] interface with
+the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/create.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..8cc6519a78
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/create.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method create'
+description: The auth-method create command is used to create new ACL Auth Methods.
+---
+
+# Command: acl auth-method create
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = local
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..45303a5658
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method delete'
+description: The auth-method delete command is used to delete existing ACL Auth Methods.
+---
+
+# Command: acl auth-method delete
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/info.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..1f7605213a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/info.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method info'
+description: |
+  The auth-method info command is used to fetch information about an existing
+  ACL Auth Method.
+---
+
+# Command: acl auth-method info
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = local
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/list.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..0cb15df8e6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method list'
+description: The auth-method list command is used to list existing ACL Auth Methods.
+---
+
+# Command: acl auth-method list
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/update.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..2dd8a9d668
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/auth-method/update.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method update'
+description: The auth-method update command is used to update existing ACL Auth Methods.
+---
+
+# Command: acl auth-method update
+
+The `acl auth-method update` command is used to update existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -config @config.json example-acl-auth-method
+Name           = example-acl-auth-method
+Type           = OIDC
+Locality       = global
+Max Token TTL  = 1h0m0s
+Default        = false
+Create Index   = 14
+Modify Index   = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/create.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..e15d870756
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule create'
+description: The binding-rule create command is used to create new ACL Binding Rules.
+---
+
+# Command: acl binding-rule create
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..0bdafd9689
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule delete'
+description: The binding-rule delete command is used to delete existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule delete
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/info.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..38dcfb2eeb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule info'
+description: |
+  The binding-rule info command is used to fetch information about an existing
+  ACL Binding Rule.
+---
+
+# Command: acl binding-rule info
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/list.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..d506f8a8d2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule list'
+description: The binding-rule list command is used to list existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule list
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/update.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..03bacdd24d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule update'
+description: The binding-rule update command is used to update existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule update
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..f797d33d2e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an apropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..d079e2ca12
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[authmethodcreate]: /nomad/docs/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/docs/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/docs/commands/acl/auth-method/info
+[authmethodlist]: /nomad/docs/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/docs/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/docs/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/docs/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/docs/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/docs/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/docs/commands/acl/binding-rule/update
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..af000cd896
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..f0622d92c4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..64d72c4b0c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl role create'
+description: The role create command is used to create new ACL Roles.
+---
+
+# Command: acl role create
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..f4e4a93b9f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl role delete'
+description: The role delete command is used to delete existing ACL Roles.
+---
+
+# Command: acl role delete
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..7a2f40a8bd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl role info'
+description: |
+  The role info command is used to fetch information about an existing ACL
+  Role.
+---
+
+# Command: acl role info
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..6f36f8d065
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl role list'
+description: The role list command is used to list existing ACL Roles.
+---
+
+# Command: acl role list
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..cc808f8386
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl role update'
+description: The role update command is used to update existing ACL Roles.
+---
+
+# Command: acl role update
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters, dashes, and underscores. This name must
+  be unique and must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..5c0c77d051
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..33e442126e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..fb8fc94ac2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..b58a7193b8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.6.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..57c293382f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.6.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/agent.mdx b/content/nomad/v1.6.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..02c1140424
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/agent.mdx
@@ -0,0 +1,231 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join] config
+  option.
+
+- `-consul-ssl`: Equivalent to the [ssl] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. This mode
+  is supported only on Linux as root.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location] config option.
+
+- `-log-json`: Equivalent to the [log_json] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface] config option.
+
+- `-node=<name>`: Equivalent to the [name] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir] config option.
+
+- `-region=<region>`: Equivalent to the [region] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad agent]: /nomad/docs/operations/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/checks.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..fc1b02c1e2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: alloc checks'
+description: |
+  Outputs service health check status information.
+---
+
+# Command: alloc checks
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability 
+for the allocation's namespace. The 'list-jobs' capability is required to run the 
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Checks Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..8ea9ae7216
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..2fdb4e42c9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..b673a63f04
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/docs/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..ddf16f7b7a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.6.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..718d962d57
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.6.x/content/docs/commands/config/index.mdx b/content/nomad/v1.6.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.6.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.6.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..9c72af2dce
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..d40b151754
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3369798607
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..86542733e2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.6.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..9214e1adf4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.6.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..a4900f08ff
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfuly deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfuly deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfuly deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.6.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.6.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.6.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.6.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.6.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/fmt.mdx b/content/nomad/v1.6.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..d40d17c95a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: fmt'
+description: |
+  Rewrite Nomad config and job files to canonical format
+---
+
+# Command: fmt
+
+The `fmt` commands check the syntax and rewrites Nomad configuration and jobspec
+files to canonical format. It can be used to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [flags] paths ...
+```
+
+Formats Nomad agent configuration and job file to a canonical format. If a path
+is a directory, it will recursively format all files with .nomad and .hcl
+extensions in the directory.
+
+If you provide a single dash (-) as argument, fmt will read from standard input
+(STDIN) and output the processed output to standard output (STDOUT).
+
+Note that, this command will check the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 jobspec will result in errors.
+
+## Format Options:
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/index.mdx b/content/nomad/v1.6.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.6.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..72f2e9a443
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.6.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..ccfcf28be1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.6.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..235cc952c3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.6.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..9d3a2cf8ee
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/history.mdx b/content/nomad/v1.6.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..9544f64140
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/index.mdx b/content/nomad/v1.6.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..47ff5c79d8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/init.mdx b/content/nomad/v1.6.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..1c5a7d5ecc
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.6.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..a96593f779
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.6.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..8aca82eb80
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.6.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..2d62783d19
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,263 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.6.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..28dab1fc76
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/restart.mdx b/content/nomad/v1.6.x/content/docs/commands/job/restart.mdx
new file mode 100644
index 0000000000..6f87e40a82
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'Commands: job restart'
+description: |
+  The job restart command is used to restart allocations for a job.
+---
+
+# Command: job restart
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+Allocations can be restarted in-place or rescheduled. When restarting
+in-place the command may target specific tasks in the allocations, restart
+only tasks that are currently running, or restart all tasks, even the ones
+that have already run. Allocations can also be targeted by groups and tasks.
+When both groups and tasks are defined only the tasks for the allocations of
+those groups are restarted.
+
+When rescheduling, the current allocations are stopped triggering the Nomad
+scheduler to create replacement allocations that may be placed in different
+clients. The command waits until the new allocations have client status `ready`
+before proceeding with the remaining batches. Services health checks are not
+taken into account.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, allocations are stopped and rescheduled instead of
+  restarted in-place. Since the group is not modified the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such
+  as [`max_parallel`][], are not taken into account. This option cannot be used
+  with `-task`. Only jobs of type `batch`, `service`, and `system` can be
+  rescheduled.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.6.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..f0bd4efa60
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/run.mdx b/content/nomad/v1.6.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..36f2c87f85
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.6.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..f3171dc5f3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.6.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..dd639766f6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/status.mdx b/content/nomad/v1.6.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..5842f80592
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.6.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..ad19f5afac
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.6.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.6.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..738f7f759f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.6.x/content/docs/commands/license/get.mdx b/content/nomad/v1.6.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..e56b0a4aeb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/license/index.mdx b/content/nomad/v1.6.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..a248a76d37
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are only available with Nomad Enterprise.
+
+The `license` commands can be used to retrieve license information from a server,
+or inspect and validate a license.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/docs/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.6.x/content/docs/commands/license/inspect.mdx b/content/nomad/v1.6.x/content/docs/commands/license/inspect.mdx
new file mode 100644
index 0000000000..d1689b5122
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/license/inspect.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license inspect'
+description: |
+  The license inspect command is used to inspect and validate an enterprise license.
+---
+
+# Command: license inspect
+
+<EnterpriseAlert>
+  This command is only present in Nomad Enterprise.
+</EnterpriseAlert>
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/login.mdx b/content/nomad/v1.6.x/content/docs/commands/login.mdx
new file mode 100644
index 0000000000..1dd2bf1645
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/login.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: login'
+description: |
+  Login to Nomad using an authentication method
+---
+
+# Command: login
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Login Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/monitor.mdx b/content/nomad/v1.6.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..445dab5007
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..c1ac6e347f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers  = ["docker", "exec"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..a32e049fff
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs. In federated clusters,
+you cannot delete a namespace that has non-terminal jobs in any of the federated
+regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..8e53e9085a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..4c1e61828b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..3f9c543249
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.6.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..1a6ea780e8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name            = api-prod
+Description     = Prod API servers
+Quota           = prod
+EnabledDrivers  = docker,exec
+DisabledDrivers = raw_exec
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..c185e960a9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: node pool apply'
+description: |
+  The node pool apply command is used to create or update a node pool.
+---
+
+# Command: node pool apply
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..bc9748cc96
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool delete'
+description: |
+  The node pool delete command is used to delete a node pool.
+---
+
+# Command: node pool delete
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/index.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..f541856c4d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool'
+description: |
+  The node pool command is used to interact with node pools.
+---
+
+# Command: node pool
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+Usage: `nomad node pool <subcommand> [options]`
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/docs/commands/node-pool/apply
+[delete]: /nomad/docs/commands/node-pool/delete
+[info]: /nomad/docs/commands/node-pool/info
+[jobs]: /nomad/docs/commands/node-pool/jobs
+[list]: /nomad/docs/commands/node-pool/list
+[nodes]: /nomad/docs/commands/node-pool/nodes
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/info.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..e15231aef2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: node pool info'
+description: |
+  The node pool info command is used to fetch information about a node pool.
+---
+
+# Command: node pool info
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name        = prod
+Description = Node pool for production workloads.
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/init.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..6f76c045e6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool init'
+description: |
+  Generate an example node pool specification.
+---
+
+# Command: node pool init
+
+The `node pool init` creates an example node pool specification file that can be
+used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/jobs.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..f55c9723df
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: node pool jobs'
+description: |
+  The node pool jobs command is used to list jobs in node pool.
+---
+
+# Command: node pool jobs
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Jobs Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/list.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..e9f472b836
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'Commands: node pool list'
+description: |
+  The node pool list command is used to list node pools.
+---
+
+# Command: node pool list
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.6.x/content/docs/commands/node-pool/nodes.mdx b/content/nomad/v1.6.x/content/docs/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..e9ebefa252
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: node pool nodes'
+description: |
+  The node pool nodes command is used to list nodes in node pool.
+---
+
+# Command: node pool nodes
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Nodes Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/config.mdx b/content/nomad/v1.6.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.6.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..4d24e9e47a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.6.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/index.mdx b/content/nomad/v1.6.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..289d1a027f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/docs/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/meta/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..5b67230336
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: node meta apply'
+description: |
+  The node meta apply command updates node metadata.
+---
+
+# Command: node meta apply
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Apply Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+[api]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/meta/index.mdx b/content/nomad/v1.6.x/content/docs/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..2b65048e5b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/meta/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: node meta'
+description: |
+  The node meta commands are used to read and update node metadata.
+---
+
+# Command: node meta
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+Usage: `nomad node meta <subcommand> [options]`
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/runtime/interpolation#node-attributes
+[apply]: /nomad/docs/commands/node/meta/apply
+[read]: /nomad/docs/commands/node/meta/read
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/meta/read.mdx b/content/nomad/v1.6.x/content/docs/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..e04e685313
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: node meta read'
+description: |
+  The node meta read command reads node metadata.
+---
+
+# Command: node meta read
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Read Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+[api]: /nomad/api-docs/client#read-node-metadata
diff --git a/content/nomad/v1.6.x/content/docs/commands/node/status.mdx b/content/nomad/v1.6.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..d6c2488c10
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/client-state.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..6475fe5477
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'Commands: operator client-state'
+description: >
+  The `operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# Command: operator client-state
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..8ffde93526
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..d703f46ae8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring generate'
+description: >
+  The `operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator gossip keyring generate
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..e30c21b5b4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring install'
+description: |
+  Install a new gossip encryption key
+---
+
+# Command: operator gossip keyring install
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..e05d940bd9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring list'
+description: |
+  List gossip keys
+---
+
+# Command: operator gossip keyring list
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..97009d769f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring remove'
+description: |
+  Remove a new gossip encryption key
+---
+
+# Command: operator gossip keyring remove
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..708b506787
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring use'
+description: |
+  Use a new gossip encryption key
+---
+
+# Command: operator gossip keyring use
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..fd097a007a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/docs/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/docs/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/docs/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/docs/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/docs/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/docs/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/docs/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/docs/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..e5f337b373
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+description: |-
+  The `operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..e049b8b795
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring list'
+description: |
+  List encryption key metadata
+---
+
+# Command: operator root keyring list
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..bcf701378e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring remove'
+description: |
+  Remove an unused encryption key
+---
+
+# Command: operator root keyring remove
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..aef49c6265
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring rotate'
+description: |
+  Rotate encryption key
+---
+
+# Command: operator root keyring rotate
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Rotate Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..b3d7049f73
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+<Warning>
+
+This snapshot agent only saves a Raft snapshot. Key material for the Nomad
+keyring is stored on disk and must be saved separately. To use a snapshot saved
+by the agent to recover a cluster, you will also need to [restore the keyring][]
+onto at least one server.
+
+</Warning>
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
+
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..1170fc5c70
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Displays information about a snapshot file stored on local disk.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Inspect Options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..049282452f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+<Warning>
+
+This command only restores the Raft snapshot, which does not include keyrings.
+
+If you are recovering a cluster, you also need to restore the keyring onto at
+least one server.  Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..d1e4a4a5e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command only saves a Raft snapshot. This snapshot does not include
+keyrings. You must back up keyrings separately.
+
+If you use this snapshot to recover a cluster, you also need to restore the
+keyring onto at least one server. Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.6.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.6.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.6.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..1775a87963
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..d7a1945d54
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..577c162878
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..1984aaa386
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..31798b859b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..466c5e3edd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.6.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..4bd6b11c7a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..a9eb367d20
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.6.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..ade257d00c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.6.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..55c9599045
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.6.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.6.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..1ae6c075e5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.6.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..cafdf65b2e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.6.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..0dda69be94
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.6.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.6.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.6.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.6.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..b6322dbfc8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..6f828efbec
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.6.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f16f4225c0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.6.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.6.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..1fff15759b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.6.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..81e8e6d6cb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.6.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..cb7f001f83
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`. 
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Force-Leave Options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/server/index.mdx b/content/nomad/v1.6.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.6.x/content/docs/commands/server/join.mdx b/content/nomad/v1.6.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..a5a6661ec8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: /nomad/tutorials/manage-clusters/federation
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.6.x/content/docs/commands/server/members.mdx b/content/nomad/v1.6.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..3ace4d8db8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server memebers in its JSON format.
+
+- `-t`: Format and display the server memebers using a Go template.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..902be4e38c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/service/index.mdx b/content/nomad/v1.6.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..c1be98efff
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.6.x/content/docs/commands/service/info.mdx b/content/nomad/v1.6.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..4c0a77007d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/service/list.mdx b/content/nomad/v1.6.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..9715fb65e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/status.mdx b/content/nomad/v1.6.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.6.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/system/index.mdx b/content/nomad/v1.6.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.6.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.6.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.6.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..3e90a45c4f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: tls ca create'
+description: |
+  This command creates a Certificate Authority that can be used to create
+  self signed certificates to be used for Nomad TLS setup.
+---
+
+# Command: nomad tls ca create
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## CA Create Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.6.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..0261571b19
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: tls ca info'
+description: |
+  This command displays relevant information that is contained within a
+  Certificate Authority certificate.
+---
+
+# Command: nomad tls ca info
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.6.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..d0fc2d5bb0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Create'
+description: |
+  This command creates a Certificate that can be used for Nomad TLS setup.
+---
+
+# Command: nomad tls cert create
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Command Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-cluster-region=<string>`: DEPRECATED please use `-region`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.6.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.6.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..c37f6a54c0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Info'
+description: |
+  This command displays relevant information that is contained within a
+  certificate.
+---
+
+# Command: nomad tls cert info
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.6.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..1e580053ee
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: tls'
+description: |
+  The tls command is used to help with creating a Certificate Authority 
+  and up self signed certificates for Nomad TLS configuration.
+---
+
+# Command: tls
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/docs/commands/ui.mdx b/content/nomad/v1.6.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/get.mdx b/content/nomad/v1.6.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..3639942887
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: "Command: var get"
+description: |-
+  The "var get" command retrieves the variable at the given path from
+  Nomad. If no variable exists at that path, an error is returned.
+---
+
+# Command: var get
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/index.mdx b/content/nomad/v1.6.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..16f7bd5334
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: "Commands: var"
+description: |-
+  The "var" command groups subcommands for interacting with Nomad variables.
+---
+
+# Command: var
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/init.mdx b/content/nomad/v1.6.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..8a99bf81fa
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: var init'
+description: |
+  Generate an example variable specification.
+---
+
+# Command: var init
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/list.mdx b/content/nomad/v1.6.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d8974ffff2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: "Command: var list"
+description: |-
+  The "var list" command lists data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# Command: var list
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.6.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..c924fa77ab
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: "Command: var purge"
+description: |-
+  The "var purge" command permanently removes the specified variable
+  from Nomad.
+---
+
+# Command: var purge
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Command Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.6.x/content/docs/commands/var/put.mdx b/content/nomad/v1.6.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..34a361ad3a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: "Command: var put"
+description: |-
+  The "var put" command writes a variable to the given path in Nomad.
+---
+
+# Command: var put
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.6.x/content/docs/commands/version.mdx b/content/nomad/v1.6.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b58b9ae222
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..39b0b39c93
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..726ed55b84
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.6.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.6.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..bc8088789e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.6.x/content/docs/concepts/acl.mdx b/content/nomad/v1.6.x/content/docs/concepts/acl.mdx
new file mode 100644
index 0000000000..aee744db85
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/acl.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Access Control List (ACL)
+description: Learn about Nomad's ACL subsystem
+---
+
+# Access Control List (ACL)
+
+The Nomad ACL system is designed to be intuitive, high-performance, and to
+provide administrative insight. At the highest level, there are four major
+components to the ACL system: tokens, policies, roles, and capabilities. The
+two components named auth methods and binding rules are specific to Nomad's
+Single Sign-On (SSO) ACL capabilities.
+
+The Nomad [access control tutorials][] provide detailed information and
+guidance on Nomad ACL system.
+
+### Policy
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy comprises one or more rules. The rules define the capabilities of a
+Nomad ACL token for accessing the objects in a Nomad cluster, objects like
+namespaces, node, agent, operator, quota, etc. For more information on writing
+policies, see the [ACL policy reference doc][].
+
+### Role
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+### Token
+
+Requests to Nomad are authenticated using a bearer token. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. `Local` tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+### Workload Identity
+
+Nomad allocations can receive workload identities in the form of a
+[JSON Web Token (JWT)][jwt]. The
+[Workload Identity concept page][workload identity] has more information on
+this topic.
+
+### Auth Method
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+### Binding Rule
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[access control tutorials]: /nomad/tutorials/access-control
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
+[vault]: https://www.vaultproject.io/
diff --git a/content/nomad/v1.6.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.6.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..f204891550
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.6.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.6.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.6.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.6.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..74dff6d50a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,491 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.6.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.6.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..d5b2f7cf42
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/nomad/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.6.x/content/docs/concepts/index.mdx b/content/nomad/v1.6.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.6.x/content/docs/concepts/node-pools.mdx b/content/nomad/v1.6.x/content/docs/concepts/node-pools.mdx
new file mode 100644
index 0000000000..e87474f7cb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/node-pools.mdx
@@ -0,0 +1,379 @@
+---
+layout: docs
+page_title: Node Pools
+description: Learn about the internal architecture of Nomad.
+---
+
+# Node Pools
+
+Node pools are a way to group clients and segment infrastructure into logical
+units that can be targeted by jobs for a strong control over where allocations
+are placed.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+A node pool can be created using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config  block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/docs/commands/node-pool/apply
+[cli_agent_np]: /nomad/docs/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..74c13eb651
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Network Plugins
+description: Learn how Nomad manages custom user-specified network configurations.
+---
+
+# Network plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#linux-post-installation-steps
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..a7f5a4ed19
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..79e2aa1a75
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.6.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.6.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..f549db2f5a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propagating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
diff --git a/content/nomad/v1.6.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.6.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..32fa6d8b67
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.6.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.6.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..b50949ae0a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: Placement
+description: Learn about how placements are computed in Nomad.
+---
+
+# Placement
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+### Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+#### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+#### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+### Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+### Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+
+[api_client_metadata]: /nomad/api-docs/client#update-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/concepts/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.6.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.6.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..291008f78b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.6.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.6.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..e6b39f2498
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.6.x/content/docs/concepts/security.mdx b/content/nomad/v1.6.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..739932e206
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/security.mdx
@@ -0,0 +1,339 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** -
+  Access to read and write to a namespace can be
+  controlled to allow for granular access to job information managed within a
+  multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
+
+
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
diff --git a/content/nomad/v1.6.x/content/docs/concepts/variables.mdx b/content/nomad/v1.6.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..85016a45e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Variables
+description: Learn about the Nomad Variables feature
+---
+
+# Nomad Variables
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to [provide such configuration to tasks](/nomad/docs/job-specification/template#nomad-variables),
+but prior to Nomad 1.4 has left the role of storing that configuration to
+external services such as [HashiCorp Consul] and [HashiCorp Vault].
+
+Nomad Variables provide the option to store configuration at file-like paths
+directly in Nomad's state store. You can [access these variables](/nomad/docs/job-specification/template#nomad-variables) directly from
+your task `template`s. The contents of these variables are encrypted
+and replicated between servers via raft. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the Variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as Variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. See [Key Management][] for details.
+
+## ACL for Variables
+
+Every Variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to Variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for Variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+In Nomad 1.4.0 tasks can only access Variables with the [`template`] block. The
+[workload identity] for each task grants it automatic read and list access to
+Variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to Variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
diff --git a/content/nomad/v1.6.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.6.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..b1c22ab2bd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Learn about Nomad's workload identity feature
+---
+
+# Workload Identity
+
+Every workload running in Nomad is given an identity. When an [allocation][] is
+accepted by the [plan applier][], the leader generates a Workload Identity for
+each task in the allocation. This workload identity is a [JSON Web Token
+(JWT)][] that has been signed by the leader's keyring. The workload identity
+includes the following identity claims:
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+## Using Workload Identity
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+## Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+## Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
diff --git a/content/nomad/v1.6.x/content/docs/configuration/acl.mdx b/content/nomad/v1.6.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..07c6437783
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. See [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.6.x/content/docs/configuration/audit.mdx b/content/nomad/v1.6.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.6.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.6.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.6.x/content/docs/configuration/client.mdx b/content/nomad/v1.6.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..0d03114d85
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/client.mdx
@@ -0,0 +1,745 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers . If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers . If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/runtime/interpolation
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/docs/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.6.x/content/docs/configuration/consul.mdx b/content/nomad/v1.6.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..cda50bede1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,247 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+## `consul` Parameters
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul Connect
+  enabled services listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+   certificate used for communication between Connect sidecar proxies and Consul
+   agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+   <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. See
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `namespace` `(string: "")` - Specifies the [Consul namespace](/consul/docs/enterprise/namespaces)
+  used by the Consul integration. If non-empty, this namespace will be used on
+  all Consul API calls and for Consul Connect configurations.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not include
+  the values for the ACL `token` or `auth`. This option should be disabled in
+  environments where Consul ACLs are not enabled.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and agent services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes. Will default to the `CONSUL_HTTP_TOKEN`
+  environment variable if set.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
diff --git a/content/nomad/v1.6.x/content/docs/configuration/index.mdx b/content/nomad/v1.6.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..08408a681f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/index.mdx
@@ -0,0 +1,401 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.6.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.6.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.6.x/content/docs/configuration/search.mdx b/content/nomad/v1.6.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.6.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.6.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.6.x/content/docs/configuration/server.mdx b/content/nomad/v1.6.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..64a1de3b93
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/server.mdx
@@ -0,0 +1,513 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens. Non-authoritative regions will replicate from
+  the authoritative to act as a mirror. By default, the local region is assumed
+  to be authoritative. Setting `authoritative_region` assumes that ACLs have
+  been bootstrapped in the authoritative region. See [Configure for multiple
+  regions][] in the ACLs tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". See [Client Heartbeats](#client-heartbeats) below for details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients
+  must heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". See [Client Heartbeats](#client-heartbeats) below
+  for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. See [Client Heartbeats](#client-heartbeats)
+  below for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`max_client_disconnect`][max_client_disconnect] is set)
+and rescheduled.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer a `down` Client's workload will
+  take to be rescheduled.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  rescheduled.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO (see below)       |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and reschedules their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator gossip keyring generate`]: /nomad/docs/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[max_client_disconnect]: /nomad/docs/job-specification/group#max-client-disconnect
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.6.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.6.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..01ab823304
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join. This is similar to [`start_join`](#start_join), but will continue to
+  be attempted even if the initial join attempt fails, up to
+  [retry_max](#retry_max). Further, `retry_join` is available to
+  both Nomad servers and clients, while `start_join` is only defined for Nomad
+  servers. This is useful for cases where we know the address will become
+  available eventually. Use `retry_join` with an array as a replacement for
+  `start_join`, **do not use both options**.
+
+  Address format includes both using IP addresses as well as an interface to the
+  [go-discover](https://github.com/hashicorp/go-discover) library for doing
+  automated cluster joining using cloud metadata. See the [Cloud Auto-join](#cloud-auto-join)
+  section below for more information.
+
+  ```
+  server_join {
+  retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Using the `go-discover` interface, this can be defined both in a client or
+  server configuration as well as provided as a command-line argument.
+
+  ```
+  server_join {
+  retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See the [server address format](#server-address-format) for more information about expected
+  server address formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+
+As of Nomad 0.8.4, `retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+#### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+#### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
diff --git a/content/nomad/v1.6.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.6.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..fe073731ed
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,191 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.6.x/content/docs/configuration/tls.mdx b/content/nomad/v1.6.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..4957e5bed1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to enforce
+secure cluster communication between servers, clients, and between. Note that in
+most cases, this is mutual TLS (mTLS) where both ends of the connection
+authenticate each other. The Nomad documentation will typically use "TLS" to
+refer to this communication except when it is potentially ambiguous between TLS
+and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.6.x/content/docs/configuration/ui.mdx b/content/nomad/v1.6.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..a51c912582
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI will default to a black background. HEX values  
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI will default to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.6.x/content/docs/configuration/vault.mdx b/content/nomad/v1.6.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..dad303682c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, Nomad can create and distribute Vault tokens to
+tasks automatically. For more information on the architecture and setup, please
+see the [Nomad and Vault integration documentation][nomad-vault].
+
+```hcl
+vault {
+  enabled = true
+  address = "https://vault.company.internal:8200"
+}
+```
+
+## `vault` Parameters
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+  The token given to Nomad does not have to be created from this role but must
+  have "`update`" capability on "`auth/token/create/<create_from_role>`" path in
+  Vault. If this value is unset and the token is created from a role, the value
+  is defaulted to the role the token is from. This is largely for backwards
+  compatibility. It is recommended to set the `create_from_role` field if Nomad
+  is deriving child tokens from a role.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows an example Vault configuration for a Nomad server:
+
+```hcl
+vault {
+  enabled     = true
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address     = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token       = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows an example Vault configuration for a Nomad client:
+
+```hcl
+vault {
+  enabled     = true
+  address     = "https://vault.service.consul:8200"
+  ca_path     = "/etc/certs/ca"
+  cert_file   = "/var/certs/vault.crt"
+  key_file    = "/var/certs/vault.key"
+}
+```
+
+The key difference is that the token is not necessary on the client.
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
diff --git a/content/nomad/v1.6.x/content/docs/devices/index.mdx b/content/nomad/v1.6.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.6.x/content/docs/drivers/docker.mdx b/content/nomad/v1.6.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..62a5823f2a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1241 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `cpuset_cpus` <sup>Beta</sup> - (Optional) CPUs in which to allow execution
+  (0-3, 0,1). Limit the specific CPUs or cores a container can use. A
+  comma-separated list or hyphen-separated range of CPUs a container can use, if
+  you have more than one CPU. The first CPU is numbered 0. A valid value might
+  be 0-3 (to use the first, second, third, and fourth CPU) or 1,3 (to use the
+  second and fourth CPU).
+
+Note: `cpuset_cpus` pins the workload to the CPUs but doesn't give the workload
+exclusive access to those CPUs.
+
+```hcl
+config {
+  cpuset_cpus = "0-3"
+}
+```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) One of `"hyper-v"`, `"process"`, or `"default"`
+  (which is the same as `process`). Enables [Windows isolation][] modes.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`. The image will only be pulled from
+  the container registry if its tag is `latest` or the image doesn't yet exist locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.6.x/content/docs/drivers/exec.mdx b/content/nomad/v1.6.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..b1aa54f348
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,281 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver runs binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.6.x/content/docs/drivers/index.mdx b/content/nomad/v1.6.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.6.x/content/docs/drivers/java.mdx b/content/nomad/v1.6.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..3c1050c668
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/java.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.6.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.6.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..4a86628ff0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.6.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.6.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..b8b2db68e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,157 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver uses cgroups by default on
+  Linux and when `/sys/fs/cgroup/freezer/nomad` is writable for the
+  Nomad process. Using a cgroup significantly reduces Nomad's CPU
+  usage when collecting process metrics.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+- `driver.raw_exec.no_cgroups` - Specifies whether the driver should not use
+  cgroups to manage the process group launched by the driver. By default,
+  cgroups are used to manage the process tree to ensure full cleanup of all
+  processes started by the task. The driver only uses cgroups when Nomad is
+  launched as root, on Linux and when cgroups are detected.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no isolation.
+
+If the launched process creates a new process group, it is possible that Nomad
+will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to manage
+the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, the cgroup system is mounted and the operator hasn't
+disabled cgroups for the driver.
+
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.6.x/content/docs/ecosystem.mdx b/content/nomad/v1.6.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.6.x/content/docs/enterprise/index.mdx b/content/nomad/v1.6.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..7880affe96
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,179 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/tutorials/governance-and-policy/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/enterprise/sentinel
diff --git a/content/nomad/v1.6.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.6.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..d393f419a2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/docs/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/docs/commands/license/inspect
diff --git a/content/nomad/v1.6.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.6.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..94ea48d421
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have a license to start. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/docs/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/docs/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.6.x/content/docs/enterprise/sentinel.mdx b/content/nomad/v1.6.x/content/docs/enterprise/sentinel.mdx
new file mode 100644
index 0000000000..6ca332992a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/enterprise/sentinel.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Sentinel Policy Reference
+description: >-
+  Learn about Nomad Sentinel Policy Objects
+---
+
+## Sentinel
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+See the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`
+subcommands][]
+
+### Sentinel Policies
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  will always be non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-nomad-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+### Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+
+### Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+### Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+[Nomad Sentinel Tutorial]: /nomad/tutorials/governance-and-policy/sentinel
+[`nomad sentinel` sub-commands]: /nomad/docs/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L12991-L13020
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L5306-L5338
diff --git a/content/nomad/v1.6.x/content/docs/faq.mdx b/content/nomad/v1.6.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..a9c683b8b6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.6.x/content/docs/glossary.mdx b/content/nomad/v1.6.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..8c2035e7b7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Learn the definition of important Nomad concepts.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.6.x/content/docs/index.mdx b/content/nomad/v1.6.x/content/docs/index.mdx
new file mode 100644
index 0000000000..3296277979
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [Getting Started collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.6.x/content/docs/install/index.mdx b/content/nomad/v1.6.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..ca2f3f86d1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/install/index.mdx
@@ -0,0 +1,311 @@
+---
+layout: docs
+page_title: Install Nomad
+description: Learn how to install Nomad on Linux, Mac, and Windows.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/install/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.6.x/content/docs/install/production/index.mdx b/content/nomad/v1.6.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..2d8e7350d4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.6.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.6.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..559f3ab490
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publically routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup Controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrat
diff --git a/content/nomad/v1.6.x/content/docs/install/quickstart.mdx b/content/nomad/v1.6.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..fb04b6eb39
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via guides containing embedded interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.6.x/content/docs/install/windows-service.mdx b/content/nomad/v1.6.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.6.x/content/docs/integrations/consul-connect.mdx b/content/nomad/v1.6.x/content/docs/integrations/consul-connect.mdx
new file mode 100644
index 0000000000..b07a2deafd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/integrations/consul-connect.mdx
@@ -0,0 +1,393 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/install#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/install#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
diff --git a/content/nomad/v1.6.x/content/docs/integrations/consul-integration.mdx b/content/nomad/v1.6.x/content/docs/integrations/consul-integration.mdx
new file mode 100644
index 0000000000..61414160ee
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/integrations/consul-integration.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and
+install Consul on your nodes alongside Nomad, or schedule it as a system job.
+Nomad does not currently run Consul for you.
+
+To enable Consul integration, please see the
+[Nomad agent Consul integration](/nomad/docs/configuration/consul)
+configuration.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please see the [Automatic Clustering with
+Consul](/nomad/tutorials/manage-clusters/clustering) guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please see the
+[`service` job specification documentation][service].
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template` block](/nomad/docs/job-specification/template)
+that utilizes a Consul ecosystem tool called [Consul Template](https://github.com/hashicorp/consul-template). This mechanism creates a convenient way to ship configuration files
+that are populated from environment variables, Consul data, Vault secrets, or just
+general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul Template,
+please see the [`template` job specification documentation](/nomad/docs/job-specification/template).
+
+## Consul Namespaces
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for service
+registrations specified in `service` blocks and Consul KV reads in `template`
+blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations or
+KV store reads, which Consul then implicitly resolves to the `"default"` namespace.
+This default namespace behavior can be modified by setting the [`namespace`][consul_agent_namespace] field
+in the Nomad agent Consul configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring the
+Consul namespace at the [group level][consul_group_namespace] in the Nomad job spec
+as well as the [`-consul-namespace`][consul_run_namespace] command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations within
+a group, as well as `template` KV store access is determined from the following
+hierarchy from lowest to highest precedence:
+
+- Consul default: If no Consul namespace options are configured, Consul will automatically
+  make use of the `"default"` namespace.
+
+- agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
+  Consul configuration parameter is set, this namespace will be used instead of
+  the Consul default.
+
+- job run command: <EnterpriseAlert inline/> If the [`-consul-namespace`][consul_run_namespace]
+  command line argument is specified on job submission, this namespace will take
+  precedence over the namespace set in Nomad agent configuration.
+
+- group configuration: <EnterpriseAlert inline/> If the [group level][consul_group_namespace]
+  Consul namespace is configured, this namespace will take precedence over all other
+  options.
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
+will control whether a Consul token will be required when submitting a job with
+Consul namespace configured. The provided Consul token must belong to the correct
+namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
+`kv:read` permissions. An example policy might look like,
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+## Assumptions
+
+- Consul 0.7.2 or later is needed for `tls_skip_verify` in HTTP checks.
+
+- Consul 0.6.4 or later is needed for using the Script checks.
+
+- Consul 0.6.0 or later is needed for using the TCP checks.
+
+- The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+- Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+
+[consul]: https://www.consul.io/ "Consul by HashiCorp"
+
+[consul_acls]: /consul/docs/security/acl
+
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+
+[consul_group_namespace]: /nomad/docs/job-specification/group#namespace
+
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
diff --git a/content/nomad/v1.6.x/content/docs/integrations/index.mdx b/content/nomad/v1.6.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.6.x/content/docs/integrations/vault-integration.mdx b/content/nomad/v1.6.x/content/docs/integrations/vault-integration.mdx
new file mode 100644
index 0000000000..9fb9016bec
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/integrations/vault-integration.mdx
@@ -0,0 +1,475 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for
+
+  tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal. Further, Nomad's [`template` block][template] can
+retrieve secrets from Vault making it easier than ever to secure your
+infrastructure.
+
+Note that in order to use Vault with Nomad, you will need to configure and
+install Vault separately from Nomad. Nomad does not run Vault for you.
+
+-> **Note:** Vault integration requires Vault version 0.6.2 or higher.
+
+## Vault Configuration
+
+To use the Vault integration, Nomad servers must be provided a Vault token. This
+token can either be a root token or a periodic token with permissions to create
+from a token role. The root token is the easiest way to get started, but we
+recommend a token role based token for production installations. Nomad servers
+will renew the token automatically. **Note that the Nomad clients do not need to
+be provided with a Vault token.**
+
+-> **Note:** See the [Enterprise specific section][ent] for configuring Vault Enterprise
+
+### Root Token Integration
+
+If Nomad is given a [root
+token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. **Must be set to
+  `true`**. This allows Nomad to renew tokens for tasks.
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+## Agent Configuration
+
+To enable Vault integration, please see the [Nomad agent Vault
+integration][config] configuration.
+
+## Vault Definition Syntax
+
+To configure a job to retrieve Vault tokens, please see the [`vault` job
+specification documentation][vault-spec].
+
+## Troubleshooting
+
+### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+### Permission Denied errors
+
+If you are using a Vault version less than 0.7.1 with a Nomad version greater than or equal to 0.6.1, you will need to update your task's policy (listed in [the `vault` block of the job specification][vault-spec]) to add the following:
+
+```hcl
+path "sys/leases/renew" {
+    capabilities = ["update"]
+}
+```
+
+This is included in Vault's "default" policy beginning with Vault 0.7.1 and is relied upon by Nomad's Vault integration beginning with Nomad 0.6.1. If you're using a newer Nomad version with an older Vault version, your default policy may not automatically include this and you will see "permission denied" errors in your Nomad logs similar to the following:
+
+```plaintext
+Code: 403. Errors:
+URL: PUT https://vault:8200/v1/sys/leases/renew
+* permission denied
+```
+
+### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise 0.12.2 introduced the ability for jobs to use multiple Vault Namespaces.
+There are a few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-cluster` role with each Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a Vault Namespace, but since
+we will be using multiple it can be left blank. By default Nomad will interact with Vault's root Namespace, but individual jobs may specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+  create_from_role      = "nomad-cluster"
+  allow_unauthenticated = false # Disabling allow_unauthenticated is a best practice for securing your cluster
+}
+```
+
+The same steps can be taken to inject a Vault token from the [Retrieving the Token Role based Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+Since [`allow_unauthenticated`][allow_unauth] is set to `false` job submitters will need to provide a sufficiently privileged token when submitting a job.
+
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+
+The example job file below specifies to use the `engineering` Namespace in Vault. It will then read the value at secret/foo and fetch the value for key `bar`
+
+```hcl
+job "vault" {
+  datacenters = ["dc1"]
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        policies  = ["access-kv"]
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+
+```
+
+To submit this job, a token that has the `access-kv` policy in the `engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[createfromrole]: /nomad/docs/configuration/vault#create_from_role 'Nomad vault create_from_role Configuration Flag'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault-spec]: /nomad/docs/job-specification/vault 'Nomad Vault Job Specification'
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[ent]: /nomad/docs/integrations/vault-integration#enterprise-configuration
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.6.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.6.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..b1cd31ebfa
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,284 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment variables
+set for the Nomad client. Inheritence of environment variables can be managed through the [`artifact.set_environment_variables`][client_artifact]
+client configuration.
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.6.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/check.mdx b/content/nomad/v1.6.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..db13448b4f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,471 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_passfail].
+  Only supported in the Consul service provider.
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider. 
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks . Only supported in the Consul
+  service provider.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.6.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.6.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.6.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..f09e253aa7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,322 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.6.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..a0bfa3ac8c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/device.mdx b/content/nomad/v1.6.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..0748bf8ec4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.6.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..af5e905a54
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/env.mdx b/content/nomad/v1.6.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.6.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..dca9fc6523
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.6.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..e709e4c464
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.6.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..30750f46dd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,666 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect Gateways](/consul/docs/connect/gateways). Nomad will
+automatically create the necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries)
+as well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making upstream
+  connections before timing out. Defaults to 5 seconds. If the upstream service has
+  the configuration option <code>[connect_timeout_ms]</code> set for the `service-resolver`, that
+  timeout value will take precedence over this gateway proxy option.
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the gateway
+  services tagged addresses should be bound to listeners in addition to the default
+  listener address.
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A map of additional addresses to be bound.
+  The keys to this map are the same of the listeners to be created and the values are
+  a map with two keys - address and port, that combined make the address to bind the
+  listener to. These are bound in addition to the default address.
+  If `bridge` networking is in use, this map is automatically populated with additional
+  listeners enabling the Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy Documentation](https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery).
+  This option applies to terminating gateways that route to services addressed by a
+  hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners that the
+  ingress gateway should setup, uniquely identified by their port number.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every listener
+  on the gateway. If TLS is enabled, then each host defined in the `host` field will
+  be added as a DNSSAN to the gateway's x509 certificate.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or `grpc`), preconfiguring a [service-default] in Consul to
+  set the [Protocol](/consul/docs/connect/config-entries/service-defaults#protocol)
+  of the service to the desired protocol is mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### `service` Parameters
+
+- `name` `(string: required)` - The name of the service to link with the gateway.
+  If the wildcard specifier `*` is provided, then ALL services within the Consul
+  namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate authority
+  is used to verify the authenticity of the service linked with the gateway. It
+  can be provided along with a `cert_file` and `key_file` for mutual TLS
+  authentication, or on its own for one-way TLS authentication. If none is provided
+  the gateway **will not** encrypt traffic to the destination.
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided to servers
+  to verify the gateway's authenticity. It must be provided if a `key_file` is provided.
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the certificate
+  to verify the gateway's authenticity. It must be provided if a `cert_file` is provided.
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify during
+  the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://www.nomadproject.io/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#service-parameters-1
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[service]: /nomad/docs/job-specification/gateway#service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/group.mdx b/content/nomad/v1.6.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..a64fe83225
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,360 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+### `consul` Parameters
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in which
+  group and task-level services within the group will be registered. Use of
+  `template` to access Consul KV will read from the specified Consul namespace.
+  Specifying `namespace` takes precedence over the [`-consul-namespace`][consul_namespace]
+  command line argument in `job run`.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost". These
+allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' reschedule policy
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements and keep
+the one with the best node score. If the `max_client_disconnect` duration
+expires before the client reconnects, the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+~> **Note:** The `max_client_disconnect` feature is only supported on Nomad
+version 1.3.0 and above. If you run a job with `max_client_disconnect` on servers
+where some servers are not upgraded to 1.3.0, the `max_client_disconnect`
+flag will be _ignored_. Deploying a job with `max_client_disconnect` to a
+`datacenter` of Nomad clients where all clients are not 1.3.0 or above is unsupported.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/group#consul-parameters
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..91ea784340
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..734fbf6589
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..6cf8bcbd89
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..6f964b533f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/integrations/vault-integration">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..667174c8a1
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://nomadproject.io/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "nomadproject.io")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..ab2f14ad6d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..fb820cf5b8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/runtime/environment
+[expression]: /nomad/docs/job-specification/hcl2/expressions
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.6.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..8e0c162d9d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: identity Block - Job Specification
+description: |-
+  The "identity" block allows tasks to use their Nomad Workload Identity via an
+  environment variable or file.
+---
+
+# `identity` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. By default Nomad will create an identity for all
+workloads, but it is *not* exposed to a task.
+
+The following will expose the Workload Identity as an environment variable and
+file to the task:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env  = true
+        file = true
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## `identity` Parameters
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/index.mdx b/content/nomad/v1.6.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..dc0478fb08
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/job.mdx b/content/nomad/v1.6.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..30f3081b1f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.6.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.6.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..bb361fd493
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with reasonable defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/drivers/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.6.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..6f32810932
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## `meta` Usage Examples
+
+### Templates
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.6.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.6.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..f03b42e37d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,290 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/network.mdx b/content/nomad/v1.6.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..cfd6b6094f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,334 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is neccessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.6.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..bf914761dc
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.6.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..ad19c7080d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,119 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions.
+  Conflicts with `cron`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.6.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..9b86faf3c2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and
+  passed directly to Consul. See [Consul Connect documentation](/consul/docs/connect/proxies/envoy#dynamic-configuration)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.6.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.6.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..c01ed11226
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`docker`, `exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][tutorial_quota] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/drivers/docker#cpu
+[exec_cpu]: /nomad/docs/drivers/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[tutorial_quota]: /nomad/tutorials/governance-and-policy/quotas
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.6.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..5b08836657
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,179 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all 
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.6.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/service.mdx b/content/nomad/v1.6.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..22d5cf6d3f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,519 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.6.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..584ef6cf02
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       "test-key" = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.6.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..85736f3215
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.6.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..6fc0455de3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/task.mdx b/content/nomad/v1.6.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..40006df9aa
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,231 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/template.mdx b/content/nomad/v1.6.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..e51d6de389
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,833 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad Integration
+
+### Nomad Services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+~> **Note**: `generate_lease` must be set to `true` (non-default) on the Vault
+PKI role.<br /><br /> Failure to do so will cause the template to frequently
+render a new certificate, approximately every minute. This creates a significant
+number of certificates to be expired in Vault and could ultimately lead to Vault
+performance impacts and failures.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/update.mdx b/content/nomad/v1.6.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..3e1243a165
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.6.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..ef39911d35
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/nomad/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](/consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.6.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..cfe5a1893c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,197 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        policies = ["cdn", "frontend"]
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+"frontend" Vault policy attached.
+
+```hcl
+vault {
+  policies = ["frontend"]
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  policies = ["frontend"]
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private Token and Change Modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  policies    = ["tls-policy", "nomad-job-policy"]
+  change_mode = "noop"
+  env         = false
+  file        = false
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  policies = ["frontend"]
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[docker]: /nomad/docs/drivers/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.6.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..58ec2bd352
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.6.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.6.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..545379bd62
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.6.x/content/docs/networking/cni.mdx b/content/nomad/v1.6.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..0cee27400f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/networking/cni.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: CNI plugins and bridge networking
+description: |-
+  Learn how to install Container Network Interface (CNI) reference plugins, configure Nomad's bridge networking, and how to use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface (CNI)
+
+This page show you how to install the [CNI reference plugins][cni-plugin-docs]
+on your Linux distribution and configure bridge networking on your Nomad
+clients. You can apply this guide's workflow to installing any plugin that
+complies with the [Container Network Interface (CNI) Specification][cni-spec],
+but you should verify plugin compatibility with Nomad before deploying in
+production.
+
+## Introduction
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, [use a CNI network with a
+job](#use-a-cni-network-with-a-job).
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a CNI bridge mode configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration). Refer to
+the external [configuration
+format](https://www.cni.dev/docs/spec/#example-configuration) for a complete
+explanation of the fields.
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode.
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,20,32">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Use a CNI network with a job
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`. Nomad then schedules the workload on client nodes
+that have fingerprinted a CNI configuration with the given name. For example, to
+use the configuration named `mynet`, you should set the task group's network
+mode to `cni/mynet`. Nodes that have a network configuration defining a network
+named `mynet` in their `cni_config_dir` are eligible to run the workload.
+
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.6.x/content/docs/networking/index.mdx b/content/nomad/v1.6.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..4a5aa1c5fd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/networking/index.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Learn about Nomad's networking internals and how it compares with other
+  tools.
+---
+
+# Networking
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+Nomad networking is quite different from what you may familiar with from other
+tools. This section explains how networking works in Nomad, some of the
+different patterns and configurations you are likely to find and use, and how
+Nomad differs from other tools in this aspect.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/concepts/architecture#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/runtime/environment#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#template-examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+### Container Network Interface (CNI) reference plugins
+
+Nomad's bridge network leverages [CNI reference
+plugins](https://github.com/containernetworking/plugins) to provide an
+operating-system agnostic interface to configure workload networking. Nomad's
+network plugin support extends Nomad's built-in compute resource scheduling to
+allow scheduling tasks with specialty network configurations, which Nomad
+implements with a combination of CNI reference plugins and CNI configuration
+files.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/networking/service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/integrations/consul-connect).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/drivers/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/drivers/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/drivers/docker#network_mode)
+documentation and the [Networking](/nomad/docs/drivers/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [Service Discovery](/nomad/docs/networking/service-discovery)
+- [Service Mesh](/nomad/docs/networking/service-mesh)
+- [Container Network Interface](/nomad/docs/networking/cni) plugins guide
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.6.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.6.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..5017babf19
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Learn about how service discovery works in Nomad to connect workloads.
+---
+
+# Service discovery
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.6.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.6.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2828748c9f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Learn about how service mesh works in Nomad to securely connect and isolate
+  your workloads.
+---
+
+# Service mesh
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.6.x/content/docs/operations/index.mdx b/content/nomad/v1.6.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.6.x/content/docs/operations/key-management.mdx b/content/nomad/v1.6.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..2f8b92165f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers store key metadata in raft, but
+the encryption key material is stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Replication
+
+When a leader is elected, it creates the keyring if it does not already
+exist. When a key is added, the metadata will be replicated via raft. Each
+server runs a key replication process that watches for changes to the state
+store and will fetch the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election.
+
+## Restoring the Keyring from Backup
+
+Key material is never stored in raft. This prevents an attacker with a backup of
+the state store from getting access to encrypted variables. It also allows the
+HashiCorp engineering and support organization to safely handle cluster
+snapshots you might provide without exposing any of your keys or variables.
+
+However, this means that to restore a cluster from snapshot you need to also
+provide the keystore directory with the `.nks.json` key files on at least one
+server. The `.nks.json` key files are unique per server, but only one server's
+key files are needed to recover the cluster. Operators should include these
+files as part of your organization's backup and recovery strategy for the
+cluster.
+
+If you are recovering a Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
diff --git a/content/nomad/v1.6.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.6.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..fbde44487c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,510 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`             | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`             | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                         | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                    | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                   | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`            | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`            | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`         | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://nomadproject.io/s/port-plan-failure
diff --git a/content/nomad/v1.6.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.6.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..6dd813a86c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://www.nomadproject.io/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.6.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.6.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..474eed327e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,188 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+By default, any stop signal to an agent (interrupt or terminate) will cause the
+agent to exit after ensuring its internal state is committed to disk as
+needed. You can configuration additonal behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when `leave_on_interrupt` or `leave_on_terminate` are set the
+server will notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there will be a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, the [`server
+force-leave` command][] should be used to eject it from the consensus peer set.
+
+For clients, when `leave_on_interrupt` or `leave_on_terminate` are set and the
+client is configured with [`drain_on_shutdown`][], the client will drain its
+workloads before shutting down.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.6.x/content/docs/operations/stateful-workloads.mdx b/content/nomad/v1.6.x/content/docs/operations/stateful-workloads.mdx
new file mode 100644
index 0000000000..d8ecf7db08
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/operations/stateful-workloads.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Portworx or Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. More information can be found on the CSI
+concepts [documentation page](/nomad/docs/concepts/plugins/csi).
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+Host volumes mount paths from the host (the Nomad client) into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+backed by a distributed networked storage such as GlusterFS, or a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore
+you can use host volumes for both local somewhat persistent storage and for
+highly persistent networked storage.
+
+Because you need to declare host volumes in the Nomad agent's configuration
+file, you must restart the Nomad client to reconfigure them. This makes host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/concepts/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add/update/remove host volumes to make them available for
+consumption by Nomad Operators. Or, with networked host volumes, a Storage
+Administrator will need to provision the volumes and make them available to the
+Nomad clients. A System Administrator will then mount them on the Nomad clients.
+
+Host volumes backed by local storage help persist data that is not critical, for
+example an on-disk cache that can be rebuilt if needed. When backed by networked
+storage such as NFS/CIFS-mounted volumes or distributed storage via
+GlusterFS/Ceph, host volumes provide a quick option to consume highly available
+and reliable storage.
+
+Refer to the [Stateful workloads with Nomad host
+volumes](/nomad/tutorials/stateful-workloads/stateful-workloads-host-volumes)
+tutorial to learn more about using host volumes with Nomad.
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/tutorials/integrate-nomad/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/concepts/plugins/csi)
+- [Nomad CSI
+  tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [Portworx on
+  Nomad](https://docs.portworx.com/portworx-enterprise/install-portworx/install-with-other/nomad#operate-and-utilize-portworx-on-nomad)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..d94a1e5bf9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,497 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node Pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..cea2206404
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: Namespace Specification
+description: Learn about Nomad's Namespace specification.
+---
+
+# Namespace Specification
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+
+Nomad Namespaces may be specified as HCL files and submitted by the [`nomad
+namespace apply`][cli_ns_apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Namespace specifications do *not*
+support [HCL2][hcl2] features like functions.
+
+In [federated][] clusters, all updates to namespaces are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers  = ["java", "docker"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+```
+
+## Namespace Specification Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+### `capabilities` Parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+### `node_pool_config` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs in
+  this namespace that don't define a node pool in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that are allowed
+  to be used by jobs in this namespace. By default, all node pools are allowed.
+  If an empty list is provided only the namespace's default node pool is
+  allowed. This field supports wildcard globbing through the use of `*` for
+  multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any node pool is allowed to be used, except for those that match any of these
+  patterns. This field cannot be used with `allowed`.
+
+[cli_ns_apply]: /nomad/docs/commands/namespace/apply
+[hcl2]: /nomad/docs/job-specification/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..f3ed362191
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Nomad Node Pool Specification
+description: Learn about Nomad's Node Pool specification.
+---
+
+# Nomad Node Pool Specification
+
+Nomad node pools may be specified as HCL files and submitted by the [`nomad node
+pool apply`][pool-apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad node pool specifications do *not*
+support HCL2 features like functions.
+
+Example node pool specification generated by [`nomad node pool
+init`][pool-init]:
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/docs/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Node Pool Specification Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` Parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/docs/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/docs/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..5422693c69
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Only allowed on **volume creation**.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**. Note that, like the rest of the volume specification, 
+  this block is declarative, and an update replaces it in its entirety, therefore 
+  all parameters need to be specified.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), [`clone_id`](#clone_id),
+[`capacity_min`](#capacity_min), or [`capacity_max`](#capacity_max) fields on
+**volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, so long as the
+  volumes existing capacity fits within that range. The actual capacity of the
+  volume is unchanged.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.6.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.6.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.6.x/content/docs/partnerships.mdx b/content/nomad/v1.6.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..b8c95e0b93
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. See the [Introduction](/nomad/intro) page for a full description of the current features. The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.6.x/content/docs/runtime/environment.mdx b/content/nomad/v1.6.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..a765f8a3b0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Prior to Nomad 0.5.5 the key was
+uppercased and since then both the original case and an uppercased version are
+injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.6.x/content/docs/runtime/index.mdx b/content/nomad/v1.6.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..86b05c6076
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details Nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.6.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.6.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..d2132a56a0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,202 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/drivers/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/drivers/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.6.x/content/docs/schedulers.mdx b/content/nomad/v1.6.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..7eb58f3d53
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/schedulers.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.6.x/content/docs/upgrade/index.mdx b/content/nomad/v1.6.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..aee9627e30
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/docs/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.6.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.6.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..abc7f15047
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,1934 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.6.4, 1.5.11
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.6.4 and 1.5.11 change the behavior of the [`distinct_hosts`][]
+constraint such that namespaces are taken into account when choosing feasible
+clients for allocation placement. The previous, less-expected behavior would
+cause **any** job with the same name running on a client to cause that node to
+be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`][]
+constraint over [`${node.pool}`][node_attributes].
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration][allow_caps_exec]:
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task][cap_add_exec] that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide][hard_guide]
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock] capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`][artifact_params]
+and [`headers`][artifact_params] fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`][artifact_env].
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`][artifact_fs_isolation].
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`][decompression_size_limit] and
+[`decompression_file_count_limit`][decompression_file_count_limit].
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`] configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`consul.allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`distinct_hosts`]: /nomad/docs/job-specification/constraint#distinct_hosts
+[`distinct_property`]: /nomad/docs/job-specification/constraint#distinct_property
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[`log_file`]: /nomad/docs/configuration#log_file
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`rejoin_after_leave`]: /nomad/docs/configuration/server#rejoin_after_leave
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[`vault.allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault.policies`]: /nomad/docs/job-specification/vault#policies
+[`vault.task_token_ttl`]: /nomad/docs/configuration/vault#task_token_ttl
+[`vault.token`]: /nomad/docs/configuration/vault#token
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[artifact_params]: /nomad/docs/job-specification/artifact#artifact-parameters
+[artifacts]: /nomad/docs/job-specification/artifact
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[cores]: /nomad/docs/job-specification/resources#cores
+[cpu]: /nomad/docs/concepts/cpu
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[enterprise licensing]: /nomad/docs/enterprise/license
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
+[hcl2]: https://github.com/hashicorp/hcl2
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[migrate]: /nomad/docs/job-specification/migrate
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul-integration#migrating-to-using-workload-identity-with-consul
+[Migrating to Using Workload Identity with Vault]: /nomad/docs/integrations/vault-integration#migrating-to-using-workload-identity-with-vault
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[node pools]: /nomad/docs/concepts/node-pools
+[node_attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[nvidia]: /nomad/plugins/devices/nvidia
+[pki]: /vault/docs/secrets/pki
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[pki]: /vault/docs/secrets/pki
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[enterprise licensing]: /nomad/docs/enterprise/license
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[`log_file`]: /nomad/docs/configuration#log_file
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.6.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.6.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..b7aeefd95e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.6.x/content/intro/index.mdx b/content/nomad/v1.6.x/content/intro/index.mdx
new file mode 100644
index 0000000000..44757a5182
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.6.x/content/intro/use-cases.mdx b/content/nomad/v1.6.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..7082888c5d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.6.x/content/intro/vs/ecs.mdx b/content/nomad/v1.6.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.6.x/content/intro/vs/index.mdx b/content/nomad/v1.6.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.6.x/content/intro/vs/mesos.mdx b/content/nomad/v1.6.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.6.x/content/intro/vs/terraform.mdx b/content/nomad/v1.6.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.6.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.6.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.6.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.6.x/content/partials/envvars.mdx b/content/nomad/v1.6.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..d79b69159a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/envvars.mdx
@@ -0,0 +1,68 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                     |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                     |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                       |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                       |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                 |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                           |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                   |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                       |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                          |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index. |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                     |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                    |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                   |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                      |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                            |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                   |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                     |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                    |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                       |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata.                                                                    |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                       |
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/runtime/environment#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/integrations/vault-integration
diff --git a/content/nomad/v1.6.x/content/partials/general_options.mdx b/content/nomad/v1.6.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.6.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.6.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.6.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.6.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.6.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.6.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..bb25000698
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/install/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.6.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.6.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..d916ba11e6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,23 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.5.1
+release](https://github.com/containernetworking/plugins/releases/tag/v1.5.1),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.5.1
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.6.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.6.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.6.x/content/partials/install/manual-install.mdx b/content/nomad/v1.6.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.6.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.6.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.6.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.6.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.6.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.6.x/content/plugins/devices/index.mdx b/content/nomad/v1.6.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.6.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.6.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..a73e98adb7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..5aa129c9cd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/firecracker-microvm/firecracker-go-sdk/tree/master/cni
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..cc8e59b489
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pledge][pledge]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[rkt]: /nomad/plugins/drivers/community/rkt
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
+[pledge]: /nomad/plugins/drivers/community/pledge
+
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..3a0a46f932
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionaly, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..0bc5c66b99
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/pledge.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/pledge.mdx
new file mode 100644
index 0000000000..93925d0309
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/pledge.mdx
@@ -0,0 +1,332 @@
+---
+layout: docs
+page_title: 'Drivers: Pledge'
+description: The Pledge task driver is capable of blocking unwanted syscall and filesystem access.
+---
+
+# Pledge Driver
+
+Name: `pledge`
+
+The `pledge` driver executes programs similar to `exec` or `raw_exec`, but
+provides sandboxing by restricting syscalls the process is allowed to make.
+The `pledge` driver uses the [Landlock LSM][landlock] to restrict filesystem
+access, which can be significantly more efficient than creating a `chroot`.
+Isolation of CPU and memory resources is provided by leveraging features of
+cgroups v2. Network, PID, and IPC isolation is powered by Linux namespaces.
+
+Source on [GitHub][repository]
+
+Downloads on GitHub [releases][releases]
+
+#### Use cases
+
+The `pledge` driver is intended as a replacement for `raw_exec`. Sometimes
+there are those management tasks that just need to be run as `root` and directly
+access the filesystem or perform privileged operations. While `raw_exec`
+provides no isolation, the `pledge` driver uses Landlock to restrict the files
+or directories the task is allowed to access and modify. Specific groups of
+system calls are allow-listed in the task configuration, greatly reducing the
+attack surface of a mis-configured or compromised task.
+
+#### About
+
+The `pledge` driver is fundamentally powered by the [pledge utility for Linux]
+[pledge] by Justine Tunney. The driver invokes this `pledge.com` CLI tool along
+with `nsenter` and `unshare` to create a strict sandbox in which to execute a
+given command.
+
+## Task Configuration
+
+```hcl
+task "http" {
+  driver = "pledge"
+  config {
+    command    = "python3"
+    args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+    promises   = "stdio rpath inet"
+    unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+  }
+}
+```
+
+The `pledge` driver supports the following task configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. The driver will search
+  for the command on the `$PATH` of the Nomad Client unless an absolute path
+  is given.
+
+- `args` - (Optional) A list of arguments to the `command`. References to
+  environment variables or any interpolable Nomad variables will be interpolated
+  before launching the task.
+
+- `promises` - A set of promises needed for the command to run. See below for
+  more information.
+
+- `unveil` - (Optional) A list of filepaths and access rights to grant to the
+  command. See below for more information.
+
+- `importance` - (Optional) One of `"lowest"`, `"low"`, `"normal"`, `"high"`,
+  `"highest"`. Indicates the `nice` value with which to run `command` (default
+  is `"normal"`). A lower importance indicates the command should be given a
+  lower priority with regard to CPU time relative to other tasks.
+
+## Syscall Isolation (promises)
+
+When using the `pledge` task driver, by default most syscalls will become
+unavailable. A process that attempts to use an unavailable syscall will receive
+an `EPERM` error from the kernel. By specifying a set of `promises`, additional
+syscalls will be made available to the `command`.
+
+See the complete documetation for [promises][promises].
+
+| Promise | Description |
+| ------- | ------------|
+| `stdio` | allow stdio, threads, and benign system calls |
+| `rpath` | allow filesystem read operations |
+| `wpath` | allow filesystem write operations |
+| `cpath` | allow filesystem create operations |
+| `dpath` | allow creation of special files |
+| `flock` | allow file locking |
+| `tty` | allow terminal ioctls |
+| `recvfd` | allow recvmsg |
+| `sendfd` | allow sendmsg |
+| `fattr` | allow changing some struct stat bits |
+| `inet` | allow IPv4 and IPv6 |
+| `unix` | allow using Unix Domain Sockets |
+| `dns` | allow DNS |
+| `proc` | allow fork process creation and control |
+| `id` | allow setuid and friends |
+| `exec` | allow executing binaries |
+| `prot_exec` | allow creating executable memory |
+| `vminfo` | allow operations around reading `/proc` |
+| `tmppath` | allow access to `/tmp` |
+
+## Filesystem Isolation (unveil)
+
+By default the `command` will not be able to access the filesystem. Using some
+promises will implicitly allow access to specific parts of the filesystem where
+applicable. The `unveil` configuration is used to grant access to additional
+filesytem paths at a specified permission level.
+
+The format of the `unveil` parameter is a list of paths and associated
+permissions. Permissions can be any combination of `r`, `w`, `c` and `x` for
+read, write, create and execute privileges.
+
+Note that reading a file also requires the `rpath` promise, writing a file
+requires the `wpath` promise, creating a file requires the `cpath` promise, and
+executing a program requires the `exec` promise.
+
+#### Examples
+
+This example allows reading of the `/srv/www` directory.
+
+```hcl
+unveil = ["r:/srv/www"]
+```
+
+This example allows executing `/opt/bin/program` and reading `/etc/prog.d`.
+
+```hcl
+unveil = ["x:/opt/bin/program", "r:/etc/prog.d"]
+```
+
+It can be useful to `unveil` the Nomad Task Directory, which can be done by
+specifying the interpolation value.
+
+```hcl
+unveil = ["rwc:${NOMAD_TASK_DIR}"]
+```
+
+## Networking
+
+The `pledge` driver supports `none`, `host`, and `group` networking modes.
+
+#### host networking
+
+If using `host` networking mode, it can be very convenient to bless the
+[pledge][pledge] utility with the `cap_net_bind_service` Linux capability. This will
+enable Nomad tasks using the pledge driver to bind to privileged ports (i.e.
+below 1024) while using host networking mode.
+
+```shell-session
+sudo setcap cap_net_bind_service+eip /opt/bin/pledge-1.8.com
+```
+
+For convenience the `driver.pledge.cap.net_bind` Client attribute will indicate
+whether the Linux capability is set on the executable.
+
+#### bridge networking
+
+If using `bridge` networking mode, be sure to install the standard [CNI plugins]
+[cni] as required by the Nomad client.
+
+## Client Requirements
+
+The `pledge` driver requires the following:
+
+- 64-bit amd64 Linux host
+  - kernel version 5.13+
+  - cgroups v2 enabled
+- The `pledge` driver binary placed in [plugin_dir][plugin_dir]
+- The `pledge.com` utility executable on the host
+
+## Plugin Options
+
+- `pledge_executable` - The path to the `pledge.com` binary. The pledge utility
+can be [downloaded][download] directly from its creator, or compiled manually
+from [source][pledge_github].
+
+```hcl
+plugin "nomad-pledge-driver" {
+  config {
+    pledge_executable = "/opt/bin/pledge-1.8.com"
+  }
+}
+```
+
+## Client Attributes
+
+The `pledge` driver will set the following Client attributes:
+
+| Attribute | Description |
+| ----------| ----------- |
+| `driver.pledge` | set to `1` if the driver is enabled |
+| `driver.pledge.abs` | the absolute path to the pledge.com utility |
+| `driver.pledge.cap.net_bind` | indicates whether the NET_BIND linux capability is set |
+| `driver.pledge.os` | the detected operating system |
+
+## Resource Isolation
+
+CPU and memory resource isolation is enforced by cgroups v2 features, and is
+configured through the resources block in task configuration.
+
+```hcl
+resources {
+  cores  = 3
+  memory = 512
+}
+```
+
+#### cpu bandwidth
+
+The `pledge` driver always enforces a maximum CPU bandwidth available to the
+task. The bandwidth is calculated whether `resources.cpu` or `resources.cores`
+is configured.
+
+If `resources.cores` is set, the scheduler reserves that many CPU cores for use
+by the task, and only this task will be able to run on those cores.
+
+#### memory oversubscription
+
+If the Nomad scheduler is configured to enable memory [oversubscription]
+[oversub], the `pledge` driver will enable configuring `memory_max` in addition
+to `memory`. In this case, `memory_max` indicates the maximum amount of memory
+the task is able to request before being OOM killed, and `memory` represents a
+minimum amount of memory the kernel will guarantee is available for the Task.
+
+```hcl
+resources {
+  cpu        = 2000
+  memory     = 1024
+  memory_max = 2048
+}
+```
+
+## Capabilities
+
+The `pledge` driver implements the following [capabilities][capabilities].
+
+| Feature              | Implementation    |
+| ------------         | ------------------|
+| send signals         | true              |
+| exec                 | false             |
+| filesystem isolation | none (landlock)   |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+For sending signals, use the `nomad alloc signal` command.
+
+## Examples
+
+A larger set of examples are available in the [source][hack] repository.
+
+Showing how to `curl example.com`.
+
+```hcl
+job "curl" {
+  type = "batch"
+  group "group" {
+    task "curl" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command  = "curl"
+        args     = ["example.com"]
+        promises = "stdio rpath inet dns sendfd"
+      }
+    }
+  }
+}
+```
+
+An example using the Python built-in HTTP server to render a trivial web page.
+
+```hcl
+job "http" {
+  group "group" {
+    network {
+      mode = "host"
+      port "http" { static = 8181 }
+    }
+
+    task "task" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command    = "python3"
+        args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+        promises   = "stdio rpath inet"
+        unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+      }
+
+      template {
+        destination = "local/index.html"
+        data        = <<EOH
+<!doctype html>
+<html>
+  <title>example</title>
+  <body><p>Hello, friend!</p></body>
+</html>
+EOH
+      }
+    }
+  }
+}
+```
+
+## Troubleshooting
+
+When setting up a new Task using the `nomad-pledge-driver` task driver, it
+helps to run the command manually using the `pledge` utility to make sure the
+necessary promises and unveil paths are well understood. To figure out which
+syscalls process needs to make, it can be run under `strace -ff`. When a syscall
+is blocked, you'll see `"EPERM (Operation not permitted)"`
+
+```shell-session
+strace -ff /opt/bin/pledge-1.8.com -p "stdio rpath inet" -- curl example.com
+```
+
+[capabilities]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[cni]: https://developer.hashicorp.com/nomad/docs/install
+[download]: https://justine.lol/pledge/#download
+[hack]: https://github.com/shoenig/nomad-pledge-driver/tree/main/hack
+[landlock]: https://docs.kernel.org/security/landlock.html
+[oversub]: https://developer.hashicorp.com/nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
+[pledge]: https://justine.lol/pledge/
+[pledge_github]: https://github.com/jart/pledge
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[promises]: https://justine.lol/pledge/#promises
+[repository]: https://github.com/shoenig/nomad-pledge-driver
+[releases]: https://github.com/shoenig/nomad-pledge-driver/releases
+
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..dfbb3dfb11
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:7"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /nomad/docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.6.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/index.mdx b/content/nomad/v1.6.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.6.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..2b9d4685c7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,590 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+Download from HashiCorp [releases][releases]
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting tlsVerify to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tlsVerify = false
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
\ No newline at end of file
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.6.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..b4346bd020
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accomodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.6.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.6.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..52c652d745
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]: /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.6.x/content/plugins/index.mdx b/content/nomad/v1.6.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..87d3059efd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.6.x/content/security.mdx b/content/nomad/v1.6.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.6.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..6d2ae9d188
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. A future version will include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..ca630dff4c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..01be84617b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..5340d70b45
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..f10a2e47e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+The `pass-through` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..13ef0a2aab
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..b8b626e869
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above
+`lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d91143a086
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM availible for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..a702f00bde
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..7bf2dbc6d7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+
+[client_meta_tag]: #client-meta-tag
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..f7df5bd0e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..4dcd9f28c2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,252 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.6.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.6.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..9113f451e7
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td></td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.6.x/content/tools/index.mdx b/content/nomad/v1.6.x/content/tools/index.mdx
new file mode 100644
index 0000000000..88d35fbbb2
--- /dev/null
+++ b/content/nomad/v1.6.x/content/tools/index.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+- [OpenAPI](https://github.com/hashicorp/nomad-openapi) - An OpenAPI/Swagger spec for Nomad, allowing for programmatic generation of SDKs and documentation. Includes a reference implementation in Go built on top of a generated client.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.6.x/data/api-docs-nav-data.json b/content/nomad/v1.6.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..c886c66f13
--- /dev/null
+++ b/content/nomad/v1.6.x/data/api-docs-nav-data.json
@@ -0,0 +1,194 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "path": "variables"
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.6.x/data/docs-nav-data.json b/content/nomad/v1.6.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..0cb34722f6
--- /dev/null
+++ b/content/nomad/v1.6.x/data/docs-nav-data.json
@@ -0,0 +1,2299 @@
+[
+  {
+    "title": "Install Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "path": "integrations/consul-integration"
+      },
+      {
+        "title": "Consul Service Mesh",
+        "path": "integrations/consul-connect"
+      },
+      {
+        "title": "Vault Integration",
+        "path": "integrations/vault-integration"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "ACL",
+        "path": "concepts/acl"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Node Pools",
+        "path": "concepts/node-pools"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "auth-method",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/auth-method/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/auth-method/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/auth-method/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/auth-method/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/auth-method/update"
+              }
+            ]
+          },
+          {
+            "title": "binding-rule",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/binding-rule/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/binding-rule/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/binding-rule/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/binding-rule/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/binding-rule/update"
+              }
+            ]
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "checks",
+            "path": "commands/alloc/checks"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "restart",
+            "path": "commands/job/restart"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/license/inspect"
+          }
+        ]
+      },
+      {
+        "title": "login",
+        "path": "commands/login"
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "meta",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "commands/node/meta"
+              },
+              {
+                "title": "apply",
+                "path": "commands/node/meta/apply"
+              },
+              {
+                "title": "read",
+                "path": "commands/node/meta/read"
+              }
+            ]
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "node pool",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node-pool"
+          },
+          {
+            "title": "apply",
+            "path": "commands/node-pool/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/node-pool/delete"
+          },
+          {
+            "title": "info",
+            "path": "commands/node-pool/info"
+          },
+          {
+            "title": "init",
+            "path": "commands/node-pool/init"
+          },
+          {
+            "title": "jobs",
+            "path": "commands/node-pool/jobs"
+          },
+          {
+            "title": "list",
+            "path": "commands/node-pool/list"
+          },
+          {
+            "title": "nodes",
+            "path": "commands/node-pool/nodes"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              }
+            ]
+          },
+          {
+            "title": "client-state",
+            "path": "commands/operator/client-state"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node Pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "href": "/plugins/drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      },
+      {
+        "title": "Considerations for Stateful Workloads",
+        "path": "operations/stateful-workloads"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      },
+      {
+        "title": "Sentinel",
+        "path": "enterprise/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.6.x/data/intro-nav-data.json b/content/nomad/v1.6.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..0fdab4c70f
--- /dev/null
+++ b/content/nomad/v1.6.x/data/intro-nav-data.json
@@ -0,0 +1,31 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "href": "https://developer.hashicorp.com/nomad/tutorials/get-started"
+  }
+]
diff --git a/content/nomad/v1.6.x/data/plugins-nav-data.json b/content/nomad/v1.6.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..f51bf50a29
--- /dev/null
+++ b/content/nomad/v1.6.x/data/plugins-nav-data.json
@@ -0,0 +1,121 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "path": "drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.6.x/data/tools-nav-data.json b/content/nomad/v1.6.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..51a278df1f
--- /dev/null
+++ b/content/nomad/v1.6.x/data/tools-nav-data.json
@@ -0,0 +1,227 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.6.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.6.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.6.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.6.x/img/autoscaling/control-loop.png b/content/nomad/v1.6.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.6.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.6.x/img/autoscaling/policy-eval.png b/content/nomad/v1.6.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.6.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.6.x/img/count-dashboard.png b/content/nomad/v1.6.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.6.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.6.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.6.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.6.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/favicon-16x16.png b/content/nomad/v1.6.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/favicon-194x194.png b/content/nomad/v1.6.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/favicon-32x32.png b/content/nomad/v1.6.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/favicon.ico b/content/nomad/v1.6.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.6.x/img/favicons/mstile-144x144.png b/content/nomad/v1.6.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/mstile-150x150.png b/content/nomad/v1.6.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/mstile-310x150.png b/content/nomad/v1.6.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/mstile-310x310.png b/content/nomad/v1.6.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/mstile-70x70.png b/content/nomad/v1.6.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.6.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.6.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.6.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.6.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.6.x/img/home-hero-pattern.svg b/content/nomad/v1.6.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.6.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/img/logo-hashicorp.svg b/content/nomad/v1.6.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.6.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.6.x/img/logo-text.svg b/content/nomad/v1.6.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.6.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.6.x/img/networking/bridge.png b/content/nomad/v1.6.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.6.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.6.x/img/networking/docker_bridge.png b/content/nomad/v1.6.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.6.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.6.x/img/networking/port_mapping.png b/content/nomad/v1.6.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.6.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-architecture-global.png b/content/nomad/v1.6.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-architecture-region.png b/content/nomad/v1.6.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-bg-pattern.svg b/content/nomad/v1.6.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.6.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.6.x/img/nomad-bridge-network.png b/content/nomad/v1.6.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-data-model.png b/content/nomad/v1.6.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-evaluation-flow.png b/content/nomad/v1.6.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-kubernetes.png b/content/nomad/v1.6.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.6.x/img/nomad-panel-learn.svg b/content/nomad/v1.6.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.6.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.6.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.6.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.6.x/img/nomad-workload.png b/content/nomad/v1.6.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.6.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.6.x/img/og-image.png b/content/nomad/v1.6.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.6.x/img/og-image.png differ
diff --git a/content/nomad/v1.6.x/img/pattern.svg b/content/nomad/v1.6.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.6.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/img/practice-pattern.svg b/content/nomad/v1.6.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.6.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/img/usecase-callout-pattern.svg b/content/nomad/v1.6.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.6.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/img/usecase-hero-pattern.svg b/content/nomad/v1.6.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.6.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.6.x/redirects.jsonc b/content/nomad/v1.6.x/redirects.jsonc
new file mode 100644
index 0000000000..b3932a00d2
--- /dev/null
+++ b/content/nomad/v1.6.x/redirects.jsonc
@@ -0,0 +1,48 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: MPL-2.0
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+  // Rename and re-arrange Autoscaling Internals section
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.7.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..56d503378a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,510 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+  The name can contain alphanumeric characters and dashes. This name must be
+  unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and `JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either `local` or `global`.
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL `${foo}` syntax.
+  Defaults to `${auth_method_type}-${auth_method_name}`.
+
+ - `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set, it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+    any `.well-known` component (base path). Required for `OIDC` method type.
+    Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+    `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+    your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+    configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+    to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+    `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+    signatures. Either this, the `JWTValidationPubKeys` or the
+    `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+    to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+    validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+    validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+    validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Names is the identifier of the ACL auth
+  method.  The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth role SSO identifier. Currently, the
+  only supported Type is "OIDC."
+
+- `TokenLocality` `(string: "")` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either "local" or "global"
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL '${foo}' syntax.
+  Defaults to '${auth_method_type}-${auth_method_name}'
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL auth method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: nil)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: "")` - The OIDC discovery URL, without
+    any .well-known component (base path).
+
+  - `OIDCClientID` `(string: "")` - The OAuth client ID configured with
+    your OIDC provider.
+
+  - `OIDCClientSecret` `(string: "")` - The OAuth client secret
+    configured with your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.7.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..93451a8704
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `POST` | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/index.mdx b/content/nomad/v1.7.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..318f42b704
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/login.mdx b/content/nomad/v1.7.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.7.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.7.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..4e07722b8c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,188 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given
+  namespace, job, group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - The namespace to attach the policy.
+    Required if `JobID` is set.
+
+  - `JobID` `(string: <optional>)` - The job to attach to the policy. Required
+    if `Group` is set.
+
+  - `Group` `(string: <optional>)` - The group to attach to the policy.
+    Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - The task to attach to the policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.7.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..b19dca9930
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `POST` | `/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                 | Produces       |
+| -------- | -------------------- | -------------- |
+| `DELETE` | `/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.7.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..9d81cee9c9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.7.x/content/api-docs/agent.mdx b/content/nomad/v1.7.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..0331407b2b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.7.x/content/api-docs/allocations.mdx b/content/nomad/v1.7.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..5176a3b38c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/allocations.mdx
@@ -0,0 +1,961 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.7.x/content/api-docs/client.mdx b/content/nomad/v1.7.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..b58244ad26
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.7.x/content/api-docs/deployments.mdx b/content/nomad/v1.7.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/evaluations.mdx b/content/nomad/v1.7.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..2984cdaf1e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.7.x/content/api-docs/events.mdx b/content/nomad/v1.7.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..e99bf630d7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/events.mdx
@@ -0,0 +1,391 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `NodePool`   | `management`         |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| NodePool   | NodePool                        |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| NodePoolUpserted              |
+| NodePoolDeleted               |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/index.mdx b/content/nomad/v1.7.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..30fe4109cf
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/index.mdx
@@ -0,0 +1,731 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter. Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+Here is an example using curl to query the `qa` namespace:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=qa'
+```
+
+Use a wildcard (`*`) to query all namespaces:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=*'
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> \
+    --data-urlencode 'filter=<filter expression>'
+```
+
+The filter expression can also be specified in the
+[`-filter`][cli_operator_api_filter] flag of the
+[`nomad operator api`][cli_operator_api] command.
+
+```shell-session
+$ nomad operator api -filter '<filter expression>' /v1/<path>
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### List Stubs
+
+Some list endpoints return a reduced version of the resource being queried.
+This smaller version is called a _stub_ and may have different fields than the
+full resource definition. To allow more expressive filtering operations, the
+filter is applied to the full version, not the stub.
+
+If a request returns an error such as `error finding value in datum` the field
+used in filter expression may need to be adjusted. For example, filtering on
+node addresses should use the `HTTPAddr` field of the full node definition
+instead of `Address` field present in the stub.
+
+```shell-session
+$ nomad operator api -filter 'HTTPAddr matches "10.0.0..+"' /v1/nodes
+```
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Datacenters contains "dc2"' /v1/jobs
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Status != "successful"' /v1/deployments
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
+
+[cli_operator_api]: /nomad/docs/commands/operator/api
+[cli_operator_api_filter]: /nomad/docs/commands/operator/api#filter
diff --git a/content/nomad/v1.7.x/content/api-docs/jobs.mdx b/content/nomad/v1.7.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..fa22ba4bef
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2675 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2`, `hcl1`, or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `IdempotencyToken` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling operation.
+  Must contain a field `Group` with the name of the task group that is the target of this scaling action.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates information or reason for scaling; one of `Message` or `Error` must be provided.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as part of the scaling event.
+  Indicates an error state preventing scaling; one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be scaled when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## List Job Actions
+
+This endpoint lists the actions available to tasks within a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/actions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/job/my-job/actions'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Args": [
+      "-s",
+      "wttr.in/Toronto?format=3"
+    ],
+    "Command": "/usr/bin/curl",
+    "Name": "weather",
+    "TaskGroupName": "group1",
+    "TaskName": "task"
+  },
+  {
+    "Args": [
+      "-c",
+      "nomad alloc status ${NOMAD_ALLOC_ID}"
+    ],
+    "Command": "/bin/sh",
+    "Name": "get-alloc-info",
+    "TaskGroupName": "group2",
+    "TaskName": "task"
+  },
+]
+```
+
+## Run Action
+
+This endpoint executes a predefined action from a job in the
+context of a specific task within an allocation. It opens a WebSocket to
+transmit output from the running action.
+
+
+| Method      | Path                     | Produces               |
+| ----------- | ------------------------ | ---------------------- |
+| `WebSocket` | `/v1/job/:job_id/action` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if task driver does not support [file system isolation](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error)) |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job containing the
+  action. This is specified as part of the path.
+- `action` `(string: <required>)` - Specifies the name of the action to be
+  executed, as defined within the job's task. Specified as a query parameter.
+- `alloc_id` `(string: <required>)` - Specifies the UUID of the target
+  allocation. Specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task where the action is
+  defined. Specified as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this action.
+  Specified as a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the
+  authentication token in the first frame, as a query parameter.
+
+### WebSocket Upgrade Request
+
+Actions are executed with a WebSocket upgrade request. The request headers
+must include the standard WebSocket upgrade parameters. Example:
+
+```shell-session
+$ curl \
+  -X GET \
+  -H 'Connection: Upgrade' \
+  -H 'Upgrade: websocket' \
+  -H 'Sec-Websocket-Version: 13' \
+  -H 'Sec-Websocket-Key: x3JJHMbDL1EzLkh9GBhXDw==' \
+  'http://127.0.0.1:4646/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+or
+```shell-session
+$ nomad operator api \
+-H "Connection: Upgrade" \
+-H "Upgrade: websocket" \
+-H "Sec-WebSocket-Version: 13" \
+-H "Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==" \
+'/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+
+### Request Frames
+
+Unlike [alloc exec](/nomad/api-docs/allocations#exec-allocation), Actions do
+not take input in the form of request frames using `stdin`. Instead, the name
+of the action is passed as a query parameter and the associated input is handled
+on the allocation apart from the stream.
+
+When `?ws_handshake=true`, the first request frame must contain the
+authentication token. Similarly, when `?tty=true`, a `tty_size` frame may be
+provided to indicate a resize.
+
+The following are valid input frames:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well
+as exit codes. Response frames encompass the full range of terminal emulator outputs, including
+the control characters necessary to render interactive applications.
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+{"exited":true,"result":{}}
+```
+
+The stdout data returned in the response frames from the job action endpoint is
+base64 encoded. This encoding is necessary to ensure that the data can be
+transmitted over WebSocket connections without issues, regardless of its content.
+
+### Sample Request and Response
+
+This example response includes instances of the ANSI "control sequence
+introducer" (CSI), which is ASCII code 27 followed by `[`. The second stdout
+frame includes the desired output from the Action in question, which prints
+the local weather.
+
+```
+# Sample WebSocket request to execute an action
+WebSocket Request: /v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+
+# Toronto: ⛅️  -1°C
+{"stdout":{"data":"VG9yb250bzog4puF77iPICAtMcKwQw0K"}}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.7.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..f35168cb02
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1221 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. This setting is supported in Docker since
+    Nomad 0.6 and rkt since Nomad 0.7. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Added in
+      Nomad 0.7.1. Unlike `PortLabel`, this setting is _not_ inherited
+      from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. In Nomad 0.7.1 or
+      later numeric ports may be used if `AddressMode: "driver"` is set on
+      the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. Requires Consul >= 0.7.2.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. Since Nomad v0.5.3, the
+template can reference [Nomad's runtime environment variables][env]. For a full
+list of the API template functions, please refer to the [Consul Template
+README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.7.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.7.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..53734a477d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,41 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+- [`nix-nomad`](https://github.com/tristanpemble/nix-nomad) - HashiCorp Nomad job definitions in Nix
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.7.x/content/api-docs/metrics.mdx b/content/nomad/v1.7.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/namespaces.mdx b/content/nomad/v1.7.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/node-pools.mdx b/content/nomad/v1.7.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.7.x/content/api-docs/nodes.mdx b/content/nomad/v1.7.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..2acff9d512
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1147 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.7.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..cfe2ea2a9d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,253 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ],
+  "Leader": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+  "Voters": [
+    "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+    "e36ee410-cc3c-0a0c-c724-63817ab30303"
+  ],
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+<EnterpriseAlert>
+  This API endpoint return with more information in Nomad Enterprise. This is
+  not present in Nomad Community Edition.
+</EnterpriseAlert>
+
+When using Nomad Enterprise this endpoint will return more information about the
+underlying actions and state of Autopilot.
+
+```json
+{
+  ...
+  "ReadReplicas": null,
+  "RedundancyZones": {},
+  "Upgrade": {
+    "Status": "idle",
+    "TargetVersion": "1.7.5+ent",
+    "TargetVersionVoters": [
+      "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "e36ee410-cc3c-0a0c-c724-63817ab30303"
+    ],
+    "TargetVersionNonVoters": null,
+    "TargetVersionReadReplicas": null,
+    "OtherVersionVoters": null,
+    "OtherVersionNonVoters": null,
+    "OtherVersionReadReplicas": null,
+    "RedundancyZones": {}
+  },
+  "OptimisticFailureTolerance": 0
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/index.mdx b/content/nomad/v1.7.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.7.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..7080d4828e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,261 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Active Public Keys
+
+This endpoint retrieves a list of active public keys used to sign [workload
+identities][wi]. The response is in the [JWKS][rfc7517] format as is commonly
+used by JWT auth methods.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/.well-known/jwks.json`    | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `none`       |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/jwks.json'
+```
+
+### Sample Response
+
+```json
+{
+  "keys": [
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "15a95f48-001a-8be5-5da9-d94901d022c9",
+      "alg": "RS256",
+      "n": "6sImUQR6A...FB7bKn02dKw",
+      "e": "AQAB"
+    },
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "b7f6a3a7-14f9-4ac5-f713-32c9bce1fa93",
+      "alg": "RS256",
+      "n": "zEdiUB3DFuM...ii3kQvOf_eDApBDWJhfQw",
+      "e": "AQAB"
+    }
+  ]
+}
+```
+
+## OIDC Discovery
+
+This endpoint retrieves [OIDC configuration metadata][oidc-disco] for using
+[workload identities][wi] with third party services. Nomad will act as an
+identity provider (IDP) to allow third parties to authenticate workload
+identity JWTs based on the OIDC configurationa and JWKS.
+
+Most third parties will require this endpoint be accessible through a
+publically resolvable domain name and HTTPS signed by a trusted certificate
+authority.
+
+You must set the [`oidc_issuer`][oidc_issuer] Server agent configuration
+parameter before this endpoint is enabled. In most situations you will also
+need to run a proxy or load balancer for in front of this endpoint to serve the
+contents with HTTPS using a trusted certificate.
+
+| Method | Path                                | Produces           |
+|--------|-------------------------------------|--------------------|
+| `GET`  | `/.well-known/openid-configuration` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `none` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/openid-configuration'
+```
+
+### Sample Response
+
+```json
+{
+  "id_token_signing_alg_values_supported": [
+    "RS256",
+    "EdDSA"
+  ],
+  "issuer": "http://example.com",
+  "jwks_uri": "http://example.com/.well-known/jwks.json",
+  "response_types_supported": [
+    "code"
+  ],
+  "subject_types_supported": [
+    "public"
+  ]
+}
+```
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[oidc-disco]: https://openid.net/specs/openid-connect-discovery-1_0.html
+[oidc_issuer]: /nomad/docs/configuration/server#oidc_issuer
+[required ACLs]: /nomad/api-docs#acls
+[rfc7517]: https://datatracker.ietf.org/doc/html/rfc7517
+[wi]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/license.mdx b/content/nomad/v1.7.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.7.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..fb77f6d8e6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,229 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api /v1/operator/raft/configuration
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+</Tab>
+</Tabs>
+
+### Sample Response
+
+```json
+{
+    "Index": 0,
+    "Servers": [
+        {
+            "Address": "10.1.0.10:4647",
+            "ID": "c13f9998-a0f3-d765-0b52-55a0b3ce5f88",
+            "Leader": false,
+            "Node": "node1.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.20:4647",
+            "ID": "d7927f2b-067f-45a4-6266-af8bb84de082",
+            "Leader": true,
+            "Node": "node2.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.30:4647",
+            "ID": "00d56ef8-938e-abc3-6f8a-f8ac80a80fb9",
+            "Leader": false,
+            "Node": "node3.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        }
+
+    ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. For Raft protocol v2, this is the
+    same as the `Address`. Raft protocol v3 uses GUIDs as the ID.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  server to remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the server to
+  remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+  <Note>
+
+  Either `address` or `id` must be provided, but not both.
+
+  </Note>
+
+### Sample Request
+
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X DELETE \
+   /v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    https://127.0.0.1:4646/v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+</Tabs>
+
+## Transfer Leadership to another Raft Peer
+
+This endpoint tells the current cluster leader to transfer leadership
+to the Nomad server with given address or ID in the Raft
+configuration. The return code signifies success or failure.
+
+| Method              | Path                                    | Produces           |
+| ------------------- | --------------------------------------- | ------------------ |
+| `PUT` <br /> `POST` | `/v1/operator/raft/transfer-leadership` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  target server as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the target server
+  as provided in the output of `/v1/operator/raft/configuration` API endpoint or
+  the `nomad operator raft list-peers` command.
+
+<Note>
+
+- The cluster must be running Raft protocol v3 or greater on all server members.
+
+- Either `address` or `id` must be provided, but not both.
+
+</Note>
+
+### Sample Requests
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X PUT \
+    "/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl --request PUT \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    "https://127.0.0.1:4646/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+</Tabs>
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.7.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.7.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.7.x/content/api-docs/operator/upgrade-check.mdx b/content/nomad/v1.7.x/content/api-docs/operator/upgrade-check.mdx
new file mode 100644
index 0000000000..8659c6b135
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/operator/upgrade-check.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: Upgrade Check - Operator - HTTP API
+description: |-
+  The /operator/upgrade-check endpoints provide tools for verifying the state
+  of the cluster prior to upgrades.
+---
+
+# Upgrade Check Operator HTTP API
+
+The `/operator/upgrade-check` endpoints provide some predefined verifications
+that can be useful prior to upgrades and changes to Nomad configuration.
+
+<Note>
+
+These endpoints are meant to target specific releases of Nomad and may be
+removed or modified without notice.
+
+</Note>
+
+## Vault Workload Identity
+
+This endpoint retrieves jobs, nodes, and Vault ACL tokens that may be affected
+when migrating a Nomad cluster to use [workload identities for
+Vault][nomad_acl_vault_wid].
+
+| Method | Path                                                 | Produces           |
+| ------ | ---------------------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/upgrade-check/vault-workload-identity` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/operator/upgrade-check/vault-workload-identity
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 20,
+  "JobsWithoutVaultIdentity": [
+    {
+      "CreateIndex": 11,
+      "Datacenters": [
+        "*"
+      ],
+      "ID": "example",
+      "JobModifyIndex": 11,
+      "JobSummary": null,
+      "ModifyIndex": 19,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "default",
+      "ParameterizedJob": false,
+      "ParentID": "",
+      "Periodic": false,
+      "Priority": 50,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1704995322434188000,
+      "Type": "service"
+    }
+  ],
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "OutdatedNodes": [
+    {
+      "Address": "192.168.0.186",
+      "CreateIndex": 8,
+      "Datacenter": "dc1",
+      "Drain": false,
+      "Drivers": {
+        "qemu": {
+          "Attributes": {
+            "driver.qemu": "true",
+            "driver.qemu.version": "8.1.1"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.993541-05:00"
+        },
+        "exec": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "exec driver unsupported on client OS",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.958495-05:00"
+        },
+        "raw_exec": {
+          "Attributes": {
+            "driver.raw_exec": "true"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.958539-05:00"
+        },
+        "java": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.97141-05:00"
+        },
+        "docker": {
+          "Attributes": {
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.runtimes": "io.containerd.runc.v2,runc",
+            "driver.docker.os_type": "linux",
+            "driver.docker": "true",
+            "driver.docker.version": "24.0.7"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.989993-05:00"
+        }
+      },
+      "HostVolumes": null,
+      "ID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "LastDrain": null,
+      "ModifyIndex": 10,
+      "Name": "client-1",
+      "NodeClass": "",
+      "NodePool": "default",
+      "SchedulingEligibility": "eligible",
+      "Status": "ready",
+      "StatusDescription": "",
+      "Version": "1.6.4"
+    }
+  ],
+  "VaultTokens": [
+    {
+      "Accessor": "czh9MPcRXzAhxBL9XKyb3Kh1",
+      "AllocID": "f00893d4-d9ef-4937-6a7a-ab495b68a971",
+      "CreateIndex": 14,
+      "CreationTTL": 60,
+      "NodeID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "Task": "redis"
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `JobsWithoutVaultIdentity` `(array<Job>)` - The list of jobs that have a
+  [`vault`][] block but do not have an [`identity`][] for Vault
+  authentication. These jobs can fail if they are not redeployed with an
+  identity for Vault before the configuration for Nomad servers are updated and
+  their access to Vault is removed.
+
+- `OutdatedNodes` `(array<Node>)` - The list of nodes running a version of
+  Nomad that does not support workload identity authentication for Vault.
+  Allocations placed in these nodes will use the deprecated legacy flow to
+  retrieve Vault tokens. If the Nomad servers configuration is update to remove
+  their access to Vault before these nodes are upgraded, these allocations will
+  fail. Allocations that use workload identity for Vault will not be able to be
+  placed in these nodes until they are upgraded.
+
+- `VaultTokens` `(array<VaultAccessor>)` - The list of Vault ACL tokens created
+  by Nomad servers using the deprecated legacy flow. They will continue to work
+  even after the migration to the workload identities, but they may not be
+  automatically revoked by Nomad and will only expire once their TTL reaches
+  zero.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+[`identity`]: /nomad/docs/job-specification/identity
+[`vault`]: /nomad/docs/job-specification/vault
+[nomad_acl_vault_wid]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.7.x/content/api-docs/plugins.mdx b/content/nomad/v1.7.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/quotas.mdx b/content/nomad/v1.7.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..112d80d7e9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/quotas.mdx
@@ -0,0 +1,354 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/recommendations.mdx b/content/nomad/v1.7.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/regions.mdx b/content/nomad/v1.7.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.7.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/search.mdx b/content/nomad/v1.7.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..247ed39453
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/search.mdx
@@ -0,0 +1,638 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.7.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.7.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/services.mdx b/content/nomad/v1.7.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/api-docs/status.mdx b/content/nomad/v1.7.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/system.mdx b/content/nomad/v1.7.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/task-api.mdx b/content/nomad/v1.7.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..8f2b43ca01
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/task-api.mdx
@@ -0,0 +1,109 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+## Limitations
+
+- Using the Task API Unix Domain Socket on Windows [requires][windows] Windows
+build 17063 or later.
+
+[acl]: /nomad/docs/concepts/acl
+[acl-tokens]: /nomad/docs/concepts/acl#token
+[alloc-exec]: /nomad/docs/commands/alloc/exec
+[anon]: /nomad/tutorials/access-control/access-control#acl-policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[dnm]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.7.x/content/api-docs/ui.mdx b/content/nomad/v1.7.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.7.x/content/api-docs/validate.mdx b/content/nomad/v1.7.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.7.x/content/api-docs/variables/index.mdx b/content/nomad/v1.7.x/content/api-docs/variables/index.mdx
new file mode 100644
index 0000000000..8f1e8bcb21
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/variables/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: |-
+  The /var endpoints are used to query for and interact with variables and variable
+  locking.
+---
+
+# Vars HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables, and set up locks and leases over them.
+
+See the [Variables][] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`][] commands.
+
+Please choose a sub-section in the navigation for more information
+
+[`nomad var`]: /nomad/docs/commands/var
+[Variables]: /nomad/docs/concepts/variables
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/api-docs/variables/locks.mdx b/content/nomad/v1.7.x/content/api-docs/variables/locks.mdx
new file mode 100644
index 0000000000..bbb79d7583
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/variables/locks.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: Variable Locks - HTTP API
+description: The /var endpoints are used to query for and interact with variables and locks.
+---
+
+# Locks HTTP API
+
+The `/var` endpoint is used to hold, renew and release a lock over a variable.
+
+## Lock Variable
+
+The endpoint to create a variable can also be used to hold a lock and interact with
+it through the use of a parameter defining the operation to be performed.
+
+| Method | Path                                 | Produces           |
+|--------|--------------------------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path?<lock-operation>` | `application/json` |
+
+### Parameters
+
+The lock operation parameter can be:
+
+- `lock-acquire`: When used, the call will introduce a lock over the variable if 
+it exists, or create a new one if it doesn't. The lock ID will be returned in the 
+response and it must be provided to perform any other operation over the lock. 
+The variable items can be updated at any time using the lock ID, but the lock
+parameters are unmmutable, attempting to modify them while a lock is present will
+generate an error. 
+
+In the case of attempting to acquire a variable that is already locked, a conflict
+response will be returned. 
+
+The lock-acquire operation will override the variable items if new values are 
+present.
+
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-acquire
+```
+
+#### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "1m"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the created or updated variable including the lock 
+parameters and ID, along with metadata created by the server:
+
+```json
+{
+  "CreateIndex": 15,
+  "CreateTime": 1694552155379696000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 16,
+  "ModifyTime": 1694552206138804000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-renew`: A valid call to lock renew needs to be placed before the lock's
+TTL is up in order to mantain the variable locked. A valid call must include the
+lock ID as part of the request body. If the lock TTL is up without a renewal or
+release calls, the variable will remain unlockable for at least the lock delay. 
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-renew
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body only returns metadata created by the server and the lock
+parameters:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 43,
+  "ModifyTime": 1694556175092779000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-release`: A call to the endpoint with the `lock-release` operation will
+immediately remove the lock over the variable, making it modifiable without 
+restrictions again. 
+
+The lock-release operation will not override the variable items, if the request
+body contains any item, it will generate a bad request response.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-release
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the released variable along with metadata
+created by the server:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "ModifyIndex": 66,
+  "ModifyTime": 1694556922600469000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+### Sample Response for Conflict
+
+In the case of an attempt to lock, renew or modify a locked variable
+without the correct ID, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "CreateIndex": 0,
+  "CreateTime": 0,
+  "Items": null,
+  "Lock": null,
+  "ModifyIndex": 0,
+  "ModifyTime": 0,
+  "Namespace": "default",
+  "Path": "example/first"
+}
+```
+
+## Restrictions
+
+When creating a new variable using the lock-acquire operation, all the known 
+[restrictions][] regarding the path and size of the content apply, but unlike 
+regular variables, locked variables can be created with or without any items.
+
+The lock TTL and Delay must be values between 10 seconds and 24 hours.
+
+[Variables]: /nomad/docs/concepts/variables
+[restrictions]: /nomad/api-docs/variables/variables#restrictions
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.7.x/content/api-docs/variables/variables.mdx b/content/nomad/v1.7.x/content/api-docs/variables/variables.mdx
new file mode 100644
index 0000000000..f53b0c7be4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/variables/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables][] documentation for information how these capabilities are
+used. 
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+- `lock-operation` `(string: <unset>)` - This endpoint can also be used to create 
+and hold a lock over a variable, refer to the [locks section][] for more
+information.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+[Variables]: /nomad/docs/concepts/variables
+[locks section]:/nomad/api-docs/variables/locks
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.7.x/content/api-docs/volumes.mdx b/content/nomad/v1.7.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..9b56c16e88
--- /dev/null
+++ b/content/nomad/v1.7.x/content/api-docs/volumes.mdx
@@ -0,0 +1,789 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below).
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_VOLUME`
+capability support this endpoint.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
+[Volume Expansion]: /nomad/docs/other-specifications/volume#volume-expansion
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/create.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..2d3d8cccc1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/create.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method create'
+description: The auth-method create command is used to create new ACL Auth Methods.
+---
+
+# Command: acl auth-method create
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..45303a5658
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method delete'
+description: The auth-method delete command is used to delete existing ACL Auth Methods.
+---
+
+# Command: acl auth-method delete
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/info.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..a6d13c61b8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/info.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method info'
+description: |
+  The auth-method info command is used to fetch information about an existing
+  ACL Auth Method.
+---
+
+# Command: acl auth-method info
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/list.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..0cb15df8e6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method list'
+description: The auth-method list command is used to list existing ACL Auth Methods.
+---
+
+# Command: acl auth-method list
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/update.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..5b0b58d0af
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/auth-method/update.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method update'
+description: The auth-method update command is used to update existing ACL Auth Methods.
+---
+
+# Command: acl auth-method update
+
+The `acl auth-method update` command is used to update existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -token-name-format '${auth_method_name}-${value.user}' -config @config.json example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = global
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_name}-${value.user}
+Default             = false
+Create Index        = 14
+Modify Index        = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/create.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..e15d870756
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule create'
+description: The binding-rule create command is used to create new ACL Binding Rules.
+---
+
+# Command: acl binding-rule create
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..0bdafd9689
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule delete'
+description: The binding-rule delete command is used to delete existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule delete
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/info.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..38dcfb2eeb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule info'
+description: |
+  The binding-rule info command is used to fetch information about an existing
+  ACL Binding Rule.
+---
+
+# Command: acl binding-rule info
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/list.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..d506f8a8d2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule list'
+description: The binding-rule list command is used to list existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule list
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/update.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..03bacdd24d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule update'
+description: The binding-rule update command is used to update existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule update
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..83f538040b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an appropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..d079e2ca12
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[authmethodcreate]: /nomad/docs/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/docs/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/docs/commands/acl/auth-method/info
+[authmethodlist]: /nomad/docs/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/docs/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/docs/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/docs/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/docs/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/docs/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/docs/commands/acl/binding-rule/update
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..af000cd896
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..f0622d92c4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..a5a48d3da0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl role create'
+description: The role create command is used to create new ACL Roles.
+---
+
+# Command: acl role create
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..f4e4a93b9f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl role delete'
+description: The role delete command is used to delete existing ACL Roles.
+---
+
+# Command: acl role delete
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..7a2f40a8bd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl role info'
+description: |
+  The role info command is used to fetch information about an existing ACL
+  Role.
+---
+
+# Command: acl role info
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..6f36f8d065
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl role list'
+description: The role list command is used to list existing ACL Roles.
+---
+
+# Command: acl role list
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..921924e82b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl role update'
+description: The role update command is used to update existing ACL Roles.
+---
+
+# Command: acl role update
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..5c0c77d051
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..33e442126e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..fb8fc94ac2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..b58a7193b8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.7.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..57c293382f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.7.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/agent.mdx b/content/nomad/v1.7.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..00685c4e91
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/agent.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir][] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled][] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token][] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr][] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect][] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address][] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth][] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise][] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file][] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file][] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise][]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join][] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name][]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name][] config option.
+
+- `-consul-client-failures-before-critical=<num>`: Equivalent to the
+  [client_failures_before_critical][] config option.
+
+- `-consul-client-failures-before-warning=<num>`: Equivalent to the
+  [client_failures_before_warning][] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file][] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name][]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name][] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name][] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name][] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join][] config
+  option.
+
+- `-consul-server-failures-before-critical=<num>`: Equivalent to the
+  [server_failures_before_critical][] config option.
+
+- `-consul-server-failures-before-warning=<num>`: Equivalent to the
+  [server_failures_before_warning][] config option.
+
+- `-consul-ssl`: Equivalent to the [ssl][] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token][] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl][] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir][] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter][] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. It may be
+  used with `-dev-consul` to configure default workload identities for Consul.
+  This mode is supported only on Linux as root.
+
+- `-dev-consul`: Starts the agent in development mode with a default Consul
+  configuration for Nomad workload identity. It may be used with `-dev-connect`
+  to configure the agent for Consul Service Mesh.
+
+- `-dev-vault`: Starts the agent in development mode with a default Vault
+  configuration for Nomad workload identity.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview][] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level][] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location][] config option.
+
+- `-log-json`: Equivalent to the [log_json][] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta][] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface][] config option.
+
+- `-node=<name>`: Equivalent to the [name][] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class][]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool][]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir][] config option.
+
+- `-region=<region>`: Equivalent to the [region][] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave][] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval][] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max][] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers][] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir][] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_failures_before_critical]: /nomad/docs/configuration/consul#client_failures_before_critical
+[client_failures_before_warning]: /nomad/docs/configuration/consul#client_failures_before_warning
+[server_failures_before_critical]: /nomad/docs/configuration/consul#server_failures_before_critical
+[server_failures_before_warning]: /nomad/docs/configuration/consul#server_failures_before_warning
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad agent]: /nomad/docs/operations/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/checks.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..fc1b02c1e2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: alloc checks'
+description: |
+  Outputs service health check status information.
+---
+
+# Command: alloc checks
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability 
+for the allocation's namespace. The 'list-jobs' capability is required to run the 
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Checks Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..8ea9ae7216
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..2fdb4e42c9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..b673a63f04
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/docs/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..ddf16f7b7a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..65bc71d15f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks. As of Nomad
+0.7.1, alloc status also shows allocation modification time in
+addition to create time. As of Nomad 0.8, alloc status shows
+information about reschedule attempts. As of Nomad 0.11, alloc status
+shows volume claims when a job claims volumes.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.7.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..718d962d57
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.7.x/content/docs/commands/config/index.mdx b/content/nomad/v1.7.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.7.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.7.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..9c72af2dce
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..d40b151754
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3369798607
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..86542733e2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.7.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..9214e1adf4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.7.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..23995ad28e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfully deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfully deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfully deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.7.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.7.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.7.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.7.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.7.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/fmt.mdx b/content/nomad/v1.7.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..d40d17c95a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: fmt'
+description: |
+  Rewrite Nomad config and job files to canonical format
+---
+
+# Command: fmt
+
+The `fmt` commands check the syntax and rewrites Nomad configuration and jobspec
+files to canonical format. It can be used to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [flags] paths ...
+```
+
+Formats Nomad agent configuration and job file to a canonical format. If a path
+is a directory, it will recursively format all files with .nomad and .hcl
+extensions in the directory.
+
+If you provide a single dash (-) as argument, fmt will read from standard input
+(STDIN) and output the processed output to standard output (STDOUT).
+
+Note that, this command will check the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 jobspec will result in errors.
+
+## Format Options:
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/index.mdx b/content/nomad/v1.7.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/action.mdx b/content/nomad/v1.7.x/content/docs/commands/job/action.mdx
new file mode 100644
index 0000000000..1d16217c08
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/action.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'Commands: job action'
+description: |
+  The job action command is used to execute predefined actions from a job
+  specification in a running task context
+---
+
+# Command: job action
+
+**Alias: `nomad action`**
+
+The `job action` command allows operators to execute predefined actions declared
+in Nomad job specifications. These actions can be defined at task level and are
+intended for specific operational tasks, such as clearing a cache, or migrating
+a database.
+
+An action may self-terminate upon completion (for example, echoing a string),
+or run for an indeterminate amount of time (for example, watching a blocking
+query). In the latter case, an action can be terminated via escape character
+(such as cmd+c / ctrl+c)
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `alloc-exec`, `read-job`, and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Usage
+
+```plaintext
+nomad job action [options] <action>
+```
+
+The `job action` command requires an action name and accepts two ways of
+specifying where it should run:
+- by passing the job name and known allocation ID along with the name of the action
+- by passing the job, task group, and task name along with the name of the action
+(when the allocation ID is not known). A random allocation will be selected if
+multiple are available.
+
+The action name provided must be defined within a task in the [job specification]
+provided. With sufficient privileges, an execution context will be opened and
+the defined action command will be run. No further input is possible, save for
+the escape character to terminate execution, so interactive commands are not
+supported.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Action Options
+
+- `-job`: (Required) Specifies the job containing the predefined action.
+
+- `-alloc`: Specifies the allocation within which the action is to be executed.
+  If omitted, `-group` and `-task` must be provided, and a random
+  allocation for the group will be selected.
+
+- `-task`: Specifies the task within the job where the action is defined. This
+  is required either if `-alloc` provided and your group has multiple tasks,
+  or if you specify a `-group`.
+
+- `-group`: Specifies the task group within the job. If present, a random
+  allocation is selected. If omitted, `-alloc` must be provided.
+
+- `-i`: Pass stdin to the action, defaults to `true`. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to `true` if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty,
+  defaults to '~'. The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot (`.`) closes the connection.
+  Setting the character to `none` disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+Execute an action within a specific task in a job:
+
+```shell-session
+$ nomad action \
+  -group=my-group \
+  -task=my-task \
+  -job=my-job \
+  weather
+
+Toronto: ☁️   +3°C
+```
+
+Execute an action within a specific allocation:
+
+```shell-session
+$ nomad action \
+  -alloc=f200a789-6da4-504c-d131-6181764f101e \
+  -job=actions-demo \
+  echo-time
+
+Running for 0 seconds
+Running for 1 seconds
+Running for 2 seconds
+Running for 3 seconds
+```
+
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.7.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..72f2e9a443
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.7.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..ccfcf28be1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.7.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..235cc952c3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.7.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..9d3a2cf8ee
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/history.mdx b/content/nomad/v1.7.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..9544f64140
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/index.mdx b/content/nomad/v1.7.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..47ff5c79d8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/init.mdx b/content/nomad/v1.7.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..1c5a7d5ecc
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.7.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..a96593f779
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.7.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..8aca82eb80
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.7.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..2d62783d19
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,263 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.7.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..28dab1fc76
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/restart.mdx b/content/nomad/v1.7.x/content/docs/commands/job/restart.mdx
new file mode 100644
index 0000000000..6f87e40a82
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'Commands: job restart'
+description: |
+  The job restart command is used to restart allocations for a job.
+---
+
+# Command: job restart
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+Allocations can be restarted in-place or rescheduled. When restarting
+in-place the command may target specific tasks in the allocations, restart
+only tasks that are currently running, or restart all tasks, even the ones
+that have already run. Allocations can also be targeted by groups and tasks.
+When both groups and tasks are defined only the tasks for the allocations of
+those groups are restarted.
+
+When rescheduling, the current allocations are stopped triggering the Nomad
+scheduler to create replacement allocations that may be placed in different
+clients. The command waits until the new allocations have client status `ready`
+before proceeding with the remaining batches. Services health checks are not
+taken into account.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, allocations are stopped and rescheduled instead of
+  restarted in-place. Since the group is not modified the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such
+  as [`max_parallel`][], are not taken into account. This option cannot be used
+  with `-task`. Only jobs of type `batch`, `service`, and `system` can be
+  rescheduled.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.7.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..f0bd4efa60
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/run.mdx b/content/nomad/v1.7.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..36f2c87f85
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,249 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.7.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..f3171dc5f3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.7.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..dd639766f6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/status.mdx b/content/nomad/v1.7.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..dfcbc885a3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
+shows allocation modification time in addition to create time. When the
+`-verbose` flag is not set, allocation creation and modify times are shown in a
+shortened relative time format like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-json`: Output the job status in JSON format.
+
+- `-t`: Format and display the job status using a Go template.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.7.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..ad19f5afac
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.7.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.7.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..738f7f759f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.7.x/content/docs/commands/license/get.mdx b/content/nomad/v1.7.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..e56b0a4aeb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/license/index.mdx b/content/nomad/v1.7.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..a248a76d37
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are only available with Nomad Enterprise.
+
+The `license` commands can be used to retrieve license information from a server,
+or inspect and validate a license.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/docs/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.7.x/content/docs/commands/license/inspect.mdx b/content/nomad/v1.7.x/content/docs/commands/license/inspect.mdx
new file mode 100644
index 0000000000..d1689b5122
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/license/inspect.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license inspect'
+description: |
+  The license inspect command is used to inspect and validate an enterprise license.
+---
+
+# Command: license inspect
+
+<EnterpriseAlert>
+  This command is only present in Nomad Enterprise.
+</EnterpriseAlert>
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/login.mdx b/content/nomad/v1.7.x/content/docs/commands/login.mdx
new file mode 100644
index 0000000000..1dd2bf1645
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/login.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: login'
+description: |
+  Login to Nomad using an authentication method
+---
+
+# Command: login
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Login Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/monitor.mdx b/content/nomad/v1.7.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..445dab5007
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..c1ac6e347f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers  = ["docker", "exec"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..a32e049fff
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs. In federated clusters,
+you cannot delete a namespace that has non-terminal jobs in any of the federated
+regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..8e53e9085a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..4c1e61828b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..3f9c543249
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.7.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..1a6ea780e8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name            = api-prod
+Description     = Prod API servers
+Quota           = prod
+EnabledDrivers  = docker,exec
+DisabledDrivers = raw_exec
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..c185e960a9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: node pool apply'
+description: |
+  The node pool apply command is used to create or update a node pool.
+---
+
+# Command: node pool apply
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..bc9748cc96
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool delete'
+description: |
+  The node pool delete command is used to delete a node pool.
+---
+
+# Command: node pool delete
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/index.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..f541856c4d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool'
+description: |
+  The node pool command is used to interact with node pools.
+---
+
+# Command: node pool
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+Usage: `nomad node pool <subcommand> [options]`
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/docs/commands/node-pool/apply
+[delete]: /nomad/docs/commands/node-pool/delete
+[info]: /nomad/docs/commands/node-pool/info
+[jobs]: /nomad/docs/commands/node-pool/jobs
+[list]: /nomad/docs/commands/node-pool/list
+[nodes]: /nomad/docs/commands/node-pool/nodes
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/info.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..e15231aef2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: node pool info'
+description: |
+  The node pool info command is used to fetch information about a node pool.
+---
+
+# Command: node pool info
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name        = prod
+Description = Node pool for production workloads.
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/init.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..6f76c045e6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool init'
+description: |
+  Generate an example node pool specification.
+---
+
+# Command: node pool init
+
+The `node pool init` creates an example node pool specification file that can be
+used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/jobs.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..f55c9723df
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: node pool jobs'
+description: |
+  The node pool jobs command is used to list jobs in node pool.
+---
+
+# Command: node pool jobs
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Jobs Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/list.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..e9f472b836
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'Commands: node pool list'
+description: |
+  The node pool list command is used to list node pools.
+---
+
+# Command: node pool list
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.7.x/content/docs/commands/node-pool/nodes.mdx b/content/nomad/v1.7.x/content/docs/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..e9ebefa252
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: node pool nodes'
+description: |
+  The node pool nodes command is used to list nodes in node pool.
+---
+
+# Command: node pool nodes
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Nodes Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/config.mdx b/content/nomad/v1.7.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.7.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..4d24e9e47a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.7.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/index.mdx b/content/nomad/v1.7.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..289d1a027f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/docs/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/meta/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..5b67230336
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: node meta apply'
+description: |
+  The node meta apply command updates node metadata.
+---
+
+# Command: node meta apply
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Apply Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+[api]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/meta/index.mdx b/content/nomad/v1.7.x/content/docs/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..2b65048e5b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/meta/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: node meta'
+description: |
+  The node meta commands are used to read and update node metadata.
+---
+
+# Command: node meta
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+Usage: `nomad node meta <subcommand> [options]`
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/runtime/interpolation#node-attributes
+[apply]: /nomad/docs/commands/node/meta/apply
+[read]: /nomad/docs/commands/node/meta/read
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/meta/read.mdx b/content/nomad/v1.7.x/content/docs/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..e04e685313
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: node meta read'
+description: |
+  The node meta read command reads node metadata.
+---
+
+# Command: node meta read
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Read Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+[api]: /nomad/api-docs/client#read-node-metadata
diff --git a/content/nomad/v1.7.x/content/docs/commands/node/status.mdx b/content/nomad/v1.7.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..d6c2488c10
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/health.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/health.mdx
new file mode 100644
index 0000000000..ee455aa17b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/health.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot health'
+description: |
+  Display the current Autopilot internal health.
+---
+
+# Command: operator autopilot state
+
+The Autopilot operator command is used to view the current Autopilot
+state. See the [Autopilot Guide][] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot health [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Output Options
+
+- `-json`: Output the Autopilot health in unformatted JSON.
+
+The output will return like below, read about the output of the command in the [API docs][].
+
+```shell-session
+$ nomad operator autopilot health
+Healthy: true
+FailureTolerance: 0
+Leader: e349749b-3303-3ddf-959c-b5885a0e1f6e
+Voters:  
+        e349749b-3303-3ddf-959c-b5885a0e1f6e
+Servers: 
+ID                                    Name      Address         SerfStatus  Version   Leader  Voter  Healthy  LastContact  LastTerm  LastIndex  StableSince
+e349749b-3303-3ddf-959c-b5885a0e1f6e  node1     127.0.0.1:4647  alive       1.7.5     true    true   true     0s           2         14         2024-02-20 16:40:55 +0000 UTC
+```
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
+[api docs]: /nomad/api-docs/operator/autopilot#read-state
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/client-state.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..6475fe5477
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'Commands: operator client-state'
+description: >
+  The `operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# Command: operator client-state
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..8ffde93526
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=2m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `2m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=DEBUG`: The log level to monitor. Defaults to `DEBUG`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..d703f46ae8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring generate'
+description: >
+  The `operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator gossip keyring generate
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..e30c21b5b4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring install'
+description: |
+  Install a new gossip encryption key
+---
+
+# Command: operator gossip keyring install
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..e05d940bd9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring list'
+description: |
+  List gossip keys
+---
+
+# Command: operator gossip keyring list
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..97009d769f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring remove'
+description: |
+  Remove a new gossip encryption key
+---
+
+# Command: operator gossip keyring remove
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..708b506787
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring use'
+description: |
+  Use a new gossip encryption key
+---
+
+# Command: operator gossip keyring use
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..fd097a007a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem. This was added in Nomad 0.5.5.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/docs/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/docs/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/docs/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/docs/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/docs/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/docs/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/docs/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/docs/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..e5f337b373
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+description: |-
+  The `operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/raft/transfer-leadership.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/raft/transfer-leadership.mdx
new file mode 100644
index 0000000000..0520b530b9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/raft/transfer-leadership.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: operator raft transfer-leadership'
+description: |
+  Transfer leadership to a specific a Nomad server.
+---
+
+# Command: operator raft transfer-leadership
+
+Transfer leadership from the current leader to the given server member.
+
+While performing a [rolling upgrade][] of your Nomad cluster, it might be
+advisable to transfer leadership to a specific node in the cluster. For example,
+setting the leader to the first upgraded server in the cluster can prevent
+leadership churn as you upgrade the remaining server nodes.
+
+The target server's ID or address:port are required and can be obtained by
+running the [`nomad operator raft list-peers`][] command or by calling the
+[Read Raft Configuration][] API endpoint.
+
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator][] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft transfer-leadership [options]
+```
+
+<Tip title="Required Permissions">
+If ACLs are enabled, this command requires a management token.
+</Tip>
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Transfer Leadership Options
+
+- `-peer-address`: Specifies the Raft **Address** of the target server as
+  provided in the output of the [`nomad operator raft list-peers`][] command or
+  the [Read Raft Configuration] API endpoint.
+
+- `-peer-id`: Specifies the Raft **ID** of the target server as provided in the
+  output of the [`nomad operator raft list-peers`][] command or the
+  [Read Raft Configuration] API endpoint.
+
+  <Note>
+
+  Either `-peer-address` or `-peer-id` must be provided, but not both.
+
+  </Note>
+
+[`nomad operator raft list-peers`]: /nomad/docs/commands/operator/raft/list-peers 'Nomad operator raft list-peers command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[rolling upgrade]: /nomad/docs/upgrade#upgrade-process
+[Read Raft Configuration]: /nomad/api-docs/operator/raft#read-raft-configuration
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..e049b8b795
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring list'
+description: |
+  List encryption key metadata
+---
+
+# Command: operator root keyring list
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..bcf701378e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring remove'
+description: |
+  Remove an unused encryption key
+---
+
+# Command: operator root keyring remove
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..aef49c6265
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring rotate'
+description: |
+  Rotate encryption key
+---
+
+# Command: operator root keyring rotate
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Rotate Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..b3d7049f73
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+<Warning>
+
+This snapshot agent only saves a Raft snapshot. Key material for the Nomad
+keyring is stored on disk and must be saved separately. To use a snapshot saved
+by the agent to recover a cluster, you will also need to [restore the keyring][]
+onto at least one server.
+
+</Warning>
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
+
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..1170fc5c70
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Displays information about a snapshot file stored on local disk.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Inspect Options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..049282452f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+<Warning>
+
+This command only restores the Raft snapshot, which does not include keyrings.
+
+If you are recovering a cluster, you also need to restore the keyring onto at
+least one server.  Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..d1e4a4a5e7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command only saves a Raft snapshot. This snapshot does not include
+keyrings. You must back up keyrings separately.
+
+If you use this snapshot to recover a cluster, you also need to restore the
+keyring onto at least one server. Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.7.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.7.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.7.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..1775a87963
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..d7a1945d54
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..577c162878
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..1984aaa386
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..31798b859b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 8,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 2500,
+                    "DiskMB": 0,
+                    "MemoryMB": 2000,
+                    "Networks": null
+                }
+            }
+        ],
+        "ModifyIndex": 56,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 8,
+            "ModifyIndex": 56,
+            "Name": "default-quota",
+            "Used": {
+                "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+                    "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 500,
+                        "DiskMB": 0,
+                        "MemoryMB": 256,
+                        "Networks": [
+                            {
+                                "CIDR": "",
+                                "Device": "",
+                                "DynamicPorts": null,
+                                "IP": "",
+                                "MBits": 0,
+                                "Mode": "",
+                                "ReservedPorts": null
+                            }
+                        ]
+                    }
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..466c5e3edd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.7.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..4bd6b11c7a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage   Memory Usage  Network Usage
+global  500 / 2500  256 / 2000    30 / 50
+
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 2500,
+                "DiskMB": 0,
+                "MemoryMB": 2000,
+                "Networks": null
+            }
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota inspect -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..a9eb367d20
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.7.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..ade257d00c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.7.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..55c9599045
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.7.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.7.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..1ae6c075e5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.7.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..cafdf65b2e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.7.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..0dda69be94
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.7.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.7.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.7.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.7.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..b6322dbfc8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..6f828efbec
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.7.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f16f4225c0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.7.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.7.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..1fff15759b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.7.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..81e8e6d6cb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.7.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..cb7f001f83
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`. 
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Force-Leave Options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/server/index.mdx b/content/nomad/v1.7.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.7.x/content/docs/commands/server/join.mdx b/content/nomad/v1.7.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..a5a6661ec8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: /nomad/tutorials/manage-clusters/federation
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.7.x/content/docs/commands/server/members.mdx b/content/nomad/v1.7.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..3ace4d8db8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server memebers in its JSON format.
+
+- `-t`: Format and display the server memebers using a Go template.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..902be4e38c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/service/index.mdx b/content/nomad/v1.7.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..c1be98efff
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.7.x/content/docs/commands/service/info.mdx b/content/nomad/v1.7.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..4c0a77007d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/service/list.mdx b/content/nomad/v1.7.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..9715fb65e7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/setup/consul.mdx b/content/nomad/v1.7.x/content/docs/commands/setup/consul.mdx
new file mode 100644
index 0000000000..1fdd828395
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/setup/consul.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: setup consul'
+description: |
+  Setup a Consul cluster for Nomad integration.
+---
+
+# Command: setup consul
+
+This command sets up Consul for allowing Nomad workloads to authenticate
+themselves using Workload Identity.
+
+This command requires `acl:write` permissions for Consul and respects
+`CONSUL_HTTP_TOKEN`, `CONSUL_HTTP_ADDR`, and other [Consul-related environment
+variables][consulenv].
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup consul [options]
+```
+
+## Setup Consul Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup consul
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Consul ACL using their
+respective workload identities.
+
+First we need to connect to Consul.
+
+[?] Is "127.0.0.1:8500" the correct address of your Consul cluster? [Y/n]
+
+Since you're running Consul Enterprise, we will additionally create
+a namespace "nomad-workloads" and bind the auth methods to that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Consul cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+Nomad needs a JWT auth method for Consul services and tasks. The method for
+services will be called "nomad-workloads".
+
+This is the "nomad-workloads" method configuration:
+
+{
+    "Name": "nomad-workloads",
+    "Type": "jwt",
+    "DisplayName": "nomad-workloads",
+    "Description": "Login method for Nomad workloads using workload identities",
+    "TokenLocality": "local",
+    "Config": {
+        "BoundAudiences": [
+            "consul.io"
+        ],
+        "ClaimMappings": {
+            "consul_namespace": "consul_namespace",
+            "nomad_job_id": "nomad_job_id",
+            "nomad_namespace": "nomad_namespace",
+            "nomad_service": "nomad_service",
+            "nomad_task": "nomad_task"
+        },
+        "JWKSURL": "http://localhost:4646/.well-known/jwks.json",
+        "JWTSupportedAlgs": [
+            "RS256"
+        ]
+    },
+    "CreateIndex": 0,
+    "ModifyIndex": 0,
+    "NamespaceRules": [
+        {
+            "BindNamespace": "${value.consul_namespace}"
+        }
+    ]
+}
+[?] Create "nomad-workloads" auth method in your Consul cluster? [Y/n]
+[✔] Created auth method "nomad-workloads".
+
+Consul uses binding rules to map claims between Nomad's JWTs to Consul service
+identities and ACL roles, so we need to create a two binding rules for the auth
+method we created above: one for services, and one for tasks.
+
+This is the binding rule for services:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad services authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" in value",
+    "BindType": "service",
+    "BindName": "${value.nomad_service}",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n]
+[✔] Created binding rule for auth method "nomad-workloads".
+
+This is the binding rule for tasks:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad tasks authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" not in value",
+    "BindType": "role",
+    "BindName": "nomad-${value.nomad_namespace}-tasks",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Consul
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Auth method: nomad-workloads
+  * Binding rules: 4d80108a-6d77-36e1-71b1-d20a9acf8b17
+  * Namespace: nomad-workloads
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted binding rule "4d80108a-6d77-36e1-71b1-d20a9acf8b17".
+[✔] Deleted auth method "nomad-workloads".
+[✔] Deleted namespace "nomad-workloads".
+
+Consul cluster has not been configured for authenticating Nomad tasks and
+services using workload identitiies.
+
+Run the command again to finish the configuration process.
+```
+
+[consulenv]: /consul/commands#environment-variables
diff --git a/content/nomad/v1.7.x/content/docs/commands/setup/index.mdx b/content/nomad/v1.7.x/content/docs/commands/setup/index.mdx
new file mode 100644
index 0000000000..15a354de1e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/setup/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: setup'
+description: |
+  The setup command is used to interact with interactive setup helpers.
+---
+
+# Command: setup
+
+The `setup` command groups helper subcommands used for setting up external
+tools.
+
+<Warning>
+
+These commands are experimental features and may change their behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+Usage: `nomad setup <subcommand> [options]`
+
+Run `nomad setup <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`setup consul`][consul] - Setup a Consul cluster for Nomad integration.
+- [`setup vault`][vault] - Setup a Vault cluster for Nomad integration.
+
+[consul]: /nomad/docs/commands/setup/consul
+[vault]: /nomad/docs/commands/setup/vault
diff --git a/content/nomad/v1.7.x/content/docs/commands/setup/vault.mdx b/content/nomad/v1.7.x/content/docs/commands/setup/vault.mdx
new file mode 100644
index 0000000000..835a85dd4f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/setup/vault.mdx
@@ -0,0 +1,213 @@
+---
+layout: docs
+page_title: 'Commands: setup vault'
+description: |
+  Setup a Vault cluster for Nomad integration.
+---
+
+# Command: setup vault
+
+This command sets up Vault for allowing Nomad workloads to authenticate
+themselves using Workload Identity.
+
+This command requires `acl:write` permissions for Vault and respects
+`VAULT_TOKEN`, `VAULT_ADDR`, and other [Vault-related environment
+variables][vaultenv].
+
+The `-check` option can be used to verify if the Nomad cluster is ready to
+migrate to use Workload Identities with Vault. This option requires
+`operator:read` permission for Nomad.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup vault [options]
+```
+
+## Setup Vault Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+- `-check`: Verify if the Nomad cluster is ready to migrate to Workload
+  Identities.
+
+### Setup Vault Options When Using `-check`:
+
+- `-json`: Output migration status information in its JSON format.
+
+- `-t`: Format and display migration status information using a Go template.
+
+- `-verbose`: Display full information.
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup vault
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Vault ACL using their
+respective workload identities.
+
+First we need to connect to Vault.
+
+[?] Is "http://127.0.0.1:8200" the correct address of your Vault cluster? [Y/n]
+
+Since you're running Vault Enterprise, we will additionally create
+a namespace "nomad-workloads" and create all configuration within that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Vault cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+We will now enable the JWT credential backend and create a JWT auth method that
+Nomad workloads will use.
+
+This is the method configuration:
+
+{
+    "default_role": "nomad-workloads",
+    "jwks_url": "http://localhost:4646/.well-known/jwks.json",
+    "jwt_supported_algs": [
+        "EdDSA",
+        "RS256"
+    ]
+}
+[?] Create JWT auth method in your Vault cluster? [Y/n]
+[✔] Created JWT auth method "jwt-nomad".
+
+We need to create a role that Nomad workloads will assume while authenticating,
+and a policy associated with that role.
+
+
+These are the rules for the policy "nomad-workloads" that we will create. It uses a templated
+policy to allow Nomad tasks to access secrets in the path
+"secrets/data/<job namespace>/<job name>":
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+
+[?] Create the above policy in your Vault cluster? [Y/n]
+[✔] Created policy "nomad-workloads".
+
+We will now create an ACL role called "nomad-workloads" associated with the policy above.
+
+{
+    "bound_audiences": "vault.io",
+    "claim_mappings": {
+        "nomad_job_id": "nomad_job_id",
+        "nomad_namespace": "nomad_namespace",
+        "nomad_task": "nomad_task"
+    },
+    "role_type": "jwt",
+    "token_period": "30m",
+    "token_policies": [
+        "nomad-workloads"
+    ],
+    "token_type": "service",
+    "user_claim": "/nomad_job_id",
+    "user_claim_json_pointer": true
+}
+[?] Create role in your Vault cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Vault
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Policy: "nomad-workloads"
+  * JWT auth method: "jwt-nomad"
+  * Namespace: "nomad-workloads"
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted policy "nomad-workloads".
+[✔] Disabled JWT auth method "jwt-nomad".
+[✔] Deleted namespace "nomad-workloads".
+
+Vault cluster has not been configured for authenticating Nomad tasks and
+services using workload identities.
+
+Run the command again to finish the configuration process.
+```
+
+The `-check` option can use to verify if a cluster is ready to migrate to using
+workload identities with Vault.
+
+```
+$ nomad setup vault -check
+
+Jobs Without Workload Identity for Vault
+The following jobs access Vault but are not configured for workload identity.
+
+You should redeploy them before fully migrating to workload identities with
+Vault to prevent unexpected errors if their tokens need to be recreated.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID       Namespace  Type     Status
+example  default    service  running
+
+Outdated Nodes
+The following nodes are running a version of Nomad that does not support using
+workload identities with Vault.
+
+You should upgrade them to Nomad 1.7 before fully migrating to workload
+identities with Vault to prevent unexpected errors if they receive allocations
+for jobs that use Vault.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID        Name      Address        Version  Drain  Eligibility  Status
+049f7683  client-1  192.168.0.186  1.6.4    false  eligible     ready
+
+Vault Tokens
+The following Vault ACL tokens were created by Nomad but will not be
+automatically revoked after migrating to workload identities. They will expire
+once their TTL reaches zero.
+
+Accessor ID               Allocation ID  Node ID   Configured TTL
+czh9MPcRXzAhxBL9XKyb3Kh1  f00893d4       049f7683  60
+```
+
+[vaultenv]: /vault/docs/commands#environment-variables
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.7.x/content/docs/commands/status.mdx b/content/nomad/v1.7.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.7.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/system/index.mdx b/content/nomad/v1.7.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.7.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.7.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.7.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..3e90a45c4f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: tls ca create'
+description: |
+  This command creates a Certificate Authority that can be used to create
+  self signed certificates to be used for Nomad TLS setup.
+---
+
+# Command: nomad tls ca create
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## CA Create Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.7.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..0261571b19
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: tls ca info'
+description: |
+  This command displays relevant information that is contained within a
+  Certificate Authority certificate.
+---
+
+# Command: nomad tls ca info
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.7.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..d0fc2d5bb0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Create'
+description: |
+  This command creates a Certificate that can be used for Nomad TLS setup.
+---
+
+# Command: nomad tls cert create
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Command Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-cluster-region=<string>`: DEPRECATED please use `-region`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.7.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.7.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..c37f6a54c0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Info'
+description: |
+  This command displays relevant information that is contained within a
+  certificate.
+---
+
+# Command: nomad tls cert info
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.7.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..1e580053ee
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: tls'
+description: |
+  The tls command is used to help with creating a Certificate Authority 
+  and up self signed certificates for Nomad TLS configuration.
+---
+
+# Command: tls
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/commands/ui.mdx b/content/nomad/v1.7.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/get.mdx b/content/nomad/v1.7.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..3639942887
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: "Command: var get"
+description: |-
+  The "var get" command retrieves the variable at the given path from
+  Nomad. If no variable exists at that path, an error is returned.
+---
+
+# Command: var get
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/index.mdx b/content/nomad/v1.7.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..695bf78dd9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: "Commands: var"
+description: |-
+  The "var" command groups subcommands for interacting with Nomad variables.
+---
+
+# Command: var
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+- [`var lock`][lock] - Acquire a lock over a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
+[lock]: /nomad/docs/commands/var/lock
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/init.mdx b/content/nomad/v1.7.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..8a99bf81fa
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: var init'
+description: |
+  Generate an example variable specification.
+---
+
+# Command: var init
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/list.mdx b/content/nomad/v1.7.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d8974ffff2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: "Command: var list"
+description: |-
+  The "var list" command lists data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# Command: var list
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/lock.mdx b/content/nomad/v1.7.x/content/docs/commands/var/lock.mdx
new file mode 100644
index 0000000000..0e9921181f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/lock.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: "Command: var lock"
+description: |-
+  The "var lock" command locks a variable, only allowing the lock owner to modify it.
+---
+
+# Command: var lock
+
+The `var lock` command holds a lock on a [variable][].
+
+## Usage
+
+```plaintext
+nomad var lock [options] <lock spec file reference> child...
+nomad var lock [options] <path to store variable> [<variable spec file reference>] child
+```
+
+The lock command provides a mechanism for simple distributed locking. A lock
+is created in the given variable, and only when held, is a child process invoked.
+
+The lock command can be called on an existing variable or an entire new variable
+specification can be provided to the command from a file by using an
+@-prefixed path to a variable specification file. Items to be stored in the 
+variable can be supplied using the specification file as well. 
+
+Nomad lock launches its children in a shell. By default, Nomad will use the
+shell defined in the environment variable SHELL. If SHELL is not defined, 
+it will default to /bin/sh. It should be noted that not all shells terminate
+child processes when they receive SIGTERM. Under Ubuntu, /bin/sh is linked 
+to dash, which does not terminate its children. In order to ensure that 
+child processes are killed when the lock is lost, be sure to set the SHELL
+environment variable appropriately, or run without a shell by setting -shell=false. 
+ 
+If [ACLs][] are enabled, this command requires the 'variables:write' capability
+for the destination namespace and path.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Lock Options
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `ttl`: Optional, TTL for the lock, time the variable will be locked. Defaults to 15s.
+
+- `delay`: Optional, time the variable is blocked from locking when a lease is not renewed.	
+	Defaults to 15s.
+
+- `max-retry`:Optional, max-retry up to this number of times if Nomad returns a 500 error
+	while monitoring the lock. This allows riding out brief periods of
+	unavailability without causing leader elections, but increases the amount of
+	time required to detect a lost lock in some cases. Defaults to 5. Set to 0 to
+	disable.
+
+- `shell`: Optional, use a shell to run the command (can set a custom shell via		
+	the SHELL environment variable). The default value is true.
+
+## Examples
+
+Attempts to acquire a lock over the variable at path "secret/creds" for a time of 
+15s and executes  `nomad job run webapp.nomad.hcl` if it succeeds:
+
+```shell-session
+$ nomad var lock -ttl=15s secret/creds "nomad job run webapp.nomad.hcl"
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var lock secret/foo @spec.nv.json `nomad job run webapp.nomad.hcl`
+```
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]:  /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
+[ACL]: /nomad/docs/other-specifications/acl-policy#variables
+
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.7.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..c924fa77ab
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: "Command: var purge"
+description: |-
+  The "var purge" command permanently removes the specified variable
+  from Nomad.
+---
+
+# Command: var purge
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Command Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.7.x/content/docs/commands/var/put.mdx b/content/nomad/v1.7.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..34a361ad3a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: "Command: var put"
+description: |-
+  The "var put" command writes a variable to the given path in Nomad.
+---
+
+# Command: var put
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.7.x/content/docs/commands/version.mdx b/content/nomad/v1.7.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b58b9ae222
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..a1ab1352f0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..726ed55b84
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.7.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.7.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..1a93d7f6c0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.7.x/content/docs/concepts/acl.mdx b/content/nomad/v1.7.x/content/docs/concepts/acl.mdx
new file mode 100644
index 0000000000..aee744db85
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/acl.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Access Control List (ACL)
+description: Learn about Nomad's ACL subsystem
+---
+
+# Access Control List (ACL)
+
+The Nomad ACL system is designed to be intuitive, high-performance, and to
+provide administrative insight. At the highest level, there are four major
+components to the ACL system: tokens, policies, roles, and capabilities. The
+two components named auth methods and binding rules are specific to Nomad's
+Single Sign-On (SSO) ACL capabilities.
+
+The Nomad [access control tutorials][] provide detailed information and
+guidance on Nomad ACL system.
+
+### Policy
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy comprises one or more rules. The rules define the capabilities of a
+Nomad ACL token for accessing the objects in a Nomad cluster, objects like
+namespaces, node, agent, operator, quota, etc. For more information on writing
+policies, see the [ACL policy reference doc][].
+
+### Role
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+### Token
+
+Requests to Nomad are authenticated using a bearer token. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. `Local` tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+### Workload Identity
+
+Nomad allocations can receive workload identities in the form of a
+[JSON Web Token (JWT)][jwt]. The
+[Workload Identity concept page][workload identity] has more information on
+this topic.
+
+### Auth Method
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+### Binding Rule
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[access control tutorials]: /nomad/tutorials/access-control
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
+[vault]: https://www.vaultproject.io/
diff --git a/content/nomad/v1.7.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.7.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..f204891550
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.7.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.7.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.7.x/content/docs/concepts/cpu.mdx b/content/nomad/v1.7.x/content/docs/concepts/cpu.mdx
new file mode 100644
index 0000000000..103bd9e55e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/cpu.mdx
@@ -0,0 +1,331 @@
+---
+layout: docs
+page_title: CPU
+description: Learn about how Nomad manages CPU resources.
+---
+
+# Modern Processors
+
+Every Nomad node has a Central Processing Unit (CPU) providing the computational
+power needed for running operating system processes. Nomad uses the CPU to
+run tasks defined by the Nomad job submitter. For Nomad to know which nodes
+have sufficient capacity for running a given task, each node in the cluster
+is fingerprinted to gather information about the performance characteristics
+of its CPU. The two metrics associated with each Nomad node with regard to
+CPU performance are its bandwidth (how much it can _compute_) and the number
+of cores.
+
+Modern CPUs may contain heterogeneous core types. Apple introduced the M1 CPU
+in 2020 which contains both _performance_ (P-Core) and _efficiency_ (E-Core)
+types. Each core type operates at a different base frequency. Intel introduced
+a similar topology in its Raptor Lake chips in 2022. When fingerprinting
+the characteristics of a CPU Nomad is capable of taking these advanced CPU
+topologies into account.
+
+[![PE Cores](/img/nomad-pe-cores.png)](/img/nomad-pe-cores.png)
+
+## Calculating CPU Resources
+
+The total CPU bandwidth of a Nomad node is the sum of the product between the
+frequency of each core type and the total number of cores of that type in the
+CPU.
+
+```
+bandwidth = (p_cores * p_frequency) + (e_cores * e_frequency)
+```
+
+The total number of cores is computed by summing the number of P-Cores and the
+number of E-Cores.
+
+```
+cores = p_cores + e_cores
+```
+
+Nomad does not distinguish between logical and physical CPU cores. One of the
+defining differences between the P-Core and E-Core types is that the E-Cores
+do not support hyperthreading, whereas P-Cores do. As such a single physical
+P-Core is presented as 2 logical cores, and a single E-Core is presented as 1
+logical core.
+
+The example below is from a Nomad node with an Intel i9-13900 CPU. It is made
+up of mixed core types, with a P-Core base frequency of 2 GHz and an E-Core
+base frequency of 1.5 GHz.
+
+These characteristics are reflected in the `cpu.frequency.performance` and
+`cpu.frequency.efficiency` node attributes respectively.
+
+```text
+cpu.arch                        = amd64
+cpu.frequency.efficiency        = 1500
+cpu.frequency.performance       = 2000
+cpu.modelname                   = 13th Gen Intel(R) Core(TM) i9-13900
+cpu.numcores                    = 32
+cpu.numcores.efficiency         = 16
+cpu.numcores.performance        = 16
+cpu.reservablecores             = 32
+cpu.totalcompute                = 56000
+cpu.usablecompute               = 56000
+```
+
+## Reserving CPU Resources
+
+In the fingerprinted node attributes, `cpu.totalcompute` indicates the total
+amount of CPU bandwidth the processor is capable of delivering. In some cases it
+may be beneficial to reserve some amount of a node's CPU resources for use by
+the operating system and other non-Nomad processes. This can be done in client
+configuration.
+
+The amount of reserved CPU can be specified in bandwidth via `cpu`.
+
+```hcl
+client {
+  reserved {
+    cpu = 3000 # mhz
+  }
+}
+```
+
+Or as a specific set of `cores` on which to disallow the scheduling of Nomad
+tasks. This capability is available on Linux systems only.
+
+```hcl
+client {
+  reserved {
+    cores = "0-3"
+  }
+}
+```
+
+When the CPU is constrained by one of the above configurations, the node
+attribute `cpu.usablecompute` indicates the total amount of CPU bandwidth
+available for scheduling of Nomad tasks.
+
+## Allocating CPU Resources
+
+When scheduling jobs, a Task must specify how much CPU resource should be
+allocated on its behalf. This can be done in terms of bandwidth in MHz with the
+`cpu` attribute. This MHz value is translated directly into [cpushares][] on
+Linux systems.
+
+```hcl
+task {
+  resources {
+    cpu = 2000 # mhz
+  }
+}
+```
+
+Note that the isolation mechanism around CPU resources is dependent on each task
+driver and its configuration. The standard behavior is that Nomad ensures a task
+has access to _at least_ as much of its allocated CPU bandwidth. In which case
+if a node has idle CPU capacity, a task may use additional CPU resources.  Some
+task drivers enable limiting a task to use only the amount of bandwidth
+allocated to the task, described in the [CPU Hard Limits](#cpu-hard-limits)
+section below.
+
+On Linux systems, Nomad supports reserving whole CPU cores specifically for a
+task. No task will be allowed to run on a CPU core reserved for another task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+  }
+}
+```
+
+Nomad Enterprise supports NUMA aware scheduling, which enables operators to
+more finely control which CPU cores may be reserved for tasks.
+
+### CPU Hard Limits
+
+Some task drivers support the configuration option `cpu_hard_limit`. If enabled
+this option restricts tasks from bursting above their CPU limit even when there
+is idle capacity on the node. The tradeoff is consistency versus utilization.
+A task with too few CPU resources may operate fine until another task is placed
+on the node causing a reduction in available CPU bandwidth, which could cause
+disruption for the underprovisioned task.
+
+### CPU Environment Variables
+
+To help tasks understand the resources available to them, Nomad sets the
+following environment variables in their runtime environment.
+
+
+- `NOMAD_CPU_LIMIT` - The amount of CPU bandwidth allocated on behalf of the
+  task.
+- `NOMAD_CPU_CORES` - The set of cores in [cpuset][] notation reserved for the
+  task. This value is only set if `resources.cores` is configured.
+
+```sh
+NOMAD_CPU_CORES=3-5
+NOMAD_CPU_LIMIT=9000
+```
+
+# NUMA
+
+Nomad clients are commonly provisioned on real hardware in an on-premise
+environment or in the cloud on large `.metal` instance types. In either case it
+is likely the underlying server is designed around a [NUMA topology][numa_wiki].
+Servers that contain multiple CPU sockets or multiple RAM banks per CPU socket
+are characterized by the non-uniform access times involved in accessing system
+memory.
+
+[![NUMA](/img/nomad-numa.png)](/img/nomad-numa.png)
+
+The simplified example machine above has the following topology
+- 2 physical CPU sockets
+- 4 system memory banks, 2 per socket
+- 8 physical cpu cores (4 per socket)
+- 2 logical cpu cores per physical core
+- 4 PCI devices, 1 per memory bank
+
+### Optimizing performance
+
+Operating system processes take longer to access memory across a NUMA boundary.
+
+Using the example above if a task is scheduled on Core 0, accessing memory in
+Mem 1 might take 20% longer than accessing memory in Mem 0, and accessing memory
+in Mem 2 might take 300% longer.
+
+The extreme differences are due to various physical hardware limitations. A core
+accessing memory in its own NUMA node is optimal. Programs which perform a high
+throughput of reads or writes to/from system memory will have their performance
+substantially hindered by not optimizing their spatial locality with regard to
+the systems NUMA topology.
+
+### SLIT tables
+
+Modern machines will define System Locality Distance Information (SLIT) tables
+in their firmware. These tables are understood and made referenceable by the
+Linux kernel. There are two key pieces of information provided by SLIT tables:
+- Which CPU cores belong to which NUMA nodes
+- The penalty incurred for accessing each NUMA node from a core in every other
+NUMA node
+
+The `lscpu` command can be used to describe the Core associativity on a machine.
+For example on an `r6a.metal` EC2 instance:
+
+```shell-session
+$ lscpu | grep NUMA
+NUMA node(s):           4
+NUMA node0 CPU(s):      0-23,96-119
+NUMA node1 CPU(s):      24-47,120-143
+NUMA node2 CPU(s):      48-71,144-167
+NUMA node3 CPU(s):      72-95,168-191
+```
+
+And the associated performance degradations are available via `numactl`:
+
+```shell-session
+$ numactl -H
+available: 4 nodes (0-3)
+...
+node distances:
+node   0   1   2   3
+  0:  10  12  32  32
+  1:  12  10  32  32
+  2:  32  32  10  12
+  3:  32  32  12  10
+```
+
+These SLIT table "node distance" values are presented as approximate relative
+ratios. The value of 10 represents an optimal situation where a memory access
+is occurring from a CPU that is part of the same NUMA node. A value of 20 would
+indicate a 200% performance degradation, 30 for 300%, etc.
+
+### Node Attributes
+
+Nomad clients will fingerprint the machine's NUMA topology and export the
+core associativity as node attributes. This data can provide a Nomad operator
+a better understanding of when it might be useful to make use of NUMA aware
+scheduling for certain workloads.
+
+```
+numa.node.count       = 4
+numa.node0.cores      = 0-23,96-119
+numa.node1.cores      = 24-47,120-143
+numa.node2.cores      = 48-71,144-167
+numa.node3.cores      = 72-95,168-191
+```
+
+## NUMA aware scheduling <EnterpriseAlert inline />
+
+Nomad Enterprise is capable of scheduling tasks in a way that is optimized for
+the NUMA topology of a client node. A task may specify a `numa` block indicating
+its NUMA optimization preference.
+
+```hcl
+task {
+  resources {
+    cores = 6
+    numa {
+      affinity = "require"
+	}
+  }
+}
+```
+
+### `affinity` Options
+
+There are three supported affinity options: `none`, `prefer`, and `require`,
+each with their own advantages and tradeoffs.
+
+#### option `none`
+
+In the `none` mode the Nomad scheduler leverages the apathy of jobs without
+preference of NUMA affinity to help reduce core fragmentation within NUMA nodes.
+It does so by bin-packing the core request of these jobs onto the NUMA nodes
+with the fewest unused cores available.
+
+The `none` mode is the default mode if the `numa` block is not specified.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "none"
+  }
+}
+```
+
+#### option `prefer`
+
+In the `prefer` mode the Nomad scheduler uses the hardware topology of a node
+to calculate an optimized selection of available cores, but does not limit
+those cores to come from a single NUMA node.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "prefer"
+  }
+}
+```
+
+#### option `require`
+
+In the `require` mode the Nomad scheduler uses the topology of each potential
+client to find a set of available CPU cores that belong to the same NUMA node.
+If no such set of cores can be found, that node is marked exhausted for the
+resource of `numa-cores`.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "require"
+  }
+}
+```
+
+## Virtual CPU Fingerprinting
+
+When running on a virtualized host such as Amazon EC2 Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions will
+require installing the `dmidecode` package manually.
+
+[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
+[cpushares]: https://www.redhat.com/sysadmin/cgroups-part-two
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
diff --git a/content/nomad/v1.7.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.7.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..74dff6d50a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,491 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.7.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.7.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..d5b2f7cf42
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses a [gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol)
+to manage membership. This is provided through the use of the [Serf library](https://www.serf.io/).
+The gossip protocol used by Serf is based on
+["SWIM: Scalable Weakly-consistent Infection-style Process Group Membership Protocol"](https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf),
+with a few minor adaptations. There are more details about [Serf's protocol here](https://www.serf.io/docs/concepts/gossip.html).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate in.
+Membership information provided by the gossip pool allows servers to perform cross region
+requests. The integrated failure detection allows Nomad to gracefully handle an entire region
+losing connectivity, or just a single server in a remote region. The gossip protocol
+is also used to detect servers in the same region to perform automatic clustering
+via the [consensus protocol](/nomad/docs/concepts/consensus).
+
+All of these features are provided by leveraging [Serf](https://www.serf.io/). It
+is used as an embedded library to provide these features. From a user perspective,
+this is not important, since the abstraction should be masked by Nomad. It can be useful
+however as a developer to understand how this library is leveraged.
diff --git a/content/nomad/v1.7.x/content/docs/concepts/index.mdx b/content/nomad/v1.7.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.7.x/content/docs/concepts/node-pools.mdx b/content/nomad/v1.7.x/content/docs/concepts/node-pools.mdx
new file mode 100644
index 0000000000..e87474f7cb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/node-pools.mdx
@@ -0,0 +1,379 @@
+---
+layout: docs
+page_title: Node Pools
+description: Learn about the internal architecture of Nomad.
+---
+
+# Node Pools
+
+Node pools are a way to group clients and segment infrastructure into logical
+units that can be targeted by jobs for a strong control over where allocations
+are placed.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+A node pool can be created using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config  block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/docs/commands/node-pool/apply
+[cli_agent_np]: /nomad/docs/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..74c13eb651
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Network Plugins
+description: Learn how Nomad manages custom user-specified network configurations.
+---
+
+# Network plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#linux-post-installation-steps
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..a7f5a4ed19
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..79e2aa1a75
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.7.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.7.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..f549db2f5a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation FSIsolation
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propagating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+}
+```
+
+The file system isolation options are:
+
+- `FSIsolationImage`: The task driver isolates tasks as machine images.
+- `FSIsolationChroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `FSIsolationNone`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
diff --git a/content/nomad/v1.7.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.7.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..32fa6d8b67
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature introduced in Nomad 0.9.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.7.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.7.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..b50949ae0a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: Placement
+description: Learn about how placements are computed in Nomad.
+---
+
+# Placement
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+### Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+#### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+#### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+### Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+### Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+
+[api_client_metadata]: /nomad/api-docs/client#update-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/concepts/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.7.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.7.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..291008f78b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Prior to Nomad 0.9, when a cluster is at capacity, any allocations that result from a newly scheduled or updated
+job remain in the pending state until sufficient resources become available - regardless of the defined priority.
+This leads to priority inversion, where a low priority task can prevent high priority tasks from completing.
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default in Nomad 0.9 for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.7.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.7.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..e6b39f2498
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.7.x/content/docs/concepts/security.mdx b/content/nomad/v1.7.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..739932e206
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/security.mdx
@@ -0,0 +1,339 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** -
+  Access to read and write to a namespace can be
+  controlled to allow for granular access to job information managed within a
+  multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)**
+
+  - Mutual TLS (mTLS) enables [mutual
+    authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+    security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                                         |
+| -------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                                 |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
+
+
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
diff --git a/content/nomad/v1.7.x/content/docs/concepts/variables.mdx b/content/nomad/v1.7.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..3cd877e626
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: Variables
+description: Learn about the Nomad Variables feature
+---
+
+# Nomad Variables
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to [provide such configuration to tasks](/nomad/docs/job-specification/template#nomad-variables),
+but prior to Nomad 1.4 has left the role of storing that configuration to
+external services such as [HashiCorp Consul] and [HashiCorp Vault].
+
+Nomad Variables provide the option to store configuration at file-like paths
+directly in Nomad's state store. You can [access these variables](/nomad/docs/job-specification/template#nomad-variables) directly from
+your task `template`s. The contents of these variables are encrypted
+and replicated between servers via raft. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the Variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as Variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. See [Key Management][] for details.
+
+## ACL for Variables
+
+Every Variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to Variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for Variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+In Nomad 1.4.0 tasks can only access Variables with the [`template`] block. The
+[workload identity] for each task grants it automatic read and list access to
+Variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to Variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+## Locks
+
+Nomad provides the ability to block a variable from being updated for a period
+of time by setting a lock on it. Once a variable is locked, it can be read by
+everyone, but it can only be updated by the lock holder.
+
+The locks are designed to provide granular locking and are heavily inspired by
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems][].
+
+A lock is composed of an ID, a TTL, and a lock delay. The ID is generated by
+the Nomad Server and must be provided on every request to modify the variable's
+items or the lock itself. The TTL defines the time the lock will be held; if the
+lock needs to be in place for longer, it can be renewed for as many new periods
+as wanted.
+
+Once it is no longer needed, it must be released. If by the time the TTL expires,
+and no renew or release calls were made, the variable will remain locked for at
+least the lock delay duration, to avoid a possible split-brain situation, where
+there are two holders at the same time.
+
+### Leader election backed by Nomad Variable Locks
+
+For some applications, like HDFS or the Nomad Autoscaler, it is necessary to
+have multiple instances running to ensure redundancy in case of a failure, but
+only one of them may be active at a time as a leader.
+
+As part of the [Go Package][], Nomad offers a helper that takes one variable and
+uses a lock over it as a sync mechanism to run multiple instances but always
+keeping just one running at any given time, using the following algorithm:
+
+[![Leader Election Helper](/img/nomad-vars-leader-election-sdk.png)](/img/nomad-vars-leader-election-sdk.png)
+
+As soon as any instance starts, it tries to lock the sync variable. If it succeeds,
+it continues to execute while a secondary thread is in charge of keeping track of
+the lock and renewing it when necessary. If by any chance the renewal fails,
+the main process is forced to return, and the instance goes into standby until it
+attempts to acquire the lock over the sync variable. 
+
+Only threads 1 and 3 or thread 2 are running at any given time, because every 
+instance is either executing as normal while renewing the lock or waiting for a 
+chance to acquire it and run.
+
+When the main process, or protected function, returns, the helper releases the 
+lock, allowing a second instance to start running.
+
+To see it implemented live, look for the [`nomad var lock`][] command 
+implementation or the [Nomad Autoscaler][] High Availability implementation.
+
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems]: https://research.google/pubs/pub27897/
+[`nomad var lock`]: /nomad/docs/commands/var
+[Go Package]: https://pkg.go.dev/github.com/hashicorp/nomad/api
+[implementation]: https://github.com/hashicorp/nomad/blob/release/1.7.0/command/var_lock.go#L240
+[Nomad Autoscaler]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.4.0/command/agent.go#L392
diff --git a/content/nomad/v1.7.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.7.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..3854896a4d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Learn about Nomad's workload identity feature
+---
+
+# Workload Identity
+
+Every workload running in Nomad is given a default identity. When an
+[allocation][] is accepted by the [plan applier][], the leader generates a
+Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring.
+Additional workload identities may be defined in tasks and services using the
+[`identity`][identity-block] block.
+
+## Workload Identity Claims
+
+Nomad workload identity for tasks include the following identity claims.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+Workload identities for Consul services have a claim with the service name
+instead of the task name.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Workload identities for tasks that use Vault have an additional claim for
+[`vault.role`][jobspec_vault_role] if a role is specified in the job.
+
+-> **Note:** This claim will *not* be added if the role is inherited from
+the [agent configuration][vault_role_agent_config] and is not present
+in the Nomad job specification.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+  "vault_role": "nomad-jwt-login"
+}
+```
+
+### Nomad Enterprise <EnterpriseAlert inline />
+
+In Nomad Enterprise, tasks and services with a [`consul`][jobspec_consul] block
+that defines a [`namespace`][jobspec_consul_ns] value, or inside a `group`
+block that does it, have an additional claim called `consul_namespace`.
+
+```json
+{
+  "consul_namespace": "prod",
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Similarly, tasks with a [`vault.namespace`][jobspec_vault_ns] value have the additional claim
+`vault_namespace`.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+  "vault_namespace": "prod",
+}
+```
+
+## Workload Identity for Nomad
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+### Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+### Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+### Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identity for Consul and Vault
+
+Consul and Vault can be configured to accept workload identities from Nomad for
+authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
+integration pages for more information.
+
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[jobspec_consul]: /nomad/docs/job-specification/consul
+[jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace
+[jobspec_vault_ns]: /nomad/docs/job-specification/vault#namespace
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[vault_role_agent_config]: /nomad/docs/configuration/vault#create_from_role
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[taskapi]: /nomad/api-docs/task-api
+[consul_int]: /nomad/docs/integrations/consul-integration
+[vault_int]: /nomad/docs/integrations/vault-integration
diff --git a/content/nomad/v1.7.x/content/docs/configuration/acl.mdx b/content/nomad/v1.7.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..07c6437783
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. See [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.7.x/content/docs/configuration/audit.mdx b/content/nomad/v1.7.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.7.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.7.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.7.x/content/docs/configuration/client.mdx b/content/nomad/v1.7.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..b91b3638b8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/client.mdx
@@ -0,0 +1,748 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID. Before
+  Nomad 0.6 the default was to use the system UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints. When hairpin mode
+  is enabled, allocations are able to reach their own IP and **all ports** bound
+  to it. Changing this value requires a reboot of the client host to take
+  effect.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers. If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers. If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(int: 0)` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path      = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr           = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/runtime/interpolation
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/docs/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.7.x/content/docs/configuration/consul.mdx b/content/nomad/v1.7.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..fd5e05df90
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,385 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+In Nomad Enterprise, you may specify multiple `consul` blocks to configure
+access to multiple Consul clusters. Each Consul cluster must have a different
+value for the [`name`](#name) field.
+
+## `consul` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`consul.cluster`][] or [`service.cluster`][] fields. In Nomad
+  Community Edition, only the `"default"` cluster will be used, so this field
+  should be omitted.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the [Consul
+  namespace](/consul/docs/enterprise/namespaces) used by the Consul
+  integration. If non-empty, this namespace will be used on all Consul API calls
+  and for Consul Connect configurations, unless overridden by the job's
+  [`consul.namespace`][] field.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and client services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes. Will default to the `CONSUL_HTTP_TOKEN`
+  environment variable if set.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`][] set to `true`.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `client_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check is critical.
+
+- `client_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check shows a warning.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+  certificate used for communication between Connect sidecar proxies and Consul
+  agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+  <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. See
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not
+  include the values for the ACL `token` or `auth`. This option should be
+  disabled in environments where Consul ACLs are not enabled.
+
+- `service_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for services.
+
+- `task_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for tasks.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `server_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check is critical.
+
+- `server_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check shows a warning.
+
+- `service_identity` <code>([Identity](#service_identity-parameters): nil)</code> - Specifies
+  a default Workload Identity to use when obtaining Service Identity tokens from
+  Consul to register services. Refer to [Workload Identity](#workload-identity)
+  for a recommended configuration.
+
+- `task_identity` <code>([Identity](#task_identity-parameters): nil)</code> - Specifies a
+  default Workload Identity to use when obtaining Consul tokens from Consul to
+  support [`template`][] blocks. Refer to [Workload
+  Identity](#workload-identity) for a recommended configuration.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul
+  Connect enabled services listed in the job. This option should be disabled in
+  an untrusted environment.
+
+## Workload Identity
+
+The `service_identity` and `task_identity` blocks accept all the same values as
+the job specification's [`identity`][identity_block] (except that the
+`service_identity` ignores the `env` and `file` fields). By ensuring these
+blocks are set on the Nomad servers, you can automatically migrate your existing
+jobs to use Workload Identity without modifying the job specification and
+resubmitting them.
+
+The recommended configuration for `service_identity` and `task_identity` is as
+follows. See [Migrating to Using Workload Identity with Consul][] for details on
+how to configure Consul to accept these identities. Note that the `ttl` field
+here refers to the TTL of the Nomad identity and not the Consul token.
+
+```hcl
+consul {
+  service_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+
+  task_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+}
+```
+
+### `service_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### `task_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN_consul_default` (or `NOMAD_TOKEN_consul_<name>` depending
+  on the [`name`](#name) field) environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_consul_default.jwt` (or
+  `secrets/nomad_consul_<name>.jwt` depending on the [`name`](#name) field). If
+  the [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace <EnterpriseAlert inline/>
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
+[`consul.cluster`]: /nomad/docs/job-specification/group#cluster
+[`service.cluster`]: /nomad/docs/job-specification/service#cluster
+[identity_block]: /nomad/docs/job-specification/identity
+[`template`]: /nomad/docs/job-specification/template
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[auth-method]: /consul/docs/security/acl/auth-methods/jwt
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[consul_bound_aud]: /consul/docs/security/acl/auth-methods/jwt#boundaudiences
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
diff --git a/content/nomad/v1.7.x/content/docs/configuration/index.mdx b/content/nomad/v1.7.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..08408a681f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/index.mdx
@@ -0,0 +1,401 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - Available in Nomad 0.10.3 and later, this is a nested object that
+  configures limits that are enforced by the agent. The following parameters
+  are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://godoc.org/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.7.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.7.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.7.x/content/docs/configuration/reporting.mdx b/content/nomad/v1.7.x/content/docs/configuration/reporting.mdx
new file mode 100644
index 0000000000..f89c6013f5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/reporting.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: reporting Block - Agent Configuration
+description: >-
+  The "reporting" block configures the Nomad agents automated license
+  utilization reporting.
+---
+
+# `reporting` Block
+
+<Placement groups={['reporting']} />
+
+The `reporting` block configures the Nomad agents automated license utilization
+reporting. This is an Enterprise-only feature and the configuration applies to
+agents running with [server mode enabled][server_mode_enabled].
+
+For more information about automated license utilization reporting, please see the
+[guide][automated_license_utilization_reporting].
+
+```hcl
+reporting {
+    license {
+      enabled = true
+    }
+}
+```
+
+## `reporting` Parameters
+
+- `license` <code>([license](#license-block): default)</code> - Configures
+  automated license utilization reporting.
+
+## `license` Block
+
+- `enabled` `(bool: true)` - Specifies whether automated license utilization
+  reporting should be enabled and run.
+
+[server_mode_enabled]: /nomad/docs/configuration/server#enabled
+[automated_license_utilization_reporting]: /nomad/docs/enterprise/license/utilization-reporting
diff --git a/content/nomad/v1.7.x/content/docs/configuration/search.mdx b/content/nomad/v1.7.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.7.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.7.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.7.x/content/docs/configuration/server.mdx b/content/nomad/v1.7.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..a30bb2f601
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/server.mdx
@@ -0,0 +1,525 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens. Non-authoritative regions will replicate from
+  the authoritative to act as a mirror. By default, the local region is assumed
+  to be authoritative. Setting `authoritative_region` assumes that ACLs have
+  been bootstrapped in the authoritative region. See [Configure for multiple
+  regions][] in the ACLs tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m". `job_gc_interval`
+  was introduced in Nomad 0.10.0.
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+  `default_scheduler_config` was introduced in Nomad 0.10.4.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". See [Client Heartbeats](#client-heartbeats) below for details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients
+  must heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". See [Client Heartbeats](#client-heartbeats) below
+  for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. See [Client Heartbeats](#client-heartbeats)
+  below for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key from the [JWKS URL][] before
+  it is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+- `oidc_issuer` `(string: "")` - Specifies the Issuer URL for [Workload
+    Identity][wi] JWTs. For example, `"https://nomad.example.com"`. If set the
+    `/.well-known/openid-configuration` HTTP endpoint is enabled for third
+    parties to discover Nomad's OIDC configuration.  Once set `oidc_issuer`
+    *cannot be changed* without invalidating Workload Identities that have the
+    old issuer claim. For this reason it is suggested to set `oidc_issuer` to a
+    proxy in front of Nomad's HTTP API to ensure a stable DNS name can be used
+    instead of a potentially ephemeral Nomad server IP.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`max_client_disconnect`][max_client_disconnect] is set)
+and rescheduled.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer a `down` Client's workload will
+  take to be rescheduled.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  rescheduled.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO (see below)       |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and reschedules their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator gossip keyring generate`]: /nomad/docs/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[max_client_disconnect]: /nomad/docs/job-specification/group#max-client-disconnect
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[wi]: /nomad/docs/concepts/workload-identity
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[JWKS URL]: /nomad/api-docs/operator/keyring#list-active-public-keys
diff --git a/content/nomad/v1.7.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.7.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..74f4dbb2f2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,298 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max      = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of Nomad server
+  addresses and [Cloud Auto-join](#cloud-auto-join) configurations that are
+  joined as cluster members. This is similar to [`start_join`](#start_join),
+  but join attempts are retried up to [retry_max](#retry_max) times.
+  Further, `retry_join` is available to both Nomad servers and clients, while
+  `start_join` is only defined for Nomad servers. This is useful for cases where
+  we know the address will become available eventually. Use `retry_join` with an
+  array as a replacement for `start_join`, **do not use both options**.
+
+  Server addresses must conform to the [server address format](#server-address-format).
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Auto-join configurations must conform to the [Cloud Auto-join format](#cloud-auto-join).
+
+  Cloud-Auto join using `go-discover` to join an AWS EC2 cluster.
+
+  ```hcl
+  server_join {
+    retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Cloud-Auto join using `go-netaddrs` to join a Hetzner cluster of servers
+  labeled with `nomad-server=true` using the `hcloud` CLI.
+
+  ```hcl
+  server_join {
+    retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+  }
+  ```
+
+  Server addresses and Cloud Auto-join configurations may be used together.
+  This is a mixed configuration containing a server address and Cloud Auto-join
+  configuration.
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See [server address format](#server-address-format) for more information
+  about expected server address formats and [Cloud Auto-join](#cloud-auto-join)
+  for more information on expected Cloud Auto-join formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+`retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud provider metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+`retry_join`'s Cloud Auto-join allows Nomad to automatically discover cluster
+server addresses using cloud provider metadata. Cloud Auto-join allows both
+[go-discover](https://github.com/hashicorp/go-discover) and
+[go-netaddrs](https://github.com/hashicorp/go-netaddrs) formats.
+
+Configurations prefixed with `provider=` use `go-discover` whereas
+configurations prefixed with `exec=` use `go-netaddrs`. For cloud providers not
+supported by `go-discover`, use `go-netaddrs`.
+
+### `go-discover` Configurations
+
+`go-discover` configurations are prefixed with `provider=`.
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+#### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+##### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+#### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+#### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+##### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
+
+
+### `go-netaddrs` Configurations
+
+`go-netaddrs` configurations are prefixed with `exec=`.
+
+What follows the `exec=` prefix may be any executable program and its arguments.
+Commands run by `go-netaddrs` must return a list of space-delimited IPv4 or IPv6
+addresses and exit with code `0` on success and non-zero on failure.
+
+You can refer to the executable by its absolute file system path, or by
+the executable's name if it can be found on the Nomad agent's PATH. See
+[executables in the current directory](https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory)
+for more details on the lookup behavior.
+
+Example `go-netaddrs` configuration.
+
+```hcl
+server_join {
+  retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+}
+```
+
+Here, `hcloud`'s newline-delimited output has been re-formatted as space-
+delimited by piping its output into `tr`.
+
+Output of an example `go-netaddrs` executable
+
+```
+"1.1.1.1 2.2.2.2"
+```
+
+Visit [go-netaddrs](https://github.com/hashicorp/go-netaddrs) for more
+information on go-netaddrs configuration.
diff --git a/content/nomad/v1.7.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.7.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..d76a07b9f4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `in_memory_collection_interval` `(duration: 10s)` Configures the in-memory
+  sink collection interval. This sink is always configured and backs the JSON
+  metrics API endpoint. This option is particularly useful for debugging or
+  development purposes, where aggressive collection is required.
+
+- `in_memory_retention_period` `(duration: 1m)` Configures the in-memory sink
+  retention period. This sink is always configured and backs the JSON metrics
+  API endpoint. This option is particularly useful for debugging or development
+  purposes.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.7.x/content/docs/configuration/tls.mdx b/content/nomad/v1.7.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..4957e5bed1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to enforce
+secure cluster communication between servers, clients, and between. Note that in
+most cases, this is mutual TLS (mTLS) where both ends of the connection
+authenticate each other. The Nomad documentation will typically use "TLS" to
+refer to this communication except when it is potentially ambiguous between TLS
+and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
diff --git a/content/nomad/v1.7.x/content/docs/configuration/ui.mdx b/content/nomad/v1.7.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..a51c912582
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI will default to a black background. HEX values  
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI will default to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.7.x/content/docs/configuration/vault.mdx b/content/nomad/v1.7.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..8d448a70d3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, tasks can use [workload
+identities][workload_id] to receive Vault ACL tokens automatically.
+
+Alternatively, Nomad servers may be configured with a high-privileged Vault
+token that is used to derive fine-grained tokens for tasks. Refer to
+[Token-based Authentication](#token-based-authentication) for configuration
+details. This workflow is deprecated and will be removed in a future version of
+Nomad. Using using workload identities is strongly recommended as it is easier
+to manage and more secure.
+
+Refer to the [Nomad and Vault Integration][nomad-vault] page for more
+information about the Vault integration.
+
+```hcl
+vault {
+  enabled = true
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+  }
+}
+```
+
+In Nomad Enterprise, you may specify multiple `vault` blocks to configure access
+to multiple Vault clusters. Each Vault cluster must have a different value for
+the [`name`](#name) field.
+
+## `vault` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+The placement also depends on the authentication strategy used. This section
+describes the parameter organization for workload identity authentication.
+Refer to the [Token-based Authentication](#token-based-authentication) section
+if using Vault tokens directly.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`vault.cluster`][] field. In Nomad Community Edition, only
+  the `"default"` cluster will be used, so this field should be omitted.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+
+  When using workload identities this field defines the role used to derive
+  task tokens when the job does not define a value for
+  [`vault.role`][jobspec_vault_role]. If empty, the default Vault cluster role
+  is used.
+
+  For token-based authentication, the Nomad servers derive tokens
+  using this role. The token given to Nomad does not have to be created from
+  this role but must have `update` capability on
+  `auth/token/create/<create_from_role>` path in Vault. If this value is unset
+  and the token is created from a role, the value is defaulted to the role the
+  token is from.
+
+  -> **Note:** This used to be a server-only field, but it is client-only when
+  using workload identities. It should be set in both while transitioning from
+  token-based authentication to workload identities.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`] set to `true`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `jwt_auth_backend_path` - `(string: "jwt-nomad")` - Specifies the mount
+  [path][vault_auth_enable_path] of the JWT authentication method to be used to
+  login with workload identity JWTs.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `default_identity` <code>([Identity](#default_identity-parameters): nil)</code> -
+  Specifies the default workload identity configuration to use when a task with
+  a `vault` block does not specify an [`identity`][jobspec_identity] block
+  named `vault_<name>`, where `<name>` matches the value of this `vault` block
+  [`name`](#name) parameter. Setting a default identity causes the value of
+  `allow_unauthenticated` to be ignored.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+### `default_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`bound_audiences`][vault_bound_aud]
+  configuration in the Vault JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in
+  the task's `NOMAD_TOKEN_vault` environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_vault.jwt`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### Token-based Authentication
+
+~> **Warning:** The token-based authentication flow is deprecated and will be
+  removed in a future release. It is highly recommended to migrate and use the
+  workload identity flow instead.
+
+When using token-based authentication the `vault` block parameters should be
+defined as below.
+
+#### Parameters for Nomad Clients and Servers
+
+- [`address`](#address)
+- [`ca_file`](#ca_file)
+- [`ca_path`](#ca_path)
+- [`cert_file`](#cert_file)
+- [`enabled`](#enabled)
+- [`key_file`](#key_file)
+- [`name`](#name)
+- [`namespace`](#namespace)
+- [`tls_server_name`](#tls_server_name)
+- [`tls_skip_verify`](#tls_skip_verify)
+
+#### Parameters for Nomad Servers
+
+- [`allow_unauthenticated`](#allow_unauthenticated)
+- [`create_from_role`](#create_from_role)
+- [`token`](#token)
+- [`task_token_ttl`](#task_token_ttl)
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows a Vault configuration for a Nomad server using the workload
+identity authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled = true
+
+  # Only needed in servers when transioning from the token-based flow to
+  # workload identities.
+  create_from_role = "nomad-cluster"
+
+  # Provide a default workload identity configuration so jobs don't need to
+  # specify one.
+  default_identity {
+    aud  = ["vault.io"]
+    env  = false
+    file = true
+    ttl  = "1h"
+  }
+}
+```
+
+This example shows a Vault configuration for a Nomad server using the
+deprecated token-based authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows a Vault configuration for a Nomad client.
+
+```hcl
+client {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  address   = "https://vault.service.consul:8200"
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+}
+```
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[jobspec_identity]: /nomad/docs/job-specification/identity
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault_bound_aud]: /vault/api-docs/auth/jwt#bound_audiences
+[vault_auth_enable_path]: /vault/docs/commands/auth/enable#path
+[workload_id]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.7.x/content/docs/devices/index.mdx b/content/nomad/v1.7.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.7.x/content/docs/drivers/docker.mdx b/content/nomad/v1.7.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..770fe37963
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1227 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) One of `"hyper-v"`, `"process"`, or `"default"`
+  (which is the same as `process`). Enables [Windows isolation][] modes.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. Note that `"all"` is not permitted here if the `allow_caps`
+  field in the driver configuration doesn't also allow all capabilities. For
+  example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `gcr.io/google_containers/pause-<goarch>:3.1`. The image will only be pulled from
+  the container registry if its tag is `latest` or the image doesn't yet exist locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad 0.10.2 introduces a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
diff --git a/content/nomad/v1.7.x/content/docs/drivers/exec.mdx b/content/nomad/v1.7.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..a1e46c9104
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,283 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver runs binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.7.x/content/docs/drivers/index.mdx b/content/nomad/v1.7.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.7.x/content/docs/drivers/java.mdx b/content/nomad/v1.7.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..88066fa787
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/java.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.7.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.7.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..4a86628ff0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.7.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.7.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..951bdca7eb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+~> The `task.user` field cannot be set on a Task using the `raw_exec` driver if
+the Nomad client has been hardened according to the [production][hardening] guide.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no filesystem isolation.
+
+If the launched process creates a new process group, it is possible that
+Nomad will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to
+manage the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, and the cgroup system is mounted.
+
+If the cluster is configured with memory oversubscription enabled, a task using
+the `raw_exec` driver can be configured to have no maximum memory limit by 
+setting `memory_max = -1`.
+
+```hcl
+resources {
+  cpu        = 500
+  memory     = 128
+  memory_max = -1 # no limit
+}
+```
+
+
+[hardening]: /nomad/docs/install/production/requirements#user-permissions
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.7.x/content/docs/ecosystem.mdx b/content/nomad/v1.7.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.7.x/content/docs/enterprise/index.mdx b/content/nomad/v1.7.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..7880affe96
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,179 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/tutorials/governance-and-policy/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/enterprise/sentinel
diff --git a/content/nomad/v1.7.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.7.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..d393f419a2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/docs/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/docs/commands/license/inspect
diff --git a/content/nomad/v1.7.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.7.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..94ea48d421
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have a license to start. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/docs/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/docs/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.7.x/content/docs/enterprise/license/utilization-reporting.mdx b/content/nomad/v1.7.x/content/docs/enterprise/license/utilization-reporting.mdx
new file mode 100644
index 0000000000..1fa42c06bd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/enterprise/license/utilization-reporting.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: Automated license utilization reporting
+description: >-
+  Learn what data HashiCorp collects to meter Enterprise license utilization. Enable or disable reporting. Review sample payloads and logs.
+---
+
+# Automated license utilization reporting
+
+Automated license utilization reporting sends license utilization data to HashiCorp without requiring you 
+to manually collect and report them. It also lets you review your license usage with the monitoring 
+solution you already use (for example Splunk, Datadog, or others) so you can optimize and manage your 
+deployments. Use these reports to understand how much more you can deploy under your current contract, 
+protect against overutilization, and budget for predicted consumption.  
+
+Automated reporting shares the minimum data required to validate license utilization as defined in our 
+contracts. They consist of mostly computed metrics and will never contain Personal Identifiable Information 
+(PII) or other sensitive information. Automated reporting shares the data with HashiCorp using a secure, 
+unidirectional HTTPS API and makes an auditable record in the product logs each time it submits a report. 
+The reporting process is GDPR compliant and submits reports roughly once every 24 hours.
+
+## Enable automated reporting
+
+To enable automated reporting, you need to make sure that outbound network traffic is configured correctly 
+and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or 
+network settings are not in place, automated reporting will not work. 
+
+### 1. Allow outbound HTTPS traffic on port 443
+
+Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by 
+allow-listing the following IP addresses:
+
+- 100.20.70.12
+- 35.166.5.222
+- 23.95.85.111
+- 44.215.244.1
+
+### 2. Upgrade
+
+Upgrade to a release that supports license utilization reporting. These releases include:
+- [Nomad v1.7.0](/nomad/downloads) and later
+
+### 3. Check logs
+
+Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product 
+logs for records that the data sent successfully.
+
+Instructions on how to check logs. 
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: recording audit record
+[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
+[DEBUG] completed recording audit record
+[DEBUG] core.reporting: export finished successfully
+```
+
+If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an 
+error. 
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: error status code received: statusCode=403
+```
+
+In this case, reconfigure your network to allow egress and check back in 24 hours. 
+
+## Opt out
+
+If your installation is air-gapped or you want to manually collect and report on the same license 
+utilization metrics, you can opt-out of automated reporting. 
+
+Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that 
+you also opt out from sending license utilization metrics. Customers who opt out of automated reporting will 
+still be required to manually collect and send license utilization metrics to HashiCorp. 
+
+If you are considering opting out because you’re worried about the data, we strongly recommend that you 
+review the [example payloads](#example-payloads) before opting out. If you have concerns with any of the 
+automatically-reported data please bring them to your account manager. 
+
+You have two options to opt out of automated reporting: HCL configuration (recommended) and Environment 
+variable (requires restart).
+
+Opting out in your product’s configuration file doesn’t require a system restart, and is the method we 
+recommend. Add the following block to your `server.hcl` file.
+
+```hcl
+reporting {
+	license {
+		enabled = false
+    }
+}
+```
+
+If you need to, you can also opt out using an environment variable, which will provide a startup message 
+confirming that you have disabled automated reporting. This option requires a system restart. 
+
+Set the following environment variable.
+
+```
+$ export OPTOUT_LICENSE_REPORTING=true
+```
+
+Now restart your system by following [these instructions](/nomad/docs/operations/nomad-agent). 
+
+Check your product logs roughly 24 hours after opting out to make sure that the system isn’t trying to send 
+reports.
+
+If your configuration file and environment variable differ, the environment variable setting will take 
+precedence.
+
+## Example payloads
+
+HashiCorp collects the following utilization data as JSON payloads:
+
+`billable.nodes` - Number of billable nodes in Nomad
+
+```json
+"metrics": {
+    "nomad.billable.nodes": {
+        "key": "nomad.billable.nodes",
+        "kind": "counter",
+        "mode": "write",
+        "value": 33
+    }
+}
+```
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/docs/enterprise/sentinel.mdx b/content/nomad/v1.7.x/content/docs/enterprise/sentinel.mdx
new file mode 100644
index 0000000000..6ca332992a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/enterprise/sentinel.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Sentinel Policy Reference
+description: >-
+  Learn about Nomad Sentinel Policy Objects
+---
+
+## Sentinel
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+See the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`
+subcommands][]
+
+### Sentinel Policies
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  will always be non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-nomad-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+### Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+
+### Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+### Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+[Nomad Sentinel Tutorial]: /nomad/tutorials/governance-and-policy/sentinel
+[`nomad sentinel` sub-commands]: /nomad/docs/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L12991-L13020
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L5306-L5338
diff --git a/content/nomad/v1.7.x/content/docs/faq.mdx b/content/nomad/v1.7.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..a9c683b8b6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.7.x/content/docs/glossary.mdx b/content/nomad/v1.7.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..8c2035e7b7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Learn the definition of important Nomad concepts.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.7.x/content/docs/index.mdx b/content/nomad/v1.7.x/content/docs/index.mdx
new file mode 100644
index 0000000000..3296277979
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [Getting Started collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.7.x/content/docs/install/index.mdx b/content/nomad/v1.7.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..7ac5f3dcf2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/install/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Install Nomad
+description: Learn how to install Nomad on Linux, Mac, and Windows.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/install/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Install dmidecode
+
+When running on a virtualized host such as Amazon EC2, Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions
+require installing the dmidecode package manually.
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.7.x/content/docs/install/production/index.mdx b/content/nomad/v1.7.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..2d8e7350d4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.7.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.7.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..559f3ab490
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publically routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup Controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrat
diff --git a/content/nomad/v1.7.x/content/docs/install/quickstart.mdx b/content/nomad/v1.7.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..fb04b6eb39
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via guides containing embedded interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.7.x/content/docs/install/windows-service.mdx b/content/nomad/v1.7.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.7.x/content/docs/integrations/consul/acl.mdx b/content/nomad/v1.7.x/content/docs/integrations/consul/acl.mdx
new file mode 100644
index 0000000000..9499fe7fe2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/consul/acl.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: Consul ACL
+description: Learn how to integrate Nomad with Consul when ACL is enabled.
+---
+
+# Consul ACL
+
+The [Consul ACL][consul_acls] system protects the cluster from unauthorized
+access. When enabled, both Consul and Nomad must be properly configured in
+order for their integrations to work.
+
+Nomad agents must be configured with their own Consul ACL token, and Consul
+must be configured to accept workload identities from tasks and services
+running in Nomad.
+
+## Nomad Agents
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task or service's [Workload
+Identity][nomad_wid] to authenticate to Consul and obtain an ACL token specific
+to the service or task. When using Nomad workload identities, you no longer
+need to pass in a Consul ACL token to submit a job.
+
+By default, Nomad does not generate workload identities for services, and tasks
+only receive an identity that can be used to access data from Nomad itself,
+such as for reading [Variables][] from a [`template`][] block. To access
+Consul, jobs must have additional workload identities defined as [`identity`][]
+blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure Nomad servers with the [`consul.service_identity`][] and
+[`consul.task_identity`][] agent configuration. Upon job registration, the
+Nomad servers update tasks that have a [`consul`][] or [`template`][] block and
+services that use the Consul service provider with these default identities.
+
+You can also specify identities for Consul directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Consul][jobspec_identity_consul] section of the `identity` block
+documentation for more information.
+
+### Configuring Consul Authentication
+
+You must configure Consul so it can receive, validate, and trust workload
+identities from Nomad. Since they are encoded as [JSON Web Tokens (JWTs)][jwt],
+you must create a [JWT ACL auth method][consul_jwt_auth_method]. The auth
+method is an endpoint that Nomad can use to exchange workload identities for
+Consul ACL tokens.
+
+Refer to Consul's [Auth Methods Overview][consul_auth_methods] documentation
+for more information.
+
+#### Consul Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Consul servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Consul is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `JWKSURL` address must be reachable by all Consul servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `JWKSURL` value.
+
+[![Consul Auth Method][img_consul_auth_method]][img_consul_auth_method]
+
+When an allocation that needs access to Consul starts, the Nomad client running
+it exchanges the Nomad workload identities for tasks and services for Consul
+ACL tokens.
+
+[![Consul JWT Login][img_consul_wid_acl_token]][img_consul_wid_acl_token]
+
+The auth method also defines the list of authorized audience values, which must
+have at least one match with the values defined in the Nomad workload identity
+[`aud`][] parameter. For security reasons, it is recommended to only define a
+single audience value.
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced as dynamic values in Consul ACL configuration. The auth method
+determines which of these claims are made available to the rest of the
+configuration.
+
+<CodeBlockConfig highlight="6-9" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### Consul Binding Rules
+
+Consul auth methods use [binding rules][consul_binding_rules] to determine the
+set of policies applied to the generated ACL token. Nomad workload identities
+can be used in Consul for two main purpose: registering services and retrieving
+configuration values and service addresses from Consul using `template` blocks
+in tasks. Each purpose requires tokens with different permissions so Nomad
+requires two binding rules.
+
+The first binding rule associates the Consul ACL token with a [service
+identity][consul_si], allowing the token to register and manage the lifecyle of
+a given service. This binding rule is only applied to Nomad workload identities
+for services because they are the only ones that have a `nomad_service` claim.
+
+```shell-session
+$ consul acl binding-rule create \
+    -method 'nomad-workloads' \
+    -bind-type 'service' \
+    -bind-name '${value.nomad_service}' \
+    -selector '"nomad_service" in value'
+```
+
+The [`-bind-name`][] flag restricts the token to only be able to modify
+services with the same name as the one defined in the Nomad workload identity
+claim. The [`-selector`][] flag ensures this binding rule only applies to
+workload identities for services.
+
+The second binding rule associates the Consul ACL token with an [ACL
+role][consul_acl_role], which is a collection of [ACL
+policies][consul_acl_policy] that define what the token is authorized to do.
+This binding rule is applied to Nomad workload identities for tasks to access
+information from Consul. The exact ACL policy rules will depend on the level of
+access required by the tasks (typically, accessing service addresses and KV with
+[`template`][] blocks).
+
+```shell-session
+$ consul acl binding-rule create \
+  -method 'nomad-workloads' \
+  -bind-type 'role' \
+  -bind-name 'nomad-tasks-${value.nomad_namespace}' \
+  -selector '"nomad_service" not in value'
+```
+
+The `-bind-name` flag defines which role is used for the token. It may
+reference claim values from the Nomad workload identity to apply different
+roles to different tasks. Similarly to the binding rule for services, the
+`-selector` flag ensures this binding rule only applies to workload identities
+for tasks since they don't have the `nomad_service` claim.
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Consul Auth Overview][img_consul_auth]][img_consul_auth]
+
+The [`consul.service_auth_method`][] and [`consul.task_auth_method`][]
+configuration define the auth method used by Nomad to retrieve Consul ACL
+tokens for services and tasks.
+
+By default, they follow the structure described above and use a single auth
+method for both, but it is possible to use two different auth methods, provided
+the resulting Consul ACL token from each have the expected service identity and
+role applied.
+
+#### Consul Namespace Rules <EnterpriseAlert inline />
+
+Consul Enterprise supports multiple namespaces and Nomad Enterprise allows jobs
+to use the [`consul.namespace`][] parameter to register services and read KV
+data from different Consul namespaces.
+
+In a multi-namespace environment, you should create the auth method and binding
+rules in the `default` namespace and configure the auth method with a set of
+[`NamespaceRules`][].
+
+```shell-session
+$ consul acl auth-method create \
+  -name 'nomad-workloads' \
+  -type 'jwt' \
+  -config '@auth-method.json' \
+  -namespace-rule-selector '"consul_namespace" in value' \
+  -namespace-rule-bind-namespace '${value.consul_namespace}'
+```
+
+Similarly to binding rules, namespace rules have a [`Selector`][] expression to
+determine when the rule should be applied and a [`BindNamespace`][] value that
+defines the namespace used.
+
+In Nomad Enterprise, workload identities for tasks and services placed within
+the scope of a `consul` block with a `namespace` value, have an additional
+claim called `consul_namespace` that represents the Consul namespace defined
+in Nomad for the workload.
+
+<CodeBlockConfig highlight="9-11" filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    consul {
+      namespace = "prod"
+    }
+
+    service {
+      port     = "db"
+      name     = "redis"
+      provider = "consul"
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+If a `consul` block is not defined, then the workload identity will not have
+the `consul_namespace` claim, since Nomad is not able to determine which Consul
+namespace will be used.
+
+Refer to the [Consul Namespaces][int_consul_ns] section for more information.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Consul servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Consul and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Consul auth method.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Consul Servers Not Able to Connect to Nomad
+
+If the Consul servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`JWTValidationPubKeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Consul servers, and use that address as the value for
+`JWKSURL`.
+
+It is important to remember that the Nomad keys **are rotated periodically**,
+so both approaches should be automated and done continually. The rotation
+frequency is controlled by the [`server.root_key_rotation_threshold`][]
+configuration of the Nomad servers.
+
+### Additional References
+
+The [Consul ACL with Nomad Workload Identities][consul_tutorial_wid] tutorial
+provides guided instructions on how to configure Consul and Nomad for workload
+identities.
+
+The [`nomad setup consul`][nomad_cli_setup_consul] command and the
+[`hashicorp-modules/nomad-setup/consul`][tf_nomad_setup_consul] Terraform
+module can help you automate the process of applying configuration to a Consul
+cluster.
+
+## Authenticating Without Workload Identity (Legacy)
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`][]
+configuration parameter will control whether a Consul token will be required
+when submitting a job with Consul namespace configured. The provided Consul
+token must belong to the correct namespace, and must be backed by a Consul ACL
+Policy with sufficient `service:write` and `kv:read` permissions. An example
+policy might look like the following.
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+<Note title="Deprecation Warning">
+
+This legacy workflow will be removed in Nomad 1.9. Before upgrading to Nomad 1.9
+you will need to have configured authentication with Consul as described in
+[Nomad Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+## Migrating to Using Workload Identity with Consul
+
+Migrating from the legacy (pre-1.7) workflow where workload use the agent's
+Consul token requires configuation on your Consul cluster and your Nomad server
+agents. It does not require updating your running Nomad jobs. To migrate:
+
+* Create the Consul auth method and binding rules on your Consul cluster.
+* Enable [`consul.service_identity`][] blocks in your Nomad server agent configurations.
+* Enable [`consul.task_identity`][] blocks in your Nomad server agent configurations.
+* (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+  different identity because of how your auth method and binding rules are
+  configured.
+
+Note that when using Workload Identity you will no longer need to pass in a
+Consul token to submit a job.
+
+[Variables]: /nomad/docs/concepts/variables
+[`-bind-name`]: /consul/commands/acl/binding-rule/create#bind-name
+[`-selector`]: /consul/commands/acl/binding-rule/create#selector
+[`BindNamespace`]: /consul/api-docs/acl/auth-methods#bindnamespace
+[`JWTValidationPubKeys`]: /consul/docs/security/acl/auth-methods/jwt#jwtvalidationpubkeys
+[`NamespaceRules`]: /consul/api-docs/acl/auth-methods#namespacerules
+[`Selector`]: /consul/api-docs/acl/auth-methods#selector
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[`consul.service_auth_method`]: /nomad/docs/configuration/consul#service_auth_method
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_auth_method`]: /nomad/docs/configuration/consul#task_auth_method
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`identity`]: /nomad/docs/job-specification/identity
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[consul_acl_policy]: /consul/docs/security/acl/acl-policies
+[consul_acl_role]: /consul/docs/security/acl/acl-roles
+[consul_acls]: /consul/docs/security/acl
+[consul_auth_methods]: /consul/docs/security/acl/auth-methods
+[consul_binding_rules]: /consul/api-docs/acl/binding-rules
+[consul_config_entry]: /consul/docs/connect/config-entries
+[consul_jwt_auth_method]: /consul/docs/security/acl/auth-methods/jwt
+[consul_si]: /consul/docs/security/acl/acl-roles#service-identities
+[consul_tutorial_wid]: /nomad/tutorials/integrate-consul/consul-acl
+[img_consul_auth]: /img/consul-integration-wi.png
+[img_consul_auth_method]: /img/consul-integration-auth-method.png
+[img_consul_wid_acl_token]: /img/consul-integration-wid-acl-token.png
+[int_consul_ns]: /nomad/docs/integrations/consul#consul-namespaces
+[jobspec_identity_consul]: /nomad/docs/job-specification/identity#workload-identities-for-consul
+[jwt]: https://jwt.io/
+[nomad_cli_setup_consul]: /nomad/docs/commands/setup/consul
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_consul]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/consul/
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.7.x/content/docs/integrations/consul/index.mdx b/content/nomad/v1.7.x/content/docs/integrations/consul/index.mdx
new file mode 100644
index 0000000000..1fb5fdeeae
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/consul/index.mdx
@@ -0,0 +1,176 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and install Consul
+on your nodes alongside Nomad, or schedule it as a system job. Nomad does not
+run Consul for you.
+
+To enable Consul integration, please refer to the [Nomad agent Consul
+configuration][] documentation.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please refer to the [Automatic Clustering
+with Consul][] guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please refer to the
+[`service` job specification documentation][service].
+
+## Service Mesh
+
+Consul service mesh provides service-to-service connection authorization and
+encryption using mutual Transport Layer Security (TLS). Nomad can automatically
+provision the components necessary to securely connect your tasks to Consul's
+service mesh.
+
+Refer to the [Consul Service Mesh integration page][int_consul_mesh] for more
+information.
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template`][] block that uses a Consul
+ecosystem tool called [Consul Template][]. This mechanism creates a convenient
+way to ship configuration files that are populated from environment variables,
+Consul data, Vault secrets, or just general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul
+Template, please see the [`template` job specification documentation][].
+
+## Consul ACL
+
+The Consul ACL system protects the cluster from unauthorized access. When
+enabled, both Consul and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Consul ACL integration page][int_consul_acl] for more
+information.
+
+## Consul Namespaces <EnterpriseAlert inline/>
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for
+service registrations specified in `service` blocks and Consul KV reads in
+`template` blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations
+or KV store reads, which Consul then implicitly resolves to the `"default"`
+namespace.  This default namespace behavior can be modified by setting the
+[`namespace`][consul_agent_namespace] field in the Nomad agent Consul
+configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring
+the Consul [namespace][consul_jobspec_namespace] at the group or task level in
+the Nomad job spec as well as the [`-consul-namespace`][consul_run_namespace]
+command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations
+within a group, as well as `template` KV store access is determined from the
+following hierarchy from highest to lowest precedence:
+
+* group and task configuration: Consul
+  [namespace field][consul_jobspec_namespace] defined in the job at the task or
+  group level.
+
+* job run command option: Consul namespace defined in the
+  [`-consul-namespace`][consul_run_namespace] command line option on job
+  submission.
+
+* job run command environment various: Consul namespace defined as the
+  [`CONSUL_NAMESPACE`][consul_env_namespace] environment variable on job
+  submission.
+
+* agent configuration: Consul namespace defined in the
+  [`namespace`][consul_agent_namespace] Nomad agent Consul configuration
+  parameter.
+
+* Consul default: If no Consul namespace options are configured, Consul will
+  automatically make use of the `"default"` namespace.
+
+## Multiple Consul Clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Consul clusters. They can be
+configured using multiple [`consul`][nomad_config_consul] blocks with different
+`name` values. If a `name` is not provided, the cluster configuration is called
+`default`. Nomad automatic clustering uses the `default` cluster for service
+discovery.
+
+Jobs that need access to Consul may specify which Consul cluster to use with
+the [`consul.cluster`][] parameter.
+
+## Assumptions
+
+* Each Nomad client should have a local Consul agent running on the same host,
+  reachable by Nomad. Nomad clients should never share a Consul agent or talk
+  directly to the Consul servers. Nomad is not compatible with [Consul Data
+  Plane][CDP].
+
+* The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+* Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+* The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+
+* Consul service mesh using network namespaces is only supported on Linux.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Consul, with some exceptions.
+
+* Nomad is not compatible with Consul Data Plane.
+
+|                   | Consul 1.16.0+ | Consul 1.17.0+ | Consul 1.18.0+ |
+|-------------------|----------------|----------------|----------------|
+| Nomad 1.7.0+      | ✅             | ✅             | ✅             |
+| Nomad 1.6.0+      | ✅             | ✅             | ✅             |
+| Nomad 1.5.0+      | ✅             | ✅             | ✅             |
+
+[Automatic Clustering with Consul]: /nomad/tutorials/manage-clusters/clustering
+[CDP]: /consul/docs/connect/dataplane
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Nomad agent Consul configuration]: /nomad/docs/configuration/consul
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`template` job specification documentation]: /nomad/docs/job-specification/template#consul-integration
+[`template`]: /nomad/docs/job-specification/template
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_jobspec_namespace]: /nomad/docs/job-specification/consul#namespace
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[consul_env_namespace]: /consul/commands#consul_namespace
+[int_consul_acl]: /nomad/docs/integrations/consul/acl
+[int_consul_mesh]: /nomad/docs/integrations/consul/service-mesh
+[nomad_config_consul]: /nomad/docs/configuration/consul
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
diff --git a/content/nomad/v1.7.x/content/docs/integrations/consul/service-mesh.mdx b/content/nomad/v1.7.x/content/docs/integrations/consul/service-mesh.mdx
new file mode 100644
index 0000000000..b07a2deafd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/consul/service-mesh.mdx
@@ -0,0 +1,393 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/install#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, submit the following service mesh-enabled services
+to Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    # ...
+  }
+```
+
+Since the API service is only accessible via Consul service mesh, it does not define
+any ports in its network. The service block enables service mesh.
+
+```hcl
+  group "api" {
+
+    # ...
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    # ...
+
+  }
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend is configured to communicate with the API service with an
+environment variable:
+
+```hcl
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+```
+
+The web frontend is configured via the `$COUNTING_SERVICE_URL`, so you must
+interpolate the upstream's address into that environment variable. Note that
+dashes (`-`) are converted to underscores (`_`) in environment variables so
+`count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/install#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
diff --git a/content/nomad/v1.7.x/content/docs/integrations/index.mdx b/content/nomad/v1.7.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.7.x/content/docs/integrations/vault/acl.mdx b/content/nomad/v1.7.x/content/docs/integrations/vault/acl.mdx
new file mode 100644
index 0000000000..f6fe3d0992
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/vault/acl.mdx
@@ -0,0 +1,868 @@
+---
+layout: docs
+page_title: Vault ACL
+description: Learn how to integrate Nomad with Vault when ACL is enabled.
+---
+
+# Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. It must be
+properly configured in order for the Vault and Nomad integrations to work.
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault ACL token specific to the task. When
+using Nomad workload identities, you no longer need to pass in a Vault ACL
+token to submit a job.
+
+By default, Nomad only generates a workload identity for tasks that can be used
+to access Nomad itself, such as for reading [Variables][] from a [`template`][]
+block. To access Vault, jobs must have additional workload identities defined
+as [`identity`][] blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure the Nomad servers with the [`vault.default_identity`][] agent
+configuration. Upon job registration, the Nomad servers update tasks that have
+a [`vault`][] block with this default identity.
+
+You can also specify identities for Vault directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Vault][jobspec_identity_vault] section of the `identity` block
+documentation for more information.
+
+### Configuring Vault Authentication
+
+Vault must be configured to receive, validate, and trust these Nomad workload
+identities. Since they are encoded as [JSON Web Tokens (JWTs)][jwt], you must
+create a [JWT ACL auth method][vault_jwt_auth_method]. The auth method is an
+endpoint that Nomad can use to exchange workload identities for Vault ACL
+tokens.
+
+Refer to Vault's [Authentication][vault_auth] documentation for more
+information.
+
+#### Vault Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Vault servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Vault is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The `jwks_url` address must be reachable by all Vault servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `jwks_url` value.
+
+[![Vault Auth Method][img_vault_auth_method]][img_vault_auth_method]
+
+When an allocation that needs access access to Vault starts, the Nomad client
+running it exchanges the Nomad workload identities for tasks for Vault ACL
+tokens.
+
+[![Vault JWT Login][img_vault_wid_acl_token]][img_vault_wid_acl_token]
+
+#### Vault ACL Role
+
+A Vault [ACL role][vault_role] groups multiple ACL policies to apply to a token
+and determine the permissions it receives.
+
+The auth method may define a default ACL role that is applied to the ACL tokens
+it generates. If no default role is set, the role must be provided in the job
+using the [`vault.role`][] parameter or in the Nomad client configuration
+[`vault.create_from_role`][].
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The ACL role specifies the list of authorized audience values using the
+[`bound_audiences`][], which must have at least one match with the values
+defined in the Nomad workload identity [`aud`][] parameter. For security
+reasons, it is recommended to only define a single audience value.
+
+<CodeBlockConfig highlight="3" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced in Vault ACL configuration. The ACL role uses the
+[`claim_mappings`][] parameter to determine which of these claims are made
+available to the rest of the configuration.
+
+The [`bound_claims`][] parameter restricts which workload identities are able
+to use the role based on their claims. Refer to Vault's [Bound
+Claims][vault_bound_claims] documentation for more information.
+
+<CodeBlockConfig highlight="4-7,10-14" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Vault has different [types of ACL tokens][vault_token_types]. Nomad typically
+uses tokens of type `service` since they can be renewed for as long as the
+workload is active. Nomad automatically renews the Vault ACL tokens it generates
+before they expire. To ensure the tokens can be renewed for as long as
+necessary, [`token_explicit_max_ttl`][] must be set to 0.
+
+Alternately, you may use `batch` tokens. This should only be used when a secret
+is requested from Vault once at the start of a task or in a short-lived prestart
+task. Long-running tasks should never set `allow_token_expiration=true` if they
+obtain Vault secrets via `template` blocks, as the Vault token will expire and
+the template runner will continue to make failing requests to Vault until its
+[`vault_retry`][] attempts are exhausted, at which point the task will
+fail. Vault's `batch` tokens cannot be renewed, and Nomad will not attempt to
+renew them when configured to use Workload Identity.
+
+<CodeBlockConfig highlight="16-18" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+#### Vault ACL Policy
+
+A Vault ACL role may have one or more ACL policies attached. Vault [ACL
+policies][vault_policies] define the permissions granted to an ACL
+token.
+
+<CodeBlockConfig highlight="15" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+ACL policies can reference dynamic values from Nomad workload identities claims
+exposed from the ACL role in [templated policies][vault_templated_policies].
+The exact ACL policy rules will depend on the level of access required by
+tasks.
+
+The following example ACL policy automatically grants `read` permissions to
+secrets in the path `secret/data/<job namespace>/<job name>/*`, where `<job
+namespace>` and `<job name>` are read from the workload identity claims
+`nomad_namespace` and `nomad_job_id`.
+
+<CodeBlockConfig highlight="1,5,9" filename="acl-policy.hcl">
+
+```hcl
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Vault Auth Overview][img_vault_auth_overview]][img_vault_auth_overview]
+
+#### Vault Namespaces <EnterpriseAlert inline />
+
+Vault Enterprise supports multiple namespaces and jobs in Nomad Enterprise can
+use the [`vault.namespace`][] parameter to specify which namespace to use. In a
+multi-namespace environment, the authentication setup described must be applied
+to each Vault namespace used by jobs.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Vault servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Vault and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Vault auth method. Nomad's CA certificate should be
+specified in the Vault auth method's
+[`jwks_ca_pem`](https://developer.hashicorp.com/vault/api-docs/auth/jwt#jwks_ca_pem)
+parameter.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Vault Servers Not Able to Connect to Nomad
+
+If the Vault servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`jwt_validation_pubkeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Vault servers, and use that address as the value for
+`jwks_url`.
+
+It is important to remember that the Nomad keys **are rotated periodically**,
+so both approaches should be automated and done continually. The rotation
+frequency is controlled by the [`server.root_key_rotation_threshold`][]
+configuration of the Nomad servers.
+
+### Additional References
+
+The [Vault ACL with Nomad Workload Identities][vault_tutorial_wid] tutorial
+provides guided instructions on how to configure Vault and Nomad for workload
+identities.
+
+The [`nomad setup vault`][nomad_cli_setup_vault] command and the
+[`hashicorp-modules/nomad-setup/vault`][tf_nomad_setup_vault] Terraform
+module can help you automate the process of applying configuration to a Vault
+cluster.
+
+## Authentication Without Workload Identity (Legacy)
+
+To use the legacy Vault integration, Nomad servers must be provided a Vault
+token. This token can either be a root token or a periodic token with
+permissions to create from a token role. The root token is the easiest way to
+get started, but we recommend a token role based token for production
+installations. Nomad servers will renew the token automatically. **Note that the
+Nomad clients do not need to be provided with a Vault token.**
+
+<Note title="Deprecation Warning">
+
+This legacy workflow will be removed in Nomad 1.9. Before upgrading to Nomad 1.9
+you will need to have configured authentication with Vault as described in
+[Nomad Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+See the [Enterprise specific section][ent] for configuring Vault Enterprise.
+
+### Root Token Integration
+
+If Nomad is given a [root token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. This allows
+  Nomad to renew tokens for tasks. Nomad clients will automatically detect when
+  tokens cannot be renewed and will not attempt to renew them (see
+  [`vault.allow_token_expiration`][]).
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Troubleshooting Legacy Authentication
+
+#### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+#### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise allows jobs to use multiple [Vault Namespaces][]. There are a
+few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the
+example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-workloads` role with each
+Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a
+Vault Namespace, but since we will be using multiple it can be left blank. By
+default Nomad will interact with Vault's root Namespace, but individual jobs may
+specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+  }
+}
+```
+
+For legacy authentication, the same steps can be taken to inject a Vault token
+from the [Retrieving the Token Role based
+Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+The example job file below specifies to use the `engineering` Namespace in
+Vault. It will authenticate to Vault using its workload identity with the
+`nomad-workloads` Vault role, then read the value at secret/foo and fetch the
+value for key `bar`.
+
+```hcl
+job "vault" {
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        role      = "nomad-workloads"
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Submitting a job with a Vault Namespace with Legacy Authentication
+
+For the legacy authentication, because [`allow_unauthenticated`][allow_unauth]
+is set to `false` job submitters will need to provide a sufficiently privileged
+token when submitting a job. A token that has access to an appropriate policy in
+`engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+## Migrating to Using Workload Identity with Vault
+
+Migrating from the legacy (pre-1.7) workflow where workloads use the agent's
+Vault token requires configuration on your Vault cluster and your Nomad server
+agents.
+
+Once the migration is fully complete, Nomad server will no longer have access
+to Vault, as it was required in the deprecated legacy workflow. This also means
+that they will no longer be able to fulfill some of their responsibilities from
+the legacy workflow, such as generating and revoking Vault ACL tokens.
+
+Before removing Vault connectivity configuration from Nomad servers, you must
+make sure the rest of the cluster is ready to support workload identities for
+Vault. You can run the [`nomad setup vault -check`][nomad_cli_setup_vault]
+command to verify what changes are still necessary.
+
+Before removing Nomad servers access to Vault you must:
+
+  * Redeploy the jobs listed in the section `Jobs Without Workload Identity for
+    Vault` with an identity for Vault. You can specify this identity [directly
+    in the job][jobspec_identity_vault] or redeploy the job without changes to
+    use the default value from the server [`vault.default_identity`][]
+    configuration if set.
+  * Upgrade nodes listed in the section `Outdated Nodes` to a version of Nomad
+    above 1.7.0.
+
+There is not action required for the Vault ACL tokens listed under `Vault
+Tokens`. Nomad will revoke them as you redeploy jobs to use workload identities
+but there may be some leftovers. You can still proceed with the migration
+process, but Nomad will not revoke them once access to Vault is removed from
+Nomad servers. They will expire once their TTL reaches zero, or you may
+manually revoke them if they are no longer needed by an allocation.
+
+The migration process can happen over time. As long as all servers are upgraded
+to Nomad 1.7+ and still retain access to Vault, jobs can still use either the
+new workload identity flow or the deprecated legacy flow.
+
+To summarize the migration process:
+
+* Enable [`vault.default_identity`][] blocks in your Nomad server agent
+  configurations, but **do not modify any of the existing Vault
+  configuration**.
+* Upgrade your cluster following the documented [Upgrade
+  Process][docs_upgrade].
+* Create the Vault auth method, default role, and policies on your Vault
+  cluster.
+* Run the `nomad setup vault -check` command to verify if the cluster is ready
+  to migrate to workload identity access to Vault.
+  * Resubmit Nomad jobs that need access to Vault to redeploy them with a new
+    workload identity for Vault.
+    * (Optionally) Add [`vault.role`][] fields to any Nomad jobs that will not
+      use the default role.
+    * (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+      different identity because of how your auth method and roles are
+      configured.
+  * Upgrade any remaining clients to Nomad 1.7+.
+* Remove parameters no longer used by the Nomad server agents from the
+  [`vault`][config] configuration block.
+
+[Variables]: /nomad/docs/concepts/variables
+[Vault Namespaces]: /vault/docs/enterprise/namespaces
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`bound_audiences`]: /vault/api-docs/auth/jwt#bound_audiences
+[`bound_claims`]: /vault/api-docs/auth/jwt#bound_claims
+[`claim_mappings`]: /vault/api-docs/auth/jwt#claim_mappings
+[`identity`]: /nomad/docs/job-specification/identity
+[`jwt_validation_pubkeys`]: /vault/api-docs/auth/jwt#jwt_validation_pubkeys
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[`token_explicit_max_ttl`]: /vault/api-docs/auth/jwt#token_explicit_max_ttl
+[`vault.create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault.namespace`]: /nomad/docs/job-specification/vault#namespace
+[`vault.role`]: /nomad/docs/job-specification/vault#role
+[`vault`]: /nomad/docs/job-specification/vault
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[docs_upgrade]: /nomad/docs/upgrade#upgrade-process
+[ent]: #enterprise-configuration
+[img_vault_auth_method]: /img/vault-integration-auth-method.png
+[img_vault_auth_overview]: /img/vault-integration-auth-overview.png
+[img_vault_wid_acl_token]: /img/vault-integration-wid-acl-token.png
+[jobspec_identity_vault]: /nomad/docs/job-specification/identity#workload-identities-for-vault
+[jwt]: https://jwt.io/
+[nomad_cli_setup_vault]: /nomad/docs/commands/setup/vault
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_vault]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault_auth]: /vault/docs/concepts/auth
+[vault_bound_claims]: /vault/docs/auth/jwt#bound-claims
+[vault_jwt_auth_method]: /vault/api-docs/auth/jwt
+[vault_policies]: /vault/docs/concepts/policies
+[vault_role]: /vault/api-docs/auth/jwt#create-update-role
+[vault_templated_policies]: /vault/tutorials/policies/policy-templating
+[vault_token_types]: /vault/tutorials/tokens/tokens#token-types
+[vault_tutorial_wid]: /nomad/tutorials/integrate-vault/vault-acl
+[`vault.allow_token_expiration`]: /nomad/docs/job-specification/vault#allow_token_expiration
diff --git a/content/nomad/v1.7.x/content/docs/integrations/vault/index.mdx b/content/nomad/v1.7.x/content/docs/integrations/vault/index.mdx
new file mode 100644
index 0000000000..b8d58e31a0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/integrations/vault/index.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal.
+
+## Configuration
+
+In order to use Vault with Nomad, you will need to configure and install Vault
+separately from Nomad. Nomad does not run Vault for you.
+
+## Agent Configuration
+
+To enable Vault integration, Nomad agents must be configured with
+[`vault`][] blocks. Each block can be enabled or disabled and configures how
+Nomad connects to the Vault cluster.
+
+## Dynamic Configuration with Secrets
+
+Nomad's job specification includes a [`template`][] block that uses a tool
+called [Consul Template][]. When used with Vault, this mechanism creates a
+convenient way to ship configuration files that are populated from Vault
+secrets.
+
+For more information on Nomad's template block please see the
+[`template` job specification documentation][].
+
+## Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. When
+enabled, both Vault and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Vault ACL integration page][int_vault_acl] for more information.
+
+## Multiple Vault Clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Vault clusters. They can be
+configured using multiple [`vault`][] blocks with different `name` values. If a
+`name` is not provided, the cluster configuration is called `default`.
+
+Jobs that need access to Vault may specify which Vault cluster to use with the
+[`vault.cluster`][] parameter.
+
+## Compatibility
+
+* Nomad versions 1.4.0 and above are compatible with any currently supported
+  version of Vault.
+
+|              | Vault 1.13.0+ |
+|--------------|---------------|
+| Nomad 1.4.0+ | ✅            |
+
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Vault]:  https://www.vaultproject.io/ 'Vault by HashiCorp'
+[`template` job specification documentation]: /nomad/docs/job-specification/template#vault-integration
+[`template`]: /nomad/docs/job-specification/template
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[int_vault_acl]: /nomad/docs/integrations/vault/acl
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/action.mdx b/content/nomad/v1.7.x/content/docs/job-specification/action.mdx
new file mode 100644
index 0000000000..bb7f4c43da
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/action.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: action Block - Job Specification
+description: The "action" block allows for executable commands that job authors can predefine for operators to subsequently run against their job.
+---
+
+# `action` Block
+
+<Placement groups={['job', 'group', 'task', 'action']} />
+
+The `action` block allows job authors to define custom commands. These commands
+can be executed by operators with the necessary permissions on a running
+allocation, offering a controlled way to interact with tasks.
+
+The name of the action can contain alphanumeric characters and dashes. This
+name must be unique within its task and must not exceed 128 characters.
+
+## `action` Parameters
+
+- `command` `(string: <required>)` - Specifies the command to be executed.
+- `args` `(array<string>: [])` - Provides a list of arguments to pass to the command.
+
+```hcl
+job "my-job" {
+  group "my-group" {
+    task "my-task" {
+      action "get-changelog" {
+        command = "/usr/bin/curl"
+        args = [
+          "-s",
+          "https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md"
+        ]
+      }
+      # ...
+    }
+  }
+}
+```
+
+## `action` Examples
+
+### Basic Action
+This example demonstrates a simple action that prints the current date and time:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "show-date" {
+      # ...
+      action "current-date" {
+        command = "/bin/date"
+      }
+    }
+  }
+}
+```
+
+### Action with Arguments
+Here, an action uses arguments to perform a specific task:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "list-files" {
+      # ...
+      action "list-tmp" {
+        command = "/bin/ls"
+        args    = ["-l", "/tmp"]
+      }
+    }
+  }
+}
+```
+
+### Action with Template
+This advanced example demonstrates an action that fetches and formats the latest
+changelog from the Nomad GitHub repository using a shell script. It showcases
+the use of templating with embedded environment variables and a multi-line script.
+
+```hcl
+action "fetch-latest-nomad-changelog" {
+  command = "/bin/sh"
+  args    = ["-c", 
+    <<EOT
+curl -s https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md | 
+
+awk 'BEGIN{
+    # Setting record and field separators
+    RS="## "; FS="\n"; 
+    section=""; count=0
+}
+{
+    # Processing only the first 3 sections after the header
+    if (count < 3 && NR > 1){
+        # Splitting the version line into components
+        split($1, versionInfo, /[()]/);
+        version=versionInfo[1];
+        gsub(" ", "", version); # Removing spaces from version
+        releaseDate=versionInfo[2];
+        # Formatting URL components
+        urlVersion=version; gsub("\\.", "", urlVersion); # Remove dots from version
+        urlDate=releaseDate; gsub(" ", "-", urlDate); gsub(",", "", urlDate); # Replace spaces with hyphens and remove comma
+        # Counting items under each section
+        for(i=1; i<=NF; i++){
+            if($i ~ /^[A-Z ]+:$/){
+                gsub(":", "", $i);
+                section=$i;
+                itemCount[section]=0;
+            }
+            if(section && $i ~ /^\*/){
+                itemCount[section]++;
+            }
+        }
+        # Printing the extracted information
+        printf "Version: %s\nRelease Date: %s\n", version, releaseDate;
+        for (s in itemCount) {
+            printf "%d %s, ", itemCount[s], s;
+        }
+        printf "\nLink: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md#%s-%s\n\n", urlVersion, tolower(urlDate);
+        delete itemCount;  # Clear the itemCount array for the next version
+        count++;
+    }
+}'
+    EOT
+  ]
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.7.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.7.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..a306fa290c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,284 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. As of Nomad 0.6 non-Amazon S3-compatible
+endpoints like [Minio] are supported, but you must explicitly set the "s3::"
+prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment variables
+set for the Nomad client. Inheritance of environment variables can be managed through the [`artifact.set_environment_variables`][client_artifact]
+client configuration.
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.7.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/check.mdx b/content/nomad/v1.7.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..c26f25a7a0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,477 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_success_before_passing].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_failure_before_critical].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_warning` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`warning`][consul_failure_before_warning].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. In Nomad 0.7.1 or later numeric ports may be used if
+  `address_mode="driver"` is set on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider. 
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks . Only supported in the Consul
+  service provider.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_success_before_passing]: /consul/api-docs/agent/check#successbeforepassing
+[consul_failure_before_critical]: /consul/api-docs/agent/check#failuresbeforecritical
+[consul_failure_before_warning]: /consul/api-docs/agent/check#failuresbeforewarning
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.7.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.7.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.7.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..f09e253aa7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,322 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/consul.mdx b/content/nomad/v1.7.x/content/docs/job-specification/consul.mdx
new file mode 100644
index 0000000000..ec76f5ab7e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/consul.mdx
@@ -0,0 +1,297 @@
+---
+layout: docs
+page_title: consul Block - Job Specification
+description: |-
+  The "consul" block allows the group or task to specify that it requires a token
+  from a HashiCorp Consul server. Nomad will automatically retrieve a Consul token
+  for the group or task.
+---
+
+# `consul` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'consul'],
+    ['job', 'group', 'task', 'consul'],
+  ]}
+/>
+
+The `consul` block specifies [Consul][] configuration options specific to a
+task. If specified at the `group` level, the configuration will apply to all
+tasks and services within the group unless a task has its own `consul` block. A
+task-level `consul` block will entirely override a group-level `consul` block.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      consul {
+        cluster   = "default"
+        namespace = "default"
+        partition = "default"
+      }
+    }
+  }
+}
+```
+
+## Workload Identity
+
+Starting in Nomad 1.7, Nomad clients will use a task or service's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+service or task when the following conditions are met:
+
+* For services, if either the [`consul.service_identity`][] is configured on the
+  Nomad servers or the service includes an `identity` block.
+* For tasks, if the [`consul.task_identity`][] is configured on the Nomad
+  servers, or the task includes an [`identity`][] block with the `name` field
+  set to `consul_default` (or `consul_$clusterName` for non-default Consul
+  clusters in Nomad Enterprise).
+
+As a fallback if none of these conditions are met, the Nomad client will instead
+use, in order of preference:
+
+* The token provided by the [`-consul-token`][flag_consul_token] flag for the
+  `nomad job run` command.
+* The Consul token as configured in the agent's [`consul.token`][] configuration.
+* The Consul token as configured by the agent's `CONSUL_HTTP_TOKEN` environment variable.
+
+To avoid failed deployments, you should first set up an authentication method
+and binding rules in Consul before configuring the Nomad servers with
+`consul.task_identity` and `consul.service_identity`. Refer to [Configuring Consul
+Authentication][] for more details.
+
+<Warning>
+Starting in Nomad 1.9, the fallback options to use the -consul-token flag when
+submitting a job, the agent's consul.token configuration, or the
+CONSUL_HTTP_TOKEN environment variable, will be removed.  This means service and
+template blocks will not be able to use the agent's Consul token or one provided
+by the job submitter. You should be prepared to migrate to the Workload Identity
+workflow for Consul and Vault before upgrading to Nomad 1.9. Refer to <a
+href="/nomad/docs/integrations/consul-integration#migrating-to-using-workload-identity-with-consul">Migrating
+to Using Workload Identity with Consul</a>
+</Warning>
+
+### Access to Token
+
+The Nomad client will make the Consul token available to the task by writing it
+to the secret directory at `secrets/consul_token` and by injecting a
+`CONSUL_TOKEN` environment variable in the task. 
+
+If the Nomad cluster is [configured][config_consul_namespace] to use [Consul Namespaces][], a
+`CONSUL_NAMESPACE` environment variable will be injected whenever `CONSUL_TOKEN`
+is set.
+
+The [`template`][template] block can use the Consul token as well.
+
+### `consul` Parameters
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use. The Nomad client will retrieve a Consul token from the
+  cluster configured in the agent configuration with the same
+  [`consul.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in
+  which group and task-level services within the group will be registered. Use
+  of `template` to access Consul KV will read from the specified Consul
+  namespace.  Specifying `namespace` takes precedence over the
+  [`-consul-namespace`][flag_consul_namespace] command line argument in `job run`.
+
+- `partition` `(string: "")` - When this field is set, a constraint will be
+  added to the group or task to ensure that the allocation is placed on a Nomad
+  client that has a Consul Enterprise agent in the specified Consul [admin
+  partition][]. Note that Consul Community Edition agents are not assigned to
+  any admin partition, so this field should not be used without Consul
+  Enterprise.
+
+## `consul` Examples
+
+The following examples only show the `consul` blocks or other relevant
+blocks. Remember that the `consul` block is only valid in the placements listed
+above.
+
+### Consul Token for Templates
+
+This example tells the Nomad client to obtain a Consul token using the task's
+Workload Identity. The token is available to the task via the canonical
+environment variable `CONSUL_TOKEN` and written to disk at
+`secrets/consul_token`. The `template` block will use the same Consul
+token. Note that the `identity.name` is set to `"consul_default"`, which tells
+the Nomad client to use this identity when making requests to the default Consul
+cluster.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      identity {
+        name = "consul_default"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.task_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted in this case.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Consul Token for Group Services
+
+This example tells the Nomad client to obtain a Consul Service Identity token
+using the service's Workload Identity. The Consul token will be used to register
+the service with Consul and configure any [Connect][] sidecar tasks for that
+service.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+      identity {}
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.service_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted for the service in this case.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+    }
+  }
+}
+```
+
+### Consul Namespace
+
+This example shows specifying a particular Consul namespace or Consul cluster
+for different tasks within a group.
+
+<EnterpriseAlert />
+
+The `template` block in the `web` task will use the default Consul cluster, and
+will obtain a token that allows it access to the `engineering/frontend` Consul
+namespace. The `template` block in the `app` task will use the Consul cluster
+named `prod-apps`, and will obtain a token that allows it access to the
+`engineering/apps` Consul namespace.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "web" {
+
+      consul {
+        namespace = "engineering/frontend"
+      }
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      consul {
+        namespace = "engineering/apps"
+        cluster   = "prod-apps"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+### Consul Admin Partition
+
+This example demonstrates how to configure Consul admin partitions for different
+tasks within a group. The Consul client agent must separately specify the admin
+partition in the agent configuration. Refer to the Consul documentation's
+[agent configuration reference][] for more information.
+
+<EnterpriseAlert />
+
+In the following example, the `web` and `app` tasks use the default Consul cluster
+and obtain a token that allows access to the `prod` admin partition in Consul. The
+Consul configuration occurs at the `group` level because tasks are placed together
+on the same Allocation. If you configure tasks with separate `consul` blocks, the
+`partition` field must be the same in both blocks.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    consul {
+      cluster   = "default"
+      namespace = "default"
+      partition = "prod"
+    }
+
+    task "web" {
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`identity`]: /nomad/docs/job-specification/identity
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[flag_consul_token]: /nomad/docs/commands/job/run#consul-token
+[`consul.token`]: /nomad/docs/configuration/consul#token
+[Configuring Consul Authentication]: /nomad/docs/integrations/consul-integration#TODO
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul-integration#migrating-to-using-workload-identity-with-consul
+[config_consul_namespace]: /nomad/docs/configuration/consul#namespace
+[Consul Namespaces]: /consul/docs/enterprise/namespaces
+[Consul Admin Partitions]: /consul/docs/enterprise/admin-partitions
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[flag_consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[Connect]: /nomad/docs/job-specification/connect
+[admin partition]: /consul/docs/enterprise/admin-partitions
+[agent configuration reference]: /consul/docs/agent/config/config-files#partition-1
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.7.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..a0bfa3ac8c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/device.mdx b/content/nomad/v1.7.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..0748bf8ec4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.7.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..af5e905a54
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/env.mdx b/content/nomad/v1.7.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.7.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..dca9fc6523
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+## `ephemeral_disk` Examples
+
+The following examples only show the `ephemeral_disk` blocks. Remember that the
+`ephemeral_disk` block is only valid in the placements listed above.
+
+### Sticky Volumes
+
+This example shows enabling sticky volumes with Nomad using ephemeral disks:
+
+```hcl
+ephemeral_disk {
+  sticky = true
+}
+```
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.7.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..e709e4c464
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/registration/service-registration#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.7.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..b97f097675
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,746 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect
+Gateways](/consul/docs/connect/gateways). Nomad will automatically create the
+necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries) as
+well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making
+  upstream connections before timing out. Defaults to 5 seconds. If the upstream
+  service has the configuration option <code>[connect_timeout_ms]</code> set for
+  the `service-resolver`, that timeout value will take precedence over this
+  gateway proxy option.
+
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the
+  gateway services tagged addresses should be bound to listeners in addition to
+  the default listener address.
+
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A
+  map of additional addresses to be bound.  The keys to this map are the same of
+  the listeners to be created and the values are a map with two keys - address
+  and port, that combined make the address to bind the listener to. These are
+  bound in addition to the default address.  If `bridge` networking is in use,
+  this map is automatically populated with additional listeners enabling the
+  Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy
+  Documentation][envoy_sd_docs].  This option applies to terminating gateways
+  that route to services addressed by a hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners
+  that the ingress gateway should setup, uniquely identified by their port
+  number.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or
+  `grpc`), preconfiguring a [service-default][] in Consul to set the
+  [Protocol][service-default-protocol] of the service to the desired protocol is
+  mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[listener-service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### Listener `service` Parameters
+
+The `service` blocks for a listener under an `ingress` gateway accept the
+following parameters. Note these are different than the `service` blocks under a
+`terminating` gateway.
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+- `request_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to requests routed to this
+  service. This cannot be used with a tcp listener.
+
+- `response_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to responses from this
+  service. This cannot be used with a tcp listener.
+
+- `max_concurrent_requests` `(int: <optional>)` - Specifies the maximum number
+  of concurrent HTTP/2 traffic requests that are allowed at a single point in
+  time. If unset, will default to the Envoy proxy's default.
+
+- `max_connections` `(int: <optional>)` - Specifies the maximum number of
+  HTTP/1.1 connections a service instance is allowed to establish against the
+  upstream. If unset, will default to the Envoy proxy's default.
+
+- `max_pending_requests` `(int: <optional>)` - Specifies the maximum number of
+  requests that are allowed to queue while waiting to establish a connection.
+  If unset, will default to the Envoy proxy's default.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this service.
+
+#### Header modifier parameters
+
+The `request_headers` and `response_headers` blocks of an `ingress.service`
+block accept the following parameters. For more details, see the [Consul
+documentation][response-headers].
+
+- `add` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  headers, where header names are keys and header values are the values. Header
+  names are not case-sensitive. If header values with the same name already
+  exist, the value is appended and Consul applies both headers.
+
+- `set` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  response header or to replace existing header values with. Use header names as
+  the keys. Header names are not case-sensitive. If header values with the same
+  names already exist, Consul replaces the header values.
+
+- `remove` `array(string): optional` - Defines a list of headers to remove. Consul
+  removes only headers containing exact matches. Header names are not
+  case-sensitive.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every
+  listener on the gateway. If TLS is enabled, then each host defined in the
+  `host` field will be added as a DNSSAN to the gateway's x509 certificate.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+- `sds` `(block: optional)` - Defines a set of parameters that configures the
+  listener to load TLS certificates from an external Secret Discovery Service
+  ([SDS][]).
+
+  - `cluster_name` `(string)` - The SDS cluster name to connect to to retrieve
+    certificates.
+
+  - `cert_resource` `(string)` - The SDS resource name to request when fetching
+    the certificate from the SDS service.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### linked `service` Parameters
+
+The `service` blocks for a `terminating` gateway accept the following
+parameters. Note these are different than the `service` blocks for listeners
+under an `ingress` gateway.
+
+- `name` `(string: required)` - The name of the service to link with the
+  gateway. If the wildcard specifier `*` is provided, then ALL services within
+  the Consul namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate
+  authority is used to verify the authenticity of the service linked with the
+  gateway. It can be provided along with a `cert_file` and `key_file` for mutual
+  TLS authentication, or on its own for one-way TLS authentication. If none is
+  provided the gateway **will not** encrypt traffic to the destination.
+
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided
+  to servers to verify the gateway's authenticity. It must be provided if a
+  `key_file` is provided.
+
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the
+  certificate to verify the gateway's authenticity. It must be provided if a
+  `cert_file` is provided.
+
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify
+  during the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#linked-service-parameters
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[listener-service]: /nomad/docs/job-specification/gateway#listener-service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
+[envoy_sd_docs]: https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery
+[SDS]: https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#listeners-services-tls-sds
+[service-default-protocol]: /consul/docs/connect/config-entries/service-defaults#protocol
+[response-headers]: /consul/docs/connect/config-entries/ingress-gateway#listeners-services-responseheaders
+[header modifiers]: /nomad/docs/job-specification/gateway#header-modifier-parameters
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/group.mdx b/content/nomad/v1.7.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..364577c081
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,398 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group. These options will be applied to all tasks and
+  services in the group unless a task has its own `consul` block.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `prevent_reschedule_on_lost` `(bool: false)` - Defines the reschedule behaviour
+  of an allocation when the node it is running on misses heartbeats.
+  When enabled, if the node it is running on becomes disconnected
+  or goes down, this allocations wont be rescheduled and will show up as `unknown`
+  until the node comes back up or it is manually restarted.
+
+  This behaviour will only modify the reschedule process on the server.
+  To modify the allocation behaviour on the client, see
+  [`stop_after_client_disconnect`](#stop_after_client_disconnect).
+
+  The `unknown` allocation has to be manually stopped to run it again.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+  same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost". These
+allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' reschedule policy
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements and keep
+the one with the best node score. If the `max_client_disconnect` duration
+expires before the client reconnects, the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+#### Max Client Disconnect and Prevent Reschedule On Lost
+
+Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect      = "12h"
+  prevent_reschedule_on_lost = true
+
+  reschedule {
+    attempts  = 0
+    unlimited = false
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+```
+
+If [`max_client_disconnect`](#max_client_disconnect) is set and
+`prevent_reschedule_on_lost = true`, allocations on disconnected nodes will be
+`unknown` until the `max_client_disconnect` window expires, at which point
+the node will be transition from `disconnected` to `down`. The allocation
+will remain as `unknown` and won't be rescheduled.
+
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/consul
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[`disable_rescheduling`]: /nomad/docs/job-specification/reschedule#disabling-rescheduling
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[`consul.name`]: /nomad/docs/configuration/consul#name
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..91ea784340
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..734fbf6589
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..6cf8bcbd89
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..6f964b533f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/integrations/vault-integration">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..2e92de5824
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://developer.hashicorp.com/nomad/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..ab2f14ad6d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Nomad 0.12 and earlier allowed a few variations for defining blocks. For example, the following variations of `meta` were accepted:
+
+```hcl
+meta {
+  # meta attributes can be quoted or not
+  "team"       = "..."
+  organization = "..."
+}
+
+# meta can be an assignment to a map
+meta = { "team" = "...", organization = "..." }
+```
+
+Starting with Nomad 1.0 and the HCL2 parser, only the block syntax with unquoted attributes is accepted:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+Nomad 0.12 and earlier accepted small decimal values without a leading zero
+(e.g. `.3`, `.59`, `.9`). In such case, Nomad 1.0 requires a leading zero (e.g.
+`0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..fb820cf5b8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/runtime/environment
+[expression]: /nomad/docs/job-specification/hcl2/expressions
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.7.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..ec2299274a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,357 @@
+---
+layout: docs
+page_title: identity Block - Job Specification
+description: |-
+  The "identity" block allows tasks to use their Nomad Workload Identity via an
+  environment variable or file.
+---
+
+# `identity` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'identity'],
+    ['job', 'group', 'task', 'identity'],
+    ['job', 'group', 'task', 'service', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. Nomad will create a _default_ identity for all
+workloads, but it is *not* exposed to a task. You may also set additional
+identities intended for use with external applications such as Vault, Consul, or
+OIDC authentication.
+
+For example, the following will expose the default Workload Identity as an
+environment variable and file to the task, and a second Workload Identity
+configured for a third-party OIDC provider:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env         = true
+        file        = true
+
+        # Restart on token renewal to get the new env var
+        change_mode = "restart"
+      }
+
+      identity {
+        name        = "example"
+        aud         = ["oidc.example.com"]
+        file        = true
+        ttl         = "1h"
+
+        # Send a HUP signal when the token file is updated
+        change_mode   = "signal"
+        change_signal = "SIGHUP"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## `identity` Parameters
+
+- `name` `(string: "default")` - The name of the workload identity, which must
+  be unique per task. Only one `identity` block in a task can omit the `name`
+  field.
+- `aud` `([]string: nil)` - The audience field for the workload identity. This
+  should always be set for non-default identities.
+- `change_mode` `(string: "noop")` - Specifies the behavior Nomad should take when the token changes.
+
+  - `"noop"` - take no action. The default since tasks may choose to reload
+      tokens only when their current token gets rejected or implement their own
+      change detection.
+  - `"restart"` - restart the task.
+  - `"signal"` - send a configurable signal to the task. Must set `change_signal`.
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGHUP"` or `"SIGUSR1"`. This option is required if the
+  `change_mode` is `signal`.
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+- `ttl` `(string: "")` - The lifetime of the identity before it expires. The
+  client will renew the identity at roughly half the TTL. This is specified
+  using a label suffix like "30s" or "1h". You may not set a TTL on the default
+  identity. You should always set a TTL for non-default identities.
+
+## Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identities for Consul
+
+Jobs that need access to Consul can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task or service that will access Consul.
+
+You can configure Nomad servers to automatically add default identities for
+Consul using the [`consul.service_identity`][] and [`consul.task_identity`][]
+agent configuration. Upon job registration, the Nomad server updates tasks that
+have a [`consul`][] or [`template`][] block and services that use the Consul
+service provider to include the default identities.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identities configured in the Nomad servers. Identities for
+tasks must have a [`name`](#name) that follows the pattern
+`consul_<cluster name>`. Identities for services do not need to specify a
+`name`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the task
+identity name should be `consul_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Consul clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/consul#cluster">
+  <code>consul.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_consul_wid] section of the Consul
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="3,14-17,30-34">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {}
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_default"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="3-5,16-19,34-38">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {
+      cluster = "prod"
+    }
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_prod"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Workload Identities for Vault
+
+Jobs that need access to Vault can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task that will access Vault.
+
+You can configure Nomad servers to automatically add default identities for
+Vault using the [`vault.default_identity`][] agent configuration. Upon job
+registration, the Nomad server updates tasks that have a [`vault`][] block to
+include the default identity.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identity configured in the Nomad servers. The identity
+[`name`](#name) must follow the pattern `vault_<cluster name>`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the
+identity name should be `vault_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Vault clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/vault#cluster">
+  <code>vault.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_vault_wid] section of the Vault
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="19,21-25">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      identity {
+        name = "vault_default"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="19-21,23-27">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {
+        cluster = "prod"
+      }
+
+      identity {
+        name = "vault_prod"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`template`]: /nomad/docs/job-specification/template
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault`]: /nomad/docs/job-specification/vault
+[int_consul_wid]: /nomad/docs/integrations/consul-integration#nomad-workload-identities
+[int_vault_wid]: /nomad/docs/integrations/vault-integration#nomad-workload-identities
+[taskapi]: /nomad/api-docs/task-api
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/index.mdx b/content/nomad/v1.7.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..dc0478fb08
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+Note that starting with Nomad 0.10, the `service` block can also be specified at the group level. This
+allows job specification authors to create and register services with Consul Connect support. A service
+block specified at the group level must include a [connect][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/job.mdx b/content/nomad/v1.7.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..30f3081b1f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  task "docs" {
+    # ...
+  }
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+  Prior to Nomad 1.0 namespaces were Enterprise-only.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` (new in
+  Nomad 1.2) schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.7.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.7.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..bb361fd493
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with reasonable defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/drivers/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.7.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..6f32810932
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## `meta` Usage Examples
+
+### Templates
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.7.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.7.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..f03b42e37d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,290 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/network.mdx b/content/nomad/v1.7.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..8ce2bce7c4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,334 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created. This matches the current behavior in Nomad 0.9.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is necessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/numa.mdx b/content/nomad/v1.7.x/content/docs/job-specification/numa.mdx
new file mode 100644
index 0000000000..a67e38cbad
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/numa.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: numa Block - Job Specification
+description: |-
+  The "numa" block is used configure NUMA aware scheduling strategy for a task.
+---
+
+# `numa` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'numa']} />
+
+The `numa` block is used to configure how Nomad will assign CPU cores for a task
+while taking the [NUMA hardware topology][numa_wiki] of a node into consideration.
+Workloads that are sensitive to memory latency can perform significantly better
+when pinned to CPU cores on the same NUMA node.
+
+<EnterpriseAlert>
+
+This functionality only exists in Nomad Enterprise. This is not
+present in the source available version of Nomad.
+</EnterpriseAlert>
+
+<Note>
+
+NUMA aware scheduling is currently limited to Linux.
+</Note>
+
+```hcl
+job "example" {
+  group "group" {
+    task "task" {
+      resources {
+        cores = 8
+        numa {
+          affinity = "require"
+        }
+      }
+    }
+  }
+}
+```
+
+In the example above, the task is requesting Nomad to reserve 8 CPU cores, all
+of which must be colocated on the same hardware NUMA node. The Nomad scheduler
+will ensure the task is placed on a Nomad node with sufficient unused CPU cores
+in a compatible configuration.
+
+Configuring the `numa` block requires the task specifies CPU resources using
+the [`cores`][cores] parameter.
+
+# `numa` Parameters
+
+- `affinity` `(string: "none")` - Specifies the strategy Nomad will use when
+  selecting CPU cores to assign to a task. Possible values are `"none"`,
+  `"prefer"`, or `"require"`.
+  - `none` - Nomad is free to allocate CPU cores using any strategy. Nomad uses
+  this freedom to allocate cores in such a way that minimizes the amount of
+  fragmentation of core availability per NUMA node. It does so by bin-packing
+  the chosen cores onto the NUMA nodes with the fewest number of cores available.
+  - `prefer` - Nomad will select the set of CPU cores on a node that minimizes
+  the total distance between those cores, but does not limit those CPU core
+  selections to come from a single NUMA node.
+  - `require` - Nomad will select a set of CPU cores that are strictly colocated
+  on the same hardware NUMA node. If there are no Nomad nodes with a sufficient
+  number of available cores in a compatible configuration, task placement will
+  fail due to exhausted resources.
+
+<Note>
+
+  The `require` affinity option causes fragmentation of available CPU cores
+  based on the NUMA node the selected cores are associated with. Use it for
+  workloads known to be highly sensitive to memory latencies. A cluster where
+  all jobs make use of the `require` affinity option will not be able to make
+  efficient use of available resources.
+</Note>
+
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.7.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..bf914761dc
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.7.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..ad19c7080d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,119 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` `(string: <required>)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions.
+  Conflicts with `cron`.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.7.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..9b86faf3c2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,88 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect). It is valid only
+within the context of a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `local_service_address` `(string: "127.0.0.1")` - The address the local service binds to. Useful to
+  customize in clusters with mixed Connect and non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in clusters with mixed
+  Connect and non-Connect services.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of each upstream service that
+  this sidecar proxy communicates with.
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path configuration for Envoy.
+  See Consul's [Expose Paths Configuration Reference](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference)
+  for more information.
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and
+  passed directly to Consul. See [Consul Connect documentation](/consul/docs/connect/proxies/envoy#dynamic-configuration)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.7.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.7.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..e6fe58988c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `numa` <code>([Numa][]: &lt;optional&gt;)</code> - Specifies the
+  NUMA scheduling preference for the task. Requires the use of `cores`.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`docker`, `exec`, and `java` task drivers.  Consult the documentation of
+community-supported task drivers for their memory oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][tutorial_quota] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/drivers/docker#cpu
+[exec_cpu]: /nomad/docs/drivers/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[tutorial_quota]: /nomad/tutorials/governance-and-policy/quotas
+[numa]: /nomad/docs/job-specification/numa 'Nomad NUMA Job Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.7.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..7347deba68
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all 
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### Disabling restart
+
+To disable restarting, set the `attempts` parameter to zero and `mode` to `"fail"`.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+  }
+}
+```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.7.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/service.mdx b/content/nomad/v1.7.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..a433c45e36
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,538 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+
+        identity {
+          aud = ["consul.io"]
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+Nomad 0.10 also allows specifying the `service` block at the task group level.
+This enables services in the same task group to opt into [Consul
+Connect][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use, when the `provider` is `"consul"`. The Nomad client
+  will retrieve a Consul token from the cluster configured in the agent
+  configuration with the same [`consul.name`][]. In Nomad Community Edition,
+  this field is ignored.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `identity` <code>([Identity][identity_block]: nil)</code> - Specifies a
+  Workload Identity to use when obtaining Service Identity tokens from Consul to
+  register the service. Only available where `provider = "consul"`. Typically
+  this can be omitted so that Nomad will fall back to the server's
+  [`consul.service_identity`][] block.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[identity_block]: /nomad/docs/job-specification/identity
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.7.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..584ef6cf02
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       "test-key" = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.7.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..85736f3215
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.7.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..6fc0455de3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter. By
+default, when using spread the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target percentage defined in the
+spread block. Spread scores are combined with other scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad
+scheduler. If no nodes match a given spread criteria, placement is
+still successful. To avoid scoring every node for every placement,
+allocations may not be perfectly spread. Spread works best on
+attributes with similar number of nodes: identically configured racks
+or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally, spread may be specified at the [job][job] and [group][group] levels for ultimate flexibility. Job level spread criteria are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/task.mdx b/content/nomad/v1.7.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..43b743bd97
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `consul` <code>([Consul][consul_jobspec]: nil)</code> - Specifies Consul
+  configuration options specific to the task.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_jobspec]: /nomad/docs/job-specification/consul
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/template.mdx b/content/nomad/v1.7.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..2866a74ec4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,827 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad Integration
+
+### Nomad Services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/update.mdx b/content/nomad/v1.7.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..3e1243a165
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.7.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..102cefb6d9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul
+Connect](/nomad/docs/integrations/consul-connect) proxy routes to. It
+is valid only within the context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect
+Guide](/consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery).
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_partition` `(string: "")` - Name of the Cluster admin partition containing the upstream service.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.7.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..250918a987
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        cluster  = "default"
+        role     = "prod"
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `disable_file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `allow_token_expiration` `(bool: false)` - Specifies that Nomad clients should
+  not attempt to renew a task's Vault token, allowing it to expire. This should
+  only be used when a secret is requested from Vault once at the start of a task
+  or in a short-lived prestart task. Long-running tasks should never set
+  `allow_token_expiration=true` if they obtain Vault secrets via `template`
+  blocks, as the Vault token will expire and the template runner will continue
+  to make failing requests to Vault until its [`vault_retry`][] attempts are
+  exhausted, at which point the task will fail.
+
+  When Nomad has been configured to use [Workload Identity with Vault][], Nomad
+  clients will automatically detect when tokens cannot be refreshed (for
+  example, when the Vault auth method is configured to issue batch tokens). In
+  this case, the `allow_token_expiration` option will be implicitly set to
+  `true` by the client. The [legacy Vault authentication workflow][] cannot
+  automatically detect this.
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Vault cluster to use. The Nomad client will retrieve a Vault token from the
+  cluster configured in the agent configuration with the same
+  [`vault.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies. This field may only be used with the legacy Vault
+  authentication workflow and not with JWT and workload identity. It is
+  deprecated in favor of the `role` field and will be removed in Nomad 1.9.
+
+- `role` `(string: "")` - Specifies the Vault role used when retrieving a token
+  from Vault using JWT and workload identity. If not specified the client's
+  [`create_from_role`][] value is used.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+Vault policies from the "prod" role attached.
+
+```hcl
+vault {
+  role = "prod"
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  role = "prod"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private Token and Change Modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  role         = "prod"
+  change_mode  = "noop"
+  env          = false
+  disable_file = true
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  role      = "prod"
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[`create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[docker]: /nomad/docs/drivers/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
+[`vault.name`]: /nomad/docs/configuration/vault#name
+[`vault_retry`]: /nomad/docs/configuration/client#vault_retry
+[Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[legacy Vault authentication workflow]: /nomad/docs/integrations/vault/acl#authentication-without-workload-identity-legacy
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.7.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..58ec2bd352
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.7.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.7.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..01929d2277
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+- `selinux_label``(string: "")` - Specifies the SELinux label for the mount.
+  This is only supported on Linux hosts and when supported by the task driver. Refer to the task driver documentation for more information. Possible 
+  values are:
+
+  - `Z` -  Specifies that the volume content is private and unshared between 
+    containers.
+  - `z` - Specifies that the volume content is shared among containers.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.7.x/content/docs/networking/cni.mdx b/content/nomad/v1.7.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..0cee27400f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/networking/cni.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: CNI plugins and bridge networking
+description: |-
+  Learn how to install Container Network Interface (CNI) reference plugins, configure Nomad's bridge networking, and how to use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface (CNI)
+
+This page show you how to install the [CNI reference plugins][cni-plugin-docs]
+on your Linux distribution and configure bridge networking on your Nomad
+clients. You can apply this guide's workflow to installing any plugin that
+complies with the [Container Network Interface (CNI) Specification][cni-spec],
+but you should verify plugin compatibility with Nomad before deploying in
+production.
+
+## Introduction
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, [use a CNI network with a
+job](#use-a-cni-network-with-a-job).
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a CNI bridge mode configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration). Refer to
+the external [configuration
+format](https://www.cni.dev/docs/spec/#example-configuration) for a complete
+explanation of the fields.
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode.
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,20,32">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Use a CNI network with a job
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`. Nomad then schedules the workload on client nodes
+that have fingerprinted a CNI configuration with the given name. For example, to
+use the configuration named `mynet`, you should set the task group's network
+mode to `cni/mynet`. Nodes that have a network configuration defining a network
+named `mynet` in their `cni_config_dir` are eligible to run the workload.
+
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.7.x/content/docs/networking/index.mdx b/content/nomad/v1.7.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..4a5aa1c5fd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/networking/index.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Learn about Nomad's networking internals and how it compares with other
+  tools.
+---
+
+# Networking
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+Nomad networking is quite different from what you may familiar with from other
+tools. This section explains how networking works in Nomad, some of the
+different patterns and configurations you are likely to find and use, and how
+Nomad differs from other tools in this aspect.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/concepts/architecture#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/runtime/environment#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#template-examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+### Container Network Interface (CNI) reference plugins
+
+Nomad's bridge network leverages [CNI reference
+plugins](https://github.com/containernetworking/plugins) to provide an
+operating-system agnostic interface to configure workload networking. Nomad's
+network plugin support extends Nomad's built-in compute resource scheduling to
+allow scheduling tasks with specialty network configurations, which Nomad
+implements with a combination of CNI reference plugins and CNI configuration
+files.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/networking/service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/integrations/consul-connect).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/drivers/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/drivers/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/drivers/docker#network_mode)
+documentation and the [Networking](/nomad/docs/drivers/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [Service Discovery](/nomad/docs/networking/service-discovery)
+- [Service Mesh](/nomad/docs/networking/service-mesh)
+- [Container Network Interface](/nomad/docs/networking/cni) plugins guide
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.7.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.7.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..5017babf19
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Learn about how service discovery works in Nomad to connect workloads.
+---
+
+# Service discovery
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.7.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.7.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2828748c9f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Learn about how service mesh works in Nomad to securely connect and isolate
+  your workloads.
+---
+
+# Service mesh
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.7.x/content/docs/operations/index.mdx b/content/nomad/v1.7.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.7.x/content/docs/operations/key-management.mdx b/content/nomad/v1.7.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..2f8b92165f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers store key metadata in raft, but
+the encryption key material is stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Replication
+
+When a leader is elected, it creates the keyring if it does not already
+exist. When a key is added, the metadata will be replicated via raft. Each
+server runs a key replication process that watches for changes to the state
+store and will fetch the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election.
+
+## Restoring the Keyring from Backup
+
+Key material is never stored in raft. This prevents an attacker with a backup of
+the state store from getting access to encrypted variables. It also allows the
+HashiCorp engineering and support organization to safely handle cluster
+snapshots you might provide without exposing any of your keys or variables.
+
+However, this means that to restore a cluster from snapshot you need to also
+provide the keystore directory with the `.nks.json` key files on at least one
+server. The `.nks.json` key files are unique per server, but only one server's
+key files are needed to recover the cluster. Operators should include these
+files as part of your organization's backup and recovery strategy for the
+cluster.
+
+If you are recovering a Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
diff --git a/content/nomad/v1.7.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.7.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..b8267ac827
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,510 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------------------------------ | ------- |
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`             | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`             | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                         | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                    | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                   | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`            | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`            | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`         | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://developer.hashicorp.com/nomad/s/port-plan-failure
diff --git a/content/nomad/v1.7.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.7.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..2823055ba1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://developer.hashicorp.com/nomad/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.7.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.7.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..7dc11710a5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,188 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+By default, any stop signal to an agent (interrupt or terminate) will cause the
+agent to exit after ensuring its internal state is committed to disk as
+needed. You can configuration additional behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when `leave_on_interrupt` or `leave_on_terminate` are set the
+server will notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there will be a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, the [`server
+force-leave` command][] should be used to eject it from the consensus peer set.
+
+For clients, when `leave_on_interrupt` or `leave_on_terminate` are set and the
+client is configured with [`drain_on_shutdown`][], the client will drain its
+workloads before shutting down.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.7.x/content/docs/operations/stateful-workloads.mdx b/content/nomad/v1.7.x/content/docs/operations/stateful-workloads.mdx
new file mode 100644
index 0000000000..d8ecf7db08
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/operations/stateful-workloads.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Portworx or Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. More information can be found on the CSI
+concepts [documentation page](/nomad/docs/concepts/plugins/csi).
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+Host volumes mount paths from the host (the Nomad client) into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+backed by a distributed networked storage such as GlusterFS, or a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore
+you can use host volumes for both local somewhat persistent storage and for
+highly persistent networked storage.
+
+Because you need to declare host volumes in the Nomad agent's configuration
+file, you must restart the Nomad client to reconfigure them. This makes host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/concepts/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add/update/remove host volumes to make them available for
+consumption by Nomad Operators. Or, with networked host volumes, a Storage
+Administrator will need to provision the volumes and make them available to the
+Nomad clients. A System Administrator will then mount them on the Nomad clients.
+
+Host volumes backed by local storage help persist data that is not critical, for
+example an on-disk cache that can be rebuilt if needed. When backed by networked
+storage such as NFS/CIFS-mounted volumes or distributed storage via
+GlusterFS/Ceph, host volumes provide a quick option to consume highly available
+and reliable storage.
+
+Refer to the [Stateful workloads with Nomad host
+volumes](/nomad/tutorials/stateful-workloads/stateful-workloads-host-volumes)
+tutorial to learn more about using host volumes with Nomad.
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/tutorials/integrate-nomad/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/concepts/plugins/csi)
+- [Nomad CSI
+  tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [Portworx on
+  Nomad](https://docs.portworx.com/portworx-enterprise/install-portworx/install-with-other/nomad#operate-and-utilize-portworx-on-nomad)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..d94a1e5bf9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,497 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node Pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..1d3d5d7b7d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,156 @@
+---
+layout: docs
+page_title: Namespace Specification
+description: Learn about Nomad's Namespace specification.
+---
+
+# Namespace Specification
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+
+Nomad Namespaces may be specified as HCL files and submitted by the [`nomad
+namespace apply`][cli_ns_apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Namespace specifications do *not*
+support [HCL2][hcl2] features like functions.
+
+In [federated][] clusters, all updates to namespaces are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers  = ["java", "docker"]
+  disabled_task_drivers = ["raw_exec"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+
+# Vault configuration is a Nomad Enterprise feature.
+vault {
+  default = "default"
+  allowed = ["default", "infra"]
+}
+
+# Consul configuration is a Nomad Enterprise feature.
+consul {
+  default = "default"
+  allowed = ["all", "default"]
+}
+```
+
+## Namespace Specification Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+- `vault` <code>([Vault](#vault-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Vault clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+- `consul` <code>([Consul](#consul-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Consul clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+### `capabilities` Parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+### `node_pool_config` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs in
+  this namespace that don't define a node pool in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that are allowed
+  to be used by jobs in this namespace. By default, all node pools are allowed.
+  If an empty list is provided only the namespace's default node pool is
+  allowed. This field supports wildcard globbing through the use of `*` for
+  multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any node pool is allowed to be used, except for those that match any of these
+  patterns. This field cannot be used with `allowed`.
+
+### `vault` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Vault cluster to use for jobs
+  in this namespace that don't define a Vault cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Vault clusters that are
+  allowed to be used by jobs in this namespace. By default, all Vault clusters
+  are allowed.  If an empty list is provided only the namespace's default Vault
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Vault clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Vault cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+### `consul` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Consul cluster to use for jobs
+  in this namespace that don't define a Consul cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Consul clusters that are
+  allowed to be used by jobs in this namespace. By default, all Consul clusters
+  are allowed.  If an empty list is provided only the namespace's default Consul
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Consul clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Consul cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+[cli_ns_apply]: /nomad/docs/commands/namespace/apply
+[hcl2]: /nomad/docs/job-specification/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..f3ed362191
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Nomad Node Pool Specification
+description: Learn about Nomad's Node Pool specification.
+---
+
+# Nomad Node Pool Specification
+
+Nomad node pools may be specified as HCL files and submitted by the [`nomad node
+pool apply`][pool-apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad node pool specifications do *not*
+support HCL2 features like functions.
+
+Example node pool specification generated by [`nomad node pool
+init`][pool-init]:
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/docs/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Node Pool Specification Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` Parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/docs/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/docs/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..9ba9fc3cc1
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Increasing this value and re-issuing
+  `volume create` or `volume register` may expand the volume, if the CSI plugin
+  supports it.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**. Note that, like the rest of the volume specification, 
+  this block is declarative, and an update replaces it in its entirety, therefore 
+  all parameters need to be specified.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), or [`clone_id`](#clone_id)
+fields on **volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Volume Expansion
+
+CSI Volumes may be expanded (increased in size) if the CSI controller plugin
+(and node plugin, if required) has the `EXPAND_VOLUME` capability.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min)
+above the current real capacity of the volume (as seen with the
+[`volume status`][] command), and re-issue either [`volume create`][]
+or [`volume register`][].
+
+Nomad will reconcile the requested capacity by issuing expand volume requests
+to the controller plugin, and if required by the controller, also to the
+node plugins for each allocation that has a claim on the volume.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+
+### Example Volume Expansion
+
+Either [`volume create`][] or [`volume register`][] commands can trigger
+an expand to occur, after the volume has already been created or registered.
+
+Example using `volume create`, with a `volume.hcl` file:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+
+capacity_min = "50gib"
+capacity_max = "50gib"
+
+# ... etc ...
+```
+
+Create the volume:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+See its current capacity with [`volume status`][]:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 50 GiB
+```
+
+Update `volume.hcl`:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+# all of the above must remain the same
+
+capacity_min = "100gib" # double
+capacity_max = "100gib" # increased to match
+
+# ... etc ...
+```
+
+Run `volume create` again:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+Check the volume capacity again:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 100 GiB
+```
+
+If you encounter errors that are not clear from the command output,
+the CSI plugin allocation logs and/or Nomad leader server logs may be
+helpful.
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume status`]: /nomad/docs/commands/volume/status
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.7.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.7.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.7.x/content/docs/partnerships.mdx b/content/nomad/v1.7.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..b8c95e0b93
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. See the [Introduction](/nomad/intro) page for a full description of the current features. The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.7.x/content/docs/runtime/environment.mdx b/content/nomad/v1.7.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..a765f8a3b0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Prior to Nomad 0.5.5 the key was
+uppercased and since then both the original case and an uppercased version are
+injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.7.x/content/docs/runtime/index.mdx b/content/nomad/v1.7.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..86b05c6076
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details Nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.7.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.7.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..d2132a56a0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,202 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/drivers/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/drivers/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.7.x/content/docs/schedulers.mdx b/content/nomad/v1.7.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..7eb58f3d53
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/schedulers.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.7.x/content/docs/upgrade/index.mdx b/content/nomad/v1.7.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..aee9627e30
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/docs/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.7.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.7.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..37ce9631ef
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,2032 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.7.2
+
+Nomad 1.7.2 fixes a critical bug in CPU fingerprinting in Nomad 1.7.0 and
+1.7.1. You should not install Nomad 1.7.0 or 1.7.1 and instead install the
+latest Nomad 1.7.x version.
+
+## Nomad 1.7.0
+
+<Warning>
+
+Nomad 1.7.0 contains a critical bug in keyring replication. You should not
+install Nomad 1.7.0 and instead install the latest Nomad 1.7.x version.
+
+</Warning>
+
+#### Keyring Replication Failure After Leader Election
+
+Nomad 1.7.0 introduced new RSA keys to the keyring for use in signing workload
+identities. These keys were not correctly replicated from leader to
+followers. This results in all workload identity verification failing after a
+leader election.
+
+This bug was fixed in Nomad 1.7.1.
+
+#### Vault Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault token specific to the task.
+
+The existing workflow using a Vault token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.9. The [`vault.policies`][] field is also deprecated and will work
+only with the existing workflow. Instead, you should configure a suitable Vault
+role and use that.
+
+The following agent configuration fields are deprecated:
+- [`vault.allow_unauthenticated`][] will be removed in Nomad 1.9. Tasks will use
+  the workload identity without the user supplying a Vault token.
+- [`vault.task_token_ttl`][] will be removed in Nomad 1.9. With workload
+  identity, tasks will receive their TTL configuration from the Vault role.
+- [`vault.token`][] will be removed in Nomad 1.9. Nomad agents will no longer
+  make requests to authenticated endpoints except with a task's workload
+  identity.
+
+Before upgrading to Nomad 1.9 you will need to have configured authentication
+with Vault to work with workload identity. See [Migrating to Using Workload
+Identity with Vault][] for more details.
+
+#### Consul Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a service's or task's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+workload.
+
+The existing workflow using a Consul token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.9. The [`consul.allow_unauthenticated`][] agent configuration field
+will be removed in Nomad 1.9. Tasks will use the workload identity without the
+user supplying a Consul token.
+
+Before upgrading to Nomad 1.9 you will need to have configured authentication
+with Consul to work with workload identity. See [Migrating to Using Workload
+Identity with Consul][] for more details.
+
+#### RS256 JWT Signing Algorithm Support
+
+Prior to Nomad 1.7, workload identity JWTs were signed with the `EdDSA`
+algorithm. While `EdDSA` has numerous advantages as a signing algorithm, most
+third parties that accept JWTs expect the `RS256` signing algorithm to be used.
+
+Therefore starting in Nomad 1.7 *new* signing keys will generate an RSA key and
+sign workload identities with the `RS256` signing algorithm.
+
+Before setting up third party authentication methods to use workload
+identities, it is recommended to run [`nomad operator root keyring
+rotate`](/nomad/docs/commands/operator/root/keyring-rotate) to ensure you
+generate a new RSA key.
+
+To verify an RSA key is present you may check the [`/.well-known/jwks.json`
+endpoint](/nomad/api-docs/operator/keyring#list-active-public-keys) on any
+Nomad agent. If you see `"kty": "RSA"`, then an RSA key exists and you do not
+need to rotate keys.
+
+New Nomad clusters will use RSA by default and are not affected.
+
+#### CPU Fingerprinting Changes
+
+Starting in Nomad 1.7, Nomad clients improve the accuracy of detected CPU
+performance metrics. The fingerprinter now takes into account heterogeneous core
+types on applicable processors. In addition, Nomad will attempt to detect and
+use the base frequency of the processor rather than the turbo frequency when
+calculating the total available CPU bandwidth. The net result of these behaviors
+is that the calculated total CPU bandwidth available on a node may change when
+upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
+meets expectations before upgrading. The [cpu concepts][cpu] documentation
+contains guidance in understanding how Nomad detects CPU metrics.
+
+#### CPU EC2 Detection Changes
+
+Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
+performance data for every EC2 instance type. In 1.7 and later Nomad instead
+gathers this data by executing the `dmidecode` command. The `dmidecode` package
+must be installed manually on some Linux distributions before the Nomad agent
+is started.
+
+#### CPU Core Isolation
+
+Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`
+attribute will be restricted to using only the CPU cores assigned to them. In
+previous versions of Nomad these tasks could also make use of other non-reserved
+CPU cores. However this feature would cause severe performance problems for
+the Linux kernel as the number of tasks increased. Operators are encouraged
+to ensure tasks making use of the `cores` attribute are given sufficient CPU
+resources before upgrading.
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.7.0 changes the behavior of the [`distinct_hosts`][] constraint such that
+namespaces are taken into account when choosing feasible clients for allocation
+placement. The previous, less-expected behavior would cause **any** job with the
+same name running on a client to cause that node to be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`][]
+constraint over [`${node.pool}`][node_attributes].
+
+#### Loading Binaries from `plugin_dir` Without Configuration
+
+Starting with Nomad 1.7.0, loading plugins that are not referenced in the agent
+configuration file is deprecated. Future versions of Nomad will only load
+plugins that have a corresponding [`plugin`](/nomad/docs/configuration/plugin)
+block in the agent configuration file.
+
+#### Changes to `raw_exec`
+
+The `raw_exec` task driver now enforces memory limits via cgroups on Linux
+platforms similar to the `exec` and `docker` task drivers. The driver does
+support memory [oversubscription][oversub], which can be configured in such a
+way to nearly replicate the previously unlimited behavior.
+
+The `no_cgroups` configuration option no longer has any effect. Previously,
+setting `no_cgroups` would disable the mechanism where Nomad used the freezer
+cgroup to halt the process group of a Task before issuing a kill signal to each
+process. Starting in Nomad 1.7.0 this behavior is always enabled (and a similar
+mechanism has always been enabled on cgroups v2 systems).
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration][allow_caps_exec]:
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task][cap_add_exec] that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide][hard_guide]
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock] capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`][artifact_params]
+and [`headers`][artifact_params] fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`][artifact_env].
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`][artifact_fs_isolation].
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`][decompression_size_limit] and
+[`decompression_file_count_limit`][decompression_file_count_limit].
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`] configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`consul.allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`distinct_hosts`]: /nomad/docs/job-specification/constraint#distinct_hosts
+[`distinct_property`]: /nomad/docs/job-specification/constraint#distinct_property
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[`log_file`]: /nomad/docs/configuration#log_file
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`rejoin_after_leave`]: /nomad/docs/configuration/server#rejoin_after_leave
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[`vault.allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault.policies`]: /nomad/docs/job-specification/vault#policies
+[`vault.task_token_ttl`]: /nomad/docs/configuration/vault#task_token_ttl
+[`vault.token`]: /nomad/docs/configuration/vault#token
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[artifact_params]: /nomad/docs/job-specification/artifact#artifact-parameters
+[artifacts]: /nomad/docs/job-specification/artifact
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[cores]: /nomad/docs/job-specification/resources#cores
+[cpu]: /nomad/docs/concepts/cpu
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[enterprise licensing]: /nomad/docs/enterprise/license
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
+[hcl2]: https://github.com/hashicorp/hcl2
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[migrate]: /nomad/docs/job-specification/migrate
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[Migrating to Using Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[node pools]: /nomad/docs/concepts/node-pools
+[node_attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[nvidia]: /nomad/plugins/devices/nvidia
+[oversub]: /nomad/docs/job-specification/resources#memory-oversubscription
+[pki]: /vault/docs/secrets/pki
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[Workload Identity]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.7.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.7.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..b7aeefd95e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.7.x/content/intro/index.mdx b/content/nomad/v1.7.x/content/intro/index.mdx
new file mode 100644
index 0000000000..44757a5182
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.7.x/content/intro/use-cases.mdx b/content/nomad/v1.7.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..7082888c5d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.7.x/content/intro/vs/ecs.mdx b/content/nomad/v1.7.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.7.x/content/intro/vs/index.mdx b/content/nomad/v1.7.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.7.x/content/intro/vs/mesos.mdx b/content/nomad/v1.7.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.7.x/content/intro/vs/terraform.mdx b/content/nomad/v1.7.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.7.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.7.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.7.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.7.x/content/partials/envvars.mdx b/content/nomad/v1.7.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..d5b10e6074
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/envvars.mdx
@@ -0,0 +1,72 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                              |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                          |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                                    |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                            |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                         |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                                |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                                  |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                                   |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index.          |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                              |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                             |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                            |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                               |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                                     |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                            |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                              |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                             |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                                |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata. |
+| `CONSUL_HTTP_TOKEN`      | The tasks' Consul token. See [Consul Integration][consul] documentation for more details.                                                                                                                                                                                                |
+| `CONSUL_TOKEN`           | The tasks' Consul token. See [Consul Integration][consul] documentation for more details. This variable is deprecated and exists only for backwards compatibility.                                                                                                                       |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                                |
+
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/runtime/environment#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/integrations/vault-integration
+[consul]: /nomad/docs/integrations/consul-integration
diff --git a/content/nomad/v1.7.x/content/partials/general_options.mdx b/content/nomad/v1.7.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.7.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.7.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.7.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.7.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.7.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.7.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..bb25000698
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/install/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.7.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.7.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..d916ba11e6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,23 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.5.1
+release](https://github.com/containernetworking/plugins/releases/tag/v1.5.1),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.5.1
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.7.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.7.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.7.x/content/partials/install/manual-install.mdx b/content/nomad/v1.7.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.7.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.7.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.7.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.7.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.7.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.7.x/content/plugins/devices/index.mdx b/content/nomad/v1.7.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.7.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.7.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..a73e98adb7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,294 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+~> **Note**: The Nvidia device plugin setup has changed in Nomad 1.2. You must
+add a [`plugin`] block to your clients configuration and install the
+[external Nvidia device plugin][nvidia_plugin_download] into their
+[`plugin_dir`] prior to upgrading. See plugin options below for an example.
+Note the job specification remains the same.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..f0e3350922
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/awslabs/tc-redirect-tap
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..a49e922d1a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pledge][pledge]
+- [Pot][pot]
+- [Rkt][rkt]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+- [Windows IIS][nomad-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[rkt]: /nomad/plugins/drivers/community/rkt
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-iis]: /nomad/plugins/drivers/community/nomad-iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
+[pledge]: /nomad/plugins/drivers/community/pledge
+
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..e71ad18b5c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionally, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..0bc5c66b99
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+~> **Note:** The LXC client set up has changed in Nomad 0.9. You must use the new [plugin syntax][plugin] and install the external LXC driver in the [plugin_dir][plugin_dir] prior to upgrading. See [plugin options][plugin-options] below for an example. Note the job specification remains the same.
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/nomad-iis.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/nomad-iis.mdx
new file mode 100644
index 0000000000..a2514d92a4
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/nomad-iis.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `nomad_iis`
+
+This plugin is a task driver to run IIS Web Applications on Windows Servers. Each allocation will create an AppPool and a Website.  
+For a full documentation please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md).
+
+Unlike most other Nomad task drivers, this one is written in the C# language using ASP.NET. It uses the Microsoft.Web.Administration-API to communicate with IIS.
+
+<Note>
+At the moment I'm developing this plugin as a hobby project. Version 1 has not yet been reached and breaking changes may still occur.
+</Note>
+
+## Sample Job
+
+```hcl
+job "iis-test" {
+  datacenters = ["dc1"]
+  type = "service"
+
+  group "iis-test" {
+    count = 1
+    
+    network {
+      port "httplabel" {}
+    }
+
+    task "iis-test" {
+      driver = "iis"
+
+      config {
+        application {
+          path = "C:\\inetpub\\wwwroot"
+        }
+        application {
+          alias = "subapp"
+          path = "C:\\inetpub\\wwwroot"
+        }
+        
+        binding {
+          type = "http"
+          port = "httplabel"
+        }
+      }
+      
+      env {
+        my_key = "my-value"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 20
+      }
+    }
+  }
+}
+```
+
+Please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md) for the full documentation and configuration options.
+
+## Download
+
+Download the latest version from [here](https://github.com/sevensolutions/nomad-iis/releases).
+
+## Source Code
+
+You can get the full source code of this plugin on [Github](https://github.com/sevensolutions/nomad-iis).
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/pledge.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/pledge.mdx
new file mode 100644
index 0000000000..93925d0309
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/pledge.mdx
@@ -0,0 +1,332 @@
+---
+layout: docs
+page_title: 'Drivers: Pledge'
+description: The Pledge task driver is capable of blocking unwanted syscall and filesystem access.
+---
+
+# Pledge Driver
+
+Name: `pledge`
+
+The `pledge` driver executes programs similar to `exec` or `raw_exec`, but
+provides sandboxing by restricting syscalls the process is allowed to make.
+The `pledge` driver uses the [Landlock LSM][landlock] to restrict filesystem
+access, which can be significantly more efficient than creating a `chroot`.
+Isolation of CPU and memory resources is provided by leveraging features of
+cgroups v2. Network, PID, and IPC isolation is powered by Linux namespaces.
+
+Source on [GitHub][repository]
+
+Downloads on GitHub [releases][releases]
+
+#### Use cases
+
+The `pledge` driver is intended as a replacement for `raw_exec`. Sometimes
+there are those management tasks that just need to be run as `root` and directly
+access the filesystem or perform privileged operations. While `raw_exec`
+provides no isolation, the `pledge` driver uses Landlock to restrict the files
+or directories the task is allowed to access and modify. Specific groups of
+system calls are allow-listed in the task configuration, greatly reducing the
+attack surface of a mis-configured or compromised task.
+
+#### About
+
+The `pledge` driver is fundamentally powered by the [pledge utility for Linux]
+[pledge] by Justine Tunney. The driver invokes this `pledge.com` CLI tool along
+with `nsenter` and `unshare` to create a strict sandbox in which to execute a
+given command.
+
+## Task Configuration
+
+```hcl
+task "http" {
+  driver = "pledge"
+  config {
+    command    = "python3"
+    args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+    promises   = "stdio rpath inet"
+    unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+  }
+}
+```
+
+The `pledge` driver supports the following task configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. The driver will search
+  for the command on the `$PATH` of the Nomad Client unless an absolute path
+  is given.
+
+- `args` - (Optional) A list of arguments to the `command`. References to
+  environment variables or any interpolable Nomad variables will be interpolated
+  before launching the task.
+
+- `promises` - A set of promises needed for the command to run. See below for
+  more information.
+
+- `unveil` - (Optional) A list of filepaths and access rights to grant to the
+  command. See below for more information.
+
+- `importance` - (Optional) One of `"lowest"`, `"low"`, `"normal"`, `"high"`,
+  `"highest"`. Indicates the `nice` value with which to run `command` (default
+  is `"normal"`). A lower importance indicates the command should be given a
+  lower priority with regard to CPU time relative to other tasks.
+
+## Syscall Isolation (promises)
+
+When using the `pledge` task driver, by default most syscalls will become
+unavailable. A process that attempts to use an unavailable syscall will receive
+an `EPERM` error from the kernel. By specifying a set of `promises`, additional
+syscalls will be made available to the `command`.
+
+See the complete documetation for [promises][promises].
+
+| Promise | Description |
+| ------- | ------------|
+| `stdio` | allow stdio, threads, and benign system calls |
+| `rpath` | allow filesystem read operations |
+| `wpath` | allow filesystem write operations |
+| `cpath` | allow filesystem create operations |
+| `dpath` | allow creation of special files |
+| `flock` | allow file locking |
+| `tty` | allow terminal ioctls |
+| `recvfd` | allow recvmsg |
+| `sendfd` | allow sendmsg |
+| `fattr` | allow changing some struct stat bits |
+| `inet` | allow IPv4 and IPv6 |
+| `unix` | allow using Unix Domain Sockets |
+| `dns` | allow DNS |
+| `proc` | allow fork process creation and control |
+| `id` | allow setuid and friends |
+| `exec` | allow executing binaries |
+| `prot_exec` | allow creating executable memory |
+| `vminfo` | allow operations around reading `/proc` |
+| `tmppath` | allow access to `/tmp` |
+
+## Filesystem Isolation (unveil)
+
+By default the `command` will not be able to access the filesystem. Using some
+promises will implicitly allow access to specific parts of the filesystem where
+applicable. The `unveil` configuration is used to grant access to additional
+filesytem paths at a specified permission level.
+
+The format of the `unveil` parameter is a list of paths and associated
+permissions. Permissions can be any combination of `r`, `w`, `c` and `x` for
+read, write, create and execute privileges.
+
+Note that reading a file also requires the `rpath` promise, writing a file
+requires the `wpath` promise, creating a file requires the `cpath` promise, and
+executing a program requires the `exec` promise.
+
+#### Examples
+
+This example allows reading of the `/srv/www` directory.
+
+```hcl
+unveil = ["r:/srv/www"]
+```
+
+This example allows executing `/opt/bin/program` and reading `/etc/prog.d`.
+
+```hcl
+unveil = ["x:/opt/bin/program", "r:/etc/prog.d"]
+```
+
+It can be useful to `unveil` the Nomad Task Directory, which can be done by
+specifying the interpolation value.
+
+```hcl
+unveil = ["rwc:${NOMAD_TASK_DIR}"]
+```
+
+## Networking
+
+The `pledge` driver supports `none`, `host`, and `group` networking modes.
+
+#### host networking
+
+If using `host` networking mode, it can be very convenient to bless the
+[pledge][pledge] utility with the `cap_net_bind_service` Linux capability. This will
+enable Nomad tasks using the pledge driver to bind to privileged ports (i.e.
+below 1024) while using host networking mode.
+
+```shell-session
+sudo setcap cap_net_bind_service+eip /opt/bin/pledge-1.8.com
+```
+
+For convenience the `driver.pledge.cap.net_bind` Client attribute will indicate
+whether the Linux capability is set on the executable.
+
+#### bridge networking
+
+If using `bridge` networking mode, be sure to install the standard [CNI plugins]
+[cni] as required by the Nomad client.
+
+## Client Requirements
+
+The `pledge` driver requires the following:
+
+- 64-bit amd64 Linux host
+  - kernel version 5.13+
+  - cgroups v2 enabled
+- The `pledge` driver binary placed in [plugin_dir][plugin_dir]
+- The `pledge.com` utility executable on the host
+
+## Plugin Options
+
+- `pledge_executable` - The path to the `pledge.com` binary. The pledge utility
+can be [downloaded][download] directly from its creator, or compiled manually
+from [source][pledge_github].
+
+```hcl
+plugin "nomad-pledge-driver" {
+  config {
+    pledge_executable = "/opt/bin/pledge-1.8.com"
+  }
+}
+```
+
+## Client Attributes
+
+The `pledge` driver will set the following Client attributes:
+
+| Attribute | Description |
+| ----------| ----------- |
+| `driver.pledge` | set to `1` if the driver is enabled |
+| `driver.pledge.abs` | the absolute path to the pledge.com utility |
+| `driver.pledge.cap.net_bind` | indicates whether the NET_BIND linux capability is set |
+| `driver.pledge.os` | the detected operating system |
+
+## Resource Isolation
+
+CPU and memory resource isolation is enforced by cgroups v2 features, and is
+configured through the resources block in task configuration.
+
+```hcl
+resources {
+  cores  = 3
+  memory = 512
+}
+```
+
+#### cpu bandwidth
+
+The `pledge` driver always enforces a maximum CPU bandwidth available to the
+task. The bandwidth is calculated whether `resources.cpu` or `resources.cores`
+is configured.
+
+If `resources.cores` is set, the scheduler reserves that many CPU cores for use
+by the task, and only this task will be able to run on those cores.
+
+#### memory oversubscription
+
+If the Nomad scheduler is configured to enable memory [oversubscription]
+[oversub], the `pledge` driver will enable configuring `memory_max` in addition
+to `memory`. In this case, `memory_max` indicates the maximum amount of memory
+the task is able to request before being OOM killed, and `memory` represents a
+minimum amount of memory the kernel will guarantee is available for the Task.
+
+```hcl
+resources {
+  cpu        = 2000
+  memory     = 1024
+  memory_max = 2048
+}
+```
+
+## Capabilities
+
+The `pledge` driver implements the following [capabilities][capabilities].
+
+| Feature              | Implementation    |
+| ------------         | ------------------|
+| send signals         | true              |
+| exec                 | false             |
+| filesystem isolation | none (landlock)   |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+For sending signals, use the `nomad alloc signal` command.
+
+## Examples
+
+A larger set of examples are available in the [source][hack] repository.
+
+Showing how to `curl example.com`.
+
+```hcl
+job "curl" {
+  type = "batch"
+  group "group" {
+    task "curl" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command  = "curl"
+        args     = ["example.com"]
+        promises = "stdio rpath inet dns sendfd"
+      }
+    }
+  }
+}
+```
+
+An example using the Python built-in HTTP server to render a trivial web page.
+
+```hcl
+job "http" {
+  group "group" {
+    network {
+      mode = "host"
+      port "http" { static = 8181 }
+    }
+
+    task "task" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command    = "python3"
+        args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+        promises   = "stdio rpath inet"
+        unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+      }
+
+      template {
+        destination = "local/index.html"
+        data        = <<EOH
+<!doctype html>
+<html>
+  <title>example</title>
+  <body><p>Hello, friend!</p></body>
+</html>
+EOH
+      }
+    }
+  }
+}
+```
+
+## Troubleshooting
+
+When setting up a new Task using the `nomad-pledge-driver` task driver, it
+helps to run the command manually using the `pledge` utility to make sure the
+necessary promises and unveil paths are well understood. To figure out which
+syscalls process needs to make, it can be run under `strace -ff`. When a syscall
+is blocked, you'll see `"EPERM (Operation not permitted)"`
+
+```shell-session
+strace -ff /opt/bin/pledge-1.8.com -p "stdio rpath inet" -- curl example.com
+```
+
+[capabilities]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[cni]: https://developer.hashicorp.com/nomad/docs/install
+[download]: https://justine.lol/pledge/#download
+[hack]: https://github.com/shoenig/nomad-pledge-driver/tree/main/hack
+[landlock]: https://docs.kernel.org/security/landlock.html
+[oversub]: https://developer.hashicorp.com/nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
+[pledge]: https://justine.lol/pledge/
+[pledge_github]: https://github.com/jart/pledge
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[promises]: https://justine.lol/pledge/#promises
+[repository]: https://github.com/shoenig/nomad-pledge-driver
+[releases]: https://github.com/shoenig/nomad-pledge-driver/releases
+
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/rkt.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/rkt.mdx
new file mode 100644
index 0000000000..dfbb3dfb11
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/rkt.mdx
@@ -0,0 +1,227 @@
+---
+layout: docs
+page_title: 'Drivers: Rkt'
+description: The rkt task driver is used to run application containers using rkt.
+---
+
+~> **Deprecation Warning!**
+Nomad introduced the rkt driver in version 0.2.0. The rkt project had some
+early adoption; in recent times user adoption has trended away from rkt towards
+other projects. Project activity has declined and there are unpatched CVEs.
+The project has been [archived by the CNCF](https://github.com/rkt/rkt/issues/4004#issuecomment-507358362)
+
+Nomad 0.11 converted the rkt driver to an external driver. We will not prioritize features
+or pull requests that affect the rkt driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-rkt) for community ownership.
+
+# Rkt Driver
+
+Name: `rkt`
+
+The `rkt` driver provides an interface for using rkt for running
+application containers.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "rkt"
+
+  config {
+    image = "redis:7"
+  }
+}
+```
+
+The `rkt` driver supports the following configuration in the job spec:
+
+- `image` - The image to run. May be specified by name, hash, ACI address
+  or docker registry.
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `command` - (Optional) A command to execute on the ACI.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `trust_prefix` - (Optional) The trust prefix to be passed to rkt. Must be
+  reachable from the box running the nomad agent. If not specified, the image is
+  run with `--insecure-options=all`.
+
+- `insecure_options` - (Optional) List of insecure options for rkt. Consult `rkt --help`
+  for list of supported values. This list overrides the `--insecure-options=all` default when
+  no `trust_prefix` is provided in the job config, which can be effectively used to enforce
+  secure runs, using `insecure_options = ["none"]` option.
+
+  ```hcl
+  config {
+    image = "example.com/image:1.0"
+    insecure_options = ["image", "tls", "ondisk"]
+  }
+  ```
+
+- `dns_servers` - (Optional) A list of DNS servers to be used in the container.
+  Alternatively a list containing just `host` or `none`. `host` uses the host's
+  `resolv.conf` while `none` forces use of the image's name resolution configuration.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains to be used in
+  the containers.
+
+- `net` - (Optional) A list of networks to be used by the containers
+
+- `port_map` - (Optional) A key/value map of ports used by the container. The
+  value is the port name specified in the image manifest file. When running
+  Docker images with rkt the port names will be of the form `${PORT}-tcp`. See
+  [networking](#networking) below for more details.
+
+  ```hcl
+  port_map {
+    # If running a Docker image that exposes port 8080
+    app = "8080-tcp"
+  }
+  ```
+
+* `debug` - (Optional) Enable rkt command debug option.
+
+* `no_overlay` - (Optional) When enabled, will use `--no-overlay=true` flag for 'rkt run'.
+  Useful when running jobs on older systems affected by https://github.com/rkt/rkt/issues/1922
+
+* `volumes` - (Optional) A list of `host_path:container_path[:readOnly]` strings to bind
+  host paths to container paths.
+  Mount is done read-write by default; an optional third parameter `readOnly` can be provided
+  to make it read-only.
+
+  ```hcl
+  config {
+    volumes = ["/path/on/host:/path/in/container", "/readonly/path/on/host:/path/in/container:readOnly"]
+  }
+  ```
+
+* `group` - (Optional) Specifies the group that will run the task. Sets the
+  `--group` flag and overrides the group specified by the image. The
+  [`user`][user] may be specified at the task level.
+
+## Networking
+
+The `rkt` can specify `--net` and `--port` for the rkt client. Hence, there are two ways to use host ports by
+using `--net=host` or `--port=PORT` with your network.
+
+Example:
+
+```hcl
+task "redis" {
+	# Use rkt to run the task.
+	driver = "rkt"
+
+	config {
+		# Use docker image with port defined
+		image = "docker://redis:latest"
+		port_map {
+			app = "6379-tcp"
+		}
+	}
+
+	service {
+		port = "app"
+	}
+
+	resources {
+		network {
+			port "app" {
+			  static = 12345
+			}
+		}
+	}
+}
+```
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network).
+
+When you use port allocation, the image manifest needs to declare public ports and host has configured network.
+For more information, please refer to [rkt Networking](https://coreos.com/rkt/docs/latest/networking/overview).
+
+## Client Requirements
+
+The `rkt` driver requires the following:
+
+- The Nomad client agent to be running as the root user.
+- rkt to be installed and in your system's `$PATH`.
+- The `trust_prefix` must be accessible by the node running Nomad. This can be an
+  internal source, private to your cluster, but it must be reachable by the client
+  over HTTP.
+
+## Plugin Options
+
+- `volumes_enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use [plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+The `rkt` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `rkt.volumes.enabled` - Defaults to `true`. Allows tasks to bind host paths
+  (`volumes`) inside their container. Binding relative paths is always allowed
+  and will be resolved relative to the allocation's directory.
+
+## Client Attributes
+
+The `rkt` driver will set the following client attributes:
+
+- `driver.rkt` - Set to `1` if rkt is found on the host node. Nomad determines
+  this by executing `rkt version` on the host and parsing the output
+- `driver.rkt.version` - Version of `rkt` e.g.: `1.27.0`. Note that the minimum required
+  version is `1.27.0`
+- `driver.rkt.appc.version` - Version of `appc` that `rkt` is using e.g.: `1.1.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the rkt version is higher than 0.8.
+  constraint {
+    attribute = "${driver.rkt.version}"
+    operator  = ">"
+    value     = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation by delegating to `rkt`. Network
+isolation is not supported as of now.
+
+[user]: /nomad/docs/job-specification/task#user
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.7.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/index.mdx b/content/nomad/v1.7.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..88f5244ad5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Starting with Nomad 0.9, task drivers are now pluggable. This gives users the
+flexibility to introduce their own drivers without having to recompile Nomad.
+You can view the [plugin block][plugin] documentation for examples on how to
+use the `plugin` block in Nomad's client configuration. Note that we have
+introduced new syntax when specifying driver options in the client configuration
+(see [docker][docker_plugin] for an example). Keep in mind that even though all
+built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.7.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..2b9d4685c7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,590 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+Download from HashiCorp [releases][releases]
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting tlsVerify to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tlsVerify = false
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
\ No newline at end of file
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.7.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..bec2c3778d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Note:** The ECS Task Driver is an example Remote Task Driver and **not
+intended for production use.**
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accommodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.7.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.7.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..52c652d745
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Nomad 1.1.0 introduces support for Remote Task Drivers. Remote Task Drivers
+allow custom task driver plugins to execute tasks using nonlocal runtimes such
+as cloud container runtimes. Without this support, task driver plugins trying
+to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature in Nomad 1.1.0 improves these behaviors for
+custom plugins that advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]: /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.7.x/content/plugins/index.mdx b/content/nomad/v1.7.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..87d3059efd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad 0.9 introduced a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.7.x/content/security.mdx b/content/nomad/v1.7.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.7.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..8df4e33d17
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. If the special wildcard namespace value `*` is used, the Autoscaler
+agent will retrieve scaling policies from all namespaces. A future version will
+include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad 0.11 includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+When utilizing the High-Availability feature added in v0.4.0, the ACL policy
+needs to include capabilities that allow the Nomad Autoscaler to obtain and release Nomad variable
+locks. The namespace identifier should match the configured
+[`high_availability.lock_namespace`][autoscaler_ha_lock_namespace] parameter,
+and the path should match the [`high_availability.lock_path`][autoscaler_ha_lock_path]
+parameter.
+
+```hcl
+namespace "default" {
+  variables {
+    path "nomad-autoscaler/lock" {
+      capabilities = ["write"]
+    }
+  }
+}
+```
+
+If running Nomad Autoscaler Enterprise, the following ACL policy addition is
+needed to ensure it can read the Nomad Enterprise license.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
+[autoscaler_ha_lock_namespace]: /nomad/tools/autoscaling/agent/high_availability#lock_namespace
+[autoscaler_ha_lock_path]: /nomad/tools/autoscaling/agent/high_availability#lock_path
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..3acc904e96
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/high_availability.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/high_availability.mdx
new file mode 100644
index 0000000000..0d8df1ac85
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/high_availability.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: high_availability Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "high_availability" block is used to configure the Nomad Autoscaler agent
+  in high availability (HA) mode. In this mode, multiple agents participate in
+  leadership election, with only the leader conducting autoscaling calculations
+  and actions.
+---
+
+# `high_availability` Block
+
+<Placement groups={['high_availability']} />
+
+The `high_availability` block is used to configure the Nomad Autoscaler agent
+in high availability (HA) mode. In this mode, multiple agents participate in
+leadership election, with only the leader conducting autoscaling calculations
+and actions.
+
+```hcl
+high_availability {
+  enabled        = true
+  lock_namespace = "prod"
+  lock_path      = "custom/lock/path"
+  lock_ttl       = "30s"
+  lock_delay     = "15s"
+}
+```
+
+## `high_availability` Parameters
+
+- `enabled` `(bool: false)` - Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired.
+
+- `lock_namespace` `(string: "default")` - Defines the namespace of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process.
+
+- `lock_path` `(string: "nomad-autoscaler/lock")` - Defines the path of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad Autoscaler
+  agents expected to take part in the same leadership election process.
+
+- `lock_ttl` `(string: "60s")` - Defines the lease period or TTL of the lock used
+  to sync the leader when running in high availability mode. If the Nomad Autoscaler
+  agent does not renew the lock within this period, the lock is considered lost.
+
+- `lock_delay` `(string: "30s")` - Defines the period that the lock will be blocked
+  after the TTL expired without being renewed. This helps prevent split brain
+  situations.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..124dba0a93
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace. If set to `*` all namespaces are queried.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..b5988c78aa
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+- `-high-availability-enabled`: Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired. It defaults to `false`.
+
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
+- `-high-availability-lock-path`: Defines the path of the Nomad variable that
+  will be used to sync the leader when running in high availability mode. This
+  parameter needs to be the same on all Nomad Autoscaler agents expected to
+  take part in the same leadership election process. Defaults to
+  `nomad-autoscaler/lock`.
+
+- `-high-availability-lock-ttl`: Defines the lease period or TTL of the lock used
+  to sync the leader when running on high availability mode. If the Nomad
+  Autoscaler agent does not renew the lock within this period, the lock is
+  considered lost. Defaults to `60s`.
+
+- `-high-availability-lock-delay`: Defines the period that the lock will be
+  blocked after the TTL expired without being renewed. This helps prevent split
+  brain situations. Defaults to `30s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..dc2554d004
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..9fdbbead9a
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..23c9391edf
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds. This value is always **inclusive**, meaning a
+  metric with the exact same value as `lower_bound` is considered within
+  bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds. This value is always **exclusive**, meaning a
+  metric with the exact same value as `upper_bound` is considered **out** of
+  bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above or
+equal to `lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d293ba125f
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..656fb74905
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+- `retry_attempts` `(int: "15")` - The number of attempts to make while waiting
+  for the cluster to stabilize after a scaling action. It may need to be tuned
+  up if errors such as `failed to ensure all activities completed` occur.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. It may be overridden per policy.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. If set, it overrides the plugin configuration.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_scale_in_protection]: https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..8d4d5f158e
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+~> The `azure-vmss` target plugin requires Azure fingerprinting, which was
+added in Nomad 1.0. If you are running a previous version of Nomad you will to
+set a [meta tag][client_meta_tag] in all of your nodes.
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+### Client meta tag
+
+The `azure-vmss` target plugin requires Nomad 1.0 for Azure fingerprinting.
+Alternatively, you can set a [client meta tag][nomad_client_meta_tag] called
+`unique.platform.azure.name` with the value being the Azure VMSS node name.
+This can be retrieved programatically via the [Azure Instance Metadata
+service][azure_instance_metadata].
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..0d4f106125
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..77fab0bae8
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `query_window_offset` - Defines a time offset from the current time to apply
+  to the query window. A short offset (for example, `1m`) can be used to avoid
+  reading unstable and incomplete data from the APM. A long offset (`168h`,
+  representing 7 days ago) can be used for predictive scaling based on past
+  data.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.7.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.7.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..52c484463c
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.7.x/content/tools/index.mdx b/content/nomad/v1.7.x/content/tools/index.mdx
new file mode 100644
index 0000000000..6d14c39cbd
--- /dev/null
+++ b/content/nomad/v1.7.x/content/tools/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+- [OpenAPI](https://github.com/hashicorp/nomad-openapi) - An OpenAPI/Swagger spec for Nomad, allowing for programmatic generation of SDKs and documentation. Includes a reference implementation in Go built on top of a generated client.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Port Forward](https://github.com/Mongey/nomad-port-forward) - A tool for forwarding ports from a Nomad job to your local machine
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.7.x/data/api-docs-nav-data.json b/content/nomad/v1.7.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..e89bec40ac
--- /dev/null
+++ b/content/nomad/v1.7.x/data/api-docs-nav-data.json
@@ -0,0 +1,211 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      },
+      {
+        "title": "Upgrade Check",
+        "path": "operator/upgrade-check"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "variables"
+      },
+      {
+        "title": "Variables",
+        "path": "variables/variables"
+      },
+      {
+        "title": "Locks",
+        "path": "variables/locks"
+      }
+    ]
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.7.x/data/docs-nav-data.json b/content/nomad/v1.7.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..25c97be7dd
--- /dev/null
+++ b/content/nomad/v1.7.x/data/docs-nav-data.json
@@ -0,0 +1,2378 @@
+[
+  {
+    "title": "Install Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/consul"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/consul/acl"
+          },
+          {
+            "title": "Service Mesh",
+            "path": "integrations/consul/service-mesh"
+          }
+        ]
+      },
+      {
+        "title": "Vault",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/vault"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/vault/acl"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "ACL",
+        "path": "concepts/acl"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "CPU",
+        "path": "concepts/cpu"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Node Pools",
+        "path": "concepts/node-pools"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "reporting",
+        "path": "configuration/reporting"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "auth-method",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/auth-method/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/auth-method/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/auth-method/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/auth-method/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/auth-method/update"
+              }
+            ]
+          },
+          {
+            "title": "binding-rule",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/binding-rule/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/binding-rule/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/binding-rule/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/binding-rule/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/binding-rule/update"
+              }
+            ]
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "checks",
+            "path": "commands/alloc/checks"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "action",
+            "path": "commands/job/action"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "restart",
+            "path": "commands/job/restart"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/license/inspect"
+          }
+        ]
+      },
+      {
+        "title": "login",
+        "path": "commands/login"
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "meta",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "commands/node/meta"
+              },
+              {
+                "title": "apply",
+                "path": "commands/node/meta/apply"
+              },
+              {
+                "title": "read",
+                "path": "commands/node/meta/read"
+              }
+            ]
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "node pool",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node-pool"
+          },
+          {
+            "title": "apply",
+            "path": "commands/node-pool/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/node-pool/delete"
+          },
+          {
+            "title": "info",
+            "path": "commands/node-pool/info"
+          },
+          {
+            "title": "init",
+            "path": "commands/node-pool/init"
+          },
+          {
+            "title": "jobs",
+            "path": "commands/node-pool/jobs"
+          },
+          {
+            "title": "list",
+            "path": "commands/node-pool/list"
+          },
+          {
+            "title": "nodes",
+            "path": "commands/node-pool/nodes"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              },
+              {
+                "title": "health",
+                "path": "commands/operator/autopilot/health"
+              }
+            ]
+          },
+          {
+            "title": "client-state",
+            "path": "commands/operator/client-state"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              },
+              {
+                "title": "transfer-leadership",
+                "path": "commands/operator/raft/transfer-leadership"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "setup",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/setup"
+          },
+          {
+            "title": "consul",
+            "path": "commands/setup/consul"
+          },
+          {
+            "title": "vault",
+            "path": "commands/setup/vault"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "lock",
+            "path": "commands/var/lock"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "action",
+        "path": "job-specification/action"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "consul",
+        "path": "job-specification/consul"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "numa",
+        "path": "job-specification/numa"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node Pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "href": "/plugins/drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/nomad-iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "source",
+            "href": "/tools/autoscaling/agent/source"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      },
+      {
+        "title": "Considerations for Stateful Workloads",
+        "path": "operations/stateful-workloads"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "Automated license utilization reporting",
+            "path": "enterprise/license/utilization-reporting"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      },
+      {
+        "title": "Sentinel",
+        "path": "enterprise/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.7.x/data/intro-nav-data.json b/content/nomad/v1.7.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..0fdab4c70f
--- /dev/null
+++ b/content/nomad/v1.7.x/data/intro-nav-data.json
@@ -0,0 +1,31 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "href": "https://developer.hashicorp.com/nomad/tutorials/get-started"
+  }
+]
diff --git a/content/nomad/v1.7.x/data/plugins-nav-data.json b/content/nomad/v1.7.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..044fc7ea4a
--- /dev/null
+++ b/content/nomad/v1.7.x/data/plugins-nav-data.json
@@ -0,0 +1,125 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "path": "drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/nomad-iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.7.x/data/tools-nav-data.json b/content/nomad/v1.7.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..195677fadc
--- /dev/null
+++ b/content/nomad/v1.7.x/data/tools-nav-data.json
@@ -0,0 +1,231 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "high_availability",
+            "path": "autoscaling/agent/high_availability"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.7.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.7.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.7.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.7.x/img/autoscaling/control-loop.png b/content/nomad/v1.7.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.7.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.7.x/img/autoscaling/policy-eval.png b/content/nomad/v1.7.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.7.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.7.x/img/consul-integration-auth-method.png b/content/nomad/v1.7.x/img/consul-integration-auth-method.png
new file mode 100644
index 0000000000..485cb5d6ac
Binary files /dev/null and b/content/nomad/v1.7.x/img/consul-integration-auth-method.png differ
diff --git a/content/nomad/v1.7.x/img/consul-integration-wi.png b/content/nomad/v1.7.x/img/consul-integration-wi.png
new file mode 100644
index 0000000000..b20fcc3863
Binary files /dev/null and b/content/nomad/v1.7.x/img/consul-integration-wi.png differ
diff --git a/content/nomad/v1.7.x/img/consul-integration-wid-acl-token.png b/content/nomad/v1.7.x/img/consul-integration-wid-acl-token.png
new file mode 100644
index 0000000000..bfb587564b
Binary files /dev/null and b/content/nomad/v1.7.x/img/consul-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.7.x/img/count-dashboard.png b/content/nomad/v1.7.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.7.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.7.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.7.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.7.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/favicon-16x16.png b/content/nomad/v1.7.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/favicon-194x194.png b/content/nomad/v1.7.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/favicon-32x32.png b/content/nomad/v1.7.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/favicon.ico b/content/nomad/v1.7.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.7.x/img/favicons/mstile-144x144.png b/content/nomad/v1.7.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/mstile-150x150.png b/content/nomad/v1.7.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/mstile-310x150.png b/content/nomad/v1.7.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/mstile-310x310.png b/content/nomad/v1.7.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/mstile-70x70.png b/content/nomad/v1.7.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.7.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.7.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.7.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.7.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.7.x/img/home-hero-pattern.svg b/content/nomad/v1.7.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.7.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/logo-hashicorp.svg b/content/nomad/v1.7.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.7.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.7.x/img/logo-text.svg b/content/nomad/v1.7.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.7.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.7.x/img/networking/bridge.png b/content/nomad/v1.7.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.7.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.7.x/img/networking/docker_bridge.png b/content/nomad/v1.7.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.7.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.7.x/img/networking/port_mapping.png b/content/nomad/v1.7.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.7.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-architecture-global.png b/content/nomad/v1.7.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-architecture-region.png b/content/nomad/v1.7.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-bg-pattern.svg b/content/nomad/v1.7.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.7.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.7.x/img/nomad-bridge-network.png b/content/nomad/v1.7.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-data-model.png b/content/nomad/v1.7.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-evaluation-flow.png b/content/nomad/v1.7.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-kubernetes.png b/content/nomad/v1.7.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-numa.png b/content/nomad/v1.7.x/img/nomad-numa.png
new file mode 100644
index 0000000000..0609d7e196
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-numa.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-panel-learn.svg b/content/nomad/v1.7.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.7.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.7.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.7.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.7.x/img/nomad-pe-cores.png b/content/nomad/v1.7.x/img/nomad-pe-cores.png
new file mode 100644
index 0000000000..e11c011d6e
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-pe-cores.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-vars-leader-election-sdk.png b/content/nomad/v1.7.x/img/nomad-vars-leader-election-sdk.png
new file mode 100644
index 0000000000..a547218579
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-vars-leader-election-sdk.png differ
diff --git a/content/nomad/v1.7.x/img/nomad-workload.png b/content/nomad/v1.7.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.7.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.7.x/img/og-image.png b/content/nomad/v1.7.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.7.x/img/og-image.png differ
diff --git a/content/nomad/v1.7.x/img/pattern.svg b/content/nomad/v1.7.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.7.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/practice-pattern.svg b/content/nomad/v1.7.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.7.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/usecase-callout-pattern.svg b/content/nomad/v1.7.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.7.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/usecase-hero-pattern.svg b/content/nomad/v1.7.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.7.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.7.x/img/vault-integration-auth-method.png b/content/nomad/v1.7.x/img/vault-integration-auth-method.png
new file mode 100644
index 0000000000..b6c1d601b9
Binary files /dev/null and b/content/nomad/v1.7.x/img/vault-integration-auth-method.png differ
diff --git a/content/nomad/v1.7.x/img/vault-integration-auth-overview.png b/content/nomad/v1.7.x/img/vault-integration-auth-overview.png
new file mode 100644
index 0000000000..ad26bed43a
Binary files /dev/null and b/content/nomad/v1.7.x/img/vault-integration-auth-overview.png differ
diff --git a/content/nomad/v1.7.x/img/vault-integration-wid-acl-token.png b/content/nomad/v1.7.x/img/vault-integration-wid-acl-token.png
new file mode 100644
index 0000000000..7fd4b406ea
Binary files /dev/null and b/content/nomad/v1.7.x/img/vault-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.7.x/redirects.jsonc b/content/nomad/v1.7.x/redirects.jsonc
new file mode 100644
index 0000000000..690b611eb4
--- /dev/null
+++ b/content/nomad/v1.7.x/redirects.jsonc
@@ -0,0 +1,81 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+
+  /**
+   * /s/* redirects for useful links that need a stable URL but we may need to
+   * change its destination in the future.
+   */
+  {
+    "source": "/nomad/s/envoy-bootstrap-error",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/consul/service-mesh#troubleshooting",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/vault-workload-identity-migration",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault",
+    "permanent": false,
+  },
+  // Rename and re-arrange Autoscaling Internals section
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+  // Redirect Consul and Vault integrations page
+  {
+    "source": "/nomad/docs/integrations/vault-integration",
+    "destination": "/nomad/docs/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-integration",
+    "destination": "/nomad/docs/integrations/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-connect",
+    "destination": "/nomad/docs/integrations/consul/service-mesh",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.8.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..56d503378a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,510 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+  The name can contain alphanumeric characters and dashes. This name must be
+  unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and `JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either `local` or `global`.
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL `${foo}` syntax.
+  Defaults to `${auth_method_type}-${auth_method_name}`.
+
+ - `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set, it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+    any `.well-known` component (base path). Required for `OIDC` method type.
+    Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+    `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+    your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+    configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+    to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+    `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+    signatures. Either this, the `JWTValidationPubKeys` or the
+    `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+    to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+    validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+    validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+    validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Names is the identifier of the ACL auth
+  method.  The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth role SSO identifier. Currently, the
+  only supported Type is "OIDC."
+
+- `TokenLocality` `(string: "")` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either "local" or "global"
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL '${foo}' syntax.
+  Defaults to '${auth_method_type}-${auth_method_name}'
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL auth method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: nil)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: "")` - The OIDC discovery URL, without
+    any .well-known component (base path).
+
+  - `OIDCClientID` `(string: "")` - The OAuth client ID configured with
+    your OIDC provider.
+
+  - `OIDCClientSecret` `(string: "")` - The OAuth client secret
+    configured with your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.8.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..93451a8704
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `POST` | `/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/index.mdx b/content/nomad/v1.8.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..318f42b704
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/login.mdx b/content/nomad/v1.8.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.8.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.8.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..4e07722b8c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,188 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                       | Produces       |
+| ------ | -------------------------- | -------------- |
+| `POST` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given
+  namespace, job, group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - The namespace to attach the policy.
+    Required if `JobID` is set.
+
+  - `JobID` `(string: <optional>)` - The job to attach to the policy. Required
+    if `Group` is set.
+
+  - `Group` `(string: <optional>)` - The group to attach to the policy.
+    Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - The task to attach to the policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                       | Produces       |
+| -------- | -------------------------- | -------------- |
+| `DELETE` | `/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.8.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..b19dca9930
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `POST` | `/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                 | Produces       |
+| -------- | -------------------- | -------------- |
+| `DELETE` | `/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.8.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..9d81cee9c9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                      | Produces       |
+| -------- | ------------------------- | -------------- |
+| `DELETE` | `/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `POST` | `/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.8.x/content/api-docs/agent.mdx b/content/nomad/v1.8.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..0331407b2b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint        | `enable_debug` | ACLs | **Available?** |
+| --------------- | -------------- | ---- | -------------- |
+| /v1/agent/pprof | unset          | n/a  | no             |
+| /v1/agent/pprof | `true`         | n/a  | yes            |
+| /v1/agent/pprof | `false`        | n/a  | no             |
+| /v1/agent/pprof | unset          | off  | no             |
+| /v1/agent/pprof | unset          | on   | **yes**        |
+| /v1/agent/pprof | `true`         | off  | yes            |
+| /v1/agent/pprof | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.8.x/content/api-docs/allocations.mdx b/content/nomad/v1.8.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..65eded2e2a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/allocations.mdx
@@ -0,0 +1,1043 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`  |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+## Override Pause Schedule State
+
+<EnterpriseAlert />
+
+The endpoint is used to override the [`schedule`][schedule] for tasks using
+time based execution.
+
+| Method         | Path                                    | Produces           |
+| -------------- | --------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:job-submit`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ echo '{"Task": "schedtask", "ScheduleState": "run"}' | \
+  nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0
+}
+```
+
+## Read Pause Schedule State
+
+<EnterpriseAlert />
+
+Retrieve the [`schedule`][schedule] state for a task using time based execution.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required              |
+| ---------------- | ------------------------- |
+| `NO`             | `namespace:read-job`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `task` - Specifies the task from which to retrieve the time based task
+  execution state.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause?task=schedtask
+```
+
+### Sample Response
+
+```json
+{
+  "ScheduleState": "scheduled_pause"
+}
+```
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[schedule]: /nomad/docs/job-specification/schedule
diff --git a/content/nomad/v1.8.x/content/api-docs/client.mdx b/content/nomad/v1.8.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..b58244ad26
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.8.x/content/api-docs/deployments.mdx b/content/nomad/v1.8.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/evaluations.mdx b/content/nomad/v1.8.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..2984cdaf1e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.8.x/content/api-docs/events.mdx b/content/nomad/v1.8.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..e99bf630d7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/events.mdx
@@ -0,0 +1,391 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](http://ndjson.org/). This means splitting the streaming
+response at every `\n` character will guarantee each message is a valid JSON object.
+Note that each JSON object may include multiple events (high server activity) or no
+events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `NodePool`   | `management`         |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| NodePool   | NodePool                        |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| NodePoolUpserted              |
+| NodePoolDeleted               |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.advertise.address": "127.0.0.1:4646",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/index.mdx b/content/nomad/v1.8.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..1f4ca6c921
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/index.mdx
@@ -0,0 +1,731 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter.
+
+Here is an example using curl to query the `qa` namespace:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=qa'
+```
+
+Use a wildcard (`*`) to query all namespaces:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=*'
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> \
+    --data-urlencode 'filter=<filter expression>'
+```
+
+The filter expression can also be specified in the
+[`-filter`][cli_operator_api_filter] flag of the
+[`nomad operator api`][cli_operator_api] command.
+
+```shell-session
+$ nomad operator api -filter '<filter expression>' /v1/<path>
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### List Stubs
+
+Some list endpoints return a reduced version of the resource being queried.
+This smaller version is called a _stub_ and may have different fields than the
+full resource definition. To allow more expressive filtering operations, the
+filter is applied to the full version, not the stub.
+
+If a request returns an error such as `error finding value in datum` the field
+used in filter expression may need to be adjusted. For example, filtering on
+node addresses should use the `HTTPAddr` field of the full node definition
+instead of `Address` field present in the stub.
+
+```shell-session
+$ nomad operator api -filter 'HTTPAddr matches "10.0.0..+"' /v1/nodes
+```
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Datacenters contains "dc2"' /v1/jobs
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Status != "successful"' /v1/deployments
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
+
+[cli_operator_api]: /nomad/docs/commands/operator/api
+[cli_operator_api_filter]: /nomad/docs/commands/operator/api#filter
diff --git a/content/nomad/v1.8.x/content/api-docs/jobs.mdx b/content/nomad/v1.8.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..c9ef94c0f6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2686 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2`, `hcl1`, or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `IdempotencyToken` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if
+  the passed `JobModifyIndex` matches the current job's index. If the index is
+  zero, the register only occurs if the job is new. This paradigm allows
+  check-and-set style job updating.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as
+  part of the scaling event.  Indicates an error state preventing scaling; one
+  of `Message` or `Error` must be provided.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted
+  as part of the scaling event.  Indicates information or reason for scaling;
+  one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+   enabled, this value must match a namespace that the token is allowed to
+   access. This is specified as a query string parameter.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be scaled when it would be
+  denied by policy.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling
+  operation.  Must contain a field `Group` with the name of the task group that
+  is the target of this scaling action.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## List Job Actions
+
+This endpoint lists the actions available to tasks within a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/actions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/job/my-job/actions'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Args": [
+      "-s",
+      "wttr.in/Toronto?format=3"
+    ],
+    "Command": "/usr/bin/curl",
+    "Name": "weather",
+    "TaskGroupName": "group1",
+    "TaskName": "task"
+  },
+  {
+    "Args": [
+      "-c",
+      "nomad alloc status ${NOMAD_ALLOC_ID}"
+    ],
+    "Command": "/bin/sh",
+    "Name": "get-alloc-info",
+    "TaskGroupName": "group2",
+    "TaskName": "task"
+  },
+]
+```
+
+## Run Action
+
+This endpoint executes a predefined action from a job in the
+context of a specific task within an allocation. It opens a WebSocket to
+transmit output from the running action.
+
+
+| Method      | Path                     | Produces               |
+| ----------- | ------------------------ | ---------------------- |
+| `WebSocket` | `/v1/job/:job_id/action` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if task driver does not support [file system isolation](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error)) |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job containing the
+  action. This is specified as part of the path.
+- `action` `(string: <required>)` - Specifies the name of the action to be
+  executed, as defined within the job's task. Specified as a query parameter.
+- `alloc_id` `(string: <required>)` - Specifies the UUID of the target
+  allocation. Specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task where the action is
+  defined. Specified as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this action.
+  Specified as a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the
+  authentication token in the first frame, as a query parameter.
+
+### WebSocket Upgrade Request
+
+Actions are executed with a WebSocket upgrade request. The request headers
+must include the standard WebSocket upgrade parameters. Example:
+
+```shell-session
+$ curl \
+  -X GET \
+  -H 'Connection: Upgrade' \
+  -H 'Upgrade: websocket' \
+  -H 'Sec-Websocket-Version: 13' \
+  -H 'Sec-Websocket-Key: x3JJHMbDL1EzLkh9GBhXDw==' \
+  'http://127.0.0.1:4646/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+or
+```shell-session
+$ nomad operator api \
+-H "Connection: Upgrade" \
+-H "Upgrade: websocket" \
+-H "Sec-WebSocket-Version: 13" \
+-H "Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==" \
+'/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+
+### Request Frames
+
+Unlike [alloc exec](/nomad/api-docs/allocations#exec-allocation), Actions do
+not take input in the form of request frames using `stdin`. Instead, the name
+of the action is passed as a query parameter and the associated input is handled
+on the allocation apart from the stream.
+
+When `?ws_handshake=true`, the first request frame must contain the
+authentication token. Similarly, when `?tty=true`, a `tty_size` frame may be
+provided to indicate a resize.
+
+The following are valid input frames:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well
+as exit codes. Response frames encompass the full range of terminal emulator outputs, including
+the control characters necessary to render interactive applications.
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+{"exited":true,"result":{}}
+```
+
+The stdout data returned in the response frames from the job action endpoint is
+base64 encoded. This encoding is necessary to ensure that the data can be
+transmitted over WebSocket connections without issues, regardless of its content.
+
+### Sample Request and Response
+
+This example response includes instances of the ANSI "control sequence
+introducer" (CSI), which is ASCII code 27 followed by `[`. The second stdout
+frame includes the desired output from the Action in question, which prints
+the local weather.
+
+```
+# Sample WebSocket request to execute an action
+WebSocket Request: /v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+
+# Toronto: ⛅️  -1°C
+{"stdout":{"data":"VG9yb250bzog4puF77iPICAtMcKwQw0K"}}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.8.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..6af8f1fe1e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1246 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+- `Ui` - Options to modify the presentation of the Job index page in the Web UI.
+  When specified, a description and any number of links will be added to the top of
+  the job page in question.
+
+  - `Description` - a markdown-enabled string description of the job
+    jobs.
+
+  - `Links` - Anchor link that will appear at the top of the job page.
+
+    - `Label` - The shown name of the link
+    - `Url` - The address that the link will point to
+
+  An example `ui` block:
+
+  ```json
+  "Ui": {
+    "Description": "A job that uses **Nomad Variables** to modify its output",
+    "Links": [
+      {
+        "Label": "Learn more about Nomad Variables",
+        "Url": "https://developer.hashicorp.com/nomad/docs/concepts/variables"
+      },
+      {
+        "Label": "See this job on Github",
+        "Url": "https://github.com/hashicorp/nomad/blob/main/ui/app/utils/default_jobs/variables.js"
+      }
+    ]
+  }
+  ```
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker and rkt.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Unlike `PortLabel`,
+      this setting is _not_ inherited from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. Numeric ports may be 
+      used if `AddressMode: "driver"` is set on the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks. 
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. The template can reference 
+[Nomad's runtime environment variables][env]. For a full list of the API template
+functions, please refer to the [Consul Template README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.8.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.8.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..53734a477d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,41 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+- [`nix-nomad`](https://github.com/tristanpemble/nix-nomad) - HashiCorp Nomad job definitions in Nix
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.8.x/content/api-docs/metrics.mdx b/content/nomad/v1.8.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/namespaces.mdx b/content/nomad/v1.8.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/node-pools.mdx b/content/nomad/v1.8.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.8.x/content/api-docs/nodes.mdx b/content/nomad/v1.8.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..2acff9d512
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1147 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.advertise.address": "127.0.0.1:4646",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.8.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..cfe2ea2a9d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,253 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ],
+  "Leader": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+  "Voters": [
+    "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+    "e36ee410-cc3c-0a0c-c724-63817ab30303"
+  ],
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+<EnterpriseAlert>
+  This API endpoint return with more information in Nomad Enterprise. This is
+  not present in Nomad Community Edition.
+</EnterpriseAlert>
+
+When using Nomad Enterprise this endpoint will return more information about the
+underlying actions and state of Autopilot.
+
+```json
+{
+  ...
+  "ReadReplicas": null,
+  "RedundancyZones": {},
+  "Upgrade": {
+    "Status": "idle",
+    "TargetVersion": "1.7.5+ent",
+    "TargetVersionVoters": [
+      "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "e36ee410-cc3c-0a0c-c724-63817ab30303"
+    ],
+    "TargetVersionNonVoters": null,
+    "TargetVersionReadReplicas": null,
+    "OtherVersionVoters": null,
+    "OtherVersionNonVoters": null,
+    "OtherVersionReadReplicas": null,
+    "RedundancyZones": {}
+  },
+  "OptimisticFailureTolerance": 0
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/index.mdx b/content/nomad/v1.8.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.8.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..7080d4828e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,261 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Active Public Keys
+
+This endpoint retrieves a list of active public keys used to sign [workload
+identities][wi]. The response is in the [JWKS][rfc7517] format as is commonly
+used by JWT auth methods.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/.well-known/jwks.json`    | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `none`       |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/jwks.json'
+```
+
+### Sample Response
+
+```json
+{
+  "keys": [
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "15a95f48-001a-8be5-5da9-d94901d022c9",
+      "alg": "RS256",
+      "n": "6sImUQR6A...FB7bKn02dKw",
+      "e": "AQAB"
+    },
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "b7f6a3a7-14f9-4ac5-f713-32c9bce1fa93",
+      "alg": "RS256",
+      "n": "zEdiUB3DFuM...ii3kQvOf_eDApBDWJhfQw",
+      "e": "AQAB"
+    }
+  ]
+}
+```
+
+## OIDC Discovery
+
+This endpoint retrieves [OIDC configuration metadata][oidc-disco] for using
+[workload identities][wi] with third party services. Nomad will act as an
+identity provider (IDP) to allow third parties to authenticate workload
+identity JWTs based on the OIDC configurationa and JWKS.
+
+Most third parties will require this endpoint be accessible through a
+publically resolvable domain name and HTTPS signed by a trusted certificate
+authority.
+
+You must set the [`oidc_issuer`][oidc_issuer] Server agent configuration
+parameter before this endpoint is enabled. In most situations you will also
+need to run a proxy or load balancer for in front of this endpoint to serve the
+contents with HTTPS using a trusted certificate.
+
+| Method | Path                                | Produces           |
+|--------|-------------------------------------|--------------------|
+| `GET`  | `/.well-known/openid-configuration` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `none` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/openid-configuration'
+```
+
+### Sample Response
+
+```json
+{
+  "id_token_signing_alg_values_supported": [
+    "RS256",
+    "EdDSA"
+  ],
+  "issuer": "http://example.com",
+  "jwks_uri": "http://example.com/.well-known/jwks.json",
+  "response_types_supported": [
+    "code"
+  ],
+  "subject_types_supported": [
+    "public"
+  ]
+}
+```
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[oidc-disco]: https://openid.net/specs/openid-connect-discovery-1_0.html
+[oidc_issuer]: /nomad/docs/configuration/server#oidc_issuer
+[required ACLs]: /nomad/api-docs#acls
+[rfc7517]: https://datatracker.ietf.org/doc/html/rfc7517
+[wi]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/license.mdx b/content/nomad/v1.8.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.8.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..fb77f6d8e6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,229 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api /v1/operator/raft/configuration
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+</Tab>
+</Tabs>
+
+### Sample Response
+
+```json
+{
+    "Index": 0,
+    "Servers": [
+        {
+            "Address": "10.1.0.10:4647",
+            "ID": "c13f9998-a0f3-d765-0b52-55a0b3ce5f88",
+            "Leader": false,
+            "Node": "node1.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.20:4647",
+            "ID": "d7927f2b-067f-45a4-6266-af8bb84de082",
+            "Leader": true,
+            "Node": "node2.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.30:4647",
+            "ID": "00d56ef8-938e-abc3-6f8a-f8ac80a80fb9",
+            "Leader": false,
+            "Node": "node3.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        }
+
+    ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. For Raft protocol v2, this is the
+    same as the `Address`. Raft protocol v3 uses GUIDs as the ID.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  server to remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the server to
+  remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+  <Note>
+
+  Either `address` or `id` must be provided, but not both.
+
+  </Note>
+
+### Sample Request
+
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X DELETE \
+   /v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    https://127.0.0.1:4646/v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+</Tabs>
+
+## Transfer Leadership to another Raft Peer
+
+This endpoint tells the current cluster leader to transfer leadership
+to the Nomad server with given address or ID in the Raft
+configuration. The return code signifies success or failure.
+
+| Method              | Path                                    | Produces           |
+| ------------------- | --------------------------------------- | ------------------ |
+| `PUT` <br /> `POST` | `/v1/operator/raft/transfer-leadership` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  target server as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the target server
+  as provided in the output of `/v1/operator/raft/configuration` API endpoint or
+  the `nomad operator raft list-peers` command.
+
+<Note>
+
+- The cluster must be running Raft protocol v3 or greater on all server members.
+
+- Either `address` or `id` must be provided, but not both.
+
+</Note>
+
+### Sample Requests
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X PUT \
+    "/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl --request PUT \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    "https://127.0.0.1:4646/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+</Tabs>
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.8.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.8.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.8.x/content/api-docs/operator/upgrade-check.mdx b/content/nomad/v1.8.x/content/api-docs/operator/upgrade-check.mdx
new file mode 100644
index 0000000000..8659c6b135
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/operator/upgrade-check.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: Upgrade Check - Operator - HTTP API
+description: |-
+  The /operator/upgrade-check endpoints provide tools for verifying the state
+  of the cluster prior to upgrades.
+---
+
+# Upgrade Check Operator HTTP API
+
+The `/operator/upgrade-check` endpoints provide some predefined verifications
+that can be useful prior to upgrades and changes to Nomad configuration.
+
+<Note>
+
+These endpoints are meant to target specific releases of Nomad and may be
+removed or modified without notice.
+
+</Note>
+
+## Vault Workload Identity
+
+This endpoint retrieves jobs, nodes, and Vault ACL tokens that may be affected
+when migrating a Nomad cluster to use [workload identities for
+Vault][nomad_acl_vault_wid].
+
+| Method | Path                                                 | Produces           |
+| ------ | ---------------------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/upgrade-check/vault-workload-identity` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/operator/upgrade-check/vault-workload-identity
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 20,
+  "JobsWithoutVaultIdentity": [
+    {
+      "CreateIndex": 11,
+      "Datacenters": [
+        "*"
+      ],
+      "ID": "example",
+      "JobModifyIndex": 11,
+      "JobSummary": null,
+      "ModifyIndex": 19,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "default",
+      "ParameterizedJob": false,
+      "ParentID": "",
+      "Periodic": false,
+      "Priority": 50,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1704995322434188000,
+      "Type": "service"
+    }
+  ],
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "OutdatedNodes": [
+    {
+      "Address": "192.168.0.186",
+      "CreateIndex": 8,
+      "Datacenter": "dc1",
+      "Drain": false,
+      "Drivers": {
+        "qemu": {
+          "Attributes": {
+            "driver.qemu": "true",
+            "driver.qemu.version": "8.1.1"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.993541-05:00"
+        },
+        "exec": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "exec driver unsupported on client OS",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.958495-05:00"
+        },
+        "raw_exec": {
+          "Attributes": {
+            "driver.raw_exec": "true"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.958539-05:00"
+        },
+        "java": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.97141-05:00"
+        },
+        "docker": {
+          "Attributes": {
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.runtimes": "io.containerd.runc.v2,runc",
+            "driver.docker.os_type": "linux",
+            "driver.docker": "true",
+            "driver.docker.version": "24.0.7"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.989993-05:00"
+        }
+      },
+      "HostVolumes": null,
+      "ID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "LastDrain": null,
+      "ModifyIndex": 10,
+      "Name": "client-1",
+      "NodeClass": "",
+      "NodePool": "default",
+      "SchedulingEligibility": "eligible",
+      "Status": "ready",
+      "StatusDescription": "",
+      "Version": "1.6.4"
+    }
+  ],
+  "VaultTokens": [
+    {
+      "Accessor": "czh9MPcRXzAhxBL9XKyb3Kh1",
+      "AllocID": "f00893d4-d9ef-4937-6a7a-ab495b68a971",
+      "CreateIndex": 14,
+      "CreationTTL": 60,
+      "NodeID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "Task": "redis"
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `JobsWithoutVaultIdentity` `(array<Job>)` - The list of jobs that have a
+  [`vault`][] block but do not have an [`identity`][] for Vault
+  authentication. These jobs can fail if they are not redeployed with an
+  identity for Vault before the configuration for Nomad servers are updated and
+  their access to Vault is removed.
+
+- `OutdatedNodes` `(array<Node>)` - The list of nodes running a version of
+  Nomad that does not support workload identity authentication for Vault.
+  Allocations placed in these nodes will use the deprecated legacy flow to
+  retrieve Vault tokens. If the Nomad servers configuration is update to remove
+  their access to Vault before these nodes are upgraded, these allocations will
+  fail. Allocations that use workload identity for Vault will not be able to be
+  placed in these nodes until they are upgraded.
+
+- `VaultTokens` `(array<VaultAccessor>)` - The list of Vault ACL tokens created
+  by Nomad servers using the deprecated legacy flow. They will continue to work
+  even after the migration to the workload identities, but they may not be
+  automatically revoked by Nomad and will only expire once their TTL reaches
+  zero.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+[`identity`]: /nomad/docs/job-specification/identity
+[`vault`]: /nomad/docs/job-specification/vault
+[nomad_acl_vault_wid]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.8.x/content/api-docs/plugins.mdx b/content/nomad/v1.8.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/quotas.mdx b/content/nomad/v1.8.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..112d80d7e9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/quotas.mdx
@@ -0,0 +1,354 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+    "Limits": [
+      {
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "DiskMB": 0,
+          "MemoryMB": 2000,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ]
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 56,
+    "Name": "shared-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 8,
+  "Description": "Limit the shared default namespace",
+  "Hash": "SgDCH7L5ZDqNSi2NmJlqdvczt/Q6mjyVwVJC0XjWglQ=",
+  "Limits": [
+    {
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "DiskMB": 0,
+        "MemoryMB": 2000,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 56,
+  "Name": "shared-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "shared-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 1000,
+        "Networks": [
+          {
+            "Mbits": 50
+          }
+        ]
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "MemoryMB": 256,
+          "DiskMB": 0,
+          "Networks": null
+        },
+        "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+      }
+    },
+    "Name": "default",
+    "CreateIndex": 8,
+    "ModifyIndex": 56
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "MemoryMB": 256,
+        "DiskMB": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ]
+      },
+      "Hash": "NLOoV2WBU8ieJIrYXXx8NRb5C2xU61pVVWRDLEIMxlU="
+    }
+  },
+  "Name": "default",
+  "CreateIndex": 8,
+  "ModifyIndex": 56
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/recommendations.mdx b/content/nomad/v1.8.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/regions.mdx b/content/nomad/v1.8.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.8.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/search.mdx b/content/nomad/v1.8.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..247ed39453
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/search.mdx
@@ -0,0 +1,638 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.8.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.8.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/services.mdx b/content/nomad/v1.8.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/api-docs/status.mdx b/content/nomad/v1.8.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/system.mdx b/content/nomad/v1.8.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/task-api.mdx b/content/nomad/v1.8.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..8f2b43ca01
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/task-api.mdx
@@ -0,0 +1,109 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+## Limitations
+
+- Using the Task API Unix Domain Socket on Windows [requires][windows] Windows
+build 17063 or later.
+
+[acl]: /nomad/docs/concepts/acl
+[acl-tokens]: /nomad/docs/concepts/acl#token
+[alloc-exec]: /nomad/docs/commands/alloc/exec
+[anon]: /nomad/tutorials/access-control/access-control#acl-policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[dnm]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.8.x/content/api-docs/ui.mdx b/content/nomad/v1.8.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.8.x/content/api-docs/validate.mdx b/content/nomad/v1.8.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.8.x/content/api-docs/variables/index.mdx b/content/nomad/v1.8.x/content/api-docs/variables/index.mdx
new file mode 100644
index 0000000000..8f1e8bcb21
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/variables/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: |-
+  The /var endpoints are used to query for and interact with variables and variable
+  locking.
+---
+
+# Vars HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables, and set up locks and leases over them.
+
+See the [Variables][] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`][] commands.
+
+Please choose a sub-section in the navigation for more information
+
+[`nomad var`]: /nomad/docs/commands/var
+[Variables]: /nomad/docs/concepts/variables
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/api-docs/variables/locks.mdx b/content/nomad/v1.8.x/content/api-docs/variables/locks.mdx
new file mode 100644
index 0000000000..bbb79d7583
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/variables/locks.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: Variable Locks - HTTP API
+description: The /var endpoints are used to query for and interact with variables and locks.
+---
+
+# Locks HTTP API
+
+The `/var` endpoint is used to hold, renew and release a lock over a variable.
+
+## Lock Variable
+
+The endpoint to create a variable can also be used to hold a lock and interact with
+it through the use of a parameter defining the operation to be performed.
+
+| Method | Path                                 | Produces           |
+|--------|--------------------------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path?<lock-operation>` | `application/json` |
+
+### Parameters
+
+The lock operation parameter can be:
+
+- `lock-acquire`: When used, the call will introduce a lock over the variable if 
+it exists, or create a new one if it doesn't. The lock ID will be returned in the 
+response and it must be provided to perform any other operation over the lock. 
+The variable items can be updated at any time using the lock ID, but the lock
+parameters are unmmutable, attempting to modify them while a lock is present will
+generate an error. 
+
+In the case of attempting to acquire a variable that is already locked, a conflict
+response will be returned. 
+
+The lock-acquire operation will override the variable items if new values are 
+present.
+
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-acquire
+```
+
+#### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "1m"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the created or updated variable including the lock 
+parameters and ID, along with metadata created by the server:
+
+```json
+{
+  "CreateIndex": 15,
+  "CreateTime": 1694552155379696000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 16,
+  "ModifyTime": 1694552206138804000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-renew`: A valid call to lock renew needs to be placed before the lock's
+TTL is up in order to mantain the variable locked. A valid call must include the
+lock ID as part of the request body. If the lock TTL is up without a renewal or
+release calls, the variable will remain unlockable for at least the lock delay. 
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-renew
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body only returns metadata created by the server and the lock
+parameters:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 43,
+  "ModifyTime": 1694556175092779000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-release`: A call to the endpoint with the `lock-release` operation will
+immediately remove the lock over the variable, making it modifiable without 
+restrictions again. 
+
+The lock-release operation will not override the variable items, if the request
+body contains any item, it will generate a bad request response.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-release
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the released variable along with metadata
+created by the server:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "ModifyIndex": 66,
+  "ModifyTime": 1694556922600469000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+### Sample Response for Conflict
+
+In the case of an attempt to lock, renew or modify a locked variable
+without the correct ID, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "CreateIndex": 0,
+  "CreateTime": 0,
+  "Items": null,
+  "Lock": null,
+  "ModifyIndex": 0,
+  "ModifyTime": 0,
+  "Namespace": "default",
+  "Path": "example/first"
+}
+```
+
+## Restrictions
+
+When creating a new variable using the lock-acquire operation, all the known 
+[restrictions][] regarding the path and size of the content apply, but unlike 
+regular variables, locked variables can be created with or without any items.
+
+The lock TTL and Delay must be values between 10 seconds and 24 hours.
+
+[Variables]: /nomad/docs/concepts/variables
+[restrictions]: /nomad/api-docs/variables/variables#restrictions
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.8.x/content/api-docs/variables/variables.mdx b/content/nomad/v1.8.x/content/api-docs/variables/variables.mdx
new file mode 100644
index 0000000000..f53b0c7be4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/variables/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables][] documentation for information how these capabilities are
+used. 
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+- `lock-operation` `(string: <unset>)` - This endpoint can also be used to create 
+and hold a lock over a variable, refer to the [locks section][] for more
+information.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+[Variables]: /nomad/docs/concepts/variables
+[locks section]:/nomad/api-docs/variables/locks
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.8.x/content/api-docs/volumes.mdx b/content/nomad/v1.8.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..9b56c16e88
--- /dev/null
+++ b/content/nomad/v1.8.x/content/api-docs/volumes.mdx
@@ -0,0 +1,789 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below).
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_VOLUME`
+capability support this endpoint.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
+[Volume Expansion]: /nomad/docs/other-specifications/volume#volume-expansion
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/create.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..2d3d8cccc1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/create.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method create'
+description: The auth-method create command is used to create new ACL Auth Methods.
+---
+
+# Command: acl auth-method create
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..45303a5658
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method delete'
+description: The auth-method delete command is used to delete existing ACL Auth Methods.
+---
+
+# Command: acl auth-method delete
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/info.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..a6d13c61b8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/info.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method info'
+description: |
+  The auth-method info command is used to fetch information about an existing
+  ACL Auth Method.
+---
+
+# Command: acl auth-method info
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/list.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..0cb15df8e6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method list'
+description: The auth-method list command is used to list existing ACL Auth Methods.
+---
+
+# Command: acl auth-method list
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/update.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..5b0b58d0af
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/auth-method/update.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: 'Commands: acl auth-method update'
+description: The auth-method update command is used to update existing ACL Auth Methods.
+---
+
+# Command: acl auth-method update
+
+The `acl auth-method update` command is used to update existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -token-name-format '${auth_method_name}-${value.user}' -config @config.json example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = global
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_name}-${value.user}
+Default             = false
+Create Index        = 14
+Modify Index        = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/create.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..e15d870756
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule create'
+description: The binding-rule create command is used to create new ACL Binding Rules.
+---
+
+# Command: acl binding-rule create
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..0bdafd9689
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule delete'
+description: The binding-rule delete command is used to delete existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule delete
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/info.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..38dcfb2eeb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule info'
+description: |
+  The binding-rule info command is used to fetch information about an existing
+  ACL Binding Rule.
+---
+
+# Command: acl binding-rule info
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/list.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..d506f8a8d2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule list'
+description: The binding-rule list command is used to list existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule list
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/update.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..03bacdd24d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl binding-rule update'
+description: The binding-rule update command is used to update existing ACL Binding Rules.
+---
+
+# Command: acl binding-rule update
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..83f538040b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: acl bootstrap'
+description: |
+  The bootstrap command is used to create the initial ACL token.
+---
+
+# Command: acl bootstrap
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways: 
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-". 
+Please make sure you secure this token in an appropriate manner as it could be written to your terminal history.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap Options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin 
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..d079e2ca12
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: acl'
+description: |
+  The acl command is used to interact with ACL policies and tokens.
+---
+
+# Command: acl
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[authmethodcreate]: /nomad/docs/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/docs/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/docs/commands/acl/auth-method/info
+[authmethodlist]: /nomad/docs/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/docs/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/docs/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/docs/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/docs/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/docs/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/docs/commands/acl/binding-rule/update
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..af000cd896
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: acl policy apply'
+description: |
+  The policy apply command is used to create or update ACL policies.
+---
+
+# Command: acl policy apply
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..2ec7e3b8a7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: acl policy delete'
+description: |
+  The policy delete command is used to delete an existing ACL policies.
+---
+
+# Command: acl policy delete
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..f0622d92c4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: acl policy info'
+description: >
+  The policy info command is used to fetch information on an existing ACL
+  policy.
+---
+
+# Command: acl policy info
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..9e412c9f30
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: acl policy list'
+description: |
+  The policy list command is used to list available ACL policies.
+---
+
+# Command: acl policy list
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..a5a48d3da0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: acl role create'
+description: The role create command is used to create new ACL Roles.
+---
+
+# Command: acl role create
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..f4e4a93b9f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: acl role delete'
+description: The role delete command is used to delete existing ACL Roles.
+---
+
+# Command: acl role delete
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..7a2f40a8bd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: acl role info'
+description: |
+  The role info command is used to fetch information about an existing ACL
+  Role.
+---
+
+# Command: acl role info
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..6f36f8d065
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: acl role list'
+description: The role list command is used to list existing ACL Roles.
+---
+
+# Command: acl role list
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..921924e82b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: acl role update'
+description: The role update command is used to update existing ACL Roles.
+---
+
+# Command: acl role update
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..5c0c77d051
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'Commands: acl token create'
+description: |
+  The token create command is used to create new ACL tokens.
+---
+
+# Command: acl token create
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..6759a8089c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: acl token delete'
+description: |
+  The token create command is used to delete existing ACL tokens.
+---
+
+# Command: acl token delete
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..33e442126e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: acl token info'
+description: >
+  The token info command is used to fetch information about an existing ACL
+  token.
+---
+
+# Command: acl token info
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..fb8fc94ac2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: acl token list'
+description: |
+  The token list command is used to list existing ACL tokens.
+---
+
+# Command: acl token list
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..b58a7193b8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: acl token self'
+description: >
+  The token self command is used to fetch information about the currently set
+  ACL token.
+---
+
+# Command: acl token self
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.8.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..319b6b2f3e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: acl token update'
+description: |
+  The token update command is used to update existing ACL tokens.
+---
+
+# Command: acl token update
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update Options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens. If any policies are
+  specified, they completely replace the policies on the existing token.
+
+- `-role-id`: ID of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+- `-role-name`: Name of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.8.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..d7f2ddfec1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: agent-info'
+description: |
+  Display information and status of a running agent.
+---
+
+# Command: agent-info
+
+The `agent-info` command dumps metrics and status information of a running
+agent. The information displayed pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Agent Info Options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, information from different subsystems is
+returned. These subsystems are described below:
+
+- client - Status of the local Nomad client
+- nomad - Status of the local Nomad server
+- serf - Gossip protocol metrics and information
+- raft - Status information about the Raft consensus protocol
+- runtime - Various metrics from the runtime environment
+
+## Examples
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/agent.mdx b/content/nomad/v1.8.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..00685c4e91
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/agent.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: 'Commands: agent'
+description: |
+  The agent command is the main entrypoint to running a Nomad client or server.
+---
+
+# Command: agent
+
+The agent command is the heart of Nomad: it runs the agent that handles client
+or server functionality, including exposing interfaces for client consumption
+and running jobs.
+
+Due to the power and flexibility of this command, the Nomad agent is documented
+in its own section. See the [Nomad Agent] guide and the [Configuration]
+documentation section for more information on how to use this command and the
+options it has.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+## Command-line Options
+
+A subset of the available Nomad agent configuration can optionally be passed in
+via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir][] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled][] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token][] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr][] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect][] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address][] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth][] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise][] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file][] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file][] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise][]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join][] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name][]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name][] config option.
+
+- `-consul-client-failures-before-critical=<num>`: Equivalent to the
+  [client_failures_before_critical][] config option.
+
+- `-consul-client-failures-before-warning=<num>`: Equivalent to the
+  [client_failures_before_warning][] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file][] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name][]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name][] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name][] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name][] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join][] config
+  option.
+
+- `-consul-server-failures-before-critical=<num>`: Equivalent to the
+  [server_failures_before_critical][] config option.
+
+- `-consul-server-failures-before-warning=<num>`: Equivalent to the
+  [server_failures_before_warning][] config option.
+
+- `-consul-ssl`: Equivalent to the [ssl][] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token][] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl][] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir][] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter][] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. It may be
+  used with `-dev-consul` to configure default workload identities for Consul.
+  This mode is supported only on Linux as root.
+
+- `-dev-consul`: Starts the agent in development mode with a default Consul
+  configuration for Nomad workload identity. It may be used with `-dev-connect`
+  to configure the agent for Consul Service Mesh.
+
+- `-dev-vault`: Starts the agent in development mode with a default Vault
+  configuration for Nomad workload identity.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview][] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level][] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location][] config option.
+
+- `-log-json`: Equivalent to the [log_json][] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta][] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface][] config option.
+
+- `-node=<name>`: Equivalent to the [name][] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class][]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool][]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir][] config option.
+
+- `-region=<region>`: Equivalent to the [region][] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave][] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval][] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max][] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers][] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir][] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_failures_before_critical]: /nomad/docs/configuration/consul#client_failures_before_critical
+[client_failures_before_warning]: /nomad/docs/configuration/consul#client_failures_before_warning
+[server_failures_before_critical]: /nomad/docs/configuration/consul#server_failures_before_critical
+[server_failures_before_warning]: /nomad/docs/configuration/consul#server_failures_before_warning
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[configuration]: /nomad/docs/configuration
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad agent]: /nomad/docs/operations/nomad-agent
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/checks.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..fc1b02c1e2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'Commands: alloc checks'
+description: |
+  Outputs service health check status information.
+---
+
+# Command: alloc checks
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability 
+for the allocation's namespace. The 'list-jobs' capability is required to run the 
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Checks Options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..8ea9ae7216
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'Commands: alloc exec'
+description: |
+  Runs a command in a container.
+---
+
+# Command: alloc exec
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Exec Options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..2fdb4e42c9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Commands: alloc fs'
+description: |
+  Introspect an allocation directory on a Nomad client
+---
+
+# Command: alloc fs
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fs Options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..b673a63f04
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: alloc'
+description: |
+  The alloc command is used to interact with allocations.
+---
+
+# Command: alloc
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/docs/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..ddf16f7b7a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'Commands: alloc logs'
+description: |
+  Stream the logs of a task.
+---
+
+# Command: alloc logs
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Logs Options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/pause.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/pause.mdx
new file mode 100644
index 0000000000..d6bcaa4099
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/pause.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'Commands: alloc pause'
+description: |
+  Override the schedule for tasks using time based execution.
+---
+
+# Command: alloc pause
+
+<EnterpriseAlert />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes. 
+
+Override the schedule for tasks using time based execution.
+
+## Usage
+
+```plaintext
+nomad alloc pause [options] <allocation> <command>
+```
+
+The `alloc pause` command allows a user to override the schedule for tasks
+that use time based execution. A user may override a task's
+[`schedule`][schedule] and force it to run or stop. The `schedule` will be
+ignored until a user resets the override.
+
+When ACLs are enabled, this command requires the `job-submit` capability for
+the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-state`: Override the current scheduled task state to be the specified state
+  or reset to the scheduled state. Must be one of `pause`, `run`, or
+  `scheduled`. When set to `pause` the task is halted. When set to `run` the
+  task is started. When set to `scheduled` the task respects its
+  [`schedule`][schedule].
+
+- `-status`: Get the current time based task execution state.
+
+- `-task`: Override the schedule of the specified task. May also be specified
+  as a positional argument.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+The following command stops the `schedtask` task of the allocation `4d37a9d1`
+overriding the task's [`schedule`][schedule] block:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command runs the task overriding the tasks current state or
+schedule:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command returns the task to its [`schedule`][schedule]:
+
+```shell-session
+$ nomad alloc pause -state=scheduled 4d37a9d1 schedtask
+```
+
+[schedule]: /nomad/docs/job-specification/schedule
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..32f14b6e83
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: alloc restart'
+description: |
+  Restart a running allocation or task
+---
+
+# Command: alloc restart
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..d23924a6e6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: alloc signal'
+description: |
+  Signal a running allocation or task
+---
+
+# Command: alloc signal
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command 
+argument. If task name is given with both an argument and the `-task` option, 
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Signal Options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..966bbf9731
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,182 @@
+---
+layout: docs
+page_title: 'Commands: alloc status'
+description: |
+  Display status and metadata about existing allocations and their tasks.
+---
+
+# Command: alloc status
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Alloc Status Options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount Options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.8.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..718d962d57
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: alloc stop'
+description: |
+  Stop and reschedule a running allocation
+---
+
+# Command: alloc stop
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped and rescheduled. Otherwise, a list of
+matching allocs and information will be displayed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.8.x/content/docs/commands/config/index.mdx b/content/nomad/v1.8.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..a4e30b15d5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'Commands: config'
+description: |
+  The config command interacting with configurations.
+---
+
+# Command: config
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.8.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.8.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..b270541dc7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'Commands: config validate'
+description: |
+  The config validate command is used to validate Nomad configuration files.
+---
+
+# Command: config validate
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..9c72af2dce
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: deployment fail'
+description: |
+  The deployment fail command is used to manually fail a deployment.
+---
+
+# Command: deployment fail
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Fail Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..e46e78073b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: deployment'
+description: |
+  The deployment command is used to interact with deployments.
+---
+
+# Command: deployment
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..b6e2d35e63
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: deployment list'
+description: |
+  The deployment list command is used to list deployments.
+---
+
+# Command: deployment list
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..b4070a097c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: deployment pause'
+description: >
+  The deployment pause command is used to pause a deployment and disallow new
+  placements.
+---
+
+# Command: deployment pause
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Pause Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..d40b151754
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'Commands: deployment promote'
+description: |
+  The deployment promote command is used to promote canaries in a deployment.
+---
+
+# Command: deployment promote
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..3369798607
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: deployment resume'
+description: |
+  The deployment resume command is used to resume a paused deployment.
+---
+
+# Command: deployment resume
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Resume Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..86542733e2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: deployment status'
+description: |
+  The deployment status command is used to display the status of a deployment.
+---
+
+# Command: deployment status
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.8.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..9214e1adf4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Commands: deployment unblock'
+description: |
+  The deployment unblock command is used to manually unblock a deployment.
+---
+
+# Command: deployment unblock
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Unblock Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.8.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..23995ad28e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: eval delete'
+description: |
+  The eval delete command is used to delete evaluations.
+---
+
+# Command: eval delete
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Delete Options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfully deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfully deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfully deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.8.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.8.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..3c2451cf87
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: eval'
+description: |
+  The eval command is used to interact with evals.
+---
+
+# Command: eval
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.8.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.8.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..1081d2f529
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: eval list'
+description: |
+  The eval list command is used to list evaluations.
+---
+
+# Command: eval list
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.8.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..663c3a562c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: eval status'
+description: >
+  The eval status command is used to see the status and potential failed
+  allocations of an evaluation.
+---
+
+# Command: eval status
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Status Options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/fmt.mdx b/content/nomad/v1.8.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..d40d17c95a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: fmt'
+description: |
+  Rewrite Nomad config and job files to canonical format
+---
+
+# Command: fmt
+
+The `fmt` commands check the syntax and rewrites Nomad configuration and jobspec
+files to canonical format. It can be used to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [flags] paths ...
+```
+
+Formats Nomad agent configuration and job file to a canonical format. If a path
+is a directory, it will recursively format all files with .nomad and .hcl
+extensions in the directory.
+
+If you provide a single dash (-) as argument, fmt will read from standard input
+(STDIN) and output the processed output to standard output (STDOUT).
+
+Note that, this command will check the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 jobspec will result in errors.
+
+## Format Options:
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/index.mdx b/content/nomad/v1.8.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..0617239944
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/index.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: Commands (CLI)
+description: >
+  Nomad can be controlled via a command-line interface. This page documents all
+  the commands Nomad accepts.
+---
+
+# Nomad Commands (CLI)
+
+Nomad is controlled via a very easy to use command-line interface (CLI).
+Nomad is only a single command-line application: `nomad`, which
+takes a subcommand such as "agent" or "status". The complete list of
+subcommands is in the navigation to the left.
+
+The Nomad CLI is a well-behaved command line application. In erroneous cases,
+a non-zero exit status will be returned. It also responds to `-h` and `--help`
+as you would most likely expect.
+
+To view a list of the available commands at any time, just run Nomad
+with no arguments. To get help for any specific subcommand, run the subcommand
+with the `-h` argument.
+
+Each command has been conveniently documented on this website. Links to each
+command can be found on the left.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete. Autocomplete can be installed or
+uninstalled by running the following on bash, zsh or fish shells:
+
+```shell-session
+$ nomad -autocomplete-install
+$ nomad -autocomplete-uninstall
+```
+
+## Command Contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise.
+
+For example, the `nomad job run` command is used to run a new job, the `nomad status` command queries information about existing jobs, etc. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote Usage
+
+The Nomad CLI may be used to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The provided address must be reachable from your local machine. There are a
+variety of ways to accomplish this (VPN, SSH Tunnel, etc). If the port is
+exposed to the public internet it is highly recommended to configure TLS.
+
+### Environment Variables
+
+Nomad can use environment variables to configure command-line tool options.
+These environment variables can be overridden as needed using individual
+flags.
+
+#### Connection Environment Variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### ACL Environment Variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI Environment Variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### mTLS Environment Variables
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise Licensing Environment Variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/action.mdx b/content/nomad/v1.8.x/content/docs/commands/job/action.mdx
new file mode 100644
index 0000000000..1d16217c08
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/action.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'Commands: job action'
+description: |
+  The job action command is used to execute predefined actions from a job
+  specification in a running task context
+---
+
+# Command: job action
+
+**Alias: `nomad action`**
+
+The `job action` command allows operators to execute predefined actions declared
+in Nomad job specifications. These actions can be defined at task level and are
+intended for specific operational tasks, such as clearing a cache, or migrating
+a database.
+
+An action may self-terminate upon completion (for example, echoing a string),
+or run for an indeterminate amount of time (for example, watching a blocking
+query). In the latter case, an action can be terminated via escape character
+(such as cmd+c / ctrl+c)
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `alloc-exec`, `read-job`, and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Usage
+
+```plaintext
+nomad job action [options] <action>
+```
+
+The `job action` command requires an action name and accepts two ways of
+specifying where it should run:
+- by passing the job name and known allocation ID along with the name of the action
+- by passing the job, task group, and task name along with the name of the action
+(when the allocation ID is not known). A random allocation will be selected if
+multiple are available.
+
+The action name provided must be defined within a task in the [job specification]
+provided. With sufficient privileges, an execution context will be opened and
+the defined action command will be run. No further input is possible, save for
+the escape character to terminate execution, so interactive commands are not
+supported.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Action Options
+
+- `-job`: (Required) Specifies the job containing the predefined action.
+
+- `-alloc`: Specifies the allocation within which the action is to be executed.
+  If omitted, `-group` and `-task` must be provided, and a random
+  allocation for the group will be selected.
+
+- `-task`: Specifies the task within the job where the action is defined. This
+  is required either if `-alloc` provided and your group has multiple tasks,
+  or if you specify a `-group`.
+
+- `-group`: Specifies the task group within the job. If present, a random
+  allocation is selected. If omitted, `-alloc` must be provided.
+
+- `-i`: Pass stdin to the action, defaults to `true`. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to `true` if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty,
+  defaults to '~'. The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot (`.`) closes the connection.
+  Setting the character to `none` disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+Execute an action within a specific task in a job:
+
+```shell-session
+$ nomad action \
+  -group=my-group \
+  -task=my-task \
+  -job=my-job \
+  weather
+
+Toronto: ☁️   +3°C
+```
+
+Execute an action within a specific allocation:
+
+```shell-session
+$ nomad action \
+  -alloc=f200a789-6da4-504c-d131-6181764f101e \
+  -job=actions-demo \
+  echo-time
+
+Running for 0 seconds
+Running for 1 seconds
+Running for 2 seconds
+Running for 3 seconds
+```
+
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.8.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..72f2e9a443
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: job allocs'
+description: |
+  The allocs command is used to list allocations for a job.
+---
+
+# Command: job allocs
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Allocs Options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.8.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..ccfcf28be1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: job deployments'
+description: |
+  The deployments command is used to list deployments for a job.
+---
+
+# Command: job deployments
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deployment Options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.8.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..235cc952c3
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: 'Commands: job dispatch'
+description: |
+  The dispatch command is used to create an instance of a parameterized job.
+---
+
+# Command: job dispatch
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Dispatch Options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.8.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..9d3a2cf8ee
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'Commands: job eval'
+description: |
+  The job eval command is used to force an evaluation of a job
+---
+
+# Command: job eval
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Eval Options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/history.mdx b/content/nomad/v1.8.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..9544f64140
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: job history'
+description: |
+  The history command is used to display all tracked versions of a job.
+---
+
+# Command: job history
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## History Options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/index.mdx b/content/nomad/v1.8.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..6a592688e5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: job'
+description: |
+  The job command is used to interact with jobs.
+---
+
+# Command: job
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job inspect`][inspect] - Inspect the contents of a submitted job.
+- [`job promote`][promote] - Promote a job's canaries
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job status`][status] - Display status information about a job
+
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[inspect]: /nomad/docs/commands/job/inspect
+[promote]: /nomad/docs/commands/job/promote "Promote a job's canaries"
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/init.mdx b/content/nomad/v1.8.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..1c5a7d5ecc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: job init'
+description: |
+  The job init command is used to generate a skeleton jobspec template.
+---
+
+# Command: job init
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init Options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.8.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..90a8535b27
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'Commands: job inspect'
+description: |
+  The job inspect command is used to inspect a submitted job.
+---
+
+# Command: job inspect
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format. Cannot be used with `-hcl`.
+- `-hcl`: Output the original HCL submitted with the job. Cannot be used with
+  `-json`.
+- `-with-vars`: Include the original HCL2 variables submitted with the job. Can
+    only be used with `-hcl`.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.8.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..8aca82eb80
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: job periodic force'
+description: >
+  The job periodic force command is used to force the evaluation of a periodic
+  job.
+---
+
+# Command: job periodic force
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.8.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..7d4b12fba0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,264 @@
+---
+layout: docs
+page_title: 'Commands: job plan'
+description: |
+  The job plan command is used to dry-run a job update to determine its effects.
+---
+
+# Command: job plan
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Plan Options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`. HCLv1 is deprecated and will be removed in
+  Nomad 1.9.0.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.8.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..28dab1fc76
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'Commands: job promote'
+description: |
+  The promote command is used to promote a job's canaries.
+---
+
+# Command: job promote
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Promote Options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/restart.mdx b/content/nomad/v1.8.x/content/docs/commands/job/restart.mdx
new file mode 100644
index 0000000000..6f87e40a82
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'Commands: job restart'
+description: |
+  The job restart command is used to restart allocations for a job.
+---
+
+# Command: job restart
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+Allocations can be restarted in-place or rescheduled. When restarting
+in-place the command may target specific tasks in the allocations, restart
+only tasks that are currently running, or restart all tasks, even the ones
+that have already run. Allocations can also be targeted by groups and tasks.
+When both groups and tasks are defined only the tasks for the allocations of
+those groups are restarted.
+
+When rescheduling, the current allocations are stopped triggering the Nomad
+scheduler to create replacement allocations that may be placed in different
+clients. The command waits until the new allocations have client status `ready`
+before proceeding with the remaining batches. Services health checks are not
+taken into account.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Restart Options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, allocations are stopped and rescheduled instead of
+  restarted in-place. Since the group is not modified the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such
+  as [`max_parallel`][], are not taken into account. This option cannot be used
+  with `-task`. Only jobs of type `batch`, `service`, and `system` can be
+  rescheduled.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.8.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..f0bd4efa60
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: 'Commands: job revert'
+description: |
+  The revert command is used to revert to a prior version of the job.
+---
+
+# Command: job revert
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```plaintext
+nomad job revert [options] <job> <version>
+```
+
+The `job revert` command requires two inputs, the job ID and the version of that
+job to revert to.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Revert Options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/run.mdx b/content/nomad/v1.8.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..48e80466ef
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,250 @@
+---
+layout: docs
+page_title: 'Commands: job run'
+description: |
+  The job run command is used to run a new job.
+---
+
+# Command: job run
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Run Options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`. HCLv1 is deprecated and will be removed in
+  Nomad 1.9.0.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.8.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..0647d7d209
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: 'Commands: job scale'
+description: |
+  The job scale command is used to change the count of a Nomad job group.
+---
+
+# Command: job scale
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scale Options
+
+- `-check-index`: If set, the job is only scaled if the passed job modify index
+  matches the server side version. Ignored if value of zero is passed. If a
+  non-zero value is passed, it ensures that the job is being updated from a
+  known state.
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.8.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..dd639766f6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Commands: job scaling-events'
+description: |
+  The job scaling-events command details scaling events for a given job.
+---
+
+# Command: job scaling-events
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Scaling-Events Options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/status.mdx b/content/nomad/v1.8.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..7706775ca0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Commands: job status'
+description: |
+  Display information and status of jobs.
+---
+
+# Command: job status
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. Alloc status also shows allocation 
+modification time in addition to create time. When the `-verbose` flag is not set,
+allocation creation and modify times are shown in a shortened relative time format
+like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-json`: Output the job status in JSON format.
+
+- `-t`: Format and display the job status using a Go template.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.8.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..ad19f5afac
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: job stop'
+description: |
+  The job stop command is used to stop a running job.
+---
+
+# Command: job stop
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Stop Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.8.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.8.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..5e96521103
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: 'Commands: job validate'
+description: >
+  The job validate command is used to check a job specification for syntax
+  errors and validation problems.
+---
+
+# Command: job validate
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Validate Options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl1`: If set, HCL1 parser is used for parsing the job spec. Takes
+  precedence over `-hcl2-strict`. HCLv1 is deprecated and will be removed in
+  Nomad 1.9.0.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true, but ignored if `-hcl1` is defined.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.8.x/content/docs/commands/license/get.mdx b/content/nomad/v1.8.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..e56b0a4aeb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: license get'
+description: |
+  The license get command is used to get the current license.
+---
+
+# Command: license get
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/license/index.mdx b/content/nomad/v1.8.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..a248a76d37
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: license'
+description: |
+  The license command is used to interact with an enterprise license.
+---
+
+# Command: license
+
+~> License commands are only available with Nomad Enterprise.
+
+The `license` commands can be used to retrieve license information from a server,
+or inspect and validate a license.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/docs/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.8.x/content/docs/commands/license/inspect.mdx b/content/nomad/v1.8.x/content/docs/commands/license/inspect.mdx
new file mode 100644
index 0000000000..d1689b5122
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/license/inspect.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: license inspect'
+description: |
+  The license inspect command is used to inspect and validate an enterprise license.
+---
+
+# Command: license inspect
+
+<EnterpriseAlert>
+  This command is only present in Nomad Enterprise.
+</EnterpriseAlert>
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/login.mdx b/content/nomad/v1.8.x/content/docs/commands/login.mdx
new file mode 100644
index 0000000000..3969a49b2d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/login.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: login'
+description: |
+  Login to Nomad using an authentication method
+---
+
+# Command: login
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Login Options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+
+$ export NOMAD_TOKEN=a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+$ nomad ...
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/monitor.mdx b/content/nomad/v1.8.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..445dab5007
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Commands: monitor'
+description: |
+  Stream the logs of a running nomad agent.
+---
+
+# Command: monitor
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor Options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..d3f37d1462
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Commands: namespace apply'
+description: |
+  The namespace apply command is used create or update a namespace.
+---
+
+# Command: namespace apply
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers   = ["docker", "exec"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..3f2b043074
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: namespace delete'
+description: |
+  The namespace delete command is used to delete a namespace.
+---
+
+# Command: namespace delete
+
+The `namespace delete` command is used delete a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs or allocations,
+existing CSI volumes or variables attached to it, or quotas associated with it.
+In federated clusters, you cannot delete a namespace that has any of the above
+in any of the federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..8e53e9085a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: namespace'
+description: |
+  The namespace command is used to interact with namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..4c1e61828b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: namespace inspect'
+description: >
+  The namespace inspect command is used to view raw information about a
+  particular namespace.
+---
+
+# Command: namespace inspect
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect Options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..3f9c543249
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Commands: namespace list'
+description: |
+  The namespace list command is used to list namespaces.
+---
+
+# Command: namespace list
+
+The `namespace list` command is used list available namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.8.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..a9f28d5369
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: namespace status'
+description: >
+  The namespace status command is used to view the status of a particular
+  namespace.
+---
+
+# Command: namespace status
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name                 = api-prod
+Description          = Prod API servers
+Quota                = prod
+EnabledDrivers       = docker,exec
+DisabledDrivers      = raw_exec
+EnabledNetworkModes  = bridge,cni/custom
+DisabledNetworkModes = host
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..c185e960a9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: node pool apply'
+description: |
+  The node pool apply command is used to create or update a node pool.
+---
+
+# Command: node pool apply
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..bc9748cc96
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool delete'
+description: |
+  The node pool delete command is used to delete a node pool.
+---
+
+# Command: node pool delete
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/index.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..f541856c4d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/index.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool'
+description: |
+  The node pool command is used to interact with node pools.
+---
+
+# Command: node pool
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+Usage: `nomad node pool <subcommand> [options]`
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/docs/commands/node-pool/apply
+[delete]: /nomad/docs/commands/node-pool/delete
+[info]: /nomad/docs/commands/node-pool/info
+[jobs]: /nomad/docs/commands/node-pool/jobs
+[list]: /nomad/docs/commands/node-pool/list
+[nodes]: /nomad/docs/commands/node-pool/nodes
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/info.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..e15231aef2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'Commands: node pool info'
+description: |
+  The node pool info command is used to fetch information about a node pool.
+---
+
+# Command: node pool info
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info Options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name        = prod
+Description = Node pool for production workloads.
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/init.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..6f76c045e6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: node pool init'
+description: |
+  Generate an example node pool specification.
+---
+
+# Command: node pool init
+
+The `node pool init` creates an example node pool specification file that can be
+used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/jobs.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..f55c9723df
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Commands: node pool jobs'
+description: |
+  The node pool jobs command is used to list jobs in node pool.
+---
+
+# Command: node pool jobs
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Jobs Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/list.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..e9f472b836
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'Commands: node pool list'
+description: |
+  The node pool list command is used to list node pools.
+---
+
+# Command: node pool list
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.8.x/content/docs/commands/node-pool/nodes.mdx b/content/nomad/v1.8.x/content/docs/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..e9ebefa252
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: node pool nodes'
+description: |
+  The node pool nodes command is used to list nodes in node pool.
+---
+
+# Command: node pool nodes
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Nodes Options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/config.mdx b/content/nomad/v1.8.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..da0fd39b5e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'Commands: node config'
+description: |
+  The node config command is used to view or modify client configuration.
+---
+
+# Command: node config
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config Options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.8.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..4d24e9e47a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'Commands: node drain'
+description: |
+  The node drain command is used to configure a node's drain strategy.
+---
+
+# Command: node drain
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain Options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.8.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..aefde653bd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: node eligibility'
+description: >
+  The node eligibility command is used to configure a node's scheduling
+  eligibility.
+---
+
+# Command: node eligibility
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility Options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/index.mdx b/content/nomad/v1.8.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..289d1a027f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: node'
+description: |
+  The node command is used to interact with nodes.
+---
+
+# Command: node
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/docs/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/meta/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..5b67230336
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: node meta apply'
+description: |
+  The node meta apply command updates node metadata.
+---
+
+# Command: node meta apply
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Apply Options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+[api]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/meta/index.mdx b/content/nomad/v1.8.x/content/docs/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..2b65048e5b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/meta/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: node meta'
+description: |
+  The node meta commands are used to read and update node metadata.
+---
+
+# Command: node meta
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+Usage: `nomad node meta <subcommand> [options]`
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/runtime/interpolation#node-attributes
+[apply]: /nomad/docs/commands/node/meta/apply
+[read]: /nomad/docs/commands/node/meta/read
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/meta/read.mdx b/content/nomad/v1.8.x/content/docs/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..e04e685313
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'Commands: node meta read'
+description: |
+  The node meta read command reads node metadata.
+---
+
+# Command: node meta read
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Node Meta Read Options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+[api]: /nomad/api-docs/client#read-node-metadata
diff --git a/content/nomad/v1.8.x/content/docs/commands/node/status.mdx b/content/nomad/v1.8.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..d6c2488c10
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: 'Commands: node status'
+description: |
+  The node status command is used to display information about nodes.
+---
+
+# Command: node status
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount Options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..e51d90d58a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: 'Commands: operator api'
+description: |
+  operator api is a utility command for accessing Nomad's HTTP API similar to
+  the popular open source program curl.
+---
+
+# Command: operator api
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Operator API Options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..e17aa2fe91
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot get-config'
+description: |
+  Display the current Autopilot configuration.
+---
+
+# Command: operator autopilot get-config
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/health.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/health.mdx
new file mode 100644
index 0000000000..ee455aa17b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/health.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot health'
+description: |
+  Display the current Autopilot internal health.
+---
+
+# Command: operator autopilot state
+
+The Autopilot operator command is used to view the current Autopilot
+state. See the [Autopilot Guide][] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot health [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Output Options
+
+- `-json`: Output the Autopilot health in unformatted JSON.
+
+The output will return like below, read about the output of the command in the [API docs][].
+
+```shell-session
+$ nomad operator autopilot health
+Healthy: true
+FailureTolerance: 0
+Leader: e349749b-3303-3ddf-959c-b5885a0e1f6e
+Voters:  
+        e349749b-3303-3ddf-959c-b5885a0e1f6e
+Servers: 
+ID                                    Name      Address         SerfStatus  Version   Leader  Voter  Healthy  LastContact  LastTerm  LastIndex  StableSince
+e349749b-3303-3ddf-959c-b5885a0e1f6e  node1     127.0.0.1:4647  alive       1.7.5     true    true   true     0s           2         14         2024-02-20 16:40:55 +0000 UTC
+```
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
+[api docs]: /nomad/api-docs/operator/autopilot#read-state
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..ce700ebb77
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'Commands: operator autopilot set-config'
+description: |
+  Modify the current Autopilot configuration.
+---
+
+# Command: operator autopilot set-config
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/client-state.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..6475fe5477
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'Commands: operator client-state'
+description: >
+  The `operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# Command: operator client-state
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..aa5b18224d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: 'Commands: operator debug'
+description: |
+  Build an archive of debug data.
+---
+
+# Command: operator debug
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Debug Options
+
+- `-duration=5m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `5m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=TRACE`: The log level to monitor. Defaults to `TRACE`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..d703f46ae8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring generate'
+description: >
+  The `operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# Command: operator gossip keyring generate
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..e30c21b5b4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring install'
+description: |
+  Install a new gossip encryption key
+---
+
+# Command: operator gossip keyring install
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..e05d940bd9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring list'
+description: |
+  List gossip keys
+---
+
+# Command: operator gossip keyring list
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..97009d769f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring remove'
+description: |
+  Remove a new gossip encryption key
+---
+
+# Command: operator gossip keyring remove
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..708b506787
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: operator gossip keyring use'
+description: |
+  Use a new gossip encryption key
+---
+
+# Command: operator gossip keyring use
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..1195fa5a67
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'Commands: operator'
+description: |
+  The operator command provides cluster-level tools for Nomad operators.
+---
+
+# Command: operator
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/docs/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/docs/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/docs/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/docs/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/docs/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/docs/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/docs/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/docs/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..e5f337b373
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Commands: operator metrics'
+description: |-
+  The `operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# Command: operator metrics
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific Options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..022a6731ac
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: operator raft info'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft info
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..5b361c73b5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator raft list-peers'
+description: |
+  Display the current Raft peer configuration.
+---
+
+# Command: operator raft list-peers
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers Options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..c57b5b075d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: operator raft logs'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft logs
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..f52f9b6788
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft remove-peer'
+description: |
+  Remove a Nomad server from the Raft configuration.
+---
+
+# Command: operator raft remove-peer
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer Options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..4768c18950
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: operator raft state'
+description: |
+  Display Raft server state.
+---
+
+# Command: operator raft state
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State Options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/raft/transfer-leadership.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/raft/transfer-leadership.mdx
new file mode 100644
index 0000000000..0520b530b9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/raft/transfer-leadership.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'Commands: operator raft transfer-leadership'
+description: |
+  Transfer leadership to a specific a Nomad server.
+---
+
+# Command: operator raft transfer-leadership
+
+Transfer leadership from the current leader to the given server member.
+
+While performing a [rolling upgrade][] of your Nomad cluster, it might be
+advisable to transfer leadership to a specific node in the cluster. For example,
+setting the leader to the first upgraded server in the cluster can prevent
+leadership churn as you upgrade the remaining server nodes.
+
+The target server's ID or address:port are required and can be obtained by
+running the [`nomad operator raft list-peers`][] command or by calling the
+[Read Raft Configuration][] API endpoint.
+
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator][] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft transfer-leadership [options]
+```
+
+<Tip title="Required Permissions">
+If ACLs are enabled, this command requires a management token.
+</Tip>
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Transfer Leadership Options
+
+- `-peer-address`: Specifies the Raft **Address** of the target server as
+  provided in the output of the [`nomad operator raft list-peers`][] command or
+  the [Read Raft Configuration] API endpoint.
+
+- `-peer-id`: Specifies the Raft **ID** of the target server as provided in the
+  output of the [`nomad operator raft list-peers`][] command or the
+  [Read Raft Configuration] API endpoint.
+
+  <Note>
+
+  Either `-peer-address` or `-peer-id` must be provided, but not both.
+
+  </Note>
+
+[`nomad operator raft list-peers`]: /nomad/docs/commands/operator/raft/list-peers 'Nomad operator raft list-peers command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[rolling upgrade]: /nomad/docs/upgrade#upgrade-process
+[Read Raft Configuration]: /nomad/api-docs/operator/raft#read-raft-configuration
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..e049b8b795
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring list'
+description: |
+  List encryption key metadata
+---
+
+# Command: operator root keyring list
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..bcf701378e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring remove'
+description: |
+  Remove an unused encryption key
+---
+
+# Command: operator root keyring remove
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..aef49c6265
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: operator root keyring rotate'
+description: |
+  Rotate encryption key
+---
+
+# Command: operator root keyring rotate
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Rotate Options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..01a5d20499
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler get-config'
+description: |
+  Display the current scheduler configuration.
+---
+
+# Command: operator scheduler get-config
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config Options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..f8d6719c45
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'Commands: operator scheduler set-config'
+description: |
+  Modify the scheduler configuration.
+---
+
+# Command: operator scheduler set-config
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config Options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..b3d7049f73
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot agent'
+description: |
+  Periodically saves snapshots of Nomad server state
+---
+
+# Command: operator snapshot agent
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+<Warning>
+
+This snapshot agent only saves a Raft snapshot. Key material for the Nomad
+keyring is stored on disk and must be saved separately. To use a snapshot saved
+by the agent to recover a cluster, you will also need to [restore the keyring][]
+onto at least one server.
+
+</Warning>
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent Options
+
+### Snapshot Options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent Options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage Options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage Options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage Options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage Options
+
+- `-google-bucket`: The bucket to use.
+
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..1170fc5c70
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot inspect'
+description: |
+  Displays information about a snapshot file stored on local disk.
+---
+
+# Command: operator snapshot inspect
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Inspect Options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..049282452f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot restore'
+description: |
+  Restore snapshot of Nomad server state
+---
+
+# Command: operator snapshot restore
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+<Warning>
+
+This command only restores the Raft snapshot, which does not include keyrings.
+
+If you are recovering a cluster, you also need to restore the keyring onto at
+least one server.  Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..d1e4a4a5e7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot save'
+description: |
+  Saves snapshot of Nomad server state
+---
+
+# Command: operator snapshot save
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command only saves a Raft snapshot. This snapshot does not include
+keyrings. You must back up keyrings separately.
+
+If you use this snapshot to recover a cluster, you also need to restore the
+keyring onto at least one server. Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot Save Options
+
+- `-stale`: The stale argument defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..e944c049b4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: operator snapshot state'
+description: |
+  Displays a JSON representation of a Raft snapshot.
+---
+
+# Command: operator snapshot state
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.8.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..4b32cbde19
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: plugin'
+description: |
+  The plugin command is used to interact with plugins.
+---
+
+# Command: plugin
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.8.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.8.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..cdd979a927
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'Commands: plugin status'
+description: |
+  Display information and status of plugins.
+---
+
+# Command: plugin status
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status Options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..1775a87963
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: quota apply'
+description: |
+  The quota apply command is used to create or update quota specifications.
+---
+
+# Command: quota apply
+
+The `quota apply` command is used to create or update quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..d7a1945d54
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: quota delete'
+description: |
+  The quota delete command is used to delete an existing quota specification.
+---
+
+# Command: quota delete
+
+The `quota delete` command is used to delete an existing quota specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..577c162878
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'Commands: quota'
+description: |
+  The quota command is used to interact with quota specifications.
+---
+
+# Command: quota
+
+The `quota` command is used to interact with quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..1984aaa386
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: quota init'
+description: |
+  Generate an example quota specification.
+---
+
+# Command: quota init
+
+The `quota init` command is used to create an example quota specification file
+that can be used as a starting point to customize further.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..aea7b9ef69
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: 'Commands: quota inspect'
+description: >
+  The quota inspect command is used to view raw information about a particular
+  quota specification.
+---
+
+# Command: quota inspect
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 11,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 1000,
+                    "Cores": 1,
+                    "Devices": null,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "MemoryMB": 1000,
+                    "MemoryMaxMB": 0,
+                    "NUMA": null,
+                    "Networks": null
+                },
+                "VariablesLimit": 0
+            }
+        ],
+        "ModifyIndex": 11,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 11,
+            "ModifyIndex": 12,
+            "Name": "default",
+            "Used": {
+                "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=": {
+                    "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 0,
+                        "Cores": 0,
+                        "Devices": null,
+                        "DiskMB": 0,
+                        "IOPS": 0,
+                        "MemoryMB": 0,
+                        "MemoryMaxMB": 0,
+                        "NUMA": null,
+                        "Networks": null
+                    },
+                    "VariablesLimit": 0
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t '{{ .Description }}' default-quota
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..466c5e3edd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: quota list'
+description: |
+  The quota list command is used to list available quota specifications.
+---
+
+# Command: quota list
+
+The `quota list` command is used to list available quota specifications.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.8.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..a353e155ab
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'Commands: quota status'
+description: >
+  The quota status command is used to view the status of a particular quota
+  specification.
+---
+
+# Command: quota status
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+~> Quota commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Inspect Options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 1000   0 / 1       0 / 1000      0 / inf           0 / inf
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota status -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota status -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..a9eb367d20
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'Commands: recommendation apply'
+description: |
+  The recommendation apply command is used to apply recommendations.
+---
+
+# Command: recommendation apply
+
+The `recommendation apply` command is used to apply recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Apply Options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.8.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..ade257d00c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: recommendation dismiss'
+description: |
+  The recommendation dismiss command is used to dismiss recommendations.
+---
+
+# Command: recommendation dismiss
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.8.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..55c9599045
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: recommendation'
+description: |
+  The recommendation command is used to interact with recommendations.
+---
+
+# Command: recommendation
+
+The `recommendation` command is used to interact with recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.8.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.8.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..1ae6c075e5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'Commands: recommendation info'
+description: |
+  The recommendation info command is used to read the specified recommendation.
+---
+
+# Command: recommendation info
+
+The `recommendation info` command is used to read the specified recommendation.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.8.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..cafdf65b2e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'Commands: recommendation list'
+description: |
+  The recommendation list command is used to list the available recommendations.
+---
+
+# Command: recommendation list
+
+The `recommendation list` command is used to list the available recommendations.
+
+~> Recommendation commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.8.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..0dda69be94
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'Commands: scaling'
+description: |
+  The scaling command is used to interact with the scaling API.
+---
+
+# Command: scaling
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.8.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.8.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..57a106f373
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy info'
+description: |
+  Display an individual Nomad scaling policy.
+---
+
+# Command: scaling policy info
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy Info Options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.8.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..362fc82145
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'Commands: scaling policy list'
+description: |
+  Display all Nomad scaling policies.
+---
+
+# Command: scaling policy list
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Policy List Options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.8.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..b6322dbfc8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Commands: sentinel apply'
+description: >
+  The sentinel apply command is used to write a new, or update an existing,
+  Sentinel policy.
+---
+
+# Command: sentinel apply
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply Options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..6f828efbec
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: sentinel delete'
+description: |
+  The sentinel delete command is used to delete a Sentinel policy.
+---
+
+# Command: sentinel delete
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.8.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..f16f4225c0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'Commands: sentinel'
+description: |
+  The sentinel command is used to interact with Sentinel policies.
+---
+
+# Command: sentinel
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.8.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.8.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..1fff15759b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Commands: sentinel list'
+description: |
+  The sentinel list command is used to list all installed Sentinel policies.
+---
+
+# Command: sentinel list
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.8.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..81e8e6d6cb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'Commands: sentinel read'
+description: |
+  The sentinel read command is used to inspect a Sentinel policies.
+---
+
+# Command: sentinel read
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+~> Sentinel commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read Options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.8.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..cb7f001f83
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'Commands: server force-leave'
+description: >
+  The server force-leave command is used to force a server into the "left"
+  state.
+---
+
+# Command: server force-leave
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`. 
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Force-Leave Options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/server/index.mdx b/content/nomad/v1.8.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..fb032de78f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'Commands: server'
+description: |
+  The server command is used to interact with Nomad servers.
+---
+
+# Command: server
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.8.x/content/docs/commands/server/join.mdx b/content/nomad/v1.8.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..a5a6661ec8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'Commands: server join'
+description: >
+  The server join command is used to join the local server to one or more Nomad
+  servers.
+---
+
+# Command: server join
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: /nomad/tutorials/manage-clusters/federation
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.8.x/content/docs/commands/server/members.mdx b/content/nomad/v1.8.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..3ace4d8db8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'Commands: server members'
+description: >
+  The server members command is used to display a list of the known server
+  members and their status.
+---
+
+# Command: server members
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members Options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server memebers in its JSON format.
+
+- `-t`: Format and display the server memebers using a Go template.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..902be4e38c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'Commands: service delete'
+description: |
+  The service delete command is used to delete Nomad service registrations.
+---
+
+# Command: service delete
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/service/index.mdx b/content/nomad/v1.8.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..c1be98efff
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'Commands: service'
+description: |
+  The service command is used to interact with the service API.
+---
+
+# Command: service
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.8.x/content/docs/commands/service/info.mdx b/content/nomad/v1.8.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..4c0a77007d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'Commands: service info'
+description: |
+  The service info command is used to read the specified Nomad registered
+  service by name.
+---
+
+# Command: service info
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Info Options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/service/list.mdx b/content/nomad/v1.8.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..9715fb65e7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'Commands: service list'
+description: |
+  The service list command is used to list the registered Nomad services.
+---
+
+# Command: service list
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/setup/consul.mdx b/content/nomad/v1.8.x/content/docs/commands/setup/consul.mdx
new file mode 100644
index 0000000000..1fdd828395
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/setup/consul.mdx
@@ -0,0 +1,159 @@
+---
+layout: docs
+page_title: 'Commands: setup consul'
+description: |
+  Setup a Consul cluster for Nomad integration.
+---
+
+# Command: setup consul
+
+This command sets up Consul for allowing Nomad workloads to authenticate
+themselves using Workload Identity.
+
+This command requires `acl:write` permissions for Consul and respects
+`CONSUL_HTTP_TOKEN`, `CONSUL_HTTP_ADDR`, and other [Consul-related environment
+variables][consulenv].
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup consul [options]
+```
+
+## Setup Consul Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup consul
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Consul ACL using their
+respective workload identities.
+
+First we need to connect to Consul.
+
+[?] Is "127.0.0.1:8500" the correct address of your Consul cluster? [Y/n]
+
+Since you're running Consul Enterprise, we will additionally create
+a namespace "nomad-workloads" and bind the auth methods to that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Consul cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+Nomad needs a JWT auth method for Consul services and tasks. The method for
+services will be called "nomad-workloads".
+
+This is the "nomad-workloads" method configuration:
+
+{
+    "Name": "nomad-workloads",
+    "Type": "jwt",
+    "DisplayName": "nomad-workloads",
+    "Description": "Login method for Nomad workloads using workload identities",
+    "TokenLocality": "local",
+    "Config": {
+        "BoundAudiences": [
+            "consul.io"
+        ],
+        "ClaimMappings": {
+            "consul_namespace": "consul_namespace",
+            "nomad_job_id": "nomad_job_id",
+            "nomad_namespace": "nomad_namespace",
+            "nomad_service": "nomad_service",
+            "nomad_task": "nomad_task"
+        },
+        "JWKSURL": "http://localhost:4646/.well-known/jwks.json",
+        "JWTSupportedAlgs": [
+            "RS256"
+        ]
+    },
+    "CreateIndex": 0,
+    "ModifyIndex": 0,
+    "NamespaceRules": [
+        {
+            "BindNamespace": "${value.consul_namespace}"
+        }
+    ]
+}
+[?] Create "nomad-workloads" auth method in your Consul cluster? [Y/n]
+[✔] Created auth method "nomad-workloads".
+
+Consul uses binding rules to map claims between Nomad's JWTs to Consul service
+identities and ACL roles, so we need to create a two binding rules for the auth
+method we created above: one for services, and one for tasks.
+
+This is the binding rule for services:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad services authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" in value",
+    "BindType": "service",
+    "BindName": "${value.nomad_service}",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n]
+[✔] Created binding rule for auth method "nomad-workloads".
+
+This is the binding rule for tasks:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad tasks authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" not in value",
+    "BindType": "role",
+    "BindName": "nomad-${value.nomad_namespace}-tasks",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Consul
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Auth method: nomad-workloads
+  * Binding rules: 4d80108a-6d77-36e1-71b1-d20a9acf8b17
+  * Namespace: nomad-workloads
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted binding rule "4d80108a-6d77-36e1-71b1-d20a9acf8b17".
+[✔] Deleted auth method "nomad-workloads".
+[✔] Deleted namespace "nomad-workloads".
+
+Consul cluster has not been configured for authenticating Nomad tasks and
+services using workload identitiies.
+
+Run the command again to finish the configuration process.
+```
+
+[consulenv]: /consul/commands#environment-variables
diff --git a/content/nomad/v1.8.x/content/docs/commands/setup/index.mdx b/content/nomad/v1.8.x/content/docs/commands/setup/index.mdx
new file mode 100644
index 0000000000..15a354de1e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/setup/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Commands: setup'
+description: |
+  The setup command is used to interact with interactive setup helpers.
+---
+
+# Command: setup
+
+The `setup` command groups helper subcommands used for setting up external
+tools.
+
+<Warning>
+
+These commands are experimental features and may change their behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+Usage: `nomad setup <subcommand> [options]`
+
+Run `nomad setup <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`setup consul`][consul] - Setup a Consul cluster for Nomad integration.
+- [`setup vault`][vault] - Setup a Vault cluster for Nomad integration.
+
+[consul]: /nomad/docs/commands/setup/consul
+[vault]: /nomad/docs/commands/setup/vault
diff --git a/content/nomad/v1.8.x/content/docs/commands/setup/vault.mdx b/content/nomad/v1.8.x/content/docs/commands/setup/vault.mdx
new file mode 100644
index 0000000000..835a85dd4f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/setup/vault.mdx
@@ -0,0 +1,213 @@
+---
+layout: docs
+page_title: 'Commands: setup vault'
+description: |
+  Setup a Vault cluster for Nomad integration.
+---
+
+# Command: setup vault
+
+This command sets up Vault for allowing Nomad workloads to authenticate
+themselves using Workload Identity.
+
+This command requires `acl:write` permissions for Vault and respects
+`VAULT_TOKEN`, `VAULT_ADDR`, and other [Vault-related environment
+variables][vaultenv].
+
+The `-check` option can be used to verify if the Nomad cluster is ready to
+migrate to use Workload Identities with Vault. This option requires
+`operator:read` permission for Nomad.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup vault [options]
+```
+
+## Setup Vault Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+- `-check`: Verify if the Nomad cluster is ready to migrate to Workload
+  Identities.
+
+### Setup Vault Options When Using `-check`:
+
+- `-json`: Output migration status information in its JSON format.
+
+- `-t`: Format and display migration status information using a Go template.
+
+- `-verbose`: Display full information.
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup vault
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Vault ACL using their
+respective workload identities.
+
+First we need to connect to Vault.
+
+[?] Is "http://127.0.0.1:8200" the correct address of your Vault cluster? [Y/n]
+
+Since you're running Vault Enterprise, we will additionally create
+a namespace "nomad-workloads" and create all configuration within that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Vault cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+We will now enable the JWT credential backend and create a JWT auth method that
+Nomad workloads will use.
+
+This is the method configuration:
+
+{
+    "default_role": "nomad-workloads",
+    "jwks_url": "http://localhost:4646/.well-known/jwks.json",
+    "jwt_supported_algs": [
+        "EdDSA",
+        "RS256"
+    ]
+}
+[?] Create JWT auth method in your Vault cluster? [Y/n]
+[✔] Created JWT auth method "jwt-nomad".
+
+We need to create a role that Nomad workloads will assume while authenticating,
+and a policy associated with that role.
+
+
+These are the rules for the policy "nomad-workloads" that we will create. It uses a templated
+policy to allow Nomad tasks to access secrets in the path
+"secrets/data/<job namespace>/<job name>":
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+
+[?] Create the above policy in your Vault cluster? [Y/n]
+[✔] Created policy "nomad-workloads".
+
+We will now create an ACL role called "nomad-workloads" associated with the policy above.
+
+{
+    "bound_audiences": "vault.io",
+    "claim_mappings": {
+        "nomad_job_id": "nomad_job_id",
+        "nomad_namespace": "nomad_namespace",
+        "nomad_task": "nomad_task"
+    },
+    "role_type": "jwt",
+    "token_period": "30m",
+    "token_policies": [
+        "nomad-workloads"
+    ],
+    "token_type": "service",
+    "user_claim": "/nomad_job_id",
+    "user_claim_json_pointer": true
+}
+[?] Create role in your Vault cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Vault
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Policy: "nomad-workloads"
+  * JWT auth method: "jwt-nomad"
+  * Namespace: "nomad-workloads"
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted policy "nomad-workloads".
+[✔] Disabled JWT auth method "jwt-nomad".
+[✔] Deleted namespace "nomad-workloads".
+
+Vault cluster has not been configured for authenticating Nomad tasks and
+services using workload identities.
+
+Run the command again to finish the configuration process.
+```
+
+The `-check` option can use to verify if a cluster is ready to migrate to using
+workload identities with Vault.
+
+```
+$ nomad setup vault -check
+
+Jobs Without Workload Identity for Vault
+The following jobs access Vault but are not configured for workload identity.
+
+You should redeploy them before fully migrating to workload identities with
+Vault to prevent unexpected errors if their tokens need to be recreated.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID       Namespace  Type     Status
+example  default    service  running
+
+Outdated Nodes
+The following nodes are running a version of Nomad that does not support using
+workload identities with Vault.
+
+You should upgrade them to Nomad 1.7 before fully migrating to workload
+identities with Vault to prevent unexpected errors if they receive allocations
+for jobs that use Vault.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID        Name      Address        Version  Drain  Eligibility  Status
+049f7683  client-1  192.168.0.186  1.6.4    false  eligible     ready
+
+Vault Tokens
+The following Vault ACL tokens were created by Nomad but will not be
+automatically revoked after migrating to workload identities. They will expire
+once their TTL reaches zero.
+
+Accessor ID               Allocation ID  Node ID   Configured TTL
+czh9MPcRXzAhxBL9XKyb3Kh1  f00893d4       049f7683  60
+```
+
+[vaultenv]: /vault/docs/commands#environment-variables
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.8.x/content/docs/commands/status.mdx b/content/nomad/v1.8.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..db503e1127
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'Commands: status'
+description: |
+  Display the status output for any Nomad resource.
+---
+
+# Command: status
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.8.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..1c01d42a44
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'Commands: system gc'
+description: |
+  Run the system garbage collection process.
+---
+
+# Command: system gc
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/system/index.mdx b/content/nomad/v1.8.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..ceebafed74
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'Commands: system'
+description: |
+  The system command is used to interact with the system API.
+---
+
+# Command: system
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.8.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.8.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..5b075e1bc2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: system reconcile summaries'
+description: |
+  Reconciles the summaries of all registered jobs.
+---
+
+# Command: system reconcile summaries
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.8.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..3e90a45c4f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'Commands: tls ca create'
+description: |
+  This command creates a Certificate Authority that can be used to create
+  self signed certificates to be used for Nomad TLS setup.
+---
+
+# Command: nomad tls ca create
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## CA Create Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.8.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..0261571b19
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Commands: tls ca info'
+description: |
+  This command displays relevant information that is contained within a
+  Certificate Authority certificate.
+---
+
+# Command: nomad tls ca info
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.8.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..d0fc2d5bb0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Create'
+description: |
+  This command creates a Certificate that can be used for Nomad TLS setup.
+---
+
+# Command: nomad tls cert create
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Command Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-cluster-region=<string>`: DEPRECATED please use `-region`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.8.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.8.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..c37f6a54c0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'Commands: TLS Cert Info'
+description: |
+  This command displays relevant information that is contained within a
+  certificate.
+---
+
+# Command: nomad tls cert info
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.8.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..1e580053ee
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'Commands: tls'
+description: |
+  The tls command is used to help with creating a Certificate Authority 
+  and up self signed certificates for Nomad TLS configuration.
+---
+
+# Command: tls
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/commands/ui.mdx b/content/nomad/v1.8.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..8c585e6884
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'Commands: ui'
+description: |
+  The ui command is used to open the Nomad Web UI.
+---
+
+# Command: ui
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## UI Options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/get.mdx b/content/nomad/v1.8.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..3639942887
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: "Command: var get"
+description: |-
+  The "var get" command retrieves the variable at the given path from
+  Nomad. If no variable exists at that path, an error is returned.
+---
+
+# Command: var get
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Output Options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/index.mdx b/content/nomad/v1.8.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..695bf78dd9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: "Commands: var"
+description: |-
+  The "var" command groups subcommands for interacting with Nomad variables.
+---
+
+# Command: var
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+- [`var lock`][lock] - Acquire a lock over a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
+[lock]: /nomad/docs/commands/var/lock
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/init.mdx b/content/nomad/v1.8.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..8a99bf81fa
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'Commands: var init'
+description: |
+  Generate an example variable specification.
+---
+
+# Command: var init
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init Options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/list.mdx b/content/nomad/v1.8.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d8974ffff2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: "Command: var list"
+description: |-
+  The "var list" command lists data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# Command: var list
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## List Options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/lock.mdx b/content/nomad/v1.8.x/content/docs/commands/var/lock.mdx
new file mode 100644
index 0000000000..0e9921181f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/lock.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: "Command: var lock"
+description: |-
+  The "var lock" command locks a variable, only allowing the lock owner to modify it.
+---
+
+# Command: var lock
+
+The `var lock` command holds a lock on a [variable][].
+
+## Usage
+
+```plaintext
+nomad var lock [options] <lock spec file reference> child...
+nomad var lock [options] <path to store variable> [<variable spec file reference>] child
+```
+
+The lock command provides a mechanism for simple distributed locking. A lock
+is created in the given variable, and only when held, is a child process invoked.
+
+The lock command can be called on an existing variable or an entire new variable
+specification can be provided to the command from a file by using an
+@-prefixed path to a variable specification file. Items to be stored in the 
+variable can be supplied using the specification file as well. 
+
+Nomad lock launches its children in a shell. By default, Nomad will use the
+shell defined in the environment variable SHELL. If SHELL is not defined, 
+it will default to /bin/sh. It should be noted that not all shells terminate
+child processes when they receive SIGTERM. Under Ubuntu, /bin/sh is linked 
+to dash, which does not terminate its children. In order to ensure that 
+child processes are killed when the lock is lost, be sure to set the SHELL
+environment variable appropriately, or run without a shell by setting -shell=false. 
+ 
+If [ACLs][] are enabled, this command requires the 'variables:write' capability
+for the destination namespace and path.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Lock Options
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `ttl`: Optional, TTL for the lock, time the variable will be locked. Defaults to 15s.
+
+- `delay`: Optional, time the variable is blocked from locking when a lease is not renewed.	
+	Defaults to 15s.
+
+- `max-retry`:Optional, max-retry up to this number of times if Nomad returns a 500 error
+	while monitoring the lock. This allows riding out brief periods of
+	unavailability without causing leader elections, but increases the amount of
+	time required to detect a lost lock in some cases. Defaults to 5. Set to 0 to
+	disable.
+
+- `shell`: Optional, use a shell to run the command (can set a custom shell via		
+	the SHELL environment variable). The default value is true.
+
+## Examples
+
+Attempts to acquire a lock over the variable at path "secret/creds" for a time of 
+15s and executes  `nomad job run webapp.nomad.hcl` if it succeeds:
+
+```shell-session
+$ nomad var lock -ttl=15s secret/creds "nomad job run webapp.nomad.hcl"
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var lock secret/foo @spec.nv.json `nomad job run webapp.nomad.hcl`
+```
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]:  /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
+[ACL]: /nomad/docs/other-specifications/acl-policy#variables
+
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.8.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..c924fa77ab
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: "Command: var purge"
+description: |-
+  The "var purge" command permanently removes the specified variable
+  from Nomad.
+---
+
+# Command: var purge
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Command Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.8.x/content/docs/commands/var/put.mdx b/content/nomad/v1.8.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..34a361ad3a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: "Command: var put"
+description: |-
+  The "var put" command writes a variable to the given path in Nomad.
+---
+
+# Command: var put
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Put Options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.8.x/content/docs/commands/version.mdx b/content/nomad/v1.8.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..b58b9ae222
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: version'
+description: |
+  Display the version and build data of Nomad
+---
+
+# Command: version
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..f383469f0a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'Commands: volume create'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# Command: volume create
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..fd7de75021
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'Commands: volume delete'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# Command: volume delete
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..2cea660291
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'Commands: volume deregister'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# Command: volume deregister
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Deregister Options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..f2d0eb8860
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Commands: volume detach'
+description: |
+  Detach volumes with CSI plugins.
+---
+
+# Command: volume detach
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..01d450f5e0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'Commands: volume'
+description: |
+  The volume command is used to interact with volumes.
+---
+
+# Command: volume
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..c16054cdd9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'Commands: volume init'
+description: |
+  Generate an example volume specification.
+---
+
+# Command: volume init
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init Options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..a1ab1352f0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'Commands: volume register'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# Command: volume register
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..bc37a23728
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'Commands: volume snapshot create'
+description: |
+  Create external volume snapshots.
+---
+
+# Command: volume snapshot create
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Create Options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..9145548dfb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot delete'
+description: |
+  Delete external volume snapshots.
+---
+
+# Command: volume snapshot delete
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..726ed55b84
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'Commands: volume snapshot list'
+description: |
+  List external volume snapshots.
+---
+
+# Command: volume snapshot list
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Snapshot List Options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.8.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.8.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..1a93d7f6c0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'Commands: volume status'
+description: |
+  Display information and status of volumes.
+---
+
+# Command: volume status
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General Options
+
+@include 'general_options.mdx'
+
+## Status Options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount Options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.8.x/content/docs/concepts/acl.mdx b/content/nomad/v1.8.x/content/docs/concepts/acl.mdx
new file mode 100644
index 0000000000..784fbd5da5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/acl.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Access Control List (ACL)
+description: Learn about Nomad's ACL subsystem
+---
+
+# Access Control List (ACL)
+
+The Nomad ACL system is designed to be intuitive, high-performance, and to
+provide administrative insight. At the highest level, there are four major
+components to the ACL system: tokens, policies, roles, and capabilities. The
+two components named auth methods and binding rules are specific to Nomad's
+Single Sign-On (SSO) ACL capabilities.
+
+The Nomad [access control tutorials][] provide detailed information and
+guidance on Nomad ACL system.
+
+### Policy
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy comprises one or more rules. The rules define the capabilities of a
+Nomad ACL token for accessing the objects in a Nomad cluster, objects like
+namespaces, node, agent, operator, quota, etc. For more information on writing
+policies, see the [ACL policy reference doc][].
+
+### Role
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+### Token
+
+Requests to Nomad are authenticated using a bearer token. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. `Local` tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+### Workload Identity
+
+Nomad allocations can receive workload identities in the form of a
+[JSON Web Token (JWT)][jwt]. The
+[Workload Identity concept page][workload identity] has more information on
+this topic.
+
+### Auth Method
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+### Binding Rule
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+<Note>
+  Binding rules are evaluated in no specific order, and should there be an
+  overlap in their selectors or scope, a "sum" of all the binding rules will be
+  applied, thus the least granular binding rules will always override the more
+  granular ones, as long as they apply to the same auth method and identity.
+</Note>
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[access control tutorials]: /nomad/tutorials/access-control
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
+[vault]: https://www.vaultproject.io/
diff --git a/content/nomad/v1.8.x/content/docs/concepts/architecture.mdx b/content/nomad/v1.8.x/content/docs/concepts/architecture.mdx
new file mode 100644
index 0000000000..f204891550
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/architecture.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: Architecture
+description: Learn about the internal architecture of Nomad.
+---
+
+# Architecture
+
+Nomad is a complex system that has many different pieces. To help both users and developers of Nomad
+build a mental model of how it works, this page documents the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.8.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.8.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..509c257c87
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,211 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol to provide Consistency as defined by CAP.
+  The consensus protocol is based on Raft: In search of an Understandable
+  Consensus Algorithm. For a visual explanation of Raft, see The Secret Lives of
+  Data.
+---
+
+# Consensus Protocol
+
+Nomad uses a [consensus protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>)
+to provide [Consistency (as defined by CAP)](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr class="warning">
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr class="warning">
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.8.x/content/docs/concepts/cpu.mdx b/content/nomad/v1.8.x/content/docs/concepts/cpu.mdx
new file mode 100644
index 0000000000..103bd9e55e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/cpu.mdx
@@ -0,0 +1,331 @@
+---
+layout: docs
+page_title: CPU
+description: Learn about how Nomad manages CPU resources.
+---
+
+# Modern Processors
+
+Every Nomad node has a Central Processing Unit (CPU) providing the computational
+power needed for running operating system processes. Nomad uses the CPU to
+run tasks defined by the Nomad job submitter. For Nomad to know which nodes
+have sufficient capacity for running a given task, each node in the cluster
+is fingerprinted to gather information about the performance characteristics
+of its CPU. The two metrics associated with each Nomad node with regard to
+CPU performance are its bandwidth (how much it can _compute_) and the number
+of cores.
+
+Modern CPUs may contain heterogeneous core types. Apple introduced the M1 CPU
+in 2020 which contains both _performance_ (P-Core) and _efficiency_ (E-Core)
+types. Each core type operates at a different base frequency. Intel introduced
+a similar topology in its Raptor Lake chips in 2022. When fingerprinting
+the characteristics of a CPU Nomad is capable of taking these advanced CPU
+topologies into account.
+
+[![PE Cores](/img/nomad-pe-cores.png)](/img/nomad-pe-cores.png)
+
+## Calculating CPU Resources
+
+The total CPU bandwidth of a Nomad node is the sum of the product between the
+frequency of each core type and the total number of cores of that type in the
+CPU.
+
+```
+bandwidth = (p_cores * p_frequency) + (e_cores * e_frequency)
+```
+
+The total number of cores is computed by summing the number of P-Cores and the
+number of E-Cores.
+
+```
+cores = p_cores + e_cores
+```
+
+Nomad does not distinguish between logical and physical CPU cores. One of the
+defining differences between the P-Core and E-Core types is that the E-Cores
+do not support hyperthreading, whereas P-Cores do. As such a single physical
+P-Core is presented as 2 logical cores, and a single E-Core is presented as 1
+logical core.
+
+The example below is from a Nomad node with an Intel i9-13900 CPU. It is made
+up of mixed core types, with a P-Core base frequency of 2 GHz and an E-Core
+base frequency of 1.5 GHz.
+
+These characteristics are reflected in the `cpu.frequency.performance` and
+`cpu.frequency.efficiency` node attributes respectively.
+
+```text
+cpu.arch                        = amd64
+cpu.frequency.efficiency        = 1500
+cpu.frequency.performance       = 2000
+cpu.modelname                   = 13th Gen Intel(R) Core(TM) i9-13900
+cpu.numcores                    = 32
+cpu.numcores.efficiency         = 16
+cpu.numcores.performance        = 16
+cpu.reservablecores             = 32
+cpu.totalcompute                = 56000
+cpu.usablecompute               = 56000
+```
+
+## Reserving CPU Resources
+
+In the fingerprinted node attributes, `cpu.totalcompute` indicates the total
+amount of CPU bandwidth the processor is capable of delivering. In some cases it
+may be beneficial to reserve some amount of a node's CPU resources for use by
+the operating system and other non-Nomad processes. This can be done in client
+configuration.
+
+The amount of reserved CPU can be specified in bandwidth via `cpu`.
+
+```hcl
+client {
+  reserved {
+    cpu = 3000 # mhz
+  }
+}
+```
+
+Or as a specific set of `cores` on which to disallow the scheduling of Nomad
+tasks. This capability is available on Linux systems only.
+
+```hcl
+client {
+  reserved {
+    cores = "0-3"
+  }
+}
+```
+
+When the CPU is constrained by one of the above configurations, the node
+attribute `cpu.usablecompute` indicates the total amount of CPU bandwidth
+available for scheduling of Nomad tasks.
+
+## Allocating CPU Resources
+
+When scheduling jobs, a Task must specify how much CPU resource should be
+allocated on its behalf. This can be done in terms of bandwidth in MHz with the
+`cpu` attribute. This MHz value is translated directly into [cpushares][] on
+Linux systems.
+
+```hcl
+task {
+  resources {
+    cpu = 2000 # mhz
+  }
+}
+```
+
+Note that the isolation mechanism around CPU resources is dependent on each task
+driver and its configuration. The standard behavior is that Nomad ensures a task
+has access to _at least_ as much of its allocated CPU bandwidth. In which case
+if a node has idle CPU capacity, a task may use additional CPU resources.  Some
+task drivers enable limiting a task to use only the amount of bandwidth
+allocated to the task, described in the [CPU Hard Limits](#cpu-hard-limits)
+section below.
+
+On Linux systems, Nomad supports reserving whole CPU cores specifically for a
+task. No task will be allowed to run on a CPU core reserved for another task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+  }
+}
+```
+
+Nomad Enterprise supports NUMA aware scheduling, which enables operators to
+more finely control which CPU cores may be reserved for tasks.
+
+### CPU Hard Limits
+
+Some task drivers support the configuration option `cpu_hard_limit`. If enabled
+this option restricts tasks from bursting above their CPU limit even when there
+is idle capacity on the node. The tradeoff is consistency versus utilization.
+A task with too few CPU resources may operate fine until another task is placed
+on the node causing a reduction in available CPU bandwidth, which could cause
+disruption for the underprovisioned task.
+
+### CPU Environment Variables
+
+To help tasks understand the resources available to them, Nomad sets the
+following environment variables in their runtime environment.
+
+
+- `NOMAD_CPU_LIMIT` - The amount of CPU bandwidth allocated on behalf of the
+  task.
+- `NOMAD_CPU_CORES` - The set of cores in [cpuset][] notation reserved for the
+  task. This value is only set if `resources.cores` is configured.
+
+```sh
+NOMAD_CPU_CORES=3-5
+NOMAD_CPU_LIMIT=9000
+```
+
+# NUMA
+
+Nomad clients are commonly provisioned on real hardware in an on-premise
+environment or in the cloud on large `.metal` instance types. In either case it
+is likely the underlying server is designed around a [NUMA topology][numa_wiki].
+Servers that contain multiple CPU sockets or multiple RAM banks per CPU socket
+are characterized by the non-uniform access times involved in accessing system
+memory.
+
+[![NUMA](/img/nomad-numa.png)](/img/nomad-numa.png)
+
+The simplified example machine above has the following topology
+- 2 physical CPU sockets
+- 4 system memory banks, 2 per socket
+- 8 physical cpu cores (4 per socket)
+- 2 logical cpu cores per physical core
+- 4 PCI devices, 1 per memory bank
+
+### Optimizing performance
+
+Operating system processes take longer to access memory across a NUMA boundary.
+
+Using the example above if a task is scheduled on Core 0, accessing memory in
+Mem 1 might take 20% longer than accessing memory in Mem 0, and accessing memory
+in Mem 2 might take 300% longer.
+
+The extreme differences are due to various physical hardware limitations. A core
+accessing memory in its own NUMA node is optimal. Programs which perform a high
+throughput of reads or writes to/from system memory will have their performance
+substantially hindered by not optimizing their spatial locality with regard to
+the systems NUMA topology.
+
+### SLIT tables
+
+Modern machines will define System Locality Distance Information (SLIT) tables
+in their firmware. These tables are understood and made referenceable by the
+Linux kernel. There are two key pieces of information provided by SLIT tables:
+- Which CPU cores belong to which NUMA nodes
+- The penalty incurred for accessing each NUMA node from a core in every other
+NUMA node
+
+The `lscpu` command can be used to describe the Core associativity on a machine.
+For example on an `r6a.metal` EC2 instance:
+
+```shell-session
+$ lscpu | grep NUMA
+NUMA node(s):           4
+NUMA node0 CPU(s):      0-23,96-119
+NUMA node1 CPU(s):      24-47,120-143
+NUMA node2 CPU(s):      48-71,144-167
+NUMA node3 CPU(s):      72-95,168-191
+```
+
+And the associated performance degradations are available via `numactl`:
+
+```shell-session
+$ numactl -H
+available: 4 nodes (0-3)
+...
+node distances:
+node   0   1   2   3
+  0:  10  12  32  32
+  1:  12  10  32  32
+  2:  32  32  10  12
+  3:  32  32  12  10
+```
+
+These SLIT table "node distance" values are presented as approximate relative
+ratios. The value of 10 represents an optimal situation where a memory access
+is occurring from a CPU that is part of the same NUMA node. A value of 20 would
+indicate a 200% performance degradation, 30 for 300%, etc.
+
+### Node Attributes
+
+Nomad clients will fingerprint the machine's NUMA topology and export the
+core associativity as node attributes. This data can provide a Nomad operator
+a better understanding of when it might be useful to make use of NUMA aware
+scheduling for certain workloads.
+
+```
+numa.node.count       = 4
+numa.node0.cores      = 0-23,96-119
+numa.node1.cores      = 24-47,120-143
+numa.node2.cores      = 48-71,144-167
+numa.node3.cores      = 72-95,168-191
+```
+
+## NUMA aware scheduling <EnterpriseAlert inline />
+
+Nomad Enterprise is capable of scheduling tasks in a way that is optimized for
+the NUMA topology of a client node. A task may specify a `numa` block indicating
+its NUMA optimization preference.
+
+```hcl
+task {
+  resources {
+    cores = 6
+    numa {
+      affinity = "require"
+	}
+  }
+}
+```
+
+### `affinity` Options
+
+There are three supported affinity options: `none`, `prefer`, and `require`,
+each with their own advantages and tradeoffs.
+
+#### option `none`
+
+In the `none` mode the Nomad scheduler leverages the apathy of jobs without
+preference of NUMA affinity to help reduce core fragmentation within NUMA nodes.
+It does so by bin-packing the core request of these jobs onto the NUMA nodes
+with the fewest unused cores available.
+
+The `none` mode is the default mode if the `numa` block is not specified.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "none"
+  }
+}
+```
+
+#### option `prefer`
+
+In the `prefer` mode the Nomad scheduler uses the hardware topology of a node
+to calculate an optimized selection of available cores, but does not limit
+those cores to come from a single NUMA node.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "prefer"
+  }
+}
+```
+
+#### option `require`
+
+In the `require` mode the Nomad scheduler uses the topology of each potential
+client to find a set of available CPU cores that belong to the same NUMA node.
+If no such set of cores can be found, that node is marked exhausted for the
+resource of `numa-cores`.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "require"
+  }
+}
+```
+
+## Virtual CPU Fingerprinting
+
+When running on a virtualized host such as Amazon EC2 Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions will
+require installing the `dmidecode` package manually.
+
+[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
+[cpushares]: https://www.redhat.com/sysadmin/cgroups-part-two
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
diff --git a/content/nomad/v1.8.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.8.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..74dff6d50a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,491 @@
+---
+layout: docs
+page_title: Filesystem
+description: |-
+  Nomad creates an allocation working directory for every allocation. Learn what
+  goes into the working directory and how it interacts with Nomad task drivers.
+---
+
+# Filesystem
+
+Nomad creates a working directory for each allocation on a client. This
+directory can be found in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, write logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like the one below.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.8.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.8.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..8ea094b4e3
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Nomad uses a gossip protocol to manage membership. All of this is provided
+  through the use of the Serf library.
+---
+
+# Gossip Protocol
+
+Nomad uses the [Serf library][serf] to provide a [gossip
+protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to manage membership.
+The gossip protocol used by Serf is based on ["SWIM: Scalable Weakly-consistent
+Infection-style Process Group Membership Protocol"][swim], with a few minor
+adaptations. There are more details about [Serf's protocol here][gossip].
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate
+in. Membership information provided by the gossip pool allows servers to perform
+cross region requests. The integrated failure detection allows Nomad to
+gracefully handle an entire region losing connectivity, or just a single server
+in a remote region. Nomad also uses the gossip protocol to detect servers in the
+same region to perform automatic clustering via the [consensus
+protocol](/nomad/docs/concepts/consensus).
+
+To provide all these features, Nomad uses [Serf][serf] as an embedded
+library. From a user perspective, this is not important, since Nomad masks the
+abstraction. However, developers may find it useful to understand how Nomad
+leverages the Serf library.
+
+
+[serf]: https://github.com/hashicorp/serf
+[gossip]: https://github.com/hashicorp/serf/blob/master/docs/internals/gossip.html.markdown
+[swim]: https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf
diff --git a/content/nomad/v1.8.x/content/docs/concepts/index.mdx b/content/nomad/v1.8.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..105e8f44fe
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  This section covers the core concepts of Nomad and explains technical details of
+  Nomads operation.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.8.x/content/docs/concepts/job.mdx b/content/nomad/v1.8.x/content/docs/concepts/job.mdx
new file mode 100644
index 0000000000..8968c0f4c7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/job.mdx
@@ -0,0 +1,126 @@
+---
+layout: docs
+page_title: Job
+description: |-
+  Learn about Nomad's job feature, which is how you deploy your apps, maintenance scripts, cron jobs, and similar tasks.
+---
+
+# Job
+
+This page explains jobs, which are the main Nomad constructs for workloads that
+run your apps, maintenance scripts, cron jobs, and other tasks.
+
+## Background
+
+In Nomad, a _job_ is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into [task groups][task-groups].
+
+Declare the desired state of your job in a [job specification][job-specification], or _jobspec_, that describes
+the tasks and resources necessary for the job to run. You can also
+include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual
+job state matches your desired state.
+
+## Job statuses
+
+After you submit your job, Nomad assigns a status to indicate how a job is
+performing. This status indicates how the job's current allocations compare to the desired
+job state.
+
+Nomad uses one of three values to describe a job's status.
+
+- `complete`
+- `dead`
+- `running`
+
+The CLI and API return these rigid statuses, which are useful for scheduling and
+garbage collection. However, the Nomad UI displays additional human-readable
+statuses to help you manage jobs.
+
+The following table maps the CLI and API statuses to the statuses that appear in the Nomad UI.
+
+| CLI and API status | UI status |
+| ---------------    | --------------- |
+| `complete `        | `Complete`    |
+| `dead`             | `Failed`, `Scaled Down`, `Stopped` |
+| `running`          | `Degraded`, `Deploying`, `Healthy`, `Recovering`, `Running`, `Scaled Down` |
+
+### UI statuses
+
+These job statuses only appear in the Nomad UI.
+
+#### Complete
+
+The `Complete` status indicated that all expected allocations are complete. This
+status applies to batch and sysbatch jobs only.
+
+#### Degraded
+
+The `Degraded` status indicates that a [deployment] is not taking place. Some allocations are failed, lost, or unplaced.
+
+#### Deploying
+
+The `Deploying` status indicates that a deployment is actively taking place.
+
+#### Failed
+
+The `Failed` status indicates that all allocations are failed, lost, or unplaced.
+
+#### Healthy
+
+The `Healthy` status indicates that all expected allocations are running and healthy.
+
+#### Recovering
+
+The `Recovering` status indicates that some allocations are pending.
+
+#### Removed
+
+The `Removed` status indicates that the job appeared in the initial query, but
+the garbage collector has since removed the job. This happens when the user
+remains on the page for a long time.
+
+#### Running
+
+The `Running` status indicates that all expected allocations are running. This
+status applies to batch and sysbatch jobs only.
+
+#### Scaled Down
+
+The `Scaled Down` status indicates that a user has scaled all allocations to
+zero. Nomad's garbage collector has not yet removed or purged the job.
+
+#### Stopped
+
+The `Stopped` status indicates that a user has manually stopped the job.
+Nomad's garbage collector has not yet removed or purged the job.
+
+## Related resources
+
+Refer to the following Nomad documentation pages for more information about
+jobs:
+
+- The [job specification][job-spec] contains detailed
+  configuration and examples.
+- The [Schedulers] page explains the different types of Nomad schedulers and how
+  those schedulers run jobs.
+
+These tutorial resources contain examples of different kinds of jobs and how to
+configure them:
+
+- The [Quick Start][quickstart] tutorials cover deploying an application and
+  its resources, which include parameterized and periodic jobs.
+- The [Deploy and Manage Jobs][deploy-jobs] tutorial contains examples of different types of jobs.
+- The [Create Nomad Job Specifications][job-spec-tutorial] collection explains several aspects of job creation, including parameterized jobs and deploying a Java app on Nomad.
+
+
+[allocations]: /nomad/docs/glossary#allocation
+[deployment]: /nomad/docs/glossary/#deployment
+[deploy-jobs]: /nomad/tutorials/manage-jobs/
+[job-spec]: /nomad/docs/job-specification
+[job-spec-tutorial]: /nomad/tutorials/job-specifications
+[quickstart]: /nomad/tutorials/get-started/gs-deploy-job
+[Schedulers]: /nomad/docs/schedulers
+[task-groups]: /nomad/docs/glossary#task-group
+[tasks]: /nomad/docs/glossary#task
diff --git a/content/nomad/v1.8.x/content/docs/concepts/node-pools.mdx b/content/nomad/v1.8.x/content/docs/concepts/node-pools.mdx
new file mode 100644
index 0000000000..e87474f7cb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/node-pools.mdx
@@ -0,0 +1,379 @@
+---
+layout: docs
+page_title: Node Pools
+description: Learn about the internal architecture of Nomad.
+---
+
+# Node Pools
+
+Node pools are a way to group clients and segment infrastructure into logical
+units that can be targeted by jobs for a strong control over where allocations
+are placed.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+A node pool can be created using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config  block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/docs/commands/node-pool/apply
+[cli_agent_np]: /nomad/docs/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..3d546a93e1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad plugin.
+---
+
+# Base Plugin
+
+The base plugin is a special plugin type implemented by all plugins. It allows
+for common plugin operations such as defining a configuration schema and
+version information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..74c13eb651
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Network Plugins
+description: Learn how Nomad manages custom user-specified network configurations.
+---
+
+# Network plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#linux-post-installation-steps
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..a7f5a4ed19
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: Learn how Nomad manages dynamic storage plugins.
+---
+
+# Storage Plugins
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..40da71b30d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Learn how to author a Nomad device plugin.
+---
+
+# Devices
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, see the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..401d472f2b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in Nomad.
+---
+
+# Plugins
+
+Nomad implements a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+# Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.8.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.8.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..aa6c1e8da4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,279 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to author a Nomad task driver plugin.
+---
+
+# Task Drivers
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, see the [LXC
+driver source][lxcdriver].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation fsisolation.Mode
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propagating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+
+    // DynamicWorkloadUsers indicates this driver is capable (but not required)
+    // of making use of a UID/GID not backed by a user known to the operating
+    // system. The allocation of a unique, not-in-use UID/GID is managed by the
+    // Nomad client ensuring no overlap.
+    DynamicWorkloadUsers bool
+}
+```
+
+The file system isolation options are:
+
+- `fsisolation.Image`: The task driver isolates tasks as machine images.
+- `fsisolation.Chroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `fsisolation.Unveil`: The task driver isolates tasks with the
+  [Landlock LSM][landlock] or other [`unveil`][unveil] like system.
+- `fsisolation.None`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+#### Remote Task Drivers
+
+[Remote Task Drivers][rtd] should set `RemoteTasks` to `true`. Remote Task
+Drivers are task driver plugins that execute tasks on a different system than
+the Nomad client. This means the tasks lifecycle is distinct from the Nomad
+client's.
+
+For task driver plugin authors there are 2 important new behaviors when
+`RemoteTasks` is `true`:
+
+1. The `TaskHandle` returned by `StartTask` will be propagated to replacement
+   allocations if the Nomad client is drained or down. Nomad will call
+   `RecoverTask` instead of `StartTask` for remote tasks in replacement
+   allocations when a `TaskHandle` has been propagated from the previous
+   allocation.
+2. If the Nomad client managing a remote task is drained or if the allocation
+   was `lost`, the remote task is sent a special `DETACH` kill signal. This
+   indicates the plugin should stop managing the remote task, but _not_ stop
+   it.
+
+These behaviors are meant to keep remote tasks running even when the Nomad
+client managing them is shutdown. Remote tasks are stopped when the job is
+explicitly stopped like traditional tasks.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### Dynamic Workload Users
+
+Nomad is capable of dynamically allocating unused UID/GID values for use by
+task drivers when launching a task. These UID/GID values are deallocated when
+the task is destroyed. The pool of available UID/GID values can be controlled
+in client config via the [users][users] block.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[lxcdriver]: https://github.com/hashicorp/nomad-driver-lxc
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[rtd]: /nomad/plugins/drivers/remote
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[unveil]: https://man.openbsd.org/unveil
+[users]: /nomad/docs/configuration/client#users-block
+
diff --git a/content/nomad/v1.8.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.8.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..1bc895b27a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling
+
+Scheduling is a core function of Nomad. It is the process of assigning tasks
+from jobs to client machines. The design is heavily inspired by Google's work on
+both [Omega: flexible, scalable schedulers for large compute clusters][omega] and
+[Large-scale cluster management at Google with Borg][borg]. See the links below
+for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.8.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.8.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..b50949ae0a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: Placement
+description: Learn about how placements are computed in Nomad.
+---
+
+# Placement
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+### Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+#### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+#### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+### Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+### Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+
+[api_client_metadata]: /nomad/api-docs/client#update-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/concepts/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.8.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.8.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..93ce9723a6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Preemption
+description: Learn about how preemption works in Nomad.
+---
+
+# Preemption
+
+Preemption allows Nomad to kill existing allocations in order to place allocations for a higher priority job.
+The evicted allocation is temporarily displaced until the cluster has capacity to run it. This allows operators to
+run high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+# Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+# Details
+
+Preemption is enabled by default for system jobs. Operators can use the [scheduler config](/nomad/api-docs/operator#update-scheduler-configuration) API endpoint to disable preemption.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of more than 10 from the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+# Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+# Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.8.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.8.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..e6b39f2498
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Scheduling
+description: Learn about how scheduling works in Nomad.
+---
+
+# Scheduling in Nomad
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary "nouns" in Nomad; jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.8.x/content/docs/concepts/security.mdx b/content/nomad/v1.8.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..ac5f52ade9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/security.mdx
@@ -0,0 +1,347 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad relies on both a lightweight gossip mechanism and an RPC system to
+  provide various features. Both of the systems have different security
+  mechanisms that stem from their designs. However, the security mechanisms of
+  Nomad have a common goal: to provide confidentiality, integrity, and
+  authentication.
+---
+
+## Overview
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. It can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual authentication of both the TLS server and client x509 certificates
+  prevents internal abuse by preventing unauthenticated access to network
+  components within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** - Enables
+  authorization for authenticated connections by granting capabilities to ACL
+  tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** -
+  Access to read and write to a namespace can be
+  controlled to allow for granular access to job information managed within a
+  multi-tenant cluster.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - Sentinel policies allow for granular control over
+  components such as task drivers within a cluster.
+
+### Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+### Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+#### Requirements
+
+- **[mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)** -
+  Mutual TLS (mTLS) enables [mutual
+  authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+  security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+    Some API endpoints, such as [`/v1/metrics`][api_metrics] and
+    [`/v1/status/peers`][api_status_peers], can be accessed without an ACL
+    token and may be exposed to anyone with access to the Nomad HTTP address
+    when using `tls.verify_https_client=false`. You can use a reverse proxy or
+    other external means to restrict access to them.
+
+- **[ACLs enabled](/nomad/tutorials/access-control)** - The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)**
+
+  - This feature allows for a cluster to be shared by
+    multiple teams within a company. Using this logical separation is important
+    for multi-tenant clusters to prevent users without access to that namespace
+    from conflicting with each other. This requires ACLs to be enabled in order
+    to be enforced.
+
+- **[Sentinel Policies](/nomad/tutorials/governance-and-policy/sentinel)**
+  (**Enterprise Only**) - [Sentinel](https://www.hashicorp.com/sentinel/) is
+  a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- **[Resource Quotas](/nomad/tutorials/governance-and-policy/quotas)**
+  (**Enterprise Only**) - Can limit a namespace's access to the underlying
+  compute resources in the cluster by setting upper-limits for operators.
+  Access to these resource quotas can be managed via ACLs to ensure read-only
+  access for operators so they can't just change their quotas.
+
+#### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+### Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+#### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+#### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+### Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                           |
+|----------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                   |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf][serf].                                                                        |
+
+
+[api_metrics]: /nomad/api-docs/metrics
+[api_status_peers]: /nomad/api-docs/status#list-peers
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[serf]: https://github.com/hashicorp/serf
diff --git a/content/nomad/v1.8.x/content/docs/concepts/variables.mdx b/content/nomad/v1.8.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..9b1fc45a95
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,251 @@
+---
+layout: docs
+page_title: Variables
+description: Learn about the Nomad Variables feature
+---
+
+# Nomad Variables
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to [provide such configuration to tasks](/nomad/docs/job-specification/template#nomad-variables),
+but prior to Nomad 1.4 has left the role of storing that configuration to
+external services such as [HashiCorp Consul] and [HashiCorp Vault].
+
+Nomad Variables provide the option to store configuration at file-like paths
+directly in Nomad's state store. You can [access these variables](/nomad/docs/job-specification/template#nomad-variables) directly from
+your task `template`s. The contents of these variables are encrypted
+and replicated between servers via raft. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the Variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as Variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. See [Key Management][] for details.
+
+## ACL for Variables
+
+Every Variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to Variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for Variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+Tasks can access Variables with the [`template`] block or using the [Task API].
+The [workload identity] for each task grants it automatic read and list access to
+Variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to Variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+## Locks
+
+Nomad provides the ability to block a variable from being updated for a period
+of time by setting a lock on it. Once a variable is locked, it can be read by
+everyone, but it can only be updated by the lock holder.
+
+The locks are designed to provide granular locking and are heavily inspired by
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems][].
+
+A lock is composed of an ID, a TTL, and a lock delay. The ID is generated by
+the Nomad Server and must be provided on every request to modify the variable's
+items or the lock itself. The TTL defines the time the lock will be held; if the
+lock needs to be in place for longer, it can be renewed for as many new periods
+as wanted.
+
+Once it is no longer needed, it must be released. If by the time the TTL expires,
+and no renew or release calls were made, the variable will remain locked for at
+least the lock delay duration, to avoid a possible split-brain situation, where
+there are two holders at the same time.
+
+### Leader election backed by Nomad Variable Locks
+
+For some applications, like HDFS or the Nomad Autoscaler, it is necessary to
+have multiple instances running to ensure redundancy in case of a failure, but
+only one of them may be active at a time as a leader.
+
+As part of the [Go Package][], Nomad offers a helper that takes one variable and
+uses a lock over it as a sync mechanism to run multiple instances but always
+keeping just one running at any given time, using the following algorithm:
+
+[![Leader Election Helper](/img/nomad-vars-leader-election-sdk.png)](/img/nomad-vars-leader-election-sdk.png)
+
+As soon as any instance starts, it tries to lock the sync variable. If it succeeds,
+it continues to execute while a secondary thread is in charge of keeping track of
+the lock and renewing it when necessary. If by any chance the renewal fails,
+the main process is forced to return, and the instance goes into standby until it
+attempts to acquire the lock over the sync variable. 
+
+Only threads 1 and 3 or thread 2 are running at any given time, because every 
+instance is either executing as normal while renewing the lock or waiting for a 
+chance to acquire it and run.
+
+When the main process, or protected function, returns, the helper releases the 
+lock, allowing a second instance to start running.
+
+To see it implemented live, look for the [`nomad var lock`][] command 
+implementation or the [Nomad Autoscaler][] High Availability implementation.
+
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems]: https://research.google/pubs/pub27897/
+[`nomad var lock`]: /nomad/docs/commands/var
+[Go Package]: https://pkg.go.dev/github.com/hashicorp/nomad/api
+[implementation]: https://github.com/hashicorp/nomad/blob/release/1.7.0/command/var_lock.go#L240
+[Nomad Autoscaler]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.4.0/command/agent.go#L392
+[Task API]: /nomad/api-docs/task-api
diff --git a/content/nomad/v1.8.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.8.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..3854896a4d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Learn about Nomad's workload identity feature
+---
+
+# Workload Identity
+
+Every workload running in Nomad is given a default identity. When an
+[allocation][] is accepted by the [plan applier][], the leader generates a
+Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring.
+Additional workload identities may be defined in tasks and services using the
+[`identity`][identity-block] block.
+
+## Workload Identity Claims
+
+Nomad workload identity for tasks include the following identity claims.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+Workload identities for Consul services have a claim with the service name
+instead of the task name.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Workload identities for tasks that use Vault have an additional claim for
+[`vault.role`][jobspec_vault_role] if a role is specified in the job.
+
+-> **Note:** This claim will *not* be added if the role is inherited from
+the [agent configuration][vault_role_agent_config] and is not present
+in the Nomad job specification.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+  "vault_role": "nomad-jwt-login"
+}
+```
+
+### Nomad Enterprise <EnterpriseAlert inline />
+
+In Nomad Enterprise, tasks and services with a [`consul`][jobspec_consul] block
+that defines a [`namespace`][jobspec_consul_ns] value, or inside a `group`
+block that does it, have an additional claim called `consul_namespace`.
+
+```json
+{
+  "consul_namespace": "prod",
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Similarly, tasks with a [`vault.namespace`][jobspec_vault_ns] value have the additional claim
+`vault_namespace`.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+  "vault_namespace": "prod",
+}
+```
+
+## Workload Identity for Nomad
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+### Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+### Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+### Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identity for Consul and Vault
+
+Consul and Vault can be configured to accept workload identities from Nomad for
+authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
+integration pages for more information.
+
+[allocation]: /nomad/docs/concepts/architecture#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[jobspec_consul]: /nomad/docs/job-specification/consul
+[jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace
+[jobspec_vault_ns]: /nomad/docs/job-specification/vault#namespace
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[vault_role_agent_config]: /nomad/docs/configuration/vault#create_from_role
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[taskapi]: /nomad/api-docs/task-api
+[consul_int]: /nomad/docs/integrations/consul-integration
+[vault_int]: /nomad/docs/integrations/vault-integration
diff --git a/content/nomad/v1.8.x/content/docs/configuration/acl.mdx b/content/nomad/v1.8.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..07c6437783
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block - Agent Configuration
+description: >-
+  The "acl" block configures the Nomad agent to enable ACLs and tune various
+  parameters.
+---
+
+# `acl` Block
+
+<Placement groups={['acl']} />
+
+The `acl` block configures the Nomad agent to enable ACLs and tunes various
+ACL parameters. Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. See [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.8.x/content/docs/configuration/audit.mdx b/content/nomad/v1.8.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..1839d93523
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,299 @@
+---
+layout: docs
+page_title: audit Block - Agent Configuration
+description: >-
+  The "audit" block configures the Nomad agent to configure Audit Logging
+  behavior. This is an Enterprise-only feature.
+---
+
+# `audit` Block
+
+<Placement groups={['audit']} />
+
+The `audit` block configures the Nomad agent to configure Audit logging behavior.
+Audit logging is an Enterprise-only feature.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Audit Log Format
+
+Below are two audit log entries for a request made to `/v1/job/web/summary`. The
+first entry is for the `OperationReceived` stage. The second entry is for the
+`OperationComplete` stage and includes the contents of the `OperationReceived`
+stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.8.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.8.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..53cb78c19d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: autopilot Block - Agent Configuration
+description: >-
+  The "autopilot" block configures the Nomad agent to configure Autopilot
+  behavior.
+---
+
+# `autopilot` Block
+
+<Placement groups={['autopilot']} />
+
+The `autopilot` block configures the Nomad agent to configure Autopilot behavior.
+For more information about Autopilot, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - (Enterprise-only) Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version) parameter.
diff --git a/content/nomad/v1.8.x/content/docs/configuration/client.mdx b/content/nomad/v1.8.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..38ee8f412a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/client.mdx
@@ -0,0 +1,796 @@
+---
+layout: docs
+page_title: client Block - Agent Configuration
+description: |-
+  The "client" block configures the Nomad agent to accept jobs as assigned by
+  the Nomad server, join the cluster, and specify driver-specific configuration.
+---
+
+# `client` Block
+
+<Placement groups={['client']} />
+
+The `client` block configures the Nomad agent to accept jobs as assigned by
+the Nomad server, join the cluster, and specify driver-specific configuration.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `alloc_mounts_dir` `(string: "")` - Specifies the directory to use for binding
+  mounts for the [unveil file isolation mode][unveil]. When this parameter is
+  empty, Nomad generates the path as a sibling of the [top-level
+  `data_dir`][top_level_data_dir], with the name `alloc_mounts`. For example, if
+  the `data_dir` is `/opt/nomad/data`, then the alloc mounts directory is
+  `/opt/nomad/alloc_mounts`. This must be an absolute path and should not be
+  inside the Nomad data directory. Nomad creates the directory on the host,
+  if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `preferred_address_family` `(string: "")` - Specifies the preferred address family
+  for the network interface. The value can be `ipv4` or `ipv6`. If the selected network
+  interface has both IPv4 and IPv6 addresses, this option will select an IP address of
+  the preferred family. When the option is not specified, the current behavior is conserved:
+  the first IP address is selected no matter the family.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery. See the
+  documentation for more detail.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints. When hairpin mode
+  is enabled, allocations are able to reach their own IP and **all ports** bound
+  to it. Changing this value requires a reboot of the client host to take
+  effect.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+- `users` <code>([Users](#users-block): nil)</code> - Specifies options
+  concerning Nomad client's use of operating system users.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+See the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver, please
+see the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers. If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers. If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: see below)` - Specifies a comma-separated list of
+  environment variable keys not to pass to these tasks. Nomad passes the host
+  environment variables to `exec`, `raw_exec` and `java` tasks. If specified,
+  the defaults are overridden. If a value is provided, **all** defaults are
+  overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  VAULT_TOKEN
+  NOMAD_LICENSE
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  GOOGLE_APPLICATION_CREDENTIALS
+  ```
+
+- `"user.denylist"` `(string: see below)` - Specifies a comma-separated
+  denylist of usernames for which a task is not allowed to run. This only
+  applies if the driver is included in `"user.checked_drivers"`. If a value is
+  provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: see below)` - Specifies a comma-separated
+  list of drivers for which to enforce the `"user.denylist"`. For drivers using
+  containers, this enforcement is usually unnecessary. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled. A common use-case for the fingerprint denylist is to disable
+  fingerprinters of irrelevant cloud environments, which can slow down client
+  agent startup time.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "env_aws,env_gce,env_azure,env_digitalocean"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(string: "")` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports
+  to reserve on all fingerprinted network devices. Ranges can be specified by
+  using a hyphen separating the two inclusive ends. See also
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `filesystem_isolation_extra_paths` `([]string: nil)` - Allow extra paths
+  in the filesystem isolation. Paths are specified in the form `[kind]:[mode]:[path]`
+  where `kind` must be either `f` or `d` (file or directory) and
+  `mode` must be zero or more of `r`, `w`, `c`, `x` (read, write, create, execute) e.g.
+  `f:r:/dev/urandom` would enable reading the /dev/urandom file,
+  `d:rx:/opt/bin` would enable reading and executing from the /opt/bin directory
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. This
+  configuration is also exposed in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path      = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr           = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+### `users` Block
+
+The `users` block controls aspects of Nomad client's use of operating system
+users.
+
+```hcl
+client {
+  users {
+    dynamic_user_min = 80000
+    dynamic_user_max = 89999
+  }
+}
+```
+
+- `dynamic_user_min` `(int: 80000)` - The lowest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+- `dynamic_user_max` `(int: 89999)` - The highest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values below are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/runtime/interpolation
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/docs/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[unveil]: /nomad/docs/concepts/plugins/task-drivers#fsisolation-unveil
diff --git a/content/nomad/v1.8.x/content/docs/configuration/consul.mdx b/content/nomad/v1.8.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..fd5e05df90
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,385 @@
+---
+layout: docs
+page_title: consul Block - Agent Configuration
+description: |-
+  The "consul" block configures the Nomad agent's communication with
+  Consul for service discovery and key-value integration. When
+  configured, tasks can register themselves with Consul, and the Nomad cluster
+  can automatically bootstrap itself.
+---
+
+# `consul` Block
+
+<Placement groups={['consul']} />
+
+The `consul` block configures the Nomad agent's communication with
+[Consul][consul] for service discovery and key-value integration. When
+configured, tasks can register themselves with Consul, and the Nomad cluster can
+[automatically bootstrap][bootstrap] itself.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+In Nomad Enterprise, you may specify multiple `consul` blocks to configure
+access to multiple Consul clusters. Each Consul cluster must have a different
+value for the [`name`](#name) field.
+
+## `consul` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`consul.cluster`][] or [`service.cluster`][] fields. In Nomad
+  Community Edition, only the `"default"` cluster will be used, so this field
+  should be omitted.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the [Consul
+  namespace](/consul/docs/enterprise/namespaces) used by the Consul
+  integration. If non-empty, this namespace will be used on all Consul API calls
+  and for Consul Connect configurations, unless overridden by the job's
+  [`consul.namespace`][] field.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and client services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it will default to Consul's anonymous policy,
+  which may or may not allow writes. Will default to the `CONSUL_HTTP_TOKEN`
+  environment variable if set.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`][] set to `true`.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `client_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check is critical.
+
+- `client_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check shows a warning.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+  certificate used for communication between Connect sidecar proxies and Consul
+  agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+  <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. See
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not
+  include the values for the ACL `token` or `auth`. This option should be
+  disabled in environments where Consul ACLs are not enabled.
+
+- `service_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for services.
+
+- `task_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for tasks.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `server_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check is critical.
+
+- `server_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check shows a warning.
+
+- `service_identity` <code>([Identity](#service_identity-parameters): nil)</code> - Specifies
+  a default Workload Identity to use when obtaining Service Identity tokens from
+  Consul to register services. Refer to [Workload Identity](#workload-identity)
+  for a recommended configuration.
+
+- `task_identity` <code>([Identity](#task_identity-parameters): nil)</code> - Specifies a
+  default Workload Identity to use when obtaining Consul tokens from Consul to
+  support [`template`][] blocks. Refer to [Workload
+  Identity](#workload-identity) for a recommended configuration.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul
+  Connect enabled services listed in the job. This option should be disabled in
+  an untrusted environment.
+
+## Workload Identity
+
+The `service_identity` and `task_identity` blocks accept all the same values as
+the job specification's [`identity`][identity_block] (except that the
+`service_identity` ignores the `env` and `file` fields). By ensuring these
+blocks are set on the Nomad servers, you can automatically migrate your existing
+jobs to use Workload Identity without modifying the job specification and
+resubmitting them.
+
+The recommended configuration for `service_identity` and `task_identity` is as
+follows. See [Migrating to Using Workload Identity with Consul][] for details on
+how to configure Consul to accept these identities. Note that the `ttl` field
+here refers to the TTL of the Nomad identity and not the Consul token.
+
+```hcl
+consul {
+  service_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+
+  task_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+}
+```
+
+### `service_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### `task_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN_consul_default` (or `NOMAD_TOKEN_consul_<name>` depending
+  on the [`name`](#name) field) environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_consul_default.jwt` (or
+  `secrets/nomad_consul_<name>.jwt` depending on the [`name`](#name) field). If
+  the [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul Namespace <EnterpriseAlert inline/>
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace. The Consul policy below shows an example policy
+configuration for a Nomad server:
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
+[`consul.cluster`]: /nomad/docs/job-specification/group#cluster
+[`service.cluster`]: /nomad/docs/job-specification/service#cluster
+[identity_block]: /nomad/docs/job-specification/identity
+[`template`]: /nomad/docs/job-specification/template
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[auth-method]: /consul/docs/security/acl/auth-methods/jwt
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[consul_bound_aud]: /consul/docs/security/acl/auth-methods/jwt#boundaudiences
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
diff --git a/content/nomad/v1.8.x/content/docs/configuration/index.mdx b/content/nomad/v1.8.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..3c70ce061a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/index.mdx
@@ -0,0 +1,400 @@
+---
+layout: docs
+page_title: Agent Configuration
+description: Learn about the configuration options available for the Nomad agent.
+---
+
+# Nomad Configuration
+
+Nomad agents have a variety of parameters that can be specified via
+configuration files or command-line flags. Configuration files are written in
+[HCL][hcl]. Nomad can read and combine parameters from multiple configuration
+files or directories to configure the Nomad agent.
+
+## Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: see below)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  see the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: see below)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - This is a nested object that configures limits that are enforced by
+   the agent. The following parameters are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: see below)` - Specifies the network ports used for different
+  services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(see [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.8.x/content/docs/configuration/keyring/awskms.mdx b/content/nomad/v1.8.x/content/docs/configuration/keyring/awskms.mdx
new file mode 100644
index 0000000000..621a41c5f0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/keyring/awskms.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: AWS KMS - Keyring - Configuration
+description: |-
+  The AWS KMS keyring configures Nomad to use AWS KMS as the key material
+  wrapping mechanism.
+---
+
+# `awskms` keyring
+
+The AWS KMS keyring configures Nomad to use AWS KMS to wrap its keyring. This
+example shows configuring AWS KMS keyring through the Nomad configuration file
+by providing all the required values.
+
+```hcl
+keyring "awskms" {
+  active = true
+  name   = "example"
+
+  # fields specific to awskms
+  region     = "us-east-1"
+  access_key = "AKIAIOSFODNN7EXAMPLE"
+  secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  kms_key_id = "19ec80b0-dfdd-4d97-8164-c6examplekey"
+  endpoint   = "https://vpce-0e1bb1852241f8cc6-pzi0do8n.kms.us-east-1.vpce.amazonaws.com"
+}
+```
+
+## `awskms` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `region` `(string: "us-east-1")`: The AWS region where the encryption key
+  lives. If not provided, may be populated from the `AWS_REGION` or
+  `AWS_DEFAULT_REGION` environment variables, from your `~/.aws/config` file, or
+  from instance metadata.
+
+- `access_key` `(string: <required>)`: The AWS access key ID to use. Alternately
+  specify via the `AWS_ACCESS_KEY_ID` environment variable or as part of the AWS
+  profile from the AWS CLI or instance profile.
+
+- `session_token` `(string: "")`: Specifies the AWS session token. Alternately
+  specify via the environment variable `AWS_SESSION_TOKEN`.
+
+- `secret_key` `(string: <required>)`: The AWS secret access key to
+  use. Alternately specify via the `AWS_SECRET_ACCESS_KEY` environment variable
+  or as part of the AWS profile from the AWS CLI or instance profile.
+
+- `kms_key_id` `(string: <required>)`: The AWS KMS key ID or ARN to use for
+  encryption and decryption. You can alternately use an alias in the format
+  `alias/key-alias-name`.
+
+- `endpoint` `(string: "")`: The KMS API endpoint for AWS KMS
+  requests. Alternately specify via the `AWS_KMS_ENDPOINT` environment
+  variable. This is useful, for example, when connecting to KMS over a [VPC
+  Endpoint][]. If not set, Nomad uses the default API endpoint for your region.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file allows you to pass in
+`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as part of the keyring block's
+parameters, we strongly recommended that you set these values via environment
+variables or instance profile.
+
+AWS authentication values:
+
+- `AWS_REGION` or `AWS_DEFAULT_REGION`
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
+
+Note: The client uses the official AWS SDK and the specified credentials,
+environment credentials, shared file credentials, or IAM role/ECS task
+credentials in that order, if you do not provide the aforementioned AWS-specific
+values. Refer to the [AWS SDK and Tools standard credentials][aws-std-creds]
+documentation.
+
+Nomad needs the following permissions on the KMS key:
+
+- `kms:Encrypt`
+- `kms:Decrypt`
+- `kms:DescribeKey`
+
+Grant these via IAM permissions on the principal that Nomad uses, on the KMS key
+policy for the KMS key, or via KMS Grants on the key.
+
+## Key rotation
+
+This keyring supports rotating the root keys defined in AWS KMS
+[doc][rotate_docs]. Both automatic rotation and manual rotation is supported for
+KMS since the key information is stored with the encrypted data. Old keys must
+not be disabled or deleted and are used to decrypt older data. Any new or
+updated data is encrypted with the current key defined in the keyring
+configuration or set to current under a key alias.
+
+[VPC Endpoint]: https://docs.aws.amazon.com/kms/latest/developerguide/kms-vpc-endpoint.html
+[rotate_docs]: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html
+[aws-std-creds]: https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html
diff --git a/content/nomad/v1.8.x/content/docs/configuration/keyring/azurekeyvault.mdx b/content/nomad/v1.8.x/content/docs/configuration/keyring/azurekeyvault.mdx
new file mode 100644
index 0000000000..7addbf2b1d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/keyring/azurekeyvault.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: Azure Key Vault - Keyring - Configuration
+description: >-
+  The Azure Key Vault keyring configures Nomad to use Azure Key Vault as the key material
+  wrapping mechanism.
+---
+
+# `azurekeyvault` keyring
+
+The AWS KMS keyring configures Nomad to use AWS KMS to wrap its keyring. This
+example shows configuring Azure Key Vault keyring through the Nomad
+configuration file by providing all the required values.
+
+```hcl
+seal "azurekeyvault" {
+  active = true
+  name   = "example"
+
+  # fields specific to azurekeyvault
+  tenant_id      = "46646709-b63e-4747-be42-516edeaf1e14"
+  client_id      = "03dc33fc-16d9-4b77-8152-3ec568f8af6e"
+  client_secret  = "DUJDS3..."
+  vault_name     = "nomad"
+  key_name       = "nomad_key"
+}
+```
+
+## `azurekeyvault` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `tenant_id` `(string: <required>)`: The tenant id for the Azure Active
+  Directory organization. Alternately specify via the `AZURE_TENANT_ID`
+  environment variable.
+
+- `client_id` `(string: <required or MSI>)`: The client id for credentials to
+  query the Azure APIs. Alternately specify via the `AZURE_CLIENT_ID`
+  environment variable.
+
+- `client_secret` `(string: <required or MSI>)`: The client secret for
+  credentials to query the Azure APIs. Alternately specify via the
+  `AZURE_CLIENT_SECRET` environment variable.
+
+- `environment` `(string: "AZUREPUBLICCLOUD")`: The Azure Cloud environment API
+  endpoints to use. Alternately specify via the `AZURE_ENVIRONMENT` environment
+  variable.
+
+- `vault_name` `(string: <required>)`: The Key Vault vault to use the encryption
+  keys for encryption and decryption.
+
+- `key_name` `(string: <required>)`: The Key Vault key to use for encryption and
+  decryption.
+
+- `resource` `(string: "vault.azure.net")`: The AZ KeyVault resource's DNS
+  Suffix to connect to. Alternately specify via the `AZURE_AD_RESOURCE`
+  environment variable. Needs to be changed to connect to Azure's Managed HSM
+  KeyVault instance type.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+Azure authentication values:
+
+- `AZURE_TENANT_ID`
+- `AZURE_CLIENT_ID`
+- `AZURE_CLIENT_SECRET`
+- `AZURE_ENVIRONMENT`
+- `AZURE_AD_RESOURCE`
+
+~> **Note:** If Nomad is hosted on Azure, Nomad can use Managed Service
+Identities (MSI) to access Azure instead of an environment and shared client id
+and secret. MSI must be [enabled][msi_enabled] on the VMs hosting Nomad. We
+recommend this configuration since MSI prevents your Azure credentials from
+being stored as clear text.
+
+-> **Note:** If you are using a Managed HSM KeyVault, you must specify
+`AZURE_AD_RESOURCE` or the `resource` configuration parameter; usually this
+should point to `managedhsm.azure.net` but could point to other suffixes
+depending on Azure environment.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Azure Key Vault. Key metadata is
+stored with the encrypted data to ensure the correct key is used during
+decryption operations. Set up Azure Key Vault with [key rotation][] using Azure
+Automation Account so Vault recognizes newly rotated keys.
+
+[msi_enabled]: https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm
+[key rotation]: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-key-rotation-log-monitoring
diff --git a/content/nomad/v1.8.x/content/docs/configuration/keyring/gcpckms.mdx b/content/nomad/v1.8.x/content/docs/configuration/keyring/gcpckms.mdx
new file mode 100644
index 0000000000..87ebf0734b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/keyring/gcpckms.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: GCP Cloud KMS - Keyrings - Configuration
+description: >-
+  The GCP Cloud KMS keyring configures Nomad to use GCP Cloud KMS as the keyring
+  wrapping mechanism.
+---
+
+# `gcpckms` keyring
+
+
+The GCP Cloud KMS keyring configures Nomad to use GCP Cloud KMS to wrap its
+keyring. This example shows configuring GCP Cloud KMS keyring through the Nomad
+configuration file by providing all the required values.
+
+```hcl
+keyring "gcpckms" {
+  active = true
+  name   = "example"
+
+  credentials = "/etc/nomad.d/nomad-user-creds.json"
+  project     = "nomad-project"
+  region      = "global"
+  key_ring    = "nomad-keyring"
+  crypto_key  = "nomad-key"
+}
+```
+
+## `gcpckms` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `credentials` `(string: <required>)`: The path to the credentials JSON file to
+  use. Alternately specify via the `GOOGLE_CREDENTIALS` or
+  `GOOGLE_APPLICATION_CREDENTIALS` environment variable or set automatically if
+  running under Google Compute Engine.
+
+- `project` `(string: <required>)`: The GCP project ID to use. Alternately
+  specify via the `GOOGLE_PROJECT` environment variable.
+
+- `region` `(string: <required>)`: The GCP region/location where the key ring
+  lives. Alternately specify via the `GOOGLE_REGION` environment variable.
+
+- `key_ring` `(string: <required>)`: The GCP CKMS key ring to use.
+
+- `crypto_key` `(string: <required>)`: The GCP CKMS crypto key to use for
+  encryption and decryption.
+
+## Authentication &amp; permissions
+
+You must provide authentication-related values either as environment
+variables or as configuration parameters.
+
+GCP authentication values:
+
+- `GOOGLE_CREDENTIALS` or `GOOGLE_APPLICATION_CREDENTIALS`
+- `GOOGLE_PROJECT`
+- `GOOGLE_REGION`
+
+Note: The client uses the official Google SDK and the specified credentials,
+environment credentials, or [application default credentials][] in that order,
+if you do not provide the aforementioned GCP-specific values.
+
+The service account needs the following minimum permissions on the crypto key:
+
+```text
+cloudkms.cryptoKeyVersions.useToEncrypt
+cloudkms.cryptoKeyVersions.useToDecrypt
+cloudkms.cryptoKeys.get
+```
+
+These permissions can be described with the following role:
+
+```text
+roles/cloudkms.cryptoKeyEncrypterDecrypter
+cloudkms.cryptoKeys.get
+```
+
+Use `cloudkms.cryptoKeys.get` permission for retrieving metadata information of
+keys from CloudKMS within this engine initialization process.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Google Cloud KMS
+[doc][rotating_keys]. Both scheduled rotation and manual rotation is supported
+for CKMS since the key information. Old keys version must not be disabled or
+deleted and are used to decrypt older data. Any new or updated data is encrypted
+with the primary key version.
+
+
+[application default credentials]: https://developers.google.com/identity/protocols/application-default-credentials
+[rotating_keys]: https://cloud.google.com/kms/docs/rotating-keys
diff --git a/content/nomad/v1.8.x/content/docs/configuration/keyring/index.mdx b/content/nomad/v1.8.x/content/docs/configuration/keyring/index.mdx
new file mode 100644
index 0000000000..aefe410f27
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/keyring/index.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: keyring Block - Agent Configuration
+description: >-
+  The "keyring" block configures the Nomad servers keyring decryption behavior.
+---
+
+# `keyring` Block
+
+<Placement groups={['keyring']} />
+
+The `keyring` block configures how the Nomad server protects the keyring used
+for encrypting [variables][] and signing [workload identities][]. By default,
+Nomad encrypts the key material with a unique key encryption key (KEK) that is
+not shared between servers, and writes the wrapped key material to disk as
+described in [Key Management][]. Nomad refers to this as `"aead"` (authenticated
+encryption with associated data). Using the `keyring` configuration block, Nomad
+servers can instead use an external key management system (KMS) or Vault transit
+encryption. The encrypted key is stored on disk but is now protected against
+offline attacks because the KEK is not present in the file.
+
+All `keyring` blocks require a label for the KMS type. Each external KMS has its
+own configuration options. The `keyring` block only applies to Nomad servers,
+not Nomad clients.
+
+```hcl
+keyring [TYPE] {
+  name   = "example"
+  active = true
+}
+```
+
+The default `keyring` configuration is as follows:
+
+```hcl
+keyring "aead" {
+  active = true
+}
+```
+
+## `keyring` Parameters
+
+All `keyring` blocks support the following parameters.
+
+- `name` `(string: "")` - A unique identifier for the `keyring` block, used to
+  disambiguate when there are multiple blocks of the same type.
+
+- `active` `(bool: false)` - Indicates which block to use for encrypting
+  keys. For existing servers, changing which block is `active` only impacts new
+  keys created by a [key rotation][]. Existing keys are encrypted with the
+  previous `active` block, so those blocks should not be removed from the
+  configuration until they have been garbage collected and the keys have been
+  removed from the keystore. In Nomad Community Edition, only a single keyring
+  can be `active` at a time.
+
+## Migrating Keyrings
+
+To migrate to a new keyring, add the new `keyring` block to the servers with
+`active=true`, and restart the servers. The server starts using the new keyring
+wrapper when the current key is rotated either periodically or via the [`nomad
+operator root keyring rotate`][keyring_rotate_cmd] command.
+
+Adding or removing a keyring requires restarting the Nomad server. You should
+not remove a keyring until all keys it wraps have been garbage collected. You
+can examine the contents of the `keystore` directory found in the Nomad server's
+data directory and compare this against the output of [`nomad operator root
+keyring list`][keyring_list_cmd].
+
+## High Availability
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Enterprise.
+</EnterpriseAlert>
+
+Keyring high availability provides the means to configure multiple active
+`keyring` blocks, in order to have resilience against an outage of an external
+KMS. When there are multiple `keyring` blocks with `active = true`, Nomad
+Enterprise encrypts each key it creates in all the active KMS providers. On
+startup, Nomad tries each KMS provider in order until it finds a provider that
+can decrypt each key.
+
+In this example high availability configuration, both `keyring` blocks use the
+`"awskms"` provider, but each block uses a different KMS key in a different AWS
+region.
+
+```hcl
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-1"
+  region     = "us-east-1"
+  kms_key_id = "arn:aws:kms:us-east-1:000000000000:key/7d23633a-4464-11ef-a273-abd12example"
+}
+
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-2"
+  region     = "us-east-2"
+  kms_key_id = "alias/nomad-keyring-us-east-2"
+}
+```
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[Key Management]: /nomad/docs/operations/key-management
+[key rotation]: /nomad/docs/operations/key-management#key-rotation
+[keyring_rotate_cmd]: /nomad/docs/commands/operator/root/keyring-rotate
+[keyring_list_cmd]: /nomad/docs/commands/operator/root/keyring-list
diff --git a/content/nomad/v1.8.x/content/docs/configuration/keyring/transit.mdx b/content/nomad/v1.8.x/content/docs/configuration/keyring/transit.mdx
new file mode 100644
index 0000000000..05bb1a0a9a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/keyring/transit.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: Vault Transit - Keyring - Configuration
+description: |-
+  The Transit keyring configures Nomad to use Vault's Transit Secret Engine as
+  the key material wrapping mechanism.
+---
+
+# `transit` keyring
+
+The Vault transit keyring configures Nomad to use Vault's Transit Secret Engine
+to wrap its keyring. This example shows configuring Vault Transit through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "transit" {
+
+  active = true
+  name   = "example"
+
+  # fields specific to transit
+  address            = "https://vault:8200"
+  token              = "s.Qf1s5zigZ4OX6akYjQXJC1jY"
+  disable_renewal    = "false"
+
+  # Key configuration
+  key_name           = "transit_key_name"
+  mount_path         = "transit/"
+  namespace          = "ns1/"
+
+  # TLS Configuration
+  tls_ca_cert        = "/etc/vault/ca_cert.pem"
+  tls_client_cert    = "/etc/vault/client_cert.pem"
+  tls_client_key     = "/etc/vault/ca_cert.pem"
+  tls_server_name    = "vault"
+  tls_skip_verify    = "false"
+}
+```
+
+## `transit` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `key_name` `(string: <required>)`: The transit key to use for encryption and
+  decryption.
+
+- `key_id_prefix` `(string: "")`: An optional string to add to the key id of
+  values wrapped by this transit keyring. This can help disambiguate between two
+  transit keyring.
+
+- `mount_path` `(string: <required>)`: The mount path to the transit secret
+  engine.
+
+- `disable_renewal` `(string: "false")`: Disables the automatic renewal of the
+  token in case the lifecycle of the token is managed with some other mechanism
+  outside of Vault, such as Vault Agent.
+
+Set the following parameters in the `keyring` block. If not set here, Nomad uses
+the values set in the server's [`vault`][vault_config] block. You must set
+required fields either here or the `vault` block.
+
+- `address` `(string: <required>)`: The full address to the Vault cluster.
+  Alternately specify via the `VAULT_ADDR` environment variable.
+
+- `token` `(string: <required>)`: The Vault token to use. Alternately specify
+  via the `VAULT_TOKEN` environment variable.
+
+- `namespace` `(string: "")`: The namespace path to the transit secret engine.
+   Alternately specify via the `VAULT_NAMESPACE` environment variable.
+
+- `tls_ca_cert` `(string: "")`: Specifies the path to the CA certificate file
+  used for communication with the Vault server. Alternately specify via the
+  `VAULT_CACERT` environment variable.
+
+- `tls_client_cert` `(string: "")`: Specifies the path to the client certificate
+  for communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_CERT` environment variable.
+
+- `tls_client_key` `(string: "")`: Specifies the path to the private key for
+  communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_KEY` environment variable.
+
+- `tls_server_name` `(string: "")`: Name to use as the SNI host when connecting
+  to the Vault server via TLS. Alternately specify via the
+  `VAULT_TLS_SERVER_NAME` environment variable.
+
+- `tls_skip_verify` `(bool: "false")`: Disable verification of TLS certificates.
+  Using this option is highly discouraged and decreases the security of data
+  transmissions to and from the Vault server. Alternately specify via the
+  `VAULT_SKIP_VERIFY` environment variable.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file lets you to pass in `VAULT_TOKEN`
+as part of the keyring's parameters, we strongly recommended that you set these
+values via environment variables.
+
+The Vault authentication token needs the following permissions on the transit
+key:
+
+```hcl
+path "<mount path>/encrypt/<key name>" {
+  capabilities = ["update"]
+}
+
+path "<mount path>/decrypt/<key name>" {
+  capabilities = ["update"]
+}
+```
+
+Other considerations for the token used:
+* It should probably be an [orphan token][], otherwise when the parent token
+  expires or gets revoked the keyring breaks.
+* Consider making it a [periodic token][] and not setting an explicit max TTL,
+  otherwise at some point it ceases to be renewable.
+
+## Key rotation
+
+This keyring supports key rotation using the Transit Secret Engine's key
+rotation endpoints. Refer to [Vault docs][rotate_doc]. Old keys must not be
+disabled or deleted and are used to decrypt older data.
+
+[orphan token]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens
+[periodic token]: /vault/docs/concepts/tokens#periodic-tokens
+[rotate_doc]: /vault/api-docs/secret/transit#rotate-key
+[vault_config]: https://developer.hashicorp.com/nomad/docs/configuration/vault
diff --git a/content/nomad/v1.8.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.8.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..92fa1842fb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: plugin Block - Agent Configuration
+description: The "plugin" block is used to configure a Nomad plugin.
+---
+
+# `plugin` Block
+
+<Placement groups={['plugin']} />
+
+The `plugin` block is used to configure plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.8.x/content/docs/configuration/reporting.mdx b/content/nomad/v1.8.x/content/docs/configuration/reporting.mdx
new file mode 100644
index 0000000000..f89c6013f5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/reporting.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: reporting Block - Agent Configuration
+description: >-
+  The "reporting" block configures the Nomad agents automated license
+  utilization reporting.
+---
+
+# `reporting` Block
+
+<Placement groups={['reporting']} />
+
+The `reporting` block configures the Nomad agents automated license utilization
+reporting. This is an Enterprise-only feature and the configuration applies to
+agents running with [server mode enabled][server_mode_enabled].
+
+For more information about automated license utilization reporting, please see the
+[guide][automated_license_utilization_reporting].
+
+```hcl
+reporting {
+    license {
+      enabled = true
+    }
+}
+```
+
+## `reporting` Parameters
+
+- `license` <code>([license](#license-block): default)</code> - Configures
+  automated license utilization reporting.
+
+## `license` Block
+
+- `enabled` `(bool: true)` - Specifies whether automated license utilization
+  reporting should be enabled and run.
+
+[server_mode_enabled]: /nomad/docs/configuration/server#enabled
+[automated_license_utilization_reporting]: /nomad/docs/enterprise/license/utilization-reporting
diff --git a/content/nomad/v1.8.x/content/docs/configuration/search.mdx b/content/nomad/v1.8.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..dacdf56c5f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/search.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: search Block - Agent Configuration
+sidebar_title: search
+description: >-
+  The "search" block specifies configuration for the search API provided
+  by the Nomad servers.
+---
+
+# `search` Block
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+The `search` block specifies configuration for the search API provided by the
+Nomad servers.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.8.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.8.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..85085ab869
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: sentinel Block - Agent Configuration
+description: >-
+  The "sentinel" block configures the Nomad agent for Sentinel policies and
+  tune various parameters.
+---
+
+# `sentinel` Block
+
+<Placement groups={['sentinel']} />
+
+The `sentinel` block configures the Sentinel policy engine and tunes various parameters.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
diff --git a/content/nomad/v1.8.x/content/docs/configuration/server.mdx b/content/nomad/v1.8.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..a1a4fa113d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/server.mdx
@@ -0,0 +1,523 @@
+---
+layout: docs
+page_title: server Block - Agent Configuration
+description: |-
+  The "server" block configures the Nomad agent to operate in server mode to
+  participate in scheduling decisions, register with service discovery, handle
+  join failures, and more.
+---
+
+# `server` Block
+
+<Placement groups={['server']} />
+
+The `server` block configures the Nomad agent to operate in server mode to
+participate in scheduling decisions, register with service discovery, handle
+join failures, and more.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens. Non-authoritative regions will replicate from
+  the authoritative to act as a mirror. By default, the local region is assumed
+  to be authoritative. Setting `authoritative_region` assumes that ACLs have
+  been bootstrapped in the authoritative region. See [Configure for multiple
+  regions][] in the ACLs tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. See the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m".
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]:
+  nil)</code> - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or
+  value is updated through the [API endpoint][update-scheduler-config]. See [the
+  example section](#configuring-scheduler-config) for more details
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". See [Client Heartbeats](#client-heartbeats) below for details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". See [Client
+  Heartbeats](#client-heartbeats) below for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients
+  must heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". See [Client Heartbeats](#client-heartbeats) below
+  for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. See [Client Heartbeats](#client-heartbeats)
+  below for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described below. Lower values are used to tighten timing and
+  increase sensitivity while higher values relax timings and reduce sensitivity.
+  Tuning this affects the time it takes Nomad to detect leader failures and to
+  perform leader elections, at the expense of requiring more network and CPU
+  resources for better performance. The maximum allowed value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key from the [JWKS URL][] before
+  it is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. See the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, see the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+- `oidc_issuer` `(string: "")` - Specifies the Issuer URL for [Workload
+    Identity][wi] JWTs. For example, `"https://nomad.example.com"`. If set the
+    `/.well-known/openid-configuration` HTTP endpoint is enabled for third
+    parties to discover Nomad's OIDC configuration.  Once set `oidc_issuer`
+    *cannot be changed* without invalidating Workload Identities that have the
+    old issuer claim. For this reason it is suggested to set `oidc_issuer` to a
+    proxy in front of Nomad's HTTP API to ensure a stable DNS name can be used
+    instead of a potentially ephemeral Nomad server IP.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. See the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, please see the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`disconnect.lost_after`][disconnect.lost_after] is set)
+and rescheduled.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer a `down` Client's workload will
+  take to be rescheduled.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  rescheduled.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO (see below)       |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and reschedules their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator gossip keyring generate`]: /nomad/docs/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[disconnect.lost_after]: /nomad/docs/job-specification/disconnect#lost_after
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[wi]: /nomad/docs/concepts/workload-identity
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[JWKS URL]: /nomad/api-docs/operator/keyring#list-active-public-keys
diff --git a/content/nomad/v1.8.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.8.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..74f4dbb2f2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,298 @@
+---
+layout: docs
+page_title: server_join Block - Agent Configuration
+description: >-
+  The "server_join" block specifies how the Nomad agent will discover and
+  connect to Nomad servers.
+---
+
+# `server_join` Block
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+The `server_join` block specifies how the Nomad agent will discover and connect
+to Nomad servers.
+
+```hcl
+server_join {
+  retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max      = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of Nomad server
+  addresses and [Cloud Auto-join](#cloud-auto-join) configurations that are
+  joined as cluster members. This is similar to [`start_join`](#start_join),
+  but join attempts are retried up to [retry_max](#retry_max) times.
+  Further, `retry_join` is available to both Nomad servers and clients, while
+  `start_join` is only defined for Nomad servers. This is useful for cases where
+  we know the address will become available eventually. Use `retry_join` with an
+  array as a replacement for `start_join`, **do not use both options**.
+
+  Server addresses must conform to the [server address format](#server-address-format).
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Auto-join configurations must conform to the [Cloud Auto-join format](#cloud-auto-join).
+
+  Cloud-Auto join using `go-discover` to join an AWS EC2 cluster.
+
+  ```hcl
+  server_join {
+    retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Cloud-Auto join using `go-netaddrs` to join a Hetzner cluster of servers
+  labeled with `nomad-server=true` using the `hcloud` CLI.
+
+  ```hcl
+  server_join {
+    retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+  }
+  ```
+
+  Server addresses and Cloud Auto-join configurations may be used together.
+  This is a mixed configuration containing a server address and Cloud Auto-join
+  configuration.
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "provider=aws tag_key=..." ]
+  }
+  ```
+
+  See [server address format](#server-address-format) for more information
+  about expected server address formats and [Cloud Auto-join](#cloud-auto-join)
+  for more information on expected Cloud Auto-join formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+`retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud provider metadata. See [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+`retry_join`'s Cloud Auto-join allows Nomad to automatically discover cluster
+server addresses using cloud provider metadata. Cloud Auto-join allows both
+[go-discover](https://github.com/hashicorp/go-discover) and
+[go-netaddrs](https://github.com/hashicorp/go-netaddrs) formats.
+
+Configurations prefixed with `provider=` use `go-discover` whereas
+configurations prefixed with `exec=` use `go-netaddrs`. For cloud providers not
+supported by `go-discover`, use `go-netaddrs`.
+
+### `go-discover` Configurations
+
+`go-discover` configurations are prefixed with `provider=`.
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers, see further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+#### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication (see below for more information about authenticating).
+- `secret_access_key` (optional) - the AWS secret access key for authentication (see below for more information about authenticating).
+
+##### Authentication &amp; Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+#### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+#### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. See below for more information.
+
+##### Authentication &amp; Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
+
+
+### `go-netaddrs` Configurations
+
+`go-netaddrs` configurations are prefixed with `exec=`.
+
+What follows the `exec=` prefix may be any executable program and its arguments.
+Commands run by `go-netaddrs` must return a list of space-delimited IPv4 or IPv6
+addresses and exit with code `0` on success and non-zero on failure.
+
+You can refer to the executable by its absolute file system path, or by
+the executable's name if it can be found on the Nomad agent's PATH. See
+[executables in the current directory](https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory)
+for more details on the lookup behavior.
+
+Example `go-netaddrs` configuration.
+
+```hcl
+server_join {
+  retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+}
+```
+
+Here, `hcloud`'s newline-delimited output has been re-formatted as space-
+delimited by piping its output into `tr`.
+
+Output of an example `go-netaddrs` executable
+
+```
+"1.1.1.1 2.2.2.2"
+```
+
+Visit [go-netaddrs](https://github.com/hashicorp/go-netaddrs) for more
+information on go-netaddrs configuration.
diff --git a/content/nomad/v1.8.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.8.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..071fdc3caf
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,207 @@
+---
+layout: docs
+page_title: telemetry Block - Agent Configuration
+description: |-
+  The "telemetry" block configures Nomad's publication of metrics and telemetry
+  to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures Nomad's publication of metrics and telemetry
+to third-party systems.
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for
+`telemetry` block. To understand the architecture and metrics themselves,
+please see the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `in_memory_collection_interval` `(duration: 10s)` Configures the in-memory
+  sink collection interval. This sink is always configured and backs the JSON
+  metrics API endpoint. This option is particularly useful for debugging or
+  development purposes, where aggressive collection is required.
+
+- `in_memory_retention_period` `(duration: 1m)` Configures the in-memory sink
+  retention period. This sink is always configured and backs the JSON metrics
+  API endpoint. This option is particularly useful for debugging or development
+  purposes.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+- `disable_quota_utilization_metrics` `(bool: false)` - Specifies if Nomad
+  should publish metrics about quota utilization (a Nomad Enterprise feature).
+  Since each quota utilization check requires a relatively expensive check
+  against Nomad's state store, users with many namespaces and many quotas may
+  want to disable these metrics.
+
+### `statsite`
+
+These `telemetry` parameters apply to
+[statsite](https://github.com/armon/statsite).
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to
+[statsd](https://github.com/etsy/statsd).
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to
+[DataDog statsd](https://github.com/DataDog/datadog-agent).
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus](https://prometheus.io).
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus`
+
+These `telemetry` parameters apply to
+[Circonus](http://circonus.com/).
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
diff --git a/content/nomad/v1.8.x/content/docs/configuration/tls.mdx b/content/nomad/v1.8.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..8d88678fa6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: tls Block - Agent Configuration
+description: |-
+  The "tls" block configures Nomad's TLS communication via HTTP and RPC to
+  enforce secure cluster communication between servers and clients.
+---
+
+# `tls` Block
+
+<Placement groups={['tls']} />
+
+The `tls` block configures Nomad's TLS communication via HTTP and RPC to enforce
+secure cluster communication between servers, clients, and between. Note that in
+most cases, this is mutual TLS (mTLS) where both ends of the connection
+authenticate each other. The Nomad documentation will typically use "TLS" to
+refer to this communication except when it is potentially ambiguous between TLS
+and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for
+`tls` block. To understand how to setup the certificates themselves, please see
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+  Nomad does not accept explicit ciphersuite configuration when for TLS 1.3
+  because the Go team has already designated a select set of ciphers that align
+  with the broadly-accepted Mozilla Security/Server Side TLS guidance for
+  [modern TLS configuration][modern-tls].
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12", "tls13".
+
+- `tls_prefer_server_cipher_suites` `(bool: false)` - Specifies whether
+  TLS connections should prefer the server's ciphersuites over the client's.
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
+[modern-tls]: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
diff --git a/content/nomad/v1.8.x/content/docs/configuration/ui.mdx b/content/nomad/v1.8.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..a51c912582
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: ui Block - Agent Configuration
+description: |-
+  The "ui" block configures the Nomad agent's web UI.
+
+---
+
+# `ui` Block
+
+<Placement groups={['ui']} />
+
+The `ui` block configures the Nomad agent's [web UI].
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI will default to a black background. HEX values  
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI will default to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.8.x/content/docs/configuration/vault.mdx b/content/nomad/v1.8.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..60a25739d0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,346 @@
+---
+layout: docs
+page_title: vault Block - Agent Configuration
+description: |-
+  The "vault" block configures Nomad's integration with HashiCorp's Vault.
+  When configured, Nomad can create and distribute Vault tokens to tasks
+  automatically.
+---
+
+# `vault` Block
+
+<Placement groups={['vault']} />
+
+The `vault` block configures Nomad's integration with [HashiCorp's
+Vault][vault]. When configured, tasks can use [workload
+identities][workload_id] to receive Vault ACL tokens automatically.
+
+Alternatively, Nomad servers may be configured with a high-privileged Vault
+token that is used to derive fine-grained tokens for tasks. Refer to
+[Token-based Authentication](#token-based-authentication) for configuration
+details. This workflow is deprecated and will be removed in a future version of
+Nomad. Using using workload identities is strongly recommended as it is easier
+to manage and more secure.
+
+Refer to the [Nomad and Vault Integration][nomad-vault] page for more
+information about the Vault integration.
+
+```hcl
+vault {
+  enabled = true
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+
+    extra_claims {
+      unique_id = "${job.region}:${job.namespace}:${job.id}"
+    }
+  }
+}
+```
+
+In Nomad Enterprise, you may specify multiple `vault` blocks to configure access
+to multiple Vault clusters. Each Vault cluster must have a different value for
+the [`name`](#name) field.
+
+## `vault` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+The placement also depends on the authentication strategy used. This section
+describes the parameter organization for workload identity authentication.
+Refer to the [Token-based Authentication](#token-based-authentication) section
+if using Vault tokens directly.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`vault.cluster`][] field. In Nomad Community Edition, only
+  the `"default"` cluster will be used, so this field should be omitted.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+
+  When using workload identities this field defines the role used to derive
+  task tokens when the job does not define a value for
+  [`vault.role`][jobspec_vault_role]. If empty, the default Vault cluster role
+  is used.
+
+  For token-based authentication, the Nomad servers derive tokens
+  using this role. The token given to Nomad does not have to be created from
+  this role but must have `update` capability on
+  `auth/token/create/<create_from_role>` path in Vault. If this value is unset
+  and the token is created from a role, the value is defaulted to the role the
+  token is from.
+
+  -> **Note:** This used to be a server-only field, but it is client-only when
+  using workload identities. It should be set in both while transitioning from
+  token-based authentication to workload identities.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`] set to `true`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `jwt_auth_backend_path` - `(string: "jwt-nomad")` - Specifies the mount
+  [path][vault_auth_enable_path] of the JWT authentication method to be used to
+  login with workload identity JWTs.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `default_identity` <code>([Identity](#default_identity-parameters): nil)</code> -
+  Specifies the default workload identity configuration to use when a task with
+  a `vault` block does not specify an [`identity`][jobspec_identity] block
+  named `vault_<name>`, where `<name>` matches the value of this `vault` block
+  [`name`](#name) parameter. Setting a default identity causes the value of
+  `allow_unauthenticated` to be ignored.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Visit the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  to see how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+### `default_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`bound_audiences`][vault_bound_aud]
+  configuration in the Vault JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in
+  the task's `NOMAD_TOKEN_vault` environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_vault.jwt`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+- `extra_claims` `(map[string]string: optional)` - A set of key-value pairs that
+  will be provided as extra identity claims for workloads. You can use the keys
+  as [user claims in Vault role configurations][vault-jwt-user-claim]. The
+  values are interpolated. For example, if you include the extra claim
+  `unique_id = "${job.region}:${job.namespace}:${job.id}"`, you could set the
+  user claim field to `/extra_claims/unique_id` to map that identifier to an
+  entity alias. The available attributes for interpolation are:
+
+  - `${job.region}` - The region where the job is running.
+  - `${job.namespace}` - The job's namespace.
+  - `${job.id}` - The job's ID.
+  - `${job.node_pool}` - The node pool where the allocation is running.
+  - `${group.name}` - The task group name of the task using Vault.
+  - `${alloc.id}` - The allocation's ID.
+  - `${task.name}` - The name of the task using Vault.
+  - `${node.id}` - The ID of the node where the allocation is running.
+  - `${node.datacenter}` - The datacenter of the node where the allocation is running.
+  - `${node.pool}` - The node pool of the node where the allocation is running.
+  - `${node.class` - The class of the node where the allocation is running.
+  - `${vault.cluster}` - The Vault cluster name.
+  - `${vault.namespace}` - The Vault namespace.
+  - `${vault.role}` - The Vault role.
+
+### Token-based Authentication
+
+~> **Warning:** The token-based authentication flow is deprecated and will be
+  removed in a future release. It is highly recommended to migrate and use the
+  workload identity flow instead.
+
+When using token-based authentication the `vault` block parameters should be
+defined as below.
+
+#### Parameters for Nomad Clients and Servers
+
+- [`address`](#address)
+- [`ca_file`](#ca_file)
+- [`ca_path`](#ca_path)
+- [`cert_file`](#cert_file)
+- [`enabled`](#enabled)
+- [`key_file`](#key_file)
+- [`name`](#name)
+- [`namespace`](#namespace)
+- [`tls_server_name`](#tls_server_name)
+- [`tls_skip_verify`](#tls_skip_verify)
+
+#### Parameters for Nomad Servers
+
+- [`allow_unauthenticated`](#allow_unauthenticated)
+- [`create_from_role`](#create_from_role)
+- [`token`](#token)
+- [`task_token_ttl`](#task_token_ttl)
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows a Vault configuration for a Nomad server using the workload
+identity authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled = true
+
+  # Only needed in servers when transioning from the token-based flow to
+  # workload identities.
+  create_from_role = "nomad-cluster"
+
+  # Provide a default workload identity configuration so jobs don't need to
+  # specify one.
+  default_identity {
+    aud  = ["vault.io"]
+    env  = false
+    file = true
+    ttl  = "1h"
+  }
+}
+```
+
+This example shows a Vault configuration for a Nomad server using the
+deprecated token-based authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The below is the default address if
+  # unspecified.
+  address = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows a Vault configuration for a Nomad client.
+
+```hcl
+client {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  address   = "https://vault.service.consul:8200"
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+}
+```
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[jobspec_identity]: /nomad/docs/job-specification/identity
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault_bound_aud]: /vault/api-docs/auth/jwt#bound_audiences
+[vault_auth_enable_path]: /vault/docs/commands/auth/enable#path
+[workload_id]: /nomad/docs/concepts/workload-identity
+[vault-jwt-user-claim]: /vault/api-docs/auth/jwt#user_claim
diff --git a/content/nomad/v1.8.x/content/docs/devices/index.mdx b/content/nomad/v1.8.x/content/docs/devices/index.mdx
new file mode 100644
index 0000000000..28c5e58893
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/devices/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Device Plugins
+description: Device Plugins are used to expose devices to tasks in Nomad.
+---
+
+# Device Plugins
+
+Device plugins are used to detect and make devices available to tasks in
+Nomad. Devices are physical hardware that exists on a client node such as a
+GPU or an FPGA. By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+The list of supported device plugins is provided on the left of this page.
+Each device plugin documents its configuration and installation requirements,
+the attributes it fingerprints, and the environment variables it exposes to
+tasks.
diff --git a/content/nomad/v1.8.x/content/docs/drivers/docker.mdx b/content/nomad/v1.8.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..29bb6f7fff
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1249 @@
+---
+layout: docs
+page_title: 'Drivers: Docker'
+description: The Docker task driver is used to run Docker based tasks.
+---
+
+# Docker Driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `container_exists_attempts` - (Optional) A number of attempts to be made to
+  purge a container if during task creation Nomad encounters an existing one in
+  non-running state for the same task. Defaults to `5`.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) Specifies [Windows isolation][] mode: `"hyperv"` or
+  `"process"`. Defaults to `"hyperv"`.
+
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. Note that `"all"` is not permitted here if the `allow_caps`
+  field in the driver configuration doesn't also allow all capabilities. For
+  example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+Nomad clients manage a cpuset cgroup for each task to reserve or share CPU
+[cores][]. In order for Nomad to be compatible with Docker's own cgroups
+management, it must write to cgroups owned by Docker, which requires running as
+root. If Nomad is not running as root, CPU isolation and NUMA-aware scheduling
+will not function correctly for workloads with `resources.cores`, including
+workloads using task drivers other than `docker` on the same host.
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `registry.k8s.io/pause-<goarch>:3.3`. The image will only be pulled from the
+  container registry if its tag is `latest` or the image doesn't yet exist
+  locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+- `windows_allow_insecure_container_admin` - Indicates that on windows, docker
+  checks the `task.user` field or, if unset, the container image manifest after
+  pulling the container, to see if it's running as `ContainerAdmin`. If so, exits
+  with an error unless the task config has `privileged=true`. Defaults to `false`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad has a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.8.x/content/docs/drivers/exec.mdx b/content/nomad/v1.8.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..a1e46c9104
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,283 @@
+---
+layout: docs
+page_title: 'Drivers: Exec'
+description: The Exec task driver runs binaries using OS isolation primitives.
+---
+
+# Isolated Fork/Exec Driver
+
+Name: `exec`
+
+The `exec` driver is used to simply execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.8.x/content/docs/drivers/index.mdx b/content/nomad/v1.8.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..894b86210d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Task drivers are pluggable. This gives users the flexibility to introduce their
+own drivers without having to recompile Nomad. You can view the [plugin block][plugin]
+documentation for examples on how to use the `plugin` block in Nomad's client configuration.
+See [docker][docker_plugin] for a more detailed and specific example.
+Keep in mind that even though all built-in drivers are plugins, Nomad
+remains a single binary and maintains backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.8.x/content/docs/drivers/java.mdx b/content/nomad/v1.8.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..88066fa787
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/java.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: 'Drivers: Java'
+description: The Java task driver is used to run Jars using the JVM.
+---
+
+# Java Driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.8.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.8.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..4a86628ff0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: 'Drivers: QEMU'
+description: The QEMU task driver is used to run virtual machines using QEMU/KVM.
+---
+
+# QEMU Driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.8.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.8.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..b69807186f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: 'Drivers: Raw Exec'
+description: The Raw Exec task driver simply fork/execs and provides no isolation.
+---
+
+# Raw Fork/Exec Driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `cgroup_v1_override` - (Optional) A map of controller names to paths. The
+  task will be added to these cgroups. The task will fail if these cgroups do
+  not exist. **WARNING:** May conflict with other Nomad driver's cgroups and
+  have unintended side effects.
+
+- `cgroup_v2_override` - (Optional) Adds the task to a unified cgroup path.
+  Paths may be relative to the cgroupfs root or absolute.  **WARNING:** May
+  conflict with other Nomad driver's cgroups and have unintended side
+  effects.
+
+~> The `task.user` field cannot be set on a Task using the `raw_exec` driver if
+the Nomad client has been hardened according to the [production][hardening] guide.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no filesystem isolation.
+
+If the launched process creates a new process group, it is possible that
+Nomad will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to
+manage the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, and the cgroup system is mounted.
+
+If the cluster is configured with memory oversubscription enabled, a task using
+the `raw_exec` driver can be configured to have no maximum memory limit by
+setting `memory_max = -1`.
+
+```hcl
+resources {
+  cpu        = 500
+  memory     = 128
+  memory_max = -1 # no limit
+}
+```
+
+
+[hardening]: /nomad/docs/install/production/requirements#user-permissions
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.8.x/content/docs/ecosystem.mdx b/content/nomad/v1.8.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..acc28cef74
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/ecosystem.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+- [LXC](/nomad/plugins/drivers/community/lxc)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.8.x/content/docs/enterprise/index.mdx b/content/nomad/v1.8.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..dc2817aa56
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  to Nomad.
+
+  Features include Resource Quotas, Sentinel Policies, and Advanced Autopilot.
+---
+
+# Nomad Enterprise
+
+Nomad Enterprise adds collaboration, operational, and governance capabilities
+to Nomad. Nomad Enterprise is available as a base Platform package with an
+optional Governance & Policy add-on module.
+
+Please navigate the sub-sections for more information about each package and
+its features in detail.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Long Term Support (LTS) Releases
+
+Nomad Enterprise initiated the Long-Term Support (LTS) release program with
+Nomad 1.8. Going forward, the first major release of each calendar year will be
+an LTS release.
+
+LTS releases have the following benefits for Nomad operators:
+
+- **Extended maintenance:** Two years of critical fixes provided through minor
+releases 
+- **Efficient upgrades:** Support for direct upgrades from one LTS release
+to the next, reducing major-version upgrade risk and improving operational
+efficiency.
+
+LTS releases reduce operational overhead and risk by letting organizations
+receive critical fixes in minor releases without having to upgrade their major
+version more than once a year. Once you’ve upgraded to Nomad Enterprise 1.8,
+you will be running on a maintained LTS release that will allow you to easily
+upgrade to the next LTS major release when it's available. For more
+information, refer to HashiCorp’s multi-product LTS statement.
+
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+### Multiple Vault and Consul Clusters
+
+Nomad Enteprise allows sepcifying multiple integrations for Consul and Vault in
+the [vault](/nomad/docs/configuration/vault) and
+[consul](/nomad/docs/configuration/consul) portions of the Nomad agent
+configuration. After the agents are configured, Nomad jobspec writers can pick
+which Consul or Vault cluster to use in their job. Nomad administrators may
+also set default clusters for each in Nomad namespace configuration, as well as
+deny access to certain clusters by namespace.
+
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define quota specifications and apply them to namespaces. When a quota is
+attached to a namespace, the jobs within the namespace may not consume more
+resources than the quota specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/tutorials/governance-and-policy/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/enterprise/sentinel
diff --git a/content/nomad/v1.8.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.8.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..d393f419a2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Frequently Asked Questions (FAQ)
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/docs/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/docs/commands/license/inspect
diff --git a/content/nomad/v1.8.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.8.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..94ea48d421
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn about how Nomad Enterprise licensing works.
+---
+
+## Nomad Enterprise Licensing
+
+Licensing capabilities were added to Nomad Enterprise v0.12.0. Each server in
+the cluster must have a license to start. Nomad Enterprise can be downloaded from
+the [releases site].
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo of Nomad Enterprise
+or [here](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/docs/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/docs/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+~> **Note:** An Enterprise license [tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) is available to help you install the license on the server.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.8.x/content/docs/enterprise/license/utilization-reporting.mdx b/content/nomad/v1.8.x/content/docs/enterprise/license/utilization-reporting.mdx
new file mode 100644
index 0000000000..1fa42c06bd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/enterprise/license/utilization-reporting.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: Automated license utilization reporting
+description: >-
+  Learn what data HashiCorp collects to meter Enterprise license utilization. Enable or disable reporting. Review sample payloads and logs.
+---
+
+# Automated license utilization reporting
+
+Automated license utilization reporting sends license utilization data to HashiCorp without requiring you 
+to manually collect and report them. It also lets you review your license usage with the monitoring 
+solution you already use (for example Splunk, Datadog, or others) so you can optimize and manage your 
+deployments. Use these reports to understand how much more you can deploy under your current contract, 
+protect against overutilization, and budget for predicted consumption.  
+
+Automated reporting shares the minimum data required to validate license utilization as defined in our 
+contracts. They consist of mostly computed metrics and will never contain Personal Identifiable Information 
+(PII) or other sensitive information. Automated reporting shares the data with HashiCorp using a secure, 
+unidirectional HTTPS API and makes an auditable record in the product logs each time it submits a report. 
+The reporting process is GDPR compliant and submits reports roughly once every 24 hours.
+
+## Enable automated reporting
+
+To enable automated reporting, you need to make sure that outbound network traffic is configured correctly 
+and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or 
+network settings are not in place, automated reporting will not work. 
+
+### 1. Allow outbound HTTPS traffic on port 443
+
+Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by 
+allow-listing the following IP addresses:
+
+- 100.20.70.12
+- 35.166.5.222
+- 23.95.85.111
+- 44.215.244.1
+
+### 2. Upgrade
+
+Upgrade to a release that supports license utilization reporting. These releases include:
+- [Nomad v1.7.0](/nomad/downloads) and later
+
+### 3. Check logs
+
+Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product 
+logs for records that the data sent successfully.
+
+Instructions on how to check logs. 
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: recording audit record
+[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
+[DEBUG] completed recording audit record
+[DEBUG] core.reporting: export finished successfully
+```
+
+If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an 
+error. 
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: error status code received: statusCode=403
+```
+
+In this case, reconfigure your network to allow egress and check back in 24 hours. 
+
+## Opt out
+
+If your installation is air-gapped or you want to manually collect and report on the same license 
+utilization metrics, you can opt-out of automated reporting. 
+
+Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that 
+you also opt out from sending license utilization metrics. Customers who opt out of automated reporting will 
+still be required to manually collect and send license utilization metrics to HashiCorp. 
+
+If you are considering opting out because you’re worried about the data, we strongly recommend that you 
+review the [example payloads](#example-payloads) before opting out. If you have concerns with any of the 
+automatically-reported data please bring them to your account manager. 
+
+You have two options to opt out of automated reporting: HCL configuration (recommended) and Environment 
+variable (requires restart).
+
+Opting out in your product’s configuration file doesn’t require a system restart, and is the method we 
+recommend. Add the following block to your `server.hcl` file.
+
+```hcl
+reporting {
+	license {
+		enabled = false
+    }
+}
+```
+
+If you need to, you can also opt out using an environment variable, which will provide a startup message 
+confirming that you have disabled automated reporting. This option requires a system restart. 
+
+Set the following environment variable.
+
+```
+$ export OPTOUT_LICENSE_REPORTING=true
+```
+
+Now restart your system by following [these instructions](/nomad/docs/operations/nomad-agent). 
+
+Check your product logs roughly 24 hours after opting out to make sure that the system isn’t trying to send 
+reports.
+
+If your configuration file and environment variable differ, the environment variable setting will take 
+precedence.
+
+## Example payloads
+
+HashiCorp collects the following utilization data as JSON payloads:
+
+`billable.nodes` - Number of billable nodes in Nomad
+
+```json
+"metrics": {
+    "nomad.billable.nodes": {
+        "key": "nomad.billable.nodes",
+        "kind": "counter",
+        "mode": "write",
+        "value": 33
+    }
+}
+```
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/enterprise/sentinel.mdx b/content/nomad/v1.8.x/content/docs/enterprise/sentinel.mdx
new file mode 100644
index 0000000000..6ca332992a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/enterprise/sentinel.mdx
@@ -0,0 +1,93 @@
+---
+layout: docs
+page_title: Sentinel Policy Reference
+description: >-
+  Learn about Nomad Sentinel Policy Objects
+---
+
+## Sentinel
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+See the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`
+subcommands][]
+
+### Sentinel Policies
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  will always be non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-nomad-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+### Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+
+### Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+### Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+[Nomad Sentinel Tutorial]: /nomad/tutorials/governance-and-policy/sentinel
+[`nomad sentinel` sub-commands]: /nomad/docs/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L12991-L13020
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L5306-L5338
diff --git a/content/nomad/v1.8.x/content/docs/faq.mdx b/content/nomad/v1.8.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..a9c683b8b6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Frequently asked questions and answers for Nomad
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.8.x/content/docs/glossary.mdx b/content/nomad/v1.8.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..8c2035e7b7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Learn the definition of important Nomad concepts.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.8.x/content/docs/index.mdx b/content/nomad/v1.8.x/content/docs/index.mdx
new file mode 100644
index 0000000000..3296277979
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Welcome to the Nomad documentation. Nomad is a scheduler and workload
+  orchestrator. This documentation is a reference for all available features
+  and options of Nomad.
+---
+
+# Nomad Documentation
+
+Welcome to the Nomad documentation. Nomad is a scheduler and workload
+orchestrator. This documentation is a reference for all
+available features and options of Nomad. If you are just getting started with
+Nomad, please start with the [Getting Started collection][gs]
+instead.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.8.x/content/docs/install/index.mdx b/content/nomad/v1.8.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..7ac5f3dcf2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/install/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Install Nomad
+description: Learn how to install Nomad on Linux, Mac, and Windows.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/install/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Install dmidecode
+
+When running on a virtualized host such as Amazon EC2, Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions
+require installing the dmidecode package manually.
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+
+## Verify the Installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from Source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.8.x/content/docs/install/production/index.mdx b/content/nomad/v1.8.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..2d8e7350d4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/install/production/index.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: Installing Nomad for Production
+description: Learn how to install Nomad for Production.
+---
+
+# Installing Nomad for Production
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the Reference Architecture and Installation Guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify Hardware Requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Installing Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad Servers and Clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.8.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.8.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..559f3ab490
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: Requirements
+description: |-
+  Learn about Nomad client and server requirements such as memory and CPU
+  recommendations, network topologies, and more.
+---
+
+# Requirements
+
+## Resources (RAM, CPU, etc.)
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network Topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publically routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports Used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge Networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup Controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux Capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad Clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrat
diff --git a/content/nomad/v1.8.x/content/docs/install/quickstart.mdx b/content/nomad/v1.8.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..fb04b6eb39
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,106 @@
+---
+layout: docs
+page_title: Installing Nomad for QuickStart
+description: Learn how to install Nomad locally or in a sandbox.
+---
+
+# Quickstart
+
+This page lists multiple methods to installing Nomad locally or in a sandbox
+environment.
+
+These installations are designed to get you started with Nomad easily and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, please refer to the [Production Installation](/nomad/docs/install/production) guide here.
+
+<Tabs>
+<Tab heading="Interactive Online Environment">
+
+Experiment with Nomad in your browser via guides containing embedded interactive learning environments.
+
+- [Interactive Labs](/nomad/tutorials/interactive)
+
+</Tab>
+<Tab heading="Create a Cloud Lab">
+
+Install Nomad on the public cloud.
+
+- AWS
+
+  - [CloudFormation](https://aws.amazon.com/quickstart/architecture/nomad/)
+
+  - [Terraform](https://github.com/hashicorp/nomad/blob/master/terraform/aws/README.md)
+
+- Azure
+
+  - [Terraform](https://github.com/hashicorp/nomad/tree/master/terraform/azure)
+
+</Tab>
+<Tab heading="Try it Locally">
+
+## Install Nomad on your machine
+
+If you would like to try Nomad locally, you can install Nomad on your local
+machine using the same steps that you would for a production environments and
+run a single-node development instance using the `sudo nomad agent -dev` command
+
+[Installing Nomad][installing-binary]
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Run Nomad in Vagrant
+
+Alternatively, you can use a Vagrant to set up a development environment for Nomad.
+Vagrant is a tool for building and managing virtual machine environments.
+
+-> **Note**: To use the Vagrant environment, first install Vagrant following
+these [instructions](/vagrant/docs/installation). You will
+also need a virtualization tool, such as [VirtualBox][].
+
+You can download a Vagrantfile which can start a small Nomad cluster. First
+create a new directory for your Vagrant environment.
+
+```shell-session
+$ mkdir nomad-vagrant
+```
+
+Change into the directory you made with the previous command.
+
+```shell-session
+$ cd nomad-vagrant
+```
+
+Now you can get the Nomad installation configuration.
+
+```shell-session
+$ curl -O https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile
+```
+
+Now that you have created a new directory and downloaded the `Vagrantfile`
+you must create the virtual machine with the `vagrant up` command.
+
+```shell-session
+$ vagrant up
+```
+
+This takes a few minutes as the base Ubuntu box must be downloaded
+and provisioned with both Docker and Nomad. Once this completes, you should
+see this output.
+
+```plaintext
+Bringing machine 'default' up with 'virtualbox' provider...
+==> default: Importing base box 'bento/ubuntu-18.04'...
+...
+==> default: Running provisioner: docker...
+```
+
+At this point the Vagrant box is running and ready to go.
+
+</Tab>
+</Tabs>
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[vagrant-environment]: /nomad/tutorials/get-started/get-started-install#vagrant-setup-optional
+[virtualbox]: https://www.virtualbox.org/
diff --git a/content/nomad/v1.8.x/content/docs/install/windows-service.mdx b/content/nomad/v1.8.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..ca097ef2ca
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad as a Windows Service
+description: Discusses how to register and run Nomad as a native Windows service.
+---
+
+# Installing Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.8.x/content/docs/integrations/consul/acl.mdx b/content/nomad/v1.8.x/content/docs/integrations/consul/acl.mdx
new file mode 100644
index 0000000000..be98db04c4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/consul/acl.mdx
@@ -0,0 +1,450 @@
+---
+layout: docs
+page_title: Consul ACL
+description: Learn how to integrate Nomad with Consul when ACL is enabled.
+---
+
+# Consul ACL
+
+The [Consul ACL][consul_acls] system protects the cluster from unauthorized
+access. When enabled, both Consul and Nomad must be properly configured in
+order for their integrations to work.
+
+Nomad agents must be configured with their own Consul ACL token, and Consul
+must be configured to accept workload identities from tasks and services
+running in Nomad.
+
+## Nomad Agents
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task or service's [Workload
+Identity][nomad_wid] to authenticate to Consul and obtain an ACL token specific
+to the service or task. When using Nomad workload identities, you no longer
+need to pass in a Consul ACL token to submit a job.
+
+By default, Nomad does not generate workload identities for services, and tasks
+only receive an identity that can be used to access data from Nomad itself,
+such as for reading [Variables][] from a [`template`][] block. To access
+Consul, jobs must have additional workload identities defined as [`identity`][]
+blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure Nomad servers with the [`consul.service_identity`][] and
+[`consul.task_identity`][] agent configuration. Upon job registration, the
+Nomad servers update tasks that have a [`consul`][] or [`template`][] block and
+services that use the Consul service provider with these default identities.
+
+You can also specify identities for Consul directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Consul][jobspec_identity_consul] section of the `identity` block
+documentation for more information.
+
+### Configuring Consul Authentication
+
+You must configure Consul so it can receive, validate, and trust workload
+identities from Nomad. Since they are encoded as [JSON Web Tokens (JWTs)][jwt],
+you must create a [JWT ACL auth method][consul_jwt_auth_method]. The auth
+method is an endpoint that Nomad can use to exchange workload identities for
+Consul ACL tokens.
+
+Refer to Consul's [Auth Methods Overview][consul_auth_methods] documentation
+for more information.
+
+#### Consul Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Consul servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Consul is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `JWKSURL` address must be reachable by all Consul servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `JWKSURL` value.
+
+[![Consul Auth Method][img_consul_auth_method]][img_consul_auth_method]
+
+When an allocation that needs access to Consul starts, the Nomad client running
+it exchanges the Nomad workload identities for tasks and services for Consul
+ACL tokens.
+
+[![Consul JWT Login][img_consul_wid_acl_token]][img_consul_wid_acl_token]
+
+The auth method also defines the list of authorized audience values, which must
+have at least one match with the values defined in the Nomad workload identity
+[`aud`][] parameter. For security reasons, it is recommended to only define a
+single audience value.
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced as dynamic values in Consul ACL configuration. The auth method
+determines which of these claims are made available to the rest of the
+configuration.
+
+<CodeBlockConfig highlight="6-9" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### Consul Binding Rules
+
+Consul auth methods use [binding rules][consul_binding_rules] to determine the
+set of policies applied to the generated ACL token. Nomad workload identities
+can be used in Consul for two main purpose: registering services and retrieving
+configuration values and service addresses from Consul using `template` blocks
+in tasks. Each purpose requires tokens with different permissions so Nomad
+requires two binding rules.
+
+The first binding rule associates the Consul ACL token with a [service
+identity][consul_si], allowing the token to register and manage the lifecyle of
+a given service. This binding rule is only applied to Nomad workload identities
+for services because they are the only ones that have a `nomad_service` claim.
+
+```shell-session
+$ consul acl binding-rule create \
+    -method 'nomad-workloads' \
+    -bind-type 'service' \
+    -bind-name '${value.nomad_service}' \
+    -selector '"nomad_service" in value'
+```
+
+The [`-bind-name`][] flag restricts the token to only be able to modify
+services with the same name as the one defined in the Nomad workload identity
+claim. The [`-selector`][] flag ensures this binding rule only applies to
+workload identities for services.
+
+The second binding rule associates the Consul ACL token with an [ACL
+role][consul_acl_role], which is a collection of [ACL
+policies][consul_acl_policy] that define what the token is authorized to do.
+This binding rule is applied to Nomad workload identities for tasks to access
+information from Consul. The exact ACL policy rules will depend on the level of
+access required by the tasks (typically, accessing service addresses and KV with
+[`template`][] blocks).
+
+```shell-session
+$ consul acl binding-rule create \
+  -method 'nomad-workloads' \
+  -bind-type 'role' \
+  -bind-name 'nomad-tasks-${value.nomad_namespace}' \
+  -selector '"nomad_service" not in value'
+```
+
+The `-bind-name` flag defines which role is used for the token. It may
+reference claim values from the Nomad workload identity to apply different
+roles to different tasks. Similarly to the binding rule for services, the
+`-selector` flag ensures this binding rule only applies to workload identities
+for tasks since they don't have the `nomad_service` claim.
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Consul Auth Overview][img_consul_auth]][img_consul_auth]
+
+The [`consul.service_auth_method`][] and [`consul.task_auth_method`][]
+configuration define the auth method used by Nomad to retrieve Consul ACL
+tokens for services and tasks.
+
+By default, they follow the structure described above and use a single auth
+method for both, but it is possible to use two different auth methods, provided
+the resulting Consul ACL token from each have the expected service identity and
+role applied.
+
+#### Consul Namespace Rules <EnterpriseAlert inline />
+
+Consul Enterprise supports multiple namespaces and Nomad Enterprise allows jobs
+to use the [`consul.namespace`][] parameter to register services and read KV
+data from different Consul namespaces.
+
+In a multi-namespace environment, you should create the auth method and binding
+rules in the `default` namespace and configure the auth method with a set of
+[`NamespaceRules`][].
+
+```shell-session
+$ consul acl auth-method create \
+  -name 'nomad-workloads' \
+  -type 'jwt' \
+  -config '@auth-method.json' \
+  -namespace-rule-selector '"consul_namespace" in value' \
+  -namespace-rule-bind-namespace '${value.consul_namespace}'
+```
+
+Similarly to binding rules, namespace rules have a [`Selector`][] expression to
+determine when the rule should be applied and a [`BindNamespace`][] value that
+defines the namespace used.
+
+In Nomad Enterprise, workload identities for tasks and services placed within
+the scope of a `consul` block with a `namespace` value, have an additional
+claim called `consul_namespace` that represents the Consul namespace defined
+in Nomad for the workload.
+
+<CodeBlockConfig highlight="9-11" filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    consul {
+      namespace = "prod"
+    }
+
+    service {
+      port     = "db"
+      name     = "redis"
+      provider = "consul"
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+If a `consul` block is not defined, then the workload identity will not have
+the `consul_namespace` claim, since Nomad is not able to determine which Consul
+namespace will be used.
+
+Refer to the [Consul Namespaces][int_consul_ns] section for more information.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Consul servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Consul and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Consul auth method.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Consul Servers Not Able to Connect to Nomad
+
+If the Consul servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`JWTValidationPubKeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Consul servers, and use that address as the value for
+`JWKSURL`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional References
+
+The [Consul ACL with Nomad Workload Identities][consul_tutorial_wid] tutorial
+provides guided instructions on how to configure Consul and Nomad for workload
+identities.
+
+The [`nomad setup consul`][nomad_cli_setup_consul] command and the
+[`hashicorp-modules/nomad-setup/consul`][tf_nomad_setup_consul] Terraform
+module can help you automate the process of applying configuration to a Consul
+cluster.
+
+## Authenticating Without Workload Identity (Legacy)
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`][]
+configuration parameter will control whether a Consul token will be required
+when submitting a job with Consul namespace configured. The provided Consul
+token must belong to the correct namespace, and must be backed by a Consul ACL
+Policy with sufficient `service:write` and `kv:read` permissions. An example
+policy might look like the following.
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+<Note title="Deprecation Warning">
+
+This legacy workflow will be removed in Nomad 1.10. Before upgrading to Nomad 1.10,
+you need to configure authentication with Consul as described in
+[Nomad Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+## Migrating to Using Workload Identity with Consul
+
+Migrating from the legacy (pre-1.7) workflow where workload use the agent's
+Consul token requires configuation on your Consul cluster and your Nomad server
+agents. It does not require updating your running Nomad jobs. To migrate:
+
+* Create the Consul auth method and binding rules on your Consul cluster.
+* Enable [`consul.service_identity`][] blocks in your Nomad server agent configurations.
+* Enable [`consul.task_identity`][] blocks in your Nomad server agent configurations.
+* (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+  different identity because of how your auth method and binding rules are
+  configured.
+
+Note that when using Workload Identity you will no longer need to pass in a
+Consul token to submit a job.
+
+[Variables]: /nomad/docs/concepts/variables
+[`-bind-name`]: /consul/commands/acl/binding-rule/create#bind-name
+[`-selector`]: /consul/commands/acl/binding-rule/create#selector
+[`BindNamespace`]: /consul/api-docs/acl/auth-methods#bindnamespace
+[`JWTValidationPubKeys`]: /consul/docs/security/acl/auth-methods/jwt#jwtvalidationpubkeys
+[`NamespaceRules`]: /consul/api-docs/acl/auth-methods#namespacerules
+[`Selector`]: /consul/api-docs/acl/auth-methods#selector
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[`consul.service_auth_method`]: /nomad/docs/configuration/consul#service_auth_method
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_auth_method`]: /nomad/docs/configuration/consul#task_auth_method
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`identity`]: /nomad/docs/job-specification/identity
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[consul_acl_policy]: /consul/docs/security/acl/acl-policies
+[consul_acl_role]: /consul/docs/security/acl/acl-roles
+[consul_acls]: /consul/docs/security/acl
+[consul_auth_methods]: /consul/docs/security/acl/auth-methods
+[consul_binding_rules]: /consul/api-docs/acl/binding-rules
+[consul_config_entry]: /consul/docs/connect/config-entries
+[consul_jwt_auth_method]: /consul/docs/security/acl/auth-methods/jwt
+[consul_si]: /consul/docs/security/acl/acl-roles#service-identities
+[consul_tutorial_wid]: /nomad/tutorials/integrate-consul/consul-acl
+[img_consul_auth]: /img/consul-integration-wi.png
+[img_consul_auth_method]: /img/consul-integration-auth-method.png
+[img_consul_wid_acl_token]: /img/consul-integration-wid-acl-token.png
+[int_consul_ns]: /nomad/docs/integrations/consul#consul-namespaces
+[jobspec_identity_consul]: /nomad/docs/job-specification/identity#workload-identities-for-consul
+[jwt]: https://jwt.io/
+[nomad_cli_setup_consul]: /nomad/docs/commands/setup/consul
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_consul]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/consul/
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.8.x/content/docs/integrations/consul/index.mdx b/content/nomad/v1.8.x/content/docs/integrations/consul/index.mdx
new file mode 100644
index 0000000000..5c023d027c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/consul/index.mdx
@@ -0,0 +1,200 @@
+---
+layout: docs
+page_title: Consul Integration
+description: Learn how to integrate Nomad with Consul and add service discovery to jobs
+---
+
+# Consul Integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and install Consul
+on your nodes alongside Nomad, or schedule it as a system job. Nomad does not
+run Consul for you.
+
+To enable Consul integration, please refer to the [Nomad agent Consul
+configuration][] documentation.
+
+## Automatic Clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please refer to the [Automatic Clustering
+with Consul][] guide for more information.
+
+## Service Discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please refer to the
+[`service` job specification documentation][service].
+
+## Service Mesh
+
+Consul service mesh provides service-to-service connection authorization and
+encryption using mutual Transport Layer Security (TLS). Nomad can automatically
+provision the components necessary to securely connect your tasks to Consul's
+service mesh.
+
+Refer to the [Consul Service Mesh integration page][int_consul_mesh] for more
+information.
+
+## Dynamic Configuration
+
+Nomad's job specification includes a [`template`][] block that uses a Consul
+ecosystem tool called [Consul Template][]. This mechanism creates a convenient
+way to ship configuration files that are populated from environment variables,
+Consul data, Vault secrets, or just general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul
+Template, please see the [`template` job specification documentation][].
+
+## DNS
+
+To provide Consul DNS to Nomad workloads using [bridge or CNI networking
+mode][], you will need to configure Consul's DNS listener to be exposed to the
+workload network namespace, or configure `systemd-resolved`, `dnsmasq`, or
+similar DNS stub resolvers to forward DNS. See [Forward DNS for Consul service
+discovery][] for details.
+
+You can avoid exposing the Consul agent on a public IP by setting the Consul
+`bind_addr` to bind on a private IP address (the default is to use the
+`client_addr`). You will also need to either have Consul bind to port 53 for
+DNS if you are not using DNS forwarding.
+
+You will also need to set the [nameserver][] to the address. This address is
+exposed as the `consul.dns.addr` node attribute or the `DNSStubListener`
+configuration value for `systemd-resolved`.
+
+An simpler solution is to use Consul Connect [transparent proxy][] mode to
+automatically configure tasks to use Consul DNS.
+
+## Consul ACL
+
+The Consul ACL system protects the cluster from unauthorized access. When
+enabled, both Consul and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Consul ACL integration page][int_consul_acl] for more
+information.
+
+## Consul Namespaces <EnterpriseAlert inline/>
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for
+service registrations specified in `service` blocks and Consul KV reads in
+`template` blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations
+or KV store reads, which Consul then implicitly resolves to the `"default"`
+namespace.  This default namespace behavior can be modified by setting the
+[`namespace`][consul_agent_namespace] field in the Nomad agent Consul
+configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring
+the Consul [namespace][consul_jobspec_namespace] at the group or task level in
+the Nomad job spec as well as the [`-consul-namespace`][consul_run_namespace]
+command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations
+within a group, as well as `template` KV store access is determined from the
+following hierarchy from highest to lowest precedence:
+
+* group and task configuration: Consul
+  [namespace field][consul_jobspec_namespace] defined in the job at the task or
+  group level.
+
+* job run command option: Consul namespace defined in the
+  [`-consul-namespace`][consul_run_namespace] command line option on job
+  submission.
+
+* job run command environment various: Consul namespace defined as the
+  [`CONSUL_NAMESPACE`][consul_env_namespace] environment variable on job
+  submission.
+
+* agent configuration: Consul namespace defined in the
+  [`namespace`][consul_agent_namespace] Nomad agent Consul configuration
+  parameter.
+
+* Consul default: If no Consul namespace options are configured, Consul will
+  automatically make use of the `"default"` namespace.
+
+## Multiple Consul Clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Consul clusters. They can be
+configured using multiple [`consul`][nomad_config_consul] blocks with different
+`name` values. If a `name` is not provided, the cluster configuration is called
+`default`. Nomad automatic clustering uses the `default` cluster for service
+discovery.
+
+Jobs that need access to Consul may specify which Consul cluster to use with
+the [`consul.cluster`][] parameter.
+
+## Assumptions
+
+* Each Nomad client should have a local Consul agent running on the same host,
+  reachable by Nomad. Nomad clients should never share a Consul agent or talk
+  directly to the Consul servers. Nomad is not compatible with [Consul Data
+  Plane][CDP].
+
+* The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+* Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+* The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+
+* Consul service mesh using network namespaces is only supported on Linux.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Consul, with some exceptions.
+
+* Nomad is not compatible with Consul Data Plane.
+
+|                   | Consul 1.17.0+ | Consul 1.18.0+ | Consul 1.19.0+ |
+|-------------------|----------------|----------------|----------------|
+| Nomad 1.8.0+      | ✅             | ✅             | ✅            |
+| Nomad 1.7.0+      | ✅             | ✅             | ✅            |
+| Nomad 1.6.0+      | ✅             | ✅             | ✅            |
+
+[Automatic Clustering with Consul]: /nomad/tutorials/manage-clusters/clustering
+[CDP]: /consul/docs/connect/dataplane
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Nomad agent Consul configuration]: /nomad/docs/configuration/consul
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`template` job specification documentation]: /nomad/docs/job-specification/template#consul-integration
+[`template`]: /nomad/docs/job-specification/template
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_jobspec_namespace]: /nomad/docs/job-specification/consul#namespace
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[consul_env_namespace]: /consul/commands#consul_namespace
+[int_consul_acl]: /nomad/docs/integrations/consul/acl
+[int_consul_mesh]: /nomad/docs/integrations/consul/service-mesh
+[nomad_config_consul]: /nomad/docs/configuration/consul
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
+[bridge or CNI networking mode]: /nomad/docs/job-specification/network#mode
+[nameserver]: /nomad/docs/job-specification/network#servers
+[transparent proxy]: /nomad/docs/job-specification/transparent_proxy
+[Forward DNS for Consul service discovery]: https://developer.hashicorp.com/consul/tutorials/networking/dns-forwarding
diff --git a/content/nomad/v1.8.x/content/docs/integrations/consul/service-mesh.mdx b/content/nomad/v1.8.x/content/docs/integrations/consul/service-mesh.mdx
new file mode 100644
index 0000000000..21b0afd150
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/consul/service-mesh.mdx
@@ -0,0 +1,517 @@
+---
+layout: docs
+page_title: Consul Service Mesh
+description: >-
+  Learn how to use Nomad with Consul service mesh to enable secure service to service
+  communication
+---
+
+# Consul Service Mesh
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+# Nomad with Consul Service Mesh Integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul Service Mesh Example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul ACLs
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+#### Transparent Proxy
+
+Using Nomad's support for [transparent proxy][] configures the task group's
+network namespace so that traffic flows through the Envoy proxy. When the
+[`transparent_proxy`][] block is enabled:
+
+* Nomad will invoke the [`consul-cni`][] CNI plugin to configure `iptables` rules
+  in the network namespace to force outbound traffic from an allocation to flow
+  through the proxy.
+* If the local Consul agent is serving DNS, Nomad will set the IP address of the
+  Consul agent as the nameserver in the task's `/etc/resolv.conf`.
+* Consul will provide a [virtual IP][] for any upstream service the workload
+  has access to, based on the service intentions.
+
+Using transparent proxy has several important requirements:
+
+* You must have the [`consul-cni`][] CNI plugin installed on the client host
+  along with the usual [required CNI plugins][cni_plugins].
+* To use Consul DNS and virtual IPs, you will need to configure Consul's DNS
+  listener to be exposed to the workload network namespace. You can do this
+  without exposing the Consul agent on a public IP by setting the Consul
+  `bind_addr` to bind on a private IP address (the default is to use the
+  `client_addr`).
+* The Consul agent must be configured with [`recursors`][] if you want
+  allocations to make DNS queries for applications outside the service mesh.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`][tproxy_no_dns], see below).
+
+For example, a HCL configuration with a [go-sockaddr/template][] binding to the
+subnet `10.37.105.0/20`, with recursive DNS set to OpenDNS nameservers:
+
+```hcl
+bind_addr   = "{{ GetPrivateInterfaces | include \"network\" \"10.37.105.0/20\" | limit 1 | attr \"address\" }}"
+
+recursors = ["208.67.222.222", "208.67.220.220"]
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### CNI Plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/install#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+## Run the Service Mesh-enabled Services
+
+Once Nomad and Consul are running, with Consul DNS enabled for transparent proxy
+mode as described above, submit the following service mesh-enabled services to
+Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API Service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+group "api" {
+  network {
+    mode = "bridge"
+  }
+
+  # ...
+}
+```
+
+Since the API service is only accessible via Consul service mesh, it does not
+define any ports in its network. The `connect` block enables the service mesh
+and the `transparent_proxy` block ensures that the service will be reachable via
+a virtual IP address when used with Consul DNS.
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {
+        proxy {
+          transparent_proxy {}
+        }
+      }
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+group "dashboard" {
+  network {
+    mode = "bridge"
+
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        transparent_proxy {}
+      }
+    }
+  }
+}
+```
+
+The `connect` block with `transparent_proxy` configures the web frontend's
+network namespace to route all access to the `count-api` service through the
+Envoy proxy.
+
+The web frontend is configured to communicate with the API service with an
+environment variable `$COUNTING_SERVICE_URL`:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+}
+```
+
+The `transparent_proxy` block ensures that DNS queries are made to Consul so
+that the `count-api.virtual.consul` name resolves to a virtual IP address. Note
+that you don't need to specify a port number because the virtual IP will only be
+directed to the correct service port.
+
+### Manually Configured Upstreams
+
+You can also use Connect without Consul DNS and `transparent_proxy` mode. This
+approach is not recommended because it requires duplicating service intention
+information in an `upstreams` block in the Nomad job specification. But Consul
+DNS is not protected by ACLs, so you might want to do this if you don't want to
+expose Consul DNS to untrusted workloads.
+
+In that case, you can add `upstream` blocks to the job spec. You don't need the
+`transparent_proxy` block for the `count-api` service:
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {}
+    }
+  }
+
+  # ...
+
+}
+```
+
+But you'll need to add an `upstreams` block to the `count-dashboard` service:
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        upstreams {
+          destination_name = "count-api"
+          local_bind_port  = 8080
+        }
+      }
+    }
+  }
+}
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend will also need to use an environment variable to communicate
+with the API service:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+}
+```
+
+This environment variable value gets interpolated with the upstream's
+address. Note that dashes (`-`) are converted to underscores (`_`) in
+environment variables so `count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+Bootstrapping the Envoy proxy requires that the Consul ACL token and service
+registration have successfully replicated to whichever Consul server the local
+Consul agent is connected to. Nomad clients poll for this value with exponential
+backoff and a timeout. You can adjust the timeouts on a given node by setting
+node metadata values via the command line or in the [`client.meta`][] agent
+configuration block. The default values are shown below:
+
+```shell-session
+nomad node meta apply -node-id $nodeID \
+    consul.token_preflight_check.timeout=10s \
+    consul.token_preflight_check.base=500ms \
+    consul.service_preflight_check.timeout=60s \
+    consul.service_preflight_check.base=1s
+```
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/install#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
diff --git a/content/nomad/v1.8.x/content/docs/integrations/index.mdx b/content/nomad/v1.8.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..7cb314682f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad HashiStack Integrations
+description: This section features Nomad's integrations with Consul and Vault.
+---
+
+# HashiCorp Integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.8.x/content/docs/integrations/vault/acl.mdx b/content/nomad/v1.8.x/content/docs/integrations/vault/acl.mdx
new file mode 100644
index 0000000000..4b2c1717af
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/vault/acl.mdx
@@ -0,0 +1,868 @@
+---
+layout: docs
+page_title: Vault ACL
+description: Learn how to integrate Nomad with Vault when ACL is enabled.
+---
+
+# Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. It must be
+properly configured in order for the Vault and Nomad integrations to work.
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault ACL token specific to the task. When
+using Nomad workload identities, you no longer need to pass in a Vault ACL
+token to submit a job.
+
+By default, Nomad only generates a workload identity for tasks that can be used
+to access Nomad itself, such as for reading [Variables][] from a [`template`][]
+block. To access Vault, jobs must have additional workload identities defined
+as [`identity`][] blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure the Nomad servers with the [`vault.default_identity`][] agent
+configuration. Upon job registration, the Nomad servers update tasks that have
+a [`vault`][] block with this default identity.
+
+You can also specify identities for Vault directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Vault][jobspec_identity_vault] section of the `identity` block
+documentation for more information.
+
+### Configuring Vault Authentication
+
+Vault must be configured to receive, validate, and trust these Nomad workload
+identities. Since they are encoded as [JSON Web Tokens (JWTs)][jwt], you must
+create a [JWT ACL auth method][vault_jwt_auth_method]. The auth method is an
+endpoint that Nomad can use to exchange workload identities for Vault ACL
+tokens.
+
+Refer to Vault's [Authentication][vault_auth] documentation for more
+information.
+
+#### Vault Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Vault servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Vault is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The `jwks_url` address must be reachable by all Vault servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `jwks_url` value.
+
+[![Vault Auth Method][img_vault_auth_method]][img_vault_auth_method]
+
+When an allocation that needs access access to Vault starts, the Nomad client
+running it exchanges the Nomad workload identities for tasks for Vault ACL
+tokens.
+
+[![Vault JWT Login][img_vault_wid_acl_token]][img_vault_wid_acl_token]
+
+#### Vault ACL Role
+
+A Vault [ACL role][vault_role] groups multiple ACL policies to apply to a token
+and determine the permissions it receives.
+
+The auth method may define a default ACL role that is applied to the ACL tokens
+it generates. If no default role is set, the role must be provided in the job
+using the [`vault.role`][] parameter or in the Nomad client configuration
+[`vault.create_from_role`][].
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The ACL role specifies the list of authorized audience values using the
+[`bound_audiences`][], which must have at least one match with the values
+defined in the Nomad workload identity [`aud`][] parameter. For security
+reasons, it is recommended to only define a single audience value.
+
+<CodeBlockConfig highlight="3" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced in Vault ACL configuration. The ACL role uses the
+[`claim_mappings`][] parameter to determine which of these claims are made
+available to the rest of the configuration.
+
+The [`bound_claims`][] parameter restricts which workload identities are able
+to use the role based on their claims. Refer to Vault's [Bound
+Claims][vault_bound_claims] documentation for more information.
+
+<CodeBlockConfig highlight="4-7,10-14" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Vault has different [types of ACL tokens][vault_token_types]. Nomad typically
+uses tokens of type `service` since they can be renewed for as long as the
+workload is active. Nomad automatically renews the Vault ACL tokens it generates
+before they expire. To ensure the tokens can be renewed for as long as
+necessary, [`token_explicit_max_ttl`][] must be set to 0.
+
+Alternately, you may use `batch` tokens. This should only be used when a secret
+is requested from Vault once at the start of a task or in a short-lived prestart
+task. Long-running tasks should never set `allow_token_expiration=true` if they
+obtain Vault secrets via `template` blocks, as the Vault token will expire and
+the template runner will continue to make failing requests to Vault until its
+[`vault_retry`][] attempts are exhausted, at which point the task will
+fail. Vault's `batch` tokens cannot be renewed, and Nomad will not attempt to
+renew them when configured to use Workload Identity.
+
+<CodeBlockConfig highlight="16-18" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+#### Vault ACL Policy
+
+A Vault ACL role may have one or more ACL policies attached. Vault [ACL
+policies][vault_policies] define the permissions granted to an ACL
+token.
+
+<CodeBlockConfig highlight="15" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+ACL policies can reference dynamic values from Nomad workload identities claims
+exposed from the ACL role in [templated policies][vault_templated_policies].
+The exact ACL policy rules will depend on the level of access required by
+tasks.
+
+The following example ACL policy automatically grants `read` permissions to
+secrets in the path `secret/data/<job namespace>/<job name>/*`, where `<job
+namespace>` and `<job name>` are read from the workload identity claims
+`nomad_namespace` and `nomad_job_id`.
+
+<CodeBlockConfig highlight="1,5,9" filename="acl-policy.hcl">
+
+```hcl
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Vault Auth Overview][img_vault_auth_overview]][img_vault_auth_overview]
+
+#### Vault Namespaces <EnterpriseAlert inline />
+
+Vault Enterprise supports multiple namespaces and jobs in Nomad Enterprise can
+use the [`vault.namespace`][] parameter to specify which namespace to use. In a
+multi-namespace environment, the authentication setup described must be applied
+to each Vault namespace used by jobs.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Vault servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Vault and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Vault auth method. Nomad's CA certificate should be
+specified in the Vault auth method's
+[`jwks_ca_pem`](https://developer.hashicorp.com/vault/api-docs/auth/jwt#jwks_ca_pem)
+parameter.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Vault Servers Not Able to Connect to Nomad
+
+If the Vault servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`jwt_validation_pubkeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Vault servers, and use that address as the value for
+`jwks_url`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional References
+
+The [Vault ACL with Nomad Workload Identities][vault_tutorial_wid] tutorial
+provides guided instructions on how to configure Vault and Nomad for workload
+identities.
+
+The [`nomad setup vault`][nomad_cli_setup_vault] command and the
+[`hashicorp-modules/nomad-setup/vault`][tf_nomad_setup_vault] Terraform
+module can help you automate the process of applying configuration to a Vault
+cluster.
+
+## Authentication Without Workload Identity (Legacy)
+
+To use the legacy Vault integration, Nomad servers must be provided a Vault
+token. This token can either be a root token or a periodic token with
+permissions to create from a token role. The root token is the easiest way to
+get started, but we recommend a token role based token for production
+installations. Nomad servers will renew the token automatically. **Note that the
+Nomad clients do not need to be provided with a Vault token.**
+
+<Note title="Deprecation Warning">
+
+This legacy workflow will be removed in Nomad 1.10. Before upgrading to Nomad
+1.10, you need to configure authentication with Vault as described in [Nomad
+Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+See the [Enterprise specific section][ent] for configuring Vault Enterprise.
+
+### Root Token Integration
+
+If Nomad is given a [root token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. This allows
+  Nomad to renew tokens for tasks. Nomad clients will automatically detect when
+  tokens cannot be renewed and will not attempt to renew them (see
+  [`vault.allow_token_expiration`][]).
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Troubleshooting Legacy Authentication
+
+#### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+#### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise allows jobs to use multiple [Vault Namespaces][]. There are a
+few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the
+example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-workloads` role with each
+Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a
+Vault Namespace, but since we will be using multiple it can be left blank. By
+default Nomad will interact with Vault's root Namespace, but individual jobs may
+specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+  }
+}
+```
+
+For legacy authentication, the same steps can be taken to inject a Vault token
+from the [Retrieving the Token Role based
+Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+The example job file below specifies to use the `engineering` Namespace in
+Vault. It will authenticate to Vault using its workload identity with the
+`nomad-workloads` Vault role, then read the value at secret/foo and fetch the
+value for key `bar`.
+
+```hcl
+job "vault" {
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        role      = "nomad-workloads"
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Submitting a job with a Vault Namespace with Legacy Authentication
+
+For the legacy authentication, because [`allow_unauthenticated`][allow_unauth]
+is set to `false` job submitters will need to provide a sufficiently privileged
+token when submitting a job. A token that has access to an appropriate policy in
+`engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+## Migrating to Using Workload Identity with Vault
+
+Migrating from the legacy (pre-1.7) workflow where workloads use the agent's
+Vault token requires configuration on your Vault cluster and your Nomad server
+agents.
+
+Once the migration is fully complete, Nomad server will no longer have access
+to Vault, as it was required in the deprecated legacy workflow. This also means
+that they will no longer be able to fulfill some of their responsibilities from
+the legacy workflow, such as generating and revoking Vault ACL tokens.
+
+Before removing Vault connectivity configuration from Nomad servers, you must
+make sure the rest of the cluster is ready to support workload identities for
+Vault. You can run the [`nomad setup vault -check`][nomad_cli_setup_vault]
+command to verify what changes are still necessary.
+
+Before removing Nomad servers access to Vault you must:
+
+  * Redeploy the jobs listed in the section `Jobs Without Workload Identity for
+    Vault` with an identity for Vault. You can specify this identity [directly
+    in the job][jobspec_identity_vault] or redeploy the job without changes to
+    use the default value from the server [`vault.default_identity`][]
+    configuration if set.
+  * Upgrade nodes listed in the section `Outdated Nodes` to a version of Nomad
+    above 1.7.0.
+
+There is not action required for the Vault ACL tokens listed under `Vault
+Tokens`. Nomad will revoke them as you redeploy jobs to use workload identities
+but there may be some leftovers. You can still proceed with the migration
+process, but Nomad will not revoke them once access to Vault is removed from
+Nomad servers. They will expire once their TTL reaches zero, or you may
+manually revoke them if they are no longer needed by an allocation.
+
+The migration process can happen over time. As long as all servers are upgraded
+to Nomad 1.7+ and still retain access to Vault, jobs can still use either the
+new workload identity flow or the deprecated legacy flow.
+
+To summarize the migration process:
+
+* Enable [`vault.default_identity`][] blocks in your Nomad server agent
+  configurations, but **do not modify any of the existing Vault
+  configuration**.
+* Upgrade your cluster following the documented [Upgrade
+  Process][docs_upgrade].
+* Create the Vault auth method, default role, and policies on your Vault
+  cluster.
+* Run the `nomad setup vault -check` command to verify if the cluster is ready
+  to migrate to workload identity access to Vault.
+  * Resubmit Nomad jobs that need access to Vault to redeploy them with a new
+    workload identity for Vault.
+    * (Optionally) Add [`vault.role`][] fields to any Nomad jobs that will not
+      use the default role.
+    * (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+      different identity because of how your auth method and roles are
+      configured.
+  * Upgrade any remaining clients to Nomad 1.7+.
+* Remove parameters no longer used by the Nomad server agents from the
+  [`vault`][config] configuration block.
+
+[Variables]: /nomad/docs/concepts/variables
+[Vault Namespaces]: /vault/docs/enterprise/namespaces
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`bound_audiences`]: /vault/api-docs/auth/jwt#bound_audiences
+[`bound_claims`]: /vault/api-docs/auth/jwt#bound_claims
+[`claim_mappings`]: /vault/api-docs/auth/jwt#claim_mappings
+[`identity`]: /nomad/docs/job-specification/identity
+[`jwt_validation_pubkeys`]: /vault/api-docs/auth/jwt#jwt_validation_pubkeys
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[`token_explicit_max_ttl`]: /vault/api-docs/auth/jwt#token_explicit_max_ttl
+[`vault.create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault.namespace`]: /nomad/docs/job-specification/vault#namespace
+[`vault.role`]: /nomad/docs/job-specification/vault#role
+[`vault`]: /nomad/docs/job-specification/vault
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[docs_upgrade]: /nomad/docs/upgrade#upgrade-process
+[ent]: #enterprise-configuration
+[img_vault_auth_method]: /img/vault-integration-auth-method.png
+[img_vault_auth_overview]: /img/vault-integration-auth-overview.png
+[img_vault_wid_acl_token]: /img/vault-integration-wid-acl-token.png
+[jobspec_identity_vault]: /nomad/docs/job-specification/identity#workload-identities-for-vault
+[jwt]: https://jwt.io/
+[nomad_cli_setup_vault]: /nomad/docs/commands/setup/vault
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_vault]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault_auth]: /vault/docs/concepts/auth
+[vault_bound_claims]: /vault/docs/auth/jwt#bound-claims
+[vault_jwt_auth_method]: /vault/api-docs/auth/jwt
+[vault_policies]: /vault/docs/concepts/policies
+[vault_role]: /vault/api-docs/auth/jwt#create-update-role
+[vault_templated_policies]: /vault/tutorials/policies/policy-templating
+[vault_token_types]: /vault/tutorials/tokens/tokens#token-types
+[vault_tutorial_wid]: /nomad/tutorials/integrate-vault/vault-acl
+[`vault.allow_token_expiration`]: /nomad/docs/job-specification/vault#allow_token_expiration
diff --git a/content/nomad/v1.8.x/content/docs/integrations/vault/index.mdx b/content/nomad/v1.8.x/content/docs/integrations/vault/index.mdx
new file mode 100644
index 0000000000..b8d58e31a0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/integrations/vault/index.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Learn how to integrate Nomad with HashiCorp Vault and retrieve Vault tokens
+  for tasks.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal.
+
+## Configuration
+
+In order to use Vault with Nomad, you will need to configure and install Vault
+separately from Nomad. Nomad does not run Vault for you.
+
+## Agent Configuration
+
+To enable Vault integration, Nomad agents must be configured with
+[`vault`][] blocks. Each block can be enabled or disabled and configures how
+Nomad connects to the Vault cluster.
+
+## Dynamic Configuration with Secrets
+
+Nomad's job specification includes a [`template`][] block that uses a tool
+called [Consul Template][]. When used with Vault, this mechanism creates a
+convenient way to ship configuration files that are populated from Vault
+secrets.
+
+For more information on Nomad's template block please see the
+[`template` job specification documentation][].
+
+## Vault ACL
+
+The Vault ACL system protects the cluster from unauthorized access. When
+enabled, both Vault and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Vault ACL integration page][int_vault_acl] for more information.
+
+## Multiple Vault Clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Vault clusters. They can be
+configured using multiple [`vault`][] blocks with different `name` values. If a
+`name` is not provided, the cluster configuration is called `default`.
+
+Jobs that need access to Vault may specify which Vault cluster to use with the
+[`vault.cluster`][] parameter.
+
+## Compatibility
+
+* Nomad versions 1.4.0 and above are compatible with any currently supported
+  version of Vault.
+
+|              | Vault 1.13.0+ |
+|--------------|---------------|
+| Nomad 1.4.0+ | ✅            |
+
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Vault]:  https://www.vaultproject.io/ 'Vault by HashiCorp'
+[`template` job specification documentation]: /nomad/docs/job-specification/template#vault-integration
+[`template`]: /nomad/docs/job-specification/template
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[int_vault_acl]: /nomad/docs/integrations/vault/acl
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/action.mdx b/content/nomad/v1.8.x/content/docs/job-specification/action.mdx
new file mode 100644
index 0000000000..bb7f4c43da
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/action.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: action Block - Job Specification
+description: The "action" block allows for executable commands that job authors can predefine for operators to subsequently run against their job.
+---
+
+# `action` Block
+
+<Placement groups={['job', 'group', 'task', 'action']} />
+
+The `action` block allows job authors to define custom commands. These commands
+can be executed by operators with the necessary permissions on a running
+allocation, offering a controlled way to interact with tasks.
+
+The name of the action can contain alphanumeric characters and dashes. This
+name must be unique within its task and must not exceed 128 characters.
+
+## `action` Parameters
+
+- `command` `(string: <required>)` - Specifies the command to be executed.
+- `args` `(array<string>: [])` - Provides a list of arguments to pass to the command.
+
+```hcl
+job "my-job" {
+  group "my-group" {
+    task "my-task" {
+      action "get-changelog" {
+        command = "/usr/bin/curl"
+        args = [
+          "-s",
+          "https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md"
+        ]
+      }
+      # ...
+    }
+  }
+}
+```
+
+## `action` Examples
+
+### Basic Action
+This example demonstrates a simple action that prints the current date and time:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "show-date" {
+      # ...
+      action "current-date" {
+        command = "/bin/date"
+      }
+    }
+  }
+}
+```
+
+### Action with Arguments
+Here, an action uses arguments to perform a specific task:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "list-files" {
+      # ...
+      action "list-tmp" {
+        command = "/bin/ls"
+        args    = ["-l", "/tmp"]
+      }
+    }
+  }
+}
+```
+
+### Action with Template
+This advanced example demonstrates an action that fetches and formats the latest
+changelog from the Nomad GitHub repository using a shell script. It showcases
+the use of templating with embedded environment variables and a multi-line script.
+
+```hcl
+action "fetch-latest-nomad-changelog" {
+  command = "/bin/sh"
+  args    = ["-c", 
+    <<EOT
+curl -s https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md | 
+
+awk 'BEGIN{
+    # Setting record and field separators
+    RS="## "; FS="\n"; 
+    section=""; count=0
+}
+{
+    # Processing only the first 3 sections after the header
+    if (count < 3 && NR > 1){
+        # Splitting the version line into components
+        split($1, versionInfo, /[()]/);
+        version=versionInfo[1];
+        gsub(" ", "", version); # Removing spaces from version
+        releaseDate=versionInfo[2];
+        # Formatting URL components
+        urlVersion=version; gsub("\\.", "", urlVersion); # Remove dots from version
+        urlDate=releaseDate; gsub(" ", "-", urlDate); gsub(",", "", urlDate); # Replace spaces with hyphens and remove comma
+        # Counting items under each section
+        for(i=1; i<=NF; i++){
+            if($i ~ /^[A-Z ]+:$/){
+                gsub(":", "", $i);
+                section=$i;
+                itemCount[section]=0;
+            }
+            if(section && $i ~ /^\*/){
+                itemCount[section]++;
+            }
+        }
+        # Printing the extracted information
+        printf "Version: %s\nRelease Date: %s\n", version, releaseDate;
+        for (s in itemCount) {
+            printf "%d %s, ", itemCount[s], s;
+        }
+        printf "\nLink: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md#%s-%s\n\n", urlVersion, tolower(urlDate);
+        delete itemCount;  # Clear the itemCount array for the next version
+        count++;
+    }
+}'
+    EOT
+  ]
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.8.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.8.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..3960f80b35
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,283 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. Non-Amazon S3-compatible endpoints like [Minio]
+are supported, but you must explicitly set the "s3::" prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment variables
+set for the Nomad client. Inheritance of environment variables can be managed through the [`artifact.set_environment_variables`][client_artifact]
+client configuration.
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.8.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/check.mdx b/content/nomad/v1.8.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..eb9651dbe4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,477 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_success_before_passing].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_failure_before_critical].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_warning` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`warning`][consul_failure_before_warning].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. Numeric ports may be used if `address_mode="driver"` is set 
+  on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider. 
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks . Only supported in the Consul
+  service provider.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_success_before_passing]: /consul/api-docs/agent/check#successbeforepassing
+[consul_failure_before_critical]: /consul/api-docs/agent/check#failuresbeforecritical
+[consul_failure_before_warning]: /consul/api-docs/agent/check#failuresbeforewarning
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.8.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.8.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.8.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..f09e253aa7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,322 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/consul.mdx b/content/nomad/v1.8.x/content/docs/job-specification/consul.mdx
new file mode 100644
index 0000000000..e46f8fe51e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/consul.mdx
@@ -0,0 +1,297 @@
+---
+layout: docs
+page_title: consul Block - Job Specification
+description: |-
+  The "consul" block allows the group or task to specify that it requires a token
+  from a HashiCorp Consul server. Nomad will automatically retrieve a Consul token
+  for the group or task.
+---
+
+# `consul` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'consul'],
+    ['job', 'group', 'task', 'consul'],
+  ]}
+/>
+
+The `consul` block specifies [Consul][] configuration options specific to a
+task. If specified at the `group` level, the configuration will apply to all
+tasks and services within the group unless a task has its own `consul` block. A
+task-level `consul` block will entirely override a group-level `consul` block.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      consul {
+        cluster   = "default"
+        namespace = "default"
+        partition = "default"
+      }
+    }
+  }
+}
+```
+
+## Workload Identity
+
+Starting in Nomad 1.7, Nomad clients will use a task or service's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+service or task when the following conditions are met:
+
+* For services, if either the [`consul.service_identity`][] is configured on the
+  Nomad servers or the service includes an `identity` block.
+* For tasks, if the [`consul.task_identity`][] is configured on the Nomad
+  servers, or the task includes an [`identity`][] block with the `name` field
+  set to `consul_default` (or `consul_$clusterName` for non-default Consul
+  clusters in Nomad Enterprise).
+
+As a fallback if none of these conditions are met, the Nomad client will instead
+use, in order of preference:
+
+* The token provided by the [`-consul-token`][flag_consul_token] flag for the
+  `nomad job run` command.
+* The Consul token as configured in the agent's [`consul.token`][] configuration.
+* The Consul token as configured by the agent's `CONSUL_HTTP_TOKEN` environment variable.
+
+To avoid failed deployments, you should first set up an authentication method
+and binding rules in Consul before configuring the Nomad servers with
+`consul.task_identity` and `consul.service_identity`. Refer to [Configuring Consul
+Authentication][] for more details.
+
+<Warning>
+Starting in Nomad 1.10, the fallback options to use the -consul-token flag when
+submitting a job, the agent's consul.token configuration, or the
+CONSUL_HTTP_TOKEN environment variable, will be removed.  This means service and
+template blocks will not be able to use the agent's Consul token or one provided
+by the job submitter. You should be prepared to migrate to the Workload Identity
+workflow for Consul and Vault before upgrading to Nomad 1.10. Refer to <a
+href="/nomad/docs/integrations/consul-integration#migrating-to-using-workload-identity-with-consul">Migrating
+to Using Workload Identity with Consul</a>
+</Warning>
+
+### Access to Token
+
+The Nomad client will make the Consul token available to the task by writing it
+to the secret directory at `secrets/consul_token` and by injecting a
+`CONSUL_TOKEN` environment variable in the task.
+
+If the Nomad cluster is [configured][config_consul_namespace] to use [Consul Namespaces][], a
+`CONSUL_NAMESPACE` environment variable will be injected whenever `CONSUL_TOKEN`
+is set.
+
+The [`template`][template] block can use the Consul token as well.
+
+### `consul` Parameters
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use. The Nomad client will retrieve a Consul token from the
+  cluster configured in the agent configuration with the same
+  [`consul.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in
+  which group and task-level services within the group will be registered. Use
+  of `template` to access Consul KV will read from the specified Consul
+  namespace.  Specifying `namespace` takes precedence over the
+  [`-consul-namespace`][flag_consul_namespace] command line argument in `job run`.
+
+- `partition` `(string: "")` - When this field is set, a constraint will be
+  added to the group or task to ensure that the allocation is placed on a Nomad
+  client that has a Consul Enterprise agent in the specified Consul [admin
+  partition][]. Note that Consul Community Edition agents are not assigned to
+  any admin partition, so this field should not be used without Consul
+  Enterprise.
+
+## `consul` Examples
+
+The following examples only show the `consul` blocks or other relevant
+blocks. Remember that the `consul` block is only valid in the placements listed
+above.
+
+### Consul Token for Templates
+
+This example tells the Nomad client to obtain a Consul token using the task's
+Workload Identity. The token is available to the task via the canonical
+environment variable `CONSUL_TOKEN` and written to disk at
+`secrets/consul_token`. The `template` block will use the same Consul
+token. Note that the `identity.name` is set to `"consul_default"`, which tells
+the Nomad client to use this identity when making requests to the default Consul
+cluster.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      identity {
+        name = "consul_default"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.task_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted in this case.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Consul Token for Group Services
+
+This example tells the Nomad client to obtain a Consul Service Identity token
+using the service's Workload Identity. The Consul token will be used to register
+the service with Consul and configure any [Connect][] sidecar tasks for that
+service.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+      identity {}
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.service_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted for the service in this case.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+    }
+  }
+}
+```
+
+### Consul Namespace
+
+This example shows specifying a particular Consul namespace or Consul cluster
+for different tasks within a group.
+
+<EnterpriseAlert />
+
+The `template` block in the `web` task will use the default Consul cluster, and
+will obtain a token that allows it access to the `engineering/frontend` Consul
+namespace. The `template` block in the `app` task will use the Consul cluster
+named `prod-apps`, and will obtain a token that allows it access to the
+`engineering/apps` Consul namespace.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "web" {
+
+      consul {
+        namespace = "engineering/frontend"
+      }
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      consul {
+        namespace = "engineering/apps"
+        cluster   = "prod-apps"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+### Consul Admin Partition
+
+This example demonstrates how to configure Consul admin partitions for different
+tasks within a group. The Consul client agent must separately specify the admin
+partition in the agent configuration. Refer to the Consul documentation's
+[agent configuration reference][] for more information.
+
+<EnterpriseAlert />
+
+In the following example, the `web` and `app` tasks use the default Consul cluster
+and obtain a token that allows access to the `prod` admin partition in Consul. The
+Consul configuration occurs at the `group` level because tasks are placed together
+on the same Allocation. If you configure tasks with separate `consul` blocks, the
+`partition` field must be the same in both blocks.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    consul {
+      cluster   = "default"
+      namespace = "default"
+      partition = "prod"
+    }
+
+    task "web" {
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`identity`]: /nomad/docs/job-specification/identity
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[flag_consul_token]: /nomad/docs/commands/job/run#consul-token
+[`consul.token`]: /nomad/docs/configuration/consul#token
+[Configuring Consul Authentication]: /nomad/docs/integrations/consul-integration#TODO
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul-integration#migrating-to-using-workload-identity-with-consul
+[config_consul_namespace]: /nomad/docs/configuration/consul#namespace
+[Consul Namespaces]: /consul/docs/enterprise/namespaces
+[Consul Admin Partitions]: /consul/docs/enterprise/admin-partitions
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[flag_consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[Connect]: /nomad/docs/job-specification/connect
+[admin partition]: /consul/docs/enterprise/admin-partitions
+[agent configuration reference]: /consul/docs/agent/config/config-files#partition-1
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.8.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..a0bfa3ac8c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/device.mdx b/content/nomad/v1.8.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..0748bf8ec4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/docs/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/disconnect.mdx b/content/nomad/v1.8.x/content/docs/job-specification/disconnect.mdx
new file mode 100644
index 0000000000..c5c7db1da1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/disconnect.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: disconnect Block - Job Specification
+description: |-
+  The "disconnect" block describes the behavior of both the Nomad server and 
+  client in case of a network partition, as well as how to reconcile the workloads
+  in case of a reconnection.
+---
+
+# `disconnect` Block
+
+<Placement groups={['job', 'group', 'disconnect']} />
+
+The `disconnect` block describes the system's behavior in case of a network 
+partition. By default, without a `disconnect` block, if an allocation is on a 
+node that misses heartbeats, the allocation will be marked `lost` and will be 
+rescheduled.
+
+```hcl
+ job "docs" {
+  	    group "example" {
+    	    disconnect {
+		        lost_after = "6h"
+		        stop_after = "2h"
+		        replace = false
+                reconcile = "keep_original"
+     	    }
+  	    }
+    }
+```
+
+## `disconnect` Parameters
+
+- `lost_after` `(string: "")` - Specifies a duration during which a Nomad client
+  will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`][] window.  It defaults to "" which is equivalent to 
+  having the disconnect block be nil.
+  
+  See [the example code below][lost_after] for more details. This setting cannot
+  be used with [`stop_after`].
+
+- `replace` `(bool: false)` - Specifies if the disconnected allocation should 
+  be replaced by a new one rescheduled on a different node. If false and the 
+  node it is running on becomes disconnected or goes down, this allocation
+  won't be rescheduled and will be reported as `unknown` until the node reconnects, 
+  or until the allocation is manually stopped:
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  If true, a new alloc will be placed immediately upon the node becoming 
+  disconnected.
+
+- `stop_after` `(string: "")` - Specifies a duration after which a disconnected 
+  Nomad client will stop its allocations. Setting `stop_after` shorter than 
+  `lost_after` and `replace = false` at the same time is not permitted and 
+  will cause a validation error, because this would lead to a state where no 
+  allocations can be scheduled.
+
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`lost_after`].
+
+- `reconcile` `(string: "best_score")` - Specifies which allocation to keep once
+  the previously disconnected node regains connectivity.
+  It has four possible values which are described below:
+
+    - `keep_original`: Always keep the original allocation. Bear in mind 
+    when choosing this option, it can have crashed while the client was 
+    disconnected.
+    - `keep_replacement`: Always keep the allocation that was rescheduled 
+    to replace the disconnected one.
+    - `best_score`: Keep the allocation running on the node with the best 
+    score.
+    - `longest_running`: Keep the allocation that has been up and running 
+    continuously for the longest time.
+
+
+## `disconnect` Examples
+
+The following examples only show the `disconnect` blocks. Remember that the
+`disconnect` block is only valid in the placements listed above.
+
+### Stop After
+
+This example shows how `stop_after` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Lost After
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `lost_after` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost".
+These allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' `replace` settings
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements will 
+decide which ones to keep according to the `reconcile` setting. 
+If the `lost_after` duration expires before the client reconnects, 
+the allocations will be marked "lost". Clients that contain "unknown" 
+allocations will transition to "disconnected" rather than "down" until the last
+`lost_after` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `lost_after`
+is twelve hours. Once all groups' `lost_after` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+using the strategy defined by [`reconcile`].
+
+Lost After is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "best_score"
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "keep_original"
+  }
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`stop_after`]: /nomad/docs/job-specification/disconnect#stop_after
+[`lost_after`]: /nomad/docs/job-specification/disconnect#replace_after
+[`reconcile`]: /nomad/docs/job-specification/disconnect#reconcile
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.8.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..af5e905a54
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/env.mdx b/content/nomad/v1.8.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.8.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..2504291dbc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.8.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..184aad4ca0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.8.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..b97f097675
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,746 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect
+Gateways](/consul/docs/connect/gateways). Nomad will automatically create the
+necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries) as
+well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making
+  upstream connections before timing out. Defaults to 5 seconds. If the upstream
+  service has the configuration option <code>[connect_timeout_ms]</code> set for
+  the `service-resolver`, that timeout value will take precedence over this
+  gateway proxy option.
+
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the
+  gateway services tagged addresses should be bound to listeners in addition to
+  the default listener address.
+
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A
+  map of additional addresses to be bound.  The keys to this map are the same of
+  the listeners to be created and the values are a map with two keys - address
+  and port, that combined make the address to bind the listener to. These are
+  bound in addition to the default address.  If `bridge` networking is in use,
+  this map is automatically populated with additional listeners enabling the
+  Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy
+  Documentation][envoy_sd_docs].  This option applies to terminating gateways
+  that route to services addressed by a hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners
+  that the ingress gateway should setup, uniquely identified by their port
+  number.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or
+  `grpc`), preconfiguring a [service-default][] in Consul to set the
+  [Protocol][service-default-protocol] of the service to the desired protocol is
+  mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[listener-service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### Listener `service` Parameters
+
+The `service` blocks for a listener under an `ingress` gateway accept the
+following parameters. Note these are different than the `service` blocks under a
+`terminating` gateway.
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+- `request_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to requests routed to this
+  service. This cannot be used with a tcp listener.
+
+- `response_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to responses from this
+  service. This cannot be used with a tcp listener.
+
+- `max_concurrent_requests` `(int: <optional>)` - Specifies the maximum number
+  of concurrent HTTP/2 traffic requests that are allowed at a single point in
+  time. If unset, will default to the Envoy proxy's default.
+
+- `max_connections` `(int: <optional>)` - Specifies the maximum number of
+  HTTP/1.1 connections a service instance is allowed to establish against the
+  upstream. If unset, will default to the Envoy proxy's default.
+
+- `max_pending_requests` `(int: <optional>)` - Specifies the maximum number of
+  requests that are allowed to queue while waiting to establish a connection.
+  If unset, will default to the Envoy proxy's default.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this service.
+
+#### Header modifier parameters
+
+The `request_headers` and `response_headers` blocks of an `ingress.service`
+block accept the following parameters. For more details, see the [Consul
+documentation][response-headers].
+
+- `add` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  headers, where header names are keys and header values are the values. Header
+  names are not case-sensitive. If header values with the same name already
+  exist, the value is appended and Consul applies both headers.
+
+- `set` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  response header or to replace existing header values with. Use header names as
+  the keys. Header names are not case-sensitive. If header values with the same
+  names already exist, Consul replaces the header values.
+
+- `remove` `array(string): optional` - Defines a list of headers to remove. Consul
+  removes only headers containing exact matches. Header names are not
+  case-sensitive.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every
+  listener on the gateway. If TLS is enabled, then each host defined in the
+  `host` field will be added as a DNSSAN to the gateway's x509 certificate.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+- `sds` `(block: optional)` - Defines a set of parameters that configures the
+  listener to load TLS certificates from an external Secret Discovery Service
+  ([SDS][]).
+
+  - `cluster_name` `(string)` - The SDS cluster name to connect to to retrieve
+    certificates.
+
+  - `cert_resource` `(string)` - The SDS resource name to request when fetching
+    the certificate from the SDS service.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### linked `service` Parameters
+
+The `service` blocks for a `terminating` gateway accept the following
+parameters. Note these are different than the `service` blocks for listeners
+under an `ingress` gateway.
+
+- `name` `(string: required)` - The name of the service to link with the
+  gateway. If the wildcard specifier `*` is provided, then ALL services within
+  the Consul namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate
+  authority is used to verify the authenticity of the service linked with the
+  gateway. It can be provided along with a `cert_file` and `key_file` for mutual
+  TLS authentication, or on its own for one-way TLS authentication. If none is
+  provided the gateway **will not** encrypt traffic to the destination.
+
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided
+  to servers to verify the gateway's authenticity. It must be provided if a
+  `key_file` is provided.
+
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the
+  certificate to verify the gateway's authenticity. It must be provided if a
+  `cert_file` is provided.
+
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify
+  during the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#linked-service-parameters
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[listener-service]: /nomad/docs/job-specification/gateway#listener-service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
+[envoy_sd_docs]: https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery
+[SDS]: https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#listeners-services-tls-sds
+[service-default-protocol]: /consul/docs/connect/config-entries/service-defaults#protocol
+[response-headers]: /consul/docs/connect/config-entries/ingress-gateway#listeners-services-responseheaders
+[header modifiers]: /nomad/docs/job-specification/gateway#header-modifier-parameters
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/group.mdx b/content/nomad/v1.8.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..f8338e2129
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,455 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group. These options will be applied to all tasks and
+  services in the group unless a task has its own `consul` block.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `disconnect` <code>([disconnect][]: nil)</code> - Specifies the disconnect 
+  strategy for the server and client for all tasks in this group in case of a 
+  network partition. The tasks can be left unconnected, stopped or replaced 
+  when the client disconnects. The policy for reconciliation in case the client
+  regains connectivity is also specified here.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `prevent_reschedule_on_lost` `(bool: false)` - Defines the reschedule behaviour
+  of an allocation when the node it is running on misses heartbeats.
+  When enabled, if the node it is running on becomes disconnected
+  or goes down, this allocations wont be rescheduled and will show up as `unknown`
+  until the node comes back up or it is manually restarted.
+
+  This behaviour will only modify the reschedule process on the server.
+  To modify the allocation behaviour on the client, see
+  [`stop_after_client_disconnect`](#stop_after_client_disconnect).
+
+  The `unknown` allocation has to be manually stopped to run it again.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+  same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+  This field was deprecated in favour of `replace` on the [`disconnect`] block, 
+  see [example below][disconect_migration] for more details about migrating.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+  This field was deprecated in favour of `stop_after` on the [`disconnect`] block.
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+  This field was deprecated in favour of `lost_after` on the [`disconnect`] block.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` or `disconnect.lost_after` is specified,
+the Nomad server will mark clients that fail to heartbeat as "disconnected" 
+rather than "down", and will mark allocations on a disconnected client as
+"unknown" rather than "lost". These allocations may continue to run on the
+disconnected client. Replacement allocations will be scheduled according to the
+allocations' `disconnect.replace` settings. until the disconnected client 
+reconnects. Once a disconnected client reconnects, Nomad will compare the "unknown" 
+allocations with their replacements and will decide which ones to keep according 
+to the `disconnect.replace` setting. If the `max_client_disconnect` or 
+`disconnect.losta_after` duration expires before the client reconnects, 
+the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` or `disconnect.lost_after` 
+duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+#### Max Client Disconnect and Prevent Reschedule On Lost
+
+Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect      = "12h"
+  prevent_reschedule_on_lost = true
+
+  reschedule {
+    attempts  = 0
+    unlimited = false
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+```
+
+If [`max_client_disconnect`](#max_client_disconnect) is set and
+`prevent_reschedule_on_lost = true`, allocations on disconnected nodes will be
+`unknown` until the `max_client_disconnect` window expires, at which point
+the node will be transition from `disconnected` to `down`. The allocation
+will remain as `unknown` and won't be rescheduled.
+
+#### Migration to `disconnect` block
+
+The new configuration fileds in the disconnect block work exactly the same as the
+ones they are replacing: 
+  * `stop_after_client_disconnect` is replaced by `stop_after`
+  * `max_client_disconnect` is replaced by `lost_after`
+  * `prevent_reschedule_on_lost` is replaced by `replace`
+
+To keep the same behaviour as the old configuration upon reconnection, the
+`reconcile` option should be set to `best_score`.
+
+The following example shows how to migrate from the old configuration to the new one:
+
+```hcl
+job "docs" {
+  group "example" {
+    max_client_disconnect        = "6h"
+    stop_after_client_disconnect = "2h"
+    prevent_reschedule_on_lost   = true
+  }
+}
+```
+Can be directly translated to:
+
+```hcl
+job "docs" {
+  	group "example" {
+      disconnect {
+        lost_after = "6h"
+        stop_after = "2h"
+        replace = false
+        reconcile = "best_score"
+      }
+    }
+  }
+```
+
+All use constrains still apply with the disconnect block as they did before:
+ - `stop_after` and `lost_after` can't be used together.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/consul
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[`disable_rescheduling`]: /nomad/docs/job-specification/reschedule#disabling-rescheduling
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[disconnect]: /nomad/docs/job-specification/disconnect 'Nomad disconnect Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[disconect_migration]: /nomad/docs/job-specification/group#migration_to_disconnect_block
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..91ea784340
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..734fbf6589
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..6cf8bcbd89
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..6f964b533f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/integrations/vault-integration">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..2e92de5824
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://developer.hashicorp.com/nomad/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..0643bb06cc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,181 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The 
+HCL parser's JSON format is unspecified, so the API format is preferred. You can 
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+## Backward Compatibilities
+
+HCL2 syntax closely mirrors HCL1, but has some minor changes. Most existing
+Nomad job specifications will not require any changes.
+
+When you run `nomad job run` or `nomad job plan`, the CLI will report any
+required changes. Also, you can activate a backwards compatibility mode by
+passing `-hcl1` to use Nomad's HCL1 parser instead.
+
+### Blocks
+
+Block syntax is as follows, using unquoted attributes and quoted values:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+HCL2 requires a leading zero for decimal values lower than 1 (e.g. `0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..fb820cf5b8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/runtime/environment
+[expression]: /nomad/docs/job-specification/hcl2/expressions
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.8.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..ec2299274a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,357 @@
+---
+layout: docs
+page_title: identity Block - Job Specification
+description: |-
+  The "identity" block allows tasks to use their Nomad Workload Identity via an
+  environment variable or file.
+---
+
+# `identity` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'identity'],
+    ['job', 'group', 'task', 'identity'],
+    ['job', 'group', 'task', 'service', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. Nomad will create a _default_ identity for all
+workloads, but it is *not* exposed to a task. You may also set additional
+identities intended for use with external applications such as Vault, Consul, or
+OIDC authentication.
+
+For example, the following will expose the default Workload Identity as an
+environment variable and file to the task, and a second Workload Identity
+configured for a third-party OIDC provider:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env         = true
+        file        = true
+
+        # Restart on token renewal to get the new env var
+        change_mode = "restart"
+      }
+
+      identity {
+        name        = "example"
+        aud         = ["oidc.example.com"]
+        file        = true
+        ttl         = "1h"
+
+        # Send a HUP signal when the token file is updated
+        change_mode   = "signal"
+        change_signal = "SIGHUP"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## `identity` Parameters
+
+- `name` `(string: "default")` - The name of the workload identity, which must
+  be unique per task. Only one `identity` block in a task can omit the `name`
+  field.
+- `aud` `([]string: nil)` - The audience field for the workload identity. This
+  should always be set for non-default identities.
+- `change_mode` `(string: "noop")` - Specifies the behavior Nomad should take when the token changes.
+
+  - `"noop"` - take no action. The default since tasks may choose to reload
+      tokens only when their current token gets rejected or implement their own
+      change detection.
+  - `"restart"` - restart the task.
+  - `"signal"` - send a configurable signal to the task. Must set `change_signal`.
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGHUP"` or `"SIGUSR1"`. This option is required if the
+  `change_mode` is `signal`.
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+- `ttl` `(string: "")` - The lifetime of the identity before it expires. The
+  client will renew the identity at roughly half the TTL. This is specified
+  using a label suffix like "30s" or "1h". You may not set a TTL on the default
+  identity. You should always set a TTL for non-default identities.
+
+## Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identities for Consul
+
+Jobs that need access to Consul can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task or service that will access Consul.
+
+You can configure Nomad servers to automatically add default identities for
+Consul using the [`consul.service_identity`][] and [`consul.task_identity`][]
+agent configuration. Upon job registration, the Nomad server updates tasks that
+have a [`consul`][] or [`template`][] block and services that use the Consul
+service provider to include the default identities.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identities configured in the Nomad servers. Identities for
+tasks must have a [`name`](#name) that follows the pattern
+`consul_<cluster name>`. Identities for services do not need to specify a
+`name`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the task
+identity name should be `consul_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Consul clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/consul#cluster">
+  <code>consul.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_consul_wid] section of the Consul
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="3,14-17,30-34">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {}
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_default"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="3-5,16-19,34-38">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {
+      cluster = "prod"
+    }
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_prod"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Workload Identities for Vault
+
+Jobs that need access to Vault can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task that will access Vault.
+
+You can configure Nomad servers to automatically add default identities for
+Vault using the [`vault.default_identity`][] agent configuration. Upon job
+registration, the Nomad server updates tasks that have a [`vault`][] block to
+include the default identity.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identity configured in the Nomad servers. The identity
+[`name`](#name) must follow the pattern `vault_<cluster name>`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the
+identity name should be `vault_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Vault clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/vault#cluster">
+  <code>vault.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_vault_wid] section of the Vault
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="19,21-25">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      identity {
+        name = "vault_default"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="19-21,23-27">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {
+        cluster = "prod"
+      }
+
+      identity {
+        name = "vault_prod"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`template`]: /nomad/docs/job-specification/template
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault`]: /nomad/docs/job-specification/vault
+[int_consul_wid]: /nomad/docs/integrations/consul-integration#nomad-workload-identities
+[int_vault_wid]: /nomad/docs/integrations/vault-integration#nomad-workload-identities
+[taskapi]: /nomad/api-docs/task-api
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/index.mdx b/content/nomad/v1.8.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..4cbe06b145
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+The `service` block can also be specified at the group level. This allows job specification authors
+to create and register services with Consul Service Mesh. A service block specified at the group 
+level must include a [`connect`][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/job.mdx b/content/nomad/v1.8.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..0f1302becd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+    
+    task "docs" {
+      # ...
+    }
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.8.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.8.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..bb361fd493
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with reasonable defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/drivers/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.8.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..6f32810932
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## `meta` Usage Examples
+
+### Templates
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.8.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..e92348246f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.8.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..f03b42e37d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,290 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/network.mdx b/content/nomad/v1.8.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..6003535308
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,362 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+- `cni` <code>([CNIConfig](#cni-parameters): nil)</code> - Sets the custom CNI
+  arguments for a network configuration per allocation, for use with `mode="cni/*`.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `cni` Parameters
+
+- `args` `(map<string><string>: nil)` - Sets CNI arguments for network configuration.
+   These get turned into `CNI_ARGS` per the
+   [CNI spec](https://www.cni.dev/docs/spec/#parameters).
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+This example specifies a static port allocation for the port labeled "lb". Static
+ports bind your job to a specific port on the host they' are placed on. Since
+multiple services cannot share a port, the port must be open in order to place
+your task.
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is necessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### CNI Args
+
+The following example specifies CNI args for the custom CNI plugin specified above.
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+  cni {
+    args = {
+     "nomad.region" : "${node.region}"
+    }
+  }
+}
+```
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/numa.mdx b/content/nomad/v1.8.x/content/docs/job-specification/numa.mdx
new file mode 100644
index 0000000000..a67e38cbad
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/numa.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: numa Block - Job Specification
+description: |-
+  The "numa" block is used configure NUMA aware scheduling strategy for a task.
+---
+
+# `numa` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'numa']} />
+
+The `numa` block is used to configure how Nomad will assign CPU cores for a task
+while taking the [NUMA hardware topology][numa_wiki] of a node into consideration.
+Workloads that are sensitive to memory latency can perform significantly better
+when pinned to CPU cores on the same NUMA node.
+
+<EnterpriseAlert>
+
+This functionality only exists in Nomad Enterprise. This is not
+present in the source available version of Nomad.
+</EnterpriseAlert>
+
+<Note>
+
+NUMA aware scheduling is currently limited to Linux.
+</Note>
+
+```hcl
+job "example" {
+  group "group" {
+    task "task" {
+      resources {
+        cores = 8
+        numa {
+          affinity = "require"
+        }
+      }
+    }
+  }
+}
+```
+
+In the example above, the task is requesting Nomad to reserve 8 CPU cores, all
+of which must be colocated on the same hardware NUMA node. The Nomad scheduler
+will ensure the task is placed on a Nomad node with sufficient unused CPU cores
+in a compatible configuration.
+
+Configuring the `numa` block requires the task specifies CPU resources using
+the [`cores`][cores] parameter.
+
+# `numa` Parameters
+
+- `affinity` `(string: "none")` - Specifies the strategy Nomad will use when
+  selecting CPU cores to assign to a task. Possible values are `"none"`,
+  `"prefer"`, or `"require"`.
+  - `none` - Nomad is free to allocate CPU cores using any strategy. Nomad uses
+  this freedom to allocate cores in such a way that minimizes the amount of
+  fragmentation of core availability per NUMA node. It does so by bin-packing
+  the chosen cores onto the NUMA nodes with the fewest number of cores available.
+  - `prefer` - Nomad will select the set of CPU cores on a node that minimizes
+  the total distance between those cores, but does not limit those CPU core
+  selections to come from a single NUMA node.
+  - `require` - Nomad will select a set of CPU cores that are strictly colocated
+  on the same hardware NUMA node. If there are no Nomad nodes with a sufficient
+  number of available cores in a compatible configuration, task placement will
+  fail due to exhausted resources.
+
+<Note>
+
+  The `require` affinity option causes fragmentation of available CPU cores
+  based on the NUMA node the selected cores are associated with. Use it for
+  workloads known to be highly sensitive to memory latencies. A cluster where
+  all jobs make use of the `require` affinity option will not be able to make
+  efficient use of available resources.
+</Note>
+
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.8.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..bf914761dc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.8.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..021a727b09
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+## `periodic` Parameters
+
+- `cron` (_deprecated_: Replaced by `crons` in 1.6.2) `(string)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`. Either `cron` or `crons` must be set, but not both.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions. Either `cron` or `crons` must be set, but not both.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.8.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..5b95f5f2f9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul Connect][]. It is valid only within the context of
+a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation][envoy_dynamic_config]
+  for details. Keys and values support [runtime variable interpolation][].
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path
+  configuration for Envoy. See Consul's [Expose Paths Configuration
+  Reference][expose_path_ref] for more information.
+- `local_service_address` `(string: "127.0.0.1")` - The address the local
+  service binds to. Useful to customize in clusters with mixed Connect and
+  non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in
+  clusters with mixed Connect and non-Connect services.
+- `transparent_proxy` <code>([transparent_proxy][]: nil)</code> - Used to enable
+  [transparent proxy][tproxy] mode, which allows the proxy to use Consul service
+  intentions to automatically configure upstreams, and configures iptables rules
+  to force traffic from the allocation to flow through the proxy.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of
+  each upstream service that this sidecar proxy communicates with.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams
+configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+The following example is a proxy specification that includes transparent proxy
+configuration. Note that with transparent proxy, you will not need to configure
+an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+[Consul Connect]: /nomad/docs/integrations/consul-connect
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[runtime variable interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
+[envoy_dynamic_config]: /consul/docs/connect/proxies/envoy#dynamic-configuration
+[expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[transparent_proxy]: /nomad/docs/job-specification/transparent_proxy
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.8.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..97545b2e4c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified at the job
+level, the configuration will apply to all groups within the job. If the
+reschedule block is present on both the job and the group, they are merged with
+the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its
+task statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `attempts` and `interval` fields are not used.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.8.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..547e374151
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `numa` <code>([Numa][]: &lt;optional&gt;)</code> - Specifies the
+  NUMA scheduling preference for the task. Requires the use of `cores`.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+- `secrets` <code>(`int`: &lt;optional&gt;)</code> - Specifies the size of the
+  [`secrets/`][] directory in MB, on platforms where the directory is a
+  tmpfs. If set, the scheduler adds the `secrets` value to the `memory` value
+  when allocating resources on a client, and this value will be included in the
+  allocated resources shown by the `nomad alloc status` and `nomad node status`
+  commands. If unset, the client will allocate 1 MB of tmpfs space and it will
+  not be counted for scheduling purposes or included in allocated resources. You
+  should not set this value if the workload will be placed on a platform where
+  tmpfs is unsupported, because it will still be counted for scheduling
+  purposes.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2000 MB:
+
+```hcl
+resources {
+  memory = 2000
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`raw_exec`, `docker`, `exec`, and `java` task drivers.  Consult the
+documentation of community-supported task drivers for their memory
+oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][tutorial_quota] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/drivers/docker#cpu
+[exec_cpu]: /nomad/docs/drivers/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[tutorial_quota]: /nomad/tutorials/governance-and-policy/quotas
+[numa]: /nomad/docs/job-specification/numa 'Nomad NUMA Job Specification'
+[`secrets/`]: /nomad/docs/runtime/environment#secrets
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.8.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..7347deba68
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,194 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all 
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### Disabling restart
+
+To disable restarting, set the `attempts` parameter to zero and `mode` to `"fail"`.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+  }
+}
+```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.8.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/schedule.mdx b/content/nomad/v1.8.x/content/docs/job-specification/schedule.mdx
new file mode 100644
index 0000000000..454b359995
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/schedule.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: schedule Block - Job Specification
+description: |-
+  Time based task execution is enabled by using the "schedule" task block.
+---
+
+# `schedule` Block
+
+<EnterpriseAlert />
+
+<Placement groups={['job', 'group', 'task', 'periodic']} />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes. 
+
+Time based task execution is enabled by using the `schedule` block. The
+`schedule` block controls when a task is allowed to be running.
+
+Unlike [`periodic`][periodic] jobs, the `schedule` block applies to individual
+tasks. The Nomad Client starts and stops tasks at the specified time without
+interaction with the Nomad Servers. This means time based task execution works
+even when a Client is disconnected from Servers. The task's resources remain
+allocated even outside the `schedule` when the task itself is stopped.
+
+```hcl
+job "docs" {
+  group "tbte" {
+    task "scheduled" {
+      schedule {
+        cron {
+          start    = "30 9 * * MON-FRI *"
+          end      = "0 16"
+          timezone = "America/New_York"
+        }
+      }
+    }
+  }
+}
+```
+
+## `schedule` Parameters
+
+The `schedule` block must have a `cron` block containing:
+
+- `start` `(string: <required>)` - When the task should be started. Specified in 6 field
+  [cron format][cron] (no seconds) without `,` or `/` characters.
+
+- `end` `(string: <required>)` - When the task should be stopped
+  ([`kill_signal`][kill_signal] and [`kill_timeout`][kill_timeout] apply).
+  Specified in 2 field [cron format][cron] (minute and hour) without `,` or `/`
+  characters.
+
+- `timezone` `(string: "Local")` - What time zone the `start` and `end` times
+  are specified in. Defaults to the local time zone of the Nomad Client the job
+  is scheduled onto.
+
+## Limitations
+
+- Job deployments outside of the specified `schedule` will be unable to
+  succeed. To update a job using time based task execution outside of its
+  schedule, do a [force
+  update](/nomad/docs/job-specification/update#max_parallel-0).
+
+- Overnight schedules are currently not supported. Adjusting the `timezone`
+  should allow converting overnight schedules to times within a single day.
+
+[periodic]: /nomad/docs/job-specification/periodic
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/service.mdx b/content/nomad/v1.8.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..20a8f8cab9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,538 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+
+        identity {
+          aud = ["consul.io"]
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+The `service` block can also be at task group level.
+This enables services in the same task group to opt into [Consul
+Service Mesh][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use, when the `provider` is `"consul"`. The Nomad client
+  will retrieve a Consul token from the cluster configured in the agent
+  configuration with the same [`consul.name`][]. In Nomad Community Edition,
+  this field is ignored.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `identity` <code>([Identity][identity_block]: nil)</code> - Specifies a
+  Workload Identity to use when obtaining Service Identity tokens from Consul to
+  register the service. Only available where `provider = "consul"`. Typically
+  this can be omitted so that Nomad will fall back to the server's
+  [`consul.service_identity`][] block.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[identity_block]: /nomad/docs/job-specification/identity
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.8.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..584ef6cf02
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       "test-key" = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.8.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..6fc00a0151
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.8.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..d4e2f99df9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,205 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter.
+
+By default, when `spread` is omitted, the scheduler will attempt to place
+allocations from the same job on different nodes (and binpacked between
+jobs). When using `spread` the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target
+percentage defined in the spread block. Spread scores are combined with other
+scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to
+express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler. If no
+nodes match a given spread criteria, placement is still successful. To avoid
+scoring every node for every placement, allocations may not be perfectly
+spread. Spread works best on attributes with similar number of nodes:
+identically configured racks or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client
+metadata][client-meta].  Additionally, spread may be specified at the [job][job]
+and [group][group] levels for ultimate flexibility. Job level spread criteria
+are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## Comparison to `spread` Scheduling Algorithm
+
+The `spread` block is not the same concept as setting the [scheduler
+algorithm][] to `"spread"` instead of `"binpack"`. Setting the scheduler
+algorithm impacts all jobs on a cluster (or node pool), and adjusts the tendency
+of the scheduler to place workloads from different jobs on the same set of nodes
+or not. The `spread` block impacts how the scheduler places allocations for a
+given job.
+
+## Scheduling Performance
+
+Using the `spread` block can have significant impact on scheduling
+performance. For each allocation in a `service` and `batch` job, the scheduler
+iterates over nodes until it finds a small number of feasible nodes. Those
+feasible nodes are then scored to find the best placement.
+
+When `spread` is omitted, this limit is 2 for batch jobs and the log<sub>2</sub>
+of the total number of nodes in the datacenter and node pool (with a minimum of
+2) for service jobs. When the `spread` block is present, the scheduler instead
+scores a number of nodes in the datacenter and node pool equal to the task group
+count (with a maximum of 100) per allocation. This can result in
+order-of-magnitude increases in scheduling times.
+
+To monitor scheduling times potentially impacted by `spread` blocks, examine the
+`nomad.nomad.worker.invoke_scheduler.*` found in the [Key Metrics][] table. You
+can reduce scheduling times by avoiding `spread` and instead relying on the
+default distribution of a job across multiple nodes. If this is not possible,
+you may consider reducing the size of the node pool or datacenter to reduce the
+number of nodes available for the scheduler to consider.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+[Key Metrics]: /nomad/docs/operations/metrics-reference#key-metrics
+[scheduler algorithm]: /nomad/docs/commands/operator/scheduler/set-config#scheduler-algorithm
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/task.mdx b/content/nomad/v1.8.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..43b743bd97
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `consul` <code>([Consul][consul_jobspec]: nil)</code> - Specifies Consul
+  configuration options specific to the task.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] and [rkt][] images specify their own default users. This can only
+  be set on Linux platforms, and clients can restrict
+  [which drivers][user_drivers] are allowed to run tasks as
+  [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_jobspec]: /nomad/docs/job-specification/consul
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/template.mdx b/content/nomad/v1.8.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..2866a74ec4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,827 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad Integration
+
+### Nomad Services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on
+  the host as root (unless Nomad is configured to run as a non-root user).
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/transparent_proxy.mdx b/content/nomad/v1.8.x/content/docs/job-specification/transparent_proxy.mdx
new file mode 100644
index 0000000000..112edb8618
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/transparent_proxy.mdx
@@ -0,0 +1,174 @@
+---
+layout: docs
+page_title: transparent_proxy Block - Job Specification
+description: |-
+  The "transparent_proxy" block allows specifying options for configuring Envoy
+  in Consul Connect transparent proxy mode.
+---
+
+# `transparent_proxy` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'transparent_proxy',
+  ]}
+/>
+
+The `transparent_proxy` block configures the Envoy sidecar proxy to act as a
+Consul Connect [transparent proxy][tproxy]. This simplifies the configuration of
+Consul Connect by eliminating the need to configure [`upstreams`][] blocks in
+Nomad. Instead, the Envoy proxy will determines its configuration entirely from
+Consul [service intentions][].
+
+When transparent proxy is enabled traffic will automatically flow through the
+Envoy proxy. If the local Consul agent is serving DNS, Nomad will also set up
+the task's nameservers to use Consul. This lets your workload use the [virtual
+IP][] DNS name from Consul, rather than configuring a `template` block that
+queries services.
+
+Using transparent proxy has some important restrictions:
+
+* You can only have a single `connect` block in any task group that uses
+  transparent proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`](#no_dns), see below).
+* The node where the allocation is placed must be configured as described in
+  the Service Mesh integration documentation for [Transparent Proxy][].
+
+## `transparent_proxy` Parameters
+
+* `exclude_inbound_ports` `([]string: nil)` - A list of inbound ports to exclude
+  from the inbound traffic redirection. This allows traffic on these ports to
+  bypass the Envoy proxy. These ports can be specified as either [network port
+  labels][port_labels] or as numeric ports. Nomad will automatically add the
+  following to this list:
+  * The [`local_path_port`][] of any [`expose`][] block.
+  * The port of any service check with [`expose=true`][check_expose] set.
+  * The port of any `network.port` with a [`static`][] value.
+* `exclude_outbound_cidrs` `([]string: nil)` - A list of CIDR subnets that
+  should be excluded from outbound traffic redirection. This allows traffic to
+  these subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_ports`; CIDR subnets listed here are excluded regardless of
+  the port.
+* `exclude_outbound_ports` `([]int: nil)` - A list of port numbers that should
+  be excluded from outbound traffic redirection. This allows traffic to these
+  subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_cidrs`; ports listed here are excluded regardless of the
+  CIDR.
+* `exclude_uids` `([]string: nil)` - A list of Unix user IDs (UIDs) that should
+  be excluded from outbound traffic redirection. When unset, only the Envoy
+  proxy's user will be allowed to bypass the iptables rule.
+* `no_dns` `(bool: false)` - By default, Consul will be set as the nameserver
+  for the workload and IP tables rules will redirect DNS queries to Consul. If
+  you want only external DNS, set `no_dns=true`. You will need to add your own
+  CIDR and port exclusions for your DNS nameserver. You cannot set
+  [`network.dns`][] if `no_dns=false`.
+* `outbound_port` `(int: 15001)` - The port that Envoy will bind on inside the
+  network namespace. The iptables rules created by `consul-cni` will force
+  traffic to flow to this port. You should only set this value if you have
+  specifically set the [`outbound_listener_port`][] in your Consul proxy
+  configuration. You can change the default value for a given node via [client
+  metadata](#client-metadata) (see below).
+* `uid` `(string "101")` - The Unix user ID (UID) used by the Envoy proxy. You
+  should only set this value if you have a custom build of the Envoy container
+  image which uses a different UID. You can change the default value for a given
+  node via [client metadata](#client-metadata) (see below).
+
+## Client Metadata
+
+You can change the default [`outbound_port`](#outbound_port) and [`uid`](#uid)
+for a given client node by updating the node metadata via the [`nomad node meta
+apply`][] command. The attributes that can be updated are:
+
+* `connect.transparent_proxy.default_uid`: Sets the default value of
+  [`uid`](#uid) for this node.
+* `connect.transparent_proxy.default_outbound_port`: Sets the default value of
+  [`outbound_port`](#outbound_port) for this node.
+
+For example, to set the default value for the `uid` field to 120:
+
+```shell-session
+$ nomad node meta apply connect.transparent_proxy.default_uid=120
+$ nomad node meta read -json | jq -r '.Dynamic | ."connect.transparent_proxy.default_uid"'
+120
+```
+
+You should not normally need to set these values unless you are using custom
+Envoy images.
+
+## Examples
+
+### Minimal Example
+
+The following example is a minimal transparent proxy specification. Note that
+with transparent proxy, you will not need to configure an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+If you had a downstream task group `count-dashboard` that needed to connect to
+an upstream task group `count-api` listening on port 9001, you could create a
+Consul service intention with the following specification:
+
+```hcl
+Kind = "service-intentions"
+Name = "count-api"
+Sources = [
+  {
+    Name   = "count-dashboard"
+    Action = "allow"
+  }
+]
+```
+
+And then the downstream service `count-dashboard` could reach the `count-api`
+service by making requests to `http://count-api.virtual.consul`.
+
+### External DNS
+
+The following example is a transparent proxy specification where external DNS is
+used. To find the address of other allocations in this configuration, you will
+need to use a [`template`][] block to query Consul.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+      excluded_outbound_ports = [53]
+      excluded_outbound_cidrs = ["208.67.222.222/32", "208.67.220.220/32"]
+      no_dns                  = true
+    }
+  }
+}
+```
+
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[service intentions]: /consul/docs/connect/config-entries/service-intentions
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[port_labels]: /nomad/docs/job-specification/network#port-parameters
+[`local_path_port`]: /nomad/docs/job-specification/expose#local_path_port
+[`expose`]: /nomad/docs/job-specification/expose
+[check_expose]: /nomad/docs/job-specification/service#expose
+[`static`]: /nomad/docs/job-specification/network#static
+[`outbound_listener_port`]: /consul/docs/connect/proxies/proxy-config-reference#outbound_listener_port
+[`template`]: /nomad/docs/job-specification/template#consul-integration
+[`nomad node meta apply`]: /nomad/docs/commands/node/meta/apply
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[Transparent Proxy]: /nomad/docs/integrations/consul/service-mesh#transparent-proxy
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/ui.mdx b/content/nomad/v1.8.x/content/docs/job-specification/ui.mdx
new file mode 100644
index 0000000000..c9792168b2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/ui.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: ui Block - Job Specification
+description: |-
+  The "ui" block allows lets users add description and helpful links to their
+  job page in the Nomad Web UI.
+---
+
+# `ui` Block
+
+<Placement
+  groups={[
+    ['job', 'ui'],
+  ]}
+/>
+
+The `ui` block provides options to modify the presentation of the Job index page
+in the Web UI. When specified, a description and any number of links will be
+added to the top of the job page in question.
+
+The following will provide the Web UI with a job description and a pair of links:
+
+## `ui` Parameters
+
+- `description` `(string: "")` - The markdown-enabled description of the job. We
+  support [GitHub Flavored Markdown](https://github.github.com/gfm/).
+- `link` `(map<string|string>: nil)` - A link that should show up in the header
+  of the job index page in the Web UI. A job can have any number of links, and
+  they must contain both a string `label` and `url`.
+
+## `ui` Example
+
+```hcl
+job "docs" {
+  ui {
+    description = "A job that uses **Nomad Variables**"
+    link {
+      label = "Learn more about Nomad"
+      url   = "https://developer.hashicorp.com/nomad"
+    }
+    link {
+      label = "Nomad on GitHub"
+      url   = "https://github.com/hashicorp/nomad"
+    }
+  }
+  # ...
+}
+```
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/update.mdx b/content/nomad/v1.8.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..3e1243a165
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.8.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..58ad223d5f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul Connect][] proxy routes to. It is valid only within the
+context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect Guide][]. Note that using
+`upstream` may not be necessary if you have configured the proxy with the
+[`transparent_proxy`][] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation][consul_expose_path_ref]
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_partition` `(string: "")` - Name of the Cluster admin partition containing the upstream service.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[Consul Connect]: /nomad/docs/integrations/consul-connect
+[Consul Connect Guide]: /consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
+[consul_expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.8.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..2f95ff0a2b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        cluster  = "default"
+        role     = "prod"
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `disable_file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `allow_token_expiration` `(bool: false)` - Specifies that Nomad clients should
+  not attempt to renew a task's Vault token, allowing it to expire. This should
+  only be used when a secret is requested from Vault once at the start of a task
+  or in a short-lived prestart task. Long-running tasks should never set
+  `allow_token_expiration=true` if they obtain Vault secrets via `template`
+  blocks, as the Vault token will expire and the template runner will continue
+  to make failing requests to Vault until its [`vault_retry`][] attempts are
+  exhausted, at which point the task will fail.
+
+  When Nomad has been configured to use [Workload Identity with Vault][], Nomad
+  clients will automatically detect when tokens cannot be refreshed (for
+  example, when the Vault auth method is configured to issue batch tokens). In
+  this case, the `allow_token_expiration` option will be implicitly set to
+  `true` by the client. The [legacy Vault authentication workflow][] cannot
+  automatically detect this.
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Vault cluster to use. The Nomad client will retrieve a Vault token from the
+  cluster configured in the agent configuration with the same
+  [`vault.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies. This field may only be used with the legacy Vault
+  authentication workflow and not with JWT and workload identity. It is
+  deprecated in favor of the `role` field and will be removed in Nomad 1.10.
+
+- `role` `(string: "")` - Specifies the Vault role used when retrieving a token
+  from Vault using JWT and workload identity. If not specified the client's
+  [`create_from_role`][] value is used.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+Vault policies from the "prod" role attached.
+
+```hcl
+vault {
+  role = "prod"
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  role = "prod"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private Token and Change Modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  role         = "prod"
+  change_mode  = "noop"
+  env          = false
+  disable_file = true
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  role      = "prod"
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[`create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[docker]: /nomad/docs/drivers/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
+[`vault.name`]: /nomad/docs/configuration/vault#name
+[`vault_retry`]: /nomad/docs/configuration/client#vault_retry
+[Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[legacy Vault authentication workflow]: /nomad/docs/integrations/vault/acl#authentication-without-workload-identity-legacy
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.8.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..58ec2bd352
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.8.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.8.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..01929d2277
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+- `selinux_label``(string: "")` - Specifies the SELinux label for the mount.
+  This is only supported on Linux hosts and when supported by the task driver. Refer to the task driver documentation for more information. Possible 
+  values are:
+
+  - `Z` -  Specifies that the volume content is private and unshared between 
+    containers.
+  - `z` - Specifies that the volume content is shared among containers.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.8.x/content/docs/networking/cni.mdx b/content/nomad/v1.8.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..0cee27400f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/networking/cni.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: CNI plugins and bridge networking
+description: |-
+  Learn how to install Container Network Interface (CNI) reference plugins, configure Nomad's bridge networking, and how to use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface (CNI)
+
+This page show you how to install the [CNI reference plugins][cni-plugin-docs]
+on your Linux distribution and configure bridge networking on your Nomad
+clients. You can apply this guide's workflow to installing any plugin that
+complies with the [Container Network Interface (CNI) Specification][cni-spec],
+but you should verify plugin compatibility with Nomad before deploying in
+production.
+
+## Introduction
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, [use a CNI network with a
+job](#use-a-cni-network-with-a-job).
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a CNI bridge mode configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration). Refer to
+the external [configuration
+format](https://www.cni.dev/docs/spec/#example-configuration) for a complete
+explanation of the fields.
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode.
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,20,32">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Use a CNI network with a job
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`. Nomad then schedules the workload on client nodes
+that have fingerprinted a CNI configuration with the given name. For example, to
+use the configuration named `mynet`, you should set the task group's network
+mode to `cni/mynet`. Nodes that have a network configuration defining a network
+named `mynet` in their `cni_config_dir` are eligible to run the workload.
+
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.8.x/content/docs/networking/index.mdx b/content/nomad/v1.8.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..4a5aa1c5fd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/networking/index.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Learn about Nomad's networking internals and how it compares with other
+  tools.
+---
+
+# Networking
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+Nomad networking is quite different from what you may familiar with from other
+tools. This section explains how networking works in Nomad, some of the
+different patterns and configurations you are likely to find and use, and how
+Nomad differs from other tools in this aspect.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/concepts/architecture#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/runtime/environment#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#template-examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+### Container Network Interface (CNI) reference plugins
+
+Nomad's bridge network leverages [CNI reference
+plugins](https://github.com/containernetworking/plugins) to provide an
+operating-system agnostic interface to configure workload networking. Nomad's
+network plugin support extends Nomad's built-in compute resource scheduling to
+allow scheduling tasks with specialty network configurations, which Nomad
+implements with a combination of CNI reference plugins and CNI configuration
+files.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/networking/service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/integrations/consul-connect).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/drivers/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/drivers/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/drivers/docker#network_mode)
+documentation and the [Networking](/nomad/docs/drivers/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [Service Discovery](/nomad/docs/networking/service-discovery)
+- [Service Mesh](/nomad/docs/networking/service-mesh)
+- [Container Network Interface](/nomad/docs/networking/cni) plugins guide
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.8.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.8.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..5017babf19
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,144 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Learn about how service discovery works in Nomad to connect workloads.
+---
+
+# Service discovery
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.8.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.8.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2828748c9f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Learn about how service mesh works in Nomad to securely connect and isolate
+  your workloads.
+---
+
+# Service mesh
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..07d9331ac2
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Nomad as an alternative to Kubernetes
+---
+
+# An alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c43c44c12b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: Nomad vs. Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Nomad vs. Kubernetes
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes:
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..c6f99e1633
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Comparison between Nomad and Kubernetes
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.8.x/content/docs/operations/aws-oidc-provider.mdx b/content/nomad/v1.8.x/content/docs/operations/aws-oidc-provider.mdx
new file mode 100644
index 0000000000..e98015b612
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/aws-oidc-provider.mdx
@@ -0,0 +1,403 @@
+---
+layout: docs
+page_title: Federate access to AWS with Nomad Workload Identity
+description: |-
+  Integrate Nomad as an OpenID Connect (OIDC) provider with AWS IAM identity and federate access to AWS resources.
+---
+
+# Federate access to AWS with Nomad Workload Identity
+
+This page describes how to integrate Nomad with AWS IAM as an OpenID Connect (OIDC) provider and
+use [Workload Identity] to federate access to AWS resources and services. In this workflow, Nomad
+is the [OpenID Connect Provider] (OP or OIDC provider) and generates JSON Web Tokens (JWTs) which
+serve as workload identities. AWS IAM is the Relying Party (RP) and validates these workload
+identity tokens with Nomad before it permits federated access to resources and services.
+
+## Prerequisites
+
+To integrate Nomad and AWS IAM identity, you need a running Nomad cluster that
+meets the following prerequisites:
+
+- Nomad v1.7.x or later
+- TLS enabled
+
+The instructions on this page also assume the following:
+
+- Your AWS account has the necessary permissions to create IAM roles, policies, hosted zones,
+  and certificates.
+- Terraform is installed locally and 
+  [configured to communicate with AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication-and-configuration).
+
+## Workflow
+
+The process to integrate Nomad as an OIDC provider with AWS consists of the following steps:
+
+1. Create the required AWS resources:
+    - [Route 53 hosted zone](#create-a-hosted-zone)
+    - [AWS Certificate Manager SSL certificates](#generate-ssl-certificates)
+    - [Load balancer and listener](#create-an-application-load-balancer)
+    - [DNS Alias for the load balancer](#create-a-dns-alias)
+    - [OIDC Identity Provider](#create-an-oidc-identity-provider)
+    - [AWS IAM role](#create-an-iam-policy-for-oidc-federated-users)
+1. Update the Nomad server configuration.
+1. Create a jobspec file that accesses AWS and then run it to verify your configuration.
+
+## Create and configure AWS resources
+
+To use Nomad as an identity provider, you need to have a trusted SSL certificate for the
+domain used by the cluster. The following example uses AWS Certificate Manager (ACM).
+
+### Create a hosted zone
+
+Use the [`aws_route53_zone` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone).
+
+```hcl
+variable "domain_name" {
+    type = string
+    default = "<DOMAIN_NAME>"
+}
+
+resource "aws_route53_zone" "example" {
+    name = var.domain_name
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port. `var.domain_name` is used
+throughout the examples on this page to reference `<DOMAIN_NAME>`.
+
+### Generate SSL certificates
+
+Use the [`aws_acm_certificate`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate)
+and [`aws_acm_certificate_validation`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate_validation) resources to create a request and provide validation for an SSL
+certficiate.
+
+```hcl
+variable "zone_id" {
+  type    = string
+  default = "<HOSTED_ZONE_ID>"
+}
+
+resource "aws_acm_certificate" "example" {
+  domain_name       = var.domain_name
+  validation_method = "DNS"
+
+  lifecycle {
+    create_before_destroy = true
+  }
+}
+
+resource "aws_route53_record" "cert_dns" {
+  allow_overwrite = true
+  name            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_name
+  records         = [tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_value]
+  type            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_type
+  zone_id         = var.zone_id
+  ttl             = 60
+}
+
+resource "aws_acm_certificate_validation" "example" {
+  certificate_arn         = aws_acm_certificate.example.arn
+  validation_record_fqdns = [aws_route53_record.cert_dns.fqdn]
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+
+### Create an Application Load Balancer
+
+Use the [`aws_lb` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb).
+
+```hcl
+resource "aws_lb" "test" {
+  name               = "test-lb-tf"
+  internal           = false
+  load_balancer_type = "application"
+  security_groups    = [<SECURITY_GROUP_ID>]
+  subnets            = [<SUBNET_IDS>]
+
+  enable_deletion_protection = true
+
+  access_logs {
+    bucket  = <S3_BUCKET_ID>
+    prefix  = "test-lb"
+    enabled = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<SECURITY_GROUP_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#security_groups):
+A list of security groups IDs that you want to apply to the load balancer.
+- [`<SUBNET_IDS>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#subnets):
+A list of subnet IDs that you want to attach to the load balancer.
+- [`<S3_BUCKET_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#bucket):
+The ID of an S3 bucket to store the load balancer access logs in.
+
+### Create a load balancer listener
+
+Use the [`aws_lb_listener` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener).
+
+```hcl
+resource "aws_lb_listener" "example" {
+  load_balancer_arn = <LB_ARN>
+  port              = "443"
+  protocol          = "HTTPS"
+  ssl_policy        = "ELBSecurityPolicy-2016-08"
+  certificate_arn   = <CERT_ARN>
+
+  default_action {
+    type             = "forward"
+    target_group_arn = <LB_TARGET_GROUP_ARN>
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<LB_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#load_balancer_arn):
+The AWS resource name of the load balancer. This will be `aws_lb.test.arn` if you are using the
+examples from this page.
+- [`<CERT_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#certificate_arn):
+The AWS resource name of the load balancer's certificate. This will be
+`aws_acm_certificate_validation.example.certificate_arn` if you are using the examples from this
+page.
+- [`<LB_TARGET_GROUP_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#target_group_arn): The AWS resource name of the target group for the load balancer to route traffic to. This group
+includes your Nomad server instances.
+
+### Create a DNS Alias
+
+Use the [`aws_route53_record` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record).
+
+```hcl
+resource "aws_route53_record" "www" {
+  zone_id = <HOSTED_ZONE_ID>
+  name    = var.domain_name
+  type    = "A"
+
+  alias {
+    name                   = <LB_ALIAS_DNS_NAME>
+    zone_id                = <LB_ALIAS_ZONE_ID>
+    evaluate_target_health = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+- [`<LB_ALIAS_DNS_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#name):
+The DNS
+name of the load balancer. This will be `aws_lb.test.dns_name` if you are using the examples
+from this page.
+- [`<LB_ALIAS_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The zone ID of the load balancer. This will be `aws_lb.test.zone_id` if you are using the
+examples from this page.
+
+### Create an OIDC Identity Provider
+
+Use the [`aws_iam_openid_connect_provider` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider).
+
+```hcl
+data "tls_certificate" "example" {
+  url = <CERT_DOMAIN_NAME>
+}
+
+resource "aws_iam_openid_connect_provider" "nomad" {
+  # Nomad HTTPS URL
+  url = <CERT_DOMAIN_NAME>
+
+  client_id_list = [
+    "aws",
+  ]
+
+  thumbprint_list = [data.tls_certificate.example.certificates.0.sha1_fingerprint]
+}
+```
+
+This configuration requires the following information:
+- [`<CERT_DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider#url):
+The domain name of the load balancer certificate. This will be
+`aws_acm_certificate.example.domain_name` if you are using the examples from this page.
+
+### Create an IAM policy for OIDC Federated Users
+
+Use the [`aws_iam_role` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role)
+to create an appropriate IAM role for workloads acting as federated users. This will be 
+specific to your use case. The following example allows workloads access to S3 buckets.
+
+```hcl
+# Variables for OIDC provider and AWS account
+variable "oidc_provider" {
+  description = "The OIDC provider URL"
+  type        = string
+  default     = "<DOMAIN_NAME>"
+}
+
+variable "aws_account_id" {
+  description = "AWS account ID"
+  type        = string
+  default     = "<AWS_ACCOUNT_ID>"
+}
+
+data "aws_iam_policy_document" "assume_role" {
+  statement {
+    effect = "Allow"
+
+    principals {
+      type        = "Federated"
+      identifiers = ["arn:aws:iam::${var.aws_account_id}:oidc-provider/${var.oidc_provider}"]
+    }
+
+    actions = ["sts:AssumeRoleWithWebIdentity"]
+
+    condition {
+      test     = "StringEquals"
+      variable = "${var.oidc_provider}:aud"
+      values   = ["aws"]
+    }
+  }
+}
+
+# Create an IAM role with the assume role policy generated above
+resource "aws_iam_role" "s3_all_access_role" {
+  name               = "s3_all_access_role"
+  assume_role_policy = data.aws_iam_policy_document.assume_role.json
+
+  tags = {
+    tag-key = "tag-value"
+  }
+}
+
+# Inline policy that defines what the role can do (full S3 access)
+data "aws_iam_policy_document" "s3_access_policy" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "s3:*",
+      "s3-object-lambda:*"
+    ]
+
+    resources = ["*"] # You can scope this down to specific S3 buckets if necessary
+  }
+}
+
+# Create a policy resource from the inline policy document above
+resource "aws_iam_policy" "policy" {
+  name        = "nomad-oidc-policy"
+  description = "A policy for federated Nomad OIDC"
+  policy      = data.aws_iam_policy_document.s3_access_policy.json
+}
+
+# Attach the S3 access policy to the IAM role
+resource "aws_iam_role_policy_attachment" "test-attach" {
+  role       = aws_iam_role.s3_all_access_role.name
+  policy_arn = aws_iam_policy.policy.arn
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+
+## Update the Nomad server configuration
+
+After you configure AWS, modify the Nomad server configuration file. Add the
+[`oidc_issuer` attribute](/nomad/docs/configuration/server#oidc_issuer) and set the value
+to the domain name for the Nomad cluster. This [enables the HTTP endpoint in Nomad](https://developer.hashicorp.com/nomad/docs/configuration/server#oidc_issuer) that allows third parties to discover Nomad's OIDC
+configuration.
+
+```hcl
+server {
+  enabled = true
+  [...]
+  oidc_issuer = "https://<DOMAIN_NAME>"
+  [...]
+}
+```
+
+This configuration requires the following information:
+- `<DOMAIN_NAME>`: The domain name of your Nomad cluster without the protocol or port.
+
+Restart the Nomad server agent to apply the configuration changes.
+
+## Create and run a sample jobspec file
+
+Create and run a jobspec file to validate your configuration. The following file is named `s3-upload.nomad.hcl`, add the following configuration to it, and
+save the file.
+
+```hcl
+job "s3" {
+  type = "batch"
+  group "bucket" {
+    task "copy" {
+      driver = "docker"
+      config {
+        image = "public.ecr.aws/aws-cli/aws-cli"
+        command = "s3"
+        args = ["cp", "/local/test.txt", "s3://<S3_BUCKET_NAME>/test-nomad.txt"]
+      }
+
+      identity {
+        name = "aws"
+        aud = ["aws"] 
+        file = true
+        ttl = "1h" 
+        change_mode = "restart"
+      }
+
+      template {
+        destination = "local/test.txt"
+        change_mode = "restart"
+        data        = <<EOF
+Job:          {{ env "NOMAD_JOB_NAME" }}
+Alloc:        {{ env "NOMAD_ALLOC_ID" }}
+EOF
+      }
+
+      env {
+        AWS_ROLE_ARN = "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>"
+        # The format of the token file is nomad_$NAME_OF_IDENTITY.jwt
+        AWS_WEB_IDENTITY_TOKEN_FILE = "${NOMAD_SECRETS_DIR}/nomad_aws.jwt"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+This configuration requires the following information:
+- `<S3_BUCKET_NAME>`: The name of the S3 bucket where the test file will be saved.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+- `<IAM_ROLE_NAME>`: The name of the IAM role from previous steps. This will be
+`s3_all_access_role` if you are using the examples from this page.
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run s3-upload.nomad.hcl
+```
+
+Verify that the job completed successfully.
+
+```shell-session
+$ nomad job status s3
+```
+
+Verify that the file was also uploaded to the S3 bucket.
+
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[OpenID Connect Provider]: https://openid.net/developers/how-connect-works/
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/operations/benchmarking.mdx b/content/nomad/v1.8.x/content/docs/operations/benchmarking.mdx
new file mode 100644
index 0000000000..02816c0548
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/benchmarking.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Benchmarking Nomad
+description: |-
+  Load testing Nomad by utilizing the Nomad Bench project.
+---
+
+# Nomad Bench
+
+The Nomad Bench project provides reusable infrastructure automation to run test scenarios in order
+to collect metrics and data from Nomad clusters running at scale. The core goal of the project is
+to achieve reproducible large scale test scenarios so we can better understand how Nomad scales
+and uncover problems that are only detected in large cluster deployments. It is also used to
+perform release soak testing, among other things.
+
+The [repository][bench-repo] contains all the infrastructure and details to get started with your
+own load testing.
+
+[bench-repo]: https://github.com/hashicorp-forge/nomad-bench
diff --git a/content/nomad/v1.8.x/content/docs/operations/index.mdx b/content/nomad/v1.8.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.8.x/content/docs/operations/key-management.mdx b/content/nomad/v1.8.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..303c3c01e7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers store key metadata in raft, but
+the encryption key material is stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers. Nomad servers can use an external
+KMS or Vault transit encryption to wrap the key material using the [`keyring`][]
+configuration block.
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Replication
+
+When a leader is elected, it creates the keyring if it does not already
+exist. When a key is added, the metadata will be replicated via raft. Each
+server runs a key replication process that watches for changes to the state
+store and will fetch the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election.
+
+## Restoring the Keyring from Backup
+
+Key material is never stored in raft. This prevents an attacker with a backup of
+the state store from getting access to encrypted variables. It also allows the
+HashiCorp engineering and support organization to safely handle cluster
+snapshots you might provide without exposing any of your keys or variables.
+
+However, this means that to restore a cluster from snapshot you need to also
+provide the keystore directory with the `.nks.json` key files on at least one
+server. The `.nks.json` key files are unique per server, but only one server's
+key files are needed to recover the cluster. Operators should include these
+files as part of your organization's backup and recovery strategy for the
+cluster.
+
+If you are recovering a Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`keyring`]: /nomad/docs/configuration/keyring
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
diff --git a/content/nomad/v1.8.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.8.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..c71839e981
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,522 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------|
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.wait_time`               | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                                                                            | ms / Evaluation Wait           | Timer   |
+| `nomad.nomad.broker.process_time`            | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                                                                            | ms / Evaluation Process        | Timer   |
+| `nomad.nomad.broker.response_time`           | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                                                                                   | ms / Evaluation Response       | Timer   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/parameterized) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.pending`              | Number of tasks pending                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.running`              | Number of tasks running                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.dead`                 | Number of tasks dead                                                                 | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.process_time`                    | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                 | ms / Evaluation Process  | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.response_time`                   | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                        | ms / Evaluation Response | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.wait_time`                       | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                 | ms / Evaluation Wait     | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`             | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`             | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                         | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                    | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                   | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`            | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`            | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.quota.utilization.cpu`                  | Utilization of the CPU quota                                                                                                                           | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.cores`                | Utilization of the CPU Cores quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.memory_mb`            | Utilization of the Memory MB quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`         | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://developer.hashicorp.com/nomad/s/port-plan-failure
diff --git a/content/nomad/v1.8.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.8.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..2823055ba1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://developer.hashicorp.com/nomad/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.8.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.8.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..7dc11710a5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,188 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+By default, any stop signal to an agent (interrupt or terminate) will cause the
+agent to exit after ensuring its internal state is committed to disk as
+needed. You can configuration additional behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when `leave_on_interrupt` or `leave_on_terminate` are set the
+server will notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there will be a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, the [`server
+force-leave` command][] should be used to eject it from the consensus peer set.
+
+For clients, when `leave_on_interrupt` or `leave_on_terminate` are set and the
+client is configured with [`drain_on_shutdown`][], the client will drain its
+workloads before shutting down.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.8.x/content/docs/operations/stateful-workloads.mdx b/content/nomad/v1.8.x/content/docs/operations/stateful-workloads.mdx
new file mode 100644
index 0000000000..d8ecf7db08
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/operations/stateful-workloads.mdx
@@ -0,0 +1,236 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Portworx or Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. More information can be found on the CSI
+concepts [documentation page](/nomad/docs/concepts/plugins/csi).
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+Host volumes mount paths from the host (the Nomad client) into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+backed by a distributed networked storage such as GlusterFS, or a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore
+you can use host volumes for both local somewhat persistent storage and for
+highly persistent networked storage.
+
+Because you need to declare host volumes in the Nomad agent's configuration
+file, you must restart the Nomad client to reconfigure them. This makes host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/concepts/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add/update/remove host volumes to make them available for
+consumption by Nomad Operators. Or, with networked host volumes, a Storage
+Administrator will need to provision the volumes and make them available to the
+Nomad clients. A System Administrator will then mount them on the Nomad clients.
+
+Host volumes backed by local storage help persist data that is not critical, for
+example an on-disk cache that can be rebuilt if needed. When backed by networked
+storage such as NFS/CIFS-mounted volumes or distributed storage via
+GlusterFS/Ceph, host volumes provide a quick option to consume highly available
+and reliable storage.
+
+Refer to the [Stateful workloads with Nomad host
+volumes](/nomad/tutorials/stateful-workloads/stateful-workloads-host-volumes)
+tutorial to learn more about using host volumes with Nomad.
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/tutorials/integrate-nomad/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/concepts/plugins/csi)
+- [Nomad CSI
+  tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [Portworx on
+  Nomad](https://docs.portworx.com/portworx-enterprise/install-portworx/install-with-other/nomad#operate-and-utilize-portworx-on-nomad)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..efbdc81437
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,499 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace. Note that
+variable paths never start with a leading `/`, so Nomad will return an error if
+you submit a policy that has such a path.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node Pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..d5449ac44e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to [jobs][job_spec] there are other objects that can be specified
+in Nomad.
+
+- [ACL Policy][acl_policy_spec]
+- [Volume][volume_spec]
+
+[job_spec]: /nomad/docs/job-specification
+[acl_policy_spec]: /nomad/docs/other-specifications/acl-policy
+[volume_spec]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..20e711ea6c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,164 @@
+---
+layout: docs
+page_title: Namespace Specification
+description: Learn about Nomad's Namespace specification.
+---
+
+# Namespace Specification
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+
+Nomad Namespaces may be specified as HCL files and submitted by the [`nomad
+namespace apply`][cli_ns_apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Namespace specifications do *not*
+support [HCL2][hcl2] features like functions.
+
+In [federated][] clusters, all updates to namespaces are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers   = ["java", "docker"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+
+# Vault configuration is a Nomad Enterprise feature.
+vault {
+  default = "default"
+  allowed = ["default", "infra"]
+}
+
+# Consul configuration is a Nomad Enterprise feature.
+consul {
+  default = "default"
+  allowed = ["all", "default"]
+}
+```
+
+## Namespace Specification Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+- `vault` <code>([Vault](#vault-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Vault clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+- `consul` <code>([Consul](#consul-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Consul clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+### `capabilities` Parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+- `enabled_network_modes` `(array<string>: [])` - List of network modes allowed
+  in the namespace. If empty all network modes are allowed.
+
+- `disabled_network_modes` `(array<string>: [])` - List of network modes disabled
+  in the namespace.
+
+### `node_pool_config` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs in
+  this namespace that don't define a node pool in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that are allowed
+  to be used by jobs in this namespace. By default, all node pools are allowed.
+  If an empty list is provided only the namespace's default node pool is
+  allowed. This field supports wildcard globbing through the use of `*` for
+  multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any node pool is allowed to be used, except for those that match any of these
+  patterns. This field cannot be used with `allowed`.
+
+### `vault` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Vault cluster to use for jobs
+  in this namespace that don't define a Vault cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Vault clusters that are
+  allowed to be used by jobs in this namespace. By default, all Vault clusters
+  are allowed.  If an empty list is provided only the namespace's default Vault
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Vault clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Vault cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+### `consul` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Consul cluster to use for jobs
+  in this namespace that don't define a Consul cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Consul clusters that are
+  allowed to be used by jobs in this namespace. By default, all Consul clusters
+  are allowed.  If an empty list is provided only the namespace's default Consul
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Consul clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Consul cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+[cli_ns_apply]: /nomad/docs/commands/namespace/apply
+[hcl2]: /nomad/docs/job-specification/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..f3ed362191
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Nomad Node Pool Specification
+description: Learn about Nomad's Node Pool specification.
+---
+
+# Nomad Node Pool Specification
+
+Nomad node pools may be specified as HCL files and submitted by the [`nomad node
+pool apply`][pool-apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad node pool specifications do *not*
+support HCL2 features like functions.
+
+Example node pool specification generated by [`nomad node pool
+init`][pool-init]:
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/docs/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Node Pool Specification Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` Parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/docs/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/docs/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..9ba9fc3cc1
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Increasing this value and re-issuing
+  `volume create` or `volume register` may expand the volume, if the CSI plugin
+  supports it.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**. Note that, like the rest of the volume specification, 
+  this block is declarative, and an update replaces it in its entirety, therefore 
+  all parameters need to be specified.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), or [`clone_id`](#clone_id)
+fields on **volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Volume Expansion
+
+CSI Volumes may be expanded (increased in size) if the CSI controller plugin
+(and node plugin, if required) has the `EXPAND_VOLUME` capability.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min)
+above the current real capacity of the volume (as seen with the
+[`volume status`][] command), and re-issue either [`volume create`][]
+or [`volume register`][].
+
+Nomad will reconcile the requested capacity by issuing expand volume requests
+to the controller plugin, and if required by the controller, also to the
+node plugins for each allocation that has a claim on the volume.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+
+### Example Volume Expansion
+
+Either [`volume create`][] or [`volume register`][] commands can trigger
+an expand to occur, after the volume has already been created or registered.
+
+Example using `volume create`, with a `volume.hcl` file:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+
+capacity_min = "50gib"
+capacity_max = "50gib"
+
+# ... etc ...
+```
+
+Create the volume:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+See its current capacity with [`volume status`][]:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 50 GiB
+```
+
+Update `volume.hcl`:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+# all of the above must remain the same
+
+capacity_min = "100gib" # double
+capacity_max = "100gib" # increased to match
+
+# ... etc ...
+```
+
+Run `volume create` again:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+Check the volume capacity again:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 100 GiB
+```
+
+If you encounter errors that are not clear from the command output,
+the CSI plugin allocation logs and/or Nomad leader server logs may be
+helpful.
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume status`]: /nomad/docs/commands/volume/status
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.8.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.8.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.8.x/content/docs/partnerships.mdx b/content/nomad/v1.8.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..b8c95e0b93
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/partnerships.mdx
@@ -0,0 +1,133 @@
+---
+layout: docs
+page_title: Nomad Partnerships
+description: Update this content
+---
+
+# Nomad Integration Program
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. See the [Introduction](/nomad/intro) page for a full description of the current features. The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/docs/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.8.x/content/docs/release-notes/index.mdx b/content/nomad/v1.8.x/content/docs/release-notes/index.mdx
new file mode 100644
index 0000000000..fb7fb79944
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/release-notes/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Release Notes
+description: |-
+  Release notes for the major software packages for Nomad
+---
+
+# Release Notes
+
+Choose a version from the navigation sidebar to view the release notes for Nomad.
+
+Documentation for maintenance releases (e.g., 0.1.x) is on the bottom of each release notes page.
\ No newline at end of file
diff --git a/content/nomad/v1.8.x/content/docs/release-notes/nomad/upcoming.mdx b/content/nomad/v1.8.x/content/docs/release-notes/nomad/upcoming.mdx
new file mode 100644
index 0000000000..0e7a490814
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/release-notes/nomad/upcoming.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Upcoming
+description: >-
+  Notices of upcoming Nomad changes
+---
+
+# Upcoming
+
+Nomad strives to be backward compatible for at least 2 major releases, so for
+example, you can upgrade Nomad v1.6.x to Nomad v1.8.x. In addition, Enterprise
+customers have access to [Long Term Support (LTS)][LTS] releases.
+
+Refer to [Upgrading][] for details of the upgrade process, and [Upgrade
+Guides][] for notes on upgrading specific versions.
+
+However, from time to time it's necessary to make backwards _incompatible_
+changes to Nomad. We announce these on [changelog][], the [Release Notes][], and
+the version-specific [Upgrade Guides][]. In order to help you plan your
+upgrades, this page maintains a list of all planned future changes that might
+cause backwards incompatibilities or require operational changes. It's possible
+that a given change may happen later than intended, at which point we update
+this document. However, we do not move changes earlier than originally published
+unless there's a required change due to a security vulnerability.
+
+## Nomad 1.9.0
+
+* Nomad will remove support for HCL1 job specifications and the `-hcl1` flag on
+  the `nomad job run` and other commands. Refer to [GH-20195][] for more details.
+* Nomad will remove the [`tls_prefer_server_cipher_suites`][] agent configuration.
+* Nomad will remove support for Nomad client agents older than 1.6.0. Older
+  nodes will fail heartbeats. Nomad servers will mark the workloads on those
+  nodes as lost and reschedule them normally according to the job's
+  [`reschedule`][] block.
+
+## Nomad 1.10.0 LTS
+
+Nomad 1.10.0 is a Long-Term Support release for Enterprise customers.
+
+* Nomad will remove support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the integration
+  guide][consul-integration] for details.
+* Nomad will remove support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the integration guide][vault-integration] for
+  details.
+* Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+* Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+* Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+[LTS]: /nomad/docs/enterprise#long-term-support-lts-releases
+[Upgrading]: /nomad/docs/upgrade
+[Upgrade Guides]: /nomad/docs/upgrade/upgrade-specific
+[changelog]: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md
+[Release Notes]: /nomad/docs/release-notes
+[GH-20195]: https://github.com/hashicorp/nomad/issues/20195
+[`tls_prefer_server_cipher_suites`]: /nomad/docs/configuration/tls#tls_prefer_server_cipher_suites
+[consul-integration]: /nomad/docs/integrations/consul/acl
+[vault-integration]: /nomad/docs/integrations/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/job-specification/disconnect
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.8.x/content/docs/release-notes/nomad/v1_8_x.mdx b/content/nomad/v1.8.x/content/docs/release-notes/nomad/v1_8_x.mdx
new file mode 100644
index 0000000000..ede53948af
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/release-notes/nomad/v1_8_x.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: 1.8.x
+description: >-
+  Nomad release notes for version 1.8.x
+---
+
+# Nomad 1.8.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Long Term Support Release (Enterprise):** Nomad 1.8 introduces a [long term
+  support release](/nomad/docs/enterprise#long-term-support-lts-releases) which
+  provides extended maintenance (two years of critical fixes provided through
+  minor releases and efficient upgrades (support for direct upgrades from one
+  LTS release to the next).
+
+- **Exec2 Task Driver (beta):** The `exec2` driver is used to execute a
+  command for a task. It offers a security model optimized for running
+  'ordinary' processes with very low startup times and minimal overhead in
+  terms of CPU, disk, and memory utilization. The `exec2` driver leverages
+  kernel features such as the Landlock LSM, cgroups v2, and the unshare system
+  utility. Due these enhancements, tasks no longer require leveraging
+  filesystem isolation based on chroot, which provide an enhanced security
+  profile and improved performance for the Nomad operator. Refer to [Exec2 Task
+  Driver](/nomad/plugins/v1.8.x/drivers/exec2) for more details.
+
+- **Transparent proxy support for Consul service mesh:** Transparent Proxy
+  introduces a more seamless way of dialing upstream services when Consul service
+  mesh is enabled. Users can configure services to use transparent proxy with a
+  new [`transparent_proxy`](/nomad/docs/v1.8.x/job-specification/transparent_proxy)
+  block. When a service is configured to use transparent proxy, workloads can now dial the
+  service using a virtual IP Consul DNS name.
+
+- **Consul API Gateway for Nomad:** Consul API Gateway on Nomad is now
+  officially supported. A prescriptive job specification on
+  [hashicorp-guides/consul-api-gateway-on-nomad](https://github.com/hashicorp-guides/consul-api-gateway-on-nomad)
+  along with a supporting [tutorial](/nomad/tutorials/integrate-consul/deploy-api-gateway-on-nomad) on
+  how to securely deploy Consul API gateway on Nomad.
+
+- **Re-worked Jobs page in the web UI with live updates:** Within the [Jobs
+  index](/nomad/tutorials/web-ui/web-ui-workload-info#list-jobs) page Nomad has
+  made a few improvements:
+
+  - **Prioritize showing the current state over historical state for jobs:**
+  Previously, long-garbage-collected allocation placement failures, lost nodes,
+  and other historical representations of job state were shown alongside
+  currently running allocations. In self-healing jobs, this often meant that a
+  healthy job looked like it had failures, when in fact Nomad had replaced or
+  rescheduled those failures. Now, the jobs list tries to show accurate
+  allocation information and meaningful statuses (like "Degraded", or
+  "Recovering") to better illustrate the current state of a job.
+
+  - **Server-side pagination:** For users with many thousands of jobs, the main
+  landing page for the web UI will no longer have a noticeable delay on
+  rendering. Users can control page length and filter paginated jobs
+  appropriately.
+
+  - **Live updates:** Previously, users had to manually refresh
+  the page to see newly created jobs, or to hide jobs that had been stopped and
+  garbage-collected. Now, the jobs list will update in real-time as jobs are
+  created, updated, or removed. Further, any changes to allocations of jobs
+  on-page will be reflected in the status of that job in real-time.
+
+- **Time based task execution (Enterprise) :** Using a CRON-like syntax, operators can now
+  [schedule](/nomad/docs/job-specification/schedule) when tasks should execute
+  and when they should stop. This provides governance for tasks executed from
+  jobs, and allows operators to easily opt-in or opt-out of a schedule that
+  governs when the task can run through the web based UI or through the [CLI](/nomad/docs/commands/alloc/pause).
+
+- **Sentinel policy management in the Web UI (Enterprise):** Enterprise users can manage
+  Sentinel policies directly within the Nomad UI. Users can create a Sentinel
+  policy based on a template provided from the UI or create policies directly
+  using an editor for Sentinel policies. Refer to [Sentinel
+  policies](/nomad/tutorials/governance-and-policy/sentinel) to learn more about
+  how to use Sentinel within Nomad.
+
+- **nomad-bench:** Nomad now provides a testing framework through
+  [nomad-bench](https://github.com/hashicorp-forge/nomad-bench) which provisions
+  infrastructure used to run tests and benchmarks against Nomad test
+  clusters. The infrastructure consists of Nomad test clusters that each have a
+  set of servers with hundreds or thousands of simulated nodes created using
+  nomad-nodesim. The Nomad server processes are not simulated and are expected
+  to run on their own hosts, mimicking real-world deployments.  Metrics are then
+  gathered from the Nomad servers for use with benchmarking and load testing.
+
+## What's deprecated
+
+- **LXC Task driver:** The [Community LXC Task
+  Driver](/nomad/plugins/drivers/community/lxc) is now deprecated. Official
+  support will be removed and the repo will be archived when Nomad 1.9 is
+  released. Users are encouraged to migrate their workloads to another task
+  driver such as the built-in Docker task [driver](/nomad/docs/drivers/docker).
+
+- **ECS Task driver:** The remote [ECS Task
+  Driver](https://developer.hashicorp.com/nomad/plugins/drivers/remote/ecs) is
+  now deprecated. Official support will be removed and the repo will be
+  archived when Nomad 1.9 is released. Users are encouraged to migrate their
+  workloads to Amazon ECS or to another Nomad task driver.
+
+- **`stop_after_client_disconnect`, `max_client_disconnect`,
+  `prevent_reschedule_on_lost`:** Nomad 1.8.0 introduces a
+  [disconnect](/nomad/docs/job-specification/disconnect) block meant to group
+  all the configuration options related to disconnected client's and server's
+  behavior, causing the deprecation of the fields stop_after_client_disconnect,
+  max_client_disconnect and prevent_reschedule_on_lost. This block also
+  introduces new options for allocations reconciliation if the client regains
+  connectivity.
+
+- **32-bit builds**: Support for 32-bit architectures is now deprecated. Nomad
+  releases will no longer include binaries built for 32-bit platforms starting
+  with Nomad 1.9.
+
+## What's removed
+
+- **raw_exec option `no_cgroups`:** In Nomad 1.7.0 the raw_exec plugin option
+  for no_cgroups became ineffective. Starting in Nomad 1.8.0 attempting to set
+  the no_cgroups in raw_exec plugin configuration will result in an error when
+  starting the agent.
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
+
+## Known issues
+
+The following issues are known to exist in the v1.8.x releases:
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.8.0](https://github.com/hashicorp/nomad/releases/tag/v1.8.0)
diff --git a/content/nomad/v1.8.x/content/docs/runtime/environment.mdx b/content/nomad/v1.8.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..000cb4dac7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,113 @@
+---
+layout: docs
+page_title: Environment - Runtime
+description: Learn how to configure the Nomad runtime environment.
+---
+
+# Runtime Environment
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Both the original case and an uppercased 
+version are injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.8.x/content/docs/runtime/index.mdx b/content/nomad/v1.8.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..86b05c6076
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/runtime/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, caveats,
+  and more.
+---
+
+# Runtime
+
+This section details Nomad's runtime information, including environment
+variables, interpolations, caveats, and more.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.8.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.8.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..d2132a56a0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,202 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Learn about the Nomad's interpolation and interpreted variables.
+---
+
+# Variable Interpolation
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/drivers/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/drivers/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.8.x/content/docs/schedulers.mdx b/content/nomad/v1.8.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..7eb58f3d53
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/schedulers.mdx
@@ -0,0 +1,98 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn about Nomad's various schedulers.
+---
+
+# Schedulers
+
+Nomad has four scheduler types that can be used when creating your job:
+`service`, `batch`, `system` and `sysbatch`. Here we will describe the differences
+between each of these schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.8.x/content/docs/upgrade/index.mdx b/content/nomad/v1.8.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..aee9627e30
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,253 @@
+---
+layout: docs
+page_title: 'Upgrading'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Learn how to upgrade Nomad.
+---
+
+# Upgrading
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/docs/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.8.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.8.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..2de18374e0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,2166 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Specific versions of Nomad may have additional information about the upgrade
+  process beyond the standard flow.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.8.3
+
+#### Nomad keyring rotation
+
+In Nomad 1.8.3, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.8.2
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.8.2, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`. We made
+this change as a result of regressions introduced by mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.8.2 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment. We made this change as a result of regressions introduced by
+mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+## Nomad 1.8.1
+
+<EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.1 includes an updated version of the Sentinel library. Users
+that have built custom Sentinel plugins must recompile them using an SDK
+supporting Sentinel Plugin Protocol Version 3. Consult the Sentinel
+[SDK Compatibility Matrix](https://github.com/hashicorp/sentinel-sdk?tab=readme-ov-file#sdk-compatibility-matrix) for appropriate Sentinel SDK versions.
+
+## Nomad 1.8.0
+
+#### Deprecated Disconnect Fields
+
+Nomad 1.8.0 introduces a `disconnect` block meant to group all the configuration
+options related to disconnected client's and server's behavior, causing the
+deprecation of the fields `stop_after_client_disconnect`, `max_client_disconnect`
+and `prevent_reschedule_on_lost`. This block also introduces new options for
+allocations reconciliation if the client regains connectivity.
+
+#### CNI Constraints
+
+In Nomad 1.8.0, jobs with `bridge` networking will have constraints added during
+job submit that require CNI plugins to be present on the node. Nodes have
+fingerprinted the available CNI plugins starting in Nomad 1.5.0.
+
+If you are upgrading from Nomad 1.5.0 or later to 1.8.0 or later, there's
+nothing additional for you to do. It's not recommended to skip more than 2
+versions of Nomad. But if you upgrade from earlier than 1.5.0 to 1.8.0 or later,
+you will need to ensure that clients have been upgraded before submitting any
+jobs that use `bridge` networking.
+
+#### Removal of `raw_exec` option `no_cgroups`
+
+In Nomad 1.7.0 the `raw_exec` plugin option for `no_cgroups` became ineffective.
+Starting in Nomad 1.8.0 attempting to set the `no_cgroups` in `raw_exec` plugin
+configuration will result in an error when starting the agent.
+
+## Nomad 1.7.11 (UNRELEASED)
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.7.11, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.7.10
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.7.10, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.7.10 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.7.2
+
+Nomad 1.7.2 fixes a critical bug in CPU fingerprinting in Nomad 1.7.0 and
+1.7.1. You should not install Nomad 1.7.0 or 1.7.1 and instead install the
+latest Nomad 1.7.x version.
+
+## Nomad 1.7.0
+
+<Warning>
+
+Nomad 1.7.0 contains a critical bug in keyring replication. You should not
+install Nomad 1.7.0 and instead install the latest Nomad 1.7.x version.
+
+</Warning>
+
+#### Keyring Replication Failure After Leader Election
+
+Nomad 1.7.0 introduced new RSA keys to the keyring for use in signing workload
+identities. These keys were not correctly replicated from leader to
+followers. This results in all workload identity verification failing after a
+leader election.
+
+This bug was fixed in Nomad 1.7.1.
+
+#### Vault Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault token specific to the task.
+
+The existing workflow using a Vault token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`vault.policies`][] field is also deprecated and will work
+only with the existing workflow. Instead, you should configure a suitable Vault
+role and use that.
+
+The following agent configuration fields are deprecated:
+- [`vault.allow_unauthenticated`][] will be removed in Nomad 1.10. Tasks will use
+  the workload identity without the user supplying a Vault token.
+- [`vault.task_token_ttl`][] will be removed in Nomad 1.10. With workload
+  identity, tasks will receive their TTL configuration from the Vault role.
+- [`vault.token`][] will be removed in Nomad 1.10. Nomad agents will no longer
+  make requests to authenticated endpoints except with a task's workload
+  identity.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Vault to work with workload identity. See [Migrating to Using Workload
+Identity with Vault][] for more details.
+
+#### Consul Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a service's or task's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+workload.
+
+The existing workflow using a Consul token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`consul.allow_unauthenticated`][] agent configuration field
+will be removed in Nomad 1.10. Tasks will use the workload identity without the
+user supplying a Consul token.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Consul to work with workload identity. See [Migrating to Using Workload
+Identity with Consul][] for more details.
+
+#### RS256 JWT Signing Algorithm Support
+
+Prior to Nomad 1.7, workload identity JWTs were signed with the `EdDSA`
+algorithm. While `EdDSA` has numerous advantages as a signing algorithm, most
+third parties that accept JWTs expect the `RS256` signing algorithm to be used.
+
+Therefore starting in Nomad 1.7 *new* signing keys will generate an RSA key and
+sign workload identities with the `RS256` signing algorithm.
+
+Before setting up third party authentication methods to use workload
+identities, it is recommended to run [`nomad operator root keyring
+rotate`](/nomad/docs/commands/operator/root/keyring-rotate) to ensure you
+generate a new RSA key.
+
+To verify an RSA key is present you may check the [`/.well-known/jwks.json`
+endpoint](/nomad/api-docs/operator/keyring#list-active-public-keys) on any
+Nomad agent. If you see `"kty": "RSA"`, then an RSA key exists and you do not
+need to rotate keys.
+
+New Nomad clusters will use RSA by default and are not affected.
+
+#### CPU Fingerprinting Changes
+
+Starting in Nomad 1.7, Nomad clients improve the accuracy of detected CPU
+performance metrics. The fingerprinter now takes into account heterogeneous core
+types on applicable processors. In addition, Nomad will attempt to detect and
+use the base frequency of the processor rather than the turbo frequency when
+calculating the total available CPU bandwidth. The net result of these behaviors
+is that the calculated total CPU bandwidth available on a node may change when
+upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
+meets expectations before upgrading. The [cpu concepts][cpu] documentation
+contains guidance in understanding how Nomad detects CPU metrics.
+
+#### CPU EC2 Detection Changes
+
+Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
+performance data for every EC2 instance type. In 1.7 and later Nomad instead
+gathers this data by executing the `dmidecode` command. The `dmidecode` package
+must be installed manually on some Linux distributions before the Nomad agent
+is started.
+
+#### CPU Core Isolation
+
+Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`
+attribute will be restricted to using only the CPU cores assigned to them. In
+previous versions of Nomad these tasks could also make use of other non-reserved
+CPU cores. However this feature would cause severe performance problems for
+the Linux kernel as the number of tasks increased. Operators are encouraged
+to ensure tasks making use of the `cores` attribute are given sufficient CPU
+resources before upgrading.
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.7.0 changes the behavior of the [`distinct_hosts`][] constraint such that
+namespaces are taken into account when choosing feasible clients for allocation
+placement. The previous, less-expected behavior would cause **any** job with the
+same name running on a client to cause that node to be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`][]
+constraint over [`${node.pool}`][node_attributes].
+
+#### Loading Binaries from `plugin_dir` Without Configuration
+
+Starting with Nomad 1.7.0, loading plugins that are not referenced in the agent
+configuration file is deprecated. Future versions of Nomad will only load
+plugins that have a corresponding [`plugin`](/nomad/docs/configuration/plugin)
+block in the agent configuration file.
+
+#### Changes to `raw_exec`
+
+The `raw_exec` task driver now enforces memory limits via cgroups on Linux
+platforms similar to the `exec` and `docker` task drivers. The driver does
+support memory [oversubscription][oversub], which can be configured in such a
+way to nearly replicate the previously unlimited behavior.
+
+The `no_cgroups` configuration option no longer has any effect. Previously,
+setting `no_cgroups` would disable the mechanism where Nomad used the freezer
+cgroup to halt the process group of a Task before issuing a kill signal to each
+process. Starting in Nomad 1.7.0 this behavior is always enabled (and a similar
+mechanism has always been enabled on cgroups v2 systems).
+
+## Nomad 1.6.14 (UNRELEASED)
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.6.14, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.6.13
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.6.13, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.6.13 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration][allow_caps_exec]:
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task][cap_add_exec] that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide][hard_guide]
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock] capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`][artifact_params]
+and [`headers`][artifact_params] fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`][artifact_env].
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`][artifact_fs_isolation].
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`][decompression_size_limit] and
+[`decompression_file_count_limit`][decompression_file_count_limit].
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`] configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`consul.allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`distinct_hosts`]: /nomad/docs/job-specification/constraint#distinct_hosts
+[`distinct_property`]: /nomad/docs/job-specification/constraint#distinct_property
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`Local`]: /consul/docs/security/acl/acl-tokens#token-attributes
+[`log_file`]: /nomad/docs/configuration#log_file
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`rejoin_after_leave`]: /nomad/docs/configuration/server#rejoin_after_leave
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[`vault.allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault.policies`]: /nomad/docs/job-specification/vault#policies
+[`vault.task_token_ttl`]: /nomad/docs/configuration/vault#task_token_ttl
+[`vault.token`]: /nomad/docs/configuration/vault#token
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[anon_token]: /consul/docs/security/acl/acl-tokens#special-purpose-tokens
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[artifact_params]: /nomad/docs/job-specification/artifact#artifact-parameters
+[artifacts]: /nomad/docs/job-specification/artifact
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[cores]: /nomad/docs/job-specification/resources#cores
+[cpu]: /nomad/docs/concepts/cpu
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[enterprise licensing]: /nomad/docs/enterprise/license
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
+[hcl2]: https://github.com/hashicorp/hcl2
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[migrate]: /nomad/docs/job-specification/migrate
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[Migrating to Using Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[node pools]: /nomad/docs/concepts/node-pools
+[node_attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[nvidia]: /nomad/plugins/devices/nvidia
+[oversub]: /nomad/docs/job-specification/resources#memory-oversubscription
+[pki]: /vault/docs/secrets/pki
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[task-config]: /nomad/docs/job-specification/task#config
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[Process Isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation
diff --git a/content/nomad/v1.8.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.8.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..b7aeefd95e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  This page features many ways Nomad is used in production today across many
+  industries to solve critical, real-world business objectives
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+Nomad is widely adopted and used in production by PagerDuty, Cloudflare, Roblox, Pandora, and more.
+
+#### Roblox
+
+- [How Roblox built a platform for 100 million players with Nomad (2020)](https://www.hashicorp.com/case-studies/roblox/)
+- [How Roblox runs a platform for 70 million gamers on Nomad (2019)](https://portworx.com/architects-corner-roblox-runs-platform-70-million-gamers-hashicorp-nomad/)
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
+...and more!
diff --git a/content/nomad/v1.8.x/content/intro/index.mdx b/content/nomad/v1.8.x/content/intro/index.mdx
new file mode 100644
index 0000000000..44757a5182
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/index.mdx
@@ -0,0 +1,56 @@
+---
+layout: intro
+page_title: Introduction
+description: >-
+  Welcome to the intro guide to Nomad. This guide is the best place to start
+  with Nomad. We cover what Nomad is, what problems it can solve, how it
+  compares to existing software, and a quick start for using Nomad.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameborder="0"
+  allowfullscreen="true"
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key Features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/docs/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad Compares to Other Tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next Steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.8.x/content/intro/use-cases.mdx b/content/nomad/v1.8.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..7082888c5d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/use-cases.mdx
@@ -0,0 +1,66 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  This page lists some concrete use cases for Nomad, but the possible use cases
+  are much broader than what we cover.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker Container Orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy Application Deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch Processing Workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and Multi-Cloud Federated Deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
diff --git a/content/nomad/v1.8.x/content/intro/vs/ecs.mdx b/content/nomad/v1.8.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.8.x/content/intro/vs/index.mdx b/content/nomad/v1.8.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..e54a8087ea
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/vs/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: intro
+page_title: Nomad vs. Other Software
+description: Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. Other Software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.8.x/content/intro/vs/mesos.mdx b/content/nomad/v1.8.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.8.x/content/intro/vs/terraform.mdx b/content/nomad/v1.8.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.8.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.8.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.8.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.8.x/content/partials/envvars.mdx b/content/nomad/v1.8.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..1ed32107d4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/envvars.mdx
@@ -0,0 +1,75 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                              |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                          |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                                    |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                            |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                         |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                                |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                                  |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                                   |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index.          |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                              |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                             |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                            |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                               |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                                     |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                            |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                              |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                             |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                                |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata. |
+| `CONSUL_HTTP_TOKEN`      | The tasks' Consul token. See [Consul Integration][consul] documentation for more details.                                                                                                                                                                                                |
+| `CONSUL_TOKEN`           | The tasks' Consul token. See [Consul Integration][consul] documentation for more details. This variable is deprecated and exists only for backwards compatibility.                                                                                                                       |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                                |
+
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_INTERFACE_<label>`    | The configured network namespace interface for the given port `label` when using bridged or CNI networking.                                                                                                                                             |
+| `NOMAD_ALLOC_IP_<label>`           | The configured network namespace IP for the given port `label` when using bridged or CNI networking.                                                                                                                                                    |
+| `NOMAD_ALLOC_ADDR_<label>`         | The configured network namespace `IP:Port` pair for the given port `label` when using bridged or CNI networking.                                                                                                                                        |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/runtime/environment#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/integrations/vault-integration
+[consul]: /nomad/docs/integrations/consul-integration
diff --git a/content/nomad/v1.8.x/content/partials/general_options.mdx b/content/nomad/v1.8.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.8.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.8.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.8.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.8.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.8.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.8.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..bb25000698
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/install/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.8.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.8.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..d916ba11e6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,23 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.5.1
+release](https://github.com/containernetworking/plugins/releases/tag/v1.5.1),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.5.1
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.8.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.8.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.8.x/content/partials/install/manual-install.mdx b/content/nomad/v1.8.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.8.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.8.x/content/plugins/devices/community/index.mdx b/content/nomad/v1.8.x/content/plugins/devices/community/index.mdx
new file mode 100644
index 0000000000..6915b31e2d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/devices/community/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: 'Device Plugins: Community Supported'
+description: 'A list of community supported Device Plugins.'
+---
+
+# Community Supported
+
+If you have authored a device plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page. For details on authoring a
+device plugin, please refer to the [plugin authoring guide][plugin_guide].
+
+Below is a list of community-support task drivers you can use with Nomad:
+
+- [USB][usb]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[usb]: /nomad/plugins/devices/community/usb
diff --git a/content/nomad/v1.8.x/content/plugins/devices/community/usb.mdx b/content/nomad/v1.8.x/content/plugins/devices/community/usb.mdx
new file mode 100644
index 0000000000..aadea20a2a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/devices/community/usb.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Devices: USB'
+description: The USB Device Plugin detects and makes USB devices available to tasks
+---
+
+# USB Device Plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.8.x/content/plugins/devices/index.mdx b/content/nomad/v1.8.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..f09be25310
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/devices/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: 'Device Plugins: External'
+description: 'A list of external Device Plugins.'
+---
+
+# External Device Plugins
+
+Nomad has a plugin system for defining task drivers. External device driver
+plugins will have the same user experience as built in devices.
+
+Below is a list of official external task drivers you can use with Nomad:
+
+- [Nvidia][nvidia]
+
+[plugin_guide]: /nomad/docs/concepts/plugins
+[nvidia]: /nomad/plugins/devices/nvidia
diff --git a/content/nomad/v1.8.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.8.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..d3c1550e2f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,288 @@
+---
+layout: docs
+page_title: 'Device Plugins: Nvidia'
+description: The Nvidia Device Plugin detects and makes Nvidia devices available to tasks.
+---
+
+# Nvidia GPU Device Plugin
+
+Name: `nomad-device-nvidia`
+
+The Nvidia device plugin is used to expose Nvidia GPUs to Nomad.
+
+## Fingerprinted Attributes
+
+<table>
+  <thead>
+    <tr>
+      <th>Attribute</th>
+      <th>Unit</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <tt>memory</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>power</tt>
+      </td>
+      <td>W (Watt)</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>bar1</tt>
+      </td>
+      <td>MiB</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>driver_version</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>cores_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>memory_clock</tt>
+      </td>
+      <td>MHz</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>pci_bandwidth</tt>
+      </td>
+      <td>MB/s</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>display_state</tt>
+      </td>
+      <td>string</td>
+    </tr>
+    <tr>
+      <td>
+        <tt>persistence_mode</tt>
+      </td>
+      <td>string</td>
+    </tr>
+  </tbody>
+</table>
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of Nvidia GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from Nvidia to prepare a machine to use docker containers with Nvidia GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The Nvidia integration only works with drivers who natively integrate with
+Nvidia's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver]. Support for
+[`lxc`][lxc-driver] should be possible by installing the [Nvidia hook][nvidia_hook]
+but is not tested or documented by Nomad.
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[lxc-driver]: /nomad/plugins/drivers/community/lxc 'Nomad lxc Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_hook]: https://github.com/lxc/lxc/blob/master/hooks/nvidia
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..218df3e4fd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,424 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-containerd'
+description: >-
+  The containerd driver is used
+  for launching containers using containerd.
+---
+
+# containerd Task Driver
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..f0e3350922
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: 'Drivers: firecracker-task-driver'
+description: >-
+  The Firecracker task driver is used to run
+  firecracker(https://firecracker-microvm.github.io/) microvms.
+---
+
+# Firecracker task Driver
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microvms.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/awslabs/tc-redirect-tap
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..3e4605ce34
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,105 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-driver-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `win_iis`
+
+The Nomad IIS driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..ac2f2b39c7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Community Supported'
+description: A list of community supported Task Driver Plugins.
+---
+
+# Community Supported
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+Below is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [LXC][lxc]
+- [Pledge][pledge]
+- [Pot][pot]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS][nomad-driver-iis]
+- [Windows IIS][nomad-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[lxc]: /nomad/plugins/drivers/community/lxc
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-iis]: /nomad/plugins/drivers/community/nomad-iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
+[pledge]: /nomad/plugins/drivers/community/pledge
+
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..2954ce1b66
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,149 @@
+---
+layout: docs
+page_title: 'Drivers: jail-task-driver'
+description: >-
+  The Jail task driver is used to run application containers using FreeBSD
+  jails.
+---
+
+# Jail task Driver
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..e71ad18b5c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'Drivers: Lightrun'
+description: The Lightrun driver is used to run your Java application with Lightrun.
+---
+
+# Lightrun Driver
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionally, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/lxc.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/lxc.mdx
new file mode 100644
index 0000000000..cf0055f8d4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/lxc.mdx
@@ -0,0 +1,197 @@
+---
+layout: docs
+page_title: 'Drivers: LXC'
+description: The LXC task driver is used to run application containers using LXC.
+---
+
+# LXC Driver
+
+Name: `lxc`
+
+~> **Deprecation Warning!**
+The `lxc` driver is currently deprecated. We will not prioritize features or pull requests that affect the lxc driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-lxc) for community ownership.
+
+
+The `lxc` driver provides an interface for using LXC for running application
+containers. You can download the external LXC driver [here][lxc-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [LXC guide][lxc-guide].
+
+## Task Configuration
+
+```hcl
+task "busybox" {
+  driver = "lxc"
+
+  config {
+    log_level = "trace"
+    verbosity = "verbose"
+    template = "/usr/share/lxc/templates/lxc-busybox"
+    template_args = []
+
+    # these optional values can be set in the template
+    distro =          ""
+    release =         ""
+    arch =            ""
+    image_variant =   "default"
+    image_server =    "images.linuxcontainers.org"
+    gpg_key_id =      ""
+    gpg_key_server =  ""
+    disable_gpg =     false
+    flush_cache =     false
+    force_cache =     false
+  }
+}
+```
+
+The `lxc` driver supports the following configuration in the job spec:
+
+- `template` - The LXC template to run.
+
+  ```hcl
+  config {
+    template = "/usr/share/lxc/templates/lxc-alpine"
+  }
+  ```
+
+- `template_args` - A list of argument strings to pass into the template.
+
+- `log_level` - (Optional) LXC library's logging level. Defaults to `error`.
+  Must be one of `trace`, `debug`, `info`, `warn`, or `error`.
+
+  ```hcl
+  config {
+    log_level = "debug"
+  }
+  ```
+
+- `verbosity` - (Optional) Enables extra verbosity in the LXC library's
+  logging. Defaults to `quiet`. Must be one of `quiet` or `verbose`.
+
+  ```hcl
+  config {
+    verbosity = "quiet"
+  }
+  ```
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to
+  bind-mount host paths to container paths. Mounting host paths outside of the
+  [allocation working directory] is allowed by default. You can prevent
+  mounting host paths outside of the [allocation working directory] on
+  individual clients by setting the [`volumes_enabled`](#volumes_enabled)
+  option to `false` in the client's configuration
+
+  ~> **Note:** Unlike the similar option for the docker driver, this
+  option must not have an absolute path as the `container_path`
+  component. This will cause an error when submitting a job.
+
+  Setting this does not affect the standard bind-mounts of `alloc`,
+  `local`, and `secrets`, which are always created.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:also/in/container"
+    ]
+  }
+  ```
+
+- `release` - (Optional) The name/version of the distribution. By default this is set by the template.
+
+- `arch` - (Optional) The architecture of the container. By default this is set by the template.
+
+- `image_server` - (Optional) The hostname of the image server. Defaults to `images.linuxcontainers.org`.
+
+- `image_variant` - (Optional) The variant of the image. Defaults to `default` or as set by the template.
+
+- `disable_gpg` - (Optional) Disable GPG validation of images. Defaults to `false`, and enabling this flag is not recommended.
+
+- `flush_cache` - (Optional) Flush the local copy of the image (if present) and force it to be fetched from the image server. Defaults to `false`.
+
+- `force_cache` - (Optional) Force the use of the local copy even if expired. Defaults to `false`.
+
+- `gpg_key_server`: GPG key server used for checking image signatures. Default is set by the underlying LXC library.
+
+- `gpg_key_id`: GPG key ID used for checking image signatures. Default is set by the underlying LXC library.
+
+## Networking
+
+Currently the `lxc` driver only supports host networking. See the `none`
+networking type in the `lxc.container.conf` [manual][lxc_man] for more
+information.
+
+## Client Requirements
+
+The `lxc` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The LXC driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `liblxc` to be installed
+- `lxc-templates` to be installed
+
+## Plugin Options
+
+- `enabled` - The `lxc` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `volumes_enabled`<a id="volumes_enabled"></a> - Specifies whether host can bind-mount host paths to container paths (defaults to `true`).
+
+- `lxc_path` - The location in which all containers are stored (commonly defaults to `/var/lib/lxc`). See [`lxc-create`][lxc-create] for more details.
+
+- `gc` block:
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-lxc" {
+  config {
+    enabled = true
+    volumes_enabled = true
+    lxc_path = "/var/lib/lxc"
+    gc {
+      container = false
+    }
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Configuration
+
+-> Only use this section for pre-0.9 releases of Nomad. If you are using Nomad
+0.9 or above, please see [plugin options][plugin-options]
+
+The `lxc` driver has the following [client-level options][client_options]:
+
+- `lxc.enable` - The `lxc` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+## Client Attributes
+
+The `lxc` driver will set the following client attributes:
+
+- `driver.lxc` - Set to `1` if LXC is found and enabled on the host node.
+- `driver.lxc.version` - Version of `lxc` e.g.: `1.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `lxc` library. Network
+isolation is not supported as of now.
+
+[lxc-create]: https://linuxcontainers.org/lxc/manpages/man1/lxc-create.1.html
+[lxc-driver]: https://releases.hashicorp.com/nomad-driver-lxc
+[lxc-guide]: /nomad/tutorials/plugins/plugin-lxc
+[lxc_man]: https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/nomad-iis.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/nomad-iis.mdx
new file mode 100644
index 0000000000..a2514d92a4
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/nomad-iis.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'Drivers: nomad-iis'
+description: >-
+  The IIS driver is used for running
+  Windows IIS services.
+---
+
+# Windows IIS Driver
+
+Name: `nomad_iis`
+
+This plugin is a task driver to run IIS Web Applications on Windows Servers. Each allocation will create an AppPool and a Website.  
+For a full documentation please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md).
+
+Unlike most other Nomad task drivers, this one is written in the C# language using ASP.NET. It uses the Microsoft.Web.Administration-API to communicate with IIS.
+
+<Note>
+At the moment I'm developing this plugin as a hobby project. Version 1 has not yet been reached and breaking changes may still occur.
+</Note>
+
+## Sample Job
+
+```hcl
+job "iis-test" {
+  datacenters = ["dc1"]
+  type = "service"
+
+  group "iis-test" {
+    count = 1
+    
+    network {
+      port "httplabel" {}
+    }
+
+    task "iis-test" {
+      driver = "iis"
+
+      config {
+        application {
+          path = "C:\\inetpub\\wwwroot"
+        }
+        application {
+          alias = "subapp"
+          path = "C:\\inetpub\\wwwroot"
+        }
+        
+        binding {
+          type = "http"
+          port = "httplabel"
+        }
+      }
+      
+      env {
+        my_key = "my-value"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 20
+      }
+    }
+  }
+}
+```
+
+Please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md) for the full documentation and configuration options.
+
+## Download
+
+Download the latest version from [here](https://github.com/sevensolutions/nomad-iis/releases).
+
+## Source Code
+
+You can get the full source code of this plugin on [Github](https://github.com/sevensolutions/nomad-iis).
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..20d0c93483
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: 'Drivers: systemd-nspawn'
+description: The nspawn task driver is used to run application containers using systemd-nspawn.
+---
+
+# nspawn Driver
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external systemd-nspawn driver
+[here][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [guide][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/pledge.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/pledge.mdx
new file mode 100644
index 0000000000..93925d0309
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/pledge.mdx
@@ -0,0 +1,332 @@
+---
+layout: docs
+page_title: 'Drivers: Pledge'
+description: The Pledge task driver is capable of blocking unwanted syscall and filesystem access.
+---
+
+# Pledge Driver
+
+Name: `pledge`
+
+The `pledge` driver executes programs similar to `exec` or `raw_exec`, but
+provides sandboxing by restricting syscalls the process is allowed to make.
+The `pledge` driver uses the [Landlock LSM][landlock] to restrict filesystem
+access, which can be significantly more efficient than creating a `chroot`.
+Isolation of CPU and memory resources is provided by leveraging features of
+cgroups v2. Network, PID, and IPC isolation is powered by Linux namespaces.
+
+Source on [GitHub][repository]
+
+Downloads on GitHub [releases][releases]
+
+#### Use cases
+
+The `pledge` driver is intended as a replacement for `raw_exec`. Sometimes
+there are those management tasks that just need to be run as `root` and directly
+access the filesystem or perform privileged operations. While `raw_exec`
+provides no isolation, the `pledge` driver uses Landlock to restrict the files
+or directories the task is allowed to access and modify. Specific groups of
+system calls are allow-listed in the task configuration, greatly reducing the
+attack surface of a mis-configured or compromised task.
+
+#### About
+
+The `pledge` driver is fundamentally powered by the [pledge utility for Linux]
+[pledge] by Justine Tunney. The driver invokes this `pledge.com` CLI tool along
+with `nsenter` and `unshare` to create a strict sandbox in which to execute a
+given command.
+
+## Task Configuration
+
+```hcl
+task "http" {
+  driver = "pledge"
+  config {
+    command    = "python3"
+    args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+    promises   = "stdio rpath inet"
+    unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+  }
+}
+```
+
+The `pledge` driver supports the following task configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. The driver will search
+  for the command on the `$PATH` of the Nomad Client unless an absolute path
+  is given.
+
+- `args` - (Optional) A list of arguments to the `command`. References to
+  environment variables or any interpolable Nomad variables will be interpolated
+  before launching the task.
+
+- `promises` - A set of promises needed for the command to run. See below for
+  more information.
+
+- `unveil` - (Optional) A list of filepaths and access rights to grant to the
+  command. See below for more information.
+
+- `importance` - (Optional) One of `"lowest"`, `"low"`, `"normal"`, `"high"`,
+  `"highest"`. Indicates the `nice` value with which to run `command` (default
+  is `"normal"`). A lower importance indicates the command should be given a
+  lower priority with regard to CPU time relative to other tasks.
+
+## Syscall Isolation (promises)
+
+When using the `pledge` task driver, by default most syscalls will become
+unavailable. A process that attempts to use an unavailable syscall will receive
+an `EPERM` error from the kernel. By specifying a set of `promises`, additional
+syscalls will be made available to the `command`.
+
+See the complete documetation for [promises][promises].
+
+| Promise | Description |
+| ------- | ------------|
+| `stdio` | allow stdio, threads, and benign system calls |
+| `rpath` | allow filesystem read operations |
+| `wpath` | allow filesystem write operations |
+| `cpath` | allow filesystem create operations |
+| `dpath` | allow creation of special files |
+| `flock` | allow file locking |
+| `tty` | allow terminal ioctls |
+| `recvfd` | allow recvmsg |
+| `sendfd` | allow sendmsg |
+| `fattr` | allow changing some struct stat bits |
+| `inet` | allow IPv4 and IPv6 |
+| `unix` | allow using Unix Domain Sockets |
+| `dns` | allow DNS |
+| `proc` | allow fork process creation and control |
+| `id` | allow setuid and friends |
+| `exec` | allow executing binaries |
+| `prot_exec` | allow creating executable memory |
+| `vminfo` | allow operations around reading `/proc` |
+| `tmppath` | allow access to `/tmp` |
+
+## Filesystem Isolation (unveil)
+
+By default the `command` will not be able to access the filesystem. Using some
+promises will implicitly allow access to specific parts of the filesystem where
+applicable. The `unveil` configuration is used to grant access to additional
+filesytem paths at a specified permission level.
+
+The format of the `unveil` parameter is a list of paths and associated
+permissions. Permissions can be any combination of `r`, `w`, `c` and `x` for
+read, write, create and execute privileges.
+
+Note that reading a file also requires the `rpath` promise, writing a file
+requires the `wpath` promise, creating a file requires the `cpath` promise, and
+executing a program requires the `exec` promise.
+
+#### Examples
+
+This example allows reading of the `/srv/www` directory.
+
+```hcl
+unveil = ["r:/srv/www"]
+```
+
+This example allows executing `/opt/bin/program` and reading `/etc/prog.d`.
+
+```hcl
+unveil = ["x:/opt/bin/program", "r:/etc/prog.d"]
+```
+
+It can be useful to `unveil` the Nomad Task Directory, which can be done by
+specifying the interpolation value.
+
+```hcl
+unveil = ["rwc:${NOMAD_TASK_DIR}"]
+```
+
+## Networking
+
+The `pledge` driver supports `none`, `host`, and `group` networking modes.
+
+#### host networking
+
+If using `host` networking mode, it can be very convenient to bless the
+[pledge][pledge] utility with the `cap_net_bind_service` Linux capability. This will
+enable Nomad tasks using the pledge driver to bind to privileged ports (i.e.
+below 1024) while using host networking mode.
+
+```shell-session
+sudo setcap cap_net_bind_service+eip /opt/bin/pledge-1.8.com
+```
+
+For convenience the `driver.pledge.cap.net_bind` Client attribute will indicate
+whether the Linux capability is set on the executable.
+
+#### bridge networking
+
+If using `bridge` networking mode, be sure to install the standard [CNI plugins]
+[cni] as required by the Nomad client.
+
+## Client Requirements
+
+The `pledge` driver requires the following:
+
+- 64-bit amd64 Linux host
+  - kernel version 5.13+
+  - cgroups v2 enabled
+- The `pledge` driver binary placed in [plugin_dir][plugin_dir]
+- The `pledge.com` utility executable on the host
+
+## Plugin Options
+
+- `pledge_executable` - The path to the `pledge.com` binary. The pledge utility
+can be [downloaded][download] directly from its creator, or compiled manually
+from [source][pledge_github].
+
+```hcl
+plugin "nomad-pledge-driver" {
+  config {
+    pledge_executable = "/opt/bin/pledge-1.8.com"
+  }
+}
+```
+
+## Client Attributes
+
+The `pledge` driver will set the following Client attributes:
+
+| Attribute | Description |
+| ----------| ----------- |
+| `driver.pledge` | set to `1` if the driver is enabled |
+| `driver.pledge.abs` | the absolute path to the pledge.com utility |
+| `driver.pledge.cap.net_bind` | indicates whether the NET_BIND linux capability is set |
+| `driver.pledge.os` | the detected operating system |
+
+## Resource Isolation
+
+CPU and memory resource isolation is enforced by cgroups v2 features, and is
+configured through the resources block in task configuration.
+
+```hcl
+resources {
+  cores  = 3
+  memory = 512
+}
+```
+
+#### cpu bandwidth
+
+The `pledge` driver always enforces a maximum CPU bandwidth available to the
+task. The bandwidth is calculated whether `resources.cpu` or `resources.cores`
+is configured.
+
+If `resources.cores` is set, the scheduler reserves that many CPU cores for use
+by the task, and only this task will be able to run on those cores.
+
+#### memory oversubscription
+
+If the Nomad scheduler is configured to enable memory [oversubscription]
+[oversub], the `pledge` driver will enable configuring `memory_max` in addition
+to `memory`. In this case, `memory_max` indicates the maximum amount of memory
+the task is able to request before being OOM killed, and `memory` represents a
+minimum amount of memory the kernel will guarantee is available for the Task.
+
+```hcl
+resources {
+  cpu        = 2000
+  memory     = 1024
+  memory_max = 2048
+}
+```
+
+## Capabilities
+
+The `pledge` driver implements the following [capabilities][capabilities].
+
+| Feature              | Implementation    |
+| ------------         | ------------------|
+| send signals         | true              |
+| exec                 | false             |
+| filesystem isolation | none (landlock)   |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+For sending signals, use the `nomad alloc signal` command.
+
+## Examples
+
+A larger set of examples are available in the [source][hack] repository.
+
+Showing how to `curl example.com`.
+
+```hcl
+job "curl" {
+  type = "batch"
+  group "group" {
+    task "curl" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command  = "curl"
+        args     = ["example.com"]
+        promises = "stdio rpath inet dns sendfd"
+      }
+    }
+  }
+}
+```
+
+An example using the Python built-in HTTP server to render a trivial web page.
+
+```hcl
+job "http" {
+  group "group" {
+    network {
+      mode = "host"
+      port "http" { static = 8181 }
+    }
+
+    task "task" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command    = "python3"
+        args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+        promises   = "stdio rpath inet"
+        unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+      }
+
+      template {
+        destination = "local/index.html"
+        data        = <<EOH
+<!doctype html>
+<html>
+  <title>example</title>
+  <body><p>Hello, friend!</p></body>
+</html>
+EOH
+      }
+    }
+  }
+}
+```
+
+## Troubleshooting
+
+When setting up a new Task using the `nomad-pledge-driver` task driver, it
+helps to run the command manually using the `pledge` utility to make sure the
+necessary promises and unveil paths are well understood. To figure out which
+syscalls process needs to make, it can be run under `strace -ff`. When a syscall
+is blocked, you'll see `"EPERM (Operation not permitted)"`
+
+```shell-session
+strace -ff /opt/bin/pledge-1.8.com -p "stdio rpath inet" -- curl example.com
+```
+
+[capabilities]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[cni]: https://developer.hashicorp.com/nomad/docs/install
+[download]: https://justine.lol/pledge/#download
+[hack]: https://github.com/shoenig/nomad-pledge-driver/tree/main/hack
+[landlock]: https://docs.kernel.org/security/landlock.html
+[oversub]: https://developer.hashicorp.com/nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
+[pledge]: https://justine.lol/pledge/
+[pledge_github]: https://github.com/jart/pledge
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[promises]: https://justine.lol/pledge/#promises
+[repository]: https://github.com/shoenig/nomad-pledge-driver
+[releases]: https://github.com/shoenig/nomad-pledge-driver/releases
+
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..0f227afd0f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'Drivers: pot'
+description: >-
+  The Pot task driver is used to run pot (https://github.com/pizzamig/pot)
+  containers using FreeBSD jails.
+---
+
+# Pot Task Driver
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+You can download the external nomad-pot-driver [here][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..04e767ede3
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Drivers: Rookout'
+description: The Rookout driver is used to run your Java app with Rookout.
+---
+
+# Rookout Driver
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.8.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..f2cadd1e31
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,186 @@
+---
+layout: docs
+page_title: 'Drivers: Singularity'
+description: >-
+  The Singularity task driver is used to run application containers using
+  Singularity.
+---
+
+# Singularity Driver
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. You can download the external Singularity driver [here][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/exec2.mdx b/content/nomad/v1.8.x/content/plugins/drivers/exec2.mdx
new file mode 100644
index 0000000000..1483087064
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/exec2.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: 'Drivers: exec2'
+description: >-
+  The exec2 task driver leverages modern kernel features for constraining tasks.
+---
+
+# Exec2 Task Driver
+
+Name: `exec2`
+
+The `exec2` driver is used to execute a command for a task. It offers a security
+model optimized for running 'ordinary' processes with very low startup times
+and minimal overhead in terms of CPU, disk, and memory utilization. The `exec2`
+driver leverages kernel features such as the [Landlock LSM][landlock], cgroups
+v2, and the [`unshare`][unshare] system utility.
+
+Source is on [GitHub][github]
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-exec2/) and verify the binary using the
+available SHA-256 sums. After downloading nomad-driver-exec2 driver, unzip the package. Make sure
+that the `nomad-driver-exec2` binary is available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path, specified by the client's config file, before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-exec2
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-exec2
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example below is a short demonstration of what a task making use of the
+exec2 task driver looks like:
+
+```hcl
+job "http" {
+  group "web" {
+    task "python" {
+      driver = "exec2"
+      config {
+        command = "python3"
+        args    = ["-m", "http.server", "8080", "--directory", "${NOMAD_TASK_DIR}"]
+        unveil  = ["r:/etc/mime.types"]
+      }
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `exec2` task driver is not built into Nomad. It must be [downloaded][releases]
+onto the client host in the configured plugin directory.
+
+- Linux 5.15+
+- Cgroups v2 enabled
+- Landlock LSM enabled
+- Commands `nsenter` and `unshare`
+- Nomad client running as root
+
+## Capabilities
+
+The `exec2` task driver implements the following driver [capabilities][capabilities]
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | false             |
+| filesystem isolation | unveil            |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+## Concepts
+
+### Filesystem Isolation
+
+##### landlock
+
+The `exec2` task driver makes use of [`go-landlock`][landlock] for providing
+filesystem isolation, making the host filesystem unreachable except where
+explicitly allowed.
+
+By default a task is enabled to access its task directory and its shared alloc
+directory. The paths to these directories are accessible by reading the environment
+variables `$NOMAD_TASK_DIR` and `$NOMAD_ALLOC_DIR` respectively.
+
+A file access mode must also be specified when granting additional filesystem
+access to a path. This is done by prefix the path with `'r'`, `'w'`, `'x'`,
+and/or `'c'` indicating read, write, executable, and create permissions,
+respectively. e.g.,
+
+- <code>r:/srv/www</code> - read-only access to `/srv/www`
+- <code>rwc:/tmp</code> - read, write, and create files in `/tmp`
+- <code>rx:/opt/bin/application</code> - read and execute a specific application
+- <code>wc:/var/log</code> - write and create files in `/var/log`
+
+This style of permission control is modeled after the [`unveil`][unveil] system
+call pioneered by the OpenBSD project. In configuration parameters we refer to
+"unveil"-ing of filesystem paths as `exec2` is leveraging landlock to emulate
+the semantics of `unveil`.
+
+##### dynamic workload users
+
+While landlock prevents tasks from accessing the host filesystem, Nomad 1.8
+introduces `dynamic workload users` which enable tasks to be run as a UID/GID
+that is not assigned to any user. This provides protection from non-root users
+getting access inside the task and allocation directories created for the task.
+
+To make use of a dynamic workload user, simply leave the `user` field blank in
+the task definition of an `exec2` task.
+
+### Resource Isolation
+
+Similar to `exec` and other container runtimes, `exec2` makes use of cgroups for
+limiting the amount of CPU and RAM a task may consume.
+
+## Configuration
+
+### Plugin Configuration
+
+The default plugin configuration is shown below. System default paths are enabled,
+but nothing else. These default paths enable basic functionality like reading
+system TLS certificates, executing programs in `/bin`, `/usr/bin`, and accessing
+system shared object files. The exact set of paths is system dependent, and can
+be disabled or customized in plugin config.
+
+The default set of paths are listed below. These paths are enabled only if they
+are found to exist at the time of the task launching.
+
+##### shared objects
+
+```
+rx:/lib
+rx:/lib64
+rx:/usr/lib
+rx:/usr/libexec
+rx:/usr/local/lib
+rx:/usr/local/lib64
+r:/etc/ld.so.conf
+r:/etc/ld.so.cache
+r:/etc/ld.so.conf.d
+```
+
+##### io, common
+
+```
+rwc:/tmp
+rw:/dev/null
+r:/dev/zero
+r:/dev/fd
+rw:/dev/stdin
+rw:/dev/stdout
+r:/dev/urandom
+w:/dev/log
+r:/usr/share/locale
+r:/proc/self/cmdline
+r:/usr/share/zoneinfo
+r:/usr/share/common-licenses
+r:/proc/sys/kernel/ngroups_max
+r:/proc/sys/kernel/cap_last_cap
+r:/proc/sys/vm/overcommit_memory
+```
+
+##### dns
+
+```
+r:/etc/hosts
+r:/hostname
+r:/etc/services
+r:/etc/protocols
+r:/etc/resolv.conf
+```
+
+##### certificates
+
+```
+r:/etc/ssl/certs
+r:/etc/pki/tls/certs
+r:/etc/ssl/ca-bundle.pem
+r:/etc/pki/tls/cacert.pem
+r:/etc/pki/ca-trust-extracted/pem/tls-ca-bundle.pem
+r:/etc/ssl/cert.pem
+```
+
+Additional allowable paths can be specified at the plugin level, which applies
+to all tasks making use of the `exec2` task driver, or at the task level, which
+will apply specifically to each task.
+
+```hcl
+plugin "nomad-driver-exec2" {
+  config {
+    unveil_defaults = true
+    unveil_paths    = []
+    unveil_by_task  = false
+  }
+}
+```
+
+- `unveil_defaults` - (default: `true`) - enable or disable default system paths
+  useful for running basic commands
+- `unveil_paths` - (default: `[]`) - a list of filesystem paths with permissions
+  to grant all tasks
+  ```hcl
+  unveil_paths = ["rx:/opt/bin", "r:/srv/certs"]
+  ```
+- `unveil_by_task` - (default: `false`) - enable or disable job submitters to
+  specify additional filesystem path access within task config
+
+### Task Configuration
+
+##### config
+
+Task configuration for an exec2 task includes setting a `command`, `args` for
+the command, and additional `unveil` filesystem paths if `unveil_by_task` is
+enabled in plugin configuration.
+
+```hcl
+config {
+  command       = "/usr/bin/cat"
+  args          = ["/etc/os-release"]
+  unveil        = ["r:/etc/os-release"]
+  oom_score_adj = 500
+}
+```
+
+- `command` - (string: required) - command to run
+- `args` - (list(string): optional) - list of arguments to provide
+  to `command`
+- `unveil` - (list(string): optional) - list of additional filesystem paths to
+  provide access to the task (requires `unveil_by_task` in plugin config).
+- `oom_score_adj` - (optional) - The likelihood of the task being OOM killed,
+  must be a positive integer. Defaults to `0`.
+
+##### cpu
+
+Tasks are limited in CPU resources by setting the `cpu` or `cores` values in the
+task `resources` block.
+
+- `cpu` - (default: `100`) - limits the CPU bandwidth allowable for the task to
+  make use of in MHz, may not be used with `cores`.
+- `cores` - (int: optional) - specifies the number of CPU cores to reserve
+  specifically for the task, may not be used with `cpu`
+
+##### memory
+
+Tasks are limited in memory resources by setting `memory` and optionally the
+`memory_max` values in the task `resources` block.
+
+### Node Attributes
+
+When installed, the `exec2` plugin provides the following node attributes which
+can be used as constraints when authoring jobs.
+
+```
+driver.exec2.unveil.defaults    = true
+driver.exec2.unveil.tasks       = true
+```
+
+[capabilities]: https://developer.hashicorp.com/nomad/docs/concepts/plugins/task-drivers#task-driver-plugin-api
+[github]: https://github.com/hashicorp/nomad-driver-exec2
+[landlock]: https://github.com/shoenig/go-landlock
+[releases]: https://releases.hashicorp.com/nomad-driver-exec2
+[unshare]: https://www.man7.org/linux/man-pages/man1/unshare.1.html
+[unveil]: https://man.openbsd.org/unveil
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/index.mdx b/content/nomad/v1.8.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..bd91c1184c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Task Drivers
+description: Task Drivers are used to integrate with the host OS to run tasks in Nomad.
+---
+
+# Task Drivers
+
+Task drivers are used by Nomad clients to execute a task and provide resource
+isolation. By having extensible task drivers, Nomad has the flexibility to
+support a broad set of workloads across all major operating systems.
+
+Task drivers are pluggable. This gives users the flexibility to introduce their
+own drivers without having to recompile Nomad. You can view the [plugin block][plugin]
+documentation for examples on how to use the `plugin` block in Nomad's client configuration.
+Note that we have introduced new syntax when specifying driver options in the client
+configuration (see [docker][docker_plugin] for an example). Keep in mind that even though
+all built-in drivers are now plugins, Nomad remains a single binary and maintains
+backwards compatibility except with the `lxc` driver.
+
+The list of supported task drivers is provided on the left of this page. Each
+task driver documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments it can be
+used in, and the resource isolation mechanisms available.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Task driver resource isolation is intended to provide a degree of separation of
+Nomad client CPU / memory / storage between tasks. Resource isolation
+effectiveness is dependent upon individual task driver implementations and
+underlying client operating systems. Task drivers do include various
+security-related controls, but the Nomad client to task interface should not be
+considered a security boundary. See the [access control guide][acl_guide] for
+more information on how to protect Nomad cluster operations.
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins
+[acl_guide]: /nomad/tutorials/access-control
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.8.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..2d49cead75
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,653 @@
+---
+layout: docs
+page_title: 'Drivers: podman'
+description: >-
+  The Podman task driver uses podman (https://podman.io/) for containerizing
+  tasks.
+---
+
+# Podman Task Driver
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-podman/) and verify the
+binary using the available SHA-256 sums. After downloading nomad-driver-podman
+driver, unzip the package. Make sure that the `nomad-driver-podman` binary is
+available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path,
+specified by the client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install -y nomad-driver-podman
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-podman
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting tlsVerify to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tlsVerify = false
+    }
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware that you also
+  lose automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: http://docs.podman.io/en/latest/markdown/podman-run.1.html#options
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/remote/ecs.mdx b/content/nomad/v1.8.x/content/plugins/drivers/remote/ecs.mdx
new file mode 100644
index 0000000000..12f23ca4cc
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/remote/ecs.mdx
@@ -0,0 +1,124 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: ECS Task Driver'
+description: >-
+  The AWS ECS Task Driver is an example Remote Task Driver.
+---
+
+# ECS Task Driver
+
+Name: `nomad-driver-ecs`
+
+Homepage: https://github.com/hashicorp/nomad-driver-ecs
+
+~> **Deprecation Warning!**
+The `ecs` driver is currently deprecated. We will not prioritize features or pull requests that affect the ecs driver. The external driver is available as an [open source
+repository](https://github.com/hashicorp/nomad-driver-ecs) for community ownership.
+
+The ECS task driver plugin for Nomad allows running [AWS ECS][ecs] tasks via
+Nomad. Allocations for these jobs are scheduled onto Nomad clients like
+traditional task drivers, however the actual task is executed remotely in
+AWS ECS. The Nomad client agent manages the remote ECS task like any other
+local Nomad task: restarting it if it fails, stopping it when requested, etc.
+
+When a Nomad node assigned allocations with ECS tasks is drained, the ECS tasks
+are *not stopped.* Instead the replacement allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime.
+
+If a Nomad node assigned allocations with ECS tasks crashes and is considered
+`down`, the replacement allocations for the `lost` allocations reconnect to the
+original ECS tasks to avoid unnecessary downtime. If the original crashed Nomad
+node restarts, it will detect `lost` allocations and stop monitoring them since
+a new node has taken over.
+
+## Client Requirements
+
+The AWS ECS Task Driver is not currently built into Nomad and must be
+[downloaded][download] onto the client host in the configured [plugin
+directory][plugin_dir].
+
+### Plugin Options
+
+Once the plugin binary is installed, the plugin must be configured in your
+Nomad client agent's HCL:
+
+```hcl
+plugin "nomad-driver-ecs" {
+  config {
+    enabled = true
+
+    #  AWS ECS Cluster to run tasks in
+    cluster = "nomad-remote-driver-cluster"
+
+    # AWS ECS Region to run tasks in
+    region  = "us-east-1"
+  }
+}
+```
+
+- `cluster` - The [AWS ECS cluster][cluster] to run tasks in.
+- `region` - The [AWS region][region] to run tasks in.
+
+## Task Configuration
+
+Nomad ECS tasks must first be defined for the ECS cluster. See the [Nomad ECS
+driver demo][demo] task for an example ECS task provisioned by Terraform.
+
+Once the ECS task is provisioned, Nomad may run it via a job:
+
+```hcl
+job "nomad-ecs-demo" {
+  datacenters = ["dc1"]
+
+  group "ecs-remote-task-demo" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+
+    reschedule {
+      delay = "5s"
+    }
+
+    task "http-server" {
+      driver       = "ecs"
+      kill_timeout = "1m" // increased from default to accommodate ECS.
+
+      config {
+        task {
+          launch_type     = "FARGATE"
+          task_definition = "nomad-remote-driver-demo:1"
+          network_configuration {
+            aws_vpc_configuration {
+              assign_public_ip = "ENABLED"
+              security_groups  = ["sg-0d647d4c7ce15034f"]
+              subnets          = ["subnet-010b03f1a021887ff"]
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `config.task` block defines the configuration of the ECS task:
+
+  - `launch_type` - The launch type on which to run your task.
+  - `task_definition` - The family and revision (`family:revision`) or full ARN
+    of the task definition to run.
+  - `network_configuration` - The network configuration for the task (eg
+    `awsvpc` for `FARGATE` tasks).
+
+    - `aws_vpc_configuration` - The VPC subnets and security groups associated with a task.
+
+      - `assign_public_ip` - Whether the task's elastic network interface receives a public IP address.
+      - `security_groups` - The security groups associated with the task or service.
+      - `subnets` - The subnets associated with the task or service.
+
+[cluster]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html
+[ecs]: https://aws.amazon.com/ecs/
+[demo]: https://github.com/hashicorp/nomad-driver-ecs/tree/main/demo
+[download]: https://releases.hashicorp.com/nomad-driver-ecs/
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: https://docs.aws.amazon.com/general/latest/gr/ecs-service.html
diff --git a/content/nomad/v1.8.x/content/plugins/drivers/remote/index.mdx b/content/nomad/v1.8.x/content/plugins/drivers/remote/index.mdx
new file mode 100644
index 0000000000..afcc29f7ba
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/drivers/remote/index.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: 'Task Driver Plugins: Remote Task Drivers'
+description: >-
+  Remote Task Drivers support cloud and other nonlocal task runtime
+  environments.
+---
+
+# Remote Task Drivers
+
+~> **Note:** Remote Task Driver support is experimental and subject to backward
+incompatible changes between Nomad releases or deprecation. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+~> **Known Bugs:** When a Nomad node running a remote task driver goes down,
+another node must be available and able to run the replacement allocation in
+order to take advantage of remote task driver's ability to avoid restarting
+lost tasks. If a new node is not immediately available but started later,
+it will start a new instance of the remote task instead of reconnecting to the
+old one. Follow [#10592][gh-10592] for the fix.
+
+Remote Task Drivers allow custom task driver plugins to execute tasks using nonlocal
+runtimes such as cloud container runtimes. Without this support, task driver plugins
+trying to manage remote tasks would run into the following problems:
+
+1. When [draining][drain] a node, Nomad stops all allocations on that node
+   before rescheduling them.
+
+2. When a node is `down`, Nomad reschedules all allocations onto other nodes.
+
+These 2 behaviors are optimal for traditional task drivers where the task
+process is colocated with the Nomad agent. If the Nomad node is down or
+drained, the allocations should be considered down or be drained as well.
+
+However these 2 behaviors do not apply to tasks executing on remote runtimes.
+If the Nomad node managing them goes down, a new Nomad node should be able to
+manage them without restarting the task. Likewise if the Nomad node managing
+the remote task is drained, a new Nomad node should manage the remote task
+without requiring it be stopped and restarted.
+
+The Remote Task Driver feature improves these behaviors for custom plugins that
+ advertise the [`RemoteTasks` capability][remote-cap].
+
+## Caveats
+
+Due to the exerpimental nature there are a number of standard Nomad features
+which Remote Task Drivers do not support by default.
+
+### Resources
+
+~> See [*Remote Task Drivers and Resources* #10549][gh-10549] on Github for
+details.  Comments, ideas, and use cases welcome!
+
+The [`resources`][resources] block has not been altered for remote task
+drivers. Since remote tasks do not consume local resources, remote task drivers
+should not use the existing `resources` block and instead implement their own
+resource parameters in their [`task.config`][task-config] block.
+
+Jobs using remote task drivers should use the minimum allowed resources in
+their [`task.resources`][resources] block:
+
+```hcl
+resources {
+  cpu    = 1
+  memory = 10
+}
+```
+
+### Nomad Client Features
+
+Remote task drivers defer most Nomad client features to the driver plugin.
+
+Since the allocation directory is local to the Nomad node, unless a remote task
+driver is able to remotely mount or copy its contents, the following features
+will be unavailable:
+
+- [`artifact`][artifact] - artifacts are downloaded to the local Nomad
+  allocation directory.
+- [`dispatch_payload`][dispatch-payload] - dispatch payloads are written to the
+  local Nomad allocation directory.
+- [`ephemeral_disk`][ephemeral-disk] - ephemeral disks are local to the Nomad
+  node and therefore not applicable to remote task drivers.
+- [`template`][template] - templates are rendered in the local Nomad allocation
+  directory.
+- [`vault`][vault] - a secret token may be retrieved but the task driver may
+  not place the token file in the expected location.
+- [`volume`][volume] - volume and volue mounts assumed tasks have access to the
+  Nomad node's local disk are unlikely to work with remote task drivers.
+
+Furthermore since networking is completely handled by the remote runtime the
+behavior of the following features is completely driver dependent:
+
+- [`network`][network] - group networks are created on the local Nomad node,
+  and task networks are up to the remote task driver to implement.
+- [`connect`][connect] - since group networks and sidecars are local to the
+  Nomad node, Consul Connect sidecars will not work as expected.
+
+[artifact]: /nomad/docs/job-specification/artifact
+[connect]: /nomad/docs/job-specification/connect
+[dispatch-payload]: /nomad/docs/job-specification/dispatch_payload
+[drain]: /nomad/docs/commands/node/drain
+[ephemeral-disk]: /nomad/docs/job-specification/ephemeral_disk
+[gh-10549]: https://github.com/hashicorp/nomad/issues/10549
+[gh-10592]: https://github.com/hashicorp/nomad/issues/10592
+[network]: /nomad/docs/job-specification/network
+[remote-cap]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[resources]: /nomad/docs/job-specification/resources
+[task-config]: /nomad/docs/job-specification/task#config
+[template]: /nomad/docs/job-specification/template
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
+[vault]: /nomad/docs/job-specification/vault
+[volume]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.8.x/content/plugins/index.mdx b/content/nomad/v1.8.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..817495908f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about task driver and device plugins for Nomad.
+---
+
+# Plugins
+
+Nomad implements a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.8.x/content/security.mdx b/content/nomad/v1.8.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.8.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..712b04627e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. If the special wildcard namespace value `*` is used, the Autoscaler
+agent will retrieve scaling policies from all namespaces. A future version will
+include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+When utilizing the High-Availability feature added in v0.4.0, the ACL policy
+needs to include capabilities that allow the Nomad Autoscaler to obtain and release Nomad variable
+locks. The namespace identifier should match the configured
+[`high_availability.lock_namespace`][autoscaler_ha_lock_namespace] parameter,
+and the path should match the [`high_availability.lock_path`][autoscaler_ha_lock_path]
+parameter.
+
+```hcl
+namespace "default" {
+  variables {
+    path "nomad-autoscaler/lock" {
+      capabilities = ["write"]
+    }
+  }
+}
+```
+
+If running Nomad Autoscaler Enterprise, the following ACL policy addition is
+needed to ensure it can read the Nomad Enterprise license.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
+[autoscaler_ha_lock_namespace]: /nomad/tools/autoscaling/agent/high_availability#lock_namespace
+[autoscaler_ha_lock_path]: /nomad/tools/autoscaling/agent/high_availability#lock_path
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..3acc904e96
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/high_availability.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/high_availability.mdx
new file mode 100644
index 0000000000..0d8df1ac85
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/high_availability.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: high_availability Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "high_availability" block is used to configure the Nomad Autoscaler agent
+  in high availability (HA) mode. In this mode, multiple agents participate in
+  leadership election, with only the leader conducting autoscaling calculations
+  and actions.
+---
+
+# `high_availability` Block
+
+<Placement groups={['high_availability']} />
+
+The `high_availability` block is used to configure the Nomad Autoscaler agent
+in high availability (HA) mode. In this mode, multiple agents participate in
+leadership election, with only the leader conducting autoscaling calculations
+and actions.
+
+```hcl
+high_availability {
+  enabled        = true
+  lock_namespace = "prod"
+  lock_path      = "custom/lock/path"
+  lock_ttl       = "30s"
+  lock_delay     = "15s"
+}
+```
+
+## `high_availability` Parameters
+
+- `enabled` `(bool: false)` - Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired.
+
+- `lock_namespace` `(string: "default")` - Defines the namespace of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process.
+
+- `lock_path` `(string: "nomad-autoscaler/lock")` - Defines the path of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad Autoscaler
+  agents expected to take part in the same leadership election process.
+
+- `lock_ttl` `(string: "60s")` - Defines the lease period or TTL of the lock used
+  to sync the leader when running in high availability mode. If the Nomad Autoscaler
+  agent does not renew the lock within this period, the lock is considered lost.
+
+- `lock_delay` `(string: "30s")` - Defines the period that the lock will be blocked
+  after the TTL expired without being renewed. This helps prevent split brain
+  situations.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..124dba0a93
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace. If set to `*` all namespaces are queried.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..b5988c78aa
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+- `-high-availability-enabled`: Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired. It defaults to `false`.
+
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
+- `-high-availability-lock-path`: Defines the path of the Nomad variable that
+  will be used to sync the leader when running in high availability mode. This
+  parameter needs to be the same on all Nomad Autoscaler agents expected to
+  take part in the same leadership election process. Defaults to
+  `nomad-autoscaler/lock`.
+
+- `-high-availability-lock-ttl`: Defines the lease period or TTL of the lock used
+  to sync the leader when running on high availability mode. If the Nomad
+  Autoscaler agent does not renew the lock within this period, the lock is
+  considered lost. Defaults to `60s`.
+
+- `-high-availability-lock-delay`: Defines the period that the lock will be
+  blocked after the TTL expired without being renewed. This helps prevent split
+  brain situations. Defaults to `30s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..dc2554d004
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..9fdbbead9a
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..23c9391edf
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered with bounds. This value is always **inclusive**, meaning a
+  metric with the exact same value as `lower_bound` is considered within
+  bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds. This value is always **exclusive**, meaning a
+  metric with the exact same value as `upper_bound` is considered **out** of
+  bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above or
+equal to `lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d293ba125f
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..656fb74905
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+- `retry_attempts` `(int: "15")` - The number of attempts to make while waiting
+  for the cluster to stabilize after a scaling action. It may need to be tuned
+  up if errors such as `failed to ensure all activities completed` occur.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. It may be overridden per policy.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. If set, it overrides the plugin configuration.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_scale_in_protection]: https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..c5960ea9be
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..0d4f106125
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..77fab0bae8
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `query_window_offset` - Defines a time offset from the current time to apply
+  to the query window. A short offset (for example, `1m`) can be used to avoid
+  reading unstable and incomplete data from the APM. A long offset (`168h`,
+  representing 7 days ago) can be used for predictive scaling based on past
+  data.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.8.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.8.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..52c484463c
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.8.x/content/tools/index.mdx b/content/nomad/v1.8.x/content/tools/index.mdx
new file mode 100644
index 0000000000..603707a811
--- /dev/null
+++ b/content/nomad/v1.8.x/content/tools/index.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Port Forward](https://github.com/Mongey/nomad-port-forward) - A tool for forwarding ports from a Nomad job to your local machine
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.8.x/data/api-docs-nav-data.json b/content/nomad/v1.8.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..e89bec40ac
--- /dev/null
+++ b/content/nomad/v1.8.x/data/api-docs-nav-data.json
@@ -0,0 +1,211 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      },
+      {
+        "title": "Upgrade Check",
+        "path": "operator/upgrade-check"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "variables"
+      },
+      {
+        "title": "Variables",
+        "path": "variables/variables"
+      },
+      {
+        "title": "Locks",
+        "path": "variables/locks"
+      }
+    ]
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.8.x/data/docs-nav-data.json b/content/nomad/v1.8.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..b67dfc6bdf
--- /dev/null
+++ b/content/nomad/v1.8.x/data/docs-nav-data.json
@@ -0,0 +1,2457 @@
+[
+  {
+    "title": "Install Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Release Notes",
+    "routes": [
+       {
+         "title": "Overview",
+         "path": "release-notes"
+       },
+       {
+         "title": "Nomad",
+         "routes": [
+           {
+             "title": "Upcoming",
+             "path": "release-notes/nomad/upcoming"
+           },
+           {
+             "title": "v1.8.x",
+             "path": "release-notes/nomad/v1_8_x"
+           }
+         ]
+       }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/consul"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/consul/acl"
+          },
+          {
+            "title": "Service Mesh",
+            "path": "integrations/consul/service-mesh"
+          }
+        ]
+      },
+      {
+        "title": "Vault",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/vault"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/vault/acl"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "ACL",
+        "path": "concepts/acl"
+      },
+      {
+        "title": "Architecture",
+        "path": "concepts/architecture"
+      },
+      {
+        "title": "CPU",
+        "path": "concepts/cpu"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Node Pools",
+        "path": "concepts/node-pools"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Job",
+        "path": "concepts/job"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "keyring",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "configuration/keyring"
+          },
+          {
+            "title": "AWS KMS",
+            "path": "configuration/keyring/awskms"
+          },
+          {
+            "title": "Azure Key Vault",
+            "path": "configuration/keyring/azurekeyvault"
+          },
+          {
+            "title": "GCP Cloud KMS",
+            "path": "configuration/keyring/gcpckms"
+          },
+          {
+            "title": "Vault Transit",
+            "path": "configuration/keyring/transit"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "reporting",
+        "path": "configuration/reporting"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "auth-method",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/auth-method/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/auth-method/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/auth-method/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/auth-method/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/auth-method/update"
+              }
+            ]
+          },
+          {
+            "title": "binding-rule",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/binding-rule/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/binding-rule/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/binding-rule/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/binding-rule/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/binding-rule/update"
+              }
+            ]
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "checks",
+            "path": "commands/alloc/checks"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "pause",
+            "path": "commands/alloc/pause"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "action",
+            "path": "commands/job/action"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "restart",
+            "path": "commands/job/restart"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/license/inspect"
+          }
+        ]
+      },
+      {
+        "title": "login",
+        "path": "commands/login"
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "meta",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "commands/node/meta"
+              },
+              {
+                "title": "apply",
+                "path": "commands/node/meta/apply"
+              },
+              {
+                "title": "read",
+                "path": "commands/node/meta/read"
+              }
+            ]
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "node pool",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node-pool"
+          },
+          {
+            "title": "apply",
+            "path": "commands/node-pool/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/node-pool/delete"
+          },
+          {
+            "title": "info",
+            "path": "commands/node-pool/info"
+          },
+          {
+            "title": "init",
+            "path": "commands/node-pool/init"
+          },
+          {
+            "title": "jobs",
+            "path": "commands/node-pool/jobs"
+          },
+          {
+            "title": "list",
+            "path": "commands/node-pool/list"
+          },
+          {
+            "title": "nodes",
+            "path": "commands/node-pool/nodes"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              },
+              {
+                "title": "health",
+                "path": "commands/operator/autopilot/health"
+              }
+            ]
+          },
+          {
+            "title": "client-state",
+            "path": "commands/operator/client-state"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              },
+              {
+                "title": "transfer-leadership",
+                "path": "commands/operator/raft/transfer-leadership"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "setup",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/setup"
+          },
+          {
+            "title": "consul",
+            "path": "commands/setup/consul"
+          },
+          {
+            "title": "vault",
+            "path": "commands/setup/vault"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "lock",
+            "path": "commands/var/lock"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "action",
+        "path": "job-specification/action"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "consul",
+        "path": "job-specification/consul"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "disconnect",
+        "path": "job-specification/disconnect"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "numa",
+        "path": "job-specification/numa"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "schedule",
+        "path": "job-specification/schedule"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "transparent_proxy",
+        "path": "job-specification/transparent_proxy"
+      },
+      {
+        "title": "ui",
+        "path": "job-specification/ui"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node Pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Exec2",
+        "href": "/plugins/drivers/exec2"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "Podman",
+        "href": "/plugins/drivers/podman"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/community"
+          },
+          {
+            "title": "containerd",
+            "href": "/plugins/drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "href": "/plugins/drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "href": "/plugins/drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jailtask driver",
+            "href": "/plugins/drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "href": "/plugins/drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "href": "/plugins/drivers/community/lxc"
+          },
+          {
+            "title": "Pot",
+            "href": "/plugins/drivers/community/pot"
+          },
+          {
+            "title": "Rkt",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/drivers/community/rkt"
+          },
+          {
+            "title": "Rookout",
+            "href": "/plugins/drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "href": "/plugins/drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "href": "/plugins/drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/iis"
+          },
+          {
+            "title": "Windows IIS",
+            "href": "/plugins/drivers/community/nomad-iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "href": "/plugins/drivers/remote/ecs"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "External",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/plugins/devices"
+          },
+          {
+            "title": "Nvidia",
+            "href": "/plugins/devices/nvidia"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "href": "/plugins/devices/community/usb"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      },
+      {
+        "title": "Considerations for Stateful Workloads",
+        "path": "operations/stateful-workloads"
+      },
+      {
+        "title": "Benchmarking Nomad",
+        "path": "operations/benchmarking"
+      },
+      {
+        "title": "Federate AWS Access with Workload Identity",
+        "path": "operations/aws-oidc-provider"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "Automated license utilization reporting",
+            "path": "enterprise/license/utilization-reporting"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      },
+      {
+        "title": "Sentinel",
+        "path": "enterprise/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.8.x/data/intro-nav-data.json b/content/nomad/v1.8.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..0fdab4c70f
--- /dev/null
+++ b/content/nomad/v1.8.x/data/intro-nav-data.json
@@ -0,0 +1,31 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "href": "https://developer.hashicorp.com/nomad/tutorials/get-started"
+  }
+]
diff --git a/content/nomad/v1.8.x/data/plugins-nav-data.json b/content/nomad/v1.8.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..39b05a7f60
--- /dev/null
+++ b/content/nomad/v1.8.x/data/plugins-nav-data.json
@@ -0,0 +1,130 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Exec2",
+        "path": "drivers/exec2"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "path": "drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "LXC",
+            "path": "drivers/community/lxc",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            }
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/nomad-iis"
+          }
+        ]
+      },
+      {
+        "title": "Remote",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/remote"
+          },
+          {
+            "title": "ECS",
+            "path": "drivers/remote/ecs",
+            "badge": {
+              "text": "Deprecated",
+              "type": "outlined",
+              "color": "neutral"
+            }
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "Nvidia",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "devices/community"
+          },
+          {
+            "title": "USB",
+            "badge": {
+              "text": "Beta",
+              "type": "outlined",
+              "color": "neutral"
+            },
+            "path": "devices/community/usb"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.8.x/data/tools-nav-data.json b/content/nomad/v1.8.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..195677fadc
--- /dev/null
+++ b/content/nomad/v1.8.x/data/tools-nav-data.json
@@ -0,0 +1,231 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "high_availability",
+            "path": "autoscaling/agent/high_availability"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.8.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.8.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.8.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.8.x/img/autoscaling/control-loop.png b/content/nomad/v1.8.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.8.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.8.x/img/autoscaling/policy-eval.png b/content/nomad/v1.8.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.8.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.8.x/img/consul-integration-auth-method.png b/content/nomad/v1.8.x/img/consul-integration-auth-method.png
new file mode 100644
index 0000000000..485cb5d6ac
Binary files /dev/null and b/content/nomad/v1.8.x/img/consul-integration-auth-method.png differ
diff --git a/content/nomad/v1.8.x/img/consul-integration-wi.png b/content/nomad/v1.8.x/img/consul-integration-wi.png
new file mode 100644
index 0000000000..b20fcc3863
Binary files /dev/null and b/content/nomad/v1.8.x/img/consul-integration-wi.png differ
diff --git a/content/nomad/v1.8.x/img/consul-integration-wid-acl-token.png b/content/nomad/v1.8.x/img/consul-integration-wid-acl-token.png
new file mode 100644
index 0000000000..bfb587564b
Binary files /dev/null and b/content/nomad/v1.8.x/img/consul-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.8.x/img/count-dashboard.png b/content/nomad/v1.8.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.8.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.8.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.8.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.8.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/favicon-16x16.png b/content/nomad/v1.8.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/favicon-194x194.png b/content/nomad/v1.8.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/favicon-32x32.png b/content/nomad/v1.8.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/favicon.ico b/content/nomad/v1.8.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.8.x/img/favicons/mstile-144x144.png b/content/nomad/v1.8.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/mstile-150x150.png b/content/nomad/v1.8.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/mstile-310x150.png b/content/nomad/v1.8.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/mstile-310x310.png b/content/nomad/v1.8.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/mstile-70x70.png b/content/nomad/v1.8.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.8.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.8.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.8.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.8.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.8.x/img/home-hero-pattern.svg b/content/nomad/v1.8.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.8.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/logo-hashicorp.svg b/content/nomad/v1.8.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.8.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.8.x/img/logo-text.svg b/content/nomad/v1.8.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.8.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.8.x/img/networking/bridge.png b/content/nomad/v1.8.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.8.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.8.x/img/networking/docker_bridge.png b/content/nomad/v1.8.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.8.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.8.x/img/networking/port_mapping.png b/content/nomad/v1.8.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.8.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-architecture-global.png b/content/nomad/v1.8.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-architecture-region.png b/content/nomad/v1.8.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-bg-pattern.svg b/content/nomad/v1.8.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.8.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.8.x/img/nomad-bridge-network.png b/content/nomad/v1.8.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-data-model.png b/content/nomad/v1.8.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-evaluation-flow.png b/content/nomad/v1.8.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-kubernetes.png b/content/nomad/v1.8.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-numa.png b/content/nomad/v1.8.x/img/nomad-numa.png
new file mode 100644
index 0000000000..0609d7e196
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-numa.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-panel-learn.svg b/content/nomad/v1.8.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.8.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.8.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.8.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.8.x/img/nomad-pe-cores.png b/content/nomad/v1.8.x/img/nomad-pe-cores.png
new file mode 100644
index 0000000000..e11c011d6e
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-pe-cores.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-vars-leader-election-sdk.png b/content/nomad/v1.8.x/img/nomad-vars-leader-election-sdk.png
new file mode 100644
index 0000000000..a547218579
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-vars-leader-election-sdk.png differ
diff --git a/content/nomad/v1.8.x/img/nomad-workload.png b/content/nomad/v1.8.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.8.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.8.x/img/og-image.png b/content/nomad/v1.8.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.8.x/img/og-image.png differ
diff --git a/content/nomad/v1.8.x/img/pattern.svg b/content/nomad/v1.8.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.8.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/practice-pattern.svg b/content/nomad/v1.8.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.8.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/usecase-callout-pattern.svg b/content/nomad/v1.8.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.8.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/usecase-hero-pattern.svg b/content/nomad/v1.8.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.8.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.8.x/img/vault-integration-auth-method.png b/content/nomad/v1.8.x/img/vault-integration-auth-method.png
new file mode 100644
index 0000000000..b6c1d601b9
Binary files /dev/null and b/content/nomad/v1.8.x/img/vault-integration-auth-method.png differ
diff --git a/content/nomad/v1.8.x/img/vault-integration-auth-overview.png b/content/nomad/v1.8.x/img/vault-integration-auth-overview.png
new file mode 100644
index 0000000000..ad26bed43a
Binary files /dev/null and b/content/nomad/v1.8.x/img/vault-integration-auth-overview.png differ
diff --git a/content/nomad/v1.8.x/img/vault-integration-wid-acl-token.png b/content/nomad/v1.8.x/img/vault-integration-wid-acl-token.png
new file mode 100644
index 0000000000..7fd4b406ea
Binary files /dev/null and b/content/nomad/v1.8.x/img/vault-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.8.x/redirects.jsonc b/content/nomad/v1.8.x/redirects.jsonc
new file mode 100644
index 0000000000..32c0078232
--- /dev/null
+++ b/content/nomad/v1.8.x/redirects.jsonc
@@ -0,0 +1,92 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+
+  /**
+   * /s/* redirects for useful links that need a stable URL but we may need to
+   * change its destination in the future.
+   */
+  {
+    "source": "/nomad/s/port-plan-failure",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/operations/monitoring-nomad#progress",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/envoy-bootstrap-error",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/consul/service-mesh#troubleshooting",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/vault-workload-identity-migration",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault",
+    "permanent": false,
+  },
+  // Rename and re-arrange Autoscaling Internals section
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+  // Redirect Consul and Vault integrations page
+  {
+    "source": "/nomad/docs/integrations/vault-integration",
+    "destination": "/nomad/docs/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-integration",
+    "destination": "/nomad/docs/integrations/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-connect",
+    "destination": "/nomad/docs/integrations/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/agent/source",
+    "destination": "/nomad/tools/autoscaling/agent/policy",
+    "permanent": true,
+  },
+]
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/auth-methods.mdx b/content/nomad/v1.9.x/content/api-docs/acl/auth-methods.mdx
new file mode 100644
index 0000000000..42d03ca093
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/auth-methods.mdx
@@ -0,0 +1,514 @@
+---
+layout: api
+page_title: ACL auth methods - HTTP API
+description: The /acl/auth-methods endpoints are used to configure and manage ACL auth methods.
+---
+
+# ACL auth methods HTTP API
+
+The `/acl/auth-methods` and `/acl/auth-method` endpoints are used to manage ACL auth methods.
+
+## Create auth method
+
+This endpoint creates an ACL auth method. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Name is the identifier of the ACL auth method.
+  The name can contain alphanumeric characters and dashes. This name must be
+  unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth method type, supports `OIDC` and `JWT`.
+
+- `TokenLocality` `(string: <required>)` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either `local` or `global`.
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL `${foo}` syntax.
+  Defaults to `${auth_method_type}-${auth_method_name}`.
+
+ - `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set, it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL Auth Method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: <required>)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: <required>)` - The OIDC discovery URL, without
+    any `.well-known` component (base path). Required for `OIDC` method type.
+    Either this, the `JWKSURL` or the `JWTValidationPubKeys` is required for
+    `JWT` method type.
+
+  - `OIDCClientID` `(string: <required>)` - The OAuth client ID configured with
+    your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCClientSecret` `(string: <required>)` - The OAuth client secret
+    configured with your OIDC provider. Required for `OIDC` method type.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `JWTValidationPubKeys` `(array<string>)` - A list of PEM-encoded public keys
+    to use to validate JWT signatures locally. Either this, the `JWKSURL` or the
+    `OIDCDiscoveryURL` is required for `JWT` method type.
+
+  - `JWKSURL` `(string)` - JSON Web Key Sets url for authenticating JWT
+    signatures. Either this, the `JWTValidationPubKeys` or the
+    `OIDCDiscoverURL` is required for `JWT` method type.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `JWKSCACert` `(string)` - PEM encoded CA cert for use by the TLS client used
+    to talk with the JWKS server.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ExpirationLeeway` `(duration)` - Duration in seconds of leeway when
+    validating expiration of a JWT to account for clock skew.
+
+  - `NotBeforeLeeway` `(duration)` - Duration in seconds of leeway when
+    validating not before values of a JWT to account for clock skew.
+
+  - `ClockSkewLeeway` `(duration)` - Duration in seconds of leeway when
+    validating all JWT claims to account for clock skew.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+  - `VerboseLogging` `(bool: false)` - When set to `true`, Nomad will log token claims
+    and information related to binding-rule and role/policy evaluations. Not recommended
+    in production since sensitive information may be present.
+
+### Sample payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "TokenLocality": "local",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "MaxTokenTTL": "1h0m0s",
+  "Default": false,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "local",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": false,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "v1rpi2myptmv1rpi2myptmv1rpi2mypt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+            "groups"
+        ],
+        "BoundAudiences": [
+            "v1rpi2myptmv1rpi2myptmv1rpi2mypt"
+        ],
+        "AllowedRedirectURIs": [
+            "http://localhost:4646/oidc/callback"
+        ],
+        "DiscoveryCaPem": null,
+        "SigningAlgs": null,
+        "ClaimMappings": {
+            "http://example.com/first_name": "first_name",
+            "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+            "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 12
+}
+```
+
+## Update auth method
+
+This endpoint updates an existing ACL auth method. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Names is the identifier of the ACL auth
+  method.  The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Type` `(string: <required>)` - ACL auth role SSO identifier. Currently, the
+  only supported Type is "OIDC."
+
+- `TokenLocality` `(string: "")` - Defines whether the ACL auth method
+  creates a local or global token when performing SSO login. This field must be
+  set to either "local" or "global"
+
+- `TokenNameFormat` `(string <optional>)` - Defines the token name format for the
+  generated tokens This can be lightly templated using HIL '${foo}' syntax.
+  Defaults to '${auth_method_type}-${auth_method_name}'
+
+- `MaxTokenTTL` `(duration: <required>)` - Defines the maximum life of a token created
+  by this method. When set it will initialize the `ExpirationTime` field on all
+  tokens to a value of `Token.CreateTime + AuthMethod.MaxTokenTTL`. This field is
+  not persisted beyond its initial use. Can be specified in the form of `"60s"` or
+  `"5m"` (i.e., 60 seconds or 5 minutes, respectively).
+
+- `Default` `(bool: false)` - Defines whether this ACL auth method is to be
+  set as default when running `nomad login` command.
+
+- `Config` `(ACLAuthMethodConfig: nil)` - The raw configuration to use for
+  the auth method. This parameter is part of the auth method configuration, not
+  specific to Nomad.
+
+  - `OIDCDiscoveryURL` `(string: "")` - The OIDC discovery URL, without
+    any .well-known component (base path).
+
+  - `OIDCClientID` `(string: "")` - The OAuth client ID configured with
+    your OIDC provider.
+
+  - `OIDCClientSecret` `(string: "")` - The OAuth client secret
+    configured with your OIDC provider.
+
+  - `OIDCDisableUserInfo` `(bool: false)` - When set to `true`, Nomad will not make
+    a request to the identity provider to get OIDC UserInfo. You may wish to set this
+    if your identity provider doesn't send any additional claims from the UserInfo
+    endpoint.
+
+  - `OIDCScopes` `(array<string>)` - List of OIDC scopes.
+
+  - `BoundAudiences` `(array<string>)` - List of aud claims that are valid for
+    login; any match is sufficient.
+
+  - `AllowedRedirectURIs` `(array<string>)` - A list of allowed values for
+    redirect_uri. Must be non-empty.
+
+  - `DiscoveryCaPem` `(array<string>)` - PEM encoded CA certs for use by the TLS
+    client used to talk with the OIDC discovery URL. If not set, system
+    certificates are used.
+
+  - `SigningAlgs` `(array<string>)` - A list of supported signing algorithms.
+    Defaults to `RS256`.
+
+  - `ClaimMappings` `(map[string]string)` - Mappings of claims (key) that will
+    be copied to a metadata field (value). Use this if the claim you are capturing
+    is singular (such as an attribute).
+
+    When mapped, the values in each list can be any of a number, string, or
+    boolean and will all be stringified when returned.
+
+  - `ListClaimMappings` `(map[string]string)` - Mappings of claims (key) will be
+    copied to a metadata field (value). Use this if the claim you are capturing is
+    list-like (such as groups).
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-auth-method",
+  "Type": "OIDC",
+  "Tokenlocality": "global",
+  "TokenNameFormat": "${auth_method_type}-${value.user}",
+  "Maxtokenttl": "1h0m0s",
+  "Default": true,
+  "Config": {
+    "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+    "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+    "OIDCClientSecret": "example-client-secret",
+    "OIDCScopes": [
+      "groups"
+    ],
+    "BoundAudiences": [
+      "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+    ],
+    "AllowedRedirectURIs": [
+      "http://localhost:4646/oidc/callback"
+    ],
+    "ClaimMappings": {
+      "http://example.com/first_name": "first_name",
+      "http://example.com/last_name": "last_name"
+    },
+    "ListClaimMappings": {
+      "http://nomad.com/groups": "groups"
+    }
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample Response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+        "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+        "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+        "OIDCClientSecret": "example-client-secret",
+        "OIDCScopes": [
+          "groups"
+        ],
+        "BoundAudiences": [
+          "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+        ],
+        "AllowedRedirectURIs": [
+          "http://localhost:4646/oidc/callback"
+        ],
+        "ClaimMappings": {
+          "http://example.com/first_name": "first_name",
+          "http://example.com/last_name": "last_name"
+        },
+        "ListClaimMappings": {
+          "http://nomad.com/groups": "groups"
+        }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## List auth methods
+
+This endpoint lists all ACL auth methods. This lists the auth methods that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-methods` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ---- |
+| `YES`            | `all`             | None |
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-methods
+```
+
+### Sample response
+
+```json
+[
+    {
+        "CreateIndex": 12,
+        "Default": true,
+        "ModifyIndex": 32,
+        "Name": "example-acl-auth-method",
+        "Type": "OIDC"
+    }
+]
+```
+
+## Read auth method by name
+
+This endpoint reads an ACL Auth Method with the given name. This queries the
+auth method that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/auth-method/:method_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required       |
+| ---------------- | ----------------- | ------------------ |
+| `YES`            | `all`             | `management` token |
+
+### Parameters
+
+- `:method_name` `(string: <required>)` - Specifies the name of the ACL auth
+  method. This is specified as part of the path.
+
+### Sample request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
+
+### Sample response
+
+```json
+{
+    "MaxTokenTTL": "1h0m0s",
+    "Name": "example-acl-auth-method",
+    "Type": "OIDC",
+    "TokenLocality": "global",
+    "TokenNameFormat": "${auth_method_type}-${value.user}",
+    "Default": true,
+    "Config": {
+      "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+      "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+      "OIDCClientSecret": "example-client-secret",
+      "OIDCScopes": [
+        "groups"
+      ],
+      "BoundAudiences": [
+        "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+      ],
+      "AllowedRedirectURIs": [
+        "http://localhost:4646/oidc/callback"
+      ],
+      "ClaimMappings": {
+        "http://example.com/first_name": "first_name",
+        "http://example.com/last_name": "last_name"
+      },
+      "ListClaimMappings": {
+        "http://nomad.com/groups": "groups"
+      }
+    },
+    "CreateTime": "2022-12-08T11:04:43.46206Z",
+    "ModifyTime": "2022-12-08T11:04:43.46206Z",
+    "CreateIndex": 12,
+    "ModifyIndex": 32
+}
+```
+
+## Delete auth method
+
+This endpoint deletes the ACL auth method as identified by its name. This
+request is always forwarded to the authoritative region.
+
+| Method   | Path                               | Produces       |
+| -------- | ---------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/auth-method/:method_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `method_name` `(string: <required>)` - Specifies the name of auth method to
+  delete and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/auth-method/example-acl-auth-method
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/binding-rules.mdx b/content/nomad/v1.9.x/content/api-docs/acl/binding-rules.mdx
new file mode 100644
index 0000000000..9ad1c50a13
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/binding-rules.mdx
@@ -0,0 +1,289 @@
+---
+layout: api
+page_title: ACL Binding Rules - HTTP API
+description: The /acl/binding-rules endpoints are used to configure and manage ACL binding rules.
+---
+
+# ACL Binding Rules HTTP API
+
+The `/acl/binding-rules` and `/acl/binding-rule` endpoints are used to manage ACL Binding Rules.
+
+## Read Binding Rule by Name
+
+This endpoint reads an ACL Binding Rule with the given name. This queries the
+Binding Rule that has been replicated to the region, and may lag behind the
+authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `:rule_id` `(string: <required>)` - Specifies the ID of the ACL Binding Rule.
+  This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "example-acl-auth-method",
+  "BindName": "role",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "updated-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## List Binding Rules
+
+This endpoint lists all ACL Binding Rules. This lists the Binding Rules that have
+been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/acl/binding-rules` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                             |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rules
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AuthMethod": "auth0",
+    "CreateIndex": 16,
+    "Description": "updated-acl-binding-rule",
+    "Hash": "N7aEMsAfl3btWrZSwaWdzcRIAO3uRrRH2yQ8rPsuJ44=",
+    "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Create Binding Rule
+
+This endpoint creates an ACL Binding Rule. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `AuthMethod` `(string: <required>)` - Name of the auth method for which this
+  rule applies to. This is a required field and the method must exist within state
+  before the cluster administrator can create the rule.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.` (e.g. `value.owner == username` for a claim mapping that has `owner`
+  as its key).
+
+- `BindType` `(string: <required>)` - Adjusts how this binding rule is applied
+  at login time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: <required>)` - Target of the binding. Can be lightly
+  templated using HIL ${foo} syntax from available field names. If the bind
+  type is set to `management`, this should not be set. How it is used depends
+  on the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "example-acl-binding-rule",
+  "AuthMethod": "auth0",
+  "Selector": "engineering in list.roles",
+  "BindType": "role",
+  "BindName": "eng-ro",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "example-acl-binding-rule",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 16,
+  "ModifyTime": "2022-12-16T10:29:07.248465Z",
+  "Selector": "engineering in list.roles"
+}
+```
+
+## Update Binding Rule
+
+This endpoint updates an existing ACL Binding Rule. The request is always
+forwarded to the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/acl/binding-rule/:rule_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking
+queries](/nomad/api-docs#blocking-queries) and [required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Description` `(string: "")` - Human-readable, operator set description that
+  can provide additional context about the binding role. This is an operational
+  field.
+
+- `Selector` `(string: "")` - A boolean expression that matches against verified
+  identity attributes returned from the auth method during login.  This is
+  optional and when not set, provides a catch-all rule. If set, it must be a
+  valid [go-bexpr][] expression; for example, a dash in the claim name will
+  require it to be encased in quotes and escaped such as
+  `"\"project-developer\" in list.roles"`.
+
+- `BindType` `(string: "")` - Adjusts how this binding rule is applied at login
+  time. Valid values are `role`, `policy`, and `management`.
+
+- `BindName` `(string: "")` - Target of the binding. Can be lightly templated
+  using HIL ${foo} syntax from available field names. How it is used depends on
+  the BindType.
+
+### Sample Payload
+
+```json
+{
+  "Description": "new description",
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/binding-rule/example-acl-binding-rule
+```
+
+### Sample Response
+
+```json
+{
+  "AuthMethod": "auth0",
+  "BindName": "eng-ro",
+  "BindType": "role",
+  "CreateIndex": 16,
+  "CreateTime": "2022-12-16T10:29:07.248465Z",
+  "Description": "new description",
+  "ID": "5da76548-1a60-b8fb-f9be-c7736a5bca09",
+  "ModifyIndex": 17,
+  "ModifyTime": "2022-12-19T16:40:52.602004Z",
+  "Selector":"engineering in list.roles"
+}
+```
+
+## Delete Binding Rule
+
+This endpoint deletes the ACL Binding Rule as identified by its ID. This request
+is always forwarded to the authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/v1/acl/binding-rule/:rule_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `rule_id` `(string: <required>)` - Specifies the ID of Binding Rule to delete
+  and is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/binding-rule/5da76548-1a60-b8fb-f9be-c7736a5bca09
+```
+
+[go-bexpr]: https://github.com/hashicorp/go-bexpr
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/index.mdx b/content/nomad/v1.9.x/content/api-docs/acl/index.mdx
new file mode 100644
index 0000000000..318f42b704
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/index.mdx
@@ -0,0 +1,15 @@
+---
+layout: api
+page_title: ACL - HTTP API
+description: |-
+  The /acl endpoints provide access to the ACL subsystem.
+---
+
+# ACL HTTP API
+
+The `/acl` endpoints provide access to the ACL subsystem which includes ACL
+bootstrapping, ACL Policies, ACL Roles, ACL Tokens, ACL Auth Methods, and ACL
+Binding Rules. For more details about ACLs, please see the [ACL
+Guide](/nomad/tutorials/access-control).
+
+Please choose a subsection in the navigation for more information.
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/login.mdx b/content/nomad/v1.9.x/content/api-docs/acl/login.mdx
new file mode 100644
index 0000000000..bba8519d27
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/login.mdx
@@ -0,0 +1,77 @@
+---
+layout: api
+page_title: ACL Login - HTTP API
+description: The /acl/login endpoint is used to login via an externally issued token.
+---
+
+# ACL Login HTTP API
+
+The `/acl/login` endpoint is used to log in to Nomad via an externally issued
+token.
+
+## Authenticate with an externally issued token
+
+This endpoint creates an ACL Token. The request is always forwarded to the
+authoritative region.
+
+| Method | Path            | Produces           |
+|--------|-----------------|--------------------|
+| `POST` | `/v1/acl/login` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `LoginToken` `(string: <required>)` - The externally issued authentication token
+  to be exchanged for a Nomad ACL Token.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "github",
+  "LoginToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.NHVaYe26MbtOYhSKkoKYdFVomg4i8ZJd8_-RU8VNbftc4TSMb4bXP3l3YlNWACwyXPGffz5aXHc6lty1Y2t4SWRqGteragsVdZufDn5BlnJl9pdR_kdVFUsra2rWKEofkZeIC4yWytE58sMIihvo9H1ScmmVwBcQP6XETqYd0aSHp1gOa9RdUPDvoXQ5oqygTqVtxaDr6wUFKrKItgBMzWIdNZ6y7O9E0DhEPTbE9rfBo6KTFsHAZnMg4k68CDp2woYIaXbmYTWcvbzIuHO7_37GT79XdIwkm95QJ7hYC9RiwrV7mesbY4PAahERJawntho0my942XheVLmGwLMBkQ"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/login
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "JWT-github",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/oidc.mdx b/content/nomad/v1.9.x/content/api-docs/acl/oidc.mdx
new file mode 100644
index 0000000000..44f8029c0c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/oidc.mdx
@@ -0,0 +1,145 @@
+---
+layout: api
+page_title: ACL OIDC - HTTP API
+description: The /acl/oidc endpoints are used to login via an OIDC provider.
+---
+
+# ACL OIDC HTTP API
+
+The `/acl/oidc` endpoints are used to log in to Nomad via an OIDC provider.
+
+## Get an OIDC authentication URL
+
+This endpoint creates a URL which will allow the caller to navigate to their
+OIDC provider and log in. The returned string is URL encoded.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/auth-url` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/auth-url
+```
+
+### Sample Response
+
+```json
+{
+  "AuthURL": "https://some-domain.uk.auth0.com/authorize?client_id=4fOYtJiC5fo98EQj2TScs2someclient&nonce=fpSPuaodKevKfDU3IeXb&redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&response_type=code&scope=openid&state=st_4i68Nt7FcxDsomestate"
+}
+```
+
+## Complete OIDC Authentication
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/oidc/complete-auth` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `AuthMethodName` `(string: <required>)` - The name of the ACL authentication
+  method to use and will match that used within the call to generate the URL.
+
+- `RedirectURI` `(string: <required>)` - The URI that the response will be sent
+  to when authorization is finished. The value must be included within the auth
+  method's allowed redirect URIs listing.
+
+- `ClientNonce` `(string: <required>)` - A randomly generated string to prevent
+  replay attacks that will match that used within the call to generate the URL.
+
+- `State` `(string: <required>)` - An opaque value used to maintain state between
+  the request and the callback.
+
+- `Code` `(string: <required>)` - The authorization code returned from the OIDC
+  providers authorization endpoint.
+
+### Sample Payload
+
+```json
+{
+  "AuthMethodName": "auth0",
+  "RedirectURI": "http://localhost:4649/oidc/callback",
+  "ClientNonce": "fpSPuaodKevKfDU3IeXb",
+  "State": "st_4i68Nt7FcxDsomestate",
+  "Code": "SplxlOBeZQQYbYS6WxSbIA"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/oidc/complete-auth
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "cbbc7059-3acf-2ef5-378b-495f5f81f733",
+  "CreateIndex": 18,
+  "CreateTime": "2023-01-18T10:53:29.460987Z",
+  "ExpirationTTL": 600000000000,
+  "ExpirationTime": "2023-01-18T11:03:29.460987Z",
+  "Global": true,
+  "ModifyIndex": 18,
+  "Name": "OIDC-auth0",
+  "Policies": [],
+  "Roles": [
+    {
+      "ID": "10b1a678-f71d-d266-2888-8b3e47e317b8",
+      "Name": "engineering-read"
+    }
+  ],
+  "SecretID": "1fce464c-06d1-4020-8564-631c25201ea7",
+  "Type": "client"
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/policies.mdx b/content/nomad/v1.9.x/content/api-docs/acl/policies.mdx
new file mode 100644
index 0000000000..942deea0ce
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/policies.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: ACL Policies - HTTP API
+description: The /acl/policy endpoints are used to configure and manage ACL policies.
+---
+
+# ACL Policies HTTP API
+
+The `/acl/policies` and `/acl/policy/` endpoints are used to manage ACL policies.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## List Policies
+
+This endpoint lists all ACL policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path               | Produces           |
+| ------ | -----   ---------- | ------------------ |
+| `GET`  | `/v1/acl/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                                     |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all policies.<br />Output when given a non-management token will be limited to the policies on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL policies based on
+  a name prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policies?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "",
+    "CreateIndex": 12,
+    "ModifyIndex": 13
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an ACL Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                          | Produces       |
+| ------ | ----------------------------- | -------------- |
+| `POST` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Rules` `(string: <required>)` - Specifies the Policy rules in HCL or JSON format.
+
+- `JobACL` `(JobACL: <optional>)` - Associates the policy with a given job,
+  group, or task. Refer to [Workload Associated ACL
+  Policies][concepts_workload_identity_acl] for more information.
+
+  - `Namespace` `(string: <optional>)` - Attach the policy to the job in this
+    namespace.  Required if `JobID` is set.
+
+  - `JobID` `(string)` - Attach the policy to this job. Required to use `JobACL`.
+
+  - `Group` `(string: <optional>)` - Attach the policy to this group within the
+    job.  Required if `Task` is set.
+
+  - `Task` `(string: <optional>)` - Attach the policy to this task within the job.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "",
+  "JobACL": {
+    "Namespace": "default",
+    "JobID": "example"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads an ACL policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/acl/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                |
+| ---------------- | ----------------- | ------------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to policy |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Rules": "",
+  "Description": "",
+  "CreateIndex": 12,
+  "ModifyIndex": 13
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named ACL policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                          | Produces       |
+| -------- | ----------------------------- | -------------- |
+| `DELETE` | `/v1/acl/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/policy/foo
+```
+
+[concepts_workload_identity_acl]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/roles.mdx b/content/nomad/v1.9.x/content/api-docs/acl/roles.mdx
new file mode 100644
index 0000000000..67a4459683
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/roles.mdx
@@ -0,0 +1,340 @@
+---
+layout: api
+page_title: ACL Roles - HTTP API
+description: The /acl/roles endpoints are used to configure and manage ACL roles.
+---
+
+# ACL Roles HTTP API
+
+The `/acl/roles` and `/acl/role/` endpoints are used to manage ACL Roles.
+
+## Create Role
+
+This endpoint creates an ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `POST` | `/v1/acl/role` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique and must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Update Role
+
+This endpoint updates an existing ACL Role. The request is always forwarded to the
+authoritative region.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `ID` `(string: <required>)` - Specifies the ACL Role, by ID, that is being
+  updated. Must match payload body and request path.
+
+- `Name` `(string: <required>)` - Specifies the human-readable name of the ACL
+  Role. The name can contain alphanumeric characters and dashes.
+  This name must be unique a must not exceed 128 characters.
+
+- `Description` `(string: <optional>)` - A free form human-readable description
+  of the ACL Role. It must not exceed 256 characters.
+
+- `Policies` `(array<ACLRolePolicyLink>)` The list of policies that should be
+  applied to the role. An `ACLRolePolicyLink` is an object with a `"Name"` field
+  to specify a policy.
+
+### Sample Payload
+
+```json
+{
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "Name": "example-acl-role",
+  "Description": "my example ACL Role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## List Roles
+
+This endpoint lists all ACL Roles. This lists the roles that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/acl/roles` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                                                                                               |
+| ---------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `YES`            | `all`             | `management` for all roles.<br />Output when given a non-management token will be limited to the roles on the token itself |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL Roles based on an
+  ID prefix. This is specified as a query string parameter. Because the value
+  is decoded to bytes, the prefix must have an even number of hexadecimal
+  characters (`0-9a-f`).
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles
+```
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/roles?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 26,
+    "Description": "my example ACL Role",
+    "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+    "ModifyIndex": 26,
+    "Name": "example-acl-role",
+    "Policies": [
+      {
+        "Name": "example-acl-policy"
+      }
+    ]
+  }
+]
+```
+
+## Read Role by ID
+
+This endpoint reads an ACL Role with the given ID. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/acl/role/:role_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_id` `(string: <required>)` - Specifies the ID of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Read Role by Name
+
+This endpoint reads an ACL Role with the given name. This queries the role that
+has been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/v1/acl/role/name/:role_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries),
+[consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                              |
+| ---------------- | ----------------- | ----------------------------------------- |
+| `YES`            | `all`             | `management` or token with access to role |
+
+### Parameters
+
+- `:role_name` `(string: <required>)` - Specifies the Name of the ACL Role. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/name/example-acl-role
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 26,
+  "Description": "my example ACL Role",
+  "ID": "77c50812-fcdd-701b-9f1a-6cf55387b09d",
+  "ModifyIndex": 26,
+  "Name": "example-acl-role",
+  "Policies": [
+    {
+      "Name": "example-acl-policy"
+    }
+  ]
+}
+```
+
+## Delete Role
+
+This endpoint deletes the ACL role as identified by the ID. This request is
+always forwarded to the authoritative region.
+
+| Method   | Path                    | Produces       |
+| -------- | ----------------------- | -------------- |
+| `DELETE` | `/v1/acl/role/:role_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `role_id` `(string: <required>)` - Specifies the ID of role to delete and is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: <NOMAD_TOKEN_SECRET_ID>" \
+    https://localhost:4646/v1/acl/role/77c50812-fcdd-701b-9f1a-6cf55387b09d
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/acl/tokens.mdx b/content/nomad/v1.9.x/content/api-docs/acl/tokens.mdx
new file mode 100644
index 0000000000..625c04192a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/acl/tokens.mdx
@@ -0,0 +1,505 @@
+---
+layout: api
+page_title: ACL Tokens - HTTP API
+description: The /acl/token/ endpoints are used to configure and manage ACL tokens.
+---
+
+# ACL Tokens HTTP API
+
+The `/acl/bootstrap`, `/acl/tokens`, and `/acl/token/` endpoints are used to manage ACL tokens.
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Bootstrap Token
+
+This endpoint is used to bootstrap the ACL system and provide the initial management token.
+An operator created token can be provided in the body of the request to bootstrap the cluster
+if required. If no header is provided the cluster will return a generated management token.
+The provided token should be presented in a UUID format.
+This request is always forwarded to the authoritative region. It can only be invoked once
+until a [bootstrap reset](/nomad/tutorials/access-control/access-control-bootstrap#re-bootstrap-acl-system) is performed.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `POST` | `/v1/acl/bootstrap` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+### Sample Operator Payload
+
+```json
+{
+  "BootstrapSecret": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a"
+}
+```
+
+### Sample Request With Operator Token
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @root-token.json \
+    https://localhost:4646/v1/acl/bootstrap
+```
+
+### Sample Response With Operator Token
+
+```json
+{
+  "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+  "SecretID": "2b778dd9-f5f1-6f29-b4b4-9a5fa948757a",
+  "Name": "Bootstrap Token",
+  "Type": "management",
+  "Policies": null,
+  "Global": true,
+  "CreateTime": "2017-08-23T22:47:14.695408057Z",
+  "CreateIndex": 7,
+  "ModifyIndex": 7
+}
+```
+
+## List Tokens
+
+This endpoint lists all ACL tokens. This lists the local tokens and the global
+tokens which have been replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/acl/tokens` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Parameters
+
+- `global` `(bool: false)` - If true, only return ACL tokens that are
+  replicated globally to all regions.
+
+- `prefix` `(string: "")` - Specifies a string to filter ACL tokens based on an
+  accessor ID prefix. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected ACL token. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of ACL tokens to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned ACL tokens should
+  be sorted in the reverse order. By default ACL tokens are returned sorted in
+  chronological order (older ACL tokens first), or in lexicographical order by
+  their ID if the `prefix` or `global` query parameters are used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/tokens
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/acl/tokens?prefix=3da2ed52
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "Name": "Bootstrap Token",
+    "Type": "management",
+    "Policies": null,
+    "Global": true,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "CreateIndex": 7,
+    "ModifyIndex": 7
+  }
+]
+```
+
+## Create Token
+
+This endpoint creates an ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `POST` | `/v1/acl/token` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <optional>)` - Specifies the human-readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either
+  `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for
+  `management` type tokens, otherwise must specify at least one policy for
+  `client` type tokens.
+
+- `Global` `(bool: <optional>)` - If true, indicates this token should be
+  replicated globally to all regions. Otherwise, this token is created local to
+  the target region. This can not be changed after token creation.
+
+- `ExpirationTime` `(time: "")` - If set, this represents the point after which
+  a token should be considered revoked and is eligible for destruction. The
+  default unset value represents NO expiration.
+
+- `ExpirationTTL` `(duration: 0s)` - This is a convenience field and if set will
+  initialize the `ExpirationTime` field to a value of `CreateTime` +
+  `ExpirationTTL`. This value must be between the [`token_min_expiration_ttl`][]
+  and [`token_max_expiration_ttl`][] ACL configuration parameters.
+
+### Sample Payload
+
+```json
+{
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Readonly token",
+  "Type": "client",
+  "Policies": ["readonly"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 52
+}
+```
+
+## Update Token
+
+This endpoint updates an existing ACL Token. If the token is a global token, the request
+is forwarded to the authoritative region. Note that a token cannot be switched from global
+to local or visa versa.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `AccessorID` `(string: <required>)` - Specifies the token (by accessor) that is being updated. Must match payload body and request path.
+
+- `Name` `(string: <optional>)` - Specifies the human readable name of the token.
+
+- `Type` `(string: <required>)` - Specifies the type of token. Must be either `client` or `management`.
+
+- `Policies` `(array<string>: <required>)` - Must be null or blank for `management` type tokens, otherwise must specify at least one policy for `client` type tokens.
+
+### Sample Payload
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Token
+
+This endpoint reads an ACL token with the given accessor. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/:accessor_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                                       |
+| ---------------- | ----------------- | -------------------------------------------------- |
+| `YES`            | `all`             | `management` or a SecretID matching the AccessorID |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Read Self Token
+
+This endpoint reads the ACL token given by the passed SecretID. If the token is a global token
+which has been replicated to the region it may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/v1/acl/token/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required        |
+| ---------------- | ----------------- | ------------------- |
+| `YES`            | `all`             | Any valid ACL token |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    https://localhost:4646/v1/acl/token/self
+```
+
+### Sample Response
+
+```json
+{
+  "AccessorID": "aa534e09-6a07-0a45-2295-a7f77063d429",
+  "SecretID": "8176afd3-772d-0b71-8f85-7fa5d903e9d4",
+  "Name": "Read-write token",
+  "Type": "client",
+  "Policies": ["readwrite"],
+  "Global": false,
+  "CreateTime": "2017-08-23T23:25:41.429154233Z",
+  "CreateIndex": 52,
+  "ModifyIndex": 64
+}
+```
+
+## Delete Token
+
+This endpoint deletes the ACL token by accessor. This request is forwarded to the
+authoritative region for global tokens.
+
+| Method   | Path                         | Produces       |
+| -------- | ---------------------------- | -------------- |
+| `DELETE` | `/v1/acl/token/:accessor_id` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `accessor_id` `(string: <required>)` - Specifies the ACL token accessor ID.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/acl/token/aa534e09-6a07-0a45-2295-a7f77063d429
+```
+
+## Upsert One-Time Token
+
+This endpoint creates a one-time token for the ACL token provided in the
+`X-Nomad-Token` header. Returns 403 if the token header is not set.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -H "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/acl/token/onetime
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 15,
+  "OneTimeToken": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "ExpiresAt": "2017-08-23T22:47:14.695408057Z",
+    "ModifyIndex": 7,
+    "OneTimeSecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe"
+  }
+}
+```
+
+## Exchange One-Time Token
+
+This endpoint exchanges a one-time token for the original ACL token used to
+create it.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/acl/token/onetime/exchange` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `any`        |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d '{ "OneTimeSecretID": "aa534e09-6a07-0a45-2295-a7f77063d429" } \
+    https://localhost:4646/v1/acl/token/onetime/exchange
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 17,
+  "Token": {
+    "AccessorID": "b780e702-98ce-521f-2e5f-c6b87de05b24",
+    "CreateIndex": 7,
+    "CreateTime": "2017-08-23T22:47:14.695408057Z",
+    "Global": true,
+    "Hash": "UhZESkSFGFfX7eBgq5Uwph30OctbUbpe8+dlH2i4whA=",
+    "ModifyIndex": 7,
+    "Name": "Developer token",
+    "Policies": ["developer"],
+    "SecretID": "3f4a0fcd-7c42-773c-25db-2d31ba0c05fe",
+    "Type": "client"
+  }
+}
+```
+
+[`token_min_expiration_ttl`]: /nomad/docs/configuration/acl#token_min_expiration_ttl
+[`token_max_expiration_ttl`]: /nomad/docs/configuration/acl#token_max_expiration_ttl
diff --git a/content/nomad/v1.9.x/content/api-docs/agent.mdx b/content/nomad/v1.9.x/content/api-docs/agent.mdx
new file mode 100644
index 0000000000..47c1491200
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/agent.mdx
@@ -0,0 +1,934 @@
+---
+layout: api
+page_title: Agent - HTTP API
+description: |-
+  The /agent endpoints interact with the local Nomad agent to interact with
+  members and servers.
+---
+
+# Agent HTTP API
+
+The `/agent` endpoints are used to interact with the local Nomad agent.
+
+## List Members
+
+This endpoint queries the agent for the known peers in the gossip pool. This
+endpoint is only applicable to servers. Due to the nature of gossip, this is
+eventually consistent.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/members` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/members
+```
+
+### Sample Response
+
+```json
+{
+  "ServerName": "bacon-mac",
+  "ServerRegion": "global",
+  "ServerDC": "dc1",
+  "Members": [
+    {
+      "Name": "bacon-mac.global",
+      "Addr": "127.0.0.1",
+      "Port": 4648,
+      "Tags": {
+        "mvn": "1",
+        "build": "0.5.5dev",
+        "port": "4647",
+        "bootstrap": "1",
+        "role": "nomad",
+        "region": "global",
+        "dc": "dc1",
+        "vsn": "1"
+      },
+      "Status": "alive",
+      "ProtocolMin": 1,
+      "ProtocolMax": 5,
+      "ProtocolCur": 2,
+      "DelegateMin": 2,
+      "DelegateMax": 4,
+      "DelegateCur": 4
+    }
+  ]
+}
+```
+
+## List Servers
+
+This endpoint lists the known server nodes. The `servers` endpoint is used to
+query an agent in client mode for its list of known servers. Client nodes
+register themselves with these server addresses so that they may dequeue work.
+The servers endpoint can be used to keep this configuration up to date if there
+are changes in the cluster.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/servers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/servers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
+
+## Update Servers
+
+This endpoint updates the list of known servers to the provided list. This
+**replaces** all previous server addresses with the new list.
+
+| Method | Path             | Produces       |
+| ------ | ---------------- | -------------- |
+| `POST` | `/v1/agent/servers` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the list of addresses in the
+  format `ip:port`. This is specified as a query string.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/servers?address=1.2.3.4:4647&address=5.6.7.8:4647"
+```
+
+## Query Self
+
+This endpoint queries the state of the target agent (self).
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/self` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/self
+```
+
+### Sample Response
+
+```json
+{
+  "config": {
+    "Addresses": {
+      "HTTP": "127.0.0.1",
+      "RPC": "127.0.0.1",
+      "Serf": "127.0.0.1"
+    },
+    "AdvertiseAddrs": {
+      "HTTP": "127.0.0.1:4646",
+      "RPC": "127.0.0.1:4647",
+      "Serf": "127.0.0.1:4648"
+    },
+    "BindAddr": "127.0.0.1",
+    "Client": {
+      "AllocDir": "",
+      "ChrootEnv": {},
+      "ClientMaxPort": 14512,
+      "ClientMinPort": 14000,
+      "DisableRemoteExec": false,
+      "Enabled": true,
+      "GCDiskUsageThreshold": 99,
+      "GCInodeUsageThreshold": 99,
+      "GCInterval": 600000000000,
+      "MaxKillTimeout": "30s",
+      "Meta": {},
+      "NetworkInterface": "lo0",
+      "NetworkSpeed": 0,
+      "NodeClass": "",
+      "Options": {
+        "driver.docker.volumes": "true"
+      },
+      "Reserved": {
+        "CPU": 0,
+        "DiskMB": 0,
+        "MemoryMB": 0,
+        "ParsedReservedPorts": null,
+        "ReservedPorts": ""
+      },
+      "Servers": null,
+      "StateDir": ""
+    },
+    "Consul": {
+      "Addr": "",
+      "Auth": "",
+      "AutoAdvertise": true,
+      "CAFile": "",
+      "CertFile": "",
+      "ChecksUseAdvertise": false,
+      "ClientAutoJoin": true,
+      "ClientServiceName": "nomad-client",
+      "EnableSSL": false,
+      "KeyFile": "",
+      "ServerAutoJoin": true,
+      "ServerServiceName": "nomad",
+      "Timeout": 5000000000,
+      "Token": "",
+      "VerifySSL": false
+    },
+    "DataDir": "",
+    "Datacenter": "dc1",
+    "DevMode": true,
+    "DisableAnonymousSignature": true,
+    "DisableUpdateCheck": false,
+    "EnableDebug": true,
+    "EnableSyslog": false,
+    "Files": null,
+    "HTTPAPIResponseHeaders": {},
+    "LeaveOnInt": false,
+    "LeaveOnTerm": false,
+    "LogLevel": "DEBUG",
+    "NodeName": "",
+    "Ports": {
+      "HTTP": 4646,
+      "RPC": 4647,
+      "Serf": 4648
+    },
+    "Region": "global",
+    "Revision": "f551dcb83e3ac144c9dbb90583b6e82d234662e9",
+    "Server": {
+      "BootstrapExpect": 0,
+      "DataDir": "",
+      "Enabled": true,
+      "EnabledSchedulers": null,
+      "HeartbeatGrace": "",
+      "NodeGCThreshold": "",
+      "NumSchedulers": 0,
+      "ProtocolVersion": 0,
+      "RejoinAfterLeave": false,
+      "RetryInterval": "30s",
+      "RetryJoin": [],
+      "RetryMaxAttempts": 0,
+      "StartJoin": []
+    },
+    "SyslogFacility": "LOCAL0",
+    "TLSConfig": {
+      "CAFile": "",
+      "CertFile": "",
+      "EnableHTTP": false,
+      "EnableRPC": false,
+      "KeyFile": "",
+      "VerifyServerHostname": false
+    },
+    "Telemetry": {
+      "CirconusAPIApp": "",
+      "CirconusAPIToken": "",
+      "CirconusAPIURL": "",
+      "CirconusBrokerID": "",
+      "CirconusBrokerSelectTag": "",
+      "CirconusCheckDisplayName": "",
+      "CirconusCheckForceMetricActivation": "",
+      "CirconusCheckID": "",
+      "CirconusCheckInstanceID": "",
+      "CirconusCheckSearchTag": "",
+      "CirconusCheckSubmissionURL": "",
+      "CirconusCheckTags": "",
+      "CirconusSubmissionInterval": "",
+      "CollectionInterval": "1s",
+      "DataDogAddr": "",
+      "DataDogTags": [],
+      "DisableHostname": false,
+      "PublishAllocationMetrics": false,
+      "PublishNodeMetrics": false,
+      "StatsdAddr": "",
+      "StatsiteAddr": "",
+      "UseNodeName": false
+    },
+    "Vault": {
+      "Addr": "https://vault.service.consul:8200",
+      "AllowUnauthenticated": true,
+      "ConnectionRetryIntv": 30000000000,
+      "Enabled": null,
+      "Role": "",
+      "TLSCaFile": "",
+      "TLSCaPath": "",
+      "TLSCertFile": "",
+      "TLSKeyFile": "",
+      "TLSServerName": "",
+      "TLSSkipVerify": null,
+      "TaskTokenTTL": "",
+      "Token": "root"
+    },
+    "Version": "0.5.5",
+    "VersionPrerelease": "dev"
+  },
+  "member": {
+    "Addr": "127.0.0.1",
+    "DelegateCur": 4,
+    "DelegateMax": 4,
+    "DelegateMin": 2,
+    "Name": "bacon-mac.global",
+    "Port": 4648,
+    "ProtocolCur": 2,
+    "ProtocolMax": 5,
+    "ProtocolMin": 1,
+    "Status": "alive",
+    "Tags": {
+      "role": "nomad",
+      "region": "global",
+      "dc": "dc1",
+      "vsn": "1",
+      "mvn": "1",
+      "build": "0.5.5dev",
+      "port": "4647",
+      "bootstrap": "1"
+    }
+  },
+  "stats": {
+    "runtime": {
+      "cpu_count": "8",
+      "kernel.name": "darwin",
+      "arch": "amd64",
+      "version": "go1.8",
+      "max_procs": "7",
+      "goroutines": "79"
+    },
+    "nomad": {
+      "server": "true",
+      "leader": "true",
+      "leader_addr": "127.0.0.1:4647",
+      "bootstrap": "false",
+      "known_regions": "1"
+    },
+    "raft": {
+      "num_peers": "0",
+      "fsm_pending": "0",
+      "last_snapshot_index": "0",
+      "last_log_term": "2",
+      "commit_index": "144",
+      "term": "2",
+      "last_log_index": "144",
+      "snapshot_version_max": "1",
+      "latest_configuration_index": "1",
+      "latest_configuration": "[{Suffrage:Voter ID:127.0.0.1:4647 Address:127.0.0.1:4647}]",
+      "last_contact": "never",
+      "applied_index": "144",
+      "state": "Leader",
+      "last_snapshot_term": "0"
+    },
+    "client": {
+      "heartbeat_ttl": "17.79568937s",
+      "node_id": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "known_servers": "127.0.0.1:4647",
+      "num_allocations": "0",
+      "last_heartbeat": "10.107423052s"
+    },
+    "serf": {
+      "event_time": "1",
+      "event_queue": "0",
+      "encrypted": "false",
+      "member_time": "1",
+      "query_time": "1",
+      "intent_queue": "0",
+      "query_queue": "0",
+      "members": "1",
+      "failed": "0",
+      "left": "0",
+      "health_score": "0"
+    }
+  }
+}
+```
+
+## Join Agent
+
+This endpoint introduces a new member to the gossip pool. This endpoint is only
+eligible for servers.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `POST` | `/v1/agent/join` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `address` `(string: <required>)` - Specifies the address to join in the
+  `ip:port` format. This is provided as a query parameter and may be specified
+  multiple times to join multiple servers.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    "https://localhost:4646/v1/agent/join?address=1.2.3.4&address=5.6.7.8"
+```
+
+### Sample Response
+
+```json
+{
+  "error": "",
+  "num_joined": 2
+}
+```
+
+## Force Leave Agent
+
+This endpoint forces a member of the gossip pool from the `"failed"` state to
+the `"left"` state. This allows the consensus protocol to remove the peer and
+stop attempting replication. This is only applicable for servers.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/agent/force-leave` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Parameters
+
+- `node` `(string: <required>)` - Specifies the name of the node to force leave.
+- `prune` `(boolean: <optional>)` -  Removes failed or left server from the Serf
+  member list immediately. If member is actually still alive, it will eventually rejoin
+  the cluster again.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/agent/force-leave?node=client-ab2e23dc&prune=true
+```
+
+## Health
+
+This endpoint returns whether or not the agent is healthy. When using Consul it
+is the endpoint Nomad will register for its own health checks.
+
+When the agent is unhealthy 500 will be returned along with JSON response
+containing an error message.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/v1/agent/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/health
+```
+
+### Sample Response
+
+```json
+{
+  "client": {
+    "message": "ok",
+    "ok": true
+  },
+  "server": {
+    "message": "ok",
+    "ok": true
+  }
+}
+```
+
+## Host
+
+This endpoint returns data about the agent's host environment from the
+perspective of the agent. It is included in the archive produced by
+nomad operator debug. Known sensitive environment variables are shown as
+`<redacted>`, but the response may still contain sensitive
+information.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/agent/host` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `server_id` `(string: <optional>)` - Specify the server name for
+  targeting.
+
+- `node_id` `(string: <optional>)` - Specify the client node id for
+  targeting.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/host?node_id=4bb9aca7-d43b-43fc-d604-3a271ef0a6c0
+```
+
+### Sample Response
+
+```json
+{
+  "AgentID": "4bb9aca7-d43b-43fc-d604-3a271ef0a6c0",
+  "HostData": {
+    "OS": "x86_64 ip-172-31-92-147 4.15.0-1007-aws Linux #7-Ubuntu SMP Tue Apr 24 10:56:17 UTC 2018",
+    "Network": [
+      {
+        "DialPacket": "\"udp4\" \"\"",
+        "DialStream": "\"tcp4\" \"\"",
+        "ListenPacket": "\"udp4\" \"\"",
+        "ListenStream": "\"tcp4\" \"\"",
+        "address": "127.0.0.1",
+        "binary": "01111111000000000000000000000001",
+        "broadcast": "127.255.255.255",
+        "first_usable": "127.0.0.1",
+        "hex": "7f000001",
+        "host": "127.0.0.1",
+        "last_usable": "127.255.255.254",
+        "mask_bits": "8",
+        "netmask": "255.0.0.0",
+        "network": "127.0.0.0",
+        "octets": "127 0 0 1",
+        "port": "0",
+        "size": "16777216",
+        "string": "127.0.0.1/8",
+        "type": "IPv4",
+        "uint32": "2130706433"
+      }
+    ],
+    "ResolvConf": "nameserver 172.17.0.1\nnameserver 8.8.8.8\n",
+    "Hosts": "127.0.0.1 localhost\n\n# The following lines are desirable for IPv6 capable hosts\n::1 ip6-localhost ip6-loopback\nfe00::0 ip6-localnet\nff00::0 ip6-mcastprefix\nff02::1 ip6-allnodes\nff02::2 ip6-allrouters\nff02::3 ip6-allhosts\n127.0.0.1 ip-172-31-71-163\n127.0.0.1 ip-172-31-92-147\n",
+    "Environment": {
+      "INVOCATION_ID": "b106b6ac67764c9b9f85c5cc5c3357e5",
+      "JOURNAL_STREAM": "9:109527",
+      "LANG": "C.UTF-8",
+      "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
+    },
+    "Disk": {
+      "/": {
+        "DiskMB": 7876,
+        "UsedMB": 4287
+      }
+    }
+  }
+}
+```
+
+## Stream Logs
+
+This endpoint streams logs from the local agent until the connection is closed
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/agent/monitor` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+- `log_level` `(string: "info")` - Specifies a text string containing a log level
+  to filter on, such as `info`. Possible values include `trace`, `debug`,
+  `info`, `warn`, `error`
+
+- `log_json` `(bool: false)` - Specifies if the log format for streamed logs
+  should be JSON.
+
+- `log_include_location` `(bool: false)` - Specifies if the logs streamed should
+  include file and line information.
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a text
+  string containing a node-id to target for streaming.
+
+- `server_id` `(string: "server1.global")` - Specifies a text
+  string containing a server name or "leader" to target a specific remote server
+  or leader for streaming.
+
+- `plain` `(bool: false)` - Specifies if the response should be JSON or
+  plaintext
+
+### Sample Request
+
+```shell-session
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&server_id=leader"
+
+$ curl \
+    "https://localhost:4646/v1/agent/monitor?log_level=debug&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+```
+
+### Sample Response
+
+```json
+{
+  "Offset": 0,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+  "FileEvent": "log"
+}
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible value for this endpoint is "log".
+
+- `Offset` - Offset is the offset into the stream.
+
+## Agent Runtime Profiles
+
+This endpoint is the equivalent of Go's /debug/pprof endpoint but is protected
+by ACLs and supports remote forwarding to a client node or server. See the
+[Golang documentation](https://golang.org/pkg/runtime/pprof/#Profile) for a list
+of available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/v1/agent/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/v1/agent/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/v1/agent/pprof/<pprof profile>` | `application/octet-stream` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Default Behavior
+
+This endpoint is enabled whenever ACLs are enabled. Due to the potentially
+sensitive nature of data contained in profiles, as well as their significant
+performance impact, the agent/pprof endpoint is protected by a high level ACL:
+`agent:write`. For these reasons its recommended to leave [`enable_debug`][]
+unset and only use the ACL-protected endpoints.
+
+The following table explains when each endpoint is available:
+
+| Endpoint          | `enable_debug` | ACLs | **Available?** |
+| ----------------- | -------------- | ---- | -------------- |
+| `/v1/agent/pprof` | unset          | n/a  | no             |
+| `/v1/agent/pprof` | `true`         | n/a  | yes            |
+| `/v1/agent/pprof` | `false`        | n/a  | no             |
+| `/v1/agent/pprof` | unset          | off  | no             |
+| `/v1/agent/pprof` | unset          | on   | **yes**        |
+| `/v1/agent/pprof` | `true`         | off  | yes            |
+| `/v1/agent/pprof` | `false`        | on   | **yes**        |
+
+### Parameters
+
+- `node_id` `(string: "a57b2adb-1a30-2dda-8df0-25abb0881952")` - Specifies a
+  text string containing a Node ID to target for profiling.
+
+- `server_id` `(string: "server1.global")` - Specifies a text string containing
+  a Server ID, name, or `leader` to target a specific remote server or leader
+  for profiling.
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text. For goroutine profiles,
+  setting to 2 extends the plain text format with additional information helpful
+  for debugging stalled goroutines.
+
+### Sample Request
+
+```shell-session
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/goroutine?server_id=leader"
+
+$ go tool pprof goroutine
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/profile?seconds=5&node_id=a57b2adb-1a30-2dda-8df0-25abb0881952"
+
+$ go tool pprof profile
+
+$ curl -O -J \
+    --header "X-Nomad-Token: 8176afd3-772d-0b71-8f85-7fa5d903e9d4" \
+    "https://localhost:4646/v1/agent/pprof/trace?&seconds=5&server_id=server1.global"
+
+go tool trace trace
+```
+
+## Fetch all scheduler worker's status
+
+The `/agent/schedulers` endpoint allow Nomad operators to inspect the state of
+a Nomad server agent's scheduler workers.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers
+```
+
+### Sample Response
+
+```json
+{
+  "schedulers": [
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "5669d6fa-0def-7369-6558-a47c35fdc675",
+      "started": "2021-12-21T19:25:00.911883Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "c919709d-6d14-66bf-b425-80b8167a267e",
+      "started": "2021-12-21T19:25:00.91189Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "f5edb69a-6122-be8f-b32a-23cd8511dba5",
+      "started": "2021-12-21T19:25:00.911961Z",
+      "status": "Paused",
+      "workload_status": "Paused"
+    },
+    {
+      "enabled_schedulers": [
+        "service",
+        "batch",
+        "system",
+        "sysbatch",
+        "_core"
+      ],
+      "id": "458816ae-83cf-0710-d8d4-35d2ad2e42d7",
+      "started": "2021-12-21T19:25:00.912119Z",
+      "status": "Started",
+      "workload_status": "WaitingToDequeue"
+    }
+  ],
+  "server_id": "server1.global"
+}
+
+```
+
+## Read scheduler worker configuration
+
+This endpoint returns data about the agent's scheduler configuration from
+the perspective of the agent. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `agent:read` |
+
+### Parameters
+
+This endpoint accepts no additional parameters.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 8,
+  "server_id": "server1.global"
+}
+```
+
+## Update scheduler worker configuration
+
+This allows a Nomad operator to modify the server's running scheduler
+configuration, which will remain in effect until another update or until the
+node is restarted. For durable changes to this value, set the corresponding
+values—[`num_schedulers`][] and [`enabled_schedulers`][]—in the node's
+configuration file. The response contains the configuration after attempting
+to apply the provided values. This is only applicable for servers.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `PUT`  | `/v1/agent/schedulers/config` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `agent:write` |
+
+### Sample Payload
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12
+  "server_id": "server1.global"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/agent/schedulers/config
+```
+
+### Sample Response
+
+```json
+{
+  "enabled_schedulers": [
+    "service",
+    "batch",
+    "system",
+    "sysbatch",
+    "_core"
+  ],
+  "num_schedulers": 12,
+  "server_id": "server1.global"
+}
+```
+
+[`enabled_schedulers`]: /nomad/docs/configuration/server#enabled_schedulers
+[`num_schedulers`]: /nomad/docs/configuration/server#num_schedulers
+[`enable_debug`]: /nomad/docs/configuration#enable_debug
diff --git a/content/nomad/v1.9.x/content/api-docs/allocations.mdx b/content/nomad/v1.9.x/content/api-docs/allocations.mdx
new file mode 100644
index 0000000000..4590f2aeb4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/allocations.mdx
@@ -0,0 +1,1075 @@
+---
+layout: api
+page_title: Allocations - HTTP API
+description: The /allocation endpoints are used to query for and interact with allocations.
+---
+
+# Allocations HTTP API
+
+The `/allocation` endpoints are used to query for and interact with allocations.
+
+## List Allocations
+
+This endpoint lists all allocations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter allocations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected allocation.
+  This value can be obtained from the `X-Nomad-NextToken` header from the
+  previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of allocations to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all allocations across all the authorized namespaces.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `AllocatedResources` field in the response.
+
+- `task_states` `(bool: true)` - Specifies whether or not to include the
+  `TaskStates` field in the response. TaskStates are included by default but
+  can represent a large percentage of the overall response size. Clusters with
+  a large number of allocations may set `task_states=false` to significantly
+  reduce the size of the response.
+
+- `reverse` `(bool: false)` - Specifies the list of returned allocations should
+  be sorted in the reverse order. By default allocations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?prefix=a8198d79
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocations?namespace=*&prefix=a8198d79
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ClientDescription": "Tasks are running",
+    "ClientStatus": "running",
+    "CreateIndex": 10,
+    "CreateTime": 1636017249798459000,
+    "DeploymentStatus": {
+      "Canary": false,
+      "Healthy": true,
+      "ModifyIndex": 15,
+      "Timestamp": "2021-11-04T10:14:22.054814+01:00"
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "ForceReschedule": null,
+      "Migrate": null,
+      "Reschedule": null
+    },
+    "EvalID": "cb20d15d-861f-8d8d-8253-e93932beea2e",
+    "FollowupEvalID": "",
+    "ID": "5457f16d-0f87-8e6b-5e91-0c7da3a41eb7",
+    "JobID": "example",
+    "JobType": "service",
+    "JobVersion": 0,
+    "ModifyIndex": 15,
+    "ModifyTime": 1636017262190928000,
+    "Name": "example.cache[0]",
+    "Namespace": "default",
+    "NodeID": "f476d2b4-02dc-c216-d031-273396727347",
+    "NodeName": "linux",
+    "PreemptedAllocations": null,
+    "PreemptedByAllocation": "",
+    "RescheduleTracker": null,
+    "TaskGroup": "cache",
+    "TaskStates": {
+      "redis": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249803624000,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017249805254000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1636017252049956000,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": null,
+        "LastRestart": null,
+        "Restarts": 0,
+        "StartedAt": "2021-11-04T09:14:12.04996Z",
+        "State": "running",
+        "TaskHandle": null
+      }
+    }
+  }
+]
+```
+
+## Read Allocation
+
+This endpoint reads information about a specific allocation.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/allocation/:alloc_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Name": "example.cache[0]",
+  "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+  "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+  "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+  "RescheduleTracker": {
+    "Events": [
+      {
+        "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+        "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+        "RescheduleTime": 1517434161192946200,
+        "Delay": "5000000000"
+      }
+    ]
+  },
+  "JobID": "example",
+  "Job": {
+    "Region": "global",
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "AllAtOnce": false,
+    "Datacenters": ["dc1"],
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "RestartPolicy": {
+          "Attempts": 10,
+          "Interval": 300000000000,
+          "Delay": 25000000000,
+          "Mode": "delay"
+        },
+        "Spreads": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Config": {
+              "port_map": [
+                {
+                  "db": 6379
+                }
+              ],
+              "image": "redis:7"
+            },
+            "Env": null,
+            "Services": [
+              {
+                "Name": "redis-cache",
+                "PortLabel": "db",
+                "Tags": ["global", "cache"],
+                "Checks": [
+                  {
+                    "Name": "alive",
+                    "Type": "tcp",
+                    "Command": "",
+                    "Args": null,
+                    "Path": "",
+                    "Protocol": "",
+                    "PortLabel": "",
+                    "Interval": 10000000000,
+                    "Timeout": 2000000000,
+                    "InitialStatus": ""
+                  }
+                ]
+              }
+            ],
+            "Vault": null,
+            "Templates": null,
+            "Constraints": null,
+            "Affinities": null,
+            "Resources": {
+              "CPU": 500,
+              "MemoryMB": 10,
+              "DiskMB": 0,
+              "Networks": [
+                {
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 10,
+                  "ReservedPorts": null,
+                  "DynamicPorts": [
+                    {
+                      "Label": "db",
+                      "Value": 0
+                    }
+                  ]
+                }
+              ]
+            },
+            "Spreads": null,
+            "DispatchPayload": null,
+            "Meta": null,
+            "KillTimeout": 5000000000,
+            "LogConfig": {
+              "MaxFiles": 10,
+              "MaxFileSizeMB": 10
+            },
+            "Artifacts": null,
+            "Leader": false
+          }
+        ],
+        "EphemeralDisk": {
+          "Sticky": false,
+          "SizeMB": 300,
+          "Migrate": false
+        },
+        "Meta": null
+      }
+    ],
+    "Update": {
+      "Stagger": 10000000000,
+      "MaxParallel": 0
+    },
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Payload": null,
+    "Spreads": null,
+    "Meta": null,
+    "VaultToken": "",
+    "Status": "pending",
+    "StatusDescription": "",
+    "CreateIndex": 52,
+    "ModifyIndex": 52,
+    "JobModifyIndex": 52
+  },
+  "TaskGroup": "cache",
+  "Resources": {
+    "CPU": 500,
+    "MemoryMB": 10,
+    "DiskMB": 300,
+    "Networks": [
+      {
+        "Device": "lo0",
+        "CIDR": "",
+        "IP": "127.0.0.1",
+        "MBits": 10,
+        "ReservedPorts": null,
+        "DynamicPorts": [
+          {
+            "Label": "db",
+            "Value": 23116
+          }
+        ]
+      }
+    ]
+  },
+  "SharedResources": {
+    "CPU": 0,
+    "MemoryMB": 0,
+    "DiskMB": 300,
+    "Networks": null
+  },
+  "TaskResources": {
+    "redis": {
+      "CPU": 500,
+      "MemoryMB": 10,
+      "DiskMB": 0,
+      "Networks": [
+        {
+          "Device": "lo0",
+          "CIDR": "",
+          "IP": "127.0.0.1",
+          "MBits": 10,
+          "ReservedPorts": null,
+          "DynamicPorts": [
+            {
+              "Label": "db",
+              "Value": 23116
+            }
+          ]
+        }
+      ]
+    }
+  },
+  "Metrics": {
+    "NodesEvaluated": 1,
+    "NodesFiltered": 0,
+    "NodesAvailable": {
+      "dc1": 1
+    },
+    "NodesInPool": 1,
+    "ClassFiltered": null,
+    "ConstraintFiltered": null,
+    "NodesExhausted": 0,
+    "ClassExhausted": null,
+    "DimensionExhausted": null,
+    "Scores": {
+      "fb2170a8-257d-3c64-b14d-bc06cc94e34c.binpack": 0.6205732522109244
+    },
+    "AllocationTime": 31729,
+    "CoalescedFailures": 0
+  },
+  "DesiredStatus": "run",
+  "DesiredDescription": "",
+  "ClientStatus": "running",
+  "ClientDescription": "",
+  "TaskStates": {
+    "redis": {
+      "State": "running",
+      "Failed": false,
+      "FinishedAt": "0001-01-01T00:00:00Z",
+      "LastRestart": "0001-01-01T00:00:00Z",
+      "Restarts": 0,
+      "StartedAt": "2017-07-25T23:36:26.106431265Z",
+      "Events": [
+        {
+          "Type": "Received",
+          "Time": 1495747371795703800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        },
+        {
+          "Type": "Driver",
+          "Time": 1495747371798867200,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": "Downloading image redis:7"
+        },
+        {
+          "Type": "Started",
+          "Time": 1495747379525667800,
+          "FailsTask": false,
+          "RestartReason": "",
+          "SetupError": "",
+          "DriverError": "",
+          "ExitCode": 0,
+          "Signal": 0,
+          "Message": "",
+          "KillTimeout": 0,
+          "KillError": "",
+          "KillReason": "",
+          "StartDelay": 0,
+          "DownloadError": "",
+          "ValidationError": "",
+          "DiskLimit": 0,
+          "FailedSibling": "",
+          "VaultError": "",
+          "TaskSignalReason": "",
+          "TaskSignal": "",
+          "DriverMessage": ""
+        }
+      ]
+    }
+  },
+  "PreviousAllocation": "",
+  "CreateIndex": 54,
+  "ModifyIndex": 57,
+  "AllocModifyIndex": 54,
+  "CreateTime": 1495747371794276400,
+  "ModifyTime": 1495747371794276400
+}
+```
+
+#### Field Reference
+
+- `Job` - A copy of the job at the time that the allocation is created or
+  updated. This is primarily intended for use by the Nomad client when running
+  the allocation, and it may include stale information on some job fields.
+  Up-to-date information about the job status is available from the
+  [jobs API](/nomad/api-docs/jobs); take care to fetch the version of the job
+  associated with this allocation.
+
+- `TaskStates` - A map of tasks to their current state and the latest events
+  that have effected the state. `TaskState` objects contain the following
+  fields:
+
+  - `State`: The task's current state. It can have one of the following
+    values:
+
+    - `TaskStatePending` - The task is waiting to be run, either for the first
+      time or due to a restart.
+
+    - `TaskStateRunning` - The task is currently running.
+
+    - `TaskStateDead` - The task is dead and will not run again.
+
+  - `StartedAt`: The time the task was last started at. Can be updated through
+    restarts.
+
+  - `FinishedAt`: The time the task was finished at.
+
+  - `LastRestart`: The last time the task was restarted.
+
+  - `Restarts`: The number of times the task has restarted.
+
+  - `Events` - An event contains metadata about the event. The latest 10 events
+    are stored per task. Each event is timestamped (Unix nanoseconds) and has one
+    of the following types:
+
+    - `Setup Failure` - The task could not be started because there was a
+      failure setting up the task prior to it running.
+
+    - `Driver Failure` - The task could not be started due to a failure in the
+      driver.
+
+    - `Started` - The task was started; either for the first time or due to a
+      restart.
+
+    - `Terminated` - The task was started and exited.
+
+    - `Killing` - The task has been sent the kill signal.
+
+    - `Killed` - The task was killed by a user.
+
+    - `Received` - The task has been pulled by the client at the given timestamp.
+
+    - `Failed Validation` - The task was invalid and as such it didn't run.
+
+    - `Restarting` - The task terminated and is being restarted.
+
+    - `Not Restarting` - the task has failed and is not being restarted because
+      it has exceeded its restart policy.
+
+    - `Downloading Artifacts` - The task is downloading the artifact(s)
+    - specified in the task.
+
+    - `Failed Artifact Download` - Artifact(s) specified in the task failed to
+      download.
+
+    - `Restart Signaled` - The task was signaled to be restarted.
+
+    - `Signaling` - The task was is being sent a signal.
+
+    - `Sibling Task Failed` - A task in the same task group failed.
+
+    - `Leader Task Dead` - The group's leader task is dead.
+
+    - `Driver` - A message from the driver.
+
+    - `Task Setup` - Task setup messages.
+
+    - `Building Task Directory` - Task is building its file system.
+
+    Depending on the type the event will have applicable annotations.
+
+## Stop Allocation
+
+This endpoint stops and reschedules a specific allocation.
+
+| Method         | Path                            | Produces           |
+| -------------- | ------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/allocation/:alloc_id/stop` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task
+  [`shutdown_delay`] configuration so that there is no delay between service
+  deregistration and task shutdown. Note that using this parameter will result
+  in failed network connections to the allocation being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST \
+    https://localhost:4646/v1/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/stop
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Index": 54
+}
+```
+
+## Signal Allocation
+
+This endpoint sends a signal to an allocation or task.
+
+| Method         | Path                                     | Produces           |
+| -------------- | ---------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/signal` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Payload
+
+```json
+{
+  "Signal": "SIGUSR1",
+  "Task": "FOO"
+}
+```
+
+If `Task` is omitted, the signal will be sent to all tasks in the allocation.
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"Signal": "SIGUSR1" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/signal
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Restart Allocation
+
+This endpoint restarts an allocation or task in-place.
+
+| Method         | Path                                      | Produces           |
+| -------------- | ----------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/restart` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:alloc-lifecycle` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `TaskName` `(string: "")` - Specifies the individual task to restart. Cannot
+  be used with `AllTasks` set to `true`.
+
+- `AllTasks` `(bool: false)` -  If set to `true` all tasks in the allocation
+  will be restarted, even the ones that already ran. Cannot be set to `true` if
+  `TaskName` is defined.
+
+### Sample Payload
+
+```json
+{
+  "TaskName": "FOO"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl -X POST -d '{"TaskName": "redis" }' \
+    https://localhost:4646/v1/client/allocation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/restart
+```
+
+### Sample Response
+
+```json
+{}
+```
+
+## Exec Allocation
+
+This endpoint executes a command inside the isolation container where an allocation is running.
+It opens a WebSocket to transmit input to and output from the command.
+
+| Method      | Path                                   | Produces               |
+| ----------- | -------------------------------------- | ---------------------- |
+| `WebSocket` | `/v1/client/allocation/:alloc_id/exec` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if target task uses raw_exec driver) |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+- `command` `(string: <required>)` - Specifies the command to be executed. This
+  must be a JSON-encoded array of the command to be executed, e.g. `["echo", "hi"]`
+  or `["/bin/bash"]`. This is specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task name, as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this task, as
+  a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the authentication
+  token in the first frame, as a query parameter.
+
+### Request Frames
+
+Request frames represent the `stdin` stream from the command as well as TTY resize events.
+When `?ws_handshake=true`, the first request frame must contain the authentication token.
+
+The following are valid formats:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# sending stdin data
+{"stdin": {"data": "...base64 encoded string of bytes ..."}}
+
+# indicating stdin is closed
+{"stdin": {"close": true}}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well as exit codes:
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+
+# transferring stderr data
+{"stderr": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stderr
+{"stderr": {"close": true}}
+
+# signaling process exited
+{"exited": true, "result": {"exit_code": <exit_code_int>}}
+
+# basic application-level heartbeat
+{}
+```
+
+### Sample Request and Response
+
+Request and response frames encompass the full range of terminal emulator inputs and outputs, including the control characters necessary to render interactive applications. The example response includes instances of the ANSI “control sequence introducer” (CSI), which is ASCII code 27 followed by `[`.
+
+```
+# \x12: form feed, to clear terminal
+{"stdin":{"data":"DA=="}}
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+```
+
+## Allocation Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed
+allocation ID.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/allocation/:alloc_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the service name. This is
+specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Allocation Checks
+
+The endpoint is used to read all health checks registered within Nomad belonging
+to the passed allocation ID.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+| `GET`  | `/allocation/:alloc_id/checks` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `NO`             | `namespace:read-job`  |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID. This is
+specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/allocation/177160af-26f6-619f-9c9f-5e46d1104395/checks
+```
+
+### Sample Response
+
+```json
+{
+  "a1ed96606694742bf201a640a607e306": {
+    "Check": "redis_probe",
+    "Group": "example.cache[0]",
+    "ID": "a1ed96606694742bf201a640a607e306",
+    "Mode": "healthiness",
+    "Output": "nomad: tcp ok",
+    "Service": "redis",
+    "Status": "success",
+    "Timestamp": 1690442203
+  }
+}
+```
+
+## Override Pause Schedule State
+
+<EnterpriseAlert />
+
+The endpoint is used to override the [`schedule`][schedule] for tasks using
+time based execution.
+
+| Method         | Path                                    | Produces           |
+| -------------- | --------------------------------------- | ------------------ |
+| `POST` / `PUT` | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `NO`             | `namespace:job-submit`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)`- Specifies the UUID of the allocation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `Task` `(string: <required>)` - Specifies the name of the task whose schedule
+  should be overridden.
+
+- `ScheduleState` `(string: <required>)` - Specifies the pause state to force
+  the task into. One of:
+
+    - `"pause"` - Forces the task to pause.
+
+    - `"run"` - Forces the task to run.
+
+    - `"scheduled"` - Removes any overrides and forces the task to adhere to
+      its schedule.
+
+### Sample Request
+
+```shell-session
+$ echo '{"Task": "schedtask", "ScheduleState": "run"}' | \
+  nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0
+}
+```
+
+## Read Pause Schedule State
+
+<EnterpriseAlert />
+
+Retrieve the [`schedule`][schedule] state for a task using time based execution.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/pause` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required              |
+| ---------------- | ------------------------- |
+| `NO`             | `namespace:read-job`      |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the UUID of the allocation.
+  This must be the full UUID, not the short 8-character one. This is
+  specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task from which to
+  retrieve the time-based task execution state.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/allocation/23f520cc-629a-46ff-395f-0661e7aa939e/pause?task=schedtask
+```
+
+### Sample Response
+
+```json
+{
+  "ScheduleState": "scheduled_pause"
+}
+```
+
+#### Field Reference
+
+- `ScheduleState` `(string)`: The task's current paused state. It can can have
+  one of the following values:
+
+  - `""` - The task is running. The only state returned for tasks with no
+    schedule.
+
+  - `force_run` - The task's schedule has been overridden to run.
+
+  - `force_pause` - The task's schedule has been overridden to pause.
+
+  - `scheduled_pause` - The task is paused according to its schedule.
+
+  - `schedule_resume` - A schedule override is being removed. Subsequent calls
+    should return running (`""`) or paused (`scheduled_pause`) states. This
+    state is rarely possible to observe since it transitions immediately to
+    another state.
+
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[schedule]: /nomad/docs/job-specification/schedule
diff --git a/content/nomad/v1.9.x/content/api-docs/client.mdx b/content/nomad/v1.9.x/content/api-docs/client.mdx
new file mode 100644
index 0000000000..b58244ad26
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/client.mdx
@@ -0,0 +1,840 @@
+---
+layout: api
+page_title: Client - HTTP API
+description: |-
+  The /client endpoints are used to access client information, read and write
+  dynamic node metadata, and inspect allocations running on a particular
+  client.
+---
+
+# Client HTTP API
+
+The `/client` endpoints are used to interact with the Nomad clients.
+
+Both clients and servers can handle client endpoints. This is particularly
+useful for when a direct connection to a client is not possible due to the
+network configuration. For high volume access to the client endpoints,
+particularly endpoints streaming file contents, direct access to the node
+should be preferred as it avoids adding additional load to the servers.
+
+When accessing the endpoints via the server, if the desired node is ambiguous
+based on the URL, an additional `?node_id` query parameter must be provided to
+disambiguate.
+
+The [`/node`](/nomad/api-docs/nodes) endpoints provide node information that
+are retried from Nomad servers.
+
+## Read Dynamic Node Metadata
+
+This endpoint queries Node metadata on a specific Client agent and responds
+with the following fields:
+
+- `Meta` `(object)` - The Node metadata that will be registered with the Nomad
+  servers and used by the scheduler (after up to 10 seconds of delay for
+  batching). This is the merged version of the `Static` and `Dynamic` fields.
+
+- `Static` `(object)` - The Node metadata set in the Client agent's
+  configuration file. Only loaded when an agent starts.
+
+- `Dynamic` `(object)` - The Node metadata set via the API (see below). Unlike
+  `Meta` and `Static`, this object may contain `null` values to differentiate
+  "unset" keys from keys with an empty string value (`""`).
+
+Note that [`/v1/node/:node_id`][api-node-read] only contains the `Meta` object.
+It may take up to 10 seconds for dynamic Node metadata to be sent to Servers
+and visible through the Node API. Use the Node API to see the version of Node
+metadata the scheduler uses.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:read`   |
+
+### Parameters
+
+- `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This must be specified as part of the path (`?node_id=...`).
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/metadata
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+
+### Sample Request
+
+## Update Dynamic Node Metadata
+
+This endpoint updates dynamic Node metadata on a specific Client agent. Since
+dynamic Node metadata is only periodically synchronized to Nomad Servers, the
+`Meta` returned in this API may not be reflected in the
+[`/v1/node/:node_id`][api-node-read] API for up to 10 seconds. Scheduling uses
+the Node API version of `Meta`.
+
+For convenience this endpoint returns the same response as a GET.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `POST` | `/v1/client/metadata` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `node:write`  |
+
+### Parameters
+
+- `NodeID` or `:node_id` `(string: <optional>)` - Specifies the node to query.
+  This is required when the endpoint is being accessed via a server. Defaults
+  to the node receiving the request otherwise. This is specified as part of
+  the URL.  Note, this must be the _full_ node ID, not the short 8-character
+  one. This may be specified as part of the path (`?node_id=...`) or request
+  (`NodeID: "..."`).
+
+- `Meta` `(object: <required>)` - Specifies the Node metadata keys to update.
+  Only specified keys are updated.
+
+    - `<key>` `(string: <optional>)` - Specifies a metadata key to update to a
+      particular value. Since `""` is a valid value and distinct from unset,
+      the `null` value is used to mark a key as unset. Keys must be valid
+      dotted HCL identifiers. For example `connect.log_level` is a valid key
+      while `some/path` is not.
+
+### Sample Payload
+
+```json
+{
+  "Meta": {
+    "connect.log_level": "debug",
+    "key_to_unset": null,
+    "foo": "bar"
+  }
+}
+```
+
+### Sample Request
+
+Assuming the above payload is in a file called `meta.json`.
+
+```shell-session
+$ nomad operator api /v1/client/metadata < meta.json
+```
+
+### Sample Response
+
+Formatted by appending `?pretty` above.
+
+```json
+{
+    "Meta": {
+        "connect.proxy_concurrency": "1",
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "debug",
+        "foo": "bar"
+    },
+    "Dynamic": {
+        "key_to_unset": null,
+        "foo": "bar",
+        "connect.log_level": "debug"
+    },
+    "Static": {
+        "connect.sidecar_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.gateway_image": "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}",
+        "connect.log_level": "info",
+        "connect.proxy_concurrency": "1"
+    }
+}
+```
+
+## Read Stats
+
+This endpoint queries the actual resources consumed on a node. The API endpoint
+is hosted by the Nomad client and requests have to be made to the nomad client
+whose resource usage metrics are of interest.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/client/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:read`  |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to query. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/stats
+```
+
+### Sample Response
+
+```json
+{
+  "AllocDirStats": {
+    "Available": 142943150080,
+    "Device": "",
+    "InodesUsedPercent": 0.05312946180421879,
+    "Mountpoint": "",
+    "Size": 249783500800,
+    "Used": 106578206720,
+    "UsedPercent": 42.668233241448746
+  },
+  "CPU": [
+    {
+      "CPU": "cpu0",
+      "Idle": 80,
+      "System": 11,
+      "Total": 20,
+      "User": 9
+    },
+    {
+      "CPU": "cpu1",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    },
+    {
+      "CPU": "cpu2",
+      "Idle": 89,
+      "System": 7.000000000000001,
+      "Total": 11,
+      "User": 4
+    },
+    {
+      "CPU": "cpu3",
+      "Idle": 100,
+      "System": 0,
+      "Total": 0,
+      "User": 0
+    },
+    {
+      "CPU": "cpu4",
+      "Idle": 92.92929292929293,
+      "System": 4.040404040404041,
+      "Total": 7.07070707070707,
+      "User": 3.0303030303030303
+    },
+    {
+      "CPU": "cpu5",
+      "Idle": 99,
+      "System": 1,
+      "Total": 1,
+      "User": 0
+    },
+    {
+      "CPU": "cpu6",
+      "Idle": 92.07920792079209,
+      "System": 4.9504950495049505,
+      "Total": 7.920792079207921,
+      "User": 2.9702970297029703
+    },
+    {
+      "CPU": "cpu7",
+      "Idle": 99,
+      "System": 0,
+      "Total": 1,
+      "User": 1
+    }
+  ],
+  "CPUTicksConsumed": 1126.8044804480448,
+  "DeviceStats": [
+    {
+      "InstanceStats": {
+        "6a61929e-d572-092d-5921-156a913f8e56": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelA",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    },
+    {
+      "InstanceStats": {
+        "73af5d3e-00f9-0786-9bc1-8f5ffa953f15": {
+          "Stats": {
+            "Attributes": {
+              "Used Memory": {
+                "Desc": "Memory in use by the device",
+                "IntNumeratorVal": 128,
+                "Unit": "MiB"
+              }
+            },
+            "Nested": {}
+          },
+          "Summary": {
+            "Desc": "Memory in use by the device",
+            "IntNumeratorVal": 128,
+            "Unit": "MiB"
+          },
+          "Timestamp": "2020-12-18T17:15:08.949806Z"
+        }
+      },
+      "Name": "modelB",
+      "Type": "skeleton",
+      "Vendor": "hashicorp"
+    }
+  ],
+  "DiskStats": [
+    {
+      "Available": 142943150080,
+      "Device": "/dev/disk1",
+      "InodesUsedPercent": 0.05312946180421879,
+      "Mountpoint": "/",
+      "Size": 249783500800,
+      "Used": 106578206720,
+      "UsedPercent": 42.668233241448746
+    }
+  ],
+  "Memory": {
+    "Available": 6232244224,
+    "Free": 470618112,
+    "Total": 17179869184,
+    "Used": 10947624960
+  },
+  "Timestamp": 1495743032992498200,
+  "Uptime": 193520
+}
+```
+
+## Read Allocation Statistics
+
+The client `allocation` endpoint is used to query the actual resources consumed
+by an allocation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/stats` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/stats
+```
+
+### Sample Response
+
+```json
+{
+  "ResourceUsage": {
+    "CpuStats": {
+      "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+      "Percent": 0.14159538847117795,
+      "SystemMode": 0,
+      "ThrottledPeriods": 0,
+      "ThrottledTime": 0,
+      "TotalTicks": 3.256693934837093,
+      "UserMode": 0
+    },
+    "MemoryStats": {
+      "Cache": 1744896,
+      "KernelMaxUsage": 0,
+      "KernelUsage": 0,
+      "MaxUsage": 4710400,
+      "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+      "RSS": 1486848,
+      "Swap": 0
+    }
+  },
+  "Tasks": {
+    "redis": {
+      "Pids": null,
+      "ResourceUsage": {
+        "CpuStats": {
+          "Measured": ["Throttled Periods", "Throttled Time", "Percent"],
+          "Percent": 0.14159538847117795,
+          "SystemMode": 0,
+          "ThrottledPeriods": 0,
+          "ThrottledTime": 0,
+          "TotalTicks": 3.256693934837093,
+          "UserMode": 0
+        },
+        "MemoryStats": {
+          "Cache": 1744896,
+          "KernelMaxUsage": 0,
+          "KernelUsage": 0,
+          "MaxUsage": 4710400,
+          "Measured": ["RSS", "Cache", "Swap", "Max Usage"],
+          "RSS": 1486848,
+          "Swap": 0
+        }
+      },
+      "Timestamp": 1495743243970720000
+    }
+  },
+  "Timestamp": 1495743243970720000
+}
+```
+
+## Read File
+
+This endpoint reads the contents of a file in an allocation directory.
+
+| Method | Path                          | Produces     |
+| ------ | ----------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/cat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/cat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=alloc/file.json
+```
+
+### Sample Response
+
+```text
+(whatever was in the file...)
+```
+
+## Read File at Offset
+
+This endpoint reads the contents of a file in an allocation directory at a
+particular offset and limit.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/readat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `limit` `(int: <required>)` - Specifies the number of bytes to read from the
+  offset.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/readat/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/foo&offset=1323&limit=19303
+```
+
+### Sample Response
+
+```text
+(whatever was in the file, starting from offset, up to limit bytes...)
+```
+
+## Stream File
+
+This endpoint streams the contents of a file in an allocation directory.
+
+| Method | Path                             | Produces     |
+| ------ | -------------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/stream/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+- `follow` `(bool: true)`- Specifies whether to tail the file.
+
+- `offset` `(int: <required>)` - Specifies the byte offset from where content
+  will be read.
+
+- `origin` `(string: "start|end")` - Applies the relative offset to either the
+  start or end of the file.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stream/5fc98185-17ff-26bc-a802-0c74fa471c99?path=/alloc/logs/redis.log
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.log",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.log",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## Stream Logs
+
+This endpoint streams a task's stderr/stdout logs. Note that if logging is set
+to [disabled=true][] for the task, this endpoint will return a 404 error.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/logs/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `NO`             | `namespace:read-logs` or `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `task` `(string: <required>)` - Specifies the name of the task inside the
+  allocation to stream logs from.
+
+- `follow` `(bool: false)`- Specifies whether to tail the logs.
+
+- `type` `(string: "stderr|stdout")` - Specifies the stream to stream.
+
+- `offset` `(int: 0)` - Specifies the offset to start streaming from.
+
+- `origin` `(string: "start|end")` - Specifies either "start" or "end" and
+  applies the offset relative to either the start or end of the logs
+  respectively. Defaults to "start".
+
+- `plain` `(bool: false)` - Return just the plain text without framing. This can
+  be useful when viewing logs in a browser.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/logs/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+({
+  "File": "alloc/logs/redis.stdout.0",
+  "Offset": 3604480,
+  "Data": "NTMxOTMyCjUzMTkzMwo1MzE5MzQKNTMx..."
+},
+{
+  "File": "alloc/logs/redis.stdout.0",
+  "FileEvent": "file deleted"
+})
+```
+
+#### Field Reference
+
+The return value is a stream of frames. These frames contain the following
+fields:
+
+- `Data` - A base64 encoding of the bytes being streamed.
+
+- `FileEvent` - An event that could cause a change in the streams position. The
+  possible values are "file deleted" and "file truncated".
+
+- `Offset` - Offset is the offset into the stream.
+
+- `File` - The name of the file being streamed.
+
+## List Files
+
+This endpoint lists files in an allocation directory.
+
+| Method | Path                         | Produces     |
+| ------ | ---------------------------- | ------------ |
+| `GET`  | `/v1/client/fs/ls/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/ls/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "alloc",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:00.414236712-07:00"
+  },
+  {
+    "Name": "redis",
+    "IsDir": true,
+    "Size": 4096,
+    "FileMode": "drwxrwxr-x",
+    "ModTime": "2016-03-15T15:40:56.810238153-07:00"
+  }
+]
+```
+
+## Stat File
+
+This endpoint stats a file in an allocation.
+
+| Method | Path                           | Produces     |
+| ------ | ------------------------------ | ------------ |
+| `GET`  | `/v1/client/fs/stat/:alloc_id` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required        |
+| ---------------- | ------------------- |
+| `NO`             | `namespace:read-fs` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+- `path` `(string: "/")` - Specifies the path of the file to read, relative to
+  the root of the allocation directory.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/fs/stat/5fc98185-17ff-26bc-a802-0c74fa471c99
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "redis-syslog-collector.out",
+  "IsDir": false,
+  "Size": 96,
+  "FileMode": "-rw-rw-r--",
+  "ModTime": "2016-03-15T15:40:56.822238153-07:00"
+}
+```
+
+## GC Allocation
+
+This endpoint forces a garbage collection of a particular, stopped allocation
+on a node. Note that the allocation will still exist on the server and appear
+in server responses.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `GET`  | `/v1/client/allocation/:alloc_id/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:alloc_id` `(string: <required>)` - Specifies the allocation ID to query.
+  This is specified as part of the URL. Note, this must be the _full_ allocation
+  ID, not the short 8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/client/allocation/5fc98185-17ff-26bc-a802-0c74fa471c99/gc
+```
+
+## GC All Allocation
+
+This endpoint forces a garbage collection of all stopped allocations on a node.
+
+| Method | Path            | Produces     |
+| ------ | --------------- | ------------ |
+| `GET`  | `/v1/client/gc` | `text/plain` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `node_id` `(string: <optional>)` - Specifies the node to target. This is
+  required when the endpoint is being accessed via a server. This is specified as
+  part of the URL. Note, this must be the _full_ node ID, not the short
+  8-character one. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/client/gc
+```
+
+[api-node-read]: /nomad/api-docs/nodes
+[disabled=true]: /nomad/docs/job-specification/logs#disabled
diff --git a/content/nomad/v1.9.x/content/api-docs/deployments.mdx b/content/nomad/v1.9.x/content/api-docs/deployments.mdx
new file mode 100644
index 0000000000..2f49f48f0d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/deployments.mdx
@@ -0,0 +1,562 @@
+---
+layout: api
+page_title: Deployments - HTTP API
+description: The /deployment endpoints are used to query for and interact with deployments.
+---
+
+# Deployments HTTP API
+
+The `/deployment` endpoints are used to query for and interact with deployments.
+
+## List Deployments
+
+This endpoint lists all deployments.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter deployments based on
+  an ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f) .This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected deployment. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of deployments to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last deployment in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `reverse` `(bool: false)` - Specifies the list of returned deployments should
+  be sorted in the reverse order. By default deployments are returned sorted in
+  chronological order (older deployments first), or in lexicographical order
+  by their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployments?prefix=25ba81c
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+    "JobID": "example",
+    "JobVersion": 1,
+    "JobModifyIndex": 17,
+    "JobSpecModifyIndex": 17,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "Promoted": false,
+        "DesiredCanaries": 1,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 1,
+        "HealthyAllocs": 0,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "",
+    "CreateIndex": 19,
+    "ModifyIndex": 19
+  }
+]
+```
+
+## Read Deployment
+
+This endpoint reads information about a specific deployment by ID.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/70638f62-5c19-193e-30d6-f9d6e689ab8e
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "70638f62-5c19-193e-30d6-f9d6e689ab8e",
+  "JobID": "example",
+  "JobVersion": 1,
+  "JobModifyIndex": 17,
+  "JobSpecModifyIndex": 17,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "Promoted": false,
+      "DesiredCanaries": 1,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 1,
+      "HealthyAllocs": 0,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 19,
+  "ModifyIndex": 19
+}
+```
+
+## List Allocations for Deployment
+
+This endpoint lists the allocations created or modified for the given
+deployment.
+
+| Method | Path                                        | Produces           |
+| ------ | ------------------------------------------- | ------------------ |
+| `GET`  | `/v1/deployment/allocations/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/deployment/allocations/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "287b65cc-6c25-cea9-0332-e4a75ca2af98",
+    "EvalID": "9751cb74-1a0d-190e-d026-ad2bc666ad2c",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-06-29T22:29:41.52000268Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1498775380693307400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1498775380693659000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Started",
+            "Time": 1498775381508493800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "DeploymentStatus": null,
+    "CreateIndex": 19,
+    "ModifyIndex": 22,
+    "CreateTime": 1498775380678486300,
+    "ModifyTime": 1498775380678486300
+  }
+]
+```
+
+## Fail Deployment
+
+This endpoint is used to mark a deployment as failed. This should be done to
+force the scheduler to stop creating allocations as part of the deployment or to
+cause a rollback to a previous job version. This endpoint only triggers a rollback
+if the most recent stable version of the job has a different specification than
+the job being reverted.
+
+| Method | Path                                 | Produces           |
+| ------ | ------------------------------------ | ------------------ |
+| `POST` | `/v1/deployment/fail/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/fail/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Pause Deployment
+
+This endpoint is used to pause or unpause a deployment. This is done to pause
+a rolling upgrade or resume it.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/pause/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and in the JSON payload.
+
+- `Pause` `(bool: false)` - Specifies whether to pause or resume the deployment.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Pause": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/pause/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Promote Deployment
+
+This endpoint is used to promote task groups that have canaries for a
+deployment. This should be done when the placed canaries are healthy and the
+rolling upgrade of the remaining allocations should begin.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/promote/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and JSON payload.
+
+- `All` `(bool: false)` - Specifies whether all task groups should be promoted.
+
+- `Groups` `(array<string>: nil)` - Specifies a particular set of task groups
+  that should be promoted.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "All": true
+}
+```
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "Groups": ["web", "api-server"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/promote/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
+
+## Set Allocation Health in Deployment
+
+This endpoint is used to set the health of an allocation that is in the
+deployment manually. In some use cases, automatic detection of allocation health
+may not be desired. As such those task groups can be marked with an upgrade
+policy that uses `health_check = "manual"`. Those allocations must have their
+health marked manually using this endpoint. Marking an allocation as healthy
+will allow the rolling upgrade to proceed. Marking it as failed will cause the
+deployment to fail. This endpoint only triggers a rollback if the most recent stable
+version of the job has a different specification than the job being reverted.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/allocation-health/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path and the JSON payload.
+
+- `HealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as healthy.
+
+- `UnhealthyAllocationIDs` `(array<string>: nil)` - Specifies the set of
+  allocation that should be marked as unhealthy.
+
+### Sample Payload
+
+```javascript
+{
+  "DeploymentID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+  "HealthyAllocationIDs": [
+    "eb13bc8a-7300-56f3-14c0-d4ad115ec3f5",
+    "6584dad8-7ae3-360f-3069-0b4309711cc1"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/allocation-health/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "RevertedJobVersion": 1,
+  "Index": 20
+}
+```
+
+## Unblock Deployment
+
+This endpoint is used to manually mark a blocked multiregion deployment as
+successful. A blocked deployment is a multiregion deployment within a region
+that has completed within a region but is waiting on the other federated
+regions. The endpoint can be used in cases where a failed peer region is
+unable to communicate its failed deployment status to other regions to force a
+deployment to complete.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `POST` | `/v1/deployment/unblock/:deployment_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:deployment_id` `(string: <required>)`- Specifies the UUID of the deployment.
+  This must be the full UUID, not the short 8-character one. This is specified
+  as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/deployment/unblock/5456bd7a-9fc0-c0dd-6131-cbee77f57577
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "0d834913-58a0-81ac-6e33-e452d83a0c66",
+  "EvalCreateIndex": 20,
+  "DeploymentModifyIndex": 20,
+  "Index": 20
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/evaluations.mdx b/content/nomad/v1.9.x/content/api-docs/evaluations.mdx
new file mode 100644
index 0000000000..2984cdaf1e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/evaluations.mdx
@@ -0,0 +1,447 @@
+---
+layout: api
+page_title: Evaluations - HTTP API
+description: The /evaluation are used to query for and interact with evaluations.
+---
+
+# Evaluations HTTP API
+
+The `/evaluation` endpoints are used to query for and interact with evaluations.
+
+## List Evaluations
+
+This endpoint lists all evaluations.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an
+  even number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter and is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string which is the `ID` field of
+  the next expected evaluation. This value can be obtained from the
+  `X-Nomad-NextToken` header from the previous response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of evaluations to
+  return for this request. If omitted, the response is not
+  paginated. The `ID` of the last evaluation in the response can be
+  used as the `last_token` of the next request to fetch additional
+  pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `job` `(string: "")` - Filter the list of evaluations to a specific
+  job ID.
+
+- `status` `(string: "")` - Filter the list of evaluations to a
+  specific evaluation status (one of `blocked`, `pending`, `complete`,
+  `failed`, or `canceled`).
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
+  be sorted in the reverse order. By default evaluations are returned sorted in
+  chronological order (older evaluations first), or in lexicographical order by
+  their ID if the `prefix` query parameter is used.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 52,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "SnapshotIndex": 53,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "CreateIndex": 53,
+    "ModifyIndex": 55
+  }
+]
+```
+
+## Read Evaluation
+
+This endpoint reads information about a specific evaluation by ID.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+- `related` `(bool: false)` - Specifies if related evaluations should be
+  returned. Related evaluations are the ones that can be reached by following
+  the trail of IDs for `NextEval`, `PreviousEval`, and `BlockedEval`. This is
+  specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/2deb5f06-a100-f01a-3316-5e501a4965e7?related=true
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 28,
+  "CreateTime": 1647394818583344000,
+  "FailedTGAllocs": {
+    "cache": {
+      "AllocationTime": 4111,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 0
+      },
+      "NodesEvaluated": 0,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 0,
+      "QuotaExhausted": null,
+      "ResourcesExhausted": null,
+      "ScoreMetaData": null,
+      "Scores": null
+    }
+  },
+  "ID": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+  "JobID": "example",
+  "ModifyIndex": 28,
+  "ModifyTime": 1647394818583344000,
+  "Namespace": "default",
+  "PreviousEval": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+  "Priority": 50,
+  "RelatedEvals": [
+    {
+      "BlockedEval": "2deb5f06-a100-f01a-3316-5e501a4965e7",
+      "CreateIndex": 27,
+      "CreateTime": 1647394818582736000,
+      "DeploymentID": "79ae0a49-acf6-0fcf-183f-8646f3167b88",
+      "ID": "0f98f7ea-59ae-4d90-d9bd-b8ce80b9e100",
+      "JobID": "example",
+      "ModifyIndex": 30,
+      "ModifyTime": 1647394818583565000,
+      "Namespace": "default",
+      "NextEval": "",
+      "NodeID": "",
+      "PreviousEval": "",
+      "Priority": 50,
+      "Status": "complete",
+      "StatusDescription": "",
+      "TriggeredBy": "node-drain",
+      "Type": "service",
+      "WaitUntil": null
+    }
+  ],
+  "SnapshotIndex": 27,
+  "Status": "blocked",
+  "StatusDescription": "created to place remaining allocations",
+  "TriggeredBy": "queued-allocs",
+  "Type": "service"
+}
+```
+
+## Delete Evaluations
+
+This endpoint deletes evaluations. In order to utilise this endpoint the
+eval broker should be paused via the
+[operator scheduler update configuration][update_scheduler_configuration] API
+endpoint.
+
+This API endpoint should be used cautiously and only in outage situations where
+there is a large backlog of evaluations not being processed. During most normal
+and outage scenarios, Nomad's reconciliation and state management will handle
+evaluations as needed.
+
+| Method    | Path              | Produces           |
+| --------- | ----------------- | ------------------ |
+| `DELETE`  | `/v1/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `EvalIDs` `(array<string>: <required>)`- An array of evaluation UUIDs to
+  delete. This must be a full length UUID and not a prefix.
+
+### Sample Payload
+
+```javascript
+{
+  "EvalIDs": [
+    "167ec27d-2e36-979a-280a-a6b920d382db",
+    "6c193955-ac66-42e2-f4c7-f1fc707f1f5e"
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --data @payload.json \
+    https://localhost:4646/v1/evaluations
+```
+
+## List Allocations for Evaluation
+
+This endpoint lists the allocations created or modified for the given
+evaluation.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `GET`  | `/v1/evaluation/:eval_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:eval_id` `(string: <required>)`- Specifies the UUID of the evaluation. This
+  must be the full UUID, not the short 8-character one. This is specified as
+  part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluation/5456bd7a-9fc0-c0dd-6131-cbee77f57577/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+    "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+    "Name": "example.cache[0]",
+    "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495747371795703800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495747371798867200,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495747379525667800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 54,
+    "ModifyIndex": 57,
+    "CreateTime": 1495747371794276400
+  }
+]
+```
+
+## Count Evaluations
+
+This endpoint counts evaluations. Note that Nomad's state store architecture
+makes calculating this count unexpectedly expensive (similar in cost to the List
+API), and this API was designed for use during recovery operations with the
+`nomad eval delete` command. It is not recommended to use this API for
+monitoring. The `nomad.nomad.broker.*`  metrics are better for that use
+case. See the [metrics reference][] for details.
+
+
+| Method | Path                    | Produces           |
+|--------|-------------------------|--------------------|
+| `GET`  | `/v1/evaluations/count` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter evaluations based on an
+  ID prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query string
+  parameter and is used before any `filter` expression is applied.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+  Specifying `*` will return all evaluations across all authorized namespaces.
+  This parameter is used before any `filter` expression is applied.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/evaluations/count?prefix=25ba81
+```
+
+### Sample Response
+
+```json
+{
+  "Count": 36
+  "Index": 133,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": ""
+}
+```
+
+[update_scheduler_configuration]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[metrics reference]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.9.x/content/api-docs/events.mdx b/content/nomad/v1.9.x/content/api-docs/events.mdx
new file mode 100644
index 0000000000..3c488597d0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/events.mdx
@@ -0,0 +1,391 @@
+---
+layout: api
+page_title: Events - HTTP API
+description: |-
+  The /event endpoints are used to query for and stream Nomad events.
+---
+
+# Events HTTP API
+
+The `/event/stream` endpoint is used to stream events generated by Nomad.
+
+## Event Stream
+
+This endpoint streams a server's backlog of events as well as new events as they occur.
+The stream will be kept alive until the connection is closed. The format of the response
+body will be valid [ndjson](https://github.com/ndjson/ndjson-spec). This means splitting
+the streaming response at every `\n` character will guarantee each message is a valid
+JSON object. Note that each JSON object may include multiple events (high server
+activity) or no events (heartbeating to keep the connection open).
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/event/stream` | `application/json` |
+
+The table below shows this endpoint's [required ACLs](/nomad/api-docs#acls). Due to
+the nature of this endpoint individual topics require specific policies.
+
+Note that if you do not include a `topic` parameter all topics will be included
+by default, requiring a management token.
+
+| Topic        | ACL Required         |
+| ------------ | -------------------- |
+| `*`          | `management`         |
+| `ACLToken`   | `management`         |
+| `ACLPolicy`  | `management`         |
+| `ACLRole`    | `management`         |
+| `Job`        | `namespace:read-job` |
+| `Allocation` | `namespace:read-job` |
+| `Deployment` | `namespace:read-job` |
+| `Evaluation` | `namespace:read-job` |
+| `Node`       | `node:read`          |
+| `NodePool`   | `management`         |
+| `Service`    | `namespace:read-job` |
+
+### Parameters
+
+- `index` `(int: 0)` - Specifies the index to start streaming events from. If
+  the requested index is no longer in the buffer the stream will start at the
+  next available index.
+
+- `namespace` `(string: "default")` - Specifies the target namespace to filter
+  on. Specifying `*` includes all namespaces for event types that support
+  namespaces. If you specify all namespaces (`*`) you'll either need a management
+  token, or an ACL Policy that explicitly applies to all namespaces (`*`).
+
+- `topic` `(topic:filter_key: "*:*")` - Specifies a topic to subscribe to and
+  filter on. The default is to subscribe to all topics. Multiple topics may be
+  specified by passing multiple `topic` parameters. A valid topic parameter
+  includes a `topic` type and an optional `filter_key` separated by a colon
+  `:`. As an example `?topic=Deployment:redis` would subscribe to all
+  `Deployment` events for a job redis. an additional topic
+  `&topic=Deployment:web` would include deployment events for redis and web. To
+  only subscribe to `Node` events a topic parameter of `?topic=Node` without a
+  separator value would be used. `?topic=Node:*` is also valid.
+
+### Event Topics
+
+| Topic      | Output                          |
+| ---------- | ------------------------------- |
+| ACLToken   | ACLToken                        |
+| ACLPolicy  | ACLPolicy                       |
+| ACLRoles   | ACLRole                         |
+| Allocation | Allocation (no job information) |
+| Job        | Job                             |
+| Evaluation | Evaluation                      |
+| Deployment | Deployment                      |
+| Node       | Node                            |
+| NodeDrain  | Node                            |
+| NodePool   | NodePool                        |
+| Service    | Service Registrations           |
+
+### Event Types
+
+| Type                          |
+| ----------------------------- |
+| ACLTokenUpserted              |
+| ACLTokenDeleted               |
+| ACLPolicyUpserted             |
+| ACLPolicyDeleted              |
+| ACLRoleUpserted               |
+| ACLRoleDeleted                |
+| AllocationCreated             |
+| AllocationUpdated             |
+| AllocationUpdateDesiredStatus |
+| DeploymentStatusUpdate        |
+| DeploymentPromotion           |
+| DeploymentAllocHealth         |
+| EvaluationUpdated             |
+| JobRegistered                 |
+| JobDeregistered               |
+| JobBatchDeregistered          |
+| NodeRegistration              |
+| NodeDeregistration            |
+| NodeEligibility               |
+| NodeDrain                     |
+| NodeEvent                     |
+| NodePoolUpserted              |
+| NodePoolDeleted               |
+| PlanResult                    |
+| ServiceRegistration           |
+| ServiceDeregistration         |
+
+### Sample Request
+
+```shell-session
+# Subscribe to all events and topics in the default namespace
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream
+```
+
+```shell-session
+# Subscribe to all events and topics in all namespaces
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?namespace=*
+```
+
+```shell-session
+# Start at index 100 and subscribe to all Evaluation events
+$ curl -s -v -N http://127.0.0.1:4646/v1/event/stream?index=100&topic=Evaluation
+```
+
+```shell-session
+$ curl -G -s -v -N \
+--data-urlencode "topic=Node:ccc4ce56-7f0a-4124-b8b1-a4015aa82c40" \
+--data-urlencode "topic=Deployment" \
+--data-urlencode "topic=Job:web" \
+http://127.0.0.1:4646/v1/event/stream
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 7,
+  "Events": [
+    {
+      "Topic": "Node",
+      "Type": "NodeRegistration",
+      "Key": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+      "Namespace": "",
+      "FilterKeys": null,
+      "Index": 7,
+      "Payload": {
+        "Node": {
+          "ID": "ccc4ce56-7f0a-4124-b8b1-a4015aa82c40",
+          "Datacenter": "dc1",
+          "Name": "nomad-4",
+          "HTTPAddr": "127.0.0.1:4646",
+          "TLSEnabled": false,
+          "Attributes": {
+            "cpu.arch": "amd64",
+            "cpu.frequency": "4200",
+            "cpu.modelname": "Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz",
+            "cpu.numcores": "8",
+            "cpu.totalcompute": "33600",
+            "driver.docker": "1",
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.os_type": "linux",
+            "driver.docker.runtimes": "runc",
+            "driver.docker.version": "19.03.13",
+            "driver.mock_driver": "1",
+            "driver.raw_exec": "1",
+            "kernel.name": "linux",
+            "kernel.version": "5.4.0-48-generic",
+            "memory.totalbytes": "16525733888",
+            "nomad.revision": "8c88f29bff0849720e33b0cc73af87495358f3b8",
+            "nomad.version": "0.13.0-dev",
+            "os.name": "ubuntu",
+            "os.signals": "SIGBUS,SIGFPE,SIGTRAP,SIGTTOU,SIGWINCH,SIGXFSZ,SIGHUP,SIGILL,SIGALRM,SIGCHLD,SIGSYS,SIGXCPU,SIGPROF,SIGQUIT,SIGTERM,SIGUSR2,SIGCONT,SIGIO,SIGSEGV,SIGTTIN,SIGIOT,SIGKILL,SIGPIPE,SIGABRT,SIGINT,SIGSTOP,SIGTSTP,SIGURG,SIGUSR1",
+            "os.version": "20.04",
+            "unique.advertise.address": "127.0.0.1:4646",
+            "unique.cgroup.mountpoint": "/sys/fs/cgroup/systemd",
+            "unique.hostname": "x1c",
+            "unique.network.ip-address": "127.0.0.1",
+            "unique.storage.bytesfree": "299488927744",
+            "unique.storage.bytestotal": "502468108288",
+            "unique.storage.volume": "/dev/nvme0n1p2"
+          },
+          "NodeResources": {
+            "Cpu": {
+              "CpuShares": 33600
+            },
+            "Memory": {
+              "MemoryMB": 15760
+            },
+            "Disk": {
+              "DiskMB": 285614
+            },
+            "Networks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "NodeNetworks": [
+              {
+                "Mode": "bridge",
+                "Device": "",
+                "MacAddress": "",
+                "Speed": 0,
+                "Addresses": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "MacAddress": "",
+                "Speed": 1000,
+                "Addresses": [
+                  {
+                    "Family": "ipv4",
+                    "Alias": "default",
+                    "Address": "127.0.0.1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  },
+                  {
+                    "Family": "ipv6",
+                    "Alias": "default",
+                    "Address": "::1",
+                    "ReservedPorts": "",
+                    "Gateway": ""
+                  }
+                ]
+              }
+            ],
+            "Devices": null
+          },
+          "ReservedResources": {
+            "Cpu": {
+              "CpuShares": 0
+            },
+            "Memory": {
+              "MemoryMB": 0
+            },
+            "Disk": {
+              "DiskMB": 0
+            },
+            "Networks": {
+              "ReservedHostPorts": ""
+            }
+          },
+          "Resources": {
+            "CPU": 33600,
+            "MemoryMB": 15760,
+            "DiskMB": 285614,
+            "IOPS": 0,
+            "Networks": [
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "127.0.0.1/32",
+                "IP": "127.0.0.1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              },
+              {
+                "Mode": "host",
+                "Device": "lo",
+                "CIDR": "::1/128",
+                "IP": "::1",
+                "MBits": 1000,
+                "DNS": null,
+                "ReservedPorts": null,
+                "DynamicPorts": null
+              }
+            ],
+            "Devices": null
+          },
+          "Reserved": {
+            "CPU": 0,
+            "MemoryMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          },
+          "Links": null,
+          "Meta": {
+            "connect.gateway_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09",
+            "connect.log_level": "info",
+            "connect.sidecar_image": "envoyproxy/envoy:v1.11.2@sha256:a7769160c9c1a55bb8d07a3b71ce5d64f72b1f665f10d81aa1581bc3cf850d09"
+          },
+          "NodeClass": "",
+          "ComputedClass": "v1:9803688035578634002",
+          "Drain": false,
+          "DrainStrategy": null,
+          "SchedulingEligibility": "eligible",
+          "Status": "initializing",
+          "StatusDescription": "",
+          "StatusUpdatedAt": 1602770857,
+          "Events": [
+            {
+              "Message": "Node registered",
+              "Subsystem": "Cluster",
+              "Details": null,
+              "Timestamp": "2020-10-15T10:07:37-04:00",
+              "CreateIndex": 0
+            }
+          ],
+          "Drivers": {
+            "docker": {
+              "Attributes": {
+                "driver.docker": "true",
+                "driver.docker.bridge_ip": "172.17.0.1",
+                "driver.docker.os_type": "linux",
+                "driver.docker.runtimes": "runc",
+                "driver.docker.version": "19.03.13"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.904159516-04:00"
+            },
+            "exec": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445083368-04:00"
+            },
+            "java": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "Driver must run as root",
+              "UpdateTime": "2020-10-15T10:07:37.445601605-04:00"
+            },
+            "qemu": {
+              "Attributes": null,
+              "Detected": false,
+              "Healthy": false,
+              "HealthDescription": "",
+              "UpdateTime": "2020-10-15T10:07:37.445684857-04:00"
+            },
+            "raw_exec": {
+              "Attributes": {
+                "driver.raw_exec": "true"
+              },
+              "Detected": true,
+              "Healthy": true,
+              "HealthDescription": "Healthy",
+              "UpdateTime": "2020-10-15T10:07:37.445431163-04:00"
+            }
+          },
+          "CSIControllerPlugins": null,
+          "CSINodePlugins": null,
+          "HostVolumes": null,
+          "CreateIndex": 7,
+          "ModifyIndex": 7
+        }
+      }
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/index.mdx b/content/nomad/v1.9.x/content/api-docs/index.mdx
new file mode 100644
index 0000000000..1f4ca6c921
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/index.mdx
@@ -0,0 +1,731 @@
+---
+layout: api
+page_title: HTTP API
+description: |-
+  Nomad exposes a RESTful HTTP API to control almost every aspect of the
+  Nomad agent.
+---
+
+# HTTP API
+
+The main interface to Nomad is a RESTful HTTP API. The API can query the current
+state of the system as well as modify the state of the system. The Nomad CLI
+actually invokes Nomad's HTTP for many commands.
+
+## Version Prefix
+
+All API routes are prefixed with `/v1/`.
+
+## Addressing and Ports
+
+Nomad binds to a specific set of addresses and ports. The HTTP API is served via
+the `http` address and port. This `address:port` must be accessible locally. If
+you bind to `127.0.0.1:4646`, the API is only available _from that host_. If you
+bind to a private internal IP, the API will be available from within that
+network. If you bind to a public IP, the API will be available from the public
+Internet (not recommended).
+
+The default port for the Nomad HTTP API is `4646`. This can be overridden via
+the Nomad configuration block. Here is an example curl request to query a Nomad
+server with the default configuration:
+
+```shell-session
+$ curl http://127.0.0.1:4646/v1/agent/members
+```
+
+The conventions used in the API documentation do not list a port and use the
+standard URL `localhost:4646`. Be sure to replace this with your Nomad agent URL
+when using the examples.
+
+## Data Model and Layout
+
+There are five primary nouns in Nomad:
+
+- jobs
+- nodes
+- allocations
+- deployments
+- evaluations
+
+[![Nomad Data Model](/img/nomad-data-model.png)](/img/nomad-data-model.png)
+
+Jobs are submitted by users and represent a _desired state_. A job is a
+declarative description of tasks to run which are bounded by constraints and
+require resources. Jobs can also have affinities which are used to express placement
+preferences. Nodes are the servers in the clusters that tasks can be
+scheduled on. The mapping of tasks in a job to nodes is done using allocations.
+An allocation is used to declare that a set of tasks in a job should be run on a
+particular node. Scheduling is the process of determining the appropriate
+allocations and is done as part of an evaluation. Deployments are objects to
+track a rolling update of allocations between two versions of a job.
+
+The API is modeled closely on the underlying data model. Use the links to the
+left for documentation about specific endpoints. There are also "Agent" APIs
+which interact with a specific agent and not the broader cluster used for
+administration.
+
+## ACLs
+
+Several endpoints in Nomad use or require ACL tokens to operate. The token are used to authenticate the request and determine if the request is allowed based on the associated authorizations. Tokens are specified per-request by using the `X-Nomad-Token` request header or with the Bearer scheme in the authorization header set to the `SecretID` of an ACL Token.
+
+For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+## Authentication
+
+When ACLs are enabled, a Nomad token should be provided to API requests using the `X-Nomad-Token` header or with the Bearer scheme in the authorization header. When using authentication, clients should communicate via TLS.
+
+Here is an example using curl with `X-Nomad-Token`:
+
+```shell-session
+$ curl \
+    --header "X-Nomad-Token: aa534e09-6a07-0a45-2295-a7f77063d429" \
+    https://localhost:4646/v1/jobs
+```
+
+Below is an example using `curl` with a [RFC6750](https://tools.ietf.org/html/rfc6750) Bearer token:
+
+```shell-session
+$ curl \
+    --header "Authorization: Bearer <token>" \
+    http://localhost:4646/v1/jobs
+```
+
+## Namespaces
+
+Nomad has support for namespaces, which allow jobs and their associated objects
+to be segmented from each other and other users of the cluster. When using
+non-default namespace, the API request must pass the target namespace as an API
+query parameter.
+
+Here is an example using curl to query the `qa` namespace:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=qa'
+```
+
+Use a wildcard (`*`) to query all namespaces:
+
+```shell-session
+$ curl 'localhost:4646/v1/jobs?namespace=*'
+```
+
+## Filtering
+
+Filter expressions refine data queries for some API listing endpoints, as
+notated in the individual API endpoints documentation.
+
+To create a filter expression, you will write one or more expressions. Each
+expression has matching operators composed of selectors and values.
+
+Filtering is executed on the Nomad server, before data is returned, reducing
+the network load. To pass a filter expression to Nomad, use the `filter` query
+parameter with the URL encoded expression when sending requests to HTTP API
+endpoints that support it.
+
+```shell-session
+$ curl --get https://localhost:4646/v1/<path> \
+    --data-urlencode 'filter=<filter expression>'
+```
+
+The filter expression can also be specified in the
+[`-filter`][cli_operator_api_filter] flag of the
+[`nomad operator api`][cli_operator_api] command.
+
+```shell-session
+$ nomad operator api -filter '<filter expression>' /v1/<path>
+```
+
+Some endpoints may have other query parameters that are used for filtering, but
+they can't be used with the `filter` query parameter. Doing so will result in a
+`400` status error response. These query parameters are usually backed by a
+database index, so they may be prefereable over an equivalent simple `filter`
+expression due to better resource usage and performance.
+
+### List Stubs
+
+Some list endpoints return a reduced version of the resource being queried.
+This smaller version is called a _stub_ and may have different fields than the
+full resource definition. To allow more expressive filtering operations, the
+filter is applied to the full version, not the stub.
+
+If a request returns an error such as `error finding value in datum` the field
+used in filter expression may need to be adjusted. For example, filtering on
+node addresses should use the `HTTPAddr` field of the full node definition
+instead of `Address` field present in the stub.
+
+```shell-session
+$ nomad operator api -filter 'HTTPAddr matches "10.0.0..+"' /v1/nodes
+```
+
+### Creating Expressions
+
+A single expression is a matching operator with a selector and value and they
+are written in plain text format. Boolean logic and parenthesization are
+supported. In general, whitespace is ignored, except within literal strings.
+
+#### Matching Operators
+
+All matching operators use a selector or value to choose what data should be
+matched. Each endpoint that supports filtering accepts a potentially
+different list of selectors and is detailed in the API documentation for
+those endpoints.
+
+```hcl
+// Equality & Inequality checks
+<Selector> == "<Value>"
+<Selector> != "<Value>"
+
+// Emptiness checks
+<Selector> is empty
+<Selector> is not empty
+
+// Contains checks or Substring Matching
+"<Value>" in <Selector>
+"<Value>" not in <Selector>
+<Selector> contains "<Value>"
+<Selector> not contains "<Value>"
+
+// Regular Expression Matching
+<Selector> matches "<Value>"
+<Selector> not matches "<Value>"
+```
+
+#### Selectors
+
+Selectors are used by matching operators to create an expression. They are
+defined by a `.` separated list of names. Each name must start with an ASCII
+letter and can contain ASCII letters, numbers, and underscores. When part of
+the selector references a map value it may be expressed using the form
+`["<map key name>"]` instead of `.<map key name>`. This allows the possibility
+of using map keys that are not valid selectors in and of themselves.
+
+```hcl
+// selects the `cache` key within the `TaskGroups` mapping for the
+// /v1/deployments endpoint
+TaskGroups.cache
+
+// Also selects the `cache` key for the same endpoint
+TaskGroups["cache"]
+```
+
+#### Values
+
+Values are used by matching operators to create an expression. Values can be
+any valid selector, a number, or a string. It is best practice to quote values.
+Numbers can be base 10 integers or floating point numbers.
+
+When quoting strings, they may either be enclosed in double quotes or
+backticks. When enclosed in backticks they are treated as raw strings and
+escape sequences such as `\n` will not be expanded.
+
+### Connecting Expressions
+
+There are several methods for connecting expressions, including:
+
+- logical `or`
+- logical `and`
+- logical `not`
+- grouping with parenthesis
+- matching expressions
+
+```hcl
+// Logical Or - evaluates to true if either sub-expression does
+<Expression 1> or <Expression 2>
+
+// Logical And - evaluates to true if both sub-expressions do
+<Expression 1 > and <Expression 2>
+
+// Logical Not - evaluates to true if the sub-expression does not
+not <Expression 1>
+
+// Grouping - Overrides normal precedence rules
+( <Expression 1> )
+
+// Inspects data to check for a match
+<Matching Expression 1>
+```
+
+Standard operator precedence can be expected for the various forms. For
+example, the following two expressions would be equivalent.
+
+```hcl
+<Expression 1> and not <Expression 2> or <Expression 3>
+
+( <Expression 1> and (not <Expression 2> )) or <Expression 3>
+```
+
+### Filter Utilization
+
+Generally, only the main object is filtered. When filtering for an item within
+an array that is not at the top level, the entire array that contains the item
+will be returned. This is usually the outermost object of a response, but in
+some cases the filtering is performed on a object embedded within the results.
+
+#### Performance
+
+Filters are executed on the servers and therefore will consume some amount
+of CPU time on the server. For non-stale queries this means that the filter
+is executed on the leader.
+
+#### Filtering Examples
+
+##### Jobs API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/jobs
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  },
+  {
+    "CreateIndex": 42,
+    "Datacenters": [
+      "dc1"
+    ],
+    "ID": "example",
+    "JobModifyIndex": 42,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 42,
+      "JobID": "example",
+      "ModifyIndex": 46,
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 0,
+          "Running": 1,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 49,
+    "Multiregion": null,
+    "Name": "example",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "running",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230403921889000,
+    "Type": "service"
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Datacenters contains "dc2"' /v1/jobs
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 52,
+    "Datacenters": [
+      "dc1",
+      "dc2"
+    ],
+    "ID": "countdash",
+    "JobModifyIndex": 56,
+    "JobSummary": {
+      "Children": {
+        "Dead": 0,
+        "Pending": 0,
+        "Running": 0
+      },
+      "CreateIndex": 52,
+      "JobID": "countdash",
+      "ModifyIndex": 55,
+      "Namespace": "default",
+      "Summary": {
+        "api": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        },
+        "dashboard": {
+          "Complete": 0,
+          "Failed": 0,
+          "Lost": 0,
+          "Queued": 1,
+          "Running": 0,
+          "Starting": 0
+        }
+      }
+    },
+    "ModifyIndex": 56,
+    "Multiregion": null,
+    "Name": "countdash",
+    "Namespace": "default",
+    "ParameterizedJob": false,
+    "ParentID": "",
+    "Periodic": false,
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "Stop": false,
+    "SubmitTime": 1645230445788556000,
+    "Type": "service"
+  }
+]
+```
+
+##### Deployments API
+
+Command (Unfiltered)
+
+```shell-session
+$ nomad operator api /v1/deployments
+```
+
+Response (Unfiltered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  },
+  {
+    "CreateIndex": 43,
+    "EvalPriority": 50,
+    "ID": "1f18b48c-b33b-8e96-5640-71e3f3000242",
+    "IsMultiregion": false,
+    "JobCreateIndex": 42,
+    "JobID": "example",
+    "JobModifyIndex": 42,
+    "JobSpecModifyIndex": 42,
+    "JobVersion": 0,
+    "ModifyIndex": 49,
+    "Namespace": "default",
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "TaskGroups": {
+      "cache": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 1,
+        "PlacedAllocs": 1,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": "2022-02-18T19:36:54.421823-05:00",
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+Command (Filtered)
+
+```shell-session
+$ nomad operator api -filter 'Status != "successful"' /v1/deployments
+```
+
+Response (Filtered)
+
+```json
+[
+  {
+    "CreateIndex": 54,
+    "EvalPriority": 50,
+    "ID": "58fd0616-ce64-d14b-6917-03d0ab5af67e",
+    "IsMultiregion": false,
+    "JobCreateIndex": 52,
+    "JobID": "countdash",
+    "JobModifyIndex": 52,
+    "JobSpecModifyIndex": 52,
+    "JobVersion": 0,
+    "ModifyIndex": 59,
+    "Namespace": "default",
+    "Status": "cancelled",
+    "StatusDescription": "Cancelled due to newer version of job",
+    "TaskGroups": {
+      "dashboard": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      },
+      "api": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 1,
+        "HealthyAllocs": 0,
+        "PlacedAllocs": 0,
+        "PlacedCanaries": null,
+        "ProgressDeadline": 600000000000,
+        "Promoted": false,
+        "RequireProgressBy": null,
+        "UnhealthyAllocs": 0
+      }
+    }
+  }
+]
+```
+
+## Pagination
+
+Some list endpoints support partial results to limit the amount of data
+retrieved. The returned list is split into pages and the page size can be set
+using the `per_page` query parameter with a positive integer value.
+
+If more data is available past the page requested, the response will contain an
+HTTP header named `X-Nomad-Nexttoken` with the value of the next item to be
+retrieved. This value can then be set as a query parameter called `next_token`
+in a follow-up request to retrieve the next page.
+
+When the last page is reached, the `X-Nomad-Nexttoken` HTTP header will not
+be present in the response, indicating that there is nothing more to return.
+
+## Ordering
+
+List results are usually returned in ascending order by their internal key,
+such as their `ID`. Some endpoints may return data sorted by their
+`CreateIndex` value, which roughly corelates to their creation order. The
+result order may be reversed using the `reverse=true` query parameter when
+supported by the endpoint.
+
+## Blocking Queries
+
+Many endpoints in Nomad support a feature known as "blocking queries". A
+blocking query is used to wait for a potential change using long polling. Not
+all endpoints support blocking, but each endpoint uniquely documents its support
+for blocking queries in the documentation.
+
+Endpoints that support blocking queries return an HTTP header named
+`X-Nomad-Index`. This is a unique identifier representing the current state of
+the requested resource. On a new Nomad cluster the value of this index starts at 1.
+
+On subsequent requests for this resource, the client can set the `index` query
+string parameter to the value of `X-Nomad-Index`, indicating that the client
+wishes to wait for any changes subsequent to that index.
+
+When this is provided, the HTTP request will "hang" until a change in the system
+occurs, or the maximum timeout is reached. A critical note is that the return of
+a blocking request is **no guarantee** of a change. It is possible that the
+timeout was reached or that there was an idempotent write that does not affect
+the result of the query.
+
+In addition to `index`, endpoints that support blocking will also honor a `wait`
+parameter specifying a maximum duration for the blocking request. This is
+limited to 10 minutes. If not set, the wait time defaults to 5 minutes. This
+value can be specified in the form of "10s" or "5m" (i.e., 10 seconds or 5
+minutes, respectively). A small random amount of additional wait time is added
+to the supplied maximum `wait` time to spread out the wake up time of any
+concurrent requests. This adds up to `wait / 16` additional time to the maximum
+duration.
+
+## Consistency Modes
+
+Most of the read query endpoints support multiple levels of consistency. Since
+no policy will suit all clients' needs, these consistency modes allow the user
+to have the ultimate say in how to balance the trade-offs inherent in a
+distributed system.
+
+The two read modes are:
+
+- `default` - If not specified, the default is strongly consistent in almost all
+  cases. However, there is a small window in which a new leader may be elected
+  during which the old leader may service stale values. The trade-off is fast
+  reads but potentially stale values. The condition resulting in stale reads is
+  hard to trigger, and most clients should not need to worry about this case.
+  Also, note that this race condition only applies to reads, not writes.
+
+- `stale` - This mode allows any server to service the read regardless of
+  whether it is the leader. This means reads can be arbitrarily stale; however,
+  results are generally consistent to within 50 milliseconds of the leader. The
+  trade-off is very fast and scalable reads with a higher likelihood of stale
+  values. Since this mode allows reads without a leader, a cluster that is
+  unavailable will still be able to respond to queries.
+
+To switch these modes, use the `stale` query parameter on requests.
+
+To support bounding the acceptable staleness of data, responses provide the
+`X-Nomad-LastContact` header containing the time in milliseconds that a server
+was last contacted by the leader node. The `X-Nomad-KnownLeader` header also
+indicates if there is a known leader. These can be used by clients to gauge the
+staleness of a result and take appropriate action.
+
+## Cross-Region Requests
+
+By default, any request to the HTTP API will default to the region on which the
+machine is servicing the request. If the agent runs in "region1", the request
+will query the region "region1". A target region can be explicitly request using
+the `?region` query parameter. The request will be transparently forwarded and
+serviced by a server in the requested region.
+
+## Compressed Responses
+
+The HTTP API will gzip the response if the HTTP request denotes that the client
+accepts gzip compression. This is achieved by passing the accept encoding:
+
+```shell-session
+$ curl \
+    --header "Accept-Encoding: gzip" \
+    https://localhost:4646/v1/...
+```
+
+## Formatted JSON Output
+
+By default, the output of all HTTP API requests is minimized JSON. If the client
+passes `pretty` on the query string, formatted JSON will be returned.
+
+In general, clients should prefer a client-side parser like `jq` instead of
+server-formatted data. Asking the server to format the data takes away
+processing cycles from more important tasks.
+
+```shell-session
+$ curl https://localhost:4646/v1/page?pretty
+```
+
+## HTTP Methods
+
+Nomad's API aims to be RESTful, although there are some exceptions. The API
+responds to the standard HTTP verbs GET, PUT, and DELETE. Each API method will
+clearly document the verb(s) it responds to and the generated response. The same
+path with different verbs may trigger different behavior. For example:
+
+```text
+PUT /v1/jobs
+GET /v1/jobs
+```
+
+Even though these share a path, the `PUT` operation creates a new job whereas
+the `GET` operation reads all jobs.
+
+## HTTP Response Codes
+
+Individual API's will contain further documentation in the case that more
+specific response codes are returned but all clients should handle the following:
+
+- 200 and 204 as success codes.
+- 400 indicates a validation failure and if a parameter is modified in the
+  request, it could potentially succeed.
+- 403 marks that the client isn't authenticated for the request.
+- 404 indicates an unknown resource.
+- 5xx means that the client should not expect the request to succeed if retried.
+
+[cli_operator_api]: /nomad/docs/commands/operator/api
+[cli_operator_api_filter]: /nomad/docs/commands/operator/api#filter
diff --git a/content/nomad/v1.9.x/content/api-docs/jobs.mdx b/content/nomad/v1.9.x/content/api-docs/jobs.mdx
new file mode 100644
index 0000000000..1b948de60f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/jobs.mdx
@@ -0,0 +1,2843 @@
+---
+layout: api
+page_title: Jobs - HTTP API
+description: The /jobs endpoints are used to query for and interact with jobs.
+---
+
+# Jobs HTTP API
+
+The `/jobs` endpoints are used to query for and interact with jobs.
+
+## List Jobs
+
+This endpoint lists all known jobs in the system registered with Nomad.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `GET`  | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required          |
+| ---------------- | --------------------- |
+| `YES`            | `namespace:list-jobs` |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter jobs on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` would return all jobs across all the authorized namespaces.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a [meta](/nomad/docs/job-specification/meta) field containing key-value pairs provided in the job specification's `meta` block.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?prefix=team
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/jobs?namespace=*&prefix=team
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+## Create Job
+
+This endpoint creates (aka "registers") a new job in the system.
+
+| Method | Path       | Produces           |
+| ------ | ---------- | ------------------ |
+| `POST` | `/v1/jobs` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job registration. By default, this is set to the priority
+  of the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be registered when it would
+  be denied by policy.
+
+- `PreserveCounts` `(bool: false)` - If set, existing task group counts are
+  preserved, over those specified in the new job spec.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    "Datacenters": ["dc1"],
+    "ID": "cache",
+    "NodePool": "prod",
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Networks": [
+          {
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "To": 6379
+              }
+            ]
+          }
+        ],
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "PortLabel": "db"
+          }
+        ],
+        "Tasks": [
+          {
+            "Config": {
+              "image": "redis:7",
+              "ports": ["db"]
+            },
+            "Driver": "docker",
+            "Name": "redis"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "",
+  "EvalCreateIndex": 0,
+  "JobModifyIndex": 109,
+  "Warnings": "",
+  "Index": 0,
+  "LastContact": 0,
+  "KnownLeader": false
+}
+```
+
+## Parse Job
+
+This endpoint will parse a HCL jobspec and produce the equivalent JSON encoded
+job.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `POST` | `/v1/jobs/parse` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                      |
+| ---------------- | ------------------------------------------------- |
+| `NO`             | `namespace:parse-job`<br />`namespace:submit-job` |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to
+  access. This is specified as a query string parameter.
+
+- `JobHCL` `(string: <required>)` - Specifies the HCL definition of the job
+  encoded in a JSON string.
+
+- `Canonicalize` `(bool: false)` - Flag to enable setting any unset fields to
+  their default values.
+
+- `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
+  the job in the var file format.
+
+### Sample Payload
+
+```json
+{
+  "JobHCL": "job \"example\" {\n  type = \"service\"\n  group \"cache\" {}\n}",
+  "Canonicalize": true
+}
+```
+
+You can use a tool such as [`jq`](https://stedolan.github.io/jq/) to generate
+the payload from a local HCL file:
+
+```shell-session
+$ jq -Rsc '{ JobHCL: ., Canonicalize: true }' example.nomad.hcl > payload.json
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/jobs/parse
+```
+
+### Sample Response
+
+```json
+{
+  "AllAtOnce": false,
+  "Constraints": null,
+  "Affinities": null,
+  "CreateIndex": 0,
+  "Datacenters": null,
+  "ID": "my-job",
+  "JobModifyIndex": 0,
+  "Meta": null,
+  "Migrate": null,
+  "ModifyIndex": 0,
+  "Name": "my-job",
+  "Namespace": "default",
+  "NodePool": "prod",
+  "ParameterizedJob": null,
+  "ParentID": "",
+  "Payload": null,
+  "Periodic": null,
+  "Priority": 50,
+  "Region": "global",
+  "Reschedule": null,
+  "Stable": false,
+  "Status": "",
+  "StatusDescription": "",
+  "Stop": false,
+  "SubmitTime": null,
+  "TaskGroups": null,
+  "Type": "service",
+  "Update": null,
+  "VaultToken": "",
+  "Version": 0
+}
+```
+
+## Read Job
+
+This endpoint reads information about a single job for its specification and
+status.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+- `namespace` `(string: "default")` - Specifies the namespace of the job. If not specified,
+  defaults to "default". This is specified as a URL query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job?namespace=apps
+```
+
+### Sample Response
+
+```json
+{
+  "Region": "global",
+  "Namespace": "apps",
+  "ID": "example",
+  "ParentID": "",
+  "Name": "example",
+  "Type": "batch",
+  "Priority": 50,
+  "AllAtOnce": false,
+  "Datacenters": ["dc1"],
+  "NodePool": "prod",
+  "Constraints": [
+    {
+      "LTarget": "${attr.kernel.name}",
+      "RTarget": "linux",
+      "Operand": "="
+    }
+  ],
+  "TaskGroups": [
+    {
+      "Name": "cache",
+      "Count": 1,
+      "Constraints": [
+        {
+          "LTarget": "${attr.os.signals}",
+          "RTarget": "SIGUSR1",
+          "Operand": "set_contains"
+        }
+      ],
+      "Affinities": [
+        {
+          "LTarget": "${meta.datacenter}",
+          "RTarget": "dc1",
+          "Operand": "=",
+          "Weight": 50
+        }
+      ],
+      "RestartPolicy": {
+        "Attempts": 10,
+        "Interval": 300000000000,
+        "Delay": 25000000000,
+        "Mode": "delay"
+      },
+      "Tasks": [
+        {
+          "Config": {
+            "command": "env",
+            "image": "alpine"
+          },
+          "Driver": "docker",
+          "Lifecycle": {
+            "Hook": "prestart",
+            "Sidecar": false
+          },
+          "Name": "init",
+          "Resources": {
+            "CPU": 100,
+            "MemoryMB": 300
+          }
+        },
+        {
+          "Name": "redis",
+          "Driver": "docker",
+          "User": "foo-user",
+          "Config": {
+            "image": "redis:latest",
+            "port_map": [
+              {
+                "db": 6379
+              }
+            ]
+          },
+          "Env": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "Services": [
+            {
+              "Name": "cache-redis",
+              "PortLabel": "db",
+              "Tags": ["global", "cache"],
+              "Checks": [
+                {
+                  "Name": "alive",
+                  "Type": "tcp",
+                  "Command": "",
+                  "Args": null,
+                  "Path": "",
+                  "Protocol": "",
+                  "PortLabel": "",
+                  "Interval": 10000000000,
+                  "Timeout": 2000000000,
+                  "InitialStatus": ""
+                }
+              ]
+            }
+          ],
+          "Vault": null,
+          "Templates": [
+            {
+              "SourcePath": "local/config.conf.tpl",
+              "DestPath": "local/config.conf",
+              "EmbeddedTmpl": "",
+              "ChangeMode": "signal",
+              "ChangeSignal": "SIGUSR1",
+              "Splay": 5000000000,
+              "Perms": ""
+            }
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Resources": {
+            "CPU": 500,
+            "MemoryMB": 256,
+            "DiskMB": 0,
+            "Networks": [
+              {
+                "Device": "",
+                "CIDR": "",
+                "IP": "",
+                "MBits": 10,
+                "ReservedPorts": [
+                  {
+                    "Label": "rpc",
+                    "Value": 25566
+                  }
+                ],
+                "DynamicPorts": [
+                  {
+                    "Label": "db",
+                    "Value": 0
+                  }
+                ]
+              }
+            ]
+          },
+          "DispatchPayload": {
+            "File": "config.json"
+          },
+          "Meta": {
+            "foo": "bar",
+            "baz": "pipe"
+          },
+          "KillTimeout": 5000000000,
+          "LogConfig": {
+            "Disabled": false,
+            "MaxFiles": 10,
+            "MaxFileSizeMB": 10
+          },
+          "Artifacts": [
+            {
+              "GetterSource": "http://foo.com/artifact.tar.gz",
+              "GetterOptions": {
+                "checksum": "md5:c4aa853ad2215426eb7d70a21922e794"
+              },
+              "RelativeDest": "local/"
+            }
+          ],
+          "Leader": false
+        }
+      ],
+      "EphemeralDisk": {
+        "Sticky": false,
+        "SizeMB": 300,
+        "Migrate": false
+      },
+      "Meta": {
+        "foo": "bar",
+        "baz": "pipe"
+      }
+    }
+  ],
+  "Update": {
+    "Stagger": 10000000000,
+    "MaxParallel": 1
+  },
+  "Periodic": {
+    "Enabled": true,
+    "Spec": "* * * * *",
+    "SpecType": "cron",
+    "ProhibitOverlap": true
+  },
+  "ParameterizedJob": {
+    "Payload": "required",
+    "MetaRequired": ["foo"],
+    "MetaOptional": ["bar"]
+  },
+  "Payload": null,
+  "Meta": {
+    "foo": "bar",
+    "baz": "pipe"
+  },
+  "VaultToken": "",
+  "Status": "running",
+  "StatusDescription": "",
+  "CreateIndex": 7,
+  "ModifyIndex": 7,
+  "JobModifyIndex": 7
+}
+```
+
+#### Field Reference
+
+- `Status`: The job's current state. It can have one of the following values:
+  - `pending`: The job is currently waiting on scheduling.
+  - `running`: The job has non-terminal allocations.
+  - `dead`: All of the job's allocations and evaluations are terminal.
+- `Type`: The type of job in terms of scheduling. It can have one of the following values:
+  - `service`: Allocations are intended to remain alive.
+  - `batch`: Allocations are intended to exit.
+  - `system`: Each client in the datacenter and node pool gets an allocation.
+
+## Read Job Submission
+
+This endpoint reads original source information about a specific version of a single
+job. The data this endpoint provides is only available if it was provided with the
+original job during job registration. Only the most recent 6 job source files are
+retained.
+
+| Method | Path                           | Produces           |
+| ------ | ------------------------------ | ------------------ |
+|`GET`   | `/v1/job/:job_id/submission`   | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+   specified as part of the path.
+- `version` `(int: <required>)` - Specifies the version number of the job for which
+  to retrieve the original source information. This is specified as a query string
+  parameter.
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+  enabled, this value must match a namespace that the token is allowed to access.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+nomad operator api /v1/job/my-job/submission?version=42
+```
+
+### Sample Response
+
+```json
+{
+  "Format": "hcl2",
+  "JobIndex": 11,
+  "JobID": "myjob",
+  "Namespace": "default",
+  "Source": "variable \"X\" {\n  type = string\n}\n\nvariable \"Y\" {\n  type = number\n}\n\nvariable \"Z\" {\n  type = bool\n}\n  \njob \"myjob\" {\n  type = \"sysbatch\"\n  \n  meta {\n    nomad_discard_job_source = false\n  }\n\n  group \"group\" {\n    task \"task\" {\n      driver = \"raw_exec\"\n\n      config {\n        command = \"echo\"\n        args = [\"X ${var.X}, Y ${var.Y}, Z ${var.Z}\"]\n      }\n\n      resources {\n        cpu    = 10\n        memory = 16\n      }\n    }\n  }\n}\n",
+  "VariableFlags": {
+    "Z": "true",
+    "X": "x",
+    "Y": "2"
+  },
+  "Variables": "",
+  "Version": 0
+}
+```
+
+#### Field Reference
+
+- `JobID`: The ID of the job associated with the original job file.
+- `Format`: The file format of the original job file. One of `hcl2` or `json`.
+- `Source`: The literal content of the original job file.
+- `VariableFlags`: The key-value pairs of HCL variables as submitted via `-var` command
+  line arguments when submitting the job via CLI.
+- `Variables`: The content of the variables form when submitting the job via the WebUI.
+- `Version`: The version of the job this submission source is associated with.
+
+## List Job Versions
+
+This endpoint reads information about all versions of a job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/versions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `diffs` `(bool: false)` - Specifies if the Diffs field should be populated,
+  containing the structured diff between the current and last job version. This
+  is specified as a query string parameter.
+
+- `diff_version` `(int: <optional>)`: Specifies the version to to compare against the current version when you create the structured diff for a job with `diffs=true`. This is specified as a query string parameter.
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions
+```
+
+### Sample Response
+
+```json
+{
+  "Diffs": null,
+  "Index": 51,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 44,
+      "Datacenters": ["dc1"],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 44,
+      "Meta": null,
+      "ModifyIndex": 51,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NomadTokenID": "",
+      "NodePool": "prod",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608304897537638400,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": 300000000000,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": ["db"]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/versions?diffs=true
+```
+
+```json
+{
+  "Diffs": [
+    {
+      "Fields": null,
+      "ID": "example",
+      "Objects": null,
+      "TaskGroups": [
+        {
+          "Fields": null,
+          "Name": "cache",
+          "Objects": null,
+          "Tasks": [
+            {
+              "Annotations": null,
+              "Fields": [
+                {
+                  "Annotations": null,
+                  "Name": "Env[foo]",
+                  "New": "bar",
+                  "Old": "",
+                  "Type": "Added"
+                }
+              ],
+              "Name": "redis",
+              "Objects": null,
+              "Type": "Edited"
+            }
+          ],
+          "Type": "Edited",
+          "Updates": null
+        }
+      ],
+      "Type": "Edited"
+    }
+  ],
+  "Index": 26,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Versions": [
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 16,
+      "Meta": null,
+      "ModifyIndex": 26,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": true,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316675000588800,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": {
+                "foo": "bar"
+              },
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 1
+    },
+    {
+      "Affinities": null,
+      "AllAtOnce": false,
+      "Constraints": null,
+      "ConsulToken": "",
+      "CreateIndex": 10,
+      "Datacenters": [
+        "dc1"
+      ],
+      "Dispatched": false,
+      "ID": "example",
+      "JobModifyIndex": 10,
+      "Meta": null,
+      "ModifyIndex": 10,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "prod",
+      "NomadTokenID": "",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Spreads": null,
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1608316662268190500,
+      "TaskGroups": [
+        {
+          "Affinities": null,
+          "Constraints": null,
+          "Count": 1,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "MaxClientDisconnect": null,
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000
+          },
+          "Name": "cache",
+          "Networks": [
+            {
+              "CIDR": "",
+              "DNS": null,
+              "Device": "",
+              "DynamicPorts": [
+                {
+                  "HostNetwork": "default",
+                  "Label": "db",
+                  "To": 6379,
+                  "Value": 0
+                }
+              ],
+              "IP": "",
+              "MBits": 0,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Scaling": null,
+          "Services": null,
+          "ShutdownDelay": null,
+          "Spreads": null,
+          "StopAfterClientDisconnect": null,
+          "Tasks": [
+            {
+              "Affinities": null,
+              "Artifacts": null,
+              "CSIPluginConfig": null,
+              "Config": {
+                "image": "redis:7",
+                "ports": [
+                  "db"
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Kind": "",
+              "Leader": false,
+              "Lifecycle": null,
+              "LogConfig": {
+                "Disabled": false,
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "redis",
+              "Resources": {
+                "CPU": 500,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 256,
+                "Networks": null
+              },
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Delay": 15000000000,
+                "Interval": 1800000000000,
+                "Mode": "fail"
+              },
+              "ScalingPolicies": null,
+              "Services": null,
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null,
+              "VolumeMounts": null
+            }
+          ],
+          "Update": {
+            "AutoPromote": false,
+            "AutoRevert": false,
+            "Canary": 0,
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 1,
+            "MinHealthyTime": 10000000000,
+            "ProgressDeadline": 600000000000,
+            "Stagger": 30000000000
+          },
+          "Volumes": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoPromote": false,
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 1,
+        "MinHealthyTime": 0,
+        "ProgressDeadline": 0,
+        "Stagger": 30000000000
+      },
+      "VaultNamespace": "",
+      "VaultToken": "",
+      "Version": 0
+    }
+  ]
+}
+```
+
+## List Job Allocations
+
+This endpoint reads information about a single job's allocations.
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of allocations should
+  include allocations from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "ed344e0a-7290-d117-41d3-a64f853ca3c2",
+    "EvalID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Name": "example.cache[0]",
+    "NodeID": "cb1f6030-a220-4f92-57dc-7baaabdc3823",
+    "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+    "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+    "RescheduleTracker": {
+      "Events": [
+        {
+          "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+          "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+          "RescheduleTime": 1517434161192946200,
+          "Delay": 5000000000
+        }
+      ]
+    },
+    "JobID": "example",
+    "TaskGroup": "cache",
+    "DesiredStatus": "run",
+    "DesiredDescription": "",
+    "ClientStatus": "running",
+    "ClientDescription": "",
+    "TaskStates": {
+      "redis": {
+        "State": "running",
+        "Failed": false,
+        "StartedAt": "2017-05-25T23:41:23.240184101Z",
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "Events": [
+          {
+            "Type": "Received",
+            "Time": 1495755675956923000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Task Setup",
+            "Time": 1495755675957466400,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "Building Task Directory",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          },
+          {
+            "Type": "Driver",
+            "Time": 1495755675970286800,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": "Downloading image redis:7"
+          },
+          {
+            "Type": "Started",
+            "Time": 1495755683227522000,
+            "FailsTask": false,
+            "RestartReason": "",
+            "SetupError": "",
+            "DriverError": "",
+            "ExitCode": 0,
+            "Signal": 0,
+            "Message": "",
+            "KillTimeout": 0,
+            "KillError": "",
+            "KillReason": "",
+            "StartDelay": 0,
+            "DownloadError": "",
+            "ValidationError": "",
+            "DiskLimit": 0,
+            "FailedSibling": "",
+            "VaultError": "",
+            "TaskSignalReason": "",
+            "TaskSignal": "",
+            "DriverMessage": ""
+          }
+        ]
+      }
+    },
+    "CreateIndex": 9,
+    "ModifyIndex": 13,
+    "CreateTime": 1495755675944527600,
+    "ModifyTime": 1495755675944527600
+  }
+]
+```
+
+## List Job Evaluations
+
+This endpoint reads information about a single job's evaluations
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/evaluations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/evaluations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "a9c5effc-2242-51b2-f1fe-054ee11ab189",
+    "Priority": 50,
+    "Type": "service",
+    "TriggeredBy": "job-register",
+    "JobID": "example",
+    "JobModifyIndex": 7,
+    "NodeID": "",
+    "NodeModifyIndex": 0,
+    "Status": "complete",
+    "StatusDescription": "",
+    "Wait": 0,
+    "NextEval": "",
+    "PreviousEval": "",
+    "BlockedEval": "",
+    "FailedTGAllocs": null,
+    "ClassEligibility": null,
+    "EscapedComputedClass": false,
+    "AnnotatePlan": false,
+    "QueuedAllocations": {
+      "cache": 0
+    },
+    "SnapshotIndex": 8,
+    "CreateIndex": 8,
+    "ModifyIndex": 10
+  }
+]
+```
+
+## List Job Deployments
+
+This endpoint lists a single job's deployments
+
+| Method | Path                          | Produces           |
+| ------ | ----------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployments` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `all` `(bool: false)` - Specifies whether the list of deployments should
+  include deployments from a previously registered job with the same ID. This is
+  possible if the job is deregistered and re-registered.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployments
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+    "JobID": "my-job",
+    "JobVersion": 1,
+    "JobModifyIndex": 19,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": [
+          "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+          "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+        ],
+        "DesiredCanaries": 2,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 2,
+        "HealthyAllocs": 2,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "running",
+    "StatusDescription": "Deployment is running",
+    "CreateIndex": 21,
+    "ModifyIndex": 25
+  },
+  {
+    "ID": "fb6070fb-4a44-e255-4e6f-8213eba3871a",
+    "JobID": "my-job",
+    "JobVersion": 0,
+    "JobModifyIndex": 7,
+    "JobCreateIndex": 7,
+    "TaskGroups": {
+      "cache": {
+        "AutoRevert": true,
+        "Promoted": false,
+        "PlacedCanaries": null,
+        "DesiredCanaries": 0,
+        "DesiredTotal": 3,
+        "PlacedAllocs": 3,
+        "HealthyAllocs": 3,
+        "UnhealthyAllocs": 0
+      }
+    },
+    "Status": "successful",
+    "StatusDescription": "Deployment completed successfully",
+    "CreateIndex": 9,
+    "ModifyIndex": 17
+  }
+]
+```
+
+## Read Job's Most Recent Deployment
+
+This endpoint returns a single job's most recent deployment.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/deployment` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/deployment
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "85ee4a9a-339f-a921-a9ef-0550d20b2c61",
+  "JobID": "my-job",
+  "JobVersion": 1,
+  "JobModifyIndex": 19,
+  "JobCreateIndex": 7,
+  "TaskGroups": {
+    "cache": {
+      "AutoRevert": true,
+      "Promoted": false,
+      "PlacedCanaries": [
+        "d0ad0808-2765-abf6-1e15-79fb7fe5a416",
+        "38c70cd8-81f2-1489-a328-87bb29ec0e0f"
+      ],
+      "DesiredCanaries": 2,
+      "DesiredTotal": 3,
+      "PlacedAllocs": 2,
+      "HealthyAllocs": 2,
+      "UnhealthyAllocs": 0
+    }
+  },
+  "Status": "running",
+  "StatusDescription": "Deployment is running",
+  "CreateIndex": 21,
+  "ModifyIndex": 25
+}
+```
+
+## Read Job Summary
+
+This endpoint reads summary information about a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/summary` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/summary
+```
+
+### Sample Response
+
+```json
+{
+  "JobID": "example",
+  "Summary": {
+    "cache": {
+      "Queued": 0,
+      "Complete": 0,
+      "Failed": 0,
+      "Running": 1,
+      "Starting": 0,
+      "Lost": 0
+    }
+  },
+  "Children": {
+    "Pending": 0,
+    "Running": 0,
+    "Dead": 0
+  },
+  "CreateIndex": 7,
+  "ModifyIndex": 13
+}
+```
+
+## Update Existing Job
+
+This endpoint registers a new job or updates an existing job.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(Job: <required>)` - Specifies the JSON definition of the job.
+
+- `Submission` `(JobSubmission: <optional>)` - Specifies the original HCL/HCL2/JSON
+  definition of the job. This data is useful for reference only, it is not considered
+  for the actual scheduling of `Job`.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if the
+  passed `JobModifyIndex` matches the current job's index. If the index is zero,
+  the register only occurs if the job is new. This paradigm allows check-and-set
+  style job updating.
+
+- `EvalPriority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job update. By default, this is set to the priority of
+  the job.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```javascript
+{
+  "Job": {
+    // ...
+  },
+  "EnforceIndex": true,
+  "JobModifyIndex": 4
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Dispatch Job
+
+This endpoint dispatches a new instance of a parameterized job.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `idempotency_token` `(string: "")` - Optional identifier used to prevent more
+  than one instance of the job from being dispatched. This is specified as a
+  URL query parameter.
+
+- `IdPrefixTemplate` `(string: "")` - Optional prefix added to dispatched job
+  IDs.
+
+- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
+  payload. This is limited to 16384 bytes (16KiB).
+
+- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
+  the job.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Payload": "A28C3==",
+  "Meta": {
+    "key": "Value"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "JobCreateIndex": 12,
+  "EvalCreateIndex": 13,
+  "EvalID": "e5f55fac-bc69-119d-528a-1fc7ade5e02c",
+  "DispatchedJobID": "example/dispatch-1485408778-81644024"
+}
+```
+
+## Dispatch Job with raw Payload body
+
+This endpoint dispatches a new instance of a parameterized job using the full
+request body as the `Payload` as described in [Dispatch Job](#dispatch-job).
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/dispatch/payload` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required             |
+| ---------------- | ------------------------ |
+| `NO`             | `namespace:dispatch-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+specified as part of the path.
+
+### Sample Payload
+
+```
+any HTTP request body, JSON or otherwise, becomes the dispatch Payload
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data 'anything at all' \
+    https://localhost:4646/v1/job/my-job/dispatch
+```
+
+### Sample Response
+
+```json
+{
+  "DispatchedJobID": "param/dispatch-1730920906-81821d1f",
+  "EvalCreateIndex": 179,
+  "EvalID": "5e973383-8d59-3f33-4496-72112a882605",
+  "Index": 179,
+  "JobCreateIndex": 178
+}
+```
+
+## Revert to older Job Version
+
+This endpoint reverts the job to an older version.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/revert` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to revert to. Use either 
+  this parameter or `TaggedVersion`, but do not use both.
+
+- `TaggedVersion` `(string: "")` - Specifies the tag name of the job version you
+  want to revert to. Use either this parameter or `JobVersion`, but do not use both.
+
+- `EnforcePriorVersion` `(integer: nil)` - Optional value specifying the current
+  job's version. This is checked and acts as a check-and-set value before
+  reverting to the specified job.
+
+- `ConsulToken` `(string:"")` - Optional value specifying the [consul token](/nomad/docs/commands/job/revert)
+  used for Consul [service identity polity authentication checking](/nomad/docs/configuration/consul#allow_unauthenticated).
+
+- `VaultToken` `(string: "")` - Optional value specifying the [vault token](/nomad/docs/commands/job/revert)
+  used for Vault [policy authentication checking](/nomad/docs/configuration/vault#allow_unauthenticated).
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+This example specifies the version.
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2
+}
+```
+
+This example specifies the tagged version.
+
+```json
+{
+  "JobID": "my-job",
+  "TaggedVersion": "golden-version"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/revert
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Set Job Stability
+
+This endpoint sets the job's stability.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `POST` | `/v1/job/:job_id/stable` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `JobID` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobVersion` `(integer: 0)` - Specifies the job version to set the stability on.
+
+- `Stable` `(bool: false)` - Specifies whether the job should be marked as
+  stable or not.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "JobVersion": 2,
+  "Stable": true
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/stable
+```
+
+### Sample Response
+
+```json
+{
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Evaluation
+
+This endpoint creates a new evaluation for the given job. This can be used to
+force run the scheduling logic if necessary. Since Nomad 0.8.4, this endpoint
+supports a JSON payload with additional options. Support for calling this end point
+without a JSON payload will be removed in Nomad 0.9.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `JobID` `(string: <required>)` - Specify the ID of the job in the JSON payload
+
+- `EvalOptions` `(<optional>)` - Specify additional options to be used during the forced evaluation.
+  - `ForceReschedule` `(bool: false)` - If set, failed allocations of the job are rescheduled
+    immediately. This is useful for operators to force immediate placement even if the failed allocations are past
+    their rescheduling limit, or are delayed by several hours because the allocation's reschedule policy has exponential delay.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "JobID": "my-job",
+  "EvalOptions": {
+    "ForceReschedule": true
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    -d @sample.json \
+    https://localhost:4646/v1/job/my-job/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Create Job Plan
+
+This endpoint invokes a dry-run of the scheduler for the job.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/plan` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Job` `(string: <required>)` - Specifies the JSON definition of the job.
+
+- `Diff` `(bool: false)` - Specifies whether the diff structure between the
+  submitted and server side version of the job should be included in the
+  response.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a job to be registered when it would be denied
+  by policy.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Payload
+
+```json
+{
+  "Job": {
+    // ...
+  },
+  "Diff": true,
+  "PolicyOverride": false
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/my-job/plan
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "NextPeriodicLaunch": "0001-01-01T00:00:00Z",
+  "Warnings": "",
+  "Diff": {
+    "Type": "Added",
+    "TaskGroups": [
+      {
+        "Updates": {
+          "create": 1
+        },
+        "Type": "Added",
+        "Tasks": [
+          {
+            "Type": "Added",
+            "Objects": ["..."],
+            "Name": "redis",
+            "Fields": [
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "docker",
+                "Name": "Driver",
+                "Annotations": null
+              },
+              {
+                "Type": "Added",
+                "Old": "",
+                "New": "5000000000",
+                "Name": "KillTimeout",
+                "Annotations": null
+              }
+            ],
+            "Annotations": ["forces create"]
+          }
+        ],
+        "Objects": ["..."],
+        "Name": "cache",
+        "Fields": ["..."]
+      }
+    ],
+    "Objects": [
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Datacenters",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Constraint",
+        "Fields": ["..."]
+      },
+      {
+        "Type": "Added",
+        "Objects": null,
+        "Name": "Update",
+        "Fields": ["..."]
+      }
+    ],
+    "ID": "example",
+    "Fields": ["..."]
+  },
+  "CreatedEvals": [
+    {
+      "ModifyIndex": 0,
+      "CreateIndex": 0,
+      "SnapshotIndex": 0,
+      "AnnotatePlan": false,
+      "EscapedComputedClass": false,
+      "NodeModifyIndex": 0,
+      "NodeID": "",
+      "JobModifyIndex": 0,
+      "JobID": "example",
+      "TriggeredBy": "job-register",
+      "Type": "batch",
+      "Priority": 50,
+      "ID": "312e6a6d-8d01-0daf-9105-14919a66dba3",
+      "Status": "blocked",
+      "StatusDescription": "created to place remaining allocations",
+      "Wait": 0,
+      "NextEval": "",
+      "PreviousEval": "80318ae4-7eda-e570-e59d-bc11df134817",
+      "BlockedEval": "",
+      "FailedTGAllocs": null,
+      "ClassEligibility": {
+        "v1:7968290453076422024": true
+      }
+    }
+  ],
+  "JobModifyIndex": 0,
+  "FailedTGAllocs": {
+    "cache": {
+      "CoalescedFailures": 3,
+      "AllocationTime": 46415,
+      "Scores": null,
+      "NodesEvaluated": 1,
+      "NodesFiltered": 0,
+      "NodesAvailable": {
+        "dc1": 1
+      },
+      "NodesInPool": 1,
+      "ClassFiltered": null,
+      "ConstraintFiltered": null,
+      "NodesExhausted": 1,
+      "ClassExhausted": null,
+      "DimensionExhausted": {
+        "cpu": 1
+      }
+    }
+  },
+  "Annotations": {
+    "DesiredTGUpdates": {
+      "cache": {
+        "DestructiveUpdate": 0,
+        "InPlaceUpdate": 0,
+        "Stop": 0,
+        "Migrate": 0,
+        "Place": 11,
+        "Ignore": 0
+      }
+    }
+  }
+}
+```
+
+#### Field Reference
+
+- `Diff` - A diff structure between the submitted job and the server side
+  version. The top-level object is a Job Diff which contains Task Group Diffs,
+  which in turn contain Task Diffs. Each of these objects then has Object and
+  Field Diff structures embedded.
+
+- `NextPeriodicLaunch` - If the job being planned is periodic, this field will
+  include the next launch time for the job.
+
+- `CreatedEvals` - A set of evaluations that were created as a result of the
+  dry-run. These evaluations can signify a follow-up rolling update evaluation
+  or a blocked evaluation.
+
+- `JobModifyIndex` - The `JobModifyIndex` of the server side version of this job.
+
+- `FailedTGAllocs` - A set of metrics to understand any allocation failures that
+  occurred for the Task Group.
+
+- `Annotations` - Annotations include the `DesiredTGUpdates`, which tracks what
+- the scheduler would do given enough resources for each Task Group.
+
+## Force New Periodic Instance
+
+This endpoint forces a new instance of the periodic job. A new instance will be
+created even if it violates the job's
+[`prohibit_overlap`](/nomad/docs/job-specification/periodic#prohibit_overlap)
+settings. As such, this should be only used to immediately run a periodic job.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/periodic/force` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                       |
+| ---------------- | -------------------------------------------------- |
+| `NO`             | `namespace:dispatch-job` or `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    https://localhost:4646/v1/job/my-job/periodic/force
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 7,
+  "EvalID": "57983ddd-7fcf-3e3a-fd24-f699ccfb36f4"
+}
+```
+
+## Stop a Job
+
+This endpoint deregisters a job, and stops all allocations part of it.
+
+| Method   | Path              | Produces           |
+| -------- | ----------------- | ------------------ |
+| `DELETE` | `/v1/job/:job_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `eval_priority` `(int: 0)` - Override the priority of the evaluations produced
+  as a result of this job deregistration. By default, this is set to the priority
+  of the job.
+
+- `global` `(bool: false)` - Stop a multi-region job in all its regions. By default,
+  job stop will stop only a single region at a time. Ignored for single-region jobs.
+
+- `purge` `(bool: false)` - Specifies that the job should be stopped and purged
+  immediately. This means the job will not be queryable after being stopped. If
+  not set, the job will be purged by the garbage collector.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+- `no_shutdown_delay` `(bool: false)` - Ignore the group and task `shutdown_delay`
+  configuration so that there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network connections
+  to the allocations being stopped.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/job/my-job?purge=true
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID": "d092fdc0-e1fd-2536-67d8-43af8ca798ac",
+  "EvalCreateIndex": 35,
+  "JobModifyIndex": 34
+}
+```
+
+## Read Job Scale Status
+
+This endpoint reads scale information about a job.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                         |
+| ---------------- | ---------------------------------------------------- |
+| `YES`            | `namespace:read-job-scaling` or `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+enabled, this value must match a namespace that the token is allowed to
+access. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/my-job/scale
+```
+
+### Sample Response
+
+```json
+{
+  "JobCreateIndex": 10,
+  "JobID": "example",
+  "Namespace": "default",
+  "JobModifyIndex": 18,
+  "JobStopped": false,
+  "TaskGroups": {
+    "cache": {
+      "Desired": 1,
+      "Events": null,
+      "Healthy": 1,
+      "Placed": 1,
+      "Running": 0,
+      "Unhealthy": 0
+    }
+  }
+}
+```
+
+## Scale Task Group
+
+This endpoint performs a scaling action against a job.
+Currently, this endpoint supports scaling the count for a task group.
+This will return a 400 error if the job has an active deployment.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `POST` | `/v1/job/:job_id/scale` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:scale-job` or `namespace:submit-job`<br />`namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `Count` `(int: <optional>)` - Specifies the new task group count.
+
+- `EnforceIndex` `(bool: false)` - If set, the job will only be registered if
+  the passed `JobModifyIndex` matches the current job's index. If the index is
+  zero, the register only occurs if the job is new. This paradigm allows
+  check-and-set style job updating.
+
+- `Error` `(string: <optional>)` - Description of the scale action, persisted as
+  part of the scaling event.  Indicates an error state preventing scaling; one
+  of `Message` or `Error` must be provided.
+
+- `JobModifyIndex` `(int: 0)` - Specifies the `JobModifyIndex` to enforce the
+  current job is at.
+
+- `Message` `(string: <optional>)` - Description of the scale action, persisted
+  as part of the scaling event.  Indicates information or reason for scaling;
+  one of `Message` or `Error` must be provided.
+
+- `Meta` `(json: <optional>)` - JSON block that is persisted as part of the scaling event.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. If ACL is
+   enabled, this value must match a namespace that the token is allowed to
+   access. This is specified as a query string parameter.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel
+  policies will be overridden. This allows a job to be scaled when it would be
+  denied by policy.
+
+- `Target` `(json: required)` - JSON map containing the target of the scaling
+  operation.  Must contain a field `Group` with the name of the task group that
+  is the target of this scaling action.
+
+### Sample Payload
+
+```javascript
+{
+    "Count": 5,
+    "Meta": {
+        "metrics": [
+            "cpu",
+            "memory"
+        ]
+    },
+    "Message": "metric did not satisfy SLA",
+    "Target": {
+        "Group": "cache"
+    }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/job/example/scale
+```
+
+### Sample Response
+
+This is the same payload as returned by job update.
+`EvalCreateIndex` and `EvalID` will only be present if the scaling operation resulted in the creation of an evaluation.
+
+```json
+{
+  "EvalCreateIndex": 45,
+  "EvalID": "116f3ede-f6a5-f6e7-2d0e-1fda136390f0",
+  "Index": 45,
+  "JobModifyIndex": 44,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "Warnings": ""
+}
+```
+
+## Job Services
+
+The endpoint is used to read all services registered within Nomad belonging to the passed job ID.
+
+| Method | Path                    | Produces           |
+| ------ | ----------------------- | ------------------ |
+| `GET`  | `/job/:job_id/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/job/example/services
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## List Job Actions
+
+This endpoint lists the actions available to tasks within a job.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `GET`  | `/v1/job/:job_id/actions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/job/my-job/actions'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Args": [
+      "-s",
+      "wttr.in/Toronto?format=3"
+    ],
+    "Command": "/usr/bin/curl",
+    "Name": "weather",
+    "TaskGroupName": "group1",
+    "TaskName": "task"
+  },
+  {
+    "Args": [
+      "-c",
+      "nomad alloc status ${NOMAD_ALLOC_ID}"
+    ],
+    "Command": "/bin/sh",
+    "Name": "get-alloc-info",
+    "TaskGroupName": "group2",
+    "TaskName": "task"
+  },
+]
+```
+
+## Run Action
+
+This endpoint executes a predefined action from a job in the
+context of a specific task within an allocation. It opens a WebSocket to
+transmit output from the running action.
+
+
+| Method      | Path                     | Produces               |
+| ----------- | ------------------------ | ---------------------- |
+| `WebSocket` | `/v1/job/:job_id/action` | WebSocket JSON streams |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                                 |
+| ---------------- | -------------------------------------------------------------------------------------------- |
+| `NO`             | `namespace:alloc-exec` (and `namespace:alloc-node-exec` if task driver does not support [file system isolation](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error)) |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - Specifies the ID of the job containing the
+  action. This is specified as part of the path.
+- `action` `(string: <required>)` - Specifies the name of the action to be
+  executed, as defined within the job's task. Specified as a query parameter.
+- `alloc_id` `(string: <required>)` - Specifies the UUID of the target
+  allocation. Specified as a query parameter.
+- `task` `(string: <required>)` - Specifies the task where the action is
+  defined. Specified as a query parameter.
+- `tty` `(bool: false)` - Specifies whether a TTY is allocated for this action.
+  Specified as a query parameter.
+- `ws_handshake` `(bool: false)` - Specifies whether to expect the
+  authentication token in the first frame, as a query parameter.
+
+### WebSocket Upgrade Request
+
+Actions are executed with a WebSocket upgrade request. The request headers
+must include the standard WebSocket upgrade parameters. Example:
+
+```shell-session
+$ curl \
+  -X GET \
+  -H 'Connection: Upgrade' \
+  -H 'Upgrade: websocket' \
+  -H 'Sec-Websocket-Version: 13' \
+  -H 'Sec-Websocket-Key: x3JJHMbDL1EzLkh9GBhXDw==' \
+  'http://127.0.0.1:4646/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+or
+```shell-session
+$ nomad operator api \
+-H "Connection: Upgrade" \
+-H "Upgrade: websocket" \
+-H "Sec-WebSocket-Version: 13" \
+-H "Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==" \
+'/v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true'
+```
+
+### Request Frames
+
+Unlike [alloc exec](/nomad/api-docs/allocations#exec-allocation), Actions do
+not take input in the form of request frames using `stdin`. Instead, the name
+of the action is passed as a query parameter and the associated input is handled
+on the allocation apart from the stream.
+
+When `?ws_handshake=true`, the first request frame must contain the
+authentication token. Similarly, when `?tty=true`, a `tty_size` frame may be
+provided to indicate a resize.
+
+The following are valid input frames:
+
+```
+# sending authentication token
+{"version":1,"auth_token":"fc3c1968-8d31-5c50-9617-3db2e19ef32e"}
+
+# indicating that TTY was resized
+{"tty_size": {"height": <characters>, "width": <characters>}}
+```
+
+### Response Frames
+
+Response frames represent `stdout` and `stderr` output from the command as well
+as exit codes. Response frames encompass the full range of terminal emulator outputs, including
+the control characters necessary to render interactive applications.
+
+```
+# transferring stdout data
+{"stdout": {"data": "...base64 encoded string of bytes ..."}}
+
+# signaling that host closed stdout
+{"stdout": {"close": true}}
+{"exited":true,"result":{}}
+```
+
+The stdout data returned in the response frames from the job action endpoint is
+base64 encoded. This encoding is necessary to ensure that the data can be
+transmitted over WebSocket connections without issues, regardless of its content.
+
+### Sample Request and Response
+
+This example response includes instances of the ANSI "control sequence
+introducer" (CSI), which is ASCII code 27 followed by `[`. The second stdout
+frame includes the desired output from the Action in question, which prints
+the local weather.
+
+```
+# Sample WebSocket request to execute an action
+WebSocket Request: /v1/job/actions-demo/action?action=weather&allocID=8614ed07-425f-889f-170d-dd2716e0e01f&task=task&tty=true
+
+# "\x1b[H\x1b[2J$ ":
+# CSI-H (move cursor to top left corner), CSI-2J (clear entire screen), print "$ "
+{"stdout":{"data":"G1tIG1sySiQg"}}
+
+# Toronto: ⛅️  -1°C
+{"stdout":{"data":"VG9yb250bzog4puF77iPICAtMcKwQw0K"}}
+```
+
+## Create Job Version Tag
+
+This endpoint creates a tag for a job version.
+
+@include 'version/tag-reason.mdx'
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `POST`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part
+  of the path.
+- `:tag_name` `(string: <required>)` - The new tag name for the
+  version specified in the payload. Must be unique per job. Specify `tag_name` as part of the path.
+- `Version`: `(int: <optional>)` - The job version number. If not
+  specified, Nomad tags the latest version. Specify `Version` in the payload.
+- `Description`: `(string: <optional>)` - The tag description. Specify `Description` in the payload.
+
+### Sample Payload
+
+```json
+{
+  "Version": 0,
+  "Description": "The version we can roll back to."
+}
+```
+
+### Sample Request
+
+This example creates a tag named `golden-version` for version zero of the
+`hello-world` job.
+
+```shell-session
+$ curl -X POST \
+ localhost:4646/v1/job/hello-world/versions/golden-version/tag \
+ -H "Content-Type: application/json" -d \
+ '{"Version": 0, "Description": "The version we can roll back to."}'
+```
+
+### Sample Response
+
+```json
+{
+  "Name":"golden-version",
+  "Description":"The version we can roll back to.",
+  "TaggedTime":1728325495829793000,
+  "Index":361,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""}
+```
+
+## Delete Job Version Tag
+
+This endpoint deletes a job version tag.
+
+| Method | Path              | Produces           |
+| ------ | ----------------- | ------------------ |
+| `DELETE`  | `/v1/job/:job_id/versions/:tag_name/tag` | `application/json` |
+
+### Parameters
+
+- `:job_id` `(string: <required>)` - The ID of the job. Specify `job_id` as part of the path.
+- `:tag_name` `(string: <required>)` - The tag name. Specify `tag_name` as part of the path.
+
+### Sample Request
+
+This example deletes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ curl -X DELETE localhost:4646/v1/job/hello-world/versions/golden-version/tag -H "Content-Type: application/json"
+```
+
+### Sample Response
+
+```json
+{
+  "EvalID":"",
+  "EvalCreateIndex":0,
+  "JobModifyIndex":0,
+  "VolumeEvalID":"",
+  "VolumeEvalIndex":0,
+  "Index":0,
+  "LastContact":0,
+  "KnownLeader":false,
+  "NextToken":""
+}
+```
+
diff --git a/content/nomad/v1.9.x/content/api-docs/json-jobs.mdx b/content/nomad/v1.9.x/content/api-docs/json-jobs.mdx
new file mode 100644
index 0000000000..8724a47902
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/json-jobs.mdx
@@ -0,0 +1,1246 @@
+---
+layout: api
+page_title: JSON Job Specification - HTTP API
+description: |-
+  Jobs can also be specified via the HTTP API using a JSON format. This guide
+  discusses the job specification in JSON format.
+---
+
+# JSON Job Specification
+
+Nomad's HTTP API uses JSON formatted job specifications except for the
+[`/job/parse` API][job-parse] which exists to convert HCL to JSON.
+
+The Nomad CLI includes a number of useful commands for working with JSON jobs.
+
+The [`nomad job run -output`][job-output] flag converts HCL jobs to JSON
+without submitting the job:
+
+```shell-session
+$ nomad job run -output my-job.nomad
+```
+
+The [`nomad job inspect`][job-inspect] command retrieves the JSON specification
+for an existing job:
+
+```shell-session
+$ nomad job inspect example
+```
+
+The [`nomad job run -json`][job-run-json] flag submits a JSON formatted job:
+
+```shell-session
+$ nomad job run -json example.json
+```
+
+[job-inspect]: /nomad/docs/commands/job/inspect
+[job-output]: /nomad/docs/commands/job/run#output
+[job-parse]: /nomad/api-docs/jobs#parse-job
+[job-run-json]: /nomad/docs/commands/job/run#json
+
+## Syntax
+
+Below is the JSON representation of the example job as well as the commands to
+reproduce it:
+
+```shell-session
+$ nomad init
+Example job file written to example.nomad.hcl
+$ nomad job run -output example.nomad.hcl
+```
+
+```json
+{
+  "Job": {
+    "Region": null,
+    "Namespace": null,
+    "ID": "example",
+    "Name": "example",
+    "Type": "service",
+    "Priority": null,
+    "AllAtOnce": null,
+    "Datacenters": [
+      "dc1"
+    ],
+    "NodePool": "prod",
+    "Constraints": null,
+    "Affinities": null,
+    "TaskGroups": [
+      {
+        "Name": "cache",
+        "Count": 1,
+        "Constraints": null,
+        "Affinities": null,
+        "Tasks": [
+          {
+            "Name": "redis",
+            "Driver": "docker",
+            "User": "",
+            "Lifecycle": null,
+            "Config": {
+              "auth_soft_fail": true,
+              "image": "redis:7",
+              "ports": [
+                "db"
+              ]
+            },
+            "Constraints": null,
+            "Affinities": null,
+            "Env": null,
+            "Services": null,
+            "Resources": {
+              "CPU": 500,
+              "Cores": null,
+              "MemoryMB": 256,
+              "MemoryMaxMB": null,
+              "DiskMB": null,
+              "Networks": null,
+              "Devices": null,
+              "IOPS": null
+            },
+            "RestartPolicy": null,
+            "Meta": null,
+            "KillTimeout": null,
+            "LogConfig": null,
+            "Artifacts": null,
+            "Vault": null,
+            "Templates": null,
+            "DispatchPayload": null,
+            "VolumeMounts": null,
+            "Leader": false,
+            "ShutdownDelay": 0,
+            "KillSignal": "",
+            "Kind": "",
+            "ScalingPolicies": null,
+            "Identity": {
+              "Env": true,
+              "File": true
+            }
+          }
+        ],
+        "Spreads": null,
+        "Volumes": null,
+        "RestartPolicy": {
+          "Interval": 1800000000000,
+          "Attempts": 2,
+          "Delay": 15000000000,
+          "Mode": "fail"
+        },
+        "ReschedulePolicy": null,
+        "EphemeralDisk": {
+          "Sticky": null,
+          "Migrate": null,
+          "SizeMB": 300
+        },
+        "Update": null,
+        "Migrate": null,
+        "Networks": [
+          {
+            "Mode": "",
+            "Device": "",
+            "CIDR": "",
+            "IP": "",
+            "DNS": null,
+            "ReservedPorts": null,
+            "DynamicPorts": [
+              {
+                "Label": "db",
+                "Value": 0,
+                "To": 6379,
+                "HostNetwork": ""
+              }
+            ],
+            "Hostname": "",
+            "MBits": null
+          }
+        ],
+        "Meta": null,
+        "Services": [
+          {
+            "Name": "redis-cache",
+            "Tags": [
+              "global",
+              "cache"
+            ],
+            "CanaryTags": null,
+            "EnableTagOverride": false,
+            "PortLabel": "db",
+            "AddressMode": "",
+            "Address": "",
+            "Checks": null,
+            "CheckRestart": null,
+            "Connect": null,
+            "Meta": null,
+            "CanaryMeta": null,
+            "TaggedAddresses": null,
+            "TaskName": "",
+            "OnUpdate": "",
+            "Provider": "nomad"
+          }
+        ],
+        "ShutdownDelay": null,
+        "StopAfterClientDisconnect": null,
+        "MaxClientDisconnect": null,
+        "Scaling": null,
+        "Consul": null
+      }
+    ],
+    "Update": {
+      "Stagger": null,
+      "MaxParallel": 1,
+      "HealthCheck": null,
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 180000000000,
+      "ProgressDeadline": 600000000000,
+      "Canary": 0,
+      "AutoRevert": false,
+      "AutoPromote": null
+    },
+    "Multiregion": null,
+    "Spreads": null,
+    "Periodic": null,
+    "ParameterizedJob": null,
+    "Reschedule": null,
+    "Migrate": {
+      "MaxParallel": 1,
+      "HealthCheck": "checks",
+      "MinHealthyTime": 10000000000,
+      "HealthyDeadline": 300000000000
+    },
+    "Meta": null,
+    "ConsulToken": null,
+    "VaultToken": null,
+    "Stop": null,
+    "ParentID": null,
+    "Dispatched": false,
+    "DispatchIdempotencyToken": null,
+    "Payload": null,
+    "ConsulNamespace": null,
+    "VaultNamespace": null,
+    "NomadTokenID": null,
+    "Status": null,
+    "StatusDescription": null,
+    "Stable": null,
+    "Version": null,
+    "SubmitTime": null,
+    "CreateIndex": null,
+    "ModifyIndex": null,
+    "JobModifyIndex": null
+  }
+}
+```
+
+## Syntax Reference
+
+Following is a syntax reference for the possible keys that are supported and
+their default values if any for each type of object.
+
+### Job
+
+The `Job` object supports the following keys:
+
+- `AllAtOnce` - Controls whether the scheduler can make partial placements if
+  optimistic scheduling resulted in an oversubscribed node. This does not
+  control whether all allocations for the job, where all would be the desired
+  count for each task group, must be placed atomically. This should only be
+  used for special circumstances. Defaults to `false`.
+
+- `Constraints` - A list to define additional constraints where a job can be
+  run. See the constraint reference for more details.
+
+- `Affinities` - A list to define placement preferences on nodes where a job can be
+  run. See the affinity reference for more details.
+
+- `Spreads` - A list to define allocation spread across attributes. See the spread reference
+  for more details.
+
+- `Datacenters` - A list of datacenters in the region which are eligible
+  for task placement. This must be provided, and does not have a default.
+
+- `NodePool` - The node pool in which the job can be placed. Defaults to `"default"`.
+
+- `TaskGroups` - A list to define additional task groups. See the task group
+  reference for more details.
+
+- `Meta` - Annotates the job with opaque metadata.
+
+- `ConsulToken` - Specifies the Consul token that proves the submitter of the
+  job has access to the Service Identity policies associated with the job's
+  Consul Connect enabled services. This field is only used to transfer the
+  token and is not stored after job submission.
+
+- `VaultToken` - Specifies the Vault token that proves the submitter of the job
+  has access to the specified policies in the `vault` block. This field is
+  only used to transfer the token and is not stored after job submission.
+
+- `Namespace` - The namespace to execute the job in, defaults to "default".
+
+- `ParameterizedJob` - Specifies the job as a parameterized job such that it can
+  be dispatched against. The `ParameterizedJob` object supports the following
+  attributes:
+
+  - `MetaOptional` - Specifies the set of metadata keys that may be provided
+    when dispatching against the job as a string array.
+
+  - `MetaRequired` - Specifies the set of metadata keys that must be provided
+    when dispatching against the job as a string array.
+
+  - `Payload` - Specifies the requirement of providing a payload when
+    dispatching against the parameterized job. The options for this field are
+    "optional", "required" and "forbidden". The default value is "optional".
+
+- `DispatchIdempotencyToken` - Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `Payload` - The payload may not be set when submitting a job but may appear in
+  a dispatched job. The `Payload` will be a base64 encoded string containing the
+  payload that the job was dispatched with. The `payload` has a **maximum size
+  of 16 KiB**.
+
+- `Priority` - Specifies the job priority which is used to prioritize
+  scheduling and access to resources. Must be between 1 and 100 inclusively,
+  and defaults to 50.
+
+- `Region` - The region to run the job in, defaults to "global".
+
+- `Type` - Specifies the job type and switches which scheduler
+  is used. Nomad provides the `service`, `system` and `batch` schedulers,
+  and defaults to `service`. To learn more about each scheduler type visit
+  [here](/nomad/docs/schedulers)
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Periodic` - `Periodic` allows the job to be scheduled at fixed times, dates
+  or intervals. The periodic expression is always evaluated in the UTC
+  timezone to ensure consistent evaluation when Nomad Servers span multiple
+  time zones. The `Periodic` object is optional and supports the following attributes:
+
+  - `Enabled` - `Enabled` determines whether the periodic job will spawn child
+    jobs.
+
+  - `TimeZone` - Specifies the time zone to evaluate the next launch interval
+    against. This is useful when wanting to account for day light savings in
+    various time zones. The time zone must be parsable by Golang's
+    [LoadLocation](https://golang.org/pkg/time/#LoadLocation). The default is
+    UTC.
+
+  - `SpecType` - `SpecType` determines how Nomad is going to interpret the
+    periodic expression. `cron` is the only supported `SpecType` currently.
+
+  - `Spec` - A cron expression configuring the interval the job is launched
+    at. Supports predefined expressions such as "@daily" and "@weekly" See
+    [here](https://github.com/gorhill/cronexpr#implementation) for full
+    documentation of supported cron specs and the predefined expressions.
+
+  - `Specs` - A list of cron expressions configuring the intervals the job is
+    launched at. The job runs at the next earliest time that matches any of the
+    expressions. Supports predefined expressions such as `@daily` and
+    `@weekly`. Refer to [the
+    documentation](https://github.com/gorhill/cronexpr#implementation) for full
+    details about the supported cron specs and the predefined expressions.
+    Conflicts with `Spec`.
+
+  - <a id="prohibit_overlap">`ProhibitOverlap`</a> - `ProhibitOverlap` can be set
+    to true to enforce that the periodic job doesn't spawn a new instance of the
+    job if any of the previous jobs are still running. It is defaulted to false.
+
+  An example `periodic` block:
+
+  ```json
+  {
+    "Periodic": {
+      "Spec": "*/15 - *",
+      "TimeZone": "Europe/Berlin",
+      "SpecType": "cron",
+      "Enabled": true,
+      "ProhibitOverlap": true
+    }
+  }
+  ```
+
+- `ReschedulePolicy` - Specifies a reschedule policy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the reschedule blocks are merged, with the task group's taking precedence. For more
+  details on `ReschedulePolicy`, please see below.
+
+- `Ui` - Options to modify the presentation of the Job index page in the Web UI.
+  When specified, a description and any number of links will be added to the top of
+  the job page in question.
+
+  - `Description` - a markdown-enabled string description of the job
+    jobs.
+
+  - `Links` - Anchor link that will appear at the top of the job page.
+
+    - `Label` - The shown name of the link
+    - `Url` - The address that the link will point to
+
+  An example `ui` block:
+
+  ```json
+  "Ui": {
+    "Description": "A job that uses **Nomad Variables** to modify its output",
+    "Links": [
+      {
+        "Label": "Learn more about Nomad Variables",
+        "Url": "https://developer.hashicorp.com/nomad/docs/concepts/variables"
+      },
+      {
+        "Label": "See this job on Github",
+        "Url": "https://github.com/hashicorp/nomad/blob/main/ui/app/utils/default_jobs/variables.js"
+      }
+    ]
+  }
+  ```
+
+### Task Group
+
+`TaskGroups` is a list of `TaskGroup` objects, each supports the following
+attributes:
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `Count` - Specifies the number of the task groups that should
+  be running. Must be non-negative, defaults to one.
+
+- `Meta` - A key-value map that annotates the task group with opaque metadata.
+
+- `Migrate` - Specifies a migration strategy to be applied during [node
+  drains][drain].
+
+  - `HealthCheck` - One of `checks` or `task_states`. Indicates how task health
+    should be determined: either via Consul health checks or whether the task
+    was able to run successfully.
+
+  - `HealthyDeadline` - Specifies duration a task must become healthy within
+    before it is considered unhealthy.
+
+  - `MaxParallel` - Specifies how many allocations may be migrated at once.
+
+  - `MinHealthyTime` - Specifies duration a task must be considered healthy
+    before the migration is considered healthy.
+
+- `Name` - The name of the task group. Must be specified.
+
+- `RestartPolicy` - Specifies the restart policy to be applied to tasks in this group.
+  If omitted, a default policy for batch and non-batch jobs is used based on the
+  job type. See the [restart policy reference](#restart_policy) for more details.
+
+- `ReschedulePolicy` - Specifies the reschedule policy to be applied to tasks in this group.
+  If omitted, a default policy is used for batch and service jobs. System jobs are not eligible
+  for rescheduling. See the [reschedule policy reference](#reschedule_policy) for more details.
+
+- `Scaling` - Specifies the autoscaling policy for the task group. This is primarily for supporting
+  external autoscalers. See the [scaling policy reference](#scaling_policy) for more details.
+
+- `EphemeralDisk` - Specifies the group's ephemeral disk requirements. See the
+  [ephemeral disk reference](#ephemeral_disk) for more details.
+
+- `Update` - Specifies an update strategy to be applied to all task groups
+  within the job. When specified both at the job level and the task group level,
+  the update blocks are merged with the task group's taking precedence. For more
+  details on the update block, please see below.
+
+- `Tasks` - A list of `Task` object that are part of the task group.
+
+### Task
+
+The `Task` object supports the following keys:
+
+- `Artifacts` - `Artifacts` is a list of `Artifact` objects which define
+  artifacts to be downloaded before the task is run. See the artifacts
+  reference for more details.
+
+- `Config` - A map of key-value configuration passed into the driver
+  to start the task. The details of configurations are specific to
+  each driver.
+
+- `Constraints` - This is a list of `Constraint` objects. See the constraint
+  reference for more details.
+
+- `Affinities` - This is a list of `Affinity` objects. See the affinity
+  reference for more details.
+
+- `Spreads` - This is a list of `Spread` objects. See the spread
+  reference for more details.
+
+- `DispatchPayload` - Configures the task to have access to dispatch payloads.
+  The `DispatchPayload` object supports the following attributes:
+
+  - `File` - Specifies the file name to write the content of dispatch payload
+    to. The file is written relative to the task's local directory.
+
+- `Driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java`, and `exec`.
+
+- `Env` - A map of key-value representing environment variables that
+  will be passed along to the running process. Nomad variables are
+  interpreted when set in the environment variable values. See the table of
+  interpreted variables [here](/nomad/docs/runtime/interpolation).
+
+  For example the below environment map will be reinterpreted:
+
+  ```json
+  {
+    "Env": {
+      "NODE_CLASS": "${nomad.class}"
+    }
+  }
+  ```
+
+- `Identity` - Specifies whether to expose Nomad's [Workload Identity][]
+  to the task.
+
+  - `Env` - If `true` the `NOMAD_TOKEN` environment variable will be set.
+
+  - `File` - If `true` the `secrets/nomad_token` file will be created.
+
+- `KillSignal` - Specifies a configurable kill signal for a task, where the
+  default is SIGINT. Note that this is only supported for drivers which accept
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java` drivers).
+
+- `KillTimeout` - `KillTimeout` is a time duration in nanoseconds. It can be
+  used to configure the time between signaling a task it will be killed and
+  actually killing it. Drivers first sends a task the `SIGINT` signal and then
+  sends `SIGTERM` if the task doesn't die after the `KillTimeout` duration has
+  elapsed. The default `KillTimeout` is 5 seconds.
+
+- `Leader` - Specifies whether the task is the leader task of the task group. If
+  set to true, when the leader task completes, all other tasks within the task
+  group will be gracefully shutdown.
+
+- `LogConfig` - This allows configuring log rotation for the `stdout` and `stderr`
+  buffers of a Task. See the log rotation reference below for more details.
+
+- `Meta` - Annotates the task group with opaque metadata.
+
+- `Name` - The name of the task. This field is required.
+
+- `Resources` - Provides the resource requirements of the task.
+  See the resources reference for more details.
+
+- `RestartPolicy` - Specifies the task-specific restart policy.
+  If omitted, the restart policy from the encapsulating task group is used. If both
+  are present, they are merged. See the [restart policy reference](#restart_policy)
+  for more details.
+
+- `Services` - `Services` is a list of `Service` objects. Nomad integrates with
+  Consul for service discovery. A `Service` object represents a routable and
+  discoverable service on the network. Nomad automatically registers when a task
+  is started and de-registers it when the task transitions to the dead state.
+  [Click here](/nomad/docs/integrations/consul-integration#service-discovery) to learn more about
+  services. Below is the fields in the `Service` object:
+
+  - `Name`: An explicit name for the Service. Nomad will replace `${JOB}`,
+    `${TASKGROUP}` and `${TASK}` by the name of the job, task group or task,
+    respectively. `${BASE}` expands to the equivalent of
+    `${JOB}-${TASKGROUP}-${TASK}`, and is the default name for a Service.
+    Each service defined for a given task must have a distinct name, so if
+    a task has multiple services only one of them can use the default name
+    and the others must be explicitly named. Names must adhere to
+    [RFC-1123 §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are
+    limited to alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be
+    less than 64 characters in length.
+
+  - `Tags`: A list of string tags associated with this Service. String
+    interpolation is supported in tags.
+
+  - `Meta`: A key-value map that annotates the Consul service with
+    user-defined metadata. String interpolation is supported in meta.
+
+  - `CanaryTags`: A list of string tags associated with this Service while it
+    is a canary. Once the canary is promoted, the registered tags will be
+    updated to the set defined in the `Tags` field. String interpolation is
+    supported in tags.
+
+  - `CanaryMeta`: A key-value map that annotates this Service while it
+    is a canary. Once the canary is promoted, the registered meta will be
+    updated to the set defined in the `Meta` field or removed if the `Meta`
+    field is not set. String interpolation is supported in meta keys and
+    values.
+
+  - `PortLabel`: `PortLabel` is an optional string and is used to associate
+    a port with the service. If specified, the port label must match one
+    defined in the resources block. This could be a label of either a
+    dynamic or a static port.
+
+  - `Provider`: Specifies the service registration provider to use for service
+    registrations. Valid options are either `consul` or `nomad`. All services
+    within a single task group must utilise the same provider value.
+
+  - `Address`: Specifies a custom address to advertise in Consul or Nomad
+    service registration. If set, `AddressMode` must be in `auto` mode. Useful
+    with interpolation - for example to advertise the public IP address of an
+    AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+  - `AddressMode`: Specifies what address (host or driver-specific) this
+    service should advertise. Valid options are:
+
+    - `auto` - Allows the driver to determine whether the host or driver
+      address should be used. Defaults to `host` and only implemented by
+      Docker. If you use a Docker network plugin such as weave, Docker will
+      automatically use its address.
+
+    - `driver` - Use the IP specified by the driver, and the port specified
+      in a port map. A numeric port may be specified since port maps aren't
+      required by all network plugins. Useful for advertising SDN and
+      overlay network addresses. Task will fail if driver network cannot be
+      determined. Only implemented for Docker.
+
+    - `host` - Use the host IP and port.
+
+  - `Checks`: `Checks` is an array of check objects. A check object defines a
+    health check associated with the service. Nomad supports the `script`,
+    `http` and `tcp` Consul Checks. Script checks are not supported for the
+    qemu driver since the Nomad client doesn't have access to the file system
+    of a task using the QEMU driver.
+
+    - `Type`: This indicates the check types supported by Nomad. Valid
+      options are currently `script`, `http` and `tcp`.
+
+    - `Name`: The name of the health check.
+
+    - `AddressMode`: Same as `AddressMode` on `Service`. Unlike services,
+      checks do not have an `auto` address mode as there's no way for
+      Nomad to know which is the best address to use for checks. Consul
+      needs access to the address for any HTTP or TCP checks. Unlike `PortLabel`,
+      this setting is _not_ inherited from the `Service`.
+
+    - `PortLabel`: Specifies the label of the port on which the check will
+      be performed. Note this is the _label_ of the port and not the port
+      number unless `AddressMode: "driver"`. The port label must match one
+      defined in the Network block. If a port value was declared on the
+      `Service`, this will inherit from that value if not supplied. If
+      supplied, this value takes precedence over the `Service.PortLabel`
+      value. This is useful for services which operate on multiple ports.
+      `http` and `tcp` checks require a port while `script` checks do not.
+      Checks will use the host IP and ports by default. Numeric ports may be
+      used if `AddressMode: "driver"` is set on the check.
+
+    - `Header`: Headers for HTTP checks. Should be an object where the values
+      are an array of values. Headers will be written once for each value.
+
+    - `Interval`: This indicates the frequency of the health checks that
+      Consul will perform.
+
+    - `Timeout`: This indicates how long Consul will wait for a health
+      check query to succeed.
+
+    - `Method`: The HTTP method to use for HTTP checks. Defaults to GET.
+
+    - `Body`: The HTTP body to use for HTTP checks. Defaults to an empty string.
+
+    - `Path`: The path of the HTTP endpoint which Consul will query to query
+      the health of a service if the type of the check is `http`. Nomad
+      will add the IP of the service and the port, users are only required
+      to add the relative URL of the health check endpoint. Absolute paths
+      are not allowed.
+
+    - `Protocol`: This indicates the protocol for the HTTP checks. Valid
+      options are `http` and `https`. We default it to `http`.
+
+    - `Command`: This is the command that the Nomad client runs for doing
+      script based health check.
+
+    - `Args`: Additional arguments to the `command` for script based health
+      checks.
+
+    - `TLSSkipVerify`: If true, Consul will not attempt to verify the
+      certificate when performing HTTPS checks.
+
+    - `CheckRestart`: `CheckRestart` is an object which enables
+      restarting of tasks based upon Consul health checks.
+
+      - `Limit`: The number of unhealthy checks allowed before the
+        service is restarted. Defaults to `0` which disables health-based restarts.
+
+      - `Grace`: The duration to wait after a task starts or restarts
+        before counting unhealthy checks count against the limit. Defaults to "1s".
+
+      - `IgnoreWarnings`: Treat checks that are warning as passing.
+        Defaults to false which means warnings are considered unhealthy.
+
+- `ShutdownDelay` - Specifies the duration to wait when killing a task between
+  removing it from Consul and sending it a shutdown signal. Ideally services
+  would fail healthchecks once they receive a shutdown signal. Alternatively
+  `ShutdownDelay` may be set to give in flight requests time to complete before
+  shutting down.
+
+- `Templates` - Specifies the set of [`Template`](#template) objects to render for the task.
+  Templates can be used to inject both static and dynamic configuration with
+  data populated from environment variables, Consul and Vault.
+
+- `User` - Set the user that will run the task. It defaults to the same user
+  the Nomad client is being run as. This can only be set on Linux platforms.
+
+### Resources
+
+The `Resources` object supports the following keys:
+
+- `CPU` - The CPU required in MHz.
+
+- `MemoryMB` - The memory required in MB.
+
+- `Networks` - A list of network objects.
+
+- `Devices` - A list of device objects.
+
+The Network object supports the following keys:
+
+- `MBits` - The number of MBits in bandwidth required.
+
+Nomad can allocate two types of ports to a task - Dynamic and Static/Reserved
+ports. A network object allows the user to specify a list of `DynamicPorts` and
+`ReservedPorts`. Each object supports the following attributes:
+
+- `Value` - The port number for static ports. If the port is dynamic, then this
+  attribute is ignored.
+- `Label` - The label to annotate a port so that it can be referred in the
+  service discovery block or environment variables.
+
+The Device object supports the following keys:
+
+- `Name` - Specifies the device required. The following inputs are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+* `Count` - The count of devices being requested per task. Defaults to 1.
+
+* `Constraints` - A list to define constraints on which device can satisfy the
+  request. See the constraint reference for more details.
+
+* `Affinities` - A list to define preferences for which device should be
+  chosen. See the affinity reference for more details.
+
+<a id="ephemeral_disk"></a>
+
+### Ephemeral Disk
+
+The `EphemeralDisk` object supports the following keys:
+
+- `Migrate` - Specifies that the Nomad client should make a best-effort attempt
+  to migrate the data from a remote machine if placement cannot be made on the
+  original node. During data migration, the task will block starting until the
+  data migration has completed. Value is a boolean and the default is false.
+
+- `SizeMB` - Specifies the size of the ephemeral disk in MB. Default is 300.
+
+- `Sticky` - Specifies that Nomad should make a best-effort attempt to place the
+  updated allocation on the same machine. This will move the `local/` and
+  `alloc/data` directories to the new allocation. Value is a boolean and the
+  default is false.
+
+<a id="reschedule_policy"></a>
+
+### Reschedule Policy
+
+The `ReschedulePolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of reschedule attempts allowed
+  in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` is a sliding window within which at most `Attempts` number
+  of reschedule attempts are permitted.
+
+- `Delay` - A duration to wait before attempting rescheduling. It is specified in
+  nanoseconds.
+
+- `DelayFunction` - Specifies the function that is used to calculate subsequent reschedule delays.
+  The initial delay is specified by the `Delay` parameter. Allowed values for `DelayFunction` are listed below:
+
+  - `constant` - The delay between reschedule attempts stays at the `Delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `Delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `MaxDelay` - `MaxDelay` is an upper bound on the delay beyond which it will not increase. This parameter is used when
+  `DelayFunction` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `Unlimited` - `Unlimited` enables unlimited reschedule attempts. If this is set to true
+  the `Attempts` and `Interval` fields are not used.
+
+<a id="restart_policy"></a>
+
+### Restart Policy
+
+The `RestartPolicy` object supports the following keys:
+
+- `Attempts` - `Attempts` is the number of restarts allowed in an `Interval`.
+
+- `Interval` - `Interval` is a time duration that is specified in nanoseconds.
+  The `Interval` begins when the first task starts and ensures that only
+  `Attempts` number of restarts happens within it. If more than `Attempts`
+  number of failures happen, behavior is controlled by `Mode`.
+
+- `Delay` - A duration to wait before restarting a task. It is specified in
+  nanoseconds. A random jitter of up to 25% is added to the delay.
+
+- `Mode` - `Mode` is given as a string and controls the behavior when the task
+  fails more than `Attempts` times in an `Interval`. Possible values are listed
+  below:
+
+  - `delay` - `delay` will delay the next restart until the next `Interval` is
+    reached.
+
+  - `fail` - `fail` will not restart the task again.
+
+### Update
+
+Specifies the task group update strategy. When omitted, rolling updates are
+disabled. The update block can be specified at the job or task group level.
+When specified at the job, the update block is inherited by all task groups.
+When specified in both the job and in a task group, the blocks are merged with
+the task group's taking precedence. The `Update` object supports the following
+attributes:
+
+- `MaxParallel` - `MaxParallel` is given as an integer value and specifies
+  the number of tasks that can be updated at the same time.
+
+- `HealthCheck` - Specifies the mechanism in which allocations health is
+  determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated checks are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy
+    when all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `MinHealthyTime` - Specifies the minimum time the allocation must be in the
+  healthy state before it is marked as healthy and unblocks further allocations
+  from being updated.
+
+- `HealthyDeadline` - Specifies the deadline in which the allocation must be
+  marked as healthy after which the allocation is automatically transitioned to
+  unhealthy.
+
+- `ProgressDeadline` - Specifies the deadline in which an allocation must be
+  marked as healthy. The deadline begins when the first allocation for the
+  deployment is created and is reset whenever an allocation as part of the
+  deployment transitions to a healthy state. If no allocation transitions to the
+  healthy state before the progress deadline, the deployment is marked as
+  failed. If the `progress_deadline` is set to `0`, the first allocation to be
+  marked as unhealthy causes the deployment to fail.
+
+- `AutoRevert` - Specifies if the job should auto-revert to the last stable job
+  on deployment failure. A job is marked as stable if all the allocations as
+  part of its deployment were marked healthy.
+
+- `Canary` - Specifies that changes to the job that would result in destructive
+  updates should create the specified number of canaries without stopping any
+  previous allocations. Once the operator determines the canaries are healthy,
+  they can be promoted which unblocks a rolling update of the remaining
+  allocations at a rate of `max_parallel`.
+
+- `AutoPromote` - Specifies if the job should automatically promote to
+  the new deployment if all canaries become healthy.
+
+- `Stagger` - Specifies the delay between migrating allocations off nodes marked
+  for draining.
+
+An example `Update` block:
+
+```json
+{
+  "Update": {
+    "MaxParallel": 3,
+    "HealthCheck": "checks",
+    "MinHealthyTime": 15000000000,
+    "HealthyDeadline": 180000000000,
+    "AutoRevert": false,
+    "AutoPromote": false,
+    "Canary": 1
+  }
+}
+```
+
+### Constraint
+
+The `Constraint` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  constraint. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `distinct_hosts` - If set, the scheduler will not co-locate any task groups on the same
+    machine. This can be specified as a job constraint which applies the
+    constraint to all task groups in the job, or as a task group constraint which
+    scopes the effect to just that group. The constraint may not be
+    specified at the task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` and `RTarget` should be
+    omitted.
+
+  - `distinct_property` - If set, the scheduler selects nodes that have a
+    distinct value of the specified property. The `RTarget` specifies how
+    many allocations are allowed to share the value of a property. The
+    `RTarget` must be 1 or greater and if omitted, defaults to 1. This can
+    be specified as a job constraint which applies the constraint to all
+    task groups in the job, or as a task group constraint which scopes the
+    effect to just that group. The constraint may not be specified at the
+    task level.
+
+    Placing the constraint at both the job level and at the task group level is
+    redundant since when placed at the job level, the constraint will be applied
+    to all task groups. When specified, `LTarget` should be the property
+    that should be distinct and `RTarget` should be omitted.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+### Affinity
+
+Affinities allow operators to express placement preferences. More details on how they work
+are described in [affinities](/nomad/docs/job-specification/affinity)
+
+The `Affinity` object supports the following keys:
+
+- `LTarget` - Specifies the attribute to examine for the
+  affinity. See the table of attributes [here](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `RTarget` - Specifies the value to compare the attribute against.
+  This can be a literal value, another attribute or a regular expression if
+  the `Operator` is in "regexp" mode.
+
+- `Operand` - Specifies the test to be performed on the two targets. It takes on the
+  following values:
+
+  - `regexp` - Allows the `RTarget` to be a regular expression to be matched.
+
+  - `set_contains_all` - Allows the `RTarget` to be a comma separated list of values
+    that should be contained in the LTarget's value.
+
+  - `set_contains_any` - Allows the `RTarget` to be a comma separated list of values
+    any of which should be contained in the LTarget's value.
+
+  - Comparison Operators - `=`, `==`, `is`, `!=`, `not`, `>`, `>=`, `<`, `<=`. The
+    ordering is compared lexically.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one affinity.
+
+### Log Rotation
+
+The `LogConfig` object configures the log rotation policy for a task's `stdout` and
+`stderr`. The `LogConfig` object supports the following attributes:
+
+- `Disabled` - Disables log collection.
+
+- `MaxFiles` - The maximum number of rotated files Nomad will retain for
+  `stdout` and `stderr`, each tracked individually.
+
+- `MaxFileSizeMB` - The size of each rotated file. The size is specified in
+  `MB`.
+
+If the amount of disk resource requested for the task is less than the total
+amount of disk space needed to retain the rotated set of files, Nomad will return
+a validation error when a job is submitted.
+
+```json
+{
+  "LogConfig": {
+    "Disabled": false,
+    "MaxFiles": 3,
+    "MaxFileSizeMB": 10
+  }
+}
+```
+
+In the above example we have asked Nomad to retain 3 rotated files for both
+`stderr` and `stdout` and size of each file is 10 MB. The minimum disk space that
+would be required for the task would be 60 MB.
+
+### Artifact
+
+Nomad downloads artifacts using
+[`go-getter`](https://github.com/hashicorp/go-getter). The `go-getter` library
+allows downloading of artifacts from various sources using a URL as the input
+source. The key-value pairs given in the `options` block map directly to
+parameters appended to the supplied `source` URL. These are then used by
+`go-getter` to appropriately download the artifact. `go-getter` also has a CLI
+tool to validate its URL and can be used to check if the Nomad `artifact` is
+valid.
+
+Nomad allows downloading `http`, `https`, and `S3` artifacts. If these artifacts
+are archives (zip, tar.gz, bz2, etc.), these will be unarchived before the task
+is started.
+
+The `Artifact` object supports the following keys:
+
+- `GetterSource` - The path to the artifact to download.
+
+- `RelativeDest` - An optional path to download the artifact into relative to the
+  root of the task's directory. If omitted, it will default to `local/`.
+
+- `GetterOptions` - A `map[string]string` block of options for `go-getter`.
+  Full documentation of supported options are available
+  [here](https://github.com/hashicorp/go-getter/tree/ef5edd3d8f6f482b775199be2f3734fd20e04d4a#protocol-specific-options-1).
+  An example is given below:
+
+```json
+{
+  "GetterOptions": {
+    "checksum": "md5:c4aa853ad2215426eb7d70a21922e794",
+
+    "aws_access_key_id": "<id>",
+    "aws_access_key_secret": "<secret>",
+    "aws_access_token": "<token>"
+  }
+}
+```
+
+An example of downloading and unzipping an archive is as simple as:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://example.com/my.zip",
+      "GetterOptions": {
+        "checksum": "md5:7f4b3e3b4dd5150d4e5aaaa5efada4c3"
+      }
+    }
+  ]
+}
+```
+
+#### S3 examples
+
+S3 has several different types of addressing and more detail can be found
+[here](http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro)
+
+S3 region specific endpoints can be found
+[here](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region)
+
+Path based style:
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "https://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+or to override automatic detection in the URL, use the S3-specific syntax
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+Virtual hosted based style
+
+```json
+{
+  "Artifacts": [
+    {
+      "GetterSource": "my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+    }
+  ]
+}
+```
+
+### Template
+
+The `Template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+Nomad utilizes a tool called [Consul Template][ct]. The template can reference
+[Nomad's runtime environment variables][env]. For a full list of the API template
+functions, please refer to the [Consul Template README][ct].
+
+`Template` object supports following attributes:
+
+- `ChangeMode` - Specifies the behavior Nomad should take if the rendered
+  template changes. The default value is `"restart"`. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `ChangeSignal` - Specifies the signal to send to the task as a string like
+  "SIGUSR1" or "SIGINT". This option is required if the `ChangeMode` is
+  `signal`.
+
+- `ChangeScript` - Configures the script triggered on template change.  This
+  option is required if the `ChangeMode` is `script`.
+
+  The `ChangeScript` object supports the following attributes:
+
+  - `Command` - Specifies the full path to a script or executable that is to be
+    executed on template change. Path is relative to the driver, e.g., if running
+    with a container driver the path must be existing in the container. This
+    option is required is the `change_mode` is `script`.
+
+  - `Args` - List of arguments that are passed to the script that is to be
+    executed on template change.
+
+  - `Timeout` - Timeout for script execution specified using a label suffix like
+    "30s" or "1h". Default value is `"5s"`.
+
+  - `FailOnError` - If `true`, Nomad will kill the task if the script execution
+    fails. If `false`, script failure will be logged but the task will continue
+    uninterrupted. Default value is `false`.
+
+- `DestPath` - Specifies the location where the resulting template should be
+  rendered, relative to the task directory.
+
+- `EmbeddedTmpl` - Specifies the raw template to execute. One of `SourcePath`
+  or `EmbeddedTmpl` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `SourcePath` for larger templates.
+
+- `Envvars` - Specifies the template should be read back as environment
+  variables for the task.
+
+- `LeftDelim` - Specifies the left delimiter to use in the template. The default
+  is "{{" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `Perms` - Specifies the rendered template's permissions. File permissions are
+  given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `Uid` - Specifies the rendered template owner's user ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `Gid` - Specifies the rendered template owner's group ID.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `RightDelim` - Specifies the right delimiter to use in the template. The default
+  is "}}" for some templates, it may be easier to use a different delimiter that
+  does not conflict with the output file itself.
+
+- `SourcePath` - Specifies the path to the template to be rendered. `SourcePath`
+  is mutually exclusive with `EmbeddedTmpl` attribute. The source can be fetched
+  using an [`Artifact`](#artifact) resource. The template must exist on the
+  machine prior to starting the task; it is not possible to reference a template
+  inside of a Docker container, for example.
+
+- `Splay` - Specifies a random amount of time to wait between 0 ms and the given
+  splay value before invoking the change mode. Should be specified in
+  nanoseconds.
+
+- `VaultGrace` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+```json
+{
+  "Templates": [
+    {
+      "SourcePath": "local/config.conf.tpl",
+      "DestPath": "local/config.conf",
+      "EmbeddedTmpl": "",
+      "ChangeMode": "signal",
+      "ChangeSignal": "SIGUSR1",
+      "Splay": 5000000000
+    }
+  ]
+}
+```
+
+### Spread
+
+Spread allow operators to target specific percentages of allocations based on
+any node attribute or metadata. More details on how they work are described
+in [spread](/nomad/docs/job-specification/spread).
+
+The `Spread` object supports the following keys:
+
+- `Attribute` - Specifies the attribute to examine for the
+  spread. See the [table of attributes](/nomad/docs/runtime/interpolation#interpreted_node_vars) for examples.
+
+- `SpreadTarget` - Specifies a list of attribute values and percentages. This is an optional field, when
+  left empty Nomad will evenly spread allocations across values of the attribute.
+
+  - `Value` - The value of a specific target attribute, like "dc1" for `${node.datacenter}`.
+  - `Percent` - Desired percentage of allocations for this attribute value. The sum of
+    all spread target percentages must add up to 100.
+
+- `Weight` - A non zero weight, valid values are from -100 to 100. Used to express
+  relative preference when there is more than one spread or affinity.
+
+<a id="scaling_policy"></a>
+
+### Scaling
+
+Scaling policies allow operators to attach autoscaling configuration to a task group. This information
+can be queried by [external autoscalers](https://github.com/hashicorp/nomad-autoscaler).
+
+The `Scaling` object supports the following keys:
+
+- `Min` - The minimum allowable count for the task group. This is optional; if absent, the default
+  is the `Count` specified in the task group. Attempts to set the task group `Count` below `Min` will
+  result in a 400 error during job registration.
+
+- `Max` - The maximum allowable count for the task group. This is required if a scaling policy is provided.
+  This must be larger than `Min`. Attempts to set the task group `Count` above `Max` wil result in a 400
+  error during job registration.
+
+- `Enabled` - An optional boolean (default: `true`). This indicates to the autoscaler that this
+  scaling policy should be ignored. It is intended to allow autoscaling to be temporarily disabled
+  for a task group.
+
+- `Policy` - An optional JSON block. This is opaque to Nomad; see the documentation for the external
+  autoscaler (e.g., [nomad-autoscaler](https://github.com/hashicorp/nomad-autoscaler)).
+
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[drain]: /nomad/docs/commands/node/drain
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.9.x/content/api-docs/libraries-and-sdks.mdx b/content/nomad/v1.9.x/content/api-docs/libraries-and-sdks.mdx
new file mode 100644
index 0000000000..53734a477d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/libraries-and-sdks.mdx
@@ -0,0 +1,41 @@
+---
+layout: api
+page_title: Libraries and SDKs - HTTP API
+description: |-
+  There are many third-party libraries for interacting with Nomad's HTTP API.
+  This page lists the HashiCorp and community-maintained Nomad HTTP API client
+  libraries.
+---
+
+# Client Libraries & SDKs
+
+The programming libraries listed on this page can be used to consume the API
+more conveniently. Some are officially maintained while others are provided by
+the community.
+
+## Official Libraries
+
+- [`api`](https://github.com/hashicorp/nomad/tree/main/api) - Official Golang
+  client for the Nomad HTTP API ([GoDoc](https://pkg.go.dev/github.com/hashicorp/nomad/api))
+
+## Third-Party and Unsupported Libraries
+
+- [`python-nomad`](https://github.com/jrxfive/python-nomad) - Python client
+  for the Nomad HTTP API.
+
+- [`nomad-java-sdk`](https://github.com/hashicorp/nomad-java-sdk) - Official
+  Java client for the Nomad HTTP API.
+
+- [`nomad-scala-sdk`](https://github.com/hashicorp/nomad-scala-sdk) - Official
+  Scala client for the Nomad HTTP API.
+
+- [`nomad-ruby`](https://github.com/hashicorp/nomad-ruby) - Ruby client
+  for the Nomad HTTP API.
+
+- [`nomad-client`](https://github.com/barakb/nomad-client) - A non-blocking Kotlin Nomad client.
+
+- [`hostel`](https://github.com/LKNSI/hostel) - Nomad Client for NodeJS. Includes property checking, and an Object-based API.
+
+- [`nix-nomad`](https://github.com/tristanpemble/nix-nomad) - HashiCorp Nomad job definitions in Nix
+
+_Want to see your library here? [Submit a Pull Request](https://github.com/hashicorp/nomad)._
diff --git a/content/nomad/v1.9.x/content/api-docs/metrics.mdx b/content/nomad/v1.9.x/content/api-docs/metrics.mdx
new file mode 100644
index 0000000000..0f651a9a82
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/metrics.mdx
@@ -0,0 +1,96 @@
+---
+layout: api
+page_title: Metrics - HTTP API
+description: The /metrics endpoint is used to view metrics for Nomad
+---
+
+# Metrics HTTP API
+
+The `/metrics` endpoint returns metrics for the current Nomad process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:4646/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/namespaces.mdx b/content/nomad/v1.9.x/content/api-docs/namespaces.mdx
new file mode 100644
index 0000000000..f0d77e6a93
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/namespaces.mdx
@@ -0,0 +1,237 @@
+---
+layout: api
+page_title: Namespace - HTTP API
+description: The /namespace endpoints are used to query for and interact with namespaces.
+---
+
+# Namespace HTTP API
+
+The `/namespace` endpoints are used to query for and interact with namespaces.
+
+## List Namespaces
+
+This endpoint lists all namespaces.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/namespaces` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter namespaces on based on
+  an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespaces?prefix=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+  },
+  {
+    "Capabilities": null,
+    "CreateIndex": 17,
+    "Description": "Development Staging Namespace",
+    "Meta": {
+        "type": "dev",
+        "contact": "helpdesk@example.com"
+    },
+    "ModifyIndex": 17,
+    "Name": "staging",
+    "Quota": ""
+  }
+]
+```
+
+## Read Namespace
+
+This endpoint reads information about a specific namespace.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                               |
+| ---------------- | -------------------------------------------------------------------------- |
+| `YES`            | `namespace:*`<br />Any capability on the namespace authorizes the endpoint |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to query.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/namespace/staging
+```
+
+### Sample Response
+
+```json
+{
+  "Capabilities": null,
+  "CreateIndex": 17,
+  "Description": "Development Staging Namespace",
+  "Meta": {
+    "type": "dev",
+    "contact": "helpdesk@example.com"
+  },
+  "ModifyIndex": 17,
+  "Name": "staging",
+  "Quota": ""
+}
+```
+
+## Create or Update Namespace
+
+This endpoint is used to create or update a namespace.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/namespace/:namespace` <br /> `/v1/namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)`- Specifies the namespace to create or
+  update.
+
+- `Description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `Quota` `(string: "")` <EnterpriseAlert inline /> - Specifies an quota to
+  attach to the namespace.
+
+- `Capabilities` `(Capabilities: <optional>)` - Specifies capabilities allowed
+  in the namespace. These values are checked at job submission.
+
+  - `EnabledTaskDrivers` `(array<string>: [])` - List of task drivers allowed
+    in the namespace. If empty all task drivers are allowed.
+
+  - `DisabledTaskDrivers` `(array<string>: [])` - List of task drivers disabled
+    in the namespace.
+
+- `NodePoolConfiguration` `(NodePoolConfiguration: <optional>)` <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+  - `Default` `(string: "default")` - Specifies the node pool to use for jobs
+  in this namespace that don't define a node pool in their specification.
+
+  - `Allowed` `(array<string>: [])` - Specifies the node pools that are allowed
+    to be used by jobs in this namespace. This field supports wildcard globbing
+    through the use of `*` for multi-character matching. If specified, only the
+    node pools that match these patterns are allowed. This field cannot be used
+    with `Disabled`.
+
+  - `disabled` `(array<string>: [])` - Specifies the node pools that are not
+    allowed to be used by jobs in this namespace. This field supports wildcard
+    globbing through the use of `*` for multi-character matching. If specified,
+    any node pool is allowed except for those that match any of these patterns.
+    This field cannot be used with `Enabled`.
+
+### Sample Payload
+
+```json
+{
+  "Name": "api-prod",
+  "Description": "Production API Servers",
+  "Meta": {
+    "contact": "platform-eng@example.com"
+  },
+  "Quota": "prod-quota",
+  "Capabilities": {
+    "DisabledTaskDrivers": ["raw_exec"]
+  },
+  "NodePoolConfiguration": {
+    "Default": "prod-pool",
+    "Allowed": ["default"]
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace/api-prod
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @namespace.json \
+    https://localhost:4646/v1/namespace
+```
+
+## Delete Namespace
+
+This endpoint is used to delete a namespace.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/namespace/:namespace` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:namespace` `(string: <required>)`- Specifies the namespace to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/namespace/api-prod
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/node-pools.mdx b/content/nomad/v1.9.x/content/api-docs/node-pools.mdx
new file mode 100644
index 0000000000..6270c2bfb7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/node-pools.mdx
@@ -0,0 +1,437 @@
+---
+layout: api
+page_title: Node Pools - HTTP API
+description: The /node/pool endpoints are used to query for and interact with node pools.
+---
+
+# Node Pools HTTP API
+
+The `/node/pool` endpoints are used to query for and interact with node pools.
+
+## List Node Pools
+
+This endpoint list all node pools.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/v1/node/pools` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter node pools based on a
+  name prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node pool. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of node pools to return
+  for this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/v1/node/pools'
+```
+
+```shell-session
+$ nomad operator api '/v1/node/pools?prefix=prod'
+```
+
+```shell-session
+$ nomad operator api -filter 'Meta.env == "production"' '/v1/node/pools?per_page=5'
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Production workloads",
+    "Meta": {
+      "env": "production",
+      "team": "engineering"
+    },
+    "ModifyIndex": 11,
+    "Name": "prod-eng",
+    "SchedulerConfiguration": {
+      "SchedulerAlgorithm": "spread"
+    }
+  }
+]
+```
+
+## Read Node Pool
+
+This endpoint queries information about a node pool.
+
+| Method | Path                       | Produces           |
+| ------ | -------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `YES`            | `node_pool:read`  |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to query.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "ModifyIndex": 11,
+  "Name": "prod-eng",
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+## Create or Update Node Pool
+
+This endpoint is used to create or update a node pool.
+
+| Method | Path                                              | Produces           |
+| ------ | ------------------------------------------------- | ------------------ |
+| `POST` | `/v1/node/pool/:node_pool` <br /> `/v1/node/pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required      |
+| ---------------- | ----------------- |
+| `NO`             | `node_pool:write` |
+
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the node pool to create or update.
+  Must have fewer than 128 characters. Only alphanumeric, `-`, and `_` are
+  allowed.
+
+- `Description` `(string: "")` - Specifies the optional human-readable
+  description of the node pool. Must have fewer than 256 characters.
+
+- `Meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the node pool. Node pool metadata is not used by
+  Nomad and is intended for use by operators and third party tools.
+
+- `SchedulerConfiguration` `(SchedulerConfiguration: <optional>)` - Specifies
+  custom configuration applied when scheduling allocations in the node pool.
+
+  - `SchedulerAlgorithm` `(string: ""`) - The algorithm used by the scheduler
+    when scoring nodes. Possible values are `binpack` or `spread`. If not
+    specified the [global cluster configuration value][api_scheduler_algo] is used.
+
+### Sample Payload
+
+```json
+{
+  "Name": "prod-eng",
+  "Description": "Production workloads",
+  "Meta": {
+    "env": "production",
+    "team": "engineering"
+  },
+  "SchedulerConfiguration": {
+    "SchedulerAlgorithm": "spread"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pools
+```
+
+```shell-session
+$ cat pool.json | nomad operator api /v1/node/pool/prod-eng
+```
+
+## Delete Node Pool
+
+This endpoint is used to delete a node pool.
+
+| Method   | Path                       | Produces           |
+| -------- | -------------------------- | ------------------ |
+| `DELETE` | `/v1/node/pool/:node_pool` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to delete.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api -X DELETE /v1/node/pool/prod-eng
+```
+
+## List Node Pool Nodes
+
+This endpoint list the nodes in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                        |
+| ---------------- | ----------------------------------- |
+| `YES`            | `node:read` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list nodes.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "prod-eng",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+
+# List Node Pool Jobs
+
+This endpoint lists the jobs in a node pool.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `GET`  | `/v1/node/pool/:node_pool/jobs`  | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                 |
+| ---------------- | -------------------------------------------- |
+| `YES`            | `namespace:read-job` <br /> `node_pool:read` |
+
+### Parameters
+
+- `:node_pool` `(string: <required>)`- Specifies the node pool to list jobs.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination to reduce resource used
+  to serve the request.
+
+- `meta` `(bool: false)` - If set, jobs returned will include a
+  [meta](/nomad/docs/job-specification/meta) field containing key-value pairs
+  provided in the job specification's `meta` block.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all jobs across all the authorized namespaces.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of jobs to return for this
+  request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs
+```
+
+```shell-session
+$ nomad operator api /v1/node/pool/prod-eng/jobs?namespace=prod
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "ParentID": "",
+    "Name": "example",
+    "Type": "service",
+    "Priority": 50,
+    "Status": "pending",
+    "StatusDescription": "",
+    "JobSummary": {
+      "JobID": "example",
+      "Namespace": "default",
+      "Summary": {
+        "cache": {
+          "Queued": 1,
+          "Complete": 1,
+          "Failed": 0,
+          "Running": 0,
+          "Starting": 0,
+          "Lost": 0
+        }
+      },
+      "Children": {
+        "Pending": 0,
+        "Running": 0,
+        "Dead": 0
+      },
+      "CreateIndex": 52,
+      "ModifyIndex": 96
+    },
+    "CreateIndex": 52,
+    "ModifyIndex": 93,
+    "JobModifyIndex": 52
+  }
+]
+```
+
+[api_scheduler_alog]: /nomad/api-docs/operator/scheduler#scheduleralgorithm
diff --git a/content/nomad/v1.9.x/content/api-docs/nodes.mdx b/content/nomad/v1.9.x/content/api-docs/nodes.mdx
new file mode 100644
index 0000000000..ca0f1c38d4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/nodes.mdx
@@ -0,0 +1,1147 @@
+---
+layout: api
+page_title: Nodes - HTTP API
+description: The /node endpoints are used to query for and interact with client nodes.
+---
+
+# Nodes HTTP API
+
+The `/node` endpoints are used to query for and interact with client nodes.
+
+Requests to these endpoints are always forwarded to and answered by Nomad
+servers. The [`/client`](/nomad/api-docs/client) endpoints provide node
+information that are answered directly by the Nomad client.
+
+## List Nodes
+
+This endpoint lists all nodes registered with Nomad.
+
+| Method | Path        | Produces           |
+| ------ | ----------- | ------------------ |
+| `GET`  | `/v1/nodes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter nodes based on an ID
+  prefix. Because the value is decoded to bytes, the prefix must have an even
+  number of hexadecimal characters (0-9a-f). This is specified as a query
+  string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected node. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of nodes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `resources` `(bool: false)` - Specifies whether or not to include the
+  `NodeResources` and `ReservedResources` fields in the response.
+
+- `os` `(bool: false)` - Specifies whether or not to include special attributes
+   such as operating system name in the response.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?prefix=f7476465
+```
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/nodes?os=true
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "10.138.0.5",
+    "Attributes": {
+      "os.name": "ubuntu"
+    },
+    "CreateIndex": 6,
+    "Datacenter": "dc1",
+    "Drain": false,
+    "Drivers": {
+      "java": {
+        "Attributes": {
+          "driver.java.runtime": "OpenJDK Runtime Environment (build 1.8.0_162-8u162-b12-1~deb9u1-b12)",
+          "driver.java.vm": "OpenJDK 64-Bit Server VM (build 25.162-b12, mixed mode)",
+          "driver.java.version": "openjdk version \"1.8.0_162"
+        },
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.781948669Z"
+      },
+      "qemu": {
+        "Attributes": null,
+        "Detected": false,
+        "HealthDescription": "",
+        "Healthy": false,
+        "UpdateTime": "2018-04-11T23:33:48.7819898Z"
+      },
+      "rkt": {
+        "Attributes": {
+          "driver.rkt.appc.version": "0.8.11",
+          "driver.rkt.volumes.enabled": "1",
+          "driver.rkt.version": "1.29.0"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver rkt is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.81079772Z"
+      },
+      "docker": {
+        "Attributes": {
+          "driver.docker.bridge_ip": "172.17.0.1",
+          "driver.docker.version": "18.03.0-ce",
+          "driver.docker.volumes.enabled": "1"
+        },
+        "Detected": true,
+        "HealthDescription": "Driver is available and responsive",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.713720323Z"
+      },
+      "exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "Driver exec is detected: true",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:34:48.711026521Z"
+      },
+      "raw_exec": {
+        "Attributes": {},
+        "Detected": true,
+        "HealthDescription": "",
+        "Healthy": true,
+        "UpdateTime": "2018-04-11T23:33:48.710448534Z"
+      }
+    },
+    "ID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "LastDrain": null,
+    "ModifyIndex": 2526,
+    "Name": "nomad-4",
+    "NodeClass": "",
+    "NodePool": "default",
+    "SchedulingEligibility": "eligible",
+    "Status": "ready",
+    "StatusDescription": "",
+    "Version": "0.8.0-rc1"
+  }
+]
+```
+
+## Read Node
+
+This endpoint queries the status of a client node.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `YES`            | `node:read`  |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the ID of the node. This must be
+  the full UUID, not the short 8-character one. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941
+```
+
+### Sample Response
+
+```json
+{
+  "Attributes": {
+    "consul.datacenter": "dc1",
+    "consul.revision": "d2adfc0bd",
+    "consul.server": "true",
+    "consul.version": "1.5.2",
+    "cpu.arch": "amd64",
+    "cpu.frequency": "4000",
+    "cpu.modelname": "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz",
+    "cpu.numcores": "8",
+    "cpu.totalcompute": "32000",
+    "driver.docker": "1",
+    "driver.docker.bridge_ip": "172.17.0.1",
+    "driver.docker.os_type": "linux",
+    "driver.docker.runtimes": "runc",
+    "driver.docker.version": "18.09.6",
+    "driver.docker.volumes.enabled": "true",
+    "driver.mock_driver": "1",
+    "driver.raw_exec": "1",
+    "kernel.name": "linux",
+    "kernel.version": "4.19.56",
+    "memory.totalbytes": "16571674624",
+    "nomad.revision": "30da2b8f6c3aa860113c9d313c695a05eff5bb97+CHANGES",
+    "nomad.version": "1.1.0",
+    "os.name": "nixos",
+    "os.signals": "SIGTTOU,SIGTTIN,SIGSTOP,SIGSYS,SIGXCPU,SIGBUS,SIGKILL,SIGTERM,SIGIOT,SIGILL,SIGIO,SIGQUIT,SIGSEGV,SIGUSR1,SIGXFSZ,SIGCHLD,SIGUSR2,SIGURG,SIGFPE,SIGHUP,SIGINT,SIGPROF,SIGCONT,SIGALRM,SIGPIPE,SIGTRAP,SIGTSTP,SIGWINCH,SIGABRT",
+    "os.version": "\"19.03.173017.85f820d6e41 (Koi)\"",
+    "unique.advertise.address": "127.0.0.1:4646",
+    "unique.cgroup.mountpoint": "/sys/fs/cgroup",
+    "unique.consul.name": "mew",
+    "unique.hostname": "mew",
+    "unique.network.ip-address": "127.0.0.1",
+    "unique.storage.bytesfree": "8273698816",
+    "unique.storage.bytestotal": "8285835264",
+    "unique.storage.volume": "tmpfs"
+  },
+  "ComputedClass": "v1:390058673753570317",
+  "CreateIndex": 6,
+  "Datacenter": "dc1",
+  "Drain": false,
+  "DrainStrategy": null,
+  "Drivers": {
+    "docker": {
+      "Attributes": {
+        "driver.docker": "true",
+        "driver.docker.bridge_ip": "172.17.0.1",
+        "driver.docker.os_type": "linux",
+        "driver.docker.runtimes": "runc",
+        "driver.docker.version": "18.09.6",
+        "driver.docker.volumes.enabled": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.762716458+02:00"
+    },
+    "exec": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.6873373+02:00"
+    },
+    "java": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.687274359+02:00"
+    },
+    "qemu": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.688023782+02:00"
+    },
+    "raw_exec": {
+      "Attributes": {
+        "driver.raw_exec": "true"
+      },
+      "Detected": true,
+      "HealthDescription": "Healthy",
+      "Healthy": true,
+      "UpdateTime": "2019-08-26T12:22:50.687733347+02:00"
+    },
+    "rkt": {
+      "Attributes": null,
+      "Detected": false,
+      "HealthDescription": "Driver must run as root",
+      "Healthy": false,
+      "UpdateTime": "2019-08-26T12:22:50.68796043+02:00"
+    }
+  },
+  "Events": [
+    {
+      "CreateIndex": 6,
+      "Details": null,
+      "Message": "Node registered",
+      "Subsystem": "Cluster",
+      "Timestamp": "2021-03-31T12:11:39Z"
+    },
+    {
+      "CreateIndex": 11,
+      "Details": null,
+      "Message": "Node drain strategy set",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213412Z"
+    },
+    {
+      "CreateIndex": 12,
+      "Details": null,
+      "Message": "Node drain complete",
+      "Subsystem": "Drain",
+      "Timestamp": "2021-03-31T12:12:20.213639Z"
+    }
+  ],
+  "HTTPAddr": "127.0.0.1:4646",
+  "HostVolumes": {
+    "certificates": {
+      "Name": "certificates",
+      "Path": "/etc/ssl/certs",
+      "ReadOnly": true
+    },
+    "prod-mysql-a": {
+      "Name": "prod-mysql-a",
+      "Path": "/data/mysql",
+      "ReadOnly": false
+    }
+  },
+  "HostNetworks" : {
+    "public": {
+      "Name": "public",
+      "CIDR": "10.199.0.200/24",
+      "ReservedPorts": "8080,8081"
+    }
+  }
+  "ID": "1ac61e33-a465-2ace-f63f-cffa1285e7eb",
+  "LastDrain": {
+    "AccessorID": "4e1b7ce1-f8aa-d7ff-09f1-55c3a0fd3988",
+    "Meta": {
+      "message": "node maintenance"
+    },
+    "StartedAt": "2021-03-31T12:12:20Z",
+    "Status": "complete",
+    "UpdatedAt": "2021-03-31T12:12:20Z"
+  },
+  "Links": {
+    "consul": "dc1.mew"
+  },
+  "Meta": {
+    "connect.log_level": "info",
+    "connect.sidecar_image": "envoyproxy/envoy:v1.11.1"
+  },
+  "ModifyIndex": 14,
+  "Name": "mew",
+  "NodeClass": "",
+  "NodePool": "default",
+  "NodeResources": {
+    "Cpu": {
+      "CpuShares": 32000
+    },
+    "Devices": [
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "6a61929e-d572-092d-5921-156a913f8e56",
+            "Locality": {
+              "PciBusID": "77cda534-0660-2688-6c2e-ad6c62fc5ff3"
+            }
+          }
+        ],
+        "Name": "modelA",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      },
+      {
+        "Attributes": {
+          "attrB": {
+            "Float": 10.5,
+            "Unit": "MW"
+          },
+          "attrA": {
+            "Int": 1024,
+            "Unit": "MB"
+          }
+        },
+        "Instances": [
+          {
+            "HealthDescription": "",
+            "Healthy": true,
+            "ID": "73af5d3e-00f9-0786-9bc1-8f5ffa953f15",
+            "Locality": {
+              "PciBusID": "dbda64d1-ad25-6c7c-d3fb-798bae0581bf"
+            }
+          }
+        ],
+        "Name": "modelB",
+        "Type": "skeleton",
+        "Vendor": "hashicorp"
+      }
+    ],
+    "Disk": {
+      "DiskMB": 7890
+    },
+    "Memory": {
+      "MemoryMB": 15803
+    },
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ],
+    "NodeNetworks": [
+      {
+        "Addresses": [
+          {
+            "Address": "127.0.0.1",
+            "Alias": "default",
+            "Family": "ipv4",
+            "Gateway": "",
+            "ReservedPorts": ""
+          }
+        ],
+        "Device": "lo",
+        "MacAddress": "00:00:00:00:00:00",
+        "Mode": "host"
+      }
+    ]
+  },
+  "Reserved": {
+    "CPU": 0,
+    "Devices": null,
+    "DiskMB": 0,
+    "IOPS": 0,
+    "MemoryMB": 0,
+    "Networks": null
+  },
+  "ReservedResources": {
+    "Cpu": {
+      "CpuShares": 0
+    },
+    "Disk": {
+      "DiskMB": 0
+    },
+    "Memory": {
+      "MemoryMB": 0
+    },
+    "Networks": {
+      "ReservedHostPorts": ""
+    }
+  },
+  "Resources": {
+    "CPU": 32000,
+    "Devices": null,
+    "DiskMB": 7890,
+    "IOPS": 0,
+    "MemoryMB": 15803,
+    "Networks": [
+      {
+        "CIDR": "127.0.0.1/32",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "127.0.0.1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      },
+      {
+        "CIDR": "::1/128",
+        "Device": "lo",
+        "DynamicPorts": null,
+        "IP": "::1",
+        "MBits": 1000,
+        "Mode": "",
+        "ReservedPorts": null
+      }
+    ]
+  },
+  "SchedulingEligibility": "eligible",
+  "SecretID": "",
+  "Status": "ready",
+  "StatusDescription": "",
+  "StatusUpdatedAt": 1566814982,
+  "TLSEnabled": false
+}
+```
+
+## List Node Allocations
+
+This endpoint lists all of the allocations for the given node. This can be used to
+determine what allocations have been scheduled on the node, their current status,
+and the values of dynamically assigned resources, like ports.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/node/:node_id/allocations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                   |
+| ---------------- | ------------------------------ |
+| `YES`            | `node:read,namespace:read-job` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    http://localhost:4646/v1/node/e02b6169-83bd-9df6-69bd-832765f333eb/allocations
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "AllocModifyIndex": 2555,
+    "ClientDescription": "",
+    "ClientStatus": "running",
+    "CreateIndex": 2555,
+    "CreateTime": 1523490066575461000,
+    "DeploymentID": "",
+    "DeploymentStatus": {
+      "Healthy": true,
+      "ModifyIndex": 0
+    },
+    "DesiredDescription": "",
+    "DesiredStatus": "run",
+    "DesiredTransition": {
+      "Migrate": null
+    },
+    "EvalID": "5129bc74-9785-c39a-08da-bddc8aa778b1",
+    "FollowupEvalID": "",
+    "ID": "fefe81d0-08b2-4eca-fae6-6560cde46d31",
+    "Job": {
+      "AllAtOnce": false,
+      "Constraints": null,
+      "CreateIndex": 2553,
+      "Datacenters": ["dc1"],
+      "ID": "webapp",
+      "JobModifyIndex": 2553,
+      "Meta": null,
+      "ModifyIndex": 2554,
+      "Name": "webapp",
+      "Namespace": "default",
+      "ParameterizedJob": null,
+      "ParentID": "",
+      "Payload": null,
+      "Periodic": null,
+      "Priority": 50,
+      "Region": "global",
+      "Stable": false,
+      "Status": "pending",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1523490066563405000,
+      "TaskGroups": [
+        {
+          "Constraints": null,
+          "Count": 9,
+          "EphemeralDisk": {
+            "Migrate": false,
+            "SizeMB": 300,
+            "Sticky": false
+          },
+          "Meta": null,
+          "Migrate": {
+            "HealthCheck": "checks",
+            "HealthyDeadline": 300000000000,
+            "MaxParallel": 2,
+            "MinHealthyTime": 15000000000
+          },
+          "Name": "webapp",
+          "ReschedulePolicy": {
+            "Attempts": 0,
+            "Delay": 30000000000,
+            "DelayFunction": "exponential",
+            "Interval": 0,
+            "MaxDelay": 3600000000000,
+            "Unlimited": true
+          },
+          "RestartPolicy": {
+            "Attempts": 2,
+            "Delay": 15000000000,
+            "Interval": 1800000000000,
+            "Mode": "fail"
+          },
+          "Tasks": [
+            {
+              "Artifacts": null,
+              "Config": {
+                "args": ["-text", "ok4"],
+                "image": "hashicorp/http-echo:0.2.3",
+                "port_map": [
+                  {
+                    "http": 5678
+                  }
+                ]
+              },
+              "Constraints": null,
+              "DispatchPayload": null,
+              "Driver": "docker",
+              "Env": null,
+              "KillSignal": "",
+              "KillTimeout": 5000000000,
+              "Leader": false,
+              "LogConfig": {
+                "MaxFileSizeMB": 10,
+                "MaxFiles": 10
+              },
+              "Meta": null,
+              "Name": "webapp",
+              "Resources": {
+                "CPU": 100,
+                "DiskMB": 0,
+                "MemoryMB": 300,
+                "Networks": [
+                  {
+                    "CIDR": "",
+                    "Device": "",
+                    "DynamicPorts": [
+                      {
+                        "Label": "http",
+                        "Value": 0
+                      }
+                    ],
+                    "IP": "",
+                    "MBits": 10,
+                    "ReservedPorts": null
+                  }
+                ]
+              },
+              "Services": [
+                {
+                  "AddressMode": "auto",
+                  "Checks": [
+                    {
+                      "AddressMode": "",
+                      "Args": null,
+                      "CheckRestart": null,
+                      "Command": "",
+                      "Header": null,
+                      "InitialStatus": "",
+                      "Interval": 10000000000,
+                      "Method": "",
+                      "Name": "http-ok",
+                      "Path": "/",
+                      "PortLabel": "",
+                      "Protocol": "",
+                      "TLSSkipVerify": false,
+                      "Timeout": 2000000000,
+                      "Type": "http"
+                    }
+                  ],
+                  "Name": "webapp",
+                  "PortLabel": "http",
+                  "Tags": null
+                }
+              ],
+              "ShutdownDelay": 0,
+              "Templates": null,
+              "User": "",
+              "Vault": null
+            }
+          ],
+          "Update": null
+        }
+      ],
+      "Type": "service",
+      "Update": {
+        "AutoRevert": false,
+        "Canary": 0,
+        "HealthCheck": "",
+        "HealthyDeadline": 0,
+        "MaxParallel": 0,
+        "MinHealthyTime": 0,
+        "Stagger": 0
+      },
+      "VaultToken": "",
+      "Version": 0
+    },
+    "JobID": "webapp",
+    "Metrics": {
+      "AllocationTime": 63337,
+      "ClassExhausted": null,
+      "ClassFiltered": null,
+      "CoalescedFailures": 0,
+      "ConstraintFiltered": null,
+      "DimensionExhausted": null,
+      "NodesAvailable": {
+        "dc1": 2
+      },
+      "NodesEvaluated": 2,
+      "NodesExhausted": 0,
+      "NodesFiltered": 0,
+      "NodesInPool": 2,
+      "QuotaExhausted": null,
+      "Scores": {
+        "46f1c6c4-a0e5-21f6-fd5c-d76c3d84e806.binpack": 2.6950883117541586,
+        "f7476465-4d6e-c0de-26d0-e383c49be941.binpack": 2.6950883117541586
+      }
+    },
+    "ModifyIndex": 2567,
+    "ModifyTime": 1523490089807324000,
+    "Name": "webapp.webapp[0]",
+    "Namespace": "default",
+    "NextAllocation": "",
+    "NodeID": "f7476465-4d6e-c0de-26d0-e383c49be941",
+    "PreviousAllocation": "",
+    "RescheduleTracker": null,
+    "Resources": {
+      "CPU": 100,
+      "DiskMB": 300,
+      "MemoryMB": 300,
+      "Networks": [
+        {
+          "CIDR": "",
+          "Device": "eth0",
+          "DynamicPorts": [
+            {
+              "Label": "http",
+              "Value": 25920
+            }
+          ],
+          "IP": "10.138.0.5",
+          "MBits": 10,
+          "ReservedPorts": null
+        }
+      ]
+    },
+    "SharedResources": {
+      "CPU": 0,
+      "DiskMB": 300,
+      "MemoryMB": 0,
+      "Networks": null
+    },
+    "TaskGroup": "webapp",
+    "TaskResources": {
+      "webapp": {
+        "CPU": 100,
+        "DiskMB": 0,
+        "MemoryMB": 300,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "eth0",
+            "DynamicPorts": [
+              {
+                "Label": "http",
+                "Value": 25920
+              }
+            ],
+            "IP": "10.138.0.5",
+            "MBits": 10,
+            "ReservedPorts": null
+          }
+        ]
+      }
+    },
+    "TaskStates": {
+      "webapp": {
+        "Events": [
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task received by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066712543500,
+            "Type": "Received",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {
+              "message": "Building Task Directory"
+            },
+            "DiskLimit": 0,
+            "DisplayMessage": "Building Task Directory",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "Building Task Directory",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490066715208000,
+            "Type": "Task Setup",
+            "ValidationError": "",
+            "VaultError": ""
+          },
+          {
+            "Details": {},
+            "DiskLimit": 0,
+            "DisplayMessage": "Task started by client",
+            "DownloadError": "",
+            "DriverError": "",
+            "DriverMessage": "",
+            "ExitCode": 0,
+            "FailedSibling": "",
+            "FailsTask": false,
+            "GenericSource": "",
+            "KillError": "",
+            "KillReason": "",
+            "KillTimeout": 0,
+            "Message": "",
+            "RestartReason": "",
+            "SetupError": "",
+            "Signal": 0,
+            "StartDelay": 0,
+            "TaskSignal": "",
+            "TaskSignalReason": "",
+            "Time": 1523490068433051100,
+            "Type": "Started",
+            "ValidationError": "",
+            "VaultError": ""
+          }
+        ],
+        "Failed": false,
+        "FinishedAt": "0001-01-01T00:00:00Z",
+        "LastRestart": "0001-01-01T00:00:00Z",
+        "Restarts": 0,
+        "StartedAt": "2018-04-11T23:41:08.445128764Z",
+        "State": "running"
+      }
+    }
+  }
+]
+```
+
+## Create Node Evaluation
+
+This endpoint creates a new evaluation for the given node. This can be used to
+force a run of the scheduling logic.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/evaluate` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/evaluate
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3671,
+  "EvalIDs": ["4dfc2db7-b481-c53b-3072-14479aa44be3"],
+  "HeartbeatTTL": 0,
+  "Index": 3671,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "10.138.0.2:4647",
+  "NodeModifyIndex": 0,
+  "NumNodes": 3,
+  "Servers": [
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.2:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.3:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    },
+    {
+      "Datacenter": "dc1",
+      "RPCAdvertiseAddr": "10.138.0.4:4647",
+      "RPCMajorVersion": 1,
+      "RPCMinorVersion": 1
+    }
+  ]
+}
+```
+
+## Drain Node
+
+This endpoint toggles the drain mode of the node. When draining is enabled, no
+further allocations will be assigned to this node, and existing allocations will
+be migrated to new nodes. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for suggested usage.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/drain` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `DrainSpec` `(object: <optional>)` - Specifies if drain mode should be
+  enabled. A missing or null value disables an existing drain.
+
+  - `Deadline` `(int: <required>)` - Specifies how long to wait in nanoseconds
+    for allocations to finish migrating before they are force stopped. This is
+    also how long batch jobs are given to complete before being migrated.
+
+  - `IgnoreSystemJobs` `(bool: false)` - Specifies whether or not to stop system
+    jobs as part of a drain. By default system jobs will be stopped after all
+    other allocations have migrated or the deadline is reached. Setting this to
+    `true` means system jobs are always left running.
+
+- `MarkEligible` `(bool: false)` - Specifies whether to mark a node as eligible
+  for scheduling again when _disabling_ a drain.
+
+- `Meta` `(json: <optional>)` - A JSON map of strings with drain operation
+  metadata that will be persisted in `.LastDrain.Meta`.
+
+### Sample Payload
+
+```json
+{
+  "DrainSpec": {
+    "Deadline": 3600000000000,
+    "IgnoreSystemJobs": true
+  },
+  "Meta": {
+    "message": "drain for maintenance"
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @drain.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/drain
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+## Purge Node
+
+This endpoint purges a node from the system. Nodes can still join the cluster if
+they are alive.
+
+| Method | Path                      | Produces           |
+| ------ | ------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/purge` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST http://localhost:4646/v1/node/f7476465-4d6e-c0de-26d0-e383c49be941/purge
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 3817,
+  "EvalIDs": ["71bad787-5ab1-9939-be02-4809441583cd"],
+  "HeartbeatTTL": 0,
+  "Index": 3816,
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LeaderRPCAddr": "",
+  "NodeModifyIndex": 3816,
+  "NumNodes": 0,
+  "Servers": null
+}
+```
+
+## Toggle Node Eligibility
+
+This endpoint toggles the scheduling eligibility of the node.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `POST` | `/v1/node/:node_id/eligibility` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `node:write` |
+
+### Parameters
+
+- `:node_id` `(string: <required>)`- Specifies the UUID of the node. This must
+  be the full UUID, not the short 8-character one. This is specified as part of
+  the path.
+
+- `Eligibility` `(string: <required>)` - Either `eligible` or `ineligible`.
+
+### Sample Payload
+
+```json
+{
+  "Eligibility": "ineligible"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPOST \
+    --data @eligibility.json \
+    http://localhost:4646/v1/node/fb2170a8-257d-3c64-b14d-bc06cc94e34c/eligibility
+```
+
+### Sample Response
+
+```json
+{
+  "EvalCreateIndex": 0,
+  "EvalIDs": null,
+  "Index": 3742,
+  "NodeModifyIndex": 3742
+}
+```
+
+#### Field Reference
+
+- Events - A list of the last 10 node events for this node. A node event is a
+  high level concept of noteworthy events for a node.
+
+  Each node event has the following fields:
+
+  - `Message` - The specific message for the event, detailing what occurred.
+
+  - `Subsystem` - The subsystem where the node event took place. Subsystems
+    include:
+
+    - `Drain` - The Nomad server draining subsystem.
+
+    - `Driver` - The Nomad client driver subsystem.
+
+    - `Heartbeat` - Either Nomad client or server heartbeating subsystem.
+
+    - `Cluster` - Nomad server cluster management subsystem.
+
+  - `Details` - Any further details about the event, formatted as a key/value
+    pair.
+
+  - `Timestamp` - Each node event has an ISO 8601 timestamp.
+
+  - `CreateIndex` - The Raft index at which the event was committed.
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/autopilot.mdx b/content/nomad/v1.9.x/content/api-docs/operator/autopilot.mdx
new file mode 100644
index 0000000000..cfe2ea2a9d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/autopilot.mdx
@@ -0,0 +1,253 @@
+---
+layout: api
+page_title: Autopilot - Operator - HTTP API
+description: |-
+  The /operator/autopilot endpoints provide tools for managing Autopilot.
+---
+
+# Autopilot Operator HTTP API
+
+The `/operator/autopilot` endpoints allow for automatic operator-friendly
+management of Nomad servers including cleanup of dead servers, monitoring the
+state of the Raft cluster, and stable server introduction.
+
+## Read Autopilot Configuration
+
+This endpoint retrieves its latest Autopilot configuration.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+For more information about the Autopilot configuration options, see the
+[agent configuration section](/nomad/docs/configuration/autopilot).
+
+## Update Autopilot Configuration
+
+This endpoint updates the Autopilot configuration of the cluster.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `PUT`  | `/v1/operator/autopilot/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "CleanupDeadServers": true,
+  "LastContactThreshold": "200ms",
+  "MaxTrailingLogs": 250,
+  "ServerStabilizationTime": "10s",
+  "EnableRedundancyZones": false,
+  "DisableUpgradeMigration": false,
+  "EnableCustomUpgrades": false,
+  "CreateIndex": 4,
+  "ModifyIndex": 4
+}
+```
+
+- `CleanupDeadServers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `EnableRedundancyZones` `(bool: false)` - (Enterprise-only) Specifies whether
+  to enable redundancy zones.
+
+- `DisableUpgradeMigration` `(bool: false)` - (Enterprise-only) Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `EnableCustomUpgrades` `(bool: false)` - (Enterprise-only) Specifies whether to
+  enable using custom upgrade versions when performing migrations.
+
+## Read Health
+
+This endpoint queries the health of the autopilot status.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/autopilot/health` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/autopilot/health
+```
+
+### Sample response
+
+```json
+{
+  "Healthy": true,
+  "FailureTolerance": 0,
+  "Servers": [
+    {
+      "ID": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "Name": "node1",
+      "Address": "127.0.0.1:4647",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": true,
+      "LastContact": "0s",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": true,
+      "StableSince": "2017-03-06T22:07:51Z"
+    },
+    {
+      "ID": "e36ee410-cc3c-0a0c-c724-63817ab30303",
+      "Name": "node2",
+      "Address": "127.0.0.1:4747",
+      "SerfStatus": "alive",
+      "Version": "0.8.0",
+      "Leader": false,
+      "LastContact": "27.291304ms",
+      "LastTerm": 2,
+      "LastIndex": 46,
+      "Healthy": true,
+      "Voter": false,
+      "StableSince": "2017-03-06T22:18:26Z"
+    }
+  ],
+  "Leader": "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+  "Voters": [
+    "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+    "e36ee410-cc3c-0a0c-c724-63817ab30303"
+  ],
+}
+```
+
+- `Healthy` is whether all the servers are currently healthy.
+
+- `FailureTolerance` is the number of redundant healthy servers that could be
+  fail without causing an outage (this would be 2 in a healthy cluster of 5
+  servers).
+
+- `Servers` holds detailed health information on each server:
+
+  - `ID` is the Raft ID of the server.
+
+  - `Name` is the node name of the server.
+
+  - `Address` is the address of the server.
+
+  - `SerfStatus` is the SerfHealth check status for the server.
+
+  - `Version` is the Nomad version of the server.
+
+  - `Leader` is whether this server is currently the leader.
+
+  - `LastContact` is the time elapsed since this server's last contact with the leader.
+
+  - `LastTerm` is the server's last known Raft leader term.
+
+  - `LastIndex` is the index of the server's last committed Raft log entry.
+
+  - `Healthy` is whether the server is healthy according to the current Autopilot configuration.
+
+  - `Voter` is whether the server is a voting member of the Raft cluster.
+
+  - `StableSince` is the time this server has been in its current `Healthy` state.
+
+
+
+  The HTTP status code will indicate the health of the cluster. If `Healthy` is true, then a
+  status of 200 will be returned. If `Healthy` is false, then a status of 429 will be returned.
+
+<EnterpriseAlert>
+  This API endpoint return with more information in Nomad Enterprise. This is
+  not present in Nomad Community Edition.
+</EnterpriseAlert>
+
+When using Nomad Enterprise this endpoint will return more information about the
+underlying actions and state of Autopilot.
+
+```json
+{
+  ...
+  "ReadReplicas": null,
+  "RedundancyZones": {},
+  "Upgrade": {
+    "Status": "idle",
+    "TargetVersion": "1.7.5+ent",
+    "TargetVersionVoters": [
+      "e349749b-3303-3ddf-959c-b5885a0e1f6e",
+      "e36ee410-cc3c-0a0c-c724-63817ab30303"
+    ],
+    "TargetVersionNonVoters": null,
+    "TargetVersionReadReplicas": null,
+    "OtherVersionVoters": null,
+    "OtherVersionNonVoters": null,
+    "OtherVersionReadReplicas": null,
+    "RedundancyZones": {}
+  },
+  "OptimisticFailureTolerance": 0
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/index.mdx b/content/nomad/v1.9.x/content/api-docs/operator/index.mdx
new file mode 100644
index 0000000000..de998d540d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: api
+page_title: Operator - HTTP API
+description: |-
+  The /operator endpoints provides cluster-level tools for Nomad operators, such
+  as interacting with the Raft subsystem.
+---
+
+# Operator HTTP API
+
+The `/operator` endpoints provide cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem, licensing, snapshots, autopilot and scheduler configuration.
+
+~> Use this interface with extreme caution, as improper use could lead to a
+Nomad outage and even loss of data.
+
+See the [Outage Recovery](/nomad/tutorials/manage-clusters/outage-recovery) guide for some examples of how
+these capabilities are used. For a CLI to perform these operations manually,
+please see the documentation for the
+[`nomad operator`](/nomad/docs/commands/operator) command.
+
+Please choose a sub-section in the navigation for more information
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/keyring.mdx b/content/nomad/v1.9.x/content/api-docs/operator/keyring.mdx
new file mode 100644
index 0000000000..feeb0b237a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/keyring.mdx
@@ -0,0 +1,266 @@
+---
+layout: api
+page_title: Keyring - Operator - HTTP API
+description: |-
+  The /operator/keyring endpoints provide tools for Nomad operators to interact with the root keyring.
+---
+
+# Keyring Operator HTTP API
+
+The `/operator/keyring` endpoints manage encryption root keys used for storing
+variables and signing workload identities, including examining active encryption
+keys, rotating keys, or removing unused keys.
+
+See the [Key Management] documentation for information how these capabilities
+are used. For instructions on how to use the CLI to perform these operations
+manually, please see the documentation for the [`nomad operator root keyring`]
+commands.
+
+## List Active Public Keys
+
+This endpoint retrieves a list of active public keys used to sign [workload
+identities][wi]. The response is in the [JWKS][rfc7517] format as is commonly
+used by JWT auth methods.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/.well-known/jwks.json`    | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `none`       |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/jwks.json'
+```
+
+### Sample Response
+
+```json
+{
+  "keys": [
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "15a95f48-001a-8be5-5da9-d94901d022c9",
+      "alg": "RS256",
+      "n": "6sImUQR6A...FB7bKn02dKw",
+      "e": "AQAB"
+    },
+    {
+      "use": "sig",
+      "kty": "RSA",
+      "kid": "b7f6a3a7-14f9-4ac5-f713-32c9bce1fa93",
+      "alg": "RS256",
+      "n": "zEdiUB3DFuM...ii3kQvOf_eDApBDWJhfQw",
+      "e": "AQAB"
+    }
+  ]
+}
+```
+
+## OIDC Discovery
+
+This endpoint retrieves [OIDC configuration metadata][oidc-disco] for using
+[workload identities][wi] with third party services. Nomad will act as an
+identity provider (IDP) to allow third parties to authenticate workload
+identity JWTs based on the OIDC configurationa and JWKS.
+
+Most third parties will require this endpoint be accessible through a
+publically resolvable domain name and HTTPS signed by a trusted certificate
+authority.
+
+You must set the [`oidc_issuer`][oidc_issuer] Server agent configuration
+parameter before this endpoint is enabled. In most situations you will also
+need to run a proxy or load balancer for in front of this endpoint to serve the
+contents with HTTPS using a trusted certificate.
+
+| Method | Path                                | Produces           |
+|--------|-------------------------------------|--------------------|
+| `GET`  | `/.well-known/openid-configuration` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `none` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api '/.well-known/openid-configuration'
+```
+
+### Sample Response
+
+```json
+{
+  "id_token_signing_alg_values_supported": [
+    "RS256",
+    "EdDSA"
+  ],
+  "issuer": "http://example.com",
+  "jwks_uri": "http://example.com/.well-known/jwks.json",
+  "response_types_supported": [
+    "code"
+  ],
+  "subject_types_supported": [
+    "public"
+  ]
+}
+```
+
+## List Keys
+
+This endpoint retrieves a list of root keys known to the cluster. Note that only
+key metadata is returned and the key material is never made available via the
+HTTP API.
+
+| Method | Path                        | Produces           |
+|--------|-----------------------------|--------------------|
+| `GET`  | `/v1/operator/keyring/keys` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `YES`            | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/keyring/keys
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 13,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 13,
+    "State": "active"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 6,
+    "CreateTime": 1662665528857979100,
+    "KeyID": "64b96f4b-f167-f2dd-9148-7867f7e420e3",
+    "ModifyIndex": 12,
+    "State": "inactive"
+  },
+  {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 12,
+    "CreateTime": 1662665624108063000,
+    "KeyID": "f9725e52-9b49-5b55-a8eb-083e23db4a3e",
+    "ModifyIndex": 13,
+    "State": "inactive"
+  }
+]
+```
+
+## Rotate Key
+
+This endpoint forces the server to rotate the active root key.
+
+| Method | Path                          | Produces           |
+|--------|-------------------------------|--------------------|
+| `PUT`  | `/v1/operator/keyring/rotate` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+
+### Parameters
+
+- `full` `(bool: false)` - Decrypt all existing variables and re-encrypt with
+  the new key. This API request will immediately return and the re-encryption
+  process will run asynchronously on the leader.
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT \
+    https://localhost:4646/v1/operator/keyring/rotate
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 13,
+  "Key": {
+    "Algorithm": "aes256-gcm",
+    "CreateIndex": 0,
+    "CreateTime": 1662665630638648800,
+    "KeyID": "26cbda57-e01e-188d-5f39-b6e3fca95a5b",
+    "ModifyIndex": 0,
+    "State": "active"
+  }
+}
+```
+
+## Delete Key
+
+This endpoint deletes a root key in the `inactive` state.
+
+| Method   | Path                               | Produces           |
+|----------|------------------------------------|--------------------|
+| `DELETE` | `/v1/operator/keyring/key/:key_id` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | `management` |
+
+### Parameters
+
+- `force` `(bool: false)` - Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/operator/keyring/key/68237d9-1770-4d34-9c41-1f220107fc10
+```
+
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+
+[Key Management]: /nomad/docs/operations/key-management
+[`nomad operator root keyring`]: /nomad/docs/commands/operator/root/keyring-rotate
+[blocking queries]: /nomad/api-docs#blocking-queries
+[oidc-disco]: https://openid.net/specs/openid-connect-discovery-1_0.html
+[oidc_issuer]: /nomad/docs/configuration/server#oidc_issuer
+[required ACLs]: /nomad/api-docs#acls
+[rfc7517]: https://datatracker.ietf.org/doc/html/rfc7517
+[wi]: /nomad/docs/concepts/workload-identity
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/license.mdx b/content/nomad/v1.9.x/content/api-docs/operator/license.mdx
new file mode 100644
index 0000000000..7276caf06b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/license.mdx
@@ -0,0 +1,68 @@
+---
+layout: api
+page_title: License - Operator - HTTP API
+description: |-
+  The /operator/license endpoints allow for retrieving the Nomad Enterprise License.
+---
+
+# License Operator HTTP API
+
+<EnterpriseAlert />
+
+## Get Nomad Enterprise License Info
+
+This endpoint gets information about the current license.
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/operator/license` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/license
+```
+
+### Sample Response
+
+```json
+{
+  "KnownLeader": false,
+  "LastContact": 0,
+  "LastIndex": 0,
+  "License": {
+    "CustomerID": "customer name",
+    "ExpirationTime": "2020-06-01T14:50:16.581304556-04:00",
+    "Features": [
+      "Automated Upgrades",
+      "Enhanced Read Scalability",
+      "Redundancy Zones",
+      "Namespaces",
+      "Resource Quotas",
+      "Preemption",
+      "Audit Logging",
+      "Setinel Policies"
+    ],
+    "Flags": {
+      "modules": ["governance-policy"]
+    },
+    "InstallationID": "*",
+    "IssueTime": "2020-06-01T08:50:16.581304556-04:00",
+    "LicenseID": "6f706a45-bdac-4a70-968b-d93784894653",
+    "Modules": ["governance-policy"],
+    "Product": "nomad",
+    "StartTime": "2020-06-01T08:50:16.581304556-04:00",
+    "TerminationTime": "2020-06-01T14:50:16.581304556-04:00"
+  },
+  "RequestTime": 0
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/raft.mdx b/content/nomad/v1.9.x/content/api-docs/operator/raft.mdx
new file mode 100644
index 0000000000..fb77f6d8e6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/raft.mdx
@@ -0,0 +1,229 @@
+---
+layout: api
+page_title: Raft - Operator - HTTP API
+description: |-
+  The /operator/raft endpoints provide tools for management of the Raft subsystem.
+---
+
+# Raft Operator HTTP API
+
+The `/operator/raft` endpoints provide tools for management of the Raft subsystem.
+
+Please see the [Consensus Protocol Guide] for more information about Raft consensus protocol and its use.
+
+## Read Raft Configuration
+
+This endpoint queries the status of a client node registered with Nomad.
+
+| Method | Path                              | Produces           |
+| ------ | --------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/raft/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api /v1/operator/raft/configuration
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/raft/configuration
+```
+
+</Tab>
+</Tabs>
+
+### Sample Response
+
+```json
+{
+    "Index": 0,
+    "Servers": [
+        {
+            "Address": "10.1.0.10:4647",
+            "ID": "c13f9998-a0f3-d765-0b52-55a0b3ce5f88",
+            "Leader": false,
+            "Node": "node1.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.20:4647",
+            "ID": "d7927f2b-067f-45a4-6266-af8bb84de082",
+            "Leader": true,
+            "Node": "node2.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        },
+        {
+            "Address": "10.1.0.30:4647",
+            "ID": "00d56ef8-938e-abc3-6f8a-f8ac80a80fb9",
+            "Leader": false,
+            "Node": "node3.global",
+            "RaftProtocol": "3",
+            "Voter": true
+        }
+
+    ]
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft corresponding to this
+  configuration. The latest configuration may not yet be committed if changes
+  are in flight.
+
+- `Servers` `(array: Server)` - The returned `Servers` array has information
+  about the servers in the Raft peer configuration.
+
+  - `ID` `(string)` - The ID of the server. For Raft protocol v2, this is the
+    same as the `Address`. Raft protocol v3 uses GUIDs as the ID.
+
+  - `Node` `(string)` - The node name of the server, as known to Nomad, or
+    `"(unknown)"` if the node is stale and not known.
+
+  - `Address` `(string)` - The `ip:port` for the server.
+
+  - `Leader` `(bool)` - is either "true" or "false" depending on the server's
+    role in the Raft configuration.
+
+  - `Voter` `(bool)` - is "true" or "false", indicating if the server has a vote
+    in the Raft configuration. Future versions of Nomad may add support for
+    non-voting servers.
+
+## Remove Raft Peer
+
+This endpoint removes a Nomad server with given address from the Raft
+configuration. The return code signifies success or failure.
+
+| Method   | Path                     | Produces           |
+| -------- | ------------------------ | ------------------ |
+| `DELETE` | `/v1/operator/raft/peer` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  server to remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the server to
+  remove as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+  <Note>
+
+  Either `address` or `id` must be provided, but not both.
+
+  </Note>
+
+### Sample Request
+
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X DELETE \
+   /v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl \
+    --request DELETE \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    https://127.0.0.1:4646/v1/operator/raft/peer?address=1.2.3.4:4647
+```
+
+</Tab>
+</Tabs>
+
+## Transfer Leadership to another Raft Peer
+
+This endpoint tells the current cluster leader to transfer leadership
+to the Nomad server with given address or ID in the Raft
+configuration. The return code signifies success or failure.
+
+| Method              | Path                                    | Produces           |
+| ------------------- | --------------------------------------- | ------------------ |
+| `PUT` <br /> `POST` | `/v1/operator/raft/transfer-leadership` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `address` `(string: <optional>)` - Specifies the Raft **Address** of the
+  target server as provided in the output of `/v1/operator/raft/configuration`
+  API endpoint or the `nomad operator raft list-peers` command.
+
+- `id` `(string: <optional>)` - Specifies the Raft **ID** of the target server
+  as provided in the output of `/v1/operator/raft/configuration` API endpoint or
+  the `nomad operator raft list-peers` command.
+
+<Note>
+
+- The cluster must be running Raft protocol v3 or greater on all server members.
+
+- Either `address` or `id` must be provided, but not both.
+
+</Note>
+
+### Sample Requests
+
+<Tabs>
+<Tab heading="Nomad CLI">
+
+```shell-session
+$ nomad operator api -X PUT \
+    "/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+<Tab heading="curl">
+
+```shell-session
+$ curl --request PUT \
+    --header "X-Nomad-Token: ${NOMAD_TOKEN}"
+    "https://127.0.0.1:4646/v1/operator/raft/transfer-leadership?address=1.2.3.4:4647"
+```
+
+</Tab>
+</Tabs>
+
+[consensus protocol guide]: /nomad/docs/concepts/consensus
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/scheduler.mdx b/content/nomad/v1.9.x/content/api-docs/operator/scheduler.mdx
new file mode 100644
index 0000000000..be1b1328ce
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/scheduler.mdx
@@ -0,0 +1,210 @@
+---
+layout: api
+page_title: Scheduler - Operator - HTTP API
+description: |-
+  The /operator/scheduler endpoints provide tools for management of Nomad server scheduler settings.
+---
+
+# Scheduler Operator HTTP API
+
+The `/operator/scheduler` endpoints provide tools for management of Nomad server scheduler settings.
+
+## Read Scheduler Configuration
+
+This endpoint retrieves the latest Scheduler configuration. More options may be added in
+the future.
+
+| Method | Path                                   | Produces           |
+| ------ | -------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/operator/scheduler/configuration
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 5,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "SchedulerConfig": {
+    "CreateIndex": 5,
+    "MemoryOversubscriptionEnabled": false,
+    "ModifyIndex": 5,
+    "PauseEvalBroker": false,
+    "PreemptionConfig": {
+      "BatchSchedulerEnabled": false,
+      "ServiceSchedulerEnabled": false,
+      "SysBatchSchedulerEnabled": false,
+      "SystemSchedulerEnabled": true
+    },
+    "RejectJobRegistration": false,
+    "SchedulerAlgorithm": "binpack"
+  }
+}
+```
+
+#### Field Reference
+
+- `Index` `(int)` - The `Index` value is the Raft index corresponding to this
+  configuration.
+
+- `SchedulerConfig` `(SchedulerConfig)` - The returned `SchedulerConfig` object has configuration
+  settings mentioned below.
+
+  - `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+    binpacks or spreads allocations on available nodes. Node pools may set
+    their own [`SchedulerAlgorithm`][np_sched_algo] value that takes precedence
+    over this global value.
+
+  - `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+    exceed their reserved memory limit, if the client has excess memory
+    capacity. Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+    to take advantage of memory oversubscription. Node pools may set their own
+    [`MemoryOversubscriptionEnabled`][np_mem_oversubs] value that takes
+    precedence over this global value.
+
+  - `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+    permission denied errors for job registration, job dispatch, and job scale APIs,
+    unless the ACL token for the request is a management token. If ACLs are disabled,
+    no user will be able to register jobs. This allows operators to shed load from
+    automated processes during incident response.
+
+  - `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+    usually runs on the leader will be disabled. This will prevent the scheduler
+    workers from receiving new work.
+
+  - `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for various schedulers.
+
+    - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for system jobs is enabled. Note that
+      this defaults to true.
+
+    - `SysBatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for system batch jobs is enabled. Note that
+      this defaults to false.
+
+    - `BatchSchedulerEnabled` `(bool: false)` - Specifies whether preemption for batch jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+    - `ServiceSchedulerEnabled` `(bool: false)` - Specifies whether preemption for service jobs is enabled. Note that
+      this defaults to false and must be explicitly enabled.
+
+  - `CreateIndex` - The Raft index at which the config was created.
+  - `ModifyIndex` - The Raft index at which the config was modified.
+
+## Update Scheduler Configuration
+
+This endpoint updates the scheduler configuration of the cluster.
+
+| Method        | Path                                   | Produces           |
+| ------------- | -------------------------------------- | ------------------ |
+| `PUT`, `POST` | `/v1/operator/scheduler/configuration` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required     |
+| ---------------- | ---------------- |
+| `NO`             | `operator:write` |
+
+### Bootstrap Configuration Element
+
+The [`default_scheduler_config`][] attribute of the server block will provide a
+starting value for this configuration. Once bootstrapped, the value in the
+server state is authoritative.
+
+### Parameters
+
+- `cas` `(int: 0)` - Specifies to use a Check-And-Set operation. The update will
+  only happen if the given index matches the `ModifyIndex` of the configuration
+  at the time of writing.
+
+### Sample Payload
+
+```json
+{
+  "SchedulerAlgorithm": "spread",
+  "MemoryOversubscriptionEnabled": false,
+  "RejectJobRegistration": false,
+  "PauseEvalBroker": false,
+  "PreemptionConfig": {
+    "SystemSchedulerEnabled": true,
+    "SysBatchSchedulerEnabled": false,
+    "BatchSchedulerEnabled": false,
+    "ServiceSchedulerEnabled": true
+  }
+}
+```
+
+- `SchedulerAlgorithm` `(string: "binpack")` - Specifies whether scheduler
+  binpacks or spreads allocations on available nodes. Possible values are
+  `"binpack"` and `"spread"`. This value may also be set per [node
+  pool][np_sched_algo].
+
+- `MemoryOversubscriptionEnabled` `(bool: false)` - When `true`, tasks may
+  exceed their reserved memory limit, if the client has excess memory capacity.
+  Tasks must specify [`memory_max`](/nomad/docs/job-specification/resources#memory_max)
+  to take advantage of memory oversubscription. This value may also be set per
+  [node pool][np_mem_oversubs].
+
+- `RejectJobRegistration` `(bool: false)` - When `true`, the server will return
+  permission denied errors for job registration, job dispatch, and job scale APIs,
+  unless the ACL token for the request is a management token. If ACLs are disabled,
+  no user will be able to register jobs. This allows operators to shed load from
+  automated processes during incident response.
+
+- `PauseEvalBroker` `(bool: false)` - When set to `true`, the eval broker which
+  usually runs on the leader will be disabled. This will prevent the scheduler
+  workers from receiving new work.
+
+- `PreemptionConfig` `(PreemptionConfig)` - Options to enable preemption for
+  various schedulers.
+
+  - `SystemSchedulerEnabled` `(bool: true)` - Specifies whether preemption for
+    system jobs is enabled. Note that if this is set to true, then system jobs
+    can preempt any other jobs.
+
+  - `SysBatchSchedulerEnabled` `(bool: false)` <sup>1.2</sup> - Specifies
+    whether preemption for system batch jobs is enabled. Note that if this is
+    set to true, then system batch jobs can preempt any other jobs.
+
+  - `BatchSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for batch jobs is enabled. Note that if this is set to
+    true, then batch jobs can preempt any other jobs.
+
+  - `ServiceSchedulerEnabled` `(bool: false)` - Specifies
+    whether preemption for service jobs is enabled. Note that if this is set to
+    true, then service jobs can preempt any other jobs.
+
+### Sample Response
+
+```json
+{
+  "Updated": false,
+  "Index": 15
+}
+```
+
+- `Updated` - Indicates that the configuration was updated when a `cas` value is
+  provided. For non-CAS requests, this field will be false even though the
+  update is applied.
+
+- `Index` - Current Raft index when the request was received.
+
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[np_mem_oversubs]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[np_sched_algo]: /nomad/docs/other-specifications/node-pool#scheduler_algorithm
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/snapshot.mdx b/content/nomad/v1.9.x/content/api-docs/operator/snapshot.mdx
new file mode 100644
index 0000000000..d67516f2ca
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/snapshot.mdx
@@ -0,0 +1,85 @@
+---
+layout: api
+page_title: Snapshot - Operator - HTTP API
+description: |-
+  The /operator/snapshot endpoints save and restore Nomad's server state for disaster recovery.
+---
+
+# Snapshot Operator HTTP API
+
+## Generate Snapshot
+
+This endpoint generates and returns an atomic, point-in-time snapshot of the
+Nomad server state for disaster recovery. Snapshots include all state managed by Nomad's
+Raft [consensus protocol](/nomad/docs/concepts/consensus).
+
+Snapshots are exposed as gzipped tar archives which internally contain the Raft
+metadata required to restore, as well as a binary serialized version of the
+Nomad server state. The contents are covered internally by SHA-256 hashes.
+These hashes are verified during snapshot restore operations. The structure of
+the archive is internal to Nomad and not intended to be used other than for
+restore operations. The archives are not designed to be modified before a
+restore.
+
+| Method | Path                    | Produces                 |
+| :----- | :---------------------- | ------------------------ |
+| `GET`  | `/v1/operator/snapshot` | `200 application/x-gzip` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `stale` - Specifies if the cluster should respond without an active leader.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -o snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+The above example results in a tarball named `snapshot.tgz` in the current working directory.
+
+## Restore Snapshot
+
+This endpoint restores a point-in-time snapshot of the Nomad server state.
+
+Restores involve a potentially dangerous low-level Raft operation that is not
+designed to handle server failures during a restore. This operation is primarily
+intended to be used when recovering from a disaster, restoring into a fresh
+cluster of Nomad servers.
+
+The body of the request should be a snapshot archive returned from a previous
+call to the `GET` method.
+
+| Method | Path                    | Produces                      |
+| :----- | :---------------------- | ----------------------------- |
+| `PUT`  | `/v1/operator/snapshot` | `200 text/plain (empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data-binary @snapshot.tgz \
+    http://127.0.0.1:4646/v1/operator/snapshot
+```
+
+~> Some tools default to www/encoded uploads. Nomad expects the snapshot to be
+in pure binary form.
diff --git a/content/nomad/v1.9.x/content/api-docs/operator/upgrade-check.mdx b/content/nomad/v1.9.x/content/api-docs/operator/upgrade-check.mdx
new file mode 100644
index 0000000000..8659c6b135
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/operator/upgrade-check.mdx
@@ -0,0 +1,187 @@
+---
+layout: api
+page_title: Upgrade Check - Operator - HTTP API
+description: |-
+  The /operator/upgrade-check endpoints provide tools for verifying the state
+  of the cluster prior to upgrades.
+---
+
+# Upgrade Check Operator HTTP API
+
+The `/operator/upgrade-check` endpoints provide some predefined verifications
+that can be useful prior to upgrades and changes to Nomad configuration.
+
+<Note>
+
+These endpoints are meant to target specific releases of Nomad and may be
+removed or modified without notice.
+
+</Note>
+
+## Vault Workload Identity
+
+This endpoint retrieves jobs, nodes, and Vault ACL tokens that may be affected
+when migrating a Nomad cluster to use [workload identities for
+Vault][nomad_acl_vault_wid].
+
+| Method | Path                                                 | Produces           |
+| ------ | ---------------------------------------------------- | ------------------ |
+| `GET`  | `/v1/operator/upgrade-check/vault-workload-identity` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required    |
+| ---------------- | --------------- |
+| `NO`             | `operator:read` |
+
+### Sample Request
+
+```shell-session
+$ nomad operator api \
+    /v1/operator/upgrade-check/vault-workload-identity
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 20,
+  "JobsWithoutVaultIdentity": [
+    {
+      "CreateIndex": 11,
+      "Datacenters": [
+        "*"
+      ],
+      "ID": "example",
+      "JobModifyIndex": 11,
+      "JobSummary": null,
+      "ModifyIndex": 19,
+      "Multiregion": null,
+      "Name": "example",
+      "Namespace": "default",
+      "NodePool": "default",
+      "ParameterizedJob": false,
+      "ParentID": "",
+      "Periodic": false,
+      "Priority": 50,
+      "Status": "running",
+      "StatusDescription": "",
+      "Stop": false,
+      "SubmitTime": 1704995322434188000,
+      "Type": "service"
+    }
+  ],
+  "KnownLeader": true,
+  "LastContact": 0,
+  "NextToken": "",
+  "OutdatedNodes": [
+    {
+      "Address": "192.168.0.186",
+      "CreateIndex": 8,
+      "Datacenter": "dc1",
+      "Drain": false,
+      "Drivers": {
+        "qemu": {
+          "Attributes": {
+            "driver.qemu": "true",
+            "driver.qemu.version": "8.1.1"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.993541-05:00"
+        },
+        "exec": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "exec driver unsupported on client OS",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.958495-05:00"
+        },
+        "raw_exec": {
+          "Attributes": {
+            "driver.raw_exec": "true"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.958539-05:00"
+        },
+        "java": {
+          "Attributes": {},
+          "Detected": false,
+          "HealthDescription": "",
+          "Healthy": false,
+          "UpdateTime": "2024-01-11T12:48:35.97141-05:00"
+        },
+        "docker": {
+          "Attributes": {
+            "driver.docker.bridge_ip": "172.17.0.1",
+            "driver.docker.runtimes": "io.containerd.runc.v2,runc",
+            "driver.docker.os_type": "linux",
+            "driver.docker": "true",
+            "driver.docker.version": "24.0.7"
+          },
+          "Detected": true,
+          "HealthDescription": "Healthy",
+          "Healthy": true,
+          "UpdateTime": "2024-01-11T12:48:35.989993-05:00"
+        }
+      },
+      "HostVolumes": null,
+      "ID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "LastDrain": null,
+      "ModifyIndex": 10,
+      "Name": "client-1",
+      "NodeClass": "",
+      "NodePool": "default",
+      "SchedulingEligibility": "eligible",
+      "Status": "ready",
+      "StatusDescription": "",
+      "Version": "1.6.4"
+    }
+  ],
+  "VaultTokens": [
+    {
+      "Accessor": "czh9MPcRXzAhxBL9XKyb3Kh1",
+      "AllocID": "f00893d4-d9ef-4937-6a7a-ab495b68a971",
+      "CreateIndex": 14,
+      "CreationTTL": 60,
+      "NodeID": "049f7683-0cde-727f-428a-913a89f92bd8",
+      "Task": "redis"
+    }
+  ]
+}
+```
+
+#### Field Reference
+
+- `JobsWithoutVaultIdentity` `(array<Job>)` - The list of jobs that have a
+  [`vault`][] block but do not have an [`identity`][] for Vault
+  authentication. These jobs can fail if they are not redeployed with an
+  identity for Vault before the configuration for Nomad servers are updated and
+  their access to Vault is removed.
+
+- `OutdatedNodes` `(array<Node>)` - The list of nodes running a version of
+  Nomad that does not support workload identity authentication for Vault.
+  Allocations placed in these nodes will use the deprecated legacy flow to
+  retrieve Vault tokens. If the Nomad servers configuration is update to remove
+  their access to Vault before these nodes are upgraded, these allocations will
+  fail. Allocations that use workload identity for Vault will not be able to be
+  placed in these nodes until they are upgraded.
+
+- `VaultTokens` `(array<VaultAccessor>)` - The list of Vault ACL tokens created
+  by Nomad servers using the deprecated legacy flow. They will continue to work
+  even after the migration to the workload identities, but they may not be
+  automatically revoked by Nomad and will only expire once their TTL reaches
+  zero.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+[`identity`]: /nomad/docs/job-specification/identity
+[`vault`]: /nomad/docs/job-specification/vault
+[nomad_acl_vault_wid]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.9.x/content/api-docs/plugins.mdx b/content/nomad/v1.9.x/content/api-docs/plugins.mdx
new file mode 100644
index 0000000000..64ac21f232
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/plugins.mdx
@@ -0,0 +1,139 @@
+---
+layout: api
+page_title: Plugins - HTTP API
+description: The `/plugin` endpoints are used to query for and interact with dynamic plugins.
+---
+
+# Plugins HTTP API
+
+The `/plugin` endpoints are used to query for and interact with
+dynamic plugins. Currently only Container Storage Interface (CSI)
+plugins are dynamic.
+
+## List Plugins
+
+This endpoint lists all dynamic plugins.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/plugins` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+|------------------|---------------|
+| `YES`            | `plugin:read` |
+
+### Parameters
+
+- `type` `(string: "")`- Specifies the type of plugin to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugins?type=csi
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example",
+    "Provider": "aws.ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 2,
+    "ControllersExpected": 3,
+    "NodesHealthy": 14,
+    "NodesExpected": 16,
+    "CreateIndex": 52,
+    "ModifyIndex": 93
+  }
+]
+```
+
+## Read Plugin
+
+Get details of a single plugin, including information about the
+plugin's job and client fingerprint data.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/plugin/csi/:plugin_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+|------------------|-----------------------------------------------------------------|
+| `YES`            | `plugin:read`,                                                  |
+|                  | `namespace:*`<br />Allocations listed are filtered by namespace |
+
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/plugin/csi/example_plugin_id
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "example_plugin_id",
+    "Provider": "aws.ebs",
+    "Version": "1.0.1",
+    "ControllersRequired": true,
+    "ControllersHealthy": 1,
+    "Controllers": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-31T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "ControllerInfo": {
+          "SupportsReadOnlyAttach": true,
+          "SupportsAttachDetach": true,
+          "SupportsListVolumes": true,
+          "SupportsListVolumesAttachedNodes": false
+        }
+      }
+    },
+    "NodesHealthy": 1,
+    "Nodes": {
+      "example_node_id": {
+        "PluginID": "example_plugin_id",
+        "Provider": "aws.ebs",
+        "ProviderVersion": "1.0.1",
+        "AllocID": "alloc-id",
+        "Healthy": true,
+        "HealthDescription": "healthy",
+        "UpdateTime": "2020-01-30T00:00:00.000Z",
+        "RequiresControllerPlugin": true,
+        "RequiresTopologies": true,
+        "NodeInfo": {
+          "ID": "example_node_id",
+          "MaxVolumes": 51,
+          "AccessibleTopology": {
+            "key": "val2"
+          },
+          "RequiresNodeStageVolume": true
+        }
+      }
+    }
+  }
+]
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/quotas.mdx b/content/nomad/v1.9.x/content/api-docs/quotas.mdx
new file mode 100644
index 0000000000..1187f6c178
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/quotas.mdx
@@ -0,0 +1,421 @@
+---
+layout: api
+page_title: Quotas - HTTP API
+description: The /quota endpoints are used to query for and interact with quotas.
+---
+
+# Quota HTTP API
+
+The `/quota` endpoints are used to query for and interact with quotas.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Quota Specifications
+
+This endpoint lists all quota specifications.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/quotas` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quotas?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+    "Limits": [
+      {
+        "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 2500,
+          "Cores": 0,
+          "Devices": [
+            {
+              "Affinities": null,
+              "Constraints": null,
+              "Count": 1,
+              "Name": "nvidia/gpu/Tesla M60"
+            }
+          ],
+          "DiskMB": 0,
+          "IOPS": 0,
+          "MemoryMB": 2000,
+          "MemoryMaxMB": 2000,
+          "NUMA": null,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 1000
+      }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+  }
+]
+```
+
+## Read Quota Specification
+
+This endpoint reads information about a specific quota specification.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 11,
+  "Description": "Limit the shared default namespace",
+  "Hash": "uTIBStF55xKqUMGdI23rdP+W+hsvZ2WEfRWU11j7CzQ=",
+  "Limits": [
+    {
+      "Hash": "fTSnZHxUyDQcRT2Q7L3Hlu3vWpwSt0LWu7JVd3neK9k=",
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "Cores": 0,
+        "Devices": [
+          {
+            "Affinities": null,
+            "Constraints": null,
+            "Count": 1,
+            "Name": "nvidia/gpu/Tesla M60"
+          }
+        ],
+        "DiskMB": 0,
+        "IOPS": 0,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "NUMA": null,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 1000
+    }
+  ],
+  "ModifyIndex": 11,
+  "Name": "default-quota"
+}
+```
+
+## Create or Update Quota Specification
+
+This endpoint is used to create or update a quota specification.
+
+| Method | Path                                  | Produces           |
+| ------ | ------------------------------------- | ------------------ |
+| `POST` | `/v1/quota/:quota` <br /> `/v1/quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Body
+
+The request body contains a valid, JSON quota specification. View the api
+package to see the definition of a [`QuotaSpec`
+object](https://pkg.go.dev/github.com/hashicorp/nomad/api#QuotaSpec).
+
+### Sample Payload
+
+```javascript
+{
+  "Name": "default-quota",
+  "Description": "Limit the shared default namespace",
+  "Limits": [
+    {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 2500,
+        "MemoryMB": 2000,
+        "MemoryMaxMB": 2000,
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1
+          }
+        ],
+        "VariablesLimit": 1000
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @spec.json \
+    https://localhost:4646/v1/quota
+```
+
+## Delete Quota Specification
+
+This endpoint is used to delete a quota specification.
+
+| Method   | Path               | Produces           |
+| -------- | ------------------ | ------------------ |
+| `DELETE` | `/v1/quota/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required  |
+| ---------------- | ------------- |
+| `NO`             | `quota:write` |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to delete
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/quota/shared-quota
+```
+
+## List Quota Usages
+
+This endpoint lists all quota usages.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `GET`  | `/v1/quota-usages` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `prefix` `(string: "")`- Specifies a string to filter quota specifications on
+  based on an index prefix. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota-usages?prefix=sha
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Used": {
+      "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+        "Region": "global",
+        "RegionLimit": {
+          "CPU": 500,
+          "Cores": 0,
+          "MemoryMB": 256,
+          "MemoryMaxMB": 256,
+          "DiskMB": 0,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "CIDR": "",
+              "Device": "",
+              "DynamicPorts": null,
+              "IP": "",
+              "MBits": 50,
+              "Mode": "",
+              "ReservedPorts": null
+            }
+          ],
+          "Devices": [
+            {
+              "Name": "nvidia/gpu/Tesla M60",
+              "Count": 1,
+              "Constraints": null,
+              "Affinities": null
+            }
+          ],
+          "NUMA": null,
+          "SecretsMB": 0
+        },
+        "VariablesLimit": 0,
+        "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+      }
+    },
+    "Name": "default-quota",
+    "CreateIndex": 11,
+    "ModifyIndex": 38
+  }
+]
+```
+
+## Read Quota Usage
+
+This endpoint reads information about a specific quota usage.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/v1/quota/usage/:quota` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                    |
+| ---------------- | --------------------------------------------------------------- |
+| `YES`            | `quota:read`<br />`namespace:*` if namespace has quota attached |
+
+### Parameters
+
+- `:quota` `(string: <required>)`- Specifies the quota specification to query
+  where the identifier is the quota's name.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/quota/usage/shared-quota
+```
+
+### Sample Response
+
+```json
+{
+  "Used": {
+    "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc=": {
+      "Region": "global",
+      "RegionLimit": {
+        "CPU": 500,
+        "Cores": 0,
+        "MemoryMB": 256,
+        "MemoryMaxMB": 256,
+        "DiskMB": 0,
+        "IOPS": 0,
+        "Networks": [
+          {
+            "CIDR": "",
+            "Device": "",
+            "DynamicPorts": null,
+            "IP": "",
+            "MBits": 50,
+            "Mode": "",
+            "ReservedPorts": null
+          }
+        ],
+        "Devices": [
+          {
+            "Name": "nvidia/gpu/Tesla M60",
+            "Count": 1,
+            "Constraints": null,
+            "Affinities": null
+          }
+        ],
+        "NUMA": null,
+        "SecretsMB": 0
+      },
+      "VariablesLimit": 0,
+      "Hash": "+kpaU440830Btn3/a0VUL4ROJCQyBOE55xwRR8rlFpc="
+    }
+  },
+  "Name": "default-quota",
+  "CreateIndex": 11,
+  "ModifyIndex": 38
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/recommendations.mdx b/content/nomad/v1.9.x/content/api-docs/recommendations.mdx
new file mode 100644
index 0000000000..ccb3a97a13
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/recommendations.mdx
@@ -0,0 +1,373 @@
+---
+layout: api
+page_title: Recommendations - HTTP API
+description: >-
+  The /recommendation endpoints are used to query for and interact with Dynamic
+  Application Sizing recommendations.
+---
+
+# Recommendation HTTP API
+
+The `/recommendation` endpoints are used to query and interact with Dynamic
+Application Sizing recommendations.
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Recommendations
+
+This endpoint lists all the currently available recommendations and provides
+optional filtering of that list.
+
+| Method | Path                  | Produces           |
+| ------ | --------------------- | ------------------ |
+| `GET`  | `/v1/recommendations` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                        |
+| ---------------- | ----------------------------------------------------------------------------------- |
+| `YES`            | `namespace:read-job` or `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `group` `(string: "")` - Specifies the task group name to filter within a job. If
+  specified, the `job` parameter must also be specified.
+
+- `job` `(string: "")` - Specifies the job ID to filter the recommendations list by.
+
+- `namespace` `(string: "default")` - Specifies the namespace to search. Specifying
+  `*` would return all recommendations across all the authorized namespaces.
+
+- `task` `(string: "")` - Specifies the task name to filter within a job and task
+  group. If specified, the `job` and `group` query parameters must also be
+  specified.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendations?namespace=*&job=example&group=cache&task=redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "MemoryMB",
+    "Value": 10,
+    "Current": 200,
+    "Meta": {
+      "nomad_autoscaler.count.capped": true,
+      "nomad_autoscaler.count.original": 6,
+      "nomad_autoscaler.reason_history": [],
+      "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+      "num_evaluated_windows": 1148,
+      "window_size": 300000000000
+    },
+    "Stats": {
+      "min": 2.6640625,
+      "p99": 6.51171875,
+      "max": 6.515625,
+      "mean": 4.816847859995009
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372587714807000,
+    "CreateIndex": 5193,
+    "ModifyIndex": 10437
+  },
+  {
+    "ID": "fdd2b5f1-e6ad-110e-75b9-8f9410e1d8ab",
+    "Region": "global",
+    "Namespace": "default",
+    "JobID": "example",
+    "JobVersion": 0,
+    "Group": "cache",
+    "Task": "redis",
+    "Resource": "CPU",
+    "Value": 57,
+    "Current": 500,
+    "Meta": {
+      "window_size": 300000000000,
+      "nomad_policy_id": "b2c64295-4315-2fdc-6158-a27156808729",
+      "num_evaluated_windows": 1117
+    },
+    "Stats": {
+      "min": 0,
+      "p99": 50,
+      "max": 63.46186447143555,
+      "mean": 0.3649455045779875
+    },
+    "EnforceVersion": false,
+    "SubmitTime": 1603372287894356000,
+    "CreateIndex": 5275,
+    "ModifyIndex": 10419
+  }
+]
+```
+
+## Read Recommendation
+
+This endpoint reads information about a specific recommendation.
+
+| Method | Path                                    | Produces           |
+| ------ | --------------------------------------- | ------------------ |
+| `GET`  | `/v1/recommendation/:recommendation_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Parameters
+
+- `:recommendation_id` `(string: <required>)`- Specifies the recommendation ID to
+  query. This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/recommendation/cb80a13d-20d8-fb05-db3f-4ea0fe667b1b
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "cb80a13d-20d8-fb05-db3f-4ea0fe667b1b",
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 10,
+  "Current": 200,
+  "Meta": {
+    "nomad_autoscaler.count.original": 6,
+    "nomad_autoscaler.reason_history": [],
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "num_evaluated_windows": 1148,
+    "window_size": 300000000000,
+    "nomad_autoscaler.count.capped": true
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  },
+  "EnforceVersion": false,
+  "SubmitTime": 1603372587714807000,
+  "CreateIndex": 5193,
+  "ModifyIndex": 10437
+}
+```
+
+## Apply and Dismiss Recommendations
+
+This endpoint is used to apply and dismiss recommendations.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `POST` | `/v1/recommendations/apply` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                                      |
+| ---------------- | --------------------------------------------------------------------------------- |
+| `NO`             | `namespace:submit-job` with `namespace:sentinel-override` if `PolicyOverride` set |
+
+### Parameters
+
+- `Apply` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  applied. This results in Nomad applying the recommendation to the job
+  specification and performing a job register.
+
+- `Dismiss` `(array<string>: nil)` - Specifies a set of recommendation IDs to be
+  dismissed. This results in Nomad deleting them from the state store.
+
+- `PolicyOverride` `(bool: false)` - If set, any soft mandatory Sentinel policies
+  will be overridden. This allows a recommendation to be applied when it would be
+  denied by a policy.
+
+### Sample Payload
+
+```json
+{
+  "Apply": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendations/apply
+```
+
+### Sample Response
+
+```json
+{
+  "Errors": [],
+  "LastIndex": 0,
+  "RequestTime": 0,
+  "UpdatedJobs": [
+    {
+      "EvalCreateIndex": 51,
+      "EvalID": "3c91a755-f314-e2fb-500b-437ad08e13ea",
+      "JobID": "example",
+      "JobModifyIndex": 51,
+      "Namespace": "default",
+      "Recommendations": ["cb80a13d-20d8-fb05-db3f-4ea0fe667b1b"],
+      "Warnings": ""
+    }
+  ]
+}
+```
+
+## Create or Update a Recommendation
+
+This endpoint is used to create or update a recommendation.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `POST` | `/v1/recommendation` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                                                |
+| ---------------- | ----------------------------------------------------------- |
+| `NO`             | `namespace:submit-recommendation` or `namespace:submit-job` |
+
+### Parameters
+
+- `ID` `(string: "")` - The ID of an existing recommendation to update.
+
+- `Region` `(string: "")`- The Nomad region identifier which contains the job
+  that the recommendation is for. If omitted, this defaults to that of the Nomad
+  agent.
+
+- `Namespace` `(string: "")`- The namespace within which the target job is running
+  within. If omitted, this defaults to `default`.
+
+- `JobID` `(string: <required>)`- The job ID which this recommendation is for.
+
+- `Group` `(string: <required>)`- The task group name within the job which this
+  recommendation is for.
+
+- `Task` `(string: <required>)`- The task name within the task group which this
+  recommendation is for.
+
+- `Resource` `(string: <required>)`- The resource that the recommendation is for.
+  Possible values are `CPU` and `MemoryMB`.
+
+- `Value` `(int: <required>)`- The value recommendation for the resource. This
+  must met the minimum requirements which are `1` for `CPU` and `10` for `MemoryMB`.
+
+- `Meta` `(map<string|...>: nil)`- JSON block that is persisted as part of the
+  recommendation providing arbitrary, useful information.
+
+- `Stats` `(map<string|float64>: nil)` - A mapping of statistics that are persisted
+  as part of the recommendation providing insight into the recommendation
+  calculation.
+
+- `EnforceVersion` `(bool: false)`- Indicates that the recommendation is only valid
+  for the current version of the job. Subsequent job updates will automatically
+  dismiss this recommendation.
+
+### Sample Payload
+
+```json
+{
+  "Region": "global",
+  "Namespace": "default",
+  "JobID": "example",
+  "Group": "cache",
+  "Task": "redis",
+  "Resource": "MemoryMB",
+  "Value": 512,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "Stats": {
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625,
+    "mean": 4.816847859995009
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/recommendation
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 22,
+  "Current": 256,
+  "EnforceVersion": false,
+  "Group": "cache",
+  "ID": "47c97404-918f-8b19-873b-36d802f16f23",
+  "JobID": "example",
+  "JobVersion": 0,
+  "Meta": {
+    "nomad_policy_id": "c355d0ec-7aa1-2604-449d-4ec79c813d2c"
+  },
+  "ModifyIndex": 25,
+  "Namespace": "default",
+  "Region": "global",
+  "Resource": "MemoryMB",
+  "Stats": {
+    "mean": 4.816847859995009,
+    "min": 2.6640625,
+    "p99": 6.51171875,
+    "max": 6.515625
+  },
+  "SubmitTime": 1603444202372926000,
+  "Task": "redis",
+  "Value": 512
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/regions.mdx b/content/nomad/v1.9.x/content/api-docs/regions.mdx
new file mode 100644
index 0000000000..5d76fc20a9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/regions.mdx
@@ -0,0 +1,36 @@
+---
+layout: api
+page_title: Regions - HTTP API
+description: The /regions endpoints list all known regions.
+---
+
+# Regions HTTP API
+
+The `/regions` endpoints list all known regions.
+
+## List Regions
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/regions` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/regions
+```
+
+### Sample Response
+
+```json
+["region1", "region2"]
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/scaling-policies.mdx b/content/nomad/v1.9.x/content/api-docs/scaling-policies.mdx
new file mode 100644
index 0000000000..5c1c285e36
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/scaling-policies.mdx
@@ -0,0 +1,150 @@
+---
+layout: api
+page_title: Scaling Policies - HTTP API
+description: The /scaling/policy endpoints are used to list and view scaling policies.
+---
+
+# Scaling Policies HTTP API
+
+The `/scaling/policies` and `/scaling/policy/` endpoints are used to list and view scaling policies.
+
+## List Scaling Policies
+
+This endpoint returns the scaling policies from all jobs.
+
+| Method | Path                | Produces           |
+| ------ | ------------------- | ------------------ |
+| `GET`  | `/scaling/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                      |
+| ---------------- | ----------------- | --------------------------------- |
+| `YES`            | `all`             | `namespace:list-scaling-policies` |
+
+### Parameters
+
+- `job` `(string: "")`- Specifies the job ID to filter policies by.
+
+- `type` `(string: "")` - Specifies the type of scaling policy to filter by. In
+  the open source version of Nomad, `horizontal` is the only supported value.
+  Within Nomad Enterprise, `vertical_mem` and `vertical_cpu` are supported along
+  with `vertical`. The latter returns policies matching both `vertical_mem` and
+  `vertical_cpu`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?job=example
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policies?type=vertical
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "b2c64295-4315-2fdc-6158-a27156808729",
+    "Enabled": true,
+    "Type": "vertical_cpu",
+    "Target": {
+      "Namespace": "default",
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "c355d0ec-7aa1-2604-449d-4ec79c813d2c",
+    "Enabled": true,
+    "Type": "vertical_mem",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Task": "redis",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1340,
+    "ModifyIndex": 1340
+  },
+  {
+    "ID": "31a53813-24df-b2ad-77dc-1b4bad4e7dca",
+    "Enabled": true,
+    "Type": "horizontal",
+    "Target": {
+      "Job": "example",
+      "Group": "cache",
+      "Namespace": "default"
+    },
+    "CreateIndex": 1358,
+    "ModifyIndex": 1358
+  }
+]
+```
+
+## Read Scaling Policy
+
+This endpoint reads a specific scaling policy.
+
+| Method | Path                         | Produces           |
+| ------ | ---------------------------- | ------------------ |
+| `GET`  | `/scaling/policy/:policy_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required                    |
+| ---------------- | ----------------- | ------------------------------- |
+| `YES`            | `all`             | `namespace:read-scaling-policy` |
+
+### Parameters
+
+- `:policy_id` `(string: <required>)` - Specifies the ID of the scaling policy (as returned
+  by the scaling policy list endpoint). This is specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/scaling/policy/5e9f9ef2-5223-6d35-bac1-be0f3cb974ad
+```
+
+### Sample Response
+
+```json
+{
+  "CreateIndex": 10,
+  "Enabled": true,
+  "ID": "5e9f9ef2-5223-6d35-bac1-be0f3cb974ad",
+  "Type": "horizontal",
+  "Max": 10,
+  "Min": 0,
+  "ModifyIndex": 10,
+  "Policy": {
+    "engage": true,
+    "foo": "bar",
+    "howdy": "doody",
+    "value": 6.0
+  },
+  "Target": {
+    "Group": "cache",
+    "Job": "example",
+    "Namespace": "default"
+  }
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/search.mdx b/content/nomad/v1.9.x/content/api-docs/search.mdx
new file mode 100644
index 0000000000..247ed39453
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/search.mdx
@@ -0,0 +1,638 @@
+---
+layout: api
+page_title: Search - HTTP API
+description: The /search endpoint is used to search for Nomad objects
+---
+
+# Search HTTP API
+
+## Prefix Searching
+
+The `/search` endpoint returns matches for a given prefix and context, where a
+context can be jobs, allocations, evaluations, nodes, node pools, deployments,
+plugins, namespaces, or volumes. When using Nomad Enterprise, the allowed
+contexts include quotas. Additionally, a prefix can be searched for within
+every context.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `POST` | `/v1/search` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Prefix` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given prefix were "a", potential
+  matches might be "abcd", or "aabb".
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "evals", "allocs", "nodes",
+  "node_pools", "deployment", "plugins", "volumes" or "all", where "all" means
+  every context will be searched.
+
+### Sample Payload (for all contexts)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "allocs": null,
+    "deployment": null,
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"],
+    "jobs": ["abcde"],
+    "nodes": null,
+    "plugins": null,
+    "volumes": null
+  },
+  "Truncations": {
+    "allocs": "false",
+    "deployment": "false",
+    "evals": "false",
+    "jobs": "false",
+    "nodes": "false",
+    "plugins": "false",
+    "volumes": "false"
+  }
+}
+```
+
+#### Field Reference
+
+- `Matches` - A map of contexts to matching arrays of identifiers.
+
+- `Truncations` - Search results are capped at 20; if more matches were found for a particular context, it will be `true`.
+
+### Sample Payload (for a specific context)
+
+```json
+{
+  "Prefix": "abc",
+  "Context": "evals"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search
+```
+
+### Sample Response
+
+```json
+{
+  "Matches": {
+    "evals": ["abc2fdc0-e1fd-2536-67d8-43af8ca798ac"]
+  },
+  "Truncations": {
+    "evals": "false"
+  }
+}
+```
+
+## Fuzzy Searching
+
+The `/search/fuzzy` endpoint returns partial substring matches for a given
+search term and context, where a context can be jobs, allocations, nodes, node
+pools, plugins, or namespaces. Additionally, fuzzy searching can be done across
+all contexts. For better control over the performance implications of fuzzy
+searching on Nomad servers, aspects of fuzzy searching can be tuned through
+the <code>[search]</code> block in Nomad agent config.
+
+Fuzzy search results are ordered starting with closest matching terms. Items of
+a name that exactly matches the search term are listed first.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/search/fuzzy` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+|------------------|--------------|
+| `NO`             | see below    |
+
+When ACLs are enabled, requests must have a token that grants access to "list"
+or "read" capabilities for the objects in the search context. For example,
+`node:read`, `node_pool:read`, `plugin:read`, or `namespace:read-jobs` roles. If
+the token is only valid for a portion of these capabilities, then results will
+include results including only data readable with the given token.
+
+### Parameters
+
+- `Text` `(string: <required>)` - Specifies the identifier against which
+  matches will be found. For example, if the given text were "py", potential
+  fuzzy matches might be "python", "spying", or "happy".
+
+- `Context` `(string: <required>)` - Defines the scope in which a search for a
+  prefix operates. Contexts can be: "jobs", "allocs", "nodes", "node_pools",
+  "plugins", or "all", where "all" means every context will be searched. When
+  "all" is selected, additional prefix matches will be included for the
+  "deployments", "evals", and "volumes" types. When searching in the "jobs"
+  context, results that fuzzy match "groups", "services", "tasks", "images",
+  "commands", and "classes" are also included in the results.
+
+### Scope
+
+Fuzzy match results are accompanied with a `Scope` field which is used to uniquely
+identify the matched object, in a way that the Nomad API can be queried again for
+additional information. The data provided by scope varies depending on the type
+of matched object, described below.
+
+### Sample Payload (for jobs)
+
+```json
+{
+  "Text": "py",
+  "Context": "jobs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 90,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "jobs": false
+  }
+}
+```
+
+#### Scope (jobs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (groups)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+
+#### Scope (tasks)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+
+#### Scope (group services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Group
+
+#### Scope (task services)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+#### Scope (commands/images/classes)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Job ID
+- `Scope[2]` : Group
+- `Scope[3]` : Task
+
+### Sample Payload (for nodes)
+
+```json
+{
+  "Text": "lab",
+  "Context": "nodes"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "nodes": [
+      {
+        "ID": "nomad-lab1",
+        "Scope": [
+          "c48cd39f-dfe1-9cc0-9c62-617d199854be"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (nodes)
+
+- `Scope[0]` : Node ID
+
+### Sample Payload (for node pools)
+
+```json
+{
+  "Text": "lab",
+  "Context": "node_pools"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 9,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "node_pools": [
+      {
+        "ID": "dev-lab1",
+        "Scope": [
+          "dev-lab1"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "nodes": false
+  }
+}
+```
+
+##### Scope (node pools)
+
+- `Scope[0]` : Node Pool Name
+
+### Sample Payload (for allocs)
+
+```json
+{
+   "Text":"py",
+   "Context":"allocs"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 136,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "0fb703d1-ba4d-116f-13aa-27f31f046858"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "allocs": false
+  }
+}
+```
+
+#### Scope (allocs)
+
+- `Scope[0]` : Namespace
+- `Scope[1]` : Alloc ID
+
+
+### Sample Payload (for plugins)
+
+```json
+{
+  "Text": "aws",
+  "Context": "plugins"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 0,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "plugins": [
+      {
+        "ID": "aws-efs0"
+      }
+    ]
+  },
+  "Truncations": {
+    "plugins": false
+  }
+}
+```
+
+### Sample Payload (for all)
+
+```json
+{
+  "Index": 260,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "services": [
+      {
+        "ID": "python-logger",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      },
+      {
+        "ID": "super-spy-service",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "tasks": [
+      {
+        "ID": "my-python-task",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app"
+        ]
+      }
+    ],
+    "jobs": [
+      {
+        "ID": "example-python",
+        "Scope": [
+          "default"
+        ]
+      }
+    ],
+    "evals": [],
+    "scaling_policy": [],
+    "groups": [
+      {
+        "ID": "my-spy-app",
+        "Scope": [
+          "default",
+          "example-python"
+        ]
+      }
+    ],
+    "images": [
+      {
+        "ID": "python:3",
+        "Scope": [
+          "default",
+          "example-python",
+          "my-spy-app",
+          "my-python-task"
+        ]
+      }
+    ],
+    "plugins": [
+      {
+        "ID": "aws-spy-plugin"
+      }
+    ],
+    "deployment": [],
+    "volumes": [],
+    "allocs": [
+      {
+        "ID": "example-python.my-spy-app[0]",
+        "Scope": [
+          "default",
+          "48608246-4c28-0446-f3d1-c67e3bc650ad"
+        ]
+      }
+    ]
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Prefix matching when fuzzy searching
+
+If the search Context is `all` when fuzzy searching, the object types that are
+identified only with UUIDs are also concurrently prefix-searched. Those types include
+deployments, evals, volumes, and quotas (Enterprise).
+
+### Sample Payload (prefix match)
+
+```json
+{
+   "Text":"cc",
+   "Context":"all"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/search/fuzzy
+```
+
+### Sample Result
+```json
+{
+  "Index": 267,
+  "KnownLeader": true,
+  "LastContact": 0,
+  "Matches": {
+    "scaling_policy": [],
+    "evals": [],
+    "deployment": [
+      {
+        "ID": "cc786388-e071-31ec-5821-b829839f9681"
+      }
+    ],
+    "volumes": []
+  },
+  "Truncations": {
+    "deployment": false,
+    "volumes": false,
+    "plugins": false,
+    "namespaces": false,
+    "scaling_policy": false,
+    "evals": false,
+    "allocs": false,
+    "jobs": false,
+    "nodes": false
+  }
+}
+```
+
+[search]: /nomad/docs/configuration/search
diff --git a/content/nomad/v1.9.x/content/api-docs/sentinel-policies.mdx b/content/nomad/v1.9.x/content/api-docs/sentinel-policies.mdx
new file mode 100644
index 0000000000..e346230d7d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/sentinel-policies.mdx
@@ -0,0 +1,179 @@
+---
+layout: api
+page_title: Sentinel Policies - HTTP API
+description: >-
+  The /sentinel/policy/ endpoints are used to configure and manage Sentinel
+  policies.
+---
+
+# Sentinel Policies HTTP API
+
+The `/sentinel/policies` and `/sentinel/policy/` endpoints are used to manage Sentinel policies.
+For more details about Sentinel policies, please see the [Sentinel Policy Guide](/nomad/tutorials/governance-and-policy/sentinel).
+
+Sentinel endpoints are only available when ACLs are enabled. For more details about ACLs, please see the [ACL Guide](/nomad/tutorials/access-control).
+
+<EnterpriseAlert>
+  This API endpoint and functionality only exists in Nomad Enterprise. This is
+  not present in the open source version of Nomad.
+</EnterpriseAlert>
+
+## List Policies
+
+This endpoint lists all Sentinel policies. This lists the policies that have been replicated
+to the region, and may lag behind the authoritative region.
+
+| Method | Path                 | Produces           |
+| ------ | -------------------- | ------------------ |
+| `GET`  | `/sentinel/policies` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policies
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Name": "foo",
+    "Description": "test policy",
+    "Scope": "submit-job",
+    "EnforcementLevel": "advisory",
+    "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+    "CreateIndex": 8,
+    "ModifyIndex": 8
+  }
+]
+```
+
+## Create or Update Policy
+
+This endpoint creates or updates an Sentinel Policy. This request is always forwarded to the
+authoritative region.
+
+| Method | Path                            | Produces       |
+| ------ | ------------------------------- | -------------- |
+| `POST` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `Name` `(string: <required>)` - Specifies the name of the policy.
+  Creates the policy if the name does not exist, otherwise updates the existing policy.
+
+- `Description` `(string: <optional>)` - Specifies a human readable description.
+
+- `Scope` `(string: <required>)` - Specifies the scope of when this policy applies. Only `submit-job` is currently supported.
+
+- `EnforcementLevel` `(string: <required>)` - Specifies the enforcement level of the policy. Can be `advisory` which warns on failure,
+  `hard-mandatory` which prevents an operation on failure, and `soft-mandatory` which is like `hard-mandatory` but can be overridden.
+
+- `Policy` `(string: <required>)` - Specifies the Sentinel policy itself.
+
+### Sample Payload
+
+```json
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }"
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/sentinel/policy/my-policy
+```
+
+## Read Policy
+
+This endpoint reads a Sentinel policy with the given name. This queries the policy that have been
+replicated to the region, and may lag behind the authoritative region.
+
+| Method | Path                            | Produces           |
+| ------ | ------------------------------- | ------------------ |
+| `GET`  | `/sentinel/policy/:policy_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required |
+| ---------------- | ----------------- | ------------ |
+| `YES`            | `all`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
+
+### Sample Response
+
+```json
+{
+  "Name": "foo",
+  "Description": "test policy",
+  "Scope": "submit-job",
+  "EnforcementLevel": "advisory",
+  "Policy": "main = rule { true }\n",
+  "Hash": "CIs8aNX5OfFvo4D7ihWcQSexEJpHp+Za+dHSncVx5+8=",
+  "CreateIndex": 8,
+  "ModifyIndex": 8
+}
+```
+
+## Delete Policy
+
+This endpoint deletes the named Sentinel policy. This request is always forwarded to the
+authoritative region.
+
+| Method   | Path                            | Produces       |
+| -------- | ------------------------------- | -------------- |
+| `DELETE` | `/sentinel/policy/:policy_name` | `(empty body)` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Parameters
+
+- `policy_name` `(string: <required>)` - Specifies the policy name to delete.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/sentinel/policy/foo
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/services.mdx b/content/nomad/v1.9.x/content/api-docs/services.mdx
new file mode 100644
index 0000000000..bbc560eea2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/services.mdx
@@ -0,0 +1,182 @@
+---
+layout: api
+page_title: Services - HTTP API
+description: >-
+  The /service endpoints are used to query and interact with Nomad services.
+---
+
+# Service HTTP API
+
+The `/service` endpoints are used to query and interact with Nomad services.
+
+## List Services
+
+This endpoint lists all the currently available Nomad services.
+
+| Method | Path           | Produces           |
+| ------ | -------------- | ------------------ |
+| `GET`  | `/v1/services` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `YES`            | `namespace:read-job` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services
+```
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/services?namespace=*
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "default",
+    "Services": [
+      {
+        "ServiceName": "example-cache-redis",
+        "Tags": [
+          "cache",
+          "db"
+        ]
+      }
+    ]
+  }
+]
+```
+
+## Read Service
+
+This endpoint reads a specific service.
+
+| Method | Path                     | Produces           |
+| ------ | ------------------------ | ------------------ |
+| `GET`  | `/service/:service_name` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries), [consistency modes](/nomad/api-docs#consistency-modes) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | Consistency Modes | ACL Required         |
+| ---------------- | ----------------- | -------------------- |
+| `YES`            | `all`             | `namespace:read-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. This
+  parameter is used before any `filter` expression is applied.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected service. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of services to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the `next_token`
+  of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+- `choose` `(string: "")` - Specifies the number of services to return and a hash
+  key. Must be in the form `<number>|<key>`. Nomad uses [rendezvous hashing][hash] to deliver
+  consistent results for a given key, and stable results when the number of services
+  changes.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/service/example-cache-redis
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "177160af-26f6-619f-9c9f-5e46d1104395",
+    "CreateIndex": 14,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-177160af-26f6-619f-9c9f-5e46d1104395-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 24,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 29702,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  },
+  {
+    "Address": "127.0.0.1",
+    "AllocID": "ba731da0-6df9-9858-ef23-806e9758a899",
+    "CreateIndex": 35,
+    "Datacenter": "dc1",
+    "ID": "_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db",
+    "JobID": "example",
+    "ModifyIndex": 35,
+    "Namespace": "default",
+    "NodeID": "7406e90b-de16-d118-80fe-60d0f2730cb3",
+    "Port": 27232,
+    "ServiceName": "example-cache-redis",
+    "Tags": [
+      "db",
+      "cache"
+    ]
+  }
+]
+```
+
+## Delete Service Registration
+
+This endpoint is used to delete an individual service registration.
+
+| Method   | Path                                    | Produces           |
+| -------- | --------------------------------------- | ------------------ |
+| `DELETE` | `/v1/service/:service_name/:service_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required           |
+| ---------------- | ---------------------- |
+| `NO`             | `namespace:submit-job` |
+
+### Parameters
+
+- `:service_name` `(string: <required>)` - Specifies the service name. This is
+  specified as part of the path.
+
+- `:service_id` `(string: <required>)` - Specifies the service ID. This is
+  specified as part of the path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/service/example-cache-redis/_nomad-task-ba731da0-6df9-9858-ef23-806e9758a899-redis-example-cache-redis-db
+```
+
+[hash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
\ No newline at end of file
diff --git a/content/nomad/v1.9.x/content/api-docs/status.mdx b/content/nomad/v1.9.x/content/api-docs/status.mdx
new file mode 100644
index 0000000000..455a620582
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/status.mdx
@@ -0,0 +1,67 @@
+---
+layout: api
+page_title: Status - HTTP API
+description: The /status endpoints query the Nomad system status.
+---
+
+# Status HTTP API
+
+The `/status` endpoints query the Nomad system status.
+
+## Read Leader
+
+This endpoint returns the address of the current leader in the region.
+
+| Method | Path             | Produces           |
+| ------ | ---------------- | ------------------ |
+| `GET`  | `/status/leader` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/leader
+```
+
+### Sample Response
+
+```json
+"127.0.0.1:4647"
+```
+
+## List Peers
+
+This endpoint returns the set of raft peers in the region.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `GET`  | `/status/peers` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `none`       |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/status/peers
+```
+
+### Sample Response
+
+```json
+["127.0.0.1:4647"]
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/system.mdx b/content/nomad/v1.9.x/content/api-docs/system.mdx
new file mode 100644
index 0000000000..bb51aa190a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/system.mdx
@@ -0,0 +1,59 @@
+---
+layout: api
+page_title: System - HTTP API
+description: The /system endpoints are used for system maintenance.
+---
+
+# System HTTP API
+
+The `/system` endpoints are used to for system maintenance and should not be
+necessary for most users.
+
+## Force GC
+
+This endpoint initializes a garbage collection of jobs, evaluations, allocations, and
+nodes. This is an asynchronous operation.
+
+| Method | Path            | Produces           |
+| ------ | --------------- | ------------------ |
+| `PUT`  | `/v1/system/gc` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/gc
+```
+
+## Reconcile Summaries
+
+This endpoint reconciles the summaries of all registered jobs.
+
+| Method | Path                             | Produces           |
+| ------ | -------------------------------- | ------------------ |
+| `PUT`  | `/v1/system/reconcile/summaries` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required |
+| ---------------- | ------------ |
+| `NO`             | `management` |
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    https://localhost:4646/v1/system/reconcile/summaries
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/task-api.mdx b/content/nomad/v1.9.x/content/api-docs/task-api.mdx
new file mode 100644
index 0000000000..b4c89d7cbd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/task-api.mdx
@@ -0,0 +1,109 @@
+---
+layout: api
+page_title: Task HTTP API
+description: |-
+  Jobs can access Nomad's HTTP API via the Task API.
+---
+
+# Task API
+
+Nomad's Task API provides every task managed by Nomad with a Unix Domain Socket
+(UDS) to access the local agent's HTTP API. Regardless of agent configuration
+the Task API does *not* require [mTLS][], but *always* requires authentication.
+See below for details.
+
+The Unix Domain Socket is located at `${NOMAD_SECRETS_DIR}/api.sock`.
+
+## Rationale
+
+Nomad's HTTP API is available on every agent at the configured
+[`bind_addr`][bind_addr]. While this is convenient for user access, it is not
+always accessible to workloads running on Nomad. These workloads may have a
+network configuration that makes it impossible to access the agent HTTP
+address, or the agent's HTTP address may be difficult for workloads to discover
+in a way that's portable between Nomad nodes and clusters.
+
+A Unix Domain Socket is a way to expose network services that works with most
+runtimes and operating systems and adds minimal complexity or runtime overhead
+to Nomad.
+
+## Security
+
+Unlike the agent's HTTP API, the Task API *always requires authentication* even
+if [ACLs][acl] are disabled.  This allows Nomad to always make the Task API
+available even if the workload is untrusted. If ACLs are enabled, the [anonymous
+policy][anon] is not available via the Task API.
+
+Both [ACL Tokens][acl-tokens] and [Workload Identities][workload-id] are
+accepted. Once the Task API has authenticated the credentials, the normal
+endpoint-specific authorization is applied when ACLs are enabled.
+
+The Workload Identity should be used by tasks accessing the Task API.
+
+An ACL Token should be used when an operator is accessing the Task API via
+[`nomad alloc exec`][alloc-exec] or when a task is proxying Nomad HTTP requests
+on behalf of an authenticated user. The Task API could be used by a proxy
+presenting Nomad's UI with a standard TLS certificate for browsers.
+
+If [`task.user`][task-user] is set in the jobspec, the Task API will only be
+usable by that user. Otherwise the Unix Domain Socket is accessible by any
+user.
+
+mTLS is never enabled for the Task API since traffic never leaves the node.
+
+## Using the Task API
+
+The following jobspec will use the Task API to set [Dynamic Node Metadata][dnm]
+and exit.
+
+```hcl
+job "taskapi-example" {
+  type = "batch"
+
+  group "taskapi-example" {
+
+    task "taskapi" {
+      driver = "docker"
+
+      config {
+        image = "curlimages/curl:7.87.0"
+        args = [
+          "--unix-socket", "${NOMAD_SECRETS_DIR}/api.sock",
+          "-H", "Authorization: Bearer ${NOMAD_TOKEN}",
+          "--data-binary", "{\"Meta\": {\"example\": \"Hello World!\"}}",
+          "--fail-with-body",
+          "--verbose",
+          "localhost/v1/client/metadata",
+        ]
+      }
+
+      identity {
+        env = true
+      }
+    }
+  }
+}
+```
+
+If the job was able to run successfully after about 10 seconds you can observe
+the outcome by searching for the updated Node's metadata:
+
+```shell-session
+$ nomad node status -filter 'Meta.example == "Hello World!"'
+```
+
+## Limitations
+
+- Using the Task API Unix Domain Socket on Windows [requires][windows] Windows
+build 17063 or later.
+
+[acl]: /nomad/docs/concepts/acl/
+[acl-tokens]: /nomad/docs/concepts/acl/#token
+[alloc-exec]: /nomad/docs/commands/alloc/exec
+[anon]: /nomad/tutorials/access-control/access-control#acl-policies
+[bind_addr]: /nomad/docs/configuration
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[task-user]: /nomad/docs/job-specification/task#user
+[workload-id]: /nomad/docs/concepts/workload-identity
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[dnm]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.9.x/content/api-docs/ui.mdx b/content/nomad/v1.9.x/content/api-docs/ui.mdx
new file mode 100644
index 0000000000..c77bd231ad
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/ui.mdx
@@ -0,0 +1,586 @@
+---
+layout: api
+page_title: UI
+description: The /ui namespace is used to access the Nomad web user interface.
+---
+
+# Nomad Web UI
+
+The Nomad UI is accessible at `/ui`. It is not namespaced by version. A request to `/` will also redirect to `/ui`.
+
+## List Jobs
+
+This page lists all known jobs in a paginated, searchable, and sortable table.
+
+| Path       | Produces    |
+| ---------- | ----------- |
+| `/ui/jobs` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all jobs should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of jobs should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible jobs. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the jobs list that should be visible. This
+  is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of jobs to those with a matching type.
+
+- `status` `(string: "")` - Filters the list of jobs to those with a matching status.
+
+- `dc` `(string: "")` - Filters the list of jobs to those allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of jobs to those with names that start with a matching prefix.
+
+## Job Detail
+
+This page shows an overview of a specific job. Details include name, status, type,
+priority, allocation statuses, and task groups. Additionally, if there is a running
+deployment for the job, it will be shown on the overview.
+
+This page shows an overview of a specific job. The exact information shown varies
+based on the type of job.
+
+- **Service Job** - Includes job metadata (name, status, priority, namespace), allocation
+  statuses, placement failures, active deployment, task groups, and evaluations.
+
+- **Batch Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **System Job** - Includes job metadata, allocation statuses, placement failures, task
+  groups, and evaluations.
+
+- **Periodic Job** - Includes job metadata, cron information force launch action, children statuses,
+  and children list.
+
+- **Parameterized Job** - Includes job metadata, children statuses, and children list.
+
+- **Periodic Child** - Includes job metadata, link to parent job, allocation statuses, placement
+  failures, task groups, and evaluations.
+
+- **Parameterized Child** - Includes job metadata, link to parent job, allocation statuses,
+  placement failures, task groups, evaluations, and dispatch payload.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/jobs/:job_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of task groups should be
+  sorted by. This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the task groups list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Definition
+
+This page shows the definition of a job as pretty-printed, syntax-highlighted, JSON.
+
+| Path                          | Produces    |
+| ----------------------------- | ----------- |
+| `/ui/jobs/:job_id/definition` | `text/html` |
+
+### Job Versions
+
+This page lists all available versions for a job in a timeline view. Each version in
+the timeline can be expanded to show a pretty-printed, syntax-highlighted diff between
+job versions.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/jobs/:job_id/versions` | `text/html` |
+
+### Job Deployments
+
+This page lists all available deployments for a job when the job has deployments. The
+deployments are listed in a timeline view. Each deployment shows pertinent information
+such as deployment ID, status, associated version, and submit time. Each deployment can
+also be expanded to show detail information regarding canary placements, allocation
+placements, healthy and unhealthy allocations, as well the current description for the
+status. A table of task groups is also present in the detail view, which shows allocation
+metrics by task group. Lastly, each expanded deployment lists all associated allocations
+in a table to drill into for task events.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/deployments` | `text/html` |
+
+### Job Allocations
+
+This page lists all allocations for a job in a table view. Each allocation includes status indicators (e.g., rescheduled, preempted, unhealthy driver), ID, a link to the task group detail page, the created timestamp, time since last modified, current status, version, a link to the client the allocation is running on, whether or not it has a volume requirement, the current CPU utilization, and the current memory utilization.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/allocations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+### Job Evaluations
+
+This page lists all evaluations for a job in a table view. Each evaluation includes the evaluation ID, priority, created timestamp, the event that triggered the evaluation, status, and whether or not there are placement failures.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/jobs/:job_id/evaluations` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of evaluations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Task Group Detail
+
+This page shows an overview of a specific task group. Details include the number of tasks, the aggregated amount of reserved CPU, memory, and disk, all associated allocations broken
+down by status, and a list of allocations. The list of allocations include details such as
+status, the client the allocation was placed on, and the current CPU and Memory usage of the
+allocations.
+
+| Path                                | Produces    |
+| ----------------------------------- | ----------- |
+| `/ui/jobs/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Allocation Detail
+
+This page shows details and events for an allocation. Details include the job the allocation
+belongs to, the client the allocation is placed on, a list of all tasks, and lists of task
+events per task. Each task in the task list includes the task name, state, last event, time,
+and addresses. Each task event in a task history list includes the time, type, and
+description of the event.
+
+| Path                        | Produces    |
+| --------------------------- | ----------- |
+| `/ui/allocations/:alloc_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of tasks should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+## Allocation File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the allocation file system. The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Task Detail
+
+This page shows details and events for a specific task. Details include when the task started
+and stopped, all static and dynamic addresses, and all recent events.
+
+| Path                                   | Produces    |
+| -------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name` | `text/html` |
+
+## Task Logs
+
+This page streams `stdout` and `stderr` logs for a task. By default, `stdout` is tailed, but
+there are available actions to see the head of the log, pause and play streaming, and switching
+to `stderr`.
+
+| Path                                        | Produces    |
+| ------------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/:task_name/logs` | `text/html` |
+
+## Task File System
+
+This page will show either a directory listing of a path or the file at a path, depending on whether or not the path is a directory. Specifying no file path will show the root of the task file system (which is within the allocation file system). The file system is also navigible from the UI. Each entry in the directory listing will include the file size (assuming a file) and the last modified time.
+
+If the file is text based, the UI will render the text inline and the stream the file contents as it updates. If the file is a well-known image format, the image will be rendered inline. In all other cases, the UI will prompt a download link.
+
+| Path                                      | Produces    |
+| ----------------------------------------- | ----------- |
+| `/ui/allocations/:alloc_id/fs/:file_path` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of files should be sorted by.
+  This is specified as a query string parameter. Only applies to directories.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter. Only applies to directories.
+
+## Exec Job
+
+This page will show a side bar navigation to traverse the job's task groups and tasks. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path               | Produces    |
+| ------------------ | ----------- |
+| `/ui/exec/:job_id` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task Group
+
+This page will show a side bar navigation to traverse the job's task groups and tasks with the selected task group already open. The majority of this page is a latent terminal window. Using the side bar navigation will transition to the exec task page which establishes a `nomad exec` connection.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into.
+
+## Exec Task
+
+This page will show a side bar navigation to traverse the job's task group's tasks. The majority of this page is a terminal window. The terminal window will be prepopulated with a `nomad exec` command. The specific command used to establish an interactive connection can be modified (e.g., changing `/bin/bash` to `/bin/sh`). Upon submitting the command, a websocket connection is opened to facilitate bidirectional communication between this terminal window and the task running on a Nomad client.
+
+This page is meant to be rendered in a popup window.
+
+| Path                           | Produces    |
+| ------------------------------ | ----------- |
+| `/ui/exec/:job_id/:task_group` | `text/html` |
+
+### Parameters
+
+- `allocation` `(string: "")` - An allocation ID that specifies which allocation to exec into. When not specified, an allocation for the specified task group is chosen at random.
+
+## Clients List
+
+This page lists all clients in the Nomad cluster in a sortable, searchable, paginated
+table.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/clients` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of clients should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible clients . This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the clients list that should be visible. This
+  is specified as a query string parameter.
+
+- `class` `(string: "")` - Filters the list of clients to those with a matching node class.
+
+- `state` `(string: "")` - Filters the list of clients to those with a matching state. Options include `initializing`, `ready`, `down`, `ineligible`, and `draining`.
+
+- `dc` `(string: "")` - Filters the list of clients to those in the specified datacenter.
+
+- `volume` `(string: "")` - Filters the list of clients to those with a matching host volume (by name).
+
+## Client Detail
+
+This page shows the details of a client, including the client name, status, full ID,
+address, port, datacenter, allocations, and attributes.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/clients/:client_id` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+## Client Monitor
+
+This page streams log messages from a client's agent. It is the equivalent to the `nomad monitor` command with `-node-id` set to the client specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/clients/:client_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## Servers List
+
+This page lists all servers in the Nomad cluster in a sortable table. Details for each
+server include the server status, address, port, datacenter, and whether or not it is
+the leader.
+
+| Path          | Produces    |
+| ------------- | ----------- |
+| `/ui/servers` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of server agents should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the server agents list that should be visible. This
+  is specified as a query string parameter.
+
+## Server Detail
+
+This page lists all tags associated with a server.
+
+| Path                     | Produces    |
+| ------------------------ | ----------- |
+| `/ui/servers/:server_id` | `text/html` |
+
+## Server Monitor
+
+This page streams log messages from a server's agent. It is the equivalent to the `nomad monitor` command with `-server-id` set to the server specified in the URL.
+
+| Path                             | Produces    |
+| -------------------------------- | ----------- |
+| `/ui/servers/:server_id/monitor` | `text/html` |
+
+### Parameters
+
+- `level` `(string: "info")` - Specifies the log level to monitor at. Possible values, in order of verbosity, include `trace`, `debug`, `info`, `warn`, and `error`.
+
+## CSI Volumes
+
+This page lists all CSI volumes registered with the Nomad cluster by namespace. Each volume includes the volume name, health, controller plugin health, node plugin health, provider, and number of attached allocations.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/volumes` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all volumes should be a member
+  of. This is specified as a query string parameter.
+
+- `sort` `(string: "")` - Specifies the property the list of volumes should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible volumes. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the volumes list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Volume
+
+This page shows information for a CSI volume. This includes whether or not the volume is available for scheduling, the CSI provider, the external ID, and the namespace. This page also includes a table of constraints (access mode and attachment mode), and tables for all attached allocations in `read` mode and `read/write` mode.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/volumes/:volume_id` | `text/html` |
+
+## CSI Plugins
+
+This page lists all CSI plugins registered with the Nomad cluster. Each plugin includes the plugin ID, controller plugin health, node plugin health, and CSI provider.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of plugins should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible plugins. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the plugins list that should be visible. This
+  is specified as a query string parameter.
+
+## CSI Plugin
+
+This page shows information for a CSI plugin. This includes the proportion of healthy controller allocations, the proportion of healthy node allocations, a table of some controller allocations, and a table of some node allocations. Some of this information may be intentionally omitted based on the type of CSI plugin.
+
+| Path                         | Produces    |
+| ---------------------------- | ----------- |
+| `/ui/csi/plugins/:plugin_id` | `text/html` |
+
+## CSI Plugin Allocations
+
+This page lists all allocations for a CSI plugin. Each allocation includes the standard allocation information (including status indicators, ID, created timestamp, time since last modified, a link to the client the allocation is running on, a link to the job the allocation is for, the job version, volume requirements, current CPU utilization, and current memory utilization) as well as whether or not the allocation is healthy as defined by CSI.
+
+| Path              | Produces    |
+| ----------------- | ----------- |
+| `/ui/csi/plugins` | `text/html` |
+
+### Parameters
+
+- `sort` `(string: "")` - Specifies the property the list of allocations should be sorted by.
+  This is specified as a query string parameter.
+
+- `desc` `(boolean: false)` - Specifies whether or not the sort direction is descending
+  or ascending. This is specified as a query string parameter.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of
+  visible allocations. This is specified as a query string parameter.
+
+- `page` `(int: 1)` - Specifies the page in the allocations list that should be visible. This
+  is specified as a query string parameter.
+
+- `healthy` `(boolean: unset)` - Filters the list of allocations to only those with a matching health value. Value must be `true`, `false`, or unset.
+
+- `type` `(string: "")` - Filters the list of allocations to only those with a matching plugin type. Value must be `controller`, `node`, or unset.
+
+## Optimize
+
+~> **Enterprise Only!** This feature depends on functionality only present in Nomad Autoscaler Enterprise.
+
+This page lists all recommendations surfaced by [dynamic application sizing](/nomad/tools/autoscaling#dynamic-application-sizing). This page will automatically redirect to the recommendation summary route for the first recommendation sorted by relevance.
+
+Each recommendation in the list will contain information including the job and task group the recommendation is for, the time the recommendation was surfaced, the number of allocations impacted, the difference in CPU the recommendation suggests, the difference in memory the recommendation suggests, and the aggregate change in CPU and memory given the number of allocations impacted.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/optimize` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace all recommendations should be a member of. This is specified as a query string parameter.
+
+- `all-namespaces` `(boolean: false)` - Overrides the namespace parameter and returns all recommendations for all namespaces the active ACL token is authorized for.
+
+- `search` `(string: "")` - Specifies a regular expression used to filter the list of visible recommendations. This is specified as a query string parameter.
+
+- `type` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching type.
+
+- `status` `(string: "")` - Filters the list of recommendations to only those for jobs with a matching status.
+
+- `dc` `(string: "")` - Filters the list of recommendations to only those for jobs allowed in a matching datacenter value.
+
+- `prefix` `(string: "")` - Filters the list of recommendations to only those for jobs with names that start with a matching prefix.
+
+## Recommendation Summary
+
+This page includes the same list of recommendations as the optimize route as well as the recommendation card for the job and task group specified in the URL. The recommendation card includes a list of all tasks for the task group as well as toggles for each recommendation available (potentially CPU and memory for each task). The card also shows before, after, and delta values for each recommendation. The before and after values are also presented in a chart that overlays the mean, p99, and max utilization values of the task a recommendation is for.
+
+| Path                                    | Produces    |
+| --------------------------------------- | ----------- |
+| `/ui/optimize/:job_id/:task_group_name` | `text/html` |
+
+### Parameters
+
+- `namespace` `(string: "")` - Specifies the namespace of the job the recommendation is for.
+
+## Topology Visualization
+
+This page includes a visualization of all starting and running allocations grouped by client and by datacenter.
+
+| Path           | Produces    |
+| -------------- | ----------- |
+| `/ui/topology` | `text/html` |
+
+## ACL Tokens
+
+This page lets you enter an ACL token (both accessor ID and secret ID) to use with the UI.
+If the cluster does not have ACLs enabled, this page is unnecessary. If the cluster has an
+anonymous policy that grants cluster-wide read access, this page is unnecessary. If the
+anonymous policy only grants partial read access, then providing an ACL Token will
+authenticate all future requests to allow read access to additional resources.
+
+| Path                  | Produces    |
+| --------------------- | ----------- |
+| `/ui/settings/tokens` | `text/html` |
+
+
+## Keyboard Shortcuts
+
+The Nomad UI supports several keyboard shortcuts in order to help users navigate and operate Nomad. You can use common key commands to dig into jobs, view logs, monitor evaluations, and more.
+
+Type `?` from anywhere in the UI to launch the Keyboard Shortcuts panel. 
+
+### Default key commands:
+
+| Command                  | Pattern    |
+| --------------------- | ----------- |
+| Go to Jobs | `g j` |
+| Go to Storage | `g r` |
+| Go to Servers | `g s` |
+| Go to Clients | `g c` |
+| Go to Topology | `g t` |
+| Go to Evaluations | `g e` |
+| Go to ACL Tokens | `g a` |
+| Next Subnav | `Shift + →` |
+| Previous Subnav | `Shift + ←` |
+| Next Main Section | `Shift + ↓` |
+| Previous Main Section | `Shift + ↑` |
+| Show Keyboard Shortcuts | `Shift + ?` |
+| Hide Keyboard Shortcuts | `Escape` |
+| Go Up a Level | `u` |
+
+### Rebinding and Disabling Commands
+
+From the Keyboard Shortcuts modal, you can click on any pattern to re-bind it to the shortcut of your choosing. This shortcut will persist via your browser's local storage and across refreshes. You can also toggle "Keyboard shortcuts enabled" to disable them completely.
+
diff --git a/content/nomad/v1.9.x/content/api-docs/validate.mdx b/content/nomad/v1.9.x/content/api-docs/validate.mdx
new file mode 100644
index 0000000000..70a1c7775a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/validate.mdx
@@ -0,0 +1,64 @@
+---
+layout: api
+page_title: Validate - HTTP API
+description: |-
+  The /validate endpoints are used to validate object structs, fields, and
+  types.
+---
+
+# Validate HTTP API
+
+The `/validate` endpoints are used to validate object structs, fields, and
+types.
+
+## Validate Job
+
+This endpoint validates a Nomad job file. The local Nomad agent forwards the
+request to the leader. In the event the leader cannot be reached the agent verifies
+the job file locally but skips validating driver configurations.
+
+~> This endpoint accepts a **JSON job file**, not an HCL job file.
+
+| Method | Path               | Produces           |
+| ------ | ------------------ | ------------------ |
+| `POST` | `/v1/validate/job` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required         |
+| ---------------- | -------------------- |
+| `NO`             | `namespace:read-job` |
+
+### Parameters
+
+There are no parameters, but the request _body_ contains the entire job file.
+
+### Sample Payload
+
+```text
+(any valid nomad job IN JSON FORMAT)
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @my-job.nomad.json \
+    https://localhost:4646/v1/validate/job
+```
+
+### Sample Response
+
+```json
+{
+  "DriverConfigValidated": true,
+  "ValidationErrors": [
+    "Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+  ],
+  "Warnings": "1 warning(s):\n\n* Group \"cache\" has warnings: 1 error(s) occurred:\n\n* Update max parallel count is greater than task group count (13 > 1). A destructive change would result in the simultaneous replacement of all allocations.",
+  "Error": "1 error(s) occurred:\n\n* Task group cache validation failed: 1 error(s) occurred:\n\n* Task redis validation failed: 1 error(s) occurred:\n\n* 1 error(s) occurred:\n\n* minimum CPU value is 20; got 1"
+}
+```
diff --git a/content/nomad/v1.9.x/content/api-docs/variables/index.mdx b/content/nomad/v1.9.x/content/api-docs/variables/index.mdx
new file mode 100644
index 0000000000..8f1e8bcb21
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/variables/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: |-
+  The /var endpoints are used to query for and interact with variables and variable
+  locking.
+---
+
+# Vars HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables, and set up locks and leases over them.
+
+See the [Variables][] documentation for information how these capabilities are
+used. For a CLI to perform these operations manually, please see the
+documentation for the [`nomad var`][] commands.
+
+Please choose a sub-section in the navigation for more information
+
+[`nomad var`]: /nomad/docs/commands/var
+[Variables]: /nomad/docs/concepts/variables
\ No newline at end of file
diff --git a/content/nomad/v1.9.x/content/api-docs/variables/locks.mdx b/content/nomad/v1.9.x/content/api-docs/variables/locks.mdx
new file mode 100644
index 0000000000..bbb79d7583
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/variables/locks.mdx
@@ -0,0 +1,211 @@
+---
+layout: api
+page_title: Variable Locks - HTTP API
+description: The /var endpoints are used to query for and interact with variables and locks.
+---
+
+# Locks HTTP API
+
+The `/var` endpoint is used to hold, renew and release a lock over a variable.
+
+## Lock Variable
+
+The endpoint to create a variable can also be used to hold a lock and interact with
+it through the use of a parameter defining the operation to be performed.
+
+| Method | Path                                 | Produces           |
+|--------|--------------------------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path?<lock-operation>` | `application/json` |
+
+### Parameters
+
+The lock operation parameter can be:
+
+- `lock-acquire`: When used, the call will introduce a lock over the variable if 
+it exists, or create a new one if it doesn't. The lock ID will be returned in the 
+response and it must be provided to perform any other operation over the lock. 
+The variable items can be updated at any time using the lock ID, but the lock
+parameters are unmmutable, attempting to modify them while a lock is present will
+generate an error. 
+
+In the case of attempting to acquire a variable that is already locked, a conflict
+response will be returned. 
+
+The lock-acquire operation will override the variable items if new values are 
+present.
+
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-acquire
+```
+
+#### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "1m"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the created or updated variable including the lock 
+parameters and ID, along with metadata created by the server:
+
+```json
+{
+  "CreateIndex": 15,
+  "CreateTime": 1694552155379696000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  },
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 16,
+  "ModifyTime": 1694552206138804000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-renew`: A valid call to lock renew needs to be placed before the lock's
+TTL is up in order to mantain the variable locked. A valid call must include the
+lock ID as part of the request body. If the lock TTL is up without a renewal or
+release calls, the variable will remain unlockable for at least the lock delay. 
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-renew
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body only returns metadata created by the server and the lock
+parameters:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "Lock": {
+    "TTL": "15s",
+    "LockDelay": "15s",
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  },
+  "ModifyIndex": 43,
+  "ModifyTime": 1694556175092779000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+- `lock-release`: A call to the endpoint with the `lock-release` operation will
+immediately remove the lock over the variable, making it modifiable without 
+restrictions again. 
+
+The lock-release operation will not override the variable items, if the request
+body contains any item, it will generate a bad request response.
+
+#### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first?lock-release
+```
+
+#### Sample Payload
+
+```json
+{
+  "Path": "example/first",
+  "Namespace": "prod",
+  "Lock": {
+    "ID": "670c7248-e2ef-f982-e4c5-f4437f75f1e4"
+  }
+}
+```
+
+#### Sample Response
+
+The response body returns the released variable along with metadata
+created by the server:
+
+```json
+{
+  "CreateIndex": 11,
+  "CreateTime": 1694555280887153000,
+  "ModifyIndex": 66,
+  "ModifyTime": 1694556922600469000,
+  "Namespace": "prod",
+  "Path": "example/first"
+}
+```
+
+### Sample Response for Conflict
+
+In the case of an attempt to lock, renew or modify a locked variable
+without the correct ID, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "CreateIndex": 0,
+  "CreateTime": 0,
+  "Items": null,
+  "Lock": null,
+  "ModifyIndex": 0,
+  "ModifyTime": 0,
+  "Namespace": "default",
+  "Path": "example/first"
+}
+```
+
+## Restrictions
+
+When creating a new variable using the lock-acquire operation, all the known 
+[restrictions][] regarding the path and size of the content apply, but unlike 
+regular variables, locked variables can be created with or without any items.
+
+The lock TTL and Delay must be values between 10 seconds and 24 hours.
+
+[Variables]: /nomad/docs/concepts/variables
+[restrictions]: /nomad/api-docs/variables/variables#restrictions
+[`nomad var`]: /nomad/docs/commands/var
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.9.x/content/api-docs/variables/variables.mdx b/content/nomad/v1.9.x/content/api-docs/variables/variables.mdx
new file mode 100644
index 0000000000..f53b0c7be4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/variables/variables.mdx
@@ -0,0 +1,300 @@
+---
+layout: api
+page_title: Variables - HTTP API
+description: The /var endpoints are used to query for and interact with variables.
+---
+
+# Variables HTTP API
+
+The `/var` and `/vars` endpoints are used to query for and interact with
+variables.
+
+See the [Variables][] documentation for information how these capabilities are
+used. 
+
+## List Variables
+
+This endpoint lists all variables. Note this API returns only variable metadata
+without decrypting the variable body.
+
+| Method | Path       | Produces           |
+|--------|------------|--------------------|
+| `GET`  | `/v1/vars` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                            |
+|------------------|-----------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:list`<br />The list capability on the namespace and path queried |
+
+### Parameters
+
+- `prefix` `(string: "")` - Specifies a string to filter variables on based on
+  an index prefix. This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected job. This value
+  can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of variables to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering) used
+  to filter the results. Consider using pagination or a query parameter to
+  reduce resources used to serve the request.
+
+- `namespace` `(string: "default")` - Specifies the target namespace. Specifying
+  `*` will return all variables across all the authorized namespaces.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/vars?namespace=prod&prefix=example
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "Namespace": "prod",
+    "Path": "example/first",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "prod",
+    "Path": "example/second",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+## Read Variable
+
+This endpoint reads a specific variable by path. This API returns the decrypted
+variable body.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `GET`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                               |
+|------------------|--------------------------------------------------------------------------------------------|
+| `YES`            | `namespace:* variables:read`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+## Create Variable
+
+This endpoint creates or updates a variable.
+
+| Method | Path                | Produces           |
+|--------|---------------------|--------------------|
+| `PUT`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                |
+|------------------|---------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:write`<br />The read capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace. If
+  set, this will override the request body.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be updated if the
+  `cas` value matches the current variables `ModifyIndex`. If the `cas` value is
+  0, the variable is only created if it does not already exist. This paradigm
+  allows check-and-set style updates.
+
+- `lock-operation` `(string: <unset>)` - This endpoint can also be used to create 
+and hold a lock over a variable, refer to the [locks section][] for more
+information.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values
+in the `Items` field.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XPUT -d@spec.nsv.json \
+    https://localhost:4646/v1/var/example/first
+```
+
+### Sample Payload
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response
+
+The response body returns the created or updated variable along with metadata
+created by the server:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict, the API will return HTTP error code
+409 and a response body showing the conflicting variable. If the provided ACL
+token does not also have `read` permissions to the variable path, the response
+will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000,
+  "Items": {
+    "user": "me",
+    "password": "passw0rd1"
+  }
+}
+```
+
+
+## Delete Variable
+
+This endpoint deletes a specific variable by path.
+
+| Method | Path               | Produces           |
+|--------|--------------------|--------------------|
+| `DELETE`  | `/v1/var/:var_path` | `application/json` |
+
+The table below shows this endpoint's support for [blocking queries] and
+[required ACLs].
+
+| Blocking Queries | ACL Required                                                                                     |
+|------------------|--------------------------------------------------------------------------------------------------|
+| `NO`             | `namespace:* variables:destroy`<br />The destroy capability on the variable's namespace and path |
+
+### Parameters
+
+- `namespace` `(string: "default")` - Specifies the variable's namespace.
+
+- `cas` `(int: <unset>)` - If set, the variable will only be deleted if the
+  `cas` value matches the current variables `ModifyIndex`.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod
+```
+
+### Sample Response
+
+```json
+{
+  "Index": 16
+}
+```
+
+### Sample Request With CAS
+
+```shell-session
+$ curl \
+    -XDELETE \
+    https://localhost:4646/v1/var/example/first?namespace=prod&cas=1
+```
+
+### Sample Response for Conflict
+
+In the case of a compare-and-set conflict on delete, the API will return HTTP
+error code 409 and a response body showing the conflicting variable. If the
+provided ACL token does not also have `read` permissions to the variable path,
+the response will include only metadata and not the `Items` field:
+
+```json
+{
+  "Namespace": "prod",
+  "Path": "example/first",
+  "CreateIndex": 1457,
+  "ModifyIndex": 1457,
+  "CreateTime": 1662061225600373000,
+  "ModifyTime": 1662061225600373000
+}
+```
+
+[Variables]: /nomad/docs/concepts/variables
+[locks section]:/nomad/api-docs/variables/locks
+[blocking queries]: /nomad/api-docs#blocking-queries
+[required ACLs]: /nomad/api-docs#acls
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.9.x/content/api-docs/volumes.mdx b/content/nomad/v1.9.x/content/api-docs/volumes.mdx
new file mode 100644
index 0000000000..9b56c16e88
--- /dev/null
+++ b/content/nomad/v1.9.x/content/api-docs/volumes.mdx
@@ -0,0 +1,789 @@
+---
+layout: api
+page_title: Volumes - HTTP API
+description: The `/volume` endpoints are used to query for and interact with volumes.
+---
+
+# Volumes HTTP API
+
+The `/volume` and `/volumes` endpoints are used to query for and interact with
+volumes.
+
+## List Volumes
+
+This endpoint lists all volumes.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/volumes` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `type` `(string: "")` - Specifies the type of volume to
+  query. Currently only supports `csi`. This is specified as a query
+  string parameter. Returns an empty list if omitted.
+
+- `node_id` `(string: "")` - Specifies a string to filter volumes
+  based on an Node ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The `next_token`
+  parameter accepts a string which identifies the next expected volume. This
+  value can be obtained from the `X-Nomad-NextToken` header from the previous
+  response.
+
+- `per_page` `(int: 0)` - Specifies a maximum number of volumes to return for
+  this request. If omitted, the response is not paginated. The value of the
+  `X-Nomad-NextToken` header of the last response can be used as the
+  `next_token` of the next request to fetch additional pages.
+
+- `filter` `(string: "")` - Specifies the [expression](/nomad/api-docs#filtering)
+  used to filter the results. Consider using pagination or a query parameter to
+  reduce resource used to serve the request.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes?type=csi&node_id=foo&plugin_id=plugin-id1
+```
+
+### Sample Response
+
+```json
+[
+  {
+    "ID": "volume-id1",
+    "ExternalID": "vol-abcdef",
+    "Namespace": "default",
+    "Name": "volume id1",
+    "Topologies": [
+      {
+        "foo": "bar"
+      }
+    ],
+    "AccessMode": "multi-node-single-writer",
+    "AttachmentMode": "file-system",
+    "CurrentReaders": 2,
+    "CurrentWriters": 1,
+    "Schedulable": true,
+    "PluginID": "plugin-id1",
+    "Provider": "ebs",
+    "ControllerRequired": true,
+    "ControllersHealthy": 3,
+    "ControllersExpected": 3,
+    "NodesHealthy": 15,
+    "NodesExpected": 18,
+    "ResourceExhausted": 0,
+    "CreateIndex": 42,
+    "ModifyIndex": 64
+  }
+]
+```
+
+## Read Volume
+
+This endpoint reads information about a specific volume.
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `GET`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-read-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+### Sample Response
+
+```json
+{
+  "ID": "volume-id1",
+  "Name": "volume id1",
+  "Namespace": "default",
+  "ExternalID": "vol-abcdef",
+  "Topologies": [{ "foo": "bar" }],
+  "AccessMode": "multi-node-single-writer",
+  "AttachmentMode": "file-system",
+  "RequestedCapabilities": [
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "file-system"
+    },
+    {
+      "AccessMode": "single-node-writer",
+      "AttachmentMode": "block-device"
+    }
+  ],
+  "Allocations": [
+    {
+      "ID": "a8198d79-cfdb-6593-a999-1e9adabcba2e",
+      "EvalID": "5456bd7a-9fc0-c0dd-6131-cbee77f57577",
+      "Name": "example.cache[0]",
+      "NodeID": "fb2170a8-257d-3c64-b14d-bc06cc94e34c",
+      "PreviousAllocation": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+      "NextAllocation": "cd13d9b9-4f97-7184-c88b-7b451981616b",
+      "RescheduleTracker": {
+        "Events": [
+          {
+            "PrevAllocID": "516d2753-0513-cfc7-57ac-2d6fac18b9dc",
+            "PrevNodeID": "9230cd3b-3bda-9a3f-82f9-b2ea8dedb20e",
+            "RescheduleTime": 1517434161192946200,
+            "Delay": "5000000000"
+          }
+        ]
+      },
+      "JobID": "example",
+      "TaskGroup": "cache",
+      "DesiredStatus": "run",
+      "DesiredDescription": "",
+      "ClientStatus": "running",
+      "ClientDescription": "",
+      "TaskStates": {
+        "redis": {
+          "State": "running",
+          "FinishedAt": "0001-01-01T00:00:00Z",
+          "LastRestart": "0001-01-01T00:00:00Z",
+          "Restarts": 0,
+          "StartedAt": "2017-07-25T23:36:26.106431265Z",
+          "Failed": false,
+          "Events": [
+            {
+              "Type": "Received",
+              "Time": 1495747371795703800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            },
+            {
+              "Type": "Driver",
+              "Time": 1495747371798867200,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": "Downloading image redis:7"
+            },
+            {
+              "Type": "Started",
+              "Time": 1495747379525667800,
+              "FailsTask": false,
+              "RestartReason": "",
+              "SetupError": "",
+              "DriverError": "",
+              "ExitCode": 0,
+              "Signal": 0,
+              "Message": "",
+              "KillTimeout": 0,
+              "KillError": "",
+              "KillReason": "",
+              "StartDelay": 0,
+              "DownloadError": "",
+              "ValidationError": "",
+              "DiskLimit": 0,
+              "FailedSibling": "",
+              "VaultError": "",
+              "TaskSignalReason": "",
+              "TaskSignal": "",
+              "DriverMessage": ""
+            }
+          ]
+        }
+      },
+      "CreateIndex": 54,
+      "ModifyIndex": 57,
+      "CreateTime": 1495747371794276400,
+      "ModifyTime": 1495747371794276400
+    }
+  ],
+  "ReadAllocs": {
+    "a8198d79-cfdb-6593-a999-1e9adabcba2e": null
+  },
+  "WriteAllocs": {},
+  "Schedulable": true,
+  "PluginID": "plugin-id1",
+  "Provider": "ebs",
+  "Version": "1.0.1",
+  "ControllerRequired": true,
+  "ControllersHealthy": 3,
+  "ControllersExpected": 3,
+  "NodesHealthy": 15,
+  "NodesExpected": 18,
+  "ResourceExhausted": 0,
+  "CreateIndex": 42,
+  "ModifyIndex": 64
+}
+```
+
+## Register Volume
+
+This endpoint registers an external volume with Nomad. The volume must exist
+in the external storage provider (see [Create Volume] below).
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                        | Produces           |
+| ------ | --------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ExternalID": "vol-abcdef",
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+## Create Volume
+
+This endpoint creates a volume in an external storage provider and registers
+it with Nomad. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the `CREATE_DELETE_VOLUME`
+capability support this endpoint.
+
+Making the same request again with a higher `RequestedCapacityMin` value
+may trigger a [Volume Expansion][].
+
+| Method | Path                               | Produces           |
+| ------ | ---------------------------------- | ------------------ |
+| `PUT`  | `/v1/volume/csi/:volume_id/create` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Payload
+
+The payload must include a JSON document that describes the volume's
+parameters.
+
+```json
+{
+  "Volumes": [
+    {
+      "ID": "volume-id1",
+      "Name": "volume one",
+      "Namespace": "default",
+      "PluginID": "plugin-id1",
+      "MountOptions": {
+        "FsType": "ext4",
+        "MountFlags": ["ro", "noatime"],
+      },
+      "RequestedCapacityMin": 10737418240,
+      "RequestedCapacityMax": 21474836480,
+      "RequestedCapabilities": [
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "file-system"
+        },
+        {
+          "AccessMode": "single-node-writer",
+          "AttachmentMode": "block-device"
+        }
+      ],
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "SnapshotID": "snap-12345",
+      "Topologies": [{ "foo": "bar" }]
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request PUT \
+    --data @payload.json \
+    https://localhost:4646/v1/volume/csi/volume-id1
+```
+
+
+## Deregister Volume
+
+This endpoint deregisters an external volume with Nomad. It is an error to
+deregister a volume that is in use.
+
+| Method   | Path                        | Produces           |
+| -------- | --------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `force` `(bool: false)` - Force deregistration of the volume and immediately
+  drop claims for terminal allocations. Returns an error if the volume has
+  running allocations. This does not detach the volume from client nodes.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id1?force=false
+```
+
+## Delete Volume
+
+This endpoint deletes an external volume from the storage provider, and
+deregisters it from Nomad. It is an error to delete a volume that is in
+use. Only CSI plugins that implement the [Controller][csi_plugins_internals]
+interface with the `CREATE_DELETE_VOLUME` capability support this endpoint.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/delete` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the volume as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI volume was created.
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volume/csi/volume-id1/delete
+```
+
+## Detach Volume
+
+This endpoint detaches an external volume from a Nomad client node. It is an
+error to detach a volume that is in use.
+
+| Method   | Path                               | Produces           |
+| -------- | ---------------------------------- | ------------------ |
+| `DELETE` | `/v1/volume/csi/:volume_id/detach` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+### Parameters
+
+- `:volume_id` `(string: <required>)` - Specifies the ID of the
+  volume. This must be the full ID. This is specified as part of the
+  path.
+
+- `node` `(string: <required>)` - The node to detach the volume from.
+  This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    https://localhost:4646/v1/volume/csi/volume-id/detach?node=00000000-0000-0000-0000-000000000000
+```
+
+## List External Volumes
+
+This endpoint lists storage volumes that are known to the external storage
+provider but may not be registered with Nomad.  Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface with the
+`LIST_VOLUMES` capability support this endpoint.
+
+| Method | Path                   | Produces           |
+|--------|------------------------|--------------------|
+| `GET`  | `/v1/volumes/external` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `YES`             | `namespace:csi-list-volume` |
+
+### Parameters
+
+- `plugin_id` `(string: "")` - Specifies a string to filter volumes
+  based on a plugin ID prefix. Because the value is decoded to bytes,
+  the prefix must have an even number of hexadecimal characters
+  (0-9a-f). This is specified as a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    https://localhost:4646/v1/volumes/external?&plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Volumes": [
+    {
+      "ExternalID": "vol-37ac485e",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-12345",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": false,
+      "Status": ""
+    },
+    {
+      "ExternalID": "vol-10ac4879",
+      "CapacityBytes": 1000000,
+      "SnapshotID": "snap-abcdef",
+      "PublishedExternalNodeIDs": ["i-12345", "i-abcde"],
+      "IsAbnormal": true,
+      "Status": "example error message from provider"
+    }
+  ]
+}
+```
+
+## Create Snapshot
+
+This endpoint creates a snapshot of a volume on the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                              | Produces           |
+| -------- | --------------------------------- | ------------------ |
+| `POST`    | `/v1/volumes/snapshot`           | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+
+### Sample Payload
+
+The payload must include a JSON document that describes the snapshot's
+parameters.
+
+```json
+{
+  "Snapshots": [
+    {
+      "SourceVolumeID": "volume-id1",
+      "PluginID": "plugin-id1",
+      "Name": "mysnap",
+      "Secrets": {
+        "password": "xyzzy"
+      },
+      "Parameters": {
+        "example": "infrequent_access"
+      }
+    }
+  ]
+}
+```
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request POST \
+    --data @payload.json \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+### Sample Response
+
+```json
+{
+  "Snapshots": [
+    {
+      "ID": "snap-031f5f7e3406d594a",
+      "SizeBytes": 10737418240,
+      "CreateTime": 1617909982,
+      "IsReady": false,
+      "SourceVolumeID": "volume-id1"
+    }
+  ]
+}
+```
+
+## Delete Snapshot
+
+This endpoint deletes a volume snapshot from the external storage
+provider. Only CSI plugins that implement the
+[Controller][csi_plugins_internals] interface with the
+`CREATE_DELETE_SNAPSHOT` capability support this endpoint.
+
+| Method   | Path                   | Produces           |
+| -------- | ---------------------- | ------------------ |
+| `DELETE` | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                 |
+| ---------------- | ---------------------------- |
+| `NO`             | `namespace:csi-write-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the delete. Because the value is decoded to bytes, the prefix
+  must have an even number of hexadecimal characters (0-9a-f). This is
+  specified as a query string parameter.
+
+- `snapshot_id` `(string: <required>)` - Specifies the snapshot ID to
+  delete. This is specified as a query parameter.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    --request DELETE \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot
+```
+
+## List Snapshots
+
+This endpoint lists volume snapshots on the external storage provider. Only
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+with the `LIST_SNAPSHOTS` capability support this endpoint.
+
+
+| Method | Path                   | Produces           |
+| ------ | ---------------------- | ------------------ |
+| `GET`  | `/v1/volumes/snapshot` | `application/json` |
+
+The table below shows this endpoint's support for
+[blocking queries](/nomad/api-docs#blocking-queries) and
+[required ACLs](/nomad/api-docs#acls).
+
+| Blocking Queries | ACL Required                |
+| ---------------- | --------------------------- |
+| `YES`            | `namespace:csi-list-volume` |
+
+This endpoint accepts a `X-Nomad-CSI-Secrets` header to set secrets
+for deleting the snapshot as comma-separated key-value pairs (see the
+example below). These secrets will be merged with any secrets already
+stored when the CSI snapshot was created.
+
+### Parameters
+
+- `plugin_id` `(string: <required>)` - Specifies the prefix of a CSI plugin ID
+  to perform the list. Because the value is decoded to bytes, the prefix must
+  have an even number of hexadecimal characters (0-9a-f). This is specified as
+  a query string parameter.
+
+- `next_token` `(string: "")` - This endpoint supports paging. The
+  `next_token` parameter accepts a string returned in a previous response's
+  `NextToken` field to request the next page of results.
+
+- `per_page` `(int: <required>)` - Specifies a maximum number of snapshots to
+  return for this request. The response will include a `NextToken` field that
+  can be passed to the next request to fetch additional pages.
+
+### Sample Request
+
+```shell-session
+$ curl \
+    -H "X-Nomad-CSI-Secrets: secret-key-1=value-1,secret-key-2=value-2" \
+    https://localhost:4646/v1/volumes/snapshot?plugin_id=plugin-id1&per_page=2
+```
+
+### Sample Response
+
+```json
+{
+  "NextToken": "eyJ2IjoiMiIsImMiOiJLZ",
+  "Snapshots": [
+    {
+      "CreateTime": 1227088980,
+      "ExternalSourceVolumeID": "vol-37ac485e",
+      "ID": "snap-9df717f4",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 2147483648
+    },
+    {
+      "CreateTime": 1227091232,
+      "ExternalSourceVolumeID": "vol-10ac4879",
+      "ID": "snap-5cf81835",
+      "IsReady": true,
+      "Parameters": null,
+      "PluginID": "aws-ebs0",
+      "SizeBytes": 11811160064
+    }
+  ]
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[Create Volume]: #create-volume
+[Volume Expansion]: /nomad/docs/other-specifications/volume#volume-expansion
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/create.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/create.mdx
new file mode 100644
index 0000000000..6abcc08271
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/create.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method create command reference'
+description: |
+  The `nomad acl auth-method create` command creates new access control list (ACL) authentication methods. Set name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method create` command reference
+
+The `acl auth-method create` command is used to create new ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method create [options]
+```
+
+The `acl auth-method create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create options
+
+- `-name`: Sets the human readable name for the ACL auth method. The name must
+  be between 1-128 characters and is a required parameter.
+
+- `-description`: A free form text description of the auth-method that must not exceed
+  256 characters.
+
+- `-type`: Sets the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Sets the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Defines the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth-method in a JSON format.
+
+- `-t`: Format and display the ACL auth-method using a Go template.
+
+## Examples
+
+Create a new ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method create -name "example-acl-auth-method" -type "OIDC" -max-token-ttl "1h" -token-locality "local" -config "@config.json"
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
+
+Example config file:
+
+```json
+{
+  "OIDCDiscoveryURL": "https://my-corp-app-name.auth0.com/",
+  "OIDCClientID": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "OIDCClientSecret": "example-client-secret",
+  "BoundAudiences": [
+    "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt"
+  ],
+  "AllowedRedirectURIs": [
+    "http://localhost:4646/oidc/callback"
+  ],
+  "ClaimMappings": {
+    "http://example.com/first_name": "first_name",
+    "http://example.com/last_name": "last_name"
+  },
+  "ListClaimMappings": {
+    "http://nomad.com/groups": "groups"
+  }
+}
+```
+
+[configuration]: /nomad/api-docs/acl/auth-methods#config
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/delete.mdx
new file mode 100644
index 0000000000..9527030172
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method delete command reference'
+description: |
+  The `nomad auth-method delete command` deletes an existing access control list (ACL) authentication method.
+---
+
+# `nomad`acl auth-method delete` command reference
+
+The `acl auth-method delete` command is used to delete existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method delete [options] <auth-method_name>
+```
+
+The `acl auth-method delete` command requires an existing method's name.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method delete example-auth-method
+ACL auth method example-auth-method successfully deleted
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/info.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/info.mdx
new file mode 100644
index 0000000000..d4dbe9a43f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/info.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method info command reference'
+description: |
+  The `nomad auth-method info` command fetches information about an existing access control list (ACL) authentication method. Review name, type, description, locality, time to live (TTL), token name format, and authentication method configuration.
+---
+
+# `nomad acl auth-method info` command reference
+
+The `acl auth-method info` command is used to fetch information about an existing ACL Auth Method.
+
+## Usage
+
+```plaintext
+nomad acl auth-method info [options] <auth-method_name>
+```
+
+The `acl auth-method info` command requires an existing method's name.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info options
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl auth-method info example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = local
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_type}-${auth_method_name}
+Default             = false
+Create Index        = 14
+Modify Index        = 14
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/list.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/list.mdx
new file mode 100644
index 0000000000..95f6e95da1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method list command reference'
+description: |
+  The `nomad acl auth-method list` command lists existing access control list (ACL) authentication methods.
+---
+
+# `nomad acl auth-method list` command reference
+
+The `acl auth-method list` command is used to list existing ACL Auth Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method list [options]
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the ACL auth-methods in a JSON format.
+
+- `-t` : Format and display the ACL auth-methods using a Go template.
+
+## Examples
+
+List all ACL Auth Methods:
+
+```shell-session
+$ nomad acl auth-method list
+Name                     Type  Default
+example-acl-auth-method  OIDC  false
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/update.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/update.mdx
new file mode 100644
index 0000000000..7e2952aea1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/auth-method/update.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'nomad acl auth-method update command reference'
+description: |
+  The `nomad acl auth-method update` command updates an existing access control list (ACL) authentication method.  Modify name, name format, description, OIDC or JWT type, local or global, and time to live (TTL).
+---
+
+# `nomad acl auth-method update` command reference
+
+The `acl auth-method update` command is used to update existing ACL Auth
+Methods.
+
+## Usage
+
+```plaintext
+nomad acl auth-method update [options] <auth-method_name>
+```
+
+The `acl auth-method update` command requires an existing method's name.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-type`: Updates the type of the auth method. Supported types are `OIDC` and `JWT`.
+
+- `-max-token-ttl`: Updates the duration of time all tokens created by this auth
+  method should be valid for.
+
+- `-token-locality`: Updates the kind of token that this auth method should
+  produce. This can be either `local` or `global`.
+
+- `token-name-format`: Sets the token format for the authenticated users.
+  This can be lightly templated using HIL '${foo}' syntax. Defaults to
+  '${auth_method_type}-${auth_method_name}'.
+
+- `-default`: Specifies whether this auth method should be treated as a default
+  one in case no auth method is explicitly specified for a login command.
+
+- `-config`: Auth method [configuration] in JSON format. May be prefixed with '@'
+  to indicate that the value is a file path to load the config from. '-' may also
+  be given to indicate that the config is available on stdin.
+
+- `-json`: Output the ACL auth method in a JSON format.
+
+- `-t`: Format and display the ACL auth method using a Go template.
+
+## Examples
+
+Update an existing ACL auth method:
+
+```shell-session
+$ nomad acl auth-method update -token-locality "global" -token-name-format '${auth_method_name}-${value.user}' -config @config.json example-acl-auth-method
+Name                = example-acl-auth-method
+Type                = OIDC
+Locality            = global
+Max Token TTL       = 1h0m0s
+Token Name Format   = ${auth_method_name}-${value.user}
+Default             = false
+Create Index        = 14
+Modify Index        = 33
+
+Auth Method Config
+
+OIDC Discovery URL     = https://my-corp-app-name.auth0.com/
+OIDC Client ID         = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+OIDC Client Secret     = example-client-secret
+Bound audiences        = V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt
+Allowed redirects URIs = http://localhost:4646/oidc/callback
+Discovery CA pem       = <none>
+Signing algorithms     = <none>
+Claim mappings         = {http://example.com/first_name: first_name}; {http://example.com/last_name: last_name}
+List claim mappings    = {http://nomad.com/groups: groups}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/create.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/create.mdx
new file mode 100644
index 0000000000..717ceb293b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/create.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule create command reference'
+description: |
+  The `nomad acl binding-rule create` command creates new access control list (ACL) binding rules. Set a description, associated authentication method, selector expression, or bind name. Configure role, policy, or management bind type.
+---
+
+# `nomad acl binding-rule create` command reference
+
+The `acl binding-rule create` command is used to create new ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule create [options]
+```
+
+The `acl binding-rule create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-auth-method`: Specifies the name of the ACL authentication method that this
+  binding rule is associated with.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the auth method during login.
+
+  ~> **Caveat:** Selectors that operate on `ClaimMappings` (as opposed to
+  `ListClaimMappings`), the key that we match against has to be prefixed with
+  `value.`
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Create a new ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "engineering in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on UNIX
+machines:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector "\"product-developer\" in list.roles"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector needs to be escaped on Windows
+machines via PowerShell:
+
+```shell-session
+$ nomad.exe acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "auth0" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="`"project-developer`"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "\"project-developer\" in list.roles"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
+
+Create a new ACL Binding Rule where the selector uses a mathing against a
+single `ClaimMapping` which uses `owner` as its value:
+
+```shell-session
+$ nomad acl binding-rule create \
+    -description "example binding rule" \
+    -auth-method "github" \
+    -bind-type "role" \
+    -bind-name "eng-ro" \
+    -selector="value.owner == user"
+ID           = 698fdad6-dcb3-79dd-dc72-b43374057dea
+Description  = example binding rule
+Auth Method  = github
+Selector     = "value.owner == user"
+Bind Type    = role
+Bind Name    = eng-ro
+Create Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Modify Time  = 2022-12-20 11:15:22.582568 +0000 UTC
+Create Index = 14
+Modify Index = 14
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/delete.mdx
new file mode 100644
index 0000000000..a4d383d731
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule delete command reference'
+description: |
+  The `nomad acl binding-rule delete` command delete an existing access control list (ACL) binding rule.
+---
+
+# `nomad acl binding-rule delete` command reference
+
+The `acl binding-rule delete` command is used to delete existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule delete [options] <binding-rule_id>
+```
+
+The `acl binding-rule delete` command requires an existing rule's ID.
+
+## General Options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Auth Method:
+
+```shell-session
+$ nomad acl binding-rule delete 698fdad6-dcb3-79dd-dc72-b43374057dea
+ACL binding rule 698fdad6-dcb3-79dd-dc72-b43374057dea successfully deleted
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/info.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/info.mdx
new file mode 100644
index 0000000000..ff6ef2babb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/info.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule info command reference'
+description: |
+  The `nomad acl binding-rule info` command fetches information about an existing access control list (ACL) binding rule. Review ID, description, authentication method, selector, bind type, bind name, and time to live (TTL).
+---
+
+# `nomad acl binding-rule info` command reference
+
+The `acl binding-rule info` command is used to fetch information about an existing ACL Binding Rule.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule info [options] <binding-rule_id>
+```
+
+The `acl binding-rule info` command requires an existing rule's ID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info options
+
+- `-json`: Output the ACL Binding Rule in a JSON format.
+
+- `-t`: Format and display the ACL Binding Rule using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Binding Rule:
+
+```shell-session
+$ nomad acl binding-rule info dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = example binding rule
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Create Index = 17
+Modify Index = 17
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/list.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/list.mdx
new file mode 100644
index 0000000000..7a2436421b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule list command reference'
+description: |
+  The `nomad acl binding-rule list` command displays access control list (ACL) binding rules.
+---
+
+# `nomad acl binding-rule list` command reference
+
+The `acl binding-rule list` command is used to list existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule list [options]
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the ACL binding-rules in a JSON format.
+
+- `-t` : Format and display the ACL binding-rules using a Go template.
+
+## Examples
+
+List all ACL Binding Rules:
+
+```shell-session
+$ nomad acl binding-rule list
+ID                                    Description           Auth Method
+dc0e494d-0878-4e56-37d4-482e371e5bdb  example binding rule  auth0
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/update.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/update.mdx
new file mode 100644
index 0000000000..82024806fb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/binding-rule/update.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: 'nomad acl binding-rule update command reference'
+description: |
+    The `nomad acl binding-rule update` command modifies an existing access control list (ACL) binding rule. Update description, selector expression, bind name, and bind type.
+---
+
+# `nomad acl binding-rule update` command reference
+
+The `acl binding-rule update` command is used to update existing ACL Binding Rules.
+
+## Usage
+
+```plaintext
+nomad acl binding-rule update [options] <binding-rule_ID>
+```
+
+The `acl binding-rule update` command requires an existing rule's ID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update options
+
+- `-description`: A free form text description of the binding-rule that must not exceed
+  256 characters.
+
+- `-selector`: Selector is an expression that matches against verified identity
+  attributes returned from the binding rule during login.
+
+- `-bind-type`: Specifies adjusts how this binding rule is applied at login time
+  to internal Nomad objects. Valid options are `role`, `policy`, and `management`.
+
+- `-bind-name`: Specifies is the target of the binding used on selector match.
+  This can be lightly templated using HIL `${foo}` syntax. If the bind type is
+  set to `management`, this should not be set.
+
+- `-json`: Output the ACL binding-rule in a JSON format.
+
+- `-t`: Format and display the ACL binding-rule using a Go template.
+
+## Examples
+
+Update an existing ACL binding rule:
+
+```shell-session
+$ nomad acl binding-rule update -description "new description" dc0e494d-0878-4e56-37d4-482e371e5bdb
+ID           = dc0e494d-0878-4e56-37d4-482e371e5bdb
+Description  = new description
+Auth Method  = auth0
+Selector     = "engineering in list.roles"
+Bind Type    = role
+Bind Name    = engineering-ro
+Create Time  = 2022-12-20 11:17:40.483196 +0000 UTC
+Modify Time  = 2022-12-20 11:23:30.355439 +0000 UTC
+Create Index = 17
+Modify Index = 25
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/bootstrap.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/bootstrap.mdx
new file mode 100644
index 0000000000..f984e8e3c2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/bootstrap.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: 'nomad acl bootstrap command reference'
+description: |
+  The `nomad acl bootstrap` command creates the initial access control list (ACL) token. Nomad generates the token unless you provide a user-generated token.
+---
+
+# `nomad acl bootstrap` command reference
+
+The `acl bootstrap` command is used to bootstrap the initial ACL token.
+
+## Usage
+
+```plaintext
+nomad acl bootstrap [options]
+```
+
+The `acl bootstrap` command can be used in two ways:
+- If you provide no arguments it will return a system generated bootstrap token.
+- If you would like to provide an operator generated token it is possible to provide the token
+using a file `acl bootstrap [path]`. The Token can be read from stdin by setting the path to "-".
+Please make sure you secure this token in an appropriate manner as it could be written to your terminal history.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Bootstrap options
+
+- `-json` : Output the bootstrap response in JSON format.
+- `-t` : Format and display the deployments using a Go template.
+
+## Examples
+
+Bootstrap the initial token without arguments:
+
+```shell-session
+$ nomad acl bootstrap
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 9184ec35-65d4-9258-61e3-0c066d0a45c5
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token:
+
+root.token file
+```shell-session
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+```
+
+```shell-session
+$ nomad acl bootstrap root.token
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
+
+Bootstrap the initial token with provided token using stdin
+
+```shell-session
+$ nomad acl bootstrap -
+2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+EOF
+Accessor ID  = 5b7fd453-d3f7-6814-81dc-fcfe6daedea5
+Secret ID    = 2b778dd9-f5f1-6f29-b4b4-9a5fa948757a
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Policies     = n/a
+Create Time  = 2017-09-11 17:38:10.999089612 +0000 UTC
+Create Index = 7
+Modify Index = 7
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/index.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/index.mdx
new file mode 100644
index 0000000000..7d89755b03
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/index.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad acl command reference'
+description: |
+  The `nomad acl` command interacts with access control list (ACL) policies, roles, tokens, binding rules, and authentication methods.
+---
+
+# `nomad acl` command reference
+
+The `acl` command is used to interact with ACL policies and tokens. Learn more
+about using Nomad's ACL system in the [Secure Nomad with Access Control
+guide][secure-guide].
+
+In [federated][] clusters, all ACL updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+## Usage
+
+Usage: `nomad acl <subcommand> [options]`
+
+Run `nomad acl <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`acl bootstrap`][bootstrap] - Bootstrap the initial ACL token
+- [`acl auth-method create`][authmethodcreate] - Create a new ACL auth method
+- [`acl auth-method delete`][authmethoddelete] - Delete an existing ACL auth method
+- [`acl auth-method info`][authmethodinfo] - Fetch information on an existing ACL auth method
+- [`acl auth-method list`][authmethodlist] - List available ACL auth methods
+- [`acl auth-method update`][authmethodupdate] - Update existing ACL auth method
+- [`acl binding-rule create`][bindingrulecreate] - Create a new ACL binding rule
+- [`acl binding-rule delete`][bindingruledelete] - Delete an existing ACL binding rule
+- [`acl binding-rule info`][bindingruleinfo] - Fetch information on an existing ACL binding rule
+- [`acl binding-rule list`][bindingrulelist] - List available ACL binding rules
+- [`acl binding-rule update`][bindingruleupdate] - Update existing ACL binding rule
+- [`acl policy apply`][policyapply] - Create or update ACL policies
+- [`acl policy delete`][policydelete] - Delete an existing ACL policies
+- [`acl policy info`][policyinfo] - Fetch information on an existing ACL policy
+- [`acl policy list`][policylist] - List available ACL policies
+- [`acl role create`][rolecreate] - Create a new ACL role
+- [`acl role delete`][roledelete] - Delete an existing ACL role
+- [`acl role info`][roleinfo] - Get info on an existing ACL role
+- [`acl role list`][rolelist] - List available ACL roles
+- [`acl role update`][roleupdate] - Update existing ACL role
+- [`acl token create`][tokencreate] - Create new ACL token
+- [`acl token delete`][tokendelete] - Delete an existing ACL token
+- [`acl token info`][tokeninfo] - Get info on an existing ACL token
+- [`acl token list`][tokenlist] - List available ACL tokens
+- [`acl token self`][tokenself] - Get info on self ACL token
+- [`acl token update`][tokenupdate] - Update existing ACL token
+
+[bootstrap]: /nomad/docs/commands/acl/bootstrap
+[authmethodcreate]: /nomad/docs/commands/acl/auth-method/create
+[authmethoddelete]: /nomad/docs/commands/acl/auth-method/delete
+[authmethodinfo]: /nomad/docs/commands/acl/auth-method/info
+[authmethodlist]: /nomad/docs/commands/acl/auth-method/list
+[authmethodupdate]: /nomad/docs/commands/acl/auth-method/update
+[bindingrulecreate]: /nomad/docs/commands/acl/binding-rule/create
+[bindingruledelete]: /nomad/docs/commands/acl/binding-rule/delete
+[bindingruleinfo]: /nomad/docs/commands/acl/binding-rule/info
+[bindingrulelist]: /nomad/docs/commands/acl/binding-rule/list
+[bindingruleupdate]: /nomad/docs/commands/acl/binding-rule/update
+[policyapply]: /nomad/docs/commands/acl/policy/apply
+[policydelete]: /nomad/docs/commands/acl/policy/delete
+[policyinfo]: /nomad/docs/commands/acl/policy/info
+[policylist]: /nomad/docs/commands/acl/policy/list
+[tokencreate]: /nomad/docs/commands/acl/token/create
+[tokenupdate]: /nomad/docs/commands/acl/token/update
+[tokendelete]: /nomad/docs/commands/acl/token/delete
+[tokeninfo]: /nomad/docs/commands/acl/token/info
+[tokenlist]: /nomad/docs/commands/acl/token/list
+[tokenself]: /nomad/docs/commands/acl/token/self
+[rolecreate]: /nomad/docs/commands/acl/role/create
+[roleupdate]: /nomad/docs/commands/acl/role/update
+[roledelete]: /nomad/docs/commands/acl/role/delete
+[roleinfo]: /nomad/docs/commands/acl/role/info
+[rolelist]: /nomad/docs/commands/acl/role/list
+[secure-guide]: /nomad/tutorials/access-control
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/policy/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/policy/apply.mdx
new file mode 100644
index 0000000000..ff718c3e0c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/policy/apply.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl policy apply command reference'
+description: |
+  The `nomad acl policy apply` command creates or updates an  access control list (ACL) policy. Set description, job, namespace, group, and task.
+---
+
+# `nomad acl policy apply` command reference
+
+The `acl policy apply` command is used to create or update ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy apply [options] <name> <path>
+```
+
+The `acl policy apply` command requires two arguments, the policy name and path
+to file. The policy can be read from stdin by setting the path to "-".
+
+This command requires a management ACL token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply options
+
+- `-description`: Sets the human readable description for the ACL policy.
+
+- `-job`: Attaches the policy to the specified job. Requires that `-namespace` is
+    also set. Refer to [Workload Associated ACL Policies][] for more details.
+
+- `-namespace`: Attaches the policy to the specified namespace. Requires that
+    `-job` is also set.
+
+- `-group`: Attaches the policy to the specified task group. Requires that
+    `-namespace` and `-job` are also set.
+
+- `-task`: Attaches the policy to the specified task. Requires that `-namespace`,
+    `-job` and `-group` are also set.
+
+
+## Examples
+
+Create a new ACL Policy:
+
+```shell-session
+$ nomad acl policy apply my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+Associate an ACL Policy with a specific task:
+
+```shell-session
+$ nomad acl policy apply \
+    -namespace default -job example -group cache -task redis \
+    my-policy my-policy.json
+Successfully wrote 'my-policy' ACL policy!
+```
+
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/policy/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/policy/delete.mdx
new file mode 100644
index 0000000000..9e276ffe89
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/policy/delete.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad acl policy delete command reference'
+description: |
+  The `nomad acl policy delete` command deletes an access control list (ACL) policy.
+---
+
+# `nomad acl policy delete` command reference
+
+The `acl policy delete` command is used to delete an existing ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy delete <policy_name>
+```
+
+The `acl policy delete` command requires the policy name as an argument.
+
+This command requires a management ACL token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an ACL Policy:
+
+```shell-session
+$ nomad acl policy delete my-policy
+Successfully deleted 'my-policy' ACL policy!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/policy/info.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/policy/info.mdx
new file mode 100644
index 0000000000..1460634f78
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/policy/info.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad acl policy info command reference'
+description: >
+  The `nomad acl policy info` command fetches information on an access control list (ACL) policy. Review name, description, and workload, as well as access control list (ACL) policies and rules.
+---
+
+# `nomad acl policy info` command reference
+
+The `acl policy info` command is used to fetch information on an existing ACL
+policy.
+
+## Usage
+
+```plaintext
+nomad acl policy info <name>
+```
+
+The `acl policy info` command requires the policy name.
+
+This command requires a management ACL token or a token that has the
+associated policy.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information on an existing ACL Policy:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+If the ACL Policy is associated with a [Workload Identity][], additional information will be shown:
+
+```shell-session
+$ nomad acl policy info my-policy
+Name        = my-policy
+Description = <none>
+CreateIndex = 749
+ModifyIndex = 758
+
+Associated Workload
+Namespace = default
+JobID     = example
+Group     = cache
+Task      = redis
+
+Rules
+
+{
+  "Name": "my-policy",
+  "Description": "This is a great policy",
+  "Rules": "list_jobs"
+}
+```
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/policy/list.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/policy/list.mdx
new file mode 100644
index 0000000000..e561c5db28
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/policy/list.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad acl policy list command reference'
+description: |
+  The `nomad acl policy list` command displays available access control list (ACL) policies.
+---
+
+# `nomad acl policy list` command reference
+
+The `acl policy list` command is used to list available ACL policies.
+
+## Usage
+
+```plaintext
+nomad acl policy list
+```
+
+This command requires a management ACL token to view all policies. A
+non-management token can query its own policies.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the policies in their JSON format.
+- `-t` : Format and display the policies using a Go template.
+
+## Examples
+
+List all ACL policies:
+
+```shell-session
+$ nomad acl policy list
+Name      Description
+policy-1  The first policy
+policy-2  The second policy
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/role/create.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/role/create.mdx
new file mode 100644
index 0000000000..89c294d923
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/role/create.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad acl role create command reference'
+description: |
+    The `nomad acl role create` command creates an access control list (ACL) role. Set name, description, and associated policy.
+---
+
+# `nomad acl role create` command reference
+
+The `acl role create` command is used to create new ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role create [options]
+```
+
+The `acl role create` command requires the correct setting of the create options
+via flags detailed below.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Create a new ACL Role:
+
+```shell-session
+$ nomad acl role create -name="example-acl-role" -policy=example-acl-policy
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = example-acl-policy
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/role/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/role/delete.mdx
new file mode 100644
index 0000000000..aef0e6e6d8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/role/delete.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad acl role delete command reference'
+description: |
+  The `nomad acl role delete` command deletes an access control list (ACL) role.
+---
+
+# `nomad acl role delete` command reference
+
+The `acl role delete` command is used to delete existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role delete [options] <role_id>
+```
+
+The `acl role delete` command requires an existing role's ID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL Role:
+
+```shell-session
+$ nomad acl role delete a53b0095-c28a-6181-0586-807b82e665e4
+ACL role a53b0095-c28a-6181-0586-807b82e665e4 successfully deleted
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/role/info.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/role/info.mdx
new file mode 100644
index 0000000000..4ffb5036d2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/role/info.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role info command reference'
+description: |
+  The `nomad acl role info` command fetches information about an access control list (ACL) role. Review ID, name, description, and policies.
+---
+
+# `nomad acl role info` command reference
+
+The `acl role info` command is used to fetch information about an existing ACL Role.
+
+## Usage
+
+```plaintext
+nomad acl role info [options] <role_id> or <role_name>
+```
+
+The `acl role info` command requires an existing role's ID or name.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info options
+
+- `-by-name`: Look up the ACL role using its name as the identifier. The
+  command defaults to expecting the ACL ID as the argument.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Fetch information about an existing ACL Role using its ID:
+
+```shell-session
+$ nomad acl role info a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
+
+Fetch information about an existing ACL Role using its name:
+
+```shell-session
+$ nomad acl role info -by-name example-acl-role
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 71
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/role/list.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/role/list.mdx
new file mode 100644
index 0000000000..2279ce4e52
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/role/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl role list command reference'
+description: |
+    The `nomad acl role list` displays access control list (ACL) roles.
+---
+
+# `nomad acl role list` command reference
+
+The `acl role list` command is used to list existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role list [options]
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the ACL roles in a JSON format.
+
+- `-t` : Format and display the ACL roles using a Go template.
+
+## Examples
+
+List all ACL Roles:
+
+```shell-session
+$ nomad acl role list
+ID                                    Name              Description  Policies
+a53b0095-c28a-6181-0586-807b82e665e4  example-acl-role  <none>       general-write
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/role/update.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/role/update.mdx
new file mode 100644
index 0000000000..7d47948b27
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/role/update.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad acl role update command reference'
+description: |
+    The `nomad acl role update` command modifies an access control list (ACL) role. Modify name, description, and associated policy.
+---
+
+# `nomad acl role update` command reference
+
+The `acl role update` command is used to update existing ACL Roles.
+
+## Usage
+
+```plaintext
+nomad acl role update [options] <role_id>
+```
+
+The `acl role update` command requires an existing role's ID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update options
+
+- `-name`: Sets the human-readable name for the ACL Role. It is required and
+  can contain alphanumeric characters and dashes. This name must be unique and
+  must not exceed 128 characters.
+
+- `-description`: A free form text description of the role that must not exceed
+  256 characters.
+
+- `-policy`: Specifies a policy to associate with the role identified by their
+  name. This flag can be specified multiple times and must be specified at
+  least once.
+
+- `-no-merge`: Do not merge the current role information with what is provided
+  to the command. Instead, overwrite all fields with the exception of the role
+  ID which is immutable.
+
+- `-json`: Output the ACL role in a JSON format.
+
+- `-t`: Format and display the ACL role using a Go template.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl role update -name="example-acl-role-updated" a53b0095-c28a-6181-0586-807b82e665e4
+ID           = a53b0095-c28a-6181-0586-807b82e665e4
+Name         = example-acl-role-updated
+Description  = <none>
+Policies     = general-write
+Create Index = 71
+Modify Index = 80
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/create.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/create.mdx
new file mode 100644
index 0000000000..195fc69988
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/create.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: 'nomad acl token create command reference'
+description: |
+  The `nomad acl token create` command creates an access control list (ACL) token. Set name, client or management type, policy, role, time to live (TTL), and whether the policy should be global.
+---
+
+# `nomad acl token create` command reference
+
+The `acl token create` command is used to create new ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token create [options]
+```
+
+The `acl token create` command requires no arguments.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Create options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" (default), or
+  "management".
+
+- `-global`: Sets the global mode of the token. Global tokens are replicated
+  to all regions. This can not be changed after creation. Defaults to false.
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens.
+
+- `-role-id`: ID of a role to use for this token. May be specified multiple
+  times.
+
+- `-role-name`: Name of a role to use for this token. May be specified multiple
+  times.
+
+- `-ttl`: Specifies the time-to-live of the created ACL token. This takes the
+  form of a time duration such as "5m" and "1h". By default, tokens will be
+  created without a TTL and therefore never expire.
+
+- `-json`:Output the ACL token information in JSON format.
+
+- `-t`: Format and display the ACL token information using a Go template.
+
+## Examples
+
+Create a new ACL token linked to an ACL Policy and Role:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -role-name=example-acl-role
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <none>
+Create Index = 140
+Modify Index = 140
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-policy
+```
+
+Create a new ACL token with an expiry:
+
+```shell-session
+$ nomad acl token create -name="example-acl-token" -policy=example-acl-policy -ttl=8h
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/delete.mdx
new file mode 100644
index 0000000000..765ae617fb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/delete.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad acl token delete command reference'
+description: |
+  The `nomad acl token delete` command deletes an access control list (ACL) token.
+---
+
+# `nomad acl token delete` command reference
+
+The `acl token delete` command is used to delete existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token delete <token_accessor_id>
+```
+
+The `acl token delete` command requires an existing token's AccessorID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete an existing ACL token:
+
+```shell-session
+$ nomad acl token delete d532c40a-30f1-695c-19e5-c35b882b0efd
+
+Token d532c40a-30f1-695c-19e5-c35b882b0efd successfully deleted
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/info.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/info.mdx
new file mode 100644
index 0000000000..aa1e097194
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/info.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad acl token info command reference'
+description: >
+  The `nomad acl token info` command fetches information about an access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token info` command reference
+
+The `acl token info` command is used to fetch information about an existing ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token info <token_accessor_id>
+```
+
+The `acl token info` command requires an existing token's AccessorID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ nomad acl token info 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Accessor ID  = 1b60edc8-e4ed-08ef-208d-ecc18a90ccc3
+Secret ID    = e4c7c80e-870b-c6a6-43d2-dbfa90130c06
+Name         = example-acl-token
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:17:35.45067293 +0000 UTC
+Expiry Time  = 2022-08-23 20:17:35.45067293 +0000 UTC
+Create Index = 142
+Modify Index = 142
+Policies     = [example-acl-policy]
+
+Roles
+<none>
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/list.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/list.mdx
new file mode 100644
index 0000000000..a5c5266a02
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/list.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad acl token list command reference'
+description: |
+  The `nomad acl token list` command displays access control list (ACL) tokens.
+---
+
+# `nomad acl token list` command reference
+
+The `acl token list` command is used to list existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token list
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the tokens in their JSON format.
+- `-t` : Format and display the tokens using a Go template.
+
+## Examples
+
+List all ACL tokens:
+
+```shell-session
+$ nomad acl token list
+Name               Type        Global  Accessor ID                           Expired
+Bootstrap Token    management  true    9c2d1b3a-cbc3-d9a0-3df9-5a382545a819  false
+example-acl-token  client      false   ef851ca0-b331-da5d-bbeb-7ede8f7c9151  false
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/self.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/self.mdx
new file mode 100644
index 0000000000..daeea1a832
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/self.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'nomad acl token self command reference'
+description: >
+  The `nomad acl token self` command fetches information about the currently set access control list (ACL) token. Review accessor ID, secret ID, name, type, global scope, time to live (TTL), policies, and roles.
+---
+
+# `nomad acl token self` command reference
+
+The `acl token self` command is used to fetch information about the currently
+set ACL token.
+
+## Usage
+
+```plaintext
+nomad acl token self
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Fetch information about an existing ACL token:
+
+```shell-session
+$ export NOMAD_TOKEN=85310d07-9afa-ef53-0933-0c043cd673c7
+
+$ nomad acl token self
+Accessor ID  = 9c2d1b3a-cbc3-d9a0-3df9-5a382545a819
+Secret ID    = 85310d07-9afa-ef53-0933-0c043cd673c7
+Name         = Bootstrap Token
+Type         = management
+Global       = true
+Create Time  = 2022-08-23 10:35:32.371025521 +0000 UTC
+Expiry Time  = <none>
+Create Index = 8
+Modify Index = 8
+Policies     = n/a
+Roles        = n/a
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/acl/token/update.mdx b/content/nomad/v1.9.x/content/docs/commands/acl/token/update.mdx
new file mode 100644
index 0000000000..20c3b0fe55
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/acl/token/update.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad acl token update command reference'
+description: |
+  The `nomad acl token update` command modifies an access control list (ACL) token. Update name, client or management type, policy, and role.
+---
+
+# `nomad acl token update` command reference
+
+The `acl token update` command is used to update existing ACL tokens.
+
+## Usage
+
+```plaintext
+nomad acl token update [options] <token_accessor_id>
+```
+
+The `acl token update` command requires an existing token's accessor ID.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Update options
+
+- `-name`: Sets the human readable name for the ACL token.
+
+- `-type`: Sets the type of token. Must be one of "client" or "management".
+
+- `-policy`: Specifies a policy to associate with the token. Can be specified
+  multiple times, but only with client type tokens. If any policies are
+  specified, they completely replace the policies on the existing token.
+
+- `-role-id`: ID of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+- `-role-name`: Name of a role to use for this token. Can be specified multiple
+  times, but only with client type tokens. If any roles are specified, they
+  completely replace the roles on the existing token.
+
+## Examples
+
+Update an existing ACL token:
+
+```shell-session
+$ nomad acl token update -name="example-acl-token-updated" ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Accessor ID  = ef851ca0-b331-da5d-bbeb-7ede8f7c9151
+Secret ID    = 11d5348a-8768-5baa-6185-c154980e1488
+Name         = example-acl-token-updated
+Type         = client
+Global       = false
+Create Time  = 2022-08-23 12:16:09.680699039 +0000 UTC
+Expiry Time  = <never>
+Create Index = 140
+Modify Index = 151
+Policies     = [example-acl-policy]
+
+Roles
+ID                                    Name
+2fe0c403-4502-e99d-4c79-a2821355e66d  example-acl-role-updated
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/agent-info.mdx b/content/nomad/v1.9.x/content/docs/commands/agent-info.mdx
new file mode 100644
index 0000000000..142fc52c24
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/agent-info.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'nomad agent-info command reference'
+description: |
+  The `nomad agent-info` command retrieves metrics and status information for a running agent. Use this command to review agent data from the client, nomad, serf, raft, and runtime subsystems.
+---
+
+# `nomad agent-info` command reference
+
+The `nomad agent-info` command retrieves metrics and status information for a
+running agent. The information returned pertains to the specific agent the CLI
+is connected to. This is useful for troubleshooting and performance monitoring.
+
+## Usage
+
+```plaintext
+nomad agent-info [options]
+```
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## `agent-info` options
+
+- `-json` : Output agent info in its JSON format.
+- `-t` : Format and display agent info using a Go template.
+
+## Output
+
+Depending on the agent queried, the `nomad agent-info` command retrieves
+information from the following subsystems:
+
+- Client: Status of the local Nomad client
+- Nomad: Status of the local Nomad server
+- Serf: Gossip protocol metrics and information
+- Raft: Status information about the Raft consensus protocol
+- Runtime: Various metrics from the runtime environment
+
+## Example
+
+```shell-session
+$ nomad agent-info
+raft
+  commit_index = 0
+  fsm_pending = 0
+  last_contact = never
+  last_snapshot_term = 0
+  state = Follower
+  term = 0
+  applied_index = 0
+  last_log_index = 0
+  last_log_term = 0
+  last_snapshot_index = 0
+  num_peers = 0
+runtime
+  cpu_count = 4
+  goroutines = 43
+  kernel.name = darwin
+  max_procs = 4
+  version = go1.5
+  arch = amd64
+serf
+  intent_queue = 0
+  member_time = 1
+  query_queue = 0
+  event_time = 1
+  event_queue = 0
+  failed = 0
+  left = 0
+  members = 1
+  query_time = 1
+  encrypted = false
+client
+  heartbeat_ttl = 0
+  known_servers = 0
+  last_heartbeat = 9223372036854775807
+  num_allocations = 0
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/agent.mdx b/content/nomad/v1.9.x/content/docs/commands/agent.mdx
new file mode 100644
index 0000000000..3cb4293648
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/agent.mdx
@@ -0,0 +1,261 @@
+---
+layout: docs
+page_title: 'nomad agent command reference'
+description: |
+  The `nomad agent` command starts the Nomad agent, which handles client or server functionality, including exposing interfaces for client consumption and running jobs. The agent runs until it receives an interrupt signal.
+---
+
+# `nomad agent` command reference
+
+The `nomad agent` command starts the Nomad agent, which handles client or server
+functionality, including exposing interfaces for client consumption and running
+jobs. The agent runs until it receives an interrupt signal.
+
+Refer to [Operating Nomad agents] and [Nomad agent configuration] for more
+information on how to use this command and the options it has.
+
+## Usage
+
+If you are running Nomad on Linux, you need to run client agents as root, or
+with `sudo`, so that cpuset accounting and network namespaces work correctly.
+
+```plaintext
+nomad agent [options]
+```
+
+## `nomad agent` options
+
+We recommend configuring a Nomad agent with configuration files. Refer to [Nomad
+agent configuration] for details.
+
+You may, however, may pass the following configuration options as CLI arguments:
+
+- `-alloc-dir=<path>`: Equivalent to the Client [alloc_dir][] config
+  option.
+
+- `-acl-enabled`: Equivalent to the ACL [enabled][] config option.
+
+- `-acl-replication-token`: Equivalent to the ACL [replication_token][] config
+  option.
+
+- `-bind=<address>`: Equivalent to the [bind_addr][] config option.
+
+- `-bootstrap-expect=<num>`: Equivalent to the
+  [bootstrap_expect][] config option.
+
+- `-client`: Enable client mode on the local agent.
+
+- `-config=<path>`: Specifies the path to a configuration file or a directory of
+  configuration files to load. Can be specified multiple times.
+
+- `-consul-address=<addr>`: Equivalent to the [address][] config option.
+
+- `-consul-auth=<auth>`: Equivalent to the [auth][] config option.
+
+- `-consul-auto-advertise`: Equivalent to the [auto_advertise][] config option.
+
+- `-consul-ca-file=<path>`: Equivalent to the [ca_file][] config option.
+
+- `-consul-cert-file=<path>`: Equivalent to the [cert_file][] config option.
+
+- `-consul-checks-use-advertise`: Equivalent to the [checks_use_advertise][]
+  config option.
+
+- `-consul-client-auto-join`: Equivalent to the [client_auto_join][] config
+  option.
+
+- `-consul-client-service-name=<name>`: Equivalent to the [client_service_name][]
+  config option.
+
+- `-consul-client-http-check-name=<name>`: Equivalent to the
+  [client_http_check_name][] config option.
+
+- `-consul-client-failures-before-critical=<num>`: Equivalent to the
+  [client_failures_before_critical][] config option.
+
+- `-consul-client-failures-before-warning=<num>`: Equivalent to the
+  [client_failures_before_warning][] config option.
+
+- `-consul-key-file=<path>`: Equivalent to the [key_file][] config option.
+
+- `-consul-server-service-name=<name>`: Equivalent to the [server_service_name][]
+  config option.
+
+- `-consul-server-http-check-name=<name>`: Equivalent to the
+  [server_http_check_name][] config option.
+
+- `-consul-server-serf-check-name=<name>`: Equivalent to the
+  [server_serf_check_name][] config option.
+
+- `-consul-server-rpc-check-name=<name>`: Equivalent to the
+  [server_rpc_check_name][] config option.
+
+- `-consul-server-auto-join`: Equivalent to the [server_auto_join][] config
+  option.
+
+- `-consul-server-failures-before-critical=<num>`: Equivalent to the
+  [server_failures_before_critical][] config option.
+
+- `-consul-server-failures-before-warning=<num>`: Equivalent to the
+  [server_failures_before_warning][] config option.
+
+- `-consul-ssl`: Equivalent to the [ssl][] config option.
+
+- `-consul-token=<token>`: Equivalent to the [token][] config option.
+
+- `-consul-verify-ssl`: Equivalent to the [verify_ssl][] config option.
+
+- `-data-dir=<path>`: Equivalent to the [data_dir][] config option.
+
+- `-dc=<datacenter>`: Equivalent to the [datacenter][] config option.
+
+- `-dev`: Start the agent in development mode. This enables a pre-configured
+  dual-role agent (client + server) which is useful for developing or testing
+  Nomad. No other configuration is required to start the agent in this mode,
+  but you may pass an optional comma-separated list of mode configurations:
+
+- `-dev-connect`: Start the agent in development mode, but bind to a public
+  network interface rather than localhost for using Consul Connect. It may be
+  used with `-dev-consul` to configure default workload identities for Consul.
+  This mode is supported only on Linux as root.
+
+- `-dev-consul`: Starts the agent in development mode with a default Consul
+  configuration for Nomad workload identity. It may be used with `-dev-connect`
+  to configure the agent for Consul Service Mesh.
+
+- `-dev-vault`: Starts the agent in development mode with a default Vault
+  configuration for Nomad workload identity.
+
+- `-encrypt`: Set the Serf encryption key. See the [Encryption Overview][] for
+  more details.
+
+- `-join=<address>`: Address of another agent to join upon starting up. This can
+  be specified multiple times to specify multiple agents to join.
+
+- `-log-level=<level>`: Equivalent to the [log_level][] config option.
+
+- `-log-include-location`: Equivalent to the [log_include_location][] config option.
+
+- `-log-json`: Equivalent to the [log_json][] config option.
+
+- `-meta=<key=value>`: Equivalent to the Client [meta][] config option.
+
+- `-network-interface=<interface>`: Equivalent to the Client
+  [network_interface][] config option.
+
+- `-node=<name>`: Equivalent to the [name][] config option.
+
+- `-node-class=<class>`: Equivalent to the Client [node_class][]
+  config option.
+
+- `-node-pool=<node-pool>`: Equivalent to the Client [node_pool][]
+  config option.
+
+- `-plugin-dir=<path>`: Equivalent to the [plugin_dir][] config option.
+
+- `-region=<region>`: Equivalent to the [region][] config option.
+
+- `-rejoin`: Equivalent to the [rejoin_after_leave][] config option.
+
+- `-retry-interval`: Equivalent to the [retry_interval][] config option.
+
+- `-retry-join`: Similar to `-join` but allows retrying a join if the first
+  attempt fails.
+
+  ```shell-session
+  $ nomad agent -retry-join "127.0.0.1:4648"
+  ```
+
+  `retry-join` can be defined as a command line flag only for servers. Clients
+  can configure `retry-join` only in configuration files.
+
+- `-retry-max`: Similar to the [retry_max][] config option.
+
+- `-server`: Enable server mode on the local agent.
+
+- `-servers=<host:port>`: Equivalent to the Client [servers][] config
+  option.
+
+- `-state-dir=<path>`: Equivalent to the Client [state_dir][] config
+  option.
+
+- `-vault-enabled`: Whether to enable or disabled Vault integration.
+
+- `-vault-address=<addr>`: The address to communicate with Vault.
+
+- `-vault-token=<token>`: The Vault token used to derive tokens. Only needs to
+  be set on Servers. Overrides the Vault token read from the VAULT_TOKEN
+  environment variable.
+
+- `-vault-create-from-role=<role>`: The role name to create tokens for tasks
+  from.
+
+- `-vault-ca-file=<path>`: Path to a PEM-encoded CA cert file used to verify the
+  Vault server SSL certificate.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM-encoded CA cert files used
+  to verify the Vault server SSL certificate.Whether to enable or disabled Vault
+  integration.
+
+- `vault-cert-file=<path>`: The path to the certificate for Vault communication.
+
+- `vault-key-file=<path>`: The path to the private key for Vault communication.
+
+- `vault-namespace=<namespace>`: The Vault namespace used for the integration.
+  Required for servers and clients. Overrides the Vault namespace read from the
+  VAULT_NAMESPACE environment variable.
+
+- `vault-tls-skip-verify`: A boolean that determines whether to skip SSL
+  certificate verification.
+
+- `vault-tls-server-name=<name>`: Used to set the SNI host when connecting to
+  Vault over TLS.
+
+[address]: /nomad/docs/configuration/consul#address
+[alloc_dir]: /nomad/docs/configuration/client#alloc_dir
+[auth]: /nomad/docs/configuration/consul#auth
+[auto_advertise]: /nomad/docs/configuration/consul#auto_advertise
+[bind_addr]: /nomad/docs/configuration#bind_addr
+[bootstrap_expect]: /nomad/docs/configuration/server#bootstrap_expect
+[ca_file]: /nomad/docs/configuration/consul#ca_file
+[cert_file]: /nomad/docs/configuration/consul#cert_file
+[checks_use_advertise]: /nomad/docs/configuration/consul#checks_use_advertise
+[client_auto_join]: /nomad/docs/configuration/consul#client_auto_join
+[client_http_check_name]: /nomad/docs/configuration/consul#client_http_check_name
+[client_failures_before_critical]: /nomad/docs/configuration/consul#client_failures_before_critical
+[client_failures_before_warning]: /nomad/docs/configuration/consul#client_failures_before_warning
+[server_failures_before_critical]: /nomad/docs/configuration/consul#server_failures_before_critical
+[server_failures_before_warning]: /nomad/docs/configuration/consul#server_failures_before_warning
+[client_service_name]: /nomad/docs/configuration/consul#client_service_name
+[data_dir]: /nomad/docs/configuration#data_dir
+[datacenter]: /nomad/docs/configuration#datacenter
+[enabled]: /nomad/docs/configuration/acl#enabled
+[encryption overview]: /nomad/tutorials/transport-security/security-gossip-encryption
+[key_file]: /nomad/docs/configuration/consul#key_file
+[log_include_location]: /nomad/docs/configuration#log_include_location
+[log_json]: /nomad/docs/configuration#log_json
+[log_level]: /nomad/docs/configuration#log_level
+[meta]: /nomad/docs/configuration/client#meta
+[name]: /nomad/docs/configuration#name
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[node_class]: /nomad/docs/configuration/client#node_class
+[node_pool]: /nomad/docs/configuration/client#node_pool
+[Operating Nomad agents]: /nomad/docs/operations/nomad-agent
+[Nomad agent configuration]: /nomad/docs/configuration
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[region]: /nomad/docs/configuration#region
+[rejoin_after_leave]: /nomad/docs/configuration/server#rejoin_after_leave
+[replication_token]: /nomad/docs/configuration/acl#replication_token
+[retry_interval]: /nomad/docs/configuration/server#retry_interval
+[retry_max]: /nomad/docs/configuration/server#retry_max
+[server_auto_join]: /nomad/docs/configuration/consul#server_auto_join
+[server_http_check_name]: /nomad/docs/configuration/consul#server_http_check_name
+[server_rpc_check_name]: /nomad/docs/configuration/consul#server_rpc_check_name
+[server_serf_check_name]: /nomad/docs/configuration/consul#server_serf_check_name
+[server_service_name]: /nomad/docs/configuration/consul#server_service_name
+[servers]: /nomad/docs/configuration/client#servers
+[ssl]: /nomad/docs/configuration/consul#ssl
+[state_dir]: /nomad/docs/configuration/client#state_dir
+[token]: /nomad/docs/configuration/consul#token
+[verify_ssl]: /nomad/docs/configuration/consul#verify_ssl
+
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/checks.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/checks.mdx
new file mode 100644
index 0000000000..51d2b4fe73
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/checks.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: 'nomad alloc checks command reference'
+description: |
+  The `nomad alloc checks` command displays service health check status information for an allocation.
+---
+
+# `nomad alloc checks` command reference
+
+
+The `alloc checks` command outputs the latest health check status information for checks in the allocation.
+
+## Usage
+
+```plaintext
+nomad alloc checks [options] <allocation>
+```
+
+Outputs the latest health check status information for services in the allocation
+using the Nomad service discovery provider. This command accepts an allocation
+ID or prefix as the sole argument.
+
+When ACLs are enabled, this command requires a token with the 'read-job' capability
+for the allocation's namespace. The 'list-jobs' capability is required to run the
+command with an allocation ID prefix instead of the exact allocation ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Checks options
+
+- `-verbose`: Display verbose output.
+
+- `-json`: Output the allocation in its JSON format.
+
+- `-t`: Format and display the health checks status using a Go template.
+
+## Examples
+
+Show checks of an alloc health check using its short ID:
+
+```shell-session
+$ nomad alloc checks e0fdbd85
+
+Status of 1 Nomad Service Checks
+
+ID         =  9f4e18fd0867cebb19a8fac3d7a1cf27
+Name       =  alive
+Group      =  example.cache[0]
+Task       =  (group)
+Service    =  redis-cache
+Status     =  success
+Mode       =  healthiness
+Timestamp  =  2023-03-09T16:10:23+01:00
+Output     =  nomad: tcp ok
+```
+
+The `-json` flag can be used to get the health checks status in json format:
+
+```shell-session
+nomad alloc checks -json 54fde4f8
+
+{
+    "9810e90177a4c21ce3bfe04dc7da6131": {
+        "Check": "alive",
+        "Group": "example.cache[0]",
+        "ID": "9810e90177a4c21ce3bfe04dc7da6131",
+        "Mode": "healthiness",
+        "Output": "nomad: tcp ok",
+        "Service": "redis-cache",
+        "Status": "success",
+        "StatusCode": 0,
+        "Task": "",
+        "Timestamp": 1678444309
+    }
+}
+```
+
+Or use the `-t` flag to format and display the health checks using a Go template:
+
+```shell-session
+$ nomad alloc checks -t '{{range .}}{{ printf "%s: %s\n" .ID  .Status }}{{end}}' 54
+
+9810e90177a4c21ce3bfe04dc7da6131: success
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/exec.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/exec.mdx
new file mode 100644
index 0000000000..2e3d502ab2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/exec.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: 'nomad alloc exec command reference'
+description: |
+  The `nomad alloc exec` runs a command inside a running task allocation, which is useful for debugging. Execute commands with or without an interactive shell inside the allocation.
+---
+
+# `nomad alloc exec` command reference
+
+**Alias: `nomad exec`**
+
+The `alloc exec` command runs a command in a running allocation.
+
+## Usage
+
+```plaintext
+nomad alloc exec [options] <allocation> <command> [<args>...]
+```
+
+The nomad exec command can be used to run commands inside a running task/allocation.
+
+Use cases are for inspecting container state, debugging a failed application
+without needing ssh access into the node that's running the allocation.
+
+This command executes the command in the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `read-job`, and `list-jobs`
+capabilities for the allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Exec options
+
+- `-task`: Sets the task to exec command in.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-i`: Pass stdin to the container, defaults to true. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to true if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty
+  (default: '~'). The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot ('.') closes the connection.
+  Setting the character to 'none' disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+To start an interactive debugging session in a particular alloc, invoke exec
+command with your desired shell available inside the task:
+
+```shell-session
+$ nomad alloc exec eb17e557 /bin/bash
+root@eb17e557:/data# # now run any debugging commands inside container
+root@eb17e557:/data# # ps -ef
+```
+
+To run a command and stream results without starting an interactive shell, you
+can pass the command and its arguments to exec directly:
+
+```shell-session
+# run commands without starting an interactive session
+$ nomad alloc exec eb17e557 cat /etc/resolv.conf
+...
+```
+
+When passing command arguments to be evaluated in task, you may need to ensure
+that your host shell doesn't interpolate values before invoking `exec` command.
+For example, the following command would return the environment variable on
+operator shell rather than task containers:
+
+```shell-session
+$ nomad alloc exec eb17e557 echo $NOMAD_ALLOC_ID # wrong
+...
+```
+
+Here, we must start a shell in task to interpolate `$NOMAD_ALLOC_ID`, and quote
+command or use the [heredoc syntax][heredoc]
+
+```shell-session
+# by quoting argument
+$ nomad alloc exec eb17e557 /bin/sh -c 'echo $NOMAD_ALLOC_ID'
+eb17e557-443e-4c51-c049-5bba7a9850bc
+
+$ # by using heredoc and passing command in stdin
+$ nomad alloc exec eb17e557 /bin/sh <<'EOF'
+> echo $NOMAD_ALLOC_ID
+> EOF
+eb17e557-443e-4c51-c049-5bba7a9850bc
+```
+
+This technique applies when aiming to run a shell pipeline without streaming
+intermediate command output across the network:
+
+```shell-session
+# e.g. find top appearing lines in some output
+$ nomad alloc exec eb17e557 /bin/sh -c 'cat /output | sort | uniq -c | sort -rn | head -n 5'
+...
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected.
+
+```plaintext
+nomad alloc exec -job <job-id> <command> [<args>...]
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
+
+## Disabling remote execution
+
+`alloc exec` is enabled by default to aid with debugging. Operators can disable
+the feature by setting [`disable_remote_exec` client config
+option][disable_remote_exec_flag] on all clients, or a subset of clients that
+run sensitive workloads.
+
+## Exec targeting a specific task
+
+When trying to `alloc exec` for a job that has more than one task associated
+with it, you may want to target a specific task.
+
+```shell-session
+# open a shell session in one of your allocation's tasks
+$ nomad alloc exec -i -t -task mytask a1827f93 /bin/bash
+a1827f93$
+```
+
+[heredoc]: http://tldp.org/LDP/abs/html/here-docs.html
+[disable_remote_exec_flag]: /nomad/docs/configuration/client#disable_remote_exec
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/fs.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/fs.mdx
new file mode 100644
index 0000000000..c5e39f98f1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/fs.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'nomad alloc fs command reference'
+description: |
+  The `nomad alloc fs` lets you navigate an allocation working directory on a Nomad client.
+---
+
+# `nomad alloc fs` command reference
+
+**Alias: `nomad fs`**
+
+The `alloc fs` command allows a user to navigate an [allocation working
+directory] on a Nomad client. The following functionalities are available -
+`cat`, `tail`, `ls` and `stat`.
+
+- `cat`: If the target path is a file, Nomad will `cat` the file.
+
+- `tail`: If the target path is a file and `-tail` flag is specified, Nomad will
+  `tail` the file.
+
+- `ls`: If the target path is a directory, Nomad displays the name of a file and
+  directories and their associated information.
+
+- `stat`: If the `-stat` flag is used, Nomad will display information about a
+  file.
+
+## Usage
+
+```plaintext
+nomad alloc fs [options] <allocation> <path>
+```
+
+This command accepts a single allocation ID (unless the `-job` flag is
+specified, in which case an allocation is chosen from the given job) and a
+path. The path is optional and relative to the root of the [allocation working
+directory].
+
+When ACLs are enabled, this command requires a token with the `read-fs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Fs options
+
+- `-H`: Machine friendly output.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-stat`: Show stat information instead of displaying the file, or listing the
+  directory.
+
+- `-f`: Causes the output to not stop when the end of the file is reached, but
+  rather to wait for additional output.
+
+- `-tail`: Show the files contents with offsets relative to the end of the file.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the file.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the file.
+
+## Examples
+
+```shell-session
+$ nomad alloc fs eb17e557
+Mode        Size  Modified Time        Name
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  alloc/
+drwxrwxr-x  4096  28 Jan 16 05:39 UTC  redis/
+-rw-rw-r--  0     28 Jan 16 05:39 UTC  redis_exit_status
+
+
+$ nomad alloc fs eb17e557 redis/local
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  0     28 Jan 16 05:39 UTC  redis.stderr
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs -stat eb17e557 redis/local/redis.stdout
+Mode        Size  Modified Time        Name
+-rw-rw-rw-  17    28 Jan 16 05:39 UTC  redis.stdout
+
+
+$ nomad alloc fs eb17e557 redis/local/redis.stdout
+foobar
+baz
+
+$ nomad alloc fs -tail -f -n 3 eb17e557 redis/local/redis.stdout
+foobar
+baz
+bam
+<blocking>
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc fs -job <job-id> <path>
+```
+
+This can be useful for debugging a job that has multiple allocations, and it is
+not required to observe a specific allocation.
+
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/index.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/index.mdx
new file mode 100644
index 0000000000..a95746aad5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad alloc command reference'
+description: |
+  The `nomad alloc` commands interact with allocations. Access allocation directories, display status and health checks, stream task logs, run commands inside an allocation, and signal a running allocation. You can also stop, reschedule, and restart a running allocation.
+---
+
+# `nomad alloc` command reference
+
+The `alloc` command is used to interact with allocations.
+
+## Usage
+
+Usage: `nomad alloc <subcommand> [options]`
+
+Run `nomad alloc <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`alloc checks`][checks] - Outputs service health check status information.
+- [`alloc exec`][exec] - Run a command in a running allocation
+- [`alloc fs`][fs] - Inspect the contents of an allocation directory
+- [`alloc logs`][logs] - Streams the logs of a task
+- [`alloc restart`][restart] - Restart a running allocation or task
+- [`alloc signal`][signal] - Signal a running allocation
+- [`alloc status`][status] - Display allocation status information and metadata
+- [`alloc stop`][stop] - Stop and reschedule a running allocation
+
+[checks]: /nomad/docs/commands/alloc/checks 'Outputs service health check status information'
+[exec]: /nomad/docs/commands/alloc/exec 'Run a command in a running allocation'
+[fs]: /nomad/docs/commands/alloc/fs 'Inspect the contents of an allocation directory'
+[logs]: /nomad/docs/commands/alloc/logs 'Streams the logs of a task'
+[restart]: /nomad/docs/commands/alloc/restart 'Restart a running allocation or task'
+[signal]: /nomad/docs/commands/alloc/signal 'Signal a running allocation'
+[status]: /nomad/docs/commands/alloc/status 'Display allocation status information and metadata'
+[stop]: /nomad/docs/commands/alloc/stop 'Stop and reschedule a running allocation'
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/logs.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/logs.mdx
new file mode 100644
index 0000000000..5883801965
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/logs.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: 'nomad alloc logs command reference'
+description: |
+  The `nomad alloc logs` command streams the task logs from an allocation.
+---
+
+# `nomad alloc logs` command reference
+
+**Alias: `nomad logs`**
+
+The `alloc logs` command displays the log of a given task.
+
+## Usage
+
+```plaintext
+nomad alloc logs [options] <allocation> <task>
+```
+
+This command streams the logs of the given task in the allocation. If the
+allocation is only running a single task, the task name can be omitted.
+Optionally, the `-job` option may be used in which case a random allocation from
+the given job will be chosen.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the `read-logs`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Logs options
+
+- `-stdout`: Display stdout logs. This is used as the default value in all
+  commands except when using the `-f` flag where both stdout and stderr are
+  used as default.
+
+- `-stderr`: Display stderr logs.
+
+- `-verbose`: Display verbose output.
+
+- `-job`: Use a random allocation from the specified job or job ID prefix,
+  preferring a running allocation.
+
+- `-task`: Specify the task to view the logs.
+
+- `-f`: Causes the output to not stop when the end of the logs are reached, but
+  rather to wait for additional output. When supplied with no other flags except
+  optionally `-job` and `-task`, both stdout and stderr logs will be followed.
+
+- `-tail`: Show the logs contents with offsets relative to the end of the logs.
+  If no offset is given, -n is defaulted to 10.
+
+- `-n`: Sets the tail location in best-efforted number of lines relative to the
+  end of the logs.
+
+- `-c`: Sets the tail location in number of bytes relative to the end of the
+  logs.
+
+Note that the `-no-color` option applies to Nomad's own output. If the task's
+logs include terminal escape sequences for color codes, Nomad will not remove
+them.
+
+## Examples
+
+```shell-session
+$ nomad alloc logs eb17e557 redis
+foobar
+baz
+bam
+
+$ nomad alloc logs -stderr eb17e557 redis
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -job example
+[ERR]: foo
+[ERR]: bar
+
+$ nomad alloc logs -tail -n 2 eb17e557 redis
+foobar
+baz
+
+$ nomad alloc logs -tail -f -n 3 eb17e557 redis
+foobar
+baz
+bam
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will output the logs from the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc logs -task redis eb17e557 api
+```
+
+## Using Job ID instead of Allocation ID
+
+Setting the `-job` flag causes a random allocation of the specified job to be
+selected. Nomad will prefer to select a running allocation ID for the job, but
+if no running allocations for the job are found, Nomad will use a dead
+allocation.
+
+```plaintext
+nomad alloc logs -job <job-id> <task>
+```
+
+Choosing a specific allocation is useful for debugging issues with a specific
+instance of a service. For other operations using the `-job` flag may be more
+convenient than looking up an allocation ID to use.
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/pause.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/pause.mdx
new file mode 100644
index 0000000000..52a231e8f7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/pause.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: 'nomad alloc pause command reference'
+description: |
+  The `nomad alloc pause` command overrides the schedule for tasks using time-based execution, forcing the task to either stop or run.
+---
+
+# `nomad alloc pause` command reference
+
+Override the schedule for tasks using time based execution.
+
+<EnterpriseAlert />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes.
+
+## Usage
+
+```plaintext
+nomad alloc pause [options] <allocation> <command>
+```
+
+The `alloc pause` command allows a user to override the schedule for tasks
+that use time based execution. A user may override a task's
+[`schedule`][schedule] and force it to run or stop. The `schedule` will be
+ignored until a user resets the override.
+
+When ACLs are enabled, this command requires the `job-submit` capability for
+the allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Pause options
+
+- `-state`: Override the current scheduled task state to be the specified state
+  or reset to the scheduled state. Must be one of `pause`, `run`, or
+  `scheduled`. When set to `pause` the task is halted. When set to `run` the
+  task is started. When set to `scheduled` the task respects its
+  [`schedule`][schedule].
+
+- `-status`: Get the current time based task execution state.
+
+- `-task`: Override the schedule of the specified task. May also be specified
+  as a positional argument.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+The following command stops the `schedtask` task of the allocation `4d37a9d1`
+overriding the task's [`schedule`][schedule] block:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command runs the task overriding the tasks current state or
+schedule:
+
+```shell-session
+$ nomad alloc pause -state=pause 4d37a9d1 schedtask
+```
+
+The following command returns the task to its [`schedule`][schedule]:
+
+```shell-session
+$ nomad alloc pause -state=scheduled 4d37a9d1 schedtask
+```
+
+[schedule]: /nomad/docs/job-specification/schedule
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/restart.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/restart.mdx
new file mode 100644
index 0000000000..581d49d403
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/restart.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad alloc restart command reference'
+description: |
+  The `nomad alloc restart` command restarts a running task or an entire allocation.
+---
+
+# `nomad alloc restart` command reference
+
+The `alloc restart` command allows a user to perform an in place restart of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc restart [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted all tasks that are currently running will be
+restarted.
+
+Task name may also be specified using the `-task` option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+Use the option `-all-tasks` to restart tasks that have already run, such as
+non-sidecar prestart and poststart tasks.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Restart options
+
+- `-all-tasks`: If set, all tasks in the allocation will be restarted, even the
+  ones that already ran. This option cannot be used with `-task` or the
+  `<task>` argument.
+
+- `-task`: Specify the individual task to restart. This option cannot be used
+  with `-all-tasks`.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc restart eb17e557
+
+$ nomad alloc restart eb17e557 foo
+Could not find task named: foo, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will restart the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc restart -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/signal.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/signal.mdx
new file mode 100644
index 0000000000..37a3868203
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/signal.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad alloc signal command reference'
+description: |
+  The `nomad alloc signal` command sends a signal to a running allocation or task.
+---
+
+# `nomad alloc signal` command reference
+
+The `alloc signal` command allows a user to perform an in place signal of an
+an entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc signal [options] <allocation> <task>
+```
+
+This command accepts a single allocation ID and a task name. The task name must
+be part of the allocation and the task must be currently running. The task name
+is optional and if omitted every task in the allocation will be signaled.
+
+Task name may also be specified using the `-task`  option rather than a command
+argument. If task name is given with both an argument and the `-task` option,
+preference is given to the `-task` option.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Signal options
+
+- `-s`: Signal to send to the tasks. Valid options depend on the driver.
+
+- `-task`: Specify the individual task that will receive the signal.
+
+- `-verbose`: Display verbose output.
+
+## Examples
+
+```shell-session
+$ nomad alloc signal eb17e557
+
+$ nomad alloc signal eb17e557 redis
+Could not find task named: redis, found:
+* test
+<blocking>
+```
+
+Specifying task name with the `-task` option:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557
+```
+
+If task name is specified using both options, the command argument is ignored.
+The following will signal the "redis" task only, not the "api" task:
+
+```shell-session
+$ nomad alloc signal -task redis eb17e557 api
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/status.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/status.mdx
new file mode 100644
index 0000000000..827c38f13f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/status.mdx
@@ -0,0 +1,182 @@
+---
+layout: docs
+page_title: 'nomad alloc status command reference'
+description: |
+  The `nomad alloc status` command display status and metadata about existing allocations and their tasks.
+---
+
+# `nomad alloc status` command reference
+
+The `alloc status` command displays status information and metadata
+about an existing allocation and its tasks. It can be useful while
+debugging to reveal the underlying reasons for scheduling decisions or
+failures, as well as the current state of its tasks.
+
+## Usage
+
+```plaintext
+nomad alloc status [options] <allocation>
+```
+
+An allocation ID or prefix must be provided. If there is an exact match, the
+full details of the allocation will be displayed. Otherwise, a list of matching
+allocations and information will be displayed.
+
+When ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Alloc Status options
+
+- `-short`: Display short output. Shows only the most recent task event.
+- `-verbose`: Show full information.
+- `-json` : Output the allocation in its JSON format.
+- `-t` : Format and display the allocation using a Go template.
+
+## Examples
+
+Short status of an alloc:
+
+```shell-session
+$ nomad alloc status --short 0af996ed
+ID                  = 0af996ed
+Eval ID             = be9bde98
+Name                = example.cache[0]
+Node ID             = 43c0b14e
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 07/25/17 16:12:48 UTC
+Deployment ID       = 0c83a3b1
+Deployment Health   = healthy
+
+Tasks
+Name   State    Last Event  Time
+redis  running  Started     07/25/17 16:12:48 UTC
+web    running  Started     07/25/17 16:12:49 UTC
+```
+
+Full status of an alloc, which shows one of the tasks dying and then being restarted:
+
+```shell-session
+$ nomad alloc status 0af996ed
+ID                   = 0af996ed
+Eval ID              = be9bde98
+Name                 = example.cache[0]
+Node ID              = 43c0b14e
+Job ID               = example
+Job Version          = 0
+Client Status        = running
+Client Description   = <none>
+Desired Status       = run
+Desired Description  = <none>
+Created              = 5m ago
+Modified             = 5m ago
+Deployment ID        = 0c83a3b1
+Deployment Health    = healthy
+Replacement Alloc ID = 0bc894ca
+Reschedule Attempts  = 1/3
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+CSI Volumes:
+ID            Plugin  Provider  Schedulable  Mount options
+vol-4150af42  ebs0    aws.ebs   true         <none>
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
+
+Verbose status can also be accessed:
+
+```shell-session
+$ nomad alloc status -verbose 0af996ed
+ID                     = 0af996ed-aff4-8ddb-a566-e55ebf8969c9
+Eval ID                = be9bde98-0490-1beb-ced0-012d10ddf22e
+Name                   = example.cache[0]
+Node ID                = 43c0b14e-7f96-e432-a7da-06605257ce0c
+Job ID                 = example
+Job Version            = 0
+Client Status          = running
+Client Description     = <none>
+Desired Status         = run
+Desired Description    = <none>
+Created                = 07/25/17 16:12:48 UTC
+Modified               = 07/25/17 16:12:48 UTC
+Deployment ID          = 0c83a3b1-8a7b-136b-0e11-8383dc6c9276
+Deployment Health      = healthy
+Reschedule Eligibility = 2m from now
+Evaluated Nodes        = 1
+Filtered Nodes         = 0
+Exhausted Nodes        = 0
+Allocation Time        = 38.474µs
+Failures               = 0
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:27908
+
+Task Events:
+Started At     = 07/25/17 16:12:48 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:48 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+
+Task "web" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+1/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:30572
+
+Task Events:
+Started At     = 07/25/17 16:12:49 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+07/25/17 16:12:49 UTC  Started     Task started by client
+07/25/17 16:12:48 UTC  Task Setup  Building Task Directory
+07/25/17 16:12:48 UTC  Received    Task received by client
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/alloc/stop.mdx b/content/nomad/v1.9.x/content/docs/commands/alloc/stop.mdx
new file mode 100644
index 0000000000..ac35ae31a9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/alloc/stop.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad alloc stop command reference'
+description: |
+  The `nomad alloc stop` command perform an in-place restart of an entire allocation or an individual task.
+---
+
+# `nomad alloc stop` command reference
+
+The `alloc stop` command allows a user to perform an in-place restart of an
+entire allocation or individual task.
+
+## Usage
+
+```plaintext
+nomad alloc stop [options] <allocation>
+```
+
+The `alloc stop` command requires a single argument, specifying the alloc ID or
+prefix to stop. If there is an exact match based on the provided alloc ID or
+prefix, then the alloc will be stopped, otherwise, a list of
+matching allocs and information will be displayed. If the stopped allocation
+belongs to a service or batch job they will rescheduled according to their
+reschedule policy. [System allocs will not][] and will show up as completed.
+
+Stop will issue a request to stop and reschedule the allocation. An interactive
+monitoring session will display log lines as the allocation completes shutting
+down. It is safe to exit the monitor early with ctrl-c.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle`, `read-job`, and `list-jobs` capabilities for the
+allocation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Stop options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  stop command is submitted, a new evaluation ID is printed to the
+  screen, which can be used to examine the rescheduling evaluation using the
+  [eval status] command.
+
+- `-verbose`: Display verbose output.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocation being stopped.
+
+## Examples
+
+```shell-session
+$ nomad alloc stop c1488bb5
+==> Monitoring evaluation "26172081"
+    Evaluation triggered by job "example"
+    Allocation "4dcb1c98" created: node "b4dc52b9", group "cache"
+    Evaluation within deployment: "c0c594d0"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "26172081" finished with status "complete"
+
+$ nomad alloc stop -detach eb17e557
+8a91f0f3-9d6b-ac83-479a-5aa186ab7795
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
+[system allocs will not]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/commands/config/index.mdx b/content/nomad/v1.9.x/content/docs/commands/config/index.mdx
new file mode 100644
index 0000000000..f71d297b73
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/config/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: 'nomad config command reference'
+description: |
+  The `nomad config` command interacts with configurations. Validate configuration files.
+---
+
+# `nomad config` command reference
+
+The `config` command is used to interact with configurations.
+
+## Usage
+
+Usage: `nomad config <subcommand> [options]`
+
+Run `nomad config <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`config validate`][validate] - Validate configuration files
+
+[validate]: /nomad/docs/commands/config/validate 'Validate configuration files'
diff --git a/content/nomad/v1.9.x/content/docs/commands/config/validate.mdx b/content/nomad/v1.9.x/content/docs/commands/config/validate.mdx
new file mode 100644
index 0000000000..871b35d4a5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/config/validate.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: 'nomad config validate command reference'
+description: |
+  The `nomad config validate` command validates Nomad configuration files so you can test Nomad configuration without starting the agent.
+---
+
+# `nomad config validate` command reference
+
+The `config validate` command performs validation on a set of Nomad
+configuration files. This is useful to test the Nomad configuration
+without starting the agent.
+
+## Usage
+
+```plaintext
+nomad config validate <config_path> [<config_path...>]
+```
+
+The `config validate` command requires a path to either a single
+configuration file or a directory of configuration files to use for
+configuring the Nomad agent. This option can be specified multiple
+times. If multiple config files are passed, the values from each will
+be merged together. During merging, values from files found later in
+the list are merged over values from previously parsed files.
+
+This command cannot operate on partial configuration fragments since
+those won't pass the full agent validation. This command does not
+require an ACL token.
+
+Returns 0 if the configuration is valid, or 1 if there are problems.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Validate a configuration file:
+
+```shell-session
+$ nomad config validate ./nomad.hcl
+Configuration is valid!
+```
+
+Validate a directory of configuration files:
+
+```shell-session
+$ nomad config validate /etc/nomad.d
+Configuration is valid!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/fail.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/fail.mdx
new file mode 100644
index 0000000000..f1bbb7e15a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/fail.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad deployment fail command reference'
+description: |
+  The `nomad deployment fail` command manually fails a deployment, which stops the placement of new allocations.
+---
+
+# `nomad deployment fail` command reference
+
+The `deployment fail` command is used to mark a deployment as failed. Failing a
+deployment will stop the placement of new allocations as part of rolling
+deployment and if the job is configured to auto revert, the job will attempt to
+roll back to a stable version.
+
+## Usage
+
+```plaintext
+nomad deployment fail [options] <deployment id>
+```
+
+The `deployment fail` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Fail options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as failed:
+
+```shell-session
+$ nomad deployment fail 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = failed
+Description = Deployment marked as failed
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/index.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/index.mdx
new file mode 100644
index 0000000000..8b935e06cc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad deployment command reference'
+description: |
+  The `nomad deployment` command interacts with deployments. List deployments, fetch status, and promote canaries. Pause, resume, and fail deployments.
+---
+
+# `nomad deployment` command reference
+
+The `deployment` command is used to interact with deployments.
+
+## Usage
+
+Usage: `nomad deployment <subcommand> [options]`
+
+Run `nomad deployment <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`deployment fail`][fail] - Manually fail a deployment
+- [`deployment list`][list] - List all deployments
+- [`deployment pause`][pause] - Pause a deployment
+- [`deployment promote`][promote] - Promote canaries in a deployment
+- [`deployment resume`][resume] - Resume a paused deployment
+- [`deployment status`][status] - Display the status of a deployment
+
+[fail]: /nomad/docs/commands/deployment/fail 'Manually fail a deployment'
+[list]: /nomad/docs/commands/deployment/list 'List all deployments'
+[pause]: /nomad/docs/commands/deployment/pause 'Pause a deployment'
+[promote]: /nomad/docs/commands/deployment/promote 'Promote canaries in a deployment'
+[resume]: /nomad/docs/commands/deployment/resume 'Resume a paused deployment'
+[status]: /nomad/docs/commands/deployment/status 'Display the status of a deployment'
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/list.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/list.mdx
new file mode 100644
index 0000000000..9b728778fc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad deployment list command reference'
+description: |
+  The `nomad deployment list` command lists deployments.
+---
+
+# `nomad deployment list` command reference
+
+The `deployment list` command is used list all deployments.
+
+## Usage
+
+```plaintext
+nomad deployment list [options]
+```
+
+The `deployment list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-json` : Output the deployments in their JSON format.
+- `-filter`: Specifies an expression used to filter query results.
+- `-t` : Format and display the deployments using a Go template.
+- `-verbose`: Show full information.
+
+## Examples
+
+List all tracked deployments:
+
+```shell-session
+$ nomad deployment list
+ID        Job ID   Job Version  Status      Description
+8990cfbc  example  2            failed      Deployment marked as failed
+62eb607c  example  1            successful  Deployment completed successfully
+5f271fe2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/pause.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/pause.mdx
new file mode 100644
index 0000000000..8b44143a39
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/pause.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad deployment pause command reference'
+description: >
+  The `nomad deployment pause` command pauses a deployment and does not allow new allocations.
+---
+
+# `nomad deployment pause` command reference
+
+The `deployment pause` command is used to pause a deployment. Pausing a
+deployment will pause the placement of new allocations as part of rolling
+deployment.
+
+## Usage
+
+```plaintext
+nomad deployment pause [options] <deployment id>
+```
+
+The `deployment pause` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Pause options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually pause a deployment:
+
+```shell-session
+$ nomad deployment pause 2f14ba55
+Deployment "2f14ba55-acfb-cb31-821c-facf1b9b0830" paused
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/promote.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/promote.mdx
new file mode 100644
index 0000000000..44aa3be733
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/promote.mdx
@@ -0,0 +1,226 @@
+---
+layout: docs
+page_title: 'nomad deployment promote command reference'
+description: |
+  The `nomad deployment promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad deployment promote` command reference
+
+The `deployment promote` command is used to promote task groups in a deployment.
+Promotion should occur when the deployment has placed canaries for a task group
+and those canaries have been deemed healthy. When a task group is promoted, the
+rolling upgrade of the remaining allocations is unblocked. If the canaries are
+found to be unhealthy, the deployment may either be failed using the "nomad
+deployment fail" command, the job can be failed forward by submitting a new
+version or failed backwards by reverting to an older version using the
+[`job revert`] command.
+
+## Usage
+
+```plaintext
+nomad deployment promote [options] <deployment id>
+```
+
+The `deployment promote` command requires a single argument, a deployment ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Promote options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups within the deployment
+$ nomad deployment promote 9fa81f27
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad deployment promote -group cache a6b87a6c
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[`job revert`]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/resume.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/resume.mdx
new file mode 100644
index 0000000000..4bbcc4f303
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/resume.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: 'nomad deployment resume command reference'
+description: |
+  The `nomad deployment resume` command resumes a paused deployment.
+---
+
+# `nomad deployment resume` command reference
+
+The `deployment resume` command is used to unpause a paused deployment.
+Resuming a deployment will resume the placement of new allocations as part of
+rolling deployment.
+
+## Usage
+
+```plaintext
+nomad deployment resume [options] <deployment id>
+```
+
+The `deployment resume` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Resume options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually resume a deployment:
+
+```shell-session
+$ nomad deployment resume c848972e
+Deployment "c848972e-dcd3-7354-e0d2-39d86642cdb1" resumed
+
+==> Monitoring evaluation "5e266d42"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "c848972e"
+    Allocation "00208424" created: node "6240eed6", group "web"
+    Allocation "68c72edf" created: node "6240eed6", group "cache"
+    Allocation "00208424" status changed: "pending" -> "running"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "5e266d42" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/status.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/status.mdx
new file mode 100644
index 0000000000..404cd5a862
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/status.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: 'nomad deployment status command reference'
+description: |
+  The `nomad deployment status` command displays the status of a deployment.
+---
+
+# `nomad deployment status` command reference
+
+The `deployment status` command is used to display the status of a deployment.
+The status will display the number of desired changes as well as the currently
+applied changes.
+
+## Usage
+
+```plaintext
+nomad deployment status [options] <deployment id>
+```
+
+The `deployment status` command requires a single argument, a deployment ID or
+prefix.
+
+A `-monitor` flag can be used to update the current deployment status until completion.
+When combined with `-verbose`, it will also display the allocations for the given
+deployment. If the deployment fails and [`auto_revert`] is set to `true`, it will monitor
+the entire process, showing the failure and then monitoring the deployment of the rollback.
+
+When ACLs are enabled, this command requires a token with the 'read-job'
+capability for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Status options
+
+- `-json` : Output the deployment in its JSON format.
+- `-t` : Format and display the deployment using a Go template.
+- `-verbose`: Show full information.
+- `-monitor`: Enter monitor mode to poll for updates to the deployment status.
+- `-wait`: How long to wait before polling an update, used in conjunction with monitor
+    mode. Defaults to 2s.
+
+## Examples
+
+Inspect the status of a complete deployment:
+
+```shell-session
+$ nomad deployment status 06ca68a2
+ID          = 06ca68a2
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+cache       2        2       2        0          2021-06-09T15:20:27-07:00
+web         2        2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Inspect the status of a deployment that is waiting for canary promotion:
+
+```shell-session
+$ nomad deployment status 0b
+ID          = 0b23b149
+Job ID      = example
+Job Version = 1
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy  Progress Deadline
+cache       false     2        1         1       0        0          2021-06-09T15:20:27-07:00
+web         N/A       2        0         2       2        0          2021-06-09T15:20:27-07:00
+```
+
+Monitor the status of a deployment and its allocations:
+
+```shell-session
+$ nomad deployment status -monitor -verbose dab
+2021-06-09T15:10:38-07:00: Monitoring deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6"
+  ⠙ Deployment "da9bfc23-576f-be32-61c9-0f9997fe70a6" in progress...
+
+    2021-06-09T15:10:40-07:00
+    ID          = da9bfc23-576f-be32-61c9-0f9997fe70a6
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:20:27-07:00
+    web         1        1       1        0          2021-06-09T15:20:27-07:00
+
+    Allocations
+    ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+    9e1b4cb9-35c4-49f3-3ccb-1cb10a5a5aa6  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:31-07:00
+    bd0a8773-0d37-bca6-6ca1-2d9c8473bdf8  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  cache       0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:29-07:00
+    ee873095-8e76-7d4f-095f-b80ce5712d9b  e337d747-f59e-329e-4718-46edcc293695  70279742-b106-c487-315f-fb583e13178e  mbp.local  web         0        run      running  2021-06-09T15:10:17-07:00  2021-06-09T15:10:27-07:00
+```
+
+Monitor the status of a deployment that fails and has `auto_revert` set to `true`:
+
+```shell-session
+$ nomad deployment status -monitor e45
+2021-06-09T15:49:19-07:00: Monitoring deployment "e45cc3c1"
+  ! Deployment "e45cc3c1" failed
+
+    2021-06-09T15:49:48-07:00
+    ID          = e45cc3c1
+    Job ID      = example
+    Job Version = 1
+    Status      = failed
+    Description = Failed due to progress deadline - rolling back to job version 0
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        1       0        1          2021-06-09T15:49:48-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:28-07:00
+
+  ⠙ Deployment "e094a0be" in progress...
+
+    2021-06-09T15:50:02-07:00
+    ID          = e094a0be
+    Job ID      = example
+    Job Version = 2
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Auto Revert  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       true         2        2       1        0          2021-06-09T15:52:00-07:00
+    web         false        1        1       1        0          2021-06-09T15:59:58-07:00
+```
+
+**Please note**: The library used for updating terminal output in place currently isn't fully 
+Windows compatible so there may be some formatting differences (different margins, no spinner 
+indicating deployment is in progress).
+
+[`auto_revert`]: /nomad/docs/job-specification/update#auto_revert
\ No newline at end of file
diff --git a/content/nomad/v1.9.x/content/docs/commands/deployment/unblock.mdx b/content/nomad/v1.9.x/content/docs/commands/deployment/unblock.mdx
new file mode 100644
index 0000000000..5803b5f582
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/deployment/unblock.mdx
@@ -0,0 +1,75 @@
+---
+layout: docs
+page_title: 'nomad deployment unblock command reference'
+description: |
+  The`nomad deployment unblock` command marks a blocked multi-region deployment as successful so you can force completion when there is a failed peer region.
+---
+
+# `nomad deployment unblock` command reference
+
+The `deployment unblock` command is used to manually mark a blocked
+multiregion deployment as successful. A blocked deployment is a multiregion
+deployment within a region that has completed within a region but is waiting
+on the other [federated regions]. The `deployment unblock` command can be used
+in cases where a failed peer region is unable to communicate its failed
+deployment status to other regions to force a deployment to complete.
+
+## Usage
+
+```plaintext
+nomad deployment unblock [options] <deployment id>
+```
+
+The `deployment unblock` command requires a single argument, a deployment ID or
+prefix.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the deployment's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Unblock options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Manually mark an ongoing deployment as unblocked. The deployment status shows
+an error on the unreachable "east" region.
+
+```shell-session
+$ nomad deployment unblock 8990cfbc
+Deployment "8990cfbc-28c0-cb28-ca31-856cf691b987" unblocked
+
+==> Monitoring evaluation "a2d97ad5"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "8990cfbc"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "a2d97ad5" finished with status "complete"
+
+$ nomad deployment status 8990cfbc
+ID          = 8990cfbc
+Job ID      = example
+Job Version = 2
+Status      = successful
+Description = Deployment successful
+
+Multi-region Deployment
+Region        ID        Status
+west          8990cfbc  successful
+south         085787e3  blocked
+east (error)  <none>    <none>
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       3        2       1        0
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[federated regions]: /nomad/tutorials/manage-clusters/federation
diff --git a/content/nomad/v1.9.x/content/docs/commands/eval/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/eval/delete.mdx
new file mode 100644
index 0000000000..2d104f400f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/eval/delete.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad eval delete command reference'
+description: |
+  The `nomad eval delete` command deletes an evaluation by ID or a group of evaluations that match a filter.
+---
+
+# `nomad eval delete` command reference
+
+The `eval delete` command is used to delete evaluations. It should be used
+cautiously and only in outage situations where there is a large backlog of
+evaluations not being processed. During most normal and outage scenarios,
+Nomad's reconciliation and state management will handle evaluations as needed.
+
+The eval broker is expected to be paused prior to running this command and
+un-paused after. These actions can be performed by the
+[`operator scheduler get-config`][scheduler_get_config]
+and [`operator scheduler set-config`][scheduler_set_config] commands respectively.
+
+## Usage
+
+```plaintext
+nomad eval delete [options] [args]
+```
+
+It takes an optional argument which is the ID of the evaluation to delete. If
+the evaluation ID is omitted, this command will use the filter flag to identify
+and delete a set of evaluations.
+
+When ACLs are enabled, this command requires a `management` token.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Delete options
+
+- `-filter`: Specifies an expression used to filter evaluations by for
+  deletion. When using this flag, it is advisable to ensure the syntax is
+  correct using the eval list command first. Note that deleting evals by filter
+  is imprecise: for sets of evals larger than a single raft log batch, evals can
+  be inserted behind the cursor and therefore be missed.
+
+- `-yes`: Bypass the confirmation prompt if an evaluation ID was not provided.
+
+## Examples
+
+Delete an evaluation using its ID:
+
+```shell-session
+$ nomad eval delete 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+Successfully deleted 1 evaluation
+```
+
+Delete all evaluations with status `pending` for the `example` job:
+
+```shell-session
+$ nomad eval delete -filter='Status == "pending" and JobID == "example"'
+Are you sure you want to delete 3 evals? [y/N] y
+
+Successfully deleted 3 evaluations
+```
+
+Delete all evaluations for the `system` and `service` whilst skipping all
+prompts:
+
+```shell-session
+$ nomad eval delete -filter='Scheduler == "system" or Scheduler == "service"' -yes
+Successfully deleted 23 evaluations
+```
+
+[scheduler_get_config]: /nomad/docs/commands/operator/scheduler/get-config
+[scheduler_set_config]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.9.x/content/docs/commands/eval/index.mdx b/content/nomad/v1.9.x/content/docs/commands/eval/index.mdx
new file mode 100644
index 0000000000..eea008188a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/eval/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'nomad eval command reference'
+description: |
+  The `nomad eval` command interact with evaluations. Fetch status, delete an evaluation, and list all evaluations.
+---
+
+# `nomad eval` command reference
+
+The `eval` command is used to interact with evals.
+
+## Usage
+
+Usage: `nomad eval <subcommand> [options]`
+
+Run `nomad eval <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+- [`eval delete`][delete] - Delete evals
+- [`eval list`][list] - List all evals
+- [`eval status`][status] - Display the status of a eval
+
+[delete]: /nomad/docs/commands/eval/delete 'Delete evals'
+[list]: /nomad/docs/commands/eval/list 'List all evals'
+[status]: /nomad/docs/commands/eval/status 'Display the status of a eval'
diff --git a/content/nomad/v1.9.x/content/docs/commands/eval/list.mdx b/content/nomad/v1.9.x/content/docs/commands/eval/list.mdx
new file mode 100644
index 0000000000..871bf62d29
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/eval/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad eval list command reference'
+description: |
+  The `nomad eval list` command displays a list of all evaluations or evaluations that match a filter.
+---
+
+# `nomad eval list` command reference
+
+The `eval list` command is used list all evaluations.
+
+## Usage
+
+```plaintext
+nomad eval list [options]
+```
+
+The `eval list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the requested namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-verbose`: Show full information.
+- `-per-page`: How many results to show per page.
+- `-page-token`: Where to start pagination.
+- `-filter`: Specifies an expression used to filter query results.
+- `-job`: Only show evaluations for this job ID.
+- `-status`: Only show evaluations with this status.
+- `-json`: Output the evaluation in its JSON format.
+- `-t`: Format and display evaluation using a Go template.
+
+## Examples
+
+List all tracked evaluations:
+
+```shell-session
+$ nomad eval list -per-page 3 -status complete
+ID        Priority  Triggered By        Job ID   Namespace  Node ID  Status    Placement Failures
+456e37aa  50        deployment-watcher  example  default    <none>   complete  false
+1a1eafe6  50        alloc-stop          example  default    <node>   complete  false
+3411e37b  50        job-register        example  default    <node>   complete  false
+
+Results have been paginated. To get the next page run:
+
+nomad eval list -page-token 9ecffbba-73be-d909-5d7e-ac2694c10e0c
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/eval/status.mdx b/content/nomad/v1.9.x/content/docs/commands/eval/status.mdx
new file mode 100644
index 0000000000..31e1b3902d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/eval/status.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'nomad eval status command reference'
+description: >
+  The `nomad eval status` command displays the status and potential failed
+  allocations of an evaluation. Use with the `monitor` flag to start an interactive monitoring session.
+---
+
+# `nomad eval status` command reference
+
+The `eval status` command is used to display information about an existing
+evaluation. In the case an evaluation could not place all the requested
+allocations, this command can be used to determine the failure reasons.
+
+Optionally, it can also be invoked in a monitor mode to track an outstanding
+evaluation. In this mode, logs will be output describing state changes to the
+evaluation or its associated allocations. The monitor will exit when the
+evaluation reaches a terminal state.
+
+## Usage
+
+```plaintext
+nomad eval status [options] <evaluation>
+```
+
+An evaluation ID or prefix must be provided. If there is an exact match, the
+the status will be shown. Otherwise, a list of matching evaluations and
+information will be displayed.
+
+If the `-monitor` flag is passed, an interactive monitoring session will be
+started in the terminal. It is safe to exit the monitor at any time using
+ctrl+c. The command will exit when the given evaluation reaches a terminal
+state (completed or failed). Exit code 0 is returned on successful
+evaluation, and if there are no scheduling problems. If there are
+job placement issues encountered (unsatisfiable constraints,
+resource exhaustion, etc), then the exit code will be 2. Any other
+errors, including client connection issues or internal errors, are
+indicated by exit code 1.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Eval status options
+
+- `-monitor`: Monitor an outstanding evaluation
+- `-verbose`: Show full information.
+- `-json` : Output a list of all evaluations in JSON format. This
+  behavior is deprecated and has been replaced by `nomad eval list
+  -json`. In Nomad 1.4.0 the behavior of this option will change to
+  output only the selected evaluation in JSON.
+- `-t` : Format and display evaluation using a Go template.
+
+## Examples
+
+Show the status of an evaluation that has placement failures
+
+```shell-session
+$ nomad eval status 2ae0e6a5
+ID                 = 2ae0e6a5
+Status             = complete
+Status Description = complete
+Type               = service
+TriggeredBy        = job-register
+Job ID             = example
+Namespace          = default
+Priority           = 50
+Placement Failures = true
+
+==> Failed Placements
+Task Group "cache" (failed to place 1 allocation):
+  * Class "foo" filtered 1 nodes
+  * Constraint "${attr.kernel.name} = windows" filtered 1 nodes
+
+
+Evaluation "67493a64" waiting for additional capacity to place remainder
+```
+
+Monitor an existing evaluation
+
+```shell-session
+$ nomad eval status -monitor 8262bc83
+==> Monitoring evaluation "8262bc83"
+    Allocation "bd6bd0de" created: node "6f299da5", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "8262bc83" finished with status "complete"
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/fmt.mdx b/content/nomad/v1.9.x/content/docs/commands/fmt.mdx
new file mode 100644
index 0000000000..aaa5ad1850
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/fmt.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad fmt command reference'
+description: |
+  The `nomad fmt` commands rewrites Nomad configuration and job specification
+   files to canonical format. Use this command to improve readability and enforce consistency of style in Nomad files.
+---
+
+# `nomad fmt` command reference
+
+The `nomad fmt` command rewrites Nomad configuration and job specification files
+to canonical format. Use this command to improve readability and enforce
+consistency of style in Nomad files.
+
+## Usage
+
+```plaintext
+nomad fmt [options] paths ...
+```
+
+If a path is a directory, the command recursively formats all files with
+`.nomad` and `.hcl` extensions in the directory. If you provide a single dash
+(-) as an argument, the `nomad fmt` command reads from standard input and
+writes the processed text to standard output.
+
+The `nomad fmt` command checks the syntax against
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of Hashicorp Configuration Language. Running this command with
+deprecated HCL1 job specification results in errors.
+
+## `nomad fmt` options
+
+- `-check`: Check if the files are valid HCL files. If not, exit status of the
+  command will be 1 and the incorrect files will not be formatted. This flag
+  overrides any `-write` flag value.
+- `-list`: List the files which contain formatting inconsistencies. Defaults to
+  `-list=true`.
+- `-recursive`: Process files in subdirectories. By default, only the given (or
+	current) directory is processed.
+- `-write`: Overwrite the input files. Defaults to `-write=true`.
+
+## Examples
+
+```shell-session
+$ cat agent.hcl
+server {
+    enabled = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
+
+```shell-session
+$ nomad fmt
+agent.hcl
+```
+
+```shell-session
+$ cat agent.hcl
+server {
+  enabled          = true
+  bootstrap_expect = 1
+}
+
+client {
+  enabled = true
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/index.mdx b/content/nomad/v1.9.x/content/docs/commands/index.mdx
new file mode 100644
index 0000000000..13bc8b105e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/index.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: Nomad command-line interface (CLI) reference
+description: >
+  The Nomad command-line interface (CLI) interacts with a Nomad cluster. This page contains reference information on how to install CLI autocomplete, configure remote usage, and specify CLI options. Review connection, access control list (ACL), mutual TLS (mTLS), and license environment variables.
+---
+
+# Nomad command-line interface (CLI) reference
+
+The Nomad CLI is a well-behaved command-line application. In erroneous cases,
+the CLI returns a non-zero exit status. To view a list of available commands,
+run the `nomad` command with no arguments, `-h`, or `--help`. To access help for
+any specific subcommand, run the subcommand with the `-h` argument.
+
+## Autocomplete
+
+Nomad's CLI supports command autocomplete.
+
+To install autocomplete, run the `nomad` command with the
+`-autocomplete-install` option.
+
+```shell-session
+$ nomad -autocomplete-install
+```
+
+To uninstall autocomplete, run the `nomad` command with the
+`-autocomplete-uninstall` option.
+
+```shell-session
+$ nomad -autocomplete-uninstall
+```
+
+## Command contexts
+
+Nomad's CLI commands have implied contexts in their naming convention. Because
+the CLI is most commonly used to manipulate or query jobs, you can assume that
+any given command is working in that context unless the command name implies
+otherwise. For example, the `nomad job run` command runs a new job and the `nomad status` command queries information about existing jobs. Conversely,
+commands with a prefix in their name likely operate in a different context.
+Examples include the `nomad agent-info` or `nomad node drain` commands,
+which operate in the agent or node contexts respectively.
+
+### Remote usage
+
+You may use the Nomad CLI to interact with a remote Nomad cluster, even when the
+local machine does not have a running Nomad agent. To do so, set the
+`NOMAD_ADDR` environment variable or use the `-address=<addr>` flag when running
+commands.
+
+```shell-session
+$ NOMAD_ADDR=https://remote-address:4646 nomad status
+$ nomad status -address=https://remote-address:4646
+```
+
+The Nomad address must be reachable from your local machine. If the Nomad
+port is exposed to the public internet, we recommend configuring TLS. Refer to
+the [`tls` block in agent configuration] for details.
+
+### Environment variables
+
+Nomad can use environment variables to configure command-line tool options. You
+may override these environment variables with individual flags.
+
+#### Connection environment variables
+
+- `NOMAD_ADDR` - The address of the Nomad server. Defaults to
+  `http://127.0.0.1:4646`.
+
+- `NOMAD_REGION` - The region of the Nomad server to forward commands to.
+  Defaults to the Agent's local region
+
+- `NOMAD_NAMESPACE` - The target namespace for queries and actions bound to a
+  namespace. If set to `*`, job and alloc subcommands query all namespacecs
+  authorized to user. Defaults to the "default" namespace.
+
+- `NOMAD_HTTP_AUTH` - (Optional) This allows users to supply "Basic" HTTP
+  authentication scheme ([RFC 7617](https://tools.ietf.org/html/rfc7617))
+  information in environments where the Nomad API is behind an authenticating
+  proxy server.
+
+#### Access control list (ACL) environment variables
+
+- `NOMAD_TOKEN` - The SecretID of an ACL token to use to authenticate API
+  requests with.
+
+#### CLI environment variables
+
+- `NOMAD_CLI_NO_COLOR` - Disables colored command output.
+
+#### Mutual TLS (mTLS) environment variables
+
+- `NOMAD_CLI_SHOW_HINTS` - Enables ui-hints in common CLI command output.
+
+- `NOMAD_CLIENT_CERT` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `NOMAD_CLIENT_KEY`.
+
+- `NOMAD_CLIENT_KEY` - Path to an unencrypted PEM encoded private key matching
+  the client certificate from `NOMAD_CLIENT_CERT`.
+
+- `NOMAD_CACERT` - Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate.
+
+- `NOMAD_CAPATH` - Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `NOMAD_CACERT` and `NOMAD_CAPATH`
+  are specified, `NOMAD_CACERT` is used.
+
+- `NOMAD_SKIP_VERIFY` - Do not verify TLS certificate. **This is highly not
+  recommended.**
+
+- `NOMAD_TLS_SERVER_NAME` - The server name to use as the SNI host when
+  connecting via TLS.
+
+#### Nomad Enterprise license environment variables
+
+- `NOMAD_LICENSE_PATH` - An absolute path to a Nomad Enterprise license file,
+  for example `/etc/nomad.d/license.hclic`.
+
+- `NOMAD_LICENSE` - The Nomad Enterprise license file contents as a string.
+
+
+[`tls` block in agent configuration]: /nomad/docs/configuration/tls
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/action.mdx b/content/nomad/v1.9.x/content/docs/commands/job/action.mdx
new file mode 100644
index 0000000000..5d6a2fe903
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/action.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: 'nomad job action command reference'
+description: |
+  The `nomad job action` command executes predefined actions from a job
+  specification in a running task context.
+---
+
+# `nomad job action` command reference
+
+**Alias: `nomad action`**
+
+The `job action` command allows operators to execute predefined actions declared
+in Nomad job specifications. These actions can be defined at task level and are
+intended for specific operational tasks, such as clearing a cache, or migrating
+a database.
+
+An action may self-terminate upon completion (for example, echoing a string),
+or run for an indeterminate amount of time (for example, watching a blocking
+query). In the latter case, an action can be terminated via escape character
+(such as cmd+c / ctrl+c)
+
+When ACLs are enabled, this command requires a token with the `alloc-exec`,
+`read-job`, and `list-jobs` capabilities for the allocation's namespace. If
+the task driver does not have file system isolation (as with `raw_exec`),
+this command requires the `alloc-node-exec`, `alloc-exec`, `read-job`, and
+`list-jobs` capabilities for the allocation's namespace.
+
+## Usage
+
+```plaintext
+nomad job action [options] <action>
+```
+
+The `job action` command requires an action name and accepts two ways of
+specifying where it should run:
+- by passing the job name and known allocation ID along with the name of the action
+- by passing the job, task group, and task name along with the name of the action
+(when the allocation ID is not known). A random allocation will be selected if
+multiple are available.
+
+The action name provided must be defined within a task in the [job specification]
+provided. With sufficient privileges, an execution context will be opened and
+the defined action command will be run. No further input is possible, save for
+the escape character to terminate execution, so interactive commands are not
+supported.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Action options
+
+- `-job`: (Required) Specifies the job containing the predefined action.
+
+- `-alloc`: Specifies the allocation within which the action is to be executed.
+  If omitted, `-group` and `-task` must be provided, and a random
+  allocation for the group will be selected.
+
+- `-task`: Specifies the task within the job where the action is defined. This
+  is required either if `-alloc` provided and your group has multiple tasks,
+  or if you specify a `-group`.
+
+- `-group`: Specifies the task group within the job. If present, a random
+  allocation is selected. If omitted, `-alloc` must be provided.
+
+- `-i`: Pass stdin to the action, defaults to `true`. Pass `-i=false` to
+  disable explicitly.
+
+- `-t`: Allocate a pseudo-tty, defaults to `true` if stdin is detected to be a tty
+  session. Pass `-t=false` to disable explicitly.
+
+- `-e` <escape_char>: Sets the escape character for sessions with a pty,
+  defaults to '~'. The escape character is only recognized at the beginning of a
+  line. The escape character followed by a dot (`.`) closes the connection.
+  Setting the character to `none` disables any escapes and makes the session
+  fully transparent.
+
+## Examples
+
+Execute an action within a specific task in a job:
+
+```shell-session
+$ nomad action \
+  -group=my-group \
+  -task=my-task \
+  -job=my-job \
+  weather
+
+Toronto: ☁️   +3°C
+```
+
+Execute an action within a specific allocation:
+
+```shell-session
+$ nomad action \
+  -alloc=f200a789-6da4-504c-d131-6181764f101e \
+  -job=actions-demo \
+  echo-time
+
+Running for 0 seconds
+Running for 1 seconds
+Running for 2 seconds
+Running for 3 seconds
+```
+
+[job specification]: /nomad/docs/job-specification
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/allocs.mdx b/content/nomad/v1.9.x/content/docs/commands/job/allocs.mdx
new file mode 100644
index 0000000000..fbea28bdf6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/allocs.mdx
@@ -0,0 +1,77 @@
+---
+layout: docs
+page_title: 'nomad job allocs command reference'
+description: |
+  The `nomad job allocs`  command lists allocations for a job.
+---
+
+# `nomad job allocs` command reference
+
+The `job allocs` command is used to display the allocations for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job allocs [options] <job>
+```
+
+The `job allocs` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of allocations for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Allocs options
+
+- `-all`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-json`: Output the allocations in JSON format.
+
+- `-t`: Format and display the allocations using a Go template.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+List the allocations for a particular job:
+
+```shell-session
+$ nomad job allocs example
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+c2b4606d  35085106  cache       2        run      running  21s ago   10s ago
+c413424b  35085106  cache       2        run      pending  1m8s ago  11s ago
+```
+
+Verbose listing of allocations for a particular job:
+
+```shell-session
+$ nomad job allocs -verbose example
+ID                                    Eval ID                               Node ID                               Node Name  Task Group  Version  Desired  Status   Created                    Modified
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      running  2021-09-23T14:45:09-04:00  2021-09-23T14:45:19-04:00
+c413424b-d80e-9bc6-ea92-a02b336eaaf5  5e2badb6-b7cf-5177-8281-8fe14f7193d2  35085106-9480-b465-a348-deb745024394  ubuntu     cache       2        run      pending  2021-09-23T14:44:22-04:00  2021-09-23T14:45:19-04:00
+```
+
+Format job allocations using a Go template:
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ println .ID }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+c413424b-d80e-9bc6-ea92-a02b336eaaf5
+```
+
+Use a Go template to filter only allocations which are running
+```shell-session
+$ nomad job allocs -t '{{ range . }}{{ if eq .ClientStatus "running" }}{{ println .ID }}{{ end }}{{ end }}' example
+c2b4606d-1b02-0d8d-5fdd-031167cd4c91
+```
+
+Refer to the [Format Nomad Command Output With Templates][format_tutorial]
+tutorial for more examples of using Go templates to format Nomad CLI output.
+
+[format_tutorial]: /nomad/tutorials/templates/format-output-with-templates
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/deployments.mdx b/content/nomad/v1.9.x/content/docs/commands/job/deployments.mdx
new file mode 100644
index 0000000000..be3d32b0d5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/deployments.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad job deployments command reference'
+description: |
+  The `nomad job deployments` command lists deployments for a job.
+---
+
+# `nomad job deployments` command reference
+
+The `job deployments` command is used to display the deployments for a
+particular job.
+
+## Usage
+
+```plaintext
+nomad job deployments [options] <job>
+```
+
+The `job deployments` command requires a single argument, the job ID or an ID
+prefix of a job to display the list of deployments for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Deployment options
+
+- `-latest`: Display the latest deployment only.
+
+- `-json` : Output the deployment in its JSON format.
+
+- `-t` : Format and display the deployment using a Go template.
+
+- `-verbose`: Show full information.
+
+- `-all`: Display all deployments matching the job ID, even those from an
+  older instance of the job.
+
+## Examples
+
+List the deployment for a particular job:
+
+```shell-session
+$ nomad job deployments example
+ID        Job ID   Job Version  Status      Description
+0b23b149  example  1            running     Deployment is running but requires manual promotion
+06ca68a2  example  0            successful  Deployment completed successfully
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/dispatch.mdx b/content/nomad/v1.9.x/content/docs/commands/job/dispatch.mdx
new file mode 100644
index 0000000000..0ef4fd07b3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/dispatch.mdx
@@ -0,0 +1,166 @@
+---
+layout: docs
+page_title: 'nomad job dispatch command reference'
+description: |
+  The `nomad job dispatch` creates an instance of a parameterized job.
+---
+
+# `nomad job dispatch` command reference
+
+The `job dispatch` command is used to create new instances of a [parameterized
+job]. The parameterized job captures a job's configuration and runtime
+requirements in a generic way and `dispatch` is used to provide the input for
+the job to run against. A parameterized job is similar to a function definition,
+and dispatch is used to invoke the function.
+
+Each time a job is dispatched, a unique job ID is generated. This allows a
+caller to track the status of the job, much like a future or promise in some
+programming languages.
+
+## Usage
+
+```plaintext
+nomad job dispatch [options] <parameterized job> [input source]
+```
+
+Dispatch creates an instance of a parameterized job. A data payload to the
+dispatched instance can be provided via stdin by using "-" for the input source
+or by specifying a path to a file. Metadata can be supplied by using the meta
+flag one or more times.
+
+The payload has a **size limit of 16384 bytes (16KiB)**.
+
+An optional idempotency token can be specified to prevent dispatching more than
+one instance of the same job. The token can have any value and will be matched
+with existing jobs. If an instance with the same token already exists, the job
+will not be dispatched.
+
+Upon successful creation, the dispatched job ID will be printed and the
+triggered evaluation will be monitored. This can be disabled by supplying the
+detach flag.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+client connection issues or internal errors, are indicated by exit code 1.
+
+When ACLs are enabled, this command requires a token with the `dispatch-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Dispatch options
+
+- `-meta`: Meta takes a key/value pair separated by "=". The metadata key will
+  be merged into the job's metadata. The job may define a default value for the
+  key which is overridden when dispatching. The flag can be provided more than
+  once to inject multiple metadata key/value pairs. Arbitrary keys are not
+  allowed. The parameterized job must allow the key to be merged.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command
+
+- `-idempotency-token`: Optional identifier used to prevent more than one
+  instance of the job from being dispatched.
+
+- `-id-prefix-template`: Optional prefix added to dispatched job IDs.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via stdin:
+
+```shell-session
+$ cat << EOF | nomad job dispatch video-encode -
+{
+  "s3-input": "https://video-bucket.s3-us-west-1.amazonaws.com/cb31dabb1",
+  "s3-output": "https://video-bucket.s3-us-west-1.amazonaws.com/a149adbe3",
+  "input-codec": "mp4",
+  "output-codec": "webm",
+  "quality": "1080p"
+}
+EOF
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" and
+passing in a configuration payload via a file:
+
+```shell-session
+$ nomad job dispatch video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch against a parameterized job with the ID "video-encode" using the detach
+flag:
+
+```shell-session
+$ nomad job dispatch -detach video-encode video-config.json
+Dispatched Job ID = example/dispatch-1485380684-c37b3dba
+Evaluation ID     = d9034c4e
+```
+
+Dispatch with an idempotency token for the first time:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Dispatched Job ID = video-encode/dispatch-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+Dispatch with the same idempotency token:
+
+```shell-session
+$ nomad job dispatch -idempotency-token=prod video-encode video-config.json
+Job "video-encode/dispatch-1485379325-cb38d00d" already dispatched with idempotency token "prod".
+```
+
+Dispatch with an id prefix:
+
+```shell-session
+$ nomad job dispatch -id-prefix-template=config1 video-encode video-config1.json
+Jb
+Dispatched Job ID = video-encode/dispatch-config1-1485379325-cb38d00d
+Evaluation ID     = 31199841
+
+==> Monitoring evaluation "31199841"
+    Evaluation triggered by job "example/dispatch-config1-1485379325-cb38d00d"
+    Allocation "8254b85f" created: node "82ff9c50", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "31199841" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[parameterized job]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/eval.mdx b/content/nomad/v1.9.x/content/docs/commands/job/eval.mdx
new file mode 100644
index 0000000000..3e61b24e58
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/eval.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'nomad job eval command reference'
+description: |
+  The `nomad job eval` command forces an evaluation of a job. Optionally, force placement of failed allocations.
+---
+
+# `nomad job eval` command reference
+
+The `job eval` command is used to force an evaluation of a job, given the job
+ID.
+
+## Usage
+
+```plaintext
+nomad job eval [options] <job_id>
+```
+
+The `job eval` command requires a single argument, specifying the job ID to
+evaluate. If there is an exact match based on the provided job ID, then the job
+will be evaluated, forcing a scheduler run.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Eval options
+
+- `-force-reschedule`: `force-reschedule` is used to force placement of failed
+  allocations. If this is set, failed allocations that are past their reschedule
+  limit, and those that are scheduled to be replaced at a future time are placed
+  immediately. This option only places failed allocations if the task group has
+  rescheduling enabled.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Evaluate the job with ID "job1":
+
+```shell-session
+$ nomad job eval job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+Evaluate the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job eval -detach job1
+Created eval ID: "4947e728"
+```
+
+Evaluate the job with ID "job1", and reschedule any eligible failed allocations:
+
+```shell-session
+$ nomad job eval -force-reschedule job1
+==> Monitoring evaluation "0f3bc0f3"
+    Evaluation triggered by job "test"
+    Evaluation within deployment: "51baf5c8"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "0f3bc0f3" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/history.mdx b/content/nomad/v1.9.x/content/docs/commands/job/history.mdx
new file mode 100644
index 0000000000..48f3514a81
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/history.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: 'nomad job history command reference'
+description: |
+  The `nomad job history` command displays the history of a single version or all tracked versions of a job. Optionally display the difference between two versions or tags or differences between each job and its predecessor.
+---
+
+# `nomad job history` command reference
+
+The `job history` command is used to display the known versions of a particular
+job. The command can display the diff between job versions and can be useful for
+understanding the changes that occurred to the job as well as deciding job
+versions to revert to.
+
+## Usage
+
+```plaintext
+nomad job history [options] <job>
+```
+
+The `job history` command requires a single argument, the job ID or an ID prefix
+of a job to display the history for.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## History options
+
+- `-p`: Display the differences between each job and its predecessor.
+- `-full`: Display the full job definition for each version.
+- `-version`: Display only the history for the given version.
+- `-json` : Output the job versions in its JSON format.
+- `-t` : Format and display the job versions using a Go template.
+- `-diff-version`: Compare the job with a specific version.
+- `-diff-tag`: Compare the job with a specific tag.
+
+
+## Examples
+
+Display the history showing differences between versions:
+
+```shell-session
+$ nomad job history -p e
+Version     = 2
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 20:35:31 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Count: "1" => "3"
+      Task: "redis"
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 20:35:28 UTC
+```
+
+Display the memory ask across submitted job versions:
+
+```shell-session
+$ nomad job history -t "{{range .}}\
+v{{.Version}}: {{with index .TaskGroups 0}}{{with index .Tasks 0}}{{.Resources.MemoryMB}}{{end}}{{end}}\
+
+{{end}}" example
+v2: 512
+v1: 256
+v0: 256
+```
+
+Compare the current job with a specific older version:
+
+```shell-session
+$ nomad job history -version=3 -diff-version=1 example
+Version     = 3
+Stable      = false
+Submit Date = 07/25/17 20:35:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Resources {
+          CPU:      "500"
+          DiskMB:   "0"
+      +/- MemoryMB: "256" => "512"
+        }
+```
+
+Compare all job versions with a specific version by tag name:
+
+```shell-session
+$ nomad job history -diff-tag=low-energy-version example
+
+Version     = 3
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "4"
+      Task: "task"
+
+Version         = 2
+Stable          = false
+Submit Date     = 2024-09-09T16:41:53-04:00
+Tag Name        = low-energy-version
+Tag Description = test description
+
+Version     = 1
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "2"
+      Task: "task"
+
+Version     = 0
+Stable      = false
+Submit Date = 2024-09-09T16:41:53-04:00
+Diff        =
++/- Job: "example"
++/- Task Group: "group"
+  +/- Count: "3" => "1"
+      Task: "task"
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/index.mdx b/content/nomad/v1.9.x/content/docs/commands/job/index.mdx
new file mode 100644
index 0000000000..bed9c1c4c5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/index.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'nomad job command reference'
+description: |
+  The `nomad job` command interacts with jobs. Create, validate, and plan a job specification. Display allocations, deployments, history, and status. Execute predefined actions, dispatch parameterized jobs, inspect a job, force the evaluation of a periodic job, scale allocations, and promote canaries. Run, restart, revert, and stop a job.
+---
+
+# `nomad job` command reference
+
+The `job` command is used to interact with jobs.
+
+## Usage
+
+Usage: `nomad job <subcommand> [options]`
+
+Run `nomad job <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`job action`][action] - Execute predefined actions
+- [`job allocs`][allocs] - List allocations for a job
+- [`job deployments`][deployments] - List deployments for a job
+- [`job dispatch`][dispatch] - Dispatch an instance of a parameterized job
+- [`job eval`][eval] - Force an evaluation for a job
+- [`job history`][history] - Display all tracked versions of a job
+- [`job init`][init] - Create an example job specification
+- [`job inspect`][inspect] - Inspect the contents of a submitted job
+- [`job periodic force`][periodic force] - Force the evaluation of a periodic job
+- [`job plan`][plan] - Schedule a dry run for a job
+- [`job promote`][promote] - Promote a job's canaries
+- [`job restart`][restart] - Restart or reschedule allocations for a job
+- [`job revert`][revert] - Revert to a prior version of the job
+- [`job run`][run] - Submit a new job
+- [`job scale`][scale] - Update the number of allocations for a task group in a job
+- [`job scaling-events`][scaling-events] - List the recent scaling events for a job
+- [`job status`][status] - Display status information about a job
+- [`job stop`][stop] - Stop a running job and cancel its allocations
+- [`job tag`][tag] - Tag a job with a version
+- [`job validate`][validate] - Check a job specification for syntax errors
+
+
+[action]: /nomad/docs/commands/job/action 'Execute predefined actions'
+[allocs]: /nomad/docs/commands/job/allocs 'List allocations for a job'
+[deployments]: /nomad/docs/commands/job/deployments 'List deployments for a job'
+[dispatch]: /nomad/docs/commands/job/dispatch 'Dispatch an instance of a parameterized job'
+[eval]: /nomad/docs/commands/job/eval 'Force an evaluation for a job'
+[history]: /nomad/docs/commands/job/history 'Display all tracked versions of a job'
+[init]: /nomad/docs/commands/job/init 'Create an example job specification'
+[inspect]: /nomad/docs/commands/job/inspect 'Inspect the contents of a submitted job'
+[periodic force]: /nomad/docs/commands/job/periodic-force 'Force the evaluation of a periodic job'
+[plan]: /nomad/docs/commands/job/plan 'Schedule a dry run for a job'
+[restart]: /nomad/docs/commands/job/restart 'Restart or reschedule allocations for a job'
+[revert]: /nomad/docs/commands/job/revert 'Revert to a prior version of the job'
+[run]: /nomad/docs/commands/job/run 'Submit a new job'
+[status]: /nomad/docs/commands/job/status 'Display status information about a job'
+[scale]: /nomad/docs/commands/job/scale 'Update the number of allocations for a task group in a job'
+[scaling-events]: /nomad/docs/commands/job/scaling-events 'List the recent scaling events for a job'
+[stop]: /nomad/docs/commands/job/stop 'Stop a running job and cancel its allocations'
+[tag]: /nomad/docs/commands/job/tag 'Tag a job with a version'
+[validate]: /nomad/docs/commands/job/validate 'Check a job specification for syntax errors'
+[promote]: /nomad/docs/commands/job/promote
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/init.mdx b/content/nomad/v1.9.x/content/docs/commands/job/init.mdx
new file mode 100644
index 0000000000..d3d0ccb85a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/init.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad job init command reference'
+description: |
+  The `nomad job init` command generates a job specification with example configurations for tasks, task groups, runtime constraints, and resource allocation.
+---
+
+# `nomad job init` command reference
+
+**Alias: `nomad init`**
+
+The `job init` command creates an example [job specification][jobspec] in the
+current directory that demonstrates some common configurations for tasks, task
+groups, runtime constraints, and resource allocation.
+
+## Usage
+
+```plaintext
+nomad job init [options] [filename]
+```
+
+You may optionally supply a filename for the example job to be written to. The
+default filename for the generated file is "example.nomad.hcl".
+
+Please refer to the [jobspec] and [drivers] pages to learn how to customize the
+template.
+
+## Init options
+
+- `-short`: If set, a minimal jobspec without comments is emitted.
+- `-connect`: If set, the jobspec includes Consul Connect integration.
+- `-template=<template>`: Specifies a predefined template to emit. Must be a Nomad Variable that lives at `nomad/job-templates/<template>` These are commonly created via the UI, and accessible with the -list-templates flag.
+- `-list-templates`: Display a list of possible job templates to pass to -template. Reads from all variables pathed at `nomad/job-templates/<template>`.
+
+## Examples
+
+Generate an example job file:
+
+```shell-session
+$ nomad job init
+Example job file written to example.nomad.hcl
+```
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[drivers]: /nomad/docs/drivers 'Nomad Task Drivers documentation'
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/inspect.mdx b/content/nomad/v1.9.x/content/docs/commands/job/inspect.mdx
new file mode 100644
index 0000000000..f0c8105d78
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/inspect.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: 'nomad job inspect command reference'
+description: |
+  The `nomad job inspect` command displays a complete job definition so you can inspect contents.
+---
+
+# `nomad job inspect` command reference
+
+**Alias: `nomad inspect`**
+
+The `job inspect` command is used to inspect the content of a submitted job.
+
+## Usage
+
+```plaintext
+nomad job inspect [options] <job>
+```
+
+The `job inspect` command requires a single argument, a submitted job's name, and
+will retrieve the JSON version of the job. This JSON is valid to be submitted to
+the [Job HTTP API]. This command is useful to inspect what version of a job
+Nomad is running.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Inspect options
+
+- `-version`: Display only the job at the given job version.
+- `-json` : Output the job in its JSON format. Cannot be used with `-hcl`.
+- `-hcl`: Output the original HCL submitted with the job. Cannot be used with
+  `-json`.
+- `-with-vars`: Include the original HCL2 variables submitted with the job. Can
+    only be used with `-hcl`.
+- `-t` : Format and display the job using a Go template.
+
+## Examples
+
+Inspect a submitted job:
+
+```shell-session
+$ nomad job inspect redis
+{
+    "Job": {
+        "Region": "global",
+        "ID": "redis
+        "Name": "redis
+        "Type": "service",
+        "Priority": 50,
+        "AllAtOnce": false,
+        "Datacenters": [
+            "dc1"
+        ],
+        "Constraints": [
+            {
+                "LTarget": "${attr.kernel.name}",
+                "RTarget": "linux",
+                "Operand": "="
+            }
+        ],
+        "TaskGroups": [
+            {
+                "Name": "cache",
+                "Count": 1,
+                "Constraints": null,
+                "Tasks": [
+                    {
+                        "Name": "redis",
+                        "Driver": "docker",
+                        "User": "",
+                        "Config": {
+                            "image": "redis:latest",
+                            "port_map": [
+                                {
+                                    "db": 6379
+                                }
+                            ]
+                        },
+                        "Constraints": null,
+                        "Env": null,
+                        "Services": [
+                            {
+                                "Id": "",
+                                "Name": "cache-redis",
+                                "Tags": [
+                                    "global",
+                                    "cache"
+                                ],
+                                "PortLabel": "db",
+                                "Checks": [
+                                    {
+                                        "Id": "",
+                                        "Name": "alive",
+                                        "Type": "tcp",
+                                        "Command": "",
+                                        "Args": null,
+                                        "Path": "",
+                                        "Protocol": "",
+                                        "Interval": 10000000000,
+                                        "Timeout": 2000000000
+                                    }
+                                ]
+                            }
+                        ],
+                        "Resources": {
+                            "CPU": 500,
+                            "MemoryMB": 256,
+                            "DiskMB": 300,
+                            "Networks": [
+                                {
+                                    "Public": false,
+                                    "CIDR": "",
+                                    "ReservedPorts": null,
+                                    "DynamicPorts": [
+                                        {
+                                            "Label": "db",
+                                            "Value": 0
+                                        }
+                                    ],
+                                    "IP": "",
+                                    "MBits": 10
+                                }
+                            ]
+                        },
+                        "Meta": null,
+                        "KillTimeout": 5000000000,
+                        "LogConfig": {
+                            "MaxFiles": 10,
+                            "MaxFileSizeMB": 10
+                        },
+                        "Artifacts": null
+                    }
+                ],
+                "RestartPolicy": {
+                    "Interval": 300000000000,
+                    "Attempts": 10,
+                    "Delay": 25000000000,
+                    "Mode": "delay"
+                },
+                "Meta": null
+            }
+        ],
+        "Update": {
+            "Stagger": 10000000000,
+            "MaxParallel": 1
+        },
+        "Periodic": null,
+        "Meta": null,
+        "Status": "running",
+        "StatusDescription": "",
+        "CreateIndex": 5,
+        "ModifyIndex": 7
+    }
+}
+```
+
+[job http api]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/periodic-force.mdx b/content/nomad/v1.9.x/content/docs/commands/job/periodic-force.mdx
new file mode 100644
index 0000000000..fe36277b2a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/periodic-force.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad job periodic force command reference'
+description: >
+  The `nomad job periodic force` command forces the evaluation of a periodic
+  job. Use this command to immediately run a periodic job, even if it violates the job's `prohibit_overlap` setting.
+---
+
+# `nomad job periodic force` command reference
+
+The `job periodic force` command is used to [force the evaluation] of a
+[periodic job].
+
+## Usage
+
+```plaintext
+nomad job periodic force [options] <job id>
+```
+
+The `job periodic force` command requires a single argument, specifying the ID
+of the job. This job must be a periodic job. This is used to immediately run a
+periodic job, even if it violates the job's `prohibit_overlap` setting.
+
+By default, on successful job submission the command will enter an interactive
+monitor and display log information detailing the scheduling decisions and
+placement information for the forced evaluation. The monitor will exit after
+scheduling has finished or failed.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Run options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Force the evaluation of the job `example`, monitoring placement:
+
+```shell-session
+$ nomad job periodic force example
+==> Monitoring evaluation "54b2d6d9"
+    Evaluation triggered by job "example/periodic-1555094493"
+    Allocation "637aee17" created: node "a35ab8fc", group "cache"
+    Allocation "637aee17" status changed: "pending" -> "running" (Tasks are running)
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "54b2d6d9" finished with status "complete"
+```
+
+Force the evaluation of the job `example` and return immediately:
+
+```shell-session
+$ nomad job periodic force -detach example
+Force periodic successful
+Evaluation ID: 0865fbf3-30de-5f53-0811-821e73e63178
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[force the evaluation]: /nomad/api-docs/jobs#force-new-periodic-instance
+[periodic job]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/plan.mdx b/content/nomad/v1.9.x/content/docs/commands/job/plan.mdx
new file mode 100644
index 0000000000..120a7a8ec1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/plan.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: 'nomad job plan command reference'
+description: |
+  The `nomad job plan` command executes a dry run of a job to determine its effects.
+---
+
+# `nomad job plan` command reference
+
+**Alias: `nomad plan`**
+
+The `job plan` command can be used to invoke the scheduler in a dry-run mode
+with new jobs or when updating existing jobs to determine what would happen if
+the job is submitted. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job plan [options] <path>
+```
+
+The `job plan` command requires a single argument, specifying the path to a file
+containing an HCL [job specification]. This file will be read and the resulting
+parsed job will be validated. If the supplied path is "-", the job file is read
+from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+Plan invokes a dry-run of the scheduler to determine the effects of submitting
+either a new or updated version of a job. The plan will not result in any
+changes to the cluster but gives insight into whether the job could be run
+successfully and how it would affect existing allocations.
+
+A job modify index is returned with the plan. This value can be used when
+submitting the job using [`nomad job run -check-index`], which will check that
+the job was not modified between the plan and run command before invoking the
+scheduler. This ensures the job has not been modified since the plan.
+
+A structured diff between the local and remote job is displayed to
+give insight into what the scheduler will attempt to do and why.
+
+If the job has specified the region, the `-region` flag and `NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+Plan will return one of the following exit codes:
+
+- 0: No allocations created or destroyed.
+- 1: Allocations created or destroyed.
+- 255: Error determining plan results.
+
+The plan command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Plan options
+
+- `-diff`: Determines whether the diff between the remote job and planned job is
+  shown. Defaults to true.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after planning and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Increase diff verbosity.
+
+## Examples
+
+Plan a new job that has not been previously submitted:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++ Job: "example"
++ Task Group: "cache" (1 create)
+  + Task: "redis" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Job Modify Index: 0
+To submit the job with version verification run:
+
+nomad job run -check-index 0 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Increase the count of an existing without sufficient cluster capacity:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (7 create, 1 in-place update)
+  +/- Count: "1" => "8" (forces create)
+      Task: "redis"
+
+Scheduler dry-run:
+- WARNING: Failed to place all allocations.
+  Task Group "cache" (failed to place 3 allocations):
+    * Resources exhausted on 1 nodes
+    * Dimension "cpu" exhausted on 1 nodes
+
+Job Modify Index: 15
+To submit the job with version verification run:
+
+nomad job run -check-index 15 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Update an existing job such that it would cause a rolling update:
+
+```shell-session
+$ nomad job plan example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  +/- Task: "redis" (forces create/destroy update)
+    +/- Config {
+      +/- image:           "redis:2.8" => "redis:7"
+          port_map[0][db]: "6379"
+    }
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+Add a task to the task group using verbose mode:
+
+```shell-session
+$ nomad job plan -verbose example.nomad.hcl
++/- Job: "example"
++/- Task Group: "cache" (3 create/destroy update)
+  + Task: "my-website" (forces create/destroy update)
+    + Driver:      "docker"
+    + KillTimeout: "5000000000"
+    + Config {
+      + image:            "node:6.2"
+      + port_map[0][web]: "80"
+    }
+    + Resources {
+      + CPU:      "500"
+      + DiskMB:   "300"
+      + MemoryMB: "256"
+      + Network {
+        + MBits: "10"
+        + Dynamic Port {
+          + Label: "web"
+        }
+      }
+    }
+    + LogConfig {
+      + MaxFileSizeMB: "10"
+      + MaxFiles:      "10"
+    }
+    + Service {
+      + Name:      "website"
+      + PortLabel: "web"
+      + Check {
+          Command:  ""
+        + Interval: "10000000000"
+        + Name:     "alive"
+          Path:     ""
+          Protocol: ""
+        + Timeout:  "2000000000"
+        + Type:     "tcp"
+      }
+    }
+    Task: "redis"
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+- Rolling update, next evaluation will be in 10s.
+
+Job Modify Index: 7
+To submit the job with version verification run:
+
+nomad job run -check-index 7 example.nomad.hcl
+
+When running the job with the check-index flag, the job will only be run if the
+job modify index given matches the server-side version. If the index has
+changed, another user has modified the job and the plan's results are
+potentially invalid.
+```
+
+When using the `nomad job plan` command in automated environments, such as
+in CI/CD pipelines, it is useful to output the plan result for manual
+validation and also store the check index on disk so it can be used later to
+guarantee that a job deployment will match the expected changes described in
+the plan result.
+
+This can be done by parsing the command output and redirecting the index to a
+file. For example, in Linux environments the [`tee`] command can be used for
+this purpose:
+
+```console
+$ nomad job plan -no-color example.nomad.hcl | tee /dev/stderr | grep 'Job Modify Index:' | awk -F': ' '{ print $2 }' > check-index || true
+```
+
+The [`-no-color`](#no-color) flag prevents style characters from impacting
+parsing. Colored output may be helpful when analyzing the plan result, so the
+[`-force-color`](#force-color) flag can be used. This will affect how parsing
+is done to avoid hidden control characters. Adding `|| true` at the end
+prevents undesired failures since `nomad job plan` returns a non-zero exit code
+if a change is detected.
+
+[job specification]: /nomad/docs/job-specification
+[hcl job specification]: /nomad/docs/job-specification
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`nomad job run -check-index`]: /nomad/docs/commands/job/run#check-index
+[`tee`]: https://man7.org/linux/man-pages/man1/tee.1.html
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/promote.mdx b/content/nomad/v1.9.x/content/docs/commands/job/promote.mdx
new file mode 100644
index 0000000000..0959d65dc3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/promote.mdx
@@ -0,0 +1,228 @@
+---
+layout: docs
+page_title: 'nomad job promote command reference'
+description: |
+  The `nomad job promote` command promotes healthy task group canaries in a deployment.
+---
+
+# `nomad job promote` command reference
+
+The `job promote` command is used to promote task groups in the most recent
+deployment for the given job. Promotion should occur when the deployment has
+placed canaries for a task group and those canaries have been deemed healthy.
+When a task group is promoted, the rolling upgrade of the remaining allocations
+is unblocked. If the canaries are found to be unhealthy, the deployment may
+either be failed using the "nomad deployment fail" command, the job can be
+failed forward by submitting a new version or failed backwards by reverting to
+an older version using the [job revert] command.
+
+## Usage
+
+```plaintext
+nomad job promote [options] <job>
+```
+
+The `job promote` command requires a single argument, a job ID or
+prefix. When run without specifying any groups to promote, the promote command
+promotes all task groups. The group flag can be specified multiple times to
+select particular groups to promote.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with a job prefix instead of the
+exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Promote options
+
+- `-group`: Group may be specified many times and is used to promote that
+  particular group. If no specific groups are specified, all groups are
+  promoted.
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Promote canaries in all groups:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       0        0
+cache       false     2        1         1       0        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+091377e5  a8dcce2d  web         1        run      running  07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running  07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        run      running  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        run      running  07/25/17 18:31:34 UTC
+
+# Promote all groups
+$ nomad job promote example
+==> Monitoring evaluation "6c6e64ae"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "9fa81f27"
+    Allocation "8fa21654" created: node "a8dcce2d", group "web"
+    Allocation "9f6727a6" created: node "a8dcce2d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "6c6e64ae" finished with status "complete"
+
+# Inspect the status and see both groups have been promoted.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:35:05 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         2        0       2         0
+
+Latest Deployment
+ID          = 9fa81f27
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         true      2        1         2       2        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+8fa21654  a8dcce2d  web         1        run      running   07/25/17 18:35:21 UTC
+9f6727a6  a8dcce2d  cache       1        run      running   07/25/17 18:35:21 UTC
+091377e5  a8dcce2d  web         1        run      running   07/25/17 18:35:05 UTC
+d2b13584  a8dcce2d  cache       1        run      running   07/25/17 18:35:05 UTC
+4bb185b7  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+9b6811ee  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+e0a2441b  a8dcce2d  cache       0        stop     complete  07/25/17 18:31:34 UTC
+f2409f7d  a8dcce2d  web         0        stop     complete  07/25/17 18:31:34 UTC
+```
+
+Promote canaries in a particular group:
+
+```shell-session
+# Have two task groups waiting for promotion.
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         3        0       0         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+cache       false     2        1         1       1        0
+web         false     2        1         1       1        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+3071ab8f  6240eed6  web         1        run      running  07/25/17 18:37:14 UTC
+eeeed13b  6240eed6  cache       1        run      running  07/25/17 18:37:14 UTC
+0ee7800c  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+a714a926  6240eed6  cache       0        run      running  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running  07/25/17 18:37:08 UTC
+
+# Promote only the cache canaries
+$ nomad job promote -group=cache example
+==> Monitoring evaluation "37383564"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "a6b87a6c"
+    Allocation "bbddf5c3" created: node "6240eed6", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "37383564" finished with status "complete"
+
+# Inspect the status and see that only the cache canaries are promoted
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 18:37:14 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         2        0       2         0
+web         0       0         3        0       0         0
+
+Latest Deployment
+ID          = a6b87a6c
+Status      = running
+Description = Deployment is running but requires manual promotion
+
+Deployed
+Task Group  Promoted  Desired  Canaries  Placed  Healthy  Unhealthy
+web         false     2        1         1       1        0
+cache       true      2        1         2       2        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created At
+bbddf5c3  6240eed6  cache       1        run      running   07/25/17 18:37:40 UTC
+eeeed13b  6240eed6  cache       1        run      running   07/25/17 18:37:14 UTC
+3071ab8f  6240eed6  web         1        run      running   07/25/17 18:37:14 UTC
+a714a926  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+cee52788  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+ee8f972e  6240eed6  web         0        run      running   07/25/17 18:37:08 UTC
+0ee7800c  6240eed6  cache       0        stop     complete  07/25/17 18:37:08 UTC
+```
+
+[job revert]: /nomad/docs/commands/job/revert
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/restart.mdx b/content/nomad/v1.9.x/content/docs/commands/job/restart.mdx
new file mode 100644
index 0000000000..4323ecdb1e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/restart.mdx
@@ -0,0 +1,235 @@
+---
+layout: docs
+page_title: 'nomad job restart command reference'
+description: |
+  The `nomad job restart` command restarts or reschedules allocations for a job.
+---
+
+# `nomad job restart` command reference
+
+The `job restart` command is used to restart or reschedule allocations for a
+particular job.
+
+Restarting the job calls the [Restart Allocation][api_alloc_restart] API
+endpoint to restart the tasks inside allocations, so the allocations themselves
+are not modified but rather restarted in-place.
+
+Rescheduling the job uses the [Stop Allocation][api_alloc_stop] API endpoint to
+stop the allocations and trigger the Nomad scheduler to compute new placements.
+This may cause the new allocations to be scheduled in different clients from
+the originals.
+
+## Usage
+
+```plaintext
+nomad job restart [options] <job>
+```
+
+The `job restart` command requires a single argument, specifying the job ID to
+restart.
+
+The command can operate in batches and wait until all restarted or
+rescheduled allocations are running again before proceeding to the next batch.
+It is also possible to specify additional time to wait between batches.
+
+You may restart in-place or migrated allocations. When restarting in-place, the
+command may target specific tasks in the allocations, restart only tasks that
+are currently running, or restart all tasks, even the ones that have already
+run. Groups and tasks can also target allocations.  When you define both groups
+and tasks, Nomad restarts only the tasks for the allocations of those groups.
+
+When migrating, Nomad stops the current allocations, triggering the Nomad
+scheduler to create new allocations that may be placed in different clients. The
+command waits until the new allocations have client status `ready` before
+proceeding with the remaining batches. The command does not consider service
+health checks.
+
+By default the command restarts all running tasks in-place with one allocation
+per batch.
+
+When ACLs are enabled, this command requires a token with the
+`alloc-lifecycle` and `read-job` capabilities for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix instead
+of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Restart options
+
+- `-all-tasks`: If set, all tasks in the allocations are restarted, even the
+  ones that have already run, such as non-sidecar tasks. Tasks will restart
+  following their [`lifecycle`][] order. This option cannot be used with
+  `-task`.
+
+- `-batch-size=<n|n%>`: Number of allocations to restart at once. It may be
+  defined as a percentage value of the current number of running allocations.
+  Percentage values are rounded up to increase parallelism. Defaults to `1`.
+
+- `-batch-wait=<duration|ask>`: Time to wait between restart batches. If set
+  to `ask` the command halts between batches and waits for user input on how to
+  proceed. If the answer is a time duration all remaining batches will use this
+  new value. Defaults to `0`.
+
+- `-group=<group-name>`: Only restart allocations for the given group. Can be
+  specified multiple times. If no group is set all allocations for the job are
+  restarted.
+
+- `-no-shutdown-delay`: Ignore the group and task [`shutdown_delay`][]
+  configuration so there is no delay between service deregistration and task
+  shutdown or restart. Note that using this flag will result in failed network
+  connections to the allocation being restarted.
+
+- `-reschedule`: If set, Nomad stops and migrates allocations instead of
+  restarting in-place. Since the group is not modified, the restart does not
+  create a new deployment, and so values defined in [`update`][] blocks, such as
+  [`max_parallel`][], are not considered. This option cannot be used with
+  `-task`. You may only migrate jobs of type `batch`, `service`, and `system`.
+  Note that despite the name of this flag, this command migrates but does not
+  reschedule allocations, so it ignores the `reschedule` block.
+
+- `-on-error=<ask|fail>`: Determines what action to take when an error happens
+  during a restart batch. If `ask` the command stops and waits for user
+  confirmation on how to proceed. If `fail` the command exits immediately.
+  Defaults to `ask`.
+
+- `-task=<task-name>`: Specify the task to restart. Can be specified multiple
+  times. If groups are also specified the task must exist in at least one of
+  them. If no task is set only tasks that are currently running are restarted.
+  For example, non-sidecar tasks that already ran are not restarted unless
+  `-all-tasks` is used instead. This option cannot be used with `-all-tasks` or
+  `-reschedule`.
+
+- `-yes`: Automatic yes to prompts. If set, the command automatically restarts
+  multi-region jobs only in the region targeted by the command, ignores batch
+  errors, and automatically proceeds with the remaining batches without
+  waiting. Use `-on-error` and `-batch-wait` to adjust these behaviors.
+
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Restart running tasks of all allocations.
+
+```shell-session
+$ nomad job restart example
+==> 2023-02-28T17:36:31-05:00: Restarting 5 allocations
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:36:31-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+    2023-02-28T17:36:32-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:36:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Target allocations of a specific group to restart.
+
+```shell-session
+$ nomad job restart -group=web example
+==> 2023-02-28T17:37:36-05:00: Restarting 2 allocations
+    2023-02-28T17:37:36-05:00: Restarting running tasks in allocation "388129e0" for group "web"
+    2023-02-28T17:37:37-05:00: Restarting running tasks in allocation "d4303a30" for group "web"
+==> 2023-02-28T17:37:37-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Reschedule allocations instead of restarting them in-place.
+
+```shell-session
+❯ nomad job restart -group=web -reschedule example
+==> 2023-02-28T17:39:14-05:00: Restarting 2 allocations
+    2023-02-28T17:39:14-05:00: Rescheduling allocation "388129e0" for group "web"
+    2023-02-28T17:39:45-05:00: Rescheduling allocation "d4303a30" for group "web"
+==> 2023-02-28T17:40:16-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations to restart them 2 at a time.
+
+```shell-session
+$ nomad job restart -batch-size=2 example
+==> 2023-02-28T17:40:58-05:00: Restarting 5 allocations
+==> 2023-02-28T17:40:58-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T17:40:58-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+    2023-02-28T17:40:58-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T17:40:59-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T17:40:59-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Batch allocations as a percentage of total running allocations.
+
+```shell-session
+$ nomad job restart -batch-size=50% example
+==> 2023-02-28T18:52:47-05:00: Restarting 5 allocations
+==> 2023-02-28T18:52:47-05:00: Restarting 1st batch of 3 allocations
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "d28f6f60" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "b931b496" for group "proxy"
+    2023-02-28T18:52:47-05:00: Restarting running tasks in allocation "18673b40" for group "proxy"
+==> 2023-02-28T18:52:48-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "439b1632" for group "web"
+    2023-02-28T18:52:48-05:00: Restarting running tasks in allocation "8fae60f6" for group "web"
+==> 2023-02-28T18:52:48-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Pause between batches of restart and wait for user input on how to proceed.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=ask example
+==> 2023-02-28T18:04:19-05:00: Restarting 5 allocations
+==> 2023-02-28T18:04:19-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+    2023-02-28T18:04:19-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+==> 2023-02-28T18:04:19-05:00: Proceed with next batch? [Y/n/<duration>] y
+==> 2023-02-28T18:04:20-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:04:20-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:04:20-05:00: Proceed with next batch? [Y/n/<duration>] 10s
+==> 2023-02-28T18:04:22-05:00: Proceeding restarts with new wait time of 10s
+==> 2023-02-28T18:04:22-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:32-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:32-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:32-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+Wait 10 seconds before each restart batch.
+
+```shell-session
+$ nomad job restart -batch-size=2 -batch-wait=10s example
+==> 2023-02-28T18:03:43-05:00: Restarting 5 allocations
+==> 2023-02-28T18:03:43-05:00: Restarting 1st batch of 2 allocations
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "653f983e" for group "web"
+    2023-02-28T18:03:43-05:00: Restarting running tasks in allocation "4d18e545" for group "web"
+==> 2023-02-28T18:03:43-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:03:53-05:00: Restarting 2nd batch of 2 allocations
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "4fd581ee" for group "proxy"
+    2023-02-28T18:03:53-05:00: Restarting running tasks in allocation "32e143f8" for group "proxy"
+==> 2023-02-28T18:03:53-05:00: Waiting 10s before restarting the next batch
+==> 2023-02-28T18:04:03-05:00: Restarting 3rd batch of 1 allocations
+    2023-02-28T18:04:03-05:00: Restarting running tasks in allocation "77d5c4f6" for group "proxy"
+==> 2023-02-28T18:04:03-05:00: Finished job restart
+
+All allocations restarted successfully!
+```
+
+[`lifecycle`]: /nomad/docs/job-specification/lifecycle
+[`max_parallel`]: /nomad/docs/job-specification/update#max_parallel
+[`shutdown_delay`]: /nomad/docs/job-specification/task#shutdown_delay
+[`update`]: /nomad/docs/job-specification/update
+[api_alloc_restart]: /nomad/api-docs/allocations#restart-allocation
+[api_alloc_stop]: /nomad/api-docs/allocations#stop-allocation
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/revert.mdx b/content/nomad/v1.9.x/content/docs/commands/job/revert.mdx
new file mode 100644
index 0000000000..ee38ff1f35
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/revert.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad job revert command reference'
+description: |
+  The `nomad job revert` command reverts the current job to a prior version.
+---
+
+# `nomad job revert` command reference
+
+The `job revert` command is used to revert a job to a prior version of the
+job. The available versions to revert to can be found using [`job history`]
+command.
+
+The revert command will use a Consul token with the following preference:
+first the `-consul-token` flag, then the `$CONSUL_HTTP_TOKEN` environment variable.
+Because the consul token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Consul Connect enabled services and the Nomad servers were configured to require
+[consul service identity] authentication.
+
+The revert command will use a Vault token with the following preference:
+first the `-vault-token` flag, then the `$VAULT_TOKEN` environment variable.
+Because the vault token used to [run] the targeted job version was not
+persisted, it must be provided to revert if the targeted job version includes
+Vault policies and the Nomad servers were configured to require [vault policy]
+authentication.
+
+## Usage
+
+```shell-session
+nomad job revert [options] <job> <version|tag>
+```
+
+The `job revert` command requires two inputs: the job ID, and the version number
+or tag of the job to revert to.  When you specify a version number, Nomad
+reverts the job to the exact version number. Alternately, when you specify a
+custom tag name as a string, Nomad reverts to the version tagged with that
+name.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Revert options
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-consul-token`: If set, the passed Consul token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable.
+
+- `-vault-token`: If set, the passed Vault token is sent along with the revert
+  request to the Nomad servers. This overrides the token found in the
+  `$VAULT_TOKEN` environment variable.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Revert to an older version of a job:
+
+```shell-session
+$ nomad job history -p example
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+
+$ nomad job revert example 0
+==> Monitoring evaluation "faff5c30"
+    Evaluation triggered by job "example"
+    Evaluation within deployment: "e17c8592"
+    Allocation "4ed0ca3b" modified: node "e8a2243d", group "cache"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "faff5c30" finished with status "complete"
+
+$ nomad job history -p example
+Version     = 2
+Stable      = true
+Submit Date = 07/25/17 21:27:43 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:4.0" => "redis:7"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 1
+Stable      = false
+Submit Date = 07/25/17 21:27:30 UTC
+Diff        =
++/- Job: "example"
++/- Task Group: "cache"
+  +/- Task: "redis"
+    +/- Config {
+      +/- image:           "redis:7" => "redis:4.0"
+          port_map[0][db]: "6379"
+        }
+
+Version     = 0
+Stable      = false
+Submit Date = 07/25/17 21:27:18 UTC
+```
+
+[`job history`]: /nomad/docs/commands/job/history
+[eval status]: /nomad/docs/commands/eval/status
+[consul service identity]: /nomad/docs/configuration/consul#allow_unauthenticated
+[vault policy]: /nomad/docs/configuration/vault#allow_unauthenticated
+[run]: /nomad/docs/commands/job/run
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/run.mdx b/content/nomad/v1.9.x/content/docs/commands/job/run.mdx
new file mode 100644
index 0000000000..9f8593fb19
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/run.mdx
@@ -0,0 +1,246 @@
+---
+layout: docs
+page_title: 'nomad job run command reference'
+description: |
+  The `nomad job run` command submits a job to Nomad for scheduling, which then runs the job.
+---
+
+# `nomad job run` command reference
+
+**Alias: `nomad run`**
+
+The `job run` command is used to submit new jobs to Nomad or to update existing
+jobs. Job files must conform to the [job specification] format.
+
+## Usage
+
+```plaintext
+nomad job run [options] <job file>
+```
+
+The `job run` command requires a single argument, specifying the path to a file
+containing a valid [job specification]. This file will be read and the job will
+be submitted to Nomad for scheduling. If the supplied path is "-", the job file
+is read from STDIN. Otherwise it is read from the file at the supplied path or
+downloaded and read from URL specified. Nomad downloads the job file using
+[`go-getter`] and supports `go-getter` syntax.
+
+By default, on successful job submission the run command will enter an
+interactive monitor and display log information detailing the scheduling
+decisions, placement information, and [deployment status] for the provided job
+if applicable ([`batch`] and [`system`] jobs don't create deployments). The monitor will
+exit after scheduling and deployment have finished or failed.
+
+On successful job submission and scheduling, exit code 0 will be returned. If
+there are job placement issues encountered (unsatisfiable constraints, resource
+exhaustion, etc), then the exit code will be 2. Any other errors, including
+deployment failures, client connection issues, or internal errors, are indicated
+by exit code 1.
+
+If the job has specified the region, the `-region` flag and `$NOMAD_REGION`
+environment variable are overridden and the job's region is used.
+
+The run command will set the `consul_token` of the job based on the following
+precedence, going from highest to lowest: the `-consul-token` flag, the
+`$CONSUL_HTTP_TOKEN` environment variable and finally the value in the job file.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the job's namespace. Jobs that mount CSI volumes require a
+token with the `csi-mount-volume` capability for the volume's namespace. Jobs
+that mount host volumes require a token with the `host_volume` capability for
+that volume.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Run options
+
+- `-check-index`: If set, the job is only registered or
+  updated if the passed job modify index matches the server side version.
+  If a check-index value of zero is passed, the job is only registered if it does
+  not yet exist. If a non-zero value is passed, it ensures that the job is being
+  updated from a known state. The use of this flag is most common in conjunction
+  with [`job plan` command].
+
+- `-detach`: Return immediately instead of monitoring. A new evaluation ID
+  will be output, which can be used to examine the evaluation using the
+  [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job submission. By default, this is set to the priority of the job.
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job. See [JSON Jobs] for details.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-output`: Output the JSON that would be submitted to the HTTP API without
+  submitting the job.
+
+- `-policy-override`: Sets the flag to force override any soft mandatory
+  Sentinel policies.
+
+- `-preserve-counts`: If set, the existing task group counts will be preserved
+  when updating a job.
+
+- `-consul-token`: If set, the passed Consul token is stored in the job before
+  sending to the Nomad servers. This allows passing the Consul token without
+  storing it in the job file. This overrides the token found in the
+  `$CONSUL_HTTP_TOKEN` environment variable and that found in the job.
+
+- `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
+  specified Consul namespace. Any `template` block reading from Consul KV will
+  be scoped to the specified Consul namespace. If Consul ACLs are enabled and the
+  [`consul` block `allow_unauthenticated`] is disabled in the Nomad server configuration, then
+  a Consul token must be supplied with appropriate service and KV Consul ACL policy
+  permissions.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Schedule the job contained in the file `example.nomad.hcl`, monitoring placement and deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-09T15:22:58-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:58-07:00: Evaluation triggered by job "example"
+    2021-06-09T15:22:58-07:00: Allocation "5e0b39f0" created: node "3e84d3d2", group "group1"
+==> 2021-06-09T15:22:59-07:00: Monitoring evaluation "52dee78a"
+    2021-06-09T15:22:59-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T15:22:59-07:00: Allocation "5e0b39f0" status changed: "pending" -> "running"
+    2021-06-09T15:22:59-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T15:22:59-07:00: Evaluation "52dee78a" finished with status "complete"
+==> 2021-06-09T15:22:59-07:00: Monitoring deployment "62eb607c"
+  ⠦ Deployment "62eb607c" in progress...
+
+    2021-06-09T15:22:59-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 0
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       2        2       1        0          2021-06-09T15:32:58-07:00
+    web         1        1       1        0          2021-06-09T15:32:58-07:00
+```
+
+<a id="check-index"></a> Update the job using `check-index`:
+
+```shell-session
+$ nomad job run -check-index 5 example.nomad.hcl
+Enforcing job modify index 5: job exists with conflicting job modify index: 6
+Job not updated
+
+$ nomad job run -check-index 6 example.nomad.hcl
+==> 2021-06-09T16:57:29-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:29-07:00: Evaluation triggered by job "example"
+    2021-06-09T16:57:29-07:00: Allocation "6ec7d16f" modified: node "6e1f9bf6", group "cache"
+==> 2021-06-09T16:57:30-07:00: Monitoring evaluation "5ef16dff"
+    2021-06-09T16:57:30-07:00: Evaluation within deployment: "62eb607c"
+    2021-06-09T16:57:30-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:57:30-07:00: Evaluation "5ef16dff" finished with status "complete"
+==> 2021-06-09T16:57:30-07:00: Monitoring deployment "62eb607c"
+  ✓ Deployment "62eb607c" successful
+
+    2021-06-09T16:57:30-07:00
+    ID          = 62eb607c
+    Job ID      = example
+    Job Version = 2
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        1       1        0          2021-06-09T17:07:00-07:00
+```
+
+Schedule the job contained in `example.nomad.hcl` and return immediately:
+
+```shell-session
+$ nomad job run -detach example.nomad.hcl
+Job registration successful
+Evaluation ID: e18819c1-b83d-dc17-5e7b-b6f264990283
+```
+
+Schedule a job which cannot be successfully placed. This results in a scheduling
+failure and the specifics of the placement are printed:
+
+```shell-session
+$ nomad job run failing.nomad.hcl
+==> 2021-06-09T16:49:00-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:00-07:00: Evaluation triggered by job "example"
+==> 2021-06-09T16:49:01-07:00: Monitoring evaluation "2ae0e6a5"
+    2021-06-09T16:49:01-07:00: Evaluation within deployment: "db0c5e57"
+    2021-06-09T16:49:01-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-09T16:49:01-07:00: Evaluation "2ae0e6a5" finished with status "complete" but failed to place all allocations:
+    2021-06-09T16:49:01-07:00: Task Group "cache" (failed to place 1 allocation):
+      * Class "foo" filtered 1 nodes
+      * Constraint "${attr.kernel.name} = linux" filtered 1 nodes
+    2021-06-09T16:49:01-07:00: Evaluation "67493a64" waiting for additional capacity to place remainder
+==> 2021-06-09T16:49:01-07:00: Monitoring deployment "db0c5e57"
+  ⠧ Deployment "db0c5e57" in progress...
+
+    2021-06-09T16:49:03-07:00
+    ID          = db0c5e57
+    Job ID      = example
+    Job Version = 8
+    Status      = running
+    Description = Deployment is running
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    cache       1        0       0        0          N/A
+```
+
+Sample output when scheduling a system job, which doesn't create a deployment:
+
+```shell-session
+$ nomad job run example.nomad.hcl
+==> 2021-06-14T09:25:08-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:08-07:00: Evaluation triggered by job "example"
+    2021-06-14T09:25:08-07:00: Allocation "03501797" created: node "7849439f", group "cache"
+==> 2021-06-14T09:25:09-07:00: Monitoring evaluation "88a91284"
+    2021-06-14T09:25:09-07:00: Evaluation status changed: "pending" -> "complete"
+==> 2021-06-14T09:25:09-07:00: Evaluation "88a91284" finished with status "complete"
+```
+
+[`batch`]: /nomad/docs/schedulers#batch
+[`consul` block `allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[deployment status]: /nomad/docs/commands/deployment#status
+[eval status]: /nomad/docs/commands/eval/status
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[`job plan` command]: /nomad/docs/commands/job/plan
+[job specification]: /nomad/docs/job-specification
+[JSON jobs]: /nomad/api-docs/json-jobs
+[`system`]: /nomad/docs/schedulers#system
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/scale.mdx b/content/nomad/v1.9.x/content/docs/commands/job/scale.mdx
new file mode 100644
index 0000000000..a747c3d51c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/scale.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: 'nomad job scale command reference'
+description: |
+  The `nomad job scale` command changes the number of running allocations within
+  a Nomad task group.
+---
+
+# `nomad job scale` command reference
+
+The `job scale` command is used to alter the number of running allocations within
+a Nomad task group.
+
+## Usage
+
+```plaintext
+nomad job scale [options] <job> <group> <count>
+```
+
+The `job scale` commands requires at least two arguments and potentially three
+depending on the job specification. The first argument will be the job ID of the
+job you wish to scale. If the job contains a single task group, you can omit
+including the task group name as the second argument and the command will perform
+the required lookup. The final argument is the count that you wish the job task
+group to be changed to. The count is the absolute value that will be reflected in
+the job specification.
+
+Scale will issue a request to update the matched job and then invoke an interactive
+monitor that exits automatically once the scheduler has processed the request.
+It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the
+`read-job-scaling` and either the `scale-job` or `submit-job` capabilities
+for the job's namespace. The `list-jobs` capability is required to run the
+command with a job prefix instead of the exact job ID. The `read-job`
+capability is required to monitor the resulting evaluation when `-detach` is
+not used.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Scale options
+
+- `-check-index`: If set, the job is only scaled if the passed job modify index
+  matches the server side version. Ignored if value of zero is passed. If a
+  non-zero value is passed, it ensures that the job is being updated from a
+  known state.
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  scale command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Scale the job with ID "job1" which contains a single task group to a count of 8:
+
+```shell-session
+$ nomad job scale job1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Scale the job with ID "job1" which contains a single task group to a count of 8
+and return immediately:
+
+```shell-session
+$ nomad job scale -detach job1 8
+Evaluation ID: b754d6b3-8960-5652-60d8-d47df6eaed13
+```
+
+Scale the job with ID "job1" and the task group "group1" to a count of 8:
+
+```shell-session
+$ nomad job scale job1 group1 8
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Allocation "b7eefe49" created: node "2f0a2f93", group "group1"
+    Allocation "bd54a83d" created: node "2f0a2f93", group "group1"
+    Allocation "fadeaea8" created: node "2f0a2f93", group "group1"
+    Allocation "4bd1397b" modified: node "2f0a2f93", group "group1"
+    Allocation "93684511" modified: node "2f0a2f93", group "group1"
+    Allocation "b409f0a2" modified: node "2f0a2f93", group "group1"
+    Allocation "18f50054" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+[eval status]: /nomad/docs/commands/eval/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/scaling-events.mdx b/content/nomad/v1.9.x/content/docs/commands/job/scaling-events.mdx
new file mode 100644
index 0000000000..594de516bd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/scaling-events.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'nomad job scaling-events command reference'
+description: |
+  The `nomad job scaling-events` command displays scaling events for the specified job.
+---
+
+# `nomad job scaling-events` command reference
+
+The `job scaling-events` command is used display the recent scaling events for
+a given job.
+
+## Usage
+
+```plaintext
+nomad job scaling-events [options] <job>
+```
+
+The `job scaling-events` command requires a single argument, a submitted job's
+ID, and will output the stored scaling events for the job if there are any.
+
+When ACLs are enabled, this command requires a token with either the
+`read-job` or `read-job-scaling` capability for the job's namespace. The
+`list-jobs` capability is required to run the command with a job prefix
+instead of the exact job ID.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Scaling-Events options
+
+- `-verbose`: Show full information.
+
+## Examples
+
+Display the scaling events for the job with ID "job1":
+
+```shell-session
+$ nomad job scaling-events job1
+Task Group  Count   PrevCount  Date
+group1      8       8          2020-10-23T09:06:47+02:00
+group1      8       3          2020-10-23T09:02:42+02:00
+```
+
+Display the scaling events for the job with ID "job1" using the `verbose` flag:
+
+```shell-session
+$ nomad job scaling-events -verbose job1
+Task Group  Count   PrevCount  Error  Message                        Eval ID                               Date
+group1      8       8          false  submitted using the Nomad CLI  b754d6b3-8960-5652-60d8-d47df6eaed13  2020-10-23T09:06:47+02:00
+group1      8       3          false  submitted using the Nomad CLI  529cc88e-8887-725e-2a79-4997f50df153  2020-10-23T09:02:42+02:00
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/status.mdx b/content/nomad/v1.9.x/content/docs/commands/job/status.mdx
new file mode 100644
index 0000000000..3ea05706e2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/status.mdx
@@ -0,0 +1,265 @@
+---
+layout: docs
+page_title: 'nomad job status command reference'
+description: |
+  The `nomad job status` command displays information and status for the specified job.
+---
+
+# `nomad job status` command reference
+
+The `job status` command displays status information for a job.
+
+## Usage
+
+```plaintext
+nomad job status [options] [job]
+```
+
+This command accepts an optional job ID or prefix as the sole argument. If there
+is an exact match based on the provided job ID or prefix, then information about
+the specific job is queried and displayed. Otherwise, a list of matching jobs
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing jobs and a few
+of the most useful status fields for each. Alloc status also shows allocation
+modification time in addition to create time. When the `-verbose` flag is not set,
+allocation creation and modify times are shown in a shortened relative time format
+like `5m ago`.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace. The `list-jobs` capability is required to
+run the command with a job prefix instead of the exact job ID.
+
+@include 'job-status-map.mdx'
+
+## General options
+
+@include 'general_options.mdx'
+
+## Status options
+
+- `-all-allocs`: Display all allocations matching the job ID, even those from an
+  older instance of the job.
+
+- `-evals`: Display the evaluations associated with the job.
+
+- `-short`: Display short output. Used only when a single node is being queried.
+  Drops verbose node allocation data from the output.
+
+- `-json`: Output the job status in JSON format.
+
+- `-t`: Format and display the job status using a Go template.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all jobs:
+
+```shell-session
+$ nomad job status
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Short view of a specific job:
+
+```shell-session
+$ nomad job status -short job1
+ID            = job1
+Name          = Test Job
+Submit Date   = 07/25/17 15:47:11 UTC
+Type          = service
+Priority      = 3
+Datacenters   = dc1,dc2,dc3
+Status        = pending
+Periodic      = false
+Parameterized = false
+```
+
+Full status information of a job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:53:04 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = 6294be0c
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+478ce836  5ed166e8  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information of a periodic job:
+
+```shell-session
+$ nomad job status example
+ID                   = example
+Name                 = example
+Submit Date          = 07/25/17 15:59:52 UTC
+Type                 = batch
+Priority             = 50
+Datacenters          = dc1
+Status               = running
+Periodic             = true
+Parameterized        = false
+Next Periodic Launch = 07/25/17 16:00:30 UTC (5s from now)
+
+Children Job Summary
+Pending  Running  Dead
+0        3        0
+
+Previously Launched Jobs
+ID                           Status
+example/periodic-1500998400  running
+example/periodic-1500998410  running
+example/periodic-1500998420  running
+```
+
+Full status information of a parameterized job:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:59:52 UTC
+Type          = batch
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = true
+
+Parameterized Job
+Payload           = required
+Required Metadata = foo
+Optional Metadata = bar
+
+Parameterized Job Summary
+Pending  Running  Dead
+0        2        0
+
+Dispatched Jobs
+ID                                    Status
+example/dispatch-1485411496-58f24d2d  running
+example/dispatch-1485411499-fa2ee40e  running
+```
+
+Full status information of a job with placement failures:
+
+```shell-session
+$ nomad job status example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created   Modified
+048c1e9e  3f38ecb4  cache       0        run      running  5m ago    5m ago
+250f9dec  3f38ecb4  cache       0        run      running  5m ago    5m ago
+2eb772a1  3f38ecb4  cache       0        run      running  5m ago    5m ago
+a17b7d3d  3f38ecb4  cache       0        run      running  5m ago    5m ago
+```
+
+Full status information showing evaluations with a placement failure. The in
+progress evaluation denotes that Nomad is blocked waiting for resources to
+become available so that it can place the remaining allocations.
+
+```shell-session
+$ nomad job status -evals example
+ID            = example
+Name          = example
+Submit Date   = 07/25/17 15:55:27 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       1       0         4        0       0         0
+
+Evaluations
+ID        Priority  Triggered By        Status    Placement Failures
+e44a39e8  50        deployment-watcher  canceled  false
+97018573  50        deployment-watcher  complete  true
+d5a7300c  50        deployment-watcher  canceled  false
+f05a4495  50        deployment-watcher  complete  true
+e3f3bdb4  50        deployment-watcher  canceled  false
+b5f08700  50        deployment-watcher  complete  true
+73bb867a  50        job-register        blocked   N/A - In Progress
+85052989  50        job-register        complete  true
+
+Placement Failure
+Task Group "cache":
+  * Resources exhausted on 1 nodes
+  * Dimension "cpu exhausted" exhausted on 1 nodes
+
+Latest Deployment
+ID          = bb4b2fb1
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       5        4       4        0
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created                    Modified
+048c1e9e  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+250f9dec  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+2eb772a1  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+a17b7d3d  3f38ecb4  cache       0        run      running  07/25/17 15:55:27 UTC      07/25/17 15:55:27 UTC
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/stop.mdx b/content/nomad/v1.9.x/content/docs/commands/job/stop.mdx
new file mode 100644
index 0000000000..9bfe1779ad
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/stop.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: 'nomad job stop command reference'
+description: |
+  The `nomad job stop` command stops a running job and signals the scheduler
+  to cancel all of the job's running allocations.
+---
+
+# `nomad job stop` command reference
+
+**Alias: `nomad stop`**
+
+The `job stop` command is used to stop a running job and signals the scheduler
+to cancel all the running allocations.
+
+## Usage
+
+```plaintext
+nomad job stop [options] <job 1> <job 2> ... <job N>
+```
+
+The `job stop` command requires at least one job ID or prefix to stop. If there
+is an exact match based on the provided job ID or prefix, then the job will be
+cancelled. Otherwise, a list of matching jobs and information will be
+displayed.
+
+Stop will issue a request to deregister the matched jobs and then invoke an
+interactive monitor that exits automatically once the scheduler has processed
+the requests. It is safe to exit the monitor early using ctrl+c.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+and `read-job` capabilities for the job's namespace. The `list-jobs`
+capability is required to run the command with job prefixes instead of exact
+job IDs.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Stop options
+
+- `-detach`: Return immediately instead of entering monitor mode. After the
+  deregister command is submitted, a new evaluation ID is printed to the screen,
+  which can be used to examine the evaluation using the [eval status] command.
+
+- `-eval-priority`: Override the priority of the evaluations produced as a result
+  of this job deregistration. By default, this is set to the priority of the job.
+
+- `-verbose`: Show full information.
+
+- `-yes`: Automatic yes to prompts.
+
+- `-purge`: Purge is used to stop the job and purge it from the system. If not
+  set, the job will still be queryable and will be purged by the garbage
+  collector.
+
+- `-global`
+  Stop a [multi-region] job in all its regions. By default, `job stop` will
+  stop only a single region at a time. Ignored for single-region jobs.
+
+- `-no-shutdown-delay`
+  Ignore the group and task [`shutdown_delay`] configuration so that
+  there is no delay between service deregistration and task
+  shutdown. Note that using this flag will result in failed network
+  connections to the allocations being stopped.
+
+## Examples
+
+Stop the job with ID "job1":
+
+```shell-session
+$ nomad job stop job1
+==> Monitoring evaluation "43bfe672"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "43bfe672" finished with status "complete"
+```
+
+Stop multiple jobs:
+
+```shell-session
+$ nomad job stop job1 job2
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "166c39c5"
+==> 2022-12-16T15:19:28-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job1"
+    2022-12-16T15:19:28-08:00: Evaluation triggered by job "job2"
+    2022-12-16T15:19:28-08:00: Evaluation within deployment: "90885ce7"
+    2022-12-16T15:19:28-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:28-08:00: Evaluation "166c39c5" finished with status "complete"
+==> 2022-12-16T15:19:28-08:00: Monitoring deployment "90885ce7"
+  ✓ Deployment "90885ce7" successful
+
+    2022-12-16T15:19:28-08:00
+    ID          = 90885ce7
+    Job ID      = job1
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example     1        1       1        0          2022-12-16T15:29:03-08:00
+==> 2022-12-16T15:19:29-08:00: Monitoring evaluation "049404c2"
+    2022-12-16T15:19:29-08:00: Evaluation within deployment: "a13df8f8"
+    2022-12-16T15:19:29-08:00: Evaluation status changed: "pending" -> "complete"
+==> 2022-12-16T15:19:29-08:00: Evaluation "049404c2" finished with status "complete"
+==> 2022-12-16T15:19:29-08:00: Monitoring deployment "a13df8f8"
+  ✓ Deployment "a13df8f8" successful
+
+    2022-12-16T15:19:29-08:00
+    ID          = a13df8f8
+    Job ID      = job2
+    Job Version = 0
+    Status      = successful
+    Description = Deployment completed successfully
+
+    Deployed
+    Task Group  Desired  Placed  Healthy  Unhealthy  Progress Deadline
+    example2    1        1       1        0          2022-12-16T15:29:16-08:00
+```
+
+Stop the job with ID "job1" and return immediately:
+
+```shell-session
+$ nomad job stop -detach job1
+507d26cb
+```
+
+[eval status]: /nomad/docs/commands/eval/status
+[multi-region]: /nomad/docs/job-specification/multiregion
+[`shutdown_delay`]: /nomad/docs/job-specification/group#shutdown_delay
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/tag.mdx b/content/nomad/v1.9.x/content/docs/commands/job/tag.mdx
new file mode 100644
index 0000000000..0df49dd222
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/tag.mdx
@@ -0,0 +1,101 @@
+---
+layout: docs
+page_title: 'nomad job tag command reference'
+description: |
+  The `nomad job tag` command manages versions. The `nomad job tag apply` command saves a job version tag, and the `nomad job tag unset` command removes a job version tag.
+---
+
+
+# `nomad job tag` command reference
+
+@include 'version/tag-reason.mdx'
+
+Use the `job tag` command to manage tags for job versions. `job tag` has the
+following subcommands:
+
+- [`job tag apply`](#apply): Save a job version tag.
+- [`job tag unset`](#unset): Remove a tag from a job version.
+
+## Usage
+
+```shell
+nomad job tag <subcommand> [options] [args]
+```
+
+## Apply
+
+Use `job tag apply` to create or modify a version tag.
+
+### Apply usage
+
+```shell-session
+nomad job tag apply [options] <job_id>
+```
+
+### General options
+
+<details>
+<summary>Expand for general options</summary>
+
+@include 'general_options.mdx'
+
+</details>
+
+### Apply options
+
+- `name`: Specifies the name of the tag. Must be unique per job.
+- `description`: If set, specifies a description for the tag.
+- `version`: If set, specifies the version of the job to tag. If not provided, Nomad tags the latest version of the job.
+
+### Apply examples
+
+This example tags the latest version of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -name "golden-version" \
+		-description "The version we can roll back to." \
+    hello-world
+```
+
+This example tags version zero of the job `hello-world`.
+
+```shell-session
+$ nomad job tag apply -version 0 \
+      -name "golden-version" \
+      hello-world
+```
+
+## Unset
+
+Use `nomad job tag unset` to delete a tag from a version. This command requires a job name and a tag name.
+
+### Unset usage
+
+```shell-session
+nomad job tag unset [options] <job_id>
+```
+
+### General options
+
+<details>
+<summary>Expand for general options</summary>
+
+@include 'general_options.mdx'
+
+</details>
+
+### Unset options
+
+- `name`: Specifies the name of the tag to remove from the job version.
+
+### Examples
+
+This example removes the `golden-version` tag from the `hello-world` job.
+
+```shell-session
+$ nomad job tag unset -name "golden-version" hello-world
+```
+
+[diff]: /nomad/docs/commands/job/history/
+[revert]: /nomad/docs/commands/job/revert/
+
diff --git a/content/nomad/v1.9.x/content/docs/commands/job/validate.mdx b/content/nomad/v1.9.x/content/docs/commands/job/validate.mdx
new file mode 100644
index 0000000000..f9ccc324bf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/job/validate.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'nomad job validate command reference'
+description: >
+  The `nomad job validate` command checks a job specification for syntax
+  errors and validation problems.
+---
+
+# `nomad job validate` command reference
+
+**Alias: `nomad validate`**
+
+The `job validate` command is used to check an HCL [job specification] for any
+syntax errors or validation problems.
+
+## Usage
+
+```plaintext
+nomad job validate <file>
+```
+
+The `job validate` command requires a single argument, specifying the path to a
+file containing an HCL [job specification]. This file will be read and the job
+checked for any problems. If the supplied path is "-", the job file is read from
+STDIN. Otherwise it is read from the file at the supplied path or downloaded and
+read from URL specified. Nomad downloads the job file using [`go-getter`] and
+supports `go-getter` syntax.
+
+On successful validation, exit code 0 will be returned, otherwise an exit code
+of 1 indicates an error.
+
+The run command will set the `vault_token` of the job based on the following
+precedence, going from highest to lowest: the `-vault-token` flag, the
+`$VAULT_TOKEN` environment variable and finally the value in the job file.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the job's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Validate options
+
+- `-json`: Parses the job file as JSON. If the outer object has a Job field,
+  such as from "nomad job inspect" or "nomad run -output", the value of the
+  field is used as the job.
+
+- `-hcl2-strict`: Whether an error should be produced from the HCL2 parser where
+  a variable has been supplied which is not defined within the root variables.
+  Defaults to true.
+
+- `-vault-token`: Used to validate if the user submitting the job has
+  permission to run the job according to its Vault policies. A Vault token must
+  be supplied if the [`vault` block `allow_unauthenticated`] is disabled in
+  the Nomad server configuration. If the `-vault-token` flag is set, the passed
+  Vault token is added to the jobspec before sending to the Nomad servers. This
+  allows passing the Vault token without storing it in the job file. This
+  overrides the token found in the `$VAULT_TOKEN` environment variable and the
+  [`vault_token`] field in the job file. This token is cleared from the job
+  after validating and cannot be used within the job executing environment. Use
+  the `vault` block when templating in a job with a Vault token.
+
+- `-vault-namespace`: If set, the passed Vault namespace is stored in the job
+  before sending to the Nomad servers.
+
+- `-var=<key=value>`: Variable for template, can be used multiple times.
+
+- `-var-file=<path>`: Path to HCL2 file containing user variables.
+
+## Examples
+
+Validate a JSON job with invalid syntax:
+
+```shell-session
+$ nomad job validate -json example.json
+Job validation errors:
+1 error occurred:
+        * Missing job datacenters
+```
+
+Validate a job that has a configuration that causes warnings:
+
+```shell-session
+$ nomad job validate example.nomad.hcl
+Job Warnings:
+1 warning(s):
+
+* Group "cache" has warnings: 1 error(s) occurred:
+
+* Update max parallel count is greater than task group count (6 > 3). A destructive change would result in the simultaneous replacement of all allocations.
+
+Job validation successful
+```
+
+[`go-getter`]: https://github.com/hashicorp/go-getter
+[job specification]: /nomad/docs/job-specification
+[`vault` block `allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault_token`]: /nomad/docs/job-specification/job#vault_token
diff --git a/content/nomad/v1.9.x/content/docs/commands/license/get.mdx b/content/nomad/v1.9.x/content/docs/commands/license/get.mdx
new file mode 100644
index 0000000000..0ed032eaf4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/license/get.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad license get command reference'
+description: |
+  The `nomad license get` command fetches the Nomad Enterprise license from the Nomad server.
+---
+
+# `nomad license get` command reference
+
+The `license get` command is used to retrieve the current Nomad Enterprise
+license. The command is not forwarded to the Nomad leader, and will return
+the license from the specific server being contacted.
+
+~> License commands are only available with Nomad Enterprise.
+
+## Usage
+
+```plaintext
+nomad license get [options]
+```
+
+When ACLs are enabled, this command requires a token with the 'operator:read'
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad license get
+
+Product        = nomad
+License Status = valid
+License ID     = e23f63b1-00ec-4e67-e926-c22e7937ceec
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2020-05-09 00:00:00 +0000 UTC
+Terminates At  = 2020-05-10 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Preemption
+        Audit Logging
+        Setinel Policies
+```
+
+```shell-session
+$ nomad license get -stale=true
+
+Product        = nomad
+License Status = valid
+License ID     = 8c647f6c-1e6d-18d8-7f05-92c4d8110b2d
+Customer ID    = 350356e5-8aec-bdf4-8510-b205079ccad2
+Issued At      = 2021-03-31 14:21:16.969610774 +0000 UTC
+Expires At     = 2022-04-01 00:00:00 +0000 UTC
+Terminates At  = 2022-04-04 00:00:00 +0000 UTC
+Datacenter     = *
+Modules:
+        governance-policy
+        multicluster-and-efficiency
+Licensed Features:
+        Automated Upgrades
+        Enhanced Read Scalability
+        Redundancy Zones
+        Namespaces
+        Resource Quotas
+        Audit Logging
+        Sentinel Policies
+        Multiregion Deployments
+        Automated Backups
+        Multi-Vault Namespaces
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/license/index.mdx b/content/nomad/v1.9.x/content/docs/commands/license/index.mdx
new file mode 100644
index 0000000000..3ef6d9644b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/license/index.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: 'nomad license command reference'
+description: |
+  The `nomad license` command gets or inspects a Nomad Enterprise license.
+---
+
+# `nomad license` command reference
+
+~> License commands are only available with Nomad Enterprise.
+
+The `license` commands can be used to retrieve license information from a server,
+or inspect and validate a license.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+## Usage
+
+Usage: `nomad license <subcommand> [options]`
+
+Run `nomad license <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`license get`][get] - Get the current license from a server
+- [`license inspect`][inspect] - Inspect and validate a license
+
+[get]: /nomad/docs/commands/license/get 'Get the current license from a server'
+[inspect]: /nomad/docs/commands/license/inspect 'Inspect and validate a license'
diff --git a/content/nomad/v1.9.x/content/docs/commands/license/inspect.mdx b/content/nomad/v1.9.x/content/docs/commands/license/inspect.mdx
new file mode 100644
index 0000000000..3dd520ec23
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/license/inspect.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad license inspect command reference'
+description: |
+  The `nomad license inspect` command inspects a Nomad Enterprise license to see if it is valid with the installed Nomad binary.
+---
+
+# `nomad license inspect` command reference
+
+<EnterpriseAlert>
+  This command is only present in Nomad Enterprise.
+</EnterpriseAlert>
+
+The `license inspect` command is used to inspect and validate a Nomad Enterprise
+license. It will read the license from a file on disk or an environment variable
+and exit non-0 if the license is not valid with the Nomad binary.
+
+This command should always be run with the new binary before upgrading Nomad on a server,
+as the server agent will not start with an invalid license.
+
+## Usage
+
+```plaintext
+nomad license inspect [/path/to/license.hclic]
+```
+
+## Examples
+
+With a license file argument:
+
+```shell-session
+$ nomad license inspect /path/to/nomad/license.hclic
+Source: /path/to/nomad/license.hclic
+Product: nomad
+License ID: aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa
+Customer ID: bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb
+Installation ID: *
+Issue Time: 2021-12-01 17:49:23.021041516 +0000 UTC
+Start Time: 2021-12-01 00:00:00 +0000 UTC
+Expiration Time: 2023-12-01 00:00:00 +0000 UTC
+Termination Time: 2024-01-01 00:00:00 +0000 UTC
+Build Date: 2000-01-01 00:00:00 +0000 UTC
+Flags: {
+   "modules": [
+      "multicluster-and-efficiency",
+      "governance-policy"
+   ]
+}
+
+License is valid
+```
+
+With a license file environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE_PATH=/path/to/nomad/license.hclic
+$ nomad license inspect
+Source: /path/to/nomad/license.hclic (path from the NOMAD_LICENSE_PATH environment variable)
+Product: nomad
+.....
+License is valid
+```
+
+With a license string environment variable:
+
+```shell-session
+$ export NOMAD_LICENSE=full-license-text-string
+$ nomad license inspect
+Source: NOMAD_LICENSE environment variable
+.....
+License is valid
+```
+
+## Example error
+
+```shell-session
+$ nomad license inspect license.hclic
+...
+Validation Errors:
+   * license is no longer valid
+   * license expiration date is before version build date: expiration=2023-01-13T23:59:59Z build=2023-03-17T00:00:00Z
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/login.mdx b/content/nomad/v1.9.x/content/docs/commands/login.mdx
new file mode 100644
index 0000000000..2b3a8a479f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/login.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad login command reference'
+description: |
+  The `nomad login` command uses OpenID Connect (OIDC) to authenticate a user with a single sign-on (SSO) provider. Nomad creates an access control list (ACL) token after successful authentication.
+---
+
+# `nomad login` command reference
+
+The `login` command is used to log in to an SSO provider and exchange the third
+party credentials for a newly minted Nomad ACL token.
+
+## Usage
+
+```plaintext
+nomad login [options]
+```
+
+The login command will exchange the provided third party credentials with the
+requested auth method for a newly minted Nomad ACL token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Login options
+
+- `-method`: The name of the ACL auth method to log in via. If the cluster
+  administrator has configured a default, this flag is optional.
+
+- `-oidc-callback-addr`: The address to use for the local OIDC callback server.
+  This should be given in the form of `<IP>:<PORT>` and defaults to
+  `localhost:4649`.
+
+- `-json`: Output the ACL token in JSON format.
+
+- `-t`: Format and display the ACL token using a Go template.
+
+## Examples
+
+Login using an OIDC provider:
+
+```shell-session
+$ nomad login -method=auth0
+Successfully logged in via OIDC and auth0
+
+Accessor ID  = 68123fee-1e8b-7ecc-5b34-505ecd2dcb80
+Secret ID    = a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+Name         = OIDC-auth0
+Type         = client
+Global       = false
+Create Time  = 2023-01-12 14:13:04.863238 +0000 UTC
+Expiry Time  = 2023-01-12 14:23:04.863238 +0000 UTC
+Create Index = 30
+Modify Index = 30
+Policies     = [node-read]
+
+Roles
+ID                                    Name
+ac9d4281-2079-aadb-6740-625f4ed156d8  engineering
+
+$ export NOMAD_TOKEN=a47ed236-5a51-cadf-2ad0-4cd0fd5bc393
+$ nomad ...
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/monitor.mdx b/content/nomad/v1.9.x/content/docs/commands/monitor.mdx
new file mode 100644
index 0000000000..8fb6875aea
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/monitor.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'nomad monitor command reference'
+description: |
+  The `nomad monitor` command streams log messages for a given agent. Configure log level, log output, node ID, and server ID.
+---
+
+# `nomad monitor` command reference
+
+The `nomad monitor` command streams log messages for a given agent.
+
+## Usage
+
+```plaintext
+nomad monitor [options]
+```
+
+The nomad monitor command can be used to stream the logs of a
+running Nomad agent. Monitor will follow logs and exit when
+interrupted or until the remote agent quits.
+
+The power of the monitor command is that it allows you to log
+the agent at a relatively high log level (such as "warn"),
+but still access debug logs and watch the debug logs if necessary.
+The monitor command also allows you to specify a single client node id to follow.
+
+When ACLs are enabled, this command requires a token with the `agent:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Monitor options
+
+- `-log-level`: The log level to use for log streaming. Defaults to `info`.
+  Possible values include `trace`, `debug`, `info`, `warn`, `error`
+
+- `-log-include-location`: Include file and line information in each log line.
+  The default is `false`.
+
+- `-node-id`: Specifies the client node-id to stream logs from. If no
+  node-id is given the nomad server from the -address flag will be used.
+
+- `-server-id`: Specifies the nomad server id to stream logs from. Accepts
+  server names from `nomad server members` and also a special `leader` option
+  which will target the current leader.
+
+- `-json`: Stream logs in json format
+
+## Examples
+
+```shell-session
+$ nomad monitor -log-level=DEBUG -node-id=a57b2adb-1a30-2dda-8df0-25abb0881952
+2019-11-04T12:22:08.528-0500 [DEBUG] http: request complete: method=GET path=/v1/agent/health?type=server duration=1.445739ms
+2019-11-04T12:22:09.892-0500 [DEBUG] nomad: memberlist: Stream connection from=127.0.0.1:53628
+
+$ nomad monitor -log-level=DEBUG -json=true
+{"@level":"debug","@message":"request complete"...}
+
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/apply.mdx
new file mode 100644
index 0000000000..54178449ee
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/apply.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'nomad namespace apply command reference'
+description: |
+  The `nomad namespace apply` command creates or updates a Nomad namespace.
+---
+
+# `nomad namespace apply` command reference
+
+The `namespace apply` command is used create or update a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace apply [options] <input>
+```
+
+Apply is used to create or update a namespace. The HCL specification file
+will be read from stdin by specifying "-", otherwise a path to the file is
+expected.
+
+Instead of a file, you may instead pass the namespace name to create
+or update as the only argument.
+
+If ACLs are enabled, this command requires a management ACL token. In federated
+clusters, the namespace will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply options
+
+- `-quota` : An optional quota to apply to the namespace.
+
+- `-description` : An optional human readable description for the namespace.
+
+- `-json` : Parse the input as a JSON namespace specification.
+
+## Examples
+
+Create a namespace with a quota:
+
+```shell-session
+$ nomad namespace apply -description "Prod API servers" -quota prod api-prod
+Successfully applied namespace "api-prod"!
+```
+
+Remove a quota from a namespace:
+
+```shell-session
+$ nomad namespace apply -quota= api-prod
+```
+
+Create a namespace from a file:
+```shell-session
+$ cat namespace.hcl
+name        = "dev"
+description = "Namespace for developers"
+
+capabilities {
+  enabled_task_drivers   = ["docker", "exec"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+meta {
+  owner        = "John Doe"
+  contact_mail = "john@mycompany.com"
+}
+$ nomad namespace apply namespace.hcl
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/delete.mdx
new file mode 100644
index 0000000000..ee3a70b206
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/delete.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad namespace delete command reference'
+description: |
+  The `nomad namespace delete` command deletes a namespace.
+---
+
+# `nomad namespace delete` command reference
+
+The `namespace delete` command is used delete a namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace delete [options] <namespace>
+```
+
+The `namespace delete` command requires the name of the namespace to be deleted.
+
+If ACLs are enabled, this command requires a management ACL token.
+
+You cannot delete a namespace that has non-terminal jobs or allocations,
+existing CSI volumes or variables attached to it, or quotas associated with it.
+In federated clusters, you cannot delete a namespace that has any of the above
+in any of the federated regions.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a namespace
+
+```shell-session
+$ nomad namespace delete api-prod
+Successfully deleted namespace "api-prod"!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/index.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/index.mdx
new file mode 100644
index 0000000000..203e6cdfc3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad namespace command reference'
+description: |
+  The nomad namespace reference command interact with namespaces. Create, inspect, and delete a namespace. Display status information and list namespaces.
+---
+
+# Command: namespace
+
+The `namespace` command is used to interact with namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+Usage: `nomad namespace <subcommand> [options]`
+
+Run `nomad namespace <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`namespace apply`][apply] - Create or update a namespace
+- [`namespace delete`][delete] - Delete a namespace
+- [`namespace inspect`][inspect] - Inspect a namespace
+- [`namespace list`][list] - List available namespaces
+- [`namespace status`][status] - Display a namespace's status
+
+In [federated][] clusters, all namespace updates are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+[apply]: /nomad/docs/commands/namespace/apply 'Create or update a namespace'
+[delete]: /nomad/docs/commands/namespace/delete 'Delete a namespace'
+[inspect]: /nomad/docs/commands/namespace/inspect 'Inspect a namespace'
+[list]: /nomad/docs/commands/namespace/list 'List available namespaces'
+[status]: /nomad/docs/commands/namespace/status "Display a namespace's status"
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/inspect.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/inspect.mdx
new file mode 100644
index 0000000000..98061d6247
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/inspect.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'nomad namespace inspect command reference'
+description: >
+  The `nomad namespace inspect` command displays raw information about a
+  particular namespace.
+---
+
+# `nomad namespace inspect` command reference
+
+The `namespace inspect` command is used to view raw information about a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace inspect [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Inspect options
+
+- `-t` : Format and display the namespace using a Go template.
+
+## Examples
+
+Inspect a namespace:
+
+```shell-session
+$ nomad namespace inspect default
+{
+    "CreateIndex": 5,
+    "Description": "Default shared namespace",
+    "ModifyIndex": 38,
+    "Name": "default",
+    "Quota": "shared-default-quota"
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/list.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/list.mdx
new file mode 100644
index 0000000000..bb69d29104
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/list.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'nomad namespace list command reference'
+description: |
+  The `nomad namespace list` command displays a list of namespaces.
+---
+
+# `nomad namespace list` command reference
+
+The `namespace list` command is used list available namespaces.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace list [options]
+```
+
+The `namespace list` command requires no arguments.
+
+If ACLs are enabled, this command requires a management ACL token to view all
+namespaces. A non-management token can be used to list namespaces for which it
+has an associated capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-json` : Output the namespaces in their JSON format.
+
+- `-t` : Format and display the namespaces using a Go template.
+
+## Examples
+
+List all namespaces:
+
+```shell-session
+$ nomad namespace list
+Name      Description
+default   Default shared namespace
+api-prod  Production instances of backend API servers
+api-qa    QA instances of backend API servers
+web-prod  Production instances of webservers
+web-qa    QA instances of webservers
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/namespace/status.mdx b/content/nomad/v1.9.x/content/docs/commands/namespace/status.mdx
new file mode 100644
index 0000000000..39d89922f3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/namespace/status.mdx
@@ -0,0 +1,78 @@
+---
+layout: docs
+page_title: 'nomad namespace status command reference'
+description: >
+  The `nomad namespace status` command displays status information for the specified namespace.
+---
+
+# `nomad namespace status` command reference
+
+The `namespace status` command is used to view the status of a particular
+namespace.
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+## Usage
+
+```plaintext
+nomad namespace status [options] <namespace_name>
+```
+
+If ACLs are enabled, this command requires a management ACL token or a token
+that has a capability associated with the namespace.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status options
+
+- `-json` : Output the namespace status in its JSON format.
+- `-t` : Format and display the namespace status using a Go template.
+
+## Examples
+
+View the status of a namespace:
+
+```shell-session
+$ nomad namespace status default
+Name                 = api-prod
+Description          = Prod API servers
+Quota                = prod
+EnabledDrivers       = docker,exec
+DisabledDrivers      = raw_exec
+EnabledNetworkModes  = bridge,cni/custom
+DisabledNetworkModes = host
+
+Metadata
+contact = platform-eng@example.com
+
+Quota Limits
+Region  CPU Usage   Memory Usage
+global  500 / 2500  256 / 2000
+```
+
+The `-json` flag can be used to get the namespace status in json format:
+
+```shell-session
+$ nomad namespace status -json default
+{
+    "Capabilities": null,
+    "CreateIndex": 1,
+    "Description": "Default shared namespace",
+    "Meta": null,
+    "ModifyIndex": 1,
+    "Name": "default",
+    "Quota": ""
+}
+
+Or use the `-t` flag to format and display the status using a Go template:
+
+```shell-session
+$ nomad namespace status -t {{.Description}} default
+Default shared namespace
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/apply.mdx
new file mode 100644
index 0000000000..62e05ccf45
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/apply.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: 'nomad node pool apply command reference'
+description: |
+  The `nomad node pool apply` command creates or updates a node pool.
+---
+
+# `nomad node pool apply` command reference
+
+The `node pool apply` command is used to create or update a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool apply [options] <input>
+```
+
+Apply is used to create or update a node pool. The specification file is read
+from stdin by specifying `-`, otherwise a path to the file is expected.
+
+If ACLs are enabled, this command requires a token with the `write` capability
+in a `node_pool` policy that matches the node pool being targeted. In federated
+clusters, the node pool will be created in the authoritative region and will be
+replicated to all federated regions.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply options
+
+- `-json`: Parse the input as a JSON node pool specification.
+
+## Examples
+
+Create a node pool from a file:
+
+```hcl
+# prod_pool.nomad.hcl
+node_pool "prod" {
+  description = "Node pool for production workloads."
+
+  meta {
+    env = "prod"
+  }
+
+  # Available only in Nomad Enterprise.
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply prod_pool.nomad.hcl
+Successfully applied node pool "prod"!
+```
+
+Create a node pool from stdin:
+
+```shell-session
+$ cat prod_pool.nomad.hcl | nomad node pool apply -
+Successfully applied node pool "prod"!
+```
+
+```shell-session
+$ cat <<EOF | nomad node pool apply -
+node_pool "dev" {
+  description = "Node pool for dev workloads."
+}
+EOF
+Successfully applied node pool "dev"!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/delete.mdx
new file mode 100644
index 0000000000..e85cbd5db4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool delete command reference'
+description: |
+  The `nomad node pool delete` command deletes the specified node pool.
+---
+
+# `nomad node pool delete` command reference
+
+The `node pool delete` command is used delete a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool delete [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the 'delete'
+capability in a `node_pool` policy that matches the node pool being targeted.
+
+You cannot delete a node pool that has nodes or non-terminal jobs. In federated
+clusters, you cannot delete a node pool that has nodes or non-terminal jobs in
+any of the federated regions.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a node pool:
+
+```shell-session
+$ nomad node pool delete dev
+Successfully deleted node pool "dev"!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/index.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/index.mdx
new file mode 100644
index 0000000000..8a75dc9892
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad node pool command reference'
+description: |
+  The `nomad node pool` command interact with node pools. Generate an example node pool specification. Create, update, and delete a node pool. Display a list of node pools and information about a specific node pool. Display jobs and nodes in a node pool.
+---
+
+# `nomad node pool` command reference
+
+The `node pool` command is used to interact with node pools.
+
+## Usage
+
+Usage: `nomad node pool <subcommand> [options]`
+
+Run `nomad node pool <subcommand> -h` for help on that subcommand. The
+following subcommands are available:
+
+- [`node pool apply`][apply] - Create or update a node pool.
+
+- [`node pool delete`][delete] - Delete a node pool.
+
+- [`node pool info`][info] - Fetch information on an existing node pool.
+
+- [`node pool init`][init] - Generate an example node pool specification.
+
+- [`node pool jobs`][jobs] - Retrieve a list of jobs in a node pool.
+
+- [`node pool list`][list] - Retrieve a list of node pools.
+
+- [`node pool nodes`][nodes] - Retrieve a list of nodes in a node pool.
+
+[apply]: /nomad/docs/commands/node-pool/apply
+[delete]: /nomad/docs/commands/node-pool/delete
+[info]: /nomad/docs/commands/node-pool/info
+[init]: /nomad/docs/commands/node-pool/init
+[jobs]: /nomad/docs/commands/node-pool/jobs
+[list]: /nomad/docs/commands/node-pool/list
+[nodes]: /nomad/docs/commands/node-pool/nodes
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/info.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/info.mdx
new file mode 100644
index 0000000000..5eefc3ee50
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/info.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad node pool info command reference'
+description: |
+  The `nomad node pool info` command displays information about a node pool.
+---
+
+# `nomad node pool info` command reference
+
+The `node pool info` command is used to fetch information about an existing
+node pool.
+
+## Usage
+
+```plaintext
+nomad node pool info [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability
+in a `node_pool` policy that matches the node pool being targeted.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Info options
+
+- `-json`: Output the node pool in its JSON format.
+
+- `-t`: Format and display node pool using a Go template.
+
+## Examples
+
+Retrieve information on a node pool:
+
+```shell-session
+$ nomad node pool info prod
+Name        = prod
+Description = Node pool for production workloads.
+
+Metadata
+env = production
+
+Scheduler Configuration
+Scheduler Algorithm = spread
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool info -json prod
+{
+    "CreateIndex": 39,
+    "Description": "Node pool for production workloads.",
+    "Meta": {
+        "env": "production"
+    },
+    "ModifyIndex": 39,
+    "Name": "prod",
+    "SchedulerConfiguration": {
+        "SchedulerAlgorithm": "spread"
+    }
+}
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/init.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/init.mdx
new file mode 100644
index 0000000000..6138a10ae0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad node pool init command reference'
+description: |
+  The `nomad node pool init` command generates an example node pool specification.
+---
+
+# `nomad node pool init` command reference
+
+The `nomad node pool init` command creates an example node pool specification
+file that you can use as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad node pool init <filename>
+```
+
+When no filename is supplied, a default filename of "pool.nomad.hcl" or
+"pool.nomad.json" will be used depending on the output format.
+
+## Init options
+
+- `-out` `(enum: hcl | json)`: Format of generated node pool
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example node pool specification:
+
+```shell-session
+$ nomad node pool init
+Example node pool specification written to pool.nomad.hcl
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/jobs.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/jobs.mdx
new file mode 100644
index 0000000000..d20f892f1a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/jobs.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: 'nomad node pool jobs command reference'
+description: |
+  The `nomad node pool jobs` command displays jobs in the specified node pool.
+---
+
+# `nomad node pool jobs` command reference
+
+The `node pool jobs` command is used to list jobs in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool jobs [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `read` capability in
+a `node_pool` policy that matches the node pool being targeted. The results will
+be filtered by the namespaces where the token has `read-job` capability.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Jobs options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the jobs in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display jobs using a Go template.
+
+## Examples
+
+List jobs in a specific namespace in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace default prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+List jobs in all namespaces in the `prod` node pool:
+
+```shell-session
+$ nomad node pool jobs -namespace '*' prod
+ID       Namespace  Type     Priority  Status          Submit Date
+job1     default    service  80        running         07/25/17 15:47:11 UTC
+job2     default    batch    40        complete        07/24/17 19:22:11 UTC
+job3     system     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool jobs -per-page 2 prod
+ID       Type     Priority  Status          Submit Date
+job1     service  80        running         07/25/17 15:47:11 UTC
+job2     batch    40        complete        07/24/17 19:22:11 UTC
+
+Results have been paginated. To get the next page run:
+
+nomad node pool jobs -per-page 2 -page-token job3 prod
+
+$ nomad node pool jobs -per-page 2 -page-token job3 prod
+ID       Type     Priority  Status          Submit Date
+job3     service  50        dead (stopped)  07/22/17 16:34:48 UTC
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/list.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/list.mdx
new file mode 100644
index 0000000000..6a949785cd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/list.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: 'nomad node pool list command reference'
+description: |
+  The `nomad node pool list` command displays all node pools or those matching a filter expression.
+---
+
+# `nomad node pool list` command reference
+
+The `node pool list` command is used to list existing node pools.
+
+## Usage
+
+```plaintext
+nomad node pool list [options]
+```
+
+If ACLs are enabled, this command requires a management token to view all node
+pools. A non-management token can be used to list node pools for which the
+token has the 'read' capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the node pools in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display node pools using a Go template.
+
+## Examples
+
+List all node pools:
+
+```shell-session
+$ nomad node pool list
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+dev      Node pool for dev workloads.
+prod     Node pool for production workloads.
+```
+
+Retrieve information in JSON format:
+
+```shell-session
+$ nomad node pool list -json
+[
+    {
+        "CreateIndex": 1,
+        "Description": "Node pool with all nodes in the cluster.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "all",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 1,
+        "Description": "Default node pool.",
+        "Meta": null,
+        "ModifyIndex": 1,
+        "Name": "default",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 21,
+        "Description": "Node pool for dev workloads.",
+        "Meta": {
+            "env": "development"
+        },
+        "ModifyIndex": 21,
+        "Name": "dev",
+        "SchedulerConfiguration": null
+    },
+    {
+        "CreateIndex": 39,
+        "Description": "Node pool for production workloads.",
+        "Meta": {
+            "env": "production"
+        },
+        "ModifyIndex": 39,
+        "Name": "prod",
+        "SchedulerConfiguration": {
+            "SchedulerAlgorithm": "spread"
+        }
+    }
+]
+```
+
+Customize output with a Go template:
+
+```shell-session
+$ nomad node pool list -t '{{range .}}{{.Name}} [{{.Meta.env}}] - {{.Description}}{{println}}{{end}}'
+all [<no value>] - Node pool with all nodes in the cluster.
+default [<no value>] - Default node pool.
+dev [development] - Node pool for dev workloads.
+prod [production] - Node pool for production workloads.
+```
+
+```shell-session
+$ nomad node pool info -t "{{.Name}} [{{.Meta.env}}] - {{.Description}}" prod
+prod [production] - Node pool for production workloads.
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool list -per-page 2
+Name     Description
+all      Node pool with all nodes in the cluster.
+default  Default node pool.
+
+Results have been paginated. To get the next page run:
+
+nomad node pool list -per-page 2 -page-token dev
+
+$ nomad node pool list -per-page 2 -page-token dev
+Name  Description
+dev   Node pool for dev workloads.
+prod  Node pool for production workloads.
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.9.x/content/docs/commands/node-pool/nodes.mdx b/content/nomad/v1.9.x/content/docs/commands/node-pool/nodes.mdx
new file mode 100644
index 0000000000..75ed45d1d3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node-pool/nodes.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad node pool nodes command reference'
+description: |
+  The `nomad node pool nodes` command displays nodes in the specified node pool.
+---
+
+# `nomad node pool nodes` command reference
+
+The `node pool nodes` command is used to list nodes in a node pool.
+
+## Usage
+
+```plaintext
+nomad node pool nodes [options] <node-pool>
+```
+
+If ACLs are enabled, this command requires a token with the `node:read`
+capability and the `read` capability in a `node_pool` policy that matches the
+node pool being targeted.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Nodes options
+
+- `-filter`: Specifies an expression used to [filter results][api_filtering].
+
+- `-json`: Output the nodes in JSON format.
+
+- `-page-token`: Where to start [pagination][api_pagination].
+
+- `-per-page`: How many results to show per page. If not specified, or set to
+  `0`, all results are returned.
+
+- `-t`: Format and display nodes using a Go template.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+List nodes in the `prod` node pool:
+
+```shell-session
+$ nomad node pool nodes prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+3ed547cd  dc1  client-1  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Filter nodes with an expression:
+
+```shell-session
+$ nomad node pool nodes -filter='Datacenter == "dc2"' prod
+ID        DC   Name      Class   Drain  Eligibility  Status
+31c5347f  dc2  client-3  <none>  false  eligible     ready
+6e98e378  dc2  client-2  <none>  false  eligible     ready
+```
+
+Paginate list:
+
+```shell-session
+$ nomad node pool nodes -per-page=2 prod
+ID        DC   Name         Class   Drain  Eligibility  Status
+31c5347f  dc2  us-client-3  <none>  false  eligible     ready
+3ed547cd  dc1  us-client-1  <none>  false  eligible     ready
+
+Results have been paginated. To get the next page run:
+
+nomad node pool nodes -per-page=2 prod -page-token 6e98e378-b41a-86ac-8e5e-5ca8ab66236d
+```
+
+[api_filtering]: /nomad/api-docs#filtering
+[api_pagination]: /nomad/api-docs#pagination
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/config.mdx b/content/nomad/v1.9.x/content/docs/commands/node/config.mdx
new file mode 100644
index 0000000000..220ccf53e0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/config.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: 'nomad node config command reference'
+description: |
+  The `nomad node config` command displays configuration details for the specified client. You can also update the client's server list with this command.
+---
+
+# `nomad node config` command reference
+
+The `node config` command is used to view or modify client configuration
+details. This command only works on client nodes, and can be used to update
+the running client configurations it supports.
+
+## Usage
+
+```plaintext
+nomad node config [options]
+```
+
+The arguments behave differently depending on the flags given. See each flag's
+description below for specific usage information and requirements.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Node Config options
+
+- `-servers`: List the client's known servers. Client nodes do not participate
+  in the gossip pool, and instead register with these servers periodically over
+  the network. The initial value of this list may come from configuration files
+  using the [`servers`] configuration option in the client block.
+
+  If ACLs are enabled, this option requires a token with the 'agent:read'
+  capability.
+
+- `-update-servers`: Updates the client's server list using the provided
+  arguments. Multiple server addresses may be passed using multiple arguments.
+  When updating the servers list, you must specify ALL of the server nodes you
+  wish to configure. The set is updated atomically. It is an error to specify
+  this flag without any server addresses. If you do _not_ specify a port for each
+  server address, the default port `4647` will be used.
+
+  If ACLs are enabled, this option requires a token with the 'agent:write'
+  capability.
+
+## Examples
+
+Query the currently known servers:
+
+```shell-session
+$ nomad node config -servers
+server1:4647
+server2:4647
+```
+
+Update the list of servers:
+
+```shell-session
+$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4
+
+```
+
+[`servers`]: /nomad/docs/configuration/client#servers
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/drain.mdx b/content/nomad/v1.9.x/content/docs/commands/node/drain.mdx
new file mode 100644
index 0000000000..523d99d87f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/drain.mdx
@@ -0,0 +1,165 @@
+---
+layout: docs
+page_title: 'nomad node drain command reference'
+description: |
+  The `nomad node drain` command turns on or turns off a node's drain mode. Drain mode prevents any new tasks from being allocated to the node and beings migrating all existing allocations to other nodes.
+---
+
+# `nomad node drain` command reference
+
+The `node drain` command is used to toggle drain mode on a given node. Drain
+mode prevents any new tasks from being allocated to the node, and begins
+migrating all existing allocations away.
+
+The exact behavior of drained allocations depends on the job type:
+* Allocations for `service` jobs will be migrated according to their
+  [`migrate`][] block until the drain's deadline is reached. These allocations
+  are not considered rescheduled and their previous [`reschedule`][] attempts
+  will not be propagated to any replacement allocations.
+* Allocations for `batch` and `sysbatch` jobs will wait until they complete or
+  the drain's deadline is reached, whichever comes first. These allocations will
+  not be replaced.
+* Allocations for `system` job allocations will be drained last by
+  default. These allocations will be stopped but not replaced.
+
+By default the `node drain` command blocks until a node is done draining and
+all allocations have terminated. Canceling the `node drain` command _will not_
+cancel the drain. Drains may be canceled by using the `-disable` parameter
+below.
+
+When draining more than one node at a time, it is recommended you first
+disable [scheduling eligibility][eligibility] on all nodes that will be
+drained. For example if you are decommissioning an entire class of nodes,
+first run `node eligibility -disable` on all of their node IDs, and then run
+`node drain -enable`. This will ensure allocations drained from the first node
+are not placed on another node about to be drained.
+
+The [node status] command compliments this nicely by providing the current drain
+status of a given node.
+
+See the [Workload Migration guide] for detailed examples of node draining.
+
+## Usage
+
+```plaintext
+nomad node drain [options] <node>
+```
+
+A `-self` flag can be used to drain the local node. If this is not supplied, a
+node ID or prefix must be provided. If there is an exact match, the drain mode
+will be adjusted for that node. Otherwise, a list of matching nodes and
+information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Drain options
+
+- `-enable`: Enable node drain mode.
+
+- `-disable`: Disable node drain mode.
+
+- `-deadline`: Set the deadline by which all allocations must be moved off the
+  node. Remaining allocations after the deadline are removed from the node,
+  regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `-detach`: Return immediately instead of entering monitor mode.
+
+- `-monitor`: Enter monitor mode directly without modifying the drain status.
+
+- `-force`: Remove allocations off the node immediately, regardless of the
+  allocation's [`migrate`][] block. This will include system jobs and CSI
+  plugins if `-ignore-system` is not also set, and is not safe for use with CSI
+  node plugins if the volumes are not being detached externally (for example, a
+  cloud VM is being terminated).
+
+- `-no-deadline`: No deadline allows the allocations to drain off the node,
+  ignoring the default 1 hour deadline before allocations are removed regardless
+  of their [`migrate`][] block.
+
+- `-ignore-system`: Ignore system allows the drain to complete without
+  stopping system job allocations. By default system jobs (and CSI
+  plugins) are stopped last.
+
+- `-keep-ineligible`: Keep ineligible will maintain the node's scheduling
+  ineligibility even if the drain is being disabled. This is useful when an
+  existing drain is being cancelled but additional scheduling on the node is not
+  desired.
+
+- `-m`: Message for the drain update operation. Registered in drain metadata as
+  `"message"` during drain enable and `"cancel_message"` during drain disable.
+
+- `-meta <key>=<value>`: Custom metadata to store on the drain operation, can be
+  used multiple times.
+
+- `-self`: Drain the local node.
+
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable drain mode on node with ID prefix "4d2ba53b":
+
+```shell-session
+$ nomad node drain -enable f4e8a9e5 -m "node maintenance"
+Are you sure you want to enable drain mode for node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e"? [y/N] y
+2018-03-30T23:13:16Z: Ctrl-C to stop monitoring: will not cancel the node drain
+2018-03-30T23:13:16Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" drain strategy set
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" marked for migration
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" draining
+2018-03-30T23:13:17Z: Alloc "1877230b-64d3-a7dd-9c31-dc5ad3c93e9a" status running -> complete
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" marked for migration
+2018-03-30T23:13:29Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" draining
+2018-03-30T23:13:30Z: Alloc "3fce5308-818c-369e-0bb7-f61f0a1be9ed" status running -> complete
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" marked for migration
+2018-03-30T23:13:41Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" draining
+2018-03-30T23:13:41Z: Node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" has marked all allocations for migration
+2018-03-30T23:13:42Z: Alloc "9a98c5aa-a719-2f34-ecfc-0e6268b5d537" status running -> complete
+2018-03-30T23:13:42Z: All allocations on node "f4e8a9e5-30d8-3536-1e6f-cda5c869c35e" have stopped.
+```
+
+Enable drain mode on the local node:
+
+```shell-session
+$ nomad node drain -enable -self
+...
+```
+
+Enable drain mode but do not stop system jobs:
+
+```shell-session
+$ nomad node drain -enable -ignore-system 4d2ba53b
+...
+```
+
+Disable drain mode but keep the node ineligible for scheduling. Useful for
+inspecting the current state of a misbehaving node without Nomad trying to
+start or migrate allocations:
+
+```shell-session
+$ nomad node drain -disable -keep-ineligible 4d2ba53b
+...
+```
+
+Enable drain mode and detach from monitoring, then reattach later:
+
+```shell-session
+$ nomad node drain -enable -detach -self
+...
+$ nomad node drain -self -monitor
+...
+```
+
+[eligibility]: /nomad/docs/commands/node/eligibility
+[`migrate`]: /nomad/docs/job-specification/migrate
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[node status]: /nomad/docs/commands/node/status
+[workload migration guide]: /nomad/tutorials/manage-clusters/node-drain
+[internals-csi]: /nomad/docs/concepts/plugins/csi
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/eligibility.mdx b/content/nomad/v1.9.x/content/docs/commands/node/eligibility.mdx
new file mode 100644
index 0000000000..306061aee7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/eligibility.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad node eligibility command reference'
+description: >
+  The `nomad node eligibility` command turns on or turns off a node's eligibility to receive placements and run new allocations.
+---
+
+# `nomad node eligibility` command reference
+
+The `node eligibility` command is used to toggle scheduling eligibility for a
+given node. By default nodes are eligible for scheduling meaning they can
+receive placements and run new allocations. Nodes that have their scheduling
+eligibility disabled are ineligible for new placements.
+
+The [`node drain`][drain] command automatically disables eligibility. Disabling
+a drain restore eligibility by default.
+
+Disable scheduling eligibility is useful when draining a set of nodes: first
+disable eligibility on each node that will be drained. Then drain each node.
+If you just drain each node allocations may get rescheduled multiple times as
+they get placed on nodes about to be drained.
+
+Disabling scheduling eligibility may also be useful when investigating poorly
+behaved nodes. It allows operators to investigate the current state of a node
+without the risk of additional work being assigned to it.
+
+## Usage
+
+```plaintext
+nomad node eligibility [options] <node>
+```
+
+A `-self` flag can be used to toggle eligibility of the local node. If this is
+not supplied, a node ID or prefix must be provided. If there is an exact match,
+the eligibility will be adjusted for that node. Otherwise, a list of matching
+nodes and information will be displayed.
+
+It is also required to pass one of `-enable` or `-disable`, depending on which
+operation is desired.
+
+If ACLs are enabled, this option requires a token with the 'node:write'
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Eligibility options
+
+- `-enable`: Enable scheduling eligibility.
+- `-disable`: Disable scheduling eligibility.
+- `-self`: Set eligibility for the local node.
+- `-yes`: Automatic yes to prompts.
+
+## Examples
+
+Enable scheduling eligibility on node with ID prefix "574545c5":
+
+```shell-session
+$ nomad node eligibility -enable 574545c5
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: eligible for scheduling
+```
+
+Disable scheduling eligibility on the local node:
+
+```shell-session
+$ nomad node eligibility -disable -self
+Node "574545c5-c2d7-e352-d505-5e2cb9fe169f" scheduling eligibility set: ineligible for scheduling
+```
+
+[drain]: /nomad/docs/commands/node/drain
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/index.mdx b/content/nomad/v1.9.x/content/docs/commands/node/index.mdx
new file mode 100644
index 0000000000..67994b21d7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/index.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'nomad node command reference'
+description: |
+  The nomad node reference command interacts with nodes. View or modify client configuration. Toggle scheduling eligibility and node drain mode. Display metadata and status information.
+---
+
+# `nomad node` command reference
+
+The `node` command is used to interact with nodes.
+
+## Usage
+
+Usage: `nomad node <subcommand> [options]`
+
+Run `nomad node <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`node config`][config] - View or modify client configuration details
+
+- [`node drain`][drain] - Set drain mode on a given node
+
+- [`node eligibility`][eligibility] - Toggle scheduling eligibility on a given
+  node
+
+- [`node meta`][meta] - Interact with node metadata
+
+- [`node status`][status] - Display status information about nodes
+
+[config]: /nomad/docs/commands/node/config 'View or modify client configuration details'
+[drain]: /nomad/docs/commands/node/drain 'Set drain mode on a given node'
+[eligibility]: /nomad/docs/commands/node/eligibility 'Toggle scheduling eligibility on a given node'
+[meta]: /nomad/docs/commands/node/meta 'Interact with node metadata'
+[status]: /nomad/docs/commands/node/status 'Display status information about nodes'
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/meta/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/node/meta/apply.mdx
new file mode 100644
index 0000000000..7aabe802fc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/meta/apply.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad node meta apply command reference'
+description: |
+  The `nomad node meta apply` command updates node metadata on client agents.
+---
+
+# `nomad node meta apply` command reference
+
+Modify a node's metadata. This command only applies to client agents, and can
+be used to update the scheduling metadata the node registers.
+
+~> Changes are batched and may take up to 10 seconds to propagate to the
+   servers and affect scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta apply [-node-id ...] [-unset ...] key1=value1 ... kN=vN
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## Node Meta Apply options
+
+- `-node-id` - Updates metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-unset` - Unset the comma separated list of keys.
+
+## Examples
+
+```shell-session
+$ nomad node meta apply -unset testing,tempvar ready=1 role=preinit-db
+```
+
+[api]: /nomad/api-docs/client#update-node-metadata
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/meta/index.mdx b/content/nomad/v1.9.x/content/docs/commands/node/meta/index.mdx
new file mode 100644
index 0000000000..d0d3d35122
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/meta/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad node meta command reference'
+description: |
+  The nomad node meta commands read and update node metadata.
+---
+
+# nomad node meta reference
+
+The `meta` command is used to read and update node metadata. This metadata is
+available for [interpolation using the `${meta.<key>}` syntax in jobs][interp].
+
+## Usage
+
+Usage: `nomad node meta <subcommand> [options]`
+
+The `apply` subcommand allows for dynamically updating node metadata. The
+`read` subcommand allows reading all of the metadata set on the client. All
+commands interact directly with a client and allow setting a custom target with
+the `-node-id` option.
+
+Please see the individual subcommand help for detailed usage information:
+
+ - [`apply`][apply] - Modify node metadata
+ - [`read`][read] - Read node metadata
+
+[interp]: /nomad/docs/runtime/interpolation#node-attributes
+[apply]: /nomad/docs/commands/node/meta/apply
+[read]: /nomad/docs/commands/node/meta/read
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/meta/read.mdx b/content/nomad/v1.9.x/content/docs/commands/node/meta/read.mdx
new file mode 100644
index 0000000000..6acf24f364
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/meta/read.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: 'nomad node meta read command reference'
+description: |
+  The nomad node meta read command displays metadata on the specified node.
+---
+
+# nomad node meta read reference
+
+Read a node's metadata. This command only works on client agents. The node
+status command can be used to retrieve node metadata from any agent.
+
+Changes via the "node meta apply" subcommand are batched and may take up to
+10 seconds to propagate to the servers and affect scheduling. This command
+will always return the most recent node metadata while the "node status"
+command can be used to view the metadata that is currently being used for
+scheduling.
+
+This command uses the [`/v1/client/metadata` HTTP API][api].
+
+## Usage
+
+```plaintext
+nomad node meta read [-json] [-node-id ...]
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## Node Meta Read options
+
+- `-node-id` - Reads metadata on the specified node. If not specified the
+  node receiving the request will be used by default.
+
+- `-json` - Output the node metadata in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Example
+
+```shell-session
+$ nomad node meta read -node-id 3b58b0a6
+
+All Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+example                   = a
+
+Dynamic Meta
+example = a
+
+Static Meta
+connect.gateway_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+connect.log_level         = info
+connect.proxy_concurrency = 1
+connect.sidecar_image     = docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}
+```
+
+[api]: /nomad/api-docs/client#read-node-metadata
diff --git a/content/nomad/v1.9.x/content/docs/commands/node/status.mdx b/content/nomad/v1.9.x/content/docs/commands/node/status.mdx
new file mode 100644
index 0000000000..b0a2c0e2ea
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/node/status.mdx
@@ -0,0 +1,402 @@
+---
+layout: docs
+page_title: 'nomad node status command reference'
+description: |
+  The `nomad node status` command displays status information about registered client nodes.
+---
+
+# `nomad node status` command reference
+
+The `node status` command is used to display information about client nodes. A
+node must first be registered with the servers before it will be visible in this
+output.
+
+## Usage
+
+```plaintext
+nomad node status [options] [node]
+```
+
+If no node ID is passed, then the command will enter "list mode" and dump a
+high-level list of all known nodes. This list output contains less information
+but is a good way to get a bird's-eye view of things.
+
+If there is an exact match based on the provided node ID or prefix, then that
+particular node will be queried, and detailed information will be displayed,
+including resource usage statistics. Otherwise, a list of matching nodes and
+information will be displayed. If running the command on a Nomad Client, the
+`-self` flag is useful to quickly access the status of the local node.
+
+If ACLs are enabled, this option requires a token with the 'node:read'
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status options
+
+- `-self`: Query the status of the local node.
+
+- `-stats`: Display detailed resource usage statistics.
+
+- `-allocs`: When a specific node is not being queried, shows the number of
+  running allocations per node.
+
+- `-short`: Display short output. Used only when querying a single node.
+
+- `-verbose`: Show full information.
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-os`: Display operating system name.
+
+- `-quiet`:  Display only node IDs.
+
+- `-json` : Output the node in its JSON format.
+
+- `-t` : Format and display node using a Go template.
+
+## Examples
+
+List view:
+
+```shell-session
+$ nomad node status
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  false  eligible     ready
+1f3f03ea  dev        dc1  node2  <none>  false  eligible     ready
+```
+
+List view, with operating system name:
+
+```shell-session
+$ nomad node status -os
+ID        Node Pool  DC   Name   Class   OS      Drain  Eligibility  Status
+a72dfba2  default    dc1  node1  <none>  ubuntu  false  eligible     ready
+f73e3993  dev        dc1  node2  <none>  centos  false  eligible     ready
+```
+
+List view, with quiet:
+
+```shell-session
+$ nomad node status -quiet
+820561cf-830d-b089-cg03-f2cfc4cecff7
+07949e3a-4c25-e1bf-3dbh-984c2e28fec2
+8bc2c581-37ba-dj08-9f67-53bc217f36f8
+f35be281-85a5-d1e6-d268-6e8a6f0684df
+```
+
+**NOTE**: `-quiet` cannot be used in conjunction with `-verbose` or `-json`.
+
+List view, with running allocations:
+
+```shell-session
+$ nomad node status -allocs
+ID        Node Pool  DC   Name   Class   Drain  Eligibility  Status  Running Allocs
+4d2ba53b  default    dc1  node1  <none>  false  eligible     ready   1
+34dfba32  dev        dc1  node2  <none>  false  eligible     ready   3
+```
+
+Single-node view in short mode:
+
+```shell-session
+$ nomad node status -short 1f3f03ea
+ID        = c754da1f
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h2m25s
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+```
+
+Full output for a single node:
+
+```shell-session
+$ nomad node status 1f3f03ea
+ID        = c754da1f
+Name      = nomad-server01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h42m50s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU           Memory           Disk
+500/2600 MHz  256 MiB/2.0 GiB  300 MiB/32 GiB
+
+Allocation Resource Utilization
+CPU           Memory
+430/2600 MHz  199 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+513/3000 MHz  551 MiB/2.4 GiB  4.2 GiB/52 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+7bff7214  b3a6b9d2  example  cache       run             running
+```
+
+Using `-self` when on a Nomad Client:
+
+```shell-session
+$ nomad node status -self
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+You will note that in the above examples, the **Allocations** output contains
+columns labeled **Desired Status** and **Client status**.
+
+Desired Status represents the goal of the scheduler on the allocation with
+the following valid statuses:
+
+- _run_: The allocation should run
+- _stop_: The allocation should stop
+
+Client Status represents the emergent state of the allocation and include
+the following:
+
+- _pending_: The allocation is pending and will be running
+
+- _running_: The allocation is currently running
+
+- _complete_: The allocation was running and completed successfully
+
+- _failed_: The allocation was running and completed with a non-zero exit code
+
+- _lost_: The node that was running the allocation has failed or has been
+  partitioned
+
+Using `-stats` to see detailed to resource usage information on the node:
+
+```shell-session
+$ nomad node status -stats c754da1f
+ID        = c754da1f
+Name      = nomad-client01
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Drivers
+Driver    Detected  Healthy
+docker    false     false
+exec      true      true
+java      true      true
+qemu      true      true
+raw_exec  true      true
+rkt       true      true
+
+Node Events
+Time                  Subsystem       Message
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected
+2018-03-29T17:23:42Z  Cluster         Node registered
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU            Memory           Disk
+2430/3000 MHz  1.8 GiB/2.4 GiB  3.9 GiB/40 GiB
+
+CPU Stats
+CPU    = cpu0
+User   = 96.94%
+System = 1.02%
+Idle   = 2.04%
+
+CPU    = cpu1
+User   = 97.92%
+System = 2.08%
+Idle   = 0.00%
+
+Memory Stats
+Total     = 2.4 GiB
+Available = 612 MiB
+Used      = 1.8 GiB
+Free      = 312 MiB
+
+Disk Stats
+Device         = /dev/mapper/ubuntu--14--vg-root
+MountPoint     = /
+Size           = 38 GiB
+Used           = 3.9 GiB
+Available      = 32 GiB
+Used Percent   = 10.31%
+Inodes Percent = 3.85%
+
+Device         = /dev/sda1
+MountPoint     = /boot
+Size           = 235 MiB
+Used           = 45 MiB
+Available      = 178 MiB
+Used Percent   = 19.17%
+Inodes Percent = 0.48%
+
+Allocations
+ID        Eval ID   Job ID   Task Group  Desired Status  Client Status
+0b8b9e37  8bf94335  example  cache       run             running
+b206088c  8bf94335  example  cache       run             running
+b82f58b6  8bf94335  example  cache       run             running
+ed3665f5  8bf94335  example  cache       run             running
+24cfd201  8bf94335  example  cache       run             running
+```
+
+To view verbose information about the node:
+
+```shell-session
+$ nomad node status -verbose c754da1f
+ID        = c754da1f-6337-b86d-47dc-2ef4c71aca14
+Name      = nomad
+Node Pool = default
+Class     = <none>
+DC        = dc1
+Drain     = false
+Status    = ready
+Uptime    = 17h7m41s
+
+Host Volumes
+Name  ReadOnly  Source
+
+CSI Volumes
+ID        Name  Namespace  Plugin ID  Schedulable  Access Mode         Mount options
+402f2c83  vol   default    plug       true         single-node-writer  <none>
+
+Drivers
+Driver    Detected  Healthy  Message                        Time
+docker    false     false    Driver docker is not detected  2018-03-29T17:24:42Z
+exec      true      true     <none>                         2018-03-29T17:23:42Z
+java      true      true     <none>                         2018-03-29T17:23:41Z
+qemu      true      true     <none>                         2018-03-29T17:23:41Z
+raw_exec  true      true     <none>                         2018-03-29T17:23:42Z
+rkt       true      true     <none>                         2018-03-29T17:23:42Z
+
+Node Events
+Time                  Subsystem       Message                        Details
+2018-03-29T17:24:42Z  Driver: docker  Driver docker is not detected  driver: docker,
+2018-03-29T17:23:42Z  Cluster         Node registered                <none>
+
+Allocated Resources
+CPU            Memory           Disk
+2500/2600 MHz  1.3 GiB/2.0 GiB  1.5 GiB/32 GiB
+
+Allocation Resource Utilization
+CPU            Memory
+2200/2600 MHz  1.7 GiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+230/3000 MHz  121 MiB/2.4 GiB  6.5 GiB/40 GiB
+
+Allocations
+ID                                    Eval ID                               Job ID   Task Group  Desired Status  Client Status
+3d743cff-8d57-18c3-2260-a41d3f6c5204  2fb686da-b2b0-f8c2-5d57-2be5600435bd  example  cache       run             complete
+
+Attributes
+arch                      = amd64
+cpu.frequency             = 1300.000000
+cpu.modelname             = Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz
+cpu.numcores              = 2
+cpu.totalcompute          = 2600.000000
+driver.docker             = 1
+driver.docker.version     = 1.10.3
+driver.exec               = 1
+driver.java               = 1
+driver.java.runtime       = OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.14.04.2)
+driver.java.version       = 1.7.0_95
+driver.java.vm            = OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
+driver.qemu               = 1
+driver.qemu.version       = 2.0.0
+driver.raw_exec           = 1
+driver.rkt                = 1
+driver.rkt.appc.version   = 0.7.4
+driver.rkt.version        = 1.2.0
+hostname                  = nomad
+kernel.name               = linux
+kernel.version            = 3.19.0-25-generic
+memory.totalbytes         = 2094473216
+nomad.revision            = '270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES'
+nomad.version             = 0.3.2dev
+os.name                   = ubuntu
+os.version                = 14.04
+unique.cgroup.mountpoint  = /sys/fs/cgroup
+unique.network.ip-address = 127.0.0.1
+unique.storage.bytesfree  = 36044333056
+unique.storage.bytestotal = 41092214784
+unique.storage.volume     = /dev/mapper/ubuntu--14--vg-root
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/api.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/api.mdx
new file mode 100644
index 0000000000..b334208244
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/api.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: 'nomad operator api command reference'
+description: |
+  The `nomad operator api` command is a cURL-like utility command for accessing Nomad's HTTP API.
+---
+
+# `nomad operator api` command reference
+
+The `operator api` command allows easy access to Nomad's HTTP API similar to
+the popular [curl] program. Nomad's `operator api` command reads [environment
+variables][envvars] to dramatically ease HTTP API access compared to trying to
+manually write the same command with the third party `curl` command.
+
+For example for the following environment:
+
+```
+NOMAD_TOKEN=d4434353-c797-19e4-a14d-4068241f86a4
+NOMAD_CACERT=$HOME/.nomad/ca.pem
+NOMAD_CLIENT_CERT=$HOME/.nomad/cli.pem
+NOMAD_CLIENT_KEY=$HOME/.nomad/client-key.pem
+NOMAD_TLS_SERVER_NAME=client.global.nomad
+NOMAD_ADDR=https://remote.client123.internal:4646
+```
+
+Accessing Nomad's [`/v1/jobs`][jobs] HTTP endpoint with `nomad operator
+api` would require:
+
+```
+nomad operator api /v1/jobs
+```
+
+Performing the same request using the external `curl` tool would require:
+
+```
+curl \
+  --cacert "$HOME/.nomad/ca.pem" \
+  --cert "$HOME/.nomad/client.pem" \
+  --key "$HOME/.nomad/client-key.pem" \
+  --connect-to "client.global.nomad:4646:remote.client123.internal:4646" \
+  -H "X-Nomad-Token: ${NOMAD_TOKEN}" \
+  https://client.global.nomad:4646/v1/jobs
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## Operator API options
+
+- `-dryrun`: output a curl command instead of performing the HTTP request
+  immediately. Note that you do *not* need the 3rd party `curl` command
+  installed to use `operator api`. The `curl` output from `-dryrun` is intended
+  for use in scripts or running in locations without a Nomad binary present.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-H`: Adds an additional HTTP header to the request. May be specified more
+  than once. These headers take precedence over automatically set ones such as
+  X-Nomad-Token.
+
+- `-verbose`: Output extra information to stderr similar to curl's --verbose
+  flag.
+
+- `-X`: HTTP method of request. If there is data piped to stdin, then the
+  method defaults to POST. Otherwise the method defaults to GET.
+
+## Examples
+
+```shell-session
+$ nomad operator api -verbose /v1/agent/members?pretty
+> GET http://127.0.0.1:4646/v1/agent/members?pretty=
+* Sending request and receiving response...
+< HTTP/1.1 200 OK
+< Date: Wed, 02 Mar 2022 01:10:59 GMT
+< Content-Type: application/json
+< Vary: Accept-Encoding
+{
+    "Members": [
+...
+
+
+$ nomad operator api -region eu-west -filter 'Status == "completed"' -dryrun /v1/evaluations
+curl \
+  -X GET \
+    http://127.0.0.1:4646/v1/evaluations?filter=.Status+%3D%3D+%22completed%22&region=eu-west
+```
+
+
+
+
+[curl]: https://curl.se/
+[envvars]: /nomad/docs/commands#environment-variables
+[jobs]: /nomad/api-docs/jobs
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/get-config.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/get-config.mdx
new file mode 100644
index 0000000000..aba58de81b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/get-config.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot get-config command reference'
+description: |
+  The `nomad operator autopilot get-config` command displays the current Autopilot configuration.
+---
+
+# `nomad operator autopilot get-config` command reference
+
+The Autopilot operator command is used to view the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+The output looks like this:
+
+```shell-session
+$ nomad operator autopilot get-config
+CleanupDeadServers = true
+LastContactThreshold = 200ms
+MaxTrailingLogs = 250
+ServerStabilizationTime = 10s
+RedundancyZoneTag = ""
+DisableUpgradeMigration = false
+UpgradeMigrationTag = ""
+```
+
+- `CleanupDeadServers` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `LastContactThreshold` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `MaxTrailingLogs` - specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `ServerStabilizationTime` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `RedundancyZoneTag` - Controls the node-meta key to use when
+  Autopilot is separating servers into zones for redundancy. Only one server in
+  each zone can be a voting member at one time. If left blank, this feature will
+  be disabled.
+
+- `DisableUpgradeMigration` - Disables Autopilot's upgrade
+  migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `UpgradeVersionTag` - Controls the node-meta key to use for
+  version info when performing upgrade migrations. If left blank, the Nomad
+  version will be used.
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/health.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/health.mdx
new file mode 100644
index 0000000000..e7e6fa8b75
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/health.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot health command reference'
+description: |
+  The `nomad operator autopilot health` command displays the current Autopilot internal health.
+---
+
+# `nomad operator autopilot health` command reference
+
+The Autopilot operator command is used to view the current Autopilot
+state. See the [Autopilot Guide][] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot health [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Output options
+
+- `-json`: Output the Autopilot health in unformatted JSON.
+
+The output will return like below, read about the output of the command in the [API docs][].
+
+```shell-session
+$ nomad operator autopilot health
+Healthy: true
+FailureTolerance: 0
+Leader: e349749b-3303-3ddf-959c-b5885a0e1f6e
+Voters:
+        e349749b-3303-3ddf-959c-b5885a0e1f6e
+Servers:
+ID                                    Name      Address         SerfStatus  Version   Leader  Voter  Healthy  LastContact  LastTerm  LastIndex  StableSince
+e349749b-3303-3ddf-959c-b5885a0e1f6e  node1     127.0.0.1:4647  alive       1.7.5     true    true   true     0s           2         14         2024-02-20 16:40:55 +0000 UTC
+```
+
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
+[api docs]: /nomad/api-docs/operator/autopilot#read-state
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/set-config.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/set-config.mdx
new file mode 100644
index 0000000000..a6f4e26a12
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/autopilot/set-config.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: 'nomad operator autopilot set-config command reference'
+description: |
+  The `nomad operator autopilot set-config` command modifies the current Autopilot configuration.
+---
+
+# `nomad operator autopilot set-config` command reference
+
+The Autopilot operator command is used to set the current Autopilot
+configuration. See the [Autopilot Guide] for more information about Autopilot.
+
+## Usage
+
+```plaintext
+nomad operator autopilot set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set Config options
+
+- `-cleanup-dead-servers` - Specifies whether to enable automatic removal of
+  dead servers upon the successful joining of new servers to the cluster. Must be
+  one of `[true|false]`.
+
+- `-last-contact-threshold` - Controls the maximum amount of time a server can
+  go without contact from the leader before being considered unhealthy. Must be a
+  duration value such as `200ms`.
+
+- `-max-trailing-logs` - Controls the maximum number of log entries that a
+  server can trail the leader by before being considered unhealthy.
+
+- `-server-stabilization-time` - Controls the minimum amount of time a server
+  must be stable in the 'healthy' state before being added to the cluster. Only
+  takes effect if all servers are running Raft protocol version 3 or higher. Must
+  be a duration value such as `10s`.
+
+- `-disable-upgrade-migration` - (Enterprise-only) Controls whether Nomad will
+  avoid promoting new servers until it can perform a migration. Must be one of
+  `[true|false]`.
+
+- `-redundancy-zone-tag`- (Enterprise-only) Controls the [`redundancy_zone`]
+  used for separating servers into different redundancy zones.
+
+- `-upgrade-version-tag` - (Enterprise-only) Controls the [`upgrade_version`] to
+  use for version info when performing upgrade migrations. If left blank, the
+  Nomad version will be used.
+
+The output looks like this:
+
+```plaintext
+Configuration updated!
+```
+
+The return code will indicate success or failure.
+
+[`redundancy_zone`]: /nomad/docs/configuration/server#redundancy_zone
+[`upgrade_version`]: /nomad/docs/configuration/server#upgrade_version
+[autopilot guide]: /nomad/tutorials/manage-clusters/autopilot
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/client-state.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/client-state.mdx
new file mode 100644
index 0000000000..81d89354c3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/client-state.mdx
@@ -0,0 +1,679 @@
+---
+layout: docs
+page_title: 'nomad operator client-state command reference'
+description: >
+  The `nomad operator client-state` command generates a representation of the
+  stored client state in JSON format.
+---
+
+# `nomad operator client-state` command reference
+
+The `operator client-state` command generates a representation of the
+stored client state in JSON format.
+
+## Usage
+
+```plaintext
+nomad operator client-state
+```
+
+## Example
+
+The output of this command can be piped to `jq` for further filtering and analysis:
+
+```shell-session
+$ nomad operator client-state | jq
+{
+  "Allocations": {
+    "3b0ed734-f721-45d3-420a-3d96926b3f1d": {
+      "Alloc": {
+        "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+        "Namespace": "default",
+        "EvalID": "042fbfeb-0c75-e696-b9b8-e3b4328a4988",
+        "Name": "docs.example[0]",
+        "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+        "NodeName": "YOUR_NOMAD_NAME_HERE",
+        "JobID": "docs",
+        "Job": {
+          "Stop": false,
+          "Region": "global",
+          "Namespace": "default",
+          "ID": "docs",
+          "ParentID": "",
+          "Name": "docs",
+          "Type": "service",
+          "Priority": 50,
+          "AllAtOnce": false,
+          "Datacenters": [
+            "dc1"
+          ],
+          "Constraints": null,
+          "Affinities": null,
+          "Spreads": null,
+          "TaskGroups": [
+            {
+              "Name": "example",
+              "Count": 1,
+              "Update": {
+                "Stagger": 30000000000,
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000,
+                "ProgressDeadline": 600000000000,
+                "AutoRevert": false,
+                "AutoPromote": false,
+                "Canary": 0
+              },
+              "Migrate": {
+                "MaxParallel": 1,
+                "HealthCheck": "checks",
+                "MinHealthyTime": 10000000000,
+                "HealthyDeadline": 300000000000
+              },
+              "Constraints": null,
+              "Scaling": null,
+              "RestartPolicy": {
+                "Attempts": 2,
+                "Interval": 1800000000000,
+                "Delay": 15000000000,
+                "Mode": "fail"
+              },
+              "Tasks": [
+                {
+                  "Name": "server",
+                  "Driver": "docker",
+                  "User": "",
+                  "Config": {
+                    "args": [
+                      "-listen",
+                      ":5678",
+                      "-text",
+                      "hello world"
+                    ],
+                    "image": "hashicorp/http-echo",
+                    "ports": [
+                      "http"
+                    ]
+                  },
+                  "Env": null,
+                  "Services": null,
+                  "Vault": null,
+                  "Templates": null,
+                  "Constraints": null,
+                  "Affinities": null,
+                  "Resources": {
+                    "CPU": 100,
+                    "Cores": 0,
+                    "MemoryMB": 300,
+                    "MemoryMaxMB": 0,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "RestartPolicy": {
+                    "Attempts": 2,
+                    "Interval": 1800000000000,
+                    "Delay": 15000000000,
+                    "Mode": "fail"
+                  },
+                  "DispatchPayload": null,
+                  "Lifecycle": null,
+                  "Meta": null,
+                  "KillTimeout": 5000000000,
+                  "LogConfig": {
+                    "MaxFiles": 10,
+                    "MaxFileSizeMB": 10
+                  },
+                  "Artifacts": null,
+                  "Leader": false,
+                  "ShutdownDelay": 0,
+                  "VolumeMounts": null,
+                  "ScalingPolicies": null,
+                  "KillSignal": "",
+                  "Kind": "",
+                  "CSIPluginConfig": null
+                }
+              ],
+              "EphemeralDisk": {
+                "Sticky": false,
+                "SizeMB": 300,
+                "Migrate": false
+              },
+              "Meta": null,
+              "ReschedulePolicy": {
+                "Attempts": 0,
+                "Interval": 0,
+                "Delay": 30000000000,
+                "DelayFunction": "exponential",
+                "MaxDelay": 3600000000000,
+                "Unlimited": true
+              },
+              "Affinities": null,
+              "Spreads": null,
+              "Networks": [
+                {
+                  "Mode": "",
+                  "Device": "",
+                  "CIDR": "",
+                  "IP": "",
+                  "MBits": 0,
+                  "DNS": null,
+                  "ReservedPorts": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostNetwork": "default"
+                    }
+                  ],
+                  "DynamicPorts": null
+                }
+              ],
+              "Consul": {
+                "Namespace": ""
+              },
+              "Services": null,
+              "Volumes": null,
+              "ShutdownDelay": null,
+              "StopAfterClientDisconnect": null,
+              "MaxClientDisconnect": null
+            }
+          ],
+          "Update": {
+            "Stagger": 30000000000,
+            "MaxParallel": 1,
+            "HealthCheck": "",
+            "MinHealthyTime": 0,
+            "HealthyDeadline": 0,
+            "ProgressDeadline": 0,
+            "AutoRevert": false,
+            "AutoPromote": false,
+            "Canary": 0
+          },
+          "Multiregion": null,
+          "Periodic": null,
+          "ParameterizedJob": null,
+          "Dispatched": false,
+          "DispatchIdempotencyToken": "",
+          "Payload": null,
+          "Meta": null,
+          "ConsulToken": "",
+          "ConsulNamespace": "",
+          "VaultToken": "",
+          "VaultNamespace": "",
+          "NomadTokenID": "",
+          "Status": "pending",
+          "StatusDescription": "",
+          "Stable": false,
+          "Version": 0,
+          "SubmitTime": 1670925631564348000,
+          "CreateIndex": 14,
+          "ModifyIndex": 14,
+          "JobModifyIndex": 14
+        },
+        "TaskGroup": "example",
+        "Resources": {
+          "CPU": 100,
+          "Cores": 0,
+          "MemoryMB": 300,
+          "MemoryMaxMB": 300,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "SharedResources": {
+          "CPU": 0,
+          "Cores": 0,
+          "MemoryMB": 0,
+          "MemoryMaxMB": 0,
+          "DiskMB": 300,
+          "IOPS": 0,
+          "Networks": [
+            {
+              "Mode": "",
+              "Device": "",
+              "CIDR": "",
+              "IP": "192.168.1.9",
+              "MBits": 0,
+              "DNS": null,
+              "ReservedPorts": [
+                {
+                  "Label": "http",
+                  "Value": 5678,
+                  "To": 0,
+                  "HostNetwork": "default"
+                }
+              ],
+              "DynamicPorts": null
+            }
+          ],
+          "Devices": null
+        },
+        "TaskResources": {
+          "server": {
+            "CPU": 100,
+            "Cores": 0,
+            "MemoryMB": 300,
+            "MemoryMaxMB": 0,
+            "DiskMB": 0,
+            "IOPS": 0,
+            "Networks": null,
+            "Devices": null
+          }
+        },
+        "AllocatedResources": {
+          "Tasks": {
+            "server": {
+              "Cpu": {
+                "CpuShares": 100,
+                "ReservedCores": null
+              },
+              "Memory": {
+                "MemoryMB": 300,
+                "MemoryMaxMB": 0
+              },
+              "Networks": null,
+              "Devices": null
+            }
+          },
+          "TaskLifecycles": {
+            "server": null
+          },
+          "Shared": {
+            "Networks": [
+              {
+                "Mode": "",
+                "Device": "",
+                "CIDR": "",
+                "IP": "192.168.1.9",
+                "MBits": 0,
+                "DNS": null,
+                "ReservedPorts": [
+                  {
+                    "Label": "http",
+                    "Value": 5678,
+                    "To": 0,
+                    "HostNetwork": "default"
+                  }
+                ],
+                "DynamicPorts": null
+              }
+            ],
+            "DiskMB": 300,
+            "Ports": [
+              {
+                "Label": "http",
+                "Value": 5678,
+                "To": 0,
+                "HostIP": "192.168.1.9"
+              }
+            ]
+          }
+        },
+        "Metrics": {
+          "NodesEvaluated": 1,
+          "NodesFiltered": 0,
+          "NodesAvailable": {
+            "dc1": 1
+          },
+          "ClassFiltered": null,
+          "ConstraintFiltered": null,
+          "NodesExhausted": 0,
+          "ClassExhausted": null,
+          "DimensionExhausted": null,
+          "QuotaExhausted": null,
+          "ResourcesExhausted": null,
+          "Scores": null,
+          "ScoreMetaData": [
+            {
+              "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+              "Scores": {
+                "binpack": 0.014787748194725047,
+                "job-anti-affinity": 0,
+                "node-affinity": 0,
+                "node-reschedule-penalty": 0
+              },
+              "NormScore": 0.014787748194725047
+            }
+          ],
+          "AllocationTime": 64877,
+          "CoalescedFailures": 0
+        },
+        "DesiredStatus": "run",
+        "DesiredDescription": "",
+        "DesiredTransition": {
+          "Migrate": null,
+          "Reschedule": null,
+          "ForceReschedule": null,
+          "NoShutdownDelay": null
+        },
+        "ClientStatus": "pending",
+        "ClientDescription": "",
+        "TaskStates": null,
+        "AllocStates": null,
+        "PreviousAllocation": "",
+        "NextAllocation": "",
+        "DeploymentID": "dc4c0c22-3bc7-a17a-5d7b-bce06a692293",
+        "DeploymentStatus": null,
+        "RescheduleTracker": null,
+        "NetworkStatus": null,
+        "FollowupEvalID": "",
+        "PreemptedAllocations": null,
+        "PreemptedByAllocation": "",
+        "SigningKeyID": "e596c865-adad-78cc-0266-94640594e5a2",
+        "CreateIndex": 15,
+        "ModifyIndex": 15,
+        "AllocModifyIndex": 15,
+        "CreateTime": 1670925631566156300,
+        "ModifyTime": 1670925631566156300
+      },
+      "DeployStatus": {
+        "Healthy": true,
+        "Timestamp": "2022-12-13T18:00:45.351354859+08:00",
+        "Canary": false,
+        "ModifyIndex": 0
+      },
+      "Tasks": {
+        "server": {
+          "LocalState": {
+            "Hooks": {
+              "artifacts": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "devices": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "dispatch_payload": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "identity": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "logmon": {
+                "PrestartDone": false,
+                "Data": {
+                  "reattach_config": "{\"Protocol\":\"grpc\",\"Network\":\"unix\",\"Addr\":\"/tmp/plugin2391577039\",\"Pid\":97576}"
+                },
+                "Env": null
+              },
+              "script_checks": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              },
+              "task_dir": {
+                "PrestartDone": false,
+                "Data": {
+                  "is_done": "true"
+                },
+                "Env": null
+              },
+              "validate": {
+                "PrestartDone": true,
+                "Data": null,
+                "Env": null
+              },
+              "volumes": {
+                "PrestartDone": false,
+                "Data": null,
+                "Env": null
+              }
+            },
+            "DriverNetwork": {
+              "PortMap": null,
+              "IP": "172.17.0.2",
+              "AutoAdvertise": false
+            },
+            "TaskHandle": {
+              "Version": 1,
+              "Config": {
+                "ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d/server/c7ffd87f",
+                "JobName": "docs",
+                "JobID": "docs",
+                "TaskGroupName": "example",
+                "Name": "server",
+                "Namespace": "default",
+                "NodeName": "YOUR_NOMAD_NAME_HERE",
+                "NodeID": "00d48d89-d512-3ee6-4b95-271b72415916",
+                "Env": {
+                  "NOMAD_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_ALLOC_DIR": "/alloc",
+                  "NOMAD_ALLOC_ID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                  "NOMAD_ALLOC_INDEX": "0",
+                  "NOMAD_ALLOC_NAME": "docs.example[0]",
+                  "NOMAD_ALLOC_PORT_http": "5678",
+                  "NOMAD_CPU_LIMIT": "100",
+                  "NOMAD_DC": "dc1",
+                  "NOMAD_GROUP_NAME": "example",
+                  "NOMAD_HOST_ADDR_http": "192.168.1.9:5678",
+                  "NOMAD_HOST_IP_http": "192.168.1.9",
+                  "NOMAD_HOST_PORT_http": "5678",
+                  "NOMAD_IP_http": "192.168.1.9",
+                  "NOMAD_JOB_ID": "docs",
+                  "NOMAD_JOB_NAME": "docs",
+                  "NOMAD_MEMORY_LIMIT": "300",
+                  "NOMAD_NAMESPACE": "default",
+                  "NOMAD_PARENT_CGROUP": "/nomad",
+                  "NOMAD_PORT_http": "5678",
+                  "NOMAD_REGION": "global",
+                  "NOMAD_SECRETS_DIR": "/secrets",
+                  "NOMAD_SHORT_ALLOC_ID": "3b0ed734",
+                  "NOMAD_TASK_DIR": "/local",
+                  "NOMAD_TASK_NAME": "server"
+                },
+                "DeviceEnv": {},
+                "Resources": {
+                  "NomadResources": {
+                    "Cpu": {
+                      "CpuShares": 100,
+                      "ReservedCores": null
+                    },
+                    "Memory": {
+                      "MemoryMB": 300,
+                      "MemoryMaxMB": 0
+                    },
+                    "Networks": null,
+                    "Devices": null
+                  },
+                  "LinuxResources": {
+                    "CPUPeriod": 0,
+                    "CPUQuota": 0,
+                    "CPUShares": 100,
+                    "MemoryLimitBytes": 314572800,
+                    "OOMScoreAdj": 0,
+                    "CpusetCpus": "",
+                    "CpusetCgroupPath": "",
+                    "PercentTicks": 0.0023148148148148147
+                  },
+                  "Ports": [
+                    {
+                      "Label": "http",
+                      "Value": 5678,
+                      "To": 0,
+                      "HostIP": "192.168.1.9"
+                    }
+                  ]
+                },
+                "Devices": null,
+                "Mounts": null,
+                "User": "",
+                "AllocDir": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "StdoutPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stdout.fifo",
+                "StderrPath": "/home/test/alloc/3b0ed734-f721-45d3-420a-3d96926b3f1d/alloc/logs/.server.stderr.fifo",
+                "AllocID": "3b0ed734-f721-45d3-420a-3d96926b3f1d",
+                "NetworkIsolation": null,
+                "DNS": null
+              },
+              "State": "",
+              "DriverState": "g6tDb250YWluZXJJRNoAQDdkNmQxMGVjZTY1YmQ2ZjY0MDk1YzdiMWI2NjViMzUyOTI1NDc5NmQ0YzE3ODY2YzdlNmE1ZTE2YWQ0NzI3YzitRHJpdmVyTmV0d29ya4OtQXV0b0FkdmVydGlzZcKiSVCqMTcyLjE3LjAuMqdQb3J0TWFwwK5SZWF0dGFjaENvbmZpZ4SkQWRkcrUvdG1wL3BsdWdpbjE4Mjc2MjczOTCnTmV0d29ya6R1bml4o1BpZNIAAX2qqFByb3RvY29spGdycGM="
+            },
+            "RunComplete": false
+          },
+          "RemoteState": {
+            "State": "running",
+            "Failed": false,
+            "Restarts": 0,
+            "LastRestart": "0001-01-01T00:00:00Z",
+            "StartedAt": "2022-12-13T10:00:35.350231151Z",
+            "FinishedAt": "0001-01-01T00:00:00Z",
+            "Events": [
+              {
+                "Type": "Received",
+                "Time": 1670925631571274800,
+                "Message": "",
+                "DisplayMessage": "Task received by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Task Setup",
+                "Time": 1670925631572548900,
+                "Message": "Building Task Directory",
+                "DisplayMessage": "Building Task Directory",
+                "Details": {
+                  "message": "Building Task Directory"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Driver",
+                "Time": 1670925631589523700,
+                "Message": "",
+                "DisplayMessage": "Downloading image",
+                "Details": {
+                  "image": "hashicorp/http-echo:latest"
+                },
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "Downloading image",
+                "GenericSource": ""
+              },
+              {
+                "Type": "Started",
+                "Time": 1670925635350228700,
+                "Message": "",
+                "DisplayMessage": "Task started by client",
+                "Details": {},
+                "FailsTask": false,
+                "RestartReason": "",
+                "SetupError": "",
+                "DriverError": "",
+                "ExitCode": 0,
+                "Signal": 0,
+                "KillTimeout": 0,
+                "KillError": "",
+                "KillReason": "",
+                "StartDelay": 0,
+                "DownloadError": "",
+                "ValidationError": "",
+                "DiskLimit": 0,
+                "FailedSibling": "",
+                "VaultError": "",
+                "TaskSignalReason": "",
+                "TaskSignal": "",
+                "DriverMessage": "",
+                "GenericSource": ""
+              }
+            ],
+            "TaskHandle": null
+          },
+          "DriverState": {
+            "ContainerID": "7d6d10ece65bd6f64095c7b1b665b3529254796d4c17866c7e6a5e16ad4727c8",
+            "DriverNetwork": {
+              "AutoAdvertise": false,
+              "IP": "172.17.0.2",
+              "PortMap": null
+            },
+            "ReattachConfig": {
+              "Addr": "/tmp/plugin1827627390",
+              "Network": "unix",
+              "Pid": 97706,
+              "Protocol": "grpc"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/debug.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/debug.mdx
new file mode 100644
index 0000000000..602bf401ff
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/debug.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: 'nomad operator debug command reference'
+description: |
+  The `nomad operator debug` command builds an archive containing Nomad cluster configuration and state information, Nomad server and client node logs, and pprof profiles from the selected servers and client nodes.
+---
+
+# `nomad operator debug` command reference
+
+The `operator debug` command builds an archive containing Nomad cluster
+configuration and state information, Nomad server and client node
+logs, and pprof profiles from the selected servers and client nodes.
+
+If no selection option is specified, the debug archive contains only
+cluster meta information.
+
+## Usage
+
+```plaintext
+nomad operator debug [options]
+```
+
+This command accepts comma separated `server-id` and `node-id` IDs for
+monitoring and pprof profiling. If IDs are provided, the command will
+monitor logs for the `duration`, saving a snapshot of Nomad state
+every `interval`. Captured logs and configurations are subjected to
+redaction, but may still contain sensitive information and the archive
+contents should be reviewed before sharing.
+
+If an `output` path is provided, `debug` will create a timestamped
+directory in that path instead of an archive. By default, the command
+creates a compressed tar archive in the current directory.
+
+Consul and Vault status and version information are included if
+configured.
+
+If ACLs are enabled, this command will require a token with the 'node:read'
+capability to run. In order to collect information, the token will also
+require the 'agent:read' and 'operator:read' capabilities, as well as the
+'list-jobs' capability for all namespaces. To collect pprof profiles the
+token will also require 'agent:write', or enable_debug configuration set to
+true.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Debug options
+
+- `-duration=5m`: Set the duration of the debug capture. Logs will be captured from
+  specified servers and nodes at `log-level`. Defaults to `5m`.
+
+- `-interval=30s`: The interval between snapshots of the Nomad state.
+  If unspecified, only one snapshot is captured. Defaults to `30s`.
+
+- `-log-level=TRACE`: The log level to monitor. Defaults to `TRACE`.
+
+- `-log-include-location`: Include file and line information in each log line
+  monitored. The default is `true`.
+
+- `-max-nodes=<count>`: Cap the maximum number of client nodes included
+  in the capture. Defaults to 10, set to 0 for unlimited.
+
+- `-node-class=<node-class>`: Filter client nodes based on node class.
+
+- `-node-id=<node1>,<node2>`: Comma separated list of Nomad client node ids
+  to monitor for logs, API outputs, and pprof profiles. Accepts id prefixes, and
+  "all" to select all nodes (up to count = max-nodes). Defaults to `all`.
+
+- `-pprof-duration=<duration>`: Duration for pprof
+  collection. Defaults to 1s or `-duration`, whichever is less.
+
+- `-pprof-interval=30s`: The interval between pprof collections. Set interval
+    equal to pprof duration to capture a single snapshot. Defaults to 30s or
+    `-pprof-duration`, whichever is more.
+
+- `-server-id=<server1>,<server2>`: Comma separated list of Nomad server names to
+  monitor for logs, API outputs, and pprof profiles. Accepts server names, "leader", or
+  "all". Defaults to `all`.
+
+- `-stale=<true|false>`: If "false", the default, get membership data from the
+  cluster leader. If the cluster is in an outage unable to establish
+  leadership, it may be necessary to get the configuration from a non-leader
+  server.
+
+- `-event-topic=<allocation,evaluation,job,node,*>:<filter>`: Enable event
+  stream capture. Filter by comma delimited list of topic filters or "all".
+  Defaults to "none" (disabled).  Refer to the [Events API](/nomad/api-docs/events) for
+  additional detail.
+
+- `-verbose`: Enable verbose output
+
+- `-output=path`: Path to the parent directory of the output
+  directory. Defaults to the current directory. If specified, no
+  archive is built.
+
+- `-consul-http-addr=<addr>`: The address and port of the Consul HTTP
+  agent. Overrides the `CONSUL_HTTP_ADDR` environment variable.
+
+- `-consul-token=<token>`: Token used to query Consul. Overrides the
+  `CONSUL_HTTP_TOKEN` environment variable and the Consul token
+  file.
+
+- `-consul-token-file=<path>`: Path to the Consul token file. Overrides the `CONSUL_HTTP_TOKEN_FILE`
+  environment variable.
+
+- `-consul-client-cert=<path>`: Path to the Consul client cert file. Overrides the `CONSUL_CLIENT_CERT`
+  environment variable.
+
+- `-consul-client-key=<path>`: Path to the Consul client key file. Overrides the `CONSUL_CLIENT_KEY`
+  environment variable.
+
+- `-consul-ca-cert=<path>`: Path to a CA file to use with Consul. Overrides the `CONSUL_CACERT`
+  environment variable and the Consul CA path.
+
+- `-consul-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Consul
+  certificate. Overrides the `CONSUL_CAPATH` environment variable.
+
+- `-vault-address=<addr>`: The address and port of the Vault HTTP agent. Overrides the `VAULT_ADDR`
+  environment variable.
+
+- `-vault-token=<token>`: Token used to query Vault. Overrides the `VAULT_TOKEN` environment
+  variable.
+
+- `-vault-client-cert=<path>`: Path to the Vault client cert file. Overrides the `VAULT_CLIENT_CERT`
+  environment variable.
+
+- `-vault-client-key=<path>`: Path to the Vault client key file. Overrides the `VAULT_CLIENT_KEY`
+  environment variable.
+
+- `-vault-ca-cert=<path>`: Path to a CA file to use with Vault. Overrides the `VAULT_CACERT`
+  environment variable and the Vault CA path.
+
+- `-vault-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify the Vault
+  certificate. Overrides the `VAULT_CAPATH` environment variable.
+
+## Output
+
+This command prints a summary of the capture and the name of the timestamped
+archive file produced.
+
+## Examples
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id b5,20
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (2/3) [b547cd3a-085f-68c2-55f4-e99beebb0433 20c0964b-72cc-4083-87fe-ec6905b6230a]
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034455Z.tar.gz
+```
+
+```shell-session
+$ nomad operator debug -duration 5s -interval 5s -server-id all -node-id all -max-nodes=1
+Starting debugger...
+
+          Servers: (3/3) [server1.global server2.global server3.global]
+          Clients: (1/3) [b547cd3a-085f-68c2-55f4-e99beebb0433]
+                   Max node count reached (1)
+         Interval: 5s
+         Duration: 5s
+
+Capturing cluster data...
+    Capture interval 0000
+    Capture interval 0001
+    Capture interval 0002
+    Capture interval 0003
+Created debug archive: nomad-debug-2020-12-08-034113Z.tar.gz
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-generate.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-generate.mdx
new file mode 100644
index 0000000000..bf07092f64
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-generate.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring generate command reference'
+description: >
+  The `nomad operator gossip keyring generate` command generates an encryption key that can be used for
+  Nomad server's gossip traffic encryption. The keygen command uses a
+  cryptographically strong pseudo-random number generator to generate the key.
+---
+
+# nomad operator gossip keyring generate reference
+
+The `operator gossip keyring generate` command generates an encryption
+key that can be used for Nomad server's gossip traffic encryption. The
+keygen command uses a cryptographically strong pseudo-random number
+generator to generate the key.
+
+The resulting key is encoded in the [RFC4648] "URL and filename safe"
+base64 alphabet. If you use another tool such as OpenSSL to generate
+the gossip key, you should pipe the input through the `base64(1)`
+command to ensure it is safely encoded. For example: `openssl rand 32
+| base64`
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring generate
+```
+
+## Example
+
+```shell-session
+$ nomad operator gossip keyring generate
+6RhfKFZ5uYEaU6RgWzx69ssLcpiIkvnEZs5KBOQxvxA=
+```
+
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-install.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-install.mdx
new file mode 100644
index 0000000000..b1591dbd81
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-install.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring install command reference'
+description: |
+  The `nomad operator gossip keyring install` command installs a new gossip encryption key.
+---
+
+# `nomad operator gossip keyring install` command reference
+
+The `operator gossip keyring install` command is used to install a new
+encryption key used for gossip. This will broadcast the new key to all
+members in the cluster.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring install [options] <key>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring install AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Installing new gossip encryption key...
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-list.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-list.mdx
new file mode 100644
index 0000000000..95adf42733
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring list command reference'
+description: |
+  The `nomad operator gossip keyring list` command displays all gossip keys currently in use within the cluster.
+---
+
+# `nomad operator gossip keyring list` command reference
+
+The `operator gossip keyring list` command lists all gossip keys
+currently in use within the cluster.
+
+This command can only be run against server nodes. It returns 0 if all
+nodes reply and there are no errors. If any node fails to reply or
+reports failure, the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the
+`agent:write` capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring list [options]
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+The output of the `nomad operator gossip keyring list` command
+consolidates information from all the Nomad servers.
+
+```shell-session
+$ nomad operator gossip keyring list
+Gathering installed encryption keys...
+Key
+HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-remove.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-remove.mdx
new file mode 100644
index 0000000000..f8030dbfa2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring remove command reference'
+description: |
+  The `nomad operator gossip keyring remove` command removes the specified, non-primary gossip encryption key from the cluster.
+---
+
+# `nomad operator gossip keyring remove` command reference
+
+The `operator gossip keyring remove` command removes the given key
+from the cluster. This operation may only be performed on keys which
+are not currently the primary key.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring remove [options] <key>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring remove HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Removing gossip encryption key...
+error: Unexpected response code: 500 (3/3 nodes reported failure)
+
+$ nomad operator gossip keyring remove AOUfjGff+MrTBzNU7NCOTmYajKRkGv8r2ToxheWd+jk=
+Removing gossip encryption key...
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-use.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-use.mdx
new file mode 100644
index 0000000000..0fb4172b76
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/gossip/keyring-use.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator gossip keyring use command reference'
+description: |
+  The `nomad operator gossip keyring use` command changes the encryption key that Nomad uses for gossip.
+---
+
+# `nomad operator gossip keyring use` command reference
+
+The `operator gossip keyring use` command changes the encryption key
+used for gossip. The key must already be installed before this
+operation can succeed.
+
+This command can only be run against server nodes. It returns 0 if all nodes
+reply and there are no errors. If any node fails to reply or reports failure,
+the exit code will be 1.
+
+If ACLs are enabled, this command requires a token with the `agent:write`
+capability.
+
+## Usage
+
+```plaintext
+nomad operator gossip keyring use [options] <key>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+```shell-session
+$ nomad operator gossip keyring use HD5Y61iE+neTxd1n6TnXhCPViPIUq5QpWq8WW8012XA=
+Changing primary gossip encryption key...
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/index.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/index.mdx
new file mode 100644
index 0000000000..2ac15f39d6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/index.mdx
@@ -0,0 +1,91 @@
+---
+layout: docs
+page_title: 'nomad operator command reference'
+description: |
+  The `nomad operator` command provides cluster-level tools for Nomad operators.
+---
+
+# `nomad operator` command reference
+
+The `operator` command provides cluster-level tools for Nomad operators, such
+as interacting with the Raft subsystem.
+
+~> Use this command with extreme caution, as improper use could lead to a Nomad
+outage and even loss of data.
+
+See the [Outage Recovery guide] guide for some examples of how this command is
+used. For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+Usage: `nomad operator <subcommand> <subcommand> [options]`
+
+Run `nomad operator <subcommand>` with no arguments for help on that subcommand.
+The following subcommands are available:
+
+- [`operator autopilot get-config`][get-config] - Display the current Autopilot
+  configuration
+
+- [`operator autopilot set-config`][set-config] - Modify the current Autopilot
+  configuration
+
+- [`operator debug`][debug] - Build an archive of debug data
+
+- [`operator gossip keyring generate`][gossip_keyring_generate] - Generates a gossip encryption key
+
+- [`operator gossip keyring install`][gossip_keyring_install] - Install a gossip encryption key
+
+- [`operator gossip keyring list`][gossip_keyring_list] - List available gossip encryption keys
+
+- [`operator gossip keyring remove`][gossip_keyring_remove] - Deletes a gossip encryption key
+
+- [`operator gossip keyring use`][gossip_keyring_use] - Sets a gossip encryption key as the active key
+
+- [`operator raft list-peers`][list] - Display the current Raft peer
+  configuration
+
+- [`operator raft remove-peer`][remove] - Remove a Nomad server from the Raft
+  configuration
+
+- [`operator root keyring list`][root_keyring_list] - List available root encryption keys
+
+- [`operator root keyring remove`][root_keyring_remove] - Deletes a root encryption key
+
+- [`operator root keyring rotate`][root_keyring_rotate] - Rotates the root encryption key
+
+- [`operator scheduler get-config`][scheduler-get-config] - Display the current
+  scheduler configuration
+
+- [`operator scheduler set-config`][scheduler-set-config] - Modify the scheduler
+  configuration
+
+- [`operator snapshot agent`][snapshot-agent] <EnterpriseAlert inline /> - Inspects a snapshot of the Nomad server state
+
+- [`operator snapshot save`][snapshot-save] - Saves a snapshot of the Nomad server state
+
+- [`operator snapshot restore`][snapshot-restore] - Restores a snapshot of the Nomad server state
+
+- [`operator snapshot inspect`][snapshot-inspect] - Inspects a snapshot of the Nomad server state
+
+[debug]: /nomad/docs/commands/operator/debug 'Builds an archive of configuration and state'
+[get-config]: /nomad/docs/commands/operator/autopilot/get-config 'Autopilot Get Config command'
+[gossip_keyring_generate]: /nomad/docs/commands/operator/gossip/keyring-generate 'Generates a gossip encryption key'
+[gossip_keyring_install]: /nomad/docs/commands/operator/gossip/keyring-install 'Install a gossip encryption key'
+[gossip_keyring_list]: /nomad/docs/commands/operator/gossip/keyring-list 'List available gossip encryption keys'
+[gossip_keyring_remove]: /nomad/docs/commands/operator/gossip/keyring-remove 'Deletes a gossip encryption key'
+[gossip_keyring_use]: /nomad/docs/commands/operator/gossip/keyring-use 'Sets a gossip encryption key as the active key'
+[list]: /nomad/docs/commands/operator/raft/list-peers 'Raft List Peers command'
+[operator]: /nomad/api-docs/operator 'Operator API documentation'
+[outage recovery guide]: /nomad/tutorials/manage-clusters/outage-recovery
+[remove]: /nomad/docs/commands/operator/raft/remove-peer 'Raft Remove Peer command'
+[root_keyring_list]: /nomad/docs/commands/operator/root/keyring-list 'List available root encryption keys'
+[root_keyring_remove]: /nomad/docs/commands/operator/root/keyring-remove 'Deletes a root encryption key'
+[root_keyring_rotate]: /nomad/docs/commands/operator/root/keyring-rotate 'Rotates the root encryption key'
+[set-config]: /nomad/docs/commands/operator/autopilot/set-config 'Autopilot Set Config command'
+[snapshot-save]: /nomad/docs/commands/operator/snapshot/save 'Snapshot Save command'
+[snapshot-restore]: /nomad/docs/commands/operator/snapshot/restore 'Snapshot Restore command'
+[snapshot-inspect]: /nomad/docs/commands/operator/snapshot/inspect 'Snapshot Inspect command'
+[snapshot-agent]: /nomad/docs/commands/operator/snapshot/agent 'Snapshot Agent command'
+[scheduler-get-config]: /nomad/docs/commands/operator/scheduler/get-config 'Scheduler Get Config command'
+[scheduler-set-config]: /nomad/docs/commands/operator/scheduler/set-config 'Scheduler Set Config command'
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/metrics.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/metrics.mdx
new file mode 100644
index 0000000000..887024b58c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/metrics.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'nomad operator metrics command reference'
+description: |-
+  The `nomad operator metrics` command queries the metrics API
+  endpoint for metrics data related to the current Nomad
+  process.
+---
+
+# `nomad operator metrics` command reference
+
+The `operator metrics` command queries the [metrics API endpoint](/nomad/api-docs/metrics).
+
+## Usage
+
+```plaintext
+nomad operator metrics [options]
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Metrics Specific options
+
+- `-pretty`: Pretty prints the JSON output
+- `-format <format>`: Specify output format (`prometheus`)
+- `-json`: Output the allocation in its JSON format.
+- `-t`: Format and display allocation using a Go template.
+
+## Output
+
+The output of `nomad operator metrics` is a JSON representation of the
+[metrics API endpoint](/nomad/api-docs/metrics).
+
+```shell-session
+$ nomad operator metrics -pretty
+{
+  "Counters": [
+    {
+      "Count": 11,
+      "Labels": {},
+      "Max": 1.0,
+      "Mean": 1.0,
+      "Min": 1.0,
+      "Name": "nomad.nomad.rpc.query",
+      "Stddev": 0.0,
+      "Sum": 11.0
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f",
+        "datacenter": "dc1"
+      },
+      "Name": "nomad.client.allocations.blocked",
+      "Value": 0.0
+    },
+    {
+      "Labels": {
+        "datacenter": "dc1",
+        "node_id": "cd7c3e0c-0174-29dd-17ba-ea4609e0fd1f"
+      },
+      "Name": "nomad.client.allocations.migrating",
+      "Value": 0.0
+    }
+  ],
+  "Samples": [
+    {
+      "Count": 20,
+      "Labels": {},
+      "Max": 0.03544100001454353,
+      "Mean": 0.023678050097078084,
+      "Min": 0.00956599973142147,
+      "Name": "nomad.memberlist.gossip",
+      "Stddev": 0.005445327799243976,
+      "Sum": 0.4735610019415617
+    },
+    {
+      "Count": 1,
+      "Labels": {},
+      "Max": 0.0964059978723526,
+      "Mean": 0.0964059978723526,
+      "Min": 0.0964059978723526,
+      "Name": "nomad.nomad.client.update_status",
+      "Stddev": 0.0,
+      "Sum": 0.0964059978723526
+    }
+  ]
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/info.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/info.mdx
new file mode 100644
index 0000000000..10ee200c77
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/info.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad operator raft info command reference'
+description: |
+  The `nomad operator raft info` command displays summary information about the Raft logs persisted in the Nomad data directory.
+---
+
+# `nomad operator raft info` command reference
+
+The `raft info` command is used to display summary information about the
+raft logs persisted in the Nomad [data directory].
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft info <path to data dir>
+```
+
+## Examples
+
+An example output is as follows:
+
+```shell-session
+$ sudo nomad operator raft info /var/nomad/data
+path:        /var/nomad/data/server/raft/raft.db
+length:      10
+first index: 1
+last index:  10
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/list-peers.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/list-peers.mdx
new file mode 100644
index 0000000000..26b9f81859
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/list-peers.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'nomad operator raft list-peers command reference'
+description: |
+  The `nomad operator raft list-peers` command displays the current Raft peer configuration.
+---
+
+# `nomad operator raft list-peers` command reference
+
+The `raft list-peers` command is used to display the current Raft peer
+configuration.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft list-peers [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## List Peers options
+
+- `-stale`: The stale argument defaults to "false" which means the leader
+  provides the result. If the cluster is in an outage state without a leader, you
+  may need to set `-stale` to "true" to get the configuration from a non-leader
+  server.
+
+## Examples
+
+An example output with three servers is as follows:
+
+```shell-session
+$ nomad operator raft list-peers
+Node                   ID               Address          State     Voter
+nomad-server01.global  10.10.11.5:4647  10.10.11.5:4647  follower  true
+nomad-server02.global  10.10.11.6:4647  10.10.11.6:4647  leader    true
+nomad-server03.global  10.10.11.7:4647  10.10.11.7:4647  follower  true
+```
+
+- `Node` is the node name of the server, as known to Nomad, or "(unknown)" if
+  the node is stale and not known.
+
+- `ID` is the ID of the server. This is the same as the `Address` but may be
+  upgraded to a GUID in a future version of Nomad.
+
+- `Address` is the IP:port for the server.
+
+- `State` is either "follower" or "leader" depending on the server's role in the
+  Raft configuration.
+
+- `Voter` is "true" or "false", indicating if the server has a vote in the Raft
+  configuration. Future versions of Nomad may add support for non-voting servers.
+
+[operator]: /nomad/api-docs/operator
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/logs.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/logs.mdx
new file mode 100644
index 0000000000..a5cc23391b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/logs.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad operator raft logs command reference'
+description: |
+  The `nomad operator raft logs` command displays the log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft logs` command reference
+
+The `raft logs` command is used to display the log entries persisted in
+the Nomad [data directory] in JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft logs [options] <path to data dir>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft logs /var/nomad/data > ~/raft-logs.json
+$ jq . < ~/raft-logs.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/remove-peer.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/remove-peer.mdx
new file mode 100644
index 0000000000..9c0121ff0b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/remove-peer.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator raft remove-peer command reference'
+description: |
+  The `nomad operator raft remove-peer` command removes a Nomad server from the Raft configuration.
+---
+
+# `nomad operator raft remove-peer` command reference
+
+Remove the Nomad server with given address from the Raft configuration.
+
+There are rare cases where a peer may be left behind in the Raft quorum even
+though the server is no longer present and known to the cluster. This command
+can be used to remove the failed server so that it is no longer affects the Raft
+quorum. If the server still shows in the output of the [`nomad server members`]
+command, it is preferable to clean up by running [`nomad server force-leave`]
+instead of this command.
+
+See the [Outage Recovery] guide for some examples of how this command is used.
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft remove-peer [options]
+```
+
+If ACLs are enabled, this command requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Remove Peer options
+
+- `-peer-address`: Remove a Nomad server with given address from the Raft
+  configuration. The format is "IP:port"
+
+- `-peer-id`: Remove a Nomad server with the given ID from the Raft
+  configuration. The format is "id"
+
+[`nomad server force-leave`]: /nomad/docs/commands/server/force-leave 'Nomad server force-leave command'
+[`nomad server members`]: /nomad/docs/commands/server/members 'Nomad server members command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/state.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/state.mdx
new file mode 100644
index 0000000000..2b4503b98a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/state.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad operator raft state command reference'
+description: |
+  The `nomad operator raft state` command displays Raft server state obtained by replaying Raft log entries persisted in the Nomad data directory.
+---
+
+# `nomad operator raft state` command reference
+
+The `raft state` command is used to display the server state obtained by
+replaying raft log entries persisted in the Nomad [data directory] in
+JSON format.
+
+This command requires file system permissions to access the data
+directory on disk. The Nomad server locks access to the data
+directory, so this command cannot be run on a data directory that is
+being used by a running Nomad server.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator raft state [options] <path to data dir>
+```
+
+## Raft State options
+
+- `-last-index=<last_index>`: Set the last log index to be applied, to
+  drop spurious log entries not properly committed. If the
+  `last_index` option is zero or negative, it's treated as an offset
+  from the last index seen in raft.
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ sudo nomad operator raft state /var/nomad/data > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
+
+[data directory]: /nomad/docs/configuration#data_dir
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/raft/transfer-leadership.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/raft/transfer-leadership.mdx
new file mode 100644
index 0000000000..2d2adf0801
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/raft/transfer-leadership.mdx
@@ -0,0 +1,57 @@
+---
+layout: docs
+page_title: 'nomad operator raft transfer-leadership command reference'
+description: |
+  The `nomad operator raft transfer-leadership` command transfers leadership to a specific Nomad server.
+---
+
+# `nomad operator raft transfer-leadership` command reference
+
+Transfer leadership from the current leader to the given server member.
+
+While performing a [rolling upgrade][] of your Nomad cluster, it might be
+advisable to transfer leadership to a specific node in the cluster. For example,
+setting the leader to the first upgraded server in the cluster can prevent
+leadership churn as you upgrade the remaining server nodes.
+
+The target server's ID or address:port are required and can be obtained by
+running the [`nomad operator raft list-peers`][] command or by calling the
+[Read Raft Configuration][] API endpoint.
+
+For an API to perform these operations programmatically, please see the
+documentation for the [Operator][] endpoint.
+
+## Usage
+
+```plaintext
+nomad operator raft transfer-leadership [options]
+```
+
+<Tip title="Required Permissions">
+If ACLs are enabled, this command requires a management token.
+</Tip>
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Transfer Leadership options
+
+- `-peer-address`: Specifies the Raft **Address** of the target server as
+  provided in the output of the [`nomad operator raft list-peers`][] command or
+  the [Read Raft Configuration] API endpoint.
+
+- `-peer-id`: Specifies the Raft **ID** of the target server as provided in the
+  output of the [`nomad operator raft list-peers`][] command or the
+  [Read Raft Configuration] API endpoint.
+
+  <Note>
+
+  Either `-peer-address` or `-peer-id` must be provided, but not both.
+
+  </Note>
+
+[`nomad operator raft list-peers`]: /nomad/docs/commands/operator/raft/list-peers 'Nomad operator raft list-peers command'
+[operator]: /nomad/api-docs/operator 'Nomad Operator API'
+[rolling upgrade]: /nomad/docs/upgrade#upgrade-process
+[Read Raft Configuration]: /nomad/api-docs/operator/raft#read-raft-configuration
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-list.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-list.mdx
new file mode 100644
index 0000000000..0fe5576352
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-list.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring list command reference'
+description: |
+  The `nomad operator root keyring list` command displays encryption key metadata for installed keys. This command does not display sensitive key material.
+---
+
+# `nomad operator root keyring list` command reference
+
+The `operator root keyring list` command lists the currently installed
+keys. This list returns key metadata and not sensitive key material.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring list [options]
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring list
+Key       State     Create Time
+33374156  active    2022-07-11T19:11:07Z
+8d87a371  inactive  2022-07-11T19:10:37Z
+
+$ nomad operator root keyring list -verbose
+Key                                   State     Create Time
+33374156-9f81-b14c-83d4-a2f1f87dbf99  active    2022-07-11T19:11:07Z
+8d87a371-3594-e1e4-8ae1-3980122b0f25  inactive  2022-07-11T19:10:37Z
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-remove.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-remove.mdx
new file mode 100644
index 0000000000..d1a5703712
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-remove.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring remove command reference'
+description: |
+  The `nomad operator root keyring remove` command removes an unused encryption key from the cluster.
+---
+
+# `nomad operator root keyring remove` command reference
+
+The `operator root keyring remove` command removes an encryption key from the
+cluster. This operation may only be performed on keys that are not the active
+key.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring remove [options] <key ID>
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## Remove options
+
+- `-force`: Remove the key even if it was used to sign an existing variable
+or workload identity.
+
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring remove 48596ce5-3ff5-8f77-2dcf-301682ada0ce
+error: Unexpected response code: 500 (active root key cannot be deleted - call rotate first)
+
+$ nomad operator root keyring remove 33374156-9f81-b14c-83d4-a2f1f87dbf99
+Removed encryption key 33374156-9f81-b14c-83d4-a2f1f87dbf99
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-rotate.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-rotate.mdx
new file mode 100644
index 0000000000..6064c7a8c1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/root/keyring-rotate.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad operator root keyring rotate command reference'
+description: |
+  The `nomad operator root keyring rotate` command rotates the encryption key by generating a new encryption key for all future variables.
+---
+
+# `nomad operator root keyring rotate` command reference
+
+The `operator root keyring rotate` command generates a new encryption key for
+all future variables.
+
+If ACLs are enabled, this command requires a management token.
+
+## Usage
+
+```plaintext
+nomad operator root keyring rotate [options]
+```
+
+## General options
+
+@include 'general_options.mdx'
+
+## Rotate options
+
+- `-full`: Decrypt all existing variables and re-encrypt with the new key. This
+  command will immediately return and the re-encryption process will run
+  asynchronously on the leader.
+
+- `-now`: Publish the new key immediately without prepublishing. One of `-now`
+  or `-prepublish` must be set.
+
+- `-prepublish`: Set a duration for which to prepublish the new key
+  (ex. "1h"). The currently active key will be unchanged but the new public key
+  will be available in the JWKS endpoint. Multiple keys can be prepublished and
+  they will be promoted to active in order of publish time, at most once every
+  [`root_key_gc_interval`][]. One of `-now` or `-prepublish` must be set.
+
+- `-verbose`: Enable verbose output
+
+## Examples
+
+```shell-session
+$ nomad operator root keyring rotate -now
+Key       State   Create Time           Publish Time
+f19f6029  active  2022-07-11T19:14:36Z  <none>
+
+$ nomad operator root keyring rotate -now -verbose
+Key                                   State   Create Time           Publish Time
+53186ac1-9002-c4b6-216d-bb19fd37a791  active  2022-07-11T19:14:47Z  <none>
+
+$ nomad operator root keyring rotate -prepublish 1h
+Key       State   Create Time           Publish Time
+7f15e4e9  active  2022-07-11T19:15:10Z  2022-07-11T20:15:10Z
+```
+
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/get-config.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/get-config.mdx
new file mode 100644
index 0000000000..20e287ac34
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/get-config.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler get-config command reference'
+description: |
+  The `nomad operator scheduler get-config` command displays the current scheduler configuration.
+---
+
+# `nomad operator scheduler get-config` command reference
+
+The scheduler operator get-config command is used to view the current scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler get-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Get Config options
+
+- `-json`: Output the scheduler config in its JSON format.
+
+- `-t`: Format and display the scheduler config using a Go template.
+
+## Examples
+
+Display the current scheduler configuration:
+
+```shell-session
+$ nomad operator scheduler get-config
+Scheduler Algorithm           = binpack
+Memory Oversubscription       = false
+Reject Job Registration       = false
+Pause Eval Broker             = false
+Preemption System Scheduler   = true
+Preemption Service Scheduler  = false
+Preemption Batch Scheduler    = false
+Preemption SysBatch Scheduler = false
+Modify Index                  = 5
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/set-config.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/set-config.mdx
new file mode 100644
index 0000000000..8200fb19be
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/scheduler/set-config.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: 'nomad operator scheduler set-config command reference'
+description: |
+  The `nomad operator scheduler set-config` command modifies the scheduler configuration. Set binpack or spread allocation. Enable or disable preemption for batch, service, sysbatch, and system jobs.
+---
+
+# `nomad operator scheduler set-config` command reference
+
+The scheduler operator set-config command is used to modify the scheduler
+configuration.
+
+## Usage
+
+```plaintext
+nomad operator scheduler set-config [options]
+```
+
+If ACLs are enabled, this command requires a token with the `operator:write`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Set config options
+
+- `-check-index` - If set, the scheduler config is only updated if the passed
+  modify index matches the current server side version. If a non-zero value is
+  passed, it ensures that the scheduler config is being updated from a known
+  state.
+
+- `-scheduler-algorithm` - Specifies whether scheduler binpacks or spreads
+  allocations on available nodes. Must be one of `["binpack"|"spread"]`.
+
+- `-memory-oversubscription` - When true, tasks may exceed their reserved memory
+  limit, if the client has excess memory capacity. Tasks must specify [`memory_max`]
+  to take advantage of memory oversubscription. Must be one of `[true|false]`.
+
+- `-reject-job-registration` - When true, the server will return permission denied
+  errors for job registration, job dispatch, and job scale APIs, unless the ACL
+  token for the request is a management token. If ACLs are disabled, no user
+  will be able to register jobs. This allows operators to shed load from automated
+  processes during incident response. Must be one of `[true|false]`.
+
+- `-pause-eval-broker` - When set to true, the eval broker which usually runs on
+  the leader will be disabled. This will prevent the scheduler workers from
+  receiving new work. Must be one of `[true|false]`.
+
+- `-preempt-batch-scheduler` - Specifies whether preemption for batch jobs
+  is enabled. Note that if this is set to true, then batch jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-service-scheduler` - Specifies whether preemption for service jobs
+  is enabled. Note that if this is set to true, then service jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+- `-preempt-sysbatch-scheduler` - Specifies whether preemption for system batch
+  jobs is enabled. Note that if this is set to true, then system batch jobs can
+  preempt any other jobs. Must be one of `[true|false]`.
+
+- `-preempt-system-scheduler` - Specifies whether preemption for system jobs
+  is enabled. Note that if this is set to true, then system jobs can preempt any
+  other jobs. Must be one of `[true|false]`.
+
+## Examples
+
+Modify the scheduler algorithm to spread:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread
+Scheduler configuration updated!
+```
+
+Modify the scheduler algorithm to spread using the check index flag:
+
+```shell-session
+$ nomad operator scheduler set-config -scheduler-algorithm=spread -check-index=5
+Scheduler configuration updated!
+```
+
+[`memory_max`]: /nomad/docs/job-specification/resources#memory_max
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/agent.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/agent.mdx
new file mode 100644
index 0000000000..1dcdc32be5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/agent.mdx
@@ -0,0 +1,168 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot agent command reference'
+description: |
+  The `nomad operator snapshot agent` command takes snapshots of the state of the Nomad servers and saves them locally or pushes them to an optional remote storage service.
+---
+
+# `nomad operator snapshot agent` command reference
+
+<EnterpriseAlert />
+
+The snapshot agent takes snapshots of the state of the nomad servers and
+saves them locally, or pushes them to an optional remote storage service.
+
+The agent can be run as a long-running daemon process or in a one-shot mode
+from a batch job. As a long-running daemon, the agent will perform a leader
+election so multiple processes can be run in a highly available fashion with
+automatic failover. In daemon mode, the agent will also register itself with
+Consul as a service, along with health checks that show the agent is alive
+and able to take snapshots.
+
+<Warning>
+
+This snapshot agent only saves a Raft snapshot. Key material for the Nomad
+keyring is stored on disk and must be saved separately. To use a snapshot saved
+by the agent to recover a cluster, you will also need to [restore the keyring][]
+onto at least one server.
+
+</Warning>
+
+If ACLs are enabled, a management token must be supplied in order to perform
+snapshot operations.
+
+The Config file has the following format (shown populated with default values):
+
+```hcl
+nomad {
+  address         = "http://127.0.0.1:4646"
+  token           = ""
+  region          = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+
+snapshot {
+  interval         = "1h"
+  retain           = 30
+  stale            = false
+  service          = "nomad-snapshot"
+  deregister_after = "72h"
+  lock_key         = "nomad-snapshot/lock"
+  max_failures     = 3
+  prefix           = "nomad"
+}
+
+log {
+  level           = "INFO"
+  enable_syslog   = false
+  syslog_facility = "LOCAL0"
+}
+
+consul {
+  enabled         = true
+  http_addr       = "127.0.0.1:8500"
+  token           = ""
+  datacenter      = ""
+  ca_file         = ""
+  ca_path         = ""
+  cert_file       = ""
+  key_file        = ""
+  tls_server_name = ""
+}
+
+# one storage block is required
+
+local_storage {
+  path = "."
+}
+
+aws_storage {
+  access_key_id     = ""
+  secret_access_key = ""
+  s3_region         = ""
+  s3_endpoint       = ""
+  s3_bucket         = ""
+  s3_key_prefix     = "nomad-snapshot"
+}
+
+azure_blob_storage {
+  account_name   = ""
+  account_key    = ""
+  container_name = ""
+}
+
+google_storage {
+  bucket = ""
+}
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot agent [options] <config_file>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot agent options
+
+### Snapshot options
+
+- `-interval`: Interval at which to perform snapshots as a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, the agent will take a single snapshot and then exit, which is useful for running snapshots via batch jobs. Defaults to "1h".
+- `-lock-key`: A prefix in Consul's key-value store used to coordinate between different instances of the snapshot agent in order to only have one active instance at a time. For highly available operation of the snapshot agent, simply run multiple instances. All instances must be configured with the same lock key in order to properly coordinate. Defaults to "nomad-snapshot/lock".
+- `-max-failures`: Number of snapshot failures after which the snapshot agent will give up leadership. In a highly available operation with multiple snapshot agents available, this gives another agent a chance to take over if an agent is experiencing issues, such as running out of disk space for snapshots. Defaults to 3.
+- `-retain`: Number of snapshots to retain. After each snapshot is taken, the oldest snapshots will start to be deleted in order to retain at most this many snapshots. If this is set to 0, the agent will not perform this and snapshots will accumulate forever. Defaults to 30.
+
+### Agent options
+
+- `-deregister-after`: An interval, after which if the agent is unhealthy it will be automatically deregistered from Consul service. discovery. This is a time with a unit suffix, which can be "s", "m", "h" for seconds, minutes, or hours. If 0 is provided, this will be disabled. Defaults to "72h".
+- `-log-level`: Controls verbosity of snapshot agent logs. Valid options are "TRACE", "DEBUG", "INFO", "WARN", "ERR". Defaults to "INFO".
+- `-log-json`: Output logs in JSON format. Defaults to false.
+- `-service`: The service name to used when registering the agent with Consul. Registering helps monitor running agents and the leader registers an additional health check to monitor that snapshots are taking place. Defaults to "nomad-snapshot".
+- `-syslog`: This enables forwarding logs to syslog. Defaults to false.
+- `-syslog-facility`: Sets the facility to use for forwarding logs to syslog. Defaults to "LOCAL0".
+
+### Local Storage options
+
+- `-local-path`: Location to store snapshots locally. The default behavior of the snapshot agent is to store snapshots locally in this directory. Defaults to "." to use the current working directory. If an alternate storage option is configured, then local storage will be disabled and this option will be ignored.
+
+### S3 Storage options:
+
+Note that despite the AWS references, any S3-compatible endpoint can be specified with '-aws-s3-endpoint'.
+
+- `-aws-access-key-id`: These arguments supply authentication information for
+- `-aws-secret-access-key`: connecting to S3. These may also be supplied using the following alternative methods:
+  - AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables
+  - A credentials file (~/.aws/credentials or the file at the path specified by the AWS_SHARED_CREDENTIALS_FILE environment variable)
+  - ECS task role metadata (container-specific)
+  - EC2 instance role metadata
+- `-aws-s3-bucket`: S3 bucket to use. Required for S3 storage, and setting this disables local storage.
+- `-aws-s3-key-prefix`: Prefix to use for snapshot files in S3. Defaults to "nomad-snapshot".
+- `-aws-s3-region`: S3 region to use. Required for S3 storage.
+- `-aws-s3-endpoint`: Optional S3 endpoint to use. Can also be specified using the AWS_S3_ENDPOINT environment variable.
+- `-aws-s3-server-side-encryption`: Enables server side encryption with AES-256, when storing snapshots to S3. Defaults to false.
+- `-aws-s3-static-snapshot-name`: Static file name to use for snapshot files. If this is set, snapshots are always saved with the same name, and are not versioned or rotated.
+- `-aws-s3-enable-kms`: Enables using Amazon KMS for encrypting snapshots
+- `-aws-s3-kms-key`: Optional KMS key to use, if this is not set the default KMS key will be used.
+
+### Azure Blob Storage options
+
+(Note: Non-Solaris platforms only)
+
+- `-azure-blob-account-name`: These arguments supply authentication information
+- `-azure-blob-account_key`: for connecting to Azure Blob storage.
+- `-azure-blob-container-name`: Container to use. Required for Azure blob storage, and setting this disables local storage.
+- `-azure-blob-environment`: Environment to use. Defaults to AZUREPUBLICCLOUD. Other valid environments are AZURECHINACLOUD, AZUREGERMANCLOUD and AZUREUSGOVERNMENTCLOUD.
+
+### Google Storage options
+
+- `-google-bucket`: The bucket to use.
+
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/inspect.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/inspect.mdx
new file mode 100644
index 0000000000..f527e8f20e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/inspect.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot inspect command reference'
+description: |
+  The `nomad operator snapshot inspect` command displays information about a snapshot file stored on local disk.
+---
+
+# `nomad operator snapshot inspect` command reference
+
+Displays information about a snapshot file stored on local disk.
+
+## Usage
+
+```plaintext
+nomad operator snapshot inspect [options] [file]
+```
+
+## Inspect options
+
+- `-json` : Output information about the snapshot file in JSON format.
+
+## Examples
+
+To inspect the file "backup.snap":
+```shell-session
+$ nomad operator snapshot inspect backup.snap
+Created = 2024-06-10T10:54:41+01:00
+ID      = 10-215871-1718013281130
+Size    = 158 KiB
+Index   = 215871
+Term    = 10
+Version = 1
+
+Type                 Count  Size
+JobVersion           15     42 KiB
+Alloc                5      37 KiB
+TimeTable            1      28 KiB
+JobSubmission        15     17 KiB
+Node                 2      14 KiB
+Job                  4      10 KiB
+CSIPlugin            1      1.9 KiB
+Eval                 5      1.6 KiB
+CSIVolume            1      1.1 KiB
+JobSummary           4      825 B
+Variables            2      695 B
+VariablesQuota       8      562 B
+Index                18     498 B
+Deployment           1      496 B
+ServiceRegistration  1      318 B
+ACLToken             1      286 B
+SchedulerConfig      1      242 B
+NodePool             2      236 B
+Namespace            1      209 B
+RootKeyMeta          1      127 B
+ClusterMetadata      1      71 B
+
+Total                90     158 KiB
+```
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/redact.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/redact.mdx
new file mode 100644
index 0000000000..dcdd59d469
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/redact.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot redact command reference'
+description: |
+ The `nomad operator snapshot redact` command removes key material from an existing snapshot file created by the `operator snapshot save` command so you can transmit a snapshot without exposing key material.
+---
+
+# `nomad operator snapshot redact` command reference
+
+
+The `operator snapshot redact` command removes key material from an existing
+snapshot file created by the `operator snapshot save` command, when using the
+AEAD keyring provider.
+
+This is useful for situations where you need to transmit a snapshot without
+exposing key material.
+
+<Warning>
+
+When using a [KMS keyring provider][], no cleartext key material is stored in
+snapshots and this command is not necessary. Note that this command requires
+loading the entire snapshot into memory locally and overwrites the existing
+snapshot.
+
+Snapshots made before Nomad 1.9.0 will not include the keyrings.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad operator snapshot redact <file>
+```
+
+
+[KMS keyring provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/restore.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/restore.mdx
new file mode 100644
index 0000000000..e7407a50d5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/restore.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot restore command reference'
+description: |
+  The `nomad operator snapshot restore` command restores the specified Nomad snapshot.
+---
+
+# `nomad operator snapshot restore` command reference
+
+The `operator snapshot restore` command restores an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs.
+
+Restoration involves a potentially dangerous low-level Raft operation that is
+not designed to handle server failures during a restore. This command is
+primarily intended for recovering from a disaster, restoring into a
+fresh cluster of Nomad servers.
+
+<Warning>
+
+This command only restores the Raft snapshot, which does not include keyrings.
+
+If you are recovering a cluster, you also need to restore the keyring onto at
+least one server.  Refer to the Key Management's [Restoring the
+Keyring from Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+This example srestore a snapshot from the file `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot restore backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot restore [options] <file>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/save.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/save.mdx
new file mode 100644
index 0000000000..1dc288b8ef
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/save.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot save command reference'
+description: |
+  The `nomad operator snapshot save` command saves an atomic, point-in-time snapshot of state of the Nomad servers, including jobs, nodes, allocations,periodic jobs, ACLs for outage recovery, and the keyring.
+---
+
+# `nomad operator snapshot save` command reference
+
+The `operator snapshot save` command retrieves an atomic, point-in-time
+snapshot of the state of the Nomad servers, which includes jobs, nodes,
+allocations, periodic jobs, and ACLs for [outage recovery].
+
+If you enabled ACLs, you must supply a management token in order to perform
+snapshot operations.
+
+<Warning>
+
+This command includes Nomad's keyring in the snapshot. If you are not using a
+[KMS provider][] to secure the keyring, you should use the `-redact` flag to
+remove key material before transmitting the snapshot to HashiCorp Support.
+
+Snapshots made before Nomad 1.9.0 will not include the keyrings. If you use
+older snapshots to recover a cluster, you also need to restore the keyring onto
+at least one server. Refer to the Key Management's [Restoring the Keyring from
+Backup][restore the keyring] section for instructions.
+
+</Warning>
+
+Run the `nomad operator snapshot save` command to create a snapshot from the
+leader server.
+
+This example saves the backup to `backup.snap`.
+
+```shell-session
+$ nomad operator snapshot save backup.snap
+```
+
+This example creates a potentially stale snapshot from any available server
+and saves it to `backup.snap`. The `-stale` option is useful if no
+leader is available.
+
+```shell-session
+$ nomad operator snapshot save -stale backup.snap
+```
+
+## Usage
+
+```plaintext
+nomad operator snapshot save [options] <file>
+```
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Snapshot save options
+
+- `-redact`: The redact option will locally edit the snapshot to remove any
+  cleartext key material from the root keyring. Only the AEAD keyring provider
+  has cleartext key material in Raft. Note that this operation requires loading
+  the snapshot into memory locally.
+
+- `-stale`: The stale option defaults to `false`, which means the leader
+  provides the result. If the cluster is in an outage state without a leader,
+  you may need to set `-stale` to `true` to get the configuration from a
+  non-leader server.
+
+[outage recovery]: /nomad/tutorials/manage-clusters/outage-recovery
+[restore the keyring]: /nomad/docs/operations/key-management#restoring-the-keyring-from-backup
+[KMS provider]: /nomad/docs/configuration/keyring
diff --git a/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/state.mdx b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/state.mdx
new file mode 100644
index 0000000000..218e99960a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/operator/snapshot/state.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'nomad operator snapshot state command reference'
+description: |
+  The `nomad operator snapshot state` command displays a JSON representation of a Raft snapshot.
+---
+
+# `nomad operator snapshot state` command reference
+
+Displays a JSON representation of state in a raft snapshot on disk.
+
+~> **Warning:** This is a low-level debugging tool and not subject to
+  Nomad's usual backward compatibility guarantees.
+
+## Usage
+
+```plaintext
+nomad operator snapshot state <file>
+```
+
+## Examples
+
+The output of this command can be very large, so it's recommended that
+you redirect the output to a file for later examination with other
+tools.
+
+```shell-session
+$ nomad operator snapshot state backup.snap > ~/raft-state.json
+$ jq . < ~/raft-state.json
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/plugin/index.mdx b/content/nomad/v1.9.x/content/docs/commands/plugin/index.mdx
new file mode 100644
index 0000000000..a218cdcfb5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/plugin/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'nomad plugin command reference'
+description: |
+  The `nomad plugin` command interacts with external plugins that a job can use, such as Container Storage Interface (CSI) plugins.
+---
+
+# `nomad plugin` command reference
+
+The `plugin` command is used to interact with external plugins that
+can be registered by Nomad jobs. Currently Nomad supports [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+Usage: `nomad plugin <subcommand> [options]`
+
+Run `nomad plugin <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`plugin status`][status] - Display status information about a plugin
+
+[csi]: https://github.com/container-storage-interface/spec
+[status]: /nomad/docs/commands/plugin/status 'Display status information about a plugin'
diff --git a/content/nomad/v1.9.x/content/docs/commands/plugin/status.mdx b/content/nomad/v1.9.x/content/docs/commands/plugin/status.mdx
new file mode 100644
index 0000000000..da22f3260b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/plugin/status.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: 'nomad plugin status command reference'
+description: |
+  The `nomad plugin status` displays information and status for a specific plugin, plugins by type, or all plugins.
+---
+
+# `nomad plugin status` command reference
+
+The `plugin status` command displays status information for [Container
+Storage Interface (CSI)][csi] plugins.
+
+## Usage
+
+```plaintext
+nomad plugin status [options] [plugin]
+```
+
+This command accepts an optional plugin ID or prefix as the sole argument. If there
+is an exact match based on the provided plugin ID or prefix, then information about
+the specific plugin is queried and displayed. Otherwise, a list of matching plugins
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing plugins and a few
+of the most useful status fields for each.
+
+If ACLs are enabled, this command requires a token with the `plugin:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Status options
+
+- `-type`: Display only plugins of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI plugins.
+
+- `-short`: Display short output. Used only when a single plugin is being queried.
+  Drops verbose plugin allocation data from the output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format.
+
+## Examples
+
+List of all plugins:
+
+```shell-session
+$ nomad plugin [-type csi] status
+ID         Provider  Controllers Healthy / Expected  Nodes Healthy / Expected
+ebs-prod   aws.ebs   1 / 1                           1 / 1
+```
+
+Short view of a specific plugin:
+
+```shell-session
+$ nomad plugin [-type csi] status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+```
+
+Full status information of a plugin with `-verbose` flag. Note that this example
+shows a plugin that has all supported capabilities. Most plugins will support a
+subset of these capabilities. Topology fields are also controlled by the plugin.
+
+```shell-session
+$ nomad plugin [-type csi] -verbose status ebs-prod
+ID                   = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+
+Controller Capabilities
+  ATTACH_READONLY
+  CLONE_VOLUME
+  CONTROLLER_ATTACH_DETACH
+  CREATE_DELETE_SNAPSHOT
+  CREATE_DELETE_VOLUME
+  EXPAND_VOLUME
+  GET_CAPACITY
+  GET_VOLUME
+  LIST_SNAPSHOTS
+  LIST_VOLUMES
+  LIST_VOLUMES_PUBLISHED_NODES
+  VOLUME_CONDITION
+
+Node Capabilities
+  EXPAND_VOLUME
+  GET_VOLUME_STATS
+  STAGE_UNSTAGE_VOLUME
+  VOLUME_ACCESSIBILITY_CONSTRAINTS
+  VOLUME_CONDITION
+
+Accessible Topologies
+Node ID   Accessible Topology
+95303afc  topology.ebs.csi.aws.com/zone=us-east-1a
+8bf94335  topology.ebs.csi.aws.com/zone=us-east-1b
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status    Created    Modified
+0de05689  95303afc  csi         0        run      running  1m57s ago  1m19s ago
+b206088c  8bf94335  csi         0        run      running  1m56s ago  1m19s ago
+```
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/apply.mdx
new file mode 100644
index 0000000000..680a27d5c3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/apply.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad quota apply command reference'
+description: |
+  The `nomad quota apply` command creates or updates a Nomad Enterprise quota specification.
+---
+
+# `nomad quota apply` command reference
+
+The `quota apply` command is used to create or update [quota specifications][].
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota apply [options] <path>
+```
+
+The `quota apply` command requires the path to the specification file. The
+specification can be read from stdin by setting the path to "-".
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Apply options
+
+- `-json`: Parse the input as a JSON quota specification.
+
+## Examples
+
+Create a new quota specification:
+
+```shell-session
+$ nomad quota apply my-quota.hcl
+Successfully applied quota specification "my-quota"!
+```
+
+[quota specifications]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/delete.mdx
new file mode 100644
index 0000000000..80223ca9af
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad quota delete command reference'
+description: |
+  The `nomad quota delete` command deletes an existing quota specification in Nomad Enterprise.
+---
+
+# `nomad quota delete` command reference
+
+The `quota delete` command is used to delete an existing quota specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota delete <quota_name>
+```
+
+The `quota delete` command requires the quota specification name as an argument.
+
+If ACLs are enabled, this command requires a token with the `quota:write`
+capability.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a quota specification:
+
+```shell-session
+$ nomad quota delete my-quota
+Successfully deleted quota "my-quota"!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/index.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/index.mdx
new file mode 100644
index 0000000000..00fdac9ffd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: 'nomad quota command reference'
+description: |
+  The `nomad quota` command interacts with Nomad Enterprise quota specifications. Generate an example specification. Create, update, delete, and inspect a quota specification. Display quota status and current usage. Retrieve a list of all quota specifications.
+---
+
+# `nomad quota` command reference
+
+The `quota` command is used to interact with quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+Usage: `nomad quota <subcommand> [options]`
+
+Run `nomad quota <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`quota apply`][quotaapply] - Create or update a quota specification
+- [`quota delete`][quotadelete] - Delete a quota specification
+- [`quota init`][quotainit] - Create an example quota specification file
+- [`quota inspect`][quotainspect] - Inspect a quota specification
+- [`quota list`][quotalist] - List quota specifications
+- [`quota status`][quotastatus] - Display a quota's status and current usage
+
+[quotaapply]: /nomad/docs/commands/quota/apply
+[quotadelete]: /nomad/docs/commands/quota/delete
+[quotainit]: /nomad/docs/commands/quota/init
+[quotainspect]: /nomad/docs/commands/quota/inspect
+[quotalist]: /nomad/docs/commands/quota/list
+[quotastatus]: /nomad/docs/commands/quota/status
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/init.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/init.mdx
new file mode 100644
index 0000000000..7fa2755b95
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/init.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: 'nomad quota init command reference'
+description: |
+  The `nomad quota init` command generates an example quota specification that you can customize for your Nomad Enterprise quota specification.
+---
+
+# `nomad quota init` command reference
+
+The `quota init` command is used to create an example [quota specification][]
+file that can be used as a starting point to customize further.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota init
+```
+
+## Init options
+
+- `-json`: Create an example JSON quota specification.
+
+## Examples
+
+Create an example quota specification:
+
+```shell-session
+$ nomad quota init
+Example quota specification written to spec.hcl
+```
+
+[quota specification]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/inspect.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/inspect.mdx
new file mode 100644
index 0000000000..cb70d5952a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/inspect.mdx
@@ -0,0 +1,128 @@
+---
+layout: docs
+page_title: 'nomad quota inspect command reference'
+description: >
+  The `nomad quota inspect` command displays raw information about a particular
+  quota specification in Nomad Enterprise.
+---
+
+# `nomad quota inspect` command reference
+
+The `quota inspect` command is used to view raw information about a particular
+quota. The default output is in JSON format.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota inspect [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Inspect options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+Inspect a quota specification:
+
+```shell-session
+$ nomad quota inspect default-quota
+{
+    "Spec": {
+        "CreateIndex": 11,
+        "Description": "Limit the shared default namespace",
+        "Limits": [
+            {
+                "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                "Region": "global",
+                "RegionLimit": {
+                    "CPU": 1000,
+                    "Cores": 1,
+                    "Devices": null,
+                    "DiskMB": 0,
+                    "IOPS": 0,
+                    "MemoryMB": 1000,
+                    "MemoryMaxMB": 0,
+                    "NUMA": null,
+                    "Networks": null
+                },
+                "VariablesLimit": 0
+            }
+        ],
+        "ModifyIndex": 11,
+        "Name": "default-quota"
+    },
+    "UsageLookupErrors": {},
+    "Usages": {
+        "global": {
+            "CreateIndex": 11,
+            "ModifyIndex": 12,
+            "Name": "default",
+            "Used": {
+                "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=": {
+                    "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+                    "Region": "global",
+                    "RegionLimit": {
+                        "CPU": 0,
+                        "Cores": 0,
+                        "Devices": null,
+                        "DiskMB": 0,
+                        "IOPS": 0,
+                        "MemoryMB": 0,
+                        "MemoryMaxMB": 0,
+                        "NUMA": null,
+                        "Networks": null
+                    },
+                    "VariablesLimit": 0
+                }
+            }
+        }
+    }
+}
+```
+
+The `-json` flag can be used to get the quota specs in json format:
+```shell-session
+$ nomad quota inspect -json default-quota
+{
+    "CreateIndex": 11,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 11,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota specs using a Go template:
+```shell-session
+$ nomad quota inspect -t '{{ .Description }}' default-quota
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/list.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/list.mdx
new file mode 100644
index 0000000000..36c6347fa3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/list.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'nomad quota list command reference'
+description: |
+  The `nomad quota list` command displays a list of available quota specifications in Nomad Enterprise.
+---
+
+# `nomad quota list` command reference
+
+The `quota list` command is used to list available quota specifications.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota list
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability. Any quotas applied to namespaces that the token does not have
+access to will be filtered from the results.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quotas specifications using a Go template.
+
+## Examples
+
+List all quota specifications:
+
+```shell-session
+$ nomad quota list
+Name     Description
+default  Limit the shared default namespace
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/quota/status.mdx b/content/nomad/v1.9.x/content/docs/commands/quota/status.mdx
new file mode 100644
index 0000000000..a55265e5d2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/quota/status.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: 'nomad quota status command reference'
+description: >
+  The `nomad quota status` command displays status information for a particular quota specification in Nomad Enterprise.
+---
+
+# `nomad quota status` command reference
+
+The `quota status` command is used to view the status of a particular quota
+specification.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad quota status [options] <quota_name>
+```
+
+If ACLs are enabled, this command requires a token with the `quota:read`
+capability and access to any namespaces that the quota is applied to.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Inspect options
+
+- `-json`: Output the quota specifications in a JSON format.
+
+- `-t`: Format and display the quota using a Go template.
+
+## Examples
+
+View the status of a quota specification:
+
+```shell-session
+$ nomad quota status default-quota
+Name        = default-quota
+Description = Limit the shared default namespace
+Limits      = 1
+
+Quota Limits
+Region  CPU Usage  Core Usage  Memory Usage  Memory Max Usage  Variables Usage
+global  0 / 1000   0 / 1       0 / 1000      0 / inf           0 / inf
+```
+
+The `-json` flag can be used to get the quota status in json format:
+
+```shell-session
+$ nomad quota status -json default-quota
+{
+    "CreateIndex": 8,
+    "Description": "Limit the shared default namespace",
+    "Limits": [
+        {
+            "Hash": "p7s7A+4mFt+M41NS3nB3APheQS9YaePLguvnNn/c1t4=",
+            "Region": "global",
+            "RegionLimit": {
+                "CPU": 1000,
+                "Cores": 1,
+                "Devices": null,
+                "DiskMB": 0,
+                "IOPS": 0,
+                "MemoryMB": 1000,
+                "MemoryMaxMB": 0,
+                "NUMA": null,
+                "Networks": null
+            },
+            "VariablesLimit": 0
+        }
+    ],
+    "ModifyIndex": 56,
+    "Name": "default-quota"
+}
+```
+
+Or use the `-t` flag to format and display the quota status using a Go template:
+
+```shell-session
+$ nomad quota status -t {{ .Description }} default-quota
+Limit the shared default namespace
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/recommendation/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/recommendation/apply.mdx
new file mode 100644
index 0000000000..035c78161b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/recommendation/apply.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: 'nomad recommendation apply command reference'
+description: |
+  The `nomad recommendation apply` command applies one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation apply` command reference
+
+The `recommendation apply` command is used to apply recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation apply [options] <recommendation_ids>
+```
+
+The `recommendation apply` command requires at least one recommendation ID to
+be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Apply options
+
+- `-detach`: Return immediately instead of entering monitor mode. After applying
+  a recommendation, the evaluation ID will be printed to the screen, which can
+  be used to examine the evaluation using the [`eval status`][/docs/commands/eval-status] command. If applying
+  recommendations for multiple jobs, this value will always be true.
+
+- `-policy-override`: If set, any soft mandatory Sentinel policies will be
+  overridden. This allows a recommendation to be applied when it would be denied
+  by a policy.
+
+- `-verbose`: Display full information.
+
+## Examples
+
+Apply a single recommendation and enter monitor mode:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10
+==> Monitoring evaluation "529cc88e"
+    Evaluation triggered by job "job1"
+    Evaluation within deployment: "28a3378f"
+    Allocation "2a4df8ca" created: node "2f0a2f93", group "group1"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "529cc88e" finished with status "complete"
+```
+
+Apply multiple recommendations for different jobs:
+
+```shell-session
+$ nomad recommendation apply a9c041c5-3c04-aa24-bd55-0a80cded4f10 811900b6-da11-ef08-f515-f5e6684007a8
+Errors
+None
+
+Results
+IDs                                   Namespace  Job ID   Eval ID                               Warnings
+a9c041c5-3c04-aa24-bd55-0a80cded4f10  default    example  7c39ad13-0246-ab8e-6c50-9f3ee500bf5f  <none>
+811900b6-da11-ef08-f515-f5e6684007a8  default    demoapp  68236421-c90f-efa6-fc02-37ae2d59bf03  <none>
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/recommendation/dismiss.mdx b/content/nomad/v1.9.x/content/docs/commands/recommendation/dismiss.mdx
new file mode 100644
index 0000000000..fd0cd75a46
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/recommendation/dismiss.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad recommendation dismiss command reference'
+description: |
+  The `nomad recommendation dismiss` command dismisses one or more recommendations in Nomad Enterprise.
+---
+
+# `nomad recommendation dismiss` command reference
+
+The `recommendation dismiss` command is used to dismiss recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation dismiss [options] <recommendation_ids>
+```
+
+The `recommendation dismiss` command requires at least one recommendation ID
+to be passed to it. Multiple IDs can be passed, with each recommendation ID
+separated from the next by a space.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the recommendation's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Dismiss a single recommendation:
+
+```shell-session
+$ nomad recommendation dismiss a9c041c5-3c04-aa24-bd55-0a80cded4f10
+Successfully dismissed recommendation
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/recommendation/index.mdx b/content/nomad/v1.9.x/content/docs/commands/recommendation/index.mdx
new file mode 100644
index 0000000000..a4c26a836b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/recommendation/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad recommendation command reference'
+description: |
+  The `nomad recommendation` command interacts with recommendations in Nomad Enterprise. Display a specific recommendation or a list of recommendations. Apply or dismiss recommendations.
+---
+
+# `nomad recommendation` command reference
+
+The `recommendation` command is used to interact with recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+Usage: `nomad recommendation <subcommand> [options]`
+
+Run `nomad recommendation <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`recommendation apply`][recommendationapply] - Apply one or more Nomad recommendations
+- [`recommendation dismiss`][recommendationdismiss] - Dismiss one or more Nomad recommendations
+- [`recommendation info`][recommendationinfo] - Display an individual Nomad recommendation
+- [`recommendation list`][recommendationlist] - Display all Nomad recommendations
+
+[recommendationapply]: /nomad/docs/commands/recommendation/apply
+[recommendationdismiss]: /nomad/docs/commands/recommendation/dismiss
+[recommendationinfo]: /nomad/docs/commands/recommendation/info
+[recommendationlist]: /nomad/docs/commands/recommendation/list
diff --git a/content/nomad/v1.9.x/content/docs/commands/recommendation/info.mdx b/content/nomad/v1.9.x/content/docs/commands/recommendation/info.mdx
new file mode 100644
index 0000000000..acae83e8cc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/recommendation/info.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: 'nomad recommendation info command reference'
+description: |
+  The `nomad recommendation info` command displays information about the specified recommendation in Nomad Enterprise.
+---
+
+# `nomad recommendation info` command reference
+
+The `recommendation info` command is used to read the specified recommendation.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation info [options] <recommendation_id>
+```
+
+The `recommendation info` command requires a single argument, a recommendation ID.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the recommendation's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Info options
+
+- `-json` : Output the recommendation in its JSON format.
+
+- `-t` : Format and display the recommendation using a Go template.
+
+## Examples
+
+View the information of a specific recommendation:
+
+```shell-session
+$ nomad recommendation info 68236421-c90f-efa6-fc02-37ae2d59bf03
+ID         = 68236421-c90f-efa6-fc02-37ae2d59bf03
+Namespace  = default
+Job ID     = example
+Task Group = cache
+Task       = redis
+Resource   = CPU
+Value      = 57
+Current    = 500
+
+Stats
+max   mean  min   p99
+5.89  1.66  0.44  5.89
+
+Meta
+nomad_policy_id       = e20dc742-dd5d-5419-8add-c5e0233933f5
+num_evaluated_windows = 2
+window_size           = 3e+11
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/recommendation/list.mdx b/content/nomad/v1.9.x/content/docs/commands/recommendation/list.mdx
new file mode 100644
index 0000000000..29973ee84f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/recommendation/list.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: 'nomad recommendation list command reference'
+description: |
+  The `nomad recommendation list` command displays a list of available recommendations in Nomad Enterprise. Filter options include job, group, and task.
+---
+
+# `nomad recommendation list` command reference
+
+The `recommendation list` command is used to list the available recommendations.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad recommendation list [options]
+```
+
+The `recommendation list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `submit-job`,
+`read-job`, and `submit-recommendation` capabilities for the namespace being
+queried.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-job`: Specifies the job ID to filter the recommendations list by.
+
+- `-group`: Specifies the task group name to filter within a job. If specified,
+  the `-job` flag must also be specified.
+
+- `-task`: Specifies the task name to filter within a job and task group. If
+  specified, the `-job` and `-group` flags must also be specified.
+
+- `-json`: Output the recommendations in its JSON format.
+
+- `-t`: Format and display the recommendations using a Go template.
+
+## Examples
+
+List all available recommendations:
+
+```shell-session
+$ nomad recommendation list
+ID                                    Job      Group     Task   Resource  Value
+ea130ac3-1410-cfe0-f34d-adc3ca94712d  example  cache-lb  nginx  CPU       57
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache     redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache     redis  MemoryMB  10
+```
+
+List all available recommendations for the job `example` and the task group `cache`:
+
+```shell-session
+$ nomad recommendation list -job=example -group=cache
+ID                                    Job      Group  Task   Resource  Value
+68236421-c90f-efa6-fc02-37ae2d59bf03  example  cache  redis  CPU       57
+980c2554-7a1b-0c51-933a-f46850a228bd  example  cache  redis  MemoryMB  10
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/scaling/index.mdx b/content/nomad/v1.9.x/content/docs/commands/scaling/index.mdx
new file mode 100644
index 0000000000..d66b06fb76
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/scaling/index.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: 'nomad scaling command reference'
+description: |
+  The `nomad scaling` command interacts with scaling policies.
+---
+
+# `nomad scaling` command reference
+
+The `scaling` command is used to interact with the scaling API.
+
+## Usage
+
+Usage: `nomad scaling <subcommand> [options]`
+
+Run `nomad scaling <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`policy info`][scalingpolicyinfo] - Display an individual Nomad scaling policy
+- [`policy list`][scalingpolicylist] - List all Nomad scaling policies
+
+[scalingpolicyinfo]: /nomad/docs/commands/scaling/policy-info
+[scalingpolicylist]: /nomad/docs/commands/scaling/policy-list
diff --git a/content/nomad/v1.9.x/content/docs/commands/scaling/policy-info.mdx b/content/nomad/v1.9.x/content/docs/commands/scaling/policy-info.mdx
new file mode 100644
index 0000000000..60def5a97f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/scaling/policy-info.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad scaling policy info command reference'
+description: |
+  The `nomad scaling policy info` command displays detailed information for the specified scaling policy.
+---
+
+# `nomad scaling policy info` command reference
+
+Info is used to return detailed information on the specified scaling policy.
+
+## Usage
+
+```plaintext
+nomad scaling policy info [options] <policy_id>
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the policy's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Policy Info options
+
+- `-json` : Output the scaling policy in its JSON format.
+- `-t` : Format and display the scaling policy using a Go template.
+
+## Examples
+
+Inspect an individual scaling policy:
+
+```shell-session
+$ nomad scaling policy info 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+
+ID      = 31a53813-24df-b2ad-77dc-1b4bad4e7dca
+Enabled = true
+Target  = Namespace:default,Job:webapp,Group:demo
+Min     = 1
+Max     = 20
+
+Policy:
+{
+    "check": [
+        {
+            "avg_sessions": [
+                {
+                    "query": "scalar(sum(traefik_entrypoint_open_connections{entrypoint=\"horizontal-webapp\"}))",
+                    "source": "prometheus",
+                    "strategy": [
+                        {
+                            "target-value": [
+                                {
+                                    "target": 10.0
+                                }
+                            ]
+                        }
+                    ]
+                }
+            ]
+        }
+    ],
+    "cooldown": "1m",
+    "evaluation_interval": "30s"
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/scaling/policy-list.mdx b/content/nomad/v1.9.x/content/docs/commands/scaling/policy-list.mdx
new file mode 100644
index 0000000000..c3e6a0e865
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/scaling/policy-list.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: 'nomad scaling policy list command reference'
+description: |
+  The `nomad scaling policy list` command displays all Nomad scaling policies. Filter options include job and policy type.
+---
+
+# `nomad scaling policy list` command reference
+
+List is used to list all scaling policies stored in Nomad.
+
+## Usage
+
+```plaintext
+nomad scaling policy list [options]
+```
+
+If ACLs are enabled, this command requires a token with the `read-job` and
+`list-jobs` capabilities for the namespace of all policies. Any namespaces
+that the token does not have access to will have its policies filtered from
+the results.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Policy List options
+
+- `-job` : Specifies the job ID to filter the scaling policies list by.
+- `-type` : Filter scaling policies by type.
+- `-json` : Output the scaling policy list in its JSON format.
+- `-t` : Format and display the scaling policy list using a Go template.
+
+## Examples
+
+List all tracked scaling policies:
+
+```shell-session
+$ nomad scaling policy list
+
+ID                                    Enabled  Target
+b2c64295-4315-2fdc-6158-a27156808729  true     Namespace:default,Job:example,Group:cache,Task:redis
+c355d0ec-7aa1-2604-449d-4ec79c813d2c  true     Namespace:default,Job:webapp,Group:demo,Task:webapp
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/sentinel/apply.mdx b/content/nomad/v1.9.x/content/docs/commands/sentinel/apply.mdx
new file mode 100644
index 0000000000..67c6fde5fa
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/sentinel/apply.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'nomad sentinel apply command reference'
+description: >
+  The `nomad sentinel apply` command creates or updates a Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel apply` command reference
+
+The `sentinel apply` command is used to write a new, or update an existing,
+Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel apply [options] <Policy Name> <Policy File>
+```
+
+The `sentinel apply` command requires two arguments, the policy name and the
+policy file. The policy file can be read from stdin by specifying "-" as the
+file name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Apply options
+
+- `-description` : Sets a human readable description for the policy
+
+- `-scope` : (default: submit-job) Sets the scope of the policy and when it
+  should be enforced.
+
+- `-level` : (default: advisory) Sets the enforcement level of the policy. Must
+  be one of advisory, soft-mandatory, hard-mandatory.
+
+## Examples
+
+Write a policy:
+
+```shell-session
+$ nomad sentinel write -description "My test policy" foo test.sentinel
+Successfully wrote "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/sentinel/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/sentinel/delete.mdx
new file mode 100644
index 0000000000..339d75b1f8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/sentinel/delete.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad sentinel delete command reference'
+description: |
+  The `nomad sentinel delete` command deletes the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel delete` command reference
+
+The `sentinel delete` command is used to delete a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>.
+
+## Usage
+
+```plaintext
+nomad sentinel delete [options] <Policy Name>
+```
+
+The `sentinel delete` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Delete a policy:
+
+```shell-session
+$ nomad sentinel delete foo
+Successfully deleted "foo" Sentinel policy!
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/sentinel/index.mdx b/content/nomad/v1.9.x/content/docs/commands/sentinel/index.mdx
new file mode 100644
index 0000000000..ddab180e3e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/sentinel/index.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: 'nomad sentinel command reference'
+description: |
+  The `nomad sentinel` command interacts with Sentinel policies in Nomad Enterprise. Create, update, and delete a policy. Inspect and list policies.
+---
+
+# `nomad sentinel` command reference
+
+The `sentinel` command is used to interact with Sentinel policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+Usage: `nomad sentinel <subcommand> [options]`
+
+Run `nomad sentinel <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`sentinel apply`][apply] - Create a new or update existing Sentinel policies
+- [`sentinel delete`][delete] - Delete an existing Sentinel policies
+- [`sentinel list`][list] - Display all Sentinel policies
+- [`sentinel read`][read] - Inspects an existing Sentinel policies
+
+[delete]: /nomad/docs/commands/sentinel/delete
+[list]: /nomad/docs/commands/sentinel/list
+[read]: /nomad/docs/commands/sentinel/read
+[apply]: /nomad/docs/commands/sentinel/apply
diff --git a/content/nomad/v1.9.x/content/docs/commands/sentinel/list.mdx b/content/nomad/v1.9.x/content/docs/commands/sentinel/list.mdx
new file mode 100644
index 0000000000..6195cbe230
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/sentinel/list.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'nomad sentinel list command reference'
+description: |
+  The `nomad sentinel list` command displays a list all Sentinel policies installed in Nomad Enterprise.
+---
+
+# `nomad sentinel list` command reference
+
+The `sentinel list` command is used to display all the installed Sentinel
+policies.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel list [options]
+```
+
+The `sentinel list` command requires no arguments.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+List all policies:
+
+```shell-session
+$ nomad sentinel list
+Name  Scope       Enforcement Level  Description
+foo   submit-job  advisory           my test policy
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/sentinel/read.mdx b/content/nomad/v1.9.x/content/docs/commands/sentinel/read.mdx
new file mode 100644
index 0000000000..3301721d0e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/sentinel/read.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: 'nomad sentinel read command reference'
+description: |
+  The `nomad sentinel read` command displays detailed information about the specified Sentinel policy in Nomad Enterprise.
+---
+
+# `nomad sentinel read` command reference
+
+The `sentinel read` command is used to inspect a Sentinel policy.
+
+<EnterpriseAlert product="nomad"/>
+
+## Usage
+
+```plaintext
+nomad sentinel read [options] <Policy Name>
+```
+
+The `sentinel read` command requires a single argument, the policy name.
+
+Sentinel commands are only available when ACLs are enabled. This command
+requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Read options
+
+- `-raw` : Output the raw policy only.
+
+## Examples
+
+Read all policies:
+
+```shell-session
+$ nomad sentinel read foo
+Name              = foo
+Scope             = submit-job
+Enforcement Level = advisory
+Description       = my test policy
+Policy:
+
+main = rule { true }
+
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/server/force-leave.mdx b/content/nomad/v1.9.x/content/docs/commands/server/force-leave.mdx
new file mode 100644
index 0000000000..d58aee14b1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/server/force-leave.mdx
@@ -0,0 +1,55 @@
+---
+layout: docs
+page_title: 'nomad server force-leave command reference'
+description: >
+  The `nomad server force-leave` command forces a server into the left state so that you can eject server nodes that have failed.
+---
+
+# `nomad server force-leave` command reference
+
+The `server force-leave` command forces a server to enter the "left" state.
+This can be used to eject server nodes which have failed and will not rejoin
+the cluster. The failed or left server will be garbage collected after `24h`.
+
+~> Note that if the server is actually still alive, it will
+eventually rejoin the cluster again.
+
+## Usage
+
+```plaintext
+nomad server force-leave [options] <node>
+```
+
+This command expects only one argument - the node which should be forced
+to enter the "left" state.
+
+Additionally, by specifying the `prune` flag, a failed or left node can be forcibly removed
+from the list of members immediately.
+
+If ACLs are enabled, this option requires a token with the `agent:write`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server force-leave options
+
+- `-prune`: Removes failed or left server from the Serf member list immediately.
+	If member is actually still alive, it will eventually rejoin the cluster again.
+
+## Examples
+
+Force-leave the server "node1":
+
+```shell-session
+$ nomad server force-leave node1
+
+```
+
+Force-leave the server "node1" and prune it:
+
+```shell-session
+$ nomad server force-leave -prune node1
+
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/server/index.mdx b/content/nomad/v1.9.x/content/docs/commands/server/index.mdx
new file mode 100644
index 0000000000..54db6b9eec
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/server/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'nomad server command reference'
+description: |
+  The `nomad server` command interacts with Nomad servers. Display a list of servers, join server nodes together, and force a server into the left state.
+---
+
+# `nomad server` command reference
+
+Command: `nomad server`
+
+The `server` command is used to interact with servers.
+
+## Usage
+
+Usage: `nomad server <subcommand> [options]`
+
+Run `nomad server <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`server force-leave`][force-leave] - Force a server into the 'left' state
+- [`server join`][join] - Join server nodes together
+- [`server members`][members] - Display a list of known servers and their status
+
+[force-leave]: /nomad/docs/commands/server/force-leave "Force a server into the 'left' state"
+[join]: /nomad/docs/commands/server/join 'Join server nodes together'
+[members]: /nomad/docs/commands/server/members 'Display a list of known servers and their status'
diff --git a/content/nomad/v1.9.x/content/docs/commands/server/join.mdx b/content/nomad/v1.9.x/content/docs/commands/server/join.mdx
new file mode 100644
index 0000000000..f8ee26af48
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/server/join.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: 'nomad server join command reference'
+description: >
+  The `nomad server join` command joins the local server to one or more Nomad
+  servers.
+---
+
+# `nomad server join` command reference
+
+The `server join` command joins the local server to one or more Nomad servers.
+Joining is only required for server nodes, and only needs to succeed against
+one or more of the provided addresses. Once joined, the gossip layer will
+handle discovery of the other server nodes in the cluster.
+
+## Usage
+
+```plaintext
+nomad server join [options] <addr> [<addr>...]
+```
+
+One or more server addresses are required. If multiple server addresses are
+specified, then an attempt will be made to join each one. If one or more nodes
+are joined successfully, the exit code will be 0. Otherwise, the exit code will
+be 1.
+
+Joining servers in different regions will [federate][] the regions. This assumes
+that ACLs have been bootstrapped in the authoritative region. See [Configure for
+multiple regions][] in the ACLs tutorial.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Join the local server to a remote server:
+
+```shell-session
+$ nomad server join 10.0.0.8:4648
+Joined 1 servers successfully
+```
+
+[federate]: /nomad/tutorials/manage-clusters/federation
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.9.x/content/docs/commands/server/members.mdx b/content/nomad/v1.9.x/content/docs/commands/server/members.mdx
new file mode 100644
index 0000000000..183ec11a36
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/server/members.mdx
@@ -0,0 +1,103 @@
+---
+layout: docs
+page_title: 'nomad server members command reference'
+description: >
+  The `nomad server members` command displays a list of servers in the cluster. Review name, address, port, region, datacenter, Raft version, build version, status, tags, and whether the server is the leader.
+---
+
+# `nomad server members` command reference
+
+The `server members` command displays a list of the known servers in the cluster
+and their current status. Member information is provided by the gossip protocol,
+which is only run on server nodes.
+
+## Usage
+
+```plaintext
+nomad server members [options]
+```
+
+If ACLs are enabled, this option requires a token with the `node:read`
+capability.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Server Members options
+
+- `-detailed` (<code>_deprecated_</code> use `-verbose` instead): Dump the
+  basic member information as well as the raw set of tags for each member. This
+  mode reveals additional information not displayed in the standard output
+  format.
+
+- `-verbose`: Dump the basic member information as well as the raw set of tags
+  for each member. This mode reveals additional information not displayed in
+  the standard output format.
+
+- `-json`: Output the server members in its JSON format.
+
+- `-t`: Format and display the server members using a Go template.
+
+## Examples
+
+Default view:
+
+```shell-session
+$ nomad server members
+Name             Address    Port  Status  Leader  Raft Version  Build  Datacenter  Region
+server-1.global  10.0.0.8   4648  alive   true    3             1.3.0  dc1         global
+server-2.global  10.0.0.9   4648  alive   false   3             1.3.0  dc1         global
+server-3.global  10.0.0.10  4648  alive   false   3             1.3.0  dc1         global
+```
+
+Verbose view:
+
+```shell-session
+$ nomad server members -verbose
+Name             Address    Port  Status  Leader  Protocol  Raft Version  Build  Datacenter  Region  Tags
+server-1.global  10.0.0.8   4648  alive   true    2         3             1.3.0  dc1         global  id=46122039-7c4d-4647-673a-81786bce2c23,rpc_addr=10.0.0.8,role=nomad,region=global,raft_vsn=3,expect=3,dc=dc1,build=1.3.0,port=4647
+server-2.global  10.0.0.9   4648  alive   false   2         3             1.3.0  dc1         global  id=04594bee-fec9-4cec-f308-eebe82025ae7,dc=dc1,expect=3,rpc_addr=10.0.0.9,raft_vsn=3,port=4647,role=nomad,region=global,build=1.3.0
+server-3.global  10.0.0.10  4648  alive   false   2         3             1.3.0  dc1         global  region=global,dc=dc1,rpc_addr=10.0.0.10,raft_vsn=3,build=1.3.0,expect=3,id=59542f6c-fb0e-50f1-4c9f-98bb593e9fe8,role=nomad,port=4647
+```
+
+The `-json` flag can be used to get the latest server members information in json format:
+
+```shell-session
+$ nomad server members -json
+[
+    {
+        "Addr": "127.0.0.1",
+        "DelegateCur": 4,
+        "DelegateMax": 5,
+        "DelegateMin": 2,
+        "Name": "bacon-mac.global",
+        "Port": 4648,
+        "ProtocolCur": 2,
+        "ProtocolMax": 5,
+        "ProtocolMin": 1,
+        "Status": "alive",
+        "Tags": {
+            "build": "1.5.0",
+            "region": "global",
+            "rpc_addr": "127.0.0.1",
+            "role": "nomad",
+            "raft_vsn": "3",
+            "bootstrap": "1",
+            "expect": "1",
+            "dc": "dc1",
+            "port": "4647",
+            "revision": "fc40c491cacec3d8ec3f2f98cd82b9068a50797c",
+            "vsn": "1",
+            "id": "354fd9a8-4228-ca8e-8b93-3cf002514910"
+        }
+    }
+]
+  ```
+
+Or use the `-t` flag to format and display the server members information using a Go template:
+
+```shell-session
+$ nomad server members -t '{{range .}}{{printf "%s: %s" .Name .Status }}{{end}}'
+bacon-mac.global: alive
+```
\ No newline at end of file
diff --git a/content/nomad/v1.9.x/content/docs/commands/service/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/service/delete.mdx
new file mode 100644
index 0000000000..122cd71b93
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/service/delete.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: 'nomad service delete command reference'
+description: |
+  The `nomad service delete` command deletes a Nomad service by name and ID.
+---
+
+# `nomad service delete` command reference
+
+The `service delete` command is used to delete an individual service
+registration. <em>This command is not expected to be used during normal
+operations of Nomad and should be used with caution.</em>
+
+## Usage
+
+```plaintext
+nomad service delete [options] <service_name> <service_id>
+```
+
+The `service delete` command requires two arguments, the name of the service
+and the ID of the individual registration to delete.
+
+When ACLs are enabled, this command requires a token with the `submit-job`
+capability for the service registration namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Delete a service registration:
+
+```shell-session
+$ nomad service delete example-cache-redis _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Successfully deleted service registration
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/service/index.mdx b/content/nomad/v1.9.x/content/docs/commands/service/index.mdx
new file mode 100644
index 0000000000..6c73bff2b2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/service/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: 'nomad service command reference'
+description: |
+  The `nomad service` command interacts with Nomad services. Display service  information and delete a registered service.
+---
+
+# `nomad service` command reference
+
+The `service` command is used to interact with the service API.
+
+## Usage
+
+Usage: `nomad service <subcommand> [options]`
+
+Run `nomad service <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`service delete`][servicedelete] - Deregister a registered service
+- [`service info`][serviceinfo] - Display an individual Nomad service registration
+- [`service list`][servicelist] - Display all registered Nomad services
+
+[servicedelete]: /nomad/docs/commands/service/delete
+[serviceinfo]: /nomad/docs/commands/service/info
+[servicelist]: /nomad/docs/commands/service/list
diff --git a/content/nomad/v1.9.x/content/docs/commands/service/info.mdx b/content/nomad/v1.9.x/content/docs/commands/service/info.mdx
new file mode 100644
index 0000000000..6f284f973c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/service/info.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad service info command reference'
+description: |
+  The `nomad service info` command displays information about the specified registered service. Search by service name to review namespace, job, allocation, node, datacenter, address, and tags.
+---
+
+# `nomad service info` command reference
+
+The `service info` command is used to read the specified Nomad registered
+service by name.
+
+## Usage
+
+```plaintext
+nomad service info [options] <service_name>
+```
+
+The `service info` command requires a single argument, a service name.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the service's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Info options
+
+- `-per-page`: How many results to show per page.
+
+- `-page-token`: Where to start pagination.
+
+- `-filter`: Specifies an expression used to filter query results.
+
+- `-json` : Output the service registrations in JSON format.
+
+- `-t` : Format and display the service registrations using a Go template.
+
+- `verbose` : Display full information.
+
+## Examples
+
+View the information of a specific service:
+
+```shell-session
+$ nomad service info example-cache-redis
+Job ID   Address          Tags        Node ID   Alloc ID
+example  127.0.0.1:22686  [db,cache]  7406e90b  5f0730ca
+example  127.0.0.1:25854  [db,cache]  7406e90b  a831f7f2
+```
+
+View the verbose information of a specific service:
+
+```shell-session
+$ nomad service info -verbose example-cache-redis
+ID           = _nomad-task-5f0730ca-b055-52ac-f56e-358f3f7412f6-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = 5f0730ca-b055-52ac-f56e-358f3f7412f6
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:22686
+Tags         = [db,cache]
+
+ID           = _nomad-task-a831f7f2-4c01-39dc-c742-f2b8ca178a49-redis-example-cache-redis-db
+Service Name = example-cache-redis
+Namespace    = default
+Job ID       = example
+Alloc ID     = a831f7f2-4c01-39dc-c742-f2b8ca178a49
+Node ID      = 7406e90b-de16-d118-80fe-60d0f2730cb3
+Datacenter   = dc1
+Address      = 127.0.0.1:25854
+Tags         = [db,cache]
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/service/list.mdx b/content/nomad/v1.9.x/content/docs/commands/service/list.mdx
new file mode 100644
index 0000000000..2e84908bfa
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/service/list.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: 'nomad service list command reference'
+description: |
+  The `nomad service list` command displays a list of registered Nomad services.
+---
+
+# `nomad service list` command reference
+
+The `service list` command is used to list the registered Nomad services.
+
+## Usage
+
+```plaintext
+nomad service list [options]
+```
+
+The `service list` command requires no arguments.
+
+When ACLs are enabled, this command requires a token with the `read-job`
+capability for the namespace being queried.
+
+The command supports the wildcard namespace identifier. Any namespaces that
+the token does not have access to will have its services filtered from the
+results.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-json`: Output the services in its JSON format.
+
+- `-t`: Format and display the services using a Go template.
+
+## Examples
+
+List all services in the `default` namespace:
+
+```shell-session
+$ nomad service list
+Service Name         Tags
+example-cache-redis  [cache,db]
+```
+
+List all services in all namespaces:
+
+```shell-session
+$ nomad service list -namespace="*"
+Service Name                  Namespace  Tags
+example-cache-redis           default    [cache,db]
+platform-example-cache-redis  platform   []
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/setup/consul.mdx b/content/nomad/v1.9.x/content/docs/commands/setup/consul.mdx
new file mode 100644
index 0000000000..6beb6ecc87
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/setup/consul.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: 'nomad setup consul command reference'
+description: |
+  The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup consul` command reference
+
+The `nomad setup consul` command configures a Consul cluster to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Consul and respects
+`CONSUL_HTTP_TOKEN`, `CONSUL_HTTP_ADDR`, and other [Consul-related environment
+variables][consulenv].
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup consul [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup consul
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Consul ACL using their
+respective workload identities.
+
+First we need to connect to Consul.
+
+[?] Is "127.0.0.1:8500" the correct address of your Consul cluster? [Y/n]
+
+Since you're running Consul Enterprise, we will additionally create
+a namespace "nomad-workloads" and bind the auth methods to that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Consul cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+Nomad needs a JWT auth method for Consul services and tasks. The method for
+services will be called "nomad-workloads".
+
+This is the "nomad-workloads" method configuration:
+
+{
+    "Name": "nomad-workloads",
+    "Type": "jwt",
+    "DisplayName": "nomad-workloads",
+    "Description": "Login method for Nomad workloads using workload identities",
+    "TokenLocality": "local",
+    "Config": {
+        "BoundAudiences": [
+            "consul.io"
+        ],
+        "ClaimMappings": {
+            "consul_namespace": "consul_namespace",
+            "nomad_job_id": "nomad_job_id",
+            "nomad_namespace": "nomad_namespace",
+            "nomad_service": "nomad_service",
+            "nomad_task": "nomad_task"
+        },
+        "JWKSURL": "http://localhost:4646/.well-known/jwks.json",
+        "JWTSupportedAlgs": [
+            "RS256"
+        ]
+    },
+    "CreateIndex": 0,
+    "ModifyIndex": 0,
+    "NamespaceRules": [
+        {
+            "BindNamespace": "${value.consul_namespace}"
+        }
+    ]
+}
+[?] Create "nomad-workloads" auth method in your Consul cluster? [Y/n]
+[✔] Created auth method "nomad-workloads".
+
+Consul uses binding rules to map claims between Nomad's JWTs to Consul service
+identities and ACL roles, so we need to create a two binding rules for the auth
+method we created above: one for services, and one for tasks.
+
+This is the binding rule for services:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad services authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" in value",
+    "BindType": "service",
+    "BindName": "${value.nomad_service}",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n]
+[✔] Created binding rule for auth method "nomad-workloads".
+
+This is the binding rule for tasks:
+
+{
+    "ID": "",
+    "Description": "Binding rule for Nomad tasks authenticated using a workload identity",
+    "AuthMethod": "nomad-workloads",
+    "Selector": "\"nomad_service\" not in value",
+    "BindType": "role",
+    "BindName": "nomad-${value.nomad_namespace}-tasks",
+    "CreateIndex": 0,
+    "ModifyIndex": 0
+}
+[?] Create this binding rule in your Consul cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Consul
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Auth method: nomad-workloads
+  * Binding rules: 4d80108a-6d77-36e1-71b1-d20a9acf8b17
+  * Namespace: nomad-workloads
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted binding rule "4d80108a-6d77-36e1-71b1-d20a9acf8b17".
+[✔] Deleted auth method "nomad-workloads".
+[✔] Deleted namespace "nomad-workloads".
+
+Consul cluster has not been configured for authenticating Nomad tasks and
+services using workload identitiies.
+
+Run the command again to finish the configuration process.
+```
+
+[consulenv]: /consul/commands#environment-variables
diff --git a/content/nomad/v1.9.x/content/docs/commands/setup/index.mdx b/content/nomad/v1.9.x/content/docs/commands/setup/index.mdx
new file mode 100644
index 0000000000..f4d683b944
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/setup/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad setup command reference'
+description: |
+  The `nomad setup` command sets up Consul and Vault integration.
+---
+
+# `nomad setup` command reference
+
+The `setup` command groups helper subcommands used for setting up external
+tools.
+
+<Warning>
+
+These commands are experimental features and may change their behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+Usage: `nomad setup <subcommand> [options]`
+
+Run `nomad setup <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`setup consul`][consul] - Setup a Consul cluster for Nomad integration.
+- [`setup vault`][vault] - Setup a Vault cluster for Nomad integration.
+
+[consul]: /nomad/docs/commands/setup/consul
+[vault]: /nomad/docs/commands/setup/vault
diff --git a/content/nomad/v1.9.x/content/docs/commands/setup/vault.mdx b/content/nomad/v1.9.x/content/docs/commands/setup/vault.mdx
new file mode 100644
index 0000000000..e8ffc8bf22
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/setup/vault.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: 'nomad setup vault command reference'
+description: |
+  The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+---
+
+# `nomad setup vault` command reference
+
+The `nomad setup vault` command configures a Vault installation to allow Nomad workloads to authenticate themselves with workload identity.
+
+This command requires `acl:write` permissions for Vault and respects
+`VAULT_TOKEN`, `VAULT_ADDR`, and other [Vault-related environment
+variables][vaultenv].
+
+The `-check` option can be used to verify if the Nomad cluster is ready to
+migrate to use Workload Identities with Vault. This option requires
+`operator:read` permission for Nomad.
+
+Refer to [Migrating to Using Workload Identity with
+Vault][nomad_acl_vault_wid_migrate] for more information.
+
+<Warning>
+
+This command is an experimental feature and may change its behavior in future
+versions of Nomad.
+
+</Warning>
+
+## Usage
+
+```plaintext
+nomad setup vault [options]
+```
+
+## Options
+
+- `-jwks-url`: URL of Nomad's JWKS endpoint contacted by Consul to verify JWT
+  signatures. Defaults to `http://localhost:4646/.well-known/jwks.json`.
+
+- `-jwks-ca-file`: Path to a CA certificate file that will be used to validate
+  the JWKS URL if it uses TLS.
+
+- `-destroy`: Removes all configuration components this command created from the
+  Consul cluster.
+
+- `-y`: Automatically answers `yes` to all the questions, making the setup
+  non-interactive. Defaults to `false`.
+
+- `-check`: Verify if the Nomad cluster is ready to migrate to Workload
+  Identities.
+
+### Options when using `-check`
+
+- `-json`: Output migration status information in its JSON format.
+
+- `-t`: Format and display migration status information using a Go template.
+
+- `-verbose`: Display full information.
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Below is an example of an interactive session with default options, interrupted
+by answering `no` to one of the questions, demonstrating the capabilities of the
+`-destroy` flag.
+
+```shell-session
+$ nomad setup vault
+
+This command will walk you through configuring all the components required for
+Nomad workloads to authenticate themselves against Vault ACL using their
+respective workload identities.
+
+First we need to connect to Vault.
+
+[?] Is "http://127.0.0.1:8200" the correct address of your Vault cluster? [Y/n]
+
+Since you're running Vault Enterprise, we will additionally create
+a namespace "nomad-workloads" and create all configuration within that namespace.
+
+[?] Create the namespace "nomad-workloads" in your Vault cluster? [Y/n]
+[✔] Created namespace "nomad-workloads".
+
+We will now enable the JWT credential backend and create a JWT auth method that
+Nomad workloads will use.
+
+This is the method configuration:
+
+{
+    "default_role": "nomad-workloads",
+    "jwks_url": "http://localhost:4646/.well-known/jwks.json",
+    "jwt_supported_algs": [
+        "EdDSA",
+        "RS256"
+    ]
+}
+[?] Create JWT auth method in your Vault cluster? [Y/n]
+[✔] Created JWT auth method "jwt-nomad".
+
+We need to create a role that Nomad workloads will assume while authenticating,
+and a policy associated with that role.
+
+
+These are the rules for the policy "nomad-workloads" that we will create. It uses a templated
+policy to allow Nomad tasks to access secrets in the path
+"secrets/data/<job namespace>/<job name>":
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_1b8dcc32.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+
+[?] Create the above policy in your Vault cluster? [Y/n]
+[✔] Created policy "nomad-workloads".
+
+We will now create an ACL role called "nomad-workloads" associated with the policy above.
+
+{
+    "bound_audiences": "vault.io",
+    "claim_mappings": {
+        "nomad_job_id": "nomad_job_id",
+        "nomad_namespace": "nomad_namespace",
+        "nomad_task": "nomad_task"
+    },
+    "role_type": "jwt",
+    "token_period": "30m",
+    "token_policies": [
+        "nomad-workloads"
+    ],
+    "token_type": "service",
+    "user_claim": "/nomad_job_id",
+    "user_claim_json_pointer": true
+}
+[?] Create role in your Vault cluster? [Y/n] n
+
+By answering "no" to any of these questions, you are risking an incorrect Vault
+cluster configuration. Nomad workloads with Workload Identity will not be able
+to authenticate unless you create missing configuration yourself.
+
+[?] Remove everything this command creates? [Y/n]
+The following items will be deleted:
+  * Policy: "nomad-workloads"
+  * JWT auth method: "jwt-nomad"
+  * Namespace: "nomad-workloads"
+
+[?] Remove all the items listed above? [Y/n]
+[✔] Deleted policy "nomad-workloads".
+[✔] Disabled JWT auth method "jwt-nomad".
+[✔] Deleted namespace "nomad-workloads".
+
+Vault cluster has not been configured for authenticating Nomad tasks and
+services using workload identities.
+
+Run the command again to finish the configuration process.
+```
+
+The `-check` option can use to verify if a cluster is ready to migrate to using
+workload identities with Vault.
+
+```
+$ nomad setup vault -check
+
+Jobs Without Workload Identity for Vault
+The following jobs access Vault but are not configured for workload identity.
+
+You should redeploy them before fully migrating to workload identities with
+Vault to prevent unexpected errors if their tokens need to be recreated.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID       Namespace  Type     Status
+example  default    service  running
+
+Outdated Nodes
+The following nodes are running a version of Nomad that does not support using
+workload identities with Vault.
+
+You should upgrade them to Nomad 1.7 before fully migrating to workload
+identities with Vault to prevent unexpected errors if they receive allocations
+for jobs that use Vault.
+
+Refer to https://developer.hashicorp.com/nomad/s/vault-workload-identity-migration
+for more information.
+
+ID        Name      Address        Version  Drain  Eligibility  Status
+049f7683  client-1  192.168.0.186  1.6.4    false  eligible     ready
+
+Vault Tokens
+The following Vault ACL tokens were created by Nomad but will not be
+automatically revoked after migrating to workload identities. They will expire
+once their TTL reaches zero.
+
+Accessor ID               Allocation ID  Node ID   Configured TTL
+czh9MPcRXzAhxBL9XKyb3Kh1  f00893d4       049f7683  60
+```
+
+[vaultenv]: /vault/docs/commands#environment-variables
+[nomad_acl_vault_wid_migrate]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
diff --git a/content/nomad/v1.9.x/content/docs/commands/status.mdx b/content/nomad/v1.9.x/content/docs/commands/status.mdx
new file mode 100644
index 0000000000..8ebec5e9d5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/status.mdx
@@ -0,0 +1,146 @@
+---
+layout: docs
+page_title: 'nomad status command reference'
+description: |
+  The `nomad status` command display the status output for any Nomad resource.
+---
+
+# `nomad status` command reference
+
+The `status` command displays the status output for any Nomad resource.
+
+## Usage
+
+```plaintext
+nomad status [options] <identifier>
+```
+
+The status command accepts any Nomad identifier or identifier prefix as its sole
+argument. The command detects the type of the identifier and routes to the
+appropriate status command to display more detailed output.
+
+If the ID is omitted, the command lists out all of the existing jobs. This is
+for backwards compatibility and should not be relied on.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Examples
+
+Display the status of a job:
+
+```shell-session
+$ nomad status example
+ID            = example
+Name          = example
+Submit Date   = 08/28/17 23:01:39 UTC
+Type          = service
+Priority      = 50
+Datacenters   = dc1
+Status        = running
+Periodic      = false
+Parameterized = false
+
+Summary
+Task Group  Queued  Starting  Running  Failed  Complete  Lost
+cache       0       0         1        0       0         0
+
+Latest Deployment
+ID          = f5506391
+Status      = running
+Description = Deployment is running
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       0        0
+
+Actions
+Action Name     Task Group  Task
+my-action       cache       my-task
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
+
+Display the status of an allocation:
+
+```shell-session
+$ nomad status e1d14a39
+ID                  = e1d14a39
+Eval ID             = cc882755
+Name                = example.cache[0]
+Node ID             = f9dabe93
+Job ID              = example
+Job Version         = 0
+Client Status       = running
+Client Description  = <none>
+Desired Status      = run
+Desired Description = <none>
+Created At          = 08/28/17 23:01:39 UTC
+Deployment ID       = f5506391
+Deployment Health   = healthy
+
+Task "redis" is "running"
+Task Resources
+CPU        Memory           Disk     Addresses
+4/500 MHz  6.3 MiB/256 MiB  300 MiB  db: 127.0.0.1:21752
+
+Task Events:
+Started At     = 08/28/17 23:01:39 UTC
+Finished At    = N/A
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                   Type        Description
+08/28/17 23:01:39 UTC  Started     Task started by client
+08/28/17 23:01:39 UTC  Task Setup  Building Task Directory
+08/28/17 23:01:39 UTC  Received    Task received by client
+```
+
+Display the status of a deployment:
+
+```shell-session
+$ nomad status f5506391
+ID          = f5506391
+Job ID      = example
+Job Version = 0
+Status      = successful
+Description = Deployment completed successfully
+
+Deployed
+Task Group  Desired  Placed  Healthy  Unhealthy
+cache       1        1       1        0
+```
+
+Display the status of a node:
+
+```shell-session
+$ nomad status f9dabe93
+ID      = f9dabe93
+Name    = nomad-server01
+Class   = <none>
+DC      = dc1
+Drain   = false
+Status  = ready
+Drivers = docker,exec,java,qemu,raw_exec,rkt
+Uptime  = 4h17m24s
+
+Allocated Resources
+CPU           Memory           Disk
+500/8709 MHz  256 MiB/2.0 GiB  300 MiB/24 GiB
+
+Allocation Resource Utilization
+CPU         Memory
+3/8709 MHz  6.3 MiB/2.0 GiB
+
+Host Resource Utilization
+CPU           Memory           Disk
+116/8709 MHz  335 MiB/2.0 GiB  12 GiB/38 GiB
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created At
+e1d14a39  f9dabe93  cache       0        run      running  08/28/17 23:01:39 UTC
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/system/gc.mdx b/content/nomad/v1.9.x/content/docs/commands/system/gc.mdx
new file mode 100644
index 0000000000..4221bee069
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/system/gc.mdx
@@ -0,0 +1,46 @@
+---
+layout: docs
+page_title: 'nomad system gc command reference'
+description: |
+  The `nomad system gc` command runs the system garbage collection process on jobs, evaluations, allocations, and nodes.
+---
+
+# `nomad system gc` command reference
+
+Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
+This is an asynchronous operation.
+
+Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
+The exact garbage collection logic varies by object, but in general Nomad only
+permanently deletes objects once they are terminal and no longer needed for
+future scheduling decisions. See [`gc` related server agent configuration
+parameters][gc_params] for details on tuning periodic garbage collection.
+
+[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
+
+The `system gc` command bypasses these settings and immediately attempts to
+garbage collect dead objects regardless of any "threshold" or "interval" server
+settings. This is useful to quickly free memory on servers running low, but
+users should prefer tuning periodic garbage collection parameters to meet their
+needs instead of relying on manually running `system gc`.
+
+## Usage
+
+```plaintext
+nomad system gc [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system gc command does not output unless an error occurs:
+
+```shell-session
+$ nomad system gc
+
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/system/index.mdx b/content/nomad/v1.9.x/content/docs/commands/system/index.mdx
new file mode 100644
index 0000000000..d9f195d505
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/system/index.mdx
@@ -0,0 +1,24 @@
+---
+layout: docs
+page_title: 'nomad system command reference'
+description: |
+  The `nomad system` commands run garbage collection and reconcile job summaries.
+---
+
+# `nomad system` command reference
+
+The `system` command is used to interact with the system API. These calls are
+used for system maintenance and should not be necessary for most users.
+
+## Usage
+
+Usage: `nomad system <subcommand> [options]`
+
+Run `nomad system <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`system gc`][gc] - Run the system garbage collection process
+- [`system reconcile summaries`][reconcile-summaries] - Reconciles the summaries of all registered jobs
+
+[gc]: /nomad/docs/commands/system/gc 'Run the system garbage collection process'
+[reconcile-summaries]: /nomad/docs/commands/system/reconcile-summaries 'Reconciles the summaries of all registered jobs'
diff --git a/content/nomad/v1.9.x/content/docs/commands/system/reconcile-summaries.mdx b/content/nomad/v1.9.x/content/docs/commands/system/reconcile-summaries.mdx
new file mode 100644
index 0000000000..7404babd87
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/system/reconcile-summaries.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: 'nomad system reconcile summaries command reference'
+description: |
+  The `nomad system reconcile summaries` command reconciles the summaries of all registered jobs.
+---
+
+# `nomad system reconcile summaries` command reference
+
+Reconciles the summaries of all registered jobs.
+
+## Usage
+
+```plaintext
+nomad system reconcile summaries [options]
+```
+
+If ACLs are enabled, this option requires a management token.
+
+## General options
+
+@include 'general_options_no_namespace.mdx'
+
+## Examples
+
+Running the system reconcile summaries command does not output unless an error
+occurs:
+
+```shell-session
+$ nomad system reconcile summaries
+
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/tls/ca-create.mdx b/content/nomad/v1.9.x/content/docs/commands/tls/ca-create.mdx
new file mode 100644
index 0000000000..b3ea8ff0df
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/tls/ca-create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad tls ca create command reference'
+description: |
+  The `nomad tls ca create` command creates a certificate authority that you then use to create a self-signed certificate for Nomad Transport Layer Security (TLS) configuration.
+---
+
+# `nomad tls ca create` command reference
+
+Create is used to create a self signed Certificate Authority to be used for
+Nomad TLS setup.
+
+## Usage
+
+```plaintext
+nomad tls ca create [options]
+```
+
+## Options
+
+- `-additional-domain=<value>`: Add name constraints for the CA. The server will
+  reject certificates for DNS names other than those specified in `-domain` and
+  `-additional-domain`. Can be used multiple times. This option can only used in
+  combination with `-domain` and `-name-constraint`.
+
+- `-common-name`: Common Name of CA. Defaults to Nomad Agent CA.
+
+- `-country`: Country of the CA. Defaults to "US".
+
+- `-days=<int>`: Provide number of days the CA is valid for from now on,
+  defaults to 5 years.
+
+- `-domain=<string>`: Domain of nomad cluster. Only used in combination with
+  `-name-constraint`. Defaults to `nomad`.
+
+- `-locality`: Locality of the CA. Defaults to "San Francisco".
+
+- `-name-constraint`: Add name constraints for the CA. Results in rejecting
+  certificates for other DNS than specified. If set to true, "localhost" and
+  `-domain` will be added to the allowed DNS. Defaults to false.
+
+~> **Warning:** If `-name-constraint` is enabled and you intend to serve the
+  Nomad web UI over HTTPS its DNS must be added with `additional-domain`. It is
+  not possible to add that after the fact.
+
+- `-organization`: Organization of the CA. Defaults to "HashiCorp Inc.".
+
+- `-organizational-unit`: Organizational Unit of the CA. Defaults to "Nomad".
+
+- `-postal-code`: Postal Code of the CA. Defaults to "94105".
+
+- `-province`: Province of the CA. Defaults to "CA".
+
+- `-street-address`: Street Address of the CA. Defaults to "101 Second Street".
+
+## Example
+
+Create CA:
+
+```shell-session
+$ nomad tls ca create
+==> CA Certificate saved to: nomad-agent-ca.pem
+==> CA Certificate key saved to: nomad-agent-ca-key.pem
+```
+
+Create a CA with a specified domain:
+
+```shell-session
+$ nomad tls ca create -name-constraint="true" -domain="foo.com"
+==> CA Certificate saved to: foo.com-agent-ca.pem
+==> CA Certificate key saved to: foo.com-agent-ca-key.pem
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/tls/ca-info.mdx b/content/nomad/v1.9.x/content/docs/commands/tls/ca-info.mdx
new file mode 100644
index 0000000000..edb0c805fc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/tls/ca-info.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad tls ca info command reference'
+description: |
+  The `nomad tls ca info` command displays serial number, issuer, name, expiration date, and permitted DNS domains for the provided certificate authority (CA) file.
+---
+
+# `nomad tls ca info` command reference
+
+Info is used to display relevant information that is contained within the
+provided certificate file.
+
+## Usage
+
+```plaintext
+nomad tls ca info <CA file>
+```
+
+## Example
+
+Display default CA:
+
+```shell-session
+$ nomad tls ca info nomad-agent-ca.pem
+Serial Number          314623649437549144006237783956683542664
+Issuer CN              Nomad Agent CA 314623649437549144006237783956683542664
+Common Name            CN=Nomad Agent CA 314623649437549144006237783956683542664,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:37:38 +0000 UTC
+Permitted DNS Domains  []
+```
+
+Display CA with a custom domain "foo.com":
+
+```shell-session
+$ nomad tls ca info foo.com-agent-ca.pem
+Serial Number          189027561135335847320487296530900061259
+Issuer CN              Nomad Agent CA 189027561135335847320487296530900061259
+Common Name            CN=Nomad Agent CA 189027561135335847320487296530900061259,O=HashiCorp Inc.,POSTALCODE=94105,STREET=101 Second Street,L=San Francisco,ST=CA,C=US
+Expiry Date            2027-11-13 21:38:15 +0000 UTC
+Permitted DNS Domains  [foo.com localhost]
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/tls/cert-create.mdx b/content/nomad/v1.9.x/content/docs/commands/tls/cert-create.mdx
new file mode 100644
index 0000000000..7927d484d4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/tls/cert-create.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: 'nomad tls cert create command reference'
+description: |
+  The `nomad tls cert create` command creates a server, client, or command-line interface (CLI) certificate for Transport Layer Security (TLS) configuration in your Nomad cluster.
+---
+
+# `nomad tls cert create` command reference
+
+The `tls cert create` command is used to create certificates to be used for
+[TLS encryption][] for your Nomad cluster. You can then copy these to your
+servers and clients. This command will not automatically update the
+configuration of the agents.
+
+## Usage
+
+Usage: `nomad tls cert create [options]`
+
+#### Options
+
+- `-additional-dnsname=<string>`: Provide an additional dnsname for Subject
+  Alternative Names. `localhost` is always included. This flag may be provided
+  multiple times.
+
+- `-additional-ipaddress=<string>`: Provide an additional ipaddress for Subject
+  Alternative Names. `127.0.0.1` is always included. This flag may be provided
+  multiple times.
+
+- `-ca=<string>`: Provide path to the ca. Defaults to `#DOMAIN#-agent-ca.pem`.
+
+- `-cli`: Generate cli certificate.
+
+- `-client`: Generate client certificate.
+
+- `-days=<int>`: Provide number of days the certificate is valid for from now
+  on. Defaults to 1 year.
+
+- `-cluster-region=<string>`: DEPRECATED please use `-region`.
+
+- `-domain=<string>`: Provide the domain. Matters only for `-server`
+  certificates.
+
+- `-key=<string>`: Provide path to the key. Defaults to
+  `#DOMAIN#-agent-ca-key.pem`.
+
+- `-region=<string>`: Provide the region. Defaults to "global".
+
+- `-server`: Generate server certificate.
+
+## Examples
+
+Create a certificate for servers:
+
+```shell-session
+$ nomad tls cert create -server
+==> WARNING: Server Certificates grants authority to become a
+    server and access all state in the cluster including root keys
+    and all ACL tokens. Do not distribute them to production hosts
+    that are not server nodes. Store them as securely as CA keys.
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Server Certificate saved to global-server-nomad.pem
+==> Server Certificate key saved to global-server-nomad-key.pem
+```
+
+Create a certificate for clients:
+
+```shell-session
+$ nomad tls cert create -client
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Client Certificate saved to global-client-nomad.pem
+==> Client Certificate key saved to global-client-nomad-key.pem
+```
+
+Create a certificate for the CLI:
+
+```shell-session
+$ nomad tls cert create -cli
+==> Using CA file nomad-agent-ca.pem and CA key nomad-agent-ca-key.pem
+==> Cli Certificate saved to global-cli-nomad.pem
+==> Cli Certificate key saved to global-cli-nomad-key.pem
+```
+
+[TLS encryption]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.9.x/content/docs/commands/tls/cert-info.mdx b/content/nomad/v1.9.x/content/docs/commands/tls/cert-info.mdx
new file mode 100644
index 0000000000..12f55e71e6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/tls/cert-info.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'nomad tls cert info command reference'
+description: |
+  The `nomad tls cert info` command displays serial number, issuer, name, expiration date, DNS names, and IP address from a specified certificate file.
+---
+
+# `nomad tls cert info` command reference
+
+Info is used to display relevant information that is contained within a provided
+certificate file.
+
+## Usage
+
+```plaintext
+nomad tls cert info <certificate file>
+```
+
+## Examples
+
+Display default certificate info:
+
+```shell-session
+$ nomad tls cert info global-cli-nomad.pem
+Serial Number  307777061759235334129808343588809897525
+Issuer CN      Nomad Agent CA 314623649437549144006237783956683542664
+Common Name    CN=cli.global.nomad
+Expiry Date    2023-11-14 21:40:45 +0000 UTC
+DNS Names      [cli.global.nomad localhost]
+IP Addresses   []
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/tls/index.mdx b/content/nomad/v1.9.x/content/docs/commands/tls/index.mdx
new file mode 100644
index 0000000000..55667194d0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/tls/index.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: 'nomad tls command reference'
+description: |
+  The `nomad tls` command creates and displays information about a certificate authority and self-signed certificate for Nomad's Transport Security Layer (TLS).
+---
+
+# `nomad tls` command reference
+
+The `tls` command is used to help with setting up a self signed CA and certificates for Nomad TLS.
+
+## Usage
+
+Usage: `nomad tls <subcommand> <subcommand> [options]`
+
+Run `nomad tls <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`ca create`][cacreate] - Create Certificate Authority
+- [`ca info`][cainfo] - Display information from a CA certificate
+- [`cert create`][certcreate] - Create self signed certificates
+- [`cert info`][certinfo] - Display information from a certificate
+
+[cacreate]: /nomad/docs/commands/tls/ca-create 'Create Certificate Authority'
+[cainfo]: /nomad/docs/commands/tls/ca-info 'Display information from a CA certificate'
+[certcreate]: /nomad/docs/commands/tls/cert-create 'Create self signed certificates'
+[certinfo]: /nomad/docs/commands/tls/cert-info 'Display information from a certificate'
diff --git a/content/nomad/v1.9.x/content/docs/commands/ui.mdx b/content/nomad/v1.9.x/content/docs/commands/ui.mdx
new file mode 100644
index 0000000000..e73157de63
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/ui.mdx
@@ -0,0 +1,76 @@
+---
+layout: docs
+page_title: 'nomad ui command reference'
+description: |
+  The `nomad ui` command opens the Nomad Web UI. Provide a node, job, or allocation identifier to open that object's UI page in your browser. Authenticate with an access control list (ACL) token. Use the `show-url` flag to return the UI's URL.
+---
+
+# `nomad ui` command reference
+
+The `ui` command is used to open the Nomad Web UI.
+
+## Usage
+
+```plaintext
+nomad ui [options] <identifier>
+```
+
+The `ui` command can be called with no arguments, in which case the UI homepage
+will be opened in the default browser.
+
+An identifier may be provided, in which case the UI will be opened to view the
+details for that object. Supported identifiers are jobs, allocations and nodes.
+
+If ACLs are enabled, the web UI will start in an unauthenticated state and you
+may see a 403 Unauthorized page if anonymous read access is denied. The `nomad ui -authenticate` option will exchange your command line client's Nomad ACL
+token for a one-time token, which is passed to the web UI. That one-time token
+will be exchanged for your Nomad ACL token and stored in the browser's local
+storage for authentication.
+
+## General options
+
+@include 'general_options.mdx'
+
+## UI options
+
+- `-authenticate`: Exchange your Nomad ACL token for a one-time token in the
+  web UI.
+
+- `-show-url`: Show the Nomad UI URL instead of opening with the default browser.
+
+## Examples
+
+Open the UI homepage:
+
+```shell-session
+$ nomad ui
+Opening URL "http://127.0.0.1:4646"
+```
+
+Open the UI directly to look at a job:
+
+```shell-session
+$ nomad ui redis-job
+http://127.0.0.1:4646/ui/jobs/redis-job
+```
+
+Open the UI directly to look at an allocation:
+
+```shell-session
+$ nomad ui d4005969
+Opening URL "http://127.0.0.1:4646/ui/allocations/d4005969-b16f-10eb-4fe1-a5374986083d"
+```
+
+Open the UI and authenticate using your ACL token:
+
+```shell-session
+$ NOMAD_ACL_TOKEN=e9674b26-763b-4637-a28f-0df95c53cdda nomad ui -authenticate
+Opening URL "http://127.0.0.1:4646" with token
+```
+
+Show the UI URL without opening the browser:
+
+```shell-session
+$ nomad ui -show-url
+URL for web UI: http://127.0.0.1:4646
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/get.mdx b/content/nomad/v1.9.x/content/docs/commands/var/get.mdx
new file mode 100644
index 0000000000..d71ad72a10
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/get.mdx
@@ -0,0 +1,65 @@
+---
+layout: docs
+page_title: nomad var get reference
+description: |-
+  The `nomad var get` command retrieves the variable at the given path from
+  Nomad.
+---
+
+# `nomad var get` command reference
+
+The `var get` command is used to get the contents of an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var get [options] <path>
+```
+
+If ACLs are enabled, this command requires a token with the `variables:read`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Output options
+
+- `-item` `(string: "")`: Print only the value of the given item. Specifying
+   this option will take precedence over other formatting directives. The result
+   will not have a trailing newline making it ideal for piping to other
+   processes.
+
+- `-out` `(enum: go-template | hcl | json | none | table )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+Retrieve the variable stored at path "secret/creds":
+
+```shell-session
+$ nomad var get secret/creds
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Return only the "passcode" item from the variable stored at "secret/creds":
+
+```shell-session
+$ nomad var get -item=passcode secret/creds
+my-long-passcode
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/index.mdx b/content/nomad/v1.9.x/content/docs/commands/var/index.mdx
new file mode 100644
index 0000000000..c835f74ddf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/index.mdx
@@ -0,0 +1,66 @@
+---
+layout: docs
+page_title: nomad var reference
+description: |-
+  The `nomad var` commands interact with Nomad variables. Create a variable specification file. Insert, update, delete, or acquire a lock over a variable. Fetch and list variables.
+---
+
+# `nomad var` command reference
+
+The `var` command is used to interact with Nomad [variables].
+
+## Usage
+
+Usage: `nomad var <subcommand> [options] [args]`
+
+Run `nomad var <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`var init`][init] - Create a variable specification file
+- [`var list`][list] - List variables the user has access to
+- [`var get`][get] - Retrieve a variable
+- [`var put`][put] - Insert or update a variable
+- [`var purge`][purge] - Permanently delete a variable
+- [`var lock`][lock] - Acquire a lock over a variable
+
+## Examples
+
+Create or update the variable stored at the path "secret/creds", which contains
+an item named `passcode` with the value `my-long-passcode`.
+
+```shell-session
+$ nomad var put -out=table secret/creds passcode=my-long-passcode
+Successfully created variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+```
+
+Update a value:
+```shell-session
+$ nomad var get secret/creds | nomad var put -in=json -out=table -v - user=dba
+Reading whole JSON variable specification from stdin
+Successfully updated variable "secret/creds"!
+
+Namespace   = default
+Path        = secret/creds
+Create Time = 2022-08-23T11:14:37-04:00
+Check Index = 116
+
+Items
+passcode = my-long-passcode
+user     = dba
+```
+
+[variables]: /nomad/docs/concepts/variables
+[init]: /nomad/docs/commands/var/init
+[get]: /nomad/docs/commands/var/get
+[list]: /nomad/docs/commands/var/list
+[put]: /nomad/docs/commands/var/put
+[purge]: /nomad/docs/commands/var/purge
+[lock]: /nomad/docs/commands/var/lock
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/init.mdx b/content/nomad/v1.9.x/content/docs/commands/var/init.mdx
new file mode 100644
index 0000000000..17a6a4c9be
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/init.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: 'nomad var init command reference'
+description: |
+  The `nomad var init` command generates an example variable specification that you can customize for your Nomad variables.
+---
+
+# `nomad var init` command reference
+
+The `var init` creates an example variable specification file that can be used
+as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad var init <filename>
+```
+
+When no filename is supplied, a default filename of "spec.nv.hcl" or
+"spec.nv.json" will be used depending on the output format.
+
+## Init options
+
+- `-out` `(enum: hcl | json)`: Format of generated variable
+  specification. Defaults to `hcl`.
+
+- `-quiet`: Do not print success message.
+
+## Examples
+
+Create an example variable specification:
+
+```shell-session
+$ nomad var init
+Example variable specification written to spec.nv.hcl
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/list.mdx b/content/nomad/v1.9.x/content/docs/commands/var/list.mdx
new file mode 100644
index 0000000000..d14d32bea8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/list.mdx
@@ -0,0 +1,141 @@
+---
+layout: docs
+page_title: nomad var list reference
+description: |-
+  The `nomad var list` command displays data from Nomad's variables datastore at
+  or beginning with the given prefix.
+---
+
+# `nomad var list` command reference
+
+The `var list` command returns a list of [variable][] paths accessible to the
+current user, optionally filtered to paths containing a provided prefix. Do not
+encode sensitive information in variable paths. The variable's items are not
+accessible via this command.
+
+When using pagination, the next page token is provided as part of the output of
+the command. When the output format is JSON, the returned variable list is
+wrapped with additional metadata that contains the next page token. For non-JSON
+output, the next page token is printed as a message to standard error and
+standard output contains the variables from the specifically requested page.
+
+
+## Usage
+
+```plaintext
+nomad var list [options] [<prefix>]
+```
+
+If ACLs are enabled, this command requires the `variables:list` capability for
+the namespaces and paths containing the variables to list. See the [ACL policy][]
+documentation for details.
+
+## General options
+
+@include 'general_options.mdx'
+
+## List options
+
+- `-per-page` `(int: <unset>)`: How many results to show per page.
+
+- `-page-token` `(string: "")`: Where to start pagination.
+
+- `-filter` `(string: "")`: Specifies an expression used to filter query
+  results. Queries using this option are less efficient than using the prefix
+  parameter; therefore, the prefix parameter should be used whenever possible.
+
+- `-out` `(enum: go-template | json | table | terse )`: Format to render the
+  variable in. When using "go-template", you must provide the template content
+  with the `-template` option. Defaults to "table" when stdout is a terminal and
+  to "json" when stdout is redirected.
+
+- `-template` `(string: "")` Template to render output with. Required when
+  output is "go-template".
+
+## Examples
+
+List values under the key "nomad/jobs":
+
+```shell-session
+$ nomad var list nomad/jobs
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+List values under the key "nomad/jobs/variable/www" in JSON format:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" nomad/jobs/variable/www
+[
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www",
+    "CreateIndex": 1457,
+    "ModifyIndex": 1457,
+    "CreateTime": 1662061225600373000,
+    "ModifyTime": 1662061225600373000
+  },
+  {
+    "Namespace": "default",
+    "Path": "nomad/jobs/variable/www/nginx",
+    "CreateIndex": 800,
+    "ModifyIndex": 1000,
+    "CreateTime": 1662061717905426000,
+    "ModifyTime": 1662062162982630000
+  }
+]
+```
+
+Perform a paginated query:
+
+```shell-session
+$ nomad var list -per-page=3
+Namespace  Path                           Last Updated
+default    nomad/jobs/example             2022-08-23T10:35:47-04:00
+default    nomad/jobs/variable            2022-08-23T10:24:45-04:00
+default    nomad/jobs/variable/www        2022-08-23T10:24:45-04:00
+Next page token: default.nomad/jobs/variable/www/nginx
+```
+
+To fetch the next page :
+
+```shell-session
+$ nomad var list -per-page=3 \
+  -page-token=default.nomad/jobs/variable/www/nginx
+Namespace  Path                 Last Updated
+default    nomad/jobs/variable/www/nginx  2022-08-23T10:24:46-04:00
+```
+
+Perform a paginated query with JSON formatting:
+
+```shell-session
+$ nomad var list -out=json -namespace="*" -per-page=1 nomad/jobs/variable/www
+{
+    "Data": [
+        {
+           "Namespace": "default",
+            "Path": "nomad/jobs/variable/www",
+            "CreateIndex": 1457,
+            "ModifyIndex": 1457,
+            "CreateTime": 1662061225600373000,
+            "ModifyTime": 1662061225600373000
+        }
+    ],
+    "QueryMeta": {
+        "KnownLeader": true,
+        "LastContact": 0,
+        "LastIndex": 43,
+        "NextToken": "default.nomad/jobs/variable/www/nginx",
+        "RequestTime": 875792
+    }
+}
+```
+
+As with the tabular version, provide the `QueryMeta.NextToken` value as the
+`-page-token` value to fetch the next page.
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/lock.mdx b/content/nomad/v1.9.x/content/docs/commands/var/lock.mdx
new file mode 100644
index 0000000000..4e9ba5ad0d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/lock.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: nomad var lock reference
+description: |-
+  The `nomad var lock` command locks a variable, only allowing the lock owner to modify it.
+---
+
+# `nomad var lock` command reference
+
+The `var lock` command holds a lock on a [variable][].
+
+## Usage
+
+```plaintext
+nomad var lock [options] <lock spec file reference> child...
+nomad var lock [options] <path to store variable> [<variable spec file reference>] child
+```
+
+The lock command provides a mechanism for simple distributed locking. A lock
+is created in the given variable, and only when held, is a child process invoked.
+
+The lock command can be called on an existing variable or an entire new variable
+specification can be provided to the command from a file by using an
+@-prefixed path to a variable specification file. Items to be stored in the
+variable can be supplied using the specification file as well.
+
+Nomad lock launches its children in a shell. By default, Nomad will use the
+shell defined in the environment variable SHELL. If SHELL is not defined,
+it will default to /bin/sh. It should be noted that not all shells terminate
+child processes when they receive SIGTERM. Under Ubuntu, /bin/sh is linked
+to dash, which does not terminate its children. In order to ensure that
+child processes are killed when the lock is lost, be sure to set the SHELL
+environment variable appropriately, or run without a shell by setting -shell=false.
+
+If [ACLs][] are enabled, this command requires the 'variables:write' capability
+for the destination namespace and path.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Lock options
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+- `ttl`: Optional, TTL for the lock, time the variable will be locked. Defaults to 15s.
+
+- `delay`: Optional, time the variable is blocked from locking when a lease is not renewed.
+	Defaults to 15s.
+
+- `max-retry`:Optional, max-retry up to this number of times if Nomad returns a 500 error
+	while monitoring the lock. This allows riding out brief periods of
+	unavailability without causing leader elections, but increases the amount of
+	time required to detect a lost lock in some cases. Defaults to 5. Set to 0 to
+	disable.
+
+- `shell`: Optional, use a shell to run the command (can set a custom shell via
+	the SHELL environment variable). The default value is true.
+
+## Examples
+
+Attempts to acquire a lock over the variable at path "secret/creds" for a time of
+15s and executes  `nomad job run webapp.nomad.hcl` if it succeeds:
+
+```shell-session
+$ nomad var lock -ttl=15s secret/creds "nomad job run webapp.nomad.hcl"
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var lock secret/foo @spec.nv.json `nomad job run webapp.nomad.hcl`
+```
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]:  /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
+[ACL]: /nomad/docs/other-specifications/acl-policy#variables
+
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/purge.mdx b/content/nomad/v1.9.x/content/docs/commands/var/purge.mdx
new file mode 100644
index 0000000000..55ecf7a4e1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/purge.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: nomad var purge reference
+description: |-
+  The `nomad var purge` command permanently removes the specified variable
+  from Nomad.
+---
+
+# `nomad var purge` command reference
+
+The `var purge` command permanently deletes an existing [variable][] from Nomad's
+variable storage.
+
+## Usage
+
+```plaintext
+nomad var purge [options] <path>
+```
+
+The `var purge` command requires the path to the variable.
+
+If ACLs are enabled, this command requires a token with the `variables:destroy`
+capability for the target variable's namespace and path. See the [ACL policy][]
+documentation for details.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Command options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+## Examples
+
+Purge the variable at the "secret/creds" path.
+
+```shell-session
+$ nomad var purge -y secret/creds
+Successfully purged variable "secret/creds"!
+```
+
+[variable]: /nomad/docs/concepts/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
diff --git a/content/nomad/v1.9.x/content/docs/commands/var/put.mdx b/content/nomad/v1.9.x/content/docs/commands/var/put.mdx
new file mode 100644
index 0000000000..f5cc5c6511
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/var/put.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: nomad var put reference
+description: |-
+  The `nomad var put` command creates or updates a Nomad variable.
+---
+
+# `nomad var put` command reference
+
+The `var put` command creates or updates an existing [variable][].
+
+## Usage
+
+```plaintext
+nomad var put [options] <variable spec file reference> [<key>=<value>]...
+nomad var put [options] <path to store variable> [<variable spec file reference>] [<key>=<value>]...
+```
+
+Variable metadata and items can be supplied using a [variable
+specification][varspec], by using command arguments, or by a combination of the
+two techniques. An entire variable specification can be provided to the command
+via standard input (stdin) by setting the first argument to "-" or from a file
+by using an @-prefixed path to a variable specification file. When providing
+variable data via stdin, you must provide the `-in` flag with the format of the
+specification, which must be either "hcl" or "json".
+
+Items to be stored in the variable can be supplied using the specification, as a
+series of key-value pairs, or both. The value for a key-value pair can be a
+string, an @-prefixed file reference, or a '-' to get the value from stdin. Item
+values provided from file references or stdin are consumed as-is with no
+additional processing and do not require the input format to be specified.
+
+Values supplied as command line arguments supersede values provided in any
+variable specification piped into the command or loaded from file. If ACLs are
+enabled, this command requires the `variables:write` capability for the
+destination namespace and path. See the [ACL policy][] documentation for
+details.
+
+## Restrictions
+
+Variable paths are restricted to [RFC3986][] URL-safe characters that don't
+conflict with the use of the characters `@` and `.` in template blocks. This
+includes alphanumeric characters and the special characters `-`, `_`, `~`, and
+`/`. Paths may be up to 128 bytes long. The following regex matches the allowed
+paths: `^[a-zA-Z0-9-_~/]{1,128}$`
+
+The keys for the items in a variable may contain any character, but keys
+containing characters outside the set of Unicode letters, Unicode digits, and
+the underscore (`_`) can not be read directly using dotted references in Nomad's
+template engine. Instead, they require the use of the `index` template function
+to directly access their values. This does not impact cases where the keys and
+values are read using the `range` function.
+
+Variable items are restricted to 64KiB in size. This limit is calculated by
+taking the sum of the length in bytes of all of the unencrypted keys and values.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Put options
+
+- `-check-index` `(int: <unset>)`: If set, the variable is only acted upon if
+  the server-side version's index matches the provided value. When a variable
+  specification contains a modify index, that modify index is used as the
+  check-index for the check-and-set operation and can be overridden using this
+  flag.
+
+- `-force`: Perform this operation regardless of the state or index of the
+  variable on the server-side.
+
+- `-in` `(enum: hcl | json)`: Parser to use for data supplied via standard input
+  or when the variable specification's type can not be known using the file
+  extension. Defaults to "json".
+
+- `-out` `(enum: go-template | hcl | json | none | table)`: Format to render
+  created or updated variable. Defaults to "none" when stdout is a terminal and
+  "json" when the output is redirected.
+
+- `-template` `(string: "")`: Template to render output with. Required when
+  format is "go-template", invalid for other formats.
+
+- `-verbose`: Provides additional information via standard error to preserve
+  standard output (stdout) for redirected output.
+
+## Examples
+
+Writes the data to the path "secret/creds":
+
+```shell-session
+$ nomad var put secret/creds passcode=my-long-passcode
+```
+
+The data can also be consumed from a file on disk by prefixing with the "@"
+symbol. For example, you can store a variable using a specification created with
+the `nomad var init` command.
+
+```shell-session
+$ nomad var put secret/foo @spec.nv.json
+```
+
+Or it can be read from standard input using the "-" symbol:
+
+```shell-session
+$ echo "abcd1234" | nomad var put secret/foo bar=-
+```
+
+
+[variable]: /nomad/docs/concepts/variables
+[varspec]: /nomad/docs/other-specifications/variables
+[ACL Policy]: /nomad/docs/other-specifications/acl-policy#variables
+[RFC3986]: https://www.rfc-editor.org/rfc/rfc3986#section-2
diff --git a/content/nomad/v1.9.x/content/docs/commands/version.mdx b/content/nomad/v1.9.x/content/docs/commands/version.mdx
new file mode 100644
index 0000000000..eec3c9c626
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/version.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad version command reference'
+description: |
+  The `nomad version` command displays the version, build date, and revision information for a Nomad installation.
+---
+
+# `nomad version` command reference
+
+The `version` command displays build information about the running binary,
+including the release version, build date, and the exact revision.
+
+## Usage
+
+```plaintext
+nomad version
+```
+
+## Output
+
+This command prints the version number and info about the git commit that was
+used to build the binary. `BuildDate` is when the commit was made,
+and `Revision` is the exact commit SHA.
+
+The SHA may also have the string `+CHANGES` appended to the end,
+indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad version
+Nomad v1.5.0
+BuildDate 2023-02-17T19:29:26Z
+Revision a536284ebcfb4ff26065955abae446d81cc92b87+CHANGES
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/create.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/create.mdx
new file mode 100644
index 0000000000..4d57183d7f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/create.mdx
@@ -0,0 +1,72 @@
+---
+layout: docs
+page_title: 'nomad volume create command reference'
+description: |
+  Create volumes with CSI plugins.
+---
+
+# `nomad volume create` command reference
+
+The `volume create` command creates external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [registered] when it is successfully created.
+
+## Usage
+
+```plaintext
+nomad volume create [options] [file]
+```
+
+The `volume create` command requires a single argument, specifying the path to
+a file containing a valid [volume specification][volume_specification]. This
+file will be read and the volume will be submitted to Nomad for scheduling. If
+the supplied path is "-", the volume file is read from STDIN. Otherwise it is
+read from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="plugin_id" />
+<span id="snapshot_id" />
+<span id="clone_id" />
+<span id="capacity_min" />
+<span id="capacity_max" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[registered]: /nomad/docs/commands/volume/register
+[volume_specification]: /nomad/docs/other-specifications/volume
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/delete.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/delete.mdx
new file mode 100644
index 0000000000..48aa773648
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/delete.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: 'nomad volume delete command reference'
+description: |
+  Delete volumes with CSI plugins.
+---
+
+# `nomad volume delete` command reference
+
+The `volume delete` command deletes external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command. The volume will also be [deregistered] when it is successfully
+deleted.
+
+## Usage
+
+```plaintext
+nomad volume delete [options] [volume]
+```
+
+The `volume delete` command requires a single argument, specifying the ID of
+volume to be deleted. The volume must still be [registered] with Nomad in
+order to be deleted. Deleting will fail if the volume is still in use by an
+allocation or in the process of being unpublished. If the volume no longer
+exists, this command will silently return without an error.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[deregistered]: /nomad/docs/commands/volume/deregister
+[registered]: /nomad/docs/commands/volume/register
+
+## Delete Options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/deregister.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/deregister.mdx
new file mode 100644
index 0000000000..3a7d71645e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/deregister.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: 'nomad volume deregister command reference'
+description: |
+  Deregister volumes with CSI plugins.
+---
+
+# `nomad volume deregister` command reference
+
+The `volume deregister` command deregisters external storage volumes with
+Nomad's [Container Storage Interface (CSI)][csi] support. The volume will be
+removed from Nomad's state store but not deleted from the external storage
+provider. Note that deregistering a volume prevents Nomad from deleting it via
+[`volume delete`] at a later time.
+
+## Usage
+
+```plaintext
+nomad volume deregister [options] [volume]
+```
+
+The `volume deregister` command requires a single argument, specifying
+the ID of volume to be deregistered. Deregistration will fail if the
+volume is still in use by an allocation or in the process of being
+unpublished.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Deregister options
+
+- `-force`: Force deregistration of the volume and immediately drop claims for
+  terminal allocations. Returns an error if the volume has running
+  allocations. This does not detach the volume from client nodes.
+
+[csi]: https://github.com/container-storage-interface/spec
+[`volume delete`]: /nomad/docs/commands/volume/delete
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/detach.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/detach.mdx
new file mode 100644
index 0000000000..ed3c39ecd1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/detach.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'nomad volume detach command reference'
+description: |
+  The `nomad volume detach` command detaches external storage volumes with Container Storage Interface (CSI) plugins.
+---
+
+# `nomad volume detach` command reference
+
+The `volume detach` command detaches external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support.
+
+## Usage
+
+```plaintext
+nomad volume detach [options] [volume] [node]
+```
+
+The `volume detach` command requires two arguments, specifying the ID of the
+volume to be detached and the node to detach it from. Detaching will fail if
+the volume is still in use by an allocation.
+
+Note that you can use a node ID prefix just as you can with other Nomad
+commands, but if the node has been garbage collected, you may need to pass the
+full node ID.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` and `csi-read-volume` capabilities for the volume's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+[csi]: https://github.com/container-storage-interface/spec
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/index.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/index.mdx
new file mode 100644
index 0000000000..695f40fd48
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/index.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: 'nomad volume command reference'
+description: |
+  The `nomad volume` command interacts with volumes. Generate an example volume specification. Create, delete, register, and deregister a volume. Create and delete a volume snapshot. Display a list of volumes and status information for a single volume.
+---
+
+# `nomad volume` command reference
+
+The `volume` command is used to interact with volumes.
+
+## Usage
+
+Usage: `nomad volume <subcommand> [options]`
+
+Run `nomad volume <subcommand> -h` for help on that subcommand. The following
+subcommands are available:
+
+- [`volume create`][create] - Create a volume.
+- [`volume delete`][delete] - Delete a volume.
+- [`volume deregister`][deregister] - Deregister a volume.
+- [`volume detach`][detach] - Detach a volume.
+- [`volume init`][init] - Create an example volume specification file.
+- [`volume register`][register] - Register a volume.
+- [`volume snapshot create`][snapshot-create] - Create a volume snapshot.
+- [`volume snapshot delete`][snapshot-delete] - Delete a volume snapshot.
+- [`volume snapshot list`][snapshot-list] - List all volume snapshots.
+- [`volume status`][status] - Display status information about a volume.
+
+[create]: /nomad/docs/commands/volume/create
+[delete]: /nomad/docs/commands/volume/delete
+[deregister]: /nomad/docs/commands/volume/deregister 'Deregister a volume'
+[detach]: /nomad/docs/commands/volume/detach 'Detach a volume'
+[init]: /nomad/docs/commands/volume/init 'Create an example volume specification file'
+[register]: /nomad/docs/commands/volume/register 'Register a volume'
+[snapshot-create]: /nomad/docs/commands/volume/snapshot-create
+[snapshot-delete]: /nomad/docs/commands/volume/snapshot-delete
+[snapshot-list]: /nomad/docs/commands/volume/snapshot-list
+[status]: /nomad/docs/commands/volume/status 'Display status information about a volume'
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/init.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/init.mdx
new file mode 100644
index 0000000000..28dda609cd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/init.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: 'nomad volume init command reference'
+description: |
+  Generate an example volume specification.
+---
+
+# `nomad volume init` command reference
+
+The `volume init` command is used to create an example volume specification
+file that can be used as a starting point to customize further.
+
+## Usage
+
+```plaintext
+nomad volume init
+```
+
+## Init options
+
+- `-json`: Create an example JSON volume specification.
+
+## Examples
+
+Create an example volume specification:
+
+```shell-session
+$ nomad volume init
+Example volume specification written to volume.hcl
+```
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/register.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/register.mdx
new file mode 100644
index 0000000000..3165b1811a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/register.mdx
@@ -0,0 +1,87 @@
+---
+layout: docs
+page_title: 'nomad volume register command reference'
+description: |
+  Register volumes with CSI plugins.
+---
+
+# `nomad volume register` command reference
+
+The `volume register` command registers external storage volumes with Nomad's
+[Container Storage Interface (CSI)][csi] support. The volume must exist on the
+remote storage provider before it can be registered and used by a task.
+
+CSI plugins that implement the [Controller][csi_plugins_internals] interface
+can be created via the [`volume create`] command, which will automatically
+register the volume as well.
+
+## Usage
+
+```plaintext
+nomad volume register [options] [file]
+```
+
+The `volume register` command requires a single argument, specifying the path
+to a file containing a valid [volume specification][volume_specification]. This
+file will be read and the job will be submitted to Nomad for scheduling. If the
+supplied path is "-", the job file is read from STDIN. Otherwise it is read
+from the file at the supplied path.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Volume Specification
+
+<!--
+Redirection rules are applied server-side, so we can't redirect these sections
+that used to be located in this page since they use URL fragments. Creating
+these hidden anchors will at least point users to the new page, although not to
+the exact section.
+-->
+
+<span id="volume-specification-parameters" />
+<span id="id" />
+<span id="namespace-1" />
+<span id="name" />
+<span id="type" />
+<span id="external_id" />
+<span id="plugin_id" />
+<span id="capability" />
+<span id="access_mode" />
+<span id="attachment_mode" />
+<span id="mount_options" />
+<span id="fs_type" />
+<span id="mount_flags" />
+<span id="topology_request" />
+<span id="secrets" />
+<span id="parameters" />
+<span id="context" />
+<span id="topology_request-parameters" />
+<span id="segments" />
+<span id="unused-fields" />
+
+The volume specification is documented in the [Volume
+Specification][volume_specification] page.
+
+Not all fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
+[volume_specification]: /nomad/docs/other-specifications/volume
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-create.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-create.mdx
new file mode 100644
index 0000000000..1ca3958a2d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-create.mdx
@@ -0,0 +1,68 @@
+---
+layout: docs
+
+page_title: 'nomad volume snapshot create command reference'
+description: |
+  The `nomad volume snapshot create` command creates a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot create` command reference
+
+The `volume snapshot create` command creates a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot create [volume] [snapshot_name]
+```
+
+The `volume snapshot create` command requires a volume ID or prefix. If there
+is an exact match based on the provided volume ID or prefix, then the specific
+volume is snapshotted. Otherwise, a list of matching volumes and information
+will be displayed. The volume must still be [registered] with Nomad in order
+to be snapshotted.
+
+If an optional snapshot name is provided, the argument will be passed to the
+CSI plugin to be used as the ID of the resulting snapshot. Not all plugins
+accept this name and it may be ignored.
+
+When ACLs are enabled, this command requires a token with the
+`csi-write-volume` capability for the volume's namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Snapshot create options
+
+- `-parameter`: Parameters to pass to the plugin to create a
+  snapshot. Accepts multiple flags in the form `-parameter key=value`
+
+- `-secret`: Secrets to pass to the plugin to create a snapshot. Accepts
+  multiple flags in the form `-secret key=value`
+
+- `-verbose`: Display full information for the resulting snapshot.
+
+## Examples
+
+Snapshot a volume:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+Snapshot a volume with a suggested snapshot ID:
+
+```shell-session
+$ nomad volume snapshot create ebs_prod_db1 snap-12345
+Completed snapshot of volume ebs_prod_db1 with snapshot ID snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-delete.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-delete.mdx
new file mode 100644
index 0000000000..3904959c88
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-delete.mdx
@@ -0,0 +1,49 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot delete command reference'
+description: |
+  The `nomad volume snapshot delete` command deletes a snapshot of an existing Container Storage Interface (CSI) volume.
+---
+
+# `nomad volume snapshot delete` command reference
+
+The `volume snapshot delete` command deletes a snapshot of an existing
+[Container Storage Interface (CSI)][csi] volume. Only CSI plugins that
+implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot delete [plugin_id] [snapshot_id]
+```
+
+The `volume snapshot delete` command requires both the plugin ID and the
+snapshot ID. The volume that was the source of the snapshot does not still
+need to be [registered] with Nomad in order to be deleted.
+
+When ACLs are enabled, this command requires a token with the `csi-write-
+volume` and `plugin:read` capabilities.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Snapshot delete options
+
+- `-secret`: Secrets to pass to the plugin to delete the
+  snapshot. Accepts multiple flags in the form `-secret key=value`
+
+## Examples
+
+Delete a volume snapshot:
+
+```shell-session
+$ nomad volume snapshot delete aws-ebs0 snap-12345
+Deleted snapshot snap-12345.
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-list.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-list.mdx
new file mode 100644
index 0000000000..895217da27
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/snapshot-list.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: 'nomad volume snapshot list command reference'
+description: |
+  The `nomad volume snapshot list` command displays a list external Container Storage Interface (CSI) volume snapshots along with the source volume ID as known to the external storage provider.
+---
+
+# `nomad volume snapshot list` command reference
+
+The `volume snapshot list` command lists volume snapshots known to a
+[Container Storage Interface (CSI)][csi] storage provider. Only CSI plugins
+that implement the [Controller][csi_plugins_internals] interface support this
+command.
+
+## Usage
+
+```plaintext
+nomad volume snapshot list [-plugin plugin_id -secrets key=value]
+```
+
+The `volume snapshot list` command returns a list of snapshots along with their
+source volume ID as known to the external storage provider. This is not the
+same as the Nomad volume ID, as the source volume may not be [registered] with
+Nomad.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Snapshot list options
+
+- `-page-token`: Where to start pagination.
+- `-per-page`: How many results to show per page.
+- `-plugin`: Display only snapshots managed by a particular [CSI
+  plugin][csi_plugin]. This flag is required and accepts a plugin ID
+  or prefix. If there is an exact match based on the provided plugin,
+  then that specific plugin will be queried. Otherwise, a list of
+  matching plugins will be displayed.
+- `-secret`: Secrets to pass to the plugin to list snapshots. Accepts
+  multiple flags in the form `-secret key=value`
+- `-verbose`: Display full information for the resulting snapshot.
+
+When ACLs are enabled, this command requires a token with the
+`csi-list-volumes` capability for the plugin's namespace.
+
+## Examples
+
+List volume snapshots for a plugin:
+
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+snap-67890   vol-fedcba   50GiB  2021-01-04T15:45:00Z  true
+```
+
+List volume snapshots with two secret key/value pairs:
+```shell-session
+$ nomad volume snapshot list -plugin aws-ebs0 -secret key1=value1 -secret key2=val2
+Snapshot ID  External ID  Size   Creation Time         Ready?
+snap-12345   vol-abcdef   50GiB  2021-01-03T12:15:02Z  true
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[registered]: /nomad/docs/commands/volume/register
+[csi_plugins_internals]: /nomad/docs/concepts/plugins/csi#csi-plugins
diff --git a/content/nomad/v1.9.x/content/docs/commands/volume/status.mdx b/content/nomad/v1.9.x/content/docs/commands/volume/status.mdx
new file mode 100644
index 0000000000..ff5bb33486
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/commands/volume/status.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: 'nomad volume status command reference'
+description: |
+  The `nomad volume status` command displays volume information and status for a single volume or a list of volumes.
+---
+
+# `nomad volume status` command reference
+
+The `volume status` command displays status information for [Container
+Storage Interface (CSI)][csi] volumes.
+
+## Usage
+
+```plaintext
+nomad volume status [options] [volume]
+```
+
+This command accepts an optional volume ID or prefix as the sole argument. If there
+is an exact match based on the provided volume ID or prefix, then information about
+the specific volume is queried and displayed. Otherwise, a list of matching volumes
+and information will be displayed.
+
+If the ID is omitted, the command lists out all of the existing volumes and a few
+of the most useful status fields for each.
+
+When ACLs are enabled, this command requires a token with the
+`csi-read-volume` and `csi-list-volumes` capability for the volume's
+namespace.
+
+## General options
+
+@include 'general_options.mdx'
+
+## Status options
+
+- `-type`: Display only volumes of a particular type. Currently only
+  the `csi` type is supported, so this option can be omitted when
+  querying the status of CSI volumes.
+
+- `-plugin_id`: Display only volumes managed by a particular [CSI
+  plugin][csi_plugin].
+
+- `-short`: Display short output. Used only when a single volume is
+  being queried. Drops verbose volume allocation data from the
+  output.
+
+- `-verbose`: Show full information. Allocation create and modify times are
+  shown in `yyyy/mm/dd hh:mm:ss` format. When listing volumes, this flag will
+  cause Nomad to query the storage provider for volumes that are known to the
+  storage provider but not yet registered with Nomad. This may include volumes
+  that have been created by the [`volume create`] command that are not yet
+  schedulable.
+
+## Examples
+
+List of all volumes:
+
+```shell-session
+$ nomad volume [-type csi] status
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+```
+
+List of all volumes, with external provider info:
+
+```shell-session
+$ nomad volume [-type csi] status -verbose
+ID            Name      Namespace  Plugin ID  Schedulable  Access Mode
+ebs_prod_db1  database  default    ebs-prod   true         single-node-writer
+
+External ID   Condition                         Nodes
+vol-abcedf    OK                                i-abc123f2,i-14a12df13
+vol-cd46df    Abnormal (provider message here)  i-14a12df13
+```
+
+Short view of a specific volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+```
+
+Full status information of a volume:
+
+```shell-session
+$ nomad volume status [-verbose] [-plugin=ebs-prod] ebs_prod_db1
+ID                   = ebs_prod_db1
+Name                 = database
+Type                 = csi
+External ID          = vol-23452345
+Plugin ID            = ebs-prod
+Provider             = aws.ebs
+Version              = 1.0.1
+Capacity             = 100 GiB
+Schedulable          = true
+Controllers Healthy  = 1
+Controllers Expected = 1
+Nodes Healthy        = 1
+Nodes Expected       = 1
+Access Mode          = single-node-writer
+Attachment Mode      = file-system
+Mount options        = fs_type: ext4 flags: ro
+Namespace            = default
+
+Allocations
+ID        Node ID   Access Mode   Task Group  Version  Desired  [...]
+b00fa322  28be17d5  write         csi         0        run
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[`volume create`]: /nomad/docs/commands/volume/create
diff --git a/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/jwt.mdx b/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/jwt.mdx
new file mode 100644
index 0000000000..d154049e9b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/jwt.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: JSON Web Token (JWT) Auth Method
+description: >-
+  Use the JWT auth method to authenticate to Nomad with a JSON web token and receive an ACL token with privileges based on JWT identity attributes. Learn how to configure the auth method parameters using this reference page and example configuration.
+---
+
+# JSON Web Token (JWT) Auth Method
+
+Use the `jwt` auth method to authenticate with Nomad by providing a
+[JWT](https://en.wikipedia.org/wiki/JSON_Web_Token) directly. The JWT is
+cryptographically verified using locally-provided keys, or, if configured, you may use an
+OIDC Discovery service to fetch the appropriate keys.
+
+Refer to [auth-method create] for the parameters required to create a JWT auth-method with a given verification method.
+
+## JWT Verification
+
+Nomad verifies JWT signatures against public keys from the issuer. This
+process uses one of these methods:
+
+- **Static Keys** - A set of public keys is stored directly in the
+  configuration.
+
+- **JWKS** - Configure a JSON Web Key Set ([JWKS](https://tools.ietf.org/html/rfc7517))
+  URL and optional certificate chain. Nomad fetches keys from
+  this endpoint during authentication.
+
+- **OIDC Discovery** - Configure an OIDC Discovery URL and optional certificate chain. Nomad fetches keys from this URL during authentication. When you use OIDC Discovery, Nomad applies OIDC validation criteria such as `iss` and `aud`.
+
+If you need multiple methods, create another auth method of this type 
+with a different name.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[auth-method create]: /nomad/docs/commands/acl/auth-method/create
diff --git a/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/oidc.mdx b/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/oidc.mdx
new file mode 100644
index 0000000000..6968abb087
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/acl/auth-methods/oidc.mdx
@@ -0,0 +1,117 @@
+---
+layout: docs
+page_title: OpenID Connect (OIDC) Auth Method
+description: >-
+  Use the OIDC auth method type to authenticate to Nomad through a web browser with an OpenID Connect provider. Learn how to configure the auth method parameters using this reference page and example configuration.
+---
+
+# OpenID Connect (OIDC) Auth Method
+
+Use the `oidc` auth method to authenticate to Nomad with
+[OIDC](https://en.wikipedia.org/wiki/OpenID_Connect). This method allows
+authentication via a configured OIDC provider using the user's web browser.
+Initiate this method from the Nomad UI or the command line.
+
+## Prerequisites
+
+- General knowledge of [OIDC concepts](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1)
+- [Nomad Access Control List fundamentals][ACL Overview].
+
+Refer to [auth-method create] for the parameters required to create an OIDC auth-method.
+
+## JWT Verification
+
+Nomad uses OIDC discovery to verify JWT signatures against public
+keys from the issuer. Nomad first fetches keys from the OIDC
+Discovery URL during authentication and then applies OIDC
+validation criteria such as `iss` and `aud`.
+
+## OIDC Authentication
+
+Nomad includes two built-in OIDC login flows: the Nomad UI, and the CLI using
+[`nomad login`](/nomad/docs/commands/login).
+
+### Redirect URIs
+
+Properly setting redirect URIs is an important part of OIDC auth method
+configuration. You must configure these in both Nomad and the OIDC
+provider, and these configurations must align.
+
+Specify the redirect URIs for an auth method with the
+`AllowedRedirectURIs` parameter in the auth method config. The Nomad UI
+and CLI use different redirect URIs, so you need to configure one or both,
+depending on your installation.
+
+**Note:** Redirect URI is used interchangeably with callback address.
+
+Logging in via the UI requires the redirect URI
+`http://{host:port}/ui/settings/tokens`.
+
+Logging in via the CLI requires the redirect
+URI `http://{host:port}/oidc/callback`.
+
+### OIDC Login
+
+#### Nomad UI
+
+1. Select one of the provider links in the Nomad homepage or navigate directly to `/ui/settings/tokens`.
+1. Click one of the buttons for your OIDC auth method of choice.
+1. Complete the authentication with the configured provider.
+
+#### CLI
+
+Execute the `nomad login -method=oidc` command to log in.
+If the `-oidc-callback-addr` flag is not specified, it will default to `localhost:4649`.
+
+```shell-session
+$ nomad login -method=oidc -oidc-callback-addr=<host:port>
+
+Complete the login via your OIDC provider. Launching browser to:
+
+    https://myco.auth0.com/authorize?redirect_uri=http%3A%2F%2Flocalhost%3A4649%2Foidc%2Fcallback&client_id=r3qXc2bix9eF...
+```
+
+Your browser opens to the generated URL to complete the provider's login.
+Enter the URL manually if the browser does not automatically open.
+
+## OIDC Configuration Troubleshooting
+
+The amount of configuration required for OIDC is relatively small, but it can
+be tricky to debug why things aren't working. The following are tips for setting up OIDC:
+
+- Monitor the log output for the Nomad servers for important
+information about OIDC validation failures.
+
+- Ensure correct redirect URIs in Nomad and on the provider. URIs
+need to match exactly. Check http/https, 127.0.0.1/localhost,
+port numbers, and whether trailing slashes are present.
+
+- The `BoundAudiences` option is typically
+  not required. OIDC providers use the `client_id` as the audience and
+  OIDC validation expects this.
+
+- Check your provider for scopes that are required to receive all of
+  the information you need. You often need to request the scopes
+  `profile` and `groups`, which you may set with
+  `OIDCScopes=["profile", "groups"]` in the auth method configuration.
+
+- If you're seeing claim-related errors in logs, review the provider's docs
+  very carefully to see how they're naming and structuring their claims.
+  Depending on the provider, you may be able to construct a simple `curl`
+  [implicit grant](https://developer.okta.com/blog/2018/05/24/what-is-the-oauth2-implicit-grant-type)
+  request to obtain a JWT that you can inspect. This example decodes the
+  JWT located in the `access_token` field of a JSON response.
+
+      jq --raw-output '.access_token / "." | .[1] | @base64d' jwt.json
+
+- With debug level logging, use the [VerboseLogging] option in the auth
+  method configuration to log the received OIDC token. This can be helpful
+  when debugging provider setup and verifying that the received claims are
+  what you expect. Since claims data is logged verbatim and may contain
+  sensitive information, do not use this option in production.
+
+@include 'jwt_claim_mapping_details.mdx'
+
+[ACL Overview]: /nomad/docs/concepts/acl
+[auth-method create]: /nomad/docs/commands/acl/auth-method/create
+[VerboseLogging]: /nomad/api-docs/acl/auth-methods#verboselogging
diff --git a/content/nomad/v1.9.x/content/docs/concepts/acl/index.mdx b/content/nomad/v1.9.x/content/docs/concepts/acl/index.mdx
new file mode 100644
index 0000000000..2da93992bf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/acl/index.mdx
@@ -0,0 +1,122 @@
+---
+layout: docs
+page_title: Access Control List (ACL)
+description: Learn how Nomad's Access Control List (ACL) security system uses tokens, policies, roles, and capabilities to control access to data and resources.
+---
+
+# Access Control List (ACL)
+
+This page provides conceptual information about Nomad's Access Control List
+(ACL) security system. At the highest level, Nomad's ACL system has tokens,
+policies, roles, and capabilities. Additionally, Nomad's Single Sign-On (SSO)
+ACL capabilities use auth methods and binding rules to restrict access.
+
+The Nomad [access control tutorials][] provide detailed information and
+guidance on Nomad ACL system.
+
+## Policy
+
+Policies consist of a set of rules defining the capabilities or actions to be
+granted. For example, a `readonly` policy might only grant the ability to list
+and inspect running jobs, but not to submit new ones. No permissions are
+granted by default, making Nomad a default-deny system.
+
+Each policy comprises one or more rules. The rules define the capabilities of a
+Nomad ACL token for accessing the objects in a Nomad cluster, objects like
+namespaces, node, agent, operator, quota, etc. For more information on writing
+policies, see the [ACL policy reference doc][].
+
+## Role
+
+Roles group one or more ACL policies into a container which can then be used to
+generate ACL tokens for authorisation. This abstraction allows easier control
+and updating of ACL permissions, particularly in larger, more diverse clusters.
+
+## Token
+
+Requests to Nomad are authenticated using a bearer token. Each ACL token has a
+public Accessor ID which is used to name a token and a Secret ID which is used
+to make requests to Nomad. The Secret ID is provided using a request header
+(`X-Nomad-Token`) and is used to authenticate the caller. Tokens are either
+management or client types. The `management` tokens are effectively "root" in
+the system and can perform any operation. The `client` tokens are associated
+with one or more ACL policies or roles which grant specific capabilities.
+
+When ACL tokens are created, they can be optionally marked as `Global`. This
+causes them to be created in the authoritative region and replicated to all
+other regions. Otherwise, tokens are created locally in the region the request
+was made and not replicated. `Local` tokens cannot be used for cross-region
+requests since they are not replicated between regions.
+
+## Workload Identity
+
+Nomad allocations can receive workload identities in the form of a
+[JSON Web Token (JWT)][jwt]. The
+[Workload Identity concept page][workload identity] has more information on
+this topic.
+
+## Auth Method
+
+Authentication methods dictate how Nomad should talk to SSO providers when a
+user requests to authenticate using one. Currently, Nomad supports the [OpenID
+Connect (OIDC)][oidc] SSO workflow which allows users to log in to Nomad via
+applications such as [Auth0][auth0], [Okta][okta], and [Vault][vault], and
+non-interactive login via externally-issued [JSON Web Tokens (JWT)][jwt].
+
+Since both the `oidc` and `jwt` auth methods ultimately operate on JWTs as
+bearer tokens, use the following to determine which method fits your use case:
+
+- **JWT**
+
+  - Ideal for machine-oriented, headless login where an operator may have already
+    arranged for a valid JWT to be dropped on a VM or provided to a container.
+  - User or application performing the Nomad login must have a valid JWT
+    to begin login.
+  - Does not require browser interaction.
+
+- **OIDC**
+
+  - Ideal for human-oriented, interactive login where an operator or administrator
+    may have deployed SSO widely and doesn't want to distribute Nomad ACL tokens
+    to every authorized user.
+  - User performing the Nomad login does not need a JWT.
+  - Requires browser interaction.
+
+## Binding Rule
+
+Binding rules provide a mapping between a Nomad user's SSO authorisation claims
+and internal Nomad objects such as ACL Roles and ACL Policies. A binding rule
+is directly related to a single auth method, and therefore only evaluated by
+login attempts using that method. All binding rules mapped to an auth method
+are evaluated during each login attempt.
+
+<Note>
+  Binding rules are evaluated in no specific order, and should there be an
+  overlap in their selectors or scope, a "sum" of all the binding rules will be
+  applied, thus the least granular binding rules will always override the more
+  granular ones, as long as they apply to the same auth method and identity.
+</Note>
+
+A successful selector match between an SSO provider claim and a binding rule
+will result in the generated ACL token having the identified ACL role or policy
+assigned to it. If the `BindType` parameter is `management`, the ACL token
+generated will be a `management` token, rather than a client token. This
+matcher supersedes role or policy assignments, and therefore should be used
+with caution.
+
+## Replication
+
+Multi-region federated clusters run replication process to replicate ACL
+objects from the [authoritative region][]. The replication processes run on
+each federated leader and replicate ACL policies, roles, auth methods, binding
+rules, and token marked as `Global`.
+
+[access control tutorials]: /nomad/tutorials/access-control
+[ACL policy reference doc]: /nomad/docs/other-specifications/acl-policy
+[authoritative region]: /nomad/docs/configuration/server#authoritative_region
+[jwt]: https://datatracker.ietf.org/doc/html/rfc7519
+[workload identity]: /nomad/docs/concepts/workload-identity
+[oidc]: https://openid.net/connect/
+[auth0]: https://auth0.com/
+[okta]: https://www.okta.com/
+[vault]: https://www.vaultproject.io/
diff --git a/content/nomad/v1.9.x/content/docs/concepts/architecture/federation.mdx b/content/nomad/v1.9.x/content/docs/concepts/architecture/federation.mdx
new file mode 100644
index 0000000000..196087d46d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/architecture/federation.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Federation
+description: |-
+  Nomad federation enables multiple Nomad clusters in different regions to work together seamlessly. Learn about cross-region request forwarding, replication, and Nomad Enterprise's multi-region job deployments.
+---
+
+# Federation
+
+This page provides conceptual information about the Nomad federation feature.
+Learn about cross-region request forwarding, replication, and Nomad Enterprise's
+multi-region job deployments.
+
+Nomad federation is a multi-cluster orchestration and management feature that
+enables multiple Nomad clusters running in different regions to work together
+seamlessly. By federating clusters, you benefit from improved scalability, fault
+tolerance, and centralized management of workloads across various data centers
+or geographical locations.
+
+## Cross-Region request forwarding
+
+API calls can include a `region` query parameter that defines the Nomad region
+the query is specified for. If this is not the local region, Nomad transparently
+forwards the request to a server in the requested region. When you omit the
+query parameter, Nomad uses the region of the server that is processing the
+request.
+
+## Replication
+
+Nomad writes the following objects in the authoritative region and replicates
+them to all federated regions:
+
+- ACL [policies][acl_policy], [roles][acl_role], [auth methods][acl_auth_method],
+  [binding rules][acl_binding_rule], and [global tokens][acl_token]
+- [Namespaces][namespace]
+- [Node pools][node_pool]
+- [Quota specifications][quota]
+- [Sentinel policies][sentinel_policies]
+
+When creating, updating, or deleting these objects, Nomad always sends the
+request to the authoritative region using RPC forwarding.
+
+Nomad starts replication routines on each federated cluster's leader server in a
+hub and spoke design. The routines then use blocking queries to receive updates
+from the authoritative region to mirror in their own state store. These routines
+also implement rate limiting, so that busy clusters do not degrade due to overly
+aggressive replication processes.
+
+<Note> Nomad writes ACL local tokens in the region where you make the request
+and  does not replicate those local tokens. </Note>
+
+## Multi-Region job deployments <EnterpriseAlert inline />
+
+Nomad job deployments can use the [`multiregion`][] block when running in
+federated mode. Multiregion configuration instructs Nomad to register and run
+the job on all the specified regions, removing the need for multiple job
+specification copies and registration on each region. Multiregion jobs do not
+provide regional failover in the event of failure.
+
+[acl_policy]: /nomad/docs/concepts/acl/#policy
+[acl_role]: /nomad/docs/concepts/acl/#role
+[acl_auth_method]: /nomad/docs/concepts/acl/#auth-method
+[acl_binding_rule]: /nomad/docs/concepts/acl/#binding-rule
+[acl_token]: /nomad/docs/concepts/acl/#token
+[node_pool]: /nomad/docs/concepts/node-pools
+[namespace]: /nomad/docs/other-specifications/namespace
+[quota]: /nomad/docs/other-specifications/quota
+[sentinel_policies]: /nomad/docs/enterprise/sentinel#sentinel-policies
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.9.x/content/docs/concepts/architecture/index.mdx b/content/nomad/v1.9.x/content/docs/concepts/architecture/index.mdx
new file mode 100644
index 0000000000..8087ff61a7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/architecture/index.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: Architecture
+description: |-
+  Nomad's system architecture supports a "run any workload anywhere" approach to scheduling and orchestration. Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+---
+
+# Architecture
+
+This page provides conceptual information on Nomad architecture.  Learn how regions, servers, and clients interact, and how Nomad clusters replicate data and run workloads.
+
+Nomad is a complex system that has many different pieces. To help both users and
+developers of Nomad build a mental model of how it works, this page documents
+the system architecture.
+
+Refer to the [glossary][] for more details on some of the terms discussed here.
+
+~> **Advanced Topic!** This page covers technical details
+of Nomad. You do not need to understand these details to
+effectively use Nomad. The details are documented here for
+those who wish to learn about them without having to go
+spelunking through the source code.
+
+## High-Level Overview
+
+Looking at only a single region, at a high level Nomad looks like this:
+
+[![Regional Architecture](/img/nomad-architecture-region.png)](/img/nomad-architecture-region.png)
+
+Within each region, we have both clients and servers. Servers are responsible for
+accepting jobs from users, managing clients, and [computing task placements](/nomad/docs/concepts/scheduling/scheduling).
+Each region may have clients from multiple datacenters, allowing a small number of servers
+to handle very large clusters.
+
+In some cases, for either availability or scalability, you may need to run multiple
+regions. Nomad supports federating multiple regions together into a single cluster.
+At a high level, this setup looks like this:
+
+[![Global Architecture](/img/nomad-architecture-global.png)](/img/nomad-architecture-global.png)
+
+Regions are fully independent from each other, and do not share jobs, clients, or
+state. They are loosely-coupled using a gossip protocol, which allows users to
+submit jobs to any region or query the state of any region transparently. Requests
+are forwarded to the appropriate server to be processed and the results returned.
+Data is _not_ replicated between regions.
+
+The servers in each region are all part of a single consensus group. This means
+that they work together to elect a single leader which has extra duties. The leader
+is responsible for processing all queries and transactions. Nomad is optimistically
+concurrent, meaning all servers participate in making scheduling decisions in parallel.
+The leader provides the additional coordination necessary to do this safely and
+to ensure clients are not oversubscribed.
+
+Each region is expected to have either three or five servers. This strikes a balance
+between availability in the case of failure and performance, as consensus gets
+progressively slower as more servers are added. However, there is no limit to the number
+of clients per region.
+
+Clients are configured to communicate with their regional servers and communicate
+using remote procedure calls (RPC) to register themselves, send heartbeats for liveness,
+wait for new allocations, and update the status of allocations. A client registers
+with the servers to provide the resources available, attributes, and installed drivers.
+Servers use this information for scheduling decisions and create allocations to assign
+work to clients.
+
+Users make use of the Nomad CLI or API to submit jobs to the servers. A job represents
+a desired state and provides the set of tasks that should be run. The servers are
+responsible for scheduling the tasks, which is done by finding an optimal placement for
+each task such that resource utilization is maximized while satisfying all constraints
+specified by the job. Resource utilization is maximized by bin packing, in which
+the scheduling tries to make use of all the resources of a machine without
+exhausting any dimension. Job constraints can be used to ensure an application is
+running in an appropriate environment. Constraints can be technical requirements based
+on hardware features such as architecture and availability of GPUs, or software features
+like operating system and kernel version, or they can be business constraints like
+ensuring PCI compliant workloads run on appropriate servers.
+
+## Getting in Depth
+
+This has been a brief high-level overview of the architecture of Nomad. There
+are more details available for each of the sub-systems. The [consensus protocol](/nomad/docs/concepts/consensus),
+[gossip protocol](/nomad/docs/concepts/gossip), and [scheduler design](/nomad/docs/concepts/scheduling/scheduling)
+are all documented in more detail.
+
+For other details, either consult the code, [open an issue on
+GitHub][gh_issue], or ask a question in the [community forum][forum].
+
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[forum]: https://discuss.hashicorp.com/c/nomad
+[glossary]: /nomad/docs/glossary
diff --git a/content/nomad/v1.9.x/content/docs/concepts/consensus.mdx b/content/nomad/v1.9.x/content/docs/concepts/consensus.mdx
new file mode 100644
index 0000000000..961f023464
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/consensus.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: Consensus Protocol
+description: |-
+  Nomad uses a consensus protocol based on Raft to manage cluster node state. Learn about logs, Finite State Machine (FSM), peer set, quorum, committed entry, and leader. 
+---
+
+# Consensus Protocol
+
+This page provides conceptual information on Nomad's [consensus
+protocol](<https://en.wikipedia.org/wiki/Consensus_(computer_science)>), which
+provides [Consistency as defined by CAP](https://en.wikipedia.org/wiki/CAP_theorem).
+The consensus protocol is based on
+["Raft: In search of an Understandable Consensus Algorithm"](https://raft.github.io/raft.pdf).
+For a visual explanation of Raft, see [The Secret Lives of Data](http://thesecretlivesofdata.com/raft).
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Raft Protocol Overview
+
+Raft is a consensus algorithm that is based on
+[Paxos](https://en.wikipedia.org/wiki/Paxos_%28computer_science%29). Compared
+to Paxos, Raft is designed to have fewer states and a simpler, more
+understandable algorithm.
+
+There are a few key terms to know when discussing Raft:
+
+- **Log** - The primary unit of work in a Raft system is a log entry. The problem
+  of consistency can be decomposed into a _replicated log_. A log is an ordered
+  sequence of entries. We consider the log consistent if all members agree on
+  the entries and their order.
+
+- **FSM** - [Finite State Machine](https://en.wikipedia.org/wiki/Finite-state_machine).
+  An FSM is a collection of finite states with transitions between them. As new logs
+  are applied, the FSM is allowed to transition between states. Application of the
+  same sequence of logs must result in the same state, meaning behavior must be deterministic.
+
+- **Peer set** - The peer set is the set of all members participating in log replication.
+  For Nomad's purposes, all server nodes are in the peer set of the local region.
+
+- **Quorum** - A quorum is a majority of members from a peer set: for a set of size `n`,
+  quorum requires at least `⌊(n/2)+1⌋` members.
+  For example, if there are 5 members in the peer set, we would need 3 nodes
+  to form a quorum. If a quorum of nodes is unavailable for any reason, the
+  cluster becomes _unavailable_ and no new logs can be committed.
+
+- **Committed Entry** - An entry is considered _committed_ when it is durably stored
+  on a quorum of nodes. Once an entry is committed it can be applied.
+
+- **Leader** - At any given time, the peer set elects a single node to be the leader.
+  The leader is responsible for ingesting new log entries, replicating to followers,
+  and managing when an entry is considered committed.
+
+Raft is a complex protocol and will not be covered here in detail (for those who
+desire a more comprehensive treatment, the full specification is available in this
+[paper](https://raft.github.io/raft.pdf)).
+We will, however, attempt to provide a high level description which may be useful
+for building a mental model.
+
+Raft nodes are always in one of three states: follower, candidate, or leader. All
+nodes initially start out as a follower. In this state, nodes can accept log entries
+from a leader and cast votes. If no entries are received for some time, nodes
+self-promote to the candidate state. In the candidate state, nodes request votes from
+their peers. If a candidate receives a quorum of votes, then it is promoted to a leader.
+The leader must accept new log entries and replicate to all the other followers.
+In addition, if stale reads are not acceptable, all queries must also be performed on
+the leader.
+
+Once a cluster has a leader, it is able to accept new log entries. A client can
+request that a leader append a new log entry (from Raft's perspective, a log entry
+is an opaque binary blob). The leader then writes the entry to durable storage and
+attempts to replicate to a quorum of followers. Once the log entry is considered
+_committed_, it can be _applied_ to a finite state machine. The finite state machine
+is application specific; in Nomad's case, we use
+[MemDB](https://github.com/hashicorp/go-memdb) to maintain cluster state.
+
+Obviously, it would be undesirable to allow a replicated log to grow in an unbounded
+fashion. Raft provides a mechanism by which the current state is snapshotted and the
+log is compacted. Because of the FSM abstraction, restoring the state of the FSM must
+result in the same state as a replay of old logs. This allows Raft to capture the FSM
+state at a point in time and then remove all the logs that were used to reach that
+state. This is performed automatically without user intervention and prevents unbounded
+disk usage while also minimizing time spent replaying logs. One of the advantages of
+using MemDB is that it allows Nomad to continue accepting new transactions even while
+old state is being snapshotted, preventing any availability issues.
+
+Consensus is fault-tolerant up to the point where quorum is available.
+If a quorum of nodes is unavailable, it is impossible to process log entries or reason
+about peer membership. For example, suppose there are only 2 peers: A and B. The quorum
+size is also 2, meaning both nodes must agree to commit a log entry. If either A or B
+fails, it is now impossible to reach quorum. This means the cluster is unable to add
+or remove a node or to commit any additional log entries. This results in
+_unavailability_. At this point, manual intervention would be required to remove
+either A or B and to restart the remaining node in bootstrap mode.
+
+A Raft cluster of 3 nodes can tolerate a single node failure while a cluster
+of 5 can tolerate 2 node failures. The recommended configuration is to either
+run 3 or 5 Nomad servers per region. This maximizes availability without
+greatly sacrificing performance. The [deployment table](#deployment_table) below
+summarizes the potential cluster size options and the fault tolerance of each.
+
+In terms of performance, Raft is comparable to Paxos. Assuming stable leadership,
+committing a log entry requires a single round trip to half of the cluster.
+Thus, performance is bound by disk I/O and network latency.
+
+## Raft in Nomad
+
+Only Nomad server nodes participate in Raft and are part of the peer set. All
+client nodes forward requests to servers. The clients in Nomad only need to know
+about their allocations and query that information from the servers, while the
+servers need to maintain the global state of the cluster.
+
+Since all servers participate as part of the peer set, they all know the current
+leader. When an RPC request arrives at a non-leader server, the request is
+forwarded to the leader. If the RPC is a _query_ type, meaning it is read-only,
+the leader generates the result based on the current state of the FSM. If
+the RPC is a _transaction_ type, meaning it modifies state, the leader
+generates a new log entry and applies it using Raft. Once the log entry is committed
+and applied to the FSM, the transaction is complete.
+
+Because of the nature of Raft's replication, performance is sensitive to network
+latency. For this reason, each region elects an independent leader and maintains
+a disjoint peer set. Data is partitioned by region, so each leader is responsible
+only for data in their region. When a request is received for a remote region,
+the request is forwarded to the correct leader. This design allows for lower latency
+transactions and higher availability without sacrificing consistency.
+
+## Consistency Modes
+
+Although all writes to the replicated log go through Raft, reads are more
+flexible. To support various trade-offs that developers may want, Nomad
+supports 2 different consistency modes for reads.
+
+The two read modes are:
+
+- `default` - Raft makes use of leader leasing, providing a time window
+  in which the leader assumes its role is stable. However, if a leader
+  is partitioned from the remaining peers, a new leader may be elected
+  while the old leader is holding the lease. This means there are 2 leader
+  nodes. There is no risk of a split-brain since the old leader will be
+  unable to commit new logs. However, if the old leader services any reads,
+  the values are potentially stale. The default consistency mode relies only
+  on leader leasing, exposing clients to potentially stale values. We make
+  this trade-off because reads are fast, usually strongly consistent, and
+  only stale in a hard-to-trigger situation. The time window of stale reads
+  is also bounded since the leader will step down due to the partition.
+
+- `stale` - This mode allows any server to service the read regardless of if
+  it is the leader. This means reads can be arbitrarily stale but are generally
+  within 50 milliseconds of the leader. The trade-off is very fast and scalable
+  reads but with stale values. This mode allows reads without a leader meaning
+  a cluster that is unavailable will still be able to respond.
+
+## Deployment Table ((#deployment_table))
+
+Below is a table that shows quorum size and failure tolerance for various
+cluster sizes. The recommended deployment is either 3 or 5 servers. A single
+server deployment is _**highly**_ discouraged as data loss is inevitable in a
+failure scenario.
+
+<table>
+  <thead>
+    <tr>
+      <th>Servers</th>
+      <th>Quorum Size</th>
+      <th>Failure Tolerance</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>1</td>
+      <td>1</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>2</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>3</td>
+      <td>2</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>3</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>5</td>
+      <td>3</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>6</td>
+      <td>4</td>
+      <td>2</td>
+    </tr>
+    <tr>
+      <td>7</td>
+      <td>4</td>
+      <td>3</td>
+    </tr>
+  </tbody>
+</table>
diff --git a/content/nomad/v1.9.x/content/docs/concepts/cpu.mdx b/content/nomad/v1.9.x/content/docs/concepts/cpu.mdx
new file mode 100644
index 0000000000..58872046a9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/cpu.mdx
@@ -0,0 +1,385 @@
+---
+layout: docs
+page_title: How Nomad Uses CPU
+description: Learn how Nomad discovers and uses CPU resources on nodes in order to place and run workloads. Nomad Enterprise can use non-uniform memory access (NUMA) scheduling, which is optimized for the NUMA topology of a client node.
+---
+
+# How Nomad Uses CPUs
+
+This page provides conceptual information on how Nomad discovers and uses CPU resources on nodes in order to place and run workloads.
+
+Every Nomad node has a Central Processing Unit (CPU) providing the computational
+power needed for running operating system processes. Nomad uses the CPU to
+run tasks defined by the Nomad job submitter. For Nomad to know which nodes
+have sufficient capacity for running a given task, each node in the cluster
+is fingerprinted to gather information about the performance characteristics
+of its CPU. The two metrics associated with each Nomad node with regard to
+CPU performance are its bandwidth (how much it can _compute_) and the number
+of cores.
+
+Modern CPUs may contain heterogeneous core types. Apple introduced the M1 CPU
+in 2020 which contains both _performance_ (P-Core) and _efficiency_ (E-Core)
+types. Each core type operates at a different base frequency. Intel introduced
+a similar topology in its Raptor Lake chips in 2022. When fingerprinting
+the characteristics of a CPU Nomad is capable of taking these advanced CPU
+topologies into account.
+
+[![PE Cores](/img/nomad-pe-cores.png)](/img/nomad-pe-cores.png)
+
+## Calculating CPU resources
+
+The total CPU bandwidth of a Nomad node is the sum of the product between the
+frequency of each core type and the total number of cores of that type in the
+CPU.
+
+```
+bandwidth = (p_cores * p_frequency) + (e_cores * e_frequency)
+```
+
+The total number of cores is computed by summing the number of P-Cores and the
+number of E-Cores.
+
+```
+cores = p_cores + e_cores
+```
+
+Nomad does not distinguish between logical and physical CPU cores. One of the
+defining differences between the P-Core and E-Core types is that the E-Cores
+do not support hyperthreading, whereas P-Cores do. As such a single physical
+P-Core is presented as 2 logical cores, and a single E-Core is presented as 1
+logical core.
+
+The example below is from a Nomad node with an Intel i9-13900 CPU. It is made
+up of mixed core types, with a P-Core base frequency of 2 GHz and an E-Core
+base frequency of 1.5 GHz.
+
+These characteristics are reflected in the `cpu.frequency.performance` and
+`cpu.frequency.efficiency` node attributes respectively.
+
+```text
+cpu.arch                        = amd64
+cpu.frequency.efficiency        = 1500
+cpu.frequency.performance       = 2000
+cpu.modelname                   = 13th Gen Intel(R) Core(TM) i9-13900
+cpu.numcores                    = 32
+cpu.numcores.efficiency         = 16
+cpu.numcores.performance        = 16
+cpu.reservablecores             = 32
+cpu.totalcompute                = 56000
+cpu.usablecompute               = 56000
+```
+
+## Reserving CPU resources
+
+In the fingerprinted node attributes, `cpu.totalcompute` indicates the total
+amount of CPU bandwidth the processor is capable of delivering. In some cases it
+may be beneficial to reserve some amount of a node's CPU resources for use by
+the operating system and other non-Nomad processes. This can be done in client
+configuration.
+
+The amount of reserved CPU can be specified in bandwidth via `cpu`.
+
+```hcl
+client {
+  reserved {
+    cpu = 3000 # mhz
+  }
+}
+```
+
+Or as a specific set of `cores` on which to disallow the scheduling of Nomad
+tasks. This capability is available on Linux systems only.
+
+```hcl
+client {
+  reserved {
+    cores = "0-3"
+  }
+}
+```
+
+When the CPU is constrained by one of the above configurations, the node
+attribute `cpu.usablecompute` indicates the total amount of CPU bandwidth
+available for scheduling of Nomad tasks.
+
+## Allocating CPU Resources
+
+When scheduling jobs, a Task must specify how much CPU resource should be
+allocated on its behalf. This can be done in terms of bandwidth in MHz with the
+`cpu` attribute. This MHz value is translated directly into [cpushares][] on
+Linux systems.
+
+```hcl
+task {
+  resources {
+    cpu = 2000 # mhz
+  }
+}
+```
+
+Note that the isolation mechanism around CPU resources is dependent on each task
+driver and its configuration. The standard behavior is that Nomad ensures a task
+has access to _at least_ as much of its allocated CPU bandwidth. In which case
+if a node has idle CPU capacity, a task may use additional CPU resources.  Some
+task drivers enable limiting a task to use only the amount of bandwidth
+allocated to the task, described in the [CPU Hard Limits](#cpu-hard-limits)
+section below.
+
+On Linux systems, Nomad supports reserving whole CPU cores specifically for a
+task. No task will be allowed to run on a CPU core reserved for another task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+  }
+}
+```
+
+Nomad Enterprise supports NUMA aware scheduling, which enables operators to
+more finely control which CPU cores may be reserved for tasks.
+
+### CPU hard limits
+
+Some task drivers support the configuration option `cpu_hard_limit`. If enabled
+this option restricts tasks from bursting above their CPU limit even when there
+is idle capacity on the node. The tradeoff is consistency versus utilization.
+A task with too few CPU resources may operate fine until another task is placed
+on the node causing a reduction in available CPU bandwidth, which could cause
+disruption for the underprovisioned task.
+
+### CPU environment variables
+
+To help tasks understand the resources available to them, Nomad sets the
+following environment variables in their runtime environment.
+
+
+- `NOMAD_CPU_LIMIT` - The amount of CPU bandwidth allocated on behalf of the
+  task.
+- `NOMAD_CPU_CORES` - The set of cores in [cpuset][] notation reserved for the
+  task. This value is only set if `resources.cores` is configured.
+
+```sh
+NOMAD_CPU_CORES=3-5
+NOMAD_CPU_LIMIT=9000
+```
+
+## NUMA
+
+Nomad clients are commonly provisioned on real hardware in an on-premise
+environment or in the cloud on large `.metal` instance types. In either case, it
+is likely the underlying server is designed around a [non-uniform memory access (NUMA) topology][numa_wiki].
+Servers that contain multiple CPU sockets or multiple RAM banks per CPU socket
+are characterized by the non-uniform access times involved in accessing system
+memory.
+
+[![NUMA](/img/nomad-numa.png)](/img/nomad-numa.png)
+
+The simplified example machine above has the following topology:
+- 2 physical CPU sockets
+- 4 system memory banks, 2 per socket
+- 8 physical cpu cores (4 per socket)
+- 2 logical cpu cores per physical core
+- 4 PCI devices, 1 per memory bank
+
+### Optimizing performance
+
+Operating system processes take longer to access memory across a NUMA boundary.
+
+Using the example above if a task is scheduled on Core 0, accessing memory in
+Mem 1 might take 20% longer than accessing memory in Mem 0, and accessing memory
+in Mem 2 might take 300% longer.
+
+The extreme differences are due to various physical hardware limitations. A core
+accessing memory in its own NUMA node is optimal. Programs which perform a high
+throughput of reads or writes to/from system memory will have their performance
+substantially hindered by not optimizing their spatial locality with regard to
+the systems NUMA topology.
+
+### SLIT tables
+
+Modern machines will define System Locality Distance Information (SLIT) tables
+in their firmware. These tables are understood and made referenceable by the
+Linux kernel. There are two key pieces of information provided by SLIT tables:
+- Which CPU cores belong to which NUMA nodes
+- The penalty incurred for accessing each NUMA node from a core in every other
+NUMA node
+
+The `lscpu` command can be used to describe the Core associativity on a machine.
+For example on an `r6a.metal` EC2 instance:
+
+```shell-session
+$ lscpu | grep NUMA
+NUMA node(s):           4
+NUMA node0 CPU(s):      0-23,96-119
+NUMA node1 CPU(s):      24-47,120-143
+NUMA node2 CPU(s):      48-71,144-167
+NUMA node3 CPU(s):      72-95,168-191
+```
+
+And the associated performance degradations are available via `numactl`:
+
+```shell-session
+$ numactl -H
+available: 4 nodes (0-3)
+...
+node distances:
+node   0   1   2   3
+  0:  10  12  32  32
+  1:  12  10  32  32
+  2:  32  32  10  12
+  3:  32  32  12  10
+```
+
+These SLIT table node distance values are presented as approximate relative
+ratios. The value of 10 represents an optimal situation where a memory access
+is occurring from a CPU that is part of the same NUMA node. A value of 20 would
+indicate a 200% performance degradation, 30 for 300%, etc.
+
+### Node Attributes
+
+Nomad clients will fingerprint the machine's NUMA topology and export the
+core associativity as node attributes. This data can provide a Nomad operator
+a better understanding of when it might be useful to make use of NUMA aware
+scheduling for certain workloads.
+
+```
+numa.node.count       = 4
+numa.node0.cores      = 0-23,96-119
+numa.node1.cores      = 24-47,120-143
+numa.node2.cores      = 48-71,144-167
+numa.node3.cores      = 72-95,168-191
+```
+
+## NUMA aware scheduling <EnterpriseAlert inline />
+
+Nomad Enterprise is capable of scheduling tasks in a way that is optimized for
+the NUMA topology of a client node. Nomad is able to correlate CPU cores with
+memory nodes and assign tasks to run on specific CPU cores so as to minimize any
+cross-memory node access patterns. Additionally, Nomad is able to correlate
+devices to memory nodes and enable NUMA-aware scheduling to take device
+associativity into account when making scheduling decisions.
+
+A task may specify a `numa` block indicating its NUMA optimization preference. This example allocates a `1080ti` GPU and ensures it is on the same NUMA node as the 4 CPU cores reserved for the task.
+
+```hcl
+task {
+  resources {
+    cores = 4
+    memory = 2048
+
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+
+    numa {
+      affinity = "require"
+      devices = [
+        "nvidia/gpu/1080ti"
+      ]
+	  }
+  }
+}
+```
+
+### `affinity` options
+
+This is a required field. There are three supported affinity options:
+`none`, `prefer`, and `require`, each with their own advantages and tradeoffs.
+
+#### option `none`
+
+In the `none` mode, the Nomad scheduler leverages the apathy of jobs without
+preference of NUMA affinity to help reduce core fragmentation within NUMA nodes.
+It does so by bin-packing the core request of these jobs onto the NUMA nodes
+with the fewest unused cores available.
+
+The `none` mode is the default mode if the `numa` block is not specified.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "none"
+  }
+}
+```
+
+#### option `prefer`
+
+In the `prefer` mode, the Nomad scheduler uses the hardware topology of a node
+to calculate an optimized selection of available cores, but does not limit
+those cores to come from a single NUMA node.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "prefer"
+  }
+}
+```
+
+#### option `require`
+
+In the `require` mode, the Nomad scheduler uses the topology of each potential
+client to find a set of available CPU cores that belong to the same NUMA node.
+If no such set of cores can be found, that node is marked exhausted for the
+resource of `numa-cores`.
+
+```hcl
+resources {
+  cores = 4
+  numa {
+    affinity = "require"
+  }
+}
+```
+
+### `devices` options
+
+`devices` is an optional list of devices that must be colocated on the NUMA node
+along with allocated CPU cores.
+
+The following diagram shows how a set of devices can be correlated to CPU and memory.
+
+[![How a set of devices can be correlated to CPU and memory](/img/nomad-devices-correlate-cpu-memory.png)](/img/nomad-devices-correlate-cpu-memory.png)
+
+This example declares three devices and configures two in the `numa` block.
+
+```hcl
+task {
+  resources {
+    cores = 8
+    memory = 16384
+
+    device "nvidia/gpu/H100" {
+      count = 2
+    }
+    device "intel/net/XXVDA2" {
+      count = 1
+    }
+    device "xilinx/fpga/X7" {
+      count = 1
+    }
+
+    numa {
+	    affinity = "require"
+	    devices = [
+  	    "nvidia/gpu/H100",
+  	    "intel/net/XXVDA2"
+	    ]
+    }
+  }
+}
+```
+
+## Virtual CPU fingerprinting
+
+When running on a virtualized host such as Amazon EC2 Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions will
+require installing the `dmidecode` package manually.
+
+[cpuset]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cpusets.html
+[cpushares]: https://www.redhat.com/sysadmin/cgroups-part-two
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
diff --git a/content/nomad/v1.9.x/content/docs/concepts/filesystem.mdx b/content/nomad/v1.9.x/content/docs/concepts/filesystem.mdx
new file mode 100644
index 0000000000..4ceb578da8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/filesystem.mdx
@@ -0,0 +1,495 @@
+---
+layout: docs
+page_title: Allocation Filesystems
+description: |-
+  Learn how Nomad uses allocation working directories to store job task templates, storage volumes, artifacts, dispatch payloads, and logs. Review image and chroot isolation, as well as when Nomad uses isolation mode.
+---
+
+# Allocation Filesystems
+
+This page provides conceptual information about how Nomad uses allocation
+working directories to store job task templates, storage volumes, artifacts,
+dispatch payloads, and logs. Review image and chroot isolation, as well as when
+Nomad does not use any isolation mode.
+
+Nomad creates a working directory for each allocation on a client. Find this
+directory in the Nomad [`data_dir`] at
+`./alloc/«alloc_id»`. The allocation working directory is where Nomad
+creates task directories and directories shared between tasks, writes logs for
+tasks, and downloads artifacts or templates.
+
+An allocation with two tasks (named `task1` and `task2`) will have an
+allocation directory like this example.
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   ├── task1.stdout.0
+│   │   ├── task2.stderr.0
+│   │   └── task2.stdout.0
+│   └── tmp
+├── task1
+│   ├── local
+│   ├── private
+│   ├── secrets
+│   └── tmp
+└── task2
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+- **alloc/**: This directory is shared across all tasks in an allocation and
+  can be used to store data that needs to be used by multiple tasks, such as a
+  log shipper. This is the directory that's provided to the task as the
+  `NOMAD_ALLOC_DIR`. Note that this `alloc/` directory is not the same as the
+  "allocation working directory", which is the top-level directory. All tasks
+  in a task group can read and write to the `alloc/` directory. But the full host
+  path may differ depending on the task driver's [filesystem isolation mode], so
+  tasks should always used the `NOMAD_ALLOC_DIR` environment variable
+  to find this path rather than relying on the specific implementation of the
+  [`none`](#none-isolation), [`chroot`](#chroot-isolation), or [`image`](#image-isolation)
+  modes. Within the `alloc/` directory are three standard directories:
+
+  - **alloc/data/**: This directory is the location used by the
+    [`ephemeral_disk`] block for shared data.
+
+  - **alloc/logs/**: This directory is the location of the log files for every
+    task within an allocation. The `nomad alloc logs` command streams these
+    files to your terminal.
+
+  - **alloc/tmp/**: A temporary directory used as scratch space by task drivers.
+
+- **«taskname»**: Each task has a **task working directory** with the same name as
+  the task. Tasks in a task group can't read each other's task working
+  directory. Depending on the task driver's [filesystem isolation mode], a
+  task may not be able to access the task working directory. Within the
+  `task/` directory are three standard directories:
+
+  - **«taskname»/local/**: This directory is the location provided to the task as the
+    `NOMAD_TASK_DIR`. Note this is not the same as the "task working
+    directory". This directory is private to the task.
+
+  - **«taskname»/private/**: This directory is used by Nomad to store private files
+    related to the allocation, such as Vault tokens, that are not shared with tasks
+    when using [`image` isolation](#image-isolation). The contents of files in this
+    directory cannot be read by the `nomad alloc fs` command or the via Nomad's
+    API.
+    <Warning>
+      While not shared with tasks that use <code>image</code> isolation, this
+      path is still accessible by tasks using <a href="#chroot-isolation">
+      <code>chroot</code></a> or <a href="#none-isolation"><code>none</code></a> isolation
+    </Warning>
+
+  - **«taskname»/secrets/**: This directory is the location provided to the task as
+    `NOMAD_SECRETS_DIR`. The contents of files in this directory cannot be read
+    by the `nomad alloc fs` command. It can be used to store secret data that
+    should not be visible outside the task. Where possible it is backed by an
+    in-memory filesystem and mounted `noexec`.
+
+  - **«taskname»/tmp/**: A temporary directory used as scratch space by task drivers.
+
+The allocation working directory is the directory you see when using the
+`nomad alloc fs` command. If you were to run `nomad alloc fs` against the
+allocation that made the working directory shown above, you'd see the
+following:
+
+```shell-session
+$ nomad alloc fs c0b2245f
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  task1/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  task2/
+
+$ nomad alloc fs c0b2245f alloc/
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  data/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:39Z  logs/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+
+$ nomad alloc fs c0b2245f task1/
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:00:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:00:32Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:00:32Z  tmp/
+```
+
+## Task Drivers and Filesystem Isolation Modes
+
+Depending on the task driver, the task's working directory may also be the
+root directory for the running task. This is determined by the task driver's
+[filesystem isolation capability].
+
+### `image` isolation
+
+Task drivers like `docker` or `qemu` use `image` isolation, where the task
+driver isolates task filesystems as machine images. These filesystems are
+owned by the task driver's external process and not by Nomad itself. These
+filesystems will not typically be found anywhere in the allocation working
+directory. For example, Docker containers will have their overlay filesystem
+unpacked to `/var/run/docker/containerd/«container_id»` by default.
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `image` isolation, typically by
+bind-mounting them to the task driver's filesystem.
+
+You can see an example of `image` isolation by running the following minimal
+job:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task1.stderr.0
+│   │   └── task1.stdout.0
+│   └── tmp
+└── task1
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs b0686b27
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  task1/
+
+$ nomad alloc fs b0686b27 task1
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T18:51:54Z  local/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  private/
+drwxrwxrwx   60 B     2020-10-27T18:51:54Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T18:51:54Z  tmp/
+
+$ nomad alloc fs b0686b27 task1/local
+Mode  Size  Modified Time  Name
+```
+
+If you inspect the Docker container that's created, you'll see three
+directories bind-mounted into the container:
+
+```shell-session
+$ docker inspect 32e | jq '.[0].HostConfig.Binds'
+[
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/alloc:/alloc",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/local:/local",
+  "/var/nomad/alloc/b0686b27-8af3-8252-028f-af485c81a8b3/task1/secrets:/secrets"
+]
+```
+
+The root filesystem inside the container can see these three mounts, along
+with the rest of the container filesystem:
+
+```shell-session
+$ docker exec -it 32e /bin/sh
+# ls /
+alloc  boot  dev  home  lib64  media  opt   root  sbin     srv  tmp  var
+bin    data  etc  lib   local  mnt    proc  run   secrets  sys  usr
+```
+
+Note that because the three directories are bind-mounted into the container
+filesystem, nothing written outside those three directories elsewhere in the
+allocation working directory will be accessible inside the container. This
+means templates, artifacts, and dispatch payloads for tasks with `image`
+isolation must be written into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`.
+
+To work around this limitation, you can use the task driver's mounting
+capabilities to mount one of the three directories to another location in the
+task. For example, with the Docker driver you can use the driver's `mounts`
+block to bind a secret written by a `template` block to the
+`NOMAD_SECRETS_DIR` into a configuration directory elsewhere in the task:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task1" {
+    driver = "docker"
+
+    config {
+      image = "redis:6.0"
+      mounts = [{
+        type     = "bind"
+        source   = "secrets"
+        target   = "/etc/redis.d"
+        readonly = true
+      }]
+
+      template {
+        destination = "${NOMAD_SECRETS_DIR}/redis.conf"
+        data        = <<EOT
+{{ with secret "secrets/data/redispass" }}
+requirepass {{- .Data.data.passwd -}}{{end}}
+EOT
+
+      }
+    }
+  }
+}
+```
+
+Note that relative mount source path are relative to the task working
+directory, so to bind the `NOMAD_ALLOC_DIR` as a mount source, you will need
+to use a relative path that traverses up into the allocation working directory
+(ex. `source = "../alloc"`).
+
+### `chroot` isolation
+
+Task drivers like `exec` or `java` (on Linux) use `chroot` isolation, where
+the task driver isolates task filesystems with `chroot` or `pivot_root`. These
+isolated filesystems will be built inside the task working directory.
+
+You can see an example of `chroot` isolation by running the following minimal
+job on Linux:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task2" {
+    driver = "exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+filesystem tree that has been populated with the task driver's [chroot
+contents], in addition to the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR`:
+
+```shell-session
+.
+├── alloc
+│   ├── container
+│   ├── data
+│   ├── logs
+│   └── tmp
+└── task2
+    ├── alloc
+    ├── bin
+    ├── dev
+    ├── etc
+    ├── executor.out
+    ├── lib
+    ├── lib32
+    ├── lib64
+    ├── local
+    ├── private
+    ├── proc
+    ├── run
+    ├── sbin
+    ├── secrets
+    ├── sys
+    ├── tmp
+    └── usr
+```
+
+Likewise, the root directory of the task is now available in the `nomad alloc fs` command output:
+
+```shell-session
+$ nomad alloc fs eebd13a7
+Mode        Size     Modified Time         Name
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxrwxrwx  4.0 KiB  2020-10-27T19:05:24Z  task2/
+
+$ nomad alloc fs eebd13a7 task2
+Mode         Size     Modified Time         Name
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:24Z  alloc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  bin/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  dev/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  etc/
+-rw-r--r--   297 B    2020-10-27T19:05:24Z  executor.out
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib32/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  lib64/
+drwxrwxrwx   4.0 KiB  2020-10-27T19:05:22Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  private/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  proc/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  run/
+drwxr-xr-x   12 KiB   2020-10-27T19:05:22Z  sbin/
+drwxrwxrwx   60 B     2020-10-27T19:05:22Z  secrets/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:24Z  sys/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:05:22Z  tmp/
+drwxr-xr-x   4.0 KiB  2020-10-27T19:05:22Z  usr/
+```
+
+Nomad will provide the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` to tasks with `chroot` isolation. But unlike with `image`
+isolation, Nomad does not need to bind-mount the `NOMAD_TASK_DIR` directory
+because it can be directly created inside the chroot.
+
+```shell-session
+$ nomad alloc exec eebd13a7 /bin/sh
+$ mount
+...
+/dev/mapper/root on /alloc type ext4 (rw,relatime,errors=remount-ro,data=ordered)
+tmpfs on /private type tmpfs (rw,noexec,relatime,size=1024k)
+tmpfs on /secrets type tmpfs (rw,noexec,relatime,size=1024k,noswap)
+...
+```
+
+### `none` isolation
+
+The `raw_exec` task driver (or the `java` task driver on Windows) uses the
+`none` filesystem isolation mode. This means the task driver does not isolate
+the filesystem for the task, and the task can read and write anywhere the
+user that's running Nomad can.
+
+You can see an example of `none` isolation by running the following minimal
+`raw_exec` job on Linux or Unix.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  task "task3" {
+    driver = "raw_exec"
+
+    config {
+      command = "/bin/sh"
+      args = ["-c", "sleep 600"]
+    }
+  }
+}
+```
+
+If you look at the allocation working directory from the host, you'll see a
+minimal filesystem tree:
+
+```shell-session
+.
+├── alloc
+│   ├── data
+│   ├── logs
+│   │   ├── task3.stderr.0
+│   │   └── task3.stdout.0
+│   └── tmp
+└── task3
+    ├── executor.out
+    ├── local
+    ├── private
+    ├── secrets
+    └── tmp
+```
+
+The `nomad alloc fs` command shows the same bare directory tree:
+
+```shell-session
+$ nomad alloc fs 87ec7d12 task3
+Mode         Size     Modified Time         Name
+-rw-r--r--   140 B    2020-10-27T19:15:33Z  executor.out
+drwxrwxrwx   4.0 KiB  2020-10-27T19:15:33Z  local/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  private/
+drwxrwxrwx   60 B     2020-10-27T19:15:33Z  secrets/
+dtrwxrwxrwx  4.0 KiB  2020-10-27T19:15:33Z  tmp/
+```
+
+But if you use `nomad alloc exec` to view the filesystem from inside the
+container, you'll see that the task has access to the entire root
+filesystem. The `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and `NOMAD_SECRETS_DIR`
+point to the filepath on the host, not a path anchored in the task working
+directory. And the task is running as `root`, because the Nomad client agent
+is running as `root`. This is why the `raw_exec` driver is disabled by
+default.
+
+```shell-session
+$ nomad alloc exec 87ec7d12 /bin/sh
+# ls /
+bin   dev  home        lib    lib64   lost+found  mnt  proc  run   snap  sys  usr  vmlinuz
+boot  etc  initrd.img  lib32  libx32  media       opt  root  sbin  srv   tmp  var
+
+# echo $NOMAD_SECRETS_DIR
+/var/nomad/alloc/87ec7d12-5e35-8fba-96cc-09e5376be15a/task3/secrets
+
+# whoami
+root
+```
+
+## Templates, Artifacts, and Dispatch Payloads
+
+The other contents of the allocation working directory depend on what features
+the job specification uses. The allocation working directory is populated by
+other features in a specific order:
+
+- The allocation working directory is created.
+- The ephemeral disk data is [migrated] from any previous allocation.
+- [CSI volumes] are staged.
+- Then, for each task:
+  - Task working directories are created.
+  - [Dispatch payloads] are written.
+  - [Artifacts] are downloaded.
+  - [Templates] are rendered.
+  - The task is started by the task driver, which includes all bind mounts and
+    [volume mounts].
+
+Dispatch payloads, artifacts, and templates are written to the task working
+directory before a task can start because the resulting files may be binary or
+image run by the task. For example, an `artifact` can be used to download a
+Docker image or .jar file, or a `template` can be used to render a shell
+script that's run by `exec`.
+
+The `artifact` and `template` blocks write their data to a destination
+relative to the task working directory, not the `NOMAD_TASK_DIR`. For task
+drivers with `image` filesystem isolation, this means the `destination` field
+path should be prefixed with either `NOMAD_TASK_DIR` or
+`NOMAD_SECRETS_DIR`. Otherwise, the file will not be visible from inside the
+resulting container. (The `dispatch_payload` block always writes its data to
+the `NOMAD_TASK_DIR`.)
+
+For [CSI volumes], the client will stage the volume before setting up the task
+working directory. Staging typically involves mounting the volume into the CSI
+plugin's task directory, sending commands to the plugin to format the volume
+as required, and making a volume claim to the Nomad server.
+
+The behavior of the `volume_mount` block is controlled by the task driver. The
+client builds a mount configuration describing the host volume or CSI volume
+and passes it to the task driver to execute. Because the task driver mounts
+the volume, it is not possible to have `artifact`, `template`, or
+`dispatch_payload` blocks write to a volume.
+
+[artifacts]: /nomad/docs/job-specification/artifact
+[csi volumes]: /nomad/docs/concepts/plugins/csi
+[dispatch payloads]: /nomad/docs/job-specification/dispatch_payload
+[templates]: /nomad/docs/job-specification/template
+[`data_dir`]: /nomad/docs/configuration#data_dir
+[`ephemeral_disk`]: /nomad/docs/job-specification/ephemeral_disk
+[artifact]: /nomad/docs/job-specification/artifact
+[chroot contents]: /nomad/docs/drivers/exec#chroot
+[filesystem isolation capability]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[filesystem isolation mode]: #task-drivers-and-filesystem-isolation-modes
+[migrated]: /nomad/docs/job-specification/ephemeral_disk#migrate
+[template]: /nomad/docs/job-specification/template
+[volume mounts]: /nomad/docs/job-specification/volume_mount
diff --git a/content/nomad/v1.9.x/content/docs/concepts/gossip.mdx b/content/nomad/v1.9.x/content/docs/concepts/gossip.mdx
new file mode 100644
index 0000000000..efe8d15a56
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/gossip.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: Gossip Protocol
+description: |-
+  Learn how Nomad's gossip protocol uses the Serf library to provide server membership management, which includes cross-region requests, failure detection, and automatic clustering using a consensus protocol.
+---
+
+# Gossip Protocol
+
+This page provides conceptual information about Nomad's gossip protocol, which
+provides server membership management, cross-region requests, failure detection,
+and automatic clustering using a consensus protocol.
+
+Nomad uses the [Serf library][serf] to provide a [gossip
+protocol](https://en.wikipedia.org/wiki/Gossip_protocol) to manage membership.
+The gossip protocol used by Serf is based on ["SWIM: Scalable Weakly-consistent
+Infection-style Process Group Membership Protocol"][swim], with a few minor
+adaptations. There are more details about [Serf's protocol here][gossip].
+
+~> **Advanced Topic!** This page covers technical details of
+the internals of Nomad. You do not need to know these details to effectively
+operate and use Nomad. These details are documented here for those who wish
+to learn about them without having to go spelunking through the source code.
+
+## Gossip in Nomad
+
+Nomad makes use of a single global WAN gossip pool that all servers participate
+in. Membership information provided by the gossip pool allows servers to perform
+cross region requests. The integrated failure detection allows Nomad to
+gracefully handle an entire region losing connectivity, or just a single server
+in a remote region. Nomad also uses the gossip protocol to detect servers in the
+same region to perform automatic clustering via the [consensus
+protocol](/nomad/docs/concepts/consensus).
+
+To provide all these features, Nomad uses [Serf][serf] as an embedded
+library. From a user perspective, this is not important, since Nomad masks the
+abstraction. However, developers may find it useful to understand how Nomad
+leverages the Serf library.
+
+
+[serf]: https://github.com/hashicorp/serf
+[gossip]: https://github.com/hashicorp/serf/blob/master/docs/internals/gossip.html.markdown
+[swim]: https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf
diff --git a/content/nomad/v1.9.x/content/docs/concepts/index.mdx b/content/nomad/v1.9.x/content/docs/concepts/index.mdx
new file mode 100644
index 0000000000..f13be5647b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Concepts
+description: >-
+  Learn about Nomad's architecture, core concepts, and behavior.
+---
+
+# Nomad Concepts
+
+This section covers the core concepts of Nomad and explains the
+technical details of how Nomad functions, its architecture, and
+sub-systems.
diff --git a/content/nomad/v1.9.x/content/docs/concepts/job.mdx b/content/nomad/v1.9.x/content/docs/concepts/job.mdx
new file mode 100644
index 0000000000..effaa1b103
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/job.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: Job
+description: |-
+  Learn how a Nomad workload, called a job, deploys your apps, maintenance scripts, cron jobs, and similar tasks. Review job statuses and how Nomad versions your jobs.
+---
+
+# Job
+
+This page contains conceptual information about jobs, which are the main Nomad
+constructs for workloads that run your apps, maintenance scripts, cron jobs, and
+other tasks. Review job statuses and how Nomad versions your jobs.
+
+## Background
+
+In Nomad, a _job_ is a user-specified state for a workload. The user expresses the job that should be running, but not where it should run. Nomad allocates resources and ensures that the actual state matches the user's desired state. A job consists of one or more tasks that you can organize into [task groups][task-groups].
+
+Declare the desired state of your job in a [job specification][job-specification], or _jobspec_, that describes
+the tasks and resources necessary for the job to run. You can also
+include job constraints to control which clients Nomad runs the job on.
+
+When you submit your job specification, Nomad automatically allocates resources
+to run it. Nomad also makes sure that the actual
+job state matches your desired state.
+
+## Job statuses
+
+After you submit your job, Nomad assigns a status to indicate how a job is
+performing. This status indicates how the job's current allocations compare to
+the desired job state.
+
+@include 'job-status-map.mdx'
+
+### CLI statuses
+
+Only the CLI returns these job statuses.
+
+#### `running`
+
+The `running` status indicates that the job has non-terminal allocations.
+
+#### `dead`
+
+The `dead` status indicates that all evaluations and allocations are in a
+terminal state.
+
+#### `dead (stopped)`
+
+The `dead (stopped)` status indicates that a user has manually stopped the job.
+You may start this job again.
+
+### UI statuses
+
+These job statuses only appear in the Nomad UI.
+
+#### Complete
+
+The `Complete` status indicates that all expected allocations are complete. This
+status applies to batch and sysbatch jobs only.
+
+#### Degraded
+
+The `Degraded` status indicates that a [deployment] is not taking place. Some
+allocations are failed, lost, or unplaced.
+
+#### Deploying
+
+The `Deploying` status indicates that a deployment is actively taking place.
+
+#### Failed
+
+The `Failed` status indicates that all allocations are failed, lost, or unplaced.
+
+#### Healthy
+
+The `Healthy` status indicates that all expected allocations are running and
+healthy.
+
+#### Recovering
+
+The `Recovering` status indicates that some allocations are pending.
+
+#### Removed
+
+The `Removed` status indicates that the job appeared in the initial query, but
+the garbage collector has since removed the job. This happens when the user
+remains on the page for a long time.
+
+#### Running
+
+The `Running` status indicates that all expected allocations are running. This
+status applies to batch and sysbatch jobs only.
+
+#### Scaled Down
+
+The `Scaled Down` status indicates that a user has scaled all allocations to
+zero. Nomad's garbage collector has not yet removed or purged the job.
+
+#### Stopped
+
+The `Stopped` status indicates that a user has manually stopped the job.
+Nomad's garbage collector has not yet removed or purged the job.
+
+## Job versions
+
+Nomad creates a new version for your job each time you run your job. A job can
+have an unlimited number of versions, and version history is stored in state.
+Over time, Nomad garbage collects dead versions that do not have a version tag.
+
+### Tag a version
+
+When you want to save or pin a specific version, you need to create a version
+tag with a unique name and optional description. Nomad does not garbage collect
+tagged versions even when the tagged version is dead. This lets you revert to
+a previous version regardless of how old the tagged version is.
+
+You can create, modify, and remove tags using the CLI, API, and web UI. Refer to
+the [Job versions guide][job-versions-guide] for examples.
+
+### Compare versions
+
+You can compare the current job version to all previous versions or to a
+specific version. Additionally, you can compare two specific versions.
+
+Run commands like `nomad job history` to review differences between past versions
+of jobs and their immediate predecessors. Additionally, you can run `nomad job
+plan` to review the hypothetical difference of an update against the current job
+version.
+
+Refer to the [Compare versions section][compare-versions-section] of the Job
+versions guide for examples.
+
+### Revert to a previous version
+
+You can revert the current running job to a previous version. Nomad stops the
+running job and deploys the chosen version with a new version number.
+
+Refer to the [Revert to a version section][revert-version-section] of
+the Job versions guide for examples using the CLI, API, and web UI.
+
+### Clone and edit
+
+Using the web UI, you may clone a version as a new version of the same job or as
+a new job. After you select the version to clone, you may edit, plan, and run
+the new version.
+
+Because Nomad passes job version attributes using query parameters, you can copy
+the browser address bar URL on the **Jobs/Run** screen to send a link to an
+editable job spec.
+
+Refer to the [Clone a version section][clone-version-section] of
+the Job versions guide for cloning examples.
+
+## Related resources
+
+Refer to the following Nomad documentation pages for more information about
+jobs:
+
+- The [job specification][job-spec] contains detailed
+  configuration and examples.
+- The [Schedulers] page explains the different types of Nomad schedulers and how
+  those schedulers run jobs.
+
+These tutorial resources contain examples of different kinds of jobs and how to
+configure them:
+
+- The [Quick Start][quickstart] tutorials cover deploying an application and
+  its resources, which include parameterized and periodic jobs.
+- The [Deploy and Manage Jobs][deploy-jobs] tutorial contains examples of different types of jobs.
+- The [Create Nomad Job Specifications][job-spec-tutorial] collection explains several aspects of job creation, including parameterized jobs and deploying a Java app on Nomad.
+
+
+[allocations]: /nomad/docs/glossary#allocation
+[deployment]: /nomad/docs/glossary/#deployment
+[deploy-jobs]: /nomad/tutorials/manage-jobs/
+[job-spec]: /nomad/docs/job-specification
+[job-spec-tutorial]: /nomad/tutorials/job-specifications
+[quickstart]: /nomad/tutorials/get-started/gs-deploy-job
+[Schedulers]: /nomad/docs/schedulers
+[task-groups]: /nomad/docs/glossary#task-group
+[tasks]: /nomad/docs/glossary#task
+[job-versions-guide]: /nomad/tutorials/manage-jobs/jobs-version
+[compare-versions-section]: /nomad/tutorials/manage-jobs/jobs-version#compare-versions
+[revert-version-section]: /nomad/tutorials/manage-jobs/jobs-version#revert-to-a-version
+[clone-version-section]: /nomad/tutorials/manage-jobs/jobs-version#clone-a-version
diff --git a/content/nomad/v1.9.x/content/docs/concepts/node-pools.mdx b/content/nomad/v1.9.x/content/docs/concepts/node-pools.mdx
new file mode 100644
index 0000000000..8ca9a3ee6d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/node-pools.mdx
@@ -0,0 +1,379 @@
+---
+layout: docs
+page_title: Node Pools
+description: Nomad's node pools feature groups clients and segments infrastructure into logical units so that jobs have control over client allocation placement. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+---
+
+# Node Pools
+
+This page contains conceptual information about Nomad's node pools feature. Use
+node pools to group clients and segment infrastructure into logical units so
+that jobs control allocation placement. Review node pool replication in multi-region clusters, built-in node pools, node pool patterns, and enterprise features such as scheduler configuration, node pool governance, and multi-region jobs.
+
+Without node pools, allocations for a job can be placed in any eligible client
+in the cluster. Affinities and constraints can help express preferences for
+certain nodes, but they do not easily prevent other jobs from placing
+allocations in a set of nodes.
+
+Create a node pool using the [`nomad node pool apply`][cli_np_apply]
+command and passing a node pool [specification file][np_spec].
+
+```hcl
+# dev-pool.nomad.hcl
+node_pool "dev" {
+  description = "Nodes for the development environment."
+
+  meta {
+    environment = "dev"
+    owner       = "sre"
+  }
+}
+```
+
+```shell-session
+$ nomad node pool apply dev-pool.nomad.hcl
+Successfully applied node pool "dev"!
+```
+
+Clients can then be added to this node pool by setting the
+[`node_pool`][client_np] attribute in their configuration file, or using the
+equivalent [`-node-pool`][cli_agent_np] command line flag.
+
+```hcl
+client {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+To help streamline this process, nodes can create node pools on demand. If a
+client configuration references a node pool that does not exist yet, Nomad
+creates the node pool automatically on client registration.
+
+<Note>
+  This behavior does not apply to clients in non-authoritative regions. Refer
+  to <a href="#multi-region-clusters">Multi-region Clusters</a> for more
+  information.
+</Note>
+
+Jobs can then reference node pools using the [`node_pool`][job_np] attribute.
+
+```hcl
+job "app-dev" {
+  # ...
+  node_pool = "dev"
+  # ...
+}
+```
+
+Similarly to the `namespace` attribute, the node pool must exist beforehand,
+otherwise the job registration results in an error. Only nodes in the given
+node pool are considered for placement. If none are available the deployment
+is kept as pending until a client is added to the node pool.
+
+## Multi-region Clusters
+
+In federated multi-region clusters, node pools are automatically replicated
+from the authoritative region to all non-authoritative regions, and requests to
+create or modify a new node pool are forwarded from non-authoritative to the
+authoritative region.
+
+Since the replication data only flows in one direction, clients in
+non-authoritative regions are not able to create node pools on demand.
+
+A client in a non-authoritative region that references a node pool that does
+not exist yet is kept in the `initializing` status until the node pool is
+created and replicated to all regions.
+
+## Built-in Node Pools
+
+In addition to the user generated node pools Nomad automatically creates two
+built-in node pools that cannot be deleted nor modified.
+
+- `default`: Node pools are an optional feature of Nomad. The `node_pool`
+  attribute in both the client configuration and job files are optional. When
+  not specified, these values are set to use the `default` built-in node pool.
+
+- `all`: In some situations, it is useful to be able to run a job across all
+  clients in a cluster, regardless of their node pool configuration. For these
+  scenarios the job may use the built-in `all` node pool which always includes
+  all clients registered in the cluster. Unlike other node pools, the `all`
+  node pool can only be used in jobs and not in client configuration.
+
+## Nomad Enterprise <EnterpriseAlert inline />
+
+Nomad Enterprise provides additional features that make node pools more
+powerful and easier to manage.
+
+### Scheduler Configuration
+
+Node pools in Nomad Enterprise are able to customize some aspects of the Nomad
+scheduler and override certain global configuration per node pool.
+
+This allows experimenting with with functionalities such as memory
+oversubscription in isolation, or adjusting the scheduler algorithm between
+`spread` or `binpacking` depending on the types of workload being deployed in a
+given set of clients.
+
+When using the built-in `all` node pool the global scheduler configuration is
+applied.
+
+Refer to the [`scheduler_config`][np_spec_scheduler_config] parameter in the
+node pool specification for more information.
+
+### Node Pool Governance
+
+Node pools and namespaces share some similarities, with both providing a way to
+group resources in isolated logical units. Jobs are grouped into namespaces and
+clients into node pools.
+
+Node Pool Governance allows assigning a default node pool to a namespace that
+is automatically used by every job registered to the namespace. This feature
+simplifies job management as the node pool is inferred from the namespace
+configuration instead of having to be specified in every job.
+
+This connection is done using the [`default`][ns_spec_np_default] attribute in
+the namespace `node_pool_config  block.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+  }
+}
+```
+
+Now any job in the `dev` namespace only places allocations in nodes in the
+`dev` node pool, and so the `node_pool` attribute may be omitted from the job
+specification.
+
+```hcl
+job "app-dev" {
+  # The "dev" node pool will be used because it is the
+  # namespace's default node pool.
+  namespace = "dev"
+  # ...
+}
+```
+
+Jobs are able to override the namespace default node pool by specifying a
+different `node_pool` value.
+
+The namespace can enforce if this behavior is allowed or limit which node pools
+can and cannot be used with the [`allowed`][ns_spec_np_allowed] and
+[`denied`][ns_spec_np_denied] parameters.
+
+```hcl
+namespace "dev" {
+  description = "Jobs for the development environment."
+
+  node_pool_config {
+    default = "dev"
+    denied  = ["prod", "qa"]
+  }
+}
+```
+
+```hcl
+job "app-dev" {
+  namespace = "dev"
+
+  # Jobs in the "dev" namespace are not allowed to use the
+  # "prod" node pool and so this job will fail to register.
+  node_pool = "prod"
+  # ...
+}
+```
+
+### Multi-region Jobs
+
+Multi-region jobs can specify different node pools to be used in each region by
+overriding the top-level `node_pool` job value, or the namespace `default` node
+pool, in each `region` block.
+
+```hcl
+job "multiregion" {
+  node_pool = "dev"
+
+  multiregion {
+    # This region will use the top-level "dev" node pool.
+    region "north" {}
+
+    # While the regions bellow will use their own specific node pool.
+    region "east" {
+      node_pool = "dev-east"
+    }
+
+    region "west" {
+      node_pool = "dev-west"
+    }
+  }
+  # ...
+}
+```
+
+## Node Pool Patterns
+
+The sections below describe some node pool patterns that can be used to achieve
+specific goals.
+
+### Infrastructure and System Jobs
+
+This pattern illustrates an example where node pools are used to reserve nodes
+for a specific set of jobs while also allowing system jobs to cross node pools
+boundaries.
+
+It is common for Nomad clusters to have certain jobs that are focused on
+providing the underlying infrastructure for more business focused applications.
+Some examples include reverse proxies for traffic ingress, CSI plugins, and
+periodic maintenance jobs.
+
+These jobs can be isolated in their own namespace but they may have different
+scheduling requirements.
+
+Reverse proxies, and only reverse proxies, may need to run in clients that are
+exposed to public traffic, and CSI controller plugins may require clients to
+have high-privileged access to cloud resources and APIs.
+
+Other jobs, like CSI node plugins and periodic maintenance jobs, may need to
+run as `system` jobs in all clients of the cluster.
+
+Node pools can be used to achieve the isolation required by the first set of
+jobs, and the built-in `all` node pool can be used for the jobs that must run
+in every client. To keep them organized, all jobs are registered in the same
+`infra` namespace.
+
+```hcl
+job "ingress-proxy" {
+  namespace = "infra"
+  node_pool = "ingress"
+  # ...
+}
+```
+
+```hcl
+job "csi-controller" {
+  namespace = "infra"
+  node_pool = "csi-controllers"
+  # ...
+}
+```
+
+```hcl
+job "csi-nodes" {
+  namespace = "infra"
+  node_pool = "all"
+  # ...
+}
+```
+
+```hcl
+job "maintenance" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+Use positive and negative constraints to fine-tune placements when targeting
+the built-in `all` node pool.
+
+```hcl
+job "maintenance-linux" {
+  type      = "batch"
+  namespace = "infra"
+  node_pool = "all"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  constraint {
+    attribute = "${node.pool}"
+    operator  = "!="
+    value     = "ingress"
+  }
+
+  periodic { /* ... */ }
+  # ...
+}
+```
+
+With Nomad Enterprise and Node Pool Governance, the `infra` namespace can be
+configured to use a specific namespace by default and only allow the specific
+node pools required.
+
+```hcl
+namespace "infra" {
+  description = "Infrastructure jobs."
+
+  node_pool_config {
+    default = "infra"
+    allowed = ["ingress", "csi-controllers", "all"]
+  }
+}
+```
+
+### Mixed Scheduling Algorithms
+
+This pattern illustrate an example where different scheduling algorithms are
+per node pool.
+
+Each of the scheduling algorithms provided by Nomad are best suited for
+different types of environments and workloads.
+
+The `binpack` algorithm aims to maximize resource usage and pack as much
+workload as possible in the given set of of clients. This makes it ideal for
+cloud environments where infrastructure is billed by the hour and can be
+quickly scaled in and out. By maximizing workload density a cluster running in
+cloud instances can reduce the number of clients needed to run everything that
+is necessary.
+
+The `spread` algorithm behaves in the opposite direction, making use of every
+client available to reduce density and potential noisy neighbors and resource
+contention. This makes it ideal for environments where clients are
+pre-provisioned and scale more slowly, such as on-premises deployments.
+
+Clusters in a mixed environment can use node pools to adjust the scheduler
+algorithm per node type. Cloud instances may be placed in a node pool that uses
+the `binpack` algorithm while bare-metal nodes are placed in a node pool
+configured to use `spread`.
+
+```hcl
+node_pool "cloud" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "binpack"
+  }
+}
+```
+
+```hcl
+node_pool "on-prem" {
+  # ...
+  scheduler_config {
+    scheduler_algorithm = "spread"
+  }
+}
+```
+
+Another scenario where mixing algorithms may be useful is to separate workloads
+that are more sensitive to noisy neighbors (and thus use the `spread`
+algorithm), from those that are able to be packed more tightly (`binpack`).
+
+[cli_np_apply]: /nomad/docs/commands/node-pool/apply
+[cli_agent_np]: /nomad/docs/commands/agent#node-pool
+[client_np]: /nomad/docs/configuration/client#node_pool
+[job_np]: /nomad/docs/job-specification/job#node_pool
+[np_spec]: /nomad/docs/other-specifications/node-pool
+[np_spec_scheduler_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
+[ns_spec_np_allowed]: /nomad/docs/other-specifications/namespace#allowed
+[ns_spec_np_default]: /nomad/docs/other-specifications/namespace#default
+[ns_spec_np_denied]: /nomad/docs/other-specifications/namespace#denied
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/base.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..c5a4638a23
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/base.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: Nomad Base Plugin
+description:  |-
+  Learn how to create a Nomad plugin so you can extend Nomad's task and device driver features. Review device plugin API functions that you must implement in your device plugin.
+---
+
+# Nomad Base Plugin
+
+This page provides conceptual information on Nomad's base plugin, which is a
+special plugin type implemented by all plugins. The base plugin allows for
+common plugin operations such as defining a configuration schema and version
+information.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfoResponse, error)`
+
+A `PluginInfoResponse` contains meta data about the plugin.
+
+```go
+PluginInfoResponse{
+    // Type is the plugin type which is implemented
+    Type: PluginTypeDriver,
+    // Plugin API versions supported by the plugin
+    PluginApiVersions: []string{drivers.ApiVersion010},
+    // Version of the plugin
+    PluginVersion: "0.1.0",
+    // Name of the plugin
+    Name: "foodriver",
+}
+```
+
+#### `ConfigSchema() (*hclspec.Spec, error)`
+
+The `ConfigSchema` function allows a plugin to tell Nomad the schema for its
+configuration. This configuration is given in a [plugin block][pluginblock] of
+the client configuration. The schema is defined with the [hclspec][hclspec]
+package.
+
+#### `SetConfig(config *Config) error`
+
+The `SetConfig` function is called when starting the plugin for the first
+time. The `Config` given has two different configuration fields. The first
+`PluginConfig`, is an encoded configuration from the `plugin` block of the
+client config. The second, `AgentConfig`, is the Nomad agent's configuration
+which is given to all plugins.
+
+## HCL Specifications
+
+`*hclspec.Spec` is a struct that defines the schema to validate an HCL entity
+against. The full documentation of the different hcl attribute types can be
+found on the [hclspec godoc][hclspec].
+
+For a basic example, lets look at the driver configuration for the raw_exec
+driver:
+
+```hcl
+job "example" {
+...
+      driver = "raw_exec"
+      config {
+        command = "/bin/sleep"
+        args = ["100"]
+      }
+}
+```
+
+The `config` block is what is validated against the `hclspec.Spec`. It has two
+keys, command which takes a string attribute and args which takes an array
+attribute. The corresponding `*hclspec.Spec` would be:
+
+```go
+    spec :=  hclspec.NewObject(map[string]*hclspec.Spec{
+		"command": hclspec.NewAttr("command", "string", true),
+		"args":    hclspec.NewAttr("args", "list(string)", false),
+	})
+```
+
+[hclspec]: https://godoc.org/github.com/hashicorp/nomad/plugins/shared/hclspec
+[pluginblock]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/cni.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/cni.mdx
new file mode 100644
index 0000000000..832bdc1ef2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/cni.mdx
@@ -0,0 +1,67 @@
+---
+layout: docs
+page_title: Network Plugins
+description:  |-
+  Nomad's network plugin support enables scheduling tasks with custom network configuration plugins that conform to the Container Network Interface (CNI). Learn about the CNI reference plugins that are required for Nomad bridge networking and Consul service mesh.
+---
+
+# Network plugins
+
+This page provides conceptual information on Nomad's network plugin support, which enables scheduling tasks with custom network configuration plugins that conform to the Container Network Interface (CNI). Learn about the CNI reference plugins that are required for Nomad bridge networking and Consul service mesh.
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's network plugin support extends
+this to allow scheduling tasks with purpose-created or specialty network
+configurations. Network plugins are third-party plugins that conform to the
+[Container Network Interface (CNI)][cni_spec] specification.
+
+Network plugins need to be installed and configured on each client. The [Nomad
+installation instructions][nomad_install] recommend installing the [CNI
+reference plugins][cni_ref] because certain Nomad networking features, like
+`bridge` network mode and Consul service mesh, leverage them to provide an
+operating-system agnostic interface to configure workload networking.
+
+Custom networking in Nomad is accomplished with a combination of CNI plugin
+binaries and CNI configuration files.
+
+## CNI plugins
+
+Spec-compliant plugins should work with Nomad, however, it's possible a plugin
+vendor has implemented their plugin to make non-standard API calls, or it is
+otherwise non-compliant with the CNI specification. In those situations the
+plugin may not function correctly in a Nomad environment. You should verify
+plugin compatibility with Nomad before deploying in production.
+
+CNI plugins are installed and configured on a per-client basis. Nomad consults
+the path given in the client's [`cni_path`][] to find CNI plugin executables.
+
+## CNI configuration files
+
+CNI defines a network configuration format for administrators. It contains
+directives for both the orchestrator and the plugins to consume.
+At plugin execution time, this configuration format is interpreted by the
+runtime and transformed in to a form to be passed to the plugins.
+
+Nomad reads the following extensions from the [`cni_config_dir`][]—
+`/opt/cni/config` by default:
+
+* `.conflist` files are loaded as [network
+  configurations][cni_spec_net_config] that contain a list of plugin
+  configurations.
+
+* `.conf` and `.json` files are loaded as individual [plugin
+  configurations][cni_spec_plugin_config] for a specific network.
+
+## Further reading
+
+You can read more about how Nomad uses CNI plugins in the [CNI section of the
+Nomad Networking documentation](/nomad/docs/networking/cni).
+
+[3rd_party_cni]: https://www.cni.dev/docs/#3rd-party-plugins
+[`cni_config_dir`]: /nomad/docs/configuration/client#cni_config_dir
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
+[cni_ref]: https://github.com/containernetworking/plugins
+[cni_spec]: https://www.cni.dev/docs/spec/
+[cni_spec_net_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#configuration-format
+[cni_spec_plugin_config]: https://github.com/containernetworking/cni/blob/main/SPEC.md#plugin-configuration-objects
+[nomad_install]: /nomad/tutorials/get-started/get-started-install#linux-post-installation-steps
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/csi.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/csi.mdx
new file mode 100644
index 0000000000..b4d8bf058c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/csi.mdx
@@ -0,0 +1,145 @@
+---
+layout: docs
+page_title: Storage Plugins
+description: |-
+  Nomad's storage plugin support enables scheduling tasks with external storage volumes that conform to the Container Storage Interface (CSI), including AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, Ceph, and Portworx. Learn about controller, node, and monolith storage plugins, as well as storage volume lifecyle.
+---
+
+# Storage Plugins
+
+This page provides conceptual information on Nomad's storage plugin support, which enables scheduling tasks with external storage volumes that conform to the Container Storage Interface (CSI), including AWS Elastic Block Storage (EBS) volumes, Google Cloud Platform (GCP) persistent disks, Ceph, and Portworx. Learn about controller, node, and monolith storage plugins, as well as storage volume lifecyle.
+
+Nomad has built-in support for scheduling compute resources such as
+CPU, memory, and networking. Nomad's storage plugin support extends
+this to allow scheduling tasks with externally created storage
+volumes. Storage plugins are third-party plugins that conform to the
+[Container Storage Interface (CSI)][csi-spec] specification.
+
+Storage plugins are created dynamically as Nomad jobs, unlike device
+and task driver plugins that need to be installed and configured on
+each client. Each dynamic plugin type has its own type-specific job
+spec block; currently there is only the `csi_plugin` type. Nomad
+tracks which clients have instances of a given plugin, and
+communicates with plugins over a Unix domain socket that it creates
+inside the plugin's tasks.
+
+## CSI Plugins
+
+Every storage vendor has its own APIs and workflows, and the industry-standard
+Container Storage Interface specification unifies these APIs in a way that's
+agnostic to both the storage vendor and the container orchestrator. Each storage
+provider can build its own CSI plugin. Jobs can claim storage volumes from AWS
+Elastic Block Storage (EBS) volumes, GCP persistent disks, Ceph, Portworx,
+etc. The Nomad scheduler will be aware of volumes created by CSI plugins and
+schedule workloads based on the availability of volumes on a given Nomad client
+node.
+
+A list of available CSI plugins can be found in the [Kubernetes CSI
+documentation][csi-drivers-list]. Spec-compliant plugins should work with Nomad.
+However, it is possible a plugin vendor has implemented their plugin to make
+Kubernetes API calls, or is otherwise non-compliant with the CSI
+specification. In those situations the plugin may not function correctly in a
+Nomad environment. You should verify plugin compatibility with Nomad before
+deploying in production.
+
+A CSI plugin task requires the [`csi_plugin`][csi_plugin] block:
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+}
+```
+
+There are three **types** of CSI plugins. **Controller Plugins**
+communicate with the storage provider's APIs. For example, for a job
+that needs an AWS EBS volume, Nomad will tell the controller plugin
+that it needs a volume to be "published" to the client node, and the
+controller will make the API calls to AWS to attach the EBS volume to
+the right EC2 instance. **Node Plugins** do the work on each client
+node, like creating mount points. **Monolith Plugins** are plugins
+that perform both the controller and node roles in the same
+instance. Not every plugin provider has or needs a controller; that's
+specific to the provider implementation.
+
+Plugins mount and unmount volumes but are not in the data path once
+the volume is mounted for a task. Plugin tasks are needed when tasks
+using their volumes stop, so plugins should be left running on a Nomad
+client until all tasks using their volumes are stopped. The `nomad
+node drain` command handles this automatically by stopping plugin
+tasks last.
+
+Typically, you should run node plugins as Nomad `system` jobs so they
+can mount volumes on any client where they are running. Controller
+plugins can create and attach volumes anywhere they can communicate
+with the storage provider's API, so they can usually be run as
+`service` jobs. You should always run more than one controller plugin
+allocation for high availability.
+
+Nomad exposes a Unix domain socket named `csi.sock` inside each CSI
+plugin task, and communicates over the gRPC protocol expected by the
+CSI specification. The `mount_dir` field tells Nomad where the plugin
+expects to find the socket file. The path to this socket is exposed in
+the container as the `CSI_ENDPOINT` environment variable.
+
+Some plugins also require the `stage_publish_base_dir` field, which
+tells Nomad where to instruct the plugin to mount volumes for staging
+and/or publishing.
+
+### Plugin Lifecycle and State
+
+CSI plugins report their health like other Nomad jobs. If the plugin
+crashes or otherwise terminates, Nomad will launch it again using the
+same `restart` and `reschedule` logic used for other jobs. If plugins
+are unhealthy, Nomad will mark the volumes they manage as
+"unscheduable".
+
+Storage plugins don't have any responsibility (or ability) to monitor
+the state of tasks that claim their volumes. Nomad sends mount and
+publish requests to storage plugins when a task claims a volume, and
+unmount and unpublish requests when a task stops.
+
+The dynamic plugin registry persists state to the Nomad client so that
+it can restore volume managers for plugin jobs after client restarts
+without disrupting storage.
+
+### Volume Lifecycle
+
+The Nomad scheduler decides whether a given client can run an
+allocation based on whether it has a node plugin present for the
+volume. But before a task can use a volume the client needs to "claim"
+the volume for the allocation. The client makes an RPC call to the
+server and waits for a response; the allocation's tasks won't start
+until the volume has been claimed and is ready.
+
+If the volume's plugin requires a controller, the server will send an
+RPC to any Nomad client where that controller is running. The Nomad
+client will forward this request over the controller plugin's gRPC
+socket. The controller plugin will make the request volume available
+to the node that needs it.
+
+Once the controller is done (or if there's no controller required),
+the server will increment the count of claims on the volume and return
+to the client. This count passes through Nomad's state store so that
+Nomad has a consistent view of which volumes are available for
+scheduling.
+
+The client then makes RPC calls to the node plugin running on that
+client, and the node plugin mounts the volume to a staging area in
+the Nomad data directory. Nomad will bind-mount this staged directory
+into each task that mounts the volume.
+
+This cycle is reversed when a task that claims a volume becomes
+terminal. The client frees the volume locally by making "unpublish"
+RPCs to the node plugin. The node plugin unmounts the bind-mount from
+the allocation and unmounts the volume from the plugin (if it's not in
+use by another task). The client will then send an "unpublish" RPC to
+the server, which will forward it to the controller plugin (if
+any), and decrement the claim count for the volume. At this point the
+volume’s claim capacity has been freed up for scheduling.
+
+[csi-spec]: https://github.com/container-storage-interface/spec
+[csi-drivers-list]: https://kubernetes-csi.github.io/docs/drivers.html
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/devices.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/devices.mdx
new file mode 100644
index 0000000000..25d210675f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/devices.mdx
@@ -0,0 +1,84 @@
+---
+layout: docs
+page_title: Device Plugins
+description: |-
+  Learn how to create a Nomad device plugin so you can schedule workload tasks with other devices, such as GPUs. Review device plugin lifecycle and the device plugin API functions that you must implement in your device plugin.
+---
+
+# Device Plugins
+
+This page provides conceptual information for creating a device driver plugin to extend Nomad's workload execution functionality.
+
+Nomad has built-in support for scheduling compute resources such as CPU, memory,
+and networking. Nomad device plugins are used to support scheduling tasks with
+other devices, such as GPUs. They are responsible for fingerprinting these
+devices and working with the Nomad client to make them available to assigned
+tasks.
+
+For a real world example of a Nomad device plugin implementation, refer to the [Nvidia
+GPU plugin](https://github.com/hashicorp/nomad-device-nvidia).
+
+## Authoring Device Plugins
+
+Authoring a device plugin in Nomad consists of implementing the
+[DevicePlugin][deviceplugin] interface alongside
+a main package to launch the plugin.
+
+The [device plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new device plugins. It provides most of the boilerplate
+necessary for a device plugin, along with detailed comments.
+
+### Lifecycle and State
+
+A device plugin is long-lived. Nomad will ensure that one instance of the plugin is
+running. If the plugin crashes or otherwise terminates, Nomad will launch another
+instance of it.
+
+However, unlike [task drivers](/nomad/docs/concepts/plugins/task-drivers), device plugins do not currently
+have an interface for persisting state to the Nomad client. Instead, the device
+plugin API emphasizes fingerprinting devices and reporting their status. After
+helping to provision a task with a scheduled device, a device plugin does not
+have any responsibility (or ability) to monitor the task.
+
+## Device Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `Fingerprint(context.Context) (<-chan *FingerprintResponse, error)`
+
+The `Fingerprint` [function][fingerprintfn] is called by the client when the plugin is started.
+It allows the plugin to provide Nomad with a list of discovered devices, along with their
+attributes, for the purpose of scheduling workloads using devices.
+The channel returned should immediately send an initial
+[`FingerprintResponse`][fingerprintresponse], then send periodic updates at
+an appropriate interval until the context is canceled.
+
+Each fingerprint response consists of either an error or a list of device groups.
+A device group is a list of detected devices that are identical for the purpose of
+scheduling; that is, they will have identical attributes.
+
+### `Stats(context.Context, time.Duration) (<-chan *StatsResponse, error)`
+
+The `Stats` [function][statsfn] returns a channel on which the plugin should
+emit device statistics, at the specified interval, until either an error is
+encountered or the specified context is cancelled. The `StatsReponse` object
+allows [dimensioned][dimensioned] statistics to be returned for each device in a device group.
+
+### `Reserve(deviceIDs []string) (*ContainerReservation, error)`
+
+The `Reserve` [function][reservefn] accepts a list of device IDs and returns the information
+necessary for the client to make those devices available to a task. Currently,
+the `ContainerReservation` object allows the plugin to specify environment
+variables for the task, as well as a list of host devices and files to be mounted
+into the task's filesystem. Any orchestration required to prepare the device for
+use should also be performed in this function.
+
+[deviceplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L20-L33
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-device-plugin
+[fingerprintresponse]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/device/device.go#L37-L43
+[fingerprintfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L159-L165
+[statsfn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L169-L176
+[reservefn]: https://github.com/hashicorp/nomad-skeleton-device-plugin/blob/v0.1.0/device/device.go#L189-L245
+[dimensioned]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/shared/structs/stats.go#L33-L34
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/index.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..9bfbe0c0c7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/index.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn how Nomad's task and device driver plugins extend a workload's supported functions.
+---
+
+# Plugins
+
+This page provides conceptual information on task and device driver plugins.
+
+Nomad implements a plugin framework which lets you extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/docs/concepts/plugins/task-drivers)
+- [Devices](/nomad/docs/concepts/plugins/devices)
+
+## Architecture
+
+The Nomad plugin framework uses the [go-plugin][goplugin] project to expose
+a language independent plugin interface. Plugins implement a set of gRPC
+services and methods which Nomad manages by running the plugin and calling the
+implemented RPCs. This means that plugins are free to be implemented in the
+author's language of choice.
+
+To make plugin development easier, a set of go interfaces and structs exist for
+each plugin type that abstract away go-plugin and the gRPC interface. The
+guides in this documentation reference these abstractions for ease of use.
+
+[goplugin]: https://github.com/hashicorp/go-plugin
diff --git a/content/nomad/v1.9.x/content/docs/concepts/plugins/task-drivers.mdx b/content/nomad/v1.9.x/content/docs/concepts/plugins/task-drivers.mdx
new file mode 100644
index 0000000000..3d3a3a5df1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/plugins/task-drivers.mdx
@@ -0,0 +1,254 @@
+---
+layout: docs
+page_title: Task Driver Plugins
+description: Learn how to create a Nomad task driver plugin to extend Nomad's workload execution functionality.
+---
+
+# Task Driver Plugins
+
+This page provides conceptual information for creating a task driver plugin to extend Nomad's workload execution functionality.
+
+Task drivers in Nomad are the runtime components that execute workloads. For
+a real world example of a Nomad task driver plugin implementation, refer to the [exec2 driver][].
+
+## Authoring Task Driver Plugins
+
+Authoring a task driver (shortened to driver in this documentation) in Nomad
+consists of implementing the [DriverPlugin][driverplugin] interface and adding
+a main package to launch the plugin. A driver plugin is long-lived and its
+lifetime is not bound to the Nomad client. This means that the Nomad client can
+be restarted without restarting the driver. Nomad will ensure that one
+instance of the driver is running, meaning if the driver crashes or otherwise
+terminates, Nomad will launch another instance of it.
+
+Drivers should maintain as little state as possible. State for a task is stored
+by the Nomad client on task creation. This enables a pattern where the driver
+can maintain an in-memory state of the running tasks, and if necessary the
+Nomad client can recover tasks into the driver state.
+
+The [driver plugin skeleton project][skeletonproject] exists to help bootstrap
+the development of new driver plugins. It provides most of the boilerplate
+necessary for a driver plugin, along with detailed comments.
+
+## Task Driver Plugin API
+
+The [base plugin][baseplugin] must be implemented in addition to the following
+functions.
+
+### `TaskConfigSchema() (*hclspec.Spec, error)`
+
+This function returns the schema for the driver configuration of the task. For
+more information on `hclspec.Spec` see the HCL section in the [base
+plugin][baseplugin] documentation.
+
+### `Capabilities() (*Capabilities, error)`
+
+Capabilities define what features the driver implements. Example:
+
+```go
+type Capabilities struct {
+    // SendSignals marks the driver as being able to send signals
+    SendSignals bool
+
+    // Exec marks the driver as being able to execute arbitrary commands
+    // such as health checks. Used by the ScriptExecutor interface.
+    Exec bool
+
+    //FSIsolation indicates what kind of filesystem isolation the driver supports.
+    FSIsolation fsisolation.Mode
+
+    //NetIsolationModes lists the set of isolation modes supported by the driver
+    NetIsolationModes []NetIsolationMode
+
+    // MustInitiateNetwork tells Nomad that the driver must create the network
+    // namespace and that the CreateNetwork and DestroyNetwork RPCs are implemented.
+    MustInitiateNetwork bool
+
+    // MountConfigs tells Nomad which mounting config options the driver supports.
+    MountConfigs MountConfigSupport
+
+    // RemoteTasks indicates this driver runs tasks on remote systems
+    // instead of locally. The Nomad client can use this information to
+    // adjust behavior such as propagating task handles between allocations
+    // to avoid downtime when a client is lost.
+    RemoteTasks bool
+
+    // DisableLogCollection indicates this driver has disabled log collection
+    // and the client should not start a logmon process.
+    DisableLogCollection bool
+
+    // DynamicWorkloadUsers indicates this driver is capable (but not required)
+    // of making use of a UID/GID not backed by a user known to the operating
+    // system. The allocation of a unique, not-in-use UID/GID is managed by the
+    // Nomad client ensuring no overlap.
+    DynamicWorkloadUsers bool
+}
+```
+
+The file system isolation options are:
+
+- `fsisolation.Image`: The task driver isolates tasks as machine images.
+- `fsisolation.Chroot`: The task driver isolates tasks with `chroot` or
+  `pivot_root`.
+- `fsisolation.Unveil`: The task driver isolates tasks with the
+  [Landlock LSM][landlock] or other [`unveil`][unveil] like system.
+- `fsisolation.None`: The task driver has no filesystem isolation.
+
+The network isolation modes are:
+
+- `NetIsolationModeHost`: The task driver supports disabling network isolation
+  and using the host network.
+- `NetIsolationModeGroup`: The task driver supports using the task group
+  network namespace.
+- `NetIsolationModeTask`: The task driver supports isolating the network to
+  just the task.
+- `NetIsolationModeNone`: There is no network to isolate. This is used for
+  task that the client manages remotely.
+
+### `Fingerprint(context.Context) (<-chan *Fingerprint, error)`
+
+This function is called by the client when the plugin is started. It allows the
+driver to indicate its health to the client. The channel returned should
+immediately send an initial Fingerprint, then send periodic updates at an
+interval that is appropriate for the driver until the context is canceled.
+
+The fingerprint consists of a `HealthState` and `HealthDescription` to inform
+the client about its health. Additionally an `Attributes` field is available
+for the driver to add additional attributes to the client node. The fingerprint
+`HealthState` can be one of three states.
+
+- `HealthStateUndetected`: Indicates that the necessary dependencies for the
+  driver are not detected on the system. Ex. java runtime for the java driver
+- `HealthStateUnhealthy`: Indicates that something is wrong with the driver
+  runtime. Ex. docker daemon stopped for the Docker driver
+- `HealthStateHealthy`: All systems go
+
+### `StartTask(*TaskConfig) (*TaskHandle, *DriverNetwork, error)`
+
+This function takes a [`TaskConfig`][taskconfig] which includes all of the configuration
+needed to launch the task. Additionally the driver configuration can be decoded
+from the `TaskConfig` by calling `*TaskConfig.DecodeDriverConfig(t interface{})`
+passing in a pointer to the driver specific configuration struct. The
+`TaskConfig` includes an `ID` field which future operations on the task will be
+referenced by.
+
+Drivers return a [`*TaskHandle`][taskhandle] which contains
+the required information for the driver to reattach to the running task in the
+case of plugin crashes or restarts. Some of this required state
+will be specific to the driver implementation, thus a `DriverState` field
+exists to allow the driver to encode custom state into the struct. Helper
+fields exist on the `TaskHandle` to `GetDriverState` and `SetDriverState`
+removing the need for the driver to handle serialization.
+
+A `*DriverNetwork` can optionally be returned to describe the network of the
+task if it is modified by the driver. An example of this is in the Docker
+driver where tasks can be attached to a specific Docker network.
+
+If an error occurs, it is expected that the driver will cleanup any created
+resources prior to returning the error.
+
+#### Logging
+
+Nomad handles all rotation and plumbing of task logs. In order for task stdout
+and stderr to be received by Nomad, they must be written to the correct
+location. Prior to starting the task through the driver, the Nomad client
+creates FIFOs for stdout and stderr. These paths are given to the driver in the
+`TaskConfig`. The [`fifo` package][fifopackage] can be used to support
+cross platform writing to these paths.
+
+#### Dynamic Workload Users
+
+Nomad is capable of dynamically allocating unused UID/GID values for use by
+task drivers when launching a task. These UID/GID values are deallocated when
+the task is destroyed. The pool of available UID/GID values can be controlled
+in client config via the [users][users] block.
+
+#### TaskHandle Schema Versioning
+
+A `Version` field is available on the TaskHandle struct to facilitate backwards
+compatible recovery of tasks. This field is opaque to Nomad, but allows the
+driver to handle recover tasks that were created by an older version of the
+plugin.
+
+### `RecoverTask(*TaskHandle) error`
+
+When a driver is restarted it is not expected to persist any internal state to
+disk. To support this, Nomad will attempt to recover a task that was
+previously started if the driver does not recognize the task ID. During task
+recovery, Nomad calls `RecoverTask` passing the `TaskHandle` that was
+returned by the `StartTask` function. If no error was returned, it is
+expected that the driver can now operate on the task by referencing the task
+ID. If an error occurs, the Nomad client will mark the task as `lost`.
+
+### `WaitTask(context.Context, id string) (<-chan *ExitResult, error)`
+
+The `WaitTask` function is expected to return a channel that will send an
+`*ExitResult` when the task exits or close the channel when the context is
+canceled. It is also expected that calling `WaitTask` on an exited task will
+immediately send an `*ExitResult` on the returned channel.
+
+### `StopTask(taskID string, timeout time.Duration, signal string) error`
+
+The `StopTask` function is expected to stop a running task by sending the given
+signal to it. If the task does not stop during the given timeout, the driver
+must forcefully kill the task.
+
+`StopTask` does not clean up resources of the task or remove it from the
+driver's internal state. A call to `WaitTask` after `StopTask` is valid and
+should be handled.
+
+### `DestroyTask(taskID string, force bool) error`
+
+The `DestroyTask` function cleans up and removes a task that has terminated. If
+force is set to true, the driver must destroy the task even if it is still
+running. If `WaitTask` is called after `DestroyTask`, it should return
+`drivers.ErrTaskNotFound` as no task state should exist after `DestroyTask` is
+called.
+
+### `InspectTask(taskID string) (*TaskStatus, error)`
+
+The `InspectTask` function returns detailed status information for the
+referenced `taskID`.
+
+### `TaskStats(context.Context, id string, time.Duration) (<-chan *cstructs.TaskResourceUsage, error)`
+
+The `TaskStats` function returns a channel which the driver should send stats
+to at the given interval. The driver must send stats at the given interval
+until the given context is canceled or the task terminates.
+
+### `TaskEvents(context.Context) (<-chan *TaskEvent, error)`
+
+The Nomad client publishes events associated with an allocation. The
+`TaskEvents` function allows the driver to publish driver specific events about
+tasks and the Nomad client will associate them with the correct allocation.
+
+An `Eventer` utility is available in the
+`github.com/hashicorp/nomad/drivers/shared/eventer` package implements an
+event loop and publishing mechanism for use in the `TaskEvents` function.
+
+### `SignalTask(taskID string, signal string) error`
+
+> Optional - can be skipped by embedding `drivers.DriverSignalTaskNotSupported`
+
+The `SignalTask` function is used by drivers which support sending OS signals
+(`SIGHUP`, `SIGKILL`, `SIGUSR1` etc.) to the task. It is an optional function
+and is listed as a capability in the driver `Capabilities` struct.
+
+### `ExecTask(taskID string, cmd []string, timeout time.Duration) (*ExecTaskResult, error)`
+
+> Optional - can be skipped by embedding `drivers.DriverExecTaskNotSupported`
+
+The `ExecTask` function is used by the Nomad client to execute commands inside
+the task execution context. For example, the Docker driver executes commands
+inside the running container. `ExecTask` is called for Consul script checks.
+
+[exec2 driver]: https://github.com/hashicorp/nomad-driver-exec2
+[driverplugin]: https://github.com/hashicorp/nomad/blob/v0.9.0/plugins/drivers/driver.go#L39-L57
+[skeletonproject]: https://github.com/hashicorp/nomad-skeleton-driver-plugin
+[baseplugin]: /nomad/docs/concepts/plugins/base
+[taskconfig]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskConfig
+[taskhandle]: https://godoc.org/github.com/hashicorp/nomad/plugins/drivers#TaskHandle
+[fifopackage]: https://godoc.org/github.com/hashicorp/nomad/client/lib/fifo
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[unveil]: https://man.openbsd.org/unveil
+[users]: /nomad/docs/configuration/client#users-block
diff --git a/content/nomad/v1.9.x/content/docs/concepts/scheduling/index.mdx b/content/nomad/v1.9.x/content/docs/concepts/scheduling/index.mdx
new file mode 100644
index 0000000000..7a538ecd7b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/scheduling/index.mdx
@@ -0,0 +1,20 @@
+---
+layout: docs
+page_title: Scheduling workloads
+description: Nomad's scheduling component assigns jobs to client machines. Explore scheduling internals, placement, and preemption.
+---
+
+# Scheduling workloads
+
+Scheduling workloads is the process of assigning tasks from jobs to client machines. 
+It is one of Nomad's core functions. The design is heavily inspired by Google's
+work on both [Omega: flexible, scalable schedulers for large compute
+clusters][omega] and [Large-scale cluster management at Google with Borg][borg].
+Refer to the links below for implementation details on scheduling in Nomad.
+
+- [Scheduling Internals](/nomad/docs/concepts/scheduling/scheduling) - An overview of how the scheduler works.
+- [Placement](/nomad/docs/concepts/scheduling/placement) - Explains how placements are computed and how they can be adjusted.
+- [Preemption](/nomad/docs/concepts/scheduling/preemption) - Details of preemption, an advanced scheduler feature.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
diff --git a/content/nomad/v1.9.x/content/docs/concepts/scheduling/placement.mdx b/content/nomad/v1.9.x/content/docs/concepts/scheduling/placement.mdx
new file mode 100644
index 0000000000..f4c7eadfce
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/scheduling/placement.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: Allocation Placement
+description: Nomad uses allocation placement when scheduling jobs to run on clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+---
+
+# Allocation Placement
+
+This page provides conceptual information about job allocation placement on
+clients. Learn about using affinities, constraints, datacenters, and node pools to specify allocation placement.
+
+When the Nomad scheduler receives a job registration request, it needs to
+determine which clients will run allocations for the job.
+
+This process is called allocation placement and can be important to understand
+it to help achieve important goals for your applications, such as high
+availability and resilience.
+
+By default, all nodes are considered for placements but this process can be
+adjusted via agent and job configuration.
+
+There are several options that can be used depending on the desired outcome.
+
+## Affinities and Constraints
+
+Affinities and constraints allow users to define soft or hard requirements for
+their jobs. The [`affinity`][job_affinity] block specifies a soft requirement
+on certain node properties, meaning allocations for the job have a preference
+for some nodes, but may be placed elsewhere if the rules can't be matched,
+while the [`constraint`][job_constraint] block creates hard requirements and
+allocations can only be placed in nodes that match these rules. Job placement
+fails if a constraint cannot be satisfied.
+
+These rules can reference intrinsic node characteristics, which are called
+[node attributes][] and are automatically detected by Nomad, static values
+defined in the agent configuration file by cluster administrators, or dynamic
+values defined after the agent starts.
+
+One restriction of using affinities and constraints is that they only express
+relationships from jobs to nodes, so it is not possible to use them to restrict
+a node to only receive allocations for specific jobs.
+
+Use affinities and constraints when some jobs have certain node preferences or
+requirements but it is acceptable to have other jobs sharing the same nodes.
+
+The sections below describe the node values that can be configured and used in
+job affinity and constraint rules.
+
+### Node Class
+
+Node class is an arbitrary value that can be used to group nodes based on some
+characteristics, like the instance size or the presence of fast hard drives,
+and is specified in the client configuration file using the
+[`node_class`][config_client_node_class] parameter.
+
+### Dynamic and Static Node Metadata
+
+Node metadata are arbitrary key-value mappings specified either in the client
+configuration file using the [`meta`][config_client_meta] parameter or
+dynamically via the [`nomad node meta`][cli_node_meta] command and the
+[`/v1/client/metadata`][api_client_metadata] API endpoint.
+
+There are no preconceived use cases for metadata values, and each team may
+choose to use them in different ways. Some examples of static metadata include
+resource ownership, such as `owner = "team-qa"`, or fine-grained locality,
+`rack = "3"`. Dynamic metadata may be used to track runtime information, such
+as jobs running in a given client.
+
+## Datacenter
+
+Datacenters represent a geographical location in a region that can be used for
+fault tolerance and infrastructure isolation.
+
+It is defined in the agent configuration file using the
+[`datacenter`][config_datacenter] parameter and, unlike affinities and
+constraints, datacenters are opt-in at the job level, meaning that a job only
+places allocations in the datacenters it uses, and, more importantly, only jobs
+in a given datacenter are allowed to place allocations in those nodes.
+
+Given the strong connotation of a geographical location, use datacenters to
+represent where a node resides rather than its intended use. The
+[`spread`][job_spread] block can help achieve fault tolerance across
+datacenters.
+
+## Node Pool
+
+Node pools allow grouping nodes that can be targeted by jobs to achieve
+workload isolation.
+
+Similarly to datacenters, node pools are configured in an agent configuration
+file using the [`node_pool`][config_client_node_pool] attribute, and are opt-in
+on jobs, allowing restricted use of certain nodes by specific jobs without
+extra configuration.
+
+But unlike datacenters, node pools don't have a preconceived notion and can be
+used for several use cases, such as segmenting infrastructure per environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+Node pools are also a first-class concept and can hold additional [metadata and
+configuration][spec_node_pool].
+
+Use node pools when there is a need to restrict and reserve certain nodes for
+specific workloads, or when you need to adjust specific [scheduler
+configuration][spec_node_pool_sched_config] values.
+
+Nomad Enterprise also allows associating a node pool to a namespace to
+facilitate managing the relationships between jobs, namespaces, and node pools.
+
+Refer to the [Node Pools][concept_np] concept page for more information.
+
+## Understanding Evaluation Status
+
+When a job cannot be immediately placed, Nomad creates a chain of evaluations
+to manage placement. First, your initial evaluation may be marked complete even if 
+placement fails. Then Nomad creates a blocked evaluation to retry placement when
+resources become available. Your job remains pending until Nomad places all allocations.
+
+For example, if your job has specific constraints that are not available, you
+get an initial completed evaluation and a blocked evaluation. Nomad tracks
+ongoing placement attempts until a node that fits your constraints is available.
+
+To troubleshoot placement issues, use `nomad eval status <eval_id>`. Check the output 
+for placement failures and linked evaluations.
+
+[api_client_metadata]: /nomad/api-docs/client#update-node-metadata
+[cli_node_meta]: /nomad/docs/commands/node/meta
+[concept_np]: /nomad/docs/concepts/node-pools
+[config_client_meta]: /nomad/docs/configuration/client#meta
+[config_client_node_class]: /nomad/docs/configuration/client#node_class
+[config_client_node_pool]: /nomad/docs/configuration/client#node_pool
+[config_datacenter]: /nomad/docs/configuration#datacenter
+[job_affinity]: /nomad/docs/job-specification/affinity
+[job_constraint]: /nomad/docs/job-specification/constraint
+[job_spread]: /nomad/docs/job-specification/spread
+[node attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[spec_node_pool]: /nomad/docs/other-specifications/node-pool
+[spec_node_pool_sched_config]: /nomad/docs/other-specifications/node-pool#scheduler_config-parameters
diff --git a/content/nomad/v1.9.x/content/docs/concepts/scheduling/preemption.mdx b/content/nomad/v1.9.x/content/docs/concepts/scheduling/preemption.mdx
new file mode 100644
index 0000000000..95a85738ee
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/scheduling/preemption.mdx
@@ -0,0 +1,102 @@
+---
+layout: docs
+page_title: Allocation Preemption
+description: Nomad uses preemption to evict existing allocations in order to place allocations for a higher priority job. Learn how Nomad uses job priority to preempt running allocations and how you can determine whether Nomad preempted an allocation. Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+---
+
+# Allocation Preemption
+
+This page provides conceptual information about preemption, which is evicting
+existing allocations in order to place allocations for a higher priority job.
+Learn how Nomad uses job priorty to determine when to preempt running
+allocations and how you can determine whether Nomad has preempted an allocation.
+Use `nomad plan` to dry run the scheduler to find out if preemption is necessary.
+
+Preemption allows Nomad to kill existing allocations in order to place
+allocations for a higher priority job. The evicted allocation is temporarily
+displaced until the cluster has capacity to run it. This allows operators to run
+high priority jobs even under resource contention across the cluster.
+
+~> **Advanced Topic!** This page covers technical details of Nomad. You do not need to understand these details to effectively use Nomad. The details are documented here for those who wish to learn about them without having to go spelunking through the source code.
+
+## Preemption in Nomad
+
+Every job in Nomad has a priority associated with it. Priorities impact scheduling at the evaluation and planning
+stages by sorting the respective queues accordingly (higher priority jobs get moved ahead in the queues).
+
+Nomad has preemption capabilities for service, batch, and system jobs. The Nomad scheduler can be configured to evict lower priority running allocations
+to free up capacity for new allocations resulting from relatively higher priority jobs, sending evicted allocations back
+into the plan queue.
+
+## Details
+
+Preemption is enabled by default for system jobs. You can use the [scheduler
+config][sched-config-api] API endpoint or [`nomad operator scheduler
+set-config`][sched-config-cli] commands to disable preemption or enable it for
+other job types.
+
+Nomad uses the [job priority](/nomad/docs/job-specification/job#priority) field to determine what running allocations can be preempted.
+In order to prevent a cascade of preemptions due to jobs close in priority being preempted, only allocations from jobs with a priority
+delta of 10 or greater compared to the job needing placement are eligible for preemption.
+
+For example, consider a node with the following distribution of allocations:
+
+| Job             | Priority | Allocations | Total Used capacity                                                      |
+| --------------- | -------- | ----------- | ------------------------------------------------------------------------ |
+| cache           | 70       | a6          | 2 GB Memory, 0.5 GB Disk, 1 CPU                                          |
+| batch-analytics | 50       | a4, a5      | <1 GB Memory, 0.5 GB Disk, 0.5 CPU>, <1 GB Memory, 0.5 GB Disk, 0.5 CPU> |
+| email-marketing | 20       | a1, a2      | <0.5 GB Memory, 0.8 GB Disk>, <0.5 GB Memory, 0.2 GB Disk>               |
+
+If a job `webapp` with priority `75` needs placement on the above node, only allocations from `batch-analytics` and `email-marketing` are considered
+eligible to be preempted because they are of a lower priority. Allocations from the `cache` job will never be preempted because its priority value `70`
+is lesser than the required delta of `10`.
+
+Allocations are selected starting from the lowest priority, and scored according
+to how closely they fit the job's required capacity. For example, if the `75` priority job needs 1GB disk and 2GB memory, Nomad will preempt
+allocations `a1`, `a2` and `a4` to satisfy those requirements.
+
+## Preemption Visibility
+
+Operators can use the [allocation API](/nomad/api-docs/allocations#read-allocation) or the `alloc status` command to get visibility into
+whether an allocation has been preempted. Preempted allocations will have their DesiredStatus set to “evict”. The `Allocation` object
+in the API also has two additional fields related to preemption.
+
+- `PreemptedAllocs` - This field is set on an allocation that caused preemption. It contains the allocation ids of allocations
+  that were preempted to place this allocation. In the above example, allocations created for the job `webapp` will have the values
+  `a1`, `a2` and `a4` set.
+- `PreemptedByAllocID` - This field is set on allocations that were preempted by the scheduler. It contains the allocation ID of the allocation
+  that preempted it. In the above example, allocations `a1`, `a2` and `a4` will have this field set to the ID of the allocation from the job `webapp`.
+
+## Integration with Nomad plan
+
+`nomad plan` allows operators to dry run the scheduler. If the scheduler determines that
+preemption is necessary to place the job, it shows additional information in the CLI output for
+`nomad plan` as seen below.
+
+```shell-session
+$ nomad plan example.nomad.hcl
+
++ Job: "test"
++ Task Group: "test" (1 create)
+  + Task: "test" (forces create)
+
+Scheduler dry-run:
+- All tasks successfully allocated.
+
+Preemptions:
+
+Alloc ID                              Job ID    Task Group
+ddef9521                              my-batch   analytics
+ae59fe45                              my-batch   analytics
+```
+
+Note that, the allocations shown in the `nomad plan` output above
+are not guaranteed to be the same ones picked when running the job later.
+They provide the operator a sample of the type of allocations that could be preempted.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
+[sched-config-api]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[sched-config-cli]: /nomad/docs/commands/operator/scheduler/set-config
diff --git a/content/nomad/v1.9.x/content/docs/concepts/scheduling/scheduling.mdx b/content/nomad/v1.9.x/content/docs/concepts/scheduling/scheduling.mdx
new file mode 100644
index 0000000000..db1d24cf61
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/scheduling/scheduling.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Scheduling in Nomad
+description: Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+---
+
+# Scheduling in Nomad
+
+This page provides conceptual information on how Nomad implements job scheduling using jobs, nodes, allocations, and evaluations. Learn about job lifecycle and how the job scheduler generates the allocation plan that the server implements using a service, batch, system, sysbatch, or core scheduler.
+
+[![Nomad Data Model][img-data-model]][img-data-model]
+
+There are four primary components in Nomad: jobs, nodes, allocations, and
+evaluations. Jobs are submitted by users and represent a _desired state_. A job
+is a declarative description of tasks to run which are bounded by constraints
+and require resources. Tasks can be scheduled on nodes in the cluster running
+the Nomad client. The mapping of tasks in a job to clients is done using
+allocations. An allocation is used to declare that a set of tasks in a job
+should be run on a particular node. Scheduling is the process of determining
+the appropriate allocations and is done as part of an evaluation.
+
+An evaluation is created any time the external state, either desired or
+emergent, changes. The desired state is based on jobs, meaning the desired
+state changes if a new job is submitted, an existing job is updated, or a job
+is deregistered. The emergent state is based on the client nodes, and so we
+must handle the failure of any clients in the system. These events trigger the
+creation of a new evaluation, as Nomad must _evaluate_ the state of the world
+and reconcile it with the desired state.
+
+This diagram shows the flow of an evaluation through Nomad:
+
+[![Nomad Evaluation Flow][img-eval-flow]][img-eval-flow]
+
+The lifecycle of an evaluation begins with an event causing the evaluation to
+be created. Evaluations are created in the `pending` state and are enqueued
+into the evaluation broker. There is a single evaluation broker which runs on
+the leader server. The evaluation broker is used to manage the queue of pending
+evaluations, provide priority ordering, and ensure at least once delivery.
+
+Nomad servers run scheduling workers, defaulting to one per CPU core, which are
+used to process evaluations. The workers dequeue evaluations from the broker,
+and then invoke the appropriate scheduler as specified by the job. Nomad ships
+with a `service` scheduler that optimizes for long-lived services, a `batch`
+scheduler that is used for fast placement of batch jobs, `system` and
+`sysbatch` schedulers that are used to run jobs on every node, and a `core`
+scheduler which is used for internal maintenance.
+
+Schedulers are responsible for processing an evaluation and generating an
+allocation _plan_. The plan is the set of allocations to evict, update, or
+create. The specific logic used to generate a plan may vary by scheduler, but
+generally the scheduler needs to first reconcile the desired state with the
+real state to determine what must be done. New allocations need to be placed
+and existing allocations may need to be updated, migrated, or stopped.
+
+Placing allocations is split into two distinct phases, feasibility checking and
+ranking. In the first phase the scheduler finds nodes that are feasible by
+filtering nodes in datacenters and node pools not used by the job, unhealthy
+nodes, those missing necessary drivers, and those failing the specified
+constraints.
+
+The second phase is ranking, where the scheduler scores feasible nodes to find
+the best fit. Scoring is primarily based on bin packing, which is used to
+optimize the resource utilization and density of applications, but is also
+augmented by affinity and anti-affinity rules. Nomad automatically applies a job
+anti-affinity rule which discourages colocating multiple instances of a task
+group. The combination of this anti-affinity and bin packing optimizes for
+density while reducing the probability of correlated failures.
+
+Once the scheduler has ranked enough nodes, the highest ranking node is
+selected and added to the allocation plan.
+
+When planning is complete, the scheduler submits the plan to the leader which
+adds the plan to the plan queue. The plan queue manages pending plans, provides
+priority ordering, and allows Nomad to handle concurrency races. Multiple
+schedulers are running in parallel without locking or reservations, making
+Nomad optimistically concurrent. As a result, schedulers might overlap work on
+the same node and cause resource over-subscription. The plan queue allows the
+leader node to protect against this and do partial or complete rejections of a
+plan.
+
+As the leader processes plans, it creates allocations when there is no conflict
+and otherwise informs the scheduler of a failure in the plan result. The plan
+result provides feedback to the scheduler, allowing it to terminate or explore
+alternate plans if the previous plan was partially or completely rejected.
+
+Once the scheduler has finished processing an evaluation, it updates the status
+of the evaluation and acknowledges delivery with the evaluation broker. This
+completes the lifecycle of an evaluation. Allocations that were created,
+modified or deleted as a result will be picked up by client nodes and will
+begin execution.
+
+[omega]: https://research.google.com/pubs/pub41684.html
+[borg]: https://research.google.com/pubs/pub43438.html
+[img-data-model]: /img/nomad-data-model.png
+[img-eval-flow]: /img/nomad-evaluation-flow.png
diff --git a/content/nomad/v1.9.x/content/docs/concepts/security.mdx b/content/nomad/v1.9.x/content/docs/concepts/security.mdx
new file mode 100644
index 0000000000..ffdc7453e8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/security.mdx
@@ -0,0 +1,342 @@
+---
+layout: docs
+page_title: Security Model
+description: >-
+  Nomad's security model provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel policies (Enterprise), and resource quotas (Enterprise) to enable fine-grained access within and between clusters. Learn how to secure your Nomad clusters with threat models for internal threats and external threats. Review the network ports used by the security model.
+---
+
+## Overview
+
+This page provides conceptual information on Nomad's security model, which
+provides mechanisms such as mTLS, namespace, access control list (ACL), Sentinel
+policies, and resource quotas to enable fine-grained access within and between
+clusters. Learn how to secure your Nomad clusters, threat models, internal
+threats, and external threats. Review the network ports used by the security
+model.
+
+Nomad utilizes a lightweight gossip and RPC system, [similar to
+Consul](/consul/docs/security/security-models/core), which provides
+various essential features. Both of these systems provide security mechanisms
+which should be utilized to help provide [confidentiality, integrity and
+authentication](https://en.wikipedia.org/wiki/Information_security).
+
+Using defense in depth is crucial for cluster security, and deployment
+requirements may differ drastically depending on your use case. Further security
+features for multi-tenant deployments are offered exclusively in the enterprise
+version. This documentation may need to be adapted to your deployment situation,
+but the general mechanisms for a secure Nomad deployment revolve around:
+
+- **[mTLS](/nomad/tutorials/transport-security/security-enable-tls)** Mutual
+  authentication of both the TLS server and client x509 certificates prevents
+  internal abuse by preventing unauthenticated access to network components
+  within the cluster.
+
+- **[ACLs](/nomad/tutorials/access-control)** Enables authorization for
+  authenticated connections by granting capabilities to ACL tokens.
+
+- **[Namespaces](/nomad/tutorials/manage-clusters/namespaces)** Access to read
+  and write to a namespace can be controlled to allow for granular access to job
+  information managed within a multi-tenant cluster.
+
+- **[Sentinel Policies]**<EnterpriseAlert inline /> Sentinel
+  policies allow for granular control over components such as task drivers
+  within a cluster.
+
+## Personas
+
+When thinking about Nomad, it helps to consider the following types of base
+personas when managing the security requirements for the cluster deployment. The
+granularity may change depending on your team's use case where rigorous roles
+can be accurately defined and managed using the [Nomad backend secret engine for
+Vault](/vault/docs/secrets/nomad). This is
+described further with getting started steps using a development server
+[here](/nomad/tutorials/access-control).
+
+It's important to note that there's no traditional concept of a user
+within Nomad itself.
+
+- **System Administrator** - This is someone who has access to the underlying
+  infrastructure to a Nomad cluster. Often she has access to SSH or RDP
+  directly into a server within a cluster through a bastion host. Ultimately
+  they have read, write and execute permissions for the actual Nomad binary.
+  This binary is the same for server and client nodes using different
+  configuration files. These users potentially have something like sudo,
+  administrative, or some other super-user access to the underlying compute
+  resource. Users like these are essentially totally trusted by Nomad as they
+  have administrative rights to the system and can start or stop the agent.
+
+- **Nomad Administrator** - This is someone (probably the same **System
+  Administrator**) who has access to define the Nomad agent configurations
+  for servers and clients, and/or have a Nomad management ACL token. They also
+  have total rights to all of the parts in the Nomad system including the
+  ability to start and stop all jobs within a cluster.
+
+- **Nomad Operator** - This is someone who likely has selective access with
+  restricted capabilities to manage jobs applicable to their namespace within
+  a cluster.
+
+- **User** - This is someone who is a user of an application being run on the
+  system. In some cases applications may be public facing and exposed to the
+  internet such as a web server. This is someone who shouldn't have any
+  network access to the Nomad server API.
+
+## Secure Configuration
+
+Nomad's security model is applicable only if all parts of the system are running
+with a secure configuration; **Nomad is not secure-by-default.** Without the following
+mechanisms enabled in Nomad's configuration, it may be possible to abuse access
+to a cluster. Like all security considerations, one must appropriately determine
+what concerns they have for their environment and adapt to these security
+recommendations accordingly.
+
+### Requirements
+
+- [mTLS enabled](/nomad/tutorials/transport-security/security-enable-tls)
+  Mutual TLS (mTLS) enables [mutual
+  authentication](https://en.wikipedia.org/wiki/Mutual_authentication) with
+  security properties to prevent the following problems:
+
+  * Unauthorized access because both server and clients must provide valid TLS
+    [X.509](https://en.wikipedia.org/wiki/X.509) certificates signed by the same
+    valid [CA](https://en.wikipedia.org/wiki/Certificate_authority) in order to
+    communicate within the cluster.
+
+  * Observing or tampering communication between nodes is thwarted due to the
+    traffic being encrypted using the well known network security protocol
+    [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) version 1.2,
+    with a [configurable minimal
+    version](/nomad/docs/configuration/tls#tls_min_version).
+    Both server and client agents must be configured to validate each other's
+    certificates to ensure mTLS is actually enabled. This requires appropriate
+    certificates to be distributed to servers, clients, machines, or operators
+    for things like CLI usage. It is recommended to use
+    [Vault](/nomad/tutorials/integrate-vault/vault-pki-nomad)
+    to securely manage the certificate creation and rotation for nodes.
+
+  * Agent role misconfiguration is prevented using the X.509
+    [SAN](https://en.wikipedia.org/wiki/Subject_Alternative_Name) extension.
+    This is essentially a domain name that is used to identify and verify a
+    node's region and role name are configured as expected (e.g.
+    `client.us-east.nomad`).
+
+  * Using the previously mentioned role name prevents maliciously masquerading
+    as a server or client node, and allows other services to be signed easily by
+    the same CA. This also avoids any potential pitfalls with certificates using
+    the IP or Hostname of nodes within a cluster.
+
+  * Using [`tls.verify_https_client=false`][verify_https_client] downgrades the
+    Nomad agent HTTP server to use TLS instead of mTLS. This is safe if ACLs are
+    enabled and is recommended if you are using the Nomad web UI to avoid the
+    difficulty of distributing client certificates to browsers.
+
+    Some API endpoints, such as [`/v1/metrics`][api_metrics] and
+    [`/v1/status/peers`][api_status_peers], can be accessed without an ACL
+    token and may be exposed to anyone with access to the Nomad HTTP address
+    when using `tls.verify_https_client=false`. You can use a reverse proxy or
+    other external means to restrict access to them.
+
+- [ACLs enabled](/nomad/tutorials/access-control) The
+  access control list (ACL) system provides a capability-based control
+  mechanism for Nomad administrators allowing for custom roles (typically
+  within Vault) to be tied to an individual human or machine operator
+  identity. This allows for access to capabilities within the cluster to be
+  restricted to specific users.
+
+- [Namespaces](/nomad/tutorials/manage-clusters/namespaces) This feature
+    allows for a cluster to be shared by multiple teams within a company. Using
+    this logical separation is important for multi-tenant clusters to prevent
+    users without access to that namespace from conflicting with each other.
+    This requires ACLs to be enabled in order to be enforced.
+
+- [Sentinel Policies]<EnterpriseAlert inline />
+  [Sentinel](https://www.hashicorp.com/sentinel/) is a feature which enables
+  [policy-as-code](https://docs.hashicorp.com/sentinel/concepts/policy-as-code)
+  to enforce further restrictions on operators. This is used to augment the
+  built-in ACL system for fine-grained control over jobs.
+
+- [Resource Quotas]<EnterpriseAlert inline /> Can limit a
+  namespace's access to the underlying compute resources in the cluster by
+  setting upper-limits for operators. Access to these resource quotas can be
+  managed via ACLs to ensure read-only access for operators so they can't just
+  change their quotas.
+
+### Recommendations
+
+The following are security recommendations that can help significantly improve
+the security of your cluster depending on your use case. We recommend always
+practicing defense in depth when architecting the security mechanisms for your
+environment.
+
+- **Rotate credentials** - Using short-lived credentials or rotating them
+  frequently is highly recommended to reduce damage of accidentally leaked
+  credentials.
+
+  - Use [Vault](/nomad/docs/integrations/vault-integration) to create and manage
+    dynamic, rotated credentials prevent secrets from being easily exposed
+    within the [job specification](/nomad/docs/job-specification) itself
+    which may be leaked into version control or otherwise be accidentally stored
+    on disk on an operator's local machine.
+
+  - Rotate credentials used by the Nomad agent; e.g. [integrate with Vault's
+    PKI secret engine](/nomad/tutorials/integrate-vault/vault-pki-nomad) to
+    automatically generate and renew dynamic, unique X.509 certificates for each
+    Nomad node with a short [TTL](https://en.wikipedia.org/wiki/Time_to_live).
+
+- **[Running without Root](https://groups.google.com/forum/#!topic/nomad-tool/pSyMwC_FSFA)** -
+  Nomad servers can be run as unprivileged users that only require access to
+  the data directory.
+
+- **Containers with Sandbox Runtimes** - In some situations, such as running
+  untrusted code as a service, it may be worth considering using different
+  container runtimes such as [gVisor](https://gvisor.dev/) or [Kata
+  Containers](https://katacontainers.io/). These types of runtimes provide
+  sandboxing features which help prevent raw access to the underlying shared
+  kernel for other containers and the Nomad client agent itself. Docker driver
+  allows [customizing runtimes](/nomad/docs/drivers/docker#runtime).
+
+- **[Disable Unused Drivers](/nomad/docs/configuration/client#driver-denylist)** -
+  Each driver provides different degrees of isolation, and bugs may allow
+  unintended privilege escalation. If a task driver is not needed, you can
+  disable it to reduce risk.
+
+- **Linux Security Modules** - Use of security modules that can be directly
+  integrated into operating systems such as AppArmor, SElinux, and Seccomp on
+  both the Nomad hosts and applied to containers for an extra layer of
+  security. Seccomp profiles are able to be passed directly to containers
+  using the
+  **[`security_opt`](/nomad/docs/drivers/docker#security_opt)**
+  parameter available in the default [Docker
+  driver](/nomad/docs/drivers/docker).
+
+- **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
+  Integrating service mesh technologies such as
+  **[Consul](https://www.consul.io/)** can be extremely useful for limiting
+  and efficiently load balancing network connectivity within a cluster.
+
+- **[TLS Settings](/nomad/docs/configuration/tls)** -
+  TLS settings, such as the available [cipher suites](/nomad/docs/configuration/tls#tls_cipher_suites), should be tuned to fit the needs of your environment.
+
+- **[HTTP Headers](/nomad/docs/configuration#http_api_response_headers)** -
+  Additional security [headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers), such as [`X-XSS-Protection`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection), can be [configured](/nomad/docs/configuration#http_api_response_headers) for HTTP API responses.
+
+## Threat Model
+
+The following are parts of the Nomad threat model:
+
+- **Nomad agent-to-agent communication** - Transport encryption for
+  agent-to-agent communication is required to prevent eavesdropping. TCP and
+  UDP based protocols within Nomad provide different mechanisms for enabling
+  encryption including symmetric (shared gossip encryption keys) and
+  asymmetric keys (TLS).
+
+- **Tampering of data in transit** - Any tampering should be detectable via mTLS
+  and cause Nomad to avoid processing the request.
+
+- **Access to data without authentication or authorization** - Requests to the
+  server should be authenticated and authorized using mTLS and ACLs
+  respectively.
+
+- **State modification or corruption due to malicious messages** - Improperly
+  formatted messages are discarded while properly formatted messages require
+  authentication and authorization.
+
+- **Non-server members accessing raw data** - All servers that join the cluster
+  require proper authentication and authorization in order to begin
+  participating in Raft. All data in Raft should be encrypted with TLS.
+
+- **Denial of Service against a node** - DoS attacks against a single node
+  should not compromise the security posture of Nomad.
+
+The following are not part of the threat model for server agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  jobs managed by Nomad is persisted to a server's data directory.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to
+  Nomad's configuration file(s) directory can enable and disable features for
+  a cluster.
+
+- **Memory access to a running Nomad server agent** - Direct access to the
+  memory of the Nomad server agent process (usually requiring a shell on the
+  system through various means) results in almost all aspects of the agent
+  being compromised including access to certificates and other secrets.
+
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
+
+The following are not part of the threat model for client agents:
+
+- **Access (read or write) to the Nomad data directory** - Information about the
+  allocations scheduled to a Nomad client is persisted to its data directory.
+  This would include any secrets in any of the allocation's file systems.
+
+- **Access (read or write) to the Nomad configuration directory** - Access to a
+  client's configuration file can enable and disable features for a client
+  including insecure drivers such as
+  [`raw_exec`](/nomad/docs/drivers/raw_exec).
+
+- **Memory access to a running Nomad client agent** - Direct access to the
+  memory of the Nomad client agent process allows an attack to extract secrets
+  from clients such as Vault tokens.
+
+- **Lax Client Driver Sandbox** - Drivers may allow some privileged operations,
+  e.g. filesystem access to configuration directories, or raw accesses to host
+  devices. Such privileges can be used to facilitate compromise other workloads,
+  or cause denial-of-service attacks.
+
+### Internal Threats
+
+- **Job Operator** - Someone with a valid mTLS certificate and ACL token may still be a
+  threat to your cluster in certain situations, especially in multi-team
+  cluster deployments. They may accidentally or intentionally use a malicious
+  job to harm a cluster which can help be protected against using
+  Quotas, Namespace, and Sentinel policies.
+
+- **Workload** - Workloads may have host network access within a cluster which
+  can lead to SSRF due to application security issues outside of the scope of
+  Nomad which may lead to internal access within the cluster. Using mTLS, ACLs
+  and Sentinel policies together can add layers of protection against
+  malicious workloads.
+
+- **RPC / API Access** - RPC and HTTP API endpoints without mTLS can expose
+  clusters to abuse within the cluster from malicious workloads.
+
+- **Client driver** - Drivers implement various workload types for a cluster,
+  and the backend configuration of these drivers should be considered to
+  implement defense in depth. For example, a custom Docker driver that limits
+  the ability to mount the host file system may be subverted by network access
+  to an exposed Docker daemon API through other means such as the [`raw_exec`](/nomad/docs/drivers/raw_exec)
+  driver.
+
+### External Threats
+
+There are two main components to consider to for external threats in a Nomad cluster:
+
+- **Server agent** - Internal cluster leader elections and replication is
+  managed via Raft between server agents encrypted in transit. However,
+  information about the server is stored unencrypted at rest in the agent's
+  data directory. This may contain sensitive information such as ACL tokens
+  and TLS certificates.
+
+- **Client agent** - Client-to-server communication within a cluster is
+  encrypted and authenticated using mTLS. Information about the allocations on
+  a client node is unencrypted in the agent's data and configuration
+  directory.
+
+## Network Ports
+
+| **Port / Protocol**  | Agents  | Description                                                                                                                                                           |
+|----------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **4646** / TCP       | All     | [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) to provide [UI](/nomad/tutorials/web-ui/web-ui-access) and [API](/nomad/api-docs) access to agents. |
+| **4647** / TCP       | All     | [RPC](https://en.wikipedia.org/wiki/Remote_procedure_call) protocol used by agents.                                                                                   |
+| **4648** / TCP + UDP | Servers | [gossip](/nomad/docs/concepts/gossip) protocol to manage server membership using [Serf][serf].                                                                        |
+
+
+[api_metrics]: /nomad/api-docs/metrics
+[api_status_peers]: /nomad/api-docs/status#list-peers
+[Variables]: /nomad/docs/concepts/variables
+[verify_https_client]: /nomad/docs/configuration/tls#verify_https_client
+[serf]: https://github.com/hashicorp/serf
+[Sentinel Policies]: /nomad/tutorials/governance-and-policy/sentinel
+[Resource Quotas]: /nomad/tutorials/governance-and-policy/quotas
diff --git a/content/nomad/v1.9.x/content/docs/concepts/variables.mdx b/content/nomad/v1.9.x/content/docs/concepts/variables.mdx
new file mode 100644
index 0000000000..8c2842f753
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/variables.mdx
@@ -0,0 +1,255 @@
+---
+layout: docs
+page_title: Nomad Variables
+description: Nomad's variables feature lets you store and use encrypted configuration data in your job specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+---
+
+# Nomad Variables
+
+This page contains conceptual information about the Nomad variables feature,
+which lets you store and use encrypted configuration data in your job
+specifications. Learn how Access Control List (ACL) policies restrict access to variables within a namespace, how a job task's workload identity grants access to variables, and how locking a variable blocks access to that variable.
+
+Most Nomad workloads need access to config values or secrets. Nomad has a
+`template` block to [provide such configuration to tasks](/nomad/docs/job-specification/template#nomad-variables),
+but prior to Nomad 1.4 has left the role of storing that configuration to
+external services such as [HashiCorp Consul] and [HashiCorp Vault].
+
+Nomad variables provide the option to store configuration at file-like paths
+directly in Nomad's state store. [Access these variables](/nomad/docs/job-specification/template#nomad-variables) directly from
+your task templates. The contents of these variables are encrypted
+and replicated between servers via raft. Access to variables is controlled by
+ACL policies, and tasks have implicit ACL policies that allow them to access
+their own variables. You can create, read, update, or delete variables via the
+command line, the Nomad API, or in the Nomad web UI.
+
+Note that the variables feature is intended for small pieces of configuration
+data needed by workloads. Because writing to the Nomad state store uses
+resources needed by Nomad, it is not well-suited for large or fast-changing
+data. For example, do not store batch job results as variables - these should be
+stored in an external database. Variables are also not intended to be a full
+replacement for HashiCorp Vault. Unlike Vault, Nomad stores the root encryption
+key on the servers. See [Key Management][] for details.
+
+## ACL for Variables
+
+Every variable belongs to a specific Nomad namespace. ACL policies can restrict
+access to variables within a namespace on a per-path basis, using a list of
+`path` blocks, located under `namespace.variables`. See the [ACL policy
+specification] docs for details about the syntax and structure of an ACL policy.
+
+Path definitions may also include wildcard symbols, also called globs, allowing
+a single path policy definition to apply to a set of paths within that
+namespace. For example, the policy below allows full access to variables at all
+paths in the "dev" namespace that are prefixed with "project/" (including child
+paths) but only read access to paths prefixed with "system/". Note that the glob
+can match an empty string and all other characters. This policy grants read
+access to paths prefixed with "system/" but not a path named "system" (without a
+trailing slash).
+
+```hcl
+namespace "dev" {
+  policy       = "write"
+  capabilities = ["alloc-node-exec"]
+
+  variables {
+
+    # full access to variables in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+The available capabilities for variables are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of variables at this path.                                                         |
+| destroy    | Delete variables at this path.                                                                                        |
+
+## Task Access to Variables
+
+Tasks can access variables with the [`template`] block or using the [Task API].
+The [workload identity] for each task grants it automatic read and list access to
+variables found at Nomad-owned paths with the prefix `nomad/jobs/`, followed by
+the job ID, task group name, and task name. This is equivalent to the following
+policy:
+
+```hcl
+namespace "$namespace" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/$job_id/$task_group/$task_name" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+For example, a task named "redis", in a group named "cache", in a job named
+"example", will automatically have access to variables as if it had the
+following policy:
+
+```hcl
+namespace "default" {
+  variables {
+
+    path "nomad/jobs" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache" {
+      capabilities = ["read", "list"]
+    }
+
+    path "nomad/jobs/example/cache/redis" {
+      capabilities = ["read", "list"]
+    }
+  }
+}
+```
+
+You can provide access to additional variables by creating policies associated
+with the task's [workload identity][]. For example, to give the task above access
+to all variables in the "shared" namespace, you can create the following policy
+file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+Then create the policy and associate it with the specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+Priority of policies and automatic task access to variables is similar to the
+[ACL policy namespace rules][]. The most specific rule for a path applies, so a
+rule for an exact path in a workload-attached policy overrides the automatic
+task access to variables, but a wildcard rule does not.
+
+As an example, consider the job `example` in the namespace `prod`, with a group
+`web` and a task named `httpd` with the following policy applied:
+
+```hcl
+namespace "*" {
+  variables {
+    path "nomad/jobs" {
+      capabilities = ["list"]
+    }
+
+    path "nomad/jobs/*" {
+      capabilities = ["deny"]
+    }
+  }
+}
+```
+
+The task will have read/list access to its own variables `nomad/jobs/example`,
+`nomad/jobs/example/web`, and `nomad/jobs/example/web/httpd` in the namespace
+`prod`, because those are more specific than the wildcard rule that denies
+access. The task will have list access to `nomad/jobs` in any namespace, because
+that path is more specific than the automatic task access to the `nomad/jobs`
+variable. And the task will not have access to `nomad/jobs/example` (or below)
+in namespaces other than `prod`, because the automatic access rule does not
+apply.
+
+See [Workload Associated ACL Policies] for more details.
+
+## Locks
+
+Nomad provides the ability to block a variable from being updated for a period
+of time by setting a lock on it. Once a variable is locked, it can be read by
+everyone, but it can only be updated by the lock holder.
+
+The locks are designed to provide granular locking and are heavily inspired by
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems][].
+
+A lock is composed of an ID, a TTL, and a lock delay. The ID is generated by
+the Nomad Server and must be provided on every request to modify the variable's
+items or the lock itself. The TTL defines the time the lock will be held; if the
+lock needs to be in place for longer, it can be renewed for as many new periods
+as wanted.
+
+Once it is no longer needed, it must be released. If by the time the TTL expires,
+and no renew or release calls were made, the variable will remain locked for at
+least the lock delay duration, to avoid a possible split-brain situation, where
+there are two holders at the same time.
+
+### Leader election backed by Nomad Variable Locks
+
+For some applications, like HDFS or the Nomad Autoscaler, it is necessary to
+have multiple instances running to ensure redundancy in case of a failure, but
+only one of them may be active at a time as a leader.
+
+As part of the [Go Package][], Nomad offers a helper that takes one variable and
+uses a lock over it as a sync mechanism to run multiple instances but always
+keeping just one running at any given time, using the following algorithm:
+
+[![Leader Election Helper](/img/nomad-vars-leader-election-sdk.png)](/img/nomad-vars-leader-election-sdk.png)
+
+As soon as any instance starts, it tries to lock the sync variable. If it succeeds,
+it continues to execute while a secondary thread is in charge of keeping track of
+the lock and renewing it when necessary. If by any chance the renewal fails,
+the main process is forced to return, and the instance goes into standby until it
+attempts to acquire the lock over the sync variable.
+
+Only threads 1 and 3 or thread 2 are running at any given time, because every
+instance is either executing as normal while renewing the lock or waiting for a
+chance to acquire it and run.
+
+When the main process, or protected function, returns, the helper releases the
+lock, allowing a second instance to start running.
+
+To see it implemented live, look for the [`nomad var lock`][] command
+implementation or the [Nomad Autoscaler][] High Availability implementation.
+
+
+[HashiCorp Consul]: https://www.consul.io/
+[HashiCorp Vault]: https://www.vaultproject.io/
+[Key Management]: /nomad/docs/operations/key-management
+[ACL policy specification]: /nomad/docs/other-specifications/acl-policy
+[`template`]: /nomad/docs/job-specification/template#nomad-variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[Workload Associated ACL Policies]: /nomad/docs/concepts/workload-identity#workload-associated-acl-policies
+[ACL policy namespace rules]: /nomad/docs/other-specifications/acl-policy#namespace-rules
+[The Chubby Lock Service for Loosely-Coupled Distributed Systems]: https://research.google/pubs/pub27897/
+[`nomad var lock`]: /nomad/docs/commands/var
+[Go Package]: https://pkg.go.dev/github.com/hashicorp/nomad/api
+[implementation]: https://github.com/hashicorp/nomad/blob/release/1.7.0/command/var_lock.go#L240
+[Nomad Autoscaler]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.4.0/command/agent.go#L392
+[Task API]: /nomad/api-docs/task-api
diff --git a/content/nomad/v1.9.x/content/docs/concepts/workload-identity.mdx b/content/nomad/v1.9.x/content/docs/concepts/workload-identity.mdx
new file mode 100644
index 0000000000..3caf74cf2d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/concepts/workload-identity.mdx
@@ -0,0 +1,193 @@
+---
+layout: docs
+page_title: Workload Identity
+description: Nomad's workload identity feature isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+---
+
+# Workload Identity
+
+This page provides conceptual information about Nomad's workload identity
+feature, which isolates and uniquely identities each workload so you can associate Access Control List (ACL) policies to jobs. Learn about workload identity claims, claims attributes specific to Nomad Enterprise, default workload ACL policy, and workload identity for Consul and Vault.
+
+Every workload running in Nomad is given a default identity. When an
+[allocation][] is accepted by the [plan applier][], the leader generates a
+Workload Identity for each task in the allocation. This workload identity is a
+[JSON Web Token (JWT)][] that has been signed by the leader's keyring.
+Additional workload identities may be defined in tasks and services using the
+[`identity`][identity-block] block.
+
+## Workload Identity Claims
+
+Nomad workload identity for tasks include the following identity claims.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "5c6328f7-48c5-4d03-bada-91ef2e904d0d",
+  "nomad_task": "web"
+}
+```
+
+Workload identities for Consul services have a claim with the service name
+instead of the task name.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Workload identities for tasks that use Vault have an additional claim for
+[`vault.role`][jobspec_vault_role] if a role is specified in the job.
+
+-> **Note:** This claim will *not* be added if the role is inherited from
+the [agent configuration][vault_role_agent_config] and is not present
+in the Nomad job specification.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_role": "nomad-jwt-login"
+}
+```
+
+### Nomad Enterprise <EnterpriseAlert inline />
+
+In Nomad Enterprise, tasks and services with a [`consul`][jobspec_consul] block
+that defines a [`namespace`][jobspec_consul_ns] value, or inside a `group`
+block that does it, have an additional claim called `consul_namespace`.
+
+```json
+{
+  "consul_namespace": "prod",
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis"
+}
+```
+
+Similarly, tasks with a [`vault.namespace`][jobspec_vault_ns] value have the additional claim
+`vault_namespace`.
+
+```json
+{
+  "nomad_namespace": "default",
+  "nomad_job_id": "example",
+  "nomad_allocation_id": "8623ac7a-28ba-20c3-24a6-e615a39bbbf3",
+  "nomad_service": "example-cache-redis",
+  "vault_namespace": "prod"
+}
+```
+
+## Workload Identity for Nomad
+
+While Nomad always creates and uses workload identities internally, the JWT is
+not exposed to tasks by default.
+
+To expose Workload Identity to tasks, add an [`identity`][identity-block] block
+to your jobspec:
+
+```hcl
+task "example" {
+
+  identity {
+    # Expose Workload Identity in NOMAD_TOKEN env var
+    env = true
+
+    # Expose Workload Identity in ${NOMAD_SECRETS_DIR}/nomad_token file
+    file = true
+  }
+
+}
+```
+
+### Default Workload ACL Policy
+
+By default, a Workload Identity has access to a implicit ACL policy. This policy
+grants access to Nomad Variables associated with the job, group, and task, as
+described in [Task Access to Variables][]. The implicit policy also allows
+access to list or read any Nomad service registration as with the [List Services
+API][] or [Read Service API][].
+
+### Workload Associated ACL Policies
+
+You can associate additional ACL policies with workload identities by passing
+the `-job`, `-group`, and `-task` flags to `nomad acl policy apply`. When Nomad
+resolves a workload identity claim, it will automatically include policies that
+match. If no matching policies exist, the workload identity does not have any
+additional capabilities.
+
+For example, to allow a workload access to secrets from the namespace "shared",
+you can create the following policy file:
+
+```hcl
+namespace "shared" {
+  variables {
+    path "*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+You can then apply this policy to a specific task:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache -task redis \
+   redis-policy ./policy.hcl
+```
+
+You can also apply this policy to all tasks in the group by omitting the `-task`
+flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example -group cache \
+   redis-policy ./policy.hcl
+```
+
+And you can apply this policy to all groups in the job by omitting both the
+`-group` and `-task` flag:
+
+```shell-session
+nomad acl policy apply \
+   -namespace default -job example \
+   redis-policy ./policy.hcl
+```
+
+### Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identity for Consul and Vault
+
+Consul and Vault can be configured to accept workload identities from Nomad for
+authentication. Refer to the [Consul][consul_int] and [Vault][vault_int]
+integration pages for more information.
+
+[allocation]: /nomad/docs/glossary#allocation
+[identity-block]: /nomad/docs/job-specification/identity
+[jobspec_consul]: /nomad/docs/job-specification/consul
+[jobspec_consul_ns]: /nomad/docs/job-specification/consul#namespace
+[jobspec_vault_ns]: /nomad/docs/job-specification/vault#namespace
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[vault_role_agent_config]: /nomad/docs/configuration/vault#create_from_role
+[plan applier]: /nomad/docs/concepts/scheduling/scheduling
+[JSON Web Token (JWT)]: https://datatracker.ietf.org/doc/html/rfc7519
+[Task Access to Variables]: /nomad/docs/concepts/variables#task-access-to-variables
+[List Services API]: /nomad/api-docs/services#list-services
+[Read Service API]: /nomad/api-docs/services#read-service
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[taskapi]: /nomad/api-docs/task-api
+[consul_int]: /nomad/docs/integrations/consul-integration
+[vault_int]: /nomad/docs/integrations/vault-integration
diff --git a/content/nomad/v1.9.x/content/docs/configuration/acl.mdx b/content/nomad/v1.9.x/content/docs/configuration/acl.mdx
new file mode 100644
index 0000000000..8dcce0d4d9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/acl.mdx
@@ -0,0 +1,71 @@
+---
+layout: docs
+page_title: acl Block in Agent Configuration
+description: >-
+   Configure Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration. Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+---
+
+# acl Block in Agent Configuration
+
+<Placement groups={['acl']} />
+
+This page provides reference information for configuring Nomad's Access Control List (ACL) system behavior in the `acl` block of a Nomad agent configuration.  Enable ACL enforcement, change token replication and expiration values, and tune the cache for token, role, and policy TTLs.
+
+Learn more about configuring Nomad's ACL system in the [Secure
+Nomad with Access Control guide][secure-guide].
+
+```hcl
+acl {
+  enabled    = true
+  token_ttl  = "30s"
+  policy_ttl = "60s"
+  role_ttl   = "60s"
+}
+```
+
+## `acl` Parameters
+
+- `enabled` `(bool: false)` - Specifies if ACL enforcement is enabled. All other
+  ACL configuration options depend on this value. All agents should have the
+  same value for this parameter. For example the Nomad command line will
+  send requests for client endpoints such as `alloc exec` directly to Nomad
+  clients whenever they are accessible. In this scenario, the client will
+  enforce ACLs, so both servers and clients should have ACLs enabled.
+
+- `token_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL tokens. This does not affect servers, since they do not cache tokens.
+  Setting this value lower reduces how stale a token can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `policy_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL policies. This does not affect servers, since they do not cache policies.
+  Setting this value lower reduces how stale a policy can be, but increases
+  the request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `role_ttl` `(string: "30s")` - Specifies the maximum time-to-live (TTL) for
+  cached ACL roles. This does not affect servers, since they do not cache roles.
+  Setting this value lower reduces how stale a role can be, but increases the
+  request load against servers. If a client cannot reach a server, for example
+  because of an outage, the TTL will be ignored and the cached value used.
+
+- `replication_token` `(string: "")` - Specifies the Secret ID of the ACL token
+  to use for replicating policies and tokens. This is used by servers in
+  non-authoritative region to mirror the policies and tokens into the local
+  region from the [`authoritative_region`][authoritative-region]. Setting
+  `replication_token` requires that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `token_min_expiration_ttl` `(string: "1m")` - Specifies the lowest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+- `token_max_expiration_ttl` `(string: "24h")` - Specifies the highest acceptable
+  TTL value for an ACL token when setting expiration. This is used by the Nomad
+  servers to validate ACL tokens and ACL authentication methods.
+
+[secure-guide]: /nomad/tutorials/access-control
+[authoritative-region]: /nomad/docs/configuration/server#authoritative_region
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
diff --git a/content/nomad/v1.9.x/content/docs/configuration/audit.mdx b/content/nomad/v1.9.x/content/docs/configuration/audit.mdx
new file mode 100644
index 0000000000..4ed021b968
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/audit.mdx
@@ -0,0 +1,301 @@
+---
+layout: docs
+page_title: audit Block in Agent Configuration
+description: >-
+  Configure audit logging behavior in the `audit` block of a Nomad agent configuration. Enable audit logs, define a sink to stream audit logs to, and change filter rules to exclude events from the audit log. Review example audit logs.
+---
+
+# `audit` Block in Agent Configuration
+
+<Placement groups={['audit']} />
+<EnterpriseAlert product="nomad"/>
+
+This page provides reference information for configuring audit logging behavior
+in the `audit` block of a Nomad agent configuration. Enable audit logs, define a
+sink to stream audit logs to, and change filter rules to exclude events from the
+audit log.
+
+```hcl
+audit {
+  enabled = true
+}
+```
+
+When enabled, each HTTP request made to a nomad agent (client or server) will
+generate two audit log entries. These two entries correspond to a stage,
+`OperationReceived` and `OperationComplete`. Audit logging will generate a
+`OperationReceived` event before the request is processed. An `OperationComplete`
+event will be sent after the request has been processed, but before the response
+body is returned to the end user.
+
+By default, with a minimally configured audit block (`audit { enabled = true }`)
+The following default sink will be added with no filters.
+
+```hcl
+audit {
+  enabled = true
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/[data_dir]/audit/audit.log"
+  }
+}
+```
+
+The sink will create an `audit.log` file located within the defined `data_dir`
+directory inside an `audit` directory. `delivery_guarantee` will be set to
+`"enforced"` meaning that all requests must successfully be written to the sink
+in order for HTTP requests to successfully complete.
+
+## `audit` Parameters
+
+- `enabled` `(bool: false)` - Specifies if audit logging should be enabled.
+  When enabled, audit logging will occur for every request, unless it is
+  filtered by a `filter`.
+
+- `sink` <code>([sink](#sink-block): default)</code> - Configures a sink
+  for audit logs to be sent to.
+
+- `filter` <code>(array<[filter](#filter-block)>: [])</code> - Configures a filter
+  to exclude matching events from being sent to audit logging sinks.
+
+### `sink` Block
+
+The `sink` block is used to make audit logging sinks for events to be
+sent to. Currently only a single sink is supported.
+
+The key of the block corresponds to the name of the sink which is used
+for logging purposes
+
+```hcl
+audit {
+  enabled = true
+
+  sink "audit" {
+    type               = "file"
+    delivery_guarantee = "enforced"
+    format             = "json"
+    path               = "/var/lib/nomad/audit/audit.log"
+    rotate_bytes       = 100
+    rotate_duration    = "24h"
+    rotate_max_files   = 10
+    mode               = "0600"
+  }
+}
+```
+
+#### `sink` Parameters
+
+- `type` `(string: "file", required)` - Specifies the type of sink to create.
+  Currently only `"file"` type is supported.
+
+- `delivery_guarantee` `(string: "enforced", required)` - Specifies the
+  delivery guarantee that will be made for each audit log entry. Available
+  options are `"enforced"` and `"best-effort"`. `"enforced"` will
+  halt request execution if the audit log event fails to be written to its sink.
+  `"best-effort"` will not halt request execution, meaning a request could
+  potentially be un-audited.
+
+- `format` `(string: "json", required)` - Specifies the output format to be
+  sent to a sink. Currently only `"json"` format is supported.
+
+- `mode` `(string: "0600")` - Specifies the permissions mode for the audit log
+   files using octal notation.
+
+- `path` `(string: "[data_dir]/audit/audit.log")` - Specifies the path and file
+  name to use for the audit log. By default Nomad will use its configured
+  [`data_dir`](/nomad/docs/configuration#data_dir) for a combined path of
+  `/data_dir/audit/audit.log`. If `rotate_bytes` or `rotate_duration` are set
+  file rotation will occur. In this case the filename will be post-fixed with
+  a timestamp `"filename-{timestamp}.log"`
+
+- `rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to an audit log before it needs to be rotated. Unless specified,
+  there is no limit to the number of bytes that can be written to a log file.
+
+- `rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  audit log should be written to before it needs to be rotated. Must be a
+  duration value such as 30s.
+
+- `rotate_max_files` `(int: 0)` - Specifies the maximum number of older audit
+  log file archives to keep. If 0, no files are ever deleted.
+
+### `filter` Block
+
+The `filter` block is used to create filters to filter **out** matching events
+from being written to the audit log. By default, all events will be sent to an
+audit log for all stages (OperationReceived and OperationComplete). Filters
+are useful for operators who want to limit the performance impact of audit
+logging as well as reducing the amount of events generated.
+
+`endpoints`, `stages`, and `operations` support [globbed pattern][glob] matching.
+
+Query parameters are ignored when evaluating filters.
+
+```hcl
+audit {
+  enabled = true
+
+  # Filter out all requests and all stages for /v1/metrics
+  filter "default" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/metrics"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out requests where endpoint matches globbed pattern
+  filter "globbed example" {
+    type       = "HTTPEvent"
+    endpoints  = ["/v1/evaluation/*/allocations"]
+    stages     = ["*"]
+    operations = ["*"]
+  }
+
+  # Filter out OperationReceived GET requests for all endpoints
+  filter "OperationReceived GETs" {
+    type       = "HTTPEvent"
+    endpoints  = ["*"]
+    stages     = ["OperationReceived"]
+    operations = ["GET"]
+  }
+}
+```
+
+#### `filter` Parameters
+
+- `type` `(string: "HTTPEvent", required)` - Specifies the type of filter to
+  create. Currently only HTTPEvent is supported.
+
+- `endpoints` `(array<string>: [])` - Specifies the list of endpoints to apply
+  the filter to.
+
+- `stages` `(array<string>: [])` - Specifies the list of stages
+  (`"OperationReceived"`, `"OperationComplete"`, `"*"`) to apply the filter to
+  for a matching endpoint.
+
+- `operations` `(array<string>: [])` - Specifies the list of operations to
+  apply the filter to for a matching endpoint. For HTTPEvent types this
+  corresponds to an HTTP verb (GET, PUT, POST, DELETE...).
+
+## Example audit logs
+
+The following audit log entries are for a request made to `/v1/job/web/summary`.
+The first entry is for the `OperationReceived` stage. The second entry is for
+the `OperationComplete` stage and includes the contents of the
+`OperationReceived` stage plus a `response` key.
+
+```json
+{
+  "created_at": "2020-03-24T13:09:35.703869927-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationReceived",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    }
+  }
+}
+{
+  "created_at": "2020-03-24T13:09:35.704224536-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "8b826146-b264-af15-6526-29cb905145aa",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:09:35.703865005-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "a162f017-bcf7-900c-e22a-a2a8cbbcef53",
+      "name": "Bootstrap Token",
+      "global": true,
+      "create_time": "2020-03-24T17:08:35.086591881Z"
+    },
+    "request": {
+      "id": "02f0ac35-c7e8-0871-5a58-ee9dbc0a70ea",
+      "operation": "GET",
+      "endpoint": "/v1/job/web/summary",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33648",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 200
+    }
+  }
+}
+
+```
+
+If the request returns an error the audit log will reflect the error message.
+
+```json
+{
+  "created_at": "2020-03-24T13:18:36.121978648-04:00",
+  "event_type": "audit",
+  "payload": {
+    "id": "21c6f97a-fbfb-1090-1e34-34d1ece57cc2",
+    "stage": "OperationComplete",
+    "type": "audit",
+    "timestamp": "2020-03-24T13:18:36.121428628-04:00",
+    "version": 1,
+    "auth": {
+      "accessor_id": "anonymous",
+      "name": "Anonymous Token",
+      "policies": ["anonymous"],
+      "create_time": "0001-01-01T00:00:00Z"
+    },
+    "request": {
+      "id": "c696cc9e-962e-18b3-4097-e0a09070f89e",
+      "operation": "GET",
+      "endpoint": "/v1/jobs?prefix=web",
+      "namespace": {
+        "id": "default"
+      },
+      "request_meta": {
+        "remote_address": "127.0.0.1:33874",
+        "user_agent": "Go-http-client/1.1"
+      },
+      "node_meta": {
+        "ip": "127.0.0.1:4646"
+      }
+    },
+    "response": {
+      "status_code": 403,
+      "error": "Permission denied"
+    }
+  }
+}
+```
+
+[glob]: https://github.com/ryanuber/go-glob/blob/master/README.md#example
diff --git a/content/nomad/v1.9.x/content/docs/configuration/autopilot.mdx b/content/nomad/v1.9.x/content/docs/configuration/autopilot.mdx
new file mode 100644
index 0000000000..350d75ef06
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/autopilot.mdx
@@ -0,0 +1,62 @@
+---
+layout: docs
+page_title: autopilot Block in Agent Configuration
+description: >-
+  Configure settings for Nomad Autopilot features in the `autopilot` block of a Nomad agent configuration. Enable dead server cleanup, redundancy zones, and custom upgrades. Disable upgrade migration. Tune Raft settings for stable server introduction.
+---
+
+# `autopilot` Block in Agent Configuration
+
+<Placement groups={['autopilot']} />
+
+This page provides reference information for configuring settings for Nomad
+Autopilot features in the `autopilot` block of a Nomad agent configuration.
+Enable dead server cleanup, redundancy zones, and custom upgrades. Disable
+upgrade migration. Tune Raft settings for stable server introduction.
+
+Refer to the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot) for
+how to configure and use Autopilot.
+
+```hcl
+autopilot {
+    cleanup_dead_servers      = true
+    last_contact_threshold    = "200ms"
+    max_trailing_logs         = 250
+    server_stabilization_time = "10s"
+    enable_redundancy_zones   = false
+    disable_upgrade_migration = false
+    enable_custom_upgrades    = false
+}
+```
+
+## `autopilot` Parameters
+
+- `cleanup_dead_servers` `(bool: true)` - Specifies automatic removal of dead
+  server nodes periodically and whenever a new server is added to the cluster.
+
+- `last_contact_threshold` `(string: "200ms")` - Specifies the maximum amount of
+  time a server can go without contact from the leader before being considered
+  unhealthy. Must be a duration value such as `10s`.
+
+- `max_trailing_logs` `(int: 250)` specifies the maximum number of log entries
+  that a server can trail the leader by before being considered unhealthy.
+
+- `server_stabilization_time` `(string: "10s")` - Specifies the minimum amount of
+  time a server must be stable in the 'healthy' state before being added to the
+  cluster. Only takes effect if all servers are running Raft protocol version 3
+  or higher. Must be a duration value such as `30s`.
+
+- `enable_redundancy_zones` `(bool: false)` - <EnterpriseAlert product="nomad" inline/> Controls whether
+  Autopilot separates servers into zones for redundancy, in conjunction with the
+  [redundancy_zone](/nomad/docs/configuration/server#redundancy_zone) parameter.
+  Only one server in each zone can be a voting member at one time.
+
+- `disable_upgrade_migration` `(bool: false)` - <EnterpriseAlert product="nomad" inline/> Disables Autopilot's
+  upgrade migration strategy in Nomad Enterprise of waiting until enough
+  newer-versioned servers have been added to the cluster before promoting any of
+  them to voters.
+
+- `enable_custom_upgrades` `(bool: false)` - <EnterpriseAlert product="nomad" inline/> Specifies whether to
+  enable using custom upgrade versions when performing migrations, in conjunction with
+  the [upgrade_version](/nomad/docs/configuration/server#upgrade_version)
+  parameter.
diff --git a/content/nomad/v1.9.x/content/docs/configuration/client.mdx b/content/nomad/v1.9.x/content/docs/configuration/client.mdx
new file mode 100644
index 0000000000..0e7c0f0f7a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/client.mdx
@@ -0,0 +1,818 @@
+---
+layout: docs
+page_title: client Block in Agent Configuration
+description: |-
+  Configure a Nomad client in the `client` block of a Nomad agent configuration. Enable a client, configure allocation directories, artifact and template behavior, networking, node pools, servers to join, garbage collection, workload behavior, client resources, chroot, host volumes, host network, and driver-specific behavior.
+---
+
+# `client` Block in Agent Configuration
+
+<Placement groups={['client']} />
+
+This page provides reference information for configuring a Nomad client in the
+`client` block of a Nomad agent configuration. Enable a client, configure
+allocation directories, artifact and template behavior, networking, node pools,
+servers to join, garbage collection, workload behavior, client resources,
+chroot, host volumes, host network, and driver-specific behavior.
+
+Refer to the [Set Server and Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent](/nomad/docs/commands/agent) pages to learn about the Nomad
+agent process and how to configure the server and client nodes in your cluster.
+
+```hcl
+client {
+  enabled = true
+  servers = ["1.2.3.4:4647", "5.6.7.8:4647"]
+}
+```
+
+## `client` Parameters
+
+- `alloc_dir` `(string: "")` - Specifies the directory to use for allocation
+  data. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `alloc`, like
+  `"/opt/nomad/alloc"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `alloc_mounts_dir` `(string: "")` - Specifies the directory to use for binding
+  mounts for the [unveil file isolation mode][unveil]. When this parameter is
+  empty, Nomad generates the path as a sibling of the [top-level
+  `data_dir`][top_level_data_dir], with the name `alloc_mounts`. For example, if
+  the `data_dir` is `/opt/nomad/data`, then the alloc mounts directory is
+  `/opt/nomad/alloc_mounts`. This must be an absolute path and should not be
+  inside the Nomad data directory. Nomad creates the directory on the host,
+  if it does not exist when the agent process starts.
+
+- `chroot_env` <code>([ChrootEnv](#chroot_env-parameters): nil)</code> -
+  Specifies a key-value mapping that defines the chroot environment for jobs
+  using the Exec and Java drivers.
+
+- `enabled` `(bool: false)` - Specifies if client mode is enabled. All other
+  client configuration options depend on this value.
+
+- `max_kill_timeout` `(string: "30s")` - Specifies the maximum amount of time a
+  job is allowed to wait to exit. Individual jobs may customize their own kill
+  timeout, but it may not exceed this value.
+
+- `disable_remote_exec` `(bool: false)` - Specifies if the client should disable
+  remote task execution to tasks running on this client.
+
+- `meta` `(map[string]string: nil)` - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `network_interface` `(string: varied)` - Specifies the name of the interface
+  to force network fingerprinting on. When run in dev mode, this defaults to the
+  loopback interface. When not in dev mode, the interface attached to the
+  default route is used. The scheduler chooses from these fingerprinted IP
+  addresses when allocating ports for tasks. This value support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  If no non-local IP addresses are found, Nomad could fingerprint link-local IPv6
+  addresses depending on the client's
+  [`"fingerprint.network.disallow_link_local"`](#fingerprint-network-disallow_link_local)
+  configuration value.
+
+- `preferred_address_family` `(string: "")` - Specifies the preferred address family
+  for the network interface. The value can be `ipv4` or `ipv6`. If the selected network
+  interface has both IPv4 and IPv6 addresses, this option will select an IP address of
+  the preferred family. When the option is not specified, the current behavior is conserved:
+  the first IP address is selected no matter the family.
+
+- `cpu_disable_dmidecode` `(bool: false)` - Specifies the client should not use dmidecode
+  as a method of cpu detection. Nomad ignores this field on all platforms except Linux.
+
+- `cpu_total_compute` `(int: 0)` - Specifies an override for the total CPU
+  compute. This value should be set to `# Cores * Core MHz`. For example, a
+  quad-core running at 2 GHz would have a total compute of 8000 (4 \* 2000). Most
+  clients can determine their total CPU compute automatically, and thus in most
+  cases this should be left unset.
+
+- `memory_total_mb` `(int:0)` - Specifies an override for the total memory. If set,
+  this value overrides any detected memory.
+
+- `disk_total_mb` `(int:0)` - Specifies an override for the total disk space
+  fingerprint attribute. This value is not used by the scheduler unless you have
+  constraints set on the attribute `unique.storage.bytestotal`. The actual total
+  disk space can be determined via the [Read Stats API](/nomad/api-docs/client#read-stats)
+
+- `disk_free_mb` `(int:0)` - Specifies the disk space free for scheduling
+  allocations. If set, this value overrides any detected free disk space. This
+  value can be seen in `nomad node status` under Allocated Resources.
+
+- `min_dynamic_port` `(int:20000)` - Specifies the minimum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `max_dynamic_port` `(int:32000)` - Specifies the maximum dynamic port to be
+  assigned. Individual ports and ranges of ports may be excluded from dynamic
+  port assignment via [`reserved`](#reserved-parameters) parameters.
+
+- `node_class` `(string: "")` - Specifies an arbitrary string used to logically
+  group client nodes by user-defined class. This value can be used during job
+  placement as an [`affinity`][] or [`constraint`][] attribute and other places
+  where [variable interpolation][runtime_var_interpolation] is supported.
+
+- `node_pool` `(string: "default")` - Specifies the node pool in which the
+  client is registered. If the node pool does not exist yet, it will be created
+  automatically if the node registers in the authoritative region. In
+  non-authoritative regions, the node is kept in the `initializing` status
+  until the node pool is created and replicated.
+
+- `options` <code>([Options](#options-parameters): nil)</code> - Specifies a
+  key-value mapping of internal configuration for clients, such as for driver
+  configuration.
+
+- `reserved` <code>([Reserved](#reserved-parameters): nil)</code> - Specifies
+  that Nomad should reserve a portion of the node's resources from receiving
+  tasks. This can be used to target a certain capacity usage for the node. For
+  example, a value equal to 20% of the node's CPU could be reserved to target
+  a CPU utilization of 80%.
+
+- `servers` `(array<string>: [])` - Specifies an array of addresses to the Nomad
+  servers this client should join. This list is used to register the client with
+  the server nodes and advertise the available resources so that the agent can
+  receive work. This may be specified as an IP address or DNS, with or without
+  the port. If the port is omitted, the default port of `4647` is used. If you
+  are specifying IPv6 addresses, they must be in URL format with brackets
+  (ex. `"[2001:db8::1]"`).
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad client will connect to Nomad servers. The `start_join` field
+  is not supported on the client. The retry_join fields may directly specify
+  the server address or use go-discover syntax for auto-discovery.
+
+- `state_dir` `(string: "")` - Specifies the directory to use to store client
+  state. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`][top_level_data_dir] suffixed with `client`, like
+  `"/opt/nomad/client"`. This must be an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `gc_interval` `(string: "1m")` - Specifies the interval at which Nomad
+  attempts to garbage collect terminal allocation directories.
+
+- `gc_disk_usage_threshold` `(float: 80)` - Specifies the disk usage percent which
+  Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_inode_usage_threshold` `(float: 70)` - Specifies the inode usage percent
+  which Nomad tries to maintain by garbage collecting terminal allocations.
+
+- `gc_max_allocs` `(int: 50)` - Specifies the maximum number of allocations
+  which a client will track before triggering a garbage collection of terminal
+  allocations. This will _not_ limit the number of allocations a node can run at
+  a time, however after `gc_max_allocs` every new allocation will cause terminal
+  allocations to be GC'd.
+
+- `gc_parallel_destroys` `(int: 2)` - Specifies the maximum number of
+  parallel destroys allowed by the garbage collector. This value should be
+  relatively low to avoid high resource usage during garbage collections.
+
+- `no_host_uuid` `(bool: true)` - By default a random node UUID will be
+  generated, but setting this to `false` will use the system's UUID.
+
+- `cni_path` `(string: "/opt/cni/bin")` - Sets the search path that is used for
+  CNI plugin discovery. Multiple paths can be searched using colon delimited
+  paths
+
+- `cni_config_dir` `(string: "/opt/cni/config")` - Sets the directory where CNI
+  network configuration is located. The client will use this path when fingerprinting
+  CNI networks. Filenames should use the `.conflist` extension. Filenames with
+  the `.conf` or `.json` extensions are loaded as individual plugin
+  configuration.
+
+- `bridge_network_name` `(string: "nomad")` - Sets the name of the bridge to be
+  created by Nomad for allocations running with bridge networking mode on the
+  client.
+
+- `bridge_network_subnet` `(string: "172.26.64.0/20")` - Specifies the subnet
+  which the client will use to allocate IP addresses from.
+
+- `bridge_network_subnet_ipv6` `(string: "")` - Enables IPv6 on Nomad's bridge
+  network by specifying the subnet which the client will use to allocate IPv6
+  addresses.
+
+- `bridge_network_hairpin_mode` `(bool: false)` - Specifies if hairpin mode
+  is enabled on the network bridge created by Nomad for allocations running
+  with bridge networking mode on this client. You may use the corresponding
+  node attribute `nomad.bridge.hairpin_mode` in constraints. When hairpin mode
+  is enabled, allocations are able to reach their own IP and **all ports** bound
+  to it. Changing this value requires a reboot of the client host to take
+  effect.
+
+- `artifact` <code>([Artifact](#artifact-parameters): varied)</code> -
+  Specifies controls on the behavior of task
+  [`artifact`](/nomad/docs/job-specification/artifact) blocks.
+
+- `template` <code>([Template](#template-parameters): nil)</code> - Specifies
+  controls on the behavior of task
+  [`template`](/nomad/docs/job-specification/template) blocks.
+
+- `host_volume` <code>([host_volume](#host_volume-block): nil)</code> - Exposes
+  paths from the host as volumes that can be mounted into jobs.
+
+- `host_network` <code>([host_network](#host_network-block): nil)</code> - Registers
+  additional host networks with the node that can be selected when port mapping.
+
+- `drain_on_shutdown` <code>([drain_on_shutdown](#drain_on_shutdown-block):
+  nil)</code> - Controls the behavior of the client when
+  [`leave_on_interrupt`][] or [`leave_on_terminate`][] are set and the client
+  receives the appropriate signal.
+
+- `cgroup_parent` `(string: "/nomad")` - Specifies the cgroup parent for which cgroup
+  subsystems managed by Nomad will be mounted under. Currently this only applies to the
+  `cpuset` subsystems. This field is ignored on non Linux platforms.
+
+- `users` <code>([Users](#users-block): nil)</code> - Specifies options
+  concerning Nomad client's use of operating system users.
+
+### `chroot_env` Parameters
+
+On Linux, drivers based on [isolated fork/exec](/nomad/docs/drivers/exec) implement file system isolation using chroot. The `chroot_env` map lets you configure the chroot environment using source paths on the host operating system.
+
+The mapping format is:
+
+```text
+source_path -> dest_path
+```
+
+The following example specifies a chroot which contains just enough to run the
+`ls` utility:
+
+```hcl
+client {
+  chroot_env {
+    "/bin/ls"           = "/bin/ls"
+    "/etc/ld.so.cache"  = "/etc/ld.so.cache"
+    "/etc/ld.so.conf"   = "/etc/ld.so.conf"
+    "/etc/ld.so.conf.d" = "/etc/ld.so.conf.d"
+    "/etc/passwd"       = "/etc/passwd"
+    "/lib"              = "/lib"
+    "/lib64"            = "/lib64"
+  }
+}
+```
+
+@include 'chroot-limitations.mdx'
+
+When `chroot_env` is unspecified, the `exec` driver uses a default chroot
+environment with the most commonly used parts of the operating system. Refer to the [Nomad `exec` driver documentation](/nomad/docs/drivers/exec#chroot) for
+the full list.
+
+Nomad never attempts to embed the `alloc_dir` in the chroot as doing so would cause infinite recursion.
+
+### `options` Parameters
+
+~> Note: In Nomad 0.9 client configuration options for drivers were deprecated.
+Refer to the [plugin block][plugin-block] documentation for more information.
+
+The following is not an exhaustive list of options for only the Nomad
+client. To find the options supported by each individual Nomad driver,
+refer to the [drivers documentation](/nomad/docs/drivers).
+
+- `"driver.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted drivers. If specified, drivers not in the allowlist will be
+  disabled. If the allowlist is empty, all drivers are fingerprinted and enabled
+  where applicable.
+
+  ```hcl
+  client {
+    options = {
+      "driver.allowlist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"driver.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted drivers. If specified, drivers in the denylist will be
+  disabled.
+
+  ```hcl
+  client {
+    options = {
+      "driver.denylist" = "docker,qemu"
+    }
+  }
+  ```
+
+- `"env.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of environment variable keys not to pass to these tasks.
+  Nomad passes the host environment variables to `exec`, `raw_exec` and `java`
+  tasks. If specified, the defaults are overridden. If a value is provided,
+  **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "env.denylist" = "MY_CUSTOM_ENVVAR"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  CONSUL_TOKEN
+  CONSUL_HTTP_TOKEN
+  CONSUL_HTTP_TOKEN_FILE
+  NOMAD_TOKEN
+  VAULT_TOKEN
+  CONSUL_LICENSE
+  NOMAD_LICENSE
+  VAULT_LICENSE
+  CONSUL_LICENSE_PATH
+  NOMAD_LICENSE_PATH
+  VAULT_LICENSE_PATH
+  AWS_ACCESS_KEY_ID
+  AWS_SECRET_ACCESS_KEY
+  AWS_SESSION_TOKEN
+  AWS_METADATA_URL
+  GOOGLE_APPLICATION_CREDENTIALS
+  GOOGLE_OAUTH_ACCESS_TOKEN
+  ```
+
+- `"user.denylist"` `(string: refer to explanation)` - Specifies a
+  comma-separated denylist of usernames for which a task is not allowed to run.
+  This only applies if the driver is included in `"user.checked_drivers"`. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.denylist" = "root,ubuntu"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  root
+  Administrator
+  ```
+
+- `"user.checked_drivers"` `(string: refer to explanation)` - Specifies a
+  comma-separated list of drivers for which to enforce the `"user.denylist"`.
+  For drivers using containers, this enforcement is usually unnecessary. If a
+  value is provided, **all** defaults are overridden (they are not merged).
+
+  ```hcl
+  client {
+    options = {
+      "user.checked_drivers" = "exec,raw_exec"
+    }
+  }
+  ```
+
+  The default list is:
+
+  ```text
+  exec
+  qemu
+  java
+  ```
+
+- `"fingerprint.allowlist"` `(string: "")` - Specifies a comma-separated list of
+  allowlisted fingerprinters. If specified, any fingerprinters not in the
+  allowlist will be disabled. If the allowlist is empty, all fingerprinters are
+  used.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.allowlist" = "network"
+    }
+  }
+  ```
+
+- `"fingerprint.denylist"` `(string: "")` - Specifies a comma-separated list of
+  denylisted fingerprinters. If specified, any fingerprinters in the denylist
+  will be disabled. A common use-case for the fingerprint denylist is to disable
+  fingerprinters of irrelevant cloud environments, which can slow down client
+  agent startup time.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.denylist" = "env_aws,env_gce,env_azure,env_digitalocean"
+    }
+  }
+  ```
+
+- `"fingerprint.network.disallow_link_local"` `(string: "false")` - Specifies
+  whether the network fingerprinter should ignore link-local addresses in the
+  case that no globally routable address is found. The fingerprinter will always
+  prefer globally routable addresses.
+
+  ```hcl
+  client {
+    options = {
+      "fingerprint.network.disallow_link_local" = "true"
+    }
+  }
+  ```
+
+### `reserved` Parameters
+
+- `cpu` `(int: 0)` - Specifies the amount of CPU to reserve, in MHz.
+
+- `cores` `(string: "")` - Specifies the cpuset of CPU cores to reserve. Only
+  supported on Linux.
+
+  ```hcl
+    client {
+      reserved {
+        cores = "0-4"
+      }
+    }
+  ```
+
+- `memory` `(int: 0)` - Specifies the amount of memory to reserve, in MB.
+
+- `disk` `(int: 0)` - Specifies the amount of disk to reserve, in MB.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all fingerprinted network devices. Ranges can be specified by using
+  a hyphen separating the two inclusive ends. Refer to
+  [`host_network`](#host_network-block) for reserving ports on specific host
+  networks.
+
+
+### `artifact` Parameters
+
+- `http_read_timeout` `(string: "30m")` - Specifies the maximum duration in
+  which an HTTP download request must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `http_max_size` `(string: "100GB")` - Specifies the maximum size allowed for
+  artifacts downloaded via HTTP. Set to `0` to not enforce a limit.
+
+- `gcs_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Google Cloud Storate operation must complete before it is canceled. Set to
+  `0` to not enforce a limit.
+
+- `git_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Git operation must complete before it is canceled. Set to `0` to not enforce
+  a limit.
+
+- `hg_timeout` `(string: "30m")` - Specifies the maximum duration in which a
+  Mercurial operation must complete before it is canceled. Set to `0` to not
+  enforce a limit.
+
+- `s3_timeout` `(string: "30m")` - Specifies the maximum duration in which an
+  S3 operation must complete before it is canceled. Set to `0` to not enforce a
+  limit.
+
+- `decompression_size_limit` `(string: "100GB")` - Specifies the maximum amount
+  of data that will be decompressed before triggering an error and cancelling the
+  operation. Set to `"0"` to not enforce a limit.
+
+- `decompression_file_count_limit` `(int: 4096)` - Specifies the maximum number
+  of files that will be decompressed before triggering an error and cancelling the
+  operation. Set to `0` to not enforce a limit.
+
+- `disable_filesystem_isolation` `(bool: false)` - Specifies whether filesystem
+  isolation should be disabled for artifact downloads. Applies only to systems
+  where filesystem isolation via [landlock] is possible (Linux kernel 5.13+).
+
+- `filesystem_isolation_extra_paths` `([]string: nil)` - Allow extra paths
+  in the filesystem isolation. Paths are specified in the form `[kind]:[mode]:[path]`
+  where `kind` must be either `f` or `d` (file or directory) and
+  `mode` must be zero or more of `r`, `w`, `c`, `x` (read, write, create, execute) e.g.
+  `f:r:/dev/urandom` would enable reading the /dev/urandom file,
+  `d:rx:/opt/bin` would enable reading and executing from the /opt/bin directory
+
+- `set_environment_variables` `(string:"")` - Specifies a comma separated list
+  of environment variables that should be inherited by the artifact sandbox from
+  the Nomad client's environment. By default a minimal environment is set including
+  a `PATH` appropriate for the operating system.
+
+### `template` Parameters
+
+- `function_denylist` `([]string: ["plugin", "writeToFile"])` - Specifies a
+  list of template rendering functions that should be disallowed in job specs.
+  By default the `plugin` and `writeToFile` functions are disallowed as they
+  allow unrestricted root access to the host.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+- `max_stale` `(string: "87600h")` - This is the maximum interval to allow "stale"
+  data. If `max_stale` is set to `0`, only the Consul leader will respond to queries, and
+  requests that reach a follower will forward to the leader. In large clusters with
+  many requests, this is not as scalable. This option allows any follower to respond
+  to a query, so long as the last-replicated data is within this bound. Higher values
+  result in less cluster load, but are more likely to have outdated data. This default
+  of 10 years (`87600h`) matches the default Consul configuration.
+
+- `wait` `(map: { min = "5s" max = "4m" })` - Defines the minimum and maximum amount
+  of time to wait before attempting to re-render a template. Consul Template re-renders
+  templates whenever rendered variables from Consul, Nomad, or Vault change. However in
+  order to minimize how often tasks are restarted or reloaded, Nomad will configure Consul
+  Template with a backoff timer that will tick on an interval equal to the specified `min`
+  value. Consul Template will always wait at least the as long as the `min` value specified.
+  If the underlying data has not changed between two tick intervals, Consul Template will
+  re-render. If the underlying data has changed, Consul Template will delay re-rendering
+  until the underlying data stabilizes for at least one tick interval, or the configured
+  `max` duration has elapsed. Once the `max` duration has elapsed, Consul Template will
+  re-render the template with the data available at the time. This is useful to enable in
+  systems where Consul is in a degraded state, or the referenced data values are changing
+  rapidly, because it will reduce the number of times a template is rendered. Setting
+  both `min` and `max` to `0` disables the feature. This configuration is also exposed
+  in the _task template block_ to allow overrides per task.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "4m"
+  }
+  ```
+
+- `wait_bounds` `(map: nil)` - Defines client level lower and upper bounds for
+  per-template `wait` configuration. If the individual template configuration has
+  a `min` lower than `wait_bounds.min` or a `max` greater than the `wait_bounds.max`,
+  the bounds will be enforced, and the template `wait` will be adjusted before being
+  sent to `consul-template`.
+
+  ```hcl
+  wait_bounds {
+    min     = "5s"
+    max     = "10s"
+  }
+    ```
+
+- `block_query_wait` `(string: "5m")` - This is amount of time in seconds to wait
+  for the results of a blocking query. Many endpoints in Consul support a feature known as
+  "blocking queries". A blocking query is used to wait for a potential change
+  using long polling.
+
+- `consul_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })`-
+  This controls the retry behavior when an error is returned from Consul. The template
+  runner will not exit in the face of failure. Instead, it uses exponential back-off
+  and retry functions to wait for the Consul cluster to become available, as is
+  customary in distributed systems.
+
+  ```hcl
+  consul_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `vault_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Vault. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  vault_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+- `nomad_retry` `(map: { attempts = 12 backoff = "250ms" max_backoff = "1m" })` -
+  This controls the retry behavior when an error is returned from Nomad. Consul
+  Template is highly fault tolerant, meaning it does not exit in the face of failure.
+  Instead, it uses exponential back-off and retry functions to wait for the cluster
+  to become available, as is customary in distributed systems.
+
+  ```hcl
+  nomad_retry {
+    # This specifies the number of attempts to make before giving up. Each
+    # attempt adds the exponential backoff sleep time. Setting this to
+    # zero will implement an unlimited number of retries.
+    attempts = 12
+    # This is the base amount of time to sleep between retry attempts. Each
+    # retry sleeps for an exponent of 2 longer than this base. For 5 retries,
+    # the sleep times would be: 250ms, 500ms, 1s, 2s, then 4s.
+    backoff = "250ms"
+    # This is the maximum amount of time to sleep between retry attempts.
+    # When max_backoff is set to zero, there is no upper limit to the
+    # exponential sleep between retry attempts.
+    # If max_backoff is set to 10s and backoff is set to 1s, sleep times
+    # would be: 1s, 2s, 4s, 8s, 10s, 10s, ...
+    max_backoff = "1m"
+  }
+  ```
+
+### `host_volume` Block
+
+The `host_volume` block is used to make volumes available to jobs.
+
+The key of the block corresponds to the name of the volume for use in the
+`source` parameter of a `"host"` type [`volume`](/nomad/docs/job-specification/volume)
+and ACLs.
+
+```hcl
+client {
+  host_volume "ca-certificates" {
+    path      = "/etc/ssl/certs"
+    read_only = true
+  }
+}
+```
+
+#### `host_volume` Parameters
+
+- `path` `(string: "", required)` - Specifies the path on the host that should
+  be used as the source when this volume is mounted into a task. The path must
+  exist on client startup.
+
+- `read_only` `(bool: false)` - Specifies whether the volume should only ever be
+  allowed to be mounted `read_only`, or if it should be writeable.
+
+### `host_network` Block
+
+The `host_network` block is used to register additional host networks with
+the node that can be used when port mapping.
+
+The key of the block corresponds to the name of the network used in the
+[`host_network`](/nomad/docs/job-specification/network#host-networks).
+
+```hcl
+client {
+  host_network "public" {
+    cidr           = "203.0.113.0/24"
+    reserved_ports = "22,80"
+  }
+}
+```
+
+#### `host_network` Parameters
+
+- `cidr` `(string: "")` - Specifies a cidr block of addresses to match against.
+  If an address is found on the node that is contained by this cidr block, the
+  host network will be registered with it.
+
+- `interface` `(string: "")` - Filters searching of addresses to a specific interface.
+
+- `reserved_ports` `(string: "")` - Specifies a comma-separated list of ports to
+  reserve on all addresses associated with this network. Ranges can be specified by using
+  a hyphen separating the two inclusive ends.
+  [`reserved.reserved_ports`](#reserved_ports) are also reserved on each host
+  network.
+
+### `drain_on_shutdown` Block
+
+The `drain_on_shutdown` block controls the behavior of the client when
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] are set. By default
+`drain_on_shutdown` is not configured and clients will not drain on any
+signal.
+
+If `drain_on_shutdown` is configured, the node will drain itself when receiving
+the appropriate signal (`SIGINT` for `leave_on_interrupt` or `SIGTERM` on
+`leave_on_terminate`). By default this acts similarly to running [`nomad node
+drain -self -no-deadline`][]
+
+Note that even if no deadline is set, your init system may send `SIGKILL` to
+Nomad if the drain takes longer than allowed by the service shutdown. For
+example, when running under Linux with `systemd`, you should adjust the
+[`TimeoutStopSec`][] value in the `nomad.service` unit file to account for
+enough time for the client to drain.
+
+```hcl
+client {
+  # Either leave_on_interrupt or leave_on_terminate must be set
+  # for this to take effect.
+  drain_on_shutdown {
+    deadline           = "1h"
+    force              = false
+    ignore_system_jobs = false
+  }
+}
+```
+
+- `deadline` `(string: "1h")` - Set the deadline by which all allocations must
+  be moved off the client. Remaining allocations after the deadline are removed
+  from the client, regardless of their [`migrate`][] block. Defaults to 1 hour.
+
+- `force` `(bool: false)` - Setting to `true` drains all the allocations on the
+  client immediately, ignoring the [`migrate`][] block. Note if you have
+  multiple allocations for the same job on the draining client without
+  additional allocations on other clients, this will result in an outage for
+  that job until the drain is complete.
+
+- `ignore_system_jobs` `(bool: false)` - Setting to `true` allows the drain to
+  complete without stopping system job allocations. By default system jobs (and
+  CSI plugins) are stopped last.
+
+### `users` Block
+
+The `users` block controls aspects of Nomad client's use of operating system
+users.
+
+```hcl
+client {
+  users {
+    dynamic_user_min = 80000
+    dynamic_user_max = 89999
+  }
+}
+```
+
+- `dynamic_user_min` `(int: 80000)` - The lowest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+- `dynamic_user_max` `(int: 89999)` - The highest UID/GID to allocate for task
+  drivers capable of making use of dynamic workload users.
+
+
+## `client` Examples
+
+### Common Setup
+
+This example shows the most basic configuration for a Nomad client joined to a
+cluster.
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Reserved Resources
+
+This example shows a sample configuration for reserving resources to the client.
+This is useful if you want to allocate only a portion of the client's resources
+to jobs.
+
+```hcl
+client {
+  enabled = true
+
+  reserved {
+    cpu            = 500
+    memory         = 512
+    disk           = 1024
+    reserved_ports = "22,80,8500-8600"
+  }
+}
+```
+
+### Custom Metadata and Node Class
+
+This example shows a client configuration which customizes the metadata
+and node class. The scheduler can use this information while processing
+[constraints][metadata_constraint]. The metadata is completely user configurable;
+the values in the example are for illustrative purposes only.
+
+```hcl
+client {
+  enabled       = true
+  node_class    = "prod"
+
+  meta {
+    owner           = "ops"
+    cached_binaries = "redis,apache,nginx,jq,cypress,nodejs"
+    rack            = "rack-12-1"
+  }
+}
+```
+
+[`affinity`]: /nomad/docs/job-specification/affinity
+[`constraint`]: /nomad/docs/job-specification/constraint
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[metadata_constraint]: /nomad/docs/job-specification/constraint#user-specified-metadata 'Nomad User-Specified Metadata Constraint Example'
+[runtime_var_interpolation]: /nomad/docs/runtime/interpolation
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task directories'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[migrate]: /nomad/docs/job-specification/migrate
+[`nomad node drain -self -no-deadline`]: /nomad/docs/commands/node/drain
+[`TimeoutStopSec`]: https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec=
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[unveil]: /nomad/docs/concepts/plugins/task-drivers#fsisolation-unveil
diff --git a/content/nomad/v1.9.x/content/docs/configuration/consul.mdx b/content/nomad/v1.9.x/content/docs/configuration/consul.mdx
new file mode 100644
index 0000000000..94a0313402
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/consul.mdx
@@ -0,0 +1,458 @@
+---
+layout: docs
+page_title: consul Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with Consul in the `consul` block of a Nomad agent configuration for service discovery and key-value integration. Configure cluster name, the Consul namespace, whether Nomad should advertize its services, certificates, tokens, security, health checks, auto join, and workload service and task identity.
+---
+
+# `consul` Block in Agent Configuration
+
+<Placement groups={['consul']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [Consul][consul] in the `consul` block of a Nomad agent
+configuration for service discovery and key-value integration. Configure cluster
+name, the Consul namespace, whether Nomad should advertize its services,
+certificates, tokens, security, health checks, auto join, and workload service
+and task identity.
+
+When configured, tasks can register themselves with Consul, and the Nomad
+cluster can [automatically bootstrap][bootstrap] itself.
+
+Refer to the [Service Discovery on Nomad
+tutorial](/nomad/tutorials/service-discovery) for how to use Consul's service
+discovery.
+
+```hcl
+consul {
+  address = "127.0.0.1:8500"
+  auth    = "admin:password"
+  token   = "abcd1234"
+}
+```
+
+A default `consul` block is automatically merged with all Nomad agent
+configurations. These sensible defaults automatically enable Consul integration
+if Consul is detected on the system. This allows for seamless bootstrapping of
+the cluster with zero configuration. To put it another way: if you have a Consul
+agent running on the same host as the Nomad agent with the default
+configuration, Nomad will be able to automatically connect to the rest of the
+Nomad cluster.
+
+If the local Consul agent is configured and accessible by the Nomad agents, the
+Nomad cluster will [automatically bootstrap][bootstrap] provided
+`server_auto_join`, `client_auto_join`, and `auto_advertise` are all enabled
+(which is the default).
+
+~> An important requirement is that each Nomad agent talks to a unique Consul
+agent. Nomad agents should be configured to talk to Consul agents and not
+Consul servers. If you are observing flapping services, you may have
+multiple Nomad agents talking to the same Consul agent. As such avoid
+configuring Nomad to talk to Consul via DNS such as consul.service.consul
+
+In Nomad Enterprise, you may specify multiple `consul` blocks to configure
+access to multiple Consul clusters. Each Consul cluster must have a different
+value for the [`name`](#name) field.
+
+## `consul` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `address` `(string: "127.0.0.1:8500")` - Specifies the address to the local
+  Consul agent, given in the format `host:port`. Supports Unix sockets with the
+  format: `unix:///tmp/consul/consul.sock`. Will default to the
+  `CONSUL_HTTP_ADDR` environment variable if set.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `auth` `(string: "")` - Specifies the HTTP Basic Authentication information to
+  use for access to the Consul Agent, given in the format `username:password`.
+
+- `auto_advertise` `(bool: true)` - Specifies if Nomad should advertise its
+  services in Consul. The services are named according to `server_service_name`
+  and `client_service_name`. Nomad servers and clients advertise their
+  respective services, each tagged appropriately with either `http` or `rpc`
+  tag. Nomad servers also advertise a `serf` tagged service.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA certificate
+  used for Consul communication. This defaults to the system bundle if
+  unspecified. Will default to the `CONSUL_CACERT` environment variable if set.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Consul communication. If this is set then you need to also set `key_file`.
+
+- `checks_use_advertise` `(bool: false)` - Specifies if Consul health checks
+  should bind to the advertise address. By default, this is the first [HTTP
+  address](/nomad/docs/configuration#http). If no
+  [HTTP address](/nomad/docs/configuration#http) is
+  specified, it will fall back to the
+  [bind_addr](/nomad/docs/configuration#bind_addr).
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Consul communication. If this is set then you need to also set `cert_file`.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`consul.cluster`][] or [`service.cluster`][] fields. In Nomad
+  Community Edition, only the `"default"` cluster will be used, so this field
+  should be omitted.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the [Consul
+  namespace](/consul/docs/enterprise/namespaces) used by the Consul
+  integration. If non-empty, this namespace will be used on all Consul API calls
+  and for Consul Connect configurations, unless overridden by the job's
+  [`consul.namespace`][] field. In Nomad Community Edition, only the `"default"`
+  namespace is used, so you should omit this field.
+
+- `ssl` `(bool: false)` - Specifies if the transport scheme should use HTTPS to
+  communicate with the Consul agent. Will default to the `CONSUL_HTTP_SSL`
+  environment variable if set.
+
+- `tags` `(array<string>: [])` - Specifies optional Consul tags to be
+  registered with the Nomad server and client services.
+
+- `timeout` `(string: "5s")` - Specifies a time limit for requests made against
+  Consul. This is specified using a label suffix like "10s".
+
+- `token` `(string: "")` - Specifies the token used to provide a per-request ACL
+  token. This option overrides the Consul Agent's default token. If the token is
+  not set here or on the Consul agent, it defaults to Consul's anonymous policy,
+  which may or may not allow writes. Defaults to the `CONSUL_HTTP_TOKEN`
+  environment variable if set. Nomad cannot refresh this token; if the token is
+  deleted, Nomad is not able to communicate with Consul.
+
+  In Nomad Enterprise, if the Consul agent running alongside Nomad is in a
+  Consul Enterprise admin partition, you must create the Consul token provided
+  to the Nomad client in the same partition.
+
+- `verify_ssl` `(bool: true)`- Specifies if SSL peer verification should be used
+  when communicating to the Consul API client over HTTPS. Will default to the
+  `CONSUL_HTTP_SSL_VERIFY` environment variable if set.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`][] set to `true`.
+
+- `client_auto_join` `(bool: true)` - Specifies if the Nomad clients should
+  automatically discover servers in the same region by searching for the Consul
+  service name defined in the `server_service_name` option. The search occurs if
+  the client is not registered with any servers or it is unable to heartbeat to
+  the leader of the region, in which case it may be partitioned and searches for
+  other servers.
+
+- `client_service_name` `(string: "nomad-client")` - Specifies the name of the
+  service in Consul for the Nomad clients.
+
+- `client_http_check_name` `(string: "Nomad Client HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad clients.
+
+- `client_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check is critical.
+
+- `client_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad client Consul health check shows a warning.
+
+- `grpc_address` `(string: "127.0.0.1:8502")` - Specifies the address to the local
+  Consul agent for `gRPC` requests, given in the format `host:port`. Note that
+  Consul does not enable the [`grpc`][grpc_port] or [`grpc_tls`][grpctls_port]
+  listeners by default.
+
+- `grpc_ca_file` `(string: "")` - Specifies an optional path to the GRPC CA
+  certificate used for communication between Connect sidecar proxies and Consul
+  agents. Will default to the `CONSUL_GRPC_CACERT` environment variable if set.
+
+  <Warning>
+
+    Consul does not support incoming TLS verification of Envoy
+    sidecars. You should set `tls.grpc.verify_incoming = false` in your
+    Consul configuration when using Connect. Refer to
+    [Consul/#13088](https://github.com/hashicorp/consul/issues/13088) for
+    more details.
+
+  </Warning>
+
+- `share_ssl` `(bool: true)` - Specifies whether the Nomad client should share
+  its Consul SSL configuration with Connect Native applications. Includes values
+  of `ca_file`, `cert_file`, `key_file`, `ssl`, and `verify_ssl`. Does not
+  include the values for the ACL `token` or `auth`. This option should be
+  disabled in environments where Consul ACLs are not enabled.
+
+- `service_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for services.
+
+- `task_auth_method` `(string: "nomad-workloads")` - Specifies the name of the
+  Consul [authentication method][auth-method] that will be used to login with a
+  Nomad JWT for tasks.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `server_service_name` `(string: "nomad")` - Specifies the name of the service
+  in Consul for the Nomad servers.
+
+- `server_http_check_name` `(string: "Nomad Server HTTP Check")` - Specifies the
+  HTTP health check name in Consul for the Nomad servers.
+
+- `server_serf_check_name` `(string: "Nomad Server Serf Check")` - Specifies
+  the Serf health check name in Consul for the Nomad servers.
+
+- `server_rpc_check_name` `(string: "Nomad Server RPC Check")` - Specifies
+  the RPC health check name in Consul for the Nomad servers.
+
+- `server_auto_join` `(bool: true)` - Specifies if the Nomad servers should
+  automatically discover and join other Nomad servers by searching for the
+  Consul service name defined in the `server_service_name` option. This search
+  only happens if the server does not have a leader.
+
+- `server_failures_before_critical` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check is critical.
+
+- `server_failures_before_warning` `(int: 0)` - Specifies the number of
+  consecutive failures before the Nomad server Consul health check shows a warning.
+
+- `service_identity` <code>([Identity](#service_identity-parameters): nil)</code> - Specifies
+  a default Workload Identity to use when obtaining Service Identity tokens from
+  Consul to register services. Refer to [Workload Identity](#workload-identity)
+  for a recommended configuration.
+
+- `task_identity` <code>([Identity](#task_identity-parameters): nil)</code> - Specifies a
+  default Workload Identity to use when obtaining Consul tokens from Consul to
+  support [`template`][] blocks. Refer to [Workload
+  Identity](#workload-identity) for a recommended configuration.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Consul token, proving
+  they have access to the service identity policies required by the Consul
+  Connect enabled services listed in the job. This option should be disabled in
+  an untrusted environment.
+
+## Workload Identity
+
+The `service_identity` and `task_identity` blocks accept all the same values as
+the job specification's [`identity`][identity_block] (except that the
+`service_identity` ignores the `env` and `file` fields). By ensuring these
+blocks are set on the Nomad servers, you can automatically migrate your existing
+jobs to use Workload Identity without modifying the job specification and
+resubmitting them.
+
+The recommended configuration for `service_identity` and `task_identity` is as
+follows. Refer to [Migrating to Using Workload Identity with Consul][] for
+details on how to configure Consul to accept these identities. Note that the
+`ttl` field here refers to the TTL of the Nomad identity and not the Consul
+token.
+
+```hcl
+consul {
+  service_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+
+  task_identity {
+    aud = ["consul.io"]
+    ttl = "1h"
+  }
+}
+```
+
+### `service_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+### `task_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`BoundAudiences`][consul_bound_aud]
+  configuration in the Consul JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN_consul_default` (or `NOMAD_TOKEN_consul_<name>` depending
+  on the [`name`](#name) field) environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_consul_default.jwt` (or
+  `secrets/nomad_consul_<name>.jwt` depending on the [`name`](#name) field). If
+  the [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+## `consul` Examples
+
+### Default
+
+This example shows the default Consul integration:
+
+```hcl
+consul {
+  address             = "127.0.0.1:8500"
+  server_service_name = "nomad"
+  client_service_name = "nomad-client"
+  auto_advertise      = true
+  server_auto_join    = true
+  client_auto_join    = true
+}
+```
+
+### Custom Address and Port
+
+This example shows pointing the Nomad agent at a different Consul address. Note
+that you should **never** point directly at a Consul server; always point to a
+local client. In this example, the Consul server is bound and listening on the
+node's private IP address instead of localhost, so we use that:
+
+```hcl
+consul {
+  address = "10.0.2.4:8500"
+}
+```
+
+### Custom SSL
+
+This example shows configuring custom SSL certificates to communicate with
+the Consul agent. The Consul agent should be configured to accept certificates
+similarly, but that is not discussed here:
+
+```hcl
+consul {
+  ssl       = true
+  ca_file   = "/var/ssl/bundle/ca.bundle"
+  cert_file = "/etc/ssl/consul.crt"
+  key_file  = "/etc/ssl/consul.key"
+}
+```
+
+### Consul ACL policy for Nomad
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+### Consul Namespace <EnterpriseAlert inline/>
+
+Consul does not allow ACL policies associated with namespaces to use agent
+permissions. Nomad requires `agent:read` permissions. In order to use the
+`consul_namespace` feature, Nomad will need a token generated in Consul's
+default namespace. That token should be created with `agent:read` as well
+as a `namespace` block with the other relevant permissions for running Nomad
+in the intended namespace.
+
+This Consul policy shows an example policy configuration for a Nomad server.
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+namespace "nomad-ns" {
+  acl = "write"
+
+  key_prefix "" {
+    policy = "read"
+  }
+
+  node_prefix "" {
+    policy = "read"
+  }
+
+  service_prefix "" {
+    policy = "write"
+  }
+}
+```
+
+### Consul Admin Partition <EnterpriseAlert inline/>
+
+In Nomad Enterprise, if the Consul agent running alongside Nomad is in a Consul
+Enterprise admin partition, you must create the Consul ACL token and ACL policy
+for Nomad clients in the same partition.
+
+
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[bootstrap]: /nomad/tutorials/manage-clusters/clustering 'Automatic Bootstrapping'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[grpc_port]: /consul/docs/agent/config/config-files#grpc_port
+[grpctls_port]: /consul/docs/agent/config/config-files#grpc_tls_port
+[`consul.cluster`]: /nomad/docs/job-specification/group#cluster
+[`service.cluster`]: /nomad/docs/job-specification/service#cluster
+[identity_block]: /nomad/docs/job-specification/identity
+[`template`]: /nomad/docs/job-specification/template
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[auth-method]: /consul/docs/security/acl/auth-methods/jwt
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[consul_bound_aud]: /consul/docs/security/acl/auth-methods/jwt#boundaudiences
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[consul_config_entry]: /consul/docs/connect/config-entries
diff --git a/content/nomad/v1.9.x/content/docs/configuration/index.mdx b/content/nomad/v1.9.x/content/docs/configuration/index.mdx
new file mode 100644
index 0000000000..9de3ecefdc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/index.mdx
@@ -0,0 +1,407 @@
+---
+layout: docs
+page_title: Nomad Agent Configuration
+description: This section contains reference information for configuring Nomad agents. Learn how Nomad loads and merges multiple configuration files. Configure networking and advertise addresses, Nomad regions and datacenters, data directories, Consul integration, handshake limits, connections per client, logging, plugins, Sentinel policies, security, update check behavior, and Vault integration. Enable debugging, write to syslog, leave on interrupt or terminate, and cross-origin resource sharing (CORS).
+---
+
+# Nomad Agent Configuration
+
+This page provides an overview of reference information for configuring Nomad
+agents. Learn how Nomad loads and merges multiple configuration files. Configure
+networking and advertise addresses, Nomad regions and data centers, data
+directories, Consul integration, handshake limits, connections per client,
+logging, plugins, Sentinel policies, security, update check behavior, and Vault
+integration. Enable debugging, writing to syslog, leave on interrupt or
+terminate, and cross-origin resource sharing (CORS).
+
+Write configuration files in [HCL][hcl] or specify parameters as command-line
+flags. Nomad can read and combine parameters from multiple configuration files
+or directories to configure the Nomad agent.
+
+## Configuration File Load Order and Merging
+
+The Nomad agent supports multiple configuration files, which can be provided
+using the `-config` CLI flag. The flag can accept either a file or folder. In
+the case of a folder, any `.hcl` and `.json` files in the folder will be loaded
+and merged in lexicographical order. Directories are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad agent -config=server.conf -config=/etc/nomad -config=extra.json
+```
+
+This will load configuration from `server.conf`, from `.hcl` and `.json` files
+under `/etc/nomad`, and finally from `extra.json`.
+
+As each file is processed, its contents are merged into the existing
+configuration. When merging, any non-empty values from the latest config file
+will append or replace parameters in the current configuration. An empty value
+means `""` for strings, `0` for integer or float values, and `false` for
+booleans. Since empty values are ignored you cannot disable a parameter like
+`server` mode once you've enabled it.
+
+Please note that `plugin` blocks for a given plugin always replace and
+override each other, rather than being merged.
+
+Here is an example Nomad agent configuration that runs in both client and server
+mode.
+
+```hcl
+data_dir  = "/var/lib/nomad"
+
+bind_addr = "0.0.0.0" # the default
+
+advertise {
+  # Defaults to the first private IP address.
+  http = "1.2.3.4"
+  rpc  = "1.2.3.4"
+  serf = "1.2.3.4:5648" # non-default ports may be specified
+}
+
+server {
+  enabled          = true
+  bootstrap_expect = 3
+}
+
+client {
+  enabled       = true
+}
+
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+
+consul {
+  address = "1.2.3.4:8500"
+}
+
+```
+
+~> Note that it is strongly recommended **not** to operate a node as both
+`client` and `server`, although this is supported to simplify development and
+testing.
+
+## General Parameters
+
+- `acl` `(`[`ACL`]`: nil)` - Specifies configuration which is specific to ACLs.
+
+- `addresses` `(Addresses: refer to explanation)` - Specifies the bind address for
+  individual network services. Any values configured in this block take
+  precedence over the default [bind_addr](#bind_addr). These values should be
+  specified in IP format without a port (ex. `"0.0.0.0"`). To set the port,
+  refer to the [`ports`](#ports) field. The values support [go-sockaddr/template
+  format][go-sockaddr/template].
+
+  - `http` - The address the HTTP server is bound to. This is the most
+    common bind address to change. The `http` field accepts multiple
+    values, separated by spaces, to bind to multiple addresses.
+
+  - `rpc` - The address to bind the internal RPC interfaces to. Should be
+    exposed only to other cluster members if possible.
+
+  - `serf` - The address used to bind the gossip layer to. Both a TCP and UDP
+    listener will be exposed on this address. Should be exposed only to other
+    cluster members if possible.
+
+- `advertise` `(Advertise: refer to explanation)` - Specifies the advertise address for
+  individual network services. This can be used to advertise a different address
+  to the peers of a server or a client node to support more complex network
+  configurations such as NAT. This configuration is optional, and defaults to
+  the bind address of the specific network service if it is not provided. Any
+  values configured in this block take precedence over the default
+  [bind_addr](#bind_addr).
+
+  If the bind address is `0.0.0.0` then the IP address of the default private
+  network interface advertised. The `advertise` values may include an
+  alternate port, but otherwise default to the port used by the bind address.
+  The values support [go-sockaddr/template format][go-sockaddr/template].
+
+  - `http` - The address to advertise for the HTTP interface. This should be
+    reachable by all the nodes from which end users are going to use the Nomad
+    CLI tools.
+
+  - `rpc` - The address used to advertise to Nomad clients for connecting to Nomad
+    servers for RPC. This allows Nomad clients to connect to Nomad servers from
+    behind a NAT gateway. This address much be reachable by all Nomad client nodes.
+    When set, the Nomad servers will use the `advertise.serf` address for RPC
+    connections amongst themselves. Setting this value on a Nomad client has no
+    effect.
+
+  - `serf` - The address advertised for the gossip layer. This address must be
+    reachable from all server nodes. It is not required that clients can reach
+    this address. Nomad servers will communicate to each other over RPC using
+    the advertised Serf IP and advertised RPC Port.
+
+- `audit` `(`[`Audit`]`: nil)` - Enterprise-only. Specifies audit logging
+  configuration.
+
+- `bind_addr` `(string: "0.0.0.0")` - Specifies which address the Nomad
+  agent should bind to for network services, including the HTTP interface as
+  well as the internal gossip protocol and RPC mechanism. This should be
+  specified in IP format, and can be used to easily bind all network services to
+  the same address. It is also possible to bind the individual services to
+  different addresses using the [addresses](#addresses) configuration option.
+  Dev mode (`-dev`) defaults to localhost.
+  The value supports [go-sockaddr/template format][go-sockaddr/template].
+
+- `client` `(`[`Client`]`: nil)` - Specifies configuration which is specific
+  to the Nomad client.
+
+- `consul` `(`[`Consul`]`: nil)` - Specifies configuration for
+  connecting to Consul.
+
+- `datacenter` `(string: "dc1")` - Specifies the data center of the local agent. A datacenter is an abstract grouping of clients within a region. Clients are not required to be in the same datacenter as the servers they are joined with, but do need to be in the same region.
+
+- `data_dir` `(string: required)` - Specifies a local directory used to store
+  agent state. Client nodes use this directory by default to store temporary
+  allocation data as well as cluster information. Server nodes use this
+  directory to store cluster state, including the replicated log and snapshot
+  data. This must be specified as an absolute path. Nomad will create the
+  directory on the host, if it does not exist when the agent process starts.
+
+- `disable_anonymous_signature` `(bool: false)` - Specifies if Nomad should
+  provide an anonymous signature for de-duplication with the update check.
+
+- `disable_update_check` `(bool: false)` - Specifies if Nomad should not check
+  for updates and security bulletins. _This defaults to `true` in Nomad Enterprise._
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about Nomad's internals.
+
+- `enable_syslog` `(bool: false)` - Specifies if the agent should log to syslog.
+  This option only works on Unix based systems. The log level inherits from
+  the Nomad agent log set in `log_level`
+
+- `http_api_response_headers` `(map<string|string>: nil)` - Specifies
+  user-defined headers to add to the HTTP API responses.
+
+- `leave_on_interrupt` `(bool: false)` - Specifies if the agent should leave
+  when receiving the interrupt signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `leave_on_terminate` `(bool: false)` - Specifies if the agent should leave
+  when receiving the terminate signal. By default, any stop signal to an agent
+  (interrupt or terminate) will cause the agent to exit after ensuring its
+  internal state is committed to disk as needed. If this value is set to true on
+  a server agent, the server will notify other servers of their intention to
+  leave the peer set. You should only set this value to true on server agents if
+  the terminated server will never join the cluster again. If this value is set
+  to true on a client agent and the client is configured with
+  [`drain_on_shutdown`][], the client will drain its workloads before shutting
+  down.
+
+- `limits` - This is a nested object that configures limits that are enforced by
+   the agent. The following parameters are available:
+
+  - `https_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long the HTTPS server in both client and server agents will wait for a
+    client to complete a TLS handshake. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    [`tls.http = true`][tls] is being used (strongly recommended in
+    production). Default value is `5s`. `0` disables HTTP handshake timeouts.
+
+  - `http_max_conns_per_client` `(int: 100)` - Configures a limit of how many
+    concurrent TCP connections a single client IP address is allowed to open to
+    the agent's HTTP server. This affects the HTTP servers in both client and
+    server agents. Default value is `100`. `0` disables HTTP connection limits.
+
+  - `rpc_handshake_timeout` `(string: "5s")` - Configures the limit for how
+    long servers will wait after a client TCP connection is established before
+    they complete the connection handshake. When TLS is used, the same timeout
+    applies to the TLS handshake separately from the initial protocol
+    negotiation. All Nomad clients should perform this immediately on
+    establishing a new connection. This should be kept conservative as it
+    limits how many connections an unauthenticated attacker can open if
+    TLS is being using to authenticate clients (strongly recommended in
+    production). When `tls.rpc` is true on servers, this limits how long the
+    connection and associated goroutines will be held open before the client
+    successfully authenticates. Default value is `5s`. `0` disables RPC handshake
+    timeouts.
+
+  - `rpc_max_conns_per_client` `(int: 100)` - Configures a limit of how
+    many concurrent TCP connections a single source IP address is allowed
+    to open to a single server. Client agents do not accept RPC TCP connections
+    directly and therefore are not affected. It affects both clients connections
+    and other server connections. Nomad clients multiplex many RPC calls over a
+    single TCP connection, except for streaming endpoints such as [log
+    streaming][log-api] which require their own connection when routed through
+    servers. A server needs at least 2 TCP connections (1 Raft, 1 RPC) per peer
+    server locally and in any federated region. Servers also need a TCP connection
+    per routed streaming endpoint concurrently in use. Only operators use streaming
+    endpoints; as of 0.10.3 Nomad client code does not. A reasonably low limit
+    significantly reduces the ability of an unauthenticated attacker to consume
+    unbounded resources by holding open many connections. You may need to
+    increase this if WAN federated servers connect via proxies or NAT gateways
+    or similar causing many legitimate connections from a single source IP.
+    Default value is `100` which is designed to support the majority of users.
+    `0` disables RPC connection limits. `26` is the minimum as `20` connections
+    are always reserved for non-streaming connections (Raft and RPC) to ensure
+    streaming RPCs do not prevent normal server operation. This minimum may be
+    lowered in the future when streaming RPCs no longer require their own TCP
+    connection.
+
+- `log_level` `(string: "INFO")` - Specifies the verbosity of logs the Nomad
+  agent will output. Valid log levels include `WARN`, `INFO`, `DEBUG`, or
+  `TRACE` in increasing order of verbosity.
+
+- `log_include_location` `(bool: false)` - Include file and line information in
+  each log line.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `log_file` `(string: "")` - Specifies the path for logging. If the path
+  does not includes a filename, the filename defaults to `nomad.log`. This
+  setting can be combined with `log_rotate_bytes` and `log_rotate_duration` for
+  a fine-grained log rotation control.
+
+- `log_rotate_bytes` `(int: 0)` - Specifies the number of bytes that should be
+  written to a log before it needs to be rotated. Unless specified, there is no
+  limit to the number of bytes that can be written to a log file.
+
+- `log_rotate_duration` `(duration: "24h")` - Specifies the maximum duration a
+  log should be written to before it needs to be rotated. Must be a duration
+  value such as 30s.
+
+- `log_rotate_max_files` `(int: 0)` - Specifies the maximum number of older
+  log file archives to keep, not including the log file currently being
+  written. If set to 0 no files are ever deleted. Note that the total number
+  of log files, for each of `stderr` and `stdout`, will be 1 greater than the
+  `log_rotate_max_files` value.
+
+- `name` `(string: [hostname])` - Specifies the name of the local node. This
+  value is used to identify individual agents. When specified on a server, the
+  name must be unique within the region.
+
+- `plugin_dir` `(string: "")` - Specifies the directory to use for looking up
+  plugins. When this parameter is empty, Nomad will generate the path using the
+  [top-level `data_dir`](#data_dir) suffixed with `plugins`, like
+  `"/opt/nomad/plugins"`. This must be an absolute path.
+
+- `plugin` `(`[`Plugin`]`: nil)` - Specifies configuration for a
+  specific plugin. The plugin block may be repeated, once for each plugin being
+  configured. The key of the block is the plugin's executable name relative to
+  the [plugin_dir](#plugin_dir).
+
+- `ports` `(Port: refer to explanation)` - Specifies the network ports used for
+  different services required by the Nomad agent.
+
+  - `http` - The port used to run the HTTP server.
+
+  - `rpc` - The port used for internal RPC communication between
+    agents and servers, and for inter-server traffic for the consensus algorithm
+    (raft).
+
+  - `serf` - The port used for the gossip protocol for cluster
+    membership. Both TCP and UDP should be routable between the server nodes on
+    this port.
+
+    The default values are:
+
+    ```hcl
+    ports {
+      http = 4646
+      rpc  = 4647
+      serf = 4648
+    }
+    ```
+
+- `region` `(string: "global")` - Specifies the region the Nomad agent is a
+  member of. A region typically maps to a geographic region, for example `us`,
+  with potentially multiple zones, which map to [datacenters](#datacenter) such
+  as `us-west` and `us-east`.
+
+  !> **Be Careful!** Changing the `region` of an agent with data stored in its
+  `data_dir` may result in overwrite and data loss in the new region so avoid
+  modifying this value after the agent starts. If you must change it, make sure
+  no local state remains from the previous region before running the agent
+  again.
+
+- `sentinel` `(`[`Sentinel`]`: nil)` - Specifies configuration for Sentinel
+  policies.
+
+- `server` `(`[`Server`]`: nil)` - Specifies configuration which is specific
+  to the Nomad server.
+
+- `syslog_facility` `(string: "LOCAL0")` - Specifies the syslog facility to
+  write to. This has no effect unless `enable_syslog` is true.
+
+- `tls` `(`[`TLS`][tls]`: nil)` - Specifies configuration for TLS.
+
+- `vault` `(`[`Vault`]`: nil)` - Specifies configuration for
+  connecting to Vault.
+
+## Configuration Reload
+
+You can send the Nomad process a `SIGHUP` signal to reload a limited subset of
+its configuration. The fields that currently support reloading are:
+
+- [`log_level`](#log_level): the log level is reloaded but not any other
+  logging configuration value.
+- [`tls`][tls-reload]: note this only reloads the TLS configuration between
+  Nomad agents (servers and clients), and not the TLS configuration for
+  communication with Consul or Vault.
+- [`vault`][vault-reload]: note this only reloads the TLS configuration
+  between Nomad and Vault, but not other configuration values.
+
+In order to reload any other configuration values, you must restart the Nomad
+agent.
+
+<EnterpriseAlert>
+Nomad Enterprise requires a license. If the server.license_path
+configuration or NOMAD_LICENSE_PATH environment variable are set, the
+license will be reloaded from the file on a configuration reload.
+</EnterpriseAlert>
+
+If the Nomad agent receives a `SIGHUP` during initialization, it may crash
+(refer to [GH-3885]). Ensure that the Nomad agent is able to receive RPC traffic
+before attempting to reload its configuration.
+
+## Examples
+
+### Custom Region and Datacenter
+
+This example shows configuring a custom region and data center for the Nomad
+agent:
+
+```hcl
+region     = "europe"
+datacenter = "ams"
+```
+
+### Enable CORS
+
+This example shows how to enable CORS on the HTTP API endpoints:
+
+```hcl
+http_api_response_headers {
+  "Access-Control-Allow-Origin" = "*"
+}
+```
+
+[`acl`]: /nomad/docs/configuration/acl 'Nomad Agent ACL Configuration'
+[`audit`]: /nomad/docs/configuration/audit 'Nomad Agent Audit Logging Configuration'
+[`client`]: /nomad/docs/configuration/client 'Nomad Agent client Configuration'
+[`consul`]: /nomad/docs/configuration/consul 'Nomad Agent consul Configuration'
+[`plugin`]: /nomad/docs/configuration/plugin 'Nomad Agent Plugin Configuration'
+[`sentinel`]: /nomad/docs/configuration/sentinel 'Nomad Agent sentinel Configuration'
+[`server`]: /nomad/docs/configuration/server 'Nomad Agent server Configuration'
+[tls]: /nomad/docs/configuration/tls 'Nomad Agent tls Configuration'
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Agent vault Configuration'
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[log-api]: /nomad/api-docs/client#stream-logs
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[tls-reload]: /nomad/docs/configuration/tls#tls-configuration-reloads
+[vault-reload]: /nomad/docs/configuration/vault#vault-configuration-reloads
+[gh-3885]: https://github.com/hashicorp/nomad/issues/3885
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
diff --git a/content/nomad/v1.9.x/content/docs/configuration/keyring/awskms.mdx b/content/nomad/v1.9.x/content/docs/configuration/keyring/awskms.mdx
new file mode 100644
index 0000000000..70bfa1cd6b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/keyring/awskms.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: AWS Key Management Service (KMS) Keyring Configuration
+description: |-
+  Configure an AWS Key Management Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS authentication. Learn how Nomad supports KMS root key rotation.
+---
+
+# AWS Key Management Service (KMS) Keyring Configuration
+
+This page provides reference information for configuring an AWS Key Management
+Service (KMS) keyring in the `keyring "awskms"` block of a Nomad agent
+configuration. Configure AWS region, KMS API endpoint, KMA key ID, and AWS
+authentication. Learn how Nomad supports KMS root key rotation.
+
+The AWS KMS keyring configures Nomad to use AWS KMS to wrap its keyring. This
+example shows configuring an AWS KMS keyring through the Nomad configuration
+file by providing all the required values.
+
+```hcl
+keyring "awskms" {
+  active = true
+  name   = "example"
+
+  # fields specific to awskms
+  region     = "us-east-1"
+  access_key = "AKIAIOSFODNN7EXAMPLE"
+  secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  kms_key_id = "19ec80b0-dfdd-4d97-8164-c6examplekey"
+  endpoint   = "https://vpce-0e1bb1852241f8cc6-pzi0do8n.kms.us-east-1.vpce.amazonaws.com"
+}
+```
+
+## `awskms` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `region` `(string: "us-east-1")`: The AWS region where the encryption key
+  lives. If not provided, may be populated from the `AWS_REGION` or
+  `AWS_DEFAULT_REGION` environment variables, from your `~/.aws/config` file, or
+  from instance metadata.
+
+- `access_key` `(string: <required>)`: The AWS access key ID to use. Alternately
+  specify via the `AWS_ACCESS_KEY_ID` environment variable or as part of the AWS
+  profile from the AWS CLI or instance profile.
+
+- `session_token` `(string: "")`: Specifies the AWS session token. Alternately
+  specify via the environment variable `AWS_SESSION_TOKEN`.
+
+- `secret_key` `(string: <required>)`: The AWS secret access key to
+  use. Alternately specify via the `AWS_SECRET_ACCESS_KEY` environment variable
+  or as part of the AWS profile from the AWS CLI or instance profile.
+
+- `kms_key_id` `(string: <required>)`: The AWS KMS key ID or ARN to use for
+  encryption and decryption. You can alternately use an alias in the format
+  `alias/key-alias-name`.
+
+- `endpoint` `(string: "")`: The KMS API endpoint for AWS KMS
+  requests. Alternately specify via the `AWS_KMS_ENDPOINT` environment
+  variable. This is useful, for example, when connecting to KMS over a [VPC
+  Endpoint][]. If not set, Nomad uses the default API endpoint for your region.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file allows you to pass in
+`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as part of the keyring block's
+parameters, we strongly recommended that you set these values via environment
+variables or instance profile.
+
+AWS authentication values:
+
+- `AWS_REGION` or `AWS_DEFAULT_REGION`
+- `AWS_ACCESS_KEY_ID`
+- `AWS_SECRET_ACCESS_KEY`
+
+Note: The client uses the official AWS SDK and the specified credentials,
+environment credentials, shared file credentials, or IAM role/ECS task
+credentials in that order, if you do not provide the aforementioned AWS-specific
+values. Refer to the [AWS SDK and Tools standard credentials][aws-std-creds]
+documentation.
+
+Nomad needs the following permissions on the KMS key:
+
+- `kms:Encrypt`
+- `kms:Decrypt`
+- `kms:DescribeKey`
+
+Grant these via IAM permissions on the principal that Nomad uses, on the KMS key
+policy for the KMS key, or via KMS Grants on the key.
+
+## Key rotation
+
+This keyring supports rotating the root keys defined in AWS KMS
+[doc][rotate_docs]. Both automatic rotation and manual rotation is supported for
+KMS since the key information is stored with the encrypted data. Old keys must
+not be disabled or deleted and are used to decrypt older data. Any new or
+updated data is encrypted with the current key defined in the keyring
+configuration or set to current under a key alias.
+
+[VPC Endpoint]: https://docs.aws.amazon.com/kms/latest/developerguide/kms-vpc-endpoint.html
+[rotate_docs]: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html
+[aws-std-creds]: https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html
diff --git a/content/nomad/v1.9.x/content/docs/configuration/keyring/azurekeyvault.mdx b/content/nomad/v1.9.x/content/docs/configuration/keyring/azurekeyvault.mdx
new file mode 100644
index 0000000000..7819d1e196
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/keyring/azurekeyvault.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Azure Key Vault Keyring Configuration
+description: >-
+  Configure an Azure Key Vault keyring in the `keyring "azurekeyvault"` block of a Nomad agent configuration. Configure the Key Vault resource's DNS, Azure Cloud environment variables and API endpoints, and vault and key names. Learn how Nomad supports rotating keys defined in Azure Key Vault.
+---
+
+# Azure Key Vault Keyring Configuration
+
+This page provides reference information for configuring an Azure Key Vault
+keyring in the `keyring "azurekeyvault"` block of a Nomad agent
+configuration. Configure the Key Vault resource's DNS, Azure Cloud environment
+API endpoints, vault and key names, tenant and client IDs, and the client secret. Learn how Nomad supports rotating keys defined in Azure Key
+Vault.
+
+The Azure Key Vault keyring configures Nomad to use Azure Key Vault to wrap its
+keyring. This example shows configuring Azure Key Vault keyring through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "azurekeyvault" {
+  active = true
+  name   = "example"
+
+  # fields specific to azurekeyvault
+  tenant_id      = "46646709-b63e-4747-be42-516edeaf1e14"
+  client_id      = "03dc33fc-16d9-4b77-8152-3ec568f8af6e"
+  client_secret  = "DUJDS3..."
+  vault_name     = "nomad"
+  key_name       = "nomad_key"
+}
+```
+
+## `azurekeyvault` parameters
+
+These parameters apply to the `keyring` block in the Nomad configuration file:
+
+- `tenant_id` `(string: <required>)`: The tenant id for the Azure Active
+  Directory organization. Alternately specify via the `AZURE_TENANT_ID`
+  environment variable.
+
+- `client_id` `(string: <required or MSI>)`: The client id for credentials to
+  query the Azure APIs. Alternately specify via the `AZURE_CLIENT_ID`
+  environment variable.
+
+- `client_secret` `(string: <required or MSI>)`: The client secret for
+  credentials to query the Azure APIs. Alternately specify via the
+  `AZURE_CLIENT_SECRET` environment variable.
+
+- `environment` `(string: "AZUREPUBLICCLOUD")`: The Azure Cloud environment API
+  endpoints to use. Alternately specify via the `AZURE_ENVIRONMENT` environment
+  variable.
+
+- `vault_name` `(string: <required>)`: The Key Vault vault to use the encryption
+  keys for encryption and decryption.
+
+- `key_name` `(string: <required>)`: The Key Vault key to use for encryption and
+  decryption.
+
+- `resource` `(string: "vault.azure.net")`: The Key Vault resource's DNS
+  Suffix to connect to. Alternately specify via the `AZURE_AD_RESOURCE`
+  environment variable. Needs to be changed to connect to Azure's Managed HSM
+  KeyVault instance type.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+Azure authentication values:
+
+- `AZURE_TENANT_ID`
+- `AZURE_CLIENT_ID`
+- `AZURE_CLIENT_SECRET`
+- `AZURE_ENVIRONMENT`
+- `AZURE_AD_RESOURCE`
+
+~> **Note:** If Nomad is hosted on Azure, Nomad can use Managed Service
+Identities (MSI) to access Azure instead of an environment and shared client id
+and secret. MSI must be [enabled][msi_enabled] on the VMs hosting Nomad. We
+recommend this configuration since MSI prevents your Azure credentials from
+being stored as clear text.
+
+-> **Note:** If you are using a Managed HSM KeyVault, you must specify
+`AZURE_AD_RESOURCE` or the `resource` configuration parameter; usually this
+should point to `managedhsm.azure.net` but could point to other suffixes
+depending on Azure environment.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Azure Key Vault. Key metadata is
+stored with the encrypted data to ensure the correct key is used during
+decryption operations. Set up Azure Key Vault with [key rotation][] using Azure
+Automation Account so Vault recognizes newly rotated keys.
+
+[msi_enabled]: https://docs.microsoft.com/en-us/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm
+[key rotation]: https://docs.microsoft.com/en-us/azure/key-vault/key-vault-key-rotation-log-monitoring
diff --git a/content/nomad/v1.9.x/content/docs/configuration/keyring/gcpckms.mdx b/content/nomad/v1.9.x/content/docs/configuration/keyring/gcpckms.mdx
new file mode 100644
index 0000000000..00ad5ff915
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/keyring/gcpckms.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: Google Cloud Platform Key Management Service Keyring Configuration
+description: >-
+  Configure a Google Cloud Platform Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block of a Nomad agent configuration. Configure GCP credentials, project, region, key ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP Cloud KMS.
+---
+
+# Google Cloud Platform Key Management Service Keyring Configuration
+
+This page provides reference information for configuring a Google Cloud Platform
+Key Management Service (GCP Cloud KMS) keyring in the `keyring "gcpckms"` block
+of a Nomad agent configuration. Configure GCP credentials, project, region, key
+ring, and crypto key. Learn how Nomad supports rotating keys defined in GCP
+Cloud KMS.
+
+The GCP Cloud KMS keyring configures Nomad to use GCP Cloud KMS to wrap its
+keyring. This example shows configuring GCP Cloud KMS keyring through the Nomad
+configuration file by providing all the required values.
+
+```hcl
+keyring "gcpckms" {
+  active = true
+  name   = "example"
+
+  credentials = "/etc/nomad.d/nomad-user-creds.json"
+  project     = "nomad-project"
+  region      = "global"
+  key_ring    = "nomad-keyring"
+  crypto_key  = "nomad-key"
+}
+```
+
+## `gcpckms` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `credentials` `(string: <required>)`: The path to the credentials JSON file to
+  use. Alternately specify via the `GOOGLE_CREDENTIALS` or
+  `GOOGLE_APPLICATION_CREDENTIALS` environment variable or set automatically if
+  running under Google Compute Engine.
+
+- `project` `(string: <required>)`: The GCP project ID to use. Alternately
+  specify via the `GOOGLE_PROJECT` environment variable.
+
+- `region` `(string: <required>)`: The GCP region/location where the key ring
+  lives. Alternately specify via the `GOOGLE_REGION` environment variable.
+
+- `key_ring` `(string: <required>)`: The GCP KMS key ring to use.
+
+- `crypto_key` `(string: <required>)`: The GCP KMS crypto key to use for
+  encryption and decryption.
+
+## Authentication &amp; permissions
+
+You must provide authentication-related values either as environment
+variables or as configuration parameters.
+
+GCP authentication values:
+
+- `GOOGLE_CREDENTIALS` or `GOOGLE_APPLICATION_CREDENTIALS`
+- `GOOGLE_PROJECT`
+- `GOOGLE_REGION`
+
+Note: The client uses the official Google SDK and the specified credentials,
+environment credentials, or [application default credentials][] in that order,
+if you do not provide the aforementioned GCP-specific values.
+
+The service account needs the following minimum permissions on the crypto key:
+
+```text
+cloudkms.cryptoKeyVersions.useToEncrypt
+cloudkms.cryptoKeyVersions.useToDecrypt
+cloudkms.cryptoKeys.get
+```
+
+These permissions can be described with the following role:
+
+```text
+roles/cloudkms.cryptoKeyEncrypterDecrypter
+cloudkms.cryptoKeys.get
+```
+
+Use `cloudkms.cryptoKeys.get` permission for retrieving metadata information of
+keys from CloudKMS within this engine initialization process.
+
+## Key rotation
+
+This keyring supports rotating keys defined in Google Cloud KMS
+[doc][rotating_keys]. Both scheduled rotation and manual rotation is supported
+for CKMS since the key information. Old keys version must not be disabled or
+deleted and are used to decrypt older data. Any new or updated data is encrypted
+with the primary key version.
+
+
+[application default credentials]: https://developers.google.com/identity/protocols/application-default-credentials
+[rotating_keys]: https://cloud.google.com/kms/docs/rotating-keys
diff --git a/content/nomad/v1.9.x/content/docs/configuration/keyring/index.mdx b/content/nomad/v1.9.x/content/docs/configuration/keyring/index.mdx
new file mode 100644
index 0000000000..b2cdef9bd6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/keyring/index.mdx
@@ -0,0 +1,110 @@
+---
+layout: docs
+page_title: keyring Block in Agent Configuration
+description: >-
+  Configure keyring protection behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring and configure a name. Learn how to configure keyring high availability (HA) and migrate keyrings.
+---
+
+# `keyring` Block in Agent Configuration
+
+<Placement groups={['keyring']} />
+
+This page provides reference information for configuring keyring protection
+behavior in the `keyring` block of a Nomad agent configuration. Enable a keyring
+and configure a name. Learn how to configure keyring high availability (HA) and
+migrate keyrings.
+
+The `keyring` block configures how the Nomad server protects the keyring used
+for encrypting [variables][] and signing [workload identities][]. By default,
+Nomad encrypts the key material with a unique key encryption key (KEK) that is
+not shared between servers, and writes the wrapped key material to disk as
+described in [Key Management][]. Nomad refers to this as `"aead"` (authenticated
+encryption with associated data). Using the `keyring` configuration block, Nomad
+servers can instead use an external key management system (KMS) or Vault transit
+encryption. The encrypted key is stored on disk but is now protected against
+offline attacks because the KEK is not present in the file.
+
+All `keyring` blocks require a label for the KMS type. Each external KMS has its
+own configuration options. The `keyring` block only applies to Nomad servers,
+not Nomad clients.
+
+```hcl
+keyring [TYPE] {
+  name   = "example"
+  active = true
+}
+```
+
+The default `keyring` configuration is as follows:
+
+```hcl
+keyring "aead" {
+  active = true
+}
+```
+
+## `keyring` Parameters
+
+All `keyring` blocks support the following parameters.
+
+- `name` `(string: "")` - A unique identifier for the `keyring` block, used to
+  disambiguate when there are multiple blocks of the same type.
+
+- `active` `(bool: false)` - Indicates which block to use for encrypting
+  keys. For existing servers, changing which block is `active` only impacts new
+  keys created by a [key rotation][]. Existing keys are encrypted with the
+  previous `active` block, so those blocks should not be removed from the
+  configuration until they have been garbage collected and the keys have been
+  removed from the keystore. In Nomad Community Edition, only a single keyring
+  can be `active` at a time.
+
+## Migrating Keyrings
+
+To migrate to a new keyring, add the new `keyring` block to the servers with
+`active=true`, and restart the servers. The server starts using the new keyring
+wrapper when the current key is rotated either periodically or via the [`nomad
+operator root keyring rotate`][keyring_rotate_cmd] command.
+
+Adding or removing a keyring requires restarting the Nomad server. You should
+not remove a keyring until all keys it wraps have been garbage collected. You
+can examine the contents of the `keystore` directory found in the Nomad server's
+data directory and compare this against the output of [`nomad operator root
+keyring list`][keyring_list_cmd].
+
+## High Availability
+
+<EnterpriseAlert product="nomad"/>
+
+Keyring high availability provides the means to configure multiple active
+`keyring` blocks, in order to have resilience against an outage of an external
+KMS. When there are multiple `keyring` blocks with `active = true`, Nomad
+Enterprise encrypts each key it creates in all the active KMS providers. On
+startup, Nomad tries each KMS provider in order until it finds a provider that
+can decrypt each key.
+
+In this example high availability configuration, both `keyring` blocks use the
+`"awskms"` provider, but each block uses a different KMS key in a different AWS
+region.
+
+```hcl
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-1"
+  region     = "us-east-1"
+  kms_key_id = "arn:aws:kms:us-east-1:000000000000:key/7d23633a-4464-11ef-a273-abd12example"
+}
+
+keyring "awskms" {
+  active     = true
+  name       = "kms-us-east-2"
+  region     = "us-east-2"
+  kms_key_id = "alias/nomad-keyring-us-east-2"
+}
+```
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[Key Management]: /nomad/docs/operations/key-management
+[key rotation]: /nomad/docs/operations/key-management#key-rotation
+[keyring_rotate_cmd]: /nomad/docs/commands/operator/root/keyring-rotate
+[keyring_list_cmd]: /nomad/docs/commands/operator/root/keyring-list
diff --git a/content/nomad/v1.9.x/content/docs/configuration/keyring/transit.mdx b/content/nomad/v1.9.x/content/docs/configuration/keyring/transit.mdx
new file mode 100644
index 0000000000..544ee23f9d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/keyring/transit.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: Vault Transit Keyring Configuration
+description: |-
+  Configure a Vault transit secrets engine keyring in the `keyring "transit"` block of a Nomad agent configuration. Configure the address to the Vault cluster, key name, mount path, namespace, TLS authentication, and whether to disable Vault token automatic renewal. Learn how Nomad supports rotating keys defined in Vault's transit secrets engine.
+---
+
+# Vault Transit Keyring Configuration
+
+This page provides reference information for configuring a Vault transit secrets
+engine keyring in the `keyring "transit"` block of a Nomad agent configuration.
+Configure the address to the Vault cluster, key name, mount path, namespace, TLS
+authentication, and whether to disable Vault token automatic renewal. Learn how
+Nomad supports rotating keys defined in Vault's transit secrets engine.
+
+The Vault transit keyring configures Nomad to use Vault's transit secrets engine
+to wrap its keyring. This example shows configuring Vault transit through the
+Nomad configuration file by providing all the required values.
+
+```hcl
+keyring "transit" {
+
+  active = true
+  name   = "example"
+
+  # fields specific to transit
+  address            = "https://vault:8200"
+  token              = "s.Qf1s5zigZ4OX6akYjQXJC1jY"
+  disable_renewal    = "false"
+
+  # Key configuration
+  key_name           = "transit_key_name"
+  mount_path         = "transit/"
+  namespace          = "ns1/"
+
+  # TLS Configuration
+  tls_ca_cert        = "/etc/vault/ca_cert.pem"
+  tls_client_cert    = "/etc/vault/client_cert.pem"
+  tls_client_key     = "/etc/vault/ca_cert.pem"
+  tls_server_name    = "vault"
+  tls_skip_verify    = "false"
+}
+```
+
+## `transit` parameters
+
+These parameters apply to the `keyring` stanza in the Nomad configuration file:
+
+- `key_name` `(string: <required>)`: The transit key to use for encryption and
+  decryption.
+
+- `key_id_prefix` `(string: "")`: An optional string to add to the key id of
+  values wrapped by this transit keyring. This can help disambiguate between two
+  transit keyring.
+
+- `mount_path` `(string: <required>)`: The mount path to the transit secret
+  engine.
+
+- `disable_renewal` `(string: "false")`: Disables the automatic renewal of the
+  token in case the lifecycle of the token is managed with some other mechanism
+  outside of Vault, such as Vault Agent.
+
+Set the following parameters in the `keyring` block. If not set here, Nomad uses
+the values set in the server's [`vault`][vault_config] block. You must set
+required fields either here or the `vault` block.
+
+- `address` `(string: <required>)`: The full address to the Vault cluster.
+  Alternately specify via the `VAULT_ADDR` environment variable.
+
+- `token` `(string: <required>)`: The Vault token to use. Alternately specify
+  via the `VAULT_TOKEN` environment variable.
+
+- `namespace` `(string: "")`: The namespace path to the transit secret engine.
+   Alternately specify via the `VAULT_NAMESPACE` environment variable.
+
+- `tls_ca_cert` `(string: "")`: Specifies the path to the CA certificate file
+  used for communication with the Vault server. Alternately specify via the
+  `VAULT_CACERT` environment variable.
+
+- `tls_client_cert` `(string: "")`: Specifies the path to the client certificate
+  for communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_CERT` environment variable.
+
+- `tls_client_key` `(string: "")`: Specifies the path to the private key for
+  communication with the Vault server. Alternately specify via the
+  `VAULT_CLIENT_KEY` environment variable.
+
+- `tls_server_name` `(string: "")`: Name to use as the SNI host when connecting
+  to the Vault server via TLS. Alternately specify via the
+  `VAULT_TLS_SERVER_NAME` environment variable.
+
+- `tls_skip_verify` `(bool: "false")`: Disable verification of TLS certificates.
+  Using this option is highly discouraged and decreases the security of data
+  transmissions to and from the Vault server. Alternately specify via the
+  `VAULT_SKIP_VERIFY` environment variable.
+
+## Authentication
+
+You must provide authentication-related values either as environment variables
+or as configuration parameters.
+
+~> **Note:** Although the configuration file lets you to pass in `VAULT_TOKEN`
+as part of the keyring's parameters, we strongly recommended that you set these
+values via environment variables.
+
+The Vault authentication token needs the following permissions on the transit
+key:
+
+```hcl
+path "<mount path>/encrypt/<key name>" {
+  capabilities = ["update"]
+}
+
+path "<mount path>/decrypt/<key name>" {
+  capabilities = ["update"]
+}
+```
+
+Other considerations for the token used:
+* It should probably be an [orphan token][], otherwise when the parent token
+  expires or gets revoked the keyring breaks.
+* Consider making it a [periodic token][] and not setting an explicit max TTL,
+  otherwise at some point it ceases to be renewable.
+
+## Key rotation
+
+This keyring supports key rotation using Vault's transit secrets engine's key
+rotation endpoints. Refer to [Vault docs][rotate_doc] for details. Old keys must
+not be disabled or deleted and are used to decrypt older data.
+
+[orphan token]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens
+[periodic token]: /vault/docs/concepts/tokens#periodic-tokens
+[rotate_doc]: /vault/api-docs/secret/transit#rotate-key
+[vault_config]: https://developer.hashicorp.com/nomad/docs/configuration/vault
diff --git a/content/nomad/v1.9.x/content/docs/configuration/plugin.mdx b/content/nomad/v1.9.x/content/docs/configuration/plugin.mdx
new file mode 100644
index 0000000000..d3d5d4d4a8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/plugin.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: plugin Block in Agent Configuration
+description: Configure task driver and device driver plugins in the `plugin` block of a Nomad agent configuration. Specify arguments to pass to the plugin. Configure values specific to the plugin.
+---
+
+# `plugin` Block in Agent Configuration
+
+<Placement groups={['plugin']} />
+
+This page provides reference information for configuring task driver and device
+driver plugins in the `plugin` block of a Nomad agent configuration. Specify
+arguments to pass to the plugin. Configure values specific to the plugin.
+
+Refer to the [Nomad plugins guide](/nomad/plugins) for details on specific task
+driver and device plugins.
+
+```hcl
+plugin "example-plugin" {
+    args = ["-my-flag"]
+    config {
+       foo = "bar"
+       bam {
+         baz = 1
+       }
+    }
+}
+```
+
+The name of the plugin is the plugin's executable name relative to to the
+[plugin_dir](/nomad/docs/configuration#plugin_dir). If the plugin has a
+suffix, such as `.exe`, this should be omitted.
+
+## `plugin` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `config` `(hcl/json: nil)` - Specifies configuration values for the plugin
+  either as HCL or JSON. The accepted values are plugin specific. Please refer
+  to the individual plugin's documentation.
diff --git a/content/nomad/v1.9.x/content/docs/configuration/reporting.mdx b/content/nomad/v1.9.x/content/docs/configuration/reporting.mdx
new file mode 100644
index 0000000000..d00fdaaa42
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/reporting.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: reporting Block in Agent Configuration
+description: >-
+  Enable automated license utilization reporting in the `reporting` block of a Nomad agent configuration. Configuration applies to agents running Nomad Enterprise with server mode enabled.
+---
+
+# `reporting` Block in Agent Configuration
+
+<Placement groups={['reporting']} />
+<EnterpriseAlert product="nomad"/>
+
+This page provides reference information for enabling automated license
+utilization reporting in the `reporting` block of a Nomad agent configuration.
+
+Configuration applies to agents running with [server mode
+enabled][server_mode_enabled].
+
+Refer to the [Automated license utilization reporting
+guide][automated_license_utilization_reporting] for which ports to open and what
+data is shared.
+
+```hcl
+reporting {
+    license {
+      enabled = true
+    }
+}
+```
+
+## `reporting` Parameters
+
+- `license` <code>([license](#license-block): default)</code> - Configures
+  automated license utilization reporting.
+
+## `license` Block
+
+- `enabled` `(bool: true)` - Specifies whether automated license utilization
+  reporting should be enabled and run.
+
+[server_mode_enabled]: /nomad/docs/configuration/server#enabled
+[automated_license_utilization_reporting]: /nomad/docs/enterprise/license/utilization-reporting
diff --git a/content/nomad/v1.9.x/content/docs/configuration/search.mdx b/content/nomad/v1.9.x/content/docs/configuration/search.mdx
new file mode 100644
index 0000000000..526e0d11c5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/search.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: search Block in Agent Configuration
+sidebar_title: search
+description: >-
+  Configure the Nomad server search API in the `search` block of a Nomad agent configuration. Enable fuzzy searching. Configure the minimum size of the search term, the maximum number of Nomad objects to search through per context type, and the max number of matching results.
+---
+
+# `search` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'search'],
+  ]}
+/>
+
+This page provides reference information for configuring the Nomad server search
+API in the `search` block of a Nomad agent configuration. Enable fuzzy
+searching. Configure the minimum size of the search term, the maximum number of
+Nomad objects to search through per context type, and the max number of matching results.
+
+```hcl
+server {
+  search {
+    fuzzy_enabled   = true
+    limit_query     = 200
+    limit_results   = 1000
+    min_term_length = 5
+  }
+}
+```
+
+## `search` Parameters
+
+- `fuzzy_enabled` `(bool: true)` - Specifies whether the [fuzzy search API][fuzzy]
+  is enabled. If not enabled, requests to the fuzzy search API endpoint will return
+  an error response.
+
+- `limit_query` `(int: 20)` - Specifies the maximum number of Nomad objects to
+  search through per context type in the Nomad server before truncating results.
+  Setting this parameter to a high value may degrade Nomad server performance.
+
+- `limit_results` `(int: 100)` - Specifies the maximum number of matching results
+  to accumulate per context type in the API response before truncating results.
+  Setting this parameter to a high value may cause excessively large API response sizes.
+
+- `min_term_length` `(int: 2)` - Specifies the minimum size of the search term
+  allowed for matching with the fuzzy search API. Setting this value higher can
+  prevent unnecessary load on the Nomad server from broad queries.
+
+[fuzzy]: /nomad/api-docs/search#fuzzy-searching
diff --git a/content/nomad/v1.9.x/content/docs/configuration/sentinel.mdx b/content/nomad/v1.9.x/content/docs/configuration/sentinel.mdx
new file mode 100644
index 0000000000..227d57fad1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/sentinel.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: sentinel Block in Agent Configuration
+description: >-
+  Configure Sentinel policy engine behavior in the "sentinel" block of a Nomad agent configuration. Configure the path to the plugin that Nomad uses to import Sentinel policies and specify arguments to pass to that plugin on startup.
+---
+
+# `sentinel` Block in Agent Configuration
+
+<Placement groups={['sentinel']} />
+<EnterpriseAlert product="nomad"/>
+
+This page provides reference information for configuring the Sentinel policy
+engine in the `sentinel` block of a Nomad agent configuration. Configure the
+path to the plugin that Nomad uses to import Sentinel policies and specify
+arguments to pass to that plugin on startup.
+
+```hcl
+sentinel {
+    import "custom-plugin" {
+        path = "/usr/bin/sentinel-custom-plugin"
+        args = ["-verbose", "foo"]
+    }
+}
+```
+
+## `sentinel` Parameters
+
+- `import` <code>([Import](#import-parameters): nil)</code> -
+  Specifies a plugin that should be made available for importing by Sentinel policies.
+  The name of the import matches the name that can be imported.
+
+### `import` Parameters
+
+- `path` `(string: "")` - Specifies the path to the import plugin. Must be executable by Nomad.
+
+- `args` `(array<string>: [])` - Specifies arguments to pass to the plugin when starting it.
+
+## Resources
+
+Refer to these resources for details on using Sentinel policies with
+Nomad:
+
+- [Governance and policy on
+  Nomad](/nomad/tutorials/governance-and-policy/governance-and-policy)
+- [Sentinel policies](/nomad/tutorials/governance-and-policy/sentinel)
+- [Sentinel policy
+  reference](https://developer.hashicorp.com/nomad/docs/enterprise/sentinel)
+
+
+
diff --git a/content/nomad/v1.9.x/content/docs/configuration/server.mdx b/content/nomad/v1.9.x/content/docs/configuration/server.mdx
new file mode 100644
index 0000000000..4f22837285
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/server.mdx
@@ -0,0 +1,529 @@
+---
+layout: docs
+page_title: server Block in Agent Configuration
+description: |-
+  Configure Nomad agent server mode in the `server` block of a Nomad agent configuration. Server mode lets the agent participate in scheduling decisions, register with service discovery, and handle join failures. Configure bootstrapping, authoritative region, redundancy zone, data directory, Nomad cluster behavior, client heartbeat period, schedulers, garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity, leader plan rejection, as well as job priority, job source content size, and tracked job versions.
+---
+
+# `server` Block in Agent Configuration
+
+<Placement groups={['server']} />
+
+This page provides reference information for configuring Nomad agent server mode
+in the `server` block of a Nomad agent configuration. Server mode lets the agent
+participate in scheduling decisions, register with service discovery, and handle
+join failures. Configure bootstrapping, authoritative region, redundancy zone,
+data directory, Nomad cluster behavior, client heartbeat period, schedulers,
+garbage collection, Raft and Raft's BoltDB store, OIDC for workload identity,
+and leader plan rejection, as well as job priority, job source content size, and
+tracked job versions.
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+## `server` Parameters
+
+- `authoritative_region` `(string: "")` - Specifies the authoritative region,
+  which provides a single source of truth for global configurations such as ACL
+  Policies and global ACL tokens in multi-region, federated deployments.
+  Non-authoritative regions will replicate from the authoritative to act as a
+  mirror. By default, the local region is assumed to be authoritative. Setting
+  `authoritative_region` assumes that ACLs have been bootstrapped in the
+  authoritative region. Refer to [Configure for multiple regions][] in the ACLs
+  tutorial.
+
+- `bootstrap_expect` `(int: required)` - Specifies the number of server nodes to
+  wait for before bootstrapping. It is most common to use the odd-numbered
+  integers `3` or `5` for this value, depending on the cluster size. A value of
+  `1` does not provide any fault tolerance and is not recommended for production
+  use cases.
+
+- `data_dir` `(string: "")` - Specifies the directory to use for server-specific
+  data, including the replicated log. When this parameter is empty, Nomad will
+  generate the path using the [top-level `data_dir`][top_level_data_dir] suffixed
+  with `server`, like `"/opt/nomad/server"`. The
+  [top-level data_dir][top_level_data_dir] must be set, even when setting this
+  value. This must be an absolute path. Nomad will create the directory on the
+  host, if it does not exist when the agent process starts.
+
+- `enabled` `(bool: false)` - Specifies if this agent should run in server mode.
+  All other server options depend on this value being set.
+
+- `enabled_schedulers` `(array<string>: [all])` - Specifies which sub-schedulers
+  this server will handle. This can be used to restrict the evaluations that
+  worker threads will dequeue for processing.
+
+- `enable_event_broker` `(bool: true)` - Specifies if this server will generate
+  events for its event stream.
+
+- `encrypt` `(string: "")` - Specifies the secret key to use for encryption of
+  Nomad server's gossip network traffic. This key must be 32 bytes that are
+  [RFC4648] "URL and filename safe" base64-encoded. You can generate an
+  appropriately-formatted key with the [`nomad operator gossip keyring
+  generate`] command. The provided key is automatically persisted to the data
+  directory and loaded automatically whenever the agent is restarted. This means
+  that to encrypt Nomad server's gossip protocol, this option only needs to be
+  provided once on each agent's initial startup sequence. If it is provided
+  after Nomad has been initialized with an encryption key, then the provided key
+  is ignored and a warning will be displayed. Refer to the [encryption
+  documentation][encryption] for more details on this option and its impact on
+  the cluster.
+
+- `event_buffer_size` `(int: 100)` - Specifies the number of events generated
+  by the server to be held in memory. Increasing this value enables new
+  subscribers to have a larger look back window when initially subscribing.
+  Decreasing will lower the amount of memory used for the event buffer.
+
+- `node_gc_threshold` `(string: "24h")` - Specifies how long a node must be in a
+  terminal state before it is garbage collected and purged from the system. This
+  is specified using a label suffix like "30s" or "1h".
+
+- `job_gc_interval` `(string: "5m")` - Specifies the interval between the job
+  garbage collections. Only jobs who have been terminal for at least
+  `job_gc_threshold` will be collected. Lowering the interval will perform more
+  frequent but smaller collections. Raising the interval will perform collections
+  less frequently but collect more jobs at a time. Reducing this interval is
+  useful if there is a large throughput of tasks, leading to a large set of
+  dead jobs. This is specified using a label suffix like "30s" or "3m".
+
+- `job_gc_threshold` `(string: "4h")` - Specifies the minimum time a job must be
+  in the terminal state before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `eval_gc_threshold` `(string: "1h")` - Specifies the minimum time an
+  evaluation must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h". Note
+  that batch job evaluations are controlled via `batch_eval_gc_threshold`.
+
+- `batch_eval_gc_threshold` `(string: "24h")` - Specifies the minimum time an
+  evaluation stemming from a batch job must be in the terminal state before it is
+  eligible for garbage collection. This is specified using a label suffix like
+  "30s" or "1h". Note that the threshold is a necessary but insufficient condition
+  for collection, and the most recent evaluation won't be garbage collected even if
+  it breaches the threshold.
+
+- `deployment_gc_threshold` `(string: "1h")` - Specifies the minimum time a
+  deployment must be in the terminal state before it is eligible for garbage
+  collection. This is specified using a label suffix like "30s" or "1h".
+
+- `csi_volume_claim_gc_interval` `(string: "5m")` - Specifies the interval
+  between CSI volume claim garbage collections.
+
+- `csi_volume_claim_gc_threshold` `(string: "1h")` - Specifies the minimum age of
+  a CSI volume before it is eligible to have its claims garbage collected.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `csi_plugin_gc_threshold` `(string: "1h")` - Specifies the minimum age of a
+  CSI plugin before it is eligible for garbage collection if not in use.
+  This is specified using a label suffix like "30s" or "1h".
+
+- `acl_token_gc_threshold` `(string: "1h")` - Specifies the minimum age of an
+  expired ACL token before it is eligible for garbage collection. This is
+  specified using a label suffix like "30s" or "1h".
+
+- `default_scheduler_config` <code>(<a href="/nomad/api-docs/operator/scheduler#update-scheduler-configuration">scheduler_configuration:</a></code>`nil`) - Specifies the initial default scheduler config when
+  bootstrapping cluster. The parameter is ignored once the cluster is
+  bootstrapped or value is updated through the [API
+  endpoint][update-scheduler-config]. Refer to [the example
+  section](#configuring-scheduler-config) for more details.
+
+- `heartbeat_grace` `(string: "10s")` - Specifies the additional time given
+  beyond the heartbeat TTL of Clients to account for network and processing
+  delays and clock skew. This is specified using a label suffix like "30s" or
+  "1h". Refer to the [Client Heartbeats](#client-heartbeats) section for
+  details.
+
+- `min_heartbeat_ttl` `(string: "10s")` - Specifies the minimum time between
+  Client heartbeats. This is used as a floor to prevent excessive updates. This
+  is specified using a label suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `failover_heartbeat_ttl` `(string: "5m")` - The time by which all Clients must
+  heartbeat after a Server leader election. This is specified using a label
+  suffix like "30s" or "1h". Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `max_heartbeats_per_second` `(float: 50.0)` - Specifies the maximum target
+  rate of heartbeats being processed per second. This allows the TTL to be
+  increased to meet the target rate. Refer to the [Client
+  Heartbeats](#client-heartbeats) section for details.
+
+- `non_voting_server` `(bool: false)` - (Enterprise-only) Specifies whether
+  this server will act as a non-voting member of the cluster to help provide
+  read scalability.
+
+- `num_schedulers` `(int: [num-cores])` - Specifies the number of parallel
+  scheduler threads to run. This can be as many as one per core, or `0` to
+  disallow this server from making any scheduling decisions. This defaults to
+  the number of CPU cores.
+
+- `license_path` `(string: "")` - Specifies the path to load a Nomad Enterprise
+  license from. This must be an absolute path
+  (ex. `/etc/nomad.d/license.hclic`). The license can also be set by setting
+  `NOMAD_LICENSE_PATH` or by setting `NOMAD_LICENSE` as the entire license
+  value. `license_path` has the highest precedence, followed by `NOMAD_LICENSE`
+  and then `NOMAD_LICENSE_PATH`.
+
+- `plan_rejection_tracker` <code>([PlanRejectionTracker](#plan_rejection_tracker-parameters))</code> -
+  Configuration for the plan rejection tracker that the Nomad leader uses to
+  track the history of plan rejections.
+
+- `raft_boltdb` - This is a nested object that allows configuring options for
+  Raft's BoltDB based log store.
+    - `no_freelist_sync` - Setting this to `true` will disable syncing the BoltDB
+    freelist to disk within the `raft.db` file. Not syncing the freelist to disk
+    will reduce disk IO required for write operations at the expense of longer
+    server startup times.
+
+- `raft_protocol` `(int: 3)` - Specifies the Raft protocol version to use when
+  communicating with other Nomad servers. This affects available Autopilot
+  features and is typically not required as the agent internally knows the
+  latest version, but may be useful in some upgrade scenarios. Must be `3` in
+  Nomad v1.4 or later.
+
+- `raft_multiplier` `(int: 1)` - An integer multiplier used by Nomad servers to
+  scale key Raft timing parameters. Omitting this value or setting it to 0 uses
+  default timing described in the following paragraph. Lower values are used to
+  tighten timing and increase sensitivity while higher values relax timings and
+  reduce sensitivity. Tuning this affects the time it takes Nomad to detect
+  leader failures and to perform leader elections, at the expense of requiring
+  more network and CPU resources for better performance. The maximum allowed
+  value is 10.
+
+  By default, Nomad will use the highest-performance timing, currently equivalent
+  to setting this to a value of 1. Increasing the timings makes leader election
+  less likely during periods of networking issues or resource starvation. Since
+  leader elections pause Nomad's normal work, it may be beneficial for slow or
+  unreliable networks to wait longer before electing a new leader. The trade-off
+  when raising this value is that during network partitions or other events
+  (server crash) where a leader is lost, Nomad will not elect a new leader for
+  a longer period of time than the default. The [`nomad.nomad.leader.barrier` and
+  `nomad.raft.leader.lastContact` metrics](/nomad/docs/operations/metrics-reference) are a good
+  indicator of how often leader elections occur and Raft latency.
+
+- `raft_snapshot_threshold` `(int: "8192")` - Specifies the minimum number of
+  Raft logs to be written to disk before the node is allowed to take a snapshot.
+  This reduces the frequency and impact of creating snapshots. During node
+  startup, Raft restores the latest snapshot and then applies the individual
+  logs to catch the node up to the last known state. This can be tuned during
+  operation by a hot configuration reload.
+
+- `raft_snapshot_interval` `(string: "120s")` - Specifies the minimum time between
+  checks if Raft should perform a snapshot. The Raft library randomly staggers
+  between this value and twice this value to avoid the entire cluster performing
+  a snapshot at once. Nodes are eligible to snapshot once they have exceeded the
+  `raft_snapshot_threshold`. This value can be tuned during operation by a hot
+  configuration reload.
+
+- `raft_trailing_logs` `(int: "10240")` - Specifies how many logs are retained
+  after a snapshot. These logs are used so that Raft can quickly replay logs on
+  a follower instead of being forced to send an entire snapshot. This value can
+  be tuned during operation by a hot configuration reload.
+
+- `redundancy_zone` `(string: "")` - (Enterprise-only) Specifies the redundancy
+  zone that this server will be a part of for Autopilot management. For more
+  information, refer to the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `rejoin_after_leave` `(bool: false)` - Specifies if Nomad will ignore a
+  previous leave and attempt to rejoin the cluster when starting. By default,
+  Nomad treats leave as a permanent intent and does not attempt to join the
+  cluster again when starting. This flag allows the previous state to be used to
+  rejoin the cluster.
+
+- `root_key_gc_interval` `(string: "10m")` - Specifies the interval between
+  [encryption key][] metadata garbage collections.
+
+- `root_key_gc_threshold` `(string: "1h")` - Specifies the minimum time after
+  the `root_key_rotation_threshold` has passed that an [encryption key][] must
+  exist before it can be eligible for garbage collection.
+
+- `root_key_rotation_threshold` `(string: "720h")` - Specifies the lifetime of
+  an active [encryption key][] before it is automatically rotated on the next
+  garbage collection interval. Nomad will prepublish the replacement key at half
+  the `root_key_rotation_threshold` time so external consumers of Workload
+  Identity have time to obtain the new public key from the [JWKS URL][] before
+  it is used.
+
+- `server_join` <code>([server_join][server-join]: nil)</code> - Specifies
+  how the Nomad server will connect to other Nomad servers. The `retry_join`
+  fields may directly specify the server address or use go-discover syntax for
+  auto-discovery. Refer to the [server_join documentation][server-join] for more detail.
+
+- `upgrade_version` `(string: "")` - A custom version of the format X.Y.Z to use
+  in place of the Nomad version when custom upgrades are enabled in Autopilot.
+  For more information, refer to the [Autopilot Guide](/nomad/tutorials/manage-clusters/autopilot).
+
+- `search` <code>([search][search]: nil)</code> - Specifies configuration parameters
+  for the Nomad search API.
+
+- `job_max_priority` `(int: 100)` - Specifies the maximum priority that can be assigned to a job.
+   A valid value must be between `100` and `32766`.
+
+- `job_default_priority` `(int: 50)` - Specifies the default priority assigned to a job.
+   A valid value must be between `50` and `job_max_priority`.
+
+- `job_max_source_size` `(string: "1M")` - Specifies the size limit of the associated
+  job source content when registering a job. Note this is not a limit on the actual
+  size of a job. If the limit is exceeded, the original source is simply discarded
+  and no error is returned from the job API.
+
+- `job_tracked_versions` `(int: 6)` - Specifies the number of historic job versions that
+  are kept.
+
+- `oidc_issuer` `(string: "")` - Specifies the Issuer URL for [Workload
+    Identity][wi] JWTs. For example, `"https://nomad.example.com"`. If set the
+    `/.well-known/openid-configuration` HTTP endpoint is enabled for third
+    parties to discover Nomad's OIDC configuration.  Once set `oidc_issuer`
+    *cannot be changed* without invalidating Workload Identities that have the
+    old issuer claim. For this reason it is suggested to set `oidc_issuer` to a
+    proxy in front of Nomad's HTTP API to ensure a stable DNS name can be used
+    instead of a potentially ephemeral Nomad server IP.
+
+### Deprecated Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of server addresses to
+  retry joining if the first attempt fails. This is similar to
+  [`start_join`](#start_join), but only invokes if the initial join attempt
+  fails. The list of addresses will be tried in the order specified, until one
+  succeeds. After one succeeds, no further addresses will be contacted. This is
+  useful for cases where we know the address will become available eventually.
+  Use `retry_join` with an array as a replacement for `start_join`, **do not use
+  both options**. Refer to the [server_join][server-join]
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts. This field is deprecated in favor of the [server_join
+  block][server-join].
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries. This field is deprecated in favor of
+  the [server_join block][server-join].
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. Refer to the [server address
+  format](/nomad/docs/configuration/server_join#server-address-format)
+  section for more information on the format of the string. This field is
+  deprecated in favor of the [server_join block][server-join].
+
+### `plan_rejection_tracker` Parameters
+
+The leader plan rejection tracker can be adjusted to prevent evaluations from
+getting stuck due to always being scheduled to a client that may have an
+unexpected issue. Refer to [Monitoring Nomad][monitoring_nomad_progress] for
+more details.
+
+- `enabled` `(bool: false)` - Specifies if plan rejections should be tracked.
+
+- `node_threshold` `(int: 100)` - The number of plan rejections for a node
+  within the `node_window` to trigger a client to be set as ineligible.
+
+- `node_window` `(string: "5m")` - The time window for when plan rejections for
+  a node should be considered.
+
+If you observe too many false positives (clients being marked as ineligible
+even if they don't present any problem) you may want to increase
+`node_threshold`.
+
+Or if you are noticing jobs not being scheduled due to plan rejections for the
+same `node_id` and the client is not being set as ineligible you can try
+increasing the `node_window` so more historical rejections are taken into
+account.
+
+## `server` Examples
+
+### Common Setup
+
+This example shows a common Nomad agent `server` configuration block. The two
+IP addresses could also be DNS, and should point to the other Nomad servers in
+the cluster
+
+```hcl
+server {
+  enabled          = true
+  bootstrap_expect = 3
+
+  server_join {
+    retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+    retry_max      = 3
+    retry_interval = "15s"
+  }
+}
+```
+
+### Configuring Data Directory
+
+This example shows configuring a custom data directory for the server data.
+
+```hcl
+server {
+  data_dir = "/opt/nomad/server"
+}
+```
+
+### Automatic Bootstrapping
+
+The Nomad servers can automatically bootstrap if Consul is configured. For a
+more detailed explanation, refer to the
+[automatic Nomad bootstrapping documentation](/nomad/tutorials/manage-clusters/clustering).
+
+### Restricting Schedulers
+
+This example shows restricting the schedulers that are enabled as well as the
+maximum number of cores to utilize when participating in scheduling decisions:
+
+```hcl
+server {
+  enabled            = true
+  enabled_schedulers = ["batch", "service"]
+  num_schedulers     = 7
+}
+```
+
+### Bootstrapping with a Custom Scheduler Config ((#configuring-scheduler-config))
+
+While [bootstrapping a cluster], you can use the `default_scheduler_config` block
+to prime the cluster with a [`SchedulerConfig`][update-scheduler-config]. The
+scheduler configuration determines which scheduling algorithm is configured—
+spread scheduling or binpacking—and which job types are eligible for preemption.
+
+~> **Warning:** Once the cluster is bootstrapped, you must configure this using
+the [update scheduler configuration][update-scheduler-config] API. This
+option is only consulted during bootstrap.
+
+The structure matches the [Update Scheduler Config][update-scheduler-config] API
+endpoint, which you should consult for canonical documentation. However, the
+attributes names must be adapted to HCL syntax by using snake case
+representations rather than camel case.
+
+This example shows configuring spread scheduling and enabling preemption for all
+job-type schedulers.
+
+```hcl
+server {
+  default_scheduler_config {
+    scheduler_algorithm             = "spread"
+    memory_oversubscription_enabled = true
+    reject_job_registration         = false
+    pause_eval_broker               = false
+
+    preemption_config {
+      batch_scheduler_enabled    = true
+      system_scheduler_enabled   = true
+      service_scheduler_enabled  = true
+      sysbatch_scheduler_enabled = true
+    }
+  }
+}
+```
+
+## Client Heartbeats ((#client-heartbeats))
+
+~> This is an advanced topic. It is most beneficial to clusters over 1,000
+   nodes or with unreliable networks or nodes (eg some edge deployments).
+
+Nomad Clients periodically heartbeat to Nomad Servers to confirm they are
+operating as expected. Nomad Clients which do not heartbeat in the specified
+amount of time are considered `down` and their allocations are marked as `lost`
+or `disconnected` (if [`disconnect.lost_after`][disconnect.lost_after] is set)
+and replaced.
+
+The various heartbeat related parameters allow you to tune the following
+tradeoffs:
+
+- The longer the heartbeat period, the longer Nomad takes to replace a `down`
+  Client's workload.
+- The shorter the heartbeat period, the more likely transient network issues,
+  leader elections, and other temporary issues could cause a perfectly
+  functional Client and its workloads to be marked as `down` and the work
+  replaced.
+
+While Nomad Clients can connect to any Server, all heartbeats are forwarded to
+the leader for processing. Since this heartbeat processing consumes resources,
+Nomad adjusts the rate at which Clients heartbeat based on cluster size. The
+goal is to try to keep the resource cost of processing heartbeats constant
+regardless of cluster size.
+
+The base formula for determining how often a Client must heartbeat is:
+
+```
+<number of Clients> / <max_heartbeats_per_second>
+```
+
+Other factors modify this base TTL:
+
+- A random factor up to `2x` is added to the base TTL to prevent the
+  [thundering herd][herd] problem where a large number of clients attempt to
+  heartbeat at exactly the same time.
+- [`min_heartbeat_ttl`](#min_heartbeat_ttl) is used as the lower bound to
+  prevent small clusters from sending excessive heartbeats.
+- [`heartbeat_grace`](#heartbeat_grace) is the amount of _extra_ time the
+  leader will wait for a heartbeat beyond the base heartbeat.
+- After a leader election all Clients are given up to `failover_heartbeat_ttl`
+  to successfully heartbeat. This gives Clients time to discover a functioning
+  Server in case they were directly connected to a leader that crashed.
+
+For example, given the default values for heartbeat parameters, different sized
+clusters will use the following TTLs for the heartbeats. Note that the `Server TTL`
+simply adds the `heartbeat_grace` parameter to the TTL Clients are given.
+
+| Clients | Client TTL  | Server TTL  | Safe after elections |
+| ------- | ----------- | ----------- | -------------------- |
+| 10      | 10s - 20s   | 20s - 30s   | yes                  |
+| 100     | 10s - 20s   | 20s - 30s   | yes                  |
+| 1000    | 20s - 40s   | 30s - 50s   | yes                  |
+| 5000    | 100s - 200s | 110s - 210s | yes                  |
+| 10000   | 200s - 400s | 210s - 410s | NO                   |
+
+Regardless of size, all clients will have a Server TTL of
+`failover_heartbeat_ttl` after a leader election. It should always be larger
+than the maximum Client TTL for your cluster size in order to prevent marking
+live Clients as `down`.
+
+For clusters over 5000 Clients you should increase `failover_heartbeat_ttl`
+using the following formula:
+
+```
+(2 * (<number of Clients> / <max_heartbeats_per_second>)) + (10 * <min_heartbeat_ttl>)
+
+# For example with 6000 Clients:
+(2 * (6000 / 50)) + (10 * 10) = 340s (5m40s)
+```
+
+This ensures Clients have some additional time to failover even if they were
+told to heartbeat after the maximum interval.
+
+The actual value used should take into consideration how much tolerance your
+system has for a delay in noticing crashed Clients. For example a
+`failover_heartbeat_ttl` of 30 minutes may give even the slowest clients in the
+largest clusters ample time to heartbeat after an election. However if the
+election was due to a datacenter-wide failure affecting Clients, it will be 30
+minutes before Nomad recognizes that they are `down` and replaces their
+work.
+
+[encryption]: /nomad/tutorials/transport-security/security-gossip-encryption 'Nomad Encryption Overview'
+[server-join]: /nomad/docs/configuration/server_join 'Server Join'
+[update-scheduler-config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration 'Scheduler Config'
+[bootstrapping a cluster]: /nomad/docs/faq#bootstrapping
+[rfc4648]: https://tools.ietf.org/html/rfc4648#section-5
+[monitoring_nomad_progress]: /nomad/docs/operations/monitoring-nomad#progress
+[`nomad operator gossip keyring generate`]: /nomad/docs/commands/operator/gossip/keyring-generate
+[search]: /nomad/docs/configuration/search
+[encryption key]: /nomad/docs/operations/key-management
+[disconnect.lost_after]: /nomad/docs/job-specification/disconnect#lost_after
+[herd]: https://en.wikipedia.org/wiki/Thundering_herd_problem
+[wi]: /nomad/docs/concepts/workload-identity
+[Configure for multiple regions]: /nomad/tutorials/access-control/access-control-bootstrap#configure-for-multiple-regions
+[top_level_data_dir]: /nomad/docs/configuration#data_dir
+[JWKS URL]: /nomad/api-docs/operator/keyring#list-active-public-keys
diff --git a/content/nomad/v1.9.x/content/docs/configuration/server_join.mdx b/content/nomad/v1.9.x/content/docs/configuration/server_join.mdx
new file mode 100644
index 0000000000..f01165f4cb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/server_join.mdx
@@ -0,0 +1,303 @@
+---
+layout: docs
+page_title: server_join Block in Agent Configuration
+description: >-
+  Configure how Nomad agents discover and connect to Nomad servers in Amazon, Microsoft, and Google clouds as well as on-prem. Use the`server_join` block to configure the list of servers to join, retry interval, and max rejoin attempts.
+---
+
+# `server_join` Block in Agent Configuration
+
+<Placement
+  groups={[
+    ['server', 'server_join'],
+    ['client', 'server_join'],
+  ]}
+/>
+
+This page provides reference information for configuring how Nomad agents
+discover and connect to Nomad servers in Amazon, Microsoft, and Google
+clouds as well as on-prem. Use the`server_join` block to configure the list of
+servers to join, retry interval, and max rejoin attempts.
+
+```hcl
+server_join {
+  retry_join     = [ "1.1.1.1", "2.2.2.2" ]
+  retry_max      = 3
+  retry_interval = "15s"
+}
+```
+
+## `server_join` Parameters
+
+- `retry_join` `(array<string>: [])` - Specifies a list of Nomad server
+  addresses and [Cloud Auto-join](#cloud-auto-join) configurations that are
+  joined as cluster members. This is similar to [`start_join`](#start_join),
+  but join attempts are retried up to [retry_max](#retry_max) times.
+  Further, `retry_join` is available to both Nomad servers and clients, while
+  `start_join` is only defined for Nomad servers. This is useful for cases where
+  we know the address will become available eventually. Use `retry_join` with an
+  array as a replacement for `start_join`, **do not use both options**.
+
+  Server addresses must conform to the [server address format](#server-address-format).
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "2.2.2.2" ]
+  }
+  ```
+
+  Auto-join configurations must conform to the [Cloud Auto-join format](#cloud-auto-join).
+
+  Cloud-Auto join using `go-discover` to join an AWS EC2 cluster.
+
+  ```hcl
+  server_join {
+    retry_join = [ "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Cloud-Auto join using `go-netaddrs` to join a Hetzner cluster of servers
+  labeled with `nomad-server=true` using the `hcloud` CLI.
+
+  ```hcl
+  server_join {
+    retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+  }
+  ```
+
+  Server addresses and Cloud Auto-join configurations may be used together.
+  This is a mixed configuration containing a server address and Cloud Auto-join
+  configuration.
+
+  ```hcl
+  server_join {
+    retry_join = [ "1.1.1.1", "provider=aws tag_key=..." ]
+  }
+  ```
+
+  Refer to [server address format](#server-address-format) for more information
+  about expected server address formats and [Cloud Auto-join](#cloud-auto-join)
+  for more information on expected Cloud Auto-join formats.
+
+- `retry_interval` `(string: "30s")` - Specifies the time to wait between retry
+  join attempts.
+
+- `retry_max` `(int: 0)` - Specifies the maximum number of join attempts to be
+  made before exiting with a return code of 1. By default, this is set to 0
+  which is interpreted as infinite retries.
+
+- `start_join` `(array<string>: [])` - Specifies a list of server addresses to
+  join on startup. If Nomad is unable to join with any of the specified
+  addresses, agent startup will fail. See the
+  [server address format](#server-address-format) section for more information
+  on the format of the string. This field is defined only for Nomad servers and
+  will result in a configuration parse error if included in a client
+  configuration.
+
+## Server Address Format
+
+This section describes the acceptable syntax and format for describing the
+location of a Nomad server. There are many ways to reference a Nomad server,
+including directly by IP address and resolving through DNS.
+
+### Directly via IP Address
+
+It is possible to address another Nomad server using its IP address. This is
+done in the `ip:port` format, such as:
+
+```
+1.2.3.4:5678
+```
+
+If the IP address is an IPv6 address, it must be in URL format surrounded by
+brackets. For example:
+
+```
+[2001:db8::1]:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+1.2.3.4 => 1.2.3.4:4648
+```
+
+### Via Domains or DNS
+
+It is possible to address another Nomad server using its DNS address. This is
+done in the `address:port` format, such as:
+
+```
+nomad-01.company.local:5678
+```
+
+If the port option is omitted, it defaults to the Serf port, which is 4648
+unless configured otherwise:
+
+```
+nomad-01.company.local => nomad-01.company.local:4648
+```
+
+### Via the go-discover interface
+`retry_join` accepts a unified interface using the
+[go-discover](https://github.com/hashicorp/go-discover) library for doing
+automated cluster joining using cloud provider metadata. Refer to [Cloud
+Auto-join](#cloud-auto-join) for more information.
+
+```
+"provider=aws tag_key=..." => 1.2.3.4:4648
+```
+
+## Cloud Auto-join
+
+`retry_join`'s Cloud Auto-join allows Nomad to automatically discover cluster
+server addresses using cloud provider metadata. Cloud Auto-join allows both
+[go-discover](https://github.com/hashicorp/go-discover) and
+[go-netaddrs](https://github.com/hashicorp/go-netaddrs) formats.
+
+Configurations prefixed with `provider=` use `go-discover` whereas
+configurations prefixed with `exec=` use `go-netaddrs`. For cloud providers not
+supported by `go-discover`, use `go-netaddrs`.
+
+### `go-discover` Configurations
+
+`go-discover` configurations are prefixed with `provider=`.
+
+The following sections describe the Cloud Auto-join `retry_join` options that are specific
+to a subset of supported cloud providers. For information on all providers,
+refer to further
+documentation in [go-discover](https://github.com/hashicorp/go-discover).
+
+#### Amazon EC2
+
+This returns the first private IP address of all servers in the given
+region which have the given `tag_key` and `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=aws tag_key=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("aws" in this case).
+- `tag_key` (required) - the key of the tag to auto-join on.
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `region` (optional) - the AWS region to authenticate in.
+- `addr_type` (optional) - the type of address to discover: `private_v4`, `public_v4`, `public_v6`. Default is `private_v4`. (>= 1.0)
+- `access_key_id` (optional) - the AWS access key for authentication. Refer to
+  the following Authentication and Precedence section for details.
+- `secret_access_key` (optional) - the AWS secret access key for authentication.
+ Refer to the following Authentication and Precedence section for details.
+
+##### Authentication and Precedence
+
+- Static credentials `access_key_id=... secret_access_key=...`
+- Environment variables (`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`)
+- Shared credentials file (`~/.aws/credentials` or the path specified by `AWS_SHARED_CREDENTIALS_FILE`)
+- ECS task role metadata (container-specific).
+- EC2 instance role metadata.
+
+  The only required IAM permission is `ec2:DescribeInstances`, and it is
+  recommended that you make a dedicated key used only for auto-joining. If the
+  region is omitted it will be discovered through the local instance's [EC2
+  metadata
+  endpoint](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html).
+
+#### Microsoft Azure
+
+This returns the first private IP address of all servers in the given region
+which have the given `tag_key` and `tag_value` in the tenant and subscription, or in
+the given `resource_group` of a `vm_scale_set` for Virtual Machine Scale Sets.
+
+```json
+{
+  "retry_join": [
+    "provider=azure tag_name=... tag_value=... tenant_id=... client_id=... subscription_id=... secret_access_key=..."
+  ]
+}
+```
+
+- `provider` (required) - the name of the provider ("azure" in this case).
+- `tenant_id` (required) - the tenant to join machines in.
+- `client_id` (required) - the client to authenticate with.
+- `secret_access_key` (required) - the secret client key.
+
+Use these configuration parameters when using tags:
+
+- `tag_name` - the name of the tag to auto-join on.
+- `tag_value` - the value of the tag to auto-join on.
+
+Use these configuration parameters when using Virtual Machine Scale Sets (Consul 1.0.3 and later):
+
+- `resource_group` - the name of the resource group to filter on.
+- `vm_scale_set` - the name of the virtual machine scale set to filter on.
+
+  When using tags the only permission needed is the `ListAll` method for `NetworkInterfaces`. When using
+  Virtual Machine Scale Sets the only role action needed is `Microsoft.Compute/virtualMachineScaleSets/*/read`.
+
+#### Google Compute Engine
+
+This returns the first private IP address of all servers in the given
+project which have the given `tag_value`.
+
+```json
+{
+  "retry_join": ["provider=gce project_name=... tag_value=..."]
+}
+```
+
+- `provider` (required) - the name of the provider ("gce" in this case).
+- `tag_value` (required) - the value of the tag to auto-join on.
+- `project_name` (optional) - the name of the project to auto-join on. Discovered if not set.
+- `zone_pattern` (optional) - the list of zones can be restricted through an RE2 compatible regular expression. If omitted, servers in all zones are returned.
+- `credentials_file` (optional) - the credentials file for authentication. Refer
+ to the following Authentication and Precedence section for more information.
+
+##### Authentication and Precedence
+
+- Use credentials from `credentials_file`, if provided.
+- Use JSON file from `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
+- Use JSON file in a location known to the gcloud command-line tool.
+- On Windows, this is `%APPDATA%/gcloud/application_default_credentials.json`.
+- On other systems, `$HOME/.config/gcloud/application_default_credentials.json`.
+- On Google Compute Engine, use credentials from the metadata
+  server. In this final case any provided scopes are ignored.
+
+Discovery requires a [GCE Service
+Account](https://cloud.google.com/compute/docs/access/service-accounts).
+Credentials are searched using the following paths, in order of precedence.
+
+
+### `go-netaddrs` Configurations
+
+`go-netaddrs` configurations are prefixed with `exec=`.
+
+What follows the `exec=` prefix may be any executable program and its arguments.
+Commands run by `go-netaddrs` must return a list of space-delimited IPv4 or IPv6
+addresses and exit with code `0` on success and non-zero on failure.
+
+You can refer to the executable by its absolute file system path, or by
+the executable's name if it can be found on the Nomad agent's PATH. Refer to
+[executables in the current directory](https://pkg.go.dev/os/exec#hdr-Executables_in_the_current_directory)
+for more details on the lookup behavior.
+
+Example `go-netaddrs` configuration.
+
+```hcl
+server_join {
+  retry_join = [ "exec=hcloud server list -o noheader -o columns=ipv4 -l nomad-server=true | tr '\n' ' '" ]
+}
+```
+
+Here, `hcloud`'s newline-delimited output has been re-formatted as space-
+delimited by piping its output into `tr`.
+
+Output of an example `go-netaddrs` executable
+
+```
+"1.1.1.1 2.2.2.2"
+```
+
+Visit [go-netaddrs](https://github.com/hashicorp/go-netaddrs) for more
+information on go-netaddrs configuration.
diff --git a/content/nomad/v1.9.x/content/docs/configuration/telemetry.mdx b/content/nomad/v1.9.x/content/docs/configuration/telemetry.mdx
new file mode 100644
index 0000000000..62ea073c94
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/telemetry.mdx
@@ -0,0 +1,222 @@
+---
+layout: docs
+page_title: telemetry Block in Agent Configuration
+description: |-
+  Configure Nomad telemetry behavior in the `telemetry` block of a Nomad agent configuration. Configure Nomad's publication of metrics and telemetry to Statsite, StatsD, DataDog, Prometheus, and Apica (Circonus).
+---
+
+# `telemetry` Block in Agent Configuration
+
+<Placement groups={['telemetry']} />
+
+This page provides reference information for configuring Nomad telemetry
+behavior in the `telemetry` block of a Nomad agent configuration. Configure
+Nomad's publication of metrics and telemetry to [Statsite], [StatsD], [DataDog],
+[Prometheus], and [Apica (Circonus)][Apica].
+
+```hcl
+telemetry {
+  publish_allocation_metrics = true
+  publish_node_metrics       = true
+}
+```
+
+This section of the documentation only covers the configuration options for the
+`telemetry` block. To understand the architecture and metrics themselves,
+refer to the [Telemetry guide](/nomad/docs/operations/monitoring-nomad).
+
+## `telemetry` Parameters
+
+Due to the number of configurable parameters to the `telemetry` block,
+parameters on this page are grouped by the telemetry provider.
+
+### Common
+
+The following options are available on all telemetry configurations.
+
+- `in_memory_collection_interval` `(duration: 10s)` Configures the in-memory
+  sink collection interval. This sink is always configured and backs the JSON
+  metrics API endpoint. This option is particularly useful for debugging or
+  development purposes, where aggressive collection is required.
+
+- `in_memory_retention_period` `(duration: 1m)` Configures the in-memory sink
+  retention period. This sink is always configured and backs the JSON metrics
+  API endpoint. This option is particularly useful for debugging or development
+  purposes.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `collection_interval` `(duration: 1s)` - Specifies the time interval at which
+  the Nomad agent collects telemetry data. For metrics tools that scrape metrics
+  (for example, Prometheus), you should ensure this value is less than or equal
+  to the value of any scrape interval.
+
+- `use_node_name` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the name of the node, instead of the hostname. If set it will
+  override [disable_hostname](#disable_hostname) value.
+
+- `publish_allocation_metrics` `(bool: false)` - Specifies if Nomad should
+  publish runtime metrics of allocations.
+
+- `include_alloc_metadata_in_metrics` `(bool: false)` - This controls whether
+  allocation metadata is included in metric labels. Enabling this option may result in
+  high cardinality labels. You should also configure [allowed_metadata_keys_in_metrics](#allowed_metadata_keys_in_metrics).
+
+- `allowed_metadata_keys_in_metrics` `(list: [])` - This filters the metadata
+  keys to be included in the metric publishing. By default it does not filter
+  out any keys and thus include all metadata.
+
+- `publish_node_metrics` `(bool: false)` - Specifies if Nomad should publish
+  runtime metrics of nodes.
+
+- `filter_default` `(bool: true)` - This controls whether to allow metrics that
+  have not been specified by the filter. Defaults to true, which will allow all
+  metrics when no filters are provided. When set to false with no filters, no
+  metrics will be sent.
+
+- `prefix_filter` `(list: [])` - This is a list of filter rules to apply for
+  allowing/blocking metrics by prefix. A leading "<b>+</b>" will enable any
+  metrics with the given prefix, and a leading "<b>-</b>" will block them. If
+  there is overlap between two rules, the more specific rule will take
+  precedence. Blocking will take priority if the same prefix is listed multiple
+  times.
+
+```python
+['-nomad.raft', '+nomad.raft.apply', '-nomad.memberlist']
+```
+
+- `disable_dispatched_job_summary_metrics` `(bool: false)` - Specifies if Nomad
+  should ignore jobs dispatched from a parameterized job when publishing job
+  summary statistics. Since each job has a small memory overhead for tracking
+  summary statistics, it is sometimes desired to trade these statistics for
+  more memory when dispatching high volumes of jobs.
+
+- `disable_quota_utilization_metrics` `(bool: false)` - Specifies if Nomad
+  should publish metrics about quota utilization (a Nomad Enterprise feature).
+  Since each quota utilization check requires a relatively expensive check
+  against Nomad's state store, users with many namespaces and many quotas may
+  want to disable these metrics.
+
+- `disable_allocation_hook_metrics` `(bool: false)` - Specifies if the Nomad
+  client should publish metrics related to allocation and task hooks.
+
+### `statsite`
+
+These `telemetry` parameters apply to [Statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd`
+
+These `telemetry` parameters apply to [StatsD].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog`
+
+These `telemetry` parameters apply to [DataDog].
+
+- `datadog_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `datadog_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like "my_tag_name:my_tag_value".
+
+```hcl
+telemetry {
+  datadog_address = "dogstatsd.company.local:8125"
+  datadog_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus`
+
+These `telemetry` parameters apply to [Prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+### `circonus` (Apica)
+
+These `telemetry` parameters apply to [Apica], formerly Circonus. Apica acquired Circonus in 2024.
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad")` - Specifies a valid app name associated
+  with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTRAP check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  hostname:application name (e.g. "host123:nomad").
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to service:app (e.g. "service:nomad").
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTRAP check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g. a specific geographic location or
+  datacenter, dc:sfo).
+
+
+[Statsite]: https://github.com/armon/statsite
+[StatsD]: https://github.com/etsy/statsd
+[DataDog]: https://github.com/DataDog/datadog-agent
+[Prometheus]: https://prometheus.io
+[Apica]: https://www.apica.io/
diff --git a/content/nomad/v1.9.x/content/docs/configuration/tls.mdx b/content/nomad/v1.9.x/content/docs/configuration/tls.mdx
new file mode 100644
index 0000000000..2ecd4257bf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/tls.mdx
@@ -0,0 +1,134 @@
+---
+layout: docs
+page_title: tls Block in Agent Configuration
+description: |-
+  Configure secure communication in the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key files. Specify the TLS version. Require client certificates for all incoming HTTPS requests and the server name on all outgoing TLS connections.
+---
+
+# `tls` Block in Agent Configuration
+
+<Placement groups={['tls']} />
+
+This page provides reference information for configuring secure communication in
+the `tls` block of a Nomad agent configuration. Enable TLS on Raft traffic and
+RFC and HTTP endpoints. Add TLS cipher suites and paths to certificates and key
+files. Specify the TLS version. Require client certificates for all incoming
+HTTPS requests and verifying the server name on all outgoing TLS connections.
+
+Note that he Nomad documentation uses "TLS" to refer to this communication
+except when it is potentially ambiguous between TLS and mTLS.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+}
+```
+
+~> Incorrect configuration of the TLS configuration can result in failure to
+start the Nomad agent.
+
+This section of the documentation only covers the configuration options for the `tls` block. To understand how to setup the certificates themselves, refer to
+the [Enable TLS Encryption for Nomad Tutorial](/nomad/tutorials/transport-security/security-enable-tls).
+
+## `tls` Parameters
+
+- `ca_file` `(string: "")` - Specifies the path to the CA certificate to use for
+  Nomad's TLS communication.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate file used
+  for Nomad's TLS communication.
+
+- `key_file` `(string: "")` - Specifies the path to the key file to use for
+  Nomad's TLS communication.
+
+- `http` `(bool: false)` - Specifies if TLS should be enabled on the HTTP
+  endpoints on the Nomad agent, including the API. By default this is non-mutual
+  TLS. You can upgrade this to mTLS by setting
+  [`verify_https_client=true`](#verify_https_client), but this can complicate
+  using the Nomad UI by requiring mTLS in your browser or running a proxy in
+  front of the Nomad UI.
+
+- `rpc` `(bool: false)` - Toggle the option to enable mTLS on the RPC endpoints
+  and [Raft][raft] traffic. When this setting is activated, it establishes
+  protection both between Nomad servers and from the clients back to the
+  servers, ensuring mutual authentication. Setting `rpc=true` is required for
+  secure operation of Nomad.
+
+- `rpc_upgrade_mode` `(bool: false)` - This option should be used only when the
+  cluster is being upgraded to TLS, and removed after the migration is
+  complete. This allows the agent to accept both TLS and plaintext traffic.
+
+- `tls_cipher_suites` `(string: "")` - Specifies the TLS cipher suites that will
+  be used by the agent as a comma-separated string. Known insecure ciphers are
+  disabled (3DES and RC4). By default, an agent is configured to use
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
+  TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
+  TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and
+  TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
+
+  Nomad does not accept explicit ciphersuite configuration when for TLS 1.3
+  because the Go team has already designated a select set of ciphers that align
+  with the broadly-accepted Mozilla Security/Server Side TLS guidance for
+  [modern TLS configuration][modern-tls].
+
+~> **Warning:** the use of insecure cipher suites such as TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, and TLS_RSA_WITH_AES_128_CBC_SHA256 is now unsupported.
+
+- `tls_min_version` `(string: "tls12")`- Specifies the minimum supported version
+  of TLS. Accepted values are "tls10", "tls11", "tls12", "tls13".
+
+- `verify_https_client` `(bool: false)` - Specifies agents should require client
+  certificates for all incoming HTTPS requests, effectively upgrading
+  [`tls.http=true`](#http) to mTLS. The client certificates must be signed by
+  the same CA as Nomad. By default, `verify_https_client` is set to `false`,
+  which is safe so long as ACLs are enabled. This is recommended if you are
+  using the Nomad web UI to avoid the difficulty of distributing client certs to
+  browsers.
+
+- `verify_server_hostname` `(bool: false)` - Specifies if outgoing TLS
+  connections should verify the server's hostname.
+
+## `tls` Examples
+
+The following examples only show the `tls` blocks. Remember that the
+`tls` block is only valid in the placements listed above.
+
+### Enabling TLS
+
+This example shows enabling TLS configuration. This enables mTLS communication
+between all servers and clients using the default system CA bundle and
+certificates.
+
+```hcl
+tls {
+  http = true
+  rpc  = true
+
+  ca_file   = "/etc/certs/ca.crt"
+  cert_file = "/etc/certs/nomad.crt"
+  key_file  = "/etc/certs/nomad.key"
+}
+```
+
+### `tls` Configuration Reloads
+
+Nomad supports dynamically reloading both client and server TLS
+configuration. To reload an agent's TLS configuration, first update the TLS
+block in the agent's configuration file and then send the Nomad agent a `SIGHUP`
+signal. Note that this will only reload a subset of the configuration file,
+including the TLS configuration.
+
+The agent reloads all its network connections when there are changes to its
+TLS configuration during a config reload via `SIGHUP`. Any new connections
+established will use the updated configuration, and any outstanding old
+connections will be closed. This process works when upgrading to TLS,
+downgrading from it, as well as rolling certificates.
+
+[raft]: https://github.com/hashicorp/serf 'Serf by HashiCorp'
+[modern-tls]: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
diff --git a/content/nomad/v1.9.x/content/docs/configuration/ui.mdx b/content/nomad/v1.9.x/content/docs/configuration/ui.mdx
new file mode 100644
index 0000000000..303e257097
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/ui.mdx
@@ -0,0 +1,123 @@
+---
+layout: docs
+page_title: ui Block in Agent Configuration
+description: |-
+  Configure Nomad's web UI in the `ui` block of a Nomad agent configuration. Provide Vault and Consul links, add custom text to Nomad's UI, and define the HTTP Content Security Policy response header.
+---
+
+# `ui` Block in Agent Configuration
+
+<Placement groups={['ui']} />
+
+This page provides reference information for configuring Nomad's web UI in the
+`ui` block of a Nomad agent configuration. Provide Vault and Consul links,
+add custom text to display in Nomad's UI, and define the HTTP Content
+Security Policy response header.
+
+```hcl
+ui {
+  enabled =  true
+
+  content_security_policy {
+    connect_src     = ["*"]
+    default_src     = ["'none'"]
+    form_action     = ["'none'"]
+    frame_ancestors = ["'none'"]
+    img_src         = ["'self'","data:"]
+    script_src      = ["'self'"]
+    style_src       = ["'self'","'unsafe-inline'"]
+  }
+
+  consul {
+    ui_url = "https://consul.example.com:8501/ui"
+  }
+
+  vault {
+    ui_url = "https://vault.example.com:8200/ui"
+  }
+
+  label {
+    text             = "Staging Cluster"
+    background_color = "yellow"
+    text_color       = "#000000"
+  }
+}
+```
+
+A default `ui` block is automatically merged with all Nomad agent
+configurations. Note that the UI can be served from any Nomad agent,
+and the configuration is individual to each agent.
+## `ui` Parameters
+- `enabled` `(bool: true)` - Specifies whether the web UI is
+  enabled. If disabled, the `/ui/` path will return an empty web page.
+
+- `consul` <code>([Consul]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Consul web UI.
+
+- `vault` <code>([Vault]: nil)</code> - Configures integrations
+  between the Nomad web UI and the Vault web UI.
+
+- `label` <code>([Label]: nil)</code> - Configures a user-defined
+  label to display in the Nomad Web UI header.
+
+## `content_security_policy` Parameters
+
+The `content_security_policy` block configures the HTTP
+[Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP)
+header sent with the web UI response.
+
+- `connect_src` `(array<string>: ["*"])` - Specifies the valid sources for
+  `connect-src` in the Content Security Policy header.
+- `default_src` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `default-src` in the Content Security Policy header.
+- `form_action` `(array<string>: ["'none'"])` - Specifies the valid sources for
+  `form-action` in the Content Security Policy header.
+- `frame_ancestors` `(array<string>: ["'none'"])` - Specifies the valid sources
+  for `frame-ancestors` in the Content Security Policy header.
+- `img_src` `(array<string>: ["'self'", "data:"])` - Specifies the valid sources
+  for `img-src` in the Content Security Policy header.
+- `script_src` `(array<string>: ["'self'"])` - Specifies the valid sources for
+  `script-src` in the Content Security Policy header.
+- `style_src` `(array<string>: ["'self'","'unsafe-inline'"])` - Specifies the
+  valid sources for `style-src` in the Content Security Policy header.
+
+## `consul` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Consul
+  web UI (for example: `https://consul.example.com:8501/ui`. This URL
+  is used to build links from the Nomad web UI to a Consul web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`consul.address`]; the `consul.address` is the URL used
+  by the Nomad to communicate with Consul, whereas the
+  `ui.consul.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `vault` Parameters
+
+- `ui_url` `(string: "")` - Specifies the full base URL to a Vault
+  web UI (for example: `https://vault.example.com:8200/ui`. This URL
+  is used to build links from the Nomad web UI to a Vault web
+  UI. Note that this URL will not typically be the same one used for
+  the agent's [`vault.address`]; the `vault.address` is the URL used
+  by the Nomad to communicate with Vault, whereas the
+  `ui.vault.ui_url` is the URL you'll visit in your browser. If
+  this field is omitted, this integration will be disabled.
+
+## `label` Parameters
+
+- `text` `(string: "")` - Specifies the text of the label that will be
+  displayed in the header of the Web UI.
+- `background_color` `(string: "")` - The background color of the label to
+  be displayed. The Web UI will default to a black background. HEX values
+  may be used.
+- `text_color` `(string: "")` - The text color of the label to be displayed.
+  The Web UI will default to white text. HEX values may be used.
+
+
+
+[web UI]: /nomad/tutorials/web-ui
+[Consul]: /nomad/docs/configuration/ui#consul-parameters
+[Vault]: /nomad/docs/configuration/ui#vault-parameters
+[Label]: /nomad/docs/configuration/ui#label-parameters
+[`consul.address`]: /nomad/docs/configuration/consul#address
+[`vault.address`]: /nomad/docs/configuration/vault#address
diff --git a/content/nomad/v1.9.x/content/docs/configuration/vault.mdx b/content/nomad/v1.9.x/content/docs/configuration/vault.mdx
new file mode 100644
index 0000000000..4a768ea48e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/configuration/vault.mdx
@@ -0,0 +1,352 @@
+---
+layout: docs
+page_title: vault Block in Agent Configuration
+description: |-
+  Configure Nomad server and client integration with HashiCorp Vault in the `vault` block of a Nomad agent configuration. Configure cluster name and the role for creating tokens. For Nomad clients, configure Vault's address, namespace, and certificate or TLS authentication. Specify the JWT authentication path. For Nomad servers, configure the server's default workload identity, which includes workload identity recipients, workload TTL, and key-value pairs for additional identity claims.
+
+---
+
+# `vault` Block in Agent Configuration
+
+<Placement groups={['vault']} />
+
+This page provides reference information for configuring Nomad server and client
+integration with [HashiCorp Vault][vault] in the `vault` block of a Nomad agent
+configuration. Configure cluster name and the role for creating tokens. For
+Nomad clients, configure Vault's address, namespace, and certificate or TLS
+authentication. Specify the JWT authentication path. For Nomad
+servers, configure the server's default workload identity, which includes
+workload identity recipients, workload TTL, and key-value pairs for additional
+identity claims.
+
+When configured, job tasks can use [workload identities][workload_id] to receive
+Vault ACL tokens automatically.
+
+Alternatively, Nomad servers may be configured with a high-privileged Vault
+token that is used to derive fine-grained tokens for tasks. Refer to
+[Token-Based Authentication](#token-based-authentication) for configuration
+details. However, we strongly recommend using workload identities since
+token-based authentication is deprecated.
+
+Refer to the [Nomad and Vault Integration][nomad-vault] page for more
+information about the Vault integration.
+
+```hcl
+vault {
+  enabled = true
+
+  default_identity {
+    aud = ["vault.io"]
+    ttl = "1h"
+
+    extra_claims {
+      unique_id = "${job.region}:${job.namespace}:${job.id}"
+    }
+  }
+}
+```
+
+In Nomad Enterprise, you may specify multiple `vault` blocks to configure access
+to multiple Vault clusters. Each Vault cluster must have a different value for
+the [`name`](#name) field.
+
+## `vault` Parameters
+
+Some parameters are expected to be specified in the configuration file of Nomad
+agents running as clients, servers, or in all agents. Parameters are safely
+ignored if placed in a configuration file where they are not expected to be
+defined.
+
+The placement also depends on the authentication strategy used. This section
+describes the parameter organization for workload identity authentication.
+Refer to the [Token-based Authentication](#token-based-authentication) section
+if using Vault tokens directly.
+
+### Parameters for Nomad Clients and Servers
+
+These parameters should be defined in the configuration file of all Nomad
+agents.
+
+- `name` `(string: "default")` <EnterpriseAlert inline/> - Specifies a name for
+  the cluster so it can be referred to by job submitters in the job
+  specification's [`vault.cluster`][] field. In Nomad Community Edition, only
+  the `"default"` cluster will be used, so this field should be omitted.
+
+- `enabled` `(bool: false)` - Specifies if the Vault integration should be
+  activated.
+
+- `create_from_role` `(string: "")` - Specifies the role to create tokens from.
+
+  When using workload identities this field defines the role used to derive
+  task tokens when the job does not define a value for
+  [`vault.role`][jobspec_vault_role]. If empty, the default Vault cluster role
+  is used.
+
+  For token-based authentication, the Nomad servers derive tokens
+  using this role. The token given to Nomad does not have to be created from
+  this role but must have `update` capability on
+  `auth/token/create/<create_from_role>` path in Vault. If this value is unset
+  and the token is created from a role, the value is defaulted to the role the
+  token is from.
+
+  -> **Note:** This used to be a server-only field, but it is client-only when
+  using workload identities. It should be set in both while transitioning from
+  token-based authentication to workload identities.
+
+### Parameters for Nomad Clients
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`client.enabled`] set to `true`.
+
+- `namespace` `(string: "")` - Specifies the [Vault namespace](/vault/docs/enterprise/namespaces)
+  used by the Vault integration. If non-empty, this namespace will be used on
+  all Vault API calls.
+
+- `address` - `(string: "https://vault.service.consul:8200")` - Specifies the
+  address to the Vault server. This must include the protocol, host/ip, and port
+  given in the format `protocol://host:port`. If your Vault installation is
+  behind a load balancer, this should be the address of the load balancer.
+
+- `jwt_auth_backend_path` - `(string: "jwt-nomad")` - Specifies the mount
+  [path][vault_auth_enable_path] of the JWT authentication method to be used to
+  login with workload identity JWTs.
+
+- `ca_file` `(string: "")` - Specifies an optional path to the CA
+  certificate used for Vault communication. If unspecified, this will fallback
+  to the default system CA bundle, which varies by OS and version.
+
+- `ca_path` `(string: "")` - Specifies an optional path to a folder
+  containing CA certificates to be used for Vault communication. If unspecified,
+  this will fallback to the default system CA bundle, which varies by OS and
+  version.
+
+- `cert_file` `(string: "")` - Specifies the path to the certificate used for
+  Vault communication. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `key_file` `(string: "")` - Specifies the path to the private key used for
+  Vault communication. If this is set then you need to also set
+  `cert_file`. This must be set if
+  [tls_require_and_verify_client_cert](/vault/docs/configuration/listener/tcp#tls_require_and_verify_client_cert)
+  is enabled in Vault.
+
+- `tls_server_name` `(string: "")` - Specifies an optional string used to set
+  the SNI host when connecting to Vault via TLS.
+
+- `tls_skip_verify` `(bool: false)` - Specifies if SSL peer validation should be
+  enforced.
+
+  !> It is **strongly discouraged** to disable SSL verification. Instead, you
+  should install a custom CA bundle and validate against it. Disabling SSL
+  verification can allow an attacker to easily compromise your cluster.
+
+### Parameters for Nomad Servers
+
+These parameters should only be defined in the configuration file of Nomad
+agents with [`server.enabled`] set to `true`.
+
+- `default_identity` <code>([Identity](#default_identity-parameters): nil)</code> -
+  Specifies the default workload identity configuration to use when a task with
+  a `vault` block does not specify an [`identity`][jobspec_identity] block
+  named `vault_<name>`, where `<name>` matches the value of this `vault` block
+  [`name`](#name) parameter. Setting a default identity causes the value of
+  `allow_unauthenticated` to be ignored.
+
+### Deprecated Parameters
+
+These parameters are used by the deprecated token-based authentication flow and
+will be removed in a future release.
+
+- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to
+  the Nomad server should be required to provide their own Vault token, proving
+  they have access to the policies listed in the job. This option should be
+  disabled in an untrusted environment.
+
+- `task_token_ttl` `(string: "72h")` - Specifies the TTL of created tokens when
+  using a root token. This is specified using a label suffix like "30s" or "1h".
+
+- `token` `(string: "")` - Specifies the parent Vault token to use to derive
+  child tokens for jobs requesting tokens. Only required on Nomad servers.
+  Nomad client agents use the allocation's token when contacting Vault.
+  Refer to the [Vault Integration Guide](/nomad/docs/integrations/vault-integration)
+  for how to generate an appropriate token in Vault.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  starting the agent instead.
+
+### `default_identity` Parameters
+
+- `aud` `(array<string>: [])` - List of valid recipients for this workload
+  identity. This value must match the [`bound_audiences`][vault_bound_aud]
+  configuration in the Vault JWT auth method. It is recommended to provide one,
+  and only one, audience to minimize where the identity may be used.
+
+- `env` `(bool: false)` - If true the workload identity will be available in
+  the task's `NOMAD_TOKEN_vault` environment variable.
+
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_vault.jwt`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+
+- `ttl` `(string: "")` - Specifies for how long the workload identity should be
+  considered as valid before expiring.
+
+- `extra_claims` `(map[string]string: optional)` - A set of key-value pairs that
+  will be provided as extra identity claims for workloads. You can use the keys
+  as [user claims in Vault role configurations][vault-jwt-user-claim]. The
+  values are interpolated. For example, if you include the extra claim
+  `unique_id = "${job.region}:${job.namespace}:${job.id}"`, you could set the
+  user claim field to `/extra_claims/unique_id` to map that identifier to an
+  entity alias. The available attributes for interpolation are:
+
+  - `${job.region}` - The region where the job is running.
+  - `${job.namespace}` - The job's namespace.
+  - `${job.id}` - The job's ID.
+  - `${job.node_pool}` - The node pool where the allocation is running.
+  - `${group.name}` - The task group name of the task using Vault.
+  - `${alloc.id}` - The allocation's ID.
+  - `${task.name}` - The name of the task using Vault.
+  - `${node.id}` - The ID of the node where the allocation is running.
+  - `${node.datacenter}` - The datacenter of the node where the allocation is running.
+  - `${node.pool}` - The node pool of the node where the allocation is running.
+  - `${node.class` - The class of the node where the allocation is running.
+  - `${vault.cluster}` - The Vault cluster name.
+  - `${vault.namespace}` - The Vault namespace.
+  - `${vault.role}` - The Vault role.
+
+### Token-Based Authentication
+
+~> **Warning:** The token-based authentication flow is deprecated and will be
+  removed in a future release. It is highly recommended to migrate and use the
+  workload identity flow instead.
+
+When using token-based authentication the `vault` block, define parameters as in
+the following examples.
+
+#### Parameters for Nomad Clients and Servers
+
+- [`address`](#address)
+- [`ca_file`](#ca_file)
+- [`ca_path`](#ca_path)
+- [`cert_file`](#cert_file)
+- [`enabled`](#enabled)
+- [`key_file`](#key_file)
+- [`name`](#name)
+- [`namespace`](#namespace)
+- [`tls_server_name`](#tls_server_name)
+- [`tls_skip_verify`](#tls_skip_verify)
+
+#### Parameters for Nomad Servers
+
+- [`allow_unauthenticated`](#allow_unauthenticated)
+- [`create_from_role`](#create_from_role)
+- [`token`](#token)
+- [`task_token_ttl`](#task_token_ttl)
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Nomad Server
+
+This example shows a Vault configuration for a Nomad server using the workload
+identity authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled = true
+
+  # Only needed in servers when transitioning from the token-based flow to
+  # workload identities.
+  create_from_role = "nomad-cluster"
+
+  # Provide a default workload identity configuration so jobs don't need to
+  # specify one.
+  default_identity {
+    aud  = ["vault.io"]
+    env  = false
+    file = true
+    ttl  = "1h"
+  }
+}
+```
+
+This example shows a Vault configuration for a Nomad server using the
+deprecated token-based authentication flow.
+
+```hcl
+server {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+
+  # Address to communicate with Vault. The following is the default address if
+  # unspecified.
+  address = "https://vault.service.consul:8200"
+
+  # Embedding the token in the configuration is discouraged. Instead users
+  # should set the VAULT_TOKEN environment variable when starting the Nomad
+  # agent
+  token = "debecfdc-9ed7-ea22-c6ee-948f22cdd474"
+
+  # Setting the create_from_role option causes Nomad to create tokens for tasks
+  # via the provided role. This allows the role to manage what policies are
+  # allowed and disallowed for use by tasks.
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Nomad Client
+
+This example shows a Vault configuration for a Nomad client.
+
+```hcl
+client {
+  enabled = true
+  # ...
+}
+
+vault {
+  enabled   = true
+  address   = "https://vault.service.consul:8200"
+  ca_path   = "/etc/certs/ca"
+  cert_file = "/var/certs/vault.crt"
+  key_file  = "/var/certs/vault.key"
+}
+```
+
+## `vault` Configuration Reloads
+
+The Vault configuration can be reloaded on servers. This can be useful if a new
+token needs to be given to the servers without having to restart them. A reload
+can be accomplished by sending the process a `SIGHUP` signal.
+
+[`client.enabled`]: /nomad/docs/configuration/client#enabled
+[`server.enabled`]: /nomad/docs/configuration/server#enabled
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[jobspec_vault_role]: /nomad/docs/job-specification/vault#role
+[jobspec_identity]: /nomad/docs/job-specification/identity
+[nomad-vault]: /nomad/docs/integrations/vault-integration 'Nomad Vault Integration'
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[vault]: https://www.vaultproject.io/ 'Vault by HashiCorp'
+[vault_bound_aud]: /vault/api-docs/auth/jwt#bound_audiences
+[vault_auth_enable_path]: /vault/docs/commands/auth/enable#path
+[workload_id]: /nomad/docs/concepts/workload-identity
+[vault-jwt-user-claim]: /vault/api-docs/auth/jwt#user_claim
diff --git a/content/nomad/v1.9.x/content/docs/drivers/docker.mdx b/content/nomad/v1.9.x/content/docs/drivers/docker.mdx
new file mode 100644
index 0000000000..8505ac12b0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/docker.mdx
@@ -0,0 +1,1282 @@
+---
+layout: docs
+page_title: Docker task driver
+description: Nomad's Docker task driver lets you run Docker-based tasks in your jobs. Learn how to configure job tasks, authenticate against a private repository, use insecure registries, and configure Docker networking. Modify the Docker task driver plugin configuration. Learn about CPU, memory, filesystem IO, and security resource isolation as well as how Nomad handles dangling containers.
+---
+
+# Docker task driver
+
+Name: `docker`
+
+The `docker` driver provides a first-class Docker workflow on Nomad. The Docker
+driver handles downloading containers, mapping ports, and starting, watching,
+and cleaning up after containers.
+
+-> **Note:** If you are using Docker Desktop for Windows or MacOS, please check
+[our FAQ][faq-win-mac].
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "docker"
+
+  config {
+    image = "redis:7"
+    labels {
+      group = "webservice-cache"
+    }
+  }
+}
+```
+
+The `docker` driver supports the following configuration in the job spec. Only
+`image` is required.
+
+- `image` - The Docker image to run. The image may include a tag or custom URL
+  and should include `https://` if required. By default it will be fetched from
+  Docker Hub. If the tag is omitted or equal to `latest` the driver will always
+  try to pull the image. If the image to be pulled exists in a registry that
+  requires authentication credentials must be provided to Nomad. Please see the
+  [Authentication section](#authentication).
+
+  ```hcl
+  config {
+    image = "https://hub.docker.internal/redis:7"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long Nomad
+  will wait before cancelling an in-progress pull of the Docker image as specified
+  in `image`. Defaults to `"5m"`.
+
+- `args` - (Optional) A list of arguments to the optional `command`. If no
+  `command` is specified, the arguments are passed directly to the container.
+  References to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task. For example:
+
+  ```hcl
+  config {
+    args = [
+      "-bind", "${NOMAD_PORT_http}",
+      "${nomad.datacenter}",
+      "${MY_ENV}",
+      "${meta.foo}",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Provide authentication for a private registry (see below).
+
+- `auth_soft_fail` `(bool: false)` - Don't fail the task on an auth failure.
+  Attempt to continue without auth. If the Nomad client configuration has an
+  [`auth.helper`](#plugin_auth_helper) block, the helper will be tried for
+  all images, including public images. If you mix private and public images,
+  you will need to include `auth_soft_fail=true` in every job using a public
+  image.
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "my-command"
+  }
+  ```
+
+- `container_exists_attempts` - (Optional) A number of attempts to be made to
+  purge a container if during task creation Nomad encounters an existing one in
+  non-running state for the same task. Defaults to `5`.
+
+- `dns_search_domains` - (Optional) A list of DNS search domains for
+  the container to use. If you are using bridge networking mode with a
+  `network` block in the task group, you must set all DNS options in
+  the `network.dns` block instead.
+
+- `dns_options` - (Optional) A list of DNS options for the container
+  to use. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `dns_servers` - (Optional) A list of DNS servers for the container
+  to use (e.g. ["8.8.8.8", "8.8.4.4"]). Requires Docker v1.10 or
+  greater. If you are using bridge networking mode with a `network`
+  block in the task group, you must set all DNS options in the
+  `network.dns` block instead.
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`. This option may not work as expected in `bridge` network mode
+  when there is more than one task within the same group. Refer to the
+  [upgrade guide][upgrade_guide_extra_hosts] for more information.
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull most recent image
+  instead of using existing local image. Should be set to `true` if repository tags
+  are mutable. If image's tag is `latest` or omitted, the image will always be pulled
+  regardless of this setting.
+
+- `group_add` - (Optional) A list of supplementary groups to be applied
+  to the container user.
+
+- `healthchecks` - (Optional) A configuration block for controlling how the
+  docker driver manages HEALTHCHECK directives built into the container. Set
+  `healthchecks.disable` to disable any built-in healthcheck.
+
+  ```hcl
+  config {
+    healthchecks {
+      disable = true
+    }
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `init` - (Optional) `true` or `false` (default). Enable init (tini) system when
+   launching your container. When enabled, an init process will be used as the PID1
+   in the container. Specifying an init process ensures the usual responsibilities
+   of an init system, such as reaping zombie processes, are performed inside the
+   created container.
+
+   The default init process used is the first `docker-init` executable found in the
+   system path of the Docker daemon process. This `docker-init` binary, included in
+   the default installation, is backed by [tini][tini].
+
+- `interactive` - (Optional) `true` or `false` (default). Keep STDIN open on
+  the container.
+
+- `isolation` - (Optional) Specifies [Windows isolation][] mode: `"hyperv"` or
+  `"process"`. Defaults to `"hyperv"`.
+
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+   <Warning>
+
+   If you are creating your job specification in JSON, you must use wrap the map in an
+   array. Do not use a bare map as you would in HCL.
+
+   ```json
+   config {
+     "sysctl": [
+      {
+       "net.core.somaxconn": "16384",
+       "net.ipv4.tw_reuse": "1"
+      }
+    ]
+   }
+   ```
+
+   </Warning>
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers on start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `privileged` - (Optional) `true` or `false` (default). Privileged mode gives
+  the container access to devices on the host. Note that this also requires the
+  nomad agent and docker daemon to be configured to allow privileged
+  containers.
+
+- `ipc_mode` - (Optional) The IPC mode to be used for the container. The default
+  is `none` for a private IPC namespace. Other values are `host` for sharing
+  the host IPC namespace or the name or id of an existing container. Note that
+  it is not possible to refer to Docker containers started by Nomad since their
+  names are not known in advance. Note that setting this option also requires the
+  Nomad agent to be configured to allow privileged containers.
+
+- `ipv4_address` - (Optional) The IPv4 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `ipv6_address` - (Optional) The IPv6 address to be used for the container when
+  using user defined networks. Requires Docker 1.13 or greater.
+
+- `labels` - (Optional) A key-value map of labels to set to the containers on
+  start.
+
+  ```hcl
+  config {
+    labels {
+      foo = "bar"
+      zip = "zap"
+    }
+  }
+  ```
+
+  A more verbose syntax must be used to specify labels with keys that require
+  quoting. For example DataDog's autodiscovery mechanism looks for labels with
+  dots in the key which must be quoted:
+
+  ```hcl
+  config {
+    labels = [
+      {
+        "com.datadoghq.ad.check_names"  =  "[\"openmetrics\"]"
+        "com.datadoghq.ad.init_configs" = "[{}]"
+      }
+    ]
+  }
+  ```
+
+- `load` - (Optional) Load an image from a `tar` archive file instead of from a
+  remote repository. Equivalent to the `docker load -i <filename>` command. If
+  you're using an `artifact` block to fetch the archive file, you'll need to
+  ensure that Nomad keeps the archive intact after download.
+
+  ```hcl
+  artifact {
+    source = "http://path.to/redis.tar"
+    options {
+      archive = false
+    }
+  }
+  config {
+    load = "redis.tar"
+    image = "redis"
+  }
+  ```
+
+- `logging` - (Optional) A key-value map of Docker logging options.
+  Defaults to `json-file` with log rotation (`max-file=2` and `max-size=2m`).
+
+  ```hcl
+  config {
+    logging {
+      type = "fluentd"
+      config {
+        fluentd-address = "localhost:24224"
+        tag = "your_tag"
+      }
+    }
+  }
+  ```
+
+- `mac_address` - (Optional) The MAC address for the container to use (e.g.
+  "02:68:b3:29:da:98").
+
+- `memory_hard_limit` - (Optional) The maximum allowable amount of memory used
+  (megabytes) by the container. If set, the [`memory`](/nomad/docs/job-specification/resources#memory)
+  parameter of the task resource configuration becomes a soft limit passed to the
+  docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory),
+  and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory)
+  hard limit. When the host is under memory pressure, the behavior of soft limit
+  activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt).
+
+- `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a
+  container to be discovered by an alternate name by any other container within
+  the scope of a particular network. Network-scoped alias is supported only for
+  containers in user defined networks
+
+  ```hcl
+  config {
+    network_mode = "user-network"
+    network_aliases = [
+      "${NOMAD_TASK_NAME}",
+      "${NOMAD_TASK_NAME}-${NOMAD_ALLOC_INDEX}"
+    ]
+  }
+  ```
+
+- `network_mode` - (Optional) The network mode to be used for the container. In
+  order to support userspace networking plugins in Docker 1.9 this accepts any
+  value. The default is `bridge` for all operating systems but Windows, which
+  defaults to `nat`. Other networking modes may not work without additional
+  configuration on the host (which is outside the scope of Nomad). Valid values
+  pre-docker 1.9 are `default`, `bridge`, `host`, `none`, or `container:name`.
+
+  The default `network_mode` for tasks that use group networking in [`bridge`]
+  mode will be `container:<name>`, where the name is the container name of the
+  parent container used to share network namespaces between tasks. If you set
+  the group [`network.mode`][] to `"bridge"` you should not set this Docker
+  `network_mode` config, otherwise the container will be unable to reach other
+  containers in the task group. This will also prevent [Connect]-enabled tasks
+  from reaching the Envoy sidecar proxy. You must also set any DNS options in
+  the `network.dns` block and not in the task configuration.
+
+  If you are in the process of migrating from the default Docker network to
+  group-wide bridge networking, you may encounter issues preventing your
+  containers from reaching networks outside of the bridge interface on systems with
+  firewalld enabled. This behavior is often caused by the CNI plugin not registering the group
+  network as trusted and can be resolved as described in the [network block] documentation.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+  See below for more details.
+
+- `ports` - (Optional) A list of port labels to map into the container (see below).
+
+- `port_map` - (Optional) _Deprecated_ A key-value map of port labels (see below).
+
+- `security_opt` - (Optional) A list of string flags to pass directly to
+  [`--security-opt`](https://docs.docker.com/engine/reference/run/#security-configuration).
+  For example:
+
+  ```hcl
+  config {
+    security_opt = [
+      "credentialspec=file://gmsaUser.json",
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) The size (bytes) of /dev/shm for the container.
+
+- `storage_opt` - (Optional) A key-value map of storage options set to the containers on start.
+  This overrides the [host dockerd configuration](https://docs.docker.com/engine/reference/commandline/dockerd/#options-per-storage-driver).
+  For example:
+
+  ```hcl
+  config {
+    storage_opt = {
+      size = "40G"
+    }
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `uts_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the UTS namespace with the host. Note that this also requires the Nomad agent
+  to be configured to allow privileged containers.
+
+- `userns_mode` - (Optional) `host` or not set (default). Set to `host` to use
+  the host's user namespace (effectively disabling user namespacing) when user
+  namespace remapping is enabled on the docker daemon. This field has no
+  effect if the docker daemon does not have user namespace remapping enabled.
+
+- `volumes` - (Optional) A list of `host_path:container_path` strings to bind
+  host paths to container paths. Mounting host paths outside of the [allocation
+  working directory] is prevented by default and limits volumes to directories
+  that exist inside the allocation working directory. You can allow mounting
+  host paths outside of the [allocation working directory] on individual clients
+  by setting the `docker.volumes.enabled` option to `true` in the
+  [client's configuration](#client-requirements). We recommend using
+  [`mount`](#mount) if you wish to have more control over volume definitions.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use absolute paths to mount arbitrary paths on the host
+      "/path/on/host:/path/in/container",
+
+      # Use relative paths to rebind paths already in the allocation dir
+      "relative/to/task:/also/in/container"
+    ]
+  }
+  ```
+
+- `volume_driver` - (Optional) The name of the volume driver used to mount
+  volumes. Must be used along with `volumes`. If `volume_driver` is omitted,
+  then relative paths will be mounted from inside the allocation dir. If a
+  `"local"` or other driver is used, then they may be named volumes instead.
+  If `docker.volumes.enabled` is false then volume drivers and paths outside the
+  allocation directory are disallowed.
+
+  ```hcl
+  config {
+    volumes = [
+      # Use named volume created outside nomad.
+      "name-of-the-volume:/path/in/container"
+    ]
+    # Name of the Docker Volume Driver used by the container
+    volume_driver = "pxd"
+  }
+  ```
+
+- `work_dir` - (Optional) The working directory inside the container.
+
+- `mount` - _Since 1.0.1_ (Optional) Specify a
+  [mount](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported. May be specified multiple times.
+
+  ```hcl
+  config {
+    # sample volume mount
+    mount {
+      type = "volume"
+      target = "/path/in/container"
+      source = "name-of-volume"
+      readonly = false
+      volume_options {
+        no_copy = false
+        labels {
+          foo = "bar"
+        }
+        driver_config {
+          name = "pxd"
+          options {
+            foo = "bar"
+          }
+        }
+      }
+    }
+
+    # sample bind mount
+    mount {
+      type = "bind"
+      target = "/path/in/container"
+      source = "/path/in/host"
+      readonly = false
+      bind_options {
+        propagation = "rshared"
+      }
+    }
+
+    # sample tmpfs mount
+    mount {
+      type = "tmpfs"
+      target = "/path/in/container"
+      readonly = false
+      tmpfs_options {
+        size = 100000 # size in bytes
+      }
+    }
+  }
+  ```
+
+- `mounts` - (_deprecated_: Replaced by `mount` in 1.0.1) (Optional) A list of
+  [mounts](https://docs.docker.com/engine/reference/commandline/service_create/#add-bind-mounts-volumes-or-memory-filesystems)
+  to be mounted into the container. Volume, bind, and tmpfs type mounts are supported.
+
+  ```hcl
+  config {
+    mounts = [
+      # sample volume mount
+      {
+        type = "volume"
+        target = "/path/in/container"
+        source = "name-of-volume"
+        readonly = false
+        volume_options = {
+          no_copy = false
+          labels = {
+            foo = "bar"
+          }
+          driver_config = {
+            name = "pxd"
+            options = {
+              foo = "bar"
+            }
+          }
+        }
+      },
+      # sample bind mount
+      {
+        type = "bind"
+        target = "/path/in/container"
+        source = "/path/in/host"
+        readonly = false
+        bind_options = {
+          propagation = "rshared"
+        }
+      },
+      # sample tmpfs mount
+      {
+        type = "tmpfs"
+        target = "/path/in/container"
+        readonly = false
+        tmpfs_options = {
+          size = 100000 # size in bytes
+        }
+      }
+    ]
+  }
+  ```
+
+- `devices` - (Optional) A list of
+  [devices](https://docs.docker.com/engine/reference/commandline/run/#add-host-device-to-container-device)
+  to be exposed the container. `host_path` is the only required field. By default, the container will be able to
+  `read`, `write` and `mknod` these devices. Use the optional `cgroup_permissions` field to restrict permissions.
+
+  ```hcl
+  config {
+    devices = [
+      {
+        host_path = "/dev/sda1"
+        container_path = "/dev/xvdc"
+        cgroup_permissions = "r"
+      },
+      {
+        host_path = "/dev/sda2"
+        container_path = "/dev/xvdd"
+      }
+    ]
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-add`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. Note that `"all"` is not permitted here if the `allow_caps`
+  field in the driver configuration doesn't also allow all capabilities. For
+  example:
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass
+  directly to [`--cap-drop`][]. Effective capabilities (computed from `cap_add`
+  and `cap_drop`) must be a subset of the allowed capabilities configured with
+  the [`allow_caps`][allow_caps] plugin option key in the client node's
+  configuration. For example:
+
+```hcl
+config {
+  cap_drop = ["mknod"]
+}
+```
+
+- `cpu_hard_limit` - (Optional) `true` or `false` (default). Use hard CPU
+  limiting instead of soft limiting. By default this is `false` which means
+  soft limiting is used and containers are able to burst above their CPU limit
+  when there is idle capacity.
+
+- `cpu_cfs_period` - (Optional) An integer value that specifies the duration in microseconds of the period
+  during which the CPU usage quota is measured. The default is 100000 (0.1 second) and the maximum allowed
+  value is 1000000 (1 second). See [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/resource_management_guide/sec-cpu#sect-cfs)
+  for more details.
+
+- `advertise_ipv6_address` - (Optional) `true` or `false` (default). Use the container's
+  IPv6 address (GlobalIPv6Address in Docker) when registering services and checks.
+  See [IPv6 Docker containers](/nomad/docs/job-specification/service#ipv6-docker-containers) for details.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount
+  the container's filesystem as read only.
+
+- `runtime` - (Optional) A string representing a configured runtime to pass to docker.
+  This is equivalent to the `--runtime` argument in the docker CLI
+  For example, to use gVisor:
+
+  ```hcl
+  config {
+    # gVisor runtime is runsc
+    runtime = "runsc"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+Additionally, the docker driver supports customization of the container's user through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+### Container Name
+
+Nomad creates a container after pulling an image. Containers are named
+`{taskName}-{allocId}`. This is necessary in order to place more than one
+container from the same task on a host (e.g. with count > 1). This also means
+that each container's name is unique across the cluster.
+
+This is not configurable.
+
+### Authentication
+
+If you want to pull from a private repo (for example on dockerhub or quay.io),
+you will need to specify credentials in your job via:
+
+- the `auth` option in the task config.
+
+- by storing explicit repository credentials or by specifying Docker
+  `credHelpers` in a file and setting the auth [config](#plugin_auth_file)
+  value on the client in the plugin options.
+
+- by specifying an auth [helper](#plugin_auth_helper) on the client in the
+  plugin options.
+
+The `auth` object supports the following keys:
+
+- `username` - (Optional) The account username.
+
+- `password` - (Optional) The account password.
+
+- `email` - (Optional) The account email.
+
+- `server_address` - (Optional) The server domain/IP without the protocol.
+  Docker Hub is used by default.
+
+Example task-config:
+
+```hcl
+task "example" {
+  driver = "docker"
+
+  config {
+    image = "secret/service"
+
+    auth {
+      username = "dockerhub_user"
+      password = "dockerhub_password"
+    }
+  }
+}
+```
+
+Example docker-config, using two helper scripts in `$PATH`,
+"docker-credential-ecr-login" and "docker-credential-vault":
+
+```json
+{
+  "auths": {
+    "internal.repo": {
+      "auth": "`echo -n '<username>:<password>' | base64 -w0`"
+    }
+  },
+  "credHelpers": {
+    "<XYZ>.dkr.ecr.<region>.amazonaws.com": "ecr-login"
+  },
+  "credsStore": "secretservice"
+}
+```
+
+Example agent configuration, using a helper script
+"docker-credential-ecr-login" in `$PATH`
+
+```hcl
+client {
+  enabled = true
+}
+
+plugin "docker" {
+  config {
+    auth {
+      # Nomad will prepend "docker-credential-" to the helper value and call
+      # that script name.
+      helper = "ecr-login"
+    }
+  }
+}
+```
+
+!> **Be Careful!** At this time these credentials are stored in Nomad in plain
+text. Secrets management will be added in a later release.
+
+## Insecure Registries
+
+In order to pull images from a registry without TLS, you must configure the
+Docker daemon's `insecure-registries` flag. No additional Nomad client
+configuration is required. You should only allow insecure registries for
+registries running locally on the client or when the communication to the
+registry is otherwise encrypted. List the `insecure-registries` flag in the
+`dockerd` [configuration file](https://docs.docker.com/config/daemon/).
+
+```json
+{
+  "insecure-registries": ["example.local:5000"]
+}
+```
+
+## Networking
+
+Docker supports a variety of networking configurations, including using host
+interfaces, SDNs, etc. Nomad uses `bridged` networking by default, like Docker.
+
+You can specify other networking options, including custom networking plugins
+in Docker 1.9. **You may need to perform additional configuration on the host
+in order to make these work.** This additional configuration is outside the
+scope of Nomad.
+
+### Allocating Ports
+
+You can allocate ports to your task using the port syntax described on the
+[networking page](/nomad/docs/job-specification/network). Here is a recap:
+
+```hcl
+group {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+  task "example" {
+    driver = "docker"
+    config {
+      ports = ["http", "https"]
+    }
+  }
+}
+```
+
+### Forwarding and Exposing Ports
+
+A Docker container typically specifies which port a service will listen on by
+specifying the `EXPOSE` directive in the `Dockerfile`.
+
+Because dynamic ports will not match the ports exposed in your Dockerfile,
+Nomad will automatically expose any ports specified in the `ports` field.
+
+These ports will be identified via environment variables. For example:
+
+```hcl
+group {
+  network {
+    port "http" {}
+  }
+  task "api" {
+    driver = "docker"
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your api task for `http`, `23332` will be
+automatically exposed and forwarded to your container, and the driver will set
+an environment variable `NOMAD_PORT_http` with the value `23332` that you can
+read inside your container.
+
+This provides an easy way to use the `host` networking option for better
+performance.
+
+### Using the Port Map
+
+If you prefer to use the traditional port-mapping method, you can specify the
+the `to` field in the port configuration. It looks like this:
+
+```hcl
+group "example" {
+  network {
+    port "redis" { to = 6379 }
+  }
+  task "example" {
+    driver = "docker"
+
+    config {
+      image = "redis"
+      ports = ["redis"]
+    }
+  }
+}
+```
+
+If Nomad allocates port `23332` to your allocation, the Docker driver will
+automatically setup the port mapping from `23332` on the host to `6379` in your
+container, so it will just work.
+
+Note that by default this only works with `bridged` networking mode. It may
+also work with custom networking plugins which implement the same API for
+expose and port forwarding.
+
+#### Deprecated `port_map` Syntax
+
+Up until Nomad 0.12, ports could be specified in a task's resource block and set using the docker
+`port_map` field. As more features have been added to the group network resource allocation, task based
+network resources are deprecated. With it the `port_map` field is also deprecated and can only be used
+with task network resources.
+
+Users should migrate their jobs to define ports in the group network block and specified which ports
+a task maps with the `ports` field.
+
+### Advertising Container IPs
+
+When using network plugins like `weave` that assign containers a routable IP
+address, that address will automatically be used in any `service`
+advertisements for the task. You may override what address is advertised by
+using the `address_mode` parameter on a `service`. See
+[service](/nomad/docs/job-specification/service) for details.
+
+### Networking Protocols
+
+The Docker driver configures ports on both the `tcp` and `udp` protocols.
+
+This is not configurable.
+
+### Other Networking Modes
+
+Some networking modes like `container` or `none` will require coordination
+outside of Nomad. First-class support for these options may be improved later
+through Nomad plugins or dynamic job configuration.
+
+## Capabilities
+
+The `docker` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | true              |
+| filesystem isolation | image             |
+| network isolation    | host, group, task |
+| volume mounting      | all               |
+
+## Client Requirements
+
+Nomad requires Docker to be installed and running on the host alongside the
+Nomad agent.
+
+By default Nomad communicates with the Docker daemon using the daemon's Unix
+socket. Nomad will need to be able to read/write to this socket. If you do not
+run Nomad as root, make sure you add the Nomad user to the Docker group so
+Nomad can communicate with the Docker daemon.
+
+For example, on Ubuntu you can use the `usermod` command to add the `nomad`
+user to the `docker` group so you can run Nomad without root:
+
+```shell-session
+$ sudo usermod -G docker -a nomad
+```
+
+Nomad clients manage a cpuset cgroup for each task to reserve or share CPU
+[cores][]. In order for Nomad to be compatible with Docker's own cgroups
+management, it must write to cgroups owned by Docker, which requires running as
+root. If Nomad is not running as root, CPU isolation and NUMA-aware scheduling
+will not function correctly for workloads with `resources.cores`, including
+workloads using task drivers other than `docker` on the same host.
+
+For the best performance and security features you should use recent versions
+of the Linux Kernel and Docker daemon.
+
+If you would like to change any of the options related to the `docker` driver
+on a Nomad client, you can modify them with the [plugin block][plugin-block]
+syntax. Below is an example of a configuration (many of the values are the
+default). See the next section for more information on the options.
+
+```hcl
+plugin "docker" {
+  config {
+    endpoint = "unix:///var/run/docker.sock"
+
+    auth {
+      config = "/etc/docker-auth.json"
+      helper = "ecr-login"
+    }
+
+    tls {
+      cert = "/etc/nomad/nomad.pub"
+      key  = "/etc/nomad/nomad.pem"
+      ca   = "/etc/nomad/nomad.cert"
+    }
+
+    extra_labels = ["job_name", "job_id", "task_group_name", "task_name", "namespace", "node_name", "node_id"]
+
+    gc {
+      image       = true
+      image_delay = "3m"
+      container   = true
+
+      dangling_containers {
+        enabled        = true
+        dry_run        = false
+        period         = "5m"
+        creation_grace = "5m"
+      }
+    }
+
+    volumes {
+      enabled      = true
+      selinuxlabel = "z"
+    }
+
+    allow_privileged = false
+    allow_caps       = ["chown", "net_raw"]
+  }
+}
+```
+
+## Plugin Options
+
+- `endpoint` - If using a non-standard socket, HTTP or another location, or if
+  TLS is being used, docker.endpoint must be set. If unset, Nomad will attempt
+  to instantiate a Docker client using the `DOCKER_HOST` environment variable and
+  then fall back to the default listen address for the given operating system.
+  Defaults to `unix:///var/run/docker.sock` on Unix platforms and
+  `npipe:////./pipe/docker_engine` for Windows.
+
+- `allow_privileged` - Defaults to `false`. Changing this to true will allow
+  containers to use privileged mode, which gives the containers full access to
+  the host's devices. Note that you must set a similar setting on the Docker
+  daemon for this to work.
+
+- `pull_activity_timeout` - Defaults to `2m`. If Nomad receives no communication
+  from the Docker engine during an image pull within this timeframe, Nomad will
+  time out the request that initiated the pull command. (Minimum of `1m`)
+
+- `pids_limit` - Defaults to unlimited (`0`). An integer value that specifies
+  the pid limit for all the Docker containers running on that Nomad client. You
+  can override this limit by setting [`pids_limit`] in your task config. If
+  this value is greater than `0`, your task `pids_limit` must be less than or
+  equal to the value defined here.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is the same list of capabilities allowed by [docker by
+  default][docker_caps] (without [`NET_RAW`][no_net_raw]). Allows the operator
+  to control which capabilities can be obtained by tasks using
+  [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options. Supports the value
+  `"all"` as a shortcut for allow-listing all capabilities supported by the
+  operating system. Note that due to a limitation in Docker, tasks running as
+  non-root users cannot expand the capabilities set beyond the default. They can
+  only have their capabilities reduced.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `allow_runtimes` - defaults to `["runc", "nvidia"]` - A list of the allowed
+  docker runtimes a task may use.
+
+- `auth` block:
+
+  - `config`<a id="plugin_auth_file"></a> - Allows an operator to specify a
+    JSON file which is in the dockercfg format containing authentication
+    information for a private registry, from either (in order) `auths`,
+    `credsStore` or `credHelpers`.
+
+  - `helper`<a id="plugin_auth_helper"></a> - Allows an operator to specify a
+    [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+    like script on `$PATH` to lookup authentication information from external
+    sources. The script's name must begin with `docker-credential-` and this
+    option should include only the basename of the script, not the path.
+
+    If you set an auth helper, it will be tried for all images, including
+    public images. If you mix private and public images, you will need to
+    include [`auth_soft_fail=true`] in every job using a public image.
+
+- `tls` block:
+
+  - `cert` - Path to the server's certificate file (`.pem`). Specify this
+    along with `key` and `ca` to use a TLS client to connect to the docker
+    daemon. `endpoint` must also be specified or this setting will be ignored.
+
+  - `key` - Path to the client's private key (`.pem`). Specify this along with
+    `cert` and `ca` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+  - `ca` - Path to the server's CA file (`.pem`). Specify this along with
+    `cert` and `key` to use a TLS client to connect to the docker daemon.
+    `endpoint` must also be specified or this setting will be ignored.
+
+- `disable_log_collection` - Defaults to `false`. Setting this to true will
+  disable Nomad logs collection of Docker tasks. If you don't rely on nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable nomad log collection overhead.
+
+- `extra_labels` - Extra labels to add to Docker containers.
+  Available options are `job_name`, `job_id`, `task_group_name`, `task_name`,
+  `namespace`, `node_name`, `node_id`. Globs are supported (e.g. `task*`)
+
+- `logging` block:
+
+  - `type` - Defaults to `"json-file"`. Specifies the logging driver docker
+    should use for all containers Nomad starts. Note that for older versions
+    of Docker, only `json-file` file or `journald` will allow Nomad to read
+    the driver's logs via the Docker API, and this will prevent commands such
+    as `nomad alloc logs` from functioning.
+
+  - `config` - Defaults to `{ max-file = "2", max-size = "2m" }`. This option
+    can also be used to pass further
+    [configuration](https://docs.docker.com/config/containers/logging/configure/)
+    to the logging driver.
+
+- `gc` block:
+
+  - `image` - Defaults to `true`. Changing this to `false` will prevent Nomad
+    from removing images from stopped tasks.
+
+  - `image_delay` - A time duration, as [defined
+    here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`.
+    The delay controls how long Nomad will wait between an image being unused
+    and deleting it. If a task is received that uses the same image within
+    the delay, the image will be reused. If an image is referenced by more than
+    one tag, `image_delay` may not work correctly.
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits. Under a name conflict,
+    Nomad may still remove the dead container.
+
+  - `dangling_containers` block for controlling dangling container detection
+    and cleanup:
+
+    - `enabled` - Defaults to `true`. Enables dangling container handling.
+
+    - `dry_run` - Defaults to `false`. Only log dangling containers without
+      cleaning them up.
+
+    - `period` - Defaults to `"5m"`. A time duration that controls interval
+      between Nomad scans for dangling containers.
+
+    - `creation_grace` - Defaults to `"5m"`. Grace period after a container is
+      created during which the GC ignores it. Only used to prevent the GC from
+      removing newly created containers before they are registered with the
+      GC. Should not need adjusting higher but may be adjusted lower to GC
+      more aggressively.
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `false`. Allows tasks to bind host paths
+    (`volumes`) inside their container and use volume drivers
+    (`volume_driver`). Binding relative paths is always allowed and will be
+    resolved relative to the allocation's directory.
+
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `docker.volumes.enabled` set to false, the labels will still be applied to
+    the standard binds in the container.
+
+- `infra_image` - This is the Docker image to use when creating the parent
+  container necessary when sharing network namespaces between tasks. Defaults to
+  `registry.k8s.io/pause-<goarch>:3.3`. The image will only be pulled from the
+  container registry if its tag is `latest` or the image doesn't yet exist
+  locally.
+
+- `infra_image_pull_timeout` - A time duration that controls how long Nomad will
+  wait before cancelling an in-progress pull of the Docker image as specified in
+  `infra_image`. Defaults to `"5m"`.
+
+- `windows_allow_insecure_container_admin` - Indicates that on windows, docker
+  checks the `task.user` field or, if unset, the container image manifest after
+  pulling the container, to see if it's running as `ContainerAdmin`. If so, exits
+  with an error unless the task config has `privileged=true`. Defaults to `false`.
+
+## Client Configuration
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block]
+documentation for more information.
+
+The `docker` driver has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `docker.endpoint` - If using a non-standard socket, HTTP or another location,
+  or if TLS is being used, `docker.endpoint` must be set. If unset, Nomad will
+  attempt to instantiate a Docker client using the `DOCKER_HOST` environment
+  variable and then fall back to the default listen address for the given
+  operating system. Defaults to `unix:///var/run/docker.sock` on Unix platforms
+  and `npipe:////./pipe/docker_engine` for Windows.
+
+- `docker.auth.config` <a id="auth_file"></a>- Allows an operator to specify a
+  JSON file which is in the dockercfg format containing authentication
+  information for a private registry, from either (in order) `auths`,
+  `credsStore` or `credHelpers`.
+
+- `docker.auth.helper` <a id="auth_helper"></a>- Allows an operator to specify a
+  [credsStore](https://docs.docker.com/engine/reference/commandline/login/#credential-helper-protocol)
+  -like script on \$PATH to lookup authentication information from external
+  sources. The script's name must begin with `docker-credential-` and this
+  option should include only the basename of the script, not the path.
+
+- `docker.tls.cert` - Path to the server's certificate file (`.pem`). Specify
+  this along with `docker.tls.key` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.key` - Path to the client's private key (`.pem`). Specify this
+  along with `docker.tls.cert` and `docker.tls.ca` to use a TLS client to
+  connect to the docker daemon. `docker.endpoint` must also be specified or this
+  setting will be ignored.
+
+- `docker.tls.ca` - Path to the server's CA file (`.pem`). Specify this along
+  with `docker.tls.cert` and `docker.tls.key` to use a TLS client to connect to
+  the docker daemon. `docker.endpoint` must also be specified or this setting
+  will be ignored.
+
+- `docker.cleanup.image` Defaults to `true`. Changing this to `false` will
+  prevent Nomad from removing images from stopped tasks.
+
+- `docker.cleanup.image.delay` A time duration, as [defined
+  here](https://golang.org/pkg/time/#ParseDuration), that defaults to `3m`. The
+  delay controls how long Nomad will wait between an image being unused and
+  deleting it. If a tasks is received that uses the same image within the delay,
+  the image will be reused.
+
+- `docker.volumes.enabled`: Defaults to `false`. Allows tasks to bind host paths
+  (`volumes`) inside their container and use volume drivers (`volume_driver`).
+  Binding relative paths is always allowed and will be resolved relative to the
+  allocation's directory.
+
+- `docker.volumes.selinuxlabel`: Allows the operator to set a SELinux label to
+  the allocation and task local bind-mounts to containers. If used with
+  `docker.volumes.enabled` set to false, the labels will still be applied to the
+  standard binds in the container.
+
+- `docker.privileged.enabled` Defaults to `false`. Changing this to `true` will
+  allow containers to use `privileged` mode, which gives the containers full
+  access to the host's devices. Note that you must set a similar setting on the
+  Docker daemon for this to work.
+
+- `docker.caps.allowlist`: A list of allowed Linux capabilities. Defaults to
+  `"CHOWN,DAC_OVERRIDE,FSETID,FOWNER,MKNOD,NET_RAW,SETGID,SETUID,SETFCAP, SETPCAP,NET_BIND_SERVICE,SYS_CHROOT,KILL,AUDIT_WRITE"`, which is the list of
+  capabilities allowed by docker by default, as [defined
+  here](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities).
+  Allows the operator to control which capabilities can be obtained by tasks
+  using `cap_add` and `cap_drop` options. Supports the value `"ALL"` as a
+  shortcut for allowlisting all capabilities.
+
+- `docker.cleanup.container`: Defaults to `true`. This option can be used to
+  disable Nomad from removing a container when the task exits. Under a name
+  conflict, Nomad may still remove the dead container.
+
+- `docker.nvidia_runtime`: Defaults to `nvidia`. This option allows operators to select the runtime that should be used in order to expose Nvidia GPUs to the container.
+
+Note: When testing or using the `-dev` flag you can use `DOCKER_HOST`,
+`DOCKER_TLS_VERIFY`, and `DOCKER_CERT_PATH` to customize Nomad's behavior. If
+`docker.endpoint` is set Nomad will **only** read client configuration from the
+config file.
+
+An example is given below:
+
+```hcl
+client {
+  options {
+    "docker.cleanup.image" = "false"
+  }
+}
+```
+
+## Client Attributes
+
+The `docker` driver will set the following client attributes:
+
+- `driver.docker` - This will be set to "1", indicating the driver is
+  available.
+
+- `driver.docker.bridge_ip` - The IP of the Docker bridge network if one
+  exists.
+
+- `driver.docker.version` - This will be set to version of the docker server.
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Require docker version higher than 1.2.
+  constraint {
+    attribute = "${attr.driver.docker.version}"
+    operator  = ">"
+    version   = "1.2"
+  }
+}
+```
+
+## Resource Isolation
+
+### CPU
+
+Nomad limits containers' CPU based on CPU shares. CPU shares allow containers
+to burst past their CPU limits. CPU limits will only be imposed when there is
+contention for resources. When the host is under load your process may be
+throttled to stabilize QoS depending on how many shares it has. You can see how
+many CPU shares are available to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env].
+1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads
+on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+### Memory
+
+Nomad limits containers' memory usage based on total virtual memory. This means
+that containers scheduled by Nomad cannot use swap. This is to ensure that a
+swappy process does not degrade performance for other workloads on the same
+host.
+
+Since memory is not an elastic resource, you will need to make sure your
+container does not exceed the amount of memory allocated to it, or it will be
+terminated or crash when it tries to malloc. A process can inspect its memory
+limit by reading [`NOMAD_MEMORY_LIMIT`][runtime_env], but will need to track its own memory
+usage. Memory limit is expressed in megabytes so 1024 = 1 GB.
+
+### IO
+
+Nomad's Docker integration does not currently provide QoS around network or
+filesystem IO. These will be added in a later release.
+
+### Security
+
+Docker provides resource isolation by way of
+[cgroups and namespaces](https://docs.docker.com/introduction/understanding-docker/#the-underlying-technology).
+Containers essentially have a virtual file system all to themselves. If you
+need a higher degree of isolation between processes for security or other
+reasons, it is recommended to use full virtualization like
+[QEMU](/nomad/docs/drivers/qemu).
+
+## Caveats
+
+### Dangling Containers
+
+Nomad has a detector and a reaper for dangling Docker containers,
+containers that Nomad starts yet does not manage or track. Though rare, they
+lead to unexpectedly running services, potentially with stale versions.
+
+When Docker daemon becomes unavailable as Nomad starts a task, it is possible
+for Docker to successfully start the container but return a 500 error code from
+the API call. In such cases, Nomad retries and eventually aims to kill such
+containers. However, if the Docker Engine remains unhealthy, subsequent retries
+and stop attempts may still fail, and the started container becomes a dangling
+container that Nomad no longer manages.
+
+The newly added reaper periodically scans for such containers. It only targets
+containers with a `com.hashicorp.nomad.allocation_id` label, or match Nomad's
+conventions for naming and bind-mounts (i.e. `/alloc`, `/secrets`, `local`).
+Containers that don't match Nomad container patterns are left untouched.
+
+Operators can run the reaper in a dry-run mode, where it only logs dangling
+container ids without killing them, or disable it by setting the
+`gc.dangling_containers` config block.
+
+### Docker for Windows
+
+Docker for Windows only supports running Windows containers. Because Docker for
+Windows is relatively new and rapidly evolving you may want to consult the
+[list of relevant issues on GitHub][winissues].
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[winissues]: https://github.com/hashicorp/nomad/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Fdriver%2Fdocker+label%3Atheme%2Fplatform-windows
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[`auth_soft_fail=true`]: #auth_soft_fail
+[cap_add]: /nomad/docs/drivers/docker#cap_add
+[cap_drop]: /nomad/docs/drivers/docker#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[upgrade_guide_extra_hosts]: /nomad/docs/upgrade/upgrade-specific#docker-driver
+[tini]: https://github.com/krallin/tini
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[allow_caps]: /nomad/docs/drivers/docker#allow_caps
+[Connect]: /nomad/docs/job-specification/connect
+[`bridge`]: /nomad/docs/job-specification/network#bridge
+[network block]: /nomad/docs/job-specification/network#bridge-mode
+[`network.mode`]: /nomad/docs/job-specification/network#mode
+[`pids_limit`]: /nomad/docs/drivers/docker#pids_limit
+[Windows isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[`--cap-add`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`--cap-drop`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cores]: /nomad/docs/job-specification/resources#cores
diff --git a/content/nomad/v1.9.x/content/docs/drivers/exec.mdx b/content/nomad/v1.9.x/content/docs/drivers/exec.mdx
new file mode 100644
index 0000000000..05e4653134
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/exec.mdx
@@ -0,0 +1,312 @@
+---
+layout: docs
+page_title: Isolated Fork/Exec task driver
+description: Nomad's Isolated Fork/Exec task driver lets you run binaries using OS isolation primitives. Learn how to use the Isolated Fork/Exec task driver in your jobs. Configure the command to execute with command arguments, namespace isolation, and Linux capabilities. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes. Learn how the Isolated Fork/Exec task driver affects resource isolation, chroot, and CPU resources.
+---
+
+# Isolated Fork/Exec task driver
+
+Name: `exec`
+
+The `exec` driver is used to execute a particular command for a task.
+However, unlike [`raw_exec`](/nomad/docs/drivers/raw_exec) it uses the underlying isolation
+primitives of the operating system to limit the task's access to resources. While
+simple, since the `exec` driver can invoke any command, it can be used to call
+scripts or other wrappers which provide higher level features.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute and within the task's
+  [chroot](#chroot) or in a [host volume][] mounted with a
+  [`volume_mount`][volume_mount] block. The driver will make the binary
+  executable and will search, in order:
+
+  - The `local` directory with the task directory.
+  - The task directory.
+  - Any mounts, in the order listed in the job specification.
+  - The `usr/local/bin`, `usr/bin` and `bin` directories inside the task
+    directory.
+
+  If executing a binary that is downloaded
+  from an [`artifact`](/nomad/docs/job-specification/artifact), the path can be
+  relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+To run a binary present on the Node:
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute.
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an
+[`artifact`](/nomad/docs/job-specification/artifact):
+
+```hcl
+task "example" {
+  driver = "exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | chroot         |
+| network isolation    | host, group    |
+| volume mounting      | all            |
+
+## Client Requirements
+
+The `exec` driver can only be run when on Linux and running Nomad as root.
+`exec` is limited to this configuration because currently isolation of resources
+is only guaranteed on Linux. Further, the host must have cgroups mounted properly
+in order for the driver to work.
+
+If you are receiving the error:
+
+```
+* Constraint "missing drivers" filtered <> nodes
+```
+
+and using the exec driver, check to ensure that you are running Nomad as root.
+This also applies for running Nomad in -dev mode.
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `no_pivot_root` `(bool: optional)` - Defaults to `false`. When `true`, the driver uses `chroot`
+  for file system isolation without `pivot_root`. This is useful for systems
+  where the root is on a ramdisk.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+## Client Attributes
+
+The `exec` driver will set the following client attributes:
+
+- `driver.exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will use cgroups, and a chroot to isolate the resources of a
+process and as such the Nomad agent must be run as root. Some Linux
+distributions do not boot with all required cgroups enabled by default. You
+can see which cgroups are enabled by reading `/proc/cgroups`, and verifying
+that all the following cgroups are enabled:
+
+```
+$ awk '{print $1 " " $4}' /proc/cgroups
+#subsys_name enabled
+cpuset 1
+cpu 1
+cpuacct 1
+blkio 1
+memory 1
+devices 1
+freezer 1
+net_cls 1
+perf_event 1
+net_prio 1
+hugetlb 1
+pids 1
+```
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+Chroot changes the root directory of the current process and all its child processes. Nomad uses a chroot environment to implement file system isolation.
+
+Nomad populates the chroot environment with data in the following host machine directories:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+Nomad populates the task's chroot environment by linking or copying the data from the host into the chroot. Note that this can take considerable disk space.
+The client manages garbage collection locally, which mitigates any issue this may create.
+
+@include 'chroot-limitations.mdx'
+
+Configure the chroot environment list through the agent client's
+[`chroot_env` attribute](/nomad/docs/configuration/client#chroot_env).
+
+### CPU
+
+Nomad limits exec tasks' CPU based on CPU shares. CPU shares allow containers to
+burst past their CPU limits. CPU limits will only be imposed when there is contention
+for resources. When the host is under load your process may be throttled to stabilize
+QoS depending on how many shares it has. You can see how many CPU shares are available
+to your process by reading [`NOMAD_CPU_LIMIT`][runtime_env]. 1000 shares are approximately equal to 1 GHz.
+
+Please keep the implications of CPU shares in mind when you load test workloads on Nomad.
+
+If resources [`cores`][cores] is set, the task is given an isolated reserved set of
+CPU cores to make use of. The total set of cores the task may run on is the private
+set combined with the variable set of unreserved cores. The private set of CPU cores
+is available to your process by reading [`NOMAD_CPU_CORES`][runtime_env].
+
+[default_pid_mode]: /nomad/docs/drivers/exec#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/exec#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/exec#cap_add
+[cap_drop]: /nomad/docs/drivers/exec#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/exec#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[host volume]: /nomad/docs/configuration/client#host_volume-block
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[cores]: /nomad/docs/job-specification/resources#cores
+[runtime_env]: /nomad/docs/runtime/environment#job-related-variables
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
diff --git a/content/nomad/v1.9.x/content/docs/drivers/index.mdx b/content/nomad/v1.9.x/content/docs/drivers/index.mdx
new file mode 100644
index 0000000000..dc300a85f2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/index.mdx
@@ -0,0 +1,11 @@
+---
+layout: docs
+page_title: Nomad task drivers
+description: Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, installation, usage, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+---
+
+# Nomad task drivers
+
+Nomad's bundled task drivers integrate with the host OS to run job tasks in isolation. Review conceptual, installation, usage, and reference information for the Docker, Isolated Fork/Exec, Java, QEMU, and Raw Fork/Exec task drivers.
+
+@include 'task-driver-intro.mdx'
diff --git a/content/nomad/v1.9.x/content/docs/drivers/java.mdx b/content/nomad/v1.9.x/content/docs/drivers/java.mdx
new file mode 100644
index 0000000000..c815bd67e9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/java.mdx
@@ -0,0 +1,269 @@
+---
+layout: docs
+page_title: Java task driver
+description: Nomad's Java task driver lets you run JAR files in your workloads. Learn how to configure a job task that uses the Java task driver. Configure paths, JAR args, JVM options, namespace isolation, work directory, and Linux capabilities. Review the Java task driver capabilities, plugin options, client requirements, and client attributes such as Java version and virtual machine. Learn how the Java task driver affects resource isolation and chroot.
+---
+
+# Java task driver
+
+Name: `java`
+
+The `java` driver is used to execute Java applications packaged into a Java Jar
+file. The driver requires the Jar file to be accessible from the Nomad
+client via the [`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/example.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+}
+```
+
+The `java` driver supports the following configuration in the job spec:
+
+- `class` - (Optional) The name of the class to run. If `jar_path` is specified
+  and the manifest specifies a main class, this is optional. If shipping classes
+  rather than a Jar, please specify the class to run and the `class_path`.
+
+- `class_path` - (Optional) The `class_path` specifies the class path used by
+  Java to lookup classes and Jars.
+
+- `jar_path` - (Optional) The path to the downloaded Jar. In most cases this will just be
+  the name of the Jar. However, if the supplied artifact is an archive that
+  contains the Jar in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.jar`).
+
+- `args` - (Optional) A list of arguments to the Jar's main method. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `jvm_options` - (Optional) A list of JVM options to be passed while invoking
+  java. These options are passed without being validated in any way by Nomad.
+
+- `pid_mode` - (Optional) Set to `"private"` to enable PID namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_pid_mode`][default_pid_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `ipc_mode` - (Optional) Set to `"private"` to enable IPC namespace isolation for
+  this task, or `"host"` to disable isolation. If left unset, the behavior is
+  determined from the [`default_ipc_mode`][default_ipc_mode] in plugin configuration.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `cap_add` - (Optional) A list of Linux capabilities to enable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a
+  subset of the allowed capabilities configured with [`allow_caps`][allow_caps].
+  Note that `"all"` is not permitted here if the `allow_caps` field in the
+  driver configuration doesn't also allow all capabilities.
+
+
+```hcl
+config {
+  cap_add = ["net_raw", "sys_time"]
+}
+```
+
+- `cap_drop` - (Optional) A list of Linux capabilities to disable for the task.
+  Effective capabilities (computed from `cap_add` and `cap_drop`) must be a subset
+  of the allowed capabilities configured with [`allow_caps`][allow_caps].
+
+```hcl
+config {
+  cap_drop = ["all"]
+  cap_add  = ["chown", "sys_chroot", "mknod"]
+}
+```
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This path must be
+  absolute and within the task's [chroot](#chroot) or in a [host volume][] mounted
+  with a [`volume_mount`][volume_mount] block. This will also change the working
+  directory when using `nomad alloc exec`.
+
+## Examples
+
+A simple config block to run a Java Jar:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    jar_path    = "local/hello.jar"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/hello.jar"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+A simple config block to run a Java class:
+
+```hcl
+task "web" {
+  driver = "java"
+
+  config {
+    class       = "Hello"
+    class_path  = "${NOMAD_TASK_DIR}"
+    jvm_options = ["-Xmx2048m", "-Xms256m"]
+  }
+
+  # Specifying an artifact is required with the "java" driver. This is the
+  # mechanism to ship the Jar to be run.
+  artifact {
+    source = "https://internal.file.server/Hello.class"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `java` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation                |
+| -------------------- | ----------------------------- |
+| `nomad alloc signal` | false                         |
+| `nomad alloc exec`   | false                         |
+| filesystem isolation | none, chroot (only for linux) |
+| network isolation    | host, group                   |
+| volume mounting      | none, all (only for linux)    |
+
+## Plugin Options
+
+- `default_pid_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable PID namespace isolation for tasks by default, or `"host"` to
+  disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will
+be able to access sensitive process information like environment variables.
+
+- `default_ipc_mode` `(string: optional)` - Defaults to `"private"`. Set to
+  `"private"` to enable IPC namespace isolation for tasks by default,
+  or `"host"` to disable isolation.
+
+!> **Warning:** If set to `"host"`, other processes running as the same user will be
+able to make use of IPC features, like sending unexpected POSIX signals.
+
+- `allow_caps` - A list of allowed Linux capabilities. Defaults to
+
+```hcl
+["audit_write", "chown", "dac_override", "fowner", "fsetid", "kill", "mknod",
+ "net_bind_service", "setfcap", "setgid", "setpcap", "setuid", "sys_chroot"]
+```
+
+  which is modeled after the capabilities allowed by [docker by default][docker_caps]
+  (without [`NET_RAW`][no_net_raw]). Allows the operator to control which capabilities
+  can be obtained by tasks using [`cap_add`][cap_add] and [`cap_drop`][cap_drop] options.
+  Supports the value `"all"` as a shortcut for allow-listing all capabilities supported
+  by the operating system.
+
+!> **Warning:** Allowing more capabilities beyond the default may lead to
+undesirable consequences, including untrusted tasks being able to compromise the
+host system.
+
+## Client Requirements
+
+The `java` driver requires Java to be installed and in your system's `$PATH`. On
+Linux, Nomad must run as root since it will use `chroot` and `cgroups` which
+require root privileges. The task must also specify at least one artifact to
+download, as this is the only way to retrieve the Jar being run.
+
+## Client Attributes
+
+The `java` driver will set the following client attributes:
+
+- `driver.java` - Set to `1` if Java is found on the host node. Nomad determines
+  this by executing `java -version` on the host and parsing the output
+- `driver.java.version` - Version of Java, ex: `1.6.0_65`
+- `driver.java.runtime` - Runtime version, ex: `Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)`
+- `driver.java.vm` - Virtual Machine information, ex: `Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the JVM is higher than version 1.6.0.
+  constraint {
+    attribute = "${attr.driver.java.version}"
+    operator  = ">"
+    value     = "1.6.0"
+  }
+}
+```
+
+## Resource Isolation
+
+The resource isolation provided varies by the operating system of
+the client and the configuration.
+
+On Linux, Nomad will attempt to use cgroups, namespaces, and chroot
+to isolate the resources of a process. If the Nomad agent is not
+running as root, many of these mechanisms cannot be used.
+
+As a baseline, the Java jars will be run inside a Java Virtual Machine,
+providing a minimum amount of isolation.
+
+Nomad can only use cgroups to control resources if all the required controllers
+are available. If one or more required cgroups are unavailable, Nomad will
+disable resource controls that require cgroups entirely. See the documentation
+on [cgroup controller requirements][] for more details.
+
+### Chroot
+
+The chroot created on Linux is populated with data in the following
+directories from the host machine:
+
+```
+[
+  "/bin",
+  "/etc",
+  "/lib",
+  "/lib32",
+  "/lib64",
+  "/run/resolvconf",
+  "/sbin",
+  "/usr",
+]
+```
+
+The task's chroot is populated by linking or copying the data from the host into
+the chroot. Note that this can take considerable disk space. Since Nomad v0.5.3,
+the client manages garbage collection locally which mitigates any issue this may
+create.
+
+This list is configurable through the agent client
+[configuration file](/nomad/docs/configuration/client#chroot_env).
+
+[default_pid_mode]: /nomad/docs/drivers/java#default_pid_mode
+[default_ipc_mode]: /nomad/docs/drivers/java#default_ipc_mode
+[cap_add]: /nomad/docs/drivers/java#cap_add
+[cap_drop]: /nomad/docs/drivers/java#cap_drop
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[allow_caps]: /nomad/docs/drivers/java#allow_caps
+[docker_caps]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[cgroup controller requirements]: /nomad/docs/install/production/requirements#hardening-nomad
+[volume_mount]: /nomad/docs/job-specification/volume_mount
+[host volume]: /nomad/docs/configuration/client#host_volume-block
diff --git a/content/nomad/v1.9.x/content/docs/drivers/qemu.mdx b/content/nomad/v1.9.x/content/docs/drivers/qemu.mdx
new file mode 100644
index 0000000000..ad68dbd918
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/qemu.mdx
@@ -0,0 +1,184 @@
+---
+layout: docs
+page_title: QEMU task driver
+description: Nomad's QEMU task driver provides a generic virtual machine runner that can execute any regular QEMU image. Learn how to use the QEMU task driver in your jobs. Configure image path, driver interface, accelerator, graceful shutdown, guest agent, and port map. Review the QEMU task driver capabilities, plugin options, client requirements, and client attributes such as QEMU version. Learn how the QEMU task driver provides the highest level of workload isolation.
+---
+
+# QEMU task driver
+
+Name: `qemu`
+
+The `qemu` driver provides a generic virtual machine runner. QEMU can utilize
+the KVM kernel module to utilize hardware virtualization features and provide
+great performance. Currently the `qemu` driver can map a set of ports from the
+host machine to the guest virtual machine, and provides configuration for
+resource allocation.
+
+The `qemu` driver can execute any regular `qemu` image (e.g. `qcow`, `img`,
+`iso`), and is currently invoked with `qemu-system-x86_64`.
+
+The driver requires the image to be accessible from the Nomad client via the
+[`artifact` downloader](/nomad/docs/job-specification/artifact).
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "qemu"
+
+  config {
+    image_path        = "/path/to/my/linux.img"
+    accelerator       = "kvm"
+    graceful_shutdown = true
+    args              = ["-nodefaults", "-nodefconfig"]
+  }
+}
+```
+
+The `qemu` driver supports the following configuration in the job spec:
+
+- `image_path` - The path to the downloaded image. In most cases this will just
+  be the name of the image. However, if the supplied artifact is an archive that
+  contains the image in a subfolder, the path will need to be the relative path
+  (`subdir/from_archive/my.img`).
+
+- `drive_interface` - (Optional) This option defines on which type of interface
+  the drive is connected. Available types are: `ide`, `scsi`, `sd`, `mtd`,
+  `floppy`, `pflash`, `virtio` and `none`. Default is `ide`.
+
+- `accelerator` - (Optional) The type of accelerator to use in the invocation.
+  If the host machine has `qemu` installed with KVM support, users can specify
+  `kvm` for the `accelerator`. Default is `tcg`.
+
+- `graceful_shutdown` `(bool: false)` - Using the [qemu
+  monitor](https://en.wikibooks.org/wiki/QEMU/Monitor), send an ACPI shutdown
+  signal to virtual machines rather than simply terminating them. This emulates
+  a physical power button press, and gives instances a chance to shut down
+  cleanly. If the VM is still running after `kill_timeout`, it will be
+  forcefully terminated. This feature uses a Unix socket that is placed within
+  the task directory and operating systems may impose a limit on how long these
+  paths can be. This feature is currently not supported on Windows.
+
+- `guest_agent` `(bool: false)` - Enable support for the [QEMU Guest
+  Agent](https://wiki.qemu.org/Features/GuestAgent) for this virtual machine.
+  This will add the necessary virtual hardware and create a `qa.sock` file in
+  the task's working directory for interacting with the agent. The QEMU Guest
+  Agent must be running in the guest VM. This feature is currently not
+  supported on Windows.
+
+- `port_map` - (Optional) A key-value map of port labels.
+
+  ```hcl
+  config {
+    # Forward the host port with the label "db" to the guest VM's port 6539.
+    port_map {
+      db = 6539
+    }
+  }
+  ```
+
+- `args` - (Optional) A list of strings that is passed to QEMU as command line
+  options.
+
+## Examples
+
+A simple config block to run a `qemu` image:
+
+```
+task "virtual" {
+  driver = "qemu"
+
+  config {
+    image_path  = "local/linux.img"
+    accelerator = "kvm"
+    args        = ["-nodefaults", "-nodefconfig"]
+  }
+
+  # Specifying an artifact is required with the "qemu"
+  # driver. This is the # mechanism to ship the image to be run.
+  artifact {
+    source = "https://internal.file.server/linux.img"
+
+    options {
+      checksum = "md5:123445555555555"
+    }
+  }
+```
+
+## Capabilities
+
+The `qemu` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | none           |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `qemu` driver requires QEMU to be installed and in your system's `$PATH`.
+The task must also specify at least one artifact to download, as this is the only
+way to retrieve the image being run.
+
+## Client Attributes
+
+The `qemu` driver will set the following client attributes:
+
+- `driver.qemu` - Set to `1` if QEMU is found on the host node. Nomad determines
+  this by executing `qemu-system-x86_64 -version` on the host and parsing the output
+- `driver.qemu.version` - Version of `qemu-system-x86_64`, ex: `2.4.0`
+
+Here is an example of using these properties in a job file:
+
+```hcl
+job "docs" {
+  # Only run this job where the qemu version is higher than 1.2.3.
+  constraint {
+    attribute = "${driver.qemu.version}"
+    operator  = ">"
+    value     = "1.2.3"
+  }
+}
+```
+
+## Plugin Options
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths    = ["/mnt/image/paths"]
+    args_allowlist = ["-drive", "-usbdevice"]
+  }
+}
+```
+
+- `image_paths` (`[]string`: `[]`) - Specifies the host paths the QEMU
+  driver is allowed to load images from.
+- `args_allowlist` (`[]string`: `[]`) - Specifies the command line
+  flags that the [`args`] option is permitted to pass to QEMU. If
+  unset, a job submitter can pass any command line flag into QEMU,
+  including flags that provide the VM with access to host devices such
+  as USB drives. Refer to the [QEMU documentation] for the available
+  flags.
+
+## Resource Isolation
+
+Nomad uses QEMU to provide full software virtualization for virtual machine
+workloads. Nomad can use QEMU KVM's hardware-assisted virtualization to deliver
+better performance.
+
+Virtualization provides the highest level of isolation for workloads that
+require additional security, and resource use is constrained by the QEMU
+hypervisor rather than the host kernel. VM network traffic still flows through
+the host's interface(s).
+
+Note that the strong isolation provided by virtualization only applies
+to the workload once the VM is started. Operators should use the
+`args_allowlist` option to prevent job submitters from accessing
+devices and resources they are not allowed to access.
+
+[`args`]: /nomad/docs/drivers/qemu#args
+[QEMU documentation]: https://www.qemu.org/docs/master/system/invocation.html
diff --git a/content/nomad/v1.9.x/content/docs/drivers/raw_exec.mdx b/content/nomad/v1.9.x/content/docs/drivers/raw_exec.mdx
new file mode 100644
index 0000000000..e2d589e854
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/drivers/raw_exec.mdx
@@ -0,0 +1,200 @@
+---
+layout: docs
+page_title: Raw Fork/Exec task driver
+description: Nomad's Raw Exec task driver lets you execute commands with no resource isolation. Learn how to use the Raw Fork/Exec task driver in your jobs. Configure the command to execute, command arguments, cgroup overrides, work directory, and out-of-memory (OOM) behavior. Review the Isolated Fork/Exec task driver capabilities, plugin options, client requirements, and client attributes.
+---
+
+# Raw Fork/Exec task driver
+
+Name: `raw_exec`
+
+The `raw_exec` driver is used to execute a command for a task without any
+isolation. Further, the task is started as the same user as the Nomad process.
+As such, it should be used with extreme care and is disabled by default.
+
+## Task Configuration
+
+```hcl
+task "webservice" {
+  driver = "raw_exec"
+
+  config {
+    command = "my-binary"
+    args    = ["-flag", "1"]
+  }
+}
+```
+
+The `raw_exec` driver supports the following configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. If executing a binary
+  that exists on the host, the path must be absolute. If executing a binary that
+  is downloaded from an [`artifact`](/nomad/docs/job-specification/artifact), the
+  path can be relative from the allocation's root directory.
+
+- `args` - (Optional) A list of arguments to the `command`. References
+  to environment variables or any [interpretable Nomad
+  variables](/nomad/docs/runtime/interpolation) will be interpreted before
+  launching the task.
+
+- `cgroup_v1_override` - (Optional) A map of controller names to paths. The
+  task will be added to these cgroups. The task will fail if these cgroups do
+  not exist. **WARNING:** May conflict with other Nomad driver's cgroups and
+  have unintended side effects.
+
+- `cgroup_v2_override` - (Optional) Adds the task to a unified cgroup path.
+  Paths may be relative to the cgroupfs root or absolute.  **WARNING:** May
+  conflict with other Nomad driver's cgroups and have unintended side
+  effects.
+
+~> The `task.user` field cannot be set on a Task using the `raw_exec` driver if
+the Nomad client has been hardened according to the [production][hardening] guide.
+
+- `oom_score_adj` - (Optional) A positive integer to indicate the likelihood of
+  the task being OOM killed (valid only for Linux). Defaults to 0.
+
+- `work_dir` - (Optional) Sets a custom working directory for the task. This
+  must be an absolute path. This will also change the working directory when
+  using `nomad alloc exec`.
+
+
+## Examples
+
+To run a binary present on the Node:
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    # When running a binary that exists on the host, the path must be absolute/
+    command = "/bin/sleep"
+    args    = ["1"]
+  }
+}
+```
+
+To execute a binary downloaded from an [`artifact`](/nomad/docs/job-specification/artifact):
+
+```
+task "example" {
+  driver = "raw_exec"
+
+  config {
+    command = "name-of-my-binary"
+  }
+
+  artifact {
+    source = "https://internal.file.server/name-of-my-binary"
+    options {
+      checksum = "sha256:abd123445ds4555555555"
+    }
+  }
+}
+```
+
+## Capabilities
+
+The `raw_exec` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation |
+| -------------------- | -------------- |
+| `nomad alloc signal` | true           |
+| `nomad alloc exec`   | true           |
+| filesystem isolation | none           |
+| network isolation    | host, group    |
+| volume mounting      | none           |
+
+## Client Requirements
+
+The `raw_exec` driver can run on all supported operating systems. For security
+reasons, it is disabled by default. To enable raw exec, the Nomad client
+configuration must explicitly enable the `raw_exec` driver in the plugin's options:
+
+```
+plugin "raw_exec" {
+  config {
+    enabled = true
+  }
+}
+```
+
+Nomad versions before v0.9 use the following client configuration. This configuration is
+also supported in Nomad v0.9.0, but is deprecated in favor of the plugin block:
+
+```
+client {
+  options = {
+    "driver.raw_exec.enable" = "1"
+  }
+}
+```
+
+## Plugin Options
+
+- `enabled` - Specifies whether the driver should be enabled or disabled.
+  Defaults to `false`.
+
+- `denied_host_uids` - (Optional) Specifies a comma-separated list of host uids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user has a user id in
+  the given ranges, the task will error before starting. This will not be checked on Windows
+  clients.
+
+```hcl
+config {
+  denied_host_uids = "0,10-15,22"
+}
+```
+
+- `denied_host_gids` - (Optional) Specifies a comma-separated list of host gids to
+  deny. Ranges can be specified by using a hyphen separating the two inclusive ends.
+  If a "user" value is specified in task configuration and that user is part of
+  any groups with gid's in the specified ranges, the task will error before
+  starting. This will not be checked on Windows clients.
+
+```hcl
+config {
+  denied_host_gids = "2,4-8"
+}
+```
+
+## Client Options
+
+~> Note: client configuration options will soon be deprecated. Please use
+[plugin options][plugin-options] instead. See the [plugin block][plugin-block] documentation for more information.
+
+- `driver.raw_exec.enable` - Specifies whether the driver should be enabled or
+  disabled. Defaults to `false`.
+
+## Client Attributes
+
+The `raw_exec` driver will set the following client attributes:
+
+- `driver.raw_exec` - This will be set to "1", indicating the driver is available.
+
+## Resource Isolation
+
+The `raw_exec` driver provides no filesystem isolation.
+
+If the launched process creates a new process group, it is possible that
+Nomad will leak processes on shutdown unless the application forwards signals
+properly. Nomad will not leak any processes if cgroups are being used to
+manage the process tree. Cgroups are used on Linux when Nomad is being run with
+appropriate privileges, and the cgroup system is mounted.
+
+If the cluster is configured with memory oversubscription enabled, a task using
+the `raw_exec` driver can be configured to have no maximum memory limit by
+setting `memory_max = -1`.
+
+```hcl
+resources {
+  cpu        = 500
+  memory     = 128
+  memory_max = -1 # no limit
+}
+```
+
+[hardening]: /nomad/docs/install/production/requirements#user-permissions
+[plugin-options]: #plugin-options
+[plugin-block]: /nomad/docs/configuration/plugin
diff --git a/content/nomad/v1.9.x/content/docs/ecosystem.mdx b/content/nomad/v1.9.x/content/docs/ecosystem.mdx
new file mode 100644
index 0000000000..d754473c0e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/ecosystem.mdx
@@ -0,0 +1,89 @@
+---
+layout: docs
+page_title: Nomad Ecosystem
+description: Learn about the Nomad ecosystem, which includes CI/CD, task drivers, service mesh, service proxy, secrets management, observability, autoscaling, storage, provisioning, GPUs, and cloud native support.
+---
+
+# Nomad Ecosystem
+
+## Continuous Integration & Delivery
+
+- [GitLab](https://www.hashicorp.com/resources/nomad-ci-cd-developer-workflows-and-integrations)
+- [Codefresh](https://codefresh.io/docs/docs/yaml-examples/examples/nomad/)
+- [CircleCI](https://circleci.com/docs/server/operator/introduction-to-nomad-cluster-operation)
+- [Drone](https://docs.drone.io/runner/nomad/overview/)
+- [Jenkins](https://plugins.jenkins.io/nomad/)
+- [Buildkite](https://buildkite.com/works-with/hashicorp)
+
+## Task Drivers
+
+- [Containerd](/nomad/plugins/drivers/community/containerd)
+- [Windows IIS](https://github.com/Roblox/nomad-driver-iis)
+- [Jailtask](/nomad/plugins/drivers/community/jail-task-driver)
+- [Pot](https://github.com/trivago/nomad-pot-driver)
+- [Singularity](/nomad/plugins/drivers/community/singularity)
+- [Firecracker](/nomad/plugins/drivers/community/firecracker-task-driver)
+- [Podman](/nomad/plugins/drivers/podman)
+
+## Application Definition & Image Build
+
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack)
+- [Levant](https://github.com/hashicorp/levant)
+- [Packer](https://www.packer.io/)
+- [Waypoint](/waypoint/tutorials/get-started-nomad)
+
+## Container Registry
+
+- [JFrog Artifactory](https://jfrog.com/blog/cluster-management-made-simple-with-jfrog-artifactory-and-hashicorp-nomad/)
+
+## Observability and Analysis
+
+- Prometheus
+  - [Using Prometheus to Monitor Nomad Metrics](/nomad/tutorials/manage-clusters/prometheus-metrics)
+  - [Start Prometheus](/nomad/tutorials/nomad-1-0/dynamic-application-sizing#start-prometheus)
+- [Grafana](https://www.metricfire.com/blog/monitoring-hashicorp-nomad-with-prometheus-and-grafana/)
+- [DataDog](https://docs.datadoghq.com/integrations/nomad/)
+- [Turbonomics](https://www.youtube.com/watch?v=lwtIaPpdDsc)
+- [Circonus](/nomad/tools/autoscaling/agent/telemetry#circonus)
+- [Splunk](https://www.kmruddy.com/2020/deploying-splunk-enterprise-with-nomad/)
+
+## Secret Management
+
+- [Vault](/nomad/docs/integrations/vault-integration)
+
+## Service Mesh
+
+- [Consul](/nomad/docs/integrations/consul-integration)
+
+## Provisioning
+
+- [Terraform](https://registry.terraform.io/providers/hashicorp/nomad/latest/docs)
+- [Chef](https://github.com/nathwill/chef-nomad)
+- [Ansible](https://github.com/ansible-community/ansible-nomad)
+
+## Cloud Native Network
+
+- [CNI](/nomad/docs/integrations/consul-connect#cni-plugins)
+
+## Service Proxy
+
+- [Envoy](/nomad/docs/integrations/consul-connect)
+- [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+- [Traefik](/nomad/tutorials/load-balancing/load-balancing-traefik)
+
+## Storage
+
+- [CSI](/nomad/docs/concepts/plugins/csi)
+- [Portworx](/nomad/tutorials/stateful-workloads/stateful-workloads-portworx)
+
+## GPUs
+
+- NVIDIA
+  - [Using HashiCorp Nomad to Schedule GPU Workloads](https://developer.nvidia.com/blog/hashicorp-nomad-gpu-scheduling/)
+  - [Running GPU-Accelerated Applications on Nomad](https://www.hashicorp.com/resources/running-gpu-accelerated-applications-on-nomad)
+
+## Autoscaling
+
+- AWS ASGs
+  - [Dynamically autoscale your Nomad clusters](https://www.hashicorp.com/blog/cluster-scaling-with-the-hashicorp-nomad-autoscaler)
+- [Spot](https://docs.spot.io/container-management/nomad/nomad-integration-with-elastigroup/)
diff --git a/content/nomad/v1.9.x/content/docs/enterprise/index.mdx b/content/nomad/v1.9.x/content/docs/enterprise/index.mdx
new file mode 100644
index 0000000000..6022fd2d87
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/enterprise/index.mdx
@@ -0,0 +1,212 @@
+---
+layout: docs
+page_title: Nomad Enterprise
+description: >-
+  Nomad Enterprise adds operations, collaboration, and governance capabilities
+  such as resource quotas, Sentinel policies, audit logging, multi-region deployments, and advanced server management using Nomad Autopilot.
+---
+
+# Nomad Enterprise
+
+This page provides an overview of Nomad Enterprise features that
+add operations, collaboration, and governance capabilities such as resource
+quotas, Sentinel policies, audit logging, multi-region deployments, and advanced
+server management using Nomad Autopilot.
+
+Nomad Enterprise is available as a base Platform package with an optional
+Governance & Policy add-on module.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Nomad Enterprise Platform
+
+Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as
+enhances performance and availability through Advanced Autopilot features such
+as Automated Upgrades, Enhanced Read Scalability, and Redundancy Zones.
+
+### Long Term Support (LTS) Releases
+
+Nomad Enterprise initiated the Long-Term Support (LTS) release program with
+Nomad 1.8. Going forward, the first major release of each calendar year will be
+an LTS release.
+
+LTS releases have the following benefits for Nomad operators:
+
+- **Extended maintenance:** Two years of critical fixes provided through minor
+releases
+- **Efficient upgrades:** Support for direct upgrades from one LTS release
+to the next, reducing major-version upgrade risk and improving operational
+efficiency.
+
+LTS releases reduce operational overhead and risk by letting organizations
+receive critical fixes in minor releases without having to upgrade their major
+version more than once a year. Once you’ve upgraded to Nomad Enterprise 1.8,
+you will be running on a maintained LTS release that will allow you to easily
+upgrade to the next LTS major release when it's available. For more
+information, refer to HashiCorp’s multi-product LTS statement.
+
+
+### Automated Upgrades
+
+Automated Upgrades allows operators to deploy a complete cluster of new
+servers and then simply wait for the upgrade to complete. As the new servers
+join the cluster, server logic checks the version of each Nomad server
+node. If the version is higher than the version on the current set of voters,
+it will avoid promoting the new servers to voters until the number of new
+servers matches the number of existing servers at the previous version. Once
+the numbers match, Nomad will begin to promote new servers and demote old
+ones.
+
+See the [Autopilot - Upgrade
+Migrations](/nomad/tutorials/manage-clusters/autopilot#upgrade-migrations)
+documentation for a thorough overview.
+
+### Automated Backups
+
+Automated Backups allows operators to run the snapshot agent as a long-running
+daemon process or in a one-shot mode from a batch job. The agent takes
+snapshots of the state of the Nomad servers and saves them locally, or pushes
+them to an optional remote storage service, such as Amazon S3.
+
+This capability provides an enterprise solution for backup and restoring the
+state of Nomad servers within an environment in an automated manner. These
+snapshots are atomic and point-in-time.
+
+See the [Operator Snapshot agent](/nomad/docs/commands/operator/snapshot/agent)
+documentation for a thorough overview.
+
+### Enhanced Read Scalability
+
+This feature enables an operator to introduce non-voting server nodes to a
+Nomad cluster. Non-voting servers will receive the replication stream but will
+not take part in quorum (required by the leader before log entries can be
+committed). Adding explicit non-voters will scale reads and scheduling without
+impacting write latency.
+
+See the [Autopilot - Read
+Scalability](/nomad/tutorials/manage-clusters/autopilot#server-read-and-scheduling-scaling)
+documentation for a thorough overview.
+
+### Redundancy Zones
+
+Redundancy Zones enables an operator to deploy a non-voting server as a hot
+standby server on a per availability zone basis. For example, in an
+environment with three availability zones an operator can run one voter and
+one non-voter in each availability zone, for a total of six servers. If an
+availability zone is completely lost, only one voter will be lost, so the
+cluster remains available. If a voter is lost in an availability zone, Nomad
+will promote the non-voter to a voter automatically, putting the hot standby
+server into service quickly.
+
+See the [Autopilot - Redundancy
+Zones](/nomad/tutorials/manage-clusters/autopilot#redundancy-zones)
+documentation for a thorough overview.
+
+### Multiple Vault Namespaces
+
+Multi-Vault Namespaces enables an operator to configure a single Nomad cluster
+to support multiple Vault Namespaces for topology simplicity and fleet
+consolidation when running Nomad and Vault together. Nomad will automatically
+retrieve a Vault token based on a job's defined Vault Namespace and make it
+available for the specified Nomad task at hand.
+
+See the [Vault Integration documentation](/nomad/docs/integrations/vault-integration#enterprise-configuration) for more information.
+
+### Multiple Vault and Consul Clusters
+
+Nomad Enteprise allows sepcifying multiple integrations for Consul and Vault in
+the [vault](/nomad/docs/configuration/vault) and
+[consul](/nomad/docs/configuration/consul) portions of the Nomad agent
+configuration. After the agents are configured, Nomad jobspec writers can pick
+which Consul or Vault cluster to use in their job. Nomad administrators may
+also set default clusters for each in Nomad namespace configuration, as well as
+deny access to certain clusters by namespace.
+
+
+## Governance & Policy
+
+Governance & Policy features are part of an add-on module that enables an
+organization to securely operate Nomad at scale across multiple teams through
+features such as Audit Logging, Resource Quotas, and Sentinel Policies.
+
+### Audit Logging
+
+Secure clusters with enhanced risk management and operational traceability to
+fulfill compliance requirements. This Enterprise feature provides
+administrators with a complete set of records for all user-issued actions in
+Nomad.
+
+With Audit Logging, enterprises can now proactively identify access anomalies,
+ensure enforcement of their security policies, and diagnose cluster behavior
+by viewing preceding user operations. Designed as an HTTP API based audit
+logging system, each audit event is captured with relevant request and
+response information in a JSON format that is easily digestible and familiar
+to operators.
+
+See the [Audit Logging Documentation](/nomad/docs/configuration/audit) for a
+thorough overview.
+
+### Resource Quotas
+
+Resource Quotas enable an operator to limit resource consumption across teams
+or projects to reduce waste and align budgets. In Nomad Enterprise, operators
+can define [quota specifications](/nomad/docs/other-specifications/quota)
+and apply them to namespaces. When a quota is attached to a namespace,
+the jobs within the namespace may not consume more resources than the quota
+specification allows.
+
+This allows operators to partition a shared cluster and ensure that no single
+actor can consume the whole resources of the cluster.
+
+See the [Resource Quotas
+Guide](/nomad/tutorials/governance-and-policy/quotas) for a thorough
+overview.
+
+### Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use
+pre-authorized Docker images. Sentinel policies are defined as code, giving
+operators considerable flexibility to meet compliance requirements.
+
+See the [Sentinel Policies Guide][] for a walk-through on deploying Sentinel
+policies and the [Nomad Sentinel policy reference][] for more information on
+what objects are available for policies.
+
+## Multi-Cluster & Efficiency
+
+Multi-Cluster & Efficiency features are part of an add-on module that enables
+an organization to operate Nomad at scale across multiple clusters through
+features such as Multiregion Deployments.
+
+### Multiregion Deployments
+
+[Multiregion Deployments] enable an operator to deploy a single job to multiple
+federated regions. This includes the ability to control the order of rollouts
+and how each region will behave in the event of a deployment failure.
+
+### Dynamic Application Sizing
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. This
+feature builds on Nomad [autoscaling capabilities] to remove the trial-and-error
+routine of manually setting resource requirements. DAS comprises support for
+vertical [scaling policies], a new API and UI for reviewing recommended job
+changes, and a collection of Nomad Autoscaler plugins informed by best-practice
+statistical measures.
+
+## Try Nomad Enterprise
+
+Click [here](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo or
+request a trial of Nomad Enterprise.
+
+[multiregion deployments]: /nomad/docs/job-specification/multiregion
+[autoscaling capabilities]: /nomad/tools/autoscaling
+[scaling policies]: /nomad/tools/autoscaling/policy
+[Sentinel Policies Guide]: /nomad/tutorials/governance-and-policy/sentinel
+[Nomad Sentinel policy reference]: /nomad/docs/enterprise/sentinel
diff --git a/content/nomad/v1.9.x/content/docs/enterprise/license/faq.mdx b/content/nomad/v1.9.x/content/docs/enterprise/license/faq.mdx
new file mode 100644
index 0000000000..db8295481b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/enterprise/license/faq.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Nomad Enterprise License FAQ
+description: >-
+  Frequently Asked Questions pertaining to Nomad Enterprise Licensing.
+---
+
+# Nomad Enterprise License FAQ
+
+This FAQ is for the license changes introduced in Nomad Enterprise version v1.6.0+ent.
+
+For license-related FAQ for earlier versions, please refer to earlier versions of this document
+using the version drop-down on this page, e.g. [v1.5.x](/nomad/docs/v1.5.x/enterprise/license/faq).
+
+## Q: Can I get a quick summary of the Nomad changes?
+
+Starting with Nomad Enterprise v1.6.0, license expiration is different.
+
+For trial licenses, the behavior remains the same.  Enterprise features will stop working
+when the license expires, and a server can not start with an expired license.
+
+For new "non-terminating" contract licenses, instead of expiration being compared to the current time,
+expiration time is compared to the build date of the Nomad binary, which you can find in the output of the
+[`nomad version`](/nomad/docs/commands/version) command.
+
+The practical result is that newer contract licenses will work in perpetuity for any v1.6.0+ version of Nomad
+built prior to the expiration time of the license.  No features will stop working,
+and server agents can be restarted safely.
+
+However, if you try to upgrade to a newer binary past license expiration, the server will not start.
+To proactively avoid that, you can test a new binary with your license using the new
+[`nomad license inspect`][license inspect] command
+before trying to upgrade your servers.
+
+## Q: What resources are available?
+
+The list below is a great starting point for learning more about license usage in general.
+
+- [v1.6.0 Upgrade Guide](/nomad/docs/upgrade/upgrade-specific#enterprise-license-validation-with-builddate)
+
+- [Nomad License Documentation](/nomad/docs/enterprise/license)
+
+- [License configuration values documentation](/nomad/docs/configuration/server#license_path)
+
+- [Install a HashiCorp Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license)
+
+## Q: Does this affect older versions of Nomad?
+
+This change only affects Nomad Enterprise version v1.6.0+ent and later.
+
+## Q: Does the license have to be present on Nomad client nodes?
+
+Only Nomad server nodes need to have the license present.
+Nomad agents running with the `-dev` flag will also need a license.
+
+## Q: What are some pitfalls that could be experienced during an upgrade because of the license changes?
+
+If you have an expired license that has not yet become fully nonfunctional
+(i.e. it is in grace period between ExpirationTime and TerminationTime),
+then a Nomad server will not be able to start using a new v1.6.0+ binary.
+
+Before shutting down a server agent to replace it with a new version,
+be sure to run [`nomad license inspect`][license inspect] with the new binary.
+
+## Q: How can a user get their existing license?
+
+If you are an existing HashiCorp enterprise customer you may contact your organization's customer success manager (CSM) or email support-softwaredelivery@hashicorp.com for information on how to get your organization's enterprise license.
+You can use `nomad license get` to retrieve information about the license, but not the license itself.
+
+## Q: What happens when a license expires?
+
+All features will continue to work until you attempt to upgrade Nomad that is newer than your license expiration time.
+In that case, the server agent will fail to start, and you'll need to roll back to the previous working version
+and acquire a new license to use with the newer Nomad version before attempting the upgrade again.
+
+## Q: Are licenses cluster-specific? node-specific?
+
+Licenses can be reused on different nodes and different clusters.
+
+## Q: Where can users get a trial license for Nomad?
+
+Follow [these instructions](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license) to request and enable a free 30-day trial license.
+
+## Q: When a Nomad client agent restarts, will it still need a license file?
+
+Every time `nomad agent` runs as a server (or in `-dev`), it requires a license.
+
+## Q: May I downgrade Nomad Enterprise from v1.6.0 to an earlier version?
+
+Yes, if you upgrade a server to 1.6.0+ but it fails to start due to license expiration,
+you can roll back to a previous working version with the old expiration logic.
+
+If a server fails to start for any other reason aside from license expiration,
+roll back to a previous version is not supported due to the Nomad state store
+not having forward compatibility, and may result in a crash loop.
+
+## Q: Is there a tutorial available for the license configuration steps?
+Please visit the [Enterprise License Tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license).
+
+[license inspect]: /nomad/docs/commands/license/inspect
diff --git a/content/nomad/v1.9.x/content/docs/enterprise/license/index.mdx b/content/nomad/v1.9.x/content/docs/enterprise/license/index.mdx
new file mode 100644
index 0000000000..c61c0869e6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/enterprise/license/index.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: Nomad Enterprise Licensing
+description: >-
+  Learn how to configure, apply, and replace your Nomad Enterprise license. Use the `nomad license` command to review your license details.
+---
+
+# Nomad Enterprise Licensing
+
+<EnterpriseAlert product="nomad"/>
+
+This page provides information on how to configure, apply, inspect, and replace
+your Nomad Enterprise license.
+
+Each server in a Nomad Enterprise cluster must have a license to start. Download
+Nomad Enterprise from the [releases site].
+
+[Contact sales](https://www.hashicorp.com/go/nomad-enterprise) to set up a demo
+of Nomad Enterprise.
+
+Refer to the Enterprise license
+[tutorial](/nomad/tutorials/enterprise/hashicorp-enterprise-license) for
+step-by-step license instructions. Review the [Request a trial license section
+](/nomad/tutorials/enterprise/hashicorp-enterprise-license#request-a-trial-license)
+for instructions on how to get a trial license.
+
+~> **Note:** A Nomad Enterprise cluster cannot be downgraded to the open
+source version of Nomad. Servers running the open source version of Nomad will
+panic if they are joined to a Nomad Enterprise cluster, due to raft entries
+relating to Enterprise features not being parseable by open source Nomad.
+
+## Expiring Licenses
+
+Nomad Enterprise licenses have an expiration time.
+You can read and validate the license on a running server,
+on disk, or in your environment with the
+[`nomad license` commands](/nomad/docs/commands/license).
+
+Before upgrading Nomad or replacing your license with a new one, you should always run
+[`nomad license inspect`](/nomad/docs/commands/license/inspect)
+to ensure the license is valid with your server binary.
+
+As a Nomad Enterprise license approaches its expiration time, Nomad servers
+will periodically log a warning message about the approaching
+expiration. Below shows log excerpts of the warnings.
+
+```
+    2021-03-29T15:02:28.100-0400 [WARN]  nomad.licensing: license expiring: time_left=5m0s
+    2021-03-29T15:03:28.103-0400 [WARN]  nomad.licensing: license expiring: time_left=4m0s
+    2021-03-29T15:04:28.106-0400 [WARN]  nomad.licensing: license expiring: time_left=3m0s
+    2021-03-29T15:05:28.109-0400 [WARN]  nomad.licensing: license expiring: time_left=2m0s
+    2021-03-29T15:06:28.112-0400 [WARN]  nomad.licensing: license expiring: time_left=1m0s
+    2021-03-29T15:07:28.114-0400 [WARN]  nomad.licensing: license expiring: time_left=0s
+    2021-03-29T15:07:58.104-0400 [ERROR] nomad.licensing: license expired, please update license: error="invalid license or license is expired"
+```
+
+When the license expires, enterprise functionality will become limited. Only
+read operations on enterprise endpoints will be supported, and write
+operations will return an error.
+
+## Configuring the License
+
+See the server [license configuration] reference documentation on all the
+options to set an enterprise license. Nomad will load the license file from
+disk or environment when it starts.
+
+In order to immediately alert operators of a bad configuration setting, if a
+license configuration option is an invalid or expired license, the Nomad server
+will exit with an error.
+
+```
+NOMAD_LICENSE=misconfigured nomad agent -dev
+==> No configuration files loaded
+==> Starting Nomad agent...
+==> Error starting agent: server setup failed: failed to initialize enterprise licensing: a file license was configured but the license is invalid: error decoding version: expected integer
+```
+
+See the [License commands](/nomad/docs/commands/license) for more information on
+interacting with the Enterprise License.
+
+[releases site]: https://releases.hashicorp.com/nomad
+[license configuration]: /nomad/docs/configuration/server#license_path
+[license endpoint]: /nomad/api-docs/operator/license#updating-the-nomad-enterprise-license
diff --git a/content/nomad/v1.9.x/content/docs/enterprise/license/utilization-reporting.mdx b/content/nomad/v1.9.x/content/docs/enterprise/license/utilization-reporting.mdx
new file mode 100644
index 0000000000..57d67127c5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/enterprise/license/utilization-reporting.mdx
@@ -0,0 +1,147 @@
+---
+layout: docs
+page_title: Automated license utilization reporting
+description: >-
+  Learn what data HashiCorp collects to monitor Enterprise license utilization. Enable or opt out of automatic reporting. Review sample payloads and logs.
+---
+
+# Automated license utilization reporting
+
+<EnterpriseAlert product="nomad" />
+
+This page provides information on the data HashiCorp collects to monitor
+Enterprise license utilization. Learn how to enable or opt out of automatic
+reporting. Review sample payloads and logs.
+
+## Introduction
+
+Automated license utilization reporting sends license utilization data to HashiCorp without requiring you
+to manually collect and report them. It also lets you review your license usage with the monitoring
+solution you already use (for example Splunk, Datadog, or others) so you can optimize and manage your
+deployments. Use these reports to understand how much more you can deploy under your current contract,
+protect against overutilization, and budget for predicted consumption.
+
+Automated reporting shares the minimum data required to validate license utilization as defined in our
+contracts. They consist of mostly computed metrics and will never contain Personal Identifiable Information
+(PII) or other sensitive information. Automated reporting shares the data with HashiCorp using a secure,
+unidirectional HTTPS API and makes an auditable record in the product logs each time it submits a report.
+The reporting process is GDPR compliant and submits reports roughly once every 24 hours.
+
+## Enable automated reporting
+
+To enable automated reporting, you need to make sure that outbound network traffic is configured correctly
+and upgrade your enterprise product to a version that supports it. If your installation is air-gapped or
+network settings are not in place, automated reporting will not work.
+
+### 1. Allow outbound HTTPS traffic on port 443
+
+Make sure that your network allows HTTPS egress on port 443 from https://reporting.hashicorp.services by
+allow-listing the following IP addresses:
+
+- 100.20.70.12
+- 35.166.5.222
+- 23.95.85.111
+- 44.215.244.1
+
+### 2. Upgrade
+
+Upgrade to a release that supports license utilization reporting. These releases include:
+- [Nomad v1.7.0](/nomad/downloads) and later
+
+### 3. Check logs
+
+Automatic license utilization reporting will start sending data within roughly 24 hours. Check the product
+logs for records that the data sent successfully.
+
+Instructions on how to check logs.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: recording audit record
+[INFO]  reporting: Report sent: auditRecord={"payload":{"payload_version":"1","license_id":"d2cdd857-4202-5a45-70a6-e4b531050c34","product":"nomad","product_version":"1.6.0","export_timestamp":"2023-05-26T20:09:13.753921087Z","snapshots":[{"snapshot_version":1,"snapshot_id":"0001J724F90F4XWQDSAA76ZQWA","process_id":"01H1CTJPC1S8H7Q45MKTJ689ZW","timestamp":"2023-05-26T20:09:13.753513962Z","schema_version":"1.0.0","service":"nomad","metrics":{"nomad.billable.nodes":{"key":"nomad.billable.nodes","kind":"counter","mode":"write","value":33}}}]}}
+[DEBUG] completed recording audit record
+[DEBUG] core.reporting: export finished successfully
+```
+
+If your installation is air-gapped or your network doesn’t allow the correct egress, logs will show an
+error.
+
+```
+[DEBUG] core.reporting: beginning snapshot export
+[DEBUG] core.reporting: creating payload
+[DEBUG] core.reporting: marshalling payload to json
+[DEBUG] core.reporting: generating authentication headers
+[DEBUG] core.reporting: creating request
+[DEBUG] core.reporting: sending request
+[DEBUG] core.reporting: performing request: method=POST url=https://reporting.hashicorp.services
+[DEBUG] core.reporting: error status code received: statusCode=403
+```
+
+In this case, reconfigure your network to allow egress and check back in 24 hours.
+
+## Opt out
+
+If your installation is air-gapped or you want to manually collect and report on the same license
+utilization metrics, you can opt-out of automated reporting.
+
+Manually reporting these metrics can be time consuming. Opting out of automated reporting does not mean that
+you also opt out from sending license utilization metrics. Customers who opt out of automated reporting will
+still be required to manually collect and send license utilization metrics to HashiCorp.
+
+If you are considering opting out because you’re worried about the data, we strongly recommend that you
+review the [example payloads](#example-payloads) before opting out. If you have concerns with any of the
+automatically-reported data please bring them to your account manager.
+
+You have two options to opt out of automated reporting: HCL configuration (recommended) and Environment
+variable (requires restart).
+
+Opting out in your product’s configuration file doesn’t require a system restart, and is the method we
+recommend. Add the following block to your `server.hcl` file.
+
+```hcl
+reporting {
+	license {
+		enabled = false
+    }
+}
+```
+
+If you need to, you can also opt out using an environment variable, which will provide a startup message
+confirming that you have disabled automated reporting. This option requires a system restart.
+
+Set the following environment variable.
+
+```
+$ export OPTOUT_LICENSE_REPORTING=true
+```
+
+Now restart your system by following [these instructions](/nomad/docs/operations/nomad-agent).
+
+Check your product logs roughly 24 hours after opting out to make sure that the system isn’t trying to send
+reports.
+
+If your configuration file and environment variable differ, the environment variable setting will take
+precedence.
+
+## Example payloads
+
+HashiCorp collects the following utilization data as JSON payloads:
+
+`billable.nodes` - Number of billable nodes in Nomad
+
+```json
+"metrics": {
+    "nomad.billable.nodes": {
+        "key": "nomad.billable.nodes",
+        "kind": "counter",
+        "mode": "write",
+        "value": 33
+    }
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/enterprise/sentinel.mdx b/content/nomad/v1.9.x/content/docs/enterprise/sentinel.mdx
new file mode 100644
index 0000000000..7abcb3a233
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/enterprise/sentinel.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: Sentinel Policy Reference
+description: >-
+  Use the Nomad Enterprise Sentinel policy feature to implement fine-grained control over jobs, such as restricting when jobs can run or ensuring jobs use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+---
+
+# Sentinel Policy Reference
+
+<EnterpriseAlert product="nomad" />
+
+This page provides reference information on using the Nomad Sentinel policy feature to implement fine-grained policies such as restricting when jobs can run or ensuring job use specific images. Learn about policy structure, job objects, Access Control List (ACL) token objects, and namespace objects.
+
+## Introduction to Sentinel Policies
+
+In Nomad Enterprise, operators can create Sentinel policies for fine-grained
+policy enforcement. Sentinel policies build on top of the ACL system and allow
+operators to define policies such as disallowing jobs to be submitted to
+production on Fridays or only allowing users to run jobs that use pre-authorized
+Docker images. Sentinel policies are defined as code, giving operators
+considerable flexibility to meet compliance requirements.
+
+Refer to the [Nomad Sentinel Tutorial][] for more information about deploying
+Sentinel policies, as well as the documentation for the [`nomad sentinel`][]
+subcommands.
+
+## Sentinel Policy Structure
+
+Sentinel policies are specified in the [Sentinel Language][sentinel]. The
+language is designed to be understandable for people who are reading and writing
+policies, while remaining fast to evaluate. There is no limitation on how
+complex policies can be, but they are in the execution path so care should be
+taken to avoid adversely impacting performance.
+
+In each scope, there are different objects made available for introspection,
+such a job being submitted. Policies can inspect these objects to apply
+fine-grained policies.
+
+The following top-level objects are available to policies in the `submit-job`
+scope automatically, without an explicit import.
+
+* `job`: the submitted job. This is a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `existing_job`: the previous version of the job. If `job_exists` is true, this
+  will always be non-nil. This is also a [Sentinel Job
+  Object](#sentinel-job-objects).
+* `job_exists`: a boolean field that indicates that a previous version of the
+  job exists.
+* `nomad_acl_token`: the ACL token the job was submitted with. This is a
+  [Sentinel Nomad ACL Token Object](#sentinel-nomad-acl-token-objects).
+* `namespace`: the namespace the job is in. This is a [Sentinel Nomad Namespace
+  Object](#sentinel-namespace-objects).
+
+Sentinel convention for identifiers is lower case and separated by underscores.
+All fields on an object are accessed by the same name, converted to lower case
+and separating camel case to underscores.
+
+### Sentinel Job Objects
+
+The `job` and `existing_job` objects map to the [JSON job specification][], with
+the fields converted to the Sentinel convention. Here are some examples:
+
+| Job Field                                | Sentinel Accessor                           |
+|------------------------------------------|---------------------------------------------|
+| `job.ID`                                 | `job.id`                                    |
+| `job.AllAtOnce`                          | `job.all_at_once`                           |
+| `job.ParentID`                           | `job.parent_id`                             |
+| `job.TaskGroups`                         | `job.task_groups`                           |
+| `job.TaskGroups[0].EphemeralDisk.SizeMB` | `job.task_groups[0].ephemeral_disk.size_mb` |
+
+
+### Sentinel ACL Token Objects
+
+The `nomad_acl_token` object maps to the [ACL token][], with the fields
+converted to the Sentinel convention. Here are some examples:
+
+| Nomad ACL Token Field         | Sentinel Accessor             |
+|-------------------------------|-------------------------------|
+| `nomad_acl_token.AccessorID`  | `nomad_acl_token.accessor_id` |
+| `nomad_acl_token.Policies[0]` | `nomad_acl_token.policies[0]` |
+
+Note that the `SecretID` field is always redacted to prevent credential leaks.
+
+### Sentinel Namespace Objects
+
+The `namespace` object maps to the [Namespace][], with the fields converted to
+the Sentinel convention. Here are some examples:
+
+| Namespace Field                              | Sentinel Accessor                              |
+|----------------------------------------------|------------------------------------------------|
+| `namespace.Description`                      | `namespace.description`                        |
+| `namespace.NodePoolConfiguration.Allowed[0]` | `namespace.node_pool_configuration.allowed[0]` |
+
+[Nomad Sentinel Tutorial]: /nomad/tutorials/governance-and-policy/sentinel
+[`nomad sentinel`]: /nomad/docs/commands/sentinel
+[sentinel]: https://docs.hashicorp.com/sentinel
+[JSON job specification]: /nomad/api-docs/json-jobs
+[ACL token]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L12991-L13020
+[Namespace]: https://github.com/hashicorp/nomad/blob/v1.7.0-rc.1/nomad/structs/structs.go#L5306-L5338
diff --git a/content/nomad/v1.9.x/content/docs/faq.mdx b/content/nomad/v1.9.x/content/docs/faq.mdx
new file mode 100644
index 0000000000..6f2c454788
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/faq.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Frequently Asked Questions
+description: Nomad frequently asked question topics include checkpoint, gossip and consensus protocols, Nomad datacenter versus Consul datacenter, bootstrapping a cluster, and connecting to a host network with Docker Desktop.
+---
+
+# Frequently Asked Questions
+
+## Q: What is Checkpoint? / Does Nomad call home?
+
+Nomad makes use of a HashiCorp service called [Checkpoint](https://checkpoint.hashicorp.com)
+which is used to check for updates and critical security bulletins.
+Only anonymous information, which cannot be used to identify the user or host, is
+sent to Checkpoint. An anonymous ID is sent which helps de-duplicate warning messages.
+This anonymous ID can be disabled. Using the Checkpoint service is optional and can be disabled.
+
+See [`disable_anonymous_signature`](/nomad/docs/configuration#disable_anonymous_signature)
+and [`disable_update_check`](/nomad/docs/configuration#disable_update_check).
+
+## Q: Is Nomad eventually or strongly consistent?
+
+Nomad makes use of both a [consensus protocol](/nomad/docs/concepts/consensus) and
+a [gossip protocol](/nomad/docs/concepts/gossip). The consensus protocol is strongly
+consistent, and is used for all state replication and scheduling. The gossip protocol
+is used to manage the addresses of servers for automatic clustering and multi-region
+federation. This means all data that is managed by Nomad is strongly consistent.
+
+## Q: Is Nomad's `datacenter` parameter the same as Consul's?
+
+No. For those familiar with Consul, [Consul's notion of a
+datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
+Nomad supports grouping nodes into multiple datacenters, which should reflect
+nodes being colocated, while being managed by a single set of Nomad servers.
+
+Consul on the other hand does not have this two-tier approach to servers and
+agents and instead [relies on federation to create larger logical
+clusters][consul_fed].
+
+## Q: What is "bootstrapping" a Nomad cluster? ((#bootstrapping))
+
+Bootstrapping is the process when a Nomad cluster elects its first leader
+and writes the initial cluster state to that leader's state store. Bootstrapping
+will not occur until at least a given number of servers, defined by
+[`bootstrap_expect`], have connected to each other. Once this process has
+completed, the cluster is said to be bootstrapped and is ready to use.
+
+Certain configuration options are only used to influence the creation of the
+initial cluster state during bootstrapping and are not consulted again so long
+as the state data remains intact. These typically are values that must be
+consistent across server members. For example, the [`default_scheduler_config`]
+option allows an operator to set the SchedulerConfig to non-default values
+during this bootstrap process rather than requiring an immediate call to the API
+once the cluster is up and running.
+
+If the state is completely destroyed, whether intentionally or accidentally, on
+all of the Nomad servers in the same outage, the cluster will re-bootstrap based
+on the Nomad defaults and any configuration present that impacts the bootstrap
+process.
+
+## Q: How to connect to my host network when using Docker Desktop (Windows and MacOS)?
+
+Since Docker is based on Linux-native technologies, Docker Desktop for Windows
+and MacOS uses a small Linux virtual machine to run containers. This extra step
+adds a layer of indirection between the network of your host (the computer you
+are currently using) and the network of the VM running your containers.
+
+This means that, by default, your Docker tasks will not be able to access
+endpoints that are available in your host network, such as a local Consul agent.
+
+In order to properly setup this connection you will need to explicitly bind
+the Nomad client to a non-loopback network interface, and anything else you
+would like to access must also be in the same interface.
+
+On Windows, we recommend you to start with the [WSL2 backend for Docker
+Desktop][wsl2-docker]. Once you are more familiarized with Nomad you can start
+running it natively.
+
+To use the network named `en0` that has the IP address `192.168.0.10`, you can
+start Nomad with this command.
+
+```shell-session
+$ sudo nomad agent -dev -bind=0.0.0.0 -network-interface=en0
+```
+
+To start Consul in the same network, you can run this command.
+
+```shell-session
+$ consul agent -dev -client=0.0.0.0 -bind=192.168.0.10
+```
+
+Now your services will be registered in Consul using the right IP and your
+tasks will be able to reach each other. To access your tasks from your host
+machine you will need to use the network interface IP address.
+
+```shell-session
+$ curl http://192.168.0.10:8080
+```
+
+[consul_dc]: /consul/docs/agent/config/config-files#datacenter
+[consul_fed]: /consul/tutorials/networking/federation-gossip-wan
+[nomad_region]: /nomad/docs/configuration#datacenter
+[`bootstrap_expect`]: /nomad/docs/configuration/server#bootstrap_expect
+[`default_scheduler_config`]: /nomad/docs/configuration/server#default_scheduler_config
+[wsl2-docker]: https://docs.docker.com/docker-for-windows/wsl/
diff --git a/content/nomad/v1.9.x/content/docs/glossary.mdx b/content/nomad/v1.9.x/content/docs/glossary.mdx
new file mode 100644
index 0000000000..bdf71eed3b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/glossary.mdx
@@ -0,0 +1,127 @@
+---
+layout: docs
+page_title: Glossary
+description: Nomad key concepts include allocation, authoritative regions, bin packing, client, datacenters, deployment, driver, evaluation, job, node, node pool, regions, server, task, and task group.
+---
+
+# Glossary
+
+This glossary provides definitions and explanations for important terms and
+concepts used in Nomad.
+
+## Allocation
+
+An Allocation is a mapping between a task group in a job and a client node. A
+single job may have hundreds or thousands of task groups, meaning an
+equivalent number of allocations must exist to map the work to client
+machines. Allocations are created by the Nomad servers as part of scheduling
+decisions made during an evaluation.
+
+## Authoritative and Non-Authoritative Regions
+
+The authoritative region is the region in a federated multi-region cluster that
+holds the source of true for entities replicated across regions, such as ACL
+tokens, policies, and roles, namespaces, and node pools.
+
+All other regions are considered non-authoritative regions and replicate these
+entities by pulling them from the authoritative region.
+
+## Bin Packing
+
+Bin Packing is the process of filling bins with items in a way that maximizes
+the utilization of bins. This extends to Nomad, where the clients are "bins"
+and the items are task groups. Nomad optimizes resources by efficiently bin
+packing tasks onto client machines.
+
+## Client
+
+A Nomad client is an agent configured to run and manage tasks using available
+compute resources on a machine. The agent is responsible for registering with
+the servers, watching for any work to be assigned and executing tasks. The
+Nomad agent is a long lived process which interfaces with the servers.
+
+## Datacenters
+
+Nomad models a datacenter as an abstract grouping of clients within a
+region. Nomad clients are not required to be in the same datacenter as the
+servers they are joined with, but do need to be in the same
+region. Datacenters provide a way to express fault tolerance among jobs as
+well as isolation of infrastructure.
+
+## Deployment
+
+Deployments are the mechanism by which Nomad rolls out changes to cluster state
+in a step-by-step fashion. Deployments are only available for Jobs with the type
+`service`. When an Evaluation is processed, the scheduler creates only the
+number of Allocations permitted by the [`update`][] block and the current state
+of the cluster. The Deployment is used to monitor the health of those
+Allocations and emit a new Evaluation for the next step of the update.
+
+## Driver
+
+A Driver represents the basic means of executing your **Tasks**.  Example
+Drivers include Docker, QEMU, Java, and static binaries.
+
+## Evaluation
+
+Evaluations are the mechanism by which Nomad makes scheduling decisions.  When
+either the _desired state_ (jobs) or _actual state_ (clients) changes, Nomad
+creates a new evaluation to determine if any actions must be taken. An
+evaluation may result in changes to allocations if necessary.
+
+## Job
+
+A Job is a specification provided by users that declares a workload for
+Nomad. A Job is a form of _desired state_; the user is expressing that the
+job should be running, but not where it should be run. The responsibility of
+Nomad is to make sure the _actual state_ matches the user desired state. A
+Job is composed of one or more task groups.
+
+## Node
+
+A more generic term used to refer to machines running Nomad agents in client
+mode. Despite being different concepts, you may find `node` being used
+interchangeably with [`client`](#client) in some materials and informal
+content.
+
+## Node Pool
+
+Node pools are used to group [nodes](#node) and can be used to restrict which
+[jobs](#job) are able to place [allocations](#allocation) in a given set of
+nodes. Example use cases for node pools include segmenting nodes by environment
+(development, staging, production), by department (engineering, finance,
+support), or by functionality (databases, ingress proxy, applications).
+
+## Regions
+
+Nomad models infrastructure as regions and datacenters. A region will contain
+one or more datacenters. A set of servers joined together will represent a
+single region. Servers federate across regions to make Nomad globally aware.
+
+In federated clusters one of the regions must be defined as the [authoritative
+region](#authoritative-and-non-authoritative-regions).
+
+## Server
+
+Nomad servers are the brains of the cluster. There is a cluster of servers per
+region and they manage all jobs and clients, run evaluations, and create task
+allocations.  The servers replicate data between each other and perform leader
+election to ensure high availability. More information about latency
+requirements for servers can be found in [Network
+Topology](/nomad/docs/install/production/requirements#network-topology).
+
+## Task
+
+A Task is the smallest unit of work in Nomad. Tasks are executed by drivers,
+which allow Nomad to be flexible in the types of tasks it supports. Tasks
+specify their driver, configuration for the driver, constraints, and resources
+required.
+
+## Task Group
+
+A Task Group is a set of tasks that must be run together. For example, a web
+server may require that a log shipping co-process is always running as well. A
+task group is the unit of scheduling, meaning the entire group must run on the
+same client node and cannot be split.
+
+[`update`]: /nomad/docs/job-specification/update
diff --git a/content/nomad/v1.9.x/content/docs/index.mdx b/content/nomad/v1.9.x/content/docs/index.mdx
new file mode 100644
index 0000000000..33bf5f9203
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/index.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: Documentation
+description: |-
+  Nomad is a flexible workload orchestrator to deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run diverse workloads including Docker, non-containerized, microservice, and batch applications.
+---
+
+# Nomad Documentation
+
+Nomad is a flexible workload orchestrator to deploy and manage any containerized
+or legacy application using a single, unified workflow. Nomad can run diverse
+workloads including Docker, non-containerized, microservice, and batch
+applications.
+
+If you are just getting started with Nomad, refer to the [Getting
+Started tutorial collection][gs].
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+[gs]: /nomad/tutorials/get-started
diff --git a/content/nomad/v1.9.x/content/docs/install/index.mdx b/content/nomad/v1.9.x/content/docs/install/index.mdx
new file mode 100644
index 0000000000..bbeba80aca
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/install/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Install Nomad
+description: |-
+  Learn how to install Nomad on Linux, Mac, and Windows. Review Linux post-installation steps such as installing Container Network Interface (CNI) reference plugins, the consul-cni plugin, and the dmidecode tool. Configure bridge network traffic to route through iptables and verify cgroup controllers. Learn how to compile a Nomad binary from source code.
+---
+
+# Install Nomad
+
+Nomad is available as a pre-compiled binary or as a package for several
+operating systems. You can also [build Nomad from source](#from-source).
+
+-> If you are interested in trialing Nomad without installing it locally, see
+the [Quickstart](/nomad/docs/install/quickstart) for options to get started with
+Nomad.
+
+<Tabs>
+<Tab heading="Linux" group="linux">
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | \
+  sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" \
+| sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+Install `dnf config-manager` to manage your repositories.
+
+```shell-session
+$ sudo dnf install -y dnf-plugins-core
+```
+
+Use `dnf config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo dnf config-manager addrepo --from-repofile=https://rpm.releases.hashicorp.com/fedora/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo dnf -y install nomad
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager \
+  --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Mac" group="mac">
+
+<Tabs>
+<Tab heading="Homebrew" group="mac-homebrew">
+
+[Homebrew](https://brew.sh) is a free and open source package management system
+for Mac OS X. Install the official [Nomad
+formula](https://github.com/hashicorp/homebrew-tap) from the terminal.
+
+First, install the HashiCorp tap, a repository of all of the HashiCorp Homebrew
+packages.
+
+```shell-session
+$ brew tap hashicorp/tap
+```
+
+Now, install Nomad with `hashicorp/tap/nomad`.
+
+```shell-session
+$ brew install hashicorp/tap/nomad
+```
+
+-> This installs a signed binary and is automatically updated with
+every new official release.
+
+To update to the latest, run
+
+```shell-session
+$ brew upgrade hashicorp/tap/nomad
+```
+</Tab>
+<Tab heading="Manual" group="mac-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+<Tab heading="Windows" group="windows">
+
+<Tabs>
+<Tab heading="Chocolatey" group="windows-chocolatey">
+
+[Chocolatey](https://chocolatey.org/) is a free and open-source package
+management system for Windows. Install the [Nomad
+package](https://chocolatey.org/packages/nomad) from the command-line.
+
+```shell-session
+$ choco install nomad
+```
+
+-> Chocolatey and the Nomad package are **NOT** directly maintained
+by HashiCorp. The latest version of Nomad is always available by manual
+installation.
+
+</Tab>
+<Tab heading="Manual" group="windows-manual">
+
+@include 'install/manual-install.mdx'
+
+</Tab>
+</Tabs>
+
+</Tab>
+
+</Tabs>
+
+
+## Linux post-installation steps
+
+These steps are optional but can be helpful for running Nomad and to
+take advantage of additional Nomad functionalities.
+
+-> You need to run client agents as root (or with `sudo`) so that cpuset accounting and network namespaces work correctly.
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Install consul-cni plugin
+
+@include 'install/install-consul-cni-plugin.mdx'
+
+### Install dmidecode
+
+When running on a virtualized host such as Amazon EC2, Nomad makes use of the
+`dmidecode` tool to detect CPU performance data. Some Linux distributions
+require installing the dmidecode package manually.
+
+### Configure bridge network to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+### Verify cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+
+## Verify the installation
+
+To verify Nomad was installed correctly, try the `nomad` command.
+
+```shell-session
+$ nomad
+```
+
+You should see help output, similar to the following.
+
+```plaintext
+Usage: nomad [-version] [-help] [-autocomplete-(un)install] <command> [args]
+
+Common commands:
+    run         Run a new job or update an existing job
+    stop        Stop a running job
+    status      Display the status output for a resource
+    alloc       Interact with allocations
+    job         Interact with jobs
+    node        Interact with nodes
+    agent       Runs a Nomad agent
+
+Other commands:
+    acl                 Interact with ACL policies and tokens
+    agent-info          Display status information about the local agent
+    config              Interact with configurations
+    deployment          Interact with deployments
+    eval                Interact with evaluations
+    exec                Execute commands in task
+    fmt                 Rewrites Nomad config and job files to canonical format
+    license             Interact with Nomad Enterprise License
+    login               Login to Nomad using an auth method
+    monitor             Stream logs from a Nomad agent
+    namespace           Interact with namespaces
+    operator            Provides cluster-level tools for Nomad operators
+    plugin              Inspect plugins
+    quota               Interact with quotas
+    recommendation      Interact with the Nomad recommendation endpoint
+    scaling             Interact with the Nomad scaling endpoint
+    sentinel            Interact with Sentinel policies
+    server              Interact with servers
+    service             Interact with registered services
+    system              Interact with the system API
+    tls                 Generate Self Signed TLS Certificates for Nomad
+    ui                  Open the Nomad Web UI
+    var                 Interact with variables
+    version             Prints the Nomad version
+    volume              Interact with volumes
+```
+
+---
+
+## Compiling from source ((#from-source))
+
+To compile from source, you will need [Go](https://golang.org) installed at the
+version described by the [.go-version][go-version] file. You should properly
+configure your Go environment, including setting a `GOPATH` environment variable
+and ensuring `GOPATH/bin` is within your `PATH`. A copy of
+[`git`](https://www.git-scm.com/) is also needed in your `PATH`.
+
+1. Clone the Nomad repository from GitHub into your `GOPATH`:
+
+   ```shell-session
+   $ mkdir -p $GOPATH/src/github.com/hashicorp && cd $_
+   $ git clone https://github.com/hashicorp/nomad.git
+   $ cd nomad
+   ```
+
+1. Bootstrap the project. This will download and compile libraries and tools
+   needed to compile Nomad:
+
+   ```shell-session
+   $ make bootstrap
+   ```
+
+1. Build Nomad for your current system and put the
+   binary in `./bin/` (relative to the git checkout). The `make dev` target is
+   just a shortcut that builds `nomad` for only your local build environment (no
+   cross-compiled targets).
+
+   ```shell-session
+   $ make dev
+   ```
+
+[consul-dev]: /consul/tutorials/certification-associate-tutorials/get-started-agent#start-the-agent
+
+[consul-download]: /consul/downloads
+
+[destroy]: /vagrant/docs/cli/destroy
+
+[gh-7865]: https://github.com/hashicorp/nomad/issues/7865
+
+[gpg-key]: https://apt.releases.hashicorp.com/gpg "HashiCorp GPG key"
+[go-version]: https://github.com/hashicorp/nomad/blob/main/.go-version
+
diff --git a/content/nomad/v1.9.x/content/docs/install/production/index.mdx b/content/nomad/v1.9.x/content/docs/install/production/index.mdx
new file mode 100644
index 0000000000..1df72e142c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/install/production/index.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: Install Nomad in a production environment
+description: |-
+  This page contains a high-level overview of Nomad production installation and links review hardware requirements, reference architecture, a deployment guide, and configuration documentation.
+---
+
+# Install Nomad in a production environment
+
+While HashiCorp Nomad provides a low-friction practitioner experience out of
+the box, there are a few critical steps to take for a successful production
+Nomad deployment.
+
+## Explore the reference architecture and installation guide
+
+Learn more about recommended practices and explore a reference architecture for
+deploying HashiCorp Nomad in production.
+
+- [Nomad Reference Architecture][] - Learn recommended practices and a reference
+  architecture for Nomad production deployments. This reference architecture
+  conveys a general architecture. Adapt it to accommodate the specific needs
+  of your implementation.
+
+- [Nomad Deployment Guide][] - Follow along with an end-to-end outline of the
+  steps required to install a single production-ready Nomad cluster as defined
+  in the Reference Architecture section.
+
+## Verify hardware requirements
+
+Review the recommended machine resources (instances), port requirements, and
+network topology for Nomad in the [Hardware Requirements](/nomad/docs/install/production/requirements).
+
+## Install Nomad
+
+Visit the [Install Nomad](/nomad/docs/install) page to learn the options
+available for installing Nomad and how to verify a successful
+installation.
+
+## Configure your Nomad servers and clients
+
+Refer to the [Set Server & Client Nodes](/nomad/docs/operations/nomad-agent)
+and [Nomad Agent documentation](/nomad/docs/commands/agent) pages to learn about the
+Nomad agent process and how to configure the server and client nodes in your
+cluster.
+
+[nomad reference architecture]: /nomad/tutorials/enterprise/production-reference-architecture-vm-with-consul
+[nomad deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul
diff --git a/content/nomad/v1.9.x/content/docs/install/production/requirements.mdx b/content/nomad/v1.9.x/content/docs/install/production/requirements.mdx
new file mode 100644
index 0000000000..58c2fa4195
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/install/production/requirements.mdx
@@ -0,0 +1,224 @@
+---
+layout: docs
+page_title: Nomad installation requirements
+description: |-
+  Learn about the hardware and networking resources that Nomad requires. Review RAM, CPU, network topology and ports, user permissions, and Linux capabilities.
+---
+
+# Nomad installation requirements
+
+This page contains an overview of the hardware and networking resources that
+Nomad requires. Review RAM, CPU, network topology and ports, user
+permissions, and Linux capabilities.
+
+## Resources
+
+**Nomad servers** may need to be run on large machine instances. We suggest
+having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of **fast** disk and
+significant network bandwidth. The core count and network recommendations are to
+ensure high throughput as Nomad heavily relies on network communication and as
+the Servers are managing all the nodes in the region and performing scheduling.
+The memory and disk requirements are due to the fact that Nomad stores all state
+in memory and will store two snapshots of this data onto disk, which causes high IO in busy clusters with lots of writes. Thus disk should
+be at least 2 times the memory available to the server when deploying a high
+load cluster. When running on AWS prefer NVME or Provisioned IOPS SSD storage for data dir.
+
+These recommendations are guidelines and operators should always monitor the
+resource usage of Nomad to determine if the machines are under or over-sized.
+
+**Nomad clients** support reserving resources on the node that should not be
+used by Nomad. This should be used to target a specific resource utilization per
+node and to reserve resources for applications running outside of Nomad's
+supervision such as Consul and the operating system itself.
+
+Please see the [reservation configuration](/nomad/docs/configuration/client#reserved) for
+more detail.
+
+## Network topology
+
+**Nomad servers** are expected to have sub 10 millisecond network latencies
+between each other to ensure liveness and high throughput scheduling. Nomad
+servers can be spread across multiple datacenters if they have low latency
+connections between them to achieve high availability.
+
+For example, on AWS every region comprises of multiple zones which have very low
+latency links between them, so every zone can be modeled as a Nomad datacenter
+and every Zone can have a single Nomad server which could be connected to form a
+quorum and a region.
+
+Nomad servers uses Raft for state replication and Raft being highly consistent
+needs a quorum of servers to function, therefore we recommend running an odd
+number of Nomad servers in a region. Usually running 3-5 servers in a region is
+recommended. The cluster can withstand a failure of one server in a cluster of
+three servers and two failures in a cluster of five servers. Adding more servers
+to the quorum adds more time to replicate state and hence throughput decreases
+so we don't recommend having more than seven servers in a region.
+
+**Nomad clients** do not have the same latency requirements as servers since they
+are not participating in Raft. Thus clients can have 100+ millisecond latency to
+their servers. This allows having a set of Nomad servers that service clients
+that can be spread geographically over a continent or even the world in the case
+of having a single "global" region and many datacenter.
+
+Nomad clients make connections to servers on the RPC port and then maintain a
+persistent TCP connection. The server and client use this TCP connection for
+two-way communication. As a result, clients that are geographically distributed
+from the servers do not need to have publicly routable IP addresses in order
+to communicate with the servers (although the workloads running on the clients
+may need public IPs). All connections between Nomad servers and between clients
+and servers must be secured with [mTLS][].
+
+Nomad clients are typically not required to be reachable from each other unless
+your workloads need to communicate with each other. The optional [ephemeral disk
+migration][] field is one exception, and requires that clients can reach each
+other on their HTTP ports.
+
+## Ports used
+
+Nomad requires 3 different ports to work properly on servers and 2 on clients,
+some on TCP, UDP, or both protocols. Below we document the requirements for each
+port. If you use a firewall of any type, you must ensure that it is configured to
+allow the following traffic.
+
+- HTTP API (Default 4646). This is used by clients and servers to serve the HTTP
+  API. TCP only.
+
+- RPC (Default 4647). This is used for internal RPC communication between client
+  agents and servers, and for inter-server traffic. TCP only.
+
+- Serf WAN (Default 4648). This is used by servers to gossip both over the LAN and
+  WAN to other servers. It isn't required that Nomad clients can reach this address.
+  TCP and UDP.
+
+When tasks ask for dynamic ports, they are allocated out of the port range
+between 20,000 and 32,000. This is well under the ephemeral port range suggested
+by the [IANA](https://en.wikipedia.org/wiki/Ephemeral_port). If your operating
+system's default ephemeral port range overlaps with Nomad's dynamic port range,
+you should tune the OS to avoid this overlap.
+
+On Linux this can be checked and set as follows:
+
+```shell-session
+$ cat /proc/sys/net/ipv4/ip_local_port_range
+32768   60999
+$ echo "49152 65535" > /proc/sys/net/ipv4/ip_local_port_range
+```
+
+## Bridge networking and `iptables`
+
+@include 'install/bridge-iptables.mdx'
+
+## Cgroup controllers
+
+@include 'install/cgroup-controllers.mdx'
+
+## Hardening Nomad
+
+As noted in the [Security Model][] guide, Nomad is not **secure-by-default**.
+
+### User permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges. If you
+are installing Nomad from the official Linux packages, the systemd unit file
+runs Nomad as `root`. For your server nodes you should change this to a
+minimally privileged `nomad` user. See the [production deployment guide][] for
+details.
+
+Nomad clients must be run as `root` due to the OS isolation mechanisms that
+require root privileges (see also [Linux Capabilities][] below). The Nomad
+client's data directory should be owned by `root` with filesystem permissions
+set to `0700`.
+
+### Linux capabilities
+
+On Linux, Nomad clients require privileged capabilities for isolating
+tasks. Nomad clients require `CAP_SYS_ADMIN` for creating the tmpfs used for
+secrets, bind-mounting task directories, mounting volumes, and running some task
+driver plugins. Nomad clients require `CAP_NET_ADMIN` for a variety of tasks to
+set up networking. You should run Nomad clients as `root`, but running as `root`
+does not grant these required capabilities if Nomad is running in a user
+namespace. Running Nomad clients inside a user namespace is unsupported. See the
+[`capabilities(7)`][] man page for details on Linux capabilities.
+
+In order to run a task, Nomad clients perform privileged operations normally
+reserved to the `root` user:
+
+* Mounting tmpfs file systems for the task `/secrets` directory.
+* Creating the network bridge for `bridge` networking.
+* Allowing inbound and outbound network traffic to the workload (typically via
+  `iptables`).
+* Starting tasks as a specific `user`.
+* Setting the owner of `template` outputs.
+
+On Linux this set of requirements expands to:
+
+* Configuring resource isolation via cgroups.
+* Configuring namespace isolation: `mount`, `user`, `pid`, `ipc`, and `network`
+  namespaces.
+
+Nomad task drivers that support bind-mounting volumes also need to run as `root`
+to do so. This includes the built-in `exec` and `java` task drivers. The
+built-in task drivers run in the same process as the Nomad client, so this
+requires that the Nomad client agent is also running as `root`.
+
+### Rootless Nomad clients
+
+Although it's possible to run a Nomad client agent as a non-root user or as
+`root` in a user namespace, to perform the privileged operations described above
+you also need to grant the client agent `CAP_SYS_ADMIN` and `CAP_NET_ADMIN`
+capabilities. Note that these capabilities are nearly functionally equivalent to
+running as `root` and that a process running with `CAP_SYS_ADMIN` can almost
+always escalate itself to "true" (unnamespaced) `root`.
+
+Some task drivers delegate many of their privileged operations to an external
+process such as `dockerd` or `podman`. If you don't need `bridge` networking and
+are using these task drivers or custom task drivers, you may be able to run
+Nomad client agents as a non-root user with the following additional
+configuration:
+
+* Delegated cgroups: to safely set cgroups as an unprivileged user requires
+  cgroups v2.
+* User namespaces: on some distros this may require setting sysctls like
+  `kernel.unprivileged_userns_clone=1`
+* The task driver engine (ex. `dockerd`, `podman`, `containerd`, etc) must be
+  configured for rootless operation. This requires cgroups v2, user namespaces,
+  and typically either a patched kernel or kernel module (ex. `overlay.ko`)
+  allowing unprivileged [overlay filesystem][] or a FUSE overlay filesystem.
+
+This is not a supported or well-tested configuration. See [GH-13669][] for a
+further discussion and to provide feedback on your experiences trying to run
+rootless Nomad clients.
+
+## Running Nomad in Docker
+
+Running systems as Docker containers has become a common practice. While it's
+possible to run Nomad servers inside containers, Nomad clients require
+extensive access to the underlying host machine, as described in
+[Rootless Nomad Clients][]. Docker containers introduce a non-trivial
+abstraction layer that makes it hard to properly configure clients and task
+drivers therefore **running Nomad clients in Docker containers is not
+officially supported**.
+
+The [`hashicorp/nomad`][nomad_docker_hub] Docker image is intended to be used
+in automated pipelines for [CLI operations][docs_cli], such as
+[`nomad job plan`][], [`nomad fmt`][], and others.
+
+~> **Note:** The Nomad Docker image is not tested when running as an agent.
+
+[Security Model]: /nomad/docs/concepts/security
+[production deployment guide]: /nomad/tutorials/enterprise/production-deployment-guide-vm-with-consul#configure-systemd
+[linux capabilities]: #linux-capabilities
+[`capabilities(7)`]: https://man7.org/linux/man-pages/man7/capabilities.7.html
+[overlay filesystem]: https://www.kernel.org/doc/html/latest/filesystems/overlayfs.html
+[GH-13669]: https://github.com/hashicorp/nomad/issues/13669
+[Rootless Nomad Clients]: #rootless-nomad-clients
+[nomad_docker_hub]: https://hub.docker.com/r/hashicorp/nomad
+[docs_cli]: /nomad/docs/commands
+[`nomad job plan`]: /nomad/docs/commands/job/plan
+[`nomad fmt`]: /nomad/docs/commands/fmt
+[mTLS]: /nomad/tutorials/transport-security/security-enable-tls
+[ephemeral disk migration]: /nomad/docs/job-specification/ephemeral_disk#migrat
diff --git a/content/nomad/v1.9.x/content/docs/install/quickstart.mdx b/content/nomad/v1.9.x/content/docs/install/quickstart.mdx
new file mode 100644
index 0000000000..3badee309b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/install/quickstart.mdx
@@ -0,0 +1,83 @@
+---
+layout: docs
+page_title: Nomad quickstart
+description: |-
+  The Nomad quickstart page contains links to resources that show you how to get started using Nomad locally or in a cloud environment.
+---
+
+# Nomad quickstart
+
+These installations are designed to get you started with Nomad and should
+be used only for experimentation purposes. If you are looking to install Nomad
+in production, refer to the [Production Installation
+guide](/nomad/docs/install/production).
+
+## Nomad tutorials
+
+We recommend these tutorials, which provision a Nomad cluster for you.
+
+- [Get Started][]: Get up and running with Nomad by learning about scheduling,
+  setting up a cluster, and deploying an example job. Create a Nomad cluster
+  on your local machine or in an AWS, Azure, or Google Cloud Platform (GCP)
+  cloud environment. This tutorial series has an associated code repository so
+  you can review the Terraform provisioning scripts and Nomad job specifications.
+- [Cluster Setup][]: Provision a Nomad cluster on AWS, Azure, or GCP. Enable
+  Consul and access control lists (ACLs). This tutorial series has an associated
+  code repository so you can review the Terraform provisioning scripts.
+- [Enable gossip encryption for Nomad][interactive]: Launch an interactive lab
+  to use Nomad in your browser.
+
+## Cloud installation
+
+The Nomad repository contains guides and Terraform scripts for provisioning a
+Nomad sandbox environment on AWS, Azure, or GCP with Consul and Vault. You can
+explore Nomad and its integrations with the HashiCorp stack.
+
+- [Provision a Nomad cluster on AWS][]
+- [Provision a Nomad cluster on Azure][]
+- [Provision a Nomad cluster on GCP][]
+
+## Local installation
+
+Use one of the following methods to run a local Nomad sandbox environment:
+
+- Install a binary
+
+  Refer to the [Install Nomad guide][installing-binary] to install the latest
+  Nomad release binary.
+
+  Run Nomad with the `sudo nomad agent -dev` [command][agent-dev], which
+  starts the Nomad agent in development mode.
+
+  If you are using Docker Desktop for Windows or MacOS, refer to [How to connect
+  to my host network when using Docker Desktop (Windows and MacOS)][faq-win-mac]
+  for instructions on binding Nomad to a non-loopback network interface.
+
+- Use Vagrant and VirtualBox
+
+  This option requires AMD hardware.
+
+  The Nomad repository contains a Vagrantfile. Refer to the [Developing with
+  Vagrant section][vagrant] of the [Nomad Codebase
+  Documentation][compile-source] file for instructions.
+
+- Compile and run from source
+
+  This option requires software engineering experience and a workstation set up
+  for Go, Node, and Docker development.
+
+  Refer to the Nomad repository's [Nomad Codebase Documentation][compile-source]
+  file for details.
+
+[faq-win-mac]: /nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos
+[installing-binary]: /nomad/docs/install#precompiled-binaries
+[Get Started]: /nomad/tutorials/get-started
+[Cluster Setup]: /nomad/tutorials/cluster-setup
+[interactive]: /nomad/tutorials/interactive/security-gossip-encryption
+[Provision a Nomad cluster on AWS]: https://github.com/hashicorp/nomad/blob/main/terraform/aws/README.md
+[Provision a Nomad cluster on Azure]:
+    https://github.com/hashicorp/nomad/blob/main/terraform/azure/README.md
+[Provision a Nomad cluster on GCP]: https://github.com/hashicorp/nomad/blob/main/terraform/gcp/README.md
+[agent-dev]: /nomad/docs/commands/agent#dev
+[vagrant]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md#developing-with-vagrant
+[compile-source]: https://github.com/hashicorp/nomad/blob/main/contributing/README.md
diff --git a/content/nomad/v1.9.x/content/docs/install/windows-service.mdx b/content/nomad/v1.9.x/content/docs/install/windows-service.mdx
new file mode 100644
index 0000000000..1b8fa6eac4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/install/windows-service.mdx
@@ -0,0 +1,95 @@
+---
+layout: docs
+page_title: Install Nomad as a Windows service
+description: |-
+  Learn how to run Nomad as a Windows service. Register Nomad with the Windows Service Control Manager. Configure Nomad to log to file, and increase the non-interactive desktop heap size.
+---
+
+# Install Nomad as a Windows service
+
+Nomad can be run as a native Windows service. In order to do this, you will need
+to register the Nomad application with the Windows Service Control Manager using
+[`sc.exe`], configure Nomad to log to a file, and then start the Nomad service.
+
+~> **Note:** These steps should be run in a PowerShell session with Administrator
+capabilities.
+
+## Register Nomad with Windows
+
+[Download] the Nomad binary for your architecture.
+
+Use the [`sc.exe`] command to create a Service named "Nomad". The binPath
+argument should include the fully qualified path to the Nomad executable and any
+arguments to the nomad command: agent, -config, etc.
+
+```plaintext
+sc.exe create "Nomad" binPath="«full path to nomad.exe» agent -config=«path to config file or directory»" start= auto
+[SC] CreateService SUCCESS
+```
+
+If you receive a success message, your service is registered with the service
+manager.
+
+If you get an error, please verify the path to the binary and check the
+arguments, by running the contents of `binPath` directly in a PowerShell session
+and observing the results.
+
+## Configure Nomad to log to file
+
+Because Windows services run non-interactively and Nomad does not log to the
+Windows Event Viewer, you will need to configure file-based logging in Nomad.
+
+To do this, set the [`log_file`][logging] argument in your Nomad configuration
+file or in the binPath argument of the [`sc.exe`] command used to register the
+service.
+
+## Start the Nomad service
+
+You have two ways to start the service.
+
+- Go to the Windows Service Manager, and look for **Nomad** in the service name
+  column. Click the _Start_ button to start the service.
+
+- Using the [`sc.exe`] command:
+
+  ```plaintext
+  sc.exe start "Nomad"
+
+  SERVICE_NAME: Nomad
+        TYPE               : 10  WIN32_OWN_PROCESS
+        STATE              : 4  RUNNING
+                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
+        WIN32_EXIT_CODE    : 0  (0x0)
+        SERVICE_EXIT_CODE  : 0  (0x0)
+        CHECKPOINT         : 0x0
+        WAIT_HINT          : 0x0
+        PID                : 8008
+        FLAGS              :
+  ```
+
+The service automatically starts up during/after boot, so you don't need to
+launch Nomad from the command-line again.
+
+## Increase the non-interactive desktop heap size
+
+If you run Nomad as a Windows service and you intend to run many allocations,
+such as more than 50, you may encounter issues with Windows terminating Nomad
+plugin processes with errors such as `exit status 0xc0000142` appearing in the
+logs. This is due to Nomad's inability to spawn more concurrent processes, and
+you may fix this by manipulating the value of
+`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
+Manager\SubSystems` Windows registry key.
+
+This key has a `Windows` value which in turn has a `SharedSection` parameter
+that accepts a value of three comma-separated integers, for example,
+`1024,20480,768`. The first integer indicates the maximum size of the
+system-wide heap, the second is the size of each desktop heap, and the third is
+the size of the desktop heap that is associated with a noninteractive Windows
+instance. All values are in kilobytes. For large Windows nodes that run large
+numbers of allocations, we recommend setting the final integer value to 2048 or
+4096 kB. Remember that any registry change requires restarting Windows, a
+restart of Nomad service is not sufficient.
+
+[`sc.exe`]: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682107(v=vs.85).aspx
+[download]: /nomad/downloads
+[logging]: /nomad/docs/configuration#log_file
diff --git a/content/nomad/v1.9.x/content/docs/integrations/consul/acl.mdx b/content/nomad/v1.9.x/content/docs/integrations/consul/acl.mdx
new file mode 100644
index 0000000000..c00b817748
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/consul/acl.mdx
@@ -0,0 +1,473 @@
+---
+layout: docs
+page_title: Integrate Consul access control list (ACL)
+description: |-
+  Learn how to integrate Consul access control list (ACL) with Nomad workload identity. Learn how to migrate to using Nomad workload identity with Consul. Configure Consul so it can receive, validate, and trust workload identities from Nomad. Create binding and namespace rules. Review considerations for using the JSON Web Key Set (JWKS) URL.
+---
+
+# Integrate Consul access control list (ACL)
+
+The [Consul ACL][consul_acls] system protects the cluster from unauthorized
+access. When enabled, both Consul and Nomad must be properly configured in
+order for their integrations to work.
+
+Nomad agents must be configured with their own Consul ACL token, and Consul
+must be configured to accept workload identities from tasks and services
+running in Nomad.
+
+## Nomad Agents
+
+Nomad agents need access to Consul in order to register themselves in the
+service catalog and discover other Nomad agents via service discovery for
+automatic clustering. Nomad clients use Consul tokens from Workload Identity to
+register services and checks but need permissions on their own token to
+deregister. Nomad servers also create [configuration
+entries][consul_config_entry] for Consul Service Mesh, so the specific
+permissions vary slightly between Nomad servers and clients. The following
+Consul ACL policies represent the minimal permissions Nomad servers and clients
+need.
+
+<Tabs>
+<Tab heading="Nomad Servers">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+
+acl  = "write"
+mesh = "write"
+```
+
+</Tab>
+<Tab heading="Nomad Clients">
+
+```hcl
+agent_prefix "" {
+  policy = "read"
+}
+
+node_prefix "" {
+  policy = "write"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+</Tab>
+</Tabs>
+
+## Nomad Workload Identities
+
+Starting in Nomad 1.7, Nomad clients can use a task or service's [Workload
+Identity][nomad_wid] to authenticate to Consul and obtain an ACL token specific
+to the service or task. When using Nomad workload identities, you no longer
+need to pass in a Consul ACL token to submit a job.
+
+By default, Nomad does not generate workload identities for services, and tasks
+only receive an identity that can be used to access data from Nomad itself,
+such as for reading [Variables][] from a [`template`][] block. To access
+Consul, jobs must have additional workload identities defined as [`identity`][]
+blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure Nomad servers with the [`consul.service_identity`][] and
+[`consul.task_identity`][] agent configuration. Upon job registration, the
+Nomad servers update tasks that have a [`consul`][] or [`template`][] block and
+services that use the Consul service provider with these default identities.
+
+You can also specify identities for Consul directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Consul][jobspec_identity_consul] section of the `identity` block
+documentation for more information.
+
+### Configuring Consul Authentication
+
+You must configure Consul so it can receive, validate, and trust workload
+identities from Nomad. Since they are encoded as [JSON Web Tokens (JWTs)][jwt],
+you must create a [JWT ACL auth method][consul_jwt_auth_method]. The auth
+method is an endpoint that Nomad can use to exchange workload identities for
+Consul ACL tokens.
+
+Refer to Consul's [Auth Methods Overview][consul_auth_methods] documentation
+for more information.
+
+#### Consul Auth Method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Consul servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Consul is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+Nomad cannot recreate Consul tokens that have been deleted. The auth method
+configuration should never set the `MaxTokenTTL` field. Consul tokens are
+local to the Consul datacenter unless you set `TokenLocality: "global"` in the
+auth method. We recommend using local tokens, which is the default. Global tokens
+require that the primary Consul datacenter is available when allocations start.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+The `JWKSURL` address must be reachable by all Consul servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `JWKSURL` value.
+
+[![Consul Auth Method][img_consul_auth_method]][img_consul_auth_method]
+
+When an allocation that needs access to Consul starts, the Nomad client running
+it exchanges the Nomad workload identities for tasks and services for Consul
+ACL tokens.
+
+[![Consul JWT Login][img_consul_wid_acl_token]][img_consul_wid_acl_token]
+
+The auth method also defines the list of authorized audience values, which must
+have at least one match with the values defined in the Nomad workload identity
+[`aud`][] parameter. For security reasons, it is recommended to only define a
+single audience value.
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced as dynamic values in Consul ACL configuration. The auth method
+determines which of these claims are made available to the rest of the
+configuration.
+
+<CodeBlockConfig highlight="6-9" filename="auth-method.json">
+
+```json
+{
+  "JWKSURL": "http://nomad.example.com:4646/.well-known/jwks.json",
+  "JWTSupportedAlgs": ["RS256"],
+  "BoundAudiences": ["consul.io"],
+  "ClaimMappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task",
+    "nomad_service": "nomad_service"
+  }
+}
+```
+
+</CodeBlockConfig>
+
+#### Consul Binding Rules
+
+Consul auth methods use [binding rules][consul_binding_rules] to determine the
+set of policies applied to the generated ACL token. Nomad workload identities
+can be used in Consul for two main purpose: registering services and retrieving
+configuration values and service addresses from Consul using `template` blocks
+in tasks. Each purpose requires tokens with different permissions so Nomad
+requires two binding rules.
+
+The first binding rule associates the Consul ACL token with a [service
+identity][consul_si], allowing the token to register and manage the lifecyle of
+a given service. This binding rule is only applied to Nomad workload identities
+for services because they are the only ones that have a `nomad_service` claim.
+
+```shell-session
+$ consul acl binding-rule create \
+    -method 'nomad-workloads' \
+    -bind-type 'service' \
+    -bind-name '${value.nomad_service}' \
+    -selector '"nomad_service" in value'
+```
+
+The [`-bind-name`][] flag restricts the token to only be able to modify
+services with the same name as the one defined in the Nomad workload identity
+claim. The [`-selector`][] flag ensures this binding rule only applies to
+workload identities for services.
+
+The second binding rule associates the Consul ACL token with an [ACL
+role][consul_acl_role], which is a collection of [ACL
+policies][consul_acl_policy] that define what the token is authorized to do.
+This binding rule is applied to Nomad workload identities for tasks to access
+information from Consul. The exact ACL policy rules will depend on the level of
+access required by the tasks (typically, accessing service addresses and KV with
+[`template`][] blocks).
+
+```shell-session
+$ consul acl binding-rule create \
+  -method 'nomad-workloads' \
+  -bind-type 'role' \
+  -bind-name 'nomad-tasks-${value.nomad_namespace}' \
+  -selector '"nomad_service" not in value'
+```
+
+The `-bind-name` flag defines which role is used for the token. It may
+reference claim values from the Nomad workload identity to apply different
+roles to different tasks. Similarly to the binding rule for services, the
+`-selector` flag ensures this binding rule only applies to workload identities
+for tasks since they don't have the `nomad_service` claim.
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Consul Auth Overview][img_consul_auth]][img_consul_auth]
+
+The [`consul.service_auth_method`][] and [`consul.task_auth_method`][]
+configuration define the auth method used by Nomad to retrieve Consul ACL
+tokens for services and tasks.
+
+By default, they follow the structure described above and use a single auth
+method for both, but it is possible to use two different auth methods, provided
+the resulting Consul ACL token from each have the expected service identity and
+role applied.
+
+#### Consul Namespace Rules <EnterpriseAlert inline />
+
+Consul Enterprise supports multiple namespaces and Nomad Enterprise allows jobs
+to use the [`consul.namespace`][] parameter to register services and read KV
+data from different Consul namespaces.
+
+In a multi-namespace environment, you should create the auth method and binding
+rules in the `default` namespace and configure the auth method with a set of
+[`NamespaceRules`][].
+
+```shell-session
+$ consul acl auth-method create \
+  -name 'nomad-workloads' \
+  -type 'jwt' \
+  -config '@auth-method.json' \
+  -namespace-rule-selector '"consul_namespace" in value' \
+  -namespace-rule-bind-namespace '${value.consul_namespace}'
+```
+
+Similarly to binding rules, namespace rules have a [`Selector`][] expression to
+determine when the rule should be applied and a [`BindNamespace`][] value that
+defines the namespace used.
+
+Auth methods with a namespace rule create Consul tokens in that Consul
+namespace. Binding rules with `-bind-type role` also target a role and
+associated policies in that same Consul namespace. So you should create the
+auth method and binding rules in the default namespace, and the role and
+policies in the target namespaces.
+
+In Nomad Enterprise, workload identities for tasks and services placed within
+the scope of a `consul` block with a `namespace` value, have an additional
+claim called `consul_namespace` that represents the Consul namespace defined
+in Nomad for the workload.
+
+<CodeBlockConfig highlight="9-11" filename="example.nomad.hcl">
+
+```hcl
+job "example" {
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    consul {
+      namespace = "prod"
+    }
+
+    service {
+      port     = "db"
+      name     = "redis"
+      provider = "consul"
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+
+If a `consul` block is not defined, then the workload identity will not have
+the `consul_namespace` claim, since Nomad is not able to determine which Consul
+namespace will be used.
+
+Refer to the [Consul Namespaces][int_consul_ns] section for more information.
+
+### Important Considerations About the JWKS URL
+
+The recommended configuration assumes Consul servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Consul and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Consul auth method.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Consul Servers Not Able to Connect to Nomad
+
+If the Consul servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`JWTValidationPubKeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Consul servers, and use that address as the value for
+`JWKSURL`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional References
+
+The [Consul ACL with Nomad Workload Identities][consul_tutorial_wid] tutorial
+provides guided instructions on how to configure Consul and Nomad for workload
+identities.
+
+The [`nomad setup consul`][nomad_cli_setup_consul] command and the
+[`hashicorp-modules/nomad-setup/consul`][tf_nomad_setup_consul] Terraform
+module can help you automate the process of applying configuration to a Consul
+cluster.
+
+## Authenticating Without Workload Identity (Legacy)
+
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`][]
+configuration parameter will control whether a Consul token will be required
+when submitting a job with Consul namespace configured. The provided Consul
+token must belong to the correct namespace, and must be backed by a Consul ACL
+Policy with sufficient `service:write` and `kv:read` permissions. An example
+policy might look like the following.
+
+```hcl
+key_prefix "" {
+  policy = "read"
+}
+
+service_prefix "" {
+  policy = "write"
+}
+```
+
+<Note title="Admin Partitions">
+
+This legacy workflow is not compatible with [Consul Admin
+Partitions](/consul/docs/enterprise/admin-partitions). If you
+are using Admin Partitions, you must use [Nomad Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+<Note title="Deprecation Warning">
+
+This legacy workflow was removed in Nomad 1.10. Before upgrading to Nomad 1.10,
+you need to configure authentication with Consul as described in
+[Nomad Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+## Migrating to Using Workload Identity with Consul
+
+Migrating from the legacy (pre-1.7) workflow where workload use the agent's
+Consul token requires configuation on your Consul cluster and your Nomad server
+agents. It does not require updating your running Nomad jobs. To migrate:
+
+* Create the Consul auth method and binding rules on your Consul cluster.
+* Enable [`consul.service_identity`][] blocks in your Nomad server agent configurations.
+* Enable [`consul.task_identity`][] blocks in your Nomad server agent configurations.
+* (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+  different identity because of how your auth method and binding rules are
+  configured.
+
+Note that when using Workload Identity you will no longer need to pass in a
+Consul token to submit a job.
+
+[Variables]: /nomad/docs/concepts/variables
+[`-bind-name`]: /consul/commands/acl/binding-rule/create#bind-name
+[`-selector`]: /consul/commands/acl/binding-rule/create#selector
+[`BindNamespace`]: /consul/api-docs/acl/auth-methods#bindnamespace
+[`JWTValidationPubKeys`]: /consul/docs/security/acl/auth-methods/jwt#jwtvalidationpubkeys
+[`NamespaceRules`]: /consul/api-docs/acl/auth-methods#namespacerules
+[`Selector`]: /consul/api-docs/acl/auth-methods#selector
+[`allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`consul.namespace`]: /nomad/docs/job-specification/consul#namespace
+[`consul.service_auth_method`]: /nomad/docs/configuration/consul#service_auth_method
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_auth_method`]: /nomad/docs/configuration/consul#task_auth_method
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`identity`]: /nomad/docs/job-specification/identity
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[consul_acl_policy]: /consul/docs/security/acl/acl-policies
+[consul_acl_role]: /consul/docs/security/acl/acl-roles
+[consul_acls]: /consul/docs/security/acl
+[consul_auth_methods]: /consul/docs/security/acl/auth-methods
+[consul_binding_rules]: /consul/api-docs/acl/binding-rules
+[consul_config_entry]: /consul/docs/connect/config-entries
+[consul_jwt_auth_method]: /consul/docs/security/acl/auth-methods/jwt
+[consul_si]: /consul/docs/security/acl/acl-roles#service-identities
+[consul_tutorial_wid]: /nomad/tutorials/integrate-consul/consul-acl
+[img_consul_auth]: /img/consul-integration-wi.png
+[img_consul_auth_method]: /img/consul-integration-auth-method.png
+[img_consul_wid_acl_token]: /img/consul-integration-wid-acl-token.png
+[int_consul_ns]: /nomad/docs/integrations/consul#consul-namespaces
+[jobspec_identity_consul]: /nomad/docs/job-specification/identity#workload-identities-for-consul
+[jwt]: https://jwt.io/
+[nomad_cli_setup_consul]: /nomad/docs/commands/setup/consul
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid]: /nomad/docs/concepts/workload-identity
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_consul]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/consul/
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
diff --git a/content/nomad/v1.9.x/content/docs/integrations/consul/index.mdx b/content/nomad/v1.9.x/content/docs/integrations/consul/index.mdx
new file mode 100644
index 0000000000..1b5a3aa6d8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/consul/index.mdx
@@ -0,0 +1,201 @@
+---
+layout: docs
+page_title: Consul integration
+description: |-
+  Integrate Consul with Nomad to use Consul features such as automatic clustering, service discovery, service mesh, Consul Template, Consul DNS, Consul ACL, and Consul namespaces with your Nomad clusters and workloads.
+---
+
+# Consul integration
+
+[Consul][] is a tool for discovering and configuring services in your
+infrastructure. Consul's key features include service discovery, health checking,
+a KV store, and robust support for multi-datacenter deployments. Nomad's integration
+with Consul enables automatic clustering, built-in service registration, and
+dynamic rendering of configuration files and environment variables. The sections
+below describe the integration in more detail.
+
+## Configuration
+
+In order to use Consul with Nomad, you will need to configure and install Consul
+on your nodes alongside Nomad, or schedule it as a system job. Nomad does not
+run Consul for you.
+
+To enable Consul integration, please refer to the [Nomad agent Consul
+configuration][] documentation.
+
+## Automatic clustering with Consul
+
+Nomad servers and clients will be automatically informed of each other's
+existence when a running Consul cluster already exists and the Consul agent is
+installed and configured on each host. Please refer to the [Automatic Clustering
+with Consul][] guide for more information.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your
+cluster. Nomad integrates with Consul to provide service discovery and
+monitoring.
+
+To configure a job to register with service discovery, please refer to the
+[`service` job specification documentation][service].
+
+## Service mesh
+
+Consul service mesh provides service-to-service connection authorization and
+encryption using mutual Transport Layer Security (TLS). Nomad can automatically
+provision the components necessary to securely connect your tasks to Consul's
+service mesh.
+
+Refer to the [Consul Service Mesh integration page][int_consul_mesh] for more
+information.
+
+## Dynamic configuration
+
+Nomad's job specification includes a [`template`][] block that uses a Consul
+ecosystem tool called [Consul Template][]. This mechanism creates a convenient
+way to ship configuration files that are populated from environment variables,
+Consul data, Vault secrets, or just general configurations within a Nomad task.
+
+For more information on Nomad's template block and how it leverages Consul
+Template, please see the [`template` job specification documentation][].
+
+## DNS
+
+To provide Consul DNS to Nomad workloads using [bridge or CNI networking
+mode][], you will need to configure Consul's DNS listener to be exposed to the
+workload network namespace, or configure `systemd-resolved`, `dnsmasq`, or
+similar DNS stub resolvers to forward DNS. See [Forward DNS for Consul service
+discovery][] for details.
+
+You can avoid exposing the Consul agent on a public IP by setting the Consul
+`bind_addr` to bind on a private IP address (the default is to use the
+`client_addr`). You will also need to either have Consul bind to port 53 for
+DNS if you are not using DNS forwarding.
+
+You will also need to set the [nameserver][] to the address. This address is
+exposed as the `consul.dns.addr` node attribute or the `DNSStubListener`
+configuration value for `systemd-resolved`.
+
+An simpler solution is to use Consul Connect [transparent proxy][] mode to
+automatically configure tasks to use Consul DNS.
+
+## Consul access control list (ACL)
+
+The Consul ACL system protects the cluster from unauthorized access. When
+enabled, both Consul and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Consul ACL integration page][int_consul_acl] for more
+information.
+
+## Consul namespaces <EnterpriseAlert inline/>
+
+Nomad provides integration with [Consul Namespaces][consul_namespaces] for
+service registrations specified in `service` blocks and Consul KV reads in
+`template` blocks.
+
+By default, Nomad will not specify a Consul namespace on service registrations
+or KV store reads, which Consul then implicitly resolves to the `"default"`
+namespace.  This default namespace behavior can be modified by setting the
+[`namespace`][consul_agent_namespace] field in the Nomad agent Consul
+configuration block.
+
+For more control over Consul namespaces, Nomad Enterprise supports configuring
+the Consul [namespace][consul_jobspec_namespace] at the group or task level in
+the Nomad job spec as well as the [`-consul-namespace`][consul_run_namespace]
+command line argument for `job run`.
+
+The Consul namespace used for a set of group or task service registrations
+within a group, as well as `template` KV store access is determined from the
+following hierarchy from highest to lowest precedence:
+
+* group and task configuration: Consul
+  [namespace field][consul_jobspec_namespace] defined in the job at the task or
+  group level.
+
+* job run command option: Consul namespace defined in the
+  [`-consul-namespace`][consul_run_namespace] command line option on job
+  submission.
+
+* job run command environment various: Consul namespace defined as the
+  [`CONSUL_NAMESPACE`][consul_env_namespace] environment variable on job
+  submission.
+
+* agent configuration: Consul namespace defined in the
+  [`namespace`][consul_agent_namespace] Nomad agent Consul configuration
+  parameter.
+
+* Consul default: If no Consul namespace options are configured, Consul will
+  automatically make use of the `"default"` namespace.
+
+## Multiple Consul clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Consul clusters. They can be
+configured using multiple [`consul`][nomad_config_consul] blocks with different
+`name` values. If a `name` is not provided, the cluster configuration is called
+`default`. Nomad automatic clustering uses the `default` cluster for service
+discovery.
+
+Jobs that need access to Consul may specify which Consul cluster to use with
+the [`consul.cluster`][] parameter.
+
+## Assumptions
+
+* Each Nomad client should have a local Consul agent running on the same host,
+  reachable by Nomad. Nomad clients should never share a Consul agent or talk
+  directly to the Consul servers. Nomad is not compatible with [Consul Data
+  Plane][CDP].
+
+* The service discovery feature in Nomad depends on operators making sure that
+  the Nomad client can reach the Consul agent.
+
+* Tasks running inside Nomad also need to reach out to the Consul agent if
+  they want to use any of the Consul APIs. Ex: A task running inside a docker
+  container in the bridge mode won't be able to talk to a Consul Agent running
+  on the loopback interface of the host since the container in the bridge mode
+  has its own network interface and doesn't see interfaces on the global
+  network namespace of the host. There are a couple of ways to solve this, one
+  way is to run the container in the host networking mode, or make the Consul
+  agent listen on an interface in the network namespace of the container.
+
+* The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+
+* Consul service mesh using network namespaces is only supported on Linux.
+
+## Compatibility
+
+All currently supported versions of Nomad are compatible with recent versions of
+Consul, with some exceptions.
+
+* Nomad is not compatible with Consul Data Plane.
+
+|                   | Consul 1.17.0+ | Consul 1.18.0+ | Consul 1.19.0+ |
+|-------------------|----------------|----------------|----------------|
+| Nomad 1.8.0+      | ✅             | ✅             | ✅            |
+| Nomad 1.7.0+      | ✅             | ✅             | ✅            |
+| Nomad 1.6.0+      | ✅             | ✅             | ✅            |
+
+[Automatic Clustering with Consul]: /nomad/tutorials/manage-clusters/clustering
+[CDP]: /consul/docs/connect/dataplane
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Nomad agent Consul configuration]: /nomad/docs/configuration/consul
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`template` job specification documentation]: /nomad/docs/job-specification/template#consul-integration
+[`template`]: /nomad/docs/job-specification/template
+[consul_agent_namespace]: /nomad/docs/configuration/consul#namespace
+[consul_jobspec_namespace]: /nomad/docs/job-specification/consul#namespace
+[consul_namespaces]: /consul/docs/enterprise/namespaces
+[consul_run_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[consul_env_namespace]: /consul/commands#consul_namespace
+[int_consul_acl]: /nomad/docs/integrations/consul/acl
+[int_consul_mesh]: /nomad/docs/integrations/consul/service-mesh
+[nomad_config_consul]: /nomad/docs/configuration/consul
+[service]: /nomad/docs/job-specification/service "Nomad service Job Specification"
+[bridge or CNI networking mode]: /nomad/docs/job-specification/network#mode
+[nameserver]: /nomad/docs/job-specification/network#servers
+[transparent proxy]: /nomad/docs/job-specification/transparent_proxy
+[Forward DNS for Consul service discovery]: https://developer.hashicorp.com/consul/tutorials/networking/dns-forwarding
diff --git a/content/nomad/v1.9.x/content/docs/integrations/consul/service-mesh.mdx b/content/nomad/v1.9.x/content/docs/integrations/consul/service-mesh.mdx
new file mode 100644
index 0000000000..1c99181081
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/consul/service-mesh.mdx
@@ -0,0 +1,519 @@
+---
+layout: docs
+page_title: Integrate Consul service mesh
+description: |-
+  Learn how to use Nomad with Consul service mesh to enable secure service-to-service communication. Review an example that enables secure communication with Consul TLS, Consul access control lists (ACLs), and a transparent proxy.
+---
+
+# Consul service mesh
+
+[Consul service mesh](/consul/docs/connect) provides
+service-to-service connection authorization and encryption using mutual
+Transport Layer Security (TLS). Applications can use sidecar proxies in a
+service mesh configuration to automatically establish TLS connections for
+inbound and outbound connections without being aware of the service mesh at all.
+
+~> **Note:** Nomad's service mesh integration requires Linux network namespaces.
+Consul service mesh will not run on Windows or macOS.
+
+# Nomad with Consul service mesh integration
+
+Nomad integrates with Consul to provide secure service-to-service communication
+between Nomad jobs and task groups. To support Consul service mesh, Nomad
+adds a new networking mode for jobs that enables tasks in the same task group to
+share their networking stack. With a few changes to the job specification, job
+authors can opt into service mesh integration. When service mesh is enabled, Nomad will
+launch a proxy alongside the application in the job file. The proxy (Envoy)
+provides secure communication with other applications in the cluster.
+
+Nomad job specification authors can use Nomad's Consul service mesh integration to
+implement [service segmentation](https://www.consul.io/use-cases/multi-platform-service-mesh) in a
+microservice architecture running in public clouds without having to directly
+manage TLS certificates. This is transparent to job specification authors as
+security features in service mesh continue to work even as the application scales up
+or down or gets rescheduled by Nomad.
+
+For using the Consul service mesh integration with Consul ACLs enabled, see the
+[Secure Nomad Jobs with Consul Service Mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+# Nomad Consul service mesh example
+
+The following section walks through an example to enable secure communication
+between a web dashboard and a backend counting service. The web dashboard and
+the counting service are managed by Nomad. Nomad additionally configures Envoy
+proxies to run along side these applications. The dashboard is configured to
+connect to the counting service via localhost on port 9001. The proxy is managed
+by Nomad, and handles mTLS communication to the counting service.
+
+## Prerequisites
+
+### Consul
+
+The Consul service mesh integration with Nomad requires [Consul 1.6 or
+later.](https://releases.hashicorp.com/consul/1.6.0/) The Consul agent can be
+run in dev mode with the following command:
+
+~> **Note:** Nomad's Consul service mesh integration requires Consul in your `$PATH`
+
+```shell-session
+$ consul agent -dev
+```
+
+To use service mesh on a non-dev Consul agent, you will minimally need to enable the
+GRPC port and set `connect` to enabled by adding some additional information to
+your Consul client configurations, depending on format. Consul agents running TLS
+and a version greater than [1.14.0](https://releases.hashicorp.com/consul/1.14.0)
+should set the `grpc_tls` configuration parameter instead of `grpc`. Please see
+the Consul [port documentation](https://developer.hashicorp.com/consul/docs/install/ports) for further reference material.
+
+For HCL configurations:
+
+```hcl
+# ...
+
+ports {
+  grpc = 8502
+}
+
+connect {
+  enabled = true
+}
+```
+
+For JSON configurations:
+
+```javascript
+{
+  // ...
+  "ports": {
+    "grpc": 8502
+  },
+  "connect": {
+     "enabled": true
+  }
+}
+```
+
+#### Consul TLS
+
+~> **Note:** Consul 1.14+ made a [backwards incompatible change][consul_grpc_tls]
+in how TLS enabled grpc listeners work. When using Consul 1.14 with TLS enabled users
+will need to specify additional Nomad agent configuration to work with Connect. The
+`consul.grpc_ca_file` value must now be configured (introduced in Nomad 1.4.4),
+and `consul.grpc_address` will most likely need to be set to use the new standard
+`grpc_tls` port of `8503`.
+
+```hcl
+consul {
+  grpc_ca_file = "/etc/tls/consul-agent-ca.pem"
+  grpc_address = "127.0.0.1:8503"
+  ca_file      = "/etc/tls/consul-agent-ca.pem"
+  cert_file    = "/etc/tls/dc1-client-consul-0.pem"
+  key_file     = "/etc/tls/dc1-client-consul-0-key.pem"
+  ssl          = true
+  address      = "127.0.0.1:8501"
+}
+```
+
+#### Consul access control lists
+
+~> **Note:** Starting in Nomad v1.3.0, Consul Service Identity ACL tokens automatically
+generated by Nomad on behalf of Connect enabled services are now created in [`Local`]
+rather than Global scope, and are no longer replicated globally.
+
+To facilitate cross-Consul datacenter requests of Connect services registered by
+Nomad, Consul agents will need to be configured with [default anonymous][anon_token]
+ACL tokens with ACL policies of sufficient permissions to read service and node
+metadata pertaining to those requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+#### Transparent proxy
+
+Using Nomad's support for [transparent proxy][] configures the task group's
+network namespace so that traffic flows through the Envoy proxy. When the
+[`transparent_proxy`][] block is enabled:
+
+* Nomad will invoke the [`consul-cni`][] CNI plugin to configure `iptables` rules
+  in the network namespace to force outbound traffic from an allocation to flow
+  through the proxy.
+* If the local Consul agent is serving DNS, Nomad will set the IP address of the
+  Consul agent as the nameserver in the task's `/etc/resolv.conf`.
+* Consul will provide a [virtual IP][] for any upstream service the workload
+  has access to, based on the service intentions.
+
+Using transparent proxy has several important requirements:
+
+* You must have the [`consul-cni`][] CNI plugin installed on the client host
+  along with the usual [required CNI plugins][cni_plugins].
+* To use Consul DNS and virtual IPs, you will need to configure Consul's DNS
+  listener to be exposed to the workload network namespace. You can do this
+  without exposing the Consul agent on a public IP by setting the Consul
+  `bind_addr` to bind on a private IP address (the default is to use the
+  `client_addr`).
+* The Consul agent must be configured with [`recursors`][] if you want
+  allocations to make DNS queries for applications outside the service mesh.
+* Your workload's task cannot use the same [Unix user ID (UID)][uid] as the
+  Envoy sidecar proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`][tproxy_no_dns], see below).
+
+For example, a HCL configuration with a [go-sockaddr/template][] binding to the
+subnet `10.37.105.0/20`, with recursive DNS set to OpenDNS nameservers:
+
+```hcl
+bind_addr   = "{{ GetPrivateInterfaces | include \"network\" \"10.37.105.0/20\" | limit 1 | attr \"address\" }}"
+
+recursors = ["208.67.222.222", "208.67.220.220"]
+```
+
+### Nomad
+
+Nomad must schedule onto a routable interface in order for the proxies to
+connect to each other. The following steps show how to start a Nomad dev agent
+configured for Consul service mesh.
+
+```shell-session
+$ sudo nomad agent -dev-connect
+```
+
+### Container Network Interface (CNI) plugins
+
+Nomad uses CNI reference plugins to configure the network namespace used to secure the
+Consul service mesh sidecar proxy. All Nomad client nodes using network namespaces
+must have these CNI plugins [installed][cni_install].
+
+To use [`transparent_proxy`][] mode, Nomad client nodes will also need the
+[`consul-cni`][] plugin installed. See the Linux post-installation [steps](/nomad/docs/install#linux-post-installation-steps) for more detail on how to install CNI plugins.
+
+## Run the service mesh-enabled services
+
+Once Nomad and Consul are running, with Consul DNS enabled for transparent proxy
+mode as described above, submit the following service mesh-enabled services to
+Nomad by copying the HCL into a file named `servicemesh.nomad.hcl` and running:
+`nomad job run servicemesh.nomad.hcl`
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "http"
+
+      connect {
+        sidecar_service {
+          proxy {
+            transparent_proxy {}
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+The job contains two task groups: an API service and a web frontend.
+
+### API service
+
+The API service is defined as a task group with a bridge network:
+
+```hcl
+group "api" {
+  network {
+    mode = "bridge"
+  }
+
+  # ...
+}
+```
+
+Since the API service is only accessible via Consul service mesh, it does not
+define any ports in its network. The `connect` block enables the service mesh
+and the `transparent_proxy` block ensures that the service will be reachable via
+a virtual IP address when used with Consul DNS.
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {
+        proxy {
+          transparent_proxy {}
+        }
+      }
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `port` in the service block is the port the API service listens on. The
+Envoy proxy will automatically route traffic to that port inside the network
+namespace. Note that currently this cannot be a named port; it must be a
+hard-coded port value. See [GH-9907].
+
+### Web Frontend
+
+The web frontend is defined as a task group with a bridge network and a static
+forwarded port:
+
+```hcl
+group "dashboard" {
+  network {
+    mode = "bridge"
+
+    port "http" {
+      static = 9002
+      to     = 9002
+    }
+  }
+
+  # ...
+
+}
+```
+
+The `static = 9002` parameter requests the Nomad scheduler reserve port 9002 on
+a host network interface. The `to = 9002` parameter forwards that host port to
+port 9002 inside the network namespace.
+
+This allows you to connect to the web frontend in a browser by visiting
+`http://<host_ip>:9002` as show below:
+
+[![Count Dashboard][count-dashboard]][count-dashboard]
+
+The web frontend connects to the API service via Consul service mesh.
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        transparent_proxy {}
+      }
+    }
+  }
+}
+```
+
+The `connect` block with `transparent_proxy` configures the web frontend's
+network namespace to route all access to the `count-api` service through the
+Envoy proxy.
+
+The web frontend is configured to communicate with the API service with an
+environment variable `$COUNTING_SERVICE_URL`:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://count-api.virtual.consul"
+}
+```
+
+The `transparent_proxy` block ensures that DNS queries are made to Consul so
+that the `count-api.virtual.consul` name resolves to a virtual IP address. Note
+that you don't need to specify a port number because the virtual IP will only be
+directed to the correct service port.
+
+### Manually configured upstreams
+
+You can also use Connect without Consul DNS and `transparent_proxy` mode. This
+approach is not recommended because it requires duplicating service intention
+information in an `upstreams` block in the Nomad job specification. But Consul
+DNS is not protected by ACLs, so you might want to do this if you don't want to
+expose Consul DNS to untrusted workloads.
+
+In that case, you can add `upstream` blocks to the job spec. You don't need the
+`transparent_proxy` block for the `count-api` service:
+
+```hcl
+group "api" {
+
+  # ...
+
+  service {
+    name = "count-api"
+    port = "9001"
+
+    connect {
+      sidecar_service {}
+    }
+  }
+
+  # ...
+
+}
+```
+
+But you'll need to add an `upstreams` block to the `count-dashboard` service:
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "http"
+
+  connect {
+    sidecar_service {
+      proxy {
+        upstreams {
+          destination_name = "count-api"
+          local_bind_port  = 8080
+        }
+      }
+    }
+  }
+}
+```
+
+The `upstreams` block defines the remote service to access (`count-api`) and
+what port to expose that service on inside the network namespace (`8080`).
+
+The web frontend will also need to use an environment variable to communicate
+with the API service:
+
+```hcl
+env {
+  COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+}
+```
+
+This environment variable value gets interpolated with the upstream's
+address. Note that dashes (`-`) are converted to underscores (`_`) in
+environment variables so `count-api` becomes `count_api`.
+
+## Limitations
+
+- The minimum Consul version to use Connect with Nomad is Consul v1.8.0.
+- The `consul` binary must be present in Nomad's `$PATH` to run the Envoy
+  proxy sidecar on client nodes.
+- Consul service mesh using network namespaces is only supported on Linux.
+- Prior to Consul 1.9, the Envoy sidecar proxy will drop and stop accepting
+  connections while the Nomad agent is restarting.
+
+## Troubleshooting
+
+If the sidecar service is not running correctly, you can investigate
+potential `envoy` failures in the following ways:
+
+* Task logs in the associated `connect-*` task
+* Task secrets (may contain sensitive information):
+  * envoy CLI command: `secrets/.envoy_bootstrap.cmd`
+  * environment variables: `secrets/.envoy_bootstrap.env`
+* An extra Allocation log file: `alloc/logs/envoy_bootstrap.stderr.0`
+
+For example, with an allocation ID starting with `b36a`:
+
+```shell-session
+nomad alloc status -short b36a  # to get the connect-* task name
+nomad alloc logs -task connect-proxy-count-api -stderr b36a
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.cmd
+nomad alloc exec -task connect-proxy-count-api b36a cat secrets/.envoy_bootstrap.env
+nomad alloc fs b36a alloc/logs/envoy_bootstrap.stderr.0
+```
+
+Note: If the alloc is unable to start successfully, debugging files may
+only be accessible from the host filesystem. However, the sidecar task secrets
+directory may not be available in systems where it is mounted in a temporary
+filesystem.
+
+Bootstrapping the Envoy proxy requires that the Consul ACL token and service
+registration have successfully replicated to whichever Consul server the local
+Consul agent is connected to. Nomad clients poll for this value with exponential
+backoff and a timeout. You can adjust the timeouts on a given node by setting
+node metadata values via the command line or in the [`client.meta`][] agent
+configuration block. The default values are shown below:
+
+```shell-session
+nomad node meta apply -node-id $nodeID \
+    consul.token_preflight_check.timeout=10s \
+    consul.token_preflight_check.base=500ms \
+    consul.service_preflight_check.timeout=60s \
+    consul.service_preflight_check.base=1s
+```
+
+[count-dashboard]: /img/count-dashboard.png
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[gh-9907]: https://github.com/hashicorp/nomad/issues/9907
+[`Local`]: /consul/docs/security/acl/tokens#token-attributes
+[anon_token]: /consul/docs/security/acl/tokens#special-purpose-tokens
+[consul_ports]: /consul/docs/agent/config/config-files#ports
+[consul_grpc_tls]: /consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration
+[cni_install]: /nomad/docs/install#linux-post-installation-steps
+[transparent proxy]: /consul/docs/k8s/connect/transparent-proxy
+[go-sockaddr/template]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[tproxy_no_dns]: /nomad/docs/job-specification/transparent_proxy#no_dns
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[`client.meta`]: /nomad/docs/configuration/client#meta
+[uid]: /nomad/docs/job-specification/transparent_proxy#uid
diff --git a/content/nomad/v1.9.x/content/docs/integrations/index.mdx b/content/nomad/v1.9.x/content/docs/integrations/index.mdx
new file mode 100644
index 0000000000..ce56bc2a66
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: HashiCorp integrations
+description: |-
+  This section features Nomad's integrations with Consul and Vault. Learn how to integrate access control lists (ACLs) and Consul service mesh.
+---
+
+# HashiCorp integrations
+
+Nomad integrates seamlessly with Consul and Vault for service discovery and secrets management.
+
+Please navigate the appropriate sub-sections for more information.
diff --git a/content/nomad/v1.9.x/content/docs/integrations/vault/acl.mdx b/content/nomad/v1.9.x/content/docs/integrations/vault/acl.mdx
new file mode 100644
index 0000000000..a27cf7ae8c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/vault/acl.mdx
@@ -0,0 +1,869 @@
+---
+layout: docs
+page_title: Integrate Vault access control list (ACL)
+description: |-
+  Learn how to protect your Nomad cluster with the Vault access control list (ACL) system and use workload identities with Vault. Configure Vault authentication.
+---
+
+# Integrate Vault access control list (ACL)
+
+The Vault ACL system protects the cluster from unauthorized access. It must be
+properly configured in order for the Vault and Nomad integrations to work.
+
+## Nomad workload identities
+
+Starting in Nomad 1.7, Nomad clients can use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault ACL token specific to the task. When
+using Nomad workload identities, you no longer need to pass in a Vault ACL
+token to submit a job.
+
+By default, Nomad only generates a workload identity for tasks that can be used
+to access Nomad itself, such as for reading [Variables][] from a [`template`][]
+block. To access Vault, jobs must have additional workload identities defined
+as [`identity`][] blocks.
+
+To avoid having to add these additional identities to every job, you can
+configure the Nomad servers with the [`vault.default_identity`][] agent
+configuration. Upon job registration, the Nomad servers update tasks that have
+a [`vault`][] block with this default identity.
+
+You can also specify identities for Vault directly in the job. When provided,
+they override the Nomad server configuration. Refer to the [Workload Identities
+for Vault][jobspec_identity_vault] section of the `identity` block
+documentation for more information.
+
+### Configuring Vault authentication
+
+Vault must be configured to receive, validate, and trust these Nomad workload
+identities. Since they are encoded as [JSON Web Tokens (JWTs)][jwt], you must
+create a [JWT ACL auth method][vault_jwt_auth_method]. The auth method is an
+endpoint that Nomad can use to exchange workload identities for Vault ACL
+tokens.
+
+Refer to Vault's [Authentication][vault_auth] documentation for more
+information.
+
+#### Vault auth method
+
+The auth method configuration points to Nomad's [JSON Web Key Set (JWKS)
+URL][nomad_jwks_url]. Vault servers call this URL to retrieve the public keys
+Nomad uses to sign workload identities. With these keys, Vault is able to
+validate their origin and confirm that they were actually created by Nomad.
+
+<CodeBlockConfig highlight="2" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The `jwks_url` address must be reachable by all Vault servers and should
+resolve to multiple Nomad agents to avoid a single point of failure. Both Nomad
+servers and clients are able to handle this request.
+
+Refer to the [Important Considerations About the JWKS
+URL](#important-considerations-about-the-jwks-url) section for additional
+information on how to configure the `jwks_url` value.
+
+[![Vault Auth Method][img_vault_auth_method]][img_vault_auth_method]
+
+When an allocation that needs access to Vault starts, the Nomad client
+running it exchanges the Nomad workload identities for tasks for Vault ACL
+tokens.
+
+[![Vault JWT Login][img_vault_wid_acl_token]][img_vault_wid_acl_token]
+
+#### Vault ACL role
+
+A Vault [ACL role][vault_role] groups multiple ACL policies to apply to a token
+and determine the permissions it receives.
+
+The auth method may define a default ACL role that is applied to the ACL tokens
+it generates. If no default role is set, the role must be provided in the job
+using the [`vault.role`][] parameter or in the Nomad client configuration
+[`vault.create_from_role`][].
+
+<CodeBlockConfig highlight="4" filename="auth-method.json">
+
+```json
+{
+  "jwks_url": "https://nomad.example.com:4646/.well-known/jwks.json",
+  "jwt_supported_algs": ["RS256", "EdDSA"],
+  "default_role": "nomad-workloads"
+}
+```
+
+</CodeBlockConfig>
+
+The ACL role specifies the list of authorized audience values using the
+[`bound_audiences`][], which must have at least one match with the values
+defined in the Nomad workload identity [`aud`][] parameter. For security
+reasons, it is recommended to only define a single audience value.
+
+<CodeBlockConfig highlight="3" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Nomad workload identities have a set of [claims][nomad_wid_claims] that can be
+referenced in Vault ACL configuration. The ACL role uses the
+[`claim_mappings`][] parameter to determine which of these claims are made
+available to the rest of the configuration.
+
+The [`bound_claims`][] parameter restricts which workload identities are able
+to use the role based on their claims. Refer to Vault's [Bound
+Claims][vault_bound_claims] documentation for more information.
+
+<CodeBlockConfig highlight="4-7,10-14" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_type": "service",
+  "token_policies": ["nomad-workloads"],
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+Vault has different [types of ACL tokens][vault_token_types]. Nomad typically
+uses tokens of type `service` since they can be renewed for as long as the
+workload is active. Nomad automatically renews the Vault ACL tokens it generates
+before they expire. To ensure the tokens can be renewed for as long as
+necessary, [`token_explicit_max_ttl`][] must be set to 0.
+
+Alternately, you may use `batch` tokens. This should only be used when a secret
+is requested from Vault once at the start of a task or in a short-lived prestart
+task. Long-running tasks should never set `allow_token_expiration=true` if they
+obtain Vault secrets via `template` blocks, as the Vault token will expire and
+the template runner will continue to make failing requests to Vault until its
+[`vault_retry`][] attempts are exhausted, at which point the task will
+fail. Vault's `batch` tokens cannot be renewed, and Nomad will not attempt to
+renew them when configured to use Workload Identity.
+
+<CodeBlockConfig highlight="16-18" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+#### Vault ACL policy
+
+A Vault ACL role may have one or more ACL policies attached. Vault [ACL
+policies][vault_policies] define the permissions granted to an ACL
+token.
+
+<CodeBlockConfig highlight="15" filename="acl-role.json">
+
+```json
+{
+  "role_type": "jwt",
+  "bound_audiences": ["vault.io"],
+  "bound_claims": {
+     "nomad_namespace": "default",
+     "nomad_job_id": "mongo"
+  },
+  "user_claim": "/nomad_job_id",
+  "user_claim_json_pointer": true,
+  "claim_mappings": {
+    "nomad_namespace": "nomad_namespace",
+    "nomad_job_id": "nomad_job_id",
+    "nomad_task": "nomad_task"
+  },
+  "token_policies": ["nomad-workloads"],
+  "token_type": "service",
+  "token_period": "30m",
+  "token_explicit_max_ttl": 0
+}
+```
+
+</CodeBlockConfig>
+
+ACL policies can reference dynamic values from Nomad workload identities claims
+exposed from the ACL role in [templated policies][vault_templated_policies].
+The exact ACL policy rules will depend on the level of access required by
+tasks.
+
+The following example ACL policy automatically grants `read` permissions to
+secrets in the path `secret/data/<job namespace>/<job name>/*`, where `<job
+namespace>` and `<job name>` are read from the workload identity claims
+`nomad_namespace` and `nomad_job_id`.
+
+<CodeBlockConfig highlight="1,5,9" filename="acl-policy.hcl">
+
+```hcl
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}/*" {
+  capabilities = ["read"]
+}
+
+path "secret/data/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_job_id}}" {
+  capabilities = ["read"]
+}
+
+path "secret/metadata/{{identity.entity.aliases.auth_jwt_d34481ad.metadata.nomad_namespace}}/*" {
+  capabilities = ["list"]
+}
+
+path "secret/metadata/*" {
+  capabilities = ["list"]
+}
+```
+
+</CodeBlockConfig>
+
+The overall configuration structure is illustrated in the following diagram.
+
+[![Vault Auth Overview][img_vault_auth_overview]][img_vault_auth_overview]
+
+#### Vault namespaces <EnterpriseAlert inline />
+
+Vault Enterprise supports multiple namespaces and jobs in Nomad Enterprise can
+use the [`vault.namespace`][] parameter to specify which namespace to use. In a
+multi-namespace environment, the authentication setup described must be applied
+to each Vault namespace used by jobs.
+
+### Important considerations about the JWKS URL
+
+The recommended configuration assumes Vault servers are able to connect to
+Nomad agents (either client or servers) to retrieve the JSON Web Key Set
+information.
+
+This section covers additional aspects you should consider depending on how
+your Vault and Nomad clusters are configured and deployed.
+
+#### Mutual TLS in Nomad
+
+It is highly recommended to use [mutual TLS][tutorial_mtls] in production
+deployments of Nomad. With mTLS enabled, the [`tls.verify_https_client`][]
+configuration must be set to `false` since it is not possible to provide client
+certificates to the Vault auth method. Nomad's CA certificate should be
+specified in the Vault auth method's
+[`jwks_ca_pem`](https://developer.hashicorp.com/vault/api-docs/auth/jwt#jwks_ca_pem)
+parameter.
+
+Alternatively, you may expose Nomad's JWKS URL from a proxy or a load balancer
+that handles the mutual TLS connection to Nomad and exposes the JWKS URL
+endpoint over standard TLS.
+
+#### Vault servers not able to connect to Nomad
+
+If the Vault servers are not able to reach Nomad's JWKS URL, you may read the
+public keys from Nomad's [`/.well-known/jwks.json`][nomad_jwks_url] endpoint
+and provide them to the auth method directly using the
+[`jwt_validation_pubkeys`][] parameter. The keys must be converted from JWKS to
+PEM format.
+
+You may also host the JWKS JSON response from Nomad in an external location
+that is reachable by the Vault servers, and use that address as the value for
+`jwks_url`.
+
+It is important to remember that the Nomad keys **are rotated periodically**, so
+both approaches should be automated and done continually. The rotation frequency
+is controlled by the [`server.root_key_rotation_threshold`][] configuration of
+the Nomad servers. Keys will be prepublished at half the rotation threshold.
+
+### Additional references
+
+The [Vault ACL with Nomad Workload Identities][vault_tutorial_wid] tutorial
+provides guided instructions on how to configure Vault and Nomad for workload
+identities.
+
+The [`nomad setup vault`][nomad_cli_setup_vault] command and the
+[`hashicorp-modules/nomad-setup/vault`][tf_nomad_setup_vault] Terraform
+module can help you automate the process of applying configuration to a Vault
+cluster.
+
+## Authentication Without Workload Identity (Legacy)
+
+To use the legacy Vault integration, Nomad servers must be provided a Vault
+token. This token can either be a root token or a periodic token with
+permissions to create from a token role. The root token is the easiest way to
+get started, but we recommend a token role based token for production
+installations. Nomad servers will renew the token automatically. **Note that the
+Nomad clients do not need to be provided with a Vault token.**
+
+<Note title="Deprecation Warning">
+
+This legacy workflow will be removed in Nomad 1.10. Before upgrading to Nomad
+1.10, you need to configure authentication with Vault as described in [Nomad
+Workload Identities](#nomad-workload-identities).
+
+</Note>
+
+See the [Enterprise specific section][ent] for configuring Vault Enterprise.
+
+### Root Token Integration
+
+If Nomad is given a [root token](/vault/docs/concepts/tokens#root-tokens), no
+further configuration is needed as Nomad can derive a token for jobs using any
+Vault policies. Best practices recommend using a periodic token with the minimal
+permissions necessary instead of providing Nomad the root vault token.
+
+### Token Role based Integration
+
+Vault's [Token Authentication Backend][auth] supports a concept called "roles".
+Token roles allow policies to be grouped together and token creation to be
+delegated to a trusted service such as Nomad. By creating a token role, the set
+of policies that tasks managed by Nomad can access may be limited compared to
+giving Nomad a root token. Token roles allow both allowlist and denylist
+management of policies accessible to the role.
+
+To configure Nomad and Vault to create tokens against a role, the following must
+occur:
+
+1. Create a "nomad-server" policy used by Nomad to create and manage tokens.
+
+2. Create a Vault token role with the configuration described below.
+
+3. Configure Nomad to use the created token role.
+
+4. Give Nomad servers a periodic token with the "nomad-server" policy created
+   above.
+
+#### Required Vault Policies
+
+The token Nomad receives must have the capabilities listed below. An explanation
+for the use of each capability is given.
+
+```hcl
+# Allow creating tokens under "nomad-cluster" token role. The token role name
+# should be updated if "nomad-cluster" is not used.
+path "auth/token/create/nomad-cluster" {
+  capabilities = ["update"]
+}
+
+# Allow looking up "nomad-cluster" token role. The token role name should be
+# updated if "nomad-cluster" is not used.
+path "auth/token/roles/nomad-cluster" {
+  capabilities = ["read"]
+}
+
+# Allow looking up the token passed to Nomad to validate # the token has the
+# proper capabilities. This is provided by the "default" policy.
+path "auth/token/lookup-self" {
+  capabilities = ["read"]
+}
+
+# Allow looking up incoming tokens to validate they have permissions to access
+# the tokens they are requesting. This is only required if
+# `allow_unauthenticated` is set to false.
+path "auth/token/lookup" {
+  capabilities = ["update"]
+}
+
+# Allow revoking tokens that should no longer exist. This allows revoking
+# tokens for dead tasks.
+path "auth/token/revoke-accessor" {
+  capabilities = ["update"]
+}
+
+# Allow checking the capabilities of our own token. This is used to validate the
+# token upon startup. Note this requires update permissions because the Vault API
+# is a POST
+path "sys/capabilities-self" {
+  capabilities = ["update"]
+}
+
+# Allow our own token to be renewed.
+path "auth/token/renew-self" {
+  capabilities = ["update"]
+}
+```
+
+The above [`nomad-server` policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) is
+available for download. Below is an example of writing this policy to Vault:
+
+```shell-session
+# Download the policy
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+```
+
+#### Vault Token Role Configuration
+
+A Vault token role must be created for use by Nomad. The token role can be used
+to manage what Vault policies are accessible by jobs submitted to Nomad. The
+policies can be managed as a allowlist by using `allowed_policies` in the token
+role definition or as a denylist by using `disallowed_policies`.
+
+If using `allowed_policies`, tasks may only request Vault policies that are in
+the list. If `disallowed_policies` is used, task may request any policy that is
+not in the `disallowed_policies` list. There are trade-offs to both approaches
+but generally it is easier to use the denylist approach and add policies that
+you would not like tasks to have access to into the `disallowed_policies` list.
+
+An example token role definition is given below:
+
+```json
+{
+  "disallowed_policies": "nomad-server",
+  "token_explicit_max_ttl": 0,
+  "name": "nomad-cluster",
+  "orphan": true,
+  "token_period": 259200,
+  "renewable": true
+}
+```
+
+##### Token Role Requirements
+
+Nomad checks that token role has an appropriate configuration for use by the
+cluster. Fields that are checked are documented below as well as descriptions of
+the important fields. See Vault's [Token Authentication Backend][auth]
+documentation for all possible fields and more complete documentation.
+
+- `allowed_policies` - Specifies the list of allowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should have access to.
+
+- `disallowed_policies` - Specifies the list of disallowed policies as a
+  comma-separated string. This list should contain all policies that jobs running
+  under Nomad should **not** have access to. The policy created above that
+  grants Nomad the ability to generate tokens from the token role should be
+  included in list of disallowed policies. This prevents tokens created by
+  Nomad from generating new tokens with different policies than those granted
+  by Nomad.
+
+  A regression occurred in Vault 0.6.4 when validating token creation using a
+  token role with `disallowed_policies` such that it is not usable with
+  Nomad. This was remedied in 0.6.5 and does not effect earlier versions
+  of Vault.
+
+- `token_explicit_max_ttl` - Specifies the max TTL of a token. **Must be set to `0`** to
+  allow periodic tokens.
+
+- `name` - Specifies the name of the policy. We recommend using the name
+  `nomad-cluster`. If a different name is chosen, replace the token role in the
+  above policy.
+
+- `orphan` - Specifies whether tokens created against this token role will be
+  orphaned and have no parents. Nomad does not enforce the value of this field
+  but understanding the implications of each value is important.
+
+  If set to false, all tokens will be revoked when the Vault token given to
+  Nomad expires. This makes it easy to revoke all tokens generated by Nomad but
+  forces all Nomad servers to use the same Vault token, even through upgrades of
+  Nomad servers. If the Vault token that was given to Nomad and used to generate
+  a tasks token expires, the token used by the task will also be revoked which
+  is not ideal.
+
+  When set to true, the tokens generated for tasks will not be revoked when
+  Nomad's token is revoked. However Nomad will still revoke tokens when the
+  allocation is no longer running, minimizing the lifetime of any task's token.
+  With orphaned enabled, each Nomad server may also use a unique Vault token,
+  making bootstrapping and upgrading simpler. As such, **setting `orphan = true`
+  is the recommended setting**.
+
+- `token_period` - Specifies the length the TTL is extended by each renewal in
+  seconds. It is suggested to set this value on the order of magnitude of 3 days
+  (259200 seconds) to avoid a large renewal request rate to Vault. **Must be set
+  to a positive value**.
+
+- `renewable` - Specifies whether created tokens are renewable. This allows
+  Nomad to renew tokens for tasks. Nomad clients will automatically detect when
+  tokens cannot be renewed and will not attempt to renew them (see
+  [`vault.allow_token_expiration`][]).
+
+The above [`nomad-cluster` token role](https://nomadproject.io/data/vault/nomad-cluster-role.json) is
+available for download. Below is an example of writing this role to Vault:
+
+```shell-session
+# Download the token role
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Example Configuration
+
+To make getting started easy, the basic [`nomad-server`
+policy](https://nomadproject.io/data/vault/nomad-server-policy.hcl) and
+[`nomad-cluster` role](https://nomadproject.io/data/vault/nomad-cluster-role.json) described above are
+available for download.
+
+The below example assumes Vault is accessible, unsealed and the operator has
+appropriate permissions.
+
+```shell-session
+# Download the policy and token role
+$ curl https://nomadproject.io/data/vault/nomad-server-policy.hcl -O -s -L
+$ curl https://nomadproject.io/data/vault/nomad-cluster-role.json -O -s -L
+
+# Write the policy to Vault
+$ vault policy write nomad-server nomad-server-policy.hcl
+
+# Create the token role with Vault
+$ vault write /auth/token/roles/nomad-cluster @nomad-cluster-role.json
+```
+
+#### Retrieving the Token Role based Token
+
+After the token role is created, a token suitable for the Nomad servers may be
+retrieved by issuing the following Vault command:
+
+```shell-session
+$ vault token create -policy nomad-server -period 72h -orphan
+Key             Value
+---             -----
+token           f02f01c2-c0d1-7cb7-6b88-8a14fada58c0
+token_accessor  8cb7fcb3-9a4f-6fbf-0efc-83092bb0cb1c
+token_duration  259200s
+token_renewable true
+token_policies  [default nomad-server]
+```
+
+The `-orphan` flag is included when generating the Nomad server token above to
+prevent revocation of the token when its parent expires. Vault typically
+creates tokens with a parent-child relationship. When an ancestor token is
+revoked, all of its descendant tokens and their associated leases are revoked
+as well.
+
+When generating Nomad's Vault token, we need to ensure that revocation of the
+parent token does not revoke Nomad's token. To prevent this behavior we
+specify the `-orphan` flag when we create the Nomad's Vault token. All
+other tokens generated by Nomad for jobs will be generated using the policy
+default of `orphan = false`.
+
+More information about creating orphan tokens can be found in
+[Vault's Token Hierarchies and Orphan Tokens documentation][tokenhierarchy].
+
+The [`-period` flag](/vault/docs/commands/token/create#period) is required to allow the automatic renewal of the token. If this is left out, a [`vault token renew` command](/vault/docs/commands/token/renew) will need to be run manually to renew the token.
+
+The token can then be set in the server configuration's
+[`vault` block][config], as a command-line flag, or via an environment
+variable.
+
+```shell-session
+$ VAULT_TOKEN=f02f01c2-c0d1-7cb7-6b88-8a14fada58c0 nomad agent -config /path/to/config
+```
+
+An example of what may be contained in the configuration is shown below. For
+complete documentation please see the [Nomad agent Vault integration][config]
+configuration.
+
+```hcl
+vault {
+  enabled          = true
+  ca_path          = "/etc/certs/ca"
+  cert_file        = "/var/certs/vault.crt"
+  key_file         = "/var/certs/vault.key"
+  address          = "https://vault.service.consul:8200"
+  create_from_role = "nomad-cluster"
+}
+```
+
+### Troubleshooting Legacy Authentication
+
+#### Invalid Vault token
+
+Upon startup, Nomad will attempt to connect to the specified Vault server. Nomad
+will lookup the passed token and if the token is from a token role, the token
+role will be validated. Nomad will not shutdown if given an invalid Vault token,
+but will log the reasons the token is invalid and disable Vault integration.
+
+#### No Secret Exists
+
+Vault has two APIs for secrets, [`v1` and `v2`][vault-secrets-version]. Each version
+has different paths, and Nomad does not abstract this for you. As such you will
+need to specify the path as reflected by Vault's HTTP API, rather than the path
+used in the `vault kv` command.
+
+You can see examples of `v1` and `v2` syntax in the
+[template documentation][vault-kv-templates].
+
+## Enterprise Configuration
+
+<EnterpriseAlert />
+
+Nomad Enterprise allows jobs to use multiple [Vault Namespaces][]. There are a
+few configuration settings to consider when using this functionality.
+
+### Example Configuration
+
+Below is an example for creating two Namespaces within Vault.
+
+```shell-session
+# Create a namespace "engineering" within Vault
+$ vault namespace create engineering
+
+# Create a child namespace "frontend" under "engineering"
+$ vault namespace create -namespace=engineering frontend
+```
+
+### Required Vault Policies
+
+Policies are configured per Vault namespace. We will apply the policy in the
+example above to each namespace—engineering and engineering/frontend.
+
+```shell-session
+# Create the "nomad-server" policy in the "engineering" namespace
+$ vault policy write -namespace=engineering nomad-server nomad-server-policy.hcl
+
+# Create the "nomad-server" policy in the "engineering/frontend" namespace
+$ vault policy write -namespace=engineering/frontend nomad-server nomad-server-policy.hcl
+```
+
+We will also configure the previously configured `nomad-workloads` role with each
+Namespace
+
+```shell-session
+# Create the "nomad-cluster" token role in the "engineering" namespace
+$ vault write -namespace=engineering /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+
+# Create the "nomad-cluster" token role in the "engineering/frontend" namespace
+$ vault write -namespace=engineering/frontend /auth/token/roles/nomad-workloads @nomad-workloads-role.json
+```
+
+The [Nomad agent Vault integration][config] configuration supports specifying a
+Vault Namespace, but since we will be using multiple it can be left blank. By
+default Nomad will interact with Vault's root Namespace, but individual jobs may
+specify other Vault Namespaces to use.
+
+```hcl
+vault {
+  enabled               = true
+  ca_path               = "/etc/certs/ca"
+  cert_file             = "/var/certs/vault.crt"
+  key_file              = "/var/certs/vault.key"
+  address               = "https://vault.service.consul:8200"
+
+  default_identity {
+    aud = ["vault.io"]
+  }
+}
+```
+
+For legacy authentication, the same steps can be taken to inject a Vault token
+from the [Retrieving the Token Role based
+Token](#retrieving-the-token-role-based-token) steps.
+
+### Submitting a job with a Vault Namespace
+
+The example job file below specifies to use the `engineering` Namespace in
+Vault. It will authenticate to Vault using its workload identity with the
+`nomad-workloads` Vault role, then read the value at secret/foo and fetch the
+value for key `bar`.
+
+```hcl
+job "vault" {
+
+  group "demo" {
+    task "task" {
+      vault {
+        namespace = "engineering"
+        role      = "nomad-workloads"
+      }
+
+      driver = "raw_exec"
+      config {
+        command = "/usr/bin/cat"
+        args    = ["secrets/config.txt"]
+      }
+
+      template {
+        data        = <<EOF
+{{ with secret "secret/foo" }}
+SOME_VAL={{.Data.bar}}
+{{ end }}
+EOF
+        destination = "secrets/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Submitting a job with a Vault Namespace with Legacy Authentication
+
+For the legacy authentication, because [`allow_unauthenticated`][allow_unauth]
+is set to `false` job submitters will need to provide a sufficiently privileged
+token when submitting a job. A token that has access to an appropriate policy in
+`engineering` namespace is needed:
+
+```shell-session
+$ vault token create -policy access-kv -namespace=engineering -period 72h -orphan
+
+Key                  Value
+---                  -----
+token                s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy
+token_accessor       VsKtJwaShwtTo1r9nWV9Rlad.fvuLy
+token_duration       72h
+token_renewable      true
+token_policies       ["access-kv" "default"]
+identity_policies    []
+policies             ["access-kv" "default"]
+```
+
+The token can then be submitted with our job
+
+```shell-session
+$ VAULT_TOKEN=s.H39hfS7eHSbb1GpkdzOQLTmz.fvuLy nomad job run vault.nomad
+```
+
+## Migrating to Using Workload Identity with Vault
+
+Migrating from the legacy (pre-1.7) workflow where workloads use the agent's
+Vault token requires configuration on your Vault cluster and your Nomad server
+agents.
+
+Once the migration is fully complete, Nomad server will no longer have access
+to Vault, as it was required in the deprecated legacy workflow. This also means
+that they will no longer be able to fulfill some of their responsibilities from
+the legacy workflow, such as generating and revoking Vault ACL tokens.
+
+Before removing Vault connectivity configuration from Nomad servers, you must
+make sure the rest of the cluster is ready to support workload identities for
+Vault. You can run the [`nomad setup vault -check`][nomad_cli_setup_vault]
+command to verify what changes are still necessary.
+
+Before removing Nomad servers access to Vault you must:
+
+  * Redeploy the jobs listed in the section `Jobs Without Workload Identity for
+    Vault` with an identity for Vault. You can specify this identity [directly
+    in the job][jobspec_identity_vault] or redeploy the job without changes to
+    use the default value from the server [`vault.default_identity`][]
+    configuration if set.
+  * Upgrade nodes listed in the section `Outdated Nodes` to a version of Nomad
+    above 1.7.0.
+
+There is not action required for the Vault ACL tokens listed under `Vault
+Tokens`. Nomad will revoke them as you redeploy jobs to use workload identities
+but there may be some leftovers. You can still proceed with the migration
+process, but Nomad will not revoke them once access to Vault is removed from
+Nomad servers. They will expire once their TTL reaches zero, or you may
+manually revoke them if they are no longer needed by an allocation.
+
+The migration process can happen over time. As long as all servers are upgraded
+to Nomad 1.7+ and still retain access to Vault, jobs can still use either the
+new workload identity flow or the deprecated legacy flow.
+
+To summarize the migration process:
+
+* Enable [`vault.default_identity`][] blocks in your Nomad server agent
+  configurations, but **do not modify any of the existing Vault
+  configuration**.
+* Upgrade your cluster following the documented [Upgrade
+  Process][docs_upgrade].
+* Create the Vault auth method, default role, and policies on your Vault
+  cluster.
+* Run the `nomad setup vault -check` command to verify if the cluster is ready
+  to migrate to workload identity access to Vault.
+  * Resubmit Nomad jobs that need access to Vault to redeploy them with a new
+    workload identity for Vault.
+    * (Optionally) Add [`vault.role`][] fields to any Nomad jobs that will not
+      use the default role.
+    * (Optionally) add [`identity`][] blocks to your jobs if you want to use a
+      different identity because of how your auth method and roles are
+      configured.
+  * Upgrade any remaining clients to Nomad 1.7+.
+* Remove parameters no longer used by the Nomad server agents from the
+  [`vault`][config] configuration block.
+
+[Variables]: /nomad/docs/concepts/variables
+[Vault Namespaces]: /vault/docs/enterprise/namespaces
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`aud`]: /nomad/docs/job-specification/identity#aud
+[`bound_audiences`]: /vault/api-docs/auth/jwt#bound_audiences
+[`bound_claims`]: /vault/api-docs/auth/jwt#bound_claims
+[`claim_mappings`]: /vault/api-docs/auth/jwt#claim_mappings
+[`identity`]: /nomad/docs/job-specification/identity
+[`jwt_validation_pubkeys`]: /vault/api-docs/auth/jwt#jwt_validation_pubkeys
+[`server.root_key_rotation_threshold`]: /nomad/docs/configuration/server#root_key_rotation_threshold
+[`template`]: /nomad/docs/job-specification/template
+[`tls.verify_https_client`]: /nomad/docs/configuration/tls#verify_https_client
+[`token_explicit_max_ttl`]: /vault/api-docs/auth/jwt#token_explicit_max_ttl
+[`vault.create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault.namespace`]: /nomad/docs/job-specification/vault#namespace
+[`vault.role`]: /nomad/docs/job-specification/vault#role
+[`vault`]: /nomad/docs/job-specification/vault
+[allow_unauth]: /nomad/docs/configuration/vault#allow_unauthenticated
+[auth]: /vault/docs/auth/token 'Vault Authentication Backend'
+[config]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[docs_upgrade]: /nomad/docs/upgrade#upgrade-process
+[ent]: #enterprise-configuration
+[img_vault_auth_method]: /img/vault-integration-auth-method.png
+[img_vault_auth_overview]: /img/vault-integration-auth-overview.png
+[img_vault_wid_acl_token]: /img/vault-integration-wid-acl-token.png
+[jobspec_identity_vault]: /nomad/docs/job-specification/identity#workload-identities-for-vault
+[jwt]: https://jwt.io/
+[nomad_cli_setup_vault]: /nomad/docs/commands/setup/vault
+[nomad_jwks_url]: /nomad/api-docs/operator/keyring#list-active-public-keys
+[nomad_wid_claims]: /nomad/docs/concepts/workload-identity#workload-identity-claims
+[tf_nomad_setup_vault]: https://registry.terraform.io/modules/hashicorp-modules/nomad-setup/vault
+[tokenhierarchy]: /vault/docs/concepts/tokens#token-hierarchies-and-orphan-tokens 'Vault Tokens - Token Hierarchies and Orphan Tokens'
+[tutorial_mtls]: /nomad/tutorials/transport-security/security-enable-tls
+[vault-kv-templates]: /nomad/docs/job-specification/template#vault-kv-api-v1 'Vault KV API v1'
+[vault-secrets-version]: /vault/docs/secrets/kv 'KV Secrets Engine'
+[vault_auth]: /vault/docs/concepts/auth
+[vault_bound_claims]: /vault/docs/auth/jwt#bound-claims
+[vault_jwt_auth_method]: /vault/api-docs/auth/jwt
+[vault_policies]: /vault/docs/concepts/policies
+[vault_role]: /vault/api-docs/auth/jwt#create-update-role
+[vault_templated_policies]: /vault/tutorials/policies/policy-templating
+[vault_token_types]: /vault/tutorials/tokens/tokens#token-types
+[vault_tutorial_wid]: /nomad/tutorials/integrate-vault/vault-acl
+[`vault.allow_token_expiration`]: /nomad/docs/job-specification/vault#allow_token_expiration
diff --git a/content/nomad/v1.9.x/content/docs/integrations/vault/index.mdx b/content/nomad/v1.9.x/content/docs/integrations/vault/index.mdx
new file mode 100644
index 0000000000..3b6cf12fbf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/integrations/vault/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Vault Integration
+description: >-
+  Integrate Vault with Nomad to use tokens, password, certificates, API keys, and secrets stored in Vault. Configure Nomad to use Vault access control lists (ACLs) to secure your cluster. Learn how to configure Nomad agents and use Consul Template in your job specification.
+---
+
+# Vault Integration
+
+Many workloads require access to tokens, passwords, certificates, API keys, and
+other secrets. To enable secure, auditable and easy access to your secrets,
+Nomad integrates with HashiCorp's [Vault][]. Nomad servers and clients
+coordinate with Vault to derive a Vault token that has access to only the Vault
+policies the tasks needs. Nomad clients make the token available to the task and
+handle the tokens renewal.
+
+## Configuration
+
+In order to use Vault with Nomad, you will need to configure and install Vault
+separately from Nomad. Nomad does not run Vault for you.
+
+## Agent configuration
+
+To enable Vault integration, Nomad agents must be configured with
+[`vault`][] blocks. Each block can be enabled or disabled and configures how
+Nomad connects to the Vault cluster.
+
+## Dynamic configuration with secrets
+
+Nomad's job specification includes a [`template`][] block that uses a tool
+called [Consul Template][]. When used with Vault, this mechanism creates a
+convenient way to ship configuration files that are populated from Vault
+secrets.
+
+For more information on Nomad's template block please see the
+[`template` job specification documentation][].
+
+## Vault access control list (ACL)
+
+The Vault ACL system protects the cluster from unauthorized access. When
+enabled, both Vault and Nomad must be properly configured in order for their
+integrations to work.
+
+Refer to the [Vault ACL integration page][int_vault_acl] for more information.
+
+## Multiple vault clusters <EnterpriseAlert inline />
+
+Nomad Enterprise supports access to multiple Vault clusters. They can be
+configured using multiple [`vault`][] blocks with different `name` values. If a
+`name` is not provided, the cluster configuration is called `default`.
+
+Jobs that need access to Vault may specify which Vault cluster to use with the
+[`vault.cluster`][] parameter.
+
+## Compatibility
+
+* Nomad versions 1.4.0 and above are compatible with any currently supported
+  version of Vault.
+
+|              | Vault 1.13.0+ |
+|--------------|---------------|
+| Nomad 1.4.0+ | ✅            |
+
+[Consul Template]: https://github.com/hashicorp/consul-template
+[Vault]:  https://www.vaultproject.io/ 'Vault by HashiCorp'
+[`template` job specification documentation]: /nomad/docs/job-specification/template#vault-integration
+[`template`]: /nomad/docs/job-specification/template
+[`vault.cluster`]: /nomad/docs/job-specification/vault#cluster
+[`vault`]: /nomad/docs/configuration/vault 'Nomad Vault Configuration Block'
+[int_vault_acl]: /nomad/docs/integrations/vault/acl
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/action.mdx b/content/nomad/v1.9.x/content/docs/job-specification/action.mdx
new file mode 100644
index 0000000000..bb7f4c43da
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/action.mdx
@@ -0,0 +1,131 @@
+---
+layout: docs
+page_title: action Block - Job Specification
+description: The "action" block allows for executable commands that job authors can predefine for operators to subsequently run against their job.
+---
+
+# `action` Block
+
+<Placement groups={['job', 'group', 'task', 'action']} />
+
+The `action` block allows job authors to define custom commands. These commands
+can be executed by operators with the necessary permissions on a running
+allocation, offering a controlled way to interact with tasks.
+
+The name of the action can contain alphanumeric characters and dashes. This
+name must be unique within its task and must not exceed 128 characters.
+
+## `action` Parameters
+
+- `command` `(string: <required>)` - Specifies the command to be executed.
+- `args` `(array<string>: [])` - Provides a list of arguments to pass to the command.
+
+```hcl
+job "my-job" {
+  group "my-group" {
+    task "my-task" {
+      action "get-changelog" {
+        command = "/usr/bin/curl"
+        args = [
+          "-s",
+          "https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md"
+        ]
+      }
+      # ...
+    }
+  }
+}
+```
+
+## `action` Examples
+
+### Basic Action
+This example demonstrates a simple action that prints the current date and time:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "show-date" {
+      # ...
+      action "current-date" {
+        command = "/bin/date"
+      }
+    }
+  }
+}
+```
+
+### Action with Arguments
+Here, an action uses arguments to perform a specific task:
+
+```hcl
+job "example" {
+  # ...
+  group "demo" {
+    # ...
+    task "list-files" {
+      # ...
+      action "list-tmp" {
+        command = "/bin/ls"
+        args    = ["-l", "/tmp"]
+      }
+    }
+  }
+}
+```
+
+### Action with Template
+This advanced example demonstrates an action that fetches and formats the latest
+changelog from the Nomad GitHub repository using a shell script. It showcases
+the use of templating with embedded environment variables and a multi-line script.
+
+```hcl
+action "fetch-latest-nomad-changelog" {
+  command = "/bin/sh"
+  args    = ["-c", 
+    <<EOT
+curl -s https://raw.githubusercontent.com/hashicorp/nomad/main/CHANGELOG.md | 
+
+awk 'BEGIN{
+    # Setting record and field separators
+    RS="## "; FS="\n"; 
+    section=""; count=0
+}
+{
+    # Processing only the first 3 sections after the header
+    if (count < 3 && NR > 1){
+        # Splitting the version line into components
+        split($1, versionInfo, /[()]/);
+        version=versionInfo[1];
+        gsub(" ", "", version); # Removing spaces from version
+        releaseDate=versionInfo[2];
+        # Formatting URL components
+        urlVersion=version; gsub("\\.", "", urlVersion); # Remove dots from version
+        urlDate=releaseDate; gsub(" ", "-", urlDate); gsub(",", "", urlDate); # Replace spaces with hyphens and remove comma
+        # Counting items under each section
+        for(i=1; i<=NF; i++){
+            if($i ~ /^[A-Z ]+:$/){
+                gsub(":", "", $i);
+                section=$i;
+                itemCount[section]=0;
+            }
+            if(section && $i ~ /^\*/){
+                itemCount[section]++;
+            }
+        }
+        # Printing the extracted information
+        printf "Version: %s\nRelease Date: %s\n", version, releaseDate;
+        for (s in itemCount) {
+            printf "%d %s, ", itemCount[s], s;
+        }
+        printf "\nLink: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md#%s-%s\n\n", urlVersion, tolower(urlDate);
+        delete itemCount;  # Clear the itemCount array for the next version
+        count++;
+    }
+}'
+    EOT
+  ]
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/affinity.mdx b/content/nomad/v1.9.x/content/docs/job-specification/affinity.mdx
new file mode 100644
index 0000000000..a070254c07
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/affinity.mdx
@@ -0,0 +1,278 @@
+---
+layout: docs
+page_title: affinity Block - Job Specification
+description: |-
+  The "affinity" block allows restricting the set of eligible nodes.
+  Affinities may filter on attributes or metadata. Additionally affinities may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `affinity` Block
+
+<Placement
+  groups={[
+    ['job', 'affinity'],
+    ['job', 'group', 'affinity'],
+    ['job', 'group', 'task', 'affinity'],
+  ]}
+/>
+
+The `affinity` block allows operators to express placement preference for a set of nodes. Affinities may
+be expressed on [attributes][interpolation] or [client metadata][client-meta].
+Additionally affinities may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+```hcl
+job "docs" {
+  # Prefer nodes in the us-west1 datacenter
+  affinity {
+    attribute = "${node.datacenter}"
+    value     = "us-west1"
+    weight    = 100
+  }
+
+  group "example" {
+    # Prefer the "r1" rack
+    affinity {
+      attribute  = "${meta.rack}"
+      value     = "r1"
+      weight    = 50
+    }
+
+    task "server" {
+      # Prefer nodes where "my_custom_value" is greater than 3
+      affinity {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+        weight    = 50
+      }
+    }
+  }
+}
+```
+
+Affinities apply to task groups but may be specified within job and task blocks as well.
+Job affinities apply to all groups within the job. Task affinities apply to the whole task group
+that the task is a part of.
+
+Nomad will use affinities when computing scores for placement. Nodes that match affinities will
+have their scores boosted. Affinity scores are combined with other scoring factors such as bin packing.
+Operators can use weights to express relative preference across multiple affinities. If no nodes match a given affinity,
+placement is still successful. This is different from [constraints][constraint] where placement is
+restricted only to nodes that meet the constraint's criteria.
+
+## `affinity` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the affinity. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. The ordering is
+  compared lexically. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  regexp
+  set_contains_all
+  set_contains_any
+  version
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `weight` `(integer: 50)` - Specifies a weight for the affinity. The weight is used
+  during scoring and must be an integer between -100 to 100. Negative weights act as
+  anti affinities, causing nodes that match them to be scored lower. Weights can be used
+  when there is more than one affinity to express relative preference across them.
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for affinities. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall affinity evaluation.
+
+```hcl
+affinity {
+  operator = "..."
+}
+```
+
+- `"regexp"` - Specifies a regular expression affinity against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains_all"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_all"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"set_contains"` - Same as `set_contains_all`
+
+- `"set_contains_any"` - Specifies a contains affinity against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+    weight    = 50
+  }
+  ```
+
+- `"version"` - Specifies a version affinity against the attribute. This
+  supports a comma-separated list of values, including the pessimistic
+  operator. For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  affinity {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+    weight    = 50
+  }
+  ```
+
+## `affinity` Examples
+
+The following examples only show the `affinity` blocks. Remember that the
+`affinity` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example adds a preference for running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+affinity {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+  weight    = 50
+}
+```
+
+### Operating Systems
+
+This example adds a preference to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+affinity {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+  weight    = 50
+}
+
+affinity {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+  weight    = 100
+}
+```
+
+### Meta Data
+
+The following example adds a preference to running on nodes with specific rack metadata
+
+```hcl
+affinity {
+  attribute = "${meta.rack}"
+  value     = "rack1"
+  weight    = 50
+}
+```
+
+The following example adds a preference to running on nodes in a specific datacenter.
+
+```hcl
+affinity {
+  attribute = "${node.datacenter}"
+  value     = "us-west1"
+  weight    = 50
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in affinities. This example adds a preference to run this
+task on nodes that are memory-optimized on AWS.
+
+```hcl
+affinity {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+
+### Placement Details
+
+Operators can run `nomad alloc status -verbose` to get more detailed information on various
+factors, including affinities that affect the final placement.
+
+#### Example Placement Metadata
+
+The following is a snippet from the CLI output of `nomad alloc status -verbose <alloc-id>` showing scoring metadata.
+
+```text
+Placement Metrics
+Node                                  binpack  job-anti-affinity  node-reschedule-penalty  node-affinity  final score
+30bd48cc-d760-1096-9bab-13caac424af5  0.225    -0.6               0                        1              0.208
+f2aa8b59-96b8-202f-2258-d98c93e360ab  0.225    -0.6               0                        1              0.208
+86df0f74-15cc-3a0e-23f0-ad7306131e0d  0.0806   0                  0                        0              0.0806
+7d6c2e9e-b080-5995-8b9d-ef1695458b52  0.0806   0                  0                        0              0.0806
+```
+
+The placement score is affected by the following factors.
+
+- `bin-packing` - Scores nodes according to how well they fit requirements. Optimizes for using minimal number of nodes.
+- `job-anti-affinity` - A penalty added for additional instances of the same job on a node, used to avoid having too many instances
+  of a job on the same node.
+- `node-reschedule-penalty` - Used when the job is being rescheduled. Nomad adds a penalty to avoid placing the job on a node where
+  it has failed to run before.
+- `node-affinity` - Used when the criteria specified in the `affinity` block matches the node.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/artifact.mdx b/content/nomad/v1.9.x/content/docs/job-specification/artifact.mdx
new file mode 100644
index 0000000000..fc791862f5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/artifact.mdx
@@ -0,0 +1,287 @@
+---
+layout: docs
+page_title: artifact Block - Job Specification
+description: |-
+  The "artifact" block instructs Nomad to fetch and unpack a remote resource,
+  such as a file, tarball, or binary, and permits downloading artifacts from a
+  variety of locations using a URL as the input source.
+---
+
+# `artifact` Block
+
+<Placement groups={['job', 'group', 'task', 'artifact']} />
+
+The `artifact` block instructs Nomad to fetch and unpack a remote resource,
+such as a file, tarball, or binary. Nomad downloads artifacts using the popular
+[`go-getter`][go-getter] library, which permits downloading artifacts from a
+variety of locations using a URL as the input source.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      artifact {
+        source      = "https://example.com/file.tar.gz"
+        destination = "local/some-directory"
+        options {
+          checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+        }
+      }
+    }
+  }
+}
+```
+
+Nomad supports downloading `http`, `https`, `git`, `hg` and `S3` artifacts. If
+these artifacts are archived (`zip`, `tgz`, `bz2`, `xz`), they are
+automatically unarchived before the starting the task.
+
+## `artifact` Parameters
+
+- `destination` `(string: "local/")` - Specifies the directory path to
+  download the artifact, relative to the root of the [task's working
+  directory]. If omitted, the default value is to place the artifact in
+  `local/`. The destination is treated as a directory unless `mode` is set to
+  `file`. Source files will be downloaded into that directory path. For more
+  details on how the `destination` interacts with task drivers, see the
+  [Filesystem internals] documentation.
+
+- `mode` `(string: "any")` - One of `any`, `file`, or `dir`. If set to `file`
+  the `destination` must be a file, not a directory. By default the
+  `destination` will be `local/<filename>`.
+
+- `options` `(map<string|string>: nil)` - Specifies configuration parameters to
+  fetch the artifact. The key-value pairs map directly to parameters appended to
+  the supplied `source` URL. Please see the [`go-getter`
+  documentation][go-getter] for a complete list of options and examples.
+
+- `headers` `(map<string|string>: nil)` - Specifies HTTP headers to set when
+  fetching the artifact using `http` or `https` protocol. Please see the
+  [`go-getter` headers documentation][go-getter-headers] for more information.
+
+- `source` `(string: <required>)` - Specifies the URL of the artifact to download.
+  See [`go-getter`][go-getter] for details.
+
+- `chown` `(bool: false)` - Specifies whether Nomad should recursively `chown`
+  the downloaded artifact to be owned by the [`task.user`][task_user] uid and gid.
+
+## Operation Limits
+
+The client [`artifact`][client_artifact] configuration can set limits to
+specific artifact operations to prevent excessive data download or operation
+time.
+
+If a task's `artifact` retrieval exceeds one of those limits, the task will be
+interrupted and fail to start. Refer to the task events for more information.
+
+## `artifact` Examples
+
+The following examples only show the `artifact` blocks. Remember that the
+`artifact` block is only valid in the placements listed above.
+
+### Download File
+
+This example downloads the artifact from the provided URL and places it in
+`local/file.txt`. The `local/` path is relative to the [task's working
+directory].
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+}
+```
+
+To set HTTP headers in the request for the source the optional `headers` field
+can be configured.
+
+```hcl
+artifact {
+  source = "https://example.com/file.txt"
+
+  headers {
+    User-Agent    = "nomad-[${NOMAD_JOB_ID}]-[${NOMAD_GROUP_NAME}]-[${NOMAD_TASK_NAME}]"
+    X-Nomad-Alloc = "${NOMAD_ALLOC_ID}"
+  }
+}
+```
+
+To use HTTP basic authentication, preprend the username and password to the
+hostname in the URL. All special characters, including the username and
+password, must be URL encoded. For example, for a username `exampleUser` and
+the password `pass/word!`:
+
+```hcl
+artifact {
+  source = "https://exampleUser:pass%2Fword%21@example.com/file.txt"
+}
+```
+
+### Download using git
+
+This example downloads the artifact from the provided GitHub URL and places it at
+`local/repo`, as specified by the optional `destination` parameter.
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+}
+```
+
+To download from a private repo, sshkey needs to be set. The key must be
+base64-encoded string. On Linux, you can run `base64 -w0 <file>` to encode the
+file. Or use [HCL2](/nomad/docs/job-specification/hcl2)
+expressions to read and encode the key from a file on your machine:
+
+```hcl
+artifact {
+  # The git:: prefix forces go-getter's protocol detection to use the git ssh
+  # protocol. It can also automatically detect the protocol from the domain of
+  # some git hosting providers (such as GitHub) without the prefix.
+  source      = "git::git@bitbucket.org:example/nomad-examples"
+  destination = "local/repo"
+  options {
+    # Make sure that the system known hosts file is populated:
+    # ssh-keyscan github.com | sudo tee -a /etc/ssh/ssh_known_hosts
+    # https://github.com/hashicorp/go-getter/issues/55
+    sshkey = "${base64encode(file("/path/to/private-key"))}"
+  }
+}
+```
+
+To clone specific refs or at a specific depth, use the `ref` and `depth`
+options:
+
+```hcl
+artifact {
+  source      = "git::https://github.com/hashicorp/nomad-guides"
+  destination = "local/repo"
+  options {
+    ref = "main"
+    depth = 1
+  }
+}
+```
+
+### Download and Unarchive
+
+This example downloads and unarchives the result in `local/file`. Because the
+source URL is an archive extension, Nomad will automatically decompress it:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+}
+```
+
+To disable automatic unarchiving, set the `archive` option to false:
+
+```hcl
+artifact {
+  source = "https://example.com/file.tar.gz"
+  options {
+    archive = false
+  }
+}
+```
+
+### Download and Verify Checksums
+
+This example downloads an artifact and verifies the resulting artifact's
+checksum before proceeding. If the checksum is invalid, an error will be
+returned.
+
+```hcl
+artifact {
+  source = "https://example.com/file.zip"
+
+  options {
+    checksum = "md5:df6a4178aec9fbdc1d6d7e3634d1bc33"
+  }
+}
+```
+
+### Download from an S3-compatible Bucket
+
+These examples download artifacts from Amazon S3. There are several different
+types of [S3 bucket addressing][s3-bucket-addr] and [S3 region-specific
+endpoints][s3-region-endpoints]. Non-Amazon S3-compatible endpoints like [Minio]
+are supported, but you must explicitly set the "s3::" prefix.
+
+This example uses path-based notation on a publicly-accessible bucket:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-us-west-2.amazonaws.com/my_app.tar.gz"
+}
+```
+
+If a bucket requires authentication, you can avoid the use of credentials by
+using [EC2 IAM instance profiles][iam-instance-profiles]. If this is not possible,
+credentials may be supplied via the `options` parameter:
+
+```hcl
+artifact {
+  options {
+    aws_access_key_id     = "<id>"
+    aws_access_key_secret = "<secret>"
+    aws_access_token      = "<token>"
+  }
+}
+```
+
+To force the S3-specific syntax, use the `s3::` prefix:
+
+```hcl
+artifact {
+  source = "s3::https://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+Alternatively you can use virtual hosted style:
+
+```hcl
+artifact {
+  source = "s3://my-bucket-example.s3-eu-west-1.amazonaws.com/my_app.tar.gz"
+}
+```
+
+[DigitalOcean Spaces][do_spaces] provide S3-compatible object storage and can be
+used in conjunction with the `artifact` block. Given a bucket named
+`my-bucket-example` located in the `sfo3` region and a file named `my_app.tar.gz`,
+the following artifact block will work, provided the bucket and file are public.
+This uses the origin endpoint as detailed directly from Digital Ocean.
+
+```hcl
+artifact {
+  source = "https://my-bucket-example.sfo3.digitaloceanspaces.com/my_app.tar.gz"
+}
+```
+
+If the bucket or file are private, the artifact source string needs to be
+modified to add the `s3::` prefix. The bucket name is also moved to form part
+of the URL path component.
+
+```hcl
+artifact {
+  source = "s3::https://sfo3.digitaloceanspaces.com/my-bucket-example/my_app.tar.gz"
+}
+```
+
+## Environment
+
+The `artifact` downloader by default does not have access to the environment variables
+set for the Nomad client. Inheritance of environment variables can be managed through the [`artifact.set_environment_variables`][client_artifact]
+client configuration.
+
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[go-getter]: https://github.com/hashicorp/go-getter 'HashiCorp go-getter Library'
+[go-getter-headers]: https://github.com/hashicorp/go-getter#headers 'HashiCorp go-getter Headers'
+[minio]: https://www.minio.io/
+[s3-bucket-addr]: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro 'Amazon S3 Bucket Addressing'
+[s3-region-endpoints]: http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region 'Amazon S3 Region Endpoints'
+[iam-instance-profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html 'EC2 IAM instance profiles'
+[task's working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[task_user]: /nomad/docs/job-specification/task#user
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[do_spaces]: https://www.digitalocean.com/products/spaces
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/change_script.mdx b/content/nomad/v1.9.x/content/docs/job-specification/change_script.mdx
new file mode 100644
index 0000000000..3841867837
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/change_script.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: change_script Block - Job Specification
+description: The "change_script" block configures a script to be run on template re-render.
+---
+
+# `change_script` Block
+
+<Placement groups={['job', 'group', 'task', 'template', 'change_script']} />
+
+The `change_script` block allows operators to configure scripts that
+will be executed on template change. This block is only used when template
+`change_mode` is set to `script`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source      = "local/redis.conf.tpl"
+        destination = "local/redis.conf"
+        change_mode = "script"
+        change_script {
+          command       = "/bin/foo"
+          args          = ["-verbose", "-debug"]
+          timeout       = "5s"
+          fail_on_error = false
+        }
+      }
+    }
+  }
+}
+```
+
+## `change_script` Parameters
+
+- `command` `(string: "")` - Specifies the full path to a script or executable
+  that is to be executed on template change. The command must return exit code 0
+  to be considered successful. Path is relative to the driver, e.g., if running
+  with a container driver the path must be existing in the container.  This option
+  is required if `change_mode` is `script`.
+
+- `args` `(array<string>: [])` - List of arguments that are passed to the script
+  that is to be executed on template change.
+
+- `timeout` `(string: "5s")` - Timeout for script execution specified using a
+  label suffix like `"30s"` or `"1h"`.
+
+- `fail_on_error` `(bool: false)` - If `true`, Nomad will kill the task if the
+  script execution fails. If `false`, script failure will be logged but the task
+  will continue uninterrupted.
+
+### Template as a script example
+
+Below is an example of how a script can be embedded in a `data` block of another
+`template` block:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        data        = "{{key \"my_key\"}}"
+        destination = "local/test"
+        change_mode = "script"
+
+        change_script {
+          command = "/local/script.sh"
+        }
+      }
+
+      template {
+        data        = <<EOF
+#!/usr/bin/env bash
+echo "Running change_mode script"
+sleep 10
+echo "Done"
+EOF
+        destination = "local/script.sh"
+        perms       = "777"
+      }
+    }
+  }
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/check.mdx b/content/nomad/v1.9.x/content/docs/job-specification/check.mdx
new file mode 100644
index 0000000000..1e03d65c58
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/check.mdx
@@ -0,0 +1,476 @@
+---
+layout: docs
+page_title: check Block - Job Specification
+description: |-
+  The "check" block declares service check definition for a service registered into the Nomad or Consul service provider.
+---
+
+# `check` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'check'],
+    ['job', 'group', 'task', 'service', 'check'],
+  ]}
+/>
+
+The `check` block instructs Nomad to register a check associated with a [service][service]
+into the Nomad or Consul service provider.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" { to = 6379 }
+    }
+
+    service {
+      provider = "nomad"
+      name     = "redis"
+      port     = "db"
+      check {
+        name     = "redis_probe"
+        type     = "tcp"
+        interval = "10s"
+        timeout  = "1s"
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+    }
+  }
+}
+```
+
+### `check` Parameters
+
+- `address_mode` `(string: "host")` - Same as `address_mode` on `service`.
+  Unlike services, checks do not have an `auto` address mode as there's no way
+  for Nomad to know which is the best address to use for checks. Consul needs
+  access to the address for any HTTP or TCP checks. See
+  [below for details.](#using-driver-address-mode) Unlike `port`, this setting
+  is _not_ inherited from the `service`.
+  If the service `address` is set and the check `address_mode` is not set, the
+  service `address` value will be used for the check address.
+
+- `args` `(array<string>: [])` - Specifies additional arguments to the
+  `command`. This only applies to script-based health checks.
+
+- `check_restart` - See [`check_restart` block][check_restart_block].
+
+- `command` `(string: <varies>)` - Specifies the command to run for performing
+  the health check. The script must exit: 0 for passing, 1 for warning, or any
+  other value for a failing health check. This is required for script-based
+  health checks. Only supported in the Consul service provider.
+
+  ~> **Caveat:** The command must be the path to the command on disk, and no
+  shell exists by default. That means operators like `||` or `&&` are not
+  available. Additionally, all arguments must be supplied via the `args`
+  parameter. To achieve the behavior of shell operators, specify the command
+  as a shell, like `/bin/bash` and then use `args` to run the check.
+
+- `grpc_service` `(string: <optional>)` - What service, if any, to specify in
+  the gRPC health check. gRPC health checks require Consul 1.0.5 or later.
+
+- `grpc_use_tls` `(bool: false)` - Use TLS to perform a gRPC health check. May
+  be used with `tls_skip_verify` to use TLS but skip certificate verification.
+  May be used with `tls_server_name` to specify the ServerName to use for SNI
+  and validation of the certificate presented by the server being checked.
+
+- `initial_status` `(string: <enum>)` - Specifies the starting status of the
+  service. Valid options are `passing`, `warning`, and `critical`. Omitting
+  this field (or submitting an empty string) will result in the Consul default
+  behavior, which is `critical`. Only supported in the Consul service provider.
+  In the Nomad service provider, the initial status of a check is `pending`
+  until Nomad produces an initial check status result.
+
+- `success_before_passing` `(int:0)` - The number of consecutive successful checks
+  required before Consul will transition the service status to [`passing`][consul_success_before_passing].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_critical` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`critical`][consul_failure_before_critical].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `failures_before_warning` `(int:0)` - The number of consecutive failing checks
+  required before Consul will transition the service status to [`warning`][consul_failure_before_warning].
+  Only supported by the Consul service provider and not applicable for health checks of type "script".
+
+- `interval` `(string: <required>)` - Specifies the frequency of the health checks
+  that Consul or Nomad service provider will perform. This is specified using a label
+  suffix like "30s" or "1h". This must be greater than or equal to "1s".
+
+- `method` `(string: "GET")` - Specifies the HTTP method to use for HTTP
+  checks. Must be a valid HTTP method.
+
+- `body` `(string: "")` - Specifies the HTTP body to use for HTTP checks.
+
+- `name` `(string: "service: <name> check")` - Specifies the name of the health
+  check. If the name is not specified Nomad generates one based on the service name.
+
+- `path` `(string: <varies>)` - Specifies the path of the HTTP endpoint which
+  will be queried to observe the health of a service. Nomad will automatically
+  add the IP of the service and the port, so this is just the relative URL to
+  the health check endpoint. This is required for HTTP-based health checks.
+
+- `expose` `(bool: false)` - Specifies whether an [Expose Path](/nomad/docs/job-specification/expose#path-parameters)
+  should be automatically generated for this check. Only compatible with
+  Connect-enabled task-group services using the default Connect proxy. If set, check
+  [`type`](#type) must be `http` or `grpc`, and check `name` must be set.
+  Only supported in the Consul service provider.
+
+- `port` `(string: <varies>)` - Specifies the label of the port on which the
+  check will be performed. Note this is the _label_ of the port and not the port
+  number unless `address_mode = driver`. The port label must match one defined
+  in the [`network`][network] block. If a port value was declared on the
+  `service`, this will inherit from that value if not supplied. If supplied,
+  this value takes precedence over the `service.port` value. This is useful for
+  services which operate on multiple ports. `grpc`, `http`, and `tcp` checks
+  require a port while `script` checks do not. Checks will use the host IP and
+  ports by default. Numeric ports may be used if `address_mode="driver"` is set
+  on the check.
+
+- `protocol` `(string: "http")` - Specifies the protocol for the HTTP-based
+  health checks. Valid options are `http` and `https`.
+
+- `task` `(string: "")` - Specifies the task associated with this
+  check. Scripts are executed within the task's environment, and
+  `check_restart` blocks will apply to the specified task. Inherits
+  the [`service.task`][service_task] value if not set. Must be unset
+  or equivalent to `service.task` in task-level services.
+
+- `timeout` `(string: <required>)` - Specifies how long to wait for a health check
+  query to succeed. This is specified using a label suffix like "30s" or "1h". This
+  must be greater than or equal to "1s"
+
+  ~> **Caveat:** Script checks use the task driver to execute in the task's
+  environment. For task drivers with namespace isolation such as `docker` or
+  `exec`, setting up the context for the script check may take an unexpectedly
+  long amount of time (a full second or two), especially on busy hosts. The
+  timeout configuration must allow for both this setup and the execution of
+  the script. Operators should use long timeouts (5 or more seconds) for script
+  checks, and monitor telemetry for
+  `client.allocrunner.taskrunner.tasklet_timeout`.
+
+- `type` `(string: <required>)` - This indicates the check types supported by
+  Nomad. For Consul service checks, valid options are `grpc`, `http`, `script`,
+  and `tcp`. For Nomad service checks, valid options are `http` and `tcp`.
+
+- `tls_server_name` `(string: "")` - Indicates the ServerName to use for SNI and
+  validation of the certificate presented by the server being checked, when
+  performing TLS enabled checks (`https` and `grpc` with `grpc_use_tls`). If left
+  unspecified, the ServerName will be inferred from the address of the server
+  being checked unless the address is an IP address. There are two common cases
+  where this is beneficial:
+
+    - When the check address contains an IP, `tls_server_name` can be specified
+      for SNI. Note: setting `tls_server_name` will also override the hostname
+      used to verify the certificate presented by the server being checked.
+
+    - When the check address contains a hostname which isn't be present in the
+      SAN (Subject Alternative Name) field of the certificate presented by the
+      server being checked. Note: setting `tls_server_name` will also override
+      the hostname used for SNI.
+
+  This field is only supported in the Consul service provider.
+
+- `tls_skip_verify` `(bool: false)` - Skip verification of certificates for
+  `https` and `grpc` with `grpc_use_tls` checks.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in the service provider and is only used to determine the check's
+  health during an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+#### `header` Block
+
+HTTP checks may include a `header` block to set HTTP headers. The `header`
+block parameters have lists of strings as values. Multiple values will cause
+the header to be set multiple times, once for each value.
+
+```hcl
+service {
+  # ...
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### HTTP Health Check
+
+This example shows a service with an HTTP health check. This will query the
+service on the IP and port registered with Nomad at `/_healthz` every 5 seconds,
+giving the service a maximum of 2 seconds to return a response, and include an
+Authorization header. Any non-2xx code is considered a failure.
+
+```hcl
+service {
+  check {
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    header {
+      Authorization = ["Basic ZWxhc3RpYzpjaGFuZ2VtZQ=="]
+    }
+  }
+}
+```
+
+### Multiple Health Checks
+
+This example shows a service with multiple health checks defined. All health
+checks must be passing in order for the service to register as healthy.
+
+```hcl
+service {
+  check {
+    name     = "HTTP Check"
+    type     = "http"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+  }
+
+  check {
+    name     = "HTTPS Check"
+    type     = "http"
+    protocol = "https"
+    port     = "lb"
+    path     = "/_healthz"
+    interval = "5s"
+    timeout  = "2s"
+    method   = "POST"
+  }
+
+  check {
+    name      = "Postgres Check"
+    type      = "script"
+    command   = "/usr/local/bin/pg-tools"
+    args      = ["verify", "database", "prod", "up"]
+    interval  = "5s"
+    timeout   = "2s"
+    on_update = "ignore_warnings"
+  }
+}
+```
+
+### gRPC Health Check
+
+gRPC health checks use the same host and port behavior as `http` and `tcp`
+checks, but gRPC checks also have an optional gRPC service to health check. Not
+all gRPC applications require a service to health check.
+
+```hcl
+service {
+  check {
+    type            = "grpc"
+    port            = "rpc"
+    interval        = "5s"
+    timeout         = "2s"
+    grpc_service    = "example.Service"
+    grpc_use_tls    = true
+    tls_skip_verify = true
+  }
+}
+```
+
+In this example Consul would health check the `example.Service` service on the
+`rpc` port defined in the task's [network resources][network] block. See
+[Using Driver Address Mode](#using-driver-address-mode) for details on address
+selection.
+
+### Script Checks with Shells
+
+Note that script checks run inside the task. If your task is a Docker container,
+the script will run inside the Docker container. If your task is running in a
+chroot, it will run in the chroot. Please keep this in mind when authoring check
+scripts.
+
+This example shows a service with a script check that is evaluated and interpolated in a shell; it
+tests whether a file is present at `${HEALTH_CHECK_FILE}` environment variable:
+
+```hcl
+service {
+  check {
+    type    = "script"
+    command = "/bin/bash"
+    args    = ["-c", "test -f ${HEALTH_CHECK_FILE}"]
+  }
+}
+```
+
+Using `/bin/bash` (or another shell) is required here to interpolate the `${HEALTH_CHECK_FILE}` value.
+
+The following examples of `command` fields **will not work**:
+
+```hcl
+# invalid because command is not a path
+check {
+  type    = "script"
+  command = "test -f /tmp/file.txt"
+}
+
+# invalid because path will not be interpolated
+check {
+  type    = "script"
+  command = "/bin/test"
+  args    = ["-f", "${HEALTH_CHECK_FILE}"]
+}
+```
+
+### Healthiness versus Readiness Checks
+
+Multiple checks for a service can be composed to create healthiness and readiness
+checks by configuring [`on_update`][on_update] for the check.
+
+```hcl
+service {
+  # This is a healthiness check that will be used to verify the service
+  # is responsive to tcp connections and behaving as expected.
+  check {
+    name     = "connection_tcp"
+    type     = "tcp"
+    port     = 6379
+    interval = "10s"
+    timeout  = "2s"
+  }
+
+  # This is a readiness check that is used to verify that, for example, the
+  # application has elected a leader by making a request to its /leader endpoint.
+  # Failures of this check are ignored during deployments.
+  check {
+    name      = "leader_elected"
+    type      = "http"
+    path      = "/leader"
+    interval  = "10s"
+    timeout   = "2s"
+    on_update = "ignore"
+  }
+}
+```
+
+For checks registered into the Nomad service provider, the status information will
+indicate `Mode = readiness` for readiness checks and `Mode = healthiness` for health
+checks.
+
+### Check status on CLI
+
+For checks registered into the Nomad service provider, the status information of
+checks can be viewed per-allocation. The `alloc status` command now includes
+summary information for Nomad service checks.
+
+```shell-session
+$ nomad alloc status <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Nomad Service Checks:
+Service   Task     Name          Mode         Status
+database  task     db_tcp_probe  readiness    success
+web       (group)  healthz       healthiness  failure
+web       (group)  index-page    healthiness  success
+```
+
+</CodeBlockConfig>
+
+The `alloc checks` command can be used for viewing complete check status information
+for all checks in an allocation.
+
+```shell-session
+$ nomad alloc checks <allocation-id>
+```
+
+<CodeBlockConfig hideClipboard>
+
+```plaintext
+Status of 3 Nomad Service Checks
+
+ID         =  d8651d93a50b9e28375a7beb9418c418
+Name       =  db_tcp_probe
+Group      =  example.group[0]
+Task       =  task
+Service    =  database
+Status     =  success
+Mode       =  readiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: tcp ok
+
+ID          =  0413b61bda7014f02671675d7e146373
+Name        =  index-page
+Group       =  example.group[0]
+Task        =  (group)
+Service     =  web
+Status      =  success
+StatusCode  =  200
+Mode        =  healthiness
+Timestamp   =  2022-08-22T10:41:23-05:00
+Output      =  nomad: http ok
+
+ID         =  c3cce3f0c97975f84bbf39bdd50deaea
+Name       =  healthz
+Group      =  example.group[0]
+Task       =  (group)
+Service    =  web
+Status     =  failure
+Mode       =  healthiness
+Timestamp  =  2022-08-22T10:41:23-05:00
+Output     =  nomad: Get "http://:9999/": dial tcp :9999: connect: connection refused
+```
+
+</CodeBlockConfig>
+
+---
+
+<sup>
+  <small>1</small>
+</sup>
+<small>
+  {' '}
+  Script checks are not supported for the QEMU driver since the Nomad client
+  does not have access to the file system of a task for that driver.
+</small>
+
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_success_before_passing]: /consul/api-docs/agent/check#successbeforepassing
+[consul_failure_before_critical]: /consul/api-docs/agent/check#failuresbeforecritical
+[consul_failure_before_warning]: /consul/api-docs/agent/check#failuresbeforewarning
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[service]: /nomad/docs/job-specification/service
+[service_task]: /nomad/docs/job-specification/service#task-1
+[on_update]: /nomad/docs/job-specification/service#on_update
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/check_restart.mdx b/content/nomad/v1.9.x/content/docs/job-specification/check_restart.mdx
new file mode 100644
index 0000000000..8964fa40ea
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/check_restart.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: check_restart Block - Job Specification
+description: |-
+  The "check_restart" block instructs Nomad when to restart tasks with
+  unhealthy service checks.
+---
+
+# `check_restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'task', 'service', 'check_restart'],
+    ['job', 'group', 'task', 'service', 'check', 'check_restart'],
+  ]}
+/>
+
+The `check_restart` block instructs Nomad when to restart tasks with unhealthy
+service checks. When a health check in Nomad or Consul has been unhealthy for the `limit`
+specified in a `check_restart` block, it is restarted according to the task group's
+[`restart` policy][restart_block]. The `check_restart` settings apply to
+[`check`s][check_block], but may also be placed on [`service`s][service_block]
+to apply to all checks on a service. If `check_restart` is set on both the check
+and service, the blocks are merged with the check values taking precedence.
+
+```hcl
+job "mysql" {
+  group "mysqld" {
+
+    restart {
+      attempts = 3
+      delay    = "10s"
+      interval = "10m"
+      mode     = "fail"
+    }
+
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "script"
+          name     = "check_table"
+          command  = "/usr/local/bin/check_mysql_table_status"
+          args     = ["--verbose"]
+          interval = "60s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+- `limit` `(int: 0)` - Restart task when a health check has failed `limit`
+  times. For example 1 causes a restart on the first failure. The default,
+  `0`, disables health check based restarts. Failures must be consecutive. A
+  single passing check will reset the count, so flapping services may not be
+  restarted.
+
+- `grace` `(string: "1s")` - Duration to wait after a task starts or restarts
+  before checking its health.
+
+- `ignore_warnings` `(bool: false)` - By default checks with both `critical`
+  and `warning` statuses are considered unhealthy. Setting `ignore_warnings = true`
+  treats a `warning` status like `passing` and will not trigger a restart. Only
+  available in the Consul service provider.
+
+## Example Behavior
+
+Using the example `mysql` above would have the following behavior:
+
+```hcl
+check_restart {
+  # ...
+  grace = "90s"
+  # ...
+}
+```
+
+When the `server` task first starts and is registered in Consul, its health
+will not be checked for 90 seconds. This gives the server time to startup.
+
+```hcl
+check_restart {
+  limit = 3
+  # ...
+}
+```
+
+After the grace period if the script check fails, it has 180 seconds (`60s interval * 3 limit`)
+to pass before a restart is triggered. Once a restart is triggered the task group's
+[`restart` policy][restart_block] takes control:
+
+```hcl
+restart {
+  # ...
+  delay    = "10s"
+  # ...
+}
+```
+
+The [`restart` block][restart_block] controls the restart behavior of the
+task. In this case it will stop the task and then wait 10 seconds before
+starting it again.
+
+Once the task restarts Nomad waits the `grace` period again before starting to
+check the task's health.
+
+```hcl
+restart {
+  attempts = 3
+  # ...
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+If the check continues to fail, the task will be restarted up to `attempts`
+times within an `interval`. If the `restart` attempts are reached within the
+`limit` then the `mode` controls the behavior. In this case the task would fail
+and not be restarted again. See the [`restart` block][restart_block] for
+details.
+
+[check_block]: /nomad/docs/job-specification/service#check-parameters 'check block'
+[gh-9176]: https://github.com/hashicorp/nomad/issues/9176
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[service_block]: /nomad/docs/job-specification/service 'service block'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/connect.mdx b/content/nomad/v1.9.x/content/docs/job-specification/connect.mdx
new file mode 100644
index 0000000000..78920e1a76
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/connect.mdx
@@ -0,0 +1,262 @@
+---
+layout: docs
+page_title: connect Block - Job Specification
+description: The "connect" block allows specifying options for Consul Connect integration
+---
+
+# `connect` Block
+
+<Placement groups={['job', 'group', 'service', 'connect']} />
+
+The `connect` block allows configuring various options for
+[Consul Connect](/nomad/docs/integrations/consul-connect). It is
+valid only within the context of a service definition at the task group
+level. For using `connect` when Consul ACLs are enabled, be sure to read through
+the [Secure Nomad Jobs with Consul Connect](/nomad/tutorials/integrate-consul/consul-service-mesh)
+guide.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `connect` Parameters
+
+Used to configure a connect service. Only one of `native`, `sidecar_service`,
+or `gateway` may be realized per `connect` block.
+
+- `native` - `(bool: false)` - This is used to configure the service as supporting
+  [Connect Native](/consul/docs/connect/native) applications.
+
+- `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
+  configure the sidecar service created by Nomad for Consul Connect.
+
+- `sidecar_task` - <code>([sidecar_task][]:nil)</code> - This modifies the
+  task configuration of the Envoy proxy created as a sidecar or gateway.
+
+- `gateway` - <code>([gateway][]:nil)</code> - This is used to configure the
+  gateway service created by Nomad for Consul Connect.
+
+## `connect` Examples
+
+### Using Connect Native
+
+The following example is a minimal service block for a
+[Consul Connect Native](/consul/docs/connect/native)
+application implemented by a task named `generate`.
+
+```hcl
+service {
+  name = "uuid-api"
+  port = "${NOMAD_PORT_api}"
+  task = "generate"
+
+  connect {
+    native = true
+  }
+}
+```
+
+### Using Sidecar Service
+
+The following example is a minimal connect block with defaults and is
+sufficient to start an Envoy proxy sidecar for allowing incoming connections
+via Consul Connect.
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying [`upstreams`][upstreams].
+
+```hcl
+  connect {
+     sidecar_service {
+       proxy {
+         upstreams {
+           destination_name = "count-api"
+           local_bind_port = 8080
+         }
+       }
+     }
+  }
+```
+
+The following is the complete `countdash` example. It includes an API service
+and a frontend Dashboard service which connects to the API service as a Connect
+upstream. Once running, the dashboard is accessible at `localhost:9002`.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        type     = "http"
+        name     = "api-health"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+### Using a Gateway
+
+The following is an example service block for creating and using a connect ingress
+gateway. It includes a gateway service definition and an api service fronted by
+the gateway. Once running, the gateway can be used to reach the api service by first
+looking up the gateway Consul DNS address, e.g.
+
+```
+curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+```
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+          ingress {
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Limitations
+
+[gateway]: /nomad/docs/job-specification/gateway
+
+[gh-7221]: https://github.com/hashicorp/nomad/issues/7221
+
+[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
+
+[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
+
+[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
+
+[native]: /consul/docs/connect/native
+
+[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
+
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
+
+[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
+
+[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/constraint.mdx b/content/nomad/v1.9.x/content/docs/job-specification/constraint.mdx
new file mode 100644
index 0000000000..f09e253aa7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/constraint.mdx
@@ -0,0 +1,322 @@
+---
+layout: docs
+page_title: constraint Block - Job Specification
+description: |-
+  The "constraint" block allows restricting the set of eligible nodes.
+  Constraints may filter on attributes or metadata. Additionally constraints may
+  be specified at the job, group, or task levels for ultimate flexibility.
+---
+
+# `constraint` Block
+
+<Placement
+  groups={[
+    ['job', 'constraint'],
+    ['job', 'group', 'constraint'],
+    ['job', 'group', 'task', 'constraint'],
+  ]}
+/>
+
+The `constraint` allows restricting the set of eligible nodes. Constraints may
+filter on [attributes][interpolation] or [client metadata][client-meta].
+Additionally constraints may be specified at the [job][job], [group][group], or
+[task][task] levels for ultimate flexibility.
+
+<Warning>
+
+**It is possible to define irreconcilable constraints in a job.**
+
+For example, specifying different [`${attr.unique.hostname}`][node-variables]
+constraints at the task level will cause a job to be unplaceable because all
+[tasks within a group are scheduled on the same client node][group].
+</Warning>
+
+```hcl
+job "docs" {
+  # All tasks in this job must run on linux.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    # All groups in this job should be scheduled on different hosts.
+    constraint {
+      operator  = "distinct_hosts"
+      value     = "true"
+    }
+
+    task "server" {
+      # All tasks must run where "my_custom_value" is greater than 3.
+      constraint {
+        attribute = "${meta.my_custom_value}"
+        operator  = ">"
+        value     = "3"
+      }
+    }
+  }
+}
+```
+
+Placing constraints at both the job level and at the group level is redundant
+since constraints are applied hierarchically. The job constraints will affect
+all groups (and tasks) in the job.
+
+## `constraint` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to examine for the constraint. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `operator` `(string: "=")` - Specifies the comparison operator. If the operator
+  is one of `>, >=, <, <=`, the ordering is compared numerically if the operands
+  are both integers or both floats, and lexically otherwise. Possible values include:
+
+  ```text
+  =
+  !=
+  >
+  >=
+  <
+  <=
+  distinct_hosts
+  distinct_property
+  regexp
+  set_contains
+  set_contains_any
+  version
+  semver
+  is_set
+  is_not_set
+  ```
+
+  For a detailed explanation of these values and their behavior, please see
+  the [operator values section](#operator-values).
+
+- `value` `(string: "")` - Specifies the value to compare the attribute against
+  using the specified operation. This can be a literal value, another attribute,
+  or any [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+### `operator` Values
+
+This section details the specific values for the "operator" parameter in the
+Nomad job specification for constraints. The operator is always specified as a
+string, but the string can take on different values which change the behavior of
+the overall constraint evaluation.
+
+```hcl
+constraint {
+  operator = "..."
+}
+```
+
+- `"distinct_hosts"` - Instructs the scheduler to not co-locate any groups on
+  the same machine. When specified as a job constraint, it applies to all groups
+  in the job. When specified as a group constraint, the effect is constrained to
+  that group. This constraint can not be specified at the task level. Note that
+  the `attribute` parameter should be omitted when using this constraint.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_hosts"
+    value     = "true"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+      distinct_hosts = true
+  }
+  ```
+
+- `"distinct_property"` - Instructs the scheduler to select nodes that have a
+  distinct value of the specified property. The `value` parameter specifies how
+  many allocations are allowed to share the value of a property. The `value`
+  must be 1 or greater and if omitted, defaults to 1. When specified as a job
+  constraint, it applies to all groups in the job. When specified as a group
+  constraint, the effect is constrained to that group. This constraint can not
+  be specified at the task level.
+
+  ```hcl
+  constraint {
+    operator  = "distinct_property"
+    attribute = "${meta.rack}"
+    value     = "3"
+  }
+  ```
+
+  The constraint may also be specified as follows for a more compact
+  representation:
+
+  ```hcl
+  constraint {
+    distinct_property = "${meta.rack}"
+    value             = "3"
+  }
+  ```
+
+- `"regexp"` - Specifies a regular expression constraint against the attribute.
+  The syntax of the regular expressions accepted is the same general syntax used
+  by Perl, Python, and many other languages. More precisely, it is the syntax
+  accepted by RE2 and described at in the [Google RE2
+  syntax](https://golang.org/s/re2syntax).
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "regexp"
+    value     = "[a-z0-9]"
+  }
+  ```
+
+- `"set_contains"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **all** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"set_contains_any"` - Specifies a contains constraint against the attribute. The
+  attribute and the list being checked are split using commas. This will check
+  that the given attribute contains **any** of the specified elements.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "set_contains_any"
+    value     = "a,b,c"
+  }
+  ```
+
+- `"version"` - Specifies a version constraint against the attribute. This
+  supports a comma-separated list of constraints, including the pessimistic
+  operator. `version` will not consider a prerelease (eg `1.6.0-beta`)
+  sufficient to match a non-prerelease constraint (eg `>= 1.0`). Use the
+  `semver` constraint for strict [Semantic Versioning 2.0][semver2] ordering.
+  For more examples please see the [go-version
+  repository](https://github.com/hashicorp/go-version) for more specific
+  examples.
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "version"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"semver"` - Specifies a version constraint against the attribute. Only
+  [Semantic Versioning 2.0][semver2] compliant versions and comparison
+  operators are supported, so there is no pessimistic operator. Unlike `version`,
+  this operator considers prereleases (eg `1.6.0-beta`) sufficient to satisfy
+  non-prerelease constraints (eg `>= 1.0`). _Added in Nomad v0.10.2._
+
+  ```hcl
+  constraint {
+    attribute = "..."
+    operator  = "semver"
+    value     = ">= 0.1.0, < 0.2"
+  }
+  ```
+
+- `"is_set"` - Specifies that a given attribute must be present. This can be
+  combined with the `"!="` operator to require that an attribute has been set
+  before checking for equality. The default behavior for `"!="` is to include
+  nodes that don't have that attribute set.
+
+- `"is_not_set"` - Specifies that a given attribute must not be present.
+
+## `constraint` Examples
+
+The following examples only show the `constraint` blocks. Remember that the
+`constraint` block is only valid in the placements listed above.
+
+### Kernel Data
+
+This example restricts the task to running on nodes which have a kernel version
+higher than "3.19".
+
+```hcl
+constraint {
+  attribute = "${attr.kernel.version}"
+  operator  = "version"
+  value     = "> 3.19"
+}
+```
+
+### Distinct Property
+
+A potential use case of the `distinct_property` constraint is to spread a
+service with `count > 1` across racks to minimize correlated failure. Nodes can
+be annotated with which rack they are on using [custom client
+metadata][client-meta] with values such as "rack-12-1", "rack-12-2", etc.
+The following constraint would assure that an individual rack is not running
+more than 2 instances of the task group.
+
+```hcl
+constraint {
+  distinct_property = "${meta.rack}"
+  value             = "2"
+}
+```
+
+### Operating Systems
+
+This example restricts the task to running on nodes that are running Ubuntu
+14.04
+
+```hcl
+constraint {
+  attribute = "${attr.os.name}"
+  value     = "ubuntu"
+}
+
+constraint {
+  attribute = "${attr.os.version}"
+  value     = "14.04"
+}
+```
+
+### Cloud Metadata
+
+When possible, Nomad populates node attributes from the cloud environment. These
+values are accessible as filters in constraints. This example constrains this
+task to only run on nodes that are memory-optimized on AWS.
+
+```hcl
+constraint {
+  attribute = "${attr.platform.aws.instance-type}"
+  value     = "m4.xlarge"
+}
+```
+
+### User-Specified Metadata
+
+This example restricts the task to running on nodes where the binaries for
+redis, cypress, and nginx are all cached locally. This particular example is
+utilizing [custom client metadata][client-meta].
+
+```hcl
+constraint {
+  attribute    = "${meta.cached_binaries}"
+  set_contains = "redis,cypress,nginx"
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[client-meta]: /nomad/docs/configuration/client#custom-metadata-and-node-class 'Nomad Custom Metadata and Node Class'
+[semver2]: https://semver.org/spec/v2.0.0.html 'Semantic Versioning 2.0'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/consul.mdx b/content/nomad/v1.9.x/content/docs/job-specification/consul.mdx
new file mode 100644
index 0000000000..84b01eeb06
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/consul.mdx
@@ -0,0 +1,304 @@
+---
+layout: docs
+page_title: consul Block - Job Specification
+description: |-
+  The "consul" block allows the group or task to specify that it requires a token
+  from a HashiCorp Consul server. Nomad will automatically retrieve a Consul token
+  for the group or task.
+---
+
+# `consul` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'consul'],
+    ['job', 'group', 'task', 'consul'],
+  ]}
+/>
+
+The `consul` block specifies [Consul][] configuration options specific to a
+task. If specified at the `group` level, the configuration will apply to all
+tasks and services within the group unless a task has its own `consul` block. A
+task-level `consul` block will entirely override a group-level `consul` block.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      consul {
+        cluster   = "default"
+        namespace = "default"
+        partition = "default"
+      }
+    }
+  }
+}
+```
+
+## Workload Identity
+
+Starting in Nomad 1.7, Nomad clients will use a task or service's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+service or task when the following conditions are met:
+
+* For services, if either the [`consul.service_identity`][] is configured on the
+  Nomad servers or the service includes an `identity` block.
+* For tasks, if the [`consul.task_identity`][] is configured on the Nomad
+  servers, or the task includes an [`identity`][] block with the `name` field
+  set to `consul_default` (or `consul_$clusterName` for non-default Consul
+  clusters in Nomad Enterprise).
+
+As a fallback if none of these conditions are met, the Nomad client will instead
+use, in order of preference:
+
+* The token provided by the [`-consul-token`][flag_consul_token] flag for the
+  `nomad job run` command.
+* The Consul token as configured in the agent's [`consul.token`][] configuration.
+* The Consul token as configured by the agent's `CONSUL_HTTP_TOKEN` environment variable.
+
+To avoid failed deployments, you should first set up an authentication method
+and binding rules in Consul before configuring the Nomad servers with
+`consul.task_identity` and `consul.service_identity`. Refer to [Configuring Consul
+Authentication][] for more details.
+
+<Warning>
+
+Starting in Nomad 1.10, the fallback options to use the -consul-token flag when
+submitting a job, the agent's consul.token configuration, or the
+CONSUL_HTTP_TOKEN environment variable, will be removed.  This means service and
+template blocks will not be able to use the agent's Consul token or one provided
+by the job submitter. You should be prepared to migrate to the Workload Identity
+workflow for Consul and Vault before upgrading to Nomad 1.10. Refer to
+[Migrating to Using Workload Identity with Consul] for more information.
+
+</Warning>
+
+### Access to Token
+
+The Nomad client will make the Consul token available to the task by writing it
+to the secret directory at `secrets/consul_token` and by injecting a
+`CONSUL_TOKEN` environment variable in the task.
+
+If the Nomad cluster is [configured][config_consul_namespace] to use [Consul Namespaces][], a
+`CONSUL_NAMESPACE` environment variable will be injected whenever `CONSUL_TOKEN`
+is set.
+
+The [`template`][template] block can use the Consul token as well.
+
+### `consul` Parameters
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use. The Nomad client will retrieve a Consul token from the
+  cluster configured in the agent configuration with the same
+  [`consul.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - The Consul namespace in
+  which group and task-level services within the group will be registered. Use
+  of `template` to access Consul KV will read from the specified Consul
+  namespace.  Specifying `namespace` takes precedence over the
+  [`-consul-namespace`][flag_consul_namespace] command line argument in `job
+  run`. In Nomad Community Edition, this field is ignored.
+
+- `partition` `(string: "")` - When this field is set, a constraint will be
+  added to the group or task to ensure that the allocation is placed on a Nomad
+  client that has a Consul Enterprise agent in the specified Consul [admin
+  partition][]. Using this field requires the following:
+
+  - [Consul Enterprise]
+  - Workload identity integration. The `partition` field does not work
+    with a legacy Consul token. Refer to [Nomad Workload Identities] for more
+    information on integrating Nomad's workload identity with Consul authentication.
+
+## `consul` Examples
+
+The following examples only show the `consul` blocks or other relevant
+blocks. Remember that the `consul` block is only valid in the placements listed
+above.
+
+### Consul Token for Templates
+
+This example tells the Nomad client to obtain a Consul token using the task's
+Workload Identity. The token is available to the task via the canonical
+environment variable `CONSUL_TOKEN` and written to disk at
+`secrets/consul_token`. The `template` block will use the same Consul
+token. Note that the `identity.name` is set to `"consul_default"`, which tells
+the Nomad client to use this identity when making requests to the default Consul
+cluster.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      identity {
+        name = "consul_default"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.task_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted in this case.
+
+```hcl
+job "example" {
+  group "app" {
+    task "web" {
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+  }
+}
+```
+
+### Consul Token for Group Services
+
+This example tells the Nomad client to obtain a Consul Service Identity token
+using the service's Workload Identity. The Consul token will be used to register
+the service with Consul and configure any [Connect][] sidecar tasks for that
+service.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+      identity {}
+    }
+  }
+}
+```
+
+The following example has the same behavior as the example above, but assumes
+that the server has a `consul.service_identity` block configured. Note that both
+the `consul` and `identity` blocks can be omitted for the service in this case.
+
+```hcl
+job "example" {
+  group "web" {
+    service {
+      port = "www"
+    }
+  }
+}
+```
+
+### Consul Namespace
+
+This example shows specifying a particular Consul namespace or Consul cluster
+for different tasks within a group.
+
+<EnterpriseAlert />
+
+The `template` block in the `web` task will use the default Consul cluster, and
+will obtain a token that allows it access to the `engineering/frontend` Consul
+namespace. The `template` block in the `app` task will use the Consul cluster
+named `prod-apps`, and will obtain a token that allows it access to the
+`engineering/apps` Consul namespace.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    task "web" {
+
+      consul {
+        namespace = "engineering/frontend"
+      }
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      consul {
+        namespace = "engineering/apps"
+        cluster   = "prod-apps"
+      }
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+### Consul Admin Partition
+
+This example demonstrates how to configure Consul admin partitions for different
+tasks within a group. The Consul client agent must separately specify the admin
+partition in the agent configuration. Refer to the Consul documentation's
+[agent configuration reference][] for more information.
+
+<EnterpriseAlert />
+
+In the following example, the `web` and `app` tasks use the default Consul cluster
+and obtain a token that allows access to the `prod` admin partition in Consul. The
+Consul configuration occurs at the `group` level because tasks are placed together
+on the same Allocation. If you configure tasks with separate `consul` blocks, the
+`partition` field must be the same in both blocks.
+
+```hcl
+job "docs" {
+  group "example" {
+
+    consul {
+      cluster   = "default"
+      namespace = "default"
+      partition = "prod"
+    }
+
+    task "web" {
+
+      template {
+        data        = "FRONTEND_NAME={{key \"fe/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+    task "app" {
+
+      template {
+        data        = "APP_NAME={{key \"app/name\"}}"
+        destination = "local/config.txt"
+      }
+    }
+
+  }
+}
+```
+
+[Consul]: https://www.consul.io/ "Consul by HashiCorp"
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`identity`]: /nomad/docs/job-specification/identity
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[flag_consul_token]: /nomad/docs/commands/job/run#consul-token
+[`consul.token`]: /nomad/docs/configuration/consul#token
+[Configuring Consul Authentication]: /nomad/docs/integrations/consul/acl#configuring-consul-authentication
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[config_consul_namespace]: /nomad/docs/configuration/consul#namespace
+[Consul Namespaces]: /consul/docs/enterprise/namespaces
+[Consul Admin Partitions]: /consul/docs/enterprise/admin-partitions
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[flag_consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[Connect]: /nomad/docs/job-specification/connect
+[admin partition]: /consul/docs/enterprise/admin-partitions
+[agent configuration reference]: /consul/docs/agent/config/config-files#partition-1
+[Consul Enterprise]: /consul/docs/enterprise
+[Nomad Workload Identities]: /nomad/docs/integrations/consul/acl#nomad-workload-identities
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/csi_plugin.mdx b/content/nomad/v1.9.x/content/docs/job-specification/csi_plugin.mdx
new file mode 100644
index 0000000000..a0bfa3ac8c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/csi_plugin.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: csi_plugin Block - Job Specification
+description: >-
+  The "csi_plugin" block allows the task to specify it provides a
+  Container Storage Interface plugin to the cluster.
+---
+
+# `csi_plugin` Block
+
+<Placement groups={['job', 'group', 'task', 'csi_plugin']} />
+
+The "csi_plugin" block allows the task to specify it provides a
+Container Storage Interface plugin to the cluster. Nomad will
+automatically register the plugin so that it can be used by other jobs
+to claim [volumes][csi_volumes].
+
+```hcl
+csi_plugin {
+  id                     = "csi-hostpath"
+  type                   = "monolith"
+  mount_dir              = "/csi"
+  stage_publish_base_dir = "/local/csi"
+  health_timeout         = "30s"
+}
+```
+
+## `csi_plugin` Parameters
+
+- `id` `(string: <required>)` - This is the ID for the plugin. Some
+  plugins will require both controller and node plugin types (see
+  below); you need to use the same ID for both so that Nomad knows they
+  belong to the same plugin.
+
+- `type` `(string: <required>)` - One of `node`, `controller`, or
+  `monolith`. Each plugin supports one or more types. Each Nomad
+  client node where you want to mount a volume will need a `node`
+  plugin instance. Some plugins will also require one or more
+  `controller` plugin instances to communicate with the storage
+  provider's APIs. Some plugins can serve as both `controller` and
+  `node` at the same time, and these are called `monolith`
+  plugins. Refer to your CSI plugin's documentation.
+
+- `mount_dir` `(string: <optional>)` - The directory path inside the
+  container where the plugin will expect a Unix domain socket for
+  bidirectional communication with Nomad. This field is typically not
+  required. Refer to your CSI plugin's documentation for details.
+
+- `stage_publish_base_dir` `(string: <optional>)` - The base directory
+  path inside the container where the plugin will be instructed to
+  stage and publish volumes. This field is typically not required.
+  Refer to your CSI plugin's documentation for details. This can not
+  be a subdirectory of `mount_dir`.
+
+- `health_timeout` `(duration: <optional>)` - The duration that
+  the plugin supervisor will wait before restarting an unhealthy
+  CSI plugin. Must be a duration value such as `30s` or `2m`.
+  Defaults to `30s` if not set.
+
+~> **Note:** Plugins running as `node` or `monolith` require root
+privileges (or `CAP_SYS_ADMIN` on Linux) to mount volumes on the
+host. With the Docker task driver, you can use the `privileged = true`
+configuration, but no other default task drivers currently have this
+option.
+
+## Recommendations for Deploying CSI Plugins
+
+CSI plugins run as Nomad tasks, but after mounting the volume are not in the
+data path for the volume. Tasks that mount volumes write and read directly to
+the volume via a bind-mount and there is no communication between the job and
+the CSI plugin. But when an allocation that mounts a volume stops, Nomad will
+need to communicate with the plugin on that allocation's node to unmount the
+volume. This has implications on how to deploy CSI plugins:
+
+* If you are stopping jobs on a node, you must stop tasks that claim
+  volumes before stopping the `node` or `monolith` plugin for those
+  volumes. If you use the `node drain` feature, plugin tasks will
+  automatically be drained last.
+
+* Only the most recently-placed allocation for a given plugin ID and
+  type (controller or node) will be used by any given client node. Run
+  `node` plugins as system jobs and distribute `controller` plugins
+  across client nodes using a constraint as shown below.
+
+* Some plugins will create volumes only in the same location as the
+  plugin. For example, the AWS EBS plugin will create and mount
+  volumes only within the same Availability Zone. You should configure
+  your plugin task as recommended by the plugin's documentation to use
+  the [`topology_request`] field in your volume specification.
+
+## `csi_plugin` Examples
+
+```hcl
+job "plugin-efs" {
+  datacenters = ["dc1"]
+
+  # you can run node plugins as service jobs as well, but running
+  # as a system job ensures all nodes in the DC have a copy.
+  type = "system"
+
+  # only one plugin of a given type and ID should be deployed on
+  # any given client node
+  constraint {
+    operator = "distinct_hosts"
+    value = true
+  }
+
+  group "nodes" {
+    task "plugin" {
+      driver = "docker"
+
+      config {
+        image = "amazon/aws-efs-csi-driver:v.1.3.2"
+
+        args = [
+          "--endpoint=unix://csi/csi.sock",
+          "--logtostderr",
+          "--v=5",
+        ]
+
+        # all CSI node plugins will need to run as privileged tasks
+        # so they can mount volumes to the host. controller plugins
+        # do not need to be privileged.
+        privileged = true
+      }
+
+      csi_plugin {
+        id             = "aws-efs0"
+        type           = "node"
+        mount_dir      = "/csi"  # this path /csi matches the --endpoint
+                            # argument for the container
+        health_timeout = "30s"
+      }
+    }
+  }
+}
+```
+
+[csi]: https://github.com/container-storage-interface/spec
+[csi_volumes]: /nomad/docs/job-specification/volume
+[system]: /nomad/docs/schedulers#system
+[`topology_request`]: /nomad/docs/commands/volume/create#topology_request
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/device.mdx b/content/nomad/v1.9.x/content/docs/job-specification/device.mdx
new file mode 100644
index 0000000000..90ed59c35c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/device.mdx
@@ -0,0 +1,329 @@
+---
+layout: docs
+page_title: device Block - Job Specification
+description: |-
+  The "device" block is used to require a certain device be made available
+  to the task.
+---
+
+# `device` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'device']} />
+
+The `device` block is used to create both a scheduling and runtime requirement
+that the given task has access to the specified devices. A device is a hardware
+device that is attached to the node and may be made available to the task.
+Examples are GPUs, FPGAs, and TPUs.
+
+When a `device` block is added, Nomad will schedule the task onto a node that
+contains the set of device(s) that meet the specified requirements. The `device` block
+allows the operator to specify as little as just the type of device required,
+such as `gpu`, all the way to specifying arbitrary constraints and affinities.
+Once the scheduler has placed the allocation on a suitable node, the Nomad
+Client will invoke the device plugin to retrieve information on how to mount the
+device and what environment variables to expose. For more information on the
+runtime environment, please consult the individual device plugin's documentation.
+
+See the [device plugin's documentation][devices] for a list of supported devices.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        device "nvidia/gpu" {
+          count = 2
+
+          constraint {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "2 GiB"
+          }
+
+          affinity {
+            attribute = "${device.attr.memory}"
+            operator  = ">="
+            value     = "4 GiB"
+            weight    = 75
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+In the above example, the task is requesting two GPUs, from the Nvidia vendor,
+but is not specifying the specific model required. Instead it is placing a hard
+constraint that the device has at least 2 GiB of memory and that it would prefer
+to use GPUs that have at least 4 GiB. This examples shows how expressive the
+`device` block can be.
+
+~> Device support is currently limited to Linux, and container based drivers
+due to the ability to isolate devices to specific tasks.
+
+## `device` Parameters
+
+- `name` `(string: "")` - Specifies the device required. The following inputs
+  are valid:
+
+  - `<device_type>`: If a single value is given, it is assumed to be the device
+    type, such as "gpu", or "fpga".
+
+  - `<vendor>/<device_type>`: If two values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor.
+    Examples include "nvidia/gpu" or "amd/gpu".
+
+  - `<vendor>/<device_type>/<model>`: If three values are given separated by a `/`, the
+    given device type will be selected, constraining on the provided vendor, and
+    model name. Examples include "nvidia/gpu/1080ti" or "nvidia/gpu/2080ti".
+
+- `count` `(int: 1)` - Specifies the number of instances of the given device
+  that are required.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Constraints to restrict
+  which devices are eligible. This can be provided multiple times to define
+  additional constraints. See below for available attributes.
+
+- `affinity` <code>([Affinity][]: nil)</code> - Affinity to specify a preference
+  for which devices get selected. This can be provided multiple times to define
+  additional affinities. See below for available attributes.
+
+## `device` Constraint and Affinity Attributes
+
+The set of attributes available for use in a `constraint` or `affinity` are as
+follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Variable</th>
+      <th>Description</th>
+      <th>Example Value</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>{'${device.ids}'}</code>
+      </td>
+      <td>Comma separated list of device IDs in the group</td>
+      <td>
+        <code>9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.type}'}</code>
+      </td>
+      <td>The type of device</td>
+      <td>
+        <code>"gpu", "tpu", "fpga"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.vendor}'}</code>
+      </td>
+      <td>The device's vendor</td>
+      <td>
+        <code>"amd", "nvidia", "intel"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>{'${device.model}'}</code>
+      </td>
+      <td>The device's model</td>
+      <td>
+        <code>"1080ti"</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>
+          ${'{'}device.attr.&lt;property&gt;{'}'}
+        </code>
+      </td>
+      <td>Property of the device</td>
+      <td>
+        <code>{'${device.attr.memory} => 8 GiB'}</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+For the set of attributes available, please see the individual [device plugin's
+documentation][devices].
+
+### Attribute Units and Conversions
+
+Devices report their attributes with strict types and can also provide unit
+information. For example, when a GPU is reporting its memory, it can report that
+it is "4096 MiB". Since Nomad has the associated unit information, a constraint
+that requires greater than "3.5 GiB" can match since Nomad can convert between
+these units.
+
+The units Nomad supports are as follows:
+
+<table>
+  <thead>
+    <tr>
+      <th>Base Unit</th>
+      <th>Values</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>Byte</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB, MiB, GiB, TiB, PiB, EiB
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB, KB (equivalent to kB), MB, GB, TB, PB,
+          EB
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Byte Rates</code>
+      </td>
+      <td>
+        <code>
+          <strong>Base 2</strong>: KiB/s, MiB/s, GiB/s, TiB/s, PiB/s, EiB/s
+        </code>
+        <br />
+        <code>
+          <strong>Base 10</strong>: kB/s, KB/s (equivalent to kB/s), MB/s, GB/s,
+          TB/s, PB/s,EB/s
+        </code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Hertz</code>
+      </td>
+      <td>
+        <code>MHz, GHz</code>
+      </td>
+    </tr>
+    <tr>
+      <td>
+        <code>Watts</code>
+      </td>
+      <td>
+        <code>mW, W, kW, MW, GW</code>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Conversion is only possible within the same base unit.
+
+## `device` Examples
+
+The following examples only show the `device` blocks. Remember that the
+`device` block is only valid in the placements listed above.
+
+### Single Nvidia GPU
+
+This example schedules a task with a single Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {}
+```
+
+### Multiple Nvidia GPU
+
+This example schedules a task with a two Nvidia GPU made available.
+
+```hcl
+device "nvidia/gpu" {
+  count = 2
+}
+```
+
+### Single Nvidia GPU with Specific Model
+
+This example schedules a task with a single Nvidia GPU made available and uses
+the name to specify the exact model to be used.
+
+```hcl
+device "nvidia/gpu/1080ti" {}
+```
+
+This is a simplification of the following:
+
+```hcl
+device "gpu" {
+  count = 1
+
+  constraint {
+    attribute = "${device.vendor}"
+    value     = "nvidia"
+  }
+
+  constraint {
+    attribute = "${device.model}"
+    value     = "1080ti"
+  }
+}
+```
+
+### Affinity with Unit Conversion
+
+This example uses an affinity to tell the scheduler it would prefer if the GPU
+had at least 1.5 GiB of memory. The following are both equivalent as Nomad can
+do unit conversions.
+
+Specified in `GiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1.5 GiB"
+    weight    = 75
+  }
+}
+```
+
+Specified in `MiB`:
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.attr.memory}"
+    operator  = ">="
+    value     = "1500 MiB"
+    weight    = 75
+  }
+}
+```
+
+### Affinity Towards Specific GPU Devices
+
+This example uses affinity to indicate scheduling preference towards specific
+GPU devices, using their UUID as selection criteria. Since devices are
+fingerprinted as a group, you may specify multiple IDs as a comma separated
+list.
+
+```hcl
+device "nvidia/gpu" {
+  affinity {
+    attribute = "${device.ids}"
+    operator  = "set_contains"
+    value     = "9afa5da1-8f39-25a2-48dc-ba31fd7c0023,c248b547-fed7-4d67-ade5-73a27d280ac4"
+  }
+}
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[devices]: /nomad/plugins/devices 'Nomad Device Plugins'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/disconnect.mdx b/content/nomad/v1.9.x/content/docs/job-specification/disconnect.mdx
new file mode 100644
index 0000000000..71060c1433
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/disconnect.mdx
@@ -0,0 +1,231 @@
+---
+layout: docs
+page_title: disconnect Block - Job Specification
+description: |-
+  The "disconnect" block describes the behavior of both the Nomad server and
+  client in case of a network partition, as well as how to reconcile the workloads
+  in case of a reconnection.
+---
+
+# `disconnect` Block
+
+<Placement groups={['job', 'group', 'disconnect']} />
+
+The `disconnect` block describes the system's behavior in case of a network
+partition. By default, without a `disconnect` block, if an allocation is on a
+node that misses heartbeats, the allocation will be marked `lost` and will be
+replaced.
+
+Replacement happens when a node is lost. When a node is drained, Nomad
+[migrates][] the allocations instead, and Nomad ignores the `disconnect`
+block. When a Nomad agent fails to set up the allocation or the tasks of an
+allocation fail more than their [`restart`][] block allows, Nomad
+[reschedules][] the allocations and ignores the `disconnect`.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    disconnect {
+      lost_after = "6h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+
+  group "example2" {
+    disconnect {
+      stop_on_client_after = "12h"
+      replace = false
+      reconcile = "keep_original"
+    }
+  }
+}
+```
+
+~> Note that you cannot use both`lost_after` and `stop_on_client_after` in the
+same `disconnect` block.
+
+## `disconnect` Parameters
+
+- `lost_after` `(string: "")` - Specifies a duration during which a Nomad client
+  will attempt to reconnect allocations after it fails to heartbeat in the
+  [`heartbeat_grace`][] window.  It defaults to "", which is equivalent to
+  having the disconnect block be nil.
+
+  You cannot use `lost_after` and `stop_on_client_after` in the same
+  `disconnect` block.
+
+  Refer to [the Lost After section][lost-after] for more details.
+
+- `replace` `(bool: false)` - Specifies if Nomad should replace the disconnected
+  allocation with a new one rescheduled on a different node. Nomad considers the
+  replacement allocation a reschedule and obeys the job's [`reschedule`][]
+  block. If false and the node the allocation is running on disconnects
+  or goes down, Nomad does not replace this allocation and reports `unknown`
+  until the node reconnects, or until you manually stop the allocation.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  If true, a new alloc will be placed immediately upon the node becoming
+  disconnected.
+
+- `stop_on_client_after` `(string: "")` - Specifies a duration after which a
+  disconnected Nomad client will stop its allocations. Setting
+  `stop_on_client_after` shorter than `lost_after` and `replace = false` at the
+  same time is not permitted and will cause a validation error, because this
+  would lead to a state where no allocations can be scheduled.
+
+  The Nomad client process must be running for this to occur.
+
+  You cannot use `stop_on_client_after` and `lost_after` in the same
+  `disconnect` block.
+
+  Refer to [the Stop After section][stop-after] for more details.
+
+- `reconcile` `(string: "best_score")` - Specifies which allocation to keep once
+  the previously disconnected node regains connectivity.
+  It has four possible values which are described below:
+
+    - `keep_original`: Always keep the original allocation. Bear in mind
+    when choosing this option, it can have crashed while the client was
+    disconnected.
+    - `keep_replacement`: Always keep the allocation that was replaced
+    to replace the disconnected one.
+    - `best_score`: Keep the allocation running on the node with the best
+    score.
+    - `longest_running`: Keep the allocation that has been up and running
+    continuously for the longest time.
+
+
+## `disconnect` Examples
+
+The following examples only show the `disconnect` blocks. Remember that the
+`disconnect` block is only valid in the placements listed previously.
+
+### Stop After
+
+This example shows how `stop_on_client_after` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server replaces the allocation. The client waits 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_on_client_after`, so the server replaces the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may replace the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  disconnect {
+    stop_on_client_after = "90s"
+  }
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Lost After
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `lost_after` is specified, the Nomad server will mark
+clients that fail to heartbeat as "disconnected" rather than "down", and will
+mark allocations on a disconnected client as "unknown" rather than "lost".
+These allocations may continue to run on the disconnected client. Replacement
+allocations will be scheduled according to the allocations' `replace` settings
+until the disconnected client reconnects. Once a disconnected client reconnects,
+Nomad will compare the "unknown" allocations with their replacements will
+decide which ones to keep according to the `reconcile` setting.
+If the `lost_after` duration expires before the client reconnects,
+the allocations will be marked "lost". Clients that contain "unknown"
+allocations will transition to "disconnected" rather than "down" until the last
+`lost_after` duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `lost_after`
+is twelve hours. Once all groups' `lost_after` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+using the strategy defined by [`reconcile`].
+
+Lost After is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with `stop_on_client_after`.
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "best_score"
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  disconnect {
+    lost_after = "12h"
+    reconcile = "keep_original"
+  }
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[stop-after]: /nomad/docs/job-specification/disconnect#stop-after
+[lost-after]: /nomad/docs/job-specification/disconnect#lost-after
+[`reconcile`]: /nomad/docs/job-specification/disconnect#reconcile
+[migrates]: /nomad/docs/job-specification/migrate
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/dispatch_payload.mdx b/content/nomad/v1.9.x/content/docs/job-specification/dispatch_payload.mdx
new file mode 100644
index 0000000000..af5e905a54
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/dispatch_payload.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: dispatch_payload Block - Job Specification
+description: |-
+  The "dispatch_payload" block allows a task to access dispatch payloads.
+---
+
+# `dispatch_payload` Block
+
+<Placement groups={['job', 'group', 'task', 'dispatch_payload']} />
+
+The `dispatch_payload` block is used in conjunction with a [`parameterized`][parameterized] job
+that expects a payload. When the job is dispatched with a payload, the payload
+will be made available to any task that has a `dispatch_payload` block. The
+payload will be written to the configured file before the task is started. This
+allows the task to use the payload as input or configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+## `dispatch_payload` Parameters
+
+- `file` `(string: "")` - Specifies the file name to write the content of
+  dispatch payload to. The file is written relative to the [task's local
+  directory][localdir].
+
+## `dispatch_payload` Example
+
+This example shows a `dispatch_payload` block in a parameterized job that writes
+the payload to a `config.json` file.
+
+```hcl
+dispatch_payload {
+  file = "config.json"
+}
+```
+
+[localdir]: /nomad/docs/runtime/environment#local 'Task Local Directory'
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/env.mdx b/content/nomad/v1.9.x/content/docs/job-specification/env.mdx
new file mode 100644
index 0000000000..9e7872395a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/env.mdx
@@ -0,0 +1,85 @@
+---
+layout: docs
+page_title: env Block - Job Specification
+description: |-
+  The "env" block configures a list of environment variables to populate the
+  task's environment before starting.
+---
+
+# `env` Block
+
+<Placement groups={['job', 'group', 'task', 'env']} />
+
+The `env` block configures a list of environment variables to populate the
+task's environment before starting.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      env {
+        my_key = "my-value"
+      }
+    }
+  }
+}
+```
+
+## `env` Parameters
+
+The "parameters" for the `env` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Invalid characters such as dashes (`-`)
+will be converted to underscores.
+
+## `env` Examples
+
+The following examples only show the `env` blocks. Remember that the
+`env` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+env {
+  key   = 1.4
+  key   = "1.4"
+
+  key = true
+  key = "1"
+  key = 1
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+env {
+  NODE_CLASS = "${node.class}"
+}
+```
+
+### Environment variables with dots
+
+Environment variables that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+env = {
+  "discovery.type" = "single-node"
+}
+```
+
+### Dynamic Environment Variables
+
+Nomad also supports populating dynamic environment variables from data stored in
+HashiCorp Consul and Vault. To use this feature please see the documentation on
+the [`template` block][template-env].
+
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[template-env]: /nomad/docs/job-specification/template#environment-variables 'Nomad template Block'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/ephemeral_disk.mdx b/content/nomad/v1.9.x/content/docs/job-specification/ephemeral_disk.mdx
new file mode 100644
index 0000000000..2504291dbc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/ephemeral_disk.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: ephemeral_disk Block - Job Specification
+description: |-
+  The "ephemeral_disk" block describes the ephemeral disk requirements of the
+  group. Ephemeral disks can be marked as sticky and support live data
+  migrations.
+---
+
+# `ephemeral_disk` Block
+
+<Placement groups={['job', 'group', 'ephemeral_disk']} />
+
+The `ephemeral_disk` block describes the ephemeral disk requirements of the
+group. Ephemeral disks can be marked as sticky and support live data migrations.
+All tasks in this group will share the same ephemeral disk.
+
+```hcl
+job "docs" {
+  group "example" {
+    ephemeral_disk {
+      migrate = true
+      size    = 500
+      sticky  = true
+    }
+  }
+}
+```
+
+The ephemeral disk can be referenced under `alloc/data/`. More information can
+be found in the [filesystem internals][].
+
+Each job's logs will be written to ephemeral disk space. See the [logs
+documentation][] for more information.
+
+## `ephemeral_disk` Parameters
+
+- `migrate` `(bool: false)` - This specifies that the Nomad client should make a
+  best-effort attempt to migrate the data from the previous allocation, even if
+  the previous allocation was on another client. Enabling `migrate`
+  automatically enables `sticky` as well. During data migration, the task will
+  block starting until the data migration has completed.
+
+  Successful migration requires that the clients can reach each other directly
+  over the Nomad HTTP port. Any failure of the transfer will result in data
+  loss, so this feature is only suitable for data that can be recreated at the
+  destination (for example, cache data). Migration is atomic and any partially
+  migrated data will be removed from the destination if an error is
+  encountered. Note that data migration will not take place if a client garbage
+  collects a failed allocation or if the allocation has been intentionally
+  stopped via `nomad alloc stop`, because the original allocation has already
+  been removed.
+
+- `size` `(int: 300)` - Specifies the size of the ephemeral disk in MB. The
+  current Nomad ephemeral storage implementation does not enforce this limit;
+  however, it is used during job placement.
+
+- `sticky` `(bool: false)` - Specifies that Nomad should make a best-effort
+  attempt to place the updated allocation on the same machine. This will move
+  the `local/` and `alloc/data` directories to the new allocation.
+
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads 'Filesystem internals documentation'
+[logs documentation]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/expose.mdx b/content/nomad/v1.9.x/content/docs/job-specification/expose.mdx
new file mode 100644
index 0000000000..184aad4ca0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/expose.mdx
@@ -0,0 +1,239 @@
+---
+layout: docs
+page_title: expose Block - Job Specification
+description: |-
+  The "expose" block allows specifying options for configuring Envoy expose
+  paths used in Consul Connect integration
+---
+
+# `expose` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'expose',
+  ]}
+/>
+
+The `expose` block allows configuration of additional listeners for the default
+Envoy sidecar proxy managed by Nomad for [Consul Connect][learn-consul-connect].
+These listeners create a bypass of the Connect TLS and network namespace
+isolation, enabling non-Connect enabled services to make requests to specific
+HTTP paths through the sidecar proxy.
+
+The `expose` configuration is valid within the context of a `proxy` block.
+Additional information about Expose Path configurations for Envoy can be found
+in Consul's [Expose Paths Configuration Reference][consul-expose-path-config].
+
+Service [check][] configurations can use their [expose][] parameter to
+automatically generate expose path configurations for HTTP and gRPC checks.
+
+```hcl
+job "expose-check-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+
+      check {
+        expose   = true
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+For uses other than Consul service checks, use the `expose` configuration in the
+`proxy` block. The example below effectively demonstrates exposing the
+`/health` endpoint similar to the example above, but using the fully flexible
+`expose` configuration.
+
+```hcl
+job "expose-example" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+
+      port "api_expose_healthcheck" {
+        to = -1
+      }
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {
+            expose {
+              path {
+                path            = "/health"
+                protocol        = "http"
+                local_path_port = 9001
+                listener_port   = "api_expose_healthcheck"
+              }
+            }
+          }
+        }
+      }
+
+      check {
+        name     = "api-health"
+        type     = "http"
+        path     = "/health"
+        port     = "api_expose_healthcheck"
+        interval = "10s"
+        timeout  = "3s"
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+
+      # e.g. reference ${NOMAD_PORT_api_expose_healthcheck} for other uses
+    }
+  }
+}
+```
+
+## `expose` Parameters
+
+- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations][expose_path]
+  to expose through Envoy.
+
+### `path` Parameters
+
+- `path` `(string: required)` - The HTTP or gRPC path to expose. The path must be prefixed
+  with a slash.
+
+- `protocol` `(string: required)` - Sets the protocol of the listener. Must be
+  `http` or `http2`. For gRPC use `http2`.
+
+- `local_path_port` `(int: required)` - The port the service is listening to for connections to
+  the configured `path`. Typically this will be the same as the `service.port` value, but
+  could be different if for example the exposed path is intended to resolve to another task
+  in the task group.
+
+- `listener_port` <code>([Port]: required)</code> - The name of the port to use
+  for the exposed listener. The port should be configured to [map inside][network-to]
+  the task's network namespace.
+
+## `expose` Examples
+
+The following example is configured to expose the `/metrics` endpoint of the
+Connect-enabled `count-dashboard` service, using the `HTTP` protocol.
+`count-dashboard` is expected to listen inside its namespace to port `9001`, and
+external services will be able to reach its `/metrics` endpoint by connecting to
+the [network interface][network_interface] of the node on the allocated
+`metrics` [Port][].
+
+```hcl
+service {
+  name = "count-dashboard"
+  port = "9001"
+
+  connect {
+    sidecar_service {
+      proxy {
+        expose {
+          path {
+            path            = "/metrics"
+            protocol        = "http"
+            local_path_port = 9001
+            listener_port   = "metrics"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## `path` Examples
+
+The following example is an expose configuration that exposes a `/metrics`
+endpoint using the `http2` protocol (typical for gRPC), and an HTTP `/v2/health`
+endpoint.
+
+```hcl
+proxy {
+  expose {
+    path {
+      path            = "/metrics"
+      protocol        = "http2"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+    path {
+      path            = "/v2/health"
+      protocol        = "http"
+      local_path_port = 9001
+      listener_port   = "expose"
+    }
+  }
+}
+```
+
+### Exposing Service Checks
+
+A common use case for `expose` is for exposing endpoints used in Consul service
+check definitions. For these cases the [expose][] parameter in the service check
+block can be used to automatically generate the expose path configuration.
+Configuring a port for use by the check is optional, as a dynamic port will be
+automatically generated if not provided.
+
+```hcl
+check {
+  expose   = true
+  type     = "http"
+  name     = "dashboard-health"
+  path     = "/health"
+  interval = "10s"
+  timeout  = "3s"
+}
+```
+
+[network-to]: /nomad/docs/job-specification/network#to
+[consul-expose-path-config]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[expose-path]: /nomad/docs/job-specification/expose#path-1
+[expose]: /nomad/docs/job-specification/service#expose
+[path]: /nomad/docs/job-specification/expose#path-parameters 'Nomad Expose Path Parameters'
+[port]: /nomad/docs/job-specification/network#port-parameters 'Nomad Port Parameters'
+[network_interface]: /nomad/docs/configuration/client#network_interface
+[learn-consul-connect]: /nomad/tutorials/integrate-consul/consul-service-mesh
+[check]: /nomad/docs/job-specification/service#check-parameters
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/gateway.mdx b/content/nomad/v1.9.x/content/docs/job-specification/gateway.mdx
new file mode 100644
index 0000000000..b97f097675
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/gateway.mdx
@@ -0,0 +1,746 @@
+---
+layout: docs
+page_title: gateway Block - Job Specification
+description: |-
+  The "gateway" block allows specifying options for configuring Consul Gateways
+  used in the Consul Connect integration
+---
+
+# `gateway` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'gateway']} />
+
+The `gateway` block allows configuration of [Consul Connect
+Gateways](/consul/docs/connect/gateways). Nomad will automatically create the
+necessary Gateway [Configuration Entry](/consul/docs/agent/config-entries) as
+well as inject an Envoy proxy task into the Nomad job to serve as the Gateway.
+
+The `gateway` configuration is valid within the context of a `connect` block.
+Additional information about Gateway configurations can be found in Consul's
+[Connect Gateways](/consul/docs/connect/gateways) documentation.
+
+~> **Note:** [Ingress Gateways](/consul/docs/connect/gateways/ingress-gateway)
+are generally intended for enabling access into a Consul service mesh from within the
+same network. For public ingress products like [NGINX](/nomad/tutorials/load-balancing/load-balancing-nginx)
+provide more suitable features.
+
+```hcl
+service {
+  connect {
+    gateway {
+      # ...
+    }
+  }
+}
+```
+
+## `gateway` Parameters
+
+Exactly one of `ingress`, `terminating`, or `mesh` must be configured.
+
+- `proxy` <code>([proxy]: nil)</code> - Configuration of the Envoy proxy that will
+  be injected into the task group.
+- `ingress` <code>([ingress]: nil)</code> - Configuration Entry of type `ingress-gateway`
+  that will be associated with the service.
+- `terminating` <code>([terminating]: nil)</code> - Configuration Entry of type `terminating-gateway`
+  that will be associated with the service.
+- `mesh` <code>([mesh]: nil)</code> - Indicates a mesh gateway will be associated
+  with the service.
+
+### `proxy` Parameters
+
+- `connect_timeout` `(string: "5s")` - The amount of time to allow when making
+  upstream connections before timing out. Defaults to 5 seconds. If the upstream
+  service has the configuration option <code>[connect_timeout_ms]</code> set for
+  the `service-resolver`, that timeout value will take precedence over this
+  gateway proxy option.
+
+- `envoy_gateway_bind_tagged_addresses` `(bool: false)` - Indicates that the
+  gateway services tagged addresses should be bound to listeners in addition to
+  the default listener address.
+
+- `envoy_gateway_bind_addresses` <code>(map<string|[address]>: nil)</code> - A
+  map of additional addresses to be bound.  The keys to this map are the same of
+  the listeners to be created and the values are a map with two keys - address
+  and port, that combined make the address to bind the listener to. These are
+  bound in addition to the default address.  If `bridge` networking is in use,
+  this map is automatically populated with additional listeners enabling the
+  Envoy proxy to work from inside the network namespace.
+
+```
+envoy_gateway_bind_addresses "<service>" {
+  address = "0.0.0.0"
+  port    = <port>
+}
+```
+
+- `envoy_gateway_no_default_bind` `(bool: false)` - Prevents binding to the default
+  address of the gateway service. This should be used with one of the other options
+  to configure the gateway's bind addresses. If `bridge` networking is in use, this
+  value will default to `true` since the Envoy proxy does not need to bind to the
+  service address from inside the network namespace.
+- `envoy_dns_discovery_type` `(string: optional)` - Determintes how Envoy will
+  resolve hostnames. Defaults to `LOGICAL_DNS`. Must be one of `STRICT_DNS` or
+  `LOGICAL_DNS`. Details for each type are available in the [Envoy
+  Documentation][envoy_sd_docs].  This option applies to terminating gateways
+  that route to services addressed by a hostname.
+- `config` `(map: nil)` - Escape hatch for [Advanced Configuration] of Envoy.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+#### `address` Parameters
+
+- `address` `(string: required)` - The address to bind to when combined with `port`.
+- `port` `(int: required)` - The port to listen to.
+
+### `ingress` Parameters
+
+- `listener` <code>(array<[listener]> : required)</code> - One or more listeners
+  that the ingress gateway should setup, uniquely identified by their port
+  number.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this gateway.
+
+#### `listener` Parameters
+
+- `port` `(int: required)` - The port that the listener should receive traffic on.
+
+- `protocol` `(string: "tcp")` - The protocol associated with the listener. One
+  of `tcp`, `http`, `http2`, or `grpc`.
+
+  ~> **Note:** If using any protocol other than `tcp` (for example: `http` or
+  `grpc`), preconfiguring a [service-default][] in Consul to set the
+  [Protocol][service-default-protocol] of the service to the desired protocol is
+  mandatory due to an [open issue](https://github.com/hashicorp/nomad/issues/8647).
+
+- `service` <code>(array<[listener-service]>: required)</code> - One or more services to be
+  exposed via this listener. For `tcp` listeners, only a single service is allowed.
+
+#### Listener `service` Parameters
+
+The `service` blocks for a listener under an `ingress` gateway accept the
+following parameters. Note these are different than the `service` blocks under a
+`terminating` gateway.
+
+- `name` `(string: required)` - The name of the service that should be exposed through
+  this listener. This can be either a service registered in the catalog, or a
+  service defined by other config entries, or a service that is going to be configured
+  by Nomad. If the wildcard specifier `*` is provided, then ALL services will be
+  exposed through this listener. This is not supported for a listener with protocol `tcp`.
+
+- `hosts` `(array<string>: nil)` - A list of hosts that specify what requests will
+  match this service. This cannot be used with a `tcp` listener, and cannot be
+  specified alongside a wildcard (`*`) service name. If not specified, the default
+  domain `<service-name>.ingress.*` will be used to match services. Requests _must_
+  send the correct host to be routed to the defined service.
+
+  The wildcard specifier `*` can be used by itself to match all traffic coming to
+  the ingress gateway, if TLS is not enabled. This allows a user to route all traffic
+  to a single service without specifying a host, allowing simpler tests and demos.
+  Otherwise, the wildcard specifier can be used as part of the host to match
+  multiple hosts, but only in the leftmost DNS label. This ensures that all defined
+  hosts are valid DNS records. For example, `*.example.com` is valid while `example.*`
+  and `*-suffix.example.com` are not.
+
+- `request_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to requests routed to this
+  service. This cannot be used with a tcp listener.
+
+- `response_headers` `([header modifiers]: <optional>)` - A set of HTTP-specific
+  header modification rules that will be applied to responses from this
+  service. This cannot be used with a tcp listener.
+
+- `max_concurrent_requests` `(int: <optional>)` - Specifies the maximum number
+  of concurrent HTTP/2 traffic requests that are allowed at a single point in
+  time. If unset, will default to the Envoy proxy's default.
+
+- `max_connections` `(int: <optional>)` - Specifies the maximum number of
+  HTTP/1.1 connections a service instance is allowed to establish against the
+  upstream. If unset, will default to the Envoy proxy's default.
+
+- `max_pending_requests` `(int: <optional>)` - Specifies the maximum number of
+  requests that are allowed to queue while waiting to establish a connection.
+  If unset, will default to the Envoy proxy's default.
+
+- `tls` <code>([tls]: nil)</code> - TLS configuration for this service.
+
+#### Header modifier parameters
+
+The `request_headers` and `response_headers` blocks of an `ingress.service`
+block accept the following parameters. For more details, see the [Consul
+documentation][response-headers].
+
+- `add` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  headers, where header names are keys and header values are the values. Header
+  names are not case-sensitive. If header values with the same name already
+  exist, the value is appended and Consul applies both headers.
+
+- `set` `(map<string|string>: optional)` - A set of key-value pairs to add to the
+  response header or to replace existing header values with. Use header names as
+  the keys. Header names are not case-sensitive. If header values with the same
+  names already exist, Consul replaces the header values.
+
+- `remove` `array(string): optional` - Defines a list of headers to remove. Consul
+  removes only headers containing exact matches. Header names are not
+  case-sensitive.
+
+#### `tls` Parameters
+
+- `enabled` `(bool: false)` - Set this configuration to enable TLS for every
+  listener on the gateway. If TLS is enabled, then each host defined in the
+  `host` field will be added as a DNSSAN to the gateway's x509 certificate.
+
+- `cipher_suites` `(array<string>: optional)` - Set the default list of TLS
+  cipher suites for the gateway's listeners. Refer to
+  [`CipherSuites`](/consul/docs/connect/config-entries/ingress-gateway#ciphersuites)
+  in the Consul documentation for the supported cipher suites.
+
+- `sds` `(block: optional)` - Defines a set of parameters that configures the
+  listener to load TLS certificates from an external Secret Discovery Service
+  ([SDS][]).
+
+  - `cluster_name` `(string)` - The SDS cluster name to connect to to retrieve
+    certificates.
+
+  - `cert_resource` `(string)` - The SDS resource name to request when fetching
+    the certificate from the SDS service.
+
+- `tls_max_version` `(string: optional)` - Set the default maximum TLS version
+  supported by the gateway. Refer to
+  [`TLSMaxVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion)
+  in the Consul documentation for supported versions.
+
+- `tls_min_version` `(string: optional)` - Set the default minimum TLS version
+  supported by the gateway. Refer to
+  [`TLSMinVersion`](/consul/docs/connect/config-entries/ingress-gateway#tlsminversion)
+  in the Consul documentation for supported versions.
+
+### `terminating` Parameters
+
+- `service` <code>(array<[linked-service]>: required)</code> - One or more services to be
+  linked with the gateway. The gateway will proxy traffic to these services. These
+  linked services must be registered with Consul for the gateway to discover their
+  addresses. They must also be registered in the same Consul datacenter as the
+  terminating gateway.
+
+#### linked `service` Parameters
+
+The `service` blocks for a `terminating` gateway accept the following
+parameters. Note these are different than the `service` blocks for listeners
+under an `ingress` gateway.
+
+- `name` `(string: required)` - The name of the service to link with the
+  gateway. If the wildcard specifier `*` is provided, then ALL services within
+  the Consul namespace wil lbe linked with the gateway.
+
+- `ca_file` `(string: <optional>)` - A file path to a PEM-encoded certificate
+  authority. The file must be accessible by the gateway task. The certificate
+  authority is used to verify the authenticity of the service linked with the
+  gateway. It can be provided along with a `cert_file` and `key_file` for mutual
+  TLS authentication, or on its own for one-way TLS authentication. If none is
+  provided the gateway **will not** encrypt traffic to the destination.
+
+- `cert_file` `(string: <optional>)` - A file path to a PEM-encoded certificate.
+  The file must be accessible by the gateway task. The certificate is provided
+  to servers to verify the gateway's authenticity. It must be provided if a
+  `key_file` is provided.
+
+- `key_file` `(string: <optional>)` - A file path to a PEM-encoded private key.
+  The file must be accessible by the gateway task. The key is used with the
+  certificate to verify the gateway's authenticity. It must be provided if a
+  `cert_file` is provided.
+
+- `sni` `(string: <optional>)` - An optional hostname or domain name to specify
+  during the TLS handshake.
+
+### `mesh` Parameters
+
+The `mesh` block currently does not have any configurable parameters.
+
+~> **Note:** If using the Mesh Gateway for [WAN Federation][connect_mesh_gw],
+the additional piece of service metadata `{"consul-wan-federation":"1"}` must
+be applied. This can be done with the service [`meta`][meta] parameter.
+
+### Gateway with host networking
+
+Nomad supports running gateways using host networking. A static port must be allocated
+for use by the [Envoy admin interface](https://www.envoyproxy.io/docs/envoy/latest/operations/admin)
+and assigned to the proxy service definition.
+
+!> **Warning:** There is no way to disable the Envoy admin interface, which will be
+accessible to any workload running on the same Nomad client. The admin interface exposes
+information about the proxy, including a Consul Service Identity token if Consul ACLs
+are enabled.
+
+### Specify Envoy image
+
+The Docker image used for Connect gateway tasks defaults to the official [Envoy
+Docker] image, `docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}`, where `${NOMAD_envoy_version}`
+is resolved automatically by a query to Consul. The image to use can be configured
+by setting `meta.connect.gateway_image` in the Nomad job. Custom images can still
+make use of the envoy version interpolation, e.g.
+
+```hcl
+meta.connect.gateway_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+### Custom gateway task
+
+The task created for the gateway can be configured manually using the
+[`sidecar_task`][sidecar_task] block.
+
+```
+connect {
+  gateway {
+    # ...
+  }
+
+  sidecar_task {
+    # see /docs/job-specification/sidecar_task for more details
+  }
+}
+```
+
+### Examples
+
+#### ingress gateway
+
+```hcl
+job "ingress-demo" {
+
+  datacenters = ["dc1"]
+
+  # This group will have a task providing the ingress gateway automatically
+  # created by Nomad. The ingress gateway is based on the Envoy proxy being
+  # managed by the docker driver.
+  group "ingress-group" {
+
+    network {
+      mode = "bridge"
+
+      # This example will enable plain HTTP traffic to access the uuid-api connect
+      # native example service on port 8080.
+      port "inbound" {
+        static = 8080
+        to     = 8080
+      }
+    }
+
+    service {
+      name = "my-ingress-service"
+      port = "8080"
+
+      connect {
+        gateway {
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not
+            # explicitly configured when using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "uuid-api" {
+            #   address = "0.0.0.0"
+            #   port    = <associated listener.port>
+            # }
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Ingress Gateway Configuration Entry.
+          ingress {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the ingress block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#ingress-parameters
+            listener {
+              port     = 8080
+              protocol = "tcp"
+              service {
+                name = "uuid-api"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The UUID generator from the connect-native demo is used as an example service.
+  # The ingress gateway above makes access to the service possible over normal HTTP.
+  # For example,
+  #
+  # $ curl $(dig +short @127.0.0.1 -p 8600 uuid-api.ingress.dc1.consul. ANY):8080
+  group "generator" {
+    network {
+      mode = "host"
+      port "api" {}
+    }
+
+    service {
+      name = "uuid-api"
+      port = "api"
+
+      connect {
+        native = true
+      }
+    }
+
+    task "generate" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/uuid-api:v5"
+        network_mode = "host"
+      }
+
+      env {
+        BIND = "0.0.0.0"
+        PORT = "${NOMAD_PORT_api}"
+      }
+    }
+  }
+}
+```
+
+#### terminating gateway
+
+```hcl
+job "countdash-terminating" {
+
+  datacenters = ["dc1"]
+
+  # This group provides the service that exists outside of the Consul Connect
+  # service mesh. It is using host networking and listening to a statically
+  # allocated port.
+  group "api" {
+    network {
+      mode = "host"
+      port "port" {
+        static = "9001"
+      }
+    }
+
+    # This example will enable services in the service mesh to make requests
+    # to this service which is not in the service mesh by making requests
+    # through the terminating gateway.
+    service {
+      name = "count-api"
+      port = "port"
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image        = "hashicorpdev/counter-api:v3"
+        network_mode = "host"
+      }
+    }
+  }
+
+  group "gateway" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "api-gateway"
+
+      connect {
+        gateway {
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "default" {
+            #   address = "0.0.0.0"
+            #   port    = <generated listener port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+
+          # Consul Terminating Gateway Configuration Entry.
+          terminating {
+            # Nomad will automatically manage the Configuration Entry in Consul
+            # given the parameters in the terminating block.
+            #
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#terminating-parameters
+            service {
+              name = "count-api"
+            }
+          }
+        }
+      }
+    }
+  }
+
+  # The dashboard service is in the service mesh, making use of bridge network
+  # mode and connect.sidecar_service. When running, the dashboard should be
+  # available from a web browser at localhost:9002.
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              # By configuring an upstream destination to the linked service of
+              # the terminating gateway, the dashboard is able to make requests
+              # through the gateway to the count-api service.
+              destination_name = "count-api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+#### mesh gateway
+
+Mesh gateways are useful when Connect services need to make cross-datacenter
+requests where not all nodes in each datacenter have full connectivity. This example
+demonstrates using mesh gateways to enable making requests between datacenters
+`one` and `two`, where each mesh gateway will bind to the `public` host network
+configured on at least one Nomad client in each datacenter.
+
+Job running where Nomad and Consul are in datacenter `one`.
+
+```hcl
+job "countdash-mesh-one" {
+  datacenters = ["one"]
+
+  group "mesh-gateway-one" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured on at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+
+              # This dashboard service is running in datacenter "one", and will
+              # make requests to the "count-api" service running in datacenter
+              # "two", by going through the mesh gateway in each datacenter.
+              datacenter       = "two"
+
+              mesh_gateway {
+                # Using "local" mode indicates requests should exit this datacenter
+                # through the mesh gateway, and enter the destination datacenter
+                # through a mesh gateway in that datacenter.
+                # Using "remote" mode indicates requests should bypass the local
+                # mesh gateway, instead directly connecting to the mesh gateway
+                # in the destination datacenter.
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+```
+
+Job running where Nomad and Consul are in datacenter `two`.
+
+```hcl
+job "countdash-mesh-two" {
+  datacenters = ["two"]
+
+  group "mesh-gateway-two" {
+    network {
+      mode = "bridge"
+
+      # A mesh gateway will require a host_network configured for at least one
+      # Nomad client that can establish cross-datacenter connections. Nomad will
+      # automatically schedule the mesh gateway task on compatible Nomad clients.
+      port "mesh_wan" {
+        host_network = "public"
+      }
+    }
+
+    service {
+      name = "mesh-gateway"
+
+      # The mesh gateway connect service should be configured to use a port from
+      # the host_network capable of cross-datacenter connections.
+      port = "mesh_wan"
+
+      connect {
+        gateway {
+          mesh {
+            # No configuration options in the mesh block.
+          }
+
+          # Consul gateway [envoy] proxy options.
+          proxy {
+            # The following options are automatically set by Nomad if not explicitly
+            # configured with using bridge networking.
+            #
+            # envoy_gateway_no_default_bind = true
+            # envoy_gateway_bind_addresses "lan" {
+            #   address = "0.0.0.0"
+            #   port    = <generated dynamic port>
+            # }
+            # envoy_gateway_bind_addresses "wan" {
+            #   address = "0.0.0.0"
+            #   port    = <configured service port>
+            # }
+            # Additional options are documented at
+            # https://developer.hashicorp.com/nomad/docs/job-specification/gateway#proxy-parameters
+          }
+        }
+      }
+    }
+  }
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "api" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+
+[address]: /nomad/docs/job-specification/gateway#address-parameters
+[advanced configuration]: /consul/docs/connect/proxies/envoy#advanced-configuration
+[connect_timeout_ms]: /consul/docs/connect/config-entries/service-resolver#connecttimeout
+[connect_mesh_gw]: /consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways
+[envoy docker]: https://hub.docker.com/r/envoyproxy/envoy/tags
+[ingress]: /nomad/docs/job-specification/gateway#ingress-parameters
+[proxy]: /nomad/docs/job-specification/gateway#proxy-parameters
+[linked-service]: /nomad/docs/job-specification/gateway#linked-service-parameters
+[listener]: /nomad/docs/job-specification/gateway#listener-parameters
+[interpolation]: /nomad/docs/runtime/interpolation
+[listener-service]: /nomad/docs/job-specification/gateway#listener-service-parameters
+[service-default]: /consul/docs/connect/config-entries/service-defaults
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[terminating]: /nomad/docs/job-specification/gateway#terminating-parameters
+[tls]: /nomad/docs/job-specification/gateway#tls-parameters
+[mesh]: /nomad/docs/job-specification/gateway#mesh-parameters
+[meta]: /nomad/docs/job-specification/service#meta
+[envoy_sd_docs]: https://www.envoyproxy.io/docs/envoy/v1.16.1/intro/arch_overview/upstream/service_discovery
+[SDS]: https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#listeners-services-tls-sds
+[service-default-protocol]: /consul/docs/connect/config-entries/service-defaults#protocol
+[response-headers]: /consul/docs/connect/config-entries/ingress-gateway#listeners-services-responseheaders
+[header modifiers]: /nomad/docs/job-specification/gateway#header-modifier-parameters
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/group.mdx b/content/nomad/v1.9.x/content/docs/job-specification/group.mdx
new file mode 100644
index 0000000000..c2c8dc1340
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/group.mdx
@@ -0,0 +1,455 @@
+---
+layout: docs
+page_title: group Block - Job Specification
+description: |-
+  The "group" block defines a series of tasks that should be co-located on the
+  same Nomad client. Any task within a group will be placed on the same client.
+---
+
+# `group` Block
+
+<Placement groups={['job', 'group']} />
+
+The `group` block defines a series of tasks that should be co-located on the
+same Nomad client. Any [task][] within a group will be placed on the same
+client.
+
+```hcl
+job "docs" {
+  group "example" {
+    # ...
+  }
+}
+```
+
+## `group` Parameters
+
+- `constraint` <code>([Constraint][]: nil)</code> -
+  This can be provided multiple times to define additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided
+  multiple times to define criteria for spreading allocations across a
+  node attribute or metadata. See the
+  [Nomad spread reference](/nomad/docs/job-specification/spread) for more details.
+
+- `count` `(int)` - Specifies the number of instances that should be running
+  under for this group. This value must be non-negative. This defaults to the
+  `min` value specified in the [`scaling`](/nomad/docs/job-specification/scaling)
+  block, if present; otherwise, this defaults to `1`.
+
+- `consul` <code>([Consul][consul]: nil)</code> - Specifies Consul configuration
+  options specific to the group. These options will be applied to all tasks and
+  services in the group unless a task has its own `consul` block.
+
+- `ephemeral_disk` <code>([EphemeralDisk][]: nil)</code> - Specifies the
+  ephemeral disk requirements of the group. Ephemeral disks can be marked as
+  sticky and support live data migrations.
+
+- `disconnect` <code>([disconnect][]: nil)</code> - Specifies the disconnect
+  strategy for the server and client for all tasks in this group in case of a
+  network partition. The tasks can be left unconnected, stopped or replaced
+  when the client disconnects. The policy for reconciliation in case the client
+  regains connectivity is also specified here.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the group strategy for
+  migrating off of draining nodes. Only service jobs with a count greater than
+  1 support migrate blocks.
+
+- `network` <code>([Network][]: &lt;optional&gt;)</code> - Specifies the network
+  requirements and configuration, including static and dynamic port allocations,
+  for the group.
+
+- `prevent_reschedule_on_lost` `(bool: false)` - Defines the replacement
+  behavior of an allocation when the node it is running on misses heartbeats.
+  When enabled, if the node disconnects or goes down,
+  Nomad does not replace this allocation and shows it as `unknown` until the node
+  reconnects or you manually restart the node.
+
+  This behavior only modifies the replacement process on the server.  To
+  modify the allocation behavior on the client, refer to
+  [`stop_after_client_disconnect`](#stop_after_client_disconnect).
+
+  The `unknown` allocation has to be manually stopped to run it again.
+
+  ```plaintext
+  `nomad alloc stop  <alloc ID>`
+  ```
+
+  Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+  same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+  We deprecated this field in favor of `replace` on the [`disconnect`] block,
+  see [example below][disconect_migration] for more details about migrating.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of the group allocation statuses become "failed".
+
+- `restart` <code>([Restart][]: nil)</code> - Specifies the restart policy for
+  all tasks in this group. If omitted, a default policy exists for each job
+  type, which can be found in the [restart block documentation][restart].
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul](/nomad/docs/configuration/consul) for service discovery. Nomad
+  automatically registers each service when an allocation is started and
+  de-registers them when the allocation is destroyed.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  stopping a group's tasks. The delay occurs between Consul or Nomad service
+  deregistration and sending each task a shutdown signal. Ideally, services
+  would fail health checks once they receive a shutdown signal. Alternatively,
+  `shutdown_delay` may be set to give in-flight requests time to complete
+  before shutting down. A group level `shutdown_delay` will run regardless
+  if there are any defined group [services](/nomad/docs/job-specification/group#service)
+  and only applies to these services. In addition, tasks may have their own
+  [`shutdown_delay`](/nomad/docs/job-specification/task#shutdown_delay) which waits
+  between de-registering task services and stopping the task.
+
+- `stop_after_client_disconnect` `(string: "")` - Specifies a duration after
+  which a Nomad client will stop allocations, if it cannot communicate with the
+  servers. By default, a client will not stop an allocation until explicitly
+  told to by a server. A client that fails to heartbeat to a server within the
+  [`heartbeat_grace`] window and any allocations running on it will be marked
+  "lost" and Nomad will schedule replacement allocations. The replaced
+  allocations will normally continue to run on the non-responsive client. But
+  you may want them to stop instead — for example, allocations requiring
+  exclusive access to an external resource. When specified, the Nomad client
+  will stop them after this duration.
+  The Nomad client process must be running for this to occur. This setting
+  cannot be used with [`max_client_disconnect`].
+
+  This field was deprecated in favour of `stop_after` on the [`disconnect`] block.
+
+- `max_client_disconnect` `(string: "")` - Specifies a duration during which a
+  Nomad client will attempt to reconnect allocations after it fails to heartbeat
+  in the [`heartbeat_grace`] window. See [the example code
+  below][max-client-disconnect] for more details. This setting cannot be used
+  with [`stop_after_client_disconnect`].
+
+  This field was deprecated in favour of `lost_after` on the [`disconnect`] block.
+
+- `task` <code>([Task][]: &lt;required&gt;)</code> - Specifies one or more tasks to run
+  within this group. This can be specified multiple times, to add a task as part
+  of the group.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
+
+- `volume` <code>([Volume][]: nil)</code> - Specifies the volumes that are
+  required by tasks within the group.
+
+## `group` Examples
+
+The following examples only show the `group` blocks. Remember that the
+`group` block is only valid in the placements listed above.
+
+### Specifying Count
+
+This example specifies that 5 instances of the tasks within this group should be
+running:
+
+```hcl
+group "example" {
+  count = 5
+}
+```
+
+### Tasks with Constraint
+
+This example shows two abbreviated tasks with a constraint on the group. This
+will restrict the tasks to 64-bit operating systems.
+
+```hcl
+group "example" {
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  task "cache" {
+    # ...
+  }
+
+  task "server" {
+    # ...
+  }
+}
+```
+
+### Metadata
+
+This example show arbitrary user-defined metadata on the group:
+
+```hcl
+group "example" {
+  meta {
+    my-key = "my-value"
+  }
+}
+```
+
+### Network
+
+This example shows network constraints as specified in the [network][] block
+which uses the `bridge` networking mode, dynamically allocates two ports, and
+statically allocates one port:
+
+```hcl
+group "example" {
+  network {
+    mode = "bridge"
+    port "http" {}
+    port "https" {}
+    port "lb" {
+      static = "8889"
+    }
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+group "example" {
+  network {
+    port "api" {}
+  }
+
+  service {
+    name = "example"
+    port = "api"
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  task "api" { ... }
+}
+```
+
+### Stop After Client Disconnect
+
+This example shows how `stop_after_client_disconnect` interacts with
+other blocks. For the `first` group, after the default 10 second
+[`heartbeat_grace`] window expires and 90 more seconds passes, the
+server will reschedule the allocation. The client will wait 90 seconds
+before sending a stop signal (`SIGTERM`) to the `first-task`
+task. After 15 more seconds because of the task's `kill_timeout`, the
+client will send `SIGKILL`. The `second` group does not have
+`stop_after_client_disconnect`, so the server will reschedule the
+allocation after the 10 second [`heartbeat_grace`] expires. It will
+not be stopped on the client, regardless of how long the client is out
+of touch.
+
+Note that if the server's clocks are not closely synchronized with
+each other, the server may reschedule the group before the client has
+stopped the allocation. Operators should ensure that clock drift
+between servers is as small as possible.
+
+Note also that a group using this feature will be stopped on the
+client if the Nomad server cluster fails, since the client will be
+unable to contact any server in that case. Groups opting in to this
+feature are therefore exposed to an additional runtime dependency and
+potential point of failure.
+
+```hcl
+group "first" {
+  stop_after_client_disconnect = "90s"
+
+  task "first-task" {
+    kill_timeout = "15s"
+  }
+}
+
+group "second" {
+
+  task "second-task" {
+    kill_timeout = "5s"
+  }
+}
+```
+
+### Max Client Disconnect
+
+`max_client_disconnect` specifies a duration during which a Nomad client will
+attempt to reconnect allocations after it fails to heartbeat in the
+[`heartbeat_grace`] window.
+
+By default, allocations running on a client that fails to heartbeat will be
+marked "lost". When a client reconnects, its allocations, which may still be
+healthy, will restart because they have been marked "lost". This can cause
+issues with stateful tasks or tasks with long restart times.
+
+Instead, an operator may desire that these allocations reconnect without a
+restart. When `max_client_disconnect` or `disconnect.lost_after` is specified,
+the Nomad server marks clients that fail to heartbeat as "disconnected"
+rather than "down", and will mark allocations on a disconnected client as
+"unknown" rather than "lost". These allocations may continue to run on the
+disconnected client. Replacement allocations will be scheduled according to the
+allocations' `disconnect.replace` settings. until the disconnected client
+reconnects. Once a disconnected client reconnects, Nomad compares the "unknown"
+allocations with their replacements and decides which ones to keep according
+to the `disconnect.replace` setting. If the `max_client_disconnect` or
+`disconnect.losta_after` duration expires before the client reconnects,
+the allocations will be marked "lost".
+Clients that contain "unknown" allocations will transition to "disconnected"
+rather than "down" until the last `max_client_disconnect` or `disconnect.lost_after`
+duration has expired.
+
+In the example code below, if both of these task groups were placed on the same
+client and that client experienced a network outage, both of the group's
+allocations would be marked as "disconnected" at two minutes because of the
+client's `heartbeat_grace` value of "2m". If the network outage continued for
+eight hours, and the client continued to fail to heartbeat, the client would
+remain in a "disconnected" state, as the first group's `max_client_disconnect`
+is twelve hours. Once all groups' `max_client_disconnect` durations are
+exceeded, in this case in twelve hours, the client node will be marked as "down"
+and the allocation will be marked as "lost". If the client had reconnected
+before twelve hours had passed, the allocations would gracefully reconnect
+without a restart.
+
+Max Client Disconnect is useful for edge deployments, or scenarios when
+operators want zero on-client downtime due to node connectivity issues. This
+setting cannot be used with [`stop_after_client_disconnect`].
+
+```hcl
+# server_config.hcl
+
+server {
+  enabled         = true
+  heartbeat_grace = "2m"
+}
+```
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect = "12h"
+
+  task "first-task" {
+    ...
+  }
+}
+
+group "second" {
+  max_client_disconnect = "6h"
+
+  task "second-task" {
+    ...
+  }
+}
+```
+
+#### Max Client Disconnect and Prevent Reschedule On Lost
+
+Setting `max_client_disconnect` and `prevent_reschedule_on_lost = true` at the
+same time requires that [rescheduling is disabled entirely][`disable_rescheduling`].
+
+```hcl
+# jobspec.nomad
+
+group "first" {
+  max_client_disconnect      = "12h"
+  prevent_reschedule_on_lost = true
+
+  reschedule {
+    attempts  = 0
+    unlimited = false
+  }
+
+  task "first-task" {
+    ...
+  }
+}
+```
+
+If [`max_client_disconnect`](#max_client_disconnect) is set and
+`prevent_reschedule_on_lost = true`, allocations on disconnected nodes will be
+`unknown` until the `max_client_disconnect` window expires, at which point
+the node will be transition from `disconnected` to `down`. The allocation
+will remain as `unknown` and won't be rescheduled.
+
+#### Migration to `disconnect` block
+
+The new configuration fileds in the disconnect block work exactly the same as the
+ones they are replacing:
+  * `stop_after_client_disconnect` is replaced by `stop_after`
+  * `max_client_disconnect` is replaced by `lost_after`
+  * `prevent_reschedule_on_lost` is replaced by `replace`
+
+To keep the same behaviour as the old configuration upon reconnection, the
+`reconcile` option should be set to `best_score`.
+
+The following example shows how to migrate from the old configuration to the new one:
+
+```hcl
+job "docs" {
+  group "example" {
+    max_client_disconnect        = "6h"
+    stop_after_client_disconnect = "2h"
+    prevent_reschedule_on_lost   = true
+  }
+}
+```
+Can be directly translated to:
+
+```hcl
+job "docs" {
+  	group "example" {
+      disconnect {
+        lost_after = "6h"
+        stop_after = "2h"
+        replace = false
+        reconcile = "best_score"
+      }
+    }
+  }
+```
+
+All use constrains still apply with the disconnect block as they did before:
+ - `stop_after` and `lost_after` can't be used together.
+
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[consul]: /nomad/docs/job-specification/consul
+[consul_namespace]: /nomad/docs/commands/job/run#consul-namespace
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[ephemeraldisk]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral_disk Job Specification'
+[`heartbeat_grace`]: /nomad/docs/configuration/server#heartbeat_grace
+[`max_client_disconnect`]: /nomad/docs/job-specification/group#max_client_disconnect
+[`disable_rescheduling`]: /nomad/docs/job-specification/reschedule#disabling-rescheduling
+[max-client-disconnect]: /nomad/docs/job-specification/group#max-client-disconnect 'the example code below'
+[`stop_after_client_disconnect`]: /nomad/docs/job-specification/group#stop_after_client_disconnect
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[disconnect]: /nomad/docs/job-specification/disconnect 'Nomad disconnect Job Specification'
+[restart]: /nomad/docs/job-specification/restart 'Nomad restart Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[disconect_migration]: /nomad/docs/job-specification/group#migration_to_disconnect_block
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/expressions.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/expressions.mdx
new file mode 100644
index 0000000000..91ea784340
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/expressions.mdx
@@ -0,0 +1,438 @@
+---
+layout: docs
+page_title: Expressions - Configuration Language
+description: |-
+  HCL allows the use of expressions to access data exported
+  by sources and to transform and combine that data to produce other values.
+---
+
+# Expressions
+
+_Expressions_ are used to refer to or compute values within a configuration.
+The simplest expressions are just literal values, like `"hello"` or `5`, but
+HCL also allows more complex expressions such as arithmetic, conditional
+evaluation, and a number of built-in functions.
+
+Expressions can be used in a number of places in HCL, particularly as attribute
+values. Attribute value expressions must adhere to the attribute type. Block
+labels must be string literals without any interpolation. Each language
+feature's documentation describes any restrictions it places on expressions.
+
+The rest of this page describes all of the features of Nomad's
+expression syntax.
+
+## Types and Values
+
+The result of an expression is a _value_. All values have a _type_, which
+dictates where that value can be used and what transformations can be
+applied to it.
+
+HCL uses the following types for its values:
+
+- `string`: a sequence of Unicode characters representing some text, like
+  `"hello"`.
+- `number`: a numeric value. The `number` type can represent both whole
+  numbers like `15` and fractional values like `6.283185`.
+- `bool`: either `true` or `false`. `bool` values can be used in conditional
+  logic.
+- `list` (or `tuple`): a sequence of values, like
+  `["us-west-1a", "us-west-1c"]`. Elements in a list or tuple are identified by
+  consecutive whole numbers, starting with zero.
+- `map` (or `object`): a group of values identified by named labels, like
+  `{name = "Mabel", age = 52}`.
+
+Strings, numbers, and bools are sometimes called _primitive types._
+Lists/tuples and maps/objects are sometimes called _complex types,_ _structural
+types,_ or _collection types._
+
+Finally, there is one special value that has _no_ type:
+
+- `null`: a value that represents _absence_ or _omission._ If you set an
+  argument to `null`, Nomad behaves as though you
+  had completely omitted it — it will use the argument's default value if it has
+  one, or raise an error if the argument is mandatory. `null` is most useful in
+  conditional expressions, so you can dynamically omit an argument if a
+  condition isn't met.
+
+### Advanced Type Details
+
+In most situations, lists and tuples behave identically, as do maps and objects.
+Whenever the distinction isn't relevant, the Nomad documentation uses each
+pair of terms interchangeably (with a historical preference for "list" and
+"map").
+
+### Type Conversion
+
+Expressions are most often used to set values for arguments. In these cases,
+the argument has an expected type and the given expression must produce a value
+of that type.
+
+Where possible, Nomad automatically converts values from one type to
+another in order to produce the expected type. If this isn't possible, Nomad
+will produce a type mismatch error and you must update the configuration with a
+more suitable expression.
+
+Nomad automatically converts number and bool values to strings when needed.
+It also converts strings to numbers or bools, as long as the string contains a
+valid representation of a number or bool value.
+
+- `true` converts to `"true"`, and vice-versa
+- `false` converts to `"false"`, and vice-versa
+- `15` converts to `"15"`, and vice-versa
+
+## Literal Expressions
+
+A _literal expression_ is an expression that directly represents a particular
+constant value. Nomad has a literal expression syntax for each of the value
+types described above:
+
+- Strings are usually represented by a double-quoted sequence of Unicode
+  characters, `"like this"`. There is also a "heredoc" syntax for more complex
+  strings. String literals are the most complex kind of literal expression in
+  Nomad, and have additional documentation on this page:
+  - See [String Literals](#string-literals) below for information about escape
+    sequences and the heredoc syntax.
+  - See [String Templates](#string-templates) below for information about
+    interpolation and template directives.
+- Numbers are represented by unquoted sequences of digits with or without a
+  decimal point, like `15` or `6.283185`.
+- Bools are represented by the unquoted symbols `true` and `false`.
+- The null value is represented by the unquoted symbol `null`.
+- Lists/tuples are represented by a pair of square brackets containing a
+  comma-separated sequence of values, like `["a", 15, true]`.
+
+  List literals can be split into multiple lines for readability, but always
+  require a comma between values. A comma after the final value is allowed,
+  but not required. Values in a list can be arbitrary expressions.
+
+- Maps/objects are represented by a pair of curly braces containing a series of
+  `<KEY> = <VALUE>` pairs:
+
+  ```hcl
+  {
+    name = "John"
+    age  = 52
+  }
+  ```
+
+  Key/value pairs can be separated by either a comma or a line break. Values
+  can be arbitrary expressions. Keys are strings; they can be left unquoted if
+  they are a valid [identifier](/nomad/docs/job-specification/hcl2/syntax#identifiers), but must be quoted
+  otherwise. You can use a non-literal expression as a key by wrapping it in
+  parentheses, like `(var.business_unit_tag_name) = "SRE"`.
+
+### Available Functions
+
+For a full list of available functions, see [the function
+reference](/nomad/docs/job-specification/hcl2/functions).
+
+## `for` Expressions
+
+A _`for` expression_ creates a complex type value by transforming
+another complex type value. Each element in the input value
+can correspond to either one or zero values in the result, and an arbitrary
+expression can be used to transform each input element into an output element.
+
+For example, if `var.list` is a list of strings, then the following expression
+produces a list of strings with all-uppercase letters:
+
+```hcl
+[for s in var.list : upper(s)]
+```
+
+This `for` expression iterates over each element of `var.list`, and then
+evaluates the expression `upper(s)` with `s` set to each respective element.
+It then builds a new tuple value with all of the results of executing that
+expression in the same order.
+
+The type of brackets around the `for` expression decide what type of result
+it produces. The above example uses `[` and `]`, which produces a tuple. If
+`{` and `}` are used instead, the result is an object, and two result
+expressions must be provided separated by the `=>` symbol:
+
+```hcl
+{for s in var.list : s => upper(s)}
+```
+
+This expression produces an object whose attributes are the original elements
+from `var.list` and their corresponding values are the uppercase versions.
+
+A `for` expression can also include an optional `if` clause to filter elements
+from the source collection, which can produce a value with fewer elements than
+the source:
+
+```text
+[for s in var.list : upper(s) if s != ""]
+```
+
+The source value can also be an object or map value, in which case two
+temporary variable names can be provided to access the keys and values
+respectively:
+
+```text
+[for k, v in var.map : length(k) + length(v)]
+```
+
+Finally, if the result type is an object (using `{` and `}` delimiters) then
+the value result expression can be followed by the `...` symbol to group
+together results that have a common key:
+
+```text
+{for s in var.list : substr(s, 0, 1) => s... if s != ""}
+```
+
+<!---
+## TODO: revamp this section
+
+## Splat Expressions
+
+A _splat expression_ provides a more concise way to express a common operation
+that could otherwise be performed with a `for` expression.
+
+If `var.list` is a list of objects that all have an attribute `id`, then a list
+of the ids could be produced with the following `for` expression:
+
+```hcl
+[for o in var.list : o.id]
+```
+
+This is equivalent to the following _splat expression:_
+
+```hcl
+var.list[*].id
+```
+
+The special `[*]` symbol iterates over all of the elements of the list given to
+its left and accesses from each one the attribute name given on its right. A
+splat expression can also be used to access attributes and indexes from lists
+of complex types by extending the sequence of operations to the right of the
+symbol:
+
+```hcl
+var.list[*].interfaces[0].name
+```
+
+The above expression is equivalent to the following `for` expression:
+
+```hcl
+[for o in var.list : o.interfaces[0].name]
+```
+
+Splat expressions are for lists only (and thus cannot be used [to reference
+resources created with
+`for_each`](https://www.terraform.io/docs/configuration/resources.html#referring-to-instances), which
+are represented as maps). However, if a splat expression is applied to a value
+that is _not_ a list or tuple then the value is automatically wrapped in a
+single-element list before processing.
+
+For example, `var.single_object[*].id` is equivalent to
+`[var.single_object][*].id`, or effectively `[var.single_object.id]`. This
+behavior is not interesting in most cases, but it is particularly useful when
+referring to resources that may or may not have `count` set, and thus may or
+may not produce a tuple value:
+
+```hcl
+aws_instance.example[*].id
+```
+
+The above will produce a list of ids whether `aws_instance.example` has `count`
+set or not, avoiding the need to revise various other expressions in the
+configuration when a particular resource switches to and from having `count`
+set.
+
+--->
+
+## `dynamic` blocks
+
+Within top-level block constructs like sources, expressions can usually be used
+only when assigning a value to an argument using the `name = expression` or
+`key = expression` form. This covers many uses, but some source types include
+repeatable _nested blocks_ in their arguments, which do not accept expressions:
+
+```hcl
+network {
+  mode = "host" # can use expressions here
+
+  port "label" {
+    # but the "port" block is always a literal block
+  }
+}
+```
+
+You can dynamically construct repeatable nested blocks like `port` using a
+special `dynamic` block type, which is supported in most places, example:
+
+```hcl
+locals {
+  ports = [
+    {
+      port_label = "api"
+      port       = 80
+    },
+    {
+      port_label = "ui"
+      port       = 8080
+    }
+  ]
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+
+      mode = "host"
+
+      dynamic "port" {
+        for_each = local.ports
+        labels   = [port.value.port_label]
+
+        content {
+          to = port.value.port
+        }
+      }
+    }
+    ...
+```
+
+~> **Caveat:** Dynamic blocks are not supported inside blocks that are opaque
+to Nomad, such as the `config` attributes in [`task`][task_config],
+[`sidecar_task`][sidecar_task_config], [`proxy`][proxy_config], and
+[`gateway`][gateway_config], and the group scaling
+[`policy`][group_scaling_policy].
+
+A `dynamic` block acts much like a `for` expression, but produces nested blocks
+instead of a complex typed value. It iterates over a given complex value, and
+generates a nested block for each element of that complex value.
+
+- The label of the dynamic block (`"port"` in the example above) specifies
+  what kind of nested block to generate.
+- The `for_each` argument provides the complex value to iterate over.
+- The `iterator` argument (optional) sets the name of a temporary variable
+  that represents the current element of the complex value. If omitted, the name
+  of the variable defaults to the label of the `dynamic` block (`"port"` in
+  the example above).
+- The `labels` argument (optional) is a list of strings that specifies the block
+  labels, in order, to use for each generated block. You can use the temporary
+  iterator variable in this value. Nomad currently only has blocks that support
+  a single label such as `port`.
+- The nested `content` block defines the body of each generated block. You can
+  use the temporary iterator variable inside this block.
+
+Since the `for_each` argument accepts any collection or structural value,
+you can use a `for` expression or splat expression to transform an existing
+collection.
+
+The iterator object (`port` in the example above) has two attributes:
+
+- `key` is the map key or list element index for the current element. If the
+  `for_each` expression produces a _set_ value then `key` is identical to
+  `value` and should not be used.
+- `value` is the value of the current element.
+
+The `for_each` value must be a map or set with one element per desired nested
+block. If you need to declare resource instances based on a nested data
+structure or combinations of elements from multiple data structures you can use
+expressions and functions to derive a suitable value. For some common examples
+of such situations, see the
+[`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) and
+[`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct)
+functions.
+
+### Best Practices for `dynamic` Blocks
+
+Overuse of `dynamic` blocks can make configuration hard to read and maintain,
+so we recommend using them only when you need to hide details in order to build
+a clean user interface for a re-usable code. Always write nested blocks out
+literally where possible.
+
+## String Literals
+
+HCL has two different syntaxes for string literals. The
+most common is to delimit the string with quote characters (`"`), like
+`"hello"`. In quoted strings, the backslash character serves as an escape
+sequence, with the following characters selecting the escape behavior:
+
+| Sequence     | Replacement                                                                   |
+| ------------ | ----------------------------------------------------------------------------- |
+| `\n`         | Newline                                                                       |
+| `\r`         | Carriage Return                                                               |
+| `\t`         | Tab                                                                           |
+| `\"`         | Literal quote (without terminating the string)                                |
+| `\\`         | Literal backslash                                                             |
+| `\uNNNN`     | Unicode character from the basic multilingual plane (NNNN is four hex digits) |
+| `\UNNNNNNNN` | Unicode character from supplementary planes (NNNNNNNN is eight hex digits)    |
+
+The alternative syntax for string literals is the so-called Here Documents or
+"heredoc" style, inspired by Unix shell languages. This style allows multi-line
+strings to be expressed more clearly by using a custom delimiter word on a line
+of its own to close the string:
+
+```hcl
+<<EOF
+hello
+world
+EOF
+```
+
+The `<<` marker followed by any identifier at the end of a line introduces the
+sequence. Nomad then processes the following lines until it finds one that
+consists entirely of the identifier given in the introducer. In the above
+example, `EOF` is the identifier selected. Any identifier is allowed, but
+conventionally this identifier is in all-uppercase and begins with `EO`, meaning
+"end of". `EOF` in this case stands for "end of text".
+
+The "heredoc" form shown above requires that the lines following be flush with
+the left margin, which can be awkward when an expression is inside an indented
+block:
+
+```hcl
+block {
+  value = <<EOF
+hello
+world
+EOF
+}
+```
+
+To improve on this, Nomad also accepts an _indented_ heredoc string variant
+that is introduced by the `<<-` sequence:
+
+```hcl
+block {
+  value = <<-EOF
+  hello
+    world
+  EOF
+}
+```
+
+In this case, Nomad analyses the lines in the sequence to find the one
+with the smallest number of leading spaces, and then trims that many spaces
+from the beginning of all of the lines, leading to the following result:
+
+```text
+hello
+  world
+```
+
+Backslash sequences are not interpreted in a heredoc string expression.
+Instead, the backslash character is interpreted literally.
+
+In both quoted and heredoc string expressions, Nomad supports template
+sequences that begin with `${` and `%{`. These are described in more detail
+in the following section. To include these sequences _literally_ without
+beginning a template sequence, double the leading character: `$${` or `%%{`.
+
+## String Templates
+
+Within quoted and heredoc string expressions, the sequences `${` and `%{` begin
+_template sequences_. Templates let you directly embed expressions into a string
+literal, to dynamically construct strings from other values.
+
+[gateway_config]: /nomad/docs/job-specification/gateway#config
+[group_scaling_policy]: /nomad/docs/job-specification/scaling#policy
+[proxy_config]: /nomad/docs/job-specification/proxy#config
+[sidecar_task_config]: /nomad/docs/job-specification/sidecar_task#config
+[task_config]: /nomad/docs/job-specification/task#config
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
new file mode 100644
index 0000000000..a335154e95
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/chunklist.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: chunklist - Functions - Configuration Language
+description: |-
+  The chunklist function splits a single list into fixed-size chunks, returning
+  a list of lists.
+---
+
+# `chunklist` Function
+
+`chunklist` splits a single list into fixed-size chunks, returning a list
+of lists.
+
+```hcl
+chunklist(list, chunk_size)
+```
+
+## Examples
+
+```shell-session
+> chunklist(["a", "b", "c", "d", "e"], 2)
+[
+  ["a", "b"],
+  ["c", "d"],
+  ["e"]
+]
+> chunklist(["a", "b", "c", "d", "e"], 1)
+[
+  ["a"],
+  ["b"],
+  ["c"],
+  ["d"],
+  ["e"]
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
new file mode 100644
index 0000000000..9e64f139aa
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalesce.mdx
@@ -0,0 +1,36 @@
+---
+layout: docs
+page_title: coalesce - Functions - Configuration Language
+description: |-
+  The coalesce function takes any number of arguments and returns the
+  first one that isn't null nor empty.
+---
+
+# `coalesce` Function
+
+`coalesce` takes any number of arguments and returns the first one
+that isn't null or an empty string.
+
+## Examples
+
+```shell-session
+> coalesce("a", "b")
+a
+> coalesce("", "b")
+b
+> coalesce(1,2)
+1
+```
+
+To perform the `coalesce` operation with a list of strings, use the `...`
+symbol to expand the list as arguments:
+
+```shell-session
+> coalesce(["", "b"]...)
+b
+```
+
+## Related Functions
+
+- [`coalescelist`](/nomad/docs/job-specification/hcl2/functions/collection/coalescelist) performs a similar operation with
+  list arguments rather than individual arguments.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
new file mode 100644
index 0000000000..047cf61e97
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/coalescelist.mdx
@@ -0,0 +1,43 @@
+---
+layout: docs
+page_title: coalescelist - Functions - Configuration Language
+description: |-
+  The coalescelist function takes any number of list arguments and returns the
+  first one that isn't empty.
+---
+
+# `coalescelist` Function
+
+`coalescelist` takes any number of list arguments and returns the first one
+that isn't empty.
+
+## Examples
+
+```shell-session
+> coalescelist(["a", "b"], ["c", "d"])
+[
+  "a",
+  "b",
+]
+> coalescelist([], ["c", "d"])
+[
+  "c",
+  "d",
+]
+```
+
+To perform the `coalescelist` operation with a list of lists, use the `...`
+symbol to expand the outer list as arguments:
+
+```shell-session
+> coalescelist([[], ["c", "d"]]...)
+[
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`coalesce`](/nomad/docs/job-specification/hcl2/functions/collection/coalesce) performs a similar operation with string
+  arguments rather than list arguments.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
new file mode 100644
index 0000000000..fedf8ec0b6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/compact.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: compact - Functions - Configuration Language
+description: The compact function removes empty string elements from a list.
+---
+
+# `compact` Function
+
+`compact` takes a list of strings and returns a new list with any empty string
+elements removed.
+
+## Examples
+
+```shell-session
+> compact(["a", "", "b", "c"])
+[
+  "a",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
new file mode 100644
index 0000000000..864149c436
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/concat.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: concat - Functions - Configuration Language
+description: The concat function combines two or more lists into a single list.
+---
+
+# `concat` Function
+
+`concat` takes two or more lists and combines them into a single list.
+
+## Examples
+
+```shell-session
+> concat(["a", ""], ["b", "c"])
+[
+  "a",
+  "",
+  "b",
+  "c",
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
new file mode 100644
index 0000000000..776d3a5b7c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/contains.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: contains - Functions - Configuration Language
+description: The contains function determines whether a list or set contains a given value.
+---
+
+# `contains` Function
+
+`contains` determines whether a given list or set contains a given single value
+as one of its elements.
+
+```hcl
+contains(list, value)
+```
+
+## Examples
+
+```shell-session
+> contains(["a", "b", "c"], "a")
+true
+> contains(["a", "b", "c"], "d")
+false
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
new file mode 100644
index 0000000000..44f5186016
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/distinct.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: distinct - Functions - Configuration Language
+description: The distinct function removes duplicate elements from a list.
+---
+
+# `distinct` Function
+
+`distinct` takes a list and returns a new list with any duplicate elements
+removed.
+
+The first occurrence of each value is retained and the relative ordering of
+these elements is preserved.
+
+## Examples
+
+```shell-session
+> distinct(["a", "b", "a", "c", "d", "b"])
+[
+  "a",
+  "b",
+  "c",
+  "d",
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/element.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
new file mode 100644
index 0000000000..92d8450d3c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/element.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: element - Functions - Configuration Language
+description: The element function retrieves a single element from a list.
+---
+
+# `element` Function
+
+`element` retrieves a single element from a list.
+
+```hcl
+element(list, index)
+```
+
+The index is zero-based. This function produces an error if used with an
+empty list.
+
+Use the built-in index syntax `list[index]` in most cases. Use this function
+only for the special additional "wrap-around" behavior described below.
+
+## Examples
+
+```shell-session
+> element(["a", "b", "c"], 1)
+b
+```
+
+If the given index is greater than the length of the list then the index is
+"wrapped around" by taking the index modulo the length of the list:
+
+```shell-session
+> element(["a", "b", "c"], 3)
+a
+```
+
+## Related Functions
+
+- [`index`](/nomad/docs/job-specification/hcl2/functions/collection/index-fn) finds the index for a particular element value.
+- [`lookup`](/nomad/docs/job-specification/hcl2/functions/collection/lookup) retrieves a value from a _map_ given its _key_.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
new file mode 100644
index 0000000000..734fbf6589
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/flatten.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: flatten - Functions - Configuration Language
+description: The flatten function eliminates nested lists from a list.
+---
+
+# `flatten` Function
+
+`flatten` takes a list and replaces any elements that are lists with a
+flattened sequence of the list contents.
+
+## Examples
+
+```shell-session
+> flatten([["a", "b"], [], ["c"]])
+["a", "b", "c"]
+```
+
+If any of the nested lists also contain directly-nested lists, these too are
+flattened recursively:
+
+```shell-session
+> flatten([[["a", "b"], []], ["c"]])
+["a", "b", "c"]
+```
+
+Indirectly-nested lists, such as those in maps, are _not_ flattened.
+
+<!---
+
+## TODO: revamp this section
+
+## Flattening nested structures for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data structure isn't naturally in a suitable shape for
+use in a `for_each` argument, and `flatten` can be a useful helper function
+when reducing a nested data structure into a flat one.
+
+For example, consider a folder that declares a variable like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    cidr_block = string
+    subnets = map(object({
+      cidr_block = string
+    })
+  })
+}
+```
+
+The above is a reasonable way to model objects that naturally form a tree,
+such as top-level networks and their subnets. The repetition for the top-level
+networks can use this variable directly, because it's already in a form
+where the resulting instances match one-to-one with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first flatten the structure to produce a collection where each
+top-level element represents a single subnet:
+
+```hcl
+locals {
+  # flatten ensures that this local value is a flat list of objects, rather
+  # than a list of lists of objects.
+  network_subnets = flatten([
+    for network_key, network in var.networks : [
+      for subnet_key, subnet in network.subnets : {
+        network_key = network_key
+        subnet_key  = subnet_key
+        network_id  = aws_vpc.example[network_key].id
+        cidr_block  = subnet.cidr_block
+      }
+    ]
+  ])
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per subnet object, while retaining
+the associations between the subnets and their containing networks.
+
+-->
+
+## Related Functions
+
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) finds all of the combinations of multiple
+  lists or sets of values, which can also be useful when preparing collections
+  for use with `for_each` constructs.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
new file mode 100644
index 0000000000..fb3149cc18
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/index-fn.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: index - Functions - Configuration Language
+description: |-
+  The index function returns an element from the given list or map
+  using the given index or key.
+---
+
+# `index` Function
+
+`index` finds the element at the index when handling lists, or the element at
+the key when handling maps.
+
+```hcl
+index(list, value)
+```
+
+## Examples
+
+```shell-session
+> index(["a", "b", "c"], 1)
+"b"
+```
+
+```shell-session
+> index({"a"=1, "c"=2, "d"=3}, "c")
+2
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a particular element from a list given
+  its index.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
new file mode 100644
index 0000000000..0042442e31
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/keys.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: keys - Functions - Configuration Language
+description: The keys function returns a list of the keys in a given map.
+---
+
+# `keys` Function
+
+`keys` takes a map and returns a list containing the keys from that map.
+
+The keys are returned in lexicographical order, ensuring that the result will
+be identical as long as the keys in the map don't change.
+
+## Examples
+
+```shell-session
+> keys({a=1, c=2, d=3})
+[
+  "a",
+  "c",
+  "d",
+]
+```
+
+## Related Functions
+
+- [`values`](/nomad/docs/job-specification/hcl2/functions/collection/values) returns a list of the _values_ from a map.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/length.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
new file mode 100644
index 0000000000..3c56ff2b36
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/length.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: length - Functions - Configuration Language
+description: The length function determines the length of a collection.
+---
+
+# `length` Function
+
+`length` determines the length of a given list, map, or tuple.
+
+If given a list, map, or tuple, the result is the number of elements in that
+collection.
+
+## Examples
+
+```shell-session
+> length([])
+0
+> length(["a", "b"])
+2
+> length({"a" = "b"})
+1
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
new file mode 100644
index 0000000000..6648828fd9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/lookup.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lookup - Functions - Configuration Language
+description: The lookup function retrieves an element value from a map given its key.
+---
+
+# `lookup` Function
+
+`lookup` retrieves the value of a single element from a map, given its key.
+If the given key does not exist, a the given default value is returned instead.
+
+```hcl
+lookup(map, key, default)
+```
+
+## Examples
+
+```shell-session
+> lookup({a="ay", b="bee"}, "a", "what?")
+ay
+> lookup({a="ay", b="bee"}, "c", "what?")
+what?
+```
+
+## Related Functions
+
+- [`element`](/nomad/docs/job-specification/hcl2/functions/collection/element) retrieves a value from a _list_ given its _index_.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
new file mode 100644
index 0000000000..e8c37ac530
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/merge.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: merge - Functions - Configuration Language
+description: |-
+  The merge function takes an arbitrary number of maps and returns a single
+  map after merging the keys from each argument.
+---
+
+# `merge` Function
+
+`merge` takes an arbitrary number of maps and returns a single map that
+contains a merged set of elements from all of the maps.
+
+If more than one given map defines the same key then the one that is later
+in the argument sequence takes precedence.
+
+## Examples
+
+```shell-session
+> merge({"a"="b", "c"="d"}, {"e"="f", "c"="z"})
+{
+  "a" = "b"
+  "c" = "z"
+  "e" = "f"
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/range.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
new file mode 100644
index 0000000000..82a04671b3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/range.mdx
@@ -0,0 +1,140 @@
+---
+layout: docs
+page_title: range - Functions - Configuration Language
+description: The range function generates sequences of numbers.
+---
+
+# `range` Function
+
+`range` generates a list of numbers using a start value, a limit value,
+and a step value.
+
+```hcl
+range(max)
+range(start, limit)
+range(start, limit, step)
+```
+
+The `start` and `step` arguments can be omitted, in which case `start` defaults
+to zero and `step` defaults to either one or negative one depending on whether
+`limit` is greater than or less than `start`.
+
+The resulting list is created by starting with the given `start` value and
+repeatedly adding `step` to it until the result is equal to or beyond `limit`.
+
+The interpretation of `limit` depends on the direction of `step`: for a positive
+step, the sequence is complete when the next number is greater than or equal
+to `limit`. For a negative step, it's complete when less than or equal.
+
+The sequence-building algorithm follows the following pseudocode:
+
+```text
+let num = start
+while num < limit: (or, for negative step, num >= limit)
+  append num to the sequence
+  num = num + step
+return the sequence
+```
+
+Because the sequence is created as a physical list in memory, Nomad imposes
+an artificial limit of 1024 numbers in the resulting sequence in order to avoid
+unbounded memory usage if, for example, a very large value were accidentally
+passed as the limit or a very small value as the step. If the algorithm above
+would append the 1025th number to the sequence, the function immediately exits
+with an error.
+
+We recommend iterating over existing collections where possible, rather than
+creating ranges. However, creating small numerical sequences can sometimes
+be useful when combined with other collections in collection-manipulation
+functions or `for` expressions.
+
+## Examples
+
+```shell-session
+> range(3)
+[
+  0,
+  1,
+  2,
+]
+
+> range(1, 4)
+[
+  1,
+  2,
+  3,
+]
+
+> range(1, 8, 2)
+[
+  1,
+  3,
+  5,
+  7,
+]
+
+> range(1, 4, 0.5)
+[
+  1,
+  1.5,
+  2,
+  2.5,
+  3,
+  3.5,
+]
+
+> range(4, 1)
+[
+  4,
+  3,
+  2,
+]
+
+> range(10, 5, -2)
+[
+  10,
+  8,
+  6,
+]
+```
+
+The `range` function is primarily useful when working with other collections
+to produce a certain number of instances of something. For example:
+
+```hcl
+variable "name_counts" {
+  type    = map(number)
+  default = {
+    "foo" = 2
+    "bar" = 4
+  }
+}
+
+locals {
+  expanded_names = {
+    for name, count in var.name_counts : name => [
+      for i in range(count) : format("%s%02d", name, i)
+    ]
+  }
+}
+
+output "expanded_names" {
+  value = local.expanded_names
+}
+
+# Produces the following expanded_names value when run with the default
+# "name_counts":
+#
+# {
+#   "bar" = [
+#     "bar00",
+#     "bar01",
+#     "bar02",
+#     "bar03",
+#   ]
+#   "foo" = [
+#     "foo00",
+#     "foo01",
+#   ]
+# }
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
new file mode 100644
index 0000000000..8019e09e95
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/reverse.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: reverse - Functions - Configuration Language
+description: The reverse function reverses a sequence.
+---
+
+# `reverse` Function
+
+`reverse` takes a sequence and produces a new sequence of the same length
+with all of the same elements as the given sequence but in reverse order.
+
+## Examples
+
+```shell-session
+> reverse([1, 2, 3])
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`strrev`](/nomad/docs/job-specification/hcl2/functions/string/strrev) reverses a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
new file mode 100644
index 0000000000..0bab199095
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setintersection.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: setintersection - Functions - Configuration Language
+description: |-
+  The setintersection function takes multiple sets and produces a single set
+  containing only the elements that all of the given sets have in common.
+---
+
+# `setintersection` Function
+
+The `setintersection` function takes multiple sets and produces a single set
+containing only the elements that all of the given sets have in common.
+In other words, it computes the
+[intersection](<https://en.wikipedia.org/wiki/Intersection_(set_theory)>) of the sets.
+
+```hcl
+setintersection(sets...)
+```
+
+## Examples
+
+```shell-session
+> setintersection(["a", "b"], ["b", "c"], ["b", "d"])
+[
+  "b",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of
+  multiple sets.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
new file mode 100644
index 0000000000..6cf8bcbd89
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setproduct.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: setproduct - Functions - Configuration Language
+description: |-
+  The setproduct function finds all of the possible combinations of elements
+  from all of the given sets by computing the cartesian product.
+---
+
+# `setproduct` Function
+
+The `setproduct` function finds all of the possible combinations of elements
+from all of the given sets by computing the
+[Cartesian product](https://en.wikipedia.org/wiki/Cartesian_product).
+
+```hcl
+setproduct(sets...)
+```
+
+This function is particularly useful for finding the exhaustive set of all
+combinations of members of multiple sets, such as per-application-per-environment
+resources.
+
+```shell-session
+> setproduct(["development", "staging", "production"], ["app1", "app2"])
+[
+  [
+    "development",
+    "app1",
+  ],
+  [
+    "development",
+    "app2",
+  ],
+  [
+    "staging",
+    "app1",
+  ],
+  [
+    "staging",
+    "app2",
+  ],
+  [
+    "production",
+    "app1",
+  ],
+  [
+    "production",
+    "app2",
+  ],
+]
+```
+
+You must past at least two arguments to this function.
+
+Although defined primarily for sets, this function can also work with lists.
+If all of the given arguments are lists then the result is a list, preserving
+the ordering of the given lists. Otherwise the result is a set. In either case,
+the result's element type is a list of values corresponding to each given
+argument in turn.
+
+## Examples
+
+There is an example of the common usage of this function above. There are some
+other situations that are less common when hand-writing but may arise in
+reusable folder situations.
+
+If any of the arguments is empty then the result is always empty itself,
+similar to how multiplying any number by zero gives zero:
+
+```shell-session
+> setproduct(["development", "staging", "production"], [])
+[]
+```
+
+Similarly, if all of the arguments have only one element then the result has
+only one element, which is the first element of each argument:
+
+```shell-session
+> setproduct(["a"], ["b"])
+[
+  [
+    "a",
+    "b",
+  ],
+]
+```
+
+Each argument must have a consistent type for all of its elements. If not,
+Nomad will attempt to convert to the most general type, or produce an
+error if such a conversion is impossible. For example, mixing both strings and
+numbers results in the numbers being converted to strings so that the result
+elements all have a consistent type:
+
+```shell-session
+> setproduct(["staging", "production"], ["a", 2])
+[
+  [
+    "staging",
+    "a",
+  ],
+  [
+    "staging",
+    "2",
+  ],
+  [
+    "production",
+    "a",
+  ],
+  [
+    "production",
+    "2",
+  ],
+]
+```
+
+<!---
+
+## TODO: Revamp this section
+
+## Finding combinations for `for_each`
+
+The
+[resource `for_each`](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+and
+[`dynamic` block](/nomad/docs/job-specification/hcl2/expressions/#dynamic-blocks)
+language features both require a collection value that has one element for
+each repetition.
+
+Sometimes your input data comes in separate values that cannot be directly
+used in a `for_each` argument, and `setproduct` can be a useful helper function
+for the situation where you want to find all unique combinations of elements in
+a number of different collections.
+
+For example, consider a folder that declares variables like the following:
+
+```hcl
+variable "networks" {
+  type = map(object({
+    base_cidr_block = string
+  }))
+}
+
+variable "subnets" {
+  type = map(object({
+    number = number
+  }))
+}
+```
+
+If the goal is to create each of the defined subnets per each of the defined
+networks, creating the top-level networks can directly use `var.networks`
+because it's already in a form where the resulting instances match one-to-one
+with map elements:
+
+```hcl
+resource "aws_vpc" "example" {
+  for_each = var.networks
+
+  cidr_block = each.value.base_cidr_block
+}
+```
+
+However, in order to declare all of the _subnets_ with a single `resource`
+block, we must first produce a collection whose elements represent all of
+the combinations of networks and subnets, so that each element itself
+represents a subnet:
+
+```hcl
+locals {
+  # setproduct works with sets and lists, but our variables are both maps
+  # so we'll need to convert them first.
+  networks = [
+    for key, network in var.networks : {
+      key        = key
+      cidr_block = network.cidr_block
+    }
+  ]
+  subnets = [
+    for key, subnet in var.subnets : {
+      key    = key
+      number = subnet.number
+    }
+  ]
+
+  network_subnets = [
+    # in pair, element zero is a network and element one is a subnet,
+    # in all unique combinations.
+    for pair in setproduct(local.networks, local.subnets) : {
+      network_key = pair[0].key
+      subnet_key  = pair[1].key
+      network_id  = aws_vpc.example[pair[0].key].id
+
+      # The cidr_block is derived from the corresponding network. See the
+      # cidrsubnet function for more information on how this calculation works.
+      cidr_block = cidrsubnet(pair[0].cidr_block, 4, pair[1].number)
+    }
+  ]
+}
+
+resource "aws_subnet" "example" {
+  # local.network_subnets is a list, so we must now project it into a map
+  # where each key is unique. We'll combine the network and subnet keys to
+  # produce a single unique key per instance.
+  for_each = {
+    for subnet in local.network_subnets : "${subnet.network_key}.${subnet.subnet_key}" => subnet
+  }
+
+  vpc_id            = each.value.network_id
+  availability_zone = each.value.subnet_key
+  cidr_block        = each.value_cidr_block
+}
+```
+
+The above results in one subnet instance per combination of network and subnet
+elements in the input variables.
+
+-->
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`flatten`](/nomad/docs/job-specification/hcl2/functions/collection/flatten) is useful for flattening hierarchical data
+  into a single list, for situations where the relationships between two
+  object types are defined explicitly.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setunion`](/nomad/docs/job-specification/hcl2/functions/collection/setunion) computes the _union_ of multiple
+  sets.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
new file mode 100644
index 0000000000..6117bc2e6f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/setunion.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: setunion - Functions - Configuration Language
+description: |-
+  The setunion function takes multiple sets and produces a single set
+  containing the elements from all of the given sets.
+---
+
+# `setunion` Function
+
+The `setunion` function takes multiple sets and produces a single set
+containing the elements from all of the given sets. In other words, it
+computes the [union](<https://en.wikipedia.org/wiki/Union_(set_theory)>) of
+the sets.
+
+```hcl
+setunion(sets...)
+```
+
+## Examples
+
+```shell-session
+> setunion(["a", "b"], ["b", "c"], ["d"])
+[
+  "d",
+  "b",
+  "c",
+  "a",
+]
+```
+
+The given arguments are converted to sets, so the result is also a set and
+the ordering of the given elements is not preserved.
+
+## Related Functions
+
+- [`contains`](/nomad/docs/job-specification/hcl2/functions/collection/contains) tests whether a given list or set contains
+  a given element value.
+- [`setintersection`](/nomad/docs/job-specification/hcl2/functions/collection/setintersection) computes the _intersection_ of
+  multiple sets.
+- [`setproduct`](/nomad/docs/job-specification/hcl2/functions/collection/setproduct) computes the _Cartesian product_ of multiple
+  sets.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
new file mode 100644
index 0000000000..7ce68f3fb9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/slice.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: slice - Functions - Configuration Language
+description: The slice function extracts some consecutive elements from within a list.
+---
+
+# `slice` Function
+
+`slice` extracts some consecutive elements from within a list.
+
+```hcl
+slice(list, startindex, endindex)
+```
+
+`startindex` is inclusive, while `endindex` is exclusive. This function returns
+an error if either index is outside the bounds of valid indices for the given
+list.
+
+## Examples
+
+```shell-session
+> slice(["a", "b", "c", "d"], 1, 3)
+[
+  "b",
+  "c",
+]
+```
+
+## Related Functions
+
+- [`substr`](/nomad/docs/job-specification/hcl2/functions/string/substr) performs a similar function for characters in a
+  string, although it uses a length instead of an end index.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
new file mode 100644
index 0000000000..dd7c04b0f2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/sort.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sort - Functions - Configuration Language
+description: |-
+  The sort function takes a list of strings and returns a new list with those
+  strings sorted lexicographically.
+---
+
+# `sort` Function
+
+`sort` takes a list of strings and returns a new list with those strings
+sorted lexicographically.
+
+The sort is in terms of Unicode codepoints, with higher codepoints appearing
+after lower ones in the result.
+
+## Examples
+
+```shell-session
+> sort(["e", "d", "a", "x"])
+[
+  "a",
+  "d",
+  "e",
+  "x",
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/values.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
new file mode 100644
index 0000000000..681ac43162
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/values.mdx
@@ -0,0 +1,29 @@
+---
+layout: docs
+page_title: values - Functions - Configuration Language
+description: The values function returns a list of the element values in a given map.
+---
+
+# `values` Function
+
+`values` takes a map and returns a list containing the values of the elements
+in that map.
+
+The values are returned in lexicographical order by their corresponding _keys_,
+so the values will be returned in the same order as their keys would be
+returned from [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys).
+
+## Examples
+
+```shell-session
+> values({a=3, c=2, d=1})
+[
+  3,
+  2,
+  1,
+]
+```
+
+## Related Functions
+
+- [`keys`](/nomad/docs/job-specification/hcl2/functions/collection/keys) returns a list of the _keys_ from a map.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
new file mode 100644
index 0000000000..0a9a5e5211
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/collection/zipmap.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: zipmap - Functions - Configuration Language
+description: |-
+  The zipmap function constructs a map from a list of keys and a corresponding
+  list of values.
+---
+
+# `zipmap` Function
+
+`zipmap` constructs a map from a list of keys and a corresponding list of
+values.
+
+```hcl
+zipmap(keyslist, valueslist)
+```
+
+Both `keyslist` and `valueslist` must be of the same length. `keyslist` must
+be a list of strings, while `valueslist` can be a list of any type.
+
+Each pair of elements with the same index from the two lists will be used
+as the key and value of an element in the resulting map. If the same value
+appears multiple times in `keyslist` then the value with the highest index
+is used in the resulting map.
+
+## Examples
+
+```shell-session
+> zipmap(["a", "b"], [1, 2])
+{
+  "a" = 1,
+  "b" = 2,
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
new file mode 100644
index 0000000000..d8ff833c50
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/can.mdx
@@ -0,0 +1,58 @@
+---
+layout: docs
+page_title: can - Functions - Configuration Language
+description: |-
+  The can function tries to evaluate an expression given as an argument and
+  indicates whether the evaluation succeeded.
+---
+
+# `can` Function
+
+`can` evaluates the given expression and returns a boolean value indicating
+whether the expression produced a result without any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its argument. For most situations where you could use `can` it's better to use
+[`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try) instead, because it allows for more concise definition of
+fallback values for failing expressions.
+
+The `can` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `can` function is intended only for simple tests in
+variable validation rules. Although it can technically accept any sort of
+expression and be used elsewhere in the configuration, we recommend against
+using it in other contexts. For error handling elsewhere in the configuration,
+prefer to use [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try).
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> can(local.foo.bar)
+true
+> can(local.foo.boop)
+false
+```
+
+The `can` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> can(local.nonexist)
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`try`](/nomad/docs/job-specification/hcl2/functions/conversion/try), which tries evaluating a sequence of expressions and
+  returns the result of the first one that succeeds.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
new file mode 100644
index 0000000000..59feaad57c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/convert.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: convert - Functions - Configuration Language
+description: 'The convert function converts a value or an expression to a given type. '
+---
+
+# `convert` Function
+
+`convert` converts a value or an expression to a given type.
+
+Explicit type conversions are rarely necessary in HCL because it will convert
+types automatically where required. Use the explicit type conversion functions
+only to normalize types returned in outputs.
+
+Only numbers and strings containing decimal representations of numbers can be
+converted to number. All other values will produce an error.
+
+Only boolean values and the exact strings "true" and "false" can be converted
+to boolean. All other values will produce an error.
+
+Only the primitive types (string, number, and bool) can be converted to string.
+All other values will produce an error.
+
+`convert(value, type_constraint)`
+
+## Examples
+
+```shell-session
+> convert(3, string)
+"3"
+> convert("3", number)
+3
+> convert("false", bool)
+false
+> convert(false, string)
+"false"
+> convert(["a", "b", 3], list(string))
+[
+  "a",
+  "b",
+  "3",
+]
+> convert(["c", "b", "b"], set(string))
+[
+  "b",
+  "c",
+]
+> convert({"a" = "foo", "b" = true}, map(string))
+{
+  "a" = "foo"
+  "b" = "true"
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
new file mode 100644
index 0000000000..ff9b2c0bb4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/conversion/try.mdx
@@ -0,0 +1,112 @@
+---
+layout: docs
+page_title: try - Functions - Configuration Language
+description: |-
+  The try function tries to evaluate a sequence of expressions given as
+  arguments and returns the result of the first one that does not produce
+  any errors.
+---
+
+# `try` Function
+
+`try` evaluates all of its argument expressions in turn and returns the result
+of the first one that does not produce any errors.
+
+This is a special function that is able to catch errors produced when evaluating
+its arguments, which is particularly useful when working with complex data
+structures whose shape is not well-known at implementation time.
+
+For example, if some data is retrieved from an external system in JSON or YAML
+format and then decoded, the result may have attributes that are not guaranteed
+to be set. We can use `try` to produce a normalized data structure which has
+a predictable type that can therefore be used more conveniently elsewhere in
+the configuration:
+
+```hcl
+locals {
+  raw_value = yamldecode("${path.folder}/example.yaml")
+  normalized_value = {
+    name   = tostring(try(local.raw_value.name, null))
+    groups = try(local.raw_value.groups, [])
+  }
+}
+```
+
+With the above local value expressions, configuration elsewhere in the folder
+can refer to `local.normalized_value` attributes without the need to repeatedly
+check for and handle absent attributes that would otherwise produce errors.
+
+We can also use `try` to deal with situations where a value might be provided
+in two different forms, allowing us to normalize to the most general form:
+
+```hcl
+variable "example" {
+  type = any
+}
+
+locals {
+  example = try(
+    [tostring(var.example)],
+    tolist(var.example),
+  )
+}
+```
+
+The above permits `var.example` to be either a list or a single string. If it's
+a single string then it'll be normalized to a single-element list containing
+that string, again allowing expressions elsewhere in the configuration to just
+assume that `local.example` is always a list.
+
+This second example contains two expressions that can both potentially fail.
+For example, if `var.example` were set to `{}` then it could be converted to
+neither a string nor a list. If `try` exhausts all of the given expressions
+without any succeeding, it will return an error describing all of the problems
+it encountered.
+
+We strongly suggest using `try` only in special local values whose expressions
+perform normalization, so that the error handling is confined to a single
+location in the folder and the rest of the folder can just use straightforward
+references to the normalized structure and thus be more readable for future
+maintainers.
+
+The `try` function can only catch and handle _dynamic_ errors resulting from
+access to data that isn't known until runtime. It will not catch errors
+relating to expressions that can be proven to be invalid for any input, such
+as a malformed reference.
+
+~> **Warning:** The `try` function is intended only for concise testing of the
+presence of and types of object attributes. Although it can technically accept
+any sort of expression, we recommend using it only with simple attribute
+references and type conversion functions as shown in the examples above.
+Overuse of `try` to suppress errors will lead to a configuration that is hard
+to understand and maintain.
+
+## Examples
+
+```shell-session
+> local.foo
+{
+  "bar" = "baz"
+}
+> try(local.foo.bar, "fallback")
+baz
+> try(local.foo.boop, "fallback")
+fallback
+```
+
+The `try` function will _not_ catch errors relating to constructs that are
+provably invalid even before dynamic expression evaluation, such as a malformed
+reference or a reference to a top-level object that has not been declared:
+
+```shell-session
+> try(local.nonexist, "fallback")
+
+Error: Reference to undeclared local value
+
+A local value with the name "nonexist" has not been declared.
+```
+
+## Related Functions
+
+- [`can`](/nomad/docs/job-specification/hcl2/functions/conversion/can), which tries evaluating an expression and returns a
+  boolean value indicating whether it succeeded.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
new file mode 100644
index 0000000000..bb7253c29e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/bcrypt.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: bcrypt - Functions - Configuration Language
+description: |-
+  The bcrypt function computes a hash of the given string using the Blowfish
+  cipher.
+---
+
+# `bcrypt` Function
+
+`bcrypt` computes a hash of the given string using the Blowfish cipher,
+returning a string in [the _Modular Crypt
+Format_](https://passlib.readthedocs.io/en/stable/modular_crypt_format.html)
+usually expected in the shadow password file on many Unix systems.
+
+```hcl
+bcrypt(string, cost)
+```
+
+The `cost` argument is optional and will default to 10 if unspecified.
+
+Since a bcrypt hash value includes a randomly selected salt, each call to this
+function will return a different value, even if the given string and cost are
+the same. Using this function directly with job arguments will therefore
+cause spurious job updates.
+
+The version prefix on the generated string (e.g. `$2a$`) may change in future
+versions of Nomad.
+
+## Examples
+
+```shell-session
+> bcrypt("hello world")
+$2a$10$D5grTTzcsqyvAeIAnY/mYOIqliCoG7eAMX0/oFcuD.iErkksEbcAa
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
new file mode 100644
index 0000000000..6a7eaed51e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/md5.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: md5 - Functions - Configuration Language
+description: |-
+  The md5 function computes the MD5 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `md5` Function
+
+`md5` computes the MD5 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the MD5 algorithm is applied
+as defined in [RFC 1321](https://tools.ietf.org/html/rfc1321). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Before using this function for anything security-sensitive, refer to
+[RFC 6151](https://tools.ietf.org/html/rfc6151) for updated security
+considerations applying to the MD5 algorithm.
+
+## Examples
+
+```shell-session
+> md5("hello world")
+5eb63bbbe01eeed093cb22bb8f5acdc3
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
new file mode 100644
index 0000000000..6f964b533f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/rsadecrypt.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: rsadecrypt - Functions - Configuration Language
+description: The rsadecrypt function decrypts an RSA-encrypted message.
+---
+
+# `rsadecrypt` Function
+
+<Note title="Deprecated">
+This function is deprecated and may be removed in the future.
+</Note>
+
+<Warning>
+While it is possible to use safely, it encourages use of cryptographic
+primitives with <a href="https://en.wikipedia.org/wiki/PKCS_1#Attacks">known
+weaknesses</a>. <a href="/nomad/docs/concepts/variables">Nomad Variables</a>
+and <a href="/nomad/docs/integrations/vault-integration">HashiCorp Vault</a> are
+the recommended ways to provide secrets to workloads.
+</Warning>
+
+`rsadecrypt` decrypts an RSA-encrypted ciphertext, returning the corresponding
+cleartext.
+
+```hcl
+rsadecrypt(ciphertext, privatekey)
+```
+
+`ciphertext` must be a base64-encoded representation of the ciphertext, using
+the PKCS #1 v1.5 padding scheme. Nomad uses the "standard" Base64 alphabet
+as defined in [RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+`privatekey` must be a PEM-encoded RSA private key that is not itself
+encrypted.
+
+Nomad has no corresponding function for _encrypting_ a message. Use this
+function to decrypt ciphertexts returned by remote services using a keypair
+negotiated out-of-band.
+
+## Examples
+
+```shell-session
+> rsadecrypt(base64(file("${path.folder}/ciphertext")), file("privatekey.pem"))
+Hello, world!
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
new file mode 100644
index 0000000000..ad0b1f76e9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha1.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: sha1 - Functions - Configuration Language
+description: |-
+  The sha1 function computes the SHA1 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha1` Function
+
+`sha1` computes the SHA1 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA1 algorithm is applied
+as defined in [RFC 3174](https://tools.ietf.org/html/rfc3174). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+Collision attacks have been successfully performed against this hashing
+function. Before using this function for anything security-sensitive, review
+relevant literature to understand the security implications.
+
+## Examples
+
+```shell-session
+> sha1("hello world")
+2aae6c35c94fcfb415dbe95f408b9ce91ee846ed
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
new file mode 100644
index 0000000000..d63232d74d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha256.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha256 - Functions - Configuration Language
+description: |-
+  The sha256 function computes the SHA256 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha256` Function
+
+`sha256` computes the SHA256 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA256 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha256("hello world")
+b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
new file mode 100644
index 0000000000..8ae21790d2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/crypto/sha512.mdx
@@ -0,0 +1,23 @@
+---
+layout: docs
+page_title: sha512 - Functions - Configuration Language
+description: |-
+  The sha512 function computes the SHA512 hash of a given string and encodes it
+  with hexadecimal digits.
+---
+
+# `sha512` Function
+
+`sha512` computes the SHA512 hash of a given string and encodes it with
+hexadecimal digits.
+
+The given string is first encoded as UTF-8 and then the SHA512 algorithm is applied
+as defined in [RFC 4634](https://tools.ietf.org/html/rfc4634). The raw hash is
+then encoded to lowercase hexadecimal digits before returning.
+
+## Examples
+
+```shell-session
+> sha512("hello world")
+309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
new file mode 100644
index 0000000000..a6106b72da
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/formatdate.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: formatdate - Functions - Configuration Language
+description: The formatdate function converts a timestamp into a different time format.
+---
+
+# `formatdate` Function
+
+`formatdate` converts a timestamp into a different time format.
+
+```hcl
+formatdate(spec, timestamp)
+```
+
+In Nomad, timestamps are conventionally represented as strings using [RFC
+3339](https://tools.ietf.org/html/rfc3339) "Date and Time format" syntax.
+`formatdate` requires the `timestamp` argument to be a string conforming to
+this syntax.
+
+## Examples
+
+```shell-session
+> formatdate("DD MMM YYYY hh:mm ZZZ", "2018-01-02T23:12:01Z")
+02 Jan 2018 23:12 UTC
+> formatdate("EEEE, DD-MMM-YY hh:mm:ss ZZZ", "2018-01-02T23:12:01Z")
+Tuesday, 02-Jan-18 23:12:01 UTC
+> formatdate("EEE, DD MMM YYYY hh:mm:ss ZZZ", "2018-01-02T23:12:01-08:00")
+Tue, 02 Jan 2018 23:12:01 -0800
+> formatdate("MMM DD, YYYY", "2018-01-02T23:12:01Z")
+Jan 02, 2018
+> formatdate("HH:mmaa", "2018-01-02T23:12:01Z")
+11:12pm
+```
+
+## Specification Syntax
+
+The format specification is a string that includes formatting sequences from
+the following table. This function is intended for producing common
+_machine-oriented_ timestamp formats such as those defined in RFC822, RFC850,
+and RFC1123. It is not suitable for truly human-oriented date formatting
+because it is not locale-aware. In particular, it can produce month and day
+names only in English.
+
+The specification may contain the following sequences:
+
+| Sequence | Result                                                                  |
+| -------- | ----------------------------------------------------------------------- |
+| `YYYY`   | Four (or more) digit year, like "2006".                                 |
+| `YY`     | The year modulo 100, zero padded to at least two digits, like "06".     |
+| `MMMM`   | English month name unabbreviated, like "January".                       |
+| `MMM`    | English month name abbreviated to three letters, like "Jan".            |
+| `MM`     | Month number zero-padded to two digits, like "01" for January.          |
+| `M`      | Month number with no padding, like "1" for January.                     |
+| `DD`     | Day of month number zero-padded to two digits, like "02".               |
+| `D`      | Day of month number with no padding, like "2".                          |
+| `EEEE`   | English day of week name unabbreviated, like "Monday".                  |
+| `EEE`    | English day of week name abbreviated to three letters, like "Mon".      |
+| `hh`     | 24-hour number zero-padded to two digits, like "02".                    |
+| `h`      | 24-hour number unpadded, like "2".                                      |
+| `HH`     | 12-hour number zero-padded to two digits, like "02".                    |
+| `H`      | 12-hour number unpadded, like "2".                                      |
+| `AA`     | Hour AM/PM marker in uppercase, like "AM".                              |
+| `aa`     | Hour AM/PM marker in lowercase, like "am".                              |
+| `mm`     | Minute within hour zero-padded to two digits, like "05".                |
+| `m`      | Minute within hour unpadded, like "5".                                  |
+| `ss`     | Second within minute zero-padded to two digits, like "09".              |
+| `s`      | Second within minute, like "9".                                         |
+| `ZZZZZ`  | Timezone offset with colon separating hours and minutes, like "-08:00". |
+| `ZZZZ`   | Timezone offset with just sign and digit, like "-0800".                 |
+| `ZZZ`    | Like `ZZZZ` but with a special case "UTC" for UTC.                      |
+| `Z`      | Like `ZZZZZ` but with a special case "Z" for UTC.                       |
+
+Any non-letter characters, such as punctuation, are reproduced verbatim in the
+output. To include literal letters in the format string, enclose them in single
+quotes `'`. To include a literal quote, escape it by doubling the quotes.
+
+```shell-session
+> formatdate("h'h'mm", "2018-01-02T23:12:01-08:00")
+23h12
+> formatdate("H 'o''clock'", "2018-01-02T23:12:01-08:00")
+11 o'clock
+```
+
+This format specification syntax is intended to make it easy for a reader
+to guess which format will result even if they are not experts on the syntax.
+Therefore there are no predefined shorthands for common formats, but format
+strings for various RFC-specified formats are given below to be copied into your
+configuration as needed:
+
+- [RFC 822](https://tools.ietf.org/html/rfc822#section-5) and
+  [RFC 2822](https://tools.ietf.org/html/rfc2822#section-3.3):
+  `"DD MMM YYYY hh:mm ZZZ"`
+- [RFC 850](https://tools.ietf.org/html/rfc850#section-2.1.4):
+  `"EEEE, DD-MMM-YY hh:mm:ss ZZZ"`
+- [RFC 1123](https://tools.ietf.org/html/rfc1123#section-5.2.14):
+  `"EEE, DD MMM YYYY hh:mm:ss ZZZ"`
+- [RFC 3339](https://tools.ietf.org/html/rfc3339):
+  `"YYYY-MM-DD'T'hh:mm:ssZ"` (but this is also the input format, so such a
+  conversion is redundant.)
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) is a more general formatting function for arbitrary
+  data.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
new file mode 100644
index 0000000000..7ccefef302
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/datetime/timeadd.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: timeadd - Functions - Configuration Language
+description: |-
+  The timeadd function adds a duration to a timestamp, returning a new
+  timestamp.
+---
+
+# `timeadd` Function
+
+`timeadd` adds a duration to a timestamp, returning a new timestamp.
+
+```hcl
+timeadd(timestamp, duration)
+```
+
+In the Nomad language, timestamps are conventionally represented as
+strings using [RFC 3339](https://tools.ietf.org/html/rfc3339)
+"Date and Time format" syntax. `timeadd` requires the `timestamp` argument
+to be a string conforming to this syntax.
+
+`duration` is a string representation of a time difference, consisting of
+sequences of number and unit pairs, like `"1.5h"` or `"1h30m"`. The accepted
+units are `"ns"`, `"us"` (or `"µs"`), `"ms"`, `"s"`, `"m"`, and `"h"`. The first
+number may be negative to indicate a negative duration, like `"-2h5m"`.
+
+The result is a string, also in RFC 3339 format, representing the result
+of adding the given direction to the given timestamp.
+
+## Examples
+
+```shell-session
+> timeadd("2017-11-22T00:00:00Z", "10m")
+2017-11-22T00:10:00Z
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
new file mode 100644
index 0000000000..d2cc5bed2e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64decode.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: base64decode - Functions - Configuration Language
+description: The base64decode function decodes a string containing a base64 sequence.
+---
+
+# `base64decode` Function
+
+`base64decode` takes a string containing a Base64 character sequence and
+returns the original string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will also interpret the resulting bytes as
+UTF-8. If the bytes after Base64 decoding are _not_ valid UTF-8, this function
+produces an error.
+
+## Examples
+
+```shell-session
+> base64decode("SGVsbG8gV29ybGQ=")
+Hello World
+```
+
+## Related Functions
+
+- [`base64encode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64encode) performs the opposite operation,
+  encoding the UTF-8 bytes for a string as Base64.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
new file mode 100644
index 0000000000..cb20e8d17f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/base64encode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: base64encode - Functions - Configuration Language
+description: The base64encode function applies Base64 encoding to a string.
+---
+
+# `base64encode` Function
+
+`base64encode` applies Base64 encoding to a string.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+Strings in the Nomad language are sequences of unicode characters rather
+than bytes, so this function will first encode the characters from the string
+as UTF-8, and then apply Base64 encoding to the result.
+
+The Nomad language applies Unicode normalization to all strings, and so
+passing a string through `base64decode` and then `base64encode` may not yield
+the original result exactly.
+
+## Examples
+
+```shell-session
+> base64encode("Hello World")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+- [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) performs the opposite operation,
+  decoding Base64 data and interpreting it as a UTF-8 string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
new file mode 100644
index 0000000000..bea440f6f5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/csvdecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: csvdecode - Functions - Configuration Language
+description: The csvdecode function decodes CSV data into a list of maps.
+---
+
+# `csvdecode` Function
+
+`csvdecode` decodes a string containing CSV-formatted data and produces a
+list of maps representing that data.
+
+CSV is _Comma-separated Values_, an encoding format for tabular data. There
+are many variants of CSV, but this function implements the format defined
+in [RFC 4180](https://tools.ietf.org/html/rfc4180).
+
+The first line of the CSV data is interpreted as a "header" row: the values
+given are used as the keys in the resulting maps. Each subsequent line becomes
+a single map in the resulting list, matching the keys from the header row
+with the given values by index. All lines in the file must contain the same
+number of fields, or this function will produce an error.
+
+## Examples
+
+```shell-session
+> csvdecode("a,b,c\n1,2,3\n4,5,6")
+[
+  {
+    "a" = "1"
+    "b" = "2"
+    "c" = "3"
+  },
+  {
+    "a" = "4"
+    "b" = "5"
+    "c" = "6"
+  }
+]
+```
+
+<!---
+## TODO: revamp this section
+
+## Use with the `for_each` meta-argument
+
+You can use the result of `csvdecode` with
+[the `for_each` meta-argument](https://www.terraform.io/docs/configuration/resources.html#for_each-multiple-resource-instances-defined-by-a-map-or-set-of-strings)
+to describe a collection of similar objects whose differences are
+described by the rows in the given CSV file.
+
+There must be one column in the CSV file that can serve as a unique id for each
+row, which we can then use as the tracking key for the individual instances in
+the `for_each` expression. For example:
+
+```hcl
+locals {
+  # We've included this inline to create a complete example, but in practice
+  # this is more likely to be loaded from a file using the "file" function.
+  csv_data = <<-CSV
+    local_id,instance_type,ami
+    foo1,t2.micro,ami-54d2a63b
+    foo2,t2.micro,ami-54d2a63b
+    foo3,t2.micro,ami-54d2a63b
+    bar1,m3.large,ami-54d2a63b
+  CSV
+
+  instances = csvdecode(local.csv_data)
+}
+
+resource "aws_instance" "example" {
+  for_each = { for inst in local.instances : inst.local_id => inst }
+
+  instance_type = each.value.instance_type
+  ami           = each.value.ami
+}
+```
+
+The `for` expression in our `for_each` argument transforms the list produced
+by `csvdecode` into a map using the `local_id` as a key, which tells
+Packer to use the `local_id` value to track each instance it creates.
+Packer will create and manage the following instance addresses:
+
+- `aws_instance.example["foo1"]`
+- `aws_instance.example["foo2"]`
+- `aws_instance.example["foo3"]`
+- `aws_instance.example["bar1"]`
+
+If you modify a row in the CSV on a subsequent plan, Packer will interpret
+that as an update to the existing object as long as the `local_id` value is
+unchanged. If you add or remove rows from the CSV then Packer will plan to
+create or destroy associated instances as appropriate.
+
+If there is no reasonable value you can use as a unique identifier in your CSV
+then you could instead use
+[the `count` meta-argument](https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count)
+to define an object for each CSV row, with each one identified by its index into
+the list returned by `csvdecode`. However, in that case any future updates to
+the CSV may be disruptive if they change the positions of particular objects in
+the list. We recommend using `for_each` with a unique id column to make
+behavior more predictable on future changes.
+-->
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
new file mode 100644
index 0000000000..5cc18701f6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsondecode.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: jsondecode - Functions - Configuration Language
+description: |-
+  The jsondecode function decodes a JSON string into a representation of its
+  value.
+---
+
+# `jsondecode` Function
+
+`jsondecode` interprets a given string as JSON, returning a representation
+of the result of decoding that string.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps JSON values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| JSON type | Nomad type                                                   |
+| --------- | ------------------------------------------------------------ |
+| String    | `string`                                                     |
+| Number    | `number`                                                     |
+| Boolean   | `bool`                                                       |
+| Object    | `object(...)` with attribute types determined per this table |
+| Array     | `tuple(...)` with element types determined per this table    |
+| Null      | The Nomad language `null` value                              |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+## Examples
+
+```shell-session
+> jsondecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+> jsondecode("true")
+true
+```
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) performs the opposite operation, _encoding_
+  a value as JSON.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
new file mode 100644
index 0000000000..e603b4f57b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/jsonencode.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: jsonencode - Functions - Configuration Language
+description: The jsonencode function encodes a given value as a JSON string.
+---
+
+# `jsonencode` Function
+
+`jsonencode` encodes a given value to a string using JSON syntax.
+
+The JSON encoding is defined in [RFC 7159](https://tools.ietf.org/html/rfc7159).
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to JSON values in the following way:
+
+| Nomad type    | JSON type |
+| ------------- | --------- |
+| `string`      | String    |
+| `number`      | Number    |
+| `bool`        | Bool      |
+| `list(...)`   | Array     |
+| `set(...)`    | Array     |
+| `tuple(...)`  | Array     |
+| `map(...)`    | Object    |
+| `object(...)` | Object    |
+| Null value    | `null`    |
+
+Since the JSON format cannot fully represent all of the Nomad language
+types, passing the `jsonencode` result to `jsondecode` will not produce an
+identical value, but the automatic type conversion rules mean that this is
+rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> jsonencode({"hello"="world"})
+{"hello":"world"}
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) performs the opposite operation, _decoding_
+  a JSON string to obtain its represented value.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
new file mode 100644
index 0000000000..a1927956d8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/urlencode.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: urlencode - Functions - Configuration Language
+description: The urlencode function applies URL encoding to a given string.
+---
+
+# `urlencode` Function
+
+`urlencode` applies URL encoding to a given string.
+
+This function identifies characters in the given string that would have a
+special meaning when included as a query string argument in a URL and
+escapes them using
+[RFC 3986 "percent encoding"](https://tools.ietf.org/html/rfc3986#section-2.1).
+
+The exact set of characters escaped may change over time, but the result
+is guaranteed to be interpolatable into a query string argument without
+inadvertently introducing additional delimiters.
+
+If the given string contains non-ASCII characters, these are first encoded as
+UTF-8 and then percent encoding is applied separately to each UTF-8 byte.
+
+## Examples
+
+```shell-session
+> urlencode("Hello World")
+Hello%20World
+> urlencode("☃")
+%E2%98%83
+> "http://example.com/search?q=${urlencode("nomad urlencode")}"
+http://example.com/search?q=nomad%20urlencode
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
new file mode 100644
index 0000000000..66e588eddc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamldecode.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: yamldecode - Functions - Configuration Language
+description: |-
+  The yamldecode function decodes a YAML string into a representation of its
+  value.
+---
+
+# `yamldecode` Function
+
+`yamldecode` parses a string as a subset of YAML, and produces a representation
+of its value.
+
+This function supports a subset of [YAML 1.2](https://yaml.org/spec/1.2/spec.html),
+as described below.
+
+This function maps YAML values to
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+in the following way:
+
+| YAML type     | Nomad type                                                         |
+| ------------- | ------------------------------------------------------------------ |
+| `!!str`       | `string`                                                           |
+| `!!float`     | `number`                                                           |
+| `!!int`       | `number`                                                           |
+| `!!bool`      | `bool`                                                             |
+| `!!map`       | `object(...)` with attribute types determined per this table       |
+| `!!seq`       | `tuple(...)` with element types determined per this table          |
+| `!!null`      | The Nomad language `null` value                                    |
+| `!!timestamp` | `string` in [RFC 3339](https://tools.ietf.org/html/rfc3339) format |
+| `!!binary`    | `string` containing base64-encoded representation                  |
+
+The Nomad language automatic type conversion rules mean that you don't
+usually need to worry about exactly what type is produced for a given value,
+and can just use the result in an intuitive way.
+
+Note though that the mapping above is ambiguous -- several different source
+types map to the same target type -- and so round-tripping through `yamldecode`
+and then `yamlencode` cannot produce an identical result.
+
+YAML is a complex language and it supports a number of possibilities that the
+Nomad language's type system cannot represent. Therefore this YAML decoder
+supports only a subset of YAML 1.2, with restrictions including the following:
+
+- Although aliases to earlier anchors are supported, cyclic data structures
+  (where a reference to a collection appears inside that collection) are not.
+  If `yamldecode` detects such a structure then it will return an error.
+
+- Only the type tags shown in the above table (or equivalent alternative
+  representations of those same tags) are supported. Any other tags will
+  result in an error.
+
+- Only one YAML document is permitted. If multiple documents are present in
+  the given string then this function will return an error.
+
+## Examples
+
+```shell-session
+> yamldecode("{\"hello\": \"world\"}")
+{
+  "hello" = "world"
+}
+
+> yamldecode("true")
+true
+
+> yamldecode("{a: &foo [1, 2, 3], b: *foo}")
+{
+  "a" = [
+    1,
+    2,
+    3,
+  ]
+  "b" = [
+    1,
+    2,
+    3,
+  ]
+}
+
+> yamldecode("{a: &foo [1, *foo, 3]}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: cannot refer to anchor "foo" from inside
+its own definition.
+
+> yamldecode("{a: !not-supported foo}")
+
+Error: Error in function call
+
+Call to function "yamldecode" failed: unsupported tag "!not-supported".
+```
+
+## Related Functions
+
+- [`jsondecode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsondecode) is a similar operation using JSON instead
+  of YAML.
+- [`yamlencode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamlencode) performs the opposite operation, _encoding_
+  a value as YAML.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
new file mode 100644
index 0000000000..3fceecfd01
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/encoding/yamlencode.mdx
@@ -0,0 +1,86 @@
+---
+layout: docs
+page_title: yamlencode - Functions - Configuration Language
+description: The yamlencode function encodes a given value as a YAML string.
+---
+
+# `yamlencode` Function
+
+`yamlencode` encodes a given value to a string using
+[YAML 1.2](https://yaml.org/spec/1.2/spec) block syntax.
+
+~> **Warning:** This function is currently **experimental** and its exact
+result format may change in future versions of Nomad, based on feedback.
+Do not use `yamldecode` to construct a value for any argument where
+changes to the result would be disruptive. To get a consistent string
+representation of a value use [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead; its
+results are also valid YAML because YAML is a JSON superset.
+
+<!--
+    The condition for removing the above warning is that the underlying
+    go-cty-yaml folder makes a stable release with a commitment to guarantee
+    that the representation of particular input will not change without a
+    major release. It is not making that commitment at the time of writing to
+    allow for responding to user feedback about its output format, since YAML
+    is a very flexible format and its initial decisions may prove to be
+    sub-optimal when generating YAML intended for specific external consumers.
+-->
+
+This function maps
+[Nomad language values](/nomad/docs/job-specification/hcl2/expressions#types-and-values)
+to YAML tags in the following way:
+
+| Nomad type    | YAML type            |
+| ------------- | -------------------- |
+| `string`      | `!!str`              |
+| `number`      | `!!float` or `!!int` |
+| `bool`        | `!!bool`             |
+| `list(...)`   | `!!seq`              |
+| `set(...)`    | `!!seq`              |
+| `tuple(...)`  | `!!seq`              |
+| `map(...)`    | `!!map`              |
+| `object(...)` | `!!map`              |
+| Null value    | `!!null`             |
+
+`yamlencode` uses the implied syntaxes for all of the above types, so it does
+not generate explicit YAML tags.
+
+Because the YAML format cannot fully represent all of the Nomad language
+types, passing the `yamlencode` result to `yamldecode` will not produce an
+identical value, but the Nomad language automatic type conversion rules
+mean that this is rarely a problem in practice.
+
+## Examples
+
+```shell-session
+> yamlencode({"a":"b", "c":"d"})
+"a": "b"
+"c": "d"
+
+> yamlencode({"foo":[1, 2, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- 2
+- 3
+
+> yamlencode({"foo":[1, {"a":"b","c":"d"}, 3], "bar": "baz"})
+"bar": "baz"
+"foo":
+- 1
+- "a": "b"
+  "c": "d"
+- 3
+```
+
+`yamlencode` always uses YAML's "block style" for mappings and sequences, unless
+the mapping or sequence is empty. To generate flow-style YAML, use
+[`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) instead: YAML flow-style is a superset
+of JSON syntax.
+
+## Related Functions
+
+- [`jsonencode`](/nomad/docs/job-specification/hcl2/functions/encoding/jsonencode) is a similar operation using JSON instead
+  of YAML.
+- [`yamldecode`](/nomad/docs/job-specification/hcl2/functions/encoding/yamldecode) performs the opposite operation, _decoding_
+  a YAML string to obtain its represented value.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
new file mode 100644
index 0000000000..b5353bc499
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/abspath.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: abspath - Functions - Configuration Language
+description: The abspath function converts the argument to an absolute filesystem path.
+---
+
+# `abspath` Function
+
+`abspath` takes a string containing a filesystem path and converts it
+to an absolute path. That is, if the path is not absolute, it will be joined
+with the job file directory.
+
+Referring directly to filesystem paths in job arguments may cause spurious
+diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only for
+transient values, such as the argument to
+[`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where only the contents are then
+stored).
+
+## Examples
+
+```shell-session
+> abspath("nomad.txt")
+/home/user/some/nomad-job/nomad.txt
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/basename.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
new file mode 100644
index 0000000000..6c3d519d1c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/basename.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: basename - Functions - Configuration Language
+description: |-
+  The basename function removes all except the last portion from a filesystem
+  path.
+---
+
+# `basename` Function
+
+`basename` takes a string containing a filesystem path and removes all except
+the last portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> basename("foo/bar/baz.txt")
+baz.txt
+```
+
+## Related Functions
+
+- [`dirname`](/nomad/docs/job-specification/hcl2/functions/file/dirname) returns all of the segments of a filesystem path
+  _except_ the last, discarding the portion that would be returned by
+  `basename`.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
new file mode 100644
index 0000000000..8cdbebf5d5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/dirname.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: dirname - Functions - Configuration Language
+description: The dirname function removes the last portion from a filesystem path.
+---
+
+# `dirname` Function
+
+`dirname` takes a string containing a filesystem path and removes the last
+portion from it.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the path is empty then the result is `"."`, representing the job file directory.
+
+The behavior of this function depends on the host platform. On Windows systems,
+it uses backslash `\` as the path segment separator. On Unix systems, the slash
+`/` is used. The result of this function is normalized, so on a Windows system
+any slashes in the given path will be replaced by backslashes before returning.
+
+Referring directly to filesystem paths in job arguments may cause
+spurious diffs if the same configuration is applied from multiple systems or on
+different host operating systems. We recommend using filesystem paths only
+for transient values, such as the argument to [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) (where
+only the contents are then stored).
+
+## Examples
+
+```shell-session
+> dirname("foo/bar/baz.txt")
+foo/bar
+```
+
+## Related Functions
+
+- [`basename`](/nomad/docs/job-specification/hcl2/functions/file/basename) returns _only_ the last portion of a filesystem
+  path, discarding the portion that would be returned by `dirname`.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/file.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/file.mdx
new file mode 100644
index 0000000000..6d1c07d360
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/file.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: file - Functions - Configuration Language
+description: |-
+  The file function reads the contents of the file at the given path and
+  returns them as a string.
+---
+
+# `file` Function
+
+`file` reads the contents of a file at the given path and returns them as
+a string. Relative paths will be resolved based on the CLI’s current working directory.
+
+```hcl
+file(path)
+```
+
+Strings in the Nomad language are sequences of Unicode characters, so
+this function will interpret the file contents as UTF-8 encoded text and
+return the resulting Unicode characters. If the file contains invalid UTF-8
+sequences then this function will produce an error.
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> file("./hello.txt")
+Hello World
+```
+
+Or in an example job specification:
+
+```hcl
+# /path/to/example/jobspec.nomad
+job "test" {
+  group "test" {
+    task "test" {
+      driver = "docker"
+      config {
+        image  = "test/image:latest"
+
+        volumes = [
+          "local/file.txt:/path/to/file/on/container/file.txt"
+        ]
+      }
+
+      template {
+        data        = file("/path/to/example/file.txt")
+        destination = "local/file.txt"
+      }
+    }
+  }
+}
+```
+
+## Related Functions
+
+- [`fileexists`](/nomad/docs/job-specification/hcl2/functions/file/fileexists) determines whether a file exists
+  at a given path.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
new file mode 100644
index 0000000000..fd6693812f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/filebase64.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: filebase64 - Functions - Configuration Language
+description: |-
+  The filebase64 function reads the contents of the file at the given path and
+  returns them as a base64-encoded string.
+---
+
+# `filebase64` Function
+
+`filebase64` reads the contents of a file at the given path and returns them as
+a base64-encoded string.
+
+```hcl
+filebase64(path)
+```
+
+The result is a Base64 representation of the raw bytes in the given file.
+
+Nomad uses the "standard" Base64 alphabet as defined in
+[RFC 4648 section 4](https://tools.ietf.org/html/rfc4648#section-4).
+
+## Examples
+
+```
+> filebase64("${path.module}/hello.txt")
+SGVsbG8gV29ybGQ=
+```
+
+## Related Functions
+
+* [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) also reads the contents of a given file,
+  but interprets the data as UTF-8 text and returns the result directly
+  as a string, without any further encoding.
+* [`base64decode`](/nomad/docs/job-specification/hcl2/functions/encoding/base64decode) can decode a
+  Base64 string representing bytes in UTF-8, but in practice `base64decode(filebase64(...))`
+  is equivalent to the shorter expression `file(...)`.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
new file mode 100644
index 0000000000..3fcc542532
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileexists.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: fileexists - Functions - Configuration Language
+description: The fileexists function determines whether a file exists at a given path.
+---
+
+# `fileexists` Function
+
+`fileexists` determines whether a file exists at a given path.
+
+```hcl
+fileexists(path)
+```
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+This function works only with regular files. If used with a directory, FIFO,
+or other special mode, it will return an error.
+
+## Examples
+
+```shell-session
+> fileexists("./hello.txt")
+true
+```
+
+```hcl
+fileexists("custom-section.sh") ? file("custom-section.sh") : local.default_content
+```
+
+## Related Functions
+
+- [`file`](/nomad/docs/job-specification/hcl2/functions/file/file) reads the contents of a file at a given path
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
new file mode 100644
index 0000000000..a9550b4130
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/fileset.mdx
@@ -0,0 +1,81 @@
+---
+layout: docs
+page_title: fileset - Functions - Configuration Language
+description: The fileset function enumerates a set of regular file names given a pattern.
+---
+
+# `fileset` Function
+
+`fileset` enumerates a set of regular file names given a path and pattern.
+The path is automatically removed from the resulting set of file names and any
+result still containing path separators always returns forward slash (`/`) as
+the path separator for cross-system compatibility.
+
+```hcl
+fileset(path, pattern)
+```
+
+Supported pattern matches:
+
+- `*` - matches any sequence of non-separator characters
+- `**` - matches any sequence of characters, including separator characters
+- `?` - matches any single non-separator character
+- `{alternative1,...}` - matches a sequence of characters if one of the comma-separated alternatives matches
+- `[CLASS]` - matches any single non-separator character inside a class of characters (see below)
+- `[^CLASS]` - matches any single non-separator character outside a class of characters (see below)
+
+Character classes support the following:
+
+- `[abc]` - matches any single character within the set
+- `[a-z]` - matches any single character within the range
+
+Functions are evaluated by the CLI during configuration parsing rather than job run time,
+so this function can only be used with files that are already present on disk on operator host.
+
+## Examples
+
+```shell-session
+> tree pkr-consul
+pkr-consul
+├── build-linux.pkr.hcl
+└── linux
+    ├── files
+    │   ├── hello.txt
+    │   └── world.txt
+    └── scripts
+        ├── script-1-install.sh
+        └── script-2-setup.sh
+
+3 directories, 5 files
+
+> fileset(".", "*")
+[
+  "build-linux.pkr.hcl",
+]
+
+> echo 'fileset(".", "linux/scripts/*")'
+[
+  "linux/scripts/script-1-install.sh",
+  "linux/scripts/script-2-setup.sh",
+]
+
+> echo 'fileset("linux", "files/{hello,world}.txt")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+]
+
+> echo 'fileset("./linux/files", "*")'
+[
+  "hello.txt",
+  "world.txt",
+]
+
+> echo 'fileset("./linux", "**")'
+[
+  "files/hello.txt",
+  "files/world.txt",
+  "scripts/script-1-install.sh",
+  "scripts/script-2-setup.sh",
+]
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
new file mode 100644
index 0000000000..f77f2b2ab8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/file/pathexpand.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: pathexpand - Functions - Configuration Language
+description: |-
+  The pathexpand function expands a leading ~ character to the current user's
+  home directory.
+---
+
+# `pathexpand` Function
+
+`pathexpand` takes a filesystem path that might begin with a `~` segment,
+and if so it replaces that segment with the current user's home directory
+path.
+
+This function works only with the path string and does not access the
+filesystem itself. It is therefore unable to take into account filesystem
+features such as symlinks.
+
+If the leading segment in the path is not `~` then the given path is returned
+unmodified.
+
+Using this function in job arguments will cause spurious diffs if the
+same configuration is run by multiple users with different home directory
+paths, or used on different host operating systems.
+
+The rules for determining the "home directory" for the current user vary
+depending on host operating system.
+
+**For Unix systems**, the following sources are consulted, in order of preference:
+
+- The `HOME` environment variable.
+- The result of running `getent passwd` followed by the Nomad process uid.
+- The result of running `cd && pwd` in `sh`.
+
+**For Windows systems**, there is not really the concept of a home directory
+in the same sense as on Unix, but the following sources are consulted in
+order of preference:
+
+- The `HOME` environment variable.
+- The `HOMEDRIVE` and `HOMEPATH` environment variables, if both are set.
+- The `USERPROFILE` environment variable.
+
+The exact rules employed for each operating system may change in future
+releases of Nomad.
+
+## Examples
+
+```shell-session
+> pathexpand("~/.ssh/id_rsa")
+/home/steve/.ssh/id_rsa
+> pathexpand("/etc/resolv.conf")
+/etc/resolv.conf
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/index.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/index.mdx
new file mode 100644
index 0000000000..df6f9a529c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/index.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: Functions - Configuration Language
+description: |-
+  The HCL language has a number of built-in functions that can be called
+  from within expressions to transform and combine values.
+---
+
+# Built-in Functions
+
+The HCL language includes a number of built-in functions that you can
+call from within expressions to transform and combine values. The general
+syntax for function calls is a function name followed by comma-separated
+arguments in parentheses:
+
+```hcl
+max(5, 12, 9)
+```
+
+HCL functions are executed on job submission and cannot be combined with client
+side interpolation.
+
+The HCL language does not support user-defined functions, and so only
+the functions built in to the language are available for use. The navigation
+for this section includes a list of all of the available built-in functions.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
new file mode 100644
index 0000000000..bca317df7c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrhost.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: cidrhost - Functions - Configuration Language
+description: |-
+  The cidrhost function calculates a full host IP address within a given
+  IP network address prefix.
+---
+
+# `cidrhost` Function
+
+`cidrhost` calculates a full host IP address for a given host number within
+a given IP network address prefix.
+
+```hcl
+cidrhost(prefix, hostnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`hostnum` is a whole number that can be represented as a binary integer with
+no more than the number of digits remaining in the address after the given
+prefix. For more details on how this function interprets CIDR prefixes and
+populates host numbers, see the worked example for
+[`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet).
+
+Conventionally host number zero is used to represent the address of the
+network itself and the host number that would fill all the host bits with
+binary 1 represents the network's broadcast address. These numbers should
+generally not be used to identify individual hosts except in unusual
+situations, such as point-to-point links.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrhost("10.12.127.0/20", 16)
+10.12.112.16
+> cidrhost("10.12.127.0/20", 268)
+10.12.113.12
+> cidrhost("fd00:fd12:3456:7890:00a2::/72", 34)
+fd00:fd12:3456:7890::22
+```
+
+## Related Functions
+
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a subnet address under a given
+  network address prefix.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
new file mode 100644
index 0000000000..1b1019998f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrnetmask.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: cidrnetmask - Functions - Configuration Language
+description: |-
+  The cidrnetmask function converts an IPv4 address prefix given in CIDR
+  notation into a subnet mask address.
+---
+
+# `cidrnetmask` Function
+
+`cidrnetmask` converts an IPv4 address prefix given in CIDR notation into
+a subnet mask address.
+
+```hcl
+cidrnetmask(prefix)
+```
+
+`prefix` must be given in IPv4 CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The result is a subnet address formatted in the conventional dotted-decimal
+IPv4 address syntax, as expected by some software.
+
+CIDR notation is the only valid notation for IPv6 addresses, so `cidrnetmask`
+produces an error if given an IPv6 address.
+
+## Examples
+
+```shell-session
+> cidrnetmask("172.16.0.0/12")
+255.240.0.0
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
new file mode 100644
index 0000000000..0b28a38b77
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnet.mdx
@@ -0,0 +1,167 @@
+---
+layout: docs
+page_title: cidrsubnet - Functions - Configuration Language
+description: |-
+  The cidrsubnet function calculates a subnet address within a given IP network
+  address prefix.
+---
+
+# `cidrsubnet` Function
+
+`cidrsubnet` calculates a subnet address within given IP network address prefix.
+
+```hcl
+cidrsubnet(prefix, newbits, netnum)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+`newbits` is the number of additional bits with which to extend the prefix.
+For example, if given a prefix ending in `/16` and a `newbits` value of
+`4`, the resulting subnet address will have length `/20`.
+
+`netnum` is a whole number that can be represented as a binary integer with
+no more than `newbits` binary digits, which will be used to populate the
+additional bits added to the prefix.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+Unlike the related function [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets), `cidrsubnet`
+allows you to give a specific network number to use. `cidrsubnets` can allocate
+multiple network addresses at once, but numbers them automatically starting
+with zero.
+
+## Examples
+
+```shell-session
+> cidrsubnet("172.16.0.0/12", 4, 2)
+172.18.0.0/16
+> cidrsubnet("10.1.2.0/24", 4, 15)
+10.1.2.240/28
+> cidrsubnet("fd00:fd12:3456:7890::/56", 16, 162)
+fd00:fd12:3456:7800:a200::/72
+```
+
+## Netmasks and Subnets
+
+Using `cidrsubnet` requires familiarity with some network addressing concepts.
+
+The most important idea is that an IP address (whether IPv4 or IPv6) is
+fundamentally constructed from binary digits, even though we conventionally
+represent it as either four decimal octets (for IPv4) or a sequence of 16-bit
+hexadecimal numbers (for IPv6).
+
+Taking our example above of `cidrsubnet("10.1.2.0/24", 4, 15)`, the function
+will first convert the given IP address string into an equivalent binary
+representation:
+
+```text
+      10 .        1 .        2 .        0
+00001010   00000001   00000010 | 00000000
+         network               |   host
+```
+
+The `/24` at the end of the prefix string specifies that the first 24
+bits -- or, the first three octets -- of the address identify the network
+while the remaining bits (32 - 24 = 8 bits in this case) identify hosts
+within the network.
+
+The CLI tool [`ipcalc`](https://gitlab.com/ipcalc/ipcalc) is useful for
+visualizing CIDR prefixes as binary numbers. We can confirm the conversion
+above by providing the same prefix string to `ipcalc`:
+
+```shell-session
+$ ipcalc 10.1.2.0/24
+Address:   10.1.2.0             00001010.00000001.00000010. 00000000
+Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
+Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
+=>
+Network:   10.1.2.0/24          00001010.00000001.00000010. 00000000
+HostMin:   10.1.2.1             00001010.00000001.00000010. 00000001
+HostMax:   10.1.2.254           00001010.00000001.00000010. 11111110
+Broadcast: 10.1.2.255           00001010.00000001.00000010. 11111111
+Hosts/Net: 254                   Class A, Private Internet
+```
+
+This gives us some additional information but also confirms (using a slightly
+different notation) the conversion from decimal to binary and shows the range
+of possible host addresses in this network.
+
+While [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) allows calculating single host IP addresses,
+`cidrsubnet` on the other hand creates a new network prefix _within_ the given
+network prefix. In other words, it creates a subnet.
+
+When we call `cidrsubnet` we also pass two additional arguments: `newbits` and
+`netnum`. `newbits` decides how much longer the resulting prefix will be in
+bits; in our example here we specified `4`, which means that the resulting
+subnet will have a prefix length of 24 + 4 = 28 bits. We can imagine these
+bits breaking down as follows:
+
+```text
+      10 .        1 .        2 .    ?        0
+00001010   00000001   00000010 |   XXXX | 0000
+         parent network        | netnum | host
+```
+
+Four of the eight bits that were originally the "host number" are now being
+repurposed as the subnet number. The network prefix no longer falls on an
+exact octet boundary, so in effect we are now splitting the last decimal number
+in the IP address into two parts, using half of it to represent the subnet
+number and the other half to represent the host number.
+
+The `netnum` argument then decides what number value to encode into those
+four new subnet bits. In our current example we passed `15`, which is
+represented in binary as `1111`, allowing us to fill in the `XXXX` segment
+in the above:
+
+```text
+      10 .        1 .        2 .    15       0
+00001010   00000001   00000010 |   1111 | 0000
+         parent network        | netnum | host
+```
+
+To convert this back into normal decimal notation we need to recombine the
+two portions of the final octet. Converting `11110000` from binary to decimal
+gives 240, which can then be combined with our new prefix length of 28 to
+produce the result `10.1.2.240/28`. Again we can pass this prefix string to
+`ipcalc` to visualize it:
+
+```shell-session
+$ ipcalc 10.1.2.240/28
+Address:   10.1.2.240           00001010.00000001.00000010.1111 0000
+Netmask:   255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
+Wildcard:  0.0.0.15             00000000.00000000.00000000.0000 1111
+=>
+Network:   10.1.2.240/28        00001010.00000001.00000010.1111 0000
+HostMin:   10.1.2.241           00001010.00000001.00000010.1111 0001
+HostMax:   10.1.2.254           00001010.00000001.00000010.1111 1110
+Broadcast: 10.1.2.255           00001010.00000001.00000010.1111 1111
+Hosts/Net: 14                    Class A, Private Internet
+```
+
+The new subnet has four bits available for host numbering, which means
+that there are 14 host addresses available for assignment once we subtract
+the network's own address and the broadcast address. You can thus use
+[`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) function to calculate those host addresses by
+providing it a value between 1 and 14:
+
+```shell-session
+> cidrhost("10.1.2.240/28", 1)
+10.1.2.241
+> cidrhost("10.1.2.240/28", 14)
+10.1.2.254
+```
+
+For more information on CIDR notation and subnetting, see
+[Classless Inter-domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnets`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnets) can allocate multiple consecutive
+  addresses under a prefix at once, numbering them automatically.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
new file mode 100644
index 0000000000..7075651f7f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/ipnet/cidrsubnets.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: cidrsubnets - Functions - Configuration Language
+description: |-
+  The cidrsubnets function calculates a sequence of consecutive IP address
+  ranges within a particular CIDR prefix.
+---
+
+# `cidrsubnets` Function
+
+`cidrsubnets` calculates a sequence of consecutive IP address ranges within
+a particular CIDR prefix.
+
+```hcl
+cidrsubnets(prefix, newbits...)
+```
+
+`prefix` must be given in CIDR notation, as defined in
+[RFC 4632 section 3.1](https://tools.ietf.org/html/rfc4632#section-3.1).
+
+The remaining arguments, indicated as `newbits` above, each specify the number
+of additional network prefix bits for one returned address range. The return
+value is therefore a list with one element per `newbits` argument, each
+a string containing an address range in CIDR notation.
+
+For more information on IP addressing concepts, see the documentation for the
+related function [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet). `cidrsubnet` calculates
+a single subnet address within a prefix while allowing you to specify its
+subnet number, while `cidrsubnets` can calculate many at once, potentially of
+different sizes, and assigns subnet numbers automatically.
+
+When using this function to partition an address space as part of a network
+address plan, you must not change any of the existing arguments once network
+addresses have been assigned to real infrastructure, or else later address
+assignments will be invalidated. However, you _can_ append new arguments to
+existing calls safely, as long as there is sufficient address space available.
+
+This function accepts both IPv6 and IPv4 prefixes, and the result always uses
+the same addressing scheme as the given prefix.
+
+## Examples
+
+```shell-session
+> cidrsubnets("10.1.0.0/16", 4, 4, 8, 4)
+[
+  "10.1.0.0/20",
+  "10.1.16.0/20",
+  "10.1.32.0/24",
+  "10.1.48.0/20",
+]
+
+> cidrsubnets("fd00:fd12:3456:7890::/56", 16, 16, 16, 32)
+[
+  "fd00:fd12:3456:7800::/72",
+  "fd00:fd12:3456:7800:100::/72",
+  "fd00:fd12:3456:7800:200::/72",
+  "fd00:fd12:3456:7800:300::/88",
+]
+```
+
+You can use nested `cidrsubnets` calls with
+[`for` expressions](/nomad/docs/job-specification/hcl2/expressions#for-expressions)
+to concisely allocate groups of network address blocks:
+
+```shell-session
+> [for cidr_block in cidrsubnets("10.0.0.0/8", 8, 8, 8, 8) : cidrsubnets(cidr_block, 4, 4)]
+[
+  [
+    "10.0.0.0/20",
+    "10.0.16.0/20",
+  ],
+  [
+    "10.1.0.0/20",
+    "10.1.16.0/20",
+  ],
+  [
+    "10.2.0.0/20",
+    "10.2.16.0/20",
+  ],
+  [
+    "10.3.0.0/20",
+    "10.3.16.0/20",
+  ],
+]
+```
+
+## Related Functions
+
+- [`cidrhost`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrhost) calculates the IP address for a single host
+  within a given network address prefix.
+- [`cidrnetmask`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrnetmask) converts an IPv4 network prefix in CIDR
+  notation into netmask notation.
+- [`cidrsubnet`](/nomad/docs/job-specification/hcl2/functions/ipnet/cidrsubnet) calculates a single subnet address, allowing
+  you to specify its network number.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
new file mode 100644
index 0000000000..d136984d2c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/abs.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: abs - Functions - Configuration Language
+description: The abs function returns the absolute value of the given number.
+---
+
+# `abs` Function
+
+`abs` returns the absolute value of the given number. In other words, if the
+number is zero or positive then it is returned as-is, but if it is negative
+then it is multiplied by -1 to make it positive before returning it.
+
+## Examples
+
+```shell-session
+> abs(23)
+23
+> abs(0)
+0
+> abs(-12.4)
+12.4
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
new file mode 100644
index 0000000000..a4f0b93776
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/ceil.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: ceil - Functions - Configuration Language
+description: |-
+  The ceil function returns the closest whole number greater than or equal to
+  the given value.
+---
+
+# `ceil` Function
+
+`ceil` returns the closest whole number that is greater than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> ceil(5)
+5
+> ceil(5.1)
+6
+```
+
+## Related Functions
+
+- [`floor`](/nomad/docs/job-specification/hcl2/functions/numeric/floor), which rounds to the nearest whole number _less than_
+  or equal.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
new file mode 100644
index 0000000000..8520b028a6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/floor.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: floor - Functions - Configuration Language
+description: |-
+  The floor function returns the closest whole number less than or equal to
+  the given value.
+---
+
+# `floor` Function
+
+`floor` returns the closest whole number that is less than or equal to the
+given value, which may be a fraction.
+
+## Examples
+
+```shell-session
+> floor(5)
+5
+> floor(4.9)
+4
+```
+
+## Related Functions
+
+- [`ceil`](/nomad/docs/job-specification/hcl2/functions/numeric/ceil), which rounds to the nearest whole number _greater than_
+  or equal.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
new file mode 100644
index 0000000000..09f84f1248
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/log.mdx
@@ -0,0 +1,34 @@
+---
+layout: docs
+page_title: log - Functions - Configuration Language
+description: The log function returns the logarithm of a given number in a given base.
+---
+
+# `log` Function
+
+`log` returns the logarithm of a given number in a given base.
+
+```hcl
+log(number, base)
+```
+
+## Examples
+
+```shell-session
+> log(50, 10)
+1.6989700043360185
+> log(16, 2)
+4
+```
+
+`log` and `ceil` can be used together to find the minimum number of binary
+digits required to represent a given number of distinct values:
+
+```shell-session
+> ceil(log(15, 2))
+4
+> ceil(log(16, 2))
+4
+> ceil(log(17, 2))
+5
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
new file mode 100644
index 0000000000..2e948b3a01
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/max.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: max - Functions - Configuration Language
+description: The max function takes one or more numbers and returns the greatest number.
+---
+
+# `max` Function
+
+`max` takes one or more numbers and returns the greatest number from the set.
+
+## Examples
+
+```shell-session
+> max(12, 54, 3)
+54
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> max([12, 54, 3]...)
+54
+```
+
+## Related Functions
+
+- [`min`](/nomad/docs/job-specification/hcl2/functions/numeric/min), which returns the _smallest_ number from a set.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
new file mode 100644
index 0000000000..fe04826e31
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/min.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: min - Functions - Configuration Language
+description: The min function takes one or more numbers and returns the smallest number.
+---
+
+# `min` Function
+
+`min` takes one or more numbers and returns the smallest number from the set.
+
+## Examples
+
+```shell-session
+> min(12, 54, 3)
+3
+```
+
+If the numbers are in a list or set value, use `...` to expand the collection
+to individual arguments:
+
+```shell-session
+> min([12, 54, 3]...)
+3
+```
+
+## Related Functions
+
+- [`max`](/nomad/docs/job-specification/hcl2/functions/numeric/max), which returns the _greatest_ number from a set.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
new file mode 100644
index 0000000000..6de1b00874
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/parseint.mdx
@@ -0,0 +1,51 @@
+---
+layout: docs
+page_title: parseint - Functions - Configuration Language
+description: >-
+  The parseint function parses the given string as a representation of an
+  integer.
+---
+
+# `parseint` Function
+
+`parseint` parses the given string as a representation of an integer in
+the specified base and returns the resulting number. The base must be between 2
+and 62 inclusive.
+
+All bases use the arabic numerals 0 through 9 first. Bases between 11 and 36
+inclusive use case-insensitive latin letters to represent higher unit values.
+Bases 37 and higher use lowercase latin letters and then uppercase latin
+letters.
+
+If the given string contains any non-digit characters or digit characters that
+are too large for the given base then `parseint` will produce an error.
+
+## Examples
+
+```shell-session
+> parseint("100", 10)
+100
+
+> parseint("FF", 16)
+255
+
+> parseint("-10", 16)
+-16
+
+> parseint("1011111011101111", 2)
+48879
+
+> parseint("aA", 62)
+656
+
+> parseint("12", 2)
+
+Error: Invalid function argument
+
+Invalid value for "number" parameter: cannot parse "12" as a base 2 integer.
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) can format numbers and other values into strings,
+  with optional zero padding, alignment, etc.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
new file mode 100644
index 0000000000..4e7685a992
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/pow.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: pow - Functions - Configuration Language
+description: The pow function raises a number to a power.
+---
+
+# `pow` Function
+
+`pow` calculates an exponent, by raising its first argument to the power of the second argument.
+
+## Examples
+
+```shell-session
+> pow(3, 2)
+9
+> pow(4, 0)
+1
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
new file mode 100644
index 0000000000..92f3e2d081
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/numeric/signum.mdx
@@ -0,0 +1,21 @@
+---
+layout: docs
+page_title: signum - Functions - Configuration Language
+description: The signum function determines the sign of a number.
+---
+
+# `signum` Function
+
+`signum` determines the sign of a number, returning a number between -1 and
+1 to represent the sign.
+
+## Examples
+
+```shell-session
+> signum(-13)
+-1
+> signum(0)
+0
+> signum(344)
+1
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
new file mode 100644
index 0000000000..4ee1a89730
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/chomp.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: chomp - Functions - Configuration Language
+description: The chomp function removes newline characters at the end of a string.
+---
+
+# `chomp` Function
+
+`chomp` removes newline characters at the end of a string.
+
+This can be useful if, for example, the string was read from a file that has
+a newline character at the end.
+
+## Examples
+
+```shell-session
+> chomp("hello\n")
+hello
+> chomp("hello\r\n")
+hello
+> chomp("hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace), which removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/format.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/format.mdx
new file mode 100644
index 0000000000..ddbd9a5677
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/format.mdx
@@ -0,0 +1,120 @@
+---
+layout: docs
+page_title: format - Functions - Configuration Language
+description: |-
+  The format function produces a string by formatting a number of other values
+  according to a specification string.
+---
+
+# `format` Function
+
+`format` produces a string by formatting a number of other values according
+to a specification string. It is similar to the `printf` function in C, and
+other similar functions in other programming languages.
+
+```hcl
+format(spec, values...)
+```
+
+## Examples
+
+```shell-session
+> format("Hello, %s!", "Ander")
+Hello, Ander!
+> format("There are %d lights", 4)
+There are 4 lights
+```
+
+Simple format verbs like `%s` and `%d` behave similarly to template
+interpolation syntax, which is often more readable:
+
+```shell-session
+> format("Hello, %s!", var.name)
+Hello, Valentina!
+> "Hello, ${var.name}!"
+Hello, Valentina!
+```
+
+The `format` function is therefore more useful when you use more complex format
+specifications, as described in the following section.
+
+## Specification Syntax
+
+The specification is a string that includes formatting verbs that are introduced
+with the `%` character. The function call must then have one additional argument
+for each verb sequence in the specification. The verbs are matched with
+consecutive arguments and formatted as directed, as long as each given argument
+is convertible to the type required by the format verb.
+
+The specification may contain the following verbs:
+
+| Verb  | Result                                                                                    |
+| ----- | ----------------------------------------------------------------------------------------- |
+| `%%`  | Literal percent sign, consuming no value.                                                 |
+| `%v`  | Default formatting based on the value type, as described below.                           |
+| `%#v` | JSON serialization of the value, as with `jsonencode`.                                    |
+| `%t`  | Convert to boolean and produce `true` or `false`.                                         |
+| `%b`  | Convert to integer number and produce binary representation.                              |
+| `%d`  | Convert to integer number and produce decimal representation.                             |
+| `%o`  | Convert to integer number and produce octal representation.                               |
+| `%x`  | Convert to integer number and produce hexadecimal representation with lowercase letters.  |
+| `%X`  | Like `%x`, but use uppercase letters.                                                     |
+| `%e`  | Convert to number and produce scientific notation, like `-1.234456e+78`.                  |
+| `%E`  | Like `%e`, but use an uppercase `E` to introduce the exponent.                            |
+| `%f`  | Convert to number and produce decimal fraction notation with no exponent, like `123.456`. |
+| `%g`  | Like `%e` for large exponents or like `%f` otherwise.                                     |
+| `%G`  | Like `%E` for large exponents or like `%f` otherwise.                                     |
+| `%s`  | Convert to string and insert the string's characters.                                     |
+| `%q`  | Convert to string and produce a JSON quoted string representation.                        |
+
+When `%v` is used, one of the following format verbs is chosen based on the value type:
+
+| Type      | Verb  |
+| --------- | ----- |
+| `string`  | `%s`  |
+| `number`  | `%g`  |
+| `bool`    | `%t`  |
+| any other | `%#v` |
+
+Null values produce the string `null` if formatted with `%v` or `%#v`, and
+cause an error for other verbs.
+
+A width modifier can be included with an optional decimal number immediately
+preceding the verb letter, to specify how many characters will be used to
+represent the value. Precision can be specified after the (optional) width
+with a period (`.`) followed by a decimal number. If width or precision are
+omitted then default values are selected based on the given value. For example:
+
+| Sequence | Result                       |
+| -------- | ---------------------------- |
+| `%f`     | Default width and precision. |
+| `%9f`    | Width 9, default precision.  |
+| `%.2f`   | Default width, precision 2.  |
+| `%9.2f`  | Width 9, precision 2.        |
+
+The following additional symbols can be used immediately after the `%` symbol
+to set additoinal flags:
+
+| Symbol | Result                                                         |
+| ------ | -------------------------------------------------------------- |
+| space  | Leave a space where the sign would be if a number is positive. |
+| `+`    | Show the sign of a number even if it is positive.              |
+| `-`    | Pad the width with spaces on the left rather than the right.   |
+| `0`    | Pad the width with leading zeros rather than spaces.           |
+
+By default, `%` sequences consume successive arguments starting with the first.
+Introducing a `[n]` sequence immediately before the verb letter, where `n` is a
+decimal integer, explicitly chooses a particular value argument by its
+one-based index. Subsequent calls without an explicit index will then proceed
+with `n`+1, `n`+2, etc.
+
+The function produces an error if the format string requests an impossible
+conversion or access more arguments than are given. An error is produced also
+for an unsupported format verb.
+
+## Related Functions
+
+- [`formatdate`](/nomad/docs/job-specification/hcl2/functions/datetime/formatdate) is a specialized formatting function for
+  human-readable timestamps.
+- [`formatlist`](/nomad/docs/job-specification/hcl2/functions/string/formatlist) uses the same specification syntax to
+  produce a list of strings.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
new file mode 100644
index 0000000000..8c17fcd470
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/formatlist.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: formatlist - Functions - Configuration Language
+description: |-
+  The formatlist function produces a list of strings by formatting a number of
+  other values according to a specification string.
+---
+
+# `formatlist` Function
+
+`formatlist` produces a list of strings by formatting a number of other
+values according to a specification string.
+
+```hcl
+formatlist(spec, values...)
+```
+
+The specification string uses
+[the same syntax as `format`](/nomad/docs/job-specification/hcl2/functions/string/format#specification-syntax).
+
+The given values can be a mixture of list and non-list arguments. Any given
+lists must be the same length, which decides the length of the resulting list.
+
+The list arguments are iterated together in order by index, while the non-list
+arguments are used repeatedly for each iteration. The format string is evaluated
+once per element of the list arguments.
+
+## Examples
+
+```shell-session
+> formatlist("Hello, %s!", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Hello, Valentina!",
+  "Hello, Ander!",
+  "Hello, Olivia!",
+  "Hello, Sam!",
+]
+> formatlist("%s, %s!", "Salutations", ["Valentina", "Ander", "Olivia", "Sam"])
+[
+  "Salutations, Valentina!",
+  "Salutations, Ander!",
+  "Salutations, Olivia!",
+  "Salutations, Sam!",
+]
+```
+
+## Related Functions
+
+- [`format`](/nomad/docs/job-specification/hcl2/functions/string/format) defines the specification syntax used by this
+  function and produces a single string as its result.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/indent.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
new file mode 100644
index 0000000000..9caf9f5751
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/indent.mdx
@@ -0,0 +1,32 @@
+---
+layout: docs
+page_title: indent - Functions - Configuration Language
+description: |-
+  The indent function adds a number of spaces to the beginnings of all but the
+  first line of a given multi-line string.
+---
+
+# `indent` Function
+
+`indent` adds a given number of spaces to the beginnings of all but the first
+line in a given multi-line string.
+
+```hcl
+indent(num_spaces, string)
+```
+
+## Examples
+
+This function is useful for inserting a multi-line string into an
+already-indented context in another string:
+
+```shell-session
+> "  items: %{indent(2, "[\n  foo,\n  bar,\n]\n")}"
+  items: [
+    foo,
+    bar,
+  ]
+```
+
+The first line of the string is not indented so that, as above, it can be
+placed after an introduction sequence that has already begun the line.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/join.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/join.mdx
new file mode 100644
index 0000000000..00768a500f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/join.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: join - Functions - Configuration Language
+description: |-
+  The join function produces a string by concatenating the elements of a list
+  with a given delimiter.
+---
+
+# `join` Function
+
+`join` produces a string by concatenating together all elements of a given
+list of strings with the given delimiter.
+
+```hcl
+join(separator, list)
+```
+
+## Examples
+
+```shell-session
+> join(", ", ["foo", "bar", "baz"])
+foo, bar, baz
+> join(", ", ["foo"])
+foo
+```
+
+## Related Functions
+
+- [`split`](/nomad/docs/job-specification/hcl2/functions/string/split) performs the opposite operation: producing a list
+  by separating a single string using a given delimiter.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/lower.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
new file mode 100644
index 0000000000..26137e99dc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/lower.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: lower - Functions - Configuration Language
+description: >-
+  The lower function converts all cased letters in the given string to
+  lowercase.
+---
+
+# `lower` Function
+
+`lower` converts all cased letters in the given string to lowercase.
+
+## Examples
+
+```shell-session
+> lower("HELLO")
+hello
+> lower("АЛЛО!")
+алло!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts letters in a string to _uppercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
new file mode 100644
index 0000000000..92974372a7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/regex_replace.mdx
@@ -0,0 +1,45 @@
+---
+layout: docs
+page_title: regex_replace - Functions - Configuration Language
+description: |-
+  The regex_replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string. The substring
+  argument can be a valid regular expression or a string.
+---
+
+# `regex_replace` Function
+
+`regex_replace` searches a given string for another given substring, and
+replaces each occurrence with a given replacement string. The substring
+argument can be a valid regular expression or a string.
+
+```hcl
+regex_replace(string, substring, replacement)
+```
+
+`substring` should not be wrapped in forward slashes, it is always treated as a
+regular expression. The `replacement` string can incorporate captured strings
+from the input by using an `$n` or `${n}` sequence, where `n` is the index or
+name of a capture group.
+
+## Examples
+
+```shell-session
+> regex_replace("hello world", "world", "everybody")
+hello everybody
+
+
+> regex_replace("hello world", "w.*d", "everybody")
+hello everybody
+
+> regex_replace("-ab-axxb-", "a(x*)b", "$1W")
+---
+
+> regex_replace("-ab-axxb-", "a(x*)b", "${1}W")
+-W-xxW-
+```
+
+## Related Functions
+
+- [`replace`](/nomad/docs/job-specification/hcl2/functions/string/replace) searches a given string for another given
+  substring, and replaces all occurrences with a given replacement string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/replace.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
new file mode 100644
index 0000000000..f927dafa43
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/replace.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: replace - Functions - Configuration Language
+description: |-
+  The replace function searches a given string for another given substring,
+  and replaces all occurrences with a given replacement string.
+---
+
+# `replace` Function
+
+`replace` searches a given string for another given substring, and replaces
+each occurrence with a given replacement string.
+
+```hcl
+replace(string, substring, replacement)
+```
+
+## Examples
+
+```shell-session
+> replace("1 + 2 + 3", "+", "-")
+1 - 2 - 3
+
+> replace("hello world", "world", "everybody")
+hello everybody
+```
+
+## Related Functions
+
+- [`regex_replace`](/nomad/docs/job-specification/hcl2/functions/string/regex_replace) searches a given string for another given substring,
+  and replaces each occurrence with a given replacement string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/split.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/split.mdx
new file mode 100644
index 0000000000..e5ec4e1b6c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/split.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: split - Functions - Configuration Language
+description: |-
+  The split function produces a list by dividing a given string at all
+  occurrences of a given separator.
+---
+
+# `split` Function
+
+`split` produces a list by dividing a given string at all occurrences of a
+given separator.
+
+```hcl
+split(separator, string)
+```
+
+## Examples
+
+```shell-session
+> split(",", "foo,bar,baz")
+[
+  "foo",
+  "bar",
+  "baz",
+]
+> split(",", "foo")
+[
+  "foo",
+]
+> split(",", "")
+[
+  "",
+]
+```
+
+## Related Functions
+
+- [`join`](/nomad/docs/job-specification/hcl2/functions/string/join) performs the opposite operation: producing a string
+  joining together a list of strings with a given separator.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
new file mode 100644
index 0000000000..c08c871d46
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strlen.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: strlen - Functions - Configuration Language
+description: The strlen function determines the length of a string.
+---
+
+# `strlen` Function
+
+`strlen` determines the length of a given string.
+
+```hcl
+strlen(string)
+```
+
+## Examples
+
+```shell-session
+> length("hello")
+5
+```
+
+When given a string, the result is the number of characters, rather than the
+number of bytes or Unicode sequences that form them:
+
+```shell-session
+> length("👾🕹️")
+2
+```
+
+A "character" is a _grapheme cluster_, as defined by
+[Unicode Standard Annex #29](http://unicode.org/reports/tr29/). Note that
+remote APIs may have a different definition of "character" for the purpose of
+length limits on string arguments; a Nomad provider is responsible for
+translating Nomad's string representation into that used by its respective
+remote system and applying any additional validation rules to it.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
new file mode 100644
index 0000000000..84c51012b3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/strrev.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: strrev - Functions - Configuration Language
+description: The strrev function reverses a string.
+---
+
+# `strrev` Function
+
+`strrev` reverses the characters in a string.
+Note that the characters are treated as _Unicode characters_ (in technical terms, Unicode [grapheme cluster boundaries](https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries) are respected).
+
+```hcl
+strrev(string)
+```
+
+## Examples
+
+```shell-session
+> strrev("hello")
+olleh
+> strrev("a ☃")
+☃ a
+```
+
+## Related Functions
+
+- [`reverse`](/nomad/docs/job-specification/hcl2/functions/collection/reverse) reverses a sequence.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/substr.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
new file mode 100644
index 0000000000..208e178d00
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/substr.mdx
@@ -0,0 +1,30 @@
+---
+layout: docs
+page_title: substr - Functions - Configuration Language
+description: |-
+  The substr function extracts a substring from a given string by offset and
+  length.
+---
+
+# `substr` Function
+
+`substr` extracts a substring from a given string by offset and length.
+
+```hcl
+substr(string, offset, length)
+```
+
+## Examples
+
+```shell-session
+> substr("hello world", 1, 4)
+ello
+```
+
+The offset and length are both counted in _unicode characters_ rather than
+bytes:
+
+```shell-session
+> substr("🤔🤷", 0, 1)
+🤔
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/title.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/title.mdx
new file mode 100644
index 0000000000..96f8165a81
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/title.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: title - Functions - Configuration Language
+description: |-
+  The title function converts the first letter of each word in a given string
+  to uppercase.
+---
+
+# `title` Function
+
+`title` converts the first letter of each word in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> title("hello world")
+Hello World
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`upper`](/nomad/docs/job-specification/hcl2/functions/string/upper) converts _all_ letters in a string to uppercase.
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts all letters in a string to lowercase.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trim.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
new file mode 100644
index 0000000000..f5b8741c7e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trim.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: trim - Functions - Configuration Language
+description: |-
+  The trim function removes the specified characters from the start and end of
+  a given string.
+---
+
+# `trim` Function
+
+`trim` removes the specified characters from the start and end of the given
+string.
+
+## Examples
+
+```shell-session
+> trim("?!hello?!", "!?")
+hello
+```
+
+## Related Functions
+
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
new file mode 100644
index 0000000000..c879e62f21
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimprefix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimprefix - Functions - Configuration Language
+description: |-
+  The trimprefix function removes the specified prefix from the start of a
+  given string.
+---
+
+# `trimprefix` Function
+
+`trimprefix` removes the specified prefix from the start of the given string.
+
+## Examples
+
+```shell-session
+> trimprefix("helloworld", "hello")
+world
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimsuffix`](/nomad/docs/job-specification/hcl2/functions/string/trimsuffix) removes a word from the end of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
new file mode 100644
index 0000000000..1d46d65124
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimspace.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: trimspace - Functions - Configuration Language
+description: |-
+  The trimspace function removes space characters from the start and end of
+  a given string.
+---
+
+# `trimspace` Function
+
+`trimspace` removes any space characters from the start and end of the given
+string.
+
+This function follows the Unicode definition of "space", which includes
+regular spaces, tabs, newline characters, and various other space-like
+characters.
+
+## Examples
+
+```shell-session
+> trimspace("  hello\n\n")
+hello
+```
+
+## Related Functions
+
+- [`chomp`](/nomad/docs/job-specification/hcl2/functions/string/chomp) removes just line ending characters from the _end_ of
+  a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
new file mode 100644
index 0000000000..f17f38d335
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/trimsuffix.mdx
@@ -0,0 +1,25 @@
+---
+layout: docs
+page_title: trimsuffix - Functions - Configuration Language
+description: |-
+  The trimsuffix function removes the specified suffix from the end of a
+  given string.
+---
+
+# `trimsuffix` Function
+
+`trimsuffix` removes the specified suffix from the end of the given string.
+
+## Examples
+
+```shell-session
+> trimsuffix("helloworld", "world")
+hello
+```
+
+## Related Functions
+
+- [`trim`](/nomad/docs/job-specification/hcl2/functions/string/trim) removes characters at the start and end of a string.
+- [`trimprefix`](/nomad/docs/job-specification/hcl2/functions/string/trimprefix) removes a word from the start of a string.
+- [`trimspace`](/nomad/docs/job-specification/hcl2/functions/string/trimspace) removes all types of whitespace from
+  both the start and the end of a string.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/upper.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
new file mode 100644
index 0000000000..b6a46bd340
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/string/upper.mdx
@@ -0,0 +1,27 @@
+---
+layout: docs
+page_title: upper - Functions - Configuration Language
+description: >-
+  The upper function converts all cased letters in the given string to
+  uppercase.
+---
+
+# `upper` Function
+
+`upper` converts all cased letters in the given string to uppercase.
+
+## Examples
+
+```shell-session
+> upper("hello")
+HELLO
+> upper("алло!")
+АЛЛО!
+```
+
+This function uses Unicode's definition of letters and of upper- and lowercase.
+
+## Related Functions
+
+- [`lower`](/nomad/docs/job-specification/hcl2/functions/string/lower) converts letters in a string to _lowercase_.
+- [`title`](/nomad/docs/job-specification/hcl2/functions/string/title) converts the first letter of each word in a string to uppercase.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
new file mode 100644
index 0000000000..4b546624a2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv4.mdx
@@ -0,0 +1,28 @@
+---
+layout: docs
+page_title: v4 - uuid - Functions - Configuration Language
+description: The uuidv4 function generates a unique id.
+---
+
+# `uuidv4` Function
+
+`uuidv4` generates a unique identifier string.
+
+The id is a generated and formatted as required by [RFC 4122 section
+4.4](https://tools.ietf.org/html/rfc4122#section-4.4), producing a Version 4
+UUID. The result is a UUID generated only from pseudo-random numbers.
+
+This function produces a new value each time it is called, and so using it
+directly in job arguments will result in spurious diffs. We do not
+recommend using the `uuidv4` function in resource configurations.
+
+## Examples
+
+```shell-session
+> uuidv4()
+b5ee72a3-54dd-c4b8-551c-4bdc0204cedb
+```
+
+## Related Functions
+
+- [`uuidv5`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv5), which generates name-based UUIDs.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
new file mode 100644
index 0000000000..2e92de5824
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/functions/uuid/uuidv5.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: uuidv5 - Functions - Configuration Language
+description: |-
+  The uuidv5 function generates a uuid v5 string representation of the value in
+  the specified namespace.
+---
+
+# `uuidv5` Function
+
+`uuidv5` generates a _name-based_ UUID, as described in [RFC 4122 section
+4.3](https://tools.ietf.org/html/rfc4122#section-4.3), also known as a "version
+5" UUID.
+
+```hcl
+uuidv5(namespace, name)
+```
+
+Unlike the pseudo-random UUIDs generated by [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4),
+name-based UUIDs derive from namespace and an name, producing the same UUID
+value every time if the namespace and name are unchanged.
+
+Name-based UUID namespaces are themselves UUIDs, but for readability this
+function accepts some keywords as aliases for the namespaces that were assigned
+by RFC 4122:
+
+| Keyword  | Namespace ID                           | Name format                                                                  |
+| -------- | -------------------------------------- | ---------------------------------------------------------------------------- |
+| `"dns"`  | `6ba7b810-9dad-11d1-80b4-00c04fd430c8` | A fully-qualified DNS domain name.                                           |
+| `"url"`  | `6ba7b811-9dad-11d1-80b4-00c04fd430c8` | Any valid URL as defined in [RFC 3986](https://tools.ietf.org/html/rfc3986). |
+| `"oid"`  | `6ba7b812-9dad-11d1-80b4-00c04fd430c8` | An [ISO/IEC object identifier](https://oidref.com/)                          |
+| `"x500"` | `6ba7b814-9dad-11d1-80b4-00c04fd430c8` | [X.500 Distinguished Name](https://tools.ietf.org/html/rfc1779)              |
+
+To use any other namespace not included in the above table, pass its assigned
+namespace ID directly in the first argument in the usual UUID string format.
+
+## Examples
+
+Use the namespace keywords where possible, to make the intent more obvious to
+a future reader:
+
+```shell-session
+> uuidv5("dns", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+
+> uuidv5("url", "https://developer.hashicorp.com/nomad/")
+a1572394-3948-5251-b0c7-b4ded43587b4
+
+> uuidv5("oid", "1.3.6.1.4")
+af9d40a5-7a36-5c07-b23a-851cd99fbfa5
+
+> uuidv5("x500", "CN=Example,C=GB")
+84e09961-4aa4-57f8-95b7-03edb1073253
+```
+
+The namespace keywords treated as equivalent to their corresponding namespace
+UUIDs, and in some special cases it may be more appropriate to use the
+UUID form:
+
+```shell-session
+> uuidv5("6ba7b810-9dad-11d1-80b4-00c04fd430c8", "developer.hashicorp.com/nomad")
+d2616d48-e1cb-5b87-8a8c-46355decc76a
+```
+
+If you wish to use a namespace defined outside of RFC 4122, using the namespace
+UUID is required because no corresponding keyword is available:
+
+```shell-session
+> uuidv5("743ac3c0-3bf7-4a5b-9e6c-59360447c757", "LIBS:diskfont.library")
+ede1a974-df7e-5f17-84b9-76208818b2c8
+```
+
+When using raw UUID namespaces, consider including a comment alongside the
+expression that indicates which namespace this represents in a
+human-significant manner, such as by reference to the standard that defined it.
+
+## Related Functions
+
+- [`uuidv4`](/nomad/docs/job-specification/hcl2/functions/uuid/uuidv4), which generates pseudorandom UUIDs.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/index.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/index.mdx
new file mode 100644
index 0000000000..d8c8119202
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/index.mdx
@@ -0,0 +1,172 @@
+---
+layout: docs
+page_title: Configuration Language
+description: |-
+  Noamd uses text files to describe infrastructure and to set variables.
+  These text files are called Nomad job specifications and are
+  written in the HCL language.
+---
+
+# HCL2
+
+Nomad uses the Hashicorp Configuration Language - HCL - designed to allow
+concise descriptions of the required steps to get to a job file.
+Nomad 1.0 adopts
+[HCL2](https://github.com/hashicorp/hcl/blob/hcl2/README.md), the second
+generation of HashiCorp Configuration Language. HCL2 extends the HCL language by
+adding expressions and input variables support to improve job spec
+reusability and readability. Also, the new HCL2 parser improves the error
+messages for invalid jobs.
+
+## HCL Parsing Context
+
+The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
+When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
+parses HCL and ultimately converts it to JSON. Because this parsing happens locally
+(i.e., where the operator is running the CLI) before job submission, there are some
+limits to the capabilities that can be accessed by HCL job specifications. For
+example, scheduling information is not yet available, including information about
+the client. Similarly, HCL features that depend on external context will take that
+context from the local environment of the CLI (e.g., files, environment variables).
+
+[jobs-api]: /nomad/api-docs/jobs
+
+## JSON Jobs
+
+Since HCL is a superset of JSON, `nomad job run example.json` will attempt to
+parse a JSON job using the HCL parser. However, the JSON format accepted by
+the HCL parser is not the same as the [API's JSON format][json-jobs-api]. The
+HCL parser's JSON format is unspecified, so the API format is preferred. You can
+use the API format with the [`-json` command line flag][run-json]:
+
+```shell-session
+$ # Generate an HCL formatted job
+$ nomad init
+
+$ # Convert HCL to API JSON format
+$ nomad job run -output example.nomad.hcl > example.json
+
+$ # Submit with the -json flag
+$ nomad job run -json example.json
+```
+
+
+[json-jobs-api]: /nomad/api-docs/json-jobs
+[run-json]: /nomad/docs/commands/job/run#json
+
+## Arguments, Blocks, and Expressions
+
+The syntax of the HCL language consists of only a few basic elements:
+
+```hcl
+task "example" {
+  driver = "docker"
+}
+
+<BLOCK TYPE> "<BLOCK LABEL>" {
+  # Block body
+  <IDENTIFIER> = <EXPRESSION> # Argument
+}
+```
+
+- _Blocks_ are containers for other content and usually represent the
+  configuration of some kind of object, like a task. Blocks have a
+  _block type,_ can have zero or more _labels,_ and have a _body_ that contains
+  any number of arguments and nested blocks. Block labels must be string literals.
+- _Arguments_ assign a value to a name. They appear within blocks.
+- _Expressions_ represent a value, either literally or by referencing and
+  combining other values. They appear as values for arguments, or within other
+  expressions.
+
+For full details about Nomad's syntax, see:
+
+- [Configuration Syntax](/nomad/docs/job-specification/hcl2/syntax)
+- [Expressions](/nomad/docs/job-specification/hcl2/expressions)
+
+### Blocks
+
+Block syntax is as follows, using unquoted attributes and quoted values:
+
+```hcl
+meta {
+  team         = "..."
+  organization = "..."
+}
+```
+
+Additionally, block attributes must be [HCL2 valid identifiers](https://github.com/hashicorp/hcl/blob/v2.8.0/hclsyntax/spec.md#identifiers).
+Generally, identifiers may only contain letters, numbers, underscore `_`,
+or a dash `-`, and start with a letter. Notable,
+[`meta`](/nomad/docs/job-specification/meta), and
+[`env`](/nomad/docs/job-specification/env) keys may not
+contain other symbols (e.g. `.`, `#`).
+
+Task driver config fields may require extra attention if they contain invalid
+identifiers. For example, docker [`sysctl`](/nomad/docs/drivers/docker#sysctl) must
+use the map assignment syntax if the keys aren't valid:
+
+```hcl
+sysctl = {
+  "net.core.somaxconn/docs/drivers/docker#sysctl" = "16384"
+}
+```
+
+Additionally, task driver config fields may not nest block syntax within an
+assignment syntax. The following [`mounts`](/nomad/docs/drivers/docker#mounts) syntax is no longer valid:
+
+```hcl
+# INVALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options {  # <- block syntax is not valid here
+      size = 10000
+    }
+  }
+]
+```
+
+Here, the `tmpfs_options` block declaration is invalid HCL2 syntax, and must be an assignment instead:
+
+```hcl
+# VALID in Nomad 1.0
+mounts = [
+  {
+    type = "tmpfs"
+    tmpfs_options = {
+      size = 10000
+    }
+  }
+]
+```
+
+Or better yet, the new [`mount`](/nomad/docs/drivers/docker#mount) syntax, introduced in Nomad 1.0.1, is more appropriate here:
+
+```hcl
+mount {
+  type = "tmpfs"
+  tmpfs_options {
+    size = 10000
+  }
+}
+```
+
+### Multiline "here doc" string
+
+Nomad supports multi-line string literals in the so-called "heredoc" style, inspired by Unix shell languages:
+
+```hcl
+template {
+  data = <<EOF
+hello
+  world
+  EOF
+}
+```
+
+HCL2 trims the whitespace preceding the delimiter in the last line. So in the
+above example, `data` is read as `"hello\n world\n "` in HCL1, but `"hello\n world\n"` (note lack of trailing whitespace) in HCL2.
+
+### Decimals
+
+HCL2 requires a leading zero for decimal values lower than 1 (e.g. `0.3`, `0.59`, `0.9`).
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/locals.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/locals.mdx
new file mode 100644
index 0000000000..5629c70c69
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/locals.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: Local Values - HCL Configuration Language
+description: >-
+  Local values assign a name to an expression that can then be used multiple
+  times within a folder.
+---
+
+# Local Values
+
+Local values assign a name to an expression, that can then be used multiple
+times within a folder.
+
+If [variables](/nomad/docs/job-specification/hcl2/variables) are analogous to
+function arguments then _local values_ are comparable to a function's local
+variables.
+
+## Examples
+
+Local values are defined in `locals` blocks:
+
+```hcl
+# A computed default name prefix
+locals {
+  default_name_prefix = "${var.project_name}-web"
+  name_prefix         = "${var.name_prefix != "" ? var.name_prefix : local.default_name_prefix}"
+
+  # unlike variables, locals don't have type constraints, so if you use
+  # functions that take maps but not objects, you may need to convert them
+  number_of_ports = length(convert({"www" = "80"}, map(string)))
+}
+
+# Local values can be interpolated elsewhere using the "local." prefix.
+job "example_loadbalancer" {
+  name = "${local.name_prefix}_loadbalancer"
+  # ...
+}
+```
+
+## Description
+
+The `locals` block defines one or more local variables.
+
+The names given for the items in the `locals` block must be unique. The given
+value can be any expression that is valid within the current file.
+
+The expression of a local value can refer to other locals, but reference cycles
+are not allowed. That is, a local cannot refer to itself or to a variable that
+refers (directly or indirectly) back to it.
+
+It's recommended to group together logically-related local values into a single
+block, particularly if they depend on each other. This will help the reader
+understand the relationships between variables. Conversely, prefer to define
+_unrelated_ local values in _separate_ blocks, and consider annotating each
+block with a comment describing any context common to all of the enclosed
+locals.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/syntax.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/syntax.mdx
new file mode 100644
index 0000000000..c07fb1a8ec
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/syntax.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: Syntax - Configuration Language
+description: |-
+  HCL has its own syntax, intended to combine declarative
+  structure with expressions in a way that is easy for humans to read and
+  understand.
+---
+
+# HCL Configuration Syntax
+
+Other pages in this section have described various configuration constructs
+that can appear in HCL. This page describes the lower-level syntax of the
+language in more detail, revealing the building blocks that those constructs
+are built from.
+
+This page describes the _native syntax_ of HCL, which is a rich language
+designed to be easy for humans to read and write.
+
+This low-level syntax of HCL is defined in terms of a syntax called _HCL_,
+which is also used by configuration languages in other applications, and in
+particular other HashiCorp products. It is not necessary to know all of the
+details of HCL in order to use Nomad, and so this page summarizes the most
+important details. If you are interested, you can find a full definition of HCL
+syntax in [the HCL native syntax
+specification](https://github.com/hashicorp/hcl/blob/hcl2/hclsyntax/spec.md).
+
+## Arguments and Blocks
+
+HCL syntax is built around two key syntax constructs:
+arguments and blocks.
+
+### Arguments
+
+An _argument_ assigns a value to a particular name:
+
+```hcl
+image_id = "nginx:1.19"
+```
+
+The identifier before the equals sign is the _argument name_, and the expression
+after the equals sign is the argument's value.
+
+The context where the argument appears determines what value types are valid
+(for example, each job block type has a schema that defines the types of its
+arguments), but many arguments accept arbitrary
+[expressions](/nomad/docs/job-specification/hcl2/expressions), which allow the value to
+either be specified literally or generated from other values programmatically.
+
+### Blocks
+
+A _block_ is a container for other content:
+
+```hcl
+task "webserver" {
+  driver = "docker"
+
+  config {
+    # ...
+  }
+}
+```
+
+A block has a _type_ (`task` in this example). Each block type defines
+how many _labels_ must follow the type keyword. The `task` block type
+expects one label, which is `webserver` in the example above.
+A particular block type may have any number of required labels, or it may
+require none as with the nested `config` block type.
+
+After the block type keyword and any labels, the block _body_ is delimited
+by the `{` and `}` characters. Within the block body, further arguments
+and blocks may be nested, creating a hierarchy of blocks and their associated
+arguments.
+
+HCL uses a limited number of _top-level block types,_ which
+are blocks that can appear outside of any other block in a configuration file.
+
+## Identifiers
+
+Argument names, block type names, and the names of most Nomad-specific
+constructs like tasks, input variables, etc. are all _identifiers_.
+
+Identifiers can contain letters, digits, underscores (`_`), and hyphens (`-`).
+The first character of an identifier must not be a digit, to avoid ambiguity
+with literal numbers.
+
+For complete identifier rules, Nomad implements
+[the Unicode identifier syntax](http://unicode.org/reports/tr31/), extended to
+include the ASCII hyphen character `-`.
+
+## Comments
+
+HCL supports three different syntaxes for comments:
+
+- `#` begins a single-line comment, ending at the end of the line.
+- `//` also begins a single-line comment, as an alternative to `#`.
+- `/*` and `*/` are start and end delimiters for a comment that might span
+  over multiple lines.
+
+The `#` single-line comment style is the default comment style and should be
+used in most cases. Automatic configuration formatting tools may automatically
+transform `//` comments into `#` comments, since the double-slash style is
+not idiomatic.
+
+## Character Encoding and Line Endings
+
+Nomad configuration files must always be UTF-8 encoded. While the
+delimiters of the language are all ASCII characters, Nomad accepts
+non-ASCII characters in identifiers, comments, and string values.
+
+Nomad accepts configuration files with either Unix-style line endings
+(LF only) or Windows-style line endings (CR then LF), but the idiomatic style
+is to use the Unix convention, and so automatic configuration formatting tools
+may automatically transform CRLF endings to LF.
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/hcl2/variables.mdx b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/variables.mdx
new file mode 100644
index 0000000000..fb820cf5b8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/hcl2/variables.mdx
@@ -0,0 +1,336 @@
+---
+layout: docs
+page_title: Input Variables - HCL Configuration Language
+description: |-
+  Input variables are parameters for Nomad jobs.
+  This page covers configuration syntax for variables.
+---
+
+# Input Variables
+
+Input variables serve as parameters for a Nomad job, allowing aspects of the
+job to be customized without altering the job's own source code.
+
+When you declare variables in the same file as the job specification, you
+can set their values using CLI options and environment variables.
+
+-> **Note:** For brevity, input variables are sometimes referred to as just
+"variables" when it is clear from context what sort of variable is being
+discussed (related to HCL job files). They should not be confused with [Nomad
+Variables][], which are useful for storing small pieces of configuration or
+secret data accessible from Jobs at runtime.  Other kinds of variables in Nomad
+include [_environment variables_][] (set by the shell where Nomad runs) and
+_expression variables_ (used to indirectly represent a value in an
+[expression][]).
+
+## Declaring an Input Variable
+
+Each input variable accepted by a job must be declared using a `variable`
+block :
+
+```hcl
+variable "image_id" {
+  type = string
+}
+
+variable "availability_zone_names" {
+  type    = list(string)
+  default = ["us-west-1a"]
+}
+
+variable "docker_ports" {
+  type = list(object({
+    internal = number
+    external = number
+    protocol = string
+  }))
+  default = [
+    {
+      internal = 8300
+      external = 8300
+      protocol = "tcp"
+    }
+  ]
+}
+```
+
+Or a less precise variables block:
+
+```hcl
+variables {
+  foo       = "value"
+  my_secret = "foo"
+}
+```
+
+The label after the `variable` keyword or a label of a `variables` block is a
+name for the variable, which must be unique among all variables in the same
+job. This name is used to assign a value to the variable from outside and to
+reference the variable's value from within the job.
+
+The `variable` block can optionally include a `type` argument to specify what
+value types are accepted for the variable, as described in the following
+section.
+
+The `variable` declaration can also include a `default` argument. If present,
+the variable is considered to be _optional_ and the default value will be used
+if no value is set when calling the job or running Nomad. The `default`
+argument requires a literal value and cannot reference other objects in the
+configuration.
+
+## Using Input Variable Values
+
+Within the job that declared a variable, its value can be accessed from within
+[expressions](/nomad/docs/job-specification/hcl2/expressions) as `var.<NAME>`, where
+`<NAME>` matches the label given in the declaration block:
+
+```hcl
+config {
+  image = var.task_image
+  label = var.task_labels
+}
+```
+
+The value assigned to a variable can be accessed only from expressions within
+the folder where it was declared. Note that a block label (such as the job ID
+or task group name) is not an expression and so can't be interpolated with a
+variable or local.
+
+## Type Constraints
+
+The `type` argument in a `variable` block allows you to restrict the [type of
+value](/nomad/docs/job-specification/hcl2/expressions#types-and-values) that will be
+accepted as the value for a variable. If no type constraint is set then a
+value of any type is accepted.
+
+While type constraints are optional, we recommend specifying them; they serve
+as easy reminders for users of the job, and allow Nomad to return a helpful
+error message if the wrong type is used.
+
+Type constraints are created from a mixture of type keywords and type
+constructors. The supported type keywords are:
+
+- `string`
+- `number`
+- `bool`
+
+The type constructors allow you to specify complex types such as collections:
+
+- `list(<TYPE>)`
+- `set(<TYPE>)`
+- `map(<TYPE>)`
+- `object({<ATTR NAME> = <TYPE>, ... })`
+- `tuple([<TYPE>, ...])`
+
+The keyword `any` may be used to indicate that any type is acceptable. For more
+information on the meaning and behavior of these different types, as well as
+detailed information about automatic conversion of complex types, see [Type
+Constraints](/terraform/language/expressions/type-constraints).
+
+If both the `type` and `default` arguments are specified, the given default
+value must be convertible to the specified type.
+
+If only `default` is specified, the type of the default value will be used.
+
+When the `type` and `default` are both _not_ specified and you try to set a
+variable [from env vars](#environment-variables) or [from the command
+line](#variables-on-the-command-line), the variable will always be interpreted
+as a string.
+
+## Input Variable Documentation
+
+Because the input variables of a job are part of its user interface, you can
+briefly describe the purpose of each variable using the optional `description`
+argument:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The docker image used for task."
+}
+```
+
+The description should concisely explain the purpose of the variable and what
+kind of value is expected. This description string might be included in
+documentation about the job, and so it should be written from the perspective
+of the user of the job rather than its maintainer. For commentary for job
+maintainers, use comments.
+
+## Input Variable Custom Validation Rules
+
+Input variables support specifying arbitrary custom validation rules for a particular
+variable using a `validation` block nested within the corresponding `variable` block:
+
+```hcl
+variable "image_id" {
+  type        = string
+  description = "The id of the machine image (AMI) to use for the server."
+
+  validation {
+    condition     = substr(var.image_id, 0, 4) == "ami-"
+    error_message = "The image_id value must be a valid AMI id, starting with \"ami-\"."
+  }
+}
+```
+
+The condition argument is an expression that must use the value of the variable to
+return true if the value is valid, or false if it is invalid. The expression can
+refer only to the variable that the condition applies to, and _must_ not produce errors.
+
+If condition evaluates to false, Nomad will produce an error message that includes
+the sentences given in `error_message`. The error message string should be at least
+one full sentence explaining the constraint that failed, starting with an uppercase
+letter ( if the alphabet permits it ) and ending with a period or question mark.
+
+Multiple validation blocks can be declared in which case error messages will be
+returned for all failed conditions.
+
+## Assigning Values to job Variables
+
+Once a variable is declared in your configuration, you can set it:
+
+- Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
+- As environment variables, for example: `NOMAD_VAR_foo=bar`
+
+The following sections describe these options in more detail.
+
+### Variables on the Command Line
+
+To specify individual variables on the command line, use the `-var` option when
+running the `nomad job run` command:
+
+```shell-session
+$ nomad job run -var="image_id=nginx:1.19" example.nomad.hcl
+```
+
+The `-var` option can be used any number of times in a single command.
+
+If you plan to assign variables via the command line, we strongly recommend that
+you at least set a default type instead of using empty blocks; this helps the
+HCL parser understand what is being set. Otherwise, the interpreter will assume
+that any variable set on the command line is a string.
+
+### Variable Definitions Files
+
+To set lots of variables, it is more convenient to specify their values in a
+_variable definitions file_ and then specify that file on the command line with
+`-var-file`:
+
+```shell-session
+$ nomad job run -var-file="testing.vars" example.nomad.hcl
+```
+
+A variable definitions file uses the same HCL basic syntax, but consists only
+of variable name assignments:
+
+```hcl
+image_id = "nginx:1.19"
+labels = [
+  "testing",
+  "internal",
+]
+```
+
+Alternatively, the files can be JSON objects, with the root object properties
+corresponding to variable names:
+
+```json
+{
+  "image_id": "nginx:1.19",
+  "labels": ["testing", "internal"]
+}
+```
+
+### Environment Variables
+
+As a fallback for the other ways of defining variables, Nomad searches the
+environment of its own process for environment variables named `NOMAD_VAR_`
+followed by the name of a declared variable.
+
+This can be useful when running Nomad in automation, or when running a
+sequence of Nomad commands in succession with the same variables. For example,
+at a `bash` prompt on a Unix system:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+$ nomad job run example.nomad.hcl
+...
+```
+
+On operating systems where environment variable names are case-sensitive,
+Nomad matches the variable name exactly as given in configuration, and so the
+required environment variable name will usually have a mix of upper and lower
+case letters as in the above example.
+
+### Complex-typed Values
+
+When variable values are provided in a variable definitions file, Nomad's
+[usual syntax](/nomad/docs/job-specification/hcl2/expressions) can be used to assign
+complex-typed values, like lists and maps.
+
+Some special rules apply to the `-var` command line option and to environment
+variables. For convenience, Nomad defaults to interpreting `-var` and
+environment variable values as literal strings, which do not need to be quoted:
+
+```shell-session
+$ export NOMAD_VAR_image_id=nginx:1.19
+```
+
+However, if an input variable uses a [type constraint](#type-constraints) to
+require a complex value (list, set, map, object, or tuple), Nomad will instead
+attempt to parse its value using the same syntax used within variable
+definitions files, which requires careful attention to the string escaping
+rules in your shell:
+
+```shell-session
+$ export NOMAD_VAR_availability_zone_names='["us-west-1b","us-west-1d"]'
+```
+
+For readability, and to avoid the need to worry about shell escaping, we
+recommend always setting complex variable values via variable definitions
+files.
+
+### Variable Definition Precedence
+
+The above mechanisms for setting variables can be used together in any
+combination.
+
+Nomad loads variables in the following order, with later sources taking
+precedence over earlier ones:
+
+- Environment variables (lowest priority)
+- Any `-var` and `-var-file` options on the command line, in the order they are
+  provided. (highest priority)
+
+If the same variable is assigned multiple values using different mechanisms,
+Nomad uses the _last_ value it finds, overriding any previous values. Note
+that the same variable cannot be assigned multiple values within a single source.
+
+~> **Important:** Variables with map and object values behave the same way as
+other variables: the last value found overrides the previous values.
+
+## A variable value must be known:
+
+Take the following variable for example:
+
+```hcl
+variable "foo" {
+  type = string
+}
+```
+
+Here `foo` must have a known value but you can default it to `null` to make
+this behavior optional :
+
+|                                 |          no default          | `default = null` | `default = "xy"` |
+| :-----------------------------: | :--------------------------: | :--------------: | :--------------: |
+|           foo unused            | error, "foo needs to be set" |        -         |        -         |
+|             var.foo             | error, "foo needs to be set" |       null       |        xy        |
+| `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
+|   `-var foo=yz`<br />var.foo    |              yz              |        yz        |        yz        |
+
+
+[Nomad Variables]: /nomad/docs/concepts/variables
+[_environment variables_]: /nomad/docs/runtime/environment
+[expression]: /nomad/docs/job-specification/hcl2/expressions
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/identity.mdx b/content/nomad/v1.9.x/content/docs/job-specification/identity.mdx
new file mode 100644
index 0000000000..a02f809c48
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/identity.mdx
@@ -0,0 +1,362 @@
+---
+layout: docs
+page_title: identity Block - Job Specification
+description: |-
+  The "identity" block allows tasks to use their Nomad Workload Identity via an
+  environment variable or file.
+---
+
+# `identity` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service', 'identity'],
+    ['job', 'group', 'task', 'identity'],
+    ['job', 'group', 'task', 'service', 'identity'],
+  ]}
+/>
+
+The `identity` block allows a task access to its [Workload Identity][] via an
+environment variable or file. Nomad will create a _default_ identity for all
+workloads, but it is *not* exposed to a task. You may also set additional
+identities intended for use with external applications such as Vault, Consul, or
+OIDC authentication.
+
+For example, the following will expose the default Workload Identity as an
+environment variable and file to the task, and a second Workload Identity
+configured for a third-party OIDC provider:
+
+```hcl
+job "docs" {
+  group "example" {
+    task "api" {
+
+      identity {
+        env         = true
+        file        = true
+        filepath    = "local/example.jwt"
+
+        # Restart on token renewal to get the new env var
+        change_mode = "restart"
+      }
+
+      identity {
+        name        = "example"
+        aud         = ["oidc.example.com"]
+        file        = true
+        ttl         = "1h"
+
+        # Send a HUP signal when the token file is updated
+        change_mode   = "signal"
+        change_signal = "SIGHUP"
+      }
+
+      # ...
+    }
+  }
+}
+```
+
+## `identity` Parameters
+
+- `name` `(string: "default")` - The name of the workload identity, which must
+  be unique per task. Only one `identity` block in a task can omit the `name`
+  field.
+- `aud` `([]string: nil)` - The audience field for the workload identity. This
+  should always be set for non-default identities.
+- `change_mode` `(string: "noop")` - Specifies the behavior Nomad should take when the token changes.
+
+  - `"noop"` - take no action. The default since tasks may choose to reload
+      tokens only when their current token gets rejected or implement their own
+      change detection.
+  - `"restart"` - restart the task.
+  - `"signal"` - send a configurable signal to the task. Must set `change_signal`.
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGHUP"` or `"SIGUSR1"`. This option is required if the
+  `change_mode` is `signal`.
+- `env` `(bool: false)` - If true the workload identity will be available in the
+  task's `NOMAD_TOKEN` environment variable.
+- `file` `(bool: false)` - If true the workload identity will be available in
+  the task's filesystem via the path `secrets/nomad_token`. If the
+  [`task.user`][taskuser] parameter is set, the token file will only be
+  readable by that user. Otherwise the file is readable by everyone but is
+  protected by parent directory permissions.
+- `filepath` `(string: "")` - If not empty and file is `true`, the workload
+  identity will be available at the specified location relative to the 
+  [task working directory][] instead of the `NOMAD_SECRETS_DIR`.
+- `ttl` `(string: "")` - The lifetime of the identity before it expires. The
+  client will renew the identity at roughly half the TTL. This is specified
+  using a label suffix like "30s" or "1h". You may not set a TTL on the default
+  identity. You should always set a TTL for non-default identities.
+
+## Task API
+
+It can be convenient to combine workload identity with Nomad's [Task API]
+[taskapi] for  enabling tasks to access the Nomad API.
+
+## Workload Identities for Consul
+
+Jobs that need access to Consul can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task or service that will access Consul.
+
+You can configure Nomad servers to automatically add default identities for
+Consul using the [`consul.service_identity`][] and [`consul.task_identity`][]
+agent configuration. Upon job registration, the Nomad server updates tasks that
+have a [`consul`][] or [`template`][] block and services that use the Consul
+service provider to include the default identities.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identities configured in the Nomad servers. Identities for
+tasks must have a [`name`](#name) that follows the pattern
+`consul_<cluster name>`. Identities for services do not need to specify a
+`name`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the task
+identity name should be `consul_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Consul clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/consul#cluster">
+  <code>consul.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_consul_wid] section of the Consul
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="3,14-17,30-34">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {}
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_default"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="3-5,16-19,34-38">
+
+```hcl
+job "httpd" {
+  group "httpd" {
+    consul {
+      cluster = "prod"
+    }
+
+    network {
+      port "http" {}
+    }
+
+    service {
+      provider = "consul"
+      name     = "httpd"
+      port     = "http"
+
+      identity {
+        aud = ["consul.io"]
+        ttl = "1h"
+      }
+    }
+
+    task "httpd" {
+      driver = "docker"
+
+      config {
+        image   = "busybox:1.36"
+        command = "httpd"
+        args    = ["-f", "-p", "${NOMAD_PORT_http}"]
+        ports   = ["http"]
+      }
+
+      identity {
+        name = "consul_prod"
+        aud  = ["consul.io"]
+        ttl  = "1h"
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+## Workload Identities for Vault
+
+Jobs that need access to Vault can use Nomad workload identities for
+authentication. These identities are specified as additional `identity` blocks
+inside the task that will access Vault.
+
+You can configure Nomad servers to automatically add default identities for
+Vault using the [`vault.default_identity`][] agent configuration. Upon job
+registration, the Nomad server updates tasks that have a [`vault`][] block to
+include the default identity.
+
+You can also specify these identities directly in the job. When provided, they
+override the default identity configured in the Nomad servers. The identity
+[`name`](#name) must follow the pattern `vault_<cluster name>`.
+
+In Nomad Community Edition, `<cluster_name>` is always `default`, so the
+identity name should be `vault_default`.
+
+<EnterpriseAlert>
+  Nomad Enterprise supports multiple Vault clusters. The value of <code>
+  &lt;cluster_name&gt;</code> must be the same as the <a href="/nomad/docs/job-specification/vault#cluster">
+  <code>vault.cluster</code></a> value for the task.
+</EnterpriseAlert>
+
+Refer to [Nomad Workload Identities][int_vault_wid] section of the Vault
+integration documentation for more information.
+
+<Tabs>
+<Tab heading="Nomad Community Edition" group="ce">
+<CodeBlockConfig highlight="19,21-25">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {}
+
+      identity {
+        name = "vault_default"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+<Tab heading="Nomad Enterprise" group="ent">
+<CodeBlockConfig highlight="19-21,23-27">
+
+```hcl
+job "mongo" {
+  namespace = "default"
+
+  group "db" {
+    network {
+      port "db" {
+        to = 27017
+      }
+    }
+
+    task "mongo" {
+      driver = "docker"
+
+      config {
+        image = "mongo:7"
+        ports = ["db"]
+      }
+
+      vault {
+        cluster = "prod"
+      }
+
+      identity {
+        name = "vault_prod"
+        aud  = ["vault.io"]
+        ttl  = "1h"
+      }
+
+      template {
+        data        = <<EOF
+{{with secret "kv/data/default/mongo/config"}}
+MONGO_INITDB_ROOT_USERNAME=root
+MONGO_INITDB_ROOT_PASSWORD={{.Data.data.root_password}}
+{{end}}
+EOF
+        destination = "secrets/env"
+        env         = true
+      }
+    }
+  }
+}
+```
+
+</CodeBlockConfig>
+</Tab>
+</Tabs>
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity "Nomad Workload Identity"
+[`consul.cluster`]: /nomad/docs/job-specification/consul#cluster
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[`consul.task_identity`]: /nomad/docs/configuration/consul#task_identity
+[`consul`]: /nomad/docs/job-specification/consul
+[`template`]: /nomad/docs/job-specification/template
+[`vault.default_identity`]: /nomad/docs/configuration/vault#default_identity
+[`vault`]: /nomad/docs/job-specification/vault
+[int_consul_wid]: /nomad/docs/integrations/consul-integration#nomad-workload-identities
+[int_vault_wid]: /nomad/docs/integrations/vault-integration#nomad-workload-identities
+[taskapi]: /nomad/api-docs/task-api
+[taskuser]: /nomad/docs/job-specification/task#user "Nomad task Block"
+[windows]: https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/index.mdx b/content/nomad/v1.9.x/content/docs/job-specification/index.mdx
new file mode 100644
index 0000000000..4cbe06b145
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/index.mdx
@@ -0,0 +1,152 @@
+---
+layout: docs
+page_title: Job Specification
+description: Learn about the Job specification used to submit jobs to Nomad.
+---
+
+# Job Specification
+
+The Nomad job specification (or "jobspec" for short) defines the schema for
+Nomad jobs. Nomad jobs are specified in [HCL][], which aims to strike a balance
+between human readable and editable, and machine-friendly.
+
+The job specification is broken down into smaller pieces, which you will find
+expanded in the navigation menu. We recommend getting started at the [job][]
+block. Alternatively, you can keep reading to see a few examples.
+
+Nomad HCL is parsed in the command line and sent to Nomad in JSON format via
+the HTTP API.
+
+The general hierarchy for a job is:
+
+```text
+job
+  \_ group
+  |     \_ task
+  |     \_ task
+  |
+  \_ group
+        \_ task
+        \_ task
+```
+
+Each job file has only a single job, however a job may have multiple groups, and
+each group may have multiple tasks. Groups contain a set of tasks that are
+co-located on the same Nomad client.
+
+## Example
+
+This example shows a sample job file. We tried to keep it as simple as possible,
+while still showcasing the power of Nomad. For a more detailed explanation of
+any of these fields, please use the navigation to dive deeper.
+
+```hcl
+# This declares a job named "docs". There can be exactly one
+# job declaration per job file.
+job "docs" {
+  # Specify this job should run in the region named "us". Regions
+  # are defined by the Nomad servers' configuration.
+  region = "us"
+
+  # Spread the tasks in this job between us-west-1 and us-east-1.
+  datacenters = ["us-west-1", "us-east-1"]
+
+  # Run this job as a "service" type. Each job type has different
+  # properties. See the documentation below for more examples.
+  type = "service"
+
+  # Specify this job to have rolling updates, two-at-a-time, with
+  # 30 second intervals.
+  update {
+    stagger      = "30s"
+    max_parallel = 2
+  }
+
+
+  # A group defines a series of tasks that should be co-located
+  # on the same client (host). All tasks within a group will be
+  # placed on the same host.
+  group "webs" {
+    # Specify the number of these tasks we want.
+    count = 5
+
+    network {
+      # This requests a dynamic port named "http". This will
+      # be something like "46283", but we refer to it via the
+      # label "http".
+      port "http" {}
+
+      # This requests a static port on 443 on the host. This
+      # will restrict this task to running once per host, since
+      # there is only one port 443 on each host.
+      port "https" {
+        static = 443
+      }
+    }
+
+    # The service block tells Nomad how to register this service
+    # with Consul for service discovery and monitoring.
+    service {
+      # This tells Consul to monitor the service on the port
+      # labelled "http". Since Nomad allocates high dynamic port
+      # numbers, we use labels to refer to them.
+      port = "http"
+
+      check {
+        type     = "http"
+        path     = "/health"
+        interval = "10s"
+        timeout  = "2s"
+      }
+    }
+
+    # Create an individual task (unit of work). This particular
+    # task utilizes a Docker container to front a web application.
+    task "frontend" {
+      # Specify the driver to be "docker". Nomad supports
+      # multiple drivers.
+      driver = "docker"
+
+      # Configuration is specific to each driver.
+      config {
+        image = "hashicorp/web-frontend"
+        ports = ["http", "https"]
+      }
+
+      # It is possible to set environment variables which will be
+      # available to the task when it runs.
+      env {
+        DB_HOST = "db01.example.com"
+        DB_USER = "web"
+        DB_PASS = "loremipsum"
+      }
+
+      # Specify the maximum resources required to run the task,
+      # include CPU and memory.
+      resources {
+        cpu    = 500 # MHz
+        memory = 128 # MB
+      }
+    }
+  }
+}
+```
+
+The `service` block can also be specified at the group level. This allows job specification authors
+to create and register services with Consul Service Mesh. A service block specified at the group 
+level must include a [`connect`][] block, like the following snippet.
+
+```hcl
+service {
+       name = "count-api"
+       port = "9001"
+
+       connect {
+         sidecar_service {}
+       }
+     }
+```
+
+[hcl]: https://github.com/hashicorp/hcl 'HashiCorp Configuration Language'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[connect]: /nomad/docs/job-specification/connect 'Connect Block Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/job.mdx b/content/nomad/v1.9.x/content/docs/job-specification/job.mdx
new file mode 100644
index 0000000000..0f1302becd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/job.mdx
@@ -0,0 +1,260 @@
+---
+layout: docs
+page_title: job Block - Job Specification
+description: |-
+  The "job" block is the top-most configuration option in the job
+  specification. A job is a declarative specification of tasks that Nomad
+  should run.
+---
+
+# `job` Block
+
+<Placement groups={['job']} />
+
+The `job` block is the top-most configuration option in the job specification.
+A job is a declarative specification of tasks that Nomad should run. Jobs have
+one or more task groups, which are themselves collections of one or more tasks.
+Job names are unique per [region][region] or [namespace][namespace].
+
+```hcl
+job "docs" {
+  constraint {
+    # ...
+  }
+
+  datacenters = ["us-east-1"]
+
+  node_pool = "prod"
+
+  group "example" {
+    # ...
+    
+    task "docs" {
+      # ...
+    }
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  parameterized {
+    # ...
+  }
+
+  periodic {
+    # ...
+  }
+
+  priority = 100
+
+  region = "north-america"
+
+  update {
+    # ...
+  }
+}
+```
+
+## `job` Parameters
+
+- `all_at_once` `(bool: false)` - Controls whether the scheduler can make
+  partial placements if optimistic scheduling resulted in an oversubscribed
+  node. This does not control whether all allocations for the job, where all
+  would be the desired count for each task group, must be placed atomically.
+  This should only be used for special circumstances.
+
+- `constraint` <code>([Constraint][constraint]: nil)</code> -
+  This can be provided multiple times to define additional constraints. See the
+  [Nomad constraint reference][constraint] for more
+  details.
+
+- `affinity` <code>([Affinity][affinity]: nil)</code> -
+  This can be provided multiple times to define preferred placement criteria. See the
+  [Nomad affinity reference][affinity] for more
+  details.
+
+- `spread` <code>([Spread][spread]: nil)</code> - This can be provided multiple times
+  to define criteria for spreading allocations across a node attribute or metadata.
+  See the [Nomad spread reference][spread] for more details.
+
+- `datacenters` `(array<string>: ["*"])` - A list of datacenters in the region
+  which are eligible for task placement. This field allows wildcard globbing
+  through the use of `*` for multi-character matching. The default value is
+  `["*"]`, which allows the job to be placed in any available datacenter.
+
+- `node_pool` `(string: <optional>)` - Specifies the node pool to place the job
+  in. The node pool must exist when the job is registered. Defaults to `"default"`.
+
+- `group` <code>([Group][group]: &lt;required&gt;)</code> - Specifies the start of a
+  group of tasks. This can be provided multiple times to define additional
+  groups. Group names must be unique within the job file.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `name` `(string: <optional>)` - Specifies a name for the job, which otherwise
+  defaults to the job ID.
+
+- `migrate` <code>([Migrate][]: nil)</code> - Specifies the groups strategy for
+  migrating off of draining nodes. If omitted, a default migration strategy is
+  applied. Only service jobs with a count greater than 1 support migrate blocks.
+
+- `namespace` `(string: "default")` - The namespace in which to execute the job.
+
+- `parameterized` <code>([Parameterized][parameterized]: nil)</code> - Specifies
+  the job as a parameterized job such that it can be dispatched against.
+
+- `periodic` <code>([Periodic][]: nil)</code> - Allows the job to be scheduled
+  at fixed times, dates or intervals.
+
+- `priority` `(int: 50)` - Specifies the job priority which is used to
+  prioritize scheduling and access to resources.
+  Must be between 1 and [`job_max_priority`] inclusively,
+  with a larger value corresponding to a higher priority.
+  If value 0 is provided this will fallback to [`job_default_priority`].
+  Priority only has an effect when job preemption is enabled.
+  It does not have an effect on which of multiple pending jobs is run first.
+
+- `region` `(string: "global")` - The region in which to execute the job.
+
+- `reschedule` <code>([Reschedule][]: nil)</code> - Allows to specify a
+  rescheduling strategy. Nomad will then attempt to schedule the task on another
+  node if any of its allocation statuses become "failed".
+
+- `type` `(string: "service")` - Specifies the [Nomad scheduler][scheduler] to
+  use. Nomad provides the `service`, `system`, `batch`, and `sysbatch` schedulers.
+
+- `update` <code>([Update][update]: nil)</code> - Specifies the task's update
+  strategy. When omitted, a default update strategy is applied.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
+
+- `vault_token` `(string: "")` - Specifies the Vault token that proves the
+  submitter of the job has access to the specified policies in the
+  [`vault`][vault] block. This field is only used to transfer the token and is
+  not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `VAULT_TOKEN` environment variable when
+  running the job instead.
+
+- `consul_token` `(string: "")` - Specifies the Consul token that proves the
+  submitter of the job has access to the Service Identity policies associated
+  with the job's Consul Connect enabled services. This field is only used to
+  transfer the token and is not stored after job submission.
+
+  !> It is **strongly discouraged** to place the token as a configuration
+  parameter like this, since the token could be checked into source control
+  accidentally. Users should set the `CONSUL_HTTP_TOKEN` environment variable when
+  running the job instead.
+
+## `job` Examples
+
+The following examples only show the `job` blocks. Remember that the
+`job` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example job starts a Docker container which runs as a service. Even though
+the type is not specified as "service", that is the default job type.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      driver = "docker"
+      config {
+        image = "hashicorp/http-echo"
+        args  = ["-text", "hello"]
+      }
+
+      resources {
+        memory = 128
+      }
+    }
+  }
+}
+```
+
+### Batch Job
+
+This example job executes the `uptime` command on 10 Nomad clients in the fleet,
+restricting the eligible nodes to Linux machines.
+
+```hcl
+job "docs" {
+  type = "batch"
+
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  group "example" {
+    count = 10
+    task "uptime" {
+      driver = "exec"
+      config {
+        command = "uptime"
+      }
+    }
+  }
+}
+```
+
+### Consuming Secrets
+
+This example shows a job which retrieves secrets from Vault and writes those
+secrets to a file on disk, which the application then consumes. Nomad handles
+all interactions with Vault.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "cat" {
+      driver = "exec"
+
+      config {
+        command = "cat"
+        args    = ["local/secrets.txt"]
+      }
+
+      template {
+        data        = "{{ secret \"secret/data\" }}"
+        destination = "local/secrets.txt"
+      }
+
+      vault {
+        policies = ["secret-readonly"]
+      }
+    }
+  }
+}
+```
+
+When submitting this job, you would run:
+
+```shell-session
+$ VAULT_TOKEN="..." nomad job run example.nomad.hcl
+```
+
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[migrate]: /nomad/docs/job-specification/migrate 'Nomad migrate Job Specification'
+[namespace]: /nomad/tutorials/manage-clusters/namespaces
+[parameterized]: /nomad/docs/job-specification/parameterized 'Nomad parameterized Job Specification'
+[periodic]: /nomad/docs/job-specification/periodic 'Nomad periodic Job Specification'
+[region]: /nomad/tutorials/manage-clusters/federation
+[reschedule]: /nomad/docs/job-specification/reschedule 'Nomad reschedule Job Specification'
+[scheduler]: /nomad/docs/schedulers 'Nomad Scheduler Types'
+[spread]: /nomad/docs/job-specification/spread 'Nomad spread Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[update]: /nomad/docs/job-specification/update 'Nomad update Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[`job_max_priority`]: /nomad/docs/configuration/server#job_max_priority
+[`job_default_priority`]: /nomad/docs/configuration/server#job_default_priority
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/lifecycle.mdx b/content/nomad/v1.9.x/content/docs/job-specification/lifecycle.mdx
new file mode 100644
index 0000000000..c6dba83713
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/lifecycle.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: lifecycle Block - Job Specification
+description: |-
+  The "lifecycle" block configures when a task is run within the lifecycle of a
+  task group
+---
+
+# `lifecycle` Block
+
+<Placement groups={['job', 'group', 'task', 'lifecycle']} />
+
+The `lifecycle` block is used to express task dependencies in Nomad by
+configuring when a task is run within the lifecycle of a task group.
+
+Main tasks are tasks that do not have a `lifecycle` block. Lifecycle task hooks
+specify when other tasks are run in relation to the main tasks.
+There are three different lifecycle hooks, indicating when a task is started:
+
+- prestart tasks are started immediately
+- poststart tasks are started after the main tasks are running
+- poststop tasks are started after the main tasks are dead
+
+Tasks can be run with an additional parameter indicating whether they are ephemeral
+tasks or "sidecar" tasks that are expected to run for the duration of the main tasks.
+The absence of the sidecar flag indicates that the task is ephemeral
+and should not be restarted if it completes successfully.
+
+Learn more about [Nomad's task dependencies][learn-taskdeps].
+
+## `lifecycle` Parameters
+
+- `hook` `(string: <required>)` - Specifies when a task should be run within
+  the lifecycle of a group. The following hooks are available:
+
+  - `prestart` - Will be started immediately. The main tasks will not start until
+    all `prestart` tasks with `sidecar = false` have completed successfully.
+  - `poststart` - Will be started once all main tasks are running.
+  - `poststop` - Will be started once all main tasks have stopped successfully
+    or exhausted their failure [retries](/nomad/docs/job-specification/restart).
+
+- `sidecar` `(bool: false)` - Controls whether a task is ephemeral or
+  long-lived within the task group. If a lifecycle task is ephemeral
+  (`sidecar = false`), the task will not be restarted after it completes successfully. If a
+  lifecycle task is long-lived (`sidecar = true`) and terminates, it will be
+  restarted as long as the allocation is running.
+
+[learn-taskdeps]: /nomad/tutorials/task-deps
+
+## Lifecycle Examples
+
+The following include examples of archetypal lifecycle patterns.
+
+### Init Task Pattern
+
+Init tasks are useful for performing initialization steps that can't be more easily
+accomplished using [`template`](/nomad/docs/job-specification/template) or
+[`artifact`](/nomad/docs/job-specification/artifact), like waiting on other services
+or performing complex initialization.
+
+In the following example, the init task will block the main task from starting
+until the upstream database service is listening on the expected port:
+
+```hcl
+  task "wait-for-db" {
+    lifecycle {
+      hook = "prestart"
+      sidecar = false
+    }
+
+    driver = "exec"
+    config {
+      command = "sh"
+      args = ["-c", "while ! nc -z db.service.local.consul 8080; do sleep 1; done"]
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Companion Sidecar Pattern
+
+Companion or sidecar tasks run alongside the main task to perform an auxiliary
+task. Common examples include proxies and log shippers. These tasks benefit from
+running in the same task group because of tighter filesystem and networking
+coupling.
+
+```hcl
+  task "fluentd" {
+    lifecycle {
+      hook = "poststart"
+      sidecar = true
+    }
+
+    driver = "docker"
+    config {
+      image = "fluentd/fluentd"
+    }
+
+    template {
+      destination = "local/fluentd.conf"
+      data = ...
+    }
+  }
+
+  task "main-app" {
+    ...
+  }
+```
+
+### Cleanup Task Pattern
+
+Poststop tasks run after the main tasks have stopped. They are useful for performing
+post-processing that isn't available in the main tasks or for recovering from
+failures in the main tasks.
+
+The example below shows a chatbot which posts a notification when the main tasks
+have stopped:
+
+```hcl
+  task "main-app" {
+    ...
+  }
+
+  task "announce" {
+    lifecycle {
+      hook = "poststop"
+    }
+
+    driver = "docker"
+    config {
+      image = "alpine/httpie"
+      command = "http"
+      args = [
+        "POST",
+        "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
+        "text='All done!'"
+      ]
+    }
+  }
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/logs.mdx b/content/nomad/v1.9.x/content/docs/job-specification/logs.mdx
new file mode 100644
index 0000000000..bb361fd493
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/logs.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: logs Block - Job Specification
+description: |-
+  The "logs" block configures the log rotation policy for a task's stdout and
+  stderr. Logging is enabled by default with reasonable defaults. The "logs" block
+  allows for finer-grained control over how Nomad handles log files.
+---
+
+# `logs` Block
+
+<Placement groups={['job', 'group', 'task', 'logs']} />
+
+The `logs` block configures the log rotation policy for a task's `stdout` and
+`stderr`. Logging is enabled by default with reasonable defaults (provided in
+the parameters section below). The `logs` block allows for finer-grained control
+over how Nomad handles log files.
+
+Nomad's log rotation works by writing stdout/stderr output from tasks to a file
+inside the `alloc/logs/` directory with the following format:
+`<task-name>.<stdout/stderr>.<index>`. Output is written to a particular index,
+starting at zero, till that log file hits the configured `max_file_size`. After,
+a new file is created at `index + 1` and logs will then be written there. A log
+file is never rolled over, instead Nomad will keep up to `max_files` worth of
+logs and once that is exceeded, the log file with the lowest index is deleted.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      logs {
+        max_files     = 10
+        max_file_size = 10
+        disabled      = false
+      }
+    }
+  }
+}
+```
+
+Each job's logs will be written to ephemeral disk space. If you increase the total
+amount of logs on disk, you may want to increase ephemeral disk size as well. See
+the [ephemeral disk documentation][] for more information.
+
+For information on how to interact with logs after they have been configured,
+please see the [`nomad alloc logs`][logs-command] command.
+
+## `logs` Parameters
+
+- `max_files` `(int: 10)` - Specifies the maximum number of rotated files Nomad
+  will retain for `stdout` and `stderr`. Each stream is tracked individually, so
+  specifying a value of 2 will create 4 files - 2 for stdout and 2 for stderr
+
+- `max_file_size` `(int: 10)` - Specifies the maximum size of each rotated file
+  in `MB`. If the amount of disk resource requested for the task is less than
+  the total amount of disk space needed to retain the rotated set of files,
+  Nomad will return a validation error when a job is submitted.
+
+- `disabled` `(bool: false)` - Specifies that log collection should be enabled for
+  this task. If set to `true`, the task driver will attach stdout/stderr of the
+  task to `/dev/null` (or `NUL` on Windows). You should only disable log
+  collection if your application has some other way of emitting logs, such as
+  writing to a remote syslog server. Note that the `nomad alloc logs` command
+  and related APIs will return errors (404 "not found") if logging is disabled.
+
+  Some task drivers such as `docker` support a [`disable_log_collection`][]
+  option. If the task driver's `disable_log_collection` option is set to `true`,
+  it will override `disabled=false` in the task's `logs` block.
+
+## `logs` Examples
+
+The following examples only show the `logs` blocks. Remember that the
+`logs` block is only valid in the placements listed above.
+
+### Configure Defaults
+
+This example shows a default logging configuration. Yes, it is empty on purpose.
+Nomad automatically enables logging with reasonable defaults as described in the
+parameters section above.
+
+```hcl
+
+```
+
+### Customization
+
+This example asks Nomad to retain 3 rotated files for each of `stderr` and
+`stdout`, each a maximum size of 5 MB per file. The minimum disk space this
+would require is 30 MB (3 `stderr` &plus; 3 `stdout` &times; 5 MB &equals; 30 MB).
+
+```hcl
+logs {
+  max_files     = 3
+  max_file_size = 5
+}
+```
+
+[logs-command]: /nomad/docs/commands/alloc/logs 'Nomad logs command'
+[`disable_log_collection`]: /nomad/docs/drivers/docker#disable_log_collection
+[ephemeral disk documentation]: /nomad/docs/job-specification/ephemeral_disk 'Nomad ephemeral disk Job Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/meta.mdx b/content/nomad/v1.9.x/content/docs/job-specification/meta.mdx
new file mode 100644
index 0000000000..6f32810932
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/meta.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: meta Block - Job Specification
+description: The "meta" block allows for user-defined arbitrary key-value pairs.
+---
+
+# `meta` Block
+
+<Placement
+  groups={[
+    ['job', 'meta'],
+    ['job', 'group', 'meta'],
+    ['job', 'group', 'task', 'meta'],
+  ]}
+/>
+
+The `meta` block allows for user-defined arbitrary key-value pairs. It is
+possible to use the `meta` block at the [job][], [group][], or [task][] level.
+
+```hcl
+job "docs" {
+  meta {
+    my-key = "my-value"
+  }
+
+  group "example" {
+    meta {
+      my-key = "my-value"
+    }
+
+    task "server" {
+      meta {
+        my-key = "my-value"
+      }
+    }
+  }
+}
+```
+
+Metadata is merged up the job specification, so metadata defined at the job
+level applies to all groups and tasks within that job. Metadata defined at the
+group layer applies to all tasks within that group.
+
+Meta values are made available inside tasks as [runtime environment variables][env_meta].
+
+## `meta` Parameters
+
+The "parameters" for the `meta` block can be any key-value. The keys and values
+are both of type `string`, but they can be specified as other types. They will
+automatically be converted to strings. Any character in a key other than
+`[A-Za-z0-9_.]` will be converted to `_`.
+
+## `meta` Examples
+
+The following examples only show the `meta` blocks. Remember that the
+`meta` block is only valid in the placements listed above.
+
+### Coercion
+
+This example shows the different ways to specify key-value pairs. Internally,
+these values will be stored as their string representation. No type information
+is preserved.
+
+```hcl
+meta {
+  key = "true"
+  key = true
+
+  key = 1.4
+  key = "1.4"
+}
+```
+
+### Interpolation
+
+This example shows using [Nomad interpolation][interpolation] to populate
+environment variables.
+
+```hcl
+meta {
+  class = "${node.class}"
+}
+```
+
+### Meta keys with dots
+
+Meta keys that aren't valid HCLv2 identifiers, like ones containing `.`, require an alternative map assignment syntax.
+
+```hcl
+meta = {
+  "project.team" = "sre"
+}
+```
+
+## `meta` Usage Examples
+
+### Templates
+
+To make use of a `meta` value in a template, refer to its environment variable
+form.
+
+```hcl
+template {
+  destination = "local/out.txt"
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[env_meta]: /nomad/docs/runtime/environment#meta
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/migrate.mdx b/content/nomad/v1.9.x/content/docs/job-specification/migrate.mdx
new file mode 100644
index 0000000000..cf00064115
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/migrate.mdx
@@ -0,0 +1,90 @@
+---
+layout: docs
+page_title: migrate Block - Job Specification
+description: |-
+  The "migrate" block specifies the group's migrate strategy. The migrate
+  strategy is used to control the job's behavior when it is being migrated off
+  of a draining node.
+---
+
+# `migrate` Block
+
+<Placement
+  groups={[
+    ['job', 'migrate'],
+    ['job', 'group', 'migrate'],
+  ]}
+/>
+
+The `migrate` block specifies the group's strategy for migrating allocations from
+[draining][drain] nodes. If omitted, a default migration strategy is applied.
+If specified at the job level, the configuration will apply to all groups
+within the job. Only service jobs with a count greater than 1 support migrate
+blocks.
+
+Migrating happens when a Nomad node is drained. When a node is lost, Nomad
+[replaces][] the allocations instead and ignores the `migrate` block.  When the
+agent fails to set up the allocation or the tasks of an allocation more than
+their [`restart`][] block allows, Nomad [reschedules][] the allocations instead
+and ignores the `migrate` block.
+
+
+```hcl
+job "docs" {
+  migrate {
+    max_parallel     = 1
+    health_check     = "checks"
+    min_healthy_time = "10s"
+    healthy_deadline = "5m"
+  }
+}
+```
+
+When one or more nodes are draining, only `max_parallel` allocations will be
+stopped at a time. Node draining will not continue until replacement
+allocations have been healthy for their `min_healthy_time` or
+`healthy_deadline` is reached.
+
+Note that a node's drain [deadline][deadline] will override the `migrate`
+block for allocations on that node. The `migrate` block is for job authors to
+define how their services should be migrated, while the node drain deadline is
+for system operators to put hard limits on how long a drain may take.
+
+See the [Workload Migration Guide](/nomad/tutorials/manage-clusters/node-drain) for details
+on node draining.
+
+## `migrate` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations that can be
+  migrated at the same time. This number must be less than the total
+  [`count`][count] for the group as `count - max_parallel` will be left running
+  during migrations.
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][checks] are
+    healthy, and unhealthy if any of the tasks fail or not all checks become
+    healthy. This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being migrated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label
+  suffix like "2m" or "1h".
+
+[checks]: /nomad/docs/job-specification/service#check-parameters
+[count]: /nomad/docs/job-specification/group#count
+[drain]: /nomad/docs/commands/node/drain
+[deadline]: /nomad/docs/commands/node/drain#deadline
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[`restart`]: /nomad/docs/job-specification/restart
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/multiregion.mdx b/content/nomad/v1.9.x/content/docs/job-specification/multiregion.mdx
new file mode 100644
index 0000000000..f03b42e37d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/multiregion.mdx
@@ -0,0 +1,290 @@
+---
+layout: docs
+page_title: multiregion Block - Job Specification
+description: |-
+  The "multiregion" block specifies that a job will be deployed to multiple federated
+  regions.
+---
+
+# `multiregion` Block
+
+<Placement groups={[['job', 'multiregion']]} />
+
+<EnterpriseAlert />
+
+The `multiregion` block specifies that a job will be deployed to multiple
+[federated regions]. If omitted, the job will be deployed to a single region—the
+one specified by the `region` field or the `-region` command line flag to
+`nomad job run`.
+
+Federated Nomad clusters are members of the same gossip cluster but not the
+same raft cluster; they don't share their data stores. Each region in a
+multiregion deployment gets an independent copy of the job, parameterized with
+the values of the `region` block. Nomad regions coordinate to rollout each
+region's deployment using rules determined by the `strategy` block.
+
+```hcl
+job "docs" {
+  multiregion {
+
+    strategy {
+      max_parallel = 1
+      on_failure   = "fail_all"
+    }
+
+    region "west" {
+      count = 2
+      datacenters = ["west-1"]
+      meta {
+        my-key = "my-value-west"
+      }
+    }
+
+    region "east" {
+      count = 5
+      datacenters = ["east-1", "east-2"]
+      meta {
+        my-key = "my-value-east"
+      }
+    }
+  }
+}
+```
+
+## Multiregion Deployment States
+
+A single region deployment using one of the various [upgrade strategies]
+begins in the `running` state, and ends in the `successful` state, the
+`canceled` state (if another deployment supersedes it before it it's
+complete), or the `failed` state. A failed single region deployment may
+automatically revert to the previous version of the job if its `update`
+block has the [`auto_revert`][update-auto-revert] setting.
+
+In a multiregion deployment, regions begin in the `pending` state. This allows
+Nomad to determine that all regions have accepted the job before
+continuing. At this point up to `max_parallel` regions will enter `running` at
+a time. When each region completes its local deployment, it enters a `blocked`
+state where it waits until the last region has completed the deployment. The
+final region will unblock the regions to mark them as `successful`.
+
+## Parameterized Dispatch
+
+Job dispatching is region specific. While a [parameterized job] can be
+registered in multiple [federated regions] like any other job, a parameterized
+job operates much like a function definition that takes variable input.
+Operators are expected to invoke the job by invoking [`job dispatch`]
+from the CLI or the [HTTP API] and provide the appropriate dispatch options
+for that region.
+
+## Periodic Time Zones
+
+Multiregion periodic jobs share [time zone] configuration, with UTC being the
+default. Operators should be mindful of this when registering multiregion jobs.
+For example, a periodic configuration that specifies the job should run every
+night at midnight New York time, may result in an undesirable execution time
+if one of the target regions is set to Tokyo time.
+
+## `multiregion` Parameters
+
+- `strategy` <code>([Strategy](#strategy-parameters): nil)</code> - Specifies
+  a rollout strategy for the regions.
+
+- `region` <code>([Region](#region-parameters): nil)</code> - Specifies the
+  parameters for a specific region. This can be specified multiple times to
+  define the set of regions for the multiregion deployment. Regions are
+  ordered; depending on the rollout strategy Nomad may roll out to each region
+  in order or to several at a time.
+
+~> **Note:** Regions can be added, but regions that are removed will not be
+stopped and will be ignored by the deployment. This behavior may change before
+multiregion deployments are considered GA.
+
+### `strategy` Parameters
+
+- `max_parallel` `(int: <optional>)` - Specifies the maximum number
+  of region deployments that a multiregion will have in a running state at a
+  time. By default, Nomad will deploy all regions simultaneously.
+
+- `on_failure` `(string: <optional>)` - Specifies the behavior when a region
+  deployment fails. Available options are `"fail_all"`, `"fail_local"`, or
+  the default (empty `""`). This field and its interactions with the job's
+  [`update` block] is described in the [examples] below.
+
+  Each region within a multiregion deployment follows the `auto_revert`
+  strategy of its own `update` block (if any). The multiregion `on_failure`
+  field tells Nomad how many other regions should be marked as failed when one
+  region's deployment fails:
+
+  - The default behavior is that the failed region and all regions that come
+    after it in order are marked as failed.
+
+  - If `on_failure: "fail_all"` is set, all regions will be marked as
+    failed. If all regions have already completed their deployments, it's
+    possible that a region may transition from `blocked` to `successful` while
+    another region is failing. This successful region cannot be rolled back.
+
+  - If `on_failure: "fail_local"` is set, only the failed region will be marked
+    as failed. The remaining regions will move on to `blocked` status. At this
+    point, you'll need to manually unblock regions to mark them successful
+    with the [`nomad deployment unblock`] command or correct the conditions
+    that led to the failure and resubmit the job.
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) is enforced. The
+`system` scheduler will be updated to support `on_failure` when the
+[`update` block] is fully supported for system jobs in a future release.
+
+### `region` Parameters
+
+The name of a region must match the name of one of the [federated regions].
+
+- `count` `(int: <optional>)` - Specifies a count override for task groups in
+  the region. If a task group specifies a `count = 0`, its count will be
+  replaced with this value. If a task group specifies its own `count` or omits
+  the `count` field, this value will be ignored. This value must be
+  non-negative.
+
+- `datacenters` `(array<string>: <optional>)` - A list of
+  datacenters in the region which are eligible for task placement. If not
+  provided, the `datacenters` field of the job will be used.
+
+- `node_pool` `(string: <optional>)` - The node pool to be used in this region.
+  It overrides the job-level `node_pool` and the namespace default node pool.
+
+- `meta` - `Meta: nil` - The meta block allows for user-defined arbitrary
+  key-value pairs. The meta specified for each region will be merged with the
+  meta block at the job level.
+
+As described above, the parameters for each region replace the default values
+for the field with the same name for each region.
+
+## `multiregion` Examples
+
+The following examples only show the `multiregion` block and the other
+blocks it might be interacting with.
+
+### Max Parallel
+
+This example shows the use of `max_parallel`. This job will deploy first to
+the "north" and "south" regions. If either "north" finishes and enters the
+`blocked` state, then "east" will be next. At most 2 regions will be in a
+`running` state at any given time.
+
+```hcl
+multiregion {
+
+  strategy {
+    max_parallel = 2
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+```
+
+### Rollback Regions
+
+This example shows the default value of `on_failure`. Because `max_parallel = 1`,
+the "north" region will deploy first, followed by "south", and so on. But
+supposing the "east" region failed, both the "east" region and the "west"
+region would be marked `failed`. Because the job has an `update` block with
+`auto_revert=true`, both regions would then rollback to the previous job
+version. The "north" and "south" regions would remain `blocked` until an
+operator intervenes.
+
+```hcl
+multiregion {
+
+  strategy {
+    on_failure = ""
+    max_parallel = 1
+  }
+
+  region "north" {}
+  region "south" {}
+  region "east" {}
+  region "west" {}
+}
+
+update {
+  auto_revert = true
+}
+```
+
+### Override Counts
+
+This example shows how the `count` field override the default `count` of the
+task group. The job the deploys 2 "worker" and 1 "controller" allocations to
+the "west" region, and 5 "worker" and 1 "controller" task groups to the "east"
+region.
+
+```hcl
+multiregion {
+
+    region "west" {
+      count = 2
+    }
+
+    region "east" {
+      count = 5
+    }
+  }
+}
+
+group "worker" {
+  count = 0
+}
+
+group "controller" {
+  count = 1
+}
+```
+
+### Merging Meta
+
+This example shows how the `meta` is merged with the `meta` field of the job,
+group, and task. A task in "west" will have the values
+`first-key="regional-west"`, `second-key="group-level"`, whereas a task in
+"east" will have the values `first-key="job-level"`,
+`second-key="group-level"`.
+
+```hcl
+multiregion {
+
+    region "west" {
+      meta {
+        first-key = "regional-west"
+        second-key = "regional-west"
+      }
+    }
+
+    region "east" {
+      meta {
+        second-key = "regional-east"
+      }
+    }
+  }
+}
+
+meta {
+  first-key = "job-level"
+}
+
+group "worker" {
+  meta {
+    second-key = "group-level"
+  }
+}
+```
+
+[federated regions]: /nomad/tutorials/manage-clusters/federation
+[`update` block]: /nomad/docs/job-specification/update
+[update-auto-revert]: /nomad/docs/job-specification/update#auto_revert
+[examples]: #multiregion-examples
+[upgrade strategies]: /nomad/tutorials/job-updates
+[`nomad deployment unblock`]: /nomad/docs/commands/deployment/unblock
+[parameterized job]: /nomad/docs/job-specification/parameterized
+[`job dispatch`]: /nomad/docs/commands/job/dispatch
+[HTTP API]: /nomad/api-docs/jobs#dispatch-job
+[time zone]: /nomad/docs/job-specification/periodic#time_zone
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/network.mdx b/content/nomad/v1.9.x/content/docs/job-specification/network.mdx
new file mode 100644
index 0000000000..ac66412774
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/network.mdx
@@ -0,0 +1,371 @@
+---
+layout: docs
+page_title: network Block - Job Specification
+description: |-
+  The "network" block specifies the networking requirements for the task group,
+  including networking mode and port allocations.
+---
+
+# `network` Block
+
+<Placement groups={[['job', 'group', 'network']]} />
+
+The `network` block specifies the networking requirements for the task group,
+including the network mode and port allocations. When scheduling jobs in
+Nomad they are provisioned across your fleet of machines along with other jobs
+and services. Because you don't know in advance what host your job will be
+provisioned on, Nomad will provide your tasks with network configuration when
+they start up.
+
+Note that this document only applies to services that want to _listen_ on a
+port. Batch jobs or services that only make outbound connections do not need to
+allocate ports, since they will use any available interface to make an outbound
+connection.
+
+```hcl
+job "docs" {
+  group "example" {
+    network {
+      port "http" {}
+      port "https" {}
+      port "lb" {
+        static = 8889
+      }
+    }
+  }
+}
+```
+
+### Network modes
+
+When the `network` block is defined with `bridge` as the networking mode,
+all tasks in the task group share the same network namespace. This is a prerequisite for
+[Consul Connect](/nomad/docs/integrations/consul-connect). Tasks running within a
+network namespace are not visible to applications outside the namespace on the same host.
+This allows [Connect][]-enabled applications to bind only to localhost within the shared network stack,
+and use the proxy for ingress and egress traffic.
+
+To use `bridge` mode, you must have the [reference CNI
+plugins](https://github.com/containernetworking/plugins/releases/tag/v1.0.0)
+installed at the location specified by the client's [`cni_path`]
+configuration. These plugins are used to create the bridge network and
+configure the appropriate iptables rules.
+
+Network modes are only supported in allocations running on Linux clients.
+All other operating systems use the `host` networking mode.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+   network mode make sure to bind your workloads to the loopback interface
+   only. Refer to the [Bridge networking][docs_networking_bridge] documentation
+   for more information.
+
+## `network` Parameters
+
+- `mbits` <code>([_deprecated_](/nomad/docs/upgrade/upgrade-specific#nomad-0-12-0) int: 10)</code> - Specifies the bandwidth required in MBits.
+
+- `port` <code>([Port](#port-parameters): nil)</code> - Specifies a TCP/UDP port
+  allocation and can be used to specify both dynamic ports and reserved ports.
+
+- `mode` `(string: "host")` - Mode of the network. This option is only supported
+  on Linux clients. The following modes are available:
+
+  - `none` - Task group will have an isolated network without any network interfaces.
+  - `bridge` - Task group will have an isolated network namespace with an interface
+    that is bridged with the host. Note that bridge networking is only
+    currently supported for the `docker`, `exec`, `raw_exec`, and `java` task
+    drivers.
+  - `host` - Each task will join the host network namespace and a shared network
+    namespace is not created.
+  - `cni/<cni network name>` - Task group will have an isolated network namespace
+    with the network configured by CNI.
+
+- `hostname` `(string: "")` - The hostname assigned to the network namespace. This
+  is currently only supported using the [Docker driver][docker-driver] and when the
+  [mode](#mode) is set to [`bridge`](#bridge). This parameter supports
+  [interpolation](/nomad/docs/runtime/interpolation).
+
+- `dns` <code>([DNSConfig](#dns-parameters): nil)</code> - Sets the DNS
+  configuration for the allocations. By default all task drivers will inherit
+  DNS configuration from the client host. DNS configuration is only supported on
+  Linux clients at this time. Note that if you are using a `mode="cni/*`, these
+  values will override any DNS configuration the CNI plugins return.
+- `cni` <code>([CNIConfig](#cni-parameters): nil)</code> - Sets the custom CNI
+  arguments for a network configuration per allocation, for use with `mode="cni/*`.
+
+### `port` Parameters
+
+- `static` `(int: nil)` - Specifies the static TCP/UDP port to allocate. If omitted, a
+  dynamic port is chosen. We **do not recommend** using static ports, except
+  for `system` or specialized jobs like load balancers.
+- `to` `(string:nil)` - Applicable when using "bridge" mode to configure port
+  to map to inside the task's network namespace. Omitting this field or
+  setting it to `-1` sets the mapped port equal to the dynamic port allocated
+  by the scheduler. The `NOMAD_PORT_<label>` environment variable will contain
+  the `to` value.
+- `host_network` `(string:nil)` - Designates the host network name to use when allocating
+  the port. When port mapping the host port will only forward traffic to the matched host
+  network address.
+- `ignore_collision` `(bool: false)` - Allows the group to be placed on a node
+  where the port may already be reserved. Intended for programs that support
+  `SO_REUSEPORT` unix socket option, so more than one instance of the program
+  may bind to the same port. Only compatible with [`host`](#host) network mode
+  and `static` ports. Some task drivers (e.g. docker) may also require setting
+  `network_mode = "host"` (or similar) to avoid runtime errors after placement.
+
+The label assigned to the port is used to identify the port in service
+discovery, and used in the name of the environment variable that indicates
+which port your application should bind to. For example:
+
+```hcl
+port "foo" {}
+```
+
+When the task starts, it will be passed the following environment variables:
+
+- <tt>NOMAD_IP_foo</tt> - The IP to bind on for the given port label.
+- <tt>NOMAD_PORT_foo</tt> - The port value for the given port label.
+- <tt>NOMAD_ADDR_foo</tt> - A combined <tt>ip:port</tt> that can be used for convenience.
+
+The label of the port is just text - it has no special meaning to Nomad.
+
+## `dns` Parameters
+
+- `servers` `(array<string>: nil)` - Sets the DNS nameservers the allocation uses for name resolution.
+- `searches` `(array<string>: nil)` - Sets the search list for hostname lookup
+- `options` `(array<string>: nil)` - Sets internal resolver variables.
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `cni` Parameters
+
+- `args` `(map<string><string>: nil)` - Sets CNI arguments for network configuration.
+   These get turned into `CNI_ARGS` per the
+   [CNI spec](https://www.cni.dev/docs/spec/#parameters).
+
+These parameters support [interpolation](/nomad/docs/runtime/interpolation).
+
+## `network` Examples
+
+The following examples only show the `network` blocks. Remember that the
+`network` block is only valid in the placements listed above.
+
+### Dynamic Ports
+
+This example specifies a dynamic port allocation for the port labeled "http".
+Dynamic ports are allocated in a range from `20000` to `32000`.
+
+Most services run in your cluster should use dynamic ports. This means that the
+port will be allocated dynamically by the scheduler, and your service will have
+to read an environment variable to know which port to bind to at startup.
+
+```hcl
+group "example" {
+  network {
+    port "http" {}
+    port "https" {}
+  }
+}
+```
+
+```hcl
+network {
+  port "http" {}
+}
+```
+
+### Static Ports
+
+Static ports place your job on a host where the port is not already reserved
+by another job with the same port.
+
+This example specifies a static port allocation for the port labeled "lb".
+
+```hcl
+network {
+  port "lb" {
+    static = 6539
+  }
+}
+```
+
+For programs that support the `SO_REUSEPORT` unix socket option,
+you may set `ignore_collision = true` to place multiple copies on a single node.
+
+### Mapped Ports
+
+Some drivers (such as [Docker][docker-driver] and [QEMU][qemu-driver]) allow you
+to map ports. A mapped port means that your application can listen on a fixed
+port (it does not need to read the environment variable) and the dynamic port
+will be mapped to the port in your container or virtual machine.
+
+```hcl
+group "app" {
+  network {
+    port "http" {
+      to = 8080
+    }
+  }
+
+  task "example" {
+    driver = "docker"
+
+    config {
+      ports = ["http"]
+    }
+  }
+}
+```
+
+The above example is for the Docker driver. The service is listening on port
+`8080` inside the container. The driver will automatically map the dynamic port
+to this service.
+
+When the task is started, it is passed an additional environment variable named
+`NOMAD_HOST_PORT_http` which indicates the host port that the HTTP service is
+bound to.
+
+### Bridge Mode
+
+Bridge mode allows compatible tasks to share a networking stack and interfaces. Nomad
+can then do port mapping without relying on individual task drivers to implement port
+mapping configuration.
+
+The following example is a group level network block that uses bridge mode
+and port mapping.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    static = 9002
+    to     = 9002
+  }
+}
+```
+
+Using bridge mode can result in failing outbound network requests on hosts that have
+[firewalld](https://firewalld.org) enabled. This includes most RHEL-based Linux distributions
+like CentOS, Rocky Linux or Oracle Linux. One solution for firewalld to allow network
+requsts coming from Nomad jobs is to mark the `nomad` bridge interface as trusted.
+
+```shell-session
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad
+$ sudo firewall-cmd --zone=trusted --add-interface=nomad --permanent
+```
+
+It is necessary to restart the affected jobs afterwards for them to be able to access
+the network. Further details can be found in Docker's documentation under [Docker and iptables](https://docs.docker.com/network/iptables/#integration-with-firewalld).
+
+### DNS
+
+The following example configures the allocation to use Google's DNS resolvers 8.8.8.8 and 8.8.4.4.
+
+```hcl
+network {
+  dns {
+    servers = ["8.8.8.8", "8.8.4.4"]
+  }
+}
+```
+
+### Container Network Interface (CNI)
+
+Nomad supports CNI by fingerprinting each node for [CNI network configurations](https://github.com/containernetworking/cni/blob/v0.8.0/SPEC.md#network-configuration).
+These are associated to the node by the `name` field of the CNI configuration.
+The `name` can then be used when setting the network `mode` field in the form of `cni/<name>`.
+
+As an example if the following CNI configuration was on a node the proceeding network block could be used.
+
+```json
+{
+  "cniVersion": "0.3.1",
+  "name": "mynet",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "172.16.30.0/24",
+        "routes": [
+          {
+            "dst": "0.0.0.0/0"
+          }
+        ]
+      }
+    },
+    {
+      "type": "portmap",
+      "capabilities": { "portMappings": true }
+    }
+  ]
+}
+```
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+The Nomad client will build the correct [capabilities arguments](https://github.com/containernetworking/cni/blob/v0.8.0/CONVENTIONS.md#well-known-capabilities) for the portmap plugin based on the defined port blocks.
+
+### CNI Args
+
+The following example specifies CNI args for the custom CNI plugin specified above.
+
+```hcl
+network {
+  mode = "cni/mynet"
+  port "http" {
+    to = 8080
+  }
+  cni {
+    args = {
+     "nomad.region" : "${node.region}"
+    }
+  }
+}
+```
+
+### Host Networks
+
+In some cases a port should only be allocated to a specific interface or address on the host.
+The `host_network` field of a port will constrain port allocation to a single named host network.
+If `host_network` is set for a port, Nomad will schedule the allocations on a node which has defined a `host_network` with the given name.
+If not set the "default" host network is used which is commonly the address with a default route associated with it.
+
+When Nomad does port mapping for ports with a defined `host_network`, the port mapping rule will use the host address as the destination address.
+
+```hcl
+network {
+  mode = "bridge"
+
+  # define a port to use for public https traffic
+  port "https" {
+    static       = 443
+    to           = 8080
+    host_network = "public"
+  }
+  # define a port that is only exposed to private traffic
+  port "admin" {
+    to           = 9000
+    host_network = "private"
+  }
+}
+```
+
+### Limitations
+
+- Only one `network` block can be specified, when it is defined at the task group level.
+- Only the `NOMAD_PORT_<label>` and `NOMAD_HOST_PORT_<label>` environment
+  variables are set for group network ports.
+
+[docs_networking_bridge]: /nomad/docs/networking#bridge-networking
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[qemu-driver]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[`cni_path`]: /nomad/docs/configuration/client#cni_path
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/numa.mdx b/content/nomad/v1.9.x/content/docs/job-specification/numa.mdx
new file mode 100644
index 0000000000..598588d9a1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/numa.mdx
@@ -0,0 +1,107 @@
+---
+layout: docs
+page_title: numa Block - Job Specification
+description: |-
+  The "numa" block is used configure NUMA aware scheduling strategy for a task.
+---
+
+# `numa` Block
+
+<Placement groups={['job', 'group', 'task', 'resources', 'numa']} />
+
+The `numa` block is used to configure how Nomad will assign CPU cores for a task
+while taking the [NUMA hardware topology][numa_wiki] of a node into consideration.
+Workloads that are sensitive to memory latency can perform significantly better
+when pinned to CPU cores on the same NUMA node.
+
+<EnterpriseAlert>
+
+This functionality only exists in Nomad Enterprise. This is not
+present in the source available version of Nomad.
+</EnterpriseAlert>
+
+<Note>
+
+NUMA aware scheduling is currently limited to Linux.
+</Note>
+
+```hcl
+job "example" {
+  group "group" {
+    task "task" {
+      resources {
+        cores = 8
+        numa {
+          affinity = "require"
+        }
+      }
+    }
+  }
+}
+```
+
+In the example above, the task is requesting Nomad to reserve 8 CPU cores, all
+of which must be colocated on the same hardware NUMA node. The Nomad scheduler
+will ensure the task is placed on a Nomad node with sufficient unused CPU cores
+in a compatible configuration.
+
+Configuring the `numa` block requires the task specifies CPU resources using
+the [`cores`][cores] parameter.
+
+# `numa` Parameters
+
+- `affinity` `(string: "none")` - Specifies the strategy Nomad will use when
+  selecting CPU cores to assign to a task. Possible values are `"none"`,
+  `"prefer"`, or `"require"`.
+  - `none` - Nomad is free to allocate CPU cores using any strategy. Nomad uses
+  this freedom to allocate cores in such a way that minimizes the amount of
+  fragmentation of core availability per NUMA node. It does so by bin-packing
+  the chosen cores onto the NUMA nodes with the fewest number of cores available.
+  - `prefer` - Nomad will select the set of CPU cores on a node that minimizes
+  the total distance between those cores, but does not limit those CPU core
+  selections to come from a single NUMA node.
+  - `require` - Nomad will select a set of CPU cores that are strictly colocated
+  on the same hardware NUMA node. If there are no Nomad nodes with a sufficient
+  number of available cores in a compatible configuration, task placement will
+  fail due to exhausted resources.
+
+- `devices` `(list<string>: nil)` - Specifies which devices must be colocated on
+  the name NUMA node, along with allocated CPU cores. Must be a subset of the
+  devices listed in the [resources] block. May only be used with `affinity` set
+  to `require`.
+
+<Note>
+
+  The `require` affinity option causes fragmentation of available CPU cores
+  based on the NUMA node the selected cores are associated with. Use it for
+  workloads known to be highly sensitive to memory latencies. A cluster where
+  all jobs make use of the `require` affinity option will not be able to make
+  efficient use of available resources.
+</Note>
+
+## `numa` Examples
+
+This example will allocate a `1080ti` GPU and ensure it is on the same NUMA node
+as the 4 CPU cores reserved for the task.
+
+```hcl
+resources {
+  cores  = 4
+  memory = 2048
+
+  device "nvidia/gpu/1080ti" {
+    count = 1
+  }
+
+  numa {
+    affinity = "require"
+    devices = [
+      "nvidia/gpu/1080ti"
+    ]
+  }
+}
+```
+
+[numa_wiki]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
+[cores]: /nomad/docs/job-specification/resources#cores
+[resources]: /nomad/docs/job-specification/resources
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/parameterized.mdx b/content/nomad/v1.9.x/content/docs/job-specification/parameterized.mdx
new file mode 100644
index 0000000000..ec0515c8ce
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/parameterized.mdx
@@ -0,0 +1,221 @@
+---
+layout: docs
+page_title: parameterized Block - Job Specification
+description: |-
+  A parameterized job is used to encapsulate a set of work that can be carried
+  out on various inputs much like a function definition. When the
+  `parameterized` block is added to a job, the job acts as a function to the
+  cluster as a whole.
+---
+
+# `parameterized` Block
+
+<Placement groups={['job', 'parameterized']} />
+
+A parameterized job is used to encapsulate a set of work that can be carried out
+on various inputs much like a function definition. When the `parameterized`
+block is added to a job, the job acts as a function to the cluster as a whole.
+
+The `parameterized` block allows job operators to configure a job that carries
+out a particular action, define its resource requirements and configure how
+inputs and configuration are retrieved by the tasks within the job.
+
+To invoke a parameterized job, [`nomad job dispatch`][dispatch command] or the equivalent HTTP APIs are
+used. When dispatching against a parameterized job, an opaque payload and
+metadata may be injected into the job. These inputs to the parameterized job act
+like arguments to a function. The job consumes them to change its behavior,
+without exposing the implementation details to the caller.
+
+To that end, tasks within the job can add a
+[`dispatch_payload`][dispatch_payload] block that
+defines where on the filesystem this payload gets written to. An example payload
+would be a task's JSON configuration.
+
+Further, certain metadata may be marked as required when dispatching a job so it
+can be used to inject configuration directly into a task's arguments using
+[interpolation]. An example of this would be to require a run ID key that
+could be used to lookup the work the job is suppose to do from a management
+service or database.
+
+Each time a job is dispatched, a unique job ID is generated. This
+allows a caller to track the status of the job, much like a future or
+promise in some programming languages. The dispatched job cannot be
+updated after dispatching; to update the job definition you need to
+update the parent job.
+
+```hcl
+job "docs" {
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+}
+```
+
+See the [multiregion] documentation for additional considerations when
+dispatching parameterized jobs.
+
+## `parameterized` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+
+## `parameterized` Parameters
+
+- `meta_optional` `(array<string>: nil)` - Specifies the set of metadata keys that
+  may be provided when dispatching against the job.
+
+- `meta_required` `(array<string>: nil)` - Specifies the set of metadata keys that
+  must be provided when dispatching against the job.
+
+- `payload` `(string: "optional")` - Specifies the requirement of providing a
+  payload when dispatching against the parameterized job. The **maximum size of a
+  `payload` is 16 KiB**. The options for this
+  field are:
+
+  - `"optional"` - A payload is optional when dispatching against the job.
+
+  - `"required"` - A payload must be provided when dispatching against the job.
+
+  - `"forbidden"` - A payload is forbidden when dispatching against the job.
+
+## `parameterized` Examples
+
+The following examples show non-runnable example parameterized jobs:
+
+### Required Inputs
+
+This example shows a parameterized job that requires both a payload and
+metadata:
+
+```hcl
+job "video-encode" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+  }
+
+  group "encode" {
+    # ...
+
+    task "ffmpeg" {
+      driver = "exec"
+
+      config {
+        command = "ffmpeg-wrapper"
+
+        # When dispatched, the payload is written to a file that is then read by
+        # the created task upon startup
+        args = ["-config=${NOMAD_TASK_DIR}/config.json"]
+      }
+
+      dispatch_payload {
+        file = "config.json"
+      }
+    }
+  }
+}
+```
+
+### Metadata Interpolation
+
+```hcl
+job "email-blast" {
+  # ...
+
+  type = "batch"
+
+  parameterized {
+    payload       = "forbidden"
+    meta_required = ["CAMPAIGN_ID"]
+  }
+
+  group "emails" {
+    # ...
+
+    task "emailer" {
+      driver = "exec"
+
+      config {
+        command = "emailer"
+
+        # The campaign ID is interpolated and injected into the task's
+        # arguments
+        args = ["-campaign=${NOMAD_META_CAMPAIGN_ID}"]
+      }
+    }
+  }
+}
+```
+
+### Use periodic with parameterized
+
+Nomad uses an internal hierarchy when scheduling a job that is both `parameterized` and [`periodic`][periodic].
+
+```plaintext
+parameterized => periodic => batch
+```
+
+Nomad processes a periodic with parameterized job in the following order:
+
+1. Nomad does not dispatch a periodic job with null parameters in the periodic configuration. This forces the parameterized job to take precedence over the periodic job.
+2. After Nomad dispatches the parameterized job and gives it parameters, Nomad uses the periodic configuration.
+3. Nomad dispatches new jobs according to the periodic configuration that uses thee parameters from the triggering parameterized job.
+
+In this example, the periodic job does not trigger any new jobs 
+until the operator dispatches the parameterized job at least once. After that, the 
+dispatched child periodically triggers more children with the given parameters. 
+
+```hcl
+  periodic {
+    crons = [
+      "*/40 * * * * * *"
+    ]
+  }
+  parameterized {
+    payload       = "required"
+    meta_required = ["dispatcher_email"]
+    meta_optional = ["pager_email"]
+  }
+```
+
+
+
+There are three columns plus comments in this example output, which is for the preceding periodic, parameterized example job. Scroll to the last column to review the comments.
+
+```
+$ nomad job status                                                      
+ID                                                     Type                            Submit Date
+sync                                                   batch/periodic/parameterized    2024-11-07T10:43:30+01:00 // Original submitted job
+sync/dispatch-1730972650-247c6e97                      batch/periodic                  2024-11-07T10:44:10+01:00 // First dispatched job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972680  batch                           2024-11-07T10:44:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972650-247c6e97/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters A
+sync/dispatch-1730972760-f79a96e1                      batch/periodic                  2024-11-07T10:46:00+01:00 // Second dispatched job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972800  batch                           2024-11-07T10:46:40+01:00 // Cron job with parameters B
+sync/dispatch-1730972760-f79a96e1/periodic-1730972860  batch                           2024-11-07T10:47:40+01:00 // Cron job with parameters B
+```
+The output illustrates the following:
+
+1. The `sync` job is the parameterized and periodic job. However, Nomad doesn't run the periodic job until you submit with the required parameters.
+2. The `sync/dispatch-1730972650-247c6e97` job contains parameters and triggers the batch jobs, named `sync/dispatch-1730972650-247c6e97/periodic-1730972680` and `sync/dispatch-1730972650-247c6e97/periodic-1730972860`.
+3. The `sync/dispatch-1730972760-f79a96e1` job assigns new parameters and triggers new batch jobs that use those parameters.
+
+If you need to force the periodic job, force the the corresponding parameterized job.
+
+This example forces the first dispatched job with parameters A from the preceding example.
+
+```
+$ nomad job periodic force sync/dispatch-1730972650-247c6e97 
+```
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[dispatch command]: /nomad/docs/commands/job/dispatch 'Nomad Job Dispatch Command'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[dispatch_payload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[multiregion]: /nomad/docs/job-specification/multiregion#parameterized-dispatch
+[periodic]: /nomad/docs/job-specification/periodic
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/periodic.mdx b/content/nomad/v1.9.x/content/docs/job-specification/periodic.mdx
new file mode 100644
index 0000000000..9a38208d39
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/periodic.mdx
@@ -0,0 +1,121 @@
+---
+layout: docs
+page_title: periodic Block - Job Specification
+description: |-
+  The "periodic" block allows a job to run at fixed times, dates, or intervals.
+  The easiest way to think about the periodic scheduler is "Nomad cron" or
+  "distributed cron".
+---
+
+# `periodic` Block
+
+<Placement groups={['job', 'periodic']} />
+
+The `periodic` block allows a job to run at fixed times, dates, or intervals.
+The easiest way to think about the periodic scheduler is "Nomad cron" or
+"distributed cron".
+
+```hcl
+job "docs" {
+  periodic {
+    cron             = "*/15 * * * * *"
+    prohibit_overlap = true
+  }
+}
+```
+
+The periodic expression by default evaluates in the **UTC timezone** to ensure
+consistent evaluation when Nomad spans multiple time zones.
+
+## `periodic` Requirements
+
+- The job's [scheduler type][batch-type] must be `batch` or `sysbatch`.
+- A job can not be updated to be periodically. Thus, to transition an existing job to be periodic, you must first run `nomad stop -purge «job name»`. This is expected behavior and is to ensure that this change has been intentionally made by an operator.
+
+Refer to the [parameterized] documentation for how to use parameters with a periodic job.
+
+## `periodic` Parameters
+
+- `cron` (_deprecated_: Replaced by `crons` in 1.6.2) `(string)` - Specifies a cron expression configuring the
+  interval to launch the job. In addition to [cron-specific formats][cron], this
+  option also includes predefined expressions such as `@daily` or `@weekly`. Either `cron` or `crons` must be set, but not both.
+
+- `crons` - A list of cron expressions configuring the intervals the job is
+  launched at. The job runs at the next earliest time that matches any of the
+  expressions. Supports predefined expressions such as `@daily` and
+  `@weekly`. Refer to [the
+  documentation](https://github.com/hashicorp/cronexpr#implementation) for full
+  details about the supported cron specs and the predefined expressions. Either `cron` or `crons` must be set, but not both.
+
+- `prohibit_overlap` `(bool: false)` - Specifies if this job should wait until
+  previous instances of this job have completed. This only applies to this job;
+  it does not prevent other periodic jobs from running at the same time.
+
+- `time_zone` `(string: "UTC")` - Specifies the time zone to evaluate the next
+  launch interval against. [Daylight Saving Time][dst] affects scheduling, so
+  please ensure the [behavior below][dst] meets your needs. The time zone must
+  be parsable by Golang's
+  [LoadLocation](https://golang.org/pkg/time/#LoadLocation).
+
+- `enabled` `(bool: true)` - Specifies if this job should run. This not only
+  prevents this job from running on the `cron` schedule but prevents force
+  launches.
+
+## `periodic` Examples
+
+The following examples only show the `periodic` blocks. Remember that the
+`periodic` block is only valid in the placements listed above.
+
+### Run Daily
+
+This example shows running a periodic job daily:
+
+```hcl
+periodic {
+  cron = "@daily"
+}
+```
+
+### Set Time Zone
+
+This example shows setting a time zone for the periodic job to evaluate in:
+
+```hcl
+periodic {
+  cron      = "*/15 * * * * *"
+  time_zone = "America/New_York"
+}
+```
+
+### Run multiple crons
+
+```hcl
+periodic {
+  crons = [
+    "*/5 * * *",
+    "*/7 * * *"
+  ]
+  time_zone = "America/New_York"
+}
+```
+
+## Daylight Saving Time
+
+Though Nomad supports configuring `time_zone`, we strongly recommend that periodic
+jobs are specified with respect to UTC `time_zone`. Only customize `time_zone`
+when the following daylight saving time behavior is _desired:_
+
+- When leaping forward, periodic jobs scheduled for the skipped hour (eg 2:30am
+  in `America/New_York`) will be _skipped_ for that day (eg March 10th).
+
+- When falling back, periodic jobs scheduled for the duplicated hour (eg 1:30am
+  in `America/New_York`) will be _run twice_ for that day (eg November 3rd).
+
+See the [multiregion] documentation for additional considerations when
+configuring time zones for periodic jobs.
+
+[batch-type]: /nomad/docs/job-specification/job#type 'Batch scheduler type'
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[dst]: #daylight-saving-time
+[multiregion]: /nomad/docs/job-specification/multiregion#periodic-time-zones
+[parameterized]: /nomad/docs/job-specification/parameterized#use-periodic-with-parameterized
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/proxy.mdx b/content/nomad/v1.9.x/content/docs/job-specification/proxy.mdx
new file mode 100644
index 0000000000..5b95f5f2f9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/proxy.mdx
@@ -0,0 +1,111 @@
+---
+layout: docs
+page_title: proxy Block - Job Specification
+description: |-
+  The "proxy" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `proxy` Block
+
+<Placement
+  groups={['job', 'group', 'service', 'connect', 'sidecar_service', 'proxy']}
+/>
+
+The `proxy` block allows configuring various options for the sidecar proxy
+managed by Nomad for [Consul Connect][]. It is valid only within the context of
+a `sidecar_service` block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {
+          proxy {}
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `proxy` Parameters
+
+- `config` `(map: nil)` - Proxy configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation][envoy_dynamic_config]
+  for details. Keys and values support [runtime variable interpolation][].
+- `expose` <code>([expose]: nil)</code> - Used to configure expose path
+  configuration for Envoy. See Consul's [Expose Paths Configuration
+  Reference][expose_path_ref] for more information.
+- `local_service_address` `(string: "127.0.0.1")` - The address the local
+  service binds to. Useful to customize in clusters with mixed Connect and
+  non-Connect services.
+- `local_service_port` `(int: <varies>)` - The port the local service binds to.
+  Usually the same as the parent service's port, it is useful to customize in
+  clusters with mixed Connect and non-Connect services.
+- `transparent_proxy` <code>([transparent_proxy][]: nil)</code> - Used to enable
+  [transparent proxy][tproxy] mode, which allows the proxy to use Consul service
+  intentions to automatically configure upstreams, and configures iptables rules
+  to force traffic from the allocation to flow through the proxy.
+- `upstreams` <code>([upstreams][]: nil)</code> - Used to configure details of
+  each upstream service that this sidecar proxy communicates with.
+
+## `proxy` Examples
+
+The following example is a proxy specification that includes upstreams
+configuration.
+
+```hcl
+sidecar_service {
+  proxy {
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port  = 8080
+    }
+  }
+}
+```
+
+The following example is a proxy specification that includes transparent proxy
+configuration. Note that with transparent proxy, you will not need to configure
+an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+[Consul Connect]: /nomad/docs/integrations/consul-connect
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[runtime variable interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[expose]: /nomad/docs/job-specification/expose 'Nomad proxy expose configuration'
+[envoy_dynamic_config]: /consul/docs/connect/proxies/envoy#dynamic-configuration
+[expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
+[transparent_proxy]: /nomad/docs/job-specification/transparent_proxy
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/reschedule.mdx b/content/nomad/v1.9.x/content/docs/job-specification/reschedule.mdx
new file mode 100644
index 0000000000..f436ef63c5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/reschedule.mdx
@@ -0,0 +1,143 @@
+---
+layout: docs
+page_title: reschedule Block - Job Specification
+description: >-
+  The "reschedule" block specifies the group's rescheduling strategy upon
+
+  allocation failures. Nomad will only attempt to reschedule failed allocations
+  on
+
+  to another node only after any local
+  [restarts](/nomad/docs/job-specification/restart)
+
+  have been exceeded.
+---
+
+# `reschedule` Block
+
+<Placement
+  groups={[
+    ['job', 'reschedule'],
+    ['job', 'group', 'reschedule'],
+  ]}
+/>
+
+The `reschedule` block specifies the group's rescheduling strategy. If specified
+at the job level, the configuration will apply to all groups within the job. If
+the reschedule block is present on both the job and the group, they are merged
+with the group block taking the highest precedence and then the job.
+
+Nomad will attempt to schedule the allocation on another node if any of its task
+statuses become `failed`. The scheduler prefers to create a replacement
+allocation on a node that was not used by a previous allocation.
+
+Rescheduling happens when the Nomad agent fails to set up the allocation or the
+tasks of an allocation fail more than their [`restart`][] block allows. When a
+node is drained, Nomad [migrates][] the allocations instead and ignores the
+`reschedule` block. When a node is lost, Nomad [replaces][] the allocations
+instead and ignores the `reschedule` block.
+
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts       = 15
+      interval       = "1h"
+      delay          = "30s"
+      delay_function = "exponential"
+      max_delay      = "120s"
+      unlimited      = false
+    }
+  }
+}
+```
+
+~> The reschedule block does not apply to `system` or `sysbatch` jobs because
+they run on every node.
+
+## `reschedule` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of reschedule attempts
+  allowed in the configured interval. Defaults vary by job type, see below
+  for more information.
+
+- `interval` `(string: <varies>)` - Specifies the sliding window which begins
+  when the first reschedule attempt starts and ensures that only `attempts`
+  number of reschedule happen within it. If more than `attempts` number of
+  failures happen with this interval, Nomad will not reschedule any more.
+
+- `delay` `(string: <varies>)` - Specifies the duration to wait before attempting
+  to reschedule a failed task. This is specified using a label suffix like "30s" or "1h".
+  Delay cannot be less than 5 seconds.
+
+- `delay_function` `(string: <varies>)` - Specifies the function that is used to
+  calculate subsequent reschedule delays. The initial delay is specified by the delay parameter.
+  `delay_function` has three possible values which are described below.
+
+  - `constant` - The delay between reschedule attempts stays constant at the `delay` value.
+  - `exponential` - The delay between reschedule attempts doubles.
+  - `fibonacci` - The delay between reschedule attempts is calculated by adding the two most recent
+    delays applied. For example if `delay` is set to 5 seconds, the next five reschedule attempts will be
+    delayed by 5 seconds, 5 seconds, 10 seconds, 15 seconds, and 25 seconds respectively.
+
+- `max_delay` `(string: <varies>)` - is an upper bound on the delay beyond which it will not increase. This parameter
+  is used when `delay_function` is `exponential` or `fibonacci`, and is ignored when `constant` delay is used.
+
+- `unlimited` `(boolean:<varies>)` - `unlimited` enables unlimited reschedule attempts. If this is
+  set to `true` the `attempts` and `interval` fields are not used. The [`progress_deadline`][]
+  parameter within the update block is still adhered to when this is set to `true`, meaning no more
+  reschedule attempts are triggered once the [`progress_deadline`][] is reached.
+
+Information about reschedule attempts are displayed in the CLI and API for
+allocations. Rescheduling is enabled by default for service and batch jobs
+with the options shown below.
+
+### `reschedule` Parameter Defaults
+
+The values for the `reschedule` parameters vary by job type. Below are the
+defaults by job type:
+
+- The default batch reschedule policy is:
+
+  ```hcl
+  reschedule {
+    attempts       = 1
+    interval       = "24h"
+    unlimited      = false
+    delay          = "5s"
+    delay_function = "constant"
+  }
+  ```
+
+- The default service reschedule policy is:
+
+  ```hcl
+  reschedule {
+   delay          = "30s"
+   delay_function = "exponential"
+   max_delay      = "1h"
+   unlimited      = true
+  }
+  ```
+
+### Disabling rescheduling
+
+To disable rescheduling, set the `attempts` parameter to zero and `unlimited` to false.
+
+```hcl
+job "docs" {
+  group "example" {
+    reschedule {
+      attempts  = 0
+      unlimited = false
+    }
+  }
+}
+```
+
+[`progress_deadline`]: /nomad/docs/job-specification/update#progress_deadline
+[`restart`]: /nomad/docs/job-specification/restart
+[migrates]: /nomad/docs/job-specification/migrate
+[replaces]: /nomad/docs/job-specification/disconnect#replace
+[reschedules]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/resources.mdx b/content/nomad/v1.9.x/content/docs/job-specification/resources.mdx
new file mode 100644
index 0000000000..21c3c66259
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/resources.mdx
@@ -0,0 +1,162 @@
+---
+layout: docs
+page_title: resources Block - Job Specification
+description: |-
+  The "resources" block describes the requirements a task needs to execute.
+  Resource requirements include memory, cpu, and more.
+---
+
+# `resources` Block
+
+<Placement groups={['job', 'group', 'task', 'resources']} />
+
+The `resources` block describes the requirements a task needs to execute.
+Resource requirements include memory, CPU, and more.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      resources {
+        cpu    = 100
+        memory = 256
+
+        device "nvidia/gpu" {
+          count = 2
+        }
+      }
+    }
+  }
+}
+```
+
+## `resources` Parameters
+
+- `cpu` `(int: 100)` - Specifies the CPU required to run this task in MHz.
+
+- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
+  to reserve specifically for the task. This may not be used with `cpu`. The behavior
+  of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
+
+- `memory` `(int: 300)` - Specifies the memory required in MB.
+
+- `memory_max` <code>(`int`: &lt;optional&gt;)</code> - Optionally, specifies the
+  maximum memory the task may use, if the client has excess memory capacity, in MB.
+  See [Memory Oversubscription](#memory-oversubscription) for more details.
+
+- `numa` <code>([Numa][]: &lt;optional&gt;)</code> - Specifies the
+  NUMA scheduling preference for the task. Requires the use of `cores`.
+
+- `device` <code>([Device][]: &lt;optional&gt;)</code> - Specifies the device
+  requirements. This may be repeated to request multiple device types.
+
+- `secrets` <code>(`int`: &lt;optional&gt;)</code> - Specifies the size of the
+  [`secrets/`][] directory in MB, on platforms where the directory is a
+  tmpfs. If set, the scheduler adds the `secrets` value to the `memory` value
+  when allocating resources on a client, and this value will be included in the
+  allocated resources shown by the `nomad alloc status` and `nomad node status`
+  commands. If unset, the client will allocate 1 MB of tmpfs space and it will
+  not be counted for scheduling purposes or included in allocated resources. You
+  should not set this value if the workload will be placed on a platform where
+  tmpfs is unsupported, because it will still be counted for scheduling
+  purposes.
+
+## `resources` Examples
+
+The following examples only show the `resources` blocks. Remember that the
+`resources` block is only valid in the placements listed above.
+
+### Cores
+
+This example specifies that the task requires 2 reserved cores. With this block, Nomad will find
+a client with enough spare capacity to reserve 2 cores exclusively for the task. Unlike the `cpu` field, the
+task will not share cpu time with any other tasks managed by Nomad on the client.
+
+```hcl
+resources {
+  cores = 2
+}
+```
+
+If `cores` and `cpu` are both defined in the same resource block, validation of the job will fail.
+
+### Memory
+
+This example specifies the task requires 2 GB of RAM to operate. 2 GB is the
+equivalent of 2048 MB:
+
+```hcl
+resources {
+  memory = 2048
+}
+```
+
+### Devices
+
+This example shows a device constraints as specified in the [device][] block
+which require two nvidia GPUs to be made available:
+
+```hcl
+resources {
+  device "nvidia/gpu" {
+    count = 2
+  }
+}
+```
+## Memory Oversubscription
+
+Setting task memory limits requires balancing the risk of interrupting tasks
+against the risk of wasting resources. If a task memory limit is set too low,
+the task may exceed the limit and be interrupted; if the task memory is too
+high, the cluster is left underutilized.
+
+To help maximize cluster memory utilization while allowing a safety margin for
+unexpected load spikes, Nomad allows job authors to set two separate memory
+limits:
+
+* `memory`: the reserve limit to represent the task’s typical memory usage —
+  this number is used by the Nomad scheduler to reserve and place the task
+
+* `memory_max`: the maximum memory the task may use, if the client has excess
+  available memory, and may be terminated if it exceeds
+
+If a client's memory becomes contended or low, the operating system will
+pressure the running tasks to free up memory. If the contention persists, Nomad
+may kill oversubscribed tasks and reschedule them to other clients. The exact
+mechanism for memory pressure is specific to the task driver, operating system,
+and application runtime.
+
+The `memory_max` limit attribute is currently supported by the official
+`raw_exec`, `exec2`, `exec`, `docker`, `podman`, and `java` task drivers.  Consult the
+documentation of community-supported task drivers for their memory
+oversubscription support.
+
+Memory oversubscription is opt-in. Nomad operators can enable [Memory
+Oversubscription in the scheduler configuration][api_sched_config]. Enterprise
+customers can use [Resource Quotas][quota_spec] to limit the memory
+oversubscription and enable or disable memory oversubscription per [node
+pool][np_sched_config].
+
+To avoid degrading the cluster experience, we recommend examining and monitoring
+resource utilization and considering the following suggestions:
+
+* Set `oom_score_adj` for Linux host services that aren't managed by Nomad, e.g.
+  Docker, logging services, and the Nomad agent itself. For Systemd services, you can use the [`OOMScoreAdj` field](https://github.com/hashicorp/nomad/blob/v1.0.0/dist/systemd/nomad.service#L25).
+
+* Monitor hosts for memory utilization and set alerts on Out-Of-Memory errors
+
+* Set the [client `reserved`](/nomad/docs/configuration/client#reserved) with enough
+  memory for host services that aren't managed by Nomad as well as a buffer
+  for the memory excess. For example, if the client reserved memory is 1GB,
+  the allocations on the host may exceed their soft memory limit by almost
+  1GB in aggregate before the memory becomes contended and allocations get
+  killed.
+
+[api_sched_config]: /nomad/api-docs/operator/scheduler#update-scheduler-configuration
+[device]: /nomad/docs/job-specification/device 'Nomad device Job Specification'
+[docker_cpu]: /nomad/docs/drivers/docker#cpu
+[exec_cpu]: /nomad/docs/drivers/exec#cpu
+[np_sched_config]: /nomad/docs/other-specifications/node-pool#memory_oversubscription_enabled
+[quota_spec]: /nomad/docs/other-specifications/quota
+[numa]: /nomad/docs/job-specification/numa 'Nomad NUMA Job Specification'
+[`secrets/`]: /nomad/docs/runtime/environment#secrets
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/restart.mdx b/content/nomad/v1.9.x/content/docs/job-specification/restart.mdx
new file mode 100644
index 0000000000..1803d72dc7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/restart.mdx
@@ -0,0 +1,196 @@
+---
+layout: docs
+page_title: restart Block - Job Specification
+description: The "restart" block configures a group's behavior on task failure.
+---
+
+# `restart` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'restart'],
+    ['job', 'group', 'task', 'restart'],
+  ]}
+/>
+
+The `restart` block configures a task's behavior on task failure. Restarts
+happen on the client that is running the task. Restarts are different from
+[rescheduling][], which happens when the tasks run out of restart attempts.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 3
+      delay    = "30s"
+    }
+  }
+}
+```
+
+If specified at the group level, the configuration is inherited by all
+tasks in the group, including any [sidecar tasks][sidecar_task]. If
+also present on the task, the policy is merged with the restart policy
+from the encapsulating task group.
+
+For example, assuming that the task group restart policy is:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 2
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+and the individual task restart policy is:
+
+```hcl
+restart {
+  attempts = 5
+}
+```
+
+then the effective restart policy for the task will be:
+
+```hcl
+restart {
+  interval         = "30m"
+  attempts         = 5
+  delay            = "15s"
+  mode             = "fail"
+  render_templates = true
+}
+```
+
+Because sidecar tasks don't accept a `restart` block, it's recommended
+that you set the `restart` for jobs with sidecar tasks at the task
+level, so that the Connect sidecar can inherit the default `restart`.
+
+## `restart` Parameters
+
+- `attempts` `(int: <varies>)` - Specifies the number of restarts allowed in the
+  configured interval. Defaults vary by job type, see below for more
+  information.
+
+- `delay` `(string: "15s")` - Specifies the duration to wait before restarting a
+  task. This is specified using a label suffix like "30s" or "1h". A random
+  jitter of up to 25% is added to the delay.
+
+- `interval` `(string: <varies>)` - Specifies the duration which begins when the
+  first task starts and ensures that only `attempts` number of restarts happens
+  within it. If more than `attempts` number of failures happen, behavior is
+  controlled by `mode`. This is specified using a label suffix like "30s" or
+  "1h". Defaults vary by job type, see below for more information.
+
+- `mode` `(string: "fail")` - Controls the behavior when the task fails more
+  than `attempts` times in an interval. For a detailed explanation of these
+  values and their behavior, please see the [mode values section](#mode-values).
+
+- `render_templates` `(bool: false)` - Specifies whether to re-render all
+templates when a task is restarted. If set to `true`, all templates will be re-rendered
+when the task restarts. This can be useful for re-fetching Vault secrets, even if the
+lease on the existing secrets has not yet expired.
+
+### `restart` Parameter Defaults
+
+The values for many of the `restart` parameters vary by job type. Here are the
+defaults by job type:
+
+- The default batch restart policy is:
+
+  ```hcl
+  restart {
+    attempts         = 3
+    delay            = "15s"
+    interval         = "24h"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+- The default service and system job restart policy is:
+
+  ```hcl
+  restart {
+    interval         = "30m"
+    attempts         = 2
+    delay            = "15s"
+    mode             = "fail"
+    render_templates = false
+  }
+  ```
+
+### Disabling restart
+
+To disable restarting, set the `attempts` parameter to zero and `mode` to `"fail"`.
+
+```hcl
+job "docs" {
+  group "example" {
+    restart {
+      attempts = 0
+      mode     = "fail"
+    }
+  }
+}
+```
+
+### `mode` Values
+
+This section details the specific values for the "mode" parameter in the Nomad
+job specification for constraints. The mode is always specified as a string:
+
+```hcl
+restart {
+  mode = "..."
+}
+```
+
+- `"delay"` - Instructs the client to wait until another `interval`
+  before restarting the task.
+
+- `"fail"` - Instructs the client not to attempt to restart the task
+  once the number of `attempts` have been used. This is the default
+  behavior. This mode is useful for non-idempotent jobs which are
+  unlikely to succeed after a few failures. The allocation will be
+  marked as failed and the scheduler will attempt to reschedule the
+  allocation according to the
+  [`reschedule`] block.
+
+### `restart` Examples
+
+With the following `restart` block, a failing task will restart 3
+times with 15 seconds between attempts, and then wait 10 minutes
+before attempting another 3 attempts. The task restart will never fail
+the entire allocation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "delay"
+}
+```
+
+With the following `restart` block, a task that fails after 1
+minute, after 2 minutes, and after 3 minutes will be restarted each
+time. If it fails again before 10 minutes, the entire allocation will
+be marked as failed and the scheduler will follow the group's
+[`reschedule`] specification, possibly resulting in a new evaluation.
+
+```hcl
+restart {
+  attempts = 3
+  delay    = "15s"
+  interval = "10m"
+  mode     = "fail"
+}
+```
+
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[`reschedule`]: /nomad/docs/job-specification/reschedule
+[rescheduling]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/scaling.mdx b/content/nomad/v1.9.x/content/docs/job-specification/scaling.mdx
new file mode 100644
index 0000000000..1789c56997
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/scaling.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: scaling Block - Job Specification
+description: The "scaling" block allows specifying scaling policy for a task group
+---
+
+# `scaling` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'scaling'],
+    ['job', 'group', 'task', 'scaling'],
+  ]}
+/>
+
+The `scaling` block allows configuring scaling options for a `task` or a
+`group`, for the purpose of supporting external autoscalers like the
+[Nomad Autoscaler](https://github.com/hashicorp/nomad-autoscaler) and scaling
+via the Nomad UI. This block is not supported within jobs of type `system`.
+
+When placed at the `group` level, the scaling policy will be of type
+[horizontal application scaling][horizontal_app_scaling], controlling the value
+of [`count`][] for the group.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    count = 1
+
+    scaling {
+      enabled = true
+      min     = 0
+      max     = 10
+
+      policy {
+        # ...
+      }
+    }
+    # ...
+  }
+}
+```
+
+When placed at the `task` level, the scaling policy will be of type
+[Dynamic Application Sizing][das], controlling the [`resources`][] values of
+the task. In this scenario, the `scaling` block must have a label indicating
+which resource will be controlled. Valid names are `cpu` and `mem`.
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 256
+      }
+
+      scaling "cpu" {
+        enabled = true
+        min     = 100
+        max     = 500
+
+        policy {
+          # ...
+        }
+      }
+
+      scaling "mem" {
+        enabled = true
+        min     = 64
+        max     = 512
+
+        policy {
+          # ...
+        }
+      }
+    }
+  }
+}
+```
+
+## `scaling` Parameters
+
+- `min` - <code>(int: nil)</code> - The minimum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations. Defaults to the specified task group [`count`][].
+
+- `max` - <code>(int: &lt;required&gt;)</code> - The maximum acceptable count for the task group.
+  This should be honored by the external autoscaler. It will also be honored by Nomad
+  during job updates and scaling operations.
+
+- `enabled` - <code>(bool: false)</code> - Whether the scaling policy is enabled.
+  This is intended to allow temporarily disabling an autoscaling policy, and should be
+  honored by the external autoscaler.
+
+- `policy` - <code>(map<string|...>: nil)</code> - The autoscaling policy. This is
+  opaque to Nomad, consumed and parsed only by the external autoscaler. Therefore,
+  its contents are specific to the autoscaler; consult the
+  [Nomad Autoscaler documentation][autoscaling_policy] for more details.
+
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[`count`]: /nomad/docs/job-specification/group#count 'Nomad Task Group specification'
+[`resources`]: /nomad/docs/job-specification/task#resources 'Nomad Task specification'
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[horizontal_app_scaling]: /nomad/tools/autoscaling#horizontal-application-autoscaling
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/schedule.mdx b/content/nomad/v1.9.x/content/docs/job-specification/schedule.mdx
new file mode 100644
index 0000000000..454b359995
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/schedule.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: schedule Block - Job Specification
+description: |-
+  Time based task execution is enabled by using the "schedule" task block.
+---
+
+# `schedule` Block
+
+<EnterpriseAlert />
+
+<Placement groups={['job', 'group', 'task', 'periodic']} />
+
+~> **Note:** Time based task execution is an experimental feature and subject
+to change. This feature is supported for select customers. Please refer to the
+[Upgrade Guide][upgrade] to find breaking changes. 
+
+Time based task execution is enabled by using the `schedule` block. The
+`schedule` block controls when a task is allowed to be running.
+
+Unlike [`periodic`][periodic] jobs, the `schedule` block applies to individual
+tasks. The Nomad Client starts and stops tasks at the specified time without
+interaction with the Nomad Servers. This means time based task execution works
+even when a Client is disconnected from Servers. The task's resources remain
+allocated even outside the `schedule` when the task itself is stopped.
+
+```hcl
+job "docs" {
+  group "tbte" {
+    task "scheduled" {
+      schedule {
+        cron {
+          start    = "30 9 * * MON-FRI *"
+          end      = "0 16"
+          timezone = "America/New_York"
+        }
+      }
+    }
+  }
+}
+```
+
+## `schedule` Parameters
+
+The `schedule` block must have a `cron` block containing:
+
+- `start` `(string: <required>)` - When the task should be started. Specified in 6 field
+  [cron format][cron] (no seconds) without `,` or `/` characters.
+
+- `end` `(string: <required>)` - When the task should be stopped
+  ([`kill_signal`][kill_signal] and [`kill_timeout`][kill_timeout] apply).
+  Specified in 2 field [cron format][cron] (minute and hour) without `,` or `/`
+  characters.
+
+- `timezone` `(string: "Local")` - What time zone the `start` and `end` times
+  are specified in. Defaults to the local time zone of the Nomad Client the job
+  is scheduled onto.
+
+## Limitations
+
+- Job deployments outside of the specified `schedule` will be unable to
+  succeed. To update a job using time based task execution outside of its
+  schedule, do a [force
+  update](/nomad/docs/job-specification/update#max_parallel-0).
+
+- Overnight schedules are currently not supported. Adjusting the `timezone`
+  should allow converting overnight schedules to times within a single day.
+
+[periodic]: /nomad/docs/job-specification/periodic
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[cron]: https://github.com/hashicorp/cronexpr#implementation 'List of cron expressions'
+[upgrade]: /nomad/docs/upgrade/upgrade-specific
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/service.mdx b/content/nomad/v1.9.x/content/docs/job-specification/service.mdx
new file mode 100644
index 0000000000..50a68fde23
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/service.mdx
@@ -0,0 +1,551 @@
+---
+layout: docs
+page_title: service Block - Job Specification
+description: |-
+  The "service" block instructs Nomad to register the task as a service using
+  the Nomad or Consul service discovery integration.
+---
+
+# `service` Block
+
+<Placement
+  groups={[
+    ['job', 'group', 'service'],
+    ['job', 'group', 'task', 'service'],
+  ]}
+/>
+
+The `service` block instructs Nomad to register a service with the specified
+provider; Nomad or Consul. This section of the documentation will discuss the
+configuration, but please also read the
+[Nomad service discovery documentation][service-discovery] for more detailed
+information about the external integrations.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      service {
+        tags = ["leader", "mysql"]
+
+        port = "db"
+
+        provider = "consul"
+
+        weights {
+          passing = 5
+          warning = 1
+        }
+
+        meta {
+          meta = "for your service"
+        }
+
+        check {
+          type     = "tcp"
+          port     = "db"
+          interval = "10s"
+          timeout  = "2s"
+        }
+
+        check {
+          type     = "http"
+          name     = "app_health"
+          path     = "/health"
+          interval = "20s"
+          timeout  = "5s"
+
+          check_restart {
+            limit = 3
+            grace = "90s"
+            ignore_warnings = false
+          }
+        }
+
+        identity {
+          aud = ["consul.io"]
+        }
+      }
+    }
+  }
+}
+```
+
+This section of the documentation only cover the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul please see
+the [Consul integration documentation][service-discovery].
+
+The `service` block can also be at task group level.
+This enables services in the same task group to opt into [Consul
+Service Mesh][connect] integration.
+
+## `service` Parameters
+
+- `provider` `(string: "consul")` - Specifies the service registration provider
+  to use for service registrations. Valid options are either `consul` or
+  `nomad`. All services within a single task group must utilise the same
+  provider value.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Consul cluster to use, when the `provider` is `"consul"`. The Nomad client
+  will retrieve a Consul token from the cluster configured in the agent
+  configuration with the same [`consul.name`][]. In Nomad Community Edition,
+  this field is ignored.
+
+- `check` <code>([Check][check]: nil)</code> - Specifies a health
+  check associated with the service. This can be specified multiple times to
+  define multiple checks for the service. At this time, a check using the Nomad
+  provider supports `tcp` and `http` checks. The Consul integration supports
+  the `grpc`, `http`, `script`<sup><small>1</small></sup>, and `tcp` checks.
+
+- `weights` <code>(Weights: nil)</code> - Specifies how a service instance is
+  weighted in a DNS SRV request based on the service's health status, as
+  described in the Consul [weights][] documentation. Only available where
+  `provider = "consul"` The `weight` block supports the following fields:
+  - `passing` <code>int: 1</code> - The weight of services in passing state.
+  - `warning` <code>int: 1</code> - The weight of services in warning state.
+
+- `connect` - Configures the [Consul Connect][connect] integration. Only
+  available on group services and where `provider = "consul"`.
+
+- `identity` <code>([Identity][identity_block]: nil)</code> - Specifies a
+  Workload Identity to use when obtaining Service Identity tokens from Consul to
+  register the service. Only available where `provider = "consul"`. Typically
+  this can be omitted so that Nomad will fall back to the server's
+  [`consul.service_identity`][] block.
+
+- `name` `(string: "<job>-<taskgroup>-<task>")` - Specifies the name this service
+  will be advertised as in Consul. If not supplied, this will default to the
+  name of the job, task group, and task concatenated together with a dash, like
+  `"docs-example-server"`. Each service must have a unique name within the
+  cluster. Names must adhere to [RFC-1123
+  §2.1](https://tools.ietf.org/html/rfc1123#section-2) and are limited to
+  alphanumeric and hyphen characters (i.e. `[a-z0-9\-]`), and be less than 64
+  characters in length.
+
+  In addition to the standard [Nomad interpolation][interpolation], the
+  following keys are also available:
+
+  - `${JOB}` - the name of the job
+  - `${TASKGROUP}` - the name of the task group
+  - `${TASK}` - the name of the task
+  - `${BASE}` - shorthand for `${JOB}-${TASKGROUP}-${TASK}`
+
+  Validation of the name occurs in two parts. When the job is registered, an initial validation pass checks that
+  the service name adheres to RFC-1123 §2.1 and the length limit, excluding any variables requiring interpolation.
+  Once the client receives the service and all interpretable values are available, the service name will be
+  interpolated and revalidated. This can cause certain service names to pass validation at submit time but fail
+  at runtime.
+
+- `port` `(string: <optional>)` - Specifies the port to advertise for this
+  service. The value of `port` depends on which [`address_mode`](#address_mode)
+  is being used:
+
+  - `alloc` - Advertise the mapped `to` value of the labeled port and the allocation address.
+    If a `to` value is not set, the port falls back to using the allocated host port. The `port`
+    field may be a numeric port or a port label specified in the same group's network block.
+
+  - `driver` - Advertise the port determined by the driver (e.g. Docker).
+    The `port` may be a numeric port or a port label specified in the driver's
+    `ports` field.
+
+  - `host` - Advertise the host port for this service. `port` must match a port
+    _label_ specified in the [`network`][network] block.
+
+- `tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service. If this is not supplied, no tags will be assigned to the service
+  when it is registered.
+
+- `canary_tags` `(array<string>: [])` - Specifies the list of tags to associate with
+  this service when the service is part of an allocation that is currently a
+  canary. Once the canary is promoted, the registered tags will be updated to
+  those specified in the `tags` parameter. If this is not supplied, the
+  registered tags will be equal to that of the `tags` parameter.
+
+- `enable_tag_override` `(bool: false)` - Enables users of Consul's Catalog API
+  to make changes to the tags of a service without having those changes be
+  overwritten by Consul's anti-entropy mechanism. See Consul
+  [documentation](/consul/docs/concepts/anti-entropy#enable-tag-override)
+  for more information. Only available where `provider = "consul"`.
+
+- `address` `(string: <optional>)` - Specifies a custom address to advertise in
+  Consul or Nomad service registration. If set, `address_mode` must be in `auto`
+  mode. Useful with interpolation - for example to advertise the public IP address
+  of an AWS EC2 instance set this to `${attr.unique.platform.aws.public-ipv4}`.
+
+- `tagged_addresses` `(map<string|string>` - Specifies custom [tagged addresses][tagged_addresses] to
+  advertise in the Consul service registration. Only available where `provider = "consul"`.
+
+- `address_mode` `(string: "auto")` - Specifies which address (host, alloc or
+  driver-specific) this service should advertise. See [below for
+  examples.](#using-driver-address-mode) Valid options are:
+
+  - `alloc` - For allocations which create a network namespace, this address mode
+    uses the IP address inside the namespace. Can only be used with "bridge" and "cni"
+    [networking modes][network_mode]. A numeric port may be specified for situations
+    where no port mapping is necessary. This mode can only be set for services which
+    are defined in a "group" block.
+
+  - `auto` - Allows the driver to determine whether the host or driver address
+    should be used. Defaults to `host` and only implemented by Docker. If you
+    use a Docker network plugin such as weave, Docker will automatically use
+    its address.
+
+  - `driver` - Use the IP specified by the driver, and the port specified in a
+    port map. A numeric port may be specified since port maps aren't required
+    by all network plugins. Useful for advertising SDN and overlay network
+    addresses. Task will fail if driver network cannot be determined. Only
+    implemented for Docker. This mode can only be set for services
+    which are defined in a "task" block.
+
+  - `host` - Use the host IP and port.
+
+- `task` `(string: "")` - Specifies the name of the Nomad task associated with
+  this service definition. Only available on group services. Must be set if this
+  service definition represents a Consul Connect-native service and there is more
+  than one task in the task group.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  the Consul service with user-defined metadata. Only available where
+  `provider = "consul"`.
+
+- `canary_meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that
+  annotates the Consul service with user-defined metadata when the service is
+  part of an allocation that is currently a canary. Once the canary is
+  promoted, the registered meta will be updated to those specified in the
+  `meta` parameter. If this is not supplied, the registered meta will be set to
+  that of the `meta` parameter. Only available where `provider = "consul"`.
+
+- `on_update` `(string: "require_healthy")` - Specifies how checks should be
+  evaluated when determining deployment health (including a job's initial
+  deployment). This allows job submitters to define certain checks as readiness
+  checks, progressing a deployment even if the Service's checks are not yet
+  healthy. Checks inherit the Service's value by default. The check status is
+  not altered in Consul and is only used to determine the check's health during
+  an update.
+
+  - `require_healthy` - In order for Nomad to consider the check healthy during
+    an update it must report as healthy.
+
+  - `ignore_warnings` - If a Service Check reports as warning, Nomad will treat
+    the check as healthy. The Check will still be in a warning state in Consul.
+
+  - `ignore` - Any status will be treated as healthy.
+
+  ~> **Caveat:** `on_update` is only compatible with certain
+  [`check_restart`][check_restart_block] configurations. `on_update = "ignore_warnings"` requires that `check_restart.ignore_warnings = true`.
+  `check_restart` can however specify `ignore_warnings = true` with `on_update = "require_healthy"`. If `on_update` is set to `ignore`, `check_restart` must
+  be omitted entirely.
+
+
+## `service` Lifecycle
+
+Nomad manages registering, updating, and deregistering services with the
+service provider. It is important to understand when each of these steps
+happens and how they can be customized.
+
+**Registration**: Nomad will register `group` services and checks _before_
+starting any tasks. Services and checks for a specific `task` are registered
+_after_ the task has started.
+
+**Updating**: If a service or check definition is updated, Nomad will update
+the service in the provider as well. This update happens without restarting a
+task.
+
+**Deregistering**: If a running task with a service block exits, the services
+and checks are immediately deregistered from the provider without delay. If,
+however, Nomad needs to kill a running task, the task is killed in the
+following order:
+
+1. Immediately remove the services and checks from the provider. This stops new
+   traffic from being routed to the task that is being killed.
+2. If [`shutdown_delay`][shutdowndelay] is set, wait the configured duration
+   before proceeding to step 3. Setting a [`shutdown_delay`][shutdowndelay] can
+   be useful if the application itself doesn't handle graceful shutdowns based
+   on the [`kill_signal`][killsignal]. The configured delay will provide a
+   period of time in which the service is no longer registered in the provider,
+   and thus is not receiving additional requests, but hasn't been signalled to
+   shutdown. This allows the application time to complete the requests and
+   become idle.
+3. Send the [`kill_signal`][killsignal] to the task and wait for the task to
+   exit. The task should use this time to gracefully drain and finish any
+   existing requests.
+4. If the task has not exited after the [`kill_timeout`][killtimeout], Nomad
+   will force kill the application.
+
+## `service` Examples
+
+The following examples only show the `service` blocks. Remember that the
+`service` block is only valid in the placements listed above.
+
+### Basic Service
+
+This example registers a service named "load-balancer" with no health checks
+using the Nomad provider:
+
+```hcl
+service {
+  name     = "load-balancer"
+  port     = "lb"
+  provider = "nomad"
+}
+```
+
+This example registers a service named "load-balancer" with no health checks
+using the Consul provider:
+
+```hcl
+service {
+  name = "load-balancer"
+  port = "lb"
+}
+```
+
+These examples must be accompanied by a [`network`][network] block which
+defines a static or dynamic port labeled "lb". For example:
+
+```hcl
+network {
+  port "lb" {}
+}
+```
+
+
+### Using Driver Address Mode
+
+The [Docker](/nomad/docs/drivers/docker#network_mode) driver supports the `driver`
+setting for the `address_mode` parameter in both `service` and `check` blocks.
+The driver address mode allows advertising and health checking the IP and port
+assigned to a task by the driver. This way, if you're using a network plugin like
+Weave with Docker, you can advertise the Weave address in Consul instead of the
+host's address.
+
+For example if you were running the example Redis job in an environment with
+Weave but Consul was running on the host you could use the following
+configuration:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = "db"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+        }
+      }
+    }
+  }
+}
+```
+
+No explicit `address_mode` required.
+
+Services default to the `auto` address mode. When a Docker network mode other
+than `"host"` or `"bridge"` is used, services will automatically advertise the
+driver's address (in this case Weave's). The service will advertise the
+container's port: 6379.
+
+However since Consul is often run on the host without access to the Weave
+network, `check` blocks default to `host` address mode. The TCP check will run
+against the host's IP and the dynamic host port assigned by Nomad.
+
+Note that the `check` still inherits the `service` block's `db` port label,
+but each will resolve the port label according to their address mode.
+
+If Consul has access to the Weave network the job could be configured like
+this:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        network_mode = "weave"
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "weave-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "host-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+In this case Nomad doesn't need to assign Redis any host ports. The `service`
+and `check` blocks can both specify the port number to advertise and check
+directly since Nomad isn't managing any port assignments.
+
+### IPv6 Docker containers
+
+The [Docker](/nomad/docs/drivers/docker#advertise_ipv6_address) driver supports the
+`advertise_ipv6_address` parameter in its configuration.
+
+Services will automatically advertise the IPv6 address when `advertise_ipv6_address`
+is used.
+
+Unlike services, checks do not have an `auto` address mode as there's no way
+for Nomad to know which is the best address to use for checks. Consul needs
+access to the address for any HTTP or TCP checks.
+
+So you have to set `address_mode` parameter in the `check` block to `driver`.
+
+For example using `auto` address mode:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+  group "cache" {
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        ports = ["db"]
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = "db"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = "db"
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+Or using `address_mode=driver` for `service` and `check` with numeric ports:
+
+```hcl
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    task "redis" {
+      driver = "docker"
+
+      config {
+        image = "redis:7"
+        advertise_ipv6_address = true
+        # No port map required.
+      }
+
+      resources {
+        cpu    = 500 # 500 MHz
+        memory = 256 # 256MB
+      }
+
+      service {
+        name = "ipv6-redis"
+        port = 6379
+        address_mode = "driver"
+        check {
+          name     = "ipv6-redis-check"
+          type     = "tcp"
+          interval = "10s"
+          timeout  = "2s"
+          port     = 6379
+          address_mode = "driver"
+        }
+      }
+    }
+  }
+}
+```
+
+The `service` and `check` blocks can both specify the port number to
+advertise and check directly since Nomad isn't managing any port assignments.
+
+---
+
+[check]: /nomad/docs/job-specification/check
+[check_restart_block]: /nomad/docs/job-specification/check_restart
+[consul_grpc]: /consul/api-docs/agent/check#grpc
+[consul_passfail]: /consul/docs/discovery/checks#success-failures-before-passing-critical
+[service-discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad Runtime Interpolation'
+[network]: /nomad/docs/job-specification/network 'Nomad network Job Specification'
+[qemu]: /nomad/docs/drivers/qemu 'Nomad QEMU Driver'
+[restart_block]: /nomad/docs/job-specification/restart 'restart block'
+[connect]: /nomad/docs/job-specification/connect 'Nomad Consul Connect Integration'
+[type]: /nomad/docs/job-specification/service#type
+[shutdowndelay]: /nomad/docs/job-specification/task#shutdown_delay
+[killsignal]: /nomad/docs/job-specification/task#kill_signal
+[killtimeout]: /nomad/docs/job-specification/task#kill_timeout
+[service_task]: /nomad/docs/job-specification/service#task-1
+[network_mode]: /nomad/docs/job-specification/network#mode
+[on_update]: /nomad/docs/job-specification/service#on_update
+[tagged_addresses]: /consul/docs/discovery/services#tagged-addresses
+[`consul.name`]: /nomad/docs/configuration/consul#name
+[`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
+[identity_block]: /nomad/docs/job-specification/identity
+[weights]: /consul/docs/services/configuration/services-configuration-reference#weights
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/sidecar_service.mdx b/content/nomad/v1.9.x/content/docs/job-specification/sidecar_service.mdx
new file mode 100644
index 0000000000..5cffbb38bf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/sidecar_service.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: sidecar_service Block - Job Specification
+description: |-
+  The "sidecar_service" block allows specifying options for configuring
+  sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_service` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_service']} />
+
+The `sidecar_service` block allows configuring various options for the sidecar
+proxy managed by Nomad for [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration. It is
+valid only within the context of a connect block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## `sidecar_service` Parameters
+
+- `disable_default_tcp_check` `(bool: false)` - disable the default TCP health
+  check.
+
+- `meta` <code>(map&lt;string|string&gt;: nil)</code> - Specifies arbitrary KV metadata pairs.
+
+- `port` `(string: )` - Port label for sidecar service.
+
+- `proxy` <code>([proxy][]: nil)</code> - This is used to configure the
+  sidecar proxy service.
+
+- `tags` <code>(array&lt;string&gt;: nil)</code> - Custom Consul service tags
+  for the sidecar service.
+
+## `sidecar_service` Examples
+
+The following example is a minimal `sidecar_service` block with defaults
+
+```hcl
+  connect {
+    sidecar_service {}
+  }
+```
+
+The following example includes specifying upstreams and meta.
+
+```hcl
+   sidecar_service {
+     proxy {
+       upstreams {
+         destination_name = "count-api"
+         local_bind_port = 8080
+       }
+     }
+     meta {
+       test-key = "test-value"
+     }
+   }
+
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[proxy]: /nomad/docs/job-specification/proxy 'Nomad sidecar proxy config Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/sidecar_task.mdx b/content/nomad/v1.9.x/content/docs/job-specification/sidecar_task.mdx
new file mode 100644
index 0000000000..6fc00a0151
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/sidecar_task.mdx
@@ -0,0 +1,190 @@
+---
+layout: docs
+page_title: sidecar_task Block - Job Specification
+description: |-
+  The "sidecar_task" block allows specifying options for configuring
+  the task of the sidecar proxies used in Consul Connect integration
+---
+
+# `sidecar_task` Block
+
+<Placement groups={['job', 'group', 'service', 'connect', 'sidecar_task']} />
+
+The `sidecar_task` block allows configuring various options for the proxy
+sidecar or Connect gateway managed by Nomad for the [Consul
+Connect](/nomad/docs/integrations/consul-connect) integration such as
+resource requirements, kill timeouts and more as defined below. It is valid
+only within the context of a [`connect`][connect] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "api" {
+    network {
+      mode = "bridge"
+    }
+
+    service {
+      name = "count-api"
+      port = "9001"
+
+      connect {
+        sidecar_service {}
+
+        sidecar_task {
+          resources {
+            cpu    = 500
+            memory = 1024
+          }
+        }
+      }
+    }
+
+    task "web" {
+      driver = "docker"
+
+      config {
+        image = "hashicorpdev/counter-api:v3"
+      }
+    }
+  }
+}
+```
+
+## Default Envoy configuration
+
+Nomad automatically launches and manages an Envoy task for use as a proxy sidecar
+or connect gateway, when [`sidecar_service`][sidecar_service] or [`gateway`][gateway]
+are configured.
+
+The default Envoy task is equivalent to:
+
+```hcl
+sidecar_task {
+  name = "connect-proxy-<service>"
+  #      "connect-gateway-<service>" when used as a gateway
+
+  lifecycle { # absent when used as a gateway
+    hook    = "prestart"
+    sidecar = true
+  }
+
+  driver = "docker"
+
+  config {
+    image = "${meta.connect.sidecar_image}"
+    #       "${meta.connect.gateway_image}" when used as a gateway
+
+    args = [
+      "-c",
+      "${NOMAD_SECRETS_DIR}/envoy_bootstrap.json",
+      "-l",
+      "${meta.connect.log_level}",
+      "--concurrency",
+      "${meta.connect.proxy_concurrency}",
+      "--disable-hot-restart"
+    ]
+  }
+
+  logs {
+    max_files     = 2
+    max_file_size = 2 # MB
+  }
+
+  resources {
+    cpu    = 250 # MHz
+    memory = 128 # MB
+  }
+
+  shutdown_delay = "5s"
+}
+```
+
+The `meta.connect.sidecar_image`, `meta.connect.gateway_image`, `meta.connect.log_level`,
+and `meta.connect.proxy_concurrency` variables are [client configurable][nodemeta]
+variables with the following defaults:
+
+- `sidecar_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `gateway_image` - `(string: "docker.io/envoyproxy/envoy:v${NOMAD_envoy_version}")` - The official
+  upstream Envoy Docker image, where `${NOMAD_envoy_version}` is resolved automatically
+  by a query to Consul.
+- `log_level` - `(string: "info")` - Envoy sidecar log level. "`debug`" is useful for
+  debugging Connect related issues.
+- `proxy_concurrency` - `(string: "1")` - The number of [worker threads][worker_threads] the Envoy
+  sidecar will run.
+
+Custom images can make use of Consul's preferred Envoy version by making use of
+Nomad's version interpolation, e.g.
+
+```hcl
+meta.connect.sidecar_image = custom/envoy-${NOMAD_envoy_version}:latest
+```
+
+## `sidecar_task` Parameters
+
+- `name` `(string: "connect-[proxy|gateway]-<service>")` - Name of the task. Defaults to
+  including the name of the service the proxy or gateway is providing.
+
+- `driver` `(string: "docker")` - Driver used for the sidecar task.
+
+- `user` `(string: nil)` - Determines which user is used to run the task, defaults
+  to the same user the Nomad client is being run as.
+
+- `config` `(map: nil)` - Configuration provided to the driver for initialization.
+  Keys and values support [runtime variable interpolation][interpolation].
+
+- `env` `(map: nil)` - Map of environment variables used by the driver.
+
+- `resources` <code>([Resources][resources])</code> - Resources needed by the sidecar task.
+
+- `meta` `(map: nil)` - Arbitrary metadata associated with this task that's opaque to Nomad.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `kill_timeout` `(string: "5s")` - Time between signalling a task that will be
+  killed and killing it.
+
+- `shutdown_delay` `(string: "5s")` - Delay between deregistering the task from
+  Consul and sending it a signal to shutdown.
+
+- `kill_signal` `(string:SIGINT)` - Kill signal to use for the task, defaults to SIGINT.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+## `sidecar_task` Examples
+
+The following example configures resources for the sidecar task and other configuration.
+
+```hcl
+   sidecar_task {
+     resources {
+       cpu = 500
+       memory = 1024
+     }
+
+     env {
+       FOO = "abc"
+     }
+
+     shutdown_delay = "5s"
+   }
+
+```
+
+[connect]: /nomad/docs/job-specification/connect 'Nomad connect Job Specification'
+[gateway]: /nomad/docs/job-specification/gateway
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[nodemeta]: /nomad/docs/configuration/client#meta
+[worker_threads]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/spread.mdx b/content/nomad/v1.9.x/content/docs/job-specification/spread.mdx
new file mode 100644
index 0000000000..d4e2f99df9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/spread.mdx
@@ -0,0 +1,205 @@
+---
+layout: docs
+page_title: spread Block - Job Specification
+description: >-
+  The "spread" block is used to spread placements across a certain node
+  attributes such as datacenter.
+
+  Spread may be specified at the job or group levels for ultimate flexibility.
+
+  More than one spread block may be specified with relative weights between
+  each.
+---
+
+# `spread` Block
+
+<Placement
+  groups={[
+    ['job', 'spread'],
+    ['job', 'group', 'spread'],
+  ]}
+/>
+
+The `spread` block allows operators to increase the failure tolerance of their
+applications by specifying a node attribute that allocations should be spread
+over. This allows operators to spread allocations over attributes such as
+datacenter, availability zone, or even rack in a physical datacenter.
+
+By default, when `spread` is omitted, the scheduler will attempt to place
+allocations from the same job on different nodes (and binpacked between
+jobs). When using `spread` the scheduler will attempt to place allocations
+equally among the available values of the given target.
+
+```hcl
+job "docs" {
+  # Spread allocations over all datacenter
+  spread {
+    attribute = "${node.datacenter}"
+  }
+
+  group "example" {
+    # Spread allocations over each rack based on desired percentage
+      spread {
+        attribute = "${meta.rack}"
+        target "r1" {
+          percent = 60
+        }
+        target "r2" {
+          percent = 40
+        }
+      }
+  }
+}
+```
+
+Nodes are scored according to how closely they match the desired target
+percentage defined in the spread block. Spread scores are combined with other
+scoring factors such as bin packing.
+
+A job or task group can have more than one spread criteria, with weights to
+express relative preference.
+
+Spread criteria are treated as a soft preference by the Nomad scheduler. If no
+nodes match a given spread criteria, placement is still successful. To avoid
+scoring every node for every placement, allocations may not be perfectly
+spread. Spread works best on attributes with similar number of nodes:
+identically configured racks or similarly configured datacenters.
+
+Spread may be expressed on [attributes][interpolation] or [client
+metadata][client-meta].  Additionally, spread may be specified at the [job][job]
+and [group][group] levels for ultimate flexibility. Job level spread criteria
+are inherited by all task groups in the job.
+
+## `spread` Parameters
+
+- `attribute` `(string: "")` - Specifies the name or reference of the attribute
+  to use. This can be any of the [Nomad interpolated
+  values](/nomad/docs/runtime/interpolation#interpreted_node_vars).
+
+- `target` <code>([target](#target-parameters): &lt;required&gt;)</code> - Specifies one or more target
+  percentages for each value of the `attribute` in the spread block. If this is omitted,
+  Nomad will spread allocations evenly across all values of the attribute.
+
+- `weight` `(integer:0)` - Specifies a weight for the spread block. The weight is used
+  during scoring and must be an integer between 0 to 100. Weights can be used
+  when there is more than one spread or affinity block to express relative preference across them.
+
+## `target` Parameters
+
+- `value` `(string:"")` - Specifies a target value of the attribute from a `spread` block.
+
+- `percent` `(integer:0)` - Specifies the percentage associated with the target value.
+
+## Comparison to `spread` Scheduling Algorithm
+
+The `spread` block is not the same concept as setting the [scheduler
+algorithm][] to `"spread"` instead of `"binpack"`. Setting the scheduler
+algorithm impacts all jobs on a cluster (or node pool), and adjusts the tendency
+of the scheduler to place workloads from different jobs on the same set of nodes
+or not. The `spread` block impacts how the scheduler places allocations for a
+given job.
+
+## Scheduling Performance
+
+Using the `spread` block can have significant impact on scheduling
+performance. For each allocation in a `service` and `batch` job, the scheduler
+iterates over nodes until it finds a small number of feasible nodes. Those
+feasible nodes are then scored to find the best placement.
+
+When `spread` is omitted, this limit is 2 for batch jobs and the log<sub>2</sub>
+of the total number of nodes in the datacenter and node pool (with a minimum of
+2) for service jobs. When the `spread` block is present, the scheduler instead
+scores a number of nodes in the datacenter and node pool equal to the task group
+count (with a maximum of 100) per allocation. This can result in
+order-of-magnitude increases in scheduling times.
+
+To monitor scheduling times potentially impacted by `spread` blocks, examine the
+`nomad.nomad.worker.invoke_scheduler.*` found in the [Key Metrics][] table. You
+can reduce scheduling times by avoiding `spread` and instead relying on the
+default distribution of a job across multiple nodes. If this is not possible,
+you may consider reducing the size of the node pool or datacenter to reduce the
+number of nodes available for the scheduler to consider.
+
+## `spread` Examples
+
+The following examples show different ways to use the `spread` block.
+
+### Even Spread Across Data Center
+
+This example shows a spread block across the node's `datacenter` attribute. If we have
+two datacenters `us-east1` and `us-west1`, and a task group of `count = 10`,
+Nomad will attempt to place 5 allocations in each datacenter.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+}
+```
+
+### Spread With Target Percentages
+
+This example shows a spread block that specifies one target percentage. If we
+have three datacenters `us-east1`, `us-east2`, and `us-west1`, and a task group
+of `count = 10`, Nomad will attempt to place 5 of the allocations in "us-east1",
+and will spread the remaining among the other two datacenters.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 50
+  }
+}
+```
+
+This example shows a spread block that specifies target percentages for two
+different datacenters. If we have two datacenters `us-east1` and `us-west1`,
+and a task group of `count = 10`, Nomad will attempt to place 6 allocations
+in `us-east1` and 4 in `us-west1`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 100
+
+  target "us-east1" {
+    percent = 60
+  }
+
+  target "us-west1" {
+      percent = 40
+  }
+}
+```
+
+### Spread Across Multiple Attributes
+
+This example shows spread blocks with multiple attributes. Consider a Nomad cluster
+where there are two datacenters `us-east1` and `us-west1`, and each datacenter has nodes
+with `${meta.rack}` being `r1` or `r2`. With the following spread block used on a job with `count=12`, Nomad
+will attempt to place 6 allocations in each datacenter. Within a datacenter, Nomad will
+attempt to place 3 allocations in nodes on rack `r1`, and 3 allocations in nodes on rack `r2`.
+
+```hcl
+spread {
+  attribute = "${node.datacenter}"
+  weight    = 50
+}
+spread {
+  attribute = "${meta.rack}"
+  weight    = 50
+}
+```
+
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[client-meta]: /nomad/docs/configuration/client#meta 'Nomad meta Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[node-variables]: /nomad/docs/runtime/interpolation#node-variables- 'Nomad interpolation-Node variables'
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad Constraint job Specification'
+[Key Metrics]: /nomad/docs/operations/metrics-reference#key-metrics
+[scheduler algorithm]: /nomad/docs/commands/operator/scheduler/set-config#scheduler-algorithm
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/task.mdx b/content/nomad/v1.9.x/content/docs/job-specification/task.mdx
new file mode 100644
index 0000000000..8b634940a5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/task.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: task Block - Job Specification
+description: |-
+  The "task" block creates an individual unit of work, such as a Docker
+  container, web application, or batch processing.
+---
+
+# `task` Block
+
+<Placement groups={['job', 'group', 'task']} />
+
+The `task` block creates an individual unit of work, such as a Docker
+container, web application, or batch processing.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      # ...
+    }
+  }
+}
+```
+
+## `task` Parameters
+
+- `artifact` <code>([Artifact][]: nil)</code> - Defines an artifact to download
+  before running the task. This may be specified multiple times to download
+  multiple artifacts.
+
+- `config` `(map<string|string>: nil)` - Specifies the driver configuration,
+  which is passed directly to the driver to start the task. The details of
+  configurations are specific to each driver, so please see specific driver
+  documentation for more information.
+
+- `consul` <code>([Consul][consul_jobspec]: nil)</code> - Specifies Consul
+  configuration options specific to the task.
+
+- `constraint` <code>([Constraint][]: nil)</code> - Specifies user-defined
+  constraints on the task. This can be provided multiple times to define
+  additional constraints.
+
+- `affinity` <code>([Affinity][]: nil)</code> - This can be provided
+  multiple times to define preferred placement criteria.
+
+- `dispatch_payload` <code>([DispatchPayload][]: nil)</code> - Configures the
+  task to have access to dispatch payloads.
+
+- `driver` - Specifies the task driver that should be used to run the
+  task. See the [driver documentation](/nomad/docs/drivers) for what
+  is available. Examples include `docker`, `qemu`, `java` and `exec`.
+
+- `env` <code>([Env][]: nil)</code> - Specifies environment variables that will
+  be passed to the running process.
+
+- `identity` <code>([Identity][]: nil)</code> - Expose [Workload Identity][] to
+  the task.
+
+- `kill_timeout` `(string: "5s")` - Specifies the duration to wait for an
+  application to gracefully quit before force-killing. Nomad first sends a
+  [`kill_signal`][kill_signal]. If the task does not exit before the configured
+  timeout, `SIGKILL` is sent to the task. Note that the value set here is capped
+  at the value set for [`max_kill_timeout`][max_kill] on the agent running the
+  task, which has a default value of 30 seconds.
+
+- `kill_signal` `(string)` - Specifies a configurable kill signal for a task,
+  where the default is SIGINT (or SIGTERM for `docker`, or CTRL_BREAK_EVENT
+  for `raw_exec` on Windows). Note that this is only supported for drivers
+  sending signals (currently `docker`, `exec`, `raw_exec`, and `java`
+  drivers).
+
+- `leader` `(bool: false)` - Specifies whether the task is the leader task of
+  the task group. If set to `true`, when the leader task completes, all other
+  tasks within the task group will be gracefully shutdown. The shutdown
+  process starts by applying the `shutdown_delay` if configured. It then stops the
+  the leader task first, followed by non-sidecar and non-poststop tasks,
+  and finally sidecar tasks. Once this process completes, post-stop tasks
+  are triggered. See the [lifecycle][] documentation for a complete description
+  of task lifecycle management.
+
+- `lifecycle` <code>([Lifecycle][]: nil)</code> - Specifies when a task is run
+  within the lifecycle of a task group. Added in Nomad v0.11.
+
+- `logs` <code>([Logs][]: nil)</code> - Specifies logging configuration for the
+  `stdout` and `stderr` of the task.
+
+- `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
+  with user-defined metadata.
+
+- `resources` <code>([Resources][]: &lt;required&gt;)</code> - Specifies the minimum
+  resource requirements such as RAM, CPU and devices.
+
+- `service` <code>([Service][]: nil)</code> - Specifies integrations with Nomad
+  or [Consul][] for service discovery. Nomad automatically registers when a task
+  is started and de-registers it when the task dies.
+
+- `shutdown_delay` `(string: "0s")` - Specifies the duration to wait when
+  killing a task between removing its service registrations from Consul or Nomad,
+  and sending it a shutdown signal. Ideally services would fail health checks
+  once they receive a shutdown signal. Alternatively, `shutdown_delay` may be
+  set to give in flight requests time to complete before shutting down. This
+  `shutdown_delay` only applies to services defined at the task level by the
+  [`service`](/nomad/docs/job-specification/task#service) block. In addition, task
+  groups have their own [`shutdown_delay`](/nomad/docs/job-specification/group#shutdown_delay)
+  which waits between de-registering group services and stopping tasks.
+
+- `user` `(string: <varies>)` - Specifies the user that will run the task.
+  Defaults to `nobody` for the [`exec`][exec] and [`java`][java] drivers.
+  [Docker][] images specify their own default users. This can only be set
+  on Linux platforms, and clients can restrict [which drivers][user_drivers]
+  are allowed to run tasks as [certain users][user_denylist].
+
+- `template` <code>([Template][]: nil)</code> - Specifies the set of templates
+  to render for the task. Templates can be used to inject both static and
+  dynamic configuration with data populated from environment variables, Consul
+  and Vault.
+
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
+
+- `volume_mount` <code>([VolumeMount][]: nil)</code> - Specifies where a group
+  volume should be mounted.
+
+- `kind` `(string: <varies>)` - Used internally to manage tasks according to
+  the value of this field. Initial use case is for Consul Connect.
+
+## `task` Examples
+
+The following examples only show the `task` blocks. Remember that the
+`task` block is only valid in the placements listed above.
+
+### Docker Container
+
+This example defines a task that starts a Docker container as a service. Docker
+is just one of many drivers supported by Nomad. Read more about drivers in the
+[Nomad drivers documentation](/nomad/docs/drivers).
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Metadata and Environment Variables
+
+This example uses custom metadata and environment variables to pass information
+to the task.
+
+```hcl
+task "server" {
+  driver = "exec"
+  config {
+    command = "/bin/env"
+  }
+
+  meta {
+    my-key = "my-value"
+  }
+
+  env {
+    MY_KEY = "${meta.my-key}"
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+### Service Discovery
+
+This example creates a service in Consul. To read more about service discovery
+in Nomad, please see the [Nomad service discovery documentation][service_discovery].
+
+```hcl
+task "server" {
+  driver = "docker"
+  config {
+    image = "hashicorp/http-echo"
+    args  = ["-text", "hello world"]
+  }
+
+  service {
+    tags = ["default"]
+
+    check {
+      type     = "tcp"
+      interval = "10s"
+      timeout  = "2s"
+    }
+  }
+
+  resources {
+    cpu = 20
+  }
+}
+```
+
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[consul]: https://www.consul.io/ 'Consul by HashiCorp'
+[consul_jobspec]: /nomad/docs/job-specification/consul
+[constraint]: /nomad/docs/job-specification/constraint 'Nomad constraint Job Specification'
+[affinity]: /nomad/docs/job-specification/affinity 'Nomad affinity Job Specification'
+[dispatchpayload]: /nomad/docs/job-specification/dispatch_payload 'Nomad dispatch_payload Job Specification'
+[env]: /nomad/docs/job-specification/env 'Nomad env Job Specification'
+[Identity]: /nomad/docs/job-specification/identity 'Nomad identity Job Specification'
+[meta]: /nomad/docs/job-specification/meta 'Nomad meta Job Specification'
+[resources]: /nomad/docs/job-specification/resources 'Nomad resources Job Specification'
+[lifecycle]: /nomad/docs/job-specification/lifecycle 'Nomad lifecycle Job Specification'
+[logs]: /nomad/docs/job-specification/logs 'Nomad logs Job Specification'
+[service]: /nomad/docs/job-specification/service 'Nomad service Job Specification'
+[vault]: /nomad/docs/job-specification/vault 'Nomad vault Job Specification'
+[volumemount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[exec]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java]: /nomad/docs/drivers/java 'Nomad Java Driver'
+[docker]: /nomad/docs/drivers/docker 'Nomad Docker Driver'
+[rkt]: /nomad/plugins/drivers/community/rkt 'Nomad rkt Driver'
+[service_discovery]: /nomad/docs/integrations/consul-integration#service-discovery 'Nomad Service Discovery'
+[template]: /nomad/docs/job-specification/template 'Nomad template Job Specification'
+[user_drivers]: /nomad/docs/configuration/client#user-checked_drivers
+[user_denylist]: /nomad/docs/configuration/client#user-denylist
+[max_kill]: /nomad/docs/configuration/client#max_kill_timeout
+[kill_signal]: /nomad/docs/job-specification/task#kill_signal
+[Workload Identity]: /nomad/docs/concepts/workload-identity 'Nomad Workload Identity'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/template.mdx b/content/nomad/v1.9.x/content/docs/job-specification/template.mdx
new file mode 100644
index 0000000000..7ab366fa23
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/template.mdx
@@ -0,0 +1,829 @@
+---
+layout: docs
+page_title: template Block - Job Specification
+description: |-
+  The "template" block instantiates an instance of a template renderer. This
+  creates a convenient way to ship configuration files that are populated from
+  environment variables, Consul data, Vault secrets, or just general
+  configurations within a Nomad task.
+---
+
+# `template` Block
+
+<Placement groups={['job', 'group', 'task', 'template']} />
+
+The `template` block instantiates an instance of a template renderer. This
+creates a convenient way to ship configuration files that are populated from
+environment variables, Consul data, Vault secrets, or just general
+configurations within a Nomad task.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      template {
+        source        = "local/redis.conf.tpl"
+        destination   = "local/redis.conf"
+        change_mode   = "signal"
+        change_signal = "SIGINT"
+      }
+    }
+  }
+}
+```
+
+Nomad utilizes [Go template][gt] and a tool called [Consul Template][ct], which
+adds a set of new functions that can be used to retrieve data from Consul and
+Vault. Nomad templates can reference [Nomad's runtime
+environment variables][env], [node attributes and metadata][nodevars],
+[Nomad service registrations][ct_api_nsvc], and [Nomad variables][nvars].
+Templates can also be used to provide environment variables to your workload.
+
+For a full list of the API template functions, please refer to the [Consul
+Template documentation][ct_api]. For a an introduction to Go templates, please
+refer to the [Learn Go Template Syntax][gt_learn] guide.
+
+## `template` Parameters
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the rendered template changes. Nomad will always write the new contents of
+  the template to the specified destination. The following possible values describe
+  Nomad's action after writing the template to disk.
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+  - `"script"` - run a script
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `change_script` <code>([`ChangeScript`][]: nil)</code> - Configures the script
+  triggered on template change. This option is required if the `change_mode` is
+  `script`.
+
+- `data` `(string: "")` - Specifies the raw template to execute. One of `source`
+  or `data` must be specified, but not both. This is useful for smaller
+  templates, but we recommend using `source` for larger templates.
+
+- `destination` `(string: <required>)` - Specifies the location where the
+  resulting template should be rendered, relative to the [task working
+  directory][]. Only drivers without filesystem isolation (ex. `raw_exec`) or
+  that build a chroot in the task working directory (ex. `exec`) can render
+  templates outside of the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+  `NOMAD_SECRETS_DIR`. For more details on how `destination` interacts with
+  task drivers, see the [Filesystem internals][] documentation. Note that where
+  possible, the `NOMAD_SECRETS_DIR` is mounted `noexec`, so rendered templates
+  can't be used as self-executing scripts.
+
+- `env` `(bool: false)` - Specifies the template should be read back in as
+  environment variables for the task ([example](#environment-variables)). To
+  update the environment on changes, you must set `change_mode` to
+  `restart`. Setting `env` when the `change_mode` is `signal` will return a
+  validation error. Setting `env` when the `change_mode` is `noop` is
+  permitted but will not update the environment variables in the task.
+
+- `error_on_missing_key` `(bool: false)` - Specifies how the template behaves
+  when attempting to index a map key that does not exist in the map.
+
+  - When `true`, the template engine will return an error, which will cause the
+    task to fail.
+
+  - When `false`, the template engine will do nothing and continue executing the
+    template.	If printed, the result of the index operation is the string
+	  "<no value\>".
+
+- `left_delimiter` `(string: "{{")` - Specifies the left delimiter to use in the
+  template. The default is "{{" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `perms` `(string: "644")` - Specifies the rendered template's permissions.
+  File permissions are given as octal of the Unix file permissions `rwxrwxrwx`.
+
+- `uid` `(int: nil)` - Specifies the rendered template owner's user ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent user will be used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `gid` `(int: nil)` - Specifies the rendered template owner's group ID. If
+  negative or not specified (`nil`) the ID of the Nomad agent group will be
+  used.
+
+  ~> **Caveat:** Works only on Unix-based systems. Be careful when using
+  containerized drivers, such as `docker` or `podman`, as groups and users
+  inside the container may have different IDs than on the host system. This
+  feature will also **not** work with Docker Desktop.
+
+- `right_delimiter` `(string: "}}")` - Specifies the right delimiter to use in the
+  template. The default is "}}" for some templates, it may be easier to use a
+  different delimiter that does not conflict with the output file itself.
+
+- `source` `(string: "")` - Specifies the path to the template to be rendered.
+  One of `source` or `data` must be specified, but not both. This source can be
+  fetched using an [`artifact`][artifact] resource. The template must exist in
+  the [task working directory][] prior to starting the task; it is not possible
+  to reference a template whose source is inside a Docker container, for
+  example.
+
+- `splay` `(string: "5s")` - Specifies a random amount of time to wait between
+  0 ms and the given splay value before invoking the change mode. This is
+  specified using a label suffix like "30s" or "1h", and is often used to
+  prevent a thundering herd problem where all task instances restart at the same
+  time.
+
+- `wait` `(Code: nil)` - Defines the minimum and maximum amount of time to wait
+  for the Consul cluster to reach a consistent state before rendering a template.
+  This is useful to enable in systems where network connectivity to Consul is degraded,
+  because it will reduce the number of times a template is rendered. This setting
+  can be overridden by the [`client.template.wait_bounds`]. If the template
+  configuration has a `min` lower than `client.template.wait_bounds.min` or a `max`
+  greater than `client.template.wait_bounds.max`, the client's bounds will be enforced,
+  and the template `wait` will be adjusted before being sent to the template
+  engine.
+
+  ```hcl
+  wait {
+    min     = "5s"
+    max     = "10s"
+  }
+  ```
+
+- `vault_grace` `(string: "15s")` - [Deprecated](https://github.com/hashicorp/consul-template/issues/1268)
+
+## `template` Examples
+
+The following examples only show the `template` blocks. Remember that the
+`template` block is only valid in the placements listed above.
+
+### Inline Template
+
+This example uses an inline template to render a file to disk. This file watches
+various keys in Consul for changes:
+
+```hcl
+template {
+  data        = "---\nkey: {{ key \"service/my-key\" }}"
+  destination = "local/file.yml"
+}
+```
+
+It is also possible to use heredocs for multi-line templates, like:
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    bind_port:   {{ env "NOMAD_PORT_db" }}
+    scratch_dir: {{ env "NOMAD_TASK_DIR" }}
+    node_id:     {{ env "node.unique.id" }}
+    service_key: {{ key "service/my-key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Remote Template
+
+This example uses an [`artifact`][artifact] block to download an input template
+before passing it to the template engine:
+
+```hcl
+artifact {
+  source      = "https://example.com/file.yml.tpl"
+  destination = "local/file.yml.tpl"
+}
+
+template {
+  source      = "local/file.yml.tpl"
+  destination = "local/file.yml"
+}
+```
+
+### Task `meta` values
+
+To render values from a task's `meta` config, use the environment variable form
+of the meta variable name.
+
+```hcl
+meta {
+  mykey = "some_value"
+}
+
+template {
+  data = <<EOH
+  {{ env "NOMAD_META_mykey" }}
+EOH
+}
+```
+
+### Node Variables
+
+Use the `env` function to access the Node's attributes and metadata inside a
+template. Note the `meta.` syntax here applies only to node meta fields.
+
+```hcl
+template {
+  data = <<EOH
+  ---
+    node_dc:    {{ env "node.datacenter" }}
+    node_cores: {{ env "attr.cpu.numcores" }}
+    meta_key:   {{ env "meta.node_meta_key" }}
+  EOH
+
+  destination = "local/file.yml"
+}
+```
+
+### Environment Variables
+
+Templates may be used to create environment variables for tasks. These templates
+work exactly like other templates except once the templates are written, they
+are parsed as `KEY=value` pairs. Those key value pairs are included in the
+task's environment.
+
+For example the following template block:
+
+```hcl
+template {
+  data = <<EOH
+# Lines starting with a # are ignored
+
+# Empty lines are also ignored
+LOG_LEVEL="{{key "service/geo-api/log-verbosity"}}"
+API_KEY="{{with secret "secret/geo-api-key"}}{{.Data.value}}{{end}}"
+EOH
+
+  destination = "secrets/file.env"
+  env         = true
+}
+```
+
+The task's environment would then have environment variables like the
+following:
+
+```text
+LOG_LEVEL=DEBUG
+API_KEY=12345678-1234-1234-1234-1234-123456789abc
+```
+
+This allows [12factor app](https://12factor.net/config) style environment
+variable based configuration while keeping all the familiar features and
+semantics of Nomad templates.
+
+Secrets or certificates may contain a wide variety of characters such as
+newlines, quotes, and backslashes which may be difficult to quote or escape
+properly.
+
+Whenever a templated variable may include special characters, use the `toJSON`
+function to ensure special characters are properly parsed by Nomad.
+
+```hcl
+CERT_PEM={{ file "path/to/cert.pem" | toJSON }}
+```
+
+The parser will read the JSON string, so the `$CERT_PEM` environment variable
+will be identical to the contents of the file.
+
+Likewise, when evaluating a password that may contain quotes or `#`, use the
+`toJSON` function to ensure Nomad passes the password to the task unchanged.
+
+```hcl
+# Passwords may contain any character including special characters like:
+#   \"'#
+# Use toJSON to ensure Nomad passes them to the environment unchanged.
+{{ with secret "secrets/data/application/backend" }}
+DB_PASSWD={{ .Data.data.DB_PASSWD | toJSON }}
+{{ end }}
+```
+
+For more details see [go-envparser's README][go-envparse].
+
+### Template Destinations
+
+Templates are rendered into the task working directory. Drivers without
+filesystem isolation (such as `raw_exec`) or drivers that build a chroot in
+the task working directory (such as `exec`) can have templates rendered to
+arbitrary paths in the task. But task drivers such as `docker` can only access
+templates rendered into the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, or
+`NOMAD_SECRETS_DIR`. To work around this restriction, you can create a mount
+from the template `destination` to another location in the task.
+
+```hcl
+task "task" {
+  driver = "docker"
+
+  config {
+    image = "redis:6.0"
+    mount {
+      type   = "bind"
+      source = "local"
+      target = "/etc/redis.d"
+    }
+  }
+
+  template {
+    destination = "local/redis.conf"
+  }
+}
+```
+
+### Dependencies
+
+For templates that read from Vault, Consul, or Nomad, each item read is called a
+"dependency". All the `template` blocks share the same internal runner which
+de-duplicates dependencies requesting the same item. You should avoid having
+large numbers of dependencies for a given task, as each dependency requires at
+least one concurrent request (a possibly blocking query) to the upstream
+server. If a task has more than 128 dependencies, a warn-level log will appear
+in the Nomad client logs which reports "watching this many dependencies could
+DDoS your servers", referring to the Vault, Consul, or Nomad cluster being
+queried.
+
+## Nomad Integration
+
+### Nomad Services
+
+Nomad service registrations can be queried using the `nomadService` and
+`nomadServices` functions. The requests are tied to the same namespace as the
+job which contains the template block.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single NGINX upstream service.
+upstream my_app {
+  {{- range nomadService "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services registered in Nomad as an NGINX upstream
+# service.
+{{ range nomadServices }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range nomadService .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+### Simple Load Balancing with Nomad Services
+
+The `nomadService` function now supports simple load balancing by selecting
+instances of a service via [rendezvous hashing][rhash].
+To enable simple load balancing, the `nomadService` function requires 3 arguments.
+
+- The number of services to select
+- The hashing key (should be unique, but consistent per requester)
+- The service name
+
+By using `NOMAD_ALLOC_ID` as the hashing key, the selected instances will remain
+mostly stable for the allocation. Each time the template is run, `nomadService`
+will return the same set of instances for each allocation - unless N instances of
+the service are added or removed, in which case there is a 1/N chance of a selected
+instance being replaced. This helps maintain a more consistent output when rendering
+configuration files, triggering fewer restarts and signaling of Nomad tasks.
+
+```hcl
+template {
+  data        = <<EOH
+# Configuration for 1 redis instances, as assigned via rendezvous hashing.
+{{$allocID := env "NOMAD_ALLOC_ID" -}}
+{{range nomadService 1 $allocID "redis"}}
+  server {{ .Address }}:{{ .Port }};
+{{- end}}
+EOH
+}
+```
+
+### Nomad Variables
+
+<Warning>
+
+Using the Nomad integration results in an implicit dependency on the Nomad
+servers. If the Nomad servers are unavailable (for example, a client is
+disconnected), then after some retries, running allocations will be
+stopped. Refer to the [`template.nomad_retry`][] client configuration option for
+more details and to adjust the retry behaviour.
+
+</Warning>
+
+Nomad [variables][] can be queried using the `nomadVar`, `nomadVarList`,
+`nomadVarListSafe`, and `nomadVarExists` functions.
+
+#### `nomadVarList` and `nomadVarListSafe`
+
+These functions can be used to list the paths of Nomad variables available to
+the task based on its [workload identity]. You can provide an optional prefix to
+filter the path list by as a parameter.
+
+The list functions return a slice of `NomadVarMeta` type:
+
+```golang
+type NomadVarMeta struct {
+  Namespace, Path          string
+  CreateIndex, ModifyIndex uint64
+  CreateTime, ModifyTime   nanoTime
+}
+```
+
+The `nanoTime` type contains Unix nanoseconds since the epoch. Its string method
+prints it out as a formatted date/time value. It also has a `Time` method that
+can be used to retrieve a Go [`time.Time`] for further manipulation.
+
+`NomadVarMeta` objects print their `Path` value when used as a string. For
+example, these two template blocks produce identical output.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ . }}
+{{ end }}
+EOH
+}
+
+template {
+  data        = <<EOH
+{{ range nomadVarList }}
+  {{ .Path }}
+{{ end }}
+EOH
+}
+```
+
+You can provide a prefix to filter the path list as an optional parameter to the
+`nomadVarList` function.
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVarList` will list variables in the same namespace as the
+task. The path filter can change the namespace by adding a suffix separated by
+the `@` character:
+
+```hcl
+template {
+  data        = <<EOH
+{{ range nomadVarList "path/to/filter@example_namespace" }}
+  {{ . }}
+{{ end }}
+EOH
+}
+```
+
+The `nomadVarListSafe` function works identically to `nomadVarList`, but refuses
+to render the template if the variable list query returns blank/empty data.
+
+#### `nomadVar`
+
+These functions can be used to a read Nomad variable, assuming the task has
+access rights to the variable based on the task's [workload identity]. If the
+path does not exist or the caller does not have access to it, the `template`
+renderer will block until the path is available. To avoid blocking, wrap
+`nomadVar` calls with [`nomadVarExists`](#nomadvarexists).
+
+The `nomadVar` function returns a map of `string` to `NomadVarItems`
+structs. Each member of the map corresponds to a member of the variable's
+`Items` collection.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, with a
+single key/value pair in its Items collection—`maxconns`:`15`
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+renders
+
+```text
+15
+```
+
+Each map value also contains helper methods to get the variable metadata and a
+link to the parent variable:
+
+- `Keys`: produces a sorted list of keys to this `NomadVarItems` map.
+
+- `Values`: produces a key-sorted list.
+
+- `Tuples`: produces a key-sorted list of K,V tuple structs, with accessors `.K` and `.V` for the key and value respectively.
+
+- `Metadata`: returns this collection's parent metadata as a `NomadVarMeta`
+
+- `Parent`: returns a parent object that has a Metadata field referring to the
+  `NomadVarMeta` and an Items field that refers to this `NomadVarItems` object.
+
+For example, given a variable exists at the path `nomad/jobs/redis`, you could
+render some of its metadata as follows:
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis" }}
+Path:       {{ .Metadata.Path }}
+Namespace:  {{ .Metadata.Namespace }}
+CreateTime: {{ .Metadata.CreateTime }}
+ModifyTime: {{ .Metadata.ModifyTime }}
+{{ end }}
+EOH
+}
+```
+
+By default, the `nomadVar` function reads a variable in the same namespace as
+the task. The path filter can change the namespace by adding a suffix separated
+by the `@` character.
+
+```hcl
+template {
+  data        = <<EOH
+{{ with nomadVar "nomad/jobs/redis@example_namespace" }}{{ .maxconns }}{{ end }}
+EOH
+}
+```
+
+#### `nomadVarExists`
+
+This function can be used to check if a Nomad variable exists at the provided
+path, assuming the task has access rights to the variable based on the task's
+[workload identity]. If a variable exists, this will return true, false
+otherwise. Unlike [`nomadVar`](#nomadvar), this function will not block if the
+variable does not exist, which can be useful for controlling flow.
+
+For example:
+
+```hcl
+template {
+  data        = <<EOH
+{{ if nomadVarExists "app/beta_active" }}
+  # ...
+{{ else }}
+  # ...
+{{ end }}
+EOH
+}
+```
+
+## Consul Integration
+
+<Warning>
+
+Using the Consul integration results in an implicit dependency on Consul. If
+Consul is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.consul_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### Consul KV
+
+Consul KV values can be accessed using the [`key`][ct_api_key] function to
+retrieve a single value from a key path. The [`ls`][ct_api_ls] function can be
+used to retrieve all keys in a path. For deeply nested paths, use the
+[`tree`][ct_api_tree] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Read single key from Consul KV.
+APP_NAME = "{{key "app/name"}}"
+
+# Read all keys in the path `app/environment` from Consul KV.
+{{range ls "app/environment"}}
+{{.Key}}={{.Value}}
+{{end}}
+    EOF
+
+    destination = "local/env"
+    env         = true
+  }
+```
+
+### Consul Services
+
+The Consul service catalog can be queried using the [`service`][ct_api_service]
+and [`services`][ct_api_services] functions. For Connect-capable services, use
+the [`connect`][ct_api_connect] function.
+
+```hcl
+  template {
+    data = <<EOF
+# Configuration for a single upstream service.
+upstream my_app {
+  {{- range service "my-app" }}
+  server {{ .Address }}:{{ .Port }};{{- end }}
+}
+
+# Configuration for all services in the catalog.
+{{ range services }}
+# Configuration for service {{ .Name }}.
+upstream {{ .Name | toLower }} {
+  {{- range service .Name }}
+  server {{ .Address}}:{{ .Port }};{{- end }}
+}
+{{ end -}}
+    EOF
+
+    destination = "local/nginx.conf"
+  }
+```
+
+## Vault Integration
+
+<Warning>
+
+Using the Vault integration results in an implicit dependency on Vault. If
+Vault is unavailable, then after some retries, running allocations will be
+stopped. Refer to the [`template.vault_retry`][] client configuration option
+for more details and to adjust the retry behaviour.
+
+</Warning>
+
+### PKI Certificate
+
+Vault is a popular open source tool for managing secrets. In addition to acting
+as an encrypted KV store, Vault can also generate dynamic secrets, like PKI/TLS
+certificates.
+
+When generating PKI certificates with Vault, the certificate, private key, and
+any intermediate certs are all returned as part of the same API call. Most
+software requires these files be placed in separate files on the system.
+
+#### As individual files
+
+For templates, all dependencies are mapped into a single list. This means that
+multiple templates watching the same path return the same data.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Cert -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/certificate.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .CA -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/ca.crt"
+  change_mode   = "restart"
+}
+
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" }}
+{{- .Key -}}
+{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/private_key.key"
+  change_mode   = "restart"
+}
+```
+
+These are three different input templates, but when run under the Nomad job,
+they are compressed into a single call, sharing the resulting data.
+
+#### As a PEM formatted file
+
+This example acquires a PKI certificate from Vault in PEM format, concatenates
+the elements into a bundle, and stores it into your application's secret
+directory.
+
+```hcl
+template {
+  data = <<EOH
+{{ with pkiCert "pki/issue/foo" "common_name=foo.service.consul" "ip_sans=127.0.0.1" "format=pem" }}
+{{ .Cert }}
+{{ .CA }}
+{{ .Key }}{{ end }}
+EOH
+  destination   = "${NOMAD_SECRETS_DIR}/bundle.pem"
+  change_mode   = "restart"
+}
+```
+
+### Vault KV API v1
+
+Under Vault KV API v1, paths start with `secret/`, and the response returns the
+raw key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/aws/s3"}}{{.Data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Note that if the name of a secret includes the `-` character, you must access
+it by index. This secret was set using `vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/app"}}{{index .Data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+### Vault KV API v2
+
+Under Vault KV API v2, paths start with `secret/data/`, and the response returns
+metadata in addition to key/value data. This secret was set using
+`vault kv put secret/aws/s3 aws_access_key_id=somekeyid`.
+
+```hcl
+  template {
+    data = <<EOF
+      AWS_ACCESS_KEY_ID = "{{with secret "secret/data/aws/s3"}}{{.Data.data.aws_access_key_id}}{{end}}"
+    EOF
+  }
+```
+
+Notice the addition of `data` in both the path and the field accessor string.
+Additionally, when using the Vault v2 API, the Vault policies applied to your
+Nomad jobs will need to grant permissions to `read` under `secret/data/...`
+rather than `secret/...`.
+
+Like KV API v1, if the name of a secret includes the `-` character, you must
+access it by index. This secret was set using
+`vault kv put secret/app db-password=somepassword`.
+
+```hcl
+  template {
+    data = <<EOF
+      DB_PASSWORD = "{{with secret "secret/data/app"}}{{index .Data.data "db-password"}}{{end}}"
+    EOF
+  }
+```
+
+## Client Configuration
+
+The `template` block has the following [client configuration
+options](/nomad/docs/configuration/client#options):
+
+- `function_denylist` `([]string: ["plugin"])` - Specifies a list of template
+  rendering functions that should be disallowed in job specs. By default, the
+  `plugin` function is disallowed as it allows running arbitrary commands on the
+  host as root (unless Nomad is configured to run as a non-root user),
+  `executeTemplate` is disallowed to prevent accidental or malicious infinitely
+  recursive execution, and `writeToFile` is disallowed.
+
+- `disable_file_sandbox` `(bool: false)` - Allows templates access to arbitrary
+  files on the client host via the `file` function. By default, templates can
+  access files only within the [task working directory].
+
+[`changescript`]: /nomad/docs/job-specification/change_script 'Nomad change_script Job Specification'
+[ct]: https://github.com/hashicorp/consul-template 'Consul Template by HashiCorp'
+[ct_api]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md 'Consul Template API by HashiCorp'
+[ct_api_connect]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#connect 'Consul Template API by HashiCorp - connect'
+[ct_api_key]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#key 'Consul Template API by HashiCorp - key'
+[ct_api_ls]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#ls 'Consul Template API by HashiCorp - ls'
+[ct_api_service]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#service 'Consul Template API by HashiCorp - service'
+[ct_api_services]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#services 'Consul Template API by HashiCorp - services'
+[ct_api_nsvc]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#nomadService 'Consul Template API by HashiCorp - nomadService'
+[nvars]: /nomad/docs/concepts/variables 'Nomad Variables'
+[ct_api_tree]: https://github.com/hashicorp/consul-template/blob/master/docs/templating-language.md#tree 'Consul Template API by HashiCorp - tree'
+[gt]: https://pkg.go.dev/text/template 'Go template package'
+[gt_learn]: /nomad/tutorials/templates/go-template-syntax
+[artifact]: /nomad/docs/job-specification/artifact 'Nomad artifact Job Specification'
+[env]: /nomad/docs/runtime/environment 'Nomad Runtime Environment'
+[nodevars]: /nomad/docs/runtime/interpolation#interpreted_node_vars 'Nomad Node Variables'
+[go-envparse]: https://github.com/hashicorp/go-envparse#readme 'The go-envparse Readme'
+[task working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
+[filesystem internals]: /nomad/docs/concepts/filesystem#templates-artifacts-and-dispatch-payloads
+[`client.template.wait_bounds`]: /nomad/docs/configuration/client#wait_bounds
+[rhash]: https://en.wikipedia.org/wiki/Rendezvous_hashing
+[variables]: /nomad/docs/concepts/variables
+[workload identity]: /nomad/docs/concepts/workload-identity
+[`time.Time`]: https://pkg.go.dev/time#Time
+[`template.nomad_retry`]: /nomad/docs/configuration/client#nomad_retry
+[`template.consul_retry`]: /nomad/docs/configuration/client#consul_retry
+[`template.vault_retry`]: /nomad/docs/configuration/client#vault_retry
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/transparent_proxy.mdx b/content/nomad/v1.9.x/content/docs/job-specification/transparent_proxy.mdx
new file mode 100644
index 0000000000..be940c77b6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/transparent_proxy.mdx
@@ -0,0 +1,177 @@
+---
+layout: docs
+page_title: transparent_proxy Block - Job Specification
+description: |-
+  The "transparent_proxy" block allows specifying options for configuring Envoy
+  in Consul Connect transparent proxy mode.
+---
+
+# `transparent_proxy` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'transparent_proxy',
+  ]}
+/>
+
+The `transparent_proxy` block configures the Envoy sidecar proxy to act as a
+Consul Connect [transparent proxy][tproxy]. This simplifies the configuration of
+Consul Connect by eliminating the need to configure [`upstreams`][] blocks in
+Nomad. Instead, the Envoy proxy will determines its configuration entirely from
+Consul [service intentions][].
+
+When transparent proxy is enabled traffic will automatically flow through the
+Envoy proxy. If the local Consul agent is serving DNS, Nomad will also set up
+the task's nameservers to use Consul. This lets your workload use the [virtual
+IP][] DNS name from Consul, rather than configuring a `template` block that
+queries services.
+
+Using transparent proxy has some important restrictions:
+
+* You can only have a single `connect` block in any task group that uses
+  transparent proxy.
+* You cannot set a [`network.dns`][] block on the allocation (unless you set
+  [`no_dns`](#no_dns), see below).
+* The node where the allocation is placed must be configured as described in
+  the Service Mesh integration documentation for [Transparent Proxy][].
+* The workload's task cannot use the same Unix user ID (UID) as the Envoy
+  sidecar proxy.
+
+## `transparent_proxy` Parameters
+
+* `exclude_inbound_ports` `([]string: nil)` - A list of inbound ports to exclude
+  from the inbound traffic redirection. This allows traffic on these ports to
+  bypass the Envoy proxy. These ports can be specified as either [network port
+  labels][port_labels] or as numeric ports. Nomad will automatically add the
+  following to this list:
+  * The [`local_path_port`][] of any [`expose`][] block.
+  * The port of any service check with [`expose=true`][check_expose] set.
+  * The port of any `network.port` with a [`static`][] value.
+* `exclude_outbound_cidrs` `([]string: nil)` - A list of CIDR subnets that
+  should be excluded from outbound traffic redirection. This allows traffic to
+  these subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_ports`; CIDR subnets listed here are excluded regardless of
+  the port.
+* `exclude_outbound_ports` `([]int: nil)` - A list of port numbers that should
+  be excluded from outbound traffic redirection. This allows traffic to these
+  subnets to bypass the Envoy proxy. Note this is independent of
+  `exclude_outbound_cidrs`; ports listed here are excluded regardless of the
+  CIDR.
+* `exclude_uids` `([]string: nil)` - A list of Unix user IDs (UIDs) that should
+  be excluded from outbound traffic redirection. When unset, only the Envoy
+  proxy's user will be allowed to bypass the iptables rule.
+* `no_dns` `(bool: false)` - By default, Consul will be set as the nameserver
+  for the workload and IP tables rules will redirect DNS queries to Consul. If
+  you want only external DNS, set `no_dns=true`. You will need to add your own
+  CIDR and port exclusions for your DNS nameserver. You cannot set
+  [`network.dns`][] if `no_dns=false`.
+* `outbound_port` `(int: 15001)` - The port that Envoy will bind on inside the
+  network namespace. The iptables rules created by `consul-cni` will force
+  traffic to flow to this port. You should only set this value if you have
+  specifically set the [`outbound_listener_port`][] in your Consul proxy
+  configuration. You can change the default value for a given node via [client
+  metadata](#client-metadata) (see below).
+* `uid` `(string "101")` - The Unix user ID (UID) used by the Envoy proxy. You
+  should only set this value if you have a custom build of the Envoy container
+  image which uses a different UID. You can change the default value for a given
+  node via [client metadata](#client-metadata) (see below). Note that your
+  workload's task cannot use the same UID as the Envoy sidecar proxy.
+
+## Client Metadata
+
+You can change the default [`outbound_port`](#outbound_port) and [`uid`](#uid)
+for a given client node by updating the node metadata via the [`nomad node meta
+apply`][] command. The attributes that can be updated are:
+
+* `connect.transparent_proxy.default_uid`: Sets the default value of
+  [`uid`](#uid) for this node.
+* `connect.transparent_proxy.default_outbound_port`: Sets the default value of
+  [`outbound_port`](#outbound_port) for this node.
+
+For example, to set the default value for the `uid` field to 120:
+
+```shell-session
+$ nomad node meta apply connect.transparent_proxy.default_uid=120
+$ nomad node meta read -json | jq -r '.Dynamic | ."connect.transparent_proxy.default_uid"'
+120
+```
+
+You should not normally need to set these values unless you are using custom
+Envoy images.
+
+## Examples
+
+### Minimal Example
+
+The following example is a minimal transparent proxy specification. Note that
+with transparent proxy, you will not need to configure an `upstreams` block.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+    }
+  }
+}
+```
+
+If you had a downstream task group `count-dashboard` that needed to connect to
+an upstream task group `count-api` listening on port 9001, you could create a
+Consul service intention with the following specification:
+
+```hcl
+Kind = "service-intentions"
+Name = "count-api"
+Sources = [
+  {
+    Name   = "count-dashboard"
+    Action = "allow"
+  }
+]
+```
+
+And then the downstream service `count-dashboard` could reach the `count-api`
+service by making requests to `http://count-api.virtual.consul`.
+
+### External DNS
+
+The following example is a transparent proxy specification where external DNS is
+used. To find the address of other allocations in this configuration, you will
+need to use a [`template`][] block to query Consul.
+
+```hcl
+sidecar_service {
+  proxy {
+    transparent_proxy {
+      excluded_outbound_ports = [53]
+      excluded_outbound_cidrs = ["208.67.222.222/32", "208.67.220.220/32"]
+      no_dns                  = true
+    }
+  }
+}
+```
+
+[tproxy]: /consul/docs/k8s/connect/transparent-proxy
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[service intentions]: /consul/docs/connect/config-entries/service-intentions
+[virtual IP]: /consul/docs/services/discovery/dns-static-lookups#service-virtual-ip-lookups
+[`consul-cni`]: https://releases.hashicorp.com/consul-cni
+[cni_plugins]: /nomad/docs/networking/cni#cni-reference-plugins
+[consul_dns_port]: /consul/docs/agent/config/config-files#dns_port
+[`recursors`]: /consul/docs/agent/config/config-files#recursors
+[port_labels]: /nomad/docs/job-specification/network#port-parameters
+[`local_path_port`]: /nomad/docs/job-specification/expose#local_path_port
+[`expose`]: /nomad/docs/job-specification/expose
+[check_expose]: /nomad/docs/job-specification/service#expose
+[`static`]: /nomad/docs/job-specification/network#static
+[`outbound_listener_port`]: /consul/docs/connect/proxies/proxy-config-reference#outbound_listener_port
+[`template`]: /nomad/docs/job-specification/template#consul-integration
+[`nomad node meta apply`]: /nomad/docs/commands/node/meta/apply
+[`network.dns`]: /nomad/docs/job-specification/network#dns-parameters
+[Transparent Proxy]: /nomad/docs/integrations/consul/service-mesh#transparent-proxy
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/ui.mdx b/content/nomad/v1.9.x/content/docs/job-specification/ui.mdx
new file mode 100644
index 0000000000..c9792168b2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/ui.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: ui Block - Job Specification
+description: |-
+  The "ui" block allows lets users add description and helpful links to their
+  job page in the Nomad Web UI.
+---
+
+# `ui` Block
+
+<Placement
+  groups={[
+    ['job', 'ui'],
+  ]}
+/>
+
+The `ui` block provides options to modify the presentation of the Job index page
+in the Web UI. When specified, a description and any number of links will be
+added to the top of the job page in question.
+
+The following will provide the Web UI with a job description and a pair of links:
+
+## `ui` Parameters
+
+- `description` `(string: "")` - The markdown-enabled description of the job. We
+  support [GitHub Flavored Markdown](https://github.github.com/gfm/).
+- `link` `(map<string|string>: nil)` - A link that should show up in the header
+  of the job index page in the Web UI. A job can have any number of links, and
+  they must contain both a string `label` and `url`.
+
+## `ui` Example
+
+```hcl
+job "docs" {
+  ui {
+    description = "A job that uses **Nomad Variables**"
+    link {
+      label = "Learn more about Nomad"
+      url   = "https://developer.hashicorp.com/nomad"
+    }
+    link {
+      label = "Nomad on GitHub"
+      url   = "https://github.com/hashicorp/nomad"
+    }
+  }
+  # ...
+}
+```
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/update.mdx b/content/nomad/v1.9.x/content/docs/job-specification/update.mdx
new file mode 100644
index 0000000000..3e1243a165
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/update.mdx
@@ -0,0 +1,275 @@
+---
+layout: docs
+page_title: update Block - Job Specification
+description: |-
+  The "update" block specifies the group's update strategy. The update strategy
+  is used to control things like rolling upgrades and canary deployments. If
+  omitted, a default update strategy is applied.
+---
+
+# `update` Block
+
+<Placement
+  groups={[
+    ['job', 'update'],
+    ['job', 'group', 'update'],
+  ]}
+/>
+
+The `update` block specifies the group's update strategy. The update strategy
+is used to control things like [rolling upgrades][rolling] and [canary
+deployments][canary]. If omitted, a default update strategy is applied. If
+specified at the job level, the configuration will apply to all groups within
+the job. If multiple `update` blocks are specified, they are merged with the
+group block taking the highest precedence and then the job.
+
+```hcl
+job "docs" {
+  update {
+    max_parallel      = 3
+    health_check      = "checks"
+    min_healthy_time  = "10s"
+    healthy_deadline  = "5m"
+    progress_deadline = "10m"
+    auto_revert       = true
+    auto_promote      = true
+    canary            = 1
+    stagger           = "30s"
+  }
+}
+```
+
+~> For `system` jobs, only [`max_parallel`](#max_parallel) and
+[`stagger`](#stagger) are enforced. The job is updated at a rate of
+`max_parallel`, waiting `stagger` duration before the next set of updates.
+The `system` scheduler will be updated to support the new `update` block in
+a future release.
+
+## `update` Parameters
+
+- `max_parallel` `(int: 1)` - Specifies the number of allocations within a task group that can be
+  updated at the same time. The task groups themselves are updated in parallel.
+
+  - `max_parallel = 0` - Specifies that the allocation should use forced updates instead of deployments
+
+- `health_check` `(string: "checks")` - Specifies the mechanism in which
+  allocations health is determined. The potential values are:
+
+  - "checks" - Specifies that the allocation should be considered healthy when
+    all of its tasks are running and their associated [checks][] are healthy,
+    and unhealthy if any of the tasks fail or not all checks become healthy.
+    This is a superset of "task_states" mode.
+
+  - "task_states" - Specifies that the allocation should be considered healthy when
+    all its tasks are running and unhealthy if tasks fail.
+
+  - "manual" - Specifies that Nomad should not automatically determine health
+    and that the operator will specify allocation health using the [HTTP
+    API](/nomad/api-docs/deployments#set-allocation-health-in-deployment).
+
+- `min_healthy_time` `(string: "10s")` - Specifies the minimum time the
+  allocation must be in the healthy state before it is marked as healthy and
+  unblocks further allocations from being updated. This is specified using a
+  label suffix like "30s" or "15m".
+
+- `healthy_deadline` `(string: "5m")` - Specifies the deadline in which the
+  allocation must be marked as healthy after which the allocation is
+  automatically transitioned to unhealthy. This is specified using a label suffix
+  like "2m" or "1h". If [`progress_deadline`](#progress_deadline) is non-zero, it
+  must be greater than `healthy_deadline`. Otherwise the `progress_deadline` may
+  fail a deployment before an allocation reaches its `healthy_deadline`.
+
+- `progress_deadline` `(string: "10m")` - Specifies the deadline in which an
+  allocation must be marked as healthy. The deadline begins when the first
+  allocation for the deployment is created and is reset whenever an allocation
+  as part of the deployment transitions to a healthy state or when a
+  deployment is manually promoted. If no allocation transitions to the healthy
+  state before the progress deadline, the deployment is marked as failed. If
+  the `progress_deadline` is set to `0`, the first allocation to be marked as
+  unhealthy causes the deployment to fail. This is specified using a label
+  suffix like "2m" or "1h".
+
+- `auto_revert` `(bool: false)` - Specifies if the job should auto-revert to the
+  last stable job on deployment failure. A job is marked as stable if all the
+  allocations as part of its deployment were marked healthy.
+
+- `auto_promote` `(bool: false)` - Specifies if the job should auto-promote to
+  the canary version when all canaries become healthy during a
+  deployment. Defaults to false which means canaries must be manually updated
+  with the `nomad deployment promote` command. If a job has multiple task
+  groups, all must be set to `auto_promote = true` in order for the deployment
+  to be promoted automatically.
+
+- `canary` `(int: 0)` - Specifies that changes to the job that would result in
+  destructive updates should create the specified number of canaries without
+  stopping any previous allocations. Once the operator determines the canaries
+  are healthy, they can be promoted which unblocks a rolling update of the
+  remaining allocations at a rate of `max_parallel`. Canary deployments cannot
+  be used with volumes when `per_alloc = true`.
+
+- `stagger` `(string: "30s")` - Specifies the delay between each set of
+  [`max_parallel`](#max_parallel) updates when updating system jobs. This
+  setting doesn't apply to service jobs which use
+  [deployments][strategies] instead, with the equivalent parameter being [`min_healthy_time`](#min_healthy_time). 
+
+## `update` Examples
+
+The following examples only show the `update` blocks. Remember that the
+`update` block is only valid in the placements listed above.
+
+### Parallel Upgrades Based on Checks
+
+This example performs 3 upgrades at a time and requires the allocations be
+healthy for a minimum of 30 seconds before continuing the rolling upgrade. Each
+allocation is given at most 2 minutes to determine its health before it is
+automatically marked unhealthy and the deployment is failed.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+}
+```
+
+### Parallel Upgrades Based on Task State
+
+This example is the same as the last but only requires the tasks to be healthy
+and does not require registered service checks to be healthy.
+
+```hcl
+update {
+  max_parallel     = 3
+  min_healthy_time = "30s"
+  healthy_deadline = "2m"
+  health_check     = "task_states"
+}
+```
+
+### Canary Upgrades
+
+This example creates a canary allocation when the job is updated. The canary is
+created without stopping any previous allocations from the job and allows
+operators to determine if the new version of the job should be rolled out.
+
+```hcl
+update {
+  canary       = 1
+  max_parallel = 3
+}
+```
+
+Once the operator has determined the new job should be deployed, the deployment
+can be promoted and a rolling update will occur performing 3 updates at a time
+until the remainder of the groups allocations have been rolled to the new
+version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Blue/Green Upgrades
+
+By setting the canary count equal to that of the task group, blue/green
+deployments can be achieved. When a new version of the job is submitted, instead
+of doing a rolling upgrade of the existing allocations, the new version of the
+group is deployed along side the existing set. While this duplicates the
+resources required during the upgrade process, it allows very safe deployments
+as the original version of the group is untouched.
+
+```hcl
+group "api-server" {
+    count = 3
+
+    update {
+      canary       = 3
+      max_parallel = 3
+    }
+    ...
+}
+```
+
+Once the operator is satisfied that the new version of the group is stable, the
+group can be promoted which will result in all allocations for the old versions
+of the group to be shutdown. This completes the upgrade from blue to green, or
+old to new version.
+
+```text
+# Promote the canaries for the job.
+$ nomad job promote <job-id>
+```
+
+### Serial Upgrades
+
+This example uses a serial upgrade strategy, meaning exactly one task group will
+be updated at a time. The allocation must be healthy for the default
+`min_healthy_time` of 10 seconds.
+
+```hcl
+update {
+  max_parallel = 1
+}
+```
+
+### Update Block Inheritance
+
+This example shows how inheritance can simplify the job when there are multiple
+task groups.
+
+```hcl
+job "example" {
+  ...
+
+  update {
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+
+  group "one" {
+    ...
+
+    update {
+      canary = 1
+    }
+  }
+
+  group "two" {
+    ...
+
+    update {
+      min_healthy_time = "3m"
+    }
+  }
+}
+```
+
+By placing the shared parameters in the job's update block, each groups update
+block may be kept to a minimum. The merged update blocks for each group
+becomes:
+
+```hcl
+group "one" {
+  update {
+    canary           = 1
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+
+group "two" {
+  update {
+    min_healthy_time = "3m"
+    max_parallel     = 2
+    health_check     = "task_states"
+    healthy_deadline = "10m"
+  }
+}
+```
+
+[canary]: /nomad/tutorials/job-updates/job-blue-green-and-canary-deployments 'Nomad Canary Deployments'
+[checks]: /nomad/docs/job-specification/service#check-parameters 'Nomad check Job Specification'
+[rolling]: /nomad/tutorials/job-updates/job-rolling-update 'Nomad Rolling Upgrades'
+[strategies]: /nomad/tutorials/job-updates 'Nomad Update Strategies'
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/upstreams.mdx b/content/nomad/v1.9.x/content/docs/job-specification/upstreams.mdx
new file mode 100644
index 0000000000..58ad223d5f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/upstreams.mdx
@@ -0,0 +1,150 @@
+---
+layout: docs
+page_title: upstreams Block - Job Specification
+description: |-
+  The "upstreams" block allows specifying options for configuring
+  upstream services
+---
+
+# `upstreams` Block
+
+<Placement
+  groups={[
+    'job',
+    'group',
+    'service',
+    'connect',
+    'sidecar_service',
+    'proxy',
+    'upstreams',
+  ]}
+/>
+
+The `upstreams` block allows configuring various options for managing upstream
+services that a [Consul Connect][] proxy routes to. It is valid only within the
+context of a `proxy` block.
+
+For Consul-specific details see the [Consul Connect Guide][]. Note that using
+`upstream` may not be necessary if you have configured the proxy with the
+[`transparent_proxy`][] block.
+
+```hcl
+job "countdash" {
+  datacenters = ["dc1"]
+
+  group "dashboard" {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        static = 9002
+        to     = 9002
+      }
+    }
+
+    service {
+      name = "count-dashboard"
+      port = "9002"
+
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "count-api"
+              local_bind_port  = 8080
+              datacenter = "dc2"
+              local_bind_address = "127.0.0.1"
+              mesh_gateway {
+                mode = "local"
+              }
+            }
+          }
+        }
+      }
+    }
+
+    task "dashboard" {
+      driver = "docker"
+
+      env {
+        COUNTING_SERVICE_URL = "http://${NOMAD_UPSTREAM_ADDR_count_api}"
+      }
+
+      config {
+        image = "hashicorpdev/counter-dashboard:v3"
+      }
+    }
+  }
+}
+
+```
+
+## `upstreams` Parameters
+
+- `config` `(map: nil)` - Upstream configuration that is opaque to Nomad and passed
+  directly to Consul. See [Consul Connect documentation][consul_expose_path_ref]
+  for details. Keys and values support [runtime variable interpolation][interpolation].
+- `destination_name` `(string: <required>)` - Name of the upstream service.
+- `destination_namespace` `(string: <required>)` - Name of the upstream Consul namespace.
+- `destination_partition` `(string: "")` - Name of the Cluster admin partition containing the upstream service.
+- `destination_peer` `(string: "")` - Name of the peer cluster containing the upstream service.
+- `destination_type` - `(string: "service")` - The type of discovery query the proxy should use for finding service mesh instances.
+- `local_bind_port` - `(int: <required>)` - The port the proxy will receive
+  connections for the upstream on.
+- `datacenter` `(string: "")` - The Consul datacenter in which to issue the
+  discovery query. Defaults to the empty string, which Consul interprets as the
+  local Consul datacenter.
+- `local_bind_address` - `(string: "")` - The address the proxy will receive
+  connections for the upstream on.
+- `local_bind_socket_mode` - `(string: "")` - Unix octal that configures file permissions for the socket.
+- `local_bind_socket_path` - `(string: "")` - The path at which to bind a Unix domain socket listener.
+- `mesh_gateway` <code>([mesh_gateway][mesh_gateway_param]: nil)</code> - Configures the mesh gateway
+  behavior for connecting to this upstream.
+
+### `mesh_gateway` Parameters
+
+- `mode` `(string: "")` - The mode of operation in which to use [Connect Mesh Gateways][mesh_gateways].
+  If left unset, the mode will default to the mode as determined by the Consul [service-defaults][service_defaults_mode]
+  configuration for the service. Can be configured with the following modes:
+  - `local` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the same datacenter. That gateway is then responsible for
+  ensuring the data gets forwarded along to gateways in the destination datacenter.
+  - `remote` - In this mode the Connect proxy makes its outbound connection to a
+  gateway running in the destination datacenter. That gateway will then forward
+  the data to the final destination service.
+  - `none` - In this mode, no gateway is used and a Connect proxy makes its
+  outbound connections directly to the destination services.
+
+The `NOMAD_UPSTREAM_ADDR_<destination_name>` environment variables may be used
+to interpolate the upstream's `host:port` address.
+
+Applications are encouraged to connect to `127.0.0.1` and a well defined port
+(eg 6379 for Redis) by default. Then when using Consul Connect the application
+can be deployed with the Redis upstream's `local_bind_port = 6379` and require
+no explicit configuration.
+
+## `upstreams` Examples
+
+The following example is an upstream config with the name of the destination service
+and a local bind port.
+
+```hcl
+    upstreams {
+      destination_name = "count-api"
+      local_bind_port = 8080
+    }
+```
+
+[Consul Connect]: /nomad/docs/integrations/consul-connect
+[Consul Connect Guide]: /consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery
+[`transparent_proxy`]: /nomad/docs/job-specification/transparent_proxy
+[job]: /nomad/docs/job-specification/job 'Nomad job Job Specification'
+[group]: /nomad/docs/job-specification/group 'Nomad group Job Specification'
+[task]: /nomad/docs/job-specification/task 'Nomad task Job Specification'
+[interpolation]: /nomad/docs/runtime/interpolation 'Nomad interpolation'
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service 'Nomad sidecar service Specification'
+[upstreams]: /nomad/docs/job-specification/upstreams 'Nomad upstream config Specification'
+[service_defaults_mode]: /consul/docs/connect/config-entries/service-defaults#meshgateway
+[mesh_gateway_param]: /nomad/docs/job-specification/upstreams#mesh_gateway-parameters
+[mesh_gateways]: /consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways
+[consul_expose_path_ref]: /consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/vault.mdx b/content/nomad/v1.9.x/content/docs/job-specification/vault.mdx
new file mode 100644
index 0000000000..2f95ff0a2b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/vault.mdx
@@ -0,0 +1,229 @@
+---
+layout: docs
+page_title: vault Block - Job Specification
+description: |-
+  The "vault" block allows the task to specify that it requires a token from a
+  HashiCorp Vault server. Nomad will automatically retrieve a Vault token for
+  the task and handle token renewal for the task.
+---
+
+# `vault` Block
+
+<Placement
+  groups={[
+    ['job', 'vault'],
+    ['job', 'group', 'vault'],
+    ['job', 'group', 'task', 'vault'],
+  ]}
+/>
+
+The `vault` block allows a task to specify that it requires a token from a
+[HashiCorp Vault][vault] server. Nomad will automatically retrieve a Vault token
+for the task and handle token renewal for the task. If specified at the `group`
+level, the configuration will apply to all tasks within the group. If specified
+at the `job` level, the configuration will apply to all tasks within the job. If
+multiple `vault` blocks are specified, they are merged with the `task` block
+taking the highest precedence, then the `group`, then the `job`.
+
+```hcl
+job "docs" {
+  group "example" {
+    task "server" {
+      vault {
+        cluster  = "default"
+        role     = "prod"
+
+        change_mode   = "signal"
+        change_signal = "SIGUSR1"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the Vault token available to the task by writing it
+to the secret directory at `secrets/vault_token` and by injecting a `VAULT_TOKEN`
+environment variable. If the Nomad cluster is [configured](/nomad/docs/configuration/vault#namespace)
+to use [Vault Namespaces](/vault/docs/enterprise/namespaces),
+a `VAULT_NAMESPACE` environment variable will be injected whenever `VAULT_TOKEN` is set.
+This behavior can be altered using the `env` and `disable_file` parameters.
+
+If Nomad is unable to renew the Vault token (perhaps due to a Vault outage or
+network error), the client will attempt to retrieve a new Vault token. If successful, the
+contents of the secrets file are updated on disk, and action will be taken
+according to the value set in the `change_mode` parameter.
+
+If a `vault` block is specified, the [`template`][template] block can interact
+with Vault as well.
+
+## `vault` Parameters
+
+- `allow_token_expiration` `(bool: false)` - Specifies that Nomad clients should
+  not attempt to renew a task's Vault token, allowing it to expire. This should
+  only be used when a secret is requested from Vault once at the start of a task
+  or in a short-lived prestart task. Long-running tasks should never set
+  `allow_token_expiration=true` if they obtain Vault secrets via `template`
+  blocks, as the Vault token will expire and the template runner will continue
+  to make failing requests to Vault until its [`vault_retry`][] attempts are
+  exhausted, at which point the task will fail.
+
+  When Nomad has been configured to use [Workload Identity with Vault][], Nomad
+  clients will automatically detect when tokens cannot be refreshed (for
+  example, when the Vault auth method is configured to issue batch tokens). In
+  this case, the `allow_token_expiration` option will be implicitly set to
+  `true` by the client. The [legacy Vault authentication workflow][] cannot
+  automatically detect this.
+
+- `change_mode` `(string: "restart")` - Specifies the behavior Nomad should take
+  if the Vault token changes. The possible values are:
+
+  - `"noop"` - take no action (continue running the task)
+  - `"restart"` - restart the task
+  - `"signal"` - send a configurable signal to the task
+
+- `change_signal` `(string: "")` - Specifies the signal to send to the task as a
+  string like `"SIGUSR1"` or `"SIGINT"`. This option is required if the
+  `change_mode` is `signal`.
+
+- `cluster` `(string: "default")` <EnterpriseAlert inline/> - Specifies the
+  Vault cluster to use. The Nomad client will retrieve a Vault token from the
+  cluster configured in the agent configuration with the same
+  [`vault.name`][]. In Nomad Community Edition, this field is ignored.
+
+- `env` `(bool: true)` - Specifies if the `VAULT_TOKEN` and `VAULT_NAMESPACE`
+  environment variables should be set when starting the task.
+
+- `disable_file` `(bool: false)` - Specifies if the Vault token should be
+  written to `secrets/vault_token`.
+  <Warning>
+    While the <code>secrets</code> path is not shared with tasks that
+    use <a href="/nomad/docs/concepts/filesystem#image-isolation">
+      <code>image</code>
+    </a> filesystem isolation, it is still accessible by tasks using <a href="/nomad/docs/concepts/filesystem#chroot-isolation">
+      <code>chroot</code>
+    </a> or <a href="/nomad/docs/concepts/filesystem#none-isolation"><code>none</code>
+    </a> isolation.
+  </Warning>
+
+- `namespace` `(string: "")` <EnterpriseAlert inline/> - Specifies the Vault Namespace
+  to use for the task. The Nomad client will retrieve a Vault token that is scoped to
+  this particular namespace.
+
+- `policies` `(array<string>: [])` - Specifies the set of Vault policies that
+  the task requires. The Nomad client will retrieve a Vault token that is
+  limited to those policies. This field may only be used with the legacy Vault
+  authentication workflow and not with JWT and workload identity. It is
+  deprecated in favor of the `role` field and will be removed in Nomad 1.10.
+
+- `role` `(string: "")` - Specifies the Vault role used when retrieving a token
+  from Vault using JWT and workload identity. If not specified the client's
+  [`create_from_role`][] value is used.
+
+## `vault` Examples
+
+The following examples only show the `vault` blocks. Remember that the
+`vault` block is only valid in the placements listed above.
+
+### Retrieve Token
+
+This example tells the Nomad client to retrieve a Vault token. The token is
+available to the task via the canonical environment variable `VAULT_TOKEN` and
+written to disk at `secrets/vault_token`. The resulting token will have the
+Vault policies from the "prod" role attached.
+
+```hcl
+vault {
+  role = "prod"
+}
+```
+
+### Signal Task
+
+This example shows signaling the task instead of restarting it.
+
+```hcl
+vault {
+  role = "prod"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+### Private Token and Change Modes
+
+This example retrieves a Vault token that is not shared with the task when using
+a driver that provides `image` isolation like [Docker][docker].
+
+This allows Nomad to use a powerful Vault token that interacts with the task's
+[`template`][template] stanzas to issue all kinds of secrets (e.g., database
+secrets, other vault tokens, etc.), without sharing that issuing power with
+the task itself:
+
+```hcl
+vault {
+  role         = "prod"
+  change_mode  = "noop"
+  env          = false
+  disable_file = true
+}
+
+template {
+  data = <<-EOH
+{{with secret "auth/token/create/nomad-job" "policies=examplepolicy"}}{{.Auth.ClientToken}}{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/examplepolicy.token"
+  change_mode = "noop"
+  perms       = "600"
+}
+
+template {
+  data = <<-EOH
+{{ with secret "pki_int/issue/nomad-task"
+   "common_name=example.service.consul" "ttl=72h"
+   "alt_names=localhost" "ip_sans=127.0.0.1"}}
+{{ .Data.certificate }}
+{{ .Data.private_key }}
+{{ end }}
+EOH
+
+  destination = "${NOMAD_SECRETS_DIR}/client.crt"
+  change_mode = "restart"
+  perms       = "600"
+}
+```
+
+The example above uses `change_mode = "noop"` in the `template` stanza for
+`examplepolicy.token`, which means that the task's workload is responsible for
+detecting and handling changes to that file. In contrast, the `template` stanza
+for `client.crt` is configured so that Nomad will restart the task whenever
+the certificate is reissued, as indicated by `change_mode = "restart"`
+(which is the default value for `change_mode`).
+
+
+### Vault Namespace
+
+This example shows specifying a particular Vault namespace for a given task.
+
+<EnterpriseAlert />
+
+```hcl
+vault {
+  role      = "prod"
+  namespace = "engineering/frontend"
+
+  change_mode   = "signal"
+  change_signal = "SIGINT"
+}
+```
+
+[`create_from_role`]: /nomad/docs/configuration/vault#create_from_role
+[docker]: /nomad/docs/drivers/docker "Docker Driver"
+[restart]: /nomad/docs/job-specification/restart "Nomad restart Job Specification"
+[template]: /nomad/docs/job-specification/template "Nomad template Job Specification"
+[vault]: https://www.vaultproject.io/ "Vault by HashiCorp"
+[`vault.name`]: /nomad/docs/configuration/vault#name
+[`vault_retry`]: /nomad/docs/configuration/client#vault_retry
+[Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#nomad-workload-identities
+[legacy Vault authentication workflow]: /nomad/docs/integrations/vault/acl#authentication-without-workload-identity-legacy
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/volume.mdx b/content/nomad/v1.9.x/content/docs/job-specification/volume.mdx
new file mode 100644
index 0000000000..58ec2bd352
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/volume.mdx
@@ -0,0 +1,209 @@
+---
+layout: docs
+page_title: volume Block - Job Specification
+description: >-
+  The "volume" block allows the group to specify that it requires a given
+  volume from the cluster. Nomad will automatically handle ensuring that the
+  volume is available and mounted into the task.
+---
+
+# `volume` Block
+
+<Placement groups={['job', 'group', 'volume']} />
+
+The `volume` block allows the group to specify that it requires a
+given volume from the cluster.
+
+The key of the block is the name of the volume as it will be exposed
+to task configuration.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type      = "host"
+      source    = "ca-certificates"
+      read_only = true
+    }
+  }
+}
+```
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "data" {
+      type            = "csi"
+      source          = "csi-volume"
+      read_only       = true
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+
+      mount_options {
+        fs_type     = "ext4"
+        mount_flags = ["noatime"]
+      }
+    }
+  }
+}
+```
+
+
+The Nomad server will ensure that the allocations are only scheduled
+on hosts that have a set of volumes that meet the criteria specified
+in the `volume` blocks. These may be [host volumes][host_volume]
+configured on the client, or [CSI volumes][csi_volume] dynamically
+mounted by [CSI plugins][csi_plugin].
+
+The Nomad client will make the volumes available to tasks according to
+the [volume_mount][volume_mount] block in the `task` configuration.
+
+## `volume` Parameters
+
+- `type` `(string: "")` - Specifies the type of a given volume. The
+  valid volume types are `"host"` and `"csi"`.
+
+- `source` `(string: <required>)` - The name of the volume to
+  request. When using `host_volume`'s this should match the published
+  name of the host volume. When using `csi` volumes, this should match
+  the ID of the registered volume.
+
+- `read_only` `(bool: false)` - Specifies that the group only requires
+  read only access to a volume and is used as the default value for
+  the `volume_mount -> read_only` configuration. This value is also
+  used for validating `host_volume` ACLs and for scheduling when a
+  matching `host_volume` requires `read_only` usage.
+
+- `per_alloc` `(bool: false)` - Specifies that the `source` of the volume
+  should have the suffix `[n]`, where `n` is the allocation index. This allows
+  mounting a unique volume per allocation, so long as the volume's source is
+  named appropriately. For example, with the source `myvolume` and `per_alloc
+  = true`, the allocation named `myjob.mygroup.mytask[0]` will require a
+  volume ID `myvolume[0]`.
+
+  The `per_alloc` field cannot be true for system jobs, sysbatch jobs, or jobs
+  that use canaries.
+
+The following fields are only valid for volumes with `type = "csi"`:
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+  available concurrently. The `access_mode` and `attachment_mode` together
+  must exactly match one of the volume's `capability` blocks. Can be one of
+  `"single-node-reader-only"`, `"single-node-writer"`,
+  `"multi-node-reader-only"`, `"multi-node-single-writer"`, or
+  `"multi-node-multi-writer"`. Most CSI plugins support only single-node
+  modes. Consult the documentation of the storage provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+  by the volume. The `access_mode` and `attachment_mode` together must exactly
+  match one of the volume's `capability` blocks. Most storage providers will
+  support `"file-system"`, to mount volumes using the CSI filesystem API. Some
+  storage providers will support `"block-device"`, which will mount the volume
+  with the CSI block device API within the container.
+
+- `mount_options` - Options for mounting CSI volumes that have the
+  `file-system` [attachment mode]. These options override the `mount_options`
+  field from [volume registration]. Consult the documentation for your storage
+  provider and CSI plugin as to whether these options are required or
+  necessary.
+
+  - `fs_type`: file system type (ex. `"ext4"`)
+  - `mount_flags`: the flags passed to `mount` (ex. `["ro", "noatime"]`)
+
+## Volume Interpolation
+
+Because volumes represent state, many workloads with multiple allocations will
+want to mount specific volumes to specific tasks. The `volume` block is used
+to schedule workloads, so `${NOMAD_ALLOC_INDEX}` can't be used directly in the
+`volume.source` field. The following job specification demonstrates how to use
+multiple volumes with multiple allocations, using the `per_alloc` field. This
+job specification also shows using HCL2 -variables interpolation to expose
+information to the task's environment.
+
+```hcl
+variables {
+  path = "test"
+}
+
+job "example" {
+  datacenters = ["dc1"]
+
+  group "cache" {
+
+    count = 2
+
+    volume "cache-volume" {
+      type            = "csi"
+      source          = "test-volume"
+      attachment_mode = "file-system"
+      access_mode     = "single-node-writer"
+      per_alloc       = true
+    }
+
+    network {
+      port "db" {
+        to = 6379
+      }
+    }
+
+    task "redis" {
+      driver = "docker"
+      config {
+        image = "redis:7"
+        ports = ["db"]
+      }
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+
+      env {
+        # this will be available as the MOUNT_PATH environment
+        # variable in the task
+        MOUNT_PATH = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+      volume_mount {
+        volume      = "cache-volume"
+        destination = "${NOMAD_ALLOC_DIR}/${var.path}"
+      }
+
+    }
+  }
+}
+```
+
+The job that results from this job specification has two task groups, each one
+named for each of the two volumes. Each allocation has its own volume.
+
+```shell-session
+$ nomad job status example
+ID            = example
+...
+
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-1     0        run      running  4s ago   3s ago
+ce6fbfc8  352c6926  cache-0     0        run      running  4s ago   3s ago
+
+$ nomad volume status 'test-volume[0]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+ce6fbfc8  352c6926  cache-0     0        run      running  29s ago  18s ago
+
+$ nomad volume status 'test-volume[1]'
+...
+Allocations
+ID        Node ID   Task Group  Version  Desired  Status   Created  Modified
+81d32909  352c6926  cache-0     0        run      running  29s ago  18s ago
+```
+
+[volume_mount]: /nomad/docs/job-specification/volume_mount 'Nomad volume_mount Job Specification'
+[host_volume]: /nomad/docs/configuration/client#host_volume-block
+[csi_volume]: /nomad/docs/commands/volume/register
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume]: /nomad/docs/commands/volume/register
+[attachment mode]: /nomad/docs/commands/volume/register#attachment_mode
+[volume registration]: /nomad/docs/commands/volume/register#mount_options
diff --git a/content/nomad/v1.9.x/content/docs/job-specification/volume_mount.mdx b/content/nomad/v1.9.x/content/docs/job-specification/volume_mount.mdx
new file mode 100644
index 0000000000..01929d2277
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/job-specification/volume_mount.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: volume_mount Block - Job Specification
+description: |-
+  The "volume_mount" block allows the task to specify where a group "volume"
+  should be mounted.
+---
+
+# `volume_mount` Block
+
+<Placement groups={['job', 'group', 'task', 'volume_mount']} />
+
+The `volume_mount` block allows the task to specify how a group
+[`volume`][volume] should be mounted into the task.
+
+```hcl
+job "docs" {
+  group "example" {
+    volume "certs" {
+      type = "host"
+      read_only = true
+      source = "ca-certificates"
+    }
+
+    task "example" {
+      volume_mount {
+        volume      = "certs"
+        destination = "/etc/ssl/certs"
+        propagation_mode = "private"
+      }
+    }
+  }
+}
+```
+
+The Nomad client will make the volumes available to tasks according to this
+configuration, and it will fail the allocation if the client configuration
+updates to remove a volume that it depends on.
+
+## `volume_mount` Parameters
+
+- `volume` `(string: "")` - Specifies the group volume that the mount is going
+  to access.
+
+- `destination` `(string: "")` - Specifies where the volume should be mounted
+  inside the task's allocation.
+
+- `read_only` `(bool: false)` - When a group volume is writeable, you may
+  specify that it is `read_only` on a per mount level using the `read_only`
+  option here.
+
+- `propagation_mode` `(string: "private")` - Specifies the mount propagation
+  mode for nested volumes. Possible values are:
+
+    - `private` - the task is not allowed to access nested mounts.
+
+    - `host-to-task` - allows new mounts that have been created outside of the
+    task to be visible inside the task.
+
+    - `bidirectional` - allows the task to both access new mounts from the host
+    and also create new mounts. This mode requires `ReadWrite` permission.
+
+    ~> **Warning:** `bidirectional` propagation mode can be dangerous to use
+    and cause problems in the host operating system if a task creates a mount
+    but does not clean it up properly before exiting.
+
+- `selinux_label``(string: "")` - Specifies the SELinux label for the mount.
+  This is only supported on Linux hosts and when supported by the task driver. Refer to the task driver documentation for more information. Possible 
+  values are:
+
+  - `Z` -  Specifies that the volume content is private and unshared between 
+    containers.
+  - `z` - Specifies that the volume content is shared among containers.
+
+For examples of how to use [HCL2] interpolation for fine-grained control of
+volumes, see [Volume Interpolation].
+
+[volume]: /nomad/docs/job-specification/volume 'Nomad volume Job Specification'
+[volume interpolation]: /nomad/docs/job-specification/volume#volume-interpolation
+[hcl2]: /nomad/docs/job-specification/hcl2
diff --git a/content/nomad/v1.9.x/content/docs/networking/cni.mdx b/content/nomad/v1.9.x/content/docs/networking/cni.mdx
new file mode 100644
index 0000000000..19376bddb8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/networking/cni.mdx
@@ -0,0 +1,265 @@
+---
+layout: docs
+page_title: CNI plugins and bridge networking
+description: |-
+  Learn how to install Container Network Interface (CNI) reference plugins, configure Nomad's bridge networking, and use CNI networks with Nomad jobs.
+---
+
+# Container Network Interface (CNI)
+
+This page shows you how to install the [CNI reference plugins][cni-plugin-docs]
+on your Linux distribution and configure bridge networking on your Nomad
+clients. You can apply this guide's workflow to installing any plugin that
+complies with the [Container Network Interface (CNI) Specification][cni-spec],
+but you should verify plugin compatibility with Nomad before deploying in
+production.
+
+## Background
+
+The CNI specification defines a network configuration format for administrators.
+The configuration contains directives for both the orchestrator and the plugins
+to consume. Nomad implements custom networking through a combination of CNI
+reference plugin binaries and CNI configuration files. Networking features, like
+bridge network mode and Consul service mesh, leverage the CNI reference plugins
+to provide an operating-system agnostic interface to configure workload
+networking.
+
+## Requirements
+
+- You are familiar with [CNI reference plugins][cni-plugin-docs].
+- You are familiar with [how Nomad uses Container Network Interface (CNI) plugins for bridge networking](/nomad/docs/networking#bridge-networking).
+- You are running Nomad on Linux.
+
+## CNI plugins and bridge networking workflow
+
+Perform the following on each Nomad client:
+
+1. [Install CNI reference plugins](#install-cni-reference-plugins).
+1. [Configure bridge module to route traffic through iptables](#configure-bridge-module-to-route-traffic-through-iptables).
+1. [Create a bridge mode configuration](#create-a-cni-bridge-mode-configuration).
+1. [Configure Nomad clients](#configure-nomad-clients).
+
+After you configure and restart your Nomad clients, [use a CNI network with a
+job](#use-a-cni-network-with-a-job).
+
+### Install CNI reference plugins
+
+@include 'install/install-cni-plugins.mdx'
+
+### Configure bridge module to route traffic through iptables
+
+@include 'install/bridge-iptables.mdx'
+
+## Create a CNI bridge mode configuration
+
+Nomad itself uses CNI plugins and configuration as the underlying implementation
+for the `bridge` network mode, using the loopback, [bridge][], [firewall][], and
+[portmap][] CNI reference plugins configured together to create Nomad's bridge
+network.
+
+[comment-source-image]:
+    https://www.figma.com/file/Ne2qaPUlBTmTYer9biCfK9/Networking?node-id=0%3A1&t=BepgOoQ0kb76GwIr-1
+
+[![Visual example of Nomad bridge
+network](/img/nomad-bridge-network.png)](/img/nomad-bridge-network.png)
+
+When setting up a bridge network, Nomad uses a configuration template based on
+the CNI Specification's [example
+configuration](https://www.cni.dev/docs/spec/#example-configuration). Refer to
+the external [configuration
+format](https://www.cni.dev/docs/spec/#example-configuration) for a complete
+explanation of the fields.
+
+You can use this template as a basis for your own CNI-based bridge network
+configuration in cases where you need access to an unsupported option in the
+default configuration, like hairpin mode.
+
+This example uses two default values from Nomad client configuration.
+
+- The default value for
+  [`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name)
+  is the value for the bridge plugin name.
+- The default value for bridge subnet [`bridge_network_subnet`](
+  /nomad/docs/configuration/client#bridge_network_subnet) is the bridge plugin
+  subnet.
+
+The `NOMAD-ADMIN` internal constant provides the value for
+`iptablesAdminChainName`. In your own configuration, ensure that you change the
+`iptablesAdminChainName` to a unique value.
+
+<CodeBlockConfig highlight="10,20,32">
+
+```json
+{
+  "cniVersion": "1.0.0",
+  "name": "nomad",
+  "plugins": [
+    {
+      "type": "loopback"
+    },
+    {
+      "type": "bridge",
+      "bridge": "nomad",
+      "ipMasq": true,
+      "isGateway": true,
+      "forceAddress": true,
+      "hairpinMode": false,
+      "ipam": {
+        "type": "host-local",
+        "ranges": [
+          [
+            {
+              "subnet": "172.26.64.0/20"
+            }
+          ]
+        ],
+        "routes": [
+          { "dst": "0.0.0.0/0" }
+        ]
+      }
+    },
+    {
+      "type": "firewall",
+      "backend": "iptables",
+      "iptablesAdminChainName": "NOMAD-ADMIN"
+    },
+    {
+      "type": "portmap",
+      "capabilities": {"portMappings": true},
+      "snat": true
+    }
+  ]
+}
+```
+
+</CodeBlockConfig>
+
+This configuration uses the following CNI reference plugins:
+
+- loopback: The loopback plugin sets the default local interface, lo0, created
+  inside the bridge network's network namespace to UP. This allows workload
+  running inside the namespace to bind to a namespace-specific loopback
+  interface.
+- bridge: The [bridge][] plugin creates a bridge (virtual switch) named `nomad`
+  that resides in the host network namespace. Because Nomad intends this bridge
+  to provide network connectivity to allocations, we configured it to be a
+  gateway by setting `isGateway` to `true`. This tells the plugin to assign an
+  IP address to the bridge interface.
+
+   The bridge plugin connects allocations on the same host into a virtual switch
+   bridge that resides in the host network namespace. By default, Nomad creates
+   a single bridge for each client.
+
+   Since Nomad's bridge network is designed to provide network connectivity to
+   the allocations, Nomad configures the bridge interface to be a gateway for
+   outgoing traffic by providing it with an address using an `ipam`
+   configuration. The default configuration creates a host-local address for the
+   host side of the bridge in the `172.26.64.0/20` subnet at `172.26.64.1`.
+
+   When associating allocations to the bridge, Nomad creates addresses for the
+   allocations from that same subnet using the host-local plugin. The
+   configuration also specifies a default route for the allocations of the
+   host-side bridge address.
+- firewall: The [firewall][] plugin creates firewall rules to allow traffic to
+  and from the allocation's IP address via the host network. Nomad uses the
+  iptables backend for the firewall plugin.
+
+   This configuration creates two new iptables chains, `CNI-FORWARD` and
+   `NOMAD-ADMIN`, in the filter table and adds rules that allow the given
+   interface to send and receive traffic.
+
+   The firewall creates an admin chain using the `iptablesAdminChainName` value,
+   which is `NOMAD-ADMIN` in this example. The admin chain is a user-controlled
+   chain for custom rules that run before rules managed by the firewall plugin.
+   The firewall plugin does not add, delete, or modify rules in the admin chain.
+
+   Nomad adds a new chain called `CNI-FORWARD` to to the `FORWARD` chain.
+   `CNI-FORWARD` is the chain where Nomad adds rules when it creates allocations
+   and removes the rules when those allocations stop. The `CNI-FORWARD` chain
+   first sends all traffic to the `NOMAD-ADMIN` chain.
+
+   Use the `iptables` command to list the iptables rules present in each chain.
+
+   ```shell-session
+   $ sudo iptables -L
+   ```
+
+- portmap: Nomad needs to be able to map specific ports from the host to tasks
+  running in the allocation namespace. The [portmap][] plugin forwards traffic
+  from one or more ports on the host to the allocation using network address
+  translation (NAT) rules.
+
+   The plugin sets up two sequences of chains and rules:
+
+   - One primary destination NAT (DNAT) sequence to rewrite the destination.
+   - One source NAT (SNAT) sequence to masquerade traffic as needed.
+
+   Use the `iptables` command to list the iptables rules in the NAT table.
+
+   ```shell-session
+   $ sudo iptables -t nat -L
+   ```
+
+Save your bridge network configuration file to a Nomad-accessible directory. By
+default, Nomad loads configuration files from the `/opt/cni/config` directory.
+However, you may configure a different location using the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter.
+Refer to the [Configure Nomad clients](#configure-nomad-clients) section for an
+example.
+
+## Configure Nomad clients
+
+At plugin execution time, Nomad interprets your CNI network configuration and
+transforms it into arguments for the plugins.
+
+Nomad reads the following files from the
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) parameter —
+`/opt/cni/config` by default:
+
+- `.conflist`: Nomad loads these files as [network
+  configurations](https://www.cni.dev/docs/spec/#configuration-format) that
+  contain a list of plugin configurations.
+
+- `.conf` and `.json`: Nomad loads these files as individual [plugin
+  configurations](https://www.cni.dev/docs/spec/#plugin-configuration-objects)
+  for a specific network.
+
+Add the [`cni_path`](/nomad/docs/configuration/client#cni_path) and
+[`cni_config_dir`](/nomad/docs/configuration/client#cni_config_dir) attributes
+to each client's `client.hcl` file.
+
+This example uses the default values for both attributes.
+
+<CodeBlockConfig filename="/etc/nomad.d/client.hcl">
+
+```hcl
+client {
+  enabled = true
+  cni_path = "opt/cni/bin"
+  cni_config_dir = "opt/cni/config"
+}
+```
+
+</CodeBlockConfig>
+
+## Use a CNI network with a job
+
+To specify that a job should use a CNI network, set the task group's network
+[`mode`](/nomad/docs/job-specification/network#mode) attribute to the value
+`cni/<your_cni_config_name>`. Nomad then schedules the workload on client nodes
+that have fingerprinted a CNI configuration with the given name. For example, to
+use the configuration named `mynet`, you should set the task group's network
+mode to `cni/mynet`. Nodes that have a network configuration defining a network
+named `mynet` in their `cni_config_dir` are eligible to run the workload. Nomad
+additionally supplies the following arguments via `CNI_ARGS` to the CNI network:
+`NOMAD_REGION`, `NOMAD_NAMESPACE`, `NOMAD_JOB_ID`, `NOMAD_GROUP_NAME`, and
+`NOMAD_ALLOC_ID`. Since the `CNI_ARGS` do not allow values to contain a semicolon
+Nomad will not set keys where the value contains a semicolon (this could happen
+with the job ID). CNI plugins utilizing `NOMAD_*` CNI arguments are advised to
+apply a defensive policy or simply error out.
+
+[cni-spec]: https://www.cni.dev/docs/spec/
+[cni-plugin-docs]: https://www.cni.dev/plugins/current/
+[bridge]: https://www.cni.dev/plugins/current/main/bridge/
+[firewall]: https://www.cni.dev/plugins/current/meta/firewall/
+[portmap]: https://www.cni.dev/plugins/current/meta/portmap/
diff --git a/content/nomad/v1.9.x/content/docs/networking/index.mdx b/content/nomad/v1.9.x/content/docs/networking/index.mdx
new file mode 100644
index 0000000000..8ee25dfd6f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/networking/index.mdx
@@ -0,0 +1,340 @@
+---
+layout: docs
+page_title: Networking
+description: |-
+  Nomad's networking features connect your workloads without running additional component tools like DNS servers and load balancers. Learn about workload allocation networking and bridge networking, which uses Container Network Interface (CNI) plugins or Docker. Review how Nomad networking differs from Kubernetes networking.
+---
+
+# Networking
+
+This page provides conceptual information about Nomad's networking feature, how
+networking works in Nomad, different patterns and configurations, and how Nomad
+networking differs from Kubernetes networking.
+
+## Introduction
+
+Nomad is a workload orchestrator and focuses on the scheduling aspects of a
+deployment, touching areas such as networking as little as possible.
+
+Networking in Nomad is usually done via _configuration_ instead of
+_infrastructure_. This means that Nomad provides ways for you to access the
+information you need to connect your workloads instead of running additional
+components behind the scenes, such as DNS servers and load balancers.
+
+## Allocation networking
+
+The base unit of scheduling in Nomad is an
+[allocation](/nomad/docs/glossary#allocation), which means that all
+tasks in the same allocation run in the same client and share common resources,
+such as disk and networking. Allocations can request access to network
+resources, such as ports, using the
+[`network`](/nomad/docs/job-specification/network) block. You can define a basic
+`network` block as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+    # ...
+  }
+}
+```
+
+Nomad reserves a random port in the client between
+[`min_dynamic_port`](/nomad/docs/configuration/client#min_dynamic_port) and
+[`max_dynamic_port`](/nomad/docs/configuration/client#max_dynamic_port) that has
+not been allocated yet. Nomad then creates a port mapping from the host network
+interface to the allocation.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Port
+Mapping](/img/networking/port_mapping.png)](/img/networking/port_mapping.png)
+
+Tasks can access the selected port number using the
+[`NOMAD_PORT_<label>`](/nomad/docs/runtime/environment#network-related-variables)
+environment variable to bind and expose the workload at the client's IP address
+and the given port.
+
+The specific configuration process depends on what you are running. However,
+usually you use a
+[`template`](/nomad/docs/job-specification/template#template-examples) to create
+a configuration file such as the following:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+    }
+
+    task "..." {
+      # ...
+      config {
+        args = [
+          "--port=${NOMAD_PORT_http}",
+        ]
+      }
+    }
+  }
+}
+```
+
+You may also pass configuration via command line arguments.
+
+It is also possible to request a specific port number instead of a random one by
+setting a [`static`](/nomad/docs/job-specification/network#static) value for the
+`port`. This should only be used by specialized workloads, such as load
+balancers and system jobs, since it can be hard to manage them manually to avoid
+scheduling collisions.
+
+With the task listening at one of the client's ports, other processes can access
+the task directly using the client's IP and port, but first the processes need
+to find these values. This process is called [service
+discovery](/nomad/docs/networking/service-discovery).
+
+When using IP and port to connect allocations it is important to make sure your
+network topology and routing configuration allow the Nomad clients to
+communicate with each other.
+
+## Bridge networking
+
+Linux clients support a network
+[`mode`](/nomad/docs/job-specification/network#mode) called
+[`bridge`](/nomad/docs/job-specification/network#bridge). A bridge network acts
+like a virtual network switch, allowing processes connected to the bridge to
+reach each other while isolating them from others.
+
+### Container Network Interface (CNI) reference plugins
+
+Nomad's bridge network leverages [CNI reference
+plugins](https://github.com/containernetworking/plugins) to provide an
+operating-system agnostic interface to configure workload networking. Nomad's
+network plugin support extends Nomad's built-in compute resource scheduling to
+allow scheduling tasks with specialty network configurations, which Nomad
+implements with a combination of CNI reference plugins and CNI configuration
+files.
+
+### How bridge networking works
+
+When an allocation uses bridge networking, the Nomad agent creates a bridge
+called `nomad` (or the value set in
+[`bridge_network_name`](/nomad/docs/configuration/client#bridge_network_name))
+using the [`bridge` CNI plugin](
+https://www.cni.dev/plugins/current/main/bridge/) if one doesn't exist yet.
+Before using this mode you must first [install the CNI
+plugins](/nomad/docs/networking/cni/) into your clients. By default, Nomad
+creates a single bridge in each Nomad client.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad Bridge](/img/networking/bridge.png)](/img/networking/bridge.png)
+
+Allocations that use the `bridge` network mode run in an isolated network
+namespace and are connected to the bridge. This allows Nomad to map random ports
+from the host to specific port numbers inside the allocation that tasks expect.
+
+For example, you can configure an HTTP server that listens on port `3000` by
+default with the following `network` block:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {
+        to = 3000
+      }
+    }
+    # ...
+  }
+}
+```
+
+To allow communication between allocations in different clients, Nomad creates
+an `iptables` rule to forward requests from the host network interface to the
+bridge. This results in three different network access scopes:
+
+- Tasks that bind to the loopback interface (`localhost` or `127.0.0.1`) are
+  accessible only from within the allocation.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  without `port` forwarding are only accessible from within the same client.
+
+- Tasks that bind to the bridge (or other general addresses, such as `0.0.0.0`)
+  with `port` forwarding are accessible from external sources.
+
+~> **Warning:** To prevent any type of external access when using `bridge`
+network mode make sure to bind your workloads to the loopback interface only.
+
+Bridge networking is at the core of [service
+mesh](/nomad/docs/networking/service-mesh) and a requirement when using [Consul
+Service Mesh](/nomad/docs/integrations/consul-connect).
+
+### Bridge networking with Docker
+
+The Docker daemon manages its own network configuration and creates its own
+[bridge network](https://docs.docker.com/network/bridge/), network namespaces,
+and [`iptable` rules](https://docs.docker.com/network/iptables/). Tasks using
+the `docker` task driver connect to the Docker bridge instead of using the one
+created by Nomad and, by default, each container runs in its own Docker managed
+network namespace.
+
+When using `bridge` network mode, Nomad creates a placeholder container using
+the image defined in [`infra_image`](/nomad/docs/drivers/docker#infra_image) to
+initialize a Docker network namespace that is shared by all tasks in the
+allocation to allow them to communicate with each other.
+
+The Docker task driver has its own task-level
+[`network_mode`](/nomad/docs/drivers/docker#network_mode) configuration. Its
+default value depends on the group-level `network.mode` configuration.
+
+```hcl
+group "..." {
+  network {
+    mode = "bridge"
+  }
+
+  task "..." {
+    driver = "docker"
+
+    config {
+      # This conflicts with the group-level network.mode configuration and
+      # should not be used.
+      network_mode = "bridge"
+      # ...
+    }
+  }
+}
+```
+
+~> **Warning:** The task-level `network_mode` may conflict with the group-level
+`network.mode` configuration and generate unexpected results. If you set the
+group `network.mode = "bridge"` you should not set the Docker config
+`network_mode`.
+
+This diagram illustrates what happens when a Docker task is configured
+incorrectly.
+
+[comment-image-source]:
+    https://drive.google.com/file/d/1q4a2ab0TyLEPdWiO2DIianAPWuPqLqZ4/view?usp=share_link
+
+[![Nomad
+Bridge](/img/networking/docker_bridge.png)](/img/networking/docker_bridge.png)
+
+The tasks in the rightmost allocation are not able to communicate with each
+other using their loopback interface because they were placed in different
+network namespaces.
+
+Since the group `network.mode` is `bridge`, Nomad creates the pause container to
+establish a shared network namespace for all tasks, but setting the task-level
+`network_mode` to `bridge` places the task in a different namespace. This
+prevents, for example, a task from communicating with its sidecar proxy in a
+service mesh deployment.
+
+Refer to the [`network_mode`](/nomad/docs/drivers/docker#network_mode)
+documentation and the [Networking](/nomad/docs/drivers/docker#networking)
+section for more information.
+
+-> **Note:** Docker Desktop in non-Linux environments runs a local virtual
+   machine, adding an extra layer of indirection. Refer to the
+   [FAQ](/nomad/docs/faq#q-how-to-connect-to-my-host-network-when-using-docker-desktop-windows-and-macos)
+   for more details.
+
+## Comparison with other tools
+
+### Kubernetes and Docker Compose
+
+Networking in Kubernetes and Docker Compose works differently than in Nomad. To
+access a container you use a fully qualified domain name such as `db` in Docker
+Compose or `db.prod.svc.cluster.local` in Kubernetes. This process relies on
+additional infrastructure to resolve the hostname and distribute the requests
+across multiple containers.
+
+Docker Compose allows you to run and manage multiple containers using units
+called services.
+
+```yaml
+version: "3.9"
+services:
+  web:
+    build: .
+    ports:
+      - "8000:8000"
+  db:
+    image: postgres
+    ports:
+      - "8001:5432"
+```
+
+To access a service from another container you can reference the service name
+directly, for example using `postgres://db:5432`. In order to enable this
+pattern, Docker Compose includes an [internal DNS
+services](https://docs.docker.com/config/containers/container-networking/#dns-services)
+and a load balancer that is transparent to the user. When running in Swarm mode,
+Docker Compose also requires an overlay network to route requests across hosts.
+
+
+Kubernetes provides the
+[`Service`](https://kubernetes.io/docs/concepts/services-networking/service/)
+abstraction that can be used to declare how a set of Pods are accessed.
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: my-service
+spec:
+  selector:
+    app.kubernetes.io/name: MyApp
+  ports:
+    - protocol: TCP
+      port: 80
+      targetPort: 9376
+```
+
+To access the Service you use a FQDN such as
+`my-service.prod.svc.cluster.local`. This name is resolved by the [DNS
+service](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/)
+which is an add-on that runs in all nodes. Along with this service, each node
+also runs a
+[`kube-proxy`](https://kubernetes.io/docs/concepts/overview/components/#kube-proxy)
+instance to distribute requests to all Pods matched by the Service.
+
+You can use the same FQDN networking style with Nomad using [Consul's DNS
+interface](/consul/docs/services/discovery/dns-overview) and configuring your
+clients with [DNS forwarding](/consul/tutorials/networking/dns-forwarding), and
+deploying a [load balancer](/nomad/tutorials/load-balancing).
+
+Another key difference from Nomad is that in Kubernetes and Docker Compose each
+container has its own IP address, requiring a virtual network to map physical IP
+addresses to virtual ones. In the case of Docker Compose in Swarm mode, an
+[`overlay`](https://docs.docker.com/network/overlay/) is also required to enable
+traffic across multiple hosts. This allows multiple containers running the same
+service to listen on the same port number.
+
+In Nomad, allocations use the IP address of the client in which they are running
+and are assigned random port numbers. Nomad service discovery with DNS uses
+[`SRV` records]( https://en.wikipedia.org/wiki/SRV_record) instead of `A` or
+`AAAA` records.
+
+## Next topics
+
+- [Service Discovery](/nomad/docs/networking/service-discovery)
+- [Service Mesh](/nomad/docs/networking/service-mesh)
+- [Container Network Interface](/nomad/docs/networking/cni) plugins guide
+
+## Additional resources
+
+- [Understanding Networking in Nomad - Karan
+  Sharma](https://mrkaran.dev/posts/nomad-networking-explained/)
+- [Understanding Nomad Networking Patterns - Luiz Aoqui, HashiTalks: Canada
+  2021](https://www.youtube.com/watch?v=wTA5HxB_uuk)
diff --git a/content/nomad/v1.9.x/content/docs/networking/service-discovery.mdx b/content/nomad/v1.9.x/content/docs/networking/service-discovery.mdx
new file mode 100644
index 0000000000..aa444e6f7d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/networking/service-discovery.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Service Discovery
+description: |-
+  Nomad service discovery helps you automatically connects workloads. Compare Nomad's built-in service discovery feature to Consul service discovery, which adds a DSN interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+---
+
+# Service discovery
+
+This page provides conceptual information about Nomad service discovery. Compare Nomad's built-in service discovery feature to using Consul service discovery, which adds a DSN interface and service mesh. Learn about health checks, configuring tags in job specification service blocks, and how to specify tags for canary and blue/green allocations.
+
+## Introduction
+
+Service discovery is the process of retrieving the low-level information
+necessary to access a service, such as its IP and port, via a high-level
+identifier, such as a human-friendly service name.
+
+The service information is stored in a service catalog which provide interfaces
+that can be used to query data. In Nomad there are two service catalogs:
+
+- The **native service discovery** catalog is embedded in Nomad and requires no
+  additional infrastructure.
+
+- The [**Consul service discovery catalog**][consul_sd] requires access to a
+  Consul cluster, but it provides additional features, including a [DNS
+  interface][consul_dns] and [service mesh][] capabilities.
+
+Services are registered using the [`service`][] block, with the [`provider`][]
+parameter defining which catalog to use. Nomad stores the IP and port of all
+allocations associated with the service in the catalog and keeps these entries
+updated as you schedule new workloads or deploy new versions of your
+applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    service {
+      name     = "database"
+      port     = "db"
+      provider = "nomad"
+      # ...
+    }
+    # ...
+  }
+}
+```
+
+To access services, other allocations can query the catalog using
+[`template`][] blocks with the [`service`][ct_service_fn] function to query the
+Consul catalog or the [`nomadService`][ct_nomad_service_fn] function when using
+Nomad native service discovery. The `template` can then be used as a
+configuration file or have its content loaded as environment variables to
+configure connection information in applications.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    task "..." {
+      template {
+        data = <<EOF
+{{ range nomadService "database" }}
+DB_CONNECTION="host={{ .Address }} port={{ .Port }} user=user password=password dbname=db_name"
+{{ end }}
+EOF
+        destination = "local/env.txt"
+        env         = true
+      }
+    }
+    # ...
+  }
+}
+```
+
+## Health checks
+
+Both Nomad and Consul services can define health checks to make sure that only
+healthy instances are returned by the service catalog. Health checks are
+specified using the [`check`][] block.
+
+## Service tags
+
+`service` blocks may be specified multiple times with the same name but for
+different ports. All instances are returned when the service name is queried.
+To restrict results you can assign [`tags`][] to services to group them. When
+querying the service you can provide tag values as part of the service name.
+
+The example below exposes an application on two ports for different protocols.
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      port "http" {}
+      port "grpc" {}
+    }
+
+    service {
+      name = "my-app"
+      port = "http"
+      tags = ["http"]
+      # ...
+    }
+
+    service {
+      name = "my-app"
+      port = "grpc"
+      tags = ["grpc"]
+      # ...
+    }
+  }
+}
+```
+
+By assigning different `tags` the port for each protocol can be reached using
+the `http.my-app` and `grpc.my-app` service queries.
+
+### Canary deployments
+
+When using [canary][jobspec_update_canary] or
+[blue/green][jobspec_update_blue_green] upgrades you can specify a different
+set of tags for the canary allocations using the [`canary_tags`][]
+configuration.
+
+During a deployment, the new allocations are registered with the tags set in
+`canary_tags` while non-canaries have the values in `tags`. Having different
+sets of tags allow you to create separate [load balancing][learn_lb] routing
+rules to preview canaries.
+
+-> **Note**: Services are registered with either `tags` or `canary_tags`. In
+  order to share values they must be set in both fields.
+
+[`canary_tags`]: /nomad/docs/job-specification/service#canary_tags
+[`check`]: /nomad/docs/job-specification/check
+[`provider`]: /nomad/docs/job-specification/service#provider
+[`service`]: /nomad/docs/job-specification/service
+[`tags`]: /nomad/docs/job-specification/service#tags
+[`template`]: /nomad/docs/job-specification/template#template-examples
+[consul_dns]: /consul/docs/services/discovery/dns-overview
+[consul_sd]: /consul/docs/concepts/service-discovery
+[ct_nomad_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#nomadservice
+[ct_service_fn]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#service
+[jobspec_update_blue_green]: /nomad/docs/job-specification/update#blue-green-upgrades
+[jobspec_update_canary]: /nomad/docs/job-specification/update#canary-upgrades
+[learn_lb]: /nomad/tutorials/load-balancing
+[service mesh]: /nomad/docs/networking/service-mesh
diff --git a/content/nomad/v1.9.x/content/docs/networking/service-mesh.mdx b/content/nomad/v1.9.x/content/docs/networking/service-mesh.mdx
new file mode 100644
index 0000000000..2057320f4c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/networking/service-mesh.mdx
@@ -0,0 +1,169 @@
+---
+layout: docs
+page_title: Service Mesh
+description: |-
+  Nomad integrates with Consul service mesh to securely connect and isolate
+  your workloads. Review example job configurations that use service mesh. Learn about the Envoy proxy as well as mesh, ingress, and terminating gateways.
+---
+
+# Service mesh
+
+This page provides conceptual information on using Consul service mesh with
+Nomad to securely connect and isolate your workloads. Review example job
+configurations that use service mesh. Learn about the Envoy proxy as well as
+mesh, ingress, and terminating gateways.
+
+## Introduction
+
+Service mesh is a networking pattern that deploys and configures
+infrastructure to directly connect workloads. One of the most common pieces of
+infrastructure deployed are sidecar proxies. These proxies usually run
+alongside the main workload in an isolated network namespace such that all
+network traffic flows through the proxy.
+
+The proxies are often referred to as the **data plane** since they are
+responsible for _moving data_ while the components that configure them are part
+of the **control plane** because they are responsible for controlling the _flow
+of data_.
+
+By funneling traffic through a common layer of infrastructure the control plane
+is able to centralize and automatically apply configuration to all proxies to
+enable features such as automated traffic encryption, fine-grained routing, and
+service-based access control permissions throughout the entire mesh.
+
+## Consul Service Mesh
+
+Nomad has native integration with Consul to provide service mesh capabilities.
+The [`connect`][] block is the entrypoint for all service mesh configuration.
+Nomad automatically deploys a sidecar proxy task to all allocations that have a
+[`sidecar_service`][] block.
+
+This proxy task is responsible for exposing the service to the mesh and can
+also be used to access other services from within the allocation. These
+external services are called upstreams and are declared using the
+[`upstreams`][] block.
+
+The allocation `network_mode` must be set to `bridge` for network isolation and
+all external traffic is provided by the sidecar.
+
+~> **Warning:** To fully isolate your workloads make sure to bind them only to
+   the `loopback` interface.
+
+The job below exposes a service called `api` to the mesh:
+
+```hcl
+job "..."  {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+
+      port "http" {}
+    }
+
+    service {
+      name = "api"
+      port = "http"
+
+      connect {
+        sidecar_service {}
+      }
+    }
+    # ...
+  }
+}
+```
+
+To access this service, a job can be configured as follows:
+
+```hcl
+job "..." {
+  # ...
+  group "..." {
+    network {
+      mode = "bridge"
+      # ...
+    }
+
+    service {
+      # ...
+      connect {
+        sidecar_service {
+          proxy {
+            upstreams {
+              destination_name = "api"
+              local_bind_port  = 8080
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+A request starting from a task within an allocation of this job follows the
+path:
+
+1. The task makes a request to `localhost:8080` which is the port where the
+   proxy binds the `api` service as an upstream.
+
+2. The proxy, configured by Consul, forwards the request to a proxy running
+   within an allocation that is part of the `api` service.
+
+3. The proxy for the `api` service forwards the request to the local port in
+   the allocation.
+
+4. The response is sent back to the first task following the same path in
+   reverse.
+
+The IP and port to use to connect to an upstream can also be read from the
+[`NOMAD_UPSTREAM_ADDR_<upstream>`][runtime_network] environment variable.
+
+### Envoy proxy
+
+Consul Service Mesh uses [Envoy][] as proxy. Nomad calls Consul's [`consul
+connect envoy -bootstrap`][consul_cli_envoy] CLI command to generate the
+initial proxy configuration.
+
+Nomad injects a prestart sidecar Docker task to run the Envoy proxy. This task
+can be customized using the [`sidecar_task`][] block.
+
+### Gateways
+
+Since the mesh defines a closed boundary that only selected services can
+participate in, there are specialized proxies called gateways that can be used
+for mesh-wide connectivity. Nomad can deploy these gateways using the
+[`gateway`][] block. Nomad injects an Envoy proxy task to any `group` with a
+`gateway` service.
+
+The types of gateways provided by Consul Service Mesh are:
+
+- **Mesh gateways** allow communication between different service meshes and
+  are deployed using the [`mesh`][] parameter.
+
+- **Ingress gateways** allow services outside the mesh to connect to services
+  inside the mesh and are deployed using the [`ingress`][] parameter.
+
+- **Egress gateways** allow services inside the mesh to communication with
+  services outside the mesh and are deployed using the [`terminating`][]
+  parameter.
+
+
+## Additional Resources
+
+- [Consul Service Mesh documentation](/consul/docs/connect)
+- [Nomad Consul Service Mesh integration](/nomad/docs/integrations/consul-connect)
+
+[Envoy]: https://www.envoyproxy.io/
+[`connect`]: /nomad/docs/job-specification/connect
+[`gateway`]: /nomad/docs/job-specification/gateway
+[`ingress`]: /nomad/docs/job-specification/gateway#ingress
+[`mesh`]: /nomad/docs/job-specification/gateway#mesh
+[`proxy`]: /nomad/docs/job-specification/proxy
+[`sidecar_service`]: /nomad/docs/job-specification/sidecar_service
+[`sidecar_task`]: /nomad/docs/job-specification/sidecar_task
+[`terminating`]: /nomad/docs/job-specification/gateway#terminating
+[`upstreams`]: /nomad/docs/job-specification/upstreams
+[consul_cli_envoy]: /consul/commands/connect/envoy
+[runtime_network]: /nomad/docs/runtime/environment#network-related-variables
diff --git a/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/alternative.mdx b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/alternative.mdx
new file mode 100644
index 0000000000..729962d1e7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/alternative.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Alternative to Kubernetes
+description: Learn why Nomad's "run anything anywhere" workload orchestration is a robust alternative to Kubernetes.
+---
+
+# Alternative to Kubernetes
+
+While known for its goal of automating and simplifying application deployment, an orchestrator itself can be extremely complex to implement and manage. Kubernetes requires significant time and deep understanding to deploy, operate, and troubleshoot. Teams and organizations choose Nomad as an alternative to Kubernetes for its two core strengths:
+
+- **Simplicity in usage and maintainability**
+
+- **Flexibility to deploy and manage containerized and non-containerized applications**
+
+Operating as a single lightweight binary, Nomad excels on-premises and at the edge, providing the same ease-of-use as it does in the cloud. Its architectural simplicity, native federation capabilities, and operator-friendly design enable companies to scale and manage an orchestrator with little operational overhead. Our customer interviews show that no matter company size, teams and organizations gain benefits from simplicity and flexibility, including
+
+- Fast time to production: Average 1-3 weeks to get Nomad from a technical proof of concept into production
+
+- Rapid adoption: From 2 hours to less than 30 minutes to onboard a developer to directly deploy applications on Nomad
+
+- Great operational efficiency: Allows operation teams to stay lean (1-4 people) to service hundreds of developers and applications, and achieve high uptime with a self-hosted orchestrator
+
+- Smooth path to migration: Allows teams to incrementally migrate or containerize existing applications at their own pace with a single, unified deployment workflow
+
+> “Nomad is easy to cluster up. We converted our Kubernetes deployment manifest to Nomad job files, then tested it. And since it’s a single binary, it’s simple to configure to our specific needs, which eliminates much of the complexity we faced with Kubernetes. More importantly, Nomad’s agnostic infrastructure resource pool and automated workflows let us deploy and manage our containers and apps across on-prem and any private or public cloud environment, which dramatically expands our datacenter options while still meeting our data residency obligations.”
+
+**AmpleOrganics**, Canada's #1 cannabis software company migrated off of Kubernetes to Nomad
+
+> “I’m a complete beginner when it comes to distributed computing and orchestration. Nomad virtually eliminates barriers to entry for developers who don’t have cloud computing expertise and makes it really easy to connect to the cluster, configure it, and run my jobs while having full visibility into the jobs’ status so I can restart them if need be.”
+
+**Autodesk**, Autodesk Research built a scalable, maintenance-free, and multi-cloud orchestration workflow with Nomad
+
+> “We have people who are first-time system administrators deploying applications, building containers, maintaining Nomad. There is a guy on our team who worked in the IT help desk for eight years — just today he upgraded an entire cluster himself. That’s the value proposition that I hope people understand. People seem to get stuck on ‘I need to run Kubernetes because my friend runs it’ — but do you really use it? Can you operate it at the level that’s needed?”
+
+**Roblox**, the top online gaming company built a global gaming platform with Nomad serving more than 150 million players
+
+> “A large portion of our applications are Windows-based, so we need both Windows and Linux support. Although we do prefer running containers, we don’t necessarily want a hard requirement to have to use them and we like the idea of directly running applications on VMs if the use case calls for it. We wanted to make improvements to the current workflow without massive and time-consuming application rewrites. Ultimately we chose Nomad because it met all of our requirements and made the most sense to our environments.”
+
+**Q2** - The ebanking platform that serves 10% of the digital banking customers in America transformed the deployment workflow with Nomad
+
+While Nomad’s strengths lie in simplicity and flexibility in core scheduling, Kubernetes excels over Nomad in terms of ecosystem. The goal for Nomad ecosystem is to build a simpler, leaner, and more prescriptive path to the ecosystem. This is an area of improvement for Nomad that we invest significantly in today and plan to continue into the future. [Read more about Nomad’s ecosystem](/nomad/docs/ecosystem).
diff --git a/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/index.mdx b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/index.mdx
new file mode 100644
index 0000000000..c5cda48fcb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/index.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Nomad versus Kubernetes
+description: Nomad is a superior workload scheduling and orchestration tool compared to Kubernetes. Compare architecture, flexible workload support, consistent deployment, and scalability.
+---
+
+# Nomad versus Kubernetes
+
+This page compares Nomad to Kubernetes and illustrates why Nomad is the superior
+workload scheduling and orchestration tool. Compare architecture, flexible workload support, consistent deployment, and scalability.
+
+~> Interested in talking with HashiCorp about your experience building, deploying,
+or managing your applications? [Set up a time to chat!](https://forms.gle/2tAmxJbyPbcL2nRW9)
+
+Kubernetes is an orchestration system for containers originally designed by Google, now governed by the Cloud Native Computing Foundation (CNCF) and developed by Google, Red Hat, and many others. Kubernetes and Nomad support similar core use cases for application deployment and management, but they differ in a few key ways. Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more. Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.
+
+The following characteristics generally differentiate Nomad from Kubernetes.
+
+## Simplicity
+
+Kubernetes is designed as a collection of more than a half-dozen interoperating services which together provide the full functionality. Coordination and storage is provided by etcd at the core. The state is wrapped by API controllers which are consumed by other services that provide higher level APIs for features like scheduling. Kubernetes supports running in a highly available configuration but is operationally complex to setup.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients and servers, and requires no external services for coordination or storage. Nomad combines a lightweight resource manager and a sophisticated scheduler into a single system. By default, Nomad is distributed, highly available, and operationally simple.
+
+## Flexible Workload Support
+
+While Kubernetes is specifically focused on Linux containers, Nomad is more general purpose. Nomad supports virtualized, containerized and standalone applications, including Docker, Java, IIS on Windows, Qemu, etc. Nomad is designed with extensible drivers and support will be extended to all common drivers.
+
+## Consistent Deployment
+
+A full Kubernetes installation for a production environment is time consuming, operationally complex, and resource intensive. An increasing number of implementations are created by the Kubernetes community to mitigate these challenges, such as minikube, kubeadm, k3s, and more. These trimmed versions of Kubernetes offer easier adoption for development and testing, but lead to inconsistency in capabilities, configuration, and management when moving into production.
+
+In contrast to Kubernetes' fragmented distributions, Nomad as a single lightweight binary can be deployed in local dev, production, on-prem, at the edge, and in the cloud in a consistent manner, and provides the same operational ease-of-use across all environments.
+
+## Scalability
+
+[Kubernetes documentation](https://kubernetes.io/docs/setup/best-practices/cluster-large/) states that they support clusters up to 5,000 nodes and 300,000 total containers. As the environment grows, the interoperating components with different constraints compound the operational complexity. [Even operators at Google revealed the significant challenges of managing the system at scale](https://blog.dave.tf/post/new-kubernetes/). The lack of maturity in the Federation project and the additional overhead of managing a centralized management plane also make it a hard experience to deploy a distributed system that spans multiple clusters.
+
+Nomad has been proven to scale to cluster sizes that exceed 10,000 nodes in real-world production environments. It can be deployed across multiple availability zones, regions, and data centers with a single cluster or multiple clusters. Nomad is designed to natively handle multi-cluster deployments without the overhead of running clusters on clusters. This makes it easier to scale the application deployment across multiple datacenters, regions, and clouds with no additional complexity.
+
+Nomad has performed strenuous benchmark on scalability with [1 million container challenge](https://www.hashicorp.com/c1m) in 2016 and [2 million container challenge](https://www.hashicorp.com/c2m) in 2020. These tests are aimed to validate Nomad's architectural design and ensure that Nomad performs under the most extreme requirements.
diff --git a/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/supplement.mdx b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/supplement.mdx
new file mode 100644
index 0000000000..8172ff7ca9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/nomad-vs-kubernetes/supplement.mdx
@@ -0,0 +1,41 @@
+---
+layout: docs
+page_title: Supplement to Kubernetes
+description: Learn how Nomad's "run anything anywhere" capability can supplement Kubernetes' container-only approach to workload orchestration.
+---
+
+# Supplement to Kubernetes
+
+Enterprises are comprised of multiple groups of people (business units) with different projects, infrastructure environments, technical competencies, team sizes, budgets, and SLAs. Each group has different requirements and leverages technologies based on their particular needs and constraints.
+
+Medium to large scale enterprises run into challenges when trying to standardize hundreds to thousands of software developers and administrators onto one single orchestrator (Kubernetes, Nomad, Mesos) as no scheduler today fits all applications, environments, projects, and teams.
+
+Companies in the Global 2000 today such as Intel, Autodesk and GitHub with multiple products and business units organically run Nomad and Kubernetes to supplement each other. They leverage each scheduler to its strengths with Kubernetes for its cutting edge ecosystem and Nomad for simple maintenance and flexibility in core scheduling.
+
+![How organizations leverage Nomad and Kubernetes](/img/nomad-kubernetes.png)
+
+These are the characteristics we see in teams that typically adopt self-hosted Kubernetes:
+
+- Greenfield use-cases such as machine learning (ML), serverless, and big data that require the Kubernetes ecosystem and Helm chart
+
+- High budget and full-time staffing to maintain Kubernetes
+
+- High-profile projects with significant investment and long-term timeline (multi-year)
+
+- Deploying and managing new, cloud-native applications
+
+- Public cloud environment such as AWS, GCP, Azure
+
+Characteristics of teams that typically adopt Nomad:
+
+- Run a mix of containerized and non-containerized workloads (Windows, Java)
+
+- Small/medium-sized teams with limited capacity to maintain an orchestrator
+
+- Deploying and managing core, existing applications
+
+- On-premises environment, or hybrid environments
+
+- Require simplicity to move fast and fulfill business needs with hard deadlines
+
+We continue to see small enterprises continue to standardize on a single orchestrator given the natural staffing and organizational constraints. There are not enough DevOps members to maintain more than one orchestrator, not enough developers to warrant diverging workflows, or simply not enough workload diversity to require more than one orchestrator.
diff --git a/content/nomad/v1.9.x/content/docs/operations/aws-oidc-provider.mdx b/content/nomad/v1.9.x/content/docs/operations/aws-oidc-provider.mdx
new file mode 100644
index 0000000000..3efbe4af7e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/aws-oidc-provider.mdx
@@ -0,0 +1,406 @@
+---
+layout: docs
+page_title: Federate access to AWS with Nomad Workload Identity
+description: |-
+  Integrate Nomad as an OpenID Connect (OIDC) provider with AWS IAM identity and federate access to AWS resources.
+---
+
+# Federate access to AWS with Nomad Workload Identity
+
+This page describes how to integrate Nomad with AWS IAM as an OpenID Connect (OIDC) provider and
+use [Workload Identity] to federate access to AWS resources and services. In this workflow, Nomad
+is the [OpenID Connect Provider] (OP or OIDC provider) and generates JSON Web Tokens (JWTs) which
+serve as workload identities. AWS IAM is the Relying Party (RP) and validates these workload
+identity tokens with Nomad before it permits federated access to resources and services.
+
+## Prerequisites
+
+To integrate Nomad and AWS IAM identity, you need a running Nomad cluster that
+meets the following prerequisites:
+
+- Nomad v1.7.x or later
+- TLS enabled
+
+The instructions on this page also assume the following:
+
+- Your AWS account has the necessary permissions to create IAM roles, policies, hosted zones,
+  and certificates.
+- You are using Terraform to manage your AWS infrastructure and you have
+  [configured it to communicate with AWS](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication-and-configuration).
+
+## Workflow
+
+The process to integrate Nomad as an OIDC provider with AWS consists of the following steps:
+
+1. Create the required AWS resources:
+    - [Route 53 hosted zone](#create-a-hosted-zone)
+    - [AWS Certificate Manager SSL certificates](#generate-ssl-certificates)
+    - [Load balancer and listener](#create-an-application-load-balancer)
+    - [DNS Alias for the load balancer](#create-a-dns-alias)
+    - [OIDC Identity Provider](#create-an-oidc-identity-provider)
+    - [AWS IAM role](#create-an-iam-policy-for-oidc-federated-users)
+1. Update the Nomad server configuration.
+1. Create a jobspec file that accesses AWS and then run it to verify your configuration.
+
+## Create and configure AWS resources
+
+To use Nomad as an identity provider, you need to have a trusted SSL certificate for the
+domain used by the cluster. The following example uses AWS Certificate Manager (ACM).
+
+### Create a hosted zone
+
+Use the [`aws_route53_zone` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone).
+
+```hcl
+variable "domain_name" {
+    type = string
+    default = "<DOMAIN_NAME>"
+}
+
+resource "aws_route53_zone" "example" {
+    name = var.domain_name
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port. `var.domain_name` is used
+throughout the examples on this page to reference `<DOMAIN_NAME>`.
+
+### Generate SSL certificates
+
+Use the [`aws_acm_certificate`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate)
+and [`aws_acm_certificate_validation`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/acm_certificate_validation) resources to create a request and provide validation for an SSL
+certficiate.
+
+```hcl
+variable "zone_id" {
+  type    = string
+  default = "<HOSTED_ZONE_ID>"
+}
+
+resource "aws_acm_certificate" "example" {
+  domain_name       = var.domain_name
+  validation_method = "DNS"
+
+  lifecycle {
+    create_before_destroy = true
+  }
+}
+
+resource "aws_route53_record" "cert_dns" {
+  allow_overwrite = true
+  name            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_name
+  records         = [tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_value]
+  type            = tolist(aws_acm_certificate.example.domain_validation_options)[0].resource_record_type
+  zone_id         = var.zone_id
+  ttl             = 60
+}
+
+resource "aws_acm_certificate_validation" "example" {
+  certificate_arn         = aws_acm_certificate.example.arn
+  validation_record_fqdns = [aws_route53_record.cert_dns.fqdn]
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+
+### Create an Application Load Balancer
+
+Use the [`aws_lb` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb).
+
+```hcl
+resource "aws_lb" "test" {
+  name               = "test-lb-tf"
+  internal           = false
+  load_balancer_type = "application"
+  security_groups    = [<SECURITY_GROUP_ID>]
+  subnets            = [<SUBNET_IDS>]
+
+  enable_deletion_protection = true
+
+  access_logs {
+    bucket  = <S3_BUCKET_ID>
+    prefix  = "test-lb"
+    enabled = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<SECURITY_GROUP_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#security_groups):
+A list of security groups IDs that you want to apply to the load balancer.
+- [`<SUBNET_IDS>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#subnets):
+A list of subnet IDs that you want to attach to the load balancer.
+- [`<S3_BUCKET_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#bucket):
+The ID of an S3 bucket to store the load balancer access logs in.
+
+### Create a load balancer listener
+
+Use the [`aws_lb_listener` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener).
+
+```hcl
+resource "aws_lb_listener" "example" {
+  load_balancer_arn = <LB_ARN>
+  port              = "443"
+  protocol          = "HTTPS"
+  ssl_policy        = "ELBSecurityPolicy-2016-08"
+  certificate_arn   = <CERT_ARN>
+
+  default_action {
+    type             = "forward"
+    target_group_arn = <LB_TARGET_GROUP_ARN>
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<LB_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#load_balancer_arn):
+The AWS resource name of the load balancer. This will be `aws_lb.test.arn` if you are using the
+examples from this page.
+- [`<CERT_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#certificate_arn):
+The AWS resource name of the load balancer's certificate. This will be
+`aws_acm_certificate_validation.example.certificate_arn` if you are using the examples from this
+page.
+- [`<LB_TARGET_GROUP_ARN>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_listener#target_group_arn): The AWS resource name of the target group for the load balancer to route traffic to. This group
+includes your Nomad server instances.
+
+### Create a DNS Alias
+
+Use the [`aws_route53_record` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record).
+
+```hcl
+resource "aws_route53_record" "www" {
+  zone_id = <HOSTED_ZONE_ID>
+  name    = var.domain_name
+  type    = "A"
+
+  alias {
+    name                   = <LB_ALIAS_DNS_NAME>
+    zone_id                = <LB_ALIAS_ZONE_ID>
+    evaluate_target_health = true
+  }
+}
+```
+
+This configuration requires the following information:
+- [`<HOSTED_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The ID of the hosted zone. This will be `aws_route53_zone.example.zone_id` if you are using the
+examples from this page.
+- [`<LB_ALIAS_DNS_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#name):
+The DNS
+name of the load balancer. This will be `aws_lb.test.dns_name` if you are using the examples
+from this page.
+- [`<LB_ALIAS_ZONE_ID>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_record#zone_id):
+The zone ID of the load balancer. This will be `aws_lb.test.zone_id` if you are using the
+examples from this page.
+
+### Create an OIDC Identity Provider
+
+Use the [`aws_iam_openid_connect_provider` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider).
+
+```hcl
+data "tls_certificate" "example" {
+  url = <CERT_DOMAIN_NAME>
+}
+
+resource "aws_iam_openid_connect_provider" "nomad" {
+  # Nomad HTTPS URL
+  url = <CERT_DOMAIN_NAME>
+
+  client_id_list = [
+    "aws",
+  ]
+
+  thumbprint_list = [data.tls_certificate.example.certificates.0.sha1_fingerprint]
+}
+```
+
+This configuration requires the following information:
+- [`<CERT_DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider#url):
+The domain name of the load balancer certificate. This will be
+`aws_acm_certificate.example.domain_name` if you are using the examples from this page.
+
+### Create an IAM policy for OIDC Federated Users
+
+Use the [`aws_iam_role` resource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role)
+to create an appropriate IAM role for workloads acting as federated users. This will be
+specific to your use case. The following example allows workloads access to S3 buckets.
+
+```hcl
+# Variables for OIDC provider and AWS account
+variable "oidc_provider" {
+  description = "The OIDC provider URL"
+  type        = string
+  default     = "<DOMAIN_NAME>"
+}
+
+variable "aws_account_id" {
+  description = "AWS account ID"
+  type        = string
+  default     = "<AWS_ACCOUNT_ID>"
+}
+
+data "aws_iam_policy_document" "assume_role" {
+  statement {
+    effect = "Allow"
+
+    principals {
+      type        = "Federated"
+      identifiers = ["arn:aws:iam::${var.aws_account_id}:oidc-provider/${var.oidc_provider}"]
+    }
+
+    actions = ["sts:AssumeRoleWithWebIdentity"]
+
+    condition {
+      test     = "StringEquals"
+      variable = "${var.oidc_provider}:aud"
+      values   = ["aws"]
+    }
+  }
+}
+
+# Create an IAM role with the assume role policy generated above
+resource "aws_iam_role" "s3_all_access_role" {
+  name               = "s3_all_access_role"
+  assume_role_policy = data.aws_iam_policy_document.assume_role.json
+
+  tags = {
+    tag-key = "tag-value"
+  }
+}
+
+# Inline policy that defines what the role can do (full S3 access)
+data "aws_iam_policy_document" "s3_access_policy" {
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "s3:*",
+      "s3-object-lambda:*"
+    ]
+
+    resources = ["*"] # You can scope this down to specific S3 buckets if necessary
+  }
+}
+
+# Create a policy resource from the inline policy document above
+resource "aws_iam_policy" "policy" {
+  name        = "nomad-oidc-policy"
+  description = "A policy for federated Nomad OIDC"
+  policy      = data.aws_iam_policy_document.s3_access_policy.json
+}
+
+# Attach the S3 access policy to the IAM role
+resource "aws_iam_role_policy_attachment" "test-attach" {
+  role       = aws_iam_role.s3_all_access_role.name
+  policy_arn = aws_iam_policy.policy.arn
+}
+```
+
+This configuration requires the following information:
+- [`<DOMAIN_NAME>`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route53_zone#name):
+The domain name of your Nomad cluster without the protocol or port.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+
+## Update the Nomad server configuration
+
+After you configure AWS, modify the Nomad server configuration file. Add the
+[`oidc_issuer` attribute](/nomad/docs/configuration/server#oidc_issuer) and set the value
+to the domain name for the Nomad cluster. This [enables the HTTP endpoint in Nomad](https://developer.hashicorp.com/nomad/docs/configuration/server#oidc_issuer) that allows third parties to discover Nomad's OIDC
+configuration.
+
+```hcl
+server {
+  enabled = true
+  [...]
+  oidc_issuer = "https://<DOMAIN_NAME>"
+  [...]
+}
+```
+
+This configuration requires the following information:
+- `<DOMAIN_NAME>`: The domain name of your Nomad cluster without the protocol or port.
+
+Restart the Nomad server agent to apply the configuration changes.
+
+## Create and run a sample jobspec file
+
+Create and run a jobspec file to validate your configuration. The following file is named `s3-upload.nomad.hcl`, add the following configuration to it, and
+save the file.
+
+```hcl
+job "s3" {
+  type = "batch"
+  group "bucket" {
+    task "copy" {
+      driver = "docker"
+      config {
+        image = "public.ecr.aws/aws-cli/aws-cli"
+        command = "s3"
+        args = ["cp", "/local/test.txt", "s3://<S3_BUCKET_NAME>/test-nomad.txt"]
+      }
+
+      identity {
+        name = "aws"
+        aud = ["aws"]
+        file = true
+        ttl = "1h"
+
+        # AWS SDKs gracefully handle OIDC/WebIdentity reauthentication when the
+        # session or token expire, therefore a restart isn't needed
+        change_mode = "noop"
+      }
+
+      template {
+        destination = "local/test.txt"
+        change_mode = "restart"
+        data        = <<EOF
+Job:          {{ env "NOMAD_JOB_NAME" }}
+Alloc:        {{ env "NOMAD_ALLOC_ID" }}
+EOF
+      }
+
+      env {
+        AWS_ROLE_ARN = "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>"
+        # The format of the token file is nomad_$NAME_OF_IDENTITY.jwt
+        AWS_WEB_IDENTITY_TOKEN_FILE = "${NOMAD_SECRETS_DIR}/nomad_aws.jwt"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+This configuration requires the following information:
+- `<S3_BUCKET_NAME>`: The name of the S3 bucket where the test file will be saved.
+- `<AWS_ACCOUNT_ID>`: The ID of the AWS account where the IAM role from the previous step was
+created.
+- `<IAM_ROLE_NAME>`: The name of the IAM role from previous steps. This will be
+`s3_all_access_role` if you are using the examples from this page.
+
+Submit the job to Nomad.
+
+```shell-session
+$ nomad job run s3-upload.nomad.hcl
+```
+
+Verify that the job completed successfully.
+
+```shell-session
+$ nomad job status s3
+```
+
+Verify that the file was also uploaded to the S3 bucket.
+
+
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[OpenID Connect Provider]: https://openid.net/developers/how-connect-works/
diff --git a/content/nomad/v1.9.x/content/docs/operations/benchmarking.mdx b/content/nomad/v1.9.x/content/docs/operations/benchmarking.mdx
new file mode 100644
index 0000000000..02816c0548
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/benchmarking.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Benchmarking Nomad
+description: |-
+  Load testing Nomad by utilizing the Nomad Bench project.
+---
+
+# Nomad Bench
+
+The Nomad Bench project provides reusable infrastructure automation to run test scenarios in order
+to collect metrics and data from Nomad clusters running at scale. The core goal of the project is
+to achieve reproducible large scale test scenarios so we can better understand how Nomad scales
+and uncover problems that are only detected in large cluster deployments. It is also used to
+perform release soak testing, among other things.
+
+The [repository][bench-repo] contains all the infrastructure and details to get started with your
+own load testing.
+
+[bench-repo]: https://github.com/hashicorp-forge/nomad-bench
diff --git a/content/nomad/v1.9.x/content/docs/operations/federation/failure.mdx b/content/nomad/v1.9.x/content/docs/operations/federation/failure.mdx
new file mode 100644
index 0000000000..0a4ea5e62f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/federation/failure.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: Federated cluster failure scenarios
+description: Failure scenarios in multi-region federated cluster deployments.
+---
+
+# Failure scenarios
+
+When running Nomad in federated mode, failure situations and impacts are different depending on
+whether the authoritative region is the impacted region or not, and what the failure mode is. In
+soft failures, the region's servers have lost quorum but the Nomad processes are still up, running,
+and reachable. In hard failures, the regional servers are completely unreachable and are akin to
+the underlying hardware having been terminated (cloud) or powered-off (on-prem).
+
+The scenarios are based on a Nomad deployment running three federated regions:
+ * `asia-south-1`
+ * `europe-west-1` - authoritative region
+ * `us-east-1`
+
+## Federated region failure: soft
+In this situation the region `asia-south-1` has lost leadership but the servers are reachable and
+up.
+
+All server logs in the impacted region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=d19e6bb5-5ec9-8f75-9caf-47e2513fe28d error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+  fail unless using the `stale=true` flag.
+
+✅ Creation and deletion of replicated objects, such as namespaces, is written to the
+  authoritative region.
+
+✅ Any federated regions with leadership is able to continue to replicate all objects detailed
+  previously.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Federated region failure: hard
+In this situation the region `asia-south-1` has gone down. When this happens, the Nomad server logs
+for the other regions have log entries similar to this example.
+```console
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Initiating push/pull sync with: us-east-1-server-1.us-east-1 192.168.1.193:9002
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: asia-south-1-server-1.asia-south-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect asia-south-1-server-1.asia-south-1 has failed, no acks received
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+✅ Creation and deletion of replicated objects, such as namespaces, are written to the
+  authoritative region.
+
+✅ Any federated regions with leadership continue to replicate all objects detailed
+  above.
+
+✅ Creation of local ACL tokens continues to work for all regions which are running with
+  leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+## Authoritative region failure: soft
+In this situation the region `europe-west-1` has lost leadership but the servers are reachable and
+up.
+
+The server logs in the authoritative region have entries such as this example.
+```console
+[ERROR] nomad/worker.go:504: worker: failed to dequeue evaluation: worker_id=68b3abe2-5e16-8f04-be5a-f76aebb0e59e error="No cluster leader"
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+🟨 API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail unless using the `stale=true` flag.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions are able to read data to replicate as they use the stale flag, but no
+  writes can occur to the authoritative region as described previously.
+
+✅ Creation of local ACL tokens continues to work for all federated regions which are running
+  with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to all federated regions which
+  are running with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fails to deploy.
+
+## Authoritative region failure: hard
+In this situation the region `europe-west-1` has gone down. When this happens, the Nomad server
+leader logs for the other regions have log entries similar to this example.
+```console
+[ERROR] nomad/leader.go:544: nomad: failed to fetch namespaces from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1767: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2498: nomad: failed to fetch ACL binding rules from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader_ent.go:226: nomad: failed to fetch quota specifications from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:703: nomad: failed to fetch node pools from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:1909: nomad: failed to fetch tokens from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2083: nomad: failed to fetch ACL Roles from authoritative region: error="rpc error: EOF"
+[DEBUG] nomad/leader_ent.go:84: nomad: failed to fetch policies from authoritative region: error="rpc error: EOF"
+[ERROR] nomad/leader.go:2292: nomad: failed to fetch ACL auth-methods from authoritative region: error="rpc error: EOF"
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+[INFO]  go-hclog@v1.6.3/stdlog.go:60: nomad: memberlist: Suspect europe-west-1-server-1.europe-west-1 has failed, no acks received
+[DEBUG] go-hclog@v1.6.3/stdlog.go:58: nomad: memberlist: Failed UDP ping: europe-west-1-server-1.europe-west-1 (timeout reached)
+```
+
+✅ Request forwarding continues to work between all federated regions that are running with
+  leadership.
+
+❌ API requests, either directly or attempting to use request forwarding to the impacted region,
+ fail.
+
+❌ Creation and deletion of replicated objects, such as namespaces, fails.
+
+❌ Any federated regions with leadership is not able to replicate objects detailed in the logs.
+
+✅ Creation of local ACL tokens continues to work for all regions with leadership.
+
+✅ Jobs **without** the [`multiregion`][] block deploy to regions with leadership.
+
+❌ Jobs **with** the [`multiregion`][] block defined fail to deploy.
+
+[`multiregion`]: /nomad/docs/job-specification/multiregion
diff --git a/content/nomad/v1.9.x/content/docs/operations/federation/index.mdx b/content/nomad/v1.9.x/content/docs/operations/federation/index.mdx
new file mode 100644
index 0000000000..d0def5b924
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/federation/index.mdx
@@ -0,0 +1,64 @@
+---
+layout: docs
+page_title: Federated cluster operations
+description: |-
+  Operational considerations for running Nomad multi-region federated clusters as well as instructions for migrating the authoritative region to a federated region.
+---
+
+# Federated cluster operations
+
+This page lists operational considerations for running multi-region federated
+clusters as well as instructions for migrating the authoritative region to a
+federated region.
+
+## Operational considerations
+
+When operating multi-region federated Nomad clusters, consider the following:
+
+* **Regular snapshots**: You can back up Nomad server state using the
+  [`nomad operator snapshot save`][] and [`nomad operator snapshot agent`][] commands. Performing
+  regular backups expedites disaster recovery. The cadence depends on cluster rates of change
+  and your internal SLA’s. You should regularly test snapshots using the
+  [`nomad operator snapshot restore`][] command to ensure they work.
+
+* **Local ACL management tokens**: You need local management tokens to perform federated cluster
+  administration when the authoritative region is down. Make sure you have existing break-glass
+  tokens available for each region.
+
+* **Known paths to creating local ACL tokens**: If the authoritative region fails, creation of
+  global ACL tokens fails. If this happens, having the ability to create local ACL tokens allows
+  you to continue to interact with each available federated region.
+
+## Authoritative and federated regions
+
+* **Can non-authoritative regions continue to operate if the authoritative region is unreachable?**:
+  Yes, running workloads are never interrupted due to federation failures. Scheduling of new
+  workloads and rescheduling of failed workloads is never interrupted due to federation failures.
+  See [Failure Scenarios][failure_scenarios] for details.
+
+* **Can the authoritative region be deployed with servers only?** Yes, deploying the Nomad
+  authoritative region with servers only, without clients, works as expected. This servers-only
+  approach can expedite disaster recovery of the region. Restoration does not include objects such
+  as nodes, jobs, or allocations, which are large and require compute intensive reconciliation
+  after restoration.
+
+* **Can I migrate the authoritative region to a currently federated region?** It is possible by
+  following these steps:
+
+  1. Update the [`authoritative_region`][] configuration parameter on the desired authoritative
+    region servers.
+  1. Restart the server processes in the new authoritative region and ensure all data is present in
+    state as expected. If the network was partitioned as part of the failure of the original
+    authoritative region, writes of replicated objects may not have been successfully replicated to
+    federated regions.
+  1. Update the [`authoritative_region`][] configuration parameter on the federated region servers
+    and restart their processes.
+
+* **Can federated regions be bootstrapped while the authoritative region is down?**  No they
+cannot.
+
+[`nomad operator snapshot save`]: /nomad/docs/commands/operator/snapshot/save
+[`nomad operator snapshot agent`]: /nomad/docs/commands/operator/snapshot/agent
+[`nomad operator snapshot restore`]: /nomad/docs/commands/operator/snapshot/restore
+[failure_scenarios]: /nomad/docs/operations/federation/failure
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.9.x/content/docs/operations/index.mdx b/content/nomad/v1.9.x/content/docs/operations/index.mdx
new file mode 100644
index 0000000000..997ae50b22
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/index.mdx
@@ -0,0 +1,19 @@
+---
+layout: docs
+page_title: Operations
+description: |-
+  Learn about operating Nomad.
+---
+
+# Operations
+
+This section includes references on how to operate Nomad in production. To
+learn more, choose an item from the sidebar, or choose one of the options
+below:
+
+- [Operating Nomad Agents](/nomad/docs/operations/nomad-agent)
+- [Telemetry Overview](/nomad/docs/operations/monitoring-nomad)
+- [Metrics](/nomad/docs/operations/metrics-reference)
+- [Cluster Management](/nomad/tutorials/manage-clusters)
+- [Transport Security](/nomad/tutorials/transport-security)
+- [Access Control](/nomad/tutorials/access-control)
diff --git a/content/nomad/v1.9.x/content/docs/operations/ipv6-support.mdx b/content/nomad/v1.9.x/content/docs/operations/ipv6-support.mdx
new file mode 100644
index 0000000000..b8be5d4351
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/ipv6-support.mdx
@@ -0,0 +1,142 @@
+---
+layout: docs
+page_title: Support for IPv6
+description: |-
+  Nomad support for IPv6
+---
+
+# IPv6 support in Nomad
+
+Nomad supports IPv6 as long as the underlying networks, host machines,
+and operating systems running it support IPv6.
+
+This guide illustrates the different configuration settings you need for different connection contexts.
+
+## Advertise
+
+[Advertise][advertise] Nomad server and client addresses to specify what
+address other servers, clients, or external systems should use to make
+connections back to the agent.
+
+You can use [go-sockaddr][] templating to dynamically select a public IPv6
+address. In this example, for each protocol, fetch one IPv6 address from public
+interfaces and assign it as the protocol's address.
+
+```hcl
+advertise {
+  http = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  rpc  = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+  serf = "{{ GetPublicInterfaces | include `type` `IPv6` | limit 1 | attr `address` }}"
+}
+```
+
+## Nomad to Nomad
+
+Nomad agent processes connect to one another to make RPC calls for cluster operations.
+
+We recommend using IPv6 on Nomad with DNS that resolves to IPv6 or by
+using cloud auto-join. The following server-to-server and client-to-server
+examples use IPv6 addresses explicitly.
+
+### Server to server
+
+Use the [`server_join`][server_join] block to link servers together.
+
+```hcl
+server {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]"]
+  }
+}
+```
+
+### Client to server
+
+Use the [`servers`][client.servers] parameter or the `server_join` parameter to
+link clients.
+
+```hcl
+client {
+  enabled = true
+  servers = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+}
+```
+
+```hcl
+client {
+  enabled = true
+  server_join {
+    retry_join = ["[2001:db8::1]", "[2001:db8::2]", "[2001:db8::3]"]
+  }
+}
+```
+
+## Nomad to external systems
+
+Most connections between Nomad and other external systems occur via HTTP.
+
+For example, when you set a `NOMAD_ADDR` environment variable like this one:
+
+```
+export NOMAD_ADDR='http://[2001:db8::1]:4646'
+```
+
+You can do the following:
+
+- Use the Nomad CLI, which makes Nomad API calls.
+- Open the Nomad web UI in a browser with the command `nomad ui`.
+- Use [Workload identity][workload-identity].
+  - Nomad can reach Consul and Vault at IPv6 addresses, if they are listening,
+    to register services or fetch secrets.
+  - Configure Consul with the [`nomad setup consul` command][setup-consul].
+
+    ```
+    nomad setup consul -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+
+  - Configure Vault with the [`nomad setup vault` command][setup-vault].
+
+    ```
+    nomad setup vault -y -jwks-url="$NOMAD_ADDR/.well-known/jwks.json"
+    ```
+
+Various other third-party services that support OIDC connections should also be
+able to reach Nomad at an IPv6 address, so long as the third-party services
+support IPv6.
+
+## Workloads
+
+Nomad supports arbitrary IPv6 network calls to and from tasks on client nodes.
+
+With host networking, tasks use the same network as the host machine.
+
+- Use these options to register services with an IPv6 address:
+  - Set the [`preferred_address_family`][preferred_address_family-config]
+    client config to `"ipv6"`.
+  - Include a [`service`][service-block] block in your job specification with
+    either the "nomad" or "consul" provider as usual.
+- Use [`bridge_network_subnet_ipv6`][bridge-network-subnet-ipv6] to configure
+  Nomad's [bridge network mode][bridge-network-mode] for IPv6.
+
+[CNI][cni] plugins can work with IPv6 as well. Nomad's bridge network does this.
+
+Some task drivers have their own IPv6 configuration options. If you have enabled
+IPv6 support in the [Docker driver][docker-driver], you can configure IPv6 in
+your job specification. Refer to [IPv6 Docker
+containers][ipv6-docker-containers] for details.
+
+
+[server_join]: /nomad/docs/configuration/server_join
+[client.servers]: /nomad/docs/configuration/client#servers
+[go-sockaddr]: https://pkg.go.dev/github.com/hashicorp/go-sockaddr/template
+[advertise]: /nomad/docs/configuration#advertise
+[workload-identity]: /nomad/docs/concepts/workload-identity
+[service-block]: /nomad/docs/job-specification/service
+[preferred_address_family-config]: /nomad/docs/configuration/client#preferred_address_family
+[bridge-network-mode]: /nomad/docs/job-specification/network#network-modes
+[bridge-network-subnet-ipv6]: /nomad/docs/configuration/client#bridge_network_subnet_ipv6
+[cni]: /nomad/docs/networking/cni
+[docker-driver]: /nomad/docs/drivers/docker
+[ipv6-docker-containers]: /nomad/docs/job-specification/service#ipv6-docker-containers
+[setup-consul]: /nomad/docs/commands/setup/consul
+[setup-vault]: /nomad/docs/commands/setup/vault
diff --git a/content/nomad/v1.9.x/content/docs/operations/key-management.mdx b/content/nomad/v1.9.x/content/docs/operations/key-management.mdx
new file mode 100644
index 0000000000..6b8142125c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/key-management.mdx
@@ -0,0 +1,96 @@
+---
+layout: docs
+page_title: Key Management
+description: Learn about the key management in Nomad.
+---
+
+# Key Management
+
+Nomad servers maintain an encryption keyring used to encrypt [Variables][] and
+sign task [workload identities][]. The servers encrypt these data encryption
+keys (DEK) and store the wrapped keys in Raft.
+
+The key encryption key (KEK) used to encrypt the DEK is controlled by the
+[`keyring`][] provider. When using an external KMS or Vault transit encryption
+provider, the KEK is securely stored outside of Nomad. For the default AEAD
+provider, the KEK is stored in cleartext in Raft.
+
+<Note>
+
+Default AEAD provider users should be aware that storing the Key Encryption Key
+(KEK) in cleartext in Raft may expose data in case of a breach.
+
+</Note>
+
+Under normal operations the keyring is entirely managed by Nomad, but this
+section provides administrators additional context around key replication and
+recovery.
+
+## Key Rotation
+
+Only one key in the keyring is "active" at any given time, and all encryption
+and signing operations happen on the leader. Nomad automatically rotates the
+active encryption key every 30 days. When a key is rotated, the existing keys
+are marked as "inactive" but not deleted, so they can be used for decrypting
+previously encrypted variables and verifying workload identities for existing
+allocations.
+
+If you believe key material has been compromised, you can execute [`nomad
+operator root keyring rotate -full`][]. A new "active" key will be created and
+"inactive" keys will be marked "rekeying". Nomad will asynchronously decrypt and
+re-encrypt all variables with the new key. As each key's variables are encrypted
+with the new key, the old key will marked as "deprecated".
+
+## Key Decryption
+
+When a leader is elected, the leader creates the keyring if it does not already
+exist. When a key is added, the new wrapped key material is replicated via
+Raft. As each server replicates the new key, the server starts a task to decrypt
+the key material. Until this task completes, the server is not able to serve
+requests that require this key.
+
+## Key Redaction in Raft Snapshots
+
+The default AEAD `keyring` configuration stores the KEK in Raft. Raft snapshots
+contain the cleartext KEK. The `nomad operator snapshot save` command has a
+`-redact` option that removes the key material when creating a snapshot. The
+`nomad operator snapshot redact` command removes key material from an
+existing snapshot.
+
+Redacting key material is not required when using an external KMS.
+
+## Legacy Keystore
+
+Versions of Nomad prior to 1.9.0 stored only key metadata in Raft, but the
+encryption key material was stored in a separate file in the `keystore`
+subdirectory of the Nomad [data directory][]. These files have the extension
+`.nks.json`. The key material in each file is wrapped in a unique key encryption
+key (KEK) that is not shared between servers.
+
+Each server runs a key replication process that watches for changes to the state
+store and fetches the key material from the leader asynchronously, falling
+back to retrieving from other servers in the case where a key is written
+immediately before a leader election. Nomad 1.9.0 and above can replicate keys
+from older servers.
+
+However, replicating keys from older servers means that to restore an older cluster from snapshot you need to
+also provide the keystore directory with the `.nks.json` key files on at least
+one server. The `.nks.json` key files are unique per server, but only one
+server's key files are needed to recover the cluster. Operators should continue
+to include these files as part of your organization's backup and recovery
+strategy for the cluster until the cluster is fully upgraded to Nomad 1.9.0 and
+at least one [`root_key_gc_interval`][] has passed.
+
+If you are recovering an older Raft snapshot onto a new cluster without running
+workloads, you can skip restoring the keyring and run [`nomad operator root
+keyring rotate`][] once the servers have joined.
+
+
+
+[variables]: /nomad/docs/concepts/variables
+[workload identities]: /nomad/docs/concepts/workload-identity
+[data directory]: /nomad/docs/configuration#data_dir
+[`keyring`]: /nomad/docs/configuration/keyring
+[`nomad operator root keyring rotate -full`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`nomad operator root keyring rotate`]: /nomad/docs/commands/operator/root/keyring-rotate
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
diff --git a/content/nomad/v1.9.x/content/docs/operations/metrics-reference.mdx b/content/nomad/v1.9.x/content/docs/operations/metrics-reference.mdx
new file mode 100644
index 0000000000..ecc6f94400
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/metrics-reference.mdx
@@ -0,0 +1,538 @@
+---
+layout: docs
+page_title: Metrics Reference
+description: Learn about the different metrics available in Nomad.
+---
+
+# Metrics Reference
+
+The Nomad agent collects various runtime metrics about the performance of
+different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute.
+
+This data can be accessed via an HTTP endpoint or via sending a signal to the
+Nomad process. This data is available via HTTP at `/metrics`. See
+[Metrics](/nomad/api-docs/metrics) for more information.
+
+To view this data via sending a signal to the Nomad process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad receives the signal,
+it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Telemetry information can be streamed to both [statsite](https://github.com/armon/statsite)
+as well as statsd based on providing the appropriate configuration options.
+
+To configure the telemetry output please see the [agent
+configuration](/nomad/docs/configuration/telemetry).
+
+Below is sample output of a telemetry dump:
+
+```text
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_pending': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.plan.queue_depth': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.malloc_count': 7568.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_runs': 8.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_ready': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.num_goroutines': 56.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.sys_bytes': 3999992.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.heap_objects': 4135.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.heartbeat.active': 1.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_unacked': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.nomad.broker.total_waiting': 0.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.alloc_bytes': 634056.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.free_count': 3433.000
+[2015-09-17 16:59:40 -0700 PDT][G] 'nomad.runtime.total_gc_pause_ns': 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.memberlist.msg.alive': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.serf.member.join': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.barrier': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.raft.apply': Count: 1 Sum: 1.000
+[2015-09-17 16:59:40 -0700 PDT][C] 'nomad.nomad.rpc.query': Count: 2 Sum: 2.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Query': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.fsm.register_node': Count: 1 Sum: 1.296
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Intent': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.runtime.gc_pause_ns': Count: 8 Min: 126492.000 Mean: 821516.875 Max: 3126670.000 Stddev: 1139250.294 Sum: 6572135.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.leader.dispatchLog': Count: 3 Min: 0.007 Mean: 0.018 Max: 0.039 Stddev: 0.018 Sum: 0.054
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcileMember': Count: 1 Sum: 0.007
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.reconcile': Count: 1 Sum: 0.025
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.fsm.apply': Count: 1 Sum: 1.306
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.get_allocs': Count: 1 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.worker.dequeue_eval': Count: 29 Min: 0.003 Mean: 363.426 Max: 503.377 Stddev: 228.126 Sum: 10539.354
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.serf.queue.Event': Count: 6 Sum: 0.000
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.raft.commitTime': Count: 3 Min: 0.013 Mean: 0.037 Max: 0.079 Stddev: 0.037 Sum: 0.110
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.leader.barrier': Count: 1 Sum: 0.071
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.client.register': Count: 1 Sum: 1.626
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.nomad.eval.dequeue': Count: 21 Min: 500.610 Mean: 501.753 Max: 503.361 Stddev: 1.030 Sum: 10536.813
+[2015-09-17 16:59:40 -0700 PDT][S] 'nomad.memberlist.gossip': Count: 12 Min: 0.009 Mean: 0.017 Max: 0.025 Stddev: 0.005 Sum: 0.204
+```
+
+### Metric Types
+
+| Type    | Description                                                                                                         | Quantiles |
+| ------- | ------------------------------------------------------------------------------------------------------------------- | --------- |
+| Gauge   | Gauge types report an absolute number at the end of the aggregation interval                                        | false     |
+| Counter | Counts are incremented and flushed at the end of the aggregation interval and then are reset to zero                | true      |
+| Timer   | Timers measure the time to complete a task and will include quantiles, means, standard deviation, etc per interval. | true      |
+
+### Tagged Metrics
+
+Nomad emits metrics in a tagged format. Each metric can support more than one
+tag, meaning that it is possible to do a match over metrics for datapoints
+such as a particular datacenter, and return all metrics with this tag. Nomad
+supports labels for namespaces as well.
+
+## Key Metrics
+
+The metrics in the table below are the most important metrics for monitoring
+the overall health of a Nomad cluster.
+
+When telemetry is being streamed to statsite or statsd, `interval` in the
+table below is defined to be their flush interval. Otherwise, the interval can
+be assumed to be 10 seconds when retrieving metrics using the above described
+signals.
+
+| Metrics                                      | Description                                                                                                                                                                                                       | Unit                           | Type    |
+|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|---------|
+| `nomad.runtime.alloc_bytes`                  | Memory utilization                                                                                                                                                                                                | # of bytes                     | Gauge   |
+| `nomad.runtime.heap_objects`                 | Number of objects on the heap. General memory pressure indicator                                                                                                                                                  | # of heap objects              | Gauge   |
+| `nomad.runtime.num_goroutines`               | Number of goroutines and general load pressure indicator                                                                                                                                                          | # of goroutines                | Gauge   |
+| `nomad.nomad.broker.total_pending`           | Evaluations that are pending until an existing evaluation for the same job completes                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_ready`             | Number of evaluations ready to be processed                                                                                                                                                                       | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.total_unacked`           | Evaluations dispatched for processing but incomplete                                                                                                                                                              | # of evaluations               | Gauge   |
+| `nomad.nomad.broker.wait_time`               | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                                                                            | ms / Evaluation Wait           | Timer   |
+| `nomad.nomad.broker.process_time`            | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                                                                            | ms / Evaluation Process        | Timer   |
+| `nomad.nomad.broker.response_time`           | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                                                                                   | ms / Evaluation Response       | Timer   |
+| `nomad.nomad.heartbeat.active`               | Number of active heartbeat timers. Each timer represents a Nomad Client connection                                                                                                                                | # of heartbeat timers          | Gauge   |
+| `nomad.nomad.heartbeat.invalidate`           | The length of time it takes to invalidate a Nomad Client due to failed heartbeats                                                                                                                                 | ms / Heartbeat Invalidation    | Timer   |
+| `nomad.nomad.plan.evaluate`                  | Time to validate a scheduler Plan. Higher values cause lower scheduling throughput. Similar to `nomad.plan.submit` but does not include RPC time or time in the Plan Queue                                        | ms / Plan Evaluation           | Timer   |
+| `nomad.nomad.plan.node_rejected`             | Number of times a node has had a plan rejected. A node with a high rate of rejections may have an underlying issue causing it to be unschedulable. Refer to [this link][s_port_plan_failure] for more information | # of rejected plans            | Counter |
+| `nomad.nomad.plan.queue_depth`               | Number of scheduler Plans waiting to be evaluated                                                                                                                                                                 | # of plans                     | Gauge   |
+| `nomad.nomad.plan.submit`                    | Time to submit a scheduler Plan. Higher values cause lower scheduling throughput                                                                                                                                  | ms / Plan Submit               | Timer   |
+| `nomad.nomad.rpc.query`                      | Number of RPC queries                                                                                                                                                                                             | RPC Queries / `interval`       | Counter |
+| `nomad.nomad.rpc.request_error`              | Number of RPC requests being handled that result in an error                                                                                                                                                      | RPC Errors / `interval`        | Counter |
+| `nomad.nomad.rpc.request`                    | Number of RPC requests being handled                                                                                                                                                                              | RPC Requests / `interval`      | Counter |
+| `nomad.nomad.vault.token_last_renewal`       | Time since last successful Vault token renewal                                                                                                                                                                    | Milliseconds                   | Gauge   |
+| `nomad.nomad.vault.token_next_renewal`       | Time until next Vault token renewal attempt                                                                                                                                                                       | Milliseconds                   | Gauge   |
+| `nomad.nomad.worker.invoke_scheduler.<type>` | Time to run the scheduler of the given type                                                                                                                                                                       | ms / Scheduler Run             | Timer   |
+| `nomad.nomad.worker.wait_for_index`          | Time waiting for Raft log replication from leader. High delays result in lower scheduling throughput                                                                                                              | ms / Raft Index Wait           | Timer   |
+| `nomad.raft.apply`                           | Number of Raft transactions                                                                                                                                                                                       | Raft transactions / `interval` | Counter |
+| `nomad.raft.leader.lastContact`              | Time since last contact to leader. General indicator of Raft latency                                                                                                                                              | ms / Leader Contact            | Timer   |
+| `nomad.raft.replication.appendEntries`       | Raft transaction commit time                                                                                                                                                                                      | ms / Raft Log Append           | Timer   |
+| `nomad.license.expiration_time_epoch`        | Time as epoch (seconds since Jan 1 1970) at which license will expire                                                                                                                                             | Seconds                        | Gauge   |
+
+## Client Metrics
+
+The Nomad client emits metrics related to the resource usage of the allocations
+and tasks running on it and the node itself. Operators have to explicitly turn
+on publishing host and allocation metrics. Publishing allocation and host
+metrics can be turned on by setting the value of `publish_allocation_metrics`
+`publish_node_metrics` to `true`.
+
+By default the collection interval is 1 second but it can be changed by the
+changing the value of the `collection_interval` key in the `telemetry`
+configuration block.
+
+Please see the [agent configuration](/nomad/docs/configuration/telemetry)
+page for more details.
+
+Additional labels are emitted for [parameterized](/nomad/docs/job-specification/parameterized) and
+[periodic](/nomad/docs/job-specification/periodic) jobs. Nomad
+emits the parent job id as a new label `parent_id`. Also, the labels `dispatch_id`
+and `periodic_id` are emitted, containing the ID of the specific invocation of the
+parameterized or periodic job respectively. For example, a dispatch job with the id
+`myjob/dispatch-1312323423423`, will have the following labels.
+
+| Label       | Value                          |
+| ----------- | ------------------------------ |
+| job         | `myjob/dispatch-1312323423423` |
+| parent_id   | `myjob`                        |
+| dispatch_id | `1312323423423`                |
+
+## Host Metrics
+
+Nomad will emit [tagged metrics][tagged-metrics], in the below format:
+
+| Metric                                    | Description                                                                          | Unit       | Type    | Labels                                                                                           |
+|-------------------------------------------|--------------------------------------------------------------------------------------|------------|---------|--------------------------------------------------------------------------------------------------|
+| `nomad.client.allocated.cpu`              | Total amount of CPU shares the scheduler has allocated to tasks                      | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.memory`           | Total amount of memory the scheduler has allocated to tasks                          | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocated.disk`             | Total amount of disk space the scheduler has allocated to tasks                      | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.blocked`        | Number of allocations waiting for previous versions to exit                          | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.migrating`      | Number of allocations migrating data from previous versions (see [`sticky`][sticky]) | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.pending`        | Number of allocations pending (received by the client but not yet running)           | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.running`        | Number of allocations running                                                        | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.start`          | Number of allocations starting                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocations.terminal`       | Number of allocations terminal                                                       | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.allocs.oom_killed`          | Number of allocations OOM killed                                                     | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.cpu.idle`              | CPU utilization in idle state                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.system`            | CPU utilization in system space                                                      | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_percent`     | Total CPU utilization in percentage                                                  | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks`       | Total CPU utilization in ticks                                                       | Integer    | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.total_ticks_count` | Total CPU utilization in ticks since startup                                         | Integer    | Counter | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.cpu.user`              | CPU utilization in user space                                                        | Percentage | Gauge   | cpu, datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status  |
+| `nomad.client.host.disk.available`        | Amount of space which is available                                                   | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.inodes_percent`   | Disk space consumed by the inodes                                                    | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.size`             | Total size of the device                                                             | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used_percent`     | Percentage of disk space used                                                        | Percentage | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.disk.used`             | Amount of space which has been used                                                  | Bytes      | Gauge   | datacenter, disk, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status |
+| `nomad.client.host.memory.available`      | Total amount of memory available to processes which includes free and cached memory  | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.free`           | Amount of memory which is free                                                       | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.total`          | Total amount of physical memory on the node                                          | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.host.memory.used`           | Amount of memory used by processes                                                   | Bytes      | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.pending`              | Number of tasks pending                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.running`              | Number of tasks running                                                              | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.tasks.dead`                 | Number of tasks dead                                                                 | Integer    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.cpu`            | Total amount of CPU shares free for the scheduler to allocate to tasks               | Mhz        | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.disk`           | Total amount of disk space free for the scheduler to allocate to tasks               | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.unallocated.memory`         | Total amount of memory free for the scheduler to allocate to tasks                   | Megabytes  | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+| `nomad.client.uptime`                     | Uptime of the host running the Nomad client                                          | Seconds    | Gauge   | datacenter, host, node_class, node_id, node_pool, node_scheduling_eligibility, node_status       |
+
+### Client Hook Metrics
+
+Nomad will emit metrics allowing you to monitor and alert on allocation and task hook performance.
+If you do not need these, they can be disabled via the [`disable_allocation_hook_metrics`][]
+configuration parameter.
+
+| Metric                                    | Description                                           | Unit         | Type    | Labels                                                      |
+|-------------------------------------------|-------------------------------------------------------|--------------|---------|-------------------------------------------------------------|
+| `nomad.client.alloc_hook.prerun.failed`   | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.success`  | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.alloc_hook.prerun.elapsed`  | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.failed`  | Number of hook executions that resulted in an error   | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.success` | Number of hook executions that completed successfully | Integer      | Counter | datacenter, host, node_class, node_id, node_pool, hook_name |
+| `nomad.client.task_hook.prestart.elapsed` | The time it took the hook to run                      | Milliseconds | Timer   | datacenter, host, node_class, node_id, node_pool, hook_name |
+
+## Allocation Metrics
+
+The following metrics are emitted for each allocation if allocation metrics
+are enabled. Note that allocation metrics available may be dependent on factors
+such as the task driver and control group (cgroup) version in use.
+
+| Metric                                        | Description                                                       | Unit        | Type    | Labels                                           |
+|-----------------------------------------------|-------------------------------------------------------------------|-------------|---------|--------------------------------------------------|
+| `nomad.client.allocs.complete`                | Number of complete allocations                                    | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.allocated`           | Total CPU resources allocated by the task across all cores        | MHz         | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.system`              | Total CPU resources consumed by the task in system space          | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_periods`   | Total number of CPU periods that the task was throttled           | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.throttled_time`      | Total time that the task was throttled                            | Nanoseconds | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_percent`       | Total CPU resources consumed by the task across all cores         | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks`         | CPU ticks consumed by the process in the last collection interval | Integer     | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.total_ticks_count`   | Total CPU ticks consumed by the task since startup                | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.cpu.user`                | Total CPU resources consumed by the task in the user space        | Percentage  | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.failed`                  | Number of failed allocations                                      | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.allocated`        | Amount of memory allocated by the task                            | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.cache`            | Amount of memory cached by the task                               | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_max_usage` | Maximum amount of memory ever used by the kernel for this task    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.kernel_usage`     | Amount of memory used by the kernel for this task                 | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_allocated`    | Maximum amount of oversubscription memory allocated by the task   | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.max_usage`        | Maximum amount of memory ever used by the task                    | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.rss`              | Amount of RSS memory consumed by the task                         | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.swap`             | Amount of memory swapped by the task                              | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.memory.usage`            | Total amount of memory used by the task                           | Bytes       | Gauge   | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.oom_killed`              | Number of oom-killed allocations                                  | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.restart`                 | Number of task restarts                                           | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+| `nomad.client.allocs.running`                 | Number of running allocations                                     | Integer     | Counter | alloc_id, host, job, namespace, task, task_group |
+
+## Job Summary Metrics
+
+Job summary metrics are emitted by the Nomad leader server.
+
+| Metric                             | Description                              | Unit    | Type  | Labels                           |
+| ---------------------------------- | ---------------------------------------- | ------- | ----- | -------------------------------- |
+| `nomad.nomad.job_summary.complete` | Number of complete allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.failed`   | Number of failed allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.lost`     | Number of lost allocations for a job     | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.unknown`  | Number of unknown allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.queued`   | Number of queued allocations for a job   | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.running`  | Number of running allocations for a job  | Integer | Gauge | host, job, namespace, task_group |
+| `nomad.nomad.job_summary.starting` | Number of starting allocations for a job | Integer | Gauge | host, job, namespace, task_group |
+
+## Job Status Metrics
+
+Job status metrics are emitted by the Nomad leader server.
+
+| Metric                           | Description            | Unit    | Type  | Labels |
+| -------------------------------- | ---------------------- | ------- | ----- | ------ |
+| `nomad.nomad.job_status.dead`    | Number of dead jobs    | Integer | Gauge | host   |
+| `nomad.nomad.job_status.pending` | Number of pending jobs | Integer | Gauge | host   |
+| `nomad.nomad.job_status.running` | Number of running jobs | Integer | Gauge | host   |
+
+## Server Metrics
+
+The following table includes metrics for overall cluster health in addition to
+those listed in [Key Metrics](#key-metrics) above.
+
+| Metric                                               | Description                                                                                                                                            | Unit                     | Type    | Labels                                                  |
+|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|---------|---------------------------------------------------------|
+| `nomad.memberlist.gossip`                            | Time elapsed to broadcast gossip messages                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.bootstrap`                          | Time elapsed for `ACL.Bootstrap` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_policies`                    | Time elapsed for `ACL.DeletePolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.delete_tokens`                      | Time elapsed for `ACL.DeleteTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policies`                       | Time elapsed for `ACL.GetPolicies` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_policy`                         | Time elapsed for `ACL.GetPolicy` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_token`                          | Time elapsed for `ACL.GetToken` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.get_tokens`                         | Time elapsed for `ACL.GetTokens` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_policies`                      | Time elapsed for `ACL.ListPolicies` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.list_tokens`                        | Time elapsed for `ACL.ListTokens` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.resolve_token`                      | Time elapsed for `ACL.ResolveToken` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_policies`                    | Time elapsed for `ACL.UpsertPolicies` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.acl.upsert_tokens`                      | Time elapsed for `ACL.UpsertTokens` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.exec`                             | Time elapsed to establish alloc exec                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_alloc`                        | Time elapsed for `Alloc.GetAlloc` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.get_allocs`                       | Time elapsed for `Alloc.GetAllocs` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.list`                             | Time elapsed for `Alloc.List` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.stop`                             | Time elapsed for `Alloc.Stop` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.alloc.update_desired_transition`        | Time elapsed for `Alloc.UpdateDesiredTransition` RPC call                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.blocked_evals.cpu`                      | Amount of CPU shares requested by blocked evals                                                                                                        | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.memory`                   | Amount of memory requested by blocked evals                                                                                                            | Integer                  | Gauge   | datacenter, host, node_class                            |
+| `nomad.nomad.blocked_evals.job.cpu`                  | Amount of CPU shares requested by blocked evals of a job                                                                                               | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.job.memory`               | Amount of memory requested by blocked evals of a job                                                                                                   | Integer                  | Gauge   | host, job, namespace                                    |
+| `nomad.nomad.blocked_evals.total_blocked`            | Count of evals in the blocked state for any reason (cluster resource exhaustion or quota limits)                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_escaped`            | Count of evals that have escaped computed node classes. This indicates a scheduler optimization was skipped and is not usually a source of concern.    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.blocked_evals.total_quota_limit`        | Count of blocked evals due to quota limits (the resources for these jobs are *not* counted in other blocked_evals metrics, except for `total_blocked`) | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_ready`                     | Count of batch evals ready to be scheduled                                                                                                             | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.batch_unacked`                   | Count of unacknowledged batch evals                                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.eval_waiting`                    | Time elapsed with evaluation waiting to be enqueued                                                                                                    | Milliseconds             | Gauge   | eval_id, job, namespace                                 |
+| `nomad.nomad.broker.process_time`                    | Time elapsed while the evaluation was dequeued and finished processing. This metric is only valid within a single term                                 | ms / Evaluation Process  | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.response_time`                   | Time elapsed from when the evaluation was last enqueued and finished processing. This metric is only valid within a single term                        | ms / Evaluation Response | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.broker.service_ready`                   | Count of service evals ready to be scheduled                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.service_unacked`                 | Count of unacknowledged service evals                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_ready`                    | Count of system evals ready to be scheduled                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.system_unacked`                  | Count of unacknowledged system evals                                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_ready`                     | Count of evals in the ready state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.total_waiting`                   | Count of evals waiting to be enqueued                                                                                                                  | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.broker.wait_time`                       | Time elapsed while the evaluation was ready to be processed and waiting to be dequeued. This metric is only valid within a single term                 | ms / Evaluation Wait     | Timer   | host, job, namespace, eval_type, triggered_by           |
+| `nomad.nomad.client.batch_deregister`                | Time elapsed for `Node.BatchDeregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.deregister`                      | Time elapsed for `Node.Deregister` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_si_token`                 | Time elapsed for `Node.DeriveSIToken` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.derive_vault_token`              | Time elapsed for `Node.DeriveVaultToken` RPC call                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.emit_events`                     | Time elapsed for `Node.EmitEvents` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.evaluate`                        | Time elapsed for `Node.Evaluate` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_allocs`                      | Time elapsed for `Node.GetAllocs` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_client_allocs`               | Time elapsed for `Node.GetClientAllocs` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.get_node`                        | Time elapsed for `Node.GetNode` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.list`                            | Time elapsed for `Node.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.register`                        | Time elapsed for `Node.Register` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.stats`                           | Time elapsed for `Client.Stats` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_alloc`                    | Time elapsed for `Node.UpdateAlloc` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_drain`                    | Time elapsed for `Node.UpdateDrain` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_eligibility`              | Time elapsed for `Node.UpdateEligibility` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client.update_status`                   | Time elapsed for `Node.UpdateStatus` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect_all` | Time elapsed for `ClientAllocations.GarbageCollectAll` RPC call                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.garbage_collect`     | Time elapsed for `ClientAllocations.GarbageCollect` RPC call                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.restart`             | Time elapsed for `ClientAllocations.Restart` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.signal`              | Time elapsed for `ClientAllocations.Signal` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_allocations.stats`               | Time elapsed for `ClientAllocations.Stats` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.attach_volume`    | Time elapsed for `Controller.AttachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.detach_volume`    | Time elapsed for `Controller.DetachVolume` RPC call                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_controller.validate_volume`  | Time elapsed for `Controller.ValidateVolume` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.client_csi_node.detach_volume`          | Time elapsed for `Node.DetachVolume` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.allocations`                 | Time elapsed for `Deployment.Allocations` RPC call                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.cancel`                      | Time elapsed for `Deployment.Cancel` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.fail`                        | Time elapsed for `Deployment.Fail` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.get_deployment`              | Time elapsed for `Deployment.GetDeployment` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.list`                        | Time elapsed for `Deployment.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.pause`                       | Time elapsed for `Deployment.Pause` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.promote`                     | Time elapsed for `Deployment.Promote` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.reap`                        | Time elapsed for `Deployment.Reap` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.run`                         | Time elapsed for `Deployment.Run` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.set_alloc_health`            | Time elapsed for `Deployment.SetAllocHealth` RPC call                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.deployment.unblock`                     | Time elapsed for `Deployment.Unblock` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.ack`                               | Time elapsed for `Eval.Ack` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.allocations`                       | Time elapsed for `Eval.Allocations` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.create`                            | Time elapsed for `Eval.Create` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.dequeue`                           | Time elapsed for `Eval.Dequeue` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.get_eval`                          | Time elapsed for `Eval.GetEval` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.list`                              | Time elapsed for `Eval.List` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.nack`                              | Time elapsed for `Eval.Nack` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reap`                              | Time elapsed for `Eval.Reap` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.reblock`                           | Time elapsed for `Eval.Reblock` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.eval.update`                            | Time elapsed for `Eval.Update` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.list`                       | Time elapsed for `FileSystem.List` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.logs`                       | Time elapsed to establish `FileSystem.Logs` RPC                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stat`                       | Time elapsed for `FileSystem.Stat` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.file_system.stream`                     | Time elapsed to establish `FileSystem.Stream` RPC                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_client_update`                | Time elapsed to apply `AllocClientUpdate` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.alloc_update_desired_transition`    | Time elapsed to apply `AllocUpdateDesiredTransition` raft entry                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_delete`            | Time elapsed to apply `ApplyACLPolicyDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_policy_upsert`            | Time elapsed to apply `ApplyACLPolicyUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_bootstrap`          | Time elapsed to apply `ApplyACLTokenBootstrap` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_delete`             | Time elapsed to apply `ApplyACLTokenDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_acl_token_upsert`             | Time elapsed to apply `ApplyACLTokenUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_plugin_delete`            | Time elapsed to apply `ApplyCSIPluginDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_batch_claim`       | Time elapsed to apply `ApplyCSIVolumeBatchClaim` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_claim`             | Time elapsed to apply `ApplyCSIVolumeClaim` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_deregister`        | Time elapsed to apply `ApplyCSIVolumeDeregister` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_csi_volume_register`          | Time elapsed to apply `ApplyCSIVolumeRegister` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_alloc_health`      | Time elapsed to apply `ApplyDeploymentAllocHealth` raft entry                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_delete`            | Time elapsed to apply `ApplyDeploymentDelete` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_promotion`         | Time elapsed to apply `ApplyDeploymentPromotion` raft entry                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_deployment_status_update`     | Time elapsed to apply `ApplyDeploymentStatusUpdate` raft entry                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_stability`                | Time elapsed to apply `ApplyJobStability` raft entry                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_job_version_tag`              | Time elapsed to apply `ApplyJobVersionTag` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_delete`             | Time elapsed to apply `ApplyNamespaceDelete` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_namespace_upsert`             | Time elapsed to apply `ApplyNamespaceUpsert` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_upsert`             | Time elapsed to apply `ApplyNodePoolUpsert` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_node_pool_delete`             | Time elapsed to apply `ApplyNodePoolDelete` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_plan_results`                 | Time elapsed to apply `ApplyPlanResults` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.apply_scheduler_config`             | Time elapsed to apply `ApplySchedulerConfig` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.autopilot`                          | Time elapsed to apply `Autopilot` raft entry                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_job`               | Time elapsed to apply `BatchDeregisterJob` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_deregister_node`              | Time elapsed to apply `BatchDeregisterNode` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.batch_node_drain_update`            | Time elapsed to apply `BatchNodeDrainUpdate` raft entry                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.cluster_meta`                       | Time elapsed to apply `ClusterMeta` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.delete_eval`                        | Time elapsed to apply `DeleteEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_job`                     | Time elapsed to apply `DeregisterJob` raft entry                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_node`                    | Time elapsed to apply `DeregisterNode` raft entry                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_si_accessor`             | Time elapsed to apply `DeregisterSITokenAccessor` raft entry                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.deregister_vault_accessor`          | Time elapsed to apply `DeregisterVaultAccessor` raft entry                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_drain_update`                  | Time elapsed to apply `NodeDrainUpdate` raft entry                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_eligibility_update`            | Time elapsed to apply `NodeEligibilityUpdate` raft entry                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.node_status_update`                 | Time elapsed to apply `NodeStatusUpdate` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.persist`                            | Time elapsed to apply `Persist` raft entry                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_job`                       | Time elapsed to apply `RegisterJob` raft entry                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.register_node`                      | Time elapsed to apply `RegisterNode` raft entry                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.update_eval`                        | Time elapsed to apply `UpdateEval` raft entry                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_node_events`                 | Time elapsed to apply `UpsertNodeEvents` raft entry                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_scaling_event`               | Time elapsed to apply `UpsertScalingEvent` raft entry                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_si_accessor`                 | Time elapsed to apply `UpsertSITokenAccessors` raft entry                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.fsm.upsert_vault_accessor`              | Time elapsed to apply `UpsertVaultAccessor` raft entry                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.allocations`                        | Time elapsed for `Job.Allocations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.batch_deregister`                   | Time elapsed for `Job.BatchDeregister` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deployments`                        | Time elapsed for `Job.Deployments` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.deregister`                         | Time elapsed for `Job.Deregister` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.dispatch`                           | Time elapsed for `Job.Dispatch` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluate`                           | Time elapsed for `Job.Evaluate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.evaluations`                        | Time elapsed for `Job.Evaluations` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job_versions`                   | Time elapsed for `Job.GetJobVersions` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.get_job`                            | Time elapsed for `Job.GetJob` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.latest_deployment`                  | Time elapsed for `Job.LatestDeployment` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.list`                               | Time elapsed for `Job.List` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.plan`                               | Time elapsed for `Job.Plan` RPC call                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.register`                           | Time elapsed for `Job.Register` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.revert`                             | Time elapsed for `Job.Revert` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale_status`                       | Time elapsed for `Job.ScaleStatus` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.scale`                              | Time elapsed for `Job.Scale` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.stable`                             | Time elapsed for `Job.Stable` RPC call                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job.validate`                           | Time elapsed for `Job.Validate` RPC call                                                                                                               | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.job_summary.get_job_summary`            | Time elapsed for `Job.Timer` RPC call                                                                                                                  | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.barrier`                         | Time elapsed to establish a raft barrier during leader transition                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcileMember`                 | Time elapsed to reconcile a serf peer with state store                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.leader.reconcile`                       | Time elapsed to reconcile all serf peers with state store                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.delete_namespaces`            | Time elapsed for `Namespace.DeleteNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespace`                | Time elapsed for `Namespace.GetNamespace`                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.get_namespaces`               | Time elapsed for `Namespace.GetNamespaces`                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.list_namespace`               | Time elapsed for `Namespace.ListNamespaces`                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.namespace.upsert_namespaces`            | Time elapsed for `Namespace.UpsertNamespaces`                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list`                         | Time elapsed for `NodePool.List` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_jobs`                    | Time elapsed for `NodePool.ListJobs` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.list_nodes`                   | Time elapsed for `NodePool.ListNodes` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.get_node_pool`                | Time elapsed for `NodePool.GetNodePool` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.upsert_node_pools`            | Time elapsed for `NodePool.UpsertNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.node_pool.delete_node_pools`            | Time elapsed for `NodePool.DeleteNodePools` RPC call                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.periodic.force`                         | Time elapsed for `Periodic.Force` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.apply`                             | Time elapsed to apply a plan                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.evaluate`                          | Time elapsed to evaluate a plan                                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.node_rejected`                     | Number of times a node has had a plan rejected                                                                                                         | Integer                  | Counter | host, node_id                                           |
+| `nomad.nomad.plan.rejection_tracker.node_score`      | Number of times a node has had a plan rejected within the tracker window                                                                               | Integer                  | Gauge   | host, node_id                                           |
+| `nomad.nomad.plan.queue_depth`                       | Count of evals in the plan queue                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.plan.submit`                            | Time elapsed for `Plan.Submit` RPC call                                                                                                                | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plan.wait_for_index`                    | Time elapsed that planner waits for the raft index of the plan to be processed                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.delete`                          | Time elapsed for `CSIPlugin.Delete` RPC call                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.get`                             | Time elapsed for `CSIPlugin.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.plugin.list`                            | Time elapsed for `CSIPlugin.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.quota.utilization.cpu`                  | Utilization of the CPU quota                                                                                                                           | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.cores`                | Utilization of the CPU Cores quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.quota.utilization.memory_mb`            | Utilization of the Memory MB quota                                                                                                                     | Integer                  | Gauge   | quota_name, namespace, region                           |
+| `nomad.nomad.scaling.get_policy`                     | Time elapsed for `Scaling.GetPolicy` RPC call                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.scaling.list_policies`                  | Time elapsed for `Scaling.ListPolicies` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.search.prefix_search`                   | Time elapsed for `Search.PrefixSearch` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.create_token`                     | Time elapsed to create Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.distributed_tokens_revoked`       | Count of revoked tokens                                                                                                                                | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.lookup_token`                     | Time elapsed to lookup Vault token                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.renew_failed`                     | Count of failed attempts to renew Vault token                                                                                                          | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.vault.renew`                            | Time elapsed to renew Vault token                                                                                                                      | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.revoke_tokens`                    | Time elapsed to revoke Vault tokens                                                                                                                    | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_last_renewal`               | Time since last successful Vault token renewal                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_next_renewal`               | Time until next Vault token renewal attempt                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.token_ttl`                        | Time to live for Vault token                                                                                                                           | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.vault.undistributed_tokens_abandoned`   | Count of abandoned tokens                                                                                                                              | Integer                  | Gauge   | host                                                    |
+| `nomad.nomad.volume.claim`                           | Time elapsed for `CSIVolume.Claim` RPC call                                                                                                            | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.deregister`                      | Time elapsed for `CSIVolume.Deregister` RPC call                                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.get`                             | Time elapsed for `CSIVolume.Get` RPC call                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.list`                            | Time elapsed for `CSIVolume.List` RPC call                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.register`                        | Time elapsed for `CSIVolume.Register` RPC call                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.volume.unpublish`                       | Time elapsed for `CSIVolume.Unpublish` RPC call                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.create_eval`                     | Time elapsed for worker to create an eval                                                                                                              | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.dequeue_eval`                    | Time elapsed for worker to dequeue an eval                                                                                                             | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.invoke_scheduler.<type>`         | Time elapsed for worker to invoke the scheduler of type `<type>`                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.send_ack`                        | Time elapsed for worker to send acknowledgement                                                                                                        | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.submit_plan`                     | Time elapsed for worker to submit plan                                                                                                                 | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.update_eval`                     | Time elapsed for worker to submit updated eval                                                                                                         | Milliseconds             | Timer   | host                                                    |
+| `nomad.nomad.worker.wait_for_index`                  | Time elapsed that worker waits for the raft index of the eval to be processed                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.appliedIndex`                            | Current index applied to FSM                                                                                                                           | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.barrier`                                 | Count of blocking raft API calls                                                                                                                       | Integer                  | Counter | host                                                    |
+| `nomad.raft.commitNumLogs`                           | Count of logs enqueued                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.commitTime`                              | Time elapsed to commit writes                                                                                                                          | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.apply`                               | Time elapsed to apply write to FSM                                                                                                                     | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.fsm.enqueue`                             | Time elapsed to enqueue write to FSM                                                                                                                   | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.lastIndex`                               | Most recent index seen                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.leader.dispatchLog`                      | Time elapsed to write log, mark in flight, and start replication                                                                                       | Milliseconds             | Timer   | host                                                    |
+| `nomad.raft.leader.dispatchNumLogs`                  | Count of logs dispatched                                                                                                                               | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.replication.appendEntries`               | Raft transaction commit time                                                                                                                           | ms / Raft Log Append     | Timer   |                                                         |
+| `nomad.raft.state.candidate`                         | Count of entering candidate state                                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.follower`                          | Count of entering follower state                                                                                                                       | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.state.leader`                            | Count of entering leader state                                                                                                                         | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.heartbeat_timeout`            | Count of failing to heartbeat and starting election                                                                                                    | Integer                  | Gauge   | host                                                    |
+| `nomad.raft.transition.leader_lease_timeout`         | Count of stepping down as leader after losing quorum                                                                                                   | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.free_count`                           | Count of objects freed from heap by go runtime GC                                                                                                      | Integer                  | Gauge   | host                                                    |
+| `nomad.runtime.gc_pause_ns`                          | Go runtime GC pause times                                                                                                                              | Nanoseconds              | Summary | host                                                    |
+| `nomad.runtime.sys_bytes`                            | Go runtime GC metadata size                                                                                                                            | # of bytes               | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_pause_ns`                    | Total elapsed go runtime GC pause times                                                                                                                | Nanoseconds              | Gauge   | host                                                    |
+| `nomad.runtime.total_gc_runs`                        | Count of go runtime GC runs                                                                                                                            | Integer                  | Gauge   | host                                                    |
+| `nomad.serf.queue.Event`                             | Count of memberlist events received                                                                                                                    | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Intent`                            | Count of memberlist changes                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.serf.queue.Query`                             | Count of memberlist queries                                                                                                                            | Integer                  | Summary | host                                                    |
+| `nomad.scheduler.allocs.rescheduled.attempted`       | Count of attempts to reschedule an allocation                                                                                                          | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.limit`           | Maximum number of attempts to reschedule an allocation                                                                                                 | Integer                  | Count   | alloc_id, job, namespace, task_group                    |
+| `nomad.scheduler.allocs.rescheduled.wait_until`      | Time that a rescheduled allocation will be delayed                                                                                                     | Float                    | Gauge   | alloc_id, job, namespace, task_group, follow_up_eval_id |
+| `nomad.state.snapshotIndex`                          | Current snapshot index                                                                                                                                 | Integer                  | Gauge   | host                                                    |
+
+## Raft BoltDB Metrics
+
+Raft database metrics are emitted by the `raft-boltdb` library.
+
+| Metric                                    | Description                               | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------- | ----------- | ------- |
+| `nomad.raft.boltdb.numFreePages`          | Number of free pages                      | Integer     | Gauge   |
+| `nomad.raft.boltdb.numPendingPages`       | Number of pending pages                   | Integer     | Gauge   |
+| `nomad.raft.boltdb.freePageBytes`         | Number of free page bytes                 | Integer     | Gauge   |
+| `nomad.raft.boltdb.freelistBytes`         | Number of freelist bytes                  | Integer     | Gauge   |
+| `nomad.raft.boltdb.totalReadTxn`          | Count of total read transactions          | Integer     | Counter |
+| `nomad.raft.boltdb.openReadTxn`           | Number of current open read transactions  | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageCount`     | Number of pages in use                    | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.pageAlloc`     | Number of page allocations                | Integer     | Gauge   |
+| `nomad.raft.boltdb.txstats.cursorCount`   | Count of total database cursors           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeCount`     | Count of total database nodes             | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.nodeDeref`     | Count of total database node dereferences | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalance`     | Count of total rebalance operations       | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.rebalanceTime` | Sample of rebalance operation times       | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.split`         | Count of total split operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spill`         | Count of total spill operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.spillTime`     | Sample of spill operation times           | Nanoseconds | Summary |
+| `nomad.raft.boltdb.txstats.write`         | Count of total write operations           | Integer     | Counter |
+| `nomad.raft.boltdb.txstats.writeTime`     | Sample of write operation times           | Nanoseconds | Summary |
+
+## Agent Metrics
+
+Agent metrics are emitted by all Nomad agents running in either client or server mode.
+
+| Metric                                    | Description                                           | Unit        | Type    |
+| ----------------------------------------- | ----------------------------------------------------- | ----------- | ------- |
+| `nomad.agent.http.exceeded`               | Count of HTTP connections exceeding concurrency limit | Integer     | Counter |
+
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[sticky]: /nomad/docs/job-specification/ephemeral_disk#sticky
+[s_port_plan_failure]: https://developer.hashicorp.com/nomad/s/port-plan-failure
+[`disable_allocation_hook_metrics`]: /nomad/docs/configuration/telemetry#disable_allocation_hook_metrics
diff --git a/content/nomad/v1.9.x/content/docs/operations/monitoring-nomad.mdx b/content/nomad/v1.9.x/content/docs/operations/monitoring-nomad.mdx
new file mode 100644
index 0000000000..2823055ba1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/monitoring-nomad.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Monitoring Nomad
+description: |-
+  Overview of runtime metrics available in Nomad along with monitoring and
+  alerting.
+---
+
+# Monitoring Nomad
+
+The Nomad client and server agents collect a wide range of runtime metrics.
+These metrics are useful for monitoring the health and performance of Nomad
+clusters. Careful monitoring can spot trends before they cause issues and help
+debug issues if they arise.
+
+All Nomad agents, both servers and clients, report basic system and Go runtime
+metrics.
+
+Nomad servers all report many metrics, but some metrics are specific to the
+leader server. Since leadership may change at any time, these metrics should be
+monitored on all servers. Missing (or 0) metrics from non-leaders may be safely
+ignored.
+
+Nomad clients have separate metrics for the host they are running on as well as
+for each allocation being run. Both of these metrics [must be explicitly
+enabled][telemetry-block].
+
+By default, the Nomad agent collects telemetry data at a [1 second
+interval][collection-interval]. Note that Nomad supports [gauges, counters, and
+timers][metric-types].
+
+There are three ways to obtain metrics from Nomad:
+
+- Query the [/v1/metrics API endpoint][metrics-api-endpoint] to return metrics
+  for the current Nomad process. This endpoint supports Prometheus formatted
+  metrics.
+
+- Send the USR1 signal to the Nomad process. This will dump the current
+  telemetry information to STDERR (on Linux).
+
+- Configure Nomad to automatically forward metrics to a third-party provider
+  such as [DataDog][datadog-telem], [Prometheus][prometheus-telem],
+  [statsd][statsd-telem], and [Circonus][circonus-telem].
+
+## Alerting
+
+The recommended practice for alerting is to leverage the alerting capabilities
+of your monitoring provider. Nomad’s intention is to surface metrics that enable
+users to configure the necessary alerts using their existing monitoring systems
+as a scaffold, rather than to natively support alerting. Here are a few common
+patterns.
+
+- Export metrics from Nomad to Prometheus using the [StatsD
+  exporter][statsd-exporter], define [alerting rules][alerting-rules] in
+  Prometheus, and use [Alertmanager][alertmanager] for summarization and
+  routing/notifications (to PagerDuty, Slack, etc.). A similar workflow is
+  supported for [Datadog][datadog-alerting].
+
+- Periodically submit test jobs into Nomad to determine if your application
+  deployment pipeline is working end-to-end. This pattern is well-suited to
+  batch processing workloads.
+
+- Deploy Nagios on Nomad. Centrally manage Nomad job files and add the Nagios
+  monitor when a new Nomad job is added. When a job is removed, remove the
+  Nagios monitor. Map Consul alerts to the Nagios monitor. This provides a
+  job-specific alerting system.
+
+- Write a script that looks at the history of each batch job to determine
+  whether or not the job is in an unhealthy state, updating your monitoring
+  system as appropriate. In many cases, it may be ok if a given batch job fails
+  occasionally, as long as it goes back to passing.
+
+# Key Performance Indicators
+
+Nomad servers' memory, CPU, disk, and network usage all scales linearly with
+cluster size and scheduling throughput. The most important aspect of ensuring
+Nomad operates normally is monitoring these system resources to ensure the
+servers are not encountering resource constraints.
+
+The sections below cover a number of other important metrics.
+
+## Consensus Protocol (Raft)
+
+Nomad uses the Raft consensus protocol for leader election and state
+replication. Spurious leader elections can be caused by networking
+issues between the servers, insufficient CPU resources, or
+insufficient disk IOPS. Users in cloud environments often bump their
+servers up to the next instance class with improved networking and CPU
+to stabilize leader elections, or switch to higher-performance disks.
+
+The `nomad.raft.leader.lastContact` metric is a general indicator of
+Raft latency which can be used to observe how Raft timing is
+performing and guide infrastructure provisioning. If this number
+trends upwards, look at CPU, disk IOPs, and network
+latency. `nomad.raft.leader.lastContact` should not get too close to
+the leader lease timeout of 500ms.
+
+The `nomad.raft.replication.appendEntries` metric is an indicator of
+the time it takes for a Raft transaction to be replicated to a quorum
+of followers. If this number trends upwards, check the disk I/O on the
+followers and network latency between the leader and the followers.
+
+The details for how to examine CPU, IO operations, and networking are
+specific to your platform and environment. On Linux, the `sysstat`
+package contains a number of useful tools. Here are examples to
+consider.
+
+- **CPU** - `vmstat 1`, cloud provider metrics for "CPU %"
+
+- **IO** - `iostat`, `sar -d`, cloud provider metrics for "volume
+  write/read ops" and "burst balance"
+
+- **Network** - `sar -n`, `netstat -s`, cloud provider metrics for
+  interface "allowance"
+
+The `nomad.raft.fsm.apply` metric is an indicator of the time it takes
+for a server to apply Raft entries to the internal state machine. If
+this number trends upwards, look at the `nomad.nomad.fsm.*` metrics to
+see if a specific Raft entry is increasing in latency. You can compare
+this to warn-level logs on the Nomad servers for `attempting to apply
+large raft entry`. If a specific type of message appears here, there
+may be a job with a large job specification or dispatch payload that
+is increasing the time it takes to apply Raft messages. Try shrinking the size
+of the job either by putting distinct task groups into separate jobs,
+downloading templates instead of embedding them, or reducing the `count` on
+task groups.
+
+## Scheduling
+
+The [Scheduling] documentation describes the workflow of how evaluations become
+scheduled plans and placed allocations.
+
+### Progress
+
+There is a class of bug possible in Nomad where the two parts of the scheduling
+pipeline, the workers and the leader's plan applier, *disagree* about the
+validity of a plan. In the pathological case this can cause a job to never
+finish scheduling, as workers produce the same plan and the plan applier
+repeatedly rejects it.
+
+While this class of bug is very rare, it can be detected by repeated log lines
+on the Nomad servers containing `plan for node rejected`:
+
+```
+nomad: plan for node rejected: node_id=0fa84370-c713-b914-d329-f6485951cddc reason="reserved port collision" eval_id=098a5
+```
+
+While it is possible for these log lines to occur infrequently due to normal
+cluster conditions, they should not appear repeatedly and prevent the job from
+eventually running (look up the evaluation ID logged to find the job).
+
+#### Plan rejection tracker
+
+Nomad provides a mechanism to track the history of plan rejections per client
+and mark them as ineligible if the number goes above a given threshold within a
+time window. This functionality can be enabled using the
+[`plan_rejection_tracker`] server configuration.
+
+When a node is marked as ineligible due to excessive plan rejections, the
+following node event is registered:
+
+```
+Node marked as ineligible for scheduling due to multiple plan rejections, refer to https://developer.hashicorp.com/nomad/s/port-plan-failure for more information
+```
+
+Along with the log line:
+
+```
+[WARN]  nomad.state_store: marking node as ineligible due to multiple plan rejections: node_id=67af2541-5e96-6f54-9095-11089d627626
+```
+
+If a client is marked as ineligible due to repeated plan rejections, try
+[draining] the node and shutting it down. Misconfigurations not caught by
+validation can cause nodes to enter this state: [#11830][gh-11830].
+
+If the `plan for node rejected` log *does* appear repeatedly with the same
+`node_id` referenced but the client is not being set as ineligible you can try
+adjusting the [`plan_rejection_tracker`] configuration of servers.
+
+### Performance
+
+The following metrics allow observing changes in throughput at the various
+points in the scheduling process.
+
+- **nomad.worker.invoke_scheduler.<type\>** - The time to run the
+  scheduler of the given type. Each scheduler worker handles one
+  evaluation at a time, entirely in-memory. If this metric increases,
+  examine the CPU and memory resources of the scheduler.
+
+- **nomad.blocked_evals.total_blocked** - The number of blocked
+  evaluations. Blocked evaluations are created when the scheduler
+  cannot place all allocations as part of a plan. Blocked evaluations
+  will be re-evaluated so that changes in cluster resources can be
+  used for the blocked evaluation's allocations. An increase in
+  blocked evaluations may mean that the cluster's clients are low in
+  resources or that job have been submitted that can never have all
+  their allocations placed.
+
+- **nomad.broker.total_unacked** - The number of unacknowledged
+  evaluations. When an evaluation has been processed, the worker sends
+  an acknowledgment RPC to the leader to signal to the eval broker
+  that processing is complete. The unacked evals are those that are
+  in-flight in the scheduler and have not yet been acknowledged. An
+  increase in unacknowledged evaluations may mean that the schedulers
+  have a large queue of evaluations to process. See the
+  `invoke_scheduler` metric (above) and examine the CPU and memory
+  resources of the scheduler. Nomad also emits a similar metric for
+  each individual scheduler. For example `nomad.broker.batch_unacked`
+  shows the number of unacknowledged evaluations for the batch
+  scheduler.
+
+- **nomad.broker.total_pending** - The number of pending evaluations in the eval
+  broker. Nomad processes only one evaluation for a given job concurrently. When
+  an unacked evaluation is acknowledged, Nomad will discard all but the latest
+  evaluation for a job. An increase in this metric may mean that the cluster
+  state is changing more rapidly than the schedulers can keep up.
+
+- **nomad.plan.evaluate** - The time to evaluate a scheduler plan
+  submitted by a worker. This operation happens on the leader to
+  serialize the plans of all the scheduler workers. This happens
+  entirely in memory on the leader. If this metric increases, examine
+  the CPU and memory resources of the leader.
+
+- **nomad.plan.wait_for_index** - The time required for the planner to wait for
+  the Raft index of the plan to be processed. If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above. If this metric approaches 5
+  seconds, scheduling operations may fail and be retried. If possible reduce
+  scheduling load until metrics improve.
+
+- **nomad.plan.submit** - The time to submit a scheduler plan from the
+  worker to the leader. This operation requires writing to Raft and
+  includes the time from `nomad.plan.evaluate` and
+  `nomad.plan.wait_for_index` (above). If this metric increases, refer
+  to the [Consensus Protocol (Raft)] section above.
+
+- **nomad.plan.queue_depth** - The number of scheduler plans waiting
+  to be evaluated after being submitted. If this metric increases,
+  examine the `nomad.plan.evaluate` and `nomad.plan.submit` metrics to
+  determine if the problem is in general leader resources or Raft
+  performance.
+
+Upticks in any of the above metrics indicate a decrease in scheduler
+throughput.
+
+## Capacity
+
+The importance of monitoring resource availability is workload specific. Batch
+processing workloads often operate under the assumption that the cluster should
+be at or near capacity, with queued jobs running as soon as adequate resources
+become available. Clusters that are primarily responsible for long running
+services with an uptime requirement may want to maintain headroom at 20% or
+more. The following metrics can be used to assess capacity across the cluster on
+a per client basis.
+
+- **nomad.client.allocated.cpu**
+- **nomad.client.unallocated.cpu**
+- **nomad.client.allocated.disk**
+- **nomad.client.unallocated.disk**
+- **nomad.client.allocated.iops**
+- **nomad.client.unallocated.iops**
+- **nomad.client.allocated.memory**
+- **nomad.client.unallocated.memory**
+
+## Task Resource Consumption
+
+The metrics listed [here][allocation-metrics] can be used to track resource
+consumption on a per task basis. For user facing services, it is common to alert
+when the CPU is at or above the reserved resources for the task.
+
+## Job and Task Status
+
+See [Job Summary Metrics] for monitoring the health and status of workloads
+running on Nomad.
+
+## Runtime Metrics
+
+Runtime metrics apply to all clients and servers. The following metrics are
+general indicators of load and memory pressure.
+
+- **nomad.runtime.num_goroutines**
+- **nomad.runtime.heap_objects**
+- **nomad.runtime.alloc_bytes**
+
+It is recommended to alert on upticks in any of the above, server memory usage
+in particular.
+
+## Federated Deployments (Serf)
+
+Nomad uses the membership and failure detection capabilities of the Serf library
+to maintain a single, global gossip pool for all servers in a federated
+deployment. An uptick in `member.flap` and/or `msg.suspect` is a reliable indicator
+that membership is unstable.
+
+If these metrics increase, look at CPU load on the servers and network
+latency and packet loss for the [Serf] address.
+
+[alerting-rules]: https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/
+[alertmanager]: https://prometheus.io/docs/alerting/alertmanager/
+[allocation-metrics]: /nomad/docs/operations/metrics-reference#allocation-metrics
+[circonus-telem]: /nomad/docs/configuration/telemetry#circonus
+[collection-interval]: /nomad/docs/configuration/telemetry#collection_interval
+[datadog-alerting]: https://www.datadoghq.com/blog/monitoring-101-alerting/
+[datadog-telem]: /nomad/docs/configuration/telemetry#datadog
+[draining]: /nomad/tutorials/manage-clusters/node-drain
+[gh-11830]: https://github.com/hashicorp/nomad/pull/11830
+[metric-types]: /nomad/docs/operations/metrics-reference#metric-types
+[metrics-api-endpoint]: /nomad/api-docs/metrics
+[prometheus-telem]: /nomad/docs/configuration/telemetry#prometheus
+[`plan_rejection_tracker`]: /nomad/docs/configuration/server#plan_rejection_tracker
+[serf]: /nomad/docs/configuration#serf-1
+[statsd-exporter]: https://github.com/prometheus/statsd_exporter
+[statsd-telem]: /nomad/docs/configuration/telemetry#statsd
+[statsite-telem]: /nomad/docs/configuration/telemetry#statsite
+[tagged-metrics]: /nomad/docs/operations/metrics-reference#tagged-metrics
+[telemetry-block]: /nomad/docs/configuration/telemetry
+[Consensus Protocol (Raft)]: /nomad/docs/operations/monitoring-nomad#consensus-protocol-raft
+[Job Summary Metrics]: /nomad/docs/operations/metrics-reference#job-summary-metrics
+[Scheduling]: /nomad/docs/concepts/scheduling/scheduling
diff --git a/content/nomad/v1.9.x/content/docs/operations/nomad-agent.mdx b/content/nomad/v1.9.x/content/docs/operations/nomad-agent.mdx
new file mode 100644
index 0000000000..7dc11710a5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/nomad-agent.mdx
@@ -0,0 +1,188 @@
+---
+layout: docs
+page_title: Nomad Agent
+description: |-
+  The Nomad agent is a long running process which can be used either in
+  a client or server mode.
+---
+
+# Operating Nomad Agents
+
+The Nomad agent is a long running process which runs on every machine that
+is part of the Nomad cluster. The behavior of the agent depends on if it is
+running in client or server mode. Clients are responsible for running tasks,
+while servers are responsible for managing the cluster.
+
+Client mode agents are relatively simple. They make use of fingerprinting
+to determine the capabilities and resources of the host machine, as well as
+determining what [drivers](/nomad/docs/drivers) are available. Clients
+register with servers to provide the node information, heartbeat to provide
+liveness, and run any tasks assigned to them.
+
+Servers take on the responsibility of being part of the
+[consensus protocol](/nomad/docs/concepts/consensus) and [gossip protocol](/nomad/docs/concepts/gossip).
+The consensus protocol, powered by Raft, allows the servers to perform
+leader election and state replication. The gossip protocol allows for simple
+clustering of servers and multi-region federation. The higher burden on the
+server nodes means that usually they should be run on dedicated instances --
+they are more resource intensive than a client node.
+
+Client nodes make up the majority of the cluster, and are very lightweight as
+they interface with the server nodes and maintain very little state of their
+own. Each cluster has usually 3 or 5 server mode agents and potentially
+thousands of clients.
+
+## Running an Agent
+
+The agent is started with the [`nomad agent` command](/nomad/docs/commands/agent). This
+command blocks, running forever or until told to quit. The agent command takes a variety
+of configuration options, but most have sane defaults.
+
+-> **Note:** If you are running Nomad on Linux, you'll need to run client agents
+as root (or with `sudo`) so that cpuset accounting and network namespaces work
+correctly.
+
+When running `nomad agent`, you should see output similar to this:
+
+```shell-session
+$ sudo nomad agent -dev
+==> Starting Nomad agent...
+==> Nomad agent configuration:
+
+                Client: true
+             Log Level: INFO
+                Region: global (DC: dc1)
+                Server: true
+
+==> Nomad agent started! Log data will stream in below:
+
+    [INFO] serf: EventMemberJoin: server-1.node.global 127.0.0.1
+    [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core]
+...
+```
+
+There are several important messages that `nomad agent` outputs:
+
+- **Client**: This indicates whether the agent has enabled client mode.
+  Client nodes fingerprint their host environment, register with servers,
+  and run tasks.
+
+- **Log Level**: This indicates the configured log level. Only messages with
+  an equal or higher severity will be logged. This can be tuned to increase
+  verbosity for debugging, or reduced to avoid noisy logging.
+
+- **Region**: This is the region and datacenter in which the agent is configured
+  to run. Nomad has first-class support for multi-datacenter and multi-region
+  configurations. The `-region` and `-dc` flags can be used to set the region
+  and datacenter. The default is the `global` region in `dc1`.
+
+- **Server**: This indicates whether the agent has enabled server mode.
+  Server nodes have the extra burden of participating in the consensus protocol,
+  storing cluster state, and making scheduling decisions.
+
+## Stopping an Agent
+
+By default, any stop signal to an agent (interrupt or terminate) will cause the
+agent to exit after ensuring its internal state is committed to disk as
+needed. You can configuration additional behaviors by setting shutdown
+[`leave_on_interrupt`][] or [`leave_on_terminate`][] to respond to the
+respective signals.
+
+For servers, when `leave_on_interrupt` or `leave_on_terminate` are set the
+server will notify other servers of their intention to leave the cluster, which
+allows them to leave the [consensus][] peer set. It is especially important that
+a server node be allowed to leave gracefully so that there will be a minimal
+impact on availability as the server leaves the consensus peer set. If a server
+does not gracefully leave, and will not return into service, the [`server
+force-leave` command][] should be used to eject it from the consensus peer set.
+
+For clients, when `leave_on_interrupt` or `leave_on_terminate` are set and the
+client is configured with [`drain_on_shutdown`][], the client will drain its
+workloads before shutting down.
+
+## Signal Handling
+
+In addition to the optional handling of interrupt (`SIGINT`) and terminate
+signals (`SIGTERM`) described in [Stopping an Agent](#stopping-an-agent), Nomad
+supports special behavior for several other signals useful for debugging.
+
+* `SIGHUP` will cause Nomad to [reload its configuration][].
+* `SIGUSR1` will cause Nomad to print its [metrics][] without stopping the
+  agent.
+* `SIGQUIT`, `SIGILL`, `SIGTRAP`, `SIGABRT`, `SIGSTKFLT`, `SIGEMT`, or `SIGSYS`
+  signals are handled by the Go runtime and will cause the Nomad agent to exit
+  and print its stack trace.
+
+When using the official HashiCorp packages on Linux, you can send these signals
+via `systemctl`. For example, to print the Nomad agent's metrics:
+
+```shell-session
+$ sudo systemctl kill nomad -s SIGUSR1
+```
+
+You can then read those metrics in the service logs:
+
+```shell-session
+$ journalctl -u nomad
+```
+
+## Lifecycle
+
+Every agent in the Nomad cluster goes through a lifecycle. Understanding
+this lifecycle is useful for building a mental model of an agent's interactions
+with a cluster and how the cluster treats a node.
+
+When a client agent is first started, it fingerprints the host machine to
+identify its attributes, capabilities, and [task drivers](/nomad/docs/drivers).
+These are reported to the servers during an initial registration. The addresses
+of known servers are provided to the agent via configuration, potentially using
+DNS for resolution. Using [Consul](https://www.consul.io/) provides a way to avoid hard
+coding addresses and resolving them on demand.
+
+While a client is running, it is performing heartbeating with servers to
+maintain liveness. If the heartbeats fail, the servers assume the client node
+has failed, and stop assigning new tasks while migrating existing tasks.
+It is impossible to distinguish between a network failure and an agent crash,
+so both cases are handled the same. Once the network recovers or a crashed agent
+restarts the node status will be updated and normal operation resumed.
+
+To prevent an accumulation of nodes in a terminal state, Nomad does periodic
+garbage collection of nodes. By default, if a node is in a failed or 'down'
+state for over 24 hours it will be garbage collected from the system.
+
+Servers are slightly more complex as they perform additional functions. They
+participate in a [gossip protocol](/nomad/docs/concepts/gossip) both to cluster
+within a region and to support multi-region configurations. When a server is
+first started, it does not know the address of other servers in the cluster.
+To discover its peers, it must _join_ the cluster. This is done with the
+[`server join` command](/nomad/docs/commands/server/join) or by providing the
+proper configuration on start. Once a node joins, this information is gossiped
+to the entire cluster, meaning all nodes will eventually be aware of each other.
+
+When a server _leaves_, it specifies its intent to do so, and the cluster marks that
+node as having _left_. If the server has _left_, replication to it will stop and it
+is removed from the consensus peer set. If the server has _failed_, replication
+will attempt to make progress to recover from a software or network failure.
+
+## Permissions
+
+Nomad servers and Nomad clients have different requirements for permissions.
+
+Nomad servers should be run with the lowest possible permissions. They need
+access to their own data directory and the ability to bind to their ports. You
+should create a `nomad` user with the minimal set of required privileges.
+
+Nomad clients should be run as `root` due to the OS isolation mechanisms that
+require root privileges. While it is possible to run Nomad as an unprivileged
+user, careful testing must be done to ensure the task drivers and features
+you use function as expected. The Nomad client's data directory should be
+owned by `root` with filesystem permissions set to `0700`.
+
+
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
+[`server force-leave` command]: /nomad/docs/commands/server/force-leave
+[consensus]: /nomad/docs/concepts/consensus
+[`drain_on_shutdown`]: /nomad/docs/configuration/client#drain_on_shutdown
+[reload its configuration]: /nomad/docs/configuration#configuration-reload
+[metrics]: /nomad/docs/operations/metrics-reference
diff --git a/content/nomad/v1.9.x/content/docs/operations/stateful-workloads.mdx b/content/nomad/v1.9.x/content/docs/operations/stateful-workloads.mdx
new file mode 100644
index 0000000000..e5c7da0899
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/operations/stateful-workloads.mdx
@@ -0,0 +1,234 @@
+---
+layout: docs
+page_title: Considerations for Stateful Workloads
+description: |-
+  Learn about persistent storage options for stateful workloads on Nomad.
+---
+
+# Considerations for Stateful Workloads
+
+By default, Nomad's allocation storage is ephemeral. Nomad can discard it during
+new deployments, when rescheduling jobs, or if it loses a client. This is
+undesirable when running persistent workloads such as databases.
+
+This document explores the options for persistent storage of workloads running
+in Nomad. The information provided is for practitioners familiar with Nomad and
+with a foundational understanding of storage basics.
+
+## Considerations
+
+Consider access patterns, performance, reliability and availability needs, and
+maintenance to choose the most appropriate storage strategy.
+
+Local storage is performant and available. If it has enough capacity it does not
+need much maintenance. But it is not redundant; if a single node, disk, or
+group of disks fails, data loss and service interruption will occur.
+
+A geographically distributed networked storage with multiple redundancies,
+including disks, controllers, and network paths, provides higher availability
+and resilience, and can tolerate multiple hardware failures before risking data
+loss. But the performance and reliability of networked storage depends
+on the network. It can have higher latency and lower throughput than local
+storage, and may require more maintenance.
+
+Consider whether Nomad is running in the public cloud or on-premises, and what
+storage options are available in that environment. From there, the most optimal
+choice will depend your organizational and application needs.
+
+### Public cloud
+
+Public cloud providers offer different storage services with various tradeoffs.
+Usually they're comprised of local disks, network attached block devices, and
+networked shared storage.
+
+### AWS
+
+| AWS service                                                                                  | Availability                                                      | Persistence                                                                      | Performance                                                                                                                                        | Suitability                                                                                                                  |
+|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Instance Storage](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html) | Locally on some instance types                                    | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                                                                    | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Elastic Block Store](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)    | Zonal block devices attached to one or more instances                         | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html), but higher latency than Instance Store                    | General purpose persistent storage                                                                                           |
+| [Elastic File System](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEFS.html)    | Regional/Multi-regional file storage that can be available to multiple instances | Persistent, with an independent lifecycle                               | [Configurable](https://docs.aws.amazon.com/efs/latest/ug/performance.html), but with less throughput and higher latency than Instance Store or EBS | File storage that needs to be available to multiple instances in multiple zones (even only as a failover)                    |
+
+### Azure
+
+| Azure service                                                                                     | Availability                                                                           | Persistence                                                                      | Performance                                                                                                | Suitability                                                                                                                  |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Ephemeral OS disks](https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks) | Locally on some instance types                                                         | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                                                            | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Managed Disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types)              | [Zonal or regional](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-redundancy) block devices attached to one or more VMs                                              | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#disk-type-comparison)            | General purpose persistent storage                                                                                           |
+| [Azure Files](https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction)    | Zonal/Regional/Multi-regional file storage that can be available to multiple VMs | Persistent, with an independent lifecycle                               | [Configurable](https://learn.microsoft.com/en-us/azure/storage/files/storage-files-planning#storage-tiers) | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                    |
+
+### GCP
+
+| GCP service                                                        | Availability                                                                                                                     | Persistence                                                                      | Performance                                                             | Suitability                                                                                                                  |
+|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| [Local SSD](https://cloud.google.com/compute/docs/disks/local-ssd) | Locally on some instance types                                                                                                   | Limited, not persistent across instance stops/terminations or hardware failures | High throughput and low latency                                         | Temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content |
+| [Persistent Disk](https://cloud.google.com/compute/docs/disks)     | [Zonal or regional](https://cloud.google.com/compute/docs/disks#repds) block devices attached to one or more instances | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/compute/docs/disks/performance) | General purpose persistent storage                                                                                           |
+| [Filestore](https://cloud.google.com/filestore)                    | Zonal/Regional file storage that can be available to multiple instances                                           | Persistent, with an independent lifecycle                               | [Configurable](https://cloud.google.com/filestore/docs/performance)     | File storage that needs to be available to multiple VMs in multiple zones (even only as a failover)                          |
+
+
+### Private cloud or on-premises
+
+When running workloads on-premises in a self-managed private cloud, SAN/NAS
+systems or Software Defined Storage like Portworx or Ceph usually provide
+non-local storage. Compute instances can access the storage using a block
+protocol such as iSCSI, FC, NVMe-oF, or a file protocol such as NFS, CIFS, or
+both. Dedicated storage teams manage these systems in most organizations.
+
+## Consuming persistent storage from Nomad
+
+Since environments differ depending on application requirements, consider
+performance, reliability, availability, and maintenance when choosing the most
+appropriate storage driver.
+
+### CSI
+
+[Container Storage
+Interface](https://github.com/container-storage-interface/spec) is a
+vendor-neutral specification that allows storage providers to develop plugins
+that orchestrators such as Nomad can use. Some CSI plugins can dynamically
+provision and manage volume lifecycles, including snapshots, deletion, and
+dynamic resizing. The exact feature set each plugin supports will depend on the
+plugin and the underlying storage platform.
+
+Find a list of plugins and their feature set in the [Kubernetes CSI Developer
+Documentation](https://kubernetes-csi.github.io/docs/drivers.html).
+
+While Nomad follows the CSI specification, some plugins may implement
+orchestrator-specific logic that makes them incompatible with Nomad. You should
+validate that your chosen plugin works with Nomad before using it. Refer to the
+plugin documentation from the storage provider for more information.
+
+There are three CSI plugin subtypes:
+
+- **Controller**: Communicates with the storage provider to manage the volume
+  lifecycle.
+- **Node**: Runs on all Nomad clients and handles all local operations (for
+  example, mounting/unmounting volumes in allocations). The node must be
+  `privileged` to perform those operations.
+- **Monolithic**: Combines both the above roles.
+
+All types can and should be run as Nomad jobs - `system` jobs for Node and
+Monolithic, `service` for Controllers. More information can be found on the CSI
+concepts [documentation page](/nomad/docs/concepts/plugins/csi).
+
+CSI plugins are useful when storage requirements are quickly and constantly
+evolving. For example, an environment that sees new workloads with persistent
+storage added or removed frequently is well suited for CSI. However, they
+present some challenges in terms of maintenance - most notably, they need to run
+continuously, be configured (including authentication and connectivity to the
+storage platform), and updated to keep track with new features and bug fixes and
+keep compatibility with the underlying storage platform. They also introduce a
+couple of moving parts, can be difficult to troubleshoot, and have a complex
+security profile (due to needing to run as `privileged` containers in order to
+be able to mount volumes).
+
+The [Stateful Workloads with CSI
+tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+and the [Nomad CSI demo
+repository](https://github.com/hashicorp/nomad/tree/main/demo/csi) offer
+guidance and examples on how to use CSI plugins with Nomad and include job files
+for running the plugins and configuration files for creating and consuming
+volumes.
+
+### Host volumes
+
+Host volumes mount paths from the host (the Nomad client) into allocations.
+Nomad is aware of host volume availability and makes use of it for job
+scheduling. However, Nomad does not know about the volume's underlying
+characteristics, such as if it is a standard folder on a local ext4 filesystem,
+backed by a distributed networked storage such as GlusterFS, or a mounted
+NFS/CIFS volume from a NAS or a public cloud service such as AWS EFS. Therefore
+you can use host volumes for both local somewhat persistent storage and for
+highly persistent networked storage.
+
+Because you need to declare host volumes in the Nomad agent's configuration
+file, you must restart the Nomad client to reconfigure them. This makes host
+volumes impractical if you frequently change your storage configuration.
+Furthermore, it might require coordination between different
+[personas](/nomad/docs/concepts/security#personas) to configure and consume
+host volumes. For example, a Nomad Administrator must modify Nomad's
+configuration file to add/update/remove host volumes to make them available for
+consumption by Nomad Operators. Or, with networked host volumes, a Storage
+Administrator will need to provision the volumes and make them available to the
+Nomad clients. A System Administrator will then mount them on the Nomad clients.
+
+Host volumes backed by local storage help persist data that is not critical, for
+example an on-disk cache that can be rebuilt if needed. When backed by networked
+storage such as NFS/CIFS-mounted volumes or distributed storage via
+GlusterFS/Ceph, host volumes provide a quick option to consume highly available
+and reliable storage.
+
+Refer to the [Stateful workloads with Nomad host
+volumes](/nomad/tutorials/stateful-workloads/stateful-workloads-host-volumes)
+tutorial to learn more about using host volumes with Nomad.
+
+#### NFS caveats
+
+A few caveats with NFS-backed host volumes include ACLs, reliability, and
+performance. NFS mount options should be the same on all mounting Nomad clients.
+
+Depending on your NFS version, the UID/GID (user/group IDs) can differ between
+the different Nomad clients, leading to issues when an allocation on another
+host tries to access the volume. The only way to ensure this isn't an issue is
+to use NFS v4 with ID mapping based on Kerberos or to have a reliable
+configuration management/image-building process that ensures UID/GIDs
+synchronize between hosts. You should use hard mounts to prevent data loss,
+optionally with `intr` to enable the option to interrupt NFS requests, which
+prevents the whole system from locking up in case of NFS server unavailability.
+
+A significant factor in the performance of NFS-backed storage is the `wsize` and
+`rsize` mount options that determine the maximum read/write size of a block.
+Smaller sizes mean bigger operations will be split into smaller chunks,
+significantly impacting performance. The underlying storage system's vendor
+provides the optimal sizes. For example, [AWS
+EFS](https://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-general.html)
+recommends a value of `1048576` bytes of data for both `wsize` and `rsize`.
+
+To learn more about NFS mount options, visit Red Hat's [NFS
+documentation](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-nfs-client-config-options).
+
+### Ephemeral disks
+
+Nomad [ephemeral disks](/nomad/docs/job-specification/ephemeral_disk), describe
+the best-effort persistence of a Nomad allocation's folder. They support data
+migrations between hosts (which require network connectivity between the Nomad
+client nodes) and are size-aware for scheduling. Since persistence is the best
+effort, however, you will lose data if the client or underlying storage fails.
+Ephemeral disks are perfect for data that you can rebuild if needed, such as an
+in-progress cache or a local copy of data.
+
+## Storage comparison
+
+With the information laid out in this document, use the following table to
+choose the storage options that best addresses your Nomad storage requirements.
+
+| Storage option  | Advantages  | Disadvantages  | Ideal for  |
+|---|---|---|---|
+| CSI volumes  | <ul><li>Wide ecosystem with many providers</li><li>Advanced features such as snapshots, cloning, and resizing</li><li>Dynamic, flexible, and self-service (anyone with the correct ACL policies can create volumes on-demand)</li></ul>    | <ul><li>Some complexity and ongoing maintenance</li><li>Plugin upgrades have to follow the underlying storage provider's API changes/upgrades</li><li>Not all CSI plugins implement all features</li><li>Not all CSI plugins respect the CSI spec and are Nomad compatible</li><li>Node plugins need to run in privileged mode to be able to mount the volumes in allocations</li></ul>  |  <ul><li>Environments where Nomad cluster operators and consumers need to easily add/change storage, and where the storage provider of choice has a CSI plugin that respects the CSI spec</li></ul> |
+| Host volumes backed by local storage  | <ul><li>Readily available</li><li>Fast due to being local</li><li>Doesn't require ongoing maintenance</li></ul>  | <ul><li>Requires coordination between multiple personas to configure and consume (operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>Not fault tolerant. In case of hardware failure on a single instance, the data will be lost</li></ul>  | <ul><li> Environments with low persistent storage requirements that could tolerate some failure but prefer not to or have high performance and low latency needs.</li></ul>   |
+| Host volumes backed by networked or clustered storage  | <ul><li>Readily available</li><li>Require no ongoing maintenance on the Nomad side (but might on the storage provider) </li></ul>  | <ul><li>Require coordination between multiple personas to configure and consume (storage admins need to provision volumes, operators running the Nomad clients need to configure them statically in the Nomad client's configuration file)</li><li>The underlying networked storage and its limitations are decoupled from the consumer, but need to be understood. For example, is concurrent access possible</li></ul>  | <ul><li>Environments with low amounts or low frequency of change of storage that have an existing storage provider that can be consumed via NFS/CIFS.</li></ul>  |
+| Ephemeral disks  | <ul><li>Fast due to being local</li><li>Basic best effort persistence, including optional migration across Nomad clients</li></ul>  | <ul><li> Not fault tolerant. In case of hardware failure on a single instance, the data will be lost </li></ul>  | <ul><li>Environments that need temporary caches, somewhere to store files undergoing processing, etc. Everything which is ephemeral and can be easily rebuilt.</li></ul>  |
+
+## Additional resources
+
+To learn more about Nomad and the topics covered in this document, visit the
+following resources:
+
+### Allocations
+- Monitoring your allocations and their storage with [Nomad's event
+  stream](/nomad/tutorials/integrate-nomad/event-stream)
+- [Best practices for cluster
+  setup](/well-architected-framework/nomad/production-reference-architecture-vm-with-consul)
+
+### CSI
+
+- [Nomad CSI plugin concepts](/nomad/docs/concepts/plugins/csi)
+- [Nomad CSI
+  tutorial](/nomad/tutorials/stateful-workloads/stateful-workloads-csi-volumes)
+- [Nomad CSI examples](https://github.com/hashicorp/nomad/tree/main/demo/csi)
+- [Ceph RBD CSI with Nomad](https://docs.ceph.com/en/latest/rbd/rbd-nomad/)
+- [Democratic CSI with
+  Nomad](https://github.com/democratic-csi/democratic-csi/blob/master/docs/nomad.md)
+- [JuiceFS CSI with Nomad](https://juicefs.com/docs/csi/csi-in-nomad/)
+- [Hetzner CSI](https://github.com/hetznercloud/csi-driver/blob/main/docs/nomad/README.md)
+- [NFS CSI Plugin](https://gitlab.com/rocketduck/csi-plugin-nfs)
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/acl-policy.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/acl-policy.mdx
new file mode 100644
index 0000000000..efbdc81437
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/acl-policy.mdx
@@ -0,0 +1,499 @@
+---
+layout: docs
+page_title: ACL Policy Specification
+description: Learn about Nomad's ACL policy specification.
+---
+
+# ACL Policy Specification
+
+The [Secure Nomad with Access Control] guide includes step-by-step instructions
+for bootstrapping Nomad's Access Control List (ACL) system, authoring policies,
+and granting policies. This document is a detailed reference of the expected
+policy structure and available options.
+
+ACL policies are written using [HashiCorp Configuration Language
+(HCL)][hcl]. The HCL interpreter can also parse JSON to facilitate
+machine-generated configuration. A detailed syntax specification for HCL can be
+found at [HCL Native Syntax Specification][hcl_syntax_spec].
+
+All content of an ACL policy is case-sensitive.
+
+An ACL policy contains one or more **rules**. Each rule block contains a
+combination of `policy` and `capabilities` fields. The specific values permitted
+are described for each rule definition below. An example structure of an ACL
+policy is as follows:
+
+```hcl
+# this is a namespace rule for the "foo" namespace
+namespace "foo" {
+  policy = "write"                # this is a policy field
+  capabilities = ["alloc-exec"]  # this is a capabilities list
+
+  # this block controls access to variables in this namespace
+  variables {
+    path "project/*" {
+      capabilities = ["read", "write"]
+    }
+  }
+}
+
+# this is a namespace rule, with a wildcard label
+namespace "*" {
+  policy = "read"
+}
+
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+
+operator {
+  policy = "read"
+}
+
+quota {
+  policy = "read"
+}
+
+# this is a host_volume rule, with a wildcard label
+host_volume "*" {
+  policy = "read"
+}
+
+plugin {
+  policy = "read"
+}
+```
+
+## Namespace Rules
+
+Namespace rules are defined with a `namespace` block. An ACL policy can include
+zero, one, or more namespace rules.
+
+Namespace rules control access to APIs in Nomad that are namespaced:
+[Jobs][api_jobs], [Allocations][api_allocations],
+[Deployments][api_deployments], [Evaluations][api_evaluations],
+[Recommendations][api_recommendations], [Scaling
+Policies][api_scaling_policies], [Services][api_services], and [CSI
+Volumes][api_volumes]. Namespace rules also filter items related to the above
+APIs from the [Event Stream][api_events] and [Search][api_search] APIs.
+
+Each namespace rule is labeled with the namespace name it applies to. If no
+namespace label is specified, the rule will apply to the "default"
+namespace. You may use wildcard globs (`"*"`) in the namespace label, to apply a
+rule to multiple namespaces.
+
+Only one namespace rule can apply. When Nomad checks an action against the ACL
+Policy, the namespace rule is selected by first checking for an _exact match_,
+before falling back to a glob-based lookup. When looking up the namespace by
+glob, Nomad chooses the rule with the greatest number of matched characters. In
+other words, Nomad chooses the rule with the _smallest character difference_,
+which is the _greatest number of matched characters_.
+
+In this example, you have a 'production-web' namespace. For the `"*-web"` rule,
+nine characters match. The character difference is four. For the `"*"`rule, no
+characters match the rule. The character difference is thirteen. Nomad chooses
+the `"*-web"` rule since it has the greatest number of matched characters.
+
+```hcl
+namespace "*-web" {
+  policy = "deny"
+}
+
+namespace "*" {
+  policy = "write"
+}
+```
+
+Each namespace rule can include a coarse-grained `policy` field, a fine-grained
+`capabilities` field, a `variables` block, or all three.
+
+The `policy` field for namespace rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`. This includes:
+
+- `deny` - When multiple policies are associated with a token, deny will take
+  precedence and prevent any capabilities.
+- `list-jobs` - Allows listing the jobs and seeing coarse grain status. This
+  implicitly grants `csi-list-volume`.
+- `parse-job` - Allows parsing a job from HCL to JSON.
+- `read-job` - Allows inspecting a job and seeing fine grain status. This
+  implicitly grants `csi-read-volume`.
+- `submit-job` - Allows jobs to be submitted, updated, or stopped.
+- `dispatch-job` - Allows jobs to be dispatched
+- `read-logs` - Allows the logs associated with a job to be viewed.
+- `read-fs` - Allows the filesystem of allocations associated to be
+  viewed. Implicitly grants `read-logs`.
+- `alloc-exec` - Allows an operator to connect and run commands in running
+  allocations.
+- `alloc-node-exec` - Allows an operator to connect and run commands in
+  allocations running without filesystem isolation, for example, raw_exec jobs.
+- `alloc-lifecycle` - Allows an operator to stop individual allocations
+  manually.
+- `csi-register-plugin` - Allows jobs to be submitted that register themselves
+  as CSI plugins.
+- `csi-write-volume` - Allows CSI volumes to be registered or deregistered. This
+  implicitly grants `csi-read-volume`.
+- `csi-read-volume` - Allows inspecting a CSI volume, seeing fine grain status,
+  and listing external volumes and snapshots. This implicitly grants
+  `csi-list-volume`.
+- `csi-list-volume` - Allows listing CSI volumes, seeing coarse grain status,
+  and listing external volumes and snapshots.
+- `csi-mount-volume` - Allows jobs to be submitted that claim a CSI volume. This
+  implicitly grants `csi-read-volume`.
+- `list-scaling-policies` - Allows listing scaling policies.
+- `read-scaling-policy` - Allows inspecting a scaling policy.
+- `read-job-scaling` - Allows inspecting the current scaling of a job.
+- `scale-job`: Allows scaling a job up or down.
+- `sentinel-override` - Allows soft mandatory policies to be overridden.
+- `submit-recommendation` - Allows submitting vertical job scaling recommendations.
+
+The coarse-grained policy permissions are shorthand for the following fine-
+grained namespace capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                                                                                                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `deny`  | deny                                                                                                                                                                                                                                                                                                      |
+| `read`  | list-jobs<br />parse-job<br />read-job<br />csi-list-volume<br />csi-read-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling                                                                                                                                                |
+| `write` | list-jobs<br />parse-job<br />read-job<br />submit-job<br />dispatch-job<br />read-logs<br />read-fs<br />alloc-exec<br />alloc-lifecycle<br />csi-write-volume<br />csi-mount-volume<br />list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job<br />submit-recommendation |
+| `scale` | list-scaling-policies<br />read-scaling-policy<br />read-job-scaling<br />scale-job                                                                                                                                                                                                                       |
+
+<!-- markdownlint-enable -->
+
+If you provide both a `policy` and `capabilities` list, the capabilities are
+merged. For example, the policy below adds the `submit-job` capability to the `read`
+policy disposition, which provides the `list-job` and `read-job` capabilities:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  policy       = "read"
+  capabilities = ["submit-job"]
+}
+```
+
+A similar policy could also be expressed as:
+
+```hcl
+# Allow reading jobs and submitting jobs, without allowing access
+# to view log output or inspect the filesystem
+namespace "default" {
+  capabilities = ["submit-job","list-jobs","read-job"]
+}
+```
+
+### Variables
+
+The `variables` block in the `namespace` rule controls access to
+[Variables][]. The variables block is optional, but you can specify only one
+variables block per namespace rule.
+
+A `variables` block includes one or more `path` blocks. Each `path` block is
+labeled with the path it applies to. You may use wildcard globs (`"*"`) in the
+path label, to apply the block to multiple paths in the namespace. Note that
+variable paths never start with a leading `/`, so Nomad will return an error if
+you submit a policy that has such a path.
+
+Each path has a list of `capabilities`. The available capabilities for Variables
+are as follows:
+
+| Capability | Notes                                                                                                                 |
+|------------|-----------------------------------------------------------------------------------------------------------------------|
+| write      | Create or update Variables at this path. Includes the "list" capability but not the "read" or "destroy" capabilities. |
+| read       | Read the decrypted contents of Variables at this path. Also includes the "list" capability                            |
+| list       | List the metadata but not contents of Variables at this path.                                                         |
+| destroy    | Delete Variables at this path.                                                                                        |
+| deny       | No permissions at this path. Deny takes precedence over other capabilities.                                           |
+
+For example, the policy below allows full access to variables at all paths in
+the "dev" namespace that are prefixed with "project/", but only read access to
+paths prefixed with "system/". Note that the glob can match an empty string but
+all other characters are strictly matched. This policy grants read access to
+paths prefixed with "system/" but not a path named "system" (without a trailing
+slash). This policy does not grant any other coarse-grained policy or
+fine-grained capabilities.
+
+```hcl
+namespace "dev" {
+
+  variables {
+
+    # full access to secrets in all "project" paths
+    path "project/*" {
+      capabilities = ["write", "read", "destroy", "list"]
+    }
+
+    # read/list access within a "system/" path belonging to administrators
+    path "system/*" {
+      capabilities = ["read"]
+    }
+  }
+}
+```
+
+## Node rules
+
+The `node` rule controls access to the [Node API][api_node] such as listing
+nodes or triggering a node drain. The node rule is optional, but you can specify
+only one node rule per ACL Policy.
+
+```hcl
+node {
+  policy = "read"
+}
+```
+
+The `policy` field for the node rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Node Pools rules
+
+Node pool rules are defined with a `node_pool` block. An ACL policy can
+include zero, one, or more node pool rules.
+
+Node pool rule controls access to the [Node Pools API][api_node_pool] such as
+create, update, and list node pools.
+
+Each node pool rule is labeled with the node pool name it applies to. You may
+use wildcard globs (`"*"`) in the label to apply a rule to multiple node pools.
+
+Similarly to [namespace rules](#namespace-rules) only one `node_pool` rule can
+be applied. First an _exact match_ is tried before falling back to a glob-based
+lookup, where the rule with the greatest number of matched characters is
+chosen.
+
+Each node pool rule can include a coarse-grained `policy` field and a
+fine-grained `capabilities` field.
+
+The `policy` field for node pool rules can have one of the following values.
+
+- `read` allows node pools to be listed and read but not modified.
+- `write` allows node pools to be read, create, updated, and deleted.
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+
+In addition to the coarse-grained `policy`, you can provide a fine-grained list
+of `capabilities`.
+
+- `deny` forbids node pools to be read or modified. Deny takes precedence when
+  multiple policies are associated with a token.
+- `delete` allows node pools to be deleted.
+- `read` allows node pools to be listed and read.
+- `write` allows node pools to be created and updated.
+
+The coarse-grained policy permissions are shorthand for the following
+fine-grained capabilities.
+
+| Policy  | Capabilities              |
+| ------- | ------------------------- |
+| `deny`  | `deny`                    |
+| `read`  | `read`                    |
+| `write` | `delete`, `read`, `write` |
+
+If you provide both a `policy` and `capabilities` list the capabilities are
+merged. For example, the policy below adds the `write` capability to the `read`
+policy, thus allowing `read` and `write` permission but no `delete`.
+
+```hcl
+node_pool "dev-*" {
+  policy       = "read"
+  capabilities = ["write"]
+}
+```
+
+## Agent rules
+
+The `agent` rule controls access to the [Agent API][api_agent] such as join and
+leave. The agent rule is optional, but you can specify only one agent rule per
+ACL Policy.
+
+```hcl
+agent {
+  policy = "read"
+}
+```
+
+The `policy` field for the agent rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Operator rules
+
+The `operator` rule controls access to the [Operator API][api_operator] such
+raft or scheduler configuration. The operator rule is optional, but you can
+specify only one operator rule per ACL Policy.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+The `policy` field for the operator rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In the example above, the token could be used to query the operator endpoints
+for diagnostic purposes but not make any changes.
+
+## Quota rules
+
+The `quota` rule controls access to the [Quota API][api_quota] such as quota
+creation and deletion. The quota rule is optional, but you can specify only one
+quota rule per ACL Policy.
+
+```hcl
+quota {
+  policy = "read"
+}
+```
+
+The `policy` field for the quota rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Host Volume rules
+
+The `host_volume` rule controls access to mounting and accessing [host
+volumes][host_volumes]. An ACL Policy can include zero, one, or more host volume
+rules.
+
+```hcl
+host_volume "*" {
+  policy = "write"
+}
+
+host_volume "prod-*" {
+  policy = "deny"
+}
+
+host_volume "prod-ca-certificates" {
+  policy = "read"
+}
+```
+
+Host volume rules are labeled with the volume names that they apply to. As with
+namespaces, you may use wildcards to reuse the same configuration across a set
+of volumes.
+
+The `policy` field for host volume rules can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+In addition to the coarse grained policy, host volume rules can include a list
+of fine-grained `capabilities`. These include:
+
+- `deny` - Do not allow a user to mount a volume in any way.
+- `mount-readonly` - Only allow the user to mount the volume as `readonly`
+- `mount-readwrite` - Allow the user to mount the volume as `readonly` or
+  `readwrite` if the `host_volume` configuration allows it.
+
+The coarse-grained policy permissions are shorthand for the fine grained
+capabilities:
+
+<!-- markdownlint-disable -->
+
+| Policy  | Capabilities                        |
+|---------|-------------------------------------|
+| `deny`  | deny                                |
+| `read`  | mount-readonly                      |
+| `write` | mount-readonly<br />mount-readwrite |
+
+<!-- markdownlint-enable -->
+
+When both the policy short hand and a capabilities list are provided, the
+capabilities are merged.
+
+~> **Note:** Host Volume policies are applied when attempting to _use_ a volume.
+Regardless of this configuration, users with access to the Node API will be able
+to list available volumes using the `nomad node status` command or API call. .
+
+## Plugin rules
+
+The `plugin` rule controls access to [CSI plugins][api_plugins], such as listing
+plugins or getting plugin status. The plugin rule is optional, but you can
+specify only one plugin rule per ACL policy.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+The `policy` field for the plugin rule can have one of the following values:
+- `read`: allow the resource to be read but not modified
+- `list`: allow the resource to be listed, but not inspected in detail
+- `write`: allow the resource to be read and modified
+- `deny`: do not allow the resource to be read or modified. Deny takes
+  precedence when multiple policies are associated with a token.
+
+## Configuring ACLs for the web UI
+
+The Nomad web UI uses the API endpoints `/v1/agent` and `/v1/node` for nearly
+every page. ACL policies for users who will use the Nomad UI should include the
+following rules.
+
+```hcl
+node {
+  policy = "read"
+}
+
+agent {
+  policy = "read"
+}
+```
+
+Additionally, ACL policies for users who can read jobs that mount CSI volumes
+should include the following rules.
+
+```hcl
+plugin {
+  policy = "read"
+}
+```
+
+[Secure Nomad with Access Control]: /nomad/tutorials/access-control
+[hcl]: https://github.com/hashicorp/hcl
+[hcl_syntax_spec]: https://github.com/hashicorp/hcl/blob/main/hclsyntax/spec.md
+[api_jobs]: /nomad/api-docs/jobs
+[api_allocations]: /nomad/api-docs/allocations
+[api_deployments]: /nomad/api-docs/deployments
+[api_evaluations]: /nomad/api-docs/evaluations
+[api_recommendations]: /nomad/api-docs/recommendations
+[api_scaling_policies]: /nomad/api-docs/scaling-policies
+[api_services]: /nomad/api-docs/services
+[api_volumes]: /nomad/api-docs/volumes
+[api_events]: /nomad/api-docs/events
+[api_search]: /nomad/api-docs/search
+[api_agent]: /nomad/api-docs/agent/
+[api_node]: /nomad/api-docs/nodes/
+[api_node_pool]: /nomad/api-docs/node-pools/
+[api_operator]: /nomad/api-docs/operator/
+[api_quota]: /nomad/api-docs/quotas/
+[host_volumes]: /nomad/docs/configuration/client#host_volume-block
+[api_plugins]: /nomad/api-docs/plugins/
+[Variables]: /nomad/docs/concepts/variables
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/index.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/index.mdx
new file mode 100644
index 0000000000..60664eda9b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Other Specifications
+description: Learn about other specifications used in Nomad.
+---
+
+# Other Specifications
+
+In addition to
+[Jobs](/nomad/docs/job-specification),
+there are other objects that can be specified in Nomad:
+
+- [ACL Policy](/nomad/docs/other-specifications/acl-policy)
+- [Namespace](/nomad/docs/other-specifications/namespace)
+- [Node Pool](/nomad/docs/other-specifications/node-pool)
+- [Quota](/nomad/docs/other-specifications/quota)
+- [Variable](/nomad/docs/other-specifications/variables)
+- [Volume](/nomad/docs/other-specifications/volume)
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/namespace.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/namespace.mdx
new file mode 100644
index 0000000000..20e711ea6c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/namespace.mdx
@@ -0,0 +1,164 @@
+---
+layout: docs
+page_title: Namespace Specification
+description: Learn about Nomad's Namespace specification.
+---
+
+# Namespace Specification
+
+<Tip>
+  Visit the <a href="https://developer.hashicorp.com/nomad/tutorials/manage-clusters/namespaces">
+    Nomad Namespaces tutorial
+  </a> for more information.
+</Tip>
+
+
+Nomad Namespaces may be specified as HCL files and submitted by the [`nomad
+namespace apply`][cli_ns_apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Namespace specifications do *not*
+support [HCL2][hcl2] features like functions.
+
+In [federated][] clusters, all updates to namespaces are forwarded to the
+[`authoritative_region`][] and replicated to non-authoritative regions. This
+requires that ACLs have been bootstrapped in the authoritative region.
+
+Example namespace specification:
+
+```hcl
+name        = "prod-eng"
+description = "Namespace for production workloads."
+
+# Quotas are a Nomad Enterprise feature.
+quota = "eng"
+
+meta {
+  owner = "eng"
+}
+
+capabilities {
+  enabled_task_drivers   = ["java", "docker"]
+  disabled_task_drivers  = ["raw_exec"]
+  enabled_network_modes  = ["bridge", "cni/custom"]
+  disabled_network_modes = ["host"]
+}
+
+# Node Pool configuration is a Nomad Enterprise feature.
+node_pool_config {
+  default = "prod"
+  allowed = ["all", "default"]
+}
+
+# Vault configuration is a Nomad Enterprise feature.
+vault {
+  default = "default"
+  allowed = ["default", "infra"]
+}
+
+# Consul configuration is a Nomad Enterprise feature.
+consul {
+  default = "default"
+  allowed = ["all", "default"]
+}
+```
+
+## Namespace Specification Parameters
+
+- `name` `(string: <required>)` - Specifies the namespace to create or update.
+
+- `description` `(string: "")` - Specifies an optional human-readable
+  description of the namespace.
+
+- `quota` `(string: "")` <EnterpriseAlert inline /> - Specifies a quota to
+  attach to the namespace.
+
+- `meta` `(object: null)` - Optional object with string keys and values of
+  metadata to attach to the namespace. Namespace metadata is not used by Nomad
+  and is intended for use by operators and third party tools.
+
+- `capabilities` <code>([Capabilities](#capabilities-parameters): &lt;optional&gt;)</code> -
+  Specifies capabilities allowed in the namespace. These values are checked at
+  job submission.
+
+- `node_pool_config` <code>([NodePoolConfiguration](#node_pool_config-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies node pool configurations. These values are checked at job
+  submission.
+
+- `vault` <code>([Vault](#vault-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Vault clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+- `consul` <code>([Consul](#consul-parameters): &lt;optional&gt;)</code> <EnterpriseAlert inline /> -
+  Specifies which Consul clusters are allowed to be used from this
+  namespace. These values are checked at job submission.
+
+### `capabilities` Parameters
+
+- `enabled_task_drivers` `(array<string>: [])` - List of task drivers allowed
+  in the namespace. If empty all task drivers are allowed.
+
+- `disabled_task_drivers` `(array<string>: [])` - List of task drivers disabled
+  in the namespace.
+
+- `enabled_network_modes` `(array<string>: [])` - List of network modes allowed
+  in the namespace. If empty all network modes are allowed.
+
+- `disabled_network_modes` `(array<string>: [])` - List of network modes disabled
+  in the namespace.
+
+### `node_pool_config` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the node pool to use for jobs in
+  this namespace that don't define a node pool in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the node pools that are allowed
+  to be used by jobs in this namespace. By default, all node pools are allowed.
+  If an empty list is provided only the namespace's default node pool is
+  allowed. This field supports wildcard globbing through the use of `*` for
+  multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the node pools that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any node pool is allowed to be used, except for those that match any of these
+  patterns. This field cannot be used with `allowed`.
+
+### `vault` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Vault cluster to use for jobs
+  in this namespace that don't define a Vault cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Vault clusters that are
+  allowed to be used by jobs in this namespace. By default, all Vault clusters
+  are allowed.  If an empty list is provided only the namespace's default Vault
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Vault clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Vault cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+### `consul` Parameters <EnterpriseAlert inline />
+
+- `default` `(string: "default")` - Specifies the Consul cluster to use for jobs
+  in this namespace that don't define a Consul cluster in their specification.
+
+- `allowed` `(array<string>: nil)` - Specifies the Consul clusters that are
+  allowed to be used by jobs in this namespace. By default, all Consul clusters
+  are allowed.  If an empty list is provided only the namespace's default Consul
+  cluster is allowed. This field supports wildcard globbing through the use of
+  `*` for multi-character matching. This field cannot be used with `denied`.
+
+- `denied` `(array<string>: nil)` - Specifies the Consul clusters that are not
+  allowed to be used by jobs in this namespace. This field supports wildcard
+  globbing through the use of `*` for multi-character matching. If specified,
+  any Consul cluster is allowed to be used, except for those that match any of
+  these patterns. This field cannot be used with `allowed`.
+
+[cli_ns_apply]: /nomad/docs/commands/namespace/apply
+[hcl2]: /nomad/docs/job-specification/hcl2
+[jobspecs]: /nomad/docs/job-specification
+[federated]: /nomad/tutorials/manage-clusters/federation
+[`authoritative_region`]: /nomad/docs/configuration/server#authoritative_region
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/node-pool.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/node-pool.mdx
new file mode 100644
index 0000000000..f3ed362191
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/node-pool.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Nomad Node Pool Specification
+description: Learn about Nomad's Node Pool specification.
+---
+
+# Nomad Node Pool Specification
+
+Nomad node pools may be specified as HCL files and submitted by the [`nomad node
+pool apply`][pool-apply] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad node pool specifications do *not*
+support HCL2 features like functions.
+
+Example node pool specification generated by [`nomad node pool
+init`][pool-init]:
+
+```hcl
+node_pool "example" {
+
+  description = "Example node pool"
+
+  # meta is optional metadata on the node pool, defined as key-value pairs.
+  # The scheduler does not use node pool metadata as part of scheduling.
+  meta {
+    environment = "prod"
+    owner       = "sre"
+  }
+
+  # The scheduler configuration options specific to this node pool. This block
+  # supports a subset of the fields supported in the global scheduler
+  # configuration as described at:
+  # https://developer.hashicorp.com/nomad/docs/commands/operator/scheduler/set-config
+  #
+  # * scheduler_algorithm is the scheduling algorithm to use for the pool.
+  #   If not defined, the global cluster scheduling algorithm is used.
+  #
+  # Available only in Nomad Enterprise.
+
+  # scheduler_config {
+  #   scheduler_algorithm = "spread"
+  # }
+}
+```
+
+Example usage if the above is in a file named `pool.nomad.hcl`:
+
+```shell-session
+$ nomad node pool apply ./pool.nomad.hcl
+Successfully applied node pool "example"!
+```
+
+## Node Pool Specification Parameters
+
+- `description` `(string: <optional>)` - Sets a human readable description for
+  the node pool.
+
+- `meta` `(map[string]string: <optional>)` - Sets optional metadata on the node
+  pool, defined as key-value pairs. The scheduler does not use node pool
+  metadata as part of scheduling.
+
+- `scheduler_config` <code>([SchedulerConfig][sched-config]: nil)</code> <EnterpriseAlert inline /> -
+  Sets scheduler configuration options specific to the node pool. If not
+  defined, the global scheduler configurations are used.
+
+### `scheduler_config` Parameters <EnterpriseAlert inline />
+
+- `scheduler_algorithm` `(string: <optional>)` - The [scheduler algorithm][]
+  used for this node pool. Must be one of `binpack` or `spread`.
+
+- `memory_oversubscription_enabled` `(bool: <optional>)` - The [memory
+  oversubscription][] setting to use for this node pool.
+
+[pool-apply]: /nomad/docs/commands/node-pool/apply
+[jobspecs]: /nomad/docs/job-specification
+[pool-init]: /nomad/docs/commands/node-pool/init
+[sched-config]: #scheduler_config-parameters
+[scheduler algorithm]: /nomad/api-docs/operator/scheduler#scheduleralgorithm-1
+[memory oversubscription]: /nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/quota.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/quota.mdx
new file mode 100644
index 0000000000..3245fb58e5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/quota.mdx
@@ -0,0 +1,94 @@
+---
+layout: docs
+page_title: Resource Quota Specification
+description: Learn about Nomad's Resource Quota specification.
+---
+
+# Resource Quota Specification
+
+<EnterpriseAlert>
+Resource Quotas are only available with Nomad Enterprise.
+</EnterpriseAlert>
+
+[Resource Quotas][] enable you to limit resource consumption across teams or
+projects to reduce waste and align budgets.
+
+You can manage quotas using the Nomad CLI via the [`quota`][] subcommands,
+or with Nomad's [Quota HTTP API][] directly.
+
+You may also follow a [Quotas tutorial][] for more example usage.
+
+## Example quota specification
+
+The CLI command `nomad quota init` generates an example `spec.hcl` file.
+
+```hcl
+name        = "default-quota"
+description = "Limit the shared default namespace"
+
+# Create a limit for the global region. Additional limits may
+# be specified in-order to limit other regions.
+limit {
+  region = "global"
+  region_limit {
+    cores      = 0
+    cpu        = 2500
+    memory     = 1000
+    memory_max = 1000
+    device "nvidia/gpu/1080ti" {
+      count = 1
+    }
+  }
+  variables_limit = 1000
+}
+```
+
+## Quota specification parameters
+
+- `name` `(string)` - The name of the Quota. Nomad uses `name` to connect the
+quota a [`Namespace`][].
+- `description` `(string: <optional>)` - A human-readable description.
+- `limit` <code>([QuotaLimit](#limit-parameters))</code> - The resource limit
+in a Nomad region.
+
+### `limit` parameters
+
+- `region` `(string)` - The Nomad `region` that the limit applies to.
+- `region_limit` <code>([RegionLimit](#region_limit-parameters))</code> -
+Resources to limit.
+- `variables_limit` `(int: 0)` - Maximum total size of all Nomad
+[`variables`][] in MiB. The default `0` means unlimited, and `-1` means
+variables are fully disabled.
+
+### `region_limit` parameters
+
+Region limits define the limits on cumulative task [`resources`][] blocks for
+allocations in the namespace and region the quota is applied to.
+
+- `cores` `(int: <optional>)` - The limit on total number of CPU cores from all
+`resources.cores` in the namespace. The [CPU concepts][] documentation
+has more details on CPU resources.
+- `cpu` `(int: <optional>)` - The limit on total amount of CPU from all
+`resources.cpu` in the namespace.
+- `memory` `(int: <optional>)` - The limit on total mount of memory in MB from
+all `resources.memory` in the namespace.
+- `memory_max` `(int: <optional>)` - The limit on total mount of hard memory
+limits in MB from all `resources.memory_max` in the namespace.
+- `device` <code>([Device](#device-parameters): nil)</code>
+
+### `device` parameters
+
+The `device` label specifies which device(s) the quota applies to,
+equivalent to the [`device`][] block in a job specification.
+
+- `count` `(int)` - How many of this device may be used.
+
+[Resource Quotas]: /nomad/docs/enterprise#resource-quotas
+[`quota`]: /nomad/docs/commands/quota
+[Quota HTTP API]: /nomad/api-docs/quotas
+[Quotas tutorial]: /nomad/tutorials/governance-and-policy/quotas
+[`Namespace`]: /nomad/docs/other-specifications/namespace
+[`variables`]: /nomad/docs/concepts/variables
+[`resources`]: /nomad/docs/job-specification/resources
+[CPU concepts]: /nomad/docs/concepts/cpu
+[`device`]: /nomad/docs/job-specification/device#device-parameters
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/variables.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/variables.mdx
new file mode 100644
index 0000000000..f658602bd0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/variables.mdx
@@ -0,0 +1,69 @@
+---
+layout: docs
+page_title: Nomad Variable Specification
+description: Learn about Nomad's Variable specification.
+---
+
+# Nomad Variable Specification
+
+[Nomad Variables][nv] may be specified as HCL files and submitted by the
+[`nomad var put`][var-put] CLI command.
+
+Unlike [Job specifications][jobspecs], Nomad Variables specifications do *not*
+support HCL2 features like functions.
+
+Example variable specification generated by [`nomad var init`][var-init]:
+
+```hcl
+# A variable path can be specified in the specification file
+# and will be used when writing the variable without specifying a
+# path in the command or when writing JSON directly to the `/var/`
+# HTTP API endpoint
+# path = "path/to/variable"
+
+# The Namespace to write the variable can be included in the specification. This
+# value can be overridden by specifying the "-namespace" flag on the "put"
+# command.
+# namespace = "default"
+
+# The items map is the only strictly required part of a variable
+# specification, since path and namespace can be set via other means.
+# It contains the sensitive material to encrypt and store as a Nomad
+# variable. The entire items map is encrypted and decrypted as a
+# single unit.
+
+# REMINDER: While keys in the items map can contain dots, using them
+# in templates is easier when they do not. As a best practice, avoid
+# dotted keys when possible.
+items {
+  key1 = "value 1"
+  key2 = "value 2"
+}
+```
+
+Example usage if the above is in a file named `spec.nv.hcl`:
+
+```shell-session
+$ nomad var put -in hcl some/path @spec.nv.hcl
+```
+
+## Variable Specification Parameters
+
+- `path` `(string: <optional>)` - The path to the variable being defined. If
+  empty it must be specified on the command line.
+
+- `namespace` `(string: <optional>)` - The namespace of the variable. May be
+  overridden by the `-namespace` command line flag or `NOMAD_NAMESPACE`
+  environment variable.
+
+- `items` `(object: <required>)` - Object of keys and values to set. Must be
+  strings.
+
+See [Variable Restrictions][var-restrict] for details on `path` and `items`
+name restrictions.
+
+[nv]: /nomad/docs/concepts/variables
+[var-init]: /nomad/docs/commands/var/init
+[var-put]: /nomad/docs/commands/var/put
+[jobspecs]: /nomad/docs/job-specification
+[var-restrict]: /nomad/docs/commands/var/put#restrictions
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/volume/capability.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/volume/capability.mdx
new file mode 100644
index 0000000000..c03e20142b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/volume/capability.mdx
@@ -0,0 +1,73 @@
+---
+layout: docs
+page_title: capability Block - Volume Specification
+description: The "capability" block allows for validating the capability of a volume.
+---
+
+# `capability` Block
+
+<Placement
+  groups={[
+    ['volume', 'capability'],
+  ]}
+/>
+
+The `capability` block allows validating that a volume meets the requested
+capabilities.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+```
+
+You must provide at least one `capability` block, and you must provide a block
+for each capability you intend to use in a job's [`volume`] block.
+
+## `capability` Parameters
+
+- `access_mode` `(string: <required>)` - Defines whether a volume should be
+available concurrently. Can be one of `"single-node-reader-only"`,
+`"single-node-writer"`, `"multi-node-reader-only"`,
+`"multi-node-single-writer"`, or `"multi-node-multi-writer"`. Most CSI plugins
+support only single-node modes. Consult the documentation of the storage
+provider and CSI plugin.
+
+- `attachment_mode` `(string: <required>)` - The storage API that will be used
+by the volume. Most storage providers will support `"file-system"`, to mount
+volumes using the CSI filesystem API. Some storage providers will support
+`"block-device"`, which will mount the volume with the CSI block device API
+within the container.
+
+## `capability` Examples
+
+The following examples only show the `capability` blocks. Remember that the
+`capability` block is only valid in the placement shown above.
+
+### Multiple capabilities
+
+This examples shows a volume that must satisfy multiple capability
+requirements.
+
+```hcl
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+```
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/volume/index.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/volume/index.mdx
new file mode 100644
index 0000000000..9ba9fc3cc1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/volume/index.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Volume Specification
+description: Learn about the Volume specification used to create and register volumes to Nomad.
+---
+
+# Volume Specification
+
+The Nomad volume specification defines the schema for creating and registering
+volumes using the [`volume create`] and [`volume register`] commands and the
+[`PUT /v1/volume/csi/:volume_id/create`][api_volume_create] and [`PUT
+/v1/volume/csi/:volume_id`][api_volume_register] API endpoints.
+
+Some attributes are only be supported by specific operation, while others may
+have a different meaning for each action, so read the documentation for each
+attribute carefully. The section [Differences Between Create and
+Register](#differences-between-create-and-register) provides a summary of the
+differences.
+
+The file may be provided as either HCL or JSON to the commands and as JSON to
+the API. An example HCL configuration for a `volume create` command:
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+snapshot_id  = "snap-12345" # or clone_id, see below
+capacity_max = "200G"
+capacity_min = "100G"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+```
+
+## Volume Specification Parameters
+
+- `id` `(string: <required>)` - The unique ID of the volume. This is how the
+  [`volume.source`][csi_volume_source] field in a job specification will refer
+  to the volume.
+
+- `namespace` `(string: <optional>)` - The namespace of the volume. This field
+  overrides the namespace provided by the `-namespace` flag or `NOMAD_NAMESPACE`
+  environment variable. Defaults to `"default"` if unset.
+
+- `name` `(string: <required>)` - The display name of the volume. On **volume
+  creation**, this field may be used by the external storage provider to tag
+  the volume.
+
+- `type` `(string: <required>)` - The type of volume. Currently only `"csi"`
+  is supported.
+
+- `external_id` `(string: <required>)` - The ID of the physical volume from
+  the storage provider. For example, the volume ID of an AWS EBS volume or
+  Digital Ocean volume. Only allowed on **volume registration**.
+
+- `plugin_id` `(string: <required>)` - The ID of the [CSI plugin][csi_plugin]
+  that manages this volume.
+
+- `snapshot_id` `(string: <optional>)` - If the storage provider supports
+  snapshots, the external ID of the snapshot to restore when creating this
+  volume. If omitted, the volume will be created from scratch. The
+  `snapshot_id` cannot be set if the `clone_id` field is set. Only allowed on
+  **volume creation**.
+
+- `clone_id` `(string: <optional>)` - If the storage provider supports cloning,
+  the external ID of the volume to clone when creating this volume. If omitted,
+  the volume will be created from scratch. The `clone_id` cannot be set if the
+  `snapshot_id` field is set. Only allowed on **volume creation**.
+
+- `capacity_min` `(string: <optional>)` - Option for requesting a minimum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers. Increasing this value and re-issuing
+  `volume create` or `volume register` may expand the volume, if the CSI plugin
+  supports it.
+
+- `capacity_max` `(string: <optional>)` - Option for requesting a maximum
+  capacity, in bytes. The capacity of a volume may be the physical size of a
+  disk, or a quota, depending on the storage provider. The specific size of the
+  resulting volume will be somewhere between `capacity_min` and `capacity_max`;
+  the exact behavior is up to the storage provider. If you want to specify an
+  exact size, you should set `capacity_min` and `capacity_max` to the same
+  value. Accepts human-friendly suffixes such as `"100GiB"`. This field may not
+  be supported by all storage providers.
+
+- `capability` <code>([Capability][capability]: &lt;required&gt;)</code> -
+  Option for validating the capability of a volume.
+
+- `mount_options` <code>([MountOptions][mount_options]: &lt;required&gt;)</code> -
+  Options for mounting `file-system` volumes that don't already have a
+  pre-formatted file system.
+
+- `topology_request` <code>([TopologyRequest][topology_request]: nil)</code> -
+  Specify locations (region, zone, rack, etc.) where the provisioned volume
+  must be accessible from in the case of **volume creation** or the locations
+  where the existing volume is accessible from in the case of **volume
+  registration**.
+
+- `secrets` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings used as credentials for publishing and unpublishing volumes.
+
+- `parameters` <code>(map<string|string>:nil)</code> - An optional key-value
+  map of strings passed directly to the CSI plugin to configure the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information.
+
+- `context` <code>(map<string|string>:nil)</code> - An optional key-value map
+  of strings passed directly to the CSI plugin to validate the volume. The
+  details of these parameters are specific to each storage provider, so consult
+  the specific plugin documentation for more information. Only allowed on
+  **volume registration**. Note that, like the rest of the volume specification, 
+  this block is declarative, and an update replaces it in its entirety, therefore 
+  all parameters need to be specified.
+
+## Differences Between Create and Register
+
+Several fields are set automatically by the plugin when `volume create` or
+`volume register` commands are successful and you should not set their values
+if they are not supported by the operation.
+
+You should not set the [`snapshot_id`](#snapshot_id), or [`clone_id`](#clone_id)
+fields on **volume registration**.
+
+And you should not set the [`external_id`](#external_id) or
+[`context`](#context) fields on **volume creation**.
+
+## Updating a Volume Definition
+
+The `volume register` command allows updating a volume definition. But not all
+fields can be updated after the volume is registered:
+
+* The `capacity_min` and `capacity_max` fields can be updated, and may increase
+  the volume size if the CSI plugin supports it. Expansion may or may not be
+  possible while the volume is in use, again depending on the plugin.
+  Reducing volume capacity is not allowed per the CSI spec.
+* The `capability` blocks can be added or removed, but only if the capability is
+  not currently in use by a mounted volume.
+* The `mount_options` block can be updated if the volume is not in use.
+* The `secrets` block can be updated.
+* The `context` block can be updated. The values for this field are typically
+  provided by the CSI plugin, and should not be updated unless recommended by
+  the CSI plugin's documentation.
+
+## Volume Expansion
+
+CSI Volumes may be expanded (increased in size) if the CSI controller plugin
+(and node plugin, if required) has the `EXPAND_VOLUME` capability.
+
+To trigger a volume expansion, increase [`capacity_min`](#capacity_min)
+above the current real capacity of the volume (as seen with the
+[`volume status`][] command), and re-issue either [`volume create`][]
+or [`volume register`][].
+
+Nomad will reconcile the requested capacity by issuing expand volume requests
+to the controller plugin, and if required by the controller, also to the
+node plugins for each allocation that has a claim on the volume.
+
+## Examples
+
+### Volume registration
+
+This is an example file used for the [`volume register`] command.
+
+```hcl
+id              = "ebs_prod_db1"
+name            = "database"
+type            = "csi"
+external_id     = "vol-23452345"
+plugin_id       = "ebs-prod"
+
+capability {
+  access_mode     = "single-node-reader-only"
+  attachment_mode = "file-system"
+}
+
+capability {
+  access_mode     = "single-node-writer"
+  attachment_mode = "file-system"
+}
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+
+topology_request {
+  required {
+    topology { segments { "rack" = "R2" } }
+    topology { segments { "rack" = "R1", "zone" = "us-east-1a"} }
+  }
+}
+
+secrets {
+  example_secret = "xyzzy"
+}
+
+parameters {
+  skuname = "Premium_LRS"
+}
+
+context {
+  endpoint = "http://192.168.1.101:9425"
+}
+```
+
+
+### Example Volume Expansion
+
+Either [`volume create`][] or [`volume register`][] commands can trigger
+an expand to occur, after the volume has already been created or registered.
+
+Example using `volume create`, with a `volume.hcl` file:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+
+capacity_min = "50gib"
+capacity_max = "50gib"
+
+# ... etc ...
+```
+
+Create the volume:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+See its current capacity with [`volume status`][]:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 50 GiB
+```
+
+Update `volume.hcl`:
+
+```hcl
+id        = "ebs_prod_db1"
+name      = "database"
+type      = "csi"
+plugin_id = "ebs-prod"
+# all of the above must remain the same
+
+capacity_min = "100gib" # double
+capacity_max = "100gib" # increased to match
+
+# ... etc ...
+```
+
+Run `volume create` again:
+
+```shell-session
+$ nomad volume create volume.hcl
+Created external volume vol-asdf1234 with ID ebs_prod_db1
+```
+
+Check the volume capacity again:
+
+```shell-session
+$ nomad volume status ebs_prod_db1 | grep Capacity
+Capacity             = 100 GiB
+```
+
+If you encounter errors that are not clear from the command output,
+the CSI plugin allocation logs and/or Nomad leader server logs may be
+helpful.
+
+[api_volume_create]: /nomad/api-docs/volumes#create-volume
+[api_volume_register]: /nomad/api-docs/volumes#register-volume
+[capability]: /nomad/docs/other-specifications/volume/capability
+[csi_plugin]: /nomad/docs/job-specification/csi_plugin
+[csi_volume_source]: /nomad/docs/job-specification/volume#source
+[mount_options]: /nomad/docs/other-specifications/volume/mount_options
+[topology_request]: /nomad/docs/other-specifications/volume/topology_request
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume status`]: /nomad/docs/commands/volume/status
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/volume/mount_options.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/volume/mount_options.mdx
new file mode 100644
index 0000000000..6bee03d013
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/volume/mount_options.mdx
@@ -0,0 +1,44 @@
+---
+layout: docs
+page_title: mount_options Block - Volume Specification
+description: The "mount_options" block allows for configuring how a volume is mounted.
+---
+
+# `mount_options` Block
+
+<Placement
+  groups={[
+    ['volume', 'mount_options'],
+  ]}
+/>
+
+Options for mounting `file-system` volumes that don't already have a
+pre-formatted file system.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+mount_options {
+  fs_type     = "ext4"
+  mount_flags = ["noatime"]
+}
+```
+
+This block will be validated during volume creation against the `capability`
+field. The `mount_options` provided in a job specification's [`volume`] block
+will override this block. Consult the documentation for your storage provider
+and CSI plugin as to whether these options are required or necessary.
+
+## `mount_options` Parameters
+
+- `fs_type` `(string <optional>)` - File system type (ex. `"ext4"`)
+- `mount_flags` `([]string: <optional>)` - The flags passed to `mount` (ex.
+  `["ro", "noatime"]`)
+
+[`volume`]: /nomad/docs/job-specification/volume
diff --git a/content/nomad/v1.9.x/content/docs/other-specifications/volume/topology_request.mdx b/content/nomad/v1.9.x/content/docs/other-specifications/volume/topology_request.mdx
new file mode 100644
index 0000000000..0c1c6a8ae9
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/other-specifications/volume/topology_request.mdx
@@ -0,0 +1,82 @@
+---
+layout: docs
+page_title: topology_request Block - Volume Specification
+description: The "topology_request" block allows specifying locations where the provisioned volume must be accessible from.
+---
+
+# `topology_request` Block
+
+<Placement
+  groups={[
+    ['volume', 'topology_request'],
+  ]}
+/>
+
+Specify locations (region, zone, rack, etc.) where the provisioned volume must
+be accessible from or from where an existing volume is accessible from.
+
+```hcl
+id           = "ebs_prod_db1"
+namespace    = "default"
+name         = "database"
+type         = "csi"
+plugin_id    = "ebs-prod"
+capacity_max = "200G"
+capacity_min = "100G"
+
+topology_request {
+  required {
+    topology { segments { rack = "R2" } }
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+Consult the documentation for your storage provider and CSI plugin as to
+whether it supports defining topology and what values it expects for topology
+segments. Specifying topology segments that aren't supported by the storage
+provider may return an error or may be silently removed by the plugin.
+
+## `topology_request` Parameters
+
+- `required` <code>([Topology][topology]: nil)</code> - On **volume creation**,
+  the `required` topologies indicate that the volume must be created in a
+  location accessible from at least one of the listed topologies. On **volume
+  registration** the `required` topologies indicate that the volume was created
+  in a location accessible from all the listed topologies.
+
+- `preferred` <code>([Topology][topology]: nil)</code> - Indicate that you
+  would prefer the storage provider to create the volume in one of the provided
+  topologies. Only allowed on **volume creation**.
+
+### `topology` Parameters
+
+- `segments` `(map[string]string)` - A map of location types to their values.
+  The specific fields required are defined by the CSI plugin.
+
+## `topology_request` Examples
+
+The following examples only show the `topology_request` blocks. Remember that
+the `topology_request` block is only valid in the placements listed above.
+
+### Volume creation with `preferred` and `required` topologies
+
+This configuration indicates you require the volume to be created within racks
+`R1` or `R2`, but that you prefer the volume to be created within `R1`.
+
+```hcl
+topology_request {
+  required {
+    topology { segments { rack = "R1", zone = "us-east-1a" } }
+    topology { segments { rack = "R2", zone = "us-east-1a" } }
+  }
+  preferred {
+    topology { segments { rack = "R1", zone = "us-east-1a"} }
+  }
+}
+```
+
+[topology]: #topology-parameters
diff --git a/content/nomad/v1.9.x/content/docs/partnerships.mdx b/content/nomad/v1.9.x/content/docs/partnerships.mdx
new file mode 100644
index 0000000000..4936caaf3f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/partnerships.mdx
@@ -0,0 +1,135 @@
+---
+layout: docs
+page_title: Nomad Integration Program
+description: The HashiCorp Nomad Integration Program is the process for building and certifying products that integrate with Nomad. Review the integration categories and development process.
+---
+
+# Nomad Integration Program
+
+This page provides an overview of the HashiCorp Nomad Integration Program.
+
+## Introduction
+
+The HashiCorp Nomad Integration Program allows vendors to integrate their products to work with Nomad. As a scheduler, Nomad encompasses a broad area. Thereby, a set of integrations may require vendor integration code.
+
+Vendors integrating their solutions via the Nomad Integration Process provide their customers a verified and seamless user experience. The Nomad Integration Program primarily supports coding with the Go programming language.
+
+This program is intended to be largely a self-service process with links and guidance to information sources, clearly defined steps, and checkpoints.
+
+## Types of Nomad Integrations
+
+Nomad is a simple and flexible orchestrator to deploy and manage containers and non-containerized applications across on-premises and cloud environments at scale. Nomad is widely adopted and used in production by organizations like Cloudflare, Roblox, Q2, Pandora, and more. See the [Introduction](/nomad/intro) page for a full description of the current features. The diagram below depicts the key Nomad integration categories and types.
+
+![Integration Categories](/img/nomad-workload.png)
+
+Main Nomad categories for partners to integrate with include:
+
+- CI/CD (Continuous Integration & Delivery)
+- Container Runtime
+- GPUs & Other Hardware Devices
+- Monitoring
+- Artifact Repo
+- Networking
+- Storage
+- Autoscaling
+
+## Development Process
+
+The Nomad integration development process is divided into six steps. By following these steps, Nomad integrations can be developed alongside HashiCorp to ensure that the integrations are able to be verified and supported in Nomad as quickly as possible. A visual representation of the self-guided steps is depicted below.
+![Development Process](https://www.datocms-assets.com/2885/1618463733-nomad-integration-program-steps.png)
+
+The individual Nomad integration steps include:
+
+1.  Engage: Initial contact between vendor and HashiCorp
+2.  Enable: Information and articles to aid with the development of the integration
+3.  Dev/Test: Integration development and test process
+4.  Review: HashiCorp code review and verification of integration (iterative process)
+5.  Release: Verified integration made available and listed on the HashiCorp website once the HashiCorp technology partnership agreement has been executed
+6.  Support: Ongoing maintenance and support of the provider by the vendor.
+
+### 1. Engage
+
+Please begin by providing some basic information about the integration that is being built via a simple [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform).
+
+This information is recorded and used by HashiCorp to track the integration through various stages. The information is also used to notify the integration developer of any overlapping work, perhaps coming from the community so you may better focus resources.
+
+Nomad has a large and active community and ecosystem of partners that may have already started working on a similar integration. We'll do our best to connect similar parties to avoid duplicate work.
+
+### 2. Enable
+
+While not mandatory, HashiCorp encourages vendors to sign and MNDA (Mutual Non-Disclosure Agreement) to allow for open dialog and sharing of ideas during the integration process.
+
+In an effort to support our self-serve model we've included links to resources, documentation, examples and best practices to guide you through the Nomad integration development and testing process.
+
+- Contributing to Nomad [guidelines](https://github.com/hashicorp/nomad/tree/main/contributing)
+- [Nomad Developer Community Forum](https://groups.google.com/g/nomad-tool)
+- [Nomad's source code](https://github.com/hashicorp/nomad)
+
+We encourage vendors to closely follow the above guidance. Adopting the same structure and coding patterns helps expedite the review and release cycles.
+
+### 3. Dev & Test
+
+Nomad requires all code-level integrations to be written in the [Go](https://golang.org/) programming language and contain an [MPL-2.0](https://en.wikipedia.org/wiki/Mozilla_Public_License) open source license. The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the Go programming language. When writing in Go-Language, HashiCorp has found the integration development process to be straightforward and simple when vendors pay close attention and follow the resources and by adopting the same structure and coding patterns helps expedite the review and release cycles. Please remember that all integration major steps should contain acceptance testing and the appropriate documentation.
+
+Container Runtime
+
+- [Task driver documentation](/nomad/docs/drivers)
+- [Guide to build, install, and maintaining a task driver plugin](/nomad/docs/concepts/plugins/task-drivers)
+- [Community examples of task drivers](/nomad/plugins/drivers/community)
+
+GPUs & Specialized Hardware Devices
+
+- [Device plugin documentation](/nomad/plugins/devices)
+- [Guide to build, install, and maintain a device plugin](/nomad/docs/concepts/plugins/devices)
+- [Template for writing a device plugin](https://github.com/hashicorp/nomad-skeleton-device-plugin)
+- [Example of a device plugin](https://github.com/hashicorp/nomad/tree/main/devices/gpu/nvidia)
+
+Autoscaling
+
+- [Autoscaling plugin documentation](/nomad/tools/autoscaling)
+
+Storage
+
+- [CSI plugins documentation](/nomad/docs/concepts/plugins/csi)
+
+Observability & Analysis
+
+- [Telemetry documentation](/nomad/docs/operations/monitoring-nomad)
+
+## 4. Review
+
+During the review process, HashiCorp will provide feedback on the newly developed integration. This is an important step to allow HashiCorp to review and verify your Nomad integration. Please send the integration code and other relevant logs for verification to: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
+
+For task, device, storage, and autoscaling plugins, please submit a GitHub pull request (PR) against the [Nomad project](https://github.com/hashicorp/nomad). In some cases the vendor may need to provide HashiCorp with a permanent test account so that the integration can be verified on an ongoing basis.
+
+The review process can take a while to complete and may require some iterations through the code to address and problems identified by the HashiCorp team.
+
+### 5. Release
+
+At this stage, it is expected that the integration is fully complete, the necessary documentation has been written, the acceptance tests have all passed, and that HashiCorp has reviewed the integration. Once the plugin has been validated and accepted by HashiCorp, the plugin can be hosted anywhere so it can easily be downloaded then installed within Nomad.
+
+Once the integration has been released the vendor is requested to sign the HashiCorp Technology Partner Agreement so that we can have their integration be listed on the HashiCorp website.
+
+### 6. Support
+
+Many vendors view the release step to be the end of the journey, while at HashiCorp we view it to be the beginning of the journey. Getting the integration built is just the first step in enabling users to leverage it against their infrastructure. Once development is completed, on-going effort is required to support the developed integration, maintain the provider, and address any issues in a timely manner.
+
+The expectation from the vendor/partner is to create a mechanism for them to track and resolve all critical issues as soon as possible within 48 hours and all other issues within 5 business days. This is a requirement given the critical nature of Nomad to the customer's operation. Vendors who choose to not support their integration will not be considered a verified integration and cannot be listed on the website.
+
+## Checklist
+
+Below is an ordered checklist of steps that should be followed during the integration process. This just reiterates the steps already documented in the sections above.
+
+- Fill out the Nomad integration [webform](https://docs.google.com/forms/d/e/1FAIpQLSflmhg8lkY5QyH3CB5TUMi4I1ZFQFx_GP_TVDtsbxMaFEMWpw/viewform)
+- Execute the HashiCorp MNDA (Mutual Non-Disclosure Agreement) if needed
+- Develop and test Nomad integration along with the acceptance tests and documentation
+- Send email to [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com) to schedule an initial review
+- Address review feedback and finalize the development process
+- Provide HashiCorp with credentials for underlying infrastructure for test purposes
+- Demo the integration and/or send the test logs to HashiCorp at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com)
+- Execute HashiCorp Partner Agreement Documents, review logo guidelines, partner listing and more
+- Plan to continue supporting the integration with additional functionality and responding to customer issues.
+
+## Contact Us
+
+For any questions or feedback, please contact us at: [Nomad-integration-dev@hashicorp.com](mailto:Nomad-integration-dev@hashicorp.com).
diff --git a/content/nomad/v1.9.x/content/docs/release-notes/index.mdx b/content/nomad/v1.9.x/content/docs/release-notes/index.mdx
new file mode 100644
index 0000000000..67d880152e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/release-notes/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: Release Notes
+description: |-
+  Hashicorp Nomad release notes.
+---
+
+# Release Notes
+
+Choose a version from the navigation sidebar to view the release notes for Nomad.
+
+Documentation for maintenance releases (e.g., 0.1.x) is on the bottom of each
+release notes page.
diff --git a/content/nomad/v1.9.x/content/docs/release-notes/nomad/upcoming.mdx b/content/nomad/v1.9.x/content/docs/release-notes/nomad/upcoming.mdx
new file mode 100644
index 0000000000..a6bc835586
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/release-notes/nomad/upcoming.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Upcoming
+description: >-
+  Review upcoming HashiCorp Nomad release changes.
+---
+
+# Upcoming
+
+Nomad strives to be backward compatible for at least 2 major releases, so for
+example, you can upgrade Nomad v1.6.x to Nomad v1.8.x. In addition, Enterprise
+customers have access to [Long Term Support (LTS)][LTS] releases.
+
+Refer to [Upgrading][] for details of the upgrade process, and [Upgrade
+Guides][] for notes on upgrading specific versions.
+
+However, from time to time it's necessary to make backwards _incompatible_
+changes to Nomad. We announce these on [changelog][], the [Release Notes][], and
+the version-specific [Upgrade Guides][]. In order to help you plan your
+upgrades, this page maintains a list of all planned future changes that might
+cause backwards incompatibilities or require operational changes. It's possible
+that a given change may happen later than intended, at which point we update
+this document. However, we do not move changes earlier than originally published
+unless there's a required change due to a security vulnerability.
+
+## Nomad 1.9.0
+
+* Nomad will remove support for HCL1 job specifications and the `-hcl1` flag on
+  the `nomad job run` and other commands. Refer to [GH-20195][] for more details.
+* Nomad will remove the [`tls_prefer_server_cipher_suites`][] agent configuration.
+* Nomad will remove support for Nomad client agents older than 1.6.0. Older
+  nodes will fail heartbeats. Nomad servers will mark the workloads on those
+  nodes as lost and reschedule them normally according to the job's
+  [`reschedule`][] block.
+
+## Nomad 1.10.0 LTS
+
+Nomad 1.10.0 is a Long-Term Support release for Enterprise customers.
+
+* Nomad will remove support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the integration
+  guide][consul-integration] for details.
+* Nomad will remove support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the integration guide][vault-integration] for
+  details.
+* Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+* Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+* Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+[LTS]: /nomad/docs/enterprise#long-term-support-lts-releases
+[Upgrading]: /nomad/docs/upgrade
+[Upgrade Guides]: /nomad/docs/upgrade/upgrade-specific
+[changelog]: https://github.com/hashicorp/nomad/blob/main/CHANGELOG.md
+[Release Notes]: /nomad/docs/release-notes
+[GH-20195]: https://github.com/hashicorp/nomad/issues/20195
+[`tls_prefer_server_cipher_suites`]: /nomad/docs/configuration/tls#tls_prefer_server_cipher_suites
+[consul-integration]: /nomad/docs/integrations/consul/acl
+[vault-integration]: /nomad/docs/integrations/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/job-specification/disconnect
+[`reschedule`]: /nomad/docs/job-specification/reschedule
diff --git a/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_8_x.mdx b/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_8_x.mdx
new file mode 100644
index 0000000000..085e30d942
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_8_x.mdx
@@ -0,0 +1,139 @@
+---
+layout: docs
+page_title: 1.8.x
+description: >-
+  HashiCorp Nomad version 1.8.x release notes. Long term support release. Exec2 task driver beta, transparent proxy support for Consul service mesh, Consul API Gateway for Nomad support, UI jobs page updates, time-based task execution, Sentinel policy management in the UI, nomad-bench.
+---
+
+# Nomad 1.8.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Long Term Support Release (Enterprise):** Nomad 1.8 introduces a [long term
+  support release](/nomad/docs/enterprise#long-term-support-lts-releases) which
+  provides extended maintenance (two years of critical fixes provided through
+  minor releases and efficient upgrades (support for direct upgrades from one
+  LTS release to the next).
+
+- **Exec2 Task Driver (beta):** The `exec2` driver is used to execute a
+  command for a task. It offers a security model optimized for running
+  'ordinary' processes with very low startup times and minimal overhead in
+  terms of CPU, disk, and memory utilization. The `exec2` driver leverages
+  kernel features such as the Landlock LSM, cgroups v2, and the unshare system
+  utility. Due these enhancements, tasks no longer require leveraging
+  filesystem isolation based on chroot, which provide an enhanced security
+  profile and improved performance for the Nomad operator. Refer to [Exec2 Task
+  Driver](/nomad/plugins/v1.8.x/drivers/exec2) for more details.
+
+- **Transparent proxy support for Consul service mesh:** Transparent Proxy
+  introduces a more seamless way of dialing upstream services when Consul service
+  mesh is enabled. Users can configure services to use transparent proxy with a
+  new [`transparent_proxy`](/nomad/docs/v1.8.x/job-specification/transparent_proxy)
+  block. When a service is configured to use transparent proxy, workloads can now dial the
+  service using a virtual IP Consul DNS name.
+
+- **Consul API Gateway for Nomad:** Consul API Gateway on Nomad is now
+  officially supported. A prescriptive job specification on
+  [hashicorp-guides/consul-api-gateway-on-nomad](https://github.com/hashicorp-guides/consul-api-gateway-on-nomad)
+  along with a supporting [tutorial](/nomad/tutorials/integrate-consul/deploy-api-gateway-on-nomad) on
+  how to securely deploy Consul API gateway on Nomad.
+
+- **Re-worked Jobs page in the web UI with live updates:** Within the [Jobs
+  index](/nomad/tutorials/web-ui/web-ui-workload-info#list-jobs) page Nomad has
+  made a few improvements:
+
+  - **Prioritize showing the current state over historical state for jobs:**
+  Previously, long-garbage-collected allocation placement failures, lost nodes,
+  and other historical representations of job state were shown alongside
+  currently running allocations. In self-healing jobs, this often meant that a
+  healthy job looked like it had failures, when in fact Nomad had replaced or
+  rescheduled those failures. Now, the jobs list tries to show accurate
+  allocation information and meaningful statuses (like "Degraded", or
+  "Recovering") to better illustrate the current state of a job.
+
+  - **Server-side pagination:** For users with many thousands of jobs, the main
+  landing page for the web UI will no longer have a noticeable delay on
+  rendering. Users can control page length and filter paginated jobs
+  appropriately.
+
+  - **Live updates:** Previously, users had to manually refresh
+  the page to see newly created jobs, or to hide jobs that had been stopped and
+  garbage-collected. Now, the jobs list will update in real-time as jobs are
+  created, updated, or removed. Further, any changes to allocations of jobs
+  on-page will be reflected in the status of that job in real-time.
+
+- **Time based task execution (Enterprise) :** Using a CRON-like syntax, operators can now
+  [schedule](/nomad/docs/job-specification/schedule) when tasks should execute
+  and when they should stop. This provides governance for tasks executed from
+  jobs, and allows operators to easily opt-in or opt-out of a schedule that
+  governs when the task can run through the web based UI or through the [CLI](/nomad/docs/commands/alloc/pause).
+
+- **Sentinel policy management in the Web UI (Enterprise):** Enterprise users can manage
+  Sentinel policies directly within the Nomad UI. Users can create a Sentinel
+  policy based on a template provided from the UI or create policies directly
+  using an editor for Sentinel policies. Refer to [Sentinel
+  policies](/nomad/tutorials/governance-and-policy/sentinel) to learn more about
+  how to use Sentinel within Nomad.
+
+- **nomad-bench:** Nomad now provides a testing framework through
+  [nomad-bench](https://github.com/hashicorp-forge/nomad-bench) which provisions
+  infrastructure used to run tests and benchmarks against Nomad test
+  clusters. The infrastructure consists of Nomad test clusters that each have a
+  set of servers with hundreds or thousands of simulated nodes created using
+  nomad-nodesim. The Nomad server processes are not simulated and are expected
+  to run on their own hosts, mimicking real-world deployments.  Metrics are then
+  gathered from the Nomad servers for use with benchmarking and load testing.
+
+## What's deprecated
+
+- **LXC Task driver:** The [Community LXC Task
+  Driver](/nomad/plugins/drivers/community/lxc) is now deprecated. Official
+  support will be removed and the repo will be archived when Nomad 1.9 is
+  released. Users are encouraged to migrate their workloads to another task
+  driver such as the built-in Docker task [driver](/nomad/docs/drivers/docker).
+
+- **ECS Task driver:** The remote [ECS Task
+  Driver](https://developer.hashicorp.com/nomad/plugins/drivers/remote/ecs) is
+  now deprecated. Official support will be removed and the repo will be
+  archived when Nomad 1.9 is released. Users are encouraged to migrate their
+  workloads to Amazon ECS or to another Nomad task driver.
+
+- **`stop_after_client_disconnect`, `max_client_disconnect`,
+  `prevent_reschedule_on_lost`:** Nomad 1.8.0 introduces a
+  [disconnect](/nomad/docs/job-specification/disconnect) block meant to group
+  all the configuration options related to disconnected client's and server's
+  behavior, causing the deprecation of the fields stop_after_client_disconnect,
+  max_client_disconnect and prevent_reschedule_on_lost. This block also
+  introduces new options for allocations reconciliation if the client regains
+  connectivity.
+
+- **32-bit builds**: Support for 32-bit architectures is now deprecated. Nomad
+  releases will no longer include binaries built for 32-bit platforms starting
+  with Nomad 1.9.
+
+## What's removed
+
+- **raw_exec option `no_cgroups`:** In Nomad 1.7.0 the raw_exec plugin option
+  for no_cgroups became ineffective. Starting in Nomad 1.8.0 attempting to set
+  the no_cgroups in raw_exec plugin configuration will result in an error when
+  starting the agent.
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
+
+## Known issues
+
+The following issues are known to exist in the v1.8.x releases:
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.8.0](https://github.com/hashicorp/nomad/releases/tag/v1.8.0)
diff --git a/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_9_x.mdx b/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_9_x.mdx
new file mode 100644
index 0000000000..81ac075fad
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/release-notes/nomad/v1_9_x.mdx
@@ -0,0 +1,136 @@
+---
+layout: docs
+page_title: 1.9.x
+description: >-
+  HashiCorp Nomad version 1.9.x release notes. Multi-Instance GPU (MIG) support, quotas for device resources, NUMA-aware scheduling, job versions, Virt task driver beta, Exec2 task driver GA, improved IPv6 support.
+---
+
+# Nomad 1.9.0
+
+We are pleased to announce the following Nomad updates.
+
+## Release highlights
+
+- **Multi-Instance GPU (MIG) support added to the NVIDIA device driver**: This
+enhances Nomad’s ability to schedule workloads across your NVIDIA hardware and
+make full use of your GPU investment. The device driver automatically detects
+MIGs. Refer to the [NVIDIA driver docs](/nomad/plugins/devices/nvidia) for
+details.
+
+- **Quotas for device resources (Enterprise)**: This release extends quotas to
+allow limiting [device resources](/nomad/docs/job-specification/device). Refer
+to [Resource quotas](/nomad/docs/other-specifications/quota) for configuration details.
+
+- **NUMA awareness for device resources (Enterprise)**: Nomad is able to
+  correlate CPU cores with memory nodes and assign tasks to run on specific CPU
+  cores so as to minimize any cross-memory node access patterns. With Nomad 1.9,
+  we are expanding this functionality to also correlate
+  [devices](/nomad/docs/concepts/plugins/devices) to memory nodes and enable
+  NUMA-aware scheduling to take device associativity into account when making
+  scheduling decisions. Refer to [numa
+  Block](/nomad/docs/job-specification/numa) for configuration details.
+
+- **Golden job versions**: This feature introduces a way to preserve and compare
+  historical versions of a job. Prior to this, any change to a job would push
+  older versions into garbage collection. Now, you can tag a version to save it
+  from garbage collection. Additionally, you can compare job versions by tag
+  name and revert by tag name. Refer to [Job
+  versions](/nomad/docs/concepts/job.mdx#job-versions) for details and links to
+  how to use job version tagging.
+
+- **Virt task driver (beta)**: The new Virt task driver uses
+  [libvirt](https://libvirt.org/) to manage virtual machines created by KVM,
+  Xen, VMware ESXi, QEMU, and other virtualization technologies. Using this
+  driver, you can perform the following:
+
+  - Start and stop a virtual machine and run a process on it.
+  - Assign a workload identity to the running task inside the virtual machine.
+  - Pass configuration values from Vault or other services using consul-template.
+  - Mount host directories into virtual machines to procure the allocation and task directories inside them.
+  - Configure port forwarding from the Nomad node to the virtual machine.
+  - Access the running task through the task API.
+
+  Refer to the [Virt driver docs](https://github.com/hashicorp/nomad-driver-virt)
+  for installation and usage guides.
+
+- **Exec2 Task Driver (GA):** The `exec2` driver is used to execute a command
+for a task. It offers a security model optimized for running 'ordinary'
+processes with very low startup times and minimal overhead in terms of CPU,
+disk, and memory utilization. The `exec2` driver leverages kernel features such
+as the Landlock LSM, cgroups v2, and the unshare system utility. Due these
+enhancements, tasks no longer require leveraging filesystem isolation based on
+chroot, which provide an enhanced security profile and improved performance for
+the Nomad operator. Refer to [Exec2 Task Driver](/nomad/plugins/drivers/exec2)
+for more details.
+
+- **Improved IPv6 support**: Nomad has improved support for Nomad's IPv6
+capabilities. We have tested and resolved some known issues with
+server-to-server and server-to-client communications. Additionally we have
+tested the Nomad CLI and UI service integrations with Consul and Vault, workload
+identity, service registration, host networking, bridge networking, and the
+Docker driver. More work will likely need to be done with IPv6 support as we
+explore integrations with Consul service mesh.
+
+
+## What's deprecated
+
+The following are deprecated and will be removed in 1.10.
+
+- Support for the legacy token workflow for Consul. Workloads
+  that need Consul support will require the cluster be configured to use
+  Workload Identity with Consul. Refer to [the Consul integration
+  guide][consul-integration] for details.
+- Support for the legacy token workflow for Vault. Workloads
+  that need Vault support will require the cluster be configured to use Workload
+  Identity with Vault. Refer to [the Vault integration guide][vault-integration] for
+  details.
+- Nomad will no longer create an implicit `consul` block for workloads that
+  don't register services with Consul. Jobs that require Consul tokens for
+  `template` rendering will be required to provide a `consul` block.
+- Nomad clients will no longer execute all binaries in the plugin directory on
+  startup for fingerprinting. Only plugins with an associated `plugin` block in
+  the Nomad agent configuration will be fingerprinted. Refer to [GH-18529][] for
+  more details.
+- Nomad will ignore the deprecated `stop_after_client_disconnect`,
+  `max_client_disconnect`, and `prevent_reschedule_on_lost` fields and only
+  support the [`disconnect`][] block, which covers the same functionality.
+
+## What's removed
+
+- Support for HCLv1 job specifications and the `-hcl1` flag on `nomad job run` and other commands. Refer to [GH-20195](https://github.com/hashicorp/nomad/issues/20195) for more details.
+
+- Support for Nomad client agents older than v1.6.0. Older nodes will fail heartbeats. Nomad servers will mark the workloads on Nomad client agents older than 1.6.0 as lost and reschedule them normally according to the job's [reschedule](/nomad/docs/job-specification/reschedule) block.
+
+- The [LXC task driver](https://github.com/hashicorp/nomad-driver-lxc) and [ECS
+  task driver](https://github.com/hashicorp/nomad-driver-ecs) projects have been
+  archived with the release of Nomad 1.9 and are no longer supported.  Both
+  plug-ins are maintained separately from the Nomad core project and are not
+  subject to the LTS program.
+
+- Nomad has removed the `tls_prefer_server_cipher_suites` agent configuration from the [`tls` block](/nomad/docs/configuration/tls).
+
+
+## Upgrading
+
+For more detailed information, please refer to the [upgrade details
+page](/nomad/docs/upgrade/upgrade-specific#nomad-1-9-0) and the changelogs.
+
+## Known issues
+
+None.
+
+## Changelogs
+
+The changelogs for this major release version and any maintenance versions are
+listed below.
+
+<Note> These links take you to the changelogs on the GitHub website. </Note>
+
+- [1.9.0](https://github.com/hashicorp/nomad/releases/tag/v1.9.0)
+
+
+[consul-integration]: /nomad/docs/integrations/consul/acl
+[vault-integration]: /nomad/docs/integrations/vault/acl
+[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
+[`disconnect`]: /nomad/docs/job-specification/disconnect
+[Resource Quotas]: /nomad/docs/other-specifications/quota
diff --git a/content/nomad/v1.9.x/content/docs/runtime/environment.mdx b/content/nomad/v1.9.x/content/docs/runtime/environment.mdx
new file mode 100644
index 0000000000..d56d00bf5f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/runtime/environment.mdx
@@ -0,0 +1,118 @@
+---
+layout: docs
+page_title: Runtime Environment Settings
+description: Nomad provides runtime environment variables that you can use in your workloads. Learn about task identifiers, CPU and memory resources, IP addresses, task directories, and host variables. Review job, network, and Consul variables. Supply arbitrary configuration to a job task.
+---
+
+# Runtime Environment Settings
+
+This page provides reference information for runtime environment settings in
+your Nomad job specification. Learn about task identifiers, CPU and memory resources, IP addresses, task directories, and host variables. Review job, network, and Consul variables. Supply arbitrary configuration to a job task.
+
+## Introduction
+
+Some settings you specify in your [job specification][jobspec] are passed
+to tasks when they start. Other settings are dynamically allocated when your job
+is scheduled. Both types of values are made available to your job through
+environment variables.
+
+## Variables Summary
+
+@include 'envvars.mdx'
+
+## Task Identifiers
+
+Nomad will pass both the allocation ID and name, the deployment ID that created
+the allocation, the job ID and name, the parent job ID as well as
+the task and group's names. These are given as `NOMAD_ALLOC_ID`, `NOMAD_ALLOC_NAME`,
+`NOMAD_ALLOC_INDEX`, `NOMAD_JOB_NAME`, `NOMAD_JOB_ID`,
+`NOMAD_JOB_PARENT_ID`, `NOMAD_GROUP_NAME` and `NOMAD_TASK_NAME`. The allocation ID
+and index can be useful when the task being run needs a unique identifier or to
+know its instance count.
+
+## Resources
+
+When you request resources for a job, Nomad creates a resource offer. The final
+resources for your job are not determined until it is scheduled. Nomad will
+tell you which resources have been allocated after evaluation and placement.
+
+### CPU and Memory
+
+Nomad will pass CPU and memory limits to your job as `NOMAD_CPU_LIMIT`,
+`NOMAD_MEMORY_LIMIT`, and `NOMAD_MEMORY_MAX_LIMIT`. Your task should use these
+values to adapt its behavior to fit inside the resource allocation that Nomad
+provides. For example, you can use the memory limit to inform how large your
+in-process cache should be, or to decide when to flush buffers to disk.
+
+Both CPU and memory are presented as integers. The unit for CPU limit is
+`1024 = 1GHz`. The unit for memory is `1 = 1 megabyte`.
+
+Writing your applications to adjust to these values at runtime provides greater
+scheduling flexibility since you can adjust the resource allocations in your
+job specification without needing to change your code. You can also schedule workloads
+that accept dynamic resource allocations so they can scale up or down as your
+cluster gets more or less busy.
+
+### Networking
+
+Nomad assigns IP addresses and ports to your jobs and exposes them via environment
+variables. See the [Networking](/nomad/docs/job-specification/network) page for more
+details.
+
+### Task Directories
+
+Nomad creates a working directory for each allocation on a client. The
+allocation working directory contains a task working directory for each task
+in the allocation.
+
+Nomad makes the following directories available to tasks, relative to the task
+working directory:
+
+- `alloc/`: This directory is shared across all tasks in a task group and can be
+  used to store data that needs to be used by multiple tasks, such as a log
+  shipper.
+- `local/`: This directory is private to each task. It can be used to store
+  arbitrary data that should not be shared by tasks in the task group.
+- `secrets/`: This directory is private to each task, not accessible via the
+  `nomad alloc fs` command or filesystem APIs. Where possible it is backed by an
+  in-memory filesystem and mounted `noexec`. It can be used to store secret data
+  that should not be visible outside the task.
+
+These directories are persisted until the allocation is removed, which occurs
+hours after all the tasks in the task group enter terminal states. This gives
+time to view the data produced by tasks.
+
+Depending on the driver and operating system being targeted, the directories
+are made available in various ways. For example, on `docker` the directories
+are bound to the container, while on `exec` on Linux the chroot is built in
+the task working directory, and the directories are mounted into that
+chroot. Regardless of how the directories are made available, the path to the
+directories can be read through the `NOMAD_ALLOC_DIR`, `NOMAD_TASK_DIR`, and
+`NOMAD_SECRETS_DIR` environment variables.
+
+For more details on the task directories, see the [Filesystem internals][].
+
+## Meta block for arbitrary configuration
+
+The job specification also allows you to specify a `meta` block to supply
+arbitrary configuration to a task. This allows you to easily provide
+job-specific configuration even if you use the same executable unit in multiple
+jobs. These key-value pairs are passed through to the job as
+`NOMAD_META_<key>=<value>` environment variables. Any character in a key other
+than `[A-Za-z0-9_.]` will be converted to `_`. Both the original case and an uppercased
+version are injected. The uppercased version will be deprecated in a future release.
+
+Currently there is no enforcement that the meta keys be lowercase, but using
+multiple keys with the same uppercased representation will lead to undefined
+behavior.
+
+## Host environment variables
+
+Nomad passes the environment variables defined in the client host to tasks when
+using the `exec`, `raw_exec`, and `java` task drivers. The variables that are
+passed to the tasks can be controlled using the client configuration
+[`env.denylist`][].
+
+[jobspec]: /nomad/docs/job-specification 'Nomad Job Specification'
+[filesystem internals]: /nomad/docs/concepts/filesystem
+[`env.denylist`]: /nomad/docs/configuration/client#env-denylist
diff --git a/content/nomad/v1.9.x/content/docs/runtime/index.mdx b/content/nomad/v1.9.x/content/docs/runtime/index.mdx
new file mode 100644
index 0000000000..680b4ef056
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/runtime/index.mdx
@@ -0,0 +1,18 @@
+---
+layout: docs
+page_title: Runtime
+description: |-
+  Learn about Nomad's runtime environment variables, interpolation, and schedulers.
+---
+
+# Runtime
+
+This section details Nomad's runtime information, including environment
+variables, interpolations, and caveats.
+
+To learn more about Nomad's runtime, choose an item from the sidebar, or choose
+one of the options below:
+
+- [Environment](/nomad/docs/runtime/environment)
+- [Interpolation](/nomad/docs/runtime/interpolation)
+- [Schedulers](/nomad/docs/schedulers)
diff --git a/content/nomad/v1.9.x/content/docs/runtime/interpolation.mdx b/content/nomad/v1.9.x/content/docs/runtime/interpolation.mdx
new file mode 100644
index 0000000000..a5f4761661
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/runtime/interpolation.mdx
@@ -0,0 +1,206 @@
+---
+layout: docs
+page_title: Variable Interpolation
+description: Nomad supports interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review job, network, and Consul environment variables.
+---
+
+# Variable Interpolation
+
+This page provides reference information on interpreting node attributes and runtime environment variables in a Nomad workload. Learn the syntax for interpreting variables in a Nomad job specification. Review node attributes for clients, hardware, platform, and OS. Review Review job, network, and Consul environment variables.
+
+## Introduction
+
+Nomad supports interpreting two classes of variables: node attributes and
+runtime environment variables. Node attributes are interpretable in constraints,
+task environment variables, and certain driver fields. Runtime environment
+variables are not interpretable in constraints because they are only defined
+once the scheduler has placed them on a particular node.
+
+Nomad supports interpreting two classes of variables: [node attributes](#interpreted_node_vars)
+and [runtime environment variables](#interpreted_env_vars). Node attributes are
+interpretable in [constraints](/nomad/docs/job-specification/constraint),
+[task environment variables](/nomad/docs/job-specification/env), and certain
+task driver fields—for example the [`labels`](/nomad/docs/drivers/docker#labels)
+attribute of the Docker [`config`](/nomad/docs/drivers/docker).
+
+<Note>
+Runtime environment variables are not defined until after the scheduler
+has placed the job, so they are unavailable for use in job constraints.
+</Note>
+
+## Syntax
+
+The syntax for interpreting variables in the Nomad job specification is
+`${variable_name}`. The [`template` block](/nomad/docs/job-specification/template)
+uses the `env` function to retrieve these variables from the environment, using
+`{{env "variable_name"}}` instead. Examples can be seen below:
+
+```hcl
+task "docs" {
+  driver = "docker"
+
+  # Drivers support interpreting node attributes and runtime environment
+  # variables
+  config {
+    image = "my-app"
+
+    # Interpret runtime variables to inject the address to bind to and the
+    # location to write logs to.
+    args = [
+      "--bind", "${NOMAD_ADDR_RPC}",
+      "--logs", "${NOMAD_ALLOC_DIR}/logs",
+    ]
+
+    port_map {
+      RPC = 6379
+    }
+  }
+
+  # Constraints only support node attributes as runtime environment variables
+  # are only defined after the task is placed on a node.
+  constraint {
+    attribute = "${attr.kernel.name}"
+    value     = "linux"
+  }
+
+  template {
+    destination = "template.txt"
+    data = <<EOT
+{{- /*
+      Environment variables are available to templates via the env function,
+      rather than the ${...} syntax.
+*/ -}}
+Running on {{env "attr.unique.hostname"}}.
+EOT
+  }
+
+  # Environment variables are interpreted and can contain both runtime and
+  # node attributes. These environment variables are passed into the task.
+  env {
+    DC      = "Running on datacenter ${node.datacenter}"
+    VERSION = "Version ${NOMAD_META_VERSION}"
+  }
+
+  # Meta keys are also interpretable.
+  meta {
+    VERSION = "v0.3"
+  }
+}
+```
+
+## Node Attributes ((#interpreted_node_vars, #node-variables-))
+
+Below is a full listing of node attributes that are interpretable. These
+attributes are interpreted by **both** constraints and within the task and
+driver.
+
+| Variable              | Description                                 | Example Value                          |
+|-----------------------|---------------------------------------------|----------------------------------------|
+| `${node.unique.id}`   | 36 character unique client identifier       | `9afa5da1-8f39-25a2-48dc-ba31fd7c0023` |
+| `${node.region}`      | Client's region                             | `global`                               |
+| `${node.datacenter}`  | Client's datacenter                         | `dc1`                                  |
+| `${node.unique.name}` | Client's name                               | `nomad-client-10-1-2-4`                |
+| `${node.class}`       | Client's class                              | `linux-64bit`                          |
+| `${node.pool}`        | Client's node pool                          | `prod`                                 |
+| `${attr.<property>}`  | Property given by `property` on the client  | `${attr.cpu.arch} => amd64`            |
+| `${meta.<key>}`       | Metadata value given by `key` on the client | `${meta.foo} => bar`                   |
+
+Below is a table documenting common node properties.
+
+| Property                                           | Description                                                                                                                                            |
+| ---------------------------------------------------| ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `${attr.cpu.arch}`                                 | CPU architecture of the client (e.g. `amd64`, `386`)                                                                                                   |
+| `${attr.cpu.numcores}`                             | Number of CPU cores on the client. May differ from how many cores are available for reservation due to OS or configuration. See `cpu.reservablecores`. |
+| `${attr.cpu.reservablecores}`                      | Number of CPU cores on the client available for scheduling. Number of cores used by the scheduler when placing work with `resources.cores` set.        |
+| `${attr.cpu.totalcompute}`                         | `cpu.frequency × cpu.numcores` but may be overridden by `client.cpu_total_compute`                                                                     |
+| `${attr.consul.datacenter}`                        | The Consul datacenter of the client (if Consul is found)                                                                                               |
+| `${attr.driver.<property>}`                        | See the [task drivers](/nomad/docs/drivers) for property documentation                                                                                 |
+| `${attr.unique.hostname}`                          | Hostname of the client                                                                                                                                 |
+| `${attr.unique.network.ip-address}`                | The IP address fingerprinted by the client and from which task ports are allocated                                                                     |
+| `${attr.kernel.arch}`                              | Kernel architecture of the client (e.g. `x86_64`, `aarch64`)                                                                                           |
+| `${attr.kernel.name}`                              | Kernel of the client (e.g. `linux`, `darwin`)                                                                                                          |
+| `${attr.kernel.version}`                           | Version of the client kernel (e.g. `3.19.0-25-generic`, `15.0.0`)                                                                                      |
+| `${attr.platform.aws.ami-id}`                      | AMI ID of the client (if on AWS EC2)                                                                                                                   |
+| `${attr.platform.aws.instance-life-cycle}`         | Instance lifecycle (e.g. spot, on-demand) of the client (if on AWS EC2)                                                                                |
+| `${attr.platform.aws.instance-type}`               | Instance type of the client (if on AWS EC2)                                                                                                            |
+| `${attr.platform.aws.placement.availability-zone}` | Availability Zone of the client (if on AWS EC2)                                                                                                        |
+| `${attr.os.name}`                                  | Operating system of the client (e.g. `ubuntu`, `windows`, `darwin`)                                                                                    |
+| `${attr.os.version}`                               | Version of the client OS                                                                                                                               |
+| `${attr.os.build}`                                 | Build number (e.g `14393.5501`) of the client OS (if on Windows)                                                                                       |
+
+The full list of node attributes can be obtained by running `nomad node status -verbose [node]`.
+
+Here are some examples of using node attributes and properties in a job file:
+
+```hcl
+job "docs" {
+  # This will constrain this job to only run on 64-bit clients.
+  constraint {
+    attribute = "${attr.cpu.arch}"
+    value     = "amd64"
+  }
+
+  # This will restrict the job to only run on clients with 4 or more cores.
+  # Note: you may also declare a resource requirement for CPU for a task.
+  constraint {
+    attribute = "${cpu.numcores}"
+    operator  = ">="
+    value     = "4"
+  }
+
+  # Only run this job on a memory-optimized AWS EC2 instance.
+  constraint {
+    attribute = "${attr.platform.aws.instance-type}"
+    value     = "m4.xlarge"
+  }
+}
+```
+
+## Environment Variables ((#interpreted_env_vars))
+
+The following are runtime environment variables that describe the environment
+the task is running in. These are only defined once the task has been placed on
+a particular node and as such can not be used in constraints.
+
+Environment variables should be enclosed in brackets `${...}` for
+interpolation or accessed using the `env` function inside the template
+block—`{{env "..."}}`
+
+### Dots in Variables ((#dots_in_vars))
+
+Nomad interprets dots in names as object notation. This causes names that have
+multiple consecutive dots to be considered invalid. For example, an environment
+variable named `invalid...name` cannot be interpolated using the standard
+`"${invalid...name}"` syntax. If you do, the parser will return an
+`Extra characters after interpolation expression` error. Nomad provides a
+variable—`env`—that can access any environment variable, regardless
+of its name, using index syntax.
+
+```hcl
+job "sample" {
+  datacenters = ["dc1"]
+  group "g1" {
+    task "redis" {
+
+      # Note: to set an environment variable with an invalid name, you must
+      # use the HCL2 map assignment syntax for `env`. Otherwise, the job spec
+      # parser will throw an `Argument or block definition required` error
+      env = {
+        "invalid...name" = "value1"
+        "valid.name"     = "value2"
+      }
+
+      driver = "docker"
+      config {
+        image  = "redis:7"
+        labels {
+          label1 = "${env["invalid...name"]}"
+          label2 = "${valid.name}"
+        }
+      }
+    }
+  }
+}
+```
+
+@include 'envvars.mdx'
diff --git a/content/nomad/v1.9.x/content/docs/schedulers.mdx b/content/nomad/v1.9.x/content/docs/schedulers.mdx
new file mode 100644
index 0000000000..e3cda48c85
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/schedulers.mdx
@@ -0,0 +1,97 @@
+---
+layout: docs
+page_title: Schedulers
+description: Learn how Nomad's service, batch, system, and system batch job schedulers enable flexible workloads.
+---
+
+# Schedulers
+
+This page provides conceptual information about Nomad service, batch, system,
+and system batch job schedulers.
+
+## Service
+
+The `service` scheduler is designed for scheduling long lived services that
+should never go down. As such, the `service` scheduler ranks a large portion
+of the nodes that meet the job's constraints and selects the optimal node to
+place a task group on. The `service` scheduler uses a best fit scoring algorithm
+influenced by Google's work on [Borg]. Ranking this larger set of candidate
+nodes increases scheduling time but provides greater guarantees about the
+optimality of a job placement, which given the service workload is highly
+desirable.
+
+Service jobs are intended to run until explicitly stopped by an operator. If a
+service task exits it is considered a failure and handled according to the job's
+[restart] and [reschedule] blocks.
+
+## Batch
+
+Batch jobs are much less sensitive to short term performance fluctuations and
+are short lived, finishing in a few minutes to a few days. Although the `batch`
+scheduler is very similar to the `service` scheduler, it makes certain
+optimizations for the batch workload. The main distinction is that after finding
+the set of nodes that meet the job's constraints it uses the power of two
+choices described in Berkeley's [Sparrow] scheduler to limit the number of nodes
+that are ranked.
+
+Batch jobs are intended to run until they exit successfully. Batch tasks that
+exit with an error are handled according to the job's [restart] and [reschedule]
+blocks.
+
+## System
+
+The `system` scheduler is used to register jobs that should be run on all
+clients that meet the job's constraints. The `system` scheduler is also invoked
+when clients join the cluster or transition into the ready state. This means
+that all registered `system` jobs will be re-evaluated and their tasks will be
+placed on the newly available nodes if the constraints are met.
+
+This scheduler type is extremely useful for deploying and managing tasks that
+should be present on every node in the cluster. Since these tasks are
+managed by Nomad, they can take advantage of job updating,
+service discovery, and more.
+
+The system scheduler will preempt eligible lower priority tasks running on a
+node if there isn't enough capacity to place a system job.  See [preemption]
+for details on how tasks that get preempted are chosen.
+
+Systems jobs are intended to run until explicitly stopped either by an operator
+or [preemption]. If a system task exits it is considered a failure and handled
+according to the job's [restart] block; system jobs do not have rescheduling.
+
+When used with node pools, system jobs run on all nodes of the pool used by the
+job. The built-in node pool `all` allows placing allocations on all clients in
+the cluster.
+
+## System Batch
+
+The `sysbatch` scheduler is used to register jobs that should be run to completion
+on all clients that meet the job's constraints. The `sysbatch` scheduler will
+schedule jobs similarly to the `system` scheduler, but like a `batch` job once a
+task exits successfully it is not restarted on that client.
+
+This scheduler type is useful for issuing "one off" commands to be run on every
+node in the cluster. Sysbatch jobs can also be created as [periodic] and [parameterized]
+jobs. Since these tasks are managed by Nomad, they can take advantage of job
+updating, service discovery, monitoring, and more.
+
+The `sysbatch` scheduler will preempt lower priority tasks running on a node if there
+is not enough capacity to place the job. See preemption details on how tasks that
+get preempted are chosen.
+
+Sysbatch jobs are intended to run until successful completion, explicitly stopped
+by an operator, or evicted through [preemption]. Sysbatch tasks that exit with an
+error are handled according to the job's [restart] block.
+
+ Like the `batch` scheduler, task groups in system batch jobs may have a `count`
+ greater than 1 to control how many instances are run. Instances that cannot be
+ immediately placed will be scheduled when resources become available,
+ potentially on a node that has already run another instance of the same job.
+
+[borg]: https://research.google.com/pubs/pub43438.html
+[parameterized]: /nomad/docs/job-specification/parameterized
+[periodic]: /nomad/docs/job-specification/periodic
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[restart]: /nomad/docs/job-specification/restart
+[reschedule]: /nomad/docs/job-specification/reschedule
+[sparrow]: https://cs.stanford.edu/~matei/papers/2013/sosp_sparrow.pdf
diff --git a/content/nomad/v1.9.x/content/docs/upgrade/index.mdx b/content/nomad/v1.9.x/content/docs/upgrade/index.mdx
new file mode 100644
index 0000000000..070ad21d27
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/upgrade/index.mdx
@@ -0,0 +1,259 @@
+---
+layout: docs
+page_title: 'Upgrade Nomad'
+sidebar_current: 'guides-upgrade'
+description: |-
+  Upgrade HashiCorp Nomad without causing an outage. Review the upgrade process for a new version, for moving from Nomad community edition to Nomad Enterprise, and for Raft protocol version three.
+---
+
+# Upgrade Nomad
+
+This page provides guidance on upgrading HashiCorp Nomad without causing an
+outage. Review the upgrade process for a new version, for moving from Nomad
+Community to Nomad Enterprise, and for Raft protocol version three.
+
+## Introduction
+
+Nomad is designed to be flexible and resilient when upgrading from one Nomad
+version to the next. Upgrades should cause neither a Nomad nor a service
+outage. However, there are some restrictions to be aware of before upgrading:
+
+- Nomad strives to be backward compatible for at least 2 point release, so
+  Nomad v1.7.x works with v1.5.x.
+
+  - Nomad does _not_ support downgrading at this time. Downgrading clients
+    requires draining allocations and removing the [data directory][data_dir].
+    Downgrading servers safely requires re-provisioning the cluster.
+
+  - New features are unlikely to work correctly until all nodes have been
+    upgraded.
+
+  - Check the [version upgrade details page][upgrade-specific] for important
+    changes and backward incompatibilities.
+
+- When upgrading a Nomad Client, if it takes longer than the
+  [`heartbeat_grace`][heartbeat_grace] (10s by default) period to restart, all
+  allocations on that node may be rescheduled.
+
+Nomad supports upgrading in place or by rolling in new servers:
+
+- In Place: The Nomad binary can be updated on existing hosts. Running
+  allocations will continue running uninterrupted.
+
+- Rolling: New hosts containing the new Nomad version may be added followed by
+  the removal of old hosts. The old nodes must be drained to migrate running
+  allocations to the new nodes.
+
+This guide describes both approaches.
+
+## Upgrade Process
+
+Once you have checked the [upgrade details for the new
+version][upgrade-specific], the upgrade process is as simple as updating the
+binary on each host and restarting the Nomad service.
+
+At a high level we complete the following steps to upgrade Nomad:
+
+- **Add the new version**
+- **Check cluster health**
+- **Remove the old version**
+- **Check cluster health**
+- **Upgrade clients**
+
+### 1. Add the new version to the existing cluster
+
+While it is possible to upgrade Nomad client nodes before servers, this guide
+recommends upgrading servers first as many new client features will not work
+until servers are upgraded.
+
+In a [federated cluster](/nomad/tutorials/manage-clusters/federation),
+new features are not guaranteed to work until all agents in a region and the
+server nodes in the authoritative region are upgraded.
+
+Whether you are replacing Nomad in place on existing systems or bringing up new
+servers you should make changes incrementally, verifying cluster health at each
+step of the upgrade.
+
+On a single server, install the new version of Nomad. You can do this by
+joining a new server to the cluster or by replacing or upgrading the binary
+locally and restarting the Nomad service.
+
+Note that if you have [`leave_on_terminate`][] or [`leave_on_interrupt`][] set,
+you should ensure you're using the expected signal for your upgrade process. For
+example, if you have `leave_on_terminate` set and you intend on updating a
+server in-place, you should `SIGINT` and not `SIGTERM` when shutting down the
+server before restarting it.
+
+### 2. Check cluster health
+
+[Monitor the Nomad logs][monitor] on the remaining servers to check that the
+new server has joined the cluster correctly.
+
+Run `nomad agent-info` on the new servers and check that the `last_log_index`
+is of a similar value to the other servers. This step ensures that changes have
+been replicated to the new server.
+
+```shell-session
+ubuntu@nomad-server-10-1-1-4:~$ nomad agent-info
+nomad
+  bootstrap = false
+  known_regions = 1
+  leader = false
+  server = true
+raft
+  applied_index = 53460
+  commit_index = 53460
+  fsm_pending = 0
+  last_contact = 54.512216ms
+  last_log_index = 53460
+  last_log_term = 1
+  last_snapshot_index = 49511
+  last_snapshot_term = 1
+  num_peers = 2
+...
+```
+
+Continue with the upgrades across the servers making sure to do a single Nomad
+server at a time. You can check state of the servers with [`nomad server members`][server-members], and the state of the client nodes with [`nomad node status`][node-status].
+
+### 3. Remove the old versions from servers
+
+If you are doing an in place upgrade on existing servers this step is not
+necessary as the version was changed in place.
+
+If you are doing an upgrade by adding new servers and removing old servers
+from the fleet you need to ensure that the server has left the fleet safely.
+
+1. Stop the service on the existing host
+2. On another server issue a `nomad server members` and check the status, if
+   the server is now in a left state you are safe to continue.
+3. If the server is not in a left state, issue a `nomad server force-leave <server id>`
+   to remove the server from the cluster.
+
+Monitor the logs of the other hosts in the Nomad cluster over this period.
+
+### 4. Check cluster health
+
+Use the same actions in step #2 above to confirm cluster health.
+
+### 5. Upgrade clients
+
+Following the successful upgrade of the servers you can now update your
+clients using a similar process as the servers. You may either upgrade clients
+in-place or start new nodes on the new version. See the [Workload Migration
+Guide](/nomad/tutorials/manage-clusters/node-drain) for instructions on how to migrate running
+allocations from the old nodes to the new nodes with the [`nomad node drain`](/nomad/docs/commands/node/drain) command.
+
+## Done
+
+You are now running the latest Nomad version. You can verify all
+Clients joined by running `nomad node status` and checking all the clients
+are in a `ready` state.
+
+## Upgrading to Nomad Enterprise
+
+Before upgrading servers to Nomad Enterprise versions 1.6.0 and later,
+you should validate your enterprise license with the
+[`nomad license inspect` command](/nomad/docs/commands/license/inspect)
+using the binary that you are upgrading to.
+See the [licensing FAQ](/nomad/docs/enterprise/license/faq)
+for more information.
+
+After that, the process of upgrading to a Nomad Enterprise version is identical to upgrading
+between versions of open source Nomad. The same guidance above should be
+followed and as always, prior to starting the upgrade please check the [specific
+version details](/nomad/docs/upgrade/upgrade-specific) page as some version
+differences may require specific steps.
+
+[data_dir]: /nomad/docs/configuration#data_dir
+[heartbeat_grace]: /nomad/docs/configuration/server#heartbeat_grace
+[monitor]: /nomad/docs/commands/monitor
+[node-status]: /nomad/docs/commands/node/status
+[server-members]: /nomad/docs/commands/server/members
+[upgrade-specific]: /nomad/docs/upgrade/upgrade-specific
+
+## Upgrading to Raft Protocol 3
+
+This section provides details on upgrading to Raft Protocol 3. Raft
+protocol version 3 requires Nomad running 0.8.0 or newer on all
+servers in order to work. Raft protocol version 2 will be removed in
+Nomad 1.4.0.
+
+To see the version of the Raft protocol in use on each server, use the
+`nomad operator raft list-peers` command.
+
+Note that the format of `peers.json` used for outage recovery is
+different when running with the latest Raft protocol. See [Manual
+Recovery Using
+peers.json](/nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson)
+for a description of the required format.
+
+When using Raft protocol version 3, servers are identified by their
+`node-id` instead of their IP address when Nomad makes changes to its
+internal Raft quorum configuration. This means that once a cluster has
+been upgraded with servers all running Raft protocol version 3, it
+will no longer allow servers running any older Raft protocol versions
+to be added.
+
+### Upgrading a Production Cluster to Raft Version 3
+
+For production raft clusters with 3 or more members, the easiest way
+to upgrade servers is to have each server leave the cluster, upgrade
+its [`raft_protocol`] version in the `server` block (if upgrading to
+a version lower than v1.3.0), and then add it back. Make sure the new
+server joins successfully and that the cluster is stable before
+rolling the upgrade forward to the next server. It's also possible to
+stand up a new set of servers, and then slowly stand down each of the
+older servers in a similar fashion.
+
+For in-place raft protocol upgrades, perform the following for each
+server, leaving the leader until last to reduce the chance of leader
+elections that will slow down the process:
+
+* Stop the server.
+* Run `nomad server force-leave $server_name`.
+* If the upgrade is for a Nomad version lower than v1.3.0, update the
+  [`raft_protocol`] in the server's configuration file to `3`.
+* Restart the server.
+* Run `nomad operator raft list-peers` to verify that the
+  `RaftProtocol` for the server is now `3`.
+* On the server, run `nomad agent-info` and check that the
+  `last_log_index` is of a similar value to the other servers. This
+  step ensures that raft is healthy and changes are replicating to the
+  new server.
+
+### Upgrading a Single Server Cluster to Raft Version 3
+
+If you are running a single Nomad server, restarting it in-place will
+result in that server not being able to elect itself as a leader. To
+avoid this, create a new [`peers.json`][peers-json] file before
+restarting the server with the new configuration. If you have `jq`
+installed you can run the following script on the server's host to
+write the correct `peers.json` file:
+
+```
+#!/usr/bin/env bash
+
+NOMAD_DATA_DIR=$(nomad agent-info -json | jq -r '.config.DataDir')
+NOMAD_ADDR=$(nomad agent-info -json | jq -r '.stats.nomad.leader_addr')
+NODE_ID=$(cat "$NOMAD_DATA_DIR/server/node-id")
+
+cat <<EOF > "$NOMAD_DATA_DIR/server/raft/peers.json"
+[
+  {
+    "id": "$NODE_ID",
+    "address": "$NOMAD_ADDR",
+    "non_voter": false
+  }
+]
+EOF
+```
+
+After running this script, if the upgrade is for a Nomad version lower
+than v1.3.0, update the [`raft_protocol`] in the server's
+configuration to `3` and restart the server.
+
+[peers-json]: /nomad/tutorials/manage-clusters/outage-recovery#manual-recovery-using-peersjson
+[`raft_protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`leave_on_interrupt`]: /nomad/docs/configuration#leave_on_interrupt
+[`leave_on_terminate`]: /nomad/docs/configuration#leave_on_terminate
diff --git a/content/nomad/v1.9.x/content/docs/upgrade/upgrade-specific.mdx b/content/nomad/v1.9.x/content/docs/upgrade/upgrade-specific.mdx
new file mode 100644
index 0000000000..7a78c0bbca
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/upgrade/upgrade-specific.mdx
@@ -0,0 +1,2271 @@
+---
+layout: docs
+page_title: Upgrade Guides
+description: |-
+  Review upgrade details for specific versions of Nomad.
+---
+
+# Upgrade Guides
+
+The [upgrading page](/nomad/docs/upgrade) covers the details of doing a standard
+upgrade. However, specific versions of Nomad may have more details provided for
+their upgrades as a result of new features or changed behavior. This page is
+used to document those details separately from the standard upgrade flow.
+
+## Nomad 1.9.5
+
+#### CNI plugins
+
+Nomad 1.9.5 includes a bug fix for restoring allocation networking after a
+client host reboot. This fix requires recent versions of the CNI reference
+plugins (minimum 1.2.0) and will fallback to the existing behavior if the CNI
+reference plugins cannot support the fix.
+
+We recommend installing the CNI reference plugins from the [CNI project release
+page](https://github.com/containernetworking/plugins/releases) rather than your
+Linux distribution's package manager.
+
+## Nomad 1.9.4
+
+#### Security updates to default deny lists
+
+In Nomad 1.9.4, the default `function_denylist` includes `executeTemplate`, as
+a measure to prevent accidental or malicious infinitely recursive execution.
+Users that require `executeTemplate` should update their
+[configuration](/nomad/docs/job-specification/template#function_denylist).
+
+Additionally, the [default client env deny
+list](/nomad/docs/configuration/client#env-denylist) includes more environment
+variables. Users who need some of these secure environment variables passed to
+their tasks should consult the list and overwrite it in the configuration.
+
+## Nomad 1.9.3
+
+In Nomad 1.9.3, the mechanism used for calculating when objects are eligible
+for garbage collection changes to a clock-based one. This has two consequences.
+First, it allows to set arbitrarily long GC intervals. Second, it requires that
+Nomad servers are kept roughly in sync time-wise, because GC can originate in a
+follower.
+
+Nomad 1.9.2 contained a bug that could drop all cluster state on upgrade and
+has been removed from downloads.
+
+## Nomad 1.9.0
+
+#### Dropped support for older clients
+
+Nomad 1.9.0 removes support for Nomad client agents older than 1.6.0. Older
+nodes fail heartbeats. Nomad servers mark the workloads on those nodes
+as lost and reschedule them normally according to the job's [reschedule][]
+block.
+
+#### Keyring In Raft
+
+Nomad 1.9.0 stores keys used for signing Workload Identity and encrypting
+Variables in Raft, instead of storing key material in the external
+keystore. When using external KMS or Vault transit encryption for the
+[`keyring`](/nomad/docs/configuration/keyring) provider, the key encryption key
+(KEK) is stored outside of Nomad and no cleartext key material exists on disk.
+When using the default AEAD provider, the key encryption key (KEK) is stored in
+Raft alongside the encrypted data encryption keys (DEK).
+
+Nomad automatically migrates the key storage for all key material on the
+first [`root_key_gc_interval`][] after all servers are upgraded to 1.9.0. The
+existing on-disk keystore is required to restore servers from older snapshots,
+so you should continue to back up the on-disk keystore until you no longer need
+those older snapshots.
+
+#### Support for HCLv1 removed
+
+Nomad 1.9.0 no longer supports the HCLv1 format for job specifications. Using
+the `-hcl1` option for the `job run`, `job plan`, and `job validate` commands
+will no longer work.
+
+One common use of `-hcl1` was when specifying [Docker
+labels](/nomad/docs/drivers/docker#labels) with dots in their keys such as for
+DataDog autodiscovery:
+
+```hcl
+labels {
+  "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+  "com.datadoghq.ad.init_configs" = "[{}]"
+  # ...
+}
+```
+
+Quoted keys are invalid in HCLv2 blocks and must be specified with a
+list-of-maps syntax:
+
+```hcl
+labels = [
+  {
+    "com.datadoghq.ad.check_names"  = "[\"openmetrics\"]"
+    "com.datadoghq.ad.init_configs" = "[{}]"
+    # ...
+  }
+]
+```
+
+## Nomad 1.8.4
+
+#### Default Docker `infra_image` changed
+
+Due to the deprecation of the third-party `gcr.io` registry, the default Docker
+[`infra_image`][] is now `registry.k8s.io/pause-<arch>:3.3`. If you do not
+override the default, clients using the `docker` driver will make outbound
+requests to the new registry.
+
+## Nomad 1.8.3
+
+#### Nomad keyring rotation
+
+In Nomad 1.8.3, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.8.2
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.8.2, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`. We made
+this change as a result of regressions introduced by mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.8.2 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment. We made this change as a result of regressions introduced by
+mitigations for
+[HCSEC-2024-03](https://discuss.hashicorp.com/t/hcsec-2024-03-nomad-vulnerable-to-arbitrary-write-through-symlink-attack/62602).
+
+## Nomad 1.8.1
+
+<EnterpriseAlert inline />
+
+Nomad Enterprise 1.8.1 includes an updated version of the Sentinel library. Users
+that have built custom Sentinel plugins must recompile them using an SDK
+supporting Sentinel Plugin Protocol Version 3. Consult the Sentinel
+[SDK Compatibility Matrix](https://github.com/hashicorp/sentinel-sdk?tab=readme-ov-file#sdk-compatibility-matrix) for appropriate Sentinel SDK versions.
+
+## Nomad 1.8.0
+
+#### Deprecated Disconnect Fields
+
+Nomad 1.8.0 introduces a `disconnect` block meant to group all the configuration
+options related to disconnected client's and server's behavior, causing the
+deprecation of the fields `stop_after_client_disconnect`, `max_client_disconnect`
+and `prevent_reschedule_on_lost`. This block also introduces new options for
+allocations reconciliation if the client regains connectivity.
+
+#### CNI Constraints
+
+In Nomad 1.8.0, jobs with `bridge` networking will have constraints added during
+job submit that require CNI plugins to be present on the node. Nodes have
+fingerprinted the available CNI plugins starting in Nomad 1.5.0.
+
+If you are upgrading from Nomad 1.5.0 or later to 1.8.0 or later, there's
+nothing additional for you to do. It's not recommended to skip more than 2
+versions of Nomad. But if you upgrade from earlier than 1.5.0 to 1.8.0 or later,
+you will need to ensure that clients have been upgraded before submitting any
+jobs that use `bridge` networking.
+
+#### Removal of `raw_exec` option `no_cgroups`
+
+In Nomad 1.7.0 the `raw_exec` plugin option for `no_cgroups` became ineffective.
+Starting in Nomad 1.8.0 attempting to set the `no_cgroups` in `raw_exec` plugin
+configuration will result in an error when starting the agent.
+
+## Nomad 1.7.11
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.7.11, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.7.10
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.7.10, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.7.10 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.7.2
+
+Nomad 1.7.2 fixes a critical bug in CPU fingerprinting in Nomad 1.7.0 and
+1.7.1. You should not install Nomad 1.7.0 or 1.7.1 and instead install the
+latest Nomad 1.7.x version.
+
+## Nomad 1.7.0
+
+<Warning>
+
+Nomad 1.7.0 contains a critical bug in keyring replication. You should not
+install Nomad 1.7.0 and instead install the latest Nomad 1.7.x version.
+
+</Warning>
+
+#### Keyring Replication Failure After Leader Election
+
+Nomad 1.7.0 introduced new RSA keys to the keyring for use in signing workload
+identities. These keys were not correctly replicated from leader to
+followers. This results in all workload identity verification failing after a
+leader election.
+
+This bug was fixed in Nomad 1.7.1.
+
+#### Vault Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a task's [Workload Identity][] to
+authenticate to Vault and obtain a Vault token specific to the task.
+
+The existing workflow using a Vault token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`vault.policies`][] field is also deprecated and will work
+only with the existing workflow. Instead, you should configure a suitable Vault
+role and use that.
+
+The following agent configuration fields are deprecated:
+- [`vault.allow_unauthenticated`][] will be removed in Nomad 1.10. Tasks will use
+  the workload identity without the user supplying a Vault token.
+- [`vault.task_token_ttl`][] will be removed in Nomad 1.10. With workload
+  identity, tasks will receive their TTL configuration from the Vault role.
+- [`vault.token`][] will be removed in Nomad 1.10. Nomad agents will no longer
+  make requests to authenticated endpoints except with a task's workload
+  identity.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Vault to work with workload identity. See [Migrating to Using Workload
+Identity with Vault][] for more details.
+
+#### Consul Integration Changes
+
+Starting in Nomad 1.7, Nomad clients will use a service's or task's [Workload
+Identity][] to authenticate to Consul and obtain a Consul token specific to the
+workload.
+
+The existing workflow using a Consul token provided in either the agent
+configuration or at the time of job submission is deprecated and will be removed
+in Nomad 1.10. The [`consul.allow_unauthenticated`][] agent configuration field
+will be removed in Nomad 1.10. Tasks will use the workload identity without the
+user supplying a Consul token.
+
+Before upgrading to Nomad 1.10 you will need to have configured authentication
+with Consul to work with workload identity. See [Migrating to Using Workload
+Identity with Consul][] for more details.
+
+#### RS256 JWT Signing Algorithm Support
+
+Prior to Nomad 1.7, workload identity JWTs were signed with the `EdDSA`
+algorithm. While `EdDSA` has numerous advantages as a signing algorithm, most
+third parties that accept JWTs expect the `RS256` signing algorithm to be used.
+
+Therefore starting in Nomad 1.7 *new* signing keys will generate an RSA key and
+sign workload identities with the `RS256` signing algorithm.
+
+Before setting up third party authentication methods to use workload
+identities, it is recommended to run [`nomad operator root keyring
+rotate`](/nomad/docs/commands/operator/root/keyring-rotate) to ensure you
+generate a new RSA key.
+
+To verify an RSA key is present you may check the [`/.well-known/jwks.json`
+endpoint](/nomad/api-docs/operator/keyring#list-active-public-keys) on any
+Nomad agent. If you see `"kty": "RSA"`, then an RSA key exists and you do not
+need to rotate keys.
+
+New Nomad clusters will use RSA by default and are not affected.
+
+#### CPU Fingerprinting Changes
+
+Starting in Nomad 1.7, Nomad clients improve the accuracy of detected CPU
+performance metrics. The fingerprinter now takes into account heterogeneous core
+types on applicable processors. In addition, Nomad will attempt to detect and
+use the base frequency of the processor rather than the turbo frequency when
+calculating the total available CPU bandwidth. The net result of these behaviors
+is that the calculated total CPU bandwidth available on a node may change when
+upgrading to Nomad 1.7. Operators are encouraged to ensure planned capacity
+meets expectations before upgrading. The [cpu concepts][cpu] documentation
+contains guidance in understanding how Nomad detects CPU metrics.
+
+#### CPU EC2 Detection Changes
+
+Prior to Nomad 1.7, Nomad clients embedded a large lookup table of CPU
+performance data for every EC2 instance type. In 1.7 and later Nomad instead
+gathers this data by executing the `dmidecode` command. The `dmidecode` package
+must be installed manually on some Linux distributions before the Nomad agent
+is started.
+
+#### CPU Core Isolation
+
+Starting in Nomad 1.7, Nomad tasks that specify CPU resources using the `cores`
+attribute will be restricted to using only the CPU cores assigned to them. In
+previous versions of Nomad these tasks could also make use of other non-reserved
+CPU cores. However this feature would cause severe performance problems for
+the Linux kernel as the number of tasks increased. Operators are encouraged
+to ensure tasks making use of the `cores` attribute are given sufficient CPU
+resources before upgrading.
+
+#### The `distinct_hosts` Constraint Now Honors Namespaces
+
+Nomad 1.7.0 changes the behavior of the [`distinct_hosts`][] constraint such that
+namespaces are taken into account when choosing feasible clients for allocation
+placement. The previous, less-expected behavior would cause **any** job with the
+same name running on a client to cause that node to be considered infeasible.
+
+This change allows workloads that formerly did not colocate to be scheduled
+onto the same client when they are in different namespaces. To prevent this,
+consider using [node pools] and constrain the jobs with a [`distinct_property`][]
+constraint over [`${node.pool}`][node_attributes].
+
+#### Loading Binaries from `plugin_dir` Without Configuration
+
+Starting with Nomad 1.7.0, loading plugins that are not referenced in the agent
+configuration file is deprecated. Future versions of Nomad will only load
+plugins that have a corresponding [`plugin`](/nomad/docs/configuration/plugin)
+block in the agent configuration file.
+
+#### Changes to `raw_exec`
+
+The `raw_exec` task driver now enforces memory limits via cgroups on Linux
+platforms similar to the `exec` and `docker` task drivers. The driver does
+support memory [oversubscription][oversub], which can be configured in such a
+way to nearly replicate the previously unlimited behavior.
+
+The `no_cgroups` configuration option no longer has any effect. Previously,
+setting `no_cgroups` would disable the mechanism where Nomad used the freezer
+cgroup to halt the process group of a Task before issuing a kill signal to each
+process. Starting in Nomad 1.7.0 this behavior is always enabled (and a similar
+mechanism has always been enabled on cgroups v2 systems).
+
+## Nomad 1.6.14
+
+<EnterpriseAlert inline />
+
+#### Nomad keyring rotation
+
+In Nomad 1.6.14, the Nomad root keyring will prepublish keys at half the
+`root_key_rotation_threshold` and promote them to active once the
+`root_key_rotation_threshold` has passed. The `nomad operator root keyring
+rotate` command now requires one of two arguments: `-prepublish <duration>` to
+prepublish a key or `-now` to rotate immediately. We recommend using
+`-prepublish` to avoid outages from workload identities used to log into
+external services such as Vault or Consul.
+
+## Nomad 1.6.13
+
+<EnterpriseAlert inline />
+
+#### New `windows_allow_insecure_container_admin` configuration option for Docker driver
+
+In 1.6.13, Nomad will refuse to run jobs that use the Docker driver on Windows
+with [Process Isolation][] that run as `ContainerAdmin`. This is in order to
+provide a more secure environment for these jobs, and this behavior can be
+overridden by setting the new `windows_allow_insecure_container_admin` Docker
+plugin configuration option to `true` or by setting `privileged=true`.
+
+#### New default isolation mode for Docker on Windows
+
+Nomad 1.6.13 changes the default isolation mode for Docker tasks on Windows from
+`process` to `hyperv`, since `hyperv` provides a much more secure execution
+environment.
+
+## Nomad 1.6.0
+
+#### Enterprise License Validation with BuildDate
+
+Nomad Enterprise 1.6.0 now compares license `ExpirationTime` with the Nomad binary's `BuildDate`,
+rather than comparing the sometimes more lenient license `TerminationTime` with `time.Now()`.
+See the [licensing FAQ](/nomad/docs/v1.6.x/enterprise/license/faq) for more info,
+but most relevant here is that you should run the new
+[`nomad license inspect`](/nomad/docs/commands/license/inspect) command
+before trying to upgrade your Enterprise servers to v1.6.0 or higher.
+
+#### Job Evaluate API Endpoint Requires `submit-job` Instead of `read-job`
+
+Nomad 1.6.0 updated the ACL capability requirement for the job evaluate
+endpoint from `read-job` to `submit-job` to better reflect that this operation
+writes state to Nomad. This endpoint is used by the `nomad job eval` CLI
+command and so the ACL requirements changed for the command as well. Users that
+called this endpoint or used this command using tokens with just the `read-job`
+capability or the `read` policy must update their tokens to use the
+`submit-job` capability or the `write` policy.
+
+#### Exec Driver Requires New Capability for mlock
+
+Nomad 1.6.0 updated the `exec` task driver to maintain the max memory locked
+limit set by the host system. In earlier versions of Nomad this limit was
+*unset* unintentionally.
+
+In practice this means that `exec` tasks such as Vault which use the `mlock`
+system call will now need to explicitly add the `ipc_lock` capability.
+
+First [allow the `ipc_lock` capability in the Client
+configuration][allow_caps_exec]:
+
+```hcl
+plugin "exec" {
+  config {
+    allow_caps = ["audit_write", "chown", "dac_override", "fowner", "fsetid",
+      "kill", "mknod", "net_bind_service", "setfcap", "setgid", "setpcap",
+      "setuid", "sys_chroot", "ipc_lock"]
+  }
+}
+```
+
+Then [add the `ipc_lock` capability to the exec task][cap_add_exec] that uses
+`mlock`:
+
+```hcl
+task "vault" {
+  driver = "exec"
+
+  config {
+    cap_add = ["ipc_lock"]
+
+    # ... other task configuration
+  }
+
+# ... rest of jobspec
+```
+
+These additions are backward compatible with Nomad v1.5, so Clients and Jobs
+should be updated prior to upgrading to Nomad v1.6.
+
+See [#17780](https://github.com/hashicorp/nomad/issues/17780) for details.
+
+#### Namespace ACL policies require a label
+
+Nomad 1.6.0 does not allow ACL policies for namespaces without a label. Prior
+to this version, ACL policies for namespaces were allowed to be defined
+without a label, and the documented behavior in this case was that the policy
+would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+#### Command `nomad tls cert create` flag `-cluster-region` deprecated
+
+Nomad 1.6.0 will deprecate the command `nomad tls cert create` flag `-cluster-region`
+in favour of using the standard flag `-region`. The `-cluster-region` flag
+will be removed in Nomad 1.7.0
+
+#### 32-bit Intel Builds Deprecated
+
+Starting with Nomad 1.6.0, HashiCorp will no longer release 32-bit Intel builds
+of Nomad and Nomad Enterprise (the builds named `windows_386` and
+`linux_386`). Bug fixes will continue to be backported to the 1.5.x and 1.4.x
+versions so long as those major versions are still supported.
+
+The 32-bit ARM build (`linux_arm` for the armhf architecture) is deprecated and
+may be removed in a future major version of Nomad. The 32-bit ARM build is not
+tested and may include bugs around platform-specific integer sizes. Using 64-bit
+builds for small form-factor hosts such as the RaspberryPi is strongly
+recommended.
+
+## Nomad 1.5.7, 1.4.11
+
+#### Namespace ACL policies require a label
+
+Nomad 1.5.7 and 1.4.11 do not allow ACL policies for namespaces without a
+label. Prior to these versions, ACL policies for namespaces were allowed to be
+defined without a label, and the documented behavior in this case was that the
+policy would be applied to the `default` namespace.
+
+A bug in this logic caused the policy to be incorrectly applied to a different
+namespace. For example, the policy below would be applied to a namespace called
+`policy` instead of `default`.
+
+```hcl
+namespace {
+  policy = "read"
+}
+```
+
+To avoid further confusion and potential security incidents, this functionality
+was removed and now all namespace policies are required to have a label.
+
+Tokens currently attached to an invalid policy will stop working after the
+upgrade, so you should fix invalid policies to have an explicit namespace label
+before upgrading Nomad.
+
+After the policies are fixed, the existing tokens with those policies will
+continue to work and do not need to be regenerated.
+
+## Nomad 1.5.5
+
+Nomad 1.5.5 fixed a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+`logs.enabled` field introduced in 1.5.4 is now deprecated and has been replaced
+by a `logs.disabled` field that defaults to false. The `logs.enabled` field value
+will be ignored in 1.5.5 and will be removed in Nomad 1.6.0.
+
+## Nomad 1.5.4
+
+Nomad 1.5.4 included a bug where allocations that are rescheduled for jobs
+registered before the upgrade would no longer collect allocation logs. The
+client will emit debug-level logs like the following:
+
+```
+client.alloc_runner.task_runner.task_hook: log collection is disabled by task
+```
+
+You should avoid this version of Nomad and instead install the latest version of
+Nomad 1.5. If you have already upgraded to Nomad 1.5.4, upgrading to Nomad 1.5.5
+will restore logging collection when clients are restarted as part of the
+upgrade process.
+
+## Nomad 1.5.1
+
+#### Artifact Download Regression Fix
+
+Nomad 1.5.1 reverts a behavior of 1.5.0 where artifact downloads were executed
+as the `nobody` user on compatible Linux systems. This was done optimistically
+as defense against compromised artifact endpoints attempting to exploit the
+Nomad Client or tools it uses to perform downloads such as git or mercurial.
+Unfortunately running the child process as any user other than root is not
+compatible with the advice given in Nomad's [security hardening guide][hard_guide]
+which calls for a specific directory tree structure making such operation impossible.
+
+Other changes to artifact downloading remain - they are executed as a child
+process of the Nomad agent, and on modern Linux systems make use of the Kernel
+landlock feature to restrict filesystem access from that process.
+
+## Nomad 1.5.0
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.5.0 introduced a regression to the way the Docker driver reconciles
+dangling containers. This meant pause containers would be erroneously removed,
+even though the allocation was still running. This would not affect the running
+allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+#### Artifact Download Sandboxing
+
+Nomad 1.5.0 changes the way [artifacts] are downloaded when specifying an `artifact`
+in a task configuration. Previously the Nomad Client would download artifacts
+in-process. External commands used to facilitate the download (e.g. `git`, `hg`)
+would be run as `root`, and the resulting payload would be owned as `root` in the
+allocation's task directory.
+
+In an effort to improve the resilience and security model of the Nomad Client,
+in 1.5.0 artifact downloads occur in a sub-process. Where possible, that
+sub-process is run as the `nobody` user, and on modern Linux systems will
+be isolated from the filesystem via the kernel's [landlock] capability.
+
+Operators are encouraged to ensure jobs making use of artifacts continue to work
+as expected. In particular, git-ssh users will need to make sure the system-wide
+`/etc/ssh/ssh_known_hosts` file is populated with any necessary remote hosts.
+Previously, Nomad's documentation suggested configuring
+`/root/.ssh/known_hosts` which would apply only to the `root` user.
+
+The artifact downloader no longer inherits all environment variables available
+to the Nomad Client. The downloader sub-process environment is set as follows on
+Linux / macOS:
+
+```
+PATH=/usr/local/bin:/usr/bin:/bin
+TMPDIR=<path to task dir>/tmp
+```
+
+and as follows on Windows:
+
+```
+TMP=<path to task dir>\tmp
+TEMP=<path to task dir>\tmp
+PATH=<inherit $PATH>
+HOMEPATH=<inherit $HOMEPATH>
+HOMEDRIVE=<inherit $HOMEDRIVE>
+USERPROFILE=<inherit $USERPROFILE>
+```
+
+Configuration of the artifact downloader should happen through the [`options`][artifact_params]
+and [`headers`][artifact_params] fields of the `artifact` block. For backwards
+compatibility, the sandbox can be configured to inherit specified environment variables
+from the Nomad client by setting [`set_environment_variables`][artifact_env].
+
+The use of filesystem isolation can be disabled in Client configuration by
+setting [`disable_filesystem_isolation`][artifact_fs_isolation].
+
+#### Artifact Decompression Limits
+
+Nomad 1.5.0 now sets default limits around artifact decompression. A single artifact
+payload is now limited to 100GB and 4096 files when decompressed. An artifact that
+exceeds these limits during decompression will cause the artifact downloader to
+fail. These limits can be adjusted or disabled in the client artifact configuration
+by setting [`decompression_size_limit`][decompression_size_limit] and
+[`decompression_file_count_limit`][decompression_file_count_limit].
+
+#### Datacenter Wildcards
+
+In Nomad 1.5.0, the
+[`datacenters`](/nomad/docs/job-specification/job#datacenters) field for a job
+accepts wildcards for multi-character matching. For example, `datacenters =
+["dc*"]` will match all datacenters that start with `"dc"`. The default value
+for `datacenters` is now `["*"]`, so the field can be omitted.
+
+The `*` character is no longer a legal character in the
+[`datacenter`](/nomad/docs/configuration#datacenter) field for an agent
+configuration. Before upgrading to Nomad 1.5.0, you should first ensure that
+you've updated any jobs that currently have a `*` in their datacenter name and
+then ensure that no agents have this character in their `datacenter` field name.
+
+#### Server `rejoin_after_leave` (default: `false`) now enforced
+
+All Nomad versions prior to v1.5.0 have incorrectly ignored the Server
+[`rejoin_after_leave`] configuration option. This bug has been fixed in Nomad
+version v1.5.0.
+
+Previous to v1.5.0 the behavior of Nomad `rejoin_after_leave` was always `true`,
+regardless of Nomad server configuration, while the documentation incorrectly
+indicated a default of `false`.
+
+Cluster operators should be aware that explicit `leave` events (such as `nomad
+server force-leave`) will now result in behavior which matches this
+configuration, and should review whether they were inadvertently relying on the
+buggy behavior.
+
+#### Changes to eval broker metrics
+
+The metric `nomad.nomad.broker.total_blocked` has been changed to
+`nomad.nomad.broker.total_pending`. This state refers to internal state of the
+leader's broker, and this is easily confused with the unrelated evaluation
+status `"blocked"` in the Nomad API.
+
+#### Deprecated gossip keyring commands removed
+
+The commands `nomad operator keyring`, `nomad keyring`, `nomad operator keygen`,
+and `nomad keygen` used to manage the gossip keyring were marked as deprecated
+in Nomad 1.4.0. In Nomad 1.5.0, these commands have been removed. Use the `nomad
+operator gossip keyring` commands to manage the gossip keyring.
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.5.0 only delete evaluations and allocations of batch jobs
+that are explicitly stopped which can lead to unbounded memory growth of Nomad
+when the batch job is executed multiple times.
+
+Nomad 1.5.0 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.5, 1.3.10
+
+#### Pause Container Reconciliation Regression
+
+Nomad 1.4.5 and 1.3.10 introduced a regression to the way the Docker driver
+reconciles dangling containers. This meant pause containers would be erroneously
+removed, even though the allocation was still running. This would not affect the
+running allocation, but does cause it to fail if it needs to restart. An immediate
+workaround is to disable
+[dangling container reconciliation][dangling_container_reconciliation].
+
+## Nomad 1.4.4, 1.3.9
+
+#### Garbage collection of evaluations and allocations for batch job
+
+Versions prior to 1.4.4 and 1.3.9 only delete evaluations and allocations of
+batch jobs that are explicitly stopped which can lead to unbounded memory
+growth of Nomad when the batch job is executed multiple times.
+
+Nomad 1.4.4 and 1.3.9 introduces a new server configuration
+[`batch_eval_gc_threshold`](/nomad/docs/configuration/server#batch_eval_gc_threshold)
+to control how allocations and evaluations for batch jobs are collected.
+
+The default threshold is `24h`. If you need to access completed allocations for
+batch jobs that are older than 24h you must increase this value when upgrading
+Nomad.
+
+## Nomad 1.4.0
+
+#### Possible Panic During Upgrades
+
+Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
+created, which writes a new raft entry. Users have reported that the keyring
+initialization can cause a panic on older servers during upgrades. Following the
+documented [upgrade process][] closely will reduce the risk of this panic. But
+if a server with version 1.4.0 becomes leader while servers with versions before
+1.4.0 are still in the cluster, the older servers will panic.
+
+The most likely scenario for this is if the leader is still on a version before
+1.4.0 and is netsplit from the rest of the cluster or the server is restarted
+without upgrading, and one of the 1.4.0 servers becomes the leader.
+
+You can recover from the panic by immediately upgrading the old servers. This
+bug was fixed in Nomad 1.4.1.
+
+#### Raft Protocol Version 2 Unsupported
+
+Raft protocol version 2 was deprecated in Nomad v1.3.0, and is being removed
+in Nomad v1.4.0. In Nomad 1.3.0, the default raft protocol version was updated
+to version 3, and in Nomad 1.4.0 Nomad requires the use of raft protocol version
+3. If [`raft_protocol`] version is explicitly set, it must now be set to `3`.
+For more information see the [Upgrading to Raft Protocol 3] guide.
+
+#### Audit logs filtering logic changed
+
+Audit Log filtering in previous versions of Nomad handled `stages` and
+`operations` filters as `OR` filters. If _either_ condition was met, the logs
+would be filtered. As of 1.4.0, `stages` and `operations` are treated as `AND
+filters`. Logs will only be filtered if all filter conditions match.
+
+#### Prevent Overlapping New Allocations with Stopping Allocations
+
+Prior to Nomad 1.4.0 the scheduler would consider the resources used by
+allocations that are in the process of stopping to be free for new allocations
+to use. This could cause newer allocations to crash when they try to use TCP
+ports or memory used by an allocation in the process of stopping. The new and
+stopping [allocations would "overlap" improperly.][alloc_overlap]
+
+[Nomad 1.4.0 fixes this behavior][gh_10446] so that an allocation's resources
+are only considered free for reuse once the client node the allocation was
+running on reports it has stopped. Technically speaking: only once the
+`Allocation.ClientStatus` has reached a terminal state (`complete`, `failed`,
+or `lost`).
+
+Despite this being a bug fix, it is considered a significant enough change in
+behavior to reserve for a major Nomad release and *not* be backported. Please
+report any negative side effects encountered as [new
+issues.][gh_issue]
+
+#### `nomad eval status -json` Without Evaluation ID Removed
+
+Using `nomad eval status -json` without providing an evaluation ID was
+deprecated in Nomad 1.2.4 with the intent to remove in Nomad 1.4.0. This option
+has been removed. You can use `nomad eval list` to get a list of evaluations and
+can use `nomad eval list -json` to get that list in JSON format. The `nomad eval
+status <eval ID>` command will format a specific evaluation in JSON format if
+the `-json` flag is provided.
+
+#### Removing Vault/Consul from Clients
+
+Nomad clients no longer have their Consul and Vault fingerprints cleared when
+connectivity is lost with Consul and Vault. To intentionally remove Consul and
+Vault from a client node, you will need to restart the Nomad client agent.
+
+#### Numeric Operand Comparisons in Constraints
+
+Prior to Nomad 1.4.0 the `<, <=, >, >=` operators in a constraint would always
+compare the operands lexically. This behavior has been changed so that the comparison
+is done numerically if both operands are integers or floats.
+
+## Nomad 1.3.3
+
+Environments that don't support the use of [`uid`][template_uid] and
+[`gid`][template_gid] in `template` blocks, such as Windows clients, may
+experience task failures with the following message after upgrading to Nomad
+1.3.3:
+
+```
+Template failed: error rendering "(dynamic)" => "...": failed looking up user: managing file ownership is not supported on Windows
+```
+
+It is recommended to avoid this version of Nomad in such environments.
+
+## Nomad 1.3.2, 1.2.9, 1.1.15
+
+#### Client `max_kill_timeout` now enforced
+
+Nomad versions since v0.9 have incorrectly ignored the Client [`max_kill_timeout`][max_kill_timeout]
+configuration option. This bug has been fixed in Nomad versions v.1.3.2,
+v1.2.9, and v1.1.15. Job submitters should be aware that a Task's [`kill_timeout`][kill_timeout]
+will be reduced to the Client's `max_kill_timeout` if the value exceeds the maximum.
+
+## Nomad 1.3.1, 1.2.8, 1.1.14
+
+#### Default `artifact` limits
+
+Nomad 1.3.1, 1.2.8, and 1.1.14 introduced mechanisms to limit the size of
+`artifact` downloads and how long these operations can take. The limits are
+defined in the new [`artifact`client configuration][client_artifact] and have
+predefined default values.
+
+While the defaults set are fairly large, it is recommended to double-check them
+prior to upgrading your Nomad clients to make sure they fit your needs.
+
+## Nomad 1.3.0
+
+#### Raft Protocol Version 2 Deprecation
+
+Raft protocol version 2 will be removed from Nomad in the next major
+release of Nomad, 1.4.0.
+
+In Nomad 1.3.0, the default raft protocol version has been updated to
+3. If the [`raft_protocol`] version is not explicitly set, upgrading a
+server will automatically upgrade that server's raft protocol. See the
+[Upgrading to Raft Protocol 3] guide.
+
+#### Client State Store
+
+The client state store will be automatically migrated to a new schema
+version when upgrading a client.
+
+Downgrading to a previous version of the client after upgrading it to
+Nomad 1.3 is not supported. To downgrade safely, users should drain
+all tasks from the Nomad client and erase its data directory.
+
+#### CSI Plugins
+
+The client filesystem layout for CSI plugins has been updated to
+correctly handle the lifecycle of multiple allocations serving the
+same plugin. Running plugin tasks will not be updated after upgrading
+the client, but it is recommended to redeploy CSI plugin jobs after
+upgrading the cluster.
+
+The directory for plugin control sockets will be mounted from a new
+per-allocation directory in the client data dir. This will still be
+bind-mounted to `csi_plugin.mount_config` as in versions of Nomad
+prior to 1.3.0.
+
+The volume staging directory for new CSI plugin tasks will now be
+mounted to the task's `NOMAD_TASK_DIR` instead of the
+`csi_plugin.mount_config`.
+
+#### Raft leadership transfer on error
+
+Starting with Nomad 1.3.0, when a Nomad server is elected the Raft leader but
+fails to complete the process to start acting as the Nomad leader it will
+attempt to gracefully transfer its Raft leadership status to another eligible
+server in the cluster. This operation is only supported when using Raft
+Protocol Version 3.
+
+#### Server Raft Database
+
+The server raft database in `raft.db` will be automatically migrated to a new
+underlying implementation provided by `go.etcd.io/bbolt`. Downgrading to a previous
+version of the server after upgrading it to Nomad 1.3 is not supported. Like with
+any Nomad upgrade it is recommended to take a snapshot of your database prior to
+upgrading in case a downgrade becomes necessary.
+
+The new database implementation enables a new server configuration option for
+controlling the underlying freelist-sync behavior. Clusters experiencing extreme
+disk IO on servers may want to consider disabling freelist-sync to reduce load.
+The tradeoff is longer server startup times, as the database must be completely
+scanned to re-build the freelist from scratch.
+
+```hcl
+server {
+  raft_boltdb {
+    no_freelist_sync = true
+  }
+}
+```
+
+#### Changes to the `nomad server members` command
+
+The standard output of the `nomad server members` command replaces the previous
+`Protocol` column that indicated the Serf protocol version with a new column
+named `Raft Version` which outputs the Raft protocol version defined in each
+server.
+
+The `-detailed` flag is now called `-verbose` and outputs the standard values
+in addition to extra information. The previous name is still supported but may
+be removed in future releases.
+
+The previous `Protocol` value can be viewed using the `-verbose` flag.
+
+#### Changes to `client.template.function_denylist` configuration
+
+consul-template v0.28 added a new function
+[`writeToFile`](https://github.com/hashicorp/consul-template/blob/v0.28.0/docs/templating-language.md#writeToFile)
+which can write to arbitrary files on the host.
+
+Nomad 1.3.0 disables this function by default in its
+[`function_denylist`](/nomad/docs/configuration/client#function_denylist).
+
+However *if you have overridden the default `template.function_denylist` in
+your client configuration, you must add `writeToFile` to your denylist.*
+Failing to do so allows templates to write to arbitrary paths on the host.
+
+#### Changes to Envoy metrics labels
+
+When using Envoy as a sidecar proxy for Connect enabled services, Nomad will now
+automatically inject the unique allocation ID into Envoy's stats tags configuration.
+Users who wish to set the tag values themselves may do so using the [`proxy.config`](/nomad/docs/job-specification/proxy#config)
+block.
+
+```hcl
+connect {
+  sidecar_service {
+    proxy {
+      config {
+        envoy_stats_tags = ["nomad.alloc_id=<allocID>"]
+      }
+    }
+  }
+}
+```
+
+#### Changes to Consul Connect Service Identity Tokens
+
+Starting with Nomad 1.3.0, Consul Service Identity Tokens created automatically
+by Nomad on behalf of Connect services will now be created as [`Local`] tokens. These
+tokens will no longer be replicated globally. To facilitate cross-Consul datacenter
+requests of Connect services registered by Nomad, Consul agents will need to be
+configured with [default anonymous][anon_token] ACL tokens with ACL policies of
+sufficient permissions to read service and node metadata pertaining to those
+requests. This mechanism is described in Consul [#7414][consul_acl].
+A typical Consul agent anonymous token may contain an ACL policy such as:
+
+```hcl
+service_prefix "" { policy = "read" }
+node_prefix    "" { policy = "read" }
+```
+
+The minimum version of Consul supported by Nomad's Connect integration is now Consul v1.8.0.
+
+#### Changes to task groups that utilise Consul services and checks
+
+Starting with Nomad 1.3.0, services and checks that utilise Consul will have an
+automatic constraint placed upon the task group. This ensures they are placed
+on a client with a Consul agent running that meets a minimum version
+requirement. The minimum version of Consul supported by Nomad's service and
+check blocks is now Consul v1.7.0.
+
+#### Linux Control Groups Version 2
+
+Starting with Nomad 1.3.0, Linux systems configured to use [cgroups v2][cgroups2]
+are now supported. A Nomad client will only activate its v2 control groups manager
+if the system is configured with the cgroups2 controller mounted at `/sys/fs/cgroup`.
+  * Systems that do not support cgroups v2 are not affected.
+  * Systems configured in hybrid mode typically mount the cgroups2
+    controller at `/sys/fs/cgroup/unified`, so Nomad will continue to
+    use cgroups v1 for these hosts.
+  * Systems configured with only cgroups v2 now correctly support setting cpu [cores].
+
+Nomad will preserve the existing cgroup for tasks when a client is
+upgraded, so there will be no disruption to tasks. A new client
+attribute `unique.cgroup.version` indicates which version of control
+groups Nomad is using.
+
+When cgroups v2 are in use, Nomad uses `nomad.slice` as the [default parent][cgroup_parent] for cgroups
+created on behalf of tasks. The cgroup created for a task is named in the form `<allocID>.<task>.scope`.
+These cgroups are created by Nomad before a task starts. External task drivers that support
+containerization should be updated to make use of the new cgroup locations.
+
+The new cgroup file system layout will look like the following:
+
+```shell-session
+➜ tree -d /sys/fs/cgroup/nomad.slice
+/sys/fs/cgroup/nomad.slice
+├── 8b8da4cf-8ebf-b578-0bcf-77190749abf3.redis.scope
+└── a8c8e495-83c8-311b-4657-e6e3127e98bc.example.scope
+```
+#### Support for pre-0.9 Tasks Removed
+
+Running tasks that were created on clusters from Nomad version 0.9 or
+earlier will fail to restore after upgrading a cluster to Nomad
+1.3.0. To safely upgrade without unplanned interruptions, force these
+tasks to be rescheduled by `nomad alloc stop` before upgrading. Note
+this only applies to tasks that have been running continuously from
+before 0.9 without rescheduling. Jobs that were created before 0.9 but
+have had tasks replaced over time after 0.9 will operate normally
+during the upgrade.
+
+## Nomad 1.2.6, 1.1.12, and 1.0.18
+
+#### ACL requirement for the job parse endpoint
+
+Nomad 1.2.6, 1.1.12, and 1.0.18 require ACL authentication for the
+[job parse][api_jobs_parse] API endpoint. The `parse-job` capability has been
+created to allow access to this endpoint. The `submit-job`, `read`, and `write`
+policies include this capability.
+
+
+The capability must be enabled for the namespace used in the API request.
+
+## Nomad 1.2.4
+
+#### `nomad eval status -json` deprecated
+
+Nomad 1.2.4 includes a new `nomad eval list` command that has the
+option to display the results in JSON format with the `-json`
+flag. This replaces the existing `nomad eval status -json` option. In
+Nomad 1.4.0, `nomad eval status -json` will be changed to display only
+the selected evaluation in JSON format.
+
+## Nomad 1.2.2
+
+### Panic on node class filtering for system and sysbatch jobs fixed
+
+Nomad 1.2.2 fixes a [server crashing bug][gh-11563] present in the scheduler
+node class filtering since 1.2.0. Users should upgrade to Nomad 1.2.2 to avoid
+this problem.
+
+## Nomad 1.2.0
+
+#### Nvidia device plugin
+
+The Nvidia device is now an external plugin and must be installed separately.
+Refer to [the Nvidia device plugin's documentation][nvidia] for details.
+
+#### ACL requirements for accessing the job details page in the Nomad UI
+
+Nomad 1.2.0 introduced a new UI component to display the status of `system` and
+`sysbatch` jobs in each client where they are running. This feature makes an
+API call to an endpoint that requires `node:read` ACL permission. Tokens used
+to access the Nomad UI will need to be updated to include this permission in
+order to access a job details page.
+
+This was an unintended change fixed in Nomad 1.2.4.
+
+#### HCLv2 Job Specification Parsing
+
+In previous versions of Nomad, when rendering a job specification using override
+variables, a warning would be returned if a variable within an override file
+was declared that was not found within the job specification. This behaviour
+differed from passing variables via the `-var` flag, which would always cause an
+error in the same situation.
+
+Nomad 1.2.0 fixed the behaviour consistency to always return an error by default,
+where an override variable was specified which was not a known variable within the
+job specification. In order to mitigate this change for users who wish to only
+be warned when this situation arises, the `-hcl-strict=false` flag can be
+specified.
+
+## Nomad 1.0.11 and 1.1.5 Enterprise
+
+#### Audit log file names
+
+Audit log file naming now matches the standard log file naming introduced in
+1.0.10 and 1.1.4. The audit log currently being written will no longer have a
+timestamp appended.
+
+## Nomad 1.0.10 and 1.1.4
+
+#### Log file names
+
+The [`log_file`] configuration option was not being fully respected, as the
+generated filename would include a timestamp. After upgrade, the active log
+file will always be the value defined in `log_file`, with timestamped files
+being created during log rotation.
+
+## Nomad 1.0.9 and 1.1.3
+
+#### Namespace in Job Run and Plan APIs
+
+The Job Run and Plan APIs now respect the `?namespace=...` query parameter over
+the namespace specified in the job itself. This matches the precedence of
+region and [fixes a bug where the `-namespace` flag was not respected for the
+`nomad run` and `nomad apply` commands.][gh-10875]
+
+For users of [`api.Client`][go-client] who want their job namespace respected,
+you must ensure the `Config.Namespace` field is unset.
+
+#### Docker Driver
+
+**1.1.3 only**
+
+Starting in Nomad 1.1.2, task groups with `network.mode = "bridge"` generated a
+hosts file in Docker containers. This generated hosts file was bind-mounted
+from the task directory to `/etc/hosts` within the task. In Nomad 1.1.3 the
+source for the bind mount was moved to the allocation directory so that it is
+shared between all tasks in an allocation.
+
+Please note that this change may prevent [`extra_hosts`] values from being
+properly set in each task when there are multiple tasks within the same group.
+When using `extra_hosts` with Consul Connect in `bridge` network mode, you
+should set the hosts values in the [`sidecar_task.config`] block instead.
+
+## Nomad 1.1.0
+
+#### Enterprise licenses
+
+Nomad Enterprise licenses are no longer stored in raft or synced between
+servers. Nomad Enterprise servers will not start without a license. There is
+no longer a six hour evaluation period when running Nomad Enterprise. Before
+upgrading, you must provide each server with a license on disk or in its
+environment (see the [Enterprise licensing] documentation for details).
+
+The `nomad license put` command has been removed.
+
+The `nomad license get` command is no longer forwarded to the Nomad leader,
+and will return the license from the specific server being contacted.
+
+Click [here](https://www.hashicorp.com/products/nomad/trial) to get a trial license for Nomad Enterprise.
+
+#### Agent Metrics API
+
+The Nomad agent metrics API now respects the
+[`prometheus_metrics`](/nomad/docs/configuration/telemetry#prometheus_metrics)
+configuration value. If this value is set to `false`, which is the default value,
+calling `/v1/metrics?format=prometheus` will now result in a response error.
+
+#### CSI volumes
+
+The volume specification for CSI volumes has been updated to support volume
+creation. The `access_mode` and `attachment_mode` fields have been moved to a
+`capability` block that can be repeated. Existing registered volumes will be
+automatically modified the next time that a volume claim is updated. Volume
+specification files for new volumes should be updated to the format described
+in the [`volume create`] and [`volume register`] commands.
+
+The [`volume`] block has an `access_mode` and `attachment_mode` field that are
+required for CSI volumes. Jobs that use CSI volumes should be updated with
+these fields.
+
+#### Connect native tasks
+
+Connect native tasks running in host networking mode will now have `CONSUL_HTTP_ADDR`
+set automatically. Before this was only the case for bridge networking. If an operator
+already explicitly set `CONSUL_HTTP_ADDR` then it will not get overridden.
+
+#### Linux capabilities in exec/java
+
+Following the security [remediation][no_net_raw] in Nomad versions 0.12.12, 1.0.5,
+and 1.1.0-rc1, the `exec` and `java` task drivers will additionally no longer enable
+the following linux capabilities by default.
+
+```
+AUDIT_CONTROL  AUDIT_READ  BLOCK_SUSPEND  DAC_READ_SEARCH  IPC_LOCK  IPC_OWNER  LEASE
+LINUX_IMMUTABLE  MAC_ADMIN  MAC_OVERRIDE  NET_ADMIN  NET_BROADCAST  NET_RAW  SYS_ADMIN
+SYS_BOOT  SYSLOG  SYS_MODULE  SYS_NICE  SYS_PACCT  SYS_PTRACE  SYS_RAWIO  SYS_RESOURCE
+SYS_TIME  SYS_TTY_CONFIG  WAKE_ALARM
+```
+
+The capabilities now enabled by default are modeled after Docker default
+[`linux capabilities`] (excluding `NET_RAW`).
+
+```
+AUDIT_WRITE  CHOWN  DAC_OVERRIDE  FOWNER  FSETID  KILL  MKNOD  NET_BIND_SERVICE
+SETFCAP  SETGID  SETPCAP  SETUID  SYS_CHROOT
+```
+
+A new `allow_caps` plugin configuration parameter for [`exec`][allow_caps_exec]
+and [`java`][allow_caps_java] task drivers can be used to restrict the set of
+capabilities allowed for use by tasks.
+
+Tasks using the `exec` or `java` task drivers can add or remove desired linux
+capabilities using the [`cap_add`][cap_add_exec] and [`cap_drop`][cap_drop_exec]
+task configuration options.
+
+#### iptables
+
+Nomad now appends its iptables rules to the `NOMAD-ADMIN` chain instead of
+inserting them as the first rule. This allows better control for user-defined
+iptables rules but users who append rules currently should verify that their
+rules are being appended in the correct order.
+
+## Nomad 1.1.0-rc1, 1.0.5, 0.12.12
+
+Nomad versions 1.1.0-rc1, 1.0.5 and 0.12.12 change the behavior of the `docker`, `exec`,
+and `java` task drivers so that the [`CAP_NET_RAW`] linux capability is disabled
+by default. This is one of the [`linux capabilities`] that Docker itself enables
+by default, as this capability enables the generation of ICMP packets - used by
+the common `ping` utility for performing network diagnostics. When used by groups in
+`bridge` networking mode, the `CAP_NET_RAW` capability also exposes tasks to ARP spoofing,
+enabling DoS and MITM attacks against other tasks running in `bridge` networking
+on the same host. Operators should weigh potential impact of an upgrade on their
+applications against the security consequences inherit with `CAP_NET_RAW`. Typical
+applications using `tcp` or `udp` based networking should not be affected.
+
+This is the sole change for Nomad 1.0.5 and 0.12.12, intended to provide better
+task network isolation by default.
+
+Users of the `docker` driver can restore the previous behavior by configuring the
+[`allow_caps`] driver configuration option to explicitly enable the `CAP_NET_RAW`
+capability.
+
+```hcl
+plugin "docker" {
+  config {
+    allow_caps = [
+      "CHOWN", "DAC_OVERRIDE", "FSETID", "FOWNER", "MKNOD",
+      "SETGID", "SETUID", "SETFCAP", "SETPCAP", "NET_BIND_SERVICE",
+      "SYS_CHROOT", "KILL", "AUDIT_WRITE", "NET_RAW",
+    ]
+  }
+}
+```
+
+An upcoming version of Nomad will include similar configuration options for the
+`exec` and `java` task drivers.
+
+This change is limited to `docker`, `exec`, and `java` driver plugins. It does
+not affect the Nomad server. This only affects Nomad clients running Linux, with
+tasks using `bridge` networking and one of these task drivers, or third-party
+plugins which relied on the shared Nomad executor library.
+
+Upgrading a Nomad client to 1.0.5 or 0.12.12 will not restart existing tasks. As
+such, processes from existing `docker`, `exec`, or `java` tasks will need to be
+manually restarted (using `alloc stop` or another mechanism) in order to be
+fully isolated.
+
+## Nomad 1.0.3, 0.12.10
+
+Nomad versions 1.0.3 and 0.12.10 change the behavior of the `exec` and `java` drivers so that
+tasks are isolated in their own PID and IPC namespaces. As a result, the
+process launched by these drivers will be PID 1 in the namespace. This has
+[significant impact](https://man7.org/linux/man-pages/man7/pid_namespaces.7.html)
+on the treatment of a process by the Linux kernel. Furthermore, tasks in the
+same allocation will no longer be able to coordinate using signals, SystemV IPC
+objects, or POSIX message queues. Operators should weigh potential impact of an
+upgrade on their applications against the security consequences inherent in using
+the host namespaces.
+
+This is the sole change for Nomad 1.0.3, intended to provide better process
+isolation by default. An upcoming version of Nomad will include options for
+configuring this behavior.
+
+This change is limited to the `exec` and `java` driver plugins. It does not affect
+the Nomad server. This only affect Nomad clients running on Linux, using the
+`exec` or `java` drivers or third-party driver plugins which relied on the shared
+Nomad executor library.
+
+Upgrading a Nomad client to 1.0.3 or 0.12.10 will not restart existing tasks.
+As such, processes from existing `exec`/`java` tasks will need to be manually restarted
+(using `alloc stop` or another mechanism) in order to be fully isolated.
+
+## Nomad 1.0.2
+
+#### Dynamic secrets trigger template changes on client restart
+
+Nomad 1.0.2 changed the behavior of template `change_mode` triggers when a
+client node restarts. In Nomad 1.0.1 and earlier, the first rendering of a
+template after a client restart would not trigger the `change_mode`. For
+dynamic secrets such as the Vault PKI secrets engine, this resulted in the
+secret being updated but not restarting or signalling the task. When the
+secret's lease expired at some later time, the task workload might fail
+because of the stale secret. For example, a web server's SSL certificate would
+be expired and browsers would be unable to connect.
+
+In Nomad 1.0.2, when a client node is restarted any task with Vault secrets
+that are generated or have expired will have its `change_mode` triggered. If
+`change_mode = "restart"` this will result in the task being restarted, to
+avoid the task failing unexpectedly at some point in the future. This change
+only impacts tasks using dynamic Vault secrets engines such as [PKI][pki], or
+when secrets are rotated. Secrets that don't change in Vault will not trigger
+a `change_mode` on client restart.
+
+## Nomad 1.0.1
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changed the default behavior around the number of worker threads
+created by the Envoy when being used as a sidecar for Consul Connect. In Nomad
+v1.0.1, the same default setting of [`--concurrency=1`][envoy_concurrency] is set for Envoy when used
+as a Connect gateway. As before, the [`meta.connect.proxy_concurrency`][proxy_concurrency]
+property can be set in client configuration to override the default value.
+
+## Nomad 1.0.0
+
+### HCL2 for Job specification
+
+Nomad v1.0.0 adopts HCL2 for parsing the job spec. HCL2 extends HCL with more
+expression and reuse support, but adds some stricter schema for HCL blocks
+(a.k.a. blocks). Check [HCL](/nomad/docs/job-specification/hcl2) for more details.
+
+### Signal used when stopping Docker tasks
+
+When stopping tasks running with the Docker task driver, Nomad documents that a
+`SIGTERM` will be issued (unless configured with `kill_signal`). However, recent
+versions of Nomad would issue `SIGINT` instead. Starting again with Nomad v1.0.0
+`SIGTERM` will be sent by default when stopping Docker tasks.
+
+### Deprecated metrics have been removed
+
+Nomad v0.7.0 added supported for tagged metrics and deprecated untagged metrics.
+There was support for configuring backwards-compatible metrics. This support has
+been removed with v1.0.0, and all metrics will be emitted with tags.
+
+### Null characters in region, datacenter, job name/ID, task group name, and task names
+
+Starting with Nomad v1.0.0, jobs will fail validation if any of the following
+contain null character: the job ID or name, the task group name, or the task
+name. Any jobs meeting this requirement should be modified before an update to
+v1.0.0. Similarly, client and server config validation will prohibit either the
+region or the datacenter from containing null characters.
+
+### EC2 CPU characteristics may be different
+
+Starting with Nomad v1.0.0, the AWS fingerprinter uses data derived from the
+official AWS EC2 API to determine default CPU performance characteristics,
+including core count and core speed. This data should be accurate for each
+instance type per region. Previously, Nomad used a hand-made lookup table that
+was not region aware and may have contained inaccurate or incomplete data. As
+part of this change, the AWS fingerprinter no longer sets the `cpu.modelname`
+attribute.
+
+As before, `cpu_total_compute` can be used to override the discovered CPU
+resources available to the Nomad client.
+
+### Inclusive language
+
+Starting with Nomad v1.0.0, the terms `blacklist` and `whitelist` have been
+deprecated from client configuration and driver configuration. The existing
+configuration values are permitted but will be removed in a future version of
+Nomad. The specific configuration values replaced are:
+
+- Client `driver.blacklist` is replaced with `driver.denylist`.
+
+- Client `driver.whitelist` is replaced with `driver.allowlist`.
+
+- Client `env.blacklist` is replaced with `env.denylist`.
+
+- Client `fingerprint.blacklist` is replaced with `fingerprint.denylist`.
+
+- Client `fingerprint.whitelist` is replaced with `fingerprint.allowlist`.
+
+- Client `user.blacklist` is replaced with `user.denylist`.
+
+- Client `template.function_blacklist` is replaced with
+  `template.function_denylist`.
+
+- Docker driver `docker.caps.whitelist` is replaced with
+  `docker.caps.allowlist`.
+
+### Consul Connect
+
+Nomad 1.0's Consul Connect integration works best with Consul 1.9 or later. The
+ideal upgrade path is:
+
+1. Create a new Nomad client image with Nomad 1.0 and Consul 1.9 or later.
+2. Add new hosts based on the image.
+3. [Drain][drain-cli] and shutdown old Nomad client nodes.
+
+While inplace upgrades and older versions of Consul are supported by Nomad 1.0,
+Envoy proxies will drop and stop accepting connections while the Nomad agent is
+restarting. Nomad 1.0 with Consul 1.9 do not have this limitation.
+
+#### Envoy proxy versions
+
+Nomad v1.0.0 changes the behavior around the selection of Envoy version used for
+Connect sidecar proxies. Previously, Nomad always defaulted to Envoy v1.11.2 if
+neither the `meta.connect.sidecar_image` parameter or `sidecar_task` block were
+explicitly configured. Likewise the same version of Envoy would be used for
+Connect ingress gateways if `meta.connect.gateway_image` was unset. Starting
+with Nomad v1.0.0, each Nomad Client will query Consul for a list of supported
+Envoy versions. Nomad will make use of the latest version of Envoy supported by
+the Consul agent when launching Envoy as a Connect sidecar proxy. If the version
+of the Consul agent is older than v1.7.8, v1.8.4, or v1.9.0, Nomad will fallback
+to the v1.11.2 version of Envoy. As before, if the `meta.connect.sidecar_image`,
+`meta.connect.gateway_image`, or `sidecar_task` block are set, those settings
+take precedence.
+
+When upgrading Nomad Clients from a previous version to v1.0.0 and above, it is
+recommended to also upgrade the Consul agents to v1.7.8, 1.8.4, or v1.9.0 or
+newer. Upgrading Nomad and Consul to versions that support the new behavior
+while also doing a full [node drain][] at the time of the upgrade for each node
+will ensure Connect workloads are properly rescheduled onto nodes in such a way
+that the Nomad Clients, Consul agents, and Envoy sidecar tasks maintain
+compatibility with one another.
+
+#### Envoy worker threads
+
+Nomad v1.0.0 changes the default behavior around the number of worker threads
+created by the Envoy sidecar proxy when using Consul Connect. Previously, the
+Envoy [`--concurrency`][envoy_concurrency] argument was left unset, which caused
+Envoy to spawn as many worker threads as logical cores available on the CPU. The
+`--concurrency` value now defaults to `1` and can be configured by setting the
+[`meta.connect.proxy_concurrency`][proxy_concurrency] property in client
+configuration.
+
+## Nomad 0.12.8
+
+### Docker volume mounts
+
+Nomad 0.12.8 includes security fixes for the handling of Docker volume mounts:
+
+- The `docker.volumes.enabled` flag now defaults to `false` as documented.
+
+- Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+  could mount arbitrary locations from the client host. The
+  `docker.volumes.enabled` configuration will now disable Docker mounts with
+  type "volume" when set to `false` (the default).
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.12.6
+
+### Artifact and Template Paths
+
+Nomad 0.12.6 includes security fixes for privilege escalation vulnerabilities
+in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the [`template.disable_file_sandbox`][] field in the client
+  configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths do
+  not escape the file sandbox. It was possible to use interpolation to bypass
+  this validation. The client now interpolates the paths before checking if they
+  are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.12.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.12.9. To work around the bug, use a relative path.
+
+## Nomad 0.12.0
+
+### `mbits` and Task Network Resource deprecation
+
+Starting in Nomad 0.12.0 the `mbits` field of the network resource block has
+been deprecated and is no longer considered when making scheduling decisions.
+This is in part because we felt that `mbits` didn't accurately account network
+bandwidth as a resource.
+
+Additionally the use of the `network` block inside of a task's `resource` block
+is also deprecated. Users are advised to move their `network` block to the
+`group` block. Recent networking features have only been added to group based
+network configuration. If any usecase or feature which was available with task
+network resource is not fulfilled with group network configuration, please open
+an issue detailing the missing capability.
+
+Additionally, the `docker` driver's `port_map` configuration is deprecated in
+lieu of the `ports` field.
+
+### Enterprise Licensing
+
+Enterprise binaries for Nomad are now publicly available via
+[releases.hashicorp.com](https://releases.hashicorp.com/nomad/). By default all
+enterprise features are enabled for 6 hours. During that time enterprise users
+should apply their license with the [`nomad license put ...`](/nomad/docs/v1.0.x/commands/license/put) command.
+
+Once the 6 hour demonstration period expires, Nomad will shutdown. If restarted
+Nomad will shutdown in a very short amount of time unless a valid license is
+applied.
+
+~> **Warning:** Due to a [bug][gh-8457] in Nomad v0.12.0, existing clusters
+that are upgraded will **not** have 6 hours to apply a license. The minimal
+grace period should be sufficient to apply a valid license, but enterprise
+users are encouraged to delay upgrading until Nomad v0.12.1 is released and
+fixes the issue.
+
+### Docker access host filesystem
+
+Nomad 0.12.0 disables Docker tasks access to the host filesystem, by default.
+Prior to Nomad 0.12, Docker tasks may mount and then manipulate any host file
+and may pose a security risk.
+
+Operators now must explicitly allow tasks to access host filesystem. [Host
+Volumes](/nomad/docs/configuration/client#host_volume-block) provide a fine tune
+access to individual paths.
+
+To restore pre-0.12.0 behavior, you can enable [Docker
+`volume`](/nomad/docs/drivers/docker#enabled-1) to allow binding host paths, by adding
+the following to the nomad client config file:
+
+```hcl
+plugin "docker" {
+  config {
+    volumes {
+      enabled = true
+    }
+  }
+}
+```
+
+### QEMU images
+
+Nomad 0.12.0 restricts the paths the QEMU tasks can load an image from. A QEMU
+task may download an image to the allocation directory to load. But images
+outside the allocation directories must be explicitly allowed by operators in
+the client agent configuration file.
+
+For example, you may allow loading QEMU images from `/mnt/qemu-images` by
+adding the following to the agent configuration file:
+
+```hcl
+plugin "qemu" {
+  config {
+    image_paths = ["/mnt/qemu-images"]
+  }
+}
+```
+
+## Nomad 0.11.7
+
+### Docker volume mounts
+
+Nomad 0.11.7 includes a security fix for the handling of Docker volume
+mounts. Docker driver mounts of type "volume" (but not "bind") were not
+sandboxed and could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with
+type "volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as
+shown below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.11.5
+
+### Artifact and Template Paths
+
+Nomad 0.11.5 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.11.5, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.11.6. To work around the bug, use a relative path.
+
+## Nomad 0.11.3
+
+Nomad 0.11.3 fixes a critical bug causing the nomad agent to become
+unresponsive. The issue is due to a [Go 1.14.1 runtime
+bug](https://github.com/golang/go/issues/38023) and affects Nomad 0.11.1 and
+0.11.2.
+
+## Nomad 0.11.2
+
+### Scheduler Scoring Changes
+
+Prior to Nomad 0.11.2 the scheduler algorithm used a [node's reserved
+resources][reserved]
+incorrectly during scoring. The result of this bug was that scoring biased in
+favor of nodes with reserved resources vs nodes without reserved resources.
+
+Placements will be more correct but slightly different in v0.11.2 vs earlier
+versions of Nomad. Operators do _not_ need to take any actions as the impact of
+the bug fix will only minimally affect scoring.
+
+Feasibility (whether a node is capable of running a job at all) is _not_
+affected.
+
+### Periodic Jobs and Daylight Saving Time
+
+Nomad 0.11.2 fixed a long outstanding bug affecting periodic jobs that are
+scheduled to run during Daylight Saving Time transitions.
+
+Nomad 0.11.2 provides a more defined behavior: Nomad evaluates the cron
+expression with respect to specified time zone during transition. A 2:30am
+nightly job with `America/New_York` time zone will not run on the day daylight
+saving time starts; similarly, a 1:30am nightly job will run twice on the day
+daylight saving time ends. See the [Daylight Saving Time][dst] documentation
+for details.
+
+## Nomad 0.11.0
+
+### client.template: `vault_grace` deprecation
+
+Nomad 0.11.0 updates
+[consul-template](https://github.com/hashicorp/consul-template) to v0.24.1. This
+library deprecates the [`vault_grace`][vault_grace] option for templating
+included in Nomad. The feature has been ignored since Vault 0.5 and as long as
+you are running a more recent version of Vault, you can safely remove
+`vault_grace` from your Nomad jobs.
+
+### Rkt Task Driver Removed
+
+The `rkt` task driver has been deprecated and removed from Nomad. While the code
+is available in an external repository,
+<https://github.com/hashicorp/nomad-driver-rkt>, it will not be maintained as
+`rkt` is [no longer being developed upstream](https://github.com/rkt/rkt). We
+encourage all `rkt` users to find a new task driver as soon as possible.
+
+## Nomad 0.10.8
+
+### Docker volume mounts
+
+Nomad 0.10.8 includes a security fix for the handling of Docker volume mounts.
+Docker driver mounts of type "volume" (but not "bind") were not sandboxed and
+could mount arbitrary locations from the client host. The
+`docker.volumes.enabled` configuration will now disable Docker mounts with type
+"volume" when set to `false`.
+
+This change Docker impacts jobs that use a `mounts` with type "volume", as shown
+below. This job will fail when placed unless `docker.volumes.enabled = true`.
+
+```hcl
+mounts = [
+  {
+    type     = "volume"
+    target   = "/path/in/container"
+    source   = "docker_volume"
+    volume_options = {
+      driver_config = {
+        name = "local"
+        options = [
+          {
+            device = "/"
+            o      = "ro,bind"
+            type   = "ext4"
+          }
+        ]
+      }
+    }
+  }
+]
+```
+
+## Nomad 0.10.6
+
+### Artifact and Template Paths
+
+Nomad 0.10.6 includes backported security fixes for privilege escalation
+vulnerabilities in handling of job `template` and `artifact` blocks:
+
+- The `template.source` and `template.destination` fields are now protected by
+  the file sandbox introduced in 0.9.6. These paths are now restricted to fall
+  inside the task directory by default. An operator can opt-out of this
+  protection with the
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The paths for `template.source`, `template.destination`, and
+  `artifact.destination` are validated on job submission to ensure the paths
+  do not escape the file sandbox. It was possible to use interpolation to
+  bypass this validation. The client now interpolates the paths before
+  checking if they are in the file sandbox.
+
+~> **Warning:** Due to a [bug][gh-9148] in Nomad v0.10.6, the
+`template.destination` and `artifact.destination` paths do not support
+absolute paths, including the interpolated `NOMAD_SECRETS_DIR`,
+`NOMAD_TASK_DIR`, and `NOMAD_ALLOC_DIR` variables. This bug is fixed in
+v0.10.7. To work around the bug, use a relative path.
+
+## Nomad 0.10.4
+
+### Same-Node Scheduling Penalty Removed
+
+Nomad 0.10.4 includes a fix to the scheduler that removes the same-node penalty
+for allocations that have not previously failed. In earlier versions of Nomad,
+the node where an allocation was running was penalized from receiving updated
+versions of that allocation, resulting in a higher chance of the allocation
+being placed on a new node. This was changed so that the penalty only applies to
+nodes where the previous allocation has failed or been rescheduled, to reduce
+the risk of correlated failures on a host. Scheduling weighs a number of
+factors, but this change should reduce movement of allocations that are being
+updated from a healthy state. You can view the placement metrics for an
+allocation with `nomad alloc status -verbose`.
+
+### Additional Environment Variable Filtering
+
+Nomad will by default prevent certain environment variables set in the client
+process from being passed along into launched tasks. The `CONSUL_HTTP_TOKEN`
+environment variable has been added to the default list. More information can
+be found in the `env.blacklist` [configuration](/nomad/docs/configuration/client#env-blacklist) .
+
+## Nomad 0.10.3
+
+### mTLS Certificate Validation
+
+Nomad 0.10.3 includes a fix for a privilege escalation vulnerability in
+validating TLS certificates for RPC with mTLS. Nomad RPC endpoints validated
+that TLS client certificates had not expired and were signed by the same CA as
+the Nomad node, but did not correctly check the certificate's name for the role
+and region as described in the [Securing Nomad with TLS][tls-guide] guide. This
+allows trusted operators with a client certificate signed by the CA to send RPC
+calls as a Nomad client or server node, bypassing access control and accessing
+any secrets available to a client.
+
+Nomad clusters configured for mTLS following the [Securing Nomad with
+TLS][tls-guide] guide or the [Vault PKI Secrets Engine
+Integration][tls-vault-guide] guide should already have certificates that will
+pass validation. Before upgrading to Nomad 0.10.3, operators using mTLS with
+`verify_server_hostname = true` should confirm that the common name or SAN of
+all Nomad client node certs is `client.<region>.nomad`, and that the common name
+or SAN of all Nomad server node certs is `server.<region>.nomad`.
+
+### Connection Limits Added
+
+Nomad 0.10.3 introduces the [limits][] agent configuration parameters for
+mitigating denial of service attacks from users who are not authenticated via
+mTLS. The default limits block is:
+
+```hcl
+limits {
+  https_handshake_timeout   = "5s"
+  http_max_conns_per_client = 100
+  rpc_handshake_timeout     = "5s"
+  rpc_max_conns_per_client  = 100
+}
+```
+
+If your Nomad agent's endpoints are protected from unauthenticated users via
+other mechanisms these limits may be safely disabled by setting them to `0`.
+
+However the defaults were chosen to be safe for a wide variety of Nomad
+deployments and may protect against accidental abuses of the Nomad API that
+could cause unintended resource usage.
+
+## Nomad 0.10.2
+
+### Preemption Panic Fixed
+
+Nomad 0.9.7 and 0.10.2 fix a [server crashing bug][gh-6787] present in scheduler
+preemption since 0.9.0. Users unable to immediately upgrade Nomad can [disable
+preemption][preemption-api] to avoid the panic.
+
+### Dangling Docker Container Cleanup
+
+Nomad 0.10.2 addresses an issue occurring in heavily loaded clients, where
+containers are started without being properly managed by Nomad. Nomad 0.10.2
+introduced a reaper that detects and kills such containers.
+
+Operators may opt to run reaper in a dry-mode or disabling it through a client
+config.
+
+For more information, see [Docker Dangling containers][dangling-containers].
+
+## Nomad 0.10.0
+
+### Deployments
+
+Nomad 0.10 enables rolling deployments for service jobs by default and adds a
+default update block when a service job is created or updated. This does not
+affect jobs with an update block.
+
+In pre-0.10 releases, when updating a service job without an update block, all
+existing allocations are stopped while new allocations start up, and this may
+cause a service degradation or an outage. You can regain this behavior and
+disable deployments by setting `max_parallel` to 0.
+
+For more information, see [`update` block][update].
+
+## Nomad 0.9.5
+
+### Template Rendering
+
+Nomad 0.9.5 includes security fixes for privilege escalation vulnerabilities in
+handling of job `template` blocks:
+
+- The client host's environment variables are now cleaned before rendering the
+  template. If a template includes the `env` function, the job should include an
+  [`env`](/nomad/docs/job-specification/env) block to allow access to the variable in
+  the template.
+
+- The `plugin` function is no longer permitted by default and will raise an
+  error if used in a template. Operator can opt-in to permitting this function
+  with the new
+  [`template.function_blacklist`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+- The `file` function has been changed to restrict paths to fall inside the task
+  directory by default. Paths that used the `NOMAD_TASK_DIR` environment
+  variable to prefix file paths should work unchanged. Relative paths or
+  symlinks that point outside the task directory will raise an error. An
+  operator can opt-out of this protection with the new
+  [`template.disable_file_sandbox`](/nomad/docs/configuration/client#template-parameters)
+  field in the client configuration.
+
+## Nomad 0.9.0
+
+### Preemption
+
+Nomad 0.9 adds preemption support for system jobs. If a system job is submitted
+that has a higher priority than other running jobs on the node, and the node
+does not have capacity remaining, Nomad may preempt those lower priority
+allocations to place the system job. See [preemption][preemption] for more
+details.
+
+### Task Driver Plugins
+
+All task drivers have become [plugins][plugins] in Nomad 0.9.0. There are two
+user visible differences between 0.8 and 0.9 drivers:
+
+- [LXC][lxc] is now community supported and distributed independently.
+
+- Task driver [`config`][task-config] blocks are no longer validated by
+  the [`nomad job validate`][validate] command. This is a regression that will
+  be fixed in a future release.
+
+There is a new method for client driver configuration options, but existing
+`client.options` settings are supported in 0.9. See [plugin
+configuration][plugin-block] for details.
+
+#### LXC
+
+LXC is now an external plugin and must be installed separately. See [the LXC
+driver's documentation][lxc] for details.
+
+### Structured Logging
+
+Nomad 0.9.0 switches to structured logging. Any log processing on the pre-0.9
+log output will need to be updated to match the structured output.
+
+Structured log lines have the format:
+
+```
+# <Timestamp> [<Level>] <Component>: <Message>: <KeyN>=<ValueN> ...
+
+2019-01-29T05:52:09.221Z [INFO ] client.plugin: starting plugin manager: plugin-type=device
+```
+
+Values containing whitespace will be quoted:
+
+```
+... starting plugin: task=redis args="[/opt/gopath/bin/nomad logmon]"
+```
+
+### HCL2 Transition
+
+Nomad 0.9.0 begins a transition to [HCL2][hcl2], the next version of the
+HashiCorp configuration language. While Nomad has begun integrating HCL2, users
+will need to continue to use HCL1 in Nomad 0.9.0 as the transition is
+incomplete.
+
+If you interpolate variables in your [`task.config`][task-config] containing
+consecutive dots in their name, you will need to change your job specification
+to use the `env` map. See the following example:
+
+```hcl
+env {
+  # Note the multiple consecutive dots
+  image...version = "3.2"
+
+  # Valid in both v0.8 and v0.9
+  image.version = "3.2"
+}
+
+# v0.8 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${image...version}"
+  }
+}
+
+# v0.9 task config block:
+task {
+  driver = "docker"
+  config {
+    image = "redis:${env["image...version"]}"
+  }
+}
+```
+
+This only affects users who interpolate unusual variables with multiple
+consecutive dots in their task `config` block. All other interpolation is
+unchanged.
+
+Since HCL2 uses dotted object notation for interpolation users should transition
+away from variable names with multiple consecutive dots.
+
+### Downgrading clients
+
+Due to the large refactor of the Nomad client in 0.9, downgrading to a previous
+version of the client after upgrading it to Nomad 0.9 is not supported. To
+downgrade safely, users should erase the Nomad client's data directory.
+
+### `port_map` Environment Variable Changes
+
+Before Nomad 0.9.0 ports mapped via a task driver's `port_map` block could be
+interpolated via the `NOMAD_PORT_<label>` environment variables.
+
+However, in Nomad 0.9.0 no parameters in a driver's `config` block, including
+its `port_map`, are available for interpolation. This means `{{ env NOMAD_PORT_<label> }}` in a `template` block or `HTTP_PORT = "${NOMAD_PORT_http}"` in an `env` block will now interpolate the _host_ ports,
+not the container's.
+
+Nomad 0.10 introduced Task Group Networking which natively supports port mapping
+without relying on task driver specific `port_map` fields. The
+[`to`](/nomad/docs/job-specification/network#to) field on group network port blocks
+will be interpolated properly. Please see the
+[`network`](/nomad/docs/job-specification/network/) block documentation for details.
+
+## Nomad 0.8.0
+
+### Raft Protocol Version Compatibility
+
+When upgrading to Nomad 0.8.0 from a version lower than 0.7.0, users will need
+to set the [`raft_protocol`] option in
+their `server` block to 1 in order to maintain backwards compatibility with the
+old servers during the upgrade. After the servers have been migrated to version
+0.8.0, `raft_protocol` can be moved up to 2 and the servers restarted to match
+the default.
+
+The Raft protocol must be stepped up in this way; only adjacent version numbers
+are compatible (for example, version 1 cannot talk to version 3). Here is a
+table of the Raft Protocol versions supported by each Nomad version:
+
+<table>
+  <thead>
+    <tr>
+      <th>Version</th>
+      <th>Supported Raft Protocols</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0.6 and earlier</td>
+      <td>0</td>
+    </tr>
+    <tr>
+      <td>0.7</td>
+      <td>1</td>
+    </tr>
+    <tr>
+      <td>0.8 and later</td>
+      <td>1, 2, 3</td>
+    </tr>
+  </tbody>
+</table>
+
+In order to enable all
+[Autopilot](/nomad/tutorials/manage-clusters/autopilot) features, all
+servers in a Nomad cluster must be running with Raft protocol version 3 or
+later.
+
+### Node Draining Improvements
+
+Node draining via the [`node drain`][drain-cli] command or the [drain
+API][drain-api] has been substantially changed in Nomad 0.8. In Nomad 0.7.1 and
+earlier draining a node would immediately stop all allocations on the node
+being drained. Nomad 0.8 now supports a [`migrate`][migrate] block in job
+specifications to control how many allocations may be migrated at once and the
+default will be used for existing jobs.
+
+The `drain` command now blocks until the drain completes. To get the Nomad 0.7.1
+and earlier drain behavior use the command: `nomad node drain -enable -force -detach <node-id>`
+
+See the [`migrate` block documentation][migrate] and [Decommissioning Nodes
+guide](/nomad/tutorials/manage-clusters/node-drain) for details.
+
+### Periods in Environment Variable Names No Longer Escaped
+
+_Applications which expect periods in environment variable names to be replaced
+with underscores must be updated._
+
+In Nomad 0.7 periods (`.`) in environment variables names were replaced with an
+underscore in both the [`env`](/nomad/docs/job-specification/env) and
+[`template`](/nomad/docs/job-specification/template) blocks.
+
+In Nomad 0.8 periods are _not_ replaced and will be included in environment
+variables verbatim.
+
+For example the following block:
+
+```text
+env {
+  registry.consul.addr = "${NOMAD_IP_http}:8500"
+}
+```
+
+In Nomad 0.7 would be exposed to the task as
+`registry_consul_addr=127.0.0.1:8500`. In Nomad 0.8 it will now appear exactly
+as specified: `registry.consul.addr=127.0.0.1:8500`.
+
+### Client APIs Unavailable on Older Nodes
+
+Because Nomad 0.8 uses a new RPC mechanism to route node-specific APIs like
+[`nomad alloc fs`](/nomad/docs/commands/alloc/fs) through servers to the node,
+0.8 CLIs are incompatible using these commands on clients older than 0.8.
+
+To access these commands on older clients either continue to use a pre-0.8
+version of the CLI, or upgrade all clients to 0.8.
+
+### CLI Command Changes
+
+Nomad 0.8 has changed the organization of CLI commands to be based on
+subcommands. An example of this change is the change from `nomad alloc-status`
+to `nomad alloc status`. All commands have been made to be backwards compatible,
+but operators should update any usage of the old style commands to the new style
+as the old style will be deprecated in future versions of Nomad.
+
+### RPC Advertise Address
+
+The behavior of the [advertised RPC address](/nomad/docs/configuration#rpc-1) has
+changed to be only used to advertise the RPC address of servers to client nodes.
+Server to server communication is done using the advertised Serf address.
+Existing cluster's should not be effected but the advertised RPC address may
+need to be updated to allow connecting client's over a NAT.
+
+## Nomad 0.6.0
+
+### Default `advertise` address changes
+
+When no `advertise` address was specified and Nomad's `bind_addr` was loopback
+or `0.0.0.0`, Nomad attempted to resolve the local hostname to use as an
+advertise address.
+
+Many hosts cannot properly resolve their hostname, so Nomad 0.6 defaults
+`advertise` to the first private IP on the host (e.g. `10.1.2.3`).
+
+If you manually configure `advertise` addresses no changes are necessary.
+
+## Nomad Clients
+
+The change to the default, advertised IP also effect clients that do not specify
+which network_interface to use. If you have several routable IPs, it is advised
+to configure the client's [network
+interface](/nomad/docs/configuration/client#network_interface) such that tasks bind to
+the correct address.
+
+## Nomad 0.5.5
+
+### Docker `load` changes
+
+Nomad 0.5.5 has a backward incompatible change in the `docker` driver's
+configuration. Prior to 0.5.5 the `load` configuration option accepted a list
+images to load, in 0.5.5 it has been changed to a single string. No
+functionality was changed. Even if more than one item was specified prior to
+0.5.5 only the first item was used.
+
+To do a zero-downtime deploy with jobs that use the `load` option:
+
+- Upgrade servers to version 0.5.5 or later.
+
+- Deploy new client nodes on the same version as the servers.
+
+- Resubmit jobs with the `load` option fixed and a constraint to only run on
+  version 0.5.5 or later:
+
+```hcl
+    constraint {
+      attribute = "${attr.nomad.version}"
+      operator  = "version"
+      value     = ">= 0.5.5"
+    }
+```
+
+- Drain and shutdown old client nodes.
+
+### Validation changes
+
+Due to internal job serialization and validation changes you may run into
+issues using 0.5.5 command line tools such as `nomad run` and `nomad validate`
+with 0.5.4 or earlier agents.
+
+It is recommended you upgrade agents before or alongside your command line
+tools.
+
+## Nomad 0.4.0
+
+Nomad 0.4.0 has backward incompatible changes in the logic for Consul
+deregistration. When a Task which was started by Nomad v0.3.x is uncleanly shut
+down, the Nomad 0.4 Client will no longer clean up any stale services. If an
+in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
+shutting down and deregistering its Consul-registered services, the Nomad Client
+will not clean up the remaining Consul services registered with the 0.3
+Executor.
+
+We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
+node once the upgrade is complete.
+
+## Nomad 0.3.1
+
+Nomad 0.3.1 removes artifact downloading from driver configurations and places them as
+a first class element of the task. As such, jobs will have to be rewritten in
+the proper format and resubmitted to Nomad. Nomad clients will properly
+re-attach to existing tasks but job definitions must be updated before they can
+be dispatched to clients running 0.3.1.
+
+## Nomad 0.3.0
+
+Nomad 0.3.0 has made several substantial changes to job files included a new
+`log` block and variable interpretation syntax (`${var}`), a modified `restart`
+policy syntax, and minimum resources for tasks as well as validation. These
+changes require a slight change to the default upgrade flow.
+
+After upgrading the version of the servers, all previously submitted jobs must
+be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
+
+- All instances of `$var` must be converted to the new syntax of `${var}`
+
+- All tasks must provide their required resources for CPU, memory and disk as
+  well as required network usage if ports are required by the task.
+
+- Restart policies must be updated to indicate whether it is desired for the
+  task to restart on failure or to fail using `mode = "delay"` or `mode = "fail"` respectively.
+
+- Service names that include periods will fail validation. To fix, remove any
+  periods from the service name before running the job.
+
+After updating the Servers and job files, Nomad Clients can be upgraded by first
+draining the node so no tasks are running on it. This can be verified by running
+`nomad node status <node-id>` and verify there are no tasks in the `running`
+state. Once that is done the client can be killed, the `data_dir` should be
+deleted and then Nomad 0.3.0 can be launched.
+
+[`allow_caps`]: /nomad/docs/drivers/docker#allow_caps
+[`cap_net_raw`]: https://security.stackexchange.com/a/128988
+[`consul.allow_unauthenticated`]: /nomad/docs/configuration/consul#allow_unauthenticated
+[`distinct_hosts`]: /nomad/docs/job-specification/constraint#distinct_hosts
+[`distinct_property`]: /nomad/docs/job-specification/constraint#distinct_property
+[`extra_hosts`]: /nomad/docs/drivers/docker#extra_hosts
+[`linux capabilities`]: https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
+[`Local`]: /consul/docs/security/acl/tokens#token-attributes
+[`log_file`]: /nomad/docs/configuration#log_file
+[`raft protocol`]: /nomad/docs/configuration/server#raft_protocol
+[`rejoin_after_leave`]: /nomad/docs/configuration/server#rejoin_after_leave
+[`sidecar_task.config`]: /nomad/docs/job-specification/sidecar_task#config
+[`template.disable_file_sandbox`]: /nomad/docs/configuration/client#template-parameters
+[`vault.allow_unauthenticated`]: /nomad/docs/configuration/vault#allow_unauthenticated
+[`vault.policies`]: /nomad/docs/job-specification/vault#policies
+[`vault.task_token_ttl`]: /nomad/docs/configuration/vault#task_token_ttl
+[`vault.token`]: /nomad/docs/configuration/vault#token
+[`volume create`]: /nomad/docs/commands/volume/create
+[`volume register`]: /nomad/docs/commands/volume/register
+[`volume`]: /nomad/docs/job-specification/volume
+[alloc_overlap]: https://github.com/hashicorp/nomad/issues/10440
+[allow_caps_exec]: /nomad/docs/drivers/exec#allow_caps
+[allow_caps_java]: /nomad/docs/drivers/java#allow_caps
+[anon_token]: /consul/docs/security/acl/tokens#special-purpose-tokens
+[api_jobs_parse]: /nomad/api-docs/jobs#parse-job
+[artifact_env]: /nomad/docs/configuration/client#set_environment_variables
+[artifact_fs_isolation]: /nomad/docs/configuration/client#disable_filesystem_isolation
+[artifact_params]: /nomad/docs/job-specification/artifact#artifact-parameters
+[artifacts]: /nomad/docs/job-specification/artifact
+[cap_add_exec]: /nomad/docs/drivers/exec#cap_add
+[cap_drop_exec]: /nomad/docs/drivers/exec#cap_drop
+[cgroup_parent]: /nomad/docs/configuration/client#cgroup_parent
+[cgroups2]: https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html
+[client_artifact]: /nomad/docs/configuration/client#artifact-parameters
+[consul_acl]: https://github.com/hashicorp/consul/issues/7414
+[cores]: /nomad/docs/job-specification/resources#cores
+[cpu]: /nomad/docs/concepts/cpu
+[dangling_container_reconciliation]: /nomad/docs/drivers/docker#enabled
+[dangling-containers]: /nomad/docs/drivers/docker#dangling-containers
+[decompression_file_count_limit]: /nomad/docs/configuration/client#decompression_file_count_limit
+[decompression_size_limit]: /nomad/docs/configuration/client#decompression_size_limit
+[drain-api]: /nomad/api-docs/nodes#drain-node
+[drain-cli]: /nomad/docs/commands/node/drain
+[dst]: /nomad/docs/job-specification/periodic#daylight-saving-time
+[enterprise licensing]: /nomad/docs/enterprise/license
+[envoy_concurrency]: https://www.envoyproxy.io/docs/envoy/latest/operations/cli#cmdoption-concurrency
+[gh_10446]: https://github.com/hashicorp/nomad/pull/10446#issuecomment-1224833906
+[gh_issue]: https://github.com/hashicorp/nomad/issues/new/choose
+[gh-10875]: https://github.com/hashicorp/nomad/pull/10875
+[gh-11563]: https://github.com/hashicorp/nomad/issues/11563
+[gh-6787]: https://github.com/hashicorp/nomad/issues/6787
+[gh-8457]: https://github.com/hashicorp/nomad/issues/8457
+[gh-9148]: https://github.com/hashicorp/nomad/issues/9148
+[go-client]: https://pkg.go.dev/github.com/hashicorp/nomad/api#Client
+[hard_guide]: /nomad/docs/install/production/requirements#hardening-nomad
+[hcl2]: https://github.com/hashicorp/hcl2
+[kill_timeout]: /nomad/docs/job-specification/task#kill_timeout
+[landlock]: https://docs.kernel.org/userspace-api/landlock.html
+[limits]: /nomad/docs/configuration#limits
+[lxc]: /nomad/plugins/drivers/community/lxc
+[max_kill_timeout]: /nomad/docs/configuration/client#max_kill_timeout
+[migrate]: /nomad/docs/job-specification/migrate
+[Migrating to Using Workload Identity with Consul]: /nomad/docs/integrations/consul/acl#migrating-to-using-workload-identity-with-consul
+[Migrating to Using Workload Identity with Vault]: /nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault
+[no_net_raw]: /nomad/docs/upgrade/upgrade-specific#nomad-1-1-0-rc1-1-0-5-0-12-12
+[node drain]: /nomad/docs/upgrade#5-upgrade-clients
+[node pools]: /nomad/docs/concepts/node-pools
+[node_attributes]: /nomad/docs/runtime/interpolation#node-attributes
+[nvidia]: /nomad/plugins/devices/nvidia
+[oversub]: /nomad/docs/job-specification/resources#memory-oversubscription
+[pki]: /vault/docs/secrets/pki
+[plugin-block]: /nomad/docs/configuration/plugin
+[plugins]: /nomad/plugins/drivers/community
+[preemption-api]: /nomad/api-docs/operator#update-scheduler-configuration
+[preemption]: /nomad/docs/concepts/scheduling/preemption
+[proxy_concurrency]: /nomad/docs/job-specification/sidecar_task#proxy_concurrency
+[reserved]: /nomad/docs/configuration/client#reserved-parameters
+[`root_key_gc_interval`]: /nomad/docs/configuration/server#root_key_gc_interval
+[task-config]: /nomad/docs/job-specification/task#config
+[template_gid]: /nomad/docs/job-specification/template#gid
+[template_uid]: /nomad/docs/job-specification/template#uid
+[tls-guide]: /nomad/tutorials/transport-security/security-enable-tls
+[tls-vault-guide]: /nomad/tutorials/integrate-vault/vault-pki-nomad
+[update]: /nomad/docs/job-specification/update
+[upgrade process]: /nomad/docs/upgrade#upgrade-process
+[Upgrading to Raft Protocol 3]: /nomad/docs/upgrade#upgrading-to-raft-protocol-3
+[validate]: /nomad/docs/commands/job/validate
+[vault_grace]: /nomad/docs/job-specification/template
+[Workload Identity]: /nomad/docs/concepts/workload-identity
+[Process Isolation]: https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container#process-isolation
+[reschedule]: /nomad/docs/jobs-specification/reschedule
+[`infra_image`]: /nomad/docs/drivers/docker#infra_image
diff --git a/content/nomad/v1.9.x/content/docs/who-uses-nomad.mdx b/content/nomad/v1.9.x/content/docs/who-uses-nomad.mdx
new file mode 100644
index 0000000000..5611e253b1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/docs/who-uses-nomad.mdx
@@ -0,0 +1,115 @@
+---
+layout: docs
+page_title: Who Uses Nomad
+description: >-
+  Learn how companies use Nomad in production to solve critical, real-world business objectives.
+---
+
+# Who Uses Nomad
+
+This page features talks from users on how they use Nomad today to solve critical, real-world business objectives.
+
+#### Cloudflare
+
+- [How We Use HashiCorp Nomad (2020)](https://blog.cloudflare.com/how-we-use-hashicorp-nomad/)
+
+#### Target
+
+- [Nomad at Target: Scaling microservices across public and private clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+
+#### BetterHelp
+
+- [How the world's largest online therapy provider runs on Nomad (2020)](https://www.youtube.com/watch?v=eN2ghrGpiUo)
+
+#### Navi Capital
+
+- [How Nomad powers a \$1B hedge fund in Brazil (2020)](https://www.hashicorp.com/blog/nomad-community-story-navi-capital/)
+
+#### Trivago
+
+- [Maybe You Don’t Need Kubernetes (2019)](https://endler.dev/2019/maybe-you-dont-need-kubernetes/)
+- [Nomad - Our Experiences and Best Practices (2019)](https://tech.trivago.com/2019/01/25/nomad-our-experiences-and-best-practices/)
+
+#### Lob.com
+
+- [Hard pass Kubernetes, Hello Nomad! (2022)](https://www.lob.com/blog/alternative-to-kubernetes)
+
+#### Behavox
+
+- [Microservices Management in Behavox: Part 2 - Nomad (2023)](https://blog.behavox.engineering/microservices-management-in-behavox-part-2-nomad/)
+
+#### Reaktor
+
+- [Nomad - Kubernetes, but without the complexity (2019)](https://youtu.be/GkmyNBUugg8)
+
+#### Pandora
+
+- [How Pandora Uses Nomad (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&t=2s)
+
+#### CircleCI
+
+- [How CircleCI Processes 4.5 Million Builds Per Month (2019)](https://stackshare.io/circleci/how-circleci-processes-4-5-million-builds-per-month)
+- [Security & Scheduling are Not Your Core Competencies (2018)](https://www.hashicorp.com/resources/nomad-vault-circleci-security-scheduling)
+
+#### PagerDuty
+
+- [PagerDuty’s Nomadic Journey (2017)](https://www.hashicorp.com/resources/pagerduty-nomad-journey)
+
+#### Q2
+
+- [Q2’s Nomad Use and Overview (2019)](https://www.youtube.com/watch?v=OsZeKTP2u98&feature=youtu.be&t=1499)
+
+#### SAP
+
+- [HashiCorp Nomad @ SAP Ariba (2018)](https://www.hashicorp.com/resources/nomad-community-call-core-team-sap-ariba)
+
+#### Deluxe Entertainment
+
+- [How Deluxe Uses the Complete HashiStack for Video Production (2018)](https://www.hashicorp.com/resources/deluxe-hashistack-video-production)
+
+#### Citadel
+
+- [End-to-End Production Nomad at Citadel (2017)](https://www.hashicorp.com/resources/end-to-end-production-nomad-citadel)
+- [Extreme Scaling with HashiCorp Nomad & Consul (2016)](https://www.hashicorp.com/resources/citadel-scaling-hashicorp-nomad-consul)
+
+#### Jet.com (Walmart)
+
+- [Driving down costs at Jet.com with HashiCorp Nomad (2017)](https://www.hashicorp.com/resources/jet-walmart-hashicorp-nomad-azure-run-apps)
+
+#### Target
+
+- [Nomad at Target - Scaling Microservices Across Public and Private Clouds (2018)](https://www.hashicorp.com/resources/nomad-scaling-target-microservices-across-cloud)
+- [Playing with Nomad from HashiCorp (2017)](https://danielparker.me/nomad/hashicorp/schedulers/nomad/)
+
+#### Oscar Health
+
+- [Scalable CI at Oscar Health with Nomad and Docker (2018)](https://www.hashicorp.com/resources/scalable-ci-oscar-health-insurance-nomad-docker)
+
+#### eBay
+
+- [HashiStack at eBay - A Fully Containerized Platform Based on Infrastructure as Code (2018)](https://www.hashicorp.com/resources/ebay-hashistack-fully-containerized-platform-iac)
+
+#### Dutch National Police
+
+- [Going Cloud-Native at the Dutch National Police (2018)](https://www.hashicorp.com/resources/going-cloud-native-at-the-dutch-national-police)
+
+#### N26
+
+- [Tech at N26 - The Bank in the Cloud (2018)](https://medium.com/insiden26/tech-at-n26-the-bank-in-the-cloud-e5ff818b528b)
+
+#### Elsevier
+
+- [Elsevier’s Container Framework with Nomad, Terraform, and Consul (2017)](https://www.hashicorp.com/resources/elsevier-nomad-container-framework-demo)
+
+#### Graymeta
+
+- [Backend Batch Processing At Scale with Nomad (2017)](https://www.hashicorp.com/resources/backend-batch-processing-nomad)
+
+#### NIH NCBI
+
+- [NCBI’s Legacy Migration to Hybrid Cloud with Consul & Nomad (2018)](https://www.hashicorp.com/resources/ncbi-legacy-migration-hybrid-cloud-consul-nomad)
+
+#### imgix
+
+- [Cluster Schedulers & Why We Chose Nomad Over Kubernetes (2017)](https://medium.com/@copyconstruct/schedulers-kubernetes-and-nomad-b0f2e14a896)
+
diff --git a/content/nomad/v1.9.x/content/intro/index.mdx b/content/nomad/v1.9.x/content/intro/index.mdx
new file mode 100644
index 0000000000..32168c4c7f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/index.mdx
@@ -0,0 +1,55 @@
+---
+layout: intro
+page_title: Introduction to Nomad
+description: >-
+  Learn what Nomad is, what problems it can solve, its key features, and how it
+  compares to existing software.
+---
+
+# Introduction to Nomad
+
+Welcome to the intro guide to Nomad. This guide is the best place to start with Nomad. We cover what Nomad is, what problems it can solve, how it compares to existing software, and how you can get started using it. If you are familiar with the basics of Nomad, the [documentation](/nomad/docs) and [tutorials](/nomad/tutorials) provide a more detailed reference of available features.
+
+<iframe
+  src="https://www.youtube.com/embed/s_Fm9UtL4YU"
+  frameBorder="0"
+  allowFullScreen={true}
+  width="560"
+  height="315"
+></iframe>
+
+## What is Nomad?
+
+Nomad is a flexible workload orchestrator that enables an organization to easily deploy and manage any containerized or legacy application using a single, unified workflow. Nomad can run a diverse workload of Docker, non-containerized, microservice, and batch applications.
+
+Nomad enables developers to use declarative infrastructure-as-code for deploying applications. Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.
+
+Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.
+
+## Key features
+
+- **Deploy Containers and Legacy Applications**: Nomad’s flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable [task drivers](/nomad/docs/drivers).
+
+- **Simple & Reliable**: Nomad runs as a single binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.
+
+- **Device Plugins & GPU Support**: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses [device plugins](/nomad/plugins/devices) to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.
+
+- **Federation for Multi-Region**: Nomad has native support for multi-region federation. This built-in capability allows multiple clusters to be linked together, which in turn enables developers to deploy jobs to any cluster in any region. Federation also enables automatic replication of ACL policies, namespaces, resource quotas and Sentinel policies across all clusters.
+
+- **Proven Scalability**: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.
+
+- **HashiCorp Ecosystem**: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.
+
+## How Nomad compares to other tools
+
+Nomad differentiates from related tools by virtue of its **simplicity**, **flexibility**,
+**scalability**, and **high performance**. Nomad's synergy and integration points with
+HashiCorp Terraform, Consul, and Vault make it uniquely suited for easy integration into
+an organization's existing workflows, minimizing the time-to-market for critical initiatives.
+
+See the [Nomad vs. Other Software](/nomad/intro/vs) page for additional details and
+comparisons.
+
+## Next steps
+
+See the [Use Cases](/nomad/intro/use-cases) page to understand the many ways Nomad is used in production today across many industries to solve critical, real-world business objectives.
diff --git a/content/nomad/v1.9.x/content/intro/use-cases.mdx b/content/nomad/v1.9.x/content/intro/use-cases.mdx
new file mode 100644
index 0000000000..c6ff3ca583
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/use-cases.mdx
@@ -0,0 +1,70 @@
+---
+layout: intro
+page_title: Use Cases
+description: |-
+  Learn about Nomad's core use cases, such as Docker container orchestration, legacy application deployment, microservices, batch processing workloads, and multi-cloud federated deployemnts.
+---
+
+# Use Cases
+
+This page features Nomad's core use cases.
+
+Note that the full range of potential use cases is broader than what is covered here.
+
+## Docker container orchestration
+
+Organizations are increasingly moving towards a Docker centric workflow for
+application deployment and management. This transition requires new tooling
+to automate placement, perform job updates, enable self-service for developers,
+and to handle failures automatically. Nomad supports a [first-class Docker workflow](/nomad/docs/drivers/docker)
+and integrates seamlessly with [Consul](/nomad/docs/integrations/consul-integration)
+and [Vault](/nomad/docs/integrations/vault-integration) to enable a complete solution
+while maximizing operational flexibility. Nomad is easy to use, can scale to
+thousands of nodes in a single cluster, and can easily deploy across private data
+centers and multiple clouds.
+
+## Legacy application deployment
+
+A virtual machine based application deployment strategy can lead to low hardware
+utilization rates and high infrastructure costs. While a Docker-based deployment
+strategy can be impractical for some organizations or use cases, the potential for
+greater automation, increased resilience, and reduced cost is very attractive.
+Nomad natively supports running legacy applications, static binaries, JARs, and
+simple OS commands directly. Workloads are natively isolated at runtime and bin
+packed to maximize efficiency and utilization (reducing cost). Developers and
+operators benefit from API-driven automation and enhanced reliability for
+applications through automatic failure handling.
+
+## Microservices
+
+Microservices and Service Oriented Architectures (SOA) are a design paradigm in
+which many services with narrow scope, tight state encapsulation, and API driven
+communication interact together to form a larger solution. However, managing hundreds
+or thousands of services instead of a few large applications creates an operational
+challenge. Nomad elegantly integrates with [Consul](/nomad/docs/integrations/consul-integration)
+for automatic service registration and dynamic rendering of configuration files. Nomad
+and Consul together provide an ideal solution for managing microservices, making it
+easier to adopt the paradigm.
+
+## Batch processing workloads
+
+As data science and analytics teams grow in size and complexity, they increasingly
+benefit from highly performant and scalable tools that can run batch workloads with
+minimal operational overhead. Nomad can natively run batch jobs and [parameterized](https://www.hashicorp.com/blog/replacing-queues-with-nomad-dispatch) jobs.
+Nomad's architecture enables easy scalability and an optimistically
+concurrent scheduling strategy that can yield [thousands of container deployments per
+second](https://www.hashicorp.com/c1m). Alternatives are overly complex and limited
+in terms of their scheduling throughput, scalability, and multi-cloud capabilities.
+
+## Multi-Region and multi-cloud federated deployments
+
+Nomad is designed to natively handle multi-datacenter and multi-region deployments
+and is cloud agnostic. This allows Nomad to schedule in private datacenters running
+bare metal, OpenStack, or VMware alongside an AWS, Azure, or GCE cloud deployment.
+This makes it easier to migrate workloads incrementally and to utilize the cloud
+for bursting.
+
+
+Nomad now enables [Proof Key for Code Exchange
+(PKCE)](https://oauth.net/2/pkce/) by default for new or updated OIDC auth
+methods. Existing auth
diff --git a/content/nomad/v1.9.x/content/intro/vs/ecs.mdx b/content/nomad/v1.9.x/content/intro/vs/ecs.mdx
new file mode 100644
index 0000000000..689b8bde7a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/vs/ecs.mdx
@@ -0,0 +1,30 @@
+---
+layout: intro
+page_title: Nomad vs. AWS ECS
+description: Comparison between Nomad and AWS ECS
+---
+
+# Nomad vs. AWS ECS
+
+Amazon Web Services provides the Elastic Container Service (ECS), which is
+a cluster manager. The ECS service is only available within AWS and
+can only be used for Docker workloads. Amazon provides customers with
+the agent that is installed on EC2 instances, but does not provide
+the servers which are a hosted service of AWS.
+
+There are a number of fundamental differences between Nomad and ECS.
+Nomad is completely open source, including both the client and server
+components. By contrast, only the agent code for ECS is open and
+the servers are closed sourced and managed by Amazon.
+
+As a side effect of the ECS servers being managed by AWS, it is not possible
+to use ECS outside of AWS. Nomad is agnostic to the environment in which it is run,
+supporting public and private clouds, as well as bare metal datacenters.
+Clusters in Nomad can span multiple datacenters and regions, meaning
+a single cluster could be managing machines on AWS, Azure, and GCE simultaneously.
+
+The ECS service is specifically focused on containers and the Docker
+engine, while Nomad is more general purpose. Nomad supports virtualized,
+containerized, and standalone applications, including Docker. Nomad is
+designed with extensible drivers and support will be extended to all
+common drivers.
diff --git a/content/nomad/v1.9.x/content/intro/vs/index.mdx b/content/nomad/v1.9.x/content/intro/vs/index.mdx
new file mode 100644
index 0000000000..5907af86f0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/vs/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: Nomad vs. other software
+description: |-
+  Comparisons between Nomad and other cluster managers.
+---
+
+# Nomad vs. other software
+
+The following characteristics generally differentiate Nomad from related products:
+
+- **Simplicity**: Nomad runs as a single process with zero external dependencies.
+  Operators can easily provision, manage, and scale Nomad. Developers can easily
+  define and run applications.
+- **Flexibility**: Nomad can run a diverse workload of containerized, legacy,
+  microservice, and batch applications. Nomad can schedule service, batch
+  processing and system jobs, and can run on both Linux and Windows.
+- **Scalability and High Performance**: Nomad can schedule thousands of containers
+  per second, scale to thousands of nodes in a single cluster, and easily federate
+  across regions and cloud providers.
+- **HashiCorp Interoperability**: Nomad elegantly integrates with Vault for secrets
+  management and Consul for service discovery and dynamic configuration. Nomad's
+  Consul-like architecture and Terraform-like job specification lower the barrier
+  to entry for existing users of the HashiCorp stack.
+
+There are many relevant categories for comparison including cluster managers,
+resource managers, workload managers, and schedulers. There are many existing
+tools in each category, and the comparisons are not exhaustive of the entire space.
+
+Due to the bias of the comparisons being on the Nomad website, we attempt to only
+use facts. If you find something that is invalid or out of date in the comparisons,
+please [open an issue](https://github.com/hashicorp/nomad/issues) and we will
+address it as soon as possible.
+
+Use the navigation on the left to read comparisons of Nomad versus other systems.
diff --git a/content/nomad/v1.9.x/content/intro/vs/mesos.mdx b/content/nomad/v1.9.x/content/intro/vs/mesos.mdx
new file mode 100644
index 0000000000..472fbffc62
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/vs/mesos.mdx
@@ -0,0 +1,35 @@
+---
+layout: intro
+page_title: 'Nomad vs. Mesos with Aurora, Marathon, etc'
+description: Comparison between Nomad and Mesos with Marathon
+---
+
+# Nomad vs. Mesos with Marathon
+
+Mesos is a resource manager, which is used to pool together the
+resources of a datacenter and exposes an API to integrate with
+Frameworks that have scheduling and job management logic. Mesos
+depends on ZooKeeper to provide both coordination and storage.
+
+There are many different frameworks that integrate with Mesos;
+popular general purpose ones include Aurora and Marathon.
+These frameworks allow users to submit jobs and implement scheduling
+logic. They depend on Mesos for resource management, and external
+systems like ZooKeeper to provide coordination and storage.
+
+Nomad is architecturally much simpler. Nomad is a single binary, both for clients
+and servers, and requires no external services for coordination or storage.
+Nomad combines features of both resource managers and schedulers into a single system.
+This makes Nomad operationally simpler and enables more sophisticated
+optimizations.
+
+Nomad is designed to be a global state, optimistically concurrent scheduler.
+Global state means schedulers get access to the entire state of the cluster when
+making decisions enabling richer constraints, job priorities, resource preemption,
+and faster placements. Optimistic concurrency allows Nomad to make scheduling
+decisions in parallel increasing throughput, reducing latency, and increasing
+the scale that can be supported.
+
+Mesos does not support federation or multiple failure isolation regions.
+Nomad supports multi-datacenter and multi-region configurations for failure
+isolation and scalability.
diff --git a/content/nomad/v1.9.x/content/intro/vs/terraform.mdx b/content/nomad/v1.9.x/content/intro/vs/terraform.mdx
new file mode 100644
index 0000000000..a0047c4704
--- /dev/null
+++ b/content/nomad/v1.9.x/content/intro/vs/terraform.mdx
@@ -0,0 +1,31 @@
+---
+layout: intro
+page_title: Nomad vs. Terraform
+description: Comparison between Nomad and Terraform
+---
+
+# Nomad vs. Terraform
+
+[Terraform](https://www.terraform.io/) is a tool for building, changing, and versioning
+infrastructure safely and efficiently. Configuration files describe to Terraform
+the components needed to run a single application or your entire datacenter. Terraform
+generates an execution plan describing what it will do to reach the desired state,
+and then executes it to build the described infrastructure. As the configuration changes,
+Terraform is able to determine what changed and create incremental execution plans which can be applied.
+
+Nomad differs from Terraform in a number of key ways. Terraform is designed to support
+any type of resource including low-level components such as compute instances, storage,
+and networking, as well as high-level components such as DNS entries, SaaS features, etc.
+Terraform knows how to create, provision, and manage the lifecycle of these resources.
+Nomad runs on existing infrastructure and manages the lifecycle of applications running
+on that infrastructure.
+
+Another major distinction is that Terraform is an offline tool that runs to completion,
+while Nomad is an online system with long lived servers. Nomad allows new jobs to
+be submitted, existing jobs updated or deleted, and can handle node failures. This
+requires operating continuously instead of in a single shot like Terraform.
+
+For small infrastructures with only a handful of servers or applications, the complexity
+of Nomad may not outweigh simply using Terraform to statically assign applications to
+machines. At larger scales, Terraform should be used to provision capacity for Nomad,
+and Nomad used to manage scheduling applications to machines dynamically.
diff --git a/content/nomad/v1.9.x/content/partials/chroot-limitations.mdx b/content/nomad/v1.9.x/content/partials/chroot-limitations.mdx
new file mode 100644
index 0000000000..f576d37e95
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/chroot-limitations.mdx
@@ -0,0 +1,3 @@
+!> **Warning chroot limitations:** Nomad by default doesn't copy the ephemeral runtime files in the `/run` directory. For exampe, on Ubuntu, `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, so Nomad doesn't copy `resolv.conf` to the chroot environment.
+
+In these cases, configure your job's [network block](/nomad/docs/job-specification/network) for each chroot task.
diff --git a/content/nomad/v1.9.x/content/partials/envvars.mdx b/content/nomad/v1.9.x/content/partials/envvars.mdx
new file mode 100644
index 0000000000..1ed32107d4
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/envvars.mdx
@@ -0,0 +1,75 @@
+### Job-related variables
+
+| Variable                 | Description                                                                                                                                                                                                                                                                              |
+|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_ALLOC_DIR`        | The path to the shared `alloc/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                              |
+| `NOMAD_TASK_DIR`         | The path to the task `local/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_SECRETS_DIR`      | Path to the task's `secrets/` directory. See the [Runtime Task Directories documentation][taskdirs] for more information.                                                                                                                                                                |
+| `NOMAD_MEMORY_LIMIT`     | Memory limit in MB for the task                                                                                                                                                                                                                                                          |
+| `NOMAD_MEMORY_MAX_LIMIT` | The maximum memory limit the task may use if client has excess memory capacity, in MB. Omitted if task isn't configured with memory oversubscription.                                                                                                                                    |
+| `NOMAD_CPU_LIMIT`        | CPU limit in MHz for the task                                                                                                                                                                                                                                                            |
+| `NOMAD_CPU_CORES`        | The specific CPU cores reserved for the task in cpuset list notation. Omitted if the task does not request CPU cores. For example, `0-2,7,12-14`                                                                                                                                         |
+| `NOMAD_ALLOC_ID`         | Allocation ID of the task                                                                                                                                                                                                                                                                |
+| `NOMAD_SHORT_ALLOC_ID`   | The first 8 characters of the allocation ID of the task                                                                                                                                                                                                                                  |
+| `NOMAD_ALLOC_NAME`       | Allocation name of the task. This is derived from the job name, task group name, and allocation index.                                                                                                                                                                                   |
+| `NOMAD_ALLOC_INDEX`      | Allocation index; useful to distinguish instances of task groups. From 0 to (count - 1). For system jobs and sysbatch jobs, this value will always be 0. The index is unique within a given version of a job, but canaries or failed tasks in a deployment may reuse the index.          |
+| `NOMAD_TASK_NAME`        | Task's name                                                                                                                                                                                                                                                                              |
+| `NOMAD_GROUP_NAME`       | Group's name                                                                                                                                                                                                                                                                             |
+| `NOMAD_JOB_ID`           | Job's ID, which is equal to the Job name when submitted through the command-line tool but can be different when using the API                                                                                                                                                            |
+| `NOMAD_JOB_NAME`         | Job's name                                                                                                                                                                                                                                                                               |
+| `NOMAD_JOB_PARENT_ID`    | ID of the Job's parent if it has one                                                                                                                                                                                                                                                     |
+| `NOMAD_DC`               | Datacenter in which the allocation is running                                                                                                                                                                                                                                            |
+| `NOMAD_PARENT_CGROUP`    | The parent cgroup used to contain task cgroups (Linux only)                                                                                                                                                                                                                              |
+| `NOMAD_NAMESPACE`        | Namespace in which the allocation is running                                                                                                                                                                                                                                             |
+| `NOMAD_REGION`           | Region in which the allocation is running                                                                                                                                                                                                                                                |
+| `NOMAD_META_<key>`       | The metadata value given by `key` on the task's metadata. Any character in a key other than `[A-Za-z0-9_.]` will be converted to `_`. <br/> **Note:** this is different from [`${meta.<key>}`](/nomad/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata. |
+| `CONSUL_HTTP_TOKEN`      | The tasks' Consul token. See [Consul Integration][consul] documentation for more details.                                                                                                                                                                                                |
+| `CONSUL_TOKEN`           | The tasks' Consul token. See [Consul Integration][consul] documentation for more details. This variable is deprecated and exists only for backwards compatibility.                                                                                                                       |
+| `VAULT_TOKEN`            | The task's Vault token. See the [Vault Integration][vault] documentation for more details                                                                                                                                                                                                |
+
+
+### Network-related Variables
+
+| Variable                           | Description                                                                                                                                                                                                                                             |
+|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `NOMAD_IP_<label>`                 | Host IP for the given port `label`. See the [`network` block documentation][network-block] for more information.                                                                                                                                        |
+| `NOMAD_PORT_<label>`               | Port for the given port `label`. Driver-specified port when a port map is used, otherwise the host's static or dynamic port allocation. Services should bind to this port. See the [`network` block documentation][network-block] for more information. |
+| `NOMAD_ADDR_<label>`               | Host `IP:Port` pair for the given port `label`.                                                                                                                                                                                                         |
+| `NOMAD_ALLOC_INTERFACE_<label>`    | The configured network namespace interface for the given port `label` when using bridged or CNI networking.                                                                                                                                             |
+| `NOMAD_ALLOC_IP_<label>`           | The configured network namespace IP for the given port `label` when using bridged or CNI networking.                                                                                                                                                    |
+| `NOMAD_ALLOC_ADDR_<label>`         | The configured network namespace `IP:Port` pair for the given port `label` when using bridged or CNI networking.                                                                                                                                        |
+| `NOMAD_HOST_PORT_<label>`          | Port on the host for the port `label`. See the [**Mapped Ports**](/nomad/docs/job-specification/network#mapped-ports) section of the `network` block documentation for more information.                                                                |
+| `NOMAD_UPSTREAM_IP_<service>`      | IP for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                          |
+| `NOMAD_UPSTREAM_PORT_<service>`    | Port for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                                        |
+| `NOMAD_UPSTREAM_ADDR_<service>`    | Host `IP:Port` for the given `service` when defined as a Consul service mesh [upstream][].                                                                                                                                                              |
+| `NOMAD_ENVOY_ADMIN_ADDR_<service>` | Local address `127.0.0.2:Port` for the admin port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+| `NOMAD_ENVOY_READY_ADDR_<service>` | Local address `127.0.0.1:Port` for the ready port of the envoy sidecar for the given `service` when defined as a Consul service mesh enabled service. Envoy runs inside the group network namespace unless configured for host networking.              |
+
+<Note>
+
+Nomad replaces characters that are neither alphanumeric nor underscores in
+port labels or task names with underscores when generating environment variable
+names such as `NOMAD_ADDR_<task>_<label>`
+
+</Note>
+
+### Consul-related Variables
+
+<Note>These variables are only set for Consul service mesh native tasks.</Note>
+
+| Variable                 | Description                                                                                                                                                                                        |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CONSUL_HTTP_ADDR`       | Specifies the address to the local Consul agent. Will be automatically set to a unix domain socket in bridge networking mode, or a TCP address in host networking mode.                            |
+| `CONSUL_HTTP_TOKEN`      | Specifies the Consul ACL token used to authorize with Consul. Will be automatically set to a generated Consul service identity token specific to the service instance if Consul ACLs are enabled.  |
+| `CONSUL_HTTP_SSL`        | Specifies whether HTTPS should be used when communicating with Consul. Will be automatically set to true if Nomad is configured to communicate with Consul using TLS.                              |
+| `CONSUL_HTTP_SSL_VERIFY` | Specifies whether the HTTPS connection with Consul should be mutually verified. Will be automatically set to true if Nomad is configured to verify TLS certificates.                               |
+| `CONSUL_CACERT`          | Specifies the path to the CA certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                       |
+| `CONSUL_CLIENT_CERT`     | Specifies the path to the Client certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                                   |
+| `CONSUL_CLIENT_KEY`      | Specifies the path to the Client Key certificate used for Consul communication. Will be automatically set if Nomad is configured with the `consul.share_ssl` option.                               |
+| `CONSUL_TLS_SERVER_NAME` | Specifies the server name to use as the SNI host for Consul communication. Will be automatically set if Consul is configured to use TLS and the task is in a group using bridge networking mode.   |
+
+[upstream]: /nomad/docs/job-specification/upstreams
+[taskdirs]: /nomad/docs/runtime/environment#task-directories
+[network-block]: /nomad/docs/job-specification/network
+[vault]: /nomad/docs/integrations/vault-integration
+[consul]: /nomad/docs/integrations/consul-integration
diff --git a/content/nomad/v1.9.x/content/partials/general_options.mdx b/content/nomad/v1.9.x/content/partials/general_options.mdx
new file mode 100644
index 0000000000..577dd6e5ca
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/general_options.mdx
@@ -0,0 +1,45 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-namespace=<namespace>`: The target namespace for queries and actions bound
+  to a namespace. Overrides the `NOMAD_NAMESPACE` environment variable if set.
+  If set to `'*'`, subcommands which support this functionality query all
+  namespaces authorized to user. Defaults to the "default" namespace.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.9.x/content/partials/general_options_no_namespace.mdx b/content/nomad/v1.9.x/content/partials/general_options_no_namespace.mdx
new file mode 100644
index 0000000000..389a404310
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/general_options_no_namespace.mdx
@@ -0,0 +1,40 @@
+- `-address=<addr>`: The address of the Nomad server. Overrides the `NOMAD_ADDR`
+  environment variable if set. Defaults to `http://127.0.0.1:4646`.
+
+- `-region=<region>`: The region of the Nomad server to forward commands to.
+  Overrides the `NOMAD_REGION` environment variable if set. Defaults to the
+  Agent's local region.
+
+- `-no-color`: Disables colored command output. Alternatively,
+  `NOMAD_CLI_NO_COLOR` may be set. This option takes precedence over
+  `-force-color`.
+
+- `-force-color`: Forces colored command output. This can be used in cases where
+  the usual terminal detection fails. Alternatively, `NOMAD_CLI_FORCE_COLOR`
+  may be set. This option has no effect if `-no-color` is also used.
+
+- `-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify the
+  Nomad server SSL certificate. Overrides the `NOMAD_CACERT` environment
+  variable if set.
+
+- `-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to verify
+  the Nomad server SSL certificate. If both `-ca-cert` and `-ca-path` are
+  specified, `-ca-cert` is used. Overrides the `NOMAD_CAPATH` environment
+  variable if set.
+
+- `-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-client-key`. Overrides
+  the `NOMAD_CLIENT_CERT` environment variable if set.
+
+- `-client-key=<path>`: Path to an unencrypted PEM encoded private key matching
+  the client certificate from `-client-cert`. Overrides the `NOMAD_CLIENT_KEY`
+  environment variable if set.
+
+- `-tls-server-name=<value>`: The server name to use as the SNI host when connecting
+  via TLS. Overrides the `NOMAD_TLS_SERVER_NAME` environment variable if set.
+
+- `-tls-skip-verify`: Do not verify TLS certificate. This is highly not
+  recommended. Verification will also be skipped if `NOMAD_SKIP_VERIFY` is set.
+
+- `-token`: The SecretID of an ACL token to use to authenticate API requests with.
+  Overrides the `NOMAD_TOKEN` environment variable if set.
diff --git a/content/nomad/v1.9.x/content/partials/install/bridge-iptables.mdx b/content/nomad/v1.9.x/content/partials/install/bridge-iptables.mdx
new file mode 100644
index 0000000000..d8f52f5b42
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/install/bridge-iptables.mdx
@@ -0,0 +1,38 @@
+Nomad's task group networks integrate with Consul's service mesh using bridge
+networking and iptables to send traffic between containers.
+
+~> **Warning:** New Linux versions, such as Ubuntu 24.04, may not enable bridge
+networking by default. Use `sudo modprobe bridge` to load the bridge module if
+it is missing.
+
+The Linux kernel bridge module has three tunable parameters that control whether
+iptables processes traffic crossing the bridge. Some operating systems,
+including RedHat, CentOS, and Fedora, might have iptables rules that are not
+correctly configured for guest traffic because these tunable parameters are
+optimized for VM workloads.
+
+Ensure your Linux operating system distribution is configured to allow iptables
+to route container traffic through the bridge network. Run the following
+commands to set the tunable parameters to allow iptables processing for the
+bridge network.
+
+```shell-session
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+$ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a client node, add a file to
+`/etc/sysctl.d/` or remove the file your Linux distribution puts in that
+directory. The following example configures the tunable parameters for a client
+node.
+
+<CodeBlockConfig filename="/etc/sysctl.d/bridge.conf">
+
+```ini
+net.bridge.bridge-nf-call-arptables = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+net.bridge.bridge-nf-call-iptables = 1
+```
+
+</CodeBlockConfig>
diff --git a/content/nomad/v1.9.x/content/partials/install/cgroup-controllers.mdx b/content/nomad/v1.9.x/content/partials/install/cgroup-controllers.mdx
new file mode 100644
index 0000000000..bb25000698
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/install/cgroup-controllers.mdx
@@ -0,0 +1,22 @@
+On Linux, Nomad uses cgroups to control access to resources like CPU and memory.
+Nomad supports both [cgroups
+v2](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html) and the
+legacy [cgroups
+v1](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/cgroups.html).
+When Nomad clients start, they determine the available cgroup controllers and
+include the attribute `os.cgroups.version` in their fingerprint.
+
+On cgroups v2, you can run the following command to verify that you have all
+required controllers.
+
+```shell-session
+$ cat /sys/fs/cgroup/cgroup.controllers
+cpuset cpu io memory pids
+```
+
+On legacy cgroups v1, this same list of required controllers appears as a series
+of sub-directories under the directory `/sys/fs/cgroup`.
+
+Refer to the [cgroup controller
+requirements](/nomad/docs/install/production/requirements#cgroup-controllers)
+for more details and to enable missing cgroups.
diff --git a/content/nomad/v1.9.x/content/partials/install/install-cni-plugins.mdx b/content/nomad/v1.9.x/content/partials/install/install-cni-plugins.mdx
new file mode 100644
index 0000000000..cf133a47b2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/install/install-cni-plugins.mdx
@@ -0,0 +1,27 @@
+Nomad uses CNI plugins to configure network namespaces when using the `bridge`
+network mode. You must install the CNI plugins on all Linux Nomad client nodes
+that use network namespaces. Refer to the [CNI Plugins external
+guide](https://www.cni.dev/plugins/current/) for details on individual plugins.
+
+The following series of commands determines your operating system architecture,
+downloads the [CNI 1.6.2
+release](https://github.com/containernetworking/plugins/releases/tag/v1.6.2),
+and then extracts the CNI plugin binaries into the `/opt/cni/bin` directory.
+Update the `CNI_PLUGIN_VERSION` value to use a different release version.
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ export CNI_PLUGIN_VERSION=v1.6.2
+$ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/${CNI_PLUGIN_VERSION}/cni-plugins-linux-${ARCH_CNI}-${CNI_PLUGIN_VERSION}".tgz && \
+  sudo mkdir -p /opt/cni/bin && \
+  sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Your Linux distribution's package manager may provide the CNI reference plugins
+but we recommend installing the most recent stable version to ensure you have
+fixes for known bugs shipping in those versions.
+
+Nomad looks for CNI plugin binaries by default in the `/opt/cni/bin` directory.
+However, you may install in the binaries in a different directory and then
+configure using the [`cni_path`](/nomad/docs/configuration/client#cni_path)
+attribute.
diff --git a/content/nomad/v1.9.x/content/partials/install/install-consul-cni-plugin.mdx b/content/nomad/v1.9.x/content/partials/install/install-consul-cni-plugin.mdx
new file mode 100644
index 0000000000..654db0ac57
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/install/install-consul-cni-plugin.mdx
@@ -0,0 +1,53 @@
+When you use the [`transparent_proxy`
+block](/nomad/docs/job-specification/transparent_proxy) for Consul service mesh,
+you must also install the [`consul-cni`
+plugin](https://releases.hashicorp.com/consul-cni) on each client node for
+Consul to properly redirect inbound and outbound traffic for services to the
+Envoy proxy. For more information, refer to [Enable the Consul CNI
+plugin](/consul/docs/k8s/connect/transparent-proxy/enable-transparent-proxy#enable-the-consul-cni-plugin)
+in the Consul documentation.
+
+You must install the CNI plugins before you install the Consul CNI plugin. The
+following commands assume that you already installed the CNI plugins.
+
+Install the `consul-cni` plugin on each client node.
+
+<Tabs>
+<Tab heading="Ubuntu/Debian" group="ubuntu">
+
+```shell-session
+$ sudo apt-get install -y consul-cni
+```
+
+</Tab>
+<Tab heading="RHEL/CentOS" group="rhel">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Fedora" group="fedora">
+
+```shell-session
+$ sudo dnf -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Amazon Linux" group="amazonlinux">
+
+```shell-session
+$ sudo yum -y install consul-cni
+```
+
+</Tab>
+<Tab heading="Manual" group="linux-manual">
+
+```shell-session
+$ export ARCH_CNI=$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)
+$ curl -L -o consul-cni.zip "https://releases.hashicorp.com/consul-cni/1.5.1/consul-cni_1.5.1_linux_${ARCH_CNI}".zip && \
+  sudo unzip consul-cni.zip -d /opt/cni/bin -x LICENSE.txt
+```
+
+</Tab>
+</Tabs>
diff --git a/content/nomad/v1.9.x/content/partials/install/manual-install.mdx b/content/nomad/v1.9.x/content/partials/install/manual-install.mdx
new file mode 100644
index 0000000000..da34c10bb6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/install/manual-install.mdx
@@ -0,0 +1,4 @@
+Download a [precompiled binary](https://releases.hashicorp.com/nomad/), verify
+the binary using the available SHA-256 sums, and unzip the package to a location
+on your machine. Make sure that the location of the `nomad` binary is available
+on your `PATH` before continuing with the other guides.
diff --git a/content/nomad/v1.9.x/content/partials/job-status-map.mdx b/content/nomad/v1.9.x/content/partials/job-status-map.mdx
new file mode 100644
index 0000000000..16322a24f3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/job-status-map.mdx
@@ -0,0 +1,17 @@
+Nomad uses one of these values to describe a job's status:
+
+- `dead`
+- `running`
+
+The CLI returns these rigid statuses, which are useful for scheduling and
+garbage collection. However, the Nomad UI displays additional human-readable
+statuses to help you manage jobs.
+
+The following table maps the CLI statuses to the statuses that appear in the
+Nomad UI.
+
+| CLI status       | UI status |
+| ---------------- | --------- |
+| `dead`           | `Complete`, `Failed`, `Scaled Down` |
+| `dead (stopped)` | `Stopped` |
+| `running`        | `Degraded`, `Deploying`, `Healthy`, `Recovering`, `Running`, `Scaled Down` |
diff --git a/content/nomad/v1.9.x/content/partials/jwt_claim_mapping_details.mdx b/content/nomad/v1.9.x/content/partials/jwt_claim_mapping_details.mdx
new file mode 100644
index 0000000000..674428c2a0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/jwt_claim_mapping_details.mdx
@@ -0,0 +1,80 @@
+## Trusted Identity Attributes via Claim Mappings
+
+The authentication step can return data from JWT claims as trusted
+identity attributes for use in binding rule selectors and bind name
+interpolation.
+
+The `ClaimMappings` and `ListClaimMappings` attributes control how Nomad maps claims
+to identity attributes. Both are maps of items to copy,
+with elements of the form `"<JWT claim>":"<attribute suffix>"`.
+
+Use `ClaimMappings` to map singular values and `ListClaimMappings` to map lists of values.
+
+This examples contains `ClaimMappings` and `ListClaimMappings`. The configuration
+instructs Nomad to copy the values in the JWT claims `"givenName"` and `"surname"`
+to attributes named `"value.first_name"` and `"value.last_name"` respectively.
+Additionally, Nomad should copy the list of values in the JWT
+claim `"groups"`  to an attribute named `"list.roles"`.
+
+```json
+{
+  "Name": "example-auth-method",
+  "Type": "<jwt|oidc>",
+  "Description": "Example auth method",
+  "Config": {
+    "ClaimMappings": {
+      "givenName": "first_name",
+      "surname": "last_name"
+    },
+    "ListClaimMappings": {
+      "groups": "roles"
+    }
+  }
+}
+```
+
+The following table shows the resulting attributes and
+the ways they may be used in rule bindings:
+
+| Attributes         | Supported selector operations                      | Can be interpolated |
+| ------------------ | -------------------------------------------------- | ------------------- |
+| `value.first_name` | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `value.last_name`  | Equal, Not Equal, In, Not In, Matches, Not Matches | yes                 |
+| `list.groups`      | In, Not In, Is Empty, Is Not Empty                 | no                  |
+
+Refer to the [binding-rule] documentation for more examples on using selectors.
+
+### Claim Specifications and JSON Pointer
+
+Use the `ClaimMappings` and `ListClaimMappings` fields to point to data
+within the JWT. If the desired key is at the top of level of the JWT, you may
+provide the name directly. If it is nested at a lower level, you may use a JSON
+Pointer.
+
+This example shows decoded JWT claims.
+
+```json
+{
+  "division": "North America",
+  "groups": {
+    "primary": "Engineering",
+    "secondary": "Software"
+  },
+  "iss": "https://my-corp-app-name.auth0.com/",
+  "sub": "auth0|eiw7OWoh5ieSh7ieyahC3ief0uyuraphaengae9d",
+  "aud": "V1RPi2MYptMV1RPi2MYptMV1RPi2MYpt",
+  "iat": 1589224148,
+  "exp": 1589260148,
+  "nonce": "eKiihooH3Fah8Ieshah4leeti6ien3"
+}
+```
+
+Use the following syntax to reference data:
+
+- Top-level key: Use direct reference. For example, `"division"` refers to `"North America"`.
+- Nested key: Use JSON Pointer syntax. For example, `"/groups/primary"` refers to `"Engineering"`.
+
+You may use any valid JSON Pointer as a selector. Refer to the [JSON Pointer
+RFC](https://tools.ietf.org/html/rfc6901) for a full description of the syntax.
+
+[binding-rule]: /nomad/docs/commands/acl/binding-rule/create#examples
diff --git a/content/nomad/v1.9.x/content/partials/task-driver-intro.mdx b/content/nomad/v1.9.x/content/partials/task-driver-intro.mdx
new file mode 100644
index 0000000000..794940bc12
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/task-driver-intro.mdx
@@ -0,0 +1,61 @@
+## Introduction
+
+Nomad clients use task drivers to execute a task and provide resource isolation.
+Extensible task drivers provide Nomad the flexibility to support a broad
+set of workloads across all major operating systems.
+
+Task driver resource isolation provides a degree of separation for Nomad's client
+CPU, memory, and storage between tasks. Resource isolation effectiveness depends
+upon individual task driver implementations and underlying client operating
+systems. Task drivers include various security-related controls, but do not
+use the Nomad client-to-task interface as a security boundary.
+Refer to the [access control guide][acl_guide] for more information on how to
+protect Nomad cluster operations.
+
+## Configuration
+
+Refer to the [plugin block documentation][plugin] for examples on how to use the
+plugin block in Nomad's client configuration. Review the [Docker driver's client
+requirements section][docker_plugin] for a detailed example.
+
+## Nomad task drivers
+
+The Nomad binary contains several bundled task drivers. We also support
+additional task driver plugins that you may install separately.
+
+| Bundled with Nomad   | Plugins               |
+|----------------------|-----------------------|
+| [Docker]             | [Exec2]               |
+| [Isolated Fork/Exec] | [Podman]              |
+| [Java]               | [Virt]                |
+| [QEMU]               |                       |
+| [Raw Fork/Exec]      |                       |
+
+Each task driver page documents the configuration available in a [job
+specification](/nomad/docs/job-specification), the environments you can use the
+task driver in, and the resource isolation mechanisms available.
+
+## Community task drivers
+
+You may also use [community-supported task driver
+plugins](/nomad/plugins/drivers/community/).
+
+## Create task drivers
+
+Nomad's task driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[plugin]: /nomad/docs/configuration/plugin
+[docker_plugin]: /nomad/docs/drivers/docker#client-requirements
+[plugin_guide]: /nomad/docs/concepts/plugins/task-drivers
+[acl_guide]: /nomad/tutorials/access-control
+[Docker]: /nomad/docs/drivers/docker
+[Exec2]: /nomad/plugins/drivers/exec2
+[Isolated Fork/Exec]: /nomad/docs/drivers/exec
+[Podman]: /nomad/plugins/drivers/podman
+[Java]: /nomad/docs/drivers/java
+[Virt]: /nomad/plugins/drivers/virt/index
+[QEMU]: /nomad/docs/drivers/qemu
+[Raw Fork/Exec]: /nomad/docs/drivers/raw_exec
diff --git a/content/nomad/v1.9.x/content/partials/version/tag-reason.mdx b/content/nomad/v1.9.x/content/partials/version/tag-reason.mdx
new file mode 100644
index 0000000000..aad3aba7cd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/version/tag-reason.mdx
@@ -0,0 +1,4 @@
+Applying a tag to a version prevents Nomad from garbage collecting that version.
+You can compare versions by tag name as well as version number.
+
+Tag names must be unique per job.
diff --git a/content/nomad/v1.9.x/content/partials/virt-beta-callout.mdx b/content/nomad/v1.9.x/content/partials/virt-beta-callout.mdx
new file mode 100644
index 0000000000..23c97213e3
--- /dev/null
+++ b/content/nomad/v1.9.x/content/partials/virt-beta-callout.mdx
@@ -0,0 +1,6 @@
+<Note title="Beta Feature">
+
+The Virt task driver is under active development. Refer to the [repo
+README](https://github.com/hashicorp/nomad-driver-virt) for the latest updates. Do not use this driver in production environments.
+
+</Note>
diff --git a/content/nomad/v1.9.x/content/plugins/devices/index.mdx b/content/nomad/v1.9.x/content/plugins/devices/index.mdx
new file mode 100644
index 0000000000..9993dbf5d1
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/devices/index.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: Nomad device driver plugins
+description: |-
+  Use device driver plugins to detect your Nomad client's physical hardware devices, such as graph processing units (GPUs), field programmable gate arrays (FPGAs), tensor processing units (TPUs), and universal serial buses (USBs). You can then use those devices in your Nomad workloads. Review conceptual, installation, usage, and reference information for the NVIDIA and USB device driver plugins.
+---
+
+# Nomad device driver plugins
+
+Use device driver plugins to detect physical hardware devices, such as graph
+processing units (GPUs), a field-programmable gate arrays (FPGAs), and universal
+serial buses (USBs), on your Nomad clients. You can then use those devices in
+your Nomad workloads.
+
+By having extensible device plugins, Nomad has the flexibility
+to support a broad set of devices and allows the community to build additional
+device plugins as needed.
+
+## Nomad device drivers
+
+We support the [NVIDIA] device driver plugin, which you must install
+separately. Refer to the [NVIDIA] documentation for instructions.
+
+## Community Device Drivers
+
+The community supports the [USB] device driver plugin.
+
+## Create device drivers
+
+Nomad's device driver architecture is pluggable, which gives you the flexibility
+to create your own drivers without having to recompile Nomad. Refer to the
+[plugin authoring guide][plugin_guide] for details.
+
+
+[NVIDIA]: /nomad/plugins/devices/nvidia
+[USB]: /nomad/plugins/devices/usb
+[plugin_guide]: /nomad/docs/concepts/plugins/devices
diff --git a/content/nomad/v1.9.x/content/plugins/devices/nvidia.mdx b/content/nomad/v1.9.x/content/plugins/devices/nvidia.mdx
new file mode 100644
index 0000000000..88f7f5a5ae
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/devices/nvidia.mdx
@@ -0,0 +1,241 @@
+---
+layout: docs
+page_title: NVIDIA GPU device plugin
+description: The NVIDIA GPU device plugin exposes NVIDIA GPUs to Nomad so you can run workloads on GPU hardware. Install and configure the plugin on your Nomad clients. Configure job tasks to use GPUs
+---
+
+# NVIDIA GPU device plugin
+
+Name: `nomad-device-nvidia`
+
+Use the NVIDIA device plugin to expose NVIDIA graphical processing units (GPUs)
+to Nomad. The driver automatically supports [Multi-Instance GPU (MIG)][mig].
+
+The NVIDIA device plugin uses [NVML] bindings to get data regarding available
+NVIDIA devices and then exposes them via [Fingerprint RPC]. The plugin detects
+whether the GPU has Multi-Instance GPU enabled, and when enabled, the plugin
+fingerprints all instances as individual GPUs. You may exclude GPUs from
+fingerprinting by setting the [`ignored_gpu_ids` field](#plugin-configuration).
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit     |
+|------------------|----------|
+| memory           | MiB      |
+| power            | W (Watt) |
+| bar1             | MiB      |
+| driver_version   | string   |
+| cores_clock      | MHz      |
+| memory_clock     | MHz      |
+| pci_bandwidth    | MB/s     |
+| display_state    | string   |
+| persistence_mode | string   |
+
+## Runtime Environment
+
+The `nvidia-gpu` device plugin exposes the following environment variables:
+
+- `NVIDIA_VISIBLE_DEVICES` - List of NVIDIA GPU IDs available to the task.
+
+### Additional Task Configurations
+
+Additional environment variables can be set by the task to influence the runtime
+environment. See [Nvidia's
+documentation](https://github.com/NVIDIA/nvidia-container-runtime#environment-variables-oci-spec).
+
+## Installation Requirements
+
+In order to use the `nomad-device-nvidia` device driver the following prerequisites must be met:
+
+1. GNU/Linux x86_64 with kernel version > 3.10
+2. NVIDIA GPU with Architecture > Fermi (2.1)
+3. NVIDIA drivers >= 340.29 with binary `nvidia-smi`
+4. Docker v19.03+
+
+### Container Toolkit Installation
+
+Follow the [NVIDIA Container Toolkit installation instructions][nvidia_container_toolkit]
+from NVIDIA to prepare a machine to use docker containers with NVIDIA GPUs. You should
+be able to run this simple command to test your environment and produce meaningful
+output.
+
+```shell
+docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi
+```
+
+
+## Plugin Configuration
+
+```hcl
+plugin "nomad-device-nvidia" {
+  config {
+    enabled            = true
+    ignored_gpu_ids    = ["GPU-fef8089b", "GPU-ac81e44d"]
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `nomad-device-nvidia` device plugin supports the following configuration in the agent
+config:
+
+- `enabled` `(bool: true)` - Control whether the plugin should be enabled and running.
+
+- `ignored_gpu_ids` `(array<string>: [])` - Specifies the set of GPU UUIDs that
+  should be ignored when fingerprinting.
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint for
+  device changes.
+
+## Limitations
+
+The NVIDIA integration only works with drivers who natively integrate with
+NVIDIA's [container runtime
+library](https://github.com/NVIDIA/libnvidia-container).
+
+Nomad has tested support with the [`docker` driver][docker-driver].
+
+## Source Code & Compiled Binaries
+
+The source code for this plugin can be found at hashicorp/nomad-device-nvidia. You
+can also find pre-built binaries on the [releases page][nvidia_plugin_download].
+
+## Examples
+
+Inspect a node with a GPU:
+
+```shell-session
+$ nomad node status 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+```
+
+Display detailed statistics on a node with a GPU:
+
+```shell-session
+$ nomad node status -stats 4d46e59f
+
+// ...TRUNCATED...
+
+Device Resource Utilization
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+// ...TRUNCATED...
+
+Device Stats
+Device              = nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]
+BAR1 buffer state   = 2 / 16384 MiB
+Decoder utilization = 0 %
+ECC L1 errors       = 0
+ECC L2 errors       = 0
+ECC memory errors   = 0
+Encoder utilization = 0 %
+GPU utilization     = 0 %
+Memory state        = 0 / 11441 MiB
+Memory utilization  = 0 %
+Power usage         = 37 / 149 W
+Temperature         = 34 C
+```
+
+Run the following example job to see that the GPU was mounted in the
+container:
+
+```hcl
+job "gpu-test" {
+  datacenters = ["dc1"]
+  type = "batch"
+
+  group "smi" {
+    task "smi" {
+      driver = "docker"
+
+      config {
+        image = "nvidia/cuda:11.0-base"
+        command = "nvidia-smi"
+      }
+
+      resources {
+        device "nvidia/gpu" {
+          count = 1
+
+          # Add an affinity for a particular model
+          affinity {
+            attribute = "${device.model}"
+            value     = "Tesla K80"
+            weight    = 50
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell-session
+$ nomad run example.nomad.hcl
+==> Monitoring evaluation "21bd7584"
+    Evaluation triggered by job "gpu-test"
+    Allocation "d250baed" created: node "4d46e59f", group "smi"
+    Evaluation status changed: "pending" -> "complete"
+==> Evaluation "21bd7584" finished with status "complete"
+
+$ nomad alloc status d250baed
+
+// ...TRUNCATED...
+
+Task "smi" is "dead"
+Task Resources
+CPU        Memory       Disk     Addresses
+0/100 MHz  0 B/300 MiB  300 MiB
+
+Device Stats
+nvidia/gpu/Tesla K80[GPU-e1f6f4f1-1ea5-7b9d-5f03-338a9dc32416]  0 / 11441 MiB
+
+Task Events:
+Started At     = 2019-01-23T18:25:32Z
+Finished At    = 2019-01-23T18:25:34Z
+Total Restarts = 0
+Last Restart   = N/A
+
+Recent Events:
+Time                  Type        Description
+2019-01-23T18:25:34Z  Terminated  Exit Code: 0
+2019-01-23T18:25:32Z  Started     Task started by client
+2019-01-23T18:25:29Z  Task Setup  Building Task Directory
+2019-01-23T18:25:29Z  Received    Task received by client
+
+$ nomad alloc logs d250baed
+Wed Jan 23 18:25:32 2019
++-----------------------------------------------------------------------------+
+| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
+|-------------------------------+----------------------+----------------------+
+| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
+| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
+|===============================+======================+======================|
+|   0  Tesla K80           On   | 00004477:00:00.0 Off |                    0 |
+| N/A   33C    P8    37W / 149W |      0MiB / 11441MiB |      0%      Default |
++-------------------------------+----------------------+----------------------+
+
++-----------------------------------------------------------------------------+
+| Processes:                                                       GPU Memory |
+|  GPU       PID   Type   Process name                             Usage      |
+|=============================================================================|
+|  No running processes found                                                 |
++-----------------------------------------------------------------------------+
+```
+
+[NVML]: https://github.com/NVIDIA/go-nvml
+[Fingerprint RPC]:
+    /nomad/docs/concepts/plugins/devices#fingerprint-context-context-chan-fingerprintresponse-error
+[mig]: https://www.nvidia.com/en-us/technologies/multi-instance-gpu/
+[docker-driver]: /nomad/docs/drivers/docker 'Nomad docker Driver'
+[exec-driver]: /nomad/docs/drivers/exec 'Nomad exec Driver'
+[java-driver]: /nomad/docs/drivers/java 'Nomad java Driver'
+[`plugin`]: /nomad/docs/configuration/plugin
+[`plugin_dir`]: /nomad/docs/configuration#plugin_dir
+[nvidia_plugin_download]: https://releases.hashicorp.com/nomad-device-nvidia/
+[nvidia_container_toolkit]: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
+[source]: https://github.com/hashicorp/nomad-device-nvidia
diff --git a/content/nomad/v1.9.x/content/plugins/devices/usb.mdx b/content/nomad/v1.9.x/content/plugins/devices/usb.mdx
new file mode 100644
index 0000000000..23ffa463eb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/devices/usb.mdx
@@ -0,0 +1,132 @@
+---
+layout: docs
+page_title: USB device plugin
+description: |-
+  The USB Device Plugin detects USB devices so you can use them in your Nomad workloads. Learn how to configure and install the plugin. Review the plugin's fingerprinted attributes and exposed runtime environment variables.
+---
+
+# USB device plugin
+
+Name: `usb`
+
+The `usb` device plugin is used to expose USB devices to Nomad. The USB plugin
+is not included within Nomad and requires downloading and providing on each
+node.
+
+## Fingerprinted Attributes
+
+| Attribute        | Unit   | Description                                     |
+| ---------------- | ------ | ----------------------------------------------- |
+| `vendor_id`      | int    | USB VID in decimal format                       |
+| `product_id`     | int    | USB PID in decimal format                       |
+| `class_id`       | int    | USB Class code in decimal format                |
+| `sub_class_id`   | int    | USB SubClass code in decimal format             |
+| `protocol_id`    | int    | USB Protocol code in decimal format             |
+| `vendor`         | string | Human readable vendor                           |
+| `product`        | string | Human readable product                          |
+| `description`    | string | Human readable description of the USB device    |
+| `classification` | string | Human readable classification of the USB device |
+| `serial`         | string | Serial Number of the USB device                 |
+
+## Runtime Environment
+
+The `usb` device plugin exposes the following environment variables:
+
+- `USB_VISIBLE_DEVICES` - List of USB IDs (from the plugin) available to the task.
+
+## Installation Requirements
+
+In order to use the `usb` device plugin the following prerequisites must be
+met:
+
+1. GNU/Linux i368/amd64/armv7/arm64 (Other Architectures and OS may work but
+   have not been tested)
+2. [libusb-1.0](https://github.com/libusb/libusb/wiki) installed
+
+## Installation
+
+To install the `usb` device plugin you will first need to download the binary
+for your Nomad client. You can find the latest release of these binaries on
+the [release
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
+
+This binary needs to be downloaded into the plugins directory of the Nomad
+node and the plugin block then needs to be added. A full example of the
+plugin block needed for the `usb` driver can be found under the plugin
+configuration section.
+
+## Plugin Configuration
+
+```hcl
+plugin "usb" {
+  config {
+    enabled = true
+
+    included_vendor_ids = [0x1CF1, 0x067b]
+    excluded_vendor_ids = []
+
+    included_product_ids = [0x0030, 0x2303]
+    excluded_product_ids = []
+
+    fingerprint_period = "1m"
+  }
+}
+```
+
+The `usb` device plugin supports the following configuration in the agent config:
+
+- `enabled` `(bool: true)` - the `usb` driver may be disabled on clients by
+  setting this option to `false` (defaults to `true`).
+
+- `included_vendor_ids` (`array<uint16>: []`): An array of VIDs to pass to
+  nomad if found
+
+- `excluded_vendor_ids` (`array<uint16>: []`): An array of VIDs to not pass to
+  nomad if found (this takes priority over the include list)
+
+- `included_product_ids` (`array<uint16>: []`): An array of PIDs to pass to
+  nomad if found
+
+- `excluded_product_ids` (`array<uint16>: []`): An array of PIDs to not pass
+  to nomad if found (this takes priority over the include list)
+
+- `fingerprint_period` `(string: "1m")` - The period in which to fingerprint
+  for device changes.
+
+## Limitations
+
+Currently the `usb` driver does not automatically provide dev paths for the
+USB devices into the task, this means in containerized applications you will
+still have to supply the dev path manually e.g. `/dev/ttyUSB0` however this
+plugin does allow containerized tasks to only be deployed on nodes which have
+specified USB devices connected.
+
+## Other Information
+
+The `usb` device plugin is currently in beta and thus is not recommended for
+production use. This will remain the case until the current limitations have
+been solved with the plugin. If you find any issues with the `usb` plugin
+please raise an issue on the plugins [issues
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/issues/new?issue)
+
+### USB Codes
+
+For a full list of available class, subclass, and protocol codes you can see
+the [usb-if-defined-class-codes](https://www.usb.org/defined-class-codes) page
+on the usb
+
+### USB Vendors & Products
+
+There are several sources where you can find known vendor and product ids for
+USB devices. These are independently maintained lists from third parties but
+can be useful as a reference.
+
+- [linux-usb.org](http://www.linux-usb.org/)
+- [devicehunt.com](https://devicehunt.com/all-usb-vendors)
+
+### Source Code & Compiled Binaries
+
+The source code for this plugin can be found at
+[CarbonCollins/nomad-usb-device-plugin](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin). You
+will also find pre built binaries on the [releases
+page](https://gitlab.com/CarbonCollins/nomad-usb-device-plugin/-/releases).
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/containerd.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/containerd.mdx
new file mode 100644
index 0000000000..a735028a67
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/containerd.mdx
@@ -0,0 +1,423 @@
+---
+layout: docs
+page_title: Task driver plugin for containerd
+description: >-
+  Use the community-supported containerd task driver to launch containerd containers in your Nomad job.
+---
+
+# containerd Task Driver Plugin
+
+Name: `containerd-driver`
+
+Homepage: https://github.com/Roblox/nomad-driver-containerd
+
+containerd ([`containerd.io`](https://containerd.io)) is a lightweight container
+daemon for running and managing container lifecycle. Docker daemon also uses
+containerd.
+
+```hcl
+dockerd (docker daemon) --> containerd --> containerd-shim --> runc
+```
+
+`nomad-driver-containerd` enables Nomad clients to launch containers directly
+using containerd, without Docker. The Docker daemon is therefore not required on
+the host system.
+
+See the [project's homepage](https://github.com/Roblox/nomad-driver-containerd)
+for more details.
+
+## Client Requirements
+
+The containerd task driver is not built into Nomad. It must be
+[`downloaded`][releases] onto the client host in the configured plugin
+directory.
+
+- Linux (Ubuntu >=16.04) with [`containerd`](https://containerd.io/downloads/) (>=1.3) installed.
+
+- [`containerd-driver`][releases] binary in Nomad's [plugin_dir][].
+
+## Capabilities
+
+The `containerd-driver` implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| send signals         | true                    |
+| exec                 | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+For sending signals, one can use `nomad alloc signal` command.<br/>
+For exec'ing into the container, one can use `nomad alloc exec` command.
+
+## Task Configuration
+
+Since Docker also relies on containerd for managing container lifecycle, the
+example job created by [`nomad init -short`][nomad-init] can easily be adapted
+to use `containerd-driver` instead:
+
+```hcl
+job "redis" {
+  datacenters = ["dc1"]
+
+  group "redis-group" {
+    task "redis-task" {
+      driver = "containerd-driver"
+
+      config {
+        image = "docker.io/library/redis:alpine"
+      }
+
+      resources {
+        cpu    = 500
+        memory = 256
+      }
+    }
+  }
+}
+```
+
+The containerd task driver supports the following parameters:
+
+- `image` - (Required) OCI image (Docker is also OCI compatible) for your
+  container.
+
+```hcl
+config {
+  image = "docker.io/library/redis:alpine"
+}
+```
+
+- `image_pull_timeout` - (Optional) A time duration that controls how long
+  `containerd-driver` will wait before cancelling an in-progress pull of the
+  OCI image as specified in `image`. Defaults to `"5m"`.
+
+- `command` - (Optional) Command to override command defined in the image.
+
+```hcl
+config {
+  command = "some-command"
+}
+```
+
+- `args` - (Optional) Arguments to the command.
+
+```hcl
+config {
+  args = [
+    "arg1",
+    "arg2",
+  ]
+}
+```
+
+- `auth` - (Optional) Provide authentication for a private registry (See [Authentication] below).
+
+- `entrypoint` - (Optional) A string list overriding the image's entrypoint.
+
+- `cwd` - (Optional) Specify the current working directory (cwd) for your container process.
+  If the directory does not exist, one will be created for you.
+
+- `privileged` - (Optional) `true` or `false` (default) Run container in
+  privileged mode. Your container will have all Linux capabilities when running
+  in privileged mode.
+
+```hcl
+config {
+  privileged = true
+}
+```
+
+- `pids_limit` - (Optional) An integer value that specifies the pid limit for
+  the container. Defaults to unlimited.
+
+- `pid_mode` - (Optional) `host` or not set (default). Set to `host` to share
+  the PID namespace with the host.
+
+- `host_dns` - (Optional) `true` (default) or `false` By default, a container
+  launched using `containerd-driver` will use host `/etc/resolv.conf`. This is
+  similar to [Docker's behavior]. However, if you don't want to use
+  host DNS, you can turn off this flag by setting `host_dns=false`.
+
+- `seccomp` - (Optional) Enable default seccomp profile. List of [allowed syscalls].
+
+- `seccomp_profile` - (Optional) Path to custom seccomp profile.
+  `seccomp` must be set to `true` in order to use `seccomp_profile`.
+
+  The default `docker` seccomp profile found in the [Moby repository]
+  can be downloaded, and modified (by removing/adding syscalls) to create a custom seccomp profile.
+  The custom seccomp profile can then be saved under `/opt/seccomp/seccomp.json` on the Nomad client nodes.
+
+```hcl
+config {
+  seccomp         = true
+  seccomp_profile = "/opt/seccomp/seccomp.json"
+}
+```
+
+- `shm_size` - (Optional) Size of /dev/shm e.g. `128M` if you want 128 MB of /dev/shm.
+
+- `sysctl` - (Optional) A key-value map of sysctl configurations to set to the
+  containers on start.
+
+```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn"  = "16384"
+      "net.ipv4.ip_forward" = "1"
+    }
+  }
+```
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default) Container root
+  filesystem will be read-only.
+
+```hcl
+config {
+  readonly_rootfs = true
+}
+```
+
+- `host_network` ((#host_network)) - (Optional) `true` or `false` (default)
+  Enable host network. This is equivalent to `--net=host` in docker.
+
+```hcl
+config {
+  host_network = true
+}
+```
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to
+  `/etc/hosts`.
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using `count`) with this option set, every
+  container the task starts will have the same hostname.
+
+- `cap_add` - (Optional) Add individual capabilities.
+
+```hcl
+config {
+  cap_add = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `cap_drop` - (Optional) Drop individual capabilities.
+
+```hcl
+config {
+  cap_drop = [
+    "CAP_SYS_ADMIN",
+    "CAP_CHOWN",
+    "CAP_SYS_CHROOT"
+  ]
+}
+```
+
+- `devices` - (Optional) A list of devices to be exposed to the container.
+
+```hcl
+config {
+  devices = [
+    "/dev/loop0",
+    "/dev/loop1"
+  ]
+}
+```
+
+- `mounts` - (Optional) A list of mounts to be mounted in the container. Volume,
+  bind and tmpfs type mounts are supported. fstab style [`mount options`][] are
+  supported.
+
+  - `type` - (Optional) Supported values are `volume`, `bind` or `tmpfs`.
+    **Default:** `volume`.
+
+  - `target` - (Required) Target path in the container.
+
+  - `source` - (Optional) Source path on the host.
+
+  - `options` - (Optional) fstab style [`mount options`][]. **NOTE:** For bind
+    mounts, at least `rbind` and `ro` are required.
+
+```hcl
+config {
+  mounts = [
+    {
+      type = "bind"
+      target = "/tmp/t1"
+      source = "/tmp/s1"
+      options = ["rbind", "ro"]
+    }
+  ]
+}
+```
+
+## Networking
+
+`nomad-driver-containerd` supports **host** and **bridge** networks.
+
+**NOTE:** `host` and `bridge` are mutually exclusive options, and only one of
+them should be used at a time.
+
+1. **Host** network can be enabled by setting `host_network` to `true` in task
+   config of the job spec (see [host_network][host-network] under Task
+   Configuration).
+
+2. **Bridge** network can be enabled by setting the `network` block in the task
+   group section of the job spec.
+
+```hcl
+network {
+  mode = "bridge"
+}
+```
+
+You need to install CNI plugins on Nomad client nodes under `/opt/cni/bin`
+before you can use `bridge` networks.
+
+**Instructions for installing CNI plugins.**
+
+```hcl
+ $ curl -L -o cni-plugins.tgz "https://github.com/containernetworking/plugins/releases/download/v1.0.0/cni-plugins-linux-$( [ $(uname -m) = aarch64 ] && echo arm64 || echo amd64)"-v1.0.0.tgz
+ $ sudo mkdir -p /opt/cni/bin
+ $ sudo tar -C /opt/cni/bin -xzf cni-plugins.tgz
+```
+
+Also, ensure your Linux operating system distribution has been configured
+to allow container traffic through the bridge network to be routed via iptables.
+These tunables can be set as follows:
+
+```hcl
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-arptables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-ip6tables
+ $ echo 1 > /proc/sys/net/bridge/bridge-nf-call-iptables
+```
+
+To preserve these settings on startup of a Nomad client node, add a file
+including the following to `/etc/sysctl.d/` or remove the file your Linux
+distribution puts in that directory.
+
+```hcl
+ net.bridge.bridge-nf-call-arptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 1
+ net.bridge.bridge-nf-call-iptables = 1
+```
+
+## Port Forwarding
+
+Nomad supports both `static` and `dynamic` port mapping.
+
+1. **Static ports**
+
+Static port mapping can be added in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "lb" {
+    static = 8889
+    to     = 8889
+  }
+}
+```
+
+Here, `host` port `8889` is mapped to `container` port `8889`.<br/>
+**NOTE:** static ports are usually not recommended, except for
+`system` or specialized jobs like load balancers.
+
+2. **Dynamic ports**
+
+Dynamic port mapping is also enabled in the `network` block.
+
+```hcl
+network {
+  mode = "bridge"
+  port "http" {
+    to = 8080
+  }
+}
+```
+
+Here, nomad will allocate a dynamic port on the `host` and that port
+will be mapped to `8080` in the container.
+
+You can read more about configuring networking under the [`network`] block documentation.
+
+## Service discovery
+
+Nomad schedules workloads of various types across a cluster of generic hosts.
+Because of this, placement is not known in advance and you will need to use
+service discovery to connect tasks to other services deployed across your cluster.
+Nomad integrates with Consul to provide service discovery and monitoring.
+
+A [`service`] block can be added to your job spec, to enable service discovery.
+
+The service block instructs Nomad to register a service with Consul.
+
+## Authentication ((#authentication))
+
+`auth` block allow you to set credentials for your private registry e.g. if you want
+to pull an image from a private repository in docker hub.
+`auth` block can be set either in `Driver Config` or `Task Config` or both.
+If set at both places, `Task Config` auth will take precedence over `Driver Config` auth.
+
+**NOTE**: In the below example, `user` and `pass` are just placeholder values which need to be
+replaced by actual `username` and `password`, when specifying the credentials. Below `auth`
+block can be used for both `Driver Config` and `Task Config`.
+
+```hcl
+auth {
+  username = "user"
+  password = "pass"
+}
+```
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - (Optional) The `containerd` driver may be disabled on hosts by
+  setting this option to `false` (defaults to `true`).
+
+- `containerd_runtime` - (Required) Runtime for `containerd` e.g.
+  `io.containerd.runc.v1` or `io.containerd.runc.v2`
+
+- `stats_interval` - (Optional) This value defines how frequently you want to
+  send `TaskStats` to nomad client. (defaults to `1 second`).
+
+- `allow_privileged` - (Optional) If set to `false`, driver will deny running
+  privileged jobs. (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "containerd-driver" {
+  config {
+    enabled = true
+    containerd_runtime = "io.containerd.runc.v2"
+    stats_interval = "5s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for
+the external driver in the [plugin_dir][plugin_dir] directory.
+
+[nomad-driver-containerd]: https://github.com/Roblox/nomad-driver-containerd
+[nomad-init]: /nomad/docs/commands/job/init
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[authentication]: #authentication
+[host-network]: #host_network
+[`mount options`]: https://github.com/containerd/containerd/blob/9561d9389d3dd87ff6030bf1da4e705bbc024130/mount/mount_linux.go#L198-L222
+[moby repository]: https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
+[docker's behavior]: https://docs.docker.com/config/containers/container-networking/#dns-services
+[allowed syscalls]: https://github.com/containerd/containerd/blob/master/contrib/seccomp/seccomp_default.go#L51-L390
+[`network`]: /nomad/docs/job-specification/network
+[`service`]: /nomad/docs/job-specification/service
+[releases]: https://github.com/Roblox/nomad-driver-containerd/releases/
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/firecracker-task-driver.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/firecracker-task-driver.mdx
new file mode 100644
index 0000000000..1869f69d90
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/firecracker-task-driver.mdx
@@ -0,0 +1,130 @@
+---
+layout: docs
+page_title: Firecracker task driver plugin
+description: >-
+  Use the community-supported Firecracker task driver to run Firecracker micro virtual machines in your Nomad job.
+---
+
+# Firecracker task driver plugin
+
+Name: `firecracker-task-driver`
+
+The Firecracker task driver provides an interface for creating Linux microVMs.
+For more detailed instructions on how to set up and use this driver, please
+refer to the [documentation][firecracker-task-guide].
+
+## Task Configuration
+
+```hcl
+task "test01" {
+  driver = "firecracker-task-driver"
+
+  config {
+    KernelImage = "/home/build/hello-vmlinux.bin"
+    Firecracker = "/home/build/firecracker"
+    Vcpus       = 1
+    Mem         = 128
+    Network     = "default"
+  }
+}
+```
+
+The firecracker task driver supports the following parameters:
+
+- `KernelImage` - (Optional) Path to the kernel image to be used on the microvm.
+  Defaults to 'vmlinux' in the [allocation working directory].
+
+- `BootDisk` - (Optional) Path to the ext4 rootfs to boot from.
+  Defaults to 'rootfs.ext4' in the [allocation working directory].
+
+- `BootOptions` - (Optional) Kernel command line options to boot the microvm.
+  Defaults to "ro console=ttyS0 reboot=k panic=1 pci=off"
+
+- `Network` - (Optional) Network name of your container network configuration
+  file.
+
+- `Vcpus` - (Optional) Number of CPUs to assign to microvm.
+
+- `Cputype` - (Optional) CPU template to use, templates available are C3 or T2.
+
+- `Mem` - (Optional) Amount of memory in Megabytes to assign to microvm.
+  Defaults to 512
+
+- `Firecracker` Location of the firecracker binary, the option could be omitted
+  if the environment variable FIRECRACKER_BIN is setup. Defaults to
+  '/usr/bin/firecracker'
+
+- `DisableHt` - (Optional) Disable CPU Hyperthreading. Defaults to false
+
+- `Log` - (Optional) path to file where to write firecracker logs.
+
+## Networking
+
+Network configuration is setup using CNI plugins, the steps to setup firecracker
+task driver with cni are the following:
+
+- Build [cni plugins][container network plugins] and [tc-redirect-tap][tc-redirect-tap]
+  and copy them to `/opt/cni`.
+
+- Create a network configuration to be used by micro-vms on /etc/cni/conf.d/,
+  for example: default.conflist.
+
+### Example network configuration
+
+```json
+{
+  "name": "default",
+  "cniVersion": "0.4.0",
+  "plugins": [
+    {
+      "type": "ptp",
+      "ipMasq": true,
+      "ipam": {
+        "type": "host-local",
+        "subnet": "192.168.127.0/24",
+        "resolvConf": "/etc/resolv.conf"
+      }
+    },
+    {
+      "type": "firewall"
+    },
+    {
+      "type": "tc-redirect-tap"
+    }
+  ]
+}
+```
+
+In this example the name of this network is default and this name is the
+parameter used in Network on the task driver job spec. Also the filename must
+match the name of the network, and use the .conflist extension.
+
+## Client Requirements
+
+`firecracker-task-driver` requires the following:
+
+- Linux 4.14+ Firecracker currently supports physical Linux x86_64 and aarch64
+  hosts, running kernel version 4.14 or later. However, the aarch64 support is
+  not feature complete (alpha stage)
+
+- The [Firecracker binary][firecracker binary]
+
+- KVM enabled in your Linux kernel, and you have read/write access to /dev/kvm
+
+- tun kernel module
+
+- The firecracker-task-driver binary placed in the [plugin_dir][plugin_dir]
+  directory
+
+- ip6tables package
+
+- [Container network plugins][container network plugins]
+
+- [tc-redirect-tap][tc-redirect-tap]
+
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[tc-redirect-tap]: https://github.com/awslabs/tc-redirect-tap
+[container network plugins]: https://github.com/containernetworking/plugins
+[firecracker binary]: https://github.com/firecracker-microvm/firecracker/releases
+[firecracker-task-guide]: https://github.com/cneira/firecracker-task-driver
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/iis.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/iis.mdx
new file mode 100644
index 0000000000..bdde310ebe
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/iis.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Windows IIS task driver plugin
+description: >-
+  Use the community-supported Windows IIS task driver (nomad-driver-iis) to run Windows IIS services in Nomad jobs.
+---
+
+# Windows IIS task driver plugin
+
+Name: `win_iis`
+
+The Nomad `win_iis` task driver provides an interface for running Windows IIS website tasks.
+A "website" is a combination of an application pool and a site (app, vdir, etc.).
+Each allocation will create an application pool and site with the name being the allocation ID (guid).
+
+For more detailed instructions on how to set up and use this driver, please
+refer to the [project README.md][nomad-driver-iis].
+
+## Task Configuration
+
+```hcl
+task "iis-test" {
+  driver = "win_iis"
+
+  config {
+    path = "C:\\inetpub\\wwwroot"
+    apppool_identity {
+      identity="SpecificUser"
+      username="vagrant"
+      password="vagrant"
+    }
+  }
+}
+```
+
+The IIS task driver supports the following parameters:
+
+- `path` (string) - (Required) The path of the website directory.
+
+- `site_config_path` (string) - (Optional) The path should point to a valid IIS Site XML that is generated from an export.
+
+- `apppool_config_path` (string) - (Optional) The path should point to a valid IIS Application Pool XML that is generated from an export.
+
+- `apppool_identity` - (Optional) `ApplicationPoolIdentity` (default). The identity which the Application Pool will run under.
+
+  - `identity` (string) - (Required) An identity is required to be set for Application Pools. Accepted inputs are `LocalService`, `LocalSystem`, `NetworkService`, `SpecificUser`, and `ApplicationPoolIdentity`.
+  - `username` (string) - (Optional) If `SpecificUser` was chosen, then provide the username.
+  - `password` (string) - (Optional) If `SpecificUser` was chosen, then provide the password.
+
+- `bindings` - (Optional) Bindings set here will be set for IIS.
+  - `hostname` (string) - (Optional) IIS hostname for a binding.
+  - `ipaddress` (string) - (Optional). `*` (default). IIS allows a binding to specify the IP Address being sent out.
+  - `resource_port` (string) - (Optional) Use a label from an established network block port. It is recommended to use this approach over using `port`.
+  - `port` (number) - (Optional) Specify a static port to use for the website. A port must be specified between `resource_port` or `port`. Ports set this way will not be recognized by nomad.
+  - `type` (string) - (Optional) Specifies which binding type IIS should use such as `http` or `https`.
+  - `cert_hash` (string) - (Optional) For SSL support, supply the cert hash here of a cert installed on the system.
+
+For optional parameters default value is assumed `nil`, if the default value is not specified in the documentation.
+
+## Networking
+
+Currently, `nomad-driver-iis` only supports host networking. No special configuration is needed as `nomad-driver-iis`
+relies on IIS to manage the networking for Windows IIS website tasks.
+
+## Client Requirements
+
+`nomad-driver-iis` requires the following:
+
+- Windows 2016+
+
+- Web Server enabled for IIS
+
+- The Nomad IIS driver binary ([build instructions][nomad-driver-iis])
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `IIS` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `stats_interval` - This value defines how frequently you want to send `TaskStats` to nomad client. (defaults to `1 second`).
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "win_iis" {
+  client {
+    enabled = true
+    stats_interval = "30s"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `IIS` driver will set the following client attributes:
+
+- `driver.win_iis.iis_version` - Sets to IIS version of IIS which is running on nomad client.
+
+[nomad-driver-iis]: https://github.com/Roblox/nomad-driver-iis
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/index.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/index.mdx
new file mode 100644
index 0000000000..b564b258d6
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/index.mdx
@@ -0,0 +1,47 @@
+---
+layout: docs
+page_title: Community task driver plugins
+description: Learn about the community-supported task driver plugins that extend Nomad job features. Review installation, usage, and reference information for containerd, Firecracker, Jail, Pledge, Pot, Rookout, Singularity, system-nspawn, and Windows IIS task driver plugins.
+---
+
+# Community task driver plugins
+
+If you have authored a task driver plugin that you believe will be useful to the
+broader Nomad community and you are committed to maintaining the plugin, please
+file a PR to add your plugin to this page.
+
+For details on authoring a task driver plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+## Task Driver Plugins
+
+Nomad has a plugin system for defining task drivers. External task driver
+plugins will have the same user experience as built in drivers.
+
+The following is a list of community-supported task drivers you can use with Nomad:
+
+- [containerd][nomad-driver-containerd]
+- [Firecracker][firecracker-task-driver]
+- [Jail task driver][jail-task-driver]
+- [Lightrun][lightrun]
+- [Pledge][pledge]
+- [Pot][pot]
+- [Rookout][rookout]
+- [Singularity][singularity]
+- [systemd-nspawn][nspawn-driver]
+- [Windows IIS (nomad-driver-iis)][nomad-driver-iis]
+- [Windows IIS (nomad-iis)][nomad-iis]
+
+[rookout]: /nomad/plugins/drivers/community/rookout
+[plugin_guide]: /nomad/docs/concepts/plugins
+[singularity]: /nomad/plugins/drivers/community/singularity
+[jail-task-driver]: /nomad/plugins/drivers/community/jail-task-driver
+[pot]: /nomad/plugins/drivers/community/pot
+[firecracker-task-driver]: /nomad/plugins/drivers/community/firecracker-task-driver
+[nspawn-driver]: /nomad/plugins/drivers/community/nspawn
+[nomad-driver-iis]: /nomad/plugins/drivers/community/iis
+[nomad-iis]: /nomad/plugins/drivers/community/nomad-iis
+[nomad-driver-containerd]: /nomad/plugins/drivers/community/containerd
+[lightrun]: /nomad/plugins/drivers/community/lightrun
+[pledge]: /nomad/plugins/drivers/community/pledge
+
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/jail-task-driver.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/jail-task-driver.mdx
new file mode 100644
index 0000000000..84c9bcf368
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/jail-task-driver.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Jail task driver plugin
+description: >-
+  Use the community-supported Jail task driver to run application containers using FreeBSD jails in your Nomad jobs.
+---
+
+# Jail task driver plugin
+
+Name: `jail-task-driver`
+
+The Jail task driver provides an interface for using FreeBSD jails for running application
+containers. You can download the external jail-task-driver [here][jail-task-driver]. For more detailed instructions on how to set up and use this driver, please refer to the [guide][jail-task-guide].
+
+## Task Configuration
+
+```hcl
+task "http-echo-jail" {
+		driver = "jail-task-driver"
+		config {
+			Path  = "/zroot/iocage/jails/myjail/root"
+			Allow_raw_sockets = true
+			Allow_chflags     = true
+			Ip4_addr          = "em1|192.168.1.102"
+			Exec_start        = "/usr/local/bin/http-echo -listen :9999 -text hello"
+			Rctl =  {
+				Vmemoryuse = {
+					Action = "deny"
+					Amount = "1G"
+					Per = "process"
+				}
+				Openfiles = {
+					Action = "deny"
+					Amount = "500"
+				}
+			}
+		}
+	}
+```
+
+The Jail task driver supports most of [JAIL(8)][jail(8)] parameters, for a list of the currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+- `Path` - (Optional) The directory which is to be the root of the jail.
+  Defaults to the [allocation working directory].
+
+- `Ip4` - (Optional) Control the availability of IPv4 addresses. Possible values are
+  **"inherit"** to allow unrestricted access to all system addresses,
+  **"new"** to restrict addresses via Ip4_addr, and "**disable"** to stop
+  the jail from using IPv4 entirely.
+
+~> Note : Setting the Ip4_addr parameter implies a value of **"new"**
+
+- `Ip4_addr` - (Optional) A list of IPv4 addresses assigned to the jail. If this is set,
+  the jail is restricted to using only these addresses. Any attempts to use other addresses fail,
+  and attempts to use wildcard addresses silently use the jailed address instead. For
+  IPv4 the first address given will be used as the source address when source address selection on
+  unbound sockets cannot find a better match. It is only possible to start multiple jails with
+  the same IP address if none of the jails has more than this
+  single overlapping IP address assigned to itself.
+
+- `Allow_raw_sockets` - (Optional) The jail root is allowed to create raw sockets. Setting
+  this parameter allows utilities like ping(8) and traceroute(8) to operate inside the jail.
+  If this is set, the source IP addresses are enforced to comply with the IP address bound to the jail,
+  regardless of whether or not the IP_HDRINCL flag has been set on the socket.
+  Since raw sockets can be used to configure and interact with various network subsystems, extra caution
+  should be used where privileged access to jails is given out to untrusted parties.
+
+## Resource Isolation
+
+Resource isolation on jails is enforced by [RCTL(8)][rctl-doc] all parameters for resource control
+are supported.
+
+- `Rctl` - (Optional) Set resource limits on the jail, for a list of currently supported parameters, please refer to the [Parameter Documentation][parameter-doc].
+
+      	* `Vmemoryuse`   - (Optional) Address space limit,in bytes
+      	* `Cputime`      - (Optional) CPU time, in seconds
+      	* `Datasize`     - (Optional)  data	size, in bytes
+      	* `Stacksize`    - (Optional   stack size, in bytes
+      	* `Coredumpsize` - (Optional)	   core	dump size, in bytes
+      	* `Memoryuse`    - (Optional)	   resident set size, in bytes
+      	* `Memorylocked` - (Optional)	   locked memory, in bytes
+      	* `Maxproc`      - (Optional)		   number of processes
+      	* `Openfiles`    - (Optional)	   file	descriptor table size
+      	* `Vmemoryuse`   - (Optional) 	   address space limit,in bytes
+      	* `Pseudoterminals`  - (Optional)	   number of PTYs
+      	* `Swapuse`  - (Optional)		   swap	space that may be reserved or used, in bytes
+      	* `Nthr`  - (Optional)		   number of threads
+      	* `Msgqqueued`  - (Optional) 	   number of queued SysV messages
+      	* `Msgqsize`  - (Optional)	   SysV	message	queue size, in bytes
+      	* `Nmsgq`  - (Optional)		   number of SysV message queues
+      	* `Nsem`  - (Optional)		   number of SysV semaphores
+      	* `Nsemop`  - (Optional)		   number of SysV semaphores modified in a single semop(2) call
+      	* `Nshm`  - (Optional)		   number of SysV shared memory	segments
+      	* `Shmsize`  - (Optional)		   SysV	shared memory size, in bytes
+      	* `Wallclock`  - (Optional)	   wallclock time, in seconds
+      	* `Pcpu`  - (Optional)		   %CPU, in percents of	a single CPU core
+      	* `Readbps`  - (Optional)		   filesystem reads, in	bytes per second
+      	* `Writebps`  - (Optional)	   filesystem writes, in bytes per second
+      	* `Readiops`  - (Optional)	   filesystem reads, in	operations per second
+      	* `Writeiops`  - (Optional)	   filesystem writes, in operations per	second
+
+## Networking
+
+The job spec could specify the `Ip4addr` parameter to add the jail's ip address to an specific interface at jail
+startup or the `Vnet` parameter to create a virtual network stack. Please refer to [JAIL(8)][jail(8)] for more details.
+
+- `vnet jail` - Example taken from Lucas, Michael W. FreeBSD Mastery: Jails (IT Mastery Book 15).
+
+```hcl
+ task "test01" {
+      driver = "jail-task-driver"
+      config {
+		Path    = "/zroot/iocage/jails/myjail/root"
+		Host_hostname = "nomad00"
+		Exec_clean = true
+		Exec_start = "sh /etc/rc"
+		Exec_stop = "sh /etc/rc.shutdown"
+		Mount_devfs = true
+		Exec_prestart = "logger trying to start "
+		Exec_poststart = "logger jail has started"
+		Exec_prestop = "logger shutting down jail "
+		Exec_poststop = "logger has shut down jail "
+		Exec_consolelog ="/var/tmp/vnet-example"
+		Vnet = true
+		Vnet_nic = "e0b_loghost"
+		Exec_prestart = "/usr/share/examples/jails/jib addm loghost em1"
+		Exec_poststop = "/usr/share/examples/jails/jib destroy loghost "
+      }
+    }
+```
+
+## Client Requirements
+
+`jail-task-driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host
+- The FreeBSD's Nomad binary
+- The jail-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- If resource control is going be used then [RACCT][racct-doc] must be enabled
+
+[jail-task-driver]: https://github.com/cneira/jail-task-driver/releases
+[jail-task-guide]: https://github.com/cneira/jail-task-driver#installation
+[jail(8)]: https://www.freebsd.org/cgi/man.cgi?jail(8)
+[racct-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[rctl-doc]: https://www.freebsd.org/doc/handbook/security-resourcelimits.html
+[parameter-doc]: https://github.com/cneira/jail-task-driver/blob/master/Parameters.md
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[allocation working directory]: /nomad/docs/runtime/environment#task-directories 'Task Directories'
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/lightrun.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/lightrun.mdx
new file mode 100644
index 0000000000..13ed6162bb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/lightrun.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Lightrun task driver plugin
+description: Use the community-supported Lightrun task driver to run your Java application with Lightrun in your Nomad jobs.
+---
+
+# Lightrun task driver plugin
+
+Name: `lightrun-java`
+
+The Lightrun Nomad driver is used to execute Java applications packaged into a
+Java Jar file and automatically add the Lightrun agent to them.
+
+[Lightrun][lightrun_website] is a developer-native observability platform. With
+Lightrun you can add logs, snapshots (virtual breakpoints), and metrics to
+production applications without the need for redeployments or restarts. You can
+use Lightrun directly from your IDE or CLI to observe, understand and debug
+your application at runtime.
+
+Refer to the [Lightrun documentation][lightrun_docs] for more information about
+Lightrun.
+
+## Prerequisites
+
+1. Download or clone the [Lightrun driver repository][repo].
+1. Find the `lightrun-java-driver` driver in the repository's root folder.
+1. Copy the driver to your Nomad plugins directory (or create one if it doesn't
+  exist).
+1. Grant executable permissions to the driver file:
+
+    ```shell-session
+    $ chmod +x ./plugins/lightrun-java-driver
+    ```
+
+1. When running the Nomad agent, make sure to specify the path to your plugins
+  directory:
+
+    ```shell-session
+    $ sudo nomad agent -dev -bind 0.0.0.0 -log-level DEBUG -plugin-dir=<path_to_plugins_directory>
+    ```
+
+## Task Configuration
+
+```hcl
+task "run-with-lightrun" {
+  driver = "lightrun-java"
+
+  config {
+    lightrun_server = "https://app.lightrun.com/company/<COMPANY-NAME>"
+    lightrun_secret = "<COMPANY-SECRET>"
+    lightrun_certificate = "ee80811b38e7e6c2dc4cc372cbea86bd86b446b012e427f2e19bf094afba5d12"
+  }
+}
+```
+
+The `lightrun-java` driver accepts all configuration options of the Nomad
+[`java`] driver.
+
+Additionally, the `lightrun-java` driver requires the following configuration in
+the job spec. To find these configurations, log into the
+[Lightrun Management Portal][lightrun_portal] and refer to the **Download the
+Agent** section:
+
+- `lightrun_server` - The Lightrun server you are working against, including
+  your company name.
+
+- `lightrun_secret` - Lightrun secret is used for authorization against the
+  Lightrun server.
+
+- `lightrun_certificate` - Used for certificate pinning.
+
+A full job file example can be found in the repo at [`example/example.driver.nomad`][example-config].
+
+[lightrun_docs]: https://docs.lightrun.com
+[lightrun_website]: https://www.lightrun.com
+[lightrun_portal]: https://app.lightrun.com
+[repo]: https://github.com/lightrun-platform/lightrun-n-nomad
+[example-config]: https://github.com/lightrun-platform/lightrun-n-nomad/blob/main/example/example.driver.nomad
+[`java`]: /nomad/docs/drivers/java
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/nomad-iis.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/nomad-iis.mdx
new file mode 100644
index 0000000000..af9cb179ac
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/nomad-iis.mdx
@@ -0,0 +1,74 @@
+---
+layout: docs
+page_title: Nomad IIS task driver plugin
+description: >-
+  Use the community-supported Nomad IIS driver to run Windows IIS services in Nomad jobs.
+---
+
+# Nomad IIS task driver plugin
+
+Name: `nomad_iis`
+
+The `nomad_iis` plugin is a task driver to run IIS Web Applications on Windows Servers. Each allocation will create an AppPool and a Website.
+For a full documentation please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md).
+
+Unlike most other Nomad task drivers, this one is written in the C# language using ASP.NET. It uses the Microsoft.Web.Administration-API to communicate with IIS.
+
+<Note>
+At the moment I'm developing this plugin as a hobby project. Version 1 has not yet been reached and breaking changes may still occur.
+</Note>
+
+## Sample Job
+
+```hcl
+job "iis-test" {
+  datacenters = ["dc1"]
+  type = "service"
+
+  group "iis-test" {
+    count = 1
+
+    network {
+      port "httplabel" {}
+    }
+
+    task "iis-test" {
+      driver = "iis"
+
+      config {
+        application {
+          path = "C:\\inetpub\\wwwroot"
+        }
+        application {
+          alias = "subapp"
+          path = "C:\\inetpub\\wwwroot"
+        }
+
+        binding {
+          type = "http"
+          port = "httplabel"
+        }
+      }
+
+      env {
+        my_key = "my-value"
+      }
+
+      resources {
+        cpu    = 100
+        memory = 20
+      }
+    }
+  }
+}
+```
+
+Please refer to the project's [Readme](https://github.com/sevensolutions/nomad-iis/blob/main/README.md) for the full documentation and configuration options.
+
+## Download
+
+Download the latest version from [here](https://github.com/sevensolutions/nomad-iis/releases).
+
+## Source Code
+
+You can get the full source code of this plugin on [Github](https://github.com/sevensolutions/nomad-iis).
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/nspawn.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/nspawn.mdx
new file mode 100644
index 0000000000..057205b329
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/nspawn.mdx
@@ -0,0 +1,204 @@
+---
+layout: docs
+page_title: Task driver plugin for nspawn
+description: Use the community-supported nspawn task driver to run application containers using systemd-nspawn in Nomad jobs.
+---
+
+# nspawn Task Driver Plugin
+
+Name: `nspawn`
+
+The `nspawn` driver provides an interface for using systemd-nspawn for running
+application containers. You can download the external nspawn driver from the
+[nomad-driver-nspawn releases page][nspawn-driver]. For more detailed instructions on how to set up and use
+this driver, please refer to the [examples in the nomad-driver-nspawn repository][nspawn-guide].
+
+## Task Configuration
+
+```hcl
+task "debian" {
+  driver = "nspawn"
+  config {
+    image = "/var/lib/machines/Debian"
+    resolv_conf = "copy-host"
+  }
+}
+```
+
+The `nspawn` driver supports the following configuration in the job spec:
+
+- [`boot`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-b) -
+  (Optional) `true` (default) or `false`. Search for an init program and invoke
+  it as PID 1. Arguments specified in `command` will be used as arguments for
+  the init program.
+
+- [`ephemeral`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-x) -
+  (Optional) `true` or `false` (default). Make an ephemeral copy of the image
+  before staring the container.
+
+- [`process_two`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-a) -
+  (Optional) `true` or `false` (default). Start the command specified with
+  `command` as PID 2, using a minimal stub init as PID 1.
+
+- [`read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--read-only) -
+  (Optional) `true` or `false` (default). Mount the used image as read only.
+
+- [`user_namespacing`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-U) -
+  (Optional) `true` (default) or `false`. Enable user namespacing features
+  inside the container.
+
+- `command` - (Optional) A list of strings to pass as the used command to the
+  container.
+
+  ```hcl
+  config {
+    command = [ "/bin/bash", "-c", "dhclient && nginx && tail -f /var/log/nginx/access.log" ]
+  }
+  ```
+
+- [`console`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--console=MODE) -
+  (Optional) Configures how to set up standard input, output and error output
+  for the container.
+
+- `image` - The image to be used in the container. This can either be the path
+  to a
+  [directory](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-D),
+  the path to a file system
+  [image](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-i)
+  or block device or the name of an image registered with
+  [`systemd-machined`](https://www.freedesktop.org/software/systemd/man/systemd-machined.service.html).
+  A path can be specified as a relative path from the configured Nomad plugin
+  directory. **This option is mandatory**.
+
+- `image_download` - (Optional) Download the used image according to the
+  settings defined in this block. Structure is documented below.
+
+- [`pivot_root`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--pivot-root=) -
+  (Optional) Pivot the specified directory to the be containers root directory.
+
+- [`resolv_conf`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=) -
+  (Optional) Configure how `/etc/resolv.conf` is handled inside the container.
+
+- [`user`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#-u) -
+  (Optional) Change to the specified user in the containers user database.
+
+- [`volatile`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--volatile) -
+  (Optional) Boot the container in volatile mode.
+
+- [`working_directory`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--chdir=) -
+  (Optional) Set the working directory inside the container.
+
+- [`bind`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount inside the container.
+
+  ```hcl
+  config {
+    bind {
+      "/var/lib/postgresql" = "/postgres"
+    }
+  }
+  ```
+
+- [`bind_read_only`](https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--bind=) -
+  (Optional) Files or directories to bind mount read only inside the container.
+
+  ```hcl
+  config {
+    bind_read_only {
+      "/etc/passwd" = "/etc/passwd"
+    }
+  }
+
+  ```
+
+- `environment` - (Optional) Environment variables to pass to the init process
+  in the container.
+
+  ```hcl
+  config {
+    environment = {
+      FOO = "bar"
+    }
+  }
+  ```
+
+- `port_map` - (Optional) A key-value map of port labels. Works the same way as
+  in the [docker driver][docker_driver].
+
+  **Note:** `systemd-nspawn` will not expose ports to the loopback interface
+  of your host.
+
+  ```hcl
+  config {
+    port_map {
+      http = 80
+    }
+  }
+  ```
+
+The `image_download` block supports the following arguments:
+
+- `url` - The URL of the image to download. The URL must be of type `http://` or
+  `https://`. **This option is mandatory**.
+
+- [`verify`](https://www.freedesktop.org/software/systemd/man/machinectl.html#pull-tar%20URL%20%5BNAME%5D) -
+  (Optional) `no` (default), `signature` or `checksum`. Whether to verify the
+  image before making it available.
+
+- `force` - (Optional) `true` or `false` (default) If a local copy already
+  exists, delete it first and replace it by the newly downloaded image.
+
+- `type` - (Optional) `tar` (default) or `raw`. The type of image to download.
+
+## Networking
+
+The `nspawn` driver has support for host networking and also bridge mode
+networking. It can therefore be used with Nomad's [Consul Connect
+integration][consul_connect_integration].
+
+## Client Requirements
+
+The `nspawn` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The nspawn driver binary placed in the [plugin_dir][plugin_dir] directory.
+- `systemd-nspawn` to be installed
+- Nomad running with root privileges
+
+## Plugin Options
+
+- `enabled` - The `nspawn` driver may be disabled on hosts by setting this
+  option to `false` (defaults to `true`).
+
+- `volumes` - Enable support for Volumes in the driver (defaults to `true`).
+
+An example of using these plugin options with the new [plugin syntax][plugin] is
+shown below:
+
+```hcl
+plugin "nspawn" {
+  config {
+    enabled = true
+    volumes = true
+  }
+}
+```
+
+## Client Attributes
+
+The `nspawn` driver will set the following client attributes:
+
+- `driver.nspawn` - Set to `true` if systemd-nspawn is found and enabled on the
+  host node and Nomad is running with root privileges.
+
+- `driver.nspawn.version` - Version of `systemd-nspawn` e.g.: `244`.
+
+[nspawn-driver]: https://github.com/JanMa/nomad-driver-nspawn/releases
+[nspawn-guide]: https://github.com/JanMa/nomad-driver-nspawn/tree/master/example
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin-options
+[client_options]: /nomad/docs/configuration/client#options
+[docker_driver]: /nomad/docs/drivers/docker#using-the-port-map
+[consul_connect_integration]: /nomad/docs/integrations/consul-connect
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/pledge.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/pledge.mdx
new file mode 100644
index 0000000000..4b010f564b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/pledge.mdx
@@ -0,0 +1,332 @@
+---
+layout: docs
+page_title: Pledge task driver plugin
+description: Use the community-supported Pledge task driver to block unwanted syscall and filesystem access in Nomad jobs.
+---
+
+# Pledge task driver plugin
+
+Name: `pledge`
+
+The `pledge` driver executes programs similar to `exec` or `raw_exec`, but
+provides sandboxing by restricting syscalls the process is allowed to make.
+The `pledge` driver uses the [Landlock LSM][landlock] to restrict filesystem
+access, which can be significantly more efficient than creating a `chroot`.
+Isolation of CPU and memory resources is provided by leveraging features of
+cgroups v2. Network, PID, and IPC isolation is powered by Linux namespaces.
+
+Source on [GitHub][repository]
+
+Downloads on GitHub [releases][releases]
+
+#### Use cases
+
+The `pledge` driver is intended as a replacement for `raw_exec`. Sometimes
+there are those management tasks that just need to be run as `root` and directly
+access the filesystem or perform privileged operations. While `raw_exec`
+provides no isolation, the `pledge` driver uses Landlock to restrict the files
+or directories the task is allowed to access and modify. Specific groups of
+system calls are allow-listed in the task configuration, greatly reducing the
+attack surface of a mis-configured or compromised task.
+
+#### About
+
+The `pledge` driver is fundamentally powered by the [pledge utility for Linux]
+[pledge] by Justine Tunney. The driver invokes this `pledge.com` CLI tool along
+with `nsenter` and `unshare` to create a strict sandbox in which to execute a
+given command.
+
+## Task Configuration
+
+```hcl
+task "http" {
+  driver = "pledge"
+  config {
+    command    = "python3"
+    args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+    promises   = "stdio rpath inet"
+    unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+  }
+}
+```
+
+The `pledge` driver supports the following task configuration in the job spec:
+
+- `command` - The command to execute. Must be provided. The driver will search
+  for the command on the `$PATH` of the Nomad Client unless an absolute path
+  is given.
+
+- `args` - (Optional) A list of arguments to the `command`. References to
+  environment variables or any interpolable Nomad variables will be interpolated
+  before launching the task.
+
+- `promises` - A set of promises needed for the command to run. See below for
+  more information.
+
+- `unveil` - (Optional) A list of filepaths and access rights to grant to the
+  command. See below for more information.
+
+- `importance` - (Optional) One of `"lowest"`, `"low"`, `"normal"`, `"high"`,
+  `"highest"`. Indicates the `nice` value with which to run `command` (default
+  is `"normal"`). A lower importance indicates the command should be given a
+  lower priority with regard to CPU time relative to other tasks.
+
+## Syscall Isolation (promises)
+
+When using the `pledge` task driver, by default most syscalls will become
+unavailable. A process that attempts to use an unavailable syscall will receive
+an `EPERM` error from the kernel. By specifying a set of `promises`, additional
+syscalls will be made available to the `command`.
+
+See the complete documetation for [promises][promises].
+
+| Promise | Description |
+| ------- | ------------|
+| `stdio` | allow stdio, threads, and benign system calls |
+| `rpath` | allow filesystem read operations |
+| `wpath` | allow filesystem write operations |
+| `cpath` | allow filesystem create operations |
+| `dpath` | allow creation of special files |
+| `flock` | allow file locking |
+| `tty` | allow terminal ioctls |
+| `recvfd` | allow recvmsg |
+| `sendfd` | allow sendmsg |
+| `fattr` | allow changing some struct stat bits |
+| `inet` | allow IPv4 and IPv6 |
+| `unix` | allow using Unix Domain Sockets |
+| `dns` | allow DNS |
+| `proc` | allow fork process creation and control |
+| `id` | allow setuid and friends |
+| `exec` | allow executing binaries |
+| `prot_exec` | allow creating executable memory |
+| `vminfo` | allow operations around reading `/proc` |
+| `tmppath` | allow access to `/tmp` |
+
+## Filesystem Isolation (unveil)
+
+By default the `command` will not be able to access the filesystem. Using some
+promises will implicitly allow access to specific parts of the filesystem where
+applicable. The `unveil` configuration is used to grant access to additional
+filesytem paths at a specified permission level.
+
+The format of the `unveil` parameter is a list of paths and associated
+permissions. Permissions can be any combination of `r`, `w`, `c` and `x` for
+read, write, create and execute privileges.
+
+Note that reading a file also requires the `rpath` promise, writing a file
+requires the `wpath` promise, creating a file requires the `cpath` promise, and
+executing a program requires the `exec` promise.
+
+#### Examples
+
+This example allows reading of the `/srv/www` directory.
+
+```hcl
+unveil = ["r:/srv/www"]
+```
+
+This example allows executing `/opt/bin/program` and reading `/etc/prog.d`.
+
+```hcl
+unveil = ["x:/opt/bin/program", "r:/etc/prog.d"]
+```
+
+It can be useful to `unveil` the Nomad Task Directory, which can be done by
+specifying the interpolation value.
+
+```hcl
+unveil = ["rwc:${NOMAD_TASK_DIR}"]
+```
+
+## Networking
+
+The `pledge` driver supports `none`, `host`, and `group` networking modes.
+
+#### host networking
+
+If using `host` networking mode, it can be very convenient to bless the
+[pledge][pledge] utility with the `cap_net_bind_service` Linux capability. This will
+enable Nomad tasks using the pledge driver to bind to privileged ports (i.e.
+below 1024) while using host networking mode.
+
+```shell-session
+sudo setcap cap_net_bind_service+eip /opt/bin/pledge-1.8.com
+```
+
+For convenience the `driver.pledge.cap.net_bind` Client attribute will indicate
+whether the Linux capability is set on the executable.
+
+#### bridge networking
+
+If using `bridge` networking mode, be sure to install the standard [CNI plugins]
+[cni] as required by the Nomad client.
+
+## Client Requirements
+
+The `pledge` driver requires the following:
+
+- 64-bit amd64 Linux host
+  - kernel version 5.13+
+  - cgroups v2 enabled
+- The `pledge` driver binary placed in [plugin_dir][plugin_dir]
+- The `pledge.com` utility executable on the host
+
+## Plugin Options
+
+- `pledge_executable` - The path to the `pledge.com` binary. The pledge utility
+can be [downloaded][download] directly from its creator, or compiled manually
+from [source][pledge_github].
+
+```hcl
+plugin "nomad-pledge-driver" {
+  config {
+    pledge_executable = "/opt/bin/pledge-1.8.com"
+  }
+}
+```
+
+## Client Attributes
+
+The `pledge` driver will set the following Client attributes:
+
+| Attribute | Description |
+| ----------| ----------- |
+| `driver.pledge` | set to `1` if the driver is enabled |
+| `driver.pledge.abs` | the absolute path to the pledge.com utility |
+| `driver.pledge.cap.net_bind` | indicates whether the NET_BIND linux capability is set |
+| `driver.pledge.os` | the detected operating system |
+
+## Resource Isolation
+
+CPU and memory resource isolation is enforced by cgroups v2 features, and is
+configured through the resources block in task configuration.
+
+```hcl
+resources {
+  cores  = 3
+  memory = 512
+}
+```
+
+#### cpu bandwidth
+
+The `pledge` driver always enforces a maximum CPU bandwidth available to the
+task. The bandwidth is calculated whether `resources.cpu` or `resources.cores`
+is configured.
+
+If `resources.cores` is set, the scheduler reserves that many CPU cores for use
+by the task, and only this task will be able to run on those cores.
+
+#### memory oversubscription
+
+If the Nomad scheduler is configured to enable memory [oversubscription]
+[oversub], the `pledge` driver will enable configuring `memory_max` in addition
+to `memory`. In this case, `memory_max` indicates the maximum amount of memory
+the task is able to request before being OOM killed, and `memory` represents a
+minimum amount of memory the kernel will guarantee is available for the Task.
+
+```hcl
+resources {
+  cpu        = 2000
+  memory     = 1024
+  memory_max = 2048
+}
+```
+
+## Capabilities
+
+The `pledge` driver implements the following [capabilities][capabilities].
+
+| Feature              | Implementation    |
+| ------------         | ------------------|
+| send signals         | true              |
+| exec                 | false             |
+| filesystem isolation | none (landlock)   |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+For sending signals, use the `nomad alloc signal` command.
+
+## Examples
+
+A larger set of examples are available in the [source][hack] repository.
+
+Showing how to `curl example.com`.
+
+```hcl
+job "curl" {
+  type = "batch"
+  group "group" {
+    task "curl" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command  = "curl"
+        args     = ["example.com"]
+        promises = "stdio rpath inet dns sendfd"
+      }
+    }
+  }
+}
+```
+
+An example using the Python built-in HTTP server to render a trivial web page.
+
+```hcl
+job "http" {
+  group "group" {
+    network {
+      mode = "host"
+      port "http" { static = 8181 }
+    }
+
+    task "task" {
+      driver = "pledge"
+      user   = "nobody"
+      config {
+        command    = "python3"
+        args       = ["-m", "http.server", "${NOMAD_PORT_http}", "--directory", "${NOMAD_TASK_DIR}"]
+        promises   = "stdio rpath inet"
+        unveil     = ["r:/etc/mime.types", "r:${NOMAD_TASK_DIR}"]
+      }
+
+      template {
+        destination = "local/index.html"
+        data        = <<EOH
+<!doctype html>
+<html>
+  <title>example</title>
+  <body><p>Hello, friend!</p></body>
+</html>
+EOH
+      }
+    }
+  }
+}
+```
+
+## Troubleshooting
+
+When setting up a new Task using the `nomad-pledge-driver` task driver, it
+helps to run the command manually using the `pledge` utility to make sure the
+necessary promises and unveil paths are well understood. To figure out which
+syscalls process needs to make, it can be run under `strace -ff`. When a syscall
+is blocked, you'll see `"EPERM (Operation not permitted)"`
+
+```shell-session
+strace -ff /opt/bin/pledge-1.8.com -p "stdio rpath inet" -- curl example.com
+```
+
+[capabilities]: /nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error
+[cni]: https://developer.hashicorp.com/nomad/docs/install
+[download]: https://justine.lol/pledge/#download
+[hack]: https://github.com/shoenig/nomad-pledge-driver/tree/main/hack
+[landlock]: https://docs.kernel.org/security/landlock.html
+[oversub]: https://developer.hashicorp.com/nomad/api-docs/operator/scheduler#memoryoversubscriptionenabled-1
+[pledge]: https://justine.lol/pledge/
+[pledge_github]: https://github.com/jart/pledge
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[promises]: https://justine.lol/pledge/#promises
+[repository]: https://github.com/shoenig/nomad-pledge-driver
+[releases]: https://github.com/shoenig/nomad-pledge-driver/releases
+
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/pot.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/pot.mdx
new file mode 100644
index 0000000000..d1aae2ef7d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/pot.mdx
@@ -0,0 +1,100 @@
+---
+layout: docs
+page_title: Pot task driver plugin
+description: >-
+  Use the community-supported Pot task driver to run pot containers inside a  FreeBSD Jail in Nomad jobs.
+---
+
+# Pot task driver plugin
+
+Name: `pot`
+
+The Pot task driver provides an interface for using [pot][pot-github-repo] for dynamically running applications inside a FreeBSD Jail.
+Download the external nomad-pot-driver from its [releases page][nomad-pot-driver].
+
+## Task Configuration
+
+```hcl
+task "nginx-pot" {
+    driver = "pot"
+
+    config {
+      image = "https://pot-registry.zapto.org/registry/"
+      pot = "FBSD120-nginx"
+      tag = "1.0"
+      command = "nginx"
+      args = [
+        "-g 'daemon off;'"
+      ]
+      network_mode = "public-bridge"
+      port_map = {
+        http = "80"
+      }
+      copy = [
+        "/root/index.html:/usr/local/www/nginx-dist/index.html",
+        "/root/nginx.conf:/usr/local/etc/nginx/nginx.conf"
+      ]
+      mount = [
+        "/tmp/test:/root/test",
+      ]
+      mount_read_only = [
+        "/tmp/test2:/root/test2"
+      ]
+      extra_hosts = [
+        "artifactory.yourdomain.com:192.168.0.1",
+        "mail.yourdomain.com:192.168.0.2"
+      ]
+   }
+}
+```
+
+The pot task driver supports the following parameters:
+
+- `image` - The url for the http registry from where to get the image.
+
+- `pot` - Name of the image in the registry.
+
+- `tag` - Version of the image.
+
+- `command` - Command that is going to be executed once the jail is started.
+
+- `args` - (Optional) List of options for the command executed on the command argument.
+
+- `network_mode` - (Optional) Defines the network mode of the pot. Default: **"public-bridge"**
+
+  Possible values are:
+
+  **"public-bridge"** pot creates an internal virtual network with a NAT table where all traffic is going to be sent.
+
+  **"host"** pot bounds the jail directly to a host port.
+
+- `port_map` - (Optional) Sets the port on which the application is listening inside of the jail. If not set, the application will inherit the port configuration from the image.
+
+- `copy` - (Optional) Copies a file from the host machine to the pot jail in the given directory.
+
+- `mount` - (Optional) Mounts a read/write folder from the host machine to the pot jail.
+
+- `mount_read_only` - (Optional) Mounts a read only directory inside the pot jail.
+
+- `extra_hosts` - (Optional) A list of hosts, given as host:IP, to be added to /etc/hosts
+
+## Client Requirements
+
+`pot Task Driver` requires the following:
+
+- 64-bit FreeBSD 12.0-RELEASE host .
+- The FreeBSD's Nomad binary (available as a package).
+- The pot-task-driver binary placed in the [plugin_dir][plugin_dir] directory.
+- Installing [pot][pot-github-repo] and following the install [guide][pot-install-guide].
+- Webserver from where to serve the images. (simple file server)
+- Following lines need to be included in your rc.conf
+
+```
+nomad_user="root"
+nomad_env="PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/sbin:/bin"
+```
+
+[nomad-pot-driver]: https://github.com/trivago/nomad-pot-driver
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[pot-github-repo]: https://github.com/pizzamig/pot
+[pot-install-guide]: https://github.com/pizzamig/pot/blob/master/share/doc/pot/Installation.md
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/rookout.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/rookout.mdx
new file mode 100644
index 0000000000..8451cc3771
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/rookout.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Rookout task driver plugin
+description: Use the community-supported Rookout task driver to run your Java application with Rookout in Nomad jobs.
+---
+
+# Rookout task driver plugin
+
+Name: `java-rookout`
+
+The Rookout Nomad driver is used to execute Java applications packaged into a Java Jar file and automatically add the Rookout SDK to them.
+
+[Rookout](https://rookout.com) is a developer solution for Cloud Native debugging and live-data collection. Rookout’s Non-Breaking Breakpoints let you collect any type of data on the fly with no extra coding, redeployments, or restarts.
+
+More info about the Rookout SDK is available in the [Rookout docs](https://docs.rookout.com).
+
+## Prerequisites
+
+Using this driver requires you to have a Rookout token which you can get by [signing up](http://rookout.com).
+
+This driver is based on the Nomad [Java driver](/nomad/docs/drivers/java).
+
+1. Clone the driver's repo: `git clone https://github.com/rookout/rookout-nomad-driver`
+2. Change to the cloned dir: `cd rookout-nomad-driver`
+3. Create a plugin dir (unless you already have one for your Nomad installation): `mkdir plugins`
+4. Copy the corresponding binary from the `bin` folder, for example: `cp ./bin/java-rookout-linux-x64 plugins/java-rookout`
+5. Make sure that the driver has execution permission: `chmod +x ./plugins/java-rookout`
+6. When running the Nomad agent, be sure to set the plugins dir accordingly, for example: `sudo nomad agent -dev -plugin-dir=/home/user/rookout-nomad-driver/plugins`
+
+## Task Configuration
+
+The `java-rookout` driver accepts all configuration options of the [`java`](/nomad/docs/drivers/java) driver.
+
+Set the `rookout_token` config key to your Rookout token, or define it as a variable and pass it as a parameter.
+
+For example:
+```hcl
+task "run-with-rookout" {
+  driver = "java-rookout"
+
+  config {
+    rookout_token = "ea15c38c4e05cf4549b..."
+  }
+}
+```
+
+Additional Rookout configuration can be passed as environment variables like so:
+```hcl
+env {
+    ROOKOUT_REMOTE_ORIGIN="https://github.com/Rookout/tutorial-java"
+}
+```
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/community/singularity.mdx b/content/nomad/v1.9.x/content/plugins/drivers/community/singularity.mdx
new file mode 100644
index 0000000000..bd6e6167e2
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/community/singularity.mdx
@@ -0,0 +1,185 @@
+---
+layout: docs
+page_title: Singularity task driver plugin
+description: >-
+  Use the community-supported Singularity task driver to run application containers using Singularity in Nomad jobs.
+---
+
+# Singularity task driver plugin
+
+Name: `Singularity`
+
+The `Singularity` driver provides an interface for using Singularity for running application
+containers. Download the external Singularity driver from its [releases page][singularity-driver].
+
+## Task Configuration
+
+```hcl
+task "lolcow" {
+  driver = "Singularity"
+
+  config {
+     # this example run an image from sylabs container library with the
+     # canonical example of lolcow
+     image = "library://sylabsed/examples/lolcow:latest"
+     # command can be run, exec or test
+     command = "run"
+  }
+}
+```
+
+The `Singularity` driver supports the following configuration in the job spec:
+
+- `image` - The Singularity image to run. It can be a local path or a supported URI.
+
+  ```hcl
+  config {
+    image = "library://sylabsed/examples/lolcow:latest"
+  }
+  ```
+
+- `verbose` - (Optional) Enables extra verbosity in the Singularity runtime logging.
+  Defaults to `false`.
+
+  ```hcl
+  config {
+    verbose = "false"
+  }
+  ```
+
+- `debug` - (Optional) Enables extra debug output in the Singularity runtime
+  logging. Defaults to `false`.
+
+  ```hcl
+  config {
+    debug = "false"
+  }
+  ```
+
+- `command` - Singularity command action; can be `run`, `exec` or `test`.
+
+  ```hcl
+  config {
+    command = "run"
+  }
+  ```
+
+- `args` - (Optional) Singularity command action arguments, when trying to pass arguments to `run`, `exec` or `test`.
+  Multiple args can be given by a comma separated list.
+
+  ```hcl
+  config {
+    args = [ "echo", "hello Cloud" ]
+  }
+  ```
+
+- [`binds`][bind] - (Optional) A user-bind path specification. This spec has the format `src[:dest[:opts]]`, where src and
+  dest are outside and inside paths. If dest is not given, it is set equal to src.
+  Mount options ('opts') may be specified as 'ro' (read-only) or 'rw' (read/write, which
+  is the default). Multiple bind paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    bind = [ "host/path:/container/path" ]
+  }
+  ```
+
+- [`overlay`][overlay] - (Optional) Singularity command action flag, to enable an overlayFS image for persistent data
+  storage or as read-only layer of container. Multiple overlay paths can be given by a comma separated list.
+
+  ```hcl
+  config {
+    overlay = [ "host/path/to/overlay" ]
+  }
+  ```
+
+- [`security`][security] - (Optional) Allows the root user to leverage security modules such as
+  SELinux, AppArmor, and seccomp within your Singularity container.
+  You can also change the UID and GID of the user within the container at runtime.
+
+  ```hcl
+  config {
+    security = [ "uid:1000 " ]
+  }
+  ```
+
+- `contain` - (Optional) Use minimal `/dev` and empty other directories (e.g. `/tmp` and `$HOME`) instead of sharing filesystems from your host.
+
+  ```hcl
+  config {
+    contain = "false"
+  }
+  ```
+
+- `workdir` - (Optional) Working directory to be used for `/tmp`, `/var/tmp` and `$HOME` (if -c/--contain was also used).
+
+  ```hcl
+  config {
+    workdir = "/path/to/folder"
+  }
+  ```
+
+- `pwd` - (Optional) Initial working directory for payload process inside the container.
+
+  ```hcl
+  config {
+    pwd = "/path/to/folder"
+  }
+  ```
+
+## Networking
+
+Currently the `Singularity` driver only supports host networking. For more detailed instructions on how to set up networking options, please refer to the `Singularity` user guides [singularity-network]
+
+## Client Requirements
+
+The `Singularity` driver requires the following:
+
+- 64-bit Linux host
+- The `linux_amd64` Nomad binary
+- The Singularity driver binary placed in the [plugin_dir][plugin_dir] directory.
+- [`Singularity`][singularity] v3.1.1+ to be installed
+
+## Plugin Options ((#plugin_options))
+
+- `enabled` - The `Singularity` driver may be disabled on hosts by setting this option to `false` (defaults to `true`).
+
+- `singularity_cache` - The location in which all containers are stored (commonly defaults to `/var/lib/singularity`). See [`Singularity-cache`][singularity-cache] for more details.
+
+An example of using these plugin options with the new [plugin
+syntax][plugin] is shown below:
+
+```hcl
+plugin "nomad-driver-Singularity" {
+  config {
+    enabled = true
+    singularity_path = "/var/lib/singularity"
+  }
+}
+```
+
+Please note the plugin name should match whatever name you have specified for the external driver in the [plugin_dir][plugin_dir] directory.
+
+## Client Attributes
+
+The `Singularity` driver will set the following client attributes:
+
+- `driver.singularity` - Set to `1` if Singularity is found and enabled on the host node.
+- `driver.singularity.version` - Version of `Singularity` e.g.: `3.1.0`.
+
+## Resource Isolation
+
+This driver supports CPU and memory isolation via the `Singularity` cgroups feature. Network
+isolation is supported via `--net` and `--network` feature (Singularity v3.1.1+ required).
+
+[singularity-driver]: https://github.com/sylabs/nomad-driver-singularity
+[singularity_man]: https://linuxcontainers.org/Singularity/manpages/man5/Singularity.container.conf.5.html#lbAM
+[plugin]: /nomad/docs/configuration/plugin
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[plugin-options]: #plugin_options
+[singularity]: https://github.com/sylabs/singularity
+[singularity-cache]: https://www.sylabs.io/guides/3.1/user-guide/appendix.html#c
+[bind]: https://www.sylabs.io/guides/3.1/user-guide/bind_paths_and_mounts.html
+[security]: https://www.sylabs.io/guides/3.1/user-guide/security_options.html
+[overlay]: https://www.sylabs.io/guides/3.1/user-guide/persistent_overlays.html
+[singularity-network]: https://www.sylabs.io/guides/3.1/user-guide/networking.html
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/exec2.mdx b/content/nomad/v1.9.x/content/plugins/drivers/exec2.mdx
new file mode 100644
index 0000000000..8aa36d9286
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/exec2.mdx
@@ -0,0 +1,318 @@
+---
+layout: docs
+page_title: Exec2 task driver plugin
+description: >-
+  The Exec2 task driver executes a command for a job task and leverages Linux kernel features such as Landlock LSM, cgroups v2, and the `unshare` system utility. Learn how to configure and install the Exec2 task driver plugin. Review capabilities, client requirements, and concepts such as filesystem and resource isolation. Learn how to use the Exec2 task driver in your Nomad job. Configure command, command args, paths, memory, CPU resources, and out-of-memory (OOM) behavior.
+---
+
+# Exec2 task driver plugin
+
+Name: `exec2`
+
+The `exec2` driver is used to execute a command for a task. It offers a security
+model optimized for running 'ordinary' processes with very low startup times
+and minimal overhead in terms of CPU, disk, and memory utilization. The `exec2`
+driver leverages kernel features such as the [Landlock LSM][landlock], cgroups
+v2, and the [`unshare`][unshare] system utility.
+
+Review the source on [GitHub][github].
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-exec2/) and verify the binary using the
+available SHA-256 sums. After downloading nomad-driver-exec2 driver, unzip the package. Make sure
+that the `nomad-driver-exec2` binary is available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path, specified by the client's config file, before continuing with the
+other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-exec2
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-exec2
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example below is a short demonstration of what a task making use of the
+exec2 task driver looks like:
+
+```hcl
+job "http" {
+  group "web" {
+    task "python" {
+      driver = "exec2"
+      config {
+        command = "python3"
+        args    = ["-m", "http.server", "8080", "--directory", "${NOMAD_TASK_DIR}"]
+        unveil  = ["r:/etc/mime.types"]
+      }
+    }
+  }
+}
+```
+
+## Client Requirements
+
+The `exec2` task driver is not built into Nomad. It must be [downloaded][releases]
+onto the client host in the configured plugin directory.
+
+- Linux 5.15+
+- Cgroups v2 enabled
+- Landlock LSM enabled
+- Commands `nsenter` and `unshare`
+- Nomad client running as root
+
+## Capabilities
+
+The `exec2` task driver implements the following driver [capabilities][capabilities]
+
+| Feature              | Implementation    |
+| -------------------- | ----------------- |
+| `nomad alloc signal` | true              |
+| `nomad alloc exec`   | false             |
+| filesystem isolation | unveil            |
+| network isolation    | host, group, none |
+| volume mounting      | false             |
+
+## Concepts
+
+### Filesystem Isolation
+
+##### landlock
+
+The `exec2` task driver makes use of [`go-landlock`][landlock] for providing
+filesystem isolation, making the host filesystem unreachable except where
+explicitly allowed.
+
+By default a task is enabled to access its task directory and its shared alloc
+directory. The paths to these directories are accessible by reading the environment
+variables `$NOMAD_TASK_DIR` and `$NOMAD_ALLOC_DIR` respectively.
+
+A file access mode must also be specified when granting additional filesystem
+access to a path. This is done by prefix the path with `'r'`, `'w'`, `'x'`,
+and/or `'c'` indicating read, write, executable, and create permissions,
+respectively. e.g.,
+
+- <code>r:/srv/www</code> - read-only access to `/srv/www`
+- <code>rwc:/tmp</code> - read, write, and create files in `/tmp`
+- <code>rx:/opt/bin/application</code> - read and execute a specific application
+- <code>wc:/var/log</code> - write and create files in `/var/log`
+
+This style of permission control is modeled after the [`unveil`][unveil] system
+call pioneered by the OpenBSD project. In configuration parameters we refer to
+"unveil"-ing of filesystem paths as `exec2` is leveraging landlock to emulate
+the semantics of `unveil`.
+
+##### dynamic workload users
+
+While landlock prevents tasks from accessing the host filesystem, Nomad 1.8
+introduces `dynamic workload users` which enable tasks to be run as a UID/GID
+that is not assigned to any user. This provides protection from non-root users
+getting access inside the task and allocation directories created for the task.
+
+To make use of a dynamic workload user, simply leave the `user` field blank in
+the task definition of an `exec2` task.
+
+### Resource Isolation
+
+Similar to `exec` and other container runtimes, `exec2` makes use of cgroups for
+limiting the amount of CPU and RAM a task may consume.
+
+## Configuration
+
+### Plugin Configuration
+
+The default plugin configuration is shown below. System default paths are enabled,
+but nothing else. These default paths enable basic functionality like reading
+system TLS certificates, executing programs in `/bin`, `/usr/bin`, and accessing
+system shared object files. The exact set of paths is system dependent, and can
+be disabled or customized in plugin config.
+
+The default set of paths are listed below. These paths are enabled only if they
+are found to exist at the time of the task launching.
+
+##### shared objects
+
+```
+rx:/lib
+rx:/lib64
+rx:/usr/lib
+rx:/usr/libexec
+rx:/usr/local/lib
+rx:/usr/local/lib64
+r:/etc/ld.so.conf
+r:/etc/ld.so.cache
+r:/etc/ld.so.conf.d
+```
+
+##### io, common
+
+```
+rwc:/tmp
+rw:/dev/null
+r:/dev/zero
+r:/dev/fd
+rw:/dev/stdin
+rw:/dev/stdout
+r:/dev/urandom
+w:/dev/log
+r:/usr/share/locale
+r:/proc/self/cmdline
+r:/usr/share/zoneinfo
+r:/usr/share/common-licenses
+r:/proc/sys/kernel/ngroups_max
+r:/proc/sys/kernel/cap_last_cap
+r:/proc/sys/vm/overcommit_memory
+```
+
+##### dns
+
+```
+r:/etc/hosts
+r:/hostname
+r:/etc/services
+r:/etc/protocols
+r:/etc/resolv.conf
+```
+
+##### certificates
+
+```
+r:/etc/ssl/certs
+r:/etc/pki/tls/certs
+r:/etc/ssl/ca-bundle.pem
+r:/etc/pki/tls/cacert.pem
+r:/etc/pki/ca-trust-extracted/pem/tls-ca-bundle.pem
+r:/etc/ssl/cert.pem
+```
+
+Additional allowable paths can be specified at the plugin level, which applies
+to all tasks making use of the `exec2` task driver, or at the task level, which
+will apply specifically to each task.
+
+```hcl
+plugin "nomad-driver-exec2" {
+  config {
+    unveil_defaults = true
+    unveil_paths    = []
+    unveil_by_task  = false
+  }
+}
+```
+
+- `unveil_defaults` - (default: `true`) - enable or disable default system paths
+  useful for running basic commands
+- `unveil_paths` - (default: `[]`) - a list of filesystem paths with permissions
+  to grant all tasks
+  ```hcl
+  unveil_paths = ["rx:/opt/bin", "r:/srv/certs"]
+  ```
+- `unveil_by_task` - (default: `false`) - enable or disable job submitters to
+  specify additional filesystem path access within task config
+
+### Task Configuration
+
+##### config
+
+Task configuration for an exec2 task includes setting a `command`, `args` for
+the command, and additional `unveil` filesystem paths if `unveil_by_task` is
+enabled in plugin configuration.
+
+```hcl
+config {
+  command       = "/usr/bin/cat"
+  args          = ["/etc/os-release"]
+  unveil        = ["r:/etc/os-release"]
+  oom_score_adj = 500
+}
+```
+
+- `command` - (string: required) - command to run
+- `args` - (list(string): optional) - list of arguments to provide
+  to `command`
+- `unveil` - (list(string): optional) - list of additional filesystem paths to
+  provide access to the task (requires `unveil_by_task` in plugin config).
+- `oom_score_adj` - (optional) - The likelihood of the task being OOM killed,
+  must be a positive integer. Defaults to `0`.
+
+##### cpu
+
+Tasks are limited in CPU resources by setting the `cpu` or `cores` values in the
+task `resources` block.
+
+- `cpu` - (default: `100`) - limits the CPU bandwidth allowable for the task to
+  make use of in MHz, may not be used with `cores`.
+- `cores` - (int: optional) - specifies the number of CPU cores to reserve
+  specifically for the task, may not be used with `cpu`
+
+##### memory
+
+Tasks are limited in memory resources by setting `memory` and optionally the
+`memory_max` values in the task `resources` block.
+
+### Node Attributes
+
+When installed, the `exec2` plugin provides the following node attributes which
+can be used as constraints when authoring jobs.
+
+```
+driver.exec2.unveil.defaults    = true
+driver.exec2.unveil.tasks       = true
+```
+
+[capabilities]: https://developer.hashicorp.com/nomad/docs/concepts/plugins/task-drivers#task-driver-plugin-api
+[github]: https://github.com/hashicorp/nomad-driver-exec2
+[landlock]: https://github.com/shoenig/go-landlock
+[releases]: https://releases.hashicorp.com/nomad-driver-exec2
+[unshare]: https://www.man7.org/linux/man-pages/man1/unshare.1.html
+[unveil]: https://man.openbsd.org/unveil
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/index.mdx b/content/nomad/v1.9.x/content/plugins/drivers/index.mdx
new file mode 100644
index 0000000000..02d441b2ec
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: Task driver plugins
+description: Task driver plugins extend Nomad functionality to provide resource isolation when executing job tasks. Review the Exec2, Podman, and Virt task driver reference. Explore plugins developed by the Nomad user community.
+---
+
+# Task driver plugins
+
+This section provides reference information for task driver plugins.
+
+@include 'task-driver-intro.mdx'
+
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/podman.mdx b/content/nomad/v1.9.x/content/plugins/drivers/podman.mdx
new file mode 100644
index 0000000000..7aaa4925db
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/podman.mdx
@@ -0,0 +1,737 @@
+---
+layout: docs
+page_title: Podman task driver plugin
+description: >-
+  The Podman task driver plugin uses the Pod Manager daemonless container runtime to execute Nomad workload tasks. Learn how to configure and install the Podman task driver plugin. Review capabilities, client requirements, plugin options, and network configuration. Learn how to use the Podman task driver in your Nomad job. Configure image registry authentication, Linux capabilities, host devices, entrypoint, paths, image, labels, logging, memory, network mode, ports, volumes, working directory, and container privileges.
+---
+
+# Podman task driver plugin
+
+Name: `podman`
+
+The Podman task driver plugin for Nomad uses the [Pod Manager (podman)][podman]
+daemonless container runtime for executing Nomad tasks. Podman supports OCI
+containers and its command line tool is meant to be [a drop-in replacement]
+[podman-cli] for docker.
+
+Source is on [GitHub][github]
+
+## Installation
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+You can download a [precompiled binary](https://releases.hashicorp.com/nomad-driver-podman/) and verify the
+binary using the available SHA-256 sums. After downloading nomad-driver-podman
+driver, unzip the package. Make sure that the `nomad-driver-podman` binary is
+available on your [plugin_dir](/nomad/docs/configuration#plugin_dir) path,
+specified by the client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install wget gpg coreutils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install -y nomad-driver-podman
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-podman
+```
+
+</Tab>
+</Tabs>
+
+## Usage
+
+The example job created by [`nomad init -short`][nomad-init] is easily adapted
+to use Podman instead:
+
+```hcl
+job "redis" {
+  group "cache" {
+    network {
+      port "redis" { to = 6379 }
+    }
+
+    task "redis" {
+      driver = "podman"
+      config {
+        image = "docker.io/library/redis:7"
+        ports = ["redis"]
+      }
+    }
+  }
+}
+```
+
+Refer to the project's [homepage][homepage] for details.
+
+## Client Requirements
+
+The Podman task driver is not built into Nomad. It must be
+[downloaded][downloaded] onto the client host in the configured plugin
+directory.
+
+- Linux host with [`podman`][podman] installed
+- For rootless containers you need a system supporting cgroups v2 and a few
+  other things, follow [this tutorial][rootless_tutorial].
+
+You need a v3.x or higher podman binary and a system socket [activation unit]
+[rest_api]. It is recommended to install podman via your system's package
+manager, which will configure systemd for you.
+
+Ensure that Nomad can find the plugin, refer to [`plugin_dir`][plugin_dir].
+
+## Capabilities
+
+The `podman` driver implements the following [capabilities](/nomad/docs/concepts/plugins/task-drivers#capabilities-capabilities-error).
+
+| Feature              | Implementation          |
+| -------------------- | ----------------------- |
+| `nomad alloc signal` | true                    |
+| `nomad alloc exec`   | true                    |
+| filesystem isolation | image                   |
+| network isolation    | host, group, task, none |
+| volume mounting      | true                    |
+
+## Task Configuration
+
+- `apparmor_profile` - (Optional) Name of an AppArmor profile to use instead of
+  the default profile. The special value `unconfined` disables AppArmor for this container.
+
+  ```hcl
+  config {
+    apparmor_profile = "your-profile"
+  }
+  ```
+
+- `args` - (Optional) A list of arguments to the optional command. If no
+  [`command`] is specified, the arguments are passed directly to the container.
+
+  ```hcl
+  config {
+    args = [
+      "arg1",
+      "arg2",
+    ]
+  }
+  ```
+
+- `auth` - (Optional) Authenticate to the image registry using a static
+  credential. By setting tlsVerify to false the driver will allow using self-
+  signed certificates or plain HTTP connections to the registry.
+
+  ```hcl
+  config {
+    image = "your.registry.tld/some/image"
+    auth {
+      username = "someuser"
+      password = "sup3rs3creT"
+      tlsVerify = false
+    }
+  }
+  ```
+
+- `auth_soft_fail` - (Optional) Ignore errors returned from auth backend so Podman can fall back to a different auth method.
+
+  ```hcl
+  config {
+    auth_soft_fail = true
+  }
+  ```
+
+- `cap_add` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-add`.
+
+  ```hcl
+  config {
+    cap_add = [
+      "SYS_TIME"
+    ]
+  }
+  ```
+
+- `cap_drop` - (Optional) A list of Linux capabilities as strings to pass to
+  `--cap-drop`.
+
+  ```hcl
+  config {
+    cap_drop = [
+      "MKNOD"
+    ]
+  }
+  ```
+
+- `command` - (Optional) The command to run when starting the container.
+
+  ```hcl
+  config {
+    command = "some-command"
+  }
+  ```
+
+- `cpu_hard_limit` (Optional) `true` or `false`. Use hard CPU limiting instead
+  of soft limiting. By default this is `false`, which means Podman uses soft
+  limiting so that containers are able to burst above their CPU limit when there
+  is idle capacity.
+
+- `cpu_cfs_period` - (Optional) Set the CPU period for the [Completely Fair
+  Scheduler (CFS)](https://docs.kernel.org/scheduler/sched-design-CFS.html),
+  which is a duration in microseconds. Refer to [`podman run
+  --cpu-period`](https://docs.podman.io/en/latest/markdown/podman-run.1.html#cpu-period-limit)
+  for details.
+
+- `devices` - (Optional) A list of `host-device[:container-device][:permissions]`
+  definitions. Each entry adds a host device to the container. Optional
+  permissions can be used to specify device permissions, it is a combination of
+  `r` for read, `w` for write, and `m` for `mknod(2)`. Refer to Podman's
+  documentation for more details.
+
+  ```hcl
+  config {
+    devices = [
+      "/dev/net/tun"
+    ]
+  }
+  ```
+
+- `entrypoint` - (Optional) The entrypoint for the container. Defaults to the
+  `entrypoint` set in the image.
+
+  ```hcl
+  config {
+    entrypoint = "/entrypoint.sh"
+  }
+  ```
+
+- `extra_hosts` - (Optional) Set additional hosts in the container.
+
+  ```hcl
+  config {
+    extra_hosts = ["test4.localhost:127.0.0.2", "test6.localhost:[::1]"]
+  }
+  ```
+
+- `force_pull` - (Optional) `true` or `false` (default). Always pull the latest
+  image on container start.
+
+  ```hcl
+  config {
+    force_pull = true
+  }
+  ```
+
+- `hostname` - (Optional) The hostname to assign to the container. When
+  launching more than one of a task (using [`count`]) with this option set,
+  every container the task starts will have the same hostname.
+
+- `image` - The image to run. Accepted transports are `docker` (default if
+  missing), `oci-archive` and `docker-archive`. Images referenced as
+  [short-names] will be treated according to user-configured preferences.
+
+  ```hcl
+  config {
+    image = "docker://redis"
+  }
+  ```
+
+- `image_pull_timeout` - (Optional) Time duration for your pull timeout
+  (default to `"5m"`). Cannot be longer than the [`client_http_timeout`].
+
+  ```hcl
+  config {
+    image_pull_timeout = "5m"
+  }
+  ```
+
+- `init` - (Optional) Run an `init` inside the container that forwards signals
+  and reaps processes.
+
+  ```hcl
+  config {
+    init = true
+  }
+  ```
+
+- `init_path` - (Optional) Path to the `container-init` binary.
+
+  ```hcl
+  config {
+    init = true
+    init_path = "/usr/libexec/podman/catatonit"
+  }
+  ```
+
+- `labels` - (Optional) Set labels on the container.
+
+  ```hcl
+  config {
+    labels = {
+      "nomad" = "job"
+    }
+  }
+  ```
+
+- `logging` - (Optional) Configure logging. Also refer to the plugin option
+  [`disable_log_collection`].
+
+    - `driver = "nomad"` - (Default) Podman redirects its combined
+    `stdout/stderr` logstream directly to a Nomad `fifo`. Benefits of this
+    mode are: zero overhead, don't have to worry about log rotation at system
+    or Podman level. Downside: you cannot easily ship the logstream to a log
+    aggregator plus `stdout/stderr` is multiplexed into a single stream.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "nomad"
+      }
+    }
+    ```
+
+    - `driver = "journald"` - The container log is forwarded from Podman to the
+    `journald` on your host. Next, it's pulled by the Podman API back from the
+    journal into the Nomad `fifo` (controllable by [`disable_log_collection`]).
+    Benefits: all containers can log into the host journal, you can ship a
+    structured stream including metadata to your log aggregator. No log
+    rotation at Podman level. You can add additional tags to the journal.
+    Drawbacks: a bit more overhead, depends on Journal (will not work on WSL2).
+    You should configure some rotation policy for your Journal. Ensure you're
+    running Podman 3.1.0 or higher because of bugs in older versions.
+
+    ```hcl
+    config {
+      logging = {
+        driver = "journald"
+        options = [
+          {
+            "tag" = "redis"
+          }
+        ]
+      }
+    }
+    ```
+
+- `memory_reservation` - (Optional) Memory soft limit (units = `b` (bytes), `k`
+  (kilobytes), `m` (megabytes), or `g` (gigabytes)).
+
+  After setting memory reservation, when the system detects memory contention
+  or low memory, containers are forced to restrict their consumption to their
+  reservation. So you should always set the value below `--memory`, otherwise
+  the hard limit will take precedence. By default, memory reservation will be
+  the same as memory limit.
+
+  ```hcl
+  config {
+    memory_reservation = "100m"
+  }
+  ```
+
+- `memory_swap` - (Optional) A limit value equal to memory plus swap. The swap
+  limit should always be larger than the [memory value][memory-value]. Unit can
+  be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you
+  don't specify a unit, `b` is used. Set `LIMIT` to `-1` to enable unlimited
+  swap.
+
+  ```hcl
+  config {
+    memory_swap = "180m"
+  }
+  ```
+
+- `memory_swappiness` - Tune a container's memory swappiness behavior. Accepts
+  an integer between `0` and `100`.
+
+  ```hcl
+  config {
+    memory_swappiness = 60
+  }
+  ```
+
+- `network_mode` - (Optional) Set the [network mode][network-mode] for the
+  container. By default the task uses the network stack defined in the task
+  group [`network`][nomad_group_network] block. If the groups network behavior
+  is also undefined, it will fallback to `bridge` in rootful mode or
+  `slirp4netns` for rootless containers.
+
+  - `bridge` - (Default for rootful) Create a network stack on the default
+  Podman bridge.
+  - `container:id` - Reuse another container's network stack.
+  - `host` - Use the Podman host network stack. Note: the host mode gives the
+  container full access to local system services such as D-bus and is therefore
+  considered insecure.
+  - `none` - No networking.
+  - `slirp4netns` - (Default for rootless) Use `slirp4netns` to create a user
+  network stack. Podman currently does not support this option for rootful
+  containers ([issue][slirp-issue]).
+  - `task:name-of-other-task`: Join the network of another task in the same
+  allocation.
+
+  ```hcl
+  config {
+    network_mode = "bridge"
+  }
+  ```
+
+- `pids_limit` - (Optional) An integer value that specified the PID limit for
+  the container.
+
+  ```hcl
+  config {
+    pids_limit = 64
+  }
+  ```
+
+- `ports` - (Optional) Forward and expose ports. Refer to
+  [Docker driver configuration][nomad_driver_ports] for details.
+
+- `privileged` - (Optional) `true` or `false` (default). A privileged container
+  turns off the security features that isolate the container from the host.
+  Dropped Capabilities, limited devices, read-only mount points,
+  Apparmor/SELinux separation, and Seccomp filters are all disabled.
+
+- `readonly_rootfs` - (Optional) `true` or `false` (default). Mount the rootfs
+  as read-only.
+
+  ```hcl
+  config {
+    readonly_rootfs = true
+  }
+  ```
+
+- `security_opt` - (Optional) A list of security-related options that Podman sets
+  in the container.
+
+  ```hcl
+  config {
+    security_opt = [
+      "no-new-privileges"
+    ]
+
+  }
+  ```
+
+- `selinux_opts` - (Optional) A list of process labels that the container uses.
+
+  ```hcl
+  config {
+    selinux_opts = [
+      "type:my_container.process"
+    ]
+  }
+  ```
+
+- `shm_size` - (Optional) Set the size of `/dev/shm`. Refer to [`podman run
+  --shm-size](https://docs.podman.io/en/latest/markdown/podman-run.1.html#shm-size-number-unit)
+  for more details.
+
+- `socket` - (Optional) The name of the socket as defined in the socket block in
+  the client agent's plugin configuration. Defaults to the socket named "default".
+
+  ```hcl
+  config {
+    socket = "app1"
+  }
+  ```
+
+- `sysctl` - (Optional) A key-value map of `sysctl` configurations to set to
+  the containers on start.
+
+  ```hcl
+  config {
+    sysctl = {
+      "net.core.somaxconn" = "16384"
+    }
+  }
+  ```
+
+- `tmpfs` - (Optional) A list of `/container_path` strings for `tmpfs` mount
+  points. Refer to `podman run --tmpfs` options for details.
+
+  ```hcl
+  config {
+    tmpfs = [
+      "/var"
+    ]
+  }
+  ```
+
+- `tty` - (Optional) `true` or `false` (default). Allocate a pseudo-TTY for the
+  container.
+
+- `volumes` - (Optional) A list of `host_path:container_path:options` strings
+  to bind host paths to container paths. Named volumes are not supported.
+
+  ```hcl
+  config {
+    volumes = [
+      "/some/host/data:/container/data:ro,noexec"
+    ]
+  }
+  ```
+
+- `working_dir` - (Optional) The working directory for the container. Defaults
+  to the default set in the image.
+
+  ```hcl
+  config {
+    working_dir = "/data"
+  }
+  ```
+
+- `ulimit` - (Optional) A key-value map of ulimit configurations to set to the
+  containers to start.
+
+  ```hcl
+  config {
+    ulimit {
+      nproc  = "4242"
+      nofile = "2048:4096"
+    }
+  }
+  ```
+
+- `userns` - (Optional) Ser the user namespace mode for the container.
+
+  ```hcl
+  config {
+    userns = "keep-id:uid=200,gid=210"
+  }
+  ```
+
+Additionally, the Podman driver supports customization of the container's user
+through the task's [`user` option](/nomad/docs/job-specification/task#user).
+
+## Network Configuration
+
+Nomad [lifecycle hooks][nomad_lifecycle_hooks] combined with the drivers
+[`network_mode`] allows very flexible network namespace definitions. This
+feature does not build upon the native Podman pod structure but simply reuses
+the networking namespace of one container for other tasks in the same group.
+
+A typical example is a network server and a metric exporter or log shipping
+sidecar. The metric exporter needs access to a private monitoring port which
+should not be exposed to the network and thus is usually bound to `localhost`.
+
+The [`nomad-driver-podman` repository][homepage] includes three different
+examples jobs for such a setup. All of them will start a
+[nats](https://nats.io/) server and a
+[prometheus-nats-exporter](https://github.com/nats-io/prometheus-nats-exporter)
+using different approaches.
+
+You can use `curl` to prove that the job is working correctly and that you can
+get Prometheus metrics:
+
+```shell-session
+$ curl http://your-machine:7777/metrics
+```
+
+### 2 Task setup, server defines the network
+
+Reference [`examples/jobs/nats_simple_pod.nomad`].
+
+Here, the `server` task is started as main workload and the `exporter` runs as
+a `poststart` sidecar. Because of that, Nomad guarantees that the server is
+started first and thus the exporter can easily join the servers network
+namespace via `network_mode = "task:server"`.
+
+Note, that the `server` configuration file binds the `http_port` to
+`localhost`.
+
+Be aware that ports must be defined in the parent network namespace, here
+`server`.
+
+### 3 Task setup, a pause container defines the network
+
+Reference [`examples/jobs/nats_pod.nomad`].
+
+A slightly different setup is demonstrated in this job. It reassembles more
+closesly the idea of a `pod` by starting a `pause` task, named `pod` via a
+[`prestart`] sidecar hook.
+
+Next, the main workload, `server` is started and joins the network namespace by
+using the `network_mode = "task:pod"` block. Finally, Nomad starts the
+`poststart` sidecar `exporter` which also joins the network.
+
+Note that all ports must be defined on the `pod` level.
+
+### 2 Task setup, shared Nomad network namespace
+
+Reference [`examples/jobs/nats_group.nomad`].
+
+This example is very different. Both `server` and `exporter` join a network
+namespace which is created and managed by Nomad itself. Refer to Nomad's
+[`network`] block to get started with this generic approach.
+
+## Plugin Options
+
+The Podman plugin has options which may be customized in the agent's
+configuration file.
+
+- `gc` block:
+
+  - `container` - Defaults to `true`. This option can be used to disable Nomad
+    from removing a container when the task exits.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      gc {
+        container = false
+      }
+    }
+  }
+  ```
+
+- `recover_stopped` - (Deprecated) Defaults to `false`. Allows the driver to
+  start and reuse a previously stopped container after a Nomad client restart.
+  Consider a simple single node system and a complete reboot. All previously
+  managed containers will be reused instead of disposed and recreated.
+
+  !> This option may cause Nomad client to hang on startup. It now defaults to
+  being disabled and may be removed in a future release.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      recover_stopped = false
+    }
+  }
+  ```
+
+- `socket_path` `(string)` - Defaults to `unix://run/podman/io.podman` when
+  running as `root` or a cgroup V1 system, and
+  `unix://run/user/<USER_ID>/podman/io.podman` for rootless cgroup V2 systems.
+
+- `disable_log_collection` `(bool: false)` - Setting this to `true` will
+  disable Nomad logs collection of Podman tasks. If you don't rely on Nomad log
+  capabilities and exclusively use host based log aggregation, you may consider
+  this option to disable Nomad log collection overhead. Beware to you also lose
+  automatic log rotation.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      disable_log_collection = false
+    }
+  }
+  ```
+
+- `client_http_timeout` `(string: "60s")` - Default timeout used by
+  `http.Client` requests.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      client_http_timeout = "60s"
+    }
+  }
+  ```
+
+- `volumes` block:
+
+  - `enabled` - Defaults to `true`. Allows tasks to bind host paths (volumes)
+    inside their container.
+  - `selinuxlabel` - Allows the operator to set a SELinux label to the
+    allocation and task local bind-mounts to containers. If used with
+    `volumes.enabled` set to false, the labels will still be applied to the
+    standard binds in the container.
+
+  ```hcl
+  plugin "nomad-driver-podman" {
+    config {
+      volumes {
+        enabled      = true
+        selinuxlabel = "z"
+      }
+    }
+  }
+  ```
+
+If you need to configure authorization to an external registry, you can write a
+file containing the details in a location such as
+`/etc/nomad.d/registry/auth.json`:
+```json
+{
+  "auths": {
+    "yourregistry": {
+      "auth": "token"
+    }
+  }
+}
+```
+
+You can then instruct Nomad and the Podman driver to use this information by
+adding the following to the `/etc/nomad.d/nomad.env` file:
+```env
+REGISTRY_AUTH_FILE=/etc/nomad.d/registry/auth.json
+```
+
+[github]: https://github.com/hashicorp/nomad-driver-podman
+[`count`]: /nomad/docs/job-specification/group#count
+[`disable_log_collection`]: #disable_log_collection
+[docker-ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[`examples/jobs/nats_group.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_group.nomad
+[`examples/jobs/nats_simple_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_simple_pod.nomad
+[`examples/jobs/nats_pod.nomad`]: https://github.com/hashicorp/nomad-driver-podman/blob/main/examples/jobs/nats_pod.nomad
+[homepage]: https://github.com/hashicorp/nomad-driver-podman
+[memory-value]: /nomad/docs/job-specification/resources#memory
+[`network`]: /nomad/docs/job-specification/network
+[nomad-init]: /nomad/docs/commands/job/init
+[nomad_download]: /nomad/downloads
+[nomad_driver_ports]: /nomad/docs/drivers/docker#forwarding-and-exposing-ports
+[nomad_group_network]: /nomad/docs/job-specification/group#network
+[nomad_lifecycle_hooks]: /nomad/docs/job-specification/lifecycle
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
+[podman]: https://podman.io/
+[podman-cli]: https://podman.io/whatis.html
+[`prestart`]: /nomad/docs/job-specification/lifecycle#prestart
+[releases]: https://releases.hashicorp.com/nomad-driver-podman
+[rootless_tutorial]: https://github.com/containers/libpod/blob/master/docs/tutorials/rootless_tutorial.md
+[task]: /nomad/docs/job-specification/task#user
+[`network_mode`]: #network_mode
+[network-mode]: https://docs.podman.io/en/latest/markdown/podman-run.1.html#network-mode-net
+[slirp-issue]: https://github.com/containers/libpod/issues/6097
+[downloaded]: https://releases.hashicorp.com/nomad-driver-podman
+[short-names]: https://github.com/containers/image/blob/master/docs/containers-registries.conf.5.md#short-name-aliasing
+[`command`]: #command
+[`client_http_timeout`]: #client_http_timeout
+[rest_api]: https://www.redhat.com/sysadmin/podmans-new-rest-api
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/virt/index.mdx b/content/nomad/v1.9.x/content/plugins/drivers/virt/index.mdx
new file mode 100644
index 0000000000..e78e704ed8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/virt/index.mdx
@@ -0,0 +1,60 @@
+---
+layout: docs
+page_title: Virt task driver plugin
+description: >-
+  The Virt task driver leverages Linux capabilities and runs virtual machines using the libvirt API and hypervisors such as QEMU. Learn about Nomad client requirements, installation, capabilities, and Nomad client node attributes.
+---
+
+# Virt task driver plugin
+
+Name: `virt`
+
+The Virt task driver utilizes the [libvirt][] API to run and manage virtual
+machines using hypervisors such as [QEMU][]. The task driver supports a wide
+variety of Nomad features including [workload identity][], [task templates][],
+and [service discovery][].
+
+@include 'virt-beta-callout.mdx'
+
+## Driver Capabilities
+
+The Virt task driver implements these driver [capabilities][capabilities].
+
+| Feature              | Implementation |
+|----------------------|----------------|
+| `nomad alloc signal` | false          |
+| `nomad alloc exec`   | false          |
+| filesystem isolation | image          |
+| network isolation    | host           |
+| volume mounting      | false          |
+
+## Nomad Client Node Attributes
+
+The Virt task driver provides these node attributes that you can use as
+constraints when authoring jobs.
+
+```
+driver.virt                              = true
+driver.virt.active                       = 0
+driver.virt.emulator.version             = 8002002
+driver.virt.inactive                     = 0bytes
+driver.virt.libvirt.version              = 10000000
+driver.virt.network.default.bridge_name  = virbr0
+driver.virt.network.default.state        = active
+```
+
+## Reference
+
+- [Install and configure the Virt task driver][install].
+- [Configure a virt task in your job specification][task-config].
+
+
+[libvirt]: https://libvirt.org/
+[QEMU]: https://www.qemu.org/
+[workload identity]: https://developer.hashicorp.com/nomad/docs/concepts/workload-identity
+[task templates]: https://developer.hashicorp.com/nomad/docs/job-specification/template
+[service discovery]: https://developer.hashicorp.com/nomad/docs/networking/service-discovery
+[github]: https://github.com/hashicorp/nomad-driver-virt
+[capabilities]: /nomad/docs/concepts/plugins/task-drivers#task-driver-plugin-api
+[install]: /nomad/plugins/drivers/virt/install
+[task-config]: /nomad/plugins/drivers/virt/task-config
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/virt/install.mdx b/content/nomad/v1.9.x/content/plugins/drivers/virt/install.mdx
new file mode 100644
index 0000000000..a84dae333c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/virt/install.mdx
@@ -0,0 +1,148 @@
+---
+layout: docs
+page_title: Install the Virt task driver plugin
+description: >-
+  Install and configure the Virt task driver plugin on your Nomad clients. Review manual instructions and those for Ubuntu, Debian, CentOS, and RHEL. Add the Virt task driver plugin to Nomad.
+---
+
+# Install the Virt task driver plugin
+
+The Virt task driver plugin for Linux operating systems is not bundled with
+Nomad. You must install the driver into each Nomad client's [configured plugin
+directory][plugin_dir].
+
+@include 'virt-beta-callout.mdx'
+
+## Prerequisites
+
+Your Nomad client must meet these requirements:
+
+- Run as root.
+- Able to run hardware-accelerated KVM virtual machines. Run the [kvm-ok][]
+  command to verify your client capabilities.
+
+The Virt driver requires the following packages:
+
+- bridge-utils
+- cloudinit
+- dnsmasq
+- iptables
+- [libvirt daemon][]
+- [QEMU][]
+
+## Install the Virt task driver plugin
+
+<Tabs>
+<Tab heading="Manual installation" group="manual">
+
+Download a [precompiled binary][releases] and verify the binary using the
+available SHA-256 sums. Unzip the package. Make sure that the
+`nomad-driver-virt` binary is on your
+[plugin_dir] path, specified by the
+client's config file, before continuing with the other guides.
+
+</Tab>
+<Tab heading="Ubuntu/Debian" group="manual">
+
+Install the required packages.
+
+```shell-session
+$ sudo apt-get update && \
+  sudo apt-get install -y \
+  wget \
+  gpg \
+  coreutils \
+  bridge-utils \
+  cloud-init \
+  dnsmasq \
+  iptables \
+  libvirt-daemon-system \
+  qemu-system \
+  qemu-system-x86 \
+  qemu-utils
+```
+
+Add the HashiCorp [GPG key][gpg-key].
+
+```shell-session
+$ wget -O- https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
+```
+
+Add the official HashiCorp Linux test repository.
+
+```shell-session
+$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) test" | sudo tee /etc/apt/sources.list.d/hashicorp.list
+```
+
+Update and install.
+
+```shell-session
+$ sudo apt-get update && sudo apt-get install nomad-driver-virt
+```
+
+</Tab>
+<Tab heading="CentOS/RHEL" group="linux">
+
+Install `yum-config-manager` to manage your repositories.
+
+```shell-session
+$ sudo yum install -y yum-utils
+```
+
+Use `yum-config-manager` to add the official HashiCorp Linux repository.
+
+```shell-session
+$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
+```
+
+Edit the repo file at `/etc/yum.repos.d/hashicorp.repo` and set `enabled=1` for `[hashicorp-test]`.
+
+Install.
+
+```shell-session
+$ sudo yum -y install nomad-driver-virt
+```
+
+</Tab>
+</Tabs>
+
+## Add the Virt task driver plugin to Nomad
+
+This example shows the default plugin configuration.
+
+```hcl
+plugin "nomad-driver-driver" {
+  config {
+    data_dir     = "/var/lib/virt"
+    image_paths  = ["/var/lib/virt", "${ALLOC_DIR}"]
+
+    emulator {
+      uri      = "qemu:///system"
+      user     = ""
+      password = ""
+    }
+  }
+}
+```
+
+- `data_dir` - (default: `"/var/lib/virt"`) - the directory for storing VM configuration files and
+  intermediate files.
+
+- `image_paths` - (default: `["/var/lib/virt", "${ALLOC_DIR}"]`) - an allow-list of paths the driver
+  is allowed to load an image from.
+
+- `emulator` - (block)
+  - `uri` - (default: `"qemu:///system"`) - The `uri` specifies which hypervisor to connect to.
+  - `user` - (default: `""`) - the username to use for authentication.
+  - `password` - (default: `""`) - the password to use for authentication.
+
+## Next steps
+
+[Learn how to use the Virt task driver in your Nomad job specification][task-config].
+
+[releases]: https://releases.hashicorp.com/nomad-driver-virt
+[kvm-ok]: https://manpages.ubuntu.com/manpages/bionic/man1/kvm-ok.1.html
+[libvirt daemon]: https://libvirt.org/daemons.html
+[QEMU]: https://www.qemu.org/
+[task-config]: /nomad/plugins/drivers/virt/task-config
+[plugin_dir]: /nomad/docs/configuration#plugin_dir
diff --git a/content/nomad/v1.9.x/content/plugins/drivers/virt/task-config.mdx b/content/nomad/v1.9.x/content/plugins/drivers/virt/task-config.mdx
new file mode 100644
index 0000000000..0de11f3ebc
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/drivers/virt/task-config.mdx
@@ -0,0 +1,158 @@
+---
+layout: docs
+page_title: Configure a Virt job task
+description: Learn how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+---
+
+# Configure a Virt job task
+
+This page provides reference information on how to use the Virt task driver in your Nomad job specification. Configure a base virtual machine (VM) image, network interface, and parameters for bootstrapping the VM instance.
+
+@include 'virt-beta-callout.mdx'
+
+## Parameters
+
+Task configuration for a virt task includes setting an `image` to provide the base VM image as
+well as other parameters required for bootstrapping a VM instance.
+
+- `image` - (string: required) - Path to an `.img` cloud image to base the VM disk on. The image should
+  be located in an allowed path. The cloud image needs to include cloud-init, otherwise certain
+  task features are not available. You may also downloaded via the [artifact block][].
+
+- `use_thin_copy` - (bool: `false`) - Make a thin copy of the image using QEMU, and use it as the
+  backing cloud image for the VM.
+
+- `hostname` - (string: `"nomad-<task-name>"`) - The hostname to assign to the VM. As this value is
+  used as a network host name, it must be a valid DNS label according to RFC 1123. Nomad generates the default
+  value using the Nomad task name.
+
+- `cmds` - (list(string): optional) - List of commands to execute on the VM once it is running.
+  These commands can provide you with a quick way to start a process on the newly created
+  VM. When used in conjunction with the template, this command list can be a powerful start up tool.
+
+- `default_user_password` - (string: `""`) - Initial password for the default user
+  on the newly created VM. When set, the user must update the password on first connect.
+
+- `default_user_authorized_ssh_key` - (string: `""`) - SSH public key  added to the SSH
+  configuration for the default user of the cloud image distribution.
+
+- `user_data ` - (string: `""`) - Path to a cloud-init compliant user data file used as the user-data for the cloud-init configuration.
+
+- `primary_disk_size` - (int: required) - Disk space to assign to the VM. Must fit the VM's OS.
+
+Example:
+```hcl
+config {
+  image                           = "local/focal-server-cloudimg-amd64.img"
+  use_thing_copy                  = false
+  hostname                        = ""
+  cmds                            = ["python -m http.server 8000"]
+  #default_user_password          = "CHANGE-ME"
+  default_user_authorized_ssh_key = ""
+  user_data                       = ""
+  primary_disk_size               = 10000
+}
+```
+
+### os
+
+The VM architecture and machine can be different from the client host. When this is the case, you must set the
+`os` block. By default, this information matches the client host where the driver
+plugin is running.
+
+- `arch` - (string: `""`) - The VM architecture.
+
+- `machine` - (string: `""`) - The machine type.
+
+Example:
+```hcl
+config {
+  os {
+    arch    = "x86_64"
+    machine = "pc-i440fx-2.9"
+  }
+}
+```
+
+### network_interface
+
+You need to attach tasks to a libvirt network in order to access the internet and route
+from the local network. The `network_interface` block enables this as a list of network interfaces
+that the driver should attach to the VM. This feature only supports a single entry.
+
+- `bridge` - (block) - Attach the VM to a bridge network. `virbr0`, the default libvirt
+  network, is a bridge network.
+
+  - `name` - The name of the bridge interface to use. This relates to the output from commands
+  such as `virsh net-info`.
+
+  - `ports` - A list of port labels to expose on the host via mapping to the network
+  interface. These labels must exist within the job specification [network block][].
+
+Example:
+```hcl
+config {
+  network_interface {
+    bridge {
+      name  = "virbr0"
+      ports = ["ssh", "http"]
+    }
+  }
+}
+```
+
+## Example configuration
+
+The following job specification displays use of all the configuration options, as well as other
+blocks that are useful when deploying tasks via the virt driver. You need to modify parameters, such as the
+`default_user_authorized_ssh_key`, before use depending on your
+requirements and Nomad setup.
+
+```hcl
+job "virt-example" {
+
+  group "virt-group" {
+
+    network {
+      mode     = "host"
+      port "ssh" {
+        to = 22
+      }
+    }
+
+    task "virt-task" {
+
+      driver = "nomad-driver-virt"
+
+      artifact {
+        source      = "http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img"
+        destination = "local/focal-server-cloudimg-amd64.img"
+        mode        = "file"
+      }
+
+      config {
+        image                           = "local/focal-server-cloudimg-amd64.img"
+        primary_disk_size               = 26000
+        #default_user_password          = "CHANGE-ME"
+        default_user_authorized_ssh_key = "ssh-ed25519 AAAAC3NzaC1lZDI..."
+
+        network_interface {
+          bridge {
+            name  = "virbr0"
+            ports = ["ssh"]
+          }
+        }
+      }
+
+      resources {
+        cores  = 2
+        memory = 4096
+      }
+    }
+  }
+}
+
+```
+
+[artifact block]: https://developer.hashicorp.com/nomad/docs/job-specification/artifact
+[network block]: https://developer.hashicorp.com/nomad/docs/job-specification/network
diff --git a/content/nomad/v1.9.x/content/plugins/index.mdx b/content/nomad/v1.9.x/content/plugins/index.mdx
new file mode 100644
index 0000000000..01c025706c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/plugins/index.mdx
@@ -0,0 +1,17 @@
+---
+layout: docs
+page_title: Nomad plugins
+description: Plugins extend Nomad's functionality. Device plugins detect hardware such as USBs and NVIDIA GPU. Task driver plugins provide specific resource isolation when executing workloads. Review configuration, installation, usage, and reference information for the NVIDIA GPU and USB device plugins, and the Exec2, Podman, and Virt task drivers.
+---
+
+# Nomad plugins
+
+Nomad implements a plugin framework which allows users to extend the
+functionality of some components within Nomad. The design of the plugin system
+is inspired by the lessons learned from plugin systems implemented in other
+HashiCorp products such as Terraform and Vault.
+
+The following components are currently pluggable within Nomad:
+
+- [Task Drivers](/nomad/plugins/drivers)
+- [Devices](/nomad/plugins/devices)
diff --git a/content/nomad/v1.9.x/content/security.mdx b/content/nomad/v1.9.x/content/security.mdx
new file mode 100644
index 0000000000..b53a182355
--- /dev/null
+++ b/content/nomad/v1.9.x/content/security.mdx
@@ -0,0 +1,16 @@
+---
+layout: index
+page_title: Security
+description: >-
+  Nomad takes security very seriously. Please responsibly disclose any security vulnerabilities found and we'll handle it quickly.
+---
+
+# Nomad Security
+
+We understand that many users place a high level of trust in HashiCorp and the tools we build. We apply best practices and focus on security to make sure we can maintain the trust of the community.
+
+We deeply appreciate any effort to disclose vulnerabilities responsibly.
+
+If you would like to report a vulnerability, please see the [HashiCorp security page](https://www.hashicorp.com/security), which has the proper email to communicate with as well as our PGP key. Please **do not create a GitHub issue for security concerns**.
+
+If you aren't reporting a security sensitive vulnerability, please open an issue on the standard [GitHub](https://github.com/hashicorp/nomad) repository.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent.mdx
new file mode 100644
index 0000000000..712b04627e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent.mdx
@@ -0,0 +1,129 @@
+---
+layout: docs
+page_title: Agent
+description: The Nomad Autoscaler is a long lived process which coordinates scaling activates.
+---
+
+# Nomad Autoscaler Agent
+
+The Nomad Autoscaler agent has a variety of parameters that can be specified
+via configuration files or command-line flags. Configuration files are written
+in [HCL][hcl_v2]. The Nomad Autoscaler can read and combine parameters from
+multiple configuration files or directories to configure the agent.
+
+## Nomad Namespaces
+
+The Nomad Autoscaler currently has limited support for
+[Nomad Namespaces][nomad_namespaces]. The `nomad` configuration below supports
+specifying a namespace; if configured with a namespace, the Autoscaler will
+retrieve scaling policies and perform autoscaling only for jobs in that
+namespace. If the special wildcard namespace value `*` is used, the Autoscaler
+agent will retrieve scaling policies from all namespaces. A future version will
+include support for multiple namespaces.
+
+## Nomad ACLs
+
+The Nomad Autoscaler can be configured to interact with an ACL-enabled Nomad
+cluster. Nomad includes the `scale` ACL policy disposition specifically for
+supporting the operations of the Nomad Autoscaler. Therefore, the
+following policy is sufficient for creating an ACL token that can be used by
+the autoscaler for fetching scaling policies and scaling jobs:
+
+```hcl
+namespace "default" {
+  policy = "scale"
+}
+```
+
+When utilizing the High-Availability feature added in v0.4.0, the ACL policy
+needs to include capabilities that allow the Nomad Autoscaler to obtain and release Nomad variable
+locks. The namespace identifier should match the configured
+[`high_availability.lock_namespace`][autoscaler_ha_lock_namespace] parameter,
+and the path should match the [`high_availability.lock_path`][autoscaler_ha_lock_path]
+parameter.
+
+```hcl
+namespace "default" {
+  variables {
+    path "nomad-autoscaler/lock" {
+      capabilities = ["write"]
+    }
+  }
+}
+```
+
+If running Nomad Autoscaler Enterprise, the following ACL policy addition is
+needed to ensure it can read the Nomad Enterprise license.
+
+```hcl
+operator {
+  policy = "read"
+}
+```
+
+Other APM and target plugins may require additional ACLs; see the plugin documentation for more information.
+
+## Load Order and Merging
+
+The Nomad Autoscaler agent supports multiple configuration files, which can be
+provided using the [`-config`][autoscaler_cli_config] CLI flag. The flag can
+accept either a file or folder. In the case of a folder, any `.hcl` and `.json`
+files in the folder will be loaded and merged in lexicographical order. Directories
+are not loaded recursively.
+
+For example:
+
+```shell-session
+$ nomad-autoscaler agent -config=autoscaler.hcl -config=/etc/nomad-autoscaler -config=extra.json
+```
+
+This will load configuration from `autoscaler.hcl`, from `.hcl` and `.json` files
+under `/etc/nomad-autoscaler`, and finally from `extra.json`. As each file is
+processed, its contents are merged into the existing configuration. When merging,
+any non-empty values from the latest config file will append or replace
+parameters in the current configuration. An empty value means `""` for strings,
+`0` for integer or float values, and `false` for booleans.
+
+## SIGHUP Reload
+
+The Nomad Autoscaler agent supports handling the `SIGHUP` signal for reloading without the need for
+restarting the agent. When sending a `SIGHUP` signal to the agent process, the agent will perform the
+following actions.
+
+- reload the contents of the scaling policy directory as defined by the [`-policy-dir`][autoscaler_cli_policy_dir]
+  parameter.
+
+- reconfigure the Nomad clients used to fetch policies and execute scaling
+  actions with the values defined in the [`nomad`][autoscaler_agent_nomad]
+  block.
+
+- stop plugins that are no longer present in the configuration file.
+
+- start plugins that were not previously present in the configuration file.
+
+- reconfigure the remaining plugins with the configuration defined in their
+  `config` parameter.
+
+## General Parameters
+
+- `enable_debug` `(bool: false)` - Specifies if the debugging HTTP endpoints
+  should be enabled. These endpoints can be used with profiling tools to dump
+  diagnostic information about the Nomad Autoscaler's internals.
+
+- `log_level` `(string: "INFO")` - Specify the verbosity level of Nomad
+  Autoscaler's logs. Valid values include DEBUG, INFO, and WARN, in decreasing
+  order of verbosity.
+
+- `log_json` `(bool: false)` - Output logs in a JSON format.
+
+- `plugin_dir` `(string: "./plugins")` - The plugin directory is used to
+  discover Nomad Autoscaler plugins.
+
+[hcl_v2]: https://github.com/hashicorp/hcl/tree/hcl2
+[nomad_namespaces]: /nomad/tutorials/manage-clusters/namespaces
+[nomad_acls]: /nomad/tutorials/access-control
+[autoscaler_agent_nomad]: /nomad/tools/autoscaling/agent/nomad
+[autoscaler_cli_config]: /nomad/tools/autoscaling/cli#config
+[autoscaler_cli_policy_dir]: /nomad/tools/autoscaling/cli#policy-dir
+[autoscaler_ha_lock_namespace]: /nomad/tools/autoscaling/agent/high_availability#lock_namespace
+[autoscaler_ha_lock_path]: /nomad/tools/autoscaling/agent/high_availability#lock_path
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/apm.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/apm.mdx
new file mode 100644
index 0000000000..9de3ec396a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/apm.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: apm Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "apm" block is used to configure application performance metric (APM) plugins.
+---
+
+# `apm` Block
+
+<Placement groups={['apm']} />
+
+The `apm` block is used to configure application performance metric (APM) plugins.
+
+```hcl
+apm "example-apm-plugin" {
+  driver = "example-apm-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    address = "http://127.0.0.1:9090"
+  }
+}
+```
+
+## `apm` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
new file mode 100644
index 0000000000..3acc904e96
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/dynamic_application_sizing.mdx
@@ -0,0 +1,63 @@
+---
+layout: docs
+page_title: dynamic_application_sizing Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "dynamic_application_sizing" block configures the Nomad Autoscaler agent
+  options for Dynamic Application Sizing.
+---
+
+# `dynamic_application_sizing` Block
+
+<Placement groups={['dynamic_application_sizing']} />
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `dynamic_application_sizing` blocks configures the Nomad Autoscaler agent
+options for Dynamic Application Sizing. Learn more about the Dynamic
+Application Sizing functionality in the
+[Dynamic Application Sizing Concepts guide][das_learn_guide]
+
+```hcl
+dynamic_application_sizing {
+  evaluate_after            = "1h"
+  metrics_preload_threshold = "12h"
+}
+```
+
+## `dynamic_application_sizing` Parameters
+
+- `cpu_metric` `(string: "nomad_client_allocs_cpu_total_ticks")` - The APM
+  metric to use for querying the historical CPU usage of a task.
+
+- `evaluate_after` `(string: "24h")` - Specifies how much historical data must
+  be available for a task before the Autoscaler starts generating
+  recommendations.
+
+- `group_label` `(string: "task_group")` - The label used by the APM to store
+  the name of a task group. It is used by the Autoscaler when querying the APM
+  for metrics.
+
+- `job_label` `(string: "exported_job")` - The label used by the APM to store
+  the ID of a job. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+- `memory_metric` `(string: "nomad_client_allocs_memory_usage")` - The APM
+  metric to use for querying the historical memory usage of a task.
+
+- `metrics_preload_threshold` `(string: "168h")` - Specifies how much
+  historical data the Autoscaler will preload from the APM when it starts.
+
+- `namespace_label` `(string: "namespace")` - The label used by the APM to
+  store the namespace of a job. It is used by the Autoscaler when querying the
+  APM for metrics.
+
+- `task_label` `(string: "task")` - The label used by the APM to store the
+  name of a task. It is used by the Autoscaler when querying the APM for
+  metrics.
+
+[das_learn_guide]: /nomad/tutorials/autoscaler/dynamic-application-sizing-concepts
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/high_availability.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/high_availability.mdx
new file mode 100644
index 0000000000..0d8df1ac85
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/high_availability.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: high_availability Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "high_availability" block is used to configure the Nomad Autoscaler agent
+  in high availability (HA) mode. In this mode, multiple agents participate in
+  leadership election, with only the leader conducting autoscaling calculations
+  and actions.
+---
+
+# `high_availability` Block
+
+<Placement groups={['high_availability']} />
+
+The `high_availability` block is used to configure the Nomad Autoscaler agent
+in high availability (HA) mode. In this mode, multiple agents participate in
+leadership election, with only the leader conducting autoscaling calculations
+and actions.
+
+```hcl
+high_availability {
+  enabled        = true
+  lock_namespace = "prod"
+  lock_path      = "custom/lock/path"
+  lock_ttl       = "30s"
+  lock_delay     = "15s"
+}
+```
+
+## `high_availability` Parameters
+
+- `enabled` `(bool: false)` - Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired.
+
+- `lock_namespace` `(string: "default")` - Defines the namespace of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process.
+
+- `lock_path` `(string: "nomad-autoscaler/lock")` - Defines the path of the Nomad
+  variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad Autoscaler
+  agents expected to take part in the same leadership election process.
+
+- `lock_ttl` `(string: "60s")` - Defines the lease period or TTL of the lock used
+  to sync the leader when running in high availability mode. If the Nomad Autoscaler
+  agent does not renew the lock within this period, the lock is considered lost.
+
+- `lock_delay` `(string: "30s")` - Defines the period that the lock will be blocked
+  after the TTL expired without being renewed. This helps prevent split brain
+  situations.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/http.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/http.mdx
new file mode 100644
index 0000000000..db99b88f01
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/http.mdx
@@ -0,0 +1,26 @@
+---
+layout: docs
+page_title: http Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "http" block configures the Nomad Autoscaler's HTTP endpoint.
+---
+
+# `http` Block
+
+<Placement groups={['http']} />
+
+The `http` block configures the Nomad Autoscaler's HTTP endpoint.
+
+```hcl
+http {
+  bind_address = "10.0.0.10"
+  bind_port    = 9999
+}
+```
+
+## `http` Parameters
+
+- `bind_address` `(string: "127.0.0.1")` - The HTTP address that the server will
+  bind to.
+
+- `bind_port` `(int: 8080)` - The port that the server will bind to.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/nomad.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/nomad.mdx
new file mode 100644
index 0000000000..124dba0a93
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/nomad.mdx
@@ -0,0 +1,56 @@
+---
+layout: docs
+page_title: nomad Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "nomad" block configures the Nomad Autoscaler's Nomad client.
+---
+
+# `nomad` Block
+
+<Placement groups={['nomad']} />
+
+The `nomad` block configures the Nomad Autoscaler's Nomad client.
+
+```hcl
+nomad {
+  address = "http://my-nomad.systems:4646"
+  region  = "esp-vlc-1"
+}
+```
+
+## `nomad` Parameters
+
+- `address` `(string: "http://127.0.0.1:4646")` - The address of the Nomad server
+  in the form of `protocol://addr:port`.
+
+- `region` `(string: "global")` - The region of the Nomad servers to connect with.
+
+- `namespace` `(string: "")` - The target namespace for queries and actions bound
+  to a namespace. If set to `*` all namespaces are queried.
+
+- `token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `http_auth` `(string: "")` - The authentication information to use when connecting
+  to a Nomad API which is using HTTP authentication.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `ca_path` `(string: "")` - Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate.
+
+- `client_cert` `(string: "")` - Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server.
+
+- `client_key` `(string: "")` - Path to an unencrypted PEM encoded private key
+  matching the client certificate.
+
+- `tls_server_name` `(string: "")` - The server name to use as the SNI host when
+  connecting via TLS.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
+  discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy.mdx
new file mode 100644
index 0000000000..a1e7d842fb
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: policy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy" block configures the Nomad Autoscaler's policy handling.
+---
+
+# `policy` Block
+
+<Placement groups={['policy']} />
+
+The `policy` block configures the Nomad Autoscaler's policy handling.
+
+```hcl
+policy {
+  dir              = "/opt/nomad-autoscaler/policies"
+  default_cooldown = "2m"
+
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+## `policy` Parameters
+
+- `default_cooldown` `(string: "5m")` - The default cooldown that will be applied
+  to all scaling policies which do not specify a cooldown period.
+
+- `default_evaluation_interval` `(string: "10s")` - The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval.
+
+- `dir` `(string: "")` - The path to a directory used to load scaling policies.
+
+- `source` <code>([Source](#source-parameters))</code> - Configures policy
+  sources. The `nomad` source is enabled by default and the `file` source is
+  automatically enabled if `dir` is set.
+
+### `source` Parameters
+
+The `source` block is used to configure scaling policies sources. Supported
+sources are `file` and `nomad`.
+
+```hcl
+policy {
+  source "nomad" {
+    enabled = false
+  }
+}
+```
+
+- `enabled` `(bool: true)` - Defines if the scaling policy source should be
+  enabled or disabled.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy_eval.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy_eval.mdx
new file mode 100644
index 0000000000..7b416a6bd0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/policy_eval.mdx
@@ -0,0 +1,39 @@
+---
+layout: docs
+page_title: policy_eval Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "policy_eval" block holds the configuration related to the policy evaluation
+  process.
+---
+
+# `policy_eval` Block
+
+<Placement groups={['policy_eval']} />
+
+The `policy_eval` block holds the configuration related to the policy evaluation
+process.
+
+```hcl
+policy_eval {
+  ack_timeout    = "10m"
+  delivery_limit = 4
+
+  workers = {
+    cluster    = 2
+    horizontal = 2
+  }
+}
+```
+
+## `policy_eval` Parameters
+
+- `ack_timeout` `(string: "5m")` - The time limit that an eval must be ACK'd
+  before being considered NACK'd.
+
+- `delivery_limit` `(int: 1)` - The maximum number of times a policy evaluation
+  can be dequeued from the broker.
+
+- `workers` `(map<string|int>: [cluster:10,horizontal:10])` - The number of workers
+  to initialize for each queue. Nomad Autoscaler supports `cluster` and `horizontal`
+  map keys. Nomad Autoscaler Enterprise supports additional `vertical_mem` and
+  `vertical_cpu` entries.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/strategy.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/strategy.mdx
new file mode 100644
index 0000000000..4911778e3c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/strategy.mdx
@@ -0,0 +1,37 @@
+---
+layout: docs
+page_title: strategy Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "strategy" block is used to configure scaling strategy plugins.
+---
+
+# `strategy` Block
+
+<Placement groups={['strategy']} />
+
+The `strategy` block is used to configure scaling strategy plugins.
+
+```hcl
+strategy "example-strategy-plugin" {
+  driver = "example-strategy-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    algorithm = "complex"
+  }
+}
+```
+
+## `strategy` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/target.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/target.mdx
new file mode 100644
index 0000000000..8ae5f56d5b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/target.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: target Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "target" block is used to configure scaling target plugins.
+---
+
+# `target` Block
+
+<Placement groups={['target']} />
+
+The `target` block is used to configure scaling target plugins.
+
+```hcl
+target "example-target-plugin" {
+  driver = "example-target-plugin"
+  args   = ["-my-flag"]
+
+  config = {
+    region = "esp-vlc-1"
+  }
+}
+```
+
+## `target` Parameters
+
+- `args` `(array<string>: [])` - Specifies a set of arguments to pass to the
+  plugin binary when it is executed.
+
+- `driver` `(string: "")` - The plugin's executable name relative to the
+  [`plugin_dir`][plugin_dir]. If the plugin has a suffix, such as .exe, this
+  should be omitted.
+
+- `config` `(map<string><string>: nil)` - Specifies configuration values for
+  the plugin either as HCL or JSON. The accepted values are plugin specific.
+  Please refer to the individual plugin's documentation.
+
+[plugin_dir]: /nomad/tools/autoscaling/agent#plugin_dir
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/agent/telemetry.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/agent/telemetry.mdx
new file mode 100644
index 0000000000..9674e5c9f8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/agent/telemetry.mdx
@@ -0,0 +1,160 @@
+---
+layout: docs
+page_title: telemetry Block - Nomad Autoscaler Agent Configuration
+description: >-
+  The "telemetry" block configures the Nomad Autoscaler's publication of metrics
+  and telemetry to third-party systems.
+---
+
+# `telemetry` Block
+
+<Placement groups={['telemetry']} />
+
+The `telemetry` block configures the Nomad Autoscaler's publication of metrics
+and telemetry to third-party systems.
+
+```hcl
+telemetry {
+  disable_hostname = true
+}
+```
+
+## `telemetry` Parameters
+
+Due to the number of provider-specific parameters to the `telemetry` block, parameters
+in this section are grouped by the telemetry provider.
+
+### Common Parameters
+
+The following options are available on all telemetry configurations.
+
+- `disable_hostname` `(bool: false)` - Specifies if gauge values should be
+  prefixed with the local hostname.
+
+- `enable_hostname_label` `(bool: false)` - Enable adding hostname to metric
+  labels.
+
+- `collection_interval` `(duration: "1s")` - Specifies the time interval at which
+  the Nomad agent collects telemetry data.
+
+### `statsite` Parameters
+
+These `telemetry` parameters apply to [Statsite][statsite].
+
+- `statsite_address` `(string: "")` - Specifies the address of a statsite server
+  to forward metrics data to.
+
+```hcl
+telemetry {
+  statsite_address = "statsite.company.local:8125"
+}
+```
+
+### `statsd` Parameters
+
+These `telemetry` parameters apply to [StatsD][statsd].
+
+- `statsd_address` `(string: "")` - Specifies the address of a statsd server to
+  forward metrics to.
+
+```hcl
+telemetry {
+  statsd_address = "statsd.company.local:8125"
+}
+```
+
+### `datadog` Parameters
+
+These `telemetry` parameters apply to [DataDog statsd][datadog_statsd].
+
+- `dogstatsd_address` `(string: "")` - Specifies the address of a DataDog statsd
+  server to forward metrics to.
+
+- `dogstatsd_tags` `(list: [])` - Specifies a list of global tags that will be
+  added to all telemetry packets sent to DogStatsD. It is a list of strings,
+  where each string looks like `my_tag_name:my_tag_value`.
+
+```hcl
+telemetry {
+  dogstatsd_address = "dogstatsd.company.local:8125"
+  dogstatsd_tags    = ["my_tag_name:my_tag_value"]
+}
+```
+
+### `prometheus` Parameters
+
+These `telemetry` parameters apply to [Prometheus][prometheus].
+
+- `prometheus_metrics` `(bool: false)` - Specifies whether the agent should
+  make Prometheus formatted metrics available at `/v1/metrics?format=prometheus`.
+
+- `prometheus_retention_time` `(string: "24h")` - Specifies the amount of time that Prometheus
+  metrics are retained in memory.
+
+### `circonus` Parameters
+
+These `telemetry` parameters apply to [Circonus][circonus].
+
+- `circonus_api_token` `(string: "")` - Specifies a valid Circonus API Token
+  used to create/manage check. If provided, metric management is enabled.
+
+- `circonus_api_app` `(string: "nomad-autoscaler")` - Specifies a valid app name
+  associated with the API token.
+
+- `circonus_api_url` `(string: "https://api.circonus.com/v2")` - Specifies the
+  base URL to use for contacting the Circonus API.
+
+- `circonus_submission_interval` `(string: "10s")` - Specifies the interval at
+  which metrics are submitted to Circonus.
+
+- `circonus_submission_url` `(string: "")` - Specifies the
+  `check.config.submission_url` field, of a Check API object, from a previously
+  created HTTPTRAP check.
+
+- `circonus_check_id` `(string: "")` - Specifies the Check ID (**not check
+  bundle**) from a previously created HTTPTrap check. The numeric portion of the
+  `check._cid` field in the Check API object.
+
+- `circonus_check_force_metric_activation` `(bool: false)` - Specifies if force
+  activation of metrics which already exist and are not currently active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered. If the metric already exists in the check, it will
+  not be activated. This setting overrides that behavior.
+
+- `circonus_check_instance_id` `(string: "<hostname>:<application>")` - Serves
+  to uniquely identify the metrics coming from this _instance_. It can be used
+  to maintain metric continuity with transient or ephemeral instances as they
+  move around within an infrastructure. By default, this is set to
+  "hostname:application name" (e.g. `host123:nomad-autoscaler`).
+
+- `circonus_check_search_tag` `(string: <service>:<application>)` - Specifies a
+  special tag which, when coupled with the instance id, helps to narrow down the
+  search results when neither a Submission URL or Check ID is provided. By
+  default, this is set to "service:app" (e.g. `service:nomad-autoscaler`).
+
+- `circonus_check_display_name` `(string: "")` - Specifies a name to give a
+  check when it is created. This name is displayed in the Circonus UI Checks
+  list.
+
+- `circonus_check_tags` `(string: "")` - Comma separated list of additional
+  tags to add to a check when it is created.
+
+- `circonus_broker_id` `(string: "")` - Specifies the ID of a specific Circonus
+  Broker to use when creating a new check. The numeric portion of `broker._cid`
+  field in a Broker API object. If metric management is enabled and neither a
+  Submission URL nor Check ID is provided, an attempt will be made to search for
+  an existing check using Instance ID and Search Tag. If one is not found, a new
+  HTTPTrap check will be created. By default, this is a random
+  Enterprise Broker is selected, or, the default Circonus Public Broker.
+
+- `circonus_broker_select_tag` `(string: "")` - Specifies a special tag which
+  will be used to select a Circonus Broker when a Broker ID is not provided. The
+  best use of this is to as a hint for which broker should be used based on
+  _where_ this particular instance is running (e.g., a specific geographic location or
+  datacenter, dc:sfo).
+
+[statsite]: https://github.com/armon/statsite
+[statsd]: https://github.com/etsy/statsd
+[datadog_statsd]: https://github.com/DataDog/datadog-agent
+[prometheus]: https://prometheus.io
+[circonus]: http://circonus.com/
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/api.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/api.mdx
new file mode 100644
index 0000000000..e47808cc71
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/api.mdx
@@ -0,0 +1,163 @@
+---
+layout: docs
+page_title: HTTP API
+description: Learn about the Nomad Autoscaler HTTP API.
+---
+
+# Nomad Autoscaler HTTP API
+
+The Nomad Autoscaler exposes a small, simple API to be used for health checking
+the agent and obtaining metric data.
+
+## Agent Runtime Profiles
+
+This endpoint can be used to retrieve runtime profile information for the Nomad
+Autoscaler. They are only available when [`enable_debug`][agent_enable_debug]
+is set to `true`. Refer to [Go's documentation][go_debug] for a list of
+available profiles.
+
+| Method | Path                           | Produces                   |
+| ------ | ------------------------------ | -------------------------- |
+| `GET`  | `/debug/pprof`                 | `text/html`                |
+| `GET`  | `/debug/pprof/cmdline`         | `text/plain`               |
+| `GET`  | `/debug/pprof/symbol`          | `text/plain`               |
+| `GET`  | `/debug/pprof/profile`         | `application/octet-stream` |
+| `GET`  | `/debug/pprof/trace`           | `application/octet-stream` |
+| `GET`  | `/debug/pprof/<pprof profile>` | `application/octet-stream` |
+
+### Parameters
+
+- `seconds` `(int: 3)` - Specifies the amount of time to run a profile or trace
+  request for.
+
+- `debug` `(int: 0)` - Specifies if a given pprof profile should be returned as
+  human readable plain text instead of the pprof binary format. Defaults to 0,
+  setting to 1 enables human readable plain text.
+
+### Sample Request
+
+```shell-session
+$ curl -O "http://localhost:8080/debug/pprof/goroutine"
+$ go tool pprof goroutine
+
+$ curl -O "http://localhost:8080/debug/pprof/profile?seconds=3"
+$ go tool pprof profile
+
+$ curl -O "http://localhost:8080/debug/pprof/trace?&seconds=5"
+$ go tool trace trace
+```
+
+## Health API
+
+This endpoint can be used to query the Nomad Autoscaler agent aliveness. If the
+agent is alive, the request will return a 200 OK, otherwise it will return a
+503 ServiceUnavailable.
+
+| Method | Path         | Produces           |
+| ------ | ------------ | ------------------ |
+| `GET`  | `/v1/health` | `application/json` |
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/health
+```
+
+## Metrics API
+
+The `/metrics` endpoint returns metrics for the current Nomad Autoscaler process.
+
+| Method | Path          | Produces           |
+| ------ | ------------- | ------------------ |
+| `GET`  | `/v1/metrics` | `application/json` |
+
+### Parameters
+
+- `format` `(string: "")` - Specifies the metrics format to be other than the
+  JSON default. Currently, only `prometheus` is supported as an alternative
+  format. This is specified as a query string parameter.
+
+### Sample Request
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics
+```
+
+```shell-session
+$ curl https://localhost:8080/v1/metrics?format=prometheus
+```
+
+### Sample Response
+
+```json
+{
+  "Counters": [
+    {
+      "Count": 1,
+      "Labels": {
+        "policy_source": "nomad"
+      },
+      "Max": 1,
+      "Mean": 1,
+      "Min": 1,
+      "Name": "nomad-autoscaler.policy.source.error_count",
+      "Rate": 0.1,
+      "Stddev": 0,
+      "Sum": 1
+    }
+  ],
+  "Gauges": [
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.policy.total_num",
+      "Value": 0
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.alloc_bytes",
+      "Value": 7230328
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.free_count",
+      "Value": 137217
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.heap_objects",
+      "Value": 90821
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.malloc_count",
+      "Value": 228038
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.num_goroutines",
+      "Value": 15
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.sys_bytes",
+      "Value": 75317504
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns",
+      "Value": 293262
+    },
+    {
+      "Labels": {},
+      "Name": "nomad-autoscaler.pathfinder.runtime.total_gc_runs",
+      "Value": 4
+    }
+  ],
+  "Points": [],
+  "Samples": [],
+  "Timestamp": "2020-08-25 10:25:20 +0000 UTC"
+}
+```
+
+[agent_enable_debug]: /nomad/tools/autoscaling/agent#enable_debug
+[go_debug]: https://golang.org/pkg/runtime/pprof/#Profile
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/cli.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/cli.mdx
new file mode 100644
index 0000000000..b5988c78aa
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/cli.mdx
@@ -0,0 +1,223 @@
+---
+layout: docs
+page_title: CLI
+description: >
+  The Nomad Autoscaler can be controlled via a command-line interface. This
+  page documents all the commands the Nomad Autoscaler accepts.
+---
+
+# Nomad Autoscaler Command: agent
+
+The agent command is used to start the Nomad Autoscaler which runs until an
+interrupt signal is received. The Nomad Autoscaler agent's configuration
+primarily comes from the config files used, but a subset of the options may
+also be passed directly as CLI arguments. See the
+[Nomad Autoscaler Agent guide][nomad_autoscaler_agent_guide] for more information
+on how to use this command and the options it has.
+
+## Command-line Options
+
+A subset of the available Nomad Autoscaler agent configuration can optionally be
+passed in via CLI arguments. The `agent` command accepts the following arguments:
+
+- `-config=<path>`: The path to either a single config file or a directory of
+  config files to use for configuring the Nomad Autoscaler agent.
+
+- `-log-level=<level>`: Specify the verbosity level of Nomad Autoscaler's logs.
+  Valid values include `DEBUG`, `INFO`, and `WARN`, in decreasing order of verbosity.
+  The default is `INFO`.
+
+- `-log-json`: Output logs in a JSON format. The default is `false`.
+
+- `-plugin-dir=<path>`: The plugin directory is used to discover Nomad Autoscaler
+  plugins. If not specified, the plugin directory defaults to be that of
+  `<current-dir>/plugins/`.
+
+- `-http-bind-address=<addr>`: The HTTP address that the health server will bind
+  to. The default is `127.0.0.1`.
+
+- `-http-bind-port=<port>`: The port that the health server will bind to. The
+  default is `8080`.
+
+- `-enable-debug`: Enable the agent debugging HTTP endpoints. The default is
+  false.
+
+- `-nomad-address=<addr>`: The address of the Nomad server in the form of
+  `protocol://addr:port`. The default is `http://127.0.0.1:4646`.
+
+- `-nomad-region=<region>`: The region of the Nomad servers to connect with.
+
+- `-nomad-namespace=<namespace>`: The target namespace for queries and actions
+  bound to a namespace.
+
+- `-nomad-token=<token>`: The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `-nomad-http-auth=<username:password>`: The authentication information to use
+  when connecting to a Nomad API which is using HTTP authentication.
+
+- `-nomad-ca-cert=<path>`: Path to a PEM encoded CA cert file to use to verify
+  the Nomad server SSL certificate.
+
+- `-nomad-ca-path=<path>`: Path to a directory of PEM encoded CA cert files to
+  verify the Nomad server SSL certificate. If both `-nomad-ca-cert` and
+  `-nomad-ca-path` are specified, `-nomad-ca-cert` is used.
+
+- `-nomad-client-cert=<path>`: Path to a PEM encoded client certificate for TLS
+  authentication to the Nomad server. Must also specify `-nomad-client-key`.
+
+- `-nomad-client-key=<path>`: Path to an unencrypted PEM encoded private key
+  matching the client certificate from `-nomad-client-cert`.
+
+- `-nomad-tls-server-name=<name>`: The server name to use as the SNI host when
+  connecting via TLS.
+
+- `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
+
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
+- `-policy-dir=<path>`: The path to a directory used to load scaling policies.
+
+- `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
+  all scaling policies which do not specify a cooldown period. The default is `5m`.
+
+- `-policy-default-evaluation-interval=<dur>`: The default evaluation interval
+  that will be applied to all scaling policies which do not specify an evaluation
+  interval. The default is `10s`.
+
+- `-policy-eval-ack-timeout=<dur>`: The time limit that an eval must be ACK'd before
+  being considered NACK'd.
+
+- `-policy-eval-delivery-limit=<num>`: The maximum number of times a policy
+  evaluation can be dequeued from the broker.
+
+- `-policy-eval-workers=<key:value>`: The number of workers to initialize for each
+  queue, formatted as `<queue1>:<num>,<queue2>:<num>`. Nomad Autoscaler supports
+  `cluster` and `horizontal` queues. Nomad Autoscaler Enterprise supports additional
+  `vertical_mem` and `vertical_cpu` queues.
+
+- `-policy-source-disable-file`: Disable the sourcing of policies from disk.
+
+- `-policy-source-disable-nomad`: Disable the sourcing of policies from the
+  Nomad API.
+
+- `-telemetry-disable-hostname`: Specifies whether gauge values should be prefixed
+  with the local hostname.
+
+- `-telemetry-enable-hostname-label`: Enable adding hostname to metric labels.
+
+- `-telemetry-collection-interval=<dur>`: Specifies the time interval at which
+  the agent collects telemetry data. The default is 1s.
+
+- `-telemetry-statsite-address=<addr>`: The address of the statsite aggregation
+  server.
+
+- `-telemetry-statsd-address=<addr>`: The address of the statsd aggregation.
+
+- `-telemetry-dogstatsd-address=<addr>`: The address of the Datadog statsd server.
+
+- `-telemetry-dogstatsd-tag=<tag_list>`: A list of global tags that will be added
+  to all telemetry packets sent to DogStatsD.
+
+- `-telemetry-prometheus-metrics`: Indicates whether the agent should make Prometheus
+  formatted metrics available. Defaults to `false`.
+
+- `-telemetry-prometheus-retention-time=<dur>`: The time to retain Prometheus
+  metrics before they are expired and untracked.
+
+- `-telemetry-circonus-api-token`: A valid API Token used to create/manage check.
+  If provided, metric management is enabled.
+
+- `-telemetry-circonus-api-app`: The app name associated with API token. Defaults
+  to `nomad_autoscaler`.
+
+- `-telemetry-circonus-api-url`: The base URL to use for contacting the Circonus
+  API. Defaults to `https://api.circonus.com/v2`.
+
+- `-telemetry-circonus-submission-interval`: The interval at which metrics are
+  submitted to Circonus. Defaults to `10s`.
+
+- `-telemetry-circonus-submission-url`: The check.config.submission_url field
+  from a previously created HTTPTrap check.
+
+- `-telemetry-circonus-check-id`: The check id from a previously created HTTPTRAP
+  check. The numeric portion of the check.\_cid field.
+
+- `-telemetry-circonus-check-force-metric-activation`: Force enabling metrics,
+  as they are encountered, if the metric already exists and is NOT active. If
+  check management is enabled, the default behavior is to add new metrics as
+  they are encountered.
+
+- `-telemetry-circonus-check-instance-id`: Uniquely identify the metrics coming
+  from this agent. Defaults to `hostname:app`.
+
+- `-telemetry-circonus-check-search-tag`: A special tag that helps to narrow
+  down the search results when neither a submission URL or check ID are provided.
+  Defaults to `service:app`.
+
+- `-telemetry-circonus-check-tags`: A comma separated list of tags to apply to
+  the check. The value of `-telemetry-circonus-check-search-tag` will always be
+  added to the check.
+
+- `-telemetry-circonus-check-display-name`: The name used for the Circonus check
+  that will be displayed in the UI. This defaults to the value of
+  `-telemetry-circonus-check-instance-id`.
+
+- `-telemetry-circonus-broker-id`: The Circonus broker to use when creating a
+  new check.
+
+- `-telemetry-circonus-broker-select-tag`: A tag which is used to select a broker
+  ID when an explicit broker ID is not provided.
+
+- `-high-availability-enabled`: Specifies whether the Nomad Autoscaler agent will
+  start in high availability mode. If enabled, the agent instance attempts to
+  hold a lock over a Nomad variable and will only execute if the lock is
+  successfully acquired. It defaults to `false`.
+
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
+- `-high-availability-lock-path`: Defines the path of the Nomad variable that
+  will be used to sync the leader when running in high availability mode. This
+  parameter needs to be the same on all Nomad Autoscaler agents expected to
+  take part in the same leadership election process. Defaults to
+  `nomad-autoscaler/lock`.
+
+- `-high-availability-lock-ttl`: Defines the lease period or TTL of the lock used
+  to sync the leader when running on high availability mode. If the Nomad
+  Autoscaler agent does not renew the lock within this period, the lock is
+  considered lost. Defaults to `60s`.
+
+- `-high-availability-lock-delay`: Defines the period that the lock will be
+  blocked after the TTL expired without being renewed. This helps prevent split
+  brain situations. Defaults to `30s`.
+
+# Nomad Autoscaler Command: version
+
+The `version` command displays build information about the running binary,
+including the release version and the exact revision.
+
+## Usage
+
+```plaintext
+nomad-autoscaler version
+```
+
+## Output
+
+This command prints both the version number as well as the exact commit SHA used
+during the build. The SHA may also have the string `+CHANGES` appended to the
+end, indicating that local, uncommitted changes were detected at build time.
+
+## Examples
+
+```shell-session
+$ nomad-autoscaler version
+Nomad Autoscaler v0.0.3-dev (da91fa9)
+```
+
+[nomad_autoscaler_agent_guide]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/index.mdx
new file mode 100644
index 0000000000..3efbc5b49b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/index.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: Autoscaling Concepts
+description: >
+  This section covers concepts of the Nomad Autoscaler and explains
+  technical details of its operation.
+---
+
+# Nomad Autoscaler Concepts
+
+This section covers concepts of the Nomad Autoscaler and explains the technical
+details of how it functions, its architecture, and sub-systems.
+
+The Nomad Autoscaler is modeled around the concept of a closed-loop control
+system. These types of systems are often at the core of self-regulating
+mechanisms because they are able to adjust some value based on the current
+state of the system and some user provided configuration. An example of a
+closed-loop control system is a thermostat, where you set the desired
+temperature and the appliance will regulate the output of cold and hot air to
+make sure the room stays at the value set.
+
+In closed-loop systems there are a few key components:
+
+* **Setpoint** is the desired output as defined by the user.
+* **Comparator** computes the difference between the setpoint and current
+  state of the system.
+* **Controller** connects all the components together and defines what
+  needs to be done to bring the system closer to the desired state.
+* **Actuator** applies the changes defined by the controller.
+* **System** is the entity being controlled.
+* **Output** is the current value of the system.
+* **Sensor** reads the system output and translates it to a value that can be
+  used by the controller.
+
+[![Closed-loop controller](/img/autoscaling/control-loop.png)](/img/autoscaling/control-loop.png)
+
+The Nomad Autoscaler follows this same base architecture and offloads some of
+the components to [different types of plugins](/nomad/tools/autoscaling/concepts/plugins).
+
+* The autoscaling **policy** is how users define their desired outcome and
+  control the Nomad Autoscaler.
+* **Target** is what users want to scale. It can be a job group, where the
+  number of allocations is scaled, or a set of Nomad clients, where the number
+  of nodes is what changes.
+* **Strategy plugins** receive the current status of the scaling target (such
+  as the number of allocations of a group) and metrics of the system to compute
+  what actions need to be taken.
+* **Target plugins** communicate with targets to both read its status and to
+  apply changes defined by the Autoscaler.
+* **APM plugins** read application performance metrics from external sources.
+
+[![Nomad Autoscaler architecture](/img/autoscaling/autoscaler-arch.png)](/img/autoscaling/autoscaler-arch.png)
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/apm.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/apm.mdx
new file mode 100644
index 0000000000..dbb8dc7e51
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/apm.mdx
@@ -0,0 +1,48 @@
+---
+layout: docs
+page_title: APM Plugins
+description: Learn how to author a Nomad Autoscaler APM plugin.
+---
+
+# APM Plugins
+
+APM plugins are used by the autoscaler to interact with an external APM system,
+returning metrics that are used by the autoscaler to inform scaling actions.
+
+For a real-world example of a Nomad APM plugin implementation, see the
+[`prometheus` plugin](https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/builtin/apm/prometheus).
+
+## Authoring APM Plugins
+
+Authoring an APM plugin in Go can be accomplished by implementing the
+[`apm.APM`][apm_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` APM plugin][noop_plugin] can be used as a starting point for new APM
+plugins.
+
+## APM Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Query(query string, timeRange sdk.TimeRange) (sdk.TimestampedMetrics, error)`
+
+The `Query` function is called by the agent during policy
+evaluation. The `query` argument is the opaque string from the scaling policy,
+and the `timeRange` indicates the period of time over which the query should be
+made. The response is a series of timestamped metrics; as such, the query semantics
+should be such that the backing APM will return a time series. An example is the
+CPU utilization of a task group, averaged over all current allocations.
+
+#### `QueryMultiple(query string, timeRange sdk.TimeRange) ([]sdk.TimestampedMetrics, error)`
+
+The `QueryMultiple` method is similar to `Query`, except that the interface allows
+multiple time series to be returned. This endpoint is currently only used for
+[Dynamic Application Sizing][das].
+An example would be to return the CPU utilization for all allocations during
+the time range.
+
+[apm_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/apm/apm.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-apm
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/base.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/base.mdx
new file mode 100644
index 0000000000..91f268d6dd
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/base.mdx
@@ -0,0 +1,33 @@
+---
+layout: docs
+page_title: Base Plugin
+description: Learn about how to author a Nomad Autoscaler plugin.
+---
+
+# Base Plugin
+
+The base plugin is an interface required of all autoscaler plugins,
+providing a set of common operations.
+
+## Plugin API
+
+#### `PluginInfo() (*PluginInfo, error)`
+
+A `PluginInfo` contains metadata about the plugin. For example,
+the Prometheus APM plugin returns the following;
+
+```go
+PluginInfo{
+    // Name of the plugin
+    Name: "prometheus",
+    // Plugin type: "apm", "strategy", or "target"
+    PluginType: "apm"
+}
+```
+
+#### `SetConfig(config map[string]string) error`
+
+The `SetConfig` function is called when starting an instance of the plugin. It contains the
+configuration for a named instance of the plugin as provided in the autoscaler [agent config][plugin_config].
+
+[plugin_config]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/index.mdx
new file mode 100644
index 0000000000..c696e2a53a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/index.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Plugins
+description: Learn about how external plugins work in the Nomad Autoscaler.
+---
+
+# Plugins
+
+The Nomad Autoscaler uses a plugin framework which allows users to extend its
+functionality. The design of the plugin system is inspired by the
+[plugin system][nomad_plugin_system] used in Nomad for task drivers and
+devices.
+
+The following components are currently pluggable within the Nomad Autoscaler:
+
+- [APMs](/nomad/tools/autoscaling/internals/plugins/apm)
+- [Strategies](/nomad/tools/autoscaling/internals/plugins/strategy)
+- [Targets](/nomad/tools/autoscaling/internals/plugins/target)
+
+In addition, each plugin implements a [base](/nomad/tools/autoscaling/internals/plugins/base)
+plugin functionality.
+
+# Architecture
+
+The Nomad Autoscaler plugin framework uses the [go-plugin][goplugin] project to expose
+a language-independent plugin interface. Plugins implement a set of gRPC
+services and methods which the Autoscaler agent manages by running the plugin
+and calling the implemented RPCs. This means that plugins are free to be
+implemented in the author's language of choice.
+
+To make plugin development easier, a set of Go interfaces and structs exist for
+each plugin type that abstract the `go-plugin` and gRPC interfaces. The guides in
+this documentation reference these abstractions for ease of use.
+
+The existing plugins can serve as examples; in addition, no-op external plugins
+are available in the [autoscaler repo][noop_plugins].
+
+[goplugin]: https://github.com/hashicorp/go-plugin
+[nomad_plugin_system]: /nomad/docs/concepts/plugins
+[noop_plugins]: https://github.com/hashicorp/nomad-autoscaler/tree/main/plugins/test
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/strategy.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
new file mode 100644
index 0000000000..d9fe85e8e5
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/strategy.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: Strategy Plugins
+description: Learn how to author a Nomad Autoscaler Strategy plugin.
+---
+
+# Strategy Plugins
+
+Strategy plugins are used by the autoscaler to implement the logic of scaling strategy.
+They typically consume metrics from the configured APM plugin and the current scaling value
+from the target plugin and compute a new desired value for the scaling target.
+
+For a real-world example of a Nomad strategy plugin implementation, see the
+[`target-value` plugin][target_value].
+
+## Authoring Strategy Plugins
+
+Authoring a strategy plugin in Go can be accomplished by implementing the
+[`strategy.Strategy`][strategy_plugin] interface, alongside a `main` package to launch the plugin.
+
+The [`no-op` Strategy plugin][noop_plugin] can be used as a starting point for new Strategy
+plugins.
+
+## Strategy Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Run(eval *sdk.ScalingCheckEvaluation, count int64) (*sdk.ScalingCheckEvaluation, error)`
+
+The `Run` function is called by the agent during policy
+evaluation. The `eval` argument contains [information](https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/eval_oss.go#L8)
+about the current policy evaluation, including the policy specification and the metrics from the APM. The `count`
+argument includes the current value of the scaling target. The returned struct should include the result
+from applying the strategy.
+
+[strategy_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/strategy/strategy.go#L11
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-strategy
+[target_value]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/strategy/target-value
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/target.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/target.mdx
new file mode 100644
index 0000000000..46e29e0269
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/plugins/target.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: Target Plugins
+description: Learn how to author a Nomad Autoscaler Target plugin.
+---
+
+# Target Plugins
+
+Target plugins are used by the autoscaler to retrieve information about a
+scaling target and also to perform a scaling action against them.
+
+For a real-world example of a Nomad Target plugin implementation, see the
+[Nomad `group->count` plugin][nomad_group_count_plugin].
+
+## Authoring Target Plugins
+
+Authoring a target plugin in Go can be accomplished by implementing the
+[`target.Target`][target_plugin] interface, alongside a `main` package to
+launch the plugin.
+
+The [`no-op` Target plugin][noop_plugin] can be used as a starting point for new Target
+plugins.
+
+## Target Plugin API
+
+The [base plugin][base_plugin] interface must be implemented in addition to the
+following functions.
+
+#### `Scale(action sdk.ScalingAction, config map[string]string) error`
+
+The `Scale` method is called by the agent during policy evaluation. The `action`
+argument specifies the [details][scaling_action_sdk] about the scaling action
+that should be made against the target. `config` includes the details about the
+scaling target that were provided in the [scaling policy][policy_target].
+
+#### `Status(config map[string]string) (*sdk.TargetStatus, error)`
+
+The `Status` method is called by the agent in order to determine the current
+status of a scaling target. This is performed as part of policy evaluation,
+and the [information][target_status_sdk] returned may be used by the scaling
+strategy to inform the next scaling action. Information returned includes
+current scaling level, readiness, and arbitrary metadata.
+
+[nomad_group_count_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/builtin/target/nomad
+[target_plugin]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/plugins/target/target.go#L12
+[base_plugin]: /nomad/tools/autoscaling/internals/plugins/base
+[noop_plugin]: https://github.com/hashicorp/nomad-autoscaler/tree/v0.3.0/plugins/test/noop-target
+[scaling_action_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/strategy.go#L25
+[policy_target]: /nomad/tools/autoscaling/policy#target
+[target_status_sdk]: https://github.com/hashicorp/nomad-autoscaler/blob/v0.3.0/sdk/target.go#L6
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
new file mode 100644
index 0000000000..25027a549d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/checks.mdx
@@ -0,0 +1,104 @@
+---
+layout: docs
+page_title: Checks
+description: Learn about how the Autoscaler deals with policy checks.
+---
+
+# Scaling Policy Checks
+
+A scaling policy can include several [checks][policy_check] all of which
+produce a scaling suggestion. Each check can specify its own source of metrics
+data and apply different strategies based on the desired outcome.
+
+```hcl
+policy {
+  # ...
+  check "cpu_allocated_percentage" {
+    source = "prometheus"
+    query  = "..."
+
+    strategy "target-value" {
+      target = 70
+    }
+  }
+
+  check "high-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    source = "prometheus"
+    query  = "..."
+    group  = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+}
+```
+
+## Resolving Conflicts
+
+The checks are all executed at the same time during a policy evaluation and
+they can generate conflicting scaling actions. In a scenario like this, the
+Autoscaler iterates over the results and chooses the safest option, which is
+defined as the action that results in retaining the most capacity of the
+resource.
+
+In a scenario where two checks return different desired scaling directions, the
+following logic is applied.
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+
+In situations where the same actions are suggested, but with different counts
+the following logic is applied, where the count is the final desired value.
+
+- `ScaleOut(10) and ScaleOut(9) => ScaleOut(10)`
+- `ScaleIn(3) and ScaleIn(4) => ScaleIn(4)`
+
+## Check Grouping
+
+The above logic for resolving conflicts only works when the checks are
+independent from each other. If you use the same `query` in multiple `check`
+blocks, or if the underlying data being queried is somehow correlated, only
+one check will result in a scaling action.
+
+In the example above, the `high-memory-usage` and `low-memory-usage` checks use
+the same query to retrieve memory usage information. We expect that memory
+usage is either low or high (or neither), but never both at the same time.
+
+Without grouping the target is never be able to reduce its count, since the
+possible resulting actions and the final scaling outcome can only be one of the
+following:
+
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleNone`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+To fix this problem, the correlated checks need to be set to the same `group`.
+The Nomad Autoscaler then computes a single scaling action for the entire group
+by applying a slightly different logic:
+
+- `ScaleOut and ScaleIn => ScaleOut`
+- `ScaleOut and ScaleNone => ScaleOut`
+- `ScaleIn and ScaleNone => ScaleIn`
+- `ScaleNone and ScaleNone => ScaleNone`
+
+`ScaleNone` results are ignored unless all checks in the group return it and so
+a group is able to `ScaleIn` a target even when all other checks results in no
+action.
+
+[policy_check]: /nomad/tools/autoscaling/policy#check-options
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
new file mode 100644
index 0000000000..09587cbaad
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/index.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: Autoscaling Policy Evaluation
+description: >
+  This section covers how scaling policies are evaluated to generate scaling
+  actions.
+---
+
+# Policy Evaluation
+
+When the Nomad Autoscaler [agent] starts it loads all the policies defined in
+the [sources][agent_source] configured and monitors them for changes. Each
+policy is assigned a handler that periodically sends the policy to a broker
+where it is evaluated by a worker. The frequency the policy is enqueued is set
+by its [`evaluation_interval`][policy_eval_interval].
+
+The worker executes a series of steps by calling the different plugins used in
+the policy to determine if a scaling action is needed and then to apply the
+necessary actions. The worker then loops back to evaluate the next policy.
+
+If a scaling action is performed and the policy defines a
+[`cooldown`][policy_cooldown] value the policy handler waits the specified
+value before enqueuing it again.
+
+If the policy target are Nomad clients the target plugin will usually execute
+more steps, such as [selecting nodes to be removed][concepts_node_selector] and
+draining them.
+
+[![Scaling policy evaluation pipeline](/img/autoscaling/policy-eval.png)](/img/autoscaling/policy-eval.png)
+
+[agent]: /nomad/tools/autoscaling/agent
+[agent_source]: /nomad/tools/autoscaling/agent/source
+[concepts_node_selector]: /nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy
+[policy_cooldown]: /nomad/tools/autoscaling/policy#cooldown
+[policy_eval_interval]: /nomad/tools/autoscaling/policy#evaluation_interval
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
new file mode 100644
index 0000000000..e59f6fb1e7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/concepts/policy-eval/node-selector-strategy.mdx
@@ -0,0 +1,59 @@
+---
+layout: docs
+page_title: Node Selector Strategy
+description: Learn about the Autoscaler's node selection strategies.
+---
+
+# Node Selector Strategy
+
+The node selector strategy is a mechanism the Nomad Autoscaler uses to identify
+nodes for termination when performing horizontal cluster scale-in actions. It
+is exposed as a target configuration option so that operators can modify its
+behaviour based on requirements.
+
+### `least_busy` Node Selector Strategy
+
+The `least_busy` strategy is the default node selector strategy used if the
+`node_selector_strategy` configuration option is omitted. When used, the Nomad
+Autoscaler will sort nodes based on their overall CPU and memory allocation;
+picking those with the lowest values. In the event a number of nodes have the
+same allocated percentage value, the selection will be random according to Golang's
+sort implementation.
+
+The `least_busy` strategy suits workloads that can tolerate migrations but
+allows you to minimise such events.
+
+### `empty` Node Selector Strategy
+
+The `empty` strategy will only consider nodes eligible for termination if they
+have zero non-terminal allocations. The terminal status of an allocation is
+determined using [these Nomad SDK allocation functions][nomad_api_terminal_alloc].
+The strategy will skip any node that does not meet this requirement. This can
+result in scaling actions terminating a smaller number of nodes than desired. In
+the event no nodes are found to be empty, the Nomad Autoscaler will decline to
+perform the scaling action.
+
+The `empty` strategy is ideal for batch workloads, ensuring allocations are not
+interrupted by scaling.
+
+~> **Note:** [system][system_scheduler] jobs will prevent this strategy from
+scaling-in nodes. Please use the [`empty_ignore_system`](#empty_ignore_system)
+strategy if you have system jobs in your cluster.
+
+### `empty_ignore_system` Node Selector Strategy
+
+The `empty_ignore_system` strategy is similar to `empty`, but it will not
+consider allocations from [system][system_scheduler] jobs. A node with only
+terminal allocations and allocations from system jobs is considered empty under
+this strategy.
+
+### `newest_create_index` Node Selector Strategy
+
+The `newest_create_index` strategy is the simplest strategy and uses the order
+in which nodes are returned by the [Nomad SDK][nomad_api_node_stub_sort]. The
+strategy is ideal for workloads and environments which can handle migrations
+due to scaling. It is also the least computationally intensive selector strategy.
+
+[nomad_api_terminal_alloc]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/allocations.go#L422-L442
+[nomad_api_node_stub_sort]: https://github.com/hashicorp/nomad/blob/14568b3e002868fc5c83ee7d158a78394c1ea9c1/api/nodes.go#L797-L810
+[system_scheduler]: /nomad/docs/schedulers#system
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/index.mdx
new file mode 100644
index 0000000000..ebf49fbf3a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/index.mdx
@@ -0,0 +1,70 @@
+---
+layout: docs
+page_title: Autoscaling
+description: |-
+  Overview of the Nomad Autoscaler that provides horizontal application and
+  cluster scaling.
+---
+
+# Nomad Autoscaler Overview
+
+This section details the Nomad Autoscaler, a horizontal application and cluster
+autoscaler for Nomad. The Nomad Autoscaler is built and released separately to
+Nomad. It runs as a daemon process, often referred to as the [Autoscaler Agent][autoscaler_agent].
+An Autoscaler Agent is a separate and distinct process from a Nomad Agent. The
+source code can be viewed on [GitHub][autoscaler_github] and releases are available
+on the [HashiCorp releases page][autoscaler_releases] or via [Docker Hub][autoscaler_dockerhub].
+
+The Nomad Autoscaler repository includes a number of [demos][autoscaler_demo]
+which provide guided learning on running the Nomad AutoScaler. Since Autoscaler
+Agent runs as its own daemon, it requires its own configuration. Configuration
+can be passed as command line flags or parsed from a configuration file. The demos
+repository includes an example [config][autoscaler_config] file that is useful to
+reference when configuring your Autoscaler Agent.
+
+## Horizontal Application Autoscaling
+
+Horizontal application autoscaling is the process of automatically controlling the
+number of instances of an application to have sufficient work throughput to meet
+service-level agreements (SLA). In Nomad, horizontal application autoscaling can
+be achieved by modifying the number of allocations in a task group based on the
+value of a relevant metric, such as CPU and memory utilization or number of open
+connections. This is enabled by configuring [autoscaling policies][autoscaling_policy]
+on individual Nomad jobs using the [`scaling` block][scaling_block].
+
+## Horizontal Cluster Autoscaling
+
+Horizontal cluster autoscaling is the process of adding or removing Nomad clients
+from a cluster to ensure there is an appropriate amount of cluster resource for
+the scheduled applications. This is achieved by interacting with remote providers
+to start or terminate new Nomad clients based on metrics such as the remaining
+free schedulable CPU or memory. Cluster scaling is enabled by configuring the
+[autoscaler agent](/nomad/tools/autoscaling/agent#dir) with policies targeting the Nomad
+cluster.
+
+## Dynamic Application Sizing
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+Dynamic Application Sizing enables organizations to optimize the resource
+consumption of applications using sizing recommendations from Nomad. It evaluates,
+processes and stores historical task resource usage data, making recommendations
+for CPU and Memory resource parameters. The recommendations can be calculated
+using a number of different algorithms to ensure the recommendation best fits
+the application profile.
+
+Dynamic Application Sizing can be enabled on an individual task by configuring
+[autoscaling policies][autoscaling_policy] within the task block using the job
+specification [`scaling` block][scaling_block].
+
+[scaling_block]: /nomad/docs/job-specification/scaling#scaling-block
+[autoscaling_policy]: /nomad/tools/autoscaling/policy
+[autoscaler_github]: https://github.com/hashicorp/nomad-autoscaler
+[autoscaler_releases]: https://releases.hashicorp.com/nomad-autoscaler/
+[autoscaler_dockerhub]: https://hub.docker.com/r/hashicorp/nomad-autoscaler
+[autoscaler_demo]: https://github.com/hashicorp/nomad-autoscaler-demos
+[autoscaler_config]: https://github.com/hashicorp/nomad-autoscaler-demos/blob/1ecd9f32c749f1faaf4154b8a7e57fa68642fd33/cloud/demos/on-demand-batch/aws/jobs/autoscaler.nomad.tpl#L20
+[autoscaler_agent]: /nomad/tools/autoscaling/agent
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/datadog.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/datadog.mdx
new file mode 100644
index 0000000000..e310b4685a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/datadog.mdx
@@ -0,0 +1,50 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Datadog'
+description: The "datadog" APM plugin queries Datadog for metrics.
+---
+
+# Datadog APM Plugin
+
+The `datadog` APM plugin allows using [time series][datadog_timeseries] data
+from [Datadog][datadog_homepage] to make scaling decisions.
+
+## Agent Configuration Options
+
+```hcl
+apm "datadog" {
+  driver = "datadog"
+
+  config = {
+    dd_api_key = "<api key>"
+    dd_app_key = "<app key>"
+
+    site = "datadoghq.eu"
+  }
+}
+```
+
+- `dd_api_key` `(string: <required>)` - The Datadog API key to use for
+  authentication.
+
+- `dd_app_key` `(string: <required>)` - The Datadog application key to use for
+  authentication.
+
+- `site` `(string: "datadoghq.com")` - The Datadog site to connect to.
+
+The Datadog plugin can also read its configuration options via environment
+variables. The accepted keys are `DD_API_KEY` and `DD_APP_KEY`. The agent
+configuration parameters take precedence over the environment variables.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "datadog"
+  query  = "avg:proxy.backend.response.time{proxy-service:web-app}"
+  # ...
+}
+```
+
+[datadog_homepage]: https://www.datadoghq.com/
+[datadog_timeseries]: https://docs.datadoghq.com/api/v1/metrics/#query-timeseries-points
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/index.mdx
new file mode 100644
index 0000000000..085f0a7871
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/index.mdx
@@ -0,0 +1,12 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: APM'
+description: APM plugins provide metric data points describing the resources current state.
+---
+
+# APM Plugins
+
+Application Performance Management (APM) tools are used to store metrics about
+an applications performance and its current state. The APM plugins are
+responsible for querying an APM and returning a time series which will be used
+to determine if scaling should occur.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/nomad.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/nomad.mdx
new file mode 100644
index 0000000000..3a4e13414a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/nomad.mdx
@@ -0,0 +1,138 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad API'
+description: The "nomad-apm" APM plugin queries the Nomad API for metrics.
+---
+
+# Nomad APM Plugin
+
+The Nomad APM plugin allows querying the Nomad API for metric data. This provides
+an immediate starting point without addition applications but comes at the price
+of efficiency and flexibility. When using this APM, it is advised to monitor
+Nomad carefully ensuring it is not put under excessive load pressure.
+
+Since Nomad does not store historical metric data and only reports instant
+metrics values, the Nomad APM plugin does not support the [`query_window`][]
+policy option and is not able to aggregate metrics over time, such as computing
+averages or percentiles. An external APM is required to support uses cases like
+these.
+
+~> The Nomad APM plugin should only be used when scaling based on CPU and
+memory usage. For more advanced scenarios, such as scaling a cluster to
+zero clients, you should use a different APM plugin.
+
+## Agent Configuration Options
+
+```hcl
+apm "nomad-apm" {
+  driver = "nomad-apm"
+}
+```
+
+When using a Nomad cluster with ACLs enabled, following ACL policy will provide the appropriate
+permissions for obtaining task group metrics:
+
+```hcl
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+In order to obtain cluster level metrics, the following ACL policy will be required:
+
+```hcl
+node {
+  policy = "read"
+}
+
+namespace "default" {
+  policy       = "read"
+  capabilities = ["read-job"]
+}
+```
+
+## Policy Configuration Options - Task Groups
+
+The Nomad APM allows querying Nomad to understand the current resource usage of
+a task group.
+
+```hcl
+check {
+  source = "nomad-apm"
+  query  = "avg_cpu"
+  # ...
+}
+```
+
+Querying Nomad task group metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `avg` - returns the average of the metric value across allocations in the task
+  group.
+
+- `min` - returns the lowest metric value among the allocations in the task group.
+
+- `max` - returns the highest metric value among the allocations in the task
+  group.
+
+- `sum` - returns the sum of all the metric values for the allocations in the
+  task group.
+
+The metric value can be:
+
+- `cpu` - CPU usage as reported by the `nomad.client.allocs.cpu.total_percent`
+  metric.
+
+- `cpu-allocated` - the percentage of CPU used out of the total CPU allocated
+for the allocation.
+
+- `memory` - Memory usage as reported by the `nomad.client.allocs.memory.usage`
+  metric.
+
+- `memory-allocated` - the percentage of memory used out of the total memory
+allocated for the allocation.
+
+## Policy Configuration Options - Client Nodes
+
+The Nomad APM allows querying Nomad to understand the current allocated resource
+as a percentage of the total available.
+
+~> **Note:** When using the Nomad APM plugin for cluster scaling, your policy `target` and
+all Nomad clients intended to be targeted by the policy must have a
+`node_class` defined. Nodes without `node_class` are evaluated using the
+default class value `autoscaler-default-pool`.
+
+```hcl
+policy {
+  # ...
+  check {
+    source = "nomad-apm"
+    query  = "percentage-allocated_cpu"
+    # ...
+  }
+
+  target "..." {
+    # ...
+    node_class = "autoscale"
+    # ..
+  }
+}
+```
+
+Querying Nomad client node metrics is be done using the `<operation>_<metric>`
+syntax, where valid operations are:
+
+- `percentage-allocated` - returns the allocated percentage of the desired
+  resource.
+
+The metric value can be:
+
+- `cpu` - allocated CPU as reported by calculating total allocatable against the
+  total allocated by the scheduler.
+
+- `memory` - allocated memory as reported by calculating total allocatable against
+  the total allocated by the scheduler.
+
+[nomad_telemetry_block]: /nomad/docs/configuration/telemetry#inlinecode-publish_allocation_metrics
+[`query_window`]: /nomad/tools/autoscaling/policy#query_window
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/prometheus.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
new file mode 100644
index 0000000000..e3a5c1f253
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/apm/prometheus.mdx
@@ -0,0 +1,61 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Prometheus'
+description: The "prometheus" APM plugin queries a Prometheus server.
+---
+
+# Prometheus APM Plugin
+
+The `prometheus` APM plugin allows querying for metrics stored in a
+[Prometheus][prometheus_io] server.
+
+## Agent Configuration Options
+
+```hcl
+apm "prometheus" {
+  driver = "prometheus"
+
+  config = {
+    address = "http://prometheus.my.endpoint.io:9090"
+
+    ca_cert = "/path/to/ca.crt"
+
+    basic_auth_user     = "user"
+    basic_auth_password = "secret"
+
+    header_X-Scope-OrgID   = "my-org"
+    header_X-Custom-Header = "custom-header"
+  }
+}
+```
+
+- `address` `(string: "http://127.0.0.1:9090")` - The address of the Prometheus
+  endpoint used to perform queries.
+
+- `basic_auth_user` `(string: "")` - The HTTP basic auth user to use when
+  making requests to Prometheus.
+
+- `basic_auth_password` `(string: "")` - The HTTP basic auth password to use
+  when making requests to Prometheus.
+
+- `ca_cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  connect to the Prometheus server.
+
+- `header_*` `(string: "")` - Additional HTTP headers to set when making
+  requests to Prometheus. Several headers may be specified and the final header
+  name will be set as the key with the `header_` prefix removed.
+
+- `skip_verify` `(bool: false)` - Do not verify TLS certificates when
+  connecting to the Prometheus server. This is strongly discouraged.
+
+## Policy Configuration Options
+
+```hcl
+check {
+  source = "prometheus"
+  query  = "avg((haproxy_server_current_sessions{backend=\"http_back\"}))"
+  # ...
+}
+```
+
+[prometheus_io]: https://prometheus.io/
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/external/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/external/index.mdx
new file mode 100644
index 0000000000..4a240c3ccf
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/external/index.mdx
@@ -0,0 +1,31 @@
+---
+layout: docs
+page_title: 'Autoscaler Plugins: Community Supported'
+description: A list of community-supported Autoscaler Plugins.
+---
+
+# Community Supported
+
+If you have authored an autoscaler plugin that you believe will be useful to
+the broader Nomad community and you are committed to maintaining the plugin,
+please file a PR to add your plugin to this page.
+
+For details on authoring an autoscaler plugin, please refer to the [plugin
+authoring guide][plugin_guide].
+
+Below is a list of community-support plugins available for the Nomad autoscaler.
+
+## Target Plugins
+
+- [Ali Cloud][aliyun]
+- [DigitalOcean Droplets][do-droplets]
+- [Hetzner Cloud][hcloud]
+- [OpenStack Nova][os-nova]
+- [OpenStack Senlin][senlin]
+
+[aliyun]: https://github.com/wrli20/nomad-aliyun-autoscaler
+[plugin_guide]: /nomad/tools/autoscaling/internals/plugins
+[senlin]: https://github.com/dkt26111/nomad-senlin-autoscaler
+[do-droplets]: https://github.com/jsiebens/nomad-droplets-autoscaler
+[os-nova]: https://github.com/jorgemarey/nomad-nova-autoscaler
+[hcloud]: https://github.com/AndrewChubatiuk/nomad-hcloud-autoscaler
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/index.mdx
new file mode 100644
index 0000000000..01fb253e31
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/index.mdx
@@ -0,0 +1,79 @@
+---
+layout: docs
+page_title: Autoscaling Plugins
+description: Plugins are used to architect the Nomad Autoscaler into distinct areas.
+---
+
+# Nomad Autoscaler Plugins
+
+Plugins are an essential part of the Nomad Autoscaler architecture. The Autoscaler
+uses the [go-plugin][go_plugin_github] library to implement an ecosystem of
+different types of plugins. Each plugin type is responsible for a specific task:
+APM plugins retrieve metrics about the workloads being monitored; strategy
+plugins decide the scaling action to satisfy the scaling policy; and target
+plugins perform the scaling action. The flexibility of plugins allows the Nomad
+Autoscaler to be extended to meet specific business requirements or technology
+use cases.
+
+The Nomad Autoscaler currently ships with a number of built-in plugins to ease
+the learning curve. Details of these can be found in the side menu, under the
+specific plugin type sections. The autoscaler also supports external plugins; see
+this list of [community-supported plugins][community_plugins].
+
+# General Options
+
+All plugins which require Nomad API connectivity support the parameters detailed
+below. These plugins include Nomad APM, Nomad Target and all cluster scaling
+targets.
+
+- `nomad_config_inherit` `(bool: true)` - A boolean flag which indicates whether
+  the plugin should inherit the agents Nomad configuration parameters. Plugins
+  can override individual parameters and have their Nomad configuration merged
+  with that of the agent.
+
+- `nomad_address` `(string: "")` - The address of the Nomad server in the form
+  of `protocol://addr:port`.
+
+- `nomad_region` `(string: "")` - The region of the Nomad servers to connect with.
+
+- `nomad_namespace` `(string: "")` - The target namespace for queries and actions
+  bound to a namespace.
+
+- `nomad_token` `(string: "")` - The SecretID of an ACL token to use to authenticate
+  API requests with.
+
+- `nomad_http-auth` `(string: "")` - The authentication information to use when
+  connecting to a Nomad API which is using HTTP authentication.
+
+- `nomad_ca-cert` `(string: "")` - Path to a PEM encoded CA cert file to use to
+  verify the Nomad server SSL certificate.
+
+- `nomad_ca-path` `(string: "")` - Path to a directory of PEM encoded CA cert
+  files to verify the Nomad server SSL certificate.
+
+- `nomad_client-cert` `(string: "")` - Path to a PEM encoded client certificate
+  for TLS authentication to the Nomad server.
+
+- `nomad-client-key` `(string: "")` - Path to an unencrypted PEM encoded private
+  key matching the client certificate.
+
+- `nomad_tls-server-name` `(string: "")` - The server name to use as the SNI
+  host when connecting via TLS.
+
+- `nomad_skip-verify` `(string: "")` - Do not verify TLS certificates. This is
+  strongly discouraged.
+
+# Loading External Plugins
+
+In order to utilise external plugins, the plugin binary must be downloaded to a
+directory on the same host that the Nomad Autoscaler will run. This directory
+should be referenced by the [plugin_dir][plugin_dir_config] config parameter along
+with an appropriate [APM][apm], [Strategy][strategy] or [Target][target] block
+entry.
+
+[go_plugin_github]: https://github.com/hashicorp/go-plugin
+[community_plugins]: /nomad/tools/autoscaling/plugins/external
+[plugin_dir_config]: /nomad/tools/autoscaling/agent#plugin_dir
+[apm]: /nomad/tools/autoscaling/agent/apm#apm-block
+[strategy]: /nomad/tools/autoscaling/agent/strategy#strategy-block
+[target]: /nomad/tools/autoscaling/agent/target#target-block
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
new file mode 100644
index 0000000000..e595f93d4d
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-avg.mdx
@@ -0,0 +1,40 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Average'
+description: The "app-sizing-avg" strategy plugin uses the historical average usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Average Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-avg` plugin calculates the average value seen across the
+historical metrics dataset. The plugin applies an exponential weight decay to
+the data, in order to give more significance to recent data over older data.
+
+This plugin is only recommended for CPU values of workloads with very stable
+resource usage levels, such as batch jobs.
+
+## Agent Configuration Options
+
+The `app-sizing-avg` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-avg" {
+  driver = "app-sizing-avg"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "avg" {
+  strategy "app-sizing-avg" {}
+}
+```
+
+The `app-sizing-avg` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
new file mode 100644
index 0000000000..708a3d334b
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-max.mdx
@@ -0,0 +1,38 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Max'
+description: The "app-sizing-max" strategy plugin uses the historical maximum usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Max Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-max` plugin calculates the maximum value seen for the target
+resource within the available dataset. This plugin is ideally suited for memory
+resources since workloads don’t release their memory too often and
+underprovisioning could cause OOM errors.
+
+## Agent Configuration Options
+
+The `app-sizing-max` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "app-sizing-max" {
+  driver = "app-sizing-max"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "max" {
+  strategy "app-sizing-max" {}
+}
+```
+
+The `app-sizing-max` plugin doesn't have any configuration.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
new file mode 100644
index 0000000000..a21aec2d83
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/app-sizing-percentile.mdx
@@ -0,0 +1,52 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing Percentile'
+description: The "app-sizing-percentile" strategy plugin uses percentile value of the historical usage to set resource recommendations.
+---
+
+# Dynamic Application Sizing Percentile Strategy Plugin
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The `app-sizing-percentile` plugin calculates its result based on a desired
+percentile value from the dataset.
+
+The plugin applies an exponential weight decay to data, in order to give
+more significance to recent data over older data. It also adjusts its calculation
+based on the amount of resources used per unit of time. This load-adjusted
+calculation results in values that are more likely to actually meet the usage
+needs of the workload when compared to the traditional time-based percentile
+calculation.
+
+This Dynamic Application Sizing plugin is the most versatile, since the percentile
+level can be fine-tuned as needed. If your workload can withstand occasional OOM
+errors gracefully, using a 98th percentile for memory instead of app-sizing-max
+could result in smaller recommendations and subsequently more resource availability
+for other tasks. A 95th to 90th percentile for CPU could have the same effect.
+
+## Agent Configuration Options
+
+The `app-sizing-percentile` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "p95" {
+  strategy "app-sizing-percentile" {
+    percentile = "95"
+  }
+}
+```
+
+- `percentile` `(int: 99)` - Specifies the percentile value to use when performing
+  the strategy calculation.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
new file mode 100644
index 0000000000..46b9414842
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/fixed-value.mdx
@@ -0,0 +1,35 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Fixed Value'
+description: The "fixed-value" strategy plugin sets a pre-defined value when scaling.
+---
+
+# Fixed Value Strategy Plugin
+
+The `fixed-value` strategy receives a count value as an input configuration
+option and returns a scaling action whose count is set to the same value. This
+strategy is useful in situations where there’s a known baseline for the
+infrastructure that does not change often.
+
+## Agent Configuration Options
+
+```hcl
+strategy "fixed-value" {
+  driver = "fixed-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "fixed-value-check" {
+  # ...
+  strategy "fixed-value" {
+    value = 3
+  }
+  # ...
+}
+```
+
+- `value` `(int: <required>)` - The value used by the Nomad Autoscaler to set
+  the target count.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/index.mdx
new file mode 100644
index 0000000000..31f32bb26e
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/index.mdx
@@ -0,0 +1,13 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Strategy'
+description: Strategy plugins compare the current state of the system against the desired state.
+---
+
+# Strategy Plugins
+
+Strategy plugins compare the current state of the system against the desired state
+defined by the operator in the scaling policy and generate an action that will
+bring the system closer to the desired state. In practical terms, strategies
+receive the current value and a metric value for a resource and output what the
+new value should be.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
new file mode 100644
index 0000000000..dc2554d004
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/pass-through.mdx
@@ -0,0 +1,42 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Pass-Through'
+description: The "pass-through" strategy plugin passes the query result directly to the target.
+---
+
+# Pass-Through Strategy Plugin
+
+The `pass-through` strategy is a very simple, yet useful strategy. It does not
+add any extra computation on top of the metric query result, and instead uses
+the APM query result as the scaling count. It doesn't have any configuration
+options.
+
+This allows the Nomad Autoscaler to be integrated into systems where the
+scaling computation is done externally like an edge router, or easily derived
+from a query such as running one allocation per item in a queue.
+
+## Agent Configuration Options
+
+```hcl
+strategy "pass-through" {
+  driver = "pass-through"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "pass-through-check" {
+  # ...
+  strategy "pass-through" {}
+  # ...
+}
+```
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/target-value.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
new file mode 100644
index 0000000000..9fdbbead9a
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/target-value.mdx
@@ -0,0 +1,99 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target Value'
+description: The "target-value" strategy plugin tracks a target metric value.
+---
+
+# Target Value Strategy Plugin
+
+The `target-value` strategy plugin performs count calculations in order to
+keep the value resulting from the APM query at or around a specified target.
+
+It accomplishes this by extrapolating the current metric value and used
+capacity linearly to determine if a scaling action is required and how many
+instances need to be added or removed. More specify, the new scaling value is
+calculated as:
+
+```
+factor = current_metric_value / target
+new_count = factor * current_count
+```
+
+As an example, a policy that tracks memory usage with target defined as `70`
+(representing 70% of memory usage) and in a scenario where there are `10`
+instances running will generate a scaling action with scaling factor of
+`1.1428571429`, which will add `2` new instances when the metric reaches `80`
+(80% of memory usage) because:
+
+```
+factor = 80/70 = 1.1428571429
+new_count = 1.1428571429 * 10 ~= 12
+```
+
+In other words, if with 10 instances the memory usage in 80%, it's expected
+that with 12 instances the memory usage will be lower and closer to the target
+value of 70%.
+
+This means that this strategy expects your infrastructure to have the following
+characteristics:
+
+- **inverse relationship** between metric and number of instances, meaning that
+  adding _more_ instances will cause your metric value to go _down_.
+
+- **linear response** to infrastructure changes, meaning that a _2x_ increase
+  in instance count will cut the metric value approximately in _half_.
+
+~> **Note:** These properties may not be true for your infrastructure. Make
+  sure you have a good grasp of your query result dynamic as the number of
+  instances changes.
+
+To fine-tune scaling decisions you can adjust the `threshold` configuration.
+This value defines a range between `1 ± threshold` where scaling actions with a
+scaling factor within this range are ignored. For example, with the default
+value of `0.01` only scaling actions with a factor lower than `0.99` and larger
+than `1.01` are taken into account.
+
+With a low `threshold` you are expected to observe more scaling actions with
+smaller changes, while a high `threshold` value is expected to generate fewer
+scaling actions with bigger changes in count.
+
+Since `threshold` is compared against the computed scaling factor, and the
+factor is based on your expected metric values and specified `target`,
+adjusting the `threshold` value can take some time and a few trial and error
+attempts.
+
+## Agent Configuration Options
+
+```hcl
+strategy "target-value" {
+  driver = "target-value"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "target-value-check" {
+  # ...
+  strategy "target-value" {
+    target    = 20
+    threshold = 0.0001
+  }
+  # ...
+}
+```
+
+- `target` `(float: <required>)` - Specifies the metric value the Autoscaler
+  should try to meet.
+
+- `threshold` `(float: 0.01)` - Specifies how significant a change in the input
+  metric should be considered. Small threshold values can lead to output
+  fluctuation.
+
+- `max_scale_up` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be added in a single scaling operation. It acts as a safeguard
+  against the system scaling up too rapidly.
+
+- `max_scale_down` `(int: unlimited)` - Specifies the maximum number of instances
+  that can be removed in a single scaling operation. It acts as a safeguard
+  against the system scaling down too rapidly.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/threshold.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
new file mode 100644
index 0000000000..d934049925
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/strategy/threshold.mdx
@@ -0,0 +1,92 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Threshold'
+description: The "threshold" strategy plugin uses metric value tiers to define scaling actions.
+---
+
+# Threshold Strategy Plugin
+
+The `threshold` strategy defines a range of metric values with a lower and an
+upper bound, and an action to take when the current metric value is considered
+to be within bounds.
+
+Multiple tiers can be defined by declaring more than one `check` in the
+same scaling policy. If there is any overlap between the bounds, the [safest
+`check`][internals_check] will be used.
+
+~> **Note:** When using the `threshold` strategy with multiple checks make sure
+  they all have the same [`group`][policy_group] value, otherwise your target
+  may not be able to scale down.
+
+## Agent Configuration Options
+
+```hcl
+strategy "threshold" {
+  driver = "threshold"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+policy {
+  # ...
+  check "high-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 100
+      lower_bound = 70
+      delta       = 1
+    }
+  }
+
+  check "low-memory-usage" {
+    # ...
+    group = "memory-usage"
+
+    strategy "threshold" {
+      upper_bound = 30
+      lower_bound = 0
+      delta       = -1
+    }
+  }
+  # ...
+}
+```
+
+- `lower_bound` `(float: <optional>)` - The minimum value a metric must have
+  to be considered within bounds. This value is always **inclusive**, meaning a
+  metric with the exact same value as `lower_bound` is considered within
+  bounds.
+
+- `upper_bound` `(float: <optional>)` - The maximum value a metric must have
+  to be considered within bounds. This value is always **exclusive**, meaning a
+  metric with the exact same value as `upper_bound` is considered **out** of
+  bounds.
+
+- `delta` `(int: <optional>)` - Specifies the relative amount to add (positive
+  value) or remove (negative value) from the current target count. Conflicts
+  with `percentage` and `value`.
+
+- `percentage` `(float: <optional>)` - Specifies a percentage value by which
+  the current count should be increased (positive value) or decreased (negative
+  value). Conflicts with `delta` and `value`.
+
+- `value` `(int: <optional>)` - Specifies an absolute value that should be set
+  as the new target count. Conflicts with `delta` and `percentage`.
+
+- `within_bounds_trigger` `(int: 5)` - The number of data points in the query
+  result time series that must be within the bound values to trigger the
+  action.
+
+At least one of `lower_bound` or `upper_bound` must be defined. If
+`lower_bound` is not defined, any value below `upper_bound` is considered
+within bounds. Similarly, if `upper_bound` is not defined, any value above or
+equal to `lower_bound` will be considered within bounds.
+
+One, and only one, of `delta`, `percentage`, or `value` must be defined.
+
+[internals_check]: /nomad/tools/autoscaling/internals/checks
+[policy_group]: /nomad/tools/autoscaling/policy#group
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
new file mode 100644
index 0000000000..d293ba125f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/app-sizing-nomad.mdx
@@ -0,0 +1,80 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Dynamic Application Sizing'
+description: The "app-sizing-nomad" target plugin scales a task resource.
+---
+
+# Dynamic Application Sizing Nomad Task Target
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+~> Note that currently Prometheus is the only APM available for Dynamic Application Sizing
+
+The `app-sizing-nomad` target plugin reports on the current task resource value
+as well as submits recommendations to Nomad via the [recommendations API endpoint][nomad_recommendations_api]
+based on the result of the Dynamic Application Sizing strategy calculations.
+
+## Agent Configuration Options
+
+The `app-sizing-nomad` plugin is automatically launched by Nomad Autoscaler
+Enterprise and so the following setup is optional.
+
+```hcl
+target "app-sizing-nomad" {
+  driver = "app-sizing-nomad"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy for a task resource, the following section can be
+omitted as Nomad will populate them on job submission. Please also refer to the
+[Nomad Autoscaler policy documentation][nomad_autoscaler_policy] for additional
+detail and guidance.
+
+```hcl
+check "mem" {
+  ...
+  target "app-sizing-nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+    Task      = "Redis"
+    Resource  = "MemoryMB"
+  }
+  ...
+```
+
+- `Region` `(string: "")` - The region in which the job resides as defined
+  by the [`region` parameter][nomad_region_parameter] within the job specification.
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+- `Task` `(string: "")` - The name of the task to scale as defined in the job
+  specification [`task` block][nomad_task_block].
+
+- `Resource` `(string: "")` - The resource to scale as defined by the job
+  specification [`resource` block][nomad_resource_block]. Supports either `CPU`
+  or `MemoryMB`.
+
+[nomad_autoscaler_policy]: /nomad/tools/autoscaling/policy
+[nomad_group_block]: /nomad/docs/job-specification/group
+[nomad_job_block]: /nomad/docs/job-specification/job
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_recommendations_api]: /nomad/api-docs/recommendations
+[nomad_region_parameter]: /nomad/docs/job-specification/job#region
+[nomad_resource_block]: /nomad/docs/job-specification/resources
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
+[nomad_task_block]: /nomad/docs/job-specification/task
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/aws-asg.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
new file mode 100644
index 0000000000..656fb74905
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/aws-asg.mdx
@@ -0,0 +1,154 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: AWS ASG'
+description: The "aws-asg" target plugin scales an Amazon Web Services Autoscaling Group.
+---
+
+# AWS AutoScaling Group Target
+
+The `aws-asg` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [AWS AutoScaling Groups][aws_autoscaling].
+
+## Agent Configuration Options
+
+To use the `aws-asg` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the AWS API can
+be supplied in a number of ways including EC2 instance roles.
+
+It is recommended, if possible to use the [Vault AWS Secrets
+engine][vault_aws_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+The IAM policy required for the AWS ASG plugin to function properly is detailed
+below.
+
+```json
+{
+  "Version": "2012-10-17",
+  "Statement": [
+    {
+      "Sid": "",
+      "Effect": "Allow",
+      "Action": [
+        "autoscaling:UpdateAutoScalingGroup",
+        "autoscaling:DescribeScalingActivities",
+        "autoscaling:DescribeAutoScalingGroups",
+        "autoscaling:CreateOrUpdateTags",
+        "autoscaling:TerminateInstanceInAutoScalingGroup"
+      ],
+      "Resource": "*"
+    }
+  ]
+}
+```
+
+```hcl
+target "aws-asg" {
+  driver = "aws-asg"
+  config = {
+    aws_region            = "eu-west-3"
+    aws_access_key_id     = "AKIAIOSFODNN7EXAMPLE"
+    aws_secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
+  }
+}
+```
+
+- `aws_region` `(string: "us-east-1")` - The [AWS region][aws_region] identifier
+  to connect to and where resources should be managed.
+
+- `aws_access_key_id` `(string: "")` - The AWS access key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_secret_access_key` `(string: "")` - The AWS secret key ID used to authenticate
+  with the AWS API. If empty, the IAM role attached to the EC2 instance will be
+  used.
+
+- `aws_session_token` `(string: "")` - The AWS session token used to authenticate
+  with the AWS API.
+
+- `aws_credential_provider` `(string: "")` - The source of AWS credentials when
+  `aws_access_key_id` and `aws_secret_access_key` are not defined. If empty,
+  the [standard credential chain][aws_sdk_creds] will be followed. If set to
+  "ec2_role" credentials will be retrieved from the EC2 instance role.
+
+- `retry_attempts` `(int: "15")` - The number of attempts to make while waiting
+  for the cluster to stabilize after a scaling action. It may need to be tuned
+  up if errors such as `failed to ensure all activities completed` occur.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. It may be overridden per policy.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "aws-asg" {
+    aws_asg_name        = "hashistack-client-asg"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `aws_asg_name` `(string: <required>)` - The name of the AWS AutoScaling Group to
+  interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+- `scale_in_protection` `(bool: false)` - If `true`, instances marked with
+  [scale-in protection][aws_scale_in_protection] are not considered for
+  removal. If set, it overrides the plugin configuration.
+
+[aws_autoscaling]: https://aws.amazon.com/autoscaling/
+[aws_region]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
+[aws_scale_in_protection]: https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_aws_backend]: /vault/docs/secrets/aws
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
new file mode 100644
index 0000000000..c5960ea9be
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/azure-vmss.mdx
@@ -0,0 +1,137 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Azure VMSS'
+description: The "azure-vmss" target plugin scales an Azure Virtual Machine Scale Set.
+---
+
+# Azure Virtual Machine Scale Set Target
+
+The `azure-vmss` target plugin allows for the scaling of the Nomad cluster
+clients via manipulating [Azure Virtual Machine Scale
+Sets][azure_virtual_machine_scale_sets].
+
+## Agent Configuration Options
+
+To use the `azure-vmss` target plugin, the agent configuration needs to be
+populated with the appropriate target block. Authentication to the Azure API
+can be supplied in a number of ways.
+
+### Virtual Machine Identities
+
+When using [virtual machine identities][azure_vm_identity] you will need to
+provide a user-managed identity with the `Contributor` role and set the
+`subscription_id` in the Autoscaler configuration file:
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    subscription_id = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+### Configuration file
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+It is recommended, if possible to use the [Vault Azure Secrets
+engine][vault_azure_backend] for supplying access credentials to the plugin.
+
+```hcl
+target "azure-vmss" {
+  driver = "azure-vmss"
+  config = {
+    tenant_id         = "02e99e69-91b0-4d0a-bd61-bf5c08fbfbab"
+    client_id         = "34c276fa-2a74-4cf9-9fce-4e60642274cb"
+    secret_access_key = "ThisIrznTIS_~FAKEj4X93FTyAgilUC511"
+    subscription_id   = "ee0886ab-5cc2-4583-a3f0-c4bfd044ee82"
+  }
+}
+```
+
+- `tenant_id` `(string: "")` - The ID of the tenant to authenticate to.
+
+- `client_id` `(string: "")` - The app ID of the user-assigned identity in
+  Azure Active Directory.
+
+- `secret_access_key` `(string: "")` - The secret key ID used to authenticate
+  with the Azure API.
+
+- `subscription_id` `(string: "")` - The ID of the subscription to authenticate
+  to.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL
+token which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "clients-azure-vmss" {
+  # ...
+  target "azure-vmss" {
+    resource_group      = "prod"
+    vm_scale_set        = "hashistack-client-set"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+
+```
+
+- `resource_group` `(string: <required>)` - The name of the [Azure resource
+  group][azure_resource_group] within which the virtual machine scale set
+  resides.
+
+- `vm_scale_set` `(string: <required>)` - The name of the Azure virtual machine
+  scale set to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[azure_instance_metadata]: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service
+[azure_resource_group]: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal#what-is-a-resource-group
+[azure_virtual_machine_scale_sets]: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview
+[azure_vm_identity]: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/
+[client_meta_tag]: #client-meta-tag
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_client_meta_tag]: /nomad/docs/configuration/client#meta
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[vault_azure_backend]: /vault/docs/secrets/azure
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/gce-mig.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
new file mode 100644
index 0000000000..0d4f106125
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/gce-mig.mdx
@@ -0,0 +1,114 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: GCE MIG'
+description: The "gcp-mig" target plugin scales a Google Cloud Engine Managed Instance Group.
+---
+
+# Google Cloud Engine Managed Instance Groups Target
+
+The `gce-mig` target plugin allows for the scaling of the Nomad cluster clients
+via manipulating [Google Cloud Engine Managed Instance Groups][gce_migs]. The
+plugin supports both regional and zonal groups.
+
+## Agent Configuration Options
+
+The plugin uses the official Google Cloud Golang SDK. This means it supports
+the common ways of [providing credentials to Google Cloud][gcp_credentials].
+
+It is recommended, if possible to use the [Vault GCP Secrets
+engine][vault_gcp_backend] for supplying access credentials to the plugin.
+
+Credentials should be injected into the configuration via a template rather
+than as environment variables. This ensures the credentials are passed only to
+the plugin, rather than being available for all plugins and the agent process.
+
+```hcl
+target "gce-mig" {
+  driver = "gce-mig"
+  config = {
+    credentials = "local/creds.json"
+  }
+}
+```
+
+- `credentials` `(string: "")` - This is specified as the path to a Google Cloud
+  credentials file, typically for a service account.
+
+### Nomad ACL
+
+When using a Nomad cluster with ACLs enabled, the plugin will require an ACL token
+which provides the following permissions:
+
+```hcl
+node {
+  policy = "write"
+}
+```
+
+## Policy Configuration Options
+
+```hcl
+check "hashistack-allocated-cpu" {
+  # ...
+  target "gce-mig" {
+    project             = "hashistack-demo"
+    region              = "us-west1"
+    mig_name            = "nomad-client-hashistack"
+    node_class          = "hashistack"
+    node_drain_deadline = "5m"
+    node_purge          = "true"
+  }
+  # ...
+}
+```
+
+- `project` `(string: <required>)` - The [Google Cloud Platform project
+  ID][gcp_projects] within which the managed instance group is running.
+
+- `region` `(string: "")` - The GCP region where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is regional. Conflicts
+  with `zone`.
+
+- `zone` `(string: "")` - The GCP zone where the Managed Instance Group
+  resides. Providing this parameter indicates the MIG is zonal. Conflicts with
+  `region`.
+
+- `mig_name` `(string: <required>)` - The name of the GCE Managed Instance
+  Group to interact with when performing scaling actions.
+
+- `datacenter` `(string: "")` - The Nomad client [datacenter][nomad_datacenter]
+  identifier used to group nodes into a pool of resource.
+
+- `node_class` `(string: "")` - The Nomad [client node class][nomad_node_class]
+  identifier used to group nodes into a pool of resource.
+
+- `node_pool` `(string: "")` - The Nomad [client node pool][nomad_node_pool]
+  identifier used to group nodes into a pool of resource.
+
+- `node_drain_deadline` `(duration: "15m")` The Nomad [drain
+  deadline][nomad_node_drain_deadline] to use when performing node draining
+  actions. **Note that the default value for this setting differs from Nomad's
+  default of 1h.**
+
+- `node_drain_ignore_system_jobs` `(bool: "false")` A boolean flag used to
+  control if system jobs should be stopped when performing node draining
+  actions.
+
+- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad
+  clients should be [purged][nomad_node_purge] when performing scale in
+  actions.
+
+- `node_selector_strategy` `(string: "least_busy")` The strategy to use when
+  selecting nodes for termination. Refer to the [node selector
+  strategy][node_selector_strategy] documentation for more information.
+
+[gcp_credentials]: https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application
+[gcp_projects]: https://cloud.google.com/resource-manager/docs/creating-managing-projects
+[gce_migs]: https://cloud.google.com/compute/docs/instance-groups/
+[nomad_datacenter]: /nomad/docs/configuration#datacenter
+[nomad_node_class]: /nomad/docs/configuration/client#node_class
+[nomad_node_pool]: /nomad/docs/configuration/client#node_pool
+[nomad_node_drain_deadline]: /nomad/api-docs/nodes#deadline
+[nomad_node_purge]: /nomad/api-docs/nodes#purge-node
+[node_selector_strategy]: /nomad/tools/autoscaling/internals/node-selector-strategy
+[vault_gcp_backend]: /vault/docs/secrets/gcp
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/index.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/index.mdx
new file mode 100644
index 0000000000..a864bc24f0
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Target'
+description: Target plugins determine where the resource to be autoscaled is located.
+---
+
+# Target Plugins
+
+Target plugins determine where the resource to be autoscaled is located and
+execute the scaling actions determined by the Autoscaler.
+
+The target can be a group of a Nomad job (in which case, the scaling type is
+called horizontal application scaling), the number of Nomad clients (horizontal
+cluster scaling), or the amount of resources assigned to a task of a Nomad job
+(vertical application scaling).
+
+## Common Policy Configuration Options
+
+All target plugins support the following policy config parameters.
+
+- `dry-run` `(bool: false)` - If set to `true`, the target will not be scaled
+  and the proposed scaling action will only be logged.
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/nomad.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/nomad.mdx
new file mode 100644
index 0000000000..9b58db02e7
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/plugins/target/nomad.mdx
@@ -0,0 +1,53 @@
+---
+layout: docs
+page_title: 'Autoscaling Plugins: Nomad'
+description: The "nomad-target" target plugin scales a task group count.
+---
+
+# Nomad Task Group Target
+
+The Nomad task group target indicates the scalable resource is a Nomad job
+running on a Nomad cluster.
+
+## Agent Configuration Options
+
+The Nomad target is automatically launched by the Nomad Autoscaler and so the
+following setup is optional.
+
+```hcl
+target "nomad" {
+  driver = "nomad-target"
+}
+```
+
+## Policy Configuration Options
+
+If using the [Nomad job specification scaling block][nomad_scaling_block] to
+configure the scaling policy, the following section can be omitted as Nomad will
+populate them on job submission.
+
+```hcl
+check "example-check" {
+  ...
+  target "nomad" {
+    Namespace = "default"
+    Job       = "example"
+    Group     = "cache"
+  }
+  ...
+```
+
+- `Namespace` `(string: "")` - The namespace in which the job resides as defined
+  by the [`namespace` parameter][nomad_namespace_parameter] within the job
+  specification.
+
+- `Job` `(string: "")` - The job identifier which contains the task group to
+  scale as defined within the job specification [`job` block][nomad_job_block].
+
+- `Group` `(string: "")` - The name of the task group to scale as defined in the
+  job specification [`group` block][nomad_group_block].
+
+[nomad_job_block]: /nomad/docs/job-specification/job#job-block
+[nomad_group_block]: /nomad/docs/job-specification/group#group-block
+[nomad_namespace_parameter]: /nomad/docs/job-specification/job#namespace
+[nomad_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/policy.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/policy.mdx
new file mode 100644
index 0000000000..77fab0bae8
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/policy.mdx
@@ -0,0 +1,258 @@
+---
+layout: docs
+page_title: Scaling Policies
+description: >
+  Scaling policies describe the target resource desired state and how to
+  perform calculations to ensure the current state reaches the desired.
+---
+
+# Nomad Autoscaler Scaling Policies
+
+Nomad Autoscaler scaling policies can be configured via the [`scaling` block][jobspec_scaling_block]
+or by configuration files stored on disk. The options available differ whether
+you are performing horizontal application/cluster scaling or Dynamic Application
+Sizing.
+
+## Top Level Options
+
+- `enabled` - A boolean flag that allows operators to administratively disable a
+  policy from active evaluation.
+
+- `min` - The minimum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+- `max` - The maximum running count of the targeted resource. This can be 0 or any
+  positive integer.
+
+## Task Group and Cluster Scaling `policy` Options
+
+The following options are available when using the Nomad Autoscaler to perform
+horizontal application scaling or horizontal cluster scaling.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `on_check_error` - Defines how to handle errors during check evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop if any [`check`](#check) returns an error and no
+  scaling action will take place. If set to `"ignore"` any errors returned by a
+  `check` will be ignored when computing the scaling action. This value may be
+  overridden individually by setting [`on_error`](#on_error). Defaults to
+  `"ignore"`.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one or more checks to be executed when determining if a
+  scaling action is required.
+
+## `check` Options
+
+- `source` - The APM plugin that should handle the metric query. If omitted,
+  this defaults to using the Nomad APM.
+
+- `query` - The query to run against the specified APM. Currently this query
+  should return a single value. Detailed information on the configuration options
+  can be found on the [APM Plugins][apm_plugin_docs] page.
+
+- `query_window` - Defines how far back to query the APM for metrics. It should
+  be provided as a duration (e.g.: `"5s"`, `"1m"`). Defaults to `1m`. This
+  value may not be supported by all APM plugins. Refer to the documentation of
+  the specific APM plugin being used for more information.
+
+- `query_window_offset` - Defines a time offset from the current time to apply
+  to the query window. A short offset (for example, `1m`) can be used to avoid
+  reading unstable and incomplete data from the APM. A long offset (`168h`,
+  representing 7 days ago) can be used for predictive scaling based on past
+  data.
+
+- `group` - Specifies which checks should treated as correlated when the policy
+  is evaluated. Refer to [Check Grouping][concepts_grouping] for more
+  information.
+
+- `on_error` - Defines how to handle errors during the `check` evaluation.
+  Possible values are `"fail"` or `"ignore"`. If set to `"fail"` the policy
+  evaluation will stop in case an error occurs and not scaling action will take
+  place. If set to `"ignore"` the result of this `check` will not be taken into
+  considation when computing the scaling action. If not set the value of
+  [`on_check_error`](#on_check_error) will be used.
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current count and the metric returned by the APM.
+  Detailed information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Strategies for
+  [Dynamic Application Sizing][das] are not allowed in this case.
+
+### Example in a Job
+
+A full example of a policy document that can be written into the Nomad task group
+`scaling` block can be seen below.
+
+```hcl
+job "example" {
+  group "app" {
+    scaling {
+      min     = 2
+      max     = 10
+      enabled = true
+
+      policy {
+        evaluation_interval = "5s"
+        cooldown            = "1m"
+
+        check "active_connections" {
+          source = "prometheus"
+          query  = "scalar(open_connections_example_cache)"
+
+          strategy "target-value" {
+            target = 10
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Example in a File
+
+An example of a policy document that can be placed in a file within the
+`policy_dir` can be seen below. Multiple policies can be defined in the same
+file using multiple `scaling` blocks.
+
+```hcl
+scaling "aws_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    cooldown            = "2m"
+    evaluation_interval = "1m"
+
+    check "cpu_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    check "mem_allocated_percentage" {
+      source = "prometheus"
+      query  = "..."
+
+      strategy "target-value" {
+        target = 70
+      }
+    }
+
+    target "aws-asg" {
+      dry-run             = "false"
+      aws_asg_name        = "hashistack-nomad_client"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+
+scaling "azure_cluster_policy" {
+  enabled = true
+  min     = 1
+  max     = 2
+
+  policy {
+    ...
+    target "azure-vmss" {
+      resource_group      = "hashistack"
+      vm_scale_set        = "clients"
+      node_class          = "hashistack"
+      node_drain_deadline = "5m"
+    }
+  }
+}
+```
+
+## Task (DAS) `policy` Options
+
+<EnterpriseAlert>
+  This functionality only exists in Nomad Autoscaler Enterprise. This is not
+  present in the open source version of Nomad Autoscaler.
+</EnterpriseAlert>
+
+The following options are available when using the Nomad Autoscaler Enterprise
+to perform Dynamic Application Sizing recommendations for task resources. When
+using the [`scaling` block][jobspec_scaling_block] for Dynamic Application
+Sizing, the block requires a label to identify which resource it relates to. It
+currently supports `cpu` and `mem` labels, examples of which can be seen below.
+
+- `cooldown` - A time interval after a scaling action during which no additional
+  scaling will be performed on the resource. It should be provided as a duration
+  (e.g.: `"5s"`, `"1m"`). If omitted the configuration value
+  [policy_default_cooldown][policy_default_cooldown_agent] from the agent will
+  be used.
+
+- `evaluation_interval` - Defines how often the policy is evaluated by the
+  Autoscaler. It should be provided as a duration (e.g.: `"5s"`, `"1m"`). If
+  omitted the configuration value [default_evaluation_interval][eval_interval_agent]
+  from the agent will be used.
+
+- `target` - Defines where the autoscaling target is running. Detailed information
+  on the configuration options can be found on the [Target Plugins][target_plugin_docs]
+  page.
+
+- `check` - Specifies one check to be executed when determining if a recommendation
+  is required. Only one check is permitted per scaling block within Dynamic
+  Application Sizing.
+
+## `check` Options
+
+- `strategy` - The strategy to use, and it's configuration when calculating the
+  desired state based on the current value and the available historic data. Detailed
+  information on the configuration options can be found on the
+  [Strategy Plugins][strategy_plugin_docs] page. Only [Dynamic Application Sizing][das]
+  strategies are allowed.
+
+### Example
+
+The following examples are minimal blocks which can be used to configure CPU and
+Memory based sizing recommendations for a Nomad job task.
+
+```hcl
+scaling "cpu" {
+  policy {
+    check "96pct" {
+      strategy "app-sizing-percentile" {
+        percentile = "96"
+      }
+    }
+  }
+}
+
+scaling "mem" {
+  policy {
+    check "max" {
+      strategy "app-sizing-max" {}
+    }
+  }
+}
+```
+
+[concepts_grouping]: /nomad/tools/autoscaling/concepts/policy-eval/checks#check-grouping
+[das]: /nomad/tools/autoscaling#dynamic-application-sizing
+[policy_default_cooldown_agent]: /nomad/tools/autoscaling/agent#default_cooldown
+[eval_interval_agent]: /nomad/tools/autoscaling/agent#default_evaluation_interval
+[target_plugin_docs]: /nomad/tools/autoscaling/plugins/target
+[strategy_plugin_docs]: /nomad/tools/autoscaling/plugins/strategy
+[apm_plugin_docs]: /nomad/tools/autoscaling/plugins/apm
+[jobspec_scaling_block]: /nomad/docs/job-specification/scaling
diff --git a/content/nomad/v1.9.x/content/tools/autoscaling/telemetry.mdx b/content/nomad/v1.9.x/content/tools/autoscaling/telemetry.mdx
new file mode 100644
index 0000000000..52c484463c
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/autoscaling/telemetry.mdx
@@ -0,0 +1,271 @@
+---
+layout: docs
+page_title: Telemetry
+description: >
+  Overview of runtime metrics available in the Nomad Autoscaler.
+---
+
+# Nomad Autoscaler Telemetry
+
+The Nomad Autoscaler agent collects various runtime metrics about the performance
+of different libraries and subsystems. These metrics are aggregated on a ten
+second interval and are retained for one minute. To configure the telemetry output
+please see the [agent configuration][agent_telemetry_config].
+
+This data can be accessed via the `/v1/metrics` HTTP endpoint, via sending a
+signal to the Nomad Autoscaler process or via a number of integrations.
+
+To view this data via sending a signal to the Nomad Autoscaler process: on Unix,
+this is `USR1` while on Windows it is `BREAK`. Once Nomad Autoscaler receives
+the signal, it will dump the current telemetry information to the agent's `stderr`.
+
+This telemetry information can be used for debugging or otherwise
+getting a better view of what Nomad is doing.
+
+Below is sample output of a telemetry dump:
+
+```text
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 219856.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4316568.000
+[2020-08-25 10:01:20 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 36243.000
+[2020-08-25 10:01:20 +0100 BST][S] 'nomad-autoscaler.runtime.gc_pause_ns': Count: 5 Min: 38083.000 Mean: 69764.400 Max: 122291.000 Stddev: 31487.808 Sum: 348822.000 LastUpdated: 2020-08-25 10:01:26.574809 +0100 BST m=+1.241576679
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.alloc_bytes': 4370504.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.malloc_count': 220853.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.free_count': 183613.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.policy.total_num': 0.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.num_goroutines': 12.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_pause_ns': 348822.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.total_gc_runs': 5.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.sys_bytes': 74793216.000
+[2020-08-25 10:01:30 +0100 BST][G] 'nomad-autoscaler.pathfinder.runtime.heap_objects': 37240.000
+```
+
+## Runtime Metrics
+
+The runtime metrics help understand the Nomad Autoscaler agent's memory and load
+pressure performance.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.num_goroutines</code>
+      </td>
+      <td>Number of running goroutines</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.alloc_bytes</code>
+      </td>
+      <td>The number of allocated heap bytes</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.sys_bytes</code>
+      </td>
+      <td>The total bytes of memory obtained from the OS</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.malloc_count</code>
+      </td>
+      <td>Cumulative count of heap objects allocated</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.free_count</code>
+      </td>
+      <td>Cumulative count of heap objects freed</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.heap_objects</code>
+      </td>
+      <td>Number of allocated heap objects</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_pause_ns</code>
+      </td>
+      <td>Cumulative nanoseconds in GC stop-the-world pauses</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.total_gc_runs</code>
+      </td>
+      <td>Number of completed GC cycles</td>
+      <td>Gauge</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.runtime.gc_pause_ns</code>
+      </td>
+      <td>Number of nanoseconds to complete the last GC cycle</td>
+      <td>Timer</td>
+    </tr>
+  </tbody>
+</table>
+
+## Policy Metrics
+
+Policy metrics provide insights into the performance of the Nomad Autoscaler's
+policy handling.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.total_num</code>
+      </td>
+      <td>The number of policies currently held within the autoscaler</td>
+      <td>Gauge</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.policy.source.error_count</code>
+      </td>
+      <td>Tracks the number of errors generated by the policy sources</td>
+      <td>Counter</td>
+      <td>policy_source</td>
+    </tr>
+  </tbody>
+</table>
+
+## Scaling Metrics
+
+Scaling metrics provide insight into the performance of scaling actions as well
+as overall success and failure counters.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.evaluate_ms</code>
+      </td>
+      <td>The time taken to evaluate the checks within a single policy</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to invoke scaling based on the scaling evaluations</td>
+      <td>Timer</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.success_count</code>
+      </td>
+      <td>Tracks the number of successful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.scale.invoke.error_count</code>
+      </td>
+      <td>Tracks the number of unsuccessful scaling actions triggered</td>
+      <td>Counter</td>
+      <td>policy_id, target_name</td>
+    </tr>
+  </tbody>
+</table>
+
+## Plugin Metrics
+
+Plugin metrics provide insight into the performance of Nomad Autoscaler plugins
+and help identify potential bottle necks or latency issues.
+
+<table>
+  <thead>
+    <tr>
+      <th>Metric</th>
+      <th>Description</th>
+      <th>Type</th>
+      <th>Labels</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.plugin.manager.access_ms</code>
+      </td>
+      <td>The time taken to dispense a plugin</td>
+      <td>Timer</td>
+      <td></td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.status.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin status call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.target.scale.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the target plugin scale call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.apm.query.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the APM plugin query call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+    <tr>
+      <td>
+        <code>nomad-autoscaler.strategy.run.invoke_ms</code>
+      </td>
+      <td>The time taken to perform the strategy plugin run call</td>
+      <td>Timer</td>
+      <td>policy_id, plugin_name</td>
+    </tr>
+  </tbody>
+</table>
+
+[agent_telemetry_config]: /nomad/tools/autoscaling/agent#telemetry-block
diff --git a/content/nomad/v1.9.x/content/tools/index.mdx b/content/nomad/v1.9.x/content/tools/index.mdx
new file mode 100644
index 0000000000..f3de72863f
--- /dev/null
+++ b/content/nomad/v1.9.x/content/tools/index.mdx
@@ -0,0 +1,54 @@
+---
+layout: docs
+page_title: Tools
+description: Learn about tools for Nomad.
+---
+
+# Tools
+
+External tools provide additional capabilities and use cases to Nomad. They are
+installed separately from Nomad itself and can sometimes be deployed as a Nomad
+job in your cluster.
+
+## HashiCorp-Maintained Tools
+
+The following external tools are currently available for Nomad and maintained by HashiCorp:
+
+- [Autoscaling](/nomad/tools/autoscaling) - HashiCorp's official Nomad Autoscaler. Supports scaling allocations within Nomad and scaling nodes on AWS, Azure, GCP, or arbitrary infrastructure via plugins.
+- [Damon](https://github.com/hashicorp/damon) - A terminal dashboard for Nomad.
+- [Levant](https://github.com/hashicorp/levant) - A templating and deployment tool for HashiCorp Nomad jobs that provides realtime feedback and detailed failure messages upon deployment issues.
+- [Nomad Pack](https://github.com/hashicorp/nomad-pack) - An official package manager and templating tool for Nomad, currently a Tech Preview.
+- [Nomad Pack GitHub Action](https://github.com/marketplace/actions/setup-hashicorp-nomad-pack) - A GitHub Action for Nomad Pack.
+
+## Community Tools
+
+The following external tools are currently available for Nomad and maintained by members of the Nomad Community:
+
+- [Caravan](https://caravanproject.io/) - Caravan is a tool to deploy and configure Nomad, Consul and Vault to AWS, Azure, or GCP, all with a single script.
+- [Chaotic](https://github.com/ngine-io/chaotic) - A Chaos Engineering tool to stop allocations, reboot or stop/start virtual machines in your cloud environment
+- [Deadman Check](https://github.com/sepulworld/deadman-check) - A monitoring companion for Nomad periodic jobs that alerts if periodic isn't running at the expected interval
+- [Hashi Up](https://github.com/jsiebens/hashi-up) - A utility to install Nomad on remote Linux hosts
+- [HashiBox](https://github.com/nunchistudio/hashibox) - Vagrant environment to simulate a highly-available cloud with Consul, Vault, and Nomad.
+- [Jenkins Nomad Cloud Plugin](https://github.com/jenkinsci/nomad-plugin) - A Jenkins plugin using Nomad to provision build workers
+- [Kreconciler](https://github.com/koyeb/kreconciler) - A library to build control-loops for things on Nomad (or other schedulers)
+- [Nelson](https://getnelson.io/) - A tool for automated, multi-region container deployment using Nomad
+- [Node Problem Detector](https://github.com/Roblox/nomad-node-problem-detector) - A tool used to detect problems on Nomad nodes based on user-defined health checks
+- [Nomad Admission Control Proxy](https://github.com/mxab/nacp) - A Nomad Proxy that mutates and validates job data on the fly via embedded OPA rules or remote webhooks.
+- [Nomadctx](https://github.com/mr-karan/nomctx) - A faster way to switch between clusters and namespaces in nomad
+- [Nomad deploy result action](https://github.com/let-sh/nomad-deploy-result-action) - A Github action to monitor deployment results
+- [Nomad events sink](https://github.com/mr-karan/nomad-events-sink) - An events collection agent which processes Nomad Events and dumps to external sink providers like HTTP
+- [Nomad External DNS](https://github.com/mr-karan/nomad-external-dns/) - Set external DNS records for Nomad services
+- [Nomad Firehose](https://github.com/seatgeek/nomad-firehose) - A tool to enable teams to quickly build logic around nomad task events without hooking into Nomad API
+- [Nomad Helper](https://github.com/seatgeek/nomad-helper) - A Nomad helper binary. Reevaluate jobs, force garbage collection, drain nodes, export/import count information
+- [Nomad Monitoring](https://github.com/mr-karan/nomad-monitoring) -  Collection of jobspecs and Grafana dashboards for end to end monitoring of Nomad clusters
+- [Nomad Ops](https://nomad-ops.github.io/nomad-ops) - A simple operator for Nomad which reconciles the running jobs in comparison to git repos
+- [Nomad Pipeline](https://github.com/HyperBadger/nomad-pipeline) - A tool to make running pipeline-style workloads on Nomad
+- [Nomad Port Forward](https://github.com/Mongey/nomad-port-forward) - A tool for forwarding ports from a Nomad job to your local machine
+- [Nomad Toast](https://github.com/jrasell/nomad-toast) - A tool for receiving notifications based on HashiCorp Nomad events
+- [Nomad Tools](https://github.com/Kamilcuk/nomad-tools) - Set of tools and utilities to ease interacting with HashiCorp Nomad scheduling solution.
+- [Nomad Vector Logger](https://github.com/mr-karan/nomad-vector-logger) -  A daemon which continuously watches jobs running in a Nomad cluster and templates out a Vector configuration file which can be used to collect application logs enriched with Nomad metadata. 
+- [Nomad Watcher](https://github.com/blalor/nomad-watcher) - A simple service that watches Nomad's nodes, jobs, deployments, evaluations, allocations, and task states, and writes the events to a file
+- [Nomadgen](https://github.com/smintz/nomadgen) - Craft your Hashicorp's Nomad job specs in python.
+- [Nomadctld](https://github.com/42wim/nomadctld) - An ssh server that sits between users and the nomad cluster allowing for limited access to your nomad cluster and allow them to attach, see logs, tail logs, stop, restart, exec containers they own on the cluster
+- [Nomad-spk](https://github.com/numkem/nomad-spk) - A tool to install nomad into a Synology NAS
+- [Wander](https://github.com/robinovitch61/wander) - A terminal application for Nomad by HashiCorp
diff --git a/content/nomad/v1.9.x/data/api-docs-nav-data.json b/content/nomad/v1.9.x/data/api-docs-nav-data.json
new file mode 100644
index 0000000000..e89bec40ac
--- /dev/null
+++ b/content/nomad/v1.9.x/data/api-docs-nav-data.json
@@ -0,0 +1,211 @@
+[
+  {
+    "title": "HTTP API Overview",
+    "path": "index"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Libraries &amp; SDKs",
+    "path": "libraries-and-sdks"
+  },
+  {
+    "title": "JSON Jobs",
+    "path": "json-jobs"
+  },
+  {
+    "title": "Task API",
+    "path": "task-api"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "ACL",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "acl"
+      },
+      {
+        "title": "Auth Methods",
+        "path": "acl/auth-methods"
+      },
+      {
+        "title": "Binding Rules",
+        "path": "acl/binding-rules"
+      },
+      {
+        "title": "Login",
+        "path": "acl/login"
+      },
+      {
+        "title": "OIDC",
+        "path": "acl/oidc"
+      },
+      {
+        "title": "Policies",
+        "path": "acl/policies"
+      },
+      {
+        "title": "Roles",
+        "path": "acl/roles"
+      },
+      {
+        "title": "Tokens",
+        "path": "acl/tokens"
+      }
+    ]
+  },
+  {
+    "title": "Agent",
+    "path": "agent"
+  },
+  {
+    "title": "Allocations",
+    "path": "allocations"
+  },
+  {
+    "title": "Client",
+    "path": "client"
+  },
+  {
+    "title": "Deployments",
+    "path": "deployments"
+  },
+  {
+    "title": "Evaluations",
+    "path": "evaluations"
+  },
+  {
+    "title": "Events",
+    "path": "events"
+  },
+  {
+    "title": "Jobs",
+    "path": "jobs"
+  },
+  {
+    "title": "Namespaces",
+    "path": "namespaces"
+  },
+  {
+    "title": "Nodes",
+    "path": "nodes"
+  },
+  {
+    "title": "Node Pools",
+    "path": "node-pools"
+  },
+  {
+    "title": "Metrics",
+    "path": "metrics"
+  },
+  {
+    "title": "Operator",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operator"
+      },
+      {
+        "title": "Autopilot",
+        "path": "operator/autopilot"
+      },
+      {
+        "title": "Keyring",
+        "path": "operator/keyring"
+      },
+      {
+        "title": "License",
+        "path": "operator/license"
+      },
+      {
+        "title": "Raft",
+        "path": "operator/raft"
+      },
+      {
+        "title": "Scheduler",
+        "path": "operator/scheduler"
+      },
+      {
+        "title": "Snapshot",
+        "path": "operator/snapshot"
+      },
+      {
+        "title": "Upgrade Check",
+        "path": "operator/upgrade-check"
+      }
+    ]
+  },
+  {
+    "title": "Plugins",
+    "path": "plugins"
+  },
+  {
+    "title": "Quotas",
+    "path": "quotas"
+  },
+  {
+    "title": "Recommendations",
+    "path": "recommendations"
+  },
+  {
+    "title": "Regions",
+    "path": "regions"
+  },
+  {
+    "title": "Scaling Policies",
+    "path": "scaling-policies"
+  },
+  {
+    "title": "Search",
+    "path": "search"
+  },
+  {
+    "title": "Sentinel Policies",
+    "path": "sentinel-policies"
+  },
+  {
+    "title": "Services",
+    "path": "services"
+  },
+  {
+    "title": "Status",
+    "path": "status"
+  },
+  {
+    "title": "System",
+    "path": "system"
+  },
+  {
+    "title": "UI",
+    "path": "ui"
+  },
+  {
+    "title": "Validate",
+    "path": "validate"
+  },
+  {
+    "title": "Variables",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "variables"
+      },
+      {
+        "title": "Variables",
+        "path": "variables/variables"
+      },
+      {
+        "title": "Locks",
+        "path": "variables/locks"
+      }
+    ]
+  },
+  {
+    "title": "Volumes",
+    "path": "volumes"
+  }
+]
diff --git a/content/nomad/v1.9.x/data/docs-nav-data.json b/content/nomad/v1.9.x/data/docs-nav-data.json
new file mode 100644
index 0000000000..51529ae7df
--- /dev/null
+++ b/content/nomad/v1.9.x/data/docs-nav-data.json
@@ -0,0 +1,2424 @@
+[
+  {
+    "title": "Install Nomad",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "install"
+      },
+      {
+        "title": "Quickstart",
+        "path": "install/quickstart"
+      },
+      {
+        "title": "Production",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "install/production"
+          },
+          {
+            "title": "Requirements",
+            "path": "install/production/requirements"
+          },
+          {
+            "title": "Reference Architecture",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-reference-architecture-vm-with-consul"
+          },
+          {
+            "title": "Deployment Guide",
+            "href": "https://learn.hashicorp.com/tutorials/nomad/production-deployment-guide-vm-with-consul"
+          }
+        ]
+      },
+      {
+        "title": "Windows Service",
+        "path": "install/windows-service"
+      }
+    ]
+  },
+  {
+    "title": "Upgrading",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "upgrade"
+      },
+      {
+        "title": "Specific Version Details",
+        "path": "upgrade/upgrade-specific"
+      }
+    ]
+  },
+  {
+    "title": "Release Notes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "release-notes"
+      },
+      {
+        "title": "Nomad",
+        "routes": [
+          {
+            "title": "Upcoming",
+            "path": "release-notes/nomad/upcoming"
+          },
+          {
+            "title": "v1.8.x",
+            "path": "release-notes/nomad/v1_8_x"
+          },
+          {
+            "title": "v1.9.x",
+            "path": "release-notes/nomad/v1_9_x"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Integrations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "integrations"
+      },
+      {
+        "title": "Consul",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/consul"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/consul/acl"
+          },
+          {
+            "title": "Service Mesh",
+            "path": "integrations/consul/service-mesh"
+          }
+        ]
+      },
+      {
+        "title": "Vault",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "integrations/vault"
+          },
+          {
+            "title": "ACL",
+            "path": "integrations/vault/acl"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Concepts",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "concepts"
+      },
+      {
+        "title": "ACL",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/acl"
+          },
+          {
+            "title": "Auth Methods",
+            "routes": [
+              {
+                "title": "JWT",
+                "path": "concepts/acl/auth-methods/jwt"
+              },
+              {
+                "title": "OIDC",
+                "path": "concepts/acl/auth-methods/oidc"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Architecture",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/architecture"
+          },
+          {
+            "title": "Federation",
+            "path": "concepts/architecture/federation"
+          }
+        ]
+      },
+      {
+        "title": "CPU",
+        "path": "concepts/cpu"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/plugins"
+          },
+          {
+            "title": "Base",
+            "path": "concepts/plugins/base"
+          },
+          {
+            "title": "Task Drivers",
+            "path": "concepts/plugins/task-drivers"
+          },
+          {
+            "title": "Devices",
+            "path": "concepts/plugins/devices"
+          },
+          {
+            "title": "Storage",
+            "path": "concepts/plugins/csi"
+          },
+          {
+            "title": "Networking",
+            "path": "concepts/plugins/cni"
+          }
+        ]
+      },
+      {
+        "title": "Scheduling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "concepts/scheduling"
+          },
+          {
+            "title": "Concepts",
+            "path": "concepts/scheduling/scheduling"
+          },
+          {
+            "title": "Placement",
+            "path": "concepts/scheduling/placement"
+          },
+          {
+            "title": "Preemption",
+            "path": "concepts/scheduling/preemption"
+          }
+        ]
+      },
+      {
+        "title": "Consensus Protocol",
+        "path": "concepts/consensus"
+      },
+      {
+        "title": "Filesystem",
+        "path": "concepts/filesystem"
+      },
+      {
+        "title": "Gossip Protocol",
+        "path": "concepts/gossip"
+      },
+      {
+        "title": "Node Pools",
+        "path": "concepts/node-pools"
+      },
+      {
+        "title": "Security Model",
+        "path": "concepts/security"
+      },
+      {
+        "title": "Job",
+        "path": "concepts/job"
+      },
+      {
+        "title": "Workload Identity",
+        "path": "concepts/workload-identity"
+      },
+      {
+        "title": "Variables",
+        "path": "concepts/variables"
+      }
+    ]
+  },
+  {
+    "title": "Configuration",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "configuration"
+      },
+      {
+        "title": "acl",
+        "path": "configuration/acl"
+      },
+      {
+        "title": "audit",
+        "path": "configuration/audit"
+      },
+      {
+        "title": "autopilot",
+        "path": "configuration/autopilot"
+      },
+      {
+        "title": "client",
+        "path": "configuration/client"
+      },
+      {
+        "title": "consul",
+        "path": "configuration/consul"
+      },
+      {
+        "title": "keyring",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "configuration/keyring"
+          },
+          {
+            "title": "AWS KMS",
+            "path": "configuration/keyring/awskms"
+          },
+          {
+            "title": "Azure Key Vault",
+            "path": "configuration/keyring/azurekeyvault"
+          },
+          {
+            "title": "GCP Cloud KMS",
+            "path": "configuration/keyring/gcpckms"
+          },
+          {
+            "title": "Vault Transit",
+            "path": "configuration/keyring/transit"
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "path": "configuration/plugin"
+      },
+      {
+        "title": "reporting",
+        "path": "configuration/reporting"
+      },
+      {
+        "title": "search",
+        "path": "configuration/search"
+      },
+      {
+        "title": "sentinel",
+        "path": "configuration/sentinel"
+      },
+      {
+        "title": "server",
+        "path": "configuration/server"
+      },
+      {
+        "title": "server_join",
+        "path": "configuration/server_join"
+      },
+      {
+        "title": "telemetry",
+        "path": "configuration/telemetry"
+      },
+      {
+        "title": "tls",
+        "path": "configuration/tls"
+      },
+      {
+        "title": "ui",
+        "path": "configuration/ui"
+      },
+      {
+        "title": "vault",
+        "path": "configuration/vault"
+      }
+    ]
+  },
+  {
+    "title": "Commands (CLI)",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "commands"
+      },
+      {
+        "title": "acl",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/acl"
+          },
+          {
+            "title": "bootstrap",
+            "path": "commands/acl/bootstrap"
+          },
+          {
+            "title": "auth-method",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/auth-method/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/auth-method/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/auth-method/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/auth-method/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/auth-method/update"
+              }
+            ]
+          },
+          {
+            "title": "binding-rule",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/binding-rule/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/binding-rule/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/binding-rule/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/binding-rule/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/binding-rule/update"
+              }
+            ]
+          },
+          {
+            "title": "policy",
+            "routes": [
+              {
+                "title": "apply",
+                "path": "commands/acl/policy/apply"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/policy/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/policy/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/policy/list"
+              }
+            ]
+          },
+          {
+            "title": "role",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/role/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/role/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/role/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/role/list"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/role/update"
+              }
+            ]
+          },
+          {
+            "title": "token",
+            "routes": [
+              {
+                "title": "create",
+                "path": "commands/acl/token/create"
+              },
+              {
+                "title": "delete",
+                "path": "commands/acl/token/delete"
+              },
+              {
+                "title": "info",
+                "path": "commands/acl/token/info"
+              },
+              {
+                "title": "list",
+                "path": "commands/acl/token/list"
+              },
+              {
+                "title": "self",
+                "path": "commands/acl/token/self"
+              },
+              {
+                "title": "update",
+                "path": "commands/acl/token/update"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "agent",
+        "path": "commands/agent"
+      },
+      {
+        "title": "agent-info",
+        "path": "commands/agent-info"
+      },
+      {
+        "title": "alloc",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/alloc"
+          },
+          {
+            "title": "checks",
+            "path": "commands/alloc/checks"
+          },
+          {
+            "title": "exec",
+            "path": "commands/alloc/exec"
+          },
+          {
+            "title": "fs",
+            "path": "commands/alloc/fs"
+          },
+          {
+            "title": "logs",
+            "path": "commands/alloc/logs"
+          },
+          {
+            "title": "pause",
+            "path": "commands/alloc/pause"
+          },
+          {
+            "title": "restart",
+            "path": "commands/alloc/restart"
+          },
+          {
+            "title": "signal",
+            "path": "commands/alloc/signal"
+          },
+          {
+            "title": "status",
+            "path": "commands/alloc/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/alloc/stop"
+          }
+        ]
+      },
+      {
+        "title": "config",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/config"
+          },
+          {
+            "title": "validate",
+            "path": "commands/config/validate"
+          }
+        ]
+      },
+      {
+        "title": "deployment",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/deployment"
+          },
+          {
+            "title": "fail",
+            "path": "commands/deployment/fail"
+          },
+          {
+            "title": "list",
+            "path": "commands/deployment/list"
+          },
+          {
+            "title": "pause",
+            "path": "commands/deployment/pause"
+          },
+          {
+            "title": "promote",
+            "path": "commands/deployment/promote"
+          },
+          {
+            "title": "resume",
+            "path": "commands/deployment/resume"
+          },
+          {
+            "title": "status",
+            "path": "commands/deployment/status"
+          },
+          {
+            "title": "unblock",
+            "path": "commands/deployment/unblock"
+          }
+        ]
+      },
+      {
+        "title": "eval",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/eval"
+          },
+          {
+            "title": "delete",
+            "path": "commands/eval/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/eval/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/eval/status"
+          }
+        ]
+      },
+      {
+        "title": "fmt",
+        "path": "commands/fmt"
+      },
+      {
+        "title": "job",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/job"
+          },
+          {
+            "title": "action",
+            "path": "commands/job/action"
+          },
+          {
+            "title": "allocs",
+            "path": "commands/job/allocs"
+          },
+          {
+            "title": "deployments",
+            "path": "commands/job/deployments"
+          },
+          {
+            "title": "dispatch",
+            "path": "commands/job/dispatch"
+          },
+          {
+            "title": "eval",
+            "path": "commands/job/eval"
+          },
+          {
+            "title": "history",
+            "path": "commands/job/history"
+          },
+          {
+            "title": "init",
+            "path": "commands/job/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/job/inspect"
+          },
+          {
+            "title": "plan",
+            "path": "commands/job/plan"
+          },
+          {
+            "title": "periodic force",
+            "path": "commands/job/periodic-force"
+          },
+          {
+            "title": "promote",
+            "path": "commands/job/promote"
+          },
+          {
+            "title": "restart",
+            "path": "commands/job/restart"
+          },
+          {
+            "title": "revert",
+            "path": "commands/job/revert"
+          },
+          {
+            "title": "run",
+            "path": "commands/job/run"
+          },
+          {
+            "title": "scale",
+            "path": "commands/job/scale"
+          },
+          {
+            "title": "scaling-events",
+            "path": "commands/job/scaling-events"
+          },
+          {
+            "title": "status",
+            "path": "commands/job/status"
+          },
+          {
+            "title": "stop",
+            "path": "commands/job/stop"
+          },
+          {
+            "title": "tag",
+            "path": "commands/job/tag"
+          },
+          {
+            "title": "validate",
+            "path": "commands/job/validate"
+          }
+        ]
+      },
+      {
+        "title": "license",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/license"
+          },
+          {
+            "title": "get",
+            "path": "commands/license/get"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/license/inspect"
+          }
+        ]
+      },
+      {
+        "title": "login",
+        "path": "commands/login"
+      },
+      {
+        "title": "monitor",
+        "path": "commands/monitor"
+      },
+      {
+        "title": "namespace",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/namespace"
+          },
+          {
+            "title": "apply",
+            "path": "commands/namespace/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/namespace/delete"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/namespace/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/namespace/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/namespace/status"
+          }
+        ]
+      },
+      {
+        "title": "node",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node"
+          },
+          {
+            "title": "config",
+            "path": "commands/node/config"
+          },
+          {
+            "title": "drain",
+            "path": "commands/node/drain"
+          },
+          {
+            "title": "eligibility",
+            "path": "commands/node/eligibility"
+          },
+          {
+            "title": "meta",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "commands/node/meta"
+              },
+              {
+                "title": "apply",
+                "path": "commands/node/meta/apply"
+              },
+              {
+                "title": "read",
+                "path": "commands/node/meta/read"
+              }
+            ]
+          },
+          {
+            "title": "status",
+            "path": "commands/node/status"
+          }
+        ]
+      },
+      {
+        "title": "node pool",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/node-pool"
+          },
+          {
+            "title": "apply",
+            "path": "commands/node-pool/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/node-pool/delete"
+          },
+          {
+            "title": "info",
+            "path": "commands/node-pool/info"
+          },
+          {
+            "title": "init",
+            "path": "commands/node-pool/init"
+          },
+          {
+            "title": "jobs",
+            "path": "commands/node-pool/jobs"
+          },
+          {
+            "title": "list",
+            "path": "commands/node-pool/list"
+          },
+          {
+            "title": "nodes",
+            "path": "commands/node-pool/nodes"
+          }
+        ]
+      },
+      {
+        "title": "operator",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/operator"
+          },
+          {
+            "title": "api",
+            "path": "commands/operator/api"
+          },
+          {
+            "title": "autopilot",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/autopilot/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/autopilot/set-config"
+              },
+              {
+                "title": "health",
+                "path": "commands/operator/autopilot/health"
+              }
+            ]
+          },
+          {
+            "title": "client-state",
+            "path": "commands/operator/client-state"
+          },
+          {
+            "title": "debug",
+            "path": "commands/operator/debug"
+          },
+          {
+            "title": "gossip",
+            "routes": [
+              {
+                "title": "keyring generate",
+                "path": "commands/operator/gossip/keyring-generate"
+              },
+              {
+                "title": "keyring install",
+                "path": "commands/operator/gossip/keyring-install"
+              },
+              {
+                "title": "keyring list",
+                "path": "commands/operator/gossip/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/gossip/keyring-remove"
+              },
+              {
+                "title": "keyring use",
+                "path": "commands/operator/gossip/keyring-use"
+              }
+            ]
+          },
+          {
+            "title": "metrics",
+            "path": "commands/operator/metrics"
+          },
+          {
+            "title": "raft",
+            "routes": [
+              {
+                "title": "info",
+                "path": "commands/operator/raft/info"
+              },
+              {
+                "title": "list-peers",
+                "path": "commands/operator/raft/list-peers"
+              },
+              {
+                "title": "logs",
+                "path": "commands/operator/raft/logs"
+              },
+              {
+                "title": "remove-peer",
+                "path": "commands/operator/raft/remove-peer"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/raft/state"
+              },
+              {
+                "title": "transfer-leadership",
+                "path": "commands/operator/raft/transfer-leadership"
+              }
+            ]
+          },
+          {
+            "title": "root",
+            "routes": [
+              {
+                "title": "keyring list",
+                "path": "commands/operator/root/keyring-list"
+              },
+              {
+                "title": "keyring remove",
+                "path": "commands/operator/root/keyring-remove"
+              },
+              {
+                "title": "keyring rotate",
+                "path": "commands/operator/root/keyring-rotate"
+              }
+            ]
+          },
+          {
+            "title": "scheduler",
+            "routes": [
+              {
+                "title": "get-config",
+                "path": "commands/operator/scheduler/get-config"
+              },
+              {
+                "title": "set-config",
+                "path": "commands/operator/scheduler/set-config"
+              }
+            ]
+          },
+          {
+            "title": "snapshot",
+            "routes": [
+              {
+                "title": "agent",
+                "path": "commands/operator/snapshot/agent"
+              },
+              {
+                "title": "inspect",
+                "path": "commands/operator/snapshot/inspect"
+              },
+              {
+                "title": "redact",
+                "path": "commands/operator/snapshot/redact"
+              },
+              {
+                "title": "restore",
+                "path": "commands/operator/snapshot/restore"
+              },
+              {
+                "title": "save",
+                "path": "commands/operator/snapshot/save"
+              },
+              {
+                "title": "state",
+                "path": "commands/operator/snapshot/state"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "plugin",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/plugin"
+          },
+          {
+            "title": "status",
+            "path": "commands/plugin/status"
+          }
+        ]
+      },
+      {
+        "title": "quota",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/quota"
+          },
+          {
+            "title": "apply",
+            "path": "commands/quota/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/quota/delete"
+          },
+          {
+            "title": "init",
+            "path": "commands/quota/init"
+          },
+          {
+            "title": "inspect",
+            "path": "commands/quota/inspect"
+          },
+          {
+            "title": "list",
+            "path": "commands/quota/list"
+          },
+          {
+            "title": "status",
+            "path": "commands/quota/status"
+          }
+        ]
+      },
+      {
+        "title": "recommendation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/recommendation"
+          },
+          {
+            "title": "apply",
+            "path": "commands/recommendation/apply"
+          },
+          {
+            "title": "dismiss",
+            "path": "commands/recommendation/dismiss"
+          },
+          {
+            "title": "info",
+            "path": "commands/recommendation/info"
+          },
+          {
+            "title": "list",
+            "path": "commands/recommendation/list"
+          }
+        ]
+      },
+      {
+        "title": "setup",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/setup"
+          },
+          {
+            "title": "consul",
+            "path": "commands/setup/consul"
+          },
+          {
+            "title": "vault",
+            "path": "commands/setup/vault"
+          }
+        ]
+      },
+      {
+        "title": "scaling",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/scaling"
+          },
+          {
+            "title": "policy info",
+            "path": "commands/scaling/policy-info"
+          },
+          {
+            "title": "policy list",
+            "path": "commands/scaling/policy-list"
+          }
+        ]
+      },
+      {
+        "title": "sentinel",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/sentinel"
+          },
+          {
+            "title": "apply",
+            "path": "commands/sentinel/apply"
+          },
+          {
+            "title": "delete",
+            "path": "commands/sentinel/delete"
+          },
+          {
+            "title": "list",
+            "path": "commands/sentinel/list"
+          },
+          {
+            "title": "read",
+            "path": "commands/sentinel/read"
+          }
+        ]
+      },
+      {
+        "title": "server",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/server"
+          },
+          {
+            "title": "force-leave",
+            "path": "commands/server/force-leave"
+          },
+          {
+            "title": "join",
+            "path": "commands/server/join"
+          },
+          {
+            "title": "members",
+            "path": "commands/server/members"
+          }
+        ]
+      },
+      {
+        "title": "service",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/service"
+          },
+          {
+            "title": "service delete",
+            "path": "commands/service/delete"
+          },
+          {
+            "title": "service info",
+            "path": "commands/service/info"
+          },
+          {
+            "title": "service list",
+            "path": "commands/service/list"
+          }
+        ]
+      },
+      {
+        "title": "status",
+        "path": "commands/status"
+      },
+      {
+        "title": "system",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/system"
+          },
+          {
+            "title": "gc",
+            "path": "commands/system/gc"
+          },
+          {
+            "title": "reconcile summaries",
+            "path": "commands/system/reconcile-summaries"
+          }
+        ]
+      },
+      {
+        "title": "tls",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/tls"
+          },
+          {
+            "title": "ca create",
+            "path": "commands/tls/ca-create"
+          },
+          {
+            "title": "ca info",
+            "path": "commands/tls/ca-info"
+          },
+          {
+            "title": "cert create",
+            "path": "commands/tls/cert-create"
+          },
+          {
+            "title": "cert info",
+            "path": "commands/tls/cert-info"
+          }
+        ]
+      },
+      {
+        "title": "ui",
+        "path": "commands/ui"
+      },
+      {
+        "title": "var",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/var"
+          },
+          {
+            "title": "get",
+            "path": "commands/var/get"
+          },
+          {
+            "title": "init",
+            "path": "commands/var/init"
+          },
+          {
+            "title": "list",
+            "path": "commands/var/list"
+          },
+          {
+            "title": "put",
+            "path": "commands/var/put"
+          },
+          {
+            "title": "lock",
+            "path": "commands/var/lock"
+          },
+          {
+            "title": "purge",
+            "path": "commands/var/purge"
+          }
+        ]
+      },
+      {
+        "title": "version",
+        "path": "commands/version"
+      },
+      {
+        "title": "volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "commands/volume"
+          },
+          {
+            "title": "create",
+            "path": "commands/volume/create"
+          },
+          {
+            "title": "delete",
+            "path": "commands/volume/delete"
+          },
+          {
+            "title": "deregister",
+            "path": "commands/volume/deregister"
+          },
+          {
+            "title": "detach",
+            "path": "commands/volume/detach"
+          },
+          {
+            "title": "init",
+            "path": "commands/volume/init"
+          },
+          {
+            "title": "register",
+            "path": "commands/volume/register"
+          },
+          {
+            "title": "snapshot create",
+            "path": "commands/volume/snapshot-create"
+          },
+          {
+            "title": "snapshot delete",
+            "path": "commands/volume/snapshot-delete"
+          },
+          {
+            "title": "snapshot list",
+            "path": "commands/volume/snapshot-list"
+          },
+          {
+            "title": "status",
+            "path": "commands/volume/status"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Glossary",
+    "path": "glossary"
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Job Specification",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "job-specification"
+      },
+      {
+        "title": "HCL2",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "job-specification/hcl2"
+          },
+          {
+            "title": "Expressions",
+            "path": "job-specification/hcl2/expressions"
+          },
+          {
+            "title": "Functions",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "job-specification/hcl2/functions"
+              },
+              {
+                "title": "Collection Functions",
+                "routes": [
+                  {
+                    "title": "chunklist",
+                    "path": "job-specification/hcl2/functions/collection/chunklist"
+                  },
+                  {
+                    "title": "coalesce",
+                    "path": "job-specification/hcl2/functions/collection/coalesce"
+                  },
+                  {
+                    "title": "coalescelist",
+                    "path": "job-specification/hcl2/functions/collection/coalescelist"
+                  },
+                  {
+                    "title": "compact",
+                    "path": "job-specification/hcl2/functions/collection/compact"
+                  },
+                  {
+                    "title": "concat",
+                    "path": "job-specification/hcl2/functions/collection/concat"
+                  },
+                  {
+                    "title": "contains",
+                    "path": "job-specification/hcl2/functions/collection/contains"
+                  },
+                  {
+                    "title": "distinct",
+                    "path": "job-specification/hcl2/functions/collection/distinct"
+                  },
+                  {
+                    "title": "element",
+                    "path": "job-specification/hcl2/functions/collection/element"
+                  },
+                  {
+                    "title": "flatten",
+                    "path": "job-specification/hcl2/functions/collection/flatten"
+                  },
+                  {
+                    "title": "index",
+                    "path": "job-specification/hcl2/functions/collection/index-fn"
+                  },
+                  {
+                    "title": "keys",
+                    "path": "job-specification/hcl2/functions/collection/keys"
+                  },
+                  {
+                    "title": "length",
+                    "path": "job-specification/hcl2/functions/collection/length"
+                  },
+                  {
+                    "title": "lookup",
+                    "path": "job-specification/hcl2/functions/collection/lookup"
+                  },
+                  {
+                    "title": "merge",
+                    "path": "job-specification/hcl2/functions/collection/merge"
+                  },
+                  {
+                    "title": "range",
+                    "path": "job-specification/hcl2/functions/collection/range"
+                  },
+                  {
+                    "title": "reverse",
+                    "path": "job-specification/hcl2/functions/collection/reverse"
+                  },
+                  {
+                    "title": "setintersection",
+                    "path": "job-specification/hcl2/functions/collection/setintersection"
+                  },
+                  {
+                    "title": "setproduct",
+                    "path": "job-specification/hcl2/functions/collection/setproduct"
+                  },
+                  {
+                    "title": "setunion",
+                    "path": "job-specification/hcl2/functions/collection/setunion"
+                  },
+                  {
+                    "title": "slice",
+                    "path": "job-specification/hcl2/functions/collection/slice"
+                  },
+                  {
+                    "title": "sort",
+                    "path": "job-specification/hcl2/functions/collection/sort"
+                  },
+                  {
+                    "title": "values",
+                    "path": "job-specification/hcl2/functions/collection/values"
+                  },
+                  {
+                    "title": "zipmap",
+                    "path": "job-specification/hcl2/functions/collection/zipmap"
+                  }
+                ]
+              },
+              {
+                "title": "Type Conversion Functions",
+                "routes": [
+                  {
+                    "title": "can",
+                    "path": "job-specification/hcl2/functions/conversion/can"
+                  },
+                  {
+                    "title": "convert",
+                    "path": "job-specification/hcl2/functions/conversion/convert"
+                  },
+                  {
+                    "title": "try",
+                    "path": "job-specification/hcl2/functions/conversion/try"
+                  }
+                ]
+              },
+              {
+                "title": "Hash and Crypto Functions",
+                "routes": [
+                  {
+                    "title": "bcrypt",
+                    "path": "job-specification/hcl2/functions/crypto/bcrypt"
+                  },
+                  {
+                    "title": "md5",
+                    "path": "job-specification/hcl2/functions/crypto/md5"
+                  },
+                  {
+                    "title": "rsadecrypt",
+                    "path": "job-specification/hcl2/functions/crypto/rsadecrypt",
+                    "badge": {
+                      "text": "Deprecated",
+                      "type": "outlined",
+                      "color": "neutral"
+                    }
+                  },
+                  {
+                    "title": "sha1",
+                    "path": "job-specification/hcl2/functions/crypto/sha1"
+                  },
+                  {
+                    "title": "sha256",
+                    "path": "job-specification/hcl2/functions/crypto/sha256"
+                  },
+                  {
+                    "title": "sha512",
+                    "path": "job-specification/hcl2/functions/crypto/sha512"
+                  }
+                ]
+              },
+              {
+                "title": "Date and Time Functions",
+                "routes": [
+                  {
+                    "title": "formatdate",
+                    "path": "job-specification/hcl2/functions/datetime/formatdate"
+                  },
+                  {
+                    "title": "timeadd",
+                    "path": "job-specification/hcl2/functions/datetime/timeadd"
+                  }
+                ]
+              },
+              {
+                "title": "Encoding Functions",
+                "routes": [
+                  {
+                    "title": "base64decode",
+                    "path": "job-specification/hcl2/functions/encoding/base64decode"
+                  },
+                  {
+                    "title": "base64encode",
+                    "path": "job-specification/hcl2/functions/encoding/base64encode"
+                  },
+                  {
+                    "title": "csvdecode",
+                    "path": "job-specification/hcl2/functions/encoding/csvdecode"
+                  },
+                  {
+                    "title": "jsondecode",
+                    "path": "job-specification/hcl2/functions/encoding/jsondecode"
+                  },
+                  {
+                    "title": "jsonencode",
+                    "path": "job-specification/hcl2/functions/encoding/jsonencode"
+                  },
+                  {
+                    "title": "urlencode",
+                    "path": "job-specification/hcl2/functions/encoding/urlencode"
+                  },
+                  {
+                    "title": "yamldecode",
+                    "path": "job-specification/hcl2/functions/encoding/yamldecode"
+                  },
+                  {
+                    "title": "yamlencode",
+                    "path": "job-specification/hcl2/functions/encoding/yamlencode"
+                  }
+                ]
+              },
+              {
+                "title": "Filesystem Functions",
+                "routes": [
+                  {
+                    "title": "abspath",
+                    "path": "job-specification/hcl2/functions/file/abspath"
+                  },
+                  {
+                    "title": "basename",
+                    "path": "job-specification/hcl2/functions/file/basename"
+                  },
+                  {
+                    "title": "dirname",
+                    "path": "job-specification/hcl2/functions/file/dirname"
+                  },
+                  {
+                    "title": "file",
+                    "path": "job-specification/hcl2/functions/file/file"
+                  },
+                  {
+                    "title": "filebase64",
+                    "path": "job-specification/hcl2/functions/file/filebase64"
+                  },
+                  {
+                    "title": "fileexists",
+                    "path": "job-specification/hcl2/functions/file/fileexists"
+                  },
+                  {
+                    "title": "fileset",
+                    "path": "job-specification/hcl2/functions/file/fileset"
+                  },
+                  {
+                    "title": "pathexpand",
+                    "path": "job-specification/hcl2/functions/file/pathexpand"
+                  }
+                ]
+              },
+              {
+                "title": "IP Network Functions",
+                "routes": [
+                  {
+                    "title": "cidrhost",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrhost"
+                  },
+                  {
+                    "title": "cidrnetmask",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrnetmask"
+                  },
+                  {
+                    "title": "cidrsubnet",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnet"
+                  },
+                  {
+                    "title": "cidrsubnets",
+                    "path": "job-specification/hcl2/functions/ipnet/cidrsubnets"
+                  }
+                ]
+              },
+              {
+                "title": "Numeric Functions",
+                "routes": [
+                  {
+                    "title": "abs",
+                    "path": "job-specification/hcl2/functions/numeric/abs"
+                  },
+                  {
+                    "title": "ceil",
+                    "path": "job-specification/hcl2/functions/numeric/ceil"
+                  },
+                  {
+                    "title": "floor",
+                    "path": "job-specification/hcl2/functions/numeric/floor"
+                  },
+                  {
+                    "title": "log",
+                    "path": "job-specification/hcl2/functions/numeric/log"
+                  },
+                  {
+                    "title": "max",
+                    "path": "job-specification/hcl2/functions/numeric/max"
+                  },
+                  {
+                    "title": "min",
+                    "path": "job-specification/hcl2/functions/numeric/min"
+                  },
+                  {
+                    "title": "parseint",
+                    "path": "job-specification/hcl2/functions/numeric/parseint"
+                  },
+                  {
+                    "title": "pow",
+                    "path": "job-specification/hcl2/functions/numeric/pow"
+                  },
+                  {
+                    "title": "signum",
+                    "path": "job-specification/hcl2/functions/numeric/signum"
+                  }
+                ]
+              },
+              {
+                "title": "String Functions",
+                "routes": [
+                  {
+                    "title": "chomp",
+                    "path": "job-specification/hcl2/functions/string/chomp"
+                  },
+                  {
+                    "title": "format",
+                    "path": "job-specification/hcl2/functions/string/format"
+                  },
+                  {
+                    "title": "formatlist",
+                    "path": "job-specification/hcl2/functions/string/formatlist"
+                  },
+                  {
+                    "title": "indent",
+                    "path": "job-specification/hcl2/functions/string/indent"
+                  },
+                  {
+                    "title": "join",
+                    "path": "job-specification/hcl2/functions/string/join"
+                  },
+                  {
+                    "title": "lower",
+                    "path": "job-specification/hcl2/functions/string/lower"
+                  },
+                  {
+                    "title": "regex_replace",
+                    "path": "job-specification/hcl2/functions/string/regex_replace"
+                  },
+                  {
+                    "title": "replace",
+                    "path": "job-specification/hcl2/functions/string/replace"
+                  },
+                  {
+                    "title": "split",
+                    "path": "job-specification/hcl2/functions/string/split"
+                  },
+                  {
+                    "title": "strlen",
+                    "path": "job-specification/hcl2/functions/string/strlen"
+                  },
+                  {
+                    "title": "strrev",
+                    "path": "job-specification/hcl2/functions/string/strrev"
+                  },
+                  {
+                    "title": "substr",
+                    "path": "job-specification/hcl2/functions/string/substr"
+                  },
+                  {
+                    "title": "title",
+                    "path": "job-specification/hcl2/functions/string/title"
+                  },
+                  {
+                    "title": "trim",
+                    "path": "job-specification/hcl2/functions/string/trim"
+                  },
+                  {
+                    "title": "trimprefix",
+                    "path": "job-specification/hcl2/functions/string/trimprefix"
+                  },
+                  {
+                    "title": "trimspace",
+                    "path": "job-specification/hcl2/functions/string/trimspace"
+                  },
+                  {
+                    "title": "trimsuffix",
+                    "path": "job-specification/hcl2/functions/string/trimsuffix"
+                  },
+                  {
+                    "title": "upper",
+                    "path": "job-specification/hcl2/functions/string/upper"
+                  }
+                ]
+              },
+              {
+                "title": "UUID Functions",
+                "routes": [
+                  {
+                    "title": "uuidv4",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv4"
+                  },
+                  {
+                    "title": "uuidv5",
+                    "path": "job-specification/hcl2/functions/uuid/uuidv5"
+                  }
+                ]
+              }
+            ]
+          },
+          {
+            "title": "Locals",
+            "path": "job-specification/hcl2/locals"
+          },
+          {
+            "title": "Syntax",
+            "path": "job-specification/hcl2/syntax"
+          },
+          {
+            "title": "Variables",
+            "path": "job-specification/hcl2/variables"
+          }
+        ]
+      },
+      {
+        "title": "action",
+        "path": "job-specification/action"
+      },
+      {
+        "title": "artifact",
+        "path": "job-specification/artifact"
+      },
+      {
+        "title": "affinity",
+        "path": "job-specification/affinity"
+      },
+      {
+        "title": "change_script",
+        "path": "job-specification/change_script"
+      },
+      {
+        "title": "check",
+        "path": "job-specification/check"
+      },
+      {
+        "title": "check_restart",
+        "path": "job-specification/check_restart"
+      },
+      {
+        "title": "connect",
+        "path": "job-specification/connect"
+      },
+      {
+        "title": "consul",
+        "path": "job-specification/consul"
+      },
+      {
+        "title": "constraint",
+        "path": "job-specification/constraint"
+      },
+      {
+        "title": "csi_plugin",
+        "path": "job-specification/csi_plugin"
+      },
+      {
+        "title": "device",
+        "path": "job-specification/device"
+      },
+      {
+        "title": "disconnect",
+        "path": "job-specification/disconnect"
+      },
+      {
+        "title": "dispatch_payload",
+        "path": "job-specification/dispatch_payload"
+      },
+      {
+        "title": "env",
+        "path": "job-specification/env"
+      },
+      {
+        "title": "ephemeral_disk",
+        "path": "job-specification/ephemeral_disk"
+      },
+      {
+        "title": "expose",
+        "path": "job-specification/expose"
+      },
+      {
+        "title": "gateway",
+        "path": "job-specification/gateway"
+      },
+      {
+        "title": "group",
+        "path": "job-specification/group"
+      },
+      {
+        "title": "identity",
+        "path": "job-specification/identity"
+      },
+      {
+        "title": "job",
+        "path": "job-specification/job"
+      },
+      {
+        "title": "lifecycle",
+        "path": "job-specification/lifecycle"
+      },
+      {
+        "title": "logs",
+        "path": "job-specification/logs"
+      },
+      {
+        "title": "meta",
+        "path": "job-specification/meta"
+      },
+      {
+        "title": "migrate",
+        "path": "job-specification/migrate"
+      },
+      {
+        "title": "multiregion",
+        "path": "job-specification/multiregion"
+      },
+      {
+        "title": "network",
+        "path": "job-specification/network"
+      },
+      {
+        "title": "numa",
+        "path": "job-specification/numa"
+      },
+      {
+        "title": "parameterized",
+        "path": "job-specification/parameterized"
+      },
+      {
+        "title": "periodic",
+        "path": "job-specification/periodic"
+      },
+      {
+        "title": "proxy",
+        "path": "job-specification/proxy"
+      },
+      {
+        "title": "reschedule",
+        "path": "job-specification/reschedule"
+      },
+      {
+        "title": "resources",
+        "path": "job-specification/resources"
+      },
+      {
+        "title": "restart",
+        "path": "job-specification/restart"
+      },
+      {
+        "title": "scaling",
+        "path": "job-specification/scaling"
+      },
+      {
+        "title": "schedule",
+        "path": "job-specification/schedule"
+      },
+      {
+        "title": "service",
+        "path": "job-specification/service"
+      },
+      {
+        "title": "sidecar_service",
+        "path": "job-specification/sidecar_service"
+      },
+      {
+        "title": "sidecar_task",
+        "path": "job-specification/sidecar_task"
+      },
+      {
+        "title": "spread",
+        "path": "job-specification/spread"
+      },
+      {
+        "title": "task",
+        "path": "job-specification/task"
+      },
+      {
+        "title": "template",
+        "path": "job-specification/template"
+      },
+      {
+        "title": "transparent_proxy",
+        "path": "job-specification/transparent_proxy"
+      },
+      {
+        "title": "ui",
+        "path": "job-specification/ui"
+      },
+      {
+        "title": "update",
+        "path": "job-specification/update"
+      },
+      {
+        "title": "upstreams",
+        "path": "job-specification/upstreams"
+      },
+      {
+        "title": "vault",
+        "path": "job-specification/vault"
+      },
+      {
+        "title": "volume",
+        "path": "job-specification/volume"
+      },
+      {
+        "title": "volume_mount",
+        "path": "job-specification/volume_mount"
+      }
+    ]
+  },
+  {
+    "title": "Other Specifications",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "other-specifications"
+      },
+      {
+        "title": "ACL Policy",
+        "path": "other-specifications/acl-policy"
+      },
+      {
+        "title": "Namespace",
+        "path": "other-specifications/namespace"
+      },
+      {
+        "title": "Node Pool",
+        "path": "other-specifications/node-pool"
+      },
+      {
+        "title": "Resource Quota",
+        "path": "other-specifications/quota"
+      },
+      {
+        "title": "Variables",
+        "path": "other-specifications/variables"
+      },
+      {
+        "title": "Volume",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "other-specifications/volume"
+          },
+          {
+            "title": "capability",
+            "path": "other-specifications/volume/capability"
+          },
+          {
+            "title": "mount_options",
+            "path": "other-specifications/volume/mount_options"
+          },
+          {
+            "title": "topology_request",
+            "path": "other-specifications/volume/topology_request"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Docker",
+        "path": "drivers/docker"
+      },
+      {
+        "title": "Isolated Fork/Exec",
+        "path": "drivers/exec"
+      },
+      {
+        "title": "Java",
+        "path": "drivers/java"
+      },
+      {
+        "title": "QEMU",
+        "path": "drivers/qemu"
+      },
+      {
+        "title": "Raw Fork/Exec",
+        "path": "drivers/raw_exec"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Exec2",
+            "href": "/plugins/drivers/exec2"
+          },
+          {
+            "title": "Podman",
+            "href": "/plugins/drivers/podman"
+          },
+          {
+            "title": "Virt <sup>Beta</sup>",
+            "href": "/plugins/drivers/virt"
+          },
+          {
+            "title": "Community",
+            "href": "/plugins/drivers/community"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "href": "/plugins/devices"
+  },
+  {
+    "title": "Schedulers",
+    "path": "schedulers"
+  },
+  {
+    "title": "Runtime",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "runtime"
+      },
+      {
+        "title": "Runtime Environment",
+        "path": "runtime/environment"
+      },
+      {
+        "title": "Variable Interpolation",
+        "path": "runtime/interpolation"
+      }
+    ]
+  },
+  {
+    "title": "Networking",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "networking"
+      },
+      {
+        "title": "Service Discovery",
+        "path": "networking/service-discovery"
+      },
+      {
+        "title": "Service Mesh",
+        "path": "networking/service-mesh"
+      },
+      {
+        "title": "CNI",
+        "path": "networking/cni"
+      }
+    ]
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "href": "/tools/autoscaling"
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "href": "/tools/autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "href": "/tools/autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "http",
+            "href": "/tools/autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "href": "/tools/autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "href": "/tools/autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "href": "/tools/autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "href": "/tools/autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "href": "/tools/autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "href": "/tools/autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "href": "/tools/autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "href": "/tools/autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "href": "/tools/autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "href": "/tools/autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "href": "/tools/autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "href": "/tools/autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "href": "/tools/autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "href": "/tools/autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "href": "/tools/autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "href": "/tools/autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "href": "/tools/autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "href": "/tools/autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "href": "/tools/autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "href": "/tools/autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "href": "/tools/autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "href": "/tools/autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "href": "/tools/autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "href": "/tools/autoscaling/plugins/external"
+          }
+        ]
+      },
+      {
+        "title": "Internals",
+        "routes": [
+          {
+            "title": "Overview",
+            "href": "/tools/autoscaling/internals"
+          },
+          {
+            "title": "Checks",
+            "href": "/tools/autoscaling/internals/checks"
+          },
+          {
+            "title": "Node Selector Strategy",
+            "href": "/tools/autoscaling/internals/node-selector-strategy"
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "href": "/tools/autoscaling/internals/plugins"
+              },
+              {
+                "title": "Base",
+                "href": "/tools/autoscaling/internals/plugins/base"
+              },
+              {
+                "title": "APM",
+                "href": "/tools/autoscaling/internals/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "href": "/tools/autoscaling/internals/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "href": "/tools/autoscaling/internals/plugins/target"
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Operations",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "operations"
+      },
+      {
+        "title": "Operating Nomad Agents",
+        "path": "operations/nomad-agent"
+      },
+      {
+        "title": "Monitoring Nomad",
+        "path": "operations/monitoring-nomad"
+      },
+      {
+        "title": "Metrics Reference",
+        "path": "operations/metrics-reference"
+      },
+      {
+        "title": "Cluster Management",
+        "href": "https://learn.hashicorp.com/collections/nomad/manage-clusters"
+      },
+      {
+        "title": "Transport Security",
+        "href": "https://learn.hashicorp.com/collections/nomad/transport-security"
+      },
+      {
+        "title": "Access Control",
+        "href": "https://learn.hashicorp.com/collections/nomad/access-control"
+      },
+      {
+        "title": "Key Management",
+        "path": "operations/key-management"
+      },
+      {
+        "title": "Federation",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "operations/federation"
+          },
+          {
+            "title": "Failure",
+            "path": "operations/federation/failure"
+          }
+        ]
+      },
+      {
+        "title": "Considerations for Stateful Workloads",
+        "path": "operations/stateful-workloads"
+      },
+      {
+        "title": "Benchmarking Nomad",
+        "path": "operations/benchmarking"
+      },
+      {
+        "title": "Federate AWS Access with Workload Identity",
+        "path": "operations/aws-oidc-provider"
+      },
+      {
+        "title": "IPv6 Support",
+        "path": "operations/ipv6-support"
+      }
+    ]
+  },
+  {
+    "divider": true
+  },
+  {
+    "title": "Nomad vs. Kubernetes",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "nomad-vs-kubernetes"
+      },
+      {
+        "title": "Alternative to Kubernetes",
+        "path": "nomad-vs-kubernetes/alternative"
+      },
+      {
+        "title": "Supplement to Kubernetes",
+        "path": "nomad-vs-kubernetes/supplement"
+      }
+    ]
+  },
+  {
+    "title": "Nomad Ecosystem",
+    "path": "ecosystem"
+  },
+  {
+    "title": "Nomad Partnerships",
+    "path": "partnerships"
+  },
+  {
+    "title": "Who Uses Nomad",
+    "path": "who-uses-nomad"
+  },
+  {
+    "title": "Nomad Enterprise",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "enterprise"
+      },
+      {
+        "title": "License",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "enterprise/license"
+          },
+          {
+            "title": "Automated license utilization reporting",
+            "path": "enterprise/license/utilization-reporting"
+          },
+          {
+            "title": "FAQ",
+            "path": "enterprise/license/faq"
+          }
+        ]
+      },
+      {
+        "title": "Sentinel",
+        "path": "enterprise/sentinel"
+      }
+    ]
+  },
+  {
+    "title": "FAQ",
+    "path": "faq"
+  }
+]
diff --git a/content/nomad/v1.9.x/data/intro-nav-data.json b/content/nomad/v1.9.x/data/intro-nav-data.json
new file mode 100644
index 0000000000..0fdab4c70f
--- /dev/null
+++ b/content/nomad/v1.9.x/data/intro-nav-data.json
@@ -0,0 +1,31 @@
+[
+  {
+    "title": "Use Cases",
+    "path": "use-cases"
+  },
+  {
+    "title": "Nomad vs. Other Software",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "vs"
+      },
+      {
+        "title": "AWS ECS",
+        "path": "vs/ecs"
+      },
+      {
+        "title": "Mesos & Marathon",
+        "path": "vs/mesos"
+      },
+      {
+        "title": "Terraform",
+        "path": "vs/terraform"
+      }
+    ]
+  },
+  {
+    "title": "Getting Started",
+    "href": "https://developer.hashicorp.com/nomad/tutorials/get-started"
+  }
+]
diff --git a/content/nomad/v1.9.x/data/plugins-nav-data.json b/content/nomad/v1.9.x/data/plugins-nav-data.json
new file mode 100644
index 0000000000..f03f8d7283
--- /dev/null
+++ b/content/nomad/v1.9.x/data/plugins-nav-data.json
@@ -0,0 +1,116 @@
+[
+  {
+    "title": "Task Drivers",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "drivers"
+      },
+      {
+        "title": "Exec2",
+        "path": "drivers/exec2"
+      },
+      {
+        "title": "Podman",
+        "path": "drivers/podman"
+      },
+      {
+        "title": "Virt",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/virt"
+          },
+          {
+            "title": "Install",
+            "path": "drivers/virt/install"
+          },
+          {
+            "title": "Task Config",
+            "path": "drivers/virt/task-config"
+          }
+        ]
+      },
+      {
+        "title": "Community",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "drivers/community"
+          },
+          {
+            "title": "containerd",
+            "path": "drivers/community/containerd"
+          },
+          {
+            "title": "Pledge",
+            "path": "drivers/community/pledge"
+          },
+          {
+            "title": "Firecracker driver",
+            "path": "drivers/community/firecracker-task-driver"
+          },
+          {
+            "title": "Jail task driver",
+            "path": "drivers/community/jail-task-driver"
+          },
+          {
+            "title": "Lightrun",
+            "path": "drivers/community/lightrun"
+          },
+          {
+            "title": "Pot",
+            "path": "drivers/community/pot"
+          },
+          {
+            "title": "Rookout",
+            "path": "drivers/community/rookout"
+          },
+          {
+            "title": "Singularity",
+            "path": "drivers/community/singularity"
+          },
+          {
+            "title": "systemd-nspawn",
+            "path": "drivers/community/nspawn"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/iis"
+          },
+          {
+            "title": "Windows IIS",
+            "path": "drivers/community/nomad-iis"
+          }
+        ]
+      }
+    ]
+  },
+  {
+    "title": "Device Plugins",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "devices"
+      },
+      {
+        "title": "NVIDIA",
+        "path": "devices/nvidia"
+      },
+      {
+        "title": "USB",
+        "badge": {
+          "text": "BETA",
+          "type": "outlined",
+          "color": "neutral"
+        },
+        "path": "devices/usb"
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.9.x/data/tools-nav-data.json b/content/nomad/v1.9.x/data/tools-nav-data.json
new file mode 100644
index 0000000000..195677fadc
--- /dev/null
+++ b/content/nomad/v1.9.x/data/tools-nav-data.json
@@ -0,0 +1,231 @@
+[
+  {
+    "title": "Overview",
+    "path": "index"
+  },
+  {
+    "title": "Autoscaling",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "autoscaling"
+      },
+      {
+        "title": "Concepts",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/concepts"
+          },
+          {
+            "title": "Policy Evaluation",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/policy-eval"
+              },
+              {
+                "title": "Checks",
+                "path": "autoscaling/concepts/policy-eval/checks"
+              },
+              {
+                "title": "Node Selector Strategy",
+                "path": "autoscaling/concepts/policy-eval/node-selector-strategy"
+              }
+            ]
+          },
+          {
+            "title": "Plugins",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/concepts/plugins"
+              },
+              {
+                "title": "Base",
+                "path": "autoscaling/concepts/plugins/base"
+              },
+              {
+                "title": "APM",
+                "path": "autoscaling/concepts/plugins/apm"
+              },
+              {
+                "title": "Strategy",
+                "path": "autoscaling/concepts/plugins/strategy"
+              },
+              {
+                "title": "Target",
+                "path": "autoscaling/concepts/plugins/target"
+              }
+            ]
+          }
+        ]
+      },
+      {
+        "title": "Agent",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/agent"
+          },
+          {
+            "title": "apm",
+            "path": "autoscaling/agent/apm"
+          },
+          {
+            "title": "dynamic_application_sizing",
+            "path": "autoscaling/agent/dynamic_application_sizing"
+          },
+          {
+            "title": "high_availability",
+            "path": "autoscaling/agent/high_availability"
+          },
+          {
+            "title": "http",
+            "path": "autoscaling/agent/http"
+          },
+          {
+            "title": "nomad",
+            "path": "autoscaling/agent/nomad"
+          },
+          {
+            "title": "policy",
+            "path": "autoscaling/agent/policy"
+          },
+          {
+            "title": "policy_eval",
+            "path": "autoscaling/agent/policy_eval"
+          },
+          {
+            "title": "strategy",
+            "path": "autoscaling/agent/strategy"
+          },
+          {
+            "title": "target",
+            "path": "autoscaling/agent/target"
+          },
+          {
+            "title": "telemetry",
+            "path": "autoscaling/agent/telemetry"
+          }
+        ]
+      },
+      {
+        "title": "API",
+        "path": "autoscaling/api"
+      },
+      {
+        "title": "CLI",
+        "path": "autoscaling/cli"
+      },
+      {
+        "title": "Policy",
+        "path": "autoscaling/policy"
+      },
+      {
+        "title": "Telemetry",
+        "path": "autoscaling/telemetry"
+      },
+      {
+        "title": "Plugins",
+        "routes": [
+          {
+            "title": "Overview",
+            "path": "autoscaling/plugins"
+          },
+          {
+            "title": "APM",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/apm"
+              },
+              {
+                "title": "Datadog",
+                "path": "autoscaling/plugins/apm/datadog"
+              },
+              {
+                "title": "Nomad API",
+                "path": "autoscaling/plugins/apm/nomad"
+              },
+              {
+                "title": "Prometheus",
+                "path": "autoscaling/plugins/apm/prometheus"
+              }
+            ]
+          },
+          {
+            "title": "Strategy",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/strategy"
+              },
+              {
+                "title": "Dynamic Application Sizing Average",
+                "path": "autoscaling/plugins/strategy/app-sizing-avg"
+              },
+              {
+                "title": "Dynamic Application Sizing Max",
+                "path": "autoscaling/plugins/strategy/app-sizing-max"
+              },
+              {
+                "title": "Dynamic Application Sizing Percentile",
+                "path": "autoscaling/plugins/strategy/app-sizing-percentile"
+              },
+              {
+                "title": "Fixed Value",
+                "path": "autoscaling/plugins/strategy/fixed-value"
+              },
+              {
+                "title": "Pass-Through",
+                "path": "autoscaling/plugins/strategy/pass-through"
+              },
+              {
+                "title": "Target Value",
+                "path": "autoscaling/plugins/strategy/target-value"
+              },
+              {
+                "title": "Threshold",
+                "path": "autoscaling/plugins/strategy/threshold"
+              }
+            ]
+          },
+          {
+            "title": "Target",
+            "routes": [
+              {
+                "title": "Overview",
+                "path": "autoscaling/plugins/target"
+              },
+              {
+                "title": "Amazon Web Services Autoscaling Group",
+                "path": "autoscaling/plugins/target/aws-asg"
+              },
+              {
+                "title": "Azure Virtual Machine Scale Set",
+                "path": "autoscaling/plugins/target/azure-vmss"
+              },
+              {
+                "title": "Dynamic Application Sizing",
+                "path": "autoscaling/plugins/target/app-sizing-nomad"
+              },
+              {
+                "title": "Google Cloud Engine Managed Instance Group",
+                "path": "autoscaling/plugins/target/gce-mig"
+              },
+              {
+                "title": "Nomad Task Group",
+                "path": "autoscaling/plugins/target/nomad"
+              }
+            ]
+          },
+          {
+            "title": "Community",
+            "path": "autoscaling/plugins/external"
+          }
+        ]
+      }
+    ]
+  }
+]
diff --git a/content/nomad/v1.9.x/img/autoscaling/autoscaler-arch.png b/content/nomad/v1.9.x/img/autoscaling/autoscaler-arch.png
new file mode 100644
index 0000000000..2165b92250
Binary files /dev/null and b/content/nomad/v1.9.x/img/autoscaling/autoscaler-arch.png differ
diff --git a/content/nomad/v1.9.x/img/autoscaling/control-loop.png b/content/nomad/v1.9.x/img/autoscaling/control-loop.png
new file mode 100644
index 0000000000..55bd007f44
Binary files /dev/null and b/content/nomad/v1.9.x/img/autoscaling/control-loop.png differ
diff --git a/content/nomad/v1.9.x/img/autoscaling/policy-eval.png b/content/nomad/v1.9.x/img/autoscaling/policy-eval.png
new file mode 100644
index 0000000000..39e9b9caa6
Binary files /dev/null and b/content/nomad/v1.9.x/img/autoscaling/policy-eval.png differ
diff --git a/content/nomad/v1.9.x/img/consul-integration-auth-method.png b/content/nomad/v1.9.x/img/consul-integration-auth-method.png
new file mode 100644
index 0000000000..485cb5d6ac
Binary files /dev/null and b/content/nomad/v1.9.x/img/consul-integration-auth-method.png differ
diff --git a/content/nomad/v1.9.x/img/consul-integration-wi.png b/content/nomad/v1.9.x/img/consul-integration-wi.png
new file mode 100644
index 0000000000..b20fcc3863
Binary files /dev/null and b/content/nomad/v1.9.x/img/consul-integration-wi.png differ
diff --git a/content/nomad/v1.9.x/img/consul-integration-wid-acl-token.png b/content/nomad/v1.9.x/img/consul-integration-wid-acl-token.png
new file mode 100644
index 0000000000..bfb587564b
Binary files /dev/null and b/content/nomad/v1.9.x/img/consul-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.9.x/img/count-dashboard.png b/content/nomad/v1.9.x/img/count-dashboard.png
new file mode 100644
index 0000000000..dbf5ef3338
Binary files /dev/null and b/content/nomad/v1.9.x/img/count-dashboard.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/android-chrome-192x192.png b/content/nomad/v1.9.x/img/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000000..c194126ce5
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/android-chrome-192x192.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/android-chrome-512x512.png b/content/nomad/v1.9.x/img/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000000..b5f80653e2
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/android-chrome-512x512.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/apple-touch-icon.png b/content/nomad/v1.9.x/img/favicons/apple-touch-icon.png
new file mode 100644
index 0000000000..baabff44a8
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/apple-touch-icon.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/favicon-16x16.png b/content/nomad/v1.9.x/img/favicons/favicon-16x16.png
new file mode 100644
index 0000000000..c8f169527b
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/favicon-16x16.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/favicon-194x194.png b/content/nomad/v1.9.x/img/favicons/favicon-194x194.png
new file mode 100644
index 0000000000..9e3696178f
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/favicon-194x194.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/favicon-32x32.png b/content/nomad/v1.9.x/img/favicons/favicon-32x32.png
new file mode 100644
index 0000000000..d415538656
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/favicon-32x32.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/favicon.ico b/content/nomad/v1.9.x/img/favicons/favicon.ico
new file mode 100644
index 0000000000..733bf0cd6e
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/favicon.ico differ
diff --git a/content/nomad/v1.9.x/img/favicons/mstile-144x144.png b/content/nomad/v1.9.x/img/favicons/mstile-144x144.png
new file mode 100644
index 0000000000..02c9951698
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/mstile-144x144.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/mstile-150x150.png b/content/nomad/v1.9.x/img/favicons/mstile-150x150.png
new file mode 100644
index 0000000000..133cf3e2cb
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/mstile-150x150.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/mstile-310x150.png b/content/nomad/v1.9.x/img/favicons/mstile-310x150.png
new file mode 100644
index 0000000000..81b2a3ccfa
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/mstile-310x150.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/mstile-310x310.png b/content/nomad/v1.9.x/img/favicons/mstile-310x310.png
new file mode 100644
index 0000000000..7093e1d307
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/mstile-310x310.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/mstile-70x70.png b/content/nomad/v1.9.x/img/favicons/mstile-70x70.png
new file mode 100644
index 0000000000..62550e1428
Binary files /dev/null and b/content/nomad/v1.9.x/img/favicons/mstile-70x70.png differ
diff --git a/content/nomad/v1.9.x/img/favicons/safari-pinned-tab.svg b/content/nomad/v1.9.x/img/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000000..4f4b4b5bef
--- /dev/null
+++ b/content/nomad/v1.9.x/img/favicons/safari-pinned-tab.svg
@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
+  <path d="m5.76 6.7.87-.5 2.3 1.27V4.8l2.2-1.32V8.8L9.3 9.87 8 9.07V16h.03L15 12V4L7.94 0 1 4v8l7 4V9.07l-.93-.53v2.66l-2.1 1.34V7.2l.8-.5z"/>
+</svg>
diff --git a/content/nomad/v1.9.x/img/home-hero-pattern.svg b/content/nomad/v1.9.x/img/home-hero-pattern.svg
new file mode 100644
index 0000000000..7619b31ee3
--- /dev/null
+++ b/content/nomad/v1.9.x/img/home-hero-pattern.svg
@@ -0,0 +1,20 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="684" height="394" fill="none" viewBox="0 0 684 394" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <path fill="#BFBFC0" d="M1 125.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-87.11a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 27.42a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM1 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 38.31a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.795.795 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM1 49.2a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 1.807 50a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM1 81.866a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm228-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.798.798 0 0 0-.588-1.092.82.82 0 0 0-.829.34.795.795 0 0 0 .1 1.012.8.8 0 0 0 .571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061M86.5.199a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.809.809 0 0 0 87.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm19 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 124.5.2Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.809.809 0 0 0 49.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 200.5.2Zm-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874A.81.81 0 0 0 30.307 1a.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm114 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 143.5.2Zm-76 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873A.81.81 0 0 0 68.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm95 0a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873A.81.81 0 0 0 11.307 1a.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171 0a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013A.8.8 0 0 0 181.5.2ZM77 114.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M77 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.803.803 0 0 0-.807-.801M77 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 27.421a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M77 38.31a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M77 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566A.8.8 0 0 0 77 49.2M58 16.532a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 168.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M58 5.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM58 49.2a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm9.5 49a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 87.111a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM77 190.754a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M96 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM96 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-9.5 49a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm-9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061ZM58 70.977a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm47.5-27.223a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm-19 54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-21.778a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061ZM96 92.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M86.5 21.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 76.222a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234ZM96 190.755a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM29.5 43.754a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM20 114.532a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m0-76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235M20 49.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.237-.567A.8.8 0 0 0 20 49.2m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M20 60.088a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235Zm0 32.666a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235ZM58 81.866a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm-38-10.89a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.566.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.567.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236ZM20 16.532a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.379-.567.8.8 0 0 0-.237-.566.8.8 0 0 0-.571-.235m-9.5 92.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 43.555a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0-32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 76.222a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 119.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 21.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5-16.333a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.8.8 0 0 0-.808-.801m0 32.666a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.804.804 0 0 0 1.1.584.81.81 0 0 0 .498-.74.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.448.136.8.8 0 0 0-.343.822.811.811 0 0 0 1.463.289.796.796 0 0 0-.101-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .176.873.81.81 0 0 0 1.378-.567.81.81 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm9.5 70.778a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.379-.567.81.81 0 0 0-.808-.801m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062ZM20 190.753a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M10.5 11.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 81.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.243-.121.8.8 0 0 0-.101-1.012.8.8 0 0 0-.571-.235m28.5-49a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.874.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.11a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.234m0 97.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236ZM58 125.42a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.235Zm0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.8.8 0 0 0-.57-.235Zm0-32.667a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.011.8.8 0 0 0-.57-.236Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.8.8 0 0 0-.1-1.012.82.82 0 0 0-.57-.235Zm-19-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.81.81 0 0 0 1.463.289.797.797 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-21.777a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.812.812 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m-9.5-81.666a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.235ZM39 125.42a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M29.5 21.976a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.809.809 0 0 0 1.378-.566.8.8 0 0 0-.236-.567.8.8 0 0 0-.57-.234Zm0-10.888a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.236-.566.8.8 0 0 0-.57-.236ZM39 168.976a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.8.8 0 0 0-.449.136.8.8 0 0 0-.343.822.8.8 0 0 0 .635.63.81.81 0 0 0 .964-.786.8.8 0 0 0-.498-.741.8.8 0 0 0-.31-.061Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.242-.121.798.798 0 0 0-.362-1.186.8.8 0 0 0-.31-.061Zm0-163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M39 5.643a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.79.79 0 0 0 .175.873.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801M39 60.088a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.873.808.808 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.889a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0 10.89a.81.81 0 0 0-.746.494.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.566.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.062Zm0-43.556a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061ZM10.5 76.421a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.809.809 0 0 0 1.378-.567.8.8 0 0 0-.498-.74.8.8 0 0 0-.31-.061Zm171-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-32.667a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 168.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 70.977a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M172 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm-9.5 27.221a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M172 49.199a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M210 16.532a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M210 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235Zm0-10.89a.81.81 0 0 0-.746.496.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 38.11a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19-76.222a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5 146.999a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.11a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0-21.779a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235M191 5.644a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235ZM134 136.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234Zm0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 146.999a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.89a.81.81 0 0 0-.746.494.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235Zm9.5-5.445a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M115 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0-10.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 87.11a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235M134 5.643a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M115 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M153 38.31a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M153 70.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234Zm9.5 16.334a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235M153 92.754a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.81.81 0 0 0 .828-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.092.82.82 0 0 0 .829-.34.794.794 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.888a.81.81 0 0 0-.746.494.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.34.795.795 0 0 0-.1-1.013.8.8 0 0 0-.571-.234m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.794.794 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.795.795 0 0 0-.1-1.012.8.8 0 0 0-.571-.234ZM86.5 196.2a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .175.874.81.81 0 0 0 1.378-.567.807.807 0 0 0-.807-.801m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.795.795 0 0 0 .175.873.81.81 0 0 0 1.378-.567.8.8 0 0 0-.807-.801m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M456 321.421a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.777a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 141.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m228-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-96.397a.81.81 0 0 0 .746-.495.797.797 0 0 0-.588-1.092.81.81 0 0 0-.829.34.8.8 0 0 0 .1 1.012c.151.15.357.235.571.235m0 107.286a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0-98a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.8.8 0 0 0 .466-.045.797.797 0 0 0 0-1.481.8.8 0 0 0-.309-.061m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.779a.81.81 0 0 0-.746.494.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235zm0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-142.5-147a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m19 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m95 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-152 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m171 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061M532 310.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-152.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M532 212.532a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 223.421a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061M532 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-10.888a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M513 201.643a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 114.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 27.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M551 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-5.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M513 266.976a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m47.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-19 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0 21.777a.8.8 0 0 0-.449.136.8.8 0 0 0 .291 1.452.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-147a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-141.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-66.5 16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-76.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m0 43.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m9.5 136.111a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235M475 256.087a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m9.5 81.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m28.5-92.556a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-38-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0 10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 108.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m-9.5-92.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 92.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 43.555a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 76.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.333a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.786.81.81 0 0 0-.808-.801m0 32.666a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.804.804 0 0 0-.808-.802m0-10.889a.82.82 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .965-.786.806.806 0 0 0-.808-.802m0-21.777a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.82.82 0 0 0 .829-.341.8.8 0 0 0 .136-.445.804.804 0 0 0-.808-.801m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 70.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.092.808.808 0 0 0 .965-.785.804.804 0 0 0-.808-.802m-9.5-179.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .176.873.805.805 0 0 0 .879.174.8.8 0 0 0-.309-1.542m28.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-87.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-54.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m9.5 114.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.808.808 0 0 0-.792.958.8.8 0 0 0 .634.629.807.807 0 0 0 .965-.786.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.235m0-43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-19-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 92.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-103.445a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 .88.174.8.8 0 0 0 .498-.74.8.8 0 0 0-.236-.566.8.8 0 0 0-.571-.236m9.5 157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-163.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 136.111a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M494 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 157.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M494 256.087a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-28.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m171-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 59.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-152.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 49a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 65.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-27.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5 38.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0-32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 114.334a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M627 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 27.222a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M627 245.199a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5 136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m38 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235M665 201.643a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 136.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M665 212.532a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 147a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-9.5-92.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-43.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m9.5 38.111a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-119.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0 98a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-32.666a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 43.555a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-19-76.223a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 76.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 54.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m9.5-70.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .828-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.81.81 0 0 0 .828-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-98a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 76.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 54.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-16.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0 10.888a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m-9.5-81.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-136.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m-19-185.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M589 332.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-168.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m-9.5-92.555a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5-49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-54.445a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5-5.444a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0 32.666a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-43.555a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m-19 163.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m19-76.222a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-59.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-32.666a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m0-87.112a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 125.222a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5-103.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5 125.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 43.556a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587M570 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m9.5 179.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m19-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235M608 234.31a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 32.666a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0-10.888a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m0-43.556a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 70.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235M608 266.976a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m9.5 16.334a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.8.8 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5-59.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 98a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-65.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .175.873.81.81 0 0 0 1.378-.566.803.803 0 0 0-.807-.802m0-54.444a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.8.8 0 0 0 .467-.045.797.797 0 0 0 .262-1.307.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0-21.778a.81.81 0 0 0-.746.495.798.798 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-9.5-27.222a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.82.82 0 0 0 .828-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-9.5-16.333a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.82.82 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 21.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m19-119.778a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.34.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m-19 130.667a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-108.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0 .075-.751.8.8 0 0 0-.437-.434.8.8 0 0 0-.309-.061m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 65.333a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-21.777a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m0 10.889a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m9.5 49a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-9.5-114.334a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m9.5 147a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5 5.445a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.802.802 0 1 0 .157-1.587m9.5 5.444a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.092.808.808 0 0 0 .964-.785.8.8 0 0 0-.236-.567.8.8 0 0 0-.571-.235m0-32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.81.81 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m0 10.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .589 1.093.808.808 0 0 0 .964-.786.8.8 0 0 0-.236-.567.82.82 0 0 0-.571-.235m-9.5-157.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0 32.667a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.8.8 0 0 0-.571-.235m0 87.111a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m0-108.889a.81.81 0 0 0-.746.495.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.796.796 0 0 0-.1-1.012.82.82 0 0 0-.571-.235m-57 174.223a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.81.81 0 0 0 .964-.786.8.8 0 0 0-.061-.307.82.82 0 0 0-.437-.433.8.8 0 0 0-.309-.061m-171 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m133 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-114 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m76 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .588 1.092.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.012.8.8 0 0 0-.571-.234m-19 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m-76 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m57 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235m-95 0a.81.81 0 0 0-.746.495.797.797 0 0 0 .589 1.092.808.808 0 0 0 .964-.786.79.79 0 0 0-.498-.74.8.8 0 0 0-.309-.061m209 0a.81.81 0 0 0-.746.494.8.8 0 0 0 .588 1.093.81.81 0 0 0 .829-.341.79.79 0 0 0-.1-1.011.8.8 0 0 0-.571-.235"/>
+  <path fill="#000" d="M482.919 197 456 212.429v1.818L486.099 197zm-19.003 0L456 201.537v1.818L467.095 197zm98.181 0h-3.185L456 255.979v1.817l105.851-60.655zm-22.178 0L456 245.098v1.819L543.099 197zm-18.997 0L456 234.207v1.817L524.101 197zm-19.004 0L456 223.315v1.818L505.097 197zm69.353 5.21-1.593.912 114.24 65.474.082.047v-1.823l-112.647-64.563zm-9.507 5.443-1.587.912 123.741 70.917.082.047v-1.824L561.846 207.7zm-9.497 5.443-1.592.912 133.243 76.366.082.047v-1.823l-131.651-75.455zm-18.997 10.886-1.594.912 152.242 87.258.082.047v-1.824l-150.648-86.346zm9.495-5.443-1.586.912 142.739 81.809.082.047v-1.824l-141.153-80.897zm-18.998 10.887-1.598.917 161.749 92.695.082.047v-1.823l-160.151-91.789zM638.001 393 456.082 288.738l-.082-.047v1.824L634.821 393zm-18.992 0-162.927-93.376-.082-.047v1.829L615.817 393zm-38.002 0-124.925-71.598-.082-.047v1.829L577.816 393zm19.004 0-143.929-82.484-.082-.047v1.823L596.82 393zm56.994 0L456.082 277.846l-.082-.047v1.829L653.82 393zm19.004 0L456.082 266.961l-.082-.047v1.823L672.817 393zM570.637 27.459 457 92.592v1.817l.082-.047L571 29.082l114 65.333v-1.823l-113.594-65.1a.8.8 0 0 0-.761-.033zm-.035 21.798L457 114.364v1.818l.082-.047L571 50.86l114 65.339v-1.824L571.406 49.27a.7.7 0 0 0-.17-.074.5.5 0 0 0-.147-.027.77.77 0 0 0-.487.088m.035-10.906L457 103.478v1.817l.082-.046 113.912-65.281L685 105.307v-1.824l-113.594-65.1a.8.8 0 0 0-.761-.032zm-.038-32.648L457 70.814v1.818l.082-.047L570.994 7.298 685 72.638v-1.824L571.349 5.68a.81.81 0 0 0-.704 0h-.003l-.043.022Zm-.001 54.448L457 125.256v1.817l.082-.046L571 61.751l114 65.334v-1.824l-113.594-65.1a.8.8 0 0 0-.808-.01m.039-43.578L457 81.7v1.817l.082-.046L571 18.19l114 65.34V81.7L571.349 16.573a.81.81 0 0 0-.705 0zM616.814 197 685 157.925v1.823L620 197zm38.002 0L685 179.702v1.824L657.996 197zm18.998 0L685 190.589v1.823L676.994 197zm-75.752-.14L685 147.039v1.823L601.002 197h-3.185zm37.756.14L685 168.817v1.823L639.003 197zm-56.766-.14L685 136.142v1.823L581.987 197h-3.18zm-190.238.14L457 157.925v1.823L392 197zm38.002 0L457 179.702v1.824L429.996 197zm18.998 0L457 190.589v1.823L448.994 197zm-75.752-.14L457 147.039v1.823L373.002 197h-3.185zm37.756.14L457 168.817v1.823L411.003 197zm-56.766-.14L457 136.142v1.823L353.987 197h-3.18z"/>
+  <path fill="#000" d="M342.637 170.541 229 105.408v-1.817l.082.047L343 168.918l114-65.333v1.823l-113.594 65.1a.8.8 0 0 1-.376.113.8.8 0 0 1-.385-.08zm-.035-21.798L229 83.636v-1.818l.082.047L343 147.14l114-65.339v1.824L343.406 148.73a.7.7 0 0 1-.17.074.5.5 0 0 1-.147.027.77.77 0 0 1-.487-.088m.035 10.906L229 94.522v-1.817l.082.046 113.912 65.281L457 92.693v1.824l-113.594 65.1a.8.8 0 0 1-.761.033zm-.038 32.648L229 127.186v-1.817l.082.046 113.912 65.287L457 125.363v1.823l-113.651 65.133a.81.81 0 0 1-.704 0h-.003zm-.001-54.448L229 72.744v-1.817l.082.046L343 136.25l114-65.334v1.824l-113.594 65.1a.81.81 0 0 1-.808.01Zm.039 43.578L229 116.3v-1.817l.082.046L343 179.81l114-65.339v1.829l-113.651 65.127a.8.8 0 0 1-.705 0zM115.363 27.459 229 92.592v1.817l-.082-.047L115 29.082 1 94.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L229 114.364v1.818l-.082-.047L115 50.86 1 116.199v-1.824L114.594 49.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.906L229 103.478v1.817l-.082-.046-113.912-65.281L1 105.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.032zm.038-32.648L229 70.814v1.818l-.082-.047L115.006 7.298 1 72.638v-1.824L114.651 5.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L229 125.256v1.817l-.082-.046L115 61.751 1 127.085v-1.824l113.594-65.1a.81.81 0 0 1 .808-.01m-.039-43.578L229 81.7v1.817l-.082-.046L115 18.19 1 83.53V81.7l113.651-65.127a.81.81 0 0 1 .705 0z"/>
+  <g fill="#000" clip-path="url(#a)">
+    <path d="M380.798 286.485c-.164-.216-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.262l-82.521 106.431-.05.075h2.154l81.261-104.78 75.832 97.784.164.206v-2.766l-75.177-96.922z"/>
+    <path d="M380.647 253.671a1.3 1.3 0 0 0-.189-.112 1.1 1.1 0 0 0-.454-.094c-.163 0-.327.037-.466.094l-.088.037v.009a.9.9 0 0 0-.264.226L271.32 392.925l-.05.075h2.154l106.58-137.453 75.845 97.793.164.207v-2.776l-75.202-96.959a2 2 0 0 0-.164-.141"/>
+    <path d="M380.798 270.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.96.96 0 0 0-.353.263L283.98 392.925l-.051.075h2.142l93.933-121.117 75.832 97.794.164.206v-2.776l-75.177-96.921z"/>
+    <path d="M380.798 221.148c-.164-.215-.479-.347-.806-.347-.164 0-.315.028-.466.094a.95.95 0 0 0-.353.263L245.988 392.925l-.05.075h2.141l131.925-170.117 75.832 97.784.164.207v-2.776l-75.177-96.922z"/>
+    <path d="M380.823 237.41h-.088l-.013-.01-.012-.037-.076-.028a.5.5 0 0 0-.088-.057c-.025-.009-.05-.028-.088-.046a.5.5 0 0 0-.113-.038.7.7 0 0 0-.227-.047c-.051-.009-.088-.009-.126-.009-.063 0-.126.009-.177.018-.025 0-.063.01-.113.019l-.101.028c-.025.01-.05.01-.075.029l-.088.037c-.051.019-.076.047-.101.066l-.126.075v.037c-.013.019-.038.038-.051.056L258.635 392.925l-.05.075h2.154l119.265-153.78 75.832 97.784.164.206v-2.776l-75.177-96.921zm-.428-.038s0-.009 0 0"/>
+    <path d="m235.407 393 144.597-186.444 75.832 97.794.164.206v-2.785l-71.159-91.754-4.005-5.168-.026-.037c-.163-.216-.478-.347-.806-.347-.163 0-.315.028-.466.094a.95.95 0 0 0-.352.262l-145.87 188.104-.063.075z"/>
+  </g>
+  <path fill="#000" d="M228 301.782v2.768L159.406 393h-2.146l70.576-91.007zm0 81.667L220.592 393h2.147l5.261-6.783zm-.164-65.123L169.926 393h2.147L228 320.883v-2.768zm0 16.334L182.592 393h2.146L228 337.217v-2.768zm0 32.666L207.925 393h2.148L228 369.884v-2.769zm0-16.333L195.259 393h2.146L228 353.55v-2.768z"/>
+  <path fill="#fff" d="M0 369.884v-2.768L131.927 197h2.146L.164 369.673zm.164 16.122L146.74 197h-2.146L0 383.449v2.768zm0-49L108.741 197h-2.147L0 334.45v2.767zm0 16.333L121.408 197h-2.147L0 350.783v2.767zm0-32.666L96.074 197h-2.146L0 318.116v2.768zm0-16.333L83.41 197h-2.147L0 301.783v2.768zM0 288.218v-2.768L68.594 197h2.147L.164 288.007zm0-81.667L7.408 197H5.26L0 203.783zm.164 65.122L58.074 197h-2.147L0 269.117v2.767zm0-16.333L45.408 197h-2.146L0 252.783v2.768zm0-32.667L20.074 197h-2.147L0 220.116v2.768zm0 16.334L32.742 197h-2.147L0 236.45v2.768z"/>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 197h228v196H228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/logo-hashicorp.svg b/content/nomad/v1.9.x/img/logo-hashicorp.svg
new file mode 100644
index 0000000000..c9aa55e464
--- /dev/null
+++ b/content/nomad/v1.9.x/img/logo-hashicorp.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 317 132">
+  <path d="M125 61.42V92h-7.44V51.68h10.16L143 82.29V51.68h7.44V92h-10.16Zm43.58 31.16c-10.1 0-12.82-5.57-12.82-11.62v-7.44c0-6 2.72-11.61 12.82-11.61s12.83 5.56 12.83 11.61V81c0 6-2.72 11.58-12.83 11.58m0-24.38c-3.93 0-5.44 1.75-5.44 5.08v7.92c0 3.33 1.51 5.09 5.44 5.09S174 84.53 174 81.2v-7.92c0-3.28-1.48-5.08-5.42-5.08M203.85 92V71.4c0-1.57-.67-2.36-2.36-2.36s-5 1.09-7.68 2.48V92h-7.38V62.51h5.62l.73 2.48a29.6 29.6 0 0 1 11.8-3.08c2.84 0 4.59 1.15 5.56 3.14A29 29 0 0 1 222 61.91c4.9 0 6.65 3.44 6.65 8.71V92h-7.38V71.4c0-1.57-.66-2.36-2.36-2.36a19.55 19.55 0 0 0-7.68 2.48V92Zm52.69 0h-6.05l-.55-2a16.15 16.15 0 0 1-8.77 2.6c-5.38 0-7.68-3.69-7.68-8.77 0-6 2.6-8.29 8.59-8.29h7.08v-3.11c0-3.26-.91-4.41-5.63-4.41a41.6 41.6 0 0 0-8.17.9l-.9-5.62a38.3 38.3 0 0 1 10.1-1.39c9.25 0 12 3.26 12 10.64Zm-7.38-11.13h-5.45c-2.42 0-3.08.67-3.08 2.91 0 2 .66 3 3 3a11.7 11.7 0 0 0 5.57-1.51Zm11.91-8.56c0-6.53 2.9-10.4 9.74-10.4a41 41 0 0 1 7.87.84V50.47l7.38-1V92h-5.87l-.73-2.48a15.46 15.46 0 0 1-9.31 3.09c-5.93 0-9.08-3.51-9.08-10.23ZM278.68 69a33 33 0 0 0-6.54-.78c-2.66 0-3.69 1.27-3.69 3.93v10.39c0 2.42.91 3.75 3.63 3.75a10.43 10.43 0 0 0 6.6-2.67Z"/>
+  <path fill="#00ca8e" d="M61.14 38.19 32 55v33.63l29.12 16.81 29.14-16.81V55Zm13 37-7.76 4.48L57 74.54v10.72l-8.81 5.59v-22.4l7-4.28 9.7 5.11V58.34l9.25-5.56Z"/>
+  <path d="M125.42 41.81v-5.66h-5.17v5.66h-2.64V28.22h2.64v5.7h5.17v-5.7h2.65v13.59Zm12.33 0h-2.1l-.19-.67a5.7 5.7 0 0 1-3 .87c-1.86 0-2.66-1.23-2.66-2.92 0-2 .9-2.76 3-2.76h2.45v-1c0-1.09-.31-1.47-1.95-1.47a15 15 0 0 0-2.83.3l-.31-1.87a14 14 0 0 1 3.5-.46c3.2 0 4.15 1.08 4.15 3.54Zm-2.56-3.7h-1.89c-.83 0-1.06.22-1.06 1s.23 1 1 1a4 4 0 0 0 1.93-.51ZM143.1 42a12.6 12.6 0 0 1-3.52-.56l.36-1.88a11.5 11.5 0 0 0 3 .43c1.13 0 1.3-.24 1.3-1s-.13-.9-1.78-1.29c-2.5-.58-2.79-1.18-2.79-3.08s.9-2.83 3.81-2.83a14 14 0 0 1 3.06.34l-.25 2a19 19 0 0 0-2.81-.28c-1.11 0-1.3.24-1.3.84 0 .79.07.85 1.45 1.19 2.85.73 3.12 1.09 3.12 3.1S146.18 42 143.1 42m11.71-.2V35c0-.53-.23-.79-.82-.79a7.1 7.1 0 0 0-2.66.83v6.8h-2.56V28l2.56.38v4.34a9.3 9.3 0 0 1 3.73-.94c1.7 0 2.31 1.14 2.31 2.89v7.11Zm4.7-11.19v-2.4h2.56v2.4Zm0 11.19V32h2.56v9.8Zm4.6-9.72c0-2.46 1.49-3.88 5-3.88a16.5 16.5 0 0 1 3.79.44l-.29 2.19a21.5 21.5 0 0 0-3.42-.34c-1.82 0-2.41.6-2.41 2v5.15c0 1.43.59 2 2.41 2a21.6 21.6 0 0 0 3.42-.35l.29 2.2a16.5 16.5 0 0 1-3.79.44c-3.48 0-5-1.43-5-3.88ZM178.52 42c-3.5 0-4.44-1.85-4.44-3.86v-2.47c0-2 .94-3.86 4.44-3.86s4.48 1.85 4.48 3.86v2.48c0 2.01-1 3.85-4.48 3.85m0-8.11c-1.36 0-1.89.58-1.89 1.69v2.64c0 1.1.53 1.69 1.89 1.69s1.89-.59 1.89-1.69v-2.63c0-1.11-.53-1.69-1.89-1.69Zm11.64.16a20.5 20.5 0 0 0-2.7 1.43v6.32h-2.56V32h2.16l.17 1.08a11.5 11.5 0 0 1 2.68-1.28Zm10.22 4.49c0 2.17-1 3.46-3.37 3.46a15 15 0 0 1-2.73-.28v4l-2.55.38V32h2l.25.82a5.54 5.54 0 0 1 3.23-1c2 0 3.14 1.16 3.14 3.4Zm-6.1 1.11a12 12 0 0 0 2.27.26c.92 0 1.28-.43 1.28-1.31v-3.45c0-.81-.32-1.25-1.26-1.25a3.68 3.68 0 0 0-2.29.89Z"/>
+</svg>
diff --git a/content/nomad/v1.9.x/img/logo-text.svg b/content/nomad/v1.9.x/img/logo-text.svg
new file mode 100644
index 0000000000..49c064315f
--- /dev/null
+++ b/content/nomad/v1.9.x/img/logo-text.svg
@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 207 60">
+  <g fill="none">
+    <path fill="#25BA81" d="M26.03.01 0 15.05l17.56 10.32 3.56-2.17 8.63 4.82v-10l8.27-4.97v10.02l14.48-8.02v-.04" class="top"/>
+    <path fill="#25BA81" d="M22.75 32.03v9.99l-7.88 5v-20l2.99-1.83L.15 15.05H0v29.96l26.25 15V34.03" class="left"/>
+    <path fill="#1F9967" d="M38.02 23.07v9.95l-6.93 4.01-4.84-3v25.98h.14l26.11-15V15.05l-.49-.01" class="right"/>
+    <path fill="#000" d="M78.49 21.83v24.24h-5.9v-32h8.06l12.14 24.32V14.1h5.9v32h-8.06m22.46.45c-8 0-10.18-4.42-10.18-9.22v-5.9c0-4.8 2.16-9.22 10.18-9.22s10.18 4.42 10.18 9.22v5.91c0 4.79-2.16 9.21-10.18 9.21m0-19.35c-3.12 0-4.32 1.39-4.32 4v6.29c0 2.64 1.2 4 4.32 4s4.32-1.39 4.32-4v-6.25c0-2.64-1.2-4.04-4.32-4.04m27.99 18.87V29.75c0-1.25-.53-1.87-1.87-1.87a16.2 16.2 0 0 0-6.1 2v16.19h-5.86V22.69h4.46l.58 2a23.4 23.4 0 0 1 9.36-2.45 4.44 4.44 0 0 1 4.42 2.5 23 23 0 0 1 9.41-2.5c3.89 0 5.28 2.74 5.28 6.91v16.92h-5.86V29.75c0-1.25-.53-1.87-1.87-1.87-2.15.234-4.23.915-6.1 2v16.19zm41.81 0h-4.8l-.43-1.58a12.8 12.8 0 0 1-7 2.06c-4.27 0-6.1-2.93-6.1-7 0-4.75 2.06-6.58 6.82-6.58H177v-2.41c0-2.59-.72-3.5-4.46-3.5-2.18.024-4.35.265-6.48.72l-.72-4.46a30.5 30.5 0 0 1 8-1.1c7.34 0 9.5 2.59 9.5 8.45zM177 37.24h-4.32c-1.92 0-2.45.53-2.45 2.3s.53 2.35 2.35 2.35a9.2 9.2 0 0 0 4.42-1.2zm9.48-6.77c0-5.18 2.3-8.26 7.73-8.26 2.097.02 4.187.244 6.24.67v-9.74l5.86-.82v33.75h-4.66l-.58-2a12.3 12.3 0 0 1-7.39 2.45c-4.7 0-7.2-2.79-7.2-8.11zm14-2.64a26 26 0 0 0-5.18-.62c-2.11 0-2.93 1-2.93 3.12v8.26c0 1.92.72 3 2.88 3a8.28 8.28 0 0 0 5.23-2.11z" class="text"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.9.x/img/networking/bridge.png b/content/nomad/v1.9.x/img/networking/bridge.png
new file mode 100644
index 0000000000..9fe7fc60c5
Binary files /dev/null and b/content/nomad/v1.9.x/img/networking/bridge.png differ
diff --git a/content/nomad/v1.9.x/img/networking/docker_bridge.png b/content/nomad/v1.9.x/img/networking/docker_bridge.png
new file mode 100644
index 0000000000..8fc184beda
Binary files /dev/null and b/content/nomad/v1.9.x/img/networking/docker_bridge.png differ
diff --git a/content/nomad/v1.9.x/img/networking/port_mapping.png b/content/nomad/v1.9.x/img/networking/port_mapping.png
new file mode 100644
index 0000000000..a9eeaff6e1
Binary files /dev/null and b/content/nomad/v1.9.x/img/networking/port_mapping.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-architecture-global.png b/content/nomad/v1.9.x/img/nomad-architecture-global.png
new file mode 100644
index 0000000000..200b212378
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-architecture-global.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-architecture-region.png b/content/nomad/v1.9.x/img/nomad-architecture-region.png
new file mode 100644
index 0000000000..76d15dd5dd
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-architecture-region.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-bg-pattern.svg b/content/nomad/v1.9.x/img/nomad-bg-pattern.svg
new file mode 100644
index 0000000000..e9f71f1ff5
--- /dev/null
+++ b/content/nomad/v1.9.x/img/nomad-bg-pattern.svg
@@ -0,0 +1,24 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1800" height="543" fill="none" viewBox="0 0 1800 543">
+  <clipPath id="a">
+    <path d="M0 362h209v181H0z"/>
+  </clipPath>
+  <clipPath id="b">
+    <path d="M1382 362h209v181h-209z"/>
+  </clipPath>
+  <clipPath id="c">
+    <path d="M1591 362h209v181h-209z"/>
+  </clipPath>
+  <g fill="#60dea9">
+    <path d="M62.504 181 0 144.915v1.684L59.584 181zm-34.835 0L0 165.026v1.684L24.754 181zm-17.415 0L0 175.079v1.684L7.339 181zm69.44-.13L0 134.862v1.684L76.998 181h2.92zm-34.61.13L0 154.973v1.684L42.164 181zm52.035-.13L0 124.799v1.684L94.429 181h2.915zm7.714-24.304L209 96.418v-1.679l-.075.044L104.5 155.067 0 94.734v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.032-20.13L209 76.312v-1.679l-.075.043-104.425 60.28L0 74.617v1.684l104.127 60.123a.65.65 0 0 0 .292.094.7.7 0 0 0 .446-.082m-.032 10.072L209 86.365v-1.679l-.075.043-104.42 60.285L0 84.676v1.684l104.127 60.118a.73.73 0 0 0 .699.03zm.035 30.149L209 116.529v-1.679l-.075.044-104.42 60.29L0 114.845v1.684l104.18 60.148a.74.74 0 0 0 .646 0h.002zm.001-50.281L209 66.254v-1.679l-.075.043-104.425 60.28L0 64.565v1.683l104.127 60.118a.74.74 0 0 0 .742.01m-.036 40.243L209 106.476v-1.678l-.075.043L104.5 165.125 0 104.787v1.689l104.18 60.143a.75.75 0 0 0 .646 0zM393.351 0h-2.952L209 104.731v1.704L393.126.13zm17.191.13L209 116.491v-1.704L407.816 0h2.951zm-52.25 0L209 86.325v-1.704L355.566 0h2.951zm17.417 0L209 96.38v-1.703L372.983 0h2.951zm-34.833 0L209 76.27v-1.705L338.149 0h2.952zm-17.417 0L209 66.215V64.51L320.733 0h2.951zM233.649 181h2.952L418 76.269v-1.705L233.874 180.87zm-17.191-.131L418 64.509v1.704L219.184 181h-2.951zm52.25 0L418 94.675v1.704L271.434 181h-2.951zm-17.417 0L418 84.619v1.704L254.017 181h-2.951zm34.833 0L418 104.73v1.705L288.851 181h-2.952zm17.417 0L418 114.785v1.704L306.267 181h-2.951zM1406.65 0h2.95L1591 104.731v1.704L1406.87.13zm-17.19.13L1591 116.491v-1.704L1392.18 0h-2.95zm52.25 0L1591 86.325v-1.704L1444.43 0h-2.95zm-17.42 0L1591 96.38v-1.703L1427.02 0h-2.95zm34.83 0L1591 76.27v-1.705L1461.85 0h-2.95zm17.42 0L1591 66.215V64.51L1479.27 0h-2.95zM1566.35 181h-2.95L1382 76.269v-1.705l184.13 106.305zm17.19-.131L1382 64.509v1.704L1580.82 181h2.95zm-52.25 0L1382 94.675v1.704L1528.57 181h2.95zm17.42 0L1382 84.619v1.704L1545.98 181h2.95zm-34.83 0L1382 104.73v1.705L1511.15 181h2.95zm-17.42 0L1382 114.785v1.704L1493.73 181h2.95zm157.04.131-62.5-36.085v1.684L1650.58 181zm-34.83 0L1591 165.026v1.684l24.75 14.29zm-17.42 0-10.25-5.921v1.684l7.34 4.237zm69.44-.13L1591 134.862v1.684L1668 181h2.92zm-34.61.13L1591 154.973v1.684L1633.16 181zm52.04-.13L1591 124.799v1.684L1685.43 181h2.91zm7.71-24.304L1800 96.418v-1.679l-.07.044-104.43 60.284L1591 94.734v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 76.312v-1.679l-.07.043-104.43 60.28L1591 74.617v1.684l104.13 60.123q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 86.365v-1.679l-.07.043-104.42 60.285L1591 84.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 116.529v-1.679l-.07.044-104.42 60.29L1591 114.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 66.254v-1.679l-.07.043-104.43 60.28L1591 64.565v1.683l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 106.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M10.254 181 0 186.921v-1.684L7.339 181zm17.415 0L0 196.974v-1.684L24.754 181zm69.674 0L.075 237.158l-.075.043v-1.684L94.429 181zm-17.425 0L.075 227.094l-.075.044v-1.684L76.998 181zm-34.834 0L0 207.026v-1.683L42.163 181zm17.42 0L0 217.085v-1.684L59.584 181zM.075 307.351l-.075.043v-1.679l104.136-60.13a.8.8 0 0 1 .363-.091.7.7 0 0 1 .363.093L209 305.716v1.684l-104.506-60.339zm0 10.053-.075.043v-1.678l104.11-60.11.021-.013a.73.73 0 0 1 .731 0L209 315.769v1.689l-104.501-60.339zm0 10.058-.075.043v-1.678l104.137-60.132a.8.8 0 0 1 .362-.09c.128 0 .253.034.363.099L209 325.827v1.684l-104.506-60.339zm0 10.053-.075.043v-1.679l104.137-60.126a.8.8 0 0 1 .362-.09.7.7 0 0 1 .363.093L209 335.885v1.684L104.494 277.23zm0 20.111L0 357.67v-1.679l104.132-60.123.1-.05.007.006a.7.7 0 0 1 .26-.049.7.7 0 0 1 .363.098L209 355.996v1.684l-104.501-60.334zm0-10.059-.075.044v-1.678l104.136-60.126a.8.8 0 0 1 .363-.091c.128 0 .253.034.363.099L209 345.938v1.69l-104.501-60.34zm1695.755-10.001L1800 277.418v-1.678l-.07.043-104.43 60.284-104.5-60.333v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.03-20.13L1800 257.312v-1.679l-.07.043-104.43 60.28-104.5-60.339v1.685l104.13 60.122q.075.045.15.069a.5.5 0 0 0 .14.025.68.68 0 0 0 .44-.082m-.03 10.072L1800 267.365v-1.679l-.07.043-104.42 60.285L1591 265.676v1.684l104.13 60.118c.1.063.22.099.34.104s.25-.02.36-.074m.04 30.149L1800 297.529v-1.679l-.07.044-104.42 60.29L1591 295.845v1.684l104.18 60.148c.1.049.21.074.32.074s.23-.025.33-.074zm0-50.281L1800 247.254v-1.679l-.07.043-104.43 60.28-104.5-60.334v1.684l104.13 60.118a.74.74 0 0 0 .74.01m-.04 40.243L1800 287.476v-1.678l-.07.043-104.43 60.284-104.5-60.338v1.689l104.18 60.143a.74.74 0 0 0 .65 0M1653.5 181l-62.5 36.085v-1.684L1650.58 181zm-34.83 0L1591 196.974v-1.684l24.75-14.29zm-17.42 0-10.25 5.921v-1.684l7.34-4.237zm69.44.13L1591 227.138v-1.684L1668 181h2.92zm-34.61-.13L1591 207.027v-1.684L1633.16 181zm52.04.13L1591 237.201v-1.684L1685.43 181h2.91z"/>
+    <g clip-path="url(#a)">
+      <path d="M111.732 543h2.952L209 488.546v-1.704l-97.043 56.028zm87.084 0L209 537.119v1.704L201.767 543zm-69.442-.13L209 496.897v1.705L132.1 543h-2.951zm17.416 0L209 506.952v1.704L149.517 543h-2.952zm34.834 0L209 527.063v1.705L184.35 543h-2.951zm-17.417 0L209 517.008v1.704L166.933 543h-2.951zm44.718-136.429L0 527.065v1.703l.075-.043L209 408.103v-1.706zm.075-10.098v1.704L.075 518.67l-.075.044v-1.704l208.925-120.624zm0 20.11v1.705L.075 538.781l-.075.043v-1.703l208.925-120.624zm0-30.166v1.704L.075 508.615l-.075.043v-1.704l208.925-120.623zm0-10.056v1.705L.075 498.559l-.075.043v-1.704l208.925-120.623zm0-10.055v1.704L.075 488.503l-.075.044v-1.704l208.925-120.624z"/>
+    </g>
+    <path d="M209.075 406.441 418 527.065v1.704l-.075-.044L209 408.103v-1.706zM209 396.343v1.704L417.925 518.67l.075.044v-1.704L209.075 396.386zm0 20.11v1.705l208.925 120.623.075.043v-1.703L209.075 416.497zm0-30.166v1.704l208.925 120.624.075.043v-1.704L209.075 386.331zm0-10.056v1.705l208.925 120.623.075.044v-1.705L209.075 376.275zm0-10.055v1.704l208.925 120.623.075.044v-1.704L209.075 366.219z"/>
+    <g clip-path="url(#b)">
+      <path d="M1493.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1514.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1531.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1566.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1548.93 543h-2.95zm44.71-136.429L1382 527.065v1.703l.08-.043L1591 408.103v-1.706zm.08-10.098v1.704L1382.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path d="M1702.73 543h2.95l94.32-54.454v-1.704l-97.04 56.028zm87.09 0 10.18-5.881v1.704l-7.23 4.177zm-69.45-.13 79.63-45.973v1.705L1723.1 543h-2.95zm17.42 0 62.21-35.918v1.704L1740.52 543h-2.95zm34.83 0 27.38-15.807v1.705L1775.35 543h-2.95zm-17.41 0 44.79-25.862v1.704L1757.93 543h-2.95zm44.71-136.429L1591 527.065v1.703l.08-.043L1800 408.103v-1.706zm.08-10.098v1.704L1591.08 518.67l-.08.044v-1.704l208.92-120.624zm0 20.11v1.705l-208.92 120.623-.08.043v-1.703l208.92-120.624zm0-30.166v1.704l-208.92 120.624-.08.043v-1.704l208.92-120.623zm0-10.056v1.705l-208.92 120.623-.08.043v-1.704l208.92-120.623zm0-10.055v1.704l-208.92 120.623-.08.044v-1.704l208.92-120.624z"/>
+    </g>
+  </g>
+</svg>
diff --git a/content/nomad/v1.9.x/img/nomad-bridge-network.png b/content/nomad/v1.9.x/img/nomad-bridge-network.png
new file mode 100644
index 0000000000..b8b8f191d8
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-bridge-network.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-data-model.png b/content/nomad/v1.9.x/img/nomad-data-model.png
new file mode 100644
index 0000000000..811f30fa1f
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-data-model.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-evaluation-flow.png b/content/nomad/v1.9.x/img/nomad-evaluation-flow.png
new file mode 100644
index 0000000000..14d9ff18c0
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-evaluation-flow.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-kubernetes.png b/content/nomad/v1.9.x/img/nomad-kubernetes.png
new file mode 100644
index 0000000000..5033e10ab3
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-kubernetes.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-numa.png b/content/nomad/v1.9.x/img/nomad-numa.png
new file mode 100644
index 0000000000..0609d7e196
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-numa.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-panel-learn.svg b/content/nomad/v1.9.x/img/nomad-panel-learn.svg
new file mode 100644
index 0000000000..b35a8e420b
--- /dev/null
+++ b/content/nomad/v1.9.x/img/nomad-panel-learn.svg
@@ -0,0 +1,712 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="664" fill="none" viewBox="0 0 600 664" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".4" style="mix-blend-mode:luminosity">
+    <mask id="a" width="600" height="664" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 664h600V0H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="var(--gray-4, #bfbfc0)" d="M586.999 292.593c-.257 0-.429.063-.515.252-.171.252-.085.503.258.629l19.982 8.49c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.982-8.491c-.086 0-.172-.063-.343-.063m-19.983 8.491c-.257 0-.428.063-.514.251-.172.252-.086.504.257.629l39.965 16.919c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-39.965-16.918c-.085-.063-.257-.063-.343-.063m-19.982 8.428c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629l59.947 25.409c.343.125.686.063.858-.189s.085-.503-.258-.629l-59.947-25.409c-.086 0-.257-.062-.343-.062m-19.982 8.49c-.258 0-.429.063-.515.252-.171.251-.086.503.257.629l80.016 33.836c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-80.015-33.836c-.172-.063-.258-.063-.343-.063m-19.983 8.491c-.257 0-.429.062-.514.251-.172.252-.086.503.257.629L606.81 369.7c.343.126.686.063.857-.189.172-.252.086-.503-.257-.629l-99.998-42.327c-.171-.062-.257-.062-.343-.062m-19.982 8.427c-.257 0-.429.063-.515.252-.171.251-.085.503.258.629l119.98 50.817c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-119.98-50.817c-.172 0-.257-.063-.343-.063m-20.068 8.491c-.258 0-.429.063-.515.251-.171.252-.085.503.258.629l139.962 59.245c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-139.962-59.244c-.086-.063-.172-.063-.343-.063m-19.983 8.427c-.257 0-.428.063-.514.252-.172.251-.086.503.257.629l159.945 67.735c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-159.945-67.735c-.085 0-.257-.063-.343-.063m-19.982 8.491c-.257 0-.429.063-.515.251-.171.252-.085.503.258.629l179.927 76.163c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-179.927-76.163c-.086-.063-.257-.063-.343-.063m-19.982 8.49c-.258 0-.429.063-.515.252-.172.251-.086.503.257.629l199.996 84.653c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-199.995-84.654c-.172-.063-.258-.063-.343-.063"/>
+      <path fill="url(#b)" d="M606.982 656.616c-.086 0-.258 0-.343.063l-19.983 8.49c-.343.126-.428.441-.257.629.172.252.6.315.858.189l19.982-8.491c.343-.125.429-.44.257-.628 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#c)" d="M606.982 639.698c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#d)" d="M606.982 622.78c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#e)" d="M606.982 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#f)" d="M606.982 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#g)" d="M606.982 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.251-.514-.251"/>
+      <path fill="url(#h)" d="M606.982 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#i)" d="M606.982 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#j)" d="M606.982 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.687.063.858-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629 0-.188-.257-.251-.514-.251"/>
+      <path fill="url(#k)" d="M606.982 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#l)" d="M606.982 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.126-.257-.252-.514-.252"/>
+      <path fill="url(#m)" d="M606.982 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#n)" d="M606.982 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.687.063.858-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629 0-.189-.257-.252-.514-.252"/>
+      <path fill="url(#o)" d="M586.999 648.188c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#p)" d="M586.999 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#q)" d="M586.999 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#r)" d="M586.999 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#s)" d="M586.999 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#t)" d="M586.999 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#u)" d="M586.999 546.554c-.085 0-.257 0-.343.063l-20.926 8.931 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-18.954-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.172-.189-.343-.315-.601-.315"/>
+      <path fill="url(#v)" d="M586.999 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-18.954-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.172-.126-.343-.251-.601-.251"/>
+      <path fill="url(#w)" d="M586.999 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#x)" d="M586.999 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#y)" d="M586.999 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#z)" d="M586.999 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#A)" d="M586.999 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#B)" d="M567.017 656.615c-.086 0-.257 0-.343.063l-19.983 8.491c-.343.126-.429.44-.257.629.171.188.6.314.858.188l19.982-8.49c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#C)" d="M567.017 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#D)" d="M567.017 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#E)" d="M567.017 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#F)" d="M567.017 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#G)" d="M567.017 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#H)" d="M567.017 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#I)" d="M567.017 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#J)" d="M567.017 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#K)" d="M567.017 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#L)" d="M567.017 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#M)" d="M567.017 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#N)" d="M567.017 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#O)" d="M567.017 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.251-.515-.251"/>
+      <path fill="url(#P)" d="M547.034 648.188c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#Q)" d="M547.034 631.27c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#R)" d="M547.034 614.289c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#S)" d="M547.034 597.371c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#T)" d="M547.034 580.453c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.051c.343-.125.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#U)" d="M547.034 563.535c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.172-.252.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#V)" d="M547.034 546.554c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#W)" d="M547.034 529.636c-.085 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.628l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.251"/>
+      <path fill="url(#X)" d="M547.034 512.718c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Y)" d="M547.034 495.8c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#Z)" d="M547.034 478.882c-.085 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.172-.252.086-.504-.257-.629l-19.04-8.051 19.04-8.05c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.515-.251"/>
+      <path fill="url(#aa)" d="M547.034 461.9c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ab)" d="M547.034 444.982c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.515-.252"/>
+      <path fill="url(#ac)" d="M547.034 428.064c-.085 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.172-.251.086-.503-.257-.629l-19.04-8.05 19.04-8.05c.343-.126.429-.44.257-.629-.086-.189-.257-.252-.515-.252"/>
+      <path fill="url(#ad)" d="M527.052 639.698c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#ae)" d="M527.052 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#af)" d="M527.052 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ag)" d="M527.052 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ah)" d="M527.052 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251"/>
+      <path fill="url(#ai)" d="M527.052 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#aj)" d="M527.052 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#ak)" d="M527.052 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251"/>
+      <path fill="url(#al)" d="M527.052 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#am)" d="M527.052 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#an)" d="M527.052 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ao)" d="M527.052 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252"/>
+      <path fill="url(#ap)" d="M527.052 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.344-.251-.515-.251"/>
+      <path fill="url(#aq)" d="M507.07 631.27c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#ar)" d="M507.07 614.289c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.857-.188.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.125-.343-.251-.514-.251"/>
+      <path fill="url(#as)" d="M507.07 597.371c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#at)" d="M507.07 580.453c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#au)" d="M507.07 563.535c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#av)" d="M507.07 546.554c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#aw)" d="M507.07 529.636c-.086 0-.258 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.251-.514-.251"/>
+      <path fill="url(#ax)" d="M507.07 512.718c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#ay)" d="M507.07 495.8c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#az)" d="M507.07 478.882c-.086 0-.258 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.343-.251-.514-.251"/>
+      <path fill="url(#aA)" d="M507.07 461.9c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aB)" d="M507.07 444.982c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.126-.343-.252-.514-.252"/>
+      <path fill="url(#aC)" d="M507.07 428.064c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#aD)" d="M487.001 622.78c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aE)" d="M487.001 605.862c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aF)" d="M487.001 588.943c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aG)" d="M487.001 571.963c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.251-.515-.251"/>
+      <path fill="url(#aH)" d="M487.001 555.045c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aI)" d="M487.001 538.127c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.126.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aJ)" d="M487.001 521.209c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.629 0-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aK)" d="M487.001 504.227c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aL)" d="M487.001 487.309c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#aM)" d="M487.001 470.391c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aN)" d="M487.001 453.472c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aO)" d="M487.001 436.555c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.258-.628l-19.038-8.051 19.038-8.05c.344-.126.429-.44.258-.629 0-.189-.258-.251-.515-.251"/>
+      <path fill="url(#aP)" d="M467.019 614.289c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.867c.343.126.686.063.858-.188.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aQ)" d="M467.019 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aR)" d="M467.019 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aS)" d="M467.019 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.858-.189.171-.252.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#aT)" d="M467.019 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aU)" d="M467.019 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.251"/>
+      <path fill="url(#aV)" d="M467.019 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aW)" d="M467.019 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aX)" d="M467.019 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.858-.188.171-.252.085-.504-.258-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.258-.629-.086-.188-.258-.251-.515-.251"/>
+      <path fill="url(#aY)" d="M467.019 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#aZ)" d="M467.019 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629a.61.61 0 0 0-.515-.252"/>
+      <path fill="url(#ba)" d="M467.019 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bb)" d="M447.037 605.862c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bc)" d="M447.037 588.943c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bd)" d="M447.037 571.963c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#be)" d="M447.037 555.045c-.086 0-.258 0-.344.063l-20.925 8.867 20.925 8.868c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bf)" d="M447.037 538.127c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.126.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bg)" d="M447.037 521.209c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.867c.343.126.686.063.858-.188.171-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.629-.086-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bh)" d="M447.037 504.227c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bi)" d="M447.037 487.309c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bj)" d="M447.037 470.391c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.124-8.05c.344-.126.429-.44.258-.629-.172-.189-.343-.252-.6-.252"/>
+      <path fill="url(#bk)" d="M447.037 453.472c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bl)" d="M447.037 436.555c-.086 0-.258 0-.344.062l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189.171-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.428-.44.257-.629-.086-.189-.257-.251-.514-.251"/>
+      <path fill="url(#bm)" d="M427.054 597.371c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bn)" d="M427.054 580.453c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bo)" d="M427.054 563.535c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bp)" d="M427.054 546.554c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#bq)" d="M427.054 529.636c-.086 0-.257 0-.343.062l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.628l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.251"/>
+      <path fill="url(#br)" d="M427.054 512.718c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bs)" d="M427.054 495.8c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bt)" d="M427.054 478.882c-.086 0-.257 0-.343.063l-20.926 8.867 20.926 8.868c.343.126.686.063.857-.188.172-.252.086-.504-.257-.629l-19.039-8.051 19.039-8.05c.343-.126.429-.44.257-.629-.085-.188-.257-.251-.514-.251"/>
+      <path fill="url(#bu)" d="M427.054 461.9c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bv)" d="M427.054 444.982c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bw)" d="M427.054 428.064c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bx)" d="M447.037 419.574c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.428-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#by)" d="M427.054 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bz)" d="M487.001 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.051c.344-.125.429-.44.258-.628 0-.126-.258-.252-.515-.252"/>
+      <path fill="url(#bA)" d="M447.037 402.656c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.125.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bB)" d="M427.054 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.257-.629-.085-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bC)" d="M467.019 411.146c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bD)" d="M447.037 385.737c-.086 0-.258 0-.344.063l-20.925 8.868 20.925 8.868c.343.126.686.063.858-.189s.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.428-.441.257-.629-.086-.189-.257-.252-.514-.252"/>
+      <path fill="url(#bE)" d="M427.054 377.247c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.062.857-.189.172-.252.086-.503-.257-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.257-.628a.6.6 0 0 0-.514-.252"/>
+      <path fill="url(#bF)" d="M467.019 394.228c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.858-.189.171-.251.085-.503-.258-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.44.258-.629-.086-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bG)" d="M487.001 402.656c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.086-.503-.258-.629l-19.038-8.05 19.038-8.05c.344-.126.429-.441.258-.629 0-.189-.258-.252-.515-.252"/>
+      <path fill="url(#bH)" d="M507.07 411.146c-.086 0-.258 0-.343.063l-20.926 8.868 20.926 8.868c.343.126.686.063.857-.189.172-.251.086-.503-.257-.629l-19.039-8.05 19.039-8.05c.343-.126.429-.441.257-.629-.085-.189-.343-.252-.514-.252"/>
+      <path fill="url(#bI)" d="M527.052 419.574c-.086 0-.257 0-.343.063l-20.926 8.868 20.926 8.868c.343.125.686.063.858-.189s.085-.503-.258-.629l-19.039-8.05 19.039-8.051c.343-.125.429-.44.258-.628-.086-.126-.344-.252-.515-.252"/>
+      <path fill="url(#bJ)" d="M407.072 368.82c-.086 0-.257 0-.343.063L75.261 509.888c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 369.7c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 526.806c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 386.618c.343-.126.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 543.724c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 403.536c.343-.125.429-.44.258-.629-.086-.188-.344-.251-.515-.251m0 16.918c-.086 0-.257 0-.343.063L75.261 560.642c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 420.454c.343-.125.429-.44.258-.629-.086-.125-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.063L75.261 577.56c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 437.373c.343-.126.429-.441.258-.629-.086-.126-.344-.189-.515-.189m0 16.918c-.086 0-.257 0-.343.063L75.261 594.541c-.343.126-.429.44-.257.629.171.251.6.314.857.189L407.33 454.353c.343-.125.429-.44.258-.628-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 611.459c-.343.126-.429.44-.257.629.171.252.6.314.857.189l331.554-141.005c.343-.126.429-.441.257-.629a.84.84 0 0 0-.6-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 628.377c-.343.126-.429.44-.257.629.171.252.6.315.857.189L407.33 488.19c.343-.126.429-.441.258-.629-.086-.126-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 645.295c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 505.108c.343-.126.429-.44.258-.629-.086-.126-.344-.252-.515-.252m0 16.981c-.086 0-.257 0-.343.063L75.261 662.276c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 522.089c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 679.194c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 539.007c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.918c-.086 0-.257 0-.343.063L75.261 696.112c-.343.126-.429.441-.257.629.171.252.6.315.857.189L407.33 555.925c.343-.126.429-.44.258-.629-.086-.189-.344-.252-.515-.252m0 16.919c-.086 0-.257 0-.343.062L75.261 713.031c-.343.125-.429.44-.257.628.171.252.6.315.857.189L407.33 572.843c.343-.126.429-.44.258-.629-.086-.126-.344-.251-.515-.251m0 16.981c-.086 0-.257 0-.343.062L75.261 729.949c-.343.125-.429.44-.257.629.171.251.6.314.857.188L407.33 589.761c.343-.126.429-.44.258-.629-.086-.126-.344-.188-.515-.188m0 16.918c-.086 0-.257 0-.343.063L75.261 746.867c-.343.126-.429.44-.257.629.171.251.6.314.857.188L407.33 606.679c.343-.126.429-.44.258-.629-.086-.125-.344-.188-.515-.188m19.982 8.427c-.085 0-.257 0-.343.063L98.331 754.036c-.343.126-.429.441-.258.629.172.252.6.315.858.189L427.312 615.17c.343-.126.428-.441.257-.629a.6.6 0 0 0-.515-.252m19.983 8.491c-.086 0-.258 0-.343.063l-96.911 41.006c-.343.125-.429.44-.257.629.171.251.6.314.858.188l96.91-41.006c.343-.126.429-.44.257-.629-.086-.188-.257-.251-.514-.251m19.982 8.49c-.086 0-.257 0-.343.063l-76.842 32.578c-.343.126-.429.441-.257.629.171.252.6.315.857.189l76.842-32.578c.343-.126.429-.441.258-.629-.086-.189-.258-.252-.515-.252m19.982 8.428c-.085 0-.257 0-.342.063l-56.86 24.088c-.343.125-.429.44-.258.629.172.251.601.314.858.188l56.86-24.088c.343-.125.429-.44.257-.629 0-.125-.257-.251-.515-.251m20.069 8.49c-.086 0-.258 0-.343.063l-36.878 15.598c-.343.125-.429.44-.257.629.171.251.6.314.857.188l36.878-15.597c.343-.126.429-.44.257-.629-.086-.189-.343-.252-.514-.252m19.982 8.428c-.086 0-.257 0-.343.063l-16.895 7.17c-.343.125-.429.44-.257.629.171.251.6.314.857.188l16.895-7.17c.343-.125.429-.44.258-.628-.086-.126-.343-.252-.515-.252"/>
+      <path fill="url(#bK)" d="M606.981 64.042c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.441-.257.629.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.44.257-.63 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.653c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.44.258-.63-.086-.125-.343-.25-.601-.25m0 16.918c-.085 0-.257 0-.343.063l-199.909 84.716c-.343.126-.429.441-.258.629.172.252.601.315.858.189l199.995-84.653c.343-.126.429-.441.258-.629-.086-.189-.343-.315-.601-.315m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.628.171.252.6.315.857.189l199.996-84.653c.343-.126.428-.441.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.654c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.918c-.085 0-.257 0-.343.063L406.643 250.33c-.343.125-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.189-.257-.252-.515-.252m0 16.919c-.085 0-.257 0-.343.062l-199.995 84.654c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.126-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.251.6.314.857.188l199.996-84.653c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l199.996-84.654c.343-.126.428-.44.257-.629 0-.188-.257-.251-.515-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.314.857.189l200.081-84.654c.343-.125.429-.44.258-.629-.086-.188-.343-.251-.601-.251m0 16.918c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.125-.257-.251-.515-.251m0 16.981c-.085 0-.257 0-.343.063l-199.995 84.653c-.343.126-.429.44-.257.629.171.252.6.315.857.189l199.996-84.654c.343-.125.428-.44.257-.629 0-.188-.257-.251-.515-.251"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="586.315" x2="607.583" y1="661.333" y2="661.333" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="c" x1="585.714" x2="607.583" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="d" x1="585.714" x2="607.583" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="e" x1="585.714" x2="607.583" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="f" x1="585.714" x2="607.583" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="g" x1="585.714" x2="607.583" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="h" x1="585.714" x2="607.583" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="i" x1="585.714" x2="607.583" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="j" x1="585.714" x2="607.583" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="k" x1="585.714" x2="607.583" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="l" x1="585.714" x2="607.583" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="m" x1="585.714" x2="607.583" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="n" x1="585.714" x2="607.583" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="o" x1="565.732" x2="587.601" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="p" x1="565.732" x2="587.601" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="q" x1="565.732" x2="587.601" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="r" x1="565.732" x2="587.601" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="s" x1="565.732" x2="587.601" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="t" x1="565.732" x2="587.601" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="u" x1="565.732" x2="587.687" y1="555.516" y2="555.516" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="v" x1="565.732" x2="587.687" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="w" x1="565.732" x2="587.601" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="x" x1="565.732" x2="587.601" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="y" x1="565.732" x2="587.601" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="z" x1="565.732" x2="587.601" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="A" x1="565.732" x2="587.601" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="B" x1="546.349" x2="567.618" y1="661.326" y2="661.326" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="C" x1="545.749" x2="567.619" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="D" x1="545.749" x2="567.619" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="E" x1="545.749" x2="567.619" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="F" x1="545.749" x2="567.619" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="G" x1="545.749" x2="567.619" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="H" x1="545.749" x2="567.619" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="I" x1="545.749" x2="567.619" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="J" x1="545.749" x2="567.619" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="K" x1="545.749" x2="567.619" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="L" x1="545.749" x2="567.619" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="M" x1="545.749" x2="567.619" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="N" x1="545.749" x2="567.619" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="O" x1="545.749" x2="567.619" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="P" x1="525.767" x2="547.636" y1="657.119" y2="657.119" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="525.767" x2="547.636" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="R" x1="525.767" x2="547.636" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="S" x1="525.767" x2="547.636" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="T" x1="525.767" x2="547.636" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="U" x1="525.767" x2="547.636" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="V" x1="525.767" x2="547.636" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="W" x1="525.767" x2="547.636" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="X" x1="525.767" x2="547.636" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="525.767" x2="547.636" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="525.767" x2="547.636" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="525.767" x2="547.636" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="525.767" x2="547.636" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="525.767" x2="547.636" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="505.785" x2="527.654" y1="648.628" y2="648.628" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="505.785" x2="527.654" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="af" x1="505.785" x2="527.654" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="505.785" x2="527.654" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="505.785" x2="527.654" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="505.785" x2="527.654" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="505.785" x2="527.654" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ak" x1="505.785" x2="527.654" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="al" x1="505.785" x2="527.654" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="am" x1="505.785" x2="527.654" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="an" x1="505.785" x2="527.654" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ao" x1="505.785" x2="527.654" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ap" x1="505.785" x2="527.654" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aq" x1="485.802" x2="507.671" y1="640.201" y2="640.201" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ar" x1="485.802" x2="507.671" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="as" x1="485.802" x2="507.671" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="at" x1="485.802" x2="507.671" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="au" x1="485.802" x2="507.671" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="av" x1="485.802" x2="507.671" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aw" x1="485.802" x2="507.671" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ax" x1="485.802" x2="507.671" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ay" x1="485.802" x2="507.671" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="az" x1="485.802" x2="507.671" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aA" x1="485.802" x2="507.671" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aB" x1="485.802" x2="507.671" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aC" x1="485.802" x2="507.671" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aD" x1="465.734" x2="487.603" y1="631.71" y2="631.71" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aE" x1="465.734" x2="487.603" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aF" x1="465.734" x2="487.603" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aG" x1="465.734" x2="487.603" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aH" x1="465.734" x2="487.603" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aI" x1="465.734" x2="487.603" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aJ" x1="465.734" x2="487.603" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aK" x1="465.734" x2="487.603" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aL" x1="465.734" x2="487.603" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aM" x1="465.734" x2="487.603" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aN" x1="465.734" x2="487.603" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aO" x1="465.734" x2="487.603" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aP" x1="445.752" x2="467.621" y1="623.219" y2="623.219" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aQ" x1="445.752" x2="467.621" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aR" x1="445.752" x2="467.621" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aS" x1="445.752" x2="467.621" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aT" x1="445.752" x2="467.621" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aU" x1="445.752" x2="467.621" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aV" x1="445.752" x2="467.621" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aW" x1="445.752" x2="467.621" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aX" x1="445.752" x2="467.621" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aY" x1="445.752" x2="467.621" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aZ" x1="445.752" x2="467.621" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="ba" x1="445.752" x2="467.621" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bb" x1="425.769" x2="447.638" y1="614.792" y2="614.792" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bc" x1="425.769" x2="447.638" y1="597.873" y2="597.873" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bd" x1="425.769" x2="447.638" y1="580.893" y2="580.893" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="be" x1="425.769" x2="447.638" y1="563.975" y2="563.975" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bf" x1="425.769" x2="447.638" y1="547.057" y2="547.057" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bg" x1="425.769" x2="447.638" y1="530.139" y2="530.139" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bh" x1="425.769" x2="447.638" y1="513.158" y2="513.158" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bi" x1="425.769" x2="447.638" y1="496.24" y2="496.24" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bj" x1="425.769" x2="447.724" y1="479.322" y2="479.322" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bk" x1="425.769" x2="447.638" y1="462.403" y2="462.403" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bl" x1="425.769" x2="447.638" y1="445.485" y2="445.485" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bm" x1="405.787" x2="427.656" y1="606.301" y2="606.301" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bn" x1="405.787" x2="427.656" y1="589.383" y2="589.383" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bo" x1="405.787" x2="427.656" y1="572.465" y2="572.465" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bp" x1="405.787" x2="427.656" y1="555.484" y2="555.484" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bq" x1="405.787" x2="427.656" y1="538.566" y2="538.566" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="br" x1="405.787" x2="427.656" y1="521.648" y2="521.648" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bs" x1="405.787" x2="427.656" y1="504.73" y2="504.73" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bt" x1="405.787" x2="427.656" y1="487.812" y2="487.812" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bu" x1="405.787" x2="427.656" y1="470.831" y2="470.831" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bv" x1="405.787" x2="427.656" y1="453.913" y2="453.913" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bw" x1="405.787" x2="427.656" y1="436.995" y2="436.995" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bx" x1="425.769" x2="447.638" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="by" x1="405.787" x2="427.656" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bz" x1="465.734" x2="487.603" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bA" x1="425.769" x2="447.638" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bB" x1="405.787" x2="427.656" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bC" x1="445.752" x2="467.621" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bD" x1="425.769" x2="447.638" y1="394.667" y2="394.667" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bE" x1="405.787" x2="427.656" y1="386.177" y2="386.177" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bF" x1="445.752" x2="467.621" y1="403.159" y2="403.159" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bG" x1="465.734" x2="487.603" y1="411.586" y2="411.586" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bH" x1="485.802" x2="507.671" y1="420.077" y2="420.077" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bI" x1="505.785" x2="527.654" y1="428.504" y2="428.504" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bJ" x1="74.947" x2="527.679" y1="561.858" y2="561.858" gradientUnits="userSpaceOnUse">
+      <stop offset=".137" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".886" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="bK" x1="507.04" x2="507.04" y1="64.025" y2="369.743" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/nomad-pattern-gray_joined.svg b/content/nomad/v1.9.x/img/nomad-pattern-gray_joined.svg
new file mode 100644
index 0000000000..6957cdaad9
--- /dev/null
+++ b/content/nomad/v1.9.x/img/nomad-pattern-gray_joined.svg
@@ -0,0 +1,4273 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" id="Layer_1" x="0" y="0" version="1.1" viewBox="0 0 1920 1080">
+  <style>
+    .st291{opacity:.6}
+  </style>
+  <defs>
+    <path id="SVGID_1_" d="M0 0h1920v1080H0z"/>
+  </defs>
+  <clipPath id="SVGID_2_">
+    <use xlink:href="#SVGID_1_" overflow="visible"/>
+  </clipPath>
+  <g clip-path="url(#SVGID_2_)">
+    <linearGradient id="SVGID_3_" x1="474.43" x2="474.43" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_3_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_4_" x1="404.485" x2="404.485" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_4_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_5_" x1="381.17" x2="381.17" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_5_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_6_" x1="451.115" x2="451.115" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_6_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_7_" x1="427.8" x2="427.8" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_7_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_8_" x1="451.115" x2="451.115" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_8_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_9_" x1="427.8" x2="427.8" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_9_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 314.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_10_" x1="497.745" x2="497.745" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_10_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_11_" x1="474.43" x2="474.43" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_11_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_12_" x1="497.745" x2="497.745" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_12_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 288 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_13_" x1="474.43" x2="474.43" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_13_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 314.9-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_14_" x1="544.375" x2="544.375" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_14_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_15_" x1="521.06" x2="521.06" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_15_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_16_" x1="521.06" x2="521.06" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_16_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 314.9-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_17_" x1="567.69" x2="567.69" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_17_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 341.8 556 328.4" opacity=".6"/>
+    <linearGradient id="SVGID_18_" x1="311.225" x2="311.225" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_18_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_19_" x1="287.91" x2="287.91" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_19_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_20_" x1="357.855" x2="357.855" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_20_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_21_" x1="334.54" x2="334.54" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_21_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_22_" x1="357.855" x2="357.855" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_22_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_23_" x1="334.54" x2="334.54" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_23_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 368.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_24_" x1="404.485" x2="404.485" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_24_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_25_" x1="381.17" x2="381.17" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_25_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_26_" x1="404.485" x2="404.485" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_26_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 341.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_27_" x1="381.17" x2="381.17" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_27_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 368.7-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_28_" x1="451.115" x2="451.115" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_28_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_29_" x1="427.8" x2="427.8" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_29_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_30_" x1="451.115" x2="451.115" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_30_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 341.8 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_31_" x1="427.8" x2="427.8" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_31_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 368.7-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_32_" x1="497.745" x2="497.745" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_32_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_33_" x1="474.43" x2="474.43" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_33_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_34_" x1="497.745" x2="497.745" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_34_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 341.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_35_" x1="474.43" x2="474.43" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_35_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 368.7-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_36_" x1="544.375" x2="544.375" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_36_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_37_" x1="521.06" x2="521.06" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_37_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_38_" x1="544.375" x2="544.375" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_38_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 341.8 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_39_" x1="521.06" x2="521.06" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_39_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 368.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_40_" x1="591.005" x2="591.005" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_40_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 368.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_41_" x1="567.69" x2="567.69" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_41_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 395.7 556 382.2" opacity=".4"/>
+    <linearGradient id="SVGID_42_" x1="591.005" x2="591.005" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_42_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 341.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_43_" x1="567.69" x2="567.69" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_43_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 368.7 556 355.3" opacity=".5"/>
+    <linearGradient id="SVGID_44_" x1="637.635" x2="637.635" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_44_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_45_" x1="614.32" x2="614.32" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_45_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_46_" x1="614.32" x2="614.32" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_46_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 368.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_47_" x1="660.95" x2="660.95" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_47_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_48_" x1="217.965" x2="217.965" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_48_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 422.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_49_" x1="194.65" x2="194.65" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_49_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 449.5 183 436" opacity=".3"/>
+    <linearGradient id="SVGID_50_" x1="264.595" x2="264.595" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_50_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_51_" x1="241.28" x2="241.28" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_51_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 449.5 229.6 436" opacity=".9"/>
+    <linearGradient id="SVGID_52_" x1="264.595" x2="264.595" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_52_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_53_" x1="241.28" x2="241.28" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_53_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 422.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_54_" x1="311.225" x2="311.225" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_54_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_55_" x1="287.91" x2="287.91" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_55_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 449.5 276.2 436" opacity=".8"/>
+    <linearGradient id="SVGID_56_" x1="311.225" x2="311.225" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_56_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 395.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_57_" x1="287.91" x2="287.91" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_57_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 422.6-23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_58_" x1="357.855" x2="357.855" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_58_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_59_" x1="334.54" x2="334.54" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_59_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 449.5 322.9 436" opacity=".7"/>
+    <linearGradient id="SVGID_60_" x1="357.855" x2="357.855" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_60_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 395.7 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_61_" x1="334.54" x2="334.54" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_61_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 422.6-23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_62_" x1="404.485" x2="404.485" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_62_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_63_" x1="381.17" x2="381.17" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_63_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 449.5 369.5 436" opacity=".6"/>
+    <linearGradient id="SVGID_64_" x1="404.485" x2="404.485" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_64_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 395.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_65_" x1="381.17" x2="381.17" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_65_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 422.6-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_66_" x1="451.115" x2="451.115" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_66_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_67_" x1="427.8" x2="427.8" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_67_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 449.5 416.1 436" opacity=".5"/>
+    <linearGradient id="SVGID_68_" x1="451.115" x2="451.115" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_68_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 395.7 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_69_" x1="427.8" x2="427.8" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_69_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 422.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_70_" x1="497.745" x2="497.745" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_70_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_71_" x1="474.43" x2="474.43" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_71_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 449.5 462.8 436" opacity=".4"/>
+    <linearGradient id="SVGID_72_" x1="497.745" x2="497.745" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_72_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 395.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_73_" x1="474.43" x2="474.43" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_73_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 422.6-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_74_" x1="544.375" x2="544.375" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_74_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 422.6 556 436" opacity=".3"/>
+    <linearGradient id="SVGID_75_" x1="521.06" x2="521.06" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_75_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 509.4 436" opacity=".3"/>
+    <linearGradient id="SVGID_76_" x1="544.375" x2="544.375" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_76_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 395.7 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_77_" x1="521.06" x2="521.06" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_77_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 422.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_78_" x1="591.005" x2="591.005" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_78_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 422.6 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_79_" x1="567.69" x2="567.69" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_79_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 449.5 556 436" opacity=".2"/>
+    <linearGradient id="SVGID_80_" x1="591.005" x2="591.005" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_80_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 395.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_81_" x1="567.69" x2="567.69" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_81_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 422.6 556 409.1" opacity=".3"/>
+    <linearGradient id="SVGID_82_" x1="637.635" x2="637.635" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_82_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_83_" x1="614.32" x2="614.32" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_83_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M626 449.5 602.7 436" opacity=".1"/>
+    <linearGradient id="SVGID_84_" x1="637.635" x2="637.635" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_84_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 395.7 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_85_" x1="614.32" x2="614.32" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_85_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m626 422.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_86_" x1="684.265" x2="684.265" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_86_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 395.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_87_" x1="660.95" x2="660.95" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_87_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m672.6 422.6-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_88_" x1="171.335" x2="171.335" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_88_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 476.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_89_" x1="148.02" x2="148.02" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_89_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_90_" x1="171.335" x2="171.335" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_90_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 183 463" opacity=".3"/>
+    <linearGradient id="SVGID_91_" x1="148.02" x2="148.02" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_91_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 476.4 136.4 463" opacity=".3"/>
+    <linearGradient id="SVGID_92_" x1="217.965" x2="217.965" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_92_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 476.4 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_93_" x1="194.65" x2="194.65" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_93_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 503.3 183 489.9" opacity=".8"/>
+    <linearGradient id="SVGID_94_" x1="217.965" x2="217.965" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_94_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 449.5 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_95_" x1="194.65" x2="194.65" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_95_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 476.4 183 463" opacity=".9"/>
+    <linearGradient id="SVGID_96_" x1="264.595" x2="264.595" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_96_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 476.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_97_" x1="241.28" x2="241.28" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_97_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3-23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_98_" x1="264.595" x2="264.595" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_98_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 449.5 23.3 13.5" opacity=".8"/>
+    <linearGradient id="SVGID_99_" x1="241.28" x2="241.28" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_99_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 476.4 229.6 463" opacity=".8"/>
+    <linearGradient id="SVGID_100_" x1="311.225" x2="311.225" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_100_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 476.4 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_101_" x1="287.91" x2="287.91" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_101_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_102_" x1="311.225" x2="311.225" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_102_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 449.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_103_" x1="287.91" x2="287.91" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_103_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 476.4 276.2 463" opacity=".7"/>
+    <linearGradient id="SVGID_104_" x1="357.855" x2="357.855" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_104_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 476.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_105_" x1="334.54" x2="334.54" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_105_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_106_" x1="357.855" x2="357.855" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_106_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 449.5 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_107_" x1="334.54" x2="334.54" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_107_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 476.4 322.9 463" opacity=".6"/>
+    <linearGradient id="SVGID_108_" x1="404.485" x2="404.485" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_108_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 476.4 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_109_" x1="381.17" x2="381.17" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_109_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_110_" x1="404.485" x2="404.485" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_110_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 449.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_111_" x1="381.17" x2="381.17" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_111_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 476.4 369.5 463" opacity=".5"/>
+    <linearGradient id="SVGID_112_" x1="451.115" x2="451.115" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_112_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 476.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_113_" x1="427.8" x2="427.8" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_113_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_114_" x1="451.115" x2="451.115" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_114_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 449.5 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_115_" x1="427.8" x2="427.8" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_115_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 476.4 416.1 463" opacity=".4"/>
+    <linearGradient id="SVGID_116_" x1="497.745" x2="497.745" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_116_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 476.4 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_117_" x1="474.43" x2="474.43" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_117_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_118_" x1="497.745" x2="497.745" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_118_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 449.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_119_" x1="474.43" x2="474.43" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_119_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M486.1 476.4 462.8 463" opacity=".3"/>
+    <linearGradient id="SVGID_120_" x1="544.375" x2="544.375" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_120_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 476.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_121_" x1="521.06" x2="521.06" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_121_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m532.7 503.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_122_" x1="544.375" x2="544.375" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_122_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 449.5 556 463" opacity=".2"/>
+    <linearGradient id="SVGID_123_" x1="521.06" x2="521.06" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_123_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M532.7 476.4 509.4 463" opacity=".2"/>
+    <linearGradient id="SVGID_124_" x1="591.005" x2="591.005" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_124_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m579.3 449.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_125_" x1="567.69" x2="567.69" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_125_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M579.3 476.4 556 463" opacity=".1"/>
+    <linearGradient id="SVGID_126_" x1="171.335" x2="171.335" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_126_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_127_" x1="148.02" x2="148.02" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_127_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_128_" x1="171.335" x2="171.335" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_128_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 503.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_129_" x1="148.02" x2="148.02" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_129_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_130_" x1="217.965" x2="217.965" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_130_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 530.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_131_" x1="194.65" x2="194.65" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_131_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 557.2 183 543.7" opacity=".8"/>
+    <linearGradient id="SVGID_132_" x1="217.965" x2="217.965" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_132_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 503.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_133_" x1="194.65" x2="194.65" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_133_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 530.3 183 516.8" opacity=".8"/>
+    <linearGradient id="SVGID_134_" x1="264.595" x2="264.595" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_134_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_135_" x1="241.28" x2="241.28" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_135_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_136_" x1="264.595" x2="264.595" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_136_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 503.3 23.3 13.5" opacity=".6"/>
+    <linearGradient id="SVGID_137_" x1="241.28" x2="241.28" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_137_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 530.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_138_" x1="311.225" x2="311.225" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_138_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_139_" x1="287.91" x2="287.91" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_139_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_140_" x1="311.225" x2="311.225" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_140_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 503.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_141_" x1="287.91" x2="287.91" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_141_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 530.3-23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_142_" x1="357.855" x2="357.855" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_142_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_143_" x1="334.54" x2="334.54" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_143_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_144_" x1="357.855" x2="357.855" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_144_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 503.3 23.3 13.5" opacity=".4"/>
+    <linearGradient id="SVGID_145_" x1="334.54" x2="334.54" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_145_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 530.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_146_" x1="404.485" x2="404.485" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_146_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_147_" x1="381.17" x2="381.17" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_147_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_148_" x1="404.485" x2="404.485" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_148_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 503.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_149_" x1="381.17" x2="381.17" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_149_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 530.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_150_" x1="451.115" x2="451.115" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_150_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_151_" x1="427.8" x2="427.8" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_151_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 557.2-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_152_" x1="451.115" x2="451.115" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_152_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 503.3 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_153_" x1="427.8" x2="427.8" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_153_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 530.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_154_" x1="497.745" x2="497.745" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_154_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 503.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_155_" x1="474.43" x2="474.43" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_155_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m486.1 530.3-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_156_" x1="171.335" x2="171.335" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_156_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_157_" x1="148.02" x2="148.02" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_157_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_158_" x1="171.335" x2="171.335" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_158_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 557.2 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_159_" x1="148.02" x2="148.02" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_159_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 584.1-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_160_" x1="217.965" x2="217.965" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_160_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 584.1 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_161_" x1="194.65" x2="194.65" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_161_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 611 183 597.6" opacity=".8"/>
+    <linearGradient id="SVGID_162_" x1="217.965" x2="217.965" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_162_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 557.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_163_" x1="194.65" x2="194.65" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_163_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 584.1 183 570.7" opacity=".8"/>
+    <linearGradient id="SVGID_164_" x1="264.595" x2="264.595" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_164_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_165_" x1="241.28" x2="241.28" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_165_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_166_" x1="264.595" x2="264.595" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_166_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 557.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_167_" x1="241.28" x2="241.28" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_167_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 584.1-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_168_" x1="311.225" x2="311.225" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_168_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_169_" x1="287.91" x2="287.91" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_169_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_170_" x1="311.225" x2="311.225" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_170_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 557.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_171_" x1="287.91" x2="287.91" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_171_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 584.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_172_" x1="357.855" x2="357.855" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_172_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_173_" x1="334.54" x2="334.54" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_173_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_174_" x1="357.855" x2="357.855" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_174_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 557.2 23.3 13.5" opacity=".2"/>
+    <linearGradient id="SVGID_175_" x1="334.54" x2="334.54" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_175_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 584.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_176_" x1="404.485" x2="404.485" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_176_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 557.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_177_" x1="381.17" x2="381.17" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_177_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 584.1-23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_178_" x1="171.335" x2="171.335" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_178_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_179_" x1="148.02" x2="148.02" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_179_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_180_" x1="171.335" x2="171.335" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_180_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 611 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_181_" x1="148.02" x2="148.02" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_181_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 638-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_182_" x1="217.965" x2="217.965" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_182_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 638 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_183_" x1="194.65" x2="194.65" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_183_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 664.9 183 651.4" opacity=".8"/>
+    <linearGradient id="SVGID_184_" x1="217.965" x2="217.965" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_184_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 611 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_185_" x1="194.65" x2="194.65" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_185_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 638 183 624.5" opacity=".8"/>
+    <linearGradient id="SVGID_186_" x1="264.595" x2="264.595" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_186_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_187_" x1="241.28" x2="241.28" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_187_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_188_" x1="264.595" x2="264.595" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_188_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 611 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_189_" x1="241.28" x2="241.28" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_189_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 638-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_190_" x1="311.225" x2="311.225" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_190_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_191_" x1="287.91" x2="287.91" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_191_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_192_" x1="311.225" x2="311.225" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_192_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 611 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_193_" x1="287.91" x2="287.91" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_193_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 638-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_194_" x1="357.855" x2="357.855" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_194_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_195_" x1="334.54" x2="334.54" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_195_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_196_" x1="357.855" x2="357.855" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_196_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 611 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_197_" x1="334.54" x2="334.54" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_197_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 638-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_198_" x1="171.335" x2="171.335" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_198_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_199_" x1="148.02" x2="148.02" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_199_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_200_" x1="171.335" x2="171.335" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_200_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 664.9 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_201_" x1="148.02" x2="148.02" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_201_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 691.8-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_202_" x1="217.965" x2="217.965" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_202_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 691.8 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_203_" x1="194.65" x2="194.65" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_203_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 718.7 183 705.3" opacity=".8"/>
+    <linearGradient id="SVGID_204_" x1="217.965" x2="217.965" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_204_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 664.9 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_205_" x1="194.65" x2="194.65" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_205_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 691.8 183 678.3" opacity=".8"/>
+    <linearGradient id="SVGID_206_" x1="264.595" x2="264.595" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_206_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_207_" x1="241.28" x2="241.28" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_207_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_208_" x1="264.595" x2="264.595" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_208_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 664.9 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_209_" x1="241.28" x2="241.28" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_209_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 691.8-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_210_" x1="311.225" x2="311.225" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_210_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_211_" x1="287.91" x2="287.91" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_211_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_212_" x1="311.225" x2="311.225" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_212_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 664.9 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_213_" x1="287.91" x2="287.91" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_213_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 691.8-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_214_" x1="357.855" x2="357.855" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_214_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_215_" x1="334.54" x2="334.54" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_215_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_216_" x1="357.855" x2="357.855" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_216_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 664.9 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_217_" x1="334.54" x2="334.54" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_217_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 691.8-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_218_" x1="171.335" x2="171.335" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_218_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_219_" x1="148.02" x2="148.02" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_219_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 772.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_220_" x1="171.335" x2="171.335" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_220_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 718.7 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_221_" x1="148.02" x2="148.02" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_221_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 745.6-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_222_" x1="217.965" x2="217.965" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_222_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 745.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_223_" x1="194.65" x2="194.65" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_223_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 772.6 183 759.1" opacity=".8"/>
+    <linearGradient id="SVGID_224_" x1="217.965" x2="217.965" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_224_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 718.7 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_225_" x1="194.65" x2="194.65" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_225_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 745.6 183 732.2" opacity=".8"/>
+    <linearGradient id="SVGID_226_" x1="264.595" x2="264.595" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_226_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_227_" x1="241.28" x2="241.28" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_227_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_228_" x1="264.595" x2="264.595" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_228_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 718.7 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_229_" x1="241.28" x2="241.28" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_229_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 745.6-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_230_" x1="311.225" x2="311.225" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_230_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_231_" x1="287.91" x2="287.91" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_231_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_232_" x1="311.225" x2="311.225" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_232_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 718.7 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_233_" x1="287.91" x2="287.91" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_233_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 745.6-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_234_" x1="357.855" x2="357.855" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_234_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_235_" x1="334.54" x2="334.54" y1="320.9" y2="307.44" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_235_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_236_" x1="357.855" x2="357.855" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_236_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 718.7 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_237_" x1="334.54" x2="334.54" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_237_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 745.6-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_238_" x1="171.335" x2="171.335" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_238_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 183 813" opacity=".9"/>
+    <linearGradient id="SVGID_239_" x1="148.02" x2="148.02" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_239_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_240_" x1="171.335" x2="171.335" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_240_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 772.6 183 786" opacity=".9"/>
+    <linearGradient id="SVGID_241_" x1="148.02" x2="148.02" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_241_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 799.5 136.4 786" opacity=".3"/>
+    <linearGradient id="SVGID_242_" x1="217.965" x2="217.965" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_242_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 799.5 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_243_" x1="194.65" x2="194.65" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_243_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 826.4 183 812.9" opacity=".8"/>
+    <linearGradient id="SVGID_244_" x1="217.965" x2="217.965" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_244_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 772.6 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_245_" x1="194.65" x2="194.65" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_245_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 799.5 183 786" opacity=".8"/>
+    <linearGradient id="SVGID_246_" x1="264.595" x2="264.595" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_246_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 799.5 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_247_" x1="241.28" x2="241.28" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_247_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_248_" x1="264.595" x2="264.595" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_248_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 772.6 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_249_" x1="241.28" x2="241.28" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_249_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 799.5 229.6 786" opacity=".6"/>
+    <linearGradient id="SVGID_250_" x1="311.225" x2="311.225" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_250_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 799.5 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_251_" x1="287.91" x2="287.91" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_251_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_252_" x1="311.225" x2="311.225" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_252_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 772.6 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_253_" x1="287.91" x2="287.91" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_253_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 799.5 276.2 786" opacity=".4"/>
+    <linearGradient id="SVGID_254_" x1="357.855" x2="357.855" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_254_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 799.5 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_255_" x1="334.54" x2="334.54" y1="267.06" y2="253.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_255_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_256_" x1="357.855" x2="357.855" y1="307.44" y2="293.98" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_256_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 772.6 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_257_" x1="334.54" x2="334.54" y1="293.98" y2="280.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_257_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 799.5 322.9 786" opacity=".2"/>
+    <linearGradient id="SVGID_258_" x1="171.335" x2="171.335" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_258_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_259_" x1="171.335" x2="171.335" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_259_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 826.4 23.3 13.5" opacity=".9"/>
+    <linearGradient id="SVGID_260_" x1="148.02" x2="148.02" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_260_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 853.3-23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_261_" x1="217.965" x2="217.965" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_261_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 853.3 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_262_" x1="194.65" x2="194.65" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_262_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 880.2 183 866.8" opacity=".8"/>
+    <linearGradient id="SVGID_263_" x1="217.965" x2="217.965" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_263_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 826.4 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_264_" x1="194.65" x2="194.65" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_264_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 853.3 183 839.9" opacity=".8"/>
+    <linearGradient id="SVGID_265_" x1="264.595" x2="264.595" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_265_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_266_" x1="241.28" x2="241.28" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_266_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_267_" x1="264.595" x2="264.595" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_267_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 826.4 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_268_" x1="241.28" x2="241.28" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_268_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 853.3-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_269_" x1="311.225" x2="311.225" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_269_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_270_" x1="287.91" x2="287.91" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_270_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_271_" x1="311.225" x2="311.225" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_271_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 826.4 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_272_" x1="287.91" x2="287.91" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_272_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 853.3-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_273_" x1="357.855" x2="357.855" y1="226.67" y2="213.21" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_273_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_274_" x1="334.54" x2="334.54" y1="213.21" y2="199.75" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_274_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_275_" x1="357.855" x2="357.855" y1="253.59" y2="240.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_275_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 826.4 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_276_" x1="334.54" x2="334.54" y1="240.13" y2="226.67" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_276_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 853.3-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_277_" x1="217.965" x2="217.965" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_277_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m206.3 880.2 23.3 13.5" opacity=".7"/>
+    <linearGradient id="SVGID_278_" x1="264.595" x2="264.595" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_278_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_279_" x1="264.595" x2="264.595" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_279_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 880.2 23.3 13.5" opacity=".5"/>
+    <linearGradient id="SVGID_280_" x1="241.28" x2="241.28" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_280_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 907.2-23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_281_" x1="311.225" x2="311.225" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_281_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_282_" x1="287.91" x2="287.91" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_282_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_283_" x1="311.225" x2="311.225" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_283_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 880.2 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_284_" x1="287.91" x2="287.91" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_284_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 907.2-23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_285_" x1="357.855" x2="357.855" y1="172.83" y2="159.37" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_285_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_286_" x1="334.54" x2="334.54" y1="159.37" y2="145.91" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_286_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_287_" x1="357.855" x2="357.855" y1="199.75" y2="186.29" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_287_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 880.2 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_288_" x1="334.54" x2="334.54" y1="186.29" y2="172.83" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_288_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 907.2-23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_289_" x1="311.225" x2="311.225" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_289_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 934.1 23.3 13.5" opacity=".3"/>
+    <linearGradient id="SVGID_290_" x1="357.855" x2="357.855" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_290_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_291_" x1="357.855" x2="357.855" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_291_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 934.1 23.3 13.5" opacity=".1"/>
+    <linearGradient id="SVGID_292_" x1="334.54" x2="334.54" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".74" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_292_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 961-23.3-13.5" opacity=".2"/>
+    <g class="st291">
+      <linearGradient id="SVGID_293_" x1="-4.178" x2="20.438" y1="293.603" y2="307.817" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_293_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 786 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_294_" x1="81.058" x2="75.092" y1="257.332" y2="263.308" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_294_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_295_" x1="104.374" x2="98.406" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_295_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_296_" x1="34.444" x2="28.446" y1="257.324" y2="263.316" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_296_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_297_" x1="57.744" x2="51.776" y1="243.87" y2="249.85" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_297_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_298_" x1="34.446" x2="28.444" y1="284.253" y2="290.247" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_298_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 786-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_299_" x1="57.759" x2="51.761" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_299_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_300_" x1="11.13" x2="5.13" y1="243.862" y2="249.858" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_300_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 839.9 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_301_" x1="11.129" x2="5.131" y1="270.789" y2="276.781" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_301_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 813 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_302_" x1="81.058" x2="75.092" y1="230.412" y2="236.388" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_302_)" stroke-linecap="round" stroke-width="1.5" d="m89.7 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_303_" x1="34.444" x2="28.446" y1="203.484" y2="209.476" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_303_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_304_" x1="34.446" x2="28.444" y1="230.403" y2="236.397" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_304_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 839.9-23.3 13.5" opacity=".6"/>
+      <linearGradient id="SVGID_305_" x1="57.744" x2="51.776" y1="216.95" y2="222.93" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_305_)" stroke-linecap="round" stroke-width="1.5" d="m43.1 866.8 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_306_" x1="11.114" x2="5.146" y1="190.03" y2="196.01" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_306_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 893.7 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_307_" x1="11.13" x2="5.13" y1="216.942" y2="222.938" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".16" stop-color="#7d7d7d"/>
+        <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".66"/>
+        <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".38"/>
+        <stop offset=".59" stop-color="#7d7d7d" stop-opacity=".17"/>
+        <stop offset=".72" stop-color="#7d7d7d" stop-opacity=".04"/>
+        <stop offset=".82" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_307_)" stroke-linecap="round" stroke-width="1.5" d="m-3.5 866.8 23.3-13.5" opacity=".6"/>
+    </g>
+    <linearGradient id="SVGID_308_" x1="311.225" x2="311.225" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_308_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 5.3 299.6-8.2" opacity=".8"/>
+    <linearGradient id="SVGID_309_" x1="287.91" x2="287.91" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_309_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 18.8 276.2 5.3l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_310_" x1="264.595" x2="264.595" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_310_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_311_" x1="241.28" x2="241.28" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_311_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_312_" x1="217.965" x2="217.965" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_312_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_313_" x1="194.65" x2="194.65" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_313_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 72.6 183 59.1l23.3-13.5"/>
+    <linearGradient id="SVGID_314_" x1="171.335" x2="171.335" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_314_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 86.1-23.3-13.5L183 59.1"/>
+    <linearGradient id="SVGID_315_" x1="148.02" x2="148.02" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_315_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 99.5 136.4 86l23.3-13.5"/>
+    <linearGradient id="SVGID_316_" x1="357.855" x2="357.855" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_316_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 5.3 346.2-8.2" opacity=".6"/>
+    <linearGradient id="SVGID_317_" x1="334.54" x2="334.54" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_317_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 18.8 322.9 5.3l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_318_" x1="311.225" x2="311.225" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_318_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 32.2-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_319_" x1="287.91" x2="287.91" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_319_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 45.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_320_" x1="264.595" x2="264.595" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_320_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_321_" x1="241.28" x2="241.28" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_321_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_322_" x1="217.965" x2="217.965" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_322_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_323_" x1="194.65" x2="194.65" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_323_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 99.5 183 86.1l23.3-13.5"/>
+    <linearGradient id="SVGID_324_" x1="171.335" x2="171.335" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_324_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 113-23.3-13.5L183 86.1"/>
+    <linearGradient id="SVGID_325_" x1="148.02" x2="148.02" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_325_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 126.4 136.4 113l23.3-13.5"/>
+    <linearGradient id="SVGID_326_" x1="404.485" x2="404.485" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_326_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 5.3 392.8-8.2" opacity=".4"/>
+    <linearGradient id="SVGID_327_" x1="381.17" x2="381.17" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_327_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 18.8 369.5 5.3l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_328_" x1="357.855" x2="357.855" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_328_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 32.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_329_" x1="334.54" x2="334.54" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_329_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 45.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_330_" x1="311.225" x2="311.225" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_330_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 59.1-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_331_" x1="287.91" x2="287.91" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_331_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 72.6-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_332_" x1="264.595" x2="264.595" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_332_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 86-23.3-13.5L276.2 59"/>
+    <linearGradient id="SVGID_333_" x1="241.28" x2="241.28" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_333_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 99.5 229.6 86l23.3-13.5"/>
+    <linearGradient id="SVGID_334_" x1="217.965" x2="217.965" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_334_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 113-23.3-13.5L229.6 86"/>
+    <linearGradient id="SVGID_335_" x1="194.65" x2="194.65" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_335_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 126.4 183 113l23.3-13.5"/>
+    <linearGradient id="SVGID_336_" x1="171.335" x2="171.335" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_336_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 139.9-23.3-13.5L183 113"/>
+    <linearGradient id="SVGID_337_" x1="148.02" x2="148.02" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_337_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_338_" x1="451.115" x2="451.115" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_338_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 5.3 439.5-8.2" opacity=".2"/>
+    <linearGradient id="SVGID_339_" x1="427.8" x2="427.8" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_339_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 18.8 416.1 5.3l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_340_" x1="404.485" x2="404.485" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_340_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 32.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_341_" x1="381.17" x2="381.17" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_341_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 45.7-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_342_" x1="357.855" x2="357.855" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_342_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 59.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_343_" x1="334.54" x2="334.54" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_343_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 72.6-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_344_" x1="311.225" x2="311.225" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_344_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 86-23.3-13.5L322.9 59" opacity=".8"/>
+    <linearGradient id="SVGID_345_" x1="287.91" x2="287.91" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_345_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 99.5 276.3 86l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_346_" x1="264.595" x2="264.595" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_346_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 113-23.3-13.5L276.2 86"/>
+    <linearGradient id="SVGID_347_" x1="241.28" x2="241.28" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_347_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M252.9 126.4 229.6 113l23.3-13.5"/>
+    <linearGradient id="SVGID_348_" x1="217.965" x2="217.965" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_348_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_349_" x1="194.65" x2="194.65" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_349_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 153.4 183 139.9l23.3-13.5"/>
+    <linearGradient id="SVGID_350_" x1="171.335" x2="171.335" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_350_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_351_" x1="148.02" x2="148.02" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_351_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_352_" x1="451.115" x2="451.115" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_352_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 32.2-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_353_" x1="427.8" x2="427.8" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_353_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 45.7-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_354_" x1="404.485" x2="404.485" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_354_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 59.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_355_" x1="381.17" x2="381.17" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_355_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 72.6-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_356_" x1="357.855" x2="357.855" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_356_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 86-23.3-13.5L369.5 59" opacity=".6"/>
+    <linearGradient id="SVGID_357_" x1="334.54" x2="334.54" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_357_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 99.5 322.9 86l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_358_" x1="311.225" x2="311.225" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_358_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 113-23.3-13.5L322.9 86" opacity=".8"/>
+    <linearGradient id="SVGID_359_" x1="287.91" x2="287.91" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_359_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M299.6 126.4 276.2 113l23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_360_" x1="264.595" x2="264.595" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_360_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_361_" x1="241.28" x2="241.28" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_361_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_362_" x1="217.965" x2="217.965" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_362_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_363_" x1="194.65" x2="194.65" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_363_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 180.3 183 166.8l23.3-13.5"/>
+    <linearGradient id="SVGID_364_" x1="171.335" x2="171.335" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_364_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_365_" x1="148.02" x2="148.02" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_365_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_366_" x1="451.115" x2="451.115" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_366_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 59.1-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_367_" x1="427.8" x2="427.8" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_367_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 72.6-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_368_" x1="404.485" x2="404.485" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_368_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 86-23.3-13.5L416.1 59" opacity=".4"/>
+    <linearGradient id="SVGID_369_" x1="381.17" x2="381.17" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_369_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 99.5 369.5 86l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_370_" x1="357.855" x2="357.855" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_370_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 113-23.3-13.5L369.5 86" opacity=".6"/>
+    <linearGradient id="SVGID_371_" x1="334.54" x2="334.54" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_371_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M346.2 126.4 322.9 113l23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_372_" x1="311.225" x2="311.225" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_372_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 139.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_373_" x1="287.91" x2="287.91" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_373_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 153.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_374_" x1="264.595" x2="264.595" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_374_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_375_" x1="241.28" x2="241.28" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_375_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_376_" x1="217.965" x2="217.965" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_376_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_377_" x1="194.65" x2="194.65" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_377_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 207.2 183 193.7l23.3-13.5"/>
+    <linearGradient id="SVGID_378_" x1="171.335" x2="171.335" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_378_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_379_" x1="148.02" x2="148.02" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_379_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_380_" x1="451.115" x2="451.115" y1="1020.87" y2="993.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_380_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 86-23.3-13.5L462.8 59" opacity=".2"/>
+    <linearGradient id="SVGID_381_" x1="427.8" x2="427.8" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_381_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 99.5 416.2 86l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_382_" x1="404.485" x2="404.485" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_382_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 113-23.3-13.5L416.1 86" opacity=".4"/>
+    <linearGradient id="SVGID_383_" x1="381.17" x2="381.17" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_383_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M392.8 126.4 369.5 113l23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_384_" x1="357.855" x2="357.855" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_384_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 139.9-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_385_" x1="334.54" x2="334.54" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_385_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 153.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_386_" x1="311.225" x2="311.225" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_386_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 166.8-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_387_" x1="287.91" x2="287.91" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_387_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 180.3-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_388_" x1="264.595" x2="264.595" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_388_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_389_" x1="241.28" x2="241.28" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_389_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_390_" x1="217.965" x2="217.965" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_390_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_391_" x1="194.65" x2="194.65" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_391_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 234.1 183 220.7l23.3-13.5"/>
+    <linearGradient id="SVGID_392_" x1="171.335" x2="171.335" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_392_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_393_" x1="148.02" x2="148.02" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_393_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_394_" x1="451.115" x2="451.115" y1="993.95" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_394_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 113-23.3-13.5L462.8 86" opacity=".2"/>
+    <linearGradient id="SVGID_395_" x1="427.8" x2="427.8" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_395_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M439.5 126.4 416.1 113l23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_396_" x1="404.485" x2="404.485" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_396_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 139.9-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_397_" x1="381.17" x2="381.17" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_397_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 153.4-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_398_" x1="357.855" x2="357.855" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_398_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 166.8-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_399_" x1="334.54" x2="334.54" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_399_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 180.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_400_" x1="311.225" x2="311.225" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_400_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 193.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_401_" x1="287.91" x2="287.91" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_401_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 207.2-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_402_" x1="264.595" x2="264.595" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_402_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_403_" x1="241.28" x2="241.28" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_403_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_404_" x1="217.965" x2="217.965" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_404_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_405_" x1="194.65" x2="194.65" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_405_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 261 183 247.6l23.3-13.5"/>
+    <linearGradient id="SVGID_406_" x1="171.335" x2="171.335" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_406_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 274.5 159.7 261l23.3-13.5"/>
+    <linearGradient id="SVGID_407_" x1="148.02" x2="148.02" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_407_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 288-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_408_" x1="451.115" x2="451.115" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_408_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 139.9-23.3-13.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_409_" x1="427.8" x2="427.8" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_409_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 153.4-23.3-13.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_410_" x1="404.485" x2="404.485" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_410_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 166.8-23.3-13.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_411_" x1="381.17" x2="381.17" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_411_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 180.3-23.3-13.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_412_" x1="357.855" x2="357.855" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_412_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 193.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_413_" x1="334.54" x2="334.54" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_413_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 207.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_414_" x1="311.225" x2="311.225" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_414_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 220.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_415_" x1="287.91" x2="287.91" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_415_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 234.1-23.3-13.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_416_" x1="264.595" x2="264.595" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_416_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_417_" x1="241.28" x2="241.28" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_417_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_418_" x1="217.965" x2="217.965" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_418_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 274.5 206.3 261l23.3-13.5"/>
+    <linearGradient id="SVGID_419_" x1="194.65" x2="194.65" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_419_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 288 183 274.5l23.3-13.5"/>
+    <linearGradient id="SVGID_420_" x1="171.335" x2="171.335" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_420_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M183 301.4 159.7 288l23.3-13.5"/>
+    <linearGradient id="SVGID_421_" x1="148.02" x2="148.02" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".448" stop-color="#7d7d7d"/>
+      <stop offset=".557" stop-color="#7d7d7d"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_421_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 314.9-23.3-13.5 23.3-13.5"/>
+    <g opacity=".9">
+      <linearGradient id="SVGID_422_" x1="451.115" x2="451.115" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_422_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 166.8-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_423_" x1="427.8" x2="427.8" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_423_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 180.3-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_424_" x1="404.485" x2="404.485" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_424_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 193.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_425_" x1="381.17" x2="381.17" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_425_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 207.2-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_426_" x1="357.855" x2="357.855" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_426_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 220.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_427_" x1="334.54" x2="334.54" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_427_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 234.1-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_428_" x1="311.225" x2="311.225" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_428_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 247.6-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_429_" x1="287.91" x2="287.91" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_429_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 261-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_430_" x1="264.595" x2="264.595" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_430_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 274.5 252.9 261l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_431_" x1="241.28" x2="241.28" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_431_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_432_" x1="217.965" x2="217.965" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_432_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M229.6 301.4 206.3 288l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_433_" x1="194.65" x2="194.65" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_433_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 314.9 183 301.4l23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_434_" x1="171.335" x2="171.335" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_434_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 328.4-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_435_" x1="148.02" x2="148.02" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_435_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+    </g>
+    <g opacity=".8">
+      <linearGradient id="SVGID_436_" x1="451.115" x2="451.115" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_436_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 193.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_437_" x1="427.8" x2="427.8" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_437_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 207.2-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_438_" x1="404.485" x2="404.485" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_438_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 220.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_439_" x1="381.17" x2="381.17" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_439_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 234.1-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_440_" x1="357.855" x2="357.855" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_440_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 247.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_441_" x1="334.54" x2="334.54" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_441_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 261-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_442_" x1="311.225" x2="311.225" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_442_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 274.5 299.6 261l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_443_" x1="287.91" x2="287.91" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_443_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 288-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_444_" x1="264.595" x2="264.595" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_444_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M276.2 301.4 252.9 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_445_" x1="241.28" x2="241.28" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_445_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 314.9-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_446_" x1="217.965" x2="217.965" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_446_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_447_" x1="194.65" x2="194.65" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_447_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 341.8 183 328.4l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_448_" x1="171.335" x2="171.335" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_448_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_449_" x1="148.02" x2="148.02" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_449_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 368.7-23.3-13.5 23.3-13.5" opacity=".8"/>
+    </g>
+    <g opacity=".7">
+      <linearGradient id="SVGID_450_" x1="451.115" x2="451.115" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_450_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 220.7-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_451_" x1="427.8" x2="427.8" y1="872.8" y2="845.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_451_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 234.1-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_452_" x1="404.485" x2="404.485" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_452_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 247.6-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_453_" x1="381.17" x2="381.17" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_453_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 261-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_454_" x1="357.855" x2="357.855" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_454_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 274.5 346.2 261l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_455_" x1="334.54" x2="334.54" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_455_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 288-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_456_" x1="311.225" x2="311.225" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_456_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M322.9 301.4 299.6 288l23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_457_" x1="287.91" x2="287.91" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_457_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 314.9-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_458_" x1="264.595" x2="264.595" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_458_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 328.4-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_459_" x1="241.28" x2="241.28" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_459_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_460_" x1="217.965" x2="217.965" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_460_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 355.3-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_461_" x1="194.65" x2="194.65" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_461_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 368.7 183 355.3l23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_462_" x1="171.335" x2="171.335" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_462_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 382.2-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_463_" x1="148.02" x2="148.02" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_463_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 395.7-23.3-13.5 23.3-13.5" opacity=".7"/>
+    </g>
+    <g class="st291">
+      <linearGradient id="SVGID_464_" x1="451.115" x2="451.115" y1="859.34" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_464_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m462.8 247.6-23.3-13.5 23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_465_" x1="427.8" x2="427.8" y1="845.88" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_465_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 261-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_466_" x1="404.485" x2="404.485" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_466_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 274.5 392.8 261l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_467_" x1="381.17" x2="381.17" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_467_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 288-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_468_" x1="357.855" x2="357.855" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_468_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M369.5 301.4 346.2 288l23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_469_" x1="334.54" x2="334.54" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_469_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 314.9-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_470_" x1="311.225" x2="311.225" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_470_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 328.4-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_471_" x1="287.91" x2="287.91" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_471_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 341.8-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_472_" x1="264.595" x2="264.595" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_472_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 355.3-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_473_" x1="241.28" x2="241.28" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_473_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 368.7-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_474_" x1="217.965" x2="217.965" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_474_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 382.2-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_475_" x1="171.335" x2="171.335" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_475_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 409.1-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_476_" x1="148.02" x2="148.02" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_476_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m159.7 422.6-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_477_" x1="194.65" x2="194.65" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_477_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 395.7 183 382.2l23.3-13.5" opacity=".6"/>
+    </g>
+    <g opacity=".4">
+      <linearGradient id="SVGID_478_" x1="451.115" x2="451.115" y1="832.41" y2="805.49" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_478_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M462.8 274.5 439.5 261l23.3-13.5" opacity=".2"/>
+      <linearGradient id="SVGID_479_" x1="427.8" x2="427.8" y1="818.95" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_479_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 288-23.3-13.5 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_480_" x1="404.485" x2="404.485" y1="805.49" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_480_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M416.1 301.4 392.8 288l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_481_" x1="381.17" x2="381.17" y1="792.03" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_481_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 314.9-23.3-13.5 23.3-13.5" opacity=".5"/>
+      <linearGradient id="SVGID_482_" x1="357.855" x2="357.855" y1="778.57" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_482_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 328.4-23.3-13.5 23.3-13.5" opacity=".6"/>
+      <linearGradient id="SVGID_483_" x1="334.54" x2="334.54" y1="765.11" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_483_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m346.2 341.8-23.3-13.5 23.3-13.5" opacity=".7"/>
+      <linearGradient id="SVGID_484_" x1="311.225" x2="311.225" y1="751.65" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_484_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m322.9 355.3-23.3-13.5 23.3-13.5" opacity=".8"/>
+      <linearGradient id="SVGID_485_" x1="287.91" x2="287.91" y1="738.19" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_485_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m299.6 368.7-23.3-13.5 23.3-13.5" opacity=".9"/>
+      <linearGradient id="SVGID_486_" x1="171.335" x2="171.335" y1="670.88" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_486_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m183 436-23.3-13.5L183 409" opacity=".4"/>
+      <linearGradient id="SVGID_487_" x1="148.02" x2="148.02" y1="657.42" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_487_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M159.7 449.5 136.4 436l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_488_" x1="194.65" x2="194.65" y1="684.34" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_488_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="M206.3 422.6 183 409.1l23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_489_" x1="217.965" x2="217.965" y1="697.81" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_489_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m229.6 409.1-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_490_" x1="241.28" x2="241.28" y1="711.27" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_490_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m252.9 395.7-23.3-13.5 23.3-13.5" opacity=".4"/>
+      <linearGradient id="SVGID_491_" x1="264.595" x2="264.595" y1="724.73" y2="697.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset=".125" stop-color="#7d7d7d" stop-opacity="0"/>
+        <stop offset=".448" stop-color="#7d7d7d"/>
+        <stop offset=".557" stop-color="#7d7d7d"/>
+        <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".056"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_491_)" stroke-linecap="round" stroke-linejoin="round" stroke-miterlimit="10" stroke-width="1.5" d="m276.2 382.2-23.3-13.5 23.3-13.5" opacity=".4"/>
+    </g>
+    <g opacity=".3">
+      <linearGradient id="SVGID_492_" x1="-2882.929" x2="-2998.679" y1="-9839.971" y2="-10187.071" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_492_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m392.8 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_493_" x1="-2749.297" x2="-2864.998" y1="-9502.538" y2="-9849.738" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_493_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1055.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_494_" x1="-2728.156" x2="-2843.956" y1="-9511.58" y2="-9858.681" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_494_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1068.7 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_495_" x1="-2619.398" x2="-2735.197" y1="-9158.664" y2="-9505.765" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_495_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m439.5 1041.8 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_496_" x1="-3013.48" x2="-3129.19" y1="-10181.445" y2="-10528.646" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_496_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m369.5 1082.2 23.3-13.5" opacity=".3"/>
+      <linearGradient id="SVGID_497_" x1="-2858.016" x2="-2973.717" y1="-9855.709" y2="-10202.909" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+        <stop offset="0" stop-color="#7d7d7d"/>
+        <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+      </linearGradient>
+      <path fill="none" stroke="url(#SVGID_497_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m416.1 1082.2 23.3-13.5" opacity=".3"/>
+    </g>
+    <linearGradient id="SVGID_498_" x1="-15.93" x2="440.21" y1="111.755" y2="111.755" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".2" stop-color="#7d7d7d"/>
+      <stop offset=".57" stop-color="#7d7d7d" stop-opacity=".54"/>
+      <stop offset=".82" stop-color="#7d7d7d" stop-opacity=".2"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_498_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m-15.2 927.4 151.5-87.5M-11.6 952.2l171.2-98.9zM183 866.8-11.6 979.1zm23.3 13.4-218.2 126zm23.3 13.5L-15.2 1035zm23.3 13.5L-15.2 1062zm23.3 13.4-291.4 168.3zm23.4 13.5L26.1 1092zm23.3 13.5-258.2 149zm23.3 13.4L113 1095.6zm23.3 13.5-209.8 121.1zm23.3 13.4-186.5 107.7zm23.3 13.5-163.2 94.2zm23.4 13.5-139.9 80.8z"/>
+    <linearGradient id="SVGID_499_" x1="-4.28" x2="277" y1="851.54" y2="851.54" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".11" stop-color="#7d7d7d" stop-opacity=".06"/>
+      <stop offset=".28" stop-color="#7d7d7d" stop-opacity=".23"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".71" stop-color="#7d7d7d" stop-opacity=".88"/>
+      <stop offset=".78" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_499_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M136.4 86.1-3.5 5.3m279.7 0L256.6-6.1zM209.9-6.1l43 24.8zm-46.6 0 66.3 38.3zm-46.6 0 89.6 51.7zM70-6.1l113 65.2zm-46.6 0 136.3 78.7zM-3.5 32.2 136.4 113zm139.9 107.7L-3.5 59.1zm0 26.9L-3.5 86.1zm0 26.9L-3.5 113zm0 27L-3.5 139.9zm0 26.9L-3.5 166.8zm0 26.9L-3.5 193.7zm0 26.9L-3.5 220.7zm0 27L-3.5 247.6zm0 26.9L-3.5 274.5zm0 26.9L-3.5 301.4zm0 26.9L-3.5 328.4zm0 26.9L-3.5 355.3zM-3.5 382.2 136.4 463z"/>
+    <linearGradient id="SVGID_500_" x1="450.465" x2="719.877" y1="1054.898" y2="899.342" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".6"/>
+      <stop offset=".29" stop-color="#7d7d7d" stop-opacity=".47"/>
+      <stop offset=".69" stop-color="#7d7d7d" stop-opacity=".34"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity=".3"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_500_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M789.2 59.1 462.8 247.6M482.5-6.1 462.8 5.3zm-19.7 38.3 66.3-38.3zM575.7-6.1l-113 65.2zm-113 92.2L622.4-6.1zm.1 26.9L669-6.1zM715.6-6.1l-252.9 146zm46.7 0L462.8 166.8zm26.9 11.4L462.8 193.7zM462.8 220.7 789.2 32.2z" opacity=".3"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m136.4 812.9-23.3 13.5M19.8 395.7l-23.3 13.5zm23.3 13.4L-3.5 436zm23.4 13.4-70 40.5zM89.7 436l-93.3 53.9zm23.4 13.5L-3.5 516.8zm23.3 13.5L-3.5 543.7zm0 26.9L-3.5 570.7zM-3.5 597.6l139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 26.9 139.9-80.8zm0 27 139.9-80.8zm0 26.9 139.9-80.8zm139.9-53.9L-3.5 759.1zm0 27L19.8 772.6zm0 26.9L43.1 786zm0 26.9-69.9 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+    <linearGradient id="SVGID_501_" x1="1710.53" x2="1710.53" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_501_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 314.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_502_" x1="1733.845" x2="1733.845" y1="792.03" y2="778.57" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_502_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 301.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_503_" x1="1757.16" x2="1757.16" y1="778.57" y2="765.11" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_503_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 314.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_504_" x1="1757.16" x2="1757.16" y1="805.49" y2="792.03" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_504_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 288 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_505_" x1="1617.27" x2="1617.27" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_505_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 368.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_506_" x1="1640.585" x2="1640.585" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_506_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 355.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_507_" x1="1663.9" x2="1663.9" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_507_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_508_" x1="1663.9" x2="1663.9" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_508_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_509_" x1="1687.215" x2="1687.215" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_509_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 355.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_510_" x1="1710.53" x2="1710.53" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_510_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 368.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_511_" x1="1687.215" x2="1687.215" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_511_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 328.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_512_" x1="1710.53" x2="1710.53" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_512_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 341.8 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_513_" x1="1733.845" x2="1733.845" y1="738.19" y2="724.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_513_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 355.3 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_514_" x1="1757.16" x2="1757.16" y1="724.73" y2="711.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_514_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 368.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_515_" x1="1733.845" x2="1733.845" y1="765.11" y2="751.65" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_515_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 328.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_516_" x1="1757.16" x2="1757.16" y1="751.65" y2="738.19" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_516_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 341.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_517_" x1="1547.325" x2="1547.325" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_517_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 409.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_518_" x1="1570.64" x2="1570.64" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_518_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 422.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_519_" x1="1570.64" x2="1570.64" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_519_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 395.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_520_" x1="1593.955" x2="1593.955" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_520_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 409.1 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_521_" x1="1617.27" x2="1617.27" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_521_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 422.6 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_522_" x1="1593.955" x2="1593.955" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_522_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 382.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_523_" x1="1617.27" x2="1617.27" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_523_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 395.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_524_" x1="1640.585" x2="1640.585" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_524_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 409.1 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_525_" x1="1663.9" x2="1663.9" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_525_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_526_" x1="1640.585" x2="1640.585" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_526_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 382.2 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_527_" x1="1663.9" x2="1663.9" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_527_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_528_" x1="1687.215" x2="1687.215" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_528_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 409.1 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_529_" x1="1710.53" x2="1710.53" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_529_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 422.6 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_530_" x1="1687.215" x2="1687.215" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_530_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 382.2 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_531_" x1="1710.53" x2="1710.53" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_531_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 395.7 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_532_" x1="1733.845" x2="1733.845" y1="684.34" y2="670.88" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_532_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 409.1 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_533_" x1="1757.16" x2="1757.16" y1="670.88" y2="657.42" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_533_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 422.6 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_534_" x1="1733.845" x2="1733.845" y1="711.27" y2="697.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_534_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 382.2 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_535_" x1="1757.16" x2="1757.16" y1="697.8" y2="684.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_535_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 395.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_536_" x1="1547.325" x2="1547.325" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_536_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 463 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_537_" x1="1570.64" x2="1570.64" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_537_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 476.4 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_538_" x1="1547.325" x2="1547.325" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_538_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 436 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_539_" x1="1570.64" x2="1570.64" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_539_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 449.5 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_540_" x1="1593.955" x2="1593.955" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_540_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 463 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_541_" x1="1617.27" x2="1617.27" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_541_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 476.4 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_542_" x1="1593.955" x2="1593.955" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_542_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 436 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_543_" x1="1617.27" x2="1617.27" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_543_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 449.5 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_544_" x1="1640.585" x2="1640.585" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_544_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 463 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_545_" x1="1663.9" x2="1663.9" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_545_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_546_" x1="1640.585" x2="1640.585" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_546_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 436 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_547_" x1="1663.9" x2="1663.9" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_547_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_548_" x1="1687.215" x2="1687.215" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_548_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 463 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_549_" x1="1710.53" x2="1710.53" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_549_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 476.4 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_550_" x1="1687.215" x2="1687.215" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_550_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 436 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_551_" x1="1710.53" x2="1710.53" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_551_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 449.5 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_552_" x1="1733.845" x2="1733.845" y1="630.5" y2="617.04" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_552_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 463 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_553_" x1="1757.16" x2="1757.16" y1="617.04" y2="603.58" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_553_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 476.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_554_" x1="1733.845" x2="1733.845" y1="657.42" y2="643.96" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_554_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 436 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_555_" x1="1757.16" x2="1757.16" y1="643.96" y2="630.5" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_555_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 449.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_556_" x1="1547.325" x2="1547.325" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_556_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 516.8 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_557_" x1="1570.64" x2="1570.64" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_557_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 530.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_558_" x1="1547.325" x2="1547.325" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_558_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 489.9 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_559_" x1="1570.64" x2="1570.64" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_559_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 503.3 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_560_" x1="1593.955" x2="1593.955" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_560_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 516.8 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_561_" x1="1617.27" x2="1617.27" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_561_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 530.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_562_" x1="1593.955" x2="1593.955" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_562_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 489.9 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_563_" x1="1617.27" x2="1617.27" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_563_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 503.3 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_564_" x1="1640.585" x2="1640.585" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_564_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 516.8 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_565_" x1="1663.9" x2="1663.9" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_565_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_566_" x1="1640.585" x2="1640.585" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_566_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 489.9 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_567_" x1="1663.9" x2="1663.9" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_567_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_568_" x1="1687.215" x2="1687.215" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_568_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 516.8 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_569_" x1="1710.53" x2="1710.53" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_569_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 530.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_570_" x1="1687.215" x2="1687.215" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_570_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 489.9 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_571_" x1="1710.53" x2="1710.53" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_571_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 503.3 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_572_" x1="1733.845" x2="1733.845" y1="576.66" y2="563.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_572_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 516.8 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_573_" x1="1757.16" x2="1757.16" y1="563.2" y2="549.73" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_573_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 530.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_574_" x1="1733.845" x2="1733.845" y1="603.58" y2="590.12" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_574_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 489.9 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_575_" x1="1757.16" x2="1757.16" y1="590.12" y2="576.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_575_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 503.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_576_" x1="1547.325" x2="1547.325" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_576_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 570.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_577_" x1="1570.64" x2="1570.64" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_577_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 584.1 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_578_" x1="1547.325" x2="1547.325" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_578_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 543.7 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_579_" x1="1570.64" x2="1570.64" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_579_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 557.2 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_580_" x1="1593.955" x2="1593.955" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_580_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 570.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_581_" x1="1617.27" x2="1617.27" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_581_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 584.1 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_582_" x1="1593.955" x2="1593.955" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_582_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 543.7 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_583_" x1="1617.27" x2="1617.27" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_583_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 557.2 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_584_" x1="1640.585" x2="1640.585" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_584_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 570.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_585_" x1="1663.9" x2="1663.9" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_585_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_586_" x1="1640.585" x2="1640.585" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_586_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 543.7 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_587_" x1="1663.9" x2="1663.9" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_587_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_588_" x1="1687.215" x2="1687.215" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_588_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 570.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_589_" x1="1710.53" x2="1710.53" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_589_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 584.1 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_590_" x1="1687.215" x2="1687.215" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_590_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 543.7 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_591_" x1="1710.53" x2="1710.53" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_591_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 557.2 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_592_" x1="1733.845" x2="1733.845" y1="522.81" y2="509.35" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_592_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 570.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_593_" x1="1757.16" x2="1757.16" y1="509.35" y2="495.89" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_593_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 584.1 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_594_" x1="1733.845" x2="1733.845" y1="549.73" y2="536.27" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_594_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 543.7 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_595_" x1="1757.16" x2="1757.16" y1="536.27" y2="522.81" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_595_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 557.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_596_" x1="1547.325" x2="1547.325" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_596_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 624.5 1559 611" opacity=".1"/>
+    <linearGradient id="SVGID_597_" x1="1570.64" x2="1570.64" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_597_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 638 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_598_" x1="1547.325" x2="1547.325" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_598_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 597.6 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_599_" x1="1570.64" x2="1570.64" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_599_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 611 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_600_" x1="1593.955" x2="1593.955" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_600_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 624.5 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_601_" x1="1617.27" x2="1617.27" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_601_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 638 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_602_" x1="1593.955" x2="1593.955" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_602_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 597.6 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_603_" x1="1617.27" x2="1617.27" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_603_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 611 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_604_" x1="1640.585" x2="1640.585" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_604_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 624.5 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_605_" x1="1663.9" x2="1663.9" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_605_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_606_" x1="1640.585" x2="1640.585" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_606_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 597.6 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_607_" x1="1663.9" x2="1663.9" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_607_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_608_" x1="1687.215" x2="1687.215" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_608_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 624.5 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_609_" x1="1710.53" x2="1710.53" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_609_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 638 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_610_" x1="1687.215" x2="1687.215" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_610_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 597.6 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_611_" x1="1710.53" x2="1710.53" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_611_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 611 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_612_" x1="1733.845" x2="1733.845" y1="468.97" y2="455.51" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_612_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 624.5 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_613_" x1="1757.16" x2="1757.16" y1="455.51" y2="442.05" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_613_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 638 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_614_" x1="1733.845" x2="1733.845" y1="495.89" y2="482.43" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_614_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 597.6 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_615_" x1="1757.16" x2="1757.16" y1="482.43" y2="468.97" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_615_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1745.5 611 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_616_" x1="1547.325" x2="1547.325" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_616_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 678.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_617_" x1="1570.64" x2="1570.64" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_617_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 691.8 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_618_" x1="1547.325" x2="1547.325" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_618_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1535.7 651.4 1559 638" opacity=".1"/>
+    <linearGradient id="SVGID_619_" x1="1570.64" x2="1570.64" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_619_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 664.9 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_620_" x1="1593.955" x2="1593.955" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_620_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 678.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_621_" x1="1617.27" x2="1617.27" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_621_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 691.8 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_622_" x1="1593.955" x2="1593.955" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_622_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 651.4 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_623_" x1="1617.27" x2="1617.27" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_623_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 664.9 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_624_" x1="1640.585" x2="1640.585" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_624_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 678.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_625_" x1="1663.9" x2="1663.9" y1="401.66" y2="388.2" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_625_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 691.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_626_" x1="1640.585" x2="1640.585" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_626_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 651.4 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_627_" x1="1663.9" x2="1663.9" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_627_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1652.2 664.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_628_" x1="1687.215" x2="1687.215" y1="415.13" y2="401.66" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_628_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 678.3 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_629_" x1="1687.215" x2="1687.215" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_629_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1675.6 651.4 23.3-13.5" opacity=".7"/>
+    <linearGradient id="SVGID_630_" x1="1710.53" x2="1710.53" y1="428.59" y2="415.13" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_630_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1698.9 664.9 23.3-13.5" opacity=".8"/>
+    <linearGradient id="SVGID_631_" x1="1733.845" x2="1733.845" y1="442.05" y2="428.59" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_631_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1722.2 651.4 23.3-13.5" opacity=".9"/>
+    <linearGradient id="SVGID_632_" x1="1547.325" x2="1547.325" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_632_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 732.2 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_633_" x1="1570.64" x2="1570.64" y1="347.82" y2="334.36" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_633_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 745.6 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_634_" x1="1547.325" x2="1547.325" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_634_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 705.3 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_635_" x1="1570.64" x2="1570.64" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_635_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1559 718.7 23.3-13.5" opacity=".2"/>
+    <linearGradient id="SVGID_636_" x1="1593.955" x2="1593.955" y1="361.28" y2="347.82" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_636_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 732.2 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_637_" x1="1593.955" x2="1593.955" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_637_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1582.3 705.3 23.3-13.5" opacity=".3"/>
+    <linearGradient id="SVGID_638_" x1="1617.27" x2="1617.27" y1="374.74" y2="361.28" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_638_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1605.6 718.7 23.3-13.5" opacity=".4"/>
+    <linearGradient id="SVGID_639_" x1="1640.585" x2="1640.585" y1="388.2" y2="374.74" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_639_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1628.9 705.3 23.3-13.5" opacity=".5"/>
+    <linearGradient id="SVGID_640_" x1="1547.325" x2="1547.325" y1="334.36" y2="320.9" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_640_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1535.7 759.1 23.3-13.5" opacity=".1"/>
+    <linearGradient id="SVGID_641_" x1="1454.065" x2="1454.065" y1="280.52" y2="267.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_641_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9 23.3-13.5" opacity=".07"/>
+    <path fill="none" stroke="#7d7d7d" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1792.1 288 2002 166.8m-186.6 134.6L2002 193.7m-163.2 121.2 163.2-94.2m-139.9 107.7 139.9-80.8m-116.6 94.2 116.6-67.3m-93.3 80.8 93.3-53.8m-233.2-27L2002 139.9"/>
+    <linearGradient id="SVGID_642_" x1="1919.99" x2="1919.99" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_642_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 18.8-23.3-13.5L1932-8.2"/>
+    <linearGradient id="SVGID_643_" x1="1919.99" x2="1919.99" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_643_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_644_" x1="1919.99" x2="1919.99" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_644_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_645_" x1="1919.99" x2="1919.99" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_645_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1932 99.5 1908.7 86l23.3-13.5"/>
+    <linearGradient id="SVGID_646_" x1="1919.99" x2="1919.99" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_646_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_647_" x1="1919.99" x2="1919.99" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_647_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_648_" x1="1919.99" x2="1919.99" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_648_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1932 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_649_" x1="1897.05" x2="1897.05" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_649_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_650_" x1="1896.675" x2="1896.675" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_650_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_651_" x1="1896.675" x2="1896.675" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_651_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_652_" x1="1896.675" x2="1896.675" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_652_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_653_" x1="1896.675" x2="1896.675" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_653_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_654_" x1="1896.675" x2="1896.675" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_654_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_655_" x1="1896.675" x2="1896.675" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_655_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_656_" x1="1873.36" x2="1873.36" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_656_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_657_" x1="1873.36" x2="1873.36" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_657_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_658_" x1="1873.36" x2="1873.36" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_658_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_659_" x1="1873.36" x2="1873.36" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_659_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1885.4 99.5 1862.1 86l23.3-13.5"/>
+    <linearGradient id="SVGID_660_" x1="1873.36" x2="1873.36" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_660_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_661_" x1="1873.36" x2="1873.36" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_661_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_662_" x1="1873.36" x2="1873.36" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_662_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_663_" x1="1850.42" x2="1850.42" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_663_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_664_" x1="1850.045" x2="1850.045" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_664_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_665_" x1="1850.045" x2="1850.045" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_665_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_666_" x1="1850.045" x2="1850.045" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_666_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_667_" x1="1850.045" x2="1850.045" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_667_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_668_" x1="1850.045" x2="1850.045" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_668_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_669_" x1="1850.045" x2="1850.045" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_669_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_670_" x1="1826.73" x2="1826.73" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_670_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_671_" x1="1826.73" x2="1826.73" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_671_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_672_" x1="1826.73" x2="1826.73" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_672_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_673_" x1="1826.73" x2="1826.73" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_673_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1838.8 99.5 1815.5 86l23.3-13.5"/>
+    <linearGradient id="SVGID_674_" x1="1826.73" x2="1826.73" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_674_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_675_" x1="1826.73" x2="1826.73" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_675_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_676_" x1="1826.73" x2="1826.73" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_676_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_677_" x1="1803.79" x2="1803.79" y1="1088.17" y2="1074.71" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_677_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 5.3-23.3-13.5"/>
+    <linearGradient id="SVGID_678_" x1="1803.415" x2="1803.415" y1="1074.71" y2="1047.79" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_678_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 32.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_679_" x1="1803.415" x2="1803.415" y1="1047.79" y2="1020.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_679_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 59.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_680_" x1="1803.415" x2="1803.415" y1="1020.87" y2="993.94" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_680_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 86.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_681_" x1="1803.415" x2="1803.415" y1="993.94" y2="967.02" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_681_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 113-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_682_" x1="1803.415" x2="1803.415" y1="967.02" y2="940.1" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_682_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 139.9-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_683_" x1="1803.415" x2="1803.415" y1="940.1" y2="913.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_683_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 166.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_684_" x1="1780.1" x2="1780.1" y1="1088.17" y2="1061.25" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_684_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 18.8-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_685_" x1="1780.1" x2="1780.1" y1="1061.25" y2="1034.33" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_685_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 45.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_686_" x1="1780.1" x2="1780.1" y1="1034.33" y2="1007.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_686_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 72.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_687_" x1="1780.1" x2="1780.1" y1="1007.41" y2="980.48" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_687_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="M1792.1 99.5 1768.8 86l23.3-13.5"/>
+    <linearGradient id="SVGID_688_" x1="1780.1" x2="1780.1" y1="980.48" y2="953.56" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_688_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 126.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_689_" x1="1780.1" x2="1780.1" y1="953.56" y2="926.64" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_689_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 153.4-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_690_" x1="1780.1" x2="1780.1" y1="926.64" y2="899.72" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_690_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 180.3-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_691_" x1="1803.415" x2="1803.415" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_691_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_692_" x1="1780.1" x2="1780.1" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_692_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_693_" x1="1850.045" x2="1850.045" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_693_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_694_" x1="1803.415" x2="1803.415" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_694_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_695_" x1="1780.1" x2="1780.1" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_695_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_696_" x1="1826.73" x2="1826.73" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_696_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_697_" x1="1803.415" x2="1803.415" y1="859.33" y2="832.41" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_697_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1815.4 247.6-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_698_" x1="1780.1" x2="1780.1" y1="845.87" y2="818.95" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_698_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1792.1 261-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_699_" x1="1826.73" x2="1826.73" y1="872.8" y2="845.87" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_699_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1838.8 234.1-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_700_" x1="1850.045" x2="1850.045" y1="886.26" y2="859.34" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_700_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1862.1 220.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_701_" x1="1873.36" x2="1873.36" y1="899.72" y2="872.8" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_701_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1885.4 207.2-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_702_" x1="1896.675" x2="1896.675" y1="913.18" y2="886.26" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".344" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".677" stop-color="#7d7d7d" stop-opacity=".056"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_702_)" stroke-linecap="round" stroke-miterlimit="10" stroke-width="1.5" d="m1908.7 193.7-23.3-13.5 23.3-13.5"/>
+    <linearGradient id="SVGID_703_" x1="1381.56" x2="1769.57" y1="1052.175" y2="1052.175" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".14" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".49" stop-color="#7d7d7d" stop-opacity=".36"/>
+      <stop offset=".89" stop-color="#7d7d7d" stop-opacity=".8"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_703_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1382.3 50.3 386.5 224.2m0-269.2-386.5-224.2zm0 26.9-386.5-224.1zm0 26.9L1382.3-165zm0 27-386.5-224.2zm0 26.9-386.5-224.2zm0 26.9L1382.3-84.3zm0 26.9L1382.3-57.3zm0 26.9L1382.3-30.4zm0 27L1382.3-3.5zm0 26.9L1382.3 23.4z"/>
+    <linearGradient id="SVGID_704_" x1="1850.42" x2="1850.42" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_704_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_705_" x1="1873.74" x2="1873.74" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_705_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 974.5 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_706_" x1="1897.055" x2="1897.055" y1="105.52" y2="92.06" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_706_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 987.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_707_" x1="1897.055" x2="1897.055" y1="132.45" y2="118.99" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_707_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 961 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_708_" x1="1920.37" x2="1920.37" y1="118.99" y2="105.52" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_708_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 974.5 1932 961" opacity=".6"/>
+    <linearGradient id="SVGID_709_" x1="1920.37" x2="1920.37" y1="145.91" y2="132.45" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_709_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1908.7 947.5 1932 934" opacity=".6"/>
+    <linearGradient id="SVGID_710_" x1="1780.475" x2="1780.475" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_710_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_711_" x1="1803.79" x2="1803.79" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_711_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_712_" x1="1803.79" x2="1803.79" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_712_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_713_" x1="1827.105" x2="1827.105" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_713_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_714_" x1="1850.42" x2="1850.42" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_714_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_715_" x1="1827.105" x2="1827.105" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_715_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_716_" x1="1850.42" x2="1850.42" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_716_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_717_" x1="1873.74" x2="1873.74" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_717_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_718_" x1="1897.055" x2="1897.055" y1="51.68" y2="38.22" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_718_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1041.8 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_719_" x1="1873.74" x2="1873.74" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_719_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_720_" x1="1897.055" x2="1897.055" y1="78.6" y2="65.14" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_720_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1014.9 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_721_" x1="1920.37" x2="1920.37" y1="65.14" y2="51.68" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_721_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1028.3 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_722_" x1="1920.37" x2="1920.37" y1="92.06" y2="78.6" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_722_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1001.4 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_723_" x1="1780.475" x2="1780.475" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_723_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_724_" x1="1780.475" x2="1780.475" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_724_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1768.8 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_725_" x1="1803.79" x2="1803.79" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_725_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1792.1 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_726_" x1="1827.105" x2="1827.105" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_726_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_727_" x1="1827.105" x2="1827.105" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_727_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1815.4 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_728_" x1="1850.42" x2="1850.42" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_728_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1838.8 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_729_" x1="1873.74" x2="1873.74" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_729_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_730_" x1="1873.74" x2="1873.74" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_730_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1862.1 1055.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_731_" x1="1897.055" x2="1897.055" y1="24.76" y2="11.3" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_731_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1885.4 1068.7 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_732_" x1="1920.37" x2="1920.37" y1="11.3" y2="-2.16" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_732_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1082.2 23.3-13.5" opacity=".6"/>
+    <linearGradient id="SVGID_733_" x1="1920.37" x2="1920.37" y1="38.22" y2="24.76" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d"/>
+      <stop offset=".849" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_733_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1908.7 1055.2 23.3-13.5"/>
+    <linearGradient id="SVGID_734_" x1="1465.082" x2="1909.384" y1="280.899" y2="24.377" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".16" stop-color="#7d7d7d" stop-opacity=".1"/>
+      <stop offset=".45" stop-color="#7d7d7d" stop-opacity=".37"/>
+      <stop offset=".84" stop-color="#7d7d7d" stop-opacity=".81"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_734_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M1745.5 664.9 2002 813m0 26.9-279.8-161.6M2002 866.8l-303.1-175M2002 893.7l-326.4-188.5m303.1 202-326.4-188.5m303 201.9-326.4-188.5m303.1 202-326.4-188.5m303.1 201.9L1582.3 759m303.1 202L1559 772.6m303.1 201.9L1535.7 786m303.1 201.9-326.4-188.5m303 202L1489 813m303.1 201.9-326.4-188.5m303.1 201.9-326.4-188.4m326.4 215.3-326.4-188.5m326.4 215.5-326.4-188.5m326.4 215.4-326.4-188.4m301.8 201.1-301.8-174.2m255.2 174.2-255.1-147.3m208.4 147.3-208.5-120.4m161.9 120.4-161.9-93.5m115.3 93.5-115.2-66.5m68.5 66.5-68.6-39.6m22 39.6-22-12.7M2002 786l-233.2-134.6" opacity=".5"/>
+    <linearGradient id="SVGID_735_" x1="1885.41" x2="1885.41" y1="320.15" y2="806.24" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#7d7d7d" stop-opacity=".5"/>
+      <stop offset=".23" stop-color="#7d7d7d" stop-opacity=".55"/>
+      <stop offset=".53" stop-color="#7d7d7d" stop-opacity=".68"/>
+      <stop offset=".87" stop-color="#7d7d7d" stop-opacity=".9"/>
+      <stop offset="1" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_735_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m2002 409.1-233.2-134.6M2002 436l-233.2-134.6zm-233.2-107.6L2002 463zm0 26.9L2002 489.9zm0 26.9L2002 516.8zM2002 543.7l-233.2-134.6zM1768.8 436 2002 570.7zM2002 597.6 1768.8 463zm-233.2-107.7L2002 624.5zM2002 651.4l-233.2-134.6zm0 26.9-233.2-134.6zm0 27-233.2-134.6zm-233.2-107.7L2002 732.2zm0 26.9L2002 759.1z"/>
+    <linearGradient id="SVGID_736_" x1="1115.25" x2="1443.16" y1="99.18" y2="99.18" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".15" stop-color="#7d7d7d" stop-opacity=".8"/>
+      <stop offset=".3" stop-color="#7d7d7d" stop-opacity=".75"/>
+      <stop offset=".48" stop-color="#7d7d7d" stop-opacity=".62"/>
+      <stop offset=".7" stop-color="#7d7d7d" stop-opacity=".41"/>
+      <stop offset=".92" stop-color="#7d7d7d" stop-opacity=".12"/>
+      <stop offset="1" stop-color="#7d7d7d" stop-opacity="0"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_736_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1116 1028.3 326.4-188.5M1116 1055.2l326.4-188.5zm0 27 326.4-188.5zm326.4-161.6L1116 1109.1zm-301.8 201.2 301.8-174.2zm301.8-147.3-255.2 147.3zm0 26.9-208.5 120.4zm0 26.9-161.9 93.5zm0 26.9-115.3 66.5zm-68.6 66.6 68.6-39.6zm46.6 0 22-12.7z" opacity=".3"/>
+    <linearGradient id="SVGID_737_" x1="1115.25" x2="1746.26" y1="623.78" y2="623.78" gradientTransform="matrix(1 0 0 -1 0 1080)" gradientUnits="userSpaceOnUse">
+      <stop offset=".42" stop-color="#7d7d7d" stop-opacity="0"/>
+      <stop offset=".85" stop-color="#7d7d7d" stop-opacity=".77"/>
+      <stop offset=".98" stop-color="#7d7d7d"/>
+    </linearGradient>
+    <path fill="none" stroke="url(#SVGID_737_)" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="m1442.4 812.9-23.3 13.5m-303.1-525 349.7-201.9zM1489 113l-373 215.4zm23.3 13.4L1116 355.3zm23.4 13.5L1116 382.2zm23.3 13.5-443 255.8zm23.3 13.4L1116 436zm23.3 13.5L1116 463zm23.3 13.4L1116 489.9zm23.3 13.5L1116 516.8zm23.4 13.5-559.6 323zm23.3 13.4L1116 570.7zm23.3 13.5-606.2 350zm23.3 13.4L1116 624.5zM1116 274.5l326.4-188.4zM1442.4 463 1116 651.4zm0 26.9-303.1 175zm0 26.9-279.8 161.5zm0 26.9-256.5 148.1zm0 27-233.2 134.6zm0 26.9-209.8 121.1zm0 26.9-186.5 107.7zm0 26.9-163.2 94.2zm0 26.9-139.9 80.8zm0 27-116.6 67.3zm0 26.9-93.3 53.8zm0 26.9-70 40.4zm0 26.9-46.6 26.9z" opacity=".4"/>
+  </g>
+</svg>
diff --git a/content/nomad/v1.9.x/img/nomad-pe-cores.png b/content/nomad/v1.9.x/img/nomad-pe-cores.png
new file mode 100644
index 0000000000..e11c011d6e
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-pe-cores.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-vars-leader-election-sdk.png b/content/nomad/v1.9.x/img/nomad-vars-leader-election-sdk.png
new file mode 100644
index 0000000000..a547218579
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-vars-leader-election-sdk.png differ
diff --git a/content/nomad/v1.9.x/img/nomad-workload.png b/content/nomad/v1.9.x/img/nomad-workload.png
new file mode 100644
index 0000000000..c47dd9ab82
Binary files /dev/null and b/content/nomad/v1.9.x/img/nomad-workload.png differ
diff --git a/content/nomad/v1.9.x/img/og-image.png b/content/nomad/v1.9.x/img/og-image.png
new file mode 100644
index 0000000000..c5497102ba
Binary files /dev/null and b/content/nomad/v1.9.x/img/og-image.png differ
diff --git a/content/nomad/v1.9.x/img/pattern.svg b/content/nomad/v1.9.x/img/pattern.svg
new file mode 100644
index 0000000000..bdbba31e7b
--- /dev/null
+++ b/content/nomad/v1.9.x/img/pattern.svg
@@ -0,0 +1,319 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="600" height="360" fill="none" viewBox="0 0 600 360" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".5">
+    <mask id="a" width="600" height="360" x="0" y="0" mask-type="alpha" maskUnits="userSpaceOnUse">
+      <path fill="var(--nomad, #60dea9)" d="M0 0h600v360H0z"/>
+    </mask>
+    <g mask="url(#a)">
+      <path fill="url(#b)" d="M417.339 324.572c-.24 0-.401-.08-.481-.321-.16-.321-.08-.641.241-.802l18.677-10.823c.32-.161.641-.08.801.24.16.321.08.642-.24.802l-18.677 10.824c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#c)" d="M436.096 313.828c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#d)" d="M454.773 324.572c-.241 0-.401-.08-.481-.321-.16-.321-.08-.641.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.081.642-.24.802l-18.676 10.824c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#e)" d="M454.773 303.005c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#f)" d="M342.633 367.785c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.677 10.824c-.16 0-.24.08-.32.08" opacity=".4"/>
+      <path fill="url(#g)" d="M361.309 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.642-.08.802.24.16.321.08.642-.24.802l-18.677 10.823c-.08.081-.241.081-.321.081" opacity=".5"/>
+      <path fill="url(#h)" d="M379.986 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-18.676 10.824c-.081 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#i)" d="M379.986 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.081.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#j)" d="M398.663 356.962c-.241 0-.401-.081-.481-.321-.161-.321-.081-.642.24-.802l18.677-10.823c.32-.161.641-.08.801.24.161.321.08.642-.24.802l-18.677 10.823c-.08.081-.16.081-.32.081" opacity=".7"/>
+      <path fill="url(#k)" d="M417.339 367.785c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.677-10.824c.32-.16.641-.08.801.241.16.32.08.641-.24.801l-18.677 10.824c-.08 0-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#l)" d="M398.663 335.395c-.241 0-.401-.08-.481-.321-.161-.32-.081-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08 0-.16.08-.32.08" opacity=".7"/>
+      <path fill="url(#m)" d="M417.339 346.138c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.241-.802l18.677-10.824c.32-.16.641-.08.801.241s.08.641-.24.802l-18.677 10.823c-.08.08-.16.08-.321.08" opacity=".8"/>
+      <path fill="url(#n)" d="M436.096 356.962c-.24 0-.401-.081-.481-.321-.16-.321-.08-.642.241-.802l18.676-10.823c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-18.676 10.823a.6.6 0 0 1-.321.081" opacity=".9"/>
+      <path fill="url(#o)" d="M454.773 367.785c-.241 0-.401-.08-.481-.321-.16-.32-.08-.641.24-.801l18.677-10.824c.32-.16.641-.08.801.241.161.32.081.641-.24.801l-18.676 10.824c-.161 0-.241.08-.321.08" opacity=".6"/>
+      <path fill="url(#p)" d="M436.096 335.395c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l18.676-10.824c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-18.676 10.823c-.161 0-.241.08-.321.08" opacity=".9"/>
+      <path fill="url(#q)" d="M454.773 346.138c-.241 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l18.677-10.824c.32-.16.641-.08.801.241s.081.641-.24.802l-18.676 10.823c-.161.08-.241.08-.321.08" opacity=".6"/>
+      <path fill="var(--gray-4, #bfbfc0)" d="M641.62 389.351c-.241 0-.401-.08-.481-.32-.161-.321-.08-.642.24-.802l18.677-10.823c.321-.161.641-.081.802.24.16.321.08.642-.241.802l-18.677 10.823c-.08 0-.16.08-.32.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l37.353-21.567c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-37.353 21.567c-.08.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.48-.321-.161-.321-.081-.641.24-.802l56.03-32.389c.321-.161.641-.081.802.24.16.321.08.641-.241.802l-56.03 32.39c-.08 0-.24.08-.321.08m-18.676-10.823c-.241 0-.401-.081-.481-.321-.16-.321-.08-.642.24-.802l74.787-43.133c.321-.16.641-.08.802.241.16.32.08.641-.241.801l-74.787 43.133c-.16.081-.24.081-.32.081m-18.677-10.824c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l93.463-53.957c.321-.16.641-.08.802.241.16.321.08.641-.241.802l-93.463 53.956c-.161.08-.241.08-.321.08m-18.677-10.743c-.24 0-.4-.08-.481-.321-.16-.32-.08-.641.241-.801l112.14-64.78c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-112.14 64.78c-.16 0-.24.08-.321.08m-18.756-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.08-.641.24-.802l130.817-75.523c.321-.16.641-.08.802.241.16.321.08.641-.241.802L529.8 324.491c-.08.081-.16.081-.32.081m-18.677-10.744c-.24 0-.401-.08-.481-.32-.16-.321-.08-.642.24-.802l149.494-86.346c.321-.161.641-.08.802.24.16.321.08.642-.241.802l-149.493 86.346c-.081 0-.241.08-.321.08m-18.677-10.823c-.24 0-.401-.08-.481-.321-.16-.32-.08-.641.241-.801l168.17-97.09c.321-.16.641-.08.802.241.16.32.08.641-.241.802l-168.17 97.089c-.08.08-.241.08-.321.08m-18.676-10.823c-.241 0-.401-.08-.481-.321-.161-.321-.081-.641.24-.802l186.927-107.912c.321-.161.641-.081.802.24.16.321.08.641-.241.802L473.77 292.102c-.16.08-.24.08-.32.08" opacity=".8"/>
+      <path fill="url(#r)" d="M660.297 680.7c-.081 0-.241 0-.321-.08L473.049 572.707c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 551.141c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.129 529.574c-.32-.16-.401-.561-.24-.802.16-.32.561-.401.801-.24l186.927 107.913c.321.16.401.561.241.801-.08.161-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.129 507.927c-.32-.16-.401-.561-.24-.801.16-.321.561-.401.801-.241l186.927 107.913c.321.16.401.561.241.802-.08.24-.321.4-.561.4m0-21.646c-.081 0-.241 0-.321-.08L473.049 486.361c-.321-.161-.401-.561-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 464.794c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 443.228c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 421.661c-.321-.16-.401-.561-.241-.802.161-.32.562-.4.802-.24l186.927 107.913c.321.16.401.561.24.801 0 .161-.24.321-.48.321m0-21.566c-.081 0-.241 0-.321-.081L473.049 400.095c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .16-.24.321-.48.321m0-21.647c-.081 0-.241 0-.321-.08L473.049 378.448c-.321-.16-.401-.561-.241-.802.161-.32.562-.401.802-.24l186.927 107.912c.321.161.401.562.24.802 0 .241-.24.321-.48.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 356.881c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .24-.24.32-.48.32m0-21.566c-.081 0-.241 0-.321-.08L473.049 335.315c-.321-.16-.401-.561-.241-.802.161-.321.562-.401.802-.24l187.007 107.912c.321.161.401.562.241.802-.08.241-.321.321-.561.321m0-21.567c-.081 0-.241 0-.321-.08L473.049 313.748c-.321-.16-.401-.561-.241-.801.161-.321.562-.401.802-.241l186.927 107.913c.321.16.401.561.24.802 0 .16-.24.32-.48.32m0-21.646c-.081 0-.241 0-.321-.08L473.049 292.102c-.321-.161-.401-.562-.241-.802.161-.321.562-.401.802-.241l186.927 107.913c.321.161.401.561.24.802 0 .24-.24.321-.48.321" opacity=".6"/>
+      <g opacity=".75">
+        <path fill="url(#s)" d="M128.311 94.342c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.161-.642.081-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#t)" d="M109.554 105.085c.24 0 .401.08.481.321.16.32.08.641-.241.801l-18.676 10.824c-.32.16-.641.08-.802-.241-.16-.321-.08-.641.24-.802l18.677-10.823c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#u)" d="M90.877 94.342c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 106.287c-.32.161-.641.081-.801-.24s-.08-.641.24-.802l18.677-10.823c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#v)" d="M90.877 115.908c.24 0 .4.08.481.321.16.321.08.641-.24.802L72.44 127.854c-.32.16-.641.08-.801-.241-.16-.32-.08-.641.24-.801l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#w)" d="M203.017 51.128c.241 0 .401.08.481.321.161.32.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#x)" d="M184.341 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#y)" d="M165.664 51.128c.241 0 .401.08.481.321.16.32.08.642-.24.802l-18.677 10.823c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#z)" d="M165.664 72.775c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#A)" d="M146.987 61.952c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.823c-.32.16-.641.08-.801-.24s-.08-.641.24-.802l18.677-10.823c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#B)" d="M128.311 51.128c.24 0 .401.08.481.321.16.32.08.642-.241.802l-18.676 10.823c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#C)" d="M146.987 83.518c.241 0 .401.08.481.32.161.322.081.642-.24.803l-18.677 10.823c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#D)" d="M128.311 72.775c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#E)" d="M109.554 61.952c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 73.897c-.32.16-.641.08-.802-.24-.16-.32-.08-.641.24-.802l18.677-10.823c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#F)" d="M90.877 51.128c.24 0 .4.08.481.321.16.32.08.642-.24.802L72.44 63.074c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#G)" d="M109.554 83.518c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 95.464c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+        <path fill="url(#H)" d="M90.877 72.775c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 84.721c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#I)" d="M277.804 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L259.368 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#J)" d="M259.128 18.819c.24 0 .4.08.481.32.16.321.08.642-.241.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L258.807 18.9c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#K)" d="M240.371 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L221.935 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.241-.802L240.05 8.075c.16-.08.241-.08.321-.08"/>
+        <path fill="url(#L)" d="M240.371 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.16 0 .241-.08.321-.08"/>
+        <path fill="url(#M)" d="M221.694 18.819c.241 0 .401.08.481.32.161.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.802L221.374 18.9c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#N)" d="M203.017 7.995c.241 0 .401.08.481.321.161.32.081.641-.24.802L184.581 19.94c-.32.16-.641.08-.801-.24-.161-.321-.081-.642.24-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#O)" d="M221.694 40.385c.241 0 .401.08.481.32.161.322.08.642-.24.803L203.258 52.33c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#P)" d="M203.017 29.562c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.24-.161-.322-.081-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#Q)" d="M184.341 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.241-.16-.32-.08-.641.24-.802L184.02 18.9c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#R)" d="M165.664 7.995c.241 0 .401.08.481.321.16.32.08.641-.24.802L147.228 19.94c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.676-10.824c.081-.08.241-.08.321-.08"/>
+        <path fill="url(#S)" d="M184.341 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L165.905 52.33c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.08-.08.241-.08.321-.08"/>
+        <path fill="url(#T)" d="M165.664 29.562c.241 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.676-10.823c.081 0 .241-.08.321-.08"/>
+        <path fill="url(#U)" d="M146.987 18.819c.241 0 .401.08.481.32.161.321.081.642-.24.802l-18.677 10.824c-.32.16-.641.08-.801-.241-.161-.32-.08-.641.24-.802L146.667 18.9c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#V)" d="M128.311 7.995c.24 0 .401.08.481.321.16.32.08.641-.241.802L109.875 19.94c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L127.99 8.075c.08-.08.16-.08.321-.08"/>
+        <path fill="url(#W)" d="M146.987 40.385c.241 0 .401.08.481.32.161.322.081.642-.24.803L128.551 52.33c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08-.08.16-.08.32-.08"/>
+        <path fill="url(#X)" d="M128.311 29.562c.24 0 .401.08.481.32.16.321.08.642-.241.802l-18.676 10.824c-.321.16-.642.08-.802-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#Y)" d="M109.554 18.819c.24 0 .401.08.481.32.16.321.08.642-.241.802L91.118 30.765c-.32.16-.641.08-.802-.241-.16-.32-.08-.641.24-.802L109.234 18.9c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#Z)" d="M90.877 7.995c.24 0 .4.08.481.321.16.32.08.641-.24.802L72.44 19.94c-.32.16-.641.08-.801-.24-.16-.321-.08-.642.24-.802L90.557 8.075c.16-.08.24-.08.32-.08"/>
+        <path fill="url(#aa)" d="M109.554 40.385c.24 0 .401.08.481.32.16.322.08.642-.241.803L91.118 52.33c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161-.08.241-.08.321-.08"/>
+        <path fill="url(#ab)" d="M90.877 29.562c.24 0 .4.08.481.32.16.321.08.642-.24.802L72.44 41.508c-.32.16-.641.08-.801-.24-.16-.322-.08-.642.24-.803l18.677-10.823c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#ac)" d="M296.481-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L278.045 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802L296.16-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ad)" d="M259.128-2.828c.24 0 .4.08.481.32.16.321.08.642-.241.803L240.691 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.321-.08"/>
+        <path fill="url(#ae)" d="M221.694-2.828c.241 0 .401.08.481.32.161.321.08.642-.24.803L203.258 9.118c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l18.677-10.824c.16 0 .24-.08.32-.08"/>
+        <path fill="url(#af)" d="M184.341-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L165.905 9.118c-.321.16-.642.08-.802-.24-.16-.321-.08-.642.24-.802L184.02-2.748c.08 0 .241-.08.321-.08"/>
+        <path fill="url(#ag)" d="M146.987-2.828c.241 0 .401.08.481.32.161.321.081.642-.24.803L128.551 9.118c-.32.16-.641.08-.801-.24-.161-.321-.08-.642.24-.802l18.677-10.824c.08 0 .16-.08.32-.08"/>
+        <path fill="url(#ah)" d="M109.554-2.828c.24 0 .401.08.481.32.16.321.08.642-.241.803L91.118 9.118c-.32.16-.641.08-.802-.24-.16-.321-.08-.642.24-.802l18.677-10.824c.161 0 .241-.08.321-.08"/>
+      </g>
+      <path fill="url(#ai)" d="M-95.97 29.562c.24 0 .401.08.481.32.16.321.08.642-.24.802l-18.677 10.824c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l18.677-10.823c.08 0 .16-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.322.081.642-.24.803l-37.353 21.566c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l37.353-21.567c.08-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.321.16.32.08.641-.24.802l-56.03 32.39c-.321.16-.641.08-.802-.24-.16-.322-.08-.642.241-.803l56.03-32.39c.08 0 .24-.08.32-.08m18.676 10.824c.24 0 .401.08.481.32.16.321.08.642-.24.802l-74.787 43.133c-.321.16-.641.08-.802-.24-.16-.321-.08-.642.241-.802l74.787-43.133c.16-.08.24-.08.32-.08m18.677 10.823c.24 0 .4.08.48.32.161.321.081.642-.24.802l-93.463 53.957c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l93.463-53.957c.16-.08.24-.08.32-.08m18.677 10.743c.24 0 .4.08.48.32.16.322.08.642-.24.803l-112.14 64.779c-.321.161-.641.081-.802-.24-.16-.321-.08-.642.241-.802l112.14-64.78c.16 0 .24-.08.32-.08m18.76 10.824c.24 0 .4.08.48.32.16.32.08.642-.24.802l-130.817 75.523c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801L15.85 94.422c.08-.08.16-.08.32-.08m18.676 10.743c.24 0 .4.08.481.32.16.321.08.642-.24.802l-149.494 86.346c-.321.161-.641.081-.802-.24-.16-.321-.08-.641.241-.802l149.493-86.346c.08 0 .24-.08.321-.08m18.677 10.823c.24 0 .4.08.48.321.161.32.08.641-.24.802l-168.17 97.089c-.321.16-.641.08-.802-.241-.16-.32-.08-.641.241-.801l168.17-97.09c.08-.08.24-.08.32-.08M72.2 126.731c.24 0 .401.081.481.321.16.321.08.642-.24.802l-186.927 107.913c-.321.16-.641.08-.802-.241-.16-.321-.08-.641.241-.802L71.88 126.812c.16-.081.24-.081.32-.081" opacity=".8"/>
+      <path fill="url(#aj)" d="M-114.647-261.787c.081 0 .241 0 .321.08L72.601-153.794c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.24-.802 0-.24.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-132.227c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.24-.801 0-.241.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.081L72.521-110.661c.32.161.4.562.24.802-.16.321-.56.401-.801.241l-186.927-107.913c-.321-.161-.401-.561-.241-.802.08-.16.321-.321.561-.321m0 21.567c.081 0 .241 0 .321.08L72.521-89.014c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.913c-.321-.16-.401-.561-.241-.801a.6.6 0 0 1 .561-.401m0 21.647c.081 0 .241 0 .321.08L72.601-67.447c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-45.881c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-152.75c-.321-.161-.401-.562-.24-.802 0-.241.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601-24.314c.32.16.4.56.24.801-.16.321-.56.401-.801.24l-186.927-107.912c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.566c.081 0 .241 0 .321.08L72.601-2.748c.32.16.4.561.24.802-.16.32-.56.4-.801.24l-186.927-107.912c-.321-.161-.401-.562-.24-.802 0-.16.24-.321.48-.321m0 21.567c.081 0 .241 0 .321.08L72.601 18.819c.32.16.4.56.24.801-.16.321-.56.401-.801.24L-114.887-88.051c-.321-.16-.401-.561-.24-.802 0-.16.24-.32.48-.32m0 21.646c.081 0 .241 0 .321.08L72.601 40.466c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.887-66.404c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32m0 21.567c.081 0 .241 0 .321.08L72.601 62.032c.32.16.4.561.24.802-.16.32-.56.4-.801.24L-114.887-44.839c-.321-.16-.401-.56-.24-.801 0-.24.24-.321.48-.321m0 21.566c.081 0 .241 0 .321.08L72.601 83.599c.32.16.4.562.24.802-.16.32-.56.401-.801.24L-114.967-23.271c-.321-.16-.401-.561-.241-.802.08-.24.321-.32.561-.32m0 21.567c.081 0 .241 0 .321.08L72.601 105.165c.32.16.4.561.24.802-.16.32-.56.401-.801.24L-114.887-1.706c-.321-.16-.401-.56-.24-.801 0-.16.24-.321.48-.321m0 21.647c.081 0 .241 0 .321.08L72.601 126.812c.32.16.4.561.24.801-.16.321-.56.401-.801.241L-114.887 19.941c-.321-.16-.401-.561-.24-.802 0-.24.24-.32.48-.32"/>
+    </g>
+  </g>
+  <defs>
+    <linearGradient id="b" x1="421.748" x2="431.696" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="c" x1="440.505" x2="450.453" y1="316.458" y2="299.23" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="d" x1="459.181" x2="469.13" y1="327.201" y2="309.973" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="e" x1="459.181" x2="469.13" y1="305.634" y2="288.407" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="f" x1="347.041" x2="356.99" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="g" x1="365.718" x2="375.666" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="h" x1="384.395" x2="394.343" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="i" x1="384.395" x2="394.343" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="j" x1="403.071" x2="413.02" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="k" x1="421.748" x2="431.696" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="l" x1="403.071" x2="413.02" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="m" x1="421.748" x2="431.696" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="n" x1="440.505" x2="450.453" y1="359.591" y2="342.363" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="o" x1="459.181" x2="469.13" y1="370.414" y2="353.186" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="p" x1="440.505" x2="450.453" y1="338.024" y2="320.797" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="q" x1="459.181" x2="469.13" y1="348.768" y2="331.54" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="r" x1="566.886" x2="566.886" y1="680.721" y2="291.005" gradientUnits="userSpaceOnUse">
+      <stop stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".5"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="s" x1="123.902" x2="113.954" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="t" x1="105.145" x2="95.197" y1="102.456" y2="119.683" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="u" x1="86.469" x2="76.52" y1="91.712" y2="108.94" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="v" x1="86.469" x2="76.52" y1="113.279" y2="130.507" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="w" x1="198.609" x2="188.66" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="x" x1="179.932" x2="169.984" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="y" x1="161.255" x2="151.307" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="z" x1="161.255" x2="151.307" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="A" x1="142.579" x2="132.63" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="B" x1="123.902" x2="113.954" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="C" x1="142.579" x2="132.63" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="D" x1="123.902" x2="113.954" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="E" x1="105.145" x2="95.197" y1="59.322" y2="76.55" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="F" x1="86.469" x2="76.52" y1="48.499" y2="65.727" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="G" x1="105.145" x2="95.197" y1="80.889" y2="98.117" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="H" x1="86.469" x2="76.52" y1="70.146" y2="87.374" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="I" x1="273.396" x2="263.447" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="J" x1="254.719" x2="244.77" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="K" x1="235.962" x2="226.014" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="L" x1="235.962" x2="226.014" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="M" x1="217.286" x2="207.337" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="N" x1="198.609" x2="188.66" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="O" x1="217.286" x2="207.337" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="P" x1="198.609" x2="188.66" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Q" x1="179.932" x2="169.983" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="R" x1="161.255" x2="151.307" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="S" x1="179.932" x2="169.984" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="T" x1="161.255" x2="151.307" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="U" x1="142.579" x2="132.63" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="V" x1="123.902" x2="113.954" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="W" x1="142.579" x2="132.63" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="X" x1="123.902" x2="113.954" y1="26.933" y2="44.161" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Y" x1="105.145" x2="95.197" y1="16.189" y2="33.417" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="Z" x1="86.469" x2="76.52" y1="5.366" y2="22.594" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="aa" x1="105.145" x2="95.197" y1="37.756" y2="54.984" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ab" x1="86.469" x2="76.52" y1="26.933" y2="44.16" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ac" x1="292.072" x2="282.124" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ad" x1="254.719" x2="244.77" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ae" x1="217.286" x2="207.337" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="af" x1="179.932" x2="169.984" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ag" x1="142.579" x2="132.63" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ah" x1="105.145" x2="95.197" y1="-5.457" y2="11.771" gradientUnits="userSpaceOnUse">
+      <stop offset=".302" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset=".825" stop-color="var(--gray-4, #bfbfc0)"/>
+    </linearGradient>
+    <linearGradient id="ai" x1="65.071" x2="-.052" y1="202.35" y2="145.203" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".8"/>
+    </linearGradient>
+    <linearGradient id="aj" x1="72.805" x2="-115.887" y1="-66.327" y2="-66.327" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="var(--gray-4, #bfbfc0)" stop-opacity=".9"/>
+      <stop offset="1" stop-color="var(--gray-4, #bfbfc0)" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/practice-pattern.svg b/content/nomad/v1.9.x/img/practice-pattern.svg
new file mode 100644
index 0000000000..e19748990c
--- /dev/null
+++ b/content/nomad/v1.9.x/img/practice-pattern.svg
@@ -0,0 +1,36 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="456" height="589" fill="none" viewBox="0 0 456 589" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <g opacity=".75">
+    <g clip-path="url(#a)">
+      <path fill="#60DEA9" d="M113.645 158.649a.8.8 0 0 0 .762-.032L228 93.517v-1.824l-114.006 65.339L.082 91.752 0 91.704v1.817l113.637 65.127h.008Zm.762-21.81L228 71.739v-1.824L114 135.25.082 69.973 0 69.927v1.817l113.597 65.105a.8.8 0 0 0 .81-.01m-.318 10.992a.5.5 0 0 0 .147-.027.6.6 0 0 0 .171-.074L228 82.625v-1.823L114 146.14.082 80.865 0 80.818v1.818l113.603 65.108a.78.78 0 0 0 .486.087m-.444 21.71a.8.8 0 0 0 .762-.033L228 104.409v-1.824l-114 65.333L.082 102.638 0 102.591v1.817l113.637 65.133zm-.002 21.778h.002a.81.81 0 0 0 .704 0L228 126.187v-1.824l-114.006 65.339L.082 124.415 0 124.368v1.818l113.599 65.111zm.002-10.892a.81.81 0 0 0 .704 0L228 115.3v-1.829L114 178.81.082 113.529 0 113.483v1.817l113.637 65.127z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#b)">
+      <path d="M68.186 393.001 0 353.926v1.823l65 37.252zm-38.002 0L0 375.703v1.824l27.004 15.474zm-18.998 0L0 386.59v1.823l8.006 4.588zm75.752-.141L0 343.039v1.824l83.998 48.138h3.185zm-37.756.141L0 364.817v1.824l45.997 26.36zm56.766-.141L0 332.142v1.824l103.013 59.035h3.18zm8.415-26.318L228 301.409v-1.817l-.082.047L114 364.919 0 299.586v1.823l113.594 65.1a.8.8 0 0 0 .761.033zm.035-21.798L228 279.637v-1.818l-.082.047L114 343.141 0 277.802v1.824l113.594 65.105q.08.048.17.074a.5.5 0 0 0 .147.027.77.77 0 0 0 .487-.088m-.035 10.906L228 290.523v-1.817l-.082.046-113.912 65.281L0 288.694v1.824l113.594 65.1a.8.8 0 0 0 .761.032zm.038 32.648L228 323.187v-1.818l-.082.047-113.912 65.287L0 321.364v1.823l113.651 65.133a.81.81 0 0 0 .704 0h.003zm.001-54.448L228 268.745v-1.817l-.082.046L114 332.25 0 266.916v1.824l113.594 65.1a.81.81 0 0 0 .808.01m-.039 43.578L228 312.301v-1.817l-.082.046L114 375.811 0 310.472v1.829l113.651 65.127a.8.8 0 0 0 .705 0z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#60DEA9" d="M26.89 393.001h3.22L228 506.412v1.845L27.136 393.142zm-18.754.141L228 519.146v-1.845l-216.89-124.3H7.89zm57 0L228 486.48v-1.845L68.11 393.001h-3.22zm-19 0L228 497.369v-1.845L49.11 393.001h-3.22zm38 0L228 475.591v-1.845L87.11 393.001h-3.22zm18.999 0L228 464.703v-1.845l-121.891-69.857h-3.219z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#d)">
+      <path d="M342.363 26.459 456 91.592v1.817l-.082-.047L342 28.082 228 93.415v-1.823l113.594-65.1a.8.8 0 0 1 .761-.033zm.035 21.798L456 113.364v1.818l-.082-.047L342 49.86l-114 65.339v-1.824L341.594 48.27a.7.7 0 0 1 .17-.074.5.5 0 0 1 .147-.027.77.77 0 0 1 .487.088m-.035-10.907L456 102.478v1.817l-.082-.046-113.912-65.281L228 104.307v-1.824l113.594-65.1a.8.8 0 0 1 .761-.033zm.038-32.647L456 69.813v1.819l-.082-.047L342.006 6.298 228 71.638v-1.824L341.651 4.68a.81.81 0 0 1 .704 0h.003l.043.022Zm.001 54.448L456 124.256v1.817l-.082-.046L342 60.751l-114 65.334v-1.824l113.594-65.1a.8.8 0 0 1 .808-.01m-.039-43.578L456 80.7v1.817l-.082-.046L342 17.19 228 82.53V80.7l113.651-65.127a.81.81 0 0 1 .705 0zM296.186 196 228 156.925v1.823L293 196zm-38.002 0L228 178.702v1.824L255.004 196zm-18.998 0L228 189.589v1.823l8.006 4.588zm75.752-.141L228 146.038v1.824L311.998 196h3.185zm-37.756.141L228 167.816v1.824L273.997 196zm56.766-.141L228 135.142v1.823L331.013 196h3.18z"/>
+    </g>
+    <g fill="#60DEA9" clip-path="url(#e)">
+      <path d="m374.675 196.071.054-.07h-2.148L228 382.444v2.768zm-63.276-.07h-2.147L228 300.775v2.769l83.344-107.473zm37.997 0h-2.148L228 349.775v2.769l121.341-156.473zm12.67 0h-2.148L228 366.107v2.768l134.011-172.804zm-25.333 0h-2.148L228 333.439v2.768l108.678-140.136zm-12.67 0h-2.148L228 317.107v2.768l96.008-123.804zm94.742 138.486a.86.86 0 0 0-.339-.251 1.2 1.2 0 0 0-.936.001.9.9 0 0 0-.348.266l-44.581 57.498h2.148l43.254-55.78L456 385.216v-2.772l-37.169-47.919zm-.802-79.934L456 303.548v-2.772l-37.169-47.919-.026-.038a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.935.001.9.9 0 0 0-.348.265L309.319 391.93l-.054.071h2.147zm.802 14.602a.86.86 0 0 0-.34-.251 1.22 1.22 0 0 0-.935.001.9.9 0 0 0-.348.265l-95.249 122.831h2.148l93.922-121.112L456 319.884v-2.772l-37.169-47.918zm-.802 15.984a1.2 1.2 0 0 0-.468.091.8.8 0 0 0-.31.231L334.659 391.93l-.055.071h2.148l81.251-104.78L456 336.216v-2.767l-37.195-47.967a.9.9 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.092m0 16.336c-.164 0-.326.032-.469.092a.8.8 0 0 0-.307.229l-69.898 90.134-.055.071h2.148l68.581-88.448L456 352.548v-2.767l-37.195-47.962a.86.86 0 0 0-.34-.251 1.2 1.2 0 0 0-.462-.093m.773 16.651a.4.4 0 0 0-.113-.102 1 1 0 0 0-.197-.116.4.4 0 0 0-.112-.039.7.7 0 0 0-.224-.047 1.1 1.1 0 0 0-.587.078l-.089.04-.002.004a.4.4 0 0 0-.1.069l-.051.042a.2.2 0 0 0-.066.061.5.5 0 0 0-.06.069l-57.237 73.816h2.147l55.918-72.116 37.997 49v-2.772l-37.206-47.969zm-.454-.113.002-.004zm.073.03.002-.002z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="a">
+      <path fill="#fff" d="M228 196H0V0h228z"/>
+    </clipPath>
+    <clipPath id="b">
+      <path fill="#fff" d="M228 393H0V197h228z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M0 393.001h228v196H0z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M456 196H228V0h228z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M456 392H228V196h228z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/usecase-callout-pattern.svg b/content/nomad/v1.9.x/img/usecase-callout-pattern.svg
new file mode 100644
index 0000000000..93b9784bf0
--- /dev/null
+++ b/content/nomad/v1.9.x/img/usecase-callout-pattern.svg
@@ -0,0 +1,22 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="175" height="350" fill="none" viewBox="0 0 175 350" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="175" height="350" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#C4C4C4" d="M0 0h175v350H0z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g fill="#000" clip-path="url(#b)">
+      <path d="M93.76 358.081 175 294.277v-1.78l-.058.046L93.5 356.492 12 292.491v1.786l81.21 63.772a.47.47 0 0 0 .269.111.45.45 0 0 0 .275-.079zm.025-21.353L175 272.95v-1.781l-.058.046L93.5 335.158 12 271.152v1.787l81.21 63.776a.44.44 0 0 0 .227.099.43.43 0 0 0 .348-.086m-.025 10.684L175 283.614v-1.781l-.058.046-81.438 63.948L12 281.822v1.786l81.21 63.772a.44.44 0 0 0 .545.032zm.027 31.981L175 315.611v-1.781l-.058.046-81.438 63.954L12 313.825v1.786l81.25 63.804a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078h.002l.03-.022Zm0-53.337L175 262.28v-1.78l-.058.045L93.5 324.489 12 260.488v1.787l81.21 63.771a.47.47 0 0 0 .288.111.46.46 0 0 0 .29-.101Zm-.027 42.689L175 304.947v-1.78l-.058.046L93.5 367.161 12 303.155v1.792l81.25 63.798a.46.46 0 0 0 .252.078.46.46 0 0 0 .252-.078zM60.747 192 12 230.278v-1.786L58.47 192zm-27.168 0L12 208.945v-1.787L31.305 192zm-13.582 0L12 198.28v-1.785L17.724 192zm54.156.138L12 240.942v-1.787L72.051 192h2.278zM47.161 192 12 219.608v-1.786L44.884 192zm40.582.138L12 251.616v-1.786L85.646 192h2.273z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="M126.253 0 175 38.278v-1.786L128.531 0zm-13.582 0 62.271 48.896.058.046v-1.787L114.949 0zm-13.59 0 75.861 59.57.058.046v-1.785L101.354 0zm40.758 0L175 27.608v-1.786L142.117 0zm27.164 0L175 6.28V4.495L169.276 0zm-13.582 0L175 16.945v-1.787L155.694 0zM93.707 68.544l-.007.01a.45.45 0 0 0-.2-.048.3.3 0 0 0-.055.008l-.037.007a.3.3 0 0 0-.055.013.5.5 0 0 0-.132.077L12 132.39v1.786L93.504 70.17l81.437 63.954.059.046v-1.78L93.786 68.607zm-.203 53.3a.2.2 0 0 0-.045.007.5.5 0 0 0-.254.107L12 185.725v1.787l81.499-64.001 81.442 63.943.059.047v-1.781l-81.213-63.777a.45.45 0 0 0-.283-.099m.144-42.645a.4.4 0 0 0-.222-.023.46.46 0 0 0-.209.1L12 143.053v1.792l81.499-64.006 81.442 63.949.059.046v-1.78L93.79 79.279a.4.4 0 0 0-.142-.08m.063 10.682-.007.008a.33.33 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 153.722v1.786l81.499-64 81.442 63.948.059.046v-1.78L93.786 89.94l-.075-.06Zm-.252 21.301a.5.5 0 0 0-.254.106L12 175.061v1.786l81.499-64.005 81.442 63.943.059.046v-1.78l-81.213-63.777a.35.35 0 0 0-.328-.092m.252-10.632-.007.008a.35.35 0 0 0-.24-.041.5.5 0 0 0-.258.107L12 164.392v1.786l81.499-64 81.442 63.943.059.046v-1.78L93.786 100.61z"/>
+      <path fill="#60DEA9" d="m51.845 90.8 1.139-.894L12 57.72v1.792l39.787 31.242.058.047Zm6.794-5.332 1.134-.894L12 47.056v1.786l46.58 36.58zm27.167-21.334 1.135-.893L12.058 4.435 12 4.39v1.786l73.748 57.913.058.046ZM72.22 74.798l1.139-.894-61.3-48.135-.059-.046v1.786l60.162 47.243zm6.793-5.332 1.139-.893-68.094-53.474-.058-.046v1.791L78.955 69.42zm-13.586 10.67 1.139-.894L12 36.386v1.792l53.369 41.911zM85.628 0 175 70.182v-1.793L87.902 0zM31.297 0l34.752 27.291.084.057 108.808 85.454.059.046v-1.786L33.57 0zm13.578 0 27.963 21.96.084.056 102.019 80.116.059.046v-1.786L47.156 0zM17.71 0l157.23 123.466.059.046v-1.786L19.992 0zm40.754 0L174.94 91.468l.059.046v-1.786L60.738 0zm13.582 0L174.94 80.799l.059.046V79.06L74.324 0z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M12 192h163v192H12z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M12 0h163v192H12z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/usecase-hero-pattern.svg b/content/nomad/v1.9.x/img/usecase-hero-pattern.svg
new file mode 100644
index 0000000000..1eaa5365da
--- /dev/null
+++ b/content/nomad/v1.9.x/img/usecase-hero-pattern.svg
@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="420" height="500" fill="none" viewBox="0 0 420 500" xmlns:xlink="http://www.w3.org/1999/xlink">
+  <mask id="a" width="420" height="500" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:alpha">
+    <path fill="#F2F2F3" d="M0 0h420v494a6 6 0 0 1-6 6H6a6 6 0 0 1-6-6z"/>
+  </mask>
+  <g mask="url(#a)">
+    <g clip-path="url(#b)">
+      <path fill="#000" d="M48.87 26.57-65.311 91.974v1.824l.082-.047L49.234 28.2 163.78 93.805v-1.83L49.643 26.602a.8.8 0 0 0-.766-.033zm-.036 21.889L-65.31 113.838v1.825l.082-.047L49.234 50.068 163.78 115.68v-1.831L49.643 48.471a.7.7 0 0 0-.32-.101.77.77 0 0 0-.489.089m.035-10.952-114.18 65.399v1.825l.082-.047L49.23 39.131l114.551 65.612v-1.831L49.643 37.539a.8.8 0 0 0-.766-.032zm-.038-32.785L-65.31 70.106v1.825l.082-.047L49.23 6.324l114.55 65.613v-1.83L49.585 4.7a.82.82 0 0 0-.708 0h-.002zm0 54.676-114.142 65.377v1.825l.082-.047L49.234 61.005l114.546 65.607v-1.831L49.643 59.408a.82.82 0 0 0-.813-.01Zm.038-43.76-114.18 65.4v1.824l.082-.047L49.234 17.262 163.78 82.874v-1.837L49.586 15.638a.82.82 0 0 0-.709 0z"/>
+      <path fill="#60DEA9" d="m95.268 196.819 68.512-39.238v1.83l-65.311 37.408zm38.184 0 30.328-17.37v1.831l-27.133 15.539zm19.089 0 11.239-6.438v1.831l-8.044 4.607zm-76.115-.141 87.354-50.029v1.831l-84.4 48.339h-3.2zm37.937.141 49.417-28.301v1.831l-46.217 26.47zm-57.038-.141 106.455-60.972v1.831L60.274 196.819h-3.195z"/>
+    </g>
+    <g clip-path="url(#c)">
+      <path fill="#000" d="m3.2 196.818-68.51 38.842v-1.812L0 196.818zm19.09 0-87.519 49.617-.082.047v-1.813l84.4-47.851h3.2Zm19.1 0-106.619 60.449-.082.046v-1.812l103.506-58.683zm-57.284 0-49.417 28.016v-1.813l46.216-26.203zm-38.178 0-11.239 6.373v-1.812l8.044-4.561zm19.089 0-30.328 17.195V212.2l27.133-15.382zm83.927 69.555.01.01a.9.9 0 0 1 .28-.049l.078.008.051.007.078.013a.8.8 0 0 1 .186.079l114.153 64.718v1.813L49.228 268.023-65.228 332.92l-.083.047v-1.807l114.143-64.724zm.285 54.086q.032 0 .063.007a.84.84 0 0 1 .357.108l114.131 64.708v1.813L49.236 322.15l-114.464 64.886-.083.047v-1.806l114.142-64.718a.8.8 0 0 1 .398-.1m-.202-43.274a.78.78 0 0 1 .605.078l114.148 64.718v1.817L49.236 278.849l-114.464 64.892-.083.047v-1.807l114.138-64.715a.7.7 0 0 1 .2-.081m-.089 10.839.01.009a.63.63 0 0 1 .337-.043.8.8 0 0 1 .363.109l114.132 64.708v1.813L49.236 289.676l-114.464 64.891-.083.047v-1.806l114.143-64.723zm.354 21.615a.84.84 0 0 1 .357.108l114.131 64.714v1.812L49.236 311.324-65.228 376.21l-.083.047v-1.807l114.142-64.717a.63.63 0 0 1 .461-.094m-.354-10.788.01.008a.65.65 0 0 1 .337-.042.9.9 0 0 1 .363.108l114.132 64.709v1.812L49.236 300.502l-114.464 64.886-.083.047v-1.806l114.143-64.718z"/>
+      <path fill="#60DEA9" d="m107.779 288.957-1.6-.907 57.601-32.661v1.818l-55.919 31.703zm-9.548-5.411-1.594-.907 67.143-38.071v1.812l-65.466 37.119zm-38.184-21.648-1.593-.907 105.244-59.672.082-.047v1.812L60.13 261.851zm19.095 10.821-1.6-.907 86.156-48.845.082-.047v1.812l-84.556 47.94zm-9.547-5.411-1.6-.906 95.703-54.262.082-.047v1.818l-94.103 53.351zm19.095 10.827-1.6-.907 76.69-43.487v1.818l-75.008 42.529zm-28.392-81.317-125.609 71.216v-1.818l122.413-69.398zm76.361 0-48.844 27.693-.117.058-152.926 86.714-.083.047v-1.813l198.775-112.699zm-19.084 0-39.301 22.283-.118.058-143.384 81.297-.083.047v-1.812l179.68-101.873zm38.178 0L-65.228 322.104l-.083.047v-1.812l217.858-123.521zm-57.278 0-163.703 92.817-.083.047v-1.813L95.28 196.818zm-19.089 0-144.614 81.99-.083.047v-1.812l141.496-80.225z"/>
+    </g>
+    <g clip-path="url(#d)">
+      <path fill="#000" d="m232.292 391.649-68.512-38.842v1.812l65.311 37.03zm-38.184 0-30.328-17.194v1.813l27.133 15.381zm-19.089 0-11.239-6.373v1.812l8.044 4.561zm76.115-.14-87.354-49.523v1.812l84.4 47.851h3.201zm-37.937.14-49.417-28.015v1.812l46.217 26.203zm57.038-.14L163.78 331.154v1.812l103.506 58.683h3.195z"/>
+    </g>
+    <g fill="#000" clip-path="url(#e)">
+      <path d="m-65.228 407.19-.083-.048v1.825l114.148 65.381a.86.86 0 0 0 .398.098.8.8 0 0 0 .397-.106l114.148-65.378v-1.837L49.235 472.737zm0 21.863-.083-.048v1.825l114.148 65.387c.123.064.26.097.398.098a.8.8 0 0 0 .397-.107l114.148-65.377V429L49.229 494.611zm0-10.932-.083-.047v1.825L48.837 485.28c.123.064.26.097.398.098a.8.8 0 0 0 .397-.101l114.148-65.384v-1.831L49.229 483.674zm0 21.869-.083-.047v1.825l114.109 65.356.032.021a.8.8 0 0 0 .405.107.8.8 0 0 0 .397-.107l114.148-65.377v-1.837L49.235 505.543zm0 10.931-.083-.047v1.825l114.148 65.386a.9.9 0 0 0 .398.099.8.8 0 0 0 .397-.102L163.78 452.7v-1.832L49.229 516.481zm0-54.669-.083-.047v1.825l114.142 65.378.11.054.007-.007a.78.78 0 0 0 .684-.053l114.148-65.377v-1.832L49.235 461.8zm182.969 192.216-182.97-104.792-.082-.047v1.831l179.852 103.008zm19.09 0-202.06-115.723-.082-.048v1.831l198.94 113.94zm19.1 0-221.16-126.666-.082-.048v1.831L152.73 588.468zm-57.285 0-163.874-93.855-.083-.047v1.831l160.762 92.071zm-38.171 0-125.703-71.991-.083-.047v1.83l122.584 70.208zm19.083 0-144.786-82.923-.083-.047v1.83l141.673 81.14z"/>
+    </g>
+    <g clip-path="url(#f)">
+      <path fill="#60DEA9" d="M270.398 391.649h-3.235L163.78 450.862v1.853l106.371-60.924zm-95.455 0-11.163 6.395v-1.853l7.928-4.542zm76.118.142-87.281 49.99v-1.853l84.292-48.279h3.235zm-19.091 0-68.19 39.056v-1.853l65.201-37.345h3.236zm-38.182 0-30.008 17.187v-1.854l27.019-15.475h3.236zm19.091 0-49.099 28.122v-1.853l46.11-26.411h3.235z"/>
+    </g>
+  </g>
+  <defs>
+    <clipPath id="b">
+      <path fill="#fff" d="M163.78 0H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="c">
+      <path fill="#fff" d="M163.78 196.818H-65.311v194.831H163.78z"/>
+    </clipPath>
+    <clipPath id="d">
+      <path fill="#fff" d="M392.871 196.818H163.78v194.831h229.091z"/>
+    </clipPath>
+    <clipPath id="e">
+      <path fill="#fff" d="M163.78 391.649H-65.311v196.819H163.78z"/>
+    </clipPath>
+    <clipPath id="f">
+      <path fill="#fff" d="M392.871 391.649H163.78v196.819h229.091z"/>
+    </clipPath>
+  </defs>
+</svg>
diff --git a/content/nomad/v1.9.x/img/vault-integration-auth-method.png b/content/nomad/v1.9.x/img/vault-integration-auth-method.png
new file mode 100644
index 0000000000..b6c1d601b9
Binary files /dev/null and b/content/nomad/v1.9.x/img/vault-integration-auth-method.png differ
diff --git a/content/nomad/v1.9.x/img/vault-integration-auth-overview.png b/content/nomad/v1.9.x/img/vault-integration-auth-overview.png
new file mode 100644
index 0000000000..ad26bed43a
Binary files /dev/null and b/content/nomad/v1.9.x/img/vault-integration-auth-overview.png differ
diff --git a/content/nomad/v1.9.x/img/vault-integration-wid-acl-token.png b/content/nomad/v1.9.x/img/vault-integration-wid-acl-token.png
new file mode 100644
index 0000000000..7fd4b406ea
Binary files /dev/null and b/content/nomad/v1.9.x/img/vault-integration-wid-acl-token.png differ
diff --git a/content/nomad/v1.9.x/redirects.jsonc b/content/nomad/v1.9.x/redirects.jsonc
new file mode 100644
index 0000000000..04ac5ac372
--- /dev/null
+++ b/content/nomad/v1.9.x/redirects.jsonc
@@ -0,0 +1,126 @@
+/**
+ * Copyright (c) HashiCorp, Inc.
+ * SPDX-License-Identifier: BUSL-1.1
+ */
+
+/**
+ * Define your custom redirects within this file.
+ *
+ * Vercel"s redirect documentation:
+ * https://nextjs.org/docs/api-reference/next.config.js/redirects
+ *
+ * Relative paths with fragments (#) are not supported.
+ * For destinations with fragments, use an absolute URL.
+ *
+ * Playground for testing url pattern matching: https://npm.runkit.com/path-to-regexp
+ *
+ * Note that redirects defined in a product"s redirects file are applied to
+ * the developer.hashicorp.com domain, which is where the documentation content
+ * is rendered. Redirect sources should be prefixed with the product slug
+ * to ensure they are scoped to the product"s section. Any redirects that are
+ * not prefixed with a product slug will be ignored.
+ */
+[
+  /*
+  Example redirect:
+  {
+    "source": "/nomad/docs/internal-docs/my-page",
+    "destination": "/nomad/docs/internals/my-page",
+    "permanent": true,
+  },
+  */
+
+  /**
+   * /s/* redirects for useful links that need a stable URL but we may need to
+   * change its destination in the future.
+   */
+  {
+    "source": "/nomad/s/port-plan-failure",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/operations/monitoring-nomad#progress",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/envoy-bootstrap-error",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/consul/service-mesh#troubleshooting",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/s/vault-workload-identity-migration",
+    "destination":
+      "https://developer.hashicorp.com/nomad/docs/integrations/vault/acl#migrating-to-using-workload-identity-with-vault",
+    "permanent": false,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/internals/:path*",
+    "destination": "/nomad/tools/autoscaling/concepts/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/checks",
+    "destination": "/nomad/tools/autoscaling/concepts/policy-eval/checks",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/concepts/node-selector-strategy",
+    "destination":
+      "/nomad/tools/autoscaling/concepts/policy-eval/node-selector-strategy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/vault-integration",
+    "destination": "/nomad/docs/integrations/vault",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-integration",
+    "destination": "/nomad/docs/integrations/consul",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/integrations/consul-connect",
+    "destination": "/nomad/docs/integrations/consul/service-mesh",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/tools/autoscaling/agent/source",
+    "destination": "/nomad/tools/autoscaling/agent/policy",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/remote/:slug*",
+    "destination": "nomad/plugins/drivers/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/community/lxc",
+    "destination": "/nomad/plugins/drivers/community/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/client",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/drivers/virt/installation",
+    "destination": "/nomad/plugins/drivers/virt/install",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/docs/devices",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community",
+    "destination": "/nomad/plugins/devices/",
+    "permanent": true,
+  },
+  {
+    "source": "/nomad/plugins/devices/community/usb",
+    "destination": "/nomad/plugins/devices/usb",
+    "permanent": true,
+  },
+]
diff --git a/productConfig.mjs b/productConfig.mjs
index c03456b96e..f4192caa1b 100644
--- a/productConfig.mjs
+++ b/productConfig.mjs
@@ -115,23 +115,24 @@ export const PRODUCT_CONFIG = {
 		versionedDocs: false,
 		websiteDir: '.',
 	},
-	// nomad: {
-	// 	/**
-	// 	 *  🟢🟢🟡 Initial migration attempt: CONTENT NOT FOUND on older versions
-	// 	 *
-	// 	 * Fails for v0.12.x (and likely earlier) with error:
-	// 	 * `nomad/website/content: No such file or directory`
-	// 	 * This likely indicates that older versions of docs have a different
-	// 	 * directory structure that needs to be accounted for. Need to confirm.
-	// 	 */
-	// 	assetDir: 'public',
-	// 	contentDir: 'content',
-	// 	dataDir: 'data',
-	//  productSlug: 'nomad',
-	// 	semverCoerce: semver.coerce,
-	//  versionedDocs: true,
-	// 	websiteDir: 'website',
-	// },
+	nomad: {
+		/**
+		 *  🟢🟢🟡 Initial migration attempt: CONTENT NOT FOUND on older versions
+		 *
+		 * Fails for v0.12.x (and likely earlier) with error:
+		 * `nomad/website/content: No such file or directory`
+		 * This likely indicates that older versions of docs have a different
+		 * directory structure that needs to be accounted for. Need to confirm.
+		 */
+		assetDir: 'public/img',
+		basePaths: ['api-docs', 'docs', 'commands', 'plugins', 'tools'],
+		contentDir: 'content',
+		dataDir: 'data',
+		productSlug: 'nomad',
+		semverCoerce: semver.coerce,
+		versionedDocs: true,
+		websiteDir: 'website',
+	},
 	packer: {
 		/**
 		 *  🟢🟢🟡 Initial migration attempt: CONTENT NOT FOUND on older versions
diff --git a/scripts/prebuild/prebuild-arm-linux-binary.gz b/scripts/prebuild/prebuild-arm-linux-binary.gz
index 38983fb9ae..9a825a61ab 100755
Binary files a/scripts/prebuild/prebuild-arm-linux-binary.gz and b/scripts/prebuild/prebuild-arm-linux-binary.gz differ
diff --git a/scripts/prebuild/prebuild-arm-mac-binary.gz b/scripts/prebuild/prebuild-arm-mac-binary.gz
index 6f4304fcac..8beb428174 100755
Binary files a/scripts/prebuild/prebuild-arm-mac-binary.gz and b/scripts/prebuild/prebuild-arm-mac-binary.gz differ
diff --git a/scripts/prebuild/prebuild-x64-linux-binary.gz b/scripts/prebuild/prebuild-x64-linux-binary.gz
index e158960474..d8c19caaeb 100755
Binary files a/scripts/prebuild/prebuild-x64-linux-binary.gz and b/scripts/prebuild/prebuild-x64-linux-binary.gz differ